diff --git a/marked/G/T-REC-G.102-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.102-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..657d3ff5a8401033b2b2d4a653b210ed5f2aa1fd --- /dev/null +++ b/marked/G/T-REC-G.102-198811-I_PDF-E/raw.md @@ -0,0 +1,136 @@ + + +![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.102** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**TRANSMISSION SYSTEMS AND MEDIA** + +**GENERAL CHARACTERISTICS OF INTERNATIONAL +TELEPHONE CONNECTIONS AND INTERNATIONAL +TELEPHONE CIRCUITS** + +--- + +**TRANSMISSION PERFORMANCE OBJECTIVES +AND RECOMMENDATIONS** + +**ITU-T Recommendation G.102** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.102 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 PERFORMANCE OBJECTIVES AND RECOMMENDATIONS** + +*(Geneva, 1980)* + +## **1 General** + +The CCITT has drawn up (or is in the process of studying) Recommendations concerning transmission impairments and their permissible magnitude with the object of achieving satisfactory performance of the network. Such impairments include for example: + +- a) loudness rating (LR) and loss, +- b) noise, +- c) attenuation distortion, +- d) crosstalk, +- e) single tone interference, +- f) spurious modulation, +- g) effects of errors in digital systems. + +Some Recommendations state objectives for an impairment with the implicit assumption that other impairments are at their maximum value (e.g. noise and loss). + +In many instances the objectives are based primarily on telephony; this however may require special measures to be applied when other, more demanding services (e.g. sound-programme transmission) are to be incorporated within the network or constituent parts thereof. + +The following distinctions may be made between different types of objectives: + +- 1) performance objectives for networks, +- 2) performance objectives for circuits, transmission and switching equipment, +- 3) design objectives for transmission and switching equipment, +- 4) commissioning objectives for circuits, transmission and switching equipment, +- 5) maintenance/service limits for circuits, transmission and switching equipment. + +## **2 Explanation of a performance objective** + +The performance objective for a measurable transmission impairment for networks, entire connections, national systems forming part of international connections, international chains of circuits, individual circuits etc. often describes in statistical terms (mean value, standard deviation, or probability of exceeding stated value, etc.) the value to be aimed at in transmission network and systems planning. It describes the performance which, based for example on subjective or other performance assessment tests, it is desirable to aim at in order to offer the user a satisfactory service. + +The items (circuits, systems, equipments) making up the network are normally assumed to have a performance related to that recommended by the performance objectives. Traffic weighting will, in some cases, be applied to calculations. + +A powerful set of tools which may be used in analyses concerning network objectives and compliance therewith are the hypothetical reference connections described in Recommendation G.103. + +## **3 Explanation of a design objective** + +The "design objective" for a measurable transmission impairment (e.g. noise, error-rate, attenuation-distortion) for an item of equipment (e.g. a line system, a telephone exchange) is its value when the item is operating in certain electrical/physical environments which might be defined by such parameters as power supply voltage, signal load, temperature, humidity, etc. Some of these parameters may be the subject of CCITT Recommendations and some may not, and it is for the Administrations to assign values to them when they prepare specifications. A suitable allowance may also be made for aging. The most adverse combination of the specified parameters is often assumed. + +The purpose of a "design objective" is to provide a basis for the design of an item with respect to the quantity concerned. The significance of the design objective for an item, and examples of the relative frequency of impairment values, are illustrated in Figures 1/G.102 and 2/G.102 respectively. + +Design objectives will in many cases directly form the basis of a specification clause for the development and/or the purchase of equipments. + +A powerful set of tools used in connection with applying design objectives are the hypothetical reference (HR) circuits and hypothetical reference (HR) digital paths (see relevant Recommendations in the G.100 and G.700 Series). + +## **4 Explanation of a commissioning objective** + +The conditions encountered on real circuits and installed equipment may differ from the assumptions valid for the HR circuits and for the design of equipment. Therefore the performance to be expected at the time of commissioning cannot be deduced uniquely from Recommendations relating to HR circuits. Suitable allowances may have to be made for such matters as circuits being made up of equipments of different design, line systems differing substantially in length from a homogeneous section, etc. (see for example Recommendation G.226 [1] for noise on real links). + +Commissioning objectives are not normally the subject of CCITT Recommendations. + +## **5 Explanations of limits for maintenance purposes** + +In service, the performance of an item or assembly of items may deteriorate for various reasons: aging, excessive loading, excessive environmental conditions, operations errors, components failures, etc. and there is an economic penalty in service costs if such deterioration is always to be kept negligibly small. Therefore design objectives are chosen to confer as great a margin as possible to assure a satisfactory in-service performance. + +![Figure 1/G.102: Illustration of the significance of design objective for an item. The diagram shows a horizontal axis representing increasing values of impairment (e.g., noise power, error rate, etc.). The axis is divided into three regions: 'Fully acceptable range', 'Tolerable range', and 'Unusable'. Key points on the axis are marked with vertical lines and labels: 'Value when the operating environment is at its optimum (e.g. power supplies producing nominal voltages, temperature at mid-range, etc.). This inherent, irreducible value is zero in some cases.'; 'The design objective, as explained in the text, for the item (e.g. system, exchange, equipment, etc.)'; 'Maximum acceptable value at commissioning for a particular set of operating conditions (may also be the same as the line-up limit)'; 'Maintenance limit at which attention is alerted (e.g. deferred maintenance limit)'; and 'Maintenance limit at which point the item is taken out of service (e.g. prompt maintenance limit)'. A 'Design allowance' is indicated between the optimum value and the design objective. A note states 'Acceptable value at time of commissioning lies within this range'. A bracket on the right indicates 'Increasing values of impairment (e.g. noise power, error rate, etc.)'. A legend at the bottom right distinguishes between 'A value ordinarily not the subject of CCI Recommendations' and 'A value which is ordinarily the subject of CCI Recommendations'. The code 'CCITT - 27 701' is also present.](f9a14fbfecbd7d059226cc93677d721b_img.jpg) + +Figure 1/G.102: Illustration of the significance of design objective for an item. The diagram shows a horizontal axis representing increasing values of impairment (e.g., noise power, error rate, etc.). The axis is divided into three regions: 'Fully acceptable range', 'Tolerable range', and 'Unusable'. Key points on the axis are marked with vertical lines and labels: 'Value when the operating environment is at its optimum (e.g. power supplies producing nominal voltages, temperature at mid-range, etc.). This inherent, irreducible value is zero in some cases.'; 'The design objective, as explained in the text, for the item (e.g. system, exchange, equipment, etc.)'; 'Maximum acceptable value at commissioning for a particular set of operating conditions (may also be the same as the line-up limit)'; 'Maintenance limit at which attention is alerted (e.g. deferred maintenance limit)'; and 'Maintenance limit at which point the item is taken out of service (e.g. prompt maintenance limit)'. A 'Design allowance' is indicated between the optimum value and the design objective. A note states 'Acceptable value at time of commissioning lies within this range'. A bracket on the right indicates 'Increasing values of impairment (e.g. noise power, error rate, etc.)'. A legend at the bottom right distinguishes between 'A value ordinarily not the subject of CCI Recommendations' and 'A value which is ordinarily the subject of CCI Recommendations'. The code 'CCITT - 27 701' is also present. + +FIGURE 1/G.102 + +### **Illustration of the significance of design objective for an item** + +With transmission impairments, there is often no value which represents a clear boundary between "tolerable" and "unusable" performance and in practice a range of impairments in excess of those provided by design objectives will give satisfactory service to customers. This is the case for telephony but for other services may be different. + +Nevertheless it is often expedient to define a particular value of impairment above which the item is deemed to be "unusable" and at which the item will be withdrawn from service at the first opportunity so that remedial action can be taken to restore the performance to comply with some defined limit (e.g. limit for prompt maintenance action). + +It is often useful to define a performance limit at which attention is alerted but (perhaps) no action is taken immediately (e.g. limit for deferred maintenance action). + +These limits are usually independent of the type of service carried by that particular entity. However, it is sometimes necessary to define a performance limit for a particular type of service, beyond which the customer is no longer offered a satisfactory service quality. This limit may differ for various services; some may coincide with a prompt maintenance limit (service limit). + +These limits (and others, if necessary) would fall above the design objective. These limits are illustrated in Figure 1/G.102 and a generic title for them is "maintenance limits". + +![Figure 2/G.102: Examples of the relative frequency of impairment values. The graph plots 'Relative frequency of occurrence' on the y-axis against 'values of impairment' on the x-axis. Three curves are shown: Curve 1 (solid line, highest peak), Curve 2 (solid line, lower peak), and Curve 3 (dashed line, lowest peak). The x-axis is divided into three regions: 'Fully acceptable range', 'Tolerable range', and 'Unusable'. A vertical line marks the 'Design objective'. An arrow indicates 'Increasing values of impairment' to the right. The text 'CCITT - 27 710' is in the bottom right corner.](431b8889a0e7f676f0eef40859590349_img.jpg) + +Figure 2/G.102: Examples of the relative frequency of impairment values. The graph plots 'Relative frequency of occurrence' on the y-axis against 'values of impairment' on the x-axis. Three curves are shown: Curve 1 (solid line, highest peak), Curve 2 (solid line, lower peak), and Curve 3 (dashed line, lowest peak). The x-axis is divided into three regions: 'Fully acceptable range', 'Tolerable range', and 'Unusable'. A vertical line marks the 'Design objective'. An arrow indicates 'Increasing values of impairment' to the right. The text 'CCITT - 27 710' is in the bottom right corner. + +Such curves may be obtained for ensembles of items of equipment at the time of commissioning. + +Alternatively curves may be plotted representing the performance of an item during its lifetime. + +Curve 1 - Example of relative frequency of occurrence of impairments at time of commissioning in which the design value is met with some margin. A similar distribution might be achieved in service throughout the lifetime of an item of equipment if the effect of environmental conditions etc. is negligible. An example might be the attenuation distortion of transformers. + +Curve 2 - Example of the relative frequency of occurrence of impairments at time of commissioning in which the design value is exceeded with some agreed probability because the item of equipment is used in a way which is more demanding than that in the design objectives. An example might be the effect of a repeater spacing of a radio or line system greater than anticipated. + +Curve 3 - Example of the relative frequency of occurrence of impairments in service in which the working environment has parameters more onerous than or additional to those specified. Examples might be the effect of excessive loading, component failure or operational errors. + +FIGURE 2/G.102 + +### **Examples of the relative frequency of impairment values** + +## **Reference** + +- [1] CCITT Recommendation *Noise on a real link*, Vol. III, Rec. G.226. \ No newline at end of file diff --git a/marked/G/T-REC-G.105-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.105-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fbbdc6aeb0507004caf898e4a12cdf8be0a5a54 --- /dev/null +++ b/marked/G/T-REC-G.105-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4e27a2aadb44e4b437298e4ee95b0b6c40a5eacb6141222fd7d412000148456 +size 7504 diff --git a/marked/G/T-REC-G.105-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/G/T-REC-G.105-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1172644eecc69a16e5d88cdc33b522b0ae2f85ad --- /dev/null +++ b/marked/G/T-REC-G.105-198811-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d26b40063ab34f6e3f3c9f744fc457af105841ef2c71b5ed74798c2db2557bb +size 54954 diff --git a/marked/G/T-REC-G.105-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg b/marked/G/T-REC-G.105-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5363210e823f684e492f8e1023749af888e88bad --- /dev/null +++ b/marked/G/T-REC-G.105-198811-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:061b2e19eb515433d8f15b24abd3dcda6c937dac59f22793f2b816b956308b2e +size 59830 diff --git a/marked/G/T-REC-G.105-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/marked/G/T-REC-G.105-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0195c41765508cd952d92ec97802c39e4502d150 --- /dev/null +++ b/marked/G/T-REC-G.105-198811-I_PDF-E/a7d78d22e465dea388b31d0739f9d0cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c13fd8e7ed2f69cf65174564e16ae05c4ebc03d1a9ebd290d601a0f83498f355 +size 42963 diff --git a/marked/G/T-REC-G.105-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg b/marked/G/T-REC-G.105-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eea0312667568e916accda5559051f0a6e860058 --- /dev/null +++ b/marked/G/T-REC-G.105-198811-I_PDF-E/f9a14fbfecbd7d059226cc93677d721b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:088b3f0d8cfda705a9b526484dbf262b292990b632ac93d4f275d330af1c1997 +size 61903 diff --git a/marked/G/T-REC-G.1072-202001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.1072-202001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/G/T-REC-G.1072-202001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/G/T-REC-G.1072-202001-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/G/T-REC-G.1072-202001-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b38fac077b4dc41588c62d6536b4eaad1a98754 --- /dev/null +++ b/marked/G/T-REC-G.1072-202001-I_PDF-E/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02358618111d1ed34800ad09b817ce9698f8e9cb4e077cfbb2c346f316ce763f +size 77575 diff --git a/marked/G/T-REC-G.1072-202001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.1072-202001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..828eb5d9ed74a3a9b6cde087e4cffb76aa1c81d0 --- /dev/null +++ b/marked/G/T-REC-G.1072-202001-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd1cd24371cf12b76a29f00ade676ef8eb5711bae1f966ec7f1df7e753f90b4d +size 85848 diff --git a/marked/G/T-REC-G.1082-200904-I_PDF-E/raw.md b/marked/G/T-REC-G.1082-200904-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00fcd7da6355c364582cd7a7fa8bc1a7788742a2 --- /dev/null +++ b/marked/G/T-REC-G.1082-200904-I_PDF-E/raw.md @@ -0,0 +1,671 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.1082** + +(04/2009) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Multimedia Quality of Service and performance – Generic +and user-related aspects + +# --- **Measurement-based methods for improving the robustness of IPTV performance** + +Recommendation ITU-T G.1082 + +## 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.1082** + +# **Measurement-based methods for improving the robustness of IPTV performance** + +## **Summary** + +Recommendation ITU-T G.1082 provides a framework for improving the robustness of IPTV performance based on the results of real-time measurements. The primary application of this framework is to control the media and network resources based on the measurement information and according to policy rules to support high quality of experience of IPTV services. + +For IPTV services, service providers and network providers may have separate monitoring systems. Measurement information is provided by the monitoring system. This Recommendation first describes the possible measurement information used in different monitoring domains and the information exchanged between providers. It then gives guidance on how to take these factors into account to adjust media and network resources in order to maintain the quality of experience for IPTV services. + +## **Source** + +Recommendation ITU-T G.1082 was approved on 29 April 2009 by ITU-T Study Group 12 (2009-2012) under Recommendation ITU-T A.8 procedure. + +## **Keywords** + +IPTV, measurement, QoE, QoS, resource adjustment. + +## 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 | Definitions ..... | 1 | +| 4 | Abbreviations and acronyms ..... | 1 | +| 5 | Conventions ..... | 2 | +| 6 | Overview of the framework of measurement-based methods for improving the robustness of IPTV performance (MMRP) ..... | 2 | +| 7 | Process of end-to-end quality improvement ..... | 3 | +| 7.1 | Monitoring system..... | 4 | +| 7.2 | Measurement-based resource adjustment function ..... | 4 | +| 7.3 | Resource control enforcement ..... | 5 | +| 8 | Measurement information reporting..... | 5 | +| 8.1 | Reported measurement information ..... | 5 | +| 8.2 | Intra-domain interactions..... | 7 | +| 9 | Information exchanged between providers..... | 8 | +| 9.1 | Information provided by SPs..... | 8 | +| 9.2 | Information provided by NPs ..... | 8 | +| 9.3 | Information exchanged between SPs and NPs ..... | 8 | +| 9.4 | Inter-domain interactions..... | 9 | +| 10 | Measurement-based adaptive resource control for IPTV services ..... | 10 | +| 10.1 | Media resource control ..... | 10 | +| 10.2 | Network resource control ..... | 10 | +| 11 | Security consideration ..... | 11 | +| | Appendix I – QoE evaluation in mid-point..... | 12 | +| I.1 | Introduction ..... | 12 | +| I.2 | Collaboration between SP and NP to evaluate QoE in mid-point..... | 12 | +| | Appendix II – Encoded bit rate adjustment in the head-end system..... | 14 | +| | Appendix III – Encoded layer adjustment ..... | 16 | +| III.1 | Introduction ..... | 16 | +| III.2 | Network device adjusts the encoded layer ..... | 16 | +| III.3 | STB adjusts the encoded layer ..... | 17 | +| | Appendix IV – Delivery path adjustment ..... | 19 | +| | Bibliography..... | 21 | + + + +## Recommendation ITU-T G.1082 + +# Measurement-based methods for improving the robustness of IPTV performance + +# 1 Scope + +This Recommendation describes some methods by which measurement information of IPTV service quality can be used to dynamically control the performance of an IPTV service such as network resource allocation, FEC redundant encoding, delivery path selection or media encoding bit rate if scalable encoding is employed. + +This Recommendation defines the subset of QoS/QoE performance parameters to be obtained from the IPTV monitoring system and methods for analysing them to provide media resource and transport network resource control in support of high quality end-to-end delivery of IPTV services. + +It also provides guidance on the collaboration between different providers and defines the metrics to be exchanged between them for resource management. + +# 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.1080] Recommendation ITU-T G.1080 (2008), *Quality of experience requirements for IPTV services*. +- [ITU-T G.1081] Recommendation ITU-T G.1081 (2008), *Performance monitoring points for IPTV*. +- [ITU-T Y.1540] Recommendation ITU-T Y.1540 (2007), *Internet protocol data communication service – IP packet transfer and availability performance parameters*. + +# 3 Definitions + +This Recommendation does not define any special terms. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|---------------------------| +| DiffServ | Differentiated Services | +| FEC | Forward Error Correction | +| GOP | Group Of Pictures | +| IP | Internet Protocol | +| IPDV | IP packet Delay Variation | +| IPLR | IP packet Loss Ratio | +| IPTD | IP packet Transfer Delay | + +| | | +|-------|----------------------------------------------------------------------------| +| IPTV | Internet Protocol Television | +| MMPAP | Monitoring Management and Performance Analysis Platform | +| MMRP | Measurement-based Methods for improving the Robustness of IPTV Performance | +| MOS | Mean Opinion Score | +| MPLS | Multi-Protocol Label Switching | +| NP | Network Provider | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RFC | Request For Comments | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SLA | Service Level Agreement | +| SP | Service Provider | +| STB | Set-Top Box | +| UDP | User Datagram Protocol | +| VoD | Video on Demand | + +# 5 Conventions + +None. + +# 6 Overview of the framework of measurement-based methods for improving the robustness of IPTV performance (MMRP) + +In IPTV services, the QoE is a great concern to the end users. The user expects the perceptual quality of IPTV services to be as good as or even better than that of conventional TV service. In order to achieve the user's expectation, a QoS/QoE monitoring system becomes an indispensable part of the IPTV services. + +In a conventional monitoring system, the measurement information is only used for evaluating network performance and QoE of end users. However, this information can also be valuable input for providing media resource and transport network resource control in support of high quality of experience of IPTV services. The SP and NP can adjust the media and network resources based on the measurement information. The resource adjustment procedure includes the steps of reporting measurement information, exchanging information between SP and NP, and deciding resource adjustment methods by SP and NP. Figure 1 depicts a reference model for a MMRP system. + +![Figure 1 – Reference model. A diagram showing the architecture of an IPTV system with monitoring and control components. At the top, a 'Policy' icon points to two boxes: 'Analysis for media resource control' and 'Analysis for network resource control', which are interconnected. Below this, three main domains are shown: 'Service Provider', 'Network Provider', and 'End user'. The Service Provider contains a VoD server, an Encoder, and a Service server connected to a monitoring point (PT). The Network Provider contains an IP core network and an IP access network, each with a PT. The End user contains an HGW and an STB connected to a PT. Below these domains are two 'Monitoring, Management and Performance Analysis Platform' boxes, one for the Service Provider (SP) and one for the Network Provider (NP), which are also interconnected. Arrows show data flow from the PTs in each domain to their respective MMPAPs. Red lines connect the MMPAPs back to the analysis boxes at the top.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +Figure 1 – Reference model. A diagram showing the architecture of an IPTV system with monitoring and control components. At the top, a 'Policy' icon points to two boxes: 'Analysis for media resource control' and 'Analysis for network resource control', which are interconnected. Below this, three main domains are shown: 'Service Provider', 'Network Provider', and 'End user'. The Service Provider contains a VoD server, an Encoder, and a Service server connected to a monitoring point (PT). The Network Provider contains an IP core network and an IP access network, each with a PT. The End user contains an HGW and an STB connected to a PT. Below these domains are two 'Monitoring, Management and Performance Analysis Platform' boxes, one for the Service Provider (SP) and one for the Network Provider (NP), which are also interconnected. Arrows show data flow from the PTs in each domain to their respective MMPAPs. Red lines connect the MMPAPs back to the analysis boxes at the top. + +**Figure 1 – Reference model** + +A monitoring system includes monitoring points (labelled PTs) and a monitoring, management and performance analysis platform (MMPAP). MMPAP manages one or multiple domains and collects measurement data from the monitoring points. The MMPAP of the SP collects information from the head-end system and the end-user system. The MMPAP of the NP collects information from backbone and access network domains. Note that the monitoring points located in a service provider's domain have different capabilities from those located in a network provider's domain. Based on the measurement data collected from monitoring points, the MMPAP provides the QoE metrics and other information of IPTV services. If the QoE metrics are below a certain predefined value, which is defined in the policy, it may trigger a network resource adjustment procedure, a media resource adjustment procedure or both. Since one single provider has limited measurement information, the SP and NP may share a set of information to decide on a resource adjustment method. During the procedures, the end users may not perceive the quality degradation of IPTV services. + +# 7 Process of end-to-end quality improvement + +MMPAP is located in the SP and NP administrative areas. The measurement-based resource adaptive control function collects the information from one or more MMPAP. The media and network resource is adjusted in a centralized model or in a distributed model. + +### Centralized model + +A single resource adaptive control function is responsible for the management of media and network resources. It collects measurement information from all the MMPAPs. If a MMPAP is + +under a different administrative area, it is not easy to aggregate the information and control the resource of entire domains. + +### Distributed model + +A number of adaptive resource control functions are responsible for the management of media and network resources. Each resource adaptive control function collects measurement information from its associated MMPAP and manages the resource of administrative domains. The measurement information is exchanged between adaptive resource control functions which collaborate with each other for the end-to-end quality maintenance. + +This Recommendation describes a distributed model. The SP and NP collect measurement information from their MMPAP and share a part of the measurement information with each other. Based on measurement and auxiliary information, SP and NP first decide which provider is responsible for adjusting the resource. Then, the media and transport network resource is adapted to maintain the end-to-end quality. Figure 2 illustrates this process. + +![Figure 2 – Resource control process flowchart](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` +graph LR; subgraph MS [Monitoring system]; MS1[Collect and analyse measurement data]; MS2[Report measurement information]; end; subgraph MRACF [Measurement-based resource adaptive control function]; MRACF1[Collect measurement information from own monitoring system]; MRACF2[Collect measurement information shared from other providers]; MRACF3[Information analysis based on resource control policy]; end; subgraph RCE [Resource control enforcement]; RCE1[Adjust the resource]; end; MS --> MRACF; MRACF --> RCE; +``` + +The diagram illustrates the resource control process flow. It consists of three main components connected sequentially from left to right. The first component is the 'Monitoring system', which contains two sub-functions: 'Collect and analyse measurement data' and 'Report measurement information'. An arrow points from the 'Monitoring system' to the second component, 'Measurement-based resource adaptive control function'. This function contains three sub-functions: 'Collect measurement information from own monitoring system', 'Collect measurement information shared from other providers', and 'Information analysis based on resource control policy'. An arrow points from the 'Measurement-based resource adaptive control function' to the third component, 'Resource control enforcement', which contains the sub-function 'Adjust the resource'. + +Figure 2 – Resource control process flowchart + +Figure 2 – Resource control process + +## 7.1 Monitoring system + +The monitoring points collect measurement metrics. The MMPAP entities will process these metrics, e.g., correlate and aggregate metrics, etc., and generate measurement reports. The reporting information obtained by processing metrics extracted from a different domain is described in clause 8. + +## 7.2 Measurement-based resource adjustment function + +Based on the reported measurement information, the NP and SP first decide the status of the perceived quality. If the measurement information indicates a trend of degradation or occurring degradation, the NP and SP will analyse how to adjust the resource to maintain the perceived quality at an expected level. + +Because of the limited ability of the SP and NP, one single provider may not be able to obtain all the information needed for resource control. The SP and NP share information with each other. The SP needs the network resource and network performance information to adjust the media resource. The NP needs the expected or experienced QoE of the user to make sure that the resource adjustment facilitates QoE. The information to be exchanged and methods for exchange are described in clause 9. + +The resource control policy instructs the SP and NP what to do. For example, if measurement information indicates mild quality degradation, one provider may adjust the network resource to + +improve the experienced quality. If serious degradation occurs, the SP and NP need to enforce the resource adjustment simultaneously. In order to adapt media and network resources, measurement information reported by MMPAP is analysed. Clause 10 describes the measurement-based resource adaptive methods. + +## 7.3 Resource control enforcement + +The last step is to enforce resource adjustment in media processing devices and network devices to ensure a high quality of experience. + +# 8 Measurement information reporting + +As shown in Figure 3, there are 5 types of monitoring points, depending on the location. Along with the IPTV services delivery path, the monitoring points, which possess different capabilities, collect the required measurement data. + +![Figure 3: Monitoring points (PT1 to PT6) diagram showing the IPTV service delivery path across five domains (A-E) with various monitoring points (PT1-PT5) and a monitoring platform at the bottom.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the IPTV service delivery path across five domains (A-E) and the locations of monitoring points (PT1 to PT5). The domains are: Domain A (Content provider), Domain B (Service provider (central headend)), Domain C (Service provider (regional headend)), Domain D (Network provider), and Domain E (End user). Monitoring points are indicated by blue boxes with 'PT' labels. A 'Monitoring, management and performance analysis platforms' bar is at the bottom, with orange arrows pointing to it from each domain. + +- Domain A (Content provider):** Includes 'Local content acquisition' (PT1), 'Metadata' (PT1), and 'Encoder' (PT1). +- Domain B (Service provider (central headend)):** Includes 'Encoder' (PT1), 'Transcoder' (PT1), 'Core VoD server' (PT2), and 'Services server' (PT2). +- Domain C (Service provider (regional headend)):** Includes 'RX' (PT1), 'Encoder' (PT1), and 'VoD server' (PT1). +- Domain D (Network provider):** Includes 'IP core network' (PT3), 'IP access network' (PT4), and 'Edge VoD server multicast replication point' (PT4). +- Domain E (End user):** Includes 'Home gateway' (PT5), 'STB' (PT5), and 'TV' (PT5). + +G.1082(09)\_F03 + +Figure 3: Monitoring points (PT1 to PT6) diagram showing the IPTV service delivery path across five domains (A-E) with various monitoring points (PT1-PT5) and a monitoring platform at the bottom. + +Figure 3 – Monitoring points (PT1 to PT6) + +## 8.1 Reported measurement information + +The MMPAP collects the measurement data from the monitoring points. After MMPAP processing, a set of metrics will be sent to the measurement-based adaptive resource control function. + +In Figure 3, Domain A provides content-related information, which is outside of the scope of this Recommendation. + +Domain B, in Figure 3, provides media encoded parameters and service quality. The following information elements may be reported by MMPAP after processing the information extracted from this domain. + +| Information | Description | +|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identifier of media flow | One example is 5-tuple of IP packet. It is transmitted with measurement information. | +| General program attribute | | +| – Service type. | Indicate the application, e.g., linear TV, VoD. The resource control policy and method is different for each application. | +| – Total bit rate. | For multimedia services, it is the sum of the bit rate of video, audio, embedded program information when present. | +| Video parameters | | +| – Bit rate of video. | | +| – Encoding format of video content. | | +| – Resolution of video content. | | +| – GOP parameters. | Include GOP size, e.g., 9, 12, etc., and GOP structure, e.g., I, P, B, IBP, IBBP, etc. | +| – Timestamp of I frames. | In encoding processing, the timestamp that reflects the sampling instant of I frames is derived. It may be provided to NP for frame-related metrics calculation. | +| Audio parameters | | +| – Number of audio channels. | | +| – Bit rate of each audio channel. | | +| – Encoding format of audio channels. | | +| Video quality. | The video quality (e.g., in terms of MOS) before being sent into the network. | +| Audio quality. | The audio quality (e.g., in terms of MOS) before being sent into the network. | +| Multimedia quality. | The multimedia quality (e.g., in terms of MOS) before being sent into the network. | + +The monitoring points located in domains C and D collect network-related metrics for monitoring media flows, including packet loss, delay, jitter, etc. The MMPAP deployed in the network domain collects and processes these metrics. The following measurement information elements may be reported by the MMPAP: + +| Information | Description | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Identifier of media flow. | One example is 5-tuple of IP packet. It is transmitted with measurement information. | +| IP network capacity information. | The metrics are defined in [b-IETF RFC 5136] and Appendix VIII of [ITU-T Y.1540], including available link capacity and available path capacity. | +| IP network performance. | Measurement points in mid-point get network performance parameters. The metrics are defined in [ITU-T Y.1540], including IPLR, IPTD and IPDV. | + +| Information | Description | +|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| One-way loss pattern related performance. | For real-time IPTV services, burst packet loss is essential and may be taken into account in performance analysis. The metrics are defined in [b-IETF RFC 3357], including loss distance, loss period, and in Appendix VII of [ITU-T Y.1540] for impaired interval ratio. | +| Video quality. | Indicate the video quality (e.g., in terms of MOS) in the network domain. | +| Audio quality. | Indicate the audio quality (e.g., in terms of MOS) in the network domain. | +| Multimedia quality. | Indicate the multimedia quality (e.g., in terms of MOS) in the network domain. | + +The monitoring points located in domain E (home network) are capable of collecting more sophisticated metrics. The following measurement information elements may be presented by the MMPAP that manages this domain. + +| Information | Description | +|---------------------------|------------------------------------------------------------------------------------------------| +| Identifier of media flow. | One example is a 5-tuple. It is transmitted with measurement information. | +| Video quality. | Indicate the experienced video quality (e.g., in terms of MOS) perceived by the end user. | +| Audio quality. | Indicate the experienced audio quality (e.g., in terms of MOS) perceived by the end user. | +| Multimedia quality. | Indicate the experienced multimedia quality (e.g., in terms of MOS) perceived by the end user. | + +Packet network measurements on the home network may require an additional monitoring point at the home gateway, and are for further study. + +## 8.2 Intra-domain interactions + +The MMPAP sends the measurement information to the measurement-based resource adaptive control function. The interaction mainly includes the following three mechanisms. + +### Request-response transactions + +When the adaptive resource control function needs current performance status, it may request the MMPAP to provide the information. For example, the adaptive network resource control function may request the latest network available resource to adjust the delivery path. + +### Notification + +The MMPAP may predefine the threshold of measurement information and report the metric which exceeds the threshold. For example, the QoE-related metric collected from end-points can be informed of the media resource adaptive control function in SP immediately, if it is below a predefined value. + +### Periodic reports + +The MMPAP may report the measurement information in a periodical manner. + +# 9 Information exchanged between providers + +In the end-to-end IPTV services delivery, service providers (SPs) and network providers (NPs) might be under different administrative domains and be responsible for head-end processing and media flow delivery, respectively. Since the SPs and the NPs have different capabilities to access the media-related information and network-related information, there is a need to exchange information between SPs and NPs. It is not mandatory that the information listed below be shared. Some information may be difficult to be obtained/exchanged in some scenarios. Conversely, there may be some other information that is essential. + +## 9.1 Information provided by SPs + +In general, the IPTV service providers deploy head-end and end-point (i.e., STB) systems. At the head-end, it is capable of providing the codec-related information such as codec type, bit rate, etc. At the end-point, it is capable of monitoring the end-to-end QoE-related performance experienced by the end user. + +## 9.2 Information provided by NPs + +As for the network providers, they provide the bearer network for IPTV services. They are capable of providing network-related information such as packet loss, delay, jitter, available bandwidth, etc. + +## 9.3 Information exchanged between SPs and NPs + +In clause 8, it has been described that MMPAPs of SPs and NPs collect and report different monitoring information. Performance metrics collected in different domains may be gathered for more comprehensive analysis. + +The NP needs 1) the information collected from the head-end system to analyse QoE related performance; 2) information about the detailed behaviour at the head-end system, the quality experienced at the end-user side and SLA information, while deciding how to control the network resources. The following information may be provided from SP to NP through their MMPAPs for the first purpose, and through their adaptive resource control functions for the second purpose. Some information can be used for both purposes. + +| Information | Description | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identifier of media flow. | It is transmitted with the exchanged data. According to the identifier, the NP can find the information of the same media flow, collected from the network domain. | +| General program attribute. | | +| – Service type. | Based on service type, e.g., linear TV, VoD, the network resource is adjusted by different methods. | +| – Total bit rate. | It may be exchanged between MMPAPs when the NP needs to analyse QoE-related performance. | +| Video parameters. | They are exchanged between MMPAPs if the NP needs to analyse QoE-related performance. | +| – Bit rate of the video. | Besides QoE-related performance analysis, the NP considers the encoded bit rate for encoded layer adjustment when a scalable encoding method is used at the head end system. | +| – Encoding format of video content. | | +| – Resolution of video content. | | +| – GOP parameters. | It may be used in frame-related metrics calculation. | +| – Timestamp of I frames. | It may be used in frame-related metrics calculation. | + +| Information | Description | +|---------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Audio parameters. | They are exchanged between MMPAPs if the NP needs to analyse QoE-related performance. | +| – Bit rate of each audio channel. | | +| – Encoding format of the audio channels. | | +| Video/Audio/Multimedia quality from domain E. | It triggers the NP to adjust the network resource.
If the NP has the ability to collect this value from the end user, the value does not need to be exchanged. | +| SLA information. | Help the NP take a reasonable resource control decision if quality degradation is detected. | +| – User's agreement on experienced quality of IPTV services. | It may be an exact value or a range of accepted values. It is used for encoded layer adjustment in the network domain. | +| Configuration of application-layer error correction and concealment (e.g., forward error correction type and block size). | May be adjusted for network conditions, and can be used to enhance measurement efficiency and applicability. | + +On the other hand, the head-end system needs to know the network conditions in order to manage media resources. For this purpose, the following information may be provided from NP to SP: + +| Information | Description | +|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identifier of media flow. | It is transmitted with the exchanged data. Using the identifier, the SP finds the information of the same media flow collected from the head end system. | +| IP network capacity information. | | +| – Available path capacity. | It indicates the capacity of an end-to-end delivery path or a path between two network nodes. The SP adjusts the media resource according to the network's available capacity. | + +## 9.4 Inter-domain interactions + +NPs and SPs may have inter-provider agreements, which determine the interaction mechanism between them. In the above clauses, information may be transmitted from one provider to another. Two kinds of mechanisms are used for sharing information. + +### Request-response transactions + +One provider may request the other one to provide measurement information. It may take place between MMPAP entities for performance analysis or between resource adaptive control functions to adjust media and network resources. For example, NP may request encoding information for QoE performance analysis, or SP may request network resource information for media resource adjustment. + +### Notifications + +One provider may inform the other one in an on-demand manner. For example, if the GOP parameters are adjusted in the encoder, the SP may notify the NP of the new GOP parameters. Another example is that, if the SP detects that the perceived quality of a broadcast service is below the agreed value, it may inform the perceived QoE and other necessary information to the NP to trigger the resource adjustment in network domains. + +# **10 Measurement-based adaptive resource control for IPTV services** + +Based on the measurement information collected in various domains, SPs and NPs can dynamically control the media resource and network resource. If the measurement value exceeds the predefined threshold, SP and NP may share some necessary information and choose a proper method to adjust the resource to maintain the QoE. + +Information on the performance of network and end-to-end quality is fundamental for resource control. + +In order to implement the QoE assessment at the network mid-point, the SP and NP will collaborate with each other. The media server provides codec parameters of a certain media flow. The SP shares it with the NP. After receiving the codec information, the NP either distributes it to the monitoring points for evaluating QoE separately, or evaluates the QoE in a centralized MMPAP. In each situation, monitoring points or the MMPAP first recognize the media flow according to the flow identifier which is transmitted with the codec information. Then, they extract the QoS metrics of such media flow monitored at a monitoring point. QoE is assessed based on the QoS and codec information. Appendix I gives an example about QoE evaluation at network mid-point. + +## **10.1 Media resource control** + +Media resource is associated with media processing, such as codec parameters, established media service connections, etc. The head-end system in the SP domain manages media resources in encoding processing. Besides it, the network device which is aware of media resource can also manage it by analysing measurement information. The following media resource control mechanisms may be enforced in the device. + +### **10.1.1 Encoded bit rate adjustment** + +If the QoE perceived by the end user is below a predefined threshold, a possible reason is that the network cannot provide sufficient resources for the service. Both the encoded bit rate and network available bandwidth resources have an impact on QoE. In order to solve the degradation problem and minimize the impact on other services, the encoding bit rate may be adjustable without interfering with network resource allocation decision. Appendix II provides an example in which the encoded bit rate adjustment mechanism is deployed by SPs for a VoD service. + +### **10.1.2 Encoded layer adjustment** + +The scalable encoding method separates a media flow into two or more encoded layers. The base layer provides a basic level of video quality. The enhancement layers provide a higher experienced quality of media flow. For broadcast services, the media server often encodes the media flow into multi-layers. The end user can receive a set of encoded layers based on its ability and the delivery path capacity. The encoded layer delivered from the network node to the end user is adjusted according to the network capacity and the user's expectation. SP and NP can both adjust the encoded layer with each other's assistance. Appendix III illustrates this mechanism used in the access node and in the STB, respectively. + +## **10.2 Network resource control** + +Network providers may have the ability to obtain network performance and adjust network resources to guarantee end-to-end quality. Transport network resources mainly include the network bandwidth. This clause describes the way the NP adjusts network resources to provide high quality service. + +### **10.2.1 Resource allocation adjustment** + +NP predefines a method to control network resources. For example, if the reported QoE of a critical service indicates degradation caused by insufficient network resources, NP may re-allocate the network resource, e.g., degrade/pause/stop less critical services. This adjustment method may be used to control the access network resource when linear TV, VoD and data services are transmitted to the home network simultaneously. When the access network is insufficient to support all the services, the adaptive network-resource control function will determine the amount of re-allocated resources from less crucial services in terms of transmission performance (e.g., data service, etc.) to highly critical services (e.g., VoD, etc.) based on access link capacity, for example. + +### **10.2.2 FEC adjustment** + +A FEC block encapsulated in RTP packets can be used to minimize the effects of packet loss. The media adaptive resource control function is capable of adjusting the FEC redundant block in the head-end system based on the network condition. If the perceived quality reported by the end user system (e.g., STB) is good enough, the packet loss ratio seems to be under a threshold. The adaptive media resource control function decreases the FEC redundancy. The released network resource is then allocated to other services, e.g., best effort service. Otherwise, the adaptive media resource control function increases the FEC redundant block to facilitate the reconstruction of lost information at the receiver side, i.e., more network resource is allocated to FEC blocks. SP may use this mechanism to control the redundancy in encoding of VoD media flow, for example. + +### **10.2.3 Delivery path adjustment** + +The quality report from the end user devices often indicates the trend of degradation. If it is caused by network congestion, a possible method to avoid the congestion area is to re-establish the delivery path. Network devices may decide a new delivery path to improve the quality. In this mechanism, NP collects topology and resource information under the administrative area. It decides all potential delivery paths between edge nodes and calculates the cost of each path in the network domain. NP may choose a path based on the cost to avoid the congestion area, e.g., the path with least cost is selected. In a manageable network, NP can use this mechanism to adjust the network resource for both linear TV and VoD service. Appendix IV illustrates an example for adjusting the delivery path in an MPLS backbone network. + +# **11 Security consideration** + +There are no specific security considerations in this Recommendation. + +# Appendix I + +## QoE evaluation in mid-point + +(This appendix does not form an integral part of this Recommendation) + +### I.1 Introduction + +The service monitoring server and network monitoring server are regarded as instances of MMPAP in SP and NP, respectively. The service monitoring server collects codec parameters from the media server. The network monitoring server manages the monitoring points and collects performance data from these. This appendix describes how to calculate QoE-related performance in mid-point. + +### I.2 Collaboration between SP and NP to evaluate QoE in mid-point + +The media server provides codec information, including general program attribute, video parameters and audio parameters of media flows (1a). The monitoring point in the network domain monitors QoS information, e.g., IP network performance, one-way loss pattern related performance, etc. (1b). SP and NP already have an agreement to share information for QoE performance analysis. The service monitoring server notifies the codec information to the network monitoring server (2). The QoE of a media flow can be evaluated separately in the monitoring points or centrally in the network monitoring server. Figure I.1 shows a distributive QoE assessment example. + +![Figure I.1: Example for QoE assessment in monitoring points. The diagram shows four entities: Media server, Service monitoring server, Network monitoring server, and Monitoring point. The flow of information is: (1a) Codec information from Media server to Service monitoring server; (2) Codec information from Service monitoring server to Network monitoring server; (3) Codec information from Network monitoring server to Monitoring point; (1b) monitor QoS information from Monitoring point to (4) QoE assessment block; and (4) QoE assessment block to Monitoring point.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` +graph LR; MS[Media server] -- "(1a) Codec information" --> SMS[Service monitoring server]; SMS -- "(2) Codec information" --> NMS[Network monitoring server]; NMS -- "(3) Codec information" --> MP[Monitoring point]; MP -- "(1b) monitor QoS information" --> QA[QoE assessment]; QA -- "(4) QoE assessment" --> MP; +``` + +Figure I.1: Example for QoE assessment in monitoring points. The diagram shows four entities: Media server, Service monitoring server, Network monitoring server, and Monitoring point. The flow of information is: (1a) Codec information from Media server to Service monitoring server; (2) Codec information from Service monitoring server to Network monitoring server; (3) Codec information from Network monitoring server to Monitoring point; (1b) monitor QoS information from Monitoring point to (4) QoE assessment block; and (4) QoE assessment block to Monitoring point. + +Figure I.1 – Example for QoE assessment in monitoring points + +The network monitoring server sends the codec information of multiple media flows to monitoring points located in the network (3). The monitoring point monitors QoS metrics of the media flow transmitted through it. It correlates codec information and QoS metrics of the same media flow using the flow identifier. QoE performance of each monitored media flow is evaluated at monitoring points based on these two kinds of information. + +In a centralized scenario, the network monitoring server embeds a QoE assessment method. The network monitoring server sends a part of codec information to the monitoring points for QoS metrics calculation. Monitoring points report the QoS metrics of monitored media flow to the network monitoring server. The network monitoring server associates the codec information with QoS metrics using the flow identifier. QoE performance of media flow is evaluated by network monitoring server based on these two kinds of information. + +In both scenarios, monitoring points may calculate frame-related QoS metrics. The codec information includes GOP parameters and timestamp of I frames, which are sent from the service monitoring server to the network monitoring server. The network monitoring server distributes the + +information to monitoring points for frame type analysis of each RTP packet. The monitoring point extracts the timestamp from RTP packets, compares the timestamp of I frames with the RTP timestamp. If there is a match, the corresponding RTP packet is marked as I frame. According to the GOP parameters, the frame type of other RTP packets in the same GOP is estimated. Based on the frame type of each RTP packet, monitoring points will analyse frame-related QoS metrics. + +# Appendix II + +## Encoded bit rate adjustment in the head-end system + +(This appendix does not form an integral part of this Recommendation) + +This appendix provides an example in which the SP adjusts the media encoded bit rate of the VoD service. + +The media resource controller, located in the SP's administrative area, collects media resource information (1a) and the quality experienced by the end user (1b). + +The network resource controller, located in the NP's administrative area, collects the network performance information (1c). + +The media resource controller will decide on a new bit rate to maintain the experienced quality according to the network resource information. The media server is required to adjust the encoded bit rate. Figure II.1 illustrates the interaction between NP and SP and the process followed to adjust the encoded bit rate. + +![Sequence diagram illustrating the interaction for encoded bit rate adjustment between a Media server, MMPAP of SP, Media resource controller, Network resource controller, and MMPAP of NP.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` +sequenceDiagram + participant MS as Media server + participant MSPAP as MMPAP of SP + participant MRC as Media resource controller + participant NRC as Network resource controller + participant NPPAP as MMPAP of NP + + Note right of MRC: (1a) Media information +(1b) QoE perceived by end user + MSPAP->>MRC: (1a) Media information (1b) QoE perceived by end user + Note right of NRC: (1c) Network performance + NRC->>NPPAP: (1c) Network performance + MRC->>NRC: (2) Request network resource information + NRC->>MRC: (3) Reply with network resource information + Note right of MRC: (4) Calculate a new encoded bit rate + MRC->>MSPAP: (5) Request to adjust bit rate + MSPAP->>MS: (5) Request to adjust bit rate +``` + +Sequence diagram illustrating the interaction for encoded bit rate adjustment between a Media server, MMPAP of SP, Media resource controller, Network resource controller, and MMPAP of NP. + +Figure II.1 – Encoded bit rate adjustment + +If the QoE reported by the end user indicates that quality is below a predefined value for the VoD service, the SP is chosen to mitigate the degradation. In order to decide a new encoded bit rate, the media resource controller needs the following information: + +- 1) Available path capacity: the media resource controller requests the current network available capacity of the transport path for the affected VoD service, from network resource controller (2). The network resource controller finds out the transport path of this service and the corresponding available link capacity. The minimum available link capacity is chosen as the available capacity of an end-to-end delivery path. The network resource controller replies with the available path capacity (3). + +- 2) Expected QoE value: the quality a user expects to perceive. The media resource controller obtains the expected QoE value from the end user or from predefined agreement profile. +- 3) Current media encoded bit rate: the media server encodes the media flow at this bit rate. The media resource controller obtains the current encoded bit rate from the media server. + +The media resource controller collects the above three kinds of information and sends it to the media resource management mechanism as inputs for analysis. The encoded bit rate adjustment method includes two aspects. The first one defines how to calculate a new encoded bit rate according to available path capacity, current media encoded bit rate and an expected QoE. A mapping table or formula is used. The second aspect defines the highest or lowest encoded bit rate to the end user. + +The adjusted bit rate should not exceed the limit. The expected bit rate is determined according to the predefined adjustment method (4). + +The media resource controller requests the media server to adjust the encoded bit rate to the expected value (5). + +# Appendix III + +## Encoded layer adjustment + +(This appendix does not form an integral part of this Recommendation) + +### III.1 Introduction + +The performance of the access network is variable. If the quality experienced by the end user is impaired by congestion occurring in the access network, the transmitted encoded layer may be adjusted to comply with network performance. This appendix illustrates two adjustment approaches implemented by NP or SP, respectively. + +### III.2 Network device adjusts the encoded layer + +In scenario 1, program 1 (P1) is a broadcast media flow and encoded in one base layer (P1-B) with two enhancement layers (P1-E1, P1-E2). The network resource requirements of the three encoded layers are different. Program 1 has a multicast IP address which is explicit to the end-point, e.g., STB. Encoded layers are transmitted in three separate multicast groups which are unknown to the end-point. The end-point sends a request to join the multicast group of P1 (e.g., IGMP) when choosing this program. The access node translates the multicast address of P1 into three encoded layers' multicast addresses and requests the resource access. The access decision will be made based on the access network's available capacity, e.g., three encoded layers are accepted. The access node receives and keeps the resource access decision. The media server sends three media flows of program 1. The access node enforces the access decision in two steps, replaces the multicast IP address of accepted encoded layers to the multicast IP address of program 1, and then forwards the accepted encoded layers to the end user. + +The accepted encoded layers may be adjusted according to the access network performance. Figure III.1 illustrates the adjustment of the encoded layers that are transmitted on the access network. + +![Sequence diagram illustrating encode layer adjustment by access node. Lifelines: Media server, MMPAP of SP, Media resource controller, Network resource controller, MMPAP of NP, Access node, STB. The process involves: (1a) QoE perceived by end user from MMPAP of SP to Media resource controller; (2) Notify resource requirement and quality agreement from Media resource controller to Network resource controller; (1b) Collect network performance from Network resource controller to MMPAP of NP; (3) Compare and make decision in Network resource controller; (4) Request to adjust encoded layer from Network resource controller to Access node; (5) Stop forwarding in Access node. The Access node notes that P1 contains the data of accepted layers, with sub-layers P1-B, P1-E1, and P1-E2.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +``` + +sequenceDiagram + participant Media server + participant MMPAP of SP + participant Media resource controller + participant Network resource controller + participant MMPAP of NP + participant Access node + participant STB + + Note right of MMPAP of SP: (1a) QoE perceived by end user + MMPAP of SP->>Media resource controller: (1a) QoE perceived by end user + Note right of Media resource controller: (2) Notify resource requirement and quality agreement + Media resource controller->>Network resource controller: (2) Notify resource requirement and quality agreement + Note right of Network resource controller: (1b) Collect network performance + Network resource controller->>MMPAP of NP: (1b) Collect network performance + Note right of Network resource controller: (3) Compare and make decision + Note right of MMPAP of NP: P1-B, P1-E1, P1-E2 + Note right of Access node: P1 contains the data of accepted layers + Note right of Network resource controller: (4) Request to adjust encoded layer + Network resource controller->>Access node: (4) Request to adjust encoded layer + Note right of Access node: (5) Stop forwarding + Access node->>STB: (5) Stop forwarding + +``` + +Sequence diagram illustrating encode layer adjustment by access node. Lifelines: Media server, MMPAP of SP, Media resource controller, Network resource controller, MMPAP of NP, Access node, STB. The process involves: (1a) QoE perceived by end user from MMPAP of SP to Media resource controller; (2) Notify resource requirement and quality agreement from Media resource controller to Network resource controller; (1b) Collect network performance from Network resource controller to MMPAP of NP; (3) Compare and make decision in Network resource controller; (4) Request to adjust encoded layer from Network resource controller to Access node; (5) Stop forwarding in Access node. The Access node notes that P1 contains the data of accepted layers, with sub-layers P1-B, P1-E1, and P1-E2. + +**Figure III.1 – Encode layer adjustment by access node** + +SP and NP receive the perceived quality and network performance metrics from MMPAP respectively (1a, 1b). If congestion occurs in the access network and the user's quality reports indicate the trend of QoE degradation, the NP is chosen to adjust the resource. SP notifies NP of the required resource of codec layers and the user's agreement about the accepted range of encoded layers (2). The network resource controller compares access network capacity with the required resource (3). Since the QoE will be improved because of less impairment, the decision is to remove some enhancement layers to mitigate the congestion, e.g., the highest layer P1-E2. The adjustment should not exceed the user's agreement of accepted range of the encoded layers. The access node receives the decision (4) and stops forwarding the media flow of P1-E2 (5). When the access network has enough resources, the highest encoded layer is resumed. + +This mechanism requires the network resource controller to be aware of the relation between program and its encoded layers and the resource requirement of each encoded layer. The end user is not aware of the encoded layer adjustment because it joins the multicast group of the program and receives the media flow of the program. + +### III.3 STB adjusts the encoded layer + +In scenario 2, program 1 (P1) is a broadcast media flow and encoded in one base layer (P1-B) with two enhancement layers (P1-E1, P1-E2). STB is aware of the separate multicast IP addresses of the three encoded layers. STB sends three requests to join P1-B, P1-E1 and P1-E2 multicast groups (e.g., IGMP) when choosing P1. Compared with scenario 1, the network node need not keep the correlation between program and the encoded layers. + +STB is requested to join or leave multicast groups of a certain program according to network performance. Figure III.2 illustrates the adjustment procedure. + +![Sequence diagram illustrating the encode layer adjustment process by the STB. The diagram shows interactions between seven entities: Media server, MMPAP of SP, Media resource controller, Network resource controller, MMPAP of NP, Network node, and STB. The process involves QoE perception, path capacity requests, network performance responses, decision making, adjustment requests, and leaving requests for specific encoded layers (P1-B, P1-E1, P1-E2).](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +``` + +sequenceDiagram + participant Media server + participant MMPAP of SP + participant Media resource controller + participant Network resource controller + participant MMPAP of NP + participant Network node + participant STB + + Note right of STB: P1-B + Note right of STB: P1-E1 + Note right of STB: P1-E2 + + MMPAP of SP->>Media resource controller: (1a) QoE perceived by end user + Media resource controller->>Network resource controller: (2) Request available path capacity + Network resource controller-->>Media resource controller: (3) Response + Note left of Network resource controller: (4) Compare and make decision + Media resource controller->>STB: (5) Request to adjust encoded layer + STB->>Network node: (6) Request of leaving encoded layer + +``` + +Sequence diagram illustrating the encode layer adjustment process by the STB. The diagram shows interactions between seven entities: Media server, MMPAP of SP, Media resource controller, Network resource controller, MMPAP of NP, Network node, and STB. The process involves QoE perception, path capacity requests, network performance responses, decision making, adjustment requests, and leaving requests for specific encoded layers (P1-B, P1-E1, P1-E2). + +**Figure III.2 – Encode layer adjustment by STB** + +SP and NP receive the perceived quality and network performance metrics from MMPAP (1a) and (1b) respectively. If network performance results in quality degradation, the media resource controller requests the available path capacity of the end user from the network resource controller (2). The network resource controller replies with the measurement metrics (3). The response information is compared with the requirement of each encoded layer (4). For example, the highest encoded layer (P1-E2) needs to be removed to guarantee quality. The media resource controller sends the adjustment decision to STB (5). STB sends a request to leave the multicast group of P1-E2 (e.g., IGMP) to the network node (6), e.g., an access node. The network node receives the multicast group leaving request, and stops forwarding the media flow of P1-E2 to the end user. + +## Appendix IV + +## Delivery path adjustment + +(This appendix does not form an integral part of this Recommendation) + +The core network implements MPLS technology for DiffServ purposes. The network resource controller is deployed to collect the network measurement information from MMPAP in the core network. The network resource controller constructs a network resource information database of administrative area, uses the database to establish potential paths and calculates the cost of each path in the managed area. The delivery path of media flow is selected from potential paths based on the cost. Network resource is allocated to the media flow. If the current delivery path is congested and results in quality degradation, the network resource controller will select again a new path for the impacted media flow based on the cost. Network resource is reallocated. Figure IV.1 provides a detailed description. + +![Diagram illustrating delivery path adjustments in a sub-network. The diagram shows a Headend system connected to ER1, which is part of a core network containing CR1, CR2, CR3, ER1, ER2, and ER3. An End user is connected to ER2. A Media resource controller and a Network resource controller are shown. The process involves: (1) Network measurement information from the core network to the Network resource controller; (2) Congestion occurs on the path from CR3 to ER2; (3) QoS perceived by end user is communicated to the Network resource controller; (4) Impacted media flow is communicated from the Media resource controller to the Network resource controller; (5) Choose a new delivery path is communicated from the Network resource controller to the core network.](e354b57563dae469c00b412b2abdf765_img.jpg) + +The diagram illustrates the delivery path adjustment process in a sub-network. It features a Headend system connected to edge router ER1, and an End user connected to edge router ER2. The core network contains three core routers: CR1, CR2, and CR3. ER1 is connected to CR1 and CR3. CR1 is connected to CR2. CR2 and CR3 are both connected to ER2. ER3 is connected to CR3. A Media resource controller and a Network resource controller are shown. The process steps are: (1) Network measurement information is sent from the core network to the Network resource controller. (2) Congestion occurs on the path from CR3 to ER2. (3) QoS perceived by the end user is communicated to the Network resource controller. (4) The Media resource controller sends an impacted media flow notification to the Network resource controller. (5) The Network resource controller chooses a new delivery path and communicates this to the core network. + +Diagram illustrating delivery path adjustments in a sub-network. The diagram shows a Headend system connected to ER1, which is part of a core network containing CR1, CR2, CR3, ER1, ER2, and ER3. An End user is connected to ER2. A Media resource controller and a Network resource controller are shown. The process involves: (1) Network measurement information from the core network to the Network resource controller; (2) Congestion occurs on the path from CR3 to ER2; (3) QoS perceived by end user is communicated to the Network resource controller; (4) Impacted media flow is communicated from the Media resource controller to the Network resource controller; (5) Choose a new delivery path is communicated from the Network resource controller to the core network. + +Figure IV.1 – Delivery path adjustments in sub-network + +The network resource controller constructs a network resource information database based on the resource and topology information, which includes the network node, the label switched path (LSP) ID and the LSP cost, in the administrative area. LSP here indicates the logical connection between routers, e.g., edge router 1 (ER1) to core router 1 (CR1), CR1 to CR2, etc. LSP cost is estimated from a physical connection attribute, such as link available capacity between routers. In the preparation process, the network resource controller calculates all potential delivery paths according to the topology information. Each path connects a pair of ERs in the core network. For example, between ER1 and ER2, there are two potential paths (ER1-CR1-CR2-ER2, ER1-CR3-ER2); between ER1 and ER3, there is one potential path (ER1-CR3-ER3); between ER2 and ER3, there is one potential path (ER2-CR3-ER3). The path cost is calculated by aggregating the weighted cost of LSPs along this path. The network resource controller collects the LSP cost from MMPAP and updates the path cost in a real-time manner. + +When the end user requests a media service, the network resource controller finds the pair of ingress and egress nodes according to the identifier of media flow (e.g., the media flow will traverse the network from ER1 to ER2). The possible delivery path of the media flow is filtered (e.g., ER1-CR1-CR2-ER2 and ER1-CR3-ER2) from all potential paths. The path of the least cost, e.g., ER1-CR3-ER2 is selected. If congestion (e.g., CR3-ER2) occurs in the delivery path (2), the user's report indicates the trend of quality degradation (3). The SP notifies the NP of the impacted media flow for which network resource adjustment (4) has to be requested. Network resource controller updates the cost of paths between ER1 and ER2, and selects a new least cost path, e.g., ER1-CR1-CR2-ER2. The rerouting decision is implemented in the related network node, e.g., ER1 (5). The network resource along the new path is allocated to the media flow. + +## Bibliography + +[b-IETF RFC 3357] IETF RFC 3357 (2002), *One-way Loss Pattern Sample Metrics*. + +[b-IETF RFC 5136] IETF RFC 5136 (2008), *Defining Network Capacity*. + + + + + +## **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.161.1-201401-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/G/T-REC-G.161.1-201401-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..619e877a0d4e457848c3da59a8c446e130fb5e0a --- /dev/null +++ b/marked/G/T-REC-G.161.1-201401-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b361cbc8cb45fa1a07fbcf375a62a2bf2f89e64001f96a5ffc55c51b3aeb4e +size 47113 diff --git a/marked/G/T-REC-G.161.1-201401-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/G/T-REC-G.161.1-201401-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a67ce7a9ca2cddba0326e13bc231ccca51d44206 --- /dev/null +++ b/marked/G/T-REC-G.161.1-201401-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1035c072d750cffc0370389f4a5828445168d47a9164e46dbba2de00d219946 +size 33873 diff --git a/marked/G/T-REC-G.161.1-201401-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg b/marked/G/T-REC-G.161.1-201401-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eac276c140811bf9ebc7b29541aa723d70eb9850 --- /dev/null +++ b/marked/G/T-REC-G.161.1-201401-I_PDF-E/7c1f9e78e0f033d391b687f1652f6e47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fa4f6aff1e5dd4948e9e6105307d74a91c336cf2eea3cbe244be9777256edc8 +size 46019 diff --git a/marked/G/T-REC-G.161.1-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/G/T-REC-G.161.1-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8476bbe10504b5b7cbc498691cdacebac15b49bd --- /dev/null +++ b/marked/G/T-REC-G.161.1-201401-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e943537b3f78363929e0739a32623e2db9b79d942b1ebfc4004b2ffe42f9486 +size 44976 diff --git a/marked/G/T-REC-G.225-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.225-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.225-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.225-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.225-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b23dd20d3ec3f688ccc55e038385c65f1a75aafa --- /dev/null +++ b/marked/G/T-REC-G.225-198811-I_PDF-E/raw.md @@ -0,0 +1,95 @@ + + +![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.225** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS** --- + +## **RECOMMENDATIONS RELATING TO THE ACCURACY OF CARRIER FREQUENCIES** + +**ITU-T Recommendation G.225** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +- 1 ITU-T Recommendation G.225 as 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. + +## **RECOMMENDATIONS RELATING TO THE ACCURACY OF CARRIER FREQUENCIES** + +*(amended at Geneva, 1964, and Mar del Plata, 1968)* + +### **1 Accuracy of the virtual carrier frequencies on an international circuit or on a chain of circuits** + +As the channels of any international telephone circuit should be suitable for voice-frequency telegraphy, the accuracy of the virtual carrier frequencies should be such that the difference between an audio-frequency applied to one end of the circuit and the frequency received at the other end should not exceed 2 Hz, even when there are intermediate modulating and demodulating processes. + +To attain this objective, the CCITT recommends that the channel and group carrier frequencies of the various stages should have the following accuracies: + +| | | +|-------------------------------------------------------|-----------------------| +| Virtual channel carrier frequencies in group..... | $\pm 10^{-6}$ | +| Group and supergroup carrier frequencies..... | $\pm 10^{-7}$ | +| Mastergroup and supermastergroup carrier frequencies: | | +| - for the 12-MHz system..... | $\pm 5 \cdot 10^{-8}$ | +| - for the 60-MHz system (above 12 MHz)..... | $\pm 10^{-8}$ | + +Experience shows that, if a proper check is kept on the operation of oscillators designed to these specifications, the difference between the frequency applied at the origin of a telephone channel and the reconstituted frequency at the other end hardly ever exceeds 2 Hz if the channel has the same composition as the 2500-km hypothetical reference circuit for the system concerned. + +Calculations indicate that, if these recommendations are followed, in the 4-wire chain forming part of the hypothetical reference connection defined in Figure 1/G.1031)) there is about 1 % probability that the frequency difference between the beginning and the end of the connection will exceed 3 Hz and less than 0.1% probability that it will exceed 4 Hz. + +*Note 1* - In small stations, i.e. in stations which do not need supergroup carrier frequencies, the accuracy of the group carrier may be $\pm 10^{-6}$ , which is the same as for channel carrier frequencies. + +*Note 2* - The modulating frequencies appropriate to $(n + n)$ systems should have the accuracies recommended in the relevant Recommendations: + +- Recommendation G.311 for 12-channel open-wire systems; +- Recommendation G.361 for 3-channel open-wire systems; +- Recommendations G.326 and G.327 [3] for $(12 + 12)$ cable systems. + +### **2 Measure of alignment of the master oscillators** + +The recommendation in § 1 above cannot be met without some measure of alignment of the master oscillators at the various stations in which modulation occurs. + +1) In fact, the chain considered for these calculations comprised 16 (instead of 12) modulator/demodulator pairs to allow for the possibility that submarine cables with equipments in conformity with Recommendation G.235 might form part of the chain. No allowance was made, however, for the effects of Doppler frequency-shift due to inclusion of a non-stationary satellite; values for this shift are given in CCIR Report 214 [2]. + +Carrier-transmission systems are formed into "partial networks" extending over the whole or a part of a country. Synchronization of the master oscillators of a partial network is ordinarily based on national frequency comparisons; international comparisons may be made if necessary. + +#### 2.1 *National frequency comparisons* + +It is necessary that, within the same partial network of coaxial carrier systems, the master oscillators in stations where frequencies are generated should be "coordinated". This "coordination" can consist of a control of one oscillator with respect to another to give one of the following three conditions: + +- 1) synchronization, i.e. identical frequency and fixed phase relationship; +- 2) isochronization, i.e. identical frequency only; +- 3) differential control to correct differences between the frequencies at intervals. + +Also, automatic devices can be used to give an alarm if the difference in frequency between the checking pilot and a local oscillator exceeds a certain fixed value. + +The CCITT has not recommended any particular method of comparing or controlling the master oscillators at different stations, and "routine frequency comparison" of the master oscillators may be thought sufficient; this comparison being followed if necessary by automatic or manual regulation, the master oscillators in each partial network being compared periodically with a national frequency standard, if possible. + +The routine comparison of the frequencies generated by the master oscillators is made by means of a "frequency check pilot" transmitted to line for this purpose. It is not necessary to compare phases. + +#### 2.2 *International frequency comparisons* + +The case may arise, either of a country that has a national frequency standard with no facilities for distributing it throughout the country (particularly in an area in which a coaxial carrier system is to be set up), or of a country that has no national frequency standard. Recommendation M.540 [4], describes methods by which such countries may obtain a standard frequency by radio, or may have a controlled frequency sent over a telephone circuit. + +## **References** + +- [1] CCITT Recommendation *Hypothetical reference connections*, Vol. III, Rec. G.103, Figure 1/G.103. +- [2] CCITT Report *The effects of doppler frequency-shifts and switching discontinuities in the fixed satellite service*, Vol. IV, Report 214, Dubrovnik, 1986. +- [3] CCITT Recommendation *Valve-type systems offering 12 telephone carrier circuits on a symmetric cable [(12 + 12) systems]*, Orange Book, Vol. III-1, Rec. G.327, ITU, Geneva, 1977. +- [4] CCITT Recommendation *Routine maintenance of carrier and pilot generating equipment*, Vol. IV, Rec. M.540. \ No newline at end of file diff --git a/marked/G/T-REC-G.230-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.230-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd6d37344e1dcb73e876a09f0e28fcc3cc12e0bf --- /dev/null +++ b/marked/G/T-REC-G.230-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:473a66f8b6837745a7f32ac1741f274c5a10ec4eec34cbcf59ae9cab1ea41190 +size 7270 diff --git a/marked/G/T-REC-G.230-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.230-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5ae86db35467017ae9eb499670bfa3246facb180 --- /dev/null +++ b/marked/G/T-REC-G.230-198811-I_PDF-E/raw.md @@ -0,0 +1,172 @@ + + +![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.230** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS** + +## **GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER - TRANSMISSION SYSTEMS** --- + +# **MEASURING METHODS FOR NOISE PRODUCED BY MODULATING EQUIPMENT AND THROUGH-CONNECTION FILTERS** + +**ITU-T Recommendation G.230** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation G.230 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.230 + +# MEASURING METHODS FOR NOISE PRODUCED BY MODULATING EQUIPMENT AND THROUGH-CONNECTION FILTERS + +(Geneva, 1976 and 1980) + +Considering the provisions of Recommendation G.222, § 4 and the assumptions for the calculation of noise of Recommendation G.223, the following methods for measuring the noise produced by modulating equipments are recommended: + +### 1 12-channel translating equipments + +For the measurement of noise produced by 12-channel translating equipments, eleven incoherent noise random signals with a normal (Gaussian) level distribution and with a power distribution according to Recommendation G.227 should be used. As a provisional value, the peak/r.m.s. ratio of each of the noise signals should be about 12 dB. The allocation on the 12-channel inputs of the conventional load of 2140 µW0 (+3.3 dBm0) should be as follows: + +| | | +|-----------------------------------------------------|-----------------| +| 1 channel being measured..... | 0 µW0 | +| 2 adjacent channels at 32 µW0 (-15 dBm0) each ..... | 64 µW0 | +| 9 channels at 230 µW0 (-6.4 dBm0) each ..... | 2070 µW0 | +| | 2134 µW0 | + +## 2 Higher order translating equipments + +### 2.1 Allocation of loading + +For the measurement of noise produced by higher order translating equipments (groups, supergroups, etc. translating equipment), the values for the allocation of the conventional load to the different translating equipments are given in Table 1/G.222. + +The number of incoherent band-limited white noise signals is assumed to be equal to the number of the input ports of the groups, supergroups, etc. translating equipment under measurement. In certain circumstances, however, the number of noise signals may be smaller than the number of group input ports. + +### 2.2 Measuring frequencies + +The measuring frequencies in Table 1/G.230 are recommended. + +TABLE 1/G.230 + +| Basic group to be measured | Frequency range (kHz) | Measuring frequencies (kHz) | | | +|----------------------------|-----------------------|-----------------------------|-------|--------| +| Group | 60- 108 | 70 | | 98 | +| Supergroup | 312- 552 | 331 | | 534 | +| Mastergroup | 812- 2 044 | 1 002 | 1 248 | 1 730 | +| 15 supergroup assembly | 312- 4 028 | 534 | 1 248 | 3 886 | +| Supermastergroup | 8 516- 12 388 | 9 073 | | 11 700 | + +### 2.3 Filter characteristics + +The following filter characteristics are recommended: + +- 2.3.1 bandpass filters (see Table 2/G.230); +- 2.3.2 bandstop filters (see Table 3/G.230). + +*Note* - Measuring frequencies of Table 1/G.230 and filter characteristics of Tables 2/G.230 and 3/G.230 (with the exception of the 70-kHz filter) are the same as in CCIR Recommendations 399 [1] and 482 [2] and CCITT Recommendation G.228 used for line system arrangements. Annex B to Recommendation G.228 deals with the subject of corrections, if any, to be applied to measurements to allow for filter effects. + +TABLE 2/G.230 + +#### Bandpass filters + +| | Capacity
(channels) | Limit of band
occupied
by telephone
channels
(Khz) | Effective cut-off
frequencies of
bandpass filters (kHz) | | Frequency bands (kHz) inside
of which the discrimination
should exceed 75 dB | | +|---------------------------------------------------------------------|------------------------|----------------------------------------------------------------|---------------------------------------------------------------|------------------|-------------------------------------------------------------------------------------------------|-----------------------| +| | | | Highpass | Lowpass | Below the
passband | Above the
passband | +| Basic Group B | 12 | 60- 108 | $61 \pm 2$ | $107 \pm 2$ | 6- 52 | 116- 1 200 | +| Basic supergroup | 60 | 312- 552 | $320 \pm 8$ | $546 \pm 10$ | 6- 288 | 577- 8 500 | +| Basic mastergroup | 300 | 812- 2 044 | $840 \pm 16$ | $2 004 \pm 30$ | 6- 412 | 2 318- 26 000 | +| Basic 15
supergroup
assembly | 900 | 312- 4 028 | $320 \pm 8$ | $4 070 \pm 60$ | 6- 288 | 4 544- 30 000 | +| Basic
supermastergroup

(15 supergroups
assembly No. 3) | 900 | 8 516- 12 388 | } $8 560 \pm 200$ | $12 250 \pm 180$ | 6- 7 686 | 13 085-135 000 | +| | 900 | 8 620- 12 336 | | | | | +| | | | | | Above and below these bands,
the discrimination may decrease
with a slope of 6 dB/octave. | | + +TABLE 3/G.230 + +#### **Bandstop filters** + +| Centre frequence $f_c$
(kHz) | Bandwidth (kHz)
in relation to $f_c$ over
which the discrimination
should be at least | | | Bandwidth (kHz),
in relation to $f_c$ outside of
which the discrimination
should not exceed | | Notes | +|---------------------------------|------------------------------------------------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------------------|-----------|-------| +| | 70 dB | 55 dB | 30dB | 3dB | 0.5dB | | +| 70 | $\pm 1.5$ | $\pm 1.7$ | $\pm 2.0$ | $\pm 5$ | $\pm 10$ | | +| 98 | $\pm 1.5$ | $\pm 1.8$ | $\pm 2.1$ | $\pm 4$ | $\pm 9$ | a) | +| 331 | $\pm 1.5$ | $\pm 2.7$ | $\pm 4.0$ | $\pm 17$ | $\pm 30$ | | +| 534 | $\pm 1.5$ | $\pm 3.5$ | $\pm 7.0$ | $\pm 15$ | $\pm 48$ | b) | +| 1 002 | $\pm 1.5$ | $\pm 4.0$ | $\pm 9.0$ | $\pm 27$ | $\pm 90$ | a) | +| 1 248 | $\pm 1.5$ | $\pm 4.0$ | $\pm 11.0$ | $\pm 35$ | $\pm 110$ | b) | +| 1 730 | $\pm 1.5$ | $\pm 4.0$ | $\pm 14.0$ | $\pm 48$ | $\pm 155$ | a) | +| 3 886 | $\pm 1.5$ | $\pm 4.2$ | $\pm 14.0$ | $\pm 48$ | $\pm 155$ | b) | +| 3 886 | $\pm 1.5$ | $\pm 1.8$ | $\pm 3.5$ | $\pm 12$ | $\pm 100$ | | +| 9 073 | — | $\pm 15.0$ | $\pm 30.0$ | $\pm 110$ | $\pm 350$ | | +| 11 700 | $\pm 1.5$ | $\pm 2.7$ | $\pm 5.8$ | $\pm 18$ | $\pm 250$ | b) | +| | $\pm 1.5$ | $\pm 3.0$ | $\pm 7.0$ | $\pm 20$ | $\pm 300$ | | + +a) CCIR Recommendation 482 [2]. + +b) CCIR Recommendation 399 [1]. + +### 2.4 *Measuring procedures* + +The measuring procedures should comply with Recommendation G.228. Measurements must be carried out with the regulators, if any, not included and with the levels at the nominal value. + +*Note* - Some Administrations have chosen for groups and supergroups not being tested in conformance with Table 1/G.230 higher values of the load, but only for testing equipments with some margin to take account of the application where higher than nominal activity is to be expected. + +As a consequence, in such cases, higher noise limits have to be admitted than those indicated in Recommendation G.222, § 4). + +## **3 Through-connection filters** + +### 3.1 *Allocation of loading* + +For the measurement of noise produced by through-connection filters the values for the allocation of the conventional load according to Table 2/G.223 to the different filters are given in Table 4/G.230. + +TABLE 4/G.230 + +| Filter for the basic | Band of the noise spectrum (kHz) | level of the noise power (dBm0) | +|------------------------|----------------------------------|-----------------------------------| +| Group | 12 to 252 | + 6.1 ( $\hat{=}$ 60 channels) | +| | 60 to 108 | + 3.3 ( $\hat{=}$ 12 channels) | +| Supergroup | 60 to 1 296 | + 9.8 ( $\hat{=}$ 300 channels) | +| | 316 to 552 | + 6.1 ( $\hat{=}$ 60 channels) | +| Mastergroup | 316 to 2 600 | + 12.3 ( $\hat{=}$ 530 channels) | +| Supermastergroup | 4 370 to 17 300 | + 17.6 ( $\hat{=}$ 1800 channels) | +| 15 supergroup assembly | 316 to 8 160 | + 17.6 ( $\hat{=}$ 1800 channels) | + +*Note 1* - Group and supergroup through-connection filters require two measurements. One with "broadband loading" with components outside the pass-band, and an additional one with loading in the passband only. Since in these cases the number of transmitted channels is smaller than 240 (the range where the power level of the conventional load is not proportional to $10 \log_{10} n$ , see § 2.1 of Recommendation G.223) the proportional part of the broadband loading transmitted in the passband gives a loading which is lower than the conventional load for 12 or 60 channels respectively. + +*Note 2* - The choice of the correct load figure for the measurement of the noise produced by the through-supermastergroup filter requires careful consideration bearing in mind that band limiting filters for a bandwidth complying with actual load conditions are not available. + +### 3.2 Measuring frequencies + +See § 2.2. + +### 3.3 Filter characteristics + +Highpass and lowpass filters complying with Table 2/G.228 and [3] can be used to limit the frequency of the noise spectrum. For bandstop filters, see Table 3/G.230. + +### 3.4 Measuring procedures + +The measuring procedure should comply with Recommendation G.228. For through-group and through-supergroup filters, two measurements have to be carried out in the appropriate measuring slots in the passband. + +## References + +- [1] CCIR Recommendation *Measurement of noise using a continuous uniform spectrum signal on frequency-division multiplex telephony radio-relay systems*, Vol. IX, Rec. 399, Dubrovnik, 1986. +- [2] CCIR Recommendation *Measurement of performance by means of a signal of a uniform spectrum for systems using frequency-division multiplex telephony in the fixed satellite service*, Vol. IV, Rec. 482, Dubrovnik, 1986. +- [3] CCIR Recommendation *Measurement of performance by means of a signal of a uniform spectrum for systems using frequency-division multiplex telephony in the fixed satellite service*, Vol. IV, Rec. 482, Table I, Dubrovnik, 1986. \ No newline at end of file diff --git a/marked/G/T-REC-G.241-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.241-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5a9b882f4346594b157f2c5c8ff6e1c16b397e11 --- /dev/null +++ b/marked/G/T-REC-G.241-198811-I_PDF-E/raw.md @@ -0,0 +1,208 @@ + + +![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.241** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER - TRANSMISSION SYSTEMS** --- + +**PILOTS ON GROUPS, SUPERGROUPS, ETC.** + +**ITU-T Recommendation G.241** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation G.241 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.241 + +## PILOTS ON GROUPS, SUPERGROUPS, ETC. + +*(amended at Geneva, 1964; further amended)* + +### 1 Use of pilots + +Experience has shown that, without the use of a group pilot transmitted throughout a group link, adequate stability of the channels of individual group links cannot be guaranteed in spite of the care given to the maintenance of the carrier systems on which they are routed. + +It may be necessary, in the first place, to place an automatic regulator, controlled by the pilot, at the end of some of the group sections forming the group link to compensate for inevitable variations in attenuation on each of the sections. This regulator is not, of course, designed to correct automatically for faults. + +It is desirable for the regulator to have a range of at least $\pm 4$ dB. While no maximum range is specified, note should be taken that too great a range can prove unsatisfactory, e.g. due to noise or the masking of faults. A maximum range of approximately $\pm 7$ dB has been found satisfactory by some Administrations. + +An alarm should be given when the amplitude of the pilot at the input of the regulator departs from its nominal value by more than $\pm 4$ dB. The conditions governing the use of these regulators are given in Recommendation M.160 [1]. + +It is also necessary to provide for measuring the level of the group pilot at the ends of group sections where it is not planned to use a regulator. In these cases, too, an alarm should be given when the level of the pilot departs from its nominal value by more than $\pm 4$ dB. + +Precisely similar considerations apply to the use of supergroup, mastergroup and supermastergroup pilots, and also to the use of basic 15-supergroup assembly pilots. + +*Note* - When a group is through-connected from a cable section (on coaxial or symmetric pairs) to an open-wire line, transmission of the group pilot over the open-wire line, which is an advantage as regards maintenance of the complete group can, to a certain extent, facilitate "tapping" of conversations by means of radio receivers of a particular type in the territory traversed by the open-wire line. However, this risk of "tapping" is less than the similar risk arising from inadequate suppression of the carrier, because the frequency of the group pilot is more remote from the nearby carrier frequency, so that the quality of the overheard conversation would be necessarily degraded. + +### 2 Nominal characteristics of pilots (group, supergroup, etc.) + +When group, supergroup, etc., pilots are considered necessary, they should be permanently transmitted. + +The frequency and the level of these pilots are shown in Table 1/G.241. + +TABLE 1/G.241 + +#### **Frequency and level of pilots** + +| Pilot for | Frequency (kHz) | Absolute power level at a zero relative level point (dBm0) | +|--------------------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------| +| Basic group | 84.080 a)
84.140 b)
104.080 a), b), c) | —20
—25
—20 | +| Basic supergroup | 411.860 a)
411.920 a), c)
547.920 a), b) | —25
—20
—20 | +| Basic mastergroup | 1 552 | —20 | +| Basic supermastergroup | 11 096 | —20 | +| Basic 15-supergroup assembly (No. 1) | 1 552 d) | —20 | + +a) The group pilots 84.080 and 84.140 kHz and the supergroup pilots 411.860 and 411.920 kHz are used over groups and supergroups transmitting telephone channels and, in some cases, wide spectrum signals (data, facsimile, etc.). For each group (or supergroup) the two pilots at 84.080 and 84.140 kHz (or 411.860 and 411.920 kHz) should be transmitted simultaneously. However, only one of these two pilots need be used if there is agreement between the Administrations concerned (including the Administrations of transit countries). + +It is now apparent that transmission of wide spectrum signals (data, facsimile, etc.) may demand use of the pilots 104.080 kHz and 547.920 kHz instead of those previously used. These latter pilots may also be used on groups and supergroups carrying only telephone channels. The choice of pilots to be used is a matter of agreement between the Administrations concerned (including the Administrations of transit countries). + +b) However, the use of the pilots at 104.080 and 547.920 kHz might lead to the following difficulties: + +- 1) The group pilot at 104.080 kHz is incompatible with the line pilots situated at 4 kHz from one end of a group, which are to be found in the following systems: + - open-wire systems using frequency allocation 1 as shown in Figure 1/G.311; + - symmetric-pair systems using variant B as shown in Figure 5/G.322, especially the transistorized system described in Recommendation G.323. +- 2) If the frequency allocation in the supergroup comprises groups A-E in accordance with Figure 2c/G.322 and 3/G.322, a supergroup pilot at 547.92 kHz will appear at frequency 103.92 kHz in group A. This frequency is liable to cause difficulties when group A is used for telephony. To avoid any disturbance, it might be necessary to introduce new routing restrictions. +- 3) Difficulties would arise if these pilots were used on groups having terminal equipment with carrier frequency spacing of 6 kHz in accordance with Recommendation G.234, unless one further channel is abandoned in some groups. + +*Note* - These difficulties have already arisen in some cases with the pilots recommended at present. + +- 4) The choice of these frequencies would make it very difficult to use signalling at the virtual carrier frequency of a telephone channel in conformity with Recommendation Q.21 [2]. However, this point (and the preceding one) can be considered to be of purely national interest. + +c) The supergroup pilot at 411.920 kHz may also be used when the supergroup contains one or more groups transmitting wideband signals. It is impossible to route a group equipped with a pilot at 104.080 kHz in the position of group 3 in a supergroup with a pilot at 411.920 kHz. + +d) This pilot, after modulation of the 15-supergroup assembly to position No. 3 (see procedure 2 of Recommendation G.211, § 1), appears at the frequency of 11 096 kHz; this is identical with the frequency of the basic supermastergroup pilot. + +### 3 Tolerances on the sent level of pilots + +The following values are recommended for the frequency accuracy of the various pilots: + +| | | +|---------------------------------------------------|-------------| +| Pilot frequency 84.080 kHz and 411.920 kHz ..... | $\pm 1$ Hz | +| Pilot frequency 84.140 kHz and 411.860 kHz ..... | $\pm 3$ Hz | +| Pilot frequency 104.080 kHz and 547.920 kHz ..... | $\pm 1$ Hz | +| Pilot frequency 1552 kHz 1) ..... | $\pm 2$ Hz | +| Pilot frequency 11 096 kHz ..... | $\pm 10$ Hz | + +*Note* - These tolerances can be taken as a basis for the specifications of the associated pilot receiving filters and stop filters, allowance also being made for recommendations concerning the accuracy of master oscillators. + +The following recommendations are made concerning the tolerances for the sent pilot level: + +- 1) The design of equipment should be such as to allow the sum of errors in the level of any group, etc., pilot as transmitted, due to finite level adjustment steps, change in number of groups supplied, and lack of adjustment facilities in individual groups, 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. + +### 4 Harmonics of pilots + +4.1 It is recommended that the levels of harmonics of group and supergroup pilots should not exceed the values given in Table 2/G.241. The point where these limits should be met is the distribution frame (or equivalent point) at the output of the next higher stage of modulation, e.g. the supergroup distribution frame in the case of the group pilot. Account should be taken of the change of frequency. + +TABLE 2/G.241 +**Maximum level of harmonics of pilots** + +| Pilot | Nominal frequency of pilot (kHz) | Maximum level of harmonics | | | +|------------|----------------------------------|----------------------------|------------------------|------------------------------| +| | | Second harmonics (dBm0) | Third harmonics (dBm0) | Each higher harmonics (dBm0) | +| Group | 84.080 or 84.140 | —73 | —67 | —75 | +| Group | 104.080 | —67
(see note) | —67 | —75 | +| Supergroup | 411.920 or 411.860 | —75 | —73 | —75 | +| Supergroup | 547.920 | —67 | —67
(see note) | —75 | + +*Note* - If the system includes 3-kHz spaced channels a maximum level of -73 dBm0 is recommended. + +1) This pilot, after modulation of the 15-supergroup assembly to position No. 3 (see procedure 2 of Recommendation G.211, § 1) appears at the frequency 11 096 kHz; this is identical with the frequency of the basic supermastergroup pilot. + +4.2 In the case of the pilot (1552 kHz) for a mastergroup, it is recommended that the level of the second harmonic of the pilot should not exceed - 50 dBm0 and the level of each other higher harmonic should not exceed - 75 dBm0 measured at the output of the next higher stage of modulation. + +4.3 In the case of the pilot (11 096 kHz) for a supermastergroup, it is recommended that the level of any harmonic should not exceed -75 dBm0 measured at the output of the next higher stage of modulation. + +4.4 In the case of the pilot (1552 kHz) for 15-supergroup assemblies, it is recommended that the level of the second harmonic should not exceed -50 dBm0, measured at the output of the supergroup translating equipment. + +Where the 15-supergroup assembly is not combined with other assemblies, there is no particular requirement on the level of the third and higher harmonics. + +Where the 15-supergroup assembly is combined with other assemblies, the level of the third and higher order harmonics should not exceed -75 dBm0, measured at the combined output. + +### 5 Protection of group, supergroup, etc., pilots against interference by noise + +Automatic regulators operated by group, supergroup, etc., reference pilots should be so designed that the interfering effect of noise does not exceed 0.02 dB for any significant period. If, for example, the regulator operates on the mean signal voltage, this corresponds to a long-term interfering signal of -20 dB relative to the pilot level. When the interference is of short duration compared with the time constant of the regulator, high levels of interference may be experienced without causing an error in regulation exceeding 0.02 dB. + +#### 5.1 *Group and supergroup pilots* + +If the pilot pick-off filter has a bandwidth of 50 Hz (25 Hz on each side of the nominal pilot frequency) the ratio between pilot and noise will always be considerably greater than 20 dB in the case of carrier systems over land-lines. This ratio is still respected if the unweighted power of the noise in a telephone channel reaches $10^6$ pW at zero relative level (level of -30 dBm0), which very rarely occurs on radio-relay links conforming to the conditions of Recommendation G.441. + +In the case of very long group or supergroup links on such radio-relay links, the pilot-to-noise ratio will be smaller than 20 dB only for a period of less than some ten-thousandths of any month. In that case the resultant error in regulation will be negligible, as the duration of the very high-level noise will be short compared with the necessarily long time-constant of the regulator. In any case, such high-level bursts are not expected to occur with any significant frequency and the chief factor limiting the interference caused to a pilot by noise is therefore the effective bandwidth of the pick-off filter. + +#### 5.2 *Other pilots* + +Similar consideration applies also to mastergroup, supermastergroup and basic 15-supergroup assembly pilots. However, the bandwidth of the pick-off filter will certainly be greater than 50 Hz and more reliance will have to be placed on the relatively long time-constant of the regulator to minimize the effect of short-duration high-level noise. + +*Note 1* - Recommendations concerning the protection and suppression of pilots at certain points appear in Recommendation G.243. + +*Note 2* - When use is made of procedure 1, described in Recommendation G.211, the spacing between the 11 096 kHz supermastergroup pilot and the audio-frequencies transposed in the adjacent channels is 28 kHz and 60 kHz. + +This same spacing is only 4 kHz with procedure 2, described in Recommendation G.211. + +In view of this, a supermastergroup regulator is not necessarily suitable for the transmission of a 15-supergroup assembly over a supermastergroup link. + +### 6 Protection of group or supergroup pilots against signals transmitted in telephone channels + +This protection is ensured in the channel and group translating equipment, in accordance with Recommendation G.232, § 12 and the Recommendation cited in [4]. + +### 7 Protection of group or supergroup link pilots transmitting wide-spectrum signals + +7.1 To protect the group or supergroup link pilots (used to establish wideband circuits) against other wide-spectrum signals (data, facsimile, etc.), it is recommended that the power spectrum emitted about the pilot frequency be limited in the equipment which transmits these signals. This limitation is so calculated that the group or supergroup regulators installed on the link will not receive interference of more than 0.1 dB, and the values to be specified therefore depend on the characteristics of the regulators (passband of the pilot filters, regulation operating time constant). + +With regard to continuous spectrum signals, the spectrum density in the band $f_0 \pm 25$ Hz must not exceed $-70$ dBm0/Hz. + +The limits to be set for discrete components are fixed by the Figure 1/G.241 which allows for the existing characteristics of regulators activated by pilots at frequencies ( $f_0$ ) of 84.08 or 104.08 kHz in group links and of 411.92 or 547.92 kHz in supergroup links. + +Such a limitation of the transmitted spectrum, obtained by a suitable choice of modulation characteristics, dispenses with the need to insert a bandstop filter to protect the pilot (such a filter would introduce harmful distortion of the group delay). However, if it is not possible to impose such a limitation on the emitted spectrum by this method, or if no guarantee can be secured that this limitation will be respected, the Administrations operating the transmission networks should, in order to protect the group regulators against interference caused by the wideband signals, insert bandstop filters (which would produce the smallest possible distortion to the group delay) at the input of the group or supergroup links under consideration, producing the limitation indicated by Figure 1/G.241. + +*Note* - The general problem of protecting the reference pilots from interference when a group or supergroup is used for the transmission of wide-spectrum signals arises because the protection of these pilots is not always secured by means of a band-clearing filter connected immediately before injection of the pilot. In normal telephone use such protection may depend upon the existence of filters in telephony channel or group translating equipment; however, these may not be in circuit when a wideband transmission path is set up. + +![Figure 1/G.241: A graph showing the maximum permissible level of discrete frequency components of wide-spectrum signals in the vicinity of group and supergroup pilot frequencies. The y-axis is 'Level of frequency component' in dBm0, ranging from -60 to -10. The x-axis is 'Frequency difference from f0 (pilot frequency)' in Hz, ranging from -300 to 300. The graph shows a sharp dip to -60 dBm0 at f0, with levels rising to -10 dBm0 at ±250 Hz and remaining constant at -10 dBm0 from ±250 Hz to ±300 Hz. The curves are symmetric around f0. A label 'CCITT - 41160' is present in the bottom right corner of the graph area.](023b142f90e1253702ac88b18380d3ec_img.jpg) + +Figure 1/G.241: A graph showing the maximum permissible level of discrete frequency components of wide-spectrum signals in the vicinity of group and supergroup pilot frequencies. The y-axis is 'Level of frequency component' in dBm0, ranging from -60 to -10. The x-axis is 'Frequency difference from f0 (pilot frequency)' in Hz, ranging from -300 to 300. The graph shows a sharp dip to -60 dBm0 at f0, with levels rising to -10 dBm0 at ±250 Hz and remaining constant at -10 dBm0 from ±250 Hz to ±300 Hz. The curves are symmetric around f0. A label 'CCITT - 41160' is present in the bottom right corner of the graph area. + +FIGURE 1/G.241 + +Maximum permissible level of discrete frequency components of wide-spectrum. (group and supergroup) signals in the vicinity of group and supergroup pilot frequencies + +The use of a group containing the supergroup pilot should always be avoided (see Recommendation H.14 [5]). This means that no special suppression of the wideband signal has to be provided in the group for the purpose of the supergroup pilot. + +#### 7.2      *"Delayed transfer"* + +It may be imagined that some data-processing devices record the wideband signal in the form in which it reaches them from the network, and then retransmit this recorded signal over the network on a group or supergroup link. On this assumption, the pilot will be recorded at the same time as the signal; it will therefore be retransmitted with it and will then interfere with the pilot injected on the new link. In this case, the recording or retransmitting device should be equipped with a frequency-stop filter providing an attenuation of at least 40 dB at the pilot frequency under consideration, and contributing as little distortion as possible to the group delay. However, if Administrations have inserted, at the input of wideband links, the cut-off filter for protection of the pilot as mentioned in § 7.1 above, the aim sought in the present paragraph will have been reached and the frequency-stop filter will be superfluous. + +#### 7.3      *Multipoint links* + +In the case of multipoint links on tree-shaped networks, the pilot should be blocked at each confluence point on all the confluent links except one, by means of a filter like the one mentioned in § 7.2 above, leaving only one pilot protected against interference from the other pilots. It is also possible to block the pilots on all the confluent links and to transmit a locally produced pilot beyond that point of the link. + +## **References** + +- [1]      CCITT Recommendation *Stability of transmission*, Vol. IV, Rec. M.160. +- [2]      CCITT Recommendation *8-channel terminal equipments*, Orange Book, Vol. III-1, Rec. G.234, ITU, Geneva, 1977. +- [3]      CCITT Recommendation *Systems recommended for out-band signalling*, Vol. VI, Rec. Q.21. +- [4]      CCITT Recommendation *8-channel terminal equipments*, Orange Book, Vol. III-1, Rec. G.234, § f), ITU, Geneva, 1977. +- [5]      CCITT Recommendation *Characteristics of group links for the transmission of wide-spectrum signals*, Vol. III, Rec. H.14. \ No newline at end of file diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/10c82dcc5f2c237961329dd29d65859c_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/10c82dcc5f2c237961329dd29d65859c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a3bf426430ffaf590bba51dafd465c171fe768 --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/10c82dcc5f2c237961329dd29d65859c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78f8c4bd3f9a957d33da033823f82b75899c5391ffe58df65967c7bcede5d23e +size 55409 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da5eed29c3555cd1112aa3e8052b379bc5607de --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea8cbfe9027ff1527f3a936add437b63fd94e8a499e5c74e0f608786b32f2a4 +size 7270 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d16ff38011b5f16d9a5264d9673cd2922aa4f7d7 --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b1fec69d6974ee2ff689b26a07b30236d361925049d35c1dc072aef8b2f5808 +size 72437 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/87658d45f2d2f009cbb9cd1079519cb5_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/87658d45f2d2f009cbb9cd1079519cb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d707dab34c8f4a851702769e54534f14b01a962 --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/87658d45f2d2f009cbb9cd1079519cb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:149855f82da9a7cfeb92817b02c6babeec5aa42765453c70c250320aba30263f +size 76264 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..868dc6d3b6924b93dcb81ce117d9e492eb6a3973 --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36303783a6797296fc76796f82515858142fc4e8beec4681a11f4c4e39b767cd +size 21319 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ed9ae00ffd8c64ce49867361b76d3cf848a25ab --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d840343d847c8a945bd25e04fd817f916e7f9079cff343e376f19b62289e00a +size 64906 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b6d41aa9d1623eed758a35d92bd5b3399b40fed --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6293dccf8844adc1c26a5abc5a3e9327218d1fb06660c921349a487557d7144d +size 79403 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/G/T-REC-G.333-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cb703ac3648d6c838456fc78f52eed2820ef39c --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ffab6f1282743c42d7127c1704024df35513555773f0ee16b4979bea7b3416d +size 45534 diff --git a/marked/G/T-REC-G.333-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.333-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..37e47313db6c68bcf25f46ed408272caa45c4db3 --- /dev/null +++ b/marked/G/T-REC-G.333-198811-I_PDF-E/raw.md @@ -0,0 +1,355 @@ + + +![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.333** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **INTERNATIONAL ANALOGUE CARRIER SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES** --- + +**60 MHz SYSTEMS ON STANDARDIZED +2.6/9.5 mm COAXIAL CABLE PAIRS** + +**ITU-T Recommendation G.333** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +1 ITU-T Recommendation G.333 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. + +## 60 MHz SYSTEMS ON STANDARDIZED 2.6/9.5 mm COAXIAL CABLE PAIRS + +## Introduction + +This Recommendation defines a coaxial cable pair system providing 10 800 telephone channels in the frequency band of approximately 4 to 60 MHz. The system may be used for the transmission of six television signals without any telephone signal or for a mixed transmission of telephone and television signals. The nominal repeater spacing is approximately 1.5 km and can be obtained by dividing the repeater spacing of 12 MHz systems by three. + +## 1 Line frequencies + +The allocation of line frequencies for telephony should be in conformity with one of the two plans given below. + +### 1.1 Plan 1 - Line-frequency allocation and modulation stages for 60-MHz systems (Figure 1/G.333) + +![Figure 1/G.333: Line-frequency allocation recommended for 60 MHz systems on 2.6/9.5 mm coaxial cable pairs using Plan 1. The diagram shows a frequency spectrum from 0 to 70,000 kHz. It identifies the 'Basic supermastergroup' (8516 to 12388 kHz) and 13 'Supermastergroup No.' blocks. Above each block is a 'Carrier frequency' indicated by an arrow and a formula: 16720 (440 x 38), 25520 (440 x 58), 30360 (440 x 69), 35200 (2380 x 15), 39600 (2200 x 18), 44000 (2200 x 20), 48400 (2200 x 22), 55000 (2200 x 25), 59400 (2200 x 27), 63800 (2200 x 29), and 68200 (2200 x 31). The bottom axis is labeled 'Frequency' and 'CCITT - 45641'.](87658d45f2d2f009cbb9cd1079519cb5_img.jpg) + +Figure 1/G.333: Line-frequency allocation recommended for 60 MHz systems on 2.6/9.5 mm coaxial cable pairs using Plan 1. The diagram shows a frequency spectrum from 0 to 70,000 kHz. It identifies the 'Basic supermastergroup' (8516 to 12388 kHz) and 13 'Supermastergroup No.' blocks. Above each block is a 'Carrier frequency' indicated by an arrow and a formula: 16720 (440 x 38), 25520 (440 x 58), 30360 (440 x 69), 35200 (2380 x 15), 39600 (2200 x 18), 44000 (2200 x 20), 48400 (2200 x 22), 55000 (2200 x 25), 59400 (2200 x 27), 63800 (2200 x 29), and 68200 (2200 x 31). The bottom axis is labeled 'Frequency' and 'CCITT - 45641'. + +FIGURE 1/G.333 + +#### Line-frequency allocation recommended for 60 MHz systems on 2.6/9.5 mm coaxial cable pairs using Plan 1 + +In this plan, the basic block for interconnection is the supermastergroup of 8516 to 12 388 kHz recommended by the CCITT in Recommendation G.211. It thus contains the three mastergroups constituting the basic supermastergroup, but the same frequency band could contain a 15-supergroup assembly (see Plan 2). + +All modulation and demodulation between the basic supermastergroup and the line-frequency band is carried out in one modulation step. The carrier frequencies for this modulation are shown in Figure 1/G.333. They are all low multiples of 440 kHz, or multiples of 2200 kHz. These two fundamental frequencies are both closely related to frequencies normally used in the 12-MHz systems. + +The extraction of blocks directly from the line-frequency band can be carried out individually for the four lowest supermastergroups. Higher supermastergroups can only be extracted in the form of an assembly of four supermastergroups. This method is chosen to save frequency bandwidth. + +The two lowest supermastergroups are identical with supermastergroups Nos. 2 and 3 shown in Figure 1/G.332. + +![Diagram showing line-frequency allocation for 60 MHz systems. It displays 15-supergroup assemblies numbered 2 through 13, with their respective frequency bands and carrier frequencies. The x-axis represents frequency in kHz from 0 to 70,000. Assembly 2 is shown as a shaded block from 312 to 4028 kHz. Assemblies 3-13 are shown as triangles with specific frequency ranges. Carrier frequencies are indicated above the assemblies with their respective modulation parameters in parentheses.](e94f3bbb6f7501b9a1344dd0210e5dd8_img.jpg) + +| Assembly No. | Frequency Range (kHz) | Carrier Frequency (kHz) | Modulation Parameters | +|--------------|-----------------------|-------------------------|-----------------------| +| 2 | 312 - 4028 | 8432 | (124 x 68) | +| 3 | 4404 - 8620 | 12648 | (124 x 102) | +| 4 | 8120 - 12336 | 25520 | (440 x 58) | +| 5 | 8620 - 13184 | 30360 | (440 x 69) | +| 6 | 16900 - 21740 | 35200 | (2200 x 16) | +| 7 | 18024 - 22864 | 39600 | (2200 x 18) | +| 8 | 21740 - 26580 | 44000 | (2200 x 20) | +| 9 | 22864 - 27264 | 48400 | (2200 x 22) | +| 10 | 26580 - 31664 | 55000 | (2200 x 25) | +| 11 | 30380 - 35064 | 59400 | (2200 x 27) | +| 12 | 35064 - 39780 | 63800 | (2200 x 29) | +| 13 | 39780 - 42664 | 68200 | (2200 x 31) | + +Diagram showing line-frequency allocation for 60 MHz systems. It displays 15-supergroup assemblies numbered 2 through 13, with their respective frequency bands and carrier frequencies. The x-axis represents frequency in kHz from 0 to 70,000. Assembly 2 is shown as a shaded block from 312 to 4028 kHz. Assemblies 3-13 are shown as triangles with specific frequency ranges. Carrier frequencies are indicated above the assemblies with their respective modulation parameters in parentheses. + +FIGURE 2/G.333 + +#### **Line-frequency allocation recommended for 60 MHz systems on 2.6/9.5 mm coaxial cable pairs using Plan 2** + +According to Plan 2, eleven assemblies of 15 supergroups are translated into the frequency band 8620 to 12 336 kHz which lies within the frequency band of the basic supermastergroup. + +The 15-supergroup assemblies transmitted to line and numbered 3 to 13, are obtained in the same way as the corresponding supermastergroups of Plan 1 above. The assembly of 15 supergroups numbered 2 is obtained by modulation of a 15-supergroup assembly in the band 312-4028 kHz, the carrier frequency being 68 x 124 = 8432 kHz. + +The facilities for extracting blocks directly from the basic-frequency band are identical to those of Plan 1. + +The two lowest 15-supergroup assemblies are identical with the second and third 15-supergroup assemblies in Figure 4/G.332. + +*Note* - It is understood that Plan 1 would be chosen in those countries whose national networks are based upon the use of basic mastergroup and supermastergroups, whereas Plan 2 could be adopted in those countries whose national networks are based on the use of supergroup assemblies only. + +In international connections between countries using the same plan in their national networks, i.e. both using Plan 1 or both using Plan 2, the plan common to these two countries would naturally be used. + +However, in international connections between countries which use different plans in their national networks and in the absence of any special agreement, between the interested Administrations, including Administrations of transit countries, use of Plan 1 is recommended. + +## **2 Pilots and additional measuring frequencies** + +### **2.1 Line-regulating pilots** + +The CCITT recommends that 61 160 kHz should be used for the main line-regulating pilot on all regulated-line sections crossing a frontier. The main line-regulating pilot is used for automatic temperature correction of the cable attenuation. + +In any regulated-line section crossing a frontier, it is recommended that in both directions of transmission the Administration on the transmitting side should permanently transmit so as to provide, for example, for additional regulation, one or more auxiliary line-regulating pilots chosen by the Administration on the receiving side from the following list: + +4287 kHz, 12 435 kHz, 22 372 kHz and 40 920 kHz. + +The power level of these pilots should be regulated, at the output of the transmit amplifier, to a nominal value of -10 dBm0. The harmonics of the 4287, 12 435, 22 372 kHz pilots should each have a level not higher than -70 dBm0. + +The frequency stability recommended for pilots is better than $\pm 1 \times 10^{-5}$ . + +The tolerances for this level are the same as those given in Recommendation G.332, § 2.1. + +### 2.2 *Frequency comparison pilots* + +Since international comparison of frequencies is rarely carried out, the CCITT recommends that Administrations choose one of the following two frequencies: + +- 4200 kHz, which is a multiple of 300 kHz and a neighbouring value of 4400 kHz, +- 8316 kHz ( $27 \times 308$ kHz) which can easily be included in the free intervals of the two frequency arrangements proposed (Figures 1/G.333 and 2/G.333). + +It is recommended that this pilot 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* + +Frequencies that may be used as additional measuring frequencies are given in Table 1/G.333. + +The power level of these additional measuring pilots should be adjusted at the output of the transmit amplifier, to obtain a nominal value of the line pilot of -10 dBm0. The harmonics of additional measuring frequencies below 30 MHz should each have a level at this point not higher than -70 dBm0. + +The frequency stability recommended is better than **Error! Reference source not found.** $1 \times 10^{-5}$ . + +The additional measuring pilots should not be permanently transmitted. They will be transmitted only for as long as is necessary for actual measurement purposes. This does not apply when the frequency is used as a line pilot. + +### 2.4 *Band reserved for monitoring and fault-tracing signals* + +These signals should be below the 4200 kHz frequencies comparison pilot. + +## 3 **Hypothetical reference circuit** + +### 3.1 *General considerations* + +The reference circuit has to reflect what is expected to be the practical application of the system. The spacing of main stations is the same as in earlier systems, e.g. the 12 MHz system. A length of 2500 km, divided into 9 sections each of 280 km with a total of 10 main stations, has therefore been adopted. + +### 3.2 *Modulation* + +With either of the line-frequency allocations recommended in § 1 above, five modulation stages are generally needed to place a particular channel in its position in the line-frequency band. + +On the above basis, the hypothetical reference circuits shown in Figures 3/G.333 and 4/G.333 are recommended by the CCITT. + +### 3.3 *Direct through-connection at line frequencies* + +It was agreed that direct through-connection was envisaged not for points intermediate between the main stations as defined above, but rather at these stations themselves so that demodulation would be avoided. While this would be an advantage from the point of view of the amount of modulation equipment, it would involve more severe requirements on line equipment. + +TABLE 1/G.333 + +| Frequency (see Note 1)
kHz
(1) | Frequency (see Note 2)
kHz
(2) | +|--------------------------------------|---------------------------------------------| +| | 4 200 (see Note 3)
or 4 287 (see Note 4) | +| 8 472 | 8 316 (see Note 3) | +| 12 678 | | +| 17 488 | 22 302 (see Note 5) | +| | 22 372 (see Note 4) | +| 26 922 | | +| 31 322 | | +| 35 722 | | +| 40 122 (see Note 6) | 40 920 (see Note 4) | +| 42 322 | | +| 46 722 | | +| 51 122 | | +| 55 522 | 59 922 | + +*Note 1* - (Applies to all frequencies in column 1.) Use of these frequencies will ensure that interference is not caused to the following fine-regulated section. They can therefore be transmitted at any time. + +*Note 2* - (Applies to all frequencies in column 2.) These frequencies will be provided when the Administration at the receiving end so requests. They should not be sent without the agreement of the Administration at the receiving end. + +*Note 3* - These frequencies may also be used as frequency-comparison pilots. + +*Note 4* - In accordance with Recommendation M.500 [1], Administrations choosing to use these frequencies must ensure that interference is not caused to a following line-regulated section which may be using these frequencies as line pilots. + +*Note 5* - If the frequency 22 372 kHz is used as an auxiliary line regulating pilot it should be ensured that no disturbance is caused to this pilot. + +*Note 6* - It may be unnecessary to use this frequency if an adjacent auxiliary line-pilot is used for regulation. + +![Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 1).](fc46871d72c65d3381d9201646d23439_img.jpg) + +The diagram shows a sequence of stations: Station 1, Station 2, Station 3, Station 4, and Station 10. Each station is represented by a set of rectangular blocks. Station 1 has 5 blocks, Station 2 has 2, Station 3 has 4, Station 4 has 8, and Station 10 has 5. The blocks are connected by lines. Some blocks have diagonal hatching. A dashed line connects Station 4 and Station 10. The text 'CCITT - 45660' is at the bottom right. + +Legend: + +- Channel translation to form a basic group. +- ▨ Group translation to form a basic supergroup. +- ▤ Supergroup translation to form a basic mastergroup. +- ▦ Mastergroup translation to form a basic supermastergroup. +- ▧ Supermastergroup translation to the line-frequency allocation (except for supermastergroup 3). + +Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 1). + +*Note* – Stations 5 and 8 are identical with Station 2 – Stations 6 and 9 are identical with Station 3 – Station 7 is identical with Station 4. + +FIGURE 3/G.333 + +**Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 1)** + +![Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 2).](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram shows a sequence of stations: Station 1, Station 2, Station 3, Station 4, and Station 10. Each station is represented by a set of rectangular blocks. Station 1 has 5 blocks, Station 2 has 2, Station 3 has 4, Station 4 has 8, and Station 10 has 5. The blocks are connected by lines. Some blocks have diagonal hatching, and some have a dot in the center. A dashed line connects Station 4 and Station 10. The text 'CCITT - 45661' is at the bottom right. + +Legend: + +- Channel translation to form a basic group. +- ▨ Group translation to form a basic supergroup. +- ▤ Supergroup translation to form a basic 15-supergroup assembly in the band 312-4028 kHz. +- ⊙ Modulation of the basic 15-supergroup assembly to place it within the frequency band of the basic supermastergroup or, in the case of assembly No. 2, within the line-frequency band. +- ▧ Modulation of the 15-supergroup assembly situated within the frequency band of the basic supermastergroup to obtain the line-frequency allocation. + +Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 2). + +*Note* – Stations 5 and 8 are identical with Station 2 – Stations 6 and 9 are identical with Station 3 – Station 7 is identical with Station 4. + +FIGURE 4/G.333 + +**Diagram of a hypothetical reference circuit for 60 MHz system on 2.6/9.5 mm coaxial cable pairs (Plan 2)** + +It has, however, been found possible to use restricted through-connection at main repeater stations with equipment designed to meet the normal noise objectives defined in connection with a hypothetical reference circuit for the 60-MHz system on coaxial pairs (see Figure 3/G.333) without incurring a noise penalty. + +The necessary restrictions are as follows: + +- 1) The frequency band containing supermastergroups 6 to 9 inclusive may be directly through-connected over a total length which must not exceed 830 km, but the adjacent frequency bands in the sections concerned must be homogeneous sections which are not abnormally long. +- 2) It is in principle also possible to use direct through-connection for the frequency band containing supermastergroups 2-5 inclusive provided that the adjacent frequency bands containing supermastergroups 6-9 and 10-13 are transmitted on normal length homogeneous sections. In practice it may be necessary to restrict the through-connection to supermastergroups which have a sufficiently low impedance mismatch effect (§ 7) to permit the extension without excessive accumulation of attenuation roll effect. + +## 4 Circuit noise + +It is recommended that the system be designed on the basis of Recommendation G.222, i.e. in such a way as to obtain a mean psophometric power of about 3 pW per km of line, on the worst telephone channel having the same composition as the 2500-km hypothetical reference circuit. + +## 5 Matching of repeater impedances and line impedance + +A value of 65 dB is recommended for the magnitude $N$ defined in Recommendation G.332, § 5. + +## 6 Interconnection + +*Levels in a main station* (see Recommendation G.213) + +When one part of the frequency band is transmitted without demodulation, the same value of -33 dBr is recommended at the output of the direct through-connection filter. + +The level at the repeater output on the highest channel should be $-19 \pm 1$ dBr. + +*Note* - Values for pre-emphasis ranging from 7 to 10 dB are commonly used. + +## 7 Power-feeding and alarm systems + +### 7.1 *Power feeding across a frontier* + +In the absence of a special agreement between the Administrations concerned with a power-feeding section crossing a frontier, it is recommended that each Administration power-feed only those repeater stations in its own country. Many Administrations used looped power-feeding on the two sides of a power-feeding station, half of each of the sections between this station and the adjacent power stations being so fed; they can close the loop at their frontier stations. Agreements will be necessary if, for example, the frontier is very far from the mid-point between the two nearest feeding stations, or if the Administrations concerned use looped power-feeding on the entire section between two feeding stations. + +If repeater stations in a country are fed from another country, special precautions will be required to protect the staff working on the cables. + +### 7.2 *Remote power-feeding systems* + +Although CCITT does not recommend the use of a specific remote power-feeding system for the 60-MHz coaxial line system, in practice only the constant current d.c. feeding via the inner conductors of the two coaxial pairs of a system is used. + +The 60-MHz coaxial 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 [2] 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 [3]. + +### 7.3 *Supervision and alarms in a frontier section* + +This should be governed by agreement between the Administrations concerned. In particular, it is necessary at the points of interconnection between two systems that if frequencies are used for monitoring or for locating faults, they be attenuated to a level of -50 dBm0 on the receiving sides to prevent any disturbance to similar frequencies used in the system farther down the line. + +*Note* - Frequencies sent only over a system already withdrawn from service because of a fault may be selected by each Administration on the national level. + +## 8 **Use of 60-MHz systems for television transmission** + +### 8.1 *General remarks* + +In § 8 all additional requirements are summarized which are recommended in the case of television transmission on the 60-MHz system. The characteristics of the television signal in the first intermediate frequency allocation (transmit side conditions) are dealt with in Recommendation J.77 [4]. + +### 8.2 *Circuit noise* + +If the 60-MHz system is used for television transmission on the basis of a hypothetical reference circuit (HRC) of a length of 2500 km, the mean value of the thermal noise of the line should not exceed 1 pW0p/km. Experience has shown that a mean value of 1.5 pW0p/km total noise of the line is sufficient when measured according to normal telephone conditions. In making through-connections between homogeneous sections of an HRC, different transmission bands may be used. As different transmission bands give different distributions of basic noise and intermodulation noise, it seems justified to assign noise limits which are average values within the whole transmission band, i.e., among the five measuring channels recommended in Recommendation G.228. + +### 8.3 *Matching of repeater impedances and line impedance* + +For television programme transmission a value of at least 72 dB for the magnitude $N$ , defined in Recommendation G.332, § 5, has been agreed to in the band occupied by television signals. + +### 8.4 *Number, nature and position of line television channels* + +Television signals may be transmitted without any other wanted signals or simultaneously with telephone channels. In the first case, there are six television channels. In the case of mixed transmission, the attention of Administrations is drawn to the fact that, if there are more than two television channels, harmful interference may occur between the two types of signal, especially interference to telephony from television. This clause is therefore limited to cases where the number of channels is less than or equal to two. + +Whether or not the 60 MHz system is allocated wholly or partially to television, television channels are capable of transmitting the signals of all television systems defined by the CCIR having a video bandwidth not exceeding 6 MHz. + +When a 60 MHz system is used entirely for television, it can provide six television channels, arranged in three pairs each of which extends over the bandwidth of four supermastergroups. The line-frequency allocation is shown in Figure 5/G.333. + +When transmission is mixed, a distinction should be made according to whether the number of television channels is two or one. + +If there are two, the use of channels 3 and 4 is recommended. + +In the case of a single television channel, there are two possibilities: + +- first alternative: channel 3 or channel 4, the choice being immaterial; +- second alternative: channel 1. + +The first alternative has the advantage of low group delay distortion and is suitable for long links. The second allows the use of simple modulation equipment, if modulation method No. 2 is applied (see Note 1 below). On the other hand, it has the disadvantage of a higher group delay distortion, requiring the use of correctors whose complexity increases with the length of exceeds a certain limit. + +*Note 1* - Two recommended modulating methods are shown in Annex A. + +*Note 2* - A television channel-pair pilot can be provided at the mean of the carrier frequencies of each television channel pair, i.e. 12 760 kHz ( $4 \times 3190$ kHz), 31900 kHz ( $10 \times 3190$ kHz) and 51 040 kHz ( $16 \times 3190$ kHz). It is recommended that these pilots be transmitted at a power level of -10 dBm0. The harmonics of the pilot 12 760 kHz should have a level of not higher than -70 dBm0; the level of the harmonics of the other pilots should not exceed -50 dBm0. + +![Diagram showing the line-frequency allocation of six television channels on the 60 MHz system. The diagram illustrates the frequency bands for channels 1 through 6, with specific frequency markers in kHz. Channel 1 starts at 5287 kHz and ends at 11287 kHz. Channel 2 starts at 11287 kHz and ends at 20233 kHz. Channel 3 starts at 24427 kHz and ends at 30427 kHz. Channel 4 starts at 30427 kHz and ends at 39373 kHz. Channel 5 starts at 43567 kHz and ends at 49567 kHz. Channel 6 starts at 49567 kHz and ends at 58513 kHz. The diagram also includes a reference 'CCITT - 45670'.](8ee3b76dd49f31624d287885bc2c81ee_img.jpg) + +Diagram showing the line-frequency allocation of six television channels on the 60 MHz system. The diagram illustrates the frequency bands for channels 1 through 6, with specific frequency markers in kHz. Channel 1 starts at 5287 kHz and ends at 11287 kHz. Channel 2 starts at 11287 kHz and ends at 20233 kHz. Channel 3 starts at 24427 kHz and ends at 30427 kHz. Channel 4 starts at 30427 kHz and ends at 39373 kHz. Channel 5 starts at 43567 kHz and ends at 49567 kHz. Channel 6 starts at 49567 kHz and ends at 58513 kHz. The diagram also includes a reference 'CCITT - 45670'. + +FIGURE 5/G.333 + +**Line-frequency allocation of six television channels on the 60 MHz system** + +### 8.5 *Pilots and additional measuring frequencies* + +Those pilots and additional measuring frequencies (mentioned in § 2), falling in gaps between TV channels, can be used. + +## ANNEX A + +(to Recommendation G.333) + +### **Modulation methods for television transmission on the 60-MHz system** + +Two recommended modulating methods are shown in Figure A-1/G.333 and Figure A-2/G.333 respectively. The modulation methods are compatible with those of the 18-MHz system (see Annex A to Recommendation G.334). + +![Diagram of modulation method 1 for the 60 MHz system. It shows six channels (1-6) with their respective frequency bands and sub-carrier frequencies. Channel 1: 5 287 - 11 287 kHz; Channel 2: 11 287 - 20 233 kHz; Channel 3: 24 427 - 30 427 kHz; Channel 4: 30 427 - 39 373 kHz; Channel 5: 43 567 - 49 567 kHz; Channel 6: 49 567 - 58 513 kHz. Above the channels, a series of trapezoidal shapes represent the modulation envelope, with vertical dashed lines indicating sub-carrier frequencies: 8 097, 11 043, 19 140 (6 x 3190), 41 470 (13 x 3190), 44 660 (14 x 3190), and 82 940 (26 x 3190). The label '60 MHz system' is on the left, and 'CCITT - 45 681' is on the right.](d48475a25698b1c0592e4cfe07138f2a_img.jpg) + +Diagram of modulation method 1 for the 60 MHz system. It shows six channels (1-6) with their respective frequency bands and sub-carrier frequencies. Channel 1: 5 287 - 11 287 kHz; Channel 2: 11 287 - 20 233 kHz; Channel 3: 24 427 - 30 427 kHz; Channel 4: 30 427 - 39 373 kHz; Channel 5: 43 567 - 49 567 kHz; Channel 6: 49 567 - 58 513 kHz. Above the channels, a series of trapezoidal shapes represent the modulation envelope, with vertical dashed lines indicating sub-carrier frequencies: 8 097, 11 043, 19 140 (6 x 3190), 41 470 (13 x 3190), 44 660 (14 x 3190), and 82 940 (26 x 3190). The label '60 MHz system' is on the left, and 'CCITT - 45 681' is on the right. + +FIGURE A-1 /G.333 +**Modulation method for television transmission on the 60 MHz system + Modulation method 1** + +![Diagram of modulation method 2 for the 60 MHz system. It shows six channels (1-6) with their respective frequency bands and sub-carrier frequencies. Channel 1: 5 287 - 11 287 kHz; Channel 2: 11 287 - 20 233 kHz; Channel 3: 24 427 - 30 427 kHz; Channel 4: 30 427 - 39 373 kHz; Channel 5: 43 567 - 49 567 kHz; Channel 6: 49 567 - 58 513 kHz. Above the channels, a series of trapezoidal shapes represent the modulation envelope, with vertical dashed lines indicating sub-carrier frequencies: 6 000, 25 520 (8 x 3190), 44 660 (14 x 3190), and 63 800 (20 x 3190). The label '60 MHz system' is on the left, and 'CCITT - 45 691' is on the right.](10c82dcc5f2c237961329dd29d65859c_img.jpg) + +Diagram of modulation method 2 for the 60 MHz system. It shows six channels (1-6) with their respective frequency bands and sub-carrier frequencies. Channel 1: 5 287 - 11 287 kHz; Channel 2: 11 287 - 20 233 kHz; Channel 3: 24 427 - 30 427 kHz; Channel 4: 30 427 - 39 373 kHz; Channel 5: 43 567 - 49 567 kHz; Channel 6: 49 567 - 58 513 kHz. Above the channels, a series of trapezoidal shapes represent the modulation envelope, with vertical dashed lines indicating sub-carrier frequencies: 6 000, 25 520 (8 x 3190), 44 660 (14 x 3190), and 63 800 (20 x 3190). The label '60 MHz system' is on the left, and 'CCITT - 45 691' is on the right. + +FIGURE A-2/G.333 +**Modulation method for television transmission on the 60 MHz system + Modulation method 2** + +## References + +- [1] CCITT Recommendation *Routine maintenance measurements to be made on regulated line sections*, Vol. IV, Rec. M.500. +- [2] CCITT manual *Directives concerning the protection of telecommunication lines against harmful effects from electricity lines*, ITU, Geneva, 1963, 1965, 1974 and 1978. +- [3] 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. +- [4] CCITT Recommendation *Characteristics of the television signals transmitted over 18-MHz and 60-MHz systems*, Vol. III, Rec. J.77. \ No newline at end of file diff --git a/marked/G/T-REC-G.345-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.345-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.345-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.631-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.631-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.631-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.631-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.631-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..51ee834317220f1e41c9f6e052b87ab672029e28 --- /dev/null +++ b/marked/G/T-REC-G.631-198811-I_PDF-E/raw.md @@ -0,0 +1,69 @@ + + +![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.631** + +# **TRANSMISSION MEDIA CHARACTERISTICS** --- + +**TYPES OF SUBMARINE CABLE +TO BE USED FOR SYSTEMS +WITH LINE FREQUENCIES OF LESS +THAN ABOUT 45 MHz** + +**ITU-T Recommendation G.631** + +(Extract from the *Blue Book*) + +--- + +## NOTES + +- 1 ITU-T Recommendation G.631 was published in Fascicle III.3 of the *Blue Book*. This file is an extract from the *Blue Book*. While the presentation and layout of the text might be slightly different from the *Blue Book* version, the contents of the file are identical to the *Blue Book* version and copyright conditions remain unchanged (see below). +- 2 In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +## Recommendation G.631 + +## TYPES OF SUBMARINE CABLE TO BE USED FOR SYSTEMS WITH LINE FREQUENCIES OF LESS THAN ABOUT 45 MHz + +(Geneva, 1976) + +The CCITT, + +*recognizing* + +that the special complications of cable repair in the case of submarine cable systems laid in deep water (i.e. at depths where there is no need to use armoured cables) justify measures which would reduce the number of cable types with which repair ships have to deal; + +*appreciating* + +at the same time that system designers require flexibility in the choice of cables in order to optimize the overall cost per unit length of individual systems; + +*recognizing* + +that the most significant cable characteristics in determining whether any two cables may be joined together are: + +- the inner diameter of the outer conductor, +- the characteristic impedance of the cable, + +*recommends* + +that for submarine systems handling line frequencies up to 45 MHz the cable used in the deep water sections of such systems should conform with the limits set out in Table 1/G.631. + +TABLE 1/G.631 + +| | | | | +|-----------------------------------|--------------|--------------------------|----------------------------------------| +| Inner diameter of outer conductor | 25.0-25.5 mm | 37.0-38.5 mm | 43.2 mm | +| Characteristic impedance | 43-46 Ω | a) 53-54 Ω
b) 60-62 Ω | a) 49-50 Ω
b) 53-54 Ω
c) 60-62 Ω | \ No newline at end of file diff --git a/marked/G/T-REC-G.694.1-202010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.694.1-202010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/G/T-REC-G.694.1-202010-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/G/T-REC-G.694.1-202010-I_PDF-E/2236272d3b3db6e6363337f5a8db72f6_img.jpg b/marked/G/T-REC-G.694.1-202010-I_PDF-E/2236272d3b3db6e6363337f5a8db72f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6bdd6c0d1a127d2d97036cddd9dfc3f47896e61 --- /dev/null +++ b/marked/G/T-REC-G.694.1-202010-I_PDF-E/2236272d3b3db6e6363337f5a8db72f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10319bb2d72cbe7edafbe106f477025997fbd33a87ede49e3adfede8767035c0 +size 30717 diff --git a/marked/G/T-REC-G.694.1-202010-I_PDF-E/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg b/marked/G/T-REC-G.694.1-202010-I_PDF-E/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a31ac118f56528a8566c189de6a38a7a242c298 --- /dev/null +++ b/marked/G/T-REC-G.694.1-202010-I_PDF-E/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a62288c6a5ed53e6ed66f2d83d1ac64c4bd862d146e364a048ae26853b19da88 +size 36943 diff --git a/marked/G/T-REC-G.694.1-202010-I_PDF-E/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg b/marked/G/T-REC-G.694.1-202010-I_PDF-E/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d1aae0487719c43b52d88a3321dbe4c292fd18b --- /dev/null +++ b/marked/G/T-REC-G.694.1-202010-I_PDF-E/dd330f8b8f6c16eae20c3a676b4eb804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d900c59725bca8a0f7854eab20fb55939d97599450b9ba2d056a1ff55e5dcf1 +size 31871 diff --git a/marked/G/T-REC-G.694.1-202010-I_PDF-E/raw.md b/marked/G/T-REC-G.694.1-202010-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..56f4a925f88249933eac326bc3e4b14c76e82fb0 --- /dev/null +++ b/marked/G/T-REC-G.694.1-202010-I_PDF-E/raw.md @@ -0,0 +1,411 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.694.1** + +(10/2020) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Transmission media and optical systems characteristics – +Characteristics of optical systems + +--- + +**Spectral grids for WDM applications: DWDM +frequency grid** + +Recommendation ITU-T G.694.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 | +| 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.694.1 + +## Spectral grids for WDM applications: DWDM frequency grid + +## Summary + +Recommendation ITU-T G.694.1 provides a frequency grid for dense wavelength division multiplexing (DWDM) applications. + +The frequency grid, anchored to 193.1 THz, supports a variety of channel spacings ranging from 12.5 GHz to 100 GHz and wider. + +Edition 3.0 of this Recommendation also includes a flexible DWDM grid and definitions for "frequency slot" and "slot width" that can be applied also in fixed grid applications. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.694.1 | 2002-06-13 | 15 | 11.1002/1000/6051 | +| 2.0 | ITU-T G.694.1 | 2012-02-13 | 15 | 11.1002/1000/11482 | +| 3.0 | ITU-T G.694.1 | 2020-10-29 | 15 | 11.1002/1000/14498 | + +## Keywords + +DWDM, flexible grid, frequency slot, slot width. + +--- + +\* 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 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 ..... | 1 | +| 3.1 Terms defined elsewhere ..... | 1 | +| 3.2 Terms defined in this Recommendation..... | 1 | +| 4 Abbreviations and acronyms ..... | 1 | +| 5 Conventions ..... | 1 | +| 6 Dense wavelength division multiplexing and its applications..... | 2 | +| 7 Fixed grid nominal central frequencies for dense WDM systems..... | 2 | +| 8 Flexible DWDM grid definition ..... | 5 | +| Appendix I – Use of the flexible grid ..... | 6 | +| I.1 Flexible grid examples ..... | 6 | +| I.2 Flexible grid compliance ..... | 7 | + + + +## Recommendation ITU-T G.694.1 + +## Spectral grids for WDM applications: DWDM frequency grid + +## 1 Scope + +The purpose of this Recommendation is to provide the definition of a frequency grid to support dense wavelength division multiplexing (DWDM) 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.671] Recommendation ITU-T G.671 (2019), *Transmission characteristics of optical components and subsystems*. + +## 3 Definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following terms as described in [ITU-T G.671] in relation to CWDM devices and DWDM devices: + +- Coarse wavelength division multiplexing (CWDM). +- Dense wavelength division multiplexing (DWDM). + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 frequency grid:** A reference set of frequencies used to denote allowed nominal central frequencies that may be used for defining applications. + +**3.2.2 frequency slot:** A contiguous frequency range characterized by its nominal central frequency and slot width. The frequency range allocated to a frequency slot is unavailable to other frequency slots. + +**3.2.3 slot width:** The full width of the contiguous frequency range allocated to a frequency slot. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +CWDM Coarse Wavelength Division Multiplexing + +DWDM Dense Wavelength Division Multiplexing + +WDM Wavelength Division Multiplexing + +## 5 Conventions + +None. + +## 6 Dense wavelength division multiplexing and its applications + +As defined in [ITU-T G.671], dense wavelength division multiplexing (DWDM), a wavelength division multiplexing (WDM) technology, is characterized by narrower channel spacing than coarse WDM (CWDM). In general, the transmitters employed in DWDM applications require a control mechanism to enable them to meet the application's frequency stability requirements, in contrast to CWDM transmitters, which are generally uncontrolled in this respect. + +The frequency grid defined by this Recommendation supports a variety of fixed channel spacings ranging from 12.5 GHz to 100 GHz and wider (integer multiples of 100 GHz) as well as a flexible grid. Uneven channel spacings using the fixed grids are also allowed. + +The current steps in channel spacing for the fixed grids have historically evolved by sub-dividing the initial 100 GHz grid by successive factors of two. + +## 7 Fixed grid nominal central frequencies for dense WDM systems + +For channel spacings of 12.5 GHz on a fibre, the allowed channel frequencies (in THz) are defined by: + +$$193.1 + n \times 0.0125 \text{ where } n \text{ is a positive or negative integer including } 0$$ + +For channel spacings of 25 GHz on a fibre, the allowed channel frequencies (in THz) are defined by: + +$$193.1 + n \times 0.025 \text{ where } n \text{ is a positive or negative integer including } 0$$ + +For channel spacings of 50 GHz on a fibre, the allowed channel frequencies (in THz) are defined by: + +$$193.1 + n \times 0.05 \text{ where } n \text{ is a positive or negative integer including } 0$$ + +For channel spacings of 100 GHz or more on a fibre, the allowed channel frequencies (in THz) are defined by: + +$$193.1 + n \times 0.1 \text{ where } n \text{ is a positive or negative integer including } 0$$ + +Table 1 illustrates some nominal central frequencies within the C and L bands based on the 12.5 GHz minimum channel spacing anchored to the 193.1 THz reference. Table 1 also illustrates the 25, 50 and 100 GHz grid frequencies within the same region. The endpoints shown are illustrative, not normative. + +Note that the value of "c" (speed of light in vacuum) that should be used for converting between frequency and wavelength is $2.99792458 \times 10^8$ m/s. + +**Table 1 – Example nominal central frequencies of the DWDM grid** + +| Nominal central frequencies (THz) for spacings of: | | | | Approximate nominal central wavelengths (nm) (Note) | +|----------------------------------------------------|---------|--------|-------------------|-----------------------------------------------------| +| 12.5 GHz | 25 GHz | 50 GHz | 100 GHz and above | | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| 195.9375 | – | – | – | 1530.0413 | +| 195.9250 | 195.925 | – | – | 1530.1389 | +| 195.9125 | – | – | – | 1530.2365 | +| 195.9000 | 195.900 | 195.90 | 195.9 | 1530.3341 | +| 195.8875 | – | – | – | 1530.4318 | + +**Table 1 – Example nominal central frequencies of the DWDM grid** + +| Nominal central frequencies (THz) for spacings of: | | | | Approximate nominal
central wavelengths (nm)
(Note) | +|----------------------------------------------------|---------|--------|----------------------|-----------------------------------------------------------| +| 12.5 GHz | 25 GHz | 50 GHz | 100 GHz
and above | | +| 195.8750 | 195.875 | – | – | 1530.5295 | +| 195.8625 | – | – | – | 1530.6271 | +| 195.8500 | 195.850 | 195.85 | – | 1530.7248 | +| 195.8375 | – | – | – | 1530.8225 | +| 195.8250 | 195.825 | – | – | 1530.9203 | +| 195.8125 | – | – | – | 1531.0180 | +| 195.8000 | 195.800 | 195.80 | 195.8 | 1531.1157 | +| 195.7875 | – | – | – | 1531.2135 | +| 195.7750 | 195.775 | – | – | 1531.3112 | +| 195.7625 | – | – | – | 1531.4090 | +| 195.7500 | 195.750 | 195.75 | – | 1531.5068 | +| 195.7375 | – | – | – | 1531.6046 | +| 195.7250 | 195.725 | – | – | 1531.7024 | +| 195.7125 | – | – | – | 1531.8003 | +| 195.7000 | 195.700 | 195.70 | 195.7 | 1531.8981 | +| 195.6875 | – | – | – | 1531.9960 | +| 195.6750 | 195.675 | – | – | 1532.0938 | +| 195.6625 | – | – | – | 1532.1917 | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| 193.2375 | – | – | – | 1551.4197 | +| 193.2250 | 193.225 | – | – | 1551.5200 | +| 193.2125 | – | – | – | 1551.6204 | +| 193.2000 | 193.200 | 193.20 | 193.2 | 1551.7208 | +| 193.1875 | – | – | – | 1551.8212 | +| 193.1750 | 193.175 | – | – | 1551.9216 | +| 193.1625 | – | – | – | 1552.0220 | +| 193.1500 | 193.150 | 193.15 | – | 1552.1225 | +| 193.1375 | – | – | – | 1552.2229 | +| 193.1250 | 193.125 | – | – | 1552.3234 | +| 193.1125 | – | – | – | 1552.4239 | +| 193.1000 | 193.100 | 193.10 | 193.1 | 1552.5244 | + +**Table 1 – Example nominal central frequencies of the DWDM grid** + +| Nominal central frequencies (THz) for spacings of: | | | | Approximate nominal
central wavelengths (nm)
(Note) | +|----------------------------------------------------|---------|--------|----------------------|-----------------------------------------------------------| +| 12.5 GHz | 25 GHz | 50 GHz | 100 GHz
and above | | +| 193.0875 | – | – | – | 1552.6249 | +| 193.0750 | 193.075 | – | – | 1552.7254 | +| 193.0625 | – | – | – | 1552.8259 | +| 193.0500 | 193.050 | 193.05 | – | 1552.9265 | +| 193.0375 | – | – | – | 1553.0270 | +| 193.0250 | 193.025 | – | – | 1553.1276 | +| 193.0125 | – | – | – | 1553.2282 | +| 193.0000 | 193.000 | 193.00 | 193.0 | 1553.3288 | +| 192.9875 | – | – | – | 1553.4294 | +| 192.9750 | 192.975 | – | – | 1553.5300 | +| 192.9625 | – | – | – | 1553.6307 | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | +| 184.7750 | 184.775 | – | – | 1622.4731 | +| 184.7625 | – | – | – | 1622.5828 | +| 184.7500 | 184.750 | 184.75 | – | 1622.6926 | +| 184.7375 | – | – | – | 1622.8024 | +| 184.7250 | 184.725 | – | – | 1622.9122 | +| 184.7125 | – | – | – | 1623.0220 | +| 184.7000 | 184.700 | 184.70 | 184.7 | 1623.1319 | +| 184.6875 | – | – | – | 1623.2417 | +| 184.6750 | 184.675 | – | – | 1623.3516 | +| 184.6625 | – | – | – | 1623.4615 | +| 184.6500 | 184.650 | 184.65 | – | 1623.5714 | +| 184.6375 | – | – | – | 1623.6813 | +| 184.6250 | 184.625 | – | – | 1623.7912 | +| 184.6125 | – | – | – | 1623.9012 | +| 184.6000 | 184.600 | 184.60 | 184.6 | 1624.0111 | +| 184.5875 | – | – | – | 1624.1211 | +| 184.5750 | 184.575 | – | – | 1624.2311 | +| 184.5625 | – | – | – | 1624.3411 | +| 184.5500 | 184.550 | 184.55 | – | 1624.4511 | +| 184.5375 | – | – | – | 1624.5612 | + +**Table 1 – Example nominal central frequencies of the DWDM grid** + +| Nominal central frequencies (THz) for spacings of: | | | | Approximate nominal central wavelengths (nm) (Note) | +|----------------------------------------------------|---------|--------|-------------------|-----------------------------------------------------| +| 12.5 GHz | 25 GHz | 50 GHz | 100 GHz and above | | +| 184.5250 | 184.525 | – | – | 1624.6712 | +| 184.5125 | – | – | – | 1624.7813 | +| 184.5000 | 184.500 | 184.50 | 184.5 | 1624.8914 | +| • | • | • | • | • | +| • | • | • | • | • | +| • | • | • | • | • | + +NOTE – The wavelengths given in this table are approximations only. The specifications applied to DWDM applications are defined with respect to the nominal central frequencies and not the approximate wavelengths. + +## **8 Flexible DWDM grid definition** + +For the flexible DWDM grid, the allowed frequency slots have a nominal central frequency (in THz) defined by: + +$$193.1 + n \times 0.00625 \text{ where } n \text{ is a positive or negative integer including } 0 \text{ and } 0.00625 \text{ is the nominal central frequency granularity in THz}$$ + +and a slot width defined by: + +$$12.5 \times m \text{ where } m \text{ is a positive integer and } 12.5 \text{ is the slot width granularity in GHz.}$$ + +Any combination of frequency slots is allowed as long as no two frequency slots overlap. + +Further information on the use of the flexible grid can be found in Appendix I. + +## Appendix I + +### Use of the flexible grid + +(This appendix does not form an integral part of this Recommendation.) + +### I.1 Flexible grid examples + +In addition to the fixed spacing dense wavelength division multiplexing (DWDM) grids defined in clause 7, a newer flexible DWDM grid has been introduced in clause 8. One of the motivations for the flexible grid is to allow a mixed bit rate or mixed modulation format transmission system to allocate frequency slots with different widths so that they can be optimized for the bandwidth requirements of the particular bit rate and modulation scheme of the individual channels. Because of the complexity of defining multi-vendor interoperable transmission systems containing mixed bit rates or modulation formats, there are currently no DWDM optical interface Recommendations that make use of this grid. + +An example use of the flexible DWDM grid is shown in Figure I.1, where two 50 GHz slots are shown together with two 75 GHz slots. For each slot in the figure, the values of $n$ and $m$ in the formulae defining the slot parameters in clause 8 are also given. The frequency range between 193.125 THz and 193.18125 THz is shown unallocated. This range could be left as a "guard band" between the two sets of channels or it could subsequently be allocated to an additional slot with a width of 50 GHz ( $n=8, m=4$ ), leaving 6.25 GHz unallocated, or other alternatives (e.g., two 25 GHz slots $n=6, m=2$ and $n=10, m=2$ ). + +![Figure I.1: An example of the use of the flexible grid. The diagram shows a frequency spectrum from 193.025 THz to 193.3125 THz. It features two 50 GHz slots on the left (n = -8, m = 4 and n = 0, m = 4) and two 75 GHz slots on the right (n = 19, m = 6 and n = 31, m = 6). A gap between 193.125 THz and 193.18125 THz is unallocated.](dd330f8b8f6c16eae20c3a676b4eb804_img.jpg) + +Figure I.1 illustrates the flexible grid with two 50 GHz slots and two 75 GHz slots. The frequency scale ranges from 193.025 THz to 193.3125 THz. The first 50 GHz slot is defined by $n = -8, m = 4$ and spans from 193.025 THz to 193.075 THz. The second 50 GHz slot is defined by $n = 0, m = 4$ and spans from 193.075 THz to 193.125 THz. There is an unallocated gap between 193.125 THz and 193.18125 THz. The first 75 GHz slot is defined by $n = 19, m = 6$ and spans from 193.18125 THz to 193.25625 THz. The second 75 GHz slot is defined by $n = 31, m = 6$ and spans from 193.25625 THz to 193.3125 THz. The diagram is labeled G.694.1(20)\_FI.1. + +Figure I.1: An example of the use of the flexible grid. The diagram shows a frequency spectrum from 193.025 THz to 193.3125 THz. It features two 50 GHz slots on the left (n = -8, m = 4 and n = 0, m = 4) and two 75 GHz slots on the right (n = 19, m = 6 and n = 31, m = 6). A gap between 193.125 THz and 193.18125 THz is unallocated. + +Figure I.1 – An example of the use of the flexible grid + +The granularity of the nominal central frequency and slot width parameters for the flexible DWDM grid have been chosen so that any of the fixed spacing DWDM grids defined in clause 7 can also be described via suitable choices of slots in the flexible DWDM grid. For example, the 50 GHz fixed spacing DWDM grid is shown in Figure I.2 represented using the DWDM flexible grid. + +![Figure I.2: The 50 GHz fixed spacing grid represented using the flexible grid. The diagram shows a frequency spectrum from 193.025 THz to 193.325 THz, divided into six consecutive 50 GHz slots. The slots are defined by n = -8, m = 4; n = 0, m = 4; n = 8, m = 4; n = 16, m = 4; n = 24, m = 4; and n = 32, m = 4.](83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg) + +Figure I.2 shows the 50 GHz fixed spacing grid represented using the flexible grid. The frequency scale ranges from 193.025 THz to 193.325 THz. The grid consists of six consecutive 50 GHz slots. The slots are defined by the following parameters: $n = -8, m = 4$ (193.025 THz to 193.075 THz), $n = 0, m = 4$ (193.075 THz to 193.125 THz), $n = 8, m = 4$ (193.125 THz to 193.175 THz), $n = 16, m = 4$ (193.175 THz to 193.225 THz), $n = 24, m = 4$ (193.225 THz to 193.275 THz), and $n = 32, m = 4$ (193.275 THz to 193.325 THz). The diagram is labeled G.694.1(20)\_FI.2. + +Figure I.2: The 50 GHz fixed spacing grid represented using the flexible grid. The diagram shows a frequency spectrum from 193.025 THz to 193.325 THz, divided into six consecutive 50 GHz slots. The slots are defined by n = -8, m = 4; n = 0, m = 4; n = 8, m = 4; n = 16, m = 4; n = 24, m = 4; and n = 32, m = 4. + +Figure I.2 – The 50 GHz fixed spacing grid represented using the flexible grid + +Since the smallest spacing fixed grid is 12.5 GHz, the slot width granularity needs to be 12.5 GHz. In order to be able to place a slot that has a width that is an even multiple of 12.5 GHz next to one + +with a width that is an odd multiple of 12.5 GHz without a gap, the nominal central frequency granularity needs to be 6.25 GHz. An example of this is shown in Figure I.3. + +![Figure I.3: A frequency spectrum diagram showing four contiguous slots with widths of 87.5 GHz, 87.5 GHz, 50 GHz, and 50 GHz. The slots are labeled with n and m values: n = -1, m = 7; n = 13, m = 7; n = 24, m = 4; and n = 32, m = 4. The frequency axis ranges from 193.05 to 193.325 THz with tick marks every 6.25 GHz.](2236272d3b3db6e6363337f5a8db72f6_img.jpg) + +The diagram illustrates a frequency spectrum with four contiguous slots. The top of the diagram shows the width of each slot using double-headed arrows: 87.5 GHz, 87.5 GHz, 50 GHz, and 50 GHz. Below this, the slots are represented as rounded rectangles labeled with their respective $n$ and $m$ values: $n = -1, m = 7$ ; $n = 13, m = 7$ ; $n = 24, m = 4$ ; and $n = 32, m = 4$ . A horizontal axis below the slots has tick marks every 6.25 GHz. Specific frequency labels (in THz) are placed vertically below certain tick marks: 193.05, 193.09375, 193.1375, 193.18125, 193.225, 193.25, 193.275, 193.3, and 193.325. The label G.694.1(20)\_FI.3 is present in the bottom right corner. + +Figure I.3: A frequency spectrum diagram showing four contiguous slots with widths of 87.5 GHz, 87.5 GHz, 50 GHz, and 50 GHz. The slots are labeled with n and m values: n = -1, m = 7; n = 13, m = 7; n = 24, m = 4; and n = 32, m = 4. The frequency axis ranges from 193.05 to 193.325 THz with tick marks every 6.25 GHz. + +**Figure I.3 – Example showing the need for 6.25 GHz nominal central frequency granularity** + +### I.2 Flexible grid compliance + +The flexible DWDM grid defined in clause 8 has a nominal central frequency granularity of 6.25 GHz and a slot width granularity of 12.5 GHz. However, devices or applications that make use of the flexible grid may not have to be capable of supporting every possible slot width or position. In other words, applications may be defined where only a subset of the possible slot widths and positions are required to be supported. + +For example, an application could be defined where the nominal central frequency granularity is 12.5 GHz (by only requiring values of $n$ that are even) and that only requires slot widths as a multiple of 25 GHz (by only requiring values of $m$ that are even). + + + + + +## 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.701-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.701-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bd1715b3a587fc50847d304004966466f21fed --- /dev/null +++ b/marked/G/T-REC-G.701-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a606405f6e113c99bc45a761e9826662fb99db9219576e7043fc02933a015c +size 8297 diff --git a/marked/G/T-REC-G.701-199303-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg b/marked/G/T-REC-G.701-199303-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dccb9f70422debb6ffa91d6478a1c64221474b57 --- /dev/null +++ b/marked/G/T-REC-G.701-199303-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4b3bd1812576710669467aea1019d9dd5eb3deeb38365aa3922e88c0ce2e8d9 +size 31719 diff --git a/marked/G/T-REC-G.701-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg b/marked/G/T-REC-G.701-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65dfd5b94c8fa5189440455ed964bc0ca4d9654e --- /dev/null +++ b/marked/G/T-REC-G.701-199303-I_PDF-E/5cab96b2d23174c25919840ecd50aa48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57e62d084001a1b9bf78a35c225521fa81f3dbce6f97648cb4c400107be8e2b6 +size 163458 diff --git a/marked/G/T-REC-G.701-199303-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg b/marked/G/T-REC-G.701-199303-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61361bef51bee9fc55b4cd7c3cbfdee9fa007748 --- /dev/null +++ b/marked/G/T-REC-G.701-199303-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab840c24ce2c348c2e50c5c8223b3f316de99f9a2a7bc0f4710e3b8627a6422 +size 33638 diff --git a/marked/G/T-REC-G.701-199303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.701-199303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae1baea6001befb48f811120e196d12e87380b28 --- /dev/null +++ b/marked/G/T-REC-G.701-199303-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:315152cea00553a3e0a3d59c8eb13ea86146ae2d751b9d25884817933ab74e23 +size 55010 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76f458e620a648b2771294471734b35f281fe500 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7d036abaa3194174b525628ddb4da801fca26b9f7d6c3d686fad81689eac917 +size 16504 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.704-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.704-199810-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ee0b37ead01626b7f3c321b953993dfcccbe8af --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:907de2acd1201161d41fc68ce2f62129c1f9495c81c62ab48e2c9227d9efe40e +size 23233 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a214403e429f35c981aa14485011ca6ba2ad769 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb1796648f17c70056883962b3d9e42878d863cd493c45420275b6d88d53d58 +size 22197 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19dea3647955e851d688ee21d35fbac8175caf48 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e726d15557b80d96b4b75ca605783e50504643a383ad149241979bd40f3928cf +size 6250 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/aae931686f171424d9dd35b358f91ce6_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/aae931686f171424d9dd35b358f91ce6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cd4d27b9845ad674b0c7bc05eb847b9798efcd5 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/aae931686f171424d9dd35b358f91ce6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4efcdec1c5d1bc7ffb3adea3a608b7cc3531bcfe3a322b0cb33d4fa0aff40b7 +size 71941 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64bd49825d156beac30d9ce57ca6fd178f843888 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51aad77edf7c0771511356430bebe1a9782b8c2a7b421dcdf8a6d71da779f83c +size 17814 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd9ae217c2f8bc2f46288c426fa2c12b1e1f6507 --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1b0ebf1d5e9acda546f44e67edc33be7f21c157e38b83082fda6bff328c6cbb +size 92915 diff --git a/marked/G/T-REC-G.704-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.704-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61a3730652bdafe1df2f432fe03eae7a454d36ef --- /dev/null +++ b/marked/G/T-REC-G.704-199810-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6773dac25fdd812dfea4616ffae6003e3b94e94daeb51ea1186e490851e10517 +size 30096 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f2b8737351f6b185c8efd3cbcab21b5ff5c4f42 --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b68139957026a6e41da864083e2eaf06b54bab34815587cbc74f700e6271584 +size 7726 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..500b0580631ff21d4c52bfa01c9570fc95cc7168 --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0aa67be041928c3ecdaf5c7e0f491b88cbb9fc226018f87f86c04f6a578832e +size 31953 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0793a9adc51e754c1773d80255ea9c1b515298ce --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e8d4c60b7e0b33e95ba450387709f50e8e10f0b3d31d12ed3193554f5a39b47 +size 151914 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cafcbf3e67a9cbd71e4e6e150dab4a4a8db204c5 --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/6324b252294c0f5d4e34dad4a1202075_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9686d36e11237b2beece1fd4b1b494dca71eacb50a64d604ee0c427dc6fa91a8 +size 34650 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6555780c80076e4ec44e6292c24b27d1f6978b9d --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83e394b3a18f275522d25679d0ffa5be49f3cb763865cd429c9a3493036cedc9 +size 6868 diff --git a/marked/G/T-REC-G.706-199104-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.706-199104-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d73f33a829380294b6f151e26ccef464b825cd79 --- /dev/null +++ b/marked/G/T-REC-G.706-199104-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffa7ee2bbc8e43d700bbe10dc285b0c755009b0feb8117b2bf6582cde4fd985f +size 38652 diff --git a/marked/G/T-REC-G.709.5-202403-I_PDF-E/raw.md b/marked/G/T-REC-G.709.5-202403-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f488b753bea0003e833394d03cfb5d73b90c234b --- /dev/null +++ b/marked/G/T-REC-G.709.5-202403-I_PDF-E/raw.md @@ -0,0 +1,1517 @@ + + +# Recommendation + +## **ITU-T G.709.5 (03/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital terminal equipments – General + +--- + +## **Flexible OTN short-reach interfaces** + +![ITU logo](84a1d09fb489061482111515543b60dc_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 | +| General | G.700-G.709 | +| Coding of voice and audio signals | G.710-G.729 | +| Principal characteristics of primary multiplex equipment | G.730-G.739 | +| Principal characteristics of second order multiplex equipment | G.740-G.749 | +| Principal characteristics of higher order multiplex equipment | G.750-G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760-G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770-G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780-G.789 | +| Other terminal equipment | G.790-G.799 | +| DIGITAL NETWORKS | G.800-G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 | +| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000-G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000-G.6999 | +| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000-G.7999 | +| PACKET OVER TRANSPORT ASPECTS | G.8000-G.8999 | +| ACCESS NETWORKS | G.9000-G.9999 | + +For further details, please refer to the list of ITU-T Recommendations. + +# Recommendation ITU-T G.709.5 + +## Flexible OTN short-reach interfaces + +## Summary + +Recommendation ITU-T G.709.5 specifies 100G, 200G, 400G and 800G flexible optical transport network (FlexO) short-reach interfaces. This Recommendation specifies the structure using forward error correction (FEC) code with a coding gain suitable for short-reach applications, and references common elements from Recommendation ITU-T G.709.1. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.709.5 | 2024-03-08 | 15 | 11.1002/1000/15794 | + +## Keywords + +Digital client signal, FlexO, FlexO-x-RS, RS, short-reach. + +--- + +\* 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 ..... | 1 | +| 3.1 | Terms defined elsewhere..... | 1 | +| 3.2 | Terms defined in this Recommendation ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Introduction and applications ..... | 3 | +| 7 | Structure and processes..... | 3 | +| 7.1 | Basic signal structure..... | 3 | +| 7.2 | Processing and information flow..... | 4 | +| 8 | FlexO frame ..... | 4 | +| 9 | Overhead..... | 4 | +| 9.1 | Alignment markers..... | 4 | +| 9.2 | FlexO-1-RS alignment markers ..... | 5 | +| 9.3 | FlexO-2-RS alignment markers ..... | 5 | +| 9.4 | FlexO-4-RS alignment markers ..... | 6 | +| 9.5 | FlexO-8-RS alignment markers ..... | 7 | +| 10 | FlexO mapping procedures..... | 9 | +| 11 | 100G FlexO-1-RS interface ..... | 9 | +| 11.1 | Frame structure..... | 9 | +| 11.2 | Bit rate and frame periods ..... | 10 | +| 11.3 | Scrambling ..... | 11 | +| 11.4 | Forward error correction (FEC)..... | 12 | +| 11.5 | FOIC1.k-RS interface ..... | 12 | +| 12 | 200G FlexO-2-RS interface ..... | 14 | +| 12.1 | Frame structure..... | 14 | +| 12.2 | Bit rate and frame periods ..... | 15 | +| 12.3 | Scrambling ..... | 16 | +| 12.4 | Forward error correction (FEC)..... | 17 | +| 12.5 | FOIC2.k-RS interface ..... | 17 | +| 13 | 400G FlexO-4-RS interface ..... | 20 | +| 13.1 | Frame structure..... | 20 | +| 13.2 | Bit rate and frame periods ..... | 21 | +| 13.3 | Scrambling ..... | 21 | +| 13.4 | Forward error correction (FEC)..... | 22 | +| 13.5 | FOIC4.k-RS interface ..... | 22 | + +| | Page | +|-----------------------------------------------------------------------------------------|-----------------------------------------------------------| +| 14 | 800G FlexO-8-RS interface..... 26 | +| 14.1 | Frame structure..... 26 | +| 14.2 | Bit rate and frame periods..... 27 | +| 14.3 | Scrambling..... 27 | +| 14.4 | Forward error correction (FEC)..... 27 | +| 14.5 | FOIC8.k-RS interface..... 27 | +| Annex A – Forward error correction for FlexO-x-RS using 10-bit RS(544,514) codecs ..... | 34 | +| A.1 | Generic processing and common code structure..... 34 | +| A.2 | FlexO-1-RS FEC codeword adaptation..... 35 | +| A.3 | FlexO-2-RS and FlexO-4-RS FEC codeword adaptation..... 35 | +| A.4 | FlexO-8-RS FEC codeword adaptation..... 36 | +| Bibliography..... | 37 | + +# Recommendation ITU-T G.709.5 + +## Flexible OTN short-reach interfaces + +# 1 Scope + +Recommendation ITU-T G.709.5 specifies a set of interoperable flexible optical transport network (FlexO) short-reach interfaces. The rates in scope for FlexO-x- are 100G, 200G, 400G and 800G (x=1, 2, 4 and 8). This Recommendation specifies the structure using forward error correction (FEC) code with a coding gain suitable for short-reach applications, and references common elements from [ITU-T G.709.1]. + +The types of FlexO short-reach interfaces that can serve as FlexO-x-RS-m interface group members are covered by application codes which are at the time of publication: 4I1-9D1F, 4L1-9C1F, C4S1-9D1F, 4L1-9D1F, C4S1-4D1F, 8R1-4D1F, 4I1-4D1F and 8I1-4D1F. These application codes are presented in [ITU-T G.695] and [ITU-T G.959.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.695] Recommendation ITU-T G.695 (2018), *Optical interfaces for coarse wavelength division multiplexing applications.* +- [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 (2024), *Flexible OTN common elements.* +- [ITU-T G.798] Recommendation ITU-T G.798 (2023), *Characteristics of optical transport network hierarchy equipment functional blocks.* +- [ITU-T G.959.1] Recommendation ITU-T G.959.1 (2024), *Optical transport network physical layer interfaces.* +- [IEEE 802.3] IEEE Std. 802.3-2022, *IEEE Standard for Ethernet.* +- [IEEE 802.3df] IEEE Std. 802.3df-2024, *IEEE Standard for Ethernet Amendment 9: Media Access Control Parameters for 800 Gb/s and Physical Layers and Management Parameters for 400 Gb/s and 800 Gb/s Operation.* + +# 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 optical transport unit order Cn (OTUCn) +- optical transport network (OTN) +- optical tributary signal (OTSi) + +- optical tributary signal assembly (OTSiA) + +### **3.1.2 Terms defined in [ITU-T G.709.1]** + +- FlexO +- FlexO-n +- FlexO-x +- FlexO-x- +- FlexO-x- interface +- FlexO-x--m interface group +- FOICx.k- + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|----------------------------------------------| +| AMi | Alignment Marker of index i | +| AM | Alignment Mechanism | +| BOH | Basic Overhead Field | +| CAUI | (Chip to) 100 Gb/s Attachment Unit Interface | +| CM | Common Marker | +| EOH | Extended Overhead Field | +| FEC | Forward Error Correction | +| FlexO | Flexible Optical Transport Network | +| GID | Group Identification | +| LSB | Least Significant Bit | +| MSB | Most Significant Bit | +| OH | Overhead | +| OTL | Optical Transport Lane | +| OTN | Optical Transport Network | +| OTSi | Optical Tributary Signal | +| OTU | Optical Transport Unit | +| OTUCn | OTU order Cn | +| PCS | Physical Coding Sublayer | +| RS | Reed-Solomon | +| UM | Unique Marker | +| UP | Unique Pad | + +# 5 Conventions + +This Recommendation uses the following conventions: + +### Names of information structures and interfaces: + +The terms FlexO-n, FlexO-x, FlexO-x-, FlexO-x--m, and FOICx.k- are used to refer to FlexO information structures and interfaces that are optimized for the optical transport network (OTN) bit rates. + +**n:** The index "n" is used to represent the number of FlexO instances that are in a FlexO group. + +**x:** The index "x" is used to represent the bit rate of the FlexO interface, in 100G increments. For example, x=1 for 100G, x=2 for 200G, x=4 for 400G, etc. + +**m:** The index "m" is used to represent the number of interfaces in a FlexO group. m is also used to represent the number of bits in a block of data / stuff in client mappings. + +**k:** The index "k" is used to represent the number of lanes on an FOICx.k- interface. + +**:** The placeholder is used by this Recommendation as RS to name the short-reach interface which includes Reed-Solomon (RS) FEC. + +The term "logical lanes" is equivalent to the term physical coding sublayer "PCS lanes" for Ethernet BASE-R interfaces. It is used to identify the internal lanes over which a FlexO-x-RS signal is distributed. One or more "logical lanes" can be multiplexed and carried on a physical lane at an OTSi interface. + +**Transmission order:** The order of transmission of information in all the diagrams in this Recommendation is first from left to right and then from top to bottom. Within each byte the most significant bit (MSB) is transmitted first. The most significant bit (bit 1) is illustrated on the left side of all diagrams. + +**Value of reserved bit(s):** The value of an overhead (OH) bit, which is reserved for future international standardization, shall be set to "0". + +**Value of non-sourced bit(s):** Unless stated otherwise, any non-sourced bits shall be set to "0". + +# 6 Introduction and applications + +The FlexO short-reach interface groups specified in this Recommendation provide an interoperable interface reusing Ethernet client modules. The FlexO interfaces only support OTUCn clients. + +Refer to clause 6.1 of [ITU-T G.709.1] and Appendix I of [ITU-T G.709.1] for short-reach applications. + +# 7 Structure and processes + +This clause introduces the FlexO-x-RS-m interface group's basic signal structure, processes and information flow. + +## 7.1 Basic signal structure + +The information structure for FlexO-x-RS groups is represented by information containment relationships and flows. The principal information containment relationship is described in Figure 7-1. The higher layers of the containment relationship are shown in Figure 7-1 of [ITU-T G.709.1]. + +The n FlexO instances from the FlexO-n signal are mapped into one FlexO-x-RS-m signal, consisting of $m = \lceil n/x \rceil$ FlexO-x-RS interfaces. Each FlexO-x-RS interface contains one padded and scrambled FlexO-x signal consisting of "x" interleaved FlexO signals, plus RS FEC parity. + +Each FlexO-x-RS information structure is split into $k$ FOICx.k-RS lanes. Depending on the pluggable optical module, each electrical lane signal may be modulated onto one OTSi and the set of $k$ OTSi is transported as an OTSiG via one media element as illustrated in Figure 7-1 below. + +![Figure 7-1: FlexO-x-RS-m interface group principal information containment relationship diagram. The diagram shows the hierarchical structure of data from a FlexO-n layer down to a Media element. FlexO-n contains a Payload. FlexO-x-RS-m (where m = ceiling(n/x)) contains an OH, Payload, and FEC. This is split into m x k FOICx.k-RS lanes, each containing FOICx.k lane 1, 2, k-1, and k. These are further split into m OTSi (OTSi 1, 2, k-1, k). Finally, all OTSi are mapped to a single Media element. A legend indicates AM (Alignment Marker) with diagonal lines, EOH (Extended Overhead) with horizontal lines, and BOH (Basic Overhead) with a cross-hatch pattern.](f4fdd410cdb84df81274da55721e56fb_img.jpg) + +Figure 7-1: FlexO-x-RS-m interface group principal information containment relationship diagram. The diagram shows the hierarchical structure of data from a FlexO-n layer down to a Media element. FlexO-n contains a Payload. FlexO-x-RS-m (where m = ceiling(n/x)) contains an OH, Payload, and FEC. This is split into m x k FOICx.k-RS lanes, each containing FOICx.k lane 1, 2, k-1, and k. These are further split into m OTSi (OTSi 1, 2, k-1, k). Finally, all OTSi are mapped to a single Media element. A legend indicates AM (Alignment Marker) with diagonal lines, EOH (Extended Overhead) with horizontal lines, and BOH (Basic Overhead) with a cross-hatch pattern. + +**Figure 7-1 – FlexO-x-RS-m interface group principal information containment relationship** + +## 7.2 Processing and information flow + +Functions, processes, and information flows are more formally specified in [ITU-T G.798]. + +# 8 FlexO frame + +Refer to clause 8 of [ITU-T G.709.1]. + +The short-reach interfaces in this Recommendation use $z=10$ interleaving granularity. + +# 9 Overhead + +Refer to clause 9.1 of [ITU-T G.709.1] for a general description of the alignment mechanism (AM) overhead and to the clauses below for descriptions of the FlexO-x-RS alignment markers. + +Refer to clauses 9.2 and 9.3 of [ITU-T G.709.1] for the basic overhead field (BOH) and extended overhead field (EOH) definitions. + +## 9.1 Alignment markers + +Lane alignment markers in the AM field are used for lane delineation, lane deskewing and lane ordering. + +Four 120-bit lane alignment markers fit in the AM field of a FlexO frame. + +A lane alignment marker, as shown in Figure 9-1, consists of a common portion across all lanes, a unique portion per lane and some pad bits. + +- CMx = 8-bit common marker field (common across lanes) – used for aligning lanes; +- UMx = 8-bit unique marker field – used for identifying lanes; +- UPx = 8-bit unique pad field – used for providing a DC balance when multiplexing lanes. + +NOTE – Alignment marker area length specified by clause 91 of [IEEE 802.3] for 100 Gbit/s Ethernet interfaces, is 1 285-bit per alignment marker FEC frame period (every 4 096 FEC codewords). It consists of 20 alignment marker blocks of 64-bit, plus 5-bit extra padding required for 257b block alignment. + +![Figure 9-1: FlexO-x-RS lane alignment marker format. A horizontal bar representing 120 bits. Bit positions are marked above: 1, 24, 25, 32, 33, 56, 57, 64, 65, 88, 89, 96, 97, 120. The bar is divided into segments: {CM0, CM1, CM2} (bits 1-24), UP0 (bits 25-32), {CM3, CM4, CM5} (bits 33-56), UP1 (bits 57-64), {UM0, UM1, UM2} (bits 65-88), UP2 (bits 89-96), and {UM3, UM4, UM5} (bits 97-120).](5b4e774d63e0e0ed73801a9247755e5f_img.jpg) + +Figure 9-1: FlexO-x-RS lane alignment marker format. A horizontal bar representing 120 bits. Bit positions are marked above: 1, 24, 25, 32, 33, 56, 57, 64, 65, 88, 89, 96, 97, 120. The bar is divided into segments: {CM0, CM1, CM2} (bits 1-24), UP0 (bits 25-32), {CM3, CM4, CM5} (bits 33-56), UP1 (bits 57-64), {UM0, UM1, UM2} (bits 65-88), UP2 (bits 89-96), and {UM3, UM4, UM5} (bits 97-120). + +**Figure 9-1 – FlexO-x-RS lane alignment marker format** + +## 9.2 FlexO-1-RS alignment markers + +The FlexO-1-RS signal supports the distribution into four logical lanes, numbered 0, 1, 2 and 3. Each lane carries a 120-bit lane alignment marker (*ami*, *i* = 0, 1, 2, 3) as specified in Table 9-1. Rows of Table 9-1 give the values of the alignment marker of index *i* (*ami*) transmitted over logical lane *i*. + +**Table 9-1 – FlexO-1-RS alignment marker encodings** + +| Logical lane | Encoding | | | | | | | | | | | | | | | +|--------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | CM 0 | CM 1 | CM 2 | UP 0 | CM 3 | CM 4 | CM 5 | UP 1 | UM 0 | UM 1 | UM 2 | UP 2 | UM 3 | UM 4 | UM 5 | +| 0 | 59 | 52 | 64 | 6D | A6 | AD | 9B | 9B | 80 | 8E | CF | 64 | 7F | 71 | 30 | +| 1 | | | | 20 | | | | E6 | 5A | 7B | 7E | 19 | A5 | 84 | 81 | +| 2 | | | | 62 | | | | 7F | 7C | CF | 6A | 80 | 83 | 30 | 95 | +| 3 | | | | 5A | | | | 21 | 61 | 01 | 0B | DE | 9E | FE | F4 | + +NOTE – The value in each byte of this table is in MSB-first transmission order. Note that this per-byte bit ordering is the reverse of the alignment marker values found in [IEEE 802.3], which uses a least significant bit (LSB)-first bit transmission format. + +The 480-bit FlexO-1 AM field contains 10-bit interleaved parts of *am*0, *am*1, *am*2 and *am*3 in repeating order, as illustrated in Figure 9-2. + +![Figure 9-2: FlexO-1-RS AM field with four interleaved lane alignment markers. A diagram showing a 480-bit AM field. Below it, a sequence of vertical blocks represents the interleaving: 1st 10 bits of am0, 1st 10 bits of am1, 1st 10 bits of am2, 1st 10 bits of am3, followed by 2nd, 3rd, and 4th sets of 10 bits for each lane. The sequence ends with the 11th and 12th sets of 10 bits for lanes am0 through am3, totaling 48 segments of 10 bits each.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +Figure 9-2: FlexO-1-RS AM field with four interleaved lane alignment markers. A diagram showing a 480-bit AM field. Below it, a sequence of vertical blocks represents the interleaving: 1st 10 bits of am0, 1st 10 bits of am1, 1st 10 bits of am2, 1st 10 bits of am3, followed by 2nd, 3rd, and 4th sets of 10 bits for each lane. The sequence ends with the 11th and 12th sets of 10 bits for lanes am0 through am3, totaling 48 segments of 10 bits each. + +**Figure 9-2 – FlexO-1-RS AM field with four interleaved lane alignment markers** + +## 9.3 FlexO-2-RS alignment markers + +The FlexO-2-RS signal supports the distribution into eight logical lanes, numbered 0, 1, 2 to 7. Each lane carries a 120-bit lane alignment marker (*ami*, *i* = 0, 1, 2 to 7) as specified in Table 9-2. Rows of Table 9-2 give the values of *ami* transmitted over logical lane *i*. + +**Table 9-2 – FlexO-2-RS alignment marker encodings** + +| Logical lane | Encoding | | | | | | | | | | | | | | | +|--------------|----------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | CM0 | CM1 | CM2 | UP0 | CM3 | CM4 | CM5 | UP1 | UM0 | UM1 | UM2 | UP2 | UM3 | UM4 | UM5 | +| 0 | 59 | 52 | 64 | A0 | A6 | AD | 9B | 6B | CD | 03 | 31 | 94 | 32 | FC | CE | +| 1 | | | | 20 | | | | E6 | 5A | 7B | 7E | 19 | A5 | 84 | 81 | +| 2 | | | | 62 | | | | 7F | 7C | CF | 6A | 80 | 83 | 30 | 95 | +| 3 | | | | 5A | | | | 21 | 61 | 01 | 0B | DE | 9E | FE | F4 | +| 4 | | | | 87 | | | | 98 | 54 | 8A | 4F | 67 | AB | 75 | B0 | +| 5 | | | | 4F | | | | 72 | 48 | F2 | 8B | 8D | B7 | 0D | 74 | +| 6 | | | | BC | | | | 77 | 42 | 39 | 85 | 88 | BD | C6 | 7A | +| 7 | | | | 44 | | | | 4C | 6B | 6E | DA | B3 | 94 | 91 | 25 | + +NOTE – The value in each byte of this table is in MSB-first transmission order. Note that this per-byte bit ordering is the reverse of the alignment marker values found in [IEEE 802.3], which uses an LSB-first bit transmission format. + +The 960-bit FlexO-2 AM field contains 10-bit interleaved parts of am0, am1, am2, am3, am4, am5, am6 and am7 as illustrated in Figure 9-3. Note that for even numbered interleaved sequences (i.e., the 2nd 10 bits sequence, the 4th ... the 12th 10 bits sequence) the interleaving of lane alignment markers is odd/even (i.e., am1, am0, am3, am2, am5, am4, am7, am6). + +![Diagram of the FlexO-2-RS AM field showing 960 bits of alignment markers (AM) interleaved from eight lanes. The diagram shows two groups of 10-bit sequences. The first group contains 1st 10 bits of am0, am1, am2, am3, am4, am5, am6, am7, followed by 2nd 10 bits of am1, am0, am3, am2, am5, am4, am7, am6. The second group contains 11th 10 bits of am0, am1, am2, am3, am4, am5, am6, am7, followed by 12th 10 bits of am1, am0, am3, am2, am5, am4, am7, am6. A vertical bar labeled 'AM' spans from bit 1 to bit 960. A note G.709.5(24) is present at the bottom right.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +G.709.5(24) + +Diagram of the FlexO-2-RS AM field showing 960 bits of alignment markers (AM) interleaved from eight lanes. The diagram shows two groups of 10-bit sequences. The first group contains 1st 10 bits of am0, am1, am2, am3, am4, am5, am6, am7, followed by 2nd 10 bits of am1, am0, am3, am2, am5, am4, am7, am6. The second group contains 11th 10 bits of am0, am1, am2, am3, am4, am5, am6, am7, followed by 12th 10 bits of am1, am0, am3, am2, am5, am4, am7, am6. A vertical bar labeled 'AM' spans from bit 1 to bit 960. A note G.709.5(24) is present at the bottom right. + +**Figure 9-3 – FlexO-2-RS AM field with eight interleaved lane alignment markers** + +## 9.4 FlexO-4-RS alignment markers + +The FlexO-4-RS signal supports the distribution into sixteen logical lanes, numbered 0, 1, 2 to 15. Each lane carries a 120-bit lane alignment marker (ami, i = 0, 1, 2 to 15) as specified in Table 9-3. Rows of Table 9-3 give the values of ami transmitted over logical lane i. + +**Table 9-3 – FlexO-4-RS alignment marker encodings** + +| Logical lane | Encoding | | | | | | | | | | | | | | | +|--------------|----------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | CM0 | CM1 | CM2 | UP0 | CM3 | CM4 | CM5 | UP1 | UM0 | UM1 | UM2 | UP2 | UM3 | UM4 | UM5 | +| 0 | 59 | 52 | 64 | 6D | A6 | AD | 9B | 9B | 80 | 8E | CF | 64 | 7F | 71 | 30 | +| 1 | | | | 20 | | | | E6 | 5A | 7B | 7E | 19 | A5 | 84 | 81 | +| 2 | | | | 62 | | | | 7F | 7C | CF | 6A | 80 | 83 | 30 | 95 | +| 3 | | | | 5A | | | | 21 | 61 | 01 | 0B | DE | 9E | FE | F4 | +| 4 | | | | 87 | | | | 98 | 54 | 8A | 4F | 67 | AB | 75 | B0 | +| 5 | | | | 4F | | | | 72 | 48 | F2 | 8B | 8D | B7 | 0D | 74 | +| 6 | | | | BC | | | | 77 | 42 | 39 | 85 | 88 | BD | C6 | 7A | +| 7 | | | | 44 | | | | 4C | 6B | 6E | DA | B3 | 94 | 91 | 25 | +| 8 | | | | 06 | | | | F9 | 87 | CE | AE | 06 | 78 | 31 | 51 | +| 9 | | | | D6 | | | | 45 | 8E | 23 | 3C | BA | 71 | DC | C3 | +| 10 | | | | 5F | | | | 20 | A9 | D7 | 1B | DF | 56 | 28 | E4 | +| 11 | | | | 36 | | | | 8E | 44 | 66 | 1C | 71 | BB | 99 | E3 | +| 12 | | | | 18 | | | | DA | 45 | 6F | A9 | 25 | BA | 90 | 56 | +| 13 | | | | 28 | | | | 33 | 8C | E9 | C3 | CC | 73 | 16 | 3C | +| 14 | | | | 0B | | | | 8D | 53 | DF | 65 | 72 | AC | 20 | 9A | +| 15 | | | | 2D | | | | 6A | 65 | 5D | 9E | 95 | 9A | A2 | 61 | + +NOTE – The value in each byte of this table is in MSB-first transmission order. Note that this per-byte bit ordering is the reverse of the alignment marker values found in [IEEE 802.3], which uses an LSB-first bit transmission format. + +The 1 920-bit FlexO-4 AM field contains 10-bit interleaved parts of am0, am1, am2, am3, am4, am5, am6, am7, am8, am9, am10, am11, am12, am13, am14 and am15 as illustrated in Figure 9-4. Note that for even numbered interleaved sequences (i.e., the 2nd 10 bits sequence, the 4th ... the 12th 10 bits sequence) the interleaving of lane alignment markers is odd/even (i.e., am1, am0, am3, am2, am5, am4, am7, am6, am9, am8, am11, am10, am13, am12, am15, am14). + +![Diagram of the FlexO-4-RS AM field showing 1920 bits of alignment markers (AM) interleaved from 16 logical lanes. The diagram shows a large block labeled 'AM' from bit 1 to 1920. Below it, two columns of 10-bit segments are shown, representing the interleaving of lanes am0 through am15. The first column contains segments for am0, am1, am2, am3, am4, am5, am6, am7, am8, am9, am10, am11, am12, am13, am14, am15, followed by a second set of am0 through am15. The second column contains segments for am10, am11, am12, am13, am14, am15, followed by a second set of am10 through am15. The segments are labeled with their respective lane numbers and bit positions (e.g., 1st 10 bits of am0, 2nd 10 bits of am1).](cab0834804fb031b43865554cc8d06ab_img.jpg) + +G.709.5(24) + +Diagram of the FlexO-4-RS AM field showing 1920 bits of alignment markers (AM) interleaved from 16 logical lanes. The diagram shows a large block labeled 'AM' from bit 1 to 1920. Below it, two columns of 10-bit segments are shown, representing the interleaving of lanes am0 through am15. The first column contains segments for am0, am1, am2, am3, am4, am5, am6, am7, am8, am9, am10, am11, am12, am13, am14, am15, followed by a second set of am0 through am15. The second column contains segments for am10, am11, am12, am13, am14, am15, followed by a second set of am10 through am15. The segments are labeled with their respective lane numbers and bit positions (e.g., 1st 10 bits of am0, 2nd 10 bits of am1). + +**Figure 9-4 – FlexO-4-RS AM field with sixteen interleaved lane alignment markers** + +## 9.5 FlexO-8-RS alignment markers + +The FlexO-8-RS signal supports distribution into thirty-two logical lanes. Each lane carries a 120-bit lane alignment marker (ami, i = 0 to 32) as specified in Table 9-4. Rows of Table 9-4 give the values of ami transmitted over logical lane i. + +**Table 9-4 – FlexO-8-RS alignment marker encodings** + +| Logical lane | Encoding | | | | | | | | | | | | | | | +|--------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | CM 0 | CM 1 | CM 2 | UP 0 | CM 3 | CM 4 | CM 5 | UP 1 | UM 0 | UM 1 | UM 2 | UP 2 | UM 3 | UM 4 | UM 5 | +| 0 | 59 | 52 | 64 | 6D | A6 | AD | 9B | 9B | 7F | 8E | CF | 64 | 80 | 71 | 30 | +| 1 | | | | 20 | | | | E6 | A5 | 7B | 7E | 19 | 5A | 84 | 81 | +| 2 | | | | 62 | | | | 7F | 83 | CF | 6A | 80 | 7C | 30 | 95 | +| 3 | | | | 5A | | | | 21 | 9E | 01 | 0B | DE | 61 | FE | F4 | +| 4 | | | | 87 | | | | 98 | AB | 8A | 4F | 67 | 54 | 75 | B0 | +| 5 | | | | 4F | | | | 72 | B7 | F2 | 8B | 8D | 48 | 0D | 74 | +| 6 | | | | BC | | | | 77 | BD | 39 | 85 | 88 | 42 | C6 | 7A | +| 7 | | | | 44 | | | | 4C | 94 | 6E | DA | B3 | 6B | 91 | 25 | +| 8 | | | | 06 | | | | F9 | 78 | CE | AE | 06 | 87 | 31 | 51 | +| 9 | | | | D6 | | | | 45 | 71 | 23 | 3C | BA | 8E | DC | C3 | +| 10 | | | | 5F | | | | 20 | 56 | D7 | 1B | DF | A9 | 28 | E4 | +| 11 | | | | 36 | | | | 8E | BB | 66 | 1C | 71 | 44 | 99 | E3 | +| 12 | | | | 18 | | | | DA | BA | 6F | A9 | 25 | 45 | 90 | 56 | +| 13 | | | | 28 | | | | 33 | 73 | E9 | C3 | CC | 8C | 16 | 3C | +| 14 | | | | 0B | | | | 8D | AC | DF | 65 | 72 | 53 | 20 | 9A | +| 15 | | | | 2D | | | | 6A | 9A | 5D | 9E | 95 | 65 | A2 | 61 | +| 16 | | | | 6D | | | | 9B | 80 | 71 | 30 | 64 | 7F | 8E | CF | +| 17 | | | | 20 | | | | E6 | 5A | 84 | 81 | 19 | A5 | 7B | 7E | +| 18 | | | | 62 | | | | 7F | 7C | 30 | 95 | 80 | 83 | CF | 6A | +| 19 | | | | 5A | | | | 21 | 61 | FE | F4 | DE | 9E | 01 | 0B | +| 20 | | | | 87 | | | | 98 | 54 | 75 | B0 | 67 | AB | 8A | 4F | +| 21 | | | | 4F | | | | 72 | 48 | 0D | 74 | 8D | B7 | F2 | 8B | +| 22 | | | | BC | | | | 77 | 42 | C6 | 7A | 88 | BD | 39 | 85 | +| 23 | | | | 44 | | | | 4C | 6B | 91 | 25 | B3 | 94 | 6E | DA | +| 24 | | | | 06 | | | | F9 | 87 | 31 | 51 | 06 | 78 | CE | AE | +| 25 | | | | D6 | | | | 45 | 8E | DC | C3 | BA | 71 | 23 | 3C | +| 26 | | | | 5F | | | | 20 | A9 | 28 | E4 | DF | 56 | D7 | 1B | +| 27 | | | | 36 | | | | 8E | 44 | 99 | E3 | 71 | BB | 66 | 1C | +| 28 | | | | 18 | | | | DA | 45 | 90 | 56 | 25 | BA | 6F | A9 | +| 29 | | | | 28 | | | | 33 | 8C | 16 | 3C | CC | 73 | E9 | C3 | +| 30 | | | | 0B | | | | 8D | 53 | 20 | 9A | 72 | AC | DF | 65 | +| 31 | | | | 2D | | | | 6A | 65 | A2 | 61 | 95 | 9A | 5D | 9E | + +NOTE – The value in each byte of this table is in MSB-first transmission order. Note that this per-byte bit ordering is the reverse of the alignment marker values found in [IEEE 802.3df], which uses an LSB-first bit transmission format. + +The 3 840-bit FlexO-8 AM field is carried in two separate 1 920-bit AM fields, one in 400G flow #0 and one in 400G flow #1 (see Figure 14-4). The 400G flow #0 AM field contains 10-bit interleaved parts of am0 through am15 and the 400G flow #1 AM field contains 10-bit interleaved parts of am16 through am31 as illustrated in Figure 9-5. Note that for even numbered interleaved sequences (e.g., the 2nd 10 bits sequence, the 4th ... the 12th 10 bits sequence) the interleaving of lane alignment markers is odd/even (e.g., am1, am0, am3, am2, am5, am4, ... am27, am26, am29, am28, am31, am30). + +![Diagram of FlexO-8-RS AM field with thirty-two interleaved lane alignment markers. It shows two rows of alignment markers (AM) for 400G flow #0 and 400G flow #1. Each flow has 32 lanes, with alignment markers placed every 10 bits. The markers are labeled with lane numbers (e.g., am0, am1, am2, etc.) and their bit positions (e.g., 1st, 2nd, 3rd, etc.). The diagram includes a callout 'G.709.5(24)'.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +G.709.5(24) + +Diagram of FlexO-8-RS AM field with thirty-two interleaved lane alignment markers. It shows two rows of alignment markers (AM) for 400G flow #0 and 400G flow #1. Each flow has 32 lanes, with alignment markers placed every 10 bits. The markers are labeled with lane numbers (e.g., am0, am1, am2, etc.) and their bit positions (e.g., 1st, 2nd, 3rd, etc.). The diagram includes a callout 'G.709.5(24)'. + +**Figure 9-5 – FlexO-8-RS AM field with thirty-two interleaved lane alignment markers** + +# 10 FlexO mapping procedures + +Refer to clause 10 of [ITU-T G.709.1]. + +Deskewing in the sink process is performed between OTUC instances within the OTUCn as specified in [ITU-T G.709.1] clause 10.4. + +The skew requirements are intended to account for variations due to the digital mapping, and cable lengths related to the delay differences for relevant applications as defined by [ITU-T G.695] and [ITU-T G.959.1]. The skew tolerance requirement over short-reach FlexO interface groups is 300 ns. + +# 11 100G FlexO-1-RS interface + +### 11.1 Frame structure + +The 100G FlexO-1-RS frame structure is shown in Figure 11-1 and consists of 128 rows by 5 440 1-bit columns. It contains a FlexO frame structure in columns 1 to 5 140 and a forward error correction (FEC) parity area in columns 5 141 to 5 440 in every row. FlexO-1-RS interfaces use alignment markers as described in clause 9. + +Each row constitutes a 5 440-bit FEC codeword, with the last 300 bits used for the FEC parity bits. This results in a bit-oriented structure. The MSB in each FEC codeword is column 1, the LSB is column 5 440. + +NOTE – The 100G FlexO-1-RS frame structure is derived from 100 Gbit/s Ethernet clause 91 [IEEE 802.3] FEC alignment and lane architecture, without any 66b alignment or 256b/257b transcoding functions. + +![Figure 11-1: 100G FlexO-1-RS frame structure diagram. It shows a grid of 128 rows and 5440 columns. The first 1280 columns are divided into AM (1-480), EOH (481-960), and BOH (961-1280). Columns 1281 to 5140 are the 'Payload area'. Columns 5141 to 5440 are the 'RS10 FEC area'. Horizontal arrows at the bottom indicate widths of 5140 bits for the payload and 300 bits for the FEC, totaling 5440 bits. The diagram is labeled G.709.5(24).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 11-1: 100G FlexO-1-RS frame structure diagram. It shows a grid of 128 rows and 5440 columns. The first 1280 columns are divided into AM (1-480), EOH (481-960), and BOH (961-1280). Columns 1281 to 5140 are the 'Payload area'. Columns 5141 to 5440 are the 'RS10 FEC area'. Horizontal arrows at the bottom indicate widths of 5140 bits for the payload and 300 bits for the FEC, totaling 5440 bits. The diagram is labeled G.709.5(24). + +Figure 11-1 – 100G FlexO-1-RS frame structure + +### 11.2 Bit rate and frame periods + +The bit rate and tolerance of the 100G FlexO-1-RS signal are defined in Table 11-1. + +The bit rate ratio between FlexO-x-RS and FlexO-x signals is shown in Figure 11-2. The number of columns 5 140 is not altered by the scrambling and AM insertion processes. The FEC encoder adds 300 columns resulting in 5 440. The lane distribution process does not alter the overall bit rate. + +![Figure 11-2: FlexO-x-RS/FlexO-x bit rate ratio diagram. A flowchart shows the signal processing: Input (FlexO-x bit rate) -> Scrambling (5140) -> AM insertion (5140) -> FEC encoder (5440) -> Lane distribution (5440) -> Output (k lanes). Above the flow, a dashed line with arrows indicates a ratio of 544/514. Below the input, the FlexO-x bit rate is given as (x × 491384/462961 × 99 523 800 kbit/s). Below the output, the FlexO-x-RS bit rate is given as (x × 30592/27233 × 99 523 800 kbit/s). The FOICx.k-RS lane bit rate is given as (x/k × 30592/27233 × 99 523 800 kbit/s). The diagram is labeled G.709.5(24).](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +Figure 11-2: FlexO-x-RS/FlexO-x bit rate ratio diagram. A flowchart shows the signal processing: Input (FlexO-x bit rate) -> Scrambling (5140) -> AM insertion (5140) -> FEC encoder (5440) -> Lane distribution (5440) -> Output (k lanes). Above the flow, a dashed line with arrows indicates a ratio of 544/514. Below the input, the FlexO-x bit rate is given as (x × 491384/462961 × 99 523 800 kbit/s). Below the output, the FlexO-x-RS bit rate is given as (x × 30592/27233 × 99 523 800 kbit/s). The FOICx.k-RS lane bit rate is given as (x/k × 30592/27233 × 99 523 800 kbit/s). The diagram is labeled G.709.5(24). + +Figure 11-2 – FlexO-x-RS/FlexO-x bit rate ratio + +Table 11-1 – 100G FlexO-1-RS bit rate + +| 100G FlexO-1-RS nominal bit rate | Bit-rate tolerance | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| $30592/27233 \times 99\ 523\ 800\ \text{kbit/s}$ | $\pm 20\ \text{ppm}$ | +| NOTE 1 – The nominal 100G FlexO-1-RS bit rate is approximately: 111 809 474.446 kbit/s.
NOTE 2 – The 100G FlexO-1-RS bit rate can be based on the OTUC bit rate as follows: $256/241 \times \text{OTUC bit rate} = 256/241 \times 239/226 \times 99\ 523\ 800\ \text{kbit/s}$ .
NOTE 3 – The resulting 100G FlexO-1-RS bit rate is within a $-4.46\ \text{ppm}$ offset of the OTU4 nominal bit rate. | | + +The frame and multi-frame periods of the 100G FlexO-1-RS signal are defined in Table 11-2. + +**Table 11-2 – 100G FlexO-1-RS frame and multi-frame periods** + +| Frame period (Note) | Multi-frame period (Note) | +|------------------------------------------------------------------------------|---------------------------| +| ~6.228 μs | 49.822 μs | +| NOTE – The period is an approximated value, rounded to three decimal places. | | + +### 11.3 Scrambling + +The 100G FlexO-1-RS frame payload, fixed stuffing, basic overhead and extended overhead must be scrambled prior to transmission in order to provide DC balance and proper running disparity on the interface. The lane alignment markers ( $a_m$ , $i = 0, 1, 2, 3$ ) in the AM field are not scrambled and the chosen values have properties of already being DC balanced. Figure 11-4 below shows the scrambled parts of the frame as yellow. + +The operation of the scrambler shall be functionally equivalent to that of a frame-synchronous additive scrambler with sequence length 65 535 and the generating polynomial shall be $x^{16} + x^{12} + x^3 + x + 1$ . See Figure 11-3 of [ITU-T G.709] for an illustration of this scrambler. + +The scrambler operates on the entire frame, including the AM field and the FEC area which contain undefined values when the frame is input to the scrambler. This is illustrated in Figure 11-3 where yellow indicates bits that are scrambled. The scrambler resets to 0xFFFF on the most significant (first transmitted) bit of the start of the FlexO-1-RS frame. The scrambler state advances during each bit of the frame. In the source function, the alignment markers are inserted into the AM field after scrambling and prior to the FEC encoding The FEC encoder overwrites the FEC area. As such, the sink receives the unscrambled AM and FEC fields, as illustrated in Figure 11-4. + +![Diagram of a 100G FlexO-1-RS frame structure after scrambling. The frame is shown as a grid with 128 rows and 5440 columns. The first 1280 columns are divided into AM (1-480), EOH (481-960), and BOH (961-1280) fields. The remaining columns (1281-5140) form the Payload area. The last 300 columns (5141-5440) form the FEC area. All fields from EOH onwards are highlighted in yellow, indicating they are scrambled. Bit counts are indicated at the bottom: 5140 bits for the payload area and 300 bits for the FEC area, totaling 5440 bits. The diagram is labeled G.709.5(24).](21ad58fee90f2be50708ff541d225507_img.jpg) + +Diagram of a 100G FlexO-1-RS frame structure after scrambling. The frame is shown as a grid with 128 rows and 5440 columns. The first 1280 columns are divided into AM (1-480), EOH (481-960), and BOH (961-1280) fields. The remaining columns (1281-5140) form the Payload area. The last 300 columns (5141-5440) form the FEC area. All fields from EOH onwards are highlighted in yellow, indicating they are scrambled. Bit counts are indicated at the bottom: 5140 bits for the payload area and 300 bits for the FEC area, totaling 5440 bits. The diagram is labeled G.709.5(24). + +**Figure 11-3 – 100G FlexO-1-RS frame after scrambling** + +![Diagram of a 100G FlexO-1-RS frame structure. The frame is shown as a grid of columns and rows. Columns are numbered 1, 480, 960, 1280, ..., 5140, 5440. Rows are numbered 1, 2, 3, ..., 128. The first row (Row 1) contains three fields: AM (Alignment Marker) from column 1 to 480, EOH (End of Header) from column 480 to 960, and BOH (Body of Header) from column 960 to 1280. The remaining part of Row 1 and all subsequent rows (Rows 2 to 128) form the 'Payload area', which extends from column 1 to 5140. The 'FEC area' is located to the right of the payload area, spanning from column 5140 to 5440. Below the grid, horizontal arrows indicate bit lengths: 5140 bits for the payload area, 300 bits for the FEC area, and a total of 5440 bits for the entire frame. The diagram is labeled G.709.5(24).](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Diagram of a 100G FlexO-1-RS frame structure. The frame is shown as a grid of columns and rows. Columns are numbered 1, 480, 960, 1280, ..., 5140, 5440. Rows are numbered 1, 2, 3, ..., 128. The first row (Row 1) contains three fields: AM (Alignment Marker) from column 1 to 480, EOH (End of Header) from column 480 to 960, and BOH (Body of Header) from column 960 to 1280. The remaining part of Row 1 and all subsequent rows (Rows 2 to 128) form the 'Payload area', which extends from column 1 to 5140. The 'FEC area' is located to the right of the payload area, spanning from column 5140 to 5440. Below the grid, horizontal arrows indicate bit lengths: 5140 bits for the payload area, 300 bits for the FEC area, and a total of 5440 bits for the entire frame. The diagram is labeled G.709.5(24). + +**Figure 11-4 – 100G FlexO-1-RS frame after AM field and FEC insertion** + +### 11.4 Forward error correction (FEC) + +The FlexO-1-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514) FEC code shall be computed as specified in Annex A. + +## 11.5 FOIC1.k-RS interface + +#### 11.5.1 FOIC1.4-RS interface + +A FlexO-1-RS structure is adapted over multi-channel parallel interfaces, using four ~28 Gbit/s physical lanes. No lane bit-multiplexing is performed. + +The alignment markers for the FlexO-1-RS are distributed on four FOIC1.4 lanes, resulting in 120 bits of data per lane. The alignment marker values are specified in clause 9. Each alignment marker has unique UMx and UPx values. The distribution of the four alignment markers to lanes 0, 1, 2 and 3, enables the unique values to be used for lane reordering in the sink function. The CMx values are replicated on all the four lanes to facilitate searching, alignment and the deskewing process. + +After the FEC encoding, the FlexO-1-RS frame is distributed to four logical FOIC1.4 lanes, in groups of 10-bits, in a round-robin distribution scheme from the lowest to the highest numbered lanes. This distribution is the inverse of the 10-bit interleaving of the AM field, such that each FOIC1.4 lane ends up with the correct AM, as illustrated in Table 11-3 where the transmission order is from left to right. + +NOTE 1 – The inverse multiplexing function is based on clause 91 [IEEE 802.3]. + +NOTE 2 – The mechanism is compatible and can reuse optical modules being developed for IEEE 100GBASE-LR4, -ER4 with OTU4 rate support. + +NOTE 3 – The electrical specifications for an FOIC1.4-RS 25G lane is in [b-OIF CEI]. + +**Table 11-3 – AM bit distribution over the four FOIC1.4-RS lanes** + +| AM bits | Lane 0 | Lane 1 | Lane 2 | Lane 3 | +|-----------|----------------------|----------------------|----------------------|----------------------| +| | 10-bit symbol of AM0 | 10-bit symbol of AM1 | 10-bit symbol of AM2 | 10-bit symbol of AM3 | +| 1 – 40 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 41 – 80 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 81 – 120 | 0100011011 | 0100001000 | 0100011000 | 0100010110 | +| 121 – 160 | 0110100110 | 0010100110 | 1010100110 | 1010100110 | + +**Table 11-3 – AM bit distribution over the four FOIC1.4-RS lanes** + +| AM bits | Lane 0 | Lane 1 | Lane 2 | Lane 3 | +|-----------|----------------------|----------------------|----------------------|----------------------| +| | 10-bit symbol of AM0 | 10-bit symbol of AM1 | 10-bit symbol of AM2 | 10-bit symbol of AM3 | +| 161 – 200 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 201 – 240 | 0110111001 | 0110111110 | 0110110111 | 0110110010 | +| 241 – 280 | 1011100000 | 0110010110 | 1111011111 | 0001011000 | +| 281 – 320 | 0010001110 | 1001111011 | 0011001111 | 0100000001 | +| 321 – 360 | 1100111101 | 0111111000 | 0110101010 | 0000101111 | +| 361 – 400 | 1001000111 | 0110011010 | 0000001000 | 0111101001 | +| 401 – 440 | 1111011100 | 0101100001 | 0011001100 | 1110111111 | +| 441 – 480 | 0100110000 | 0010000001 | 0010010101 | 1011110100 | + +NOTE – Transmission order of each 10-bit word is left-to-right (MSB first). The transmission order within the FlexO frame is left-to-right across the row and down the table. The transmission order for each lane is per-word and down the table. + +An FOIC1.4-RS interface comprises four OTSi. Specifications of the OTSi carrying a FOIC1.4-RS lane are contained in [ITU-T G.695] and [ITU-T G.959.1]. + +A group of m FOIC1.4-RS optical interfaces may be used to carry a digital client signal (e.g., an OTUCn may be carried over m FOIC1.4-RS optical interfaces). + +#### 11.5.2 FOIC1.4-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with (Chip to) 100 Gb/s attachment unit interface (CAUI4) [IEEE 802.3]. + +#### 11.5.3 FOIC1.4-RS 28G lane bit rate + +The FOIC1.4-RS lane is synchronous to the FlexO-1-RS frame. There are four lanes. + +The bit rate and tolerance of the FOIC1.4-RS lane signal is defined in Table 11-4. + +**Table 11-4 – FOIC1.4-RS lane rate** + +| FOIC1.4-RS nominal lane bit rate | Bit-rate tolerance | +|-------------------------------------------------------------------------|--------------------| +| 30592/27233 × 24 883 200 kbit/s | ±20 ppm | +| NOTE 1 – The nominal lane rate is approximately: 27 952 368.611 kbit/s. | | +| NOTE 2 – FOIC1.4-RS_lane_rate = 100G_FlexO-1-RS_rate/4. | | + +NOTE – The 100G FlexO-1-RS rate is specified in clause 11.2. + +This results in a FOIC1.4-RS lane bit rate with a -4.46 ppm offset from the optical transport lane OTL4.4 nominal bit rate. + +#### 11.5.4 FOIC1.1-RS interface + +A FlexO-1-RS is adapted over a single ~112 Gbit/s physical lane by first creating an FOIC1.4-RS as described in clause 11.5.1 and then bit multiplexing the four logical lanes into a FOIC1.1-RS. + +NOTE – The mechanism is compatible and can reuse optical modules with 100G per lane being developed for IEEE 100GBASE-FR1, -LR1, with 100G OTN rate support. + +#### 11.5.5 FOIC1.1-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with 100GAUI-1 [IEEE 802.3]. + +#### 11.5.6 FOIC1.1-RS 112G lane bit rate + +The single FOIC1.1-RS lane is synchronous to the FlexO-1-RS frame. + +The bit rate and tolerance of the FOIC1.1-RS lane signal is defined in Table 11-5. + +**Table 11-5 – FOIC1.1-RS lane rate** + +| FOIC1.1-RS nominal lane bit rate | Bit-rate tolerance | +|--------------------------------------------------------------------------|--------------------| +| $30592/27233 \times 99\,532\,800$ kbit/s | $\pm 20$ ppm | +| NOTE 1 – The nominal lane rate is approximately: 111 809 474.444 kbit/s. | | +| NOTE 2 – FOIC1.1-RS_lane_rate = 100G_FlexO-1-RS_rate. | | + +NOTE – The 100G FlexO-1-RS rate is specified in clause 11.2. + +# 12 200G FlexO-2-RS interface + +### 12.1 Frame structure + +The 200G FlexO-2-RS frame structure is shown in Figure 12-2 and consists of two 10-bit interleaved 100G FlexO frame structures in columns 1 to 10 280 and an FEC area in columns 10 281 to 10 880 in every row as illustrated in Figure 12-2. FlexO-2-RS interfaces use alignment markers as described in clause 9. + +NOTE – The 200G FlexO-2-RS frame structure is derived from 200 Gbit/s Ethernet clause 119 [IEEE 802.3] FEC alignment and lane architecture, without any 66b alignment or 256b/257b transcoding functions. + +For the case that a FlexO-2-RS-m group carries a FlexO-n with $n < 2m$ , the last FlexO-2-RS signal will contain only one equipped FlexO instance (see Figure 12-1). When a FlexO-2-RS contains fewer than 2 equipped instances, the equipped instance is the first 100G FlexO frame within this 200G FlexO-2-RS #m frame. The second 100G FlexO frame has its group identification (GID) field set to all-0s to indicate that it is unequipped. + +The following rules govern unequipped instances: + +- Unequipped instances must always be the highest numbered FlexO instance(s) in a FlexO-2-RS frame. +- There must always be at least one equipped instance in every FlexO-2-RS frame. + +![Figure 12-1: Two side-by-side diagrams of 100G FlexO frames. Each frame has 128 rows and 5140 columns. Row 1 is divided into AM (cols 1-480), EOH (cols 481-960), and BOH (cols 961-1280). The rest of the frame is the Payload area. The left diagram is for GID = FlexO Group #X. The right diagram is for GID = all-0's and labels the payload as 'Payload area with unequipped signal'. Dashed arrows point to the BOH section in both.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 12-1: Two side-by-side diagrams of 100G FlexO frames. Each frame has 128 rows and 5140 columns. Row 1 is divided into AM (cols 1-480), EOH (cols 481-960), and BOH (cols 961-1280). The rest of the frame is the Payload area. The left diagram is for GID = FlexO Group #X. The right diagram is for GID = all-0's and labels the payload as 'Payload area with unequipped signal'. Dashed arrows point to the BOH section in both. + +**Figure 12-1 – 100G FlexO frames within 200G FlexO-2-RS #m signal for case of partial fill** + +![Figure 12-2: Diagram of the 200G FlexO-2-RS frame structure. It consists of 128 rows and 10880 columns. Row 1 contains AM (cols 1-960), EOH (cols 961-1920), and BOH (cols 1921-2560). The Payload area spans columns 1 to 10280 across all rows. Columns 10281 to 10880 across all rows are designated as the RS FEC area, shown as a shaded block on the right side.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 12-2: Diagram of the 200G FlexO-2-RS frame structure. It consists of 128 rows and 10880 columns. Row 1 contains AM (cols 1-960), EOH (cols 961-1920), and BOH (cols 1921-2560). The Payload area spans columns 1 to 10280 across all rows. Columns 10281 to 10880 across all rows are designated as the RS FEC area, shown as a shaded block on the right side. + +**Figure 12-2 – 200G FlexO-2-RS frame structure** + +### 12.2 Bit rate and frame periods + +The bit rate and tolerance of the 200G FlexO-2-RS signal is defined in Table 12-1. + +**Table 12-1 – 200G FlexO-2-RS bit rate** + +| 200G FlexO-2-RS nominal bit rate | Bit-rate tolerance | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| $2 \times 30592/27233 \times 99\ 532\ 800$ kbit/s | $\pm 20$ ppm | +| NOTE 1 – The nominal 200G FlexO-2-RS bit rate is approximately: 223 618 948.893 kbit/s.
NOTE 2 – The 200G FlexO-2-RS bit rate can be based on the OTUC bit rate as follows: $2 \times 256/241 \times \text{OTUC bit rate} = 2 \times 256/241 \times 239/226 \times 99\ 532\ 800$ kbit/s. | | + +The frame and multi-frame periods of the 200G FlexO-2-RS signal are defined in Table 12-2. + +**Table 12-2 – 200G FlexO-2-RS frame and multi-frame periods** + +| Frame period (Note) | Multi-frame period (Note) | +|------------------------------------------------------------------------------|---------------------------| +| ~6.228 µs | 49.822 µs | +| NOTE – The period is an approximated value, rounded to three decimal places. | | + +### 12.3 Scrambling + +The operation of the 200G FlexO-2-RS scrambler is based on the interleaved 200G FlexO-2-RS frame structure shown in Figure 12-2 which is generated by the 10-bit interleaving of the two instances of 128 rows by 5 440 1-bit columns of the 200G FlexO-2-RS frame structure. + +The interleaved 200G FlexO-2-RS frame payload, fixed stuffing, basic overhead and extended overhead must be scrambled prior to transmission in order to provide DC balance and proper running disparity on the interface. The lane alignment markers ( $am_i$ , $i = 0, 1, 2, \dots, 7$ ) in the AM field are not scrambled and the chosen values have properties of already being DC balanced. Figure 12-3 below shows the scrambled parts of the frame as yellow. + +The operation of the scrambler shall be functionally equivalent to that of a frame-synchronous additive scrambler of sequence length 65 535 and the generating polynomial shall be $x^{16} + x^{12} + x^3 + x + 1$ . See Figure 11-3 of [ITU-T G.709] for an illustration of this scrambler. + +The scrambler operates on the entire frame, including the AM field and FEC area which contain undefined values when the frame is input to the scrambler. This is illustrated in Figure 12-3 where yellow indicates bits that are scrambled. The scrambler resets to 0xFFFF on the most significant (first transmitted) bit of the start of the FlexO-2-RS frame. The scrambler state advances during each bit of the frame. In the source function, the alignment markers are inserted into the AM field after scrambling and prior to FEC encoding. The FEC encoder overwrites the FEC area. As such, the sink receives unscrambled AM and FEC fields, as illustrated in Figure 12-4. + +![Diagram of a 200G FlexO-2-RS frame structure after scrambling. The frame is shown as a grid of 128 rows and 10880 columns. The first 960 columns are labeled 'AM' (Alignment Markers). The next 960 columns (961-1920) are labeled 'EOH' (Extended Overhead). The next 600 columns (1921-2520) are labeled 'BOH' (Basic Overhead). The remaining columns (2521-10280) are labeled 'Payload area'. The last 600 columns (10281-10880) are labeled 'FEC area'. The entire frame is highlighted in yellow, indicating it is scrambled. Below the grid, horizontal arrows indicate bit counts: 10280 bits for the payload area, 600 bits for the FEC area, and a total of 10880 bits for the entire frame. The diagram is labeled 'G.709.5(24)'.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Diagram of a 200G FlexO-2-RS frame structure after scrambling. The frame is shown as a grid of 128 rows and 10880 columns. The first 960 columns are labeled 'AM' (Alignment Markers). The next 960 columns (961-1920) are labeled 'EOH' (Extended Overhead). The next 600 columns (1921-2520) are labeled 'BOH' (Basic Overhead). The remaining columns (2521-10280) are labeled 'Payload area'. The last 600 columns (10281-10880) are labeled 'FEC area'. The entire frame is highlighted in yellow, indicating it is scrambled. Below the grid, horizontal arrows indicate bit counts: 10280 bits for the payload area, 600 bits for the FEC area, and a total of 10880 bits for the entire frame. The diagram is labeled 'G.709.5(24)'. + +**Figure 12-3 – 200G FlexO-2-RS frame after scrambling** + +![Diagram of a 200G FlexO-2-RS frame structure showing columns (1 to 10880) and rows (1 to 128). Row 1 contains AM, EOH, and BOH fields. Rows 2-128 contain the Payload area. The frame ends with an FEC area. Bit counts are 10280 for the payload and 600 for the FEC, totaling 10880 bits.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +The diagram illustrates the structure of a 200G FlexO-2-RS frame. It is organized into columns and rows. Columns are numbered 1, 960, 1920, 2560, ..., 10280, and 10880. Rows are numbered 1, 2, 3, ..., 128. Row 1 is divided into three fields: AM (Alignment Marker) from column 1 to 960, EOH (End of Hyperframe) from column 961 to 1920, and BOH (Basis Overhead) from column 1921 to 2560. Rows 2 through 128 are part of the 'Payload area', which extends from column 1 to 10280. The 'FEC area' (Forward Error Correction) occupies the remaining columns from 10281 to 10880 across all rows. Below the grid, horizontal arrows indicate bit counts: 10280 bits for the payload area and 600 bits for the FEC area, totaling 10880 bits. The reference G.709.5(24) is noted at the bottom right. + +Diagram of a 200G FlexO-2-RS frame structure showing columns (1 to 10880) and rows (1 to 128). Row 1 contains AM, EOH, and BOH fields. Rows 2-128 contain the Payload area. The frame ends with an FEC area. Bit counts are 10280 for the payload and 600 for the FEC, totaling 10880 bits. + +**Figure 12-4 – 200G FlexO-2-RS frame after AM field and FEC insertion** + +### 12.4 Forward error correction (FEC) + +The FlexO-2-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514) FEC code shall be computed as specified in Annex A. + +### 12.5 FOIC2.k-RS interface + +#### 12.5.1 FOIC2.4-RS interface + +The FlexO-2-RS structure is adapted over multi-channel parallel interfaces, using four ~56 Gbit/s physical lanes. + +The alignment markers for the FlexO-2-RS are distributed on eight logical FOIC2.4 lanes, resulting in 120 bits of data per logical lane. The alignment marker values are specified in clause 9. Each alignment marker has unique UMx and UPx values. The distribution of the eight alignment markers to lanes 0, 1, 2 to 7, enables the unique values to be used for lane reordering in the sink function. The CMx values are replicated on all eight lanes to facilitate the searching, alignment and deskewing process. + +After the FEC encoding the FlexO-2-RS frame (see Annex A), each set of two sub-rows (i.e., two FEC codewords) are interleaved on a 10-bit basis and then distributed to eight logical lanes in a round-robin distribution scheme from the lowest to the highest numbered lanes. The specific scheme of interleaving and distribution is specified in clause 119.2.4.7 of [IEEE 802.3] for 200GBASE-R interface and is designed to ensure that the correct alignment marker appears in each of the eight lanes. The resulting per-lane transmitted values of the alignment markers are illustrated in Table 12-3 where the transmission order is from left to right. + +The four physical lanes of a FOIC2.4-RS interface are generated by bit multiplexing pairs of logical lanes, e.g., bit multiplexing of lane 0 and lane 1, lane 2 and lane 3, lane 4 and lane 5, lane 6 and lane 7. + +NOTE – The mechanism is compatible and can reuse optical modules being developed for IEEE 200GBASE-FR4, -LR4, -ER4 with 200G OTN rate support. + +**Table 12-3 – AM bit distribution over the eight logical lanes** + +| AM bits | Lane 0
10-bit
symbol of
AM0 | Lane 1
10-bit
symbol of
AM1 | Lane 2
10-bit
symbol of
AM2 | Lane 3
10-bit
symbol of
AM3 | Lane 4
10-bit
symbol of
AM4 | Lane 5
10-bit
symbol of
AM5 | Lane 6
10-bit
symbol of
AM6 | Lane 7
10-bit
symbol of
AM7 | +|-----------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------|--------------------------------------| +| 1 - 80 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 81 - 160 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 161 - 240 | 0100101000 | 0100001000 | 0100011000 | 0100010110 | 0100100001 | 0100010011 | 0100101111 | 0100010001 | +| 241 - 320 | 0010100110 | 0010100110 | 1010100110 | 1010100110 | 1110100110 | 1110100110 | 0010100110 | 0010100110 | +| 321 - 400 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 401 - 480 | 0110110110 | 0110111110 | 0110110111 | 0110110010 | 0110111001 | 0110110111 | 0110110111 | 0110110100 | +| 481 - 560 | 1011110011 | 0110010110 | 1111011111 | 0001011000 | 1000010101 | 0010010010 | 0111010000 | 1100011010 | +| 561 - 640 | 0100000011 | 1001111011 | 0011001111 | 0100000001 | 0010001010 | 0011110010 | 1000111001 | 1101101110 | +| 641 - 720 | 0011000110 | 0111111000 | 0110101010 | 0000101111 | 0100111101 | 1000101110 | 1000010110 | 1101101010 | +| 721 - 800 | 0101000011 | 0110011010 | 0000001000 | 0111101001 | 1001111010 | 0011011011 | 0010001011 | 1100111001 | +| 801 - 880 | 0010111111 | 0101100001 | 0011001100 | 1110111111 | 1011011101 | 0111000011 | 1101110001 | 0100100100 | +| 881 - 960 | 0011001110 | 0010000001 | 0010010101 | 1011110100 | 0110110000 | 0101110100 | 1001111010 | 0100100101 | + +NOTE – Transmission order of each 10-bit word is left-to-right (MSB first). The transmission order within the FlexO frame is left-to-right across the row and down the table. The transmission order for each lane is per-word and down the table. + +An FOIC2.4-RS interface comprises four OTSi. Specifications of the OTSi carrying a FOIC2.4-RS lane are contained in [ITU-T G.695] and [ITU-T G.959.1]. + +A group of m FOIC2.4-RS optical interfaces may be used to carry a digital client signal (e.g., an OTUCn may be carried over m FOIC2.4-RS optical interfaces). + +#### 12.5.2 FOIC2.4-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with 200GAUI-4 [IEEE 802.3]. + +#### 12.5.3 FOIC2.4-RS 56G lane bit rate + +The FOIC2.4-RS lane is synchronous to the FlexO-2-RS frame. There are four lanes. + +The bit rate and tolerance of the FOIC2.4-RS lane signal is defined in Table 12-4. + +**Table 12-4 – FOIC2.4-RS lane rate** + +| FOIC2.4-RS nominal lane bit rate | Bit-rate tolerance | +|----------------------------------|--------------------| +| 30592/27233 × 49 766 400 kbit/s | ±20 ppm | + +NOTE 1 – The nominal FOIC2.4-RS lane rate is approximately: 55 904 737.223 kbit/s. + +NOTE 2 – FOIC2.4-RS\_lane\_rate = 200G\_FlexO-2-RS\_rate/4. + +NOTE – The 200G FlexO-2-RS bit rate is specified in clause 12.2. + +#### 12.5.4 FlexO-2-RS interface processes + +Figure 12-5 shows the processes of a FlexO-2-RS interface. The dashed lines in the Figure divide into processes that are reused from FlexO-1, processes that are unique to FlexO-2-RS, and processes that are reused from 200GBASE-R. The FOIC2.4 completely reuses all the processes from the 200GBASE-R PCS below the alignment insertion/removal processes, as well as the PMA and the PMD. + +![Diagram of 200G FlexO-2-RS interface processes showing data flow from OTUCn down to FOIC2.4-RS and back up. The diagram is divided into two main columns: the transmit path (left) and the receive path (right). The transmit path starts with OTUCn, splits into OTUC #1 and OTUC #2, applies 16-byte sync mapping, maps to 100G FlexO #1 and #2, inserts OH, interleaves, scrambles, inserts AM, distributes, encodes with RS(544, 514), muxes, and finally 2:1 bit mux to FOIC2.4-RS. The receive path reverses these steps: 1:2 bit demux, AM lock, lane deskew, decode RS(544, 514), remove AM, descramble, de-interleave, extract OH, reorder, demap from 100G FlexO, frame alignment, OTUC deskew, and back to OTUCn. Dashed lines separate FlexO-n reference point, 10-bit interleaved multiplex, and 10-bit round-robin distribution sections. Annotations indicate reused processes from FlexO-1 or 200GBASE-R and new designs for FOIC2.4.](552265bdbcf6d43d341fd018a9076269_img.jpg) + +The diagram illustrates the data flow for the 200G FlexO-2-RS interface, divided into transmit (left) and receive (right) paths. + +**Transmit Path (Top to Bottom):** + +- OTUCn** splits into **OTUC #1** and **OTUC #2**. +- Both undergo **16-Byte Sync Mapping**. +- Then **Map to 100G FlexO #1** and **Map to 100G FlexO #2** (labeled "Reuse 100G FlexO Process"). +- At the **FlexO-n reference point**, **100G FlexO OH insert (Reserved 480 bits AM placeholder)** is performed. +- Next is **10-bit interleaved multiplex**. +- Then **Scrambler (200G FlexO)**. +- Then **AM insertion** (labeled "New design"). +- Next is **10-bit round-robin distribution**. +- Then **RS(544, 514) encode (100G FlexO #1) FEC sub-row #1** and **RS(544, 514) encode (100G FlexO #2) FEC sub-row #2**. +- Then **Mux and 10-bit symbol distribution** (labeled "Reuse 200GBASE-R PCS/FEC"). +- Finally, **2:1 bit mux** outputs to **FOIC2.4-RS** via lanes **AMI** through **AM8**. + +**Receive Path (Bottom to Top):** + +- FOIC2.4-RS** inputs to **1:2 bit demux**. +- Outputs go through **AM lock** blocks. +- Then **Lane deskew, reorder and de-interleave**. +- Then **RS(544, 514) decode (100G FlexO #1) FEC sub-row #1** and **RS(544, 514) decode (100G FlexO #2) FEC sub-row #2**. +- Then **AM removal** (labeled "New design"). +- Then **Descrambler (200G FlexO)**. +- Next is **100G FlexO OH extract**. +- Then **FlexO-n reorder**. +- Then **Demap from 100G FlexO #1** and **Demap from 100G FlexO #2**. +- Then **Frame/multiframe alignment**. +- Then **OTUC deskew**. +- Finally, data is reassembled into **OTUCn**, with "The remainder OTUCs to m-1 200G FlexO lanes" indicated. + +**Annotations:** + +- FlexO-n reference point**: Located between the mapping and OH insert stages. +- 10-bit interleaved multiplex**: Located between the OH insert and scrambler stages. +- 10-bit round-robin distribution**: Located between the AM insertion and RS encode stages. +- New design**: Refers to the AM insertion and AM removal stages. +- Reuse 100G FlexO Process**: Refers to the mapping stages. +- Reuse 200GBASE-R PCS/FEC**: Refers to the mux and symbol distribution stage. +- The remainder OTUCs to m-1 200G FlexO lanes**: Indicated at the top and bottom of the diagram. +- FOIC2.4-RS**: The final output stage on the transmit path. + +Diagram of 200G FlexO-2-RS interface processes showing data flow from OTUCn down to FOIC2.4-RS and back up. The diagram is divided into two main columns: the transmit path (left) and the receive path (right). The transmit path starts with OTUCn, splits into OTUC #1 and OTUC #2, applies 16-byte sync mapping, maps to 100G FlexO #1 and #2, inserts OH, interleaves, scrambles, inserts AM, distributes, encodes with RS(544, 514), muxes, and finally 2:1 bit mux to FOIC2.4-RS. The receive path reverses these steps: 1:2 bit demux, AM lock, lane deskew, decode RS(544, 514), remove AM, descramble, de-interleave, extract OH, reorder, demap from 100G FlexO, frame alignment, OTUC deskew, and back to OTUCn. Dashed lines separate FlexO-n reference point, 10-bit interleaved multiplex, and 10-bit round-robin distribution sections. Annotations indicate reused processes from FlexO-1 or 200GBASE-R and new designs for FOIC2.4. + +G.709.5(24) + +Figure 12-5 – 200G FlexO-2-RS interface processes + +# 13 400G FlexO-4-RS interface + +### 13.1 Frame structure + +The 400G FlexO-4-RS frame structure is shown in Figure 13-2 and consists of four 10-bit interleaved FlexO frame structure instances in columns 1 to 10 280 and an FEC area in columns 10 281 to 10 880 in every row as illustrated in Figure 13-2. FlexO-4-RS interfaces use alignment markers as described in clause 9. + +NOTE – The 400G FlexO-4-RS frame structure is derived from 400 Gbit/s Ethernet clause 119 [IEEE 802.3] FEC alignment and lane architecture, without any 66b alignment or 256b/257b transcoding functions. + +For the case that a FlexO-4-RS-m group carries a FlexO-n with $n < 4m$ , the last FlexO-4-RS signal will contain one, two, or three equipped FlexO instances (see Figure 13-1). When a FlexO-4-RS frame contains fewer than four equipped instances, these three, two or one instance(s) is (are) located in the first one, two or three 100G FlexO frame(s) within this 400G FlexO-4-RS #m frame. The last one, two or three 100G FlexO frames have their GID field set to all-0s to indicate that the 100G FlexO frame is unequipped. + +The same rules in clause 12.1 governing unequipped instances apply. + +![Figure 13-1: 100G FlexO frames within 400G FlexO-4-RS #m signal for case of partial fill. The diagram shows four frame structures labeled FlexO #1, FlexO #2, FlexO #3, and FlexO #4. Each frame has 128 rows and 5140 columns. Columns are divided into AM (1-480), EOH (481-960), BOH (961-1280), and a Payload area (1281-5140). FlexO #1 and #2 have 'GID = FlexO Group #X'. FlexO #3 and #4 have 'GID = all-0's'. FlexO #1 and #2 have 'Payload area equipped or unequipped signal'. FlexO #3 and #4 have 'Payload area with unequipped signal'.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +The diagram illustrates four 100G FlexO frames (FlexO #1, FlexO #2, FlexO #3, FlexO #4) within a 400G FlexO-4-RS #m signal. Each frame is represented as a grid with 128 rows and 5140 columns. The columns are divided into four segments: AM (columns 1 to 480), EOH (columns 481 to 960), BOH (columns 961 to 1280), and a Payload area (columns 1281 to 5140). The BOH segment contains a GID field. For FlexO #1 and FlexO #2, the GID is set to 'FlexO Group #X'. For FlexO #3 and FlexO #4, the GID is set to 'all-0's'. The payload area for FlexO #1 and FlexO #2 is labeled 'Payload area equipped or unequipped signal'. The payload area for FlexO #3 and FlexO #4 is labeled 'Payload area with unequipped signal'. + +Figure 13-1: 100G FlexO frames within 400G FlexO-4-RS #m signal for case of partial fill. The diagram shows four frame structures labeled FlexO #1, FlexO #2, FlexO #3, and FlexO #4. Each frame has 128 rows and 5140 columns. Columns are divided into AM (1-480), EOH (481-960), BOH (961-1280), and a Payload area (1281-5140). FlexO #1 and #2 have 'GID = FlexO Group #X'. FlexO #3 and #4 have 'GID = all-0's'. FlexO #1 and #2 have 'Payload area equipped or unequipped signal'. FlexO #3 and #4 have 'Payload area with unequipped signal'. + +Figure 13-1 – 100G FlexO frames within 400G FlexO-4-RS #m signal for case of partial fill + +![Diagram of 400G FlexO-4-RS frame structure showing columns (1, 1960, 3840, 5120, ..., 10280, 10880) and rows (1 to 256). Row 1 contains AM, EOH, and BOH fields. Rows 2-256 contain the payload area. A shaded 'RS FEC area' is shown on the right side of the frame.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +400G FlexO-4-RS G.709.5(24) + +Diagram of 400G FlexO-4-RS frame structure showing columns (1, 1960, 3840, 5120, ..., 10280, 10880) and rows (1 to 256). Row 1 contains AM, EOH, and BOH fields. Rows 2-256 contain the payload area. A shaded 'RS FEC area' is shown on the right side of the frame. + +**Figure 13-2 – 400G FlexO-4-RS frame structure** + +### **13.2 Bit rate and frame periods** + +The bit rate and tolerance of the 400G FlexO-4-RS signal is defined in Table 13-1. + +**Table 13-1 – 400G FlexO-4-RS bit rate** + +| 400G FlexO-4-RS nominal bit rate | Bit-rate tolerance | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| $4 \times 30592/27233 \times 99\,532\,800$ kbit/s | $\pm 20$ ppm | +| NOTE 1 – The nominal 400G FlexO-4-RS bit rate is approximately: 447 237 897.786 kbit/s. | | +| NOTE 2 – The 400G FlexO-4-RS bit rate can be based on the OTUC bit rate as follows: $4 \times 256/241 \times$ OTUC bit rate $= 4 \times 256/241 \times 239/226 \times 99\,532\,800$ kbit/s. | | + +The frame and multi-frame periods of the 400G FlexO-4-RS signal are defined in Table 13-2. + +**Table 13-2 – 400G FlexO-4-RS frame and multi-frame periods** + +| Frame period (Note) | Multi-frame period (Note) | +|------------------------------------------------------------------------------|---------------------------| +| $\sim 6.228$ $\mu$ s | $49.822$ $\mu$ s | +| NOTE – The period is an approximated value, rounded to three decimal places. | | + +### **13.3 Scrambling** + +The operation of the 400G FlexO-4-RS scrambler is based on the interleaved 400G FlexO-4-RS frame structure shown in Figure 13-2 which is generated by 10-bit multiplexing of the two instances of 256 rows by 5 440 1-bit columns of the 400G FlexO-4-RS frame structure. + +The interleaved 400G FlexO-4-RS frame payload, fixed stuffing, basic overhead and extended overhead must be scrambled prior to transmission in order to provide DC balance and proper running disparity on the interface. The lane alignment markers ( $am_i$ , $i = 0, 1, 2, \dots, 15$ ) in the AM field are not scrambled and the chosen values have properties of already being DC balanced. Figure 13-4 below shows the scrambled parts of the frame as yellow. + +The operation of the scrambler shall be functionally equivalent to that of a frame-synchronous scrambler of sequence 65 535 and the generating polynomial shall be $x^{16} + x^{12} + x^3 + x + 1$ . See Figure 11-3 of [ITU-T G.709] for an illustration of this scrambler. + +The scrambler operates on the entire frame, including the AM field and the FEC area which contain undefined values when the frame is input to the scrambler. This is illustrated in Figure 13-3 where yellow indicates bits that are scrambled. The scrambler resets to 0xFFFF on the most significant (first transmitted) bit of the start of the FlexO-4-RS frame. The scrambler state advances during each bit of + +the frame. In the source function, the alignment markers are inserted into the AM field after scrambling and prior to FEC encoding. The FEC encoder overwrites the FEC area. As such, the sink receives unscrambled AM and FEC fields, as illustrated in Figure 13-4. + +![Figure 13-3: 400G FlexO-4-RS frame after scrambling. The diagram shows a grid of 256 rows and 10880 columns. Row 1 contains AM (columns 1-1960), EOH (1961-3840), and BOH (3841-5120). Rows 2-256 contain the Payload area (columns 1-10280) and FEC area (columns 10281-10880). Horizontal arrows at the bottom indicate 10280 bits for the payload and 600 bits for the FEC area, totaling 10880 bits. The label G.709.5(24) is in the bottom right.](d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg) + +Figure 13-3: 400G FlexO-4-RS frame after scrambling. The diagram shows a grid of 256 rows and 10880 columns. Row 1 contains AM (columns 1-1960), EOH (1961-3840), and BOH (3841-5120). Rows 2-256 contain the Payload area (columns 1-10280) and FEC area (columns 10281-10880). Horizontal arrows at the bottom indicate 10280 bits for the payload and 600 bits for the FEC area, totaling 10880 bits. The label G.709.5(24) is in the bottom right. + +Figure 13-3 – 400G FlexO-4-RS frame after scrambling + +![Figure 13-4: 400G FlexO-4-RS frame after AM field and FEC insertion. This diagram is identical to Figure 13-3, showing the same frame structure with 256 rows and 10880 columns. Row 1 has AM, EOH, and BOH. Rows 2-256 have Payload and FEC areas. Arrows indicate 10280 bits for payload and 600 bits for FEC. The label G.709.5(24) is in the bottom right.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Figure 13-4: 400G FlexO-4-RS frame after AM field and FEC insertion. This diagram is identical to Figure 13-3, showing the same frame structure with 256 rows and 10880 columns. Row 1 has AM, EOH, and BOH. Rows 2-256 have Payload and FEC areas. Arrows indicate 10280 bits for payload and 600 bits for FEC. The label G.709.5(24) is in the bottom right. + +Figure 13-4 – 400G FlexO-4-RS frame after AM field and FEC insertion + +### 13.4 Forward error correction (FEC) + +The FlexO-4-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514) FEC code shall be computed as specified in Annex A. + +### 13.5 FOIC4.k-RS interface + +#### 13.5.1 FOIC4.8-RS interface + +The FlexO-4-RS structure is adapted over multi-channel parallel interfaces, using eight ~56 Gbit/s physical lanes. + +The alignment markers for the FlexO-4-RS are distributed on sixteen lanes, resulting in 120 bits of data per lane. The alignment marker values are specified in clause 9. Each alignment marker has unique UMx and UPx values. The distribution of the sixteen alignment markers to lanes 0, 1, 2 to 15, enables the unique values to be used for lane reordering in the sink function. The CMx values are replicated on all the sixteen lanes to facilitate the searching, alignment and deskewing process. + +After the FEC encoding the FlexO-4-RS frame (see Annex A), each set of two sub-rows (i.e., two FEC codewords) are interleaved on a 10-bit basis and then distributed to eight logical lanes in a round-robin distribution scheme from the lowest to the highest numbered lanes. + +The specific scheme of interleaving and distribution is specified in clause 119.2.4.7 of [IEEE 802.3] for 400GBASE-R interface and is designed to ensure that the correct alignment marker appears in each of the 16 lanes. The resulting per-lane transmitted values of the alignment markers are illustrated in Table 13-3 where the transmission order is from left to right. + +The eight lanes of a FOIC4.8-RS interface are generated by bit multiplexing pairs of logical lanes, e.g., bit multiplexing of lane 0 and lane 1, lane 2 and lane 3, lane 4 and lane 5, lane 6 and lane 7, lane 8 and lane 9, lane 10 and lane 11, lane 12 and lane 13, lane 14 and lane 15. + +NOTE – The mechanism is compatible and can reuse optical modules being developed for IEEE 400GBASE-FR8, -LR8, -ER8 with 400G OTN rate support. + +**Table 13-3 – AM bit distribution over the sixteen logical lanes** + +| AM bits | Lane 0
10-bit symbol of AM0 | Lane 1
10-bit symbol of AM1 | Lane 2
10-bit symbol of AM2 | Lane 3
10-bit symbol of AM3 | Lane 4
10-bit symbol of AM4 | Lane 5
10-bit symbol of AM5 | Lane 6
10-bit symbol of AM6 | Lane 7
10-bit symbol of AM7 | +|-------------|--------------------------------|--------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------| +| 1 - 80 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 161 - 240 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 321 - 400 | 0100011011 | 0100001000 | 0100011000 | 0100010110 | 0100100001 | 0100010011 | 0100101111 | 0100010001 | +| 481 - 560 | 0110100110 | 0010100110 | 1010100110 | 1010100110 | 1110100110 | 1110100110 | 0010100110 | 0010100110 | +| 641 - 720 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 801 - 880 | 0110111001 | 0110111110 | 0110110111 | 0110110010 | 0110111001 | 0110110111 | 0110110111 | 0110110100 | +| 961 - 1 040 | 1011100000 | 0110010110 | 1111011111 | 0001011000 | 1000010101 | 0010010010 | 0111010000 | 1100011010 | +| 1121 - 1200 | 0010001110 | 1001111011 | 0011001111 | 0100000001 | 0010001010 | 0011110010 | 1000111001 | 1101101110 | +| 1281 - 1360 | 1100111101 | 0111111000 | 0110101010 | 0000101111 | 0100111101 | 1000101110 | 1000010110 | 1101101010 | +| 1441 - 1520 | 1001000111 | 0110011010 | 0000001000 | 0111101001 | 1001111010 | 0011011011 | 0010001011 | 1100111001 | +| 1601 - 1680 | 1111011100 | 0101100001 | 0011001100 | 1110111111 | 1011011101 | 0111000011 | 1101110001 | 0100100100 | +| 1761 - 1840 | 0100110000 | 0010000001 | 0010010101 | 1011110100 | 0110110000 | 0101110100 | 1001111010 | 0100100101 | +| AM bits | Lane 8
10-bit symbol of AM8 | Lane 9
10-bit symbol of AM9 | Lane 10
10-bit symbol of AM10 | Lane 11
10-bit symbol of AM11 | Lane 12
10-bit symbol of AM12 | Lane 13
10-bit symbol of AM13 | Lane 14
10-bit symbol of AM14 | Lane 15
10-bit symbol of AM15 | +| 81 - 160 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 241 - 320 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 401 - 480 | 0100000001 | 0100110101 | 0100010111 | 0100001101 | 0100000110 | 0100001010 | 0100000010 | 0100001011 | +| 561 - 640 | 1010100110 | 1010100110 | 1110100110 | 1010100110 | 0010100110 | 0010100110 | 1110100110 | 0110100110 | +| 721 - 800 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 881 - 960 | 0110111111 | 0110110100 | 0110110010 | 0110111000 | 0110111101 | 0110110011 | 0110111000 | 0110110110 | +| 1041 - 1120 | 1001100001 | 0101100011 | 0000101010 | 1110010001 | 1010010001 | 0011100011 | 1101010100 | 1010011001 | +| 1201 - 1280 | 1111001110 | 1000100011 | 0111010111 | 0001100110 | 0101101111 | 0011101001 | 1111011111 | 0101011101 | +| 1361 - 1440 | 1010111000 | 0011110010 | 0001101111 | 0001110001 | 1010100100 | 1100001111 | 0110010101 | 1001111010 | +| 1521 - 1600 | 0001100111 | 1110100111 | 0111110101 | 1100011011 | 1001011011 | 0011000111 | 1100101010 | 0101011001 | +| 1681 - 1760 | 1000001100 | 0001110111 | 0110001010 | 1011100110 | 1010100100 | 0011000101 | 1100001000 | 1010101000 | +| 1841 - 1920 | 0101010001 | 0011000011 | 0011100100 | 0111100011 | 0001010110 | 1000111100 | 0010011010 | 1001100001 | + +NOTE – Transmission order of each 10-bit word is left-to-right (MSB first). The transmission order within the FlexO frame is left-to-right across the row and down the Table. The transmission order for each lane is per-word and down the Table. + +An FOIC4.8-RS interface comprises eight OTSi. Specifications of the OTSi carrying a FOIC4.8-RS lane are contained in [ITU-T G.695] and [ITU-T G.959.1]. + +A group of m FOIC4.8-RS optical interfaces may be used to carry a digital client signal (e.g., an OTUCn may be carried over m FOIC4.8-RS optical interfaces). + +#### 13.5.2 FOIC4.8-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with 400GAUI-4 [IEEE 802.3]. + +#### 13.5.3 FOIC4.8-RS 56G lane bit rate + +The FOIC4.8-RS lane is synchronous to the FlexO-4-RS frame. There are eight lanes. + +The bit rate and tolerance of the FOIC4.8-RS lane signal is defined in Table 13-4. + +**Table 13-4 – FOIC4.8-RS lane rate** + +| FOIC4.8-RS nominal lane bit rate | Bit-rate tolerance | +|------------------------------------------------------------------------------------|---------------------------| +| 30592/27233 × 49 766 400 kbit/s | ±20 ppm | +| NOTE 1 – The nominal FOIC4.8-RS lane rate is approximately: 55 904 737.223 kbit/s. | | +| NOTE 2 – FOIC4.8-RS_lane_rate = 400G_FlexO-4-RS_rate/8. | | + +NOTE – The 400G FlexO-4-RS bit rate is specified in clause 13.2. + +#### 13.5.4 FlexO-4-RS interface processes + +Figure 13-5 shows the processes of a FlexO-4-RS interface. The dashed lines in the figure divide into processes that are reused from FlexO-1, processes that are unique to FlexO-4-RS, and processes that are reused from 400GBASE-R. The FOIC4.8 completely reuses all the processes from the 400GBASE-R PCS below the alignment insertion/removal processes, as well as the PMA and the PMD. + +![Figure 13-5 – 400G FlexO-4-RS interface processes. This diagram illustrates the data flow and processing steps for a 400G FlexO-4-RS interface, divided into transmit (left) and receive (right) paths. The transmit path starts with OTUCn, which is split into four OTUCs (OTUC #1 to #4). These are processed through 16-byte sync mapping, resulting in four 100G FlexO streams. Each stream undergoes frame alignment, OH insertion (with reserved AM placeholders), 10-bit interleaved multiplexing, scrambling, AM insertion, 10-bit round-robin distribution, RS(544, 514) encoding, and finally a 2:1 bit mux to produce the FOIC4.8-RS output. The receive path reverses these steps: starting from a 1:2 bit demux, followed by lane deskew, RS decoding, AM removal, descrambling, 10-bit interleaved demultiplexing, OH extraction, and frame/multiframe alignment to reconstruct the OTUCs. Various processing blocks are labeled as 'New design' or 'Reuse 400G PCS/FEC'.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Figure 13-5 – 400G FlexO-4-RS interface processes. This diagram illustrates the data flow and processing steps for a 400G FlexO-4-RS interface, divided into transmit (left) and receive (right) paths. The transmit path starts with OTUCn, which is split into four OTUCs (OTUC #1 to #4). These are processed through 16-byte sync mapping, resulting in four 100G FlexO streams. Each stream undergoes frame alignment, OH insertion (with reserved AM placeholders), 10-bit interleaved multiplexing, scrambling, AM insertion, 10-bit round-robin distribution, RS(544, 514) encoding, and finally a 2:1 bit mux to produce the FOIC4.8-RS output. The receive path reverses these steps: starting from a 1:2 bit demux, followed by lane deskew, RS decoding, AM removal, descrambling, 10-bit interleaved demultiplexing, OH extraction, and frame/multiframe alignment to reconstruct the OTUCs. Various processing blocks are labeled as 'New design' or 'Reuse 400G PCS/FEC'. + +G.709.5(24) + +Figure 13-5 – 400G FlexO-4-RS interface processes + +#### 13.5.5 FOIC4.4-RS interface + +The FlexO-4-RS structure is adapted over multi-channel parallel interfaces, using four ~112 Gbit/s physical lanes. + +The four lanes of a FOIC4.4-RS interface are generated by bit multiplexing groups of four logical lanes, e.g., bit multiplexing of lane 0, lane 1, lane 2 and lane 3 (physical lane 0); and lane 4, lane 5, lane 6 and lane 7 (physical lane 1); and lane 8, lane 9, lane 10 and lane 11 (physical lane 2); and lane 12, lane 13, lane 14 and lane 15 (physical lane 3). The logical lanes and alignment marker values are identical to the sixteen logical lanes of FOIC4.8-RS as defined in clauses 13.5.1. + +NOTE – The mechanism is compatible and can reuse optical modules with 100G per lane being developed for IEEE 400GBASE-FR4, -LR4-6 with 400G OTN rate support. + +#### 13.5.6 FOIC4.4-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with 400GAUI-4 [IEEE 802.3]. + +#### 13.5.7 FOIC4.4-RS 112G lane bit rate + +The FOIC4.4-RS lane is synchronous to the FlexO-4-RS frame. There are four lanes. + +The bit rate and tolerance of the FOIC4.4-RS lane signal is defined in Table 13-5. + +**Table 13-5 – FOIC4.4-RS lane rate** + +| FOIC4.4-RS nominal lane bit rate | Bit-rate tolerance | +|--------------------------------------------------------------------------|--------------------| +| 30592/27233 × 99 532 800 kbit/s | ±20 ppm | +| NOTE 1 – The nominal lane rate is approximately: 111 809 474.444 kbit/s. | | +| NOTE 2 – FOIC4.4-RS_lane_rate = 400G_FlexO-4-RS_rate/4. | | + +NOTE – The 400G FlexO-4-RS rate is specified in clause 13.2. + +# 14 800G FlexO-8-RS interface + +### 14.1 Frame structure + +The 800G FlexO-8-RS frame structure is shown in Figure 14-2 and consists of eight 10-bit interleaved FlexO frame structure instances in columns 1 to 10 280 and an FEC area in columns 10 281 to 10 880 in every row. FlexO-8-RS interfaces use alignment markers as described in clause 9. + +NOTE – The 800G FlexO-8-RS frame structure is derived from 800 Gbit/s Ethernet clause 172 [IEEE 802.3df] FEC alignment and lane architecture, without any 66b alignment or 256b/257b transcoding functions. + +For the case that a FlexO-8-RS-m group carries a FlexO-n with n < 8m, the last FlexO-8-RS signal will contain from one to seven equipped FlexO instances (see Figure 14-1). When a FlexO-8-RS frame contains fewer than eight equipped instances, these instance(s) is (are) located in the first 1 to 7 100G FlexO frame(s) within this 800G FlexO 8-RS #m frame. The last 1 to 7 100G FlexO frames have their GID field set to all-0s to indicate that the 100G FlexO frame is unequipped. + +![Figure 14-1: 100G FlexO frames within 800G FlexO-8-RS #m signal for case of partial fill. The diagram shows eight frame instances. The first seven are equipped with signals (Payload area equipped or unequipped signal), and the eighth is unequipped (Payload area with unequipped signal). Each frame has columns 1, 480, 960, 1280, ..., 5140. Rows 1, 2, 3, ..., 128 are shown. Each frame has AM, EOH, and BOH fields. The GID field is FlexO-Group #X or GID = all-0's.](e1476fd216f6cf773e262013fb4aba7d_img.jpg) + +The diagram illustrates the structure of 100G FlexO frames within an 800G FlexO-8-RS #m signal for a case of partial fill. It shows eight frame instances arranged horizontally. Each instance has a header with columns 1, 480, 960, 1280, ..., 5140 and rows 1, 2, 3, ..., 128. The first seven instances are equipped with signals, indicated by the text 'Payload area equipped or unequipped signal'. The eighth instance is unequipped, indicated by the text 'Payload area with unequipped signal'. Each frame has an alignment marker (AM), end of header (EOH), and beginning of header (BOH) fields. The GID field is set to FlexO-Group #X or GID = all-0's. The last frame (the eighth one) has its GID field set to all-0's to indicate it is unequipped. + +Figure 14-1: 100G FlexO frames within 800G FlexO-8-RS #m signal for case of partial fill. The diagram shows eight frame instances. The first seven are equipped with signals (Payload area equipped or unequipped signal), and the eighth is unequipped (Payload area with unequipped signal). Each frame has columns 1, 480, 960, 1280, ..., 5140. Rows 1, 2, 3, ..., 128 are shown. Each frame has AM, EOH, and BOH fields. The GID field is FlexO-Group #X or GID = all-0's. + +G.709.5(24) + +**Figure 14-1 – 100G FlexO frames within 800G FlexO-8-RS #m signal for case of partial fill** + +![Figure 14-2 – 800G FlexO-8-RS frame structure diagram. The diagram shows a grid of columns and rows. Columns are numbered 1, 3840, 7680, 10240, 10280, and 10880. Rows are numbered 1, 2, 3, ..., 512. The first row (Row 1) is divided into three sections: AM (columns 1 to 3840), EOH (columns 3840 to 7680), and BOH (columns 7680 to 10240). Rows 2 through 512 are labeled 'Payload area'. A large grey rectangular area on the right, spanning from column 10280 to 10880 and rows 1 to 512, is labeled 'RS FEC area'. The text 'G.709.5(24)' is at the bottom right.](08dce7ad4c512fdf0c0cde60415fade6_img.jpg) + +Figure 14-2 – 800G FlexO-8-RS frame structure diagram. The diagram shows a grid of columns and rows. Columns are numbered 1, 3840, 7680, 10240, 10280, and 10880. Rows are numbered 1, 2, 3, ..., 512. The first row (Row 1) is divided into three sections: AM (columns 1 to 3840), EOH (columns 3840 to 7680), and BOH (columns 7680 to 10240). Rows 2 through 512 are labeled 'Payload area'. A large grey rectangular area on the right, spanning from column 10280 to 10880 and rows 1 to 512, is labeled 'RS FEC area'. The text 'G.709.5(24)' is at the bottom right. + +**Figure 14-2 – 800G FlexO-8-RS frame structure** + +### 14.2 Bit rate and frame periods + +The bit rate and tolerance of the 800G FlexO-8-RS signal is defined in Table 14-1. + +**Table 14-1 – 800G FlexO-8-RS bit rate** + +| 800G FlexO-8-RS nominal bit rate | Bit-rate tolerance | +|---------------------------------------------------|--------------------| +| $8 \times 30592/27233 \times 99\,532\,800$ kbit/s | $\pm 20$ ppm | + +NOTE 1 – The nominal 800G FlexO-8-RS bit rate is approximately: 894 475 795.571 kbit/s. +NOTE 2 – The 800G FlexO-8-RS bit rate can be based on the OTUC bit rate as follows: $8 \times 256/241 \times \text{OTUC bit rate} = 8 \times 256/241 \times 239/226 \times 99\,532\,800$ kbit/s. + +The frame and multi-frame periods of the 800G FlexO-8-RS signal are defined in Table 14-2. + +**Table 14-2 – 800G FlexO-8-RS frame and multi-frame periods** + +| Frame period (Note) | Multi-frame period (Note) | +|----------------------------|---------------------------| +| $\sim 6.228$ $\mu\text{s}$ | $49.822$ $\mu\text{s}$ | + +NOTE – The period is an approximated value, rounded to three decimal places. + +### 14.3 Scrambling + +The interleaved 800G FlexO-8-RS signal is carried in two 400G flows which are generated by 10-bit multiplexing of four 100G FlexO instances. Each 400G flow has a FlexO-4-RS frame structure as shown in Figure 13-2 and is individually scrambled as described in clause 13.3. + +### 14.4 Forward error correction (FEC) + +The FlexO-8-RS FEC area contains the Reed-Solomon RS(544,514) FEC codes. The RS(544,514) FEC code shall be computed as specified in Annex A. + +### 14.5 FOIC8.k-RS interface + +#### 14.5.1 FOIC8.8-RS interface + +The FlexO-8-RS structure is adapted over multi-channel parallel interfaces using eight $\sim 112$ Gbit/s physical lanes. + +The alignment markers for the FlexO-8-RS are distributed in two 400G flows and on sixteen lanes for each flow, resulting in 120 bits of data per lane and thirty-two lanes in total. The alignment marker + +values are specified in clause 9. Each alignment marker has unique UMx and UPx values. In flow #0, sixteen alignment markers are distributed to lanes 0, 1, 2 to 15. In flow #1, the other sixteen alignment markers are distributed to lanes 16, 17, 18 to 31. The unique values are used for lane reordering in the sink function. The CMx values are replicated on all thirty-two lanes to facilitate the searching, alignment and deskewing process. + +In each flow, after FEC encoding the FlexO-4-RS frame (see Annex A), each set of two sub-rows (i.e., two FEC codewords) are interleaved (not round-robin) on a 10-bit basis and then distributed to the 16 logical lanes in a round-robin distribution scheme from the lowest to the highest numbered lanes. + +The specific scheme of interleaving and distribution is specified in clause 172.2.4.7 of [IEEE 802.3df] for 800GBASE-R interface and is designed to ensure that the correct alignment marker appears in each of the thirty-two lanes. The resulting per lane transmitted values of the alignment markers are illustrated in Table 14-3 and Table 14-4 for both flows where the transmission order is from left to right. + +The eight physical lanes of a FOIC8.8-RS interface are generated by bit-level multiplexing groups of four logical lanes with an additional constraint that each of the eight physical lanes contains two logical lanes from lane 0 to lane 15 followed by two logical lanes from lane 16 to lane 31. + +This could be obtained for example (see Figure 14-3) by bit multiplexing the logical lanes as follows: + +- lane 0, lane 1, lane 16 and lane 17 into physical lane 0; +- lane 2, lane 3, lane 18 and lane 19 into physical lane 1; +- lane 4, lane 5, lane 20 and lane 21 into physical lane 2; +- lane 6, lane 7, lane 22 and lane 23 into physical lane 3; +- lane 8, lane 9, lane 24 and lane 25 into physical lane 4; +- lane 10, lane 11, lane 26 and lane 27 into physical lane 5; +- lane 12, lane 13, lane 28 and lane 29 into physical lane 6; +- lane 14, lane 15, lane 30 and lane 31 into physical lane 7. + +![Diagram illustrating 32:8 bit level multiplexing. At the top, 'Logic lanes' are shown for Flow #0 (lanes 0-15) and Flow #1 (lanes 16-31). Alignment markers AM0-AM2 are shown for Flow #0, and AM15-AM18 for Flow #1. Below the logic lanes, a '32:8 bit-level multiplex' section shows the interleaving of logical lanes into eight physical lanes. The bottom section shows the 'FOIC8.8-RS physical lanes' as eight vertical lines. The diagram uses colored dashed lines to represent the mapping of logical lanes to physical lanes, following the scheme described in the text. A reference label 'G.709.5(24)' is in the bottom right corner.](a1890b9a9b85f13e67ed59bbad623659_img.jpg) + +Diagram illustrating 32:8 bit level multiplexing. At the top, 'Logic lanes' are shown for Flow #0 (lanes 0-15) and Flow #1 (lanes 16-31). Alignment markers AM0-AM2 are shown for Flow #0, and AM15-AM18 for Flow #1. Below the logic lanes, a '32:8 bit-level multiplex' section shows the interleaving of logical lanes into eight physical lanes. The bottom section shows the 'FOIC8.8-RS physical lanes' as eight vertical lines. The diagram uses colored dashed lines to represent the mapping of logical lanes to physical lanes, following the scheme described in the text. A reference label 'G.709.5(24)' is in the bottom right corner. + +**Figure 14-3 – Example of 32:8 bit level multiplexing** + +NOTE – The mechanism is compatible and can reuse the optical modules being developed for IEEE 800GBASE-FR4(IM-DD) and 800GBASE-LR1/ER1(coherent), with 800G OTN rate support. + +**Table 14-3 – AM bit distribution over the sixteen logical lanes of flow #0** + +| AM bits | Lane 0
10-bit
symbol of
AM0 | Lane 1
10-bit
symbol of
AM1 | Lane 2
10-bit
symbol of
AM2 | Lane 3
10-bit
symbol of
AM3 | Lane 4
10-bit
symbol of
AM4 | Lane 5
10-bit
symbol of
AM5 | Lane 6
10-bit
symbol of
AM6 | Lane 7
10-bit
symbol of
AM7 | +|----------------|------------------------------------------------|------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------| +| 1 - 80 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 161 - 240 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 321 - 400 | 0100011011 | 0100001000 | 0100011000 | 0100010110 | 0100100001 | 0100010011 | 0100101111 | 0100010001 | +| 481-560 | 0110100110 | 0010100110 | 1010100110 | 1010100110 | 1110100110 | 1110100110 | 0010100110 | 0010100110 | +| 641 - 720 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 801 - 880 | 0110111001 | 0110111110 | 0110110111 | 0110110010 | 0110111001 | 0110110111 | 0110110111 | 0110110100 | +| 961 - 1040 | 1011011111 | 0110101001 | 1111100000 | 0001100111 | 1000101010 | 0010101101 | 0111101111 | 1100100101 | +| 1121 - 1200 | 1110001110 | 0101111011 | 1111001111 | 1000000001 | 1110001010 | 1111110010 | 0100111001 | 0001101110 | +| 1281 - 1360 | 1100111101 | 0111111000 | 0110101010 | 0000101111 | 0100111101 | 1000101110 | 1000010110 | 1101101010 | +| 1441 - 1520 | 1001001000 | 0110010101 | 0000000111 | 0111100110 | 1001110101 | 0011010100 | 0010000100 | 1100110110 | +| 1601 - 1680 | 0000011100 | 1010100001 | 1100001100 | 0001111111 | 0100011101 | 1000000011 | 0010110001 | 1011100100 | +| 1761 - 1840 | 0100110000 | 0010000001 | 0010010101 | 1011110100 | 0110110000 | 0101110100 | 1001111010 | 0100100101 | +| AM bits | Lane 8
10-bit
symbol of
AM8 | Lane 9
10-bit
symbol of
AM9 | Lane 10
10-bit
symbol of
AM10 | Lane 11
10-bit
symbol of
AM11 | Lane 12
10-bit
symbol of
AM12 | Lane 13
10-bit
symbol of
AM13 | Lane 14
10-bit
symbol of
AM14 | Lane 15
10-bit
symbol of
AM15 | +| 81 - 160 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 241 - 320 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 401 - 480 | 0100000001 | 0100110101 | 0100010111 | 0100001101 | 0100000110 | 0100001010 | 0100000010 | 0100001011 | +| 561 - 640 | 1010100110 | 1010100110 | 1110100110 | 1010100110 | 0010100110 | 0010100110 | 1110100110 | 0110100110 | +| 721 - 800 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 881 - 960 | 0110111111 | 0110110100 | 0110110010 | 0110111000 | 0110111101 | 0110110011 | 0110111000 | 0110110110 | +| 1041 - 1120 | 1001011110 | 0101011100 | 0000010101 | 1110101110 | 1010101110 | 0011011100 | 1101101011 | 1010100110 | +| 1201 - 1280 | 0011001110 | 0100100011 | 1011010111 | 1101100110 | 1001101111 | 1111101001 | 0011011111 | 1001011101 | +| 1361 - 1440 | 1010111000 | 0011110010 | 0001101111 | 0001110001 | 1010100100 | 1100001111 | 0110010101 | 1001111010 | +| 1521 - 1600 | 0001101000 | 1110101000 | 0111111010 | 1100010100 | 1001010100 | 0011001000 | 1100100101 | 0101010110 | +| 1681 - 1760 | 0111001100 | 1110110111 | 1001001010 | 0100100110 | 0101100100 | 1100000101 | 0011001000 | 0101101000 | +| 1841 - 1920 | 0101010001 | 0011000011 | 0011100100 | 0111100011 | 0001010110 | 1000111100 | 0010011010 | 1001100001 | + +**Table 14-4 – AM bit distribution over the sixteen logical lanes of flow #1** + +| AM bits | Lane 16
10-bit
symbol of
AM16 | Lane 17
10-bit
symbol of
AM17 | Lane 18
10-bit
symbol of
AM18 | Lane 19
10-bit
symbol of
AM19 | Lane 20
10-bit
symbol of
AM20 | Lane 21
10-bit
symbol of
AM21 | Lane 22
10-bit
symbol of
AM22 | Lane 23
10-bit
symbol of
AM23 | +|----------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------| +| 1 - 80 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 161 - 240 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 321 - 400 | 0100011011 | 0100001000 | 0100011000 | 0100010110 | 0100100001 | 0100010011 | 0100101111 | 0100010001 | +| 481 - 560 | 0110100110 | 0010100110 | 1010100110 | 1010100110 | 1110100110 | 1110100110 | 0010100110 | 0010100110 | +| 641 - 720 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 801 - 880 | 0110111001 | 0110111110 | 0110110111 | 0110110010 | 0110111001 | 0110110111 | 0110110111 | 0110110100 | +| 961 - 1040 | 1011100000 | 0110010110 | 1111011111 | 0001011000 | 1000010101 | 0010010010 | 0111010000 | 1100011010 | +| 1121 - 1200 | 0001110001 | 1010000100 | 0000110000 | 0111111110 | 0001110101 | 0000001101 | 1011000110 | 1110010001 | +| 1281 - 1360 | 0011000001 | 1000000100 | 1001010110 | 1111010011 | 1011000001 | 0111010010 | 0111101010 | 0010010110 | +| 1441 - 1520 | 1001000111 | 0110011010 | 0000001000 | 0111101001 | 1001111010 | 0011011011 | 0010001011 | 1100111001 | +| 1601 - 1680 | 1111100011 | 0101011110 | 0011110011 | 1110000000 | 1011100010 | 0111111100 | 1101001110 | 0100011011 | +| 1761 - 1840 | 1011001111 | 1101111110 | 1101101010 | 0100001011 | 1001001111 | 1010001011 | 0110000101 | 1011011010 | +| AM bits | Lane 24
10-bit
symbol of
AM24 | Lane 25
10-bit
symbol of
AM25 | Lane 26
10-bit
symbol of
AM26 | Lane 27
10-bit
symbol of
AM27 | Lane 28
10-bit
symbol of
AM28 | Lane 29
10-bit
symbol of
AM29 | Lane 30
10-bit
symbol of
AM30 | Lane 31
10-bit
symbol of
AM31 | +| 81 - 160 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | 0101100101 | +| 241 - 320 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | 0100100110 | +| 401 - 480 | 0100000001 | 0100110101 | 0100010111 | 0100001101 | 0100000110 | 0100001010 | 0100000010 | 0100001011 | +| 561 - 640 | 1010100110 | 1010100110 | 1110100110 | 1010100110 | 0010100110 | 0010100110 | 1110100110 | 0110100110 | +| 721 - 800 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | 1010110110 | +| 881 - 960 | 0110111111 | 0110110100 | 0110110010 | 0110111000 | 0110111101 | 0110110011 | 0110111000 | 0110110110 | +| 1041 - 1120 | 1001100001 | 0101100011 | 0000101010 | 1110010001 | 1010010001 | 0011100011 | 1101010100 | 1010011001 | +| 1201 - 1280 | 1100110001 | 1011011100 | 0100101000 | 0010011001 | 0110010000 | 0000010110 | 1100100000 | 0110100010 | +| 1361 - 1440 | 0101000100 | 1100001110 | 1110010011 | 1110001101 | 0101011000 | 0011110011 | 1001101001 | 0110000110 | +| 1521 - 1600 | 0001100111 | 1110100111 | 0111110101 | 1100011011 | 1001011011 | 0011000111 | 1100101010 | 0101011001 | +| 1681 - 1760 | 1000110011 | 0001001000 | 0110110101 | 1011011001 | 1010011011 | 0011111010 | 1100110111 | 1010010111 | +| 1841 - 1920 | 1010101110 | 1100111100 | 1100011011 | 1000011100 | 1110101001 | 0111000011 | 1101100101 | 0110011110 | + +An FOIC8.8-RS interface comprises eight OTSi. Specifications of the OTSi carrying a FOIC8.8-RS lane are contained in [ITU-T G.695] and [ITU-T G.959.1]. + +A group of m FOIC8.8-RS optical interfaces may be used to carry a digital client signal (e.g., an OTUCn may be carried over m FOIC8.8-RS optical interfaces). + +#### 14.5.2 FOIC8.8-RS skew tolerance requirements + +The lane skew tolerance requirement is 180 ns. + +NOTE – These requirements are in line with 800GAUI-8 [IEEE 802.3df]. + +#### 14.5.3 FOIC8.8-RS 112G lane bit rate + +The FOIC8.8-RS lane is synchronous to the FlexO-8-RS frame. There are eight lanes. + +The bit rate and tolerance of the FOIC8.8-RS lane signal is defined in Table 14-5. + +**Table 14-5 – FOIC8.8-RS lane rate** + +| FOIC8.8-RS nominal lane bit rate | Bit-rate tolerance | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| 30592/27233 × 99 532 800 kbit/s | ±20 ppm | +| NOTE 1 – The nominal lane rate is approximately: 111 809 474.444 kbit/s.
NOTE 2 – FOIC8.8-RS_lane_rate = 800G_FlexO-8-RS_rate/8. | | + +NOTE – The 800G FlexO-8-RS rate is specified in clause 14.2. + +#### **14.5.4 FlexO-8-RS interface processes** + +Figure 14-4 and Figure 14-5 show the processes of an 800G FlexO-8-RS interface. It can be seen that it is divided into three parts (the part reusing 100G FlexO, the part with two flows based on 400G FlexO-4-RS and the part reusing [IEEE 802.3df] 800GE PCS/FEC). + +The processes of the scrambler/descrambler and AM insertion/removal are based on 400G FlexO-4-RS in each flow with the same scrambler and different AMs. Before the scrambler in the source and after the descrambler in the sink, the formation of the two 400G flows is a new design (i.e., FlexO instances #1, #2, #3, #4 are 10-bit interleaved into 400G Flow #0 and FlexO instances #5, #6, #7, #8 are 10-bit interleaved into 400G Flow #1) and the rest are completely the same processes as 100G FlexO. + +In the part reusing [IEEE 802.3df] 800GE PCS lower-part and FEC, it completely reuses all those processes. 800G FlexO uses 2 × 200G KP4-FEC in each 400G flow. + +![Figure 14-4 – 800G FlexO-8-RS interface transmit processes. This block diagram illustrates the data flow from OTUCn down to the FOIC8.8-RS interface. The process starts with OTUCn, which branches into eight OTUC lanes (OTUC #1 to #8). The remainder of the OTUCs are directed to m-1 800G FlexO lanes. Each OTUC lane feeds into a 100G FlexO lane (100G FlexO #1 to #8). The 100G FlexO lanes are processed through a series of steps: 10-bit interleaved multiplex, Scrambler (400G flow #0 and #1), AM insertion (400G flow #0 and #1), 10-bit round-robin distribution, RS(544, 514) encode (FEC sub-rows #1 to #4), Mux and 10-bit symbol distribution (400G FlexO #0 and #1), and finally a 32:8 bit-level multiplex. The output of the bit-level multiplex is labeled FOIC8.8-RS. Annotations include 'Frame 128*5140 bits', 'FlexO-n reference point', 'Reuse 100G FlexO process', 'Design based on FlxO-4-RS', and 'Reuse 800GE PCS/FEC'. The diagram also shows various bit-width calculations such as 128*(4*544)*10 bits and 2*2*256*544*10-bit symbol.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +OTUCn + +OTUC #1 OTUC #2 OTUC #3 OTUC #4 ..... OTUC #5 OTUC #6 OTUC #7 OTUC #8 +*The remainder OTUCs to m-1 800G FlexO lanes* + +Frame 128\*5140 bits + 100G FlexO #1 100G FlexO #2 100G FlexO #3 100G FlexO #4 100G FlexO #5 100G FlexO #6 100G FlexO #7 100G FlexO #8 + FlexO-n reference point + Reuse 100G FlexO process + +Frame 128\*5140 bits + 100G FlexO OH insert (Reserved 480 bits AM placeholder) + 10-bit interleaved multiplex + +2 frames 128\*(4\*544)\*10 bits + Scrambler 400G flow #0 Scrambler 400G flow #1 + Design based on FlxO-4-RS + +2 frames 128\*(4\*544)\*10 bits + AM insertion 400G flow #0 AM insertion 400G flow #1 + +10-bit round-robin distribution + +2\*2\*256\*544\*10-bit symbol + RS(544, 514) encode (100G FlexO #1, #3) FEC sub-row #1 RS(544, 514) encode (100G FlexO #2, #4) FEC sub-row #2 + RS(544, 514) encode (100G FlexO #5, #7) FEC sub-row #3 RS(544, 514) encode (100G FlexO #6, #8) FEC sub-row #4 + Reuse 800GE PCS/FEC + +2\*2\*512\*544\*10-bit symbols + Mux and 10-bit symbol distribution 400G FlexO #0 Mux and 10-bit symbol distribution 400G FlexO #1 + +AM0 AM15 AM16 AM31 + 32:8 bit-level multiplex + +FOIC8.8-RS G.709.5(24) + +Figure 14-4 – 800G FlexO-8-RS interface transmit processes. This block diagram illustrates the data flow from OTUCn down to the FOIC8.8-RS interface. The process starts with OTUCn, which branches into eight OTUC lanes (OTUC #1 to #8). The remainder of the OTUCs are directed to m-1 800G FlexO lanes. Each OTUC lane feeds into a 100G FlexO lane (100G FlexO #1 to #8). The 100G FlexO lanes are processed through a series of steps: 10-bit interleaved multiplex, Scrambler (400G flow #0 and #1), AM insertion (400G flow #0 and #1), 10-bit round-robin distribution, RS(544, 514) encode (FEC sub-rows #1 to #4), Mux and 10-bit symbol distribution (400G FlexO #0 and #1), and finally a 32:8 bit-level multiplex. The output of the bit-level multiplex is labeled FOIC8.8-RS. Annotations include 'Frame 128\*5140 bits', 'FlexO-n reference point', 'Reuse 100G FlexO process', 'Design based on FlxO-4-RS', and 'Reuse 800GE PCS/FEC'. The diagram also shows various bit-width calculations such as 128\*(4\*544)\*10 bits and 2\*2\*256\*544\*10-bit symbol. + +Figure 14-4 – 800G FlexO-8-RS interface transmit processes + +![Figure 14-5 – 800G FlexO-8-RS interface receives processes. This block diagram illustrates the signal processing flow for receiving 800G FlexO-8-RS data. The process starts at the bottom with a 32:8 bit-level multiplex, which receives FOIC8.8-RS signals. This is followed by an 'AM lock, lane deskew and reorder' block that handles AM0 through AM31 signals. Above this is a 'De-interleave' block for 400G flow #0, which takes 2*512*544* 10-bit symbols as input. The next stage consists of two 'RS(544, 514) decode' blocks for FEC sub-rows #1, #2, #3, and #4, each taking 2*2*256*544* 10-bit symbols as input. This is followed by 'AM removal' blocks for 400G flow #0 and #1, which take 2 frames (128*(4*544)* 10 bits) as input. A 'Scrambler' block for 400G flow #0 and #1 follows, also taking 2 frames (128*(4*544)* 10 bits) as input. The next stage is '100G FlexO OH extract' for eight flows, which takes 128*5140 bits as input. A 'FlexO-n reorder' block follows, with a 'FlexO-n reference point' indicated. Above this is a 'Demap from 100G FlexO' block for eight flows, which takes 128*5140 bits as input. The next stage is 'OTUC #1 frame/multiframe alignment' through 'OTUC #8 frame/multiframe alignment'. Finally, the signals pass through an 'OTUC deskew' block to reach the 'OTUCn' output. Annotations include 'The remainder OTUC's to m-1 800G FlexO lanes' and 'Design based on FlexO-4-RS'. A note 'Reuse 800GE PCS/FEC' is also present.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +OTUCn + +OTUC deskew + +OTUC #1 frame/multiframe alignment + +OTUC #2 frame/multiframe alignment + +OTUC #3 frame/multiframe alignment + +OTUC #4 frame/multiframe alignment + +OTUC #5 frame/multiframe alignment + +OTUC #6 frame/multiframe alignment + +OTUC #7 frame/multiframe alignment + +OTUC #8 frame/multiframe alignment + +The remainder OTUC's to m-1 800G FlexO lanes + +Demap from 100G FlexO #1 + +Demap from 100G FlexO #2 + +Demap from 100G FlexO #3 + +Demap from 100G FlexO #4 + +Demap from 100G FlexO #5 + +Demap from 100G FlexO #6 + +Demap from 100G FlexO #7 + +Demap from 100G FlexO #8 + +FlexO-n reference point + +FlexO-n reorder + +100G FlexO OH extract + +Scrambler 400G flow #0 + +Scrambler 400G flow #1 + +AM removal 400G flow #0 + +AM removal 400G flow #1 + +RS(544, 514) decode (100G FlexO #1, #3) FEC sub-row #1 + +RS(544, 514) decode (100G FlexO #2, #4) FEC sub-row #2 + +RS(544, 514) decode (100G FlexO #5, #7) FEC sub-row #3 + +RS(544, 514) decode (100G FlexO #6, #8) FEC sub-row #4 + +De-interleave 400G flow #0 + +De-interleave 400G flow #1 + +AM0 + +AM15 + +AM16 + +AM31 + +AM lock, lane deskew and reorder + +32:8 bit-level multiplex + +FOIC8.8-RS + +Design based on FlexO-4-RS + +Reuse 800GE PCS/FEC + +G.709.5(24) + +Figure 14-5 – 800G FlexO-8-RS interface receives processes. This block diagram illustrates the signal processing flow for receiving 800G FlexO-8-RS data. The process starts at the bottom with a 32:8 bit-level multiplex, which receives FOIC8.8-RS signals. This is followed by an 'AM lock, lane deskew and reorder' block that handles AM0 through AM31 signals. Above this is a 'De-interleave' block for 400G flow #0, which takes 2\*512\*544\* 10-bit symbols as input. The next stage consists of two 'RS(544, 514) decode' blocks for FEC sub-rows #1, #2, #3, and #4, each taking 2\*2\*256\*544\* 10-bit symbols as input. This is followed by 'AM removal' blocks for 400G flow #0 and #1, which take 2 frames (128\*(4\*544)\* 10 bits) as input. A 'Scrambler' block for 400G flow #0 and #1 follows, also taking 2 frames (128\*(4\*544)\* 10 bits) as input. The next stage is '100G FlexO OH extract' for eight flows, which takes 128\*5140 bits as input. A 'FlexO-n reorder' block follows, with a 'FlexO-n reference point' indicated. Above this is a 'Demap from 100G FlexO' block for eight flows, which takes 128\*5140 bits as input. The next stage is 'OTUC #1 frame/multiframe alignment' through 'OTUC #8 frame/multiframe alignment'. Finally, the signals pass through an 'OTUC deskew' block to reach the 'OTUCn' output. Annotations include 'The remainder OTUC's to m-1 800G FlexO lanes' and 'Design based on FlexO-4-RS'. A note 'Reuse 800GE PCS/FEC' is also present. + +Figure 14-5 – 800G FlexO-8-RS interface receives processes + +# Annex A + +## Forward error correction for FlexO-x-RS using 10-bit RS(544,514) codecs + +(This annex forms an integral part of this Recommendation.) + +## A.1 Generic processing and common code structure + +The FlexO-x-RS FEC scheme is the RS(544,514) from [IEEE 802.3] for 100GBASE-R, 200GBASE-R, 400GBASE-R and 800GBASE-R interfaces from [IEEE 802.3df]. + +The FEC scheme employs a Reed-Solomon code operating over the Galois field $GF(2^{10})$ , where the symbol size is 10 bits. + +A Reed-Solomon code is denoted as RS( $n,k$ ) where $k$ represents the number of message symbols to generate $2t$ parity symbols, which are appended to the message of total length $n$ . The corresponding formula is $n=k+2t$ , specifically: + +$$n = 544$$ + +$$k = 514$$ + +$$t = 15$$ + +The FEC encoder processes $20 \times 257$ -bit data blocks, resulting in the 5 140 data bits in the FEC codeword (row) and generates $20 \times 15 = 300$ bits of FEC parity. + +The generator polynomial of the code is given by: + +$$G(z) = \prod_{i=0}^{29} (z - \alpha^i)$$ + +where $\alpha$ is a root of the binary primitive polynomial $x^{10} + x^3 + 1$ . + +The FEC code word (see Figure A.1) consists of 10-bit information blocks and parity blocks (FEC redundancy) and is represented by the polynomial: + +$$C(z) = I(z) + R(z)$$ + +![Diagram of an RS(544,514) FEC codeword structure. The codeword is shown as a sequence of blocks. From left to right, the blocks are: D_543, D_542, D_541, D_540 (labeled 1, 2, 3, 4 above), followed by an ellipsis, then D_j (labeled 1 above), followed by an ellipsis, then D_31, D_30, R_29, R_28 (labeled 513, 514, 515, 516 above), followed by an ellipsis, then R_j (labeled above), followed by an ellipsis, and finally R_1, R_0 (labeled 543, 544 above). Below the D_j block, a tree diagram shows its 10 bits: d_9j, d_8j, d_7j, d_6j, d_5j, d_4j, d_3j, d_2j, d_1j, d_0j (labeled 1 to 10 above). Below the R_j block, a tree diagram shows its 10 bits: r_9j, r_8j, r_7j, r_6j, r_5j, r_4j, r_3j, r_2j, r_1j, r_0j (labeled 1 to 10 above). A long arrow at the top indicates the 'Transmission order within FEC code word' from left to right. The label 'FEC sub-row' is on the left. The code 'G.709.5(24)' is at the bottom right.](6b95a21425e452581ef1a50ee2a6d391_img.jpg) + +Diagram of an RS(544,514) FEC codeword structure. The codeword is shown as a sequence of blocks. From left to right, the blocks are: D\_543, D\_542, D\_541, D\_540 (labeled 1, 2, 3, 4 above), followed by an ellipsis, then D\_j (labeled 1 above), followed by an ellipsis, then D\_31, D\_30, R\_29, R\_28 (labeled 513, 514, 515, 516 above), followed by an ellipsis, then R\_j (labeled above), followed by an ellipsis, and finally R\_1, R\_0 (labeled 543, 544 above). Below the D\_j block, a tree diagram shows its 10 bits: d\_9j, d\_8j, d\_7j, d\_6j, d\_5j, d\_4j, d\_3j, d\_2j, d\_1j, d\_0j (labeled 1 to 10 above). Below the R\_j block, a tree diagram shows its 10 bits: r\_9j, r\_8j, r\_7j, r\_6j, r\_5j, r\_4j, r\_3j, r\_2j, r\_1j, r\_0j (labeled 1 to 10 above). A long arrow at the top indicates the 'Transmission order within FEC code word' from left to right. The label 'FEC sub-row' is on the left. The code 'G.709.5(24)' is at the bottom right. + +Figure A.1 – RS(544,514) FEC code word + +10-bit information blocks are represented by: + +$$I(z) = D_{543} \cdot z^{543} + D_{542} \cdot z^{542} + \dots + D_{30} \cdot z^{30}$$ + +Where $D_j$ ( $j = 30$ to 1 087) is the 10-bit information block represented by an element out of $GF(256)$ and: + +$$D_j = d_{9j} \cdot \alpha^9 + d_{8j} \cdot \alpha^8 + \dots + d_{1j} \cdot \alpha^1 + d_{0j}$$ + +Bit $d_{0j}$ is the MSB and $d_{9j}$ the LSB of the 10-bit information block. + +$D_{543}$ corresponds to 10-bit block 1 in the FEC sub-row and $D_{30}$ to 10-bit block 514. + +10-bit parity blocks are represented by: + +$$R(z) = R_{29} \cdot z^{29} + R_{28} \cdot z^{28} + \dots + R_1 \cdot z^1 + R_0$$ + +Where $R_j$ ( $j = 0$ to 29) is the 10-bit parity block represented by an element out of $GF(2^{10})$ and: + +$$R_j = r_{9j} \cdot \alpha^9 + r_{8j} \cdot \alpha^8 + \dots + r_{1j} \cdot \alpha^1 + r_{0j}$$ + +Bit $r_{9j}$ is the MSB and $r_{0j}$ the LSB of the 10-bit parity block. + +$R_{29}$ corresponds to the 10-bit block 515 in the FEC sub-row and $R_0$ to 10-bit block 544. + +$R(z)$ is calculated by: + +$$R(z) = I(z) \bmod G(z)$$ + +where "mod" is the modulo calculation over the code generator polynomial $G(z)$ with elements out of the $GF(2^{10})$ . Each element in the $GF(2^{10})$ is defined by the binary primitive polynomial $x^{10} + x^3 + 1$ . + +The Hamming distance of the RS(544,514) code is $d_{min} = 31$ . The code can correct up to 15 symbol errors in the FEC code word when it is used for error correction. The FEC can detect up to 30 symbol errors in the FEC code word when it is used for error detection capability only. + +## A.2 FlexO-1-RS FEC codeword adaptation + +A 100G FlexO-1-RS FEC codeword occupies one row in the 100G FlexO-1-RS frame. The 100G FlexO-1-RS frame allocates 300 bits for FEC parity, per row, as shown in Figure 11-1. + +NOTE – The 100G FlexO-1-RS FEC is based on RS(544,514), as specified in clause 91 of [IEEE 802.3] for 100GBASE-KP4 interfaces. + +## A.3 FlexO-2-RS and FlexO-4-RS FEC codeword adaptation + +NOTE 1 – The FlexO-x-RS FEC ( $x = 2, 4$ ) is based on RS(544,514), as specified in clause 119 of [IEEE 802.3] for 200GBASE-R and 400GBASE-R interfaces. + +The forward error correction for the FlexO-x-RS uses 10-bit interleaved codecs using a Reed-Solomon RS(544,514) code. The RS(544,514) code is a non-binary code (the FEC algorithm operates on 10-bit symbols) and belongs to the family of systematic linear cyclic block codes. + +For FEC processing, a FlexO-x-RS row is separated into two sub-rows using 10-bit-interleaving as shown in Figure A.2. Each FEC encoder/decoder processes one of these sub-rows. The 10-bit FEC parity check blocks are calculated over the 10-bit information blocks 1 to 514 of each sub-row and transmitted in 10-bit blocks 515 to 544 of the same sub-row. + +NOTE 2 – After the FEC encoding and before distribution to the logical lanes, the two sub-rows are 10-bit re-interleaved following the procedure described in clause 119.2.4.7 of [IEEE 802.3] that is not round-robin interleaving. + +NOTE 3 – In [IEEE 802.3], sub-row #1 is referred to as A and sub-row #2 is referred to as B. + +![Diagram showing the mapping of 10-bit information and parity blocks from FEC sub-rows #1 and #2 into a single FlexO-x-RS row. Arrows indicate the sequential mapping of blocks from sub-rows into the larger row structure.](0b7849dae424b0dd33e6386d2384643a_img.jpg) + +The diagram illustrates the mapping of 10-bit information and parity blocks from two FEC sub-rows into a single FlexO-x-RS row. The mapping is sequential, starting from the first block of the first sub-row and continuing through all blocks of both sub-rows into the FlexO-x-RS row. + +| FEC sub-row #2 (IEEE 802.3: #B) | | +|---------------------------------|----------------------| +| 10-bit information blocks | 10-bit parity blocks | +| 1 | 5 | +| 5 | 4 | +| 1 | 4 | +| 4 | | +| 5 | | + + + +| FEC sub-row #1 (IEEE 802.3: #A) | | +|---------------------------------|----------------------| +| 10-bit information blocks | 10-bit parity blocks | +| 1 | 5 | +| 5 | 4 | +| 1 | 4 | +| 4 | | +| 5 | | + + + +| FlexO-x-RS row (x = 2.4) | | +|---------------------------|----------------------| +| 10-bit information blocks | 10-bit parity blocks | +| 1 2 ... | 1 1 1 1 ... 1 1 | +| | 0 0 0 0 ... 0 0 | +| | 2 2 2 3 ... 8 8 | +| | 7 8 9 0 ... 7 8 | + +G.709.5(24) + +Diagram showing the mapping of 10-bit information and parity blocks from FEC sub-rows #1 and #2 into a single FlexO-x-RS row. Arrows indicate the sequential mapping of blocks from sub-rows into the larger row structure. + +**Figure A.2 – FEC sub-rows** + +The 10-bit blocks in a FlexO-x-RS row belonging to FEC sub-row X (X = 1,2) are defined by: $X + 10 \times (i - 1)$ (for $i = 1 \dots 544$ ). + +## **A.4 FlexO-8-RS FEC codeword adaptation** + +NOTE – The FlexO-8-RS FEC is based on RS(544,514), as specified in clause 172 of [IEEE 802.3df] for 800GBASE-R interfaces. + +The FlexO-8-RS FEC encoder and decoder processes are illustrated in Figures 14-4 and 14-5, respectively. The encoder (decoder) process is composed of a pair of 400G RS encoders (decoders) operating on 400G flow #0 and 400G flow #1. The 400G RS encoder (decoder) is described in clause A.3. + +# Bibliography + +- [b-OIF CEI] Optical Internetworking Forum Implementation Agreement OIF-CEI-05.1 (2022), *Common Electrical I/O (CEI) – Electrical and Jitter Interoperability agreements for 6G+ bps, 11G+ bps, 25G+ bps, 56G+ bps and 112G+ bps I/O.* +<> + + + + + +## 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.720-199507-I_PDF-E/raw.md b/marked/G/T-REC-G.720-199507-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3da70e6b4c976f3f75625e1325cc0f8c666d3c0d --- /dev/null +++ b/marked/G/T-REC-G.720-199507-I_PDF-E/raw.md @@ -0,0 +1,511 @@ + + +![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.720** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/95) + +# **GENERAL ASPECTS OF DIGITAL TRANSMISSION SYSTEMS** --- + +# **CHARACTERIZATION OF LOW-RATE DIGITAL VOICE CODER PERFORMANCE WITH NON-VOICE SIGNALS** + +**ITU-T Recommendation G.720** + +(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.720 was prepared by ITU-T Study Group 15 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 10th of July 1995. + +--- + +## 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 Introduction ..... | 1 | +| 2 Scope ..... | 1 | +| 3 References ..... | 2 | +| 4 Abbreviations ..... | 3 | +| 5 Voiceband data performance..... | 3 | +| 5.1 Test Set-up Architecture ..... | 3 | +| 5.2 Impairments ..... | 4 | +| 5.3 Measurement Procedures ..... | 6 | +| 5.4 Transmit and echo levels ..... | 7 | +| 5.5 Performance measurements ..... | 7 | +| 6.6 Calibration ..... | 8 | +| 6 Narrow-band signal performance..... | 8 | +| 6.1 System No. 5 inter-register signalling ..... | 8 | +| 6.2 R-2 Signalling..... | 9 | +| 6.3 DTMF Signals ..... | 10 | +| 6.4 System No. 5 line signalling..... | 11 | +| 6.5 Circuit Continuity Tones ..... | 11 | +| 6.6 Echo canceller disabling tone ..... | 12 | +| 6.7 Distortion, frequency and level..... | 12 | +| 7 Coding delay ..... | 13 | +| 7.1 Total delay measurement method ..... | 14 | +| 8 Convergence time..... | 14 | +| 8.1 Encoder/decoder decorrelation ..... | 15 | +| 8.2 Encoder/decoder state mismatch..... | 15 | +| 8.3 Attack time..... | 15 | +| 8.4 Measurement method..... | 15 | +| 9 Facsimile performance ..... | 15 | +| Bibliography ..... | 15 | + +# **SUMMARY** + +In this Recommendation, an evaluation methodology is presented for the characterization of low-rate digital speech (or more generally source) coder performance with non-voice signals. The types of non-voice signals considered include voiceband data, network signalling, circuit continuity tones, and dual-tone multi-frequency signalling. Also addressed is the measurement of input/output delay and convergence time. Finally, appropriate test configurations, performance metrics, and test procedures are defined. + +# CHARACTERIZATION OF LOW-RATE DIGITAL VOICE CODER PERFORMANCE WITH NON-VOICE SIGNALS + +(Geneva, 1995) + +# 1 Introduction + +In selecting speech coding algorithms for network applications, characterization of their performance with a diversity of telephone network signals is normally required. Typical non-voice signals whose in-band transmission over the telephone network is desirable include the following. + +- Voiceband Data – Some transparency to voiceband data may be desirable particularly for applications such as thin-route satellite systems, digital mobile services, and circuit multiplication systems, such as DCME and PCME. It is considered that such transparency should be afforded to Public Switched Telephone Network (PSTN) voiceband data modems operating at bit rates up to and including 2400 bit/s. These modems include those conforming to Recommendations V.22, V.22 *bis*, V.21, V.23, V.26 *bis* and V.26 *ter*. It is recognized that other leased line and proprietary modems have found extensive use in the telephone network. Therefore, it is also desirable to use voiceband data signals from other modems which are not standardized by the ITU-T. +- Supervisory and inter-register signals that are incorporated within various signalling systems in the PSTN – These signals include two frequencies (2400 Hz and 2600 Hz) present within Signalling System No. 5 for line signalling, 15 multi-frequencies used by Signalling System No. 5 for register signalling, and all valid combinations (pairs) of the six high-frequency and six low-frequency tones employed by Signalling System R-2. +- Dual-Tone Multi-Frequency (DTMF) signals – These signals may be used independently of a signalling system to provide end-user access to specialized services such as answering machine message retrieval, airline reservations and electronic banking. +- Tones employed by Signalling Systems No. 6 and No. 7 for the verification of end-to-end circuit continuity and the four high-group and four low-group frequencies, conforming to Recommendation Q.23. +- The 2100 Hz tone (including any associated phase reversals) specified in Recommendation V.25, which is employed by the V-Series modems for disabling network echo control devices. +- Finally, the tones utilized in national signalling systems to provide ringing, busy or congestion information (see Recommendation Q.35) could require support depending upon the location of the coder within the network (such as in land-mobile environments) and should therefore be included in these tests. + +This methodology has evolved over several years from performance evaluations conducted during the development of Recommendations G.726, G.727 and G.728. + +# 2 Scope + +This Recommendation encompasses methods that can be used for quantifying and characterizing the performance of low-rate digital speech codecs with non-voice signals. The signals used are primarily those employed within the telephone network and, consequently, these methods are most appropriate for speech codecs intended for network (as opposed to end-user terminal) applications. The methods presented here can be used to quantify the performance of voice codecs that operate in the telephone band and that employ transmission rates that are less than or equal to 64 kbit/s. + +# 3 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions to 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 ITU-T Recommendations is regularly published. + +- ITU-T V-Series of Recommendations, *Data communication over the telephone network*. +- ITU-T Recommendation Clause 2 Q.141 (1993), *Line signalling – 2.1 signal code for line signalling*. +- CCITT Recommendation Q.151 (1988), *Signal code for register signalling*. +- CCITT Recommendation Q 441 (1988), *Signalling code*. +- CCITT Recommendation Q.271 (1988), *General*. +- CCITT Recommendation Q.724 (1988), *Signalling procedure Specifications of Signalling System No. 7* +- CCITT Recommendation Q.23 (1988), *Technical features of push-button telephone sets*. +- CCITT Recommendation V.25 (1988), *Automatic answering equipment and/or parallel automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls*. +- CCITT Recommendation Q.35 (1988), *Technical characteristics of tones for the telephone service*. +- CCITT Recommendation G.711 (1988), *Pulse Code Modulation (PCM) of voice frequencies*. +- CCITT Recommendation G.726 (1990), 40, 32, 24,16 kbit/s *Adaptive differential pulse code modulation (ADPCM)*. +- CCITT Recommendation O.42 (1988), *Equipment to measure non-linear distortion using the 4-tone intermodulation method*. +- CCITT Supplement No. 3.1, *Measuring instrument requirements. Sinusoidal signal generators and level measuring instruments*, Green Book, Vol. IV.2, Supplement to Series-M, -N and -O Recommendations, pp. 530-533, Geneva, 1972. +- CCITT Supplement No. 3.2, *Noise measuring instruments for telecommunication circuits*, Green Book, Vol. IV.2, Supplement to Series-M, -N and -O Recommendations, pp. 534-548, Geneva, 1972. +- ITU-T O-Series of Recommendations, *Specifications for measuring equipment*. +- CCITT Recommendation Q.112 (1988), *Signal levels and signal receiver sensitivity*. +- CCITT Recommendation Q.114 (1988), *Typical transmission requirements for signal senders and receivers*. +- CCITT Recommendation Q.451 (1988), *Definitions*. +- CCITT Recommendation Q.454 (1988), *The sending part of the multifrequency signalling equipment*. +- CCITT Recommendation Q.455 (1988), *The receiving part of the multifrequency equipment. Range, speed, and reliability of interregister signalling*. +- CCITT Recommendation Q.143 (1988), *Line signal sender*. +- CCITT Recommendation G.144 (1988), *Line signal receiver*. +- ITU-T Recommendation G.165 (1993), *Echo cancellers*. +- ITU-T Recommendation O.133 (1993), *Equipment for measuring the performance of PCM encoders and decoders*. +- CCITT Recommendation O.91 (1988), *Phase jitter measuring equipment for telephone-type circuits*. + +- CCITT Recommendation O.81 (1988), *Group-delay measuring equipment for telephone-type circuits.* +- CCITT Recommendation O.131 (1988), *Quantizing distortion measuring equipment using a pseudo-random noise test signal.* +- CCITT Recommendation O.132 (1988), *Quantizing distortion measuring equipment using a sinusoidal test signal.* +- ITU-T Recommendation E.450 (1993), *Facsimile quality of service on PSTN – General aspects.* +- ITU-T Recommendation E.451 (1993), *Facsimile call cut-off performance.* +- ITU-T Recommendation E.452 (1993), *Facsimile modem speed reductions and transaction time.* + +# 4 Abbreviations + +For the purposes of this Recommendation, the following abbreviations are used: + +| | | +|-------|----------------------------------------------------| +| ASCII | American Standard Code for Information Interchange | +| BER | Bit Error Ratio | +| CEPT | European Committee on Post and Telecommunications | +| CHER | Character Error Ratio | +| DCME | Digital Circuit Multiplication Equipment | +| DTMF | Dual-Tone Multi-Frequency | +| FIR | Finite Impulse Response | +| MBER | Modem Bit Error Ratio | +| MBLER | Modem Block Error Ratio | +| MSUR | Modem Missed Start-Up Ratio | +| PCM | Pulse Code Modulation | +| PCME | Packet Circuit Multiplication Equipment | +| PSTN | Public Switched Telephone Network | +| S/N | Signal-to-Noise Ratio | +| SNR | Signal-to-Noise Ratio | +| TLP | Transmission Level Point | + +# 5 Voiceband data performance + +In this clause, the procedure to be used for evaluating a speech codec's performance with 2- and 4-wire modems is described. + +## 5.1 Test Set-up Architecture + +An architecture to be employed for voiceband data modem measurements should be centred around a Bit Error Ratio (BER) test system which can provide the source data for the transmit direction of the modems (Figure 1). This system should permit the analysis of the receive modem data in order to compute single errors, blocks, block lengths, block errors, test duration, and error-free seconds, all of which are parameters that can be used in the interpretation of the received signal quality. + +In addition to the modems and BER test set, a reference 64 kbit/s Pulse Code Modulation (PCM) codec, the speech codec under evaluation, and an analogue impairment channel should be employed. All measurements shall then be performed with the analogue channel in tandem with the digitally (speech) encoded channel in the forward direction of transmission, with the input to the digitally encoded channel defined as the 0 Transmission Level Point (0 Transmission Level Point – TLP). In this Figure 1, the signal levels are defined with the analogue channel impairments disabled, and 0 = 0 dBm0, which makes the data level equal to –15 dBm or –15 dBm0. + +![Block diagram of Modem test configuration architecture (FIGURE 1/G.720).](3121ebddccf183ca63bb9781be440a7e_img.jpg) + +The diagram illustrates the test configuration for a modem. At the top, a 'Data generator & bit y error monitor system' is connected to a 'Transmit modem' on the left and a 'Receive modem' on the right. A long arrow labeled 'Direction under test' points from left to right above the main components. The 'Transmit modem' is connected to a 'Hybrid' unit. From this 'Hybrid', one path goes to an 'Analogue channel' and another goes to a '25 ms delay' block. The 'Analogue channel' has an input level of $-15 \text{ dBm}$ (0 TLP) and its output goes to a 'Digitally encoded channel'. The 'Digitally encoded channel' output goes to another 'Hybrid' unit. From this second 'Hybrid', one path goes to the 'Receive modem' and another goes to the '25 ms delay' block. The '25 ms delay' block's output is fed back into the first 'Hybrid' unit. Various return loss and power level specifications are indicated: 'Return loss = 6 or 12 dB' for the first Hybrid's reflection, 'Return loss > 30 dB' for the second Hybrid's reflection, and power levels of $-23 \text{ dBm}$ receive and $-9 \text{ dBm}$ transmit for both Hybrid units. The identifier 'T1515920-94/d01' is shown near the bottom right. + +Block diagram of Modem test configuration architecture (FIGURE 1/G.720). + +**FIGURE 1/G.720** +**Modem test configuration architecture** + +## 5.2 Impairments + +The analogue channel shall permit the introduction of two types of network impairments: variable and fixed. Variable impairments consist of the linear addition of controlled amounts of band-limited analogue white noise prior to the digitally encoded channel. Fixed impairments consist of group and attenuation distortion, phase jitter, and second and third order non-linear distortion. The impairments to be injected in the analogue channel are in accordance with the configuration shown in Figure 2. + +The values of these impairments are given in Tables 1 and 2. + +These impairments correspond to stringent network requirements. However, they provide a frame of reference against which the speech coding algorithms can be compared with other ITU-T speech coding Recommendations. It is noted that in measuring second and third order non-linear distortion (Table 1), a four-tone method shall be used which employs two pairs of equi-level tones with a composite power equal to that of the voiceband data modem signal. In the first tone pair (denoted by A), the tones shall be 6 Hz apart and centred at 860 Hz. In the second pair (denoted by B), the tones shall be 16 Hz apart and centred at 1380 Hz. The second order non-linear distortion shall be determined by measuring the power of the four $B + A$ and four $B - A$ intermodulation products, and the third order shall be determined by measuring the six $2B - A$ products. + +NOTE – The non-linear distortion unit provides, for every 1 dB increase in the input signal, an increase in the output second-order component of 2 dB, and an increase in the output third-order component of 3 dB. + +![Block diagram of the Analogue impairment channel. The signal starts from a Transmit modem, goes through an Amplifier, then enters the Analogue impairment channel. Inside the channel, it passes through a 200-3500 Hz bandpass filter, then Attenuation & group delay. The signal then splits into Non-linear distortion and Phase jitter distortion. Both are summed at a junction. White noise is filtered by a 4 kHz Low-pass filter and also summed at the junction. The output of the junction passes through an Attenuator to become the Codec input. The input level is marked as -15 dBm and 0 TLP. Reference T1515930-94/d02 is noted.](ebff22fb5dd6f50a90e44dca0f82f285_img.jpg) + +``` + +graph TD + TM[Transmit modem] --> A[Amplifier] + A --> B[200-3500 Hz bandpass filter] + subgraph AIC [Analogue impairment channel] + B --> C[Attenuation & group delay] + C --> D[Non-linear distortion] + C --> E[Phase jitter distortion] + D --> S((+)) + E --> S + WN[White noise] --> F[4 kHz Low-pass filter] + F --> S + S --> G[Attenuator] + end + G --> CI[Codec input] + CI --- L1[--- -15 dBm ---] + CI --- L2[--- 0 TLP ---] + T1515930-94/d02 + +``` + +Block diagram of the Analogue impairment channel. The signal starts from a Transmit modem, goes through an Amplifier, then enters the Analogue impairment channel. Inside the channel, it passes through a 200-3500 Hz bandpass filter, then Attenuation & group delay. The signal then splits into Non-linear distortion and Phase jitter distortion. Both are summed at a junction. White noise is filtered by a 4 kHz Low-pass filter and also summed at the junction. The output of the junction passes through an Attenuator to become the Codec input. The input level is marked as -15 dBm and 0 TLP. Reference T1515930-94/d02 is noted. + +FIGURE 2/G.720 +Analogue impairment channel + +TABLE 1/G.720 + +Analogue impairments for voiceband data tests + +| Analogue impairments | Impairment level | +|----------------------------------------------|-----------------------| +| Group delay distortion | See Table 2 | +| Attenuation distortion | See Table 2 | +| Second order non-linear distortion | 36 dB | +| Third order non-linear distortion | 38 dB | +| Phase jitter (degrees) at 120 Hz | 3 peak to peak | +| Additive noise (measured C-message weighted) | Varied as a parameter | + +TABLE 2/G.720 + +### **Added attenuation and group distortion** + +| Frequency (Hz) | Attenuation (dB relative to 1000 Hz) | Group delay ( $\mu\text{s}$ relative to 1800 Hz) | +|----------------|--------------------------------------|--------------------------------------------------| +| 200 | 8.5 | 4645 | +| 300 | 3.0 | 3442 | +| 400 | 0.9 | 2436 | +| 500 | 0.2 | 1703 | +| 600 | 0.1 | 1200 | +| 700 | 0.0 | 857 | +| 800 | 0.0 | 613 | +| 900 | 0.0 | 440 | +| 1000 | 0.0 | 312 | +| 1100 | 0.0 | 223 | +| 1200 | 0.1 | 153 | +| 1300 | 0.2 | 101 | +| 1400 | 0.3 | 61 | +| 1500 | 0.5 | 33 | +| 1600 | 0.6 | 14 | +| 1700 | 0.7 | 3 | +| 1800 | 0.9 | 0 | +| 1900 | 1.1 | 8 | +| 2000 | 1.3 | 27 | +| 2100 | 1.6 | 60 | +| 2200 | 2.0 | 109 | +| 2300 | 2.3 | 174 | +| 2400 | 2.7 | 262 | +| 2500 | 3.0 | 376 | +| 2600 | 3.3 | 517 | +| 2700 | 3.6 | 697 | +| 2800 | 3.9 | 934 | +| 2900 | 4.3 | 1247 | +| 3000 | 4.8 | 1616 | +| 3100 | 5.2 | 1969 | +| 3200 | 5.6 | 2263 | + +## **5.3 Measurement Procedures** + +In order to assure consistency in the manner in which measurements are collected and reported, the following definitions shall be adopted: + +- *Codec Input Data Level* – This is defined as the root mean square (r.m.s.) unweighted level of the data signal at the input to the coder. The data level is determined with the analogue noise injection disabled. +- *Noise Level* – This is provided by an r.m.s. psophometrically weighted measurement of the channel noise at the input to the codec. This measurement shall be performed with the noise injection enabled and the modern data signal disconnected. + +- *Data Signal-to-Noise Ratio (SNR)* – This shall be computed as the ratio of the codec input data level to the measured noise level. +- *Bit Error Ratio (BER)* – This is defined as the ratio of the number of bits intentionally corrupted in the coder digital channel in a fixed time interval, over the total number of bits transmitted over the same coder channel and over the same time period. +- *Modem Bit Error Ratio (MBER)* – This is defined as the ratio of the number of bits received in error by a modem receiver in a fixed time interval, over the total number of bits received by the same modem receiver over the same time period. +- *Modem Data Block* – A block of modem data is defined as a contiguous stream of 511 data bits. +- *Modem Block Error Ratio (MBLER)* – This is defined as the number of blocks received with at least 1 bit in error by a modem receiver in a fixed time interval, over the total number of blocks received by the same modem receiver over the same time period. +- *Modem Missed Start-Up Ratio (MSUR)* – This is defined as the total number of switched carrier messages received with at least one bit in error by a modem receiver in a fixed time interval, over the total number of switched carrier messages received by the same modem receiver and over the same time period. The switched carrier messages should consist of the three characters: SYN, SYN, and EOT. +- *Character Error Ratio (CHER)* – This is defined as the total number of asynchronous ASCII characters received with at least one bit in error by a modem receiver in a fixed time interval, over the total number of asynchronous ASCII characters received by the same modem receiver and over the same time period. + +## 5.4 Transmit and echo levels + +In order to provide a realistic two-wire network environment, the loss of the transmit side hybrid shall be adjusted so that the echo return loss is equal to 6 dB (12 dB for the V.26 *ter* modem), measured at the output of the analogue channel's bandpass filter. The return loss across the receive side hybrid shall be greater than 30 dB. For modems employing echo cancellation, 800 ms of transmission delay shall be introduced into the receive side path so that any echo control flat delay compensation can be exercised. + +## 5.5 Performance measurements + +Once the configuration and calibration of the facility has been completed, a series of measurements can be taken to quantify the performance of various modems over the digitally speech encoded channel of interest. + +#### 5.5.1 Switched carrier mode + +- Each Measurement shall be made until either 20 000 messages are transmitted without any messages missing or being in error, or 100 messages are missing or are in error, or 100 000 messages are transmitted with less than 100 messages missing or being in error, or if it is apparent that the Modem Missed Start-Up Ratio (MSUR) versus SNR relationship is approaching an asymptote. +- The message itself shall consist of three ASCII characters (SYN, SYN, EOT) separated by a predetermined time gap ms, preceded by a modem-dependent training sequence. The value of the time gap is for further study. +- Tests shall be operated with all modems in a multipoint mode. + +#### 5.5.2 Continuous carrier mode + +- Each measurement shall be made until either 20 000 blocks are received without any blocks in error, or 100 blocks are received in error, or 100 000 blocks are received with less than 100 errors, or if it becomes apparent that the MBLER versus S/N relationship is approaching asymptote. + +#### 5.5.3 Character mode + +- In order to generate a character sequence for transmission over the evaluated link, a number of files need to be generated off-line using suitable computer equipment. The first file should be generated to contain randomized sequences of all printable keyboard characters. Subsequently a "word" template file is to be constructed containing randomized grouping information of characters into words, with 1 to 10 characters per word. Finally, a third file containing inter-word delay information is generated, wherein delays are randomly varied between 16 and 320 ms with a granularity of 16 ms. All three files are generated only once and then used for all character mode tests. +- The keyboard character file is then transmitted over an RS-232 interface to the asynchronous transmit modem with program control of word delimiting and inter-word delay as specified in the word and delay template files respectively. In addition, a fixed 48 ms delay shall be inserted between each character within a word. Characters received over the RS-232 interface from the receiving modem will be stored in an output file. Upon reception, the characters are read sequentially, ignoring word delimiting and delays. As a result, a raw output file is written and its contents can be compared against the original input file for errors. +- In order to assure sufficient statistical significance in the results obtained, at least 20 000 characters should be transmitted over the link under evaluation. + +## 5.6 Calibration + +The calibration procedures need to be further defined. The procedures used in the characterization of Recommendations G.726 and G.728 can be used as a basis in the interim. + +# 6 Narrow-band signal performance + +As identified in the introduction, supervisory and interregister signals (that is, signals that are used to monitor the status of a call and signals that are used to carry service addresses across the network) are incorporated within various PSTN signalling systems. In view of the potential use of speech coding within the PSTN, transparency to such signals may be desirable. This clause describes the methods to be adopted in characterizing the performance of speech coders with narrow-band signals. Although not specifically addressed in this contribution, all instrumentation employed shall meet or exceed the requirements identified in Supplements 3.1 and 3.2 to the Series-M, -N and -O Recommendations. + +One of the first problems to be addressed is the selection of an acceptable method for determining whether acceptable transparency to narrow-band signals can be achieved (and, if so, at what margin). Two principal philosophies are identified, one based on the use of network sending and receiving equipment (method A), and the other (method B) based on an analytical comparison of the input and output waveforms transmitted through the digitally (speech) encoded channel. In order to permit some flexibility both methods are defined wherever possible. Which of the two methods is to be selected subsequently depends on whether senders and receivers are available, and/or on whether satisfactory methods for waveform analysis can be identified and implemented. In general, waveform analysis methods are considered preferable when suitable received signal tolerance specifications could be identified. + +Since the methods that employed signal senders and receivers comprised the same test architecture as that employed for voiceband data modem measurements, the architecture employed for network signalling is not repeated here. + +## 6.1 System No. 5 inter-register signalling + +One concern with Signalling System No. 5 is the possible violation of the transmitter's tolerance limits of $55 \pm 5$ ms when low-rate-encoded channels employ block processing frames of duration of the order of 5 ms. In assessing inter-register signalling transparency, the six frequencies of 700, 900, 1100, 1300, 1500 and 1700 Hz shall be used in appropriate combinations to generate the start of pulsing KP1 and KP2 signals, the end of pulsing ST signal, the Code 11 and Code 12 operator response signals, and the ten digits of 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 (Table 2/Q.151). The waveform + +sequence, whose degradation is to be assessed, shall then be constructed by transmitting the KP signal followed by 20 repetitions of a single digit, followed by the ST signal. This shall be repeated 12 times for each of the digits 1, 2, 3, 4, 5, 6, 7, 8, 9 and Codes 11 and 12. For Signally System No. 5, measurements shall be undertaken using a signal level of –7 dBm per frequency (–4 dBm composite) and by subsequently adjusting the calibration procedures accordingly. + +### Method A + +This method necessitates the use of a System No. 5 inter-register signalling generator and the use of controllable impairments identical to the ones to be used for voiceband modem testing. The procedures to be adopted shall be as follows: + +- Measurements shall be obtained with the codec in series with the impairment configuration. The level of impairments shall be equal to that used for modem testing (Tables 1 and 2). The non-linear distortion simulator shall be calibrated using a 4-tone signal at a level equal to that of the composite signalling tone-pair. Injected analogue noise shall be linearly added as the last impairment to the impairment configuration and prior to the codec input. The level of noise shall be varied and received inter-register signalling error rate as a function of injected noise shall be assessed at a composite signalling tone level of –4 dBm0 and a composite nominal codec input level of –4 dBm0. +- Measurements shall also be performed as above, but with the analogue noise injection disabled. This time the peak-to-peak jitter shall be varied and the received inter-register signalling error rate as a function of jitter shall be assessed. + +#### Method B + +The second technique addresses the analysis of the input and output waveforms transmitted through the coder channel under evaluation (with and without the analogue impairments of Tables 1 and 2 – injected noise disabled). Here, the following measurements are required: + +- Mean duration and mean amplitude of the active and silent signalling intervals. +- Variance of the duration and variance of the amplitude of the active and silent signalling intervals. +- A silent interval is characterized by the fact that its waveform energy is less than a predetermined percentage of the peak waveform energy during the active intervals. The value of the predetermined percentage is for further study. A sliding 2 ms window is used for this determination. +- An active interval is characterized by the fact that its waveform energy is within predetermined percentage of the peak waveform energy during the active intervals. The value of the predetermined percentage is for further study. A sliding 2 ms window is used for this determination. +- Distortion in the attack and fall times of each of the tones leading to the non-temporally coincident start and termination of each frequency from a register tone pair. It is noted that a limit of 1 ms is specified as the maximum signal sender tolerance for the non-temporally coincident start and termination of the tone pair Q.153. +- Level differences between the two tones. A limit of 4 dB in absolute level differences between the two unmodulated signal frequencies is imposed at signal senders (Recommendation Q.154). + +## 6.2 R-2 Signalling + +Signalling System R-2 is designed to use six signalling frequencies (1380, 1500, 1620, 1740, 1860 and 1980 Hz) in the forward direction and six signalling frequencies (1140, 1020, 900, 780, 660 and 540 Hz) in the backward direction of transmission. A 2-out-of-n code (Table 5/Q.441) then composes an inter-register signal consisting of the simultaneous transmission of a pair of frequencies. + +In conducting an assessment of inter-register signalling, the 15 forward and ten backward multi-frequencies [Table 5/Q.441, Note a)] shall be used. These frequencies shall be employed in appropriate combinations to generate the ten digits of 0, 1, 2, 3, 4, 5, 6, 7, 8 and 9 with nominal duration values in accordance to those defined in Recommendation Q.451. Finally, the signal sequence whose degradation is to be assessed shall consist of 20 repetitions + +of a single digit. This process was repeated ten times to generate each of the digits 1, 2, 3, 4, 5, 6, 7, 8, 9 and 0. Unlike Signalling System No. 5, where the signal levels are equal to $-7$ dBm per frequency, the nominal signal level at the input to the digitally encoded channel is defined to be equal to $-11.5$ dBm per frequency (or $-8.5$ dBm for the composite signal). + +#### Method A + +This method necessitates the use of a System R-2 inter-register signalling generator and the use of controllable impairments identical to the ones defined in conjunction with voiceband modem testing. The procedures to be applied shall be the same as in method A of Signalling System No. 5 inter-register testing with appropriate calibration adjustments to account for differences in signal levels. Thus, the level of noise shall be varied and the received inter-register signalling error rate as a function of injected noise shall be assessed at a composite signalling tone level of $-8.5$ dBm0. + +#### Method B + +The second technique addresses the analysis of the received signal which is processed through the digitally (speech) encoded channel (with and without the analogue impairments of Tables 1 and 2 – injected noise disabled). Here the following measurements are required: + +- Level between differences between the two tones. A limit of 1 dB in absolute level differences between the two unmodulated signal frequencies is imposed at signal senders (Recommendation Q.454) and a limit of 3 dB is imposed for signal receivers (Recommendation Q.455). +- Distortion in the attack and fall times of each tone leading to the non-temporally coincident start and termination of each frequency from a register tone pair. It is noted that a limit of 1 ms is specified as the maximum signal sender tolerance for the non-temporally coincident start and termination of the tone pair Recommendation Q.454. + +## 6.3 DTMF Signals + +DTMF signals are often used independently of a signalling system and after a call has been established to provide end-user access to specialized services. The DTMF signals which should be used to characterize the performance of a speech coder under evaluation shall be transmitted at a composite level of $-4$ dBm employing a minimum digit separation of 40 ms, and comprise pairs of tones selected from a high- and a low-group frequency set. The low-group frequencies are 697, 770, 852 and 941 Hz. The high-group frequencies are 1209, 1336, 1477 and 1633 Hz. Appropriate combinations of these frequencies shall then be used to derive the ten digits 1, 2, 3, 4, 5, 6, 7, 8, 9, and 0, and the characters \*, #, A, B, C and D (see Figure 1/Q.23). + +In measuring the performance of the speech coder under evaluation with DTMF signalling, the correct recognition percentage, as well as the variation of signal and signal-gap duration as a function of SNR were measured (the noise was injected in the analogue channel prior to codec input). It is noted that satisfactory performance can typically be assured when the total distortion products (resulting from harmonics and inter-modulation) does not exceed 20 dB below the fundamental frequencies. + +#### 6.3.1 Balanced pair + +The signal duration for each DTMF tone pair shall equal 50 ms and the separation between adjacent tone pairs shall equal 40 ms. In addition, the start and termination of the two tones, in a given DTMF tone pair, shall be temporally coincident. In assessing performance with DTMF tones, the following shall be measured (both with and without analogue impairments, and with analogue noise and bit error injection disabled). + +- Total distortion products (resulting from inter-modulation), which must not exceed 20 dB below the fundamental frequencies. +- The correct recognition percentage of DTMF tone pairs when analogue noise is injected prior to the codec input so that the reference input signal to noise ratio is equal to 20 dB. + +### 6.3.2 Twisted pair + +- This method of DTMF signal pair generation employs the same timing relationship for the “on” and “off” cycles as above. In this case however, one of the two tones shall be 6 dB higher than the other. Subsequently, the following shall be measured. +- The correct recognition percentage of DTMF tone pairs when analogue noise is injected prior to the codec input so that the reference input signal to noise ratio is equal to 22.5 dB. + +## 6.4 System No. 5 line signalling + +In addition to inter-register signalling which was addressed above, line signalling is employed in the network. Signalling System No. 5 line signals are comprised of two frequencies: 2400 and 2600 Hz, used either separately or combined. + +In assessing single-tone performance, measurements should be undertaken with and without analogue impairments. No bit errors shall be injected into the coder channel under evaluation. The analogue impairment channel shall be adjusted (using the output attenuator) so that the level of each tone at the encoder input is equal to $-9$ dBm0. The following shall then be measured: + +- frequency offset; and +- total distortion. + +It is noted that the requirement regarding frequency offsets impose a tolerance mask of $\pm 6$ Hz for signal senders (Recommendation Q.143) and $\pm 15$ Hz for signal receivers (Recommendation Q.144). Recommendation Q.143 also imposes a signal to total distortion ratio limit of 40 dB for signal senders. (Recommendation O.132 deals with relevant methods for performing these measurements.) + +#### Compound tone + +This is defined by the simultaneous presence of the 2400 and 2600 Hz tones and is used to signify a clear forward and a release guard line condition. Performance with this compound tone shall be assessed without bit errors injected into the coder link under evaluation. The analogue impairment channel shall be adjusted so that the level of each tone is the same and equal to $-9$ dBm0 per frequency at the input to the encoder (this calibration is made without analogue impairments). The start and termination of the two tones shall be temporarily coincidental. The following shall then be measured: + +- any distortion in the attack and fall times of each tone leading to the non-temporally coincidental start and termination of this tone pair; +- total distortion; and +- level differences between the two tones. + +It is noted that a limit of 5 ms is specified as the maximum signal sender tolerance for the non-temporally coincident start and termination of the tone pair Q.141. Further, a limit of 5 dB in absolute level differences between the two unmodulated signal frequencies is imposed at signal receivers (Recommendation Q.144). The requirements for total distortion (in this case this will include inter-modulation components) are the same as above. + +## 6.5 Circuit Continuity Tones + +Because Signalling Systems Nos. 6 and 7 are transmitted out of band, facilities are normally provided for making a continuity check of the speech path prior to making an end-to-end connection available to the end-users. This check is undertaken by transmitting a $2000 \pm 20$ Hz tone at a $-12$ dBm level. For these tests, a tone duration of 30 ms is defined, and the following shall be measured: + +- Total distortion of the channel output signal. +- Tone duration of the channel output signal. A tone is determined as being present if its energy is within predetermined percentage of the peak waveform energy of the tone during the active signal period. The value of the predetermined percentage is for further study. A 2.5 ms window shall be employed for this determination. + +## 6.6 Echo canceller disabling tone + +A special narrow-band signal (which is often associated with voiceband data and Group 3 facsimile transmissions) may be transmitted over the network after a call has been established in order to disable echo canceller devices. This tone comprises a 2100 Hz signal with 180° phase reversals every 400 ms, as defined in Recommendation G.165. + +In assessing the ability of a digitally (speech) encoded channel to transmit the 2100 Hz signal and associated phase reversals, the requirements defined in Annex B/G.165 are noted, particularly as regards the fact that phase reversals are only considered valid if they fall within $\pm 70$ of the transmitter's 180° phase change. + +### Method A + +This method uses a sufficient number of signal receivers to assess the performance degradation due to processing through a coder channel with and without bit slips in the digital channel. + +- Use will be made of an echo canceller employing a phase sensitive tone disabler. Subsequently the V.25 tone degradation will be assessed by observation of the number of times the tone disabler fails to function properly. In order to obtain statistical significance in these results, it is important to replicate these measurements a minimum of 50 times. Furthermore, in obtaining each measurement, the system under evaluation should be reset, or should this capability not be provided, the tone should be disconnected and reconnected for each measurement. +- These measurements should be repeated with and without the fixed analogue impairments defined in Tables 1 and 2. It will be important to employ at least four different tone disabling cancellers, each being supplied from a different manufacturer. + +### Method B + +This method depends on the recording and analysis of the waveform transmitted through the coder channel under evaluation in order to measure the phase reversals that should be occurring every 400 ms. In practice, since the 180° phase change will eventually always be reached, the parameter measured can be the time taken to settle to the 180° phase state following the actual transition in the transmitted waveform. + +In order to assess this type of degradation, a modulated 2100 Hz sine wave consisting of a sequence of 180° phase transitions occurring at 400 ms intervals shall be processed over the digitally (speech) encoded channel. In addition, this same waveform shall be recorded (after phase alignment) through a direct (unprocessed) recording path. The two waveforms may then be compared, and the settling time of the processed waveform after the phase transition measured. + +The two waveforms are compared in accordance with the functional configuration shown in Figure 3. Subsequently, the settling time of the processed waveform in the neighbourhood of the phase transition is measured. + +## 6.7 Distortion, frequency and level + +In order to assess the ability of a digitally-encoded channel to transcode with 64 kbit/s PCM, a series of measurements aimed at the characterization of non-linear distortion, dynamic range, and quantization distortion may be undertaken. These include the following: + +- Second- and third-order non-linear distortion employing a four-tone test signal at a codec input signal level of -4 and -15 dBm. +- Idle channel noise measurements taken psophometrically weighted. +- Input/output gain with an 820 Hz and/or a 1020 Hz and/or four-tone test signals (see bibliography) over a codec input signal range of +3 to -50 dBm (measured at 0 TLP) using the procedures defined in Recommendation O.133. + +NOTE – A reference to an 820 Hz and/or a 1020 Hz tone is meant to imply a tone whose frequency is in the neighbourhood of 800 and 1000 Hz but which is not a sub-multiple of 8 kHz. + +- Phase jitter, amplitude jitter, second and third order harmonic distortion employing a 1 kHz tone at a codec input signal level of -4 and -15 dBm. + +- Group delay and amplitude response variation with frequency at a codec input signal level of $-15$ dBm over the telephone voiceband spectrum of 200 to 3400 Hz. Recommendations O.81 and O.133 address relevant procedures to be used in taking these measurements. +- Signal-to-quantization distortion over a codec input signal range of $+3$ to $-50$ dBm (measured at 0 TLP) employing an 820 Hz test signal measured psophometrically weighted and/or a 1020 Hz test signal measured C-message weighted. Recommendations O.131 and O.132 address relevant procedures to be used in taking these measurements. +- Signal-to-quantization distortion over a codec input signal range of 0 to $-50$ dBm (measured at 0 TLP) employing a pseudo-random noise generator. Recommendation O.131 addresses relevant procedures to be used in making these measurements. + +![Functional diagram for echo canceller phase distortion measurement configuration. The diagram shows a signal flow from a 'Waveform generator' to a 'Coding channel' and a 'Phase compensation' block (labeled with theta). The outputs are multiplied (L x R), then processed through 'ABS' (resulting in |L x R|), 'SQRT' (resulting in sqrt(|L x R|)), and a 'Low-pass filter'. The final output is shown as a step-like waveform with labels for 'Codec delay (less phase compensation)' and 'Settling time'. A reference label 'T1518710-95/d03' is also present.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +The diagram illustrates the functional configuration for echo canceller phase distortion measurement. It starts with a 'Waveform generator' at the top. The signal from the generator is split into two paths: one goes through a 'Phase compensation' block (labeled with the Greek letter $\theta$ ) to produce signal 'L', and the other goes through a 'Coding channel' to produce signal 'R'. Signals 'L' and 'R' are then multiplied together in a block labeled with an 'X' to produce $L \times R$ . This result is processed by an 'ABS' (absolute value) block to produce $|L \times R|$ , which is then processed by an 'SQRT' (square root) block to produce $\sqrt{|L \times R|}$ . This signal is then passed through a 'Low-pass filter'. The output of the low-pass filter is shown as a waveform with a flat top and sloped edges. Two time intervals are indicated: 'Codec delay (less phase compensation)' from the start of the signal to the start of the flat top, and 'Settling time' from the start of the flat top to the end of the signal. A reference label 'T1518710-95/d03' is also present. + +Functional diagram for echo canceller phase distortion measurement configuration. The diagram shows a signal flow from a 'Waveform generator' to a 'Coding channel' and a 'Phase compensation' block (labeled with theta). The outputs are multiplied (L x R), then processed through 'ABS' (resulting in |L x R|), 'SQRT' (resulting in sqrt(|L x R|)), and a 'Low-pass filter'. The final output is shown as a step-like waveform with labels for 'Codec delay (less phase compensation)' and 'Settling time'. A reference label 'T1518710-95/d03' is also present. + +FIGURE 3/G.720 +**Functional diagram for echo canceller phase distortion measurement configuration** + +# 7 Coding delay + +In measuring processing delay, it should be noted that in waveform coders, measurements of delay rarely present a problem, because a direct assessment of the elapsed time between the signal onset at the codec input and the signal appearance at the codec output is possible (e.g. using a modulated sine wave). However, in block processing coders (or + +when little is known about the actual technique employed) this approach may be unreliable. This is because codec performance could vary substantially with the nature and type of signal being encoded, as well as with the precise time at which a signal appears at the codec input (in relation to the coder's frame structure, if there is one). + +The technique presented below for measuring the input/output delay of digitally (speech) encoded channels employs artificial speech and overcomes the previously mentioned narrow-band signal limitation. + +## 7.1 Total delay measurement method + +This method permits the direct measurement of the total delay introduced by a digitally (speech) encoded channel between its input and output 8-bit companded PCM interfaces. This delay is comprised of a delay introduced by the algorithm encoding and decoding functions, as well as any additional delay introduced by the processing or specific algorithm hardware implementation. + +The delay is measured by observing the first peak of the cross-correlation function between the encoder input and decoder output signals. This is determined by examining the peak response of an adaptive Finite Impulse Response (FIR) filter in a joint linear-process estimator configuration, as shown in Figure 4. In order to obtain a delay measurement which represents as closely as possible the delay likely to be experienced in real conversations (and at the same time retain the reproducibility of the measurement), an artificial speech signal shall be employed at a nominal codec input level of -22 dBm. + +As can be seen from Figure 4, the signal provided as reference to the adaptive filter is obtained from the input and 64 kbit/s $\mu$ -law PCM interface to the speech codec. Similarly, the point where the adaptive filter output is subtracted from the speech codec signal is defined as the codec's 64 kbit/s $\mu$ -law PCM output interface. + +![Block diagram of delay measurement architecture. The diagram shows two main signal paths. The top path (Encoder) consists of an Analogue input passing through a Filter, then an A/D converter, then a μ-law PCM encoder (outputting 14-bit data), then a μ-law PCM decoder (outputting 8-bit data), and finally a Speech encoder (outputting 14-bit data). The bottom path (Decoder) consists of a Speech decoder (outputting 14-bit data), then a μ-law PCM encoder (outputting 8-bit data), which is then subtracted from the 8-bit data from the top path. The result is then processed by a μ-law PCM decoder (outputting 14-bit data), then a D/A converter, then a Filter, and finally an Analogue output. An Adaptive FIR filter is connected to the 14-bit data from the top path and the 14-bit data from the bottom path. The output of the Adaptive FIR filter is subtracted from the 8-bit data from the top path before it enters the μ-law PCM decoder in the bottom path. The diagram is labeled T1515940-94/d04.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Block diagram of delay measurement architecture. The diagram shows two main signal paths. The top path (Encoder) consists of an Analogue input passing through a Filter, then an A/D converter, then a μ-law PCM encoder (outputting 14-bit data), then a μ-law PCM decoder (outputting 8-bit data), and finally a Speech encoder (outputting 14-bit data). The bottom path (Decoder) consists of a Speech decoder (outputting 14-bit data), then a μ-law PCM encoder (outputting 8-bit data), which is then subtracted from the 8-bit data from the top path. The result is then processed by a μ-law PCM decoder (outputting 14-bit data), then a D/A converter, then a Filter, and finally an Analogue output. An Adaptive FIR filter is connected to the 14-bit data from the top path and the 14-bit data from the bottom path. The output of the Adaptive FIR filter is subtracted from the 8-bit data from the top path before it enters the μ-law PCM decoder in the bottom path. The diagram is labeled T1515940-94/d04. + +FIGURE 4/G.720 +Block diagram of delay measurement architecture + +# 8 Convergence time + +Assuming that the encoder input signal characteristics have remained steady for a sufficient amount of time and assuming that disturbances causing loss of block synchronization have not occurred, two distinct phenomena can cause the decoder of an encoder-decoder pair to acquire an abnormal state. In addition, a convergence time is associated with a coder's tracking capability in the case of non-stationary signals. This gives rise to a third case where convergence is an issue. The three cases are as follows. + +## 8.1 Encoder/decoder decorrelation + +This case is generated when a burst of digital errors is presented to the encoder to decoder link, that are sufficiently long to cause a decorrelation between the encoder input and the decoder output to occur. Further, these burst errors should not cause loss of block synchronization. In this case, convergence time is determined by measuring the time needed for the “input signal” to “output noise” ratio to return to 90% of its steady state value after termination of the error burst. (The length of burst errors, the type of signals to be employed for this measurement, as well as the level of input signal to output noise ratio, under steady state conditions, are for further study.) + +## 8.2 Encoder/decoder state mismatch + +This case is generated when a decoder is connected to a transmitting encoder such that the encoder and decoder states are mismatched. This, for example, can occur when a decoder is disconnected or is switched between different encoded channels. In this case, convergence time can be assessed by measurement of the time necessary to achieve 90% of the steady state value of the “input signal” to “output noise” ratio after encoder to decoder reconnection. Should the decoder be provided with an independent reset capability, this case can also be more efficiently generated by resetting the decoder function, while maintaining block synchronization. + +## 8.3 Attack time + +This case is relevant to the attack time of the coding process when a new signal is presented or a signal present for some time is terminated at the encoder input. In this case, convergence time can be assessed by measurement of the time necessary for the “input signal” to “output noise” ratio to rise to 90% or fall to 10% of its steady state value after the appearance or after the termination of a sinusoidal signal at the encoder. It is assumed that prior to the appearance and after the termination of this signal, the encoder input signal is comprised of digital zeros. This measurement addresses the attack and fall times of sinusoidal signals. Of particular interest is the fall time of the 2100 Hz tone, since excessive distortion may affect the performance of the V.25 automatic answering sequence and the T.30 facsimile protocols. As a consequence, a 2100 Hz tone should be employed as a minimum in obtaining these measurements. + +## 8.4 Measurement method + +Unlike coder delay which is only likely to be impacted during the first frame (if there is one) after a signal has appeared at the encoder input, convergence time may be found to be signal dependent. As a consequence, a sufficiently exhaustive range of signals should be employed for this purpose. + +The signals to be used for this measurement should include tones and voice signals. At least ten tones spanning the 200 to 3200 Hz frequency range should be used and input signal power levels of 0, -15 and -30 dBm0 should be employed. Measurement of signal to noise ratio should be accomplished by application of a sliding window with predetermined duration. Since the sliding window will probably be of a duration that is comparable to the convergence time being measured, a large number of replicated measurements (e.g. 50) may be needed in order to obtain statistical significance. The duration of sliding window is for further study. + +In conducting these measurements, it is assumed that the input and output codec signals will be recorded and analysed digitally. Further, proper signal alignment will be required, this being accomplished by knowledge of the codec processing delay or by using the method described in clause 7. + +# 9 Facsimile performance + +The E.450-Series of Recommendations provide a comprehensive methodology for measuring facsimile performance over the telephone network. These Recommendations shall also be applied, as appropriate, in measuring performance of Group 3 facsimile over digitally (speech) encoded channels. In this case, the equipment configurations presented in clause 5 for voiceband data measurements (Figure 1) continue to apply, with the exception that the voiceband data modems shall be replaced by facsimile terminals. + +# Bibliography + +Bell System Technical Reference: *Transmission parameters affecting voiceband data transmission-measuring techniques*, Publication 41009. Section 3.7 Intermodulation (non-linear) Distortion, May 1975. \ No newline at end of file diff --git a/marked/G/T-REC-G.727-199012-I_PDF-E/raw.md b/marked/G/T-REC-G.727-199012-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3d578a266ee343e9ed42d5b0550ce7c8366053dc --- /dev/null +++ b/marked/G/T-REC-G.727-199012-I_PDF-E/raw.md @@ -0,0 +1,1836 @@ + + +![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 + +**CCITT** + +**G.727** + +THE INTERNATIONAL +TELEGRAPH AND TELEPHONE +CONSULTATIVE COMMITTEE + +**GENERAL ASPECTS OF DIGITAL +TRANSMISSION SYSTEMS; +TERMINAL EQUIPMENTS** + +--- + +**5-, 4-, 3- AND 2-BITS SAMPLE EMBEDDED +ADAPTIVE DIFFERENTIAL PULSE CODE +MODULATION (ADPCM)** + +**Recommendation G.727** + +--- + +![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.727 was prepared by Study Group XV and was approved under the Resolution No. 2 procedure on the 14th 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. + +###### **5-, 4-, 3- AND 2-bits SAMPLE EMBEDDED ADAPTIVE DIFFERENTIAL PULSE CODE MODULATION (ADPCM)** + +## **1 Introduction** + +This Recommendation contains the specification of an embedded Adaptive Differential Pulse Code Modulation (ADPCM) algorithms with 5-, 4-, 3- and 2-bits per sample (i.e., at rates of 40, 32, 24 and 16 kbit/s). The characteristics below are recommended for the conversion of 64 kbit/s. A-law or $\mu$ -law PCM channels to/ from variable rate-embedded ADPCM channels. + +The Recommendation defines the transcoding law when the source signal is a pulse-code modulation signal at a pulse rate of 64 kbit/s developed from voice frequency analog signals as fully specified by Blue Book Volume, Recommendation G.711. + +Applications where the encoder is aware and the decoder is not aware of the way in which the ADPCM codeword bits have been altered, or when both the encoder and decoder are aware of the ways the codewords are altered, or where neither the encoder nor the decoder are aware of the ways in which the bits have been altered can benefit from other embedded ADPCM algorithms. + +## **2 General** + +The embedded ADPCM algorithms specified here are extensions of the ADPCM algorithms defined in Recommendation G.726 and are recommended for use in packetized speech systems operating according to the Packetized Voice Protocol (PVP) specified in draft Recommendation G.764. + +PVP is able to relieve congestion by modifying the size of a speech packet when the need arises. Utilizing the embedded property of the algorithm described here, the least significant bit(s) of each codeword can be disregarded at packetization points and/or intermediate nodes to relieve congestion. This provides for significantly better performance than by dropping packets during congestion. + +Section 3 outlines a description of the ADPCM transcoding algorithm. Figure 1/G.727 shows a simplified block diagram of the encoder and the decoder. Sections 4 and 5 provide the principles and functional descriptions of the ADPCM encoding and decoding algorithms, respectively. Section 6 contains the computational details of the algorithm. In this section, 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 Section 6 will incur performance penalties which may be severe. + +![Simplified block diagrams of the ADPCM encoder and decoder. Part (a) shows the encoder where an A-or m-law 64 kbit/s PCM input is converted to uniform PCM, then a difference signal is calculated by subtracting a signal estimate. This difference signal is processed by an adaptive quantizer to produce an ADPCM output. The ADPCM output is also passed through BIT masking and an inverse adaptive quantizer to produce a quantizer difference signal. This signal is added to the signal estimate and passed through an adaptive predictor to produce a reconstructed signal, which is then used to update the signal estimate. Part (b) shows the decoder where an ADPCM input is processed through BIT masking and a feed-back inverse adaptive quantizer to produce a quantizer difference signal. This signal is added to a signal estimate and passed through an adaptive predictor to produce a reconstructed signal. The reconstructed signal is also passed through a feed-forward inverse adaptive quantizer and added to the signal estimate. The result is then converted to PCM and processed by synchronous coding adjustment to produce the final A-or m-law 64 kbit/s PCM output. A reference code T1508300-92 is present in the decoder diagram.](2763901b7a1fd1b5d704cdc450d12ed0_img.jpg) + +a) Encoder + +T1508300-92 + +b) Decoder + +Simplified block diagrams of the ADPCM encoder and decoder. Part (a) shows the encoder where an A-or m-law 64 kbit/s PCM input is converted to uniform PCM, then a difference signal is calculated by subtracting a signal estimate. This difference signal is processed by an adaptive quantizer to produce an ADPCM output. The ADPCM output is also passed through BIT masking and an inverse adaptive quantizer to produce a quantizer difference signal. This signal is added to the signal estimate and passed through an adaptive predictor to produce a reconstructed signal, which is then used to update the signal estimate. Part (b) shows the decoder where an ADPCM input is processed through BIT masking and a feed-back inverse adaptive quantizer to produce a quantizer difference signal. This signal is added to a signal estimate and passed through an adaptive predictor to produce a reconstructed signal. The reconstructed signal is also passed through a feed-forward inverse adaptive quantizer and added to the signal estimate. The result is then converted to PCM and processed by synchronous coding adjustment to produce the final A-or m-law 64 kbit/s PCM output. A reference code T1508300-92 is present in the decoder diagram. + +FIGURE 1/G.727 +Simplified block diagrams + +## 3 Embedded ADPCM algorithms + +Embedded ADPCM algorithms are variable bit rate coding algorithms with the capability of bit dropping outside the encoder and decoder blocks. They consist of a series of algorithms such that the decision levels of the lower rates quantizers are subsets of the quantizer at the highest rate. This allows bit reductions at any point in the network without the need of coordination between the transmitter and the receiver. In contrast, the decision levels of the conventional ADPCM algorithms, such as those in Recommendation G.726, are not subsets of one another and therefore, the transmitter must inform the receiver of the coding rate the encoding algorithm. + +Embedded algorithms can accommodate the unpredictable and bursty characteristics of traffic patterns that require congestion relief. Because congestion relief may occur after the encoding is performed, embedded coding is different from variable-rate coding where the encoder and decoder must use the same number of bits in each sample. In both cases, the decoder must be told the number of bits to use in each sample. + +Embedded algorithms produce code words which contain enhancement bits and core bits. The Feed-Forward (FF) path utilizes enhancement and core bits, while the Feedback (FB) path uses core bits only. The inverse quantizer and the predictor of both the encoder and the decoder use the core bits. With this structure, enhancement bits can be discarded or dropped during network congestion. However, the number of core bits in the FB paths of both the encoder and decoder must remain the same to avoid mistracking. + +The four embedded ADPCM rates are 40, 32, 24 and 16 kbit/s, where the decision levels for the 32, 24 and 16 kbit/s quantizers are sub-sets of those for the 40 kbit/s quantizer. Embedded ADPCM algorithms are referred to by $(x, y)$ pairs where $x$ refers to the FF (enhancement and core) ADPCM bits and $y$ refers to the FB (core) ADPCM bits. For example, if $y$ is set to 2 bits, $(5,2)$ will represent the 40 kbits/s embedded algorithm, $(4,2)$ will represent the 32 kbit/s embedded algorithm, $(3,2)$ will represent the 24 kbit/s embedded algorithm and $(2,2)$ the 16 kbit/s algorithm. The bit rate is never less than 16 kbit/s because the minimum number of core bits is 2. Simplified block diagrams of both the embedded ADPCM encoder and decoder are shown in Figure 1/G.727. + +The Recommendation provides coding rates of 40, 32, 24 and 16 kbit/s and core rates of 32, 24 and 16 kbit/s. This corresponds to the following pairs: $(5,2)$ , $(4,2)$ , $(3,2)$ , $(2,2)$ ; $(5,3)$ , $(4,3)$ , $(3,3)$ ; $(5,4)$ , $(4,4)$ . + +### 3.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 4-, 8-, 16- or 32-level quantizer is used to assign 2, 3, 4 or 5 binary digits to the value of the difference signal for transmission to the decoder. (Not all the bits necessarily arrive at the decoder since some of these bits can be dropped to relieve congestion in the packet network. For a given received sample, however, the core bits are guaranteed arrival if there are no transmission errors and the packets arrive at destination.) FB bits are fed to the inverse quantizer. The number of core bits depends on the embedded algorithm selected. For example, the $(5,2)$ algorithm will always contain 2 core bits. The inverse quantizer produces a quantized difference signal from these binary digits. 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. + +### 3.2 *ADPCM decoder* + +The decoder includes a structure identical to the FB portion of the encoder. In addition, there is also an FF path that contains a uniform PCM to A-law or $\mu$ -law conversion. The core as well as the enhancement bits are used by the synchronous coding adjustment block to prevent cumulative distortion on synchronous tandem codings (ADPCM-PCM-ADPCM, etc., digital connections) under certain conditions (see § 5.10). The synchronous coding adjustment is achieved by adjusting the PCM output codes to eliminate quantizing distortion in the next ADPCM encoding stage. + +### 3.3 *One's density requirements* + +These algorithms produce the all-zero code words. If requirements on one's density exist in national networks, other methods should be used to ensure that this requirement is satisfied. + +In the anticipated application with G.764, the Coding Type (CT) field and the block Dropping Indicator (BDI) field in the packet header defined in G.764 will inform the coder of what algorithm to use. For all other applications, the information that PVP supplies must be made known to the decoder. + +## 4 ADPCM encoder principles + +Figure 2/G.727 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 description of each block is given in §§ 4.1 to 4.9. + +![Block schematic of the ADPCM encoder (Figure 2/G.727). The diagram shows the signal flow from input PCM format conversion to the final ADPCM output, with various processing blocks and feedback loops.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +The block schematic illustrates the ADPCM encoder architecture. The input signal $s(k)$ is processed through a series of blocks: 'Input PCM format conversion' (outputting $s_l(k)$ ), 'Difference signal computation' (outputting $d(k)$ ), and 'Adaptive quantizer' (outputting $l(k)$ , which is the ADPCM output). The quantizer output $l(k)$ is also fed into 'Feed-back BIT masking' (outputting $l_c(k)$ ). This signal is then processed by 'Inverse adaptive quantizer' (outputting $d_q(k)$ ). The signal $d_q(k)$ is fed into 'Adaptive predictor' (outputting $s_e(k)$ ), which also receives feedback from 'Reconstructed signal calculator' (outputting $s_r(k)$ ). The 'Adaptive predictor' also outputs $a_2(k)$ . The signal $s_e(k)$ is fed into 'Tone and transition detector' (outputting $t_r(k)_{FB}$ and $t_d(k)$ ). The 'Tone and transition detector' also outputs $y_l(k)$ , which is fed into 'Quantizer scale factor adaptation' (outputting $y(k)$ and $a_1(k)$ ). The 'Quantizer scale factor adaptation' block also receives inputs from 'Adaptation speed control' (outputting $t_r(k)_{FB}$ and $t_d(k)$ ). The 'Adaptation speed control' block also receives inputs from 'Tone and transition detector' and 'Quantizer scale factor adaptation'. + +Block schematic of the ADPCM encoder (Figure 2/G.727). The diagram shows the signal flow from input PCM format conversion to the final ADPCM output, with various processing blocks and feedback loops. + +FIGURE 2/G.727 +Encoder block schematic + +### 4.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)$ . + +### 4.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 (4-1)$$ + +### 4.3 Adaptive quantizer + +A 4-, 8-, 16- or 32-level non-uniform mid-rise adaptive quantizer is used to quantize the difference signal $d(k)$ . 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.727 through 4/G.727 for the 16, 24, 32 and 40 kbit/s algorithms, respectively. Two, three, four or five binary digits are used to specify the quantized level representing $d(k)$ (the most significant bit represents the sign bit and the remaining bits represent the magnitude). The 2-, 3-, 4- or 5-bit quantizer output $I(k)$ forms the 16, 24, 32 or 40 kbit/s output signal and is also fed to the bit-masking block. $I(k)$ includes both the enhancement and core bits. + +### 4.4 Bit masking + +This block produces the core bits $I_c(k)$ by logically right-shifting the input signal $I(k)$ so as to mask the maximum droppable (least significant) bits. The number of bits to mask and the number of places to right shift depend on the embedded algorithm selected. For example, this block will mask the two least significant bits (LSB's) and shift the remaining bits two places to the right when the (4,2) algorithm is selected. The output of the bit-masking block $I_c(k)$ is fed to the inverse adaptive quantizer, the quantizer scale factor adaptation and the adaptation speed control blocks. + +TABLE 1/G.727 + +#### **Quantizer normalized input/output Characteristic for 16 kbit/s embedded operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $
$ I_c(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|------------------------|---------------------------------------------------------| +| $(-\infty, 2.04)$ | 0 | 0.91 | +| $[2.04, \infty)$ | 1 | 2.85 | + +*Note* – In Tables 1/G.727 through 4/G.727, “[” indicates that the endpoint value is included in the range, and (“ or “)” indicates that the endpoint value is excluded from the range. + +TABLE 2/G.727 + +#### **Quantizer normalized input/output Characteristic for 24 kbit/s embedded operation** + +| Normalized quantizer input range
$\log_2 d(k) - y(k)$ | $ I(k) $
$ I_c(k) $ | Normalized quantizer output
$\log_2 d_q(k) - y(k)$ | +|------------------------------------------------------------|------------------------|---------------------------------------------------------| +| $(-\infty, 0.96)$ | 0 | -0.09 | +| $[0.96, 2.04)$ | 1 | 1.55 | +| $[2.04, 2.78)$ | 2 | 2.40 | +| $[2.78, \infty)$ | 3 | 3.09 | + +TABLE 3/G.727 + +#### **Quantizer normalized input/output Characteristic for 32 kbit/s embedded operation** + +| Normalized quantizer
input range
$\log_2 d(k) - y(k)$ | $ I(k) $
$ I_c(k) $ | Normalized quantizer
output
$\log_2 d_q(k) - y(k)$ | +|---------------------------------------------------------------|------------------------|------------------------------------------------------------| +| $(-\infty, -0.05)$ | 0 | -1.06 | +| $[-0.05, 0.96)$ | 1 | 0.53 | +| $[0.96, 1.58)$ | 2 | 1.29 | +| $[1.58, 2.04)$ | 3 | 1.81 | +| $[2.04, 2.42)$ | 4 | 2.23 | +| $[2.42, 2.78)$ | 5 | 2.59 | +| $[2.78, 3.16)$ | 6 | 2.95 | +| $[3.16, \infty)$ | 7 | 3.34 | + +TABLE 4/G.727 + +#### **Quantizer normalized input/output Characteristic for 40 kbit/s embedded operation** + +| Normalized quantizer
input range
$\log_2 d(k) - y(k)$ | $ I(k) $ | Normalized quantizer
output
$\log_2 d_q(k) - y(k)$ | +|---------------------------------------------------------------|----------|------------------------------------------------------------| +| $(-\infty, -1.05)$ | 0 | -2.06 | +| $[-1.05, -0.05)$ | 1 | -0.48 | +| $[-0.05, 0.54)$ | 2 | 0.27 | +| $[0.54, 0.96)$ | 3 | 0.76 | +| $[0.96, 1.30)$ | 4 | 1.13 | +| $[1.30, 1.58)$ | 5 | 1.44 | +| $[1.58, 1.82)$ | 6 | 1.70 | +| $[1.82, 2.04)$ | 7 | 1.92 | +| $[2.04, 2.23)$ | 8 | 2.13 | +| $[2.23, 2.42)$ | 9 | 2.33 | +| $[2.42, 2.60)$ | 10 | 2.51 | +| $[2.60, 2.78)$ | 11 | 2.69 | +| $[2.78, 2.97)$ | 12 | 2.87 | +| $[2.97, 3.16)$ | 13 | 3.05 | +| $[3.16, 3.43)$ | 14 | 3.27 | +| $[3.43, \infty)$ | 15 | 3.56 | + +### 4.5 Inverse adaptive quantizer + +The inverse quantizer uses the core bits to compute a quantized version $d_q(k)$ of the difference signal using the scale factor $y(k)$ and Table 1/G.727, 2/G.727, 3/G.727 or 4/G.727 and then taking the antilog to the base 2 of the result. The estimated difference $s_e(k)$ is added to $d_q(k)$ to produce the reconstructed version $s_r(k)$ of the input signal. Table 1/G.727, 2/G.727, 3/G.727 or 4/G.727 will be applicable only when there are 2, 3, 4 or 5 bits, respectively, in the FF path. + +### 4.6 Quantizer scale factor adaptation + +This bloc computes $y(k)$ , the scaling factor for the quantizer and the inverse quantizer. (The scaling factor $y(k)$ is also fed to the adaptation speed control block.) The inputs are the bit-masked output $I_c(k)$ and the adaptation speed control parameter $a(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_c(k)] \quad (4-2)$$ + +where + +$y_u(k)$ is limited by $1.06 \leq y_u(k) \leq 10.00$ . + +For 2-core-bit operation (1 sign bit), the discrete function $W[I_c(k)]$ is defined as follows (infinite precision values): + +| | | | +|--------------|-------|-------| +| $ I_c(k) $ | 1 | 0 | +| $W[I_c(k)]$ | 27.44 | -1.38 | + +For 3-core-bit operation (1 sign bit), the discrete function $W[I_c(k)]$ is defined as follows (infinite precision values): + +| | | | | | +|-------------|-------|------|------|-------| +| $ I_c(k) $ | 3 | 2 | 1 | 0 | +| $W[I_c(k)]$ | 36.38 | 8.56 | 1.88 | -0.25 | + +For 4-core-bit (1 sign bit) operation, the discrete function $W[I_c(k)]$ is defined as follows (infinite precision values): + +| | | | | | | | | | +|-------------|-------|-------|-------|------|------|------|------|-------| +| $ I_c(k) $ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| $W[I_c(k)]$ | 69.25 | 21.25 | 11.50 | 6.13 | 3.13 | 1.69 | 0.25 | -0.75 | + +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 (4-3)$$ + +The fast and slow scale factors are then combined to form the resultant scale for: + +$$y(k) = a_l(k) y_u(k - 1) + [1 - a_l(k)] y_l(k - 1) \quad (4-4)$$ + +where + +$$0 \leq a_l(k) \leq 1.$$ + +### 4.7 Adaptation speed control + +The controlling parameter $a_l(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_c(k)$ are computed: + +$$d_{ms}(k) = (1 - 2^{-5}) d_{ms}(k - 1) + 2^{-5} F[I_c(k - 1)] \quad (4-5)$$ + +and + +$$d_{ml}(k) = (1 - 2^{-7}) d_{ml}(k - 1) + 2^{-7} F[I_c(k - 1)] \quad (4-6)$$ + +where + +$F[I_c(k)]$ is defined by + +| | | | +|------------------------------|---|---| +| $\frac{ I_c(k) }{F[I_c(k)]}$ | 1 | 0 | +| | 7 | 0 | + +for 2-core-bit (1 sign bit) operation; or + +| | | | | | +|------------------------------|---|---|---|---| +| $\frac{ I_c(k) }{F[I_c(k)]}$ | 3 | 2 | 1 | 0 | +| | 7 | 2 | 1 | 0 | + +for 3-core-bit (1 sign bit) operation; or + +| | | | | | | | | | +|------------------------------|---|---|---|---|---|---|---|---| +| $\frac{ I_c(k) }{F[I_c(k)]}$ | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| | 7 | 3 | 1 | 1 | 1 | 0 | 0 | 0 | + +for 4-core-bit (1 sign bit) operation. + +Thus, $d_{ms}(k)$ is a relatively short term average of $F[I_c(k)]$ and $d_{ml}(k)$ is a relatively long term average of $F[I_c(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 (4-7)$$ + +Thus, $a_p(k)$ tends towards the value 2 if the difference between $d_{ms}(k)$ and $d_m(k)$ is large (average magnitude $I_c(k)$ changing), for an idle channel [indicated by $y(k) < 3$ ] or for partial band (indicated by $t_d(k) = 1$ as described in § 4.9) signals. The value of $a_p(k)$ tends towards the value 0 if the difference is small [average magnitude of $I_c(k)$ relatively constant]. Note that $a_p(k)$ is set to one upon detection of a partial band signal transition [indicated by $t_r(k) = 1$ , see § 4.9]. + +$a_p(k - 1)$ is then limited to yield $a_l(k)$ used in equation (4-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 (4-8)$$ + +This asymmetrical limiting has the effect of delaying the start of a fast to slow state transition until the absolute value of $I_c(k)$ remains constant for some time. This tends to eliminate premature transitions for pulsed input signals such as switched carrier voiceband data. + +### 4.8 Adaptive predictor and feedback 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 zeroes 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 (4-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 (4-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 (4-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 § 4.9), 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 (4-12)$$ + +for $i = 1, 2, \dots, 6$ . + +If $t_r(k) = 1$ (see § 4.9), 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$ . + +### 4.9 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 (4-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_l(k)} \\ 0, & \text{otherwise} \end{cases} \quad (4-14)$$ + +## 5 ADPCM decoder principles + +Figure 3/G.727 is a block schematic of the decoder. A functional description of each block is given in §§ 5.1 to 5.10 below. There is an FB path and an FF path. The FB path uses the core bits to calculate the signal estimate. The FF path contains the core and enhanced bits and reconstructs the output PCM code word. + +![Block diagram of an ADPCM decoder schematic showing signal flow between various processing blocks including bit masking, inverse adaptive quantizers, reconstructed signal calculators, adaptive predictor, and adaptation control units.](7c1f9e78e0f033d391b687f1652f6e47_img.jpg) + +FIGURE 3/G.727 + +**Decoder block schematic** + +The diagram illustrates the internal architecture of a G.727 decoder. It takes an ADPCM input \$I'(k)\$ which passes through a 'Feed-back BIT masking' block to produce \$I\_c(k)\$. This signal is fed into a 'Feed-back inverse adaptive quantizer' and 'Quantizer scale factor adaptation'. The decoder features two parallel paths: a feed-forward path producing \$s\_r(k)\_{FF}\$ and a feed-back path producing \$s\_r(k)\_{FB}\$. An 'Adaptive predictor' generates an estimate \$s\_e(k)\$ based on the feedback signal. The final output \$s\_d(k)\$ is produced after 'Output PCM format conversion' and 'Synchronous coding adjustment'. Control signals like adaptation speed and tone detection influence the quantizer and predictor behavior. + +Block diagram of an ADPCM decoder schematic showing signal flow between various processing blocks including bit masking, inverse adaptive quantizers, reconstructed signal calculators, adaptive predictor, and adaptation control units. + +5.1 *Bit masking* + +The function of this block is described in § 4.4. + +5.2 *Feedback inverse adaptive quantizer* + +The function of this block is described in § 4.5. + +5.3 *Feed-forward inverse adaptive quantizer* + +A quantized difference signal $d_q(k)$ of the difference signal is produced from the input $I'(k)$ which contains the core and enhanced bits. + +5.4 *Quantizer scale factor adaptation* + +The function of this block is described in § 4.6. + +5.5 *Adaptation speed control* + +The function of this block is described in § 4.7. + +12 **Recommendation G.727** + +### 5.6 *Adaptive predictor and feedback reconstructed signal calculator* + +The functions of this block are described in § 4.8. + +### 5.7 *Feed-forward reconstructed signal calculator* + +This block receives input from the FF inverse adaptive quantizer and the adaptive predictor to reconstruct the uniform PCM signal that is fed to the PCM format conversion block. + +### 5.8 *Tone and transition detector* + +The function of this block is described in § 4.9. + +### 5.9 *Output PCM format conversion* + +This block converts the reconstructed uniform PCM signal $s_r(k)_{FF}$ into an A-law or $\mu$ -law PCM signal $s_p(k)$ as required. + +### 5.10 *Synchronous coding adjustment* + +The synchronous coding adjustment prevents cumulative distortion occurring on synchronous tandem codings (ADPCM-PCM-ADPCM, etc., digital connections) for: + +- error-free transmission, +- instances when the embedded 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 encoder have identical values and there are no transmission errors, the forced equivalence of both feed-forward quantizer output sequences for all values of $k$ guarantees the 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 (5-1)$$ + +The difference signal $d_x(k)$ is then examined to see if it falls in 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 (5-2)$$ + +where + +$s_d(k)$ : the output PCM code word of the decoder; + +$s_p^+(k)$ : 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_p^+(k)$ is constrained to be the value $s_p(k)$ ); + +$s_p^-(k)$ : the code word that represents the next more negative PCM output level (when $s_p(k)$ represents the most negative output level, then $s_p^-(k)$ is constrained to be the value $s_p(k)$ ). + +# 6 Computational details + +Computational details for each of the encoder and decoder elements are provided in §§ 6.1 and 6.2. + +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, the Signal Estimate (SE) of Figure 10/G.727 is calculated using delay values and then SE is used as shown in Figure 4/G.727. + +### 6.1 Input and output signals + +Table 5/G.727 defines the input and output signals for the encoder and decoder. Table 6/G.727 defines control variables for the algorithm. + +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 that require an immediate reset function (e.g. digital circuit multiplication equipment), the reset is mandatory, not optional. + +TABLE 5/G.727 + +#### **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 | $E + C$ | C = core bits,
E = Enhancement bits | +| DECODER | | | | +| | Name | Number of bits | Description | +| Input | I' | $C + E$ | C = core bits,
E = Enhancement bits | +| Input | LAW | 1 | PCM law select, 0 = $\mu$ -law,
1 = A-law | +| Input | R (optional) | 1 | Reset | +| Output | SD | 8 | Decoder PCM output word | + +TABLE 6/G.727 + +#### **Control variables** + +| Coding rate kbit/s | Core bits (C) | Enhancement bits (E) | +|--------------------|---------------|----------------------| +| 16 | 2 | 0 | +| 24 | 2 | 1 | +| | 3 | 0 | +| 32 | 2 | 2 | +| | 3 | 1 | +| | 4 | 0 | +| 40 | 2 | 3 | +| | 3 | 2 | +| | 4 | 1 | + +*Note* – For 16-kbit/s, 24-kbit/s and 32 kbit/s operation, E = 0 corresponds to the algorithm at higher rates with all the enhancement bits dropped. For 40-kbit/s operation, E = 0 is invalid because no higher rate embedded algorithm has been defined. + +TABLE 7/G.727 + +#### 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$ unlimited | +| 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 FB | 15 SM | S,13,...,0 | | Feed-back (FB) quantized difference signal | +| DQ FF | 15 SM | S,13,...,0 | | Feed-forward (FF) quantized difference signal | +| 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 FB | 12 TC | S,3,...,-7 | | Log 2 (FB quantized difference signal) | +| DQL FF | 12 TC | S,3,...,-7 | | Log 2 (FF quantized difference signal) | +| DQLN FB | 12 TC | S,3,...,-7 | | Log 2 (FB normalized quantized difference) | +| DQLN FF | 12 TC | S,3,...,-7 | | Log 2 (FF normalized quantized difference) | +| DQS FB | 1 TC | S | | Sign bit of FB quantized difference signal | +| DQS FF | 1 TC | S | | Sign bit of FF quantized difference signal | + +TABLE 7/G.727 (Cont.) + +| Name | Bits | Binary representation | Optional reset values | Description | +|---------------------------------------|-------|-----------------------|-----------------------|---------------------------------------------------| +| 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) | +| I c | 2 SM | S,0 | | 2 bit core ADPCM bits | +| I c | 3 SM | S,1,0 | | 3 bit core ADPCM bits | +| I c | 4 SM | S,2,...,0 | | 4 bit core ADPCM bits | +| 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 FF | 16 TC | S,14,...,0 | | Reconstructed signal | +| SR FB | 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 reset. When reset is invoked, the output of the DELAY sub-block (see § 7.2.5) is given in column 4. + +TC Two's complement            e Exponent bits +SM Signed magnitude            m Mantissa bits +FL Floating point            S Sign bit + +### 6.2 Description of variables and detailed specification of sub-blocks + +This section contains a detailed expansion off all blocks in Figures 2/G.727 and 3/G.727, described in §§ 4 and 5. The expansions are illustrated in Figures 4/G.727 to 13/G.727 with the internal processing variables as defined in Table 7/G.727. A brief functional description and full specification is given for each sub-block. + +The notations used in the sub-block descriptions are as follows: + +<<*n* *n*-bit shift left operation (zero fill); + +>>*n* *n*-bit shift right operation (in the direction of the least significant bit and zero fill); + +& Logical “and” operation; + ++ Arithmetic addition; + +– Arithmetic subtraction; + +\* Arithmetic multiplication; + +\*\* Logical “exclusive or” operation; + +| +| Comments to equations. +| + +#### 6.2.1 Input PCM format conversion and difference signal computation + +![Block diagram of input PCM format conversion and difference signal computation. The diagram shows two main blocks: EXPAND and SUBTA. The EXPAND block has two inputs on the left: S and LAW. It has two outputs on the right: SL and SE. The SUBTA block has two inputs on the left: SL and SE. It has one output on the right: D. The diagram is labeled T1508330-92.](cd141897aa368dbbaa398ace230cdd85_img.jpg) + +``` +graph LR; S[S] --> EXPAND[EXPAND]; LAW[LAW] --> EXPAND; EXPAND -- SL --> SUBTA[SUBTA]; EXPAND -- SE --> SUBTA; SUBTA -- D --> D; +``` + +Block diagram of input PCM format conversion and difference signal computation. The diagram shows two main blocks: EXPAND and SUBTA. The EXPAND block has two inputs on the left: S and LAW. It has two outputs on the right: SL and SE. The SUBTA block has two inputs on the left: SL and SE. It has one output on the right: D. The diagram is labeled T1508330-92. + +FIGURE 4/G.727 + +**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 (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$$ + +#### 6.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 path labeled DS connects the output I back to the input of the LOG block. A label T1508340-92 is present below the QUAN block.](04dc3838022e96d8d5548bb1b777b38c_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 path labeled DS connects the output I back to the input of the LOG block. A label T1508340-92 is present below the QUAN block. + +FIGURE 5/G.727 +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 8/G.727 + +##### **16 kbit/s quantizer decision levels and 2-bit outputs** + +| DS | DLN | I | | +|----|-----------|----|----------------------------------| +| | | 12 | | +| 0 | 261-2047 | 01 | | +| 0 | 0- 260 | 00 | -- Positive 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 | | + +TABLE 9/G.727 + +##### **24 kbit/s quantizer decision levels and 3-bit outputs** + +| DS | DLN | I | | +|----|-----------|-----|----------------------------------| +| | | 123 | | +| 0 | 356-2047 | 011 | | +| 0 | 261- 355 | 010 | | +| 0 | 123- 260 | 001 | | +| 0 | 0- 122 | 000 | -- Positive portion of interval | +| 0 | 2048-4095 | 000 | -- Negative portion of interval | +| 1 | 2048-4095 | 111 | -- Negative portion of interval | +| 1 | 0- 122 | 111 | -- Positive portion of interval | +| 1 | 123- 260 | 110 | | +| 1 | 261- 355 | 101 | | +| 1 | 356-2047 | 100 | | + +TABLE 10/G.727 + +##### **32 kbit/s quantizer decision levels and 4-bit outputs** + +| DS | DLN | I | | +|----|-----------|------|----------------------------------| +| | | 1234 | | +| 0 | 405-2047 | 0111 | | +| 0 | 356- 404 | 0110 | | +| 0 | 310- 355 | 0101 | | +| 0 | 261- 309 | 0100 | | +| 0 | 202- 260 | 0011 | | +| 0 | 123- 201 | 0010 | | +| 0 | 0- 122 | 0001 | -- Positive portion of interval | +| 0 | 4089-4095 | 0001 | -- Negative portion of interval | +| 0 | 2048-4088 | 0000 | | +| 1 | 2048-4088 | 1111 | | +| 1 | 4089-4095 | 1110 | -- Negative portion of interval | +| 1 | 0- 122 | 1110 | -- Positive portion of interval | +| 1 | 123- 201 | 1101 | | +| 1 | 202- 260 | 1100 | | +| 1 | 261- 309 | 1011 | | +| 1 | 310- 355 | 1010 | | +| 1 | 356- 404 | 1001 | | +| 1 | 405-2047 | 1000 | | + +TABLE 11/G.727 + +##### **40 kbit/s quantizer decision levels and 5-bit outputs** + +| DS | DLN | I | | +|----|-----------|-------|----------------------------------| +| | | 12345 | | +| 0 | 439-2047 | 01111 | | +| 0 | 405- 438 | 01110 | | +| 0 | 380- 404 | 01101 | | +| 0 | 356- 379 | 01100 | | +| 0 | 333- 355 | 01011 | | +| 0 | 310- 332 | 01010 | | +| 0 | 286- 309 | 01001 | | +| 0 | 261- 285 | 01000 | | +| 0 | 233- 260 | 00111 | | +| 0 | 202- 232 | 00110 | | +| 0 | 166- 201 | 00101 | | +| 0 | 123- 165 | 00100 | | +| 0 | 69- 122 | 00011 | | +| 0 | 0- 68 | 00010 | -- Positive portion of interval | +| 0 | 4089-4095 | 00010 | -- Negative portion of interval | +| 0 | 3961-4088 | 00001 | | +| 0 | 2048-3960 | 00000 | | +| 1 | 2048-3960 | 11111 | | +| 1 | 3961-4088 | 11110 | | +| 1 | 4089-4095 | 11101 | -- Negative portion of interval | +| 1 | 0- 68 | 11101 | -- Positive portion of interval | +| 1 | 69- 122 | 11100 | | +| 1 | 123- 165 | 11011 | | +| 1 | 166- 201 | 11010 | | +| 1 | 202- 232 | 11001 | | +| 1 | 233- 260 | 11000 | | +| 1 | 261- 285 | 10111 | | +| 1 | 286- 309 | 10110 | | +| 1 | 310- 332 | 10101 | | +| 1 | 333- 355 | 10100 | | +| 1 | 356- 379 | 10011 | | +| 1 | 380- 404 | 10010 | | +| 1 | 405- 438 | 10001 | | +| 1 | 439-2047 | 10000 | | + +*Note* – The I values are transmitted starting with bit 1. + +##### 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$$ + +#### 6.2.3 Bit masking + +![Block diagram of Bit masking. An input signal 'I' enters a block labeled 'BIT MASKING', and an output signal 'I_c' exits the block. The reference code 'T1508350-92' is shown below the block.](088921fa3f5a44c8551815122517eefd_img.jpg) + +Block diagram of Bit masking. An input signal 'I' enters a block labeled 'BIT MASKING', and an output signal 'I\_c' exits the block. The reference code 'T1508350-92' is shown below the block. + +FIGURE 6/G.727 + +##### Bit masking + +Input: $I(k)$ or $I'(k)$ + +Outputs: $I_c(k)$ + +Function: Masking of quantized difference signal to extract the core bits. + +Note: Figure 6/G.727 and equations are given for the encoder. They are also valid when substituting $I'(k)$ for $I(k)$ for the decoder. + +$$I_c = I \gg E, E = \text{Enhancement Bits.}$$ + +#### 6.2.4 Inverse adaptive quantizer + +![Block diagram of the Inverse adaptive quantizer. The input 'I_c(k)' enters a 'RECONST' block, which outputs 'DQLN_FB'. This signal enters an 'ADDA' block, which also receives an input 'Y' from below. The output of 'ADDA' is 'DQL_FB'. This signal enters an 'ANTILOG' block, which outputs 'DQ_FB'. A feedback signal 'DQS_FB' is taken from the output 'DQ_FB' and fed back to the 'RECONST' block. The reference code 'T1508360-92' is shown below the 'ANTILOG' block.](db7ae70402c81d140ae7df14b002e057_img.jpg) + +Block diagram of the Inverse adaptive quantizer. The input 'I\_c(k)' enters a 'RECONST' block, which outputs 'DQLN\_FB'. This signal enters an 'ADDA' block, which also receives an input 'Y' from below. The output of 'ADDA' is 'DQL\_FB'. This signal enters an 'ANTILOG' block, which outputs 'DQ\_FB'. A feedback signal 'DQS\_FB' is taken from the output 'DQ\_FB' and fed back to the 'RECONST' block. The reference code 'T1508360-92' is shown below the 'ANTILOG' block. + +FIGURE 7/G.727 + +##### Inverse adaptive quantizer + +##### RECONST + +Input: $I_c$ or $I'(k)$ + +Outputs: $DQS_{FB}$ or $DQS_{FF}$ , $DQLN_{FB}$ or $DQLN_{FF}$ + +Function: Reconstruction of quantized difference signal in the logarithmic domain. + +Note: Figure 7/G.727, equations and tables are given for the feed-back path. They are also valid when substituting $I'(k)$ for $I_c(k)$ , $DQS_{FF}$ for $DQS_{FB}$ and $DQLN_{FF}$ for $DQLN_{FB}$ . + +$$DQS_{FB} = I_c \gg (C - 1)$$ + +$$DQS_{FF} = I' \gg (E + C - 1)$$ + +TABLE 12/G.727 + +##### **16 kbit/s quantizer output levels** + +| $I'$ or $I_c$ | $DQS_{FF}$ or | $DQLN_{FF}$ or | +|---------------|---------------|----------------| +| 12 | $DQS_{FB}$ | $DQLN_{FB}$ | +| 01 | 0 | 365 | +| 00 | 0 | 116 | +| 11 | 1 | 116 | +| 10 | 1 | 365 | + +TABLE 13/G.727 + +##### **24 kbit/s quantizer output levels** + +| $I'$ or $I_c$ | $DQS_{FF}$ or | $DQLN_{FF}$ or | +|---------------|---------------|----------------| +| 123 | $DQS_{FB}$ | $DQLN_{FB}$ | +| 011 | 0 | 395 | +| 010 | 0 | 307 | +| 001 | 0 | 199 | +| 000 | 0 | 4085 | +| 111 | 1 | 4085 | +| 110 | 1 | 199 | +| 101 | 1 | 307 | +| 100 | 1 | 395 | + +TABLE 14/G.727 + +##### **32 kbit/s quantizer output levels** + +| $I'$ or $I_c$ | DQS FF or | DQLN FF or | +|---------------|----------------------|-----------------------| +| 1234 | DQS FB | DQLN FB | +| 0111 | 0 | 428 | +| 0110 | 0 | 377 | +| 0101 | 0 | 332 | +| 0100 | 0 | 285 | +| 0011 | 0 | 232 | +| 0010 | 0 | 165 | +| 0001 | 0 | 68 | +| 0000 | 0 | 3961 | +| 1111 | 1 | 3961 | +| 1110 | 1 | 68 | +| 1101 | 1 | 165 | +| 1100 | 1 | 232 | +| 1011 | 1 | 285 | +| 1010 | 1 | 332 | +| 1001 | 1 | 377 | +| 1000 | 1 | 428 | + +TABLE 15/G.727 + +##### **40 kbit/s quantizer output levels** + +| $I'$ | DQS FF | DQLN FF | +|-------|-------------------|--------------------| +| 12345 | | | +| 01111 | 0 | 456 | +| 01110 | 0 | 419 | +| 01101 | 0 | 391 | +| 01100 | 0 | 367 | +| 01011 | 0 | 344 | +| 01010 | 0 | 321 | +| 01001 | 0 | 298 | +| 01000 | 0 | 273 | +| 00111 | 0 | 246 | +| 00110 | 0 | 217 | +| 00101 | 0 | 184 | +| 00100 | 0 | 145 | +| 00011 | 0 | 97 | +| 00010 | 0 | 34 | +| 00001 | 0 | 4035 | +| 00000 | 0 | 3832 | +| 11111 | 1 | 3832 | +| 11110 | 1 | 4035 | +| 11101 | 1 | 34 | +| 11100 | 1 | 97 | +| 11011 | 1 | 145 | +| 11010 | 1 | 184 | +| 11001 | 1 | 217 | +| 11000 | 1 | 246 | +| 10111 | 1 | 273 | +| 10110 | 1 | 298 | +| 10101 | 1 | 321 | +| 10100 | 1 | 344 | +| 10011 | 1 | 367 | +| 10010 | 1 | 391 | +| 10001 | 1 | 419 | +| 10000 | 1 | 456 | + +*Note 1* – The $I$ values are received starting with bit 1. + +##### ADDA + +Inputs: DQLNFB or DQLNFF, Y + +Output: DQLFB or DQLFF + +Function: Addition of scale factor to logarithmic version of quantized difference signal. + +Note: Subscripts are given for the feed-back path. Figure 7/G.727 and equation are also valid when substituting DQLNFF for DQLNFB and DQLFF for DQLFB. + +$$DQL_{FB} = (DQLN_{FB} + (Y \gg 2)) \& 4095$$ + +##### ANTILOG + +Inputs: DQLFB, DQSFB + +Output: DQFB + +Function: Convert quantized difference signal from the logarithmic to the linear domain. + +Note: Figure 7/G.727 and equations are given for the feed-back path. The equations are also valid when substituting DQLFF for DQLFB, DQSFF for DQSFB and DQFF for DQFB. + +$$DS = DQL_{FB} \gg 11 \quad | \text{ Extract 4-bit exponent}$$ + +$$DEX = (DQL_{FB} \gg 7) \& 15$$ + +$$DMN = DQL_{FB} \& 127 \quad | \text{ Extract 7-bit mantissa}$$ + +$$DQT = (1 \ll 7) + DMN \quad | \text{ Convert mantissa to linear using}$$ + +$$DQMAG = \begin{cases} (DQT \ll 7) \gg (14 - DEX), & DS = 0 \\ 0, & DS = 1 \end{cases} \quad | \text{ approximation } 2^x = 1 + x$$ + +$$DQ_{FB} = (DQS \ll 14) + DQMAG \quad | \text{ Attach sign bit to signed magnitude word}$$ + +#### 6.2.5 Quantizer scale factor adaptation + +![Block diagram of Quantizer scale factor adaptation. The input Ic enters a FUNCTW block, producing WI. WI enters a FILTD block, producing YUT. YUT enters a LIMB block, producing YUP. YUP enters a DELAY block, which also receives input R, producing YU. YU enters a MIX block, which also receives input AL, producing the final output Y. A feedback path from the output Y goes through a FILTE block, then a DELAY block (receiving input R), producing YL. YL enters the MIX block. The output of the FILTE block also feeds back to the FILTD block. A label T1508370-92 is at the bottom right.](58c06f7ad7d3d86e8161f0a2218c7b54_img.jpg) + +Block diagram of Quantizer scale factor adaptation. The input Ic enters a FUNCTW block, producing WI. WI enters a FILTD block, producing YUT. YUT enters a LIMB block, producing YUP. YUP enters a DELAY block, which also receives input R, producing YU. YU enters a MIX block, which also receives input AL, producing the final output Y. A feedback path from the output Y goes through a FILTE block, then a DELAY block (receiving input R), producing YL. YL enters the MIX block. The output of the FILTE block also feeds back to the FILTD block. A label T1508370-92 is at the bottom right. + +FIGURE 8/G.727 +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{reset value given in column 4 of Table 3/G.727}, & R = 1 \end{cases} \quad | \text{ reset}$$ + + +--- + +##### FILTD + +Inputs: WI, Y + +Output: YUT + +Function: Update of fast quantizer scale factor. + +$$DIF = ((WI \ll 5) + 131072 - Y) \& 131071 \quad | \text{ Compute difference}$$ + +$$DIFS = DIF \gg 16 \quad |$$ + +$$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 \quad | \text{ Compute difference}$$ + +$$DIFS = DIF \gg 13 \quad | \text{ Time constant is } 1/64$$ + +$$DIFSX = \begin{cases} DIF, & DIFS = 0 \\ DIF + 507904, & DIFS = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Sign extension} \\ | \end{array}$$ + +$$YLP = (YL + DIFSX) \& 524287$$ + + +--- + +##### FUNCTW + +Input: $I_c$ + Output: $WI$ + Function: Map quantizer output into logarithmic version of scale factor multiplier. + +$$IS = I_c \gg (C - 1), C = 2, 3, 4.$$ + +For $C = 2$ : + +$$IM = \begin{cases} I_c \& 1, & IS = 0 \\ (3 - I_c) \& 1, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 439, & IM = 1 \\ 4074, & IM = 0 \end{cases} \quad \left| \begin{array}{c} | \\ | \text{ Scale factor multipliers} \\ | \end{array} \right.$$ + +For $C = 3$ : + +$$IM = \begin{cases} I_c \& 3, & IS = 0 \\ (7 - I_c) \& 3, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 582, & IM = 3 \\ 137, & IM = 2 \\ 30, & IM = 1 \\ 4092, & IM = 0 \end{cases} \quad \left| \begin{array}{c} | \\ | \text{ Scale factor multipliers} \\ | \end{array} \right.$$ + +For $C = 4$ : + +$$IM = \begin{cases} I_c \& 7, & IS = 0 \\ (15 - I_c) \& 7, & IS = 1 \end{cases}$$ + +$$WI = \begin{cases} 1108, & IM = 7 \\ 340, & IM = 6 \\ 184, & IM = 5 \\ 98, & IM = 4 \\ 50, & IM = 3 \\ 27, & IM = 2 \\ 4, & IM = 1 \\ 4084, & IM = 0 \end{cases} \quad \left| \begin{array}{c} | \\ | \text{ Scale factor multipliers} \\ | \end{array} \right.$$ + +##### 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 \\ 5120, & GEUL = 0 \\ YUT, & \text{otherwise} \end{cases} \quad \begin{array}{l} | \text{ Set lower limit to 1.06} \\ | \text{ Set upper limit to 10.00} \end{array}$$ + +##### MIX + +Inputs: AL, YU, YL + Output: Y + Function: Form linear combination of fast and slow quantizer scale factors. + +$$\begin{array}{l} DIF = (YU + 16384 - (YL \gg 6)) \& 16383 \\ DIFS = DIF \gg 13 \end{array} \quad \begin{array}{l} | \text{ Compute difference} \\ | \end{array}$$ + +$$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}$$ + +$$PRODM = (DIFM * AL) \gg 6 \quad \begin{array}{l} | \text{ Compute magnitude} \\ | \text{ of product} \end{array}$$ + +$$PROD = \begin{cases} PRODM, & DIFS = 0 \\ (16384 - PRODM) \& 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$$ + +#### 6.2.6 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: FILTA and FILTB. FILTA produces DMSP and has a feedback loop with a DELAY block labeled DMS. FILTB produces DMLP and has a feedback loop with a DELAY block labeled DML. Both DMSP and DMLP enter a SUBTC block, which also receives inputs Y and TDP (producing AX). The output of SUBTC enters a FILTC block, producing APP. APP enters a TRIGA block, which also receives input TR, producing APR. APR enters a DELAY block, which also receives input R, producing AP. AP enters a LIMA block, producing AL. A feedback line from the LIMA output goes back to the TRIGA block. The diagram is labeled T1508380-92.](85e2327652d513a7fee8fdbf97ad06f1_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: FILTA and FILTB. FILTA produces DMSP and has a feedback loop with a DELAY block labeled DMS. FILTB produces DMLP and has a feedback loop with a DELAY block labeled DML. Both DMSP and DMLP enter a SUBTC block, which also receives inputs Y and TDP (producing AX). The output of SUBTC enters a FILTC block, producing APP. APP enters a TRIGA block, which also receives input TR, producing APR. APR enters a DELAY block, which also receives input R, producing AP. AP enters a LIMA block, producing AL. A feedback line from the LIMA output goes back to the TRIGA block. The diagram is labeled T1508380-92. + +FIGURE 9/G.727 +Adaptation speed control + +##### DELAY + +See § 6.2.5 for specification. + +##### FILTA + +Inputs: FI, DMS + +Output: DMSP + +Function: Update of short-term average of F(I). + +$$DIF = ((FI \ll 9) + 8192 - DMS) \& 8191$$ + +| Compute difference + +$$DIFS = DIF \gg 12$$ + +| + +$$DIFSX = \begin{cases} DIF \gg 5, & DIFS = 0 \\ (DIF \gg 5) + 3840, & DIFS = 1 \end{cases}$$ + +| +| Time constant is 1/32, +| Sign extension +| + +$$DMSP = (DIFSX + DMS) \& 4095$$ + +##### FILTB + +Inputs: FI, DML + Output: DMLP + Function: Update of long-term average of F(I). + +$$\begin{aligned} DIF &= ((FI \ll 11) + 32768 - DML) \& 32767 && | \text{Compute difference} \\ DIFS &= DIF \gg 14 && | \end{aligned}$$ + +$$DIFSX = \begin{cases} DIF \gg 7, & DIFS = 0 \\ (DIF \gg 7) + 16128, & DIFS = 1 \end{cases} \quad \begin{aligned} &| \\ &| \text{Time constant is } 1/28, \\ &| \text{Sign extension} \\ &| \end{aligned}$$ + +$$DMLP = (DIFSX + DML) \& 16383$$ + + +--- + +##### FILTC + +Inputs: AX, AP + Output: APP + Function: Low pass filter of speed control parameter. + +$$\begin{aligned} DIF &= ((AX \ll 9) + 2048 - AP) \& 2047 && | \text{Compute difference} \\ DIFS &= DIF \gg 10 && | \end{aligned}$$ + +$$DIFSX = \begin{cases} DIF \gg 4, & DIFS = 0 \\ (DIF \gg 4) + 896, & DIFS = 1 \end{cases} \quad \begin{aligned} &| \\ &| \text{Time constant is } 1/16, \\ &| \text{Sign extension} \\ &| \end{aligned}$$ + +$$APP = (DIFSX + AP) \& 1023$$ + + +--- + +##### FUNCTF + +Input: $I_c$ + +Output: FI + +Function: Map quantizer output into the F(I) function. + +$$IS = I_c \gg (C - 1), C = 2, 3, 4.$$ + +For C = 2: + +$$IM = \begin{cases} I_c \& 1, & IS = 0 \\ (3 - I_c) \& 1, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 7, & IM = 1 \\ 0, & IM = 0 \end{cases}$$ + +For C = 3: + +$$IM = \begin{cases} I_c \& 3, & IS = 0 \\ (7 - I_c) \& 3, & IS = 1 \end{cases}$$ + +$$FI = \begin{cases} 7, & IM = 3 \\ 2, & IM = 2 \\ 1, & IM = 1 \\ 0, & IM = 0 \end{cases}$$ + +For C = 4: + +$$IM = \begin{cases} I_c \& 7, & IS = 0 \\ (15 - I_c) \& 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}$$ + +##### 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}$$ + +#### 6.2.7 Adaptive predictor and reconstructed signal calculator (feedback path) + +![Block diagram of Adaptive predictor and reconstructed signal calculator. The diagram shows signal flow from input DQ_FB through various processing blocks including ADDC, DELAY, FLOATA, XOR, UPB, TRIGB, FMULT, ADDB, FLOATB, UPA1, LIMD, UPA2, LIMC, and a shared ACCUM block. Control signals like SEZ, R, SE, TR, SIGPK, PK0, PK1, PK2, and SR_FFB are also shown.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +The diagram illustrates the signal processing pipeline for an adaptive predictor and reconstructed signal calculator. The main input is $DQ_{FB}$ , which branches into several processing paths: + +- Top Path:** $DQ_{FB}$ enters an **ADDC** block along with **SEZ**. The output of **ADDC** is split: one branch goes through a **DELAY** block (receiving **R**) to produce **PK2**; another branch goes through another **DELAY** block (receiving **R**) to produce **PK1**. A third branch from **ADDC** produces **SIGPK** and **PK0**. +- Middle Path:** $DQ_{FB}$ enters a **FLOATA** block, producing **DQ0**. **DQ0** passes through a **DELAY** block (receiving **R**) to become **DQ1**. **DQ1** then splits: one branch goes through a **DELAY** block (receiving **R**) to become **DQ6**; another branch is labeled **DQ5** and also goes through a **DELAY** block (receiving **R**) to become **DQ6**. +- Bottom Path:** $DQ_{FB}$ enters an **XOR** block, producing **U1**. **U1** enters a **UPB** block, producing **B1P**. **B1P** enters a **TRIGB** block (receiving **TR**), producing **B1R**. **B1R** passes through a **DELAY** block (receiving **R**) to become **B1**. **B1** enters an **FMULT** block, producing **WB1**. **WB1** and **DQ6** both enter another **FMULT** block, which produces **WB6**. +- Right Path:** $DQ_{FB}$ enters an **ADDB** block along with **SE**. The output of **ADDB** enters a **FLOATB** block, producing **SR0** and **SR\_{FB}**. **SR0** passes through a **DELAY** block (receiving **R**) to become **SR1**. +- Parallel Processing:** + - Left Sub-path:** **SIGPK**, **PK0**, **PK1**, and **PK2** enter a **UPA2** block, producing **A2T**. **A2T** enters a **LIMC** block, producing **A2P**. **A2P** enters a **TRIGB** block (receiving **TR**), producing **A2R**. **A2R** passes through a **DELAY** block (receiving **R**) to become **A2**. **A2** enters an **FMULT** block, producing **WA2**. + - Right Sub-path:** **SIGPK**, **PK0**, and **PK1** enter a **UPA1** block, producing **A1T**. **A1T** enters a **LIMD** block, producing **A1P**. **A1P** enters a **TRIGB** block (receiving **TR**), producing **A1R**. **A1R** passes through a **DELAY** block (receiving **R**) to become **A1**. **A1** enters an **FMULT** block, producing **WA1**. +- Accumulation:** **WA2** and **WA1** both enter a large **ACCUM** block. The **ACCUM** block outputs **SEZ** and **SE**. A feedback signal from the **ACCUM** block passes through a **DELAY** block (receiving **R**) to become **SR2**, which is then fed back into the **UPA1** and **UPA2** blocks. + +Block diagram of Adaptive predictor and reconstructed signal calculator. The diagram shows signal flow from input DQ\_FB through various processing blocks including ADDC, DELAY, FLOATA, XOR, UPB, TRIGB, FMULT, ADDB, FLOATB, UPA1, LIMD, UPA2, LIMC, and a shared ACCUM block. Control signals like SEZ, R, SE, TR, SIGPK, PK0, PK1, PK2, and SR\_FFB are also shown. + +FIGURE 10/G.727 + +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$$ + + +--- + +##### ADDB + +Inputs: DQFB or DQFF, SE + +Output: SRFB or DQFF + +Function: Addition of quantized difference signal and signal estimate to form reconstructed signal. + +Note: Subscripts are given for the feed-back path. Equation is also valid when substituting DQFF for DQFB and DQFF for DQFB. + +$$DQS_{FB} = DQ_{FB} \gg 14$$ + +$$DQI = \begin{cases} DQ_{FB}, & DQS_{FB} = 0 \\ (65536 - (DQ_{FB} \& 16383)) \& 65535, & DQS_{FB} = 1 \end{cases} \quad | \text{ 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} \quad | \text{ Sign extension}$$ + +$$SR_{FB} = (DQI + SEI) \& 65535$$ + + +--- + +##### ADDC + +Inputs: DQFB, SEZ + Output: PK0, SIGPK + Function: Obtain sign of addition of quantized difference signal and partial signal estimate. + +$$DQS_{FB} = DQ_{FB} \gg 14$$ + +$$DQI = \begin{cases} DQ_{FB}, & DQS_{FB} = 0 \\ (65536 - (DQ_{FB} \& 16383)) \& 65535, & DQS_{FB} = 1: \end{cases} \quad \begin{array}{l} | \\ | \text{ Convert signed} \\ | \text{ magnitude to} \\ | \text{ two's complement} \end{array}$$ + +$$SEZS = SEZ \gg 14$$ + +$$SEZI = \begin{cases} SEZ, & SEZS = 0 \\ (1 \ll 15) + SEZ, & SEZS = 1 \end{cases} \quad \begin{array}{l} | \\ | \text{ Sign extension} \\ | \end{array}$$ + +$$DQSEZ = (DQI + SEZI) \& 65535$$ + +$$PK0 = DQSEZ \gg 15$$ + +$$SIGPK = \begin{cases} 1, & DQSEZ = 0 \\ 0, & \text{otherwise} \end{cases}$$ + +##### DELAY + +See § 6.2.5 for specification. + +##### FLOATA + +Input: DQFB + Output: DQ0 + Function: Convert 15-bit signed magnitude to floating point. + +$$DQS_{FB} = DQ_{FB} \gg 14$$ + +$$MAG = DQ_{FB} \& 16383 \quad | \text{ Compute magnitude}$$ + +$$EXP = \begin{cases} 14, & 8192 \leq MAG \\ 13, & 4096 \leq MAG \leq 8191 \\ \vdots, & \vdots \\ 2, & 2 \leq MAG \leq 3 \\ 1, & MAG = 1 \\ 0, & MAG = 0 \end{cases} \quad | \begin{matrix} \\ \\ \\ \\ \text{Compute exponent} \\ \\ \\ \end{matrix}$$ + +$$MANT = \begin{cases} 1 \ll 5, & MAG = 0 \\ (MAG \ll 6) \gg EXP, & \text{otherwise} \end{cases} \quad | \begin{matrix} \text{Compute mantissa with a} \\ | \text{ 1 in the most} \\ | \text{ significant bit} \end{matrix}$$ + +$$DQ_0 = (DQS_{FB} \ll 10) + (EXP \ll 6) + MANT \quad | \begin{matrix} \text{Combine sign bit, 4 exponent} \\ | \text{ bits and 6 mantissa bits} \\ | \text{ into one 11-bit word} \end{matrix}$$ + +##### FLOATB + +Input: $SR_{FB}$ + Output: $SR0$ + Function: Convert 16-bit two's complement to floating point. + +$$SRS = SR_{FB} \gg 15$$ + +$$MAG = \begin{cases} SR_{FB}, & SRS = 0 \\ (65536 - SR_{FB}) \& 32767, & SRS = 1 \end{cases} \quad \left| \begin{array}{l} \\ \text{Compute magnitude} \\ \end{array} \right.$$ + +$$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 \left| \begin{array}{l} \\ \\ \\ \text{Compute exponent} \\ \\ \end{array} \right.$$ + +$$MANT = \begin{cases} 1 \ll 5, & MAG = 0 \\ (MAG \ll 6) \gg EXP, & \text{otherwise} \end{cases} \quad \left| \begin{array}{l} \text{Compute mantissa with a} \\ \text{1 in the most} \\ \text{significant bit} \end{array} \right.$$ + +$$SR0 = (SRS \ll 10) + (EXP \ll 6) + MANT \quad \left| \begin{array}{l} \text{combine sign bit, 4 exponent} \\ \text{bits and 6 mantissa bits} \\ \text{into one 11-bit word} \end{array} \right.$$ + +##### 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}$$ + +| Convert +| floating +| point to +| magnitude + +$$WAn = \begin{cases} WAnMAG, & WAnS = 0 \\ (65536 - WAnMAG) \& 65535, & WAnS = 1 \end{cases}$$ + +| Convert mag. to +| two's complement + +##### LIMC + +Input: A2T + Output: A2P + Function: Limits on $a_2$ coefficient of second order predictor. + +$$A2UL = 12288 \quad | \text{ Upper limit of } +0.75$$ + +$$A2LL = 53248 \quad | \text{ 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 \quad | (1 - \epsilon) \text{ where} \\ | \epsilon = 1/16$$ + +$$A1UL = (OME + 65536 - A2P) \& 65535 \quad | \text{ Compute upper limit}$$ + +$$A1LL = (A2P + 65536 - OME) \& 65535 \quad | \text{ 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 | \text{ Leak factor} = 1/256$$ + +$$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 \text{ ** } PK1 \quad | \text{ 1-bit "exclusive or"}$$ + +$$PKS2, = PK0 \text{ ** } 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 |$$ + +##### UPB + +Inputs: $U_n, B_n, DQ_{FB}$ + Output: $BnP$ + Function: Update for coefficients of sixth order predictor. + +$$DQMAG = DQ_{FB} \& 16383$$ + +$$UGBn = \begin{cases} 128, & U_n = 0 \text{ and } DQMAG \neq 0 \\ 65408, & U_n = 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 = B_n \gg 15$$ + +$$ULBn = \begin{cases} (65536 - (B_n \gg 8)) \& 65535, & BnS = 0 \\ (65536 - ((B_n \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 &= (B_n + UBn) \& 65535 \end{aligned} \quad \left| \begin{array}{l} \text{Compute update} \\ \end{array} \right.$$ + +##### XOR + +Inputs: $DQ_n, DQ_{FB}$ + Output: $U_n$ + Function: One bit “exclusive or” of sign of difference signal and sign of delayed difference signal. + +$$\begin{aligned} DQS_{FB} &= DQ_{FB} \gg 14 \\ DQnS &= DQ_n \gg 10 \end{aligned}$$ + +$$U_n = DQS_{FB} ** DQnS \quad \left| \begin{array}{l} \text{1-bit “exclusive or”} \end{array} \right.$$ + +6.2.8 Reconstructed signal calculator (feed-forward path) + See § 6.2.7 for specification. + +![Block diagram of the reconstructed signal calculator (feed-forward path). A block labeled 'ADDB' has an input 'DQ_FF' on the left and an output 'SR_FF' on the right. A control input 'SE' is shown below the block with an upward arrow. The identifier 'T1508400-92' is located to the right of the block.](12c19090355e19922e23044633b9d1ea_img.jpg) + +Block diagram of the reconstructed signal calculator (feed-forward path). A block labeled 'ADDB' has an input 'DQ\_FF' on the left and an output 'SR\_FF' on the right. A control input 'SE' is shown below the block with an upward arrow. The identifier 'T1508400-92' is located to the right of the block. + +FIGURE 11/G.727 +**Reconstructed signal calculator (feed-forward path)** + +#### 6.2.9 Tone and transition detector + +![Block diagram of the tone and transition detector. The signal flow is: 'A2P' input to a 'TONE' block, which outputs 'TDP'. 'TDP' is input to a 'TRIGB' block, which also receives 'TR' from above and outputs 'TDR'. 'TDR' is input to a 'DELAY' block, which also receives 'R' from above and outputs 'TD'. 'TD' is input to a 'TRANS' block, which also receives 'YL' and 'DQ_FB' from above and outputs 'TR'. The identifier 'T1508410-92' is located below the 'TRANS' block.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Block diagram of the tone and transition detector. The signal flow is: 'A2P' input to a 'TONE' block, which outputs 'TDP'. 'TDP' is input to a 'TRIGB' block, which also receives 'TR' from above and outputs 'TDR'. 'TDR' is input to a 'DELAY' block, which also receives 'R' from above and outputs 'TD'. 'TD' is input to a 'TRANS' block, which also receives 'YL' and 'DQ\_FB' from above and outputs 'TR'. The identifier 'T1508410-92' is located below the 'TRANS' block. + +FIGURE 12/G.727 +**Tone and transition detector** + +##### DELAY + +See § 6.2.5 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, DQFB + Output: TR + Function: Transition detector. + +$$DQMAG = DQ_{FB} \& 16383$$ + +$$YLINT = YL \gg 15$$ + +$$YLFRAC = (YL \gg 10) \& 31$$ + +$$THR1 = (32 + YLFRAC) \ll YLINT$$ + +$$THR2 = \begin{cases} 31 \ll 9, YLINT > 8 \\ THR1, \text{ otherwise} \end{cases}$$ + +$$DQTHR = (THR2 + (THR2 \gg 1)) \gg 1$$ + +$$TR = \begin{cases} 1, DQMAG > DQTHR \text{ and } TD = 1 \\ 0, \text{ otherwise} \end{cases}$$ + +##### TRIGB + +See § 6.2.7 for specification. + +#### 6.2.10 Output PCM format conversion and synchronous coding adjustment + +![Block diagram of Output PCM format conversion and synchronous coding adjustment. The diagram shows a sequence of blocks: COMPRESS, EXPAND, SUBTA, LOG, SUBTB, and SYNC. Inputs include SR_FF, LAW (for COMPRESS, EXPAND, and SYNC), SE (for SUBTA), Y (for SUBTB), and I'(k) (for SYNC). The output is SD. There are feedback loops: DSX from LOG to EXPAND, DLX from LOG to SUBTB, and DLNX from SUBTB to SYNC. A line labeled T1508420-92 is also present.](981668c6be5792b778cccb1af38477e2_img.jpg) + +``` + + graph LR + SR_FF[SR_FF] --> COMPRESS[COMPRESS] + LAW1[LAW] --> COMPRESS + COMPRESS -- SP --> EXPAND[EXPAND] + LAW2[LAW] --> EXPAND + EXPAND -- SLX --> SUBTA[SUBTA] + SE --> SUBTA + SUBTA -- DX --> LOG[LOG] + LOG -- DSX --> EXPAND + LOG -- DLX --> SUBTB[SUBTB] + Y --> SUBTB + SUBTB -- DLNX --> SYNC[SYNC] + LAW3[LAW] --> SYNC + I_prime_k[I'(k)] --> SYNC + SYNC -- SD --> SD + +``` + +Block diagram of Output PCM format conversion and synchronous coding adjustment. The diagram shows a sequence of blocks: COMPRESS, EXPAND, SUBTA, LOG, SUBTB, and SYNC. Inputs include SR\_FF, LAW (for COMPRESS, EXPAND, and SYNC), SE (for SUBTA), Y (for SUBTB), and I'(k) (for SYNC). The output is SD. There are feedback loops: DSX from LOG to EXPAND, DLX from LOG to SUBTB, and DLNX from SUBTB to SYNC. A line labeled T1508420-92 is also present. + +FIGURE 13/G.727 + +Output PCM format conversion and synchronous coding adjustment + +##### COMPRESS (decoder only) + +Input: SRFF, LAW + Output: SP + Function: Convert from uniform PCM to either A-law or μ-law PCM. + +$$IS = SR_{FF} \gg 15$$ + +$$IM = \begin{cases} SR_{FF}, & IS = 0 \\ (65536 - SR_{FF}) \& 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/G.711, 1b/G.711, 2a/G.711 and 2b/G.711) in the following way: + +$$SP = \begin{cases} \text{character signal after even bit inversion deduced} \\ \text{from Table 1a/G.711 (column 6),} & IS = 0 \text{ and } LAW = 1 \\ \text{character signal after even bit inversion deduced} \\ \text{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 μ-law in the vicinity of the origin are given in the table below: + +TABLE 16/G.727 +**Conversion for A-law and μ-law examples** + +| IS | IMAG | PCM code word SP | | +|----|------|------------------|----------| +| | | A-law | μ-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 § 6.2.1 for specification. Substitute SP for S as input and SLX for SL as output. + +--- + +##### SUBTA + +See § 6.2.1 for specification. Substitute SLX for SL as input and DX for D as output. + +--- + +##### LOG + +See § 6.2.2 for specification. Substitute DX for D as input, DLX for DL and DSX for DS as outputs. + +--- + +##### SUBTB + +See § 6.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. + +$$IS = I' \gg (E + C - 1)$$ + +For $E + C = 2$ : + +$$IM = \begin{cases} I' + 2, & IS = 0 \\ I' \& 1, & IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 17/G.727 + +###### **ID definition for E + C = 2** + +| 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 (E + C = 3): + +$$IM = \begin{cases} I' + 4, IS = 0 \\ I' + 3, IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 18/G.727 + +###### **ID definition for E + C = 3** + +| DSX | DLNX | ID | | +|-----|-----------|----|-------------------------------------------| +| 0 | 356-2047 | 7 | | +| 0 | 261- 355 | 6 | | +| 0 | 123- 260 | 5 | | +| 0 | 0- 122 | 4 | – Positive portion of decision interval | +| 0 | 2048-4095 | 4 | – Negative portion of decision interval | +| 1 | 2048-4095 | 3 | – Negative portion of decision interval | +| 1 | 0- 122 | 3 | – Positive portion of decision interval | +| 1 | 123- 260 | 2 | | +| 1 | 261- 355 | 1 | | +| 1 | 356-2047 | 0 | | + +For (E + C = 4): + +$$IM = \begin{cases} I' + 8, IS = 0 \\ I' + 7, IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 19/G.727 + +###### **ID definition for E + C = 4** + +| DSX | DLNX | ID | | +|-----|-----------|----|-------------------------------------------| +| 0 | 405-2047 | 15 | | +| 0 | 356- 404 | 14 | | +| 0 | 310- 355 | 13 | | +| 0 | 261- 309 | 12 | | +| 0 | 202- 260 | 11 | | +| 0 | 123- 201 | 10 | | +| 0 | 0- 122 | 9 | -- Positive portion of decision interval | +| 0 | 4089-4095 | 9 | -- Negative portion of decision interval | +| 0 | 2048-4088 | 8 | | +| 1 | 2048-4088 | 7 | | +| 1 | 4089-4095 | 6 | -- Negative portion of decision interval | +| 1 | 0- 122 | 6 | -- Positive portion of decision interval | +| 1 | 123- 201 | 5 | | +| 1 | 202- 260 | 4 | | +| 1 | 261- 309 | 3 | | +| 1 | 310- 355 | 2 | | +| 1 | 356- 404 | 1 | | +| 1 | 405-2047 | 0 | | + +For (E + C = 5): + +$$IM = \begin{cases} I' + 16, IS = 0 \\ I' \& 15, IS = 1 \end{cases}$$ + +ID is defined according to the following table: + +TABLE 20/G.727 + +###### **ID definition for E + C = 5** + +| DSX | DLNX | ID | | +|-----|-----------|----|-------------------------------------------| +| 0 | 439-2047 | 31 | | +| 0 | 405- 438 | 30 | | +| 0 | 380- 404 | 29 | | +| 0 | 356- 379 | 28 | | +| 0 | 333- 355 | 27 | | +| 0 | 310- 332 | 26 | | +| 0 | 286- 309 | 25 | | +| 0 | 261- 285 | 24 | | +| 0 | 233- 260 | 23 | | +| 0 | 202- 232 | 22 | | +| 0 | 166- 201 | 21 | | +| 0 | 123- 165 | 20 | | +| 0 | 69- 122 | 19 | | +| 0 | 0- 68 | 18 | – Positive portion of decision interval | +| 0 | 4089-4095 | 18 | – Negative portion of decision interval | +| 0 | 3961-4088 | 17 | | +| 0 | 2048-3960 | 16 | | +| 1 | 2048-3960 | 15 | | +| 1 | 3961-4088 | 14 | | +| 1 | 4089-4095 | 13 | – Negative portion of decision interval | +| 1 | 0- 68 | 13 | – Positive portion of decision interval | +| 1 | 69- 122 | 12 | | +| 1 | 123- 165 | 11 | | +| 1 | 166- 201 | 10 | | +| 1 | 202- 232 | 9 | | +| 1 | 233- 260 | 8 | | +| 1 | 261- 285 | 7 | | +| 1 | 286- 309 | 6 | | +| 1 | 310- 332 | 5 | | +| 1 | 333- 355 | 4 | | +| 1 | 356- 379 | 3 | | +| 1 | 380- 404 | 2 | | +| 1 | 405- 438 | 1 | | +| 1 | 439-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$ ). + +$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 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 21/G.727 + +##### **Re-encoding for A-law and $\mu$ -law** + +| 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 above for the exact representation of SP (and SD). + +# APPENDIX I + +(to Recommendation G.727) + +## **Digital test sequences for the verification of the algorithms in G.727** + +This Appendix gives information on the digital test sequences which have been chosen to verify implementations of the algorithms in G.727. 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. 12/XV, 1991). + +### I.1 *Purpose of digital test sequences* + +Digital sequences are used to verify the conformance of an implementation of a digital transcoding algorithm. The sequences are chosen to exercise the major arithmetic components and thus given 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. + +### I.2 *Diskette interface and format* + +Copies of the digital test sequences are available from the ITU on twelve 5-1/4" diskettes. The diskettes were created under MS-DOS operating system (version 3.2 or newer), and are of the 1.2 Mbyte high density double-sided 96 tracks per inch 51/4 MS-DOS format. \ No newline at end of file diff --git a/marked/G/T-REC-G.732-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.732-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.732-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.732-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.732-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a99ac059ea38a7f7ad3a721ef7e9b9c896ae3206 --- /dev/null +++ b/marked/G/T-REC-G.732-198811-I_PDF-E/raw.md @@ -0,0 +1,247 @@ + + +![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.732** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL ASPECTS OF DIGITAL TRANSMISSION +SYSTEMS** + +**TERMINAL EQUIPMENTS** + +--- + +**CHARACTERISTICS OF PRIMARY PCM +MULTIPLEX EQUIPMENT OPERATING AT +2048 kbit/s** + +**ITU-T Recommendation G.732** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +- 1 ITU-T Recommendation G.732 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 2048 kbit/s** + +*(Geneva, 1972; further amended)* + +## **1 General characteristics** + +### 1.1 *Fundamental characteristics* + +The encoding law used is the A-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 256. + +*Note* - The inversion of bits 2, 4, 6, and 8 is covered by the encoding law and is applicable only to voice-channel time slots. + +### 1.2 *Bit rate* + +The nominal bit rate is 2048 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. + +*Note* - Further study is required on the effect of jitter of the incoming signal on the timing signal, and on the measures to be taken in case of loss of the incoming signal or the external source. + +## **2 Frame structure** + +Refer to §§ 3.3.1 and 3.3.2 of Recommendation G.704 for frame structure and use of derived channel time slots. + +*Note* - If channel time slot 16 which is assigned to signalling as covered in § 5 below is not needed for signalling it may be used for purposes other than a voice channel encoded within the PCM multiplex equipment. + +## **3 Loss and recovery of frame alignment** + +The strategy for the loss and recovery of frame alignment should be according to Recommendation G.706, § 4.1. + +## **4 Fault conditions and consequent actions** + +### 4.1 *Fault conditions* + +The PCM multiplex equipment should detect the following fault conditions: + +#### 4.1.1 Failure of power supply. + +#### 4.1.2 Failure of codec (except when using single-channel codecs). + +As a minimum requirement this fault condition should be recognized when, for at least one signal level in the range -21 to -6 dBm0, the signal-to-quantizing noise ratio performance of the local codec is 18 dB or more below the level recommended in Recommendation G.712. + +#### 4.1.3 Loss of incoming signal at the 64 kbit/s input port (time slot 16). + +*Note 1* - The detection of this fault condition is not mandatory when channel associated signalling is used and the signalling multiplex is situated within a few metres of the PCM multiplex equipment. + +*Note 2* - The detection of this fault condition is not mandatory when contradirectional interfaces are used. + +#### 4.1.4 Loss of the incoming signal at 2048 kbit/s. + +*Note* - The detection of this fault condition is required only when it does not result in an indication of loss of frame alignment. + +#### 4.1.5 Loss of frame alignment. + +#### 4.1.6 Excessive bit error ratio detected by monitoring the frame alignment signal. + +##### 4.1.6.1 With a random bit error ratio of $\leq 10^{-4}$ , the probability of activating the indication of fault condition within a few seconds should be less than $10^{-6}$ . + +With a random bit error ratio of $\geq 10^{-3}$ , the probability of activating the indication of fault condition within a few seconds should be higher than 0.95. + +##### 4.1.6.2 With a random bit error ratio of $\geq 10^{-3}$ , the probability of deactivating the indication of fault condition within a few seconds should be almost 0. + +With a random bit error ratio of $\leq 10^{-4}$ , the probability of deactivating the indication of fault condition within a few seconds should be higher than 0.95. + +*Note* - The activating and the deactivating period specified as "a few seconds" is intended to be in the order of 4 to 5 seconds. + +#### 4.1.7 Alarm indication received from the remote PCM multiplex equipment (see § 4.2.3 below). + +### 4.2 *Consequent actions* + +Further to the detection of a fault condition, appropriate actions should be taken as specified in Table 1/G.732. The consequent actions are as follows: + +#### 4.2.1 Service alarm indication generated to signify that the service provided by the PCM multiplex is no longer available. This indication should be forwarded at least to the switching and/or signalling multiplex equipment depending upon the arrangements provided. The indication should be given as soon as possible and not later than 2 ms after detection of the relevant fault condition. + +This specification, taking into account the specification given in § 3 above, is equivalent to recommending that the average time to detect a loss of frame alignment and to give the relevant indication should not be greater than 3 ms. + +When using common-channel signalling, the indication should be forwarded to the switching equipment by means of a separate interface on the PCM multiplex equipment. + +4.2.2 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 General Notes below to § 4.2) is detected, the prompt maintenance alarm indication associated with loss of frame alignment (see § 4.1.5 above) and excessive error ratio (see § 4.1.6 above) should be inhibited, while the rest of the consequent actions are in accordance with those associated in Table 1/G.732 with the two fault conditions. + +*Note -* The location and provision of any visual and/or audible alarm activated by the alarm indications given in §§ 4.2.1 and 4.2.2 above, is left to the discretion of each Administration. + +4.2.3 Alarm indication to the remote end, transmitted by changing bit 3 of channel time-slot 0 from the state 0 to the state 1 in those frames not containing the frame alignment signal. This should be effected as soon as possible. + +4.2.4 Transmission suppressed at the analogue outputs. + +4.2.5 AIS applied to time-slot 16 64 kbit/s output (see General Notes below to § 4.2). This action should be taken as soon as possible and not later than 2 ms after the detection of the fault condition. + +4.2.6 AIS applied to time slot 16 of the output 2048 kbit/s composite signal (if supervision of the incoming 64 kbit/s signal is provided). + +### *General Notes to § 4.2* + +*Note 1 -* The equivalent binary content of the AIS is a continuous stream of binary 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 of $1 \cdot 10^{-3}$ . However, a signal with all bits except the frame alignment in the 1 state, should not be mistaken as an AIS. + +*Note 2 -* All timing requirements quoted apply equally to restoration, subsequent to the fault condition clearing. + +## **5 Signalling** + +### *5.1 Signalling arrangement* + +Refer to § 3.3.3 of Recommendation G.704. Channel time slot 16 may be used to provide an interface at 64 kbit/s which shall be suitable for use with either common channel or channel associated signalling. + +TABLE 1/G.732 + +### **Fault conditions and consequent actions for the PCM multiplex equipment** + +| Equipment part | Fault conditions (see § 4.1) | Consequent actions (see § 4.2) | | | | | | +|-------------------------------|-----------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------|------------------------------------------------|-------------------------------------------------|------------------------------------------------|-----------------------------------------------------------------| +| | | Service alarm indication generated | Prompt maintenance alarm indication generated | Alarm indication to the remote end transmitted | Transmission suppressed at the analogue outputs | AIS applied to 64 kbit/s output (time slot 16) | AIS applied to time slot 16 of the 2048 kbit/s composite signal | +| Multiplexer and demultiplexer | Failure of power supply | Yes | Yes | Yes (if practicable) | Yes (if practicable) | Yes (if practicable) | Yes (if practicable) | +| | Failure of codec | Yes | Yes | Yes | Yes | | | +| Multiplexer only | Loss of incoming signal at 64 kbit/s input time slot 16 (see Notes under § 4.1.3) | | Yes | | | | Yes | +| | Loss of incoming signal at 2048 kbit/s | Yes | Yes | Yes | Yes | Yes | | +| | Loss of frame alignment | Yes | Yes | Yes | Yes | Yes | | +| Demultiplexer only | Error ratio $10^{-3}$ on the frame alignment signal | Yes | Yes | Yes | Yes | Yes | | +| | Alarm indication received from the remote end (bit 3 of time slot 0) | Yes | | | | | | + +*Note - 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.* + +### 5.2 *Loss and recovery of multiframe alignment in case of channel associated signalling* + +Multiframe alignment should be assumed to have been lost when two consecutive multiframe alignment signals have been received with an error. + +Multiframe alignment should be assumed to have been recovered as soon as the first correct multiframe alignment signal is detected. + +*Note* - To avoid a condition of spurious multiframe alignment, the following procedure may be used in addition to the above: + +- Multiframe alignment should be assumed to have been lost when, for a period of one or two multiframes, all the bits in time slot 16 are in state 0. +- Multiframe alignment should be assumed to have been recovered only when at least one bit in state 1 is present in the time slot 16 preceding the multiframe alignment signal first detected. + +### 5.3 *Fault conditions and consequent actions in case of channel associated signalling* + +#### 5.3.1 *Fault conditions* + +The signalling multiplex equipment should detect the following fault conditions: + +##### 5.3.1.1 Failure of power supply. + +##### 5.3.1.2 Loss of 64 kbit/s incoming signal at the input of the signalling demultiplexer. + +*Note 1* - The detection of this fault condition is not mandatory when the signalling multiplex equipment is situated within a few metres of the PCM multiplex equipment or when this fault condition results in an indication of loss of multiframe 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. + +##### 5.3.1.3 Loss of multiframe alignment. + +##### 5.3.1.4 Alarm indication received from the remote signalling multiplex equipment (see § 5.3.2.3 below). + +##### 5.3.1.5 Receipt of the service alarm indication from the PCM multiplex equipment (see § 4.2.1 above). + +#### 5.3.2 *Consequent actions* + +Further to the detection of a fault condition appropriate actions should be taken as specified in Table 2/G.732. The consequent actions are as follows: + +##### 5.3.2.1 Service alarm indication to be forwarded to the switching equipment depending upon the switching and signalling arrangements provided. + +##### 5.3.2.2 Prompt maintenance alarm indication generated to signify that performance is below acceptable standards and maintenance attention is required locally. If provision is made for detecting the AIS, then on the reception of the AIS, the prompt maintenance alarm indication should be inhibited in the case of loss of multiframe (see § 5.3.1.3 above). + +*Note* - The location and provision of any visual and or audible alarms activated by the alarm indications given in §§ 5.3.2.1 and 5.3.2.2 above is left to the discretion of each Administration. + +##### 5.3.2.3 Alarm indication to the remote signalling multiplex equipment, generated by changing from the state 0 to the state 1 bit 6 of channel time slot 16 of frame 0 of the multiframe (see Table 7/G.704); this should be effected as soon as possible. + +##### 5.3.2.4 Application of the condition corresponding to state 1 on the line to all receive signalling channels. This condition should be forwarded as soon as possible and not later than 3 ms after the detection of the fault condition. + +*Note - All timing requirements quoted apply equally to restoration, subsequent to the fault condition clearing.* + +## 6 Interfaces + +The analogue interfaces should be in accordance with Recommendations G.712, G.713, G.714 and G.715. The digital interfaces at 2048 kbit/s should be in accordance with Recommendation G.703. The digital interfaces at 64 kbit/s should be of either the codirectional or the contradirectional type specified in Recommendation G.703. The specifications for 64 kbit/s interfaces are not mandatory for channel associated signalling. The interface for external synchronization of the transmitting timing signal should be in accordance with Recommendation G.703. + +TABLE 2/G.732 +**Fault conditions and consequent actions for channel-associated signalling multiplex equipment** + +| Equipment part | Fault conditions(see § 5.3.1) | Consequent actions (see § 5.3.2) | | | | +|-------------------------------|--------------------------------------------------------------------------|------------------------------------|-----------------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------| +| | | Service alarm indication generated | Prompt maintenance alarm indication generated | Alarm indication to the remote end transmitted | Application of state, equivalent to state 1, on line to all receive signalling channels | +| Multiplexer and demultiplexer | Failure of power supply | Yes | Yes | Yes
(if practicable) | Yes
(if practicable) | +| | Loss of incoming signal | Yes | Yes | Yes | Yes | +| | Loss of multiframe alignment | Yes | Yes | Yes | Yes | +| Demultiplexer only | Alarm indication received from the remote signalling multiplex equipment | Yes | | | Yes | +| | Receipt of the service alarm indication from PCM mux | Yes | | | Yes | + +*Note - 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.* + +## 7 Jitter + +### 7.1 Jitter at 2048 kbit/s output + +In the case where the transmitting timing signal is derived from an internal oscillator, the peak-to-peak jitter at the 2048 kbit/s output should not exceed 0.05 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 100$ kHz. + +### 7.2 *Jitter at 64 kbit/s output (for interfaces according to Rec. G.703)* + +7.2.1 In the case where the incoming 2048 kbit/s signal has no jitter, the peak-to-peak jitter at the 64 kbit/s output should not exceed 0.025 UI when it is measured within the frequency range from $f_1 = 20$ Hz to $f_4 = 10$ kHz. The equivalent binary content of the test signal applied to the 2048 kbit/s input shall be a pseudo-random bit sequence of length $2^{15} - 1$ as specified in Recommendation O.151. + +*Note* - In order to carry out this measurement without invoking AIS at the 64 kbit/s output, it will normally be necessary to include a frame alignment signal in the test signal. + +7.2.2 The jitter transfer function between the 2048 kbit/s input and the 64 kbit/s output should not exceed -29.6 dB when measured over the frequency range $f_0$ to 10 kHz. The frequency $f_0$ should be less than 20 Hz and as low as possible (e.g. 10 Hz), taking into account the limitations of measuring equipment. + +*Note 1* - The 2048 kbit/s test signal shall be modulated by sinusoidal jitter. The equivalent binary content of the test signal shall be 1000. + +*Note 2* - In order to carry out this measurement without invoking AIS at the 64 kbit/s output, it will normally be necessary to include a frame alignment signal in the test signal. + +*Note 3* - The jitter reduction of 1/32 due to demultiplexing is equivalent to -30.1 dB. \ No newline at end of file diff --git a/marked/G/T-REC-G.735-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.735-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.735-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.735-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg b/marked/G/T-REC-G.735-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a526cb924675b13518c3f0e0e84ccc15595ec770 --- /dev/null +++ b/marked/G/T-REC-G.735-198811-I_PDF-E/2fa4a1bf91d0f34e87c689fbc1211fe3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4d2920c89a0ba52a61b573d2fb7c9c2a5704e4ad303b003c8af23fd789d90c6 +size 114228 diff --git a/marked/G/T-REC-G.735-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg b/marked/G/T-REC-G.735-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc4104d10044802606a2c90c2c5316e625a64da0 --- /dev/null +++ b/marked/G/T-REC-G.735-198811-I_PDF-E/6b32b7b928d34eeccb15c29cdf9d2cb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeffe2df0b438600f9b5bbb2405e94911bde2d5c77a302e78a983c1469460a65 +size 43151 diff --git a/marked/G/T-REC-G.735-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg b/marked/G/T-REC-G.735-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3dd58790ad99f2c448cb300ed3f204a3f5856c3 --- /dev/null +++ b/marked/G/T-REC-G.735-198811-I_PDF-E/d48475a25698b1c0592e4cfe07138f2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca1976998d29672f99733449aea84b3fa86fe2c60a01d80c95303e669fefe583 +size 33979 diff --git a/marked/G/T-REC-G.743-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.743-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5870b7302684ef8cb4c5d6657eeac3dde7f57f4d --- /dev/null +++ b/marked/G/T-REC-G.743-198811-I_PDF-E/raw.md @@ -0,0 +1,212 @@ + + +![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.743** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**GENERAL ASPECTS OF DIGITAL TRANSMISSION +SYSTEMS** + +**TERMINAL EQUIPMENTS** + +--- + +**SECOND ORDER DIGITAL MULTIPLEX +EQUIPMENT OPERATING AT 6312 kbit/s AND +USING POSITIVE JUSTIFICATION** + +**ITU-T Recommendation G.743** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.743 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 6312 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 1544 kbit/s primary multiplex equipments. + +## **2 Bit rate** + +The nominal bit rate should be 6312 kbit/s. + +The tolerance on that rate should be $\pm 30$ parts per million (ppm). + +## **3 Frame structure** + +Table 1/G.743 gives: + +- the tributary bit rate and the number of tributaries; +- the number of bits per frame; +- the bit numbering scheme; +- the bit assignment; +- the distributed frame and multiframe alignment signals. + +## **4 Loss and recovery of frame and multiframe alignment and consequent action** + +The frame alignment recovery time should not exceed 16 ms. The signal to be applied to the tributaries during the out-of-frame-alignment time should be studied. + +Once frame alignment is established, multiframe alignment should be recovered in less than 420 microseconds. + +## **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.743). + +Positive justification should be indicated by the signal 111, no justification by the signal 000. Majority decision is recommended. + +Table 1/G.743 gives the maximum justification rate per tributary and the nominal justification ratio. + +## **6 Jitter** + +### **6.1 Specifications at the input ports** + +The digital signal presented at the input ports shall be as defined in Recommendation G.703 modified by the + +transmission characteristic of the interconnecting cable. The input ports shall be able to tolerate a digital signal with these electrical characteristics but modified by sinusoidal jitter up to the limits specified by the amplitude frequency relationship in Figure 1/G.743. The equivalent binary content of the signal, with jitter modulation, applied to the inputs shall be a pseudo-random bit sequence of length $2^{15} - 1$ . + +*Note* - The signal with jitter modulation applied to the demultiplexer input shall contain the bits necessary for framing and justification in addition to information bits. + +TABLE 1/G.743 +**6312-kbit/s multiplexing frame structure** + +| | | +|-------------------------------------------------------------|---------------------| +| Tributary bit rate (kbit/s) | 1544 | +| Number of tributaries | 4 | +| Frame structure (see Notes 1 and 2) | Bit number | +| Bit for multiframe alignment signal ( $M_j$ ) (see Note 1) | Set I
1 | +| Bits from tributaries | 2 to 49 | +| 1st bit for justification control signal ( $C_{j1}$ ) | Set II
1 | +| Bits from tributaries | 2 to 49 | +| 1st bit for frame alignment signal ( $F_0$ ) (see Note 3) | Set III
1 | +| Bits from tributaries | 2 to 49 | +| 2nd bit for justification control signal ( $C_{j2}$ ) | Set IV
1 | +| Bits from tributaries | 2 to 49 | +| 3rd bit for justification control signal ( $C_{j3}$ ) | Set V
1 | +| Bits from tributaries | 2 to 49 | +| 2nd bit for frame alignment signal ( $F_1$ ) (see Note 3) | Set VI
1 | +| Bits from tributaries (see Note 4) | 2 to 49 | +| Frame length | 294 bits | +| Multiframe length | 1176 bits | +| Bits per tributary per multiframe (including justification) | 288 bits | +| Maximum justification rate per tributary | 5367 bit/s | +| Nominal justification ratio | 0.334 | + +*Note 1* - This frame is repeated 4 times to form a multiframe with designated $j = 1, 2, 3, 4$ . The multiframe alignment signal is a 011x-pattern. x may be used as an alarm service digit. + +*Note 2* - The bits from the second and fourth tributaries are inverted logically before multiplexing with the bits from the first and third tributaries. + +*Note 3* - The frame alignment is $F_0 = 0$ and $F_1 = 1$ . + +*Note 4* - The bit available for the justification of tributary $j$ is the first time slot of tributary $j$ following $F_1$ in the $j$ th frame. + +![Graph of Peak-to-peak jitter amplitude (UI) vs Jitter frequency (f). The graph shows a piecewise linear characteristic with a flat top at A1 from f1 to f2, a downward slope of 20 dB/decade from f2 to f3 reaching A2, and a flat bottom at A2 from f3 to f4. CCITT - 31760](de6e8b740c69dac308cce9edfec3eff4_img.jpg) + +Graph of Peak-to-peak jitter amplitude (UI) vs Jitter frequency (f). The graph shows a piecewise linear characteristic with a flat top at A1 from f1 to f2, a downward slope of 20 dB/decade from f2 to f3 reaching A2, and a flat bottom at A2 from f3 to f4. CCITT - 31760 + +| Input | A 1 (UI) | A 2 (UI) | f 1 (Hz) | f 2 (Hz) | f 3 (kHz) | f 4 (kHz) | +|---------------------------|---------------------|---------------------|---------------------|---------------------|----------------------|----------------------| +| 1544 kbit/s | 2 | 0.05 | 10 | 200 | 8 | 40 | +| 6312 kbit/s (provisional) | 8 | 0.05 | 10 | 200 | 32 | 160 | + +UI Unit interval + +FIGURE 1/G.743 + +#### **Lower limit of maximum tolerable input jitter** + +### 6.2 *Multiplex signal output jitter* + +The jitter at the 6312 kbit/s output of the multiplexer should not exceed 0.01 UI rms. + +### 6.3 *Demultiplexer output jitter with no multiplexer or demultiplexer input jitter* + +With no jitter at the input to the multiplexer and demultiplexer, the jitter at the demultiplexer output should not exceed 1/3 unit intervals peak-to-peak. + +### 6.4 *Demultiplexer jitter transfer characteristic* + +The gain of the jitter transfer characteristic should not exceed the limits given in Figure 2/G.743. + +![Graph of Jitter gain (dB) vs Jitter frequency (f). The graph shows a piecewise linear characteristic with a flat top at 0.5 dB from f0 to 0.35 kHz, a downward slope of 40 dB/decade from 0.35 kHz to 2.5 kHz, and a downward slope of 20 dB/decade from 2.5 kHz to 15 kHz. The area above the curve is shaded. CCITT - 31770](c82c7d8107cba121734a9cfba891216d_img.jpg) + +Graph of Jitter gain (dB) vs Jitter frequency (f). The graph shows a piecewise linear characteristic with a flat top at 0.5 dB from f0 to 0.35 kHz, a downward slope of 40 dB/decade from 0.35 kHz to 2.5 kHz, and a downward slope of 20 dB/decade from 2.5 kHz to 15 kHz. The area above the curve is shaded. CCITT - 31770 + +Note - The frequency f0 should be as low as possible taking into account the limitations of measuring equipment. + +FIGURE 2/G.743 + +#### **Demultiplexer transfer characteristic** + +## 7 Digital interfaces + +The digital interfaces at 1544 kbit/s and 6312 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 + +The service digits are reserved for national use. + +## 10 Fault conditions and consequent actions + +### 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 frame alignment at the demultiplexer. + +It may also be equipped to detect the following fault conditions. + +- 10.1.3 Loss or degradation of incoming 1544 kbit/s signal. +- 10.1.4 Loss or degradation of incoming 6312 kbit/s signal. +- 10.1.5 Failure of the multiplex or demultiplex as evidenced by incorrect multiplexing or demultiplexing action. +- 10.1.6 Failure of standby (if the multiplex is so equipped). + +### 10.2 *Consequent actions* + +On the detection of a fault condition, the following appropriate actions should be taken: + +10.2.1 For a multiplex equipped with automatic changeover, the consequent actions are specified in Table 2/G.743. For a multiplex so equipped, a switch to a standby is performed in the event of a failure of the multiplex equipment in service. A maintenance alarm is generated if a switch takes place, or if the standby fails. A prompt maintenance alarm is generated if an incoming signal fails, or if service is lost due to inability to complete automatic changeover to the standby. + +10.2.2 For a multiplex not equipped with automatic changeover, a prompt maintenance alarm is generated in response to any fault condition detected. Such multiplexers will normally be equipped to detect power failure and loss or degradation of incoming signal at the demultiplexer. + +10.2.3 The provision of an Alarm Indication Signal (AIS) to the 1544 kbit/s tributary outputs from the demultiplexer is under study. An AIS, suitable for use without special detectors at the primary PCM multiplex might be provided on an optional basis. + +TABLE 2/G.743 +**Fault conditions and consequent actions for a multiplex equipped with automatic changeover** + +| Equipment part | Fault condition
(see § 10.1) | Consequent actions (see § 10.2.1) | | | | +|------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------| +| | | Prompt
maintenance
alarm indication
generated | Deferred
maintenance
alarm indication
generated | Alarm indication
to the remote
multiplex
equipment
generated
(if so equipped) | Automatic
changeover
actuated | +| Multiplexer
demultiplexer | Failure
of power supply | No | Yes | | Yes | +| Multiplexer only | Loss or degradation
of incoming signal
on a tributary | Yes | | | No | +| Demultiplexer
only | Loss or degradation
of incoming signal
at 6312 kbit/s | | Yes | Yes | No | +| | Alarm indication
received from the
remote multiplex
equipment
(if so equipped) | | Yes | | | + +*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. \ No newline at end of file diff --git a/marked/G/T-REC-G.744-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.744-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.744-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.751-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.751-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64672153e39c851d9e16fdbc702e526c7ba7e8a7 --- /dev/null +++ b/marked/G/T-REC-G.751-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.751-198811-I_PDF-E/79d61011f426d34fb542d86176482d2c_img.jpg b/marked/G/T-REC-G.751-198811-I_PDF-E/79d61011f426d34fb542d86176482d2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38b15a088fff7b17ae3a6c375f50a611835eb49a --- /dev/null +++ b/marked/G/T-REC-G.751-198811-I_PDF-E/79d61011f426d34fb542d86176482d2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71e4da40aa2fb61484745e1ef803244c508959a6400bbf9714499c3dd68b9eaa +size 33804 diff --git a/marked/G/T-REC-G.751-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg b/marked/G/T-REC-G.751-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fa1bb96fb0f2cb47eb5faa4fab02d8338fade8d --- /dev/null +++ b/marked/G/T-REC-G.751-198811-I_PDF-E/84e2ac543ffc4145dc85b05a48ec62e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e64642573f6f3f6d4dc52d04a8570c496313eb9cbe61acd4ec17c844240987 +size 33667 diff --git a/marked/G/T-REC-G.751-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg b/marked/G/T-REC-G.751-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6531fa6533362af5ca6a343442cb39b7abc5251a --- /dev/null +++ b/marked/G/T-REC-G.751-198811-I_PDF-E/8ee3b76dd49f31624d287885bc2c81ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62a57cb22167c9558ae1f5f209f1004345601f64ede6fb63b3beef393309de0d +size 34891 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ae6afed88d3e5834d7166631c32536170303ea1 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/0a42e05c07941450f34e4f7117725834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25cab9598116862c560b94aab78d5fd0100e5b72f6966d33b01d395992c73cb5 +size 103547 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c52fe84070814f426979b8ab1ff25f02b9a000e --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/255efa1d461fc79b4ed367aaec11637f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c72fb5990bc2cc4a4344200eea6335fc84b2b9dbb733b76f81ed67fd8c0ac6 +size 50634 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..241913df8e37fdba0875a4cd7d3094177d4668bc --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/2df09d249c38abee55dbf0526dd6da0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79261928c086a1971e5720822a5af487ca28c69b619d7d6a8c2d0234c43c8281 +size 31366 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6abdfdcec18c76cf7e57d2f0fe0d12e0e09ce1 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69d45a49fda7eb0a23007d0165e41182bf483b52cd7d90e95401dd080fe80eaf +size 8286 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcfb80fabed85b4d2eeb6dde473707ca2ef4ca53 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a88597d57b48c4367968a0d1dac1d6791d594f9b668df06d3e77351838dce0f5 +size 87773 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7a21801118a04051fbee96228d8b987bf2d330c --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/3c6151f296d5800335472b7dc00ce423_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:413cd92f9761c2bfe93f2b671a59f36e2b3034cd258f561a5b37adcea0ca6074 +size 54073 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..831d344e8a78132c34e84c49253110cc788811c2 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48641ebc3ad37385e5a5c3cc9e576bc001173ac73e71a9cd92665d957125832d +size 58846 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35ae558603f8ea192b6635e66534d518ffad747c --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/5a9cdc1fed33ae8fb871a8cd4d591729_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9003be922975ee224f476c1903d15fd92ac783621b186daae6f13fbc227dab3c +size 58304 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b44ad6d031f3089649f6a4977ba900c75eb85ff8 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4194287fbe2056b47ea0cf81d8c282404ae6cebcd92826dca0a8e9a1defacaf +size 56607 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b107fb47edafb1197e06620352cedb907ac7c1d --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/701bc79e78b382bcfd3ba85597dbb9c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7034a90743fd4d3b52fa1fd51b4e7cca22f97fc50645246bcabaeb3adb53c23 +size 93749 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5658c0a156bdaf7a1fab9d080984307646f0b2ad --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:013f9f80f1e84ac81895c02431e770b81e8df8e96f9d22df1d42169feb7be9d6 +size 50257 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d84b4da20873d2e48394f6a8dc7b9f1d6c8121bd --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a332feef3902a548c51c3b353f50e5fd1173e6041d8553cf3446fc0dae26d582 +size 81161 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94c12f85b99203ea602aabacbc2d75b23aed38a2 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55c4298a69bee32ca2699c12b9d667c727f06d7bc8897c153cae95270272946d +size 96720 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f014c20e3f2cd6c9faf9f7bd79341856dbf767ad --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67c8845cd2167dd540546a1a237de081dc0ffc49850b3ffcfb3c918eb800b979 +size 34006 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03d52c2060008f744de06a73dbda2196a486b27e --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/9e6062272bbe3ddbb7c0606721d64cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6b30239b3504cf62c5743449fe6ba97aa118e1f111daa40cfd54e8c029eb4bb +size 44180 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d135b360e6f890bf45b20053fac76f173cf7729 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1271ee403be5d08a9d4bc4ac40bc8f2de8c1828d65fed213755a5bb05a7224 +size 53162 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6da29131a1f4d8e35f0f31eb405e100609b532e --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc971e8aaf00c3ddfb55d7a5054317889ff52809ea2183b79bf2eb775d324b11 +size 121661 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf3626500f9b6fd8b45713ea3ff28de2d099e71e --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/a37adbbe12ec735a20ead2466363d07a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f8f1bd7007e6279bb6b9c6316cd046eea1d2c87d1dd46bdd12610f5035ad037 +size 62037 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8476b8b1269ef58edf2f09ebe2169c3c51edb2b0 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de35a487d124694aecb7523b042e89e3fa54847357b6fe83c6aa0f3d5aa08985 +size 46799 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4482a67299634451b573ab1d138f0e86ff4f63ab --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9955140d74c7f222061c2ca67995f37969c7c164f31752fc263e85dd630f8b9a +size 68004 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10ec0b884cf64e73e4a1f596228042aeaecc858a --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9610a6e94878cfc46b7bf093a335d183317b1d140e87a0d7b34ffd02df54df62 +size 90068 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..962abdb75736381ba5664c6ea9c409f8d5f2d544 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/c1df61cc3717e878a48e530218403403_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a328541dbd0df8b2dda821b8d39c7a1c80264bac2f57a4258669fc04d351cd7 +size 93892 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fcb0ce60fbb17c7c790759a7806346a532d6c75 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e90a91a911a597ebf4b1d6b8209f2dec2be32a915a6a84a3a3afb74d7958486 +size 80000 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..114c06384a2a2f86d5b7c772d122760330b04ec9 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67d88d50be25afe6a3918cb78ed9a0f91c9082cc10b0be0d5102386508016e41 +size 64516 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c661bd93013a62755c4bf05a91ecad894c9a3fba --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc43343728976c0377ef9a82b6c6d274f31d7d40248399c6dae37e415e05ad80 +size 56305 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..136baad195ee468c6f3a56d79ab766e629a6cfb0 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e35c2236edae021b5384f83a6acee29f7bfb76c14281eeed141d07aea1d60c72 +size 65482 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb18afb6dfd581da1ae71ea2a5791445a7e8b82e --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e83e9a3d0b6f6aba76480ad30961c18223649b12bd817da4dcbe99cbb7167a3b +size 112318 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dade36fa158edd05d1c2d7eeae85a6b938678a2 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/e8f5117fb031f413a836525061addd61_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76dcc0fc8f0439f6f3923cdf0b83ab9aba7acfce9561a00ad653de3a4eda08d5 +size 25904 diff --git a/marked/G/T-REC-G.765-199209-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/marked/G/T-REC-G.765-199209-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84fa06b6c957ba86e5c2d70119930a28d8c04d90 --- /dev/null +++ b/marked/G/T-REC-G.765-199209-I_PDF-E/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1ee7ec9511daea5e8365ed3e57a378076d6bf6714575b7b286592117b2ec9fe +size 92068 diff --git a/marked/G/T-REC-G.767-199810-I_PDF-E/raw.md b/marked/G/T-REC-G.767-199810-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b182e8e470d11469c7ee69bed55bb89f73d4a3e1 --- /dev/null +++ b/marked/G/T-REC-G.767-199810-I_PDF-E/raw.md @@ -0,0 +1,1009 @@ + + +![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.767** + +(10/98) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Terminal equipments – +Principal characteristics of transcoder and digital +multiplication equipment + +--- + +**Digital circuit multiplication equipment using +16 kbit/s LD-CELP, digital speech interpolation +and facsimile demodulation/remodulation** + +ITU-T Recommendation G.767 + +(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 | +| General | G.700–G.709 | +| Coding of analogue signals by pulse code modulation | G.710–G.719 | +| Coding of analogue signals by methods other than PCM | G.720–G.729 | +| Principal characteristics of primary multiplex equipment | G.730–G.739 | +| Principal characteristics of second order multiplex equipment | G.740–G.749 | +| Principal characteristics of higher order multiplex equipment | G.750–G.759 | +| Principal characteristics of transcoder and digital multiplication equipment | G.760–G.769 | +| Operations, administration and maintenance features of transmission equipment | G.770–G.779 | +| Principal characteristics of multiplexing equipment for the synchronous digital hierarchy | G.780–G.789 | +| Other terminal equipment | G.790–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **ITU-T RECOMMENDATION G.767** + +# **DIGITAL CIRCUIT MULTIPLICATION EQUIPMENT USING 16 kbit/s LD-CELP, DIGITAL SPEECH INTERPOLATION AND FACSIMILE DEMODULATION/REMODULATION** + +# **Summary** + +This Recommendation specifies the elements of DCME using 16 kbit/s LD-CELP, Digital Speech Interpolation (DSI) and Facsimile Demodulation/Remodulation in order to achieve interworking of such equipment. It specifies extensions and deviations for Recommendations G.763 and G.766 which specify a 32 kbit/s ADPCM DCME, and Facsimile Demodulation/Remodulation. + +###### **Source** + +ITU-T Recommendation G.767 was prepared by ITU-T Study Group 15 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 13th 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 ..... | 1 | +| 3 | Definitions ..... | 1 | +| 4 | Abbreviations ..... | 1 | +| 5 | DCME frame structure ..... | 2 | +| 5.1 | General ..... | 2 | +| 5.1.1 | Supported services ..... | 2 | +| 5.1.2 | PCM frame ..... | 2 | +| 5.1.3 | DCME frame ..... | 2 | +| 5.1.4 | DCME multiframe ..... | 2 | +| 5.1.5 | 16 kbit/s DCME frames ..... | 3 | +| 6 | Bearer frame structure ..... | 3 | +| 6.1 | Cliques, destinations and bearers ..... | 3 | +| 6.1.1 | Number of cliques ..... | 3 | +| 6.1.2 | Number of destinations ..... | 3 | +| 6.1.3 | Multiple outgoing bearers ..... | 3 | +| 6.2 | Assignment Messages (AM) ..... | 3 | +| 6.3 | Bearer Channels (BC) ..... | 4 | +| 6.4 | Control Channel (CC) ..... | 4 | +| 6.5 | BC numbering and the use of the bearer frame ..... | 4 | +| 6.5.1 | 8-bit (64 kbit/s transparent calls) BCs ..... | 4 | +| 6.5.2 | 5-bit (VBD optimized 40 kbit/s LD-CELP) BCs ..... | 5 | +| 6.5.3 | 4-bit BCs (BB, FB) ..... | 5 | +| 6.5.4 | Normal range 2-bit BCs (LD-CELP voice) ..... | 5 | +| 6.5.5 | Overload BCs ..... | 5 | +| 6.5.6 | Pre-assigned BCs ..... | 5 | +| 7 | Control channel ..... | 5 | +| 7.1 | General ..... | 5 | +| 7.2 | Number of assignment messages ..... | 5 | +| 7.2.1 | Single/double AM mode criterion ..... | 5 | +| 7.2.2 | Total number of assignment messages ..... | 5 | +| 7.3 | Control channel content ..... | 6 | +| 7.3.1 | CC synchronization ..... | 6 | +| 7.3.2 | Assignment messages ..... | 6 | + +| | Page | +|------------------------------------------------------------------------|-------------| +| 7.3.3 Asynchronous data word..... | 8 | +| 7.3.4 Error correction ..... | 10 | +| 7.4 CC message transmission scheme..... | 11 | +| 7.4.1 Control channel structure ..... | 11 | +| 7.4.2 CC bit mapping ..... | 11 | +| 8 Variable bit rate and overload channel creation..... | 16 | +| 8.1 Principles..... | 16 | +| 8.1.1 Creation of 16 kbit/s channels..... | 16 | +| 8.1.2 Creation of 12.8 kbit/s channels..... | 16 | +| 8.1.3 Creation of 9.6 kbit/s channels..... | 16 | +| 8.2 Overload channel creation..... | 16 | +| 8.2.1 Notations ..... | 16 | +| 8.2.2 Packaging schemes..... | 16 | +| 8.3 Overload channel creation process – The VBR scheme..... | 17 | +| 8.3.1 VBR lists ..... | 17 | +| 8.3.2 Notations ..... | 18 | +| 8.3.3 VBR not required ..... | 18 | +| 8.3.4 VBR required ..... | 18 | +| 9 ABPS calculations ..... | 20 | +| 10 Channel check procedure ..... | 20 | +| 11 Facsimile demodulation/remodulation ..... | 20 | +| 11.1 General ..... | 20 | +| 11.2 Facsimile blocks, facsimile transport channels and fax banks..... | 20 | +| 11.3 Facsimile data channel ..... | 21 | +| 11.4 Facsimile control channel and forward error correction ..... | 22 | +| 11.5 FCC location on the bearer..... | 23 | +| 12 System statistics measurement ..... | 23 | + +# Introduction + +The introduction of the 16 kbit/s LD-CELP speech compression algorithm by ITU-T (Recommendation G.728), with its expansions to variable bit rates below and above 16 kbit/s, has enabled the enhancement of circuit multiplication equipment performance in both speech quality and multiplication gain. Third generation DCME follows the operation principles of the second generation DCME (DCME in accordance with Recommendations G.763 and G.766), with modifications dictated by the transition from ADPCM, which is a single sample based speech compression algorithm, to LD-CELP, which operates on a 5-sample vector. This Recommendation is, therefore, an extension to Recommendations G.763 (Digital Circuit Multiplication Equipment Using 32 kbit/s ADPCM and Digital Speech Interpolation) and G.766 (Facsimile Demodulation/Remodulation for DCME), as it specifies only the deviations of the third generation DCME from its predecessor. + + + +## Recommendation G.767 + +# DIGITAL CIRCUIT MULTIPLICATION EQUIPMENT USING 16 kbit/s LD-CELP, DIGITAL SPEECH INTERPOLATION AND FACSIMILE DEMODULATION/REMODULATION + +(Geneva, 1998) + +# 1 Scope + +This Recommendation specifies the elements of DCME using 16 kbit/s LD-CELP, Digital Speech Interpolation (DSI) and facsimile demodulation/remodulation (namely a 16 kbit/s DCME) in order to achieve interworking of such equipment. It is an extension to Recommendations G.763 (Digital Circuit Multiplication Equipment Using 32 kbit/s ADPCM and Digital Speech Interpolation) and G.766 (Facsimile Demodulation/Remodulation for DCME), as it specifies only the deviations of the 16 kbit/s DCME from the G.763 32 kbit/s DCME. + +# 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.763 (1998), *Digital circuit multiplication equipment using ADPCM (Recommendation G.726) and digital speech interpolation.* +- ITU-T Recommendation G.766 (1996), *Facsimile demodulation/remodulation for digital circuit multiplication equipment.* + +# 3 Definitions + +The same definitions of Recommendations G.763 and G.766 are used in this Recommendation. + +# 4 Abbreviations + +The abbreviations used in the above-referenced Recommendations are also used in this Recommendation as well. This Recommendation uses also the following abbreviations. + +| | | +|------|----------------------------| +| ABPS | Averaged Bit Per Sample | +| AM | Assignment Message | +| BB | Bit Bank | +| BCH | Bose-Chaudhuri-Hocquenghem | +| FB | Fax Bank | +| FCC | Facsimile Control Channel | +| FDC | Facsimile Data Channel | + +| | | +|---------|------------------------------------------| +| FTC | Facsimile Transport Channel | +| Info | Information | +| LD-CELP | Low-Delay Code Excited Linear Prediction | +| PCM | Pulse Code Modulation | +| QB | Quarter Byte | +| Rx | Receive | +| Tx | Transmit | +| VBD | Voice-Band Data | + +# 5 DCME frame structure + +## 5.1 General + +### 5.1.1 Supported services + +The 16 kbit/s DCME frame structure accommodates the following services: + +- 8-bit channels to support 64 kbit/s transparent calls. +- 2-bit channels to support voice calls at LD-CELP 16 kbit/s, 12.8 kbit/s, 9.6 kbit/s according to Recommendation G.728 and its Annex H. +- 5-bit channels to support VBD calls at 40 kbit/s according to Recommendation G.728 and its draft Annex J. +- 4-bit channels to support fax banks carrying demodulated fax calls similar to Recommendations G.763 and G.766. +- 8-, 5-, 2-bit channels to support 64 kbit/s, 40 kbit/s, 16 kbit/s, 12.8 kbit/s and 9.6 kbit/s pre-assigned channels. + +### 5.1.2 PCM frame + +As in Recommendation G.763, the bearer structure of the 16 kbit/s DCME retains compatibility with Recommendation G.704, so it contains 32 consecutively numbered 8-bit time slots, from 0 to 311. + +### 5.1.3 DCME frame + +The low rate encoding algorithm used in the 16 kbit/s DCME is LD-CELP according to Recommendation G.728. The LD-CELP algorithm handles a speech vector of 5 consecutive PCM samples (at 64 kbit/s) and results in a vector of 10, 8 or 6 bits (at 16, 12.8 or 9.6 kbit/s respectively). The encoding rate can be altered once every 4 speech vectors, i.e. every 2.5 ms. A DCME frame of 2.5 ms, which contains 20 G.704 PCM frames, is used in the 16 kbit/s DCME. + +### 5.1.4 DCME multiframe + +The IT related circuit supervision/alarm condition field of the asynchronous word supports up to 360 ITs, carried over up to 12 primary rate interfaces. The G.767 DCME multiframe of 72 DCME frames is used to accommodate that. + +--- + +1 The case of T1 bearer interface is similar to E1 and handled as in Recommendation G.763. + +### 5.1.5 16 kbit/s DCME frames + +The 16 kbit/s DCME frame and multiframe structures are depicted in Figure 1. + +![Diagram showing the hierarchy of DCME frames, PCM frames, and Time Slots (TS) for a 16 kbit/s bearer.](e9314c83043183351ed74908e9bf2f90_img.jpg) + +The diagram illustrates the relationship between DCME multiframe, DCME frame, and PCM frame structures. It consists of three horizontal rows of boxes, with dashed lines indicating the nesting of frames. + +- DCME multiframe: 180 ms**: The top row shows a sequence of DCME frames. The first two are labeled "DCME frame #0" and "DCME frame #1". A dashed line connects the end of "DCME frame #1" to the start of "DCME frame #71", indicating a gap in the sequence. +- DCME frame: 2.5 ms**: The middle row shows a sequence of PCM frames. The first two are labeled "PCM frame #0" and "PCM frame #1". A dashed line connects the end of "PCM frame #1" to the start of "PCM frame #19", indicating a gap in the sequence. Dashed lines also connect the boundaries of the DCME multiframe to the boundaries of the DCME frame, showing that one DCME multiframe contains 72 DCME frames. +- PCM frame: 125 ms**: The bottom row shows a sequence of Time Slots (TS). The first two are labeled "TS0" and "TS1". A dashed line connects the end of "TS1" to the start of "TS31", indicating a gap in the sequence. Dashed lines also connect the boundaries of the DCME frame to the boundaries of the PCM frame, showing that one DCME frame contains 20 PCM frames. + +T1528700-98 + +Diagram showing the hierarchy of DCME frames, PCM frames, and Time Slots (TS) for a 16 kbit/s bearer. + +Figure 1/G.767 – 16 kbit/s frame and multiframe structures + +# 6 Bearer frame structure + +## 6.1 Cliques, destinations and bearers + +### 6.1.1 Number of cliques + +With LD-CELP, small cliques (compared to G.763 DCME) can support a fairly large amount of traffic. Therefore the maximum number of cliques (pools) carried on a single bearer in 16 kbit/s DCME is increased to 4. Each pool starts and ends on TS boundaries (and therefore occupies an integral number of time slots). + +### 6.1.2 Number of destinations + +The maximum number of destinations is 4 including the cases of mixed operation between multi-clique and multi-destination modes. + +### 6.1.3 Multiple outgoing bearers + +Optionally, a 16 kbit/s DCME will support up to 4 outgoing bearers. A single bearer will be able to carry up to 4 cliques. A clique shall not be split across bearers. + +## 6.2 Assignment Messages (AM) + +When using LD-CELP, the DCME gain increases significantly and the number of supported ITs is increased accordingly (compared to ADPCM). As a result, the number of activity events (and assignment messages) increases. Taking into account the fact that the DCME frame is extended (from 2 ms to 2.5 ms), the control channel can support up to two assignment messages (namely double AM) every DCME frame, so as to avoid long queues and freeze-out due to limited control channel capacity. The option of operating with a single Assignment Message (single AM), when smaller configurations are applied, is maintained. + +## 6.3 Bearer Channels (BC) + +16 kbit/s LD-CELP encoded voice calls use 2 bits every PCM frame. Therefore the 16 kbit/s DCME bearer channels occupy 2 bits each. These basic Bearer Channels (BCs) shall be referred to as Quarter Bytes (QB) in this Recommendation. Each QB occupies 40 bits every DCME frame2. + +## 6.4 Control Channel (CC) + +A single AM control channel of the 16 kbit/s DCME occupies 4 bits every PCM frame, i.e. 2 QBs. The single AM control channel holds the synchronization word, an assignment message (IT and BC numbers and synchronous data word), the asynchronous data word and some error correction bits. When an additional assignment message in the same DCME frame is required (double AM), one additional QB supports it. + +## 6.5 BC numbering and the use of the bearer frame + +Each time slot is subdivided into 4 QBs. The leftmost two or three QBs of each pool carries the control channel (single or double AM, respectively). The remaining QBs of the pool are the Bearer Channels (BCs) and are used to carry traffic. + +The normal range BCs are consecutively numbered. When a single AM control channel is used, the BC that follows the control channel is BC number one. In the case of double AM the numbering starts with 2, i.e. BC number 1 is skipped. In the case of a single pool, the maximum number of normal BCs is 122 for single AM and 121 for double AM. The numbering scheme is shown in Figure 2. + +![Figure 2/G.767 – 16 kbit/s DCME frame structure and BC numbering scheme for 2 pools. The diagram shows a frame divided into two pools: Pool 1 (Double AM) and Pool 2 (Single AM). Pool 1 starts with TS0, followed by a Control Channel (CC) of 3 QBs, then Bearer Channels (BC) numbered 2, 3, 4, 5, ..., n-1, n. Pool 2 starts with an 'Unused' section, followed by a Control Channel (CC) of 2 QBs, then Bearer Channels (BC) numbered 1, 2, ..., m-4, m-3, m-2, m-1, m. The frame ends with TS31. The diagram is labeled T1528710-98.](853f59c89931a666c07903b31d098277_img.jpg) + +Figure 2/G.767 – 16 kbit/s DCME frame structure and BC numbering scheme for 2 pools. The diagram shows a frame divided into two pools: Pool 1 (Double AM) and Pool 2 (Single AM). Pool 1 starts with TS0, followed by a Control Channel (CC) of 3 QBs, then Bearer Channels (BC) numbered 2, 3, 4, 5, ..., n-1, n. Pool 2 starts with an 'Unused' section, followed by a Control Channel (CC) of 2 QBs, then Bearer Channels (BC) numbered 1, 2, ..., m-4, m-3, m-2, m-1, m. The frame ends with TS31. The diagram is labeled T1528710-98. + +**Figure 2/G.767 – 16 kbit/s DCME frame structure and BC numbering scheme for 2 pools** + +The BC numbers contained in the assignment messages can be either in the range 1 through 122 (normal range) or in the range 128 through 207 (overload range). The total number of normal bearer channels shall also not exceed 122 even in the case of multiple outgoing bearer usage. The criteria for associating the BCs contained in the assignment message to bits within the bearer structure are as follows: + +### 6.5.1 8-bit (64 kbit/s transparent calls) BCs + +The BC number in the assignment message indicates the BC which carries the first 2 bits of the 8-bit sample. The rest of the bits are carried by the next three higher BCs. The same restrictions of G.763 are maintained, so unrestricted 64 kbit/s ITs will occupy one G.704 time slot. This implies that the 4-modulus of the BC number in the assignment message is 3. 16 kbit/s DCME will maintain frame integrity of consecutive trunk time slots which are allocated for $N \times 64$ kbit/s calls. + +2 The term "QB" replaces the term "nibble" of Recommendation G.763. + +### **6.5.2 5-bit (VBD optimized 40 kbit/s LD-CELP) BCs** + +The BC number in the assignment message indicates the BC which carries the first 2 bits (MSB, MSB – 1) of the 5-bit sample. The next higher BC carries the next 2 bits ((MSB – 2, MSB – 3) $\equiv$ (LSB + 2, LSB + 1)). The 5th bit (LSB) is obtained from a different 4-bit bearer channel which is independently assigned as a bit bank. Similarly to Recommendation G.763, all 4-bit BCs (Data, FB or BB) occupy either the four MSBs or the four LSBs of a G.704 time slot. This implies that the BC number in the assignment message, for such BCs, is an odd number. + +### **6.5.3 4-bit BCs (BB, FB)** + +16 kbit/s DCME fax banks and bit banks are used in the same manner as they are used in Recommendation G.763/G.766. The BC number in the assignment message indicates the BC which carries the first 2 bits of the 4-bit sample. The next higher BC carries 2 more bits. + +### **6.5.4 Normal range 2-bit BCs (LD-CELP voice)** + +The BC number in the assignment message indicates the BC which carries the LD-CELP encoded IT bits. If high load conditions exist, overload channels will be created. The BC number of a 4-bit channel is an odd number. + +### **6.5.5 Overload BCs** + +The BC number in the assignment message indicates an overload bearer channel which carries the IT bits. + +### **6.5.6 Pre-assigned BCs** + +16 kbit/s DCME pre-assigned ITs are assigned in the same manner as they are in G.763 DCME. 64, 40, 16, 12.8 and 9.6 kbit/s ITs can be pre-assigned. + +# **7 Control channel** + +## **7.1 General** + +The 16 kbit/s DCME control channel operates with two assignment messages (one assignment message for small cliques) in the 2.5 ms time-frame. The control channel contains a total of 80 or 120 bits of data in each 2.5 ms DCME frame, depending on whether one or two assignment messages (AMs) are used. These bits are transmitted at a rate of 4 or 6 bits every 125 $\mu$ s PCM frame. The control channel, thus, occupies 2 Quarter Bytes (QB) in the case of single AM mode and 3 QBs in the case of double AM mode. + +Apart from assignment messages, the control channel also conveys the asynchronous data word. + +## **7.2 Number of assignment messages** + +The single or double AM mode is determined for each clique, according to the following rules: + +### **7.2.1 Single/double AM mode criterion** + +When the clique size is 11 time slots or lower, that clique's control channel operates in the single AM mode. When the clique size is 12 time slots or higher, that clique's control channel operates in the double AM mode. + +### **7.2.2 Total number of assignment messages** + +The total number of assignment messages per Tx unit is 5. + +## **7.3 Control channel content** + +The contents of the control channel are a synchronization pattern, one or two assignment messages, an asynchronous data word and error correction code. + +### **7.3.1 CC synchronization** + +The frame synchronization pattern is a unique word of 20 bits, one bit every PCM frame of the DCME frame. The 20-bit unique word also provides a means of identifying the beginning of a 180 ms DCME multiframe (72 DCME frames) for use by the asynchronous data word. + +#### **7.3.1.1 Unique word pattern** + +The unique word transmitted with DCME frame #0 is: + +00010001111100101101 + +The unique word transmitted with DCME frames #1 through #71 is: + +11101110000011010010 + +#### **7.3.1.2 Unique word detection** + +The unique word detection is based on the detection of a correlation match between the accumulated contents of the first bit of the CC and a locally stored unique word pattern. The resulting correlation matches is used to attain, maintain and regain the synchronization of the CC message. + +In the steady state, a detection threshold of three is used to maintain synchronization, and a 3-bit window centred 20 bits after the previous detection of the correlation match is used to locate the start of the DCME frame for the proper decoding of the CC message. If the correlation match is not achieved, the CC message bits are discarded and a search procedure is initiated over a 20-bit window. + +### **7.3.2 Assignment messages** + +Each assignment message consists of 23 bits that include: + +- 9 bits IT identification word; +- 9 bits BC identification word (1 bit BC type + 8 bits BC number); +- 5 bits synchronous data word. + +#### **7.3.2.1 IT Identification word** + +The 9 bits of the IT identification word is used to identify the ITs. IT numbering is given in Table 1. + +**Table 1/G.767 – Numbers of ITs used in assignment messages** + +| IT number | IT identification | +|-----------------|---------------------------------------------------------------------------------------| +| 0 | Explicit disconnection of BC or during system start-up and map change. | +| 1 through 360 | IT used for traffic. | +| 461 through 464 | Voice order wire to destination number 1 to 4 respectively. | +| 490 | BC used as a bit bank. | +| 491 | BC used as a fax bank. | +| 471 through 474 | Channel check to clique number 1 to 4 respectively. | +| 475 through 478 | Local IT number to receive channel check from destination number 1 to 4 respectively. | +| 511 | Ineffective CC message when all traffic is pre-assigned. | + +#### 7.3.2.2 BC identification word + +The first (MSB) bit of the 9-bit BC identification word is used to indicate the BC type. For data, this bit will be 1 and for all other BC types it will be 0. + +The 8 LSBs in binary code identify the BC number in accordance with the agreed numbering scheme. The normal BC numbering range is 1 through 122. The overload BC numbering range is 128 through 207. + +For 4-bit services, the BC number identifies the first 2-bit BC of a pair adjacent 2-bit BCs, used to create a 4-bit BC and is an odd number. + +For a 64 kbit/s transparent channel, the BC number identifies the first 2-bit BC of a group of 4 adjacent BCs that occupy exactly one G.704 time slot of the bearer and its 4-modulus is 3. + +BC number 0 in binary code is used for CC messages transmitted during system start-up or during a DCME transmit unit map change. + +BC number 511 in binary code is used to indicate an ineffective CC message if all traffic is pre-assigned. + +#### 7.3.2.3 Synchronous data word + +The 5 bits synchronous data word supports the following messages: + +- Background noise level (16 levels). +- Channel check procedure. +- Transparent request. +- Signalling information when optional USM is used. +- The ineffective code (transmitted when the IT number indicates a fax bank or a bit bank and when a disconnect message or an ineffective message is sent). + +Table 2 shows the encoded messages to be transported by the synchronous data word. + +**Table 2/G.767 – Synchronous data word encoding** + +| Code | Transmit side action:
measure noise level | Receive side action:
store noise level | Code | Transmit side action:
measure noise level | Receive side action:
store noise level | +|-------|----------------------------------------------------------|-------------------------------------------|-------|----------------------------------------------|-------------------------------------------| +| 00000 | Ineffective | | 10000 | n/u | | +| 00001 | $\mu$ -law: $n < -72.0$
A-law: not applicable | $\mu$ -law: no noise | 10001 | $-54.0 \leq n < -51.0$ | -52 | +| 00010 | $\mu$ -law: $-72.0 \leq n < -67.0$
A-law: $n < -67.0$ | $\mu$ -law: -68
A-law: no noise | 10010 | $-51.0 \leq n < -49.0$ | -50 | +| 00011 | $-67.0 \leq n < -65.5$ | -66.5 | 10011 | $-49.0 \leq n < -47.0$ | -48 | +| 00100 | $-65.5 \leq n < -64.0$ | -65 | 10100 | $-47.0 \leq n < -45.0$ | -46 | +| 00101 | $-64.0 \leq n < -61.0$ | -62.5 | 10101 | $-45.0 \leq n < -44.0$ | -44.5 | +| 00110 | $-61.0 \leq n < -59.0$ | -60 | 10110 | $-44.0 \leq n < -42.8$ | -43 | +| 00111 | $-59.0 \leq n < -56.0$ | -57.5 | 10111 | $-42.8 \leq n < -42.0$ | -42.5 | +| 01000 | $-56.0 \leq n < -54.0$ | -55 | 11000 | $-42.0 \leq n$ | -42 | +| 01001 | n/u | | 11001 | n/u | | +| 01010 | n/u | | 11010 | n/u | | +| 01011 | n/u | | 11011 | n/u | | +| 01100 | n/u | | 11100 | n/u | | +| 01101 | n/u | | 11101 | Transparent | | +| 01110 | n/u | | 11110 | n/u | | +| 01111 | n/u | | 11111 | BC is under channel check procedure | | + +NOTE 1 – Noise levels in dBm0. + +NOTE 2 – The transmit unit noise measurement should be broadband. + +NOTE 3 – "n/u" means this code is not used – reserved for future use. + +NOTE 4 – It is suggested that because the noise inserted at the receive unit is broadband, the transmit unit noise measurement should also be broadband. + +NOTE 5 – The DCME transmit unit noise intervals are implementation specific, a tolerance of $\pm 2$ dB is suggested. + +NOTE 6 – When the background noise level is high ( $-46$ dBm0 or greater), some Administrations have indicated there may be a subjective benefit in inserting lower values of noise at the receive unit than those measured at the transmit unit. The contrast is most apparent when the noise spectral density at the DCME transmit unit is substantially different from the noise inserted at the receive unit. Since the noise inserted at the receive unit does not affect DCME interoperability, the selection of the noise level is left as an option ( $-50$ dBm0 is being considered). + +### 7.3.3 Asynchronous data word + +The asynchronous data word consists of 6 bits transmitted in a multiframe structure of 72 DCME frames (180 ms). This results in 432 bits per DCME multiframe for the asynchronous data message. The asynchronous data message holds a net number of 390 bits, including: + +- 360 bits IT related circuit supervision/alarm indication. +- 4 bits DCME bearer backward alarm. +- 4 bits DLC support message. +- 5 bits report channel check results. + +- 8 bits report BC related channel check results. +- 9 bits number of decoder under test. + +These bits are transmitted in the asynchronous data word according to Table 3 where bit 1 is transmitted first and bit 6 is transmitted last. + +**Table 3/G.767 – Asynchronous data word bit allocation** + +| DCME frame | Bit 1 (Note) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Message | +|------------|--------------|-------|-------|-------|-------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | Type: IT-related circuit supervision/alarm condition.
Designation: The number represents IT number.
Content:
0 = normal condition.
1 = alarm condition. | +| 1 | 7 | 8 | 9 | 10 | 11 | 12 | | +| ⋮ | ⋮ | ⋮ | ⋮ | ⋮ | ⋮ | ⋮ | | +| 58 | 349 | 350 | 351 | 352 | 353 | 354 | | +| 59 | 355 | 356 | 357 | 358 | 359 | 360 | | +| 60 | A | A | A | A | x | x | | +| 61 | p | q | r | s | x | x | Type: DLC support message.
Designation:
p: voice/voice-band data.
q: unrestricted 64 kbit/s.
Content:
0 = LL or UCA.
1 = HL or UCNA.
r, s = 2-bit binary code to identify each receive destination. | +| 62 | b1 | b2 | R | Y | T | x | Type: Identification of Rx bearer to which channel check results apply, if channel check is progressing normally.
Designation and content:
b1, b2: Rx bearer number.
R:
1 = channel check disregarded (high BER).
0 = progressing normally.
Y: channel check alarm.
0 = normal (pass).
1 = alarm (fail).
T: transmit channel check inhibit.
0 = channel check normal.
1 = channel check interrupted. | + +**Table 3/G.767 – Asynchronous data word bit allocation (concluded)** + +| DCME frame | Bit 1 (Note) | Bit 2 | Bit 3 | Bit 4 | Bit 5 | Bit 6 | Message | +|------------|--------------|-------|-------|----------|---------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 63 | BC (MSB) | BC | BC | BC | x | x | Type: BC related channel check results, transmitted one BC per DCME multiframe.
BC: 8-bit code represents the number of the BC for which the results apply. | +| 64 | BC | BC | BC | BC (LSB) | x | x | | +| 65 | D (MSB) | D | D | D | x | x | D: 9-bit code represents the number of the decoder for which the results apply. | +| 66 | D | D | D | D | D (LSB) | x | | +| 67-71 | x | x | x | x | x | x | Not used, reserved. | + +NOTE – x means unused, set to zero, reserved for future use. + +### 7.3.4 Error correction + +#### 7.3.4.1 Bit count + +Each assignment message contains 23 bits (9-bit BC, 9-bit IT and 5-bit synchronous data word). The 6-bit asynchronous data word appears once (regardless of AM mode) in the control channel. A spare of 12 bits is reserved for each DCME frame. It is therefore required to protect 41 bits in the single AM mode (23 + 6 + 12) and 64 bits (23 + 23 + 6 + 12) in the double AM mode. + +#### 7.3.4.2 Error correction code + +The control channel error correction code to be used is BCH(63,45) which uses the polynomial division remainder of: + +$$g(X) = X^{18} + X^{17} + X^{16} + X^{15} + X^9 + X^7 + X^6 + X^3 + X^2 + X^1 + 1$$ + +This is a triple error correcting code of minimum distance 7. The code is capable of protecting up to 45 bits by adding 18 check bits. + +Since the code is capable of protecting 45 bits by adding 18 check bits, and here it is required to protect only 41 data bits in single AM and 23 data bits in double AM, it is assumed that the 4 unused most significant bits of data in single AM and 22 unused most significant bits of data in double AM are all zero at both Tx and Rx side, as shown in Figures 3 and 4 respectively. + +![Diagram showing the structure of the BCH(63,45) code for single AM. It consists of three main parts: 4 unused bits (0000), 41 data bits, and 18 check bits. The total number of code bits is 63. The transmitted bits are the 41 data bits and the 18 check bits. The diagram shows the bit positions from MSB to LSB for each part.](124c6108c63173818afb8ed49521e22d_img.jpg) + +The diagram illustrates the bit structure of the BCH(63,45) code for single AM. It is divided into three segments: + + +- 4 unused bits (0000):** The first 4 bits, all set to zero. Their MSB and LSB are at the far left. +- 41 data bits:** The next 41 bits. The MSB is at the boundary after the unused bits, and the LSB is at the boundary before the check bits. +- 18 check bits:** The final 18 bits. The MSB is at the boundary after the data bits, and the LSB is at the far right. + + Above the segments, two double-headed arrows indicate: + + +- Total number of code bits:** Spanning the entire 63 bits (4 unused + 41 data + 18 check). +- Transmitted bits:** Spanning the 41 data bits and 18 check bits (total 59 bits). + + The diagram is labeled with 'T1528720-98' at the bottom right. + +Diagram showing the structure of the BCH(63,45) code for single AM. It consists of three main parts: 4 unused bits (0000), 41 data bits, and 18 check bits. The total number of code bits is 63. The transmitted bits are the 41 data bits and the 18 check bits. The diagram shows the bit positions from MSB to LSB for each part. + +**Figure 3/G.767 – Structure of BCH(63,45) code for single AM** + +![Diagram of BCH(63,45) code structure for double AM. It shows a 63-bit code word divided into three parts: 22 unused bits (0000000000000000000000), 23 data bits, and 18 check bits. The total number of code bits is 63. The transmitted bits are the 23 data bits and 18 check bits, totaling 41 bits. The diagram also indicates the MSB and LSB for each part.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +| | | | | | +|------------------------------------------|-------------------------------|----------------------|-----|--------------------------------------------------------| +| | ← Total number of code bits → | | | | +| | | ← Transmitted bits → | | | +| 22 unused bits
0000000000000000000000 | 23 data bits | 18 check bits | | | +| | MSB | LSB | MSB | LSB T1528730-98 | + +Diagram of BCH(63,45) code structure for double AM. It shows a 63-bit code word divided into three parts: 22 unused bits (0000000000000000000000), 23 data bits, and 18 check bits. The total number of code bits is 63. The transmitted bits are the 23 data bits and 18 check bits, totaling 41 bits. The diagram also indicates the MSB and LSB for each part. + +**Figure 4/G.767 – Structure of BCH(63,45) code for double AM** + +## 7.4 CC message transmission scheme + +### 7.4.1 Control channel structure + +#### 7.4.1.1 Single AM + +- assignment message: 23 bits +- asynchronous data word: 6 bits +- spare: 12 bits +- error correction: 18 bits +- dummy: 1 bit +- synchronization pattern: 20 bits +- *Total* 80 bits + +#### 7.4.1.2 Double AM + +- two assignment messages: 46 bits ( $23 \times 2$ ) +- asynchronous data word: 6 bits +- spare: 12 bits +- error correction: 36 bits ( $18 \times 2$ ) +- synchronization pattern: 20 bits +- *Total* 120 bits + +### 7.4.2 CC bit mapping + +Following are the control channel message transmission schemes for single AM and double AM modes and for USM. The schemes are given in Tables 4 through 7. Each row in the tables lists the bits to be transmitted in one PCM frame within the DCME frame. The leftmost bit of each row is transmitted first. For each field of the message (BC identification, IT identification, etc.) bit number 0 (e.g. it0, bc0) is the MSB, bit number 1 is MSB – 1 and so on. + +#### 7.4.2.1 Single IT USM + +Optionally, USM will be used to carry signalling information of a single IT and its associated *abcd* bits. In this case, the a2 and b2 fields in Tables 6 and 7 will be used to carry the *c* and *d* bits (respectively) associated with it1, the a3 and b3 fields will carry the *c* and *d* bits of it3, and the it2 and it4 fields will not be used. + +**Table 4/G.767 – CC message transmission scheme of a single AM control channel** + +| | | | | | +|---------------|----------------------------------------------------------------|-----|-----|-----| +| PCM frame #0 | u0 | bc0 | it0 | it1 | +| PCM frame #1 | u1 | bc1 | it2 | it3 | +| PCM frame #2 | u2 | bc2 | it4 | it5 | +| PCM frame #3 | u3 | bc3 | it6 | it7 | +| PCM frame #4 | u4 | bc4 | it8 | d0 | +| PCM frame #5 | u5 | bc5 | d1 | d2 | +| PCM frame #6 | u6 | bc6 | d3 | d4 | +| PCM frame #7 | u7 | bc7 | d5 | d6 | +| PCM frame #8 | u8 | bc8 | d7 | d8 | +| PCM frame #9 | u9 | sw0 | d9 | d10 | +| PCM frame #10 | u10 | sw1 | d11 | c0 | +| PCM frame #11 | u11 | sw2 | c1 | c2 | +| PCM frame #12 | u12 | sw3 | c3 | c4 | +| PCM frame #13 | u13 | sw4 | c5 | c6 | +| PCM frame #14 | u14 | aw0 | c7 | c8 | +| PCM frame #15 | u15 | aw1 | c9 | c10 | +| PCM frame #16 | u16 | aw2 | c11 | c12 | +| PCM frame #17 | u17 | aw3 | c13 | c14 | +| PCM frame #18 | u18 | aw4 | c15 | c16 | +| PCM frame #19 | u19 | aw5 | c17 | o | +| u0-u19: | Synchronization bits (unique word) (u0 = MSB) | | | | +| it0-it8: | IT number (it0 = MSB) | | | | +| bc0: | BC type | | | | +| bc1-bc8: | BC number (bc1 = MSB) | | | | +| sw0-sw4: | Synchronous data word of single assignment message (sw0 = MSB) | | | | +| aw0-aw5: | Asynchronous data word (aw0 = MSB) | | | | +| d: | spare | | | | +| o: | dummy bit | | | | +| c0-c17: | Check bits (c1 = MSB) | | | | + +**Table 5/G.767 – CC message transmission scheme of a double AM control channel** + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-----|-----|-----|-----| +| PCM frame #0 | u0 | bc0 | it0 | it1 | BC0 | BC1 | +| PCM frame #1 | u1 | bc1 | it2 | it3 | BC2 | BC3 | +| PCM frame #2 | u2 | bc2 | it4 | it5 | BC4 | BC5 | +| PCM frame #3 | u3 | bc3 | it6 | it7 | BC6 | BC7 | +| PCM frame #4 | u4 | bc4 | it8 | d0 | BC8 | IT0 | +| PCM frame #5 | u5 | bc5 | d1 | d2 | IT1 | IT2 | +| PCM frame #6 | u6 | bc6 | d3 | d4 | IT3 | IT4 | +| PCM frame #7 | u7 | bc7 | d5 | d6 | IT5 | IT6 | +| PCM frame #8 | u8 | bc8 | d7 | d8 | IT7 | IT8 | +| PCM frame #9 | u9 | sw0 | d9 | d10 | SW0 | SW1 | +| PCM frame #10 | u10 | sw1 | d11 | c0 | SW2 | SW3 | +| PCM frame #11 | u11 | sw2 | c1 | c2 | SW4 | C0 | +| PCM frame #12 | u12 | sw3 | c3 | c4 | C1 | C2 | +| PCM frame #13 | u13 | sw4 | c5 | c6 | C3 | C4 | +| PCM frame #14 | u14 | aw0 | c7 | c8 | C5 | C6 | +| PCM frame #15 | u15 | aw1 | c9 | c10 | C7 | C8 | +| PCM frame #16 | u16 | aw2 | c11 | c12 | C9 | C10 | +| PCM frame #17 | u17 | aw3 | c13 | c14 | C11 | C12 | +| PCM frame #18 | u18 | aw4 | c15 | c16 | C13 | C14 | +| PCM frame #19 | u19 | aw5 | c17 | C17 | C15 | C16 | +| u0-u19: Synchronization bits (unique word)
it0-it8: IT number of first assignment message
bc0-bc8: BC type and BC number of first assignment message
sw0-sw4: Synchronous data word of first assignment message
IT0-IT8: IT number of second assignment message
BC0-BC8: BC type and BC number of second assignment message
SW0-SW4: Synchronous data word of second assignment message
aw0-aw5: Asynchronous data word
d: spare
c0-c17: Check bits of correction block #1
C0-C17: Check bits of correction block #2 (C1 = MSB)
Unshaded bits are in correction block #1
Shaded bits are in correction block #2 | | | | | | | + +**Table 6/G.767 – CC USM message transmission scheme of a single AM control channel** + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------|-------|-------| +| PCM frame #0 | u0 | it1.0 | it2.0 | it2.1 | +| PCM frame #1 | u1 | it1.1 | it2.2 | it2.3 | +| PCM frame #2 | u2 | it1.2 | it2.4 | it2.5 | +| PCM frame #3 | u3 | it1.3 | it2.6 | it2.7 | +| PCM frame #4 | u4 | it1.4 | it2.8 | d0 | +| PCM frame #5 | u5 | it1.5 | d1 | d2 | +| PCM frame #6 | u6 | it1.6 | d3 | d4 | +| PCM frame #7 | u7 | it1.7 | d5 | d6 | +| PCM frame #8 | u8 | it1.8 | d7 | d8 | +| PCM frame #9 | u9 | a1 | d9 | d10 | +| PCM frame #10 | u10 | b1 | d11 | c0 | +| PCM frame #11 | u11 | a2 | c1 | c2 | +| PCM frame #12 | u12 | b2 | c3 | c4 | +| PCM frame #13 | u13 | o | c5 | c6 | +| PCM frame #14 | u14 | aw0 | c7 | c8 | +| PCM frame #15 | u15 | aw1 | c9 | c10 | +| PCM frame #16 | u16 | aw2 | c11 | c12 | +| PCM frame #17 | u17 | aw3 | c13 | c14 | +| PCM frame #18 | u18 | aw4 | c15 | c16 | +| PCM frame #19 | u19 | aw5 | c17 | o | +| u0-u19: Synchronization bits (unique word) (u0 = MSB)
it1.0-it1.8: First IT number (it1.0 = MSB)
it2.0-it2.8: Second IT number (it2.0 = MSB)
a1, b1: a and b signalling bits of 1 st IT
a2, b2: a and b signalling bits of 2 nd IT or c and d bits of 1 st IT
aw0-aw5: Asynchronous data word (aw0 = MSB)
d: spare
o: dummy bit
c0-c17: Check bits (c1 = MSB) | | | | | + +**Table 7/G.767 – CC USM message transmission scheme of a double AM control channel** + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------|-------|-------|-------|-------| +| PCM frame #0 | u0 | it1.0 | it2.0 | it2.1 | it3.0 | it3.1 | +| PCM frame #1 | u1 | it1.1 | it2.2 | it2.3 | it3.2 | it3.3 | +| PCM frame #2 | u2 | it1.2 | it2.4 | it2.5 | it3.4 | it3.5 | +| PCM frame #3 | u3 | it1.3 | it2.6 | it2.7 | it3.6 | it3.7 | +| PCM frame #4 | u4 | it1.4 | it2.8 | d0 | it3.8 | it4.0 | +| PCM frame #5 | u5 | it1.5 | d1 | d2 | it4.1 | it4.2 | +| PCM frame #6 | u6 | it1.6 | d3 | d4 | it4.3 | it4.4 | +| PCM frame #7 | u7 | it1.7 | d5 | d6 | it4.5 | it4.6 | +| PCM frame #8 | u8 | it1.8 | d7 | d8 | it4.7 | it4.8 | +| PCM frame #9 | u9 | a1 | d9 | d10 | a3 | b3 | +| PCM frame #10 | u10 | b1 | d11 | c0 | a4 | b4 | +| PCM frame #11 | u11 | a2 | c1 | c2 | o | c0 | +| PCM frame #12 | u12 | b2 | c3 | c4 | c1 | c2 | +| PCM frame #13 | u13 | o | c5 | c6 | c3 | c4 | +| PCM frame #14 | u14 | aw0 | c7 | c8 | c5 | c6 | +| PCM frame #15 | u15 | aw1 | c9 | c10 | c7 | c8 | +| PCM frame #16 | u16 | aw2 | c11 | c12 | c9 | c10 | +| PCM frame #17 | u17 | aw3 | c13 | c14 | c11 | c12 | +| PCM frame #18 | u18 | aw4 | c15 | c16 | c13 | c14 | +| PCM frame #19 | u19 | aw5 | c17 | c17 | c15 | c16 | +| u0-u19: Synchronization bits (unique word)
it1.0-it1.8: First IT number (it1.0 = MSB)
it2.0-it2.8: Second IT number (it2.0 = MSB)
it3.0-it3.8: Third IT number (it1.0 = MSB)
it4.0-it4.8: Fourth IT number (it2.0 = MSB)
a1, b1: a and b signalling bits of 1 st IT
a2, b2: a and b signalling bits of 2 nd IT or c and d bits of 1 st IT
a3, b3: a and b signalling bits of 3 rd IT
a4, b4: a and b signalling bits of 4 th IT or c and d bits of 3 rd IT
o: dummy bit
aw0-aw5: Asynchronous data word
d: spare
c0-c17: Check bits of correction block #1
C0-C17: Check bits of correction block #2 (C1 = MSB)
Unshaded bits are in correction block #1
Shaded bits are in block #2 | | | | | | | + +# 8 Variable bit rate and overload channel creation + +## 8.1 Principles + +The LD-CELP algorithm produces a 10-bit vector every 5 PCM frames (625 $\mu$ s) when operating in 16 kbit/s, an 8-bit vector in the same time-frame when operating in 12.8 kbit/s and a 6-bit vector in 9.6 kbit/s. + +The change of rate can be done once every 2.5 ms (a 16 kbit/s DCME frame). The above-mentioned rates are achieved using two basic packaging schemes: + +### 8.1.1 Creation of 16 kbit/s channels + +To create a 16 kbit/s channel, a single Quarter Byte (QB) is used to carry one channel. + +### 8.1.2 Creation of 12.8 kbit/s channels + +To create 12.8 kbit/s channels, 4 QBs are used to carry 5 channels. From each QB, 2 bits are "stolen" every 5 PCM frames therefore leaving 8 bits in that QB to carry one normal range 12.8 kbit/s channel. The total amount of "stolen" bits within the algorithmic frame is 8 ( $4 \times 2$ ) bits serving one additional 12.8 kbit/s overload channel. + +### 8.1.3 Creation of 9.6 kbit/s channels + +To create 9.6 kbit/s channels, 3 QBs are used to carry 5 channels. From each QB, 4 bits are "stolen" every 5 PCM frames therefore leaving 6 bits in that QB to carry one normal range 9.6 kbit/s channel. The total amount of "stolen" bits within the algorithmic frame is 12 ( $3 \times 4$ ) bits serving two additional 9.6 kbit/s overload channels. + +## 8.2 Overload channel creation + +### 8.2.1 Notations + +$\{i/j\}$ Bit number j of the LD-CELP vector of BC number i. The first bit is $j = 0$ and the last bit is $j = 9$ for 16 kbit/s, $j = 7$ for 12.8 kbit/s and $j = 5$ for 9.6 kbit/s. + +C 5-modulus counter that counts PCM frames within the DCME frame. + +### 8.2.2 Packaging schemes + +Many packaging schemes can be designed to accommodate the principles defined above. The specific schemes used in this Recommendation comply also with the requirement that no more than 2 bits of the same LD-CELP vector will be injected every PCM frame. + +#### 8.2.2.1 16 kbit/s packaging + +If a QB is assigned to carry traffic at 16 kbit/s from BC number N, then in $C = 0$ PCM frames (PCM frames #0, #5, #10 and #15 of the DCME frame) it carries $\{N/0\}$ as MSB and $\{N/1\}$ as LSB, in $C = 1$ PCM frames (PCM frames #1, #6, #11 and #16 of the DCME frame) it carries $\{N/2\}$ and $\{N/3\}$ and so on. + +#### 8.2.2.2 12.8 kbit/s packaging + +QBa, QBb, QBc and QBd are assigned to carry traffic from BCs I, J, K, L and M. This is done according to the scheme shown in Figure 5: + +| C | QB a | | QB b | | QB c | | QB d | | +|---|-----------------|-------|-----------------|-------|-----------------|-------|-----------------|-------| +| 0 | {M/0} | {M/1} | {J/0} | {J/1} | {K/0} | {K/1} | {L/0} | {L/1} | +| 1 | {I/0} | {I/1} | {M/2} | {M/3} | {K/2} | {K/3} | {L/2} | {L/3} | +| 2 | {I/2} | {I/3} | {J/2} | {J/3} | {M/4} | {M/5} | {L/4} | {L/5} | +| 3 | {I/4} | {I/5} | {J/4} | {J/5} | {K/4} | {K/5} | {M/6} | {M/7} | +| 4 | {I/6} | {I/7} | {J/6} | {J/7} | {K/6} | {K/7} | {L/6} | {L/7} | + +T1528740-98 + +NOTE – BC #M uses the "stolen" bits. + +**Figure 5/G.767 –12.8 kbit/s packaging** + +#### 8.2.2.3 9.6 kbit/s packaging + +QBa, QBb and QBc are assigned to carry traffic from BCs I, J, K, L and M. This is done according to the scheme shown in Figure 6: + +| C | QB a | | QB b | | QB c | | +|---|-----------------|-------|-----------------|-------|-----------------|-------| +| 0 | {I/0} | {I/1} | {J/0} | {J/1} | {L/0} | {L/1} | +| 1 | {I/2} | {I/3} | {J/2} | {J/3} | {M/0} | {M/1} | +| 2 | {I/4} | {I/5} | {J/4} | {J/5} | {K/0} | {K/1} | +| 3 | {L/2} | {L/3} | {M/2} | {M/3} | {K/2} | {K/3} | +| 4 | {L/4} | {L/5} | {M/4} | {M/5} | {K/4} | {K/5} | + +T1528750-98 + +NOTE – BCs #L and #M use the "stolen" bits. + +**Figure 6/G.767 – 9.6 kbit/s packaging** + +## 8.3 Overload channel creation process – The VBR scheme + +### 8.3.1 VBR lists + +The overload channel creation process maintains two lists: + +**Voice list** – This list contains the numbers of BCs which state voice (normal and overload), voice-avail and disconnect (normal range only). At initialization, this list contains all normal BC numbers subject to DSI. + +**QB list** – This list contains the numbers of QBs that can be used to carry voice traffic, including disconnected BCs. This list is actually a subset of the voice list and contains only the numbers of the normal range BCs. + +Both lists are maintained in ascending order and can be changed once every DCME frame. When overload channel creation is required, the VBR procedure enables the creation of all three rates (16 kbit/s, 12.8 kbit/s and 9.6 kbit/s) simultaneously. + +### 8.3.2 Notations + +| | | +|------------|----------------------------------------------------------| +| $N_{QB}$ | Length of the QB list. | +| $N_V$ | Length of the voice list. | +| $N_{16}$ | Number of QBs that carry traffic at 16 kbit/s. | +| $N_{12.8}$ | Number of QBs that carry traffic at 12.8 kbit/s. | +| $N_{9.6}$ | Number of QBs that carry traffic at 9.6 kbit/s. | +| $P_V$ | Pointer to the voice list. | +| $I_1$ | Intermediate variable for the calculation of $N_{9.6}$ . | + +### 8.3.3 VBR not required + +When $N_V = N_{QB}$ , all the BCs in the voice list are normal range BCs and no VBR is required. All BCs are carried at 16 kbit/s. Each QB of the QB list carries traffic from the BC which has the same ordering number as that QB. + +### 8.3.4 VBR required + +If $N_V$ is greater than $N_{QB}$ , VBR is required to create the additional overload channels3. In this case, there are more BCs than QBs and there is not always an association between BCs and QBs of the same number. The values of $N_{16}$ , $N_{12.8}$ and $N_{9.6}$ are calculated to determine how many QBs of the QB list will be used to carry traffic at each rate. These values are determined according to the following criteria: + +- Maximize instantaneous average bit rate of the traffic while using available bearer resources. +- Create enough channels for all BCs in the voice list. +- Minimize the number of 9.6 kbit/s channels. + +The formal representation of these criteria is: + +- $$\max \left( 16 \times N_{16} + 12.8 \times \frac{5}{4} N_{12.8} + 9.6 \times \frac{5}{3} N_{9.6} \right)$$ +- $$N_{16} + \frac{5}{4} N_{12.8} + \frac{5}{3} N_{9.6} \geq N_V$$ +- $$\min(N_{9.6})$$ + +--- + +3 The maximum number of channels that can be created using $N_{QB}$ QBs is $5 \times \text{int} \left( \frac{1}{3} N_{QB} \right) + N_{QB} \bmod 3$ . + +These criteria lead to the following rules used to uniquely determine the values of $N_{16}$ , $N_{12.8}$ and $N_{9.6}$ (see derivations in Supplement 38 to G-series): + +- a) If $N_{QB}$ is a multiplier of 3 and also $N_V = \frac{5}{3} N_{QB} - 1$ , then adjust $N_V$ by adding 1 to its value and by that create an extra dummy BC that will be virtually inserted to the voice list as entry number $P_V - 1$ (following is the calculation of $P_V$ ) so it will be carried at 9.6 kbit/s. +- b) Set $I_1$ to $\frac{4}{5} N_V - N_{QB}$ . If $I_1$ is smaller than zero, then set it to zero. +- c) If $I_1$ is not an integer, then add 1 to its value. +- d) Set $N_{9.6}$ to $3 \times \text{int}(I_1)$ +- e) Set $N_{12.8}$ to $4 \left( N_V - N_{QB} - \frac{2}{3} N_{9.6} \right)$ +- f) Set $N_{16}$ to $N_{QB} - N_{12.8} - N_{9.6}$ + +These rules assure compliance with the above-mentioned criteria. + +Next step is to assign BCs to QBs in a manner that will not discriminate BCs from a sampling rate point of view so that bit stealing will be uniformly randomly distributed in order to obtain similar average quality of all serviced ITs. + +A pointer $P_V$ shall be calculated as: + +$$P_V = (BC' + IT) \bmod N_V$$ + +where $BC'$ and $IT$ are extracted from the last assignment message (when in double AM mode $BC'$ and $IT$ shall be extracted from the first assignment message of the two). + +$BC'$ is the number represented by the nine bits that constitute the BC type and BC number. + +If USM is used and the frame is a signalling frame, then IT1 shall be used instead of $BC'$ and IT2 shall be used instead of $IT$ . + +The first $N_{16}$ QBs of the QB list shall carry traffic from BCs number $P_V$ through $P_V + N_{16} - 1$ (inclusive) of the voice list at 16 kbit/s, so that each QB shall carry traffic from one BC. The next + +$N_{12.8}$ QBs shall carry traffic from the next $\frac{5}{4} N_{12.8}$ BCs at 12.8 kbit/s, so that every 4 consecutive QBs of the QB list will carry traffic from 5 consecutive BCs of the voice list. The rest $N_{9.6}$ QBs shall + +carry traffic from the rest $\frac{5}{3} N_{9.6}$ BCs at 9.6 kbit/s, so that every 3 consecutive QBs of the QB list will carry traffic from 5 consecutive BCs of the voice list. Reference to the lists shall be done in a cyclic way, e.g. entry number one of the voice list follows entry number $N_V$ . + +The VBR scheme is demonstrated in Figure 7. + +![Diagram of the VBR scheme showing the relationship between the QB list and the Voice list. The QB list contains three blocks: N16, N12.8, and N9.6, with a total length NQB. The Voice list contains five blocks: N9.6^1, a small block (NOTE 1), N16, (5/4) * N12.8, and N9.6^2, with a total length NV. Arrows show mapping: N16 in QB list maps to N16 in Voice list; N12.8 in QB list maps to (5/4) * N12.8 in Voice list; N9.6 in QB list maps to the combination of N9.6^1 and N9.6^2 in Voice list. PV indicates the start of the Voice list.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +NOTE 1 – could be a dummy BC. + +NOTE 2 – $N_{9.6}^1 + N_{9.6}^2 = \frac{5}{3} \times N_{9.6}$ + +Diagram of the VBR scheme showing the relationship between the QB list and the Voice list. The QB list contains three blocks: N16, N12.8, and N9.6, with a total length NQB. The Voice list contains five blocks: N9.6^1, a small block (NOTE 1), N16, (5/4) \* N12.8, and N9.6^2, with a total length NV. Arrows show mapping: N16 in QB list maps to N16 in Voice list; N12.8 in QB list maps to (5/4) \* N12.8 in Voice list; N9.6 in QB list maps to the combination of N9.6^1 and N9.6^2 in Voice list. PV indicates the start of the Voice list. + +**Figure 7/G.767 – VBR scheme** + +# 9 ABPS calculations + +For the purpose of DLC calculations and thresholds and performance statistic, given an ADPCM bit per sample measure, its equivalent LD-CELP measure is: + +$$B_L = 0.4 \times (B_A + 1)$$ + +where $B_L$ is the LD-CELP bit per sample measure and $B_A$ is the ADPCM bit per sample measure. For example, the LD-CELP equivalent of an ADPCM ABPS of 3.7 bits/sample is $0.4 \times (3.7 + 1) = 1.88$ bits/sample. + +# 10 Channel check procedure + +A means of verifying end-to-end continuity and correct assignment of channels similar to the procedure described in Recommendation G.763 shall be provided. + +The use of the control channel for conveying channel check messages is the same as specified in Recommendation G.763. + +Details of the test procedure are for further study. + +# 11 Facsimile demodulation/remodulation + +## 11.1 General + +Fax demodulation in the 16 kbit/s DCME is performed as defined in Recommendation G.766 with the proper modifications resulting from the fact that the DCME frame is 2.5 ms, as described hereafter. + +## 11.2 Facsimile blocks, facsimile transport channels and fax banks + +One fax bank occupies two QBs, i.e. 80 bits per DCME frame (4 bits $\times$ 20 PCM frames). Facsimile blocks and facsimile transport channels occupy 40 bits each. All G.766 schemes for bit mapping from FDCs to fax blocks to FTCs to fax banks remain unchanged except for the trivial transition from 64 and 32 bits to 80 and 40 respectively (see Figures 8 and 9). + +![Diagram of Facsimile blocks showing FCC and Data sections. FCC contains Block 1 (Info. bits and Check bits). Data contains Block 2, Block 3, ..., Block m. Bit counts: 28 bits for Info. bits, 12 bits for Check bits, 40 bits for Block 2, and m even for Block m.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +The diagram illustrates the structure of a facsimile block. It is divided into two main sections: FCC (Facsimile Control Channel) and Data. The FCC section contains Block 1, which is further divided into 'Info. bits' (28 bits) and 'Check bits' (12 bits). The Data section contains multiple blocks: Block 2 (40 bits), Block 3, an ellipsis indicating intermediate blocks, and Block m (m even). A reference code 'T1528770-98' is present at the bottom right. + +Diagram of Facsimile blocks showing FCC and Data sections. FCC contains Block 1 (Info. bits and Check bits). Data contains Block 2, Block 3, ..., Block m. Bit counts: 28 bits for Info. bits, 12 bits for Check bits, 40 bits for Block 2, and m even for Block m. + +**Figure 8/G.767 – Facsimile blocks** + +## **11.3 Facsimile data channel** + +The demodulated data obtained from each trunk channel carrying a facsimile call is accumulated for a period of one DCME frame. The same stuffing scheme as in Recommendation G.766 is maintained with new values for demodulated bits per DCME frame for each facsimile transmission rate and, resulting from that, a new FDC length per rate, as shown in Table 8. + +![Diagram of Facsimile transport channels showing blocks 1, 2, and m mapped to PCM frames 0, 1, and 19. Each frame contains multiple FTCs (FTC 1, FTC 2, ...). Bits are labeled j(n) = bit j of block n.](474a819357587e34949a3e110ff19b30_img.jpg) + +This diagram shows the mapping of facsimile blocks to transport channels (FTCs) within PCM frames. Above the diagram, a legend states 'j(n) = bit j of block n'. The diagram shows three PCM frames: PCM frame No. 0, PCM frame No. 1, and PCM frame No. 19. Each frame contains multiple FTCs (FTC 1, FTC 2, ...). Bits from different blocks are interleaved across these FTCs. For example, in PCM frame No. 0, bits from Block 1 (1(1), 2(1), 1(2), 2(2)) are in FTC 1, and bits from Block 2 (1(3), 2(3), 1(4), 2(4)) are in FTC 2. Similar patterns are shown for other frames and blocks (e.g., Block 39 and 40 in PCM frame No. 19). A reference code 'T1528780-98' is at the bottom right. + +Diagram of Facsimile transport channels showing blocks 1, 2, and m mapped to PCM frames 0, 1, and 19. Each frame contains multiple FTCs (FTC 1, FTC 2, ...). Bits are labeled j(n) = bit j of block n. + +**Figure 9/G.767 – Facsimile transport channels** + +**Table 8/G.767 – Facsimile data channel length** + +| Facsimile transmission rate (kbit/s) | Nominal No. of bits in DCME frame | FDC length (bits) | +|--------------------------------------|-----------------------------------|-----------------------| +| R (Note 1) | $I(2.5 \times R)$ | $I(2.5 \times R) + 2$ | +| 33.6 | 84 | 86 | +| 31.2 | 78 | 80 | +| 28.8 | 72 | 74 | +| 26.4 | 66 | 68 | +| 24 | 60 | 62 | +| 21.6 | 54 | 56 | +| 19.2 | 48 | 50 | +| 16.8 | 42 | 44 | +| 14.4 | 36 | 38 | +| 12.0 | 30 | 32 | +| 9.6 | 24 | 26 | +| 7.2 | 18 | 20 | +| 4.8 | 12 | 14 | +| 2.4 | 6 | 8 | +| 0.3 (Note 2) | 1 | 6 | + +NOTE 1 – The same notations as in Recommendation G.766 are used. +NOTE 2 – The same FDC structure for V.21 as in G.766 is used. + +## **11.4 Facsimile control channel and forward error correction** + +Maintaining the same scheme used in Recommendation G.766, where the FCC occupies one facsimile block, the FCC of the 16 kbit/s DCME is 40 bits long holding 9 bits for IT field and 12 bits for message field plus 7 dummy bits and 12 check bits (see Figure 10). The same structure of the FCC is maintained, so only 12 (MSB) bits out of the 14 of the message field are used and the 2 remaining LSB bits are reserved for future provisions. + +The error correction code is BCH(63,51) which maintains the properties of BCH(31,21) used in Recommendation G.766, i.e. a double error correcting code with a minimum distance of 5. When FEC is ON, the facsimile data channels are divided into blocks of 28 consecutive bits each and 12 check bits are applied to each block. Since the code is capable of protecting 51 bits by adding 12 check bits and here it is required to protect only 28 bits, it is assumed that the 23 unused most significant bits of data are all zero at both Tx and Rx side, as shown in Figure 11. + +![](7d2d1d3870cd224c4430d19334557716_img.jpg) + +| | | | | +|----------|---------------|-----------------------|------------| +| IT Field | Message Field | d
u
m
m
y | Check Bits | +| (9 bits) | (12 bits) | (7 bits) | (12 bits) | +| | | | | + +T1530490-99 + +**Figure 10/G.767 – Facsimile control channel** + +![Figure 11/G.767 – Structure of BCH(63,51) code for 28 data bits. The diagram shows a 63-bit code word structure. The first 23 bits are '23 unused bits' (00000000000000000000000). The next 28 bits are '28 data bits', with MSB at the start and LSB at the end. The final 12 bits are '12 check bits', also with MSB at the start and LSB at the end. Arrows indicate 'Total number of code bits' (63) and 'Transmitted bits' (40, covering data and check bits). Reference T1528790-98 is shown.](c494cd874a082a97b50b3c4d3938f467_img.jpg) + +Figure 11/G.767 – Structure of BCH(63,51) code for 28 data bits. The diagram shows a 63-bit code word structure. The first 23 bits are '23 unused bits' (00000000000000000000000). The next 28 bits are '28 data bits', with MSB at the start and LSB at the end. The final 12 bits are '12 check bits', also with MSB at the start and LSB at the end. Arrows indicate 'Total number of code bits' (63) and 'Transmitted bits' (40, covering data and check bits). Reference T1528790-98 is shown. + +**Figure 11/G.767 – Structure of BCH(63,51) code for 28 data bits** + +## 11.5 FCC location on the bearer + +The FCC occupies QBs number 1 and 2 in single AM mode and QBs number 3 and 4 in double AM mode, as shown in Figures 12 and 13 respectively. In double AM mode, QB #2 can be used to carry voice. + +![Figure 12/G.767 – FCC location in single AM mode. The diagram shows a sequence of 6 quadrature bits (QB1 to QB6). QB1 and QB2 are shaded and labeled 'CC' and 'FCC' respectively. QB3, QB4, QB5, and QB6 are unshaded. Reference T1528800-98 is shown.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +Figure 12/G.767 – FCC location in single AM mode. The diagram shows a sequence of 6 quadrature bits (QB1 to QB6). QB1 and QB2 are shaded and labeled 'CC' and 'FCC' respectively. QB3, QB4, QB5, and QB6 are unshaded. Reference T1528800-98 is shown. + +**Figure 12/G.767 – FCC location in single AM mode** + +![Figure 13/G.767 – FCC location in double AM mode. The diagram shows a sequence of 6 quadrature bits (QB1 to QB6). QB1 is shaded and labeled 'CC'. QB2 is unshaded. QB3 and QB4 are shaded and labeled 'FCC'. QB5 and QB6 are unshaded. Reference T1528810-98 is shown.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +Figure 13/G.767 – FCC location in double AM mode. The diagram shows a sequence of 6 quadrature bits (QB1 to QB6). QB1 is shaded and labeled 'CC'. QB2 is unshaded. QB3 and QB4 are shaded and labeled 'FCC'. QB5 and QB6 are unshaded. Reference T1528810-98 is shown. + +**Figure 13/G.767 – FCC location in double AM mode** + +# 12 System statistics measurement + +System statistics measurements in the 16 kbit/s DCME shall be performed in the same manner as defined in 15.2.3/G.763 (1998), with the modification that the Statistic Test Interval (STI) is in the range of 10 to 60 minutes (in 5 minutes steps). + + + +# 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.7713-200911-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e32f57436a404304a88b2f58a7c7a1f9ef4e06c --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b483c0c487814dd21a660f81a8878d2e15580b5b20461bafdf4a4ca2773f9dc6 +size 61828 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a2d88be6bf8756f25edd1603ea6169982e28d94 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f9093b09d7f2af21a50eb64b64b81a2b768358e75a92e9bc941ef805bdbf8b1 +size 52188 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dda517bd758c83cb77cbfff2832515da7c6e5fcb --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/08dce7ad4c512fdf0c0cde60415fade6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbf67dfd5ffb3560e1122bf4cd76272bb427971a95f24aa7494fedcaf5f091c4 +size 24790 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b60e71fb18b803c099e4eb43906c154a24a4e6 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d95e2ad6124c824dad0584314cc2ef544c54a57f84bcc3841db87f699ae93ca9 +size 66436 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed4cf0ce6c84c9ac948719958788ae43d21c355d --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa57bacc65164832bf6a0eb391999dd89432c896d4391f4ab76910374dba5213 +size 47960 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60b84aed8d53791ae4e0a2c1a203d5196846a6ce --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f13100f0c2a54090ca2d5d56749e21adcb145155699d4da0c255018adde1775 +size 34499 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bdf929d2c43488be05c21b3c4fbfa8df4e40daa --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:add769ba60b5c44f802ec5dc989ee69a8c2056cb7350e83275adff8a6f64f4ce +size 35904 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/1c79f31a718d63814feb28ab46f64f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46423095aee4115f2c68eae59348049dfd2a8c42 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/1c79f31a718d63814feb28ab46f64f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2be95d640423dbe96e75afe298272cf793fa04dfc5b316024b490d0594afeeb9 +size 40902 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6ba3585365c82f70024d6f406caa1d21c15e15c --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f2c74bc9d95d9462ea96228c07d27e90c2455b608fac0ec7e3b683390b4f65b +size 19828 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e38e0c733c7914938a1efee6deadc57d223e7352 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893d7a435e13f458290d6efe1cbc5a12a912e01ad247db5d81fe90bf8b948a7f +size 23481 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a7b2239392bf4ec9a710306a64301fa6b66e0c3 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/2cde062fd82833415971a8bd1a2cafab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59fb4cb8c38900ceadf14511cef277e4458bee2f21bded023720cada5fae43a8 +size 48349 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1807d4d606f506dc7e60372ed5bf40a0bc73df86 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b9f4837b66feef63be4a5dbf22e7f08923bb6f35652bf25c9566ea8949c4655 +size 26539 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..706e48730d51dcb4682cbbe01547959e66716121 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ffa28be4407aafd70ae9c59b7064e9922780abd5cd1b1972ef5c51bc34c325 +size 62279 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70f3f07bfb0276db8416736442dd27a27172f561 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/339be989b91d5b1e73e5ecdc8401ca75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cf9ceb8b177e1d6c470221e452ecce58606d948b454eeb8963a6c2a763dc61a +size 23134 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d062c3df8fad19f9cee55f425eb9ba9ec52a2c --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0719579d835c4ac2424cb4f103bea999417ce0d7a401495e3424e1a496abac3 +size 42816 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6f27042dbca108c1ffd10693eb4180d80d4c993 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e96496f5208bb23f2b82db137d23b63cc3db1afeaa8ed14ac5dc1d73a7b9541e +size 15898 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faef7f524139fb32a97204842d95d6dd149e19b9 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e589ad8fac77e7051cbefb8fc142dd301ac85c05f3fca780c042c831798411c1 +size 40505 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a930fafc06c294e3473c569fb10a573ea248eaff --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/47a7beddcb8a1b7abdca746967e32bb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:945451f00f95f755a77286fe42112fa058d6b72d7155b9f02487060af75a1feb +size 88154 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7df7be104bb1a5f47a1c66b8061cd92382b4dd65 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/4a2b39fa33747a6553031cfe1e0947fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2940ca57dd89e4c463297d668830fd67fcc63aff0421f367fb37f5ba76e063ea +size 28991 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02f839f7b75376e117329cb93c7b84285e137699 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df66ba7fd8817560e8ea9eddb67f53686bf3194dec919b6f15eafa41d4997feb +size 38251 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bde7542b7508d0e698202e6d5e1e3fe589fda189 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05c6b0591cbb511d43e5a52f983d56bce63089bddf64eff22740cc0fb2e12157 +size 42415 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e13838c035e7385d335b32fbc0c40c68d489137 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837b498736ae1ec326cd5bb9581db4de16a2918ca81bb242e99096d813885249 +size 13855 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b77bcba3fe136e081084b8b35d1e249d51b137f1 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9e14ce7e558fd751599db11a0303ad35b78ea010844774123d4a8f140a2be66 +size 83532 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66347e7ff59355775467d5cbd1ac0ee40a227850 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82ec090999f6d8c6a78eeac1a024dca21f00208ab80fc41e708a374fa23261ca +size 45931 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b49bd34c6ed239457c1cb3cb482aac9198cf9ac2 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9102c1c22f627ca05248af7502fb684702510a6d4a49bac1c81e14c5ab69ea53 +size 54388 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33b7e358f77ec38cbf155cd045f57e335b0e28c0 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61fa0fbe967578a269d424a24680fb7a456feecc9672bcbd36bcd35bd931a56b +size 30401 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7965b5d58feb838880047b223d5e278279b908ac --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d23d1d1b2fd4596f1d2175bb3bc015bc35bdf8e3d70dce2584e3e76d05f33b9 +size 21225 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5bdea8a6548b26363422b9592dc87f5554a8fde --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f5dca0c04df437634c6b40dee3319f3a598ec10d853f08bae4f5be37efe7c3 +size 57945 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa1314e7e19749fa0316495b7bd5c325f9a1435 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63fc4dadc56e1e15d7593e836b8adc1916134145866179825d002a3048a5070c +size 50745 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec81983e2d50a3b12673dc322d12dc4711772d4 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:829c52f766594115092e9913602c23aace701205f6cd52aff9778b63908b471e +size 36483 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76bd57ebac8f17dbcce2b2a9e5281497d90e9959 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04d1086532d8acafda7babe39ca3b086a4a45821f6fa2bc0b0812568bad0a9ef +size 57079 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cd0120a02bfc86ebfb2c5e5dee85440ec234298 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efbac300ac9aab908895f10856f84609abe752075818f907054dc65a5c99ea94 +size 58181 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1901983875024ba11498773d3a4aa4e69a102530 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4f16caf3a07ed8a27208b68a1c6b52d88ee423d6f33c576b9b4e7030c204518 +size 21506 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8faae62f419c07ce94320e4b762c344e009beb0f --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33ae702641e1228cca56baf5c3720d0e80f9f91b577a01e82cf7352b91554c71 +size 88952 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb624037a552a3a333efce3b88e827c0cd093760 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0291546e523a062b7321f2754ec3d51c174370e978038ed1b813d1e2b9584d6b +size 63946 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3accf8b7b8cfa6f27c0da77f5362ed8c690bf22 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/af6c3f383ddc0c142cdd7e186cc78199_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3e5b872b90764d4c76d474ddd2eb69f146b0e2dc0d99a7022f40134bbc9f416 +size 31524 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..819dbcaa804c6e893b6591cdc7852b0d3ca739be --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c63ec85c1953e5f9d0ccd5fbd364d0c4fc1f1a6f483ac22fbc76e10179ef71b +size 56802 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..560579e2a4e0a241be1d43c53eda32580f188afa --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c455c691082c92112b1ebcd13c63571404cb90c4f76646b28138510e6df495d4 +size 55298 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ae2bb85b2da5eb90b2194ca2d49cca375b4bd88 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/bd0283b61b6a59829e9370b29076c79a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6512ccaa8d516490fea559d18d363b65b59cfbc7c4b1e33857b0d9d2e2ebd093 +size 56007 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbcab39395d53eafd12ac654fd78d7fc0fefc1c9 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:385862185a6f1055f11ecb217d10a885f0edac2d0eadd0ca5e1d4083f45b27ad +size 71828 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/cd3e29b6d40dce0580fa43b721157489_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/cd3e29b6d40dce0580fa43b721157489_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87558395da5ee382264807f15eb54e04596cc979 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/cd3e29b6d40dce0580fa43b721157489_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a20c0b32f01b325a2107d3a55b973bbd999b07717be6f5d6b6445b60b051c2b +size 30505 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/cf018d13814389b0bd7f94a2f9bb812a_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/cf018d13814389b0bd7f94a2f9bb812a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3dd09d1f0e8b8262098233f142cd57a9a487d6d --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/cf018d13814389b0bd7f94a2f9bb812a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b499337c203f4330cd4cdf31a2b6080e096286cbda6d633bd18dabd946a9dcc9 +size 42220 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f31b6c0a8366f643bf9da9b2f7548ad6fd2d565 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/cfb98c691c1af5befe32ff9442eea511_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e715335db7346c079ff35388d2ae9ed956cfe7e2a2eb04fd14fcab2118405de8 +size 34544 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7891ad4da866f8afa77ca25dc85476b390f8447 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a02d9c72e32cfb302c5fd9b64b961d1940f565b2e5e663e9ed88d0336be29b1 +size 7391 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f1f29079362cf0a05b673166e7da050346abec1 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41d80af4c96e0714659ad1d27683ef37637603f7d43e8f6241579e95b2aab618 +size 199016 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/d510bddda14c44163bbeee33b491a105_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/d510bddda14c44163bbeee33b491a105_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c572658aed589f6af99927771b5b8e6067ab445 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/d510bddda14c44163bbeee33b491a105_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7662f4f6304bfc795d19ca277c9a8526a9e7931f59082a7b390b7ad0ef28c24e +size 33244 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c593a7ea02e37ff073159cf56504f12f3c4779c --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dad7f3ef29592440aa7209ad074ae44bc7d72f61964568dfe6baa31950de956 +size 58280 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ca3981387bce6634b3ca9cf9abb59becd83de6b --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e7430dd0804129c2040de297c8fc45499b7b0addaa6971e3fac4bf6a77ca588 +size 38717 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48e7711bd6cc5f3b8e8108b55e1e497e40c22764 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b123b5af2169cdf5850c5c028b6fd7ec4788c1fabd8bdf98e30c27d8d5adcb68 +size 41769 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a2991f3d8f6b44b3de505641a65144ea153cb0c --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd71c3593037468bcd99eda8a482b7159eebdbcab098a95fc08a717f527a1488 +size 38318 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86ec9cdea18b90185fb1137d332e9a470cd891d0 --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fdb602f6112b2c4dd506fbbece6d740537c93e4160169d48bc26076bfc0447b +size 30845 diff --git a/marked/G/T-REC-G.7713-200911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.7713-200911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74fd6855381668f7e3526fee0d1f77472b16d38f --- /dev/null +++ b/marked/G/T-REC-G.7713-200911-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5be1245a11df66dd52946c88f71beb1470f57178fdc9b459f7a0ad7bdba8e10f +size 34475 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..346a7302e493c0c2321a269d88e198ddc3e41225 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:316268d6927901392475ce136d00393b6f7fcd8616190cd1c6cd62d9a893d4d5 +size 59529 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3afd3e32efa9e2a376b43f7eeebaebdc633519f --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d56b6fa31ce8c27bef1a71dd9e3d1b7d8d7f2e9594bd814d0f7e7aaecad17654 +size 67842 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02618e1c9d69bb72ac37b909dab893cd21430aee --- /dev/null +++ b/marked/G/T-REC-G.774.8-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.8-200102-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb4b603b29d7ae42d5bf8a8abf4a0cd4c0270651 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0f8404f58b5174081d1b489582ea12b4a80371a322ce619eca3e285cb54994b +size 63790 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9adc735e9cb1dd462dada21bbd86b3571006a442 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ae60934ee880603d5cda2d41cb49ca564183e9db3d30743c4b90843050619b6 +size 35843 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1d7d0341e25f10d29ba4830ec2ac18968ddce72 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6ee0462b2179a6dc376fce1c301ae6fd491e79e0ce8774e5bc5fc08d4a168b2 +size 35920 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c896e2d7ed2382ea222608c7340caa2acbc74621 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ea56f8db217c6053cc0793d311f34b4ad9ceabc96d34be7752a4ee5bcf1c308 +size 42474 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc862c0af8c1148a10e5368dcbab9bf30e3385bf --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19a5e66a79504790d9382fcfd4acac1b0e323b423b8c0c6a63088e11af95e6f7 +size 68703 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9b022576f995e0a461c39e772074fa738196853 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d37f9c0e8a697b6648cfe1de61c055ec9b4762b0abe8502ead60fe8a96ef0ccb +size 92876 diff --git a/marked/G/T-REC-G.774.8-200102-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/G/T-REC-G.774.8-200102-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7167c54a10446e133d5233c665f96319ab275473 --- /dev/null +++ b/marked/G/T-REC-G.774.8-200102-I_PDF-E/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a544e569e737aeb4e80093ad3fe788379f70879ef0a55e762f8873b9fdb22c83 +size 9923 diff --git a/marked/G/T-REC-G.775-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.775-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc6438bcedc9e72173b2d8e74cd31c264ae32aeb --- /dev/null +++ b/marked/G/T-REC-G.775-199810-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40203e46b9f9a68e88bdb204bdd4b7e5899358c088ed2f2902abbc4eb57db8cb +size 8190 diff --git a/marked/G/T-REC-G.775-199810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg b/marked/G/T-REC-G.775-199810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..535605a8a558303f66e9122d511108b43b5dab44 --- /dev/null +++ b/marked/G/T-REC-G.775-199810-I_PDF-E/ebff22fb5dd6f50a90e44dca0f82f285_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab87ba2448d5d6dd06ad9ed9b8d43f08bb95fcea3b9e37f12b1a7ea22ab76307 +size 38560 diff --git a/marked/G/T-REC-G.798.1-201301-I_PDF-E/raw.md b/marked/G/T-REC-G.798.1-201301-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2f466fbe7cbba690be29fe4bb2e311f53c8d1c07 --- /dev/null +++ b/marked/G/T-REC-G.798.1-201301-I_PDF-E/raw.md @@ -0,0 +1,1333 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.798.1** + +(01/2013) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital terminal equipments – Other terminal equipment + +# --- **Types and characteristics of optical transport network equipment** + +Recommendation ITU-T G.798.1 + +![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a globe with a red lightning bolt striking it, symbolizing global connectivity and telecommunications. 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 | +| 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.1 + +# Types and characteristics of optical transport network equipment + +# Summary + +Recommendation ITU-T G.798.1 provides an overview of the functions of optical transport network (OTN) equipment and examples of possible OTN equipment types based on the atomic functions specified in Recommendation ITU-T G.798. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|-----------------------------|------------|-------------| +| 1.0 | ITU-T G.798.1 | 2011-04-13 | 15 | +| 2.0 | ITU-T G.798.1 | 2013-01-13 | 15 | +| 2.1 | ITU-T G.798.1 (2013) Amd. 1 | 2013-08-29 | 15 | + +## Keywords + +Optical transport network. + +## 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 ..... | 2 | +| 3.1 | Terms defined elsewhere ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 5 | +| 6 | OTN layer hierarchy, domains, topology and connections ..... | 5 | +| 6.1 | Network overview ..... | 5 | +| 6.2 | Layer networks ..... | 5 | +| 6.3 | OTN OAM functions..... | 8 | +| 7 | Operations, administration, maintenance and provisioning ..... | 9 | +| 7.1 | OAM applications ..... | 9 | +| 7.2 | TMN access ..... | 19 | +| 7.3 | Timing function ..... | 20 | +| 7.4 | Control plane access ..... | 21 | +| 7.5 | Connection management ..... | 21 | +| 8 | Protection switching ..... | 21 | +| 8.1 | Linear protection ..... | 21 | +| 8.2 | Shared ring protection ..... | 21 | +| 8.3 | Shared mesh protection ..... | 21 | +| 9 | Interface ports on optical transport network equipment..... | 21 | +| 9.1 | I-NNI ..... | 21 | +| 9.2 | E-NNI ..... | 23 | +| 9.3 | UNI ..... | 25 | +| 10 | Basic OTN equipment types..... | 25 | +| 10.1 | 3R regeneration compound function ..... | 26 | +| 10.2 | OTN network termination unit (NTU) ..... | 26 | +| 10.3 | Wavelength add/drop multiplexer (WADM) ..... | 27 | +| 10.4 | Wavelength cross connect (WXC) ..... | 27 | +| 10.5 | Sub-wavelength cross connect (SWXC) ..... | 28 | +| 10.6 | Optical amplifier..... | 30 | +| 10.7 | Sub-wavelength add/drop multiplexer (SWADM) ..... | 30 | +| 11 | OTN and packet transport network (PTN) hybrid equipment..... | 30 | +| | Appendix I – ODU multiplexing considerations ..... | 32 | +| | Appendix II – Examples of SNC protection implementation ..... | 33 | +| II.1 | Analysis ..... | 33 | + +| | | +|--------------------------------------------------------------------------|----| +| Appendix III – OTN link and connection examples ..... | 37 | +| Appendix IV – Multi-layer OTM-n network node interface ..... | 45 | +| Appendix V – Converged packet and optical transport equipment type ..... | 46 | + +## Recommendation ITU-T G.798.1 + +# Types and characteristics of optical transport network equipment + +# 1 Scope + +This Recommendation provides an overview of the functions of optical transport network (OTN) equipment and examples of possible OTN equipment types. It does not define required OTN equipment types. The Recommendation is based on the OTN atomic functions specified in [ITU-T G.798]. + +# 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 (2001), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [ITU-T G.707] Recommendation ITU-T G.707 (2007), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2009), *Interfaces for the optical transport network (OTN)*. +- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- [ITU-T G.798] Recommendation ITU-T G.798 (2010), *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 (2009), *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 (2008), *Terms and definitions for optical transport networks (OTN)*. +- [ITU-T G.872] Recommendation ITU-T G.872 (2001), *Architecture of optical transport networks*. +- [ITU-T G.873.1] Recommendation ITU-T G.873.1 (2011), *Optical Transport Network (OTN): Linear protection*. +- [ITU-T G.874] Recommendation ITU-T G.874 (2010), *Management aspects of optical transport network elements*. +- [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 (2010), *Architecture and specification of data communication network.* +- [ITU-T G.8012.1] Recommendation ITU-T G.8012.1/Y.1308.1 (2012), *Interfaces for the Ethernet transport network.* +- [ITU-T G.8021] Recommendation ITU-T G.8021/Y.1341.1 (2012), *Types and characteristics of Ethernet transport network equipment.* +- [ITU-T G.8112] Recommendation ITU-T G.8112/Y.1371 (2012), *Interfaces for the MPLS Transport Profile layer network.* +- [ITU-T G.8121] Recommendation ITU-T G.8121/Y.1381 (2012), *Characteristics of MPLS-TP equipment functional blocks.* +- [ITU-T G.8080] Recommendation ITU-T G.8080/Y.1304 (2006), *Architecture for the automatically switched optical network (ASON).* +- [ITU-T I.112] Recommendation ITU-T I.112 (1984), *Vocabulary of terms for ISDNs.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 **adaptation function (A)**: [ITU-T G.806]. +- 3.1.2 **compound function**: [ITU-T G.806]. +- 3.1.3 **connection function (C)**: [ITU-T G.806]. +- 3.1.4 **defect**: [ITU-T G.806]. +- 3.1.5 **fault cause**: [ITU-T G.806]. +- 3.1.6 **function**: [ITU-T G.806]. +- 3.1.7 **network**: [ITU-T G.805]. +- 3.1.8 **ODUk path (ODUkP)**: [ITU-T G.870]. +- 3.1.9 **ODUk TCM (ODUkT)**: [ITU-T G.870]. +- 3.1.10 **optical channel (OCh[r])**: [ITU-T G.870]. +- 3.1.11 **optical channel data unit (ODUk)**: [ITU-T G.870]. +- 3.1.12 **optical channel payload unit (OPUk)**: [ITU-T G.870]. +- 3.1.13 **optical channel transport unit (OTUk[V])**: [ITU-T G.870]. +- 3.1.14 **optical channel with full functionality (OCh)**: [ITU-T G.870]. +- 3.1.15 **optical channel with reduced functionality (OChr)**: [ITU-T G.870]. +- 3.1.16 **optical multiplex section (OMS)**: [ITU-T G.872]. +- 3.1.17 **optical physical section of order n (OPSn)**: [ITU-T G.870]. +- 3.1.18 **optical supervisory channel (OSC)**: [ITU-T G.870]. +- 3.1.19 **optical transmission section (OTS)**: [ITU-T G.872]. +- 3.1.20 **optical transport hierarchy (OTH)**: [ITU-T G.870]. +- 3.1.21 **optical transport module (OTM-n[r].m)**: [ITU-T G.870]. + +- 3.1.22 optical transport network (OTN):** [ITU-T G.870]. +- 3.1.23 subnetwork connection (SNC):** [ITU-T G.805]. +- 3.1.24 switching:** [ITU-T I.112]. +- 3.1.25 trail termination function (TT):** [ITU-T G.806]. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|---------|--------------------------------------| +| ADM | Add-Drop Multiplexer | +| AIS | Alarm Indication Signal | +| AMP | Asynchronous Mapping Procedure | +| 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 | +| BMP | Bit-synchronous Mapping Procedure | +| CBR | Constant Bit Rate signal | +| COMMS | Communications channel | +| EEC | Ethernet Equipment Clock | +| E-NNI | External Network Node Interface | +| FDI | Forward Defect Indication | +| FDI-O | Forward Defect Indicator Overhead | +| FDI-P | Forward Defect Indicator Payload | +| GMP | Generic Mapping Procedure | +| HO | High Order | +| IAE | Incoming Alignment Error | +| I-NNI | Internal Network Node Interface | +| IP | Internet Protocol | +| LCK | Locked indication | +| LF | Local Fault | +| LO | Low Order | +| LOA | Loss Of Alignment | +| 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 | +| LSP | Label Switched Path | +| MPLS-TP | Multiprotocol Label Switching – Transport Profile | +| MSIM | Multiplex Structure Identifier Mismatch | +| OAM | Operations, Administration and Maintenance | +| OCh | Optical Channel | +| OCI | Open Connection Indication | +| ODU | Optical Data Unit | +| OH | Overhead | +| OLA | Optical Line Amplifier | +| OMS | Optical Multiplex Section | +| ONTU | OTN Network Termination Unit | +| OPS | Optical Physical Section | +| OTM | Optical Transport Module | +| OTN | Optical Transport Network | +| OTS | Optical Transport Section | +| OTU | Optical Transport Unit | +| PMI | Payload Missing Indication | +| PRC | Primary Reference Clock | +| PTN | Packet Transport Network | +| SEC | SDH Equipment Clock | +| SNC | Subnetwork Connection | +| SNC/S | Subnetwork Connection protection with Sublayer monitoring | +| SSU | Synchronization Supply Unit | +| STM-N | Synchronous Transport Module, level N | +| SWXC | Sub-Wavelength Cross Connect | +| TDM | Time Division Multiplexing | +| TIM | Trail trace Identifier Mismatch | +| UNI | User Network Interface | +| VLAN | Virtual Local Area Network | +| VPN | Virtual Private Network | +| WADM | Wavelength Add-Drop Multiplexer | +| WDM | Wavelength Division Multiplexing | +| WXC | Wavelength Cross Connect | + +# 5 Conventions + +None. + +# 6 OTN layer hierarchy, domains, topology and connections + +## 6.1 Network overview + +Figure 6-1 shows a simplified view of an OTN network that consists of two optical domains (identified by the clouds) and showing different types of OTN equipment within those clouds. At the customer premises there may be client nodes, or there may be a client node and an OTN network termination unit (ONTU). Within the service provider domains there are ONTUs, wavelength add-drop multiplexers (WADMs)/cross connects, sub-wavelength cross connects (SWXC), and optical line amplifiers (OLAs). + +![Figure 6-1 – OTN network example. A diagram showing two optical domains, Domain A and Domain B, connected by a central SWXC node. Domain A contains a WADM/WXC and an SWXC node. Domain B contains an OLA, two WADM/WXC nodes, and two SWXC nodes. Customer premises are connected to ONTUs, which are then connected to client nodes or directly to SWXC nodes.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates an OTN network topology with two optical domains, Domain A and Domain B, represented by grey clouds. Domain A contains a WADM/WXC node and an SWXC node. Domain B contains an OLA (Optical Line Amplifier), two WADM/WXC nodes, and two SWXC nodes. A central SWXC node acts as a bridge between the two domains. On the left, a 'Customer premises' box contains an ONTU connected to a 'Client node', which is further connected to an SWXC node within Domain B. On the top right, another 'Customer premises' box contains an ONTU connected to a 'Client node', which is connected to an SWXC node between Domain A and the central SWXC node. On the bottom right, a third 'Customer premises' box contains a 'Client node' connected directly to an SWXC node within Domain B. The central SWXC node is connected to the SWXC node in Domain A, the SWXC node in Domain B, and the ONTU in the top-right customer premises. The diagram is labeled 'G.798.1(13)\_F6-1' in the bottom right corner. + +Figure 6-1 – OTN network example. A diagram showing two optical domains, Domain A and Domain B, connected by a central SWXC node. Domain A contains a WADM/WXC and an SWXC node. Domain B contains an OLA, two WADM/WXC nodes, and two SWXC nodes. Customer premises are connected to ONTUs, which are then connected to client nodes or directly to SWXC nodes. + +Figure 6-1 – OTN network example + +## 6.2 Layer networks + +[ITU-T G.872] decomposes an OTN into four layers: optical channel (OCh), optical multiplex section (OMS), optical transport section (OTS), and physical media. In cases where there is a single wavelength, the OMS and OTS layers are collapsed into a single optical physical section (OPS). The OCh layer is further decomposed into digital section (optical transport unit (OTU)) and digital path (optical data unit (ODU)) sublayers. The ODU layer further supports time division multiplexing (TDM) of lower-speed ODU clients into a server ODU. + +For the purposes of this Recommendation, it is convenient to introduce some additional terminology to differentiate the ODU layers when TDM is used: the optical services layer (low order ODU, service ODU, or sub-wavelength), which represents an ODU into which a service is mapped, and the optical path layer (high order ODU, wavelength), which represents an ODU into which low order ODUs are multiplexed. The use of the optical path layer is optional. Further, within this Recommendation, the term optical section is used to refer to either the OMS and OTS layers or the OPS layer. + +Figure 6-2 shows how these layers are related to one another. The dashed boxes labelled "Lower layers" indicate that the detail of the layers below the application services layer or the optical services layer are not included in the figure; the lower layers that are present will depend on whether the service ODU begins on the customer or network side of the UNI. + +![Figure 6-2 – OTN network layer stack example. This diagram illustrates the OTN layer stack between two User networks connected via an Optical transport network. The stack consists of several layers: Application services layers (top, pink), Optical services layer (LO ODU) (yellow), Optical path layer (HO ODU) (green), OTUk/OCh layer (light blue), Optical section layer (OPS/OMS) (blue), and Physical media layer (bottom, grey). The diagram shows how data flows from the User network through various multiplexers (1:1 or n:1 packet or TDM mux, OCh mux, ODU mux) and across the layers. The Optical transport network is shown as a horizontal double-headed arrow at the top. The 'Lower layers' are indicated by dashed boxes on the sides.](007b053fe94a8348f75128a584503fd0_img.jpg) + +The diagram illustrates the OTN network layer stack. At the top, the **Application services layers** (pink) are shown, which include circuits (STM-N, FC-x, xGE, xG SDI, ESCON, IB, OTUk, ...) and packets (Ethernet, MPLS-TP). These layers are connected to the **Optical transport network** (represented by a double-headed arrow) via **UNI** (User Network Interface) points. Below the application services layers is the **Optical services layer (LO ODU)** (yellow), which contains ODUk (k = 0, 1, 2, 2e, 3, 4, flex). This layer is connected to the **Optical path layer (HO ODU)** (green) via **1:1 or n:1 (packet or TDM mux)** units. The optical path layer contains ODUk (k = 1, 2, 3, 4). Below the optical path layer is a layer containing **OTUk, OTUkV, k = 1, 2, 3, 4** and **OCh**. This is followed by the **Optical section layer (OPS)** (blue) and the **Optical section layer (OMS) (OTS)** (blue). The bottom layer is the **Physical media layer (ITU-T G.693, ITU-T G.959.1, ...)** (grey). The stack is flanked by dashed boxes labeled **Lower layers**. Various multiplexers are shown throughout the stack, including **1:1 or n:1 (OChr mux)**, **n:1 (OCh mux)**, and **n:1 (ODU mux)**. + +Figure 6-2 – OTN network layer stack example. This diagram illustrates the OTN layer stack between two User networks connected via an Optical transport network. The stack consists of several layers: Application services layers (top, pink), Optical services layer (LO ODU) (yellow), Optical path layer (HO ODU) (green), OTUk/OCh layer (light blue), Optical section layer (OPS/OMS) (blue), and Physical media layer (bottom, grey). The diagram shows how data flows from the User network through various multiplexers (1:1 or n:1 packet or TDM mux, OCh mux, ODU mux) and across the layers. The Optical transport network is shown as a horizontal double-headed arrow at the top. The 'Lower layers' are indicated by dashed boxes on the sides. + +G.798.1(13)\_F6-2 + +**Figure 6-2 – OTN network layer stack example** + +These layer networks are depicted from the viewpoint of network management, however other perspectives are possible. OTN network management manages the OTM-n physical media connections, optical section connections, optical path connections and optical services connections. An OTU or OCh connection is always 1-to-1 related to an ODU network connection (in the case of no 3R regeneration or optical cross-connection) or link connection (in the case where 3R regeneration or optical cross-connection occurs between ODU endpoints). + +### 6.2.1 Application services layer + +The application services layer network instance is the client of the OTN. Details of this layer are outside the scope of this Recommendation. Client signals may be constant bit rate circuit signals like STM-N, 802.3 Ethernet, fibre channel, and high definition SDI, or packet signals like Ethernet VLANs, MPLS-TP LSPs and IP VPN or Internet. + +### 6.2.2 Optical services layer + +The optical services layer network instance provides point-to-point and point-to-multipoint transport network services. Those services are supported by means of an ODU connection, which carries a single instance of the client service. From the perspective of this network, the ODU in the optical services layer is referred to as a low order ODU (LO ODU). The optical services layer network provides OAM for inherent monitoring of the client service. The structure of the client service may comprise a single client signal, a bundle of such client signals or a port-based client signal. + +Client signals may be mapped into ODU signals within the bounds of the optical transport network, or outside those bounds and inside the user network. + +In situations where a service transits multiple domains (or operators), the optical services layer of Domain A may also be the optical services layer of Domain B as well (peering relationship). Alternatively, the optical services layer of Domain A may be multiplexed to an optical path layer in Domain B (client/server relationship). The optical services layer in Domain A may also be multiplexed to an optical path layer within Domain A. + +### 6.2.3 Optical path layer + +The use of an optical path layer is optional. It is only present when time-division multiplexing of ODUs from the optical services layer into a wavelength is required. The optical path layer is supported by an ODU connection (at a higher rate than that of the ODUs supporting the optical services layer). From the perspective of the network in which it exists, the ODU supporting the optical path is referred to as a high order ODU (HO ODU). + +The optical path layer network establishes the point-to-point optical service layer links (i.e., LO ODU layer topology) in metro and core subnetwork domains. Those links are supported by means of a point-to-point ODU connection, which starts/ends at the edges of metro domains. The optical path layer network instance provides OAM for monitoring, which may also be used to trigger protection within the optical path layer or optical service layer compound link SNC group protection switching, as specified in [ITU-T G.808.1]. + +In situations where a service transits multiple domains (or operators), the optical path layer of Domain A is the optical services layer for Domain B. Within Domain B, the operator may perform further time-division multiplexing of the Domain B optical services layer into an optical path layer within Domain B. + +### 6.2.4 OTU and OCh layers + +The OTU layer provides the digital section layer that allows monitoring of the OCh. The OCh is the individual optical channel. There is always a 1:1 association between an OTU and OCh, and these two layers always terminate at the same location. From the perspective of the OTU layer, there is no difference between HO and LO ODUs; the mapping of either type of ODU onto an OTU/OCh is identical. The OTU layer establishes the point-to-point ODU layer links. + +### 6.2.5 Optical section layers + +The optical section layer network consists of either the OPS layer network, or the OMS/OTS layer networks. + +The OPS layer network provides the capability to monitor the physical media layer point-to-point connections for a loss of signal condition and establish point-to-point OCh layer links. Those links carry one or more ODU signals between OTN network nodes. + +The OMS/OTS layer network provides the capability to monitor the physical media layer point-to-point connections and establishes the point-to-point OCh layer links (OCh layer topology). Those links carry one or more ODU signals between OTN network nodes. Those links and their monitoring are supported by means of a point-to-point OMS connection, which starts/ends typically at wavelength or sub-wavelength cross-connects. An OMS connection is supported by means of one or more OTS connections that start/end at the same points where the physical media layer connection starts/ends. + +### **6.2.6 Physical media layers** + +The Physical media layer network provides the fibre interconnection between OTN systems. Details of this layer are outside the scope of this Recommendation. + +## **6.3 OTN OAM functions** + +The optical transport network supports ITU-T G.709-based OTN OAM in each of the OTN layer networks. In the optical path and optical services layers, ODU trail termination functions are present; optionally, ODU tandem connection monitors and/or end-to-end non-intrusive monitor functions may be present. For ODUs that are mapped onto wavelengths, OTU and OCh trail termination functions are also present. Trail termination functions are also present in the optical section layer (either OMS and OTS, or OPS). + +Figure 6-3 shows an example with several different types of network elements and the OAM functions that are present in each. In this figure, there are no tandem connection functions present, but such functions could be added to the ODU layers. + +![Figure 6-3: Example of an OTN layer stack showing OAM entities. The diagram illustrates the hierarchy of OTN layers and the placement of OAM entities (represented by ovals) at various points. The layers from top to bottom are: Application services layer (pink), Optical service layer (LO ODU) (yellow), Optical path layer (HO ODU) (green), OTU layer (orange), OCh layer (light blue), OMS layer (medium blue), and OTS layer (dark blue). OAM entities are shown at the boundaries between these layers, specifically at the LO ODU, HO ODU, OTU, OCh, OMS, and OTS interfaces. The bottom of the diagram shows the physical components: OTN access node/NTU, Sub-Wavelength crossconnect/ADM, Optical amplifier, Sub-Wavelength crossconnect/ADM, Wavelength crossconnect/ADM, and OTN access node/NTU.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Figure 6-3: Example of an OTN layer stack showing OAM entities. The diagram illustrates the hierarchy of OTN layers and the placement of OAM entities (represented by ovals) at various points. The layers from top to bottom are: Application services layer (pink), Optical service layer (LO ODU) (yellow), Optical path layer (HO ODU) (green), OTU layer (orange), OCh layer (light blue), OMS layer (medium blue), and OTS layer (dark blue). OAM entities are shown at the boundaries between these layers, specifically at the LO ODU, HO ODU, OTU, OCh, OMS, and OTS interfaces. The bottom of the diagram shows the physical components: OTN access node/NTU, Sub-Wavelength crossconnect/ADM, Optical amplifier, Sub-Wavelength crossconnect/ADM, Wavelength crossconnect/ADM, and OTN access node/NTU. + +G.798.1(13)\_F6-3 + +**Figure 6-3 – Example of an OTN layer stack showing OAM entities** + +# 7 Operations, administration, maintenance and provisioning + +## 7.1 OAM applications + +[ITU-T G.709] specifies bandwidth allocated within the OPUk, ODUk, OTUk, OCh, OMSn and OTSn characteristic and adapted information for various control and maintenance functions. Seven types of overhead for OAM are identified: OPUk overhead, ODUk overhead, OTUk overhead, OCh overhead, OMS overhead, OTS overhead and COMMS overhead. [ITU-T G.798] specifies the processing of this overhead. + +### 7.1.1 OPU, ODU, OTU and OCh OAM application + +The functions of the OPU, ODU, OTU and OCh overhead include pro-active and on-demand fault management, performance monitoring, protection switching, embedded communications channels, and ODU maintenance and operation functions. + +The OPU and ODU overhead is generated and terminated at the point where the payload is assembled or disassembled. It is used for end-to-end monitoring of the payload and may transit several switching systems. Some of the OPU and the ODU overhead is completely payload independent, while other parts of the OPU overhead are used in specific ways according to the type of payload. The ODU overhead may be monitored at any point within an ODU network to confirm network operation. + +NOTE – ODU AIS/OCI/LCK and OCh FDI maintenance signals are generated at intermediate points along the ODU connection. + +Additional levels of ODU overhead may also be generated and terminated at administrative domain boundaries and at protected domain boundaries to provide those domains with dedicated ODU monitoring capabilities. These are referred to as tandem connections. Six layers of tandem connections are possible per [ITU-T G.709]. + +If the ODU is carried over a wavelength or over an OTM-0, OTU overhead will be deployed to monitor the ODU link connection supported by the OCh trail. The OCh trail supports maintenance signals for alarm suppression and open connection indications, but no further overhead to support fault management, performance monitoring or protection switching. + +### 7.1.2 OMS, OTS, OPS, OPSM and COMMS OAM application + +The functions of the OMS, OTS, and COMMS overhead include pro-active fault management and optical section maintenance and operation functions for a single owner of an optical section. + +The OPS and OPSM do not support any overhead; monitoring of the OPS and OPSM is delegated to monitoring of the individual OTU or OTUs carried by it. + +The optical section overhead is subdivided into optical amplifier section overhead (OTS OH) and optical multiplex section overhead (OMS OH). The OMS OH is accessible only at terminal equipment, whereas the OTS OH is accessible at both terminal equipment and optical amplifiers. + +The OMS overhead is generated and terminated at the point where the OCh signals are multiplexed or demultiplexed. It is used for end-to-end monitoring of the OCh/ODU aggregate. + +NOTE – OMS FDI maintenance signals are generated at intermediate points along the OMS connection. + +The OTS, OMS, and COMMS overhead is carried out of band in the optical supervisory channel (OSC). + +### 7.1.3 Maintenance signals + +The maintenance signals defined in [ITU-T G.709] provide network connection status information in the form of payload missing indication (PMI), backward error and defect indication (BEI, BDI), open connection indication (OCI), and link and tandem connection status information in the form of locked indication (LCK) and alarm indication signal (forward defect indication (FDI) and alarm indication signal (AIS)). Figures 7-1 and 7-2 illustrate the layer-to-layer and peer-to-peer maintenance interaction provided by OTN OAM. At the generation points where multiple arcs are shown, the arcs pointing to the right indicate signals that are transmitted out of the type of equipment listed to the right of the diagram; the arcs that point in a downward direction to other generators show the propagation of signals between layers (e.g., at the open circle where OMS FDI-P originates, there are two arcs, one that goes to the right, indicating that this signal is transmitted out of an optical amplifier, and one that goes downward, indicating the propagation to the next layer for other equipment types). + +NOTE – These figures provide a consolidated view of the maintenance signalling behaviours that are specified by the atomic functions in [ITU-T G.798]. In the event of a conflict between these figures and the atomic functions in [ITU-T G.798], the description in the atomic functions takes precedence. + +![Figure 7-1 – OTN maintenance signal interaction (Part I). A complex diagram showing the flow of maintenance signals between various OTN layers (OTS, OMS, OCh, OTU, HO ODU, LO ODU, Client) and external entities (Optical amplifier, OCh switching equipment). It uses open circles for 'Generation' and solid circles for 'Detection'.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram illustrates the interaction of maintenance signals across different layers of an Optical Transport Network (OTN). The layers are organized into columns: UPSTREAM (OTS/OMS/OPMS, OMS, OCh), and DOWNSTREAM (OTU, HO ODU, LO ODU, Client). The diagram shows how signals like LOS, LOF, LOL, BDI, TIM, PMI, and AIS are generated and detected at various points within these layers. + +**Legend:** + +- Generation +- Detection + +**Signal Interactions:** + +- OTS/OMS/OPMS Layer:** + - OPSM OTL LOS[]: Detection at OTS/OMS/OPMS, Generation at OMS. + - OPSM OTL LOFLANE[]: Detection at OTS/OMS/OPMS, Generation at OMS. + - OPSM LOL: Detection at OTS/OMS/OPMS. + - OPS LOS-P: Detection at OTS/OMS/OPMS, Generation at OMS. + - OTS BDI-O: Detection at OTS/OMS/OPMS, Generation at OMS. + - OTS LOS-O: Detection at OTS/OMS/OPMS, Generation at OMS. + - OTS TIM: Detection at OTS/OMS/OPMS. + - OTS PMI: Detection at OTS/OMS/OPMS. + - OTS LOS-P: Detection at OTS/OMS/OPMS, Generation at OMS. + - OTS BDI-P: Detection at OTS/OMS/OPMS, Generation at OMS. + - No OMS signal: Detection at OTS/OMS/OPMS, Generation at OMS. +- OMS Layer:** + - OMS BDI-O: Detection at OMS, Generation at OTS/OMS/OPMS. + - OMS FDI-O: Generation at OMS, Detection at OTU. + - OMS PMI: Detection at OMS. + - OMS FDI-P: Generation at OMS, Detection at OTU. + - OMS LOS-P: Detection at OMS. + - OMS BDI-P: Detection at OMS, Generation at OTS/OMS/OPMS. + - No OCh signals: Detection at OMS, Generation at OTS/OMS/OPMS. +- OCh Layer:** + - OCh matrix output port not connected: Detection at OCh, Generation at OTU. + - OCh FDI-O: Detection at OCh. + - OCh FDI-P: Detection at OCh. + - OCh OCI: Detection at OCh. + - OCh LOS-P: Detection at OCh. +- OTU Layer:** + - OTU AIS: Detection at OTU. + - OTU LOF: Detection at OTU. + - OTU LOM: Detection at OTU. + +**External Entities:** + +- Optical amplifier:** Receives OMS FDI-O and OMS FDI-P signals. +- OCh switching equipment:** Receives OCh FDI-P and OMS PMI signals. + +**References:** + +- To figure 7-2 + +Figure 7-1 – OTN maintenance signal interaction (Part I). A complex diagram showing the flow of maintenance signals between various OTN layers (OTS, OMS, OCh, OTU, HO ODU, LO ODU, Client) and external entities (Optical amplifier, OCh switching equipment). It uses open circles for 'Generation' and solid circles for 'Detection'. + +Figure 7-1 – OTN maintenance signal interaction (Part I) + +![Figure 7-2 – OTN maintenance signal interaction (Part II). A detailed diagram showing the flow of maintenance signals between Upstream and Downstream equipment across OTS/OMS/OPMS, OMS, OCh, OTU, HO ODU, LO ODU, and Client layers. It includes signal types like OTU TIM, OTU DEG, OTU BDI, OTU bit errors, OTU BEI, OTU IAE, OTU BIAE, ODU frame discontinuity, HO ODU matrix output port not connected, Admin state = LOCKED, HO ODU LCK, HO ODU AIS, HO ODU OCI, HO ODU TIM, HO ODU DEG, HO ODU BDI, HO ODU bit errors, HO ODU BEI, HO ODU PLM, LO ODU MSIM, LO ODU LOFLM, LO ODU matrix output port not connected, LO ODU LCK, LO ODU AIS, LO ODU OCI, LO ODU TIM, LO ODU DEG, LO ODU BDI, LO ODU bit errors, LO ODU BEI, LO ODU PLM, and LO ODU CSF. Equipment blocks include 3R function or HO/LO ODU switching equipment, LO ODU switching equipment, and LO ODU terminating equipment. A legend at the bottom indicates that open circles represent 'Generation' and solid circles represent 'Detection'.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Figure 7-2 – OTN maintenance signal interaction (Part II). A detailed diagram showing the flow of maintenance signals between Upstream and Downstream equipment across OTS/OMS/OPMS, OMS, OCh, OTU, HO ODU, LO ODU, and Client layers. It includes signal types like OTU TIM, OTU DEG, OTU BDI, OTU bit errors, OTU BEI, OTU IAE, OTU BIAE, ODU frame discontinuity, HO ODU matrix output port not connected, Admin state = LOCKED, HO ODU LCK, HO ODU AIS, HO ODU OCI, HO ODU TIM, HO ODU DEG, HO ODU BDI, HO ODU bit errors, HO ODU BEI, HO ODU PLM, LO ODU MSIM, LO ODU LOFLM, LO ODU matrix output port not connected, LO ODU LCK, LO ODU AIS, LO ODU OCI, LO ODU TIM, LO ODU DEG, LO ODU BDI, LO ODU bit errors, LO ODU BEI, LO ODU PLM, and LO ODU CSF. Equipment blocks include 3R function or HO/LO ODU switching equipment, LO ODU switching equipment, and LO ODU terminating equipment. A legend at the bottom indicates that open circles represent 'Generation' and solid circles represent 'Detection'. + +**Figure 7-2 – OTN maintenance signal interaction (Part II)** + +Figure 7-3 below provides an example of the ITU-T G.798 atomic functions in an OTN NE two stages of ODU multiplexing, followed by the OTUk and OCh adaptation/termination functions. Figure 7-4 provides an example with one stage of ODU multiplexing that includes tandem connection monitoring functions. + +Identified beside each of the atomic functions are the maintenance signals detected and generated at those points. Where the generation of more than one maintenance signal is possible, numbers indicate their relative priority (e.g., Generate ODUk LCK (1), AIS (2) means that ODUk LCK generation overrides ODUk AIS generation). + +![Diagram illustrating maintenance signal detection/generation points with two stages of ODU multiplexing. The diagram shows the flow of signals through various ODU and OTU functions, with maintenance signals being inserted or generated at specific points. The layers shown are ODUi, ODuj, ODUkP, ODUk, OTUk, OCh/OTUk, and OCh, leading down to the OMS or OPS layer. Maintenance signals include OCI, AIS, LCK, BDI, BEI, and BIAE. Detection points are indicated by arrows pointing up to the signal flow, while insertion/generation points are indicated by arrows pointing down or into the signal flow.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the flow of signals through various ODU and OTU functions, showing maintenance signal detection and generation points. The layers shown are ODUi, ODuj, ODUkP, ODUk, OTUk, OCh/OTUk, and OCh, leading down to the OMS or OPS layer. + +Key maintenance signal points include: + +- ODUi layer:** Insert ODUi OCI, AIS; Generate ODUi LCK. Detection: Detect OPUj PLM, CSF; Generate ODUi LCK (1), AIS (2). +- ODuj layer:** Insert ODuj BDI, BEI; Insert ODuj OCI, AIS; Generate ODuj LCK. Detection: Detect ODuj AIS, LCK, OCI, TIM, DEG, BDI. +- ODUkP layer:** Insert ODUkP BDI, BEI; Insert ODUkP OCI, AIS; Generate ODUkP LCK. Detection: Detect ODUkP AIS, LCK, OCI, TIM, DEG, BDI. +- OTUk layer:** Insert OTU BDI, BEI, BIAE; Insert OTUk OCI, AIS; Generate OTUk LCK. Detection: Detect OTU TIM, DEG, BDI, IAE, BIAE. +- OCh/OTUk layer:** Detection: Detect LOF, LOMF. +- OCh layer:** Detection: Detect LOS. + +NOTE 1 – From the OTUk/ODUk\_A or ODUkP/ODUj\_A functions the signal may either be connected to the ODU\_C function or to the ODUkP\_TT or ODujP\_TT function, respectively. In the case that the signal connects to the ODU\_C function, it is also possible to have an ODUkP\_TT\_Sk or ODujP\_TT\_Sk, respectively, for the purpose of non-intrusive monitoring. + +G.798.1(13)\_F7-3 + +Diagram illustrating maintenance signal detection/generation points with two stages of ODU multiplexing. The diagram shows the flow of signals through various ODU and OTU functions, with maintenance signals being inserted or generated at specific points. The layers shown are ODUi, ODuj, ODUkP, ODUk, OTUk, OCh/OTUk, and OCh, leading down to the OMS or OPS layer. Maintenance signals include OCI, AIS, LCK, BDI, BEI, and BIAE. Detection points are indicated by arrows pointing up to the signal flow, while insertion/generation points are indicated by arrows pointing down or into the signal flow. + +**Figure 7-3 – Example of maintenance signal detection/generation points with two stages of ODU multiplexing** + +![Diagram illustrating maintenance signal detection and generation points in an optical transport network (OTN) hierarchy. The diagram shows the flow of signals through various sublayers: ODUj, ODUkP, ODUkT, ODUk, OTUk, OCh, and finally the OMS or OPS layer. Maintenance signals like OCI, LCK, BDI, BEI, and BIAE are generated and detected at various points. Detection points include OPUk PLM, CSF, ODUj LCK (1), AIS (2), ODUkP AIS, LCK, OCI, TIM, DEG, BDI, ODUkT BDI, BEI, BIAE, ODUk LCK, ODUk LCK (1), AIS (2), OTUk TIM, DEG, BDI, IAE, BIAE, LOF, LOMF, and LOS. The diagram also includes notes about optional tandem connection (ODUkT) sublayers and network element configuration.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +The diagram illustrates the maintenance signal detection and generation points in an optical transport network (OTN) hierarchy. The hierarchy starts with the ODU (Optical Data Unit) at the top, which generates OCI, LCK, BDI, BEI, and BIAE signals. These signals are passed through various sublayers: ODUj, ODUkP, ODUkT, ODUk, OTUk, OCh, and finally the OMS or OPS layer. Maintenance signals are generated and detected at various points in the hierarchy. Detection points include OPUk PLM, CSF, ODUj LCK (1), AIS (2), ODUkP AIS, LCK, OCI, TIM, DEG, BDI, ODUkT BDI, BEI, BIAE, ODUk LCK, ODUk LCK (1), AIS (2), OTUk TIM, DEG, BDI, IAE, BIAE, LOF, LOMF, and LOS. The diagram also includes notes about optional tandem connection (ODUkT) sublayers and network element configuration. + +Diagram illustrating maintenance signal detection and generation points in an optical transport network (OTN) hierarchy. The diagram shows the flow of signals through various sublayers: ODUj, ODUkP, ODUkT, ODUk, OTUk, OCh, and finally the OMS or OPS layer. Maintenance signals like OCI, LCK, BDI, BEI, and BIAE are generated and detected at various points. Detection points include OPUk PLM, CSF, ODUj LCK (1), AIS (2), ODUkP AIS, LCK, OCI, TIM, DEG, BDI, ODUkT BDI, BEI, BIAE, ODUk LCK, ODUk LCK (1), AIS (2), OTUk TIM, DEG, BDI, IAE, BIAE, LOF, LOMF, and LOS. The diagram also includes notes about optional tandem connection (ODUkT) sublayers and network element configuration. + +NOTE 1 – From the OTUk/ODUk\_A or ODUkT/ODUk\_A functions only one of the paths shown is followed, based on network element configuration. + +NOTE 2 – The tandem connection (ODUkT) sublayer that is monitoring the incoming signal is optional. It may be present zero to six times. + +NOTE 3 – The tandem connection (ODUkT) sublayer that is monitoring the signal from the ODU\_C function is optional. It may be present zero to six times. + +**Figure 7-4 – Example of maintenance signal detection/generation points with tandem connection monitoring** + +Within the ODU layer, there are interactions between the AIS, OCI, and LCK maintenance signals that occur across multiple atomic functions. The figures below illustrate several examples of these interactions. + +Figure 7-5 shows an ODU that is not cross-connected and is also administratively locked. In this case the OCI signal that is generated by the ODU\_C function for the unconnected ODU is overwritten by the LCK signal generated in the srv/ODUk\_A\_So function. + +![Figure 7-5: ODU layer interaction between OCI and LCK maintenance signals. The diagram shows an ODU_C layer at the top connected to two OTUk/ODUk_A_So and OTUk/ODUk_A_Sk functions. OCI and MI_AdminState are inputs to the OTUk/ODUk_A_So function. LCK is an input to the OTUk/ODUk_A_So function. The OTUk/ODUk_A_So function outputs to an OTUk_TT_So function, which then outputs to the bottom. The OTUk/ODUk_A_Sk function outputs to an OTUk_TT_Sk function, which then outputs to the bottom. The OTUk/ODUk_A_Sk function also receives an input from the OTUk_TT_Sk function. The diagram is labeled G.798.1(13)_F7-5.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 7-5: ODU layer interaction between OCI and LCK maintenance signals. The diagram shows an ODU\_C layer at the top connected to two OTUk/ODUk\_A\_So and OTUk/ODUk\_A\_Sk functions. OCI and MI\_AdminState are inputs to the OTUk/ODUk\_A\_So function. LCK is an input to the OTUk/ODUk\_A\_So function. The OTUk/ODUk\_A\_So function outputs to an OTUk\_TT\_So function, which then outputs to the bottom. The OTUk/ODUk\_A\_Sk function outputs to an OTUk\_TT\_Sk function, which then outputs to the bottom. The OTUk/ODUk\_A\_Sk function also receives an input from the OTUk\_TT\_Sk function. The diagram is labeled G.798.1(13)\_F7-5. + +**Figure 7-5 – ODU layer interaction between OCI and LCK maintenance signals** + +Figure 7-6 shows a cross-connection between two ODUs. One port has a failure, and as a result the OTUk/ODUk\_A\_Sk function is inserting AIS. The other port is administratively locked. In this case the AIS signal is overwritten by the LCK signal generated in the OTUk/ODUk\_A\_So function. + +![Figure 7-6: ODU layer interaction between AIS and LCK maintenance signals. The diagram shows an ODU_C layer at the top connected to two sets of OTUk/ODUk_A_So and OTUk/ODUk_A_Sk functions. The left set has an OTUk/ODUk_A_So function that outputs to an OTUk_TT_So function, which then outputs to the bottom. The OTUk/ODUk_A_Sk function in the left set receives an input from an OTUk_TT_Sk function, which is marked with a red X. The OTUk/ODUk_A_Sk function in the left set outputs an AIS signal to the ODU_C layer. The OTUk/ODUk_A_So function in the right set receives an MI_AdminState input and outputs an LCK signal to the OTUk_TT_So function, which then outputs to the bottom. The OTUk/ODUk_A_Sk function in the right set outputs to an OTUk_TT_Sk function, which then outputs to the bottom. The diagram is labeled G.798.1(13)_F7-6.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 7-6: ODU layer interaction between AIS and LCK maintenance signals. The diagram shows an ODU\_C layer at the top connected to two sets of OTUk/ODUk\_A\_So and OTUk/ODUk\_A\_Sk functions. The left set has an OTUk/ODUk\_A\_So function that outputs to an OTUk\_TT\_So function, which then outputs to the bottom. The OTUk/ODUk\_A\_Sk function in the left set receives an input from an OTUk\_TT\_Sk function, which is marked with a red X. The OTUk/ODUk\_A\_Sk function in the left set outputs an AIS signal to the ODU\_C layer. The OTUk/ODUk\_A\_So function in the right set receives an MI\_AdminState input and outputs an LCK signal to the OTUk\_TT\_So function, which then outputs to the bottom. The OTUk/ODUk\_A\_Sk function in the right set outputs to an OTUk\_TT\_Sk function, which then outputs to the bottom. The diagram is labeled G.798.1(13)\_F7-6. + +**Figure 7-6 – ODU layer interaction between AIS and LCK maintenance signals** + +Figures 7-7 and 7-8 show examples that include the termination of a tandem connection. In this example, the incoming signal has either the OCI or LCK maintenance signal. This is detected by the OTUk\_TT\_Sk function, and the AI\_TSF signal is asserted as a result. The OTUk/ODUk\_A\_Sk function inserts AIS in response to AI\_TSF, so the incoming OCI/LCK is replaced with AIS. At a network level, this means that the OCI/LCK is confined to the tandem connection in which it occurs; any tandem connections that have larger scope, and the end-to-end ODUkP, will see AIS (i.e., a server layer failure). + +![Diagram of OCI/LCK/AIS interaction with tandem connection endpoints (1).](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +This diagram illustrates the maintenance signal interactions at tandem connection endpoints. At the top, an oval labeled ODU\_C is connected to two trapezoidal blocks: ODUkT/ODUk\_A\_So (left) and ODUkT/ODUk\_A\_Sk (right). Downward arrows from ODU\_C point to both blocks. Upward arrows from these blocks point to two triangular blocks: ODUkT\_TT\_So (left) and ODUkT\_TT\_Sk (right). A horizontal arrow labeled RI\_BDI points from ODUkT\_TT\_Sk to ODUkT\_TT\_So. Below the triangles are two more trapezoidal blocks: OTUk/ODUk\_A\_So (left) and OTUk/ODUk\_A\_Sk (right). Downward arrows from the triangles point to these blocks. Upward arrows from these blocks point to two more triangular blocks: OTUk\_TT\_So (left) and OTUk\_TT\_Sk (right). A horizontal arrow labeled RI\_BDI points from OTUk\_TT\_Sk to OTUk\_TT\_So. External signals include AIS pointing to ODUkT/ODUk\_A\_Sk, AI\_TSF pointing to ODUkT/ODUk\_A\_Sk, BDI pointing to ODUkT\_TT\_So, dLCK or dOCI pointing to ODUkT\_TT\_Sk, and LCK or OCI (in ODU) pointing to OTUk\_TT\_Sk. The diagram is labeled G.798.1(13)\_F7-7. + +Diagram of OCI/LCK/AIS interaction with tandem connection endpoints (1). + +Figure 7-7 – OCI/LCK/AIS interaction with tandem connection endpoints (1) + +![Diagram of OCI/LCK/AIS interaction with tandem connection endpoints (2).](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +This diagram shows another configuration of maintenance signal interactions. At the top, an oval labeled ODU\_C is connected to two trapezoidal blocks: OTUk/ODUk\_A\_So (left) and OTUk/ODUk\_A\_Sk (right). Downward arrows from ODU\_C point to both blocks. Upward arrows from these blocks point to two triangular blocks: OTUk\_TT\_So (left) and OTUk\_TT\_Sk (right). Below these are two more trapezoidal blocks: ODUkT/ODUk\_A\_Sk (left) and ODUkT/ODUk\_A\_So (right). Downward arrows from the triangles point to these blocks. Upward arrows from these blocks point to two more triangular blocks: ODUkT\_TT\_Sk (left) and ODUkT\_TT\_So (right). External signals include LCK or OCI (in ODU) pointing to ODU\_C, dLCK or dOCI pointing to ODUkT\_TT\_Sk, AI\_TSF pointing to ODUkT/ODUk\_A\_Sk, AIS pointing to ODUkT/ODUk\_A\_Sk, and LCK or OCI (in ODU) pointing to OTUk\_TT\_Sk. The diagram is labeled G.798.1(13)\_F7-8. + +Diagram of OCI/LCK/AIS interaction with tandem connection endpoints (2). + +Figure 7-8 – OCI/LCK/AIS interaction with tandem connection endpoints (2) + +When multiple tandem connection sublayers are in use, there are maintenance signal interactions between tandem connections that are concatenated in the same sublayer and between tandem connections that are in different sublayers. The next several figures illustrate two examples of these interactions. Figure 7-9 shows an example network with two layers of tandem connections, and indicates the status information for the PM, TCM1, and TCM2 overhead that is seen on each link. + +The interpretation of the status values is defined by Tables 15-3 and 15-5 of [ITU-T G.709]; the values used in these examples are summarized in Table 7-1 for convenience. + +**Table 7-1 – ODUk PM and TCM status interpretation** + +| PM or TCM bits 6 7 8 | PM Status | TCM Status | +|----------------------|---------------------------------------------|--------------------------| +| 0 0 0 | (value reserved for future standardization) | TCM level not in use | +| 0 0 1 | Normal path signal | TCM level in use, no IAE | +| 1 0 1 | LCK | LCK | +| 1 1 0 | OCI | OCI | +| 1 1 1 | AIS | AIS | + +![Figure 7-9: Example network with two tandem connections sublayers in use. The diagram shows a sequence of nodes A through G. Above the nodes, three horizontal lines represent different sublayers: ODUkP-PM (pink triangles at A and G), ODUkT-TCM1 (green triangles at A and F), and ODUkT-TCM2 (yellow triangles at B, C, D, E, and F). Below the nodes, a row of colored boxes shows the PM/TCM Status bits for each node: A (001 001 000), B (001 001 001), C (001 001 001), D (001 001 001), E (001 001 001), F (001 000 000), and G (001 000 000).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 7-9: Example network with two tandem connections sublayers in use. The diagram shows a sequence of nodes A through G. Above the nodes, three horizontal lines represent different sublayers: ODUkP-PM (pink triangles at A and G), ODUkT-TCM1 (green triangles at A and F), and ODUkT-TCM2 (yellow triangles at B, C, D, E, and F). Below the nodes, a row of colored boxes shows the PM/TCM Status bits for each node: A (001 001 000), B (001 001 001), C (001 001 001), D (001 001 001), E (001 001 001), F (001 000 000), and G (001 000 000). + +**Figure 7-9 – Example network with two tandem connections sublayers in use** + +Figure 7-10 considers the case where there is a link failure within one of the level 2 tandem connections, and shows how the overhead for the concatenated connection at level 2 replaces the AIS maintenance signal with a 'normal' status. In this scenario, Node C detects the failure and inserts AIS in the PM and all TCM overheads. At Node D, the tandem connection at level 2 is terminated and new level 2 tandem connection is started. As such, Node D extracts the TCM2 overhead it receives from Node C, and initiates new TCM2 overhead toward Node E. Figure 7-11 shows the atomic functions for Node D. + +![Figure 7-10: Maintenance signalling due to link failure with two tandem connections. The diagram shows the same network as Figure 7-9, but with a red 'X' indicating a link failure between nodes B and C. The status bits below the nodes are: A (001 001 000), B (001 001 001), C (111 111 111), D (111 111 001), E (111 111 001), F (111 000 000), and G (111 000 000). The ODUkP-PM and ODUkT-TCM1 sublayers remain the same as in Figure 7-9. The ODUkT-TCM2 sublayer is now shown with yellow triangles at nodes C, D, and E, indicating a new tandem connection segment has been established between C and E, bypassing the failed link.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Figure 7-10: Maintenance signalling due to link failure with two tandem connections. The diagram shows the same network as Figure 7-9, but with a red 'X' indicating a link failure between nodes B and C. The status bits below the nodes are: A (001 001 000), B (001 001 001), C (111 111 111), D (111 111 001), E (111 111 001), F (111 000 000), and G (111 000 000). The ODUkP-PM and ODUkT-TCM1 sublayers remain the same as in Figure 7-9. The ODUkT-TCM2 sublayer is now shown with yellow triangles at nodes C, D, and E, indicating a new tandem connection segment has been established between C and E, bypassing the failed link. + +**Figure 7-10 – Maintenance signalling due to link failure with two tandem connections** + +![Figure 7-11: Atomic function view of Node D. The diagram shows a central oval labeled ODU_C connected to four trapezoidal blocks: ODUkT/ODUk_A_So, ODUkT/ODUk_A_Sk, ODUkT/ODUk_TT_So, and ODUkT/ODUk_TT_Sk. These are further connected to OTUk/ODUk_A_So, OTUk/ODUk_A_Sk, OTUk_TT_So, and OTUk_TT_Sk blocks. Arrows indicate signal flow, with labels like RI_BDI, ODU AIS, To Node C, and To Node E. Bit sequences like 111 111 000, 111 111 001, and 111 111 111 are shown in colored boxes.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Figure 7-11: Atomic function view of Node D. The diagram shows a central oval labeled ODU\_C connected to four trapezoidal blocks: ODUkT/ODUk\_A\_So, ODUkT/ODUk\_A\_Sk, ODUkT/ODUk\_TT\_So, and ODUkT/ODUk\_TT\_Sk. These are further connected to OTUk/ODUk\_A\_So, OTUk/ODUk\_A\_Sk, OTUk\_TT\_So, and OTUk\_TT\_Sk blocks. Arrows indicate signal flow, with labels like RI\_BDI, ODU AIS, To Node C, and To Node E. Bit sequences like 111 111 000, 111 111 001, and 111 111 111 are shown in colored boxes. + +Figure 7-11 – Atomic function view of Node D in Figure 7-10 + +Figure 7-12 shows a network level example related to the behaviour described in Figures 7-7 and 7-8. In this example the cross-connection in Node B has been disconnected, causing Node B to insert the OCI maintenance signal in the PM and all TCM overheads. As there are no tandem connections that terminate in Node C, the OCI signal passes through unmodified. At Node D, the TCM2 overhead is extracted and processed, and as a result AIS is inserted in the PM and TCM1 overheads. The TCM2 overhead is then overwritten when the concatenated tandem connections starts, as in the previous example. + +![Figure 7-12: Maintenance signalling due to open connection with two tandem connections. The diagram shows a sequence of nodes A through G. A 'Missing cross-connection' is indicated at Node B. Below the nodes, three horizontal lines represent ODUkP-PM, ODUkT-TCM1, and ODUkT-TCM2 paths. At the bottom, a table shows PM/TCM Status bits for each node.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +| | | | | | | | +|--------------------|-------------|-------------|-------------|-------------|-------------|-------------| +| PM/TCM Status bits | 001 001 000 | 110 110 110 | 110 110 110 | 111 111 001 | 111 111 001 | 111 000 000 | +|--------------------|-------------|-------------|-------------|-------------|-------------|-------------| + +Figure 7-12: Maintenance signalling due to open connection with two tandem connections. The diagram shows a sequence of nodes A through G. A 'Missing cross-connection' is indicated at Node B. Below the nodes, three horizontal lines represent ODUkP-PM, ODUkT-TCM1, and ODUkT-TCM2 paths. At the bottom, a table shows PM/TCM Status bits for each node. + +Figure 7-12 – Maintenance signalling due to open connection with two tandem connections + +### 7.1.4 Fault and performance reports + +Details of the fault and performance reporting functions are provided in [ITU-T G.798], [ITU-T G.874], and [ITU-T G.7710]. + +The fault management functions include fault and degradation detection, correlation, persistency filtering and reporting. Only the fault report representing the root cause is presented to network management. Fault reporting at client layers or sublayers above the (sub)layer with the fault is suppressed by forwarding detected signal fail conditions. Within one network element this is provided via the chain of trail signal fail (TSF) and server signal fail (SSF) signals. Between network elements, this is provided via the transmission of Forward Defect Indicator (FDI) and alarm indication signal (AIS) maintenance signals (see Figures 7-1 and 7-2). + +Service management requires status information on an individual service basis. For the OTN, this is on an individual LO ODU basis. Suppression – for fault management – of fault reporting at client layers or sublayers due to a fault on a server layer, prevents by default the pro-active reporting of the interruption of the service to the service manager. To support service management, an additional pro-active SSF report is provided. This is configurable per service instance. Service management may instead have the ability to reactively request the status of the service connection at its endpoints when the customer makes inquiries. + +A fault in a connection itself (e.g., a configuration fault) may occur. Reporting of such faults is not suppressed. In addition, degradation (e.g., bit errors) in a connection itself may occur. Such degradation can be detected; its sensitivity and detection period is configurable with default values, causing detection before entering unavailable time. This allows protection switching to switch to the standby subnetwork connection and thus prevent the service from becoming unavailable. + +The performance monitoring functions include errored second, severely errored second, unavailable time and background block error reporting. There are maintenance and service performance monitoring functions, which are configurable per connection. Each second with an interruption or bit errors is counted in 15-minute and 24-hour intervals. For details refer to [ITU-T G.7710]. Counts of errored seconds represent the number of seconds in the interval in which there were bit errors detected, while there was no unavailable time and no signal fail condition. Counts of severely errored seconds represent the number of seconds in the interval in which there was a signal failure condition or there were more than a configured number of bit errors detected, while there was no unavailable time. Unavailable time starts at the first second of ten successive severely errored seconds, and ends at the first second of ten successive not severely errored seconds. Counts of background block errors represent the number of errored blocks detected outside severely errored seconds and unavailable seconds. + +The ES, SES, BBE counters are equipped with configurable threshold crossing report capability, which pro-actively reports the presence of an excessive condition. + +Performance reporting is independent of fault reporting, i.e., not impacted by fault report suppression. + +## 7.2 TMN access + +OTN equipment should provide interfaces for messages to or from the TMN via the COMMS, GCC, or a Q interface. Messages arriving at the interface not addressed to the local equipment should be relayed to the appropriate Q, GCC, or COMMS interface. The TMN can thus be provided with a direct logical link to any OTN equipment via a single Q interface and the interconnecting GCC or COMMS interfaces. OTN equipment may be located behind a third party network; for such cases the OTN equipment should provide interfaces for messages to or from the TMN via either a GCC or a Q interface or both. + +### 7.2.1 Q interface + +When access to the TMN is provided by a COMMS, GCC or Q-interface, the interface will conform to [ITU-T G.874]. + +### 7.2.2 Embedded communications channels (ECC) + +Embedded communications channels may be used in support of management communications (MCC) and/or signalling communications (SCC). The use of the ECCs is dependent on the network operator's maintenance strategy and the specific situation. It may not always be required as it is possible to carry out the required functions by other means. + +There are two types of ECCs: + +- i) the COMMS located in the OTN non-associated overhead accessible at NEs within the network operator's domain, but not accessible at remote NEs; +- ii) the GCC located in the OTU overhead (GCC0) and/or the GCCs located in the ODU overhead (GCC1, GCC2), which are accessible within the network operator's domain and also may be accessible at remote NEs. + +These channels are message based and provide communications between network elements. They can be used to support communications between sites and the TMN. Further information is given in [ITU-T G.874] and [ITU-T G.7712]. + +### 7.2.3 Equipment management function (EMF) + +This converts performance data and implementation-specific hardware alarms into object-oriented messages for transmission on the MCC(s) and/or a Q-interface. It also converts object-oriented messages related to other management functions for passing across the MP reference points. + +### 7.2.4 Message communication function (MCF) + +This function receives and buffers messages from the MCC(s), Q- and F-interfaces and EMF. Messages not addressed to the local site are relayed to one or more outgoing MCC(s) and Q-interfaces in accordance with local routing procedures and/or Q-interface(s). The function provides layer 1 (and layer 2 in some cases) translation between a MCC and a Q-interface or another MCC interface. + +## 7.3 Timing function + +The OTN does not require any synchronization functionality. The OTN – specifically the mapping/demapping/desynchronizing and multiplexing/demultiplexing processes and justification granularity information – is designed to transport synchronous client signals, like synchronous STM-N and synchronous Ethernet signals. When these signals are bit synchronously mapped into the ODUk (using BMP), this ODUk will be traceable to the same clock to which the synchronous client signal is traceable (i.e., PRC, SSU, SEC/EEC and under a signal fail condition of the synchronous client the AIS/LF clock). When those signals are asynchronously mapped into the ODUk (using AMP or GMP), this ODUk will be plesiochronous with a frequency/bit rate tolerance of $\pm 20$ ppm. + +Non-synchronous constant bit rate client signals can be mapped bit synchronously (using BMP) or asynchronously (using AMP, GMP) into the ODUk. In the former case, the frequency/bit rate tolerance of the ODUk will be the frequency/bit rate tolerance of the client signal, with a maximum of $\pm 45$ ppm for $k=0, 1, 2, 3, 4$ and $\pm 100$ ppm for $k=2e, flex$ . In the latter case, the frequency/bit rate tolerance of the ODUk will be $\pm 20$ ppm. + +Multiplexing of low order ODUs into a high order ODUk uses an asynchronous mapping (either AMP or GMP). The frequency/bit rate tolerance of the high order ODUk signal is $\pm 20$ ppm. + +Variable rate packet client signals are mapped into the ODUk using the generic framing procedure (GFP-F). The frequency/bit rate tolerance of the ODUk is $\pm 20$ ppm for $k=0, 1, 2, 3, 4$ and $\pm 100$ ppm for $k=\text{flex}$ . + +NOTE – It is possible to use the clock from an EEC or SEC function to generate the ODUk carrying clients mapped with AMP, GMP, or GFP-F or a multiplex of low order ODUs. Such ODUk is then traceable to an EEC, SSU or PRC. At this point in time, such ODUk does not provide support for a Synchronization Status Message (ODUk SSM), and consequently cannot be used as a synchronous-ODUk, i.e., as a synchronous STM-N or synchronous Ethernet replacement signal. + +ODUk signals are mapped frame-synchronously into OTUk, thus the frequency/bit rate tolerance of the OTUk signals depends on the frequency/bit rate tolerance of the ODUk signal being carried. + +## **7.4 Control plane access** + +Control plane support for OTN is described in [ITU-T G.8080]. + +## **7.5 Connection management** + +OTN connection management is described in [ITU-T G.874]. + +# **8 Protection switching** + +## **8.1 Linear protection** + +ODU subnetwork connection protection is described in clause 14.1.1.1 of [ITU-T G.798] and [ITU-T G.873.1]. + +OCh subnetwork connection protection is described in clause 12.1.1.1 of [ITU-T G.798]. + +OMS trail protection is described in clause 10.4.1 of [ITU-T G.798]. + +## **8.2 Shared ring protection** + +ODU shared ring protection is under development. + +## **8.3 Shared mesh protection** + +ODU shared mesh protection is under development. + +# **9 Interface ports on optical transport network equipment** + +The figures in this section illustrate examples of different types of ports that could be used in OTN equipment. The term 'port' is used here in a logical context and does not imply any partitioning of functions to hardware modules. A hardware module may implement one port, many ports, or a portion of the functions for one or more ports. + +## **9.1 I-NNI** + +Figure 9-1 shows several different examples compound functions for individual NNI wavelengths. In the examples, the functions drawn with dashed lines are not active. + +The Type 1 I-NNI port supports multiplexing of low order ODUj into ODUk and tandem connection monitoring on the low order ODUs to support SNC/S protection. + +The Type 2 I-NNI port is used when the low order ODU is mapped directly onto the wavelength. + +The Type 3 I-NNI port supports two levels of multiplexing. + +![Diagram showing three types of I-NNI port compound functions (Type 1, Type 2, Type 3) with layers of ODU and OTU functions.](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +The diagram illustrates three types of I-NNI port compound functions, labeled I-NNI Type 1, I-NNI Type 2, and I-NNI Type 3. Each type shows a vertical stack of protocol layers represented by triangles. + +- I-NNI Type 1:** From top to bottom, the layers are: + - ODUiT (shaded triangle) + - ODUiT/ODUi (shaded triangle) + - ODUiT/ODUi (shaded triangle) + - ODUiT (shaded triangle) + - ODUjP/ODUi (shaded triangle) + - ODUjP (shaded triangle) + - ODUjT (shaded triangle) + - ODUjT/ODUj (shaded triangle) + - ODUjT (white triangle) + - ODUkP/ODUj (white triangle) + - ODUkP (white triangle) + - ODUkT (shaded triangle) + - ODUkT/ODUk (shaded triangle) + - ODUkT (shaded triangle) + - OTUk/ODUk (white triangle) + - OTUk (white triangle) + - OCh/OTUk (white triangle) + - OCh (white triangle) +- I-NNI Type 2:** From top to bottom, the layers are: + - ODUiT (shaded triangle) + - ODUiT/ODUi (shaded triangle) + - ODUiT/ODUi (shaded triangle) + - ODUiT (shaded triangle) + - ODUjP/ODUi (shaded triangle) + - ODUjP (shaded triangle) + - ODUjT (shaded triangle) + - ODUjT/ODUj (shaded triangle) + - ODUjT (shaded triangle) + - ODUkP/ODUj (shaded triangle) + - ODUkP (shaded triangle) + - ODUkT (shaded triangle) + - ODUkT/ODUk (shaded triangle) + - ODUkT (white triangle) + - OTUk/ODUk (white triangle) + - OTUk (white triangle) + - OCh/OTUk (white triangle) + - OCh (white triangle) +- I-NNI Type 3:** From top to bottom, the layers are: + - ODUiT (shaded triangle) + - ODUiT/ODUi (shaded triangle) + - ODUiT/ODUi (white triangle) + - ODUiT (white triangle) + - ODUjP/ODUi (white triangle) + - ODUjP (white triangle) + - ODUjT (shaded triangle) + - ODUjT/ODUj (shaded triangle) + - ODUjT (white triangle) + - ODUkP/ODUj (white triangle) + - ODUkP (white triangle) + - ODUkT (shaded triangle) + - ODUkT/ODUk (shaded triangle) + - ODUkT (white triangle) + - OTUk/ODUk (white triangle) + - OTUk (white triangle) + - OCh/OTUk (white triangle) + - OCh (white triangle) + +G.798.1(13)\_F9-1 + +Diagram showing three types of I-NNI port compound functions (Type 1, Type 2, Type 3) with layers of ODU and OTU functions. + +**Figure 9-1 – I-NNI port compound function** + +An I-NNI can be single channel or multi-channel. Multi-channel I-NNI ports contain a WDM interface and individual NNI functions for each wavelength. Compound functions for these ports are shown in Figure 9-2. + +![Figure 9-2: WDM and single-channel physical layer compound functions. The diagram shows four inverted triangle structures representing different physical layer configurations. Each triangle is divided into two horizontal sections. The top section represents the higher-order layer (e.g., OMSn/OCh, OPSn/OChr, OPS0/OChr, OPSMnk/OTUk) and the bottom section represents the lower-order layer (e.g., OMSn, OTSn, OPSn, OPS0, OPSMnk). Above each triangle are vertical lines representing input channels, with an ellipsis indicating multiple channels. Below each triangle is a label for the overall function (e.g., OTM-n.m, OTM-nr.m, OTM-0.m, OTM-0.mvn). At the bottom of each triangle, there are colored vertical bars representing the output signal: four colors (red, green, blue, yellow) for OTM-n.m and OTM-nr.m, a single black line for OTM-0.m, and two colors (yellow, blue) for OTM-0.mvn.](69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg) + +Figure 9-2: WDM and single-channel physical layer compound functions. The diagram shows four inverted triangle structures representing different physical layer configurations. Each triangle is divided into two horizontal sections. The top section represents the higher-order layer (e.g., OMSn/OCh, OPSn/OChr, OPS0/OChr, OPSMnk/OTUk) and the bottom section represents the lower-order layer (e.g., OMSn, OTSn, OPSn, OPS0, OPSMnk). Above each triangle are vertical lines representing input channels, with an ellipsis indicating multiple channels. Below each triangle is a label for the overall function (e.g., OTM-n.m, OTM-nr.m, OTM-0.m, OTM-0.mvn). At the bottom of each triangle, there are colored vertical bars representing the output signal: four colors (red, green, blue, yellow) for OTM-n.m and OTM-nr.m, a single black line for OTM-0.m, and two colors (yellow, blue) for OTM-0.mvn. + +**Figure 9-2 – WDM and single-channel physical layer compound functions** + +## 9.2 E-NNI + +E-NNI ports are similar to I-NNI ports, but use only the OPS physical layers rather than OTS and OMS layers. Figure 9-3 shows several examples of E-NNI ports. In the examples, the functions shown in grey are not active. + +The Type 1 E-NNI port supports multiplexing of low order ODUj into ODUk and tandem connection monitoring on the low order ODUs to support SNC/S protection. + +The Type 2 E-NNI port is used when the low order ODU is mapped directly onto the wavelength. + +The Type 3 E-NNI port supports two levels of multiplexing. + +![Diagram showing E-NNI port compound functions for Type 1, Type 2, and Type 3. Each type shows a vertical stack of protocol layers represented by triangles. Type 1 has 8 triangles, Type 2 has 7, and Type 3 has 8. Layers include ODUiT, ODUjP, ODUjT, ODUkP, ODUkT, OTUk, and OCh/OPS+OChr. Some triangles are shaded grey.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +The diagram illustrates the compound functions for three E-NNI port types. Each type is represented by a vertical stack of triangles, each containing specific protocol layer labels. + +- E-NNI Type 1:** + - Top triangle (shaded): ODUiT / ODUiT/ODUi + - Second triangle (shaded): ODUiT/ODUi / ODUiT + - Third triangle (shaded): ODUjP/ODUi / ODUjP + - Fourth triangle: ODUjT / ODUjT/ODUj + - Fifth triangle: ODUjT/ODUj / ODUjT + - Sixth triangle: ODUkP/ODUj / ODUkP + - Seventh triangle (shaded): ODUkT / ODUkT/ODUk + - Eighth triangle: ODUkT/ODUk / ODUkT + - Ninth triangle: OTUk/ODUk / OTUk + - Tenth triangle: OCh/OTUk / OPS+ OChr +- E-NNI Type 2:** + - Top triangle (shaded): ODUiT / ODUiT/ODUi + - Second triangle (shaded): ODUiT/ODUi / ODUiT + - Third triangle (shaded): ODUjP/ODUi / ODUjP + - Fourth triangle (shaded): ODUjT / ODUjT/ODUj + - Fifth triangle (shaded): ODUjT/ODUj / ODUjT + - Sixth triangle (shaded): ODUkP/ODUj / ODUkP + - Seventh triangle: ODUkT / ODUkT/ODUk + - Eighth triangle: ODUkT/ODUk / ODUkT + - Ninth triangle: OTUk/ODUk / OTUk + - Tenth triangle: OCh/OTUk / OPS+ OChr +- E-NNI Type 3:** + - Top triangle: ODUiT / ODUiT/ODUi + - Second triangle: ODUiT/ODUi / ODUiT + - Third triangle: ODUjP/ODUi / ODUjP + - Fourth triangle (shaded): ODUjT / ODUjT/ODUj + - Fifth triangle: ODUjT/ODUj / ODUjT + - Sixth triangle: ODUkP/ODUj / ODUkP + - Seventh triangle (shaded): ODUkT / ODUkT/ODUk + - Eighth triangle: ODUkT/ODUk / ODUkT + - Ninth triangle: OTUk/ODUk / OTUk + - Tenth triangle: OCh/OTUk / OPS+ OChr + +G.798.1(13)\_F9-3 + +Diagram showing E-NNI port compound functions for Type 1, Type 2, and Type 3. Each type shows a vertical stack of protocol layers represented by triangles. Type 1 has 8 triangles, Type 2 has 7, and Type 3 has 8. Layers include ODUiT, ODUjP, ODUjT, ODUkP, ODUkT, OTUk, and OCh/OPS+OChr. Some triangles are shaded grey. + +**Figure 9-3 – E-NNI port compound functions** + +## 9.3 UNI + +Figure 9-4 shows several examples of UNI-N ports. + +- (a) This shows a non-OTN client signal adapted to an ODUk. Path monitoring is used to verify the SLA between the UNI-N ports. The mapping to the ODUk is client-specific. Additional client-specific functions such as non-intrusive monitoring or protection may also be performed. +- (b) This shows the two versions of OTN client UNIs, one for serial interfaces and one for multilane interfaces. +- (c) This shows a UNI-N supporting multiple non-OTN clients that are multiplexed to a high order ODU directly at the UNI. Such a port might be used for the introduction of ODU0 or ODUflex services at the edge of a legacy network, without the need for upgrading all NEs in the network to be ODU0 or ODUflex capable. + +![Figure 9-4 – UNI port compound functions. The diagram shows three types of UNI port structures: (a) CBR client UNI, (b) OTN client UNI, and (c) Multiclient UNI. Each structure is represented by a stack of triangles indicating the hierarchy of functions from the client down to the network interface.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The diagram illustrates three types of UNI port compound functions: + +- (a) CBR client UNI:** A single Client triangle is connected to an ODUkP/Client triangle, which is connected to an ODUkP triangle. This is then connected to an ODUkT/ODUk triangle, which is finally connected to an ODUkT triangle. +- (b) OTN client UNI:** Two separate stacks are shown. The left stack starts with OPS0, followed by OPS0/OChr, OChr, OChr/OTUk, OTUk, OTUk/ODUk, ODUkT, ODUkT/ODUk, and ODUkT. The right stack starts with OPSMnk, followed by OPSMnk/OTUk, OTUk, OTUk/ODUk, ODUkT, ODUkT/ODUk, and ODUkT. +- (c) Multiclient UNI:** Two Client triangles are each connected to an ODujP/Client triangle, which is connected to an ODujP triangle. These are then connected to ODUkT/ODUk triangles, which are connected to an ODUkP/ODUj triangle, which is finally connected to an ODUkT/ODUk triangle, which is connected to an ODUkT triangle. + +Figure 9-4 – UNI port compound functions. The diagram shows three types of UNI port structures: (a) CBR client UNI, (b) OTN client UNI, and (c) Multiclient UNI. Each structure is represented by a stack of triangles indicating the hierarchy of functions from the client down to the network interface. + +G.798.1(11)\_F9-4 + +**Figure 9-4 – UNI port compound functions** + +# 10 Basic OTN equipment types + +Several examples of OTN equipment are described in this section, illustrating different ways to combine the atomic functions defined in [ITU-T G.798]. To keep diagrams simple, the NNI and UNI port compound functions from the previous section are used. + +## 10.1 3R regeneration compound function + +Figure 10-1 shows the model of 3R regeneration. This function is used in some of the equipment examples that follow. + +![Diagram of 3R regenerator compound function showing signal flow through four triangular blocks. The top two blocks are labeled 'OTUk/ODUk_A' and 'OTUk_TT'. The bottom two blocks are labeled 'OCh/OTUk_A' and 'OCh_TT'. A horizontal line connects the top two blocks, and vertical lines connect the top block to the bottom block in each pair. The bottom of each pair has a vertical line extending downwards. The label G.798.1(11)_F10-1 is at the bottom right.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) + +Diagram of 3R regenerator compound function showing signal flow through four triangular blocks. The top two blocks are labeled 'OTUk/ODUk\_A' and 'OTUk\_TT'. The bottom two blocks are labeled 'OCh/OTUk\_A' and 'OCh\_TT'. A horizontal line connects the top two blocks, and vertical lines connect the top block to the bottom block in each pair. The bottom of each pair has a vertical line extending downwards. The label G.798.1(11)\_F10-1 is at the bottom right. + +Figure 10-1 – 3R regenerator compound function + +## 10.2 OTN network termination unit (NTU) + +An OTN network termination unit adapts one or more client signals (CBR, packet, or single-channel OTN) into either a WDM port or a single-channel OTN port. Three examples of NTU are shown below: single channel single client, single channel multiple client, and multiple channel. + +![Two diagrams labeled (a) and (b). (a) shows a 'UNI (single client)' block connected to an 'I-NNI type 2' block, which is connected to a 'Single-channel physical layer' block. (b) shows a 'UNI (multiple client)' block connected to an 'I-NNI type 1 or type 3' block, which is connected to a 'Single-channel physical layer' block. The label G.798.1(11)_F10-2 is at the bottom right.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +Two diagrams labeled (a) and (b). (a) shows a 'UNI (single client)' block connected to an 'I-NNI type 2' block, which is connected to a 'Single-channel physical layer' block. (b) shows a 'UNI (multiple client)' block connected to an 'I-NNI type 1 or type 3' block, which is connected to a 'Single-channel physical layer' block. The label G.798.1(11)\_F10-2 is at the bottom right. + +Figure 10-2 – Examples of single channel OTN NTU equipment + +![Diagram of multiple channel OTN NTU equipment showing two parallel paths. The left path has a 'UNI (multiple client)' block connected to an 'I-NNI type 1 or type 3' block. The right path has a 'UNI (single client)' block connected to an 'I-NNI type 2' block. Both paths converge to a common 'WDM physical layer' block at the bottom. The label G.798.1(11)_F10-3 is at the bottom right.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +Diagram of multiple channel OTN NTU equipment showing two parallel paths. The left path has a 'UNI (multiple client)' block connected to an 'I-NNI type 1 or type 3' block. The right path has a 'UNI (single client)' block connected to an 'I-NNI type 2' block. Both paths converge to a common 'WDM physical layer' block at the bottom. The label G.798.1(11)\_F10-3 is at the bottom right. + +Figure 10-3 – Example of multiple channel OTN NTU equipment + +## 10.3 Wavelength add/drop multiplexer (WADM) + +A wavelength ADM consists of two WDM ports (OTM-n.m interfaces) with add-drop or pass-through capability for the individual optical channels within the WDM signals. Add-drop and pass-through may be performed in the optical domain or the electrical domain if 3R regeneration is necessary. The figure below illustrates several possible connections that can be made in a WADM. Note that the coloured lines are used only to make it easier to distinguish the different channels within the diagram, and are not meant to indicate that the signal at that point is a WDM-compliant wavelength. + +The red channel illustrates optical pass-through. + +The orange channel on the right illustrates unprotected optical add-drop to a non-OTN client port. In this case, the functions of a UNI and an I-NNI type 2 are present, but there is no ODUk matrix between them since a wavelength ADM does not support ODU layer switching. + +The green channel on the right illustrates unprotected add-drop with 3R regeneration. + +The orange and green channels on the left are not in use. + +The blue channel illustrates protected optical add-drop. + +The purple channel illustrates electrical pass-through (3R regeneration). + +![Diagram of a Wavelength Add/Drop Multiplexer (WADM) showing various optical channel connections between two WDM ports and different client types.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +The diagram shows a central oval labeled "OCh\_C" containing an "SNC" (Subnetwork Connection) block. Two "WDM port" blocks are on the left and right. Various colored lines represent signal paths: + +- Red (solid):** Connects left WDM port to right WDM port directly through the SNC. +- Blue (thick dashed):** Connects left WDM port to a "Single-channel physical layer" block in the "OCh client" section. +- Orange (thin dashed):** Connects right WDM port to an "I-NNI type 2" block, which connects to a "UNI" block in the "Non-OTN client" section. +- Green (thin dashed):** Connects right WDM port to a "3R regeneration" block, which connects to a "Single-channel physical layer" block in the "OCh client with regeneration" section. +- Purple (dotted):** Connects left WDM port to right WDM port via an external "3R regeneration" block at the top. + +| Line style | Color indicated in text | +|------------|-------------------------| +| — | Red | +| - - | Blue | +| --- | Orange | +| --- | Green | +| ... | Purple | + +G.798.1(11)\_F10-4 + +Diagram of a Wavelength Add/Drop Multiplexer (WADM) showing various optical channel connections between two WDM ports and different client types. + +**Figure 10-4 – Example of wavelength ADM showing various connections** + +## 10.4 Wavelength cross connect (WXC) + +A wavelength cross connect is similar to a WADM, except that it supports more than two WDM ports (OTM-n.m interfaces). One consequence of this difference is that protected connections can be supported with all three connection points supported by WDM ports (whereas in the WADM, protected connections always have a client port as the reliable resource). + +![Figure 10-5: Example of wavelength cross connect. The diagram shows a central OCh_C node connected to two WDM ports (top) and two Single-channel physical layers (bottom). The OCh_C node is also connected to an SNC node. The SNC node is connected to two 3R regeneration nodes (top) and a Non-OTN client (bottom). The Non-OTN client contains an I-NNI type 2 node and a UNI node. A legend indicates line styles and colors: Red (solid), Blue (dashed), Orange (dash-dot), Green (dotted), and Purple (dash-dot-dot).](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Line style      Color indicated in text + +- Red +- - Blue +- · Orange +- Green +- · · Purple + +G.798.1(11)\_F10-5 + +Figure 10-5: Example of wavelength cross connect. The diagram shows a central OCh\_C node connected to two WDM ports (top) and two Single-channel physical layers (bottom). The OCh\_C node is also connected to an SNC node. The SNC node is connected to two 3R regeneration nodes (top) and a Non-OTN client (bottom). The Non-OTN client contains an I-NNI type 2 node and a UNI node. A legend indicates line styles and colors: Red (solid), Blue (dashed), Orange (dash-dot), Green (dotted), and Purple (dash-dot-dot). + +**Figure 10-5 – Example of wavelength cross connect** + +## 10.5 Sub-wavelength cross connect (SWXC) + +### 10.5.1 Sub-wavelength cross connect (SWXC) Type I + +A sub-wavelength cross connect Type I adds an ODU matrix to a WXC. This allows flexibility in the assignment of clients to wavelengths and also supports multiplexing of multiple clients into a single wavelength. The I-NNI ports may or may not support an optical supervisory channel. Management and signalling communications channels may be supported via OSC or via GCC. + +![Figure 10-6a: Example of sub-wavelength cross connect. The diagram shows a central OCh_C node connected to two WDM ports (I-NNI) (left and right) and three WDM ports (E-NNI) (bottom). The OCh_C node is also connected to an ODUk_C node. The ODUk_C node is connected to three UNI nodes (top) and five NNI nodes (middle): I-NNI type 3, I-NNI type 2, I-NNI type 1, E-NNI type 2, and E-NNI type 1. The NNI nodes are connected to the OCh_C node. The WDM ports (I-NNI) are connected to OTM-n.m nodes. The WDM ports (E-NNI) are connected to OTM-nr.m, OTM-0.m, and OTM-nr.m nodes. A legend indicates line styles and colors: Red (solid), Blue (dashed), Orange (dash-dot), Green (dotted), and Purple (dash-dot-dot).](a4b963a07cc368283154762c4b156fe7_img.jpg) + +G.798.1(13)\_F10-6a + +Figure 10-6a: Example of sub-wavelength cross connect. The diagram shows a central OCh\_C node connected to two WDM ports (I-NNI) (left and right) and three WDM ports (E-NNI) (bottom). The OCh\_C node is also connected to an ODUk\_C node. The ODUk\_C node is connected to three UNI nodes (top) and five NNI nodes (middle): I-NNI type 3, I-NNI type 2, I-NNI type 1, E-NNI type 2, and E-NNI type 1. The NNI nodes are connected to the OCh\_C node. The WDM ports (I-NNI) are connected to OTM-n.m nodes. The WDM ports (E-NNI) are connected to OTM-nr.m, OTM-0.m, and OTM-nr.m nodes. A legend indicates line styles and colors: Red (solid), Blue (dashed), Orange (dash-dot), Green (dotted), and Purple (dash-dot-dot). + +**Figure 10-6a – Example of sub-wavelength cross connect** + +### 10.5.2 Sub-wavelength cross connect (SWXC) Type II + +A sub-wavelength cross-connect Type II includes an ODU matrix, zero or more UNI-N ports and a number of OTM-n I-NNI ports directly connected to WDM ports. This allows flexibility in the assignment of clients to wavelengths and also supports multiplexing of multiple clients into a single wavelength. The SWXC Type II does not include an OCh matrix and all wavelengths are terminated on the NNI port cards. Optical supervisory channel wavelengths are not supported on the WDM ports and management and signalling communication channels (MCC, SCC) are supported via OTUk GCC0. Values for n are, e.g., 8, 12, 16 and 20 with 10G wavelengths. Values for n are, e.g., 4, 5 with 100G wavelengths. + +The OTM-n NNI ports may support multiple I-NNI port types; e.g., I-NNI port types 1 and 2, or I-NNI port types 1, 2 and 3. + +NOTE 1 – [ITU-T G.709] specifies that OTM-n interfaces which do not support an OSC are reduced functionality OTM-nr.m interfaces. These interfaces are stated to be ITU-T G.959.1 compliant inter-domain interfaces with 16 or 32 wavelengths. The OTM-n NNI ports described here are reduced functionality intra-domain interfaces with vendor specific numbers of wavelengths and optical parameters. + +NOTE 2 – It is possible to deploy a set of four 10G wavelengths to transport an OTU3 over an n\*10G OTM-n NNI; e.g., an OTM-12 NNI can support a mix of OTU2, OTU2e, OTU3 and OTU3e signals. It is possible to deploy a set of ten 10G wavelengths to transport an OTU4 over an n\*10G OTM-n NNI; e.g., an OTM-20 NNI can then support a mix of OTU2, OTU2e, OTU3, OTU3e, OTU4 signals. The OTU3/3e and OTU4 signals are in those cases transported as groups of OTL-3.4/OTL3e.4 and OTL-4.10 signals. Care is to be taken not to exceed the differential delay compensation capabilities of the multi-lane receivers. The specific atomic functions to support such mixed OTUk/OTLk.n support are for further study. + +![Diagram of a sub-wavelength cross-connect Type II architecture. At the top, three UNI-N ports are connected to a central ODUk_C matrix. Below the matrix, there are five output paths. The first three paths lead to OTM-nr.m interfaces, each containing an I-NNI port (types 1 or 2, or 1, 2 or 3) connected to a WDM physical layer. The fourth and fifth paths lead to OTM-0.m interfaces, each containing an E-NNI port (type 1 or 2) connected to a single channel physical layer. The diagram is labeled 'Figure 10-6b – Example of sub-wavelength cross-connect Type II' and includes the reference 'G.798.1(13)_F10-6b'.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +Diagram of a sub-wavelength cross-connect Type II architecture. At the top, three UNI-N ports are connected to a central ODUk\_C matrix. Below the matrix, there are five output paths. The first three paths lead to OTM-nr.m interfaces, each containing an I-NNI port (types 1 or 2, or 1, 2 or 3) connected to a WDM physical layer. The fourth and fifth paths lead to OTM-0.m interfaces, each containing an E-NNI port (type 1 or 2) connected to a single channel physical layer. The diagram is labeled 'Figure 10-6b – Example of sub-wavelength cross-connect Type II' and includes the reference 'G.798.1(13)\_F10-6b'. + +Figure 10-6b – Example of sub-wavelength cross-connect Type II + +### 10.5.3 Sub-wavelength cross connect (SWXC) Type III + +A sub-wavelength cross-connect Type III combines the functionalities of sub-wavelength cross connect Type I and Type II. + +![Figure 10-6c: Example of sub-wavelength cross-connect Type III. This diagram shows a network architecture where seven UNI (User Network Interface) blocks are connected to a central ODUk_C (Optical Data Unit) oval. Below the ODUk_C, there are several E-NNI (External Network-to-Network Interface) and I-NNI (Internal Network-to-Network Interface) blocks. These interfaces connect to various physical layers: 'Single channel physical layer' (leading to OTM-0.m or OTM-0vm), 'WDM physical layer' (leading to OTM-nr.m), and 'OTM-n.m'. All these physical layers converge into a central OCh_C (Optical Channel) oval. From the OCh_C, multiple paths emerge: one to a 'WDM physical layer' (OTM-n.m), another to a 'Single channel physical layer' (OTM-0.m), and a third to another 'WDM physical layer' (OTM-n.m). A separate path from the OCh_C leads to a 'WDM physical layer' (OTM-n.m) labeled G.798.1(13)_F10-6c.](e451401f8fa77b466f401d5fce15b26c_img.jpg) + +Figure 10-6c: Example of sub-wavelength cross-connect Type III. This diagram shows a network architecture where seven UNI (User Network Interface) blocks are connected to a central ODUk\_C (Optical Data Unit) oval. Below the ODUk\_C, there are several E-NNI (External Network-to-Network Interface) and I-NNI (Internal Network-to-Network Interface) blocks. These interfaces connect to various physical layers: 'Single channel physical layer' (leading to OTM-0.m or OTM-0vm), 'WDM physical layer' (leading to OTM-nr.m), and 'OTM-n.m'. All these physical layers converge into a central OCh\_C (Optical Channel) oval. From the OCh\_C, multiple paths emerge: one to a 'WDM physical layer' (OTM-n.m), another to a 'Single channel physical layer' (OTM-0.m), and a third to another 'WDM physical layer' (OTM-n.m). A separate path from the OCh\_C leads to a 'WDM physical layer' (OTM-n.m) labeled G.798.1(13)\_F10-6c. + +Figure 10-6c – Example of sub-wavelength cross-connect Type III + +## 10.6 Optical amplifier + +An optical amplifier is used to amplify a WDM signal. It terminates the OTS layer but passes the OMS layer through intact. The OSC is accessible at an optical amplifier, allowing management access via the OTS COMMS channel. + +![Figure 10-7: Example of optical amplifier. This diagram shows two identical optical amplifier units. Each unit is represented by a triangle divided into two horizontal sections. The top section is labeled 'OTS_n/OMS_n_A' and the bottom section is labeled 'OTS_n_TT'. A line connects the top of one triangle to the top of the other, representing the optical signal path. Below the triangles, the text G.798.1(11)_F10-7 is present.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +Figure 10-7: Example of optical amplifier. This diagram shows two identical optical amplifier units. Each unit is represented by a triangle divided into two horizontal sections. The top section is labeled 'OTS\_n/OMS\_n\_A' and the bottom section is labeled 'OTS\_n\_TT'. A line connects the top of one triangle to the top of the other, representing the optical signal path. Below the triangles, the text G.798.1(11)\_F10-7 is present. + +Figure 10-7 – Example of optical amplifier + +## 10.7 Sub-wavelength add/drop multiplexer (SWADM) + +### 10.7.1 Sub-wavelength add/drop multiplexer (SWADM) Type I + +A SWADM Type I is a SWXC Type I with two WDM ports. + +### 10.7.2 Sub-wavelength add/drop multiplexer (SWADM) Type II + +A SWADM Type II is a SWXC Type II with two OTM-n ports. + +# 11 OTN and packet transport network (PTN) hybrid equipment + +Many OTN systems are also capable of supporting packet transport applications. A high-level description of OTN/PTN hybrid equipment is shown in Figure 11-1. The details of PTN functions are outside the scope of this Recommendation. + +At the UNI, packet services may be treated as any other CBR flow and mapped into ODUk without packet awareness, or they may be treated as packet flows and processed as described in other Recommendations. The latter option allows for aggregation of packets from multiple UNIs and/or splitting the flow at one UNI to multiple NNIs. After packet processing, the resulting stream is mapped to an ODU. + +At the NNI, ODUs carrying PTN traffic may pass through the ODU switch fabric prior to reaching the packet-processing function. This path is necessary if ODU SNC protection is required. This path provides greater flexibility in multiplexing ODUs because it allows the packet UNI, packet processing, and mapping to low order ODU functions, to be on a separate circuit pack from the NNI function. + +ODUs carrying PTN traffic may also bypass the ODU switch fabric. This architecture might be used for ODU2 or higher rate ODUs that carry PTN traffic directly and do not require ODU connection functions. Note that ODU multiplexing is still possible in this architecture but it may be constrained if the packet UNI, packet processing, ODU mapping, and NNI functions, are all located on the same circuit pack. + +![Diagram of OTN/PTN hybrid equipment architecture showing connections between CBR UNIs, Packet UNIs, ODU_C, Packet_C, Packet NNI with mapping into ODU, various NNI types, and OTN/WDM physical layers.](145d00f59802048185303f15937ea65c_img.jpg) + +The diagram illustrates the internal architecture of OTN/PTN hybrid equipment. At the top, four rectangular blocks represent user interfaces: two labeled 'CBR UNI' and two labeled 'Packet UNI'. The 'CBR UNI' blocks connect to an oval component labeled 'ODU\_C'. The 'Packet UNI' blocks connect to an oval component labeled 'Packet\_C'. Both 'ODU\_C' and 'Packet\_C' connect to a rectangular block labeled 'Packet NNI with mapping into ODU'. This block then connects to four rectangular blocks labeled 'I-NNI type 2', 'I-NNI type 1', 'E-NNI type 2', and 'E-NNI type 1'. These four NNI blocks all connect to a central oval component labeled 'OCh\_C'. Finally, 'OCh\_C' connects to four rectangular blocks labeled 'OTN/WDM physical layer', each connected via a multi-colored line representing multiple wavelengths. + +Diagram of OTN/PTN hybrid equipment architecture showing connections between CBR UNIs, Packet UNIs, ODU\_C, Packet\_C, Packet NNI with mapping into ODU, various NNI types, and OTN/WDM physical layers. + +**Figure 11-1 – OTN/PTN hybrid equipment** + +The Packet\_C could be Ethernet connection function ETH\_C as described in [ITU-T G.8021] or MPLS-TP connection function MT\_C as described in [ITU-T G.8121]. + +The Packet UNI/NNI could be Ethernet UNI/NNI as described in [ITU-T G.8012.1] or MPLS-TP NNI as described in [ITU-T G.8112]. + +# Appendix I + +## ODU multiplexing considerations + +(This appendix does not form an integral part of this Recommendation.) + +The ODU multiplexing mechanism is designed to allow ODUj of different rates to be multiplexed directly into an ODUk (e.g., an ODU3 may have ODU0, ODU1, ODU2, ODU2e, and/or ODUFlex multiplexed directly into it). In many applications, a single stage of multiplexing is sufficient. + +In other applications, more than one stage of multiplexing within a domain may be desirable or necessary. Examples of such applications include: + +- Adding ODU0 or ODUFlex clients to an existing OTN network based on equipment that does not support ODU0 or ODUFlex. In this case, it will be necessary to first multiplex those signals into an ODU that the existing network can support. (e.g., 2 x ODU0 into an ODU1, or a mix of ODU0 and ODUFlex into an ODU2). If the existing network uses ODU3 links, it will then be necessary to multiplex that ODU into an ODU3. The two stages of multiplexing could be done in one network element (on either the same card or different cards) or in separate network elements. +- Carrier-carrier applications, where the HO ODU of one carrier is treated as a LO ODU of the second carrier, may thus be multiplexed into a higher rate ODU in the second carrier's network. For example, carrier A may multiplex ODU0, ODU1, and ODUFlex into an ODU2. When that ODU2 is handed off to carrier B, carrier B may then multiplex the ODU2 into an ODU4. In this case, the two stages of multiplexing are always in separate network elements. +- Within a carrier's network, aggregation of traffic may occur at multiple points along the backhaul to a switching centre. In this case, there would be two stages of multiplexing built up in multiple network elements until the switching centre is reached. In the switching centre, all the multiplexing would be undone so that the individual client signals can be switched. +- Bundling of services may require two stages of multiplexing. For example, suppose that five gigabit Ethernet services are to be bundled together, each service would be mapped into an ODU0, and the five ODU0s would be multiplexed into an ODU2. If the transport links in the service provider's network are ODU3, a second stage of multiplexing would be used. + +# Appendix II + +## Examples of SNC protection implementation + +(This appendix does not form an integral part of this Recommendation.) + +In a network element supporting ODU cross-connect functions, switching can be performed at multiple ODU layers (e.g., ODuk or ODuj). Because SNC protection (as specified in [ITU-T G.873.1]) is a process within the ODU\_C function, SNC protection can also occur at multiple ODU layers. When the ODuk layer is protected, it can either be switched intact, or the reliable ODuk can be terminated with switching at the ODuj layer. + +In a technology, commonly available and in use today, OTN NEs consist of "port units" (PU) and "switch units". The switch units perform the cross-connection/switching, the port units perform all necessary OTN overhead processing. + +The typical implementation uses a single switch unit for both the ODuk and ODuj layers. A port unit will perform OTUk trail termination in all cases and ODukP trail termination when the switching is being done at the ODuj layer (see Figure II.1 for HO ODuk SNC/S; Figure II.2 for HO ODuk SNC/I). + +![Figure II.1: Port unit functions (simplified model) (HO ODuk SNC/S). The diagram shows a block diagram of a port unit. On the left, an 'OTUk OH' block is connected to an 'ODUkTm OH' block (dashed box). This is followed by a 'Selector' block. The output of the selector splits into two paths: one goes to an 'ODUkTh OH' block (dashed box) and the other to an 'ODUkP OH' block. Both of these blocks are connected to a 'BDI/BEI cross-coupling to mate card' (dashed box at the top). The 'ODUkTh OH' block is connected to an 'ODUjT OH' block (dashed box), which outputs to 'ODUj'. The 'ODUkP OH' block outputs to 'ODUk'. The diagram is labeled G.798.1(13)_FII.1 at the bottom right.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +Figure II.1: Port unit functions (simplified model) (HO ODuk SNC/S). The diagram shows a block diagram of a port unit. On the left, an 'OTUk OH' block is connected to an 'ODUkTm OH' block (dashed box). This is followed by a 'Selector' block. The output of the selector splits into two paths: one goes to an 'ODUkTh OH' block (dashed box) and the other to an 'ODUkP OH' block. Both of these blocks are connected to a 'BDI/BEI cross-coupling to mate card' (dashed box at the top). The 'ODUkTh OH' block is connected to an 'ODUjT OH' block (dashed box), which outputs to 'ODUj'. The 'ODUkP OH' block outputs to 'ODUk'. The diagram is labeled G.798.1(13)\_FII.1 at the bottom right. + +Figure II.1 – Port unit functions (simplified model) (HO ODuk SNC/S) + +![Figure II.2: Port unit functions (simplified model) (HO ODuk SNC/I). The diagram shows a block diagram of a port unit. On the left, an 'OTUk OH' block is connected to a 'Selector' block. The output of the selector splits into two paths: one goes to an 'ODUkT OH' block (dashed box) and the other to an 'ODUkP OH' block. Both of these blocks are connected to a 'BDI/BEI cross-coupling to mate card' (dashed box at the top). The 'ODUkT OH' block is connected to an 'ODUjT OH' block (dashed box), which outputs to 'ODUj'. The 'ODUkP OH' block outputs to 'ODUk'. The diagram is labeled G.798.1(13)_FII.2 at the bottom right.](f1091147d93cee4dfa88498610e395a7_img.jpg) + +Figure II.2: Port unit functions (simplified model) (HO ODuk SNC/I). The diagram shows a block diagram of a port unit. On the left, an 'OTUk OH' block is connected to a 'Selector' block. The output of the selector splits into two paths: one goes to an 'ODUkT OH' block (dashed box) and the other to an 'ODUkP OH' block. Both of these blocks are connected to a 'BDI/BEI cross-coupling to mate card' (dashed box at the top). The 'ODUkT OH' block is connected to an 'ODUjT OH' block (dashed box), which outputs to 'ODUj'. The 'ODUkP OH' block outputs to 'ODUk'. The diagram is labeled G.798.1(13)\_FII.2 at the bottom right. + +Figure II.2 – Port unit functions (simplified model) (HO ODuk SNC/I) + +## II.1 Analysis + +In the case of ODuk switching (with or without ODuk SNC protection) or ODukP termination and ODuj switching (with or without ODuj SNC protection), the implementation and functional models are fully aligned. + +In the case of ODUk SNC protection but ODUj switching, the implementation does not strictly match the functional model (Figure II.3 for HO ODUk SNC/S; Figure II.4 for HO ODUk SNC/I). Two ports units are used (one for each ODUk), and each unit performs OTUk termination and ODUkP termination, while the ODUj protection switch is implemented at the switch unit by switching the total group of ODUj signals. + +![Figure II.3 – Mapping of functional view into implementation (HO ODUk SNC/S). The diagram is split into two columns: 'Functional model, management view' on the left and 'Implementation model' on the right. The functional model shows a 'Switch unit' containing an 'ODUj' node connected to three 'ODUjT/ODUj' nodes, which then connect to 'ODUk/ODUj' nodes, then 'ODUkT/ODUk' nodes, and finally 'ODUkTn' nodes. Below this, an 'ODUk' node with an 'SNC' block connects to two 'Port unit' blocks. Each 'Port unit' contains 'ODUkT/ODUk' nodes, 'ODUkTm' nodes, 'OTUk/ODUk' nodes, and 'OTUk' nodes. The implementation model shows a 'Switch unit' containing an 'ODUj' node connected to an 'SNCG' block. The 'SNCG' block is connected to two 'TCM' nodes, which then connect to 'ODUk/ODUj' nodes, then 'ODUkP' nodes, then 'ODUkT/ODUk' nodes, then 'ODUkTm' nodes, then 'OTUk/ODUk' nodes, and finally 'OTUk' nodes. A central yellow block labeled 'RDI/REI cross-coupling for ODUkTn, ODUkP, ODUjT' and 'Input MI_xxx dual-feed' / 'Output MI_xxx selection from active unit' is connected to the 'ODUk/ODUj' nodes. The 'Port unit' blocks at the bottom are identical to those in the functional model.](67114ecf6da13c97a89aeff0d86885d5_img.jpg) + +Figure II.3 – Mapping of functional view into implementation (HO ODUk SNC/S). The diagram is split into two columns: 'Functional model, management view' on the left and 'Implementation model' on the right. The functional model shows a 'Switch unit' containing an 'ODUj' node connected to three 'ODUjT/ODUj' nodes, which then connect to 'ODUk/ODUj' nodes, then 'ODUkT/ODUk' nodes, and finally 'ODUkTn' nodes. Below this, an 'ODUk' node with an 'SNC' block connects to two 'Port unit' blocks. Each 'Port unit' contains 'ODUkT/ODUk' nodes, 'ODUkTm' nodes, 'OTUk/ODUk' nodes, and 'OTUk' nodes. The implementation model shows a 'Switch unit' containing an 'ODUj' node connected to an 'SNCG' block. The 'SNCG' block is connected to two 'TCM' nodes, which then connect to 'ODUk/ODUj' nodes, then 'ODUkP' nodes, then 'ODUkT/ODUk' nodes, then 'ODUkTm' nodes, then 'OTUk/ODUk' nodes, and finally 'OTUk' nodes. A central yellow block labeled 'RDI/REI cross-coupling for ODUkTn, ODUkP, ODUjT' and 'Input MI\_xxx dual-feed' / 'Output MI\_xxx selection from active unit' is connected to the 'ODUk/ODUj' nodes. The 'Port unit' blocks at the bottom are identical to those in the functional model. + +Figure II.3 – Mapping of functional view into implementation (HO ODUk SNC/S) + +![Figure II.4 – Mapping of functional view into implementation (HO ODUk SNC/I). The diagram is split into two parts. The left part shows a functional view where a 'Switch unit' contains an 'ODUj' oval connected to three stacked trapezoidal blocks: 'ODUjT/ODUj' (top), 'ODUk/ODUj' (middle), and 'ODUkT/ODUk' (bottom). Below this, an 'SNC' oval labeled 'ODUk' connects to two 'Port unit' boxes, each containing 'OTUk/ODUk' and 'OTUk' trapezoidal blocks. The right part shows the implementation view. The 'Switch unit' contains an 'ODUj' oval connected to an 'SNC' box. Below the 'SNC' box, there are two 'TCM' trapezoidal blocks. In the center is a yellow box labeled 'RDI/REI cross-coupling for ODUkT, ODUkP, ODUjT', 'Input MI_xxx dual-feed', and 'Output MI_xxx selection from active unit'. This central box is connected to the 'TCM' blocks and to two 'ODUk/ODUj' (top) and 'ODUkT/ODUk' (bottom) trapezoidal blocks. Each of these blocks is connected to an 'ODUkP' block, which in turn connects to an 'OTUk/ODUk' and 'OTUk' trapezoidal block within a 'Port unit' box. The diagram is labeled 'G.798.1(13)_FII.4' at the bottom right.](9a5927586a691c4908aa2cf98bd47ebb_img.jpg) + +Figure II.4 – Mapping of functional view into implementation (HO ODUk SNC/I). The diagram is split into two parts. The left part shows a functional view where a 'Switch unit' contains an 'ODUj' oval connected to three stacked trapezoidal blocks: 'ODUjT/ODUj' (top), 'ODUk/ODUj' (middle), and 'ODUkT/ODUk' (bottom). Below this, an 'SNC' oval labeled 'ODUk' connects to two 'Port unit' boxes, each containing 'OTUk/ODUk' and 'OTUk' trapezoidal blocks. The right part shows the implementation view. The 'Switch unit' contains an 'ODUj' oval connected to an 'SNC' box. Below the 'SNC' box, there are two 'TCM' trapezoidal blocks. In the center is a yellow box labeled 'RDI/REI cross-coupling for ODUkT, ODUkP, ODUjT', 'Input MI\_xxx dual-feed', and 'Output MI\_xxx selection from active unit'. This central box is connected to the 'TCM' blocks and to two 'ODUk/ODUj' (top) and 'ODUkT/ODUk' (bottom) trapezoidal blocks. Each of these blocks is connected to an 'ODUkP' block, which in turn connects to an 'OTUk/ODUk' and 'OTUk' trapezoidal block within a 'Port unit' box. The diagram is labeled 'G.798.1(13)\_FII.4' at the bottom right. + +**Figure II.4 – Mapping of functional view into implementation (HO ODUk SNC/I)** + +According to the functional model, too much functionality is present on each port unit in the implementation; i.e., OTUk processing and optional ODUkT processing is expected to be present twice, while ODUkP and optional ODUjT processing should be present only once. It is expected that SNC/I or SNC/S protection at the ODUk layer is present; instead, SNC group protection at the ODUj layer is performed. + +With software, an NE can present the expected functionality via BDI/BEI cross-coupling: + +- For SNC/S, it hides the standby ODUkT\_TT (applicable to the TCM layer n which is outside of or the same scope as the specified TCM layer m for SNC/S protection), ODUkP\_TT and ODUjT\_TT processes for the manager, and presents the ODUj group switching as ODUk switching. This is accomplished by ensuring that all MI\_xxx input signals are configured the same on both port units, selecting MI\_xxx output signals from the active port unit, and ensuring that the same BDI and BEI signals are output from both ODUkT\_TT, ODUkP\_TT, and ODUjT\_TT functions. +- For HO ODUk SNC/I, it hides the standby ODUkT\_TT, ODUkP\_TT and ODUjT\_TT processes for the manager, and presents the ODUj group switching as ODUk switching. This is accomplished by ensuring that all MI\_xxx input signals are configured the same on both port units, selecting MI\_xxx output signals from the active port unit, and ensuring that the same BDI/BEI signals are output from ODUkT\_TT (applicable to any terminated TCM layer), ODUkP\_TT, and ODUjT\_TT functions. + +In the case where BDI/BEI cross-coupling is not implemented, it will not be possible to add ITU-T G.826 performance monitoring to networks in which the above protection implementations are operational. [ITU-T G.826] requires bidirectional (services based) performance monitoring to be supported. This requires that the far-end information be used. This far-end information must represent the error/defects detected in the signal path that is actually transporting the client information. + +Unidirectional switching causes each end of the protection span to independently select between working and protection trail/SNC. If, in the direction $A \rightarrow Z$ , the working ODU SNC is selected and protection ODU SNC, in the direction $Z \rightarrow A$ the far-end information extracted at each end is inserted by the ODUkP\_TT or ODUjT\_TT on the standby port unit; i.e., the one that is not selected at this end. If it (now) uses its local RI\_BDI/RI\_BEI signals (instead of its companion RI\_BDI/RI\_BEI signals), the far-end would receive far-end information that is not related to the actually selected ODU. + +The bidirectional performance monitoring registers would (in this case) represent the wrong information; i.e., it cannot be used. + +The same problem exists for the unidirectional (maintenance based) far-end registers. + +# Appendix III + +## OTN link and connection examples + +(This appendix does not form an integral part of this Recommendation.) + +This appendix illustrates multiple types of OTN connections and links and the relationships between these OTN connections and links. These links and connections are illustrated within the context of an OTN subnetwork example illustrated in Figure III.1. This subnetwork contains a number of SWXC Type I and Type III, WXC and OA network elements (A to K). These network elements are connected via fibres over which OTM-n.m or OTN-nr.m interface signals are transported. This subnetwork provides an ODU0 or ODUflex subnetwork connection between port X on Node A and port Y on Node H. The subnetwork connection passes through intermediate Nodes B, C, D, E, F and G. Node G is not capable of supporting an ODU0 or ODUflex. Nodes E and H will therefore deploy I-NNI Type 3 (I3) ports supporting 2-stage ODU multiplexing. These I3 ports will cause nesting of ODU links. ODU link nesting implies that an outer ODU link contains or supports a smaller, inner ODU link. Such smaller, inner ODU link may have zero, one or both end points co-located with the larger, outer ODU link. In the first two cases, the smaller, inner ODU link is supported by two or more, larger, outer ODU links. + +![Figure III.1 – OTN subnetwork example. A network diagram showing nodes A through K connected by OTM-n.m and OTN-nr.m links. Node A (SWXC Type I) has port X. Node H (SWXC Type III) has port Y. A dashed line represents an ODU0/flex subnetwork connection from port X to port Y. Intermediate nodes include OA (B), WXC (C, D, F, J, K), SWXC Type I (E), and SWXC Type III (G). Node G is labeled 'G: ODU0/flex not supported'.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +The diagram illustrates an OTN subnetwork with the following components and connections: + +- Node A:** SWXC Type I, with port X. It is connected to Node B via an OTM-n.m link. +- Node B:** OA (Optical Amplifier), connected to Node A and Node C via OTM-n.m links. +- Node C:** WXC (Wavelength Cross-Connect), connected to Node B, Node D, and Node K via OTM-n.m links. +- Node D:** WXC, connected to Node C, Node E, and Node F via OTM-n.m links. +- Node E:** SWXC Type I, connected to Node D and Node F via OTM-n.m links. It has an I-NNI Type 3 (I3) port. +- Node F:** WXC, connected to Node D, Node E, and Node G via OTM-n.m links. +- Node G:** SWXC Type III, connected to Node F and Node H via OTM-nr.m links. A note indicates "G: ODU0/flex not supported". +- Node H:** SWXC Type III, connected to Node G via OTM-nr.m links. It has port Y and an I-NNI Type 3 (I3) port. +- Node I:** Not explicitly shown in the diagram but mentioned in the text as an intermediate node. +- Node J:** WXC, connected to Node C, Node K, and Node G via OTM-n.m links. +- Node K:** WXC, connected to Node C, Node J, and Node G via OTM-n.m links. + +A dashed line labeled "ODU0/flex subnetwork connection" originates from port X on Node A and terminates at port Y on Node H, passing through the intermediate nodes. + +Figure III.1 – OTN subnetwork example. A network diagram showing nodes A through K connected by OTM-n.m and OTN-nr.m links. Node A (SWXC Type I) has port X. Node H (SWXC Type III) has port Y. A dashed line represents an ODU0/flex subnetwork connection from port X to port Y. Intermediate nodes include OA (B), WXC (C, D, F, J, K), SWXC Type I (E), and SWXC Type III (G). Node G is labeled 'G: ODU0/flex not supported'. + +Figure III.1 – OTN subnetwork example + +Figures III.2 to III.7 illustrate the set-up of OTS, OMS, OCh and ODU connections and OCh and ODU links in a step-by-step manner. The configurations of the atomic functions described hereafter are accomplished using the MI signals as specified in [ITU-T G.798]. + +Figure III.2 illustrates the main network elements and their functionality of interest in this example prior to interconnecting OTM-n ports on those network elements together. **NE A** is a SWXC Type I network element containing ODU (green ellipses) and OCh (red ellipses) connection functions, an I-NNI Type 1/2 port (I) interconnecting the ODU and OCh connection functions and an OTM-n.m port (n.m) connecting the OCh connection function with the physical interface port. **NE B** is an OA network element containing two back to back OTM-n interface ports. **NE C, NE D and NE F** are WXC network elements containing an OCh connection function and at either side an OTM-n.m port connecting the OCh connection function with the physical interface ports at the left and right sides. **NE E** is a SWXC Type I network element containing ODU and OCh connection functions, an I-NNI Type 1/2 port and an I-NNI Type 1/2/3 port interconnecting the ODU and OCh connection functions and at each side an OTM-n.m port connecting the OCh connection function with the physical interface ports. **NE G** is a SWXC Type III network element containing ODU and OCh connection functions, I-NNI Type 1/2 ports at each side of the ODU connection function, an OTM-n.m port connecting the OCh connection functions with the left physical interface port and an OTM-nr.m port connecting one of the I-NNI type 1/2 ports with the right physical interface port. **NE H** is a SWXC Type III network element with one I-NNI type 1/2 port and one I-NNI Type 1/2/3 port. + +![Diagram showing various OTN network elements (NE A through NE H) and their internal functional blocks and port types. The diagram includes labels for ODUkP, OTUk[V], OCh, OMSn, OPSn, and OTSn. A note indicates that ODU connection functions are used to select between ODU termination and ODU pass-through.](b05bae46f7079e5c9b1da38adb2319e8_img.jpg) + +The diagram illustrates the internal functional architecture of eight different network elements (NE A through NE H) in an OTN network. Each NE is shown with its specific combination of ODU (green ellipses), OCh (red ellipses), and I-NNI (I) ports, and how they are interconnected with physical interface ports (OTM-n.m). + +- NE A (SWXC Type I):** Shows a vertical stack of functional blocks: ODUkP, OTUk[V], OCh, and OMSn/OPSn/OTSn. It has an I-NNI port (I) and an OTM-n.m port (n.m). +- NE B (OA):** Shows two back-to-back OTM-n interface ports (n.m). +- NE C and NE D (WXC):** Show OCh connection functions with OTM-n.m ports (n.m) on both sides. +- NE E (SWXC Type I):** Shows a more complex internal structure with multiple ODU and OCh connection functions, I-NNI ports (I), and OTM-n.m ports (n.m) on both sides. A note indicates: "Those ODU connections functions are used to select between ODU termination and ODU pass-through". +- NE F (WXC):** Similar to NE C and D, showing OCh connection functions with OTM-n.m ports (n.m) on both sides. +- NE G (SWXC Type III):** Shows ODU and OCh connection functions, I-NNI Type 1/2 ports (I) on both sides of the ODU function, an OTM-n.m port on the left, and an OTM-nr.m port on the right. A note indicates: "ODU0/flex not supported". +- NE H (SWXC Type III):** Shows ODU and OCh connection functions, an I-NNI Type 1/2 port (I) on the left, and an I-NNI Type 1/2/3 port (I) on the right. + +Common functional blocks shown across the elements include ODUkP, OTUk[V], OCh, OMSn, OPSn, and OTSn. The diagram uses green ellipses for ODU functions and red ellipses for OCh functions. Port types are labeled as 'I' for I-NNI and 'n.m' for OTM-n.m. + +Diagram showing various OTN network elements (NE A through NE H) and their internal functional blocks and port types. The diagram includes labels for ODUkP, OTUk[V], OCh, OMSn, OPSn, and OTSn. A note indicates that ODU connection functions are used to select between ODU termination and ODU pass-through. + +G.798.1(13)\_FIII.2 + +**Figure III.2 – Some OTN network elements without fibre interconnections and their basic port and switching functionalities** + +Figure III.3 illustrates the interconnection of OTM-n and OTM-nr ports on NE A to NE H by means of fibres. After connection of a fibre between NE A and NE B, a physical link and an OTS network connection is created. After connection of a fibre between NE B and NE C a second physical link and second OTS network connection is created; also an OMS network connection between NE A and NE C appears. This latter network connection and its bounding OMS trail termination and adaptation functions establish an OCh link between NE A and NE C. Similarly, physical links and OCh links are established after connecting a fibre between NEs C and D, NEs D and E, NEs E and F and NEs F and G. After connection of a fibre between NE G and NE H a physical link, an OChr link and also an ODUk link are established. + +![Diagram illustrating the interconnection of OTM-n and OTM-nr ports on NE A to NE H via fibres, showing various network layers and links.](878d9539700bd792e7d12ad6f1203c5d_img.jpg) + +The diagram shows a sequence of network elements (NEs) connected by fibres, with various network layers and links established at different points. + +- NE A:** SWXC Type I. It has an internal structure with 'I' and 'n.m' ports. It connects to NE B via a physical link. +- NE B:** OA (Optical Amplifier). It has 'n' and 'n' ports. It connects to NE C via a physical link. +- NE C:** WXC (Wavelength Cross-Connector). It has 'n.m' and 'n.m' ports. It connects to NE D via a physical link. +- NE D:** WXC. It has 'n.m' and 'n.m' ports. It connects to NE E via a physical link. +- NE E:** SWXC Type I. It has 'n.m', 'I', 'I', and 'n.m' ports. It connects to NE F via a physical link. +- NE F:** WXC. It has 'n.m' and 'n.m' ports. It connects to NE G via a physical link. +- NE G:** SWXC Type III. It has 'n.m', 'I', 'I', and 'nr.m' ports. A note indicates 'ODU0/flex not supported'. It connects to NE H via a physical link. +- NE H:** SWXC Type III. It has 'nr.m', 'I', 'I', and 'n.m' ports. + +Network layers and links shown: + +- ODUkP:** Optical Data Unit k Payload. Shown at NE A and NE H. +- OTUk[V]:** Optical Transport Unit k. Shown at NE A and NE H. +- OCh:** Optical Channel. Shown as a pink line connecting NE A and NE C. +- OMS:** Optical Multiplex Section. Shown as OMSn at NE A. +- OPS:** Optical Payload Section. Shown as OPSn at NE A. +- OTS:** Optical Transport Section. Shown as OTSn at NE A. +- Physical link:** Shown as a black line between adjacent NEs (A-B, B-C, C-D, D-E, E-F, F-G, G-H). +- Link:** Shown as a pink line between NE A and NE C, and between NE G and NE H. +- ODUk link:** Shown as a green line between NE G and NE H. + +The diagram also includes various symbols for optical components like amplifiers and switches, and a reference label 'G.798.1(13)\_FIII.3' at the bottom right. + +Diagram illustrating the interconnection of OTM-n and OTM-nr ports on NE A to NE H via fibres, showing various network layers and links. + +**Figure III.3 – Interconnecting OTM-n interface ports via fibres to establish (i) OCh links between NEs A and C, C and D, D and E, E and F, and F and G; (ii) OChr link between NEs G and H; (iii) ODUk link between NEs G and H** + +Figure III.4 illustrates the establishment of two ODuk links, one between NE A and NE E and the other one between NE E and NE G. The **ODuk link A-E** is established by creating an OCh network connection between NE A and NE E via the creation of OCh connection points in NEs A, C, D and E (which establishes OCh link connections between NEs A and C, NEs C and D, and NEs D and E), the set-up of four OCh matrix connections in NEs A, C, D, and E between those connection points, and the configuration of the OCh and OTUk[V] trail termination and adaptation functions at each end point. Similarly, the **ODuk link E-G** is established by creating an OCh network connection between NE E and NE G via the creation of OCh connection points in NEs E, F and G (which establishes OCh link connections between NEs E and F and NEs F and G), the set up of three OCh matrix connections in NEs E, F and G between those connection points, and the configuration of the OCh and OTUk[V] trail termination and adaptation functions at each end point. + +![Diagram illustrating the network architecture for setting up OCh network connections between NEs A and E, and E and G to establish ODU links. The diagram shows a sequence of network elements: NE A (SWXC Type I), NE B (OA), NE C (WXC), NE D (WXC), NE E (SWXC Type I), NE F (WXC), NE G (SWXC Type III, ODU0/flex not supported), and NE H (SWXC Type III). Above the elements, boxes show internal port configurations: NE A has ports 'I' and 'n.m'; NE B has 'n' and 'n'; NE C and D have 'n.m' and 'n.m'; NE E has 'n.m', 'I', 'I', and 'n.m'; NE F has 'n.m' and 'n.m'; NE G has 'n.m', 'I', 'I', and 'nr.m'; NE H has 'nr.m', 'I', 'I', and 'n.m'. Below the elements, a layered model shows the hierarchy: ODUP (top), OTUk[V], OCh, OMSn, OPSn, OTSn, and Physical link (bottom). Two green horizontal lines represent ODuk links: one from NE A to NE E, and another from NE E to NE G. Annotations indicate the setup of matrix and link connections: 'Set up 4 matrix connections and 3 link connections' for the A-E path, and 'Set up 3 matrix connections and 2 link connections' for the E-G path. The diagram is labeled G.798.1(13)_FIII.4 at the bottom right.](6cc85a2b62fd8a2a3faab29730f20e81_img.jpg) + +Diagram illustrating the network architecture for setting up OCh network connections between NEs A and E, and E and G to establish ODU links. The diagram shows a sequence of network elements: NE A (SWXC Type I), NE B (OA), NE C (WXC), NE D (WXC), NE E (SWXC Type I), NE F (WXC), NE G (SWXC Type III, ODU0/flex not supported), and NE H (SWXC Type III). Above the elements, boxes show internal port configurations: NE A has ports 'I' and 'n.m'; NE B has 'n' and 'n'; NE C and D have 'n.m' and 'n.m'; NE E has 'n.m', 'I', 'I', and 'n.m'; NE F has 'n.m' and 'n.m'; NE G has 'n.m', 'I', 'I', and 'nr.m'; NE H has 'nr.m', 'I', 'I', and 'n.m'. Below the elements, a layered model shows the hierarchy: ODUP (top), OTUk[V], OCh, OMSn, OPSn, OTSn, and Physical link (bottom). Two green horizontal lines represent ODuk links: one from NE A to NE E, and another from NE E to NE G. Annotations indicate the setup of matrix and link connections: 'Set up 4 matrix connections and 3 link connections' for the A-E path, and 'Set up 3 matrix connections and 2 link connections' for the E-G path. The diagram is labeled G.798.1(13)\_FIII.4 at the bottom right. + +**Figure III.4 – Setting up OCh network connections between NEs A and E, and E and G to establish ODU links between NEs A and E, and E and G** + +Figure III.5 illustrates the establishment of three ODUsj links ( $j < k$ ) between NEs A and E, NEs E and G and NEs G and H. The **ODUsj link A-E** is established by creating an ODUsk network connection between NE A and NE E via the configuration of the I-NNI type 1/2 ports in NEs A and E as a Type 1 ports (I1), the creation of ODU connection points in NEs A and E, the set up of two ODUsk matrix connections in NEs A and E between those connection points, the set-up of an ODUsk link connection in the ODUsk link A-E between two of those connection points, and the configuration of the ODUskP trail termination and adaptation functions at each end point. The **ODUsj link E-G** is established by creating an ODUsk network connection between NE E and NE G via the creation of ODU connection points in NEs E and G, the configuration of the I-NNI type 1/2/3 port in NE E as a Type 3 port (I3), the configuration of the I-NNI type 1/2 port in NE G as a Type 1 port (I1), the set up of two ODUsk matrix connections in NEs E and G between those connection points, the set-up of one ODUsk link connection in the ODUsk link E-G between two of those connection points, and the configuration of the ODUskP trail termination and adaptation functions at each end point. The **ODUsj link G-H** is established by creating an ODUsk network connection between NE G and NE H via the creation of ODU connection points in NEs G and H, the configuration of the I-NNI type 1/2 port in NE G as a Type 1 port (I1), the configuration of the I-NNI type 1/2/3 port in NE H as a Type 3 port (I3), the set up of two ODUsk matrix connections in NEs G and H between those connection points, the set-up of one ODUsk link connection in the ODUsk link G-H between two of those connection points, and the configuration of the ODUskP trail termination and adaptation functions at each end point. + +![Diagram illustrating the setup of three ODUk network connections between NEs A and E, E and G, and G and H to establish three ODUj links between the same NE pairs.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +The diagram shows a sequence of Network Elements (NEs) labeled A through H at the top. + - NE A: SWXC Type I with ports [I1] [n.m] + - NE B: OA with ports [n] [n] + - NE C: WXC with ports [n.m] [n.m] + - NE D: WXC with ports [n.m] [n.m] + - NE E: SWXC Type I with ports [n.m] [I1] [I3] [n.m] + - NE F: WXC with ports [n.m] [n.m] + - NE G: SWXC Type III with ports [n.m] [I1] [I1] [nr.m]. A note below states 'ODU0/flex not supported'. + - NE H: SWXC Type III with ports [nr.m] [I3] [I] [n.m] + + Below the NEs, a layered architecture is shown: + - Top layer: ODUj links (green lines) established between A-E, E-G, and G-H. + - Middle layer: ODUk links (green lines) established between A-E, E-G, and G-H. Annotations indicate 'Set up 2 matrix connections and link connection' at NE E, NE G, and NE H. + - Lower layers: Show adaptation functions including ODUkP, OTUk[V], OCh, OMSn, OPSn, and OTSn. + - Bottom layer: Physical links (black lines) connecting the NEs sequentially from A to H. Red 'Link' labels are shown between the adaptation stages. + +Diagram illustrating the setup of three ODUk network connections between NEs A and E, E and G, and G and H to establish three ODUj links between the same NE pairs. + +**Figure III.5 – Setting up three ODUk network connections between NEs A and E, E and G, and G and H to establish three ODUj links between the same NE pairs** + +Figure III.6 illustrates the establishment of an ODUi link ( $i < j < k$ ) between NEs E and H. The **ODUi link E-H** is established by creating an ODUj network connection between NE E and NE H via the creation of ODU connection points in NEs E, G and H, the set up of three ODUj matrix connections in NEs E, G and H between those connection points, the set up of two ODUj link connections in the ODUj links E-G and G-H between these connection points, and the configuration of the ODUkP trail termination and adaptation functions at each end point. There are no intermediate ODU link points present in NE G in this ODUi link. When setting up a connection in such ODUi link, it will only be required to configure ODU connection points in the ODUi link end points in NE E and NE H, see Figure III.7. + +![Diagram showing network elements (NE A to H) and their internal structures (SWXC, OA, WXC) and connections (ODUj, ODUk, ODUi, Link, Physical link).](12c19090355e19922e23044633b9d1ea_img.jpg) + +The diagram illustrates a network topology with eight network elements (NE A through NE H) connected in a linear sequence. Each NE is represented by a box containing internal components and their interfaces. + +- NE A:** SWXC Type I with interfaces I1 and n.m. +- NE B:** OA with interfaces n and n. +- NE C:** WXC with interfaces n.m and n.m. +- NE D:** WXC with interfaces n.m and n.m. +- NE E:** SWXC Type I with interfaces n.m, I1, I3, and n.m. +- NE F:** WXC with interfaces n.m and n.m. +- NE G:** SWXC Type III with interfaces n.m, I1, I1, and nr.m. A note indicates "ODU0/flex not supported". +- NE H:** SWXC Type III with interfaces nr.m, I3, I, and n.m. + +Connections between these elements are shown at different layers: + +- ODUj links:** Green lines connecting NE A to NE E and NE E to NE H. +- ODUk links:** Green lines connecting NE A to NE E and NE E to NE H, positioned below the ODUj links. +- Links:** Red lines connecting NE A to NE E and NE E to NE H, positioned below the ODUk links. +- Physical links:** Black lines at the bottom, connecting the physical layers of adjacent NEs. + +Internal components and interfaces are labeled on the left side of the diagram: ODUkP, ODUkP, OTUk[V], OCh, OMSn, OPSn, and OTSn. A callout from NE E points to the ODUi link setup, stating "Set up 3 matrix connections and 2 link connections". The diagram is labeled "G.798.1(13)\_FIII.6" in the bottom right corner. + +Diagram showing network elements (NE A to H) and their internal structures (SWXC, OA, WXC) and connections (ODUj, ODUk, ODUi, Link, Physical link). + +**Figure III.6 – Setting up ODUj network connection between NEs E and H to establish an ODUi link between the same NEs** + +Figure III.7 illustrates the set-up of an ODU0 or ODUflex subnetwork connection between port X on NE A and port Y on NE H using the topology created in the previous steps illustrated above. This ODU0/flex subnetwork connection is created after creating ODU connection points in NEs A, E and H, setting up an ODU0/flex matrix connection in NEs A, E and H between those connection points and setting up an ODU0/flex link connection in ODUj link A-E and ODUi link E-H between those connection points. + +![Diagram showing the setup of an ODU0 or ODUflex SNC between NEs A and H. It illustrates the path through various network elements (SWXC, OA, WXC) and the corresponding optical layers (ODUj, ODUk, OCh, OTS).](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +The diagram illustrates the configuration of an ODU0 or ODUflex subnetwork connection (SNC) between Network Elements (NEs) A and H. The path is established through a series of nodes, each with specific internal components and interfaces. + +- NE A (SWXC Type I):** Contains interfaces I1 and n.m. It is connected to NE B via an ODUj link. +- NE B (OA):** Contains two 'n' interfaces. It is connected to NE C via an ODUj link. +- NE C (WXC):** Contains two 'n.m' interfaces. It is connected to NE D via an ODUj link. +- NE D (WXC):** Contains two 'n.m' interfaces. It is connected to NE E via an ODUj link. +- NE E (SWXC Type I):** Contains interfaces n.m, I1, I3, and n.m. It is connected to NE F via an ODUj link. +- NE F (WXC):** Contains two 'n.m' interfaces. It is connected to NE G via an ODUi link. +- NE G (SWXC Type III):** Contains interfaces n.m, I1, I1, and nr.m. A note indicates "ODU0/flex not supported". It is connected to NE H via an ODUj link. +- NE H (SWXC Type III):** Contains interfaces nr.m, I3, I, and n.m. It is the termination point for the connection at node Y. + +The connection path is highlighted in green, showing the flow of ODUj and ODUi links. Below the main path, the diagram shows the underlying optical layers: ODUk links, OCh (Optical Channel), and OTS (Optical Transport Section) layers, which are supported by physical links. The text "Set up of ODU0 or ODUflex SNC between A and H: 3 matrix, 1 ODUjlink and 1 ODUi link connections" is present at the top. + +Diagram showing the setup of an ODU0 or ODUflex SNC between NEs A and H. It illustrates the path through various network elements (SWXC, OA, WXC) and the corresponding optical layers (ODUj, ODUk, OCh, OTS). + +Figure III.7 – Setting up an ODU0 or ODUflex subnetwork connection between NEs A and H + +# Appendix IV + +## Multi-layer OTM-n network node interface + +(This appendix does not form an integral part of this Recommendation.) + +Figure IV.1 illustrates a layer stack supported by a multi-layer OTM-n network node interface. It represents a subset of the options supported by [ITU-T G.709], [ITU-T G.707], [ITU-T G.802.1] and [ITU-T G.812]. The options listed here are preferable to enhance interworking capabilities; for other options, future study is required. + +![Diagram of the Multi-layer OTM-n network node interface layer stack.](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +The diagram illustrates the layer stack for a multi-layer OTM-n network node interface. At the top is a pink block labeled 'Clients'. Below this, a large yellow block contains several sub-layers: 'S-EC' (Service Ethernet Connection) and 'B-EC' (Backbone Ethernet Connection) are on the left; 'PW' (Packet Weight) is in the center; 'Service - LSP' (Service Label Switched Path) is on the right, with 'Sm' (lower order VC-m layer) and 'Sn' (higher order VC-n layer) stacked above it. Below 'Service - LSP' are 'MS' (Multiplex Section) and 'RS' (Regenerator Section). In the center of the yellow block is 'Transport - LSP'. Below the yellow block is a yellow block labeled 'LO ODU' (Lower Order Optical Data Unit), which contains a green block labeled 'HO ODU' (Higher Order Optical Data Unit). Below the LO ODU block is a yellow block labeled 'OTU' (Optical Transport Unit). At the bottom, the interface is divided into two sections: 'OTM-n' on the left, containing 'Och' (Optical Channel), 'OMS' (Optical Multiplex Section), and 'OTS' (Optical Transport Section); and 'OTM-nr' on the right, containing 'OPS' (Optical Payload Section). + +Diagram of the Multi-layer OTM-n network node interface layer stack. + +S-EC: Service Ethernet Connection; B-EC: Backbone Ethernet Connection; +Sm: lower order VC-m layer; Sn: higher order VC-n layer; +MS: Multiplex Section; RS: Regenerator Section + +Figure IV.1 – Multi-layer OTM-n network node interface + +# Appendix V + +## Converged packet and optical transport equipment type + +(This appendix does not form an integral part of this Recommendation.) + +![Diagram of converged packet and optical transport equipment type showing various interfaces and connections.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram illustrates the architecture of converged packet and optical transport equipment. At the top, various user interfaces are shown: two CBR UNI, two Packet UNI, one SDH NNI, and one PDH CBR UNI. The two Packet UNI units connect to a central oval labeled 'Packet\_C'. The SDH NNI and PDH CBR UNI connect to an oval labeled 'Sn\_C'. Below 'Packet\_C' is a rectangular block labeled 'Packet NNI with mapping into ODU'. Below 'Sn\_C' is a rectangular block labeled 'SDH NNI with mapping into ODU'. Both of these blocks connect to a large oval labeled 'ODU\_C'. From 'ODU\_C', lines connect to four rectangular blocks labeled 'I-NNI type 2', 'I-NNI type 1', 'E-NNI type 2', and 'E-NNI type 1'. Each of these four blocks has multiple lines connecting to a central oval labeled 'OCh\_C'. At the bottom, four rectangular blocks labeled 'OTN/WDM physical layer' are connected to 'OCh\_C', each via a multi-colored line representing multiple wavelengths. + +Diagram of converged packet and optical transport equipment type showing various interfaces and connections. + +Figure V.1 – Converged packet and optical transport equipment type + +The Packet\_C could be Ethernet connection function ETH\_C as described in [ITU-T G.8021] or MPLS-TP connection function MT\_C as described in [ITU-T G.8121]. The Sn\_C is SDH cross-connection function as described in [ITU-T G.783]. + +The Packet UNI/NNI could be Ethernet UNI/NNI as described in [ITU-T G.8012.1] or MPLS-TP UNI/NNI as described in [ITU-T G.8112]. The SDH NNI is defined in [ITU-T G.707], and the PDH CBR interface is defined in [ITU-T G.703]; PDH client support is a requirement of SDH functionality in such a converged packet and optical transport equipment. + + + +# 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.799.1-201607-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9f15ba8728564f2c1c3fead09ed15072fb17203 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94a1485bb2ba331ad86b349f1cceaf5e6d8ab5d9a721ab53d25dbb77798cd506 +size 34057 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb4044f5f4ebe3ecc943684e09ad83771031df1 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb9cbba90ec25614ed2e5af6adda526e23b53c19cc5159cabeb2bb01ac1252f +size 71456 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee61c15fb914dd7d4bced26b332de5bc257ab3a7 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c861e39df203186e34c7f361e4529c9911d272ba682d62ff5ed662812a9df5f +size 94460 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..250ea6fa509d1972fb4a288353aeb2fcb5af8a1b --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8052adf881128394cc08e53238963d578171e32d318a14bfe1963bf2e713b35 +size 74613 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59c23ddbddfb78bf6720c534bf2b249ff1146ba8 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:051c40c84ec158fa0d7e57ddd4578e06bb1f8823cc346a6506daf5004a5d0a48 +size 30623 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81d4c7b006b8fe8d730121270f16428908c398f4 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/724c7777b608e53be38b12b6fb3c43bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:887e2f72d1786e6dab4c6be4fdceebf3735313b48b5ee002738da51dd62f7179 +size 88681 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b220213003fb011ecbd5dfbe4e277f50b451d0f --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b09586c8f7dd1bc882c4d99645cfb86adade4f80c096191ecd5c413abd683af +size 51512 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76aef62abd47c554463d822d5ea8bbd421da3a0c --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c21c1023c0ace3c4723c4ab1bd2ec349b7343589f678bd204cc1f9fba038552b +size 21884 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3addf4cf6dc84e01534977eb626ba718fa82e2e6 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb7158d2c223baba666066aaa2841d6d6788fd855a59cec4914a445526479ed6 +size 45013 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32adcd5e9aef36266c1433e49ed30ea3230f6171 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:047525cd9a22bb68d20a047f9d8d72c59307d557c2e89347444770e76ee77ed9 +size 13295 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..695e511c817636e8b11f2f73002a185950da769c --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7645ff98594ad5139f84e596dbaf32e0f60e81f801b3042226133f2d6e9a1cc9 +size 66966 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efdd41b51f17b99ea38a51270f3da1682cd00e72 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58fbcdc850d58939ebf8885a7b2fec5abf838a18e0b6903b3ba5fe44f7f6f370 +size 21621 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4980949ee7a7914fd5058ec94ceb6f0132871a0c --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38c2c240114ca358a35b69bf596fd451a4df7aa22a73ccfc343c4e50de9b53a5 +size 6961 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9771840258f3edd85f2304593ed1480d970c2a20 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47b74091279c2c21bf5e46060eb8480a7817a0400a986c50be2284b34bdc2c36 +size 54376 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.799.1-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d1013c5f8b9bf097c87399356ff5eb97ee57926 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25a81e17e6553ce36f516d40ec64c5076c23590e50cac95a027a8fc74295ffd9 +size 76190 diff --git a/marked/G/T-REC-G.799.1-201607-I_PDF-E/raw.md b/marked/G/T-REC-G.799.1-201607-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bd43e08caac6c57cdd0320ad1efc7534e335ead1 --- /dev/null +++ b/marked/G/T-REC-G.799.1-201607-I_PDF-E/raw.md @@ -0,0 +1,1426 @@ + + +**ITU-T** + +**G.799.1/Y.1451.1** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(07/2016) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital terminal equipments – Other terminal equipment + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS +AND NEXT-GENERATION NETWORKS, INTERNET OF +THINGS AND SMART CITIES + +Internet protocol aspects – Interworking + +--- + +**Functionality and interface specifications for +GSTN transport network equipment for +interconnecting GSTN and IP networks** + +Recommendation ITU-T G.799.1/Y.1451.1 + +![ITU logo: International Telecommunication Union](d3294dc879b451b369c0b06f42e9b39f_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue, with the full name 'International Telecommunication Union' written in smaller blue text to the right. + +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 | +| 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 Recom.* + +## Recommendation ITU-T G.799.1/Y.1451.1 + +## Functionality and interface specifications for GSTN transport network equipment for interconnecting GSTN and IP networks + +## Summary + +Voice and voiceband traffic in international networks has traditionally been transported by circuit switched systems and equipment. With the advent of the networks optimized for the transport of Internet protocol (IP), and as a result of its considerable growth and pervasive nature, more and more voice traffic is expected to be carried over IP networks. + +Given that voice and voiceband services remain a significant part of telecommunications, there is a need to ensure a high quality of service for voice carried in part, or wholly, via IP. This Recommendation defines interfaces and functionality for equipment (e.g., GSTN to IP gateway, vehicle gateway and integrated access devices) that interconnect GSTN networks at the TDM interface and networks optimized for the transport of IP, such that they will provide the degree of voice quality and interoperability required. + +This revision provides updated references and clarify its applicability to vehicle gateway and integrated access devices. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.799.1/Y.1451.1 | 2004-06-13 | 15 | 11.1002/1000/7330 | +| 2.0 | ITU-T G.799.1/Y.1451.1 | 2016-07-14 | 16 | 11.1002/1000/12898 | + +## Keywords + +Bearer interface, echo canceller, end-to-end transmission performance, fax over IP, gateway, integrated access devices (IAD), Internet gateway, Internet protocol, IP gateway, media gateway, media gateway controller, quality of service, signalling interface, speech coding, signalling interface, TDM, TDM-IP gateway, TIGIN, VoIP, vehicle gateway, voice gateway, voice over IP, voice quality. + +--- + +\* 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 2016 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|---------------------------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Terms and definitions ..... | 5 | +| 3.1 | Terms defined elsewhere ..... | 5 | +| 3.2 | Terms defined in this Recommendation..... | 5 | +| 4 | Abbreviations and acronyms ..... | 6 | +| 5 | Conventions ..... | 8 | +| 6 | General description of GSTN transport network equipment for interconnecting GSTN and IP networks (TIGIN) ..... | 8 | +| 7 | Interfaces..... | 9 | +| 7.1 | IP bearer interfaces ..... | 10 | +| 7.2 | GSTN (TDM) bearer interfaces..... | 11 | +| 7.3 | TIGIN control interfaces ..... | 12 | +| 7.4 | TDM signalling interface ..... | 14 | +| 7.5 | Management interface ..... | 15 | +| 8 | TIGIN functionality ..... | 15 | +| 8.1 | Signal processing functions ..... | 15 | +| 8.2 | Speech quality ..... | 20 | +| 8.3 | Switching..... | 22 | +| 8.4 | Clock recovery and synchronization ..... | 22 | +| 8.5 | Security..... | 22 | +| 8.6 | Additional features ..... | 23 | +| 8.7 | Management functions and management system interfaces ..... | 23 | +| | Appendix I – Overview of the location of TIGIN gateways in end-to-end connections ..... | 29 | +| | Appendix II – Further information on performance/interworking and synchronization ..... | 31 | +| II.1 | Performance/interworking..... | 31 | +| II.2 | RTP timestamps..... | 31 | +| | Appendix III – TIGIN equipment arrangements..... | 32 | +| | Appendix IV – Mapping of E-model (ITU-T G.107) parameters from IETF RFC 3611 metrics and determining R-factor ..... | 34 | +| IV.1 | The E-model ..... | 34 | +| IV.2 | Parameters related to delay..... | 35 | +| IV.3 | Parameters related to packet loss..... | 35 | +| IV.4 | Parameters related to noise ..... | 36 | +| IV.5 | Parameters related to signal level and loudness ..... | 36 | +| IV.6 | Parameters related to Echo ..... | 36 | +| IV.7 | Calculating R, MOS-LQ and MOS-CQ values ..... | 36 | + +Bibliography..... 38 + +## Recommendation ITU-T G.799.1/Y.1451.1 + +## Functionality and interface specifications for GSTN transport network equipment for interconnecting GSTN and IP networks + +# 1 Scope + +This Recommendation covers the requirements of equipment that interconnects GSTN networks at the TDM interface and networks optimized for the transport of IP (e.g., GSTN to IP gateway, vehicle gateway and integrated access devices). Such equipment is referred to in this Recommendation as a TIGIN gateway. This Recommendation describes functionality such as voiceband coding and echo control, transport interfaces, signalling interfaces, and OA&M interfaces of these devices. Support is provided for calls from IP to GSTN, GSTN to IP, IP to IP and GSTN to GSTN. While such TIGIN gateways may support multimedia traffic and remote access server (RAS) functionality, this Recommendation covers only voice, voiceband data, facsimile, narrow-band digital data, address and signalling tones. Support of other media such as digital data and video are outside the scope of this Recommendation. + +This Recommendation describes bearer and signalling-related aspects of a TDM to IP interworking media gateway. It does not describe the requirements on a media gateway controller, with the exception that the MGC is required to provide ITU-T Q.115.1 echo control logic. This Recommendation does not define any new protocols or network architectures, but rather refers to existing protocols and architectures. It also does not specify a level of performance, as this will be covered by other Recommendations referenced by this Recommendation. Operation and management procedures are outside the scope of this Recommendation. + +TIGIN gateways are assumed to support bulk interconnection between GSTN and IP networks. They are considered to be a trunking and not an access gateway. Support of asynchronous transfer mode (ATM) on the GSTN interface is not included in 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.109] Recommendation ITU-T G.109 (1999), *Definition of categories of speech transmission quality*. +- [ITU-T G.114] Recommendation ITU-T G.114 (2003), *One-way transmission time*. +- [ITU-T G.168] Recommendation ITU-T G.168 (2015), *Digital network echo cancellers*. +- [ITU-T G.177] Recommendation ITU-T G.177 (1999), *Transmission planning for voiceband services over hybrid Internet/PSTN connections*. +- [ITU-T G.701] Recommendation ITU-T G.701 (1993), *Vocabulary of digital transmission and multiplexing and pulse code modulation (PCM) terms*. +- [ITU-T G.703] Recommendation ITU-T G.703 (2016), *Physical/electrical characteristics of hierarchical digital interfaces*. + +- [ITU-T G.704] Recommendation ITU-T G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels.* +- [ITU-T G.707] Recommendation ITU-T G.707/Y.1322 (2007), *Network node interface for the synchronous digital hierarchy (SDH).* +- [ITU-T G.711] Recommendation ITU-T G.711 (1988), *Pulse code modulation (PCM) of voice frequencies.* +- [ITU-T G.711ApI] Recommendation ITU-T G.711 Appendix I (1999), *A high quality low-complexity algorithm for packet loss concealment with G.711.* +- [ITU-T G.711-ApII] Recommendation ITU-T G.711 Appendix II (2000), *A comfort noise payload definition for ITU-T G.711 use in packet-based multimedia communication systems.* +- [ITU-T G.723.1] Recommendation ITU-T G.723.1 (2006), *Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s.* +- [ITU-T G.723.1A] Recommendation ITU-T G.723.1 Annex A (1996), *Silence compression scheme.* +- [ITU-T G.726] Recommendation ITU-T G.726 (1990), *40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM).* +- [ITU-T G.727] Recommendation ITU-T G.727 (1990), *5-, 4-, 3- and 2-bit/sample embedded adaptive differential pulse code modulation (ADPCM).* +- [ITU-T G.728] Recommendation ITU-T G.728 (1992), *Coding of speech at 16 kbit/s using low-delay code excited linear prediction.* +- [ITU-T G.728A] Recommendation ITU-T G.728 Annex I (1999), *Frame or packet loss concealment for the LD-CELP decoder.* +- [ITU-T G.729] Recommendation ITU-T G.729 (2012), *Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear prediction (CS-ACELP).* +- [ITU-T G.729A] Recommendation ITU-T G.729 Annex A (1996), *Reduced complexity 8 kbit/s CS-ACELP speech codec.* +- [ITU-T G.729B] Recommendation ITU-T G.729 Annex B (1996), *A silence compression scheme for G.729 optimized for terminals conforming to Recommendation V.70.* +- [ITU-T G.784] Recommendation ITU-T G.784 (2008), *Management aspects of synchronous digital hierarchy (SDH) transport network elements.* +- [ITU-T G.811] Recommendation ITU-T G.811 (1997), *Timing characteristics of primary reference clocks.* +- [ITU-T G.813] Recommendation ITU-T G.813 (2003), *Timing characteristics of SDH equipment slave clocks (SEC).* +- [ITU-T G.823] Recommendation ITU-T G.823 (2000), *The control of jitter and wander within digital networks which are based on the 2048 kbit/s hierarchy.* +- [ITU-T G.824] Recommendation ITU-T G.824 (2000), *The control of jitter and wander within digital networks which are based on the 1544 kbit/s hierarchy.* +- [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.957] Recommendation ITU-T G.957 (2006), *Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.* +- [ITU-T H.248.1] Recommendation ITU-T H.248.1 (2013), *Gateway control protocol: Version 3.* +- [ITU-T H.248.4] Recommendation ITU-T H.248.4 (2009), *Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP).* +- [ITU-T H.248.7] Recommendation ITU-T H.248.7 (2004), *Gateway control protocol: Generic announcement package.* +- [ITU-T H.248.10] Recommendation ITU-T H.248.10 (2001), *Gateway control protocol: Media gateway resource congestion handling package.* +- [ITU-T H.248.11] Recommendation ITU-T H.248.11 (2013), *Gateway control protocol: Media gateway overload control package.* +- [ITU-T H.248.25] Recommendation ITU-T H.248.25 (2013), *Gateway control protocol: Basic CAS packages.* +- [ITU-T H.248.30] Recommendation ITU-T H.248.30 (2007), *Gateway control protocol: RTCP extended performance metrics packages.* +- [ITU-T M.3100] Recommendation ITU-T M.3100 (2005), *Generic network information model.* +- [ITU-T P.501] Recommendation ITU-T P.501 (2012), *Test signals for use in telephonometry.* +- [ITU-T P.502] Recommendation ITU-T P.502 (2000), *Objective test methods for speech communication systems using complex test signals.* +- [ITU-T P.862] Recommendation ITU-T P.862 (2001), *Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs.* +- [ITU-T Q.52] Recommendation ITU-T Q.52 (2001), *Signalling between international switching centres and stand-alone echo control devices.* +- [ITU-T Q.55] Recommendation ITU-T Q.55 (1999), *Signalling between signal processing network equipments (SPNE) and international switching centres (ISC).* +- [ITU-T Q.115.0] Recommendation ITU-T Q.115.0 (2002), *Protocols for the control of signal processing network elements and functions.* +- [ITU-T Q.115.1] Recommendation ITU-T Q.115.1 (2002), *Logic for the control of echo control devices and functions.* +- [ITU-T Q.310] Recommendations ITU-T Q.310-Q.332 (1988), *Specifications of Signalling System R1.* +- [ITU-T Q.400] Recommendations ITU-T Q.400-Q.490 (1988), *Specifications of Signalling System R2.* +- [ITU-T Q.701] Recommendation ITU-T Q.701 (1993), *Functional description of the message transfer part (MTP) of Signalling System No. 7.* +- [ITU-T Q.702] Recommendation ITU-T Q.702 (1988), *Signalling data link.* +- [ITU-T Q.703] Recommendation ITU-T Q.703 (1996), *Signalling link.* + +- [ITU-T Q.704] Recommendation ITU-T Q.704 (1996), *Signalling network functions and messages*. +- [ITU-T T.38] Recommendation ITU-T T.38 (2015), *Procedures for real-time Group 3 facsimile communication over IP networks*. +- [ITU-T T.120] Recommendation ITU-T T.120 (2007), *Data protocols for multimedia conferencing*. +- [ITU-T V.18] Recommendation ITU-T V.18 (2000), *Operational and interworking requirements for DCEs operating in the text telephone mode*. +- [ITU-T V.150.1] Recommendation ITU-T V.150.1 (2003), *Modem-over-IP networks: Procedures for the end-to-end connection of V-series DCEs*. +- [ITU-T X.509] Recommendation ITU-T X.509 (2012) | ISO/IEC 9594-8:2014, *Information technology – Open Systems Interconnection – The Directory: Public-key and attribute certificate frameworks*. +- [ANSI T1.105.06] ANSI T1.105.06-2002, *Synchronous Optical Network (SONET) – Physical Layer Specifications*. +- [ANSI T1.107] ANSI T1.107-2002, *Digital Hierarchy – Formats Specifications*. +- [ETSI TS 128 062] ETSI TS 128 062 (2010-01), *Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3*. +- [IETF RFC 768] IETF RFC 768 (1980), *User Datagram Protocol*. +- [IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol – DARPA Internet Program Protocol Specification*. +- [IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol: DARPA Internet Program Protocol Specification*. +- [IETF RFC 919] IETF RFC 919 (1984), *Broadcasting Internet Datagrams*. +- [IETF RFC 950] IETF RFC 950 (1985), *Internet Standard Subnetting Procedure*. +- [IETF RFC 2401] IETF RFC 2401 (1998), *Security Architecture for the Internet Protocol*. +- [IETF RFC 2406] IETF RFC 2406 (1998), *IP Encapsulating Security Payload (ESP)*. +- [IETF RFC 2409] IETF RFC 2409 (1998), *The Internet Key Exchange*. +- [IETF RFC 2579] IETF RFC 2579 (1999), *Textual Conventions for SMIv2*. +- [IETF RFC 2719] IETF RFC 2719 (1999), *Framework Architecture for Signalling Transport*. +- [IETF RFC 2833] IETF RFC 2833 (2000), *RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals*. +- [IETF RFC 2960] IETF RFC 2960 (2000), *Stream Control Transmission Protocol*. +- [IETF RFC 3280] IETF RFC 3280 (2002), *Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile*. +- [IETF RFC 3309] IETF RFC 3309 (2002), *Stream Control Transmission Protocol (SCTP) Checksum Change*. +- [IETF RFC 3331] IETF RFC 3331 (2002), *Signalling System 7 (SS7) Message Transfer Part 2 (MTP2) – User Adaptation Layer*. +- [IETF RFC 3332] IETF RFC 3332 (2002), *Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)*. + +| | | +|-----------------|-------------------------------------------------------------------------------------| +| [IETF RFC 3550] | IETF RFC 3550 (2003), RTP: A Transport Protocol for Real-Time Applications . | +| [IETF RFC 3611] | IETF RFC 3611 (2003), RTP Control Protocol Extended Reports (RTCP XR) . | +| [TIA/EIA-895-A] | TIA/EIA-895-A (2002), CDMA Tandem Free Operation . | + +## 3 Terms and definitions + +### 3.1 Terms defined elsewhere + +This Recommendation uses the following term defined elsewhere: + +**3.1.1 vehicle gateway** [b-ITU-T F.749.1]: A vehicle gateway is a device in a vehicle that enables communications between a device in the vehicle and another device which may be physically located either inside the vehicle or outside the vehicle (e.g., roadside station, cloud-based server, etc.). A vehicle gateway provides standardized interfaces and protocols, communications across heterogeneous networks, optimized network selection based on application needs and network QoS, arbitration and integration of network communications, security and switching network connections to maintain service continuity. + +### 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +For terms and definitions not appearing in this clause, see [ITU-T G.701] (1993), *Vocabulary of digital transmission and multiplexing, and pulse code modulation (PCM) terms*. + +**3.2.1 access gateway**: A type of gateway that provides a user-network interface (UNI) such as integrated services digital network (ISDN). + +**3.2.2 general switched telephone network (GSTN)**: This network includes ATM, PSTN, ISDN, wireless networks and private networks. + +**3.2.3 media gateway (MG)**: The media gateway converts media format provided in one type of network to the format required in another type of network. For example, a MG could terminate bearer channels from a switched circuit network (e.g., DS0s) and media streams from a packet network (e.g., RTP streams in an IP network). This gateway may be capable of processing audio, video and T.120 multimedia signals alone or in any combination, and will be capable of full duplex media format translations. The MG may also play audio/video messages and performs other interactive voice response (IVR) functions, or may perform media conferencing. For the purpose of this Recommendation, the term media gateway refers to a voice gateway. + +**3.2.4 media gateway controller (MGC)**: Controls the parts of the call state that pertain to connection control for media channels in a media gateway. + +**3.2.5 media gateway control (Megaco)**: The term Megaco is the IETF name for [ITU-T H.248.1]. Megaco is defined in [b-IETF RFC 3525]. The protocol defined in [b-IETF RFC 3525] is common text with [ITU-T H.248.1] Version 1. However, the latest version is ITU-T H.248.1 Version 2 which is not published as an IETF RFC. When used in this Recommendation, Megaco is meant to be synonymous with the protocol defined in [ITU-T H.248.1] Version 2 and is referred to throughout the Recommendation as "ITU-T H.248/Megaco". + +**3.2.6 signalling gateway (SG)**: A signalling gateway contains the SCN signalling interface that terminates SS7 or other signalling links where the call control channels are separated from bearer channels. + +**3.2.7 simple packet relay transport (SPRT)**: A transport protocol defined in [ITU-T V.150.1]. + +**3.2.8 TIGIN gateway:** A voice gateway complying with this Recommendation. + +**3.2.9 trunking gateway:** A gateway between an SCN network and packet network that typically terminates a large number of digital circuits. + +**3.2.10 UDP transport layer (UDPTL):** A transport protocol defined in [ITU-T T.38]. + +**3.2.11 voiceband data mode (VBD mode):** A mode of operation characterized by use of a codec (e.g., ITU-T G.711) that passes voiceband modulated signals with minimal distortion, has constant end-to-end latency, disables voice activity detection, comfort noise generation and any DC removal filters that may be integral with the speech encoder. + +**3.2.12 voice gateway (VG):** A voice gateway is a subset of a gateway that deals with voice and voiceband traffic only, and not data or video traffic. + +## 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| CAS | Channel Associated Signalling | +| CDMA | Code Division Multiple Access | +| DiffServ | Differentiated Services | +| DS0 | Digital Signal level 0 | +| DS1 | Digital Signal level 1 | +| DS3 | Digital Signal level 3 | +| DTMF | Dual Tone Multi-Frequency | +| DTX | Discontinuous Transmission | +| E11 (T1) | Digital interface signal 1544 kbit/s (see [ITU-T G.703]) | +| E12 (E1) | Digital interface signal 2048 kbit/s (see [ITU-T G.703]) | +| E32 (T3) | Digital interface signal 44 736 kbit/s (see [ITU-T G.703]) | +| E31 (E3) | Digital interface signal 34 368 kbit/s (see [ITU-T G.703]) | +| ESP | Encapsulating Security Payload | +| FAX | Facsimile | +| GSTN | General Switched Telephone Network | +| IAD | Integrated Access Devices | +| IETF | Internet Engineering Task Force | +| IKE | Internet Key Exchange | +| IP | Internet Protocol | +| ISDN | Integrated Services Digital Network | +| ITU | International Telecommunication Union | +| IVR | Interactive Voice Response | +| M2UA | A protocol, as defined in [IETF RFC 3331], for the backhauling of Signalling System 7 Message Transfer Part 2 (SS7 MTP2) User signalling messages over IP using the Stream Control Transmission Protocol (SCTP). | + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M3UA | A protocol, as defined in [IETF RFC 3332], for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the stream control transmission protocol. | +| MF | Multi-Frequency | +| MG | Media Gateway | +| MGC | Media Gateway Controller | +| MR | Modem Relay | +| MTP | Message Transfer Part | +| NAT | Network Address Translation | +| OC3 | Optical Carrier level 3 | +| OC12 | Optical Carrier level 12 | +| OC48 | Optical Carrier level 48 | +| OC192 | Optical Carrier level 192 | +| PCC | Per Call Control | +| PCM | Pulse Code Modulation | +| PDH | Plesiochronous Digital Hierarchy | +| PPP | Point-to-Point Protocol | +| PSTN | Public Switched Telephone Network | +| QoS | Quality of Service | +| RAS | Remote Access Server | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SCN | Switched Circuit Network | +| SCTP | Stream Control Transmission Protocol | +| SDH | Synchronous Digital Hierarchy | +| SG | Signalling Gateway | +| SID | Silence Insertion Descriptor | +| SIGTRAN | Signalling Transport | +| SNMP | Simple Network Management Protocol | +| SONET | Synchronous Optical Network | +| SPRT | Simple Packet Relay Transport | +| SS7 | Signalling System No. 7 | +| STM1 | Synchronous Transport Module 1 | +| STM4 | Synchronous Transport Module 4 | +| STM16 | Synchronous Transport Module 16 | +| STM64 | Synchronous Transport Module 64 | +| TCP | Transmission Control Protocol | + +| | | +|-------|----------------------------------------------------------------------| +| TDM | Time Division Multiplex(ing) | +| TFO | Tandem Free Operation | +| TIGIN | Transport Network Equipment for Interconnecting GSTN and IP Networks | +| TMN | Telecommunication Management Network | +| UDP | User Datagram Protocol | +| UDPTL | Facsimile UDP Transport Layer Protocol | +| VBD | Voiceband Data | +| VG | Voice Gateway | +| VoIP | Voice over IP | + +## 5 Conventions + +In order to be compliant with this Recommendation, an implementation must provide functionality that is defined as mandatory. The words "shall" and "must", and their negatives, "shall not" and "must not" are used to express mandatory provisions. + +Compliance with this Recommendation is achieved only when all mandatory provisions are met. However, the inclusion of mandatory provisions in a Recommendation does not imply, of itself, that compliance with the Recommendation is required of any party. + +## 6 General description of GSTN transport network equipment for interconnecting GSTN and IP networks (TIGIN) + +This Recommendation covers the requirements of equipment that interconnects general switched telephone network (GSTN) networks and networks optimized for the transport of Internet protocol (IP). TIGIN gateway is a physical entity that comprises the voice and voiceband data-related part of the media gateway function and, in some cases, the signalling gateway function as described in the decomposed gateway architecture ([ITU-T H.248.1]). The mapping of the functional entities to the physical entity is shown in Figure 1. + +![Entity relationship diagram showing functional and physical planes. Functional plane contains Signalling gateway, Media gateway controller, and Media gateway. Physical plane contains TIGIN GW. Relations r1 and r2 connect functional entities. Mappings connect functional entities to the physical entity.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +The diagram illustrates the relationship between functional and physical planes in a TIGIN gateway architecture. The **Functional plane** (top) contains three entities: **Signalling gateway**, **Media gateway controller**, and **Media gateway**. A solid line labeled **r1** connects the Signalling gateway and the Media gateway controller. A solid line labeled **r2** connects the Media gateway controller and the Media gateway. The **Physical plane** (bottom) contains the **TIGIN GW** entity. Dashed lines represent mappings from the functional entities to the physical entity: one from the Signalling gateway, one from the Media gateway controller, and one from the Media gateway, all pointing to the TIGIN GW. A legend at the bottom left indicates that **rn** represents a **Relation** and a dashed line represents a **Mapping**. The document code **G.799.1-Y.1451.1(16)\_F01** is shown in the bottom right. + +Entity relationship diagram showing functional and physical planes. Functional plane contains Signalling gateway, Media gateway controller, and Media gateway. Physical plane contains TIGIN GW. Relations r1 and r2 connect functional entities. Mappings connect functional entities to the physical entity. + +**Figure 1 – Entity relationship diagram** + +In practice, a TIGIN gateway may be composed of multiple pieces of equipment, each with specialized functions, such as signalling interfaces, voice compression/decompression, packetization, etc. Figure 2 illustrates some of the functions performed in a gateway. This Recommendation does not specify how these functions are to be performed, nor does it specify the specific interconnections which may be implemented between functions. It is recognized that the + +functions of a signalling gateway may be combined with those of a TIGIN gateway in the same physical device. In this situation, certain interfaces described in this Recommendation may not be present. This Recommendation does not describe the requirements on a media gateway controller, with the exception that the media gateway controller (MGC) is required to provide ITU-T Q.115.1 echo control logic. + +The TIGIN gateway supports network configurations with SS7-associated signalling on time division multiplex(ing) (TDM) interface. In network configurations with quasi-associated signalling, a stand-alone signalling gateway, as shown in Figure 3, is required. The use of both quasi-associated signalling and associated signalling system no. 7 (SS7) signalling links within one cluster of TIGIN gateway, media gateway controller and signalling gateway is not possible due to SS7 constraints. + +![Figure 2: Illustration of functions performed by a TIGIN gateway. The diagram shows a central TIGIN gateway block with various internal functions and external interfaces. Internal functions include Call control, Bearer control, Network management system, Synchronization, Time division multiplexed network Interface, Signal processing functions, TDM signalling interface, SS7 Link, ITU-T Q.55 Echo canceller control interface, and Switching function. External interfaces include TDM bearer interface, TDM interface for MF/DTMF/CAS/SS7 signalling, ITU-T Q.55 Signalling interface, and IP bearer interface. Notes 1, 2, 3, and 4 are used to indicate optional or shared interface requirements. A backhaul signalling path via ITU-T H.248/Megaco is also shown.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) + +The diagram illustrates the internal architecture of a TIGIN gateway. At the top, three boxes labeled 'Call control', 'Bearer control', and 'Network management system' are shown, each with a 'Note 1' label above it. Below 'Call control' is a 'Synchronization' box. To the right, a 'Backhaul signalling via ITU-T H.248/Megaco (Note 1)' path connects to an 'M2UA/SCTP' box. On the left, three external interfaces are shown: 'TDM bearer interface' (Note 4), 'TDM interface for MF/DTMF/CAS/SS7 signalling' (Note 4), and 'ITU-T Q.55 Signalling interface' (Note 4). These connect to internal components: 'Time division multiplexed network Interface', 'Signal processing functions', 'TDM signalling interface' (Note 2), 'SS7 Link', and 'ITU-T Q.55 Echo canceller control interface' (Note 3). On the right, a 'Packetization / Depacketization' block connects to an 'Internet protocol interface' (Note 1), which in turn connects to an 'IP bearer interface'. At the bottom right, a 'Switching function' box is shown. The diagram is labeled 'G.799.1-Y.1451.1(16)\_F02' at the bottom right. + +Figure 2: Illustration of functions performed by a TIGIN gateway. The diagram shows a central TIGIN gateway block with various internal functions and external interfaces. Internal functions include Call control, Bearer control, Network management system, Synchronization, Time division multiplexed network Interface, Signal processing functions, TDM signalling interface, SS7 Link, ITU-T Q.55 Echo canceller control interface, and Switching function. External interfaces include TDM bearer interface, TDM interface for MF/DTMF/CAS/SS7 signalling, ITU-T Q.55 Signalling interface, and IP bearer interface. Notes 1, 2, 3, and 4 are used to indicate optional or shared interface requirements. A backhaul signalling path via ITU-T H.248/Megaco is also shown. + +NOTE 1 – These may or may not share the same external interface (see 7.1 and 7.3). + +NOTE 2 – Optional. Only required if SS7 associated or in-band (MF/DTMF/CAS) signalling on TDM interface is supported. + +NOTE 3 – Optional. + +NOTE 4 – These may or may not share the same external interface. + +**Figure 2 – Illustration of functions performed by a TIGIN gateway** + +Security functions which may be provided at several protocol layers of the various interfaces are not shown in Figure 2 above. Each of the elements included in the above block diagram is described in detail in the following clauses. + +## 7 Interfaces + +The overall relationship between the TIGIN gateway and other devices and protocols in the network is illustrated in Figure 3. + +![Figure 3: Relationship between TIGIN gateway and other devices and protocols. The diagram shows a central TIGIN gateway (ITU-T G.799.1/Y.1451.1) connected to a GSTN TDM network, a Media gateway controller (MGC), and an IP network. The TIGIN gateway has a TDM bearer interface (see 7.2) and a TDM signalling interface (see 7.4) connected to the GSTN TDM network. It has a Management interface (see 7.5) connected to the MGC. It has an IP bearer interface (see 7.1) connected to the IP network. The MGC has a TIGIN control – Per call PCC Interface (see 7.3.1) and a Signalling transport and ITU-T H.248/Megaco over IP (see 7.3) connected to the IP network. The GSTN TDM network is connected to a Signalling gateway (dotted box) which is connected to the IP network via an Alternative (see 7.3.2.2) path.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 3: Relationship between TIGIN gateway and other devices and protocols. The diagram shows a central TIGIN gateway (ITU-T G.799.1/Y.1451.1) connected to a GSTN TDM network, a Media gateway controller (MGC), and an IP network. The TIGIN gateway has a TDM bearer interface (see 7.2) and a TDM signalling interface (see 7.4) connected to the GSTN TDM network. It has a Management interface (see 7.5) connected to the MGC. It has an IP bearer interface (see 7.1) connected to the IP network. The MGC has a TIGIN control – Per call PCC Interface (see 7.3.1) and a Signalling transport and ITU-T H.248/Megaco over IP (see 7.3) connected to the IP network. The GSTN TDM network is connected to a Signalling gateway (dotted box) which is connected to the IP network via an Alternative (see 7.3.2.2) path. + +NOTE – In cases where the SS7 signalling networks consists of quasi-associated links, a separate signalling gateway is required as shown in the dotted-line box at upper left of this figure. It is not the intent of this figure to suggest the co-existence of quasi-associated and associated signalling links (see clause 7). + +**Figure 3 – Relationship between TIGIN gateway and other devices and protocols** + +The support of network address translation (NAT) and firewall traversal in networks with TIGIN gateways is for further study. + +A TIGIN gateway should implement a mechanism for differentiating quality of service (QoS) for bearer stream, call set-up signalling, per call control signalling and management control signalling. + +This can be achieved by, e.g.: + +- Physical separation of interfaces; +- DiffServ (see [b-IETF RFC 2475]); +- Separation at Layer 2 (e.g., MPLS, VLAN, ATM VCC multiplexing, etc.). + +### 7.1 IP bearer interfaces + +The IP interface block in the block diagram in Figure 2 provides the transmission facility interface for the network element to the IP network. + +Table 1 shows layers of the TIGIN IP bearer interface model. + +**Table 1 – IP bearer interface protocol layers** + +| Application | Transparent | Voice | Tones | Modem (Note 1) | | FAX (Note 1) | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|-------|-------|----------------|----------------------|-----------------------------|-------------------| +| Upper layers | RTP | | | SPRT | RTP
(VBD
mode) | UDPTL or
RTP
(Note 2) | RTP (VBD
mode) | +| Transport layers | UDP (User datagram protocol) | | | | | | | +| Network layer | IP (Internet protocol) | | | | | | | +| Lower layers | Physical and data link | | | | | | | +| NOTE 1 – See clause 8.1.5 for Modem and FAX support.
NOTE 2 – The use of real-time transport protocol (RTP) provides call statistics through RTP control protocol (RTCP) and allows a smoother transition between speech and non-speech communication in a call. | | | | | | | | + +Table 1 shows only basic stacks. Additional function for quality of service, security, header compression, etc. may be added. + +#### 7.1.1 Lower layers + +This Recommendation does not restrict the use of any lower layer protocol intended for IP packet transmission and approved by an internationally recognized standards body. + +Lower layer interface performs link protection, alarm detection and performance monitoring of the interface layers, as defined in appropriate standards. + +#### 7.1.2 IP layer + +IP protocol shall conform to [IETF RFC 791], [IETF RFC 950] and [IETF RFC 919]. + +Support of IPv6 ([b-IETF RFC 2460]) is for further study. + +IP network topology, IP packet distribution and routing protocols are not the subject of this Recommendation. + +For a given call, a TIGIN gateway shall transmit and receive packets on the same IP address. + +#### 7.1.3 Transport layer + +User datagram protocol (UDP) protocol shall be used as transport layer protocol and it shall conform to [IETF RFC 768]. For a given call, a TIGIN gateway shall include in the source UDP port field of the UDP port header of all its transmitted packets, pertaining to a particular media stream, the same UDP port number as the one announced to its peer for that media stream. + +#### 7.1.4 Upper layers + +RTP protocol is used for transparent signal transmission and for voice and tones transmission as [IETF RFC 3550] describes. [IETF RFC 3550] also defines RTP control protocol as a companion control protocol for RTP. + +### 7.2 GSTN (TDM) bearer interfaces + +The TDM interface block in the block diagram in Figure 2 provides the transmission facility interface for the network element to the GSTN network. The physical layer of the TDM bearer interface shall consist of at least one of the interface types in Table 2. Voice and voiceband coding on this interface shall conform to [ITU-T G.711]. + +**Table 2 – TDM bearer interfaces** + +| | | | | | +|------------|-------|---------------------|-------|-------------| +| Electrical | E1 | G.703, G.704 | DS1 | ANSI T1.107 | +| | E3 | G.703, G.704 | DS3 | ANSI T1.107 | +| | STM1 | G.707/Y.1322, G.703 | | | +| Optical | STM1 | G.707/Y.1322, G.957 | OC3 | ANSI T1.105 | +| | STM4 | G.707/Y.1322, G.957 | OC12 | ANSI T1.105 | +| | STM16 | G.707/Y.1322, G.957 | OC48 | ANSI T1.105 | +| | STM64 | G.707/Y.1322, G.957 | OC192 | ANSI T1.105 | + +### 7.3 TIGIN control interfaces + +#### 7.3.1 TIGIN control-per call + +Per call control (PCC) describes the interface between the TIGIN and the MGC that provides for real-time per call control of the TIGIN. The MGC is the control element that interworks between the signalling network and the TIGIN, providing the TIGIN with the real-time per-call control signals. + +The PCC protocol defines the messaging between the MGC and the TIGIN and allows for the following capabilities such as: + +- Establish, modify, and release connections within the TIGIN, including originating and terminating addresses (e.g., TDM-TDM, TDM-IP). +- Query the status of connections or resources within the TIGIN. +- Notification of call-related alarms or failures. +- Continuity check. +- Transfer of certain GSTN signalling information for multi-frequency (MF) and channel associated signalling (CAS)-based protocols carried on the TDM link. + +PCC allows the MGC to specify the internal TIGIN resources required in the bearer stream (echo control, dual tone multi-frequency (DTMF) detection, modem/fax detection, etc.). It also allows for the setting of per call features and parameters required, based on call type and interoperability needs. These parameters may include some or all of the following: + +- real-time call processing event notification, including the control of echo cancellers; +- silence suppression activation; +- comfort noise generation; +- jitter buffer size; +- selection of and/or negotiation of codec (e.g., [ITU-T G.711], [ITU-T G.723.1], [ITU-T G.729]). + +NOTE 1 – The presence of different codecs on the GSTN and IP interfaces implies performing a transcoding function (e.g., [ITU-T G.711] to [ITU-T G.729]). + +- packet size selection. + +Selection of these mechanisms will affect voice quality. See clauses 8.1, 8.2 and 8.3 for more information on this topic. + +Upon completion of a call, as specified in PCC protocols, a TIGIN shall be capable of supplying, upon request, statistics related to the call. A minimal set of statistics is listed below. These statistics can be provided using RTCP sender and receiver reports as outlined in [IETF RFC 3550]. + +- number of packets sent; +- number of octets sent; + +- number of packets received; +- number of octets received; +- average inter-arrival jitter. + +The upper layer protocol used shall conform to ITU-T H.248/Megaco. + +The IP-based PCC interface may share the same physical media as the IP bearer interface. + +The options for transport of ITU-T H.248/Megaco control protocol between MGC and the TIGIN gateway are shown in Table 3. The transport over UDP and transmission control protocol (TCP) is defined in Annex D of [ITU-T H.248.1]. + +Transport over stream control transmission protocol (SCTP) is defined in [ITU-T H.248.4]. + +**Table 3 – TIGIN control protocol layers** + +| Application | TIGIN control | | | | | +|--------------------|------------------------|--------|------------------------|-----|-----| +| Upper layers | ITU-T H.248/Megaco | | | | | +| Transport layer | SCTP | MTP L3 | M3UA
SCTP | UDP | TCP | +| Network layer | IP (Internet Protocol) | MTP L2 | IP (Internet Protocol) | | | +| Lower layers | Physical and data link | | Physical and data link | | | + +NOTE 2 – If SS7-associated signalling links are used, then TIGIN and MGC should have the same signalling point code. However, if ITU-T H.248/Megaco is used over M3UA or MTPL3, then TIGIN and MGC must have different signalling point codes. If ITU-T H.248/Megaco signalling carried over M3UA or MTPL3 is used, then the use of SS7-associated signalling links is not possible. Conversely, in a network with SS7-associated links, the use of M3UA or MTPL3 as the transport layer for ITU-T H.248/Megaco between TIGIN and MGC is, therefore, not possible. + +Note that for networks that do not provide highly reliable connections, but where highly reliable transport is required SCTP, MTP3 or M3UA over SCTP should be used. + +The protocols used in various stacks shall meet the requirements specified in the publications referenced below: + +- 1) IP protocol shall conform to [IETF RFC 791], [IETF RFC 950] and [IETF RFC 919]. +- 2) Support of IPv6 ([b-IETF RFC 2460]) is for further study. +- 3) IP network topology, IP packet distribution and routing protocols are not the subject of this Recommendation. +- 4) UDP protocol is used as transport layer protocol and it shall conform to [IETF RFC 768]. +- 5) SCTP protocol shall conform to [IETF RFC 2960] and [IETF RFC 3309]. +- 6) TCP protocol ([IETF RFC 793]) may be optionally used for non-time-critical applications. +- 7) M3UA protocol shall conform to [IETF RFC 3332]. +- 8) MTP L1 protocol shall conform to [ITU-T Q.702]. +- 9) MTP L2 protocol shall conform to [ITU-T Q.703]. +- 10) MTP L3 protocol shall conform to [ITU-T Q.704]. + +#### 7.3.2 Signalling over IP + +A TIGIN gateway should support the signalling transport (SIGTRAN) framework architecture for signalling transport over IP networks, defined by [IETF RFC 2719]. + +##### 7.3.2.1 In-band tones and signals + +A TIGIN gateway shall have the capability to detect DTMF digits and other in-band signalling tones, as defined in clause 8.1.4, and generate messages to the media gateway controller, as described in ITU-T H.248/Megaco. + +When the call control used in an IP network does not mandate an out-of-band transport of DTMF and other in-band signals, a TIGIN gateway shall support the undistorted transport of DTMF and other in-band signals across the IP network. If a TIGIN gateway is using a codec that does not support the undistorted transport of DTMF, it shall transport those events either by other means provided by that codec for undistorted transport if available, or alternatively by [IETF RFC2833], if mutually negotiated. + +##### 7.3.2.2 Support for SS7, MF, and CAS signalling + +The signalling gateway function may be integrated in the TIGIN Gateway. Its purpose is to transfer GSTN signalling information that arrives at the TDM interfaces of the TIGIN gateway to the MGC, and vice versa. + +Alternatively, the signalling interface for support of SS7 signalling may exist between the TIGIN gateway and the signalling gateway. Signalling support exists for two families of GSTN signalling, namely common channel signalling and MF/CAS-based signalling. Each case is handled in a different manner. + +###### 7.3.2.2.1 Support for signalling system no. 7 + +A TIGIN gateway shall support SS7 by one of the following methods (see Table 4): + +- Backhaul of common channel signalling using M2UA over SCTP, as described in [IETF RFC 2960] and [IETF RFC 3309]. +- Use of M3UA, as described in [IETF RFC 3332]. +- SS7 signalling transport over RTP using 64 bit/s clear channel method (for further study). + +**Table 4 – Signalling transport control protocol layers** + +| | | | +|-----------------|------------------------|------------------------| +| Upper layers | M2UA/M3UA | RTP | +| Transport layer | SCTP | UDP | +| Network layer | IP (Internet Protocol) | IP (Internet Protocol) | +| Lower layers | Physical and data link | Physical and data link | + +Note that for networks that do not provide highly reliable connections, but where highly reliable transport is required, M2UA or M3UA over SCTP should be used. + +###### 7.3.2.2.2 Support for MF and CAS-based signalling + +A TIGIN gateway should support MF and CAS-based GSTN signalling protocols using the ITU-T H.248/Megaco packages. The basic CAS packages are defined in [ITU-T H.248.25]. + +### 7.4 TDM signalling interface + +TDM signalling interfaces supported by equipment conforming to this Recommendation shall conform to national or international standards. + +### 7.5 Management interface + +Both telecommunication management network (TMN) and simple network management protocol (SNMP) management interfaces are for further study. + +## 8 TIGIN functionality + +### 8.1 Signal processing functions + +The network element supports voice-related features as described in this clause. Some or all of the voice feature functions listed in this clause may be utilized during a call. The PCC message specifies which functions shall be used on a call. + +As an example, silence suppression and comfort noise generation may be requested on a call that uses ITU-T G.711 coding. The network element, in that case, would take the GSTN data, interpret it as ITU-T G.711 coding and generate packets to the IP network using ITU-T G.711 coding only if it detects speech activity. In the reverse direction, it would receive packets from the IP network, interpret them as ITU-T G.711-encoded pulse code modulation (PCM), convert the packets into a synchronous (TDM) stream and send it to the GSTN network. During the time packets are not received it would generate comfort noise ITU-T G.711 PCM values and send it to the GSTN network. + +In addition, other signal processing features supported by the network element could include the following: + +- continuity check tone generation and detection; +- continuity check loop-back. + +Signal processing functions may affect voice quality. See clauses 7.3.1 and 8.2 for more information on this topic. + +#### 8.1.1 Echo control + +In compliance with [ITU-T G.177], a voice-over-IP connection traversing a hybrid is required to include a ITU-T G.168-compliant echo canceller. Since the echo canceller needs to have a constant delay for its echo path, it shall be placed so that the echo path is on the TDM side of the interface that includes the hybrid. + +Network operators and service providers should ensure that echo cancellation is applied in the most appropriate location for the specific configuration. The echo canceller shall be associated with the TIGIN gateway in one of three possible configurations, as outlined in the following clauses. + +It should be reinforced that all voice connections involving GSTN-to-IP interworking involving a hybrid, require echo cancellation and the network operator or service provider, choosing to utilize either configuration B, as shown in Figure 5, or C, as shown in Figure 6, should ensure that an echo canceller is provisioned on the TDM bearer side of the hybrid Internet/GSTN connection. + +##### 8.1.1.1 TIGIN internal echo control – Configuration A + +In this configuration, the echo canceller is integrated into the TIGIN gateway itself, as shown in Figure 4. With this configuration, ITU-T H.248/Megaco messages convey the echo canceller control information from the MGC to the TIGIN gateway. The TIGIN gateway then directly controls the internal echo canceller function in accordance with the messages received. For this configuration, the echo canceller function within the TIGIN gateway is required and the ITU-T Q.55/Q.52 process is optional but not used. + +![Figure 4: Echo canceller integrated into TIGIN gateway – Configuration A. This diagram shows a GSTN TDM network connected to a Signalling gateway via SS7. The Signalling gateway is connected to a Media gateway controller (MGC) which contains ITU-T Q.115.1 echo control logic. The MGC is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via ITU-T H.248/Megaco messages. The TIGIN gateway has an integrated Echo canceller function. A TDM bearer from the GSTN network enters the TIGIN gateway, and an IP bearer connects the TIGIN gateway to an IP network. An 'Echo' label with a curved arrow indicates the echo path within the TDM bearer.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +G.799.1-Y.1451(16)\_F04 + +Figure 4: Echo canceller integrated into TIGIN gateway – Configuration A. This diagram shows a GSTN TDM network connected to a Signalling gateway via SS7. The Signalling gateway is connected to a Media gateway controller (MGC) which contains ITU-T Q.115.1 echo control logic. The MGC is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via ITU-T H.248/Megaco messages. The TIGIN gateway has an integrated Echo canceller function. A TDM bearer from the GSTN network enters the TIGIN gateway, and an IP bearer connects the TIGIN gateway to an IP network. An 'Echo' label with a curved arrow indicates the echo path within the TDM bearer. + +**Figure 4 – Echo canceller integrated into TIGIN gateway – Configuration A** + +##### 8.1.1.2 TIGIN external echo control with ITU-T Q.55/Q.52 control – Configuration B + +In this configuration, the echo canceller is directly associated with and controlled by the TIGIN gateway, as shown in Figure 5. With this configuration, ITU-T H.248/Megaco messages convey the echo canceller control information from the MGC to the TIGIN gateway. The TIGIN gateway then converts the messages into appropriate protocol data units and sends them to the associated external echo canceller. The conversion processes are described in clause 8.1.1.2.1. For this configuration, the echo canceller function within the TIGIN gateway is optional but not used, and the ITU-T Q.55 process is mandatory. + +![Figure 5: TIGIN external echo control with ITU-T Q.55 control – Configuration B. This diagram shows a GSTN TDM network connected to a Signalling gateway via SS7. The Signalling gateway is connected to a Media gateway controller (MGC) which contains ITU-T Q.115.1 echo control logic. The MGC is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via ITU-T H.248/Megaco messages. The TIGIN gateway is connected to an external 'TIGIN associated echo canceller' via an ITU-T Q.55 control protocol. The TIGIN gateway also contains an ITU-T Q.55 process. A dashed box labeled 'Echo canceller association' encloses the external echo canceller and the ITU-T Q.55 control protocol. A TDM bearer from the GSTN network enters the TIGIN gateway, and an IP bearer connects the TIGIN gateway to an IP network. An 'Echo' label with a curved arrow indicates the echo path within the TDM bearer.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +G.799.1-Y.1451(16)\_F05 + +Figure 5: TIGIN external echo control with ITU-T Q.55 control – Configuration B. This diagram shows a GSTN TDM network connected to a Signalling gateway via SS7. The Signalling gateway is connected to a Media gateway controller (MGC) which contains ITU-T Q.115.1 echo control logic. The MGC is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via ITU-T H.248/Megaco messages. The TIGIN gateway is connected to an external 'TIGIN associated echo canceller' via an ITU-T Q.55 control protocol. The TIGIN gateway also contains an ITU-T Q.55 process. A dashed box labeled 'Echo canceller association' encloses the external echo canceller and the ITU-T Q.55 control protocol. A TDM bearer from the GSTN network enters the TIGIN gateway, and an IP bearer connects the TIGIN gateway to an IP network. An 'Echo' label with a curved arrow indicates the echo path within the TDM bearer. + +**Figure 5 – TIGIN external echo control with ITU-T Q.55 control – Configuration B** + +###### 8.1.1.2.1 Echo canceller control procedures + +When the echo cancellation function is not integrated into the TIGIN gateway, but is located on a TDM trunk of the gateway and is controlled by the TIGIN gateway, the following procedures shall be used. These procedures define the mapping between ITU-T H.248/Megaco messages received by + +the TIGIN gateway from the media gateway controller, and ITU-T Q.55 protocol data units transmitted to the associated external echo canceller. + +###### Echo canceller enable procedure + +When the ITU-T H.248/Megaco package responsible for controlling echo cancellers is received with the value set to "on" for a specific TDM digital signal level 0 (DS0) channel, the ITU-T Q.55 protocol data unit "enable echo cancellation for channel n", as defined in Annex H of [ITU-T Q.55], where 'n' is the DS0 channel specified by the ITU-T H.248/Megaco message, is transmitted on the ITU-T Q.55 echo control interface of the TIGIN gateway. + +###### Echo canceller disable procedure + +When the ITU-T H.248/Megaco package responsible for controlling echo cancellers is received with the value set to "off" for a specific TDM DS0 channel, the ITU-T Q.55 protocol data unit "disable echo cancellation for channel n", as defined in Annex H of [ITU-T Q.55], where 'n' is the DS0 channel specified by the ITU-T H.248/Megaco message, is transmitted on the ITU-T Q.55 echo control interface of the TIGIN gateway. + +##### 8.1.1.3 GSTN switch-associated echo control – Configuration C (Informational) + +In this configuration, the echo canceller is not directly associated with or controlled by the TIGIN gateway. Instead, the echo canceller is associated with and may be controlled by a switch in the GSTN, as shown in Figure 6. + +If the GSTN switch controls the echo canceller, it may either be controlled via a ITU-T Q.55 interface, or, via some other control mechanism. If the GSTN switch controls the associated echo canceller via ITU-T Q.55, echo control messages are generated as a result of the ITU-T Q.115.1 echo control logic information in the GSTN switch and are sent to the GSTN switch-associated echo canceller. For this configuration, while the echo canceller function and/or ITU-T Q.55 process within the TIGIN gateway may exist, they are not used. + +It shall be noted that the ITU-T Q.115.1 echo control logic in the MGC will request the disabling of a canceller associated with the TIGIN gateway, if any is present, as in this particular case, one has already been provisioned in the GSTN. + +![Diagram of Non-TIGIN-associated echo control – Configuration C. The diagram shows a Media gateway controller (MGC) with ITU-T Q.115.1 echo control logic connected to a Signalling gateway via SS7. The Signalling gateway is connected to a GSTN TDM network. Within the GSTN TDM network, there is ITU-T Q.115.1 echo control logic, an ITU-T Q.55 (or other) control process, and a GSTN switch-associated echo canceller. The ITU-T Q.55 control process is connected to the echo canceller via an ITU-T Q.55 control protocol. The echo canceller is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via a TDM bearer. The TIGIN gateway is connected to an IP network via an IP bearer. The MGC is also connected to the TIGIN gateway via ITU-T H.248/Megaco. A dashed box labeled 'Echo canceller association' contains the ITU-T Q.115.1 echo control logic, the ITU-T Q.55 control process, and the GSTN switch-associated echo canceller. The GSTN TDM network is represented by a cloud shape.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +Diagram of Non-TIGIN-associated echo control – Configuration C. The diagram shows a Media gateway controller (MGC) with ITU-T Q.115.1 echo control logic connected to a Signalling gateway via SS7. The Signalling gateway is connected to a GSTN TDM network. Within the GSTN TDM network, there is ITU-T Q.115.1 echo control logic, an ITU-T Q.55 (or other) control process, and a GSTN switch-associated echo canceller. The ITU-T Q.55 control process is connected to the echo canceller via an ITU-T Q.55 control protocol. The echo canceller is connected to a TIGIN gateway (ITU-T G.799.1/Y.1451.1) via a TDM bearer. The TIGIN gateway is connected to an IP network via an IP bearer. The MGC is also connected to the TIGIN gateway via ITU-T H.248/Megaco. A dashed box labeled 'Echo canceller association' contains the ITU-T Q.115.1 echo control logic, the ITU-T Q.55 control process, and the GSTN switch-associated echo canceller. The GSTN TDM network is represented by a cloud shape. + +Figure 6 – Non-TIGIN-associated echo control – Configuration C + +#### **8.1.2 Voice coding** + +As a minimum, a TIGIN gateway shall include a ITU-T G.711 codec (for both A and $\mu$ -laws). The default ITU-T G.711 codec (e.g., A or $\mu$ -law) shall be selected based upon the physical location of the TIGIN and mechanisms described in [ITU-T H.248.1]. + +A TIGIN gateway may optionally include codecs other than ITU-T G.711 (e.g., ITU-T G.728, G.729, G.723.1, codecs commonly used in GSM, code division multiple access - CDMA, TDMA, etc. networks). Delay caused by voice coding should be kept to a minimum (see Annex A of [ITU-T G.114] for calculation of delay figures). + +#### **8.1.3 Digital speech interpolation** + +Silence suppression and comfort noise generation can be either internal or external to the codec. + +##### **8.1.3.1 Internal silence suppression and comfort noise generation** + +###### **8.1.3.1.1 Silence suppression** + +Silence suppression shall be supported according to the speech codec used, e.g., Annex B of [ITU-T G.729] for ITU-T G.729, or Annex A of [ITU-T G.723.1] for ITU-T G.723. + +###### **8.1.3.1.2 Comfort noise generation** + +Comfort noise generation shall be supported according to the speech codec used, e.g., Appendix II of [ITU-T G.711] for ITU-T G.711, Annex B of [ITU-T G.729] for ITU-T G.729, or Annex A of [ITU-T G.723.1] for ITU-T G.723.1. + +##### **8.1.3.2 External silence suppression and comfort noise generation** + +There should be a method of ensuring synchronous reset capability between the encoder and decoder of ITU-T G.726, ITU-T G.727, ITU-T G.728 and ITU-T G.729 when external comfort noise generation is used with these codecs. In these cases, an external synchronous reset will be beneficial to voice quality, particularly at the transient from-silence-to-active-speech when the codec is used in the discontinuous transmission (DTX) condition. If generic silence insertion descriptor (SID) comfort noise insertion is used with a low bit rate coder, synchronous reset between encoder and decoder should be employed. + +#### **8.1.4 Tones and announcements** + +The following functions may be hosted by a TIGIN gateway: + +- voice announcements; +- supervisory tones; +- tone detection. + +If any of these features are provided, they shall be provided in the manner described in this clause. The following clauses describe each function in detail and give some examples of when they are required. + +##### **8.1.4.1 Voice announcements** + +Voice announcements fall into two categories: + +- fixed announcements; +- announcements with variable parts. + +Fixed announcements are used by basic public switched telephone network (PSTN) calls in circumstances where, for example, it is necessary to play a rejection announcement to a caller such as: *The number you have dialled has not been recognized, please check and try again.* + +Announcements with variable parts are often required for PSTN supplementary services where, for example, a date, time or telephone number needs to be inserted into a standard announcement e.g., for a call that has been diverted: ***Telephone number will receive your incoming calls.*** In this case, is the variable part that identifies the diverted-to telephone number. + +All voice announcements shall be controlled via ITU-T H.248/Megaco from the media gateway controller using [ITU-T H.248.7]. + +##### 8.1.4.2 Supervisory tones + +In addition to the voice announcements described in clause 8.1.4.1, a small range of supervisory tones, e.g., dial, ringing, busy, etc., need to be generated to support PSTN supplementary services. For example, these are necessary to cover supplementary service invocation confirmations such as: ***If this is incorrect press # after the dial tone .*** + +All supervisory tones shall be controlled via ITU-T H.248/Megaco from the media gateway controller using Annex E of [ITU-T H.248.1]. + +Technical characteristics of the tone generation shall conform to relevant national and international standards. + +##### 8.1.4.3 DTMF tone detection + +DTMF receivers are required to collect end-user responses for PSTN supplementary services that involve interactive dialogues. Generally, this functionality is required for intelligent network (IN) services with interactive menu dialogues, but it is also needed for some of the more basic PSTN services such as call diversion. For example, a DTMF receiver is necessary to collect the invited response to the call diversion service prompt: ***If this is incorrect press # after the dial tone.*** + +Tone detection shall be controlled via ITU-T H.248/Megaco from the media gateway controller using Annex E of [ITU-T H.248.1]. + +#### 8.1.5 Facsimile, voiceband data modem, and text telephony handling + +A TIGIN gateway shall be capable of transporting facsimile data, voiceband modem data and text telephony data defined in [ITU-T V.18] over IP networks. National preferences shall dictate which of the ITU-T V.18 modulation schemes are supported. At a minimum, a TIGIN gateway shall support facsimile, voiceband data (VBD) modem and text telephony transmission via VBD mode. A standardized mechanism for transport of this type is under study within ITU-T. + +Support for the following relay mechanisms is optional. + +If facsimile transmission is supported via facsimile relay, it shall be done by standardized mechanisms. For Group 3 facsimile equipment, ITU-T T.38 shall be used. To ensure a minimum expectation of performance, a TIGIN gateway that supports ITU-T T.38 shall support the ITU-T T.38 default and optional transitioning mechanisms defined in Annex E of [ITU-T T.38] for transitioning between voice and ITU-T T.38 states. The choice of the transitioning mechanism is made by the MGC. + +If modem transmission is supported via modem relay, it shall be done by [ITU-T V.150.1]. Note that [ITU-T V.150.1] also supports VBD mode. If [ITU-T V.150.1] is a mutually negotiated option, then VBD mode can be supported by the procedures defined by that Recommendation. + +To ensure a minimum expectation of performance, a TIGIN gateway that supports an ITU-T V.150.1 modem relay shall: + +- Only use a universal modem relay (MR) gateway type. +- Use either single or double trans-compression. + +If text transmission is supported via text relay, it shall be supported via applicable national and international standards. A standardized mechanism for transport of this type is under study within ITU-T. + +#### **8.1.6 Speech reconstruction** + +Voice coders in a TIGIN gateway should follow established rules for speech reconstruction under conditions of lost packets. Packet loss concealment techniques shall be provided for all codecs supported by the TIGIN gateway, e.g., Appendix I of [ITU-T G.711] and Annex I of [ITU-T G.728]. It should be noted that [ITU-T G.729] and [ITU-T G.723.1] have packet loss concealment capabilities embedded into their respective decoders. + +#### **8.1.7 Voice encryption** + +Methods of supporting voice encryption are for further study. + +#### **8.1.8 Distributed speech recognition and distributed speaker verification** + +Methods of supporting distributed speech recognition and distributed speaker verification are for further study. + +#### **8.1.9 Jitter buffer** + +A TIGIN gateway shall include a jitter buffer that compensates for jitter (or delay variation) introduced by the IP network. Jitter (delay variation) can occur for a number of different reasons including network congestion, queuing, etc. and, if the jitter buffer is not dimensioned properly, then voice quality degradation can result. If the jitter buffer is too small to accommodate the maximum delay experienced by some packets, then packet loss will occur. If the jitter buffer is too large, the end-to-end delay experienced by the user is increased. + +For voice traffic the jitter buffer shall be adaptive to minimize the delay while keeping packet loss rate below a reasonable limit. + +For VBD mode, the jitter buffer shall provide constant latency. For example, this may be achieved either by fixed jitter buffer, or by freezing the adaptive jitter buffer. + +The default jitter buffer settings shall be provisionable via a management interface. It shall be possible to override these settings on a per-ephemeral basis using ITU-T H.248/Megaco control via the media gateway controller. + +It should be possible to set jitter buffer parameters to support reliable transport of 64 kbit/s ISDN data. Jitter buffer requirements for supporting 64 kbit/s ISDN data are for further study. + +### **8.2 Speech quality** + +In providing the following functions, TIGIN gateway design should be optimized to minimize degradation of speech transmission performance: + +- echo cancellation; +- adaptive jitter buffering; +- packet loss concealment; +- silence suppression; +- voice activity detection; +- comfort noise generation. + +See clause 8.1.3 for handling of silence suppression and comfort noise generation. + +Support for tandem coder avoidance, other than tandem free operation (TFO), is for further study. As outlined in [ITU-T G.177], it is recommended that only one encode/decode of speech be performed, and that speech coder tandem processing be eliminated whenever possible. + +[ITU-T P.1010] provides fundamental speech transmission objectives for voice over IP (VoIP) gateways and provides references to other Recommendations which need to be taken into account for gateways to support acceptable end-to-end speech transmission performance. Additionally, [ITU-T G.177] should be followed with respect to end-to-end transmission performance and planning guidance for voiceband services. + +Note that a methodology to objectively predict and evaluate end-to-end speech quality is described in [ITU-T P.862]. Additionally, [ITU-T P.502] provides objective test methods for evaluation of speech transmission quality of terminals and speech transmission systems, and utilizes test signals defined in [ITU-T P.501]. Specific objective requirements for these methodologies are for further study. + +Definitions of categories of voice transmission quality may be found in [ITU-T G.109]. + +#### **8.2.1 TIGIN support for tandem free operation (Optional)** + +As different packet networks will be interfaced with one another, the tandeming of speech codecs operating at low to medium rates (4 to 16 kbit/s) will be very common. Because tandem speech codecs degrade speech quality, it is highly recommended that a single coded pair be used end-to-end. + +In calls where TIGIN gateways connect two transcoding mobile networks, the TIGIN gateways become in-path equipment with respect to the two networks. In order to avoid speech codecs in tandem operation and to avoid degradation of voice quality, ITU-T G.799.1/Y.1451.1 gateways could optionally support, on a call-by-call basis depending on the bandwidth available in the IP network, one or more TFO protocols such as defined in the following: + +- TIA/EIA-895-A, *CDMA Tandem Free Operation*; +- ETSI TS 128 062, *Inband Tandem Free Operation (TFO) of Speech Codecs, Stage 3 – Service Description*. + +The support for other possible TFO standards is for further study. + +The above two TFO standards were based on the same in-band signalling protocol and are intended for Wireless services over circuit-switched networks. The mechanism for supporting TFO over IP-based networks is for further study. + +#### **8.2.2 Packet size selection** + +The choice of packet size is a trade-off between transport efficiency, quality and delay. The delay associated with codec processing and packetization should be kept as short as possible. Gateways should adhere to [ITU-T G.177] in this regard. When multiple frames of coded speech are allocated to the same packet, packet loss concealment techniques become less effective and, as a result, may possibly lower end-to-end speech quality when packet loss is encountered. + +Where codec frame size permits, a TIGIN gateway shall support the packetization times of 10 and 20 ms. Otherwise, a TIGIN gateway shall support a packetization time of one frame size (e.g., 30 ms for ITU-T G.723.1). These packetization times shall be supported in both transmit and receive directions. Other packetization times may be supported and negotiated under control of ITU-T H.248.1. + +Packet size shall be an integer multiple of the codec frame length. To accomplish this objective when ITU-T G.729 or ITU-T G.729A is used, two frames per packet shall be considered as the maximum packet size. + +Similarly, ITU-T G.711 and ITU-T G.726 may be used with packet sizes of 10 ms (80 samples) or 20 ms (160 samples) to achieve this objective. + +Finally, when ITU-T G.723.1 is used, only one frame shall be included in each packet. The 7.5 ms look-ahead and the 30 ms frame size of ITU-T G.723.1 results in a combined voice buffering and + +processing delay of between 37.5 ms and 67.5 ms (depending on the computational power available), thus contributing to the difficulty of interactive communications. + +### **8.3 Switching** + +The TIGIN gateway shall provide the ability to switch telephone calls in the direction of the PSTN and in the direction of the IP network. Switch control is based on general call control and allows the establishment, modification and release of the connection within the TIGIN. The TIGIN architecture is based on separation of the logical control plane from the transport resources. The TIGIN architecture should be suitable for high availability networks, which includes non-blocking paths through the TIGIN. + +TIGIN switching functions include: + +- Providing basic cross-connect functionality between TDM and IP logical ports. +- Forwarding user information. +- Supporting a multiplicity of switching elements under the domain of a single controller. +- Providing switching element reliability. +- Replicating data for point-to-multipoint connections. +- Providing a common switch control interface to one or more controllers. + +### **8.4 Clock recovery and synchronization** + +A TIGIN gateway requires a clock recovery circuit that allows synchronization to a reference clock and generation of a precise local clock. This synchronization circuit shall support primary and secondary synchronization inputs for reference clocks, and may support additional reference inputs. + +A TIGIN gateway node clock shall be traceable to an external [ITU-T G.811] source. This may be achieved using external clock ports or traffic ports as described below: + +- any E1 or DS1 TDM or SONET/SDH interface; +- ITU-T G.703 E1/T1 external clock port; +- 2048 kHz synchronization signal according to clause 13 of [ITU-T G.703]. + +In addition, the TIGIN gateway node clock shall meet the requirements of [ITU-T G.813] that specifies slave clock performance applicable to synchronous digital hierarchy (SDH) equipment. The following references on Jitter and Wander are applicable to signal interfaces and synchronization signals. [ITU-T G.823] is applicable for plesiochronous digital hierarchy (PDH) signals based on the 2048 kbit/s hierarchy and synchronization signals, and [ITU-T G.824] is applicable for PDH signals based on the 1544 kbit/s hierarchy. [ITU-T G.825] is applicable for SDH signals. The physical layer for these signals is defined in [ITU-T G.703]. Specifically, 2048 kHz is specified in clause 13 of [ITU-T G.703]. + +Similar to the case of hierarchical master-slave switched circuit network (SCN) synchronization methods, it is recommended that a primary and a secondary synchronization reference input be provided to each clock. + +NOTE – If a TIGIN gateway connects to a VoIP terminal then there may be clock rate differences between the local clock in the VoIP terminals and the clock rate in the GSTN network. This frequency difference may result in slips and packet discards/duplications. + +### **8.5 Security** + +#### **8.5.1 Security on management interfaces** + +Security on management interfaces is for further study. + +#### **8.5.2 Per call control and signalling interfaces security** + +If a TIGIN gateway supports security on IP-based per call control and signalling interfaces, then it shall be supported in the following manner. A TIGIN that utilizes IP for the transport of per call control and signalling shall support IPsec and must be able to secure the traffic flows using encapsulating security payload (ESP) (see [IETF RFC 2406]) with null encryption and IPsec transport and tunnel mode encapsulation as defined in [IETF RFC 2401]. All other methods of security defined in [IETF RFC 2401] are optional and shall be negotiated via Internet key exchange (IKE). + +### **8.6 Additional features** + +#### **8.6.1 Packet filtering** + +A TIGIN gateway may provide support for source IP address and source UDP port filtering. This support must be provisionable. This is based on source and destination transport addresses being equal as per clauses 7.1.2 and 7.1.3. + +Note that when connecting to devices that are not TIGIN gateways, this may not be possible as this may lead to RTP non-interoperability if the remote device does not send and receive from the same transport address. + +#### **8.6.2 Lawful interception (optional)** + +Support for lawful interception is optional. + +If lawful interception is supported by a TIGIN gateway then it shall not degrade the quality of service of any intercepted call in a detectable way. + +NOTE – The following is a list of possible (non-exhaustive) ways that lawful intercept could degrade performance in a detectable way: + +- impact on latency (e.g., large or fixed increase); +- impact on loss (e.g., large or fixed increase); +- impact on jitter. + +Ways of providing lawful interception in this Recommendation are for further study. + +### **8.7 Management functions and management system interfaces** + +The management system interface performs the functions to administer the system on a non-real-time (non-per-call) basis with respect to the following subclauses. Further details for each of the management functions outlined in the following subclauses are included in the general (e.g., [ITU-T M.3100]) and technology specific (e.g., [ITU-T G.784], [IETF RFC 2579]) Recommendations. + +Support of TMN and SNMP management systems are for further study. + +#### **8.7.1 Configuration management** + +For further study. Issues to be considered include the management of: + +- TDM interface features such as line rates, frame formats; +- IP interface features; +- packetizer options such as packet loss mitigation scheme, which are not needed to be controlled on a per call basis; +- echo canceller options; +- voice feature options; +- clock recovery; + +- all other configurable parameters. + +#### 8.7.2 Fault management + +For further study. Issues to be considered include the management of: + +- equipment faults; +- facility faults at TDM and IP sides. + +#### 8.7.3 Performance management + +Performance management includes items such as facility and connection performance monitoring, congestion control, and traffic management. + +Clause 8.7.3.1 provides requirements for call-quality monitoring and diagnostic capabilities. + +Clause 8.7.3.2 provides requirements for congestion control and traffic management. + +##### 8.7.3.1 Call-quality monitoring and diagnostics + +The TIGIN gateway shall provide the capability to monitor and report on individual call-quality and causes of voice or signal degradation using RTCP extended reports (RTCP XR) parameters and reporting capabilities. [ITU-T H.248.30] provides a method of reporting those parameters to MGC. A generic RTCP monitoring and reporting capability that meets these requirements is described in [IETF RFC 3611]. The following listing of performance parameters shall be supported by the TIGIN gateway. Note that the performance parameters/metrics listed below are a subset of those listed in [IETF RFC 3611]. The definitions for each of the listed parameters/metrics are provided in [IETF RFC 3611]. + +- a) Network packet loss rate – See [IETF RFC 3611], section 4.7.1 for the definition of this parameter/metric. The proportion of packets lost during transmission. +- b) Jitter buffer discard rate – See [IETF RFC 3611], section 4.7.1 for the definition of this parameter/metric. The proportion of packets discarded by the receiving jitter buffer. This may be high if the jitter level is high or if the jitter buffer is too small. +- c) Burst loss density – See [IETF RFC 3611], section 4.7.2 for the definition of this parameter/metric. The average proportion of packets both lost and discarded during burst periods. A burst is a period during which a high proportion of packets are either lost in transit or discarded due to late arrival. In general, a burst is likely to result in audible degradation to call quality. A burst is defined as a longest sequence that: + - 1) starts with a lost or discarded packet; + - 2) does not contain any occurrences of $G_{min}$ or more consecutively received (and not discarded) packets; and + - 3) ends with a lost or discarded packet. +- d) Gap loss density – See [IETF RFC 3611], section 4.7.2 for the definition of this parameter/metric. The average proportion of packets lost and discarded during gaps. A gap is a period between bursts; the above burst definition means that during gaps the packet loss rate is low and lost/discarded packets are isolated and hence can be effectively masked by packet loss concealment algorithms. +- e) Burst duration – See [IETF RFC 3611], section 4.7.2 for the definition of this parameter/metric. The average length of burst periods expressed in milliseconds. +- f) Gap duration – See [IETF RFC 3611], section 4.7.2 for the definition of this parameter/metric. The average length of gap periods expressed in milliseconds. +- g) RTCP round trip delay – See [IETF RFC 3611], section 4.7.3 for the definition of this parameter/metric. The round trip delay between RTP instances, expressed in milliseconds. + +- h) End system delay – See [IETF RFC 3611], section 4.7.3 for the definition of this parameter/metric. The end system delay, comprising encode, decode and jitter buffer delay, expressed in milliseconds. This may be combined with the RTCP round trip delay to estimate the overall voice over IP segment round trip delay. +- i) Signal level – See [IETF RFC 3611], section 4.7.4 for the definition of this parameter/metric. The received signal level measured during talk spurts, expressed in dBm0. +- j) Noise level – See [IETF RFC 3611], section 4.7.4 for the definition of this parameter/metric. The received noise level measured during silence periods, expressed in dBm0. +- k) Residual echo return loss – See [IETF RFC 3611], section 4.7.4 for the definition of this parameter/metric. The echo return loss after the effects of echo cancellation, expressed in dB. Both local and remote RERL values are specified, although only the local RERL may be available (from the gateway's echo canceller). +- l) Gmin – See [IETF RFC 3611], section 4.7.6 for the definition of this parameter/metric. A parameter used to define bursts. (See c above for the definition of "burst".) This is, by default, set to 16, which sets the threshold packet loss rate between bursts and gaps to approximately 6%. +- m) R factor – See [IETF RFC 3611], section 4.7.5 for the definition of this parameter/metric. A calculated R-factor representing receiving end call quality. + +The R-factor is dependent on the availability of a number of different parameters. The minimum set of parameters that shall be measured or confidently estimated in order to calculate a meaningful R-factor is as follows: + +- talker echo loudness rating; +- mean one-way delay of the echo path; +- round-trip delay in a 4-wire loop; +- absolute delay in echo-free connections; +- equipment impairment factor; +- packet-loss robustness factor; +- random packet-loss probability; +- circuit noise referred to 0 dBr-point. + +All other parameters that cannot be measured or estimated may be set to their default values defined in [b-ITU-T G.107]. This includes the case where an echo canceller is not integrated with the TIGIN gateway as per configuration A in clause 8.1.1.1. + +- n) External R factor – See [IETF RFC 3611], section 4.7.5 for the definition of this parameter/metric. An R-factor representing the effects of an externally connected network. +- o) Estimated MOS-LQ – See [IETF RFC 3611], section 4.7.5 for the definition of this parameter/metric. An estimated receiving end listening quality MOS. +- p) Estimated MOS-CQ – See [IETF RFC 3611], section 4.7.5 for the definition of this parameter/metric. +- q) Packet loss concealment type – See [IETF RFC 3611], section 4.7.6 for the definition of this parameter/metric. Type of packet loss concealment algorithm in use. Indicates unknown, silence insertion, "standard" (i.e., per appropriate ITU-T Recommendation) and "enhanced". + +- r) Jitter buffer type – See [IETF RFC 3611], section 4.7.6 for the definition of this parameter/metric. Indication of whether the receiving jitter buffer is fixed or adaptive or unknown. +- s) Jitter buffer adaptation rate – See [IETF RFC 3611], section 4.7.6 for the definition of this parameter/metric. For adaptive jitter buffers – the adaptation rate. This is defined as the time taken to adjust to a step of 70 ms increase in jitter divided by twice the frame size in milliseconds. This value need only be provided if the jitter buffer type is specified. +- t) Jitter buffer nominal size – See [IETF RFC 3611], section 4.7.7 for the definition of this parameter/metric. For fixed and adaptive jitter buffers – the current nominal jitter buffer size. This is expressed in milliseconds. This value need only be provided if the jitter buffer type is specified. +- u) Jitter buffer max size – See [IETF RFC 3611], section 4.7.7 for the definition of this parameter/metric. For fixed and adaptive jitter buffers – the maximum jitter buffer size in milliseconds. This value need only be provided if the jitter buffer type is specified. +- v) Jitter buffer absolute max – See [IETF RFC 3611], section 4.7.7 for the definition of this parameter/metric. For adaptive jitter buffers – the maximum achievable size of the buffer in milliseconds. This value need only be provided if the jitter buffer type is specified. + +##### 8.7.3.2 Congestion control and traffic management + +The TIGIN gateway shall be robust against excessive ITU-T H.248 messaging from MGC, e.g., it must not reset itself nor shall calls in-progress be terminated in an uncontrolled manner. + +The TIGIN gateway shall support ITU-T H.248.10, media gateway resource congestion handling package or ITU-T H.248.11, media gateway overload control package, or both, to protect the gateway from call processing overload. + +When SS7 messages enter the TIGIN via a TDM interface and get forwarded to the MGC (using M2UA or M3UA over SCTP), overload protection against signalling congestion at the TIGIN may be required, depending upon how the TIGIN is engineered internally. If it is required, then the TIGIN shall be capable of detecting that it has internal signalling congestion, and shall apply SS7 signalling management controls: + +- For M3UA scenarios, control using transfer controlled (TFC) and transfer prohibited (TFP) procedures defined in [ITU-T Q.703] and [ITU-T Q.704] shall be used. +- For M2UA scenarios, congestion control using MTP2 messaging and M2UA primitives shall be used. + +Overload controls and traffic management required for the other signalling interfaces (MF, DTMF, CAS) are for further study. + +Monitoring of TIGIN internal resource usage for performance and capacity management purposes is for further study. + +#### 8.7.4 Security management + +##### 8.7.4.1 Key management + +If a TIGIN gateway supports security on IP-based per call control and signalling interfaces, then security management shall be supported in the following manner: + +A TIGIN gateway shall support the Internet key exchange protocol for security key management (see [IETF RFC 2409]) with the minimum support of pre-shared keys as defined in [IETF RFC 2409]. + +A TIGIN gateway may additionally authenticate itself to the remote site using either one of public key encryption authentication forms or digital signature as described in [IETF RFC 2409]. For the + +case of digital signature authentication, ITU-T X.509 certificates shall be used (see [IETF RFC 3280]). + +Security management, including key management for all other IP traffic, is for further study. + +#### 8.7.5 Accounting + +No accounting functions are supported in a TIGIN gateway. Note that this does not imply that signals such as on-hook, off-hook, etc., that support or provide information necessary for certain accounting type functions (e.g., call billing) do not need to be conveyed or supported. Rather, that the TIGIN gateway itself does not provide any direct accounting functionality such as call billing, etc. + +#### 8.7.6 Maintenance testing + +The TIGIN gateway shall provide the ability to monitor calls and place test calls in the direction of the GSTN and in the direction of the IP network. + +The monitor and intrusive access point shall provide a test access point on a per TIGIN gateway basis and not on a per-shelf or per-rack basis, i.e., one per TIGIN gateway. This test access capability shall support all features and services provided by the TIGIN gateway. + +##### 8.7.6.1 Non-intrusive monitor access + +The monitor access shall provide the ability to connect to a specific port/address/call and monitor one or both directions of an active call simultaneously (Figure 7). It shall be possible to monitor a specific port or connection within the TIGIN gateway allowing a port to be monitored before a call is active on the port. When an active call is placed on the port, the monitor shall remain active. The monitor access may provide either a TDM or IP output and will depend on the actual implementation of the TIGIN gateway. + +In the non-intrusive monitoring case, there is no requirement that signalling be monitored. + +![Diagram of a TIGIN gateway showing non-intrusive monitor access. A central box labeled 'TIGIN gateway' has a solid line labeled 'TDM' entering from the left and a solid line labeled 'IP' exiting to the right. A dashed horizontal line passes through the center of the box. Below the box, a label 'Test access port (TDM and/or IP)' points to this dashed line. In the bottom right corner of the diagram area, the text 'G.799.1-Y.1451.1(16)_F07' is present.](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +TIGIN gateway + +TDM + +IP + +Test access port +(TDM and/or IP) + +G.799.1-Y.1451.1(16)\_F07 + +Diagram of a TIGIN gateway showing non-intrusive monitor access. A central box labeled 'TIGIN gateway' has a solid line labeled 'TDM' entering from the left and a solid line labeled 'IP' exiting to the right. A dashed horizontal line passes through the center of the box. Below the box, a label 'Test access port (TDM and/or IP)' points to this dashed line. In the bottom right corner of the diagram area, the text 'G.799.1-Y.1451.1(16)\_F07' is present. + +**Figure 7 – Non-intrusive monitor access** + +##### 8.7.6.2 Intrusive monitor access + +The intrusive test access shall allow test calls to be made in either direction. The intrusive test access shall allow the user to connect to a specific port/address and place a call to a destination, either in the direction of the GSTN, or the IP network. The intrusive test access may provide either a TDM or IP output and will depend on the actual implementation of the TIGIN gateway. + +In the case where the test access port is TDM (e.g., Figure 8a), a TDM/IP conversion function is required to access the IP data port or stream. + +The specific point within the IP path where access is placed shall be the last IP point prior to any speech processing functions. + +![Figure 8a: Intrusive test access – TDM test access port. The diagram shows a TDM line entering a dashed box labeled 'Gateway functions'. An arrow points from the TDM line to a circle, which then connects to a 'TDM/IP' block. From the 'TDM/IP' block, an arrow points to another circle, which then connects to an IP line exiting the 'Gateway functions' box. Below the first circle, a 'Test access port (TDM)' is shown with an arrow pointing to it. The diagram is labeled G.799.1-Y.1451.1(16)_F08a.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Figure 8a: Intrusive test access – TDM test access port. The diagram shows a TDM line entering a dashed box labeled 'Gateway functions'. An arrow points from the TDM line to a circle, which then connects to a 'TDM/IP' block. From the 'TDM/IP' block, an arrow points to another circle, which then connects to an IP line exiting the 'Gateway functions' box. Below the first circle, a 'Test access port (TDM)' is shown with an arrow pointing to it. The diagram is labeled G.799.1-Y.1451.1(16)\_F08a. + +**Figure 8a – Intrusive test access – TDM test access port** + +In the case where the test access port is IP (e.g., Figure 8b), a TDM/IP conversion function is required to access the TDM data port or stream. + +The specific point within the TDM path where access is placed shall be prior to any speech processing functions. + +![Figure 8b: Intrusive test access – IP test access port. The diagram shows a TDM line entering a dashed box labeled 'Gateway functions'. The TDM line first passes through a 'TDM/IP' block, then a circle, and then enters the 'Gateway functions' box. An arrow points from the circle before the box to a 'Test access port (IP)'. An IP line exits the 'Gateway functions' box and connects to another circle. The diagram is labeled G.799.1-Y.1451.1(16)_F08b.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Figure 8b: Intrusive test access – IP test access port. The diagram shows a TDM line entering a dashed box labeled 'Gateway functions'. The TDM line first passes through a 'TDM/IP' block, then a circle, and then enters the 'Gateway functions' box. An arrow points from the circle before the box to a 'Test access port (IP)'. An IP line exits the 'Gateway functions' box and connects to another circle. The diagram is labeled G.799.1-Y.1451.1(16)\_F08b. + +**Figure 8b – Intrusive test access – IP test access port** + +If TDM is provided, the interface shall be E1/T1 ([ITU-T G.703], [ITU-T G.704]) and signalling shall conform to clause 7.2. If an IP output is provided, the interface shall be as specified within 7.1 (G ITU-T.799.1/ ITU-T Y.1451.1) and signalling shall be accomplished via ITU-T H.248/Megaco signalling messages sent to/from the TIGIN gateway, as with any other IP port. + +In the case of SS7 signalling arrangements, the signalling to set up calls is done via the ITU-T H.248/Megaco path to the MGC. + +The functions provided by the management system should not overlap with those provided by per-call control. + +## Appendix I + +## Overview of the location of TIGIN gateways in end-to-end connections + +(This appendix does not form an integral part of this Recommendation.) + +Figure I.1 shows a functional block diagram of transport network equipment for interconnecting GSTN terminals and VoIP terminals (hereinafter abbreviated TIGIN). The MGC is present although, for simplicity, is not shown in Figure I.1. + +![Figure I.1: Location of TIGIN and possible connection types of interest in this Recommendation. The diagram shows a central TIGIN gateway (ITU-T G.799.1/Y.1451.1) connecting a GSTN network on the left to an IP network on the right. On the left, two GSTN terminals are connected to a GSTN network (represented by a large oval). On the right, two VoIP terminals are connected to a network optimized for transport of internet protocol (also represented by a large oval). Four connection types are numbered: (1) Bearer interface from GSTN to IP network; (2) Bearer interface from IP network to GSTN; (3) Bearer interface from IP network to GSTN; (4) Bearer interface from GSTN to IP network. Signalling is shown as dotted lines: GSTN - TIGIN signalling from the GSTN network to the gateway, and IP Network to TIGIN signalling from the gateway to the IP network. A legend at the bottom left indicates that solid lines are Bearer interfaces and dotted lines are Signalling. The diagram is labeled G.799.1-Y.1451.1(16)_FI.1 in the bottom right corner.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +Figure I.1 is a functional block diagram illustrating the location of TIGIN gateways in end-to-end connections between GSTN terminals and VoIP terminals. The diagram is divided into three main vertical sections: GSTN (left), TIGIN gateway (center), and Network optimized for transport of internet protocol (right). + +- GSTN (left):** Contains two GSTN terminals connected to a GSTN network (represented by a large oval). +- TIGIN gateway (center):** Labeled "TIGIN gateway (ITU-T G.799.1/Y.1451.1)". It acts as the central interconnection point. +- Network optimized for transport of internet protocol (right):** Contains two VoIP terminals connected to the network (represented by a large oval). + +Four connection types are numbered in the diagram: + +- (1) Bearer interface from GSTN to IP network. +- (2) Bearer interface from IP network to GSTN. +- (3) Bearer interface from IP network to GSTN. +- (4) Bearer interface from GSTN to IP network. + +Signalling is indicated by dotted lines: + +- GSTN - TIGIN signalling: From the GSTN network to the TIGIN gateway. +- IP Network to TIGIN signalling: From the TIGIN gateway to the IP network. + +Legend: + +- Bearer interface +- ..... Signalling + +Reference: G.799.1-Y.1451.1(16)\_FI.1 + +Figure I.1: Location of TIGIN and possible connection types of interest in this Recommendation. The diagram shows a central TIGIN gateway (ITU-T G.799.1/Y.1451.1) connecting a GSTN network on the left to an IP network on the right. On the left, two GSTN terminals are connected to a GSTN network (represented by a large oval). On the right, two VoIP terminals are connected to a network optimized for transport of internet protocol (also represented by a large oval). Four connection types are numbered: (1) Bearer interface from GSTN to IP network; (2) Bearer interface from IP network to GSTN; (3) Bearer interface from IP network to GSTN; (4) Bearer interface from GSTN to IP network. Signalling is shown as dotted lines: GSTN - TIGIN signalling from the GSTN network to the gateway, and IP Network to TIGIN signalling from the gateway to the IP network. A legend at the bottom left indicates that solid lines are Bearer interfaces and dotted lines are Signalling. The diagram is labeled G.799.1-Y.1451.1(16)\_FI.1 in the bottom right corner. + +**Figure I.1 – Location of TIGIN and possible connection types of interest in this Recommendation** + +This appendix describes the four connection types illustrated in Figure I.1. + +The terminals attached to the Internet are assumed to have ITU-T H.323 functionality from the point of view of voice and voiceband data transmission. These terminals may be connected to the IP network via a direct connection (e.g., Ethernet, token ring, etc.) or a dial-up connection (e.g., modem and point-to-point protocol (PPP) link). The IP and GSTN sections are interconnected through a GSTN/IP gateway, called a TIGIN. For convenience, this gateway is designated with a single box in Figure I.1. + +The specific functions of the gateway will depend on whether the direction of transmission is from the IP network to the GSTN or vice versa. In particular, the functions in the gateway include (but are not limited to): + +*Call originating on the IP network and terminating on GSTN* + +- reception, interpretation and generation of relevant signalling messages; +- packet disassembly (including "IP stack"); +- speech decoder (including error concealment, comfort noise, silence insertion, etc.); +- management or regulation of delay variation; + +- echo cancellation. + +### *Call originating on the GSTN and terminating on IP network* + +- reception, interpretation and generation of relevant signalling messages; +- speech encoder (including silence removal, comfort noise decisions, etc.); +- packet assembly (including "IP stack"); +- management or regulation of delay variation; +- echo cancellation. + +Four connection arrangements are considered in this Recommendation, each of which is shown in Figure I.1. They are: + +- 1) GSTN terminal → VoIP terminal (GSTN terminal → GSTN → TIGIN → IP network → VoIP terminal); +- 2) VoIP terminal → GSTN terminal (VoIP terminal → IP network → TIGIN → GSTN → GSTN terminal); +- 3) VoIP terminal → VoIP terminal (VoIP terminal → IP network → TIGIN → IP network → VoIP terminal); +- 4) GSTN terminal → GSTN terminal (GSTN terminal → GSTN → TIGIN → GSTN → GSTN terminal). + +Each of these four connection arrangements requires the use of one gateway. Hence, connections that are purely GSTN-based or are strictly VoIP-to-VoIP using only the Internet are not the subject of this Recommendation. Situations in which multiple or tandem gateways are used are covered by combinations of connections 1 through 4 (e.g., a combination of 1 and 2 would be GSTN terminal → GSTN → TIGIN #1 → IP network → TIGIN #2 → GSTN → GSTN terminal). More complex arrangements may be envisaged but it is not considered necessary to describe them in detail as they can be made up of the cases above. + +## Appendix II + +## Further information on performance/interworking and synchronization + +(This appendix does not form an integral part of this Recommendation.) + +### II.1 Performance/interworking + +Performance/interworking issues include: + +- a) Ability to vary the packet size on a per call basis. + +Voice samples are accumulated and buffered into a packet, and a packet is sent when it becomes full. The size of the packet can be controlled by PCC messages, but the network must ensure that they are the same on both ends of a connection. In addition, the capability to vary the packet size on a per call basis must be supported by the PCC protocol, and is outside the scope of this Recommendation. + +- b) Silence suppression/comfort noise generation when used in conjunction with codecs that do not describe them. +- c) Real-time control protocol (RTCP). +- d) Packet loss mitigation scheme. +- e) Jitter buffer size. + +Variation in the arrival of packets into the TIGIN (packet delay variation) must be accommodated by a jitter buffer. The size of the jitter buffer must be selected based on the quality goals for the network. In addition, the type of data being transported may affect the selection of the jitter buffer size. For example, voice transmission is tolerant to packet loss but not to excessive delay, whereas voiceband data or data is tolerant to delay but not to packet loss. + +- f) Transmission delay. + +Delay through the TIGIN should be minimized. In addition, the TIGIN should be tolerant to the overall delay produced by the network. + +### II.2 RTP timestamps + +As described in [IETF RFC 3550], the randomly initialized RTP timestamp is a 32-bit field that must be updated such that it reflects the sampling instance of the first octet in the RTP data packet. Consequently, there is a direct relation between the rate of the TDM clock at the sending TIGIN and the rate of the RTP packets being filled up, sent over the IP network, and the rate of their arrival at the receiving TIGIN. At the receive end, the arrival of an RTP packet could be timestamped based on the TDM clock of the circuit switch domain interfacing to the local (receiving) TIGIN. + +The difference between the packet arrival times and the difference between RTP packet timestamps could be algorithmically processed to extract information for adjusting the local TDM clock (see [IETF RFC 2833]). + +## Appendix III + +## TIGIN equipment arrangements + +(This appendix does not form an integral part of this Recommendation.) + +The basic interworking arrangements between IP networks and GSTN networks are shown in Figure III.1. Note that the figures shown in this appendix are only examples and are not exhaustive. The MGC is present although, for simplicity, is not shown in the figures below. + +![Diagram of GSTN terminal interworking with H.323 terminal via a TIGIN gateway.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +This diagram illustrates the interworking of a GSTN terminal and an ITU-T H.323 terminal. On the left, a 'GSTN terminal' (represented by a telephone icon) is connected to a cloud labeled 'General switched telephone network'. This network is connected to a rectangular box labeled 'TIGIN gateway (ITU-T G.799.1/Y.1451.1)'. The TIGIN gateway is connected to another cloud labeled 'IP network'. On the right, an 'ITU-T H.323 terminal' (represented by a computer monitor and keyboard icon) is connected to the 'IP network' cloud. The reference code 'G.799.1-Y.1451.1(16)\_FIII.1' is shown at the bottom right. + +Diagram of GSTN terminal interworking with H.323 terminal via a TIGIN gateway. + +Figure III.1 – GSTN terminal interworking with H.323 terminal + +Other cases may exist as shown in Figures III.2 and III.3. + +![Diagram of two GSTN terminals interconnected through a network optimized for transport of IP.](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +This diagram shows two GSTN terminals interconnected through a central network. At the top is a cloud labeled 'Network optimized for transport of Internet protocol'. Below it are two rectangular boxes, both labeled 'TIGIN gateway (ITU-T G.799.1/Y.1451.1)'. Each TIGIN gateway is connected to the top cloud and to a 'General switched telephone network' cloud. Each 'General switched telephone network' cloud is connected to a 'GSTN terminal' (represented by a telephone icon). The reference code 'G.799.1-Y.1451.1(16)\_FIII.2' is shown at the bottom right. + +Diagram of two GSTN terminals interconnected through a network optimized for transport of IP. + +Figure III.2 – GSTN Terminals interconnected through network optimized for transport of IP + +or + +![Diagram showing two ITU-T H.323 terminals connected via networks optimized for Internet protocol, which are then connected to TIGIN gateways (ITU-T G.799.1/Y.1451.1) that interface with a General switched telephone network (GSTN).](77959075c823bb5169480d7b8ff82a63_img.jpg) + +The diagram illustrates a network architecture for H.323 terminals. At the top, a cloud represents the 'General switched telephone network'. Below it, two rectangular boxes represent 'TIGIN gateway (ITU-T G.799.1/Y.1451.1)'. Each gateway is connected to the top network cloud by a double-headed arrow. Below each gateway is another cloud labeled 'Network optimized for transport of Internet protocol', which is also connected to the gateway by a double-headed arrow. On the far left and far right, an icon of a computer monitor and keyboard represents an 'ITU-T H.323 terminal'. Each terminal is connected to its respective 'Network optimized for transport of Internet protocol' cloud by a single line. In the bottom right corner of the diagram area, the text 'G.799.1-Y.1451.1(16)\_FIII.3' is present. + +Diagram showing two ITU-T H.323 terminals connected via networks optimized for Internet protocol, which are then connected to TIGIN gateways (ITU-T G.799.1/Y.1451.1) that interface with a General switched telephone network (GSTN). + +**Figure III.3 – H.323 terminals interconnected through GSTN network** + +In the latter two cases, the interworking functions will remain the same so will, therefore, not be dealt with further. + +## Appendix IV + +## Mapping of E-model (ITU-T G.107) parameters from IETF RFC 3611 metrics and determining R-factor + +(This appendix does not form an integral part of this Recommendation.) + +### IV.1 The E-model + +The E-model ([b-ITU-T G.107]) was developed as a planning tool, but may, however, be used to estimate transmission quality based on measured network parameters. The E-model defines a method for determining an R-factor, which may be translated into an estimated mean opinion score (MOS). The E-model was developed under the assumption that parameters were stable. However, some parameters, notably packet loss rate, may vary considerably during a call. Extensions to the E-model, such as [b-ETSI TS 101 329-5] Annex E, have been developed in order to permit time-varying parameters to be incorporated into calculated transmission quality values. + +![Figure IV.1: ITU-T G.107 reference model diagram showing the flow of audio and delay components between a send side (A) and a receive side (B).](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +The diagram illustrates the ITU-T G.107 reference model for determining the R-factor. It shows a 'Send side (A)' on the left and a 'Receive side (B)' on the right, connected by a central network element. At each side, a person is shown using a telephone handset, with associated parameters: **Ds-Factor** and **Room noise Ps** on the send side, and **Dr-Factor** and **Room noise Pr** on the receive side. The central network element contains a 'Weighted echo path loss WEPL' and 'Round-TripDelay Tr' loop, a 'Coding / Decoding' block, and various impairment factors: **Circuit Noise Nc** (referred to 0 dBr), **Equipment impairment factor Ie**, **Packet-Loss probability Ppl**, and **Packet-Loss robustness factor Bpl**. A '0 dBr point' is marked at the top of the central element. Delay components are indicated by horizontal arrows: **SLR** (Send Side Loudness Rating) from A to the 0 dBr point, **RLR** (Receive Side Loudness Rating) from the 0 dBr point to B, and **OLR** (Overall Loudness Rating) from A to B. Other delay parameters include **Mean one-way delay T**, **Absolute delay Ta**, **Quantizing distortion qdu**, and **Expectation factor A**. On the receive side, additional ratings are shown: **Sidetone masking rating STMR**, **Listener sidetone rating LSTR** (where $LSTR = STMR + Dr$ ), and **Talker echo loudness rating TELR**. The diagram is labeled with the code G.799.1-Y.1451.1(16)\_FIV.1. + +Figure IV.1: ITU-T G.107 reference model diagram showing the flow of audio and delay components between a send side (A) and a receive side (B). + +Figure IV.1 – ITU-T G.107 reference model (figure from [b-ITU-T G.107]) + +Figure IV.1 is taken from [b-ITU-T G.107] and is incorporated into this appendix to facilitate the following description of the mappings between [IETF RFC 3611] parameters and E-model parameters. In the scenario shown, an R-factor is being determined for the "Receive Side", and hence the diagram would be reversed for the other direction of communication. To facilitate the explanation below, the send side will be denoted A and the receive side denoted B, and hence an R-factor is being determined for the B end of the connection (in this case gateway "B"). The E-model parameters below are all "B" side parameters unless otherwise noted. + +It should also be noted that [b-ITU-T G.108] provides more detailed guidance on the application of the E-model and also makes use of the same "A" and "B" notations for the two endpoints. + +Some factors, for example the handset **Ds**, **Dr** and **STMR** parameters, **RLR** and **Pr** are generally not observable or measurable at a trunking gateway and, hence, should be set to known values for the specific network or ITU-T G.107 default values. + +### IV.2 Parameters related to delay + +[b-ITU-T G.107] specifies three delay parameters: + +- $T_a$ the mean end-to-end one way delay; +- $T$ the mean one way delay from the receive side to the point at which talker echo would occur if the receive side were talking; and +- $T_r$ the round trip delay between sources of echo on the send and receive sides. + +[IETF RFC 3611] specifies two delay parameters, the RTCP round trip delay and the end system delay, denoted $T_{RTCP}$ and $T_{ESD}(A \text{ or } B)$ below. + +Gateway B may measure or estimate $T_{RTCP}$ and $T_{ESD}(B)$ and may receive $T_{ESD}(A)$ in an RTCP XR message from the remote gateway A. In addition, gateway B may determine the local echo path one way delay $T_{EPD}(B)$ from the gateway's echo canceller, however, it should be noted that this delay differs from the ITU-T G.107 $T$ parameter as it represents only the echo path delay over the PCM or analog path. + +The E-model parameters may be estimated from the parameters known to gateway B as follows – (Note that in [b-ITU-T G.107], $T_a$ is shown in Figure 1 as "absolute delay", however, is referred to in Table 2 of [b-ITU-T G.107] and clause 8.7.3.1 m) fourth bullet, as "absolute delay in echo-free connections"): + +$$T_a = \frac{(T_{RTCP} + T_{ESD}(A) + T_{ESD}(B) + T_{EPD}(B) \dots \dots \dots + T_{EPD}(A) \text{ (if known)})}{2}$$ + +NOTE – If an RTCP XR message has not been received from gateway A, then assume that + +$$T_{ESD}(A) = T_{ESD}(B)$$ + +$T$ is approximately equal to $T_a$ + +$T_r$ is approximately equal to $2 \times T$ + +### IV.3 Parameters related to packet loss + +[b-ITU-T G.107] provides a formula for calculating the effective $I_e$ ( $I_e\text{-eff}$ ) factor under conditions of independent (non-bursty) packet loss using the packet loss probability ( $P_{pl}$ ) and the packet-loss robustness factor ( $B_{pl}$ ). [b-ITU-T G.107] omits to mention that the packet loss rate should be measured after the de-jitter buffer in the end system i.e., should use the probability of *lost and discarded* packets. The base (zero packet loss) $I_e$ factor and packet-loss robustness factor is tabulated in Appendix I of [b-ITU-T G.113] for a range of common codec types. + +[b-ETSI TS 101 329-5] Annex E defines algorithms for measuring the distribution of lost and discarded packets, and for calculating $I_e\text{-eff}$ in the presence of time-varying (bursty) packet loss and discard. This approach has been shown to provide improved correlation with subjective test data for time-varying conditions (e.g., correlation coefficient of about 0.84 instead of 0.71). + +[b-ETSI TS 101 329-5] Annex E requires that $I_e\text{-eff}$ be separately calculated for the burst and gap condition, giving $I_e\text{-eff}(\text{burst})$ and $I_e\text{-eff}(\text{gap})$ , and then combined to give a single $I_e\text{-eff}$ value. The $B_{pl}$ method defined in [b-ITU-T G.107] for mapping packet loss rate to $I_e\text{-eff}$ should be used to determine $I_e\text{-eff}(\text{gap})$ and $I_e\text{-eff}(\text{burst})$ based respectively on the packet loss rate in gaps and bursts. + +[IETF RFC 3611] incorporates the TS 101 329-5 Annex E algorithm for packet loss distribution measurement and hence the burst loss density, and gap loss density can be input directly to the ETSI TS 101 329-5 Annex E $I_e\text{-eff}(\text{burst})$ and $I_e\text{-eff}(\text{gap})$ calculations and used to produce an overall $I_e\text{-eff}$ factor. + +- a) *Approach based on bursty/time varying packet loss rate* + +$$P_{pl}(\text{burst}) = \text{Burst Loss Density}$$ + +Ppl (gap) = Gap Loss Density + +Ie-eff(burst) calculated using Ppl (burst) and Bpl for Codec + +Ie-eff(gap) calculated using Ppl (burst) and Bpl for Codec + +Ie-eff calculated using [b-ETSI TS 101 329-5] Annex E (section E.7.1) + +If the Ie-eff factor is calculated based only on average packet loss and discard rate, then the ITU-T G.107 Ppl parameter can be calculated as the weighted average of the RTCP XR gap and burst loss densities. + +b) *Approach based on assumed independent/constant packet loss rate* + +$$Ppl = \frac{(Burst\ Loss\ Density \times Burst\ Duration + Gap\ Loss\ Density \times Gap\ Duration)}{(Burst\ Duration + Gap\ Duration)}$$ + +Ie-eff calculated using Ppl and Bpl for codec. + +### IV.4 Parameters related to noise + +[b-ITU-T G.107] defines the noise level as the sum of the noise powers for circuit and room noise. If no information on noise level is measured or available, then the default ITU-T G.107 parameters should be used. + +[IETF RFC 3611] defines noise level as the received noise level during silence periods expressed in dBm0. This corresponds to the sum of the sending end room noise and circuit noise, and may be directly input into the E-model as parameter No(B). + +### IV.5 Parameters related to signal level and loudness + +The remote end ITU-T G.107 Send Loudness Rating SLR(A) can be estimated from the locally measured [IETF RFC 3611] signal level (B) parameter, and the local SLR(B) value from the signal level (A), reported via a received RFC 3611 message. + +SLR(A) = -15 – Signal Level (B) direct input to R-factor calculation + +SLR(B) = -15 – Signal Level (A) used to determine TELR + +### IV.6 Parameters related to Echo + +The ITU-T G.107 talker echo loudness rating is the sum of the remote echo return loss and local send and receive loudness ratings. + +$$TELR(B) = SLR(B) + ERL(A) + RLR(B)$$ + +The echo return loss value should be the estimated ERL **after** the effects of the echo canceller (defined as "Residual" echo return loss in [IETF RFC 3611]) from the remote gateway, and should be the value reported via a received RFC 3611 message. If the "residual echo return loss" value(s) are not reported via the IETF RFC 3611 messages, then the ITU-T G.107 default value for TELR should be used. + +### IV.7 Calculating R, MOS-LQ and MOS-CQ values + +[b-ITU-T G.107] defines the R-factor as: + +$$R = Ro - Is - Id - Ie + A$$ + +Where $R_o$ is primarily related to the basic signal-to-noise ratio, $I_s$ represents impairments that occur simultaneously with speech, $I_d$ represents impairments that are delayed with respect to speech, $I_e$ represents the equipment impairment factor and $A$ the advantage factor. + +$R$ is a *conversational* quality metric, and can be translated to an estimated conversational quality MOS score (MOS-CQ in [IETF RFC 3611]) using the $R$ to MOS conversion function in [b-ITU-T G.107]. By omitting the $I_d$ parameter, an estimated listening quality MOS score (MOS-LQ in [IETF RFC 3611]) can be determined. + +## Bibliography + +- [b-ITU-T F.749.1] Recommendation ITU-T F.749.1 (2015), *Functional requirements for vehicle gateways*. +- [b-ITU-T G.107] Recommendation ITU-T G.107 (2015), *The E-Model, a computational model for use in transmission planning*. +- [b-ITU-T G.108] Recommendation ITU-T G.108 (1999), *Application of the E-model: A planning guide*. +- [b-ITU-T G.113] Recommendation ITU-T G.113 (2007), *Transmission impairments due to speech processing*. +- [b-ITU-T G.113Ap. I] Recommendation ITU-T G.113 Appendix I (2002), *Provisional planning values for the equipment impairment factor $I_e$ and packet-loss robustness factor $B_{pl}$* . +- [b-ITU-T H.323] Recommendation ITU-T H.323 v7 (2009), *Packet-based multimedia communications systems*. +- [b-ITU-T V.32] Recommendation ITU-T V.32 (1993), *A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits*. +- [b-ITU-T V.34] Recommendation ITU-T V.34 (1998), *A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits*. +- [b-ETSI TS 101 329-5] ETSI TS 101 329-5 Annex E (2002), *Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; End-to-end Quality of Service in TIPHON systems; Part 5: Quality of Service (QoS) measurement methodologies – Annex E: Method for determining an equipment impairment factor using passive monitoring*. +- [b-IETF RFC 2460] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification*. +- [b-IETF RFC 2475] IETF RFC 2475 (1998), *An Architecture for Differentiated Services*. +- [b-IETF RFC 3260] IETF RFC 3260 (2002), *New Terminology and Clarifications for DiffServ*. +- [b-IETF RFC 3525] IETF RFC 3525 (2003), *Gateway Control Protocol Version 1*. + +# ITU-T Y-SERIES RECOMMENDATIONS + +## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES + +| | | +|--------------------------------------------------------------------|----------------------| +| GLOBAL INFORMATION INFRASTRUCTURE | | +| General | Y.100–Y.199 | +| Services, applications and middleware | Y.200–Y.299 | +| Network aspects | Y.300–Y.399 | +| Interfaces and protocols | Y.400–Y.499 | +| Numbering, addressing and naming | Y.500–Y.599 | +| Operation, administration and maintenance | Y.600–Y.699 | +| Security | Y.700–Y.799 | +| Performances | Y.800–Y.899 | +| INTERNET PROTOCOL ASPECTS | | +| General | Y.1000–Y.1099 | +| Services and applications | Y.1100–Y.1199 | +| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 | +| Transport | Y.1300–Y.1399 | +| Interworking | Y.1400–Y.1499 | +| Quality of service and network performance | Y.1500–Y.1599 | +| Signalling | Y.1600–Y.1699 | +| Operation, administration and maintenance | Y.1700–Y.1799 | +| Charging | Y.1800–Y.1899 | +| IPTV over NGN | Y.1900–Y.1999 | +| NEXT GENERATION NETWORKS | | +| Frameworks and functional architecture models | Y.2000–Y.2099 | +| Quality of Service and performance | Y.2100–Y.2199 | +| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 | +| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 | +| Enhancements to NGN | Y.2300–Y.2399 | +| Network management | Y.2400–Y.2499 | +| Network control architectures and protocols | Y.2500–Y.2599 | +| Packet-based Networks | Y.2600–Y.2699 | +| Security | Y.2700–Y.2799 | +| Generalized mobility | Y.2800–Y.2899 | +| Carrier grade open environment | Y.2900–Y.2999 | +| FUTURE NETWORKS | Y.3000–Y.3499 | +| CLOUD COMPUTING | Y.3500–Y.3999 | +| INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES | | +| General | Y.4000–Y.4049 | +| Definitions and terminologies | Y.4050–Y.4099 | +| Requirements and use cases | Y.4100–Y.4249 | +| Infrastructure, connectivity and networks | Y.4250–Y.4399 | +| Frameworks, architectures and protocols | Y.4400–Y.4549 | +| Services, applications, computation and data processing | Y.4550–Y.4699 | +| Management, control and performance | Y.4700–Y.4799 | +| Identification and security | Y.4800–Y.4899 | +| Evaluation and assessment | Y.4900–Y.4999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## **SERIES OF ITU-T RECOMMENDATIONS** + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | 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 | 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 | 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, 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.8032-202003-I_PDF-E/02e16c8e8e61c2706b5c0129674884a8_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/02e16c8e8e61c2706b5c0129674884a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4009623522372484c2560a096a6c74900168709 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/02e16c8e8e61c2706b5c0129674884a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5085d42b97d14c54efcea291647589da4531eda2fd107edc398a176a9862f822 +size 58001 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e8c405e960c332b1f60ebce8cd2f69bb40a3382 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd27d2c6ec07bdab3181ab9ea1295592f247a1dba91cee23e32b34447d29d3b8 +size 136172 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ff0c4d88c57b0f5f4ea96a14dc14c99b5f94df --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5b9bc6457f2b067bc1cd4da4489b4a43b1f81bfd13e578d49c9e98ec6551fbc +size 9899 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a2e9aab84c45ef3291cc8f24e429c4ad4d27881 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/1b23b78336d8bd286c653cbdb38428dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24ebf8dfe5e9e0235f51b2ea6d21f990cebc4a2ed04e01314b552fff2a672553 +size 47300 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3701d714d756000fafbef289abc446d0c84526b9 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:857950a1aff12590f78844cfbb169e383bcc90b91a66bee19a10b4c74909b6b5 +size 112792 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/21327313f7b18a481da0c87a6472a80d_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/21327313f7b18a481da0c87a6472a80d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ada234d88cd8698199e190ba6bb8c11e58c66417 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/21327313f7b18a481da0c87a6472a80d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e975a04e3f8993ccd5d837f451592c737931815a1996afcc5efc6c30754012ed +size 40121 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23513c641c243b7e74bfacaee6595af4a0f83557 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9be4b82bc38a3f226bd00a7e1fc4e31da654a42f7001f7e714ce33d0a393af6 +size 166460 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..624814f13495e6042c483cbe6405d794f2f9ff05 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09510207f2ea053dcfef7852ed8c79be370a2ac4ac5d0c4fc50d3b10c0620fe7 +size 67230 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b248b5f1e39a8c94dfe5bb9d6bd878bce5fd9fc --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df25bf86fed186a91db260d75834228060b3d87f7e28fc26bf3d89a8394cde1d +size 115412 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cec256985cb44906d4c75ca980dfb9996e4c1ac2 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94e8edf11a6b1616da3f032efb85656b83f25ee8ada8d765afb3140628f44ef2 +size 164286 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b80d100c0748dfa3f8bd24da2a848185aec316cb --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01b971747f689af9d56c99207271e4b2241c085ad7424c1c610690b335701cc1 +size 81862 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99de5c16f30233510537e785054424e1909815e9 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/5ee1bbbf85b473f78af9ec8368a4159a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3660895f74a319a2b0f9da7acc90a99bc68cb67005d0cdb456317a393e0d1791 +size 42565 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dc0c20104e21ea0d4c91346dfcb9088ac389ce5 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/638a308af25f1f56b4456a1fc503f161_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41e8707afdcb70914c398e88372da9558609fa5eaa84eaef15c8d61176e44973 +size 45534 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da1c88427707fc3b9b80c942ce75df80f8aea0e3 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8acec7f22c98794a3c25660475e453aa49c530c8a4dc328c9463f24dbab5aec7 +size 133792 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/7156cf400ef0e19f9d06a5d0549834a3_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/7156cf400ef0e19f9d06a5d0549834a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6478e50add8fb388e01f3cf148d8d92fe4ebbb --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/7156cf400ef0e19f9d06a5d0549834a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde8ccf2c40c23f52c147fea8f0f5b2fb6de58048627f27397f58bb2b6df0070 +size 140458 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9e1f4e39cd6f84c46685a9f40a1ee8b38b05ac6 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:915a706ee95c5a03751cfd0f1ae75473bd3e930d8564ee9ad32a81597131bd66 +size 164286 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dd411850445529a0a570699a1c1e2b6e3a3ec1a --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30fc17318da4ca68872d2de3e76a097902c4af59b816d326de9182a363e8b49b +size 61342 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b6249fe9b9ce6baa325ad8c344745ce86522b7 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/87c64bd7d33fca8b9b29228c80ddf175_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568288407389690080f2a1b689f7c1fcd00a7b217c16b6181bd7ecd9fc2b9a11 +size 171439 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f9e3ded3398381101427949108a1cf6abe0ccff --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee71fbb2489551e01fac5a6b7013c15e21d4dcf1f6807dfa62e47b1da9c5bc38 +size 16916 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..578a283366285dd74efa7bcc2f27ca3fe4a06796 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d764e11b0434cfbd3ffee36e391d155a3fb3d1a129666812ae0e1392eb63945 +size 180577 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c8de7571ed5b296f6c59f00f3f5bee34d77edf7 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc03a6de44094b7fc6f52b6a0c0b6471c740a5fec2137588e52a69e781869b2e +size 104159 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64447172ce0d7a9a283b6c57d8dcf508ac8a3913 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcda518e3a01b2db74ad2997a30a766bfc7fab17638c946e7bb2370ce242c731 +size 20696 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4312f0401cd6dc2644733cc40e68727b0dc0737 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6554db527eafd4e1767b92c63d0ee18241502daad7941ed70763a53e0cc8472 +size 180227 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..842eecbfa28d18d3a7ff8e8b7936b7215993f740 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b51b32ba249beb5135b5745e47570a2769762666d059ea6e3649b93bcf1ebc3 +size 15527 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a094fc5cd9f2823932b133fdf3209a7250c0151 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f752cdd6ef96a44eecca531b69c9f5fe78fb51d35d9e734a23f20a6f371f5c6 +size 42489 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..680bd55456e4604e1032136c23da14f1f48b0905 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b7c5ae8f94c221072fd84040edaf18ebccb63596e8418165b90c063b75ae77d +size 20221 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e67ba3c899f41522e211a86fdec591ebd81c5902 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd19e2216f29e665ea4055d0e59709744e6a62e131f0b3a943774d7b4df6c32f +size 191858 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd1e1d20bd64b8b3d699a82664e3a102f6a4e2c3 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9931b95868c2780ae7cb82726d9970301b4f843ec21c49e20ef0710492cb485d +size 159562 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a301e7d33414b70744a533d93120be93324d65f --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495ee7941c7600e88a0c1c54f16a28f3f2fc1e38b184a86e63ebbaa77fa26f1d +size 182159 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f5859c5c48f5d34007fbcf195e9a901152fac55 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2343cbc5f74a9444087383a942b11d6fb8faa4202a66a973ae0256141b0bc34c +size 116046 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef30321f1688fcfa1098c82c660d48053474e663 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a9592172d2218d818199141ad6c800c2498c4508b1c874611b1dbeabd2697a2 +size 26042 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7308feb7633250888d5576fdf2f1efcc692fbb31 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c232d91285b9bdbafefb489e0ab2aaa21fccbd7fb70cda9fd86faa0098dc3d9 +size 146415 diff --git a/marked/G/T-REC-G.8032-202003-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.8032-202003-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a75aeb14004b3be2fb6793e3e9da11add8b2239 --- /dev/null +++ b/marked/G/T-REC-G.8032-202003-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc53e134ecbd197891cf673c0df290f4267b3bc8a1aea1bd3f08f56d253ec0b +size 115574 diff --git a/marked/G/T-REC-G.808.2-201908-I_PDF-E/raw.md b/marked/G/T-REC-G.808.2-201908-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ed7c5dad2ec83410e20e8467d5e6c1161f792a9e --- /dev/null +++ b/marked/G/T-REC-G.808.2-201908-I_PDF-E/raw.md @@ -0,0 +1,757 @@ + + +International Telecommunication Union + +# **ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +# **G.808.2** + +(08/2019) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital networks – General aspects + +--- + +**Generic protection switching – Ring protection** + +Recommendation ITU-T G.808.2 + +**ITU-T** + +![ITU logo](1d7527f4316cfe2d342b08d1653d1592_img.jpg) + +The logo of the International Telecommunication Union (ITU) features a stylized globe with a red lightning bolt striking across it. The letters 'ITU' are prominently displayed in blue and white within the globe's design. + +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.808.2 + +# Generic protection switching – Ring protection + +## Summary + +Recommendation ITU-T G.808.2 defines the generic functional models, characteristics and processes associated with various ring protection schemes for connection oriented networks; e.g., optical transport networks (OTNs), synchronous digital hierarchy (SDH) networks, and multi-protocol label switching – transport profile (MPLS-TP) networks. It also defines the objectives and applications for these schemes. The protection scheme described in this Recommendation is shared ring protection (SRP). + +Generic functional models, characteristics and processes for linear protection and interconnected subnetwork protection schemes are defined in other Recommendations. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.808.2 | 2013-11-22 | 15 | 11.1002/1000/7504 | +| 2.0 | ITU-T G.808.2 | 2019-08-29 | 15 | 11.1002/1000/13998 | + +## Keywords + +MPLS-TP, OTN, ring protection, SDH. + +--- + +\* 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 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..... | 2 | +| 4 | Abbreviations and acronyms ..... | 2 | +| 5 | Conventions ..... | 3 | +| 6 | Individual and group protection concept ..... | 3 | +| 6.1 | Individual protection ..... | 3 | +| 6.2 | Group protection..... | 4 | +| 7 | Architecture and traffic types ..... | 4 | +| 7.1 | Protection classes..... | 4 | +| 7.2 | Traffic types..... | 6 | +| 7.3 | Architecture types..... | 7 | +| 8 | Switching types..... | 9 | +| 9 | Operation types..... | 9 | +| 10 | Switching protocol and ring topology information ..... | 9 | +| 11 | Functional models for ring protection ..... | 10 | +| 11.1 | Functional models for SLRing ..... | 10 | +| 11.2 | Functional models for DLRing..... | 13 | +| 12 | Multi-ring scenario ..... | 15 | +| 13 | Protection switching performance ..... | 15 | +| 14 | Hold-off timer ..... | 15 | +| 15 | Wait-to-restore timer ..... | 16 | +| 16 | Automatic protection switching (APS) signal ..... | 16 | +| 17 | Blank clause..... | 17 | +| 18 | External commands ..... | 17 | +| 19 | Automatic commands ..... | 18 | +| 20 | Priority ..... | 19 | +| 21 | SF and SD trigger conditions..... | 20 | +| 22 | Mechanisms to prevent misconnections ..... | 20 | +| 22.1 | Circuit-switched technologies ..... | 20 | +| 22.2 | Packet switched technologies ..... | 21 | + + + +## Recommendation ITU-T G.808.2 + +# Generic protection switching – Ring protection + +# 1 Scope + +This Recommendation describes the generic aspects of ring protection switching. It covers synchronous digital hierarchy (SDH), optical transport network (OTN), and multi-protocol label switching – transport profile (MPLS-TP) based protection schemes. Ethernet ring protection scheme is not covered in this version of the Recommendation. + +Overviews of ring protection and dual node subnetwork (e.g., dual ring) interconnect schemes will be provided in other 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.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks*. +- [ITU-T G.798] Recommendation ITU-T G.798 (2017), *Characteristics of optical transport network hierarchy equipment functional blocks*. +- [ITU-T G.808] Recommendation ITU-T G.808 (2016), *Terms and definitions for network protection and restoration*. +- [ITU-T G.841] Recommendation ITU-T G.841 (1998), *Types and characteristics of SDH network protection architectures*. +- [ITU-T G.8121] Recommendation ITU-T G.8121/Y.1381 (2018), *Characteristics of MPLS-TP equipment functional blocks*. +- [ITU-T M.495] Recommendation ITU-T M.495 (1988), *Transmission restoration and transmission route diversity: terminology and general principles*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +- 3.1.1 long path [ITU-T G.841] +- 3.1.2 non-revertive (protection) operation [ITU-T G.808] +- 3.1.3 revertive (protection) operation [ITU-T G.808] +- 3.1.4 ring switching [ITU-T G.841] +- 3.1.5 short path [ITU-T G.841] +- 3.1.6 span switching [ITU-T G.841] + +### 3.1.7 switching time [ITU-T G.808] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 extra traffic:** This is the traffic that will be discarded as soon as protection of the normal traffic is required. It will have the lowest availability of the three types of traffic because every protection switch in the ring affects it. + +**3.2.2 non-pre-emptible unprotected traffic:** This is the traffic that will not be affected by the protection switch. It will have availability between that of the normal traffic and the extra traffic as it will be affected only by a defect in a section it passes. + +**3.2.3 normal traffic:** This is the traffic that will be protected and will have the highest availability. + +**3.2.4 ring map:** This is a map (table) present in each node on a ring that contains information regarding the order in which the nodes appear on the ring including their node IDs. + +NOTE – Also present in each node is a ring circuit map, containing the cross-connection (added, dropped, and passed-through client traffic) maps of all nodes in the ring with the squelch table per node as a subset. + +**3.2.5 span:** A bidirectional adjacency between two nodes that participate in a shared ring protection (SRP) mechanism, in the layer in which the SRP mechanism operates. + +**3.2.6 steering:** A protection method in which a source node redirects a traffic to the ring section into the direction retaining connectivity to a destination node. + +**3.2.7 wrapping:** The transmission of the traffic into the opposing direction in the ring, in order to route around a fault in a given ring segment. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|--------|-------------------------------------------| +| AIS | Alarm Indication Signal | +| APS | Automatic Protection Switching | +| BER | Bit Error Rate | +| DEG | Degraded | +| DLRing | Dedicated section Link Ring | +| ET | Extra Traffic (signal) | +| EXER-R | Exercise – Ring | +| EXER-S | Exercise – Span | +| FS-R | Forced Switch to protection – Ring | +| FS-S | Forced Switch to protection – Span | +| HO | Hold-Off | +| ID | Identifier | +| LOW-R | Lockout of Working channels – Ring switch | +| LOW-S | Lockout of Working channels – Span switch | +| LP-S | Lockout of Protection – Span | +| LSP | Label Switched Path | + +| | | +|---------|-----------------------------------------------| +| MPLS | Multi-Protocol Label Switching | +| MPLS-TP | MPLS – Transport Profile | +| MS-N | Multiplex Section – N | +| MS-R | Manual Switch to protection – Ring | +| MS-S | Manual Switch to protection – Span | +| NR | No Request | +| NUT | Non-pre-emptible Unprotected Traffic (signal) | +| OTN | Optical Transport Network | +| RR-R | Reverse Request – Ring | +| RR-S | Reverse Request – Span | +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SD-P | Signal Degrade – Protection | +| SD-R | Signal Degrade – Ring | +| SD-S | Signal Degrade – Span | +| SF | Signal Fail | +| SF-P | Signal Fail – Protection | +| SF-R | Signal Fail – Ring | +| SF-S | Signal Fail – Span | +| SLRing | Shared section Link Ring protection | +| SPRing | Shared Protection Ring | +| SRP | Shared Ring Protection | +| SSF | Server Signal Fail | +| TSD | Trail Signal Degrade | +| TSF | Trail Signal Fail | +| TT | Trail Termination | +| VC-n | Virtual Container – n | +| WTR | Wait-To-Restore | + +# 5 Conventions + +None. + +# 6 Individual and group protection concept + +## 6.1 Individual protection + +In individual protection, the protection mechanism relies on defects detected in the server layer that affect all individual protected entities in the physical section at the same time. In general, individual protection is used in synchronous digital hierarchy (SDH) and optical transport network (OTN) technologies in physical rings. + +## 6.2 Group protection + +In group protection, the protection mechanism relies on defects detected by one of the members of the group or by the whole group in a logical section. + +# 7 Architecture and traffic types + +In general, shared ring protection mechanisms operate on a ring of two or more nodes. In the case of MPLS-TP, the minimum number of nodes of a ring required for proper ring protection operation is three. Nodes on a ring are adjacent to each other in the layer network in which the shared ring protection mechanism operates, with bidirectional spans between each pair of nodes. The layer network in which a shared ring protection mechanism operates is connection-oriented; it may be circuit switched or packet switched. + +Each bidirectional span on the ring provides, in each direction, a working transport entity, a protection transport entity and, optionally, an entity to transport non-pre-emptible unprotected traffic (NUT), as shown in Figure 7-1. + +![Diagram of a ring topology with six nodes (Node #1 to Node #6) connected in a circular fashion. Each node is connected to two adjacent nodes via bidirectional spans. Each span consists of three parallel lines representing different traffic types: Working (top, light gray), NUT (middle, white), and Protection (bottom, dark gray). Arrows indicate the direction of traffic flow. Tributaries are shown entering and leaving each node. A legend in the center identifies the traffic types by color: Working (light gray), NUT (white), and Protection (dark gray). The diagram is labeled G.808.2(13)_F7-1 in the bottom right corner.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates a ring topology with six nodes labeled Node #1 through Node #6. The nodes are arranged in a circle, with Node #1 at the bottom left, Node #2 at the top left, Node #3 at the top right, Node #4 at the top right, Node #5 at the bottom right, and Node #6 at the bottom left. Each node is connected to two adjacent nodes via bidirectional spans. Each span is represented by three parallel lines: a light gray line for 'Working' traffic, a white line for 'NUT' (Non-Pre-emptible Unprotected Traffic), and a dark gray line for 'Protection' traffic. Arrows on the lines indicate the direction of traffic flow. Tributaries are shown entering and leaving each node. A legend in the center of the ring identifies the traffic types: 'Working' (light gray), 'NUT' (white), and 'Protection' (dark gray). The diagram is labeled 'G.808.2(13)\_F7-1' in the bottom right corner. + +Diagram of a ring topology with six nodes (Node #1 to Node #6) connected in a circular fashion. Each node is connected to two adjacent nodes via bidirectional spans. Each span consists of three parallel lines representing different traffic types: Working (top, light gray), NUT (middle, white), and Protection (bottom, dark gray). Arrows indicate the direction of traffic flow. Tributaries are shown entering and leaving each node. A legend in the center identifies the traffic types by color: Working (light gray), NUT (white), and Protection (dark gray). The diagram is labeled G.808.2(13)\_F7-1 in the bottom right corner. + +Figure 7-1 – Ring topology + +## 7.1 Protection classes + +### 7.1.1 Shared section link ring protection (SLRing) + +Shared section link ring protection requires only two links for each span of the ring and forms two rings. Each link in the ring carries both working transport entities and protection transport entities. On each ring, up to half the entities are defined as working transport entities and up to half are defined as protection transport entities, that is to say working transport entities go around the ring clockwise and anti-clockwise, same for protection transport entities. The normal traffic carried on working transport entities is protected by the protection transport entities travelling in the other ring in the opposite direction (see Figure 7-2). This enables the bidirectional transport of normal traffic. + +![Diagram of shared section link ring protection (SLRing) showing six nodes (A, B, C, D, E, F) in a ring. Node A is connected to B and F; B to A and C; C to B and D; D to C and E; E to D and F; F to E and A. Each node has external connections. Between nodes A and B, there are two channels: a solid line labeled W(a) (Working channel) and a dashed line labeled P(b) (Protection channel). Between nodes F and E, there are two channels: a solid line labeled W(b) (Working channel) and a dashed line labeled P(a) (Protection channel). Arrows indicate traffic flow. A legend at the bottom shows a solid line for 'Working channel' and a dashed line for 'Protection channel'. The text 'G.808.2(19)_F7-2' is in the bottom right.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram of shared section link ring protection (SLRing) showing six nodes (A, B, C, D, E, F) in a ring. Node A is connected to B and F; B to A and C; C to B and D; D to C and E; E to D and F; F to E and A. Each node has external connections. Between nodes A and B, there are two channels: a solid line labeled W(a) (Working channel) and a dashed line labeled P(b) (Protection channel). Between nodes F and E, there are two channels: a solid line labeled W(b) (Working channel) and a dashed line labeled P(a) (Protection channel). Arrows indicate traffic flow. A legend at the bottom shows a solid line for 'Working channel' and a dashed line for 'Protection channel'. The text 'G.808.2(19)\_F7-2' is in the bottom right. + +**Figure 7-2 – Working transport entity and protection transport entity in shared section link ring protection** + +The normal traffic carried on working transport entity W(a) is protected by protection transport entity P(a), and the normal traffic carried on working transport entity W(b) is protected by protection transport entity P(b). + +If a shared section link is carried directly over a fibre, the term 2-Fibre SPRing may be used instead of SLRing. + +### 7.1.2 Dedicated section link ring protection (DLRing) + +Dedicated section link ring protection requires four links for each span of the ring and forms four rings. Working and protection transport entities are carried over different rings: two rings transmitting in opposite directions carry the working transport entities; while two rings, also transmitting in opposite directions, carry the protection transport entities (see Figure 7-3). + +![Diagram of dedicated section link ring protection (DLRing) showing six nodes (A, B, C, D, E, F) in a ring. Node A is connected to B and F; B to A and C; C to B and D; D to C and E; E to D and F; F to E and A. Each node has external connections. Between nodes A and B, there are four channels: two solid lines (one labeled W(a), one labeled P(b)) and two dashed lines (one labeled P(a), one labeled W(b)). Between nodes F and E, there are four channels: two solid lines (one labeled W(b), one labeled P(a)) and two dashed lines (one labeled P(b), one labeled W(a)). Arrows indicate traffic flow. A legend at the bottom shows a solid line for 'Working channel' and a dashed line for 'Protection channel'. The text 'G.808.2(19)_F7-3' is in the bottom right.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +Diagram of dedicated section link ring protection (DLRing) showing six nodes (A, B, C, D, E, F) in a ring. Node A is connected to B and F; B to A and C; C to B and D; D to C and E; E to D and F; F to E and A. Each node has external connections. Between nodes A and B, there are four channels: two solid lines (one labeled W(a), one labeled P(b)) and two dashed lines (one labeled P(a), one labeled W(b)). Between nodes F and E, there are four channels: two solid lines (one labeled W(b), one labeled P(a)) and two dashed lines (one labeled P(b), one labeled W(a)). Arrows indicate traffic flow. A legend at the bottom shows a solid line for 'Working channel' and a dashed line for 'Protection channel'. The text 'G.808.2(19)\_F7-3' is in the bottom right. + +**Figure 7-3 – Working transport entity and protection transport entity in dedicated section link ring protection** + +The normal traffic carried on working transport entity W(a) is protected either by protection transport entity P(b) in case of span-switch or by protection transport entity P(a) in case of ring-switch. Similarly, the normal traffic carried on working transport entity W(b) is protected either by protection transport entity P(a) in case of span-switch or by protection transport entity P(b) in case of ring-switch. + +If a dedicated section link is carried directly over fibres the term 4-Fibre SPRing may be used instead of DLRing. + +## 7.2 Traffic types + +### 7.2.1 Normal (protected) traffic + +Normal traffic uses resources within the working transport entity, and can be protected by resources within the protection transport entity during protection switching conditions. All shared protection rings support normal traffic. + +In circuit switched networks, a shared ring protection mechanism is typically described as existing in a server layer network, while the actual protection switching is implemented as group protection in a client layer network. For example, SDH MS-SPRing is described as a sublayer of the MS layer, but the virtual container – n (VC-n) within the multiplex section – N (MS-N) are wrapped or steered as a result of failures. + +In packet switched networks, a shared ring protection mechanism typically uses unique identifiers for each working or protection transport entity and for each egress node at which these transport entities terminate, allowing one or more logical rings to share the same server layer. + +### 7.2.2 Non-pre-emptible unprotected traffic (NUT) + +Non-pre-emptible unprotected traffic (NUT) has no protection associated with it, but cannot be dropped from the network to allow protection of other traffic signals. It may be present on the server layer supporting working transport entity and/or the server layer supporting the protection transport entity. + +In a circuit switched network, NUT must be specifically identified within the protection mechanism. For example, SDH MS-SPRing is described as a sub-layer of the MS layer. The use of NUT means that some VC-n within the MS-N signal are not protected, which is only possible if the actual switching of traffic is occurring in the VC-n layer. In this case, if NUT is configured for a particular VC-n timeslot in the working transport entity, the corresponding VC-n in the protection transport entity is also designated for NUT (since it is not otherwise needed for protection). + +In the case of a ring based on packet switching, the shared ring protection mechanism is not aware of the NUT because the working and protection transport entities use specific identifiers. For example, MPLS-TP uses tunnel labels to identify shared protection rings. NUT LSPs do not have the tunnel label, and would thus be excluded from the actions of the MPLS-TP shared ring protection scheme. + +### 7.2.3 Extra traffic (ET) + +Extra traffic (ET) allows the use of the protection transport entities for additional traffic signals during normal operation in ring architectures. When a protection switch occurs, this traffic can be dropped. Extra traffic provides a less reliable service than either protected traffic or non-pre-emptible unprotected traffic. It is unrelated to the normal traffic signal. + +In circuit switched networks, extra traffic must be specifically identified as such, so that it can be pre-empted in the event of a failure that requires use of the resources in the protection transport entity to protect normal traffic. + +In packet switched networks, the existence of a connection does not guarantee that traffic for that connection will be forwarded; forwarding decisions are taken on a per-packet basis based on priority of the traffic available to be switched. As such, extra traffic needs to be lower in priority than all normal traffic and NUT that is using the protection transport entity, but it does not have to be explicitly disconnected when a failure occurs on the working transport entity. Extra traffic will continue to be forwarded as bandwidth allows even when a failure has occurred in the working + +transport entity. For example, MPLS-TP uses tunnel labels to identify shared protection rings. LSPs that are ET will not have the tunnel label, and will have lower priority than the tunnel or any NUT. + +## 7.3 Architecture types + +### 7.3.1 Wrapping protection + +The normal traffic signal is wrapped from the working transport entity to the protection transport entity in the nodes adjacent to the failed section or node. + +During a ring protection switch, normal traffic signal transmitted toward the failed section/node is switched (wrapped) at the node just before the failure to the protection transport entity in the opposite direction (away from the failure). This bridged traffic signal travels around the ring on the protection transport entities to the node just after the failure where the normal traffic signal from the protection transport entity is switched (wrapped) back onto the working transport entity. In the other direction, the normal traffic signal is bridged and switched in the same manner. + +Figure 7-4 illustrates a ring protection switch in response to a section failure. + +Since the protection transport entity of each section (except the failed section) is used for recovery, the protection capacity is effectively shared by all sections. + +![Diagram of a ring network illustrating wrapping protection. The ring consists of six nodes: Node #1, Node #2, Node #3, Node #4, Node #5, and Node #6. A failure is indicated between Node #2 and Node #3. At Node #2, the working path (solid black line) is interrupted, and the traffic is wrapped (indicated by a red dashed line and the label 'wrap') onto the protection path (red dashed line) in the opposite direction. At Node #3, the traffic is wrapped back onto the working path. The protection path (red dashed line) travels around the ring in the opposite direction of the working path (solid black line). The diagram shows the working path continuing from Node #1 through Node #6, Node #5, and Node #4 to Node #3, where it is interrupted. The protection path (red dashed line) travels from Node #2, through Node #1, Node #6, Node #5, Node #4, and Node #3, where it is wrapped back onto the working path. The working path then continues from Node #3 through Node #4, Node #5, Node #6, and Node #1 to Node #2. The protection path (red dashed line) also continues from Node #3 through Node #4, Node #5, Node #6, and Node #1 to Node #2. The failure is indicated by a red dashed line and the label 'Failure' between Node #2 and Node #3. The diagram is labeled G.808.2(19)_F7-4.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +Legend: +---> Protection path (red dashed line) +-> Working path (solid black line) + +Diagram of a ring network illustrating wrapping protection. The ring consists of six nodes: Node #1, Node #2, Node #3, Node #4, Node #5, and Node #6. A failure is indicated between Node #2 and Node #3. At Node #2, the working path (solid black line) is interrupted, and the traffic is wrapped (indicated by a red dashed line and the label 'wrap') onto the protection path (red dashed line) in the opposite direction. At Node #3, the traffic is wrapped back onto the working path. The protection path (red dashed line) travels around the ring in the opposite direction of the working path (solid black line). The diagram shows the working path continuing from Node #1 through Node #6, Node #5, and Node #4 to Node #3, where it is interrupted. The protection path (red dashed line) travels from Node #2, through Node #1, Node #6, Node #5, Node #4, and Node #3, where it is wrapped back onto the working path. The working path then continues from Node #3 through Node #4, Node #5, Node #6, and Node #1 to Node #2. The protection path (red dashed line) also continues from Node #3 through Node #4, Node #5, Node #6, and Node #1 to Node #2. The failure is indicated by a red dashed line and the label 'Failure' between Node #2 and Node #3. The diagram is labeled G.808.2(19)\_F7-4. + +Figure 7-4 – Wrapping + +### 7.3.2 Steering protection + +The normal traffic signal is switched to the protection transport entity at its ingress and egress nodes. + +During a ring protection switch, normal traffic signal transmitted toward the failed section/node is switched (steered) at the node where it enters the ring to the protection transport entity in the opposite direction (away from the failure). This bridged traffic signal travels around the ring on the protection transport entities to the node where the normal traffic signal exits the ring and where the normal traffic signal from the protection transport entity is switched (steered) back to the output. In the other direction, the normal traffic signal is bridged and switched in the same manner. + +Figure 7-5 illustrates a ring protection switch in response to a section failure. + +Since the protection transport entity of each section (except the failed section) is used for recovery, the protection capacity is effectively shared by all spans. + +![Diagram of a ring network showing steering protection. A failure is indicated between Node #2 and Node #3. Nodes #1 and #4 are labeled 'steer'. Solid black arrows represent working paths, and dashed red arrows represent protection paths. The diagram is labeled G.808.2(19)_F7-5.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg) + +The diagram illustrates a ring network with six nodes labeled Node #1 through Node #6. A failure is indicated between Node #2 and Node #3. Nodes #1 and #4 are labeled 'steer'. Solid black arrows represent working paths, and dashed red arrows represent protection paths. The diagram is labeled G.808.2(19)\_F7-5. + +Diagram of a ring network showing steering protection. A failure is indicated between Node #2 and Node #3. Nodes #1 and #4 are labeled 'steer'. Solid black arrows represent working paths, and dashed red arrows represent protection paths. The diagram is labeled G.808.2(19)\_F7-5. + +**Figure 7-5 – Steering** + +### 7.3.3 Short wrapping protection + +The normal traffic signal is wrapped from the working transport entity to the protection transport entity only at the upstream node of the failed section or node and exits the ring at the egress node. + +During a ring protection switch, normal traffic signal transmitted toward the failed section/node is switched (wrapped) at the node just before the failure to the protection transport entity in the opposite direction (away from the failure). This bridged traffic signal travels around the ring on the protection transport entities to the node where the normal traffic signal from the protection transport entity is switched (steered) to the output. In the other direction, the normal traffic signal is bridged and switched in the same manner. + +Figure 7-6 illustrates a ring protection switch in response to a section failure. + +Short wrapping is an optimization to wrapping protection in terms of latency and bandwidth consumption during protection switching. However, the protected bidirectional normal traffics are not co-routed due to the discrepancy of the switching nodes used in each direction. + +Since the protection transport entity of each section (except the failed section) is used for recovery, the protection capacity is effectively shared by all spans. + +![Diagram of a ring network showing short wrapping protection. A failure is indicated between Node #2 and Node #3. Node #2 performs a 'wrap' operation, and Node #4 performs a 'steer' operation. The protection path is shown as a dashed red line, and the working path as a solid black line. Nodes are labeled Node #1 through Node #6. A legend at the bottom left identifies the dashed red line as the 'Protection path' and the solid black line as the 'Working path'. The diagram is labeled G.808.2(19)_F7-6.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +Diagram of a ring network showing short wrapping protection. A failure is indicated between Node #2 and Node #3. Node #2 performs a 'wrap' operation, and Node #4 performs a 'steer' operation. The protection path is shown as a dashed red line, and the working path as a solid black line. Nodes are labeled Node #1 through Node #6. A legend at the bottom left identifies the dashed red line as the 'Protection path' and the solid black line as the 'Working path'. The diagram is labeled G.808.2(19)\_F7-6. + +**Figure 7-6 – Short wrapping** + +# 8 Switching types + +- Shared ring protection switching is bidirectional. + +# 9 Operation types + +The protection operation types can be a *revertive* operation type or a *non-revertive* operation type. + +- In a revertive (protection) operation, the normal traffic signal always returns to (or remains on) the working transport entity if the switch requests are terminated, that is to say, when the working transport entity has recovered from the defect or the external request is cleared. +- In non-revertive (protection) operation, the normal traffic signal does not return to the working transport entity if the switch requests are terminated. + +NOTE – Non-revertive switching is not recommended because the protection entities are shared. + +# 10 Switching protocol and ring topology information + +Shared ring protection requires that all nodes in the ring coordinate their actions of bridging and selecting. Therefore, ring nodes maintain a ring map that describes the topology of the ring and communicate with each other via a protocol carried over the automatic protection switching (APS) channel. + +The ring map provides an ordered list of the node IDs of all the nodes in the ring, so every node is aware of how the nodes are connected in the ring. This information is used in conjunction with the APS protocol to make switching decisions. The ring map may be provisioned by management or exchanged among the nodes via other control protocols. + +There are two basic requirements for a protection protocol: + +- 1) The prevention of misconnections. +- 2) The minimization of the number of communication cycles among the ring nodes in order to minimize the protection switching time. + +The details of the ring map and the APS protocol are technology-specific. + +# 11 Functional models for ring protection + +## 11.1 Functional models for SLRing + +Figure 11-1 shows the bidirectional functional model of the connection function of the client layer that is protected by the shared section link ring protection in each node of a protected ring when no protection switch is activated. + +![Figure 11-1: Shared section link ring protection functional model. The diagram shows a central node 'node i' with connections to 'To node (i-1)' and 'To node (i+1)'. At the top, 'Normal traffic' and 'Extra traffic' are indicated with dashed lines, and 'NUT' with a solid line. These connect to 'Client_TT' (yellow and green triangles). Below, 'Client_C' is a central block. The node has two 'APS/SSF' blocks on either side. Connections are labeled with 'a' and 'b' for capacity and 'w' (working), 'p' (protection), and 'n' (NUT) for transport entities. At the bottom left, 'Server/Client_A' and 'Server_TT' are shown.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Figure 11-1: Shared section link ring protection functional model. The diagram shows a central node 'node i' with connections to 'To node (i-1)' and 'To node (i+1)'. At the top, 'Normal traffic' and 'Extra traffic' are indicated with dashed lines, and 'NUT' with a solid line. These connect to 'Client\_TT' (yellow and green triangles). Below, 'Client\_C' is a central block. The node has two 'APS/SSF' blocks on either side. Connections are labeled with 'a' and 'b' for capacity and 'w' (working), 'p' (protection), and 'n' (NUT) for transport entities. At the bottom left, 'Server/Client\_A' and 'Server\_TT' are shown. + +**Figure 11-1 – Shared section link ring protection functional model** + +The following types of traffic will be transported over the section between adjacent nodes: + +- normal traffic. It is transported in the working transport entity ('w' in Figure 11-1). +- extra traffic. It is transported in the protection transport entity ('p' in Figure 11-1). +- non–pre-emptible unprotected traffic (NUT). It is transported in the NUT transport entity ('n' in Figure 11-1). + +The maximum payload capacity of the working transport entity is equal to the capacity of the protection transport entity, as indicated by 'a' in Figure 11-1. The payload capacity of the NUT transport entity is different from the working and protection transport entity as indicated by 'b' in Figure 11-1. The values 'a' and 'b' are provisioned to have the same value in all nodes of the ring. Note that the 'a' and 'b' entities will carry traffic originating locally or traffic passed through from node (i-1) to node (i+1) and vice versa. + +In general, the following limits apply: $0 < a \leq N/2$ , $0 \leq b < N$ and $(2a + b) \leq N$ where $N$ is the total bandwidth capacity of the server section. + +### 11.1.1 Functional models for wrapping protection on a SLRing + +Figure 11-2 shows the functional model in a node adjacent to the failed section or node when wrapping protection is activated on a SLRing. + +![Functional model of a node adjacent to a failure in wrapping protection on a SLRing. The diagram shows traffic paths (Normal, Extra, NUT) entering a central node 'i' from 'Client_C' and being rerouted via 'APS/SSF' and 'Server/Client_A' components to 'node (i-1)'. The path to 'node (i+1)' is shown as failed with a red 'X'.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +This diagram illustrates the functional model of a node adjacent to a failure in wrapping protection on a SLRing. At the top, three traffic types are shown: 'Normal traffic' (dashed line), 'Extra traffic' (dashed line), and 'NUT' (dashed line). These enter from 'Client\_C' (represented by a central oval) through 'Client\_TT' (yellow triangles). The traffic is processed by 'APS/SSF' (Adaptive Protection and Switching and Steering Function) and 'Server/Client\_A' (Server/Client Adapter) components. The 'Server/Client\_A' has three ports labeled 'w', 'p', and 'n'. The traffic is then sent 'To node (i - 1)' via the 'Server\_TT' (yellow triangle). The path to 'node (i + 1)' is shown as failed, indicated by a red 'X' on the line. The diagram is labeled 'G.808.2(19)\_F11-2'. + +Functional model of a node adjacent to a failure in wrapping protection on a SLRing. The diagram shows traffic paths (Normal, Extra, NUT) entering a central node 'i' from 'Client\_C' and being rerouted via 'APS/SSF' and 'Server/Client\_A' components to 'node (i-1)'. The path to 'node (i+1)' is shown as failed with a red 'X'. + +**Figure 11-2 – Functional model of a node adjacent to a failure in wrapping protection on a SLRing** + +Figure 11-3 shows the functional model of an intermediate (non-adjacent) node when wrapping protection is activated on a SLRing. + +![Functional model of an intermediate node in wrapping protection on a SLRing. The diagram shows traffic paths (Normal, Extra, NUT) entering from 'Client_C', being processed by 'APS/SSF' and 'Server/Client_A' components, and then being rerouted to 'node (i+1)' via the 'Server_TT'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +This diagram illustrates the functional model of an intermediate node in wrapping protection on a SLRing. At the top, three traffic types are shown: 'Normal traffic' (dashed line), 'Extra traffic' (dashed line), and 'NUT' (dashed line). These enter from 'Client\_C' (represented by a central oval) through 'Client\_TT' (yellow triangles). The traffic is processed by 'APS/SSF' (Adaptive Protection and Switching and Steering Function) and 'Server/Client\_A' (Server/Client Adapter) components. The 'Server/Client\_A' has three ports labeled 'w', 'p', and 'n'. The traffic is then sent 'To node (i + 1)' via the 'Server\_TT' (yellow triangle). The diagram is labeled 'G.808.2(19)\_F11-3'. + +Functional model of an intermediate node in wrapping protection on a SLRing. The diagram shows traffic paths (Normal, Extra, NUT) entering from 'Client\_C', being processed by 'APS/SSF' and 'Server/Client\_A' components, and then being rerouted to 'node (i+1)' via the 'Server\_TT'. + +**Figure 11-3 – Functional model of an intermediate node in wrapping protection on a SLRing** + +### 11.1.2 Functional models for steering protection on a SLRing + +Figure 11-4 shows the functional model in a node adjacent to the failed section or node when steering protection is activated on a SLRing. + +![Figure 11-4: Functional model of an ingress or egress node of normal traffic signal in steering protection on a SLRing. The diagram shows a central node 'i' connected to 'Client_C' and 'NUT' entities. Above 'NUT' are 'Normal traffic', 'Extra traffic', and 'NUT' labels. On the left, 'Client_TT' (yellow triangles) connects to 'APS/SSF' (yellow triangle) labeled 'Server/Client_A', which then connects to 'Server_TT' (yellow triangle) and 'To node (i - 1)'. On the right, 'APS/SSF' (green triangle) labeled 'Server/Client_A' connects to 'Server_TT' (green triangle) and 'To node (i + 1)'. Solid blue lines represent normal traffic paths, while dashed blue lines represent extra traffic paths. A red 'X' is on the right output path. Reference G.808.2(19)_F11-4 is at the bottom right.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Figure 11-4: Functional model of an ingress or egress node of normal traffic signal in steering protection on a SLRing. The diagram shows a central node 'i' connected to 'Client\_C' and 'NUT' entities. Above 'NUT' are 'Normal traffic', 'Extra traffic', and 'NUT' labels. On the left, 'Client\_TT' (yellow triangles) connects to 'APS/SSF' (yellow triangle) labeled 'Server/Client\_A', which then connects to 'Server\_TT' (yellow triangle) and 'To node (i - 1)'. On the right, 'APS/SSF' (green triangle) labeled 'Server/Client\_A' connects to 'Server\_TT' (green triangle) and 'To node (i + 1)'. Solid blue lines represent normal traffic paths, while dashed blue lines represent extra traffic paths. A red 'X' is on the right output path. Reference G.808.2(19)\_F11-4 is at the bottom right. + +**Figure 11-4 – Functional model of an ingress or egress node of normal traffic signal in steering protection on a SLRing** + +Figure 11-5 shows the functional model of an intermediate (non-adjacent) node when steering protection is activated on a SLRing. The normal traffic signal is switched to the protection transport entity if the normal traffic signal is affected by the failed section or node as indicated by blue dashed lines in Figure 11-5. Otherwise, the normal traffic signal keeps to be transported by the working transport entity as indicated by blue solid lines in Figure 11-5. The protection transport entity may be used for extra traffic if the protection transport entity is not occupied by the normal traffic signal even when the steering protection is activated as indicated by red dashed lines in Figure 11-5. + +![Figure 11-5: Functional model of an intermediate node in steering protection on a SLRing. The diagram shows a central node 'i' connected to 'Client_C' and 'NUT' entities. Above 'NUT' are 'Normal traffic', 'Extra traffic', and 'NUT' labels. On the left, 'Client_TT' (yellow triangles) connects to 'APS/SSF' (yellow triangle) labeled 'Server/Client_A', which then connects to 'Server_TT' (yellow triangle) and 'To node (i - 1)'. On the right, 'APS/SSF' (green triangle) labeled 'Server/Client_A' connects to 'Server_TT' (green triangle) and 'To node (i + 1)'. Solid blue lines represent normal traffic paths, dashed blue lines represent protection transport paths, and dashed red lines represent extra traffic paths. Reference G.808.2(19)_F11-5 is at the bottom right.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 11-5: Functional model of an intermediate node in steering protection on a SLRing. The diagram shows a central node 'i' connected to 'Client\_C' and 'NUT' entities. Above 'NUT' are 'Normal traffic', 'Extra traffic', and 'NUT' labels. On the left, 'Client\_TT' (yellow triangles) connects to 'APS/SSF' (yellow triangle) labeled 'Server/Client\_A', which then connects to 'Server\_TT' (yellow triangle) and 'To node (i - 1)'. On the right, 'APS/SSF' (green triangle) labeled 'Server/Client\_A' connects to 'Server\_TT' (green triangle) and 'To node (i + 1)'. Solid blue lines represent normal traffic paths, dashed blue lines represent protection transport paths, and dashed red lines represent extra traffic paths. Reference G.808.2(19)\_F11-5 is at the bottom right. + +**Figure 11-5 – Functional model of an intermediate node in steering protection on a SLRing** + +### 11.1.3 Functional models for short wrapping protection on a SLRing + +Figure 11-6 shows the functional model in a node adjacent to the failed section or node when short wrapping protection is activated on a SLRing. The difference from the functional model of the + +wrapping protection shown in Figure 11-2 is that wrapping is performed only in the direction from the working transport entity to the protection transport entity. + +![Functional model of a node adjacent to a failure in short wrapping protection on a SLRing.](7f25db95ce3916c0e09803b861a2f7bc_img.jpg) + +The diagram illustrates the functional model of node *i* adjacent to a failure. At the top, traffic types are categorized as Normal traffic, Extra traffic, and NUT (Non-Preemptible Unprotected Traffic), entering through Client\_TT (Transport Termination) points represented by yellow and green triangles. These connect to a central oval representing Client\_C (Connection function). Below this, the traffic is routed through APS/SSF (Automatic Protection Switching/Server Signal Failure) blocks. On the left, traffic flows to node (*i* – 1) through a Server/Client\_A (Adaptation) block and Server\_TT. On the right, traffic intended for node (*i* + 1) is blocked by a red 'X' indicating a failure. The APS/SSF blocks show internal switching between working (w), protection (p), and normal (n) paths. Blue arrows indicate the flow of traffic within the Client\_C function, showing the wrapping mechanism where traffic is redirected from the failed working path to the protection path. Source label: G.808.2(19)\_F11-6. + +Functional model of a node adjacent to a failure in short wrapping protection on a SLRing. + +**Figure 11-6 – Functional model of a node adjacent to a failure in short wrapping protection on a SLRing** + +Figure 11-7 shows the functional model of an intermediate (non-adjacent) node when short wrapping protection is activated on a SLRing. The normal traffic signal entering the ring is transmitted to the working transport entity, while the normal traffic signal to be exiting the ring is received from the protection transport entity. + +![Functional model of an intermediate node in short wrapping protection on a SLRing.](10781f43062bf3e9601a1e086710556c_img.jpg) + +This diagram shows the functional model of an intermediate node *i*. Similar to Figure 11-6, it features Client\_TT points for Normal traffic, Extra traffic, and NUT at the top, connecting to a central Client\_C oval. Below, traffic is routed through APS/SSF blocks to node (*i* – 1) on the left and node (*i* + 1) on the right via Server/Client\_A and Server\_TT blocks. Unlike Figure 11-6, there is no failure 'X'. Blue arrows within the Client\_C oval show traffic passing through the node on both working and protection paths, as well as local traffic entering and exiting. The APS/SSF blocks show the connectivity between working (w), protection (p), and normal (n) ports. Source label: G.808.2(19)\_F11-7. + +Functional model of an intermediate node in short wrapping protection on a SLRing. + +**Figure 11-7 – Functional model of an intermediate node in short wrapping protection on a SLRing** + +## 11.2 Functional models for DLRing + +Figure 11-8 shows the bidirectional functional model of the connection function of the client layer that is protected by the dedicated section link ring protection in each node of a protected ring when no protection switch is activated. The difference from the functional model of the SLRing shown in + +Figure 11-1 is that the working transport entity and the protection transport entity are carried over two different server sections. + +![Figure 11-8: Dedicated section link ring protection functional model. The diagram shows a ring network with nodes labeled 'node i', 'To node (i-1)', and 'To node (i+1)'. At node i, there are two server sections: Server/Client_A (yellow) and Server/Client_B (green). Client_TT (yellow) and Client_C (green) are connected to these servers. The diagram illustrates traffic paths: 'Normal traffic' (dashed line), 'Extra traffic' (dashed line), and 'NUT' (dashed line). Labels 'a', 'b', and 'c' indicate bandwidth capacities. Other labels include SSF, APS/SSF, and G.808.2(19)_F11-8.](83852ec55d4802521a727926336bedab_img.jpg) + +Figure 11-8: Dedicated section link ring protection functional model. The diagram shows a ring network with nodes labeled 'node i', 'To node (i-1)', and 'To node (i+1)'. At node i, there are two server sections: Server/Client\_A (yellow) and Server/Client\_B (green). Client\_TT (yellow) and Client\_C (green) are connected to these servers. The diagram illustrates traffic paths: 'Normal traffic' (dashed line), 'Extra traffic' (dashed line), and 'NUT' (dashed line). Labels 'a', 'b', and 'c' indicate bandwidth capacities. Other labels include SSF, APS/SSF, and G.808.2(19)\_F11-8. + +**Figure 11-8 – Dedicated section link ring protection functional model** + +The maximum payload capacity of the working transport entity is equal to the capacity of the protection transport entity, as indicated by 'a' in Figure 11-8. The payload capacity of the NUT transport entity is different from the working and protection transport entity as indicated by 'b' or 'c' in Figure 11-8. The values 'a', 'b', and 'c' are provisioned to have the same respective values in all nodes of the ring. Note that the 'a', 'b', and 'c' entities will carry traffic originating locally or traffic passed through from node (i-1) to node (i+1) and vice versa. + +In general, the following limits apply: $0 < a \leq \min(N1, N2)$ , $0 \leq b < N1$ , $0 \leq c < N2$ , $(a + b) \leq N1$ , and $(a + c) \leq N2$ where N1 is the total bandwidth capacity of the server section carrying working transport entities and N2 is the total bandwidth capacity of the server section carrying protection transport entities. + +### 11.2.1 Functional models for span switch protection on a DLRing + +Figure 11-9 shows the functional model in a node adjacent to the failed section or node when span switch protection is activated on a DLRing. + +![Figure 11-9: Functional model of a node adjacent to a failure in span switch protection on a DLRing. The diagram shows a central node 'i' connected to two adjacent nodes, 'i-1' and 'i+1'. Node 'i' contains a 'Client_C' block. Above it, 'Normal traffic', 'Extra traffic', and 'NUT' are shown entering the node. On the left, 'Client_TT' and 'Server/Client_A' (with 'Server_TT') are connected via 'SSF' and 'APS/SSF' blocks. On the right, another 'Server/Client_A' (with 'Server_TT') is connected via 'APS/SSF' and 'SSF' blocks. A failure is indicated by a red 'X' on the line to node 'i+1'. The diagram is labeled 'G.808.2(19)_F11-9'.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Figure 11-9: Functional model of a node adjacent to a failure in span switch protection on a DLRing. The diagram shows a central node 'i' connected to two adjacent nodes, 'i-1' and 'i+1'. Node 'i' contains a 'Client\_C' block. Above it, 'Normal traffic', 'Extra traffic', and 'NUT' are shown entering the node. On the left, 'Client\_TT' and 'Server/Client\_A' (with 'Server\_TT') are connected via 'SSF' and 'APS/SSF' blocks. On the right, another 'Server/Client\_A' (with 'Server\_TT') is connected via 'APS/SSF' and 'SSF' blocks. A failure is indicated by a red 'X' on the line to node 'i+1'. The diagram is labeled 'G.808.2(19)\_F11-9'. + +**Figure 11-9 – Functional model of a node adjacent to a failure in span switch protection on a DLRing** + +NOTE – Functional models for wrapping, steering and short-wrapping protection on a DLRing are identical with those on a SLRing except that the DLRing has two sever sections in each span while the SLRing has only one (see Figure 11-1 and Figure 11-8). + +# 12 Multi-ring scenario + +In actual networks, multi-ring scenarios are widely applied, including tangent rings and intersecting rings (see Figure 12-1). The multi-ring mechanism should inherit and be compatible with the single ring mechanism, to simplify the equipment implementation. + +![Figure 12-1: Multiple rings scenario. The diagram shows two examples of multi-ring topologies. The left example shows two hexagonal rings sharing a common vertical edge (tangent rings). The right example shows two hexagonal rings connected by two parallel horizontal edges (intersecting rings). The diagram is labeled 'G.808.2(13)_F12-1'.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 12-1: Multiple rings scenario. The diagram shows two examples of multi-ring topologies. The left example shows two hexagonal rings sharing a common vertical edge (tangent rings). The right example shows two hexagonal rings connected by two parallel horizontal edges (intersecting rings). The diagram is labeled 'G.808.2(13)\_F12-1'. + +**Figure 12-1 – Multiple rings scenario** + +# 13 Protection switching performance + +The protection switching temporal model derived from [ITU-T M.495] and model parameters are defined in [ITU-T G.808]. + +# 14 Hold-off timer + +Hold-off (HO) timers are intended to operate when a signal is protected by means of nested protection. Those are to allow an inner protection group to restore the traffic signal before the outer protection group tries to do so, in order to limit the number of switch actions. + +Each protection selector may have one hold-off timer. + +A hold-off timer is started when one or more of the SF or SD conditions in the protection group become active, and runs for a non-resettable period which is provisionable from 0 to 10 seconds in steps of X ms. X is 100 ms (SDH, OTN, and MPLS-TP). + +During this period, the modified SF/SD statuses are not passed to the protection switching process. + +When the timer expires, the SF/SD status of all signals are read and passed through to the protection switching process. The protection switching process will react on the new SF/SD status at this point. + +NOTE 1 – An SF/SD condition does not have to be present for the entire duration of the hold-off period, only the state at the expiry of the hold-off timer is relevant. Further, the SF/SD condition that triggers the hold-off timer does not need to be of the same one as the one at the expiry of the hold-off period. + +NOTE 2 – Clearing of SF or SD does not result in a start of the hold-off timer. Instead the wait-to-restore (WTR) timer may be started. + +# 15 Wait-to-restore timer + +To prevent frequent operation of the protection switch due to an intermittent defect (e.g., BER fluctuating around the SD threshold), a failed server layer section which carries the working transport entities must become fault-free (e.g., BER less than a restoration threshold). After such a failed server layer section meets this criterion, a fixed period of time shall elapse before normal traffic signals use it again. This period, called wait-to-restore (WTR) period, is of the order of 0...12 minutes and should be capable of being set. An SF or SD condition will override the WTR. + +In revertive mode of operation, when the protection is no longer requested, that is to say, the failed server layer section which carries the working transport entities is no longer in SD or SF condition (and assuming no other relevant requests exist), 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 server layer section on their protection transport entities. This state shall normally time out unless any request of higher priority pre-empts this state. + +# 16 Automatic protection switching (APS) signal + +An APS signal is used to synchronize the actions at the A and Z ends of the protected domain. Communicated are: + +- Request/State Type; +- Source Node ID; +- Destination Node ID; +- Additional Information. + +The Request/State Type information identifies the highest priority fault condition, external command or protection process state at the source node. + +The Source Node ID identifies the node transmitting the request. + +The Destination node ID identifies the other node that is adjacent to the fault that was detected by the source node. + +The Additional Information provides other information necessary for the protocol, and may include elements that identify: + +- type of request (short/long path); +- signal status (idle, bridged, bridged and switched, ...). + +APS information is communicated between nodes on the ring by a technology-specific mechanism. + +# 17 Blank clause + +*This clause is intentionally left blank.* + +# 18 External commands + +The autonomous behaviour of the protection switch process on the fault conditions of its transport entities can be modified by means of external (switch) commands, that is to say an external (switch) command issues an appropriate external request on to the protection process. + +NOTE – Only one external (switch) command can be issued per side of the protection group. Not accepted or overruled external commands are released/forgotten. + +External commands are defined to allow: + +1. Configuration modifications and maintenance to be performed on the protection group or its transport entities: + - **Clear:** This command clears the externally initiated command and WTR at the node to which the command was addressed. The node-to-node signalling following removal of the externally initiated commands is performed using the no request (NR) code. + +The following two commands are useful if one span has excessive switching to protection. Another use for these commands includes blocking protection access for some spans that have only traffic that does not need protection. The commands are not time critical (that is to say they do not need to be completed in tens of milliseconds). Thus, they can be transmitted over the management system to each affected node. + - **Lockout of Working channels – Ring switch (LOW-R):** This command prevents the normal traffic from working channels over the addressed span from accessing the protection channels for a ring switch by disabling the node's capability to request a ring protection switch of any kind. If any normal traffic is already on protection, the ring bridge is dropped regardless of the condition of the working channels. If no other bridge requests are active on the ring, the NR code is transmitted. This command has no impact on the use of protection channels for any other span. For example, the node can go into any of the pass-through modes. + - **Lockout of Working channels – Span switch (LOW-S):** This command prevents the normal traffic from the working channels over the addressed span from accessing the protection channels for a span switch. If any normal traffic is already on protection, the span switch is dropped regardless of the condition of the working channels. If no other bridge requests are active on the ring, the NR code is transmitted. This command has no impact on the use of protection channels for any other span. + - **Lockout of Protection – Span (LP-S):** This command prevents the usage of the span for any protection activity and prevents using ring switches anywhere in the ring. If any ring switches exist in the ring, this command causes the switches to drop. If there is a span switch for this span, it is dropped. Thus, all ring switching is prevented (and pre-empted), and span switching is prevented only on the locked-out span. + - **Forced Switch to protection – Ring (FS-R):** This command performs the ring switch of normal traffic signal from working entities to the protection entities for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the state of the protection entities, unless the protection entities are satisfying a higher priority bridge request. + - **Forced Switch to protection – Span (FS-S):** This command switches the normal traffic signal from the working entities to the protection entities of that span. This switch occurs regardless of the state of the protection entities, unless the protection + +entities are satisfying a higher priority bridge request, or a signal failure exists on the protection entities of the span. + +- **Manual Switch to protection – Ring (MS-R):** This command performs the ring switch of the normal traffic signal from the working entities to the protection entities for the span between the node at which the command is initiated and the adjacent node to which the command is destined. This occurs if the protection entities are not in an SD condition and are not satisfying an equal or higher priority bridge request (including failure of the protection entities). +- **Manual Switch to protection – Span (MS-S):** This command switches the normal traffic signal from the working entities to the protection entities for the same span over which the command is initiated. This occurs if the protection entities are not in an SD condition and are not satisfying an equal or higher priority bridge request (including failure of the protection entities). + +2. Testing the protection process and APS channel between the two endpoints: + +- **Exercise – Ring (EXER-R):** This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no normal traffic signal is affected. +- **Exercise – Span (EXER-S):** This command exercises span protection of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no normal traffic signal is affected. + +# 19 Automatic commands + +The following automatically initiated commands shall be supported: + +- **Signal Fail – Span (SF-S):** An SF is defined as the presence of the trail signal fail (TSF) condition detected on a span. For Dedicated section Link rings, if the failure affects only the working entities, traffic can be restored by switching to the protection entities on the same span. The SF-S bridge request is used to initiate span switching for an SF on the working entities of a dedicated section link ring. +- **Signal Fail – Ring (SF-R):** For shared section link rings, all SFs (as defined previously for span switching) are protected using the ring switch. For dedicated section link rings, the ring switch is used only if traffic cannot be restored using span switching. If failures exist on both the working and protection entities within a span, it is necessary to initiate a ring bridge request. Hence, this command is used to request ring switching for signal failures. For a dedicated section link ring (DLRing), a SF-R results from the combination of LOW-S and a detected or received working entity failure on the same span or the following combination of detected or received conditions on the working and protection entities: + - working entity failed AND protection entity failed on the same span; + - working entity failed AND protection entity degraded on the same span; + - working entity degraded AND protection entity failed on the same span. +- **Signal Fail – Protection (SF-P):** This command is used to indicate to an adjacent node that the protection entities are in a Signal Fail state (as defined previously for span switching). A signal failure of the protection entities is equivalent to a lockout of protection for the span that is affected by the failure. SF-P is used only for dedicated section link rings. +- **Signal Degrade – Span (SD-S):** Signal degrade is defined as the presence of the trail signal degrade (TSD) condition detected on a span. In dedicated section link rings, the working entities on the degraded span can be protected using the protection entities on the same span. This bridge request is used to switch the normal traffic signal to the protection entities in the same span where the failure is located. + +- **Signal Degrade – Ring (SD-R):** For shared section link rings, any degraded span is protected using the ring switch (degradation is defined above under Signal Degrade – Span). For dedicated section link rings, a SD-R results from the combination of LOW-S and a detected or received working entity degrade on the same span or the combination of detected or received signal degrade conditions on the working and protection entities on the same span. +- **Signal Degrade – Protection (SD-P):** This command is used when a node detects a degradation on its protection entities, and there are no higher priority bridge requests existing on the working entities (degradation is defined above under Signal degrade – Span). This bridge request is used only for dedicated section link rings. +- **Reverse Request – Span (RR-S):** This command is transmitted to the tail-end node as an acknowledgment for receiving the short-path span bridge request. It is transmitted on the short path only. +- **Reverse Request – Ring (RR-R):** This command is transmitted to the tail-end node on the short path as an acknowledgment for receiving the short-path ring bridge request. +- **Wait-To-Restore (WTR):** This command is issued when working entities meet the restoral threshold after an SD or SF condition. It is used to maintain the state during the WTR period unless it is pre-empted by a higher priority bridge request. +- **No Request (NR):** This command is issued when there is no need to use the protection entities. The protection transport entity carries either no (null) signal or extra traffic signal. + +# 20 Priority + +Fault conditions, external commands and protection states are defined to have a relative priority with respect to each other. Priority is applied to these conditions/command/states locally at each node of the ring. + +- Lockout of Protection (Span) LP-S +- Signal Fail (Protection) SF-P + +NOTE – In SDH MS-SPRing, LP-S and SF-P share the same priority code. See [ITU-T G.841] for further details. + +- Forced Switch (Span) FS-S +- Forced Switch (Ring) FS-R +- Signal Fail (Span) SF-S +- Signal Fail (Ring) SF-R +- Signal Degrade (Protection) SD-P +- Signal Degrade (Span) SD-S +- Signal Degrade (Ring) SD-R +- Manual Switch (Span) MS-S +- Manual Switch (Ring) MS-R +- Wait-To-Restore WTR +- Exerciser (Span) EXER-S +- Exerciser (Ring) EXER-R +- Reverse Request (Span) RR-S +- Reverse Request (Ring) RR-R +- No Request NR + +# 21 SF and SD trigger conditions + +An SF condition is a TSF in the server section trail termination function. + +TSD in the server section trail termination function is the only SD trigger condition. It is issued on the detection of dDEG. TSD is always local to a Trail Termination function (TT), that is to say, it does not pass layer boundaries. The SF and SD conditions are described in the individual equipment specifications. + +- For SDH in [ITU-T G.783] +- For OTN in [ITU-T G.798] +- For MPLS-TP in [ITU-T G.8121] + +NOTE – MPLS-TP shared ring protection mechanism defined in [b-ITU-T G.8132] protects normal traffics against SF only. + +# 22 Mechanisms to prevent misconnections + +Because ring protection mechanisms share the protection resources across multiple working resources, it is necessary to consider mechanisms to avoid misconnection of traffic during protection switching events. This is particularly important in the case where the protection resources support extra traffic, or in the case of multiple failures that can lead to ring segmentation. + +## 22.1 Circuit-switched technologies + +In a ring protection mechanism based on circuit-switched technology, the protection transport entities are essentially shared among each span of the ring (that is to say a protection transport entity on one span can support a ring switch for the working transport entity on every other span). Extra traffic may reside in the protection transport entity on a span when the protection transport entity is not currently being used to restore normal traffic transported on the working transport entities of other spans. Thus, each protection transport entity is subject to use by multiple services (services from the working transport entities on different spans, as well as service from extra traffic). A number of scenarios can lead to multiple services contending for access to the same protection transport entity, and thus the potential for misconnection. With no extra traffic on the ring, under certain multiple failure conditions, such as those that cause node(s) isolation, services (from the working transport entity on different spans) may contend for access to the same protection transport entity. With extra traffic on the ring, even under single point failures, normal traffic on the working transport entity may contend for access to the same protection transport entity that carries the extra traffic. + +### 22.1.1 Wrapping protection + +A potential misconnection is determined by identifying the nodes that will act as the switching nodes for a bridge request, and by examining the traffic that will be affected by the switch. The switching nodes can be determined from the node addresses in the APS protocol. The switching nodes determine the traffic affected by the protection switch from the information contained in their ring maps and from the identifications of the switching nodes. + +Squelching by inserting the appropriate alarm indication signal (AIS) signal in those entities where misconnected traffic could occur shall avoid potential misconnections. Specifically, the traffic that is sourced or dropped at the node(s) isolated from the ring by the failure shall be squelched. The squelching is performed at the switching nodes and is applied to the normal or extra traffic into or out of the protection transport entity, that is to say normal traffic into or out of a working transport entity is never squelched. + +### 22.1.2 Steering protection + +The avoidance of misconnections for the steering application is for further study. + +## **22.2 Packet switched technologies** + +Packet switched shared ring protection mechanisms do not require special mechanisms to prevent misconnected traffic because the destination of each traffic unit is explicitly identified within that traffic unit. In the case of MPLS-TP shared ring protection, the protection resource has a specific label that is added to the normal traffic when it transits a protection tunnel. When a failure occurs, extra traffic does not have to be explicitly blocked; rather, the normal priority mechanisms used in packet networks will ensure that the protected normal traffic and NUT traffic receives higher priority than the extra traffic. The extra traffic will continue to be forwarded to the extent that there is bandwidth available for it to use. + +# Bibliography + +- [b-ITU-T G.805] Recommendation ITU-T G.805 (2000), *Generic functional architecture of transport networks.* +- [b-ITU-T G.842] Recommendation ITU-T G.842 (1997), *Interworking of SDH network protection architectures.* +- [b-ITU-T G.873.2] Recommendation ITU-T G.873.2 (2012), *ODUk shared ring protection.* +- [b-ITU-T G.8132] Recommendation ITU-T G.8132/Y.1383 (2017), *MPLS-TP shared ring protection.* + + + +## 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.8113.1-201604-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ab3e75ff7922afcb42c255d804e296e2270d406 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c4b760c1f6879dfcf153ccc8672b3f314706b2f62f9a3becff6a4084661f475 +size 29307 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b318ab4c422c582f813923be16c90afbc49c9768 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71cc315c4f86db81151b35ff9ac59aae09be09cb0f94902a0c58f3fc14970b5e +size 24478 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e736f6895f5375f3a63de898fc48b9c2e709bc03 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7eb93b85bf8f08af79ad79099cd67810556dd8d9ffd10c37bb3b095466bcb434 +size 53159 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1341a29d805f766d1983f726b4a285a210584e36 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e3c0529e5c819f6875cda8d4cc237724723332aac6625de0d666395c082ab0d +size 29543 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3cc076b0707d754e4d1a5968fffe73248402f87 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5db8dea0d106d066689f1e6c23d0dca546704475313c699475b2fe80caf1cba3 +size 168861 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fc1d41a75f4ba0dcdbd3fe2e85270febbcce09d --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de84d87522036c862994a57c838ca69d6fb2b80cc50375e7d70a8da737c2eb8c +size 41930 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97edb73658382ebd98222653f8eb9bd308d179d7 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f327fe304990d701eeee50c8d6958845d0f3e5a1c73886f80639abc431c7545f +size 30782 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac7b3da64645539c421d3e2b2cba6ac81d5ad00f --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/5a1abd59a95fa47ae192807de151e9eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8da71f14eeb02a35cc77f8a45cf76d6b35938602bbfb9fc4ad247ba9f5d4fb03 +size 31635 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4550f46f8df7fea8b1e81e317f532bfcf133aa9f --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c3eef5e333c8510e8142f1d226a4b6fea82ccab0e63ae61ab7444a77f7f2b82 +size 42604 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68b5495fd8ee190313c5e5f82f60bb344d888145 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8c880d6b715587bd710a9ba8414469b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44e07318db79a2758e5afe9c5e85a26265859f0d2b1bd4acc4a1dc0565c5f2c4 +size 107212 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41765dfd9ab997537d3db659896c7be9abafda16 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2993db7f830de46aa52ae15e95e85174cf759cd490dbef8b4847036b406c320a +size 53057 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..448db2526c0a29b380607a2b6365c5da4a2b0662 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a4c085fbb4744ccaead5f14f4f6240c8f22070e54e4b91a3af2c757ee4ec93a +size 27907 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..165e91d19612bfd4748dab1a954e8663cb14908f --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83312b11d8ee3d1845a618bdb6fac75cb8c12c6854d55bd725e2ec03dd50f30f +size 29519 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce38c4bfaf51bcd3c205d26c8f73433f80566dfc --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:498ac4b35443f41ac9f3714a3b80146ae4213b7f30169a8bfbb6ee18690ee1a8 +size 135264 diff --git a/marked/G/T-REC-G.8113.1-201604-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3f51724d3e0138c7cb7385fe154aaa8db760825 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_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.8113.1-201604-I_PDF-E/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97db37b12fcedb9c1b47fec2a4b21177b6351c45 --- /dev/null +++ b/marked/G/T-REC-G.8113.1-201604-I_PDF-E/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27ac67af0042d382c0c343aaef797ee9c85c1d2ca8fc50687b2606ea5b3cfa05 +size 43366 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22649f90635364de5f3f49ba01398f7c1b02b8c3 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/0850300da6b28250eb47881da35cabad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6480397ed47988ab64e3cbf3503e51abd2b9635d3076338349de64e2f2b09bc +size 28931 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49b5c1c652fd98c9d8489c8fa4c4d9c5b9e86244 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/09036266c6dba47efb2613ceaebe2b19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:217218467795aa0193fa22e7d8ec3432ccacf3feb0de1936700685fabc4fd41a +size 7916 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/0912a2665a461bed9dafb29a78986961_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/0912a2665a461bed9dafb29a78986961_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23b51666a5dc7012b36f1cb3383a65b5273f38bf --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/0912a2665a461bed9dafb29a78986961_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d089e2dbeeca3c0652f9b412d5affae40f9f7c815c884a3f4af7d7cbadf9b08 +size 11032 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/09db1d3c990a8ce8a2e8a35bc93cfb5f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/09db1d3c990a8ce8a2e8a35bc93cfb5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3f15b3bf7fcf793911598bd7725691330f48fd7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/09db1d3c990a8ce8a2e8a35bc93cfb5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:409cdf7132840cdba5c40039ec692c4242b5ca5973458592f720bea9d26d7cd5 +size 16768 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c4dc17fe058e4fbffb32556a458b2c4fc891322 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b957933aa121df9bd20730c0fbc720d4397cf6e6f87af7723fdbfb7f7c7cc46f +size 35975 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb85e97aee4da0e299d2d4a5f56cac099ea15b27 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/0b2ee589f5c7802f3d332f421340cae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b5cadd4453a1003c3e75cf21799e550ef5624fe25ae03c30be1e49674bfe19 +size 17259 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b278a49ca9674346c45717105db621490153871c --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6adb05a7ef2a91408a14580088bf57ef89772249340ddb4159e62f37ef81a2c +size 20157 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a46fc9c1b76149c444128f55234fc34ff75f0e7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/1142ba0197b158bb198186fe8baccc32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6fb70319d1e6783e2e5cc2509fcbfed8205077313ef87977292b3979044a268 +size 32365 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f32ea7928e14dce6c6aebf7103695d51281ba8a --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59ec0126d3180d221baf13bf561ed79f953a2146b8b5d3e16a1be84d66b63844 +size 28845 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/15d5c901284409186049549eec95c4a4_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/15d5c901284409186049549eec95c4a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7ef0be2da977274c28a1c1bca85be6fb2a9051 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/15d5c901284409186049549eec95c4a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b1d72d646af5b403b2d69ce5a2e2fa68814082ee3947dc36efc52668122e2e9 +size 78544 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54871540c4e02b94c7e20090484be255c058d43e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/18d7d8de298d79e7bc87af5217f11203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bec30a0648bade404fdfa49178305a1c2e068630f9f3c413edb157e5f0898724 +size 30045 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff90e4c71db5b0fb7530951bb25527622b2d3cd --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e13803f2adb5274bb303922bd0e14b9e8ad943c1b5900a412394934c1cafe769 +size 76294 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4d0f09fb5fe58a527b2cb6788d92d1a0dc177ac --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ece8101a8746db89bc48a620c06b9a35b61d40456ead81b3994b2a3b09f29b07 +size 10545 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..960c722928617acf2e742091993ce09b123f7eba --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cf71ebd3d67f410a6ad0bd82f93d1aa2fcf3eb0cc72ed1c1dd94a596b228d8b +size 9379 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/24ca460ee3381aee781887e9e586ec67_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/24ca460ee3381aee781887e9e586ec67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef30da2036187b43113df0fedbca8bf080364a6b --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/24ca460ee3381aee781887e9e586ec67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b0faad77d5bc481cb7f42cee3451b600aadbb8b7a00dacdf823fc2caab1a7b +size 9179 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/2c41e286ea9a1b008d3beb348d86096f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/2c41e286ea9a1b008d3beb348d86096f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ddf2a9846cc3371fb1a4f620070fcbbda175ab3 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/2c41e286ea9a1b008d3beb348d86096f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca40e0dd3ceebb327cd9286f5cadea3479513a9527cd45205877a2b1186ce58f +size 83900 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/2d8e8a86768f5861aef582d938c0597d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/2d8e8a86768f5861aef582d938c0597d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76f6b1bc914d4f4154551fc8928dcdd6ab5305cd --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/2d8e8a86768f5861aef582d938c0597d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a9c5476df96755f8525e6413d99e34e51c5b53433e44b472deb3c212cefe6de +size 17762 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0f6750a3c96985bd2383683457a7b50edb91d52 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84b7e7ff2352359a2f709ec412aa59eca43fcf66d610139ead57fb04d45bf880 +size 71650 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/2fc2e531b3b3c695cca497516ec79f20_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/2fc2e531b3b3c695cca497516ec79f20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b724523363cf7bf88ae77bb19c98e88eaeee915 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/2fc2e531b3b3c695cca497516ec79f20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:880e74abc07e26df59fb7ed29859fc43e22c4fcc34a894b92689ca7d216af957 +size 25455 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6434f0270998fb67837bf7b82d175311dbc5ed40 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2312e6e34abad728a511e075272361252ff5d111bc4c7e8f28e0c96f4332b6f9 +size 23476 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894d164aec26756a1eee2f2ffbd9ac425557388d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bece6a6264447de5c62bdb8969e4f8d456d0d43c4a800e80d4254b0f8605a13f +size 14377 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bd5c7a7255a92c699c1cb38c92c8c6abea2fdb --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed5898a3d67470babbda3806b1db8c4c98065f0ecd492896a66f13edee2212f2 +size 11460 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efcbc4a0dbe1805357904ea4e64d821cdfbfd0c0 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/38331e6e38fda222ecacad7292694c84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0394cc2c79a99ea06a40c974a1637acf8285dc4c6fa0a570b89dd082d5008bde +size 10574 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d02480e9445761b449a58952b22a70f51b6996 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/387a316ca4f909a5260b0c5e232d5cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e56c21a7cc88a9f02226cd75f22030bb8cf5a53a9e56d2660eb34b5ce0e4438 +size 82530 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81a604a2362c5cdc42d5864f63b101d6d4838c5d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1a6fc745f2f8a5ecfcbecdd37774bce885441d1770e97fb074d0cd8d02d05f2 +size 15459 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/3a568746c00925506d5c39f2a86a5a63_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/3a568746c00925506d5c39f2a86a5a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3ea1bb463614ec07cfa3ba4f761edf328e52a51 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/3a568746c00925506d5c39f2a86a5a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830ee05e411be5d265b624d661dca7990272ed8bc59b0c4a1c7e1cbe477a5c66 +size 126000 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/3abb87a27232fe2f2806b67f2e5e1390_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/3abb87a27232fe2f2806b67f2e5e1390_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4344cee8ed39026d9f99cfa493e7922d67c30036 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/3abb87a27232fe2f2806b67f2e5e1390_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3305aaf4c0d2754ded636aa802c303a29ec52bbd2b6c28285b16c13868bac505 +size 25237 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f711657b6800b300800f9fd3e29d122970e9b9 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55e39dde11cd0b1c96adef56f87bf69a7596ff3537d6aecd34cd3453ed787f49 +size 84367 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1b1e826e2f48c656658f17ad1341af8fe6dca3d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73e8e0853a9349c82920446e4f76f47d22e0d0316dc31901a44da67d81dde650 +size 88741 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/418ac859afe534b37c6f4e96e15c0b25_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/418ac859afe534b37c6f4e96e15c0b25_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aa32d509af3816dd63365c016417af56d2712a3 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/418ac859afe534b37c6f4e96e15c0b25_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:980319e803ebc0ddf276e1cf1a0a3bf874b37facc7a5ecc612f562639cc16f6f +size 12039 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/437a88375397eec8390174b5426e99b0_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/437a88375397eec8390174b5426e99b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b9476e72e64a58a6f642a6f5c8c6f31fe5a5e0c --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/437a88375397eec8390174b5426e99b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e75da7a431333fdd177183a7d2f0400231470727ab65aa50412b2285e588904 +size 24875 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9edb543fba9bb5bdfb927c0ca2598682b1947e06 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ecabb574a29efbb80b99b3c35804c84d710af32471c3c64ac37177477925e2f +size 116905 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faec8787554c8c866a4568d2c2dcbfe4451b8ab7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/48adb97a6a4a14b039450192f25cc1e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b3a22af4f7abc3041c8aeca6f01621c9d5255049ae1adfe5516fb69a230ff47 +size 14337 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73658a3deec1a88cb6c438291f50944cc084fc9c --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:251dc430627ac233052ed968160d14d8144988f313dd758e1d91e58170ee90ed +size 8331 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0154a74d53f0b35cb2a3789da0d12ea31c63b970 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/51167ecef86d85cdc6dde05a3afb74b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11a21a8703e490b6c196c628babec5f88e9bd545c2a175d067e1757b83463d3f +size 57899 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a6acac186b8c10a9f43a3b0579ab9948ba5dfc0 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:534b6ffc8b685abf682e34e68b15742f5e33235cfb7dec87fa28885a46d94e8d +size 35627 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/52ddf5847d6a0dec582fc4e972db6397_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/52ddf5847d6a0dec582fc4e972db6397_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1e53cd6ebcf10f3fcdb9e74a2da7f5f09eda458 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/52ddf5847d6a0dec582fc4e972db6397_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd4c2ba77134fbbee14298377a97de22fc3156b9a22df0a2244704b7f5965d6f +size 79061 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c62c2a4dff32adcf93c12c6685fb29ea2f5c2770 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f93de3da969952119a3c3075fa5ed653fbfcf6572a4fa48066d4e27bd932d043 +size 12994 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2386acaadb4c559b2c53ead35ac868f1afca46d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:425be4c1ef68558502f6602fe7a23a19fbb7f5de54e7ea3545004407baad74c1 +size 12326 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58af2bbd3f9538d0dcf8fd8624b67a869f31c2f6 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a80b70f93447b9419c7aacccaa747dc0085b429e97e9974af0a7a27d9646a042 +size 40290 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/584c8bae39761224bd920bbc68831c1e_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/584c8bae39761224bd920bbc68831c1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84e884993a22e75297f7ef7bb6270268d52ce8ca --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/584c8bae39761224bd920bbc68831c1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5daffba2d0c66172ac2c8b8cbacf05c22efac15239c70c9b05a0fb683a85670 +size 14809 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c043a4639b141c3567fa51050bd85573df4b697 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6128d7188ccd1279254deed0da5bc380408cf7d5aed33acd5289b98dacd67ccb +size 11031 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36d30d9b4b699fd1fbf38c08e161cdb6e7a3dba6 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/5d3455c6c2a37cb3aff761fedeb8644e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c7ec2738f1d144604bd3f8f109aaba3b8894958d632921e7cf48b6c978994c4 +size 19358 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af45bb66ee31840ccced6c301c1753da13209d8e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8d1e5c23e62a80194fa5484d144b259e44de95b3adfd76e4b2bf488971c5b4c +size 11091 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a5e5fad1b20ca7551097ebf5a746c0592c23b5e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/61a49f3179b455e4d35242fc3d187a29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4982e8e8c7b86669ac1411bfeda881e2809244568556956fb0d33cf1f8e6456d +size 11579 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4a0c390fec2c2a8541bd1bbf1e2293c4cbccb21 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/66decd3c38c5f918f528096090219e15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff625b9e394e28480fc289fe39326fcd0e7c0ce3134e14cfc00229c72f86d8cc +size 15918 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53a8365fc0205c53aae6f0d7d2273ed3e5f9711f --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/66e89867f97592fd4bfab0e4f2b2054f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0893f100900c6e70b1f5df0b4fe9103276c085416d8261548ec279b068bdbec +size 12420 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/6a91a6df50795695b71693ad679a4f31_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/6a91a6df50795695b71693ad679a4f31_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fca40dbed34dc736e64768df4dcd4c37ab25323 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/6a91a6df50795695b71693ad679a4f31_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87076064fa7c4cd2aab9d46147e09d13ed2cee6aaf850e4992b7167254091dfa +size 24665 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a18ab9623812029c224ae46dc346edb69d45d4d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9698c2fe4de4c866181d7eb57924c3da76d4e33c3e4858af7573bcdfe43f51aa +size 11307 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8804e29674d9d82106099d7b4802114357461145 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccdbae1921fd9d5332b456426969ca3b8735b9baa1e825b1e31bc9ed16a3a3b9 +size 93163 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..160c11b6e4aa3cf0168b0ac086a6cdbd2e5824fc --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c56d11615a5dd87e61164a063809020f8263e468fb7d15da60cda56d4535ef75 +size 118806 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d762a9d7348aa902b903092b199d1b0471758740 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e737ffd51c7da0ba69594c13bf66b1b9f0cff54daf7817b4f0c654c0aaafdcfa +size 13229 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bef13dcbbc0bd19461e8550850d29c2ab3f4f83f --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7597c547a503f45d6ac8389878c5ea4e33fdae0ad0eb8d47651c5032a4a22acc +size 21310 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8544016cdebf6c43f1e6b7590080138ef534af1 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8b87f93fb22857601333807d95e93290ab300fadd4f92cc64a29d3981143381 +size 8706 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd6f06410b84e3e688cc88fbedace6b6b7feaa82 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/7c3ecd751b69a0fc7b08633a84822f42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a9e6720d37d6c59cb3632fbfe05ace262b7749034e8a37b8f9ed60695c9b6fd +size 25428 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304017529ec2ba57eaa33e3010c1ef97a5fae1ad --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7e678202637eac0f0afc08f1baf6c7695ece8da3ba8eb9ab5231dff12341fba +size 55019 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/7ee70c4daffe1f4f1d07ac574964a3a8_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/7ee70c4daffe1f4f1d07ac574964a3a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c427d3200b9df38d0596bdb482a4c8993f5381e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/7ee70c4daffe1f4f1d07ac574964a3a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef58459cbcd7c2994ec1cf3e06d124443ddc8ec0b37a6931fe1947561a738af5 +size 13229 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/7f7718a1d18d1f9055d85871d02364b3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/7f7718a1d18d1f9055d85871d02364b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ed8c6ca515aaea0f048d9ec896085a1e18be39f --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/7f7718a1d18d1f9055d85871d02364b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46de35be29077d40e010029b4ec73ad355ba1d9999dcbfb10cdea43e8d7579fa +size 11670 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/81a685da17696e2b65791368a3e8ce8f_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/81a685da17696e2b65791368a3e8ce8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..506924a29c4583f3d323bc78d98c5a4b3ac885c0 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/81a685da17696e2b65791368a3e8ce8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d505dbaf9497ef08fe487ed3c321889cd0d7268b0a3494e5dfb6a2dd0ebb46d +size 11633 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/8206c9e6dac8ba2d4c3e28ee5d008058_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/8206c9e6dac8ba2d4c3e28ee5d008058_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ad579949477413e45e66a74033f85efea59a8eb --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/8206c9e6dac8ba2d4c3e28ee5d008058_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc60c96e3bb45f0455ec44be68aad24990f6b48577539a23625ccdb1f9a232fd +size 11037 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/879d68959f0c0ba370ef82447298ba17_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/879d68959f0c0ba370ef82447298ba17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c947b3f130d8145133086a4e4f224c7b59a0b79 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/879d68959f0c0ba370ef82447298ba17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67ab709fac081b5c3d4f52fd8fc2b9c119ef57e9aaa7e0df163fd30dc853b13b +size 6557 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d21e8ca7840a7510f35bb45beeadfe2ef122f5bb --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9281fccd60473c84b6a29a1f2bf0540bc7aa95436013e47a125ed4521cd47596 +size 98561 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80dc6d65bb830c817660aa809c87c0ce729344cd --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31261669cedd578a652340a8b734ccd9e0cfcf085a277a77a11c2b1e29694c45 +size 111343 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/986e77e2df3c318680a569774888f4aa_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/986e77e2df3c318680a569774888f4aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..956da5362a2e45b7668b850622e314ec8eaae919 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/986e77e2df3c318680a569774888f4aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d9bb5ede0635eda8b95bdce7abf77e1971a680c672e2ea79d02970276ba1153 +size 17540 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f17c96da92ff124d8d16fae5bf274eb700635252 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/a02b188a5fd52c99f84255322873bf29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c086ecb6621219845dd543cb48e2e817c49e4a7f67bdcdd0824b70a58cbb67 +size 10104 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d6d9ca2a31b5364f84fa8b3439d692b1271e70d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ac8194ec0d833d53a0a36adada95b39e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aef5462cacb0a9a2ae018227399c3647cf030d82bc16e99847bc28c7b3debad8 +size 10835 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13af076c8531e74c1a62f87515c3c4d93c382f19 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ae57a92114d2bd84ef81129e7fbdd89d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c42d0032ab4e2e65436ff6a595e394c88c094368f17cdb605f9270a6efac443 +size 16170 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b0517f9ca66ffb186c33e3877529f507_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b0517f9ca66ffb186c33e3877529f507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b86d0211333062f133973d75068d9ab10a760744 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b0517f9ca66ffb186c33e3877529f507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c853ade87ed0867c7051c702d06e5dd6ce39dbff048d7ed8b72d7f15e274437 +size 34193 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b15cf8c50195a52cca59b4645c6f59fa_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b15cf8c50195a52cca59b4645c6f59fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c97449d943dcbe59373221b352fb150e4f0340d7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b15cf8c50195a52cca59b4645c6f59fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5966ce569be4d7bc3f6667ec774d16848beb4c806892991fa417932a16e3c1fb +size 47796 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b22a2b17c5f35e4706033e34ab0f3e9a_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b22a2b17c5f35e4706033e34ab0f3e9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df39e59163d5f8247a477f9fb6166e3528ab0da6 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b22a2b17c5f35e4706033e34ab0f3e9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b2e89cfe880fab764809863de8d33a764eadb5b262405ce059058aed5350cab +size 11340 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87b270e6a0295ad785780662eae07320c05c558d --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec5b46284b6d67d9c9840ee6c2e5dc21b1a595f878ed4407d0f4f6e51a4b208d +size 15192 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69037ebabbaf8cde3eb873e64ec4edc9f0c9b76b --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10967d5cffda9a2d6f7646c56af994e7d23edde3586c995f73a43109fd548fe0 +size 11746 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e27c3d42fdeaf89f94a3caef8776f24efc4bfd --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d5be579a7b93c4a1d8c9b9920f1ff81d9a40bc31ba8d5c43ed1bb4d757894fa +size 52890 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15a6b0756f24aeec9630206d2c0886182998e1e7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b550cb515008f6bab9f295adcb28b5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:034a5ddb3d2a1bf45fe1fe4c7ffb9ca127193e13cba774f49033ce5e61e89f08 +size 73940 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/b87818c8505328b198d035761bbc3f2d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/b87818c8505328b198d035761bbc3f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c735fbc4acbe5b6b6daf8577214f66f3e4aba02b --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/b87818c8505328b198d035761bbc3f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18884a3a4e1e48a8a0bd5da0ba5855a4ebd80b815042af2a7afa0ae008fb2600 +size 22562 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef665b562995d464dae81d69c56d0abf12c684e3 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/bc90605aeb4173d4b4aa6eb475037a0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:179320497101f7149ade8036e5aeb6a01b52ab08b6956ae75416afc0285ff50e +size 73605 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee2a2dbda905cb20f21bae0e414068f968763875 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43c7e4368287b1b2c938c51c950983d592d5d21de458963885ba7c742a993c57 +size 36446 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c05763eff20551449de1eac378fed769_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c05763eff20551449de1eac378fed769_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6164bf045aad5b523d3529a0cd0e99929c50d96 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c05763eff20551449de1eac378fed769_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a10ae0c104a2789aeeed3679c195416b53605230cadf88282ac6488799d13f5d +size 124236 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c06fd7dbef68a8b788158f2081d9d734_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c06fd7dbef68a8b788158f2081d9d734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e138bead2f00486673f54bb264f3e434cf58ecec --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c06fd7dbef68a8b788158f2081d9d734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c17617df3ba7e551ff4987ff4a7cb121048b2039b0f1160d7151ea3f9824c80d +size 9756 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e650a87f59696c80ab272bd389483d42a31d713a --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:973e9a361181ba10e8e278f38d163fc985540aa62d33c0e0b9690a55d82e075d +size 33756 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..860e2ae129d46dc35ad208330380c0b8af169467 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a50f61da708b1e7bc4470ff1c17a77160909f14d3742c22cd920bf283852db85 +size 36326 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..434b61415cc394814f0e4b0de279063d6f7396d4 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/c85ded401105f62f2d6ff26b3b5eb4af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39377349597bf74db04586ff65073d9fc3647a4efd540a854d760a79a8c69fd5 +size 53803 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8612a5f5b501fdcba5152482faa09207c375407 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ca86f53f9735fe98b6c6003d1b759f64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2175a932dc8b2b430645b887422cb1b0e3de5f353155a7ebf23e71bc53027b75 +size 58901 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..056ce3f30f3453ffb15bb88d6051e8a69526f09e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6e396b3814ebeda244c4b61983b75115794d6704ef405120d78e0de7bb4b547 +size 96737 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/cc468dcda006ef315536400517a09ad3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/cc468dcda006ef315536400517a09ad3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db76b2825b5f3ab43c1eae174d494283a7307e7b --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/cc468dcda006ef315536400517a09ad3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79b0cf3f7ce49db6e5aa2259715f76ec375221f621d675e3a89d6958a3e560cc +size 6885 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3d1091be79d236cb7392b5218bfab0fece7d37b --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d09c01d5fb8d3e578c3351778737218a2448dd0e1f767fb4acf8a593df0c2392 +size 50778 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad28e7c9d9237cf5f6ca41c893d5513361f0ca95 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae85ab69cbffcbb49b1cbd986d5da54c11e2fa23543a8a082c1d63f8906351ee +size 161174 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a354fecd80511b6b89a6cc58877c0c96f999298 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/d7896dd2d38adf224c3b76cd22d29c10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee81eea77ac2da951f2df2549106f0252fa4e9d88b14164aaa8f0813647d54e4 +size 15730 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..962698c1e6f36f52d9102ac7a6b5c5f371a7add6 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc2e5b74e6991e9dcc51d8321e9ad0fd9b53222045d02b81f7c3a2a2d49d721 +size 42967 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/e2b7490a3455c66c85db12872c78fcc3_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/e2b7490a3455c66c85db12872c78fcc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce45b259c5def5c11797fc2677cda43d618ad47a --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/e2b7490a3455c66c85db12872c78fcc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0891702108902ec11233d8c8592ff36f108642f5a260f486840f8b74b3a3cf +size 160094 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3954c40964c0206a4a468c2278c85add05737a79 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe4d918faf7d7d707405d0f0e5b9a2e01cac46edb1e4156b617986289f057cd4 +size 118264 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c3e3415006871ab1dc6d24f308e52fd7b6648e7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1777fd567b13951fe7466372f7056740fb2f4e3f326880a96cb72f0339654c1 +size 36971 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d5f1ea27e9bee9f3ec1723b8a29e8c50615c508 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df450d9d5613fae3903b05307b0b316d0604075f51fb755736d355eda15c8670 +size 11351 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48f6c1ad0a844e02bfdd9c7fcb676db18b8b74fb --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ed48e24e36ea0501953177401c900f86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d2110eba714e2add04415e3bf878a9540f69751a584e1b31b2eb6da74015232 +size 12884 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52d318e8f9a4aa99eca85712d860d8e1eb5f9b1e --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bb97881e637f6fc5319e31ad0b5d65f1ec77fde1fe98d2913ba17efc960011a +size 53727 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/f40480872b021d2ac7c29202c199b695_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/f40480872b021d2ac7c29202c199b695_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..944d78a4eb8a34bf0a0cc930544e8b965f997ad9 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/f40480872b021d2ac7c29202c199b695_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dc4022b95094027c87b2de3a205409311a1d043b81ddf6d6d4681e838e7bd45 +size 12488 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b65bba8d5b0a246a5c060ebdad0940ab1bc266d8 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28d535cd8672de9c0560d76b22183114ecebca25707103522105ae7b5cb9c3a5 +size 12403 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8c62073a660866061cbd10b75e4479397d8d3a5 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81580ca6b194a4c7a1c8327aed515ecebd6bbab3255d7a1e264ee6ff8ab598a4 +size 16597 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a5122de5f33ab3b095207de4899690e97bd357c --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb63e44efac9266b2d7bc80afa54b50758bfaae79f383e21a4f19b1c65e29a2b +size 136549 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92e274f08fc26d84d891e7409e47aba71f8338d7 --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96263300518c46b4e69d2906f3f6dcf53c0b28b5940037694ec9de26706acd83 +size 97034 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg b/marked/G/T-REC-G.8121-201811-I_PDF-E/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..562a9a5d045399419594ef9510387f21a0b6780c --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06d86c09f990e68f4693caa533c6a5f14d938277f5f500d992f267155132e550 +size 12466 diff --git a/marked/G/T-REC-G.8121-201811-I_PDF-E/raw.md b/marked/G/T-REC-G.8121-201811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7478a1b2834e92dbe6835f53188e4c8fb5482d3f --- /dev/null +++ b/marked/G/T-REC-G.8121-201811-I_PDF-E/raw.md @@ -0,0 +1,5375 @@ + + +**ITU-T** + +**G.8121/Y.1381** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +(11/2018) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Packet over Transport aspects – MPLS over Transport +aspects + +SERIES Y: GLOBAL INFORMATION +INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, +NEXT-GENERATION NETWORKS, INTERNET OF +THINGS AND SMART CITIES + +Internet protocol aspects – Transport + +# --- **Characteristics of MPLS-TP equipment functional blocks** + +Recommendation ITU-T G.8121/Y.1381 + +## ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000–G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000–G.6999 | +| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000–G.7999 | +| PACKET OVER TRANSPORT ASPECTS | G.8000–G.8999 | +| Ethernet over Transport aspects | G.8000–G.8099 | +| MPLS over Transport aspects | G.8100–G.8199 | +| Synchronization, quality and availability targets | G.8200–G.8299 | +| Service Management | G.8600–G.8699 | +| ACCESS NETWORKS | G.9000–G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T G.8121/Y.1381 + +# Characteristics of MPLS-TP equipment functional blocks + +# Summary + +Recommendation ITU-T G.8121/Y.1381 specifies both the functional components and the methodology that should be used in order to specify multi-protocol label switching – transport profile (MPLS-TP) layer network functionality of network elements; it does not specify individual MPLS-TP network equipment as such. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|-----------------------------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8121/Y.1381 | 2006-03-29 | 15 | 11.1002/1000/8785 | +| 1.1 | ITU-T G.8121/Y.1381 (2006) Cor. 1 | 2006-12-14 | 15 | 11.1002/1000/9007 | +| 1.2 | ITU-T G.8121/Y.1381 (2006) Amd. 1 | 2007-10-22 | 15 | 11.1002/1000/9178 | +| 2.0 | ITU-T G.8121/Y.1381 | 2012-09-21 | 15 | 11.1002/1000/11517 | +| 2.1 | ITU-T G.8121/Y.1381 (2012) Amd. 1 | 2012-12-22 | 15 | 11.1002/1000/11800 | +| 3.0 | ITU-T G.8121/Y.1381 | 2013-11-06 | 15 | 11.1002/1000/12020 | +| 4.0 | ITU-T G.8121/Y.1381 | 2016-04-13 | 15 | 11.1002/1000/12804 | +| 4.1 | ITU-T G.8121/Y.1381 (2016) Cor. 1 | 2016-11-13 | 15 | 11.1002/1000/13100 | +| 4.2 | ITU-T G.8121/Y.1381 (2016) Amd. 1 | 2017-08-13 | 15 | 11.1002/1000/13317 | +| 5.0 | ITU-T G.8121/Y.1381 | 2018-11-29 | 15 | 11.1002/1000/13759 | + +## Keywords + +Atomic functions, equipment functional blocks, multi-protocol label switching – transport profile, MPLS-TP, MPLS-TP layer 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 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..... | 2 | +| 3 | Definitions ..... | 4 | +| 3.1 | Terms defined elsewhere ..... | 4 | +| 3.2 | Terms defined in this Recommendation..... | 5 | +| 4 | Abbreviations and acronyms ..... | 5 | +| 5 | Conventions ..... | 8 | +| 6 | Supervision ..... | 8 | +| 6.1 | Defects..... | 9 | +| 6.2 | Consequent actions..... | 16 | +| 6.3 | Defect correlations..... | 16 | +| 6.4 | Performance filters ..... | 16 | +| 7 | Information flow across reference points ..... | 16 | +| 8 | MPLS-TP processes..... | 16 | +| 8.1 | G-ACh process ..... | 16 | +| 8.2 | TC/Label processes ..... | 18 | +| 8.3 | Queuing process ..... | 20 | +| 8.4 | MPLS-TP-specific GFP-F processes..... | 21 | +| 8.5 | Control word (CW) processes ..... | 23 | +| 8.6 | OAM related processes used by server adaptation functions..... | 24 | +| 8.7 | OAM related processes used by adaptation functions..... | 26 | +| 8.8 | Proactive and on-demand OAM related processes..... | 31 | +| 8.9 | Dataplane loopback processes..... | 40 | +| 9 | MPLS-TP layer functions ..... | 42 | +| 9.1 | Connection functions..... | 44 | +| 9.2 | Termination functions ..... | 57 | +| 9.3 | Adaptation functions ..... | 69 | +| 9.4 | MT diagnostic function ..... | 81 | +| 9.5 | MPLS-TP MEP and MIP functions..... | 93 | +| 10 | MPLS-TP to Non-MPLS-TP client adaptation functions..... | 95 | +| 10.1 | MPLS-TP to ETH adaptation function (MT/ETH_A) ..... | 95 | +| 10.2 | MPLS-TP to SCC and MCC adaptation functions..... | 100 | +| 11 | Non-MPLS-TP server to MPLS-TP adaptation functions..... | 106 | +| 11.1 | SDH to MPLS-TP adaptation function (S/MT_A)..... | 106 | +| 11.2 | OTH to MPLS-TP adaptation function (O/MT_A)..... | 126 | +| 11.3 | PDH to MPLS-TP adaptation function (P/MT_A)..... | 138 | +| 11.4 | Ethernet to MPLS-TP adaptation function ..... | 147 | + +###### **Page** + +| | | +|----------------------------------------------------------------------|-----| +| Appendix I – Examples of processing of packets with expired TTL..... | 151 | +| Appendix II – Flow of PHB information through MEP and MIP ..... | 155 | +| Appendix III – SDL descriptions ..... | 157 | +| Bibliography..... | 158 | + +# Characteristics of MPLS-TP equipment functional blocks1 + +# 1 Scope + +This Recommendation describes both the functional components and the methodology that should be used in order to describe multi-protocol label switching – transport profile (MPLS-TP) layer network functionality of network elements; it does not describe individual MPLS-TP network equipment as such. + +This Recommendation provides a representation of the MPLS-TP technology using the methodologies that have been used for other transport technologies (e.g., synchronous digital hierarchy (SDH), optical transport network (OTN) and Ethernet).2 + +This Recommendation forms part of a suite of Recommendations covering the full functionality of network equipment. These Recommendations are [ITU-T G.705], [ITU-T G.783], [ITU-T G.798], [ITU-T G.806] and [ITU-T G.8021]. This Recommendation also follows the principles defined in [ITU-T G.805]. + +These Recommendations specify a library of basic building blocks and a set of rules by which they may be combined in order to describe digital transmission equipment. The library comprises the functional building blocks needed to specify completely the generic functional structure of the MPLS-TP layer network. In order to be compliant with this Recommendation, equipment 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. + +Not every atomic function defined in this Recommendation is required for every application. Different subsets of atomic functions may be assembled in different ways according to the combination rules given in this Recommendation to provide a variety of different capabilities. Network operators and equipment suppliers may choose which functions must be implemented for each application. + +--- + +1 Cisco Systems has expressed concerns that in the event of a difference between this ITU-T Recommendation and any of the normatively referenced IETF RFCs, interoperability issues may arise. To prevent interoperability issues, the behaviour defined in the IETF RFCs must be maintained, and any such differences must be resolved in coordination with the IETF in a timely manner. + +Orange has expressed concerns that in the event of a difference between this ITU-T Recommendation and any of the normatively referenced IETF RFCs, interoperability issues may arise. To prevent interoperability issues, the behaviour defined in the IETF RFCs must be maintained, and any such differences must be resolved in coordination with the IETF in a timely manner. + +Verizon Communications has expressed concerns that in the event of a difference between this ITU-T Recommendation and the behavior defined in the normatively referenced IETF RFCs, interoperability issues may arise. There is no guidance in this ITU-T Recommendation that describes how to address differences in behaviour between the Recommendation and the normatively referenced IETF RFCs. Verizon Communications feels that any difference should be resolved in coordination with the IETF in a timely manner and until the issue is resolved, the behavior defined in the IETF RFCs should be maintained. + +2 This ITU-T Recommendation is intended to be aligned with the IETF MPLS RFCs normatively referenced by this Recommendation. + +Figure 1-1 presents the set of atomic functions associated with the traffic signal transport. The functions are based on the functional architecture as described in [ITU-T G.8110.1]. It is noted that this Recommendation only defines Ethernet for the client of MPLS-TP as multi-protocol label switching - transport profile / Ethernet MAC layer network (MT/ETH) adaptation function. + +![Diagram of MPLS-TP atomic functions showing various network interfaces and their adaptation functions (MT, MTp, MTs, MTsP, MTsC, MTsM, MTsE, MTsR) connected to a central MT (Multi-Protocol Transport) layer. The diagram illustrates the hierarchy of functions for different client types, including Ethernet (ETH_FP), SCC (SCC_FP), and MCC (MCC_FP).](2ee59e629035d641140e55f4d215b0d7_img.jpg) + +The diagram illustrates the functional architecture of MPLS-TP atomic functions. At the top, three client types are shown: ETH\_FP, SCC\_FP, and MCC\_FP. Each client type has a corresponding adaptation function (MT/ETH, MT/SCC, MT/MCC) which then connects to a central MT (Multi-Protocol Transport) layer. Below the MT layer, various network interfaces are shown, including Pq/MT, Pq-x/MT, Sn/MT, Sn-x/MT, ODUkP/MT, and ETH/MT. Each interface has its own adaptation function (e.g., MT, MTp, MTs, MTsP, MTsC, MTsM, MTsE, MTsR) that connects to the MT layer. The diagram also shows the hierarchy of functions for different client types, such as MT/MT, MTp, MTs, MTsP, MTsC, MTsM, MTsE, and MTsR. The central MT layer is represented by a large oval, and the various adaptation functions are represented by smaller ovals and rectangles. The diagram is labeled with 'G.8121-Y.1381(18)\_F1-1' in the bottom right corner. + +Diagram of MPLS-TP atomic functions showing various network interfaces and their adaptation functions (MT, MTp, MTs, MTsP, MTsC, MTsM, MTsE, MTsR) connected to a central MT (Multi-Protocol Transport) layer. The diagram illustrates the hierarchy of functions for different client types, including Ethernet (ETH\_FP), SCC (SCC\_FP), and MCC (MCC\_FP). + +**Figure 1-1 – MPLS-TP 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.704] Recommendation ITU-T G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels.* +- [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 (2016), *Interfaces for the optical transport network.* +- [ITU-T G.783] Recommendation ITU-T G.783 (2006), *Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks.* +- [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.832] Recommendation ITU-T G.832 (1998), *Transport of SDH elements on PDH networks – Frame and multiplexing structures.* +- [ITU-T G.7041] Recommendation ITU-T G.7041/Y.1303 (2016), *Generic framing procedure.* +- [ITU-T G.7043] Recommendation ITU-T G.7043/Y.1343 (2004), *Virtual concatenation of plesiochronous digital hierarchy (PDH) signals.* +- [ITU-T G.7044] Recommendation ITU-T G.7044/Y.1347 (2011), *Hitless adjustment of ODUflex(GFP).* +- [ITU-T G.7712] Recommendation ITU-T G.7712/Y.1703 (2010), *Architecture and specification of data communication network.* +- [ITU-T G.8021] Recommendation ITU-T G.8021/Y.1341 (2018), *Characteristics of Ethernet transport network equipment functional blocks.* +- [ITU-T G.8040] Recommendation ITU-T G.8040/Y.1340 (2005), *GFP frame mapping into Plesiochronous Digital Hierarchy (PDH).* +- [ITU-T G.8110.1] Recommendation ITU-T G.8110.1/Y.1370.1 (2011), *Architecture of the Multi-Protocol Label Switching transport profile layer network.* +- [ITU-T G.8131] Recommendation ITU-T G.8131/Y.1382 (2014), *Linear protection switching for MPLS transport profile.* +- [ITU-T G.8251] Recommendation ITU-T G.8251 (2010), *The control of jitter and wander within the optical transport network (OTN).* +- [ITU-T Y.1415] Recommendation ITU-T Y.1415 (2005), *Ethernet-MPLS network interworking – User plane interworking.* +- [IETF RFC 3031] IETF RFC 3031 (2001), *Multiprotocol Label Switching Architecture.* +- [IETF RFC 3032] IETF RFC 3032 (2001), *MPLS Label Stack Encoding.* +- [IETF RFC 3270] IETF RFC 3270 (2002), *Multi-Protocol Label Switching (MPLS) Support of Differentiated Services.* +- [IETF RFC 4448] IETF RFC 4448 (2006), *Encapsulation Methods for Transport of Ethernet over MPLS Networks.* +- [IETF RFC 4720] IETF RFC 4720 (2006), *Pseudowire Emulation Edge-to-Edge (PWE3) – Frame Check Sequence Retention.* +- [IETF RFC 5332] IETF RFC 5332 (2008), *MPLS Multicast Encapsulation.* +- [IETF RFC 5462] IETF RFC 5462 (2009), *Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field.* +- [IETF RFC 5586] IETF RFC 5586 (2009), *MPLS Generic Associated Channel.* +- [IETF RFC 5718] IETF RFC 5718 (2010), *An In-Band Data Communication Network For the MPLS Transport Profile.* +- [IETF RFC 6371] IETF RFC 6371 (2011), *Operations, Administration and Maintenance Framework for MPLS-Based Transport Networks.* +- [IETF RFC 6374] IETF RFC 6374 (2011), *Packet Loss and Delay Measurement for MPLS Networks.* +- [IETF RFC 6435] IETF RFC 6435 (2011), *MPLS Transport Profile Lock Instruct and Loopback Functions, plus Errata 3429 (2013)* + +# 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 **adapted information:** [ITU-T G.805] +- 3.1.3 **associated channel header:** [IETF RFC 5586] +- 3.1.4 **bottom of stack:** [IETF RFC 3032] +- 3.1.5 **characteristic information:** [ITU-T G.805] +- 3.1.6 **client/server relationship:** [ITU-T G.805] +- 3.1.7 **connection:** [ITU-T G.805] +- 3.1.8 **connection point:** [ITU-T G.805] +- 3.1.9 **explicitly TC-encoded-PSC LSP:** [IETF RFC 5462] +- 3.1.10 **G-ACh label:** [IETF RFC 5586] +- 3.1.11 **generic associated channel:** [IETF RFC 5586] +- 3.1.12 **label:** [IETF RFC 3031] +- 3.1.13 **label-only-inferred PSC LSP:** [IETF RFC 3270] +- 3.1.14 **label stack:** [IETF RFC 3031] +- 3.1.15 **label switched path:** [IETF RFC 3031] +- 3.1.16 **label value:** [IETF RFC 3032] +- 3.1.17 **layer network:** [ITU-T G.805] +- 3.1.18 **matrix:** [ITU-T G.805] +- 3.1.19 **MPLS label stack:** [IETF RFC 3031] +- 3.1.20 **network:** [ITU-T G.805] +- 3.1.21 **network connection:** [ITU-T G.805] +- 3.1.22 **per-hop behaviour:** [IETF RFC 3270] +- 3.1.23 **reference point:** [ITU-T G.805] +- 3.1.24 **subnetwork:** [ITU-T G.805] +- 3.1.25 **subnetwork connection:** [ITU-T G.805] +- 3.1.26 **termination connection point:** [ITU-T G.805] +- 3.1.27 **time-to-live:** [IETF RFC 3031] +- 3.1.28 **traffic class:** [IETF RFC 5462] +- 3.1.29 **trail:** [ITU-T G.805] +- 3.1.30 **trail termination:** [ITU-T G.805] +- 3.1.31 **transport:** [ITU-T G.805] +- 3.1.32 **transport entity:** [ITU-T G.805] +- 3.1.33 **transport processing function:** [ITU-T G.805] + +**3.1.34 unidirectional connection:** [ITU-T G.805] + +**3.1.35 unidirectional trail:** [ITU-T G.805] + +## **3.2 Terms defined in this Recommendation** + +None. + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|------------------------------------------------| +| ACH | Associated Channel Header | +| AI | Adapted Information | +| AIS | Alarm Indication Signal | +| AP | Access Point | +| APC | Automatic Protection Coordination | +| APS | Automatic Protection Switching | +| APSb | APS packet with incompatible "PT" | +| APSc | APS packet with incompatible Capabilities TLV | +| BWR | Bandwidth Resize | +| CC | Continuity Check | +| CC-V | Continuity Check and Connectivity Verification | +| CC/CV | Continuity Check or Connectivity Verification | +| CI | Characteristic Information | +| CII | Common Interworking Indicator | +| CoS | Class of Service | +| CP | Connection Point | +| CSF | Client Signal Fail | +| CSP | Client Specific Process | +| CV | Connectivity Verification | +| CW | Control Word | +| DCI | Detect Clearance Indication | +| DEG | Degraded Signal | +| DM | Delay Measurement | +| DP | Drop Precedence | +| DT | Diagnostic Test | +| ECC | Embedded Communication Channel | +| EMF | Equipment Management Function | +| ETH | Ethernet MAC layer network | +| ETY | Ethernet PHY layer network | +| E-LSP | Explicitly TC-encoded-PSC LSP | + +| | | +|---------|----------------------------------------------------| +| FDI | Forward Defect Indication | +| FP | Flow Point | +| FTP | Flow Termination Point | +| G-ACh | Generic Associated Channel | +| GAL | G-ACh Label | +| GFP | Generic Framing Procedure | +| HAO | Hitless Adjustment of ODUflex | +| iPHB | incoming PHB | +| L-LSP | Label-only-inferred PSC LSP | +| LCAS | Link Capacity Adjustment Scheme | +| LCK | Lock | +| LER | Label Edge Router | +| LKI | Lock Instruct | +| LKR | Lock Report | +| LM | Loss Measurement | +| LOC | Loss of Continuity | +| LOS | Loss of Signal | +| LSE | Label Stack Entry | +| LSP | Label Switched Path | +| LSR | Label Switching Router | +| LStack | Label Stack | +| MAC | Media Access Control | +| MCC | Maintenance Communication Channel | +| MEG | Maintenance Entity Group | +| MEL | Maintenance Entity group Level | +| MEP | Maintenance entity group (MEG) End Point | +| MI | Management Information | +| MIP | Maintenance entity group (MEG) Intermediate Point | +| MP | Management Point | +| MMG | Mismerge | +| MPLS | Multi-Protocol Label Switching | +| MPLS-TP | Multi-Protocol Label Switching – Transport Profile | +| MSRP | MPLS-TP Shared Ring Protection | +| MT | Multi-Protocol Label Switching – Transport Profile | +| MTDe | MPLS-TP MEP Diagnostic function | +| MTDi | MPLS-TP MIP Diagnostic function | +| NCM | Network Connection Monitoring | + +| | | +|------|-------------------------------------------------------------------------------------------------| +| NCS | Network Connectivity Status | +| NE | Network Element | +| NMS | Network Management System | +| OAM | Operation, Administration and Maintenance | +| ODU | Optical channel Data Unit | +| ODUk | Optical channel Data Unit – order k | +| oPHB | outgoing PHB | +| OPU | Optical Payload Unit | +| OPUk | Optical Payload Unit of level k | +| OTH | Optical Transport Hierarchy | +| OTN | Optical Transport Network | +| PDU | Protocol Data Unit | +| PFI | Payload Frame check sequence Indication | +| PHB | Per Hop Behaviour | +| PLM | Payload Mismatch | +| PM | Performance Monitoring | +| POH | Path Overhead | +| PSC | PHB Scheduling Class | +| PSI | Payload Structure Indication | +| PT | Payload Type | +| PTI | Payload Type Identifier | +| PW | Pseudowire | +| P11s | 1 544 kbit/s PDH path layer with synchronous 125 µs frame structure according to [ITU-T G.704] | +| P12s | 2 048 kbit/s PDH path layer with synchronous 125 µs frame structure according to [ITU-T G.704] | +| P31s | 34 368 kbit/s PDH path layer with synchronous 125 µs frame structure according to [ITU-T G.832] | +| P32e | 44 736 kbit/s PDH path layer with frame structure according to [ITU-T G.704] | +| RCOH | Resize Control Overhead | +| RDI | Remote Defect Indication | +| RES | Reserved overhead | +| RFC | IETF Request For Comments | +| RI | Remote Information | +| RP | Remote Point | +| RPS | Ring Protection Switch | +| RT | Route Tracing | + +| | | +|---------|-------------------------------------------------------------------| +| SCC | Signalling Communication Channel | +| SCCType | Signalling Communication Channel Type | +| SCN | Signalling Communication Network | +| SD | Signal Degrade | +| SDH | Synchronous Digital Hierarchy | +| SDL | Specification and Description Language | +| SLM | Synthetic Loss Measurement | +| SNC | Subnetwork Connection | +| SNCP | Subnetwork Connection Protection | +| SNC/S | SNCP with Sublayer monitoring | +| SPME | Sub-Path Maintenance Element | +| SSD | Server Signal Degrade | +| SSF | Server Signal Fail | +| TC | Traffic Class | +| TCM | Tandem Connection Monitoring | +| TCP | Termination Connection Point | +| TFP | Termination Flow Point | +| TH | Throughput | +| TLV | Type Length Value | +| TSD | Trail Signal Degrade | +| TSF | Trail Signal Fail | +| TTL | Time-To-Live | +| TTSI | Trail Termination Source Identifier | +| UNC | Unexpected CoS | +| UNM | Unexpected MEP | +| UNP | Unexpected Period | +| UPI | User Payload Identifier | +| VLI | Virtual concatenation/Link capacity adjustment scheme Information | +| WTR | Wait-To-Restore | + +# 5 Conventions + +The diagrammatic convention for connection-oriented layer networks described in this Recommendation is that of [ITU-T G.805]. + +# 6 Supervision + +The generic supervision functions are defined in clause 6 of [ITU-T G.806]. Specific supervision functions for the MPLS-TP network are defined in this clause. + +## 6.1 Defects + +### 6.1.1 Summary of entry/exit conditions for defects + +The defect entry and exit conditions are based on events. Occurrence or absence of specific events may raise or reset specific defects. + +In the following: + +Valid means a received value is *equal* to the value configured via the management information (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 as a quick overview. Events, other than the protection switching events, are generated by processes in the MT\_TT\_Sk function as defined in clause 9.2. 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 | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| unexpMEG | Reception of a CC-V packet with an invalid maintenance entity group (MEG) value.(Note 1)
NOTE – Clause 5.1.1 of [IETF RFC 6371] describes the conditions when a received CC-V packet is considered to have invalid MEG and maintenance entity group end point (MEP) values. In case (1) a CC packet is received by a sink MEP monitoring the MEG for CC and CV functions, or (2) a CV packet is received by a sink MEP monitoring the MEG for CC-only function; the received CC-V packet is considered as having an invalid MEG value (thus triggering the unexpMEG event) | +| unexpMEP | Reception of a CV packet with an invalid MEP value, but with a valid MEG value. | +| unexpPeriod | Reception of a CC-V packet with an invalid Periodicity value, but with valid MEG and MEP values. | +| unexpCoS | Reception of a CC-V packet with an invalid traffic class (TC) value, but with valid MEG and MEP values. | +| expCC-V | Reception of a CC-V packet with valid MEG and MEP values. | +| RDI=x | Reception of a CC-V packet for the peer MEP with the remote defect indication (RDI) information indicate to x; where x=0 (remote defect clear) and x=1 (remote defect set). | +| LCK | Reception of a locked (LCK) packet. (Note 2) | +| AIS | Reception of an alarm indication signal (AIS) packet. | +| BS | Bad second, a second in which the lost frame ratio exceeds the bad second threshold (BS_THR). | +| CSF-LOS | Reception of a client signal fail (CSF) packet that indicates "Client Loss of Signal". | +| CSF-FDI | Reception of a CSF packet that indicates "Client Forward Defect Indication". | +| CSF-RDI | Reception of a CSF packet that indicates "Client Reverse Defect Indication". | +| expAPS | Reception of a valid APS packet. (Note3) | +| APSw | Reception of an automatic protection switching (APS) packet from the working transport entity. | +| APSb | Reception of an APS packet with incompatible "PT" field value. | + +**Table 6-1 – Overview of events** + +| Event | Meaning | +|-------|------------------------------------------------------------------------------| +| APSc | Reception of an APS packet with incompatible "Capabilities TLV" information. | +| APSr | Reception of an APS packet with incompatible "Data Path" value. (Note 4) | + +NOTE 1 – According to [IETF RFC 6371], a CC-V packet is either a CC packet or a CV packet. A CV packet performs both CC and CV OAM functions. A CC packet performs only CC OAM function. +NOTE 2 – IETF uses this term LCK as lock report (LKR) and lock instruct (LKI) in [IETF RFC 6371] +NOTE 3 – For the term APS, [ITU-T G.8131] conventionally uses the term automatic protection coordination (APC) for the protocol of MPLS-TP linear protection. +NOTE 4 – One way to detect this event is to detect that the transmitted "Data Path" and the received "Data Path" 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. + +Table 6-2 gives a quick overview of the types of defects for MPLS-TP layer and the raising and clearing conditions for these defects as described in [IETF RFC 6371]. + +**Table 6-2 – Overview of detection and clearing conditions** + +| Defect | Defect detection | Clearing condition | +|----------|------------------------------------|----------------------------------------------| +| dLOC | #expCC-V==0 (K × CC_Period) | expCC-V | +| dUNC | unexpCoS | #unexpCoS==0 (K × CC-V_Period) | +| dMMG | unexpMEG | #unexpMEG==0 (K × CC-V_Period) | +| dUNM | unexpMEP | #unexpMEP==0 (K × CC-V_Period) | +| dUNP | unexpPeriod | #unexpPeriod==0 (K × CC-V_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 | #BS==DEGM (DEGM × 1second) | #BS==0 (M × 1second) | +| dFOP-PMb | APSB | expAPS | +| dFOP-PMc | APSc | expAPS | +| dFOP-NR | APSr continues more than 50ms | expAPS | +| dFOP-CM | APSw | #APSw == 0 (K × normal APS Period) | +| dFOP-TO | #expAPS==0 (K × long APS interval) | expAPS | + +### 6.1.2 Continuity supervision + +![Flowchart of the dLOC detection and clearance process.](c85ded401105f62f2d6ff26b3b5eb4af_img.jpg) + +``` + +graph TD + Start([dLOC detection and clearance]) --> Set1[Set(K × MI_CC_Period, Timer)] + Set1 --> Cleared([dLOC Cleared]) + Cleared --> expCC1{expCC} + Cleared --> Timer1{Timer} + expCC1 --> Reset[Reset Timer +Set(K × MI_CC_Period, Timer)] + Timer1 --> dLOC1{dLOC} + Reset --> Detected([dLOC detected]) + dLOC1 --> Detected + Detected --> expCC2{expCC} + expCC2 --> Set2[Set(K × MI_CC_Period, Timer)] + Set2 --> NotdLOC{!dLOC} + 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 rectangular box 'Set(K×MI\_CC\_Period, Timer)'. This box points down to a rounded rectangle 'dLOC Cleared'. From 'dLOC Cleared', two arrows branch out: one to a chevron-shaped box 'expCC' and another to a chevron-shaped box 'Timer'. The 'expCC' box points down to a rectangular box 'Reset Timer Set(K×MI\_CC\_Period, Timer)'. The 'Timer' box points down to a chevron-shaped box 'dLOC'. Both the 'Reset Timer' box and the 'dLOC' box point down to a rounded rectangle 'dLOC detected'. From 'dLOC detected', an arrow points down to a chevron-shaped box 'expCC', which in turn points down to a rectangular box 'Set(K×MI\_CC\_Period, Timer)'. This box points down to a chevron-shaped box '!dLOC'. Finally, an arrow from the '!dLOC' box loops back up to the first 'Set(K×MI\_CC\_Period, Timer)' box. A small label 'G.8121-Y.1381(16)\_F6-1' is located at the bottom right of the diagram. + +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 MT layer. It monitors the presence of continuity in MT trails. + +Its detection and clearance are defined in Figure 6-1. The 'period' in Figure 6-1 is set to $K \times MI\_CC\_Period$ , where $MI\_CC\_Period$ corresponds to the configured CC Period and $K$ is such that $3.25 \le K \le 3.5$ . + +### 6.1.3 Connectivity supervision + +![Flowchart of the defect detection and clearance process for various defects (dMMG, dUNM, dUNP, dUNC, dAIS, dLCK, dCSF).](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +``` + +graph TD + Start([Defect detection and clearance]) --> Cleared{ Cleared} + Cleared --> EventPeriod[/(Period)/] + EventPeriod --> Defect{} + Defect --> SetTimer[Set(K×Period, Timer) +Old_Period=Period] + SetTimer --> Detected{ Detected} + Detected --> EventPeriod2[/(Period)/] + Detected --> ClearEvent[//] + Detected --> Timer[/Timer/] + EventPeriod2 --> ResetTimer1[Reset(Timer)] + ClearEvent --> ResetTimer2[Reset(Timer)] + Timer --> NotDefect1{!} + ResetTimer1 --> PeriodOldPeriod{Period NotDefect2{!} + PeriodOldPeriod -- Y --> SetOldPeriod[Set(K×Old_Period, Timer)] + PeriodOldPeriod -- N --> SetPeriod[Set(K×Period, Timer)] + SetPeriod --> OldPeriod[Old_Period=Period] + SetOldPeriod --> Detected + OldPeriod --> Detected + NotDefect1 --> Detected + NotDefect2 --> Detected + +``` + +The flowchart illustrates the defect detection and clearance process. It begins with 'Defect detection and clearance', leading to a state where the defect is cleared. Upon receiving an event with a period, if a defect is detected, the timer is set to $K \times \text{Period}$ and $\text{Old\_Period} = \text{Period}$ . When the defect is detected, three paths are possible: an event with a period, a clear event, or a timer expiration. Both event and clear event paths lead to a timer reset. The timer path leads to a state where the defect is not detected. After a reset, if the current period is less than the old period, the timer is reset to $K \times \text{Old\_Period}$ ; otherwise, it is reset to $K \times \text{Period}$ and $\text{Old\_Period}$ is updated. All paths eventually lead back to the detection state or the initial clearance state. + +Flowchart of the defect detection and clearance process for various defects (dMMG, dUNM, dUNP, dUNC, dAIS, dLCK, dCSF). + +G.8121-Y.1381(16)\_F6-2 + +**Figure 6-2 – Defect detection and clearance process for dMMG, dUNM, dUNP, dUNC, dAIS, dLCK and dCSF** + +Figure 6-2 shows a generic state diagram that is used to detect and clear the dMMG, dUNM, dUNP, dUNC, dAIS, dLCK and dCSF (dCSF-LOS, dCSF-FDI, and dCSF-RDI) 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 operation, administration and maintenance (OAM) packet 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 Mismerge defect (dMMG) + +The mismerge defect detect is calculated at the MT layer. It monitors the connectivity in a maintenance entity group (MEG). + +Its detection and clearance are defined in Figure 6-2. The in Figure 6-2 is dMMG. The in Figure 6-2 is the unexpectedMEG event and the "Period" is the period carried in the CV packet that triggered the event, unless an earlier CV packet triggering an unexpectedMEG event carried a greater period. + +#### 6.1.3.2 Unexpected MEP defect (dUNM) + +The unexpected MEP defect is calculated at the MT 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 unexpectedMEP event and the Period is the Period carried in the CV packet that triggered the event, unless an earlier CV packet triggering an unexpectedMEP event carried a greater period. + +#### 6.1.3.3 Degraded signal defect (dDEG) + +![Flowchart of the dDEG detection and clearance process. The process starts with 'dDEC detection and clearance', which leads to 'BS=GS=0' and 'BadSecond=0'. From there, it branches into two main paths. The left path is for 'dDEG Cleared', which checks 'nN_TF(N_TF)' and 'nN_LF(N_LF)', updates 'BS and GS', and then checks if 'BS==MI_LM_DEGM'. If 'Yes', it leads to 'dDEG' (defect state); if 'No', it loops back to the start of the 'dDEG Cleared' path. The right path is for 'dDEG detected', which also checks 'nN_TF(N_TF)' and 'nN_LF(N_LF)', updates 'BS and GS', and then checks if 'GS==MI_LM_M'. If 'Yes', it leads to '!dDEG' (cleared state); if 'No', it loops back to the start of the 'dDEG detected' path. A third path on the far right starts with 'Update BS and GS', then checks 'If (N_TF>TF_MIN) && (N_LF>=0)'. If 'Yes', it checks 'If (N_LF/N_TF)>MI_LM_DEGTHR'. If 'Yes', it sets 'BadSecond=1'; if 'No', it sets 'BadSecond=0'. Both 'BadSecond=1' and 'BadSecond=0' lead to 'If BadSecond'. If 'Yes', it sets 'GS=0' and 'BS++'; if 'No', it sets 'GS++' and 'BS=0'. Both 'GS=0 BS++' and 'GS++ BS=0' lead to a circle with an 'X' (exit/merge point). The text 'G.8121-Y.1381(16)_F6-3' is in the bottom right corner.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Flowchart of the dDEG detection and clearance process. The process starts with 'dDEC detection and clearance', which leads to 'BS=GS=0' and 'BadSecond=0'. From there, it branches into two main paths. The left path is for 'dDEG Cleared', which checks 'nN\_TF(N\_TF)' and 'nN\_LF(N\_LF)', updates 'BS and GS', and then checks if 'BS==MI\_LM\_DEGM'. If 'Yes', it leads to 'dDEG' (defect state); if 'No', it loops back to the start of the 'dDEG Cleared' path. The right path is for 'dDEG detected', which also checks 'nN\_TF(N\_TF)' and 'nN\_LF(N\_LF)', updates 'BS and GS', and then checks if 'GS==MI\_LM\_M'. If 'Yes', it leads to '!dDEG' (cleared state); if 'No', it loops back to the start of the 'dDEG detected' path. A third path on the far right starts with 'Update BS and GS', then checks 'If (N\_TF>TF\_MIN) && (N\_LF>=0)'. If 'Yes', it checks 'If (N\_LF/N\_TF)>MI\_LM\_DEGTHR'. If 'Yes', it sets 'BadSecond=1'; if 'No', it sets 'BadSecond=0'. Both 'BadSecond=1' and 'BadSecond=0' lead to 'If BadSecond'. If 'Yes', it sets 'GS=0' and 'BS++'; if 'No', it sets 'GS++' and 'BS=0'. Both 'GS=0 BS++' and 'GS++ BS=0' lead to a circle with an 'X' (exit/merge point). The text 'G.8121-Y.1381(16)\_F6-3' is in the bottom right corner. + +Figure 6-3 – dDEG detection and clearance process + +The degraded signal defect (dDEG) is calculated at the MT layer. It monitors the connectivity of a MT trail. + +Its detection and clearance are defined Figure 6-3. + +Every second the state machine receives the 1 second counters for the 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 (TF\_MIN). If this is true, then a bad second is declared if either the frame loss is negative (i.e., there are more frames received than transmitted) or the frame loss ratio (i.e., lost frames/transmitted frames) is greater than MI\_LM\_DEGTHR. + +### 6.1.4 Protocol supervision + +#### 6.1.4.1 Unexpected periodicity defect (dUNP) + +The unexpected periodicity defect is calculated at the MT layer. It detects the configuration of different periodicities at different MEPs belonging to the same MEG. + +Its detection and clearance are defined Figure 6-2. The in Figure 6-2 is dUNP. The in Figure 6-2 is the unexpectedPeriod event and the "Period" is the period carried in the CC-V packet that triggered the event, unless an earlier CC-V packet triggering an unexpectedPeriod event carried a greater period. + +#### 6.1.4.2 Unexpected CoS defect (dUNC) + +The unexpected class of service (CoS) defect is detected at the MT layer. It detects the configuration error of different CoS at different MEPs belonging to the same MEG. + +Its detection and clearance are defined Figure 6-2. + +The in Figure 6-2 is dUNC. The in Figure 6-2 is the unexpectedCoS event and the "Period" is the period associated with the CC-V packet that triggered the event, unless an earlier CC-V packet triggering an unexpectedCoS event carried a greater period. + +#### 6.1.4.3 Protection protocol supervision + +For linear protection, the failure of protocol defects are applied in the case of a bidirectional protection switching operation, where the coordination between the two ends is needed. + +##### 6.1.4.3.1 Linear protection failure of protocol provisioning mismatch on bridge type (dFOP-PMb) + +The failure of protocol provisioning mismatch – bridge type defect is calculated at the MT layer. It monitors the provisioning mismatch on bridge type: + +- By comparing bridge type (i.e., selector bridge or permanent bridge) of the transmitted and the received APS packets. The reception of an APS packet with incompatible bridge type results in APSb event as defined in Table 6-1. +- In case of APS protocol defined in [ITU-T G.8131], the bridge type is signalled in the Protection type field as defined in clause 8 of [ITU-T G.8131]. If the value of the PT field of one side is 2 (i.e., selector bridge) and the value of PT field of the other side is 1 or 3 (i.e., permanent bridge), then this will result in an APCb event as defined in Table 6-1. + +dFOP-PMb defect detection and clearing condition are defined in Table 6-2. + +dFOP-PMb is detected on the receipt of an APSb event and is cleared on the receipt of an expAPS event. + +The detection and clearance events of the defects are generated by the subnetwork connection protection process (clause 9.1.1). + +##### 6.1.4.3.2 Linear protection failure of protocol provisioning mismatch on Capabilities TLV (dFOP-PMc) + +The failure of protocol provisioning mismatch – Capabilities TLV defect is calculated at the MT layer. It monitors the provisioning mismatch on Capabilities TLV as defined in clause 8.1 of [ITU-T G.8131]: + +- by comparing the 12 octet Capabilities TLV information of the received APS packets with the default values defined in clause 8.1 of [ITU-T G.8131]. + +dFOP-PMc defect detection and clearing condition are defined in Table 6-2. + +dFOP-PMc is detected on the receipt of an APSc event and is cleared on the receipt of an expAPS event. + +The detection and clearance events of the defects are generated by the subnetwork connection protection process (clause 9.1.1). + +##### **6.1.4.3.3 Linear protection failure of protocol no response (dFOP-NR)** + +The failure of protocol no response defect is calculated at the MT layer. It monitors incompletion of protection switching by comparing the transmitted "Data Path" and the received "Data Path" values in the APS protocol. + +dFOP-NR defect detection and clearing condition are defined in Table 6-2. + +dFOP-NR is detected when an APSr event continues for more than 50ms and it is cleared on the receipt of the expAPS event. + +The detection and clearance events of the defects are generated by the subnetwork connection protection process (clause 9.1.1). + +##### **6.1.4.3.4 Linear protection failure of protocol configuration mismatch (dFOP-CM)** + +The failure of protocol configuration mismatch defect is calculated at the MT layer. It monitors working and protection configuration mismatch by detecting the receipt of the APS packet from the working transport entity. + +dFOP-CM defect detection and clearing condition are defined in Table 6-2. + +dFOP-CM is detected on the receipt of an APSw event and is cleared on the receipt of no APSw event during K times the long APS transmission period defined in [ITU-T G.8131], where $3.25 \leq K \leq 3.5$ . + +The detection and clearance events of the defects are generated by the subnetwork connection protection process (clause 9.1.1). + +##### **6.1.4.3.5 Linear protection failure of protocol time out (dFOP-TO)** + +The failure of protocol time out defect is calculated at the MT layer. It monitors the time out defect by detecting the prolonged absence of expected APS packets. + +dFOP-TO defect detection and clearing condition are defined in Table 6-2. + +dFOP-TO is detected on the receipt of no expAPS event during K times the long APS interval defined in [ITU-T G.8131] (where $K \geq 3.5$ ). dFOP-TO is cleared on the receipt of an expAPS event. + +The detection and clearance events of the defects are generated by the subnetwork connection protection process (clause 9.1.1). + +### **6.1.5 Maintenance signal supervision** + +#### **6.1.5.1 Remote defect indicator defect (dRDI)** + +The remote defect indicator defect (dRDI) is detected at the MT layer. It monitors the presence of the RDI maintenance signal. + +dRDI is detected on the receipt of the RDI=1 event and is cleared on receipt of the RDI=0 event. + +#### **6.1.5.2 Alarm indication signal defect (dAIS)** + +The alarm indication signal defect (dAIS) is detected at the MT layer. It monitors the presence of the AIS maintenance signal. + +dAIS defect detection and clearance process are illustrated in Figure 6-2. The in Figure 6-2 is dAIS. The in Figure 6-2 is the AIS event and the "Period" is the period associated with the AIS packet unless an earlier AIS packet was associated with a greater period. + +#### 6.1.5.3 Locked defect (dLCK) + +The locked defect (dLCK) is detected at the MT layer. It monitors the presence of the locked maintenance signal. + +dLCK defect detection and clearance process are illustrated in Figure 6-2. The in Figure 6-2 is dLCK. The in Figure 6-2 is the LCK event and the "Period" is the period associated with the LCK packet unless an earlier LCK packet was associated with a greater period. + +#### 6.1.5.4 Client signal fail defect (dCSF) + +The CSF (i.e., CSF-LOS, CSF-FDI and CSF-RDI) defect is detected at the MT layer. It monitors the presence of the CSF maintenance signal. + +dCSF defect detection and clearance process conditions are illustrated 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 and the "Period" is the period associated with the CSF packet unless an earlier CSF packet was associated with a greater period + +The in Figure 6-2 is the CSF event which indicates detect clearance indication (DCI). + +## 6.2 Consequent actions + +For generic consequent actions, see [ITU-T G.806]. For the specific consequent actions applicable to MPLS-TP, refer to the specific atomic functions. + +## 6.3 Defect correlations + +For the defect correlations, see the specific atomic functions. + +## 6.4 Performance filters + +For further study. + +# 7 Information flow across reference points + +Information flow for MPLS-TP functions is defined in clause 9. A generic description of information flow is defined in clause 7 of [ITU-T G.806]. + +# 8 MPLS-TP processes + +This clause defines the specific processes for the MPLS-TP network. Generic processes are defined in clause 8 of [ITU-T G.806]. + +## 8.1 G-ACh process + +### 8.1.1 Overview + +In order to ensure proper operational control, MPLS-TP network elements exchange OAM packets that strictly follow the same path as user traffic packets; that is, OAM packets are subject to the exact same forwarding schemes (e.g., fate sharing) as the user traffic packets. These OAM packets can be distinguished from the user traffic packets by using the G-ACh and G-ACh label (GAL) constructs. + +The G-ACh is a generic associated control channel mechanism for "sections", label switched paths (LSPs) and pseudowires (PWs), over which OAM and other control messages can be exchanged. The GAL is a label based exception mechanism to alert label edge routers/label switching routers (LERs/LSRs) of the presence of an associated channel header (ACH) after the bottom of the stack. + +The format of GAL and ACH is described in [IETF RFC 5586]. + +### 8.1.2 G-ACh insertion process + +Figure 8-1 describes G-ACh insertion process. + +![Diagram of the G-ACh insertion process. At the top, three input signals labeled D, iPHB, and oPHB enter a large rectangular box. Inside this box, on the left, there is an 'OAM' block receiving inputs from MI_GAL_Enable, PDU, TTL, PHB, and ChannelType. Below the OAM block is a 'G-ACh/GAL Generation' block. To the right of these is a 'Data' block. Below the Data block is a 'G-ACh Traffic Extraction' block. Arrows show the flow from the OAM and Generation blocks into the G-ACh block, and from the G-ACh and Data blocks into the Extraction block. At the bottom of the large box, three output signals labeled D, iPHB, and oPHB exit.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +Diagram of the G-ACh insertion process. At the top, three input signals labeled D, iPHB, and oPHB enter a large rectangular box. Inside this box, on the left, there is an 'OAM' block receiving inputs from MI\_GAL\_Enable, PDU, TTL, PHB, and ChannelType. Below the OAM block is a 'G-ACh/GAL Generation' block. To the right of these is a 'Data' block. Below the Data block is a 'G-ACh Traffic Extraction' block. Arrows show the flow from the OAM and Generation blocks into the G-ACh block, and from the G-ACh and Data blocks into the Extraction block. At the bottom of the large box, three output signals labeled D, iPHB, and oPHB exit. + +Figure 8-1 – G-ACh insertion process + +The G-ACh insertion process encapsulates OAM packets and multiplexes them with the data packets. The data packets are passed through unchanged, while the OAM packets are encapsulated as follows: + +A G-ACh header is prepended to the OAM PDU, with the channel type set to the specified value. If MI\_GAL\_Enable is true, the process then further prepends a G-ACh label (GAL) as described in [IETF RFC 5586]. If the time-to-live (TTL) signal is not specified, the TTL field in the MI\_CI\_D is set to 255; otherwise, it is set to the value in the TTL signal. If a GAL is inserted, the TTL field in the GAL label stack entry (LSE) is set as defined in [IETF RFC 5586]. + +NOTE 1 – Certain OAM packets can be addressed to a MIP and thus need to be inserted with a specific TTL to ensure that the TTL expires at the target MIP. OAM packets addressed to a MEP have the TTL set to 255. + +NOTE 2 – MI\_GAL\_Enable must be set to true on LSPs and to false on PWs. Setting it to true for PWs is for further study. + +### 8.1.3 G-ACh extraction process + +Figure 8-2 describes G-ACh extraction process. + +![Figure 8-2: G-ACh extraction process diagram. The diagram shows a stack of layers. At the top, four arrows point upwards labeled D, iPHB, oPHB, and LStack. Below these is a large rectangular block. Inside this block, on the left, is an 'OAM' sub-block with inputs MI_GAL_Enable, PDU, PHB, and ChannelType. To the right of OAM is a 'G-ACh/GAL Extraction' sub-block. Below the large block is a 'G-ACh traffic extraction' block containing 'G-ACh' and 'Data' sub-blocks. At the bottom, four arrows point upwards labeled D, iPHB, oPHB, and LStack. A label G.8121-Y.1381(16)_F8-2 is at the bottom right.](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg) + +Figure 8-2: G-ACh extraction process diagram. The diagram shows a stack of layers. At the top, four arrows point upwards labeled D, iPHB, oPHB, and LStack. Below these is a large rectangular block. Inside this block, on the left, is an 'OAM' sub-block with inputs MI\_GAL\_Enable, PDU, PHB, and ChannelType. To the right of OAM is a 'G-ACh/GAL Extraction' sub-block. Below the large block is a 'G-ACh traffic extraction' block containing 'G-ACh' and 'Data' sub-blocks. At the bottom, four arrows point upwards labeled D, iPHB, oPHB, and LStack. A label G.8121-Y.1381(16)\_F8-2 is at the bottom right. + +**Figure 8-2 – G-ACh extraction process** + +The G-ACh traffic unit will be extracted if it includes GAL and ACH in the incoming data when MI\_GAL\_Enable is set. + +## 8.2 TC/Label processes + +The TC/Label processes can operate in two modes, as described in clause 7.3 of [ITU-T G.8110.1]. Mode 1 is the default mode and is mandatory. Mode 2 is optional and is only used for section monitoring. The mode is set as MI\_Mode by the equipment management function (EMF); it is expected that the EMF sets this automatically to the appropriate value depending on whether the MEP is monitoring a section or a PW/LSP. It is not expected that this MI is exposed to the user. + +NOTE – MI\_Mode is always set to mode 1 when the TC/Label process is within a MT/MT\_A function, since a MPLS section is the lowest monitoring level and is only applicable to monitoring directly over the (non-MPLS) server layer. In a Server/MT\_A function, the TC/Label process may operate in mode 1 (if there is no section MEP) or mode 2 (if there is a section MEP). + +### 8.2.1 TC/Label source processes + +![Figure 8-3: TC/Label source processes in mode 1 diagram. The diagram shows a flow of data through several blocks. Inputs on the left include LSPTYPE[m], CoS[m], PHB2TCMapping[m], QoSEncodingMode[m], and Label[m]. The first block is 'Insert TC' with inputs D, iPHB, oPHB and outputs D, PHB. The second block is 'Insert label' with input Label[m] and outputs D, PHB. This is followed by a series of blocks labeled CSP#1, CSP#2, ..., CSP#M, each with inputs D, PHB and output D. All these blocks feed into a wide 'Interleave' block at the bottom, which outputs D and PHB. A label G.8121-Y.1381(13)_F8-3 is at the bottom right.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure 8-3: TC/Label source processes in mode 1 diagram. The diagram shows a flow of data through several blocks. Inputs on the left include LSPTYPE[m], CoS[m], PHB2TCMapping[m], QoSEncodingMode[m], and Label[m]. The first block is 'Insert TC' with inputs D, iPHB, oPHB and outputs D, PHB. The second block is 'Insert label' with input Label[m] and outputs D, PHB. This is followed by a series of blocks labeled CSP#1, CSP#2, ..., CSP#M, each with inputs D, PHB and output D. All these blocks feed into a wide 'Interleave' block at the bottom, which outputs D and PHB. A label G.8121-Y.1381(13)\_F8-3 is at the bottom right. + +**Figure 8-3 – TC/Label source processes in mode 1** + +Figure 8-3 shows the TC/Label source processes when MI\_Mode is set to mode 1. These processes are performed on a packet-per-packet basis. + +**Client specific processes:** The function supports $M$ ( $M \leq 2^N - 16$ , with $N = 20$ for MPLS label) client specific processes (CSP#1 to CSP# $M$ ), each connected to a single MPLS-TP connection point. CSP# $m$ ( $1 \leq m \leq M$ ) is active when Label[ $m$ ] has a value in the range of 16 to $2^N - 1$ . + +**TC insertion process:** Insert the TC field, encoding the PHB information according to the following rules: + +- If LSPTYPE[ $m$ ] = L-LSP, the drop precedence (DP) information is encoded into the TC field according to [ITU-T G.8110.1] and CoS[ $m$ ]. +- If LSPTYPE[ $m$ ] = E-LSP, the PHB information is encoded into the TC field according to the 1:1 mapping configured in the PHB2TCMapping[ $m$ ]. + +NOTE – E-LSP and L-LSP are referred to in [ITU-T G.8110.1] + +The PHB information to map into the TC field is selected according to the following rules: + +- If QoSEncodingMode[ $m$ ] = A, the iPHB information is mapped into the TC field. +- If QoSEncodingMode[ $m$ ] = B, the oPHB information is mapped into the TC field. + +**Label insertion process:** Insert the 20-bit MPLS Label field with the value provided via Label[ $m$ ]. + +**Interleave process:** Interleave the MPLS-TP traffic units from the client specific processes into a single stream. + +When MI\_Mode is set to mode 2, the TC/Label source process simply deletes the TTL and S fields from each MPLS traffic unit. + +### 8.2.2 TC/Label sink processes + +![Diagram of TC/Label sink processes in mode 1. A 'De-interleave' block at the bottom receives an input stream with 'D' (Drop Precedence) and 'PHB' (Per-Hop Behavior) fields. It outputs to multiple client-specific process blocks: CSP#1, CSP#2, ..., CSP#M. Each CSP block contains a 'Decrement TTL' block, a 'Generate PHB' block, and an 'Extract label/TC' block. The 'Extract label/TC' block outputs 'D', 'iPHB', and 'oPHB' fields. Configuration parameters LSPTYPE[m], CoS[m], TC2PHBMapping[m], and QoSDecodingMode[m] are shown as inputs to the 'Extract label/TC' block. The label 'Label[m]' is shown as an input to the 'De-interleave' block. A reference code 'G.8121-Y.1381(13)_F8-4' is in the bottom right.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +Diagram of TC/Label sink processes in mode 1. A 'De-interleave' block at the bottom receives an input stream with 'D' (Drop Precedence) and 'PHB' (Per-Hop Behavior) fields. It outputs to multiple client-specific process blocks: CSP#1, CSP#2, ..., CSP#M. Each CSP block contains a 'Decrement TTL' block, a 'Generate PHB' block, and an 'Extract label/TC' block. The 'Extract label/TC' block outputs 'D', 'iPHB', and 'oPHB' fields. Configuration parameters LSPTYPE[m], CoS[m], TC2PHBMapping[m], and QoSDecodingMode[m] are shown as inputs to the 'Extract label/TC' block. The label 'Label[m]' is shown as an input to the 'De-interleave' block. A reference code 'G.8121-Y.1381(13)\_F8-4' is in the bottom right. + +Figure 8-4 – TC/Label sink processes in mode 1 + +Figure 8-4 shows the TC/Label sink processes when MI\_Mode is set to mode 1. These processes are performed on a packet-per-packet basis. + +**Deinterleave process:** Deinterleaves the MPLS-TP traffic units and forwards each of its client specific process # $m$ based on the value in the Label field of the traffic unit. Relation between CSP and MPLS label value is provided by Label[1.. $M$ ]. + +Traffic units received with a label value identifying a non-active CSP are dropped. + +**Client specific processes:** The function supports $M$ ( $M \leq 2^N - 16$ , with $N = 20$ for MPLS label) client specific processes (CSP#1 to CSP# $M$ ), each connected to a single MPLS-TP connection point. CSP# $m$ ( $1 \leq m \leq M$ ) is active when Label[ $m$ ] has a value in the range of 16 to $2^N - 1$ . + +**Label and TC extraction process:** Extracts the MPLS label and the TC fields from the traffic unit. + +**TTL decrement process:** Decrements the TTL. If the MPLS-TP CP is not a TCP and the decremented TTL is less than or equal to zero, the traffic unit is dropped silently. + +NOTE – MIPs and MEPs compound functions are connected to the Server/MT\_A (or MT/MT\_A) functions via a MPLS-TP TCP. + +**PHB generation process:** Processes the TC field. + +The iPHB signal is generated according to the following rules: + +- If LSPTYPE[m] = L-LSP, the CoS information is equal to the CoS[m] while the DP information is decoded from the TC field according to [ITU-T G.8110.1] and the CoS[m]. +- If LSPTYPE[m] = E-LSP, the PHB information is decoded from the TC field according to the 1:1 mapping configured in the TC2PHBMAPPING[m]. + +NOTE – E-LSP and L-LSP are referred to in [ITU-T G.8110.1] + +The CI\_oPHB is generated according to the following rule: + +- If QoSDecodingMode = A, the oPHB is equal to the generated iPHB. +- If QoSDecodingMode = B, the oPHB is equal to the received PHB. + +When MI\_Mode is set to mode 2, the TC/Label sink process simply inserts a TTL and a S field on to each MPLS traffic unit, with the values set to 254 and 0 respectively. + +### 8.2.3 Label stack copy process + +![Diagram of the Label stack copy process. A central box labeled 'Label stack copy process' has an input arrow labeled 'D' pointing into it from the bottom. It has two output arrows: one labeled 'D' pointing upwards and another labeled 'LStack' pointing upwards. Below the input arrow is the text 'G.8121-Y.1381(13)_F8-5'.](f1fbb1287d999c7034742de35bdab836_img.jpg) + +``` +graph TD; D_in[D] --> LSCP[Label stack copy process]; LSCP --> D_out[D]; LSCP --> LStack[LStack]; G8121[G.8121-Y.1381(13)_F8-5] +``` + +Diagram of the Label stack copy process. A central box labeled 'Label stack copy process' has an input arrow labeled 'D' pointing into it from the bottom. It has two output arrows: one labeled 'D' pointing upwards and another labeled 'LStack' pointing upwards. Below the input arrow is the text 'G.8121-Y.1381(13)\_F8-5'. + +**Figure 8-5 – Label stack copy process** + +Figure 8-5 shows Label stack copy process. It passes through the CI\_D unchanged and copies from the CI\_D traffic unit the complete label stack. + +The LStack information is lost at the input of Server/MT and MT/MT source adaptation function and at the input of MT/Client sink adaptation function. + +## 8.3 Queuing process + +The Queuing process buffers received MPLS packets for output according to the CI\_oPHB. Figure 8-6 shows Queuing process. The details of the Queuing process implementation are out of the scope of this Recommendation. + +The Queuing process is also responsible for dropping packets if their rate at the MT\_CI is higher than the \_AI\_D can accommodate. Performance monitor counters are for further study. + +![Figure 8-6: Queuing process diagram. Two input arrows labeled 'oPHB' and 'D' enter a box labeled 'Queuing'. Two output arrows labeled 'oPHB' and 'D' exit the box. Below the output arrows is the text 'G.8121-Y.1381(13)_F8-6'.](aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg) + +Figure 8-6: Queuing process diagram. Two input arrows labeled 'oPHB' and 'D' enter a box labeled 'Queuing'. Two output arrows labeled 'oPHB' and 'D' exit the box. Below the output arrows is the text 'G.8121-Y.1381(13)\_F8-6'. + +**Figure 8-6 – Queuing process** + +## 8.4 MPLS-TP-specific GFP-F processes + +### 8.4.1 MPLS-TP-specific GFP-F source processes + +![Figure 8-7: MPLS-TP-specific GFP-F source process diagram. Two parallel input arrows enter boxes 'Map MPLS-TP unicast data' and 'Map SCC data'. Both boxes lead to 'Frame count' boxes. The 'Map SCC data' path also leads to an addition box '+'. Both 'Frame count' boxes lead to 'Generate pFCS' boxes, which are also influenced by 'FCSEnable = true'. Both 'Generate pFCS' boxes lead to a 'Generate PTI/UPI interleave' box, which is also influenced by 'SCCType'. The final output arrow is labeled 'G.8121-Y.1381(13)_F8-7'.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +Figure 8-7: MPLS-TP-specific GFP-F source process diagram. Two parallel input arrows enter boxes 'Map MPLS-TP unicast data' and 'Map SCC data'. Both boxes lead to 'Frame count' boxes. The 'Map SCC data' path also leads to an addition box '+'. Both 'Frame count' boxes lead to 'Generate pFCS' boxes, which are also influenced by 'FCSEnable = true'. Both 'Generate pFCS' boxes lead to a 'Generate PTI/UPI interleave' box, which is also influenced by 'SCCType'. The final output arrow is labeled 'G.8121-Y.1381(13)\_F8-7'. + +**Figure 8-7 – MPLS-TP-specific GFP-F source process** + +Figure 8-7 shows the MPLS-TP-specific GFP-F source processes. These processes are performed on a packet-per-packet basis. + +**Mapping of MPLS-TP data:** The MPLS-TP packet is inserted into the client payload information field of the generic framing procedure (GFP) frame as defined in clause 7.6 of [ITU-T G.7041]. One MPLS-TP packet results in one GFP frame. + +**Mapping of SCC data:** The signalling communication channel (SCC) frame is inserted into the client payload information field of the GFP frame as defined in clause 7 of [ITU-T G.7041]. One SCC packet results in one GFP frame. + +**Frame count:** It counts the number of frames (n\_FramesOK) and of octets (n\_OctetsOK) that passes through. + +**pFCS generation:** See clause 8.5.4.1.1 of [ITU-T G.806]. GFP FCS is always enabled (FCSEnable=true). + +**Generate PTI and UPI, interleave:** The payload type identifier (PTI) field of the GFP type header is set fixed to "000". The user payload identifier (UPI) field of the GFP type header is set to: + +- the MPLS UPI (as defined in Table 6-3 of [ITU-T G.7041]), for frames coming from the Map MPLS-TP data process; +- the SCC UPI according to SCC type for frames coming from the Map SCC data process. + +The frames are then interleaved to form a single stream. + +NOTE – GFP client management frames are not defined for MPLS-TP over GFP-F mapping. + +### 8.4.2 MPLS-TP-specific GFP-F sink processes + +![Figure 8-8: MPLS-TP-specific GFP-F sink process flowchart. The diagram shows a vertical stack of processing blocks. At the bottom, an input arrow points to 'Check PTI/UPI deinterleave'. This block has two output arrows: 'dUPM' and 'LastInvalidUPI'. Above it is 'Check length', which receives an arrow from the block below and has an arrow pointing to a '+' symbol. To the left of 'Check length' is 'FCSDiscard = true'. Above 'Check length' is 'Check pFCS', which also receives an arrow from the block below and has an arrow pointing to the same '+' symbol. To the left of 'Check pFCS' is 'FCSDiscard = true'. Above 'Check pFCS' is 'Frame count', which receives an arrow from the block below and has an arrow pointing to another '+' symbol. Above 'Frame count' is 'Map MPLS-TP unicast data' (left) and 'Demap SCC data' (right). Both receive arrows from the 'Frame count' block and have arrows pointing upwards. The '+' symbols are connected to output labels: 'n_FramesOK' and 'n_OctetsOK' for the top '+' symbol, and 'n_FDis_Frametoolong' for the bottom '+' symbol. A small label 'G.8121-Y.1381(16)_F8-8' is at the bottom right.](d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg) + +Figure 8-8: MPLS-TP-specific GFP-F sink process flowchart. The diagram shows a vertical stack of processing blocks. At the bottom, an input arrow points to 'Check PTI/UPI deinterleave'. This block has two output arrows: 'dUPM' and 'LastInvalidUPI'. Above it is 'Check length', which receives an arrow from the block below and has an arrow pointing to a '+' symbol. To the left of 'Check length' is 'FCSDiscard = true'. Above 'Check length' is 'Check pFCS', which also receives an arrow from the block below and has an arrow pointing to the same '+' symbol. To the left of 'Check pFCS' is 'FCSDiscard = true'. Above 'Check pFCS' is 'Frame count', which receives an arrow from the block below and has an arrow pointing to another '+' symbol. Above 'Frame count' is 'Map MPLS-TP unicast data' (left) and 'Demap SCC data' (right). Both receive arrows from the 'Frame count' block and have arrows pointing upwards. The '+' symbols are connected to output labels: 'n\_FramesOK' and 'n\_OctetsOK' for the top '+' symbol, and 'n\_FDis\_Frametoolong' for the bottom '+' symbol. A small label 'G.8121-Y.1381(16)\_F8-8' is at the bottom right. + +**Figure 8-8 – MPLS-TP-specific GFP-F sink process** + +Figure 8-8 shows the MPLS-TP-specific GFP-F sink processes. These processes are performed on a packet-per-packet basis. + +**Check PTI and UPI, deinterleave:** GFP frames with an accepted PTI (AcPTI, see clause 8.5.1.1 of [ITU-T G.806]) of "000" are client data frames. All GFP frames with an accepted PTI (AcPTI, see clause 8.5.1.1 of [ITU-T G.806]) value other than "000" shall be discarded. + +The UPI of client data frames is checked to generate dUPM as follows: + +- a "valid-UPI frame" is a frame with a UPI that equals either the MPLS UPI (as defined in Table 6-3 of [ITU-T G.7041]) or the SCC UPI according to SCCTYPE. All other frames are "invalid-UPI frames". +- dUPM is raised as soon as one "invalid-UPI frame" is received. +- dUPM is cleared if no "invalid-UPI frames" have been received for the last Tclear seconds. + +Tclear is for further study. If dUPM is active, the latest received invalid UPI is available at LastInvalidUPI. If dUPM is not active, LastInvalidUPI is "n/a". + +The UPI of client data frames is further used to deinterleave the frames: + +- "valid-UPI frames" with UPI equalling the MPLS UPI (as defined in Table 6-3 of [ITU-T G.7041]) are sent towards the "Demap MPLS-TP data" process. +- "valid-UPI frames" with UPI equalling the SCC UPI according to SCCTYPE (as defined in Table 6-3 of [ITU-T G.7041]) are sent towards the "Demap SCC data" process. +- "invalid-UPI frames" are discarded. + +**GFP-F frame length:** It checks whether the length of the GFP-F frame is allowed. Frames longer than GFP\_Length bytes are dropped and counted (n\_FramesTooLong). + +NOTE – GFP\_Length is for further study. + +**pFCS supervision:** See clause 8.5.4.1.2 of [ITU-T G.806]. The discarding of errored frames is always enabled (FCSdiscard=true). If the accepted payload frame check sequence indication. + +(PFI) is 0, the frame is dropped and counted (n\_FDis\_PFI). + +**Frame count:** It counts the number of frames (n\_FramesOK) and of octets (n\_OctetsOK) that pass through. + +**Demapping of SCC data:** The SCC packet is extracted from the client payload information field of the GFP frame as defined in clause 7 of [ITU-T G.704]. One GFP frame results in one SCC frame. + +**Demapping of unicast MPLS-TP data:** The MPLS-TP packet is extracted from the client payload information field of the GFP frame as defined in clause 7.6 of [ITU-T G.704]. One GFP frame results in one MPLS-TP packet. + +## 8.5 Control word (CW) processes + +This function performs the control word (CW) processing as described in [IETF RFC 4448]. The CW is known as the common interworking indicators (CII) in [ITU-T Y.1415]. + +### 8.5.1 CW insertion process + +![Diagram of the CW insertion process. A central box labeled 'CW insertion' has two input arrows from the top labeled 'D' and 'PHB'. It has two output arrows on the left labeled 'CWEnable' and 'SQUse'. It has two output arrows from the bottom labeled 'D' and 'PHB'. Below the box is the text 'G.8121-Y.1381(13)_F8-9'.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +G.8121-Y.1381(13)\_F8-9 + +Diagram of the CW insertion process. A central box labeled 'CW insertion' has two input arrows from the top labeled 'D' and 'PHB'. It has two output arrows on the left labeled 'CWEnable' and 'SQUse'. It has two output arrows from the bottom labeled 'D' and 'PHB'. Below the box is the text 'G.8121-Y.1381(13)\_F8-9'. + +**Figure 8-9 – CW insertion process** + +Figure 8-9 shows CW insertion process. This function should generate and insert the CW as described in [IETF RFC 4448] if the indication CWEnable is true. Otherwise, no insertion should be performed. If the indication SQUse is false, the sequence number field should be set at all zeroes. + +### 8.5.2 CW extraction process + +![Diagram of the CW extraction process. A central box labeled 'CW extraction' has two input arrows from the bottom labeled 'D' and 'PHB'. It has two output arrows on the left labeled 'CWEnable' and 'SQUse'. It has two output arrows from the top labeled 'D' and 'PHB'. Below the box is the text 'G.8121-Y.1381(13)_F8-10'.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +G.8121-Y.1381(13)\_F8-10 + +Diagram of the CW extraction process. A central box labeled 'CW extraction' has two input arrows from the bottom labeled 'D' and 'PHB'. It has two output arrows on the left labeled 'CWEnable' and 'SQUse'. It has two output arrows from the top labeled 'D' and 'PHB'. Below the box is the text 'G.8121-Y.1381(13)\_F8-10'. + +**Figure 8-10 – CW extraction process** + +Figure 8-10 shows CW extraction process. This function should process and remove the CW as described in [IETF RFC 4448], if the indication CWEnable is true. In this case, if the indication SQUse is true, the sequence number field should be processed and out-of-sequence packets dropped (no reordering is performed by this process). + +## 8.6 OAM related processes used by server adaptation functions + +### 8.6.1 Selector process + +![Figure 8-11: Selector process symbol diagram. A box labeled 'Selector' contains two sub-processes: 'Normal' and 'LCK'. The 'Normal' sub-process has inputs D, iPHB, and oPHB. The 'LCK' sub-process also has inputs D, iPHB, and oPHB. The 'Selector' box has an output MI_Admin_state. The overall output of the Selector process is D, iPHB, and oPHB.](fa01531ea2c45beeb4036005da3037a4_img.jpg) + +G.8121-Y.1381(13)\_F8-11 + +Figure 8-11: Selector process symbol diagram. A box labeled 'Selector' contains two sub-processes: 'Normal' and 'LCK'. The 'Normal' sub-process has inputs D, iPHB, and oPHB. The 'LCK' sub-process also has inputs D, iPHB, and oPHB. The 'Selector' box has an output MI\_Admin\_state. The overall output of the Selector process is D, iPHB, and oPHB. + +**Figure 8-11 – Selector process** + +Figure 8-11 shows the Selector process symbol. The Selector process selects the valid signal from the input of the normal MT\_CI signal or the MT\_CI LCK signal (as generated by the LCK generation process in clause 8.6.3). The normal signal is blocked if MI\_Admin\_State is LOCKED. The behaviour is illustrated in Figure 8-12. + +![Figure 8-12: Selector behaviour flowchart. The flowchart starts with a 'Selector' process block. It branches into two main paths: 'Normal' and 'Locked'. The 'Normal' path includes a 'Normal' process block, which leads to a decision block 'State=Locked?'. If 'Y' (Yes), it goes to the 'Locked' path. If 'N' (No), it goes to an output block 'D(D), iPHB(iPHB), oPHB(oPHB)'. The 'Locked' path includes a 'Locked' process block, which leads to a decision block 'State=Normal?'. If 'Y' (Yes), it goes to the output block. If 'N' (No), it goes to the 'Normal' path. Both paths also include input blocks for 'Normal_D(D), Normal_iPHB(iPHB), Normal_oPHB(oPHB)' and 'LCK.D(D), Lock_iPHB(iPHB), Lock_oPHB(oPHB)'.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +G.8121-Y.1381(16)\_F8-12 + +Figure 8-12: Selector behaviour flowchart. The flowchart starts with a 'Selector' process block. It branches into two main paths: 'Normal' and 'Locked'. The 'Normal' path includes a 'Normal' process block, which leads to a decision block 'State=Locked?'. If 'Y' (Yes), it goes to the 'Locked' path. If 'N' (No), it goes to an output block 'D(D), iPHB(iPHB), oPHB(oPHB)'. The 'Locked' path includes a 'Locked' process block, which leads to a decision block 'State=Normal?'. If 'Y' (Yes), it goes to the output block. If 'N' (No), it goes to the 'Normal' path. Both paths also include input blocks for 'Normal\_D(D), Normal\_iPHB(iPHB), Normal\_oPHB(oPHB)' and 'LCK.D(D), Lock\_iPHB(iPHB), Lock\_oPHB(oPHB)'. + +**Figure 8-12 – Selector behaviour** + +### 8.6.2 AIS insert process + +![Diagram of the AIS insert process. A central block labeled 'AIS insert' has an input 'aAIS' on the left. On the right, four parameters are input: 'MI_GAL_Enable', 'MI_AIS_Period', 'MI_AIS_CoS', and 'MI_AIS_OAM_Tool'. At the top, three outputs are shown: 'D', 'iPHB', and 'oPHB'. At the bottom, three more outputs are shown: 'D', 'iPHB', and 'oPHB'. A reference code 'G.8121-Y.1381(13)_F8-13' is at the bottom right.](5d3455c6c2a37cb3aff761fedeb8644e_img.jpg) + +G.8121-Y.1381(13)\_F8-13 + +Diagram of the AIS insert process. A central block labeled 'AIS insert' has an input 'aAIS' on the left. On the right, four parameters are input: 'MI\_GAL\_Enable', 'MI\_AIS\_Period', 'MI\_AIS\_CoS', and 'MI\_AIS\_OAM\_Tool'. At the top, three outputs are shown: 'D', 'iPHB', and 'oPHB'. At the bottom, three more outputs are shown: 'D', 'iPHB', and 'oPHB'. A reference code 'G.8121-Y.1381(13)\_F8-13' is at the bottom right. + +**Figure 8-13 – AIS insert process** + +Figure 8-13 shows the AIS insert process symbol. 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. + +The period between consecutive AIS traffic units is determined by the MI\_AIS\_Period parameter. The format of the AIS traffic units is defined by the MI\_AIS\_OAM\_Tool parameter. The generated AIS traffic units are G-ACH encapsulated as described in clause 8.1 which includes GAL or not depending on MI\_GAL\_Enable. + +The value of the MT\_CI\_iPHB and MT\_CI\_oPHB signals associated with the generated AIS traffic units is the PHB with the lowest drop precedence within the CoS defined by the MI\_AIS\_CoS input parameter. As described in [IETF RFC 6371], AIS packets are transmitted with the "minimum loss probability PHB". + +### 8.6.3 LCK generation process + +![Diagram of the LCK generation process. A central block labeled 'LCK generate' has four parameters input from the right: 'MI_GAL_Enable', 'MI_LCK_Period', 'MI_LCK_CoS', and 'MI_LCK_OAM_Tool'. At the top, three outputs are shown: 'D', 'iPHB', and 'oPHB'. A reference code 'G.8121-Y.1381(13)_F8-14' is at the bottom right.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +G.8121-Y.1381(13)\_F8-14 + +Diagram of the LCK generation process. A central block labeled 'LCK generate' has four parameters input from the right: 'MI\_GAL\_Enable', 'MI\_LCK\_Period', 'MI\_LCK\_CoS', and 'MI\_LCK\_OAM\_Tool'. At the top, three outputs are shown: 'D', 'iPHB', and 'oPHB'. A reference code 'G.8121-Y.1381(13)\_F8-14' is at the bottom right. + +**Figure 8-14 – LCK generation process** + +Figure 8-14 shows the LCK3 generation process symbol. The LCK generation process generates MT\_CI traffic units where the MT\_CI\_D signal contains the LCK signal. Figure 8-15 defines the behaviour of the LCK generation process. + +--- + +3 IETF uses the term LKR for this function. + +![Flowchart of LCK generation behaviour. The process starts with 'LCK generation' (oval), followed by 'Set(0, Timer)' (rectangle), 'LCK Generate' (oval), 'Timer' (parallelogram), 'OAM=LCK(MI_LCK_OAM_Tool, MI_GAL_Enable, MI_LCK_Period)' (rectangle), 'PHB=PHB(MI_LCK_CoS)' (rectangle), 'D(OAM, iPHB(PHB), oPHB(PHB))' (parallelogram), and 'Set(MI_LCK_Period, Timer)' (rectangle). A feedback loop connects the final step back to the 'LCK Generate' step. The diagram is labeled G.8121-Y.1381(16)_F8-15.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +``` + +graph TD + A([LCK generation]) --> B[Set(0, Timer)] + B --> C([LCK Generate]) + C --> D[/Timer/] + D --> E[OAM=LCK(MI_LCK_OAM_Tool, MI_GAL_Enable, MI_LCK_Period)] + E --> F[PHB=PHB(MI_LCK_CoS)] + F --> G[/D(OAM, iPHB(PHB), oPHB(PHB))/] + G --> H[Set(MI_LCK_Period, Timer)] + H --> C + I[G.8121-Y.1381(16)_F8-15] + +``` + +Flowchart of LCK generation behaviour. The process starts with 'LCK generation' (oval), followed by 'Set(0, Timer)' (rectangle), 'LCK Generate' (oval), 'Timer' (parallelogram), 'OAM=LCK(MI\_LCK\_OAM\_Tool, MI\_GAL\_Enable, MI\_LCK\_Period)' (rectangle), 'PHB=PHB(MI\_LCK\_CoS)' (rectangle), 'D(OAM, iPHB(PHB), oPHB(PHB))' (parallelogram), and 'Set(MI\_LCK\_Period, Timer)' (rectangle). A feedback loop connects the final step back to the 'LCK Generate' step. The diagram is labeled G.8121-Y.1381(16)\_F8-15. + +**Figure 8-15 – LCK generation behaviour** + +The LCK generation process continuously generates LCK traffic units. The period between consecutive LCK traffic units is determined by the MI\_LCK\_Period parameter. + +The LCK(LCK\_OAM\_Tool, GAL\_Enable, Period) function generates a LCK traffic unit, whose format is defined by the LCK\_OAM\_Tool parameter, that encodes the period information defined by the value of the Period parameter. The generated traffic unit is G-ACh encapsulated, as described in clause 8.1, with or without the GAL depending on the GAL\_Enable parameter. + +The value of the MT\_CI\_iPHB and MT\_CI\_oPHB signal associated with the generated LCK traffic units is the PHB with the lowest drop precedence within the CoS defined by the MI\_LCK\_CoS input parameter. The PHB(MI\_LCK\_CoS) function generates such PHB information. As described in [IETF RFC 6371], LCK packets are transmitted with the "minimum loss probability PHB". + +## 8.7 OAM related processes used by adaptation functions + +### 8.7.1 MCC and SCC mapping and demapping + +As defined in [ITU-T G.7712], an embedded communication channel (ECC) provides a logical operations channel between network elements (NEs) that can be utilized by various applications. A maintenance communication channel (MCC) is an ECC dedicated for management plane communications. A signalling communication channel (SCC) is an ECC dedicated for control plane communications. + +The MCC mapping and demapping processes are provided to support the MT to MCC adaptation function for accessing the MCC. The SCC mapping and demapping processes are provided to support the MT to SCC adaptation function for accessing to the SCC. The mapping and demapping processes for MCC is very similar to that of the SCC. In the following description given in this clause and in clause 8.7.2, the term ECC will be used, which applies to both MCC and SCC. + +#### 8.7.1.1 ECC mapping + +The ECC mapping process is associated with the MT/MCC\_A\_So and MT/SCC\_A\_So functions, which are described in clauses 10.2.2.1 and 10.2.1.1 respectively. + +This process shall map the incoming ECC packet into G-ACh encapsulated ECC traffic unit (i.e., a MT\_AI\_D traffic units carrying an ECC packet). + +The ECC traffic units generated by this process are encapsulated into the G\_ACh, as defined in [IETF RFC 5718], using or not the GAL depending on the MI\_GAL\_Enable configuration parameters. The value of the MT\_AI\_PHB associated with the generated ECC traffic units is defined by the MI\_ECC\_CoS input parameter. + +#### 8.7.1.2 ECC demapping + +The ECC Demapping process is associated with the MT/MCC\_A\_Sk and MT/SCC\_A\_Sk functions, which are described in clauses 10.2.2.2 and 10.2.1.2 respectively. + +This process shall extract the ECC packet from the G-ACh encapsulated ECC traffic unit (i.e., MT\_AI\_D traffic units carrying ECC packets). + +The criteria for selecting ECC traffic units are based on the values of the fields within the MT\_AI\_D signal: + +- GAL is included to the MT\_AI\_D if GAL usage is enabled via MI\_GAL\_Enable. +- The Channel type of G-ACh indicates a MCC packet (in MT/MCC\_A\_Sk) or a SCC packet (in MT/SCC\_A\_Sk), as defined in [IETF RFC 5718]. + +### 8.7.2 APS insert and extract processes + +Figure 8-16 shows a protocol-neutral abstract model of the different processes inside the MEPs and the MIPs that are involved in the automatic protection switching (APS)4 function. + +![Figure 8-16: Overview of the processes involved with APS function. The diagram shows three main components: MEP, MIP, and MEP. The left MEP contains 'APS insert' and 'APS extract' blocks. The 'APS insert' block receives 'CI_D' and 'CI_APS' signals and sends data to a 'Proactive OAM insert' block. The 'APS extract' block receives data from a 'Proactive OAM extract' block and sends 'CI_D' and 'CI_APS' signals. The MIP contains 'On-demand OAM extract' blocks. The right MEP contains 'Proactive OAM extract', 'APS extract', 'Proactive OAM insert', and 'APS insert' blocks. The 'Proactive OAM extract' block receives data from the MIP and sends it to the 'APS extract' block. The 'Proactive OAM insert' block receives data from the 'APS insert' block and sends it to the MIP. The 'APS extract' block in the right MEP receives 'CI_D' and 'CI_APS' signals and sends data to the 'Proactive OAM extract' block. The 'APS insert' block in the right MEP receives data from the 'Proactive OAM insert' block and sends 'CI_D' and 'CI_APS' signals. The diagram is labeled G.8121-Y.1381(13)_F8-16.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +G.8121-Y.1381(13)\_F8-16 + +Figure 8-16: Overview of the processes involved with APS function. The diagram shows three main components: MEP, MIP, and MEP. The left MEP contains 'APS insert' and 'APS extract' blocks. The 'APS insert' block receives 'CI\_D' and 'CI\_APS' signals and sends data to a 'Proactive OAM insert' block. The 'APS extract' block receives data from a 'Proactive OAM extract' block and sends 'CI\_D' and 'CI\_APS' signals. The MIP contains 'On-demand OAM extract' blocks. The right MEP contains 'Proactive OAM extract', 'APS extract', 'Proactive OAM insert', and 'APS insert' blocks. The 'Proactive OAM extract' block receives data from the MIP and sends it to the 'APS extract' block. The 'Proactive OAM insert' block receives data from the 'APS insert' block and sends it to the MIP. The 'APS extract' block in the right MEP receives 'CI\_D' and 'CI\_APS' signals and sends data to the 'Proactive OAM extract' block. The 'APS insert' block in the right MEP receives data from the 'Proactive OAM insert' block and sends 'CI\_D' and 'CI\_APS' signals. The diagram is labeled G.8121-Y.1381(13)\_F8-16. + +**Figure 8-16 – Overview of the processes involved with APS function** + +APS insert and extract processes are located in MT/MT\_Adaptation function. The CI\_APS signal contains the APS specific information as defined in clause 8.2 of [ITU-T G.8131]. APS traffic units are inserted into and extracted from the stream of MT\_CI\_D traffic units. + +4 [ITU-T G.8131] conventionally uses the term APC for this function. + +#### 8.7.2.1 APS insert process + +![Figure 8-17: APS insert process block diagram. A central 'APS insert' block has three input arrows from the top labeled 'APS', 'PHB D', and 'D'. It has three input arrows from the right labeled 'MI_APS_CoS', 'MI_GAL_Enable', and 'MI_APS_OAM_Tool'. It has two output arrows from the bottom labeled 'PHB D' and 'D'. A reference label 'G.8121-Y.1381(16)_F8-17' is at the bottom right.](399a5af4f606059626c92c92279d54b7_img.jpg) + +Figure 8-17: APS insert process block diagram. A central 'APS insert' block has three input arrows from the top labeled 'APS', 'PHB D', and 'D'. It has three input arrows from the right labeled 'MI\_APS\_CoS', 'MI\_GAL\_Enable', and 'MI\_APS\_OAM\_Tool'. It has two output arrows from the bottom labeled 'PHB D' and 'D'. A reference label 'G.8121-Y.1381(16)\_F8-17' is at the bottom right. + +Figure 8-17 – APS insert process + +Figure 8-17 shows the APS insert process and Figure 8-18 illustrates the behaviour. 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 MT\_CI\_APS signal contains the APS specific information as defined in [ITU-T G.8131]. + +![Figure 8-18: APS insert behaviour flowchart. The flow starts with 'APS insert' leading to 'Waiting'. From 'Waiting', it branches into two parallel paths. The left path shows 'D(D), PHB(PHB)' being processed. The right path shows 'APS(APS)' being processed through 'OAM= APS(MI_APS_OAM_Tool, MI_GAL_Enable, APS)', then 'PHB=PHB(MI_APS_CoS)', and finally 'D(OAM), PHB(PHB)'. Both paths merge back into the main flow. A reference label 'G.8121-Y.1381(16)_F8-18' is at the bottom right.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Figure 8-18: APS insert behaviour flowchart. The flow starts with 'APS insert' leading to 'Waiting'. From 'Waiting', it branches into two parallel paths. The left path shows 'D(D), PHB(PHB)' being processed. The right path shows 'APS(APS)' being processed through 'OAM= APS(MI\_APS\_OAM\_Tool, MI\_GAL\_Enable, APS)', then 'PHB=PHB(MI\_APS\_CoS)', and finally 'D(OAM), PHB(PHB)'. Both paths merge back into the main flow. A reference label 'G.8121-Y.1381(16)\_F8-18' is at the bottom right. + +Figure 8-18 – APS insert behaviour + +The APS(APS\_OAM\_Tool, GAL\_Enable, APS) function generates an APS traffic unit, whose format is defined by the APS\_OAM\_Tool parameter, that encodes the APS information defined by the value of the APS parameter. The generated traffic unit is G-ACH encapsulated, as described in clause 8.1, with or without the GAL depending on the GAL\_Enable parameter. + +The value of the MT\_AI\_PHB signals associated with the generated APS traffic units are the PHB with the lowest drop precedence within the CoS defined by the MI\_APS\_CoS input parameter. The PHB(MI\_APS\_CoS) function generates such PHB information. + +#### 8.7.2.2 APS extract process + +![Figure 8-19: APS extract process block diagram](85e2327652d513a7fee8fdbf97ad06f1_img.jpg) + +A block diagram of the APS extract process. A central blue rectangular block is labeled "APS extract". It has two input arrows pointing into its bottom edge, both labeled "PHB D". It has two output arrows pointing out of its top edge, labeled "APS" and "PHB D". It also has two input arrows pointing into its right edge, labeled "MI\_GAL\_Enable" and "MI\_APS\_OAM\_Tool". A small text label "G.8121-Y.1381(16)\_F8-19" is located to the right of the block. + +Figure 8-19: APS extract process block diagram + +**Figure 8-19 – APS extract process** + +The APS extract process, shown in Figure 8-19, extracts MT\_AI\_APS signals from the incoming stream of MT\_AI traffic units. + +The MT\_AI\_APS is the APS specific information as described in [ITU-T G.8131] contained in the received traffic unit. All other traffic units will be transparently forwarded. + +The criteria for filtering are based on the values of the fields within the MT\_AI\_D signal: + +- S bit (1) and GAL included to the MT\_AI\_D if GAL usage is enabled via MI\_GAL\_Enable. +- OAM type that is defined in channel type of G-ACh indicates APS + +This is illustrated in Figure 8-20. The function APS(D) extracts the APS specific information from the received traffic unit. + +![Figure 8-20: APS extract behaviour flowchart](446100c084b94817a19c319fa776b412_img.jpg) + +A flowchart illustrating the APS extract behaviour. It starts with a rounded rectangle labeled "APS extract". An arrow points down to a rounded rectangle labeled "Waiting". From "Waiting", an arrow points down to a chevron-shaped block labeled "D(D), PHB(PHB)". From this chevron, an arrow points down to a decision diamond labeled "GAL and CT(D) = APS". If the answer is "N" (No), an arrow points right to a chevron-shaped block labeled "D(D), PHB(PHB)". If the answer is "Y" (Yes), an arrow points down to a chevron-shaped block labeled "APS(APS(D))". Both chevron-shaped blocks have arrows pointing to a common vertical line on the right, which then loops back up to the "Waiting" block. A small text label "G.8121-Y.1381(16)\_F8-20" is located to the right of the bottom chevron. + +Figure 8-20: APS extract behaviour flowchart + +**Figure 8-20 – APS extract behaviour** + +### 8.7.3 CSF insert and extract processes + +Figure 8-21 shows the different processes inside MEPs and MIPs that are involved in the CSF5 protocol. + +![Figure 8-21: Overview of processes involved with CSF protocol. The diagram shows three main components: a left MEP, a central MIP, and a right MEP. The left MEP has an input MT_CI and three configuration inputs: MI_CSF_OAM_Tool, MI_CSF_OAM_Period, and MI_CSF_OAM_CoS. It contains a 'Data' block with '...' and a 'CSF insertion' block. An arrow labeled MT_CI points from the left MEP to the central MIP. The MIP contains a dashed box labeled 'On-demand OAM extraction'. An arrow labeled MT_CI points from the MIP to the right MEP. The right MEP contains a 'Data' block with '...' and a 'CSF extraction' block. An arrow labeled MT_CI points from the right MEP to an output. Another arrow labeled MI_CSF_OAM_Tool points from the right MEP to a 'CSF' output. The diagram is labeled G.8121-Y.1381(18)_F8-21.](1142ba0197b158bb198186fe8baccc32_img.jpg) + +Figure 8-21: Overview of processes involved with CSF protocol. The diagram shows three main components: a left MEP, a central MIP, and a right MEP. The left MEP has an input MT\_CI and three configuration inputs: MI\_CSF\_OAM\_Tool, MI\_CSF\_OAM\_Period, and MI\_CSF\_OAM\_CoS. It contains a 'Data' block with '...' and a 'CSF insertion' block. An arrow labeled MT\_CI points from the left MEP to the central MIP. The MIP contains a dashed box labeled 'On-demand OAM extraction'. An arrow labeled MT\_CI points from the MIP to the right MEP. The right MEP contains a 'Data' block with '...' and a 'CSF extraction' block. An arrow labeled MT\_CI points from the right MEP to an output. Another arrow labeled MI\_CSF\_OAM\_Tool points from the right MEP to a 'CSF' output. The diagram is labeled G.8121-Y.1381(18)\_F8-21. + +Figure 8-21 – Overview of processes involved with CSF protocol + +The MPLS-TP client signal fail function (MT-CSF) is used by a MEP to propagate to a peer MEP the detection of a failure or defect event in a MPLS-TP client signal when the client itself does not support appropriate fault or defect detection or propagation mechanisms, such as MT-CC or MT-AIS. The MT-CSF messages propagate in the direction from MPLS-TP MEP function detecting the failure or defect event to the MPLS-TP sink-adaptation function associated with the peer MEP. + +MT-CSF generation is located at the MT/Client\_A\_So to insert CSF traffic unit and ProActive OAM insertion is located at the MT\_TT. + +#### 8.7.3.1 CSF Insert process + +![Figure 8-22: CSF insert process. The diagram shows a central block labeled 'CSF insert'. Inputs from the left are aCSF-RDI, aCSF-FDI, and aCSF-LOS. Inputs from the right are MI_GAL_Enable, MI_CSF_OAM_Tool, MI_CSF_OAM_Period, and MI_CSF_OAM_CoS. Outputs at the top are D and PHB. Outputs at the bottom are D and PHB. The diagram is labeled G.8121-Y.1381(18)_F8-22.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +Figure 8-22: CSF insert process. The diagram shows a central block labeled 'CSF insert'. Inputs from the left are aCSF-RDI, aCSF-FDI, and aCSF-LOS. Inputs from the right are MI\_GAL\_Enable, MI\_CSF\_OAM\_Tool, MI\_CSF\_OAM\_Period, and MI\_CSF\_OAM\_CoS. Outputs at the top are D and PHB. Outputs at the bottom are D and PHB. The diagram is labeled G.8121-Y.1381(18)\_F8-22. + +Figure 8-22 – CSF insert process + +The CSF insert process is located at the MT/Client\_A\_So as a part of CSF generation. Figure 8-22 shows the CSF insert process symbol. + +The behaviour is specified in [ITU-T G.8121.1] and [ITU-T G.8121.2] depending on the MI\_CSF\_OAM\_Tool parameter. The format of the CSF traffic units is specified in [ITU-T G.8113.1] and [ITU-T G.8113.2] depending on the MI\_CSF\_OAM\_Tool parameter. + +5 IETF uses the term "Client Failure Indication" for this function in [IETF RFC 6371]. + +#### 8.7.3.2 CSF extract process + +![Diagram of the CSF extract process. A central box labeled 'CSF extract' has three output arrows pointing upwards labeled 'CSF', 'D', and 'PHB'. It has two input arrows pointing from the right labeled 'MI_GAL_Enable' and 'MI_CSF_OAM_Tool'. It has two input arrows pointing from below labeled 'D' and 'PHB'. Below the diagram is the text 'G.8121-Y.1381(18)_F8-23'.](ed48e24e36ea0501953177401c900f86_img.jpg) + +G.8121-Y.1381(18)\_F8-23 + +Diagram of the CSF extract process. A central box labeled 'CSF extract' has three output arrows pointing upwards labeled 'CSF', 'D', and 'PHB'. It has two input arrows pointing from the right labeled 'MI\_GAL\_Enable' and 'MI\_CSF\_OAM\_Tool'. It has two input arrows pointing from below labeled 'D' and 'PHB'. Below the diagram is the text 'G.8121-Y.1381(18)\_F8-23'. + +**Figure 8-23 – CSF extract process** + +The CSF extract process is located at MT/Client\_A\_sk and extracts MT-CSF from MI\_AI\_D. Figure 8-23 shows the CSF extract process symbol. + +AI\_CSF signal is extracted from the incoming stream of MT\_AI traffic units. Figure 8-23 shows the CSF extract process symbol. The behaviour and criteria for filtering are specified in [ITU-T G.8121.1] and [ITU-T G.8121.2] depending on the MI\_CSF\_OAM\_Tool parameter. + +## 8.8 Proactive and on-demand OAM related processes + +As described in [IETF RFC 6371], OAM functions are categorized as proactive and on-demand and these OAM functionalities provide the different interfaces. + +OAM functions can be also categorised as single-ended and dual-ended. Single-ended functions are those in which an initiating MEP sends OAM PDUs to a target MEP, which processes it and sends a response OAM PDU back to the initiating MEP. The results of the function are available only on the initiating MEP. Dual-ended functions are those in which an initiating MEP sends OAM PDUs to a target MEP, which processes it and does not send a response. The results of the function are available only on the target MEP. Dual-ended functions are typically deployed in pairs, one in each direction. + +Figure 8-24 shows an OAM protocol-neutral abstract model of the different processes inside MEPs and MIPs that are involved in performing single-ended proactive or on-demand OAM functions. In the case of dual-ended functions, the model is equivalent to the top half of the diagram only, and the results are reported by the OAM sink control process on the target MEP. + +![Figure 8-24: Overview of the processes involved with proactive or on-demand OAM functions. The diagram shows three vertical columns representing different network elements: Initiating MEP, MIP, and Target MEP. Each column contains a stack of processes. The Initiating MEP column includes G-ACh/GAL insertion, OAM PDU generation, Proactive or on-demand OAM sink control, Proactive or on-demand OAM source control, OAM PDU reception, and G-ACh/GAL extraction. The MIP column includes G-ACh/GAL extraction, OAM PDU reception, On-demand OAM sink control, On-demand OAM source control, OAM PDU generation, and G-ACh/GAL insertion. The Target MEP column includes G-ACh/GAL extraction, OAM PDU reception, Proactive or on-demand OAM sink control, Proactive or on-demand OAM source control, OAM PDU generation, and G-ACh/GAL insertion. Arrows indicate the flow of MT_CI, MI_, RI_, and Results signals between these processes. A note indicates that MT_CI signals are internal to the MEPs. A label 'Results (dual-ended case)' is present in the Target MEP column.](e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg) + +G.8121-Y.1381(18)\_F8-24 + +Figure 8-24: Overview of the processes involved with proactive or on-demand OAM functions. The diagram shows three vertical columns representing different network elements: Initiating MEP, MIP, and Target MEP. Each column contains a stack of processes. The Initiating MEP column includes G-ACh/GAL insertion, OAM PDU generation, Proactive or on-demand OAM sink control, Proactive or on-demand OAM source control, OAM PDU reception, and G-ACh/GAL extraction. The MIP column includes G-ACh/GAL extraction, OAM PDU reception, On-demand OAM sink control, On-demand OAM source control, OAM PDU generation, and G-ACh/GAL insertion. The Target MEP column includes G-ACh/GAL extraction, OAM PDU reception, Proactive or on-demand OAM sink control, Proactive or on-demand OAM source control, OAM PDU generation, and G-ACh/GAL insertion. Arrows indicate the flow of MT\_CI, MI\_, RI\_, and Results signals between these processes. A note indicates that MT\_CI signals are internal to the MEPs. A label 'Results (dual-ended case)' is present in the Target MEP column. + +**Figure 8-24 – Overview of the processes involved with proactive or on-demand OAM functions** + +NOTE – The MT\_CI signals at the input of the G-ACh insertion process and at the output of the G-ACh extraction process are not input/output signals of the Initiation/Target MEPs but signals which are internal to these MEPs. + +The processes shown in Figure 8-24 are described further below, with the exception of the G-ACh insertion and extraction processes which are described in clause 8.1. + +The relevant management information (MI\_) and remote information (RI\_) used by these processes depend on the OAM function to be performed and is defined in the following clauses. + +The detailed specification of all the OAM processes, including further process decomposition and the interface between them, is OAM protocol-specific and therefore outside the scope of this Recommendation. + +### OAM control processes + +The four OAM control processes (i.e., the Proactive OAM source control process, Proactive OAM sink control process, On-demand OAM source control process and On-demand OAM sink control process) perform all the OAM control procedures (e.g., they maintain the necessary state machine) that are required for a specific OAM protocol. The proactive OAM source and sink control processes operate within the MT\_TT\_So and MT\_TT\_Sk atomic functions respectively. + +Similarly, the On-demand OAM source and sink control processes operate within the MTDe\_TT\_So or MTDi\_TT\_So and the MTDe\_TT\_Sk or MTDi\_TT\_Sk atomic functions respectively. + +All four processes consist of a number of OAM protocol-specific control sub-processes, each relating to a different OAM function. The details of these sub-processes are outside the scope of this Recommendation + +The OAM source control process within the initiating MEP (Proactive or On-demand as appropriate) requests the OAM PDU generation process to generate OAM Request PDUs towards the target MEP on the basis of the local state machine and the relevant management information (MI\_). This supports both single-ended and dual-ended OAM transactions. + +In the case of a dual-ended OAM transaction, the appropriate OAM sink control process within the target MEP (Proactive or On-demand) or within the target MIP (On-demand only) reports the dual-ended OAM results on the basis of the OAM Request PDUs received by the OAM PDU Reception process. + +In the case of single-ended OAM transactions, the following actions are taken: + +- The OAM sink control process within the target MEP or MIP provides the local OAM source control process the relevant remote information (RI\_) to generate a reply to the OAM Request PDU received by the local PDU reception process. +- The OAM source control process within the target MEP or MIP requests the OAM PDU generation process to generate OAM Reply PDUs towards the initiating MEP based on the information it receives from the local OAM sink control process via the relevant remote information (RI\_). +- The OAM sink control process within the initiating MEP reports the unidirectional or bidirectional OAM results based on the OAM Reply PDUs received by the local OAM PDU reception process + +### **OAM PDU generation process** + +The OAM PDU generation process builds, when instructed by its control process, the required OAM PDU and passes it to the G-ACh insertion process, defined in clause 8.1, for insertion within the MPLS-TP characteristic information (CI) traffic flow. It also passes the following information elements that are required by the G-ACh insertion process: the PHB associated to the OAM packet (on the basis of the CoS instruction received by the control process); the ACH channel type that identifies the OAM PDU and the TTL value which it is either the TTL distance to a MIP (for OAM PDUs targeted to a MIP and properly requested by the control process) or the default value as configured via MI\_TTLValue. + +The OAM PDU generation process consists of a number of OAM protocol-specific PDU generation sub-processes (one for each PDU type) and a sub-process that multiplexes all the PDUs generated by these OAM protocol-specific PDU generation sub-processes into a single stream of OAM PDUs, which is sent to the G-ACh insertion process along with the appropriate ACH channel type. The details of these sub-processes are outside the scope of this Recommendation. + +### **OAM PDU reception process** + +The OAM PDU reception process receives an OAM PDU, together with the ACH channel type value identifying the PDU type, the associated PHB, and the label stack (LStack) data, from the G-ACh process and passes the relevant information to its control process. + +The OAM PDU reception process consists of a number of OAM protocol-specific PDU reception sub-processes (one for each PDU type) and a sub-process that demultiplexes OAM PDUs received from the G-ACh extraction process towards these OAM protocol-specific PDU reception sub-processes based on the ACH channel type. The details of these sub-processes are outside the scope of this Recommendation. + +### **8.8.1 Proactive continuity check or connectivity verification (CC/CV)** + +As described in [IETF RFC 6371], both continuity check (CC) and connectivity verification (CV) OAM functions are based on the proactive generation of OAM packets by the source MEP that are processed by the peer sink MEP(s). + +The source MEP generates CC/CV OAM packets if it is enabled via management information (MI). As described in [IETF RFC 6371], the CC/CV OAM packets are generated at a regular rate which is configured by the operator via the MI\_CC\_Period. These packets are also transmitted using PHB which is configured via MI\_CC\_CoS (and that is typically the "minimum loss probability PHB"). + +In order to perform connectivity verification (CV), the generated CC/CV packets also include a globally unique source MEP identifier: the transmitted value is configured via protocol-specific management information on the source MEP while the expected value is configured via different protocol-specific management information on the sink MEP. + +The sink MEP always processes received CC/CV OAM packets and detects the following CC/CV defects, as defined in clause 6.1: + +- dLOC +- dUNC +- dMMG +- dUNM +- dUNP + +CC/CV OAM packets pass transparently through MIPs as described in [IETF RFC 6371]. + +The EMF can retrieve from the sink MEP the latest CC/CV OAM packet which caused a defect condition via the MI\_Get\_SvdCC command: the CC/CV OAM packet is returned to the EMF via the MI\_SvdCC. + +### **8.8.2 Remote defect indication (RDI)** + +As described in [IETF RFC 6371], in case of co-routed and associated bidirectional transport paths, RDI is associated with proactive CC/CV, and the RDI indicator can be piggy-backed onto the CC/CV packet. + +RDI information is carried in the CC/CV packets based upon the RI\_CC/CV\_RDI input. It is extracted in the CC/CV reception process. + +In case of unidirectional transport paths, the RDI related OAM process is for further study. + +### **8.8.3 On-demand connectivity verification (CV)** + +As described in [IETF RFC 6371], on-demand CV OAM functions are based on the on-demand generation of OAM packets by the source MEP, that are processed and responded to by the peer sink MIP(s) or MEP(s). + +The source MEP generates on-demand CV OAM packets when requested via protocol-specific MI signals. The results of the on-demand CV operation are returned by the source MEP using additional protocol-specific management information. + +### **8.8.4 Proactive packet loss measurement (LMp)** + +As described in [IETF RFC 6371], proactive loss measurement (LM) is performed by periodically sending LM OAM packets from the initiating MEP to the target MEP and by receiving LM OAM packets from the target MEP on a co-routed bidirectional connection. Each MEP performs measurements of its transmitted and received user data packets (TxFCI and RxFCI). These measurements are then correlated in real time with the target MEP in the ME to derive the impact of packet loss on a number of performance metrics for the ME in the MEG. + +As described in [IETF RFC 6374], there are two types of LM mechanism. One is to directly measure dataplane packet loss by counting packets transmitted and received. This is called LM or direct LM. The other is to measure the approximate dataplane loss level by counting synthetic packets transmitted and received. This is called synthetic loss measurement (SLM) or inferred loss measurement. + +For single-ended measurement: + +- The initiating MEP generates proactive LM OAM Request packets if MI\_LMp\_Enable is true. These packets are generated at the rate configured via the MI\_LMp\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_LMp\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted user data packets (TxFCI) is inserted within the LM OAM packet by the OAM PDU generation process. +- The target MEP replies to the LM OAM packets if it is enabled. The local value of the received user data packets (RxFCI) at the time the proactive LM OAM Request packet has been received is passed by OAM PDU reception process to the proactive OAM sink control process, then to the proactive OAM source control process (via RI\_OAM\_Info) and inserted by the OAM PDU generation process within the transmitted proactive LM OAM Reply: the actual behaviour on how this information is passed is OAM protocol specific and therefore outside the scope of this Recommendation. The OAM PDU generation process also inserts the local value of the transmitted user data packets (TxFCI) in the reverse direction within the transmitted proactive LM OAM Reply. +- The initiating MEP processes the received proactive LM OAM Reply packet, together with the local value of the received used data packets (RxFCI) in the reverse direction at the time this OAM packet is received, as passed by the OAM PDU reception process, and generates LM results. + +Depending on the LMp OAM tool that it is used, the LM results can be either calculated by the proactive OAM sink control process or by the proactive OAM source control process. In the latter case, the proactive OAM sink control process passes the required information in the received LM OAM Reply to the proactive OAM source control process via the RI\_LMRp and receives the LM results back via the RI\_LMp\_Result. In both cases, the proactive OAM sink control process passes the LM results to the relevant performance monitoring processes within the MT\_TT\_Sk atomic function for reporting to the EMF that is described in [b-ITU-T G.8151]. + +NOTE – The behaviour is the same when synthetic proactive (SLp) LM is used. In this Recommendation, the term SLp is used to address the management and remote information (MI and RI) for synthetic loss measurement. + +For dual-ended measurement: + +- The initiating MEP generates proactive LM OAM Request packets if MI\_1LMp\_Enable is true. These packets are generated at the rate configured via the MI\_LMp\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_LMp\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted user data packets (TxFCI) is inserted within the LM OAM packet by the OAM PDU generation process. +- The target MEP receives LM OAM packets if it is enabled to do so via management information. The local value of the received user data packets (RxFCI) at the time the proactive LM OAM Request packet has been received is passed by OAM PDU reception process to the proactive OAM sink control process and generates LM results. + +NOTE – The behaviour is the same when dual-ended synthetic proactive (1SLp) LM is used. In this Recommendation, the term 1SLp is used to address the management and remote information (MI and RI) for synthetic loss measurement. + +Proactive LM OAM packets pass transparently through MIPs as described in [IETF RFC 6371]. + +### 8.8.5 On-demand packet loss measurement (LMo) + +As described in [IETF RFC 6371], on-demand LM is performed by the command that sends LM OAM packets from the initiating MEP to the target MEP and by receiving LM OAM packets from the target MEP on a co-routed bidirectional connection. The initiating MEP performs measurements of its transmitted and received user data packets (TxFCI and RxFCI). These measurements are then correlated in real time with values received from the target MEP in the ME to derive the impact of packet loss for the ME in the MEG. + +As described in [IETF RFC 6374], there are two types of LM mechanism. One is to directly measure data-plane packet loss by counting packets transmitted and received. This is called LM or direct LM. The other is to measure the approximate dataplane loss level by counting synthetic packets transmitted and received. This is called synthetic loss measurement (SLM) or inferred loss measurement. + +For single-ended measurement: + +- The initiating MEP generates on-demand LM OAM Request packets when enabled via management information. These packets are generated with the PHB configured via management information that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted user data packets (TxFCI) is inserted within the LM OAM packet by the OAM PDU generation process. +- The target MEP replies to the LM OAM packets if enabled via management information. The local value of the received user data packets (RxFCI) at the time the on-demand LM OAM Request packet has been received is passed by OAM PDU reception process to the on-demand OAM sink control process, then to the on-demand OAM source control process (via RI\_OAM\_Info) and inserted by the OAM PDU generation process within the transmitted on-demand LM OAM Reply: the actual behaviour on how this information is passed is OAM protocol specific and therefore outside the scope of this Recommendation. The OAM PDU generation process also inserts the local value of the transmitted user data packets (TxFCI) in the reverse direction within the transmitted on-demand LM OAM Reply. +- The initiating MEP processes the received on-demand LM OAM Reply packet, together with the local value of the received used data packets (RxFCI) in the reverse direction at the time this OAM packet is received, as passed by the OAM PDU reception process, and generates LM results. +- Depending on the LMo OAM tool that it is used, the LM results can be either calculated by the on-demand OAM sink control process or by the on-demand OAM source control process. In both cases, the LM results are reported to EMF by the MTDe\_TT\_So using the MI\_LMo\_Result(N\_TF,N\_LF,F\_TF,F\_LF) signal, containing the near-end transmitted packets, near-end lost packets, far-end transmitted packets and far-end lost packets. + +NOTE – The behaviour is same when synthetic on-demand (SLo) LM is used. In this Recommendation, the term SLo is used to address the management and remote information (MI and RI) for synthetic loss measurement. + +For dual-ended measurement: + +- The initiating MEP generates on-demand LM OAM Request packets when enabled via management information. These packets are generated at the rate configured via the MI\_LMo\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_LMo\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted user data packets (TxFCI) is inserted within the LM OAM packet by the OAM PDU generation process. + +- The target MEP receives LM OAM packets when enabled via management information. The local value of the received user data packets (RxFCI) at the time the on-demand LM OAM Request packet has been received is passed by OAM PDU reception process to the on-demand OAM sink control process and generates LM results. + +On demand LM OAM packets pass transparently through MIPs as described in [IETF RFC 6371]. + +### 8.8.6 Proactive packet delay measurement (DMp) + +As described in [IETF RFC 6371], proactive delay measurement (DM) is performed by periodically sending DM OAM packets from the initiating MEP to the target MEP and by receiving DM OAM packets from the target MEP on a co-routed bidirectional connection. Each MEP records its transmitted and received timestamps. The timestamps from the initiating and target MEPs are then correlated to derive a number of performance metrics relating to delay for the ME in the MEG. + +For single-ended measurement: + +- The initiating MEP generates proactive DM OAM Request packets if MI\_DMp\_Enable is true. These packets are generated at the rate configured via the MI\_DMp\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_DMp\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted timestamp (TxTimeStampf) is inserted within the DM OAM packet by the OAM PDU generation process. +- The target MEP replies to the DM OAM packets if enabled by management information. The local value of the received timestamp (RxTimeStampl) at the time the proactive DM OAM Request packet has been received is passed by OAM PDU reception process to the proactive OAM sink control process, then to the proactive OAM source control process (via RI\_OAM\_Info) and inserted by the OAM PDU generation process within the transmitted proactive DM OAM Reply: the actual behaviour on how this information is passed is OAM protocol specific and therefore outside the scope of this Recommendation. The OAM PDU generation process also inserts the local value of the transmitted timestamp (TxTimeStampf) in the reverse direction within the transmitted proactive DM OAM Reply. +- The initiating MEP processes the received proactive DM OAM Reply packet, together with the local value of the received timestamp (RxTimeStampl) in the reverse direction at the time this OAM packet is received, as passed by the OAM PDU reception process, and generates DM results. +- Depending on the DMp OAM tool that it is used, the DM results can be either calculated by the proactive OAM sink control process or by the proactive OAM source control process. In the latter case, the proactive OAM sink control process passes the required information in the received DM OAM Reply to the proactive OAM source control process via the RI\_DMRp and receives the DM results back via the RI\_DMp\_Result. In both cases, the proactive OAM sink control process passes the DM results to the relevant performance monitoring processes within the MT\_TT\_Sk atomic function for reporting to the EMF. + +For dual-ended measurement: + +- The initiating MEP generates proactive DM OAM Request packets if MI\_1DMp\_Enable is true. These packets are generated at the rate configured via the MI\_DMp\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_DMp\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted timestamp (TxTimeStampl) is inserted within the DM OAM packet by the OAM PDU generation process. + +- The target MEP receives DM OAM packets if enabled by management information. The local value of the received timestamp (RxTimeStamp1) at the time the proactive DM OAM Request packet has been received is passed by OAM PDU reception process to the proactive OAM sink control process which generates DM results. + +Proactive DM OAM packets pass transparently through MIPs as described in [IETF RFC 6371]. + +### 8.8.7 On-demand packet delay measurement (DMo) + +As described in [IETF RFC 6371], on-demand DM is performed by the command that sends DM OAM packets from the initiating MEP to the target MEP and by receiving DM OAM packets from the target MEP on a co-routed bidirectional connection. Each MEP records its transmitted and received timestamps. The timestamps from the initiating and target MEPs are then correlated to derive a number of performance metrics relating to delay for the ME in the MEG. + +For single-ended measurement: + +- The initiating MEP generates on-demand DM OAM Request packets if MI\_DMo\_Enable is true. These packets are generated with the PHB configured via MI\_DMo\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted timestamp (TxTimeStampf) is inserted within the DM OAM packet by the OAM PDU generation process. +- The target MEP replies to the PM OAM packets if the MI\_PMo\_Enable is true. The local value of the received timestamp (RxTimeStamp1) at the time the on-demand PM OAM Request packet has been received is passed by OAM PDU reception process to the on-demand OAM sink control process, then to the on-demand OAM source control process (via RI\_OAM\_Info) and inserted by the OAM PDU generation process within the transmitted on-demand DM OAM Reply: the actual behaviour on how this information is passed is OAM protocol specific and therefore outside the scope of this Recommendation. +- The initiating MEP processes the received on-demand DM OAM Reply packet, together with the local value of the received timestamp (RxTimeStamp1) in the reverse direction at the time this OAM packet is received, as passed by the OAM PDU reception process, and generates DM results. +- Depending on the DMo OAM tool that it is used, the DM results can be either calculated by the on-demand OAM sink control process or by the on-demand OAM source control process. In both cases, the DM results are reported to EMF by the MTDe\_TT\_So using the MI\_DMo\_Result(B\_FD[],F\_FD[],N\_FD[]) signal, containing the count of measurements, and arrays of round-trip frame delay, far-end frame delay and near-end frame delay measurements. + +For dual-ended measurement: + +- The initiating MEP generates on-demand DM OAM Request packets if MI\_DMo\_Enable is true. These packets are generated at the rate configured via the MI\_DMo\_Period and, as described in [IETF RFC 6371], with the PHB configured via MI\_DMo\_CoS that yields the lowest drop precedence within the measured PHB scheduling class, in order to maximize reliability of measurement within the traffic class. The local value of transmitted Timestamp (TxTimeStampf) is inserted within the DM OAM packet by the OAM PDU Generation process. +- The target MEP receives DM OAM packets if the MI\_DMo\_Enable is true. The local value of the received timestamp (RxTimeStamp1) at the time the on-demand DM OAM Request packet has been received is passed by OAM PDU reception process to the on-demand OAM sink control process and generates DM results. + +On-demand DM OAM packets pass transparently through MIPs as described in [IETF RFC 6371]. + +### 8.8.8 Throughput test + +For single-ended throughput test: + +- For further study. + +For dual-ended throughput test: + +- As described in [IETF RFC 6371], out of service on-demand throughput estimation can be performed by sending OAM test packets at an increasing rate (up to the theoretical maximum), computing the percentage of OAM test packets received and reporting the rate at which OAM test packets begin to drop. In general, this rate is dependent on the OAM test packet size. +- The source MEP starts generating test packets when requested via protocol-specific management information and continues generating these packets at the configured period until requested to stop; at this time the number of sent packets is reported via protocol-specific management information. +- The sink MEP, when enabled via protocol-specific management information, starts processing the received OAM test packets until the test is terminated; at this time, the calculated test results are reported. + +### 8.8.9 Route tracing (RT) + +For further study. + +### 8.8.10 LCK/AIS reception + +As described in [IETF RFC 6371], when a MEP detects a signal fail condition or is locked, it may transmit AIS or lock messages at the client layer, respectively. These are transmitted by the AIS insert process (see clause 8.6.2) or the LCK generation process (see clause 8.6.3), and are received by the LCK/AIS reception sub-process in the Proactive OAM sink control process. The receipt of AIS or lock message triggers the dAIS or dLCK defects respectively, as described in clause 6.1. + +### 8.8.11 Lock instruct processes + +As described in [IETF RFC 6371], when a MEP is administratively locked, it puts the local MPLS-TP trail into a locked state and, if enabled by the MI\_Lock\_Instruct\_Enable, it also starts transmitting a lock instruct message to its peer MEP. The locking of the trail at the local MEP is performed by the Selector process defined in clause 8.6.1; the transmission of lock instruct (LKI) messages is performed by the On-demand OAM process. + +On receiving a LKI message, the peer MEP must also lock the path. + +The lock instruct message is received by the On-demand OAM process and the request is signalled to the EMF via MI\_Admin\_State\_Request. The EMF should then combine this remote request with any local request from the user, and set MI\_Admin\_State accordingly in the corresponding MT/MT\_A\_So and MT/MT\_A\_Sk processes. + +Figure 8-25 illustrates how setting MI\_Admin\_State on the local MEP both locks the local Selector processes (the local selector in the MT/MT\_A\_Sk is not shown), and triggers the generation of LKI messages to the remote MEP that cause the two remote Selector processes to also be locked. + +![Figure 8-25: Overview of the processes involved with lock instruct. This diagram shows the interaction between a Local MEP and a Remote MEP. On the Local MEP side, an 'MT_Admin_State' input goes to a 'Selector' block which contains a 'Label process'. The output of the 'Selector' is 'MT/MT_A_So', which is also an input to a 'MTDe/MT_A_So' block. Below this is a 'MTDe/TT_So' block. An 'MI_Lock_Instruct_Enable' input goes to an 'On-demand OAM So' block. The output of 'On-demand OAM So' goes to an 'OAM insertion' block. The output of 'OAM insertion' is 'MT_CI_D/iPHB/oPHB'. On the Remote MEP side, 'MT/MT_A_Sk' and 'MT/MT_A_So' inputs go to a 'Selector' block containing a 'Label process'. The output of the 'Selector' is 'MT/MT_A_So', which is also an input to a 'MTDe/MT_A_So' block. Below this is a 'MTDe/TT_Sk' block. An 'On-demand OAM Sk' block receives input from 'MTDe/TT_Sk' and sends output to an 'OAM extraction' block. The output of 'OAM extraction' is 'MT_CI_D/iPHB/oPHB'. Both 'MT_CI_D/iPHB/oPHB' outputs from Local and Remote MEPs converge at an 'EMF' block. The 'EMF' block sends an 'MI_Admin_State_Request' to the 'MTDe/TT_So' block on the Local MEP side. The 'EMF' block also receives an 'MI_Admin_State' input from the 'MTDe/MT_A_So' block on the Remote MEP side. A dashed vertical line separates the Local MEP and Remote MEP sections. A reference label 'G.8121-Y.1381(18)_F8-25' is in the bottom right corner.](0a42e05c07941450f34e4f7117725834_img.jpg) + +Figure 8-25: Overview of the processes involved with lock instruct. This diagram shows the interaction between a Local MEP and a Remote MEP. On the Local MEP side, an 'MT\_Admin\_State' input goes to a 'Selector' block which contains a 'Label process'. The output of the 'Selector' is 'MT/MT\_A\_So', which is also an input to a 'MTDe/MT\_A\_So' block. Below this is a 'MTDe/TT\_So' block. An 'MI\_Lock\_Instruct\_Enable' input goes to an 'On-demand OAM So' block. The output of 'On-demand OAM So' goes to an 'OAM insertion' block. The output of 'OAM insertion' is 'MT\_CI\_D/iPHB/oPHB'. On the Remote MEP side, 'MT/MT\_A\_Sk' and 'MT/MT\_A\_So' inputs go to a 'Selector' block containing a 'Label process'. The output of the 'Selector' is 'MT/MT\_A\_So', which is also an input to a 'MTDe/MT\_A\_So' block. Below this is a 'MTDe/TT\_Sk' block. An 'On-demand OAM Sk' block receives input from 'MTDe/TT\_Sk' and sends output to an 'OAM extraction' block. The output of 'OAM extraction' is 'MT\_CI\_D/iPHB/oPHB'. Both 'MT\_CI\_D/iPHB/oPHB' outputs from Local and Remote MEPs converge at an 'EMF' block. The 'EMF' block sends an 'MI\_Admin\_State\_Request' to the 'MTDe/TT\_So' block on the Local MEP side. The 'EMF' block also receives an 'MI\_Admin\_State' input from the 'MTDe/MT\_A\_So' block on the Remote MEP side. A dashed vertical line separates the Local MEP and Remote MEP sections. A reference label 'G.8121-Y.1381(18)\_F8-25' is in the bottom right corner. + +**Figure 8-25 – Overview of the processes involved with lock instruct** + +NOTE 1 – It is important that the remote MEP is locked as soon as possible after receiving the first lock instruct message; therefore the EMF must handle the MI\_Admin\_State\_Request with high priority to ensure it is reflected in MI\_Admin\_State as quickly as possible. + +NOTE 2 – The EMF must combine any local lock request from the user with the received MI\_Admin\_State\_Request, when setting MI\_Admin\_State in the MT/MT\_A\_So and MT/MT\_A\_Sk functions. However, when setting MI\_Admin\_State in the MTDe\_TT\_So function, the EMF must only do so based on a local request from the user. This is to prevent a deadlock situation where receipt of a lock instruct message causes transmission of a lock instruct message in the opposite direction. + +## 8.9 Dataplane loopback processes + +As described in [IETF RFC 6435], the dataplane loopback process controls looping back of all traffic (i.e., both data and OAM packets), under management control. An overview is shown in Figure 8-26. + +![Figure 8-26: Overview of the processes involved with dataplane loopback. This diagram shows two main blocks: 'Dataplane loopback sink' on the left and 'Dataplane loopback source' on the right. The 'Dataplane loopback sink' has three input arrows at the bottom labeled 'D', 'iPHB', and 'oPHB', with an additional label 'MT_CI' below them. It has three output arrows at the top labeled 'D', 'iPHB', and 'oPHB'. A 'MI_DP_Loopback_Enable' input arrow points to the 'Dataplane loopback sink' from the left. A horizontal arrow labeled 'RI_CI(D, iPHB, oPHB)' points from the 'Dataplane loopback sink' to the 'Dataplane loopback source'. The 'Dataplane loopback source' has three output arrows at the bottom labeled 'D', 'iPHB', and 'oPHB', with an additional label 'MT_CI' below them. It has three input arrows at the top labeled 'D', 'iPHB', and 'oPHB'. A 'MI_DP_Loopback_Enable' input arrow points to the 'Dataplane loopback source' from the right. A reference label 'G.8121-Y.1381(18)_F8-26' is in the bottom right corner.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +Figure 8-26: Overview of the processes involved with dataplane loopback. This diagram shows two main blocks: 'Dataplane loopback sink' on the left and 'Dataplane loopback source' on the right. The 'Dataplane loopback sink' has three input arrows at the bottom labeled 'D', 'iPHB', and 'oPHB', with an additional label 'MT\_CI' below them. It has three output arrows at the top labeled 'D', 'iPHB', and 'oPHB'. A 'MI\_DP\_Loopback\_Enable' input arrow points to the 'Dataplane loopback sink' from the left. A horizontal arrow labeled 'RI\_CI(D, iPHB, oPHB)' points from the 'Dataplane loopback sink' to the 'Dataplane loopback source'. The 'Dataplane loopback source' has three output arrows at the bottom labeled 'D', 'iPHB', and 'oPHB', with an additional label 'MT\_CI' below them. It has three input arrows at the top labeled 'D', 'iPHB', and 'oPHB'. A 'MI\_DP\_Loopback\_Enable' input arrow points to the 'Dataplane loopback source' from the right. A reference label 'G.8121-Y.1381(18)\_F8-26' is in the bottom right corner. + +**Figure 8-26 – Overview of the processes involved with dataplane loopback** + +NOTE – The dataplane loopback processes are included in the MEP diagnostic trail termination function (MTDe\_TT, see clause 9.4.1.1) and the MIP diagnostic trail termination function (MTDi\_TT, see clause 9.4.2.1). Dataplane loopback may also be enabled on a transport path at a point where there is no MEP or MIP; the location of the dataplane loopback processes in this case is for further study. + +### 8.9.1 Dataplane loopback sink processes + +The dataplane loopback sink process is illustrated in Figure 8-27. + +![Flowchart of Dataplane loopback sink process. The process starts with 'Dataplane loopback sink' leading to 'Normal' state. In 'Normal' state, data passes through 'D(D), iPHB(iPHB), oPHB(oPHB)' and then to 'Loopback' state. 'MI_DP_Loopback_Enable' is checked. In 'Loopback' state, data passes through 'D(D), iPHB(iPHB), oPHB(oPHB)' and then to 'RI_CI(D, iPHB, oPHB)'. '!MI_DP_Loopback_Enable' is checked. A feedback loop connects the output of 'RI_CI' back to the input of 'Normal' state. Source: G.8121-Y.1381(18)_F8-27.](c1df61cc3717e878a48e530218403403_img.jpg) + +``` + +graph TD + Start([Dataplane loopback sink]) --> Normal([Normal]) + Normal --> D1{{D(D), iPHB(iPHB), oPHB(oPHB)}} + D1 --> D2{{D(D), iPHB(iPHB), oPHB(oPHB)}} + D2 --> Loopback([Loopback]) + Normal --> MI_DP_Enable{{MI_DP_Loopback_Enable}} + Loopback --> D3{{D(D), iPHB(iPHB), oPHB(oPHB)}} + D3 --> RI_CI{{RI_CI(D, iPHB, oPHB)}} + Loopback --> Not_MI_DP_Enable{{!MI_DP_Loopback_Enable}} + RI_CI --> Normal + +``` + +G.8121-Y.1381(18)\_F8-27 + +Flowchart of Dataplane loopback sink process. The process starts with 'Dataplane loopback sink' leading to 'Normal' state. In 'Normal' state, data passes through 'D(D), iPHB(iPHB), oPHB(oPHB)' and then to 'Loopback' state. 'MI\_DP\_Loopback\_Enable' is checked. In 'Loopback' state, data passes through 'D(D), iPHB(iPHB), oPHB(oPHB)' and then to 'RI\_CI(D, iPHB, oPHB)'. '!MI\_DP\_Loopback\_Enable' is checked. A feedback loop connects the output of 'RI\_CI' back to the input of 'Normal' state. Source: G.8121-Y.1381(18)\_F8-27. + +**Figure 8-27 – Dataplane loopback sink process** + +In Normal state, data traffic passes through the process unmodified; in Loopback state, it is intercepted and sent to the dataplane loopback source process via RI\_CI. + +### 8.9.2 Dataplane loopback source processes + +The dataplane loopback source process is illustrated in Figure 8-28. + +![Flowchart of the Dataplane loopback source process. The process starts with a 'Dataplane loopback source' oval pointing to a 'Normal' state oval. From 'Normal', three paths emerge: 1) Data flow D(D, iPHB(iPHB), oPHB(oPHB)) which loops back to itself; 2) RI_CI(D, iPHB, oPHB); 3) MI_DP_Loopback_Enable. All three paths lead to a 'Loopback' state oval. From 'Loopback', three paths emerge: 1) Data flow D(D, iPHB(iPHB), oPHB(oPHB)); 2) RI_CI(D, iPHB, oPHB) which loops back to itself; 3) !MI_DP_Loopback_Enable. A large blue line on the right side of the diagram connects the 'Normal' state back to the 'Loopback' state.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + DLS((Dataplane loopback source)) --> Normal((Normal)) + Normal --> D1{{D(D, iPHB(iPHB), oPHB(oPHB))}} + Normal --> RI1{{RI_CI(D, iPHB, oPHB)}} + Normal --> MI1{{MI_DP_Loopback_Enable}} + D1 --> D2{{D(D, iPHB(iPHB), oPHB(oPHB))}} + D2 --> Loopback((Loopback)) + RI1 --> Loopback + MI1 --> Loopback + Loopback --> D3{{D(D, iPHB(iPHB), oPHB(oPHB))}} + Loopback --> RI2{{RI_CI(D, iPHB, oPHB)}} + Loopback --> MI2{{!MI_DP_Loopback_Enable}} + RI2 --> RI3{{RI_CI(D, iPHB, oPHB)}} + RI3 --> Loopback + MI2 --> Loopback + +``` + +G.8121-Y.1381(18)\_F8-28 + +Flowchart of the Dataplane loopback source process. The process starts with a 'Dataplane loopback source' oval pointing to a 'Normal' state oval. From 'Normal', three paths emerge: 1) Data flow D(D, iPHB(iPHB), oPHB(oPHB)) which loops back to itself; 2) RI\_CI(D, iPHB, oPHB); 3) MI\_DP\_Loopback\_Enable. All three paths lead to a 'Loopback' state oval. From 'Loopback', three paths emerge: 1) Data flow D(D, iPHB(iPHB), oPHB(oPHB)); 2) RI\_CI(D, iPHB, oPHB) which loops back to itself; 3) !MI\_DP\_Loopback\_Enable. A large blue line on the right side of the diagram connects the 'Normal' state back to the 'Loopback' state. + +**Figure 8-28 – Dataplane loopback source process** + +In Normal state, data traffic passes through the process unmodified; in Loopback state, data traffic is dropped, and data received via RI\_CI from the dataplane loopback sink process is transmitted instead. + +# 9 MPLS-TP layer functions + +Figure 9-1 illustrates the MPLS-TP layer network and server and client layer adaptation functions. The information crossing the MPLS-TP connection point (MT\_CP) is referred to as the MPLS-TP characteristic information (MT\_CI) and consists of: + +- MT\_CI\_D (containing the 'S' bit, TTL and MPLS payload) +- MT\_CI\_iPHB +- MT\_CI\_oPHB +- MT\_CI\_SSF +- MT\_CI\_APS +- MT\_CI\_LStack + +These are described in clause 6.1.2 of [ITU-T G.8110.1] except for MT\_CI\_LStack, which contains a copy of the complete label stack received from the network. + +The information crossing the MPLS-TP access point (MT\_AP) is referred to as the MPLS-TP adapted information (MT\_AI) and consists of: + +- MT\_AI\_D (containing the 'S' bit and MPLS payload) +- MT\_AI\_PHB +- MT\_AI\_TSF +- MT\_AI\_TSD +- MT\_AI\_AIS + +## – MT\_AI\_LStack + +These are described in clause 6.1.1 of [ITU-T G.8110.1] except for MT\_AI\_LStack, which is as above, and MT\_AI\_AIS, which indicates an alarm indication signal (AIS) condition. + +The information crossing the MPLS-TP diagnostic access points (MTDe\_AP and MTDi\_AP) is referred to as MPLS-TP diagnostic adapted information (MTDe\_AI and MTDi\_AI respectively). These both consist of the same signals, with the same definitions, as MT\_CI. + +NOTE – MTDe\_AI and MTDi\_AI are not the same as MT\_AI. In particular, MTDe\_AI\_D and MTDi\_AI\_D contain a TTL field (whereas MT\_AI\_D does not); and MTDe\_AI and MTDi\_AI contain separate iPHB and oPHB signals (whereas MT\_AI contains a single PHB signal). + +The MPLS-TP layer network provides embedded hierarchy via the label stacking mechanism. This is represented in the model by MPLS-TP tunnel sublayers, which contain MT\_TT and MT/MT\_A functions. Figure 9-1 shows a generic example for the connection of the MPLS-TP tunnel functions. It is not required to connect them via a MT\_C function; they can be directly inserted without a connection function. It is noted that this Recommendation only defines Ethernet for the client of MPLS-TP as MT/ETH adaptation function. + +This mechanism (MPLS-TP tunnel sublayers) is also used when sublayer (tandem connection) monitoring is required. + +![Figure 9-1 – MPLS-TP atomic functions. This diagram illustrates the hierarchical structure of MPLS-TP atomic functions. At the top, there are three horizontal paths: ETH_FP (containing MT/ETH), SCC_FP (containing MT/SCC), and MCC_FP (containing MT/MCC). These paths connect to a central MT/AP block, which in turn connects to an MT/CP block. Below these, there are four vertical stacks of MT/MT and MT blocks, each associated with an MTDi/MT and MTDe/MT pair. These pairs connect to a central MT block. At the bottom, there are six vertical stacks of MT/MT blocks, each associated with an adaptation function: Pq/MT (Pq_AP), Pq-x/MT (Pq-X_AP), Sn/MT (Sn_AP), Sn-x/MT (Sn-X_AP), ODUkP/MT (ODUKP_AP), and ETH/MT (ETH_AP). On the right side, there are two vertical stacks of MT/MT blocks, each associated with an MT/MTp or MT/MSRP block, which then connect to an MT/MTp or MT/MSRP block, followed by an MT block, an MT/CP block, and finally an MTDe/MT block. The central MT block is connected to all these vertical stacks. The diagram is labeled G.8121-Y.1381(18)_F9-1.](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +Figure 9-1 – MPLS-TP atomic functions. This diagram illustrates the hierarchical structure of MPLS-TP atomic functions. At the top, there are three horizontal paths: ETH\_FP (containing MT/ETH), SCC\_FP (containing MT/SCC), and MCC\_FP (containing MT/MCC). These paths connect to a central MT/AP block, which in turn connects to an MT/CP block. Below these, there are four vertical stacks of MT/MT and MT blocks, each associated with an MTDi/MT and MTDe/MT pair. These pairs connect to a central MT block. At the bottom, there are six vertical stacks of MT/MT blocks, each associated with an adaptation function: Pq/MT (Pq\_AP), Pq-x/MT (Pq-X\_AP), Sn/MT (Sn\_AP), Sn-x/MT (Sn-X\_AP), ODUkP/MT (ODUKP\_AP), and ETH/MT (ETH\_AP). On the right side, there are two vertical stacks of MT/MT blocks, each associated with an MT/MTp or MT/MSRP block, which then connect to an MT/MTp or MT/MSRP block, followed by an MT block, an MT/CP block, and finally an MTDe/MT block. The central MT block is connected to all these vertical stacks. The diagram is labeled G.8121-Y.1381(18)\_F9-1. + +**Figure 9-1 – MPLS-TP atomic functions** + +## 9.1 Connection functions + +### 9.1.1 MPLS-TP connection function (MT\_C) + +MT\_C is the function that assigns MPLS packets at its input ports to MPLS-TP packets at its output ports. + +The MT\_C connection process is a unidirectional function as illustrated in Figure 9-2. The signal formats at the input and the output ports of the function are similar, differing only in the logical sequence of the MPLS-TP packets. As the process does not affect the nature of the characteristic information of the signal, the reference point on either side of the MT\_C function is the same, as illustrated in Figure 9-2. + +Incoming MPLS-TP packets at the MT\_CP are assigned to available outgoing MPLS-TP capacity at the MT\_CP. In addition, the MT\_C function supports the SNC/S protection schemes as defined in [ITU-T G.8131]. The Protection functionality is described in clause 9.1.1.1. + +##### Symbol + +![Diagram of the MT_C symbol. A central oval labeled 'MT' represents the connection function. On the left, a horizontal double-headed arrow labeled 'MT_C_MI' points to the oval. Above the oval, there are two sets of vertical arrows pointing upwards, each labeled 'MT_CI', with an ellipsis between them. Below the oval, there are two sets of vertical arrows pointing downwards, each labeled 'MT_CI', with an ellipsis between them. The text 'G.8121-Y.1381(13)_F9-2' is written below the diagram.](552328a9daaf3bc0069424b500025880_img.jpg) + +G.8121-Y.1381(13)\_F9-2 + +Diagram of the MT\_C symbol. A central oval labeled 'MT' represents the connection function. On the left, a horizontal double-headed arrow labeled 'MT\_C\_MI' points to the oval. Above the oval, there are two sets of vertical arrows pointing upwards, each labeled 'MT\_CI', with an ellipsis between them. Below the oval, there are two sets of vertical arrows pointing downwards, each labeled 'MT\_CI', with an ellipsis between them. The text 'G.8121-Y.1381(13)\_F9-2' is written below the diagram. + +Figure 9-2 – MT\_C symbol + +#### Interfaces + +The interfaces are described in Table 9-1. + +**Table 9-1– MT\_C input and output signals** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Per MT_CP, n × for the function:

  • MT_CI_D
  • MT_CI_iPHB
  • MT_CI_oPHB
  • MT_CI_APS
  • MT_CI_SSF
  • MT_CI_SSD (for SNC/S protection)
  • MT_CI_LStack

Per input and output connection point:
for further study

MT_C_MP:
MT_C_MI_MatrixControl

Per matrix connection:

  • MT_C_MI_ConnectionType
  • MT_C_MI_Return_CP_ID
  • MT_C_MI_ConnectionPortIds

Per protection group:

  • MT_C_MI_PS_WorkingPortId
  • MT_C_MI_PS_ProtectionPortId
  • MT_C_MI_PS_ProtType
  • MT_C_MI_PS_OperType
  • MT_C_MI_PS_HoTime
  • MT_C_MI_PS_WTR
  • MT_C_MI_PS_ExtCMD
  • MT_C_MI_PS_SD_Protection
|

Per MT_CP, m × per function:

  • MT_CI_D
  • MT_CI_iPHB
  • MT_CI_oPHB
  • MT_CI_APS
  • MT_CI_SSF
  • MT_CI_LStack

Per protection group:

  • MT_C_MI_cFOP-PMb
  • MT_C_MI_cFOP-PMc
  • MT_C_MI_cFOP-CM
  • MT_C_MI_cFOP-NR
  • MT_C_MI_cFOP-TO
| + +#### **Processes** + +In the MT\_C function MPLS-TP characteristic information is routed between input (termination) connection points ((T)CPs) and output (T)CPs by means of matrix connections. (T)CPs may be allocated within a protection group. + +NOTE – 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. + +MT-C process diagram is illustrated in Figure 9-3. + +![Figure 9-3 – MT_C process diagram. The diagram shows a 'Routing' block and a 'Protection switching' block. 'MT_C_MI' is an input to the 'Routing' block. The 'Routing' block has multiple output arrows pointing to 'MT_CI_D/LStack' and multiple input arrows from 'MT_CI_D/LStack'. The 'Protection switching' block has multiple output arrows pointing to 'MT_CI_SSF' and 'MT_CI_APS' and multiple input arrows from 'MT_CI_SSF' and 'MT_CI_APS'. A double-headed arrow connects the 'Routing' block and the 'Protection switching' block. The diagram is labeled 'G.8121-Y.1381(16)_F9-3'.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) + +Figure 9-3 – MT\_C process diagram. The diagram shows a 'Routing' block and a 'Protection switching' block. 'MT\_C\_MI' is an input to the 'Routing' block. The 'Routing' block has multiple output arrows pointing to 'MT\_CI\_D/LStack' and multiple input arrows from 'MT\_CI\_D/LStack'. The 'Protection switching' block has multiple output arrows pointing to 'MT\_CI\_SSF' and 'MT\_CI\_APS' and multiple input arrows from 'MT\_CI\_SSF' and 'MT\_CI\_APS'. A double-headed arrow connects the 'Routing' block and the 'Protection switching' block. The diagram is labeled 'G.8121-Y.1381(16)\_F9-3'. + +**Figure 9-3 – MT\_C process diagram** + +##### – *Routing process:* + +This process passes all the traffic units received from a specific input to the corresponding output according to the matrix connection between the specified input and output, and it shall be able to remove an established matrix connection as defined by MI\_MatrixControl. + +Each (matrix) connection in the MT\_C function shall be characterized by the: + +| | | +|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| +| Type of connection (MI_ConnectionType): | Unprotected, protected | +| Traffic direction (MI_Return_CP_ID): | Unidirectional if NULL, otherwise it identifies the CP of the return connection (Note) | +| Input and output connection points (MI_ConnectionPortIDs): | Set of connection point identifiers | +| NOTE – Bidirectional LSPs are supported by associating two unidirectional LSPs in the dataplane, as per [ITU-T G.8110.1]. | | + +##### – *Protection switching process:* + +Protection switching process for SNC/S is defined in clause 9.1.1.1. + +**Performance monitoring:** None. + +**Defects:** None. + +**Consequent actions:** If an output of this function is not connected to one of its inputs, the connection function shall send no traffic units and SSF = false to the output. + +**Defect correlations:** None. + +#### 9.1.1.1 Protection process for SNC/S + +SNC protection with sublayer monitoring based on TCM is supported. For the term TCM, [IETF RFC 6371] uses the term called sub-path maintenance elements (SPMEs). + +Figure 9-4 shows the involved atomic functions in SNC/S. The MT\_TT\_Sk provides the trail signal fail/trail signal degrade (TSF/TSD) protection switching criterion via the MT/MT\_A\_Sk function (SSF/SSD) to the MT\_C function. + +![Figure 9-4: Involved atomic functions in SNC/S. This diagram shows the signal flow and atomic functions for a network element. At the top, two 'MT' (Management Terminal) blocks are connected to a central 'MT_C' (Management Controller) oval via 'MT_CI_D/iPHB/oPHB' interfaces. The 'MT_C' oval is divided into 'Normal', 'Working', and 'Protection' sections. Below the 'Working' section, there are two parallel paths. Each path consists of an 'MT/MT' block, an 'MT' block, and a 'Srv/MT' block. Various interfaces are shown between these blocks and the 'MT_C' oval, including 'MT_CI_SSF/SSD', 'MT_CI_D/iPHB/oPHB', 'MT_AI_TSF/TSD', and 'MT_AI_D/PHB'. The 'Protection' section follows a similar structure but includes 'APS' (Automatic Protection Switching) interfaces. Arrows indicate the direction of signal flow between the components. A reference code 'G.8121-Y.1381(16)_F9-4' is at the bottom right.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +Figure 9-4: Involved atomic functions in SNC/S. This diagram shows the signal flow and atomic functions for a network element. At the top, two 'MT' (Management Terminal) blocks are connected to a central 'MT\_C' (Management Controller) oval via 'MT\_CI\_D/iPHB/oPHB' interfaces. The 'MT\_C' oval is divided into 'Normal', 'Working', and 'Protection' sections. Below the 'Working' section, there are two parallel paths. Each path consists of an 'MT/MT' block, an 'MT' block, and a 'Srv/MT' block. Various interfaces are shown between these blocks and the 'MT\_C' oval, including 'MT\_CI\_SSF/SSD', 'MT\_CI\_D/iPHB/oPHB', 'MT\_AI\_TSF/TSD', and 'MT\_AI\_D/PHB'. The 'Protection' section follows a similar structure but includes 'APS' (Automatic Protection Switching) interfaces. Arrows indicate the direction of signal flow between the components. A reference code 'G.8121-Y.1381(16)\_F9-4' is at the bottom right. + +**Figure 9-4 – Involved atomic functions in SNC/S** + +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 connection point (i.e., working or protection) to the protected (sub)network connection point. + +The signal flows associated with the MT\_ protection process are described with reference to Figure 9-5. The protection process receives control parameters and external switch requests at the management point (MP) reference point. The report of status information at the MP reference point is for further study. + +![Figure 9-5: Protection process. This diagram illustrates the internal structure of the protection process. A central box contains a 'Selector' and a 'Bridge', each with 'W' (Working) and 'P' (Protection) sub-components. The box is labeled 'Protection process' and 'Normal'. External interfaces include 'MT_CI_D/iPHB/oPHB' at the top, 'MT_C_MI_PS' on the left, and 'MT_CI_D/iPHB/oPHB/APS', 'MT_CI_SSF/SSD', and 'MT_CI_D/iPHB/oPHB/APS', 'MT_CI_SSF/SSD' at the bottom. Arrows indicate signal flow into and out of the 'Selector' and 'Bridge' components. A reference code 'G.8121-Y.1381(16)_F9-5' is at the bottom right.](bccc028d0e75bc30c41528056f581545_img.jpg) + +Figure 9-5: Protection process. This diagram illustrates the internal structure of the protection process. A central box contains a 'Selector' and a 'Bridge', each with 'W' (Working) and 'P' (Protection) sub-components. The box is labeled 'Protection process' and 'Normal'. External interfaces include 'MT\_CI\_D/iPHB/oPHB' at the top, 'MT\_C\_MI\_PS' on the left, and 'MT\_CI\_D/iPHB/oPHB/APS', 'MT\_CI\_SSF/SSD', and 'MT\_CI\_D/iPHB/oPHB/APS', 'MT\_CI\_SSF/SSD' at the bottom. Arrows indicate signal flow into and out of the 'Selector' and 'Bridge' components. A reference code 'G.8121-Y.1381(16)\_F9-5' is at the bottom right. + +**Figure 9-5 – Protection process** + +##### *Source direction:* + +For a 1+1 architecture, the CI coming from the normal (protected) MT\_CP is bridged permanently to both the working and protection MT\_CP. + +For a 1:1 architecture, the CI coming from the normal (protected) MT\_CP is switched to either the working or the protection or both MT\_CPs. A switch-over from working to protection MT\_CP 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 MT\_CP is switched to the normal (protected) MT\_CP. A switch-over from working to protection MT\_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 the protection (sub)network connections, for SNC/S protection server signal fail (SSF) and server signal degrade (SSD). + +A hold-off timer is provided in order to allow interworking between nested protection schemes. 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 8.11 of [ITU-T G.8131]. + +Protection switching can also be initiated by external switch commands received via the MP or a request from the far end via the received MT\_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.8131]. + +##### *Switching time:* + +Refer to [ITU-T G.8131]. + +##### *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 timer is defined in clause 8.12 of [ITU-T G.8131]. + +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.8131]: + +- MT\_C\_MI\_PS\_WorkingPortId configures the working port. +- MT\_C\_MI\_PS\_ProtectionPortId configures the protection port. +- MT\_C\_MI\_PS\_ProtType configures the protection type. +- MT\_C\_MI\_PS\_OperType configures to be in revertive mode. +- MT\_C\_MI\_PS\_HoTime configures the hold-off timer. + +- MT\_C\_MI\_PS\_WTR configures the wait-to-restore timer. +- MT\_C\_MI\_PS\_ExtCMD configures the protection group command. +- MT\_C\_MI\_PS\_SD\_Protection configures the ability of a SNC protection switching process to trigger protection switching upon signal degrade (SD). + +##### **Defects:** + +The function detects dFOP-PMb, dFOP-PMc, dFOP-CM, dFOP-NR and dFOP-TO defects in case the APS protocol is used. + +**Consequent actions:** None. + +**Defect correlations:** + +- cFOP-PMb $\leftarrow$ dFOP-PMb and (not CI\_SSF) +- cFOP-PMc $\leftarrow$ dFOP-PMc 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 – In case of cFOP-PMb/PMc/NR/TO, CI\_SSF of the protection transport entity is used. + +### **9.1.2 Connection functions for trail protection (MTp\_C)** + +MTp\_C is the specific function that is used to support trail protection defined in [ITU-T G.8131]. + +The MTp\_C connection process is a unidirectional function as illustrated in Figure 9-6 and the interface is described in Table 9-2. + +![Diagram of MTp_C symbol showing Normal MTp_CI, Working MTp_CI, and Protection MTp_CI interfaces connected to a central MTp_C oval, with an MTp_C_MI interface on the left.](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +The diagram illustrates the MTp\_C symbol as a central oval. On the left, an interface labeled 'MTp\_C\_MI' is connected via a double-headed arrow. Above the oval, 'Normal MTp\_CI' is shown with multiple upward-pointing arrows and a set of downward-pointing arrows, separated by an ellipsis. Below the oval, 'Working MTp\_CI' and 'Protection MTp\_CI' are shown. Each has multiple upward-pointing arrows and a set of downward-pointing arrows, also separated by an ellipsis. A small label 'G.8121-Y.1381(16)\_F9-6' is located at the bottom right of the diagram. + +Diagram of MTp\_C symbol showing Normal MTp\_CI, Working MTp\_CI, and Protection MTp\_CI interfaces connected to a central MTp\_C oval, with an MTp\_C\_MI interface on the left. + +**Figure 9-6 – MTp\_C symbol** + +MPLS-TP packets at the normal MTp\_CP are bridged/selected to/from the working and/or protection MTp\_C by the protection switching process for trail protection. The Protection functionality is described in clause 9.1.2.1. + +**Table 9-2 – MTp\_C input and output signals** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Per normal MTp_CP:
MTp_CI_D
MTp_CI_PHB

Per working MTp_CP:
MTp_CI_D
MTp_CI_PHB
MTp_CI_SSF
MTp_CI_SSD
MTp_CI_AIS
MTp_CI_LStack

Per protection MTp_CP:
MTp_CI_D
MTp_CI_PHB
MTp_CI_APS
MTp_CI_SSF
MTp_CI_SSD
MTp_CI_LStack

Per input and output connection point:
for further study

Per protection group:
MTp_C_MI_PS_WorkingPortId
MTp_C_MI_PS_ProtectionPortId
MTp_C_MI_PS_ProtType
MTp_C_MI_PS_OperType
MTp_C_MI_PS_HoTime
MTp_C_MI_PS_WTR
MTp_C_MI_PS_ExtCMD
MTp_C_MI_PS_SD_Protection | Per normal MTp_CP:
MTp_CI_D
MTp_CI_PHB
MTp_CI_SSF
MTp_CI_AIS
MTp_CI_LStack

Per working MTp_CP:
MTp_CI_D
MTp_CI_PHB

Per protection MTp_CP:
MTp_CI_D
MTp_CI_PHB
MTp_CI_APS

Per protection group:
MTp_C_MI_cFOP-PMb
MTp_C_MI_cFOP-PMc
MTp_C_MI_cFOP-CM
MTp_C_MI_cFOP-NR
MTp_C_MI_cFOP-TO | + +#### 9.1.2.1 Protection process for trail protection + +Figure 9-7 shows the involved atomic functions in trail protection. The MT\_TT\_Sk provides the TSF/TSD protection switching criterion via the MT/MTp\_A\_Sk function (SSF/SSD) to the MTp\_C function. + +![Figure 9-7: Involved atomic functions in trail protection. This diagram shows the signal flow and functional blocks for trail protection. At the top, two 'MT/MT' blocks are connected to external sources. Below them, 'MTp' blocks process signals. The central part is a large oval labeled 'MTp_C' with 'Normal' at the top. Inside, it's divided into 'Working' and 'Protection' sections. The 'Working' section has two vertical paths: one with 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals, and another with 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals. The 'Protection' section has two vertical paths: one with 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals, and another with 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals. Each path contains 'MT/MTp', 'MT', and 'Srv/MT' blocks with various signal labels like 'MTp_CI_D/PHB', 'MTp_CI_SSF/SSD', 'MT_AI_D/PHB', 'MT_AI_TSF/TSD', 'MT_CI_D/iPHB/oPHB', and 'MT_CI_SSF/SSD'. The diagram is labeled 'G.8121-Y.1381(16)_F9-7' at the bottom right.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +Figure 9-7: Involved atomic functions in trail protection. This diagram shows the signal flow and functional blocks for trail protection. At the top, two 'MT/MT' blocks are connected to external sources. Below them, 'MTp' blocks process signals. The central part is a large oval labeled 'MTp\_C' with 'Normal' at the top. Inside, it's divided into 'Working' and 'Protection' sections. The 'Working' section has two vertical paths: one with 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals, and another with 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals. The 'Protection' section has two vertical paths: one with 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals, and another with 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals. Each path contains 'MT/MTp', 'MT', and 'Srv/MT' blocks with various signal labels like 'MTp\_CI\_D/PHB', 'MTp\_CI\_SSF/SSD', 'MT\_AI\_D/PHB', 'MT\_AI\_TSF/TSD', 'MT\_CI\_D/iPHB/oPHB', and 'MT\_CI\_SSF/SSD'. The diagram is labeled 'G.8121-Y.1381(16)\_F9-7' at the bottom right. + +**Figure 9-7 – Involved atomic functions in trail protection** + +The protection functions at both ends operate the same way, by monitoring the working and the protection trail for defects, evaluating the system status, taking into consideration the priorities of defect conditions and of external switch requests, and switching the appropriate connection point (i.e., working or protection) to the protected connection point. + +The signal flows associated with the MTp\_protection process are described with reference to Figure 9-8. 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 9-8: Protection process for trail protection. This diagram shows the internal structure of the protection process. A central box labeled 'Protection process' contains 'Selector' and 'Bridge' sub-boxes, each with 'W' (Working) and 'P' (Protection) options. Above the box, 'Normal' is indicated, with 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals entering from the top. Below the box, 'Working' and 'Protection' sections are shown. The 'Working' section has 'MTp_CI_D/PHB' and 'MTp_CI_SSF/SSD' signals. The 'Protection' section has 'MTp_CI_D/PHB/APS' and 'MTp_CI_SSF/SSD' signals. A 'MTp_C_MI_PS' signal is shown on the left. The diagram is labeled 'G.8121-Y.1381(16)_F9-8' at the bottom right.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +Figure 9-8: Protection process for trail protection. This diagram shows the internal structure of the protection process. A central box labeled 'Protection process' contains 'Selector' and 'Bridge' sub-boxes, each with 'W' (Working) and 'P' (Protection) options. Above the box, 'Normal' is indicated, with 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals entering from the top. Below the box, 'Working' and 'Protection' sections are shown. The 'Working' section has 'MTp\_CI\_D/PHB' and 'MTp\_CI\_SSF/SSD' signals. The 'Protection' section has 'MTp\_CI\_D/PHB/APS' and 'MTp\_CI\_SSF/SSD' signals. A 'MTp\_C\_MI\_PS' signal is shown on the left. The diagram is labeled 'G.8121-Y.1381(16)\_F9-8' at the bottom right. + +**Figure 9-8 – Protection process for trail protection** + +##### *Source direction:* + +For a 1+1 architecture, the CI coming from the normal (protected) MTp\_CP is bridged permanently to both the working and protection MTp\_CP. + +For a 1:1 architecture, the CI coming from the normal (protected) MTp\_CP is switched to either the working or the protection or both MT\_CPs. A switch-over from working to protection MTp\_CP 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 MTp\_CP is switched to the normal (protected) MTp\_CP. A switch-over from working to protection MTp\_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 trails, server signal fail (SSF) and server signal degrade (SSD). + +A hold-off timer is provided in order to allow interworking between nested protection schemes. 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 8.11 of [ITU-T G.8131]. + +Protection switching can also be initiated by external switch commands received via the MP or a request from the far end via the received MTp\_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.8131]. + +##### *Switching time:* + +Refer to [ITU-T G.8131]. + +##### *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 of the order of 5-12 minutes and should be capable of being set. The WTR is defined in clause 8.12 of [ITU-T G.8131]. + +In the non-revertive mode of operation no switch back to the working trail is performed when it has recovered from the fault. + +##### *Configuration:* + +The following configuration parameters are defined in [ITU-T G.8131]: + +- MTp\_C\_MI\_PS\_WorkingPortId configures the working port. +- MTp\_C\_MI\_PS\_ProtectionPortId configures the protection port. +- MTp\_C\_MI\_PS\_ProtType configures the protection type. +- MTp\_C\_MI\_PS\_OperType configures to be in revertive mode. +- MTp\_C\_MI\_PS\_HoTime configures the hold-off timer. +- MTp\_C\_MI\_PS\_WTR configures the wait-to-restore timer. +- MTp\_C\_MI\_PS\_ExtCMD configures the protection group command. + +- MTp\_C\_MI\_PS\_SD\_Protection configures the ability of a trail protection switching process to trigger protection switching upon SD. + +##### **Defects:** + +The function detects dFOP-PMb, dFOP-PMc, dFOP-CM, dFOP-NR and dFOP-TO defects in case the APS protocol is used. + +**Consequent actions:** None. + +**Defect correlations:** + +- cFOP-PMb $\leftarrow$ dFOP-PMb and (not CI\_SSF) +- cFOP-PMc $\leftarrow$ dFOP-PMc 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 – In case of cFOP-PMb/PMc/NR/TO, CI\_SSF of the protection transport entity is used. + +### **9.1.3 Connection functions for MPLS-TP shared ring protection (MSRP\_C)** + +MSRP\_C is the specific function that is used to support ring protection as specified in [ITU-T G.812]. + +The MSRP\_C connection process is a unidirectional function as illustrated in Figure 9-9 and the interface is described in Table 9-3. + +![Diagram of MSRP_C symbol showing an oval labeled MSRP_C with various interfaces: MSRP_C_MI on the left, Access link (MSRP_CI) at the top, West ring link (MSRP_CI) at the bottom left, and East ring link (MSRP_CI) at the bottom right. Each link interface includes SSF/APS, D/PHB, and PHB labels with directional arrows.](30fe9e9487585118063341332e802e98_img.jpg) + +The diagram illustrates the MSRP\_C symbol as an oval. To its left is an interface labeled MSRP\_C\_MI. Above the oval is the 'Access link' labeled MSRP\_CI, with two vertical arrows pointing towards the oval, each labeled D/PHB. Below the oval are two interfaces: 'West ring link' labeled MSRP\_CI on the left and 'East ring link' labeled MSRP\_CI on the right. Each of these ring link interfaces has three vertical arrows pointing towards the oval, labeled from left to right as SSF/APS, D/PHB, and PHB. A small text label 'G.8121-Y.1381(18)\_F9-9' is located at the bottom right of the diagram. + +Diagram of MSRP\_C symbol showing an oval labeled MSRP\_C with various interfaces: MSRP\_C\_MI on the left, Access link (MSRP\_CI) at the top, West ring link (MSRP\_CI) at the bottom left, and East ring link (MSRP\_CI) at the bottom right. Each link interface includes SSF/APS, D/PHB, and PHB labels with directional arrows. + +**Figure 9-9 – MSRP\_C symbol** + +**Table 9-3 – MSRP\_C input and output signals** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Per access MSRP_CP:
MSRP_CI_D
MSRP_CI_PHB

Per East/West MSRP_CP:
MSRP_CI_D
MSRP_CI_PHB
MSRP_CI_SSF
MSRP_CI_APS
MSRP_CI_LStack

Per input and output connection point:
for further study

Per ring protection process:
MSRP_C_MI_MSRP_EastPort
MSRP_C_MI_MSRP_WestPort
MSRP_C_MI_MSRP_ProtType
MSRP_C_MI_MSRP_HoTime
MSRP_C_MI_MSRP_WTR
MSRP_C_MI_MSRP_ExtCMD | Per access MSRP_CP:
MSRP_CI_D
MSRP_CI_PHB
MSRP_CI_LStack

Per East/West MSRP_CP:
MSRP_CI_D
MSRP_CI_PHB
MSRP_CI_SSF
MSRP_CI_APS

Per ring protection process:
for further study | + +#### 9.1.3.1 Protection process for MPLS-TP shared ring protection + +Figure 9-10 provides the involved atomic functions that support MSRP. This figure includes the LSPs entering to/exiting from MSRP. + +![Diagram of involved atomic functions MSRP. The diagram shows a hierarchy of network functions. At the top, an oval labeled MT_C is connected to external MT_CI_D/iPHB/oPHB signals. Below it are two parallel paths of functions: MSRP/MT, MSRP, and MT_CI_D/PHB[i]. These connect to a central oval labeled MSRP_C. Below MSRP_C, four parallel paths are shown. The leftmost path consists of MT/MSRP, MT, and Srv/MT, connected to a 'West ring link'. The rightmost path is identical and connected to an 'East ring link'. The two inner paths consist of MT/MSRP, MT, and Srv/MT, but the Srv/MT functions are not connected to external links. Various data flows are indicated between these functions, such as MT_CI_D/PHB, MT_AI_D/PHB, MT_AI_TSF, and MT_CI_SSF/APs.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +G.8121-Y.1381(18)\_F9-10 + +Diagram of involved atomic functions MSRP. The diagram shows a hierarchy of network functions. At the top, an oval labeled MT\_C is connected to external MT\_CI\_D/iPHB/oPHB signals. Below it are two parallel paths of functions: MSRP/MT, MSRP, and MT\_CI\_D/PHB[i]. These connect to a central oval labeled MSRP\_C. Below MSRP\_C, four parallel paths are shown. The leftmost path consists of MT/MSRP, MT, and Srv/MT, connected to a 'West ring link'. The rightmost path is identical and connected to an 'East ring link'. The two inner paths consist of MT/MSRP, MT, and Srv/MT, but the Srv/MT functions are not connected to external links. Various data flows are indicated between these functions, such as MT\_CI\_D/PHB, MT\_AI\_D/PHB, MT\_AI\_TSF, and MT\_CI\_SSF/APs. + +**Figure 9-10 – Involved atomic functions MSRP** + +Figure 9-11 shows the involved atomic functions for MSRP\_C. This figure is the same as Figure 8-1 in [ITU-T G.8132]. The MT\_TT\_Sk provides the trail signal fail (TSF) protection switching criterion via the MT/MT\_A\_Sk function (SSF) to the MSRP\_C function. The ring protection switch (RPS) in Figure 9-11 corresponds to the APS in Figure 9-10. + +![Diagram of involved atomic functions for MSRP_C at node i. It shows a central MSRP_C block connected to two ring ports: West ring port (to node i-1) and East ring port (to node i+1). Each port has an RPS/SSF block, which connects to an MT/MSRP_A block. The MT/MSRP_A block is connected to an MT_TT block. Above the MT/MSRP_A blocks are MSRP_CP(W) and MSRP_CP(P) blocks. Above these are MSRP_TCPs and MSRP_TT blocks. A 'Normal traffic' label is at the top. A legend on the right indicates P: Protection and W: Working. The diagram is labeled G.8121-Y.1381(18)_F9-11.](7e14467740b2570a44379b347a697921_img.jpg) + +Diagram of involved atomic functions for MSRP\_C at node i. It shows a central MSRP\_C block connected to two ring ports: West ring port (to node i-1) and East ring port (to node i+1). Each port has an RPS/SSF block, which connects to an MT/MSRP\_A block. The MT/MSRP\_A block is connected to an MT\_TT block. Above the MT/MSRP\_A blocks are MSRP\_CP(W) and MSRP\_CP(P) blocks. Above these are MSRP\_TCPs and MSRP\_TT blocks. A 'Normal traffic' label is at the top. A legend on the right indicates P: Protection and W: Working. The diagram is labeled G.8121-Y.1381(18)\_F9-11. + +**Figure 9-11– Involved atomic functions for MSRP\_C** + +The signal flows associated with the MSRP protection process are described with reference to Figure 9-12. The protection process receives control parameters and external switch requests at the management point (MP) reference point. The report of status information at the MP reference point is for further study. + +![Diagram of the protection process for MSRP. It shows a central box containing 'Normal' and 'Protection process' paths. The 'Normal' path is a solid blue line. The 'Protection process' path is a dashed blue line. Below the box are 'West ring' and 'East ring' labels. Arrows point from the rings to the box, labeled MSRP_CI_D/PHB/APS and MSRP_CI_SSF. Above the box, an arrow points to MSRP_CI_D/PHB. To the left, an arrow points from MSRP_C_MI_PS. The diagram is labeled G.8121-Y.1381(18)_F9-12.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Diagram of the protection process for MSRP. It shows a central box containing 'Normal' and 'Protection process' paths. The 'Normal' path is a solid blue line. The 'Protection process' path is a dashed blue line. Below the box are 'West ring' and 'East ring' labels. Arrows point from the rings to the box, labeled MSRP\_CI\_D/PHB/APS and MSRP\_CI\_SSF. Above the box, an arrow points to MSRP\_CI\_D/PHB. To the left, an arrow points from MSRP\_C\_MI\_PS. The diagram is labeled G.8121-Y.1381(18)\_F9-12. + +**Figure 9-12 – Protection process for MSRP** + +##### *Switching direction:* + +The CI coming from the normal MSRP\_CP is switched to either the east ring or the west ring MSRP\_CP. + +The CI coming from the east ring or west ring MSRP\_CP is switched to either the east ring or the west ring or the normal MSRP\_CP. A switch-over is initiated by the switch initiation criteria defined below. + +##### *Switch initiation criteria:* + +Automatic protection switching is based on the defect conditions of section MEP. SF is declared when the MPLS-TP trail termination sink (MT\_TT\_Sk) function of an MPLS-TP section MEP detects failure. + +A hold-off timer is provided. This is defined in clause 13 of [ITU-T G.812]. + +Protection switching can also be initiated by external switch commands received via the MP or a request from the far end via the received MT\_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.812]. + +*Switching time:* + +Refer to clause 7 in [ITU-T G.812]. + +*Switch restoration:* + +MSRP supports only the revertive protection operation type. Refer to clause 11 in [ITU-T G.812]. + +*Configuration:* + +The following configuration parameters are defined in [ITU-T G.812]: + +- MI\_MSRP\_EastPort configures the east ring port that contains Tunnel labels. In case of Node D in Figure 8-2 of [ITU-T G.812], This MI configures RcW\_D(D) and RcW\_X(D) (X means other nodes but C in the ring.) +- MI\_MSRP\_WestPort configures the protection port. In case of Node D in Figure 8-2 of [ITU-T G.812], This MI configures RaW\_Y(D) (Y means all the nodes in the ring.) +- MI\_MSRP\_ProtType configures the protection type. +- MI\_MSRP\_HoTime configures the hold-off timer. +- MI\_MSRP\_WTR configures the wait-to-restore timer. +- MI\_MSRP\_ExtCMD configures the protection group command. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +## 9.2 Termination functions + +### 9.2.1 MPLS-TP trail termination (MT\_TT) function + +The bidirectional MPLS-TP trail termination (MT\_TT) function terminates the MPLS-TP OAM to determine the status of the MPLS-TP (sub)layer trail. The MT\_TT function is performed by a co-located pair of the MPLS-TP trail termination source (MT\_TT\_So) and sink (MT\_TT\_Sk) functions as shown in Figure 9-13. + +![Diagram of the MT_TT function showing two MT units connected by an MT_RP link. Each MT unit is connected to an MT_AP and an MT_TCP.](38331e6e38fda222ecacad7292694c84_img.jpg) + +The diagram illustrates the MT\_TT function. It consists of two triangular nodes labeled 'MT'. A horizontal double-headed arrow labeled 'MT\_RP' connects the two 'MT' nodes. Above each 'MT' node is an 'MT\_AP' label with a vertical arrow pointing down to the 'MT' node. Below each 'MT' node is an 'MT\_TCP' label with a vertical arrow pointing up from the 'MT\_TCP' to the 'MT' node. + +Diagram of the MT\_TT function showing two MT units connected by an MT\_RP link. Each MT unit is connected to an MT\_AP and an MT\_TCP. + +G.8121-Y.1381(18)\_F9-13 + +**Figure 9-13 – MT\_TT function** + +#### 9.2.1.1 MPLS-TP trail termination source (MT\_TT\_So) function + +The MT\_TT\_So function determines and inserts the TTL value in the shim header TTL field and adds MPLS-TP OAM for proactive monitoring to the MT\_AI signal at its MT\_AP. + +##### Symbol + +The MT\_TT\_So function symbol is shown in Figure 9-14. + +![Figure 9-14 – MT_TT_So function symbol. The diagram shows a central triangle labeled 'MT'. Above it, an arrow labeled 'MT_AP' points down to the top vertex. Below it, an arrow labeled 'MT_TCP' points down from the bottom vertex. To the left, an arrow labeled 'MT_TT_So_MP' points right to the left vertex. To the right, an arrow labeled 'MT_RP' points left from the right vertex. Below the diagram is the text 'G.8121-Y.1381(18)_F9-14'.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +Figure 9-14 – MT\_TT\_So function symbol. The diagram shows a central triangle labeled 'MT'. Above it, an arrow labeled 'MT\_AP' points down to the top vertex. Below it, an arrow labeled 'MT\_TCP' points down from the bottom vertex. To the left, an arrow labeled 'MT\_TT\_So\_MP' points right to the left vertex. To the right, an arrow labeled 'MT\_RP' points left from the right vertex. Below the diagram is the text 'G.8121-Y.1381(18)\_F9-14'. + +Figure 9-14 – MT\_TT\_So function + +##### Interfaces + +The interfaces are described in Table 9-4. + +Table 9-4 – MT\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| +| MT_AP:
MT_AI_D
MT_AI_PHB

MT_RP:
MT_RI_CC_RDI
MT_RI_CC_Blk
MT_RI_OAM_Info(D,CoS,DP)

MT_TT_So_MP:
MT_TT_So_MI_GAL_Enable
MT_TT_So_MI_TTLVALUE
MT_TT_So_MI_MEG_ID
MT_TT_So_MI_MEP_ID

MT_TT_So_MI_CC_OAM_Tool
MT_TT_So_MI_RDI_OAM_Tool
MT_TT_So_MI_CC_Enable (Note)
MT_TT_So_MI_CVp_Enable (Note)
MT_TT_So_MI_CC_CoS
MT_TT_So_MI_CC_Period

MT_TT_So_MI_1LMp_Enable | MT_TCP:
MT_CI_D
MT_CI_oPHB
MT_CI_iPHB

MT_RP: | + +**Table 9-4 – MT\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| MT_TT_So_MI_LMp_OAM_Tool
MT_TT_So_MI_LMp_Enable[1...M LMp ]
MT_TT_So_MI_LMp_Period[1...M LMp ]
MT_TT_So_MI_LMp_CoS[1...M LMp ]

MT_TT_So_MI_DMp_OAM_Tool
MT_TT_So_MI_DMp_Enable[1...M DMp ]
MT_TT_So_MI_DMp_Period[1...M DMp ]
MT_TT_So_MI_DMp_Test_ID[1...M DMp ]
MT_TT_So_MI_DMp_CoS[1...M DMp ]
MT_TT_So_MI_DMp_Length[1...M DMp ]

MT_TT_So_MI_1DMp_OAM_Tool
MT_TT_So_MI_1DMp_Enable[1...M 1DMp ]
MT_TT_So_MI_1DMp_Period[1...M 1DMp ]
MT_TT_So_MI_1DMp_Test_ID[1...M 1DMp ]
MT_TT_So_MI_1DMp_Length[1...M 1DMp ]
MT_TT_So_MI_1DMp_CoS[1...M 1DMp ]

MT_TT_So_MI_SLP_OAM_Tool
MT_TT_So_MI_SLP_Enable[1...M SLP ]
MT_TT_So_MI_SLP_Period[1...M SLP ]
MT_TT_So_MI_SLP_Test_ID[1...M SLP ]
MT_TT_So_MI_SLP_Length[1...M SLP ]
MT_TT_So_MI_SLP_CoS[1...M SLP ]

MT_TT_So_MI_1SLP_OAM_Tool
MT_TT_So_MI_1SLP_Enable[1...M 1SLP ]
MT_TT_So_MI_1SLP_Period[1...M 1SLP ]
MT_TT_So_MI_1SLP_Test_ID[1...M 1SLP ]
MT_TT_So_MI_1SLP_Length[1...M 1SLP ]
MT_TT_So_MI_1SLP_CoS[1...M 1SLP ]
MT_TP:
MT_TT_So_TI_TimeStamp1 | | +| NOTE – MI_CC_Enable and MI_CVp_Enable are used to enable CC and CV functions respectively.
The possible combinations are:
– no CC function and no CV function: MI_CC_Enable = false and MI_CVp_Enable = false
– CC-only function: MI_CC_Enable = true and MI_CVp_Enable = false
– CC and CV functions: MI_CC_Enable = true and MI_CVp_Enable = true | | + +##### Processes + +The processes associated with the MT\_TT\_So function are as depicted in Figure 9-15. + +![Figure 9-15 – MT_TT_So process diagram. This block diagram illustrates the MT_TT_So function within the MT_AP layer. It shows the flow of traffic units from input (AI_D, AI_PHB) through a series of processing blocks: Block, Insert TTL, PHB, and Counter. The Counter feeds into the MEP proactive OAM G-ACh insertion block. This block interacts with the OAM PDU generation block, which in turn interacts with the Proactive OAM source control block. The output of the MEP block is CI_D, CI_oPHB, and CI_iPHB. The diagram also shows various management interfaces (MI) and reference points (RI) involved in the process. Reference points include MT_RP, MT_TT_So_MP, and MT_TT_So_TP. Management interfaces include RI_CC_Blk, RI_CC_RDI, RI_OAM_Info(D, CoS, DP), MI_TTLVALUE, MI_GAL_Enable, MI_DMp_OAM_Tool, MI_DMp_Enable[1...M_DMp], MI_DMp_Period[1...M_DMp], MI_DMp_Test_ID[1...M_DMp], MI_DMp_CoS[1...M_DMp], MI_DMp_Length[1...M_DMp], MI_1DMp_OAM_Tool, MI_1DMp_Enable, MI_1DMp_Period[1...M_1DMp], MI_1DMp_Test_ID[1...M_1DMp], MI_1DMp_Length[1...M_1DMp], MI_1DMp_CoS[1...M_1DMp], MI_SLP_OAM_Tool, MI_SLP_Enable[1...M_SLP], MI_SLP_Period[1...M_SLP], MI_SLP_Test_ID[1...M_SLP], MI_SLP_Length[1...M_SLP], MI_SLP_CoS[1...M_SLP], MI_1SLP_OAM_Tool, MI_1SLP_Enable[1...M_1SLP], MI_1SLP_Period[1...M_1SLP], MI_1SLP_Test_ID[1...M_1SLP], MI_1SLP_Length[1...M_1SLP], MI_1SLP_CoS[1...M_1SLP], MI_MEG_ID, MI_MEP_ID, MI_CC_OAM_Tool, MI_RDI_OAM_Tool, MI_CC_Enable, MI_CC_Period, MI_CVp_Enable, MI_CC_CoS, MI_LMp_OAM_Tool, MI_LMp_Enable[1...M_LMp], MI_LMp_Period[1...M_LMp], MI_LMp_CoS[1...M_LMp], and TI_TimeStamp1. The diagram is labeled G.8121-Y.1381(18)_F9-15.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +Figure 9-15 – MT\_TT\_So process diagram. This block diagram illustrates the MT\_TT\_So function within the MT\_AP layer. It shows the flow of traffic units from input (AI\_D, AI\_PHB) through a series of processing blocks: Block, Insert TTL, PHB, and Counter. The Counter feeds into the MEP proactive OAM G-ACh insertion block. This block interacts with the OAM PDU generation block, which in turn interacts with the Proactive OAM source control block. The output of the MEP block is CI\_D, CI\_oPHB, and CI\_iPHB. The diagram also shows various management interfaces (MI) and reference points (RI) involved in the process. Reference points include MT\_RP, MT\_TT\_So\_MP, and MT\_TT\_So\_TP. Management interfaces include RI\_CC\_Blk, RI\_CC\_RDI, RI\_OAM\_Info(D, CoS, DP), MI\_TTLVALUE, MI\_GAL\_Enable, MI\_DMp\_OAM\_Tool, MI\_DMp\_Enable[1...M\_DMp], MI\_DMp\_Period[1...M\_DMp], MI\_DMp\_Test\_ID[1...M\_DMp], MI\_DMp\_CoS[1...M\_DMp], MI\_DMp\_Length[1...M\_DMp], MI\_1DMp\_OAM\_Tool, MI\_1DMp\_Enable, MI\_1DMp\_Period[1...M\_1DMp], MI\_1DMp\_Test\_ID[1...M\_1DMp], MI\_1DMp\_Length[1...M\_1DMp], MI\_1DMp\_CoS[1...M\_1DMp], MI\_SLP\_OAM\_Tool, MI\_SLP\_Enable[1...M\_SLP], MI\_SLP\_Period[1...M\_SLP], MI\_SLP\_Test\_ID[1...M\_SLP], MI\_SLP\_Length[1...M\_SLP], MI\_SLP\_CoS[1...M\_SLP], MI\_1SLP\_OAM\_Tool, MI\_1SLP\_Enable[1...M\_1SLP], MI\_1SLP\_Period[1...M\_1SLP], MI\_1SLP\_Test\_ID[1...M\_1SLP], MI\_1SLP\_Length[1...M\_1SLP], MI\_1SLP\_CoS[1...M\_1SLP], MI\_MEG\_ID, MI\_MEP\_ID, MI\_CC\_OAM\_Tool, MI\_RDI\_OAM\_Tool, MI\_CC\_Enable, MI\_CC\_Period, MI\_CVp\_Enable, MI\_CC\_CoS, MI\_LMp\_OAM\_Tool, MI\_LMp\_Enable[1...M\_LMp], MI\_LMp\_Period[1...M\_LMp], MI\_LMp\_CoS[1...M\_LMp], and TI\_TimeStamp1. The diagram is labeled G.8121-Y.1381(18)\_F9-15. + +Figure 9-15 – MT\_TT\_So process diagram + +NOTE 1 – The interface between proactive OAM control and OAM PDU generation is protocol specific. + +NOTE 2 –The parameters and values in the MT\_TT\_So\_MI\_XX\_OAM\_Tool are outside the scope of this Recommendation. + +**Block:** When RI\_CC\_Blk is raised, the Block process will discard all AI\_D traffic units it receives. If RI\_CC\_Blk is cleared, the received AI\_D traffic units will be passed to the output port. + +**Insert TTL:** The time-to-live value is inserted in the outer shim header's TTL field within the MT\_AI traffic unit + +**PHB:** The AI\_PHB signal is assigned to both the CI\_iPHB and CI\_oPHB signals at the MT\_TCP reference point. + +**Counter:** This process is used to count packets for proactive loss measurements. The location of the Counter process is shown for illustration only. The exact set of packets to be counted is outside the scope of this Recommendation. + +**MEP proactive OAM G-ACh insertion:** See clause 8.1. + +**OAM PDU generation:** See clause 8.8. + +**Proactive OAM source control:** See clause 8.8. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.2.1.2 MPLS-TP trail termination sink (MT\_TT\_Sk) function + +The MT\_TT\_Sk function reports the state of the MPLS-TP trail (network connection). It extracts MPLS-TP trail OAM - for proactive monitoring - from the MPLS-TP signal at its MT\_TCP, detects defects, counts during 1-second periods errors and defects to feed performance monitoring when connected and forwards the defect information as backward indications to the companion MT\_TT\_So function. + +NOTE – The MT\_TT\_Sk function extracts and processes one level of MPLS-TP OAM irrespective of the presence of more levels. + +##### Symbol + +The MT\_TT\_Sk function symbol is shown in Figure 9-16. + +![Symbol diagram for MT_TT_Sk function. A central triangle labeled 'MT' has four interfaces: MT_AP (top, pointing up), MT_TT_Sk_MP (left, pointing left), MT_RP (right, pointing right), and MT_TCP (bottom, pointing up). Below the diagram is the text 'G.8121-Y.1381(18)_F9-16'.](a02b188a5fd52c99f84255322873bf29_img.jpg) + +G.8121-Y.1381(18)\_F9-16 + +Symbol diagram for MT\_TT\_Sk function. A central triangle labeled 'MT' has four interfaces: MT\_AP (top, pointing up), MT\_TT\_Sk\_MP (left, pointing left), MT\_RP (right, pointing right), and MT\_TCP (bottom, pointing up). Below the diagram is the text 'G.8121-Y.1381(18)\_F9-16'. + +**Figure 9-16 – MT\_TT\_Sk function** + +##### Interfaces + +The interfaces are described in Table 9-5. + +**Table 9-5 – MT\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| MT_TCP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_Lstack

MT_RP:

MT_TT_Sk_MP: | MT_AP:
MT_AI_D
MT_AI_PHB
MT_AI_TSF
MT_AI_TSD
MT_AI_AIS

MT_AI_LStack

MT_RP:
MT_RI_CC_RDI | + +**Table 9-5 – MT\_TT\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|--------------------------------------------------|---------------------------| +| MT_TT_Sk_MI_GAL_Enable | MT_RI_CC_Blk | +| MT_TT_Sk_MI_MEG_ID | | +| MT_TT_Sk_MI_PeerMEP_ID | MT_RI_OAM_Info(D,CoS,DP) | +| MT_TT_Sk_MI_CC_OAM_Tool | | +| MT_TT_Sk_MI_RDI_OAM_Tool | MT_TT_Sk_MP: | +| | MT_TT_Sk_MI_SvdCC | +| MT_TT_Sk_MI_CC_Enable (Note) | MT_TT_Sk_MI_cSSF | +| MT_TT_Sk_MI_CVp_Enable (Note) | MT_TT_Sk_MI_cLCK | +| | MT_TT_Sk_MI_cLOC | +| MT_TT_Sk_MI_CC_Period | MT_TT_Sk_MI_cMMG | +| MT_TT_Sk_MI_CC_CoSMT_TT_Sk_MI_Get_SvdCC | MT_TT_Sk_MI_cUNM | +| | MT_TT_Sk_MI_cUNP | +| MT_TT_Sk_MI_1LMp_Enable | MT_TT_Sk_MI_cUNC | +| | MT_TT_Sk_MI_cDEG | +| MT_TT_Sk_MI_LMp_OAM_Tool | MT_TT_Sk_MI_cRDI | +| MT_TT_Sk_MI_LMp_Enable[1... M LMp ] | MT_TT_Sk_MI_pN_LF[1...P] | +| MT_TT_Sk_MI_LMp_CoS[1... M LMp ] | MT_TT_Sk_MI_pN_TF[1...P] | +| MT_TT_Sk_MI_LM_DEGM | MT_TT_Sk_MI_pF_LF[1...P] | +| MT_TT_Sk_MI_LM_M | MT_TT_Sk_MI_pF_TF[1...P] | +| MT_TT_Sk_MI_LM_DEGTHR | MT_TT_Sk_MI_pF_DS | +| MT_TT_Sk_MI_LM_TFMIN | MT_TT_Sk_MI_pN_DS | +| | MT_TT_Sk_MI_pB_FD[1...P] | +| MT_TT_Sk_MI_DMp_OAM_Tool | MT_TT_Sk_MI_pB_FDV[1...P] | +| MT_TT_Sk_MI_DMp_Enable[1... M DMp ] | MT_TT_Sk_MI_pN_FD[1...P] | +| MT_TT_Sk_MI_DMp_CoS[1... M DMp ] | MT_TT_Sk_MI_pN_FDV[1...P] | +| | MT_TT_Sk_MI_pF_FD[1...P] | +| MT_TT_Sk_MI_1DMp_OAM_Tool | MT_TT_Sk_MI_pF_FDV[1...P] | +| MT_TT_Sk_MI_1DMp_Enable[1...M 1DMp ] | | +| MT_TT_Sk_MI_1DMp_Test_ID[1...M 1DMp ] | | +| MT_TT_Sk_MI_SLPp_OAM_Tool | | +| MT_TT_Sk_MI_SLPp_Enable[1... M SLp ] | | +| MT_TT_Sk_MI_SLPp_CoS[1... M SLp ] | | +| MT_TT_Sk_MI_1SLp_OAM_Tool | | +| MT_TT_Sk_MI_1SLp_Enable[1...M 1SLp ] | | +| MT_TT_Sk_MI_1SLp_Test_ID[1...M 1SLp ] | | +| MT_TT_Sk_MI_AIS_OAM_Tool | | +| MT_TT_Sk_MI_LCK_OAM_Tool | | +| MT_TT_Sk_MI_1second | | +| MT_TP: | | +| MT_TT_Sk_TI_TimeStamp1 | | + +NOTE – See NOTE in Table 9-4 + +##### Processes + +The processes associated with the MT\_TT\_Sk function are as depicted in Figure 9-17. + +![Figure 9-17 – MT_TT_Sk process diagram. This is a complex block diagram showing the internal processes of the MT_TT_Sk function. It is bounded by reference points MT_AP (top), MT_TCP (bottom), MT_RP (left), and MT_TT_So_TP (bottom left). The diagram includes several functional blocks: 'Consequent actions' (receiving AI_TSF, AI_TSD, AI_AIS and sending RI_CC_RDI, RI_CC_BLK), 'Defect correlation' (receiving MI_cSSF, MI_cLCK, MI_cLOC, MI_cMMG, MI_cUNM, MI_cUNP, MI_cUNC, MI_cDEG, MI_cRDI and sending aTSF), 'Defect generation' (receiving dxxx and sending RI_OAM_Info(D, P, DP)), 'Performance monitoring' (receiving MI_pN_TF, MI_pN_LF, MI_pF_TF, MI_pF_LF, MI_pN_DS, MI_pF_DS, MI_1second and sending MI_SvdCC, MI_1DMp_Result), 'Performance counter' (receiving aTSF), 'Proactive OAM sink control', 'OAM PDU reception', 'Block' (receiving aBLK and sending AI_PHB, AI_D, AI_LStack), 'Extract TTL', 'PHB', and 'Counter' (receiving TxFC[] and sending AI_PHB, AI_D, AI_LStack). A large 'non OAM' block represents 'MEP proactive OAM G-ACh extraction'. Numerous Management Information (MI) and Control Information (CI) signals are shown entering or leaving the main function block.](e2b7490a3455c66c85db12872c78fcc3_img.jpg) + +Figure 9-17 – MT\_TT\_Sk process diagram. This is a complex block diagram showing the internal processes of the MT\_TT\_Sk function. It is bounded by reference points MT\_AP (top), MT\_TCP (bottom), MT\_RP (left), and MT\_TT\_So\_TP (bottom left). The diagram includes several functional blocks: 'Consequent actions' (receiving AI\_TSF, AI\_TSD, AI\_AIS and sending RI\_CC\_RDI, RI\_CC\_BLK), 'Defect correlation' (receiving MI\_cSSF, MI\_cLCK, MI\_cLOC, MI\_cMMG, MI\_cUNM, MI\_cUNP, MI\_cUNC, MI\_cDEG, MI\_cRDI and sending aTSF), 'Defect generation' (receiving dxxx and sending RI\_OAM\_Info(D, P, DP)), 'Performance monitoring' (receiving MI\_pN\_TF, MI\_pN\_LF, MI\_pF\_TF, MI\_pF\_LF, MI\_pN\_DS, MI\_pF\_DS, MI\_1second and sending MI\_SvdCC, MI\_1DMp\_Result), 'Performance counter' (receiving aTSF), 'Proactive OAM sink control', 'OAM PDU reception', 'Block' (receiving aBLK and sending AI\_PHB, AI\_D, AI\_LStack), 'Extract TTL', 'PHB', and 'Counter' (receiving TxFC[] and sending AI\_PHB, AI\_D, AI\_LStack). A large 'non OAM' block represents 'MEP proactive OAM G-ACh extraction'. Numerous Management Information (MI) and Control Information (CI) signals are shown entering or leaving the main function block. + +Figure 9-17 – MT\_TT\_Sk process diagram + +NOTE – The parameters and values in the MT\_TT\_Sk\_MI\_XX\_OAM\_Tool are outside the scope of this Recommendation. + +**Extract TTL:** The time-to-live value is extracted from the outer shim header's TTL field within the MT\_CI traffic unit + +**Block:** When the aBlock (aBLK) consequent action is asserted, this process drops all traffic units arriving at its input. + +**PHB:** The CI\_oPHB signal is assigned to the AI\_PHB signal at the reference point MT\_AP. + +Note that the CI\_iPHB signal is not used by any of the processes in the function. + +**Counter:** This process is used to count packets for proactive loss measurements. The location of the counter process is shown for illustration only. The exact set of packets to be counted is outside the scope of this Recommendation. + +**MEP proactive OAM G-ACh extraction:** See clause 8.1.3. The process of CI\_D is made according to the following rule: + +``` +if ( ( (MI_GAL_Enable && MT-label(D) == GAL) || + (!MI_GAL_Enable && 1stNibble(D) == 0b0001) ) && + (Packet_Type(D) == Proactive_OAM && !APS_OAM) ) + forward to G-ACh port +} else { + forward to data port +} +``` + +NOTE – MT-label(D) and 1stNibble(D) are functions which return, respectively, the Label field at the top of the stack within the MPLS payload, the first nibble of the MPLS payload as defined in Figure 6-3 of [ITU-T G.8110.1]. + +These fields are used to identify G-ACh packets as described in clause 4.2.1 of [IETF RFC 5586]. Packet\_Type (D) is a protocol-specific function that determines whether the traffic unit contains a proactive OAM packet. + +**OAM PDU reception:** See clause 8.8 + +**Proactive OAM sink control:** See clause 8.8 + +##### **Defects generation:** + +This function detects and clears the defects (dLOC, dMMG, dUNM, dDEG, dUNP, dUNC, dRDI, dAIS and dLCK) as defined in clause 6.1 + +##### **Consequent actions:** + +``` +aBLK ← (dMMG or dUNM) +aTSF ← (dLOC and MI_CC_Enable) or (dAIS and not(MI_CC_Enable)) or (dLCK and not + (MI_CC_Enable)) or dMMG or dUNM or CI_SSF +aTSD ← dDEG and (not aTSF) +aAIS ← aTSF +aRDI ← aTSF +``` + +##### **Defect correlations:** + +``` +cLOC ← dLOC and (not dAIS) and (not dLCK) and (not CI_SSF) and (MI_CC_Enable) +cMMG ← dMMG +cUNM ← dUNM +cDEG ← dDEG and (not dAIS) and (not dLCK) and (not CI_SSF) and (not (dLOC or dMMG + or dUNM)) and (MI_CC_Enable)) +cUNP ← dUNP +cUNC ← dUNC +cRDI ← dRDI and (MI_CC_Enable) +cSSF ← CI_SSF or dAIS +``` + +cLCK $\leftarrow$ dLCK and (not dAIS) + +##### **Performance monitoring:** + +pN\_TF $\leftarrow$ N\_TF + pN\_LF $\leftarrow$ N\_LF + pF\_TF $\leftarrow$ F\_TF + pF\_LF $\leftarrow$ F\_LF + pN\_DS $\leftarrow$ aTSF + pF\_DS $\leftarrow$ aRDI[1] + pB\_FD $\leftarrow$ B\_FD + pB\_FDV $\leftarrow$ B\_FDV + pF\_FD $\leftarrow$ F\_FD + pF\_FDV $\leftarrow$ F\_FDV + pN\_FD $\leftarrow$ N\_FD + pN\_FDV $\leftarrow$ N\_FDV + +### **9.2.2 MPLS-TP trail termination function for trail protection (MTp\_TT)** + +The MTp\_TT function is used for trail protection and it is included to satisfy the modelling rules. + +The bidirectional MTp\_TT is performed by a co-located pair of MTp\_TT source (MTp\_TT\_So) and sink (MTp\_TT\_Sk) functions. + +#### **9.2.2.1 MPLS-TP trail termination source function for trail protection (MTp\_TT\_So)** + +##### **Symbol** + +The MT\_TT\_So function symbol is shown in Figure 9-18. + +![Symbol diagram for MTp_TT_So function showing input MT_AP entering a triangle labeled MTp, with output MTp_TCP exiting the bottom.](879d68959f0c0ba370ef82447298ba17_img.jpg) + +The diagram shows a vertical line labeled MT\_AP at the top pointing down into an inverted triangle labeled MTp. A vertical line exits from the bottom vertex of the triangle, labeled MTp\_TCP. Below the diagram is the text G.8121-Y.1381(18)\_F9-18. + +Symbol diagram for MTp\_TT\_So function showing input MT\_AP entering a triangle labeled MTp, with output MTp\_TCP exiting the bottom. + +**Figure 9-18 – MTp\_TT\_So function** + +##### **Interfaces** + +The interfaces are described in Table 9-6. + +**Table 9-6 – MTp\_TT\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------|-------------------------------------------| +| MT_AP:
MT_AI_D
MT_AI_PHB | MTp_TCP:
MTp_CI_D
MTp_CI_PHB | + +##### Processes + +The processes associated with the MTp\_TT\_So function are as depicted in Figure 9-19. + +![Figure 9-19: MTp_TT_So process diagram. A rectangular box represents the MTp_TT_So function. Above the box are two input labels: 'AI_D' and 'AI_PHB', with a common label 'MT_AP' above them. Below the box are two output labels: 'CI_D' and 'CI_PHB', with a common label 'MTp_TCP' below them. Arrows point from the inputs into the box and from the box to the outputs. A reference code 'G.8121-Y.1381(18)_F9-19' is at the bottom.](24ca460ee3381aee781887e9e586ec67_img.jpg) + +Figure 9-19: MTp\_TT\_So process diagram. A rectangular box represents the MTp\_TT\_So function. Above the box are two input labels: 'AI\_D' and 'AI\_PHB', with a common label 'MT\_AP' above them. Below the box are two output labels: 'CI\_D' and 'CI\_PHB', with a common label 'MTp\_TCP' below them. Arrows point from the inputs into the box and from the box to the outputs. A reference code 'G.8121-Y.1381(18)\_F9-19' is at the bottom. + +Figure 9-19– MTp\_TT\_So process diagram + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.2.2.2 MPLS-TP trail termination sink function for trail protection (MTp\_TT\_Sk) + +##### Symbol + +The MTp\_TT\_Sk function symbol is shown in Figure 9-20. + +![Figure 9-20: MTp_TT_Sk function symbol. A downward-pointing triangle is labeled 'MTp'. Above the triangle is an input label 'MT_AP' with an arrow pointing down to the triangle. Below the triangle is an output label 'MTp_TCP' with an arrow pointing up from the triangle. A reference code 'G.8121-Y.1381(18)_F9-20' is at the bottom.](cc468dcda006ef315536400517a09ad3_img.jpg) + +Figure 9-20: MTp\_TT\_Sk function symbol. A downward-pointing triangle is labeled 'MTp'. Above the triangle is an input label 'MT\_AP' with an arrow pointing down to the triangle. Below the triangle is an output label 'MTp\_TCP' with an arrow pointing up from the triangle. A reference code 'G.8121-Y.1381(18)\_F9-20' is at the bottom. + +Figure 9-20 – MTp\_TT\_Sk function + +##### Interfaces + +The interfaces are described in Table 9-7. + +Table 9-7 – MTp\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| +| MTp_TCP:
MTp_CI_D
MTp_CI_PHB
MTp_CI_Lstack

MTp_CI_SSF
MTp_CI_AIS | MT_AP:
MT_AI_D
MT_AI_PHB
MT_AI_LStack

MT_AI_TSF
MTp_CI_AIS | + +##### Processes + +The processes associated with the MTp\_TT\_Sk function are as depicted in Figure 9-21. + +![Figure 9-21 – MTp_TT_Sk process diagram. The diagram shows a process block for MTp_TT_Sk. At the top, the label 'MT_AP' is centered. Below it, five input labels are listed: 'AI_TSF', 'AI_AIS', 'AI_D', 'AI_PHB', and 'AI_LStack'. At the bottom, five corresponding output labels are listed: 'CI_SSF', 'CI_AIS', 'CI_D', 'CI_PHB', and 'CI_LStack'. Inside the process block, an arrow labeled 'aTSF' points from the 'CI_SSF' output to a box labeled 'Consequent action'. Another arrow points from this box to the 'AI_TSF' input. All other inputs and outputs are represented by vertical lines passing through the process block. A small reference code 'G.8121-Y.1381(18)_F9-21' is at the bottom right.](7f7211748473542096717109ebe5a9d6_img.jpg) + +Figure 9-21 – MTp\_TT\_Sk process diagram. The diagram shows a process block for MTp\_TT\_Sk. At the top, the label 'MT\_AP' is centered. Below it, five input labels are listed: 'AI\_TSF', 'AI\_AIS', 'AI\_D', 'AI\_PHB', and 'AI\_LStack'. At the bottom, five corresponding output labels are listed: 'CI\_SSF', 'CI\_AIS', 'CI\_D', 'CI\_PHB', and 'CI\_LStack'. Inside the process block, an arrow labeled 'aTSF' points from the 'CI\_SSF' output to a box labeled 'Consequent action'. Another arrow points from this box to the 'AI\_TSF' input. All other inputs and outputs are represented by vertical lines passing through the process block. A small reference code 'G.8121-Y.1381(18)\_F9-21' is at the bottom right. + +Figure 9-21 – MTp\_TT\_Sk process diagram + +**Defects:** None. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +$aTSF \leftarrow CI\_SSF$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 9.2.3 MPLS-TP shared ring protection trail termination function (MSRP\_TT) + +#### 9.2.3.1 MPLS-TP shared ring protection trail termination source function (MSRP\_TT\_So) + +##### Symbol + +The MSRP\_TT\_So function symbol is shown in Figure 9-22. + +![Figure 9-22 – MSRP_TT_So function symbol. The diagram shows a function symbol represented by an inverted triangle labeled 'MSRP'. Above the triangle, two parallel vertical lines descend from the label 'MT_AP'. Below the triangle, two parallel vertical lines descend to the label 'MSRP_TCP'. A small reference code 'G.8121-Y.1381(18)_F9-22' is at the bottom right.](5603b5c0db1dd6b96f76b2c851504557_img.jpg) + +Figure 9-22 – MSRP\_TT\_So function symbol. The diagram shows a function symbol represented by an inverted triangle labeled 'MSRP'. Above the triangle, two parallel vertical lines descend from the label 'MT\_AP'. Below the triangle, two parallel vertical lines descend to the label 'MSRP\_TCP'. A small reference code 'G.8121-Y.1381(18)\_F9-22' is at the bottom right. + +Figure 9-22 – MSRP\_TT\_So function + +##### Interfaces + +The interfaces are described in Table 9-8. + +Table 9-8 – MSRP\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------|--------------------------------------------------| +| per MT_AP:
MT_AI_D
MT_AI_PHB | per MSRP_TCP:
MSRP_CI_D
MSRP_CI_PHB | + +##### Processes + +The processes associated with the MSRP\_TT\_So function are as depicted in Figure 9-23. + +![Figure 9-23 – MSRP_TT_So process diagram](c06fd7dbef68a8b788158f2081d9d734_img.jpg) + +The diagram shows a rectangular block representing the MSRP\_TT\_So process. Above the block, the text 'per MT\_AP' is centered, with 'AI\_D/PHB' below it. Two upward-pointing arrows originate from the top of the block and point towards 'AI\_D/PHB'. Below the block, the text 'CI\_D/PHB' is centered, with 'per MSRP\_TCP' below it. Two downward-pointing arrows originate from the bottom of the block and point towards 'CI\_D/PHB'. At the bottom right of the diagram, the text 'G.8121-Y.1381(18)\_F9-23' is present. + +Figure 9-23 – MSRP\_TT\_So process diagram + +Figure 9-23 – MSRP\_TT\_So process diagram + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.2.3.2 MPLS-TP shared ring protection trail termination sink function (MSRP\_TT\_Sk) + +##### Symbol + +The MSRP\_TT\_Sk function symbol is shown in Figure 9-24. + +![Figure 9-24 – MSRP_TT_Sk function](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) + +The diagram shows a downward-pointing triangle representing the MSRP\_TT\_Sk function. Above the triangle, the text 'MT\_AP' is centered. Two upward-pointing arrows originate from the top vertex of the triangle and point towards 'MT\_AP'. Inside the triangle, the text 'MSRP' is centered. Below the triangle, the text 'MSRP\_TCP' is centered. Two downward-pointing arrows originate from the bottom vertex of the triangle and point towards 'MSRP\_TCP'. At the bottom right of the diagram, the text 'G.8121-Y.1381(18)\_F9-24' is present. + +Figure 9-24 – MSRP\_TT\_Sk function + +Figure 9-24 – MSRP\_TT\_Sk function + +##### Interfaces + +The interfaces are described in Table 9-9. + +Table 9-9 – MSRP\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------|------------------------------------| +| per MSRP_TCP:
MSRP_CI_D
MSRP_CI_PHB | per MT_AP:
MT_AI_D
MT_AI_PHB | + +##### Processes + +The processes associated with the MSRP\_TT\_Sk function are as depicted in Figure 9-25. + +![Diagram of MSRP_TT_Sk process](d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg) + +The diagram shows a rectangular box representing the MSRP\_TT\_Sk process. Above the box, the text "per MT\_AP" is centered, with "AI\_D/PHB" directly below it. Below the box, the text "CI\_D/PHB" is centered, with "per MSRP\_TCP" directly below it. Two vertical arrows point from the "AI\_D/PHB" label, through the box, to the "CI\_D/PHB" label. At the bottom right of the diagram, the text "G.8121-Y.1381(18)\_F9-25" is present. + +Diagram of MSRP\_TT\_Sk process + +Figure 9-25 – MSRP\_TT\_Sk process + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 9.3 Adaptation functions + +### 9.3.1 MPLS-TP to MPLS-TP adaptation function (MT/MT\_A) + +#### 9.3.1.1 MPLS-TP to MPLS-TP adaptation source function (MT/MT\_A\_So) + +##### Symbol + +The MT/MT\_A\_So function symbol is shown in Figure 9-26. This function maps client MT\_CI traffic units into server MT\_AI traffic units. + +![Diagram of MT/MT_A_So function](53cbabe6260e970b4472b25503f74e9f_img.jpg) + +The diagram shows a yellow trapezoidal symbol representing the MT/MT\_A\_So function. Above the symbol, multiple vertical arrows labeled "MT\_CI" point into the top edge, with an ellipsis "..." between them. Below the symbol, a single vertical arrow labeled "MT\_AI" points out from the bottom vertex. To the right of the symbol, a horizontal arrow labeled "MT/MT\_A\_So\_MI" points into the right side. At the bottom right of the diagram, the text "G.8121-Y.1381(18)\_F9-26" is present. + +Diagram of MT/MT\_A\_So function + +Figure 9-26 – MT/MT\_A\_So function + +##### Interfaces + +The interfaces are described in Table 9-10. + +**Table 9-10 – MT/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB

MT_CP:
MT_CI_APS

MT/MT_A_So_MI:
MT/MT_A_So_MI_Admin_State
MT/MT_A_So_MI_Label[1...M]
MT/MT_A_So_MI_LSPTYPE[1...M]
MT/MT_A_So_MI_CoS[1...M]
MT/MT_A_So_MI_PHB2TCMapping[1...M]
MT/MT_A_So_MI_QoSEncodingMode[1...M]
MT/MT_A_So_MI_Mode

MT/MT_A_So_MI_LCK_Period[1...M]
MT/MT_A_So_MI_LCK_CoS[1...M]
MT/MT_A_So_MI_LCK_OAM_Tool[1...M]
MT/MT_A_So_MI_GAL_Enable[1...M]

MT/MT_A_So_MI_APS_CoS
MT/MT_A_So_MI_APS_OAM_Tool | MT_AP:
MT_AI_Data
MT_AI_PHB | + +##### Processes + +The processes associated with the MT/MT\_A\_So function are as depicted in Figure 9-27. + +![Figure 9-27 – MT/MT_A_So process diagram. This block diagram illustrates the data flow and processing stages for MT/MT_A_So. On the left, multiple input paths labeled MT_CI[1] through MT_CI[M] enter the system. Each path consists of three parallel signals: D, iPHB, and oPHB. These signals first pass through an 'LCK generate' block, which is influenced by configuration parameters: MI_GAL_Enable, MI_LCK_OAM_Tool[1..M], MI_LCK_Period[1..M], and MI_LCK_CoS[1..M]. The output of the 'LCK generate' block goes to a 'Selector' block with 'Normal' and 'Lock' inputs. The 'Selector' is controlled by MI_Admin_State. The output of the 'Selector' (D, iPHB, oPHB) then enters a 'TC/Label processes' block, which is configured by MI_LSPTYPE[1..M], MI_Label[1..M], MI_CoS[1..M], MI_PHB2TCMapping[1..M], and MI_QoSEncodingMode[1..M]. The output of this block (D, PHB) goes to an 'Insert S field' block. The output of 'Insert S field' (D, PHB) then goes to an 'APS insert' block, which is configured by MI_GAL_Enable, MI APS_OAM_Tool[1..M], and MI APS_CoS[1..M]. The final output of the system is labeled MT_AI.](3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg) + +Figure 9-27 – MT/MT\_A\_So process diagram. This block diagram illustrates the data flow and processing stages for MT/MT\_A\_So. On the left, multiple input paths labeled MT\_CI[1] through MT\_CI[M] enter the system. Each path consists of three parallel signals: D, iPHB, and oPHB. These signals first pass through an 'LCK generate' block, which is influenced by configuration parameters: MI\_GAL\_Enable, MI\_LCK\_OAM\_Tool[1..M], MI\_LCK\_Period[1..M], and MI\_LCK\_CoS[1..M]. The output of the 'LCK generate' block goes to a 'Selector' block with 'Normal' and 'Lock' inputs. The 'Selector' is controlled by MI\_Admin\_State. The output of the 'Selector' (D, iPHB, oPHB) then enters a 'TC/Label processes' block, which is configured by MI\_LSPTYPE[1..M], MI\_Label[1..M], MI\_CoS[1..M], MI\_PHB2TCMapping[1..M], and MI\_QoSEncodingMode[1..M]. The output of this block (D, PHB) goes to an 'Insert S field' block. The output of 'Insert S field' (D, PHB) then goes to an 'APS insert' block, which is configured by MI\_GAL\_Enable, MI APS\_OAM\_Tool[1..M], and MI APS\_CoS[1..M]. The final output of the system is labeled MT\_AI. + +Figure 9-27 – MT/MT\_A\_So process diagram + +– *LCK generation process:* + +See clause 8.6.3. Each CP has its LCK generation process. + +– *Selector process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +– *TC/Label processes:* + +See 8.2.1. + +– *S Field Insertion:* + +A 1-bit S Field set to 0 (not bottom of label stack) is inserted to indicate the client is MPLS. + +– *APS insert processes:* + +See clause 8.7.2.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.3.1.2 MPLS-TP to MPLS-TP adaptation sink function (MT/MT\_A\_Sk) + +The MT/MT\_A\_Sk function symbol is shown in Figure 9-28. This function retrieves client MT\_CI traffic units from server MT\_AI traffic units. + +![Diagram of the MT/MT_A_Sk function symbol. It is a yellow trapezoid pointing downwards. An arrow labeled 'MT_AI' points into the bottom vertex. An arrow labeled 'MT/MT_A_Sk_MI' points into the right side. Multiple arrows labeled 'MT_CI' point out of the top edge, with an ellipsis between them. Below the diagram is the text 'G.8121-Y.1381(18)_F9-28'.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) + +Diagram of the MT/MT\_A\_Sk function symbol. It is a yellow trapezoid pointing downwards. An arrow labeled 'MT\_AI' points into the bottom vertex. An arrow labeled 'MT/MT\_A\_Sk\_MI' points into the right side. Multiple arrows labeled 'MT\_CI' point out of the top edge, with an ellipsis between them. Below the diagram is the text 'G.8121-Y.1381(18)\_F9-28'. + +Figure 9-28 – MT/MT\_A\_Sk function + +##### Interfaces + +The interfaces are described in Table 9-11. + +Table 9-11 – MT/MT\_A\_Sk interfaces + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| MT_AP:
MT_AI_Data
MT_AI_PHB
MT_AI_TSF
MT_AI_TSD
MT_AI_AIS
MT_AI_LStack
MT/MT_A_Sk_MP:
MT/MT_A_Sk_MI_AdminState
MT/MT_A_Sk_MI_Label[1...M]
MT/MT_A_Sk_MI_LSPTYPE[1...M]
MT/MT_A_Sk_MI_CoS[1...M]
MT/MT_A_Sk_MI_TC2PHBMapping[1...M]
MT/MT_A_Sk_MI_QoSDecodingMode[1...M]
MT/MT_A_Sk_MI_Mode

MT/MT_A_Sk_MI_AIS_Period[1...M]
MT/MT_A_Sk_MI_AIS_CoS[1...M]
MT/MT_A_Sk_MI_AIS_OAM_Tool[1...M]
MT/MT_A_Sk_MI_LCK_Period[1...M]
MT/MT_A_Sk_MI_LCK_CoS[1...M]
MT/MT_A_Sk_MI_LCK_OAM_Tool[1...M]
MT/MT_A_Sk_MI_APS_OAM_Tool

MT/MT_A_Sk_MI_GAL_Enable [1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack
MT_CI_SSF

MT_CP[1]:
MT_CI_SSD[1]
MT_CI_APS[1] | + +##### Processes + +The processes associated with the MT/MT\_A\_Sk function are as depicted in Figure 9-29. + +![Figure 9-29 – MT/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of the MT/MT_A_Sk function. At the top, multiple input streams labeled MT_CI[1] through MT_CI[M] enter the system. Each stream passes through a 'Selector' block with 'Normal' and 'Lock' options, then an 'LCK generate' block, and an 'AIS insert' block. Below these, a 'TC/Label processes' block handles the data. Further down, an 'Insert S field' block and an 'APS extract' block are shown. On the left, 'Consequent actions' are triggered by 'aSSF' and 'aAIS' signals. The bottom output is labeled MT_AI. Various management information (MI) parameters are shown on the right, such as MI_Admin_State, MI_LCK_OAM_Tool[1..M], MI_AIS_OAM_Tool[1..M], MI_Label[1..M], and MI_GAL_Enable. Data flow is indicated by arrows labeled with 'D', 'iPHB', 'oPHB', 'aSSF', 'aAIS', 'AIS', 'TSF', 'PHB', 'APS', and 'LStack'.](d31b402b650e68c7d6b55d3cf8fda086_img.jpg) + +Figure 9-29 – MT/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of the MT/MT\_A\_Sk function. At the top, multiple input streams labeled MT\_CI[1] through MT\_CI[M] enter the system. Each stream passes through a 'Selector' block with 'Normal' and 'Lock' options, then an 'LCK generate' block, and an 'AIS insert' block. Below these, a 'TC/Label processes' block handles the data. Further down, an 'Insert S field' block and an 'APS extract' block are shown. On the left, 'Consequent actions' are triggered by 'aSSF' and 'aAIS' signals. The bottom output is labeled MT\_AI. Various management information (MI) parameters are shown on the right, such as MI\_Admin\_State, MI\_LCK\_OAM\_Tool[1..M], MI\_AIS\_OAM\_Tool[1..M], MI\_Label[1..M], and MI\_GAL\_Enable. Data flow is indicated by arrows labeled with 'D', 'iPHB', 'oPHB', 'aSSF', 'aAIS', 'AIS', 'TSF', 'PHB', 'APS', and 'LStack'. + +Figure 9-29 – MT/MT\_A\_Sk process diagram + +- *Selector process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +- *LCK generation process:* + +See clause 8.6.3. + +- *AIS insert process:* + +See clause 8.6.2. + +- *TC/Label sink processes:* + +See clause 8.2.2. + +- *Label stack copy processes:* + +See clause 8.2.3. + +- *S field extraction:* + +Extract and process the 1-bit S Field: the retrieved S Field should have the value 0 (not bottom of label stack) to indicate the client is MPLS; for such case the traffic unit is accepted and forwarded (together with the PHB information) after extraction of the S-bit field to the next process. For the case the S-bit has the value 1, the traffic unit is silently discarded. + +– *APS extract processes:* + +See clause 8.7.2.2. + +**Defects:** None. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +aSSD $\leftarrow$ AI\_TSD + +aAIS $\leftarrow$ AI\_AIS + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### **9.3.2 MPLS-TP to MPLS-TP adaptation function for trail protection (MT/MTp\_A)** + +The MT/MTp\_A function is used for trail protection. + +The bidirectional MT/MTp\_A is performed by a co-located pair of MT/MTp\_A source (MT/MTp\_A\_So) and sink (MT/MTp\_A\_Sk) functions. + +#### **9.3.2.1 MPLS-TP to MPLS-TP adaptation source function for Trail Protection (MT/MTp\_A\_So)** + +##### **Symbol** + +The MT/MTp\_A\_So function symbol is shown in Figure 9-30. This function maps client MTp\_CI traffic units into server MT\_AI traffic units. + +![Diagram of the MT/MTp_A_So function symbol. It shows a trapezoidal block labeled 'MT/MTp'. An arrow labeled 'MTp_CP' points into the top of the block. An arrow labeled 'MT/MTp_MP' points into the right side of the block. An arrow labeled 'MT_AP' points out from the bottom of the block.](6d7b7d0e208d784d9172282cf788cb31_img.jpg) + +``` +graph TD; MTp_CP[MTp_CP] --> MT_MTp{MT/MTp}; MT_MTp_MP[MT/MTp_MP] --> MT_MTp; MT_MTp --> MT_AP[MT_AP]; +``` + +Diagram of the MT/MTp\_A\_So function symbol. It shows a trapezoidal block labeled 'MT/MTp'. An arrow labeled 'MTp\_CP' points into the top of the block. An arrow labeled 'MT/MTp\_MP' points into the right side of the block. An arrow labeled 'MT\_AP' points out from the bottom of the block. + +G.8121-Y.1381(18)\_F9-30 + +**Figure 9-30 – MT/MTp\_A\_So function** + +##### **Interfaces** + +The interfaces are described in Table 9-12. + +**Table 9-12 – MT/MTp\_A\_So interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| MT_CP:
MTp_CI_Data
MTp_CI_PHB
MTp_CI_APS

MT/MTp_A_So_MI:
MT/MTp_A_So_MI_GAL_Enable
MT/MTp_A_So_MI_APS_CoS
MT/MTp_A_So_MI_APS_OAM_Tool | MT_AP:
MT_AI_Data
MT_AI_PHB | + +##### **Processes** + +The processes associated with the MT/MTp\_TT\_So function are as depicted in Figure 9-31. + +![MT/MTp_A_So process diagram showing the APS insert process. Inputs CI_APS and CI_D/PHB enter a box labeled 'APS insert'. Control inputs MI_GAL_Enable, MI_APS_OAM_Tool, and MI_APS_CoS enter from the right. Output AI_D/PHB exits the box. The diagram is labeled MTP_CP at the top and MT_AP at the bottom. Reference G.8121-Y.1381(18)_F9-31 is shown.](b87818c8505328b198d035761bbc3f2d_img.jpg) + +The diagram illustrates the 'APS insert' process. At the top, 'MTP\_CP' is labeled. Below it, two input lines labeled 'CI\_APS' and 'CI\_D/PHB' enter a rectangular box labeled 'APS insert'. To the right of the box, three control inputs labeled 'MI\_GAL\_Enable', 'MI\_APS\_OAM\_Tool', and 'MI\_APS\_CoS' enter. From the bottom of the box, two output lines labeled 'AI\_D/PHB' exit. At the bottom of the diagram, 'MT\_AP' is labeled. In the bottom right corner, the reference 'G.8121-Y.1381(18)\_F9-31' is shown. + +MT/MTp\_A\_So process diagram showing the APS insert process. Inputs CI\_APS and CI\_D/PHB enter a box labeled 'APS insert'. Control inputs MI\_GAL\_Enable, MI\_APS\_OAM\_Tool, and MI\_APS\_CoS enter from the right. Output AI\_D/PHB exits the box. The diagram is labeled MTP\_CP at the top and MT\_AP at the bottom. Reference G.8121-Y.1381(18)\_F9-31 is shown. + +**Figure 9-31 – MT/MTp\_A\_So process diagram** + +– APS insert process: + +See clause 8.7.2.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### **9.3.2.2 MPLS-TP to MPLS-TP adaptation sink function for trail protection (MT/MTp\_A\_Sk)** + +The MT/MTp\_A\_Sk function symbol is shown in Figure 9-32. This function retrieves client MTp\_CI traffic units from the server MT\_AI traffic units. + +![Figure 9-32: MT/MTp_A_Sk function block diagram. A central trapezoidal block labeled 'MT/MTp' has three input arrows from below: 'MT_AP', 'MT/MTp_MP', and 'MTp_CP'.](24ba47df8be44ae91945d88ce2232df5_img.jpg) + +G.8121-Y.1381(18)\_F9-32 + +Figure 9-32: MT/MTp\_A\_Sk function block diagram. A central trapezoidal block labeled 'MT/MTp' has three input arrows from below: 'MT\_AP', 'MT/MTp\_MP', and 'MTp\_CP'. + +**Figure 9-32 – MT/MTp\_A\_Sk function** + +##### **Interfaces** + +The interfaces are described in Table 9-13. + +**Table 9-13 – MT/MTp\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| MT_AP:
MT_AI_Data
MT_AI_PHB
MT_AI_TSF
MT_AI_TSD
MT_AI_AIS
MT_AI_LStack

MT/MTp_A_Sk_MP:
MT/MTp_A_Sk_MI_APS_OAM_Tool
MT/MTp_A_Sk_MI_GAL_Enable | MTp_CP:
MTp_CI_Data
MTp_CI_PHB

MTp_CI_SSF
MTp_CI_SSD
MTp_CI_AIS
MTp_CI_LStack
MTp_CI_APS | + +##### **Processes** + +The processes associated with the MT/MT\_A\_Sk function are as depicted in Figure 9-33. + +![Figure 9-33: MT/MTp_A_Sk process diagram. A large box contains two sub-processes: 'Consequent action' and 'APS extract'. Inputs from 'MT_AP' (AI_AIS, AI_TSF, AI_TSD, AI_D/PHB, AI_LStack) enter the box. 'Consequent action' outputs CI_AIS, CI_SSF, CI_SSD, CI_APS. 'APS extract' outputs CI_D/PHB, CI_LStack. External inputs MI_GAL_Enable and MI_APS_OAM_Tool enter the 'APS extract' process. A small box labeled 'aSSF aSSD' is between the two processes.](6334c962f5e106e3331e59946e4d166e_img.jpg) + +G.8121-Y.1381(18)\_F9-33 + +Figure 9-33: MT/MTp\_A\_Sk process diagram. A large box contains two sub-processes: 'Consequent action' and 'APS extract'. Inputs from 'MT\_AP' (AI\_AIS, AI\_TSF, AI\_TSD, AI\_D/PHB, AI\_LStack) enter the box. 'Consequent action' outputs CI\_AIS, CI\_SSF, CI\_SSD, CI\_APS. 'APS extract' outputs CI\_D/PHB, CI\_LStack. External inputs MI\_GAL\_Enable and MI\_APS\_OAM\_Tool enter the 'APS extract' process. A small box labeled 'aSSF aSSD' is between the two processes. + +**Figure 9-33 – MT/MTp\_A\_Sk process diagram** + +– APS extract process: + +See clause 8.7.2.2. + +**Defects:** None. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +aSSD $\leftarrow$ AI\_TSD + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### **9.3.3 MPLS-TP to MSRP adaptation function (MT/MSRP\_A)** + +#### **9.3.3.1 MPLS-TP to MSRP adaptation source function (MT/MSRP\_A\_So)** + +##### **Symbol** + +The MT/MSRP\_A\_So function symbol is shown in Figure 9-34. This function maps client MSRP\_CI traffic units into server MT\_AI traffic units. + +![Function symbol diagram for MT/MSRP_A_So. It shows a trapezoidal block labeled 'MT/MSRP'. An arrow labeled 'MSRP_CP' points into the top of the block. An arrow labeled 'MT/MSRP_MP' points into the right side of the block. An arrow labeled 'MT_AP' points out from the bottom of the block.](7b2d685b805535c1e94aee1365753b92_img.jpg) + +``` +graph TD; + MSRP_CP[MSRP_CP] --> MT_MSRP[MT/MSRP]; + MT_MSRP_MP[MT/MSRP_MP] --> MT_MSRP; + MT_MSRP --> MT_AP[MT_AP]; +``` + +Function symbol diagram for MT/MSRP\_A\_So. It shows a trapezoidal block labeled 'MT/MSRP'. An arrow labeled 'MSRP\_CP' points into the top of the block. An arrow labeled 'MT/MSRP\_MP' points into the right side of the block. An arrow labeled 'MT\_AP' points out from the bottom of the block. + +G.8121-Y.1381(18)\_F9-34 + +**Figure 9-34 – MT/MSRP\_A\_So function** + +##### **Interfaces** + +The interfaces are described in Table 9-14. + +**Table 9-14 – MT/MSRP\_A\_So interfaces** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| MSRP_CP:
MSRP_CI_Data
MSRP_CI_PHB
MSRP_CI_APS

MT/ MSRP_A_So_MI:
MT/MSRP_A_So_MI_GAL_Enable
MT/MSRP_A_So_MI_APS_CoS
MT/MSRP_A_So_MI_APS_OAM_Tool | MT_AP:
MT_AI_Data
MT_AI_PHB | + +##### Processes + +The processes associated with the MT/MSRP\_TT\_So function are as depicted in Figure 9-35. + +![Figure 9-35 – MT/MSRP_A_So process diagram](d510bddda14c44163bbeee33b491a105_img.jpg) + +The diagram shows a process block for MT/MSRP\_A\_So. At the top, 'MSRP\_CP' is labeled, with two sub-interfaces 'CI\_APS' and 'CI\_D/PHB' below it. Arrows from these interfaces point into a rectangular box containing a smaller box labeled 'APS insert'. To the right of the 'APS insert' box, three management interface labels are shown: 'MI\_GAL\_Enable', 'MI\_APS\_OAM\_Tool', and 'MI\_APS\_CoS', with an arrow pointing from them into the 'APS insert' box. Below the main box, two arrows point down to 'AI\_D/PHB' and 'MT\_AP'. The reference code 'G.8121-Y.1381(18)\_F9-35' is located at the bottom right of the diagram. + +Figure 9-35 – MT/MSRP\_A\_So process diagram + +Figure 9-35 – MT/MSRP\_A\_So process diagram + +– APS insert process: + +See clause 8.7.2.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.3.3.2 MPLS-TP to MSRP adaptation sink function (MT/MSRP\_A\_Sk) + +The MT/MSRP\_A\_Sk function symbol is shown in Figure 9-36. This function extracts client MSRP\_CI traffic units from the server MT\_AI traffic units. + +![Figure 9-36 – MT/MSRP_A_Sk function](f40480872b021d2ac7c29202c199b695_img.jpg) + +The diagram shows the MT/MSRP\_A\_Sk function symbol, which is a trapezoid pointing downwards. Above the symbol, 'MSRP\_CP' is labeled with an upward-pointing arrow. To the right, 'MT/MSRP\_MP' is labeled with a leftward-pointing arrow. Below the symbol, 'MT\_AP' is labeled with an upward-pointing arrow. The reference code 'G.8121-Y.1381(18)\_F9-36' is located at the bottom right of the diagram. + +Figure 9-36 – MT/MSRP\_A\_Sk function + +Figure 9-36 – MT/MSRP\_A\_Sk function + +##### Interfaces + +The interfaces are described in Table 9-15. + +**Table 9-15 – MT/MSRP\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------| +| MT_AP:
MT_AI_Data
MT_AI_PHB
MT_AI_TSF
MT_AI_LStack

MT/MSRP_A_Sk_MP:
MT/MSRP_A_Sk_MI_APS_OAM_Tool
MT/MSRP_A_Sk_MI_GAL_Enable | MSRP_CP:
MSRP_CI_Data
MSRP_CI_PHB
MSRP_CI_SSF
MSRP_CI_LStack
MSRP_CI_APS | + +##### **Processes** + +The processes associated with the MT/MSRP\_A\_Sk function are as depicted in Figure 9-37. + +![Figure 9-37: MT/MSRP_A_Sk process diagram. It shows a central box containing two sub-processes: 'Consequent action' and 'APS extract'. Inputs from MT_AP (AI_TSF, AI_D/PHB, AI_LStack) enter the box. 'Consequent action' outputs CI_SSF. 'APS extract' outputs CI_APS, CI_D/PHB, and CI_LStack. Control inputs MI_GAL_Enable and MI_APS_OAM_Tool enter from the right. The diagram is labeled G.8121-Y.1381(18)_F9-37.](18d7d8de298d79e7bc87af5217f11203_img.jpg) + +Figure 9-37: MT/MSRP\_A\_Sk process diagram. It shows a central box containing two sub-processes: 'Consequent action' and 'APS extract'. Inputs from MT\_AP (AI\_TSF, AI\_D/PHB, AI\_LStack) enter the box. 'Consequent action' outputs CI\_SSF. 'APS extract' outputs CI\_APS, CI\_D/PHB, and CI\_LStack. Control inputs MI\_GAL\_Enable and MI\_APS\_OAM\_Tool enter from the right. The diagram is labeled G.8121-Y.1381(18)\_F9-37. + +**Figure 9-37– MT/MSRP\_A\_Sk process** + +### **9.3.4 MSRP to MPLS-TP adaptation function (MSRP/MT\_A)** + +#### **9.3.4.1 MSRP to MPLS-TP adaptation source function (MSRP/MT\_A\_So)** + +##### **Symbol** + +The MSRP/MT\_A\_So function symbol is shown in Figure 9-38. + +![Figure 9-38: MSRP/MT_A_So function symbol. It shows a trapezoidal symbol labeled 'MSRP/MT'. Multiple input arrows labeled 'MT_CP' enter from the top. An output arrow labeled 'MSRP_AP' exits from the bottom. A control input labeled 'MSRP/MT_MP' enters from the right. The diagram is labeled G.8121-Y.1381(18)_F9-38.](5ec2b6e9c9133bfbb26789d85dc49774_img.jpg) + +Figure 9-38: MSRP/MT\_A\_So function symbol. It shows a trapezoidal symbol labeled 'MSRP/MT'. Multiple input arrows labeled 'MT\_CP' enter from the top. An output arrow labeled 'MSRP\_AP' exits from the bottom. A control input labeled 'MSRP/MT\_MP' enters from the right. The diagram is labeled G.8121-Y.1381(18)\_F9-38. + +**Figure 9-38 – MSRP/MT\_A\_So function** + +##### Interfaces + +The interfaces are described in Table 9-16. + +**Table 9-16 – MSRP/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| per MT_CP[1..n]:
MSRP_CI_Data
MSRP_CI_iPHB
MSRP_CI_oPHB
MSRP_CI_LSTACK

MT/MSRP_A_So_MI:
MT/MSRP_MI_DestNode_ID[1..m] | per MT_AP[1..m]:
MT_AI_Data
MT_AI_PHB | +| NOTE – 'n' means number of LSPs to MSRP sublayer. 'm' means number of nodes in a ring. | | + +##### Processes + +The processes associated with the MSRP/MT\_A\_So function are as depicted in Figure 9-39. + +![Diagram of MSRP/MT_A_So process showing inputs (CI_D/iPHB/oPHB/LSTACK, CI_D/iPHB/oPHB/STTCK) entering a block with 'To node#1' and 'To node#m' sub-processes. An external input MI_DestNode_ID[1..m] also enters the 'To node#m' sub-process. Outputs are AI_D/PHB leading to m x MSRP_APs.](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +G.8121-Y.1381(18)\_F9-39 + +Diagram of MSRP/MT\_A\_So process showing inputs (CI\_D/iPHB/oPHB/LSTACK, CI\_D/iPHB/oPHB/STTCK) entering a block with 'To node#1' and 'To node#m' sub-processes. An external input MI\_DestNode\_ID[1..m] also enters the 'To node#m' sub-process. Outputs are AI\_D/PHB leading to m x MSRP\_APs. + +**Figure 9-39 – MSRP/MT\_A\_So process** + +– *To node#i process:* + +This process enables each MPLS-TP LSP traffic to go to each ring node. + +#### 9.3.4.2 MSRP to MPLS-TP adaptation sink function (MSRP/MT\_A\_Sk) + +##### Symbol + +The MSRP/MT\_A\_Sk function symbol is shown in Figure 9-40. + +![Symbol for MSRP/MT_A_Sk function showing a trapezoidal block labeled MT/MSRP. Inputs MT_AP and MT/MSRP_MP enter from the bottom. Multiple arrows labeled MSRP_CP exit from the top.](ac8194ec0d833d53a0a36adada95b39e_img.jpg) + +G.8121-Y.1381(18)\_F9-40 + +Symbol for MSRP/MT\_A\_Sk function showing a trapezoidal block labeled MT/MSRP. Inputs MT\_AP and MT/MSRP\_MP enter from the bottom. Multiple arrows labeled MSRP\_CP exit from the top. + +**Figure 9-40– MSRP/MT\_A\_Sk function** + +##### Interfaces + +The interfaces are described in Table 9-17. + +**Table 9-17 – MSRP/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| per MT_AP[1...m]:
MT_AI_Data
MT_AI_PHB | per MT_CP[1..n]:
MSRP_CI_Data
MSRP_CI_iPHB
MSRP_CI_oPHB
MSRP_CI_LSTACK | +| NOTE – 'n' means number of LSPs from MSRP sublayer. 'm' means number of nodes in a ring. | | + +##### Processes + +The processes associated with the MSRP/MT\_A\_Sk function are as depicted in Figure 9-41. + +![Diagram of MSRP/MT_A_Sk process showing m x MT_CPs and m x MSRP_APs.](2fc2e531b3b3c695cca497516ec79f20_img.jpg) + +The diagram illustrates the MSRP/MT\_A\_Sk process. At the top, 'm x MT\_CPs' are shown. Below them, a large rectangle contains 'm' individual boxes labeled 'From node#1', '...', and 'From node#m'. Each of these boxes has two upward-pointing arrows leading to 'CI\_D/iPHB/oPHB/LSTACK' and 'CI\_D/iPHB/oPHB/STACK' respectively. Below the rectangle, 'm x MSRP\_APs' are shown. Each of these has an upward-pointing arrow labeled 'AI\_D/PHB' leading into the rectangle. A reference code 'G.8121-Y.1381(18)\_F9-41' is located to the right of the rectangle. + +Diagram of MSRP/MT\_A\_Sk process showing m x MT\_CPs and m x MSRP\_APs. + +**Figure 9-41 – MSRP/MT\_A\_Sk process** + +– *From node#i process:* + +This process enables MPLS-TP LSPs from each ring traffic to go out of the ring. + +## 9.4 MT diagnostic function + +### 9.4.1 MT diagnostic functions for MEPs (MTDe) + +#### 9.4.1.1 MT diagnostic trail termination functions for MEPs (MTDe\_TT) + +The bidirectional MTDe trail termination (MTDe\_TT) function is performed by a co-located pair of MTDe trail termination source (MTDe\_TT\_So) and sink (MTDe\_TT\_Sk) functions as shown in Figure 9-42. + +![Diagram of MTDe_TT function showing two MTDe units connected by MTDe_RP.](d5661c3661190c44429a1a75f61d7550_img.jpg) + +The diagram shows the MTDe\_TT function. It consists of two triangular MTDe units facing each other, connected by a horizontal line labeled 'MTDe\_RP'. The left MTDe unit has an incoming arrow from 'MTDe\_AP' above it and an outgoing arrow to 'MT\_TCP' below it. The right MTDe unit has an outgoing arrow to 'MTDe\_AP' above it and an incoming arrow from 'MT\_TCP' below it. A reference code 'G.8121-Y.1381(18)\_F9-42' is located below the right MTDe unit. + +Diagram of MTDe\_TT function showing two MTDe units connected by MTDe\_RP. + +**Figure 9-42 – MTDe\_TT** + +##### 9.4.1.1.1 MT diagnostic trail termination source function for MEPs (MTDe\_TT\_So) + +###### Symbol + +The MTDe\_TT\_So function symbol is shown in Figure 9-43. + +![Figure 9-43 – MTDe_TT_So symbol. The diagram shows a central triangle labeled 'MTDe'. Above it, 'MTDe_AP' points down to the top vertex. To the left, 'MTDe_TT_So_MP' points right to the left vertex. To the right, 'MTDe_RP' points left to the right vertex. Below the triangle, 'MT_TCP' points up from the bottom vertex. At the very bottom, the text 'G.8121-Y.1381(18)_F9-43' is present.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +Figure 9-43 – MTDe\_TT\_So symbol. The diagram shows a central triangle labeled 'MTDe'. Above it, 'MTDe\_AP' points down to the top vertex. To the left, 'MTDe\_TT\_So\_MP' points right to the left vertex. To the right, 'MTDe\_RP' points left to the right vertex. Below the triangle, 'MT\_TCP' points up from the bottom vertex. At the very bottom, the text 'G.8121-Y.1381(18)\_F9-43' is present. + +Figure 9-43 – MTDe\_TT\_So symbol + +###### Interfaces + +The interfaces are described in Table 9-18. + +Table 9-18 – MTDe\_TT\_So interfaces + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTDe_AP:
MTDe_AI_D
MTDe_AI_oPHB
MTDe_AI_iPHB

MTDe_RP:
MTDe_RI_OAM_Info(D,CoS,DP)
MTDe_RI_CI

MTDe_TT_So_MP:
MTDe_TT_So_MI_GAL_Enable
MTDe_TT_So_MI_TTLVALUE
MTDe_TT_So_MI_CV_OAM_Tool
MTDe_TT_So_MI_CV_Series () [Note]

MTDe_TT_So_MI_1TH_OAM_Tool
MTDe_TT_So_MI_1TH_Start
(CoS,Length,Period)
MTDe_TT_So_MI_1TH_Terminate

MTDe_TT_So_MI_LMo_OAM_Tool
MTDe_TT_So_MI_LMo_Start(CoS,Period) [1...M LMo ]
MTDe_TT_So_MI_LMo_Intermediate_Request[1...M LMo ]
MTDe_FT_So_MI_LMo_Terminate[1...M LMo ] | MT_TCP:
MT_CI_D
MT_CI_oPHB
MT_CI_iPHB

MTDe_TT_So_MP:

MTDe_TT_So_MI_CV_Series_Result[Note]
MTDe_TT_So_MI_1TH_Result(Sent)
MTDe_TT_So_MI_LMo_Result(N_TF,N_LF,F_TF,F_LF)[1...M LMo ]
MTDe_TT_So_MI_DMo_Result(count,B_FD[],F_FD[],N_FD())[1...M DMo ]
MTDe_TT_So_MI_SLo_Result(N_TF,N_LF,F_TF,F_LF)[1...M SLo ] | + +**Table 9-18 – MTDe\_TT\_So interfaces** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| MTDe_TT_So_MI_DMo_OAM_Tool
MTDe_TT_So_MI_DMo_Start
(CoS,Test_ID,Length,Period)[1...M DMo ]
MTDe_TT_So_MI_DMo_Intermediate_Request[1...M LMo ]
MTDe_TT_So_MI_DMo_Terminate[1...M DMo ]

MTDe_TT_So_MI_1DMo_OAM_Tool
MTDe_TT_So_MI_1DMo_Start
(CoS,Test_ID,Length,Period)[1...M 1DMo ]
MTDe_TT_So_MI_1DMo_Terminate[1...M 1DMo ]

MTDe_TT_So_MI_SLo_OAM_Tool
MTDe_TT_So_MI_SLo_Start
(CoS,Test_ID,Length,Period)[1...M SLo ]
MTDe_TT_So_MI_SLo_Intermediate_Request[1...M LMo ]
MTDe_TT_So_MI_SLo_Terminate[1...M SLo ]
MTDe_TT_So_MI_Admin_State
MTDe_TT_So_MI_Lock_Instruct_Enable

MTDe_TT_So_MI_DP_Loopback_Enable

MTDe_TT_So_TP:
MTDe_TT_So_TI_TimeStamp1 | | +| NOTE: The parameters for MI_CV_Series and MI_CV_Series_Result are not within the scope of this Recommendation. | | + +##### **Processes** + +The processes associated with the MTDe\_TT\_So function are as depicted in Figure 9-44. + +![Diagram of MTDe_TT_So process showing internal components and management interfaces.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +The diagram illustrates the internal architecture of the MTDe\_TT\_So process. At the top, external inputs AI\_D and AI\_iPHB/oPHB enter a 'Counter' block. The 'Counter' block is connected to a large 'MEP on-demand G-Ach insertion' block. This block is further connected to a 'Dataplane loopback source' block at the bottom. Between the 'MEP on-demand G-Ach insertion' and 'Dataplane loopback source' blocks are two vertical blocks: 'On-demand OAM PDU generation' and 'On-demand OAM source control'. These blocks exchange data with the 'MEP on-demand G-Ach insertion' and 'Dataplane loopback source' blocks via arrows labeled PDU, TTL, Channel type, and PHB. The 'On-demand OAM PDU generation' block also has an arrow labeled TxFCf pointing to the 'MEP on-demand G-Ach insertion' block. At the bottom, the 'Dataplane loopback source' block outputs CI\_D, CI\_oPHB, and CI\_iPHB, which are then processed by the 'MT\_TCP' block. + +Management interfaces are listed on the right side of the diagram, categorized into four groups: + +- MT\_RP**: + - RI\_OAM\_Info(D, CoS, DP) + - RI\_LMRo(TxF Cf, RxF Cf, TxF Cb, RxF Cb, CoS) + - RI\_DMRo(TxTimeStampf, RxTimeStampf, TxTimeStampb, RxTimeb, CoS, TestID) + - RI\_SLRo(TxF Cf, TxF Cb, rTestID) + - RI\_CI(D, iPHB, oPHB) +- MT\_TT\_So\_MP**: + - MI\_CV\_Series\_Result() + - MI\_ITH\_Result(Sent) + - MI\_LMo\_Result(N\_TF, N\_LF, F\_TF, F\_LF)[1...M\_LMo] + - MI\_DMo\_Result(count, B\_FD[], F\_FD[], N\_FD[][1...M\_DMo]) + - MI\_SLo\_Result(N\_TF, N\_LF, F\_TF, F\_LF)[1...M\_SLo] + - MI\_GAL\_Enable + - MI\_TTLVALUE +- MT\_TT\_So\_TP**: + - MI\_CV\_OAM\_Tool + - MI\_CV\_Series() + - MI\_ITH\_OAM\_Tool + - MI\_ITH\_Start(CoS, Length, Period) + - MI\_ITH\_Terminate + - MI\_LMo\_OAM\_Tool + - MI\_LMo\_Start(P, Period)[1...M\_LMo] + - MI\_LMo\_Intermediate\_Request[1...M\_LMo] + - MI\_LMo\_Terminate[1...M\_LMo] + - MI\_DMo\_OAM\_Tool + - MI\_DMo\_Start(CoS, Test\_ID, Length, Period)[1...M\_DMo] + - MI\_DMo\_Intermediate\_Request[1...M\_DMo] + - MI\_DMo\_Terminate[1...M\_DMo] + - MI\_IDMo\_OAM\_Tool + - MI\_IDMo\_Start(CoS, Test\_ID, Length, Period)[1...M\_IDMo] + - MI\_IDMo\_Terminate[1...M\_IDMo] + - MI\_SLo\_OAM\_Tool + - MI\_SLo\_Start(CoS, Test\_ID, Length, Period)[1...M\_SLo] + - MI\_SLo\_Intermediate\_Request[1...M\_SLo] + - MI\_SLo\_Terminate[1...M\_SLo] + - MI\_DP\_Loopback\_Enable + - TI\_TimeStamp1 + +G.8121-Y.1381(18)\_F9-44 + +Diagram of MTDe\_TT\_So process showing internal components and management interfaces. + +Figure 9-44 – MTDe\_TT\_So process + +**MEP on-demand G-Ach insertion:** See clause 8.1.2. + +**OAM PDU generation:** See clause 8.8. + +**On-demand OAM source control:** See clause 8.8. + +**Dataplane loopback source process:** See clause 8.9.2. + +**Counter:** This process is used to count packets for on-demand loss measurements. The location of the counter process is shown for illustration only. The exact set of packets to be counted is outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.1.1.2 MT diagnostic trail termination sink function for MEPs (MTDe\_TT\_Sk) + +###### Symbol + +The MTDe\_TT\_Sk function symbol is shown in Figure 9-45. + +![Figure 9-45 – MTDe_TT_Sk symbol. The diagram shows a central triangle labeled 'MTDe'. Above it is an upward-pointing arrow labeled 'MTDe_AP'. Below it is a downward-pointing arrow labeled 'MT_TCP'. To the left is a leftward-pointing arrow labeled 'MTDe_TT_Sk_MP'. To the right is a rightward-pointing arrow labeled 'MTDe_RP'. Below the diagram is the text 'G.8121-Y.1381(18)_F9-45'.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +Figure 9-45 – MTDe\_TT\_Sk symbol. The diagram shows a central triangle labeled 'MTDe'. Above it is an upward-pointing arrow labeled 'MTDe\_AP'. Below it is a downward-pointing arrow labeled 'MT\_TCP'. To the left is a leftward-pointing arrow labeled 'MTDe\_TT\_Sk\_MP'. To the right is a rightward-pointing arrow labeled 'MTDe\_RP'. Below the diagram is the text 'G.8121-Y.1381(18)\_F9-45'. + +Figure 9-45 – MTDe\_TT\_Sk symbol + +###### Interfaces + +The interfaces are described in Table 9-19. + +Table 9-19 – MTDe\_TT\_Sk interfaces + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MT_TCP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack

MTDe_TT_Sk_MP:
MTDe_TT_Sk_MI_GAL_Enable
MTDe_TT_Sk_MI_CV_OAM_Tool
MTDe_TT_Sk_MI_1TH_OAM_Tool
MTDe_TT_Sk_MI_1TH_Start
MTDe_TT_Sk_MI_1TH_Terminate
MTDe_TT_Sk_MI_LMo_OAM_Tool
MTDe_TT_Sk_MI_DMo_OAM_Tool
MTDe_TT_Sk_MI_1DMo_OAM_Tool
MTDe_TT_Sk_MI_1DMo_Start(Test_ID, CoS)[1...M 1DMo ]
MTDe_TT_Sk_MI_1DMo_Intermediate_Request[1..
..M LMo ]
MTDe_TT_Sk_MI_1DMo_Terminate[1...M 1DMo ]
MTDe_TT_Sk_MI_SLo_OAM_Tool
MTDe_TT_Sk_MI_DP_Loopback_Enable
MTDe_TP:
MTDe_TT_Sk_TI_TimeStamp1 | MTDe_AP:
MTDe_AI_D
MTDe_AI_oPHB
MTDe_AI_iPHB
MTDe_AI_LStack

MTDe_RP:
MTDe_RI_OAM_Info(D,CoS,DP)
MTDe_RI_CI

MTDe_TT_Sk_MP:
MTDe_TT_Sk_MI_1TH_Result(REC,CRC,BER,O
O)
MTDe_TT_Sk_MI_1DMo_Result(count,N_FD[])[1..
..M DMo ]]
MTDe_TT_Sk_MI_Admin_State_Request | + +###### Processes + +The processes associated with the MTDe\_TT\_Sk function are as depicted in Figure 9-46. + +![Figure 9-46 – MTDe_TT_Sk process diagram. This block diagram illustrates the internal components and data flows of the MTDe_TT_Sk process. At the top, the MTDe_AP interface provides AI_iPHB, AI_oPHB, AI_D, and AI_LStack signals. At the bottom, the MT_TCP interface provides CI_iPHB, CI_oPHB, CI_D, and CI_LStack signals. The central area contains three main functional blocks: 'On-demand OAM sink control', 'OAM PDU reception', and 'MEP on-demand G-ACh extraction'. The 'On-demand OAM sink control' block receives various RI and MI messages from the MT_TT_Sk_RP, MTDe_TT_Sk_MP, and MT_TT_Sk_TP interfaces and interacts with the 'OAM PDU reception' block. The 'OAM PDU reception' block receives PDU, PHB, and Channel type signals from the 'MEP on-demand G-ACh extraction' block and sends TxFCf signals to a 'Counter' block. The 'Counter' block sends non-OAM signals to the 'MEP on-demand G-ACh extraction' block. The 'MEP on-demand G-ACh extraction' block also receives signals from the 'Dataplane Loopback sink' block. The 'Dataplane Loopback sink' block receives MI_GAL_Enable and TI_TimeStamp1 signals from the MT_TT_Sk_TP interface and sends signals to the 'MEP on-demand G-ACh extraction' block.](8a781a0a8c956859f63a1ca7f2bb1644_img.jpg) + +Figure 9-46 – MTDe\_TT\_Sk process diagram. This block diagram illustrates the internal components and data flows of the MTDe\_TT\_Sk process. At the top, the MTDe\_AP interface provides AI\_iPHB, AI\_oPHB, AI\_D, and AI\_LStack signals. At the bottom, the MT\_TCP interface provides CI\_iPHB, CI\_oPHB, CI\_D, and CI\_LStack signals. The central area contains three main functional blocks: 'On-demand OAM sink control', 'OAM PDU reception', and 'MEP on-demand G-ACh extraction'. The 'On-demand OAM sink control' block receives various RI and MI messages from the MT\_TT\_Sk\_RP, MTDe\_TT\_Sk\_MP, and MT\_TT\_Sk\_TP interfaces and interacts with the 'OAM PDU reception' block. The 'OAM PDU reception' block receives PDU, PHB, and Channel type signals from the 'MEP on-demand G-ACh extraction' block and sends TxFCf signals to a 'Counter' block. The 'Counter' block sends non-OAM signals to the 'MEP on-demand G-ACh extraction' block. The 'MEP on-demand G-ACh extraction' block also receives signals from the 'Dataplane Loopback sink' block. The 'Dataplane Loopback sink' block receives MI\_GAL\_Enable and TI\_TimeStamp1 signals from the MT\_TT\_Sk\_TP interface and sends signals to the 'MEP on-demand G-ACh extraction' block. + +Figure 9-46 – MTDe\_TT\_Sk process + +**MEP On-demand G-ACh extraction:** See clause 8.1. The process of CI\_D is made according to the following rule: + +``` +if ( ((MI_GAL_Enable && MT-label(D) == GAL) || + (!MI_GAL_Enable && 1stNibble(D) == 0b0001)) && + (Packet_Type(D) == On-demand_OAM) ) + forward to G-ACh port +} else { + forward to data port +} +``` + +NOTE – MT-label(D) and 1stNibble(D) are functions which return, respectively, the Label field at the top of the stack within the MPLS payload, the first nibble of the MPLS payload as defined in Figure 6-3 of [ITU-T G.8110.1]. + +These fields are used to identify G-ACh packets as described in clause 4.2.1 of [IETF RFC 5586]. + +Packet\_Type(D) is a protocol-specific function that determines whether the traffic unit contains an on-demand OAM packet. + +**OAM PDU reception:** See clause 8.8 + +**On-demand OAM sink control:** See clause 8.8 + +**Dataplane loopback sink process:** See clause 8.9.1 + +**Counter:** This process is used to count packets for on-demand loss measurements. The location of the counter process is shown for illustration only. The exact set of packets to be counted is outside the scope of this Recommendation. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.4.1.2 MTDe to MT adaptation functions (MTDe/MT\_A) + +##### 9.4.1.2.1 MTDe to MT adaptation source function (MTDe/MT\_A\_So) + +This function consists of input MT\_CI and output MTDe\_AI. The function inside is empty, i.e., the input signals are simply passed to the output. + +##### 9.4.1.2.2 MTDe to MT adaptation sink function (MTDe/MT\_A\_Sk) + +This function consists of input MTDe\_AI and output MT\_CI. The function inside is empty, i.e., the input signals are simply passed to the output. + +### 9.4.2 MT diagnostic functions for MIPs (MTDi) + +#### 9.4.2.1 MT diagnostic trail termination functions for MIPs (MTDi\_TT) + +##### 9.4.2.1.1 MT diagnostic trail termination source function for MIPs (MTDi\_TT\_So) + +###### Symbol + +The MTDi\_TT\_So function symbol is shown in Figure 9-47 + +![Figure 9-47 – MTDi_TT_So symbol. The diagram shows a central triangle labeled 'MTDi'. Above the triangle is an input interface 'MTDi_AP' with an arrow pointing down to the triangle. To the left of the triangle is an input interface 'MTDi_TT_So_MP' with an arrow pointing right to the triangle. To the right of the triangle is an input interface 'MTDi_RP' with an arrow pointing left to the triangle. Below the triangle is an output interface 'MT_TCP' with an arrow pointing down from the triangle. Below the diagram is the text 'G.8121-Y.1381(18)_F9-47'.](b22a2b17c5f35e4706033e34ab0f3e9a_img.jpg) + +G.8121-Y.1381(18)\_F9-47 + +Figure 9-47 – MTDi\_TT\_So symbol. The diagram shows a central triangle labeled 'MTDi'. Above the triangle is an input interface 'MTDi\_AP' with an arrow pointing down to the triangle. To the left of the triangle is an input interface 'MTDi\_TT\_So\_MP' with an arrow pointing right to the triangle. To the right of the triangle is an input interface 'MTDi\_RP' with an arrow pointing left to the triangle. Below the triangle is an output interface 'MT\_TCP' with an arrow pointing down from the triangle. Below the diagram is the text 'G.8121-Y.1381(18)\_F9-47'. + +**Figure 9-47 – MTDi\_TT\_So symbol** + +###### Interfaces + +The interfaces are described in Table 9-20. + +**Table 9-20 – MTDi\_TT\_So interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| MTDi_AP
MTDi_AI_D
MTDi_AI_iPHB
MTDi_AI_oPHB
MTDi_AI_Lstack

MTDi_RP
MTDi_RI_OAM_Info (D, CoS, DP)
MTDi_RI_CI

MTDi_TT_So_MP
MTDi_TT_So_MI_GAL_Enable
MTDi_TT_So_MI_TTLVALUE
MTDi_TT_So_MI_MIP_ID
MTDi_TT_So_MI_CV_OAM_Tool
MTDi_TT_So_MI_DP_Loopback_Enable | MT_TCP
MT_CI_D,
MT_CI_iPHB,
MT_CI_oPHB,
MT_CI_LStack | + +###### **Processes** + +The processes associated with the MTDi\_TT\_So function are as depicted in Figure 9-48. + +![Figure 9-48 – MTDi_TT_So Process diagram showing internal components like On-demand OAM source control, On-demand OAM PDU generation, MIP on-demand OAM G-ACh insertion, and Data-plane loopback source with their respective inputs and outputs.](c7e27041e661260fd0c8e89c763bb32e_img.jpg) + +The diagram illustrates the internal architecture of the MTDi\_TT\_So process. It features four main functional blocks: 'On-demand OAM source control', 'On-demand OAM PDU generation', 'MIP on-demand OAM G-ACh insertion', and 'Data-plane loopback source'. Inputs from the MTDi\_TT\_So\_MP interface (MI\_GAL\_Enable, MI\_TTLVALUE, MI\_MIP\_ID, MI\_CV\_OAM\_Tool, RI\_OAM\_Info(D, P, DP), RI\_CI(D, iPHB, oPHB), and MI\_Dataplane\_Loopback\_Enable) are distributed to these blocks. The 'On-demand OAM source control' and 'On-demand OAM PDU generation' blocks feed into the 'MIP on-demand OAM G-ACh insertion' block, which also receives 'Data' from the MTDi\_AP interface. The 'MIP on-demand OAM G-ACh insertion' block outputs PDU, TTL, PHB, and Channel type information. Finally, the 'Data-plane loopback source' block outputs to the MT\_TCP interface (CI\_D/iPHB/oPHB and CI\_LStack). + +Figure 9-48 – MTDi\_TT\_So Process diagram showing internal components like On-demand OAM source control, On-demand OAM PDU generation, MIP on-demand OAM G-ACh insertion, and Data-plane loopback source with their respective inputs and outputs. + +**Figure 9-48 – MTDi\_TT\_So Process** + +**MIP On-demand OAM G-ACh insertion:** The MIP OAM insertion process inserts OAM traffic units that are generated in the MTDi\_TT\_So process into the stream of traffic units. + +The GAL is used or not according to the MI\_GAL\_Enable parameter. + +**OAM PDU generation:** See clause 8.8. + +**On-demand OAM source control:** See clause 8.8. + +**Dataplane loopback source process:** See clause 8.9.2 + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.2.1.2 MT diagnostic trail termination sink function for MIPs (MTDi\_TT\_Sk) + +###### Symbol + +The MTDi\_TT\_Sk function symbol is shown in Figure 9-49. + +![Figure 9-49 – MTDi_TT_Sk symbol. The diagram shows a central triangle labeled 'MTDi'. Above it, an arrow points up to 'MTDi_AP'. Below it, an arrow points up from 'MT_TCP'. To the left, an arrow points right into the triangle from 'MTDi_TT_So_MP'. To the right, an arrow points left into the triangle from 'MTDi_RP'. Below the triangle, the text 'G.8121-Y.1381(18)_F9-49' is present.](61a49f3179b455e4d35242fc3d187a29_img.jpg) + +G.8121-Y.1381(18)\_F9-49 + +Figure 9-49 – MTDi\_TT\_Sk symbol. The diagram shows a central triangle labeled 'MTDi'. Above it, an arrow points up to 'MTDi\_AP'. Below it, an arrow points up from 'MT\_TCP'. To the left, an arrow points right into the triangle from 'MTDi\_TT\_So\_MP'. To the right, an arrow points left into the triangle from 'MTDi\_RP'. Below the triangle, the text 'G.8121-Y.1381(18)\_F9-49' is present. + +**Figure 9-49 – MTDi\_TT\_Sk symbol** + +###### Interfaces + +The interfaces are described in Table 9-21. + +**Table 9-21 – MTDi\_TT\_Sk interfaces** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| MT_TCP
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack

MTDi_TT_Sk_MP
MTDi_TT_Sk_MI_GAL_Enable
MTDi_TT_Sk_MI_MIP_ID
MTDi_TT_Sk_MI_CV_OAM_Tool
MTDi_TT_Sk_MI_DP_Loopback_Enable | MTDi_AP
MTDi_AI_D
MTDi_AI_iPHB
MTDi_AI_oPHB
MTDi_AI_LStack

MTDi_RP
MTDi_RI_OAM_Info (D, CoS, DP)
MTDi_RI_CI | + +###### Processes + +The processes associated with the MTDi\_TT\_Sk function are as depicted in Figure 9-50. + +![Figure 9-50 – MTDi_TT_Sk Process diagram. The diagram shows a central processing block labeled 'MT_TCP' containing three main components: 'On-demand OAM sink control', 'OAM PDU reception', and 'Dataplane loopback sink'. The 'On-demand OAM sink control' receives inputs 'MI_GAL_Enable', 'MI_MIP_ID', and 'MI_CV_OAM_Tool' and sends output 'RI_OAM_Info(D, P, DP)'. The 'OAM PDU reception' receives 'PDU', 'PHB', and 'Channel type' from the 'Dataplane loopback sink' and sends output to the 'On-demand OAM sink control'. The 'Dataplane loopback sink' receives 'RI_CI(D, iPHB, oPHB)' and 'MI_Dataplane_Loopback_Enable' and sends output to the 'OAM PDU reception'. Above the 'MT_TCP' block is a large box labeled 'AI_D/iPHB/oPHB/LStack' containing 'Data', 'MIP On-demand OAM G-Ach extraction', and 'OAM'. Below the 'MT_TCP' block is a box labeled 'CI_D/iPHB/oPHB/LStack'. Arrows indicate data flow between the 'MT_TCP' components and the 'AI_D/iPHB/oPHB/LStack' and 'CI_D/iPHB/oPHB/LStack' boxes. The diagram is labeled 'G.8121-Y.1381(18)_F9-50'.](ca86f53f9735fe98b6c6003d1b759f64_img.jpg) + +Figure 9-50 – MTDi\_TT\_Sk Process diagram. The diagram shows a central processing block labeled 'MT\_TCP' containing three main components: 'On-demand OAM sink control', 'OAM PDU reception', and 'Dataplane loopback sink'. The 'On-demand OAM sink control' receives inputs 'MI\_GAL\_Enable', 'MI\_MIP\_ID', and 'MI\_CV\_OAM\_Tool' and sends output 'RI\_OAM\_Info(D, P, DP)'. The 'OAM PDU reception' receives 'PDU', 'PHB', and 'Channel type' from the 'Dataplane loopback sink' and sends output to the 'On-demand OAM sink control'. The 'Dataplane loopback sink' receives 'RI\_CI(D, iPHB, oPHB)' and 'MI\_Dataplane\_Loopback\_Enable' and sends output to the 'OAM PDU reception'. Above the 'MT\_TCP' block is a large box labeled 'AI\_D/iPHB/oPHB/LStack' containing 'Data', 'MIP On-demand OAM G-Ach extraction', and 'OAM'. Below the 'MT\_TCP' block is a box labeled 'CI\_D/iPHB/oPHB/LStack'. Arrows indicate data flow between the 'MT\_TCP' components and the 'AI\_D/iPHB/oPHB/LStack' and 'CI\_D/iPHB/oPHB/LStack' boxes. The diagram is labeled 'G.8121-Y.1381(18)\_F9-50'. + +**Figure 9-50 – MTDi\_TT\_Sk Process** + +**MIP On-demand OAM G-ACh extraction:** The MIP OAM extraction process classifies the OAM traffic units targeted to the MIP to which this MTDi\_TT belongs, as configured by MI\_MIP\_ID, and delivers them to the On-demand OAM PDU reception process. All the other traffic units are delivered to MTDi\_AP. The process is made according to the following rule: + +``` +if ( (TTL(D) == 0) && + ((MI_GAL_Enable && MT-label(D) == GAL) || + (!MI_GAL_Enable && 1stNibble(D) == 0b0001)) && + (Packet_Type(D) == OnDemandForThisMIP) ) +{ + forward to G-Ach port +} else { + forward to data port +} +``` + +NOTE – For LSP and pseudowire MIPs, MT-label(D), 1stNibble(D) and TTL(D) are functions which return, respectively, the Label field at the top of the stack within the MPLS payload, the first nibble of the MPLS payload and the TTL field as defined in Figure 6-3 of [ITU-T G.8110.1]. + +These fields are used to identify G-ACh packets as described in clause 4.2.1 of [IETF RFC 5586]. + +Packet\_Type(D) is a protocol-specific function that determines whether the traffic unit contains an on-demand OAM packet to be processed by this MIP. + +**OAM PDU reception:** See clause 8.8. + +**On-demand OAM sink control:** See clause 8.8. + +**Dataplane loopback sink process:** See clause 8.9.1 + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.4.2.2 MTDi to MT adaptation functions (MTDi/MT\_A) + +The MTDi/MT adaptation function is an empty function; it is included to satisfy the modelling rules. + +The bidirectional MTDi/MT adaptation function is performed by a co-located pair of MTDi/MT adaptation source (MTDi/MT\_A\_So) and sink (MTDi/MT\_A\_Sk) functions. + +##### 9.4.2.2.1 MTDi to MT adaptation source functions (MTDi/MT\_A\_So) + +###### Symbol + +The MTDi/MT\_A\_So function symbol is shown in Figure 9-51. + +![Figure 9-51: MTDi/MT_A_So symbol diagram. It shows a trapezoidal block labeled 'MTDi/MT'. An arrow labeled 'MT_CP' points into the top of the block, and an arrow labeled 'MTDi_AP' points out from the bottom. The text 'G.8121-Y1381(18)_F9-51' is at the bottom right.](09036266c6dba47efb2613ceaebe2b19_img.jpg) + +Figure 9-51: MTDi/MT\_A\_So symbol diagram. It shows a trapezoidal block labeled 'MTDi/MT'. An arrow labeled 'MT\_CP' points into the top of the block, and an arrow labeled 'MTDi\_AP' points out from the bottom. The text 'G.8121-Y1381(18)\_F9-51' is at the bottom right. + +Figure 9-51 – MTDi/MT\_A\_So symbol + +###### Interfaces + +The interfaces are described in Table 9-22. + +Table 9-22 – MTDi/MT\_A\_So interfaces + +| Input(s) | Output(s) | +|----------------------------------------------------------------------|--------------------------------------------------------------------------------| +| MT_CP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack | MTDi_AP:
MTDi_AI_D
MTDi_AI_iPHB
MTDi_AI_oPHB
MTDi_AI_LStack | + +###### Processes + +The processes associated with the MTDi/MT\_A\_So function are as depicted in Figure 9-52. + +![Figure 9-52: MTDi/MT_A_So process diagram. It shows a horizontal bar with four downward-pointing arrows. Above the arrows are labels: CI_D, CI_iPHB, CI_oPHB, and CI_LStack. Below the arrows are labels: AI_D, AI_iPHB, AI_oPHB, and AI_LStack. The text 'G.8121-Y.1381(18)_F9-52' is at the bottom right.](66decd3c38c5f918f528096090219e15_img.jpg) + +Figure 9-52: MTDi/MT\_A\_So process diagram. It shows a horizontal bar with four downward-pointing arrows. Above the arrows are labels: CI\_D, CI\_iPHB, CI\_oPHB, and CI\_LStack. Below the arrows are labels: AI\_D, AI\_iPHB, AI\_oPHB, and AI\_LStack. The text 'G.8121-Y.1381(18)\_F9-52' is at the bottom right. + +Figure 9-52 – MTDi/MT\_A\_So process + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.2.2.2 MTDi to MT adaptation sink function (MTDi/MT\_A\_Sk) + +###### Symbol + +The MTDi/MT\_A\_Sk function symbol is shown in Figure 9-53. + +![Figure 9-53: MTDi/MT_A_Sk symbol diagram. A central trapezoidal block labeled 'MTDi/MT' has three input arrows from the left and bottom, and one output arrow pointing upwards. The left input is labeled 'MTDi/MT_Sk_MP', the bottom input is 'MTDi_AP', and the output is 'MTDi_CP'. A small text label 'G.8121-Y.1381(18)_F9-53' is at the bottom right.](b3335932702b8668e62791e9fd12c9ff_img.jpg) + +Figure 9-53: MTDi/MT\_A\_Sk symbol diagram. A central trapezoidal block labeled 'MTDi/MT' has three input arrows from the left and bottom, and one output arrow pointing upwards. The left input is labeled 'MTDi/MT\_Sk\_MP', the bottom input is 'MTDi\_AP', and the output is 'MTDi\_CP'. A small text label 'G.8121-Y.1381(18)\_F9-53' is at the bottom right. + +**Figure 9-53 – MTDi/MT\_A\_Sk symbol** + +###### **Interfaces** + +The MTDi/MT\_A\_Sk interfaces are described in Table 9-23. + +**Table 9-23 – MTDi/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| MTDi_AP:
MTDi_AI_D
MTDi_AI_iPHB
MTDi_AI_oPHB
MTDi_AI_LStack

MTDi/MT_Sk_MP:
MTDi/MT_A_MI_DS_MP_Type | MT_CP:
MT_CI_D
MT_CI_iPHB
MT_CI_oPHB
MT_CI_LStack | + +###### **Processes** + +The processes associated with the MTDi/MT\_A\_Sk function are as depicted in Figure 9-54. + +![Figure 9-54: MTDi/MT_A_Sk process diagram. A rectangular block labeled 'TTL check' is shown. An input arrow labeled 'MI_DS_MP_Type' points to it from the left. Above the block, four arrows point upwards labeled 'CI_D', 'CI_iPHB', 'CI_oPHB', and 'CI_LStack'. Below the block, four arrows point downwards labeled 'AI_D', 'AI_iPHB', 'AI_oPHB', and 'AI_LStack'. A small text label 'G.8121-Y.1381(18)_F9-54' is at the bottom right.](986e77e2df3c318680a569774888f4aa_img.jpg) + +Figure 9-54: MTDi/MT\_A\_Sk process diagram. A rectangular block labeled 'TTL check' is shown. An input arrow labeled 'MI\_DS\_MP\_Type' points to it from the left. Above the block, four arrows point upwards labeled 'CI\_D', 'CI\_iPHB', 'CI\_oPHB', and 'CI\_LStack'. Below the block, four arrows point downwards labeled 'AI\_D', 'AI\_iPHB', 'AI\_oPHB', and 'AI\_LStack'. A small text label 'G.8121-Y.1381(18)\_F9-54' is at the bottom right. + +**Figure 9-54 – MTDi/MT\_A\_Sk process** + +###### *TTL check process:* + +For LSP and pseudowire MIPs, the TTL check process examines the TTL field in the MTDi\_AI\_D traffic unit. TTL check process drops all MPLS-TP packets with TTL = 0 by default (MI\_DS\_MP\_Type set to none). + +When MI\_DS\_MP\_Type is set to MIP, TTL check process drops only user data MPLS-TP packets with TTL = 0 while OAM packets with TTL = 0 are not dropped in this process and are forwarded. + +When the MI\_DS\_MP\_Type is set to MEP, TTL check process does not block any MPLS-TP packet with TTL = 0: all MPLS-TP packets with TTL = 0 are forwarded. + +NOTE – The MI\_DS\_MP\_Type parameter should be properly configured by the EMF on the basis of the MPLS-TP connection configuration within the node and not exposed to the operator as a configuration parameter of the equipment management interface. Examples of MI\_DS\_MP\_Type configuration are described in Appendix I. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 9.5 MPLS-TP 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 MT termination, adaptation and diagnostic atomic functions described in clauses 9.2, 9.3 and 9.4 respectively. + +### 9.5.1 MPLS-TP NCM MEP function + +An MPLS-TP network connection monitoring (NCM) MEP function is capable of originating, filtering and terminating proactive MPLS-TP OAM signals and originating, responding to and terminating diagnostic MPLS-TP OAM signals at the MPLS-TP layer. The NCM MEP is composed of MT\_TT, MTDe/MT\_A and MTDe\_TT atomic functions. This MEP is located at the MPLS-TP layer boundary and connected with MT/client\_A or MT/MT\_A. + +Figure 9-55 illustrates MT NCM MEP compound functions. + +![Diagram illustrating MT NCM MEP compound functions. The left side shows a simplified symbol with two horizontal lines inside an inverted triangle. The right side shows a detailed view of the compound functions: MT, MTDe/MT, and MTDe, stacked vertically within a larger triangle. The MT function is at the top, connected to an external node. The MTDe/MT function is in the middle, and the MTDe function is at the bottom, connected to another external node. The diagram is labeled G.8121-Y.1381(18)_F55.](0f5c79ad7c317f14f16aa5a2c036e406_img.jpg) + +G.8121-Y.1381(18)\_F55 + +Diagram illustrating MT NCM MEP compound functions. The left side shows a simplified symbol with two horizontal lines inside an inverted triangle. The right side shows a detailed view of the compound functions: MT, MTDe/MT, and MTDe, stacked vertically within a larger triangle. The MT function is at the top, connected to an external node. The MTDe/MT function is in the middle, and the MTDe function is at the bottom, connected to another external node. The diagram is labeled G.8121-Y.1381(18)\_F55. + +**Figure 9-55 – MT NCM MEP compound functions** + +### 9.5.2 MPLS-TP TCM MEP function + +Tandem connection monitoring (TCM) can be supported by the instantiation of sub-path maintenance entity (SPME), as described in [IETF RFC 6371], that has a 1:1 relationship with the monitored connection. + +A MPLS-TP TCM MEP function is capable of originating, filtering and terminating proactive MPLS-TP OAM signals and originating, responding to and terminating diagnostic MPLS-TP OAM signals at the MPLS-TP sub-layer. The TCM MEP is composed of MT\_TT, MTDe/MT\_A and MTDe\_TT atomic functions. + +Figure 9-56 illustrates MT TCM MEP compound functions. + +![Diagram of MT TCM MEP compound functions](7c3ecd751b69a0fc7b08633a84822f42_img.jpg) + +The diagram illustrates the expansion of an MT TCM MEP compound function. On the left, a single inverted triangle represents the compound function, with a terminal circle at its top vertex and another at its bottom vertex. An arrow points to the right, where the function is shown as a stack of four nested triangles. From top to bottom, these are labeled: MT/MT, MT, MTDe/MT, and MTDe. Each of these nested triangles has its own top and bottom terminal circles. The label G.8121-Y.1381(18)\_F56 is located at the bottom right. + +Diagram of MT TCM MEP compound functions + +**Figure 9-56 – MT TCM MEP compound functions** + +### 9.5.3 MT MIP function + +An MT MIP function is capable of responding to on-demand MT OAM signals at one of the MPLS-TP (sub-)layers in both directions. The MIP combines two back-to-back half-MIP functions. It consists of two pairs of MTDi/MT\_A and MTDi\_TT atomic functions, each facing opposite directions. + +Figure 9-57 illustrates MT MIP compound functions. + +![Diagram of MT MIP compound functions](6a91a6df50795695b71693ad679a4f31_img.jpg) + +The diagram illustrates the expansion of an MT MIP compound function. On the left, a diamond shape represents the compound function, with a terminal circle at its top and bottom vertices. An arrow points to the right, where the function is shown as a stack of four nested triangles. From top to bottom, these are labeled: MTDi, MTDi/MT, MTDi/MT, and MTDi. Each of these nested triangles has its own top and bottom terminal circles. The label G.8121-Y.1381(18)\_F57 is located at the bottom right. + +Diagram of MT MIP compound functions + +**Figure 9-57 – MT MIP compound functions** + +### 9.5.4 MT half MIP function + +An MPLS-TP half MIP function is capable of responding to on-demand MPLS-TP OAM signals at one of the MPLS-TP sublayers in a single direction. The half MIP is composed of a pair of MTDi/MT\_A and MTDi\_TT atomic functions. + +Figure 9-58 illustrates MT half MIP compound functions. + +![Diagram of MT half MIP compound functions. It shows a transition from a simple trapezoidal symbol to a more complex one. The complex symbol is a trapezoid containing two stacked blue boxes labeled 'MTDi/MT' and 'MTDi'. Below the diagram is the text 'G.8121-Y.1381(18)_F58'.](48adb97a6a4a14b039450192f25cc1e0_img.jpg) + +Diagram of MT half MIP compound functions. It shows a transition from a simple trapezoidal symbol to a more complex one. The complex symbol is a trapezoid containing two stacked blue boxes labeled 'MTDi/MT' and 'MTDi'. Below the diagram is the text 'G.8121-Y.1381(18)\_F58'. + +**Figure 9-58 – MT half MIP compound functions** + +# 10 MPLS-TP to Non-MPLS-TP client adaptation functions + +## 10.1 MPLS-TP to ETH adaptation function (MT/ETH\_A) + +The MPLS-TP to ETH adaptation functions that include CSF processes are specified in [ITU-T G.8121.1] and [ITU-T G.8121.2]. + +### 10.1.1 MPLS-TP to ETH adaptation source function (MT/ETH\_A\_So) + +This function maps the ETH\_CI information for transport in a MT\_AI signal. + +The information flow and processing of the MT/ETH\_A\_So function is defined with reference to Figure 10-1. + +##### Symbol + +![Diagram of the MT/ETH_A_So function. A yellow trapezoidal symbol labeled 'MT/ETH_A_So' has three interfaces: 'ETH_CI' entering from the top, 'MT/ETH_A_So_MI' entering from the left, and 'MT_AI' exiting from the bottom. Below the diagram is the text 'G.8121-Y.1381(13)_F10-1'.](ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg) + +Diagram of the MT/ETH\_A\_So function. A yellow trapezoidal symbol labeled 'MT/ETH\_A\_So' has three interfaces: 'ETH\_CI' entering from the top, 'MT/ETH\_A\_So\_MI' entering from the left, and 'MT\_AI' exiting from the bottom. Below the diagram is the text 'G.8121-Y.1381(13)\_F10-1'. + +**Figure 10-1 – MT/ETH\_A\_So function** + +#### Interfaces + +The MT/ETH\_A\_So interfaces are described in Table 10-1. + +**Table 10-1 – MT/ETH\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| ETH_FP:
ETH_CI_Data
ETH_CI_P
ETH_CI_DE
MT/ETH_A_So_MP:
MT/ETH_A_So_MI_AdminState
MT/ETH_A_So_MI_FCSEnable
MT/ETH_A_So_MI_CWEnable | MT_AP:
MT_AI_Data
MT_AI_PHB | + +**Table 10-1 – MT/ETH\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| MT/ETH_A_So_MI_SQUse
MT/ETH_A_So_MI_PRI2CoSMapping
MT/ETH_A_So_MI_MEP_MAC*
MT/ETH_A_So_MI_Client_MEL*
MT/ETH_A_So_MI_LCK_Period*
MT/ETH_A_So_MI_LCK_Pri*
MT/ETH_A_So_MI_MEL*
* ETH OAM related | | + +##### Processes + +The processes associated with the MT/ETH\_A\_So function are as depicted in Figure 10-2. + +![Figure 10-2 – MT/ETH_A_So process diagram. This is a vertical flowchart showing the data processing pipeline for MT/ETH_A_So. The input is ETH_CI, which consists of three parallel streams: D (Data), P (Priority), and DE (Drop Eligible). The flow proceeds through several processing blocks: 1. LCK generate: Takes inputs D, P, and DE, and configuration parameters MI_MEP_MAC, MI_Client_MEL, MI_LCK_Period, and MI_LCK_Pri. 2. Normal | Lock Selector: Takes D, P, and DE from the LCK generate block, and configuration parameter MI_Admin_State. It has two output paths: 'Normal' and 'Lock'. 3. OAM MEL filter: Takes D, P, and DE from the Selector, and configuration parameter MI_MEL. 4. 802.3 MAC FCS: Takes D, P, and DE from the OAM MEL filter, and configuration parameter MI_FCSenable. 5. QoS mapping: Takes D, P, and DE from the 802.3 MAC FCS, and configuration parameter MI_PRI2CoSMapping. 6. CW insertion: Takes D, P, and DE from the QoS mapping, and configuration parameters MI_CWEnable and MI_SQUse. 7. Insert S bit: Takes D, P, and DE from the CW insertion block. The final output is MT_AI, which consists of three parallel streams: D (Data), PHB (Packet Handling Bit), and PHB (Packet Handling Bit). The diagram is labeled G.8121-Y.1381(18)_F10-2.](51167ecef86d85cdc6dde05a3afb74b8_img.jpg) + +Figure 10-2 – MT/ETH\_A\_So process diagram. This is a vertical flowchart showing the data processing pipeline for MT/ETH\_A\_So. The input is ETH\_CI, which consists of three parallel streams: D (Data), P (Priority), and DE (Drop Eligible). The flow proceeds through several processing blocks: 1. LCK generate: Takes inputs D, P, and DE, and configuration parameters MI\_MEP\_MAC, MI\_Client\_MEL, MI\_LCK\_Period, and MI\_LCK\_Pri. 2. Normal | Lock Selector: Takes D, P, and DE from the LCK generate block, and configuration parameter MI\_Admin\_State. It has two output paths: 'Normal' and 'Lock'. 3. OAM MEL filter: Takes D, P, and DE from the Selector, and configuration parameter MI\_MEL. 4. 802.3 MAC FCS: Takes D, P, and DE from the OAM MEL filter, and configuration parameter MI\_FCSenable. 5. QoS mapping: Takes D, P, and DE from the 802.3 MAC FCS, and configuration parameter MI\_PRI2CoSMapping. 6. CW insertion: Takes D, P, and DE from the QoS mapping, and configuration parameters MI\_CWEnable and MI\_SQUse. 7. Insert S bit: Takes D, P, and DE from the CW insertion block. The final output is MT\_AI, which consists of three parallel streams: D (Data), PHB (Packet Handling Bit), and PHB (Packet Handling Bit). The diagram is labeled G.8121-Y.1381(18)\_F10-2. + +**Figure 10-2 – MT/ETH\_A\_So process diagram** + +– *LCK generation process:* + +See clause 8.1.2 of [ITU-T G.8021]. + +– *Selector process:* + +See clause 8.1.3 of [ITU-T G.8021]. The normal CI is blocked if Admin\_State = LOCKED. + +– *OAM MEL filter process:* + +See clause 8.1.1 of [ITU-T G.8021]. + +– *802.3 MAC FCS generation:* + +See clause 8.8.1 of [ITU-T G.8021]. MAC FCS generation is optional (see [IETF RFC 4720] and [ITU-T Y.1415]): MAC FCS is generated if MI\_FCSEnabled is true. + +– *QoS mapping process:* + +This process maps the Ethernet-based QoS signals into MPLS-based QoS signals. + +The CoS part of the AI\_PHB is generated by the received CI\_P according to the 1:1 mapping configured by the MI\_PRI2CoSMapping. + +The DP part of the AI\_PHB is generated by the received CI\_DE according to the following rule: + +``` +If CI_DE = True + DP(AI_PHB) = Yellow +Else + DP(AI_PHB) = Green +``` + +– *CW insertion process:* + +See clause 8.5.1. + +– *Insert S bit process:* + +A 1-bit S Field set to 1 (bottom of label stack) is inserted to indicate the client is not MPLS. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 10.1.2 MPLS-TP to ETH adaptation sink function (MT/ETH\_A\_Sk) + +This function extracts the ETH\_CI information from a MT\_AI signal. + +The information flow and processing of the MT/ETH\_A\_Sk function is defined with reference to Figure 10-3. + +#### Symbol + +![Diagram of the MT/ETH_A_Sk function symbol. It is a yellow trapezoid labeled 'MT/ETH_A_Sk'. An arrow labeled 'MT_AI' points into the bottom of the trapezoid. An arrow labeled 'ETH_CI' points out of the top of the trapezoid. A double-headed arrow labeled 'MT/ETH_A_Sk_MI' points into the right side of the trapezoid. Below the diagram is the text 'G.8121-Y.1381(13)_F10-3'.](8206c9e6dac8ba2d4c3e28ee5d008058_img.jpg) + +G.8121-Y.1381(13)\_F10-3 + +Diagram of the MT/ETH\_A\_Sk function symbol. It is a yellow trapezoid labeled 'MT/ETH\_A\_Sk'. An arrow labeled 'MT\_AI' points into the bottom of the trapezoid. An arrow labeled 'ETH\_CI' points out of the top of the trapezoid. A double-headed arrow labeled 'MT/ETH\_A\_Sk\_MI' points into the right side of the trapezoid. Below the diagram is the text 'G.8121-Y.1381(13)\_F10-3'. + +**Figure 10-3 – MT/ETH\_A\_Sk function** + +#### Interfaces + +The MT/ETH\_A\_Sk interfaces are described in Table 10-2. + +**Table 10-2 – MT/ETH\_A\_Sk Inputs and Outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| Each MT_AP:
MT_AI_Data
MT_AI_PHB
MT_AI_TSF
MT_AI_AIS
MT/ETH_A_Sk_MP:
MT/ETH_A_Sk_MI_FCSEnable
MT/ETH_A_Sk_MI_CWEnable
MT/ETH_A_Sk_MI_SQUse
MT/ETH_A_Sk_MI_GAL_Enable
MT/ETH_A_Sk_MI_CoS2PRIMapping

MT/ETH_A_Sk_MI_MEL*

MT/ETH_A_Sk_MI_Admin_State
MT/ETH_A_Sk_MI_LCK_Period *
MT/ETH_A_Sk_MI_LCK_Pri *
MT/ETH_A_Sk_MI_Client_MEL *
MT/ETH_A_Sk_MI_MEP_MAC *
MT/ETH_A_Sk_MI_AIS_Pri *
MT/ETH_A_Sk_MI_AIS_Period *

* ETH OAM related | ETH_FP:
ETH_CI_Data
ETH_CI_P
ETH_CI_DE
ETH_CI_SSF

MT/ETH_A_Sk_MP:
MT/ETH_A_Sk_MI_pFCSErrors | + +##### Processes + +The processes associated with the MT/ETH\_A\_Sk function are as depicted in Figure 10-4. + +![Figure 10-4 – MT/ETH_A_Sk process diagram. This block diagram illustrates the data flow and control processes for the MT/ETH_A_Sk function. At the bottom, the MT_AI input is processed through a series of blocks: G-ACh filter, Extract S bit, CW extraction, QoS mapping, 802.3 MAC Frm Chk, OAM MEL filter, AIS insert, Selector (with Normal and Lock sub-blocks), and LCK generate. Control parameters (MI_*) are fed into the LCK generate, AIS insert, Selector, and OAM MEL filter blocks. The Selector outputs to the ETH_CI interface via SSF, D, P, and DE paths. A 'Consequent actions' block receives inputs from the OAM MEL filter and AIS insert blocks. Various internal signals like aSSF, aAIS, TSF, PHB, and D are shown between blocks. A reference code G.8121-Y.1381(18)_F10-4 is in the bottom right.](6d697ce8828ba75fddee0a1b7767a7ca_img.jpg) + +Figure 10-4 – MT/ETH\_A\_Sk process diagram. This block diagram illustrates the data flow and control processes for the MT/ETH\_A\_Sk function. At the bottom, the MT\_AI input is processed through a series of blocks: G-ACh filter, Extract S bit, CW extraction, QoS mapping, 802.3 MAC Frm Chk, OAM MEL filter, AIS insert, Selector (with Normal and Lock sub-blocks), and LCK generate. Control parameters (MI\_\*) are fed into the LCK generate, AIS insert, Selector, and OAM MEL filter blocks. The Selector outputs to the ETH\_CI interface via SSF, D, P, and DE paths. A 'Consequent actions' block receives inputs from the OAM MEL filter and AIS insert blocks. Various internal signals like aSSF, aAIS, TSF, PHB, and D are shown between blocks. A reference code G.8121-Y.1381(18)\_F10-4 is in the bottom right. + +**Figure 10-4 – MT/ETH\_A\_Sk process diagram** + +- *Selector process:* + +See clause 8.1.3 of [ITU-T G.8021]. The normal CI is blocked if Admin\_State = LOCKED. + +- *LCK generate process:* + +See clause 8.1.2 of [ITU-T G.8021]. + +- *AIS insert process:* + +See clause 8.1.4 of [ITU-T G.8021]. + +- *OAM MEL filter process:* + +See clause 8.1.1 of [ITU-T G.8021]. + +– *"802.3 MAC Frame Check" process:* + +See clause 8.8.2 of [ITU-T G.8021]. MAC Frame Check is optional (see [IETF RFC 4720] and [ITU-T Y.1415]): MAC FCS is checked if MI\_FCSEnabled is true. + +– *QoS mapping process:* + +This process maps the MPLS-based QoS signals into Ethernet-based QoS signals. + +The CI\_P is generated by the received PSC part of the AI\_PHB according to the 1:1 mapping configured by the MI\_CoS2PRIMapping. + +The CI\_DE is generated by the received DP part of the AI\_PHB according to the following rule: + +``` +If DP(AI_PHB) = Green + CI_DE = False +Else + CI_DE = True +``` + +– *CW extraction process:* + +See clause 8.5.2. + +– *G-ACh filter process:* + +This process removes all the received traffic units which are G-ACh encapsulated, which include GAL or not depending on the MI\_GAL\_Enable. + +– *Extract S bit process:* + +Extract and process the 1-bit S Field: the retrieved S Field should have the value 1 (bottom of label stack) to indicate the client is not MPLS: for such case the traffic unit is accepted and forwarded (together with the PHB information) after extraction of the S-bit field to the next process. For the case the S-bit has the value 0, the traffic unit is silently discarded. + +**Defects:** None. + +#### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF and (not MI\_Admin\_State == LOCKED) + +aAIS $\leftarrow$ AI\_AIS + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +## **10.2 MPLS-TP to SCC and MCC adaptation functions** + +This clause provides the descriptions of the MPLS-TP adaptation functions for the MPLS-TP MCC and SCC. + +Figure 10-5 shows the MPLS-TP adaptation functions providing access to the MCC and SCC. These MT/MCC and MT/SCC adaptation functions are defined in more detail below. + +In case that the client is MPLS-TP, MT/Client will be MT/MT. + +![Figure 10-5: MT/SCC_A function, MT/MCC_A function, and MT/client_A function diagram. At the top, three groups of forwarding points (FPs) are shown: MCC_FPs (IPv4 FWP, IPv6 FWP, OSI FWP), SCC_FPs (IPv4 FWP, IPv6 FWP, OSI FWP), and Client_CPs/FPs. These are connected to three yellow trapezoidal blocks: MT/MCC, MT/SCC, and MT/Client. Each FP group has a diamond symbol below it. The MT/MCC, MT/SCC, and MT/Client blocks are connected to a common horizontal line. Below this line is a yellow triangle labeled MT_AP. Below MT_AP is a yellow triangle labeled MT_TT. At the bottom is a yellow rectangle labeled MT_TCP. A reference code G.8121-Y.1381(13)_F10-5 is at the bottom right.](301f4a188198a15b1415d54545b07e0d_img.jpg) + +Figure 10-5: MT/SCC\_A function, MT/MCC\_A function, and MT/client\_A function diagram. At the top, three groups of forwarding points (FPs) are shown: MCC\_FPs (IPv4 FWP, IPv6 FWP, OSI FWP), SCC\_FPs (IPv4 FWP, IPv6 FWP, OSI FWP), and Client\_CPs/FPs. These are connected to three yellow trapezoidal blocks: MT/MCC, MT/SCC, and MT/Client. Each FP group has a diamond symbol below it. The MT/MCC, MT/SCC, and MT/Client blocks are connected to a common horizontal line. Below this line is a yellow triangle labeled MT\_AP. Below MT\_AP is a yellow triangle labeled MT\_TT. At the bottom is a yellow rectangle labeled MT\_TCP. A reference code G.8121-Y.1381(13)\_F10-5 is at the bottom right. + +**Figure 10-5 – MT/SCC\_A function, MT/MCC\_A function, and MT/client\_A function** + +### 10.2.1 MT/SCC\_A adaptation function + +The MT to SCC adaptation function provides access to the SCC for signalling communication. It is used for the scenarios where the signalling communication network (SCN) utilizes the SCC as defined in [IETF RFC 5718]. + +#### 10.2.1.1 MT to SCC adaptation source function (MT/SCC\_A\_So function) + +The MT/SCC\_A\_So function maps the SCN data into the G-ACh SCC packets as defined in [IETF RFC 5718]. The diamonds in Figure 10-6 represent traffic shaping and conditioning functions that may be needed to prevent the SCC forwarding points from exceeding their committed bandwidth in congestion situations. These traffic shaping and conditioning functions as well as the related bandwidth management and bandwidth assignment functions are outside the scope of this Recommendation. + +The information flow and processing of the MT/SCC\_A\_So functions is defined with reference to Figures 10-6 and 10-7. + +##### Symbol + +![Figure 10-6: MT/SCC_A_So function diagram. At the top, a group of SCC_FPs (IPv4 FWP, IPv6 FWP, OSI FWP) is shown. Below each FP is a diamond symbol. Arrows point from these diamonds to a yellow trapezoidal block labeled MT/SCC. An arrow labeled MT/SCC_A_So_MP points into the MT/SCC block from the left. An arrow points from the MT/SCC block down to a yellow rectangle labeled MT_AP. A reference code G.8121-Y.1381(13)_F10-6 is at the bottom right.](3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg) + +Figure 10-6: MT/SCC\_A\_So function diagram. At the top, a group of SCC\_FPs (IPv4 FWP, IPv6 FWP, OSI FWP) is shown. Below each FP is a diamond symbol. Arrows point from these diamonds to a yellow trapezoidal block labeled MT/SCC. An arrow labeled MT/SCC\_A\_So\_MP points into the MT/SCC block from the left. An arrow points from the MT/SCC block down to a yellow rectangle labeled MT\_AP. A reference code G.8121-Y.1381(13)\_F10-6 is at the bottom right. + +**Figure 10-6 – MT/SCC\_A\_So function** + +##### Interfaces + +The MT/SCC\_A\_So interfaces are described in Table 10-3. + +**Table 10-3 – MT/SCC\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------|---------------------------------------| +| SCC_FP:
SCC_CI_D
MT/SCC_A_So_MP:
MT/SCC_A_So_MI_ECC_CoS
MT/SCC_A_So_MI_GAL_Enable | MT_AP:
MT_AI_D
MT_AI_PHB | + +##### Processes + +##### Activation + +- The MT/SCC\_A\_So function shall access the access point when it is activated (MI\_Active is true). Otherwise, it shall not access the access point. + +The process associated with the MT/SCC\_A\_So function is as depicted in Figure 10-7. + +![Diagram of MT/SCC_A_So processes showing a box labeled 'ECC mapping' with inputs SCC_CP, SCC_CI_D, MI_ECC_CoS, MI_GAL_Enable, and MT/SCC_A_So_MP. It has outputs MT_AI_D and MT_AP.](7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg) + +The diagram illustrates the MT/SCC\_A\_So process. A central box labeled "ECC mapping" receives several inputs: "SCC\_CP" and "SCC\_CI\_D" from the top; "MI\_ECC\_CoS", "MI\_GAL\_Enable", and "MT/SCC\_A\_So\_MP" from the right (these three are stacked vertically). The box produces two outputs at the bottom: "MT\_AI\_D" and "MT\_AP" (stacked vertically). + +Diagram of MT/SCC\_A\_So processes showing a box labeled 'ECC mapping' with inputs SCC\_CP, SCC\_CI\_D, MI\_ECC\_CoS, MI\_GAL\_Enable, and MT/SCC\_A\_So\_MP. It has outputs MT\_AI\_D and MT\_AP. + +G.8121-Y.1381(18)\_F10-7 + +**Figure 10-7 – MT/SCC\_A\_So processes** + +**ECC mapping process:** See clause 8.7.1.1 + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 10.2.1.2 MT to SCC adaptation sink function (MT/SCC\_A\_Sk function) + +The MT/SCC\_A\_Sk function extracts the SCN from the G-ACh SCC packets as defined in [IETF RFC 5718]. + +The information flow and processing of the MT/SCC\_A\_Sk functions is defined with reference to Figures 10-8 and 10-9. + +##### Symbol + +![Figure 10-8: MT/SCC_A_Sk function symbol diagram. A yellow trapezoid labeled 'MT/SCC' has an input arrow from the left labeled 'MT/SCC_A_Sk_MP' and an input arrow from below labeled 'MT_AP'. Above the trapezoid, a bracket labeled 'SCC_FPs' groups five upward-pointing arrows labeled 'IPv4 FwP', 'IPv6 FwP', 'OSI FwP', and two unlabeled 'FwP' entries. The text 'G.8121-Y.1381(13)_F10-8' is at the bottom right.](dc7f3c8b7f8859a78d5705f104504e4c_img.jpg) + +Figure 10-8: MT/SCC\_A\_Sk function symbol diagram. A yellow trapezoid labeled 'MT/SCC' has an input arrow from the left labeled 'MT/SCC\_A\_Sk\_MP' and an input arrow from below labeled 'MT\_AP'. Above the trapezoid, a bracket labeled 'SCC\_FPs' groups five upward-pointing arrows labeled 'IPv4 FwP', 'IPv6 FwP', 'OSI FwP', and two unlabeled 'FwP' entries. The text 'G.8121-Y.1381(13)\_F10-8' is at the bottom right. + +Figure 10-8 – MT/SCC\_A\_Sk function + +##### Interfaces + +The MT/SCC\_A\_Sk interfaces are described in Table 10-4. + +Table 10-4 – MT/SCC\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------|------------------------------------------| +| MT_AP:
MT_AI_D
MT_AI_PHB
MT_AI_TSF
MT/SCC_A_Sk_MP:
MT/SCC_A_Sk_MI_GAL_Enable | SCC_FP:
SCC_CI_D
SCC_CI_SSF | + +##### Processes + +The processes associated with the MT/SCC\_A\_Sk function are as depicted in Figure 10-9. + +![Figure 10-9: MT/SCC_A_Sk processes diagram. A grey box labeled 'SCC_CP' contains two sub-processes: 'ECC demapping' and 'Consequent actions'. Inputs 'MT_AI_D' and 'MT_AI_TSF' enter from the bottom, with 'MT_AP' below them. 'ECC demapping' outputs 'SCC_CI_D' and 'Consequent actions' outputs 'SCC_CI_SSF' to the top. On the right, 'MI_GAL_Enable' and 'MT/SCC_A_Sk_MP' enter the box. The text 'G.8121-Y.1381(18)_F10-9' is at the bottom right.](2e3b1ae09da2cba02f0bb8a531f1515e_img.jpg) + +Figure 10-9: MT/SCC\_A\_Sk processes diagram. A grey box labeled 'SCC\_CP' contains two sub-processes: 'ECC demapping' and 'Consequent actions'. Inputs 'MT\_AI\_D' and 'MT\_AI\_TSF' enter from the bottom, with 'MT\_AP' below them. 'ECC demapping' outputs 'SCC\_CI\_D' and 'Consequent actions' outputs 'SCC\_CI\_SSF' to the top. On the right, 'MI\_GAL\_Enable' and 'MT/SCC\_A\_Sk\_MP' enter the box. The text 'G.8121-Y.1381(18)\_F10-9' is at the bottom right. + +Figure 10-9 – MT/SCC\_A\_Sk processes + +**ECC demapping process:** See clause 8.7.1.2 + +**Defects:** None. + +**Consequent actions:** The function shall perform the following consequent actions: + $aSSF \leftarrow AI\_TSF$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### 10.2.2 MT/MCC\_A Adaptation Function + +The MT to MCC adaptation function provides access to the MCC for signalling communication. It is used for the scenarios where the MCN utilizes the MCC as defined in [IETF RFC 5718]. + +#### 10.2.2.1 MT to MCC adaptation source function (MT/MCC\_A\_So function) + +The MT/MCC\_A\_So function maps the MCN data into the G-ACh MCC packets as defined in [IETF RFC 5718]. The diamonds in Figure 10-10 represent traffic shaping and conditioning functions that may be needed to prevent the MCC forwarding points from exceeding their committed bandwidth in congestion situations. These traffic shaping and conditioning functions as well as the related bandwidth management and bandwidth assignment functions are outside the scope of this Recommendation. + +The information flow and processing of the MT/MCC\_A\_So functions is defined with reference to Figures 10-10 and 10-11. + +##### Symbol + +![Diagram of the MT/MCC_A_So function symbol. At the top, a bracket labeled 'MCC_FPs' covers four input paths: IPv4 FWP, IPv6 FWP, OSI FWP, and another IPv6 FWP. Each path has a diamond symbol representing traffic shaping. Arrows from these diamonds point to a central yellow trapezoidal block labeled 'MT/MCC'. To the left of this block is an input arrow labeled 'MT/MCC_A_So_MP'. An arrow points out from the bottom of the block to 'MT_AP'. The diagram is labeled 'G.8121-Y.1381(13)_F10-10'.](b30e390cb591b39482fe7ecd4c4cd84b_img.jpg) + +Diagram of the MT/MCC\_A\_So function symbol. At the top, a bracket labeled 'MCC\_FPs' covers four input paths: IPv4 FWP, IPv6 FWP, OSI FWP, and another IPv6 FWP. Each path has a diamond symbol representing traffic shaping. Arrows from these diamonds point to a central yellow trapezoidal block labeled 'MT/MCC'. To the left of this block is an input arrow labeled 'MT/MCC\_A\_So\_MP'. An arrow points out from the bottom of the block to 'MT\_AP'. The diagram is labeled 'G.8121-Y.1381(13)\_F10-10'. + +Figure 10-10 – MT/MCC\_A\_So function + +##### Interfaces + +The MT/MCC\_A\_So interfaces are described in Table 10-5. + +Table 10-5 – MT/MCC\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------|---------------------------------------| +| MCC_FP:
MCC_CI_D
MT/MCC_A_So_MP:
MT/MCC_A_So_MI_ECC_CoS
MT/MCC_A_So_MI_GAL_enable | MT_AP:
MT_AI_D
MT_AI_PHB | + +##### Processes + +The process associated with the MT/MCC\_A\_So function is as depicted in Figure 10-11. + +![Diagram of the MT/MCC_A_So processes. A grey box contains a 'Mapping' block. Inputs to the Mapping block are 'MCC_CP', 'MCC_CI_D', and 'MT_AI_D'. An arrow points from the Mapping block to 'MT_AP'. To the right of the box, three vertical labels represent additional inputs: 'MI_ECC_CoS', 'MI_GAL_Enable', and 'MT/MCC_A_So_MP'. The diagram is labeled 'G.8121-Y.1381(18)_F10-11'.](bd1fc4ff61890bfc6fb1095f4143bc42_img.jpg) + +Diagram of the MT/MCC\_A\_So processes. A grey box contains a 'Mapping' block. Inputs to the Mapping block are 'MCC\_CP', 'MCC\_CI\_D', and 'MT\_AI\_D'. An arrow points from the Mapping block to 'MT\_AP'. To the right of the box, three vertical labels represent additional inputs: 'MI\_ECC\_CoS', 'MI\_GAL\_Enable', and 'MT/MCC\_A\_So\_MP'. The diagram is labeled 'G.8121-Y.1381(18)\_F10-11'. + +Figure 10-11 – MT/MCC\_A\_So processes + +**MCC mapping process:** See clause 8.7.1.1 + +**Defects:** None. +**Consequent actions:** None. +**Defect correlations:** None. +**Performance monitoring:** None. + +#### **10.2.2.2 MT to MCC adaptation sink function (MT/MCC\_A\_Sk function)** + +The MT/MCC\_A\_Sk function extracts the MCN data from the G-ACh MCC packets as defined in [IETF RFC 5718]. + +The information flow and processing of the MT/MCC\_A\_Sk functions is defined with reference to Figures 10-12 and 10-13. + +##### **Symbol** + +![Symbol diagram for MT/MCC_A_Sk function. A yellow trapezoid labeled 'MT/MCC' has an input arrow from the left labeled 'MT/MCC_A_Sk_MP' and an input arrow from below labeled 'MT_AP'. Above the trapezoid, a bracket labeled 'MCC_FPs' encompasses five output arrows labeled 'IP<4 Fwp', 'IP<6 Fwp', 'OSI Fwp', and two unlabeled 'Fwp' arrows. A small text 'G.8121-Y.1381(13)_F10-12' is at the bottom right.](584c8bae39761224bd920bbc68831c1e_img.jpg) + +Symbol diagram for MT/MCC\_A\_Sk function. A yellow trapezoid labeled 'MT/MCC' has an input arrow from the left labeled 'MT/MCC\_A\_Sk\_MP' and an input arrow from below labeled 'MT\_AP'. Above the trapezoid, a bracket labeled 'MCC\_FPs' encompasses five output arrows labeled 'IP<4 Fwp', 'IP<6 Fwp', 'OSI Fwp', and two unlabeled 'Fwp' arrows. A small text 'G.8121-Y.1381(13)\_F10-12' is at the bottom right. + +**Figure 10-12 – MT/MCC\_A\_Sk function** + +##### **Interfaces** + +The MT/MCC\_A\_Sk interfaces are described in Table 10-6. + +**Table 10-6 – MT/MCC\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------|------------------------------------------| +| MT_AP:
MT_AI_D
MT_AI_PHB
MT_AI_TSF

MT/MCC_A_Sk_MP:
MT/SCC_A_Sk_MI_GAL_Enable | MCC_FP:
MCC_CI_D
MCC_CI_SSF | + +##### **Processes** + +The processes associated with the MT/MCC\_A\_Sk function are as depicted in Figure 10-13. + +![Process diagram for MT/MCC_A_Sk. A grey box contains two sub-processes: 'Demapping' and 'Consequent actions'. Inputs 'MT_AI_D' and 'MT_AI_TSF' enter from the bottom, with 'MT_AP' below them. 'Demapping' outputs 'MCC_CI_D' and 'Consequent actions' outputs 'MCC_CI_SSF' to the top, under the label 'MCC_CP'. On the right, 'MI_Active' and 'MI_GAL_Enable' enter from the bottom, with 'MT/MCC_A_Sk_MP' below them. A small text 'G.8121-Y.1381(18)_F10-13' is at the bottom right.](449732882b537bd24ca2184f1a2b7a50_img.jpg) + +Process diagram for MT/MCC\_A\_Sk. A grey box contains two sub-processes: 'Demapping' and 'Consequent actions'. Inputs 'MT\_AI\_D' and 'MT\_AI\_TSF' enter from the bottom, with 'MT\_AP' below them. 'Demapping' outputs 'MCC\_CI\_D' and 'Consequent actions' outputs 'MCC\_CI\_SSF' to the top, under the label 'MCC\_CP'. On the right, 'MI\_Active' and 'MI\_GAL\_Enable' enter from the bottom, with 'MT/MCC\_A\_Sk\_MP' below them. A small text 'G.8121-Y.1381(18)\_F10-13' is at the bottom right. + +**Figure 10-13 – MT/MCC\_A\_Sk processes** + +**ECC demapping process:** See clause 8.7.1.2 + +**Defects:** None. + +**Consequent actions:** The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +# 11 Non-MPLS-TP server to MPLS-TP adaptation functions + +## 11.1 SDH to MPLS-TP adaptation function (S/MT\_A) + +### 11.1.1 VC-n to MPLS-TP adaptation functions (Sn/MT\_A; n=3, 3-X, 4, 4-X) + +#### 11.1.1.1 VC-n to MPLS-TP adaptation source function (Sn/MT\_A\_So) + +This function maps MT\_CI information onto a Sn\_AI signal (n=3, 3-X, 4, 4-X). + +Data at the Sn\_AP is a VC-n (n = 3, 3-X, 4, 4-X), having a payload as described in [ITU-T G.707], but with indeterminate path overhead (POH) bytes: J1, B3, G1. + +##### Symbol + +The Sn/MT\_A\_So function symbol is shown in Figure 11-1. + +![Figure 11-1 – Sn/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'Sn/MT_A_So'. Inputs from the top are SCC_CI, MT_CI, and an ellipsis. An output at the bottom is Sn_CI. Inputs from the right are Sn/MT_A_So_MI and Sn_TI. A reference label 'G.8121-Y.1381(13)_F11-1' is at the bottom right.](81a685da17696e2b65791368a3e8ce8f_img.jpg) + +Figure 11-1 – Sn/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'Sn/MT\_A\_So'. Inputs from the top are SCC\_CI, MT\_CI, and an ellipsis. An output at the bottom is Sn\_CI. Inputs from the right are Sn/MT\_A\_So\_MI and Sn\_TI. A reference label 'G.8121-Y.1381(13)\_F11-1' is at the bottom right. + +**Figure 11-1 – Sn/MT\_A\_So symbol** + +##### Interfaces + +The Sn/MT\_A\_So interfaces are described in Table 11-1. + +**Table 11-1 – Sn/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Sn_TP:
Sn_TI_Clock
Sn_TI_FrameStart | Sn_AP:
Sn_AI_Data
Sn_AI_Clock
Sn_AI_FrameStart | + +**Table 11-1 – Sn/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Sn/MT_A_So_MP:
Sn/MT_A_So_MI_SCCType
Sn/MT_A_So_MI_Label[1..M]
Sn/MT_A_So_MI_LSPTYPE[1..M]
Sn/MT_A_So_MI_CoS[1..M]
Sn/MT_A_So_PHB2TCMapping[1..M]
Sn/MT_A_So_MI_QoSEncodingMode[1..M]
Sn/MT_A_So_MI_Mode[1..M]
Sn/MT_A_So_MI_GAL_Enable[1..M] | | + +##### **Processes** + +A process diagram of this function is shown in Figure 11-2. + +![Figure 11-2 – Sn/MT_A_So process diagram. This block diagram shows the flow of data through several processing stages. Inputs on the left include MI_Label[1..M], MI_LSPTYPE[1..M], MI_PSC[1..M], MI_PHB2TCMapping[1..M], MI_QoSEncodingMode[1..M], MI_Mode[1..M], and MI_SCCType. Inputs at the top include MT_CI_D[1] through MT_CI_D[M] and SCC_CI. The flow starts with 'TC/Label processes' which receive the top and left inputs and output 'Muxed MT_CI_D'. This goes to a 'Queueing' block, which then feeds into 'MPLS-TP specific GFP-F processes'. This block also receives MI_SCCType and SCC_CI. It outputs 'GFP_FS' and 'GFP_Frame' to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' also points to this block. The next stage is 'VC-n specific GFP-F processes', which receive 'GFP_FS' and 'GFP_Frame' and also receive 'Sn_TI_CK' and 'Sn_TI_FS'. It outputs 'Sn_AI_D', 'Sn_AI_CK', and 'Sn_AI_FS' to the final 'VC-n specific processes' block, which produces the final outputs 'Sn_AI_D', 'Sn_AI_CK', and 'Sn_AI_FS'. The entire diagram is enclosed in a grey box.](b550cb515008f6bab9f295adcb28b5f6_img.jpg) + +Figure 11-2 – Sn/MT\_A\_So process diagram. This block diagram shows the flow of data through several processing stages. Inputs on the left include MI\_Label[1..M], MI\_LSPTYPE[1..M], MI\_PSC[1..M], MI\_PHB2TCMapping[1..M], MI\_QoSEncodingMode[1..M], MI\_Mode[1..M], and MI\_SCCType. Inputs at the top include MT\_CI\_D[1] through MT\_CI\_D[M] and SCC\_CI. The flow starts with 'TC/Label processes' which receive the top and left inputs and output 'Muxed MT\_CI\_D'. This goes to a 'Queueing' block, which then feeds into 'MPLS-TP specific GFP-F processes'. This block also receives MI\_SCCType and SCC\_CI. It outputs 'GFP\_FS' and 'GFP\_Frame' to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' also points to this block. The next stage is 'VC-n specific GFP-F processes', which receive 'GFP\_FS' and 'GFP\_Frame' and also receive 'Sn\_TI\_CK' and 'Sn\_TI\_FS'. It outputs 'Sn\_AI\_D', 'Sn\_AI\_CK', and 'Sn\_AI\_FS' to the final 'VC-n specific processes' block, which produces the final outputs 'Sn\_AI\_D', 'Sn\_AI\_CK', and 'Sn\_AI\_FS'. The entire diagram is enclosed in a grey box. + +G.8121-Y.1381(18)\_F11-2 + +**Figure 11-2 – Sn/MT\_A\_So process diagram** + +- *TC/Label processes:* +See clause 8.2.1. +- *Queueing process:* +See clause 8.3. +- *MPLS-TP-specific GFP-F source process:* + +See clause 8.4.1. + +– *Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *VC-n specific GFP source process:* + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the VC-n payload area according to clause 10.6 of [ITU-T G.707]. + +– *VC-n specific source process:* + +**C2:** Signal label information is derived directly from the Adaptation function type. The value for "GFP mapping" in Table 9-11 of [ITU-T G.707] is placed in the C2 byte position. + +**H4:** For Sn/MT\_A\_So with n=3, 4, the H4 byte is sourced as all-zeros. + +NOTE 1 – For Sn/MT\_A\_So with n=3-X, 4-X, the H4 byte is undefined at the Sn-X\_AP output of this function (as per clause 12 of [ITU-T G.783]). + +NOTE 2 – For Sn/MT\_A\_So with n=3, 4, 3-X, 4-X, the K3, F2, F3 bytes are undefined at the Sn-X\_AP output of this function (as per clause 12 of [ITU-T G.783]). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.1.1.2 VC-n to MPLS-TP adaptation sink function (Sn/MT\_A\_Sk) + +This function extracts MT\_CI information from the Sn\_AI signal (n=3, 3-X, 4, 4-X), delivering MT\_CI. + +Data at the Sn\_AP is a VC-n (n=3, 3-X, 4, 4-X) but with indeterminate POH bytes J1, B3, G1, as per [ITU-T G.707]. + +##### Symbol + +The Sn/MT\_A\_Sk function symbol is shown in Figure 11-3. + +![Diagram of the Sn/MT_A_Sk function symbol. It is a trapezoidal block labeled 'Sn/MT_A_Sk'. An input arrow labeled 'Sn_CI' points into the bottom of the block. Multiple output arrows labeled 'SCC_CI', 'MT_CI', and '...' point out of the top of the block. A bidirectional arrow labeled 'Sn/MT_A_Sk_MI' is connected to the right side of the block. A small text label 'G.8121-Y.1381(13)_F11-3' is located to the right of the block.](0912a2665a461bed9dafb29a78986961_img.jpg) + +The diagram shows a trapezoidal block representing the Sn/MT\_A\_Sk function. An input arrow labeled 'Sn\_CI' points into the bottom of the block. Multiple output arrows labeled 'SCC\_CI', 'MT\_CI', and '...' point out of the top of the block. A bidirectional arrow labeled 'Sn/MT\_A\_Sk\_MI' is connected to the right side of the block. A small text label 'G.8121-Y.1381(13)\_F11-3' is located to the right of the block. + +Diagram of the Sn/MT\_A\_Sk function symbol. It is a trapezoidal block labeled 'Sn/MT\_A\_Sk'. An input arrow labeled 'Sn\_CI' points into the bottom of the block. Multiple output arrows labeled 'SCC\_CI', 'MT\_CI', and '...' point out of the top of the block. A bidirectional arrow labeled 'Sn/MT\_A\_Sk\_MI' is connected to the right side of the block. A small text label 'G.8121-Y.1381(13)\_F11-3' is located to the right of the block. + +**Figure 11-3 – Sn/MT\_A\_Sk symbol** + +##### Interfaces + +The Sn/MT\_A\_Sk interfaces are described in Table 11-2. + +**Table 11-2 – Sn/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Sn_AP:
Sn_AI_Data
Sn_AI_Clock
Sn_AI_FrameStart
Sn_AI_TSF
Sn/MT_A_Sk_MP:
Sn/MT_A_Sk_MI_SCCType
Sn/MT_A_Sk_MI_Label[1...M]
Sn/MT_A_Sk_MI_LSPTYPE[1...M]
Sn/MT_A_Sk_MI_CoS[1...M]
Sn/MT_A_Sk_MI_TC2PHBMapping[1...M]
Sn/MT_A_Sk_MI_QoSDecodingMode[1...M]
Sn/MT_A_Sk_MI_Mode[1...M]
Sn/MT_A_Sk_MI_LCK_Period[1...M]
Sn/MT_A_Sk_MI_LCK_CoS[1...M]
Sn/MT_A_Sk_MI_Admin_State
Sn/MT_A_Sk_MI_AIS_Period[1...M]
Sn/MT_A_Sk_MI_AIS_CoS[1...M]
Sn/MT_A_Sk_MI_GAL_enable[1...M]
Sn/MT_A_Sk_MI_LCK_OAM_Tool [1...M]
Sn/MT_A_Sk_MI_AIS_OAM_Tool[1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_LStack

SCC_CP:
SCC_CI_Data
SCC_CI_SSF
Sn/MT_A_Sk_MP:
Sn/MT_A_Sk_MI_AcSL
Sn/MT_A_Sk_MI_AcEXI
Sn/MT_A_Sk_MI_LastInvalidUPI
Sn/MT_A_Sk_MI_cPLM
Sn/MT_A_Sk_MI_cLFD
Sn/MT_A_Sk_MI_cEXM
Sn/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-4. + +![Figure 11-4 – Sn/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of a network element. At the top, multiple 'MT_CI_SSF' inputs (labeled 1 to M) enter a 'Consequent action' block. Below this, there are 'Selector' blocks with 'Normal' and 'LCK' options, followed by 'AIS insert' and 'LCK generate' blocks. These are connected to 'TC/Label processes', which in turn connect to a 'Label stack copy' block. The 'Label stack copy' block feeds into 'MPLS-TP specific GFP-F processes'. Below this are 'Common GFP-F processes', 'VC-n specific GFP-F processes', and another 'VC-n specific processes' block at the bottom. Various input and output signals are shown, such as 'MI_Label[1...M]', 'MI_LSPType[1...M]', 'MI_CoS[1...M]', 'MI_PHB2TCMapping[1...M]', 'MI_QoSEncodingModel[1...M]', 'MI_Mode[1...M]', 'MI_LastInvalidUPI', 'MI_SCCType', 'MI_AcEXI', 'MI_AcSL', 'MI_Admin_State', 'MI_LCK_Period/CoS/OAM_Tool[1...M]', 'MI_GAL_Enable[1...M]', 'MI_AIS_Period/CoS/OAM_Tool[1...M]', 'MI_GAL_Enable[1...M]', 'MI_cUPM', 'MI_cEXM', 'MI_cLFD', 'MI_cPLM', 'MI_CI_LStack[1...M]', 'SCC_CI_D', and 'SCC_CI_SSF'. A parameter 'CMuxActive = false' is indicated. The diagram is labeled G.8121-Y.1381(18)_F11-4.](3349dc82c6333221b0610be6ee7250b6_img.jpg) + +Figure 11-4 – Sn/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of a network element. At the top, multiple 'MT\_CI\_SSF' inputs (labeled 1 to M) enter a 'Consequent action' block. Below this, there are 'Selector' blocks with 'Normal' and 'LCK' options, followed by 'AIS insert' and 'LCK generate' blocks. These are connected to 'TC/Label processes', which in turn connect to a 'Label stack copy' block. The 'Label stack copy' block feeds into 'MPLS-TP specific GFP-F processes'. Below this are 'Common GFP-F processes', 'VC-n specific GFP-F processes', and another 'VC-n specific processes' block at the bottom. Various input and output signals are shown, such as 'MI\_Label[1...M]', 'MI\_LSPType[1...M]', 'MI\_CoS[1...M]', 'MI\_PHB2TCMapping[1...M]', 'MI\_QoSEncodingModel[1...M]', 'MI\_Mode[1...M]', 'MI\_LastInvalidUPI', 'MI\_SCCType', 'MI\_AcEXI', 'MI\_AcSL', 'MI\_Admin\_State', 'MI\_LCK\_Period/CoS/OAM\_Tool[1...M]', 'MI\_GAL\_Enable[1...M]', 'MI\_AIS\_Period/CoS/OAM\_Tool[1...M]', 'MI\_GAL\_Enable[1...M]', 'MI\_cUPM', 'MI\_cEXM', 'MI\_cLFD', 'MI\_cPLM', 'MI\_CI\_LStack[1...M]', 'SCC\_CI\_D', and 'SCC\_CI\_SSF'. A parameter 'CMuxActive = false' is indicated. The diagram is labeled G.8121-Y.1381(18)\_F11-4. + +**Figure 11-4 – Sn/MT\_A\_Sk process diagram** + +– *Selector generation process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +– *AIS insert process:* + +See clause 8.6.2. There is a single AIS insert process for each MT. + +– *LCK generation process:* + +See clause 8.6.3. There is a single LCK generation process for each MT. + +– *TC/Label sink processes:* + +See clause 8.2.2. + +– *Label stack copy process:* + +See clause 8.2.3. + +– *MPLS-TP-specific GFP-F sink process:* + +See clause 8.4.2. + +– *Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *VC-n specific GFP sink process* + +See clause 8.5.2.2 of [ITU-T G.806]. The GFP frames are demapped from the VC-n payload area according to clause 10.6 of [ITU-T G.707]. + +– *VC-n-specific sink process:* + +**C2:** The signal label is recovered from the C2 byte as per clause 6.2.4.2 of [ITU-T G.806]. The signal label for "GFP mapping" in Table 9-11 of [ITU-T G.707] shall be expected. The accepted value of the signal label is also available at the Sn/MT\_A\_Sk\_MP. + +##### **Defects:** + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### **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 ← dPLM and (not AI\_TSF) + +cLFD ← dLFD and (not dPLM) and (not AI\_TSF) + +cEXM ← dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM ← dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### **Performance monitoring:** + +For further study. + +### **11.1.2 LCAS-capable VC-n to MPLS-TP adaptation functions (Sn-X-L/MT\_A; n=3, 4)** + +#### **11.1.2.1 LCAS-capable VC-n to MPLS-TP adaptation source function (Sn-X-L/MT\_A\_So)** + +This function maps MT\_CI information onto a Sn-X-L\_AI signal (n=3, 4). + +Data at the Sn-X-L\_AP is a VC-n-X (n = 3, 4), having a payload as described in [ITU-T G.707], but with indeterminate path overhead (POH) bytes: J1, B3, G1. + +##### Symbol + +The Sn-X-L/MT\_A\_So function symbol is shown in Figure 11-5. + +![Figure 11-5 – Sn-X-L/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'Sn-X-L/MT_A_So'. Inputs from the top include 'SCC_CI' and multiple 'MT_CI' signals (indicated by arrows and an ellipsis). Inputs from the bottom include 'Sn-X-L_AI_X_AT' (indicated by an upward arrow) and 'Sn-X-L_AI_D' (indicated by a downward arrow). Outputs to the right include 'Sn-X-L/MT_A_So_MI' and 'Sn-X-L_TI' (both indicated by rightward arrows). A small note 'G.8121-Y.1381(13)_F11-5' is present at the bottom right of the diagram.](0b2ee589f5c7802f3d332f421340cae1_img.jpg) + +Figure 11-5 – Sn-X-L/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'Sn-X-L/MT\_A\_So'. Inputs from the top include 'SCC\_CI' and multiple 'MT\_CI' signals (indicated by arrows and an ellipsis). Inputs from the bottom include 'Sn-X-L\_AI\_X\_AT' (indicated by an upward arrow) and 'Sn-X-L\_AI\_D' (indicated by a downward arrow). Outputs to the right include 'Sn-X-L/MT\_A\_So\_MI' and 'Sn-X-L\_TI' (both indicated by rightward arrows). A small note 'G.8121-Y.1381(13)\_F11-5' is present at the bottom right of the diagram. + +**Figure 11-5 – Sn-X-L/MT\_A\_So symbol** + +##### Interfaces + +The Sn-X-L/MT\_A\_So interfaces are described in Table 11-3. + +**Table 11-3 – Sn-X-L/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Sn-X-L_AP:
Sn-X-L_AI_X_AT
Sn-X-L_TP:
Sn-X-L_TI_Clock
Sn-X-L_TI_FrameStart
Sn-X-L/MT_A_So_MP:
Sn-X-L/MT_A_So_MI_SCCType
Sn-X-L/MT_A_So_MI_Label[1...M]
Sn-X-L/MT_A_So_MI_LSPTYPE[1...M]
Sn-X-L/MT_A_So_MI_CoS[1...M]
Sn-X-L/MT_A_So_PHB2TCMapping[1...M]
Sn-X-L/MT_A_So_MI_QoSEncodingMode[1...M]
Sn-X-L/MT_A_So_MI_Mode[1...M]
Sn-X-L/MT_A_So_MI_GAL_Enable[1...M] | Sn-X-L_AP:
Sn-X-L_AI_Data
Sn-X-L_AI_Clock
Sn-X-L_AI_FrameStart | + +##### Processes + +A process diagram of this function is shown in Figure 11-6. + +![Figure 11-6 – Sn-X-L/MT_A_So process diagram. This flowchart illustrates the data processing pipeline for the Sn-X-L/MT_A_So function. Inputs include MT_CI_D[1] to MT_CI_D[M], SCC_CI, MI_Label[1..M], MI_LSPTYPE[1..M], MI_CoS[1..M], MI_PHB2TCMapping[1..M], MI_QoSEncodingModel[1..M], MI_Mode[1..M], Sn-X-L_AI_X_AT, and MI_SCCType. The process flows through TC/Label processes, Queuing, MPLS-TP specific GFP-F processes, Common GFP-F processes (conditional on CMuxActive = false), VC-n specific GFP-F processes, and VC-n specific processes. The final outputs are Sn-X-L_AI_D, Sn-X-L_AI_CK, and Sn-X-L_AI_FS. A dashed line indicates a conditional path for the Common GFP-F processes based on CMuxActive = false.](2c41e286ea9a1b008d3beb348d86096f_img.jpg) + +The diagram shows the following process flow: + +- Inputs:** + - MT\_CI\_D[1] . . . MT\_CI\_D[M] + - SCC\_CI + - MI\_Label[1..M], MI\_LSPTYPE[1..M], MI\_CoS[1..M], MI\_PHB2TCMapping[1..M], MI\_QoSEncodingModel[1..M], MI\_Mode[1..M] + - Sn-X-L\_AI\_X\_AT + - MI\_SCCType +- TC/Label processes:** Receives MT\_CI\_D inputs and MI parameters. Output: Muxed MT\_CI\_D. +- Queuing:** Receives Muxed MT\_CI\_D and Sn-X-L\_AI\_X\_AT. Output: Muxed MT\_CI\_D. +- MPLS-TP specific GFP-F processes:** Receives Muxed MT\_CI\_D, SCC\_CI, and MI\_SCCType. Output: GFP\_FS, GFP\_Frame. +- Common GFP-F processes:** Conditional block (CMuxActive = false). Receives GFP\_FS, GFP\_Frame. Output: GFP\_FS, GFP\_Frame. +- VC-n specific GFP-F processes:** Receives GFP\_FS, GFP\_Frame, Sn-X-L\_AI\_D, Sn-X-L\_AI\_CK, and Sn-X-L\_AI\_FS. Output: Sn-X-L\_AI\_D, Sn-X-L\_AI\_CK, Sn-X-L\_AI\_FS. +- VC-n specific processes:** Receives Sn-X-L\_AI\_D, Sn-X-L\_AI\_CK, and Sn-X-L\_AI\_FS. Output: Sn-X-L\_AI\_D, Sn-X-L\_AI\_CK, Sn-X-L\_AI\_FS. + +G.8121-Y.1381(18)\_F11-6 + +Figure 11-6 – Sn-X-L/MT\_A\_So process diagram. This flowchart illustrates the data processing pipeline for the Sn-X-L/MT\_A\_So function. Inputs include MT\_CI\_D[1] to MT\_CI\_D[M], SCC\_CI, MI\_Label[1..M], MI\_LSPTYPE[1..M], MI\_CoS[1..M], MI\_PHB2TCMapping[1..M], MI\_QoSEncodingModel[1..M], MI\_Mode[1..M], Sn-X-L\_AI\_X\_AT, and MI\_SCCType. The process flows through TC/Label processes, Queuing, MPLS-TP specific GFP-F processes, Common GFP-F processes (conditional on CMuxActive = false), VC-n specific GFP-F processes, and VC-n specific processes. The final outputs are Sn-X-L\_AI\_D, Sn-X-L\_AI\_CK, and Sn-X-L\_AI\_FS. A dashed line indicates a conditional path for the Common GFP-F processes based on CMuxActive = false. + +Figure 11-6 – Sn-X-L/MT\_A\_So process diagram + +The processes have the same definition as in clause 11.1.1.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.1.2.2 LCAS-capable VC-n to MPLS-TP adaptation sink function (Sn-X-L/MT\_A\_Sk) + +This function extracts MT\_CI information from the Sn-X-L\_AI signal (n=3, 4), delivering MT\_CI. + +Data at the Sn-X-L\_AP is a VC-n-Xv (n=3, 4) but with indeterminate POH bytes J1, B3, G1, as per [ITU-T G.707]. + +##### Symbol + +The Sn-X-L/MT\_A\_Sk function symbol is shown in Figure 11-7. + +![Figure 11-7: Sn-X-L/MT_A_Sk symbol diagram. The symbol is a trapezoid labeled 'Sn-X-L/MT_A_Sk'. It has multiple input arrows on the left: 'SCC_CI', 'MT_CI', and an ellipsis '...'. It has one output arrow on the right labeled 'Sn-X-L/MT_A_Sk_MI'. At the bottom, there are two input arrows: 'Sn-X-L_AI_X_AR' and 'Sn-X-L_AI_D'. A small note 'G.8121-Y.1381(13)_F11-7' is present at the bottom right.](ae57a92114d2bd84ef81129e7fbdd89d_img.jpg) + +Figure 11-7: Sn-X-L/MT\_A\_Sk symbol diagram. The symbol is a trapezoid labeled 'Sn-X-L/MT\_A\_Sk'. It has multiple input arrows on the left: 'SCC\_CI', 'MT\_CI', and an ellipsis '...'. It has one output arrow on the right labeled 'Sn-X-L/MT\_A\_Sk\_MI'. At the bottom, there are two input arrows: 'Sn-X-L\_AI\_X\_AR' and 'Sn-X-L\_AI\_D'. A small note 'G.8121-Y.1381(13)\_F11-7' is present at the bottom right. + +**Figure 11-7 – Sn-X-L/MT\_A\_Sk symbol** + +##### Interfaces + +The Sn-X-L/MT\_A\_Sk interfaces are described in Table 11-4. + +**Table 11-4 – Sn-X-L/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Sn-X-L_AP:
Sn-X-L_AI_Data
Sn-X-L_AI_Clock
Sn-X-L_AI_FrameStart
Sn-X-L_AI_TSF
Sn-X-L_AI_X AR
Sn-X-L/MT_A_Sk_MP:
Sn-X-L/MT_A_Sk_MI_SCCType
Sn-X-L/MT_A_Sk_MI_Label[1...M]
Sn-X-L/MT_A_Sk_MI_LSPTYPE[1...M]
Sn-X-L/MT_A_Sk_MI_CoS[1...M]
Sn-X-L/MT_A_Sk_MI_TC2PHBMapping[1...M]
Sn-X-L/MT_A_Sk_MI_QoSDecodingMode[1...M]
Sn-X-L/MT_A_Sk_MI_Mode[1...M]
Sn-X-L/MT_A_Sk_MI_LCK_Period[1...M]
Sn-X-L/MT_A_Sk_MI_LCK_CoS[1...M]
Sn-X-L/MT_A_Sk_MI_Admin_State
Sn-X-L/MT_A_Sk_MI_AIS_Period[1...M]
Sn-X-L/MT_A_Sk_MI_AIS_CoS [1...M]
Sn-X-L/MT_A_Sk_MI_GAL_Enable [1...M]
Sn-X-L/MT_A_Sk_MI_LCK_OAM_Tool [1...M]
Sn-X-L/MT_A_Sk_MI_AIS_OAM_Tool [1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MI_CI_LStack

SCC_CP:
SCC_CI_Data
SCC_CI_SSF

Sn-X-L/MT_A_Sk_MP:
Sn-X-L/MT_A_Sk_MI_AcSL
Sn-X-L/MT_A_Sk_MI_AcEXI
Sn-X-L/MT_A_Sk_MI_LastInvalidUPI
Sn-X-L/MT_A_Sk_MI_cPLM
Sn-X-L/MT_A_Sk_MI_cLFD
Sn-X-L/MT_A_Sk_MI_cEXM
Sn-X-L/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-8. + +![Figure 11-8 – Sn-X-L/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of the Sn-X-L/MT_A_Sk function. At the bottom, multiple input interfaces (Sn_X-L_AI_D/CK/SF/TSF, Sn-X-L_AI_X_AT) feed into 'VC-n specific processes'. These connect to 'VC-n specific GFP-F processes', which then connect to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' is present near the 'Common GFP-F processes'. Above 'Common GFP-F processes' is 'MPLS-TP specific GFP-F processes', which connects to 'Label stack copy'. 'Label stack copy' feeds into 'TC/Label processes', which in turn feed into 'Consequent action' blocks. 'Consequent action' blocks output to 'Selector' blocks (Normal, LCK), which then output to 'MT_CI_D/iPHB/oPHB' interfaces. Various management interfaces (MI_Label, MI_LSPTYPE, MI_CoS, MI_PHB2TCMapping, MI_QoSEncodingModel, MI_Mode, MI_LastInvalidUPI, MI_SCCType, MI_AcEXI, MI_AcSL, MI_Admin_State, MI_LCK_Period/CoS/OAM_Tool, MI_GAL_Enable, MI_AIS_Period/CoS/OAM_Tool, MI_GAL_Enable, MI_cUPM, MI_cEXM, MI_cLFD, MI_cPLM) are shown on the left and right sides, connected to various process blocks. The diagram is labeled G.8121-Y.1381(18)_F11-8 in the bottom right corner.](c05763eff20551449de1eac378fed769_img.jpg) + +Figure 11-8 – Sn-X-L/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of the Sn-X-L/MT\_A\_Sk function. At the bottom, multiple input interfaces (Sn\_X-L\_AI\_D/CK/SF/TSF, Sn-X-L\_AI\_X\_AT) feed into 'VC-n specific processes'. These connect to 'VC-n specific GFP-F processes', which then connect to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' is present near the 'Common GFP-F processes'. Above 'Common GFP-F processes' is 'MPLS-TP specific GFP-F processes', which connects to 'Label stack copy'. 'Label stack copy' feeds into 'TC/Label processes', which in turn feed into 'Consequent action' blocks. 'Consequent action' blocks output to 'Selector' blocks (Normal, LCK), which then output to 'MT\_CI\_D/iPHB/oPHB' interfaces. Various management interfaces (MI\_Label, MI\_LSPTYPE, MI\_CoS, MI\_PHB2TCMapping, MI\_QoSEncodingModel, MI\_Mode, MI\_LastInvalidUPI, MI\_SCCType, MI\_AcEXI, MI\_AcSL, MI\_Admin\_State, MI\_LCK\_Period/CoS/OAM\_Tool, MI\_GAL\_Enable, MI\_AIS\_Period/CoS/OAM\_Tool, MI\_GAL\_Enable, MI\_cUPM, MI\_cEXM, MI\_cLFD, MI\_cPLM) are shown on the left and right sides, connected to various process blocks. The diagram is labeled G.8121-Y.1381(18)\_F11-8 in the bottom right corner. + +**Figure 11-8 – Sn-X-L/MT\_A\_Sk process diagram** + +See process diagram and process description in clause 11.1.1.2. The additional Sn-X-L\_AI\_XAR interface is not connected to any of the internal processes. + +##### Defects: + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +##### Consequent actions: + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### **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) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### **Performance monitoring:** + +For further study. + +### **11.1.3 VC-m to MPLS-TP adaptation functions (Sm/MT\_A; m=11, 11-X, 12, 12-X)** + +#### **11.1.3.1 VC-m to MPLS-TP adaptation source function (Sm/MT\_A\_So)** + +This function maps MT\_CI information onto a Sm\_AI signal (m=11, 11-X, 12, 12-X). + +Data at the Sm\_AP is a VC-m (m = 11, 11-X, 12, 12-X), having a payload as described in [ITU-T G.707], but with indeterminate POH bytes: J2, V5[1-4], V5[8]. + +##### **Symbol** + +The Sm/MT\_A\_So function symbol is shown in Figure 11-9. + +![Diagram of Sm/MT_A_So function symbol. It shows a trapezoidal block labeled 'Sm/MT_A_So'. Inputs from the top include SCC_CI, MT_CI, and an ellipsis. An output labeled Sm_AI points downwards. On the right side, two bidirectional arrows represent interfaces labeled Sm/MT_A_So_MI and Sm_TI. A small text 'G.8121-Y.1381(13)_F11-9' is at the bottom right.](72d375793611d82866edc20cb031d867_img.jpg) + +Diagram of Sm/MT\_A\_So function symbol. It shows a trapezoidal block labeled 'Sm/MT\_A\_So'. Inputs from the top include SCC\_CI, MT\_CI, and an ellipsis. An output labeled Sm\_AI points downwards. On the right side, two bidirectional arrows represent interfaces labeled Sm/MT\_A\_So\_MI and Sm\_TI. A small text 'G.8121-Y.1381(13)\_F11-9' is at the bottom right. + +**Figure 11-9 – Sm/MT\_A\_So symbol** + +##### **Interfaces** + +The Sm/MT\_A\_So interfaces are described in Table 11-5. + +**Table 11-5 – Sm/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Sm_TP:
Sm_TI_Clock
Sm_TI_FrameStart | Sm_AP:
Sm_AI_Data
Sm_AI_Clock
Sm_AI_FrameStart | + +**Table 11-5 – Sm/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Sm/MT_A_So_MP:
Sm/MT_A_So_MI_SCCType
Sm/MT_A_So_MI_Label[1..M]
Sm/MT_A_So_MI_LSPTYPE[1..M]
Sm/MT_A_So_MI_CoS[1..M]
Sm/MT_A_So_PHB2TCMapping[1..M]
Sm/MT_A_So_MI_QoS_ENCODINGMode[1..M]
Sm/MT_A_So_MI_Mode[1..M]
Sm/MT_A_So_MI_GAL_Enable[1..M] | | + +##### **Processes** + +A process diagram of this function is shown in Figure 11-10. + +![Figure 11-10 – Sm/MT_A_So process diagram. This flowchart illustrates the data processing pipeline for Sm/MT_A_So. Inputs include MT_CI_D[1] to MT_CI_D[M], SCC_CI, and various MI parameters (Label, LSPType, CoS, PHB2TCMapping, QoS_ENCODINGMode, Mode). The flow starts with TC/Label processes, followed by Queuing, then MPLS-TP specific GFP-F processes, Common GFP-F processes (with CMuxActive = false), VC-n specific GFP-F processes (receiving Sm_TI_CK and Sm_TI_FS), and finally VC-n specific processes. The output consists of Sm_AI_D, Sm_AI_CK, and Sm_AI_FS.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +``` + +graph TD + subgraph Inputs + direction TB + I1[MT_CI_D[1] ... MT_CI_D[M]] + I2[SCC_CI] + I3["MI_Label[1..M] +MI_LSPType[1..M] +MI_CoS[1..M] +MI_PHB2TCMapping[1..M] +MI_QoS_ENCODINGMode[1..M] +MI_Mode[1..M]"] + I4[MI_SCCType] + end + + subgraph Processes + direction TB + P1[TC/Label processes] + P2[Queuing] + P3[MPLS-TP specific GFP-F processes] + P4[Common GFP-F processes] + P5[VC-n specific GFP-F processes] + P6[VC-n specific processes] + end + + I1 --> P1 + I2 --> P3 + I3 --> P1 + I4 --> P3 + + P1 -- "Mixed MT_CI_D" --> P2 + P2 --> P3 + P3 -- "GFP_FS, GFP_Frame" --> P4 + P4 -- "GFP_FS, GFP_Frame" --> P5 + P5 -- "Sm_AI_D, Sm_AI_CK, Sm_AI_FS" --> P6 + P6 -- "Sm_AI_D, Sm_AI_CK, Sm_AI_FS" --> O1[Sm_AI_D] + P6 -- "Sm_AI_D, Sm_AI_CK, Sm_AI_FS" --> O2[Sm_AI_CK] + P6 -- "Sm_AI_D, Sm_AI_CK, Sm_AI_FS" --> O3[Sm_AI_FS] + + CMuxActive[CMuxActive = false] -.-> P4 + Sm_TI_CK[Sm_TI_CK] --> P5 + Sm_TI_FS[Sm_TI_FS] --> P5 + +``` + +Figure 11-10 – Sm/MT\_A\_So process diagram. This flowchart illustrates the data processing pipeline for Sm/MT\_A\_So. Inputs include MT\_CI\_D[1] to MT\_CI\_D[M], SCC\_CI, and various MI parameters (Label, LSPType, CoS, PHB2TCMapping, QoS\_ENCODINGMode, Mode). The flow starts with TC/Label processes, followed by Queuing, then MPLS-TP specific GFP-F processes, Common GFP-F processes (with CMuxActive = false), VC-n specific GFP-F processes (receiving Sm\_TI\_CK and Sm\_TI\_FS), and finally VC-n specific processes. The output consists of Sm\_AI\_D, Sm\_AI\_CK, and Sm\_AI\_FS. + +G.8121-Y.1381(18)\_F11-10 + +**Figure 11-10 – Sm/MT\_A\_So process diagram** + +- *TC/Label processes:* +See clause 8.2.1. +- *Queuing process:* +See clause 8.3. +- *MPLS-TP-specific GFP-F source process:* +See clause 8.4.1. + +– *Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *VC-m-specific GFP source process:* + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the VC-m payload area according to clause 10.6 of [ITU-T G.707]. + +– *VC-m-specific source process:* + +**V5[5-7] and K4[1]:** Signal label information is derived directly from the Adaptation function type. The value for "GFP mapping" in Table 9-13 of [ITU-T G.707] is placed in the K4[1] extended signal label field as described in clause 8.2.3.2 of [ITU-T G.783]. + +**K4[2]:** For Sm/MT\_A\_So with m = 11, 12, the K4[2] bit is sourced as all-zeros. + +NOTE 1 – For Sm/MT\_A\_So with m = 11-X, 12-X, the K4[2] bit is undefined at the Sm-X\_AP output of this function (as per clause 13 of [ITU-T G.783]). + +NOTE 2 – For Sm/MT\_A\_So with m = 11, 11-X, 12, 12-X, 2, the K4[3-8], V5[1-4] and V5[8] bits are undefined at the Sm-X\_AP output of this function (as per clause 13 of [ITU-T G.783]). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.1.3.2 VC-m to MPLS-TP adaptation sink function (Sm/MT\_A\_Sk) + +This function extracts MT\_CI information from the Sm\_AI signal (m=11, 11-X, 12, 12-X), delivering MT\_CI. + +Data at the Sm\_AP is a VC-m (m=11, 11-X, 12, 12-X) but with indeterminate POH bytes J2, V5[1-4], V5[8], as per [ITU-T G.707]. + +##### Symbol + +The Sm/MT\_A\_Sk function symbol is shown in Figure 11-11. + +![Figure 11-11 – Sm/MT_A_Sk symbol. The diagram shows a trapezoidal block labeled 'Sm/MT_A_Sk'. An input arrow labeled 'Sm_AI' points into the bottom of the block. An output arrow labeled 'Sm/MT_A_Sk_MI' points out from the right side of the block. Multiple output arrows point upwards from the top of the block, labeled 'SCC_CI', 'MT_CI', and '...' (ellipsis). A small text label 'G.8121-Y.1381(13)_F11-11' is located at the bottom right of the diagram.](5603d6dc13a0dc1c6fff98ae9690daf3_img.jpg) + +Figure 11-11 – Sm/MT\_A\_Sk symbol. The diagram shows a trapezoidal block labeled 'Sm/MT\_A\_Sk'. An input arrow labeled 'Sm\_AI' points into the bottom of the block. An output arrow labeled 'Sm/MT\_A\_Sk\_MI' points out from the right side of the block. Multiple output arrows point upwards from the top of the block, labeled 'SCC\_CI', 'MT\_CI', and '...' (ellipsis). A small text label 'G.8121-Y.1381(13)\_F11-11' is located at the bottom right of the diagram. + +**Figure 11-11 – Sm/MT\_A\_Sk symbol** + +##### Interfaces + +The Sm/MT\_A\_Sk interfaces are described in Table 11-6. + +**Table 11-6 – Sm/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Sm_AP:
Sm_AI_Data
Sm_AI_Clock
Sm_AI_FrameStart
Sm_AI_TSF
Sm/MT_A_Sk_MP:
Sm/MT_A_Sk_MI_SCCType
Sm/MT_A_Sk_MI_Label[1...M]
Sm/MT_A_Sk_MI_LSPTYPE[1...M]
Sm/MT_A_Sk_MI_CoS[1...M]
Sm/MT_A_Sk_MI_TC2PHBMapping[1...M]
Sm/MT_A_Sk_MI_QoSDecodingMode[1...M]
Sm/MT_A_Sk_MI_Mode[1...M]
Sm/MT_A_Sk_MI_LCK_Period[1...M]
Sm/MT_A_Sk_MI_LCK_CoS[1...M]
Sm/MT_A_Sk_MI_Admin_State
Sm/MT_A_Sk_MI_AIS_Period[1...M]
Sm/MT_A_Sk_MI_AIS_CoS[1...M]
Sm/MT_A_Sk_MI_GAL_Enable[1...M]
Sm/MT_A_Sk_MI_LCK_OAM_Tool [1...M]
Sm/MT_A_Sk_MI_AIS_OAM_Tool[1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MI_CI_LStack

SCC_CP:
SCC_CI_Data
SCC_CI_SSF

Sm/MT_A_Sk_MP:
Sm/MT_A_Sk_MI_AcSL
Sm/MT_A_Sk_MI_AcEXI
Sm/MT_A_Sk_MI_LastInvalidUPI
Sm/MT_A_Sk_MI_cPLM
Sm/MT_A_Sk_MI_cLFD
Sm/MT_A_Sk_MI_cEXM
Sm/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-12. + +![Figure 11-12 – Sm/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of a transport system. At the top, multiple MT_CI_SSF inputs (1 to M) and MT_CI_D inputs (1 to M) are shown. These connect to 'Selector' blocks containing 'Normal' and 'LCK' options. Below the selectors are 'AIS insert' and 'LCK generate' blocks, which receive inputs like 'aAIS', 'D, iPHB, oPHB', and management parameters (MI_Admin_State, MI_LCK_Period/CoS/OAM_Tool, MI_AIS_Period/CoS/OAM_Tool, MI_GAL_Enable). These blocks feed into 'TC/Label processes', which also receive 'Mixed D' and 'Mixed LStack' inputs. Below that is a 'Label stack copy' block receiving 'Client_SF' and 'Mixed MT_CI_D'. This is followed by 'MPLS-TP specific GFP-F processes', 'Common GFP-F processes' (with CMuxActive=false), 'VC-n specific GFP-F processes', and finally 'VC-n specific processes' at the bottom. Various management interfaces (MI_Label, MI_LSPTYPE, MI_CoS, MI_PHB2TCMapping, MI_QoSEncodingModel, MI_Mode, MI_LastInvalidUPI, MI_SCCType, MI_AcEXI, MI_AcSL, MI_cUPM, MI_cEXM, MI_cLFD, MI_cPLM) are shown as inputs or outputs to these process blocks. The diagram is labeled G.8121-Y.1381(18)_F11-12.](92e26d86c5a582766cb9afdbd2c1aee7_img.jpg) + +Figure 11-12 – Sm/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of a transport system. At the top, multiple MT\_CI\_SSF inputs (1 to M) and MT\_CI\_D inputs (1 to M) are shown. These connect to 'Selector' blocks containing 'Normal' and 'LCK' options. Below the selectors are 'AIS insert' and 'LCK generate' blocks, which receive inputs like 'aAIS', 'D, iPHB, oPHB', and management parameters (MI\_Admin\_State, MI\_LCK\_Period/CoS/OAM\_Tool, MI\_AIS\_Period/CoS/OAM\_Tool, MI\_GAL\_Enable). These blocks feed into 'TC/Label processes', which also receive 'Mixed D' and 'Mixed LStack' inputs. Below that is a 'Label stack copy' block receiving 'Client\_SF' and 'Mixed MT\_CI\_D'. This is followed by 'MPLS-TP specific GFP-F processes', 'Common GFP-F processes' (with CMuxActive=false), 'VC-n specific GFP-F processes', and finally 'VC-n specific processes' at the bottom. Various management interfaces (MI\_Label, MI\_LSPTYPE, MI\_CoS, MI\_PHB2TCMapping, MI\_QoSEncodingModel, MI\_Mode, MI\_LastInvalidUPI, MI\_SCCType, MI\_AcEXI, MI\_AcSL, MI\_cUPM, MI\_cEXM, MI\_cLFD, MI\_cPLM) are shown as inputs or outputs to these process blocks. The diagram is labeled G.8121-Y.1381(18)\_F11-12. + +**Figure 11-12 – Sm/MT\_A\_Sk process diagram** + +– *Selector generation process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +– *AIS insert process:* + +See clause 8.6.2. There is a single AIS insert process for each MT. + +– *LCK generation process:* + +See clause 8.6.3. There is a single LCK generation process for each MT. + +– *TC/Label sink processes:* + +See clause 8.2.2. + +– *Label stack copy process:* + +See clause 8.2.3. + +– *MPLS-TP specific GFP-F sink process:* + +See clause 8.4.2. + +– *Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *VC-m-specific GFP sink process:* + +See clause 8.5.2.2 of [ITU-T G.806]. The GFP frames are demapped from the VC-m payload area according to clause 10.6 of [ITU-T G.707]. + +– *VC-m-specific sink process:* + +**V5[5-7] and K4[1]:** The signal label is recovered from the extended signal label position as described in clause 8.2.3.2 of [ITU-T G.783] and clause 6.2.4.2 of [ITU-T G.806]. The signal label for "GFP mapping" in Table 9-13 of [ITU-T G.707] shall be expected. The accepted value of the signal label is also available at the Sm/MT\_A\_Sk\_MP. + +##### **Defects:** + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### **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) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### **Performance monitoring:** + +For further study. + +### **11.1.4 LCAS-capable VC-m to MPLS-TP adaptation functions (Sm-X-L/MT\_A; $m=11, 12$ )** + +#### **11.1.4.1 LCAS-capable VC-m to MPLS-TP adaptation source function (Sm-X-L/MT\_A\_So)** + +This function maps MT\_CI information onto a Sm-X-L\_AI signal ( $m=11, 12$ ). + +Data at the Sm-X-L\_AP is a VC-m-X ( $m = 11, 12$ ), having a payload as described in [ITU-T G.707], but with indeterminate POH bytes: J2, V5[1-4], V5[8]. + +##### Symbol + +The Sm-X-L/MT\_A\_So function symbol is shown in Figure 11-13. + +![Figure 11-13 – Sm-X-L/MT_A_So symbol diagram. The diagram shows a trapezoidal block labeled 'Sm-X-L/MT_A_So'. Inputs from the top include SCC_CI and multiple MT_CI signals (indicated by an ellipsis). Inputs from the bottom include Sm-X-L_AI_X_AT and Sm-X-L_AI_D. Outputs to the right include Sm-X-L/MT_A_So_MI and Sm-X-L_TI. A return output Sm-X-L_AI_D is shown at the bottom. The diagram is labeled G.8121-Y.1381(13)_F11-13.](2d8e8a86768f5861aef582d938c0597d_img.jpg) + +Figure 11-13 – Sm-X-L/MT\_A\_So symbol diagram. The diagram shows a trapezoidal block labeled 'Sm-X-L/MT\_A\_So'. Inputs from the top include SCC\_CI and multiple MT\_CI signals (indicated by an ellipsis). Inputs from the bottom include Sm-X-L\_AI\_X\_AT and Sm-X-L\_AI\_D. Outputs to the right include Sm-X-L/MT\_A\_So\_MI and Sm-X-L\_TI. A return output Sm-X-L\_AI\_D is shown at the bottom. The diagram is labeled G.8121-Y.1381(13)\_F11-13. + +**Figure 11-13 – Sm-X-L/MT\_A\_So symbol** + +##### Interfaces + +The Sm-X-L/MT\_A\_So interfaces are described in Table 11-7. + +**Table 11-7 – Sm-X-L/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Sm-X-L_AP:
Sm-X-L_AI_X_AT
Sm-X-L_TP:
Sm-X-L_TI_Clock
Sm-X-L_TI_FrameStart
Sm-X-L/MT_A_So_MP:
Sm-X-L/MT_A_So_MI_SCCType
Sm-X-L/MT_A_So_MI_Label[1...M]
Sm-X-L/MT_A_So_MI_LSPTYPE[1...M]
Sm-X-L/MT_A_So_MI_CoS[1...M]
Sm-X-L/MT_A_So_MI_PHB2TCMapping[1...M]
Sm-X-L/MT_A_So_MI_QoSEncodingMode[1...M]
Sm-X-L/MT_A_So_MI_Mode[1...M]
Sm-X-L/MT_A_So_MI_GAL_Enable[1...M] | Sm-X-L_AP:
Sm-X-L_AI_Data
Sm-X-L_AI_Clock
Sm-X-L_AI_FrameStart | + +##### Processes + +A process diagram of this function is shown in Figure 11-14. + +![Figure 11-14 – Sm-X-L/MT_A_So process diagram. This flowchart illustrates the data processing pipeline for the Sm-X-L/MT_A_So function. Inputs include MT_CI_D[1] through MT_CI_D[M], SCC_CI, MI_Label[1...M], MI_LSPTYPE[1...M], MI_CoS[1...M], MI_PHB2TCMapping[1...M], MI_QoSEncodingModel[1...M], MI_Mode[1...M], Sm-X-L_AI_X_AT, and MI_SCCType. The process starts with TC/Label processes, followed by Queueing, MPLS-TP specific GFP-F processes, Common GFP-F processes (conditional on CMuxActive = false), VC-n specific GFP-F processes, and finally VC-n specific processes. The output consists of Sm-X-L_AI_D, Sm-X-L_AI_CK, and Sm-X-L_AI_FS. Control signals Sm-X-L_TI_CK and Sm-X-L_TI_FS are also shown.](387a316ca4f909a5260b0c5e232d5cc8_img.jpg) + +The diagram shows a vertical flow of data through several processing blocks. At the top, multiple inputs $MT\_CI\_D[1] \dots MT\_CI\_D[M]$ and $SCC\_CI$ enter a grey-shaded area. Inside, the first block is 'TC/Label processes', which also receives a group of inputs: $MI\_Label[1\dots M]$ , $MI\_LSPTYPE[1\dots M]$ , $MI\_CoS[1\dots M]$ , $MI\_PHB2TCMapping[1\dots M]$ , $MI\_QoSEncodingModel[1\dots M]$ , and $MI\_Mode[1\dots M]$ . The output of this block is 'Muxed $MT\_CI\_D$ '. This signal goes to a 'Queueing' block, which also receives $Sm-X-L\_AI\_X_{AT}$ . The output of 'Queueing' goes to 'MPLS-TP specific GFP-F processes', which also receives $MI\_SCCType$ . The output of this block is split into 'GFP\\_FS' and 'GFP\\_Frame'. These go to 'Common GFP-F processes', which is also influenced by a dashed arrow labeled $CMuxActive = false$ . The output of 'Common GFP-F processes' is again split into 'GFP\\_FS' and 'GFP\\_Frame'. These go to 'VC-n specific GFP-F processes', which also receives $Sm-X-L\_TI\_CK$ and $Sm-X-L\_TI\_FS$ . The output of 'VC-n specific GFP-F processes' is split into $Sm-X-L\_AI\_D$ , $Sm-X-L\_AI\_CK$ , and $Sm-X-L\_AI\_FS$ . These three signals go to the final block, 'VC-n specific processes'. The output of this final block is the same three signals: $Sm-X-L\_AI\_D$ , $Sm-X-L\_AI\_CK$ , and $Sm-X-L\_AI\_FS$ , which exit the grey-shaded area. A small text 'G.8121-Y.1381(18)\_F11-14' is at the bottom right. + +Figure 11-14 – Sm-X-L/MT\_A\_So process diagram. This flowchart illustrates the data processing pipeline for the Sm-X-L/MT\_A\_So function. Inputs include MT\_CI\_D[1] through MT\_CI\_D[M], SCC\_CI, MI\_Label[1...M], MI\_LSPTYPE[1...M], MI\_CoS[1...M], MI\_PHB2TCMapping[1...M], MI\_QoSEncodingModel[1...M], MI\_Mode[1...M], Sm-X-L\_AI\_X\_AT, and MI\_SCCType. The process starts with TC/Label processes, followed by Queueing, MPLS-TP specific GFP-F processes, Common GFP-F processes (conditional on CMuxActive = false), VC-n specific GFP-F processes, and finally VC-n specific processes. The output consists of Sm-X-L\_AI\_D, Sm-X-L\_AI\_CK, and Sm-X-L\_AI\_FS. Control signals Sm-X-L\_TI\_CK and Sm-X-L\_TI\_FS are also shown. + +Figure 11-14 – Sm-X-L/MT\_A\_So process diagram + +The processes have the same definition as in clause 11.1.1.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** *For further study.* + +#### 11.1.4.2 LCAS-capable VC-m to MPLS-TP adaptation sink function (Sm-X-L/MT\_A\_Sk) + +This function extracts $MT\_CI$ information from the $Sm-X-L\_AI$ signal ( $m=11, 12$ ), delivering $MT\_CI$ . + +Data at the $Sm-X-L\_AP$ is a VC-m-Xv ( $m=11, 12$ ) but with indeterminate POH bytes J2, V5[1-4], V5[8], as per [ITU-T G.707]. + +##### Symbol + +The Sm-X-L/MT\_A\_Sk function symbol is shown in Figure 11-15. + +![Figure 11-15 – Sm-X-L/MT_A_Sk symbol. The diagram shows a trapezoidal block labeled 'Sm-X-L/MT_A_Sk'. Inputs from the bottom are 'Sm-X-L_AI_X_AT' and 'Sm-X-L_AI_D', with a vertical dashed line between them and 'Sm-X-L_AI' below. Inputs from the top are 'SCC_CI' and 'MT_CI' (with an ellipsis between them). An output arrow on the right is labeled 'Sm-X-L/MT_A_Sk_MI'. A small note 'G.8121-Y.1381(13)_F11-15' is at the bottom right.](8159756d3acf4761a73fa0d263f1d338_img.jpg) + +Figure 11-15 – Sm-X-L/MT\_A\_Sk symbol. The diagram shows a trapezoidal block labeled 'Sm-X-L/MT\_A\_Sk'. Inputs from the bottom are 'Sm-X-L\_AI\_X\_AT' and 'Sm-X-L\_AI\_D', with a vertical dashed line between them and 'Sm-X-L\_AI' below. Inputs from the top are 'SCC\_CI' and 'MT\_CI' (with an ellipsis between them). An output arrow on the right is labeled 'Sm-X-L/MT\_A\_Sk\_MI'. A small note 'G.8121-Y.1381(13)\_F11-15' is at the bottom right. + +Figure 11-15 – Sm-X-L/MT\_A\_Sk symbol + +##### Interfaces + +The Sm-X-L/MT\_A\_Sk interfaces are described in Table 11-8. + +Table 11-8 – Sm-X-L/MT\_A\_Sk interfaces + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Sm-X-L_AP:
Sm-X-L_AI_Data
Sm-X-L_AI_ClockK
Sm-X-L_AI_FrameStart
Sm-X-L_AI_TSF
Sm-X-L_AI_X AR
Sm-X-L/MT_A_Sk_MP:
Sm-X-L/MT_A_Sk_MI_SCCType
Sm-X-L/MT_A_Sk_MI_Label[1...M]
Sm-X-L/MT_A_Sk_MI_LSPTYPE[1...M]
Sm-X-L/MT_A_Sk_MI_CoS[1...M]
Sm-X-L/MT_A_Sk_MI_TC2PHBMapping[1...M]
Sm-X-L/MT_A_Sk_MI_QoSDecodingMode[1...M]
Sm-X-L/MT_A_Sk_MI_Mode[1...M]
Sm-X-L/MT_A_Sk_MI_LCK_Period[1...M]
Sm-X-L/MT_A_Sk_MI_LCK_CoS[1...M]
Sm-X-L/MT_A_Sk_MI_Admin_State
Sm-X-L/MT_A_Sk_MI_AIS_Period[1...M]
Sm-X-L/MT_A_Sk_MI_AIS_CoS[1...M]
Sm-X-L/MT_A_Sk_MI_GAL_Enable[1...M]
Sm-X-L/MT_A_Sk_MI_LCK_OAM_Tool [1...M]
Sm-X-L/MT_A_Sk_MI_AIS_OAM_Tool [1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MI_CI_LStack
SCC_CP:
SCC_CI_Data
SCC_CI_SSF
Sm-X-L/MT_A_Sk_MP:
Sm-X-L/MT_A_Sk_MI_AcSL
Sm-X-L/MT_A_Sk_MI_AcEXI
Sm-X-L/MT_A_Sk_MI_LastInvalidUPI
Sm-X-L/MT_A_Sk_MI_cPLM
Sm-X-L/MT_A_Sk_MI_cLFD
Sm-X-L/MT_A_Sk_MI_cEXM
Sm-X-L/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-16. + +![Figure 11-16 – Sm-X-L/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of the Sm-X-L/MT_A_Sk function. At the bottom, three process blocks are stacked vertically: 'VC-n specific processes', 'VC-n specific GFP-F processes', and 'Common GFP-F processes'. Above 'Common GFP-F processes' is a block for 'MPLS-TP specific GFP-F processes'. Above that is a 'Label stack copy' block, followed by 'TC/Label processes'. At the top are two 'Selector' blocks, each with 'Normal' and 'LCK' options, and a 'Consequent action' block. Numerous interfaces are shown on the left, right, top, and bottom, with labels like MT_CI_SSF[1], MT_CI_SSF[M], MI_Label[1...M], MI_cPLM, MI_cLFD, MI_cEXM, MI_cUPM, MI_Ci_LStack[1...M], SCC_CI_D, and SCC_CI_SSF. The diagram also includes internal data flows and control signals such as aAIS, aSSF, CMuxActive, and various D, iPHB, oPHB, and LCK signals.](3a568746c00925506d5c39f2a86a5a63_img.jpg) + +Figure 11-16 – Sm-X-L/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of the Sm-X-L/MT\_A\_Sk function. At the bottom, three process blocks are stacked vertically: 'VC-n specific processes', 'VC-n specific GFP-F processes', and 'Common GFP-F processes'. Above 'Common GFP-F processes' is a block for 'MPLS-TP specific GFP-F processes'. Above that is a 'Label stack copy' block, followed by 'TC/Label processes'. At the top are two 'Selector' blocks, each with 'Normal' and 'LCK' options, and a 'Consequent action' block. Numerous interfaces are shown on the left, right, top, and bottom, with labels like MT\_CI\_SSF[1], MT\_CI\_SSF[M], MI\_Label[1...M], MI\_cPLM, MI\_cLFD, MI\_cEXM, MI\_cUPM, MI\_Ci\_LStack[1...M], SCC\_CI\_D, and SCC\_CI\_SSF. The diagram also includes internal data flows and control signals such as aAIS, aSSF, CMuxActive, and various D, iPHB, oPHB, and LCK signals. + +Figure 11-16 – Sm-X-L/MT\_A\_Sk process diagram + +See process diagram and process description in clause 11.1.1.2. The additional Sm-X-L\_AI\_XAR interface is not connected to any of the internal processes. + +##### Defects: + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +##### Consequent actions: + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_ or dPLM or dLFD or dUPM or dEXM + +##### 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) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### Performance monitoring: + +For further study. + +## 11.2 OTH to MPLS-TP adaptation function (O/MT\_A) + +### 11.2.1 ODUk to MPLS-TP adaptation functions + +#### 11.2.1.1 ODUk to MPLS-TP adaptation source function (ODUkP/MT\_A\_So) + +The ODUkP/MT\_A\_So function creates the ODUk signal from a free running clock. It maps the MT\_CI information into the payload of the OPUk, adds OPUk overhead (RES, PT) and default ODUk overhead. + +##### Symbol + +The ODUkP/MT\_A\_So function symbol is shown in Figure 11-17. + +![Figure 11-17 – ODUkP/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'ODUkP/MT_A_So'. Inputs from the top include 'SCC_CI' and multiple 'MT_CI' signals (indicated by arrows and an ellipsis). An output labeled 'ODUkP/MT_A_So_MI' points to the right side of the block. An output labeled 'ODUkP_AI' points downwards from the bottom of the block. A small text 'G.8121-Y.1381(13)_F11-17' is located to the right of the block.](0681cad811f269a7c9592f8e3d824b06_img.jpg) + +Figure 11-17 – ODUkP/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'ODUkP/MT\_A\_So'. Inputs from the top include 'SCC\_CI' and multiple 'MT\_CI' signals (indicated by arrows and an ellipsis). An output labeled 'ODUkP/MT\_A\_So\_MI' points to the right side of the block. An output labeled 'ODUkP\_AI' points downwards from the bottom of the block. A small text 'G.8121-Y.1381(13)\_F11-17' is located to the right of the block. + +Figure 11-17 – ODUkP/MT\_A\_So symbol + +##### Interfaces + +The ODUkP/MT\_A\_So interfaces are described in Table 11-9. + +Table 11-9 – ODUkP/MT\_A\_So interfaces + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
ODUkP/MT_A_So_MP:
ODUkP/MT_A_So_MI_SCCType
ODUkP/MT_A_So_MI_Label[1...M]
ODUkP/MT_A_So_MI_LSPTYPE[1...M]
ODUkP/MT_A_So_MI_CoS[1...M] | ODUkP_AP:
ODUkP_AI_Data
ODUkP_AI_Clock
ODUkP_AI_FrameStart
ODUkP_AI_MultiFrameStart | + +**Table 11-9 – ODUkP/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|----------------------------------------|-----------| +| ODUkP/MT_A_So_PHB2TCMapping[1..M] | | +| ODUkP/MT_A_So_MI_QoSEncodingMode[1..M] | | +| ODUkP/MT_A_So_MI_Mode[1..M] | | +| ODUkP/MT_A_So_MI_GAL_Enable[1..M] | | + +##### **Processes** + +A process diagram of this function is shown in Figure 11-18. + +![Figure 11-18 – ODUkP/MT_A_So process diagram. This flowchart illustrates the data processing pipeline for ODUkP/MT_A_So. It starts with multiple input streams (MI_Label, MI_LSPTypes, MI_CoS, MI_PHB2TCMapping, MI_QoSEncodingMode, MI_Mode) entering 'TC/Label processes'. These are followed by 'MT_CI_D' inputs. The output of 'TC/Label processes' is 'Mixed MT_CI_D', which goes to a 'Queueing' block. From 'Queueing', the data flows to 'MPLS-TP specific GFP-F processes', which also receives 'MI_SCCType' and 'SCC_CI' inputs. The output of this block is 'GFP_FS' and 'GFP_Frame', which then enter 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' points to this block. The output of 'Common GFP-F processes' is again 'GFP_FS' and 'GFP_Frame', which enter 'ODUk specific GFP-F processes'. The output of this block is 'ODUkP_AI_D', 'ODUkP_AI_CK', and 'ODUkP_AI_FS', which enter 'ODUk specific processes'. The final output of the entire process is 'ODUkP_AI_D/CK/FS/MFS'. A reference code 'G.8121-Y.1381(18)_F11-18' is at the bottom right.](bc90605aeb4173d4b4aa6eb475037a0c_img.jpg) + +Figure 11-18 – ODUkP/MT\_A\_So process diagram. This flowchart illustrates the data processing pipeline for ODUkP/MT\_A\_So. It starts with multiple input streams (MI\_Label, MI\_LSPTypes, MI\_CoS, MI\_PHB2TCMapping, MI\_QoSEncodingMode, MI\_Mode) entering 'TC/Label processes'. These are followed by 'MT\_CI\_D' inputs. The output of 'TC/Label processes' is 'Mixed MT\_CI\_D', which goes to a 'Queueing' block. From 'Queueing', the data flows to 'MPLS-TP specific GFP-F processes', which also receives 'MI\_SCCType' and 'SCC\_CI' inputs. The output of this block is 'GFP\_FS' and 'GFP\_Frame', which then enter 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' points to this block. The output of 'Common GFP-F processes' is again 'GFP\_FS' and 'GFP\_Frame', which enter 'ODUk specific GFP-F processes'. The output of this block is 'ODUkP\_AI\_D', 'ODUkP\_AI\_CK', and 'ODUkP\_AI\_FS', which enter 'ODUk specific processes'. The final output of the entire process is 'ODUkP\_AI\_D/CK/FS/MFS'. A reference code 'G.8121-Y.1381(18)\_F11-18' is at the bottom right. + +**Figure 11-18 – ODUkP/MT\_A\_So process diagram** + +- *TC/Label processes:* + +See clause 8.2.1. + +- *Queueing process:* + +See clause 8.3. + +- *MPLS-TP-specific GFP-F source process:* + +See clause 8.4.1. + +- *Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *ODUk 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.3 of [ITU-T G.709]. + +– *ODUk specific source process:* + +See Figure 11-19. + +![Figure 11-19 – ODUkP specific source processes. The diagram shows the internal logic for generating ODUkP signals. A 'Free run clock generator (ODCa)' provides a 'CK' signal. This clock is divided by 122368 to produce the 'FS' (frame start) signal, and by 256 to produce the 'MFS' (multiframe start) signal. The 'CK' signal is also output as 'AI_CK'. The 'FS' and 'MFS' signals are output as 'AI_FS' and 'AI_MFS' respectively. On the left, there are three input signals: 'PT' (payload type), 'RES' (residual), and a box stating 'ODUk OH is set to all-0's, except PM STAT = 001'. These are combined into the 'AI_D' (data) signal. The entire process is labeled 'ODUkP_AP' at the bottom.](37104233d1b6d7728427e833816594dc_img.jpg) + +Figure 11-19 – ODUkP specific source processes. The diagram shows the internal logic for generating ODUkP signals. A 'Free run clock generator (ODCa)' provides a 'CK' signal. This clock is divided by 122368 to produce the 'FS' (frame start) signal, and by 256 to produce the 'MFS' (multiframe start) signal. The 'CK' signal is also output as 'AI\_CK'. The 'FS' and 'MFS' signals are output as 'AI\_FS' and 'AI\_MFS' respectively. On the left, there are three input signals: 'PT' (payload type), 'RES' (residual), and a box stating 'ODUk OH is set to all-0's, except PM STAT = 001'. These are combined into the 'AI\_D' (data) signal. The entire process is labeled 'ODUkP\_AP' at the bottom. + +**Figure 11-19 – ODUkP specific source 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 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 payload structure indication (PSI) overhead as defined in clause 15.9.2.1.1 of [ITU-T G.709]. + +**RES:** The function shall insert all-0's into the RES 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). + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.2.1.2 ODUk to MPLS-TP adaptation sink function (ODUkP/MT\_A\_Sk) + +The ODUkP/MT\_A\_Sk extracts MT\_CI information from the ODUkP payload area. It extracts the OPUk overhead (PT and RES) and monitors the reception of the correct payload type. + +##### Symbol + +The ODUkP/MT\_A\_Sk function symbol is shown in Figure 11-20. + +![Figure 11-20 – ODUkP/MT_A_Sk symbol. The diagram shows a trapezoidal block labeled 'ODUkP/MT_A_Sk'. An arrow labeled 'ODUkP_AI' points into the block from the bottom. An arrow labeled 'ODUkP/MT_A_Sk_MI' points out of the block to the right. Multiple arrows labeled 'SCC_CI' and 'MT_CI' (with an ellipsis between them) point out of the block from the top. A small text 'G.8121-Y.1381(13)_F11-20' is located at the bottom right of the diagram.](f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg) + +Figure 11-20 – ODUkP/MT\_A\_Sk symbol. The diagram shows a trapezoidal block labeled 'ODUkP/MT\_A\_Sk'. An arrow labeled 'ODUkP\_AI' points into the block from the bottom. An arrow labeled 'ODUkP/MT\_A\_Sk\_MI' points out of the block to the right. Multiple arrows labeled 'SCC\_CI' and 'MT\_CI' (with an ellipsis between them) point out of the block from the top. A small text 'G.8121-Y.1381(13)\_F11-20' is located at the bottom right of the diagram. + +Figure 11-20 – ODUkP/MT\_A\_Sk symbol + +##### Interfaces + +The ODUkP/MT\_A\_Sk interfaces are described in Table 11-10. + +Table 11-10 – ODUkP/MT\_A\_Sk interfaces + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP_AP:
ODUkP_AI_Data
ODUkP_AI_Clock
ODUkP_AI_FrameStart
ODUkP_AI_MultiFrameStart
ODUkP_AI_TSF
ODUkP/MT_A_Sk_MP:
ODUkP/MT_A_Sk_MI_SCCType
ODUkP/MT_A_Sk_MI_Label[1...M]
ODUkP/MT_A_Sk_MI_LSPTYPE[1...M]
ODUkP/MT_A_Sk_MI_CoS[1...M]
ODUkP/MT_A_Sk_MI_TC2PHBMapping[1...M]
ODUkP/MT_A_Sk_MI_QoSDecodingMode[1...M]
ODUkP/MT_A_Sk_MI_Mode[1...M]
ODUkP/MT_A_Sk_MI_LCK_Period[1...M]
ODUkP/MT_A_Sk_MI_LCK_CoS[1...M]
ODUkP/MT_A_Sk_MI_Admin_State
ODUkP/MT_A_Sk_MI_AIS_Period[1...M]
ODUkP/MT_A_Sk_MI_AIS_CoS[1...M]
ODUkP/MT_A_Sk_MI_GAL_Enable[1...M]
ODUkP/MT_A_Sk_MI_LCK_Tool[1...M]
ODUkP/MT_A_Sk_MI_AIS_Tool[1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_LStack
SCC_CP:
SCC_CI_Data
SCC_CI_SSF
ODUkP/MT_A_Sk_MP:
ODUkP/MT_A_Sk_MI_AcPT
ODUkP/MT_A_Sk_MI_AcEXI
ODUkP/MT_A_Sk_MI_LastInvalidUPI
ODUkP/MT_A_Sk_MI_cPLM
ODUkP/MT_A_Sk_MI_cLFD
ODUkP/MT_A_Sk_MI_cEXM
ODUkP/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-21. + +![Figure 11-21 – ODUkP/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of an ODUkP/MT_A_Sk function. At the top, multiple MT_CI_SSF inputs (1 to M) enter a 'Selector' block. Each selector has 'Normal' and 'LCK' paths. Below the selectors are 'AIS insert' and 'LCK generate' blocks. These are followed by 'TC/Label processes', 'Label stack copy', and 'MPLS-TP specific GFP-F processes'. Below that are 'Common GFP-F processes', 'ODUkP specific GFP-F processes', and finally 'ODUkP specific processes' at the bottom. Various management information (MI) inputs and outputs are shown, such as MI_Label, MI_LSPType, MI_CoS, MI_PHB2TCMapping, MI_QoSEncodingModel, MI_Mode, MI_LastInvalidUPI, MI_SCCType, MI_AcEXI, MI_AcSL, MI_CUPM, MI_cEXM, MI_cLFD, MI_cPLM, MI_Admin_State, MI_LCK_Period/CoS/OAM_Tool, MI_GAL_Enable, MI_AIS_Period/CoS/OAM_Tool, MI_GAL_Enable, MI_CI_LStack, SCC_CI_D, and SCC_CI_SSF. Data flows are indicated by arrows between the blocks and external entities.](3c0be9369e1f99f7f820fda3f9d676e6_img.jpg) + +Figure 11-21 – ODUkP/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of an ODUkP/MT\_A\_Sk function. At the top, multiple MT\_CI\_SSF inputs (1 to M) enter a 'Selector' block. Each selector has 'Normal' and 'LCK' paths. Below the selectors are 'AIS insert' and 'LCK generate' blocks. These are followed by 'TC/Label processes', 'Label stack copy', and 'MPLS-TP specific GFP-F processes'. Below that are 'Common GFP-F processes', 'ODUkP specific GFP-F processes', and finally 'ODUkP specific processes' at the bottom. Various management information (MI) inputs and outputs are shown, such as MI\_Label, MI\_LSPType, MI\_CoS, MI\_PHB2TCMapping, MI\_QoSEncodingModel, MI\_Mode, MI\_LastInvalidUPI, MI\_SCCType, MI\_AcEXI, MI\_AcSL, MI\_CUPM, MI\_cEXM, MI\_cLFD, MI\_cPLM, MI\_Admin\_State, MI\_LCK\_Period/CoS/OAM\_Tool, MI\_GAL\_Enable, MI\_AIS\_Period/CoS/OAM\_Tool, MI\_GAL\_Enable, MI\_CI\_LStack, SCC\_CI\_D, and SCC\_CI\_SSF. Data flows are indicated by arrows between the blocks and external entities. + +**Figure 11-21 – ODUkP/MT\_A\_Sk process diagram** + +– *Selector generation process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +– *AIS insert process:* + +See clause 8.6.2. There is a single AIS insert process for each MT. + +– *LCK generation process:* + +See clause 8.6.3. There is a single LCK generation process for each MT. + +– *TC/Label sink processes:* + +See clause 8.2.2. + +– *Label stack copy process:* + +See 8.2.3. + +– *MPLS-TP-specific GFP-F sink process:* + +See clause 8.4.2. + +– *Common GFP sink process:* + +See clause 8.5.3.2 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +– *ODUk 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.3 of [ITU-T G.709]. + +– *ODUk-specific sink process:* + +The ODUkP specific sink processes are shown in Figure 11-22. + +![Figure 11-22 – ODUkP specific sink processes. The diagram shows the internal processing of an ODUkP sink. On the left, five vertical lines represent input signals: AI_D, AI_CK, AI_FS, AI_MFS, and AI_TSF. These are grouped under the label 'ODUkP_AP'. The AI_D, AI_CK, and AI_FS lines extend upwards as output arrows. The AI_MFS line enters a block labeled 'Extract PT'. The output of 'Extract PT' enters a block labeled 'PT process'. The 'PT process' block has an output labeled 'MI_AcPT' and a feedback input labeled 'dPLM'. Above the 'PT process' block is a 'Defect correlations' block. This block receives inputs 'dPLM' and 'AI_TSF' and has an output labeled 'MI_cPLM'. The 'PT process' block also has an output arrow pointing to the 'Defect correlations' block. The diagram is labeled 'G.8121-Y.1381(18)_F11-22' at the bottom right.](5efe6377e22b9ab76a19a70da29976b9_img.jpg) + +Figure 11-22 – ODUkP specific sink processes. The diagram shows the internal processing of an ODUkP sink. On the left, five vertical lines represent input signals: AI\_D, AI\_CK, AI\_FS, AI\_MFS, and AI\_TSF. These are grouped under the label 'ODUkP\_AP'. The AI\_D, AI\_CK, and AI\_FS lines extend upwards as output arrows. The AI\_MFS line enters a block labeled 'Extract PT'. The output of 'Extract PT' enters a block labeled 'PT process'. The 'PT process' block has an output labeled 'MI\_AcPT' and a feedback input labeled 'dPLM'. Above the 'PT process' block is a 'Defect correlations' block. This block receives inputs 'dPLM' and 'AI\_TSF' and has an output labeled 'MI\_cPLM'. The 'PT process' block also has an output arrow pointing to the 'Defect correlations' block. The diagram is labeled 'G.8121-Y.1381(18)\_F11-22' at the bottom right. + +**Figure 11-22 – ODUkP specific sink processes** + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.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 payload mismatch (PLM) defect detection. + +**RES:** The value in the RES bytes shall be ignored. + +##### **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]. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### **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 ← dPLM and (not AI\_TSF) + +cLFD $\leftarrow$ dLFD and (not dPLM) and (not AI\_TSF) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### Performance monitoring: + +For further study. + +### 11.2.2 HAO capable ODUk to MPLS-TP adaptation functions (ODUkP-h/MT\_A; k=ODUflex) + +#### 11.2.2.1 HAO capable ODUk to MPLS-TP adaptation source function (ODUkP-h/MT\_A\_So) + +The ODUkP-h/MT\_A\_So function creates the ODUk signal from a free running clock. It maps the MT\_CI information into the payload of the OPUk (k=flex), adds OPUk Overhead (RES, PT, RCOH) and default ODUk overhead. + +##### Symbol + +The ODUkP-h/MT\_A\_So function symbol is shown in Figure 11-23. + +![Figure 11-23 – ODUkP-h/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'ODUkP-h/MT_A_So'. Inputs from the top are SCC_CI and MT_CI (with an ellipsis indicating multiple inputs). An input from the right is ODUkP-h/MT_A_So_MI. The output at the bottom is ODUkP_AI. A reference code G.8121-Y.1381(18)_F11-23 is shown to the right of the block.](c3d58ba0812530ed8c8a9c9f68c209b1_img.jpg) + +Figure 11-23 – ODUkP-h/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'ODUkP-h/MT\_A\_So'. Inputs from the top are SCC\_CI and MT\_CI (with an ellipsis indicating multiple inputs). An input from the right is ODUkP-h/MT\_A\_So\_MI. The output at the bottom is ODUkP\_AI. A reference code G.8121-Y.1381(18)\_F11-23 is shown to the right of the block. + +Figure 11-23 – ODUkP-h/MT\_A\_So symbol + +##### Interfaces + +The ODUkP-h/MT\_A\_So interfaces are described in Table 11-11. + +Table 11-11 – ODUkP-h/MT\_A\_So interfaces + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
ODUkP_RP:
ODUkP_RI_RP
ODUkP_RI_TSCC
ODUkP_RI_NCS
SCC_CP:
SCC_CI_Data
ODUkP-h/MT_A_So_MP:
ODUkP-h/MT_A_So_MI_SCCType
ODUkP-h/MT_A_So_MI_Label[1...M]
ODUkP-h/MT_A_So_MI_LSPTYPE[1...M]
ODUkP-h/MT_A_So_MI_CoS[1...M]
ODUkP-h/MT_A_So_PHB2TCMapping[1...M] | ODUkP_AP:
ODUkP_AI_Data
ODUkP_AI_Clock
ODUkP_AI_FrameStart
ODUkP_AI_MultiFrameStart
ODUkP_(A/M)I_RP
ODUkP_(A/M)I_TSCC
ODUkP-h/MT_A_So_MP:
ODUkP-h/MT_A_So_MI_ADJSTATE | + +**Table 11-11 – ODUkP-h/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| ODUkP-h/MT_A_So_MI_QoSEncodingMode[1..M]
ODUkP-h/MT_A_So_MI_Mode[1..M]

ODUkP-h/MT_A_So_MI_GAL_Enable[1..M]

ODUkP-h/MT_A_So_MI_Increase
ODUkP-h/MT_A_So_MI_Decrease
ODUkP-h/MT_A_So_MI_TSNUM
ODUkP-h/MT_A_So_MI_ODUflexRate | | +| NOTE – (A/M)I_xxx indicates that the xxx signal may either be an AI_xxx or a MI_xxx signal. | | + +##### Processes + +A process diagram of this function is shown as Figure 11-18 in clause 11.2.1.1. An ODU specific process for HAO capable adaptation function is described as below. Other processes are described in clause 11.2.1.1. + +– *ODUk specific source process:* + +Figure 11-24 illustrates ODUkP (k=flex) specific source processes. + +![Figure 11-24 – ODUkP (k=flex) specific source processes. This block diagram shows the internal logic for generating ODUkP signals. On the left, three blocks labeled RCOH, PT, and RES are connected to a vertical bus labeled AI_D. Below them, a block 'ODUk is set to all-0's, except PM STAT = 001' is also connected to the AI_D bus. The central part of the diagram features an 'Adjustable free run clock generator (ODCa)' which receives a CK signal and an 'ODUflex clock control' signal. It outputs a CK signal to a 'BWR generator' block and also to a divider block labeled '1 / 122368'. The divider outputs an AI_FS signal. Below that is another divider block labeled '1 / 256' which outputs an AI_MFS signal. The 'BWR generator' block receives several inputs: BWR_IND, NCS, MI_ODUflexRate, MI_Increase, MI_Decrease, MI_TSNUM, MI_ADJstate, RI_RP, RI_TSCC, and RI_NSC. It outputs signals to the AI_D bus and to a group of outputs labeled xl_RP, xl_TSCC, and X=A/M. The entire diagram is labeled 'ODUkP_AP' at the bottom left and 'G.8121-Y.1381(18)_F11-24' at the bottom right.](15d5c901284409186049549eec95c4a4_img.jpg) + +Figure 11-24 – ODUkP (k=flex) specific source processes. This block diagram shows the internal logic for generating ODUkP signals. On the left, three blocks labeled RCOH, PT, and RES are connected to a vertical bus labeled AI\_D. Below them, a block 'ODUk is set to all-0's, except PM STAT = 001' is also connected to the AI\_D bus. The central part of the diagram features an 'Adjustable free run clock generator (ODCa)' which receives a CK signal and an 'ODUflex clock control' signal. It outputs a CK signal to a 'BWR generator' block and also to a divider block labeled '1 / 122368'. The divider outputs an AI\_FS signal. Below that is another divider block labeled '1 / 256' which outputs an AI\_MFS signal. The 'BWR generator' block receives several inputs: BWR\_IND, NCS, MI\_ODUflexRate, MI\_Increase, MI\_Decrease, MI\_TSNUM, MI\_ADJstate, RI\_RP, RI\_TSCC, and RI\_NSC. It outputs signals to the AI\_D bus and to a group of outputs labeled xl\_RP, xl\_TSCC, and X=A/M. The entire diagram is labeled 'ODUkP\_AP' at the bottom left and 'G.8121-Y.1381(18)\_F11-24' at the bottom right. + +**Figure 11-24 – ODUkP (k=flex) specific source processes** + +**Clock and (multi)frame start signal generation:** The function shall generate a local ODUk clock with a clock rate within the minimum to maximum clock rate of the ODUflex 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]. The PT value of a HAO capable adaptation function is the same as a non-HAO capable one. + +**RES:** The function shall insert all-0's into the RES 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). + +**RCOH generator:** This process inserts network connectivity status (NCS) generated by HAO process into the NCS field of the resize control overhead (RCOH) in OPUflex. + +**BWR\_Generator:** This process is used for bandwidth resize (BWR) protocol adjustment processing and generation of BWR protocol overhead. It contains the following processes as shown in Figure 11-25. + +*Adjustment activation:* When MI\_Increase or MI\_Decrease is true, BWR protocol is activated and RI processing is started. + +*Rate adjustment control:* Generates ODUflex clock control signal. Original ODUflex clock rate will gradually change to new ODUflex clock rate such that no GMP buffer overflow or underflow will occur in the ODUflex network connection. Refer to [ITU-T G.7044]. + +![Figure 11-25 – BWR_Generator process block diagram. The diagram shows a large grey box representing the BWR_Generator process. Inside, there are three main functional blocks: 'Adjustment activation', 'RI processing', and 'Rate adjustment control'. 'Adjustment activation' receives 'CK', 'FS', and 'MFS' signals from the top and 'MI_Increase' and 'MI_Decrease' signals from the right. It outputs a signal to 'RI processing'. 'RI processing' receives 'RI_RP', 'RI_TSCC', and 'RI_NCS' signals from the left and the signal from 'Adjustment activation'. It outputs 'MI_ADJstate' to the right and signals 'NCS' and 'BWR_IND' to the left. 'Rate adjustment control' receives 'MI_TSNUM' from the right and a signal from 'RI processing'. It outputs 'ODUflex clock control information' to the bottom. The 'ODUflex clock control information' is also input to the 'BWR_generator' block, which is located at the bottom right of the main box. The 'BWR_generator' block outputs 'xl_RP' and 'xl_TSCC' signals to the bottom. A small text 'G.8121-Y.1381(18)_F11-25' is at the bottom right of the diagram.](46b47a38697e3aedb09cccd7eba47192_img.jpg) + +Figure 11-25 – BWR\_Generator process block diagram. The diagram shows a large grey box representing the BWR\_Generator process. Inside, there are three main functional blocks: 'Adjustment activation', 'RI processing', and 'Rate adjustment control'. 'Adjustment activation' receives 'CK', 'FS', and 'MFS' signals from the top and 'MI\_Increase' and 'MI\_Decrease' signals from the right. It outputs a signal to 'RI processing'. 'RI processing' receives 'RI\_RP', 'RI\_TSCC', and 'RI\_NCS' signals from the left and the signal from 'Adjustment activation'. It outputs 'MI\_ADJstate' to the right and signals 'NCS' and 'BWR\_IND' to the left. 'Rate adjustment control' receives 'MI\_TSNUM' from the right and a signal from 'RI processing'. It outputs 'ODUflex clock control information' to the bottom. The 'ODUflex clock control information' is also input to the 'BWR\_generator' block, which is located at the bottom right of the main box. The 'BWR\_generator' block outputs 'xl\_RP' and 'xl\_TSCC' signals to the bottom. A small text 'G.8121-Y.1381(18)\_F11-25' is at the bottom right of the diagram. + +**Figure 11-25 – BWR\_Generator process** + +*RI processing:* This process performs BWR protocol according to 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 ODUflex signal's bit rate adjustment starts, and is set to "0" y $\mu$ s before ODUflex signal's bit rate adjustment completes. 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 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 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 network management system (NMS) when receiving RI\_RP=0. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.2.2.2 HAO capable ODUk to MPLS-TP adaptation sink function (ODUkP-h/MT\_A\_Sk) + +The ODUkP-h/MT\_A\_Sk extracts MT\_CI information from the ODUkP payload area. It extracts the OPUk overhead (PT, RCOH and RES) and monitors the reception of the correct payload type. + +##### Symbol + +The ODUkP-h/MT\_A\_Sk function symbol is shown in Figure 11-26. + +![Figure 11-26 – ODUkP-h/MT_A_Sk symbol. The diagram shows a trapezoidal block labeled 'ODUkP-h/MT_A_Sk'. An input arrow labeled 'ODUkP_AI' points into the bottom of the block. Multiple output arrows labeled 'SCC_CI', 'MT_CI', and '...' point out of the top of the block. A bidirectional arrow labeled 'ODUkP-h/MT_A_Sk_MI' is connected to the right side of the block. A small text label 'G.8121-Y.1381(18)_F11-26' is located to the right of the block.](7ee70c4daffe1f4f1d07ac574964a3a8_img.jpg) + +Figure 11-26 – ODUkP-h/MT\_A\_Sk symbol. The diagram shows a trapezoidal block labeled 'ODUkP-h/MT\_A\_Sk'. An input arrow labeled 'ODUkP\_AI' points into the bottom of the block. Multiple output arrows labeled 'SCC\_CI', 'MT\_CI', and '...' point out of the top of the block. A bidirectional arrow labeled 'ODUkP-h/MT\_A\_Sk\_MI' is connected to the right side of the block. A small text label 'G.8121-Y.1381(18)\_F11-26' is located to the right of the block. + +**Figure 11-26 – ODUkP-h/MT\_A\_Sk symbol** + +##### Interfaces + +The ODUkP-h/MT\_A\_Sk interfaces are described in Table 11-12. + +**Table 11-12 – ODUkP-h/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 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
ODUkP-h/MT_A_Sk_MP: | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_LStack
SCC_CP:
SCC_CI_Data
SCC_CI_SSF
ODUkP_RP: | + +**Table 11-12 – ODUkP-h/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ODUkP-h/MT_A_Sk_MI_SCCType
ODUkP-h/MT_A_Sk_MI_Label[1...M]
ODUkP-h/MT_A_Sk_MI_LSPTYPE[1...M]
ODUkP-h/MT_A_Sk_MI_CoS[1...M]
ODUkP-h/MT_A_Sk_MI_TC2PHBMapping[1...M]
ODUkP-h/MT_A_Sk_MI_QoSDecodingMode[1...M]
ODUkP/MT_A_Sk_MI_Mode[1...M]
ODUkP-h/MT_A_Sk_MI_LCK_Period[1...M]
ODUkP-h/MT_A_Sk_MI_LCK_CoS[1...M]
ODUkP-h/MT_A_Sk_MI_LCK_Tool[1...M]
ODUkP-h/MT_A_Sk_MI_AIS_Tool[1...M]
ODUkP-h/MT_A_Sk_MI_Admin_State
ODUkP-h/MT_A_Sk_MI_AIS_Period[1...M]
ODUkP-h/MT_A_Sk_MI_AIS_CoS[1...M]
ODUkP-h/MT_A_Sk_MI_LCK_Tool[1...M]
ODUkP-h/MT_A_Sk_MI_AIS_Tool[1...M]
ODUkP-h/MT_A_Sk_MI_GAL_Enable[1...M]
ODUkP-h/MT_A_Sk_MI_Increase
ODUkP-h/MT_A_Sk_MI_Decrease | ODUkP_RI_RP
ODUkP_RI_TSCC
ODUkP_RI_NCS

ODUkP-h/MT_A_Sk_MP:
ODUkP-h/MT_A_Sk_MI_AcPT
ODUkP-h/MT_A_Sk_MI_AcEXI
ODUkP-h/MT_A_Sk_MI_LastInvalidUPI
ODUkP-h/MT_A_Sk_MI_cPLM
ODUkP-h/MT_A_Sk_MI_cLFD
ODUkP-h/MT_A_Sk_MI_cEXM
ODUkP-h/MT_A_Sk_MI_cUPM | + +##### **Processes** + +A process diagram of this function is shown as Figure 11-21 in clause 11.2.1.2. An ODU specific process for HAO capable adaptation function is described as below. Other processes are described in clause 11.2.1.2. + +– *ODUk-specific sink process:* + +The ODUkP (k=flex) specific sink process is illustrated in Figure 11-27. + +![Block diagram of ODUkP (k=flex) specific sink processes. The diagram shows signal flow from left to right. On the far left, inputs MI_Increase, MI_Decrease, RI_RP, RI_TSCC, and RI_NSC enter a 'BWR receiver' block. The BWR receiver outputs NCS to an 'RCOH receiver' block. The RCOH receiver outputs D, CK, and FS signals. Below the RCOH receiver, there are three vertical lines labeled AI_D, AI_CK, and AI_FS. The BWR receiver also outputs xl_RP, xl_TSCC, and X=A/M signals. These signals enter an 'Extract PT' block. The Extract PT block outputs AI_MFS and AI_TSF signals. The Extract PT block also outputs dPLM and AI_TSF signals to a 'Defect correlations' block. The Defect correlations block outputs MI_cPLM. The Extract PT block also outputs dPLM and AI_TSF signals to a 'PT process' block. The PT process block outputs MI_AcPT. The PT process block also outputs AI_TSF. The diagram is labeled G.8121-Y.1381(18)_F11-27 at the bottom right.](7fb56e3e9f8a134112eee90463cc9962_img.jpg) + +Block diagram of ODUkP (k=flex) specific sink processes. The diagram shows signal flow from left to right. On the far left, inputs MI\_Increase, MI\_Decrease, RI\_RP, RI\_TSCC, and RI\_NSC enter a 'BWR receiver' block. The BWR receiver outputs NCS to an 'RCOH receiver' block. The RCOH receiver outputs D, CK, and FS signals. Below the RCOH receiver, there are three vertical lines labeled AI\_D, AI\_CK, and AI\_FS. The BWR receiver also outputs xl\_RP, xl\_TSCC, and X=A/M signals. These signals enter an 'Extract PT' block. The Extract PT block outputs AI\_MFS and AI\_TSF signals. The Extract PT block also outputs dPLM and AI\_TSF signals to a 'Defect correlations' block. The Defect correlations block outputs MI\_cPLM. The Extract PT block also outputs dPLM and AI\_TSF signals to a 'PT process' block. The PT process block outputs MI\_AcPT. The PT process block also outputs AI\_TSF. The diagram is labeled G.8121-Y.1381(18)\_F11-27 at the bottom right. + +**Figure 11-27 – ODUkP (k=flex) specific sink processes** + +**PT:** The function shall extract the PT byte from the PSI overhead as defined in clause 8.7.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. The PT value of a HAO capable adaptation function is the same as a non-HAO capable one. + +**RES:** The value in the RES bytes shall be ignored. + +**RCOH receiver:** This process extracts NCS from RCOH overhead area, and then forwards it to the 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 11-28. + +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 BWR\_RELAY\_Receiver process and NCS from Extract NCS process. Then the detected value of RP, TSCC and NCS are sent to BWR generator. + +![Figure 11-28 – BWR_Receiver process diagram](0850300da6b28250eb47881da35cabad_img.jpg) + +The diagram illustrates the BWR\_Receiver process. It is contained within a large grey rectangle labeled 'BWR\_receiver' at the bottom right. Inside this rectangle, there are two main processing blocks. The top block is labeled 'BWR OH detecting processing'. It receives several inputs from above: 'NCS', 'x1\_RP', 'CK', 'FS', and 'MFS'. It also receives two inputs from the right: 'MI\_Increase' and 'MI\_Decrease'. An arrow points from the bottom of this block to the second block. The second block is labeled 'Forwarding processing'. It outputs three signals to the left: 'RI\_RP', 'RI\_TSCC', and 'RI\_NCS'. Below the 'BWR\_receiver' label, the text 'G.8121-Y.1381(18)\_F11-28' is present. + +Figure 11-28 – BWR\_Receiver process diagram + +**Figure 11-28 – BWR\_Receiver process** + +##### 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]. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +##### Consequent actions: + +The function shall perform the following consequent actions: + +aSSF $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS $\leftarrow$ AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### 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) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### Performance monitoring: + +For further study. + +## 11.3 PDH to MPLS-TP adaptation function (P/MT\_A) + +### 11.3.1 Pq to MPLS-TP adaptation functions (Pq/MT\_A; q = 11s, 12s, 31s, 32e) + +#### 11.3.1.1 Pq to MPLS-TP adaptation source function (Pq/MT\_A\_So) + +This function maps MT\_CI information onto a Pq\_AI signal (q = 11s, 12s, 31s, 32e). + +Data at the Pq\_AP is a Pq (q = 11s, 12s, 31s, 32e), having a payload as described in [ITU-T G.7043] with a value of N=1. The VLI byte is reserved and not used for payload data. + +##### Symbol + +The Pq/MT\_A\_So function symbol is shown in Figure 11-29. + +![Figure 11-29 – Pq/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'Pq/MT_A_So'. Inputs from the top include SCC_CI, MT_CI, and an ellipsis. An output labeled Pq_AI points downwards. On the right side, two bidirectional arrows represent interfaces labeled Pq/MT_A_So_MI and Pq_TI. A small text label 'G.8121-Y.1381(18)_F11-29' is at the bottom right.](4e3bce0b4a3062f7f237acd0b04e5c66_img.jpg) + +Figure 11-29 – Pq/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'Pq/MT\_A\_So'. Inputs from the top include SCC\_CI, MT\_CI, and an ellipsis. An output labeled Pq\_AI points downwards. On the right side, two bidirectional arrows represent interfaces labeled Pq/MT\_A\_So\_MI and Pq\_TI. A small text label 'G.8121-Y.1381(18)\_F11-29' is at the bottom right. + +Figure 11-29 – Pq/MT\_A\_So symbol + +##### Interfaces + +The Pq/MT\_A\_So interfaces are described in Table 11-13. + +Table 11-13 – Pq/MT\_A\_So interfaces + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Pq_TP:
Pq_TI_Clock
Pq_TI_FrameStart
Pq/MT_A_So_MP:
Pq/MT_A_So_MI_SCCType
Pq/MT_A_So_MI_Label[1...M]
Pq/MT_A_So_MI_LSPTYPE[1...M]
Pq/MT_A_So_MI_CoS[1...M]
Pq/MT_A_So_PHB2TCMapping[1...M]
Pq/MT_A_So_MI_QoSEncodingMode[1...M]
Pq/MT_A_So_MI_Mode[1...M]
Pq/MT_A_So_MI_GAL_Enable[1...M] | Pq_AP:
Pq_AI_Data
Pq_AI_Clock
Pq_AI_FrameStart | + +##### Processes + +A process diagram of this function is shown in Figure 11-30. + +![Figure 11-30 – Pq/MT_A_So process diagram. This block diagram illustrates the data flow through various processing stages. Inputs on the left include MI_Label[1...M], MI_LSPTYPE[1...M], MI_CoS[1...M], MI_PHB2TCMapping[1...M], MI_QoSEncodingModel[1...M], MI_Mode[1...M], and MI_SCCType. Inputs at the top include MT_CI_D[1] through MT_CI_D[M] and SCC_CI. The flow starts with TC/Label processes, which output 'Muxed MT_CI_D' to a Queueing block. The Queueing block outputs to MPLS-TP specific GFP-F processes. This block also receives MI_SCCType and SCC_CI. It outputs GFP_FS and GFP_Frame to Common GFP-F processes. A dashed arrow labeled 'CMuxActive = false' points to the Common GFP-F processes block. The Common GFP-F processes output GFP_FS and GFP_Frame to Pq specific GFP-F processes. These processes receive Pq_TI_CK and Pq_TI_FS from the right and output Pq_AI_D, Pq_AI_CK, and Pq_AI_FS to Pq specific processes. Finally, the Pq specific processes output Pq_AI_D, Pq_AI_CK, and Pq_AI_FS. The diagram is labeled G.8121-Y.1381(18)_F11-30.](200e768e8ed91aadff59c651287d1009_img.jpg) + +Figure 11-30 – Pq/MT\_A\_So process diagram. This block diagram illustrates the data flow through various processing stages. Inputs on the left include MI\_Label[1...M], MI\_LSPTYPE[1...M], MI\_CoS[1...M], MI\_PHB2TCMapping[1...M], MI\_QoSEncodingModel[1...M], MI\_Mode[1...M], and MI\_SCCType. Inputs at the top include MT\_CI\_D[1] through MT\_CI\_D[M] and SCC\_CI. The flow starts with TC/Label processes, which output 'Muxed MT\_CI\_D' to a Queueing block. The Queueing block outputs to MPLS-TP specific GFP-F processes. This block also receives MI\_SCCType and SCC\_CI. It outputs GFP\_FS and GFP\_Frame to Common GFP-F processes. A dashed arrow labeled 'CMuxActive = false' points to the Common GFP-F processes block. The Common GFP-F processes output GFP\_FS and GFP\_Frame to Pq specific GFP-F processes. These processes receive Pq\_TI\_CK and Pq\_TI\_FS from the right and output Pq\_AI\_D, Pq\_AI\_CK, and Pq\_AI\_FS to Pq specific processes. Finally, the Pq specific processes output Pq\_AI\_D, Pq\_AI\_CK, and Pq\_AI\_FS. The diagram is labeled G.8121-Y.1381(18)\_F11-30. + +Figure 11-30 – Pq/MT\_A\_So process diagram + +##### *TC/Label processes:* + +See clause 8.2.1. + +###### *Queueing process:* + +See clause 8.3. + +##### *MPLS-TP-specific GFP-F source process:* + +See clause 8.4.1. + +###### *Common GFP source process:* + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +###### *Pq specific GFP source process:* + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are mapped into the Pq payload area according to [ITU-T G.8040]. + +###### *Pq specific source process:* + +NOTE – The VLI byte is fixed and equal to 0x00 at the Pq\_AP output of this function. + +*P31s specific:* + +**MA:** Signal label information is derived directly from the Adaptation function type. The value for "GFP mapping" in clause 2.1 of [ITU-T G.832] is placed in the "Payload type" field of the MA byte. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.3.1.2 Pq to MPLS-TP adaptation sink function (Pq/MT\_A\_Sk) + +This function extracts MT\_CI information from the Pq\_AI signal (q = 11s, 12s, 31s, 32e), delivering MT\_CI. + +Data at the Pq\_AP is a Pq (q = 11s, 12s, 31s, 32e), having a payload as described in [ITU-T G.7043] with a value of N=1. The VLI byte is reserved and not used for payload data. + +##### Symbol + +The Pq/MT\_A\_Sk function symbol is shown in Figure 11-31. + +![Figure 11-31 – Pq/MT_A_Sk symbol. The diagram shows a trapezoidal block labeled 'Pq/MT_A_Sk'. An arrow labeled 'Pq_AI' points into the block from the bottom. An arrow labeled 'Pq/MT_A_Sk_MI' points out of the block to the right. Multiple arrows labeled 'SCC_CI' and 'MT_CI' point out of the block from the top. A small text 'G.8121-Y.1381(18)_F11-31' is located at the bottom right of the diagram.](7f7718a1d18d1f9055d85871d02364b3_img.jpg) + +Figure 11-31 – Pq/MT\_A\_Sk symbol. The diagram shows a trapezoidal block labeled 'Pq/MT\_A\_Sk'. An arrow labeled 'Pq\_AI' points into the block from the bottom. An arrow labeled 'Pq/MT\_A\_Sk\_MI' points out of the block to the right. Multiple arrows labeled 'SCC\_CI' and 'MT\_CI' point out of the block from the top. A small text 'G.8121-Y.1381(18)\_F11-31' is located at the bottom right of the diagram. + +**Figure 11-31 – Pq/MT\_A\_Sk symbol** + +##### Interfaces + +The Pq/MT\_A\_Sk interfaces are described in Table 11-14. + +**Table 11-14 – Pq/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pq_AP:
Pq_AI_Data
Pq_AI_Clock
Pq_AI_FrameStart
Pq_AI_TSF
Pq/MT_A_Sk_MP:
Pq/MT_A_Sk_MI_SCCType
Pq/MT_A_Sk_MI_Label[1...M]
Pq/MT_A_Sk_MI_LSPTType[1...M]
Pq/MT_A_Sk_MI_CoS[1...M]
Pq/MT_A_Sk_MI_TC2PHBMapping[1...M]
Pq/MT_A_Sk_MI_QoSDecodingMode[1...M]
Pq/MT_A_Sk_MI_Mode[1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_LStack
SCC_CP:
SCC_CI_Data
SCC_CI_SSF
Pq/MT_A_Sk_MP:
Pq/MT_A_Sk_MI_AcSL
Pq/MT_A_Sk_MI_AcEXI
Pq/MT_A_Sk_MI_LastInvalidUPI
Pq/MT_A_Sk_MI_cPLM
Pq/MT_A_Sk_MI_cLFD
Pq/MT_A_Sk_MI_cEXM | + +**Table 11-14 – Pq/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| Pq/MT_A_Sk_MI_LCK_Period[1..M]
Pq/MT_A_Sk_MI_LCK_CoS[1..M]
Pq/MT_A_Sk_MI_Admin_State
Pq/MT_A_Sk_MI_AIS_Period[1..M]
Pq/MT_A_Sk_MI_AIS_CoS[1..M]
Pq/MT_A_Sk_MI_GAL_Enable [1..M]
Pq/MT_A_Sk_MI_LCK_Tool[1..M]
Pq/MT_A_Sk_MI_AIS_Tool[1..M] | Pq/MT_A_Sk_MI_cUPM | + +##### Processes + +A process diagram of this function is shown in Figure 11-32. + +![Figure 11-32 – Pq/MT_A_Sk process diagram. This is a complex block diagram showing the internal processes of the Pq/MT_A_Sk function. At the bottom, 'Pq specific processes' receive 'Pq_AI_D/CK/SF/TSF' and output 'MI_AcSL'. Above them, 'Pq specific GFP-F processes' receive 'Pq_AI_D/CK/SF/TSF' and output 'MI_cLFD'. These are followed by 'Common GFP-F processes' which receive 'GFP_Frame/SF/FS' and output 'MI_cEXM' (conditional on CMuxActive = false) and 'MI_AcEXI'. The next layer is 'MPLS-TP specific GFP-F processes' which receive 'Client_SF' and output 'MI_cUPM'. Above this is a 'Label stack copy' block receiving 'Mixed MT_CI_D' and outputting 'Mixed D' and 'Mixed LStack'. The 'TC/Label processes' block receives 'Mixed D' and 'Mixed LStack' and outputs 'aAIS'. Above that are two parallel paths: one with 'AIS insert' and 'LCK generate' blocks, and another with 'Selector' blocks (Normal/LCK). These receive inputs from 'Consequent action' and configuration parameters like 'MI_Admin_State', 'MI_LCK_Period/CoS/OAM_Tool', 'MI_GAL_Enable', and 'MI_AIS_Period/CoS/OAM_Tool'. The final output layer consists of 'MT_CI_SSF[1]...MT_CI_SSF[M]' and 'MT_CI_D/iPHB/oPHB[1]...MT_CI_D/iPHB/oPHB[M]'. External inputs include 'MI_Label', 'MI_LSPTYPE', 'MI_CoS', 'MI_PHB2TCMapping', 'MI_QoSEncodingModel', 'MI_Mode', 'MI_LastInvalidUPI', 'MI_SCCType', and 'MI_AcSL'. External outputs include 'MI_cUPM', 'MI_cEXM', 'MI_cLFD', 'MI_cPLM', 'MI_CI_LStack', 'SCC_CI_D', and 'SCC_CI_SSF'.](48090d8f1db2e826aaa740035aa12ecb_img.jpg) + +Figure 11-32 – Pq/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal processes of the Pq/MT\_A\_Sk function. At the bottom, 'Pq specific processes' receive 'Pq\_AI\_D/CK/SF/TSF' and output 'MI\_AcSL'. Above them, 'Pq specific GFP-F processes' receive 'Pq\_AI\_D/CK/SF/TSF' and output 'MI\_cLFD'. These are followed by 'Common GFP-F processes' which receive 'GFP\_Frame/SF/FS' and output 'MI\_cEXM' (conditional on CMuxActive = false) and 'MI\_AcEXI'. The next layer is 'MPLS-TP specific GFP-F processes' which receive 'Client\_SF' and output 'MI\_cUPM'. Above this is a 'Label stack copy' block receiving 'Mixed MT\_CI\_D' and outputting 'Mixed D' and 'Mixed LStack'. The 'TC/Label processes' block receives 'Mixed D' and 'Mixed LStack' and outputs 'aAIS'. Above that are two parallel paths: one with 'AIS insert' and 'LCK generate' blocks, and another with 'Selector' blocks (Normal/LCK). These receive inputs from 'Consequent action' and configuration parameters like 'MI\_Admin\_State', 'MI\_LCK\_Period/CoS/OAM\_Tool', 'MI\_GAL\_Enable', and 'MI\_AIS\_Period/CoS/OAM\_Tool'. The final output layer consists of 'MT\_CI\_SSF[1]...MT\_CI\_SSF[M]' and 'MT\_CI\_D/iPHB/oPHB[1]...MT\_CI\_D/iPHB/oPHB[M]'. External inputs include 'MI\_Label', 'MI\_LSPTYPE', 'MI\_CoS', 'MI\_PHB2TCMapping', 'MI\_QoSEncodingModel', 'MI\_Mode', 'MI\_LastInvalidUPI', 'MI\_SCCType', and 'MI\_AcSL'. External outputs include 'MI\_cUPM', 'MI\_cEXM', 'MI\_cLFD', 'MI\_cPLM', 'MI\_CI\_LStack', 'SCC\_CI\_D', and 'SCC\_CI\_SSF'. + +**Figure 11-32 – Pq/MT\_A\_Sk process diagram** + +– *Selector generation process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +– *AIS insert process:* + +See clause 8.6.2. There is a single AIS insert process for each MT. + +– *LCK generation process:* + +See clause 8.6.3. There is a single LCK generation process for each MT. + +***TC/Label sink processes:*** + +See clause 8.2.2. + +– *Label stack copy process:* + +See clause 8.2.3. + +***MPLS-TP specific GFP-F sink process:*** + +See clause 8.4.2. + +***Common GFP sink process:*** + +See clause 8.5.3.1 of [ITU-T G.806]. GFP channel multiplexing is not supported (CMuxActive=false). + +***Pq specific GFP sink process:*** + +See clause 8.5.2.1 of [ITU-T G.806]. The GFP frames are demapped from the Pq payload area according to [ITU-T G.8040]. + +***Pq specific sink process:*** + +NOTE – The VLI byte at the Pq\_AP input of this function is ignored. + +***P31s specific:*** + +**MA:** The signal label is recovered from the "Payload type" field in the MA byte as per clause 6.2.4.2 of [ITU-T G.806]. The signal label for "GFP mapping" in clause 2.1 of [ITU-T G.832] shall be expected. The accepted value of the signal label is also available at the P31s/ETH\_A\_Sk\_MP. + +**Defects:** + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806] + +dUPM – See clause 8.4.2 + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +NOTE – dPLM is only defined for q = 31s. dPLM is assumed to be false for q = 11s, 12s, 32e. + +**Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +**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 ← dPLM and (not AI\_TSF) + +cLFD ← dLFD and (not dPLM) and (not AI\_TSF) + +cEXM ← dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM ← dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### Performance monitoring: + +For further study. + +### 11.3.2 LCAS-capable Pq to MPLS-TP adaptation functions (Pq-X-L/MT\_A; q=11s, 12s, 31s, 32e) + +#### 11.3.2.1 LCAS-capable Pq to MPLS-TP adaptation source function (Pq-X-L/MT\_A\_So) + +This function maps MT\_CI information onto a Pq-X-L\_AI signal (q=11s, 12s, 31s, 32e). + +Data at the Pq-X-L\_AP is a Pq-X (q = 11s, 12s, 31s, 32e), having a payload as described in [ITU-T G.7043]. + +##### Symbol + +The Pq-X-L/MT\_A\_So function symbol is shown in Figure 11-33. + +![Figure 11-33 – Pq-X-L/MT_A_So symbol. The diagram shows a trapezoidal block labeled 'Pq-X-L/MT_A_So'. Inputs from the top are SCC_CI and multiple MT_CI signals (indicated by three vertical lines and an ellipsis). Inputs from the bottom are Pq-X-L_AI_X_AT and Pq-X-L_AI_D (indicated by a dashed line). Outputs to the right are Pq-X-L/MT_A_So_MI and Pq-X-L_TI. An output at the bottom is Pq-X-L_AI. A small note 'G.8121-Y.1381(18)_F11-33' is present.](09db1d3c990a8ce8a2e8a35bc93cfb5f_img.jpg) + +Figure 11-33 – Pq-X-L/MT\_A\_So symbol. The diagram shows a trapezoidal block labeled 'Pq-X-L/MT\_A\_So'. Inputs from the top are SCC\_CI and multiple MT\_CI signals (indicated by three vertical lines and an ellipsis). Inputs from the bottom are Pq-X-L\_AI\_X\_AT and Pq-X-L\_AI\_D (indicated by a dashed line). Outputs to the right are Pq-X-L/MT\_A\_So\_MI and Pq-X-L\_TI. An output at the bottom is Pq-X-L\_AI. A small note 'G.8121-Y.1381(18)\_F11-33' is present. + +Figure 11-33 – Pq-X-L/MT\_A\_So symbol + +##### Interfaces + +The Pq-X-L/MT\_A\_So interfaces are described in Table 11-15. + +Table 11-15 – Pq-X-L/MT\_A\_So interfaces + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
SCC_CP:
SCC_CI_Data
Pq-X-L_AP:
Pq-X-L_AI_X_AT
Pq-X-L_TP:
Pq-X-L_TI_Clock
Pq-X-L_TI_FrameStart
Pq-X-L/MT_A_So_MP:
Pq-X-L/MT_A_So_MI_SCCType
Pq-X-L/MT_A_So_MI_Label[1...M]
Pq-X-L/MT_A_So_MI_LSPTYPE[1...M]
Pq-X-L/MT_A_So_MI_CoS[1...M]
Pq-X-L/MT_A_So_PHB2TCMapping[1...M]
Pq-X-L/MT_A_So_MI_QoSEncodingMode[1...M]
Pq-X-L/MT_A_So_MI_Mode[1...M] | Pq-X-L_AP:
Pq-X-L_AI_Data
Pq-X-L_AI_Clock
Pq-X-L_AI_FrameStart | + +**Table 11-15 – Pq-X-L/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|-------------------------------------|-----------| +| Pq-X-L/MT_A_So_MI_GAL_Enable[1...M] | | + +##### **Processes** + +A process diagram of this function is shown in Figure 11-34. + +![Figure 11-34 – Pq-X-L/MT_A_So process diagram. This flowchart illustrates the data processing pipeline for the Pq-X-L/MT_A_So function. Inputs include MT_CI_D/iPHB/oPHB[1] through MT_CI_D/iPHB/oPHB[M], MI_Label[1...M], MI_LSPTYPE[1...M], MI_CoS[1...M], MI_PHB2TCMapping[1...M], MI_QoSEncodingModel[1...M], MI_Mode[1...M], Pq-X-L_AI_X_AT, MI_SCCType, and SCC_CI. The data flows through TC/Label processes, Queueing, MPLS-TP specific GFP-F processes, Common GFP-F processes (with CMuxActive = false), Pq specific GFP-F processes (receiving Pq-X-L_TI_CK and Pq-X-L_TI_FS), and finally Pq specific processes. The output consists of Pq-X-L_AI_D, Pq-X-L_AI_CK, and Pq-X-L_AI_FS. A reference code G.8121-Y.1381(18)_F11-34 is present at the bottom right.](52ddf5847d6a0dec582fc4e972db6397_img.jpg) + +Figure 11-34 – Pq-X-L/MT\_A\_So process diagram. This flowchart illustrates the data processing pipeline for the Pq-X-L/MT\_A\_So function. Inputs include MT\_CI\_D/iPHB/oPHB[1] through MT\_CI\_D/iPHB/oPHB[M], MI\_Label[1...M], MI\_LSPTYPE[1...M], MI\_CoS[1...M], MI\_PHB2TCMapping[1...M], MI\_QoSEncodingModel[1...M], MI\_Mode[1...M], Pq-X-L\_AI\_X\_AT, MI\_SCCType, and SCC\_CI. The data flows through TC/Label processes, Queueing, MPLS-TP specific GFP-F processes, Common GFP-F processes (with CMuxActive = false), Pq specific GFP-F processes (receiving Pq-X-L\_TI\_CK and Pq-X-L\_TI\_FS), and finally Pq specific processes. The output consists of Pq-X-L\_AI\_D, Pq-X-L\_AI\_CK, and Pq-X-L\_AI\_FS. A reference code G.8121-Y.1381(18)\_F11-34 is present at the bottom right. + +**Figure 11-34 – Pq-X-L/MT\_A\_So process diagram** + +The processes have the same definition as in clause 11.1.1.1. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### **11.3.2.2 LCAS-capable Pq to MPLS-TP adaptation sink function (Pq-X-L/MT\_A\_Sk)** + +This function extracts MT\_CI information from the Pq-X-L\_AI signal (q = 11s, 12s, 31s, 32e), delivering MT\_CI. + +Data at the Pq-X-L\_AP is a Pq-Xv (q = 11s, 12s, 31s, 32e), having a payload as described in [ITU-T G.703]. + +##### Symbol + +The Pq-X-L/MT\_A\_Sk function symbol is shown in Figure 11-35. + +![Figure 11-35 – Pq-X-L/MT_A_Sk symbol. The diagram shows a trapezoidal function symbol labeled 'Pq-X-L/MT_A_Sk'. Inputs are shown at the bottom: 'Pq-X-L_AI_X_AR' and 'Pq-X-L_AI_D' (with a vertical dashed line between them), and 'Pq-X-L_AI' below. An input 'Pq-X-L/MT_A_Sk_MI' points to the right side. Outputs are shown at the top: 'SCC_CI' and 'MT_CI' (with an ellipsis between them). A reference code 'G.8121-Y.1381(18)_F11-35' is at the bottom right.](d7896dd2d38adf224c3b76cd22d29c10_img.jpg) + +Figure 11-35 – Pq-X-L/MT\_A\_Sk symbol. The diagram shows a trapezoidal function symbol labeled 'Pq-X-L/MT\_A\_Sk'. Inputs are shown at the bottom: 'Pq-X-L\_AI\_X\_AR' and 'Pq-X-L\_AI\_D' (with a vertical dashed line between them), and 'Pq-X-L\_AI' below. An input 'Pq-X-L/MT\_A\_Sk\_MI' points to the right side. Outputs are shown at the top: 'SCC\_CI' and 'MT\_CI' (with an ellipsis between them). A reference code 'G.8121-Y.1381(18)\_F11-35' is at the bottom right. + +**Figure 11-35 – Pq-X-L/MT\_A\_Sk symbol** + +##### Interfaces + +The Pq-X-L/MT\_A\_Sk interfaces are described in Table 11-16. + +**Table 11-16 – Pq-X-L/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pq-X-L_AP:
Pq-X-L_AI_Data
Pq-X-L_AI_Clock
Pq-X-L_AI_FrameStart
Pq-X-L_AI_TSF
Pq-X-L_AI_XAR
Pq-X-L/MT_A_Sk_MP:
Pq-X-L/MT_A_Sk_MI_SCCType
Pq-X-L/MT_A_Sk_MI_Label[1...M]
Pq-X-L/MT_A_Sk_MI_LSPTYPE[1...M]
Pq-X-L/MT_A_Sk_MI_CoS[1...M]
Pq-X-L/MT_A_Sk_MI_TC2PHBMapping[1...M]
Pq-X-L/MT_A_Sk_MI_QoSDecodingMode[1...M]
Pq-X-L/MT_A_Sk_MI_Mode[1...M]

Pq-X-L/MT_A_Sk_MI_LCK_Period[1...M]
Pq-X-L/MT_A_Sk_MI_LCK_P[1...M]
Pq-X-L/MT_A_Sk_MI_Admin_State
Pq-X-L/MT_A_Sk_MI_AIS_Period[1...M]
Pq-X-L/MT_A_Sk_MI_AIS_P[1...M]

Pq-X-L/MT_A_Sk_MI_GAL_Enable[1...M]
Pq-X-L/MT_A_Sk_MI_LCK_Tool[1...M]
Pq-X-L/MT_A_Sk_MI_AIS_Tool[1...M] | Each MT_CP:
MT_CI_Data
MT_CI_iPHB
MT_CI_oPHB
MT_CI_SSF
MT_CI_LStack

SCC_CP:
SCC_CI_Data
SCC_CI_SSF

Pq-X-L/MT_A_Sk_MP:
Pq-X-L/MT_A_Sk_MI_AcSL
Pq-X-L/MT_A_Sk_MI_AcEXI
Pq-X-L/MT_A_Sk_MI_LastInvalidUPI
Pq-X-L/MT_A_Sk_MI_cPLM
Pq-X-L/MT_A_Sk_MI_cLFD
Pq-X-L/MT_A_Sk_MI_cEXM
Pq-X-L/MT_A_Sk_MI_cUPM | + +##### Processes + +The Pq-X-L/MT\_A\_Sk process diagram is illustrated in Figure 11-36. + +![Figure 11-36 – Pq-X-L/MT_A_Sk process diagram. This is a complex block diagram showing the internal architecture of a network element. At the bottom, multiple 'Pq specific processes' are shown, receiving inputs from 'Pq-X-L_AI_D/CK/SF/TSF' and 'Pq-X-L_AI_X_AT'. These processes output to 'Pq specific GFP-F processes', which in turn output to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' is associated with the 'Common GFP-F processes' block. Above 'Common GFP-F processes' is the 'MPLS-TP specific GFP-F processes' block, which receives 'GFP_Frame/SF/FS' and 'Mixed MT_CI_D' inputs. It outputs to 'Label stack copy', which then outputs to 'TC/Label processes'. 'TC/Label processes' receive 'Mixed D' and 'Mixed LStack' inputs and output to 'Consequent action' blocks. 'Consequent action' blocks output to 'MT_CI_SSF[1...M]' and 'MT_CI_SSF[M]'. Above 'Consequent action' are two 'Selector' blocks with 'Normal' and 'LCK' options. These receive 'D, iPHB, oPHB' inputs and output to 'MT_CI_D/iPHB/oPHB[1]' and 'MT_CI_D/iPHB/oPHB[M]'. 'Selector' blocks also receive 'AIS insert' and 'LCK generate' inputs from 'Consequent action' blocks. 'AIS insert' and 'LCK generate' blocks receive 'aAIS' inputs. Various management interfaces are shown: 'MI_Label[1...M]', 'MI_LSPTYPE[1...M]', 'MI_CoS[1...M]', 'MI_PHB2TCMapping[1...M]', 'MI_QoSEncodingModel[1...M]', 'MI_Mode[1...M]' on the left; 'MI_LastInvalidUPI', 'MI_SCCType', 'MI_AcEXI', 'MI_AcSL' on the left; 'MI_cUPM', 'MI_cEXM', 'MI_cLFD', 'MI_cPLM' on the right; and 'MI_Admin_State', 'MI_LCK_Period/CoS/OAM_Tool[1...M]', 'MI_GAL_Enable[1...M]', 'MI_AIS_Period/CoS/OAM_Tool[1...M]', 'MI_GAL_Enable[1...M]' on the right. Top right outputs include 'MI_CI_LStack[1...M]', 'SCC_CI_D', and 'SCC_CI_SSF'. A reference code 'G.8121-Y.1381(18)_F11-36' is in the bottom right corner.](b8dd9521b601d25e46c5effa0a59b7e1_img.jpg) + +Figure 11-36 – Pq-X-L/MT\_A\_Sk process diagram. This is a complex block diagram showing the internal architecture of a network element. At the bottom, multiple 'Pq specific processes' are shown, receiving inputs from 'Pq-X-L\_AI\_D/CK/SF/TSF' and 'Pq-X-L\_AI\_X\_AT'. These processes output to 'Pq specific GFP-F processes', which in turn output to 'Common GFP-F processes'. A dashed line labeled 'CMuxActive = false' is associated with the 'Common GFP-F processes' block. Above 'Common GFP-F processes' is the 'MPLS-TP specific GFP-F processes' block, which receives 'GFP\_Frame/SF/FS' and 'Mixed MT\_CI\_D' inputs. It outputs to 'Label stack copy', which then outputs to 'TC/Label processes'. 'TC/Label processes' receive 'Mixed D' and 'Mixed LStack' inputs and output to 'Consequent action' blocks. 'Consequent action' blocks output to 'MT\_CI\_SSF[1...M]' and 'MT\_CI\_SSF[M]'. Above 'Consequent action' are two 'Selector' blocks with 'Normal' and 'LCK' options. These receive 'D, iPHB, oPHB' inputs and output to 'MT\_CI\_D/iPHB/oPHB[1]' and 'MT\_CI\_D/iPHB/oPHB[M]'. 'Selector' blocks also receive 'AIS insert' and 'LCK generate' inputs from 'Consequent action' blocks. 'AIS insert' and 'LCK generate' blocks receive 'aAIS' inputs. Various management interfaces are shown: 'MI\_Label[1...M]', 'MI\_LSPTYPE[1...M]', 'MI\_CoS[1...M]', 'MI\_PHB2TCMapping[1...M]', 'MI\_QoSEncodingModel[1...M]', 'MI\_Mode[1...M]' on the left; 'MI\_LastInvalidUPI', 'MI\_SCCType', 'MI\_AcEXI', 'MI\_AcSL' on the left; 'MI\_cUPM', 'MI\_cEXM', 'MI\_cLFD', 'MI\_cPLM' on the right; and 'MI\_Admin\_State', 'MI\_LCK\_Period/CoS/OAM\_Tool[1...M]', 'MI\_GAL\_Enable[1...M]', 'MI\_AIS\_Period/CoS/OAM\_Tool[1...M]', 'MI\_GAL\_Enable[1...M]' on the right. Top right outputs include 'MI\_CI\_LStack[1...M]', 'SCC\_CI\_D', and 'SCC\_CI\_SSF'. A reference code 'G.8121-Y.1381(18)\_F11-36' is in the bottom right corner. + +**Figure 11-36 – Pq-X-L/MT\_A\_Sk process diagram** + +See process diagram and process description in clause 11.1.1.2. The additional Pq-X-L\_AI\_XAR interface is not connected to any of the internal processes. + +##### **Defects:** + +dPLM – See clause 6.2.4.2 of [ITU-T G.806]. + +dLFD – See clause 6.2.5.2 of [ITU-T G.806]. + +dUPM – See clause 8.4.2. + +dEXM – See clause 6.2.4.4 of [ITU-T G.806]. + +NOTE: dPLM is only defined for q = 31s. dPLM is assumed to be false for q = 11s, 12s, 32e. + +##### **Consequent actions:** + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +aAIS ← AI\_TSF or dPLM or dLFD or dUPM or dEXM + +##### 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) + +cEXM $\leftarrow$ dEXM and (not dPLM) and (not dLFD) and (not AI\_TSF) + +cUPM $\leftarrow$ dUPM and (not dEXM) and (not dPLM) and (not dLFD) and (not AI\_TSF) + +##### Performance monitoring: + +For further study. + +## 11.4 Ethernet to MPLS-TP adaptation function + +### 11.4.1 ETH to MPLS-TP adaptation function (ETH/MT\_A) + +#### 11.4.1.1 ETH to MPLS-TP adaptation source function (ETH/MT\_A\_So) + +##### Symbol + +The ETH/MT\_A\_So function symbol is shown in Figure 11-37. + +![Diagram of the ETH/MT_A_So function symbol. The symbol is a trapezoid labeled 'ETH/MT_A_So'. Above it, multiple vertical arrows labeled 'MT_CI' point down into the trapezoid. To the right, a horizontal double-headed arrow labeled 'ETH/MT_A_So_MI' connects the trapezoid to the text 'ETH/MT_A_So_MI'. Below the trapezoid, a vertical arrow points down to the text 'ETH_FP (ETH_AI)'. In the bottom right corner of the diagram, the text 'G.8121-Y.1381(18)_F11-37' is present.](418ac859afe534b37c6f4e96e15c0b25_img.jpg) + +Diagram of the ETH/MT\_A\_So function symbol. The symbol is a trapezoid labeled "ETH/MT\_A\_So". Above it, multiple vertical arrows labeled "MT\_CI" point down into the trapezoid. To the right, a horizontal double-headed arrow labeled "ETH/MT\_A\_So\_MI" connects the trapezoid to the text "ETH/MT\_A\_So\_MI". Below the trapezoid, a vertical arrow points down to the text "ETH\_FP (ETH\_AI)". In the bottom right corner of the diagram, the text "G.8121-Y.1381(18)\_F11-37" is present. + +Diagram of the ETH/MT\_A\_So function symbol. The symbol is a trapezoid labeled 'ETH/MT\_A\_So'. Above it, multiple vertical arrows labeled 'MT\_CI' point down into the trapezoid. To the right, a horizontal double-headed arrow labeled 'ETH/MT\_A\_So\_MI' connects the trapezoid to the text 'ETH/MT\_A\_So\_MI'. Below the trapezoid, a vertical arrow points down to the text 'ETH\_FP (ETH\_AI)'. In the bottom right corner of the diagram, the text 'G.8121-Y.1381(18)\_F11-37' is present. + +Figure 11-37 – ETH/MT\_A\_So symbol + +##### Interfaces + +The ETH/MT\_A\_So interfaces are described in Table 11-17. + +**Table 11-17 – ETH/MT\_A\_So interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Each MT_CP:
MT_CI_Data[1..M]
MT_CI_iPHB[1..M]
MT_CI_oPHB[1..M]

ETH/MT_A_So_MP:
ETH/MT_A_So_MI_Label[1..M]
ETH/MT_A_So_MI_LSPTYPE[1..M]
ETH/MT_A_So_MI_CoS[1..M]
ETH/MT_A_So_PHB2TCMapping[1..M]
ETH/MT_A_So_MI_QoSEncodingMode[1..M]
ETH/MT_A_So_MI_Mode[1..M]
ETH/MT_A_So_MI_Etype

ETH/MT_A_So_MI_GAL_Enable[1..M] | ETYn_AP:
ETH_AI_Data
ETH_AI_P
ETH_AI_DE | + +##### **Processes** + +A process diagram of this function is shown in Figure 11-38. + +![Figure 11-38 – ETH/MT_A_So process diagram. The diagram shows a flow from multiple MT inputs (MT_CI_D/iPHB/oPHB[1] to MT_CI_D/iPHB/oPHB[M]) through a 'TC/Label processes' block, then a 'Queueing' block, and finally an 'MPLS-TP specific Ethernet process' block. Inputs include MI_Label[1..M], MI_LSPTYPE[1..M], MI_CoS[1..M], MI_PHB2TCMapping[1..M], MI_QoSEncodingMode[1..M], MI_Mode[1..M], and MI_Etype. The output is ETH_FP (ETH_AI_D/DE/P). A 'Muxed D/PHB' label is present next to the Queueing block. The diagram is labeled G.8121-Y.1381(18)_F11-38.](b15cf8c50195a52cca59b4645c6f59fa_img.jpg) + +Figure 11-38 – ETH/MT\_A\_So process diagram. The diagram shows a flow from multiple MT inputs (MT\_CI\_D/iPHB/oPHB[1] to MT\_CI\_D/iPHB/oPHB[M]) through a 'TC/Label processes' block, then a 'Queueing' block, and finally an 'MPLS-TP specific Ethernet process' block. Inputs include MI\_Label[1..M], MI\_LSPTYPE[1..M], MI\_CoS[1..M], MI\_PHB2TCMapping[1..M], MI\_QoSEncodingMode[1..M], MI\_Mode[1..M], and MI\_Etype. The output is ETH\_FP (ETH\_AI\_D/DE/P). A 'Muxed D/PHB' label is present next to the Queueing block. The diagram is labeled G.8121-Y.1381(18)\_F11-38. + +**Figure 11-38 – ETH/MT\_A\_So process** + +- *TC/Label processing* + +See clause 8.2.1. + +- *Queueing process:* + +See clause 8.3. + +- *MPLS-TP specific Ethernet process:* + +This process inserts the Ethertype for MPLS-TP packets according to [IETF RFC 5332]. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +#### 11.4.1.2 ETH to MPLS-TP adaptation sink function (ETH/MT\_A\_Sk) + +##### Symbol + +The ETH/MT\_A\_Sk function symbol is shown in Figure 11-39. + +![Figure 11-39 – ETH/MT_A_Sk symbol. The diagram shows a trapezoidal symbol labeled 'ETH/MT_A_Sk'. Above the symbol, three upward-pointing arrows are shown with an ellipsis between them. Below the symbol, an upward-pointing arrow is labeled 'ETH_FP (ETH_AI)'. To the right of the symbol, a double-headed horizontal arrow is labeled 'ETH/MT_A_Sk_MI'. In the bottom right corner of the diagram area, the text 'G.8121-Y.1381(18)_F11-39' is present.](ffe2d3e622dd30bea4caf15951c60e42_img.jpg) + +Figure 11-39 – ETH/MT\_A\_Sk symbol. The diagram shows a trapezoidal symbol labeled 'ETH/MT\_A\_Sk'. Above the symbol, three upward-pointing arrows are shown with an ellipsis between them. Below the symbol, an upward-pointing arrow is labeled 'ETH\_FP (ETH\_AI)'. To the right of the symbol, a double-headed horizontal arrow is labeled 'ETH/MT\_A\_Sk\_MI'. In the bottom right corner of the diagram area, the text 'G.8121-Y.1381(18)\_F11-39' is present. + +**Figure 11-39 – ETH/MT\_A\_Sk symbol** + +##### Interfaces + +The ETH/MT\_A\_Sk interfaces are described in Table 11-18. + +**Table 11-18 – ETH/MT\_A\_Sk interfaces** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| ETH_AP:
ETH_AI_Data
ETH_AI_P
ETH_AI_DE
ETH_AI_TSF
ETH_AI_AIS

ETH/MT_A_Sk_MP:
ETH/MT_A_Sk_MI_Etype
ETH/MT_A_Sk_MI_Frame_Type_Config

ETH/MT_A_Sk_MI_Label[1...M]
ETH/MT_A_Sk_MI_LSPTYPE[1...M]
ETH/MT_A_Sk_MI_CoS[1...M]
ETH/MT_A_Sk_MI_TC2PHBMapping[1...M]
ETH/MT_A_Sk_MI_QoSDecodingMode[1...M]
ETH/MT_A_Sk_MI_Mode[1...M]

ETH/MT_A_Sk_MI_GAL_Enable[1...M]
ETH/MT_A_Sk_MI_Admin_State

ETH/MT_A_Sk_MI_LCK_Period[1...M]
ETH/MT_A_Sk_MI_LCK_CoS[1...M]

ETH/MT_A_Sk_MI_AIS_Period[1...M]
ETH/MT_A_Sk_MI_AIS_CoS[1...M]
ETH/MT_A_Sk_MI_LCK_OAM_Tool[1...M]
ETH/MT_A_Sk_MI_AIS_OAM_Tool[1...M] | Each MT_CP:
MT_CI_Data[1...M]
MT_CI_iPHB[1...M]
MT_CI_oPHB[1...M]
MI_CI_Lstack[1...M] | + +##### Processes + +A process diagram of this function is shown in Figure 11-40. + +![Figure 11-40 – ETH/MT_A_Sk process diagram. This block diagram illustrates the data flow and processing within the ETH/MT_A_Sk function. At the bottom, an input labeled 'ETH_FP (ETH_AL_D/DE/P)' enters the 'MPLS-TP specific frame type filter'. Above this filter, several configuration parameters are listed: 'MI_Label[1...M]', 'MI_LSPTYPE[1...M]', 'MI_CoS[1...M]', 'MI_PHB2TCMapping[1...M]', 'MI_QoSEncodingModel[1...M]', 'MI_Mode[1...M]', 'MI_Etype', and 'MI_Frame_type_config'. The filter outputs 'Mixed MT_CI_D/PHB' to a 'Label stack copy' block. The 'Label stack copy' block outputs 'Mixed D/PHB' and 'Mixed LStack' to 'TC/Label processes'. From 'TC/Label processes', data flows to 'Consequent action' and 'AIS insert' blocks. The 'Consequent action' block outputs 'MT_CI_SSF[1...M]'. The 'AIS insert' block outputs 'D, iPHB, oPHB' to a 'Selector' block. The 'Selector' block has 'Normal' and 'LCK' paths and outputs 'MT_CI_D/iPHB/oPHB[1]' and 'MT_CI_D/iPHB/oPHB[M]'. The 'LCK generate' block within the 'AIS insert' process also outputs 'D, iPHB, oPHB' to the 'Selector'. The 'Selector' block also receives 'MI_Admin_State', 'MI_GAL_Enable[1...M]', 'MI_LCK_Period/CoS/OAM_Tool[1...M]', 'MI_GAL_Enable[1...M]', and 'MI_AIS_Period/CoS/OAM_Tool[1...M]'. Finally, the 'Selector' block outputs 'MT_CI_LStack[1...M]'.](6a2b92323d788c2e7e9e570025885181_img.jpg) + +Figure 11-40 – ETH/MT\_A\_Sk process diagram. This block diagram illustrates the data flow and processing within the ETH/MT\_A\_Sk function. At the bottom, an input labeled 'ETH\_FP (ETH\_AL\_D/DE/P)' enters the 'MPLS-TP specific frame type filter'. Above this filter, several configuration parameters are listed: 'MI\_Label[1...M]', 'MI\_LSPTYPE[1...M]', 'MI\_CoS[1...M]', 'MI\_PHB2TCMapping[1...M]', 'MI\_QoSEncodingModel[1...M]', 'MI\_Mode[1...M]', 'MI\_Etype', and 'MI\_Frame\_type\_config'. The filter outputs 'Mixed MT\_CI\_D/PHB' to a 'Label stack copy' block. The 'Label stack copy' block outputs 'Mixed D/PHB' and 'Mixed LStack' to 'TC/Label processes'. From 'TC/Label processes', data flows to 'Consequent action' and 'AIS insert' blocks. The 'Consequent action' block outputs 'MT\_CI\_SSF[1...M]'. The 'AIS insert' block outputs 'D, iPHB, oPHB' to a 'Selector' block. The 'Selector' block has 'Normal' and 'LCK' paths and outputs 'MT\_CI\_D/iPHB/oPHB[1]' and 'MT\_CI\_D/iPHB/oPHB[M]'. The 'LCK generate' block within the 'AIS insert' process also outputs 'D, iPHB, oPHB' to the 'Selector'. The 'Selector' block also receives 'MI\_Admin\_State', 'MI\_GAL\_Enable[1...M]', 'MI\_LCK\_Period/CoS/OAM\_Tool[1...M]', 'MI\_GAL\_Enable[1...M]', and 'MI\_AIS\_Period/CoS/OAM\_Tool[1...M]'. Finally, the 'Selector' block outputs 'MT\_CI\_LStack[1...M]'. + +**Figure 11-40 – ETH/MT\_A\_Sk process** + +- *Selector generation process:* + +See clause 8.6.1. The normal CI is blocked if Admin\_State = LOCKED. + +- *AIS insert process:* + +See clause 8.6.2. There is a single AIS insert process for each MT. + +- *LCK generation process:* + +See clause 8.6.3. There is a single LCK generation process for each MT. + +- *TC/Label sink processes:* + +See clause 8.2.2. + +- *Label stack copy process:* + +See clause 8.2.3. + +- *MPLS-TP specific Filter process:* + +This process is for the reception process of the Ethertype for MPLS-TP packets according to [IETF RFC 5332]. + +**Defects:** None. + +**Consequent actions:** For further study. + +**Defect correlations:** None. + +**Performance monitoring:** For further study. + +# Appendix I + +## Examples of processing of packets with expired TTL + +(This appendix does not form an integral part of this Recommendation.) + +MPLS-TP packets received with an expired TTL shall not be forwarded. However, MPLS-TP OAM packets received with an expired TTL can be processed and their processing can happen at different locations (i.e., from different atomic functions) within a MPLS-TP equipment. + +The proper behaviour depends on the MPLS-TP connection configuration within the node. The following examples are considered and are described: + +- Intermediate node with no MIPs +- Intermediate node – interface MIPs +- Intermediate node – node MIP +- Terminating node – down MEP or node MEP +- Terminating node – up MEP (with interface MIP) + +NOTE – As indicated in clause 9.4.2.2.2, the MI\_DS\_MP\_Type parameter should be properly configured by the EMF and not exposed to the operator as a configuration parameter of the NE management. The examples described in this appendix provide guidelines on how the EMF can properly configure the MI\_DS\_MP\_Type. + +Figure I.1 describes the behaviour of an intermediate node with no MIPs using the atomic functions defined in this Recommendation: + +![Diagram of an intermediate node with no MIPs. It shows a central oval labeled MT_C connected to two trapezoidal blocks labeled Srv/MT. The left Srv/MT is connected to MT_C via a CP (Control Plane) point. The right Srv/MT is also connected to MT_C. Arrows indicate traffic flow: from the left Srv/MT up to the CP, then up to MT_C, and from MT_C down to the right Srv/MT. Below the diagram is the text G.8121-Y.1381(16)_Fl.1.](813ef40a14c7e2a52988a63e33c2b59f_img.jpg) + +G.8121-Y.1381(16)\_Fl.1 + +Diagram of an intermediate node with no MIPs. It shows a central oval labeled MT\_C connected to two trapezoidal blocks labeled Srv/MT. The left Srv/MT is connected to MT\_C via a CP (Control Plane) point. The right Srv/MT is also connected to MT\_C. Arrows indicate traffic flow: from the left Srv/MT up to the CP, then up to MT\_C, and from MT\_C down to the right Srv/MT. Below the diagram is the text G.8121-Y.1381(16)\_Fl.1. + +NOTE – Srv can be any server (MT or non-MT). + +**Figure I.1 – Intermediate node with no MIPs** + +The Server/MT\_A\_Sk is connected to the MT\_C via a MT\_CP. Therefore, the TTL decrement process, as defined in clause 8.2.2, will discard all the MPLS-TP packets (user data or OAM) that are received with an expired TTL. + +Figure I.2 describes the behaviour of an intermediate node supporting per-interface MIPs using the atomic functions defined in this Recommendation: + +![Diagram of an intermediate node with per-interface MIPs. At the top is an oval labeled MT_C. Below it are two yellow diamond-shaped MIP blocks. The left MIP has an arrow pointing up to MT_C and an arrow pointing down to a trapezoidal Srv/MT block. Between these arrows is a small circle labeled TCP. An arrow from the left points to the left MIP with the label MI_DS_MP_Type = MIP. The right MIP has an arrow pointing up to MT_C and an arrow pointing down to another trapezoidal Srv/MT block. Between these arrows is a label MI_DS_MP_Type = none. Below the right Srv/MT block is the text G.8121-Y.1381(16)_Fl.2.](3abb87a27232fe2f2806b67f2e5e1390_img.jpg) + +Diagram of an intermediate node with per-interface MIPs. At the top is an oval labeled MT\_C. Below it are two yellow diamond-shaped MIP blocks. The left MIP has an arrow pointing up to MT\_C and an arrow pointing down to a trapezoidal Srv/MT block. Between these arrows is a small circle labeled TCP. An arrow from the left points to the left MIP with the label MI\_DS\_MP\_Type = MIP. The right MIP has an arrow pointing up to MT\_C and an arrow pointing down to another trapezoidal Srv/MT block. Between these arrows is a label MI\_DS\_MP\_Type = none. Below the right Srv/MT block is the text G.8121-Y.1381(16)\_Fl.2. + +NOTE – Srv can be any server (MT or non-MT). + +**Figure I.2 – Intermediate node with per-interface MIPs** + +The Server/MT\_A\_Sk is connected to ingress MIP via a MT\_TCP. Therefore, the TTL decrement process, as defined in clause 8.2.2, will forward all the MPLS-TP packets (user data or OAM) that are received with an expired TTL to the ingress MIP. + +The MTDi\_TT\_Sk atomic function within the ingress MIP will process all the MPLS-TP OAM packets received with an expired TTL and which are targeted to the ingress MIP. + +The TTL check process in the MTDi/MT\_A\_Sk within the ingress MIP, as defined in clause 9.4.2.2.2, is properly configured by the EMF (MI\_DS\_MP\_Type=MIP) to drop all the MPLS-TP user data packets received with an expired TTL and to forward all the MPLS-TP OAM packets received with an expired TTL together (i.e., with fate share) with all the MPLS-TP packets received with a non-expired TTL. + +These packets are forwarded up to the egress MIP where the MTDi\_TT\_Sk atomic function will process all the MPLS-TP OAM packets received with an expired TTL and which are targeted to the egress MIP. + +The TTL check process in the MTDi/MT\_A\_Sk within the egress MIP, as defined in clause 9.4.2.2.2, is properly configured by the EMF (MI\_DS\_MP\_Type=none) to drop all the MPLS-TP packets received with an expired TTL. Although MPLS-TP user data packets with an expired TTL will never arrive at this point, this check will ensure also that any MPLS-TP OAM packet with an expired TTL is not forwarded. + +Figure I.3 describes the behaviour of an intermediate node with a per-node MIP using the atomic functions defined in this Recommendation. The per-node MIP is modelled as being composed by two half-MIPs on each side of the MT\_C: + +![Diagram of an intermediate node with a per-node MIP. At the top is an oval labeled MT_C. Below it are two yellow inverted triangles labeled 'Half MIP'. The left 'Half MIP' has an incoming arrow from the left labeled 'MI_DS_MP_Type = none' and an outgoing arrow pointing up to MT_C. The right 'Half MIP' has an incoming arrow pointing down from MT_C and an outgoing arrow pointing down. Between the 'Half MIP' triangles and the bottom trapezoids labeled 'Srv/MT' are TCP connection symbols (a circle with a dot). Arrows point from the 'Half MIP' triangles to the 'Srv/MT' trapezoids. A final arrow points down from the right 'Srv/MT' trapezoid. The diagram is labeled G.8121-Y.1381(16)_FI.3 at the bottom right.](ce06eec6bb6d76bf7688932b2f6eb6fa_img.jpg) + +Diagram of an intermediate node with a per-node MIP. At the top is an oval labeled MT\_C. Below it are two yellow inverted triangles labeled 'Half MIP'. The left 'Half MIP' has an incoming arrow from the left labeled 'MI\_DS\_MP\_Type = none' and an outgoing arrow pointing up to MT\_C. The right 'Half MIP' has an incoming arrow pointing down from MT\_C and an outgoing arrow pointing down. Between the 'Half MIP' triangles and the bottom trapezoids labeled 'Srv/MT' are TCP connection symbols (a circle with a dot). Arrows point from the 'Half MIP' triangles to the 'Srv/MT' trapezoids. A final arrow points down from the right 'Srv/MT' trapezoid. The diagram is labeled G.8121-Y.1381(16)\_FI.3 at the bottom right. + +NOTE – Srv can be any server (MT or non-MT). + +**Figure I.3 – Intermediate node with a per-node MIP** + +The Server/MT\_A\_Sk is connected to ingress MIP via a MT\_TCP. Therefore, the TTL decrement process, as defined in clause 8.2.2, will forward all the MPLS-TP packets (user data or OAM) that are received with an expired TTL to the ingress half-MIP. + +The MTDi\_TT\_Sk atomic function within the ingress half-MIP will process all the MPLS-TP OAM packets received with an expired TTL and which are targeted to the node MIP. + +The TTL check process in the MTDi/MT\_A\_Sk, as defined in clause 9.4.2.2.2, is properly configured by the EMF (MI\_DS\_MP\_Type=none) to drop all the MPLS-TP packets (user data or OAM) that are received with an expired TTL. + +Figure I.4 describes the behaviour of a terminating node with a down MEP or a per-node MEP using the atomic functions defined in this Recommendation. These two cases are modelled in the same way: + +![Diagram of a terminating node with a down MEP or node MEP. At the top is a yellow inverted triangle labeled 'MEP'. Below it is a TCP connection symbol (a circle with a dot). Below that is a trapezoid labeled 'Srv/MT'. Arrows point from the 'Srv/MT' trapezoid up through the TCP symbol to the 'MEP' triangle. A final arrow points up into the 'Srv/MT' trapezoid from the bottom. The diagram is labeled G.8121-Y.1381(16)_FI.4 at the bottom right.](02f3fc8e346370e82afa09b56ad7f83b_img.jpg) + +Diagram of a terminating node with a down MEP or node MEP. At the top is a yellow inverted triangle labeled 'MEP'. Below it is a TCP connection symbol (a circle with a dot). Below that is a trapezoid labeled 'Srv/MT'. Arrows point from the 'Srv/MT' trapezoid up through the TCP symbol to the 'MEP' triangle. A final arrow points up into the 'Srv/MT' trapezoid from the bottom. The diagram is labeled G.8121-Y.1381(16)\_FI.4 at the bottom right. + +NOTE – Srv can be any server (MT or non-MT). + +**Figure I.4 – Terminating node with a down MEP or node MEP** + +The Server/MT\_A\_Sk is connected to MEP via a MT\_TCP. Therefore, the TTL decrement process, as defined in clause 8.2.2, will forward all the MPLS-TP packets (user data or OAM) that are received with an expired TTL to the MEP. + +The MEP terminates the MPLS-TP trail and processes all the MPLS-TP packets it receives regardless of whether the TTL has expired or not. + +Figure I.5 describes the behaviour of a terminating node with an Up MEP, and therefore a per-interface ingress MIP, using the atomic functions defined in this Recommendation: + +![Diagram of a terminating node (MT_C) with an Up MEP and a per-interface MIP. The diagram shows a central node MT_C connected to a yellow diamond-shaped MIP and a yellow triangle-shaped MEP. The MIP is connected to a TCP layer, which is connected to a trapezoidal Srv/MT node. An arrow labeled 'MI_DS_MP_Type = MEP' points to the MIP. A small blue circle is on the TCP layer. The diagram is labeled G.8121-Y.1381(16)_FI.5.](2cc98b619abc7a0e53aac9c44226ca89_img.jpg) + +The diagram illustrates a terminating node (MT\_C) at the top, represented by an oval. Below it, a yellow diamond labeled 'MIP' and a yellow triangle labeled 'MEP' are shown. An arrow points from the MIP to the MT\_C, and another arrow points from the MT\_C to the MEP. To the left of the MIP, an arrow labeled 'MI\_DS\_MP\_Type = MEP' points towards it. Below the MIP, a blue circle labeled 'TCP' is connected to a trapezoidal node labeled 'Srv/MT'. An arrow points from the Srv/MT node up to the TCP layer. In the bottom right corner, the text 'G.8121-Y.1381(16)\_FI.5' is present. + +Diagram of a terminating node (MT\_C) with an Up MEP and a per-interface MIP. The diagram shows a central node MT\_C connected to a yellow diamond-shaped MIP and a yellow triangle-shaped MEP. The MIP is connected to a TCP layer, which is connected to a trapezoidal Srv/MT node. An arrow labeled 'MI\_DS\_MP\_Type = MEP' points to the MIP. A small blue circle is on the TCP layer. The diagram is labeled G.8121-Y.1381(16)\_FI.5. + +NOTE – Srv can be any server (MT or non-MT). + +**Figure I.5 – Terminating node with an Up MEP (and a per-interface MIP)** + +The Server/MT\_A\_Sk is connected to ingress MIP via a MT\_TCP. Therefore, the TTL decrement process, as defined in clause 8.2.2, will forward all the MPLS-TP packets (user data or OAM) that are received with an expired TTL to the ingress MIP. + +The MTDi\_TT\_Sk atomic function within the ingress MIP will process all the MPLS-TP OAM packets received with an expired TTL and which are targeted to the ingress MIP. + +The TTL check process in the MTDi/MT\_A\_Sk within the ingress MIP, as defined in clause 9.4.2.2.2, is properly configured by the EMF (MI\_DS\_MP\_Type=MEP) to forward all the MPLS-TP packets (user data or OAM) that are received with an expired TTL together (i.e., with fate share) with all the MPLS-TP packets received with a non-expired TTL. + +These packets are forwarded up to the Up MEP that terminates the MPLS-TP trail and processes all the MPLS-TP packets it receives regardless of whether the TTL has expired or not. + +# Appendix II + +## Flow of PHB information through MEP and MIP + +(This appendix does not form an integral part of this Recommendation.) + +This Recommendation describes the various atomic functions that comprise MIPs and MEPs: + +- MEP: MT/MT\_A, MT\_TT, MTDe/MT\_A, MTDe\_TT +- MIP: Two MHFs each comprising MTDi\_TT, MTDi/MT\_A + +The handling of PHB values is described in clauses 8.2, 9.2, 9.3 and 9.4. The PHB information is passed between the atomic functions in characteristic information (CI) and adapted information (AI). + +As described in clause 10 of [ITU-T G.8110.1], the MPLS-TP Diffserv architecture supports two models: the "Short Pipe" model, and the "Uniform" model. To support this, it is necessary in certain cases to pass two PHB values in the CI and the AI, referred to as the incoming PHB (iPHB) and outgoing PHB (oPHB). In other cases, only a single PHB values needs to be passed between the atomic functions. + +Figures 10-1 and 10-2 of [ITU-T G.8110.1] are the reference diagrams showing how PHB values are used in the two models. However, these do not show all of the atomic functions defined in this Recommendation that comprise MEPs and MIPs. So, in particular, it is unclear at a first glance why in some cases the AI carries a single PHB value, while in other cases it carries separate iPHB and oPHB values. + +Figure II.1 and II.2 show a MEP and a MIP and illustrate the flow of PHB information through them. The iPHB values are shown in green, oPHB values in red, and where only a single PHB value is used, this is shown in black. + +![Figure II.1 – Flow of PHB information through a MEP. The diagram shows two vertical paths of data flow within a dashed box labeled 'MEP'. The left path represents the 'TC/Label source process' and the right path represents the 'TC/Label sink process'. Both paths show the flow of PHB information through various atomic functions (MT/MT_A, MT_TT, MTDe/MT_A, MTDe_TT) in both Source (So) and Sink (Sk) modes. PHB values are represented by green lines for iPHB and red lines for oPHB. In the source process, the TC/Label source process selects iPHB or oPHB depending on MI_QoSEncodingMode and also uses this value to determine the TC. In the sink process, the TC/Label sink process uses received TC to determine iPHB and selects this or AI_PHB to determine oPHB depending on MI_QoSDecodingMode. The diagram includes labels for CI_iPHB, CI_oPHB, AI_PHB, AI_iPHB, and AI_oPHB at various points in the flow.](107942f4434bbcf421cb2554330f7536_img.jpg) + +The diagram illustrates the flow of PHB information through a MEP, divided into two main vertical paths within a dashed box labeled 'MEP'. + +- Left Path (TC/Label source process):** This path shows the flow of PHB information from top to bottom. It starts with CI\_iPHB (green) and CI\_oPHB (red) entering the MT/MT\_A\_So atomic function. The TC/Label source process selects iPHB or oPHB depending on MI\_QoSEncodingMode and also uses this value to determine the TC. The output is AI\_PHB (black), which then flows into the MT\_TT\_So atomic function. The output of MT\_TT\_So is CI\_iPHB (green) and CI\_oPHB (red), which then flow into the MTDe/MT\_A\_So atomic function. The output of MTDe/MT\_A\_So is AI\_iPHB (green) and AI\_oPHB (red), which then flow into the MTDe\_TT\_So atomic function. The final output at the bottom is CI\_iPHB (green) and CI\_oPHB (red). +- Right Path (TC/Label sink process):** This path shows the flow of PHB information from bottom to top. It starts with CI\_iPHB (green) and CI\_oPHB (red) entering the MTDe\_TT\_Sk atomic function. The output is AI\_iPHB (green) and AI\_oPHB (red), which then flow into the MTDe/MT\_A\_Sk atomic function. The output of MTDe/MT\_A\_Sk is CI\_iPHB (green) and CI\_oPHB (red), which then flow into the MT\_TT\_Sk atomic function. The output of MT\_TT\_Sk is AI\_PHB (black), which then flows into the MT/MT\_A\_Sk atomic function. The TC/Label sink process uses received TC to determine iPHB and selects this or AI\_PHB to determine oPHB depending on MI\_QoSDecodingMode. The final output at the top is CI\_iPHB (green) and CI\_oPHB (red). + +Labels for CI\_iPHB, CI\_oPHB, AI\_PHB, AI\_iPHB, and AI\_oPHB are shown at various points in the flow. The diagram also includes a reference code G.8121-Y.1381(13)\_FII-1. + +Figure II.1 – Flow of PHB information through a MEP. The diagram shows two vertical paths of data flow within a dashed box labeled 'MEP'. The left path represents the 'TC/Label source process' and the right path represents the 'TC/Label sink process'. Both paths show the flow of PHB information through various atomic functions (MT/MT\_A, MT\_TT, MTDe/MT\_A, MTDe\_TT) in both Source (So) and Sink (Sk) modes. PHB values are represented by green lines for iPHB and red lines for oPHB. In the source process, the TC/Label source process selects iPHB or oPHB depending on MI\_QoSEncodingMode and also uses this value to determine the TC. In the sink process, the TC/Label sink process uses received TC to determine iPHB and selects this or AI\_PHB to determine oPHB depending on MI\_QoSDecodingMode. The diagram includes labels for CI\_iPHB, CI\_oPHB, AI\_PHB, AI\_iPHB, and AI\_oPHB at various points in the flow. + +Figure II.1 – Flow of PHB information through a MEP + +![Figure II.2: Flow of PHB information through a MIP. The diagram shows two mirrored views of a Multi-Service Interface (MIP) block. On the left, data flows from top to bottom: CI_iPHB (black), CI_oPHB (red), MTDi_TT_Sk (triangle), AI_iPHB/AI_oPHB (rectangle), MTDi/MT_A_Sk (trapezoid), CI_iPHB/CI_oPHB (rectangle), MTDi/MT_A_So (trapezoid), AI_iPHB/AI_oPHB (rectangle), and MTDi_TT_So (triangle). The output at the bottom is CI_iPHB (black) and CI_oPHB (red). On the right, the flow is reversed: CI_iPHB (green), CI_oPHB (red), MTDi_TT_So (triangle), AI_iPHB/AI_oPHB (rectangle), MTDi/MT_A_So (trapezoid), CI_iPHB/CI_oPHB (rectangle), MTDi/MT_A_Sk (trapezoid), AI_iPHB/AI_oPHB (rectangle), and MTDi_TT_Sk (triangle). The output at the bottom is CI_iPHB (green) and CI_oPHB (red). The MIP block is indicated by a dashed box labeled 'MIP'.](1ab8da167ae10f58b4b0b57e0c1283ad_img.jpg) + +Figure II.2: Flow of PHB information through a MIP. The diagram shows two mirrored views of a Multi-Service Interface (MIP) block. On the left, data flows from top to bottom: CI\_iPHB (black), CI\_oPHB (red), MTDi\_TT\_Sk (triangle), AI\_iPHB/AI\_oPHB (rectangle), MTDi/MT\_A\_Sk (trapezoid), CI\_iPHB/CI\_oPHB (rectangle), MTDi/MT\_A\_So (trapezoid), AI\_iPHB/AI\_oPHB (rectangle), and MTDi\_TT\_So (triangle). The output at the bottom is CI\_iPHB (black) and CI\_oPHB (red). On the right, the flow is reversed: CI\_iPHB (green), CI\_oPHB (red), MTDi\_TT\_So (triangle), AI\_iPHB/AI\_oPHB (rectangle), MTDi/MT\_A\_So (trapezoid), CI\_iPHB/CI\_oPHB (rectangle), MTDi/MT\_A\_Sk (trapezoid), AI\_iPHB/AI\_oPHB (rectangle), and MTDi\_TT\_Sk (triangle). The output at the bottom is CI\_iPHB (green) and CI\_oPHB (red). The MIP block is indicated by a dashed box labeled 'MIP'. + +G.8121-Y.1381(13)\_FII-2 + +**Figure II.2 – Flow of PHB information through a MIP** + +By considering a case where the sink side of one MEP is connected to the source side of another MEP, via a MIP, it becomes clear why both the iPHB and oPHB values must be passed through the MIP without modification. This is illustrated in Figure II.3. The same logic would apply if the MTDe\_TT and MTDe/MT\_A atomic functions were used without their associated MT\_TT and MT/MT\_A functions. + +![Figure II.3: Example showing two MEPs and a MIP. The diagram shows three components: 'MEP Sink', 'MIP', and 'MEP Source'. The 'MEP Sink' has an input 'iPHB' (green) and 'oPHB' (red) entering its right side, and a 'TC' (Traffic Class) input at the bottom. The 'MIP' is a central diamond-shaped block. The 'MEP Source' has an output 'iPHB' (green) and 'oPHB' (red) exiting its right side, and a 'TC' (Traffic Class) input at the bottom. Green and red lines connect the 'iPHB' and 'oPHB' inputs/outputs of the MEPs through the 'MIP' block, showing they pass through unchanged.](b0517f9ca66ffb186c33e3877529f507_img.jpg) + +Figure II.3: Example showing two MEPs and a MIP. The diagram shows three components: 'MEP Sink', 'MIP', and 'MEP Source'. The 'MEP Sink' has an input 'iPHB' (green) and 'oPHB' (red) entering its right side, and a 'TC' (Traffic Class) input at the bottom. The 'MIP' is a central diamond-shaped block. The 'MEP Source' has an output 'iPHB' (green) and 'oPHB' (red) exiting its right side, and a 'TC' (Traffic Class) input at the bottom. Green and red lines connect the 'iPHB' and 'oPHB' inputs/outputs of the MEPs through the 'MIP' block, showing they pass through unchanged. + +G.8121-Y.1381(13)\_FII-3 + +**Figure II.3 – Example showing two MEPs and a MIP** + +# Appendix III + +## 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 specification and description language (SDL) diagrams specified in [b-ITU-T Z.100]. The SDL diagrams use the following conventions, as shown in Figure III.1. + +![Figure III.1 – SDL symbols. A grid of ten symbols with their labels: Procedure start (oval), Procedure stop (X), State (oval with vertical line), Input (parallelogram), Label/connector (circle), Decision (diamond), Task (rectangle), Output (parallelogram), Procedure call (double rectangle), Procedure return (circle with X). Oval symbol Diamond symbol X symbol Rectangle symbol Oval with vertical line symbol Parallelogram symbol Parallelogram symbol Double rectangle symbol Circle symbol Circle with X symbol](437a88375397eec8390174b5426e99b0_img.jpg) + +| | | +|-----------------|------------------| +| Procedure start | Decision | +| Procedure stop | Task | +| State | Output | +| Input | Procedure call | +| Label/connector | Procedure return | + +Figure III.1 – SDL symbols. A grid of ten symbols with their labels: Procedure start (oval), Procedure stop (X), State (oval with vertical line), Input (parallelogram), Label/connector (circle), Decision (diamond), Task (rectangle), Output (parallelogram), Procedure call (double rectangle), Procedure return (circle with X). Oval symbol Diamond symbol X symbol Rectangle symbol Oval with vertical line symbol Parallelogram symbol Parallelogram symbol Double rectangle symbol Circle symbol Circle with X symbol + +G.8121.2-Y.1381.2(16)\_FII.1 + +**Figure III.1 – SDL symbols** + +# Bibliography + +- [b-ITU-T G.780] Recommendation ITU-T G.780/Y.1351 (2010), *Terms and definitions for synchronous digital hierarchy (SDH) networks.* +- [b-ITU-T G.8151] Recommendation ITU-T G.8151/Y.1374 (2018), *Management aspects of the MPLS-TP network element.* +- [b-ITU-T Z.100] Recommendation ITU-T Z.100 (2016), *Specification and Description Language- Overview of SDL-2010.* +- [b-IETF RFC 6378] IETF RFC 6378 (2011), *MPLS Transport Profile (MPLS-TP) Linear Protection.* + + + + + +## ITU-T Y-SERIES RECOMMENDATIONS + +## **GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES** + +| | | +|--------------------------------------------------------------------|----------------------| +| GLOBAL INFORMATION INFRASTRUCTURE | | +| General | Y.100–Y.199 | +| Services, applications and middleware | Y.200–Y.299 | +| Network aspects | Y.300–Y.399 | +| Interfaces and protocols | Y.400–Y.499 | +| Numbering, addressing and naming | Y.500–Y.599 | +| Operation, administration and maintenance | Y.600–Y.699 | +| Security | Y.700–Y.799 | +| Performances | Y.800–Y.899 | +| INTERNET PROTOCOL ASPECTS | | +| General | Y.1000–Y.1099 | +| Services and applications | Y.1100–Y.1199 | +| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 | +| Transport | Y.1300–Y.1399 | +| Interworking | Y.1400–Y.1499 | +| Quality of service and network performance | Y.1500–Y.1599 | +| Signalling | Y.1600–Y.1699 | +| Operation, administration and maintenance | Y.1700–Y.1799 | +| Charging | Y.1800–Y.1899 | +| IPTV over NGN | Y.1900–Y.1999 | +| NEXT GENERATION NETWORKS | | +| Frameworks and functional architecture models | Y.2000–Y.2099 | +| Quality of Service and performance | Y.2100–Y.2199 | +| Service aspects: Service capabilities and service architecture | Y.2200–Y.2249 | +| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 | +| Enhancements to NGN | Y.2300–Y.2399 | +| Network management | Y.2400–Y.2499 | +| Network control architectures and protocols | Y.2500–Y.2599 | +| Packet-based Networks | Y.2600–Y.2699 | +| Security | Y.2700–Y.2799 | +| Generalized mobility | Y.2800–Y.2899 | +| Carrier grade open environment | Y.2900–Y.2999 | +| FUTURE NETWORKS | | +| CLOUD COMPUTING | | +| | Y.3000–Y.3499 | +| INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES | | +| General | Y.4000–Y.4049 | +| Definitions and terminologies | Y.4050–Y.4099 | +| Requirements and use cases | Y.4100–Y.4249 | +| Infrastructure, connectivity and networks | Y.4250–Y.4399 | +| Frameworks, architectures and protocols | Y.4400–Y.4549 | +| Services, applications, computation and data processing | Y.4550–Y.4699 | +| Management, control and performance | Y.4700–Y.4799 | +| Identification and security | Y.4800–Y.4899 | +| Evaluation and assessment | Y.4900–Y.4999 | + +For further details, please refer to the list of ITU-T Recommendations. + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9357083934674594a479f84c2fef6a8e238120a1 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c162d030c4a35a98e25ef168616dcb5a5854169acc45bd3b7b0f0ee591297ea +size 42644 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bdf694fbd0fbba25b3cf5f45fa8cebaa8ca5134 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7c5a4a63592b2d9a0e9bac08adbc0ccf6d101e9d7fdc3697b0d21428920e8ef +size 70418 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceecc12aec8829974294bc602d5a3770c1755104 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d30c384f1e8e5898c3313fbe20486056234b0ebe8db02b6f020ccf17b2b96c95 +size 75207 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7424de82afb2e548ee4d95347f87729e82843bd3 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41461f56a125b0a60049ae72d7987975a4cdc11c4e5c269e96d2838d3b710347 +size 61862 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..792c7e24677a027888ee80dea0555929cd557918 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed0c268485b494fa0b34e5e729de727b20a026136b6efede0fbe85013818d153 +size 24833 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f158b28fd8615606e4560fc699893a2285d0d9e5 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8f50f6e73967b019eaff6b612a2991543958e6b71a9452d3cfeafd0812a1ab +size 42368 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27624321e13b60fa0eb4bbbe528127e51969507a --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbe61c98bd64b183813250bd04081403e9692cc5311ef244d366792635fb370c +size 5750 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d90c2551905487d2776f67783aa363dd2abe0baf --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f13477687690af1137411c61bd889ffe4883289212cccc3b4919c6a03b7224 +size 100486 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5abc30874df516ca52d5ec61db9dfd34057cad17 --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d16e79941752d89b1e939e79d40fa30f7e45d92ee21268c6d98a46d6142cb5d +size 16065 diff --git a/marked/G/T-REC-G.8152.1-202101-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ae9c6b7e3016e33ed5392dfd8487afb2283acac --- /dev/null +++ b/marked/G/T-REC-G.8152.1-202101-I_PDF-E/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eea74a259e67d98924ce7e1ba4bf2c0853ebfd1c0c46c88478d3ba10dea6bae6 +size 44804 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5577f70918126f6107ba21d331fe3ab7fb2dea12 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc0f0600aada1a01fb163e982e6af1e5ffd7d68c23a5a6a0f928f9941fdd48ef +size 44523 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7984bf67005b3ffcebf57c4d228e73f9aaa8ea15 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab72504e26c77ed134ece52a05e593d43ffb47286a4710b61ace231f0e244461 +size 21600 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d828c91738324c5c93a331ac1855df1af7f25a0 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/0f79a59f3766fc341ff688a23692c1d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bac51faae138eac1d5c18fcbba15cfbcc929852125c3e2bb062da7693645db3 +size 33590 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f1930bbd89a50a0894d935445360ded9ddbc124 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/2a23751710f7827065d2b99b6df588df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20cc9dbb9da343ce99dc72bb6108dd9e95d62bbf42e0036b8d09d629ae89000c +size 37380 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab2cbdd4af6bc1ea9ffa8cca87f9d455eb147008 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94ee226724314e8b36ac3c73e99f9ed2a4fbb4786e0c7f3f43c1debd5966aa00 +size 8239 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef441153cd4ff6585eac9c7c2abaac9b3f4e7ced --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/3102c32204f998dba666e1e915d5babf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5075ae3bda0c6c715521b067295218bd09421aa499df7193e2344352fd2268dd +size 37417 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffc1c434f310059a32a8f185c520492a80f18f1f --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e767d78c9b4f61e0e4aca27a68d9b7a704dc3bce9a328cfda83fa2e7062bdf26 +size 61755 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98bd45e7415bd28a9790bf4e601e901ca2a90f4 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8b27839d932324811bba5a503961ade73228d95c3e6501083d269376a648723 +size 44317 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa89d87a009c87c50554d23d790b9474dda99d2a --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2aadef5c335de837d8dce2b5f7e4a6293d36fdaf03e1fbe8268711c14622112e +size 81400 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bfcf56461cf2aa3d348ac246af53e91fbc61f6c --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/60e9207be66a64332619bb4b667fe67b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c7320dd72a861d6874c056b6b777ad8208932b842306f56d8f5d53f6e195085 +size 32215 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64392897c6ab0a3593a2ec705b642b5edf316f9a --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1650bef965ada512040bc4bfa921b6305f63a99f2371301bd1b071372021a655 +size 32439 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb95bcb51302cd5735a63bec94b74374f2a30f17 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:648dd4a913d06b58cad86e8fa86975370081c6d50a417984b882098d80cb8678 +size 203477 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5528fb7c6716136a4dea90ce26f3416c90f16ad0 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/71ab4df17511d75261da8d462d643b1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91df435b980320eef0d2c95e198567108ad3212b16035940f5ec0c54c5cd5a19 +size 32241 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/723827e0738d2743c3b3423760a5c48e_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/723827e0738d2743c3b3423760a5c48e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be96415758d21a89775239bad450dd6d5d9ee28c --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/723827e0738d2743c3b3423760a5c48e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d50d18de2d6eaecfbdb90c791144ea24f8d28a8beaff97392f2dfdab79044aa9 +size 35119 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..356631adf03592d36dd39ca15dbe0ae97a15b76f --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1102ec810b4d4e44d330e0b2609f28e1fab42a21ed51aa42a3a1033381f0a5 +size 43131 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d47f6a520c7a52515abaacd5ed6c22eebc5048f8 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/798679874d1c29f8343506a156c79d7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ae49ebb715e55acb52b8e0d49b9c5e0bd46bb8867333bb92f4a7aa37ea3de88 +size 43829 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..135ee6b4a9b63e3cb80249c92497ff6722fa2a77 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/7bed2d7c96d86bf922295a1252da52a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:675165d616974ae74f8f85adb3340c603c4294fc1a3b1f4742b00dcc29873aff +size 32935 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4684e2d7c60c5acba8bd43ca86c0666308f9d44 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/97f61e67792478fb6ce089868e503063_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c1d3c30f9d89f4df08c2cc4f04060245f01300e6274ee81259c5eb1812b8efa +size 42513 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9900ec9f48df2267cd5b8f30160a9879a26b97d --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4809797e964d0408a019134d224bd729969311bda545b307cc565518abf7f5fb +size 42661 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4dd9d4ec5076cf52a4c85c50bd277d571fc4bee --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dcac3016fcf6bd886e6f88379a697fac03c9b81f2a7641b444587d194a30ff1 +size 47800 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7d9f4bb26377ce35dcbcfd5ea88d65ca83edf90 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a01bf6debae99722ff2269361a202f4e2300eef463213709330b832f3bdae78f +size 42029 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa8620edc2d8c49e51ad051ea69f0d6b62383ac5 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/bfb6d182d624680db577069bbc0b2a93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4aea32118d80728f23d3adb7a308eba9d48c0b9fee9541955a338e84a762b31 +size 46692 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7b4fc168ce3004916517bf55e136ef8c44431c5 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e2a4b68822aa4bce4fcdfd15f66d685b50f57a13a93ee06371214e2d53c1d83 +size 35844 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07ff2d40134e760852c889fa66ccb5eb57f8ac4d --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/cc8bec39d25eb0aafb5382c05f0d5deb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c0b7e79946a7b23c8a3348f03389867fb4e0648b95cf85e4a533158abd6c0f4 +size 29722 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37e8fe39c647a36059ca44908a09baf6d9358cf3 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a678f1324df14841a30341e5a2a7b4396c998edae6b7a08345cc5d4f4b9ae13 +size 59431 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fe15ecdc6477ddbccf023f94e275f92a8d40368 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae3a6450a42080a9e6e0b53116032cc12478a123bf84745619f3ea36e73c9835 +size 35086 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af70a7b48bc9292b502d3a07425b8d6203918d9b --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbd3a8bf1e39749c00f1f1dccde6272e49475a27421ddcf6d6671d8265c503e0 +size 52781 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56d51e83085eb1a2ef78e97e8549273254c41e86 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ea753e49b184745ed31944182b33056049c868857f643668a8e0c97181929d4 +size 22750 diff --git a/marked/G/T-REC-G.823-200003-I_PDF-E/fc857414626a8d94d132e12d9afe52a4_img.jpg b/marked/G/T-REC-G.823-200003-I_PDF-E/fc857414626a8d94d132e12d9afe52a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fc9d7abc8c73d1aaa776e5f07cc9f666f536008 --- /dev/null +++ b/marked/G/T-REC-G.823-200003-I_PDF-E/fc857414626a8d94d132e12d9afe52a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67fd89c054208450852306d40660d4d3446d9b7ad7444ed37680a690a33c0811 +size 28535 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2665e63e330e09e33a9fa23b505ec06c34ede19 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/0245dc88c1db93181871e732bc0655dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01fe387a94b4b8ffec245dd89c9562f19fd3e87ab71370db4bdde06dc96c19dd +size 42732 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/02d7901f2a570d0c08f8b2b310ec6826_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/02d7901f2a570d0c08f8b2b310ec6826_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dbcedb3e16a29ee2db04115077ad901aac2b3c8 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/02d7901f2a570d0c08f8b2b310ec6826_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5f2fd745ba5ad5703b4e9577013bd4749c3e9e205e7d6db013d67f777ec427 +size 16848 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5ad2a0aee61a849dc9306872f9d7f3aeb930791 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb06f7e7a4f7b8a480a7fdc3dbb7006bc53f17bf641fbfc313b0c23c6fd95682 +size 42165 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a0fc1629e8b0fcd7dac4545a6759e9eb85860a5 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e07b4b23eb0769df3e89fa45603856a377f1dcf92abdd6eee2bb3421360f6e5 +size 18904 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b757e35a58ad904e904954abd34f1d249e8eadc --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e8e10effcbd132134d438415415d5c6a5984a2b117284e53cd9c17453b1fc6b +size 83286 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3537eff3ad3a8fcd364bb72fd2d2220fca3725ad --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcd1d7f5f96c516e0bbf9fec25824a1da026ce093cdc09fb1f6661950c702bef +size 78459 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb55d606d93a095cbb7c4bff2811d4eb64b3cff4 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ece75d04ef074c725bb3931b96f85979bd55b3906a086bba25dd4caaa5bdd545 +size 47903 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1018d0db7bb02c169f646cb9cc244dc6_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1018d0db7bb02c169f646cb9cc244dc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d666aa3472590042c0ce54eed6140f2d2e5e4db7 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1018d0db7bb02c169f646cb9cc244dc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd42ed91c774e4c2df43340472eda2f9382a0fa969ff716a9edd9368c79adfdb +size 31323 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c57f26c258f55d1945fcda69f639263c2b3b0400 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:979b6d21e49550485b027ff68ad3c96953ea06f1fecd40f4e52b9d5589d8ae62 +size 32647 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4055f85c8faf3d98d90664f36b01e760bb2590b4 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/140bd031d724324269168296afd1e04d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:737c3cc1baa5e050c6b3e6fde23fa214a8755509ccef6b65c483c82100de8f28 +size 59846 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/149826281804ec51b5cca5603c88b23b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/149826281804ec51b5cca5603c88b23b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e26cbca7523e660d3ff081d851dab923c04d0ff --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/149826281804ec51b5cca5603c88b23b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b70832db4d1281838064f74fcfb3d92c5729a70d8da81f5cfc12d331a683fee +size 26027 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bcc4ab67ca968bde9dbe3efad118be188b5ae0f --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e40e5bf3396751fca99c4f6b794a6ee82e60797e6193841eb13fea49b7bc865 +size 99504 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45acd32554c46fcab1993a6575b59904d6fa9adf --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50b4560bc02eaa3074c418561d08ac9b3aca81ec71269dad4fe598aa35136024 +size 53566 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc7127964c7145e84d8bd6a859164b4a406ed5a8 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19afdaf2eca156780d7f422c9dcc4b2af70c24da5bff4a8c3682bb6eb70e244d +size 34259 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a57808bc2e1b13cd210385b85e9eb7b49819f7a --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cfbb0e585e9a77239fb83ecebae9c96d1b79f434806ecd6efcce862412d7c39 +size 37844 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/1d6443fd69c3c131178e7325031ca166_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/1d6443fd69c3c131178e7325031ca166_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b46b5245acddfa5b3bf0213efd6ee16502ebce09 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/1d6443fd69c3c131178e7325031ca166_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4ad918b301ad535ea054931bf7086ae2fd39f6711e8c9d43e8a7804b8008559 +size 50433 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84fa9ec82bf9a76086547842c6599ef189a968a3 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/20727e57890be6da5692a02d13c0a8ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8fce0261b2d43d9438a83e6f2d492b42b00f0e81dc9473b6058094a0b395fbd +size 35736 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/239c9d313ad906eda294af980e34ef48_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/239c9d313ad906eda294af980e34ef48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d21c79e55f71e515970bc4a0680a3d96d90e57e --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/239c9d313ad906eda294af980e34ef48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e23c82a49d51f5bdef5637825a4a9bc5672a524dd1cb2de3982b5f28658841e0 +size 20766 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df53056907e327a14e7100c5bbf3fc336573867b --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/2cca454bbea734b85b2a785da04388f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d55ce91a205d9dc9b17b0b8f8ab38a77202554441dc8a165499efe46d99a4908 +size 59727 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2b26cf6fbfbbebbc2cc349feab2d1ea7f532c6 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:684d653f3d65427ea7b2d10792fde6351891d3c2a85822de318333fec1715228 +size 40331 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ec767635ff4e42797f67e9695788222bdfa32ef --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:056845fc5399ae2d6496151bb52d7abdd57f9888fba1afdf33c68060665c1cfc +size 111616 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76e8ed6ca8106ae36cf4ff95cb1a704d14fb72c9 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/3b6177b1edfdc8c7740f03f346d7838f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7970066e140b4f59a1e1ce5776066a377758da06be555eeb4feb1f73c4415d8 +size 26003 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e85f4449022a08045bae0b7417c42a88f27a9fe --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/3bf1696c3034743b5ab07a0b5e398347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc48c98499baa5bdae48640f682c60c3e3c016cb10d284e47ec09550577fac38 +size 19680 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4523abf3d5e3dc7bbd938bcc05b3390199be1020 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b85f738009175f208c01c089329d4816d405e85e553dc4351aabddfbed479245 +size 25942 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4af3ebd1cb62138b21626b218a2dab22a63a43e --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a6a78b77f48e97e65196849b715fbbe2e58eea15cd95133a00dcbc5068a652e +size 32949 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..398f26f234db03323decb591df8713b933f33359 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e1f911b16ced580bc1f5b9a39135b0db92fb67252679f025c3c66cd38904cc5 +size 75791 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d660bfad2cb1a24b179b4e8c9b2c52f8d22a9fe --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ea9fd66604067eeda0f1d3dc9e1349e8b43ec5dcc0effc1eca9379f934e841d +size 30574 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..792c5bc3c202a7a3362dbafc18df0a15cf7d9536 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a34ebaa967ff09bafa7806aa040da9369775f39914967a46c75549d3b3bcba01 +size 44136 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/605ad256780bc1b6022dfb65a6e24a3b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/605ad256780bc1b6022dfb65a6e24a3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13316e8dad8eac00052be2775dda18e6da296a8a --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/605ad256780bc1b6022dfb65a6e24a3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bc2c0d747b67e4e78aa026d6735d5eb72964ea5394894cdfc61ff1217916228 +size 16203 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/62ee64afa2d368d732de66628cf2c841_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/62ee64afa2d368d732de66628cf2c841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07a861ab0e5d9f5792acd009bac1d8742fecda7c --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/62ee64afa2d368d732de66628cf2c841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f0a12176343e0eac4b9f349ba3b5031f1f0512ae2aa93ecde67690f7458d888 +size 58305 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..585cecaa12a67af997f6f0646477adcdc41ca1d9 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09c3aaf93bc364577af6a2d126562ca6275a2a2ecea89efe267e341c87d86273 +size 35559 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12940edc87014aca922c2b38d81be1d0f3165f7b --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/65678100712a6817696109be76a51f0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e6292b27956de313483a9b836c7e6bdae7535d6b59f21e6d7199e1343e33ed6 +size 57614 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5db560aa0a2930aba973a15657970a86cd7f7578 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/6d2057d7e401741861ca63545a5d7d3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a40088d8b7ae7fab7aea1e5d9a058674884de109e3e91cd080c829c6d6bdcfe9 +size 27536 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f4cd3d5915d063bcd9df2695fcad74abb378025 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/6ee57fd30c7e609827c2a11d0983eeba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e83bc6a61010f4c30513d5006ed57d989387db0b05f69d7b807f43984f3f227 +size 39698 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8c08b8e1d4612d46c9faa9566bf79e5f94036b6 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/6f46eccb86e008f8bc7af8ea3ab806a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8474837378627b7d66b06aef8fc7e84d09d1f593562fa946a055b1765c91f31d +size 98814 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93a51b06a595f1742cb47e0db2346a1989a5bd9b --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b51d32dda3a0b8537fd8320e6dd38fdf09c1df40c4c04315f285fbf592ac3040 +size 41049 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4549f8bd5153d1c7a18b82020820529f62097121 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b51b93fcd95eb684cb62cc5b62fc327191f59e7111b65533aaba25514eb6f9c0 +size 48082 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/7fd711d47481adc15851b6f81405a26c_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/7fd711d47481adc15851b6f81405a26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa0ada5caabf362c87c270f7d138bda15f3b4036 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/7fd711d47481adc15851b6f81405a26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c53d4bcbbf98b050d608c497fa6fac2213e4d30a46efad2f27c93d4bcf82a77 +size 102053 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74b4410dfc3c6a5796f2e510db604dc87627fc56 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51da1489d8f6367c3ac3052d6703661a635cf843ed437de06df9427232db7499 +size 97606 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..873ff1158b6319cf4bef7dde660a8f766c5f473e --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff41a27f13ed0c634569705ea5d399a868478374f523346fc4ff6f96be6ef866 +size 108436 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..826f5d7312a612c8acd1e9740b57c73e6b999463 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3283e3b64fc89374ac2790544f4f40ac0c7ceb5834615d61771928088fe6fc0 +size 15680 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d5a2ee043f651155a7c91614d6665c9df6c997d --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:521897ce9a7af200aa7f768f250409d518022018226cdea9fc393fc255f3bffc +size 40726 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b0f2cfc2934be4bba842724828ed0f038fed359 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:665a58015f8d696229b3ff0e48945e8490679e8aa6a6db8ad3a6844ab27164fb +size 29006 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3183e5f1ced27c8473574e077bc21f6258d1d222 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af4d9271a99ec92b7cce182aea8c8adfc4b7266cb69052b0035a3a3ee78b3507 +size 34132 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9c8070d46f1d2480a875239e792f1ef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1213c1366072ad3c7992de5d9e9adb61c1c4894 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9c8070d46f1d2480a875239e792f1ef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c58e47fd1d62f20033ec933b3517f3fe7ffadf9260028c243e171c0e8476c787 +size 34938 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e55ecc691e94aff77a9b0765499750253d102d8 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac43a2ead2d6846275a21c2813a34d3e6da45618382ffec4b63155042dabb87 +size 14590 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a27c16e7a9db45d25fae7b4868ae4b4bfddb0912 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/9faa3512b2ff7973283e76192e91bf65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd781b90e276796e4d7e29f241c59a3a2791a6ccc027f960641a17588a363958 +size 34975 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f052057d032b70032d6d88a50c02d578ed3f452f --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f1ba641a50c422ae0449b99df73a014b1950da752cefaeb8fece3f0def3a6bf +size 98340 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0f047ca18833bef3cb581fe94c777acc9f454d3 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2767175636b6734606857e0925b8f8a61166e0afd0cc034fa775c5fabbb6f27 +size 26901 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/a312ce7823f1d58ab6c3e86e6a7e9059_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/a312ce7823f1d58ab6c3e86e6a7e9059_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fcb5fdbac2ae72af9e831ada2194e24f45bbeaf --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/a312ce7823f1d58ab6c3e86e6a7e9059_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76c73e5e173cd74cb0cc80641fee86a1cd5ec2d447cc89e864e67ae253ae007b +size 28693 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d58c49d406e3efb9d1797a2861e769fe4fa29b81 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/a72d02d4e6305689a79b46d36739cd51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4b243021002e87c2efca0c46b44b2bd8ec828a93aafdfbfd1c7ecdb067d9f2a +size 70011 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/a7721892ae499a78173ff3dfdc4e65a9_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/a7721892ae499a78173ff3dfdc4e65a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..581e6f79357107075bd3376b753fd6f7380d9656 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/a7721892ae499a78173ff3dfdc4e65a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dc4e6ab1205ad41ee927f1640070dc58b68c20ff23e199af8bc596a36f2be57 +size 31970 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97b1c52c1132370c4d6e31612ddd576db0238b17 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a0699f8d0eb4217011742dbb6d12430555cf1595637b4ec9fd9628fa500ea4a +size 37281 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55c97090130b40412b1acb91bca8d73a216c0446 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99dd4b09341e162e87439acd7c28f52e78e380c7a9ae04153567302caa74f293 +size 48358 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ed588d1056e333e7879c30ec9b9ba780b2553bd --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6671b0b2e954420a6c46c8e8ffd2c86c93105d59988d6f9d306792580e87a157 +size 30710 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de41ac7363f4f64f443a6faa595639a66dbe16a9 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5a1719156ad9017e654d058aa422c00fc15678f422a7947f446fd327f1be771 +size 65968 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04048730a4f1fadeb799f008082b9e4f08ef1d26 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55ed9057ebe6a295d84828c6cc97e17416822b8af1bdba7edef8390c8c80369e +size 64332 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1951ddea95b782bab570c6d82b903b4b249d38c7 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b00dfd42c084596c44cd93b8217127f38e34660df028590917239e66ad727bb3 +size 58197 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e8aaa9069f18c33905a32ae29fe03530bae6909 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67bc98df8a75ddbdb7cd63212cd63451984ae3a534186e79a29fea18a67c668d +size 73884 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e567a76b44614bfea9ea7862bbab72cee22ede2 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d27444af793ee7aee1b2c51c91a98939ee1ea0dfbaf294b8ef5dc16f4d7d2472 +size 74677 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1725e86765b01d011a2fdefa6bc7092a1d99bf5 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a08be7bb7f4c241932a96ea25e91ca077d416334b1cf03f54dd944efd144ca45 +size 35641 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/c7753d4f59c41563733ca6a3d256db6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d4ea4e44b611cdbb77e4663f1e48fec157f354f --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bdb674dd2194b63017eff002cae96df0abde97004fc299c9745b42f0894bf35 +size 109824 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51c67720774c0848d280d610a6ffdbdca7dc4993 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/cc72b4769f15fe33763025416c1e274d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4146626505c2f410946a6cb20be2be66de8634f5467b31cb5499e0ab761d24fc +size 24102 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/cc893412ff9ca2426705e878c75548ba_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/cc893412ff9ca2426705e878c75548ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53ee9d0033942c5db980b20d5c98ff6cf7681b60 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/cc893412ff9ca2426705e878c75548ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b732ca6493b43eb4a7d3f90bbc79f73078be0ef3b8c4d05768e83c8b8dc18a16 +size 28591 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/cdba53bb2fb4d459f37515ee7fab3418_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/cdba53bb2fb4d459f37515ee7fab3418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76a6e612ae7e19b0fee0dc38befbf161c989bc4e --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/cdba53bb2fb4d459f37515ee7fab3418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae3337e479db7940d8be440f1a14f676dc72b5d23d6657bc4798d728311b2607 +size 34328 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9eaf2d68f1a49702eabe626cd74607f6555873d --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e74e3690578a53932b998146fc9920b1f5468cdc8efea9b8d99eef8d2b4692ca +size 57637 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae9d062ee0b5da91d797291bcd8b65b3c9b14d58 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:478751c6f6641909b1e39d35bdcc9b3bb7337dd4677e22919b80bc98fdf245b2 +size 49495 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8646e12ae2b7419933459843e9888249b2cadf13 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/d7996c295c6d5c251be4bce3dea03f2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5f49c8a652343cdbf2fd967f10ca445c069f0d2caa75cc9b1a5c84aae9b4a09 +size 68956 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/da6000b1371b5528262d4f9cb2f2707c_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/da6000b1371b5528262d4f9cb2f2707c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51b3d3909a2d7aa948e8915f339160983a58c576 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/da6000b1371b5528262d4f9cb2f2707c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1896aa1ca89273e5cb4035d0a199684b2c83ec48699a78ddae81fd13f515a23e +size 43172 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c538468524c3bfbbbaf1e40d7daf13df4bc88a --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54385065a356069487bb275f5f4ec648ed06ee6bb6fed37ce6f087c6a8391b22 +size 27002 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/e02ed04c67bf93a49b8cc3a427e66bca_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/e02ed04c67bf93a49b8cc3a427e66bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95f32c6e2d4f50c175296cbc408052ab1b842ddf --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/e02ed04c67bf93a49b8cc3a427e66bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d126e8960ff7df352a41609d9f80e1ef8d10bdb2f461346d86546cdaf02a483 +size 23938 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d1435fb884952335f3c81a991102bfc5580446b --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:353d02b94195a92264dec91c9d6afe90f19601fcd43e6ffdadcc7b75b3259085 +size 34072 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd63218437d7f5f28e4385e4d2a2cf990edcc3d8 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf75f708f2d7d11458f7f5ca07fddfe65714e61a247817fad5a60a7da39238a7 +size 61960 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0958ac85d735a46ab737a5c51061e11549492ad7 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7767ef600b8818656131f89580fc22dc6bbc5a01268a86f9a8212d52470637b +size 17597 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ffb7e542e7b552047dc12953f13f6dab8333ae3 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50efabe527fd1003bf23220a51241d0bd0f391461c98ae3de4323d48a6bb2af2 +size 35988 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ac5ecf9826ee5543671a238266b85f39afb53e --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:429b58c3e0578a1994e8e10824ba1dd1f861e87981441ebe0003022217a56e24 +size 44393 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95d6fd6e463ca148672fcd84ec808e49bd1ba727 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/f8163a5402ad1756cf135c42bc22c5f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78c229fbcc9a3930cc9e1780491bf80bdc877adaf0ce4c76bab1f92f1767380f +size 21078 diff --git a/marked/G/T-REC-G.8261-201908-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/G/T-REC-G.8261-201908-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ea9940215773899f4604778371fa66ce6f46eb7 --- /dev/null +++ b/marked/G/T-REC-G.8261-201908-I_PDF-E/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b29651293a39e5f5839a8b61f7237920346e1632d3b189f01a3f124b49c048 +size 24109 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f55172fc81f7fe5a0d0fd750eb2a2c15ad07b7 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91804c50555b80274036459047de9983979f6dd5daa9db99e2964015ff4b207c +size 13686 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f4ee740318a02ab367c3379812eeb3769e9097d --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92bb5646b71496a5f4f10166b856401e48395063f3605775b3a1d2df6f4b269a +size 41328 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0cd6e945f6a84723037f93592fb5e3fca746bf5 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2c0c687f342a0225aae3c872e9f65c98f5b6cf9f122bedaae1756d46c2e910a +size 48834 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/1acc7c1338d89d86a162eb4ebedae856_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/1acc7c1338d89d86a162eb4ebedae856_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29b92e1fd5c5c6317de3101f05029cce389f8a50 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/1acc7c1338d89d86a162eb4ebedae856_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24cafc0cf5cd7a66622e16b7a7c79b8aca2662799e38a51fbdac629896bf74ff +size 17698 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..021505ebd8b043cf2fcd6a540e3e2ec5dc3bbedc --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/24b549c0c4b79c515b244625cf4f4978_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33c5bc10c36f2f50a0e2f5713d2bb01d9259d7a591511a72c3db66b6e8b3b425 +size 54179 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e70bd7d8c251362dc0e651c44544be2c14cd79e2 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a9f4388b436bac0cd967870121b8588af16cfc5af984f6d64c796578b31ec83 +size 25709 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b1df77254d6398c2700e404c20b2444e7e3168b --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f96ef0e5af9441a9a44a7af3df53d35c49f789f064b3e55b445e37076145f6a5 +size 69856 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..864cf3e3bfc3745464ff5ff464b3aac47d9c205f --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99b38454b149d33c46a9793a7fec081cefb10f91cac2fe9925972979936bfb4 +size 41469 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c56c4938fb8d0fb3ae9f38b966e92a3d48ec200 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:285510ee26750356a58c8423927eccb47a18d88680a7dbd03419cadb468346d6 +size 49385 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53016b261e0aa02e9b841fec99c700fbaf1a29fb --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df2f5a5cbf74aa8df12c86fc8d2c97bdeab4bf33c444f5e98eeb20f205e78e42 +size 30685 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c885cbc7a45c98e6ea782aa59594337f255dc1f --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f64c504a7c8c5319a9f1465d72becbfe441ffa26038b2394c191379557990a27 +size 33592 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e69269ae1b185cdff0a6595787a4f204bc912c6a --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24802606a3fd7bbc18066f51133698f75b1bdeafa9f047cace3e55766dda9c8c +size 53891 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ed1419464092e380c4678e2b8fe57b8600aed7f --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b8f7df5fab2069d369aed64f33b8be874e01511f84a06b6fb4c84a01765d4de +size 20703 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b667df4b443b8e246cba9bc3e29d9e455e9167e --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84852a732eecd37aac19374a66e6ec7c4a8920f4a96572910b17fcc71be28956 +size 40638 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82281a000c5704d1f738c5d19dd8746b85ab0b46 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5f5780bffde24accc14a47f6cce40c19c2a52904d9c483acf930865012a60a7 +size 57337 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd259162c59c35e94e6dad3fe562b9b83f56d78f --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/7848a2560bb726462c09c09bf727d81d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f5e20d2a5c0382e15f8171d9787af5d0fa86ccf31bf7a64b3fb46f25ddf47a4 +size 60324 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb7af3ec2033d3ebd934959cb4e4c8b6567c1d1b --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2939938395072e3a444e198b4f521ddf083f6208c5a16411d1e18299e0b2cd58 +size 41315 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..908a22c54c85e97ccecba3db7825a2def577bafa --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cba09cc72665ce230378a900dab8104e59762a05fa4f90409c2837e62a8b348e +size 26193 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2626860e27c7686f9abc2e95e365277682fb8cf7 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/a01a138884c0b7c6e4c5a0a8cd5a41ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1724f9a9e7bc9f5e77018bd66732c7a98f7c6b9ed9ebc1f88362dc629657f8ac +size 20980 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8854fab001b68d1be2487ddaf3456dcdfebe4460 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba167978f5f4f3eb027fba880a824e7adbf5db93860b0b8447f0e038957cb675 +size 46036 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6d90799cb44ce8e334cd24fc46d33ad24986b6f --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41e7d0a24677e3f71a7bbb7d5d54da9fbc089e525665b0dd06f4f9532a65518b +size 45286 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b9298d721e02e644beb6ef7542a4047bef3fc0c --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e8b2013d2f000e3d538388a075ebf9c3f2069d939d646aaea579bdcaee01d2f +size 19302 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..147a411df92ab0dc06d66c8890d5315abea5efe0 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bbee4e45f4f45c480774e4a93ffbf35351fcc5f0c391b7c40f50d3592a3b921 +size 55288 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/d3294dc879b451b369c0b06f42e9b39f_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.8273-202306-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b2472ecf9356be9e3c7384a1f923c7a0764d7ad --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c45a4f3ea66c36202c9b5e7aa605c3516e7bebbf1ede175e6179cfc8a90ae8f +size 24926 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d932dc4bea010e34f564cbee02f5cfa8a7beac61 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6f1cf03868c5eab7ecbeaca12f45370cab917e01139ea7ff22ac09c856ca8a1 +size 32845 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a82df4602dad9b8ad8af2e6526c13d78a8d1898 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ec03804b9b587e3005cbde02fa4d2b9c435a5e10911a6fc1ddc7b91e577033d +size 38776 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1a1820cc4c01c9d019037be82ddfb5982342cba --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/dc23d430e878eb71b8cd589984113940_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a9b069bcbfd62ddf4c9d8085657566c54477d6ef5cb68b9dd31e18719727fa +size 15455 diff --git a/marked/G/T-REC-G.8273-202306-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.8273-202306-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff59534ec3b21772aae3a01fa7f7f7552eb433c4 --- /dev/null +++ b/marked/G/T-REC-G.8273-202306-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1526e7802c689a873f799e788c5094bea3b9316338a643423053aa65a7682a0b +size 24857 diff --git a/marked/G/T-REC-G.8321-202211-I_PDF-E/raw.md b/marked/G/T-REC-G.8321-202211-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2e601e06ff7ae46167a4211f8a935c5952d637da --- /dev/null +++ b/marked/G/T-REC-G.8321-202211-I_PDF-E/raw.md @@ -0,0 +1,2154 @@ + + +# Recommendation**ITU-T G.831 (11/2022)** + +SERIES G: Transmission systems and media, digital systems and networks + +Packet over Transport aspects – Mobile network transport aspects + +# --- **Characteristics of metro transport network equipment functional blocks** + +![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.8321 + +# Characteristics of metro transport network equipment functional blocks + +## Summary + +Recommendation ITU-T G.8321 specifies both the components and methodology that should be used in order to specify the metro transport network (MTN) functionality of network elements; it does not specify individual MTN equipment. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.8321 | 2022-11-13 | 15 | 11.1002/1000/15120 | + +## Keywords + +Equipment functional blocks, metro transport network, 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 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 2023 + +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 ..... | 7 | +| 6 Supervision ..... | 7 | +| 6.1 Defects..... | 8 | +| 6.2 Consequent actions ..... | 12 | +| 6.3 Defect correlations..... | 12 | +| 6.4 Performance filters ..... | 12 | +| 7 Information flow across reference points ..... | 12 | +| 8 MTN processes ..... | 12 | +| 8.1 Processes for MTN Path layer ..... | 12 | +| 8.2 Processes for MTN Section layer ..... | 14 | +| 9 MTN path layer functions..... | 17 | +| 9.1 Connection functions..... | 17 | +| 9.2 Termination functions ..... | 19 | +| 9.3 Adaptation functions ..... | 30 | +| 9.4 Sublayer functions ..... | 34 | +| 10 MTN Section layer functions..... | 42 | +| 10.1 Connection functions..... | 42 | +| 10.2 Termination functions ..... | 42 | +| 10.3 Adaptation functions ..... | 46 | +| 11 Media adaptation functions..... | 53 | +| 11.1 M-AI to MTNS y adaptation function (M-AI/MTNS_A, y = 0,1,2,4)..... | 53 | +| Appendix I – Example state machine of MTN Path OAM Basic block alignment ..... | 61 | +| Appendix II – BIP calculation under missing Basic block ..... | 62 | + +# Introduction + +This Recommendation forms part of a suite of Recommendations covering the full functionality of network equipment and follows the principles defined in [ITU-T G.806]. + +This Recommendation specifies a library of basic building blocks and a set of rules by which they may be combined to describe equipment used in a metro transport network. The library comprises the functional building blocks needed to specify completely the generic functional structure of the metro transport network. In order to be compliant with this Recommendation, the MTN functionality of any equipment which processes at least one of the MTN layers needs to be describable as an interconnection of a subset of the functional blocks contained within this Recommendation. The interconnections of these blocks should obey the combination rules given. + +The specification method is based on the functional decomposition of the equipment into atomic and compound functions. The equipment is then described by its equipment functional specification (EFS) which lists the constituent atomic and compound functions, their interconnection and any overall performance objectives (e.g., transfer delay, availability, etc.). + +# Characteristics of metro transport network equipment functional blocks + +# 1 Scope + +This Recommendation defines the functional requirements of metro transport network (MTN) functionality within equipment. + +This Recommendation uses the methodology defined in [ITU-T G.806], in general for transport network equipment, and is based on the architecture of MTN defined in [ITU-T G.8310] and the interfaces for metro transport networks defined in [ITU-T G.8312]. The description of the functional blocks will be generic and no particular physical partitioning of functions will be implied. The input/output information flows associated with the functional blocks serve for defining the functions of the blocks and are conceptual, not physical. + +The functionality that will be defined in this Recommendation can be applied at user-to-network interfaces (UNIs) and network node interfaces (NNIs) of the metro transport network. Additionally, the overhead processing functionality necessary for operations and management of the metro transport network will also be defined. + +Not every functional block defined in this Recommendation is required for every application. Different subsets of functional blocks from this Recommendation and similar Recommendations 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). + +# 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.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.7712] Recommendation ITU-T G.7712/Y.1703 (2019), *Architecture and specification of data communication network*. +- [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.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.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 for metro transport networks*. +- [IEEE 802.3] IEEE 802.3-2022, *IEEE Standard for Ethernet*. + +# 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.3] +- 3.1.5 **access point (AP)** [ITU-T G.805] +- 3.1.6 **adaptation function (A)** [ITU-T G.806] +- 3.1.7 **adapted information (AI)** [ITU-T G.806] +- 3.1.8 **characteristic information (CI)** [ITU-T G.806] +- 3.1.9 **connection function (C)** [ITU-T G.806] +- 3.1.10 **connection point (CP)** [ITU-T G.806] +- 3.1.11 **defect** [ITU-T G.806] +- 3.1.12 **fault cause** [ITU-T G.806] +- 3.1.13 **FlexE** [ITU-T G.8312] +- 3.1.14 **FlexE group** [ITU-T G.8023] +- 3.1.15 **FlexE instance** [ITU-T G.8312] +- 3.1.16 **function** [ITU-T G.806] +- 3.1.17 **flow point** [ITU-T G.809] +- 3.1.18 **MAC frame** [IEEE 802.3] +- 3.1.19 **management information (MI)** [ITU-T G.806] +- 3.1.20 **management point (MP)** [ITU-T G.806] +- 3.1.21 **ordered set** [IEEE 802.3] +- 3.1.22 **path** [ITU-T G.806] +- 3.1.23 **physical coding sublayer (PCS)** [IEEE 802.3] + +- 3.1.24 **physical layer entity (PHY)** [IEEE 802.3] +- 3.1.25 **process** [ITU-T G.806] +- 3.1.26 **reconciliation sublayer** [IEEE 802.3] +- 3.1.27 **remote information (RI)** [ITU-T G.806] +- 3.1.28 **remote point (RP)** [ITU-T G.806] +- 3.1.29 **section** [ITU-T G.806] +- 3.1.30 **server signal degrade (SSD)** [ITU-T G.806] +- 3.1.31 **server signal fail (SSF)** [ITU-T G.806] +- 3.1.32 **termination connection point (TCP)** [ITU-T G.806] +- 3.1.33 **termination flow point** [ITU-T G.809] +- 3.1.34 **trail signal degrade (TSD)** [ITU-T G.806] +- 3.1.35 **trail signal fail (TSF)** [ITU-T G.806] +- 3.1.36 **trail termination function (TT)** [ITU-T G.806] + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 B1 block:** MTNP OAM block carrying a basic message and preceding the APS message opportunity, with SoM bit set to 1 and EoM bit set to 0 as defined in clause 9.3.1.1 of [ITU-T G.8312]. + +**3.2.2 B2 block:** MTNP OAM block carrying a Basic message and preceding the Low Priority message opportunity, with SoM bit set to 0 and EoM bit set to 1 as defined in clause 9.3.1.1 of [ITU-T G.8312]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------------|----------------------------------------| +| 1DM | one-way Delay Measurement | +| 2DMM | two-way Delay Measurement | +| 2DMR | two-way Delay Measurement Response | +| A | Adaptation function | +| AcCA | Accepted Calendar switch Acknowledge | +| AcCC | Accepted Calendar Configuration in use | +| AcCCA | Accepted Client Calendar A | +| AcCCB | Accepted Client Calendar B | +| AcCR | Accepted Calendar switch Request | +| AcFlexEMAP | Accepted FlexE instance Map | +| AcGID | Accepted Group Identification | +| AcIID | Accepted Instance Identification | +| AcPT | Accepted Payload Type | +| AcTI | Accepted Trail trace Identifier | +| AI | Adapted Information | + +| | | +|--------|-------------------------------------------------------------| +| AIS | Alarm Indication Signal | +| AP | Access Point | +| APS | Automatic Protection Switching | +| BIP | Bit-Interleaved Parity | +| BIPV | Bit-Interleaved Parity Violation | +| C | Connection function | +| C | Calendar configuration in use | +| CA | Calendar switch Acknowledge | +| CCA | Client Calendar A | +| CCB | Client Calendar B | +| CCM | Client Calendar Mismatch | +| CI | Characteristic Information | +| CK | Clock | +| COMMS | Communications channel | +| CP | Connection Point | +| CR | Calendar switch Request | +| CRC | Cyclic Redundancy Check | +| CS | Client Signal | +| CV | Connectivity Verification | +| D | Data | +| DAPI | Destination Access Point Identifier | +| DE | Drop Eligibility | +| DEG | Degraded | +| DEGM | Degraded defect consecutive one-second Monitoring intervals | +| DEGThr | Degraded defect one-second errored block count Threshold | +| DM | Delay Measurement | +| DS | Defect Second | +| EBC | Errored Block Count | +| ECC | Embedded Communication Channel | +| EFS | Equipment Functional Specification | +| EMF | Equipment Management Function | +| EN | Enabled | +| EoM | End of Message | +| ETH | Ethernet MAC layer | +| ETHF | Ethernet Flow | +| ETHTF | Ethernet Termination Flow | +| ExCC | Expected Calendar Configuration in use | + +| | | +|------------|----------------------------------------------| +| ExCCA | Expected Client Calendar A | +| ExCCB | Expected Client Calendar B | +| ExDAPI | Expected Destination Access Point Identifier | +| ExFlexEMAP | Expected FlexE instance Map | +| ExGID | Expected GID | +| ExSAPI | Expected SAPI | +| ExtCMD | External Command | +| F | Far-end | +| F_B | Far-end Block | +| F_DS | Far-end Defect Second | +| F_EBC | Far-end Errored Block Count | +| FCS | Frame Check Sequence | +| FD | Frame Delay | +| FlexE | Flex Ethernet | +| FMM | FlexE instance Map Mismatch | +| FOP | Failure Of Protocol | +| FOP-NR | Failure Of Protocol No Responce | +| FOP-PM | Failure Of Protocol Provisioning Mismatch | +| FOP-TO | Failure Of Protocol Time Out | +| FS | Frame Start | +| GID | Group Identification | +| GIDM | Group Identification Mismatch | +| HoTime | Hold-off Time | +| IBA | In-Basic-block-Alignment | +| IF | In-Frame | +| IID | Instance Identification | +| IL | In-Lock | +| ILA | In-multiLane-Alignment | +| IM | In-Multiframe | +| IPG | Inter-Packet Gap | +| LF | Local Fault | +| LLDP | Link Layer Discovery Protocol | +| LOB | Loss Of Basic message | +| LOCS | Loss Of CS message | +| LOCV | Loss Of CV message | +| LOF | Loss Of FlexE overhead Frame | +| LOL | Loss Of Lane alignment | + +| | | +|----------|---------------------------------------------| +| LOM | Loss of FlexE overhead Multi-frame | +| M-AI | Modulator Adapted Information | +| MCC | Management Communication Channel | +| MFS | Multi-Frame Start | +| MI | Management Information | +| MP | Management Point | +| MTN | Metro Transport Network | +| MTNP | MTN Path | +| MTNS | MTN Section | +| N | Near-end | +| N_B | Near-end Block | +| N_DS | Near-end Defect Second | +| N_EBC | Near-end Errored Block Count | +| NNI | Network Node Interface | +| NR | No Response | +| OAM | Operations, Administration, and Maintenance | +| OCI | Open Connection Indication | +| OH | Overhead | +| OLA | Out-of-multilane-Alignment | +| OMF | Overhead Multi-frame Indicator | +| OMFS | Overhead Multi-Frame Start | +| OoBA | Out-of-Basic-block-Alignment | +| OOF | Out-Of-Frame | +| OOL | Out-Of-lock | +| OOM | Out-Of-Multiframe | +| OperType | Operation Type | +| PCS | Physical Coding Sublayer | +| PHY | Physical layer entity | +| PI | replication Information | +| PLM | Payload Mismatch | +| PMA | Physical Medium Attachment | +| PMD | Physical Medium Dependent | +| PM | Provisioning Mismatch | +| PP | replication Point | +| ProtType | Protection Type | +| PT | Payload type | +| RDI | Remote Defect Indication | + +| | | +|-----------|-------------------------------------------------------------| +| REI | Remote Error Indication | +| RES | Reserved | +| RI | Remote Information | +| RP | Remote Point | +| RPF | Remote PHY Fault | +| SAPI | Source Access Point Identifier | +| SD | Signal Degrade | +| SoM | Start of Message | +| SSD | Server Signal Degrade | +| SSF | Server Signal Fail | +| TCP | Termination Connection Point | +| TI | Timing Information | +| TIM | Trail trace Identifier Mismatch | +| TIMActDis | Trail trace Identifier Mismatch consequent Actions Disabled | +| TIMDetMo | Trail trace Identifier Mismatch Detection Mode | +| TO | Time Out | +| TP | Timing Point | +| TSF | Trail Signal Fail | +| TT | Trail Termination function | +| TTI | Trail Trace Identifier | +| WTR | Wait-To-Restore | + +# 5 Conventions + +For the basic methodology to describe transport network functionality of network elements, refer to clause 5 of [ITU-T G.806]. + +The convention MI\_[IEEE 802.3] is used to indicate the MI\_ input/output signals required to map the management attributes, defined in clause 30 of [IEEE 802.3], for the [IEEE 802.3] processes supported by an adaptation function. Their detailed definition is intentionally left outside the scope of this Recommendation. + +The label [IEEE 802.3] processes is used in multiple process diagrams to refer to processes performed by an adaptation function that are defined in [IEEE 802.3]. The processes referenced may encompass the entire 802.3 PHY, or only some of the sublayers of the PHY, depending on the nature of the specific adaptation function. The text that accompanies the process diagrams clarifies which portions of the PHY are being referenced. + +# 6 Supervision + +The generic supervision functions are defined in clause 6 of [ITU-T G.806]. Specific supervision functions for the MTN are defined in this clause. + +## 6.1 Defects + +### 6.1.1 Continuity supervision + +#### 6.1.1.1 Open connection indication defect (dOCI) + +Open connection indication defect (dOCI) is monitored at the MTNP layer and indicates that an output connection point in an upstream connection function is not connected to an input connection point, and therefore there is no MTNP network connection. + +For dOCI detection, the defect activation threshold is N and the defect clearing threshold is M. If more than N /E/ blocks are received within an interval I of 66B blocks, dOCI is declared; If less than M /E/ blocks are received within an interval I of 66B blocks, dOCI is cleared. N shall be 6144, M shall be 128 and I shall be 8192. + +dOCI shall be set to false during CI\_SSF. + +### 6.1.2 Connectivity supervision + +#### 6.1.2.1 Trail trace identifier mismatch defect (dTIM) + +The TTI mismatch process reports the trail trace identifier mismatch defect (dTIM). The TTI consists of SAPI and DAPI fields. The received and expected values of SAPI, DAPI, or both are compared based on the setting of MI\_TIMDetMo. The specific fields compared are determined by MI\_TIMDetMo. When the value of MI\_TIMDetMo is set to OFF, there is no TIM detection. + +dTIM shall be declared if the comparison of AcTI is inconsistent with the expected SAPI/DAPI values set via the MP (MI\_ExSAPI/DAPI). + +dTIM shall be cleared if the comparison of AcTI is equal to the expected SAPI/DAPI values set via the MP (MI\_ExSAPI/DAPI). + +dTIM shall be set to false during CI\_SSF. + +For TTI acceptance process (AcTI), see clause 8.1.5. + +#### 6.1.2.2 Group ID Mismatch (dGIDM) + +As described in clause 9.2.2 of [ITU-T G.8312], the MTNS is based on a FlexE Group. To differentiate between multiple FlexE Groups on a node, each Group has an ID. The Group ID Mismatch defect indicates that one or more members of the group has an incorrect ID. + +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. + +For GID acceptance process (AcGID), see clause 8.2.1.1. + +#### 6.1.2.3 MTNS FlexE instance Map Mismatch (dFMM) + +MTNS FlexE instance Map mismatch defect of a group of m PHYs carrying p FlexE instances is based on the comparison of the p AcFlexEMAP values, the p AcIID values and the expected FlexE Map (ExFlexEMAP). + +dFMM shall be cleared if + +- the AcFlexEMAP value of each instance matches the value of ExFlexEMAP, +- each value of AcIID has the corresponding bit set in ExFlexEMAP, +- every AcIID value is unique. + +Otherwise, dFMM shall be declared. + +dFMM shall be detected within 100 ms of changes to the AcFlexEMAP[1..p] or AcIID[1..p] values. + +For IID acceptance process (AcIID), see clause 8.2.1.2. + +For MTNS FlexE instance Map acceptance process (AcFlexEMAP), see clause 8.2.1.3 (in case of 100G FlexE instances) or clause 8.2.1.4 (in case of 50G FlexE instances). + +#### **6.1.2.4 Loss of CV message defect (dLOCV)** + +Loss of CV message defect (dLOCV) is monitored at the MTNP layer. + +dLOCV shall be declared if no CV message has been accepted within N (N is equal to 3) consecutive low priority opportunity patterns specified in Table 8-3 of [ITU-T G.8312]. + +dLOCV shall be cleared if the CV message is accepted. + +For the CV message acceptance process, see clause 8.1.4. + +### **6.1.3 Signal quality supervision** + +#### **6.1.3.1 Degraded signal defect (dDEG)** + +The algorithm for the MTNP dDEG detection is defined in clause 6.2.3.1.2 of [ITU-T G.806]. The "block" in ITU-T G.806 is referring to the nominal $n \times 32K$ 66B blocks that compose a monitoring interval. + +### **6.1.4 Payload type supervision** + +#### **6.1.4.1 Payload mismatch defect (dPLM)** + +dPLM shall be declared if the accepted payload type (AcPT) is not equal to the expected payload type (ExPT) 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. + +For the payload type acceptance process, see clause 8.1.6. + +#### **6.1.4.2 Loss of CS message defect (dLOCS)** + +Loss of CS message defect (dLOCS) is monitored at the MTNP layer. + +dLOCS shall be declared if no CS message has been accepted within N (N is equal to 3) consecutive low priority opportunity patterns specified in Table 8-3 of [ITU-T G.8312]. + +dLOCS shall be cleared if the CS message is accepted. + +For the CS message acceptance process, see clause 8.1.4. + +### **6.1.5 Alignment supervision** + +#### **6.1.5.1 MTNS overhead Loss of Frame defect (dLOF)** + +MTNS FlexE instance overhead dLOF is generated based on the state of the frame alignment process defined in clause 8.2.2.2. + +dLOF shall be declared if the FlexE instance overhead frame alignment process is in the out-of-frame (OOF) or in the PAD out-of-lock state (OOL). + +dLOF shall be cleared when entering the in-frame (IF) state and the PAD in-lock (IL) state. + +#### **6.1.5.2 MTNS overhead Loss of Multi-frame defect (dLOM)** + +MTNS FlexE instance overhead dLOM is generated based on the state of the multi-frame alignment process defined in clause 8.2.2.3 for 100G FlexE instance or clause 8.2.2.4 for 50G FlexE instance. + +dLOM shall be declared if the multi-frame alignment process is in the out-of-multiframe (OOM) state. + +dLOM shall be cleared immediately when the multi-frame alignment process is in the in-multiframe (IM) state. + +#### 6.1.5.3 Loss of Basic message defect (dLOB) + +Loss of Basic message defect dLOB is generated based on the state of the MTN path OAM Basic block alignment process defined in clause 8.1.3. + +dLOB shall be declared if the MTN path OAM Basic block alignment is in the out-of-basic-block-alignment (OoBA) state. + +dLOB shall be cleared when the MTN path OAM Basic block alignment is in the in-basic-block-alignment (IBA) state. + +### 6.1.6 Protocol supervision + +#### 6.1.6.1 Client Calendar Mismatch defect (dCCM[j]) + +MTNS overhead defines calendar management as described in clause 9.2.3 of [ITU-T G.8312]. + +Client Calendar Mismatch defect is defined for each MTN path layer signal which is mapped into calendar slot in MTNS frame. + +The dCCM defect for MTNP tributaries is based on comparing the AcCC/AcCCA/AcCCB and ExCC/ExCCA/ExCCB of all FlexE instances extracted from the MTNS. dCCM shall be detected for each MTNP. The index *j* ranges from 1 to *p* and denotes the MTNP tributary port. + +Upon accepting a new AcCC/AcCCA/AcCCB value for all FlexE instances the nCCM anomalies for all tributary ports are initialized to false. The AcCC/AcCCA/AcCCB are then compared to the ExCC/ExCCA/ExCCB for all FlexE instances. + +When AcCC is equal to ExCC and both are equal to '0', for each case where the AcCCA/and ExCCA values pertaining to the same calendar slot are not equal, + +- a) if the calendar slot is allocated in the ExCCA value, the nCCManomaly of the tributary port subfield of the ExCCA value is set; +- b) if the calendar slot is allocated in the AcCCA value, the nCCManomaly of the tributary port subfield of the AcCCA value is set. + +When AcCC is equal to ExCC and both are equal to '1', for each case where the AcCCB/and ExCCB values pertaining to the same calendar slot are not equal, + +- a) if the calendar slot is allocated in the ExCCB value, the nCCManomaly of the tributary port subfield of the ExCCB value is set; +- b) if the calendar slot is allocated in the AcCCB value, the nCCManomaly of the tributary port subfield of the AcCCB value is set. + +The dCCM defect of each tributary port shall be set to the corresponding nCCM anomaly. + +``` + +for trib_port = 1 to number_of_trib_ports + nCCM[trib_port] = false +for FlexE = 1 to number_of_instances + for trib_slot = 1 to number_of_trib_slots + if AcCC == '0' and ExCC == '0' + if AcCCA[FlexE][trib_slot] != ExCCA[FlexE][trib_slot] + if ExCCA[FlexE][trib_slot].allocated + nCCM[ ExCCA[trib_slot].trib_port ] = true + if AcCCA[FlexE][trib_slot].allocated + nCCM[ AcCCA[trib_slot].trib_port ] = true + else if AcCC == '1' and ExCC == '1' + if AcCCB[FlexE][trib_slot] != ExCCB[FlexE][trib_slot] + if ExCCB[FlexE][trib_slot].allocated + nCCM[ ExCCB[trib_slot].trib_port ] = true + if AcCCB[FlexE][trib_slot].allocated + nCCM[ AcCCB[trib_slot].trib_port ] = true +for trib_port = 1 to number_of_trib_ports + dCCM[trib_port] = nCCM[trib_port] + +``` + +#### 6.1.6.2 Protection protocol supervision + +For linear protection, the failure of protocol defects are applied in the case of a bidirectional protection switching operation, where the coordination between the two ends is needed. + +According to clause 8.18 in [ITU-T G.8331], the following failure of protocol defects (dFOPs) are defined: + +- a) dFOP-PM that detects fully incompatible provisioning. It detects "B" bit mismatch, as described in clause 8.7 in [ITU-T G.8331]; +- b) dFOP-NR that detects mismatch in sent "Requested Signal" and received "Requested Signal" in case of bidirectional switching for > 50 ms. +- c) dFOP-TO that detects three consecutive APS messages are not received when there are no defects on the protection transport entity. + +### 6.1.7 Maintenance signal supervision + +#### 6.1.7.1 Alarm indication signal defect (dAIS) + +The alarm indication signal defect (dAIS) is detected at the MTNP layer. It monitors the presence of the AIS maintenance signal. + +As described in clause 10.2.1 of [ITU-T G.8312], MTNP AIS is indicated with continuous LF 66B blocks. Due to the possible insertion of IDLE blocks in intermediate nodes, the received LF 66B ordered set blocks may not be necessarily continuous. + +dAIS shall be declared if more than 4 LF blocks are received within an interval of 128 66B blocks. dAIS shall be cleared if no LF block is received within an interval of 128 66B blocks (and no intervening other fault ordered set). + +#### **6.1.7.2 Remote defect indicator defect (dRDI)** + +The remote defect indicator defect (dRDI) is detected at the MTNP layer. It monitors the presence of the RDI maintenance signal. + +dRDI shall be declared if the RDI bit in 3 consecutive basic messages is "1". + +dRDI shall be cleared if RDI bit in 5 consecutive received basic messages is "0". + +During CI\_SSF, dRDI shall be set to false.. + +#### **6.1.7.3 Remote PHY Fault defect (dRPF)** + +The remote PHY Fault defect (dRPF) is detected at the MTNS layer. It monitors the presence of the RPF signal. + +dRPF shall be declared if the extracted RPF is "1" in an overhead frame with good CRC. + +dRPF shall be cleared if the extracted RPF returns to "0" in an overhead frame with good CRC. + +## **6.2 Consequent actions** + +For consequent actions, see [ITU-T G.806] and the specific atomic functions. + +## **6.3 Defect correlations** + +For the defect correlations, see the specific atomic functions. + +## **6.4 Performance filters** + +### **6.4.1 One-second performance monitoring filters associated with counts** + +#### **6.4.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. + +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. + +NOTE – The "block" here is referring to the nominal $n \times 32K$ 66B blocks that compose a monitoring interval. + +#### **6.4.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. + +# **7 Information flow across reference points** + +See clause 7 of [ITU-T G.806] for a generic description of information flow. For the MTN-specific information flow, see the description of the functions in clauses 9 and following. + +# **8 MTN processes** + +Generic processes are defined in clause 8 of [ITU-T G.806]. This clause defines the specific process for the MTN. + +## **8.1 Processes for MTN Path layer** + +### **8.1.1 OAM block signature insertion process** + +The OAM block signature (i.e., ordered set block pattern) is inserted into the corresponding fields of the 66B OAM block. The ordered set block pattern is defined by the pattern "10" in bits 0 to 1 (i.e., the sync header), the pattern "0x4B" in bits 2 to 9 (i.e., the control block type), the pattern "0xC" in + +bits 34 to 37 (i.e., the "O" code) and the pattern all-zeros in bits 38 to 65 as described in clause 8.2.3 of [ITU-T G.8312]. + +### 8.1.2 OAM block acceptance process + +As defined in clause 8.3 of [ITU-T G.8312], a received MTNP OAM block will arrive in a range of blocks centred around the nominal insertion point with a deviation caused by delaying the actual insertion point to the first available IPG and the insertion or removal of idles for rate compensation. The behaviour is not specified for OAM blocks received outside this range. + +NOTE – The range is $\pm 2 \cdot 1130$ blocks (for jumbo frames) + the effect of rate compensation. For example, the range is $\pm (2260 + 230n)$ blocks for a 20 hop connection where $n$ is number of calendar slots. + +OAM blocks are identified based on the pattern "10" in bits 0 to 1 (i.e., the sync header), the pattern "0x4B" in bits 2 to 9 (i.e., the control block type), the pattern "0xC" in bits 34 to 37 (i.e., the "O" code), and the pattern all-zeros in bits 38 to 65, as described in clause 8.4 of [ITU-T G.8312]. + +A MTNP OAM block must be accepted and processed if the following criteria are satisfied: + +- 1) The receiver is in alignment with the BABL insertion opportunity pattern defined in Figure 8-9 of [ITU-T G.8312]. +- 2) The MTNP OAM message block appears within the expected range provided by the BABL alignment process. + +### 8.1.3 MTN Path OAM Basic block alignment + +The MTN Path OAM Basic block alignment shall be found by searching for the B1 and B2 Basic blocks (see [ITU-T G.8312]) contained in the MTN Path OAM sequence. + +In the OoBA state, the receiver searches for B1 and B2 Basic blocks. The IBA state shall be entered if a B1 block is found and confirmed with a B2 block received no later than $2T + 7K$ blocks. Alternatively, the IBA state shall be entered if a B2 block is found and confirmed with a B1 block received no later than $2T + 7K$ blocks. + +In the IBA state, the receiver monitors for a sequence of alternating B1 and B2 Basic blocks. The nominal location of a subsequent Basic block is $2T \times j$ from the location of the last accepted Basic block, where $j = 1 +$ the number of Basic blocks missing since the last accepted Basic block. A Basic block is declared missing if it has not been detected before the nominal location + $7K$ blocks. If a B1 block is declared missing the receiver searches for a B2 block. If a B2 block is declared missing the receiver searches for a B1 block. The OoBA state shall be entered when no Basic blocks are accepted within period of $7T$ . + +$T$ indicates the nominal MTNP OAM block insertion period which is equal to $n \times 16K$ blocks, where $n$ is the number of 5 Gbit/s calendar slots that the MTNP occupies. + +Appendix I provides an example state machine of this alignment process. + +### 8.1.4 OAM message acceptance process + +The MTNP OAM messages are transmitted at the insertion opportunities defined in clause 8.3 of [ITU-T G.8312]. + +OAM messages that meet the following criteria must be accepted and processed. + +- 1) The boundaries of an OAM message are identified by the SoM and EoM bits defined in Table 9-1 of [ITU-T G.8312]. +- 2) The length of the message is consistent with the value defined in Table 8-2 of [ITU-T G.8312] for the Message type. +- 3) In the A insertion opportunity: The MTN Message Type in the SoM block of a message is consistent with the message type for APS defined in Table 9-2 of [ITU-T G.8312]. + +In the L insertion opportunity: The MTN Message Type in the SoM block is consistent with the Message Type for the corresponding low priority opportunity in Table 9-2 of [ITU-T G.8312]. + +- 4) The CRC-12 checksum is correct. + +### 8.1.5 Trail trace identifier (TTI) acceptance and reporting process + +A new TTI is accepted if a new value is received in the 32 TTI field in the CV message with good CRC. + +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 6.1.2.1). + +### 8.1.6 Payload type (PT) acceptance process + +A new payload type is accepted (AcPT) if a new value is received in the PT field of the CS message with good CRC. + +## 8.2 Processes for MTN Section layer + +### 8.2.1 MTNS overhead acceptance processes + +#### 8.2.1.1 Group Identification (GID) acceptance process + +A new GID value (AcGID) is accepted if a new value of the FlexE Group Number field of the 50G/100G FlexE instance overhead is received in an overhead frame with good CRC. + +#### 8.2.1.2 Instance Identification (IID) acceptance process + +A new IID value (AcIID) is accepted when the same value of the 50G/100G FlexE instance number field of the 50G/100G FlexE instance overhead is received in two consecutive overhead frames with good CRC. + +#### 8.2.1.3 100G FlexE Map acceptance process + +The 256-bit 100G FlexE Map[0:255] is recovered from the FlexE Map field of the 100G FlexE instance overhead. + +When 100G FlexE instance overhead frame #i in the 32 frame multi-frame is received with good CRC, the bits AcFlexEMAP[(i-1)×8:(i-1)×8+7] are accepted from the FlexE Map field. + +#### 8.2.1.4 50G FlexE Map acceptance process + +The 128-bit 50G FlexE Map[0:127] is recovered from the FlexE Map field of the 50G FlexE instance overhead. + +When 50G FlexE instance overhead frame #i in the 16 frame multi-frame is received with good CRC, the bits AcFlexEMAP[(i-1)×8:(i-1)×8+7] are accepted from the FlexE Map field. + +#### 8.2.1.5 FlexE OH client calendar acceptance processes + +**Calendar configuration in use overhead (C):** The "calendar configuration in use" overhead from each FlexE instance shall be accepted (AcCC[i]) by majority vote of the 3 C overhead bits. Furthermore, it shall confirm the accepted "AcCC" by unanimity of the n FlexE instances in the MTNS (i.e., FlexE group). + +**Client calendar A and B overheads:** The 16-bit "client calendar A" and 16-bit "client calendar B" overhead fields from each FlexE instance shall be read and the calendar slot information shall be accepted in overhead frames with good CRC (AcCCA[i] and AcCCB[i]). + +**Calendar switch request overhead (CR):** The "calendar switch request" overhead from each FlexE instance shall be read and the calendar switch request information shall be accepted in overhead frames with good CRC (AcCR[i]). Furthermore, it shall confirm the accepted "AcCR" value by unanimity of the n FlexE instances in the MTNS (i.e., FlexE group). + +**Calendar switch acknowledge overhead (CA):** The "calendar switch acknowledge" overhead from each FlexE instance shall be read and the calendar switch acknowledge information shall be accepted in overhead frames with good CRC (AcCA[i]). Furthermore, it shall confirm the accepted "AcCA" value by unanimity of the n FlexE instances in the MTNS (i.e., FlexE group). + +### 8.2.2 Alignment processes + +#### 8.2.2.1 MTNS 66B PAD block lock + +The process shall perform 66B PAD block lock for each 50G/100G 66B stream carrying a 50G/100G FlexE instance in the case of a 50GBASE-R PHY, 200GBASE-R PHY or 400GBASE-R PHY to MTNS adaptation sink function (i.e., M-AI/MTNSy\_A\_Sk, with y=0, 2 or 4). The PAD blocks are arranged as one P1 block followed by one P2 block every 163830 blocks of a FlexE instance. The P1 PAD block is encoded as a special ordered set (the sync header is 10, the control block type is 0x4B (ordered set), the "O" code is 0x5 and with the value 0xFFFFF in bits 12-31). The P2 pad block is an Ethernet error control block. + +The process has two states, out-of-lock (OOL) and in-lock (IL). + +In the OOL state, the lock process shall search for the PAD block P1 followed by P2. The IL state shall be entered, when this P1+P2 block set of is found and confirmed one 163830 block period later. + +In the IL state, the 66B block stream shall be continuously checked with the presumed PAD start (PS) position for correct lock. The OOL state shall be entered if this P1+P2 block set is not found at the correct position in five consecutive 163830 block periods. + +The PAD start shall be maintained during the OOL state. + +#### 8.2.2.2 FlexE instance overhead frame alignment + +The FlexE instance overhead frame alignment shall be found by searching for FlexE instance block 1 of the FlexE instance overhead frame every $(1023 \times 20 + 1) \times 8$ blocks as described in clause 9.2.1 of [ITU-T G.8312]. + +NOTE – The 66B block 1 of the 50G/100G FlexE instance 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 instance block 1 is found in two consecutive FlexE instance overhead frames. + +In the IF state, OOF shall be entered when the FlexE instance block 1 of the FlexE instance overhead frame has mismatches on the sync header, control block type or O code fields for 5 consecutive occurrences. + +#### 8.2.2.3 100G FlexE instance overhead multi-frame alignment + +The 100G FlexE instance overhead multi-frame is a sequence of 32 100G FlexE instance overhead frames. The 100G Flex instance overhead multi-frame alignment shall be found based on the overhead multi-frame (OMF) bit in the 100G FlexE instance overhead. 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 100G FlexE instance overhead frames with good CRC. In the IM state, the state shall change from IM to OOM, when the two consecutive 100G FlexE instance 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. + +#### 8.2.2.4 50G FlexE instance overhead multi-frame alignment + +The 50G FlexE instance overhead multi-frame is a sequence of 16 50G FlexE instance overhead frames. The 50G Flex instance overhead multi-frame alignment shall be found based on the overhead multi-frame (OMF) bit in the 50G FlexE instance overhead. 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 50G FlexE instance overhead frames with good CRC. In the IM state, the state shall change from IM to OOM, when the two consecutive 50G FlexE instance 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. + +### 8.2.3 MCC insertion and extraction processes + +As defined in [ITU-T G.7712], an embedded communication channel (ECC) provides a logical operations channel between network elements (NEs) that can be utilized by various applications. A management communication channel (MCC) is an ECC dedicated for management plane communications. + +The MTNS MCC mapping and demapping processes are provided in MTNS to MTNP adaptation function to support the MTNS to MCC adaptation function as defined in [ITU-T G.7712]. + +#### 8.2.3.1 MCC insertion process + +Figure 8-1 provides MCC insertion process. The incoming COMMS (CI\_D) data is inserted into the MTNS management communication channel (MCC) field as described in clause 9.2.4 of [ITU-T G.8312]. + +![Diagram of the MCC insertion process. It shows a flow from COMMS_CI_D input to a 'COMMS mapping' block, which outputs MTNS_AI_D. The diagram is labeled G.8321(22).](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +``` +graph TD; A[COMMS_CI_D] --> B[COMMS mapping]; B --> C[MTNS_AI_D]; +``` + +Diagram of the MCC insertion process. It shows a flow from COMMS\_CI\_D input to a 'COMMS mapping' block, which outputs MTNS\_AI\_D. The diagram is labeled G.8321(22). + +Figure 8-1 – MCC insertion process + +#### 8.2.3.2 MCC extraction process + +Figure 8-2 provides MCC extraction process. + +![Figure 8-2: MCC extraction process diagram. A box labeled 'COMMS demapping' has an upward arrow from its top labeled 'COMMS_CI_D' and a downward arrow from its bottom labeled 'MTNS_AI_D'. Below the diagram is the text 'G.8321(22)'.](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Figure 8-2: MCC extraction process diagram. A box labeled 'COMMS demapping' has an upward arrow from its top labeled 'COMMS\_CI\_D' and a downward arrow from its bottom labeled 'MTNS\_AI\_D'. Below the diagram is the text 'G.8321(22)'. + +**Figure 8-2 – MCC extraction process** + +This process extracts MTNS management communication channel (MCC) field as described in clause 9.2.4 of [ITU-T G.8312]. + +# 9 MTN path layer functions + +Figure 9-1 illustrates the MTN Path layer network and client layer adaptation functions. The information crossing the MTNP connection point (MTNP\_CP) is referred to as the MTNP characteristic information (MTNP\_CI). The information crossing the MTNP access point (MTNP\_AP) is referred to as the MTNP adapted information (MTNP\_AI). The MTNP access point can be expanded to provide trail protection, as described in clause 9.4.1. + +![Figure 9-1: MTN Path layer network and client layer adaptation functions diagram. The diagram shows two symmetric paths. On the left, 'ETH_FP' and 'ETH_TFP' point to a trapezoid 'MTNP/ETH', which points to 'MTNP_AP', which points to a triangle 'MTNP', which points to 'MTNP_TCP', which points to an oval 'MTNP_C', which points to 'MTNP_CP'. On the right, 'MTNP_CP' points to 'MTNP_C', which points to 'MTNP_TCP', which points to a triangle 'MTNP', which points to 'MTNP_AP', which points to a trapezoid 'MTNP/ETH', which points to 'ETH_FP' and 'ETH_TFP'. A dashed double-headed arrow labeled 'MTNP_RP' connects the two 'MTNP' triangles. Below the diagram is the text 'G.8321(22)'.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +Figure 9-1: MTN Path layer network and client layer adaptation functions diagram. The diagram shows two symmetric paths. On the left, 'ETH\_FP' and 'ETH\_TFP' point to a trapezoid 'MTNP/ETH', which points to 'MTNP\_AP', which points to a triangle 'MTNP', which points to 'MTNP\_TCP', which points to an oval 'MTNP\_C', which points to 'MTNP\_CP'. On the right, 'MTNP\_CP' points to 'MTNP\_C', which points to 'MTNP\_TCP', which points to a triangle 'MTNP', which points to 'MTNP\_AP', which points to a trapezoid 'MTNP/ETH', which points to 'ETH\_FP' and 'ETH\_TFP'. A dashed double-headed arrow labeled 'MTNP\_RP' connects the two 'MTNP' triangles. Below the diagram is the text 'G.8321(22)'. + +**Figure 9-1 – MTN Path layer network and client layer adaptation functions** + +## 9.1 Connection functions + +### 9.1.1 MTNP connection function (MTNP\_C) + +The information flow and processing of the MTNP\_C function is defined with reference to Figures 9-2 and 9-3. The MTNP\_C function connects MTNP characteristic information from its input ports to its output ports. As the process does not affect the nature of the characteristic information, the reference points on either side of the MTNP\_C function are the same as illustrated in Figure 9-2. + +The connection process is bidirectional. As the MTNP\_CP has both sink and source functions, the combination of the unidirectional sink and source functions in Figure 9-2 forms a bidirectional function. + +#### Symbol + +![Diagram of the MTNP_C function symbol. It is an oval labeled 'MTNP_C'. On the left, an arrow labeled 'MTNP_C_MP' points into the oval. Above the oval, three arrows labeled 'MTNP_CP' point down into it, with ellipses between them. Below the oval, three arrows point down from it, labeled 'MTNP_CP' with ellipses between them. The text 'G.8321(22)' is written below the bottom right arrow.](73b5cce955ba9415a98791db7b0080ad_img.jpg) + +Diagram of the MTNP\_C function symbol. It is an oval labeled 'MTNP\_C'. On the left, an arrow labeled 'MTNP\_C\_MP' points into the oval. Above the oval, three arrows labeled 'MTNP\_CP' point down into it, with ellipses between them. Below the oval, three arrows point down from it, labeled 'MTNP\_CP' with ellipses between them. The text 'G.8321(22)' is written below the bottom right arrow. + +**Figure 9-2 – MTNP\_C function** + +#### Interfaces + +**Table 9-1 – MTNP\_C function inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| +| per MTNP_CP:
MTNP_CI_D
MTNP_CI_SSF
MTNP_CI_CK
MTNP_C_MP:
MTNP_C_MI_MatrixControl | per MTNP_CP:
MTNP_CI_D
MTNP_CI_SSF
MTNP_CI_CK | + +#### Processes + +The processes associated with the MTNP\_C function are as depicted in Figure 9-3. + +MTNP\_CI is routed between input and output connection points by means of a matrix connection. + +NOTE – 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, and it shall be able to remove an established matrix connection as defined by MI\_MatrixControl. + +Each (matrix) connection in the MTNP\_C function should be characterized by the: + +- Type of connection: unprotected. +- Traffic direction: bidirectional. +- Input and output connection points: set of connection points. + +**Open connection indication (OCI):** If an output of the connection function is not connected to an input, an MTNP-OCI signal as defined in clause 10.2.2 of [ITU-T G.8312] is generated for this output. + +![Figure 9-3: MTNP_C function processes diagram. A large grey rectangle represents the MTNP_C function. Inside, a white rectangle labeled 'Matrix connection' contains a smaller white rectangle labeled 'OCI'. An arrow labeled 'MTNP_C_MP' enters from the left. Multiple sets of three vertical arrows (labeled 'CL_D', 'CL_SSF', 'CL_CK') enter from the top and exit through the 'Matrix connection' to the bottom. These are labeled 'MTNP_CP' at both top and bottom. Ellipses indicate multiple such sets. A small label 'G.8321(22)' is at the bottom right.](7133ccf78043568ca62ecbcd43628a4a_img.jpg) + +Figure 9-3: MTNP\_C function processes diagram. A large grey rectangle represents the MTNP\_C function. Inside, a white rectangle labeled 'Matrix connection' contains a smaller white rectangle labeled 'OCI'. An arrow labeled 'MTNP\_C\_MP' enters from the left. Multiple sets of three vertical arrows (labeled 'CL\_D', 'CL\_SSF', 'CL\_CK') enter from the top and exit through the 'Matrix connection' to the bottom. These are labeled 'MTNP\_CP' at both top and bottom. Ellipses indicate multiple such sets. A small label 'G.8321(22)' is at the bottom right. + +Figure 9-3 – MTNP\_C function processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +## 9.2 Termination functions + +### 9.2.1 MTNP Trail Termination function (MTNP\_TT) + +The MTNP\_TT function terminates the path monitoring overhead of the MTNP to determine the status of the MTN path trail. Figure 9-4 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Figure 9-4: MTNP_TT diagram. Two inverted triangles labeled 'MTNP' are shown. The left triangle has an input arrow 'MTNP_AP' from above and an output arrow 'MTNP_TCP' from below. The right triangle has an output arrow 'MTNP_AP' from above and an input arrow 'MTNP_TCP' from below. A horizontal arrow labeled 'MTNP_RP' points from the right triangle to the left triangle. A small label 'G.8321(22)' is at the bottom right.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +Figure 9-4: MTNP\_TT diagram. Two inverted triangles labeled 'MTNP' are shown. The left triangle has an input arrow 'MTNP\_AP' from above and an output arrow 'MTNP\_TCP' from below. The right triangle has an output arrow 'MTNP\_AP' from above and an input arrow 'MTNP\_TCP' from below. A horizontal arrow labeled 'MTNP\_RP' points from the right triangle to the left triangle. A small label 'G.8321(22)' is at the bottom right. + +Figure 9-4 – MTNP\_TT + +#### 9.2.1.1 MTNP trail termination source function (MTNP\_TT\_So) + +The MTNP\_TT\_So function computes the BIP-8 and adds MTN path monitoring overhead – including the BIP-8, REI, RDI, TTI and DM signals – together with the CS and APS information message in the corresponding MTNP OAM block overhead field to the MTNP signal at its MTNP\_AP. + +The information flow and processing of the MTNP\_TT\_So function is defined with reference to Figures 9-5 and 9-6. + +##### Symbol + +![Symbol diagram for MTNP_TT_So function. A central triangle labeled MTNP has four input arrows from the top, left, and right, and one output arrow pointing downwards. The inputs are labeled MTNP_AP (top), MTNP_TP (left), MTNP_TT_So_MP (left), and MTNP_RP (right). The output is labeled MTNP_TCP. The reference G.8321(22) is shown to the right of the output.](0c08e48c08f96934cd6bc6911f3069dc_img.jpg) + +Symbol diagram for MTNP\_TT\_So function. A central triangle labeled MTNP has four input arrows from the top, left, and right, and one output arrow pointing downwards. The inputs are labeled MTNP\_AP (top), MTNP\_TP (left), MTNP\_TT\_So\_MP (left), and MTNP\_RP (right). The output is labeled MTNP\_TCP. The reference G.8321(22) is shown to the right of the output. + +Figure 9-5 – MTNP\_TT\_So function + +##### Interfaces + +Table 9-2 – MTNP\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| +| MTNP_AP:
MTNP_AI_CK
MTNP_AI_D
MTNP_AI_CS
MTNP_AI_APS
MTNP_RP:
MTNP_RI_RDI
MTNP_RI_REI
MTNP_RI_DM
MTNP_TP:
MTNP_TT_So_TI_Timestamp1
MTNP_TT_So_MP:
MTNP_TT_So_MI_TxTI
MTNP_TT_So_MI_APS_EN
MTNP_TT_So_MI_1DM_Trigger
MTNP_TT_So_MI_2DMM_Trigger | MTNP_TCP:
MTNP_CI_CK
MTNP_CI_D | + +##### Processes + +The processes associated with the MTNP\_TT\_So function are as depicted in Figure 9-6. + +**Basic OAM block generation:** Basic message is encoded into one 66B ordered set block. The function shall insert the following overhead into the corresponding field to generate a complete Basic OAM block. + +- **BIP:** The calculated BIP is inserted into the Parity byte position of the Basic message. The BIP computation method is described in clause 9.3.2.1 of [ITU-T G.8312]. +- **RDI:** The remote defect indication is inserted in the RDI bit position of the Basic message. Its value is derived from reference point MTNP\_RP. Upon the declaration/clearing of aRDI at the trail termination sink function, the trail termination source function shall have inserted/removed the RDI indication within 50 ms. +- **REI:** The number of errors indicated in RI\_REI is encoded in the REI bits position of the Basic message. Upon the detection of a number of errors at the trail termination sink function, the trail termination source function shall have inserted that value in the REI bits within 50 ms. + +- **RES:** The function shall insert all-zeros into the RES bits. +- **OAM type:** The function shall insert the OAM type value "001111" into the type field of the Basic OAM block as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" or "10" into the SoM&EoM field of the Basic OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**APS OAM blocks generation:** APS message is encoded into two 66B ordered set blocks. The first one carries APS1 and APS2 fields and the second one carries RES and CRC-12 fields. The function shall insert the following overhead into the corresponding field to generate complete APS OAM blocks. + +- **APS message information:** If the MI\_APS\_EN is true, the function shall insert the AI\_APS value into the corresponding position of the APS message. +- **CRC-12:** The function shall compute the CRC-12 over APS1, APS2 and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the APS message. +- **OAM type:** The function shall insert the OAM type value "010001" into the type field of the APS OAM blocks as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" into the SoM&EoM field of the first APS OAM block and value "01" into the SoM&EoM field of the second APS OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**CV OAM blocks generation:** CV message is encoded into seventeen 66B ordered set blocks. The first to the sixteenth of the CV OAM blocks carry TTI field and the last one carries RES and CRC-12 fields. The function shall insert the following overhead into the corresponding field to generate complete CV OAM blocks. + +- **TTI:** The trail trace identifier is inserted in the TTI bytes position of the CV message. Its value is derived from reference point MTNP\_TT\_So\_MP. The trail trace format is described in clause 9.1 of [ITU-T G.8312]. +- **RES:** The function shall insert all-zeros into the RES bits. +- **CRC-12:** The function shall compute the CRC-12 over TTI and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the CV message. +- **OAM type:** The function shall insert the OAM type value "110011" into the type field of the CV OAM blocks as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" into the SoM&EoM field of the first CV OAM block, value "00" into the SoM&EoM field of the second to sixteenth CV OAM blocks and value "01" into the SoM&EoM field of the seventeenth CV OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**1DM OAM blocks generation:** 1DM message is encoded into five 66B ordered set blocks. The first to the fourth of the 1DM OAM blocks carry Tx-f-TS field and the last one carries RES and CRC-12 fields. The function shall insert the following overhead into the corresponding field to generate complete 1DM OAM blocks. + +- **Tx-f-TS:** If MI\_1DM\_Trigger toggles, then a 64-bit timestamp TI\_timestamp1 is inserted into the Tx-f-TS bytes position of 1DM message, and TI\_timestamp1 is referenced to the time at which the first block of the low priority message sequence containing the 1DM (i.e., the first block of the CV message) was transmitted, which corresponds to its departure time. + +- **RES:** The function shall insert all-zeros into the RES bits. +- **CRC-12:** The function shall compute the CRC-12 over Tx-f-TS and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the 1DM message. +- **OAM type:** The function shall insert the OAM type value "110101" into the type field of the 1DM OAM blocks as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" into the SoM&EoM field of the first 1DM OAM block, value "00" into the SoM&EoM field of the second to forth 1DM OAM blocks and value "01" into the SoM&EoM field of the fifth 1DM OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**2DMM OAM blocks generation:** 2DMM message is encoded into five 66B ordered set blocks. The first to the fourth of the 2DMM OAM blocks carry Tx-f-TS field and the last one carries RES and CRC-12 fields. The function shall insert the following overhead into the corresponding field to generate complete 2DMM OAM blocks. + +- **Tx-f-TS:** If MI\_2DMM\_Trigger toggles, then a 64-bit timestamp TI\_timestamp1 is inserted into the Tx-f-TS bytes position of 2DMM message, and TI\_timestamp1 is referenced to the time at which the first block of the low priority message sequence containing the 2DMM (i.e., the first block of the CV message) was transmitted, which corresponds to its departure time. +- **RES:** The function shall insert all-zeros into the RES bits. +- **CRC-12:** The function shall compute the CRC-12 over Tx-f-TS and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the 2DMM message. +- **OAM type:** The function shall insert the OAM type value "111001" into the type field of the 2DMM OAM blocks as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" into the SoM&EoM field of the first 2DMM OAM block, value "00" into the SoM&EoM field of the second to forth 2DMM OAM blocks and value "01" into the SoM&EoM field of the fifth 2DMM OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**2DMR OAM blocks generation:** 2DMR message is generated upon reception of 2DMM message and encoded into thirteen 66B ordered set blocks. The first to the fourth of the 2DMR OAM blocks carry Tx-f-TS field, the fifth to the eighth of the 2DMR OAM blocks carry Rx-f-TS field, the ninth to the twelfth of the 2DMR OAM blocks carry Tx-b-TS field and the last one includes RES and CRC-12 fields. The function shall insert the following overhead into the corresponding field to generate complete 2DMR OAM blocks. + +- **Tx-f-TS:** The value of the Tx-f-TS bytes position of 2DMR message is determined by the RI\_DM. +- **Rx-f-TS:** A 64-bit timestamp TI\_timestamp1 is inserted into the Rx-f-TS bytes position of 2DMR message, and TI\_timestamp1 is referenced to the time at which the first block of the low priority message sequence containing the 2DMM (i.e., the first block of the CV message) was received, which corresponds to its arrival time. +- **Tx-b-TS:** A 64-bit timestamp TI\_timestamp1 is inserted into the Tx-b-TS bytes position of 2DMR message, and TI\_timestamp1 is referenced to the time at which the first block of the low priority message sequence containing the 2DMR (i.e., the first block of the CV message) was transmitted, which corresponds to its departure time. + +- **RES:** The function shall insert all-zeros into the RES bits. +- **CRC-12:** The function shall compute the CRC-12 over Tx-f-TS, Rx-f-TS, Tx-b-TS and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the 2DMR message. +- **OAM type:** The function shall insert the OAM type value "110000" into the type field of the 2DMR OAM blocks as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "10" into the SoM&EoM field of the first 2DMR OAM block, value "00" into the SoM&EoM field of the second to twelfth 2DMR OAM blocks and value "01" into the SoM&EoM field of the thirteenth 2DMR OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**CS OAM block generation:** CS message is encoded into one 66B ordered set block. The function shall insert the following overhead into the corresponding field to generate complete CS OAM blocks. + +- **CS message information:** The function shall insert the AI\_PT value into the corresponding bit position of the CS message. +- **CRC-12:** The function shall compute the CRC-12 over PT and RES fields as described in clause 9.3.3.1.1 of [ITU-T G.8312] and insert the calculated CRC-12 value into the CRC-12 field of the CS message. +- **OAM type:** The function shall insert the OAM type value "110110" into the type field of the CS OAM block as described in clause 9.3.1.2 of [ITU-T G.8312]. +- **SoM&EoM:** The function shall insert the SoM&EoM value "11" into the SoM&EoM field of the CS OAM block as described in clause 9.3.1.1 of [ITU-T G.8312]. +- **OAM block signature:** See clause 8.1.1. + +**MTNP OAM Insertion:** The function shall insert MTNP OAM blocks into the encoded Ethernet MAC client block sequence according to the sequence and insertion interval defined in clause 8.3 of [ITU-T G.8312]. + +**Basic OAM block insertion:** The function shall insert the Basic OAM blocks in the B opportunities shown in Figure 8-9 of [ITU-T G.8312]. The B1 block is inserted in the opportunity before the A opportunity, and the B2 block is inserted in the opportunity before the L opportunity. + +**APS OAM blocks insertion:** The function shall insert the APS OAM blocks into the A opportunity. + +**CV OAM blocks insertion:** The function shall insert the CV OAM blocks into the 1st to 17th L opportunities in the low priority opportunity pattern. + +**CS OAM blocks insertion:** The function shall insert the CS OAM block into the 18th L opportunity in the low priority opportunity pattern. + +**DM OAM blocks insertion:** 1DM and 2DMM OAM blocks are inserted on demand and 2DMR OAM blocks are inserted upon receiving 2DMM OAM blocks. These three kinds of DM OAM blocks share the same opportunities and for a given cycle of 64 low priority opportunities, only one kind of the DM OAM blocks may be transmitted. The function shall insert the DM OAM blocks into the L opportunities beginning with the 19th opportunity in the low priority opportunity pattern. + +NOTE – The NMS should avoid scheduling concurrent DM operations at a node (e.g., if the NMS has initiated a 2DMM at the A end of a path, it should not initiate a 1DM or 2DMM at the Z end of that path at the same time). The detailed mechanism is out of the scope of this Recommendation. + +![Figure 9-6 – MTNP_TT_So processes. This block diagram shows the internal processing of the MTNP_TT_So function. At the top, input signals AI_D, AI_CS, AI_APS, and AI_CK enter the MTNP_AP block. AI_D is connected to a 'Compute BIP-8' block and a vertical 'MTNP OAM insertion' block. AI_CS and AI_APS are also connected to the 'Compute BIP-8' block. AI_CK is connected to the 'MTNP OAM insertion' block. The 'Compute BIP-8' block outputs a 'BIP-8' signal to a 'Basic OAM generation' block. The 'Basic OAM generation' block outputs RI_REI and RI_RDI signals. The 'MTNP OAM insertion' block is connected to several 'OAM generation' blocks: 'Basic OAM generation', 'APS OAM generation', 'CV OAM generation', 'CS OAM generation', '1DM OAM generation', '2DMM OAM generation', and '2DMR OAM generation'. These blocks output various signals: APS_OAM generation outputs MI_APS_EN; CV_OAM generation outputs MI_TxTI; CS_OAM generation outputs AI_CS; 1DM_OAM generation outputs MI_1DM_Trigger and TI_Timestamp1; 2DMM_OAM generation outputs MI_2DMM_Trigger; 2DMR_OAM generation outputs RI_DM. All OAM generation blocks feed into the 'MTNP OAM insertion' block. The 'MTNP OAM insertion' block outputs CI_D and CI_CK signals at the bottom. The entire process is labeled MTNP_TCP at the bottom and G.8321(22) at the bottom right.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +Figure 9-6 – MTNP\_TT\_So processes. This block diagram shows the internal processing of the MTNP\_TT\_So function. At the top, input signals AI\_D, AI\_CS, AI\_APS, and AI\_CK enter the MTNP\_AP block. AI\_D is connected to a 'Compute BIP-8' block and a vertical 'MTNP OAM insertion' block. AI\_CS and AI\_APS are also connected to the 'Compute BIP-8' block. AI\_CK is connected to the 'MTNP OAM insertion' block. The 'Compute BIP-8' block outputs a 'BIP-8' signal to a 'Basic OAM generation' block. The 'Basic OAM generation' block outputs RI\_REI and RI\_RDI signals. The 'MTNP OAM insertion' block is connected to several 'OAM generation' blocks: 'Basic OAM generation', 'APS OAM generation', 'CV OAM generation', 'CS OAM generation', '1DM OAM generation', '2DMM OAM generation', and '2DMR OAM generation'. These blocks output various signals: APS\_OAM generation outputs MI\_APS\_EN; CV\_OAM generation outputs MI\_TxTI; CS\_OAM generation outputs AI\_CS; 1DM\_OAM generation outputs MI\_1DM\_Trigger and TI\_Timestamp1; 2DMM\_OAM generation outputs MI\_2DMM\_Trigger; 2DMR\_OAM generation outputs RI\_DM. All OAM generation blocks feed into the 'MTNP OAM insertion' block. The 'MTNP OAM insertion' block outputs CI\_D and CI\_CK signals at the bottom. The entire process is labeled MTNP\_TCP at the bottom and G.8321(22) at the bottom right. + +Figure 9-6 – MTNP\_TT\_So processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.2.1.2 MTNP trail termination sink function (MTNP\_TT\_Sk) + +The MTNP\_TT\_Sk function reports the state of the MTN path trail. It computes the BIP-8, extracts MTN path monitoring overhead (MTN PMOH) – including the BIP-8, REI, RDI, TTI and DM signals – together with the CS and APS message information in the MTNP OAM block overhead fields from the MTNP signal at its MTNP\_TCP, detects for AIS, OCI, TIM, DEG and RDI 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 MTNP\_TT\_So function. + +The information flow and processing of the MTNP\_TT\_Sk function is defined with reference to Figures 9-7 and 9-8. + +##### Symbol + +![Symbol diagram for MTNP function. A central triangle labeled 'MTNP' has four input/output arrows: 'MTNP_AP' pointing up from the top vertex, 'MTNP_TP' pointing right into the left vertex, 'MTNP_TT_Sk_MP' pointing left from the right vertex, and 'MTNP_RP' pointing right from the right vertex. Below the triangle, 'MTNP_TCP' points up to the bottom vertex. The reference 'G.8321(22)' is shown to the right.](5d3455c6c2a37cb3aff761fedeb8644e_img.jpg) + +Symbol diagram for MTNP function. A central triangle labeled 'MTNP' has four input/output arrows: 'MTNP\_AP' pointing up from the top vertex, 'MTNP\_TP' pointing right into the left vertex, 'MTNP\_TT\_Sk\_MP' pointing left from the right vertex, and 'MTNP\_RP' pointing right from the right vertex. Below the triangle, 'MTNP\_TCP' points up to the bottom vertex. The reference 'G.8321(22)' is shown to the right. + +Figure 9-7 – MTNP\_TT\_Sk function + +##### Interfaces + +Table 9-3 – MTNP\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTNP_TCP:
MTNP_CI_CK
MTNP_CI_D
MTNP_CI_SSF

MTNP_TP:
MTNP_TT_Sk_TI_Timestamp

MTNP_TT_Sk_MP:
MTNP_TT_Sk_MI_APS_EN
MTNP_TT_Sk_MI_ExSAPI
MTNP_TT_Sk_MI_ExDAPI
MTNP_TT_Sk_MI_GetAcTI
MTNP_TT_Sk_MI_TIMDetMo
MTNP_TT_Sk_MI_TIMActDis
MTNP_TT_Sk_MI_DEGThr
MTNP_TT_Sk_MI_DEGM
MTNP_TT_Sk_MI_1second | MTNP_AP:
MTNP_AI_CK
MTNP_AI_D
MTNP_AI_CS
MTNP_AI_APS
MTNP_AI_TSF
MTNP_AI_TSD

MTNP_RP:
MTNP_RI_RDI
MTNP_RI_REI
MTNP_RI_DM

MTNP_TT_Sk_MP:
MTNP_TT_Sk_MI_AcTI
MTNP_TT_Sk_MI_cOCI
MTNP_TT_Sk_MI_cLOB
MTNP_TT_Sk_MI_cLOCV
MTNP_TT_Sk_MI_cLOCS
MTNP_TT_Sk_MI_cTIM
MTNP_TT_Sk_MI_cDEG
MTNP_TT_Sk_MI_cRDI
MTNP_TT_Sk_MI_cSSF
MTNP_TT_Sk_MI_pN_EBC
MTNP_TT_Sk_MI_pN_DS
MTNP_TT_Sk_MI_pF_EBC
MTNP_TT_Sk_MI_pF_DS
MTNP_TT_Sk_MI_1DM_result[N_FD]
MTNP_TT_Sk_MI_2DM_result[N_FD, F_FD,B_FD] | + +##### Processes + +The processes associated with the MTNP\_TT\_Sk function are as depicted in Figure 9-8. + +**MTNP maintenance signal detection:** The function shall detect the status of the MTNP signal at the MTNP\_TCP. It shall be used for AIS and OCI defect detection. + +**MTNP OAM block acceptance:** See clause 8.1.2. + +**MTNP OAM Basic block alignment:** See clause 8.1.3. + +**MTNP OAM extraction:** The function shall extract MTNP OAM blocks from the MTNP signal, as defined in clause 8.4 of [ITU-T G.8312]. + +**Basic message extraction:** The function shall extract Basic message and process the following overhead. + +- **MTN BIP:** The MTN BIP is computed over the interval between basic messages as described in clause 9.3.2.1 of [ITU-T G.8312]. The MTN BIP value generated by MTNP\_TT\_So shall be extracted from the Parity byte position of the MTNP Basic message of the MTNP signal at the MTNP\_TCP. The location of the basic block in the sequence of received blocks defines the end/start of a parity calculation interval. The value calculated by the source in interval *i* is compared to the value carried in the basic block extracted at the end of *i*+2 parity calculation interval. If there is a mismatch between the two values, the parity calculation interval is marked as errored, one near-end errored block is detected and the number of BIP violations (nBIPV) is forwarded to the companion MTNP\_TT\_So function. +- **RDI:** The remote defect indication shall be recovered from the RDI bit position in the MTNP Basic message of the MTNP signal at the MTNP\_TCP. It shall be used for RDI defect detection. +- **REI:** The REI shall be recovered from the REI bits in the MTNP Basic message of the MTNP signal at the MTNP\_TCP. It shall be used to determine if a far-end errored block (nF\_B) has occurred. One nF\_B has occurred per REI value between 1 [0001] and 8 [1000]; otherwise, no nF\_B has occurred. + +NOTE 1 – The "block" here is referring to the nominal $n \times 32K$ 66B blocks that compose a monitoring interval. + +In the case of a missing Basic block, the count of errored intervals will reflect the interval with a missing BIP value for comparison and the intervals where the start or end of the interval is not known. Note that the RI\_REI value is set to a non-zero value for the intervals detected as errored due to a missing basic block. Appendix II provides more details about error monitoring when a basic message is not received. + +**APS message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract APS message. + +- **APS message information:** When APS is enabled (MI\_APS\_EN is true), the MTNP\_TT\_Sk function shall extract the APS message information from the APS1 and APS2 field of the APS message, and apply the extracted information to the AI\_APS. + +**CV message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract CV message. + +- **TTI:** The MTNP\_TT\_Sk function shall extract the information from the TTI field of the CV message and processed as specified in clause 8.1.5. The accepted value of the TTI is available at the MP (MI\_AcTI). + +**CS message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract CS message. + +- **CS message information:** The MTNP\_TT\_Sk function shall extract the CS message information from the corresponding field of the CS message and apply the extracted information to the AI\_CS. + +**1DM message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract 1DM message. + +- **Tx-f-TS:** The MTNP\_TT\_Sk function shall extract the information from the Tx-f-TS field of the 1DM message and compare it to the Rx-f-TS 64-bit timestamp which is referenced to the time at which the first block of the low priority message sequence carrying this 1DM message (i.e., arrival time) was received. The near end one-way delay result 1DM\_N\_FD equals [Rx-f-TS - Tx-f-TS]. + +NOTE 2 – For one way delay measurement, the source node and the sink node should be synchronized. + +**2DMM message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract 2DMM message. + +- **Tx-f-TS:** The MTNP\_TT\_Sk function shall extract the information from the Tx-f-TS field of the 2DMM message and output it to RI\_DM together with the Rx-f-TS 64-bit timestamp which is referenced to the time at which the first block of the low priority message sequence carrying this 2DMM message (i.e., arrival time) was received. + +**2DMR message extraction:** The function shall perform the OAM message acceptance process as defined in clause 8.1.4 to extract 2DMR message. + +- **Tx-f-TS:** The MTNP\_TT\_Sk function shall extract the information from the Tx-f-TS field of the 2DMR message. +- **Rx-f-TS:** The MTNP\_TT\_Sk function shall extract the information from the Rx-f-TS field of the 2DMR message, the far end delay result 2DM\_F\_FD equals [Rx-f-TS - Tx-f-TS]. +- **Tx-b-TS:** The MTNP\_TT\_Sk function shall extract the information from the Tx-b-TS field of the 2DMR message and compare it to the Rx-b-TS 64-bit timestamp which is referenced to the time at which the first block of the low priority message sequence carrying this 2DMR message (i.e., arrival time) was received. The near end one-way delay result 2DM\_N\_FD equals [Rx-b-TS - Tx-b-TS], the round trip delay result 2DM\_B\_FD equals [(Rx-f-TS – Tx-f-TS) + (Rx-b-TS – Tx-b-TS)]. + +![Figure 9-8 – MTNP_TT_Sk processes. A complex block diagram showing the internal processes of an MTNP_TT_Sk unit. The diagram is divided into three main horizontal sections: MTNP_AP (top), MTNP_TT_Sk_MP (middle), and MTNP_TCP (bottom). MTNP_AP contains blocks for 'Consequent actions' and 'Process TTI'. MTNP_TT_Sk_MP contains 'Defect correlation', 'Performance monitoring', 'Process errors', 'Extract TTI', 'Extract 2MM', 'Process 2DMR', 'Extract 2DMR', 'Process IDM', 'Extract IDM', 'Extract CS message information', 'Extract APS message information', 'Extract RID', 'Extract REI', 'Extract BIP', 'Compute BIP', 'Compare', 'MTNP OAM basic block alignment', 'MTNP OAM block acceptance', and 'Maintenance signal detection'. MTNP_TCP contains 'Basic message extraction'. Numerous input and output signals are shown, such as RI_REI, RI_DM, RI_RDI, MI_TIMActDis, MI_ExSAPI, MI_ExDAPI, MI_TIMDetMo, MI_GetAcTI, MI_ActTI, TI_Timestamp, MI_cTIM, MI_cDEG, MI_cRDI, MI_cLOB, MI_cLOCV, MI_cLOCS, MI_cOCI, MI_cSSF, MI_APS_EN, MI_2DM_result, MI_1DM_result, MI_1second, MI_pF_DS, MI_pF_EBC, MI_pN_DS, MI_pN_EBC, MU_DEGThr, MI_DEGM, AI_TSD, AI_TSF, AI_CS, AI_APS, AI_CK, AI_D, CI_SSF, CI_CK, and CI_D. Data flows are indicated by arrows between the various processing blocks.](7ae836e598020d937ed1478c2ef13025_img.jpg) + +Figure 9-8 – MTNP\_TT\_Sk processes. A complex block diagram showing the internal processes of an MTNP\_TT\_Sk unit. The diagram is divided into three main horizontal sections: MTNP\_AP (top), MTNP\_TT\_Sk\_MP (middle), and MTNP\_TCP (bottom). MTNP\_AP contains blocks for 'Consequent actions' and 'Process TTI'. MTNP\_TT\_Sk\_MP contains 'Defect correlation', 'Performance monitoring', 'Process errors', 'Extract TTI', 'Extract 2MM', 'Process 2DMR', 'Extract 2DMR', 'Process IDM', 'Extract IDM', 'Extract CS message information', 'Extract APS message information', 'Extract RID', 'Extract REI', 'Extract BIP', 'Compute BIP', 'Compare', 'MTNP OAM basic block alignment', 'MTNP OAM block acceptance', and 'Maintenance signal detection'. MTNP\_TCP contains 'Basic message extraction'. Numerous input and output signals are shown, such as RI\_REI, RI\_DM, RI\_RDI, MI\_TIMActDis, MI\_ExSAPI, MI\_ExDAPI, MI\_TIMDetMo, MI\_GetAcTI, MI\_ActTI, TI\_Timestamp, MI\_cTIM, MI\_cDEG, MI\_cRDI, MI\_cLOB, MI\_cLOCV, MI\_cLOCS, MI\_cOCI, MI\_cSSF, MI\_APS\_EN, MI\_2DM\_result, MI\_1DM\_result, MI\_1second, MI\_pF\_DS, MI\_pF\_EBC, MI\_pN\_DS, MI\_pN\_EBC, MU\_DEGThr, MI\_DEGM, AI\_TSD, AI\_TSF, AI\_CS, AI\_APS, AI\_CK, AI\_D, CI\_SSF, CI\_CK, and CI\_D. Data flows are indicated by arrows between the various processing blocks. + +Figure 9-8 – MTNP\_TT\_Sk processes + +##### Defects + +The function shall detect dAIS, dOCI, dLOB, dLOCV, dLOCS, dTIM, dDEG, and dRDI defects. + +**dAIS:** See clause 6.1.7.1. + +**dOCI:** See clause 6.1.1.1; dOCI shall be set to false during CI\_SSF. + +**dLOB:** See clause 6.1.5.3. + +**dLOCV:** See clause 6.1.2.4; dLOCV shall be set to false during dLOB. + +**dLOCS:** See clause 6.1.4.2; dLOCS shall be set to false during dLOB. + +**dTIM:** See clause 6.1.2.1; dTIM shall be set to false during CI\_SSF. + +**dDEG:** See clause 6.1.3.1. + +**dRDI:** See clause 6.1.7.2; dRDI shall be set to false during CI\_SSF. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aRDI $\leftarrow$ CI\_SSF or dAIS or dOCI or dLOB or dLOCV or dTIM +aTSF $\leftarrow$ CI\_SSF or dAIS or dOCI or dLOB or dLOCV or dLOCS or (dTIM and (not TIMActDis)) +aTSD $\leftarrow$ dDEG +aREI $\leftarrow$ nBIPV + +##### 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. + +cOCI $\leftarrow$ dOCI and (not CI\_SSF) +cLOB $\leftarrow$ dLOB and (not dAIS) and (not dOCI) and (not CI\_SSF) +cLOCV $\leftarrow$ dLOCV and (not dLOB) and (not dAIS) and (not dOCI) and (not CI\_SSF) +cLOCS $\leftarrow$ dLOCS and (not dLOB) and (not dAIS) and (not dOCI) and (not CI\_SSF) +cTIM $\leftarrow$ dTIM and (not dLOCV) and (not dLOB) and (not dAIS) and (not dOCI) and (not CI\_SSF) +cDEG $\leftarrow$ dDEG and (not CI\_SSF) and (not dAIS) and (not dOCI) and (not dLOB) and (not (dTIM and (not TIMActDis)))) +cRDI $\leftarrow$ dRDI and (not CI\_SSF) and (not dAIS) and (not dOCI) and (not dLOB) and (not dLOCV) and (not dLOCS) and (not (dTIM and (not TIMActDis)))) +cSSF $\leftarrow$ 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. + +2DM\_result[B\_FD] $\leftarrow$ 2DM\_B\_FD +2DM\_result[F\_FD] $\leftarrow$ 2DM\_F\_FD +2DM\_result[N\_FD] $\leftarrow$ 2DM\_N\_FD +1DM\_result[N\_FD] $\leftarrow$ 1DM\_N\_FD +pN\_DS $\leftarrow$ CI\_SSF or dAIS or dOCI or dTIM +pF\_DS $\leftarrow$ dRDI +pN\_EBC $\leftarrow$ $\sum$ nN\_B + +NOTE 3 – During CI\_SSF, dAIS and dOCI, no errored blocks shall be counted. + +pF\_EBC $\leftarrow$ $\sum$ nF\_B + +NOTE 4 – During CI\_SSF, dAIS and dOCI, no errored blocks shall be counted. + +## 9.3 Adaptation functions + +### 9.3.1 MTNP to ETH adaptation function (MTNP/ETH\_A) + +The MTNP to ETH adaptation functions perform the adaptation between MTN Path layer adapted information and the characteristic information of Ethernet MAC frames. + +#### 9.3.1.1 MTNP to ETH adaptation source function (MTNP/ETH\_A\_So) + +The MTNP/ETH\_A\_So function maps the sequence of Ethernet MAC frame client signals to the MTNP layer. It inserts CS message information (everything but CRC-12 of the CS message) to the sequence. The information flow and processing of the MTNP/ETH\_A\_So function is defined with reference to Figures 9-9 and 9-10. + +##### Symbol + +![Diagram of the MTNP/ETH_A_So function symbol. A central trapezoidal block labeled 'MTNP/ETH' has two input arrows from the top labeled 'ETH_FP' and 'ETH_TFP'. It has one output arrow pointing left labeled 'MTNP/ETH_A_So_MP'. It has two output arrows pointing right labeled 'ETH_TF_PP' and 'ETHF_PP'. It has one output arrow pointing down labeled 'MTNP_AP'. The text 'G.8321(22)' is located to the right of the block.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +Diagram of the MTNP/ETH\_A\_So function symbol. A central trapezoidal block labeled 'MTNP/ETH' has two input arrows from the top labeled 'ETH\_FP' and 'ETH\_TFP'. It has one output arrow pointing left labeled 'MTNP/ETH\_A\_So\_MP'. It has two output arrows pointing right labeled 'ETH\_TF\_PP' and 'ETHF\_PP'. It has one output arrow pointing down labeled 'MTNP\_AP'. The text 'G.8321(22)' is located to the right of the block. + +Figure 9-9 – MTNP/ETH\_A\_So function + +##### Interfaces + +Table 9-3 – MTNP/ETH\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ETH_TFP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

ETH_FP:
ETH_CI_D
ETH_CI_P
ETH_CI_DE

MTNP/ETH_A_So_MP:
MTNP/ETH_A_So_MI [IEEE 802.3] | MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS message information

ETH_TF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

MTNP/ETH_A_So_MP:
MTNP/ETH_A_So_MI [IEEE 802.3] | + +##### Processes + +The processes associated with the MTNP/ETH\_A\_So function are as depicted in Figure 9-10. + +![Figure 9-10 – MTNP/ETH_A_So processes. A flowchart showing the data flow from input signals (ETH_CI (ETH_FP) and ETH_CI (ETH_TFP)) through Client-specific processes, [IEEE 802.3] processes, and CS message information generation to output signals (ETH_PI (ETHF_PP), ETH_PI (ETHF_PP), MI_[IEEE 802.3], MTNP_AI, and MTNP_AP).](145d00f59802048185303f15937ea65c_img.jpg) + +The diagram illustrates the data flow for the MTNP/ETH\_A\_So function. At the top, two input signals, ETH\_CI (ETH\_FP) and ETH\_CI (ETH\_TFP), enter a grey box representing the function. The first signal goes to a white box labeled 'Client-specific processes'. The second signal goes to a yellow box labeled '[IEEE 802.3] processes'. The 'Client-specific processes' box has two output arrows pointing to ETH\_PI (ETHF\_PP) and ETH\_PI (ETHF\_PP). The '[IEEE 802.3] processes' box has an output arrow pointing to MI\_[IEEE 802.3]. Below the '[IEEE 802.3] processes' box is a white box labeled 'CS message information generation'. This box has two input arrows from the right, labeled 'Insert PT' and 'Insert RES'. The output of the 'CS message information generation' box points to MTNP\_AI and MTNP\_AP. The reference G.8321(22) is noted in the bottom right corner of the diagram. + +Figure 9-10 – MTNP/ETH\_A\_So processes. A flowchart showing the data flow from input signals (ETH\_CI (ETH\_FP) and ETH\_CI (ETH\_TFP)) through Client-specific processes, [IEEE 802.3] processes, and CS message information generation to output signals (ETH\_PI (ETHF\_PP), ETH\_PI (ETHF\_PP), MI\_[IEEE 802.3], MTNP\_AI, and MTNP\_AP). + +Figure 9-10 – MTNP/ETH\_A\_So processes + +**Client-specific processes:** The client-specific processes, and associated MI and PI signals, are defined in clause 9.5 of [ITU-T G.8021]. + +**[IEEE802.3] processes:** The [IEEE 802.3] processes include 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. + +**CS message information generation:** The function shall insert the following overhead into the corresponding field to generate a complete CS message information and apply it to AI\_CS. + +- **PT:** The function shall insert the payload type code "01" into the PT bit position of the CS message, as defined in clause 9.3.3.5.1 of [ITU-T G.8312]. +- **RES:** The function shall insert all-zeros into the RES bits. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.3.1.2 MTNP to ETH sink function (MTNP/ETH\_A\_Sk) + +The MTNP/ETH\_A\_Sk extracts ETH\_CI information from the MTNP layer, delivering ETH\_CI to ETH\_TFP and ETH\_FP. It extracts the CS message information and monitors the reception of the correct payload type. The information flow and processing of the MTNP/ETH\_A\_So function is defined with reference to Figures 9-11 and 9-12. + +##### Symbol + +![Diagram of the MTNP/ETH_A_Sk symbol. A central trapezoidal block labeled 'MTNP/ETH' has several interfaces: 'MTNP/ETH_A_Sk_MP' on the left with a double-headed arrow; 'ETH_FP' and 'ETH_TFP' at the top with upward-pointing arrows; 'ETHTF_PP' and 'ETHF_PP' on the right with leftward-pointing arrows; and 'MTNP_AP' at the bottom with an upward-pointing arrow. The reference 'G.8321(22)' is shown in the bottom right corner.](7f5df81190b8dc50dad2604562ae0715_img.jpg) + +Diagram of the MTNP/ETH\_A\_Sk symbol. A central trapezoidal block labeled 'MTNP/ETH' has several interfaces: 'MTNP/ETH\_A\_Sk\_MP' on the left with a double-headed arrow; 'ETH\_FP' and 'ETH\_TFP' at the top with upward-pointing arrows; 'ETHTF\_PP' and 'ETHF\_PP' on the right with leftward-pointing arrows; and 'MTNP\_AP' at the bottom with an upward-pointing arrow. The reference 'G.8321(22)' is shown in the bottom right corner. + +Figure 9-11 – MTNP/ETH\_A\_Sk symbol + +##### Interfaces + +Table 9-9 – MTNP/ETH\_A\_Sk interfaces + +| Inputs | Outputs | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS
MTNP_AI_TSF

ETHTF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

ETHF_PP:
ETH_PI_D
ETH_PI_P
ETH_PI_DE

MTNP/ETH_A_Sk_MP:
MTNP/ETH_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

MTNP/ETH_A_Sk_MP:
MTNP/ETH_A_Sk_MI_cPLM
MTNP/ETH_A_Sk_MI_AcPT
MTNP/ETH_A_Sk_MI_[IEEE 802.3] | + +##### Processes + +The processes associated with the MTNP/ETH\_A\_Sk function are as depicted in Figure 9-12. + +![Figure 9-12 – MTNP/ETH_A_Sk process diagram. The diagram shows a hierarchy of processes within a grey box labeled MTNP_AP. At the top are three output labels: ETH_CI_D/P/DE (ETH_FP), ETH_CI_D/P/DE (ETH_TFP), and ETH_CI_SSF. Below these, a box labeled 'Client-specific processes' receives 'MI_signals (See ITU-T G.8021)' from the left and two 'ETH_PI' signals (ETHHTF_PP and ETHTF_PP) from the right. It also receives inputs from '[IEEE 802.3] processes' (highlighted in yellow) and 'CS message information extraction'. The 'Client-specific processes' box outputs to the top three labels and to a 'Consequent actions' box. The 'Consequent actions' box outputs to 'ETH_CI_SSF' and receives inputs from 'dPLM' and 'AI_TSF'. The '[IEEE 802.3] processes' box receives 'MI_[IEEE 802.3]' from the left and outputs to 'Client-specific processes' and a 'Defect correlations' box. The 'Defect correlations' box outputs to 'MI_cPLM' and receives inputs from 'dPLM' and 'AI_TSF'. The 'CS message information extraction' box receives 'MTNP_AI' from the bottom and outputs to 'Client-specific processes' and a 'PT process' box. The 'PT process' box outputs to 'MI_AcPT' and receives inputs from 'dPLM'. The 'PT process' box also outputs to 'ETH_CI_SSF'. The bottom of the diagram shows 'MTNP_AI' and 'AI_TSF' inputs to the 'MTNP_AP' box. The reference 'G.8321(22)' is noted in the bottom right corner of the diagram area.](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) + +Figure 9-12 – MTNP/ETH\_A\_Sk process diagram. The diagram shows a hierarchy of processes within a grey box labeled MTNP\_AP. At the top are three output labels: ETH\_CI\_D/P/DE (ETH\_FP), ETH\_CI\_D/P/DE (ETH\_TFP), and ETH\_CI\_SSF. Below these, a box labeled 'Client-specific processes' receives 'MI\_signals (See ITU-T G.8021)' from the left and two 'ETH\_PI' signals (ETHHTF\_PP and ETHTF\_PP) from the right. It also receives inputs from '[IEEE 802.3] processes' (highlighted in yellow) and 'CS message information extraction'. The 'Client-specific processes' box outputs to the top three labels and to a 'Consequent actions' box. The 'Consequent actions' box outputs to 'ETH\_CI\_SSF' and receives inputs from 'dPLM' and 'AI\_TSF'. The '[IEEE 802.3] processes' box receives 'MI\_[IEEE 802.3]' from the left and outputs to 'Client-specific processes' and a 'Defect correlations' box. The 'Defect correlations' box outputs to 'MI\_cPLM' and receives inputs from 'dPLM' and 'AI\_TSF'. The 'CS message information extraction' box receives 'MTNP\_AI' from the bottom and outputs to 'Client-specific processes' and a 'PT process' box. The 'PT process' box outputs to 'MI\_AcPT' and receives inputs from 'dPLM'. The 'PT process' box also outputs to 'ETH\_CI\_SSF'. The bottom of the diagram shows 'MTNP\_AI' and 'AI\_TSF' inputs to the 'MTNP\_AP' box. The reference 'G.8321(22)' is noted in the bottom right corner of the diagram area. + +**Figure 9-12 – MTNP/ETH\_A\_Sk process** + +**Client-specific processes:** The client-specific processes, and associated MI and PI signals, are defined in clause 9.5 of [ITU-T G.8021]. + +**CS message information extraction:** The following overheads are extracted and processed. + +- **PT:** The function shall extract the PT bits from the CS message information as defined in clause 8.1.6. The accepted PT value is available at the MP (MI\_AcPT) and is used for PLM defect detection. +- **RES:** The value in the RES bits shall be ignored. + +**[IEEE802.3] processes:** The [IEEE 802.3] processes include 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. + +##### Defects + +The function shall detect dPLM. + +**dPLM:** See clause 6.1.4.1. The expected payload type is "01" as defined in clause 9.3.3.5.1 of [ITU-T G.8312]. + +##### Consequent actions + +The function shall perform the following consequent actions: + +aSSF ← AI\_TSF or dPLM + +##### 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 ← dPLM and (not AI\_TSF) + +**Performance monitoring:** None. + +## 9.4 Sublayer functions + +### 9.4.1 MTNP trail protection functions + +Figure 9-13 shows the involved atomic functions in MTNP trail protection. The MTNP\_TT\_Sk provides the TSF/TSD protection switching criterion via the MTNP/MTNPp\_A\_Sk function (SSF/SSD) to the MTNPp\_C function. + +![Figure 9-13: Involved atomic functions in trail protection. The diagram illustrates the flow of data and control signals through various MTNP and MTNS functions. At the top, two MTNP/ETH functions are shown with arrows pointing to and from them. Below them are MTNPp functions. The central part is a large oval labeled 'MTNPp_C' with three states: 'Normal', 'Working', and 'Protection'. Arrows connect the MTNPp functions to this central oval. Below the oval, there are four columns of functions: MTNP/MTNPp, MTNP, and MTNS/MTNP. Arrows show the flow of signals like MTNPp_CI_D, MTNPp_CI_SSF/SSD, MTNPp_CI_APS, MTNP_AI_D, and MTNP_AI_TSF/TSD between these functions and the central oval. The diagram is labeled G.8321(22) at the bottom right.](26e334e61dd059cff029338a2a604d8d_img.jpg) + +Figure 9-13: Involved atomic functions in trail protection. The diagram illustrates the flow of data and control signals through various MTNP and MTNS functions. At the top, two MTNP/ETH functions are shown with arrows pointing to and from them. Below them are MTNPp functions. The central part is a large oval labeled 'MTNPp\_C' with three states: 'Normal', 'Working', and 'Protection'. Arrows connect the MTNPp functions to this central oval. Below the oval, there are four columns of functions: MTNP/MTNPp, MTNP, and MTNS/MTNP. Arrows show the flow of signals like MTNPp\_CI\_D, MTNPp\_CI\_SSF/SSD, MTNPp\_CI\_APS, MTNP\_AI\_D, and MTNP\_AI\_TSF/TSD between these functions and the central oval. The diagram is labeled G.8321(22) at the bottom right. + +**Figure 9-13 – Involved atomic functions in trail protection** + +The protection functions at both ends operate the same way, by monitoring the working and the protection trail for defects, evaluating the system status, taking into consideration the priorities of defect conditions and of external switch requests, and switching the appropriate connection point (i.e., working or protection) to the protected termination connection point. + +#### 9.4.1.1 Connection function for trail protection (MTNPp\_C) + +MTNPp\_C is the specific function that is used to support trail protection defined in [ITU-T G.8331]. The MTNPp\_C connection process is a unidirectional function as illustrated in Figure 9-14 and the interface is described in Table 9-15. + +##### Symbol + +![Diagram of MTNPp_C function symbol. A central oval is labeled 'MTNPp_C'. Above it, 'Normal MTNPp_CP' has two upward arrows and two downward arrows. Below it, 'Working MTNPp_CP' has two upward arrows and two downward arrows. To the right, 'Protection MTNPp_CP' has two upward arrows and two downward arrows. To the left, 'MTNPp_C_MP' has a single double-headed arrow. The diagram is labeled G.8321(22) at the bottom right.](70a863dc6cd47bac82c12162a9479aac_img.jpg) + +Diagram of MTNPp\_C function symbol. A central oval is labeled 'MTNPp\_C'. Above it, 'Normal MTNPp\_CP' has two upward arrows and two downward arrows. Below it, 'Working MTNPp\_CP' has two upward arrows and two downward arrows. To the right, 'Protection MTNPp\_CP' has two upward arrows and two downward arrows. To the left, 'MTNPp\_C\_MP' has a single double-headed arrow. The diagram is labeled G.8321(22) at the bottom right. + +**Figure 9-14 – MTNPp\_C function** + +MTNPp\_CI at the normal MTNPp\_CP are bridged/selected to/from the working and/or protection MTNPp\_CP by the protection switching process for trail protection. + +**Table 9-10 – MTNPp\_C input and output signals** + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Per normal MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS

Per working MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_SSF
MTNPp_CI_SSD
MTNPp_CI_AIS
MTNPp_CI_CK
MTNPp_CI_CS

Per protection MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_APS
MTNPp_CI_SSF
MTNPp_CI_SSD
MTNPp_CI_CK
MTNPp_CI_CS

MTNPp_C_MP:
Per protection group:
MTNPp_C_MI_WorkingPortId
MTNPp_C_MI_ProtectionPortId
MTNPp_C_MI_ProtType
MTNPp_C_MI_OperType
MTNPp_C_MI_HoTime
MTNPp_C_MI_WTR
MTNPp_C_MI_ExtCMD
MTNPp_C_MI_SDEnable | Per normal MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_SSF
MTNPp_CI_AIS
MTNPp_CI_CK
MTNPp_CI_CS

Per working MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS

Per protection MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_APS
MTNPp_CI_CK
MTNPp_CI_CS

MTNPp_C_MP:
Per protection group:
MTNPp_C_MI_cFOP-PM
MTNPp_C_MI_cFOP-CM
MTNPp_C_MI_cFOP-NR
MTNPp_C_MI_cFOP-TO | + +The signal flows associated with the MTNPp\_protection process are described with reference to Figure 9-15. The protection process receives control parameters and external switch requests at the MP reference point. + +![Diagram of the protection process for trail protection. The diagram shows a 'Normal' section at the top with input MTNPp_CI_D and output MTNPp_CI_SSF/SSD. Below it is a 'Protection process' box containing two sub-sections: 'Selector' and 'Bridge'. Each sub-section has two internal components labeled 'W' (Working) and 'P' (Protection). The 'Selector' section is connected to 'working' trails, and the 'Bridge' section is connected to 'protection' trails. External connections include MTNPp_CI_MI on the left, and MTNPp_CI_D and MTNPp_CI_SSF/SSD on the bottom for both working and protection trails. A small label 'G.8321(22)' is in the bottom right corner.](4ae4505e885586e481a3ad3bff5198b7_img.jpg) + +Diagram of the protection process for trail protection. The diagram shows a 'Normal' section at the top with input MTNPp\_CI\_D and output MTNPp\_CI\_SSF/SSD. Below it is a 'Protection process' box containing two sub-sections: 'Selector' and 'Bridge'. Each sub-section has two internal components labeled 'W' (Working) and 'P' (Protection). The 'Selector' section is connected to 'working' trails, and the 'Bridge' section is connected to 'protection' trails. External connections include MTNPp\_CI\_MI on the left, and MTNPp\_CI\_D and MTNPp\_CI\_SSF/SSD on the bottom for both working and protection trails. A small label 'G.8321(22)' is in the bottom right corner. + +**Figure 9-15 – Protection process for trail protection** + +##### *Source direction:* + +For a 1+1 architecture, the CI coming from the normal (protected) MTNPp\_CP is bridged permanently to both the working and protection MTNPp\_CP. + +##### *Sink direction:* + +For a 1+1 architecture, the CI coming from either the working or protection MTNPp\_CP is switched to the normal (protected) MTNPp\_CP. A switch-over from working to protection MTNPp\_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 trails, server signal fail (SSF) and server signal degrade (SSD). + +A hold-off timer is provided in order to allow interworking between nested protection schemes. The hold-off timer delays switch initiation, in case of signal fail or signal degrade, 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 or signal degrade and runs for the hold-off time. Protection switching is only initiated if signal fail or signal degrade is still present at the end of the hold-off time. The hold-off time shall be provisionable as defined in [ITU-T G.8331]. + +Protection switching can also be initiated by external switch commands received via the MP or a request from the far end via the received MTNPp\_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.8331]. + +##### *Switching time:* + +Refer to [ITU-T G.8331]. + +##### *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 faulty 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 capable of being set. The WTR is defined in [ITU-T G.831]. + +In the non-revertive mode of operation no switch back to the working trail is performed when it has recovered from the fault. + +##### *Configuration:* + +The configuration parameters are as following: + +- MTNPp\_C\_MI\_WorkingPortId configures the working port. +- MTNPp\_C\_MI\_ProtectionPortId configures the protection port. +- MTNPp\_C\_MI\_ProtType configures the protection type. +- MTNPp\_C\_MI\_OperType configures to be in revertive mode. +- MTNPp\_C\_MI\_HoTime configures the hold-off timer. +- MTNPp\_C\_MI\_WTR configures the wait-to-restore timer. +- MTNPp\_C\_MI\_ExtCMD configures the protection group command. +- MTNPp\_C\_MI\_SDEnable configures the ability of a trail protection switching process to trigger protection switching upon SD. + +##### **Defects:** + +The function detects dFOP-PM, dFOP-NR and dFOP-TO defects as described in clause 6.1.6 in case the APS protocol is used. + +**Consequent actions:** None. + +##### **Defect correlations:** + +- cFOP-PM        ← dFOP-PM and (not CI\_SSF) +- cFOP-NR        ← dFOP-NR and (not CI\_SSF) +- cFOP-TO        ← dFOP-TO and (not dFOP-CM) and (not CI\_SSF) + +#### **9.4.1.2 MTNP trail termination function for trail protection (MTNPp\_TT)** + +The MTNPp\_TT function is used for trail protection and it is included to satisfy the modelling rules. Figure 9-16 shows the combination of the unidirectional sink and source functions to form a bidirectional function. + +![Diagram showing two MTNPp functions. The left one is a sink function with input MTNP_AP and output MTNPp_TCP. The right one is a source function with input MTNPp_TCP and output MTNP_AP. Both are labeled with G.8321(22).](ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg) + +The diagram illustrates two unidirectional MTNPp functions combined to form a bidirectional MTNPp\_TT function. On the left, an arrow points from 'MTNP\_AP' down into a triangle labeled 'MTNPp', and an arrow points from the bottom of the triangle down to 'MTNPp\_TCP'. On the right, an arrow points from 'MTNPp\_TCP' up into a triangle labeled 'MTNPp', and an arrow points from the top of the triangle up to 'MTNP\_AP'. Below the right triangle, the text 'G.8321(22)' is present. + +Diagram showing two MTNPp functions. The left one is a sink function with input MTNP\_AP and output MTNPp\_TCP. The right one is a source function with input MTNPp\_TCP and output MTNP\_AP. Both are labeled with G.8321(22). + +**Figure 9-16 – MTNPp\_TT** + +##### **9.4.1.2.1 MTNP trail protection termination source (MTNPp\_TT\_So)** + +The MTNPp\_TT\_So function relays the MTNP sequence at its MTNP\_AP input to its MTNPp\_TCP. + +The information flow and processing of the MTNPp\_TT\_So function is defined with reference to Figures 9-17 and 9-18. + +###### Symbol + +![Symbol diagram for MTNPp_TT_So function. It shows an input MTNP_AP pointing to a triangle labeled MTNPp, which then points to an output MTNPp_TCP. Below the output is the reference G.8321(22).](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) + +Symbol diagram for MTNPp\_TT\_So function. It shows an input MTNP\_AP pointing to a triangle labeled MTNPp, which then points to an output MTNPp\_TCP. Below the output is the reference G.8321(22). + +Figure 9-17 – MTNPp\_TT\_So function + +###### Interfaces + +Table 9-11 – MTNPp\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------|---------------------------------------------------------------| +| MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS | MTNPp_TCP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS | + +###### Processes + +![Process diagram for MTNPp_TT_So function. It shows three vertical arrows representing data flow from inputs AI_D, AI_CK, and AI_CS (under the heading MTNP_AP) to outputs CI_D, CI_CK, and CI_CS (under the heading MTNPp_TCP). Below the outputs is the reference G.8321(22).](09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg) + +Process diagram for MTNPp\_TT\_So function. It shows three vertical arrows representing data flow from inputs AI\_D, AI\_CK, and AI\_CS (under the heading MTNP\_AP) to outputs CI\_D, CI\_CK, and CI\_CS (under the heading MTNPp\_TCP). Below the outputs is the reference G.8321(22). + +Figure 9-18 – MTNPp\_TT\_So function processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.1.2.2 MTNP trail protection termination sink (MTNPp\_TT\_Sk) + +The information flow and processing of the MTNPp\_TT\_Sk function is defined with reference to Figures 9-19 and 9-20. + +###### Symbol + +![Symbol diagram for MTNPp_TT_Sk function. It shows a triangle labeled MTNPp. An arrow points from MTNPp_TCP (G.8321(22)) at the bottom into the triangle. An arrow points from the top of the triangle to MTNP_AP.](878d9539700bd792e7d12ad6f1203c5d_img.jpg) + +Symbol diagram for MTNPp\_TT\_Sk function. It shows a triangle labeled MTNPp. An arrow points from MTNPp\_TCP (G.8321(22)) at the bottom into the triangle. An arrow points from the top of the triangle to MTNP\_AP. + +Figure 9-19 – MTNPp\_TT\_Sk function + +###### Interfaces + +Table 9-12– MTNPp\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| MTNPp_TCP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS
MTNPp_CI_SSF | MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS
MTNP_AI_TSF | + +###### Processes + +![Process diagram for MTNPp_TT_Sk function. A large grey rectangle represents the function boundary. Inside, a box labeled 'Consequent actions' has an arrow pointing to it from CI_SSF. Above the box, an arrow labeled aTSF points to AI_TSF. To the right, four vertical arrows point from CI_D, CI_CK, and CI_CS to their respective AI counterparts (AI_D, AI_CK, AI_CS). The bottom of the rectangle is labeled MTNPp_TCP (G.8321(22)). The top of the rectangle is labeled MTNP_AP.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +Process diagram for MTNPp\_TT\_Sk function. A large grey rectangle represents the function boundary. Inside, a box labeled 'Consequent actions' has an arrow pointing to it from CI\_SSF. Above the box, an arrow labeled aTSF points to AI\_TSF. To the right, four vertical arrows point from CI\_D, CI\_CK, and CI\_CS to their respective AI counterparts (AI\_D, AI\_CK, AI\_CS). The bottom of the rectangle is labeled MTNPp\_TCP (G.8321(22)). The top of the rectangle is labeled MTNP\_AP. + +Figure 9-20 – MTNPp\_TT\_Sk function processes + +**Defects:** None. + +###### Consequent actions: + +The function shall perform the following consequent actions: + +aTSF ← CI\_SSF + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 9.4.1.3 MTNP trail protection adaptation function (MTNP/MTNPp\_A) + +The MTNP/MTNPp\_A function is used for trail protection defined in [ITU-T G.831]. + +The bidirectional MTNP/MTNPp\_A is performed by a co-located pair of MTNP/MTNPp\_A source (MTNP/MTNPp\_A\_So) and sink (MTNP/MTNPp\_A\_Sk) functions. + +##### 9.4.1.3.1 MTNP trail protection adaptation source (MTNP/MTNPp\_A\_So) + +The information flow and processing of the MTNP/MTNPp\_A\_So function is defined with reference to Figures 9-21 and 9-22. + +###### Symbol + +![Symbol diagram for MTNP/MTNPp_A_So function. It shows a trapezoidal block labeled 'MTNP/MTNPp'. An arrow labeled 'MTNPp_CP' points into the top of the block, and an arrow labeled 'MTNP_AP' points out from the bottom. The reference 'G.8321(22)' is noted below the output arrow.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +Symbol diagram for MTNP/MTNPp\_A\_So function. It shows a trapezoidal block labeled 'MTNP/MTNPp'. An arrow labeled 'MTNPp\_CP' points into the top of the block, and an arrow labeled 'MTNP\_AP' points out from the bottom. The reference 'G.8321(22)' is noted below the output arrow. + +Figure 9-21– MTNP/MTNPp\_A\_So function + +###### Interfaces + +Table 9-13 –MTNP/MTNPp\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS
MTNPp_CI_APS | MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS
MTNP_AI_APS | + +###### Processes + +![Process diagram for MTNP/MTNPp_A_So function. It shows a large grey rectangular block representing the function. Above the block, four labels 'CI_APS', 'CI_D', 'CI_CK', and 'CI_CS' are grouped under the heading 'MTNPp_CP'. Arrows point from each of these labels into the block. Below the block, four labels 'AI_APS', 'AI_D', 'AI_CK', and 'AI_CS' are grouped under the heading 'MTNP_AP'. Arrows point from the block to each of these labels. The reference 'G.8321(22)' is noted below the output labels.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +Process diagram for MTNP/MTNPp\_A\_So function. It shows a large grey rectangular block representing the function. Above the block, four labels 'CI\_APS', 'CI\_D', 'CI\_CK', and 'CI\_CS' are grouped under the heading 'MTNPp\_CP'. Arrows point from each of these labels into the block. Below the block, four labels 'AI\_APS', 'AI\_D', 'AI\_CK', and 'AI\_CS' are grouped under the heading 'MTNP\_AP'. Arrows point from the block to each of these labels. The reference 'G.8321(22)' is noted below the output labels. + +Figure 9-22 – MTNP/MTNPp\_A\_So function processes + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +##### 9.4.1.3.2 MTNP trail protection adaptation sink (MTNP/MTNPp\_A\_Sk) + +The information flow and processing of the MTNP/MTNPp\_A\_Sk function is defined with reference to Figures 9-23 and 9-24. + +###### Symbol + +![Symbol diagram for MTNP/MTNPp_A_Sk function. A trapezoidal block labeled 'MTNP/MTNPp' has an input arrow from 'MTNP_AP' at the bottom and an output arrow to 'MTNPp_CP' at the top. The reference 'G.8321(22)' is shown below the input.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Symbol diagram for MTNP/MTNPp\_A\_Sk function. A trapezoidal block labeled 'MTNP/MTNPp' has an input arrow from 'MTNP\_AP' at the bottom and an output arrow to 'MTNPp\_CP' at the top. The reference 'G.8321(22)' is shown below the input. + +Figure 9-23 – MTNP/MTNPp\_A\_Sk function + +###### Interfaces + +Table 9-14 –MTNP/MTNPp\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| MTNP_AP:
MTNP_AI_D
MTNP_AI_CK
MTNP_AI_CS
MTNP_AI_APS
MTNP_AI_TSF
MTNP_AI_TSD | MTNPp_CP:
MTNPp_CI_D
MTNPp_CI_CK
MTNPp_CI_CS
MTNPp_CI_APS
MTNPp_CI_SSF
MTNPp_CI_SSD | + +###### Processes + +![Process diagram for MTNP/MTNPp_A_Sk function. A large grey rectangle represents the function boundary. Inside, a white box labeled 'Consequent actions' receives inputs 'AI_TSF' and 'AI_TSD' from the bottom. It outputs 'aSSF' and 'aSSD' to 'CI_SSF' and 'CI_SSD' at the top. Other inputs from the bottom are 'AI_APS', 'AI_D', 'AI_CK', and 'AI_CS', which map to outputs 'CI_APS', 'CI_D', 'CI_CK', and 'CI_CS' at the top. The top outputs are grouped under 'MTNPp_CP'. The reference 'G.8321(22)' is shown at the bottom right.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +Process diagram for MTNP/MTNPp\_A\_Sk function. A large grey rectangle represents the function boundary. Inside, a white box labeled 'Consequent actions' receives inputs 'AI\_TSF' and 'AI\_TSD' from the bottom. It outputs 'aSSF' and 'aSSD' to 'CI\_SSF' and 'CI\_SSD' at the top. Other inputs from the bottom are 'AI\_APS', 'AI\_D', 'AI\_CK', and 'AI\_CS', which map to outputs 'CI\_APS', 'CI\_D', 'CI\_CK', and 'CI\_CS' at the top. The top outputs are grouped under 'MTNPp\_CP'. The reference 'G.8321(22)' is shown at the bottom right. + +Figure 9-24 –MTNP/MTNPp\_A\_Sk function processes + +**Defects:** None. + +###### Consequent actions: + +The function shall perform the following consequent actions: + +$aSSF \leftarrow AI\_TSF$ + +$aSSD \leftarrow AI\_TSD$ + +**Defect correlations:** None. + +**Performance monitoring:** None. + +# 10 MTN Section layer functions + +Figure 10-1 illustrates the MTN Section layer network and client layer adaptation functions. The information crossing the MTNSy (termination) connection point (MTNSy\_CP/TCP) is referred to as the MTNSy characteristic information (MTNSy\_CI) for $y=0$ (50G PHY), $y=1$ (100G PHY), $y=2$ (200G PHY) or $y=4$ (400G PHY). The information crossing the MTNS access point (MTNSy\_AP) is referred to as the MTNSy adapted information (MTNSy\_AI). + +![Figure 10-1: MTN Section layer network and client layer adaptation functions diagram. At the top, two connection points, MTNP_CP and COMMS_CP, are shown with arrows labeled 'p' and 'm' respectively, pointing down to a central horizontal bar labeled 'MTNSy-m/MTNP&COMMS'. Below this bar, multiple MTNSy_AP points (labeled MTNSy_AP[1], MTNSy_AP[2], ..., MTNSy_AP[m]) are shown, each with a downward arrow to a triangle labeled 'MTNSy'. From each 'MTNSy' triangle, a downward arrow points to a label 'MTNSy_TCP'. The diagram is labeled G.8321(22) at the bottom right.](ec3647789b5c38fb686f2a0833324e79_img.jpg) + +Figure 10-1: MTN Section layer network and client layer adaptation functions diagram. At the top, two connection points, MTNP\_CP and COMMS\_CP, are shown with arrows labeled 'p' and 'm' respectively, pointing down to a central horizontal bar labeled 'MTNSy-m/MTNP&COMMS'. Below this bar, multiple MTNSy\_AP points (labeled MTNSy\_AP[1], MTNSy\_AP[2], ..., MTNSy\_AP[m]) are shown, each with a downward arrow to a triangle labeled 'MTNSy'. From each 'MTNSy' triangle, a downward arrow points to a label 'MTNSy\_TCP'. The diagram is labeled G.8321(22) at the bottom right. + +Figure 10-1 – MTN Section layer network and client layer adaptation functions + +## 10.1 Connection functions + +Not applicable. + +## 10.2 Termination functions + +### 10.2.1 MTNSy Trail Termination function (MTNSy\_TT, $y = 0,1,2,4$ ) + +The MTNSy trail termination function (MTNSy\_TT) terminates the section monitoring overhead of each MTNS PHY overhead to determine the status of the MTNS trail. Figure 10-2 shows the combination of the unidirectional sink and source functions to form a bidirectional function for $y=0$ (50G PHY), $y=1$ (100G PHY), $y=2$ (200G PHY) or $y=4$ (400G PHY). + +![Figure 10-2: MTNSy_TT function diagram. It shows two triangles labeled 'MTNSy'. The left triangle has an arrow labeled 'MTNSy_AP' pointing down to it and an arrow labeled 'MTNSy_TCP' pointing down from it. The right triangle has an arrow labeled 'MTNSy_TCP' pointing up to it and an arrow labeled 'MTNSy_AP' pointing up from it. A horizontal arrow labeled 'MTNSy_RP' points from the right triangle to the left triangle. The diagram is labeled G.8321(22) at the bottom right.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +Figure 10-2: MTNSy\_TT function diagram. It shows two triangles labeled 'MTNSy'. The left triangle has an arrow labeled 'MTNSy\_AP' pointing down to it and an arrow labeled 'MTNSy\_TCP' pointing down from it. The right triangle has an arrow labeled 'MTNSy\_TCP' pointing up to it and an arrow labeled 'MTNSy\_AP' pointing up from it. A horizontal arrow labeled 'MTNSy\_RP' points from the right triangle to the left triangle. The diagram is labeled G.8321(22) at the bottom right. + +Figure 10-2 – MTNSy\_TT function + +#### 10.2.1.1 MTNSy trail termination source function (MTNSy\_TT\_So, $y = 0,1,2,4$ ) + +The MTNSy\_TT\_So function adds PHY-related section monitoring overhead – i.e., the RPF indication – to the first FlexE instance signal in a PHY at its MTNSy\_AP. + +The information flow and processing of the MTNSy\_TT\_So function ( $y = 0,1,2,4$ ) is defined with reference to Figure 10-3. + +##### Symbol + +![Symbol diagram for MTNSy_TT_So function. It shows a downward arrow from MTNSy_AP to an inverted triangle labeled MTNSy. A horizontal arrow from MTNSy_RP points to the right side of the triangle. A downward arrow from the bottom vertex of the triangle points to MTNSy_TCP. Below MTNSy_TCP is the reference text G.8321(22).](ae0a735d106290c594b0bafb1f5e72e7_img.jpg) + +Symbol diagram for MTNSy\_TT\_So function. It shows a downward arrow from MTNSy\_AP to an inverted triangle labeled MTNSy. A horizontal arrow from MTNSy\_RP points to the right side of the triangle. A downward arrow from the bottom vertex of the triangle points to MTNSy\_TCP. Below MTNSy\_TCP is the reference text G.8321(22). + +Figure 10-3 – MTNSy\_TT\_So function + +##### Interfaces + +Table 10-1 – MTNSy\_TT\_So inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| +| MTNSy_AP :
MTNSy_AI_CK
MTNSy_AI_D[1.. q ] (Note)
MTNSy_AI_FS
MTNSy_AI_MFS

MTNSy_RP:
MTNSy_RI_RPF | MTNSy_TCP :
MTNSy_CI_CK
MTNSy_CI_D[1.. q ] (Note)
MTNSy_CI_FS
MTNSy_CI_MFS | +| NOTE – $q=y$ if $y=(1, 2, 4)$ , or $q=1$ if $y=0$ . | | + +##### Processes + +The processes associated with the MTNSy\_TT\_So functions are as depicted in Figure 10-4 below. + +As described in clause 7.1 of [ITU-T G.8312] the signal comprises $q$ FlexE instances per PHY. For MTNS0 ( $y=0$ ), a single 50G FlexE instance is carried over the 50G PHY (i.e., $q=1$ ). For MTNSy with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are interleaved within the $[y \times 100G]$ PHY (i.e., $q=y$ ). + +![Diagram showing MTNSy_TT_So processes for two cases: y=0,1 and y=2,4. The left diagram for y=0,1 shows MTNSy_AP(y=0,1) inputs (AI_D, AI_CK, AI_FS, AI_MFS) entering a functional block labeled 'Insert RPF'. The block also receives RI_RPF from MTNSy_RP. The outputs are CI_D, CI_CK, CI_FS, CI_MFS, which form MTNSy_TCP(y=0,1). The right diagram for y=2,4 shows MTNSy_AP(y=2,4) inputs (AI_D[2..y], AI_D[1], AI_CK, AI_FS, AI_MFS) entering a functional block labeled 'Insert RPF'. The block also receives RI_RPF from MTNSy_RP. The outputs are CI_D[2..y], CI_D[1], CI_CK, CI_FS, CI_MFS, which form MTNSy_TCP(y=2,4). Both diagrams include the reference text G.8321(22).](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +Diagram showing MTNSy\_TT\_So processes for two cases: y=0,1 and y=2,4. The left diagram for y=0,1 shows MTNSy\_AP(y=0,1) inputs (AI\_D, AI\_CK, AI\_FS, AI\_MFS) entering a functional block labeled 'Insert RPF'. The block also receives RI\_RPF from MTNSy\_RP. The outputs are CI\_D, CI\_CK, CI\_FS, CI\_MFS, which form MTNSy\_TCP(y=0,1). The right diagram for y=2,4 shows MTNSy\_AP(y=2,4) inputs (AI\_D[2..y], AI\_D[1], AI\_CK, AI\_FS, AI\_MFS) entering a functional block labeled 'Insert RPF'. The block also receives RI\_RPF from MTNSy\_RP. The outputs are CI\_D[2..y], CI\_D[1], CI\_CK, CI\_FS, CI\_MFS, which form MTNSy\_TCP(y=2,4). Both diagrams include the reference text G.8321(22). + +Figure 10-4 – MTNSy\_TT\_So processes; $y = 0,1,2,4$ + +**Insert RPF:** The remote PHY fault indication is inserted in the RPF bit position of the first FlexE instance input signal of the PHY as described in clause 9.2.6 of [ITU-T G.8312]. Its value is derived from reference point MTNSy\_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. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 10.2.1.2 MTNSy trail termination sink function (MTNSy\_TT\_Sk, y = 0,1,2,4) + +The MTNSy\_TT\_Sk function reports the state of a PHY trail in the MTNS. It extracts PHY-related MTNS monitoring overhead – i.e., the RPF signal – from the first FlexE instance signal at its MTNSy\_TCP, detects for the RPF defect, and forwards the defect information as backward indication to the companion MTNSy\_TT\_So function. + +The information flow and processing of the MTNSy\_TT\_Sk function (y = 0,1,2,4) is defined with reference to Figure 10-5. + +##### Symbol + +![Symbol diagram for MTNSy_TT_Sk function. A central triangle labeled MTNSy has four arrows pointing to it from the top (MTNSy_AP), bottom (MTNSy_TCP), left (MTNSy_TT_So_MP), and right (MTNSy_RP). The text G.8321(22) is located to the right of the triangle.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +Symbol diagram for MTNSy\_TT\_Sk function. A central triangle labeled MTNSy has four arrows pointing to it from the top (MTNSy\_AP), bottom (MTNSy\_TCP), left (MTNSy\_TT\_So\_MP), and right (MTNSy\_RP). The text G.8321(22) is located to the right of the triangle. + +Figure 10-5 – MTNSy\_TT\_Sk function + +##### Interfaces + +Table 10-2 – MTNSy\_TT\_Sk inputs and outputs + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MTNSy_TCP :
MTNSy_CI_CK
MTNSy_CI_D[1..q] (Note)
MTNSy_CI_FS
MTNSy_CI_MFS
MTNSy_CI_CRCerr[1..q] (Note)
MTNSy_CI_SSF | MTNSy_AP :
MTNSy_AI_CK
MTNSy_AI_D[1..q] (Note)
MTNSy_AI_FS
MTNSy_AI_MFS
MTNSy_AI_CRCerr[1..q] (Note)
MTNSy_AI_TSF
MTNSy_RP:
MTNSy_RI_RPF
MTNSy_TT_Sk_MP:
MTNSy_TT_Sk_MI_cRPF
MTNSy_TT_Sk_MI_cSSF | +| NOTE – q= y if y= (1, 2, 4), or q= 1 if y = 0. | | + +##### Processes + +The processes associated with the MTNSy\_TT\_Sk functions are as depicted in Figure 10-6 below. + +As described in clause 7.1 of [ITU-T G.832] the signal comprises $q$ FlexE instances per PHY. For MTNS0 ( $y=0$ ), a single 50G FlexE instance is carried over the 50G PHY (i.e., $q=1$ ). For MTNSy with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are interleaved within the $[y \times 100G]$ PHY (i.e., $q=y$ ). + +![Figure 10-6 – MTNSy_TT_Sk processes; y = 0,1,2,4. The diagram shows two process flowcharts for MTNSy_TT_Sk. The left chart is for MTNSy_AP(y=0,1) and MTNSy_TCP(y=0,1). The right chart is for MTNSy_AP(y=2,4) and MTNSy_TCP(y=2,4). Both charts show the flow of information from input signals (CI_SSF, CI_CRCerr, CI_CK, CI_FS, CI_MFS, CI_D) through 'Defect correlations', 'Extract RPF', and 'Consequent actions' blocks to output signals (aRPF, aTSF, RI_RPF, MI_cRPF, MI_cSSF).](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates two process flowcharts for MTNSy\_TT\_Sk. The left chart is for MTNSy\_AP(y=0,1) and MTNSy\_TCP(y=0,1). The right chart is for MTNSy\_AP(y=2,4) and MTNSy\_TCP(y=2,4). Both charts show the flow of information from input signals (CI\_SSF, CI\_CRCerr, CI\_CK, CI\_FS, CI\_MFS, CI\_D) through 'Defect correlations', 'Extract RPF', and 'Consequent actions' blocks to output signals (aRPF, aTSF, RI\_RPF, MI\_cRPF, MI\_cSSF). The right chart also includes additional input and output signals for multiple FlexE instances (1..y, [1], [2..y]). + +Figure 10-6 – MTNSy\_TT\_Sk processes; y = 0,1,2,4. The diagram shows two process flowcharts for MTNSy\_TT\_Sk. The left chart is for MTNSy\_AP(y=0,1) and MTNSy\_TCP(y=0,1). The right chart is for MTNSy\_AP(y=2,4) and MTNSy\_TCP(y=2,4). Both charts show the flow of information from input signals (CI\_SSF, CI\_CRCerr, CI\_CK, CI\_FS, CI\_MFS, CI\_D) through 'Defect correlations', 'Extract RPF', and 'Consequent actions' blocks to output signals (aRPF, aTSF, RI\_RPF, MI\_cRPF, MI\_cSSF). + +Figure 10-6 – MTNSy\_TT\_Sk processes; $y = 0,1,2,4$ + +**Extract RPF:** The remote PHY fault indication shall be recovered from the RPF bit position in the overhead field of the first 50G or 100G FlexE instance in the PHY as described in clause 9.2.6 of [ITU-T G.832]. It shall be used for RPF defect detection. + +##### Defects + +The function shall detect the dRPF defect. + +**dRPF:** If the extracted RPF is "1" in an overhead frame with good CRC (CRCerr = 0), dRPF shall be set to true; otherwise, dRPF shall be set to false; dRPF 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 equipment management function (EMF). + +cSSF $\leftarrow$ CI\_SSF + +cRPF ← dRPF and (not CI\_SSF) + +**Performance monitoring:** None. + +## 10.3 Adaptation functions + +### 10.3.1 MTNSy-m to MTNP adaptation function (MTNSy-m/MTNP\_A, y = 0,1,2,4) + +The MTNSy-m to MTNP adaptation functions perform the adaptation between the MTNS layer adapted information of a group of *m* PHYs and the characteristic information of *p* MTNP tributary signals for *y*= 0 (50G PHYs), *y*= 1 (100G PHYs), *y*= 2 (200G PHYs) or *y*=4 (400G PHYs). The nominal bit rate of the MTNP tributary signal characteristic information at the MTNP connection point could be a multiple of 5.15625 Gbit/s. + +The MTNSy-m to MTNP adaptation functions contains the MTNS ECC function in itself, such as the MTNSy-m to MCC adaptation functions as defined in [ITU-T G.7712]. + +#### 10.3.1.1 MTNSy-m to MTNP adaptation source function (MTNSy-m/MTNP\_A\_So, y = 0,1,2,4) + +The information flow and processing of the MTNSy-m/MTNP\_A\_So function (*y*= 0,1,2,4) is defined with reference to Figure 10-7. + +##### Symbol + +![Diagram of the MTNSy-m/MTNP_A_So function. A central trapezoidal block labeled 'MTNSy-m/MTNP&COMMS' has multiple input and output interfaces. On the left, 'MTNSy-m/MTNP_A_So_MP' enters the block. On the right, 'MTNS_TP' enters the block. At the top, 'MTNP_CP' (labeled with 'p') and 'COMMS_CP' (labeled with 'm') are shown with arrows pointing into the block. At the bottom, multiple outputs exit the block, labeled 'MTNSy_AP[1]' through 'MTNSy_AP[m]', with an ellipsis between them. The reference 'G.8321(22)' is noted at the bottom right.](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +Diagram of the MTNSy-m/MTNP\_A\_So function. A central trapezoidal block labeled 'MTNSy-m/MTNP&COMMS' has multiple input and output interfaces. On the left, 'MTNSy-m/MTNP\_A\_So\_MP' enters the block. On the right, 'MTNS\_TP' enters the block. At the top, 'MTNP\_CP' (labeled with 'p') and 'COMMS\_CP' (labeled with 'm') are shown with arrows pointing into the block. At the bottom, multiple outputs exit the block, labeled 'MTNSy\_AP[1]' through 'MTNSy\_AP[m]', with an ellipsis between them. The reference 'G.8321(22)' is noted at the bottom right. + +**Figure 10-7 – MTNSy-m/MTNP\_A\_So function** + +##### Interfaces + +**Table 10-3 – MTNSy-m/MTNP\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| p × MTNP_CP :
MTNP_CI_CK[1.. p ]
MTNP_CI_D[1.. p ]
m × COMMS_CP :
COMMS_CI_D[1.. m ]
MTNS_TP :
MTNS_TI_CK | m × MTNSy_AP :
MTNSy_CI_CK[1.. m ]
MTNSy_CI_D[1.. m ][1.. q ] (Note)
MTNSy_CI_FS[1.. m ]
MTNSy_CI_MFS[1.. m ]
m × COMMS_CP :
COMMS_CI_CK[1.. m ] | + +**Table 10-3 – MTNSy-m/MTNP\_A\_So inputs and outputs** + +| Input(s) | Output(s) | +|-----------------------------------------------------------|-----------| +| MTNSy-m/MTNP_A_So_MP: | | +| MTNSy-m/MTNP_A_So_MI_TxCC | | +| MTNSy-m/MTNP_A_So_MI_TxCCA | | +| MTNSy-m/MTNP_A_So_MI_TxCCB | | +| MTNSy-m/MTNP_A_So_MI_TxCR | | +| MTNSy-m/MTNP_A_So_MI_TxCA | | +| MTNSy-m/MTNP_A_So_MI_TxTI[1..m] | | +| MTNSy-m/MTNP_A_So_MI_TxGID | | +| MTNSy-m/MTNP_A_So_MI_TxFlexEMAP | | +| NOTE – $q = y$ if $y = (1, 2, 4)$ or $q = 1$ if $y = 0$ . | | + +##### **Processes** + +The processes associated with the MTNSy-m/MTNP\_A\_So functions are as depicted in Figure 10-8. + +As described in clause 7.1 of [ITU-T G.8312] each one of the $m$ PHYs in the MTNS group carries $q$ FlexE instances, so that there are $n$ FlexE instances in the group, with $n = [m \times q]$ . For MTNS0-m ( $y=0$ ), a single 50G FlexE instance is carried over each 50G PHY (i.e., $q=1$ ). For MTNSy-m with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are carried within each $[y \times 100G]$ PHY (i.e., $q=y$ ). + +![Figure 10-8 – MTNSy-m/MTNP_A_So processes; y = 0,1,2,4. This block diagram illustrates the internal architecture of the MTNSy-m/MTNP_A_So process. At the top, p x MTNP_CP input ports (CL_D[1], CL_CK[1] to CL_D[p], CL_CK[p]) feed into 'Rate adaptation' blocks. These blocks output CK and FS signals to a central 'Multiplexer'. The Multiplexer has n output slots (1 to n), where n = q x m. Each slot contains a series of 'Insert' blocks: 'Insert client calendar', 'Insert GID' (receiving MI_TxGID), 'Insert IID' (receiving MI_TxFlexEMAP), 'Insert FlexE MAP' (receiving OMFS and MI_TxFlexEMAP), 'Insert reserved OH', and 'Insert management channel' (receiving D_COM[1] and CK_COM). The Multiplexer outputs (1 to n) feed into 'm x MTNSy_AP' output ports (AL_D[1..q], AL_FS[1], AL_CK[1], AL_MFS[1] to AL_D[m], AL_FS[m], AL_CK[m], AL_MFS[m]). On the right, 'COMMS clock generation' receives CK_COM and D_COM[1..m] and provides a clock to 'Clock generation' (receiving MTNS_TI_CK) and 'FS and OMFS generation' (receiving FS). 'FS and OMFS generation' outputs FS and OMFS signals. Various MI signals (MI_TxCC, MI_TxCCA, MI_TxCCB, MI_TxCR, MI_TxCA, MI_TxGID, MI_TxFlexEMAP) are shown as inputs to the 'Insert' blocks and the 'FS and OMFS generation' block. The diagram is labeled G.8321(22) and has vertical labels MTNS_TP and MTNSy-m/MTNP_A_So_MP on the right side.](701bc79e78b382bcfd3ba85597dbb9c3_img.jpg) + +Figure 10-8 – MTNSy-m/MTNP\_A\_So processes; y = 0,1,2,4. This block diagram illustrates the internal architecture of the MTNSy-m/MTNP\_A\_So process. At the top, p x MTNP\_CP input ports (CL\_D[1], CL\_CK[1] to CL\_D[p], CL\_CK[p]) feed into 'Rate adaptation' blocks. These blocks output CK and FS signals to a central 'Multiplexer'. The Multiplexer has n output slots (1 to n), where n = q x m. Each slot contains a series of 'Insert' blocks: 'Insert client calendar', 'Insert GID' (receiving MI\_TxGID), 'Insert IID' (receiving MI\_TxFlexEMAP), 'Insert FlexE MAP' (receiving OMFS and MI\_TxFlexEMAP), 'Insert reserved OH', and 'Insert management channel' (receiving D\_COM[1] and CK\_COM). The Multiplexer outputs (1 to n) feed into 'm x MTNSy\_AP' output ports (AL\_D[1..q], AL\_FS[1], AL\_CK[1], AL\_MFS[1] to AL\_D[m], AL\_FS[m], AL\_CK[m], AL\_MFS[m]). On the right, 'COMMS clock generation' receives CK\_COM and D\_COM[1..m] and provides a clock to 'Clock generation' (receiving MTNS\_TI\_CK) and 'FS and OMFS generation' (receiving FS). 'FS and OMFS generation' outputs FS and OMFS signals. Various MI signals (MI\_TxCC, MI\_TxCCA, MI\_TxCCB, MI\_TxCR, MI\_TxCA, MI\_TxGID, MI\_TxFlexEMAP) are shown as inputs to the 'Insert' blocks and the 'FS and OMFS generation' block. The diagram is labeled G.8321(22) and has vertical labels MTNS\_TP and MTNSy-m/MTNP\_A\_So\_MP on the right side. + +**Figure 10-8 – MTNSy-m/MTNP\_A\_So processes; y = 0,1,2,4** + +**Clock generation:** The function shall generate a local FlexE instance clock of "16383/16384 × 103 125 000 kHz ± 100 ppm" if y=(1,2,4) or "16383/16384 × 51 562 500 kHz ± 100 ppm" if y=0, from the synchronisation timing information clock input (TI\_CK) or, if the TI\_CK is absent, from a free-running oscillator. + +**FS and MFS generation:** The function shall generate FlexE frame start (FS) and FlexE overhead multi-frame start (MFS) signals as described in clause 7.3.1 of [ITU-T G.8312]. + +**Rate adaptation:** The function shall adjust the MTNP signals applied at the MTNP\_CP input ports to the required rate using the MTNS layer clock through insertion of IDLE blocks and deletion of IDLE and Ordered Set blocks as described in clause 7.2 of [ITU-T G.8312]. + +**Multiplexer:** The function assigns the individual MTNP to specific calendar slots of the MTNSy-m payload area as defined by the active client calendar. The active client calendar is the calendar configuration in use and is derived by the configuration provided by either the MI\_TxCCA or the MI\_TxCCB as indicated by the MI\_TxCC, as described in clause 9.2.3 of [ITU-T G.8312]. + +NOTE – It is assumed that the client calendar configuration protocol is implemented by the EMF. + +**Insert client calendar:** The function shall insert the calendar configuration information into the FlexE instance frame overhead fields as defined in clause 9.2.3 of [ITU-T G.8312]. The "calendar configuration in use" overhead bits are set as configured by the MI\_TxCC; the "client carried calendar A/B" overhead fields are set extracting the sub-calendar information from the configured MI\_TxCCA and MI\_TxCCB. The "client switch request" and "client switch acknowledged" overhead bits are set as configure by the MI\_TxCR and MI\_TxCA. + +**Insert GID:** The group identifier (GID) is inserted in the FlexE Group Number field of each FlexE instance overhead. Its value is configured via the MI\_TxGID. The group number format is described in clause 9.2.2 of [ITU-T G.8312]. + +**Insert IID:** The instance identifier (IID) is inserted in the FlexE instance number field of each FlexE instance overhead. Its value for each FlexE instance in the group is a unique one and can be configured via the MI\_TxFlexEMAP. The FlexE instance Number format and its relationship with each PHY Number is described in clause 9.2.2 of [ITU-T G.8312]. + +**Insert FlexE MAP:** The FlexE MAP is inserted in the OMF and FlexE MAP fields of each FlexE instance overhead as specified in clause 9.2.2 of [ITU-T G.8312] using the multiframe structure specified in clause 9.2.1 of [ITU-T G.8312]. Its value is configured via the MI\_TxFlexEMAP. + +**Reserved OH:** The function shall insert "all zero" in the reserved overhead field and in bit 36 to 63 of the FlexE instance overhead in row 1 as described in clause 9.2.7 of [ITU-T G.8312]. + +**Insert Management channel:** The function shall perform MCC insertion as described in clause 8.2.3.1. The trail trace identifier (TTI) is carried over the MTNS message communication channel as specified in Annex A of [ITU-T G.8350]. The TTI value to be transmitted is configured via MI\_TxTI. The TTI is sent with a 10s fixed interval. + +**COMMS clock generation:** The function shall generate the COMMS clock (CI\_CK\_COM) by dividing the local FlexE instance clock (CK) by a factor of 3/163688. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +#### 10.3.1.2 MTNSy-m to MTNP adaptation sink function (MTNSy-m/MTNP\_A\_Sk, $y = 0, 1, 2, 4$ ) + +The information flow and processing of the MTNSy-m/MTNP\_A\_Sk function ( $y = 0, 1, 2, 4$ ) is defined with reference to Figure 10-9. + +As described in clause 7.1 of [ITU-T G.8312] each one of the $m$ PHYS in the MTNS group carries $q$ FlexE instances, so that there are $n$ FlexE instances in the group, with $n = [m \times q]$ . For MTNS0-m ( $y=0$ ), a single 50G FlexE instance is carried over each 50G PHY (i.e., $q=1$ ). For MTNSy-m with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are carried within each $[y \times 100G]$ PHY (i.e., $q=y$ ). + +##### Symbol + +![Functional block diagram of the MTNSy-m/MTNP_A_Sk function. A trapezoidal block is labeled 'MTNSy-m/MTNP&COMMS'. From the bottom, multiple arrows enter the block, labeled 'MTNSy_AP[1]', a series of dots, and 'MTNSy_AP[m]'. From the top, two arrows exit: one labeled 'p' leading to 'MTNP_CP' and another labeled 'm' leading to 'COMMS_CP'. A single-headed arrow exits from the right side of the block, labeled 'MTNSy-m/MTNP_A_Sk_MP'. The source reference 'G.8321(22)' is at the bottom right.](0ed8d001e745e9b2bb07fc63eb8525d5_img.jpg) + +Functional block diagram of the MTNSy-m/MTNP\_A\_Sk function. A trapezoidal block is labeled 'MTNSy-m/MTNP&COMMS'. From the bottom, multiple arrows enter the block, labeled 'MTNSy\_AP[1]', a series of dots, and 'MTNSy\_AP[m]'. From the top, two arrows exit: one labeled 'p' leading to 'MTNP\_CP' and another labeled 'm' leading to 'COMMS\_CP'. A single-headed arrow exits from the right side of the block, labeled 'MTNSy-m/MTNP\_A\_Sk\_MP'. The source reference 'G.8321(22)' is at the bottom right. + +**Figure 10-9 – MTNSy-m/MTNP\_A\_Sk function** + +##### Interfaces + +**Table 10-4 – MTNSy-m/MTNP\_A\_Sk inputs and outputs** + +| Input(s) | Output(s) | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| m \times \text{MTNSy\_AP} :
MTNSy_AI_CK[1..m] (Note 1)
MTNSy_AI_D[1..m][1..q] (Note 2)
MTNSy_AI_FS[1..m]
MTNSy_AI_MFS[1..m]
MTNSy_AI_CRCerr[1..m][1..q] (Note 2)
MTNSy_AI_TSF[1..m] | p \times \text{MTNP\_CP} :
MTNP_CI_CK[1..p]
MTNP_CI_D[1..p]
MTNP_CI_SSF[1..p]

m \times \text{COMMS\_CP} :
COMMS_CI_D[1..m]
COMMS_CI_CK[1..m]
COMMS_CI_SSF[1..m]

MTNSy-m/MTNP_A_Sk_MP:
MTNSy-m/MTNP_A_Sk_MI_AcCC
MTNSy-m/MTNP_A_Sk_MI_AcCR
MTNSy-m/MTNP_A_Sk_MI_AcCA
MTNSy-m/MTNP_A_Sk_MI_AcCCA (Note 3)
MTNSy-m/MTNP_A_Sk_MI_AcCCB (Note 3)
MTNSy-m/MTNP_A_Sk_MI_cCCM[1..p]
MTNSy-m/MTNP_A_Sk_MI_cLOBA[1..p]
MTNSy-m/MTNP_A_Sk_MI_AcGID[1..n]
MTNSy-m/MTNP_A_Sk_MI_AcIID[1..n]
MTNSy-m/MTNP_A_Sk_MI_AcFlexEMAP[1..n]
MTNSy-m/MTNP_A_Sk_MI_cLOL
MTNSy-m/MTNP_A_Sk_MI_cFMM
MTNSy-m/MTNP_A_Sk_MI_cGIDM
MTNSy-m/MTNP_A_Sk_MI_AcTI[1..m]
MTNSy-m/MTNP_A_Sk_MI_cTIM | +| NOTE 1 – It needs only to select one clock of them to use, e.g., MTNSy_AI_CK[1]. | | +| NOTE 2 – $q=y$ if $y=(1, 2, 4)$ , or $q=1$ if $y=0$ . | | +| NOTE 3 – MI_AcCCA or MI_AcCCB each are $n$ sets of $z \times 16$ -bit values, with $z=10$ if $y=0$ or $z=20$ if $y=(1,2,4)$ . | | + +##### Processes + +The processes associated with the MTNSy-m/MTNP\_A\_Sk functions are as depicted in Figure 10-10 below, for $y=0$ (50GBASE-R PHY), $y=1$ (100GBASE-R PHY), $y=2$ (200GBASE-R PHY) or $y=4$ (400GBASE-R PHY). As described in clause 7.1 of [ITU-T G.8312] the signal comprises $q$ FlexE instances per PHY. For MTNS0 ( $y=0$ ), a single 50G FlexE instance is carried over the PHY (i.e., $q=1$ ). For MTNSy with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are interleaved within a PHY (i.e., $q=y$ ). + +![Figure 10-10: Block diagram of MTNSy-m/MTNP_A_Sk processes. The diagram shows a complex signal processing architecture. On the left, multiple inputs (AL_D[1..q], AL_FS[1], etc.) enter through a series of blocks including 'Rate adaptation', 'Elastic store', and 'Demultiplexing'. A 'Clock generation' block interacts with the elastic stores. The demultiplexed signals pass through 'Extract client calendar' and 'Reorder and deskew' blocks. Below these, parallel processing paths for 'Management channel', 'Extract FlexE MAP', 'Extract IID', and 'Extract GID' are shown for 'n' instances. These feed into a 'Defect generation' block and a 'Defect correlations' block on the right. Outputs include signals to 'MTNP_CP' and 'COMMS_CP' at the top, and various management information (MI) signals on the right side (e.g., MI_AcGID[1..n], MI_cTIM). The diagram is labeled with G.8321(22) at the bottom right.](cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg) + +Figure 10-10: Block diagram of MTNSy-m/MTNP\_A\_Sk processes. The diagram shows a complex signal processing architecture. On the left, multiple inputs (AL\_D[1..q], AL\_FS[1], etc.) enter through a series of blocks including 'Rate adaptation', 'Elastic store', and 'Demultiplexing'. A 'Clock generation' block interacts with the elastic stores. The demultiplexed signals pass through 'Extract client calendar' and 'Reorder and deskew' blocks. Below these, parallel processing paths for 'Management channel', 'Extract FlexE MAP', 'Extract IID', and 'Extract GID' are shown for 'n' instances. These feed into a 'Defect generation' block and a 'Defect correlations' block on the right. Outputs include signals to 'MTNP\_CP' and 'COMMS\_CP' at the top, and various management information (MI) signals on the right side (e.g., MI\_AcGID[1..n], MI\_cTIM). The diagram is labeled with G.8321(22) at the bottom right. + +**Figure 10-10 –MTNSy-m/MTNP\_A\_Sk processes; $y = 0,1,2,4$** + +**Group OH extraction:** The function shall extract and process the MTNS group overhead (GID, IID, FlexE MAP and client calendar) from each of the $n$ FlexE instances signals in the FlexE group (incoming from $m$ MTNSy\_AI) as defined in clause 9.2 of [ITU-T G.8312]. + +**Extract and process GID:** The GID field shall be read from the "FlexE Group Number" field of each FlexE instance overhead as described in clause 9.2.2 of [ITU-T G.8312] and processed as specified in clause 8.2.1.1. The accepted GID values are available at the MP (MI\_AcGID[i]) and are used for dGIDM defect detection. + +**Extract and process IID:** The IID fields shall be read from the "FlexE instance Number" field of each FlexE instance overhead as described in clause 9.2.2 of [ITU-T G.8312] and processed as specified in clause 8.2.1.2. The accepted IID values are available at the MP (MI\_AcIID[i]) and are used for dFMM defect detection. + +**Extract and process FlexE MAP:** The FlexE MAP fields shall be read from each FlexE instance overhead as described in clause 9.2.2 of [ITU-T G.8312] and processed as specified in clause 8.2.1.3 for 100G FlexE instance and in clause 8.2.1.4 for 50G FlexE instance. The + +accepted FlexE MAP values are available at the MP (MI\_AcFlexEMAP[i]) and are used for dFMM defect detection. + +**Management communication channel:** The function shall perform MCC extraction as described in clause 8.2.3.2. The trail trace identifier (TTI) is extracted via MCC as specified in Annex A of [ITU-T G.8350]. The accepted value is used to support dTIM detection and is made available to the EMF as MI\_AcTI. + +**Reorder and deskew:** The function shall include reordering and deskewing processes. + +**Reordering:** The process shall reorder $n$ FlexE instances in the FlexE group based on IID, per clause 9.2.2 of [ITU-T G.8312]. + +**Deskewing:** The process shall compensate the skew between the $n$ FlexE instances based on FlexE frame start indication (alignment markers) as described in clause 9.2.1 of [ITU-T G.8312]. The alignment process shall establish the delay compensation, compensating the differential delay between the FlexE instances. The compensation between FlexE instances is achieved by an elastic store per FlexE instance. Each FlexE instance signal shall be written into an elastic store with the FlexE frame start indication. Each elastic store shall be capable of compensating at least 300 ns of absolute differential delay between $n$ FlexE instances. 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 $n$ FlexE instance 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 FlexE instances exceeds the maximum delay that can be compensated, the OLA state shall be entered. + +**FlexE OH client calendar:** The calendar information defined in clause 9.2.3 of [ITU-T G.8312] shall be read from the calendar configuration in use (C), client calendar A and B, calendar switch request (CR) and calendar switch acknowledge (CA) overhead fields extracted from each FlexE instance overhead and processed as specified in clause 8.2.1.5. + +**Calendar configuration in use overhead (C):** The accepted "calendar configuration in use" value is available at the MP (MI\_AcCC) to indicate the active calendar and is used for dCCM[j] defects detection. + +**Client calendar A and B overheads:** The accepted "client calendar A" and "client calendar B" calendar slot information values are available at the MP (MI\_AcCCA[1..n][1..z] and MI\_AcCCB[1..n][1..z]) and used for dCCM[j] defects detection. For each one of the $n$ FlexE instances there are $z$ MI\_AcCCA 16-bit values and $z$ MI\_AcCCB 16-bit values where $z$ is the number of 5G calendar slots in the sub-calendar with $z=10$ for 50G FlexE instance ( $y=0$ ) or $z=20$ for 100G FlexE instance ( $y=1,2,4$ ). + +**Calendar switch request overhead (CR):** The accepted "calendar switch request" value is available at the MP (MI\_AcCR). + +**Calendar switch acknowledge overhead (CA):** The accepted "calendar switch acknowledge" value is available at the MP (MI\_AcCA). + +**Demultiplexing:** The function activates the MTNP and assigns the calendar slots of the MTNSy-m payload area to the individual MTNP as defined by the active client calendar. The active client calendar is the client calendar in use and is derived by the configuration provided by either the MI\_ExCCA[1..n] or the MI\_ExCCB[1..n] as indicated by the MI\_ExCC, as described in clause 9.2.3 of [ITU-T G.8312]. + +NOTE – It is assumed that the client calendar configuration protocol is controlled by the EMF. + +**Clock generation:** The function shall generate each MTNP clock (MTNP\_CI\_CK[j]) from a free-running oscillator or the MTNSy-m group clock with a nominal bit rate of approximately $[s \times 5\ 156]$ + +250 kbit/s], with $s$ corresponding to the configured number of calendar slots the MTNP tributary port $j$ is extracted from. + +**Rate adaptation:** The function shall adjust the demapped MTNP to the required rate through insertion of IDLE blocks or deletion of IDLE or ordered set blocks as described in clause 7.2 of [ITU-T G.8312]. + +**Replacement signal generation:** When aAIS[ $j$ ] is true, the function shall provide for a replacement signal of MTNP and clock generation process that generates a stream of local fault sequence ordered sets as specified in clause 10.2.1 of [ITU-T G.8312]. + +**Selector:** The function shall select the normal MTNP signal or the replacement signal. When aAIS[ $j$ ] is true, it shall select the replacement signal. Otherwise, it shall select the normal MTNP signal. + +##### Defects + +The function shall detect dGIDM, dFMM, dTIM[ $i$ ], dLOL and dCCM[ $j$ ]. + +**dGIDM:** See clause 6.1.2.2. + +**dFMM:** See clause 6.1.2.3. + +**dTIM[ $i$ ]:** See clause 6.1.2.1; The index $i$ ranges from 1 to $m$ and denotes the MTNS PHY. dTIM is detected per MTNS PHY. + +**dLOL:** If the alignment process of the deskew function 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. + +**dCCM[ $j$ ] (client calendar mismatch):** See clause 6.1.6.1. dCCM shall be detected per MTNP. The index $j$ ranges from 1 to $p$ and denotes the MTNP tributary port. + +##### Consequent actions + +$aSSF[j] \leftarrow dCCM[j] \text{ or } dLOL \text{ or } dTIM[i] \text{ or } dFMM \text{ or } dGIDM \text{ or } \sum AI\_TSF[1..n]$ , where $i=1$ to $m$ , $j=1$ to $p$ . + +$aAIS[j] \leftarrow dCCM[j] \text{ or } dLOL \text{ or } dTIM[i] \text{ or } dFMM \text{ or } dGIDM \text{ or } \sum AI\_TSF[1..n]$ , where $i=1$ to $m$ , $j=1$ to $p$ . + +##### Defect correlations + +$cGIDM \leftarrow dGIDM \text{ and (not } \sum AI\_TSF[1..n])$ + +$cFMM \leftarrow dFMM \text{ and (not } dGIDM) \text{ and (not } \sum AI\_TSF[1..n])$ + +$cTIM \leftarrow \sum dTIM[i] \text{ and (not } dFMM) \text{ and (not } dGIDM) \text{ and (not } \sum AI\_TSF[1..n])$ , where $i=1$ to $m$ . + +$cLOL \leftarrow dLOL \text{ and (not } dFMM) \text{ and (not } dGIDM) \text{ and (not } \sum AI\_TSF[1..n])$ + +$cCCM[j] \leftarrow dCCM[j] \text{ and (not } dLOL) \text{ and (not } dTIM[i]) \text{ and (not } dFMM) \text{ and (not } dGIDM) \text{ and (not } \sum AI\_TSF[1..n])$ , where $i=1$ to $m$ , $j=1$ to $p$ . + +**Performance monitoring:** None. + +# 11 Media adaptation functions + +## 11.1 M-AI to MTNS $y$ adaptation function (M-AI/MTNS\_A, $y = 0,1,2,4$ ) + +The M-AI to MTNS $y$ adaptation functions perform the adaptation between the group of optical signals related with a PHY that is part of the group carrying the MTNS (i.e., the MTNS is carried over a group of $m$ PHYs operating at same rate) and the characteristic information of the MTNS layer signal. PHY rates of 50G ( $y=0$ ), 100G ( $y=1$ ), 200G ( $y=2$ ), and 400G ( $y=4$ ) are supported. + +The MTNS characteristic information is defined in clause 10.2. + +### 11.1.1 M-AI to MTNSy adaptation source function (M-AI/MTNS\_So\_A, $y = 0, 1, 2, 4$ ) + +The information flow and processing of the M-AI/MTNSy\_A\_So function ( $y = 0, 1, 2, 4$ ) is defined with reference to Figure 11-1. + +#### Symbol + +![Figure 11-1 – M-AI/MTNSy_A_So function symbol diagram. A trapezoidal block labeled 'M-AI/MTNSy' has an input arrow from 'MTNSyp_CP (y=0,1,2,4)' pointing down to it. An output arrow points down from the block to 'M_AP' with a reference 'G.8321(22)'. A bidirectional horizontal arrow connects the right side of the block to 'M-AI/MTNSy_A_So_MP'.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +Figure 11-1 – M-AI/MTNSy\_A\_So function symbol diagram. A trapezoidal block labeled 'M-AI/MTNSy' has an input arrow from 'MTNSyp\_CP (y=0,1,2,4)' pointing down to it. An output arrow points down from the block to 'M\_AP' with a reference 'G.8321(22)'. A bidirectional horizontal arrow connects the right side of the block to 'M-AI/MTNSy\_A\_So\_MP'. + +Figure 11-1 – M-AI/MTNSy\_A\_So function + +#### Interfaces + +Table 11-1 – M-AI/MTNSy\_A\_So inputs and outputs + +| Input(s) | Output(s) | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| +| MTNSy_CP :
MTNSy_CI_CK
MTNSy_CI_D[1..q] (Note)
MTNSy_CI_FS
MTNSy_CI_MFS

M-AI/MTNSy_A_So_MP:
M-AI/MTNSy_A_So_MI_[IEEE802.3] | M_AP:
M-AI_D[1..N]

M-AI/MTNSy_A_So_MP:
M-AI/MTNSy_A_So_MI_[IEEE802.3] | +| NOTE – $q = y$ if $y = (1, 2, 4)$ or $q = 1$ if $y = 0$ . | | + +#### Processes + +The processes associated with the M-AI/MTNSy\_A\_So function are as depicted in Figures 11-2.1 and 11-2.2 for $y = 0$ (50GBASE-R PHY), $y = 1$ (100GBASE-R PHY), $y = 2$ (200GBASE-R PHY) or $y = 4$ (400GBASE-R PHY). + +As described in clause 7.1 of [ITU-T G.8312] the signal comprises $q$ FlexE instances per PHY. For MTNS0 ( $y=0$ ), a single 50G FlexE instance is carried over the 50G PHY (i.e., $q = 1$ ). For MTNSy with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are interleaved within the $[y \times 100G]$ PHY (i.e., $q = y$ ). + +![Block diagrams of M-AI/MTNS0_A_So_MP and M-AI/MTNS1_A_So_MP processes. Both show a vertical stack of processing blocks: OMFS insertion, CRC-16, FS insertion, PAD insertion, Error marking, and [IEEE 802.3] processes. Inputs include CL_FS, CL_MFS, CL_D, and CL_CK. A clock generation block (50G or 100G BASE-R) provides CK and CKP signals. The output is labeled M1_[IEEE 802.3] and M_AI/MTNSy_A_So_MP. Below the stack, AI_D[1] to AI_D[N] are shown, leading to M_AP. Reference G.8321(22) is noted.](6f11044c88ea04e43de06c3491defeee_img.jpg) + +The diagram illustrates two process flows for M-AI/MTNS0\_A\_So\_MP and M-AI/MTNS1\_A\_So\_MP. Both follow a similar structure: inputs (CL\_FS, CL\_MFS, CL\_D, CL\_CK) enter a series of blocks (OMFS insertion, CRC-16, FS insertion, PAD insertion, Error marking, [IEEE 802.3] processes). A clock generation block (50G BASE-R for MTNS0, 100G BASE-R for MTNS1) provides CK and CKP signals. The output is labeled M1\_[IEEE 802.3] and M\_AI/MTNSy\_A\_So\_MP. Below the stack, AI\_D[1] to AI\_D[N] are shown, leading to M\_AP. Reference G.8321(22) is noted. + +Block diagrams of M-AI/MTNS0\_A\_So\_MP and M-AI/MTNS1\_A\_So\_MP processes. Both show a vertical stack of processing blocks: OMFS insertion, CRC-16, FS insertion, PAD insertion, Error marking, and [IEEE 802.3] processes. Inputs include CL\_FS, CL\_MFS, CL\_D, and CL\_CK. A clock generation block (50G or 100G BASE-R) provides CK and CKP signals. The output is labeled M1\_[IEEE 802.3] and M\_AI/MTNSy\_A\_So\_MP. Below the stack, AI\_D[1] to AI\_D[N] are shown, leading to M\_AP. Reference G.8321(22) is noted. + +Figure 11-2.1 – M-AI/MTNS1\_A\_So (y= 1) and M-AI/MTNS0\_A\_So (y=0) processes + +![Block diagram of M-AI/MTNSy_A_So_MP processes for y=2 or y=4. It shows multiple parallel processing paths (y paths) for inputs CL_D[y]. Each path has blocks: OMFS insertion, CRC-16, FS insertion, PAD insertion. These are followed by a common 'Interleaving' block, then 'Error marking', and '[IEEE 802.3] processes'. A clock generation block (y00G BASE-R) provides CK and CKP signals. The output is labeled M1_[IEEE 802.3] and M-AI/MTNSy_A_So_MP. Below, AI_D[1] to AI_D[N] lead to M_AP. Reference G.8321(22) is noted.](b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg) + +The diagram illustrates the M-AI/MTNSy\_A\_So\_MP process for y=2 or y=4. It features multiple parallel processing paths (y paths) for inputs CL\_D[y]. Each path consists of OMFS insertion, CRC-16, FS insertion, and PAD insertion blocks. The outputs of these paths are then combined in an 'Interleaving' block, followed by 'Error marking' and '[IEEE 802.3] processes'. A clock generation block (y00G BASE-R) provides CK and CKP signals. The output is labeled M1\_[IEEE 802.3] and M-AI/MTNSy\_A\_So\_MP. Below the stack, AI\_D[1] to AI\_D[N] are shown, leading to M\_AP. Reference G.8321(22) is noted. + +Block diagram of M-AI/MTNSy\_A\_So\_MP processes for y=2 or y=4. It shows multiple parallel processing paths (y paths) for inputs CL\_D[y]. Each path has blocks: OMFS insertion, CRC-16, FS insertion, PAD insertion. These are followed by a common 'Interleaving' block, then 'Error marking', and '[IEEE 802.3] processes'. A clock generation block (y00G BASE-R) provides CK and CKP signals. The output is labeled M1\_[IEEE 802.3] and M-AI/MTNSy\_A\_So\_MP. Below, AI\_D[1] to AI\_D[N] lead to M\_AP. Reference G.8321(22) is noted. + +Figure 11-2.2 – M-AI/MTNSy\_A\_So processes (y= 2 or y= 4) + +The following processes are performed for each FlexE instance: + +- **OMFS insertion:** FlexE overhead multi-frame alignment signal (i.e., multi-frame start (MFS)) is inserted within the OMF bit as described in clause 9.2.1 of [ITU-T G.8312]. For $y=0$ (50G FlexE instance), the multiframe sequence is over sixteen consecutive overhead frames, while for $y=\{1,2,4\}$ ( $y \times 100$ G FlexE instance(s)), the multiframe sequence is over thirty-two consecutive overhead frames. +- **FS insertion:** FlexE overhead frame alignment signal (i.e., frame start (FS)) is inserted in the first 66B block of the FlexE instance overhead frame encoded as a special ordered set as described in clause 9.2.1 of [ITU-T G.8312]. The overhead frame alignment signal is defined by a 2-bit sync header of '10' (i.e., control block), the pattern "0x4B" in bits 0 to 7 (i.e., control block type value) and the pattern "0x5" in bits 32 to 35 (i.e., "O" code value). It is present once per $(1023 \times 20 + 1) \times 8$ 66B blocks that is the length of FlexE overhead frame as illustrated in Figure 7-1 of [ITU-T G.8312]. +- **Cyclic redundancy check (CRC)-16:** See clause 9.2.8 of [ITU-T G.8312]. The function shall compute the CRC-16 and insert the calculated CRC-16 value into the CRC-16 field of FlexE instance overhead. +- **PAD insertion (only in the case of $y=0, 2$ or $4$ ):** The function shall insert two 66B pad blocks (P1, P2) after every 163830 66B blocks at the same relative position on each FlexE instance as described in clause 7.1 of [ITU-T G.8312]. It is used to compensate the difference between the 1/16K alignment marker spacing for 100GBASE-R PHYs and the 1/20K alignment marker spacing for 50GBASE-R, 200GBASE-R, or 400GBASE-R PHYs so that the 5G calendar slots carried over all PHY types are the same nominal size. + +**Interleaving (only in the case of $y=2$ or $4$ ):** The function shall frame-synchronously 66B block interleave the 'y' 100G FlexE instances after pad blocks insertion into a 66B block data stream as described in clause 7.1 of [ITU-T G.8312]. The 'y' 100G FlexE instances are interleaved in ascending FlexE instance number value. + +**Error Marking:** The function shall replace any 66B block that has been error-marked by [IEEE 802.3 processes] or any 66B block with invalid sync headers or any 66B control block carrying an invalid Type field (per [IEEE 802.3] Table 82-5) with an error control block /E/ to avoid possible error contamination in an MTNP Forwarding node, per clause 8.1 in [ITU-T G.8312]. + +**xGBASE-R Clock Generation:** The function shall generate a 50GBASE-R clock if $y=0$ or $y=100$ GBASE-R clock if $y=\{1,2$ or $4\}$ that is locked to the incoming clock (CI\_CK). + +**[IEEE 802.3] processes:** The [IEEE 802.3] processes represent the whole functionality of the PCS sublayer below MTNS functions, as well as the PMA and PMD sublayers in the IEEE 802.3 model. + +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. + +**Defects:** None. + +**Consequent actions:** None. + +**Defect correlations:** None. + +**Performance monitoring:** None. + +### **11.1.2 M-AI to MTNSy adaptation sink function (M-AI/MTNS\_Sk\_A, $y = 0,1,2,4$ )** + +The information flow and processing of the M-AI/MTNSy\_A\_Sk function ( $y = 0,1,2,4$ ) is defined with reference to Figure 11-3. + +#### Symbol + +![Figure 11-3 – M-AI/MTNSy_A_Sk function symbol diagram. A trapezoidal block labeled 'M-AI/MTNSy' has three connections: an input arrow from the bottom labeled 'M_AP' and 'G.8321(22)', an output arrow pointing up labeled 'MTNSy_CP (y=0,1,2,4)', and a bidirectional arrow on the right labeled 'M-AI/MTNSy_A_Sk_MP'.](feae5a5b6e128162dbced0860fd97b9b_img.jpg) + +Figure 11-3 – M-AI/MTNSy\_A\_Sk function symbol diagram. A trapezoidal block labeled 'M-AI/MTNSy' has three connections: an input arrow from the bottom labeled 'M\_AP' and 'G.8321(22)', an output arrow pointing up labeled 'MTNSy\_CP (y=0,1,2,4)', and a bidirectional arrow on the right labeled 'M-AI/MTNSy\_A\_Sk\_MP'. + +Figure 11-3 – M-AI/MTNSy\_A\_Sk function + +#### Interfaces + +Table 11-2 – M-AI/MTNSy\_A\_Sk inputs and outputs + +| Input(s) | Output(s) | +|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M_AP:
M-AI_D[1..N]

M-AI/MTNSy_A_Sk_MP:
M-AI/MTNSy_A_Sk_MI_[IEEE802.3] | MTNSy_CP :
MTNSy_CI_CK
MTNSy_CI_D[1..q] (Note 1)
MTNSy_CI_FS
MTNSy_CI_MFS
MTNSy_CI_CRCerr[1..q] (Note 1)
MTNSy_CI_SSF

M-AI/MTNSy_A_Sk_MP:
M-AI/MTNSy_A_Sk_MI_[IEEE802.3]
M-AI/MTNSy_A_Sk_MI_cLOF
M-AI/MTNSy_A_Sk_MI_cLOM | + +NOTE – $q = y$ if $y = (1, 2, 4)$ , or $q = 1$ if $y = 0$ . + +#### Processes + +The processes associated with the M-AI/MTNSy\_A\_Sk functions are as depicted in Figure 11-4.1 and Figure 11-4.2 below, for $y = 0$ (50GBASE-R PHY), $y = 1$ (100GBASE-R PHY), $y = 2$ (200GBASE-R PHY) or $y = 4$ (400GBASE-R PHY). + +As described in clause 7.1 of [ITU-T G.832] the signal comprises $q$ FlexE instances per PHY. For MTNS0 ( $y=0$ ), a single 50G FlexE instance is carried over the 50G PHY (i.e., $q = 1$ ). For MTNSy with $y=(1, 2, 4)$ , $y$ 100G FlexE instances are interleaved within the $[y \times 100G]$ PHY (i.e., $q = y$ ). + +![Two block diagrams showing the internal architecture of MTNS0_CP and MTNS1_CP processes. Both diagrams show a vertical stack of functional blocks: [IEEE 802.3] processes, Error marking, PAD lock, PAD deletion, Frame alignment, CRC-16, Overhead multiframe alignment, and a Selector. The MTNS0_CP diagram includes a 'Remplacement signal generation' block and 'Consequent actions' block, while the MTNS1_CP diagram includes an 'Error marking' block and 'Defect correlations' block. Various signal labels like CL_MFS, CL_CRCerr, CL_FS, CL_D, CL_CK, dLOM, dLOF, dPCS, aAIS, aSSF, MI_cLOM, and MI_cLOF are shown throughout the diagrams.](87c64bd7d33fca8b9b29228c80ddf175_img.jpg) + +The diagram illustrates two process architectures, MTNS0\_CP and MTNS1\_CP, both enclosed in a grey box labeled M-AI/MTNS $\gamma$ \_A\_Sk\_MP. + +**MTNS0\_CP (Left):** + +- Inputs: AL\_D[1] to AL\_D[N] (labeled M\_AP) enter the [IEEE 802.3] processes block. +- [IEEE 802.3] processes block outputs: D, CK, and dPCS. +- Error marking block: Receives D and CK; outputs to PAD lock. +- PAD lock block: Outputs to PAD deletion. +- PAD deletion block: Outputs to Frame alignment (dLOM, dLOF). +- Frame alignment block: Outputs to CRC-16 (FS). +- CRC-16 block: Outputs to Overhead multiframe alignment (CRCerr). +- Overhead multiframe alignment block: Outputs to Selector (MFS). +- Remplacement signal generation block: Receives MFS, FS, D, and CK; outputs aAIS and aSSF. +- Consequent actions block: Receives dLOM, dLOF, and dPCS; outputs to Selector. +- Selector block: Outputs CL\_MFS, CL\_CRCerr, CL\_FS, CL\_D, and CL\_CK. +- Defect correlations block: Receives dLOM, dLOF, and dPCS; outputs MI\_cLOM and MI\_cLOF. + +**MTNS1\_CP (Right):** + +- Inputs: AL\_D[1] to AL\_D[N] (labeled M\_AP) enter the [IEEE 802.3] processes block. +- [IEEE 802.3] processes block outputs: D, CK, and dPCS. +- Error marking block: Receives D and CK; outputs to Error marking. +- Error marking block: Outputs to Frame alignment. +- Frame alignment block: Outputs to CRC-16 (FS). +- CRC-16 block: Outputs to Overhead multiframe alignment (CRCerr). +- Overhead multiframe alignment block: Outputs to Selector (MFS). +- Remplacement signal generation block: Receives MFS, FS, D, and CK; outputs aAIS and aSSF. +- Consequent actions block: Receives dLOM, dLOF, and dPCS; outputs to Selector. +- Selector block: Outputs CL\_MFS, CL\_CRCerr, CL\_FS, CL\_D, and CL\_CK. +- Defect correlations block: Receives dLOM, dLOF, and dPCS; outputs MI\_cLOM and MI\_cLOF. + +Reference G.8321(22) is noted at the bottom right. + +Two block diagrams showing the internal architecture of MTNS0\_CP and MTNS1\_CP processes. Both diagrams show a vertical stack of functional blocks: [IEEE 802.3] processes, Error marking, PAD lock, PAD deletion, Frame alignment, CRC-16, Overhead multiframe alignment, and a Selector. The MTNS0\_CP diagram includes a 'Remplacement signal generation' block and 'Consequent actions' block, while the MTNS1\_CP diagram includes an 'Error marking' block and 'Defect correlations' block. Various signal labels like CL\_MFS, CL\_CRCerr, CL\_FS, CL\_D, CL\_CK, dLOM, dLOF, dPCS, aAIS, aSSF, MI\_cLOM, and MI\_cLOF are shown throughout the diagrams. + +Figure 11-4.1 – M-AI/MTNS1\_A\_Sk ( $\gamma=1$ ) and M-AI/MTNS0\_A\_Sk ( $\gamma=0$ ) processes + +![Figure 11-4.2 – M-AI/MTNSy_A_Sk processes (y= 2 or 4). This block diagram illustrates the data flow and processing stages for multiple FlexE instances (y=2, 4). At the bottom, data from '[IEEE 802.3] processes' enters the 'Error marking' block, which also receives 'CK' and 'D' inputs. The output then goes to 'De-interleaving', which receives 'PAD_location' from 'PAD lock' blocks. Above 'De-interleaving' are 'PAD lock' and 'PAD deletion' blocks. The 'PAD deletion' output goes to 'Frame alignment', which produces 'dLOF[y]'. This is followed by 'CRC-16' (producing 'CRCerr') and 'Overhead multiframe alignment' (producing 'dLOM[y]'). All these signals ('dLOM[y]', 'CRCerr', 'FS', 'MFS') are fed into a 'Selector' block. The 'Selector' produces 'MTNSy_CP (y=2,4)' outputs: 'CI_CRCerr[y]', 'CI_D[y]', 'CI_CRCerr[2]', 'CI_D[2]', 'CI_CRCerr[1]', 'CI_D[1]', 'CI_MFS', 'CI_FS', 'CI_CK', and 'CI_SSF'. A 'Replacement signal generation' block receives 'aAIS' and 'aSSF' and provides inputs to the 'Selector'. 'Consequent actions' block receives 'dLOM[1..y]', 'dLOF[1..y]', and 'dPCS' and produces 'MI_cLOM', 'MI_cLOF', and 'MI_[IEEE 802.3]'. A 'Defect correlations' block receives 'dLOM[1..y]', 'dLOF[1..y]', and 'dPCS' and produces 'MI_cLOM', 'MI_cLOF', and 'MI_[IEEE 802.3]'. The entire diagram is labeled 'G.8321(22)' and 'M-AI/MTNSy_A_Sk_MP'.](352d21d1e740e4a58cb17ab8656cfad8_img.jpg) + +Figure 11-4.2 – M-AI/MTNSy\_A\_Sk processes (y= 2 or 4). This block diagram illustrates the data flow and processing stages for multiple FlexE instances (y=2, 4). At the bottom, data from '[IEEE 802.3] processes' enters the 'Error marking' block, which also receives 'CK' and 'D' inputs. The output then goes to 'De-interleaving', which receives 'PAD\_location' from 'PAD lock' blocks. Above 'De-interleaving' are 'PAD lock' and 'PAD deletion' blocks. The 'PAD deletion' output goes to 'Frame alignment', which produces 'dLOF[y]'. This is followed by 'CRC-16' (producing 'CRCerr') and 'Overhead multiframe alignment' (producing 'dLOM[y]'). All these signals ('dLOM[y]', 'CRCerr', 'FS', 'MFS') are fed into a 'Selector' block. The 'Selector' produces 'MTNSy\_CP (y=2,4)' outputs: 'CI\_CRCerr[y]', 'CI\_D[y]', 'CI\_CRCerr[2]', 'CI\_D[2]', 'CI\_CRCerr[1]', 'CI\_D[1]', 'CI\_MFS', 'CI\_FS', 'CI\_CK', and 'CI\_SSF'. A 'Replacement signal generation' block receives 'aAIS' and 'aSSF' and provides inputs to the 'Selector'. 'Consequent actions' block receives 'dLOM[1..y]', 'dLOF[1..y]', and 'dPCS' and produces 'MI\_cLOM', 'MI\_cLOF', and 'MI\_[IEEE 802.3]'. A 'Defect correlations' block receives 'dLOM[1..y]', 'dLOF[1..y]', and 'dPCS' and produces 'MI\_cLOM', 'MI\_cLOF', and 'MI\_[IEEE 802.3]'. The entire diagram is labeled 'G.8321(22)' and 'M-AI/MTNSy\_A\_Sk\_MP'. + +**Figure 11-4.2 – M-AI/MTNSy\_A\_Sk processes (y= 2 or 4)** + +**[IEEE 802.3 processes]:** The [IEEE 802.3] processes represent the whole functionality of the PCS sublayer below the MTNS section, as well as the PMA and PMD sublayers in the IEEE 802.3 model. +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. + +**Error Marking:** The function shall replace any 66B block that has been error-marked by [IEEE 802.3 processes] or any 66B block with invalid sync headers or any 66B control block carrying an invalid Type field (per [IEEE 802.3] Table 82-5) with an error control block /E/ to avoid possible error contamination in an MTNP Forwarding node, per clause 8.1 in [ITU-T G.8312]. + +**De-interleaving (only if y=2 or 4):** The function shall 66B block de-interleave the $[y \times 100G]$ 66B block stream in a round-robin manner over $y$ 100G 66B streams, such that the $y$ 66B P1 PAD blocks appear at the same time on the $y$ de-interleaved 100G 66B block streams. This deinterleaving process ensure that after PAD deletion, the first 100G FlexE instance (with lowest FlexE instance number) is output towards MTNSy\_CI\_D[1] and the last 100G FlexE instance (with highest FlexE instance number) is output towards MTNSy\_CI\_D[y]. + +The following processes are performed for each FlexE instance: + +- **PAD lock (only if y=0, 2 or 4):** The function shall perform 66B PAD block lock as described in clause 8.2.2.1. + +- **PAD deletion (only if $y=0, 2$ or $4$ ):** deletion (only if $y=0, 2$ or $4$ ): The function shall delete the 66B PAD blocks P1 and P2. +- **Frame alignment:** The function shall recover the FlexE instance overhead frame start as described in clause 8.2.2.2. +- **CRC-16:** The CRC-16 is extracted from the CRC-16 field. If the extracted CRC-16 value has the expected value per the computation specified in clause 9.2.8 of [ITU-T G.8312], CRCerr is set to 0; otherwise, CRCerr is set to 1. +- **Overhead multi-frame alignment:** The function shall recover the overhead multi-frame start from the overhead multi-frame (OMF) bit indication in the FlexE instance overhead as described in clause 8.2.2.3 for $y=(1, 2$ or $4)$ or in clause 8.2.2.4 for $y=0$ . + +**Replacement signal generation:** When aAIS is true, the function shall provide for a replacement signal (including clock, frame start, and multi-frame start) generation process that generates a stream of local fault sequence ordered sets for each FlexE instance signal. + +**Normal/Replacement signal Selector:** The function shall select the normal FlexE instance signal or the replacement signal. When aAIS is true, it shall select the replacement signal. Otherwise, it shall select the normal FlexE instance signal. + +#### Defects + +The function shall detect dPCS, dLOF[1.. $q$ ], and dLOM[1.. $q$ ], with $q=y$ if $y=(1, 2$ or $4)$ , or $q=1$ if $y=0$ . + +**dPCS:** This defect represents any defect detected by the [IEEE 802.3] processes in the portion of the PCS below the FlexE shim, or in the PMA or PMD sublayers. + +**dLOF[1.. $q$ ]:** The loss of FlexE instance overhead frame defect dLOF is generated based on the state of the FlexE instance overhead frame alignment process. See dLOF described in clause 6.1.5.1. + +**dLOM[1.. $q$ ]:** The loss of FlexE instance overhead multi-frame defect dLOM is generated based on the state of the FlexE instance overhead multi-frame alignment process. See dLOM described in clause 6.1.5.2. + +##### Consequent actions + +aSSF $\leftarrow$ dPCS or $\sum$ dLOF[1.. $q$ ] or $\sum$ dLOM[1.. $q$ ] + +aAIS $\leftarrow$ dPCS or $\sum$ dLOF[1.. $q$ ] or $\sum$ dLOM[1.. $q$ ] + +On declaration of aAIS, the function shall output a replacement signal per FlexE instance signal, which consists of a continuous stream of Local Fault ordered sets at a bit rate of $103.125 \text{ Gb/s} \times \frac{16383}{16384} \pm 100 \text{ ppm}$ for 100G FlexE instance or at a bit rate of $51.5625 \text{ Gb/s} \times \frac{20479}{20480} \pm 100 \text{ ppm}$ for 50G FlexE instance, within two FlexE overhead frames. On clearing aAIS, the FlexE replacement signal shall be removed within two FlexE overhead frames, with normal data being output. The FlexE replacement signal clock, frame start, and multi-frame start shall be independent from the incoming clock, frame start, and multi-frame start. + +#### Defect correlations + +cLOF $\leftarrow$ $\sum$ dLOF[1.. $q$ ] and (not dPCS) + +cLOM $\leftarrow$ $\sum$ dLOM[1.. $q$ ] and (not dPCS) and (not $\sum$ dLOF[1.. $q$ ]) + +#### Performance monitoring + +Performance monitoring is part of the [IEEE 802.3] processes. There is no additional performance monitoring for the MTNSy-related processes. + +# Appendix I + +## Example state machine of MTN Path OAM Basic block alignment + +(This appendix does not form an integral part of this Recommendation.) + +Figure I.1 shows an example state machine that implements the MTN Path OAM Basic block alignment process. + +![State machine diagram for MTN Path OAM Basic block alignment. It consists of five states: IBA_ExpB1, IBA_ExpB2, OoBA_Root, OoBA_ExpB1, and OoBA_ExpB2. Transitions are labeled with events and actions.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +``` +stateDiagram-v2 + [*] --> IBA_ExpB1 + IBA_ExpB1 --> IBA_ExpB2 : (B1 detected before declared missing, reset missing count) OR (B1 declared missing, increment missing count) + IBA_ExpB2 --> IBA_ExpB1 : (B2 detected before declared missing, reset missing count) OR (B2 declared missing, increment missing count) + IBA_ExpB1 --> OoBA_Root : Missing count threshold exceeded, reset missing count + IBA_ExpB2 --> OoBA_Root : Missing count threshold exceeded, reset missing count + OoBA_Root --> IBA_ExpB1 : B2 detected before declared missing, reset missing count + OoBA_Root --> IBA_ExpB2 : B1 detected before declared missing, reset missing count + OoBA_Root --> OoBA_ExpB1 : B1 detected + OoBA_Root --> OoBA_ExpB2 : B2 detected + OoBA_ExpB1 --> IBA_ExpB1 : B1 detected before declared missing, reset missing count + OoBA_ExpB1 --> OoBA_Root : B1 declared missing + OoBA_ExpB2 --> IBA_ExpB2 : B2 detected before declared missing, reset missing count + OoBA_ExpB2 --> OoBA_Root : B2 declared missing +``` + +The diagram illustrates a state machine with five states: IBA\_ExpB1, IBA\_ExpB2, OoBA\_Root, OoBA\_ExpB1, and OoBA\_ExpB2. Transitions are labeled with events and actions. + +- Initial state to IBA\_ExpB1. +- IBA\_ExpB1 to IBA\_ExpB2: (B1 detected before declared missing, reset missing count) OR (B1 declared missing, increment missing count) +- IBA\_ExpB2 to IBA\_ExpB1: (B2 detected before declared missing, reset missing count) OR (B2 declared missing, increment missing count) +- IBA\_ExpB1 to OoBA\_Root: Missing count threshold exceeded, reset missing count +- IBA\_ExpB2 to OoBA\_Root: Missing count threshold exceeded, reset missing count +- OoBA\_Root to IBA\_ExpB1: B2 detected before declared missing, reset missing count +- OoBA\_Root to IBA\_ExpB2: B1 detected before declared missing, reset missing count +- OoBA\_Root to OoBA\_ExpB1: B1 detected +- OoBA\_Root to OoBA\_ExpB2: B2 detected +- OoBA\_ExpB1 to IBA\_ExpB1: B1 detected before declared missing, reset missing count +- OoBA\_ExpB1 to OoBA\_Root: B1 declared missing +- OoBA\_ExpB2 to IBA\_ExpB2: B2 detected before declared missing, reset missing count +- OoBA\_ExpB2 to OoBA\_Root: B2 declared missing + +G.8321(22) + +State machine diagram for MTN Path OAM Basic block alignment. It consists of five states: IBA\_ExpB1, IBA\_ExpB2, OoBA\_Root, OoBA\_ExpB1, and OoBA\_ExpB2. Transitions are labeled with events and actions. + +Figure I.1 – Example of a MTP path OAM basic block alignment state machine + +The MTN path OAM basic block alignment process is in the IBA state when the above state machine is in the IBA\_ExpB1 and IBA\_ExpB2 states. Conversely, the alignment process is in the OoBA state when the above state machine is in the OoBA\_ROOT, OoBA\_ExpB1 and OoBA\_ExpB2 states. + +The state machine is expecting to receive a B1 Basic block when it is in the IBA\_ExpB1 and the OoBA\_ExpB1 states. Similarly, state machine is expecting to receive a B2 Basic block when it is in the IBA\_ExpB2 and the OoBA\_ExpB2 states. + +# Appendix II + +## BIP calculation under missing Basic block + +(This appendix does not form an integral part of this Recommendation.) + +A sequence of parity calculation intervals with the Basic blocks that terminate and start an interval is shown in Figure II.1. + +![Figure II.1: Basic blocks and parity calculation windows. A horizontal timeline from 0 to 7. Vertical bars at 0, 1, 2, 4, 5, 6, and 7 are black. A bar at 3 is grey. Intervals A, B, C, D, E, F, and G are labeled between the bars. G.8321(22) is written at the bottom right.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +Figure II.1: Basic blocks and parity calculation windows. A horizontal timeline from 0 to 7. Vertical bars at 0, 1, 2, 4, 5, 6, and 7 are black. A bar at 3 is grey. Intervals A, B, C, D, E, F, and G are labeled between the bars. G.8321(22) is written at the bottom right. + +**Figure II.1 – Basic blocks and parity calculation windows** + +Table II.1 provides an example of the relationship between the parity calculation interval and the Basic block that carries the result. + +**Table II.1- Relationship between the parity calculation interval and the Basic block** + +| Parity calculation interval | A | B | C | D | E | F | G | +|-----------------------------|---|---|---|---|---|---|---| +| B block | 3 | 4 | 5 | 6 | 7 | 8 | 9 | + +For example, if block 3 is declared missing (and all other blocks are received) the parity calculation interval A is marked as errored. The location of the boundary between parity calculation intervals C and D is unknown and these intervals are marked as errored. + +The results of the parity calculated in interval B is compared to the result provided in Basic block 4, the result of parity calculated in interval E is compared to the parity provided in Basic block 7. + + + +# 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.852.12-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.852.12-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.852.12-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d77a478c5b78d330a2a6abbd32e7d0ac053d8b9c1ffe8a96476214afa6ddf7ae +size 8196 diff --git a/marked/G/T-REC-G.852.12-199903-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/G/T-REC-G.852.12-199903-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e1a29ee29701de081fe41bb8c82283faf18898b --- /dev/null +++ b/marked/G/T-REC-G.852.12-199903-I_PDF-E/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f43181e868fb5ce23ce963e364413445e82cc761d145f094f068d100a519313 +size 114439 diff --git a/marked/G/T-REC-G.852.12-199903-I_PDF-E/raw.md b/marked/G/T-REC-G.852.12-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a3fdcdad9dd09b593f885c7429b44f17462cc0d5 --- /dev/null +++ b/marked/G/T-REC-G.852.12-199903-I_PDF-E/raw.md @@ -0,0 +1,381 @@ + + +![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.852.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 + +--- + +**Enterprise viewpoint for pre-provisioned link +management** + +ITU-T Recommendation G.852.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 | +| 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. + +# **ENTERPRISE 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 (see 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 (see G.85x.8 series of Recommendations) within topological linking entities or the link management within client linking entities. + +## **Source** + +ITU-T Recommendation G.852.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 ..... | 1 | +| 6 | Community pre-provisioned link management ..... | 2 | +| 6.1 | Purpose ..... | 2 | +| 6.2 | Role ..... | 3 | +| 6.3 | Community policy ..... | 3 | +| 6.4 | Action ..... | 4 | +| 6.4.1 | Add transport entities to client linking entity ..... | 4 | +| 6.4.2 | Remove transport entities from client linking entity ..... | 5 | +| 6.4.3 | Report client linking entity capacity change ..... | 6 | + + + +## Recommendation G.852.12 + +# ENTERPRISE VIEWPOINT FOR PRE-PROVISIONED LINK MANAGEMENT + +(Geneva, 1999) + +# 1 Scope + +This Recommendation specifies the enterprise viewpoint for the pre-provisioned link management of a transport 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; 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.852.2 (1999), *Enterprise viewpoint description of transport network resource model.* + +# 3 Definitions + +None. + +# 4 Abbreviations + +This Recommendation uses the following abbreviations: + +| | | +|-----|----------------------------------| +| CTP | Connection Termination Point | +| Id | Identifier | +| plm | pre-provisioned link management | +| SDH | Synchronous Digital Hierarchy | +| WDM | Wavelength Division Multiplexing | + +# 5 Conventions + +None. + +# 6 Community pre-provisioned link management + +## 6.1 Purpose + +The purpose of this community is to allow a caller: + +- to add link connections to a link or remove link connections from a link and to update the capacity of the link in the arc view (see Figure 1); or +- to add CTPs to a link end or remove CTPs from a link end and to update the capacity of the link end in the point view. + +This community should be used in the case where capacity has already been provisioned using the trail management and adaptation management communities. This capability of having pre-provisioned link connections is available in technologies such as SDH or WDM. + +![Diagram illustrating the possible functionalities of the link management community (arc view).](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram illustrates the interaction between a client linking entity (e.g., link), a provider linking entity (e.g., link or topological link), and a transport entity (e.g., link connection) within the context of the link management community. The diagram is divided into two main sections: the top section shows a client linking entity (a cylinder with four horizontal lines) connected to a provider linking entity (another cylinder with four horizontal lines) via a link management community. The bottom section shows a provider linking entity (cylinder with four horizontal lines) connected to a transport entity (cylinder with four horizontal lines) via a link management community. Both sections show the flow of information and control through the link management community. The bottom section also includes an adaptation function and a trail management component. The diagram is labeled with various entities and communities, and the reference number T0410220-98 is present in the bottom right corner. + +Diagram illustrating the possible functionalities of the link management community (arc view). + +**Figure 1/G.852.12 – Possible functionalities of the link management community (arc view)** + +## 6.2 Role + +### **plm\_caller** + +This role reflects the client of the actions defined within this community. One and only one caller role occurrence must exist in the community. + +### **plm\_provider** + +This role reflects the server of the actions defined within this community. One and only one provider role occurrence must exist in the community. + +### **notification receiver** + +This role represents a receiver of the reporting actions defined within this community. Zero or more notification receiver role occurrence may exist in the community. + +### **layer network domain** + +This role represents the layer network domain resource defined in Recommendation G.852.2. One and only one role occurrences must exist in the community. + +### **client linking entity** + +This role reflects the link resource or the link end resource as defined in Recommendation G.852.2 to/from which the transport entities could be added/removed. One or more linking entity role occurrences may exist in the community. + +### **provider linking entity** + +This role reflects the topological link or link resource, or the topological link end or link end resource as defined in Recommendation G.852.2. Zero or more topological linking entity or linking entity role occurrences may exist in the community. + +### **transport entity** + +This role reflects the link connection resource or the connection termination point resource as defined in Recommendation G.852.2 which could be added/removed to/from the client linking entity. One or more transport entity role occurrences may exist in the community. + +## 6.3 Community policy + +### **OBLIGATION resourceConsistency** + +This community applies for both arc-oriented view and point-oriented view. The roles linking entity and transport entity can be played by either arc-oriented resources or point-oriented resources, but consistently: those two roles can be played either by arc-oriented resources or by point-oriented resources, but not by a mixture of arc-oriented and point-oriented resources. In an arc-oriented view the point oriented resources may only exist at the boundary of a subnetwork. + +### **OBLIGATION scope** + +Only properties that are explicitly stated in this community are valid and can be accessed by both caller and provider of this community. Conformance to this service depends only on the explicit specification of this service. Any other modifications outside of this community are not relevant for conformance. + +### **OBLIGATION serviceRejection** + +In case of service rejection, the provider shall identify the obligation or prohibition which is not fulfilled either by the caller or the provider. The provider shall give an indication about any + +execution infrastructure problem. In this case, the level of detail indicated by the provider shall be dependent on the shared knowledge of the infrastructure on which the community is running. For the case where any wrong parameters have been passed to the provider, the return exception shall indicate these parameters. + +### OBLIGATION signalId + +Each resource in the community shall have the same signal identification. The community constitutes a layer network domain. + +### OBLIGATION viewingCapabilities + +The provider shall support a view of the resource properties and relationships that have been identified or permitted in the service contract with the caller. + +### OBLIGATION belongingConstraints + +All resources managed in the community actions shall belong to the community. + +### OBLIGATION architecturalConstraints + +All the modifications performed on the resources in the community shall respect the architectural constraints expressed in Recommendation G.852.2. + +### OBLIGATION topologicalLinkingEntity + +The actions of this community shall not modify a topological linking entity. + +## 6.4 Action + +### 6.4.1 Add transport entities to client linking entity + +This action is used to add one or more transport entities to a client linking entity. + +#### ACTION\_POLICY + +##### OBLIGATION supplyClientLinkingEntityId + +The caller shall uniquely identify a client linking entity which will contain the added transport entities. + +##### OBLIGATION noExistingClientLinkingEntity + +This action will fail if the supplied client linking entity does not exist within the layer network domain. In the case of failure, the provider shall return the identifier in error. + +##### OBLIGATION supplyProviderLinkingEntityId + +The caller shall uniquely identify a provider linking entity which has to contain the transport entities that shall be added. + +##### OBLIGATION noExistingProviderLinkingEntity + +This action will fail if the supplied provider linking entity does not exist within the layer network domain. In the case of failure, the provider shall return the identifier in error. + +##### PERMISSION identifyTransportEntities + +The caller may uniquely identify one or more transport entities (within the provider linking entity) that shall be added to the client linking entity. + +##### OBLIGATION failIfSelectedTransportEntitiesNotAvailable + +If PERMISSION identifyTransportEntities is part of the service contract the action will fail if at least one of the selected transport entities is not available within the provider linking entity. In this case the identification of this transport entity shall be given back to the caller. + +##### PERMISSION supplyNumberOfTransportEntities + +The caller may identify the number of transport entities (within the provider linking entity) that shall be added to the client linking entity. + +##### OBLIGATION failIfNotEnoughTransportEntitiesAvailable + +If PERMISSION supplyNumberOfTransportEntities is part of the service contract, the action will fail if there are not enough transport entities available within the provider linking entity. The number of requested transport entities shall be returned to the caller. + +##### PERMISSION requestAllTransportEntities + +The caller may request all available transport entities (within the provider linking entity) to be added to the client linking entity. + +##### OBLIGATION failIfProviderLinkingEntityHasNoAvailableTransportEntities + +If PERMISSION requestAllTransportEntities is part of the service contract, the action will fail if the provider linking entity does not have any available transport entities. In the case of failure, the provider shall return the identifier of the provider linking entity. + +##### OBLIGATION usePermission + +The action will fail if the caller does not use "one and only one" of the permissions identifyTransportEntities, supplyNumberOfTransportEntities or requestAllTransportEntities. + +##### OBLIGATION addTransportEntitiesToLinkingEntity + +The provider shall add the requested transport entities to the provider linking entity. + +##### OBLIGATION increaseCapacity + +In case of a successful action, the provider shall increase the capacity of the client linking entity by the number of transport entities added to this linking entity. + +##### OBLIGATION success + +In case of a successful action, the provider shall return to the caller the unique transport entity identifiers that have been added to the client linking entity. + +### 6.4.2 Remove transport entities from client linking entity + +This action is used to remove one or more transport entities from a client linking entity. + +#### ACTION\_POLICY + +##### OBLIGATION supplyClientLinkingEntityId + +The caller shall uniquely identify a client linking entity from which the transport entities shall be removed. + +##### OBLIGATION noExistingClientLinkingEntity + +This action will fail if the supplied client linking entity does not exist within the layer network domain. In the case of failure, the provider shall return the identifier in error. + +OBLIGATION identifyTransportEntities + +The caller shall identify one or more transport entities that shall be removed. + +OBLIGATION failIfSelectedTransportEntitiesNotAvailable + +The action will fail if at least one of the identified transport entities is not available. In this case, the identification of this transport entity shall be given back to the caller. + +OBLIGATION removeTransportEntitiesFromClientLinkingEntity + +The provider shall remove the identified transport entities from the client linking entity. + +OBLIGATION decreaseCapacity + +In case of a successful action, the provider shall decrease the capacity of the client linking entity by the number of transport entities removed from the client linking entity. + +OBLIGATION success + +In case of a successful action, the provider shall inform the caller that the action was successful. + +### **6.4.3 Report client linking entity capacity change** + +This action is used by the provider to report to the notification receiver the change of the number of transport entities in a client linking entity. + +#### **ACTION\_POLICY** + +OBLIGATION supplyClientLinkingEntityId + +When the capacity of the client linking entity has been changed, the notification receiver shall be informed by the provider of the identifier of this client linking entity. + +OBLIGATION informTransportEntityIdentifiers + +The notification receiver shall be informed by the provider of the identifiers of the transport entities that have been added to or removed from the client linking entity. + +# 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.10-199903-I_PDF-E/raw.md b/marked/G/T-REC-G.854.10-199903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..89ab6a3d0d4da5a3d5e4fa162d0a27fe70889ea7 --- /dev/null +++ b/marked/G/T-REC-G.854.10-199903-I_PDF-E/raw.md @@ -0,0 +1,944 @@ + + +![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.854.10** + +(03/99) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Digital networks – +Management of transport network + +--- + +**Computational viewpoint for pre-provisioned +link connection management** + +ITU-T Recommendation G.854.10 + +(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 PRE-PROVISIONED LINK CONNECTION MANAGEMENT** + +## **Summary** + +The pre-provisioned link connection management community is used to assign transport entities (link connections or connection termination points) to a caller and to control and update the available capacity of the linking entity (link or link end) that contains the transport entities. The available capacity of the linking entity contains all the unassigned transport entities. This community should be used in the case where transport entities have already been provisioned inside the linking entity using the pre-provisioned adaptation management service (See Recommendation G.853.8). + +The capability of having pre-provisioned transport entities is available in technologies such as SDH or WDM. + +Enterprise community actions covered by this specification: + +- COMMUNITY pre-provisioned linkConnection management; +- assign transport entities; +- de-assign transport entities; +- report transport entities change. + +## **Source** + +ITU-T Recommendation G.854.10 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 ..... | 2 | +| 7.1 | Query interfaces ..... | 2 | +| 7.2 | Operational interfaces ..... | 3 | +| 7.2.1 | PLCM Link Connection Assignment Interface ..... | 3 | +| 7.2.2 | PLCM NetworkCTP Assignment Interface ..... | 6 | +| 7.3 | Report interfaces ..... | 9 | +| 7.3.1 | PLCM Reporting Arcview Interface ..... | 9 | +| 7.3.2 | PLCM Reporting Pointview Interface ..... | 11 | +| 7.4 | ASN.1 supporting productions ..... | 14 | + + + +# **COMPUTATIONAL VIEWPOINT FOR PRE-PROVISIONED LINK CONNECTION MANAGEMENT** + +*(Geneva, 1999)* + +# **1 Scope** + +This computational viewpoint specification is related to the pre-provisioned linkConnection management enterprise specification defined in Recommendation G.852.10 and the pre-provisioned linkConnection management information specification defined in Recommendation G.853.10. + +# **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.10 (1999), *Enterprise viewpoint for pre-provisioned link connection management*. +- [4] 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: + +| | | +|---------|---------------------------------------| +| ASN.1 | Abstract Syntax Notation One | +| CTP | Connection Termination Point | +| Id | Identifier | +| Ifce | Interface | +| inv | invariant | +| ITU | International Telecommunication Union | +| layerND | layer Network Domain | +| LC | Link Connection | + +| | | +|--------|-------------------------------------------------| +| LE | Link End | +| LND | Layer Network Domain | +| pam | pre-provisioned adaptation management | +| plcm | pre-provisioned link connection management | +| RM-ODP | Reference Model for Open Distributed Processing | + +# 5 Conventions + +In order to increase the readability of the behaviour in the operations: + +- parameters are written in **bold**; +- elements defined in the information specification are written in *italic*. + +# 6 Label references + +| Full label reference | Local label reference | +|-----------------------------------------------------------------------|----------------------------| +| <"Rec. G.853.10", INFORMATION_OBJECT:plcmLayerNetworkDomain> | plcmLayerNetworkDomain | +| <"Rec. G.853.10", INFORMATION_OBJECT:plcmLink> | plcmLink | +| <"Rec. G.853.10", INFORMATION_OBJECT:plcmLinkConnection> | plcmLinkConnection | +| <"Rec. G.853.10", INFORMATION_OBJECT:plcmLinkEnd> | plcmLinkEnd | +| <"Rec. G.853.10", INFORMATION_OBJECT:plcmNetworkCTP> | plcmNetworkCTP | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:layerNetworkDomainIsMadeOf> | layerNetworkDomainIsMadeOf | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:linkHasLinkConnections> | linkHasLinkConnections | +| <"Rec. G.853.1", INFORMATION_RELATIONSHIP:link?EndHasNetworkCTPs> | linkEndHasNetworkCTPs | +| <"Rec. G.853.8", ATTRIBUTE:pamAvailableLinkCapacity> | pamAvailableLinkCapacity | +| <"Rec. G.853.10", ATTRIBUTE:plcmCallerId> | plcmCallerId | + +| Full ASN.1 production reference | Local label reference | +|----------------------------------------------------------|-----------------------| +| <"Rec. X.721:1992:Attribute-ASN1Module": SimpleNameType> | SimpleNameType | +| <"Rec. X.680:1997":INTEGER> | INTEGER | + +# 7 Interfaces + +This specification do 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 identification and properties of resources involved in the "pre-provisioned link connection management" community. As the invocation of 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 the following table with the information they allow access to. + +| Interface name | Information object | Attributes and relationships | +|---------------------------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| plcmLayerNetworkDomainQueryIfce | |

| +| plcmLinkQueryIfce | |




| +| plcmLinkConnectionQueryIfce | |





| +| plcmLinkEndQueryIfce | |




| +| plcmNetworkCTPQueryIfce | |




| + +## 7.2 Operational interfaces + +### 7.2.1 PLCM Link Connection Assignment Interface + +The plcm link connection assignment interface provides functionality for assigning link connections within links to callers. It satisfies the enterprise requirements stated in <"Rec. G.852.10", COMMUNITY: Pre-provisioned LinkConnection Management, ACTION: assign transport entities and ACTION: de-assign transport entities>. + +``` +COMPUTATIONAL_INTERFACE plcmAssignmentIfce { + OPERATION ; + OPERATION ; } +``` + +#### 7.2.1.1 assign Link Connection on Link + + + +OPERATION assignLinkConnectionOnLink { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce ::= PlcmLayerNetworkDomainQueryIfce +requestingCaller: plcmCallerId +involvedLink: PlcmLinkId +requestedLinkConnections: PlcmRequestedLinkConnectionChoice; + +##### OUTPUT\_PARAMETERS + +providedLinkConnections: SetOfLinkConnections; + +##### RAISED\_EXCEPTIONS + +linkAndLinkConnectionNotCompatible: involvedLink; +invalidLinkConnection: linkConnection; +notEnoughLinkConnections: numberOfLC ::= INTEGER; +linkConnectionAlreadyAssigned: linkConnection; +inconsistentSignalIdentification: NULL; +inconsistentDirectionality: NULL; +failureToSetLinkConnectionCallerId: NULL; +failureToDecreaseCapacity: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +requestingCaller: ; +involvedLink: ; +requestedLinkConnections ELEMENTS: ; +providedLinkConnections ELEMENTS: ; +linkConnection: ; + +##### PRE\_CONDITIONS + +inv\_linkAndLinkConnectionCompatible + +"**involvedLink** and **requestedLinkConnections** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_existingRequestedLinkConnections + +"**requestedLinkConnections** refers to *elementLC* in a relationship +where **involvedLink** refers to *containerLink*." + +-- NOTE – The following invariant is only needed when the *numberOfLC* choice is used for the +*requestedLinkConnections* by the caller. + +inv\_requestedLinkConnectionsAvailable + +"the number of available linkConnections in of **involvedLink** has to +be greater than or equal to the number of requested linkConnections referred to by +**requestedLinkConnections**." + +inv\_freeLinkConnections + +" of referred to by **requestedLinkConnections** must be +equal to NULL." + +##### POST\_CONDITIONS + +inv\_assignedLinkConnections +" of referred to by **requestedLinkConnections** must be set to the identifier of the caller referred to by **requestingCaller**." + +inv\_capacityDecrease +" of referred to by involvedLink has been decreased by the number (size of 'SET OF' **inrequestedLinkConnections**) of that have been requested to be assigned."; + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_linkAndLinkConnectionCompatible NOT\_VERIFIED RAISE\_EXCEPTION linkAndLinkConnectionNotCompatible; +IF PRE\_CONDITION inv\_existingRequestedLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION invalidLinkConnection; +IF PRE\_CONDITION inv\_requestedLinkConnectionsAvailable NOT\_VERIFIED RAISE\_EXCEPTION notEnoughLinkConnections; +IF PRE\_CONDITION inv\_freeLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION linkConnectionAlreadyAssigned; +IF PRE\_CONDITION NOT\_VERIFIED RAISE\_EXCEPTION inconsistentSignalIdentification; +IF PRE\_CONDITION NOT\_VERIFIED RAISE\_EXCEPTION inconsistentDirectionality; +IF POST\_CONDITION inv\_assignedLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION failureToSetLinkConnectionCallerId; +IF POST\_CONDITION inv\_capacityDecrease NOT\_VERIFIED RAISE\_EXCEPTION failureToDecreaseCapacity; + +; } + +#### 7.2.1.2 de-assign Link Connection on Link + + + +##### OPERATION de-assignLinkConnectionOnLink { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce := PlcmLayerNetworkDomainQueryIfce +requestingCaller: plcmCallerId +involvedLink: PlcmLinkId +involvedLinkConnections: SetOfLinkConnections; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +linkAndLinkConnectionNotCompatible: involvedLink; +invalidLinkConnection: linkConnection; +notAssignedToCaller: linkConnection; +failureToDe-assignLinkConnection: NULL; +failureToIncreaseCapacity: NULL; + +##### BEHAVIOUR + +###### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +requestingCaller: ; +involvedLink: ; +involvedLinkConnections ELEMENTS: ; +linkConnection: ; + +###### PRE\_CONDITIONS + +inv\_linkAndLinkConnectionCompatible + +"**involvedLink** and **involvedLinkConnections** shall refer to *element* of the same ** relationship where **layerND** refers to *containerLND*." + +inv\_existingDe-assignedLinkConnections + +"**involvedLinkConnections** refers to *elementLC* in a ** relationship where **involvedLink** refers to *containerLink*." + +inv\_callerAssignedLinkConnections + +"** of ** referred to by **involvedLinkConnections** must be equal to the identifier of **requestingCaller**." + +###### POST\_CONDITIONS + +inv\_de-assignedLinkConnections + +"** of ** referred to by **involvedLinkConnections** is equal to NULL." + +inv\_capacityIncrease + +"** of ** referred to by **involvedLink** has been increased by the number (size of 'SET OF' **ininvolvedLinkConnections**) of ** that have been requested to be de-assigned." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_linkAndLinkConnectionCompatible NOT\_VERIFIED RAISE\_EXCEPTION +linkAndLinkConnectionNotCompatible; + +IF PRE\_CONDITION inv\_existingDe-assignedLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION +invalidLinkConnection; + +IF PRE\_CONDITION inv\_callerAssignedLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION +notAssignedToCaller; + +IF POST\_CONDITION inv\_de-assignedLinkConnections NOT\_VERIFIED RAISE\_EXCEPTION +failureToDe-assignLinkConnection; + +IF POST\_CONDITION inv\_capacityIncrease NOT\_VERIFIED RAISE\_EXCEPTION +failureToIncreaseCapacity; + +;} + +### 7.2.2 PLCM NetworkCTP Assignment Interface + +The plcm networkCTP assignment interface provides functionality for assigning network CTPs within link ends to callers. It satisfies the enterprise requirements stated in <"Rec. G.852.10", COMMUNITY: Pre-provisioned LinkConnection Management, ACTION: assign transport entities and ACTION: de-assign transport entities>. + +COMPUTATIONAL\_INTERFACE plcmNetworkCTPAssignmentIfce { +    OPERATION ; +    OPERATION ; } + +#### 7.2.2.1 assign NetworkCTP on LinkEnd + + + +OPERATION assignNetworkCTPOnLinkEnd { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce := PlcmLayerNetworkDomainQueryIfce +requestingCaller: plcmCallerId +involvedLinkEnd: PlcmLinkEndId +requestedNetworkCTPs: PlcmRequestedNetworkCTPChoice; + +##### OUTPUT\_PARAMETERS + +providedNetworkCTPs: SetOfNetworkCTPs; + +##### RAISED\_EXCEPTIONS + +linkEndAndNetworkCTPNotCompatible: involvedLinkEnd; +invalidNetworkCTP: networkCTP; +notEnoughNetworkCTPs: numberOfNetworkCTPs ::= INTEGER; +networkCTPAlreadyAssigned: networkCTP; +inconsistentSignalIdentification: NULL; +inconsistentDirectionality: NULL; +failureToSetNetworkCTPCallerId: NULL; +failureToDecreaseCapacity: NULL; + +##### BEHAVIOUR + +##### SEMI\_FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +requestingCaller: ; +involvedLinkEnd: ; +requestedNetworkCTPs ELEMENTS: ; +providedNetworkCTPs ELEMENTS: ; +networkCTP: ; + +##### PRE\_CONDITIONS + +inv\_linkEndAndNetworkCTPCompatible + +"**involvedLinkEnd** and **requestedNetworkCTPs** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_existingRequestedNetworkCTPs + +"**requestedNetworkCTPs** refers to *elementCTP* in a relationship +where **involvedLinkEnd** refers to *containerLE*." + +-- NOTE – The following invariant is only needed when the *numberOfNetworkCTPs* choice is used for the +*requestedNetworkCTPs* by the caller. + +inv\_requestedNetworkCTPsAvailable + +"the number of available NetworkCTPs in of **involvedLinkEnd** has +to be greater than or equal to the number of requested NetworkCTPs referred to by +**requestedNetworkCTPs**." + +inv\_freeNetworkCTPs + +" of referred to by **requestedNetworkCTPs** must be equal +to NULL." + +##### POST\_CONDITIONS + +inv\_assignedNetworkCTPs + +" of referred to by **requestedNetworkCTPs** must be set to +the identifier of the caller referred to by **requestingCaller**." + +inv\_capacityDecrease + +" of referred to by **involvedLinkEnd** has been +decreased by the number (size of 'SET OF' in **requestedNetworkCTPs**) of plcmlayerNetworkCTPs that +have been requested to be assigned." + +##### EXCEPTIONS + +``` + IF PRE_CONDITION inv_linkEndAndNetworkCTPCompatible NOT_VERIFIED RAISE_EXCEPTION + linkEndAndNetworkCTPNotCompatible; + IF PRE_CONDITION inv_existingRequestedNetworkCTPs NOT_VERIFIED RAISE_EXCEPTION + invalidNetworkCTP; + IF PRE_CONDITION inv_requestedNetworkCTPsAvailable NOT_VERIFIED RAISE_EXCEPTION + notEnoughNetworkCTPs; + IF PRE_CONDITION inv_freeNetworkCTPs NOT_VERIFIED RAISE_EXCEPTION + networkCTPAlreadyAssigned; + IF PRE_CONDITION NOT_VERIFIED RAISE_EXCEPTION inconsistentSignalIdentification; + IF PRE_CONDITION NOT_VERIFIED RAISE_EXCEPTION inconsistentDirectionality; + IF POST_CONDITION inv_assignedNetworkCTPs NOT_VERIFIED RAISE_EXCEPTION + failureToSetNetworkCTPCallerId; + IF POST_CONDITION inv_capacityDecrease NOT_VERIFIED RAISE_EXCEPTION + failureToDecreaseCapacity; +; } +``` + +#### 7.2.2.2 de-assign NetworkCTP on LinkEnd + + + +OPERATION de-assignNetworkCTPOnLinkEnd { + +##### INPUT\_PARAMETERS + +``` + layerND: layerNetworkDomainIfce ::= PlcmLayerNetworkDomainQueryIfce + requestingCaller: plcmCallerId + involvedLinkEnd: PlcmLinkEndId + involvedNetworkCTPs: SetOfNetworkCTPs; +``` + +##### OUTPUT\_PARAMETERS + +``` +-- none +``` + +##### RAISED\_EXCEPTIONS + +``` + linkEndAndNetworkCTPNotCompatible: involvedLinkEnd; + invalidNetworkCTP: networkCTP; + notAssignedToCaller: networkCTP; + failureToDe-assignNetworkCTP: NULL; + failureToIncreaseCapacity: NULL; +``` + +##### BEHAVIOUR + +##### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +``` + layerND: ; + requestingCaller: ; + involvedLinkEnd: ; + involvedNetworkCTPs ELEMENTS: ; + networkCTP: ; +``` + +##### PRE\_CONDITIONS + +``` + inv_linkEndAndNetworkCTPCompatible + "involvedLinkEnd and involvedNetworkCTPs shall refer to element of the same + relationship where layerND refers to containerLND." +``` + +inv\_existingDe-assignedNetworkCTPs + "involvedNetworkCTPs refers to *elementCTP* in a relationship where + involvedLinkEnd refers to *containerLE*." + +inv\_callerAssignedNetworkCTPs + " of referred to by involvedNetworkCTPs must be equal to + the identifier of requestingCaller." + +##### POST\_CONDITIONS + +inv\_de-assignedNetworkCTPs + " of referred to by involvedNetworkCTPs is equal to + NULL." + +inv\_capacityIncrease + " of referred to by involvedLinkEnd has been + increased by the number (size of 'SET OF' ininvolvedNetworkCTPs) of plcmNetworkCTPs that + have been requested to be de-assigned." + +##### EXCEPTIONS + +IF PRE\_CONDITION inv\_linkEndAndNetworkCTPCompatible NOT\_VERIFIED RAISE\_EXCEPTION + linkEndAndNetworkCTPNotCompatible; + IF PRE\_CONDITION inv\_existingDe-assignedNetworkCTPs NOT\_VERIFIED RAISE\_EXCEPTION + invalidNetworkCTP; + IF PRE\_CONDITION inv\_callerAssignedNetworkCTPs NOT\_VERIFIED RAISE\_EXCEPTION + notAssignedToCaller; + IF POST\_CONDITION inv\_de-assignedNetworkCTPs NOT\_VERIFIED RAISE\_EXCEPTION + failureToDe-assignNetworkCTP; + IF POST\_CONDITION inv\_capacityIncrease NOT\_VERIFIED RAISE\_EXCEPTION + failureToIncreaseCapacity; + +;} + +## 7.3 Report interfaces + +### 7.3.1 PLCM Reporting Arcview Interface + +The plcm reporting arcview interface provides functionality for the reporting of the assignment of link connections to callers and for the de-assignment from callers. It satisfies the enterprise requirements stated in <"Rec. G.852.10", COMMUNITY: Pre-provisioned LinkConnection Management, ACTION: report transport entities change>. + +COMPUTATIONAL\_INTERFACE plcmReportingArcviewIfce { + OPERATION ; + OPERATION ; } + +#### 7.3.1.1 Report Link Connection Assigned On Link + + + +OPERATION reportLinkConnectionAssignedOnLink { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce := PlcmLayerNetworkDomainQueryIfce + involvedCaller: plcmCallerId + involvedLink: PlcmLinkId + assignedLinkConnections: SetOfLinkConnections; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +##### BEHAVIOUR + +##### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; +involvedCaller: ; +involvedLink: ; +assignedLinkConnections ELEMENTS: ; + +##### TRIGGERING\_CONDITIONS + +##### PRE-CONDITIONS + +inv\_linkAndLinkConnectionExistingAndCompatible +" **involvedLink** and **assignedLinkConnections** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_involvedLinkAndAssignedLinkConnectionsCompatible +" **assignedLinkConnections** refers to *elementLC* in a relationship +where **involvedLink** refers to *containerLink*." + +inv\_freeLinkConnections +" of referred to by **assignedLinkConnections** must be +equal to NULL. "; + +##### POST\_CONDITIONS + +inv\_assignedLinkConnection +" of referred to by **assignedLinkConnections** must be set +to the identifier of the caller referred to by **involvedCaller**." + +inv\_capacityDecrease +" of referred to by **involvedLink** has been decreased by +the number of plcmlinkConnections that have been requested to be assigned. "; + +##### EXCEPTIONS + +-- none + +;} + +#### 7.3.1.2 Report Link Connection De-Assigned On Link + + + +OPERATION reportLinkConnectionDe-assignOnLink { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce ::= PlcmLayerNetworkDomainQueryIfce +involvedLink: PlcmLinkId +de-assignedLinkConnections: SetOfLinkConnections; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +##### BEHAVIOUR + +##### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerND: ; + +involvedLink: ; + +de-assignedLinkConnections ELEMENTS: ; + +##### TRIGGERING\_CONDITIONS + +##### PRE-CONDITIONS + +inv\_linkAndLinkConnectionExistingAndCompatible + +"**involvedLink** and **de-assignedLinkConnections** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_involvedLinkAndDe-assignedLinkConnectionsCompatible + +"**de-assignedLinkConnections** refers to *elementLC* in a relationship +where **involvedLink** refers to *containerLink*." + +inv\_assignedLinkConnections + +" of referred to by **de-assignedLinkConnections** is +different from NULL." + +##### POST\_CONDITIONS + +inv\_de-assignedLinkConnections + +" of referred to by **de-assignedLinkConnections** is equal +to NULL." + +inv\_capacityIncrease + +" of referred to by **involvedLink** has been increased by +the number of plcLinkConnections that have been requested to be de-assigned." + +##### EXCEPTIONS + +-- none + +;} + +### 7.3.2 PLCM Reporting Pointview Interface + +The plc reporting pointview interface provides functionality for the reporting of the assignment of network CTPs to callers and for the de-assignment from callers. It satisfies the enterprise requirements stated in <"Rec. G.852.10", COMMUNITY: Pre-provisioned LinkConnection Management, ACTION: report transport entities change> + +``` +COMPUTATIONAL_INTERFACE plcReportingPointviewIfce { + OPERATION ; + OPERATION ; } +``` + +#### 7.3.2.1 Report Network CTP Assigned On Link End + + + +OPERATION reportNetworkCTPAssignedOnLinkEnd { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce ::= PlcmLayerNetworkDomainQueryIfce +involvedCaller: plcmCallerId +involvedLinkEnd: PlcmLinkEndId +assignedNetworkCTPs: SetOfNetworkCTPs; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +##### BEHAVIOUR + +##### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerNDId: ; +involvedCaller: ; +involvedLinkEnd: ; +assignedNetworkCTPs ELEMENTS: ; + +##### TRIGGERING\_CONDITIONS + +##### PRE-CONDITIONS + +inv\_linkAndLinkConnectionExistingAndCompatible + +"**involvedLinkEnd** and **requestedNetworkCTPs** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_involvedLinkEndAndAssignedNetworkCTPsCompatible + +"**assignedNetworkCTPs** refers to *elementCTP* in a relationship where +**involvedLinkEnd** refers to *containerLE*." + +inv\_freeNetworkCTPs + +" of referred to by **assignedNetworkCTPs** must be equal to +NULL." + +##### POST\_CONDITIONS + +inv\_assignedNetworkCTP + +" of referred to by **assignedNetworkCTPs** must be set to the +identifier of the caller referred to by **involvedCaller**." + +inv\_capacityDecrease + +" of referred to by **involvedLinkEnd** has been +decreased by the number of plcmNetworkCTPs that have been requested to be assigned." + +##### EXCEPTIONS + +-- none + +;} + +#### 7.3.2.2 Report network CTP de-assigned on link end + + + +OPERATION reportNetworkCTPDe-assignOnLinkEnd { + +##### INPUT\_PARAMETERS + +layerND: layerNetworkDomainIfce ::= PlcmLayerNetworkDomainQueryIfce +involvedLinkEnd: PlcmLinkEndId +de-assignedNetworkCTPs: SetOfNetworkCTPs; + +##### OUTPUT\_PARAMETERS + +-- none + +##### RAISED\_EXCEPTIONS + +-- none + +##### BEHAVIOUR + +##### SEMI-FORMAL + +##### PARAMETER\_MATCHING + +layerNDId: ; +involvedLinkEnd: ; +de-assignedNetworkCTPs ELEMENTS: ; + +##### TRIGGERING\_CONDITIONS + +##### PRE-CONDITIONS + +inv\_linkAndLinkConnectionExistingAndCompatible + +"**involvedLinkEnd** and **de-assignedNetworkCTPs** shall refer to *element* of the same + relationship where **layerND** refers to *containerLND*." + +inv\_involvedLinkEndAndDe-assignedNetworkCTPsCompatible + +"**de-assignedNetworkCTPs** refers to *elementCTP* in a relationship where +**involvedLinkEnd** refers to *containerLE*." + +inv\_assignedNetworkCTPs + +" of referred to by **de-assignedNetworkCTPs** is different from +NULL." + +##### POST\_CONDITIONS + +inv\_de-assignedNetworkCTPs + +" of referred to by **de-assignedNetworkCTPs** is equal to NULL." + +inv\_capacityIncrease + +" of referred to by **involvedLinkEnd** has been increased +by the number of plcmNetworkCTPs that have been requested to be de-assigned." + +##### EXCEPTIONS + +-- none + +;} + +## 7.4 ASN.1 supporting productions + +This subclause defines the ASN.1 productions which are used within other ASN.1 productions in the operations. + +In this Recommendation, 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. + +``` +PlcmLinkEndId ::= CHOICE { + linkEndQueryInterface PlcmLinkEndQueryInterface, + userIdentifier SimpleNameType }; + +PlcmLinkId ::= CHOICE { + linkQueryInterface PlcmLinkQueryInterface, + userIdentifier SimpleNameType }; + +PlcmRequestedLinkConnectionChoice ::= CHOICE { + plcmlinkConnections SetOfLinkConnections, + numberOfLC INTEGER }; + +PlcmRequestedNetworkCTPChoice ::= CHOICE { + plcmlinkNetworkCTPs SetOfNetworkCTPs, + numberOfNetworkCTPs INTEGER }; + +SetOfLinkConnections ::= SET OF CHOICE { + linkConnectionId PlcmLinkConnectionQueryIfce, + userIdentifier SimpleNameType }; + +SetOfNetworkCTPs ::= SET OF CHOICE { + networkCTPId PlcmNetworkCTPQueryIfce, + 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 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.8-199903-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18e1aaf1566dd8b6b6980774e5b0f748a5a140a6 --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ce10f9677549e6b4cd8987c383b4a4a359108f2c2de61b39bb49bf6bde615b +size 85807 diff --git a/marked/G/T-REC-G.854.8-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7da83ecb82b51a4cef7694858eef2c35f1986ff --- /dev/null +++ b/marked/G/T-REC-G.854.8-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.8-199903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81eb3ed73a1650f71f3b8ed1655e4e11d45e22f3 --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04b625c09cef7ece3e568b36cb82b4207b0e5155d81829ee6cde67338c5a6a60 +size 88308 diff --git a/marked/G/T-REC-G.854.8-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b1d6e1fb471e37a08b1ef3188610c399daf2ecb --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:232b6485d7f2901f11cbd012946a2af86e11d542f5f11bb1426bc322db180475 +size 24951 diff --git a/marked/G/T-REC-G.854.8-199903-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbc3b5a7b6208d7a8b5af520aabd24b3f4ea7007 --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8adffaf86dd0b23dd3ea57d1d6c2245929b44b3e584b6a493f4281f441b35398 +size 28689 diff --git a/marked/G/T-REC-G.854.8-199903-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47e3c1ea8118de405b5e411eb17deb057398e392 --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad5a9611edc55bb4a0892c8e9ea0b7b62d2c6974cf0fbf9a2e2f84b1bd4df6b0 +size 64359 diff --git a/marked/G/T-REC-G.854.8-199903-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.854.8-199903-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..715f7aa74b0032f402228b25ef5044c95634394d --- /dev/null +++ b/marked/G/T-REC-G.854.8-199903-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3e6ceb187f8ae9ab6532326cc31d2642523e4f842773f6b9890144207e312ca +size 38078 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/01465752f3ac36c403672804f406a676_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/01465752f3ac36c403672804f406a676_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b6789e39e1e4245a00d45e410cfb4f43369fde7 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/01465752f3ac36c403672804f406a676_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70891f5546ed929335f721a3f75b1fcd151f51b6a1ff581b291312b4a9c336d +size 17080 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..642cc7d9871cb85efdc52a94b8e5c2d35d7d9fa8 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/014daefdecf9d847ca82cb5b9f50731f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3330cffc9da4f789faddcb3c36ad3c5f6c48f7c1e9f8c7574f13ff2b471aa77e +size 28072 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42e7cd3fff3034dfb55b65780eb54e42005b88d1 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e63d63786d4b2d9d1ae68707e23bef40a167e17c4e284be45cfe77d34ebb772 +size 26621 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faa395befd3043250d5e5216b927b52551e46730 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f33bb33d2d468b18c01518cac9d068af71cedb9a101d3938d22c2d3da702fb3f +size 17993 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0875656f74739df169f9a22cd3099e8406461e2 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/15de63f0b5df62e6ab9164f2a72e2e33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6cbe7490e678ab81c4d078fa2260fd3d11ab7563b439c5e6adbd1a9fa9e790d3 +size 285933 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a67b548f042b4841c115004a5a5eacdc61cec70 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d59844940921289250dc8a6c1c890d103f2d38bcb3cfc74be61ce989ea20f3b +size 29251 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9002ee68e2b9ebf63d27d39ba8c73bdafb0e6be6 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df701536c25ab8246d2868de3c20c8a4e25168bb52c5eb9078278ab1b5b4fd8 +size 6859 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b96436d52438a911d5de0b48a99780f2b242589e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/24ba47df8be44ae91945d88ce2232df5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0040ccb86799e673c42d4d686f77212436cc3435175558319c85ccb17069884e +size 230199 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be37ae66bd4e61869a537f0a9abd0bc68e29f2f --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/29043c6ca27a7cfbc757a5d2eb029d33_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37526f12fcd7aa007c27d53cacf5e954abad5fa2e3f048f8dac3b438f4a1af83 +size 270363 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0597cf198afbe65255f6fb10b7f234a326d6412 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f386ae84b95626662953dd2a7aa9c0acf0ba7af36f90288707cec1b8800378a8 +size 75830 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..817477b4fada943487df62cebbe7812a1c507841 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/2dd10dd89365981b6b6154de6390a602_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b5b35546205b2b9b45a52af7120679ac2e1b640376d019b016982aa7ac1fbd2 +size 27074 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3348c430b981204df1c88effdda909a96c98c50d --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/32d36dfe7dc75b7c63f8edf0f28e4009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:633ba4e6af1840623f4b7d739ba79b1cbeb0a24d20f8188d98965d419e081cdc +size 260123 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7cd09ef99858b71d09c807f5076e1150bc62db1 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/352d21d1e740e4a58cb17ab8656cfad8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b675711d73ff4a894a107c94544ffc918423898346c0af3c7ad01f72a826909 +size 19368 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a93ca214bba3083184800b25285e40976b04d33 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/3d6f5edac3d5e7113d960c2202f1b0fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87263381a0ccd84c1260288d950d240457285ed2391950492ed69e3b3b023bae +size 24204 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7d21c8e809756f7bfc587edd9ae9a3b054a8fa7 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/4162c218fc7881cd90fc9574e07d2327_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8ac1d7ab9e84f7d3e280cd1deb03aa219f004d939a62d7cc7701c2e801c065d +size 35565 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c69fad0de77809331513d2898749f5fe33c934 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:657c849610cb935278b23b9ac40cd778be49e1361619bf9c985caac6fac21d3e +size 18842 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474706d3f20ec29992808880e41493eaf8d4f5af --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/51d4540605fdfa2c090638305022143b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7360830583606c9f9e289496d20ae0b80527d29e52ecf27f71be2fd5374373d +size 103312 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/524cc6038f81916add4e259efa7e780b_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/524cc6038f81916add4e259efa7e780b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6363cd224d62efa591a3161318c608d01060168 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/524cc6038f81916add4e259efa7e780b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:564c7a6ca4991753c2eee900639dccdb83582972090940987307438301c0764f +size 213696 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3471e537e81750ac4e988349b2e9dc982a2f79e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfd195f4e5012508f56ba1203b3e2cd193a0d027a3a03d12706e7de3583ad920 +size 26644 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0faff0e3de1da86b88483a6644a5a1c22eb3dc93 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273a3ae9d0700cec8671fcfcc8073f9ad3ce26497d7fe6000ece1021157d067f +size 198579 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ab81080ed5f8b0597746f10b997156069979b28 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:865d6afe683c37703349134e67db020a910d74b8a23067634cd570790c10392c +size 239090 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98898c1bff2a78c810118e1b3339c7508c5c9d67 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17787a2abe0c8894191b5af013a32d5c329d85b1ef21c222c3e1cc2dc7d2eaa +size 55309 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cfac6a219ac3bd9856eb4e7595415fd0eeb39ff --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:997b647d57c4261ecb782b2723e03efd372618cfe4c5a6b763c2e99938b18a3c +size 51969 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/69733eeb3ef32197543f66f22a431771_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/69733eeb3ef32197543f66f22a431771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d1e8628832e4d9e19ec5bdbd5b5e9f68163f8a5 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/69733eeb3ef32197543f66f22a431771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c72edbd2310e000a4521704ef2626b26c56980f87f8b39889c55383db0490f1 +size 26848 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e66be56c869586c08ee993b0e2a6abdeea0e8c53 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/6a7ea9d5162b0a0cfbd8d77c6cac90d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14b98c96e4b7dadc350f3228cace0cbcb2dcd3c782f8d00893f270147f23dc93 +size 292818 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..999da5478ddcb347e3d518b1e765ffed19e821ae --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c47f8ba8a5ae39d21c221cee344199b9332aaf2c11ed58767ea63dc13516e518 +size 46358 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b12c2e0f39b8d0fe5a0f27b9c827c3118b8433f --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:349b7cf797f2523058e8ac423144dce05ad3296326ab96e83e664ca2e22419ef +size 60347 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04fd4f686adffb9075bdb2f42b268dc9dce0b451 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccb551be0e83063e2638541cbd8a20b8266a3484f412c2fc3fd2c16247566742 +size 63000 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4913547c52260d0750c071eec66de93bf209a8e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0c49116b404f1d0992b6b702b81f725550782e801755cc1c94b99e524755c26 +size 102730 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d95172a885821ed2174f8b9f048eee23a850873e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/7ec36a0a9788e1cb33df5372695498c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ffdfd966ae71efcc9d6091f43a70a66e9dc82fda55bcdb7952f86e6032d497b +size 245755 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..127da93c877001df298bce161c0679594db65d69 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/811d62d08ce934a2a7e5bd877abff7ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:138886ece22e8fbcfb1f867bc413ce92a9d7c5323c55bc2a7de61dfbee3ff872 +size 236064 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98d0cd7588bebabd3189292ebbf3cea12113648 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6214c28f157af04e49129db538513c57e18a5c13e7975e7f4fc2811a9ba99991 +size 56724 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0d4c82a1f3e264be5f3b74a8f780e7e8da6c52a --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bbffe2510bc7edc8382790011414d498579e6941f58c94d980c16582cbb7a15 +size 62152 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75d6b562f677eb2b8237e76eda98db40eecd4494 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cef9800fa70e336c20a1e5ac52be62c65edd1b9543be52a9f023e3efce3f0f28 +size 64488 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d737ab5cea60d925db411ae91801706b599e125d --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/909726977de6efd2d4df015198a2907b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04725a456137ba7002c97dbd81e7c959a83bc880d27637ce56b1e95b0b7a8b85 +size 28318 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc476b23eac51f91c4309500802c322c75153716 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea48d86a303843defbd3a0d4a5a8f5793f1aab486be5f4b8f9fc5b93a4b2da0e +size 129929 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fcf4c53e61442a74b28ae812f6ff586d1405c83 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a842398fa706adc0bbf4e5737b1505e085131841c9531a6d7b7f94c2e83c8021 +size 116981 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3d940878cef4e8c52725cc8aa9a4940f7a98af8 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/99698c448635861b7dc8d352f87a1b2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbca0d24545bcf68df3ea5df97f784d878636d7d52c0461f7b39ec48fd2e7574 +size 238943 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d27cfd7ecb90cbd08447c1073e408499affa7c8e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e7f9e10e7062fc60e631beef70080857b4618a77869c307b6d6220ebe0e9bb5 +size 72480 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc4785b4b9a5bac6d1ed39a1aeff04136b6e8100 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8252b05c0c6949a19001f78087cbe421a27ec9abf5910928117ac5ef21855eed +size 57287 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c10a20cc97b730614857689a4a16f872bf455daf --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a447b2987d1c97785a18fc8c036ab70c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3242036f4c1207d1131baec7367a8313a55a8345ba914030b428304b1994fd82 +size 10106 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ec2476979fadeaaec15f4fa80acc8a07e36c596 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05bf68ca65b227cb3637b7f6ab8ffcc89254cfa4e34cf4756f590faf63ef904c +size 53125 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7357deb2f4298ec4e52ed7669bc2217ecb72285 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d414f795d7763a8328ba14151ce77b12d275dea8e336f19a57930c3257db06be +size 41841 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1df8aca387d517e4639398972670141bb23aa63 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d11e617c01957cda6278fd628dff67bb173e3211a971c6b305be2d5380156de +size 54098 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9286722ec73bc2e56cd554e91b77ae75c2c9450f --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35db892d4f03aa7e2841cca5f323980d9ee411c83e18ffb925cb02758f310e56 +size 151757 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03615a109f5aa781e0e1a49e7559ac882ec547e0 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b20942bb14022381a243971ab9790dd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ee51650ae9bf7bd6637b06d7dc84914b07978216356f1db6eaadc93b5e56604 +size 294214 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6e96879f41ff693c9e652ccaa1fda07e37dac03 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b3335932702b8668e62791e9fd12c9ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83c47078674efe7f1434b5645abc389807c0e9372f25ba6a764dc6e7d9ff0cd0 +size 11539 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec689458852a72667787be2edeaa3e3ae62aad2f --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/b68ed2f7c90787b2fcfeb6be5640ecd4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90d9abb6074bad5c6f2df4a598f555999f158ebc25655c9450ce777dd396978a +size 19395 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ea99abbcf0603b6b516495cf3e4d574ca6d1be7 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d15918d6f8effd47a8e87ba934f3d5074879354c4183bd1f84b74dd284d8ef7f +size 161038 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29efa8a051f435b0abd247621c1c5609fccef6fe --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a15f44c7a599b6dbfdf4a2d8a023a20dbdfc89b4e861f541c6adce54195ce7 +size 94360 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..637bacea4b7c952e988aa2e2334f9bd18cc1a34a --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1303ed8f8b9ed42f3fdc21520ffcee000cff2207ce86eff35fdb7daaaeeb57e8 +size 26419 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3a69a0db2657845b4b9e5ed0796df0e61852016 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7bd7e6f2b4cbec597b2999e06938ca804c2166b970469c012bf420c5fc8f2d1 +size 258179 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bd7829fc1e086a42d9d6a1ddf1a6ec350394bbe --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed86a9a80df482372d9206ff22f7b78509ffa61367d4faa0f734adbc4d08788d +size 47506 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf603884a32bb52a0a2255e185cf7d101038d2ce --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e531b0f9f0c5e4dc3d92abcd4ae2428906b27d822cae053bb597521114ab9cc +size 55519 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71b78dc797bf290787c0cf0758f01856f0c7765b --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d6373f941d64d7a8f553bf68bdf57650e9da1ca75f239696f694595919dc6f9 +size 166761 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a229b9ff0f8be77a4d6c3b94e5a45139dda4beb4 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fed5dbbca0f54d3bb16e7ce9d2a90feb17c19a308dda0fda5fb9b24f6f79222 +size 112818 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..022d625a002597e7601743286730b10e7ad8abdc --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d155a1511db57a83e3f7f7c6172e1939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:887e070ba2c44bbb7250755d44bf50c033798f46545adbb09c2175ae224260d9 +size 261621 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d197b6ded14ea918198a280ff07122b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f547066ae4942e80c389c0173cbf71a88dc192d --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d197b6ded14ea918198a280ff07122b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f21246e966b39567dbe1d77676764ff8b18a58820b3d22afc64fc3e3ab71c0d8 +size 28061 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c391bdc9d50b695835516bb77c9ae1c1e3f261b4 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2786b576b5e50e32860ce44560ea470c4cdc40c50d3578009b1914d9a4308352 +size 175381 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fe13488ae7268df065a6934fa895fdfcd9b44ae --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53983058ef1f1ead1cacdbda07fa627762d701e3f1f49dbd1293e67bc977847e +size 218317 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8f2d7f4909190592e2b796310162a425bb6c8ee --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b08017612ab49b971d3da6a4a0523fdc5fb3486bb0e807f0a34b4f29fa68f191 +size 78414 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf8bce9fa9404b6bf9ef5a41b9193da568936a4d --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dca52dcbce29c5d3a9f07346d7ad296c6b65f1c472f1bf50267ce71fa17c4d6f +size 28308 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b70a33093c9b6e29962b798d671ace6aa5f0bf38 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e280069386f9f6c3b4bbcf8ea26411ec10eaeab22ffca0a7207d05fb99db27eb +size 28413 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83c89eea922aafe9af1544b298a56cf36c622ba4 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/dbd074feb5cce1300f42f91da8f673d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56b26509e3197dab86e94946027a3eb1f9fce4e837e84a57b344fca753f7a00a +size 25474 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dd963bfc3ec6201776cfbbe0105efac9ea2b8dd --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:805a676062cb98499df5aee1b0f25acbe754c4f8a964c65a52a23c7415f3a72e +size 177149 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23a18b3c787ca0d3646ada9b40a704161ab38a6b --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae56a022b7c9296138346468c84cc0526a4e54652cc28f61ee976e80399d906f +size 61220 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b10f2b2527db8653bcec9955a5fd777a14a6f92e --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ce218002871e4005ddf6f0c97bb984448be34c77ab6add4aac7bca998f4cfbd +size 54784 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8fb4ff0148b54d64b48c5740dcd4d820d183cd1 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e2dad48ec062e71202459a9ab82261e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27d4c6d27fb3a8713b7a5edcae568ff37f7d7aad263be0227f20f9d6f8183b10 +size 229623 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74ef63cca160af796fc25e7e25010feca77d6612 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af67f35519cb358c1fb9a7a7c8ecb05711dd1ab89579ef79258a867825fb4b75 +size 203625 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a437079db67ddbcdb3bc09c1ed0fa79c61b23c9 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ec96d99a16edb981eb7defe41a79b57f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b4222ac8f2adb0afa238653786a52f6095851065045e80115dae556ee4bbdaf +size 168693 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c764c968b170eeb158393b9fa001e1d610d05424 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f1144e794c1d5c92a8f278bdb17cb54221f29f0a6606b9dedb3dc83744f8bd7 +size 33001 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b68825df9ad577aa6a5472d03ac893cab0d3a1f3 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb6c30e2507d27a94f0d01e8d0a30bb42b8fa10b81c40eabea77abdf08fb4345 +size 132150 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..256efac34d3a56c0655152aa9278b922f8899321 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f1fb809a944095f787c85ea0c6992c7ad99a029487fafc6197b462f0be222f8 +size 57778 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff3417b75213b8688e6504a21220b430_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff3417b75213b8688e6504a21220b430_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0642e111819483c5d7d31a550260b06f70e2e9ae --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff3417b75213b8688e6504a21220b430_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0498ed00c5352c260b8db870c1a8fec077b3343bd0a073ab654ac70ffc791a4e +size 59250 diff --git a/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d33178937d469f36d9693458ffc3aa96114aed7 --- /dev/null +++ b/marked/G/T-REC-G.873.2-201508-I_PDF-E/ff87509cc2b267501d910a2d9f9054ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:001a8c7f6373bad599eb5f91fd8520c9e4588406dde8850367956191d3413167 +size 53889 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.875-202412-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.875-202412-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a15c01c98087428f66fa262c493ec4c4dd7803cb --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7871be605aeabad8338d23e4a56af914ed87fa8bd0b1e7983fcc6e60629175e7 +size 137986 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03200fb52ce03149496e72aeefd9355f4709d4fe --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/0c08e48c08f96934cd6bc6911f3069dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55f86936069bb901268c514ccbe354fccd03303c62b52b622b0f76029b04fd32 +size 69958 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67c06c7c130d9de15680a5718d68198f40c46d55 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a63468e45472b7a1e28d2471180f2b5fb34bd41117ed094db70f2ca834b1896b +size 106939 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90feea0725f39e450d313a0d3ac101560cffb6d8 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bbe37e280303222f76950ee3c5a51c0f11fbb06afa70c5e26ee8c2c791b0e86 +size 86856 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2211365d433af5a4539d928947da967019141dd --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/1cd6a2d6e58e0e6d75c879a999be06ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89568c5180b3cb9b43c424fca5bf31581e73be634ffd4f8aec7f5818c9f40dc7 +size 92234 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..025d295d1bc8a7ab3d4655356cb210cd7c06deaa --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/1ddf3a99e7935a2f5f85e7f7e038e2fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc33713aa1a81c57a898ae67fc8be60f645233498b932ee6a983da0bcd48df01 +size 47042 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6a1a36b9d8022c43004c85eb7aa0163c619a0a9 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc3810729031a224571fd533d4f3c208ebe8ec3200378a84e53a1570ca352972 +size 37035 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcbf58687392604b7cb1b2d4b1d31072f6f8073b --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/3121ebddccf183ca63bb9781be440a7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ea241c0a50564f2dcd4ea5918d04319bf81e8f20778fb8efb733d8cf6154d7c +size 39350 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d8012480cc384cd52c36fb3c722fb82e6a884b4 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:017708e15013de42257c7d87ac34f454a5702d2c31b76332951ba7e1d8ccd345 +size 95841 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a78f8f86220105ee2f28272636474f1973f93fde --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebbe4feb9f03ebcf47982a2a76fda7566808151822fbce5bdfeab83fc534e118 +size 64717 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c251ee018a26c0a5dbf310e6f122696c0fd0bebb --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da12180c770af461ac9af4776cf869b0bfa1800ddf40ebdf3b2179ba08115305 +size 70033 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b49c7c104e7e24b8b6606fdc3ac4ab66531ee2d5 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f071a3a8cd7923d5f53b117a7ea31afca71ba0cf6aba360b679d0d1d5ec3667 +size 52607 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd4474cd940b35f15cfd83a1cb62d22485d830d3 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9c79069e2a2756cbf9eb07241915aad79820b4086c0ea4f14f72e64005119b8 +size 56313 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fecc4c4a154ff146e96e173f7b21bfe433a60a9 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bfcebe0a082e35ffb37c32c75bc0e9401da510a052e7b59665735d5cad5527c +size 92106 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f26833022bb2fe998b60af814c7a21e5cdf97805 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87b9ce217ecffad57dd40ae71e2812ddef8ac247260bd5749c5dc644b3a71da8 +size 90943 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0dcf89cf304cca15dbaf3e5cd6daba10fbe84a6 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/69b7bd65e85cdef6fdd7fb0a8194257c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6094b284fc0eb541ef20967adbd8b8d27831eaf46413a64afb19b633edebfe3c +size 60421 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e369a9a73656726b02ecf01f922fe5bd641e877 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/7f25db95ce3916c0e09803b861a2f7bc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dbb83d8ecdba2989dac2e7c53e0f48c3acb2fa034d4db018e2820929e84ba90 +size 80949 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4840c838b0ac0e279e381be33c309aebfe637a57 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b6a49a3e7f5f0216afab01d81523240fa4d2b1ab1cc3b88b1e3b228aca4480b +size 36817 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..227df17410dfedf6538856040d8d98e1b01854f7 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/878d9539700bd792e7d12ad6f1203c5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef04c63795650857d3f9136ca3ffbcd250ffe4aabeca1b69dca457b12263a6be +size 110630 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f224371cd3aa5722b108c3a43daa9dfe2f1906a6 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4373e11257da96ba4eed4145122126b0a103dd1263ff128ae438e599071b6626 +size 60672 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8665a23d017213fd0291d45014e7bc808f9479ee --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:295e1915f514ee44bb06ae834778f16a5e10d8c2a2799db0fc187d8f85fad20f +size 111910 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e21ce15c98e0b519315bef0d164afbacc2f2b783 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/9a5927586a691c4908aa2cf98bd47ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ded2de58a58e69e228b9214a76d531e73b84bbdbf3793677f3816163351967e7 +size 73623 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a063e3555bfc13375df5830a0712378f57e452d1 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e44f7d661bd7e83402423b64e757212e58b879deb817ddafd94319b5e8a48477 +size 71392 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b74f19109ed5fe7c262a8537358e6d477a96b238 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46d4f345fa5747bced0fd7859b83930402510e9059ca93b277de03a2f43f5673 +size 66649 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eef42eabc40b39d9ef3a860c5b6f02375e125db6 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fd3b829be23f25ce39ae486da4ccc3bb830142fe6746f08a99cb6b8db02dbfd +size 54409 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50cee13b7d4bd1a8e0d87d96a14170f51d80b947 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/a1890b9a9b85f13e67ed59bbad623659_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37adf955ab71bcd641c13ef17b9d75f7a7da6fa40220fa79cc02b25daafd78f9 +size 47124 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebc53cb4eab728ddd3e346b37143dc234e0d475d --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c3546820ee6f92136bea2b598a3ed1e97d06abc7982f344533f9baf42be9ac8 +size 83937 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62830615872a7afcc9f5ee84a9d08b68f9255df7 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28e3a939556aaa9c4e73ff460f2dd0519f0c253fe1402b838cb27dc500e33d0c +size 67769 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0074b58e46ca8345920217cebe62bc25723ee4f5 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/a74294f34a0c736b7ee0f5f0cdca7e28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c654e0a0374d575fa3df23d88bc7d013e432fad9fd144a690cda19bfe991bf5 +size 81120 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5f15e3a2df6ea2878380d038b2d3996b643fd95 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/aa1b948a76d8a599c76b5033f5db9e2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dee02a4ab85ff22809abedd52be9661daf0f64c2cec0f83709123cc4898674d6 +size 53934 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1048e66eb14a96d10377b8b4e037c18f5b975324 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e58371e6db65e32707be466b9dd7cc64ca9cf7f77f0da53c8a850e51c4f4338 +size 53851 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0413ae437eb57901e6d827ca32c6313579359775 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/ae0a735d106290c594b0bafb1f5e72e7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eabcbdcff73e91ab165e044b638afeaa1ff2d1855a484e6081ac699bfbadd81e +size 166403 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..003fd5385440997580e5f04b0c2030207544e41a --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/b05bae46f7079e5c9b1da38adb2319e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73d247d232cd945fff15ad9dd0ef013ecb976e7047677d3b4ef093fbe2c3cbc4 +size 66828 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64dee1f83984740b71ccb80d01df6dd3b591607b --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7dfa2e5efceddbdc735386d744b35d2d984b17e91c28fb72159525d8821647d +size 39063 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07d9fd91e0c602a077896d1304c083c9ef0f53ab --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbd14e6b72ebd93e78a3b5455cb786eea48617615eb8963ff49fb6ce2ac15f54 +size 102159 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32dc6640c5b5387115b8abc3f9f66135e1cfd1a3 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/b9c0d46c1148cf65cb79f27fac420981_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:316f526210ef368843897b2e97053bcbf8cb444e3fd52c0c32446c01b1104346 +size 82481 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a91638e1bc2758d18b6ebc69b1671d19731541c0 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/bb4d2112ed07e2031c92fbff3494af9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29de5abd7df241f4631ffd47296b81c9f9487ab30de73550d5ed72bbdb7ff6c4 +size 88569 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc4f18770af86a8b6194fe8fdbe5fd7336c7ea67 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbcd4a11d93ec06a404d3553e1eb257fc48d56d6358bd5792c621325e2eac9f5 +size 70173 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..846158c30c1e193d447fb5db04992791028b399f --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0abd4c7431bd6d516667d8d40fac9474835cc894d9d0408de681c559a46957c +size 105255 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f9fcc1aa44fb2943484a95f20a46e3bba238cef --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6faf6c47b6827fd84be88350ae8dfb0abd7bec0924a41efce29caded2096e14 +size 83800 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d12db4361f5f986b2d4534f9199fcdd860ccb8 --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e900a6fbe8b22d3a6d7740cb92db1e92903141b48e758e44bfcdcac7f5fd80c +size 207624 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7b5faf3fc2bcc7d831432413784f085198662ba --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/fc02903382cebe6fc11e4c0d74b5313f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b047e388be0612bf9383ac53e8f2847091e310687a04df4e77222f8f276c6e38 +size 98866 diff --git a/marked/G/T-REC-G.875-202412-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/marked/G/T-REC-G.875-202412-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ba1d60a4c3a3293343c2aacb5c4c7fe7fe7320e --- /dev/null +++ b/marked/G/T-REC-G.875-202412-I_PDF-E/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd17b02d1e93f2b29833ae054bc075813898eaede1a8fcba62594b621947a17a +size 101254 diff --git a/marked/G/T-REC-G.941-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.941-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46e9e20269288838975cb8ea9ef2093353928cfa --- /dev/null +++ b/marked/G/T-REC-G.941-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd02699aa3de6c2fb4800221698b705c7af6798fc5e7430a12856fe24449be74 +size 7283 diff --git a/marked/G/T-REC-G.953-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.953-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f462aa76a1bd4abc43e71c76fb2d758330d8e893 --- /dev/null +++ b/marked/G/T-REC-G.953-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b69fbf51a775dd9a6d6f1a54889692b863303e635a263d2ff12b4e9196beb36b +size 7452 diff --git a/marked/G/T-REC-G.953-198811-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/G/T-REC-G.953-198811-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ad001320014e3a0dae786c58dba900821e4f7b --- /dev/null +++ b/marked/G/T-REC-G.953-198811-I_PDF-E/c9d8a18a6137ad054b841d7a614afb48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17326fc7f3e8c2afa622b4c9aa6b3aabbabe5c0bf84b1e22ea5440ef97e8333 +size 30778 diff --git a/marked/G/T-REC-G.953-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/G/T-REC-G.953-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cd41b620fe63754a1e157b1189c872584c2aa2e --- /dev/null +++ b/marked/G/T-REC-G.953-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69a39248371033f437ea90692bfa129ccecd6ef5b1a2ace7f00d1e52b3b9c73f +size 31017 diff --git a/marked/G/T-REC-G.953-198811-I_PDF-E/raw.md b/marked/G/T-REC-G.953-198811-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3f645b046f886c2056d35f642dbdecbe5f306810 --- /dev/null +++ b/marked/G/T-REC-G.953-198811-I_PDF-E/raw.md @@ -0,0 +1,274 @@ + + +![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. A lightning bolt symbol is positioned to the right of the globe. + +ITU logo + +INTERNATIONAL TELECOMMUNICATION UNION + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.953** + +**DIGITAL SECTIONS AND DIGITAL LINE SYSTEMS** + +--- + +**DIGITAL LINE SYSTEMS BASED +ON THE 1544 kbit/s HIERARCHY +ON COAXIAL PAIR CABLES** + +**ITU-T Recommendation G.953** + +(Extract from the *Blue Book*) + +--- + +# NOTES + +1 ITU-T Recommendation G.953 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 1544 kbit/s HIERARCHY ON COAXIAL PAIR CABLES** + +*(Malaga-Torremolinos, 1983; amended at Melbourne, 1988)* + +## **1 General** + +This Recommendation covers digital line systems for the transmission of signals based on the 1544 kbit/s hierarchy on coaxial pair cables and includes systems conveying the following bit rates: + +44 736 kbit/s + +97 728 kbit/s + +## **2 Transmission media** + +The systems can be operated on coaxial pairs, as defined in the Series G.620 Recommendations, in accordance with Table 1/G.953. + +TABLE 1/G.953 + +### **Transmission media** + +| System (kbit/s) | Cable Recommendation | +|-----------------|----------------------| +| 44 736 | G.623 | +| 97 728 | G.623 | + +## **3 Overall design features** + +### 3.1 *Availability* + +The availability objective of the system should be derived taking into account the availability requirement for the hypothetical reference digital section given in Recommendation G.801. + +### 3.2 *Reliability* + +MTBF values should be specified for the line system as a whole taking into account the requirements concerning availability. + +### 3.3 *Repeater noise margin* + +Repeater Noise Margin is defined in Annex A together with suggested measurement techniques. The Noise Margin quantifies the performance of digital regenerators for coaxial pairs. This is a function of BER and repeater spacing loss $A_0$ (at half the line system baud rate). + +At a BER = $10^{-7}$ and over the loss range of the system $A_1 \leq A_0 \leq A_2$ , the Noise Margin should meet the following specification: + +$$\text{Noise Margin (M)} \geq B + C (A_2 - A_0)$$ + +It has been possible to recommend specific values for parameters $A_1$ , $A_2$ , $B$ and $C$ . + +*Note* - The degrading effect of timing jitter on Noise Margin should be measured by superimposing appropriate jitter on the test signal. + +### 3.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. + +## 4 Specific design features + +### 4.1 Type of power feeding + +Although CCITT does not recommend the use of a specific remote power-feeding system for these coaxial line systems, in practice only the constant current d.c. feeding via the inner conductors of the two coaxial pairs of system is used. + +These coaxial cable systems 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]. + +### 4.2 Nominal repeater spacing + +A specific repeater spacing is not recommended but in practice the nominal values indicated in Table 2/G.953 are used by most Administrations: + +TABLE 2/G.953 +Nominal repeater spacings + +| | Nominal repeater spacing (km) | +|-----------------|------------------------------------------| +| System (kbit/s) | Cable Recommendation a) G.623 | +| 44 736 | — | +| 97 728 | 4.5 | + +a) Recommendation G.623 refers to 2.6/9.5 mm coaxial pairs. + +### 4.3 Maintenance strategy + +#### 4.3.1 Type of supervision and fault location + +In-service monitoring or out-of-service fault location can be used. + +#### 4.3.2 Fault conditions and consequent actions + +The fault conditions and consequent actions should be complementary to those recommended for digital line sections. + +## ANNEX A + +(to Recommendation G.953) + +## Definition and measurement of repeater noise margin + +### A.1 Definition + +The noise margin $m_n$ : + +$$m_n = SNR / SNR_{ER} \quad (A-1)$$ + +where: + +$$SNR = SNR_{th} \cdot F(t, ER) \quad (A-2)$$ + +The product $SNR_{th} \cdot F(t, ER)$ can be considered the actual signal-to-noise ratio $SNR$ , being the measure for the regenerator performance. + +$SNR_{th}$ is the theoretical signal-to-noise ratio determined by the system parameters such as output pulse, section loss, noise figure of the regenerator input amplifier, etc. + +$F(t, ER)$ is the reduction factor due to an off-set from the optimum timing instant (including phase jitter) in conjunction with the pulse realized $S(t)$ , the intersymbol interference $I(t)$ and any other disturbance which causes a corruption in the information signal ( $I_c$ ). + +*Note* - The intersymbol interference and other disturbances are fluctuating processes with bounded distributions. The "mean" reduction factor depends on $ER$ , and, for a ternary signal, is given by: + +$$F(t, ER) = \frac{S(t)}{S(0)} - 2 \left\{ \frac{I(t)}{S(0)} - \frac{I_c}{S(0)} \right\} \quad (A-3)$$ + +where $S(0)$ is the realized pulse at $t = 0$ giving the maximum amplitude. + +$SNR_{ER}$ is the signal-to-noise ratio required for an error ratio equal to $ER$ . For a ternary signal the relation between $ER$ and $SNR_{ER}$ is given by the known Gaussian distribution: + +$$ER = \frac{4}{3} P[E] = \frac{4}{3\sqrt{2\pi}} \int_{SNR_{ER}}^{\infty} e^{-x^2/2} dx \quad (A-4)$$ + +### A.2 Derived definitions + +The noise margin can be measured by applying an external disturbing signal. For that purpose more practical definitions are derived. + +A.2.1 $SNR_{ER}$ (giving an error ratio ER) can be achieved by injecting sufficient white noise into the input of the regenerator: + +$$SNR_{ER} = \left\{ \frac{N_T}{N_T + N_E} \right\} \cdot SNR \quad (A-5)$$ + +where + +$N_T$ = thermal noise that appears at the decision point during normal operation. + +$N_E$ = mean power of the external noise that appears at the decision point to induce an error rate $ER$ . + +Combining (A-1) and (A-5) results in the noise margin $M$ : + +$$M = 20 \log m_n = 10 \log \left( 1 + \frac{N_E}{N_T} \right) \quad (A-6)$$ + +$$N_E = N_0 \int_0^\infty |E(f)|^2 df \quad (A-7)$$ + +$$N_T = kT \int_0^\infty |E(f)|^2 F(f) df \quad (A-8)$$ + +$N_0$ = power density of the external noise that is superimposed on the signal + +$E(f)$ = transfer function of the regenerator's equalizer + +$k, T$ = Boltzmann constant and absolute temperature + +$F(f)$ = noise figure of the equalizer amplifier of the regenerator + +A.2.2 By injecting a sine wave disturbing signal, a second definition for $m_n$ can be derived. + +This disturbance causes a decreasing $F(t, ER)$ , which can be defined by: + +$$F_d(t, ER) = SNR_{ER} / SNR_{th}$$ + +Next [in accordance with (A-1) and (A-2)], + +$$F(t, ER) = m_n \cdot SNR_{ER} / SNR_{th}$$ + +Substraction gives: + +$$F(t, ER) - F_d(t, ER) = 2 \frac{I_s}{S(0)} - (m_n - 1) SNR_{ER} / SNR_{th}$$ + +where $I_s / S(0)$ is the normalized disturbing signal at the decision point. + +Substitution of $SNR_{th} = S(0)/2\sqrt{N_T R_0}$ and some rearrangements results in the noise margin: + +$$M = 20 \log 1 \cdot \left( \frac{I_s}{SNR_{ER} \cdot \sqrt{N_T R_0}} \right) \quad (A-9)$$ + +$$I_s = S_d \cdot |E(f_d)| \cdot a_c \quad (A-10)$$ + +$S_d$ = the magnitude of the disturbing signal at the input of the regenerator + +$f_d$ = the frequency of the disturbing signal + +$a_c$ = a correction factor taking into account the effect of the disturbance on the peak detector of the automatic equalizer + +$R_0$ = the real part of the characteristic impedance of the cable. + +### A.3 Measurements + +Method A is based on the definition directly related to the noise margin (A-6) and therefore, is the reference test method. Methods B and C are alternative test methods. + +#### Method A (Figure A-1/G.953) + +The values of $N_E$ and $N_T$ are measured directly at the decision point. The value of $N_T$ is measured in the absence of both a signal and externally applied noise. Under these conditions the automatic gain control (AGC) of the equalizer must be externally controlled to a level appropriate to the corresponding cable attenuation. With the signal restored, the level of the externally applied noise is adjusted to give the desired BER. The noise level ( $N_T + N_E$ ) is now measured with the signal removed and with the AGC set at the same value as in the measurement of $N_T$ . + +![Block diagram of the measurement setup for Method A. A signal generator (square wave) is connected to a regenerator, which is connected to a cable. The output of the cable is connected to a summing junction (+). A noise generator is connected to this summing junction. The output of the summing junction is connected to a regenerator under test. The regenerator under test has an AGC input connected to a noise power meter. The output of the regenerator under test is connected to a decision point, which is also connected to an error detector. The diagram is labeled CCITT-64.200.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +Block diagram of the measurement setup for Method A. A signal generator (square wave) is connected to a regenerator, which is connected to a cable. The output of the cable is connected to a summing junction (+). A noise generator is connected to this summing junction. The output of the summing junction is connected to a regenerator under test. The regenerator under test has an AGC input connected to a noise power meter. The output of the regenerator under test is connected to a decision point, which is also connected to an error detector. The diagram is labeled CCITT-64.200. + +FIGURE A-1/G.953 +Measurement of noise margin (Method A) + +#### Method B (Figure A-2/G.953) + +This method realizes a measurement without the need to access the decision point. The applied noise at the input, to cause a given BER, is measured directly. The corresponding value at the decision point and also the thermal noise ( $N_T$ ) are evaluated by means of the transfer function and the noise figure of the amplifier equalizer. + +*Note* - Both the transfer and the noise figure of the amplifier equalizer need to be calculated and measured on a sample of repeaters before this method can be applied to a particular repeater design. + +#### Method C (Figure A-2/G.953) + +This method is similar to the previous method (B) except that in this case the applied disturbance is a sine wave signal. This applied signal at the input, to cause a given error ratio, is likewise measured directly. + +The corresponding disturbance at the decision point ( $I_s$ ) as well as the thermal noise voltage ( $\sqrt{N_T R_0}$ ) are evaluated by means of the transfer function, the noise figure of the equalizer and the correction factor $a_c$ , which have to be determined. + +*Note* - It follows from (A-8) and (A-9): + +$$M = 20 \log (1 + S_d \cdot X / SNR_{ER})$$ + +$$\text{where } X = |E(f_d)| \cdot a_c / \sqrt{N_T R_0}$$ + +being an unknown factor, which has to be determined on the basis of measurements on a sample of prototype regenerators before this method can be applied to a particular regenerator design. + +For this purpose, the noise margin of the prototype regenerator needs to be measured in accordance with the reference test method (A). + +*Note 2* - This method allows the presence of an LBO-network at the regenerator input. In contrast to method B it is not necessary to insert a complementary filter in the injection path. + +*Note 3* - To obtain the most accurate measurement the disturbing frequency should be around the Nyquist frequency. + +![Block diagram of the measurement setup for noise margin. A signal generator (square wave symbol) connects to a Regenerator (triangle symbol), which connects to a Cable (rectangle with a curve symbol). The Cable output connects to a summing junction (circle with a plus sign). A Noise generator (B) or Sine wave generator (C) (rectangle symbol) connects to the summing junction via a Filter (rectangle with a sine wave symbol). The summing junction output connects to a Regenerator under test (triangle symbol), which then connects to an Error detector (rectangle symbol). A Power meter (circle with a needle symbol) is connected to the summing junction.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +Block diagram of the measurement setup for noise margin. A signal generator (square wave symbol) connects to a Regenerator (triangle symbol), which connects to a Cable (rectangle with a curve symbol). The Cable output connects to a summing junction (circle with a plus sign). A Noise generator (B) or Sine wave generator (C) (rectangle symbol) connects to the summing junction via a Filter (rectangle with a sine wave symbol). The summing junction output connects to a Regenerator under test (triangle symbol), which then connects to an Error detector (rectangle symbol). A Power meter (circle with a needle symbol) is connected to the summing junction. + +a) Can be deleted in Method C. + +FIGURE A-2/G.953 +Measurement of noise margin (Methods B and C) + +## 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. \ No newline at end of file diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4896c07fffeab7aef8c7e17bbb7f7f8010669d31 --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af41350e30a32c317d2475bc3ec2908c04374a9fe10822078b5e4995162a0e1b +size 23887 diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46e9e20269288838975cb8ea9ef2093353928cfa --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd02699aa3de6c2fb4800221698b705c7af6798fc5e7430a12856fe24449be74 +size 7283 diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24ef25715ca02083b12fb03ffabd73161679c3d2 --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/4e4be0bd8b235167902f2c03e41da651_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4987d53eb22f5a9ee5a453871be6c9e20bca4034c7ef6a29c801952353e166f +size 23822 diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdcccab96eca372490199bd9d2aba9d430e2eaf0 --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6366e49825d9cf989d947e96f479f458a7edc9e4bc3c9a5f8525b45245f623c5 +size 92238 diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5eeaab060981bc8c7f9327f3e6291feee3b5a887 --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78d3cc72d273ab54d823a896c23c65239c84d0720b3490b0fc4d0af851b96a4d +size 29858 diff --git a/marked/G/T-REC-G.954-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/G/T-REC-G.954-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4ae826c5574d774afa3fffc755924247b35d1ba --- /dev/null +++ b/marked/G/T-REC-G.954-198811-I_PDF-E/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bcc6aa2e3368fd967be32f4bb2b35fac8ead0d3052459645073d7faa7104448 +size 41504 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/1033ab90cd19fd4c5901966aeec07a86_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/1033ab90cd19fd4c5901966aeec07a86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55c32de2048c6073a9b92b15131cdb0874237eac --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/1033ab90cd19fd4c5901966aeec07a86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:344ccae10422fe8eaaf359863af6cd00f4a3cdf9ebe6defd2c461b68a5fdf401 +size 20162 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21a09d3b4abb2bc8764d368c8ca3e33353a886ff --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71932e7de3cca7bb0f51a5bcaa8f1b1f00fc5a33419c88ed255152d0c6e00c51 +size 4898 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/152efae989544ee653283e8de26cc9b1_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/152efae989544ee653283e8de26cc9b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cbbc39eac037f4733f846eeb3f5189346d65395 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/152efae989544ee653283e8de26cc9b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98ddd99f644194a8862fa25feeb70572b290bbd327154b385f204c62579520e1 +size 33162 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4b37d4ff5ed0ac2900135f80278cff8b07797ac --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/1d529a819ad929684331c55eed6673bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ec7100634ba6003cb90e5a75114174b48039d848e8cf08f3954f3bfc2f0da1c +size 41769 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af17a7fc29564b4600848c4fadc7469da78947ed --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcf44d5d9cd998c0c0af60ebdcf748a2c2b3b0cdf1806f79dfcf44a586765346 +size 28389 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..796fbe5aef1b02174a32898f9654888b00b67e5f --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59115e83fdadd094d10932f46a9aff148d700788bd1317e10c33b70c9fd32943 +size 37606 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db4ad9d69874dc6be12eb8a91502292c65bd4dbe --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:257b433b205cf1d6d06d0acd88de12e9929ecefe1eeb06671541cdc9013735e2 +size 25464 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c6647ac60529a96034f6a648c1b0f70c22ed1de --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:009cf526d660a31fe8d2b51551882f0cd1065518b98a008c82c6a426fc665553 +size 25963 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02d54e62f68236061d647e22e760724331206469 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a171dcadf5426fb3ec93e49cf06e5949beb7a45a3321b1ff16bca95ff4caf185 +size 35192 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01509104d9252004a1f0ee0543a559f6f6219e19 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dae43d04328894d4df680889659f1a72e1ead869b57081e26fff19ad9f333547 +size 51240 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/6fe536731996880570f251da168376cf_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/6fe536731996880570f251da168376cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd8578cdc2568076af360827b92799bd55c74d43 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/6fe536731996880570f251da168376cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e240c3c04251dcd4a8b011f5b4147293d8d9faf84383b40a7d70d8a771382f +size 25877 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d270a3c34954005d3ae08559af7dc7f678e5bf46 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3f9bd0e68c2229c19d024f676415625c4a46538b806471055a9c47ee9c775e4 +size 14338 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec8446a94738fe793a6aa3433910ea44c6eda85 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/8fd97886a32c3ac7abb08aba9f7f231b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac65c90fc58d76f0a844d5fa351fa482d12f48ae9cf5afa644cb71644383c3b +size 47462 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fbdaea5739956ed1efeafd514f18f492ae4017e --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a4825f12d3499b9d5f7b91181dd217a4347e4897d0acae424ce80ee893c8e8d +size 18906 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/a1a474be12b8992842992294b1d18592_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/a1a474be12b8992842992294b1d18592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4308fdc17706da144f01de2d4305a582dd14e567 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/a1a474be12b8992842992294b1d18592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16ec0f6de5a592ba1d69d2d2ccc2947e99cb432d9c27644b9ecb26cd9567bdf1 +size 86456 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6e177a2b89849a858e887c57d7441aadcb94084 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/a7585024ebe2bba8ac0757150a12759a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d01446fec0e1b13d566eff5e3e21409ad96f77e3f931d9425903580493c686cc +size 40457 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48db636448f7e218eb8b654933bf01b4b8e5b944 --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/b9d879f357d5f15fac9ea8585b87d0a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcc0464759946b4e7c5f5ef4b839a72d2e916217f9b8e37f9dea27a7a7ef348a +size 70538 diff --git a/marked/G/T-REC-G.957-200603-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg b/marked/G/T-REC-G.957-200603-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11100b5786c3525c9920a2293aa8e6aabde7f00e --- /dev/null +++ b/marked/G/T-REC-G.957-200603-I_PDF-E/d68ecc44f3cfaed866a846f9fa4bdf38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5000672151bb7901916ce45ebb6f991b12a122ec1d3334687a8bc6c049a54d64 +size 34179 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f95eeaa070340233d64fb0a2fb44c8430a60c1d4 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/14294c70b5a0effb6bdaf09c46bbdc9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c02493e8cf17a6c458eea55150652cb21b8af58704c8f427dc28c68161eef91 +size 50424 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..503d5228124418b8f736ffa8affa09ebc43d0454 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51458c2fc6eb301b98ad1ad902a1c6a4aea3fe51e4325c796d8adef12f3147e4 +size 50609 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7662643f86d8112e0b5867ce8a3040f4305b5de3 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3be41157aeca415c5a21fa143540bad3b9b252496dd3def6d40d18246a97fd55 +size 67825 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5c339792e051e6911b7f9cf20076392f79ad774 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/48a08e5cabec8b75386679d8a57dec3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84476a879520a3d151322a5b23c001997adeb6efbac1253bb02592bdede8bdcf +size 41788 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0349b74a2aa939e89931ce51849e5264ca6ea48 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/51536f203c07ce20ce119e7e09b11cb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a0daad646f79a7e52d7c3c22053fb525e389c1de37115f316ed9f26a69a4d3e +size 33753 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46d0295000ac2ac4abe771badea5ea54b64733b7 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5bbef9228522aa7beb608a373f7a452600dbdf2e427537dd0dcb430f13ef41e +size 67213 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/8f00510b4163fff77451c01ef42f696f_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/8f00510b4163fff77451c01ef42f696f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5327a81dee54009d0cee822f3c5c53184f113a3f --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/8f00510b4163fff77451c01ef42f696f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2112d38a65d1509b1beded772f062da0e584e22a65b4481de936713e01e3550b +size 48647 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bba41669a403b093147ef3c86e397b40d5af646c --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c873a52d9d5c3eaf73b36f080a013644f6b0952cd941990fc6b49fba80e8e12 +size 59242 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e0d438d0552ce799fcacf863216a264d73ea699 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/a2dcc4a0703102026ec86e82caa4985e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2a25533c3c16015d6c2a6ab4c206bbadfc7fe8fc3a76f0ceab7ec45d57f6c18 +size 33995 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40b52af8229b23906d0094457318baf3efb61182 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24ad8fc494c312152bb6ba20fa82cfe5e58ec0c512825c9ae83a939d2d40cdb2 +size 119557 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6955c8bff9aa86663ed24acb9a98ae4aceaebfb --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b082c36d92c6a102785dddbd9e1897c2682652366c4966a51d4fc3e1113f93d9 +size 61068 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7010363c3327e6311638d1674fd224a2ad127f85 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d7dd72352c405b2ad4e8df086620cc98939472542b01325308ed44cd847a28e +size 19730 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..584bc8d23b89c799ee3223eedc590310bf4649f6 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56aa5ffb1df9b526604f2cdaf1c9c219929bd4f92cd137c856a559356d1f6947 +size 19596 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/bafe3665fa89ba09857af5a2532c79fe_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/bafe3665fa89ba09857af5a2532c79fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fb09c8ad4e2c0f9decc90ce3aeb2297d139b251 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/bafe3665fa89ba09857af5a2532c79fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c97c5a7692cdb36a14c6ca762b1b45ed65bb586d0195ba69bf5d5cc247c86dc2 +size 38777 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ceb45ca71c7ce483c8d51d4a6f2165589cf1181 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce7fc3bac5dbe050290306b837fdb5e0c21cc9f82cdb64d227e3249a698aceba +size 30453 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8537c84539d889a72f4a22b753b602d59887fa3c --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/dfe556fea00682b09a59427aaf72051c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d0548b9aa3c771137b9fa3ebccbc91df1006ae7ff8fb3aa072fe702bf17f867 +size 64673 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..469dcd4485b685ca0947f46ca4e843d0ada2ac89 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/f732d3320afe06d979aabbd366184254_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91c04e15759bb0a4df558cb8634e10b0db3e8de7ea2e64115f04fffe4ed16b38 +size 28402 diff --git a/marked/G/T-REC-G.959.1-202401-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/G/T-REC-G.959.1-202401-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22730e5d6bf06ff5305e94563012da024857c953 --- /dev/null +++ b/marked/G/T-REC-G.959.1-202401-I_PDF-E/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07fac7b31dd2309cab2a6f100f81d2d108cca040a3d6985d6b13f9f9fe4a8601 +size 60564 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f37125ec01cd7a2f95ed1a2b3f69a29cb68d25ad --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93686ef4e72bfc0d54058187d04e7e21a6cbfccc34d8175cb50c2c8bb1ab8733 +size 8250 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d2074706315ac75486540f068eccb189f6ae13 --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/2ee59e629035d641140e55f4d215b0d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76d967e8ea94be0559dde4fba1a72522674c18871542896830af26640ad1972c +size 89666 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5b42ef2a0cb854e1147a08f15175d5261038a24 --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/547f726730e589392f239257a833ede3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:718fb5dbf7f3bd04eb10c25a1415e52a969dcae4fb801328dd88025836c701bb +size 25675 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db8fb851df71b5a020933a5a0404e560e878d09e --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/562f471e8153729557e6a4ee6343c32c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d83e8089b559a8ac69aa8d97540be62849235096b12387a811927e52e18789b4 +size 51621 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ebec478e77bb92b491d0d922e62c2528d9c8b69 --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:790b934757dac6db228eb730b00a3c251e89eaecb141dc3873b1b6e1b76ea729 +size 62189 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fb342206675d2c04a8bb8b97c2bae9f0962c540 --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/fc46871d72c65d3381d9201646d23439_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fd410fb89e8d967c916c07f361c8d29f9cf987a1ea9848d81d1c31c55fb38fc +size 67952 diff --git a/marked/G/T-REC-G.960-199303-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/G/T-REC-G.960-199303-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e364402c8421d491f7ac1412b3c36d7d56e6382b --- /dev/null +++ b/marked/G/T-REC-G.960-199303-I_PDF-E/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fe750958eea5421579ce5c35a56e286175390554f4c386c6353c8ffcffdc756 +size 66719 diff --git a/marked/G/T-REC-G.971-202412-I_PDF-E/raw.md b/marked/G/T-REC-G.971-202412-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..95282920b9f4b6ef79523f0290c407aa1c8d4da6 --- /dev/null +++ b/marked/G/T-REC-G.971-202412-I_PDF-E/raw.md @@ -0,0 +1,827 @@ + + +# Recommendation**ITU-T G.971 (12/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital sections and digital line system – Optical fibre submarine cable systems + +--- + +# **General features of optical fibre 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 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 | +| 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.971 + +# General features of optical fibre submarine cable systems + +## Summary + +Recommendation ITU-T G.971 applies to optical fibre submarine cable systems. The purpose of this Recommendation is to identify the main features of optical fibre submarine cable systems and provide generic information on relevant Recommendations in the field of optical fibre submarine cable systems. A common implementation relevant to all the optical fibre submarine cable systems is described in Annex A. Specific information relevant to each optical fibre submarine cable system is included in annexes of other Recommendations. The updated data on cable ships and submersible equipment of various countries are also described in Appendix I. + +In this latest version, the diagram of optical fibre submarine cable systems with scientific sensing function is described in Figure 1(c). + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.971 | 1993-03-12 | 15 | 11.1002/1000/1036 | +| 2.0 | ITU-T G.971 | 1996-11-11 | 15 | 11.1002/1000/3830 | +| 3.0 | ITU-T G.971 | 2000-04-04 | 15 | 11.1002/1000/5059 | +| 4.0 | ITU-T G.971 | 2004-06-13 | 15 | 11.1002/1000/7339 | +| 5.0 | ITU-T G.971 | 2007-07-29 | 15 | 11.1002/1000/9157 | +| 6.0 | ITU-T G.971 | 2010-07-29 | 15 | 11.1002/1000/10882 | +| 7.0 | ITU-T G.971 | 2016-11-13 | 15 | 11.1002/1000/13088 | +| 8.0 | ITU-T G.971 | 2020-10-29 | 15 | 11.1002/1000/14501 | +| 9.0 | ITU-T G.971 | 2024-12-07 | 15 | 11.1002/1000/16063 | + +## Keywords + +Cable ship, optical fibre submarine cable systems, submersible equipment. + +--- + +\* 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 | +| 4 Abbreviations and acronyms ..... | 2 | +| 5 Conventions ..... | 2 | +| 6 Features of optical fibre submarine cable systems ..... | 3 | +| 7 Relationship among Recommendations relevant to optical fibre submarine cable systems..... | 5 | +| Annex A – Common implementation aspects of optical submarine cable systems for manufacturing, installing and maintenance ..... | 7 | +| A.1 Introduction ..... | 7 | +| A.2 Manufacturing ..... | 7 | +| A.3 System installation..... | 8 | +| A.4 System commissioning..... | 9 | +| A.5 Maintenance ..... | 9 | +| Appendix I – Data on cable ships and submersible equipment of various countries..... | 11 | +| I.1 Cable ships..... | 11 | +| I.2 Submersible equipment ..... | 18 | +| Bibliography..... | 25 | + + + +# Recommendation ITU-T G.971 + +# General features of optical fibre submarine cable systems + +# 1 Scope + +This Recommendation applies to optical fibre submarine cable systems. + +The purpose of this Recommendation is to identify the main features of optical fibre submarine cable systems and provide generic information on relevant Recommendations in the field of optical fibre submarine cable systems. Annex A contains common implementation aspects of all optical submarine cable systems. Appendix I contains data on cable ships and submersible equipment of various countries. + +# 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.821](#)] Recommendation ITU-T G.821 (2002), *Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an Integrated Services Digital Network.* +- [[ITU-T G.826](#)] Recommendation ITU-T G.826 (2002), *End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections.* +- [[ITU-T G.828](#)] Recommendation ITU-T G.828 (2000), *Error performance parameters and objectives for international, constant bit-rate synchronous digital paths.* +- [[ITU-T G.8201](#)] Recommendation ITU-T G.8201 (2011), *Error performance parameters and objectives for multi-operator international paths within optical transport networks.* +- [[ITU-T G.972](#)] Recommendation ITU-T G.972 (2024), *Definition of terms relevant to optical fibre submarine cable systems.* +- [[ITU-T G.973](#)] Recommendation ITU-T G.973 (2016), *Characteristics of repeaterless optical fibre submarine cable systems.* +- [[ITU-T G.973.1](#)] Recommendation ITU-T G.973.1 (2009), *Longitudinally compatible DWDM applications for repeaterless optical fibre submarine cable systems.* +- [[ITU-T G.973.2](#)] Recommendation ITU-T G.973.2 (2011), *Multichannel DWDM applications with single channel optical interfaces for repeaterless optical fibre submarine cable systems.* +- [[ITU-T G.974](#)] Recommendation ITU-T G.974 (2007), *Characteristics of regenerative 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.9730.1] Recommendation ITU-T G.9730.1 (2024), *Dedicated scientific sensing submarine cable system.* +- [ITU-T G.9730.2] Recommendation ITU-T G.9730.2 (2024), *Scientific monitoring and reliable telecommunication submarine cable systems.* + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the terms defined in [ITU-T G.972]. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|-----------------------------------------------| +| BAS | Burial Assessment Survey | +| BOL | Beginning of Life | +| BU | Branching Unit | +| CPT | Cone Penetrometer Testing | +| CTE | Cable Terminating Equipment | +| DP-system | Dynamic Positioning-system | +| DWDM | Dense Wavelength Division Multiplexing | +| ECR | Electrical Command Response | +| ME | Monitoring Equipment | +| MC | Maintenance Controller | +| OCJ | Optical Coupling Junction | +| PFE | Power Feeding Equipment | +| PLGR | Pre-Lay Grapnel Run | +| ROV | Remotely Operated Vehicle | +| SCARAB | Submersible Craft Assisting Repair and Burial | +| SWL | Safe Working Load | +| TSE | Terminal Station Equipment | +| TTE | Terminal Transmission Equipment | + +# 5 Conventions + +None. + +# 6 Features of optical fibre submarine cable systems + +An optical fibre submarine cable system has specific technical features: + +- a) A submarine cable system should have a long lifetime and be highly reliable. The main reason for this is that the construction and maintenance of a link is long and expensive due to the difficulty in accessing submerged plants. Moreover, most submarine links are of strategic importance in the transmission network – the interruption of a link usually results in significant loss of traffic and revenue. +- b) A submarine cable system should possess mechanical characteristics which enable it: + - 1) to be installed accurately with correct slack and with due attention to safety considerations on the seabed – deep-water installations can reach depths up to 8000 metres. (In general, submarine cable systems shall be installed, buried or inspected by specially designed cable ships and submerged equipment. Detailed information of such cable ships and submerged equipment (i.e., ploughs, remotely operated vehicles (ROVs), etc.) is contained in Appendix I); + - 2) to resist environmental conditions on the sea bottom at the installation depth, particularly hydrostatic pressure, temperatures, abrasion, corrosion and marine life; + - 3) to be adequately protected (i.e., by armouring or burying) against aggression, due for example to trawlers or anchors; + - 4) to survive recovery from such a depth, and subsequent repair and relay, with due safety considerations. +- c) The material characteristics of a submarine cable system should enable the optical fibre: + - 1) to achieve its desired reliability over its design lifetime; + - 2) to tolerate stated loss and aging mechanisms, especially bending, strain, hydrogen, stress, corrosion and radiation. +- d) The transmission quality of a submarine cable system should follow, as a minimum [ITU-T G.821] or [ITU-T G.826] or [ITU-T G.828] or [ITU-T G.8201]. + +Figure 1(a) shows the basic concept of optical fibre submarine cable systems and boundaries. Optical submarine repeaters or optical submarine branching units could be included, depending on each system requirement. Figure 1(b) shows the diagram of interoperable optical fibre submarine cable systems and boundaries. Figure 1(c) shows the architecture of optical fibre submarine cable systems with scientific sensing capabilities. Sensor subsystem, scientific subsystem, sensors and/or sensor sets are located in the submarine portion. It should be noted that branching unit (BU) only for sensors or sensor sets is related to [ITU-T G.9730.1]. + +In Figure 1, "A" denotes the system interfaces at the terminal station (where the system can be interfaced to terrestrial digital links or to other submarine cable systems), "B" denotes beach joints or landing points, and "C" denotes interoperable cable portion interface. Numbers in brackets in the figure refer to [ITU-T G.972]. + +![Diagram (a) showing a submarine cable system configuration with land and submarine portions, repeaters, and various interfaces.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg) + +Diagram (a) illustrates a submarine cable system configuration. The system is divided into three main segments: Land portion (1004), Submarine portion (1005), and Land portion (1004). The components and interfaces are as follows: + +- Land portion (1004):** Contains TTE (1010), CTE (1014), MC (1012), and PFE (1013). The system interfaces (A) are located at the ends of the land portions. +- Submarine portion (1005):** Contains an Optical submarine repeater (1020), three Repeater units, and a BU (1022). The submarine cable (1019) connects the land portions. +- Interfaces:** + - System interface (A):** Located at the ends of the land portions. + - Landing points or beach joints (B):** Located at the boundaries between land and submarine portions. + - Optical interface (2009):** Represented by a circle. + - System interface (2008):** Represented by a solid black circle. +- Other labels:** + - Supervisory section (2007) + - Elementary cable section (1028) + - Cable jointing box (5013) - indicated by an 'X' on the cable. + +**Legend:** + +- Optical fibre submarine cable (1019) +- Optical fibre land cable (1018) +- Optical fibre station cable (1017) +- Electrical cable +- Optical interface (2009) +- System interface (2008) + +**NOTES:** + +- NOTE 1 – A denotes system interface +- NOTE 2 – B denotes landing points or beach joints (1006) +- NOTE 3 – X denotes cable jointing box (5013) +- NOTE 4 – Numbers in brackets relate to [ITU-T G.972] + +G.971(20)\_F01a + +Diagram (a) showing a submarine cable system configuration with land and submarine portions, repeaters, and various interfaces. + +(a) + +![Diagram (b) showing a more complex submarine cable system configuration including terminal portions, interoperable cable portions, and various repeaters and interfaces.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) + +Diagram (b) illustrates a more complex submarine cable system configuration. The system is divided into three main segments: Terminal portion (1063), Interoperable cable portion (1064), and Terminal portion. The components and interfaces are as follows: + +- Terminal portion (1063):** Contains TTE (1010), OCJ (1062), Land repeater (1065), Land repeater, CTE (1014), MC (1012), MC (7015), ME (1061), and ECR (1061). The system interfaces (A) are located at the ends of the terminal portions. +- Interoperable cable portion (1064):** This portion contains the Land portion (1004), Submarine portion (1005), and Land portion (1004) segments. + - Land portion (1004):** Contains TTE (1010), CTE (1014), MC (1012), and PFE (1013). + - Submarine portion (1005):** Contains an Optical submarine repeater (1020), three Repeater units, and a BU (1022). + - Interfaces:** + - System interface (A):** Located at the ends of the terminal portions. + - Landing points or beach joints (B):** Located at the boundaries between land and submarine portions. + - Interoperable cable portion interface (C):** Located at the boundaries between the terminal and interoperable portions. + - Optical interface (2009):** Represented by a circle. + - System interface (2008):** Represented by a solid black circle. + - Other labels:** + - Supervisory section (2007) + - Elementary cable section (1028) + - Cable jointing box (5013) - indicated by an 'X' on the cable. + +**Legend:** + +- Optical fibre submarine cable (1019) +- Optical fibre land cable (1018) +- Optical fibre station cable (1017) +- Electrical cable +- Optical interface (2009) +- System interface (2008) + +**NOTES:** + +- NOTE 1 – A denotes system interface +- NOTE 2 – B denotes landing points or beach joints (1006) +- NOTE 3 – X denotes cable jointing box (5013) +- NOTE 4 – C denotes interoperable cable portion interface +- NOTE 5 – Numbers in brackets relate to [ITU-T G.972] + +G.971(20)\_F01b + +Diagram (b) showing a more complex submarine cable system configuration including terminal portions, interoperable cable portions, and various repeaters and interfaces. + +(b) + +![Diagram (c) showing an optical fibre submarine cable system with scientific sensing function. The system is divided into three main sections: Land portion (1004), Submarine portion (1005), and Land portion (1004). On the left land portion, a TTE (1010) is connected to a CTE (1014) via an optical interface (2009). The CTE is connected to a submarine cable (1019) via a system interface (2008) at point B. The submarine portion contains an optical submarine repeater (1020), a repeater with sensor subsystem (2058) or scientific subsystem (2059), a BU (1022), another optical submarine repeater (1020), and a sensor (1069) or sensor set (1071) connected to a P-UJB (1067) and an S-UJB (1068). The right land portion consists of a CTE (1014) connected to a TTE (1010) via an optical interface (2009) at point B, which is then connected to a system interface (2008) at point A. Various components are labeled with their reference numbers in parentheses. A legend at the bottom left defines the line types: thick grey for submarine cable (1019), thin grey for land cable (1018), thin black for station cable (1017), thin black for electrical cable, an oval for optical interface (2009), and a circle with a dot for system interface (2008). Four notes are provided: NOTE 1 – A denotes system interface; NOTE 2 – B denotes landing points or beach joints (1006); NOTE 3 – Numbers in brackets relate to [ITU-T G.972]; NOTE 4 – BU only for sensor sets is related to [ITU-T G.9730.1].](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg) + +Diagram (c) showing an optical fibre submarine cable system with scientific sensing function. The system is divided into three main sections: Land portion (1004), Submarine portion (1005), and Land portion (1004). On the left land portion, a TTE (1010) is connected to a CTE (1014) via an optical interface (2009). The CTE is connected to a submarine cable (1019) via a system interface (2008) at point B. The submarine portion contains an optical submarine repeater (1020), a repeater with sensor subsystem (2058) or scientific subsystem (2059), a BU (1022), another optical submarine repeater (1020), and a sensor (1069) or sensor set (1071) connected to a P-UJB (1067) and an S-UJB (1068). The right land portion consists of a CTE (1014) connected to a TTE (1010) via an optical interface (2009) at point B, which is then connected to a system interface (2008) at point A. Various components are labeled with their reference numbers in parentheses. A legend at the bottom left defines the line types: thick grey for submarine cable (1019), thin grey for land cable (1018), thin black for station cable (1017), thin black for electrical cable, an oval for optical interface (2009), and a circle with a dot for system interface (2008). Four notes are provided: NOTE 1 – A denotes system interface; NOTE 2 – B denotes landing points or beach joints (1006); NOTE 3 – Numbers in brackets relate to [ITU-T G.972]; NOTE 4 – BU only for sensor sets is related to [ITU-T G.9730.1]. + +G.971(24)\_F01c + +(c) + +**Figure 1 – Examples of (a) optical fibre submarine cable systems, (b) interoperable optical fibre submarine cable systems, (c) optical fibre submarine cable systems with scientific sensing function** + +NOTE – Figure 1(b) illustrates an example of the optical fibre submarine cable system with terrestrial network. The land repeaters in the land portion may or may not be a part of the interoperable cable portions. + +# 7 Relationship among Recommendations relevant to optical fibre submarine cable systems + +Relationships among the various Recommendations pertaining to optical fibre submarine cable systems are shown in the flow chart presented in Figure 2. Recommendations relevant to optical fibre submarine cable systems can be categorized into four groups. The first group covers general aspects of optical fibre submarine cable systems. This category is composed of ITU-T G.971, [ITU-T G.972] and [b-ITU-T G Suppl.41]. These documents respectively describe general features, definitions and design guidelines for optical fibre submarine systems. The second group deals with the components or functions used in optical fibre submarine systems. This category is composed of [b-ITU-T G.975], [b-ITU-T G.975.1], [b-ITU-T G.976], [b-ITU-T G.978] and [b-ITU-T G.979]. These documents describe forward error correction, advanced forward error correction, test methods, optical fibre cables and characteristics of monitoring systems relevant to optical fibre submarine systems. The third group describes system requirements. This category contains [ITU-T G.973], [ITU-T G.973.1], [ITU-T G.973.2], [ITU-T G.974], [ITU-T G.977] and [ITU-T G.977.1]. Respectively, these Recommendations consider: the repeaterless, longitudinal compatible repeaterless, single channel interface based repeaterless, regenerative and optically amplified, and transverse compatible dense wavelength division multiplexing (DWDM) repeated submarine systems. The final group describes system with sensing capabilities. This category includes [ITU-T G.9730.1] for submarine cable systems dedicated to sensing and [ITU-T G.9730.2] for submarine cable systems capable of supporting both sensing and telecommunications. + +![A hierarchical diagram showing relationships among ITU-T Recommendations for optical fibre submarine cable systems. The diagram is divided into three main categories: General, System component/function, and Transmission system, with a final category for System with sensing capabilities. Each category contains a list of specific recommendations in boxes connected by lines.](d4af765160d04ecef538e5066006dc77_img.jpg) + +``` + +graph TD + subgraph General + G1[General features +ITU-T G.971] + G2[Definitions +[ITU-T G.972]] + G3[Design guidelines for +submarine systems +[b-ITU-T G Suppl.41]] + end + + subgraph System_component_function [System component/function] + SCF1[Characteristics of optical fibre submarine cables +[b-ITU-T G.978]] + SCF2[Forward error correction for high bit-rate DWDM submarine systems +[b-ITU-T G.975.1]] + SCF2_1[Forward error correction for submarine systems +[b-ITU-T G.975]] + SCF3[Test method +[b-ITU-T G.976]] + SCF4[Characteristics of monitoring systems for optical submarine cable systems +[b-ITU-T G.979]] + end + + subgraph Transmission_system [Transmission system] + TS1[Regenerative submarine systems +[ITU-T G.974]] + TS2[Optically amplified submarine systems +[ITU-T G.977]] + TS2_1[Transverse compatible DWDM application for repeated optical fibre submarine cable systems +[ITU-T G.977.1]] + TS3[Repeaterless submarine systems +[ITU-T G.973]] + TS3_1[Longitudinal compatible DWDM application for repeaterless submarine systems +[ITU-T G.973.1]] + TS3_2[Multichannel DWDM applications with single channel optical interfaces for repeaterless optical fibre submarine cable systems +[ITU-T G.973.2]] + end + + subgraph System_with_sensing_capabilities [System with sensing capabilities] + SSC1[Dedicated scientific sensing submarine cable systems +[ITU-T G.9730.1]] + SSC2[Scientific monitoring and reliable telecommunication submarine cable systems +[ITU-T G.9730.2]] + end + + General --- SCF + General --- TS + General --- SSC + +``` + +**General** + +- General features ITU-T G.971 +- Definitions [ITU-T G.972] +- Design guidelines for submarine systems [b-ITU-T G Suppl.41] + +**System component/function** + +- Characteristics of optical fibre submarine cables [b-ITU-T G.978] +- Forward error correction for high bit-rate DWDM submarine systems [b-ITU-T G.975.1] + - Forward error correction for submarine systems [b-ITU-T G.975] +- Test method [b-ITU-T G.976] +- Characteristics of monitoring systems for optical submarine cable systems [b-ITU-T G.979] + +**Transmission system** + +- Regenerative submarine systems [ITU-T G.974] +- Optically amplified submarine systems [ITU-T G.977] + - Transverse compatible DWDM application for repeated optical fibre submarine cable systems [ITU-T G.977.1] +- Repeaterless submarine systems [ITU-T G.973] + - Longitudinal compatible DWDM application for repeaterless submarine systems [ITU-T G.973.1] + - Multichannel DWDM applications with single channel optical interfaces for repeaterless optical fibre submarine cable systems [ITU-T G.973.2] + +**System with sensing capabilities** + +- Dedicated scientific sensing submarine cable systems [ITU-T G.9730.1] +- Scientific monitoring and reliable telecommunication submarine cable systems [ITU-T G.9730.2] + +A hierarchical diagram showing relationships among ITU-T Recommendations for optical fibre submarine cable systems. The diagram is divided into three main categories: General, System component/function, and Transmission system, with a final category for System with sensing capabilities. Each category contains a list of specific recommendations in boxes connected by lines. + +G.971(24) + +**Figure 2 – Relationships among Recommendations relevant to optical fibre submarine cable systems** + +## Annex A + +## Common implementation aspects of optical submarine cable systems for manufacturing, installing and maintenance + +(This annex forms an integral part of this Recommendation.) + +### A.1 Introduction + +This annex outlines the common aspects of submarine cable systems specified in [ITU-T G.973], [ITU-T G.973.1], [ITU-T G.973.2], [ITU-T G.974], [ITU-T G.977], [ITU-T G.977.1], [ITU-T G.9730.1] and [ITU-T G.9730.2] such as manufacturing, installation and maintenance. + +The information provided in this annex is intended as a guide to current practice and is not intended as a Recommendation relating to existing or future systems. + +### A.2 Manufacturing + +#### A.2.1 Quality in optical fibre submarine cable systems + +The high performance and reliability requirements established for an optical fibre submarine cable system can be fulfilled only if stringent quality procedures are applied during designing, manufacturing, and laying of a system. Although quality procedures are particular to each optical fibre submarine cable supplier, the following basic principles generally apply. + +##### A.2.1.1 Qualification of the designs and technologies + +This activity – part of the development process – is intended to demonstrate that the performance of the technology, a component or an assembly is compatible with meeting the overall system performance requirements and provides reasonable assurance that the reliability target can be met. Qualification includes high-stress testing, intended to estimate the durability of the technology, component, or subassembly and to determine the screening procedure. It also includes long-term life testing (some of which might be accelerated, for instance by temperature), the purpose of which is to confirm the validity of the screening procedure and to evaluate the lifetime and/or the reliability of the technology, component or assembly. Qualification of a cable or submarine equipment may also include sea trials. + +##### A.2.1.2 Certification of components and sub-assemblies + +This activity, part of the manufacturing process, is intended to assure the ability of each component or assembly to comply with its performance and reliability specifications, once installed. For submarine equipment, each component is individually certified. The certification is based on the results of screening tests. Its aim is to remove any items or components that may be unsatisfactory, particularly those likely to exhibit early failures. + +##### A.2.1.3 Manufacturing inspection + +This activity, during the manufacturing process, is intended to verify that the quality plan is respected, that each operation is accomplished according to the agreed procedure, and that the result is satisfactory. + +The responsibility for manufacturing inspection can be shared between the manufacturer and the purchaser of an optical fibre submarine cable system. + +##### A.2.1.4 Factory acceptance tests + +After completion of the manufacture of each item (terminal station equipment (TSE) and submerged equipment), functional and performance tests must be carried out in order to release the equipment from the factory. + +This activity, conducted in the factory, should comprise all tests necessary to confirm that TSE (including final software) and submerged equipment (repeater and cable sections) are ready for installation or assembly. The tests should demonstrate that the requirements of the technical specification will be met by the segments and the full network once installed or assembled, if no discrepancy occurs during the installation or assembly period. + +On completion of factory testing, equipment may be tested during a trial period to check its stability. + +#### **A.2.2 Assembly and loading procedure** + +Link assembly consists of jointing the cable sections, the repeaters and the branching units and checking that the guaranteed margin is present for each fibre in each cable section, so as to constitute the submarine portion. Link assembly is usually performed in the cable factory prior to loading. + +Ship loading consists of installing the submarine portion, or fractions of it, on board the cable ship, prior to laying. Ship loading is generally performed with the link unpowered. Tests are conducted periodically during loading to confirm that the performance of the assembled equipment has not been affected by the loading process. + +### **A.3 System installation** + +#### **A.3.1 Submarine route survey** + +A route survey is performed prior to cable laying to select the cable route and means of cable protection (lightweight protection, armour, burial). The route survey consists of studying the sea depth profile, the sea bottom temperature and seasonal variations, the morphology and nature of the sea bottom, the position of existing cables and pipes, the cable fault history, fishing and mining activities, sea current, seismic activity, laws, etc. + +A cable route study should normally be carried out prior to the start of a route survey to determine all environmental, political, economic and practical aspects related to the route. Discussions should be held with local authorities and fishing bodies for this purpose, along with the inspection of landing sites and access points, as necessary. + +An assessment of burial feasibility can also be carried out as part of the route survey, either through direct continuous measurement (e.g., burial assessment survey (BAS)) or discrete periodic measurement (e.g., cone penetrometer testing (CPT)). + +#### **A.3.2 Submarine cable installation** + +Cable laying is normally performed using a recognized cable ship after any necessary route clearance in shallow water has been carried out (e.g., pre-lay grapnel run (PLGR)). + +Laying is normally undertaken only when weather and sea conditions do not pose severe risk of damage to the submarine portion, cable ship and laying equipment, or of injury to personnel. + +The cable may be buried in the seabed to increase cable protection. Burial can be undertaken during laying by using a sea plough towed by the laying cable ship, or after laying using a self-propelled submersible robot or other means. + +During laying, a predetermined cable overlength (slack) is laid, to ensure that the cable is properly laid on the sea bottom. The system should be tested during the laying and at the end of laying, to ensure that no significant system degradation has been induced. Laying testing includes transmission and functional tests and may include tests on redundant subassemblies. To permit testing during cable laying, the link may be powered, provided that safety regulations are respected. + +#### **A.3.3 Land cable installation and testing** + +Land cable tests will be performed after the completion of land cable installation at each site to confirm performances. + +In particular, the return earth system shall be tested after its installation. + +#### **A.3.4 Terminal station equipment installation and testing** + +After completion of terminal station equipment installation activities in the cable terminal station, a site acceptance testing programme should be conducted, based on the factory acceptance test programme already performed. The results of both periods should be compared. In the event of an unfavourable comparison between the two sets of results, the cause of the irregularities should be determined. + +All equipment units provided as spares shall be tested for correct operation by substitution with working units. + +Upon completion of the suite tests, the equipment shall be subject to a continuous confidence trial period to be defined depending on the equipment type. + +Following the site acceptance testing period for each item, interconnection of equipment should be carried out to control their interoperability. A specific integration test plan should then be conducted. The results obtained could be compared with previous results (including technology demonstration). In the event of an unfavourable comparison between the two sets of results, the cause of the irregularities should be determined. + +## **A.4 System commissioning** + +Commissioning testing is performed prior to installing traffic on the system to ensure that the system meets its overall transmission performance contractual requirement, and that all functionalities, with respect to network management, are operating. When extra margins are available at the beginning of life (BOL), it is recommended that they be assessed in order to track the ageing of the system. + +If redundancy is used in the design to meet the reliability performance, redundant components could be used to correct faults occurring during laying or prior to commissioning. However, the aim is to ensure that the number of redundant devices remaining is sufficient to meet, with a high probability, the target for the number of ship repairs. + +Upon completion of the system commissioning period, a continuous transmission segment out-of-service confidence trial should be followed. Carefully controlled procedures should be established to prevent the introduction of errors through human action. Any irregularity, variation alarm or non-routine event observed should be investigated. + +## **A.5 Maintenance** + +#### **A.5.1 Routine maintenance** + +Routine maintenance is performed from the terminal stations using the supervisory system. It consists of periodic monitoring of the system parameters and, when required, preventive redundancy switching. + +#### **A.5.2 Maintenance at sea** + +Optical fibre submarine cable systems can be subject to faults, particularly due to external aggression and component failure. It is important to define and develop well-established and efficient repair procedures and equipment to facilitate repair and limit loss of traffic. + +Maintenance at sea is usually performed using dedicated repair cable ships. + +##### **A.5.2.1 Fault localization** + +For systems equipped with optical submarine repeaters, a first localization to within one supervisory section is obtained using the supervisory system. + +For the end cable sections, cable fault localization may be achieved from the terminal stations, using adequate electrical measurements (resistance, capacitance, insulation, etc.) and optical reflectometry. + +Similarly, cable fault localization may be achieved from the cable ship after cable recovery, using the same methods. + +Electroding can be used to locate the cable route. + +##### **A.5.2.2 Cable recovery** + +During cable recovery, it may be necessary, to limit the mechanical tension applied to the cable, to cut the cable on the sea bottom prior to recovering both ends separately. + +##### **A.5.2.3 Sea repair** + +Several methods can be used for sea repair, depending on the sea depth: + +- Shallow water repair may necessitate additional cable length, but not a repeater. A margin for repair work is generally included in the shallow water optical power budget as the shallow water sections are the most exposed to risk from external aggression, even when precautions have been taken. +- Deep sea repair usually necessitates the addition of a cable length and sometimes a repeater to compensate for the extra attenuation. + +When a fault is identified within one supervisory section, the section may be replaced by a mini system, without further localization. This method may save time but requires more spare equipment. + +Repair safety procedures are applied on board the cable ship and in the terminal station to ensure the safety of the personnel operating on board the cable ship. In particular, power safety procedures involve earthing the cable in the terminal station, on board the cable ship and at the branching unit. + +# Appendix I + +## Data on cable ships and submersible equipment of various countries + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Cable ships + +Cable ships are used for laying optical submarine cables and also for repairing optical submarine cables, including repeaters. A cable ship contains a cable tank, a cable engine and an unwinding/winding pulley. The cable tank houses spooled optical submarine cable and repeaters. The cable engine controls the unwinding/winding speed so that it synchronizes well with the ship's speed. Unwinding/winding pulleys are installed at the bow and/or stern of the ship, and are called bow and stern sheaves, respectively. + +The cable ship also carries submersible equipment for underwater work. Generally, a dynamic positioning (DP) system is used as it automatically maintains the position of the ship at a fixed point without the use of an anchor. + +Table I.1 gives examples of cable ships used in several countries. + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | | | | | | | | | | | | +|--------------------------------------------------------------------------|----------------------|---------------------|--------------------|-----------------------|----------------------|-----------------------------------|-------------------|-------------------|---------------|-----------|----------------------------------------------------|--------------------------|---------------------------|-----------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | | | | | | | | | | | | +| | | | | | | | | Cubic metres (m³) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | | | | | | | | | | | | +| CHINA | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ship belonging to China Submarine Cable Construction Co., Ltd. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Feng Yang Hai Gong (FYHG) | 2010 | 1916.5 | 57.6 | 2.6 | 10 | – | 1 | 350 | 800 | 3 | – | 10 | – | – | 2000 | FYHG is capable of deploying a 5 m sea plough within WD200 m. | | | | | | | | | | | | +| 2) Ships belonging to S.B. Submarine Systems Ltd. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CS Fu Hai | 2000 | 9850 | 105.8 | 12.0 | 12.5 | 45 days | 2 tanks
2 hold | 2736.8
548 | 5200
1042 | 96 | 3.0 | 20 | – | 2 × 3.0 | All | Laying and repair optical fibre systems. | | | | | | | | | | | | +| Bold Maverick | 2001 | 9850 | 105.8 | 12.0 | 12.5 | 45 days | 2 tanks
2 hold | 2736.8
548 | 5200
1042 | 96 | 3.0 | 20 | – | 2 × 3.0 | All | Laying and repair optical fibre systems. | | | | | | | | | | | | +| CS Fu An | 1982 | 10 380 | 141.5 | 11.6 | 12.0 | 38 days | 3 tanks
1 hold | 1200
120 | 2394
309 | 35 | 2 × 3.0 | – | – | 2 × 3.0 | All | Laying and repair optical fibre systems. | | | | | | | | | | | | +| DENMARK | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Ships belonging to Tele Denmark | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Peter Faber | 1982 | 3680 | 78.35 | Ice 3.8
Summer 5.0 | 13.0 | 7000 | 1 tank
1 hold | 310
230 | 600
400 | App. 10 | 3.0 | | 2 × 3.0 | – | 4000 | Reinforced for operation in ice-filled waters.
A-frame for ROV. Two hydraulic double-drum warping winches. | | | | | | | | | | | | +| Lodbrog | 1985/2002 | 12 503 | 143.4 | 8.50 | 16.0 | 10 000 | 6 | 2940 | 5040 | 84 | 2 × 4.0 (25 t) | 2 × 6 (6 t) | – | 2 × 3.0 | All | Laying/burying and repair of all types of cables (coaxial, optical fibre and power cables).
ROV capability, safe working load (SWL) 8 tonne. | | | | | | | | | | | | +| FINLAND | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ship belonging to Sonera Ltd | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| M/S Telepaatti | 1978 (modification) | 450 | 42.6 | 3.0 | 12 | – | 1 | – | 350 | – | 2 linear engines with 3 caterpillar tracks on each | 3.0 | | 300 | | Laying of all types of telecom cables. Specially equipped for cable route survey and cable repair. Fully automatic autopilot and dynamic positioning-system (DP-system). | | | | | | | | | | | | + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | | | | +|------------------------------------------------------------------|---------------------------|---------------------|--------------------|-----------|----------------------|-----------------------------------|-----------------|--------------------------------|---------------|-----------|---------------------|----------------------------------------------------|---------------------------|-----------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | | | | +| | | | | | | | | Cubic metres (m 3 ) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | | | | +| 2) Ship belonging to YIT Primatel | | | | | | | | | | | | | | | | | | | | +| c/s Telepaatti | 1978
Modification 1999 | 450 | 42.6 | 3.0 | 10.5 | – | 1 | 250 | 260 | – | – | 2 linear engines with 3 caterpillar tracks on each | 3.0 | – | 300 | Laying of all types of telecom cables and < 150 mm power cables.
Specially equipped for cable route survey and cable repair.
Fully automatic autopilot and DP-system. | | | | +| FRANCE | | | | | | | | | | | | | | | | | | | | +| 1) Ships belonging to France Telecom Marine | | | | | | | | | | | | | | | | | | | | +| Chamarel (formerly Vercors) | 1974 | 11 000 | 136 | 7.2 | 16.0 | 12 000 | 3 | 2425 | 4900 | 144 | 3.0 | 24 | 3.0 | Chute | All | Laying and repair of all types of telecom cables.
Burying of cables with plough and 200 kW Hector 4. | | | | +| Léon Thevenin | 1983 | 6800 | 107 | 6.24 | 15.0 | 10 000 | 2 + 1 | 1420 | 2000 | 11 | 3.4 | 12 | 3.0 | Chute | All | Laying and repair of all types of telecom cables.
Burying of cables using 300 kW Hector 5. | | | | +| Raymond Croze | 1983 | 6800 | 107 | 6.24 | 15.0 | 10 000 | 2 + 1 | 1420 | 2000 | 11 | 3.4 | 12 | 3.0 | Chute | All | Laying and repair of all types of telecom cables.
Burying of cables using 250 kW Hector 3. | | | | +| René Descartes | 2002 | 15 450 | 114.50 | 7.42 | 16.0 | 12 000 | 4 | 3250 | 5500 | 210 | 4.0 | 20 | Aft sheave 3.0 m | Sheave | All | Stem concept cable ship. Laying and repair of all types of telecom cables.
Burying of cables with plough and 250 kW ROV Hector 6. | | | | +| 2) Ships belonging to Alda Marine | | | | | | | | | | | | | | | | | | | | +| Ile de Sein
Ile de Batz
Ile de Brehat | 2002 | 18 006 | 140.4 | 8.016 | 15.0 | 15 000 | 2 + 2 | 3000 | 5500 | 202 | 4.0 | 21 | NA | 3.0 | All | Laying and repair of all types of telecom cables.
Burying of cables with 2/3m Rock plough. Sea state 7 A-frame. | | | | +| Ile de Ré | 1983
rebuilt 2002 | 12 687 | 143.4 | 7.23 | 16.0 | 11 000 | 3 + 3 | 2900 | 4500 | 84 | 2 × 4.0 | NA | NA | 3.0 | All | Laying and repair of types of cable.
ROV to 2500 m. A plough is available. | | | | + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | | | | | | | | | | | | +|---------------------------------------------------------------------------------------|----------------------|---------------------|--------------------|-----------|----------------------|-----------------------------------|-----------------|--------------------------------|---------------|-----------|---------------------|--------------------------|---------------------------|-----------------------------|-------------------------|------------------------------------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | | | | | | | | | | | | +| | | | | | | | | Cubic metres (m 3 ) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | | | | | | | | | | | | +| ITALY | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ships belonging to Elettra TLC S.p.A | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Teliri | 1996 | 6500 | 111.5 | 6.5 | 14.01 | 10 000 | 3 | 2000 | 2600 | 70 | 2 × 3.5 | 18 | 3 | 4 | All | Laying and repair optical fibre systems. | | | | | | | | | | | | +| Antonio Meucci | 1987 | 7900 | 114 | 6.5 | 12.0 | 10 000 | 3 | 1500 | 2600 | 80 | 2 × 3.5 | 12 | 3 | 3 | All | Laying and repair optical fibre systems. | | | | | | | | | | | | +| 2) Ship belonging to Prysmian Cavi e Sistemi Energia S.r.l. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Giulio Verne | 1984 | 16 900 | 133.18 | 8.5 | 10 | 7000 | 2 | 2600 | 7000 | 10 | 6.0 (55 t) | 1 (Pads type 10 t) | – | 6.0 | All | Lay and repair from the stern. | | | | | | | | | | | | +| JAPAN | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ships belonging to Kokusai Cable Ship (KCS) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| KDDI Ocean Link | 1992 | 11 700 | 133.2 | 7.0 | 15 | 10 000 | Main 3 Spare 4 | 2600 | 4500 | 57 | 3.6 | 21 | 3.2 | 4.0 | All | Laying by linear engine. Lays and repairs all types of submarine cables. | | | | | | | | | | | | +| KDDI Cable Infinity | 2019 | TBA | 113.1 | 7.1 | 12 | 10 000 | Main 2 Spare 2 | 2070 | 4500 | 70 | 4.0 | – | – | 4.0 | All | Laying and repair of all types of telecom cables.
Laying of power cables. | | | | | | | | | | | | +| 2) Ships belonging to NTT World Engineering Marine Corporation (NTT-WE Marine) | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CS Subaru | 1999 | 9557 | 123.3 | 7.0 | 13.2 | 8800 | Main 2 Spare 2 | 2770 | 4000 | 50 | 4.0 | 21 | – | 3.2 | All | Lays and repairs all types of telephone cables. | | | | | | | | | | | | +| C/S VEGA | 1984 | 2293 | 74.3 | 4.5 | 13.0 | 4500 | 2 | 169 | 250 | – | 3.0 | N/A | 2.5 | N/A | All | Lays and repairs for non-powered telephone cable system.
DP, ROV system. | | | | | | | | | | | | +| ORION | 2013 | 299 | 54.9 | 3.4 | 10.0 | 3708 | 2 | 100 | 200 | N/A | 2.5 | N/A | N/A | 2.5 | 500 | Domestic maintenance purpose. | | | | | | | | | | | | +| KIZUNA | 2017 | 8598 | 108.64 | 6.014 | 13.8 | 9500 | Main 2 Spare 2 | 1984.18 | 2184.03 | 0 | 3.6 | N/A | N/A | 2.5 | All | | | | | | | | | | | | | + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | | | | | | | | | | | | +|------------------------------------------------------------|----------------------|---------------------|--------------------|-----------|----------------------|-----------------------------------|-----------------|--------------------------------|---------------|-----------|---------------------|--------------------------|---------------------------|---------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------|--|--|--|--|--|--|--|--|--|--|--| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | | | | | | | | | | | | +| | | | | | | | | Cubic metres (m 3 ) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | | | | | | | | | | | | +| UNITED KINGDOM | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ship belonging to British Telecommunications plc | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Sovereign | 1991 | 13 018 | 131 | 7.0 | 13.5 | 14 000 | 4 | 2800 | 6200 | 90 | 3.50 | | 3.00 | 3.50 | All | Lays, repairs all types of coaxial and optical fibre cable. (operated by C&W marine.) | | | | | | | | | | | | +| 2) Ships belonging to Global Marine Systems Ltd | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MV Cable Installer | 1980 | 6065 | 89.42 | 5 | 12 | 42 days | 4 | 840 | 1600 | None | 3.0 | 4-track pair | – | 3.0 | – | Ditto (no plough). Repeaterless installation vessel fully DP Cegelec 901 system. | | | | | | | | | | | | +| Seaspread | 1980 | 10 887 | 116 | 6.8 | 13 | 65 days | 2 | 1010 | 1701 | – | 2 × 3 | – | – | 3 | All | Lays/repairs by aft drums. Burial by plough. Lays/repairs armoured and lightweight cables. | | | | | | | | | | | | +| Pacific Guardian | 1984 | 7526 | 116 | 6.32 | 14.0 | 8000 | 3 | 1416 | 3470 | 96 | 3.5 | | 3.00 | 3.00 | All | Laying by linear cable engine. Lays and repairs armoured and lightweight cables. | | | | | | | | | | | | +| Sir Elic Sharp | 1988 | 7526 | 115 | 6.3 | 13.5 | 9600 | 3 | 1416 | 1700 | 96 | 2 × 3.5 | – | 3 | 3 | All | Laying by linear cable engine. Repairs and lays armoured and lightweight cables. Post lay/repair burial by integral ROV. | | | | | | | | | | | | +| 3) Ship belonging to Global Marine Systems Ltd | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| MV Cable Innovator | 1995 | – | 142 | 8.3 | 14.5 | 42 days | 4 | 4900 | 7500 | 180 | 4.0 | 21 pairs (min) | – | 4.0 | – | Simplex D/P system. Lays/repairs cables. | | | | | | | | | | | | +| MARSHALL ISLANDS | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| 1) Ship belonging to TE CONNECTIVITY SUBCOM, SLU. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Teneo | 1992 | 4000 | 81 | 5.7 | 13 | 4200 | 2 | 435 | 1000 | 20 | 2 × 3.5 | 1 × 9 | 2 × 3 | 1 × 3 | All | Lays and repairs of all types of telephone cables. | | | | | | | | | | | | +| 2) Ship belonging to CS Tyco Decisive, Inc. | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CS Decisive | 2003 | 16 148 | 140 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T
1.15
80 T .046 | – | The Decisive is capable of deploying SubCom's ROVs; Triton STs and SMD Nereus and SubCom's 3 m ploughs up to 80 T bollard pull. | | | | | | | | | | | | + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | | | +|---------------------------------------------------------------|----------------------|---------------------|--------------------|-----------|----------------------|-----------------------------------|-----------------|------------------------------------------|---------------|-----------|---------------------|--------------------------|---------------------------|------------------------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | | | +| | | | | | | | | Cubic metres (m 3 ) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | | | +| 3) Ship belonging to CS Tyco Dependable, Inc. | | | | | | | | | | | | | | | | | | | +| CS Dependable | 2002 | 16 148 | 139.1 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T 1.15
80 T .046 | – | The Dependable is capable of deploying SubCom's ROVs; Triton STs and SMD Nereus and SubCom's 3 m ploughs up to 80 T bollard pull. | | | +| 4) Ship belonging to CS Tyco Durable, Inc. | | | | | | | | | | | | | | | | | | | +| CS Durable | 2003 | 16 148 | 139.1 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T 1.15
80 T .046 | – | The Durable is capable of deploying SubCom's ROVs; Triton STs and SMD Nereus and SubCom's 3 m ploughs up to 80 T bollard pull. | | | +| 5) Ship belonging to CS Tyco Reliance, Inc. | | | | | | | | | | | | | | | | | | | +| CS Reliance | 2001 | 16 148 | 140 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T 1.15
80 T .046 | – | The Reliance is capable of deploying SubCom's ROVs; Triton STs and SMD Nereus and SubCom's 3 m ploughs up to 80 T bollard pull. | | | +| 6) Ship belonging to CS Tyco Resolute, Inc. | | | | | | | | | | | | | | | | | | | +| CS Resolute | 2002 | 16 148 | 140 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T 1.15
80 T .046 | – | The Resolute is capable of deploying SubCom's ROVs; Triton STs and SMD Nereus and SubCom's 3 m ploughs up to 80 T bollard pull. | | | +| 7) Ship belonging to CS Tyco Responder, Inc. | | | | | | | | | | | | | | | | | | | +| CS Responder | 2001 | 16 148 | 140 | 8.4 | 13.9 | 25 000 | 3 Main | 1138.6 | 8841 | | 2 × ODIM 4.0 | ODIM 20 pairs | – | 30 T 0.6 m
2 × 50 T 1.15
80 T .046 | – | | | | +| UNITED STATES OF AMERICA | | | | | | | | | | | | | | | | | | | +| Ship belonging to Transceanic Cable Ship Company, LLC. | | | | | | | | | | | | | | | | | | | +| CS Global Sentinel | 1991 | 16 118 | 145.7 | 8.08 | 15 | 10 000 | 3 main, 4 spare | 3258 (main, total)
164 (spare, total) | 6098 | 100+ | 2 × 3.7 | 1 × Dowty 21 pairs | 2 × 3 | 1 × trough/Chute type | – | The Global Sentinel is capable of deploying TRITON ST ROVs, as well as SMD 1.5 m sea ploughs. | | | + +**Table I.1 – Examples of cable ships** + +| Name of ship | Year of construction | Displacement (tons) | Overall length (m) | Draft (m) | Normal speed (knots) | Range (autonomy) (nautical miles) | Number of tanks | Cable capacity | | | Cable gear | | | | Max operating depth (m) | Capability | +|---------------------------------------------------------------------------------------------------------------|---------------------------|---------------------|-----------------------------------------------------------------------------------|---------------------------------|----------------------|-----------------------------------|-------------------|--------------------------------|---------------|-----------|---------------------|----------------------------|---------------------------|-----------------------------|-------------------------|------------------------------------------------------------------------------------| +| | | | | | | | | Cable | | Repeaters | Cable engine | | Unwinding pulley | | | | +| | | | | | | | | Cubic metres (m 3 ) | Weight (tons) | | Drum (diameter) (m) | Linear (pairs of wheels) | Bow sheave (diameter) (m) | Stern sheave (diameter) (m) | | | +| UNITED ARAB EMIRATES
Ships belonging to E-marine PJSC | | | | | | | | | | | | | | | | | +| CS Etisalat | 1990 | 2221 | 74.7 | 4.5 | 13 | 35 days | 3 | 667 | 600 | 12 | 3 | 6 | 3 | 4 | Unlimited | Surface lay, maintenance, ROV inspection and jet burial. | +| CS NIWA | 1990 | 16 375 | 145.66 | 8.08 | 15 | 60 days | 3 main
4 spare | 3258 | 6098 | 152 | 4 | 18 | 4 | 4 | Unlimited | Surface lay, plough burial, maintenance, work class ROV inspection and jet burial. | +| CS UAA | 1972
Converted in 1996 | 7800 | 133.7 | 6.15 | 13 | 48 days | 3 main
1 spare | 3360 | 4500 | 120 | 4 | 18 | 4 | 4 | Unlimited | Surface lay, plough, maintenance, work class ROV inspection and jet burial. | +| REPUBLIC OF KOREA
Ships belonging to LS Marine Solution | | | | | | | | | | | | | | | | | +| SEGERO | 1998 | 8323 | 115 | 7.8 | 12 | | 4 | 45002047 | 22183890 | 70ea120 | 2 × 4 | 4 pairs
2 × 4 s
DOHB | – | 3.6 | Unlimited | Surface lay, Plough burial, Repair & Maintenance, ROV burial, Inspection | +| MALTA
1) Ship belonging to J. Ray Mcdermott (Norway) AS Of Oslo Norway (as registered owner) | | | | | | | | | | | | | | | | | +| NORTH OCEAN 102 | 2008 | 11 680 Gross Tons | 118.97 (length according to Article 2(8) of the International Tonnage Convention) | Moulded Draught (Reg 4(2) 6.70) | 15 | Not known (N/K) | N/K | N/K | N/K | N/K | N/K | N/K | N/K | N/K | N/K | – | +| 4) Prysmian Powerlink Services Limited, Chickenhall Lane, Eastleigh, Hampshire SO506YU, United Kingdom | | | | | | | | | | | | | | | | | +| ULISSE | 2010 | 10 490 | 115.23 | 5.33 | – | – | – | – | – | – | – | – | – | – | – | – | + +## I.2 Submersible equipment + +Various types of submersible equipment are used to support the installation and maintenance of an optical submarine cable system. Typical examples of submersible equipment include a plough and a remotely operated vehicle (ROV). + +A plough is towed by a cable ship and is used to lay the optical submarine cable while burying it. + +An ROV is used when a plough is not available. A submersible craft assisting repair and burial (SCARAB) is a type of ROV. ROVs typically enable inspection, repair, and burial. + +Table I.2 gives examples of submersible equipment used in several countries. + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|--------------------------------------------------------------------------------|--------------------------------|--------------------|-----------------------------|------------|---------------------------------|------------------------------|---------------------------------|-------------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------| +| CHINA | | | | | | | | | | | +| 1) Submersible belonging to China Submarine Cable Construction Co.,Ltd. | | | | | | | | | | | +| SHARK-600 Submersible Plough system | 12 | 11.01 | 4.42 | 2 | Water jet tool | Max burial depth: 5m | Towed | 200 | 25 T | Lay and bury all types of cables. | +| 2) Submersibles belonging to S.B. Submarine Systems Ltd. | | | | | | | | | | | +| SMD MD3 | 25 | 10.3 | 5.1 | 4.7 | Articulated towed plough system | 3 m | Towed by ship | 1500 | 80 T | | +| SMD Hi- Plough | 27 | 10.3 | 5.1 | 7.5 | Injecting/Jetting | Up to 3.25 m | Towed by ship | 200 | 20 T | | +| ROV SEA LION | 6.5 | 3.2 | 2.9 | 2.9 | Jet burial tool | 1.5 m | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| ROV SEA LION III | Free Fly 17.25
Tracked 18.4 | 6.5 | Free fly 3.7
Tracked 5.2 | 3.1 | Jet burial tool | 3.0 m | Hydraulic thrusters &/or tracks | 2500 | 600 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| FRANCE | | | | | | | | | | | +| Submersibles belonging to France Telecom Marine | | | | | | | | | | | +| ELISE2 Submersible Plough system | 17 | 7.60 | 2.90 | 2.95 | Ploughshare | Immediate burial up to 1.1 m | Towed by support ship | 1500 | | Lay and bury all types of cables. | +| ELISE3 Submersible Plough system | 17 | 7.60 | 2.90 | 2.95 | Ploughshare | Immediate burial up to 1.1 m | Towed by support ship | 1500 | | Lay and bury all types of cables. | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|------------------------------------------------------------|-------------------------------|--------------------|-----------|------------|-----------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------|-------------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Self-advancing buried system CASTOR2 | 12 | 7.0 | 2.40 | 3.00 | Trenching wheel or chain | Burial of existing cables down to 2 m | Tracked vehicle | 1000 | | Burial of cables and pipes.
Visual inspection. | +| ROVs HECTOR 3, 4, 5 & 6 | 9 | 4.0 | 3.50 | 2.10 | High-pressure water jets | Up to 1.5 m depth | Thrusters (inspection)
Back drive (burial) | 2000 | | Visual inspection, post-lay burial, cable location, cable manipulation, cable cutting. | +| Remote control submersible Scorpio 2000 | 3.4 | 2.9 | 1.5 | 2.11 | High-pressure water jets | Up to 60 cm depth | Thrusters | 1000 | | Visual inspection, post-lay burial, cable location/manipulation/cutting. | +| ITALY | | | | | | | | | | | +| Submersibles belonging to Elettra TLC SpA | | | | | | | | | | | +| Plough Taurus 1 | 14 | 9 | 4.6 | 4.5 | Plough share | Up to 1 m | Towed by cable ship | 1500 | 50 | Lay and bury all types of cables. | +| Plough Taurus 2 | 16 | 9.5 | 4.5 | 5.1 | Plough share | Up to 1.5 m | Towed by cable ship | 1500 | 50 | Lay and bury all types of cables. | +| ROV – Phoenix 2 | 6.8 | 4.8 | 2 | 2.6 | High/low-pressure jetting | Up to 1.2 m | 8 Hydraulic thrusters | 1000 | | Visual inspection, post-lay burial, cable location/manipulation/cutting. | +| ROV-T200 | Free-fly mode 6, Track mode 7 | 3.1 | 2 | 2.2 | High/low-pressure jetting | Up to 1.2 m | 4 vertical and 4 horizontal thrusters | 2500 | | Visual inspection, post-lay burial, cable location/manipulation/cutting. | +| UNITED KINGDOM | | | | | | | | | | | +| Submersibles belonging to Global Marine Systems Ltd | | | | | | | | | | | +| Submersible trencher | 17.0 | 6.6 | 4 | 3.4 | Fluidization and cutting jets and dredge pump | Up to 1 m depth with cutting and fluidization jets | Three vertical and four horizontal thrusters, track drive differential steering | 274 | | Trench in existing cable and pipe. | +| Submersible Plough system | 9.75 | 6.1 | 2.6 | 2.6 | Ploughshare proceeded by disc | Immediate burial of cable on ploughing | Towed by support ship | 900 | | Lay and bury cable, umbilical and pipe in one action giving full cable protection. | +| Remote control submersible 2 off Cirus A&B | 3.2 | 3.5 | 2.1 | 2.3 | Water jets | Trenching capability 0.3 m | Thrusters (7) | 1000 | | Visual inspection, cable location/inspection/deburial, manipulation.
Tools include cable cutter, cable gripper and two manipulators with line cutters. | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|----------------------------------------------------|---------------|--------------------|-----------|------------|-----------------------------------------------------------------|--------------------------------------------------------------------------|----------------------------------------|--------------------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Plough 2 off A&B | 14.5 | 9 | 4.1 | 4 | Passive blade | Trenching capability 1.0 m | Towed | 1000 | | Steerable, repeater burial. | +| Remote control submersible ROV 128 | 7.5 | 2.9 | 1.8 | 2.0 | Jetting tool | Trenching capability 0.6 m | Tracked burial
Thrusters survey | 1000 (burial)
2000 (survey) | | Tools include cable cutter, cable gripper and two manipulators with line cutters. | +| Underwater vehicle – MARLIN | 7.8 | 4.191 | 2.438 | 3.175 | Burial skid | To 1.0 m
(Optimized for 0-30 kPa soil) | Hydraulic driven thrusters | 2500 | | Burial, deburial, inspection. Maintenance and repair. Tools include cable cutter, cable gripper. | +| Scarab I – Umbilically tethered ROV | 3.2 | 2.74 | 1.82 | 1.52 | Jetting tool | Up to 0.6 m | Thrusters:
2 vertical
4 vectored | 2000 | | Cable detection and inspection. Visual survey. Cable manipulation and cutting. Debris elimination. Cable and repeater burial/deburial. | +| Subtrack – ROV | 10.0 | 8.0 (Max) | 3.7 | 3.8 | Jetting tool | Burial to 1.0 m | Electro-hydraulic track drives | 1000 | | Cable burial and deburial. Inspection. Maintenance and repair. | +| EUREKA: Deepwater burial + trenching system | 17 (Max) | 5.5 | 4.2 | 3.85 | Jetting tool
Rock wheel cutter
Mechanical chain excavator | 1 m
1.2 m
2.2 m | Electro-hydraulic track drives | 1500 | | Capable of burying cable, small flexible flowlines and also rigid pipes. Can also debury cable and restore. Visual and electronic inspections. | +| Plough 5 | 14.0 | 9.0 | 4.6 | 3.7 | Passive blade | Variable from 0-1100 mm
(600-900 mm in all conditions) | Towed | 1000 | | Simultaneously lay and bury cables and umbilicals at varying depths. | +| Plough 6 and 7 | 14.0 | 9.0 | 4.6 | 3.7 | Passive blade | Max burial depth:
1100 mm | Towed | 1000 | | Simultaneously lay and bury cables and umbilicals at varying depths. | +| Cable Plough 1000 mm | 14.4 | 9.75 | 4.1 | 3.9 | Passive blade | 1000 mm
(Good conditions:
1100 mm;
Repeaters/Joints:
500 mm) | Towed | 1000 | | Simultaneously lay and bury cables and umbilicals at varying depths. | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|--------------------------------------------------|---------------------------------------|--------------------|---------------------------------------|---------------------------------------|--------------------------------|--------------------------------------------------------|---------------------------------------------------------------------|-------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| DENMARK | | | | | | | | | | | +| Submersibles belonging to Telecom Denmark | | | | | | | | | | | +| Plough D | 13.5 | 9.0 | 4.6 | 3.7 | Plough share | Variable from 0-1100 mm (600-900 mm in all conditions) | Towed by host vessel | 1500 | | Lay and bury telecom cables, power cables and umbilicals.
Cables: Up to 120 mm $\phi$ (bury).
Joints and repeaters: Up to 400 mm $\phi$ (pass). | +| Plough 7 | 13.5 | 9.0 | 4.6 | 3.7 | Plough share | Variable from 0-1100 mm (600-900 mm in all conditions) | Towed by surface vessel | 1000 | | Lay and bury fibre optic cables, power cables and umbilicals. | +| Subtrack-Subsea tractor | 10.0 | 8.0 (Max) | 3.7 | 3.8 | Jetting tool | Burial to 1.0 m | Electro-hydraulic track drives | 1000 | | Cable burial and deburial.
Inspection.
Maintenance and repair. | +| Super Phantom S4-ROV | 0.09 | 1.5 | 0.75 | 0.6 | – | – | Thrusters
4 prop fwd/aft
2 prop vertical
2 prop transverse | 300 | | Inspect cables and other underwater objects. Can also be used to inspect seabed conditions. | +| JAPAN | | | | | | | | | | | +| 1) Submersibles belonging to KCS | | | | | | | | | | | +| MARCAS-IV-ROV | Jet tool mode: 17.0 | 6.5 | Jet tool mode: 3.65 | Jet tool mode: 3.0 | Water jet tool | Up to 3.0 m | 4 horizontal, 4 vertical and 2 lateral thrusters | 2500 | | Post-lay burial, maintenance of cable. Can survey seabed. | +| MARCAS-V-ROV | Jet tool mode: 8.7
Track mode: 9.3 | 5.4 | Jet tool mode: 3.0
Track mode: 3.1 | Jet tool mode: 2.1
Track mode: 2.7 | Water jet tool | Up to 2.0 m | 4 horizontal, and 4 vertical | 3000 | | Post-lay burial, maintenance of cable. Can survey seabed. | +| PLOW-II | 18.5
Jet tool mode: 20.0 | 9.5 | 5.6 | 5.0 | Plough share
Water jet tool | Up to 3.0 m | Towed by cable ship | 1500 | 80 | Simultaneously lay and bury cables and umbilicals at varying depth. | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|--------------------------------------------------------------------------------------------------|---------------|--------------------|-----------|------------|---------------------------------|----------------------------------------------------------|-------------------------------------------------------|-------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| 2) Submersibles belonging to NTT-WE Marine | | | | | | | | | | | +| Plough-type 7 Submarine cable burying system | 21 | 9.1 | 5.1 | 6.0 | – | Up to 2.0 m depth immediate burial of cable on ploughing | Towed by support ship | 1500 | | Simultaneous or post-lay burial of cable. | +| CARBIS-II ROV system (C/S VEGA) | 8.0 | 3.2 | 2.1 | 2.8 | Water jetting | Trenching capability 1.5 m | Vertical and horizontal thrusters | 2500 | | Cable detection & inspection visual survey.
Cable manipulation & cutting.
Cable & repeater burial. | +| CARBIS-III ROV system (C.S Subaru) | 9.0 | 3 | 3.4 | 2.1 | Water jetting | Trenching capability 3.0 m | Vertical and horizontal thrusters | 2000 | | Cable detection & inspection visual survey.
Cable manipulation & cutting.
Cable & repeater burial. | +| CABRIS-IV ROV system (KIZUNA) | 7.4 | 3.6 | 2.2 | 3.3 | Water jetting | Trenching capability 1.5 m | Vertical and horizontal thrusters | 2500 | | Cable detection & inspection visual survey.
Cable manipulation & cutting.
Cable & repeater burial. | +| UNITED STATES OF AMERICA
Submersibles belonging to TE CONNECTIVITY SUBCOM, SLU. | | | | | | | | | | | +| Arado 1 | 14.0 | 10.5 | 6.0 | 4.3 | Towed plough system | 1.5 m burial | Towed by ship. 1 thruster for launches and recoveries | 1400 | | ARADO 1 is a towed burial tool employing state-of-the-art burial features. It can achieve 1.5 m burial depth in up to 1400 m water depth. | +| SMD MD3 | 25 | 9.3 | 5.0 | 4.4 | Articulated towed plough system | 3 m | Towed by ship | 1500 | 80 T | | +| SMD MD3 DF | 25 | 9.3 | 5.0 | 4.4 | Articulated towed plough system | 3 m | Towed by ship | 1500 | 80 T | | +| SeaStallion 1 | 32 | 13.8 | 5.4 | 5.3 | Towed plough system | 3 m | Towed by ship | 2000 | 100 T | | +| SeaStallion 2 | 32 | 13.8 | 5.4 | 5.3 | Towed plough system | 3 m | Towed by ship | 2000 | 100 T | | +| SeaStallion 3 | 32 | 13.8 | 5.4 | 5.3 | Towed plough system | 3 m | Towed by ship | 2000 | 100 T | | +| SeaStallion 4 | 32 | 13.8 | 5.4 | 5.3 | Towed plough system | 3 m | Towed by ship | 2000 | 100 T | | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|-------------------------------|------------------------------|--------------------|-----------|------------|---------------------|-----------------------|---------------------------------|-------------------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------| +| SeaStallion SEP | 12 | 8.0 | 4.2 | 4.0 | Towed plough system | 2 m | Towed by ship | 1000 | 50 | Sea Stallion SEP is a dedicated Shore End Plough. | +| SMD QT800 | 21 (free fly) 22 (tracked) | 5.4 | 4.6 | 3.3 | Jet burial tool | 3 m | Hydraulic Thrusters &/or tracks | 2500 | 800 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST213 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST214 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST215 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST216 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST273 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Triton ST218 ROV | 6.3 (free fly) 7.0 (tracked) | 3.1 | 2.0 | 2.2 | Jet burial tool | 1.5 m
2 m optional | Hydraulic Thrusters &/or tracks | 2500 | 200 HP | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| SMD Nereus 3 ROV | 8.3 (free fly) 9.5 (tracked) | 3.8 | 3.2 | 2.5 | Jet burial tool | 2 m | Hydraulic Thrusters &/or tracks | 2500 | 300 kW | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| SMD Nereus 4 ROV | 8.3 (free fly) 9.5 (tracked) | 3.8 | 3.2 | 2.5 | Jet burial tool | 2 m | Hydraulic Thrusters &/or tracks | 2500 | 300 kW | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | + +**Table I.2 – Examples of submersible equipment** + +| Type of submersible equipment | Weight (tons) | Overall length (m) | Width (m) | Height (m) | Trenching system | Trenching | Propulsion | Max operating depth (m) | Max pulling tension (tons) | Capability | +|-----------------------------------------------------|-----------------------------------|--------------------|----------------------------|------------|---------------------------------|------------------------------------------------|------------------------------|-------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| UNITED ARAB EMIRATES | | | | | | | | | | | +| Submersibles belonging to E-marine PJSC | | | | | | | | | | | +| SMD Plough | 15
12 (Submerged) | 9
9.8 (Max) | 4.6 | 4.5 | Plough share | 1.5 m | Towrope from surface vessel | 2000 | 50 | Cables from 17 mm to 150 mm diameter. Repeaters up to 380 mm diameter. | +| Olympian T2 ROV | 10.1 (Skid)
10.9 (With tracks) | 5.2 | 2.3 (Skid)
3.8 (Track) | 2.9 | Jet burial tool config. | 1 m cohesive seabed
2 m non-cohesive seabed | Hydraulic thrusters/tracks | 3000 | 1 | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| SMD ROV | 8 (Skid)
9.2 (With track) | 3.8 | 3.2 (Skid)
3.7 (Tracks) | 2.7 | Jet burial tool config. | 0-1 m | Hydraulic thrusters/tracks | 2000 | 1 | Cable burial and deburial. Inspect cables, seabed and underwater objects. 7-function 2-manipulation cutting and grip. | +| Navajo ROV | 0.042 | 1.052 | 0.628 | 0.411 | NA | NA | DC brushless thrusters | 300 | Power supply
115 VAC/26 A
230 VAC/13 A | High quality video & sonar surveys. Capable of carrying buoyant work skids and manipulators. | +| REPUBLIC OF KOREA | | | | | | | | | | | +| Submersibles belonging to LS Marine Solutino | | | | | | | | | | | +| T800 ROV | 19 | 5.3 | 4.2 | 3.0 | Water jetting | 3.0 m | Hydraulic Thrusters | 2500 | – | Cable burial, Inspection, Manipulator | +| QT1500 ROV Plough | 26 | 5.5 | 5.5 | 3.4 | Water jetting | 3.0 m | Hydraulic Thrusters & Tracks | 1000 | – | Cable burial, Inspection, Manipulator | +| BurialMD3XT Plough | 27.5 | 9.5 | 5.1 | 5.5 | Plough share with water jetting | –3.3 m | Towed by ship | 1500 | – | Simultaneous lay and burial of cable | + +## Bibliography + +- [b-ITU-T G.975] Recommendation ITU-T G.975 (2000), *Forward error correction for submarine systems*. +- [b-ITU-T G.975.1] Recommendation ITU-T G.975.1 (2004), *Forward error correction for high bit-rate DWDM submarine systems*, including Cor.1 (2006) and Cor.2 (2013). +- [b-ITU-T G.976] Recommendation ITU-T G.976 (2014), *Test methods applicable to optical fibre submarine cable systems*. +- [b-ITU-T G.978] Recommendation ITU-T G.978 (2010), *Characteristics of optical fibre submarine cables*. +- [b-ITU-T G.979] Recommendation ITU-T G.979 (2016), *Characteristics of monitoring systems for optical submarine cable systems*. +- [b-ITU-T G Suppl.41] ITU-T G-series Recommendations – Supplement 41 (2024), *Design guidelines for optical fibre 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.972-202408-I_PDF-E/raw.md b/marked/G/T-REC-G.972-202408-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b8c43746fe9c254e0449789f269332221fb6b77b --- /dev/null +++ b/marked/G/T-REC-G.972-202408-I_PDF-E/raw.md @@ -0,0 +1,1047 @@ + + +# Recommendation**ITU-T G.972 (08/2024)** + +SERIES G: Transmission systems and media, digital systems and networks + +Digital sections and digital line system – Optical fibre submarine cable systems + +--- + +## **Definition of terms relevant to optical fibre submarine cable systems** + +![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 white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font overlaid on the globe. + +ITU logo + +## ITU-T G-SERIES RECOMMENDATIONS **Transmission systems and media, digital systems and networks** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100-G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200-G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300-G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400-G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450-G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600-G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700-G.799 | +| DIGITAL NETWORKS | G.800-G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 | +| 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.972 + +## Definition of terms relevant to optical fibre submarine cable systems + +## Summary + +Recommendation ITU-T G.972 applies to optical fibre submarine cable systems. The purpose of this Recommendation is to provide definitions of terms relevant to optical fibre submarine cable systems, including terms relevant to system configuration, system aspects, terminal equipment, optical submarine repeaters and branching units, optical fibre submarine cable, manufacturing and installation, and the maintenance of the submarine portion. Appendix I is the alphabetical list of terms defined in this Recommendation. + +In this latest version, terms and definitions introduced by new Recommendations ITU-T G.9730.1 and ITU-T G.9730.2 are added. All the terms that the definitions that were for further study have been added as well. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.972 | 1993-03-12 | 15 | 11.1002/1000/1037 | +| 2.0 | ITU-T G.972 | 1997-04-08 | 15 | 11.1002/1000/4027 | +| 3.0 | ITU-T G.972 | 2000-10-06 | 15 | 11.1002/1000/5187 | +| 4.0 | ITU-T G.972 | 2004-06-13 | 15 | 11.1002/1000/7340 | +| 5.0 | ITU-T G.972 | 2008-03-29 | 15 | 11.1002/1000/9378 | +| 6.0 | ITU-T G.972 | 2011-09-06 | 15 | 11.1002/1000/11123 | +| 7.0 | ITU-T G.972 | 2016-11-13 | 15 | 11.1002/1000/13116 | +| 8.0 | ITU-T G.972 | 2020-10-29 | 15 | 11.1002/1000/14502 | +| 9.0 | ITU-T G.972 | 2024-08-29 | 15 | 11.1002/1000/16064 | + +## Keywords + +Definition of terms, optical fibre submarine cable systems. + +--- + +\* 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 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 relevant to elements of system configuration..... | 2 | +| 3.2 Terms relevant to system aspects ..... | 7 | +| 3.3 Terms relevant to terminal equipment..... | 11 | +| 3.4 Terms relevant to optical submarine repeaters and branching units ..... | 12 | +| 3.5 Terms relevant to optical fibre submarine cable ..... | 13 | +| 3.6 Terms relevant to manufacturing and installation..... | 14 | +| 3.7 Terms relevant to the maintenance of the submarine portion ..... | 15 | +| 4 Abbreviations and acronyms ..... | 16 | +| 5 Conventions ..... | 18 | +| Appendix I – Alphabetical list of terms defined in this Recommendation..... | 19 | +| Bibliography..... | 26 | + + + +# Recommendation ITU-T G.972 + +## Definition of terms relevant to optical fibre submarine cable systems + +# 1 Scope + +The purpose of this Recommendation is to provide definitions of terms relevant to optical fibre submarine cable systems. + +A small number of terms defined in this Recommendation are associated with definitions in [ITU-T G.601], [ITU-T G.602] and [ITU-T G.701]. References to these definitions are given in parenthesis as an aid to ensure consistency between the different Recommendations in the event of future amendments. + +Figure 1 of [ITU-T G.971] shows the basic concept of optical fibre submarine cable systems and boundaries. Optical submarine repeaters or optical submarine branching units could be included, depending on each system requirement. + +In Figure 1 of [ITU-T G.971], A denotes the system interfaces at the terminal station (where the system can be interfaced to terrestrial digital links or to other submarine cable systems) and B denotes beach joints or landing points. Letters in brackets in the definitions of this Recommendation refer to the above figure. + +# 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.601] Recommendation ITU-T G.601 (1988), *Terminology for cables*. +- [ITU-T G.602] Recommendation ITU-T G.602 (1988), *Reliability and availability of analogue cable transmission systems and associated equipments*. +- [ITU-T G.652] Recommendation ITU-T G.652 (2024), *Characteristics of a single-mode optical fibre and cable*. +- [ITU-T G.653] Recommendation ITU-T G.653 (2010), *Characteristics of a dispersion-shifted, single-mode optical fibre and cable*. +- [ITU-T G.654] Recommendation ITU-T G.654 (2024), *Characteristics of a cut-off shifted, single-mode optical fibre and cable*. +- [ITU-T G.655] Recommendation ITU-T G.655 (2009), *Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable*. +- [ITU-T G.656] Recommendation ITU-T G.656 (2010), *Characteristics of a fibre and cable with non-zero dispersion for wideband optical transport*. +- [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*. +- [ITU-T G.701] Recommendation ITU-T G.701 (1993), *Vocabulary of digital transmission and multiplexing, and pulse code modulation (PCM) terms*. + +- [ITU-T G.870] Recommendation ITU-T G.870/Y.1352 (2016), *Terms and definitions for optical transport networks*. +- [ITU-T G.872] Recommendation ITU-T G.872 (2019), *Architecture of optical transport networks*. +- [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.971] Recommendation ITU-T G.971 (2024), *General features of optical fibre submarine cable systems*. +- [ITU-T G.976] Recommendation ITU-T G.976 (2014), *Test methods applicable 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 DWDM applications for repeated optical fibre submarine cable systems*. +- [ITU-T G.979] Recommendation ITU-T G.979 (2016), *Characteristics of monitoring systems for optical submarine cable systems*. +- [ITU-T G.9730.1] Recommendation ITU-T G.9730.1 (2024), *Dedicated scientific sensing submarine cable system*. +- [ITU-T G.9730.2] Recommendation ITU-T G.9730.2 (2024), *Scientific monitoring and reliable telecommunication submarine cable systems*. + +# 3 Definitions + +This Recommendation defines the following terms: + +## 3.1 Terms relevant to elements of system configuration + +**1001 optical fibre submarine cable system:** A set of equipment designed to permit the interconnection of two or more terminal stations. + +The optical fibre submarine cable system is usually composed of terminal equipment (terminal transmission equipment, power feeding equipment, maintenance controller, etc.), and submersible equipment (cable, repeater(s), branching unit(s), etc.). + +**1002 optical fibre submarine cable link:** A link which interconnects two terminal stations using a single optical fibre submarine cable system or an integrated system using system portions supplied by different suppliers. + +**1003 optical fibre submarine cable network:** A network which interconnects three or more terminal stations using a single optical fibre submarine cable system or an integrated system made of system portions supplied by different suppliers. + +**1004 land portion:** The portion between the system interface in the terminal station (A), and the beach joint or landing point (B) when it exists. It includes the optical fibre land cable, land repeaters, land joints and the system terminal equipment. + +**1005 submarine portion:** The portion of the system laying on the seabed, between the beach joints or landing points (B), which includes the optical fibre submarine cable and the submarine equipment (e.g., optical submarine repeater(s), optical submarine branching unit(s) and optical submarine cable jointing box(es)). + +**1006 beach joint:** The cable joint made between the optical fibre submarine cable and the optical fibre land cable. + +**1007 terminal station:** The telecommunication station usually located in the vicinity of the landing point and housing the optical fibre submarine cable system terminal equipment and that of associated terrestrial systems. + +**1008 terminal station equipment (TSE):** The TSE comprises the system terminal equipment (STE) and the ancillary equipment used for the operation of the optical fibre submarine cable system. + +**1009 system terminal equipment (STE):** The STE comprises all equipments specific to a given optical fibre submarine cable system. + +**1010 terminal transmission equipment (TTE):** The equipment terminating the optical submarine transmission line at the optical interface and connected to the system interface. The TTE may have multiple signal sources with channel multiplexer/demultiplexer. For interoperable submarine cable systems, TTE is treated as the terminal portion, and terminates the interoperable cable section. + +**1011 supervisory system:** The whole of equipment and sub-assemblies commonly providing one or more of the following functions: + +- monitoring the performance of the submarine equipment and sub-assemblies; +- monitoring the performance of the system terminal equipment; +- monitoring the end-to-end performance of the digital line sections; +- enabling fault location inside the submarine plant, to within one repeater section, where possible; +- controlling redundancy switching, if provided inside the submarine portion; +- providing interfaces to other management facilities. + +**1012 maintenance controller:** A computer with an interface to the supervision and remote maintenance equipment, which is commonly used during the supervision and remote maintenance activity for the equipment in the submarine portion. It is also used for terminal transmission equipment (TTE) maintenance purposes. + +**1013 power feeding equipment (PFE):** The equipment providing, through a power conductor in the optical fibre submarine cable, a stabilized constant electrical current for powering optical submarine repeaters and/or optical submarine branching units. + +**1014 cable terminating equipment (CTE):** The equipment providing the interface between the optical fibre from the terminal transmission equipment (TTE) and the optical fibre cable, and the interface between the power feeding line from the power feeding equipment (PFE) and the power feeding conductor from the optical fibre cable. + +NOTE – The CTE is usually part of the PFE. + +**1015 power feed earth:** The earth provided to establish the return path of the repeater power feeding current circuit. + +**1016 power feed earth electrode cable:** The cable installed between the power feed earth and the power feeding equipment (PFE). + +**1017 optical fibre station cable:** The optical fibre cable installed inside the cable station. + +**1018 optical fibre land cable:** The optical fibre cable installed between the cable terminating equipment (CTE) and the beach joint. + +**1019 optical fibre submarine cable:** The submarine cable using optical fibres as transmission line. + +**1020 optical submarine repeater:** (Related to definition 1001 provided in [ITU-T G.601]) An equipment essentially including one or more regenerators or amplifiers and associated devices, in the submarine portion. + +**1021 bipolar repeater:** An optical submarine repeater which can be powered by a power feeding current flowing in either direction. + +**1022 branching unit (BU):** An equipment connecting more than two optical fibre submarine cable sections. + +NOTE – Applications for the optical submarine branching may include the following additional functions: + +- optical signal path switching; +- signal regeneration or amplification; +- power path switching. + +**1023 undersea branching multiplexer (UBM):** A branching unit that separates lower level digital signals from incoming optical line signals and recombines them differently in outgoing optical line signals. + +**1024 integration specification:** A set of specifications established to permit the interconnection of two or more optical fibre submarine cable systems designed by different suppliers. + +**1025 integration line optical interface:** The optical interface between fractions of the submarine cable sections provided by different suppliers. + +**1026 shallow water:** Water depths down to a given limit, corresponding to the depths of fishing activity, or more generally of marine activity, creating a risk of cable fault. + +NOTE – The limit of shallow water is of the order of 1000 metres. + +**1027 deep water:** Water depths exceeding the limit of shallow water. + +**1028 elementary cable section:** The whole length of optical fibre cable between two pieces of equipment (repeaters, branching units or terminal transmission equipment). + +**1029 repeated submarine cable:** An electrically powered underwater optical fibre cable, designed for repeated applications, and suitable for shallow and deep water use, which has been extensively tested to show it can be installed and repaired *in situ*, even in the worst weather conditions, without any impairment of optical, electrical or mechanical performance or reliability. + +NOTE – For appropriate test methods, please refer to [ITU-T G.976]. + +**1030 repeaterless submarine cable:** An underwater optical fibre cable, designed for unrepeated applications, and suitable for shallow and deep water use, which has been extensively tested to show it can be installed and repaired *in situ*, even in the worst weather conditions, without any impairment of optical, electrical or mechanical performance or reliability. + +NOTE 1 – For appropriate test methods, please refer to [ITU-T G.976]. + +NOTE 2 – The term "repeaterless" is also known as "unrepeated" or "non-repeated". + +**1031 marinized terrestrial cable (MTC):** An underwater optical fibre cable construction based on a conventional multi-fibre terrestrial cable core protected to withstand the marine environment, designed for unrepeated applications and tested for use in non-aggressive shallow waters with varying repair capability. + +NOTE 1 – Sometimes known in Europe as an "underwater" cable. + +NOTE 2 – Appropriate test methods are under study. + +**1032 single wavelength system (SWS):** A bidirectional optical system that carries on only one line optical channel (LOC). + +**1033 wavelength division multiplexing (WDM):** An aggregate of several line optical channels (LOCs) to be carried through part or the whole of the submarine line on the same line fibre. + +**1034 wavelength division multiplexing system (WDMS):** A bidirectional optical system that carries on several line optical channels (LOCs). + +- 1035 dense wavelength division multiplexing (DWDM):** An aggregate of a large number of line optical channels (LOCs) to be carried through part or the whole of the submarine line on the same line fibre. +- 1036 dense wavelength division multiplexing system (DWDMs):** A bidirectional optical system that carries on a large number of line optical channels (LOCs). +- 1037 gain equalizer:** Gain equalizer is the means used to adapt the submerged plant gain profile characteristics suitable for transmission. +- 1038 tilt equalizer:** Tilt equalizer is the means for wavelength division multiplexing system (WDMS) to provide the equalization of the residual gain/wavelength tilt which accumulates when the signal is transmitted through a chain of submerged repeaters. +- 1039 slope equalizer:** Slope equalizer is the means for wavelength division multiplexing system (WDMS) to provide the equalization of the residual gain/wavelength slope which accumulates when the signal is transmitted through a chain of submerged repeaters. +- 1040 shunt fault:** A shunt fault is a current leakage path between the power conductor and the sea water without a break in the power conductor. +- 1041 remote optically pumped amplifier (ROPA):** An optical fibre amplifier (OFA) consisting of a section of erbium doped fibre that is activated by a pump beam sent from the terminal station. +- 1042 distributed Raman amplifier (DRA):** An optical fibre amplifier (OFA) using the transmission fibre as an amplifier medium that is pumped from the terminal station. The gain is obtained all along the fibre (therefore distributed) using the Raman properties of the fibre until sufficient pump power is available. +- 1043 Raman gain coefficient:** The Raman gain coefficient quantifies the change in the intensity of the Raman-scattered light per unit length and per unit pump power within the fibre. +- 1044 elementary cable:** A series of elementary cable sections. +- 1045 single-fibre type elementary cable:** Elementary cable consisting of a single type of optical fibre. +- 1046 hybrid-fibre type elementary cable:** Elementary cable consisting of more than one type of optical fibre. +- 1047 cut-off shifted single-mode fibre (CSF):** Loss-minimized and cut-off shifted single-mode optical fibre, specified in [ITU-T G.654]. +- 1048 dispersion compensating single-mode fibre (DCF):** Single-mode optical fibre with large negative chromatic dispersion value. +- 1049 dispersion shifted single-mode fibre (DSF):** Zero-dispersion wavelength shifted single-mode optical fibre, specified in [ITU-T G.653]. +- 1050 large effective area single-mode fibre (LEF):** Single-mode optical fibre with enlarged effective area. +- 1051 negative dispersion single-mode fibre (NDF):** Single-mode optical fibre with negative chromatic dispersion value in the signal wavelength region. +- 1052 non-zero dispersion shifted single-mode fibre (NZDSF):** Zero-dispersion wavelength shifted single-mode optical fibre, but it has some non-zero chromatic dispersion value in the wavelength region of 1530 to 1565 nm, specified in [ITU-T G.655]. +- 1053 positive dispersion single-mode fibre (PDF):** Single-mode optical fibre with positive chromatic dispersion value in the signal wavelength region. + +**1054 non-dispersion shifted single-mode fibre (SMF):** Single-mode optical fibre, which has a zero-dispersion wavelength in the 1310 nm wavelength region, specified in [ITU-T G.652]. + +**1055 wideband non-zero dispersion single-mode fibre (WNZDF):** Single-mode optical fibre, which has some non-zero chromatic dispersion value in the wavelength region of 1460 to 1625 nm, specified in [ITU-T G.656]. + +**1056 optical transport network (OTN):** Optical network, which is composed of a set of optical network elements connected by optical fibre links, able to provide functionality of transport, multiplexing, routing, management, supervision and survivability of optical channels carrying client signals, according to the requirements given in [ITU-T G.872] (see [ITU-T G.870]). + +**1057 optical transport hierarchy (OTH):** A hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over optical transmission networks (see [ITU-T G.870]). + +**1058 optical submarine equalizer (OSE):** Submerged equipment used to compensate for, or to handle, the accumulative gain ripple and tilt along a submarine digital line section (SDLS) in order to be compliant with the pre-emphasis capability of the terminal transmission equipment (TTE) at the transmitter side, and with the corresponding impairment allocated in the power budget table. + +**1059 longitudinal compatibility:** The arrangement where both ends of an optical section are terminated by equipment from the same manufacturer (see [b-ITU-T G.Sup.39]). + +**1060 transverse compatibility:** The capability to mix various manufacturers' equipments within a single optical section (see [ITU-T G.957]). + +**1061 electrical command response (ECR):** The equipment providing communication functions with the equipment in the submarine portion such as repeaters and branching units to control them and receive the monitoring data from the equipment. + +**1062 optical coupling junction (OCJ):** The equipment connecting the monitoring related equipment and providing functions to forward the monitoring signals to the submarine cable section together with the signals from the terminal transmission equipment (TTE). It can be either a passive or active coupling device and may include a bandwidth multiplexer/demultiplexer and/or amplifier to accommodate the wave division multiplexing (WDM) signals from multiple TTEs. + +**1063 terminal portion:** The portion between the system interface in the terminal station (A, refers to Figure 1 in [ITU-T G.971]), and the interoperable system interface for an interoperable submarine cable system (C, refers to Figure 1 in [ITU-T G.971]), which is a joint point between the terminal transmission equipment (TTE) and the optical coupling junction (OCJ). It includes TTE and MC for TTE. + +**1064 interoperable cable portion:** The portion of the system between the joint points (C), which includes optical coupling junctions (OCJs), other maintenance related equipment (MC, ME, ECR or PFE), the optical fibre submarine cable and the submarine equipment (e.g., optical submarine repeater(s), optical submarine branching unit(s) and optical submarine cable jointing box(es)). It may include the land repeaters and optical fibre land cable when the system has a repeated land cable section. + +**1065 land repeater:** (Related to definition 1001 provided in [ITU-T G.601]) An equipment essentially including one or more amplifiers and associated devices, in the land portion. + +**1066 underwater junction box (UJB):** It includes equipment for scientific monitoring data collection and transmission, power supply and voltage transition, fault isolation, interfaces. + +**1067 primary underwater junction box (P-UJB):** Underwater junction box (UJB) that is connected directly or via a branching unit (BU) to the trunk cable. + +**1068 secondary underwater junction box (S-UJB):** Underwater junction box ((UJB) that is connected to a primary underwater junction box (P-UJB) and is used for the extension of the set of sensors. + +**1069 sensor:** An element of the system that measures a physical property of the environment and returns an observed value. + +**1070 set of sensors:** Different kinds of sensors grouped together for submarine scientific sensing. + +**1071 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). + +**1072 sensor data processing and storage (SDPS):** A device used to process and store the data generated by sensors in the submarine portion. + +**1073 wet-pluggable connector:** Connector that is used for the wet-pluggable interface. + +**1074 telecommunication functions:** Functions and aspects of the optical submarine cable transmission system that are not related to sensing. + +**1075 land station:** Station that could be located in terrestrial stations or offshore platforms. + +## **3.2 Terms relevant to system aspects** + +**2001 system design life:** The period of time over which the optical fibre submarine cable system is designed to operate in conformance with its performance specification. + +**2002 optical power budget:** The allocation of the available optical power in an optical section. + +**2003 digital line section:** (Related to definitions 3007 and 3012 provided in [ITU-T G.701]) The whole of the means of transmission of a digital signal at a specified bit rate between the corresponding input and output system interfaces at the digital distribution frame or equivalent. A digital line section forms a part of a digital link and includes terminal equipment, repeaters and branching units. The definition normally applies to the combination of "go" and "return" directions of transmission. + +NOTE – This definition differs from the definition in [ITU-T G.701] as the latter excludes multiplexers. In an optical fibre submarine cable system, a digital line section is meant to include optical submarine branching multiplexers, if any, and also terminal multiplexing equipment included in the terminal transmission equipment (TTE) which may include multiplexing. + +**2004 optical section:** The whole of the optical path as a physical transmission medium between the optical source output (point O) of one equipment and the optical detector input (point I) of the following equipment. + +**2005 optical source output:** The point where the launched power is measured (point O). + +**2006 optical detector input:** The point where the received optical power is measured (point I). + +**2007 supervisory section:** The fraction of the submarine portion extending from one specified point in a repeater to a similar point in the adjacent repeater which can be identified using the supervisory system for fault location. + +**2008 system interface:** (Related to definition 1008 provided in [ITU-T G.701]) The point (A) on the specified equipment, such as the digital distribution frame, at which each digital line section terminates. The interfaces are usually designated as $I_i$ , pertaining to the incoming tributaries, and $I_o$ , pertaining to the outgoing tributaries. + +**2009 optical interface:** (Related to definition 1008 provided in [ITU-T G.701]) A common boundary between two associated parts of an optical section. + +**2010 transmit terminal optical interface:** The optical interface at the output port (point S) of a transmit terminal equipment. + +- 2011** **receive terminal optical interface:** The optical interface at the input port (point R) of a receive terminal equipment. +- 2012** **repeater (or BU) optical output interface:** The optical interface at the output port (point S) of a repeater (or BU). +NOTE – The output port is usually at the splice between the repeater fibre and the cable fibre. +- 2013** **repeater (or BU) optical input interface:** The optical interface at the input port (point R) of a repeater (or BU). +NOTE – The input port is usually at the splice between the repeater fibre and the cable fibre. +- 2014** **optical line signal:** The optical signal transmitted on one optical fibre in the submarine portion. +- 2015** **line frame:** (Related to definition 4007 provided in [ITU-T G.701]) A cyclic set of consecutive time slots in the optical line signal in which the relative position of each time slot can be identified. +NOTE – The line frame results from the multiplexing and coding operations performed by the terminal transmission equipment (TTE), taking into account the inclusion of the service and supervisory channels. +- 2016** **system interface bit rate:** (Related to definition 2013 provided in [ITU-T G.701]) The number of bits (binary digits) per unit time in the digital signal at the system interface. +NOTE – Several interface bit rates may coexist for one single optical fibre submarine cable system. +- 2017** **line error ratio:** The error ratio as could be observed using appropriate means at a given location in the submarine portion. +- 2018** **apparent line error ratio:** The value of the line error ratio obtained using the supervisory equipment of the submarine optical fibre cable system. +- 2019** **electroding:** The use of undersea equipment for the detection of a low frequency modulation of the power feeding current for cable location purposes. +- 2020** **power feeding current:** The stabilized electric current provided by the PFE through the cable power conductor with return through the power feed earth. +- 2021** **line bit rate:** (Related to definition 2014 provided in [ITU-T G.701]) The number of signal elements of the optical line signal per unit time. +NOTE – The line bit rate results from the multiplexing and coding operations performed by the terminal transmission equipment (TTE), taking into account the inclusion of the service and supervisory channel. +- 2022** **line code:** (Related to definition 9002 provided in [ITU-T G.701]) A code chosen to suit the characteristics of the submarine portion that defines the equivalence between sets of digits presented for transmission and the corresponding sequence of signal elements transmitted over that channel. +NOTE – The line code and violations of the line code can be used for system monitoring and supervisory. +- 2023** **system performance penalty:** A parameter included in the optical power budget to take into account phenomena such as chromatic dispersion, partition noise, etc. +- 2024** **cable section margin:** A parameter included in the optical power budget, to take into account the variation of the fibre attenuation due to ageing during the system design life. +- 2025** **equipment margin:** A parameter included in the optical power budget to take into account the variation of the optical power at both ends of a cable section due to equipment component ageing during the system design life. +- 2026** **repair allowance:** A parameter included in the optical power budget to take into account the possible increase of attenuation of the cable fibre due to cable repair during the system design life. + +- 2027 unassigned margin:** A parameter included in the power budget as a provision for unforeseen phenomena. +- 2028 guaranteed margin:** The minimum margin in the power budget. +- 2029 overload margin:** The minimum difference between the received power and the input power above which the bit error ratio would exceed a specified level. +- 2030 expected ship repair number:** The mean number of repairs by cableshop (statistical expectation) due to system failures during the system design life. +NOTE – This excludes faults due to external aggression. +- 2031 reliability budget:** A reliability model indicating the reliability of each of the components of the submarine portion to be met so as to keep the expected ship repair number below a given limit. +- 2032 availability:** (See the definitions provided in [ITU-T G.602]) The ability of the system to be in a state to perform adequately at a given instant of time within a given time interval. The availability of an optical fibre submarine cable system is quantified by the ratio of the time during which the system is operating to a specified total time. +NOTE – System interruptions due to faults requiring ship repair are excluded for availability calculation. +- 2033 end-to-end performance monitoring:** The evaluation of the end-to-end transmission quality performance of each digital line section in the submarine optical fibre cable transmission system. +- 2034 supervisory of an optical fibre submarine cable system:** The function provided by the supervisory system of the optical fibre submarine cable system so as to permit fault localization, repeater performance monitoring and remote-controlled redundancy switching. +- 2035 forward error correction (FEC):** A technique which consists of transmitting the data in an encoded form such that the redundancy added by the coding allows the decoding to detect and correct errors. +- 2036 FEC frame:** In frame-structured coding algorithms, the cyclic set of consecutive time slots delivered by the FEC encoder which, at a minimum, contains a frame alignment word, the data at system interface (A) and the redundant information computed with the FEC algorithm. +- 2037 Q factor:** A measurement of the quality of the received signal (see [ITU-T G.976]). +- 2038 line optical channel (LOC):** A bidirectional optical data channel carried on a specific optical frequency/wavelength for each transmission direction. +- 2039 submarine cable optical interface (SCOI):** The bidirectional optical interface between the submarine cable including the terrestrial cable section and the terminal transmission equipment (TTE). +- 2040 LOC-TTE:** A terminal transmission equipment (TTE) whose submarine cable optical interface (SCOI) is composed of only one line optical channel (LOC). +- 2041 WDM-TTE:** A TTE equipped with WM and WD, whose submarine cable optical interface (SCOI) is a WDM. +- 2042 submarine electro-optic interface (SEOI):** The bidirectional interface inside the TTE where an electro-optic conversion and an electrical generation are performed between a line optical channel (LOC) and an electrical channel. +- 2043 submarine digital line section (SDLS):** A bidirectional continuous optical path along which one line optical channel (LOC) links two terminal transmission equipments (TTEs) at the SEOI level. +- 2044 terrestrial interface (TI):** The interface between the submarine system and the terrestrial network. + +**2045 intermediate terrestrial interface (ITI):** It is to be noted that the terminal transmission equipment (TTE) can be composed of two distinct pieces of equipment interfaced together, the first piece, called submarine cable transmission terminal equipment (SCTTE), facing with submarine cable, and the second piece, called terrestrial network transmission terminal equipment (TNTTE), facing the terrestrial network. In this case, an intermediate interface is required, which links the two pieces of equipment. This interface is composed of bidirectional data interfaces and, where applicable, an extra link used to exchange information between the two pieces of TTE equipment. + +**2046 dispersion map:** A graphical representation of how chromatic dispersion varies with wavelength as a function of transmission distance. + +**2047 polarization hole burning:** Polarization hole burning (PHB) results from an anisotropic saturation created by a strongly polarized signal launched into the erbium fibre. This results in a selective depopulation of excited states aligned with the polarized field. Consequently, the available gain in the orthogonal direction is higher. + +**2048 Q-time variations margin (or time varying system penalty (TVSP)):** A margin that defines an impairment due to performance fluctuations around the mean performance. Five standard deviations of Q factor should be allocated. + +**2049 generalized optical signal to noise ratio (GOSNR):** Optical signal to noise ratio including the total noise contributions due to linear noise and fibre nonlinearities, while referenced in the noise bandwidth typically of 12.5 GHz or 0.1 nm at wavelength of 1550 nm. + +**2050 generalized signal to noise ratio (GSNR):** Signal to noise ratio including the total noise contributions due to linear noise and fibre nonlinearities, while referenced in the same signal and noise bandwidth. + +**2051 signal to noise ratio (SNR):** Power ratio between signal and noise components. + +**2052 interoperable cable portion interface:** The interface before and after the optical coupling junction (OCJ) in an interoperable cable system. + +**2053 guided acousto-optic wave Brillouin scattering (GAWBS):** An acousto-optic effect whereby light propagating along an optical fibre can be scattered in the forward direction by interacting with thermally excited transverse acoustic modes of the fibre. The locally induced phase and polarization modulations translate into a crosstalk noise, the variance of which is proportional to distance and signal power. + +**2054 guided acousto-optic wave Brillouin scattering signal-to-noise ratio (SNRGAWBS):** The guided acousto-optic wave Brillouin scattering signal-to-noise ratio (SNRGAWBS) is the contribution from the acoustic modes of the transmission fibre scattering light in the forward direction with a frequency shift that is determined by the acoustic mode oscillation frequency. + +**2055 generalized droop:** The generalized droop model aims to account for the aggregation of multiple sources of Gaussian noise (or signal distortions modelled as a Gaussian noise) under the constraint of fixed total power. + +**2056 optical signal-to-noise ratio (OSNR):** The ratio of the signal power in the wanted channel to the highest noise power density (referred to 0.1 nm) within the channel frequency range. + +**2057 wet-pluggable interface:** An interface that can be connected and disconnected underwater to an underwater junction box (UJB). + +**2058 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. + +**2059 scientific subsystem:** Monitoring subsystem using sensors or sensor sets with their dedicated power supply and data transmission components. + +## 3.3 Terms relevant to terminal equipment + +**3001 service channel:** A communication channel established between associated terminal stations through the optical fibre submarine cable system for the purpose of operating and maintaining the system. + +**3002 order wire channel:** A voice service channel. + +**3003 PFE earth protection equipment:** A protective device that automatically routes the power-feeding current to the station earth under abnormal power feeding equipment (PFE) earth conditions. + +**3004 PFE personnel protection equipment:** Protective equipment installed to prevent personnel from gaining access to dangerous potentials. + +**3005 PFE mutual protection:** The ability of a power feeding unit installed at one end of a link to provide in an emergency situation the whole of the power necessary for a given link, when in normal operating condition that total power is shared between the power feeding equipment installed at both ends of the link. + +**3006 PFE nominal current:** The nominal value of the power feeding current. + +**3007 maximum PFE current:** The value of the power feeding current above which the power feeding equipment (PFE) switches off in order to protect the system. + +**3008 maximum PFE voltage:** The value of the voltage at the power feeding equipment (PFE) output above which the PFE switches off in order to protect the system. + +**3009 PFE current stability:** The limitation of the variation of the power feeding equipment (PFE) current in time. + +**3010 FEC encoder:** A unit included in the transmit terminal transmission equipment (TTE) which accomplishes all the digital operations needed to translate the digital data at system interface (A) into the desired coded bit sequence according to the employed forward error correction (FEC) algorithm. + +**3011 FEC decoder:** A unit included in the receive terminal transmission equipment (TTE) which accomplishes the correction of the data transmitted through the submarine portion into symbol decisions that reproduce, as accurately as possible, the data that was encoded by the forward error correction (FEC) encoder. + +**3012 wavelength multiplexer (WM):** The equipment required to combine several line optical channels (LOCs) and/or WDM coming from different fibres into a common WDM composed of all the combined LOCs. + +**3013 wavelength demultiplexer (WD):** The equipment required to split a WDM into several LOCs and/or WDM to be carried on different fibres. + +**3014 submarine cable transmission terminal equipment (SCTTE):** Terminal transmission equipment (TTE) for a submarine cable transmission system. + +**3015 terrestrial network transmission terminal equipment (TNTTE):** Terminal transmission equipment (TTE) for a terrestrial network optical transmission system. + +**3016 umbilical:** The extra link used at an intermediate terrestrial interface (ITI) to exchange information between the two pieces of terminal transmission equipment (TTE) which are the submarine cable transmission terminal equipment (SCTTE) and the terrestrial network transmission terminal equipment (TNTTE). + +**3017 outer code:** The forward error correction (FEC) code used for the first FEC encoding/decoding of an FEC scheme using two concatenated FEC codes. + +**3018 inner code:** The forward error correction (FEC) code used for the second FEC encoding/decoding of an FEC scheme using two concatenated FEC codes. + +**3019 hard decision decoding:** Hard decision decoding refers to the use of a single quantization level in bit sampling, resulting in binary bit information provided to the decoding process. + +**3020 soft decision decoding:** For the same received waveform, soft decision decoders make use of multiple levels of quantization (typically three or more). + +**3021 coding gain:** Coding gain means the improvement of received optical sensitivity by forward error correction (FEC), without considering the penalty caused by the bit rate increasing. + +**3022 net coding gain:** Net coding gain means the improvement of received optical sensitivity by forward error correction (FEC), considering the penalty caused by the bit rate increasing. + +**3023 Q limit:** Q limit means the minimum required allowable Q factor of the input signal for the receiver decision circuit in order to achieve a reference BER. + +**3024 redundancy ratio:** Redundancy ratio describes the ratio between the number of information bits covered by the forward error correction (FEC) and the number of bits after encoding comprising the same information plus the added redundancy information. + +**3025 latency:** Latency means transmission delay for forward error correction (FEC) encoding, decoding, interleaving and de-interleaving. + +## **3.4 Terms relevant to optical submarine repeaters and branching units** + +**4001 repeater (or BU) housing:** The mechanical part of a repeater (or branching unit). + +**4002 repeater (or BU) optoelectronic unit:** The optoelectronic part of a repeater (or branching unit). + +**4003 repeater (or BU) supervisory circuit:** Electronic circuits installed in a repeater (or branching unit) to perform, in association with the supervisory equipment installed in the terminal station, system supervision and fault localization. + +**4004 repeater (or BU) power supply and protection circuit:** The electronic circuits installed in a repeater (or BU) to power, in association with the power feeding equipment (PFE), the repeater (or BU) electronic unit with a regulated voltage, and to provide a protection against electrical discharges due to cable discharge or lightning. + +**4005 branching unit sea electrode:** An electrode provided at a branching unit (BU) to establish the return path of the power feeding current through the sea. + +**4006 full fibre drop BU (FFD-BU):** A BU where the optical interconnection between the three submarine cables is made by physically connecting fibre pairs between any two cables. + +**4007 wavelength division multiplexing branching unit (WDM-BU):** A branching unit (BU) where the optical interconnection between the three submarine cables is made through WM and WD, which is adding and dropping one or more line optical channels (LOCs) out of the N-wavelength division multiplex (N-WDM). + +**4008 fixed optical add/drop multiplexing-branching unit (FOADM-BU):** A branching unit (BU) with OADM function where the added, dropped and passed-through wavelengths are fixed. + +**4009 reconfigurable optical add/drop multiplexing-branching unit (ROADM-BU):** A branching unit (BU) with OADM function where the added, dropped and passed-through wavelengths can be dynamically modified. + +## 3.5 Terms relevant to optical fibre submarine cable + +**5001 lightweight cable:** Cable suitable for laying, recovery and operation where no special protection is required. + +**5002 lightweight protected cable:** Lightweight cable with an additional protective layer. + +NOTE – This cable is suitable for laying, recovery and operation in areas where cable erosion or fish-bite risk is significant. + +**5003 single armoured cable:** A cable with a single layer of protective armour. + +NOTE – This cable is suitable for laying, burial, recovery and operation, and is suitably protected for specific areas in shallow water. + +**5004 double armoured cable:** A cable with a double layer of protective armour. + +NOTE – This cable is suitable for laying, burial, recovery and operation, and is suitably protected for specific areas in shallow water. + +**5005 rock armoured cable:** A cable with a multiple layer of protective armour (usually two), the outer layer being wound with a small pitch. + +NOTE – This cable is suitable for laying, recovery and operation, and is suitably protected for specific areas in shallow water. + +**5006 land cable:** Cable with suitable protection for installation in ducts or direct burying in the ground. + +**5007 cable breaking load (CBL):** The minimum guaranteed breaking strength of the cable, with ends fixed, taking into account material and dimensional tolerances of the cable components. + +**5008 fibre-breaking cable load:** The load which, when applied longitudinally to the cable with fixed ends, results in an instantaneous fibre break. + +**5009 nominal permanent tensile strength (NPTS):** The maximum permanent cable tension that does not significantly reduce the system performance, lifetime and reliability. NPTS represents the maximum residual tension that may be permanently applied to the cable on the seabed after installation. + +NOTE – NPTS is also known elsewhere as the maximum permanent cable load. + +**5010 nominal operating tensile strength (NOTS):** The maximum average operational tension which the cable can support for the period required for marine operations (typically 48 hours) without significantly reducing the system performance, lifetime and reliability. NOTS represents the maximum average operational tension during installation or repair. + +NOTE – NOTS is also known elsewhere as the operational cable load. + +**5011 nominal transient tensile strength (NTTS):** The maximum short-term tension that can be applied to the cable during an at-sea recovery operation over a cumulative period of approximately one hour without significantly reducing the system performance, lifetime and reliability. NTTS represents the maximum transient or unexpected tension that may be applied to the cable and is normally limited to a percentage of the cable breaking load (CBL) from a mechanical safety point of view. + +NOTE – NTTS is also known elsewhere as the transitory cable load. + +**5012 longitudinal water propagation:** The cable length being penetrated by water as a function of water depth or pressure and of duration of submission for an open-ended cable. + +**5013 cable jointing box:** A mechanical assembly used to join two optical fibre submarine cables. + +**5014 cable coupler (or cable termination):** A mechanical assembly used to join an optical fibre submarine cable to a repeater or a branching unit. + +- 5015 cable transition:** A transition between different types of cables, which can be achieved using either a transition cable or a transition joint. +- 5016 cable gyration:** The rotation of one end of a cable length relative to the other end. +- 5017 cable elongation with fixed end:** The cable elongation under a load, when both ends are prevented from rotating. +- 5018 cable elongation with free gyration:** The cable elongation under a load, when one end is free to rotate. +- 5019 cable modulus:** The length of cable, measured in km, the weight of which in water is equal to the cable breaking load. +- 5020 cable operational modulus:** The length of cable, measured in km, the weight of which in water is equal to the nominal operation tensile strength (NOTS). +- 5021 cable full safe modulus:** The length of cable, measured in km, the weight of which in water is equal to the nominal permanent tensile strength (NPTS). +- 5022 cable transitory modulus:** The length of cable, measured in km, the weight of which in water is equal to the nominal transient tensile strength (NTTS). +- 5023 cabled fibre attenuation:** The optical attenuation of the cable, including any fibre overlenth and fibre splices present, as measured in dB per length of cable. +- 5024 cabled fibre strain:** The strain in an optical fibre in a cable after manufacture. +- 5025 cable safety margin:** The cable safety margin is the difference in tensile load between the measured load at failure and the maximum installation/recovery load proposed by the installer. The cable safety margin may typically be expressed as a percentage of measured load at failure. +- 5026 duct shielded cable:** A cable with a circumferential safety shield which may be the fish-bite protection shield, and which is suitable to be pulled into ducts. +- 5027 tight cable structure:** A cable structure where the fibres are strongly maintained in the cable, so that the fibre elongation is essentially equal to that of the cable. +- 5028 loose cable structure:** A cable structure where the fibres are free to move inside the cable, so that the fibre elongation is lower than that of the cable, staying at zero until the cable elongation reaches a given value. +- 5029 transitory cable load:** The load that could be accidentally encountered, particularly during recovery operations. +- 5030 operational cable load:** The load that could be encountered during repairs. +- 5031 permanent cable load:** The load that characterizes the status of cable after lay. +- 5032 minimum cable bending radius:** The bending radius which is a guideline for cable handling. + +## **3.6 Terms relevant to manufacturing and installation** + +- 6001 qualification:** The activity, part of the development process, intended to demonstrate that a technology, a component or an assembly is able to comply with its performance and reliability specification. +- 6002 sea trial:** A test made at sea during the development process, as part of the qualification of the submarine portion. +- 6003 certification:** The activity, part of the manufacturing process, intended to eliminate all components or subassemblies which present a risk of not complying with their performance and reliability specification. + +**6004 batch qualification:** The activity, part of the manufacturing process, intended to eliminate batches of components suspected to present a generalized failure mechanism. + +**6005 route survey:** The activity performed prior to cable laying so as to select the cable route and cable protection (fish-bite protection, armour, burying). + +**6006 link assembly:** The activity of jointing the cable sections, repeaters and branching units, together with monitoring the performance of each cable section. + +**6007 ship loading:** The operation of installing the submarine portion, or fractions of it, on board the cable ship prior to laying. + +**6008 cable laying:** The operation of laying on the sea bottom the submarine portion or fractions of it. + +**6009 laying limit condition:** Weather and sea conditions above which laying should not be undertaken or should be interrupted. + +**6010 slack control:** Operation consisting of controlling that a predetermined cable overlength (slack) is laid. + +**6011 shore end:** The end of the submarine cable to be laid from the cableship toward the beach so as to be connected to the land cable. + +**6012 initial splice:** The splice made on board the cableship between parts of the submarine portion at the beginning of a lay. + +**6013 final splice:** The splice made on board the cableship between parts of the submarine portion at the end of a lay. + +**6014 cable burial:** The operation consisting of burying the cable in the seabed so as to provide better cable protection. + +NOTE – The burial operation may be carried out either during installation or as a post-lay activity. + +**6015 laying angle:** The angle between the cable being laid (which is theoretically along a straight line) and the sea surface. + +**6016 manufacturing inspection:** The activity during the manufacturing process intended to verify that the quality plan is respected, that each operation is accomplished along the agreed procedure, and that the result is satisfactory. + +**6017 commissioning testing:** A test prior to installing traffic on the system to ensure that the system meets its overall transmission performance contractual requirement, and that all functionalities with respect to network management are operating. + +## **3.7 Terms relevant to the maintenance of the submarine portion** + +**7001 cable recovery:** The operation of recovering a cable from the sea bottom. + +**7002 deep sea repair:** The operation of repairing a submarine cable system installed in deep sea. + +**7003 shallow water repair:** The operation of repairing a submarine cable system installed in shallow water. + +**7004 mini system:** A length of cable, pre-equipped with repeaters, to be used for replacing one or more optical cable sections and the associated repeaters during a sea repair. + +**7005 spare repeater (or BU):** An additional repeater (or BU) stored in a marine depot or on board a cableship to be used during a repair operation. + +**7006 spare cable:** An additional cable length, stored in a marine depot or on board a cableship to be used during a repair operation. + +**7007 spare storage condition:** The environment condition for storing the spare repeaters and cable. + +**7008 repair safety procedure:** Procedures to be applied on board the cableship and in the terminal station so as to ensure the safety of personnel during a repair. + +**7009 submersible robot:** A remote-controlled submersible vehicle which can be used for locating, observing, post-lay burying or recovering a cable installed in shallow water. + +**7010 routine maintenance:** The periodic monitoring of the system parameters and preventive redundancy switching performed from the terminal station using the supervisory system. + +**7011 fault localization:** The process of identifying and pinpointing the location of faults or issues within an optical communication system or network. + +**7012 fault location:** The precise determination of the location or position of a fault or anomaly within an optical communication system or network. + +**7013 optical time domain reflectometry (OTDR):** The optoelectronic instrument used to characterize the optical fibres. OTDR injects a series of optical pulses into the fibre under test. It also extracts, from the same end of the fibre, light that is scattered and reflected back from points in the fibre where the index of refraction changes. The strength of the return pulses is measured and integrated as a function of time, and is plotted as a function of fibre length. + +**7014 coherent optical time domain reflectometry (COTDR):** COTDR has similar features to OTDR, but uses coherent detection instead of direct detection, which gives it higher sensitivity and higher frequency selectivity than OTDR. + +**7015 monitoring equipment (ME):** Equipment used to monitor the status of the submerged plant of a submarine cable system, which is classified into two categories according to the monitoring mechanism: passive monitoring equipment, or active monitoring equipment. + +NOTE – For monitoring systems for optical fibre submarine cable systems, please refer to [ITU-T G.979]. + +**7016 active monitoring equipment (AME):** One of the two categories of MEs which monitors the status of submerged equipment by communicating with the monitored equipment to obtain a performance status. + +**7017 passive monitoring equipment (PME):** One of the two categories of MEs which does not communicate with the submerged plant, but monitors the status of the submerged plant by detecting optical/electrical paths, e.g., monitoring equipment based on OTDR/COTDR. To get a performance status, return paths within submerged plant (described in clause 8.5 of [ITU-T G.977]) are necessary. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|-----------------------------------------------| +| AME | Active Monitoring Equipment | +| BU | optical submarine Branching Unit | +| CBL | Cable Breaking Load | +| COTDR | Coherent Optical Time Domain Reflectometry | +| CSF | Cut-off Shifted single-mode Fibre | +| CTE | Cable Terminating Equipment | +| DCF | Dispersion Compensating single-mode Fibre | +| DRA | Distributed Raman Amplifier | +| DSF | Dispersion Shifted single-mode Fibre | +| DWDM | Dense Wavelength Division Multiplexing | +| DWDMS | Dense Wavelength Division Multiplexing System | + +| | | +|----------|-------------------------------------------------------------| +| ECR | Electrical Command Response | +| FEC | Forward Error Correction | +| FFD-BU | Full Fibre Drop Branching Unit | +| FOADM-BU | Fixed Optical Add/Drop Multiplexing-Branching Unit | +| GAWBS | Guided Acousto-optic Wave Brillouin Scattering | +| GOSNR | Generalized Optical Signal to Noise Ratio | +| GSNR | Generalized Signal to Noise Ratio | +| ITI | Intermediate Terrestrial Interface | +| LEF | Large Effective area single-mode Fibre | +| LOC | Line Optical Channel | +| ME | Monitoring Equipment | +| MTC | Marinized Terrestrial Cable | +| N-WDM | N-Wavelength Division Multiplex | +| NDF | Negative Dispersion single-mode Fibre | +| NOTS | Nominal Operating Tensile Strength | +| NPTS | Nominal Permanent Tensile Strength | +| NTTS | Nominal Transient Tensile Strength | +| NZDSF | Non-Zero Dispersion Shifted single-mode Fibre | +| OCJ | Optical Coupling Junction | +| OFA | Optical Fibre Amplifier | +| OSE | Optical Submarine Equalizer | +| OSNR | Optical Signal-to-Noise Ratio | +| OTDR | Optical Time Domain Reflectometry | +| OTH | Optical Transport Hierarchy | +| OTN | Optical Transport Network | +| PDF | Positive Dispersion single-mode Fibre | +| PFE | Power Feeding Equipment | +| PHB | Polarization Hole Burning | +| PME | Passive Monitoring Equipment | +| P-UJB | Primary Underwater Junction Box | +| ROADM-BU | Reconfigurable Optical Add/Drop Multiplexing-Branching Unit | +| ROPA | Remote Optically Pumped Amplifier | +| SCOI | Submarine Cable Optical Interface | +| SCS | Single Channel System | +| SCTTE | Submarine Cable Transmission Terminal Equipment | +| SDLS | Submarine Digital Line Section | +| SDPS | Sensor Data Processing and Storage | + +| | | +|---------|---------------------------------------------------------------| +| SEOI | Submarine Electro-Optic Interface | +| SMF | Single-Mode Fibre | +| SNR | Signal to Noise Ratio | +| STE | System Terminal Equipment | +| S-UJB | Secondary Underwater Junction Box | +| SWS | Single Wavelength System | +| TI | Terrestrial Interface | +| TNTTE | Terrestrial Network Transmission Terminal Equipment | +| TSE | Terminal Station Equipment | +| TTE | Terminal Transmission Equipment | +| TVSP | Time Varying System Penalty | +| UBM | Undersea Branching Multiplexer | +| UJB | Underwater Junction Box | +| WD | Wavelength Demultiplexer | +| WDM | Wavelength Division Multiplexing | +| WDM-BU | Wavelength Division Multiplex-Branching Unit | +| WDMS | Wavelength Division Multiplexing System | +| WDM-TTE | Wavelength Division Multiplex-Terminal Transmission Equipment | +| WM | Wavelength Multiplexer | +| WNZDF | Wideband Non-Zero Dispersion single-mode Fibre | + +# 5 Conventions + +In this Recommendation each definition is preceded by a number, see example below: + +**1008 terminal station equipment (TSE):** The TSE comprises the STE and the ancillary equipment used for the operation of the optical fibre submarine cable system. + +The number indicates the order of the definitions in each subclause. In this example, 1008 indicates that terminal station equipment (TSE) is the 8th definition in subclause 3.1. + +# Appendix I + +### Alphabetical list of terms defined in this Recommendation + +(This appendix does not form an integral part of this Recommendation.) + +- 7015 active monitoring equipment (AME) +- 2018 apparent line error ratio +- 2032 availability +- 6004 batch qualification +- 1006 beach joint +- 1021 bipolar repeater +- 1022 branching unit (BU) +- 4005 branching unit sea electrode +- 5007 cable breaking load (CBL) +- 6014 cable burial +- 5014 cable coupler (or cable termination) +- 5017 cable elongation with fixed end +- 5018 cable elongation with free gyration +- 5021 cable full safe modulus +- 5016 cable gyration +- 5013 cable jointing box +- 6008 cable laying +- 5019 cable modulus +- 5020 cable operational modulus +- 7001 cable recovery +- 5025 cable safety margin +- 2024 cable section margin +- 1014 cable terminating equipment (CTE) +- 5015 cable transition +- 5022 cable transitory modulus +- 5023 cabled fibre attenuation +- 5024 cabled fibre strain +- 6003 certification +- 3021 coding gain +- 7014 coherent optical time domain reflectometry (COTDR) +- 6017 commissioning testing +- 1047 cut-off shifted single-mode fibre (CSF) + +7002 deep sea repair +1027 deep water +1035 dense wavelength division multiplexing (DWDM) +1036 dense wavelength division multiplexing system (DWDMS) +2003 digital line section +1048 dispersion compensating single-mode fibre (DCF) +2046 dispersion map +1049 dispersion shifted single-mode fibre (DSF) +1042 distributed Raman amplifier (DRA) +5004 double armoured cable +5026 duct shielded cable +1061 electrical command response (ECR) +2019 electroding +1044 elementary cable +1028 elementary cable section +2033 end-to-end performance monitoring +2025 equipment margin +2030 expected ship repair number +7011 fault localization +7012 fault location +3011 FEC decoder +3010 FEC encoder +2036 FEC frame +5008 fibre-breaking cable load +6013 final splice +4008 fixed optical add/drop multiplexing-branching unit (FOADM-BU) +2035 forward error correction (FEC) +4006 full fibre drop BU (FFD-BU) +1037 gain equalizer +2055 generalized droop +2049 generalized optical signal to noise ratio (GOSNR) +2050 generalized signal to noise ratio (GSNR) +2028 guaranteed margin +2053 guided acousto-optic wave Brillouin scattering (GAWBS) +2054 guided acousto-optic wave Brillouin scattering signal-to-noise ratio +3019 hard decision decoding +1046 hybrid-fibre type elementary cable + +6012 initial splice +3018 inner code +1025 integration line optical interface +1024 integration specification +2045 intermediate terrestrial interface (ITI) +1065 interoperable cable portion +2052 interoperable cable portion interface +5006 land cable +1004 land portion +1066 land repeater +1075 land stations +1050 large effective area single-mode fibre (LEF) +3025 latency +6015 laying angle +6009 laying limit condition +5001 lightweight cable +5002 lightweight protected cable +2021 line bit rate +2022 line code +2017 line error ratio +2015 line frame +2038 line optical channel (LOC) +6006 link assembly +2040 LOC-TTE +1059 longitudinal compatibility +5012 longitudinal water propagation +5028 loose cable structure +1012 maintenance controller +6016 manufacturing inspection +1031 marinized terrestrial cable (MTC) +3007 maximum PFE current +3008 maximum PFE voltage +7016 monitoring equipment (ME) +7004 mini system +5032 minimum cable bending radius +1051 negative dispersion single-mode fibre (NDF) +3022 net coding gain + +5010 nominal operating tensile strength (NOTS) + +5009 nominal permanent tensile strength (NPTS) + +5011 nominal transient tensile strength (NTTS) + +1054 non-dispersion shifted single-mode fibre (SMF) + +1052 non-zero dispersion shifted single-mode fibre (NZDSF) + +5030 operational cable load + +1062 optical coupling junction + +2006 optical detector input + +1018 optical fibre land cable + +1017 optical fibre station cable + +1019 optical fibre submarine cable + +1002 optical fibre submarine cable link + +1003 optical fibre submarine cable network + +1001 optical fibre submarine cable system + +2009 optical interface + +2014 optical line signal + +2002 optical power budget + +2004 optical section + +2005 optical source output + +1058 optical submarine equalizer (OSE) + +2056 optical signal-to-noise ratio (OSNR) + +1020 optical submarine repeater + +7013 optical time domain reflectometry (OTDR) + +1057 optical transport hierarchy (OTH) + +1056 optical transport network (OTN) + +3002 order wire channel + +3017 outer code + +2029 overload margin + +7017 passive monitoring equipment (PME) + +5031 permanent cable load + +3009 PFE current stability + +3003 PFE earth protection equipment + +3005 PFE mutual protection + +3006 PFE nominal current + +3004 PFE personnel protection equipment + +2047 polarization hole burning + +1053 positive dispersion single-mode fibre (PDF) + +1015 power feed earth + 1016 power feed earth electrode cable + 2020 power feeding current + 1013 power feeding equipment (PFE) + 1067 primary underwater junction box (P-UJB) + 2037 Q factor + 3023 Q limit + 2048 Q-time variations margin + 6001 qualification + 1043 Raman gain coefficient + 2011 receive terminal optical interface + 4009 reconfigurable optical add/drop multiplexing-branching unit (ROADM-BU) + 3024 redundancy ratio + 2031 reliability budget + 1041 remote optically pumped amplifier (ROPA) + 2026 repair allowance + 7008 repair safety procedure + 4001 repeater (or BU) housing + 2013 repeater (or BU) optical input interface + 2012 repeater (or BU) optical output interface + 4002 repeater (or BU) optoelectronic unit + 4004 repeater (or BU) power supply and protection circuit + 4003 repeater (or BU) supervisory circuit + 1029 repeated submarine cable + 1030 repeaterless submarine cable + 5005 rock armoured cable + 6005 route survey + 7010 routine maintenance + 2059 scientific subsystem + 6002 sea trial + 1068 secondary underwater junction box (S-UJB) + 1069 sensor + 1071 sensor set + 1072 sensors data processing and storage (SDPS) + 2058 sensor subsystem + 3001 service channel + 1070 set of sensors + +1026 shallow water +7003 shallow water repair +6007 ship loading +6011 shore end +1040 shunt fault +5003 single armoured cable +1032 single wavelength system (SWS) +1045 single-fibre type elementary cable +2051 signal to noise ratio (SNR) +6010 slack control +1039 slope equalizer +3020 soft decision decoding +7006 spare cable +7005 spare repeater (or BU) +7007 spare storage condition +2039 submarine cable optical interface (SCOI) +3014 submarine cable transmission terminal equipment (SCTTE) +2043 submarine digital line section (SDLS) +2042 submarine electro-optic interface (SEOI) +1005 submarine portion +7009 submersible robot +2034 supervisory of an optical fibre submarine cable system +2007 supervisory section +1011 supervisory system +2001 system design life +2008 system interface +2016 system interface bit rate +2023 system performance penalty +1009 system terminal equipment (STE) +1074 telecommunication functions +1064 terminal portion +1007 terminal station +1008 terminal station equipment (TSE) +1010 terminal transmission equipment (TTE) +2044 terrestrial interface (TI) +3015 terrestrial network transmission terminal equipment (TNTTE) +5027 tight cable structure + +1038 tilt equalizer +2048 time varying system penalty (TVSP) +5029 transitory cable load +2010 transmit terminal optical interface +1060 transverse compatibility +3016 umbilical +2027 unassigned margin +1023 undersea branching multiplexer (UBM) +1066 underwater junction box (UJB) +3013 wavelength demultiplexer (WD) +1033 wavelength division multiplexing (WDM) +1034 wavelength division multiplexing system (WDMS) +3012 wavelength multiplexer (WM) +4007 WDM-BU +2041 WDM-TTE +1073 wet-pluggable connector +2057 wet-pluggable interface +1055 wideband non-zero dispersion single-mode fibre (WNZDF) + +# Bibliography + +- [b-ITU-T G-Sup.39] ITU-T G-series Recommendations – Supplement 39 (2016), *Optical system design and engineering considerations*. + + + +## SERIES OF ITU-T RECOMMENDATIONS + +| | | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Series A | Organization of the work of ITU-T | +| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues | +| Series E | Overall network operation, telephone service, service operation and human factors | +| Series F | Non-telephone telecommunication services | +| Series G | Transmission systems and media, digital systems and networks | +| Series H | Audiovisual and multimedia systems | +| Series I | Integrated services digital network | +| Series J | Cable networks and transmission of television, sound programme and other multimedia signals | +| Series K | Protection against interference | +| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant | +| Series M | Telecommunication management, including TMN and network maintenance | +| Series N | Maintenance: international sound programme and television transmission circuits | +| Series O | Specifications of measuring equipment | +| Series P | Telephone transmission quality, telephone installations, local line networks | +| Series Q | Switching and signalling, and associated measurements and tests | +| Series R | Telegraph transmission | +| Series S | Telegraph services terminal equipment | +| Series T | Terminals for telematic services | +| Series U | Telegraph switching | +| Series V | Data communication over the telephone network | +| Series X | Data networks, open system communications and security | +| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities | +| Series Z | Languages and general software aspects for telecommunication systems | \ No newline at end of file diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddece30ecf188fb8e98a6fb53692413c0e0b482c --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:391e7a48933fce290351c3fa3c9c8aae266b44e9a7bd1992a6c4963ca986c6d0 +size 40869 diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477 --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4 +size 7192 diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e929571d75f7eb26b498500f7da5e1d5b83d9522 --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44bc32903e5f9c4ccab2e2dcb4363b8aa6beb55ed3b38a55ed32449e4a90cd67 +size 36651 diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14a0f5aecf56857dfe89536778e331d9e3314d39 --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2efbccf40bfcecda6ad75fd37ac4a17dbcd6767a60a8364d2763fafddf87956 +size 52617 diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c983f3011b1e8e5a4c64a96b6ccf618821f685ce --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ced0ba0b14236cd3185df82aa0d798ee98d64563abf6bf6ceaa53b5b96a3057 +size 25944 diff --git a/marked/G/T-REC-G.979-202511-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/G/T-REC-G.979-202511-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7216c7970dd09d1970d4f8985245bc5ae62744f8 --- /dev/null +++ b/marked/G/T-REC-G.979-202511-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f59fd3f9d54e9e4420cddd005dec0708b5b2512c42f5400c554421c3cd95d81d +size 26162 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e817d0bf2746f9df6b702c156e4838533b2af076 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fa7be38a14b8f049d4e547ca93f004816400049863d21e0907262e83009bcc2 +size 78133 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c33f7bff2e6e2a749d4d2ce1253a598fb60ddf3 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c47291bb59738020ca469504603bc361eefc1a2a9bd050c63efa391334eb16ef +size 34651 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f52f9985bbcd5f02e1cbbf27234d87073dd03db --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/1d7527f4316cfe2d342b08d1653d1592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:788fdd502ad03f76c874f714950cbd13863dde8b02dc0573d3ee8274382877a0 +size 6975 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cb4f5631c9fa3f4d58f8b526e9719a43cd9874e --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbdf999e97ee0da4df1f17143fa2fcaca6614483760742907cd1c74b4d319911 +size 71726 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b2f004f6a1d49e7322dd5ec66c75b095ded4a80 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae870471e8e45161164db3282e3c2b466265b002c9bd548a6d8b50d084c69475 +size 93462 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7f84027ba48914a9443d42af50424a5b56f344 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acdece0924bcc69499fed7871beeeaede8113f688dc509da7013d567c4537c01 +size 94821 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6eefe5eafd8e5f3b7ad136cc1ed9d6c4d6ec17eb --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c30661a440e453cfbc8e84233203e4bd1ee24fe66e3990efdc964649780e9a54 +size 44002 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6e0ee35eb7051c1416224a1069d31baa941fde8 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6e3d7b1d88190477626a79a2a9a43c174ff1c0b818f85549fa8a13ef9cad7d4 +size 139884 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da3a1e3851bb28fabb46fdfeb0d17484b42d88f3 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776a81d47ba66ed5923bd0286a4a91ff4176a72cbfb409816609714b2aa774f0 +size 41660 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bc8160db5327266d79b176c3d71ed37c3222e11 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a93b721b8e8e9a3448fe9f2d5f47c6067471a125cba6c1d1b8c1d6b1a2f7d063 +size 21762 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f3db69cc094ce9e33b06657e77528b1165742a6 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f2fdb014fbf199d00245a97fb40f1f3b1ab6257c1cdf23eaca6e6208ea904d +size 137297 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b6ab97bc3c29fb1f18208ab2776560df8ab3b59 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6950fc2793e8a781312f06e2fbc1bb01e1b654bb0691c7881adfaabec9e209a5 +size 53270 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/a3472689858b068ef469213682965325_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af6a4ab1e258ba23cba6b6f8548286e7cb8fbea --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c477a1fb3caae65dce396767732572a3fdcea0425a841fdb9ef8a1b0c89b3c44 +size 96943 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b9355c5c03edc0bfea38040274cd72fffa8a62b --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d442018785c6160c9ae636b56533506c25a8ead3a191c10ad07284b8c305da2 +size 110254 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dfae24f77223f47f12eac7ab0a9f27951ea0053 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9ce1075c75a0c4d328880239c1a15a5953843124cde2e119ce3e99ed4cc4fed +size 47762 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/bac21fd48fcd7f025c723590e07d1823_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/bac21fd48fcd7f025c723590e07d1823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c79b4cb2796d2de7e6913170ac1c1b50ef59932 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/bac21fd48fcd7f025c723590e07d1823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:861df4608623d9beceec9d30927ab403bf4ef1a907a0beb63d3500cfe882ca26 +size 137293 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9070a5e76fb36a99fc19fedee64a5b2816957472 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:781b440566b1f8f222f02fa5f460b7875985a5609a52bf66567e1eb7b3d95877 +size 87301 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5ef0bd99b46874fb000876c2b68c0ea5d9fcd0b --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d117df888a3bd156c921bc317dea04adcd9ac4329b44b1bc6e64ac97f10530be +size 69638 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..883f974f71848e2b026ee92f76947c80127670dc --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a355bfa21abcb28a2ad5d5ad960a48955cb555ae05aff6defb6524d827f426e +size 68824 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8ee7afc381f5068e2fa9ba7efa10511d74821d7 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faf44967bd62a02146c5e7f1bc0c6238baf2dd2a1f9d65ba7025a1fbd7565dc1 +size 96964 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/d94a0100320109c1b9cd75c1054c7b95_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/d94a0100320109c1b9cd75c1054c7b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4dcdd17a75548875b39d8eb47d9bb44388bb655 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/d94a0100320109c1b9cd75c1054c7b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fd5ec714f4138dd2cba6cbb213b7cb5c0bbe9f672c16f10ac214fa2a323f8c8 +size 52738 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b73550135fceffc7e32ac39ecb0f0b61a32a6bdb --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9cd3727cfab0cdeecad981de84ae11065bc0a3e7c64fc84e0f3b8237478973d +size 95860 diff --git a/marked/G/T-REC-G.9803-201811-I_PDF-E/dd0c2145bef6df0bf52f9ff319cf6713_img.jpg b/marked/G/T-REC-G.9803-201811-I_PDF-E/dd0c2145bef6df0bf52f9ff319cf6713_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdbc66a458d0d08c0b78543ec54c9943ca0b1c46 --- /dev/null +++ b/marked/G/T-REC-G.9803-201811-I_PDF-E/dd0c2145bef6df0bf52f9ff319cf6713_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aa10ef2b2192e05d0d0e47daa35a72387788462466fd5c58e138f1551dd2f08 +size 46761 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c1a90f3e95a68b02abb80fdf52d5f521ec98912 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/01832e59ebad7ada5e790de6f90cc9b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b23c78102e80837b45373d314224026318100153442c7414afbc4a0202aed37 +size 57805 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/06291c5328a7a4335d41a48850a3a207_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/06291c5328a7a4335d41a48850a3a207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67d20b96b24f4e7eb5a4b44d3f785aaa2eed0e92 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/06291c5328a7a4335d41a48850a3a207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6eea2a6bf62dab37b1eb7a99b7380fa0a560eef8f9c68e8cdc5d5a32c72777e +size 60343 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc451b3162a69bd0a9845b958dd2a3e9db774ce3 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:527359b03a28795192657954b39c69630bf2715f2ad9188f4a59b5ccba510164 +size 26248 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bfeccc782320359193735b9e1f120eb8ee3caff --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb787009a3932dff1466faa7a9caf9080e871c66102466af3b8ee47abe6c927 +size 82464 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cf350dad15103859eab74f84c062787ac3a60ad --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9db6614a0d482da9dd1a58180b9e7f11ea4acbe45f1749c9a11b09a76f83840 +size 22714 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bc8562a7f6c8b9707a9df724bc57b1e93be9c8c --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/0b7849dae424b0dd33e6386d2384643a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42253b9eb07382ea60dcd9363d359856b54115da34f13a11b5e0184e2f6b874c +size 44520 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d029dd4fbf2b92152823b8298396c96c7282e426 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:476aa07e8e41a13b741a431c04ad0f9bd3a7bd0a3822f14a669b12f2abaf0e0d +size 3828 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9704a93e2ecf652460c2973c41ff92a07715e410 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc91f9d89868718a04d50cf4a3c079780b644005ddad6db70503ff9e2694486b +size 72305 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21ac749e1ecb0392c715d15395e5d62265a6b88a --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be1f0a5beb92c008ca672ed35537eecbb063f079d1bdecd3cc32e503f4663068 +size 61138 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92a8ae9d888c7269cf2a7eee0125ac16777bc516 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/365b54f616aff249b4e6c0edafdcb9b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c9dcb0f4788d9b9620eead072600ceeb3e1ba1d58a1c6f1df546d2f94ec194e +size 41098 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cacebfaaea5a59a21df8d52e0d590621a12978f --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/399a5af4f606059626c92c92279d54b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42df8e32e1c62aa4453852f353eebd1a3e09dac782c299e26e703a4fd082e9d7 +size 61212 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b91197bed787fff6b383a6d7a21e1592e63f9fb --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/4cec89a753c447a050c0171c274f2acb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69e09945dc97e43c17c7c639c0c3b5443d437cf46fa3d4678231edadd319524c +size 44250 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2857e0aecfdd9ab2700499b5ce43f5fdf0fbed90 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aedab8db00b84c6a51b5c251f06949aea146ae3d6070452b9b2f770d65875d1b +size 44238 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43baf447049de37f97991c0f0aecc7a319e7911f --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5414f65867392f05ba0063b208eeb5e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70dcbfe528634d2df1f850a39264b54ba82063e930e2b222c4107b2a1ba6340 +size 74499 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31be145307fbce2aaa9cb8cff0d312be51a29198 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1940d9e5a715e4f013f0d8cc03478360033678021e957458147fab2fce7224c5 +size 28898 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fc257ffe3791082d536847e2988e0ddcd2bc56b --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/645bea0b27d63e4a9a300af5793ae7d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f8ac2968e15846723d3c90e93c82499ebbdde921562ccf32e7b51cd08490a6e +size 70998 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ac8575d6e170fd1083f1b96fa6e02c17efd79d --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7071b34c9ecccf79f3e796b5cbd70461695f6f69c7e824299e30ca77d684068 +size 50131 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3adc8eb648dec14413d4b05c4e74ed5d0e20e408 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01ad90a07537bf86e75473e51f921ef3a43d35e083a78efabdf09366d3841813 +size 18153 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..405e6a950672f98d21cb1e1060934239a08351ff --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd38b3963a353c8d7247a35bcc1b278d7bacff21e520c35ebb0ff958a6949356 +size 43201 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbfb0609013494f433556e52680d14201ded2a3b --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/6f11044c88ea04e43de06c3491defeee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8347ddb0bf1b534445e97fc171be384b05e9b4ac1d2186d6cdf86d32cbcc6ec +size 46593 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd6a0b9357099c7ee1823265e1e4f8b8569de9ae --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6925d4f2c738cb305d152deae96ce709c0ab7913085bc979c3c289b394b62e84 +size 65770 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..773af6f114367a57da6f6582be37c824f2148133 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/7fdd9eacc17f06e094850c6755b47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9452c0f0f4ce9c941675036f19a8bcf0cfa4e1cf9e8f864085b9d5b0b9e72597 +size 48518 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2f97bc1c86e92156a0e144c68c8100164b57bda --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:184004271c53bdf04607d6342c4104f6baaa1c68ebeba4de7592c277e0fc4cea +size 39761 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7047d7717070f72268aa503cfbb8cdc26ddb151a --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/89f8aefc01866631793087542316cef2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1088edff46b35baddaf0879e135b5d46ba64a99228d5efa55595e70616ed5fff +size 130186 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d81a5a7bcd43a715dd2d5e2dd43432b57907c9e --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ce50bc10864dc86e1cdee4be08f1897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca07533337583fd85455158ec682c152c8fbf6750b379d4865d2cf712fa8bf1d +size 57690 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52372326dcae0d2b8202cf094654907f0d397205 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1225ee8407b17c64cf7d3dff0734d31be23f4c56ad668f9a95b5924965937d80 +size 30733 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7249b7fe270ee8cf1dcb2d7524360893731cfd7f --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4bb30248034a14d5233fcda6709c580104c94bbff65428f634602f1dc754bfa +size 26995 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0af82fedd41052cb8503f118737aeb94b0be3c22 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/a2251e3bbfcd726b68cc50b091e53b02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2582aa2fc5c568564c89a1837bc05e554483abf0129799a0b13056a077857f39 +size 65716 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35c8004b932c2bb42edab54125bf9fab7c054ffb --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c0b9e5fc63e19306394e0d4249da62cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b59d0f3357c0b56fa7fbcfa8c48e72be0d2ec0fdff91a89052f75840e05a35a +size 140170 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f337d5258b939fcf1534eb2a1423478a6512ab9a --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f89bab17377f03337b83fe1a96c7ab9929b69a87ae34319fe7c45cf1472d6f2d +size 71272 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15c2527c3b7488b39c324cb1441398a017b29bd0 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbab05075b3d7dc0d27c4cbb0c914a94_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:786e818463488ab457287740d094bbbb93d034825e6f78ed765eed09a620985f +size 120899 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e704ca238c3a668003a77080cb0ef43dd896fe0 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eef1aac062ba0ffee9d31c616682d16a2343e3bba7ae4bb02c8e0ec60cfc0394 +size 31570 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..974eb7dc9109f884296fb13a1a066d1b67f6e6df --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d28b826b8e7678d9dcfdbdada641024dabdf9193f982a64d0940d62f1366845a +size 53385 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f77d51660fc63be6c4407e14471ef7a28d13277 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/cc98b584f9b31fe69948e3fa65a3ba69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fca8c4c7a5dd4b03acf7219db9c7c85e80ed95d8cc479f1e9b52cbfb82b33cf +size 63974 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1af76fbc1c5137c952d8540ea80eaec45c9dc5fb --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126c9b2162366954047a26769ab626c1c33b24978c361d3d7f9854e2fe9f2bc1 +size 39663 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2958611ae150a246313f94531c2b11c413512010 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6ae9aa65bf4684cdc0ee9491191ca91c7acdcd55a0643992b304476872e7902 +size 72787 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4fc566a3ae118f71eed274867c0711d2c3d85c0 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e451401f8fa77b466f401d5fce15b26c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fc40e5f5147a1b15057cf5afb4bf4af8b381c7fe2f131faf2e9511241f09a7c +size 60370 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489ee99923bcbabe55f450913ccd432d6304bb44 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/e64c7b989e5bdb2708cd7aefd18b06e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8efce2bd988824bcda9c45b102504ae7b8b14bd0669abb1edbd4a8b2a7afd2e0 +size 31516 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00e0692ef7e1f7a28ddd5417693ab4c404a95382 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b26516b3788284bd763e2c8476e9eb8f9b831e08f33d6044523ac928457b88a2 +size 66950 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/f97eb8e2582d6496a25e6508c9db6572_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/f97eb8e2582d6496a25e6508c9db6572_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fbe72056cd1c9a65ef9a66d10849f7cd9de8760 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/f97eb8e2582d6496a25e6508c9db6572_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9ab3db8f04eaef9e2ae2df1ff76c6c3b3ca9527289c881fd1b04057fa3bf6ed +size 64201 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82a3d2cce3a3dccecd75c5e799f123baaf25a8cc --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287ed6e091d9c1812e695bc4809f8ad8243de528554052c2823976c5f0aa1ac3 +size 30594 diff --git a/marked/G/T-REC-G.9804.1-201911-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22f5a829689934aa0d49bd664ee14a1313524e45 --- /dev/null +++ b/marked/G/T-REC-G.9804.1-201911-I_PDF-E/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ef0b43928b116edf80656149f6c899b28a36e84a63e119f58da09310c812c8f +size 26640 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99278a75fe5ba5bd92d2e71e94b97fa18c06e49b --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/14252bcd35912bd656e98b16b2ee51c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cba7a54c10fb1a8baadefbcaa2bba1d48fd5384c74d87b4415c4bbc2fd725ee3 +size 84664 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5a35041124e73f88d6638cd17f42a2eb4f6781a --- /dev/null +++ b/marked/G/T-REC-G.984.1-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.984.1-200803-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ab46b9c2c60c177b0e34186679b5eb8bef42b41 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/2bacc162a73d75c43a7f90715832bd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77bdcc0887e9ddb4315a5a92e23fb69156c0dc43641777d7cf80fb49b7521258 +size 106153 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6edf1dcac8c11c7613f40932e5479573c3a79e2f --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da9dad24b3ca0659bfc5830b7a30870c8e9551db61ba922be293c8a693df6e2b +size 43460 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d6dd0d22a94c0e093e39486d20e7046d23447a9 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8624efb6793ab0a302dfcecfe3ea5aef5fa56f3aff5a32cb9f0d8bd93b8f7b40 +size 20329 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6c1f9ceda83505ac5330358e67dc641b9638f98 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1566469a65eaf63b894e1486fea280cabddc4ecb5ea5f2ff133b90708f99cba4 +size 31857 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36433b134bd32ecc54fd1f6f042c68782d5e24ed --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/7133ccf78043568ca62ecbcd43628a4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f26208ba535010ebf95e490a0f0e433d21049c7d239247cd522d92ac7fdec202 +size 56217 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..390ad2862db2679d57dc89066f05b8cb53bd3ebe --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/7ae836e598020d937ed1478c2ef13025_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d923d07ffd869cabebf807f43fc19bd58a750b044a60e4de506f8ab59ad3de17 +size 130880 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43567d942968165e0bddae2d80a1ad945dc44c2f --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/812e188283162af0b54fb3e30ffee51b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f00e0003278c8603262caf2feb7bcc413812ae3c67b9ca9a313fcb9fab982d0e +size 26188 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82478d3f2e34c8ff93290adf7d2437a1e21286be --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab268054bc71c8ab8ca333a3e06fae38cbae133077a821b72ad2893dbbfd88c5 +size 37398 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20cdac4a7fba3830f5b715937dd3411a11fae01e --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cae2aa2f9fbd65666b3289dcf1bc5df1c484cc98847a1b6335bc938187bf121 +size 32357 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31dee6a2155b548848e737fa1064fa2be6930160 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/aaf3e6e44cdeabd6d1df869c5f392ea1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b24e9896a225fca2928f502091d5d2f62c003532a0180f8115d8596aa98571a4 +size 92183 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b9e22b74c662214bef90de82f28b8ec5cdcaa3 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbe80043bf7602c5f1552bcbdb4aea70e5045452fdbb201d19baf1bbcb340368 +size 41008 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0aab385804e2b60ada7551242e8a03c320cebb5c --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/c494cd874a082a97b50b3c4d3938f467_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1be40fcdcc66d6e88cb4e15f561435433c332d8eae8f1b873dfa14df78407fe +size 114782 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deba324e972384f79efa080ea4d9afbe8af31828 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:191caa293e1087b91ed5bfa3549986bc64e99fa59d0fa7d771ebc3e9e252faf4 +size 73271 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65177a1e32451c058626ce54de07ee33c99be97c --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d0826fcc4e0db0b75bb8a5bf8b69d04d190bb500234edd83b10cc53b5b68bd3 +size 77625 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ce9a4e89d04226c7bc9fcb8c5c6d6903f5442d6 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17aa1fcc3b86503ad1dd0717a6c34c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e68b730570f307e62f24da1c76b42f7bd6a64d73972c47e095542319b7bf0977 +size 91599 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31f8709c55ec694b1538bc44b86b9417d0e51156 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae08e03da79e1b827c8e50ab7bebc9f32c71b56979850e007a463a5c753cb457 +size 45255 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df237f4192b693eb3ef98a741e15373b1120d25c --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1787b34818b4106cfd34eef931ad4332c69bf1cc2aca808f23ffbb97f975ff9d +size 55324 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de925b74bf5bf608bc63d2c538205015788371ab --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aed25e9e83e9e5a80d446fe34942c20a32fdd8327c8096ff891b2836b4efa6b +size 22929 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4634a7e8eb40a6106aab27780e089e2db08b8991 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d11d03f82e6df24cef95addf55755322a2c387efffab765256f9984e83403b3 +size 49329 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0525d4775440ae520bb9653a95a9f15598361977 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32db4be8d77743508b1093bc37fbd1b9c5cac6e1eb7b973b3b76d4248ce3de77 +size 101162 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2610adb50179f49c77e9a9efa2aad79819db97f5 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a00bfd50d0622a32fb61628c7b224c5e63b2b406d8ed5380dbcbd2bcb39d523a +size 22464 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149a91114a7911019b4e10d9667f086b6c649a39 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a7eead64d2613baf950f1b4ffac1a53af03fcfb709fbde902abe8bcdfe9c1b5 +size 20481 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da09831c5d52f617ac2c657759b96767ccfb6f0f --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77eab8dea3f3bc82a29cb17234e992564d1870a3ed9c28f8a6610ab1c714650a +size 25517 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a0277774a94559fa8dbb9de659a55e9fcbb3ffd --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41ee1d675ea85507d1d768b370504f30054f676cf86ce1618d13f2d9de76aba3 +size 93724 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c62b8fa234c1728b534eaa92a4b777fdd408b765 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/f57c7b37d7a05a99618104f390089f03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:477f007d0c2f6978ae42ff16d665cee62a7358dfa7fe9ae297c4d0b21a54ad33 +size 38951 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ea927a1ca2135e8cc6e77e3e5788d58ae477777 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa01531ea2c45beeb4036005da3037a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b573c14eefd483878c250d35576da6055d34a13feb879bbf2d11e27c20803858 +size 125148 diff --git a/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1be9bfc75fe5e930b9da87cc3ae79c1bcc8197c7 --- /dev/null +++ b/marked/G/T-REC-G.984.1-200803-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3751eab80a7f8e5006ea70545974f7969e6e6accb0eac4c81079ab03c6c7137a +size 40142 diff --git a/marked/G/T-REC-G.986-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.986-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04ed0575fb17e6faeb57d9d81b58c3b85f7e21df --- /dev/null +++ b/marked/G/T-REC-G.986-201001-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3223bb567d6cdfacad7ced972fc4eab63d7b0659969b11a4801458bec7649f19 +size 3852 diff --git a/marked/G/T-REC-G.986-201001-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/G/T-REC-G.986-201001-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0a2bf971ab4c8c65d0bdd9c77d8fb525d79838d --- /dev/null +++ b/marked/G/T-REC-G.986-201001-I_PDF-E/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:925493c0533c9e7d2e7cd322543b1ec3ab8f4c14e6e22601bef8508e685dc89a +size 10251 diff --git a/marked/G/T-REC-G.986-201001-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg b/marked/G/T-REC-G.986-201001-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fb4ed64946c4d62dce3921016ca9935081aca64 --- /dev/null +++ b/marked/G/T-REC-G.986-201001-I_PDF-E/b9ecbc3baefab13719e000faa6e0c7eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:853cf01b1c6dd1c19efde8d561accc3ca3c5a20d220448f09dc858c04bba1205 +size 57998 diff --git a/marked/G/T-REC-G.986-201001-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.986-201001-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fface6ca205a1d8e0042958798f888b6e19600fd --- /dev/null +++ b/marked/G/T-REC-G.986-201001-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeb69da415f7c93eef5d3e248d3b36ef94ba6b84d072626aebbb93d0e497a34d +size 39785 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b54d5787bd32cfe3640f53967115afea4068662 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/0019f09403376d6444ee323591fa2e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71e9b74a07f17c67d7d31187d351e11c737d59f2a86d3dd6655bafaf3b493250 +size 57638 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bedaf3161817f696ff73b211e3c9a313f7858e94 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8368f6af22c881d674198cde949e61582be0697ec03b650fb07bcea7a4b8f160 +size 25607 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/04c52bd4e8f924f176fa4d9dcc138e85_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/04c52bd4e8f924f176fa4d9dcc138e85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b565884eedffed20d91790997a5c3def51617d08 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/04c52bd4e8f924f176fa4d9dcc138e85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:765cb623873a4aba9cdc0c58626587ec7d4fdf44afa1f166ce20d5b6dfda49e8 +size 29312 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/0a8d173734e4e46c344178e8d21bcbc3_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/0a8d173734e4e46c344178e8d21bcbc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..409c87fba3ee7d193cede2dcafb2b53997254c7a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/0a8d173734e4e46c344178e8d21bcbc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74ad40be744192b19ccf80589986417ec2de1bbb8eff92420c3f59a6158677c2 +size 31551 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c647a01cf902cf7c88f41032141f43a4f8bc64fc --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8568acf6db632b10c6733acd859de9c362444f689471e1f2643ba11447b6c118 +size 84710 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db30ea31c11d9424f55300c0d4a121b2f6bc671a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/0f007a07756791edf7be50672cb010a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87a48b73c5b024aa7c8d536393dcda02fdf09d5920c5a96fe7cc1e1967af96ba +size 95124 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a798d9b0032f2a27ca54532f1fd045351fac1572 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edce5530cdc049c5a9f04e77b41310e3b32376fe692dbcfc7f47dd988c746c98 +size 19440 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fc754d324f3cd725986cfd19c7e0b61bd3f43ae --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/107c8e1abcb7033ad244e30e7a910045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a81cee458ae8626397203e44b736adc1cc14ced65e0059c739002cf3aa34dd1 +size 45723 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..802d519f9fe2fcf2207ec736e0f41c001f5cfe64 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/177e8bc1c595b7fe3461d9919f87e044_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd3100d69d137ff70439851180ed05b2f3db78a5022bc1dc74cdae37191cac32 +size 96556 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..378bb6127f1f91ee5cb92cbe44695d349aaa879c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/20e1585db1a707a774877194c689de82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f80f1d9e39bb1b84eff83bc2038b7c11de668965276457a31644b2d9fdb82c45 +size 35039 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfdc4472862caf353305d86573297a494e3ec20c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/21ea5add6a61cc951b5c43ddffefb3ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a3c8870dd22ae67802f2333a0660391900bde592cfb703485d6c1302451e88 +size 19815 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69a3f298d2a89bcc46b64fee3269749df7b0dd2b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/235e996e83e7d5198cf9d909f5713cdd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c8fe681a14846ed811a542c86eca229db496cac90fea9f457b82cbacfc7fe53 +size 31494 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1efeb7ec4e41ad27fc9e25c15749226fd92001d7 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/238754529581b74f0696943d436494bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:122f04062ddca893761bcc70fda8e2c0cc64a464f4ec35fe65a272401d9af358 +size 23145 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ea220a7ad7237484814fe201f1a307874e015a7 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:377fe750a1c2423a627ca08f19a2e4344619f1adef7cfe95a0a4d2f0eb115cd9 +size 23246 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5828a3fb79cb9f943be567a99b7a95d2c01e45b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/2580688a4de0a29692805cc6ba4822d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7bf6b52c22e4fef5cebc04ab95d47de38758cf2c0d983846ff69be9912b76cf +size 109414 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ceaf884cd359242ddc60356e45f126384051d1 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6070019fd80850d21ee355a910fe5eef778da20c0fe1b86af21a8f2066df87de +size 35084 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..331496494365d5c9802ab70c64e0a3144e3a08b3 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d18b2a0aad450862428a4bbd9ca79266f1144b476c4bc5456fe5a9b513ca869 +size 24215 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..990034b87672e89c99ac098ee18f2f612b9f5122 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2875036d48c86c836d25cab000d1469811d04a76a6856a859d2b1579a6c40534 +size 65136 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..242820a92a56a87c488762717e6ebf1ec57cd45b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/2d548db0b26b7bf33244320322d5ee2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3e3feaecd209f18d37aaab2b173b1c9345347c8ff30d08cf60f7029409e3832 +size 8971 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44b79e91e000a0a5231820d509e0cdad4cbb7d8e --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/2e399449b7f62d40167a65ca88888917_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df22da52fd9519c4acf394ec32514e820d3856fdb88ecc132cd8e27c322629b8 +size 22270 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8adfeee7146d0a9e9f8cc553aca784a4e328ee15 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/2fbbd361d3aff2374a19eb4fe03983bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86471e1ced9144c7d9d02f1698b39d75dca8481bafc54ae3246345c75bf6b3a4 +size 14369 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74e21847f597b372402589a01381c99830755f94 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f23510805eae5db4bded30cc11319ee894cb7c68a43d42f140bbb73ea164d7f +size 24370 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/315e87b80426782bb6e06222d653f515_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/315e87b80426782bb6e06222d653f515_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dab4d3fe4609d6333ccb9bc98575aaba83bbf29c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/315e87b80426782bb6e06222d653f515_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a53430b1005b975e9faef63c41d8f6ad2e22eb0f94499ca0ae9ab0ce427f37a1 +size 10997 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bf34a59e203a17377c30f942968cd9b13db763f --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/3349dc82c6333221b0610be6ee7250b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f171f28de4116595c25ec10fb6e47b03f6b207211a1135f4bcacf0bc9a7940a6 +size 33496 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e26ac3a6c51e1ee184be3a37e695b5f0f8d1a20 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:313764332d651d73b5fe66c37ed4f9b09aba84b62bc746012b8c25efb5655971 +size 23559 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4782c44c87e53ee6f5cc0aca5dd75b9260dbf3f7 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dff917cd322b8aea94490174541e671166f054b22bb4bae869d237b296d72f1b +size 43768 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12f83c950efceb3b396dcefc1020f6d566cc13cd --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/34b381406f073080ef510a32772b2612_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62b260d87422f70f88ad49d92bc0e16861f162f94b4b66f53a68e8600f01d39a +size 33029 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d4c0832e08e2cfaa69baad046a87dff2535c7e4 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/38cbce07f83fba6d5a7c46605bd5743f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d62fe28c7e86ab90d45ff7cd715cc48fd930cedfaf688640c5151999bafc66d3 +size 66111 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5d99f0d2affe9e5c987448e343471a1321880ac --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/3a006a7c9c9934695f0fc731344eff8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab6e2bee5ac9cce173164db4f877de5a39382899b97ddf201b5d0cfc3fe4b0c6 +size 24904 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c257f4c1a1d11f62188f020f24f3f7a50b5df956 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06c6edad833c6a5b9388a239707217fdebea293d7319b477eabd228bb3487592 +size 16340 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fda292eb00a7deed633b73def0b26bda79c928b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/42c65f5cb106938992fc73c05c8713d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:001b6cbaad5554c6e3681908f5c493b596fda61cdaf4ef57b3fa00b04663b020 +size 13813 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/461ef997feb933486effd3b0d3504016_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/461ef997feb933486effd3b0d3504016_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2d4ab5a2db42b82c3ef5a7f934a320999e95a2d --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/461ef997feb933486effd3b0d3504016_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2cb08a7a891bfde8657d928908660557afe55a70da7718ca07ea2cdf72f33e8 +size 12124 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/468be155058fd5d2862919eb8ec35496_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/468be155058fd5d2862919eb8ec35496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48f4a1318cca17ccfc8de4ad2d23c8ddccfdc67a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/468be155058fd5d2862919eb8ec35496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dadd13ef012ba4646846c27205721e5f7cde93736e39f371bff00896ce55bef6 +size 20664 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2db4ba2b3d845d593c99cdb4968007b0347bdcf --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:750421c7d643176a22b419445f3427a33c65f4a984d6d2a0815a4b99b71179f2 +size 10154 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e423f8add2a2c5d4fa6750b2ad3d64dfc888e08 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/4851479cde0f63d07f4db536c69bbdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7486c5084420949534474b0da36404d1422c9d43f5a84296a41f734a4bfb9915 +size 72883 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8c42c7ccf5903068ecf4cc545ef6ebe4208af52 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/4a390493f601ce1ac6b9201db4e28b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aff57ed950364ac3ca571c4805c759359a68d7fb1faa612021ddc49b961e36a +size 16394 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06d1634e5753c59f9af896661e4bc6492b704469 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8348d865ef914703aba6ccf289352a5d10393337b1231aa4caba66a78b8d3770 +size 63266 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..181d949bd994251e4b9f62e83715f452cc916977 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd6866f90d67a3206cd870d1f47d835a80a9e8d98b96ab275236edac074094f0 +size 91739 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5793aade052ce4346427dfe4a9a8d91de923b09b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:588e81330bfde929b0aa23d818debbaf924391a7618e97af3c587668fcb23c72 +size 6411 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9e76091144849ec741537071161c15447a4bfda --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/52c40e2f443985dc63f45dec57d90c8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d73ba95f45d845ba8bdd374e5855962ccaaa4d3f32d878a417419f8cb450ddd8 +size 89440 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3868d8cd98c69864a920b5e7c80f2d5af0bb6b47 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/52ed951cbf3a5e682e913881bc0d13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0702d8695fdb2ce29f3f533a72b6e09525258c1318035763cbe81f15246df8b0 +size 27892 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/5953341e6a100b62c000fca825371797_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/5953341e6a100b62c000fca825371797_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4ada976e80348a949e5510967ea8cea8336889b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/5953341e6a100b62c000fca825371797_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80a2bd1c7ee6f8a14deb742cc953684db207b4df4161fa6784decb35567b904d +size 6468 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ccf2315aa760a181c9dcb10f6cf9c47c8d2d30e --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2d6b96e2c759a45741cea8f7cb9dc0595125b6829fa2cf39543ee25731fe99c +size 35309 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b959dd687928d6ecba4c4eb5e480b2686f226552 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/6308d51a4454ddd3509eba3e3b6a11a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2474198348b5dd92de307faee7c18be6597a59b88271019001ef6a5bdf3feb9c +size 5927 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0031a6598431f5e9e93ef85c67167f576d807e1c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/68b20651884fcd557e865537f0803de5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b1fe22c9e2c3fcbffab6904ba136aaafa8062edf6e3e3f3cfbc27a92b60b3ec +size 92916 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92d0fe427284ca1c7f13e6fda6002afbed54fa4f --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:686fe2a738eb1074911c7360501fb1e15aa3397ff0c2667ce9f9f53bcc66d074 +size 28485 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20b442304ea6a2851d90667571678a72e2e6401f --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dc5232b6dbfd318b8a9a724d450390cd366ce45bc86766d74211f0137574f50 +size 35466 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/737abf1e655afd3324b6b3987945d913_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/737abf1e655afd3324b6b3987945d913_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db9615a53fef599f4a142d500b67ed96e3473104 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/737abf1e655afd3324b6b3987945d913_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd8781c70e23d5a51cb928dfab2d6f50160b72f4f7a5a73005a81436251752f8 +size 83881 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e0b1c7e0a47de4f9abf737a8d71d7ac2ef395dc --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/77959075c823bb5169480d7b8ff82a63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fee91a57dbe1605b301816f12e36e6ab1a6f2e25a64218a68ba1d9d984dc682 +size 32802 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae26a1975a6f43cdcfbb1dc41e674a595609f8f3 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:717b928b6b9c91af1f1a247363fa5c8b3b9504c4634bce0f5ce9989d244a9352 +size 23101 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/7d0629aa168bf800e491bcbd1979f262_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/7d0629aa168bf800e491bcbd1979f262_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d0f7a6ce3a1847d3babb6983614fc9371f93d2 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/7d0629aa168bf800e491bcbd1979f262_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ed7265f6dd98d44cc4b82b2b1a3237183d1784027240b818e5f13ce825c206 +size 6597 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c1de7ea5633a112b65cfa7f487483253040b33c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3c0aac4e3e4579282bc9e68ca8b2e413cacb2509efcab8e49a07adeed0e20d8 +size 35494 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acf4b6e328195c491651b5c88d108daf2ce9c495 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e14467740b2570a44379b347a697921_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66ec874711ad02f21d47dae3b76e9696419807c32ae19ceb333d10d533ee9de9 +size 17013 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d017ff9954beccc042addbf7b55bd7cdf2857230 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/7e1f88e0cc7be8060240e12252a833d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ef28407bd8fc072767550eaedbf5dcace17ac617c518158c1bb2a05558dd95 +size 99046 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90e6240a6f9fb7bb49849f9676c05f768e988a1c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b5c73076a56a6138b720f7f3f75c44b8d40e698b4c7a1385558967937808b2 +size 14656 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6891e98eb607d59d12836f191e4f395a8f9fffe5 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/863f4c0af0db9c27290338ff76162c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcefd01bc740bd916e068b8581efe34cd53659290cdc6aaaa501403f63e12796 +size 21103 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b951dad8336c6682e45fd8bc4ee7876a5a2a96f7 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59a4db2d6eec84d9649607ec160132ea46fa9e91863f706e87ab457bb559c866 +size 127938 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7bcaac29b4fc1d52f365b388ca94492a267407b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/8c3eb53c927f55acd19723cfcd0c43b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d17a2fee9435a43b2cf9c83d82b8a786f258a0d7e92a5aa98f20af379c6ceeb +size 62231 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b95e6f9c4b42d9542584c4a56c3a9b6f85b2612d --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dde2261548715e87476b05d12447256a82b5cba6f35661eaa01768f28ca32d6 +size 23388 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/909e1cd5419742a8ea8a95a16a40d849_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/909e1cd5419742a8ea8a95a16a40d849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57bc714b9973c82e366e8266f3f11a3f37e2b88a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/909e1cd5419742a8ea8a95a16a40d849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b34309a663d4cf15b02288d0f8626dcdfa0968de480636a86e0ce2c1bf48f463 +size 13277 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/9507bf8a743ef8e70785692053d75e7c_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/9507bf8a743ef8e70785692053d75e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d0d5aee3f211b0c625f650691ea03577a6161cb --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/9507bf8a743ef8e70785692053d75e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0df43a7b28e02726cd19eab29a091446838783d0911f4a12213813db0a8a2dd +size 16243 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..122a5e4789e3a2124ea49ccf2d483351d8c0c8d7 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/9687bd5e8b62cadba093b0d1b70536cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fab5372cf7d19406c96a48a6cdd06ab01bff883b573401fddc12147329dc39c8 +size 23598 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d73df1b12eab1c3dadd3bcac61e5ebca5a71c576 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e76ec853743541c28da935d72bb3648fe8b09bb5fc92bde54c910a6aafd588f +size 62394 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd7993ef145041781999bafc1a19523648794342 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/9dd03da031e134bfc9ecc730dd5f6583_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90bad789e79c26b159304dfb4d742b3229b4ae97a087cea818c7d2d5fcd96fda +size 23171 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41bba76ab3ad3e51d71d60d553d8d566903c18d1 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04825220a156cafd1cb319de277cbfb4bbf1588e5518b4b9ad6d3cebdaa3d90a +size 31377 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b92e246c815cb0bf86b97582b9bbf1a57dded7cb --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f719fe553d23ec4592cddcd8b6f0f8be7f6a98a211e3190c0313695d12861b8 +size 29524 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1cc8d3f7e055e6fb263348e44050fc31f894c05 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/a04291a026e9ac4a7b644e556a0672b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bcb4a61ac8c513643f0e15785e14789748a88a97fa1a2914733049b2b5823ae +size 70561 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b310ac210c3a7914165adf06403f98576a85c994 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0953d8a48897d2f76d40d07a4f72e9fd2630b3ba8f1e39b9ba5bc493583058ef +size 3635 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c87e6fdeac7d8694eea4ad3f975c504e1ee7200d --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/a48594f1a3fecef5e047a7c3a63b1220_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79c97002c2ec8fa35dda4d92036b9d013de1b4eb31c95e3b4351122aa444125f +size 7870 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a831050509959dc2cbff51ef0ccfd178c7eea7f --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/a83c022a6dac411615bcc38b7cd0d573_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccdf717e48fd7d48014d3c2b19815b43269ef909eec2dfd95d05208c79dfc1a6 +size 32424 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a0d1aba5a43a6e9706296abc7894851b5a05896 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55546a67081ebc6ed22c031bda986b8d7d9c640bbc60b5eb9ab4ff9e426e56bf +size 35618 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..830beb61632ecbc0eb65c691955f9a916567080a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c88e1faa7010a759f63e7d09e24662b5aceeee1d04e4fb761968c4194eb2d48c +size 16104 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b2448ec0a23090beb4402121beeff751_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b2448ec0a23090beb4402121beeff751_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14b2df99e938b4b1c59a920640abc098d8de3879 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b2448ec0a23090beb4402121beeff751_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1233a0c577e08a3ee426e5e4016d3d0d4865f56af47bc1e51d9f37b2b7c838d +size 13645 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b33756b534bb4d9e9ceb8d0af4617768_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b33756b534bb4d9e9ceb8d0af4617768_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..becf19a28eaf12cd8bcb29aa9a54d81f9f53a3f4 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b33756b534bb4d9e9ceb8d0af4617768_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0bef5805136c034362845f57c254c9b3ac1b89a69fb3f51eb8786e96b330eb +size 21250 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..256879ff5fa5b784904800cc5a201ebc4d8b7b66 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:296089245abd01146d676515f56819fcfb5315fa3600a0fdd02e2f98699bf7a1 +size 15356 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b53846f262c6904a1b45abef2e95fbd8_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b53846f262c6904a1b45abef2e95fbd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d793cb0aa4593d2f6d3cfe67a3a1fe5df8e4d580 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b53846f262c6904a1b45abef2e95fbd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8755e96f851533dff05994c05b713991523399b9aff6123275891b5649e595c0 +size 59386 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9eb5a6d78fe9de15f030a94c10c1323451ccac89 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac3386f19e43647e78ac811b4fc50030848dce753ff7e01b68036114bf0fb79 +size 11497 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7f2e8b7767fff7efc19c638e9e0c4f44f20fc49 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45d312ccbb2e52e52cd9add7018627a28c33ebd2419a51406c51c51fd61d8f14 +size 33095 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b82b870697ef3993804c839b298c0f4f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b82b870697ef3993804c839b298c0f4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..938accf18fd6170b78c43c0ae06c262bb925b772 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b82b870697ef3993804c839b298c0f4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e03fa0aaf3647b642f3b5061d249dff9c3629ada13047a8aa1e6c049afc385e +size 20604 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12bd289f7c40bec0c64f8cf7e01af46fe7b0fa2a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1591bd9111b1116d9c183bdecf9adaa1238da130f6d235f0589c87e3ea4560fc +size 21063 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2df816c35c2437108b99c096d26cd827a6f1787 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/b99ddca16383b6f00fc70050d695a235_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d174c31c24b0f2840480a88902e25751930c3fb22d891f0c667c1b1d005fed2 +size 18719 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4189e044b43af67b0177d1eb609c4623e30c0e89 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/bc6f20871b4f01c61470306c304fc9fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b1b3b383c0aaa22fe2288d1ebd199662d0a2dd1a80c2da4442f40b013ee214f +size 27810 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ca49157088467ecbc53bb6f793ee4313d2193d0 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/bd33d5bc49161429f4c7da76529bcd18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092a5c993677bc50e32c283c4f8a9231f76934ca27243047c219383605aef849 +size 44729 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33ca92e7ce46d20030e1cc79587512f5e3e96cce --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/bdee2715697a4142d16a360549fa7c7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb2ac8fcff5cdd6d7885a8e6992f7f3f47e7c95bd16f1ab35e559684b4d8fecd +size 70047 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43c8bebeea461fb991b6bfd080c3475ed300b9ed --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/c0c7f65c51c83fbe595b47326f6b089a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a7c57d328ee0bdab89c12ce72a61dda0cb63db3a85e06f5e2d7631d44f36a6e +size 87080 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62446575a7fb5296d813c6487ba694611b0618bb --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42b58296f8951e78bdd914c4e2b9f6004d84049a9aabe5f6e26f203084920c07 +size 41146 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c175a2e38ffdd690f4f2d067c6963492b979d97c --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/c7111699f84f3e2bc4016b7876f10de6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ed9409905943c1ec3c22ec97fec2622e7293e6992b9b6dfc75e6cebdbeb2460 +size 100683 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9573980e33f30e1836628ec8d003cd26b493bb7e --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:468fbbae1baee4e970d6f8948d827651b923ba0bb823fd64053220dee12d3b9d +size 37481 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/ceb9a4217df4b6e301712b3b88b09c69_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/ceb9a4217df4b6e301712b3b88b09c69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2dd7d1d53059508813e803cc966c4221770514 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/ceb9a4217df4b6e301712b3b88b09c69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:254489a6020d35b1405ada15ca4bb160844b93e984fe1e6534c11708b66a4a30 +size 12792 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/cf93ada09f25903eceb97d1a89649d36_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/cf93ada09f25903eceb97d1a89649d36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6585f65fb33b9054acaf25bec7311d62aceaf0ca --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/cf93ada09f25903eceb97d1a89649d36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bda92fd3756958852e5249134475d00e43d8350913b9cb202cbf73e22ccc6f31 +size 28848 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79e7e3d7f73a1b9c6e32ecad632de4b1d72d2079 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/d3162014eae89d17bf0117dabb0c8796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf12389814bb19ac0c761346770fdbcf098bc4a036702598780637fc850f90e8 +size 28767 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..241e24c3fa715eed1f9f9f8ed89d817408310923 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68146e7e35a50778701e0b982ff52c637240d3680e7dac978d597f6c5cdb67f3 +size 16462 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..119067c4950e8d07cf138c71f25a1a8252de10e4 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15538ec6a3458c232e6704ee3703645eff4526701b4a2bc6c5027a9fa88f7b98 +size 27110 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f297dfd184f8725a9cec3e984a4ff01201efa5de --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe0db029f09f0a685130cb4b27a3e52f76365f09527bdff2c87494253c4e0246 +size 31260 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..308a0b9ca15baec1f1645a9fb7d3169ce766f2e8 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/defe20e5056d0c3552de2d50ce88c5cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97342b08db79373249e7a03387609309e77542889527c016f34d2658c719f084 +size 92454 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95073a0bb1e4ff3163fd3e023be93e989371e324 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/df803281854ce2cbde7019b5aeefd8cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89004cefc8af0481aaac7b88dbd7aec90fd1c7208199f86cde3762023dedef87 +size 62346 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1590d3e01b100dc6974ec57918d9cab1fe8cb8f4 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/e33485d4301404e5a43a61e4cfb96fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8735eaa014f916dd17925334ffd567d4159bb79732b1d3ccb1e9499c7b890cc5 +size 16878 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0e758d17673d9843a9f2c35ce8a6240adac6cfe --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/e69b9188aa2c14ec6b21c83f711fef65_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebce6a1bb8bc3ed66625a19a6b662353f232890638dd528bfe7bbc173531deae +size 13954 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0a291f6b7cd4ee00c0b47eefe75688291267ff1 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2915a834f02067050d0fb66ac30a29fd0d0b01a7447e56087b71199de3103c9 +size 10376 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15e1669418c94ec16641c8b7b721b79bb56c978a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/e776395ba1d4a6d568f08b406d784abd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f9ccbaed7db750e1c3e58813c5407503124142b5598734f1f61b3b6258794f6 +size 16636 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bee1507949213b574ad2783e1e951e4dbe1a5cba --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/e8e818455bb0d1a6153299a388b94868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f05f6ba0802e61fc3663b8adfb8b5997fab9991ec9be4032f5465850635dac5c +size 123322 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..144f514b186c0898751f08ddb37af6c784bd0b2e --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cabdb46e633c8f451c7758fa67792f23e8242081f9dd9560978ff2c1c1851ef5 +size 28800 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..081e8272cd3fd21665f77aa50565c5dbfe276739 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c69f2b13b8e793d00faeedee19187c53438bb781ec8d01ec2fec75675610c1e9 +size 40237 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c6ad6bc0a7058e14acaf5f54e5af824c71adc24 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d0f8f00e1bb0153268bdbb2f4cb1499807b9a47d2cdd84272ec0a9e41e53797 +size 20693 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8faf8bb7ef6ac76e28b759e7853e05cec95504a --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1345b41f30ce4ceecb70a7708a0ea136f60f1fe34b5a8336f08a03c01ed340d2 +size 31038 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/f3a012f283609ae9109e6471db1a9621_img.jpg b/marked/G/T-REC-G.9904-201210-I_PDF-E/f3a012f283609ae9109e6471db1a9621_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9113c6d9424d4de5d331e73fd1f26acaffde4e5b --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/f3a012f283609ae9109e6471db1a9621_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be35d001c949962f071fbbc6aab581394f3b0846294a4d872b6978ff8fee72ef +size 11919 diff --git a/marked/G/T-REC-G.9904-201210-I_PDF-E/raw.md b/marked/G/T-REC-G.9904-201210-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..94848fb5ce77a5b635d676a51f8938f62dac0dc8 --- /dev/null +++ b/marked/G/T-REC-G.9904-201210-I_PDF-E/raw.md @@ -0,0 +1,7454 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.9904** + +(10/2012) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Access networks – In premises networks + +--- + +**Narrowband orthogonal frequency division +multiplexing power line communication +transceivers for PRIME networks** + +Recommendation ITU-T G.9904 + +# 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 | +| In premises networks | G.9900–G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +## Recommendation ITU-T G.9904 + +# Narrowband orthogonal frequency division multiplexing power line communication transceivers for PRIME networks + +# Summary + +Recommendation ITU-T G.9904 contains the physical layer (PHY) and data link layer (DLL) specification for PRIME narrowband orthogonal frequency division multiplexing (OFDM) power line communication transceivers for communications via alternating current and direct current electric power lines over frequencies in the CENELEC A band. + +This Recommendation uses material from Recommendations ITU-T G.9955, ITU-T G.9956 and ITU-T G.9956 Amendment 1; specifically using material from Annex B of ITU-T G.9955, Annex B of ITU-T G.9956 and ITU-T G.9956 Amendment 1. New technical material has not been introduced in this version. + +The control parameters that determine spectral content, power spectral density (PSD) mask requirements and the set of tools to support the reduction of the transmit PSD can be found in Recommendation ITU-T G.9901. + +## History + +| Edition | Recommendation | Approval | Study Group | +|---------|----------------|------------|-------------| +| 1.0 | ITU-T G.9904 | 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 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 ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 6 | +| 6 | General description..... | 6 | +| 6.1 | General description of the architecture..... | 6 | +| 7 | Physical layer..... | 7 | +| 7.1 | Introduction ..... | 7 | +| 7.2 | Overview ..... | 7 | +| 7.3 | PHY parameters..... | 8 | +| 7.4 | Preamble, header and payload structure ..... | 8 | +| 7.5 | Convolutional encoder..... | 11 | +| 7.6 | Scrambler..... | 12 | +| 7.7 | Interleaver..... | 12 | +| 7.8 | Modulation ..... | 13 | +| 7.9 | Electrical specification of the transmitter..... | 15 | +| 7.10 | PHY service specification ..... | 16 | +| 8 | Data link layer specifications..... | 30 | +| 8.1 | Overview ..... | 30 | +| 8.2 | Addressing..... | 31 | +| 8.3 | MAC functional description ..... | 34 | +| 8.4 | MAC PDU format ..... | 54 | +| 8.5 | MAC service access point ..... | 77 | +| 8.6 | MAC procedures ..... | 95 | +| 8.7 | Automatic repeat request (ARQ)..... | 110 | +| 9 | Convergence layer ..... | 114 | +| 9.1 | Overview ..... | 114 | +| 9.2 | Common part convergence sublayer (CPCS)..... | 114 | +| 9.3 | NULL specific service convergence sublayer (NULL SSCS) ..... | 116 | +| 9.4 | IPv4 specific service convergence sublayer (IPv4 SSCS) ..... | 117 | +| 9.5 | IEC 61334-4-32 specific service convergence sublayer (IEC 61334-4-32 SSCS) ..... | 129 | +| 9.6 | IPv6 service-specific convergence sublayer (IPv6 SSCS) ..... | 133 | + +| | Page | +|---------------------------------------------|-------------| +| 10 Management plane ..... | 148 | +| 10.1 Introduction ..... | 148 | +| 10.2 Node management ..... | 149 | +| 10.3 Firmware upgrade ..... | 162 | +| 10.4 Management interface description ..... | 179 | +| 10.5 List of mandatory PIB attributes ..... | 184 | +| Annex A – EVM and SNR calculation ..... | 187 | +| Annex B – MAC layer constants ..... | 188 | +| Annex C – Convergence layer constants ..... | 189 | +| Appendix I – Examples of CRC ..... | 190 | +| Appendix II – Interleaving matrices ..... | 191 | + +# Narrowband orthogonal frequency division multiplexing power line communication transceivers for PRIME networks + +# 1 Scope + +This Recommendation contains the physical layer (PHY) and data link layer (DLL) specification for PRIME narrowband orthogonal frequency division multiplexing (OFDM) power line communication transceivers for communications via alternating current and direct current electric power lines over frequencies below 500 kHz. This Recommendation supports indoor and outdoor communications over low-voltage lines, medium-voltage lines, through transformer low-voltage to medium-voltage and through transformer medium-voltage to low-voltage power lines in both urban and in long distance rural communications. This Recommendation addresses grid to utility meter applications, advanced metering infrastructure (AMI), and other 'Smart Grid' applications such as the charging of electric vehicles, home automation and home area networking (HAN) communications scenarios. + +This Recommendation removes the control parameters that determine spectral content, power spectral density (PSD) mask requirements, and the set of tools to support reduction of the transmit PSD, all of which have been moved to [ITU-T G.9901]. + +# 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.9901] Recommendation ITU-T G.9901 (2012), *Narrowband orthogonal frequency division multiplexing power line communication transceivers – Power spectral density specification*. +- [IEC 61334-4-1] IEC 61334-4-1 Ed.1996, *Distribution automation using distribution line carrier systems – Part 4: Data communication protocols – Section 1: Reference model of the communication system*. +- [IEC 61334-4-32] IEC 61334-4-32 Ed.1996, *Distribution automation using distribution line carrier systems – Part 4: Data communication protocols – Section 32: Data link layer – Logical link control (LLC)*. +- [IEC 61334-4-511] IEC 61334-4-511 Ed. 2000, *Distribution automation using distribution line carrier systems – Part 4-511: Data communication protocols – Systems management – CIASE protocol*. +- [IEC 61334-4-512] IEC 61334-4-512, Ed. 1.0:2001, *Distribution automation using distribution line carrier systems – Part 4-512: Data communication protocols – System management using profile 61334-5-1 – Management Information Base (MIB)*. +- [IEEE 802-2001] IEEE Std 802-2001 (R2007), *IEEE Standard for Local and Metropolitan Area Networks. Overview and Architecture*. +- [IETF RFC 768] IETF RFC 768 (1980), *User Datagram Protocol (UDP)*. + +- [IETF RFC 791] IETF RFC 791 (1981), *Internet Protocol, DARPA Internet Program, Protocol Specification*. +- [IETF RFC 793] IETF RFC 793 (1981), *Transmission Control Protocol (TCP)*. +- [IETF RFC 1144] IETF RFC 1144 (1990), *Compressing TCP/IP Headers for Low-Speed Serial Links*. +- [IETF RFC 2131] IETF RFC 2131 (1997), *Dynamic Host Configuration Protocol (DHCP)*. +- [IETF RFC 2460] IETF RFC 2460 (1998), *Internet Protocol, Version 6 (IPv6) Specification*. +- [IETF RFC 2462] IETF RFC 2462 (1998), *IPv6 Stateless Address Autoconfiguration*. +- [IETF RFC 2464] IETF RFC 2464 (1998), *Transmission of IPv6 Packets over Ethernet Networks*. +- [IETF RFC 3022] IETF RFC 3022 (2001), *Traditional IP Network Address Translator (Traditional NAT)*. +- [IETF RFC 3315] IETF RFC 3315 (2003), *Dynamic Host Configuration Protocol for IPv6 (DHCPv6)*. +- [IETF RFC 4291] IETF RFC 4291 (2006), *IP Version 6 Addressing Architecture*. +- [IETF RFC 4862] IETF RFC 4862 (2007), *Ipv6 Stateless Address Autoconfiguration*. +- [IETF RFC 6282] IETF RFC 6282 (2011), *Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks*. +- [EN 50065-1] CENELEC EN 50065-1 (2011), *Signalling on low-voltage electrical installations in the frequency range 3 kHz to 148,5 kHz – Part 1: General requirements, frequency bands and electromagnetic disturbances*. +- [PUB 197] NIST FIPS PUB 197 (2001), *Advanced Encryption Standard (AES)*. +- [SP 800-38A] NIST SP 800-38A (2001), *Recommendation for Block Cipher Modes of Operation. Methods and Techniques*. +- [SP 800-57] NIST SP 800-57 (2007), *Recommendation for Key Management – Part 1: General (Revised)*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +- 3.2.1 base node:** The master node which controls and manages the resources of a subnetwork. +- 3.2.2 beacon slot:** The location of the beacon PDU within a frame. +- 3.2.3 destination node:** A node that receives a frame. +- 3.2.4 downlink:** Data travelling in the direction from the base node towards the service nodes. +- 3.2.5 level (PHY layer):** When used in the physical layer (PHY) context, it implies the transmit power level. +- 3.2.6 level (MAC layer):** When used in the medium access control (MAC) context, it implies the position of the reference device in switching hierarchy. + +- 3.2.7 MAC frame:** A composite unit of abstraction of time for channel usage. A MAC frame is comprised of one or more beacons, one SCP, and zero or one CFP. The transmission of the beacon by the base node acts as a delimiter for the MAC frame. +- 3.2.8 neighbour node:** Node A is neighbour node of node B if A can directly transmit to and receive from B. +- 3.2.9 node:** Any one element of a subnetwork which is able to transmit to and receive from other subnetwork elements. +- 3.2.10 PHY frame:** The set of OFDM symbols and preamble which constitute a single PHY layer protocol data unit (PPDU). +- 3.2.11 preamble:** The initial part of a PHY frame, used for synchronization purposes. +- 3.2.12 registration:** The process by which a service node is accepted as member of a subnetwork and allocated an LNID. +- 3.2.13 service node:** Any one node of a subnetwork which is not a base node. +- 3.2.14 source node:** A node that sends a frame. +- 3.2.15 subnetwork:** A set of elements that can communicate by complying with this Recommendation and share a single base node. +- 3.2.16 subnetwork address:** The property that universally identifies a subnetwork. It is its base node EUI-48 address. +- 3.2.17 switching:** Providing connectivity between nodes that are not neighbour nodes. +- 3.2.18 unregistration:** The process by which a service node leaves a subnetwork. +- 3.2.19 uplink:** Data travelling in the direction from the service node towards the base node. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-----------|----------------------------------------------| +| AC | Alternating Current | +| ADC | Analogue-to-Digital Converter | +| AES | Advanced Encryption Standard | +| AMM | Advanced Meter Management | +| ARQ | Automatic Repeat request | +| ATM | Asynchronous Transfer Mode | +| BER | Bit Error Rate | +| BPDU | Beacon PDU | +| BPSK | Binary Phase Shift Keying | +| BSI | Beacon Slot Information | +| CFP | Contention-Free Period | +| CID | Connection Identifier | +| CL | Convergence Layer | +| CIMTUSize | Convergence layer Maximum Transmit Unit Size | +| CPCS | Common Part Convergence Sublayer | + +| | | +|---------|---------------------------------------------------| +| CRC | Cyclic Redundancy Check | +| CSMA-CA | Carrier Sense Multiple Access-Collision Avoidance | +| D8PSK | Differential Eight-Phase Shift Keying | +| DBPSK | Differential Binary Phase Shift Keying | +| DHCP | Dynamic Host Configuration Protocol | +| DPSK | Differential Phase Shift Keying (general) | +| DQPSK | Differential Quaternary Phase Shift Keying | +| DSK | Device Secret Key | +| ECB | Electronic Code Book | +| EMA | Exponential Moving Average | +| ENOB | Effective Number Of Bits | +| EUI-48 | 48-bit Extended Unique Identifier | +| EVM | Error Vector Magnitude | +| FCS | Frame Check Sequence | +| FEC | Forward Error Correction | +| FFT | Fast Fourier Transform | +| FU | Firmware Upgrade | +| GK | Generation Key | +| GPDU | Generic MAC PDU | +| HCS | Header Check Sum | +| IFFT | Inverse Fast Fourier Transform | +| IGMP | Internet Group Management Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| KDIV | Key Diversifier | +| LCID | Local Connection Identifier | +| LFSR | Linear Feedback Shift Register | +| LLC | Logical Link Control | +| LNID | Local Node Identifier | +| LSID | Local Switch Identifier | +| LWK | Local Working Key | +| MAC | Medium Access Control | +| MK | Master Key | +| MLME | MAC Layer Management Entity | +| MOL | Maximal Output Level | +| MPDU | MAC Protocol Data Unit | +| MSB | Most Significant Bit | + +| | | +|-------|-----------------------------------------------------------| +| MSDU | MAC Service Data Unit | +| MSPS | Million Samples Per Second | +| MTU | Maximum Transmission Unit | +| NAT | Network Address Translation | +| NID | Node Identifier | +| NSK | Network Secret Key | +| OFDM | Orthogonal Frequency Division Multiplexing | +| PDU | Protocol Data Unit | +| PHY | Physical Layer | +| PIB | PLC Information Base | +| PLC | Power Line Communications | +| PLME | PHY Layer Management Entity | +| PNPDU | Promotion Needed PDU | +| PPDU | PHY Protocol Data Unit | +| ppm | Parts per million | +| PRBS | Pseudo-Random Binary Sequence | +| PSD | Power Spectral Density | +| PSDU | PHY Service Data Unit | +| QoS | Quality of Service | +| SAP | Service Access Point | +| SAR | Segmentation And Reassembly | +| SCP | Shared-Contention Period | +| SCRC | Secure CRC | +| SDU | Service Data Unit | +| SEC | Security | +| SID | Switch Identifier | +| SNA | Subnetwork Address | +| SNK | Subnetwork Key (corresponds to either REG.SNK or SEC.SNK) | +| SNR | Signal to Noise Ratio | +| SP | Security Profile | +| SSCS | Service Specific Convergence Sublayer | +| SWK | Subnetwork Working Key | +| TCP | Transmission Control Protocol | +| TOS | Type Of Service | +| UI | Unique Identifier | +| USK | Unique Secret Key | +| VJ | Van Jacobson | + +# 5 Conventions + +Binary numbers are indicated by the prefix '0b' followed by the binary digits, e.g., '0b0101'. +Hexadecimal numbers are indicated by the prefix '0x', e.g., '0x0F'. + +Mandatory requirements are indicated with 'shall' in the main body of this Recommendation. + +Optional requirements are clearly indicated. If an option is incorporated in an implementation, it shall be applied as specified in this Recommendation. + +*roof* (.) denotes rounding to the closest higher or equal integer. + +*floor* (.) denotes rounding to the closest lower or equal integer. + +A mod B denotes the remainder (from 0, 1, ..., B-1) obtained when an integer A is divided by an integer B. + +# 6 General description + +This Recommendation provides a solution for power line communications in the bands specified by the main body and Annex C of [ITU-T G.9901] using OFDM modulation. This solution focuses on providing a very robust communication channel in applications such as advanced meter management (AMM). The target transmission rate is in the order of tens of kilobits per second. + +## 6.1 General description of the architecture + +Figure 6-1 depicts the communication layers and the scope of this Recommendation. + +![Figure 6-1: Reference model of ITU-T G.9904 protocol layers. The diagram shows two main planes: Control and Data Plane, and Management Plane. The Control and Data Plane contains three layers: Convergence (CL) Layer, Media Access Control (MAC) Layer, and Physical (PHY) Layer. The Management Plane contains two entities: MAC Layer Mgmt. Entity (MLME) and PHY Layer Mgmt. Entity (PLME). The CL Layer is connected to the MAC Layer, which is connected to the PHY Layer. The MAC Layer is connected to the MLME via the MLME-SAP. The PHY Layer is connected to the PLME via the PLME-SAP.](0019f09403376d6444ee323591fa2e98_img.jpg) + +``` + +graph LR + subgraph CDP [Control and Data Plane] + CL[Convergence (CL) Layer] + MAC[Media Access Control (MAC) Layer] + PHY[Physical (PHY) Layer] + CL --- MAC + MAC --- PHY + end + subgraph MP [Management Plane] + MLME[MAC Layer Mgmt. Entity (MLME)] + PLME[PHY Layer Mgmt. Entity (PLME)] + end + MAC <--> |MLME-SAP| MLME + PHY <--> |PLME-SAP| PLME + +``` + +Figure 6-1: Reference model of ITU-T G.9904 protocol layers. The diagram shows two main planes: Control and Data Plane, and Management Plane. The Control and Data Plane contains three layers: Convergence (CL) Layer, Media Access Control (MAC) Layer, and Physical (PHY) Layer. The Management Plane contains two entities: MAC Layer Mgmt. Entity (MLME) and PHY Layer Mgmt. Entity (PLME). The CL Layer is connected to the MAC Layer, which is connected to the PHY Layer. The MAC Layer is connected to the MLME via the MLME-SAP. The PHY Layer is connected to the PLME via the PLME-SAP. + +**Figure 6-1 – Reference model of ITU-T G.9904 protocol layers** + +The convergence layer (CL) classifies traffic associating it with its proper MAC connection. This layer performs the mapping of any kind of traffic to be properly included in MAC service data units (MSDUs). It may also include compression functions. Several SSCSs are defined to accommodate different kinds of traffic into MSDUs. + +The MAC layer provides core MAC functionalities of system access, bandwidth allocation, connection establishment/maintenance and topology resolution. + +The PHY layer transmits and receives MPDUs between neighbour nodes using orthogonal frequency division multiplexing (OFDM). OFDM is chosen as the modulation technique mainly because of the following: + +- its inherent adaptability in the presence of frequency selective channels (which are quite common but unpredictable, due to narrowband interference or unintentional jamming); +- its robustness to impulsive noise, resulting from extended symbol duration and use of FEC; + +- its capacity for achieving high spectral efficiencies with simple transceiver implementations. + +# 7 Physical layer + +## 7.1 Introduction + +This clause specifies the physical layer (PHY) entity for an OFDM based PLC communications scheme in the bands specified in the main body and Annex C of [ITU-T G.9901]. + +Differential modulation is used with three possible constellations: DBPSK, DQPSK or D8PSK. Thus, theoretical uncoded speeds of around 47 kbit/s, 94 kbit/s, and 141 kbit/s (without a cyclic prefix overhead) could be obtained. + +An additive scrambler is used to avoid the occurrence of long sequences of identical bits. + +Finally, rate $\frac{1}{2}$ convolutional coding will be used along with bit interleaving. This can be disabled by higher layers if the channel is good enough and higher throughputs are needed. + +## 7.2 Overview + +Figure 7-1 shows the PHY layer transmitter block diagram. + +On the transmitter side, the PHY layer receives an MPDU from the MAC layer and generates a PHY frame. If decided by higher layers, the PPDU after the CRC block is convolutionally encoded and then interleaved (however, it will always be scrambled). The output is differentially modulated using a DBPSK, DQPSK or D8PSK scheme. The next step is OFDM, which comprises the inverse fast Fourier transform (IFFT) block and the cyclic prefix generator. + +![Figure 7-1: PHY layer transmitter block diagram. The diagram shows a sequence of seven blocks connected by arrows: CRC, convolutional encoder, scrambler, interleaver, sub-carrier modulator, IFFT, and cyclic prefix. A label 'G.9955(11)_FB-2' is located at the bottom right of the diagram.](2e399449b7f62d40167a65ca88888917_img.jpg) + +``` + +graph LR + Input(( )) --> CRC[CRC] + CRC --> CE[convolutional encoder] + CE --> S[scrambler] + S --> I[interleaver] + I --> SM[sub-carrier modulator] + SM --> IFFT[IFFT] + IFFT --> CP[cyclic prefix] + CP --> Output(( )) + +``` + +Figure 7-1: PHY layer transmitter block diagram. The diagram shows a sequence of seven blocks connected by arrows: CRC, convolutional encoder, scrambler, interleaver, sub-carrier modulator, IFFT, and cyclic prefix. A label 'G.9955(11)\_FB-2' is located at the bottom right of the diagram. + +Figure 7-1 – PHY layer transmitter + +The structure of the PHY frame is shown in Figure 7-2. Each PHY frame starts with a preamble lasting 2.048 ms, followed by a number of OFDM symbols, each lasting 2.24 ms. The first two OFDM symbols carry the PHY frame header. The PHY header is also generated as described in clause 7.4. The remaining $M$ OFDM symbols carry payload, generated as described in clause 7.4. The value of $M$ is signalled in the PHY header, and is at most equal to 63. + +![Figure 7-2: PHY frame format diagram. The diagram shows a frame structure with three main sections: PREAMBLE, HEADER, and PAYLOAD. The PREAMBLE section is labeled with a duration of 2.048ms. The HEADER section is labeled with a duration of 4.48ms and contains '2 symbols'. The PAYLOAD section is labeled with a duration of Mx2.24ms and contains 'M symbols'.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +| PREAMBLE | HEADER | PAYLOAD | +|----------|---------------------|-----------------------------------------| +| 2.048ms | 4.48ms
2 symbols | $M \times 2.24\text{ms}$
$M$ symbols | + +Figure 7-2: PHY frame format diagram. The diagram shows a frame structure with three main sections: PREAMBLE, HEADER, and PAYLOAD. The PREAMBLE section is labeled with a duration of 2.048ms. The HEADER section is labeled with a duration of 4.48ms and contains '2 symbols'. The PAYLOAD section is labeled with a duration of Mx2.24ms and contains 'M symbols'. + +Figure 7-2 – PHY frame format + +## 7.3 PHY parameters + +PHY parameters are defined in clause C.2 of [ITU-T G.9901]. + +There are parameters which depend on the modulation of each OFDM subcarrier. + +Table 7-1 shows the PHY data rate during payload transmission, and the maximum MSDU length for various modulation and coding combinations. + +**Table 7-1 – PHY data rates for each modulation with the FEC on and off** + +| | DBPSK | | DQPSK | | D8PSK | | +|------------------------------------------------|-------|------|-------|-------|-------|-------| +| | On | Off | On | Off | On | Off | +| Convolutional code (1/2) | | | | | | | +| Information bits per subcarrier, $N_{BPSC}$ | 0.5 | 1 | 1 | 2 | 1.5 | 3 | +| Information bits per OFDM symbol, $N_{BPS}$ | 48 | 96 | 96 | 192 | 144 | 288 | +| Raw data rate (kbit/s approx) | 21.4 | 42.9 | 42.9 | 85.7 | 64.3 | 128.6 | +| Maximum MSDU length (in bits) with 63 symbols | 3016 | 6048 | 6040 | 12096 | 9064 | 18144 | +| Maximum MSDU length (in bytes) with 63 symbols | 377 | 756 | 755 | 1512 | 1133 | 2268 | + +Table 7-2 shows the modulation and coding scheme and the size of the header portion of the PHY frame + +**Table 7-2 – Header parameters** + +| | DBPSK | +|---------------------------------------------|-------| +| Convolutional code (1/2) | On | +| Information bits per subcarrier, $N_{BPSC}$ | 0.5 | +| Information bits per OFDM symbol, $N_{BPS}$ | 42 | + +It is strongly recommended that all frequencies used to generate the OFDM transmit signal come from one single frequency reference. The system clock shall have a maximum tolerance of $\pm 50$ ppm, including ageing. + +## 7.4 Preamble, header and payload structure + +### 7.4.1 Preamble + +The preamble is used at the beginning of every PPDU for synchronization purposes. In order to provide a maximum of energy, a constant envelope signal is used instead of OFDM symbols. There is also a need for the preamble to have frequency agility that will allow synchronization in the presence of frequency selective attenuation and of course, excellent aperiodic autocorrelation properties are mandatory. A linear chirp signal meets all the above requirements. The waveform of the preamble is defined as: + +$$S_{CH}(t) = A \cdot rect(t/T) \cdot \cos\left[2\pi\left(f_0 t + 1/2\mu t^2\right)\right]$$ + +where $T, f_0, f_s$ , and $\mu$ are defined in clause C.3 of [ITU-T G.9901]. + +$rect(\cdot)$ function is defined as: + +$$\begin{aligned} rect(t) &= 1, & 0 < t < 1 \\ rect(t) &= 0, & otherwise \end{aligned}$$ + +### 7.4.2 Pilot structure + +The two OFDM symbols comprising the PHY header shall contain 13 pilot subcarriers which can be used to estimate the sampling start error and the sampling frequency offset. + +For subsequent OFDM symbols, one pilot subcarrier is used to provide a phase reference for frequency domain DPSK demodulation. + +Pilot subcarrier frequency allocation is shown in Figures 7-3 and 7-4, where $P_{i}$ is the $i$ -th pilot subcarrier and $D_{j}$ is the $j$ -th data subcarrier. + +![Figure 7-3 – Pilot and data subcarrier allocation (OFDM symbols vs subcarriers)](177e8bc1c595b7fe3461d9919f87e044_img.jpg) + +A grid diagram showing Frequency on the vertical axis (from 1 to 97) and Time on the horizontal axis. The grid cells represent subcarriers. Legend indicates white squares are 'Data subcarrier' and yellow squares are 'Pilot subcarrier'. At frequency 1, there is a row of pilot subcarriers with binary values (000000100010011000101111010110110). At frequency 9, a pilot subcarrier is marked with '01'. At frequency 89, a pilot subcarrier is marked with '10'. At frequency 97, a pilot subcarrier is marked with '00'. + +**Figure 7-3 – Pilot and data subcarrier allocation (OFDM symbols vs subcarriers)** + +Figure 7-3 – Pilot and data subcarrier allocation (OFDM symbols vs subcarriers) + +![Figure 7-4 – Pilot and data subcarrier allocation inside the header](0a8d173734e4e46c344178e8d21bcbc3_img.jpg) + +A linear axis labeled 'Sub-carrier number (FFT 512)' showing specific subcarrier indices: 86, 87, 93, 94, 95, 101, 102, 103, 109, 110, 111, 117, 118, 119, 125, 126, 127, 133, 134, 135, 141, 142, 143, 149, 150, 151, 157, 158, 159, 165, 166, 167, 173, 174, 175, 181, 182. Above the axis, subcarriers are labeled as $P_{1}, D_{1}, D_{7}, P_{2}, D_{8}, D_{14}, P_{3}, D_{15}, D_{21}, P_{4}, D_{22}, D_{28}, P_{5}, D_{29}, D_{35}, P_{6}, D_{36}, D_{42}, P_{7}, D_{43}, D_{49}, P_{8}, D_{50}, D_{56}, P_{9}, D_{57}, D_{63}, P_{10}, D_{64}, D_{70}, P_{11}, D_{71}, D_{77}, P_{12}, D_{78}, D_{84}, P_{13}$ . + +G.9955(11)\_FB-5 + +**Figure 7-4 – Pilot and data subcarrier frequency allocation inside the header** + +Figure 7-4 – Pilot and data subcarrier allocation inside the header + +Pilot subcarriers shall be BPSK modulated by a pseudo-random binary sequence (PRBS) to prevent the generation of spectral lines. The phase of the pilot subcarriers is controlled by the PRBS sequence which is a cyclic extension of the 127 bit sequence given by: + +$Pref_{0..126} =$ + {0,0,0,0,0,1,1,1,0,1,1,1,1,0,0,1,0,1,1,0,0,1,0,0,1,0,0,0,0,0,0,1,0,0,0,1,0,0,1,1,0,0,0,1,0,1,1,1,0,1,0,1,1,0,1,1,0,0,0,0,0,1,1,0,0,1,1,0,1,0,1,0,1,0,0,1,1,1,0,0,1,1,1,1,0,1,1,0,1,1,0,1,0,0,0,0,1,0,1,0,1,0,1,0,1,1,1,1,1,0,1,0,0,1,0,1,0,0,0,1,1,0,1,1,1,1,1,1,1} + +**Rec. ITU-T G.9904 (10/2012)**      9 + +where '1' means 180° phase shift and '0' means 0° phase shift. One bit of the sequence will be used per pilot subcarrier, starting with the first pilot subcarrier in the first OFDM symbol, then the next pilot subcarrier, and so on. The same process is used for the second OFDM symbol. For subsequent OFDM symbols, one element of the sequence is used for the pilot subcarrier (see Figure 7-3). + +The PRBS sequence can be generated by the scrambler defined in Figure 7-5 when the "all-ones" initial state is used. + +![Figure 7-5: LFSR for use in pilot sequence generation. The diagram shows a linear feedback shift register (LFSR) with two shift register stages. The first stage has three cells, all containing '1'. The second stage has four cells, all containing '1'. The output of the last cell in the second stage is fed back through an XOR gate (represented by a circle with a cross) and then back into the first cell of the first stage. The output of the last cell in the second stage is also labeled as 'Output Sequence'. A small text 'G.9955(11)_FB-6' is present below the diagram.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) + +Figure 7-5: LFSR for use in pilot sequence generation. The diagram shows a linear feedback shift register (LFSR) with two shift register stages. The first stage has three cells, all containing '1'. The second stage has four cells, all containing '1'. The output of the last cell in the second stage is fed back through an XOR gate (represented by a circle with a cross) and then back into the first cell of the first stage. The output of the last cell in the second stage is also labeled as 'Output Sequence'. A small text 'G.9955(11)\_FB-6' is present below the diagram. + +Figure 7-5 – LFSR for use in pilot sequence generation + +The loading of the PRBS sequence shall be initiated at the start of every PPDU, just after the preamble. + +### 7.4.3 PHY header and payload + +The PHY header is composed of two OFDM symbols which are always sent using DBPSK modulation and FEC (convolutional coding) 'On'. However the payload is DBPSK, DQPSK or D8PSK modulated, depending on the configuration by the MAC layer. The MAC layer selects the modulation scheme, e.g., using information from errors in previous transmissions to the same receiver(s), or by using the SNR feedback. Thus, the system will then configure itself dynamically to provide the best compromise between throughput and efficiency in the communication. This includes deciding whether or not FEC (convolutional coding) is used. + +The first two OFDM symbols in the PPDU corresponding to the PHY header are composed of 84 data subcarriers and 13 pilot subcarriers. After the PHY header, each OFDM symbol in the payload carries 96 data subcarriers and one pilot subcarrier. Each data subcarrier carries 1, 2 or 3 bits. + +The bit stream from each field shall be sent MSB first. See Figure 7-6. + +![Figure 7-6: PPDU: PHY header and payload (bits transmitted before encoding). The diagram shows a table representing the structure of a PPDU. The table is divided into two main sections: HEADER and PAYLOAD. The HEADER section includes fields: PROTOCOL (4 bits), LEN (6 bits), PAD_LEN (6 bits), MAC_H (54 bits), CRC_Ctrl (8 bits), and FLUSHING_H (6 bits). The PAYLOAD section includes fields: MSDU (8xM bits), FLUSHING_D (8 bits), and PAD (8 bits). The total number of bits is indicated as 'bits' at the bottom right. A small text 'G.9955(11)_FB-7' is present below the diagram.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +| HEADER | | | | | | PAYLOAD | | | | +|----------|-----|---------|-------|----------|------------|---------|------------|-----|------| +| PROTOCOL | LEN | PAD_LEN | MAC_H | CRC_Ctrl | FLUSHING_H | MSDU | FLUSHING_D | PAD | | +| 4 | 6 | 6 | 54 | 8 | 6 | 8xM | 8 | 8 | bits | + +Figure 7-6: PPDU: PHY header and payload (bits transmitted before encoding). The diagram shows a table representing the structure of a PPDU. The table is divided into two main sections: HEADER and PAYLOAD. The HEADER section includes fields: PROTOCOL (4 bits), LEN (6 bits), PAD\_LEN (6 bits), MAC\_H (54 bits), CRC\_Ctrl (8 bits), and FLUSHING\_H (6 bits). The PAYLOAD section includes fields: MSDU (8xM bits), FLUSHING\_D (8 bits), and PAD (8 bits). The total number of bits is indicated as 'bits' at the bottom right. A small text 'G.9955(11)\_FB-7' is present below the diagram. + +Figure 7-6 – PPDU: PHY header and payload (bits transmitted before encoding) + +PHY HEADER: Each PPDU contains both PHY and MAC header information. It is composed of the following fields: + +- PROTOCOL: contains the transmission scheme of the payload. Added by the PHY layer. + +| | | | | | | | | | | | | | | | | +|-------|-------|-------|-----|---------|---------|---------|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | +| DBPSK | DQPSK | D8PSK | RES | DBPSK_F | DQPSK_F | D8PSK_F | RES | RES | RES | RES | RES | RES | RES | RES | RES | + +Figure 7-7 – "PROTOCOL" field of the PPDU + +- Where RES means "reserved" and the suffix "\_F" means FEC is 'On'. +- LEN: defines the length of the payload (after coding) in OFDM symbols. Added by the PHY layer. +- PAD\_LEN: defines the length of the PAD field (before coding) in bytes. Added by the PHY layer. +- MAC\_H: MAC layer header. It is included inside the header symbols to protect the information contained. The MAC header is generated by the MAC layer and only the first 54 bits of the MAC header are embedded in the PHY header. +- CRC\_Ctrl: the CRC\_Ctrl( $m$ ), $m = 0..7$ , contains the CRC checksum over PROTOCOL, LEN, PAD\_LEN and MAC\_H field (PD\_Ctrl). The polynomial form of PD\_Ctrl is expressed as follows: + +$$\sum_{m=0}^{69} PD_{Ctrl}(m)x^m$$ + +The checksum is calculated as follows: the remainder of the division of PD\_Ctrl by the polynomial $x^8 + x^2 + x + 1$ forms CRC\_Ctrl( $m$ ), where CRC\_Ctrl(0) is the LSB. The generator polynomial is the well-known CRC-8-ATM. Some examples are shown in Appendix I. + +- FLUSHING\_H: flushing bits needed for convolutional decoding. All bits in this field are set to zero to reset the convolutional encoder. Added by the PHY layer. + +#### PAYLOAD: + +- MSDU: uncoded MAC layer service data unit. +- FLUSHING\_P: flushing bits needed for convolutional decoding. All bits in this field are set to zero to reset the convolutional encoder. This field only exists when FEC is 'On'. +- PAD: In order to ensure that the number of (coded) bits generated in the payload fills an integer number of OFDM symbols, pad bits shall be added to the payload before encoding. All pad bits shall be set to zero. + +## 7.5 Convolutional encoder + +The uncoded PHY stream can be convolutionally encoded to form the encoded PHY stream. The encoder is a rate $\frac{1}{2}$ convolutional encoder with constraint length $K = 7$ and code generator "polynomials" 1111001 and 1011011. At the beginning, the encoder state is set to zero. At the end of the transmission of either the header or the payload, zeroes shall be inserted to flush the encoder (8 zeroes for the PHY header and 6 zeroes for the payload). The bit generated by the first code generator is first output. The block diagram of the encoder is shown in Figure 7-8. + +![Figure 7-8 – Convolutional encoder](b53846f262c6904a1b45abef2e95fbd8_img.jpg) + +Figure 7-8 – Convolutional encoder shows a feed-forward convolutional encoder with a constraint length K=7. The input bit is shifted into a series of six delay elements, denoted as Z-1. There are two output paths. The first output is the XOR sum of the input and the outputs of the 1st, 2nd, 3rd, and 6th delay elements, corresponding to the generator polynomial coefficients (1, 1, 1, 1, 0, 0, 1). The second output is the XOR sum of the input and the outputs of the 2nd, 3rd, 4th, and 6th delay elements, corresponding to the generator polynomial coefficients (1, 0, 1, 1, 0, 1, 1). The diagram includes labels for these coefficients (1, 1, 1, 1, 0, 0, 1 for the top and 1, 0, 1, 1, 0, 1, 1 for the bottom) and identifies the 'First output' and 'Second output'. The reference G.9955(11)\_FB-8 is at the bottom right of the diagram. + +Figure 7-8 – Convolutional encoder + +**Figure 7-8 – Convolutional encoder** + +**7.6 Scrambler** + +The scrambler block randomizes the bit stream so it reduces the crest factor at the output of the IFFT. Scrambling shall always be performed. + +The scrambler block performs an XOR of the input bit stream using a pseudo noise sequence pn obtained by a cyclic extension of the 127 element sequence given by: + +Pref0..126 = + +{0,0,0,0,1,1,1,0,1,1,1,1,0,0,1,0,1,1,0,0,1,0,0,1,0,0,0,0,0,0,1,0,0,0,1,0,0,1,1,0,0,0,1,0,1,1,1,0,1,0,1,1,0 + ,1,1,0,0,0,0,0,1,1,0,0,1,1,0,1,0,1,0,0,1,1,1,0,0,1,1,1,1,0,1,1,0,1,0,0,0,0,1,0,1,0,1,0,1,1,1,1,1,0,1,0,0,1, + 0,1,0,0,0,1,1,0,1,1,1,0,0,0,1,1,1,1,1,1,1} + +The PRBS sequence can be generated by the scrambler defined in Figure 7-9 when the "all-ones" initial state is used. + +![Figure 7-9 – LFSR for use in the scrambler block](ef177a7090c8da3fcd9beb78e78fd68f_img.jpg) + +Figure 7-9 shows a Linear Feedback Shift Register (LFSR) used for scrambling. It consists of 7 delay stages. The first three stages are initialized with '1 1 1' and the next four stages with '1 1 1 1'. Feedback is taken from the output of the 4th stage and the 7th stage, which are XORed together. This feedback is then fed back into the input of the first stage. The output of the 7th stage is XORed with the 'Input Sequence' to produce the 'Output Sequence'. The reference G.9955(11)\_FB-9 is at the bottom right. + +Figure 7-9 – LFSR for use in the scrambler block + +**Figure 7-9 – LFSR for use in the scrambler block** + +Loading of the sequence pn shall be initiated at the start of every PPDU, just after the preamble. + +**7.7 Interleaver** + +Because of the frequency fading (narrowband interference) of typical power line channels, OFDM subcarriers are generally received at different amplitudes. Deep fades in the spectrum may cause groups of subcarriers to be less reliable than others, thereby causing bit errors to occur in bursts rather than be randomly scattered. If (and only if) coding is used as described in clause 7.4, interleaving is applied to randomize the occurrence of bit errors prior to decoding. At the + +12 Rec. ITU-T G.9904 (10/2012) + +transmitter, the coded bits are permuted in a certain way, which ensures that adjacent bits are separated by several bits after interleaving. + +Let $N_{\text{CBPS}} = 2 \times N_{\text{BPS}}$ be the number of coded bits per OFDM symbol in the cases where convolutional coding is used. All coded bits shall be interleaved by a block interleaver with a block size corresponding to $N_{\text{CBPS}}$ . The interleaver ensures that adjacent coded bits are mapped onto non-adjacent data subcarriers. Let $v(k)$ , with $k = 0, 1, \dots, N_{\text{CBPS}}-1$ , be the coded bits vector at the interleaver input. $v(k)$ is transformed into an interleaved vector $w(i)$ , with $i = 0, 1, \dots, N_{\text{CBPS}}-1$ , by the block interleaver as follows: + +$$w((N_{\text{CBPS}}/s) \times (k \bmod s) + \text{floor}(k/s)) = v(k) \quad k = 0, 1, \dots, N_{\text{CBPS}}-1.$$ + +The value of $s$ is determined by the number of coded bits per subcarrier, $N_{\text{CBPSC}} = 2 \times N_{\text{BPSC}}$ . $N_{\text{CBPSC}}$ is related to $N_{\text{CBPS}}$ so that $N_{\text{CBPS}} = 96 \times N_{\text{CBPSC}}$ (payload) and $N_{\text{CBPS}} = 84 \times N_{\text{CBPSC}}$ (header) + +$$s = 8 \times (1 + \text{floor}(N_{\text{CBPSC}}/2)) \text{ for the payload and}$$ + +$$s = 7 \text{ for the header.}$$ + +The de-interleaver performs the inverse operation. Hence, if $w'(i)$ , with $i = 0, 1, \dots, N_{\text{CBPS}}-1$ , is the de-interleaver vector input, the vector $w'(i)$ is transformed into a de-interleaved vector $v'(k)$ , with $k = 0, 1, \dots, N_{\text{CBPS}}-1$ , by the block de-interleaver as follows: + +$$v'(s \times i - (N_{\text{CBPS}}-1) \times \text{floor}(s \times i / N_{\text{CBPS}})) = w'(i) \quad i = 0, 1, \dots, N_{\text{CBPS}}-1.$$ + +Descriptive tables showing index permutations can be found in Appendix II for reference. + +## 7.8 Modulation + +The PPDU payload is modulated as a multicarrier differential phase shift keying signal with one pilot subcarrier and 96 data subcarriers that comprise 96, 192 or 288 bits per symbol. The header is modulated DBPSK with 13 pilot subcarriers and 84 data subcarriers that comprise 84 bits per symbol. + +The bit stream coming from the interleaver is divided into groups of M bits where the first bit of the group of M is the most significant bit (MSB). + +Frequency domain differential modulation is performed. Figure 7-10 shows the DBPSK, DQPSK and D8PSK mapping. + +![Figure 7-10 shows three constellation diagrams for differential modulation: DBPSK, DQPSK, and D8PSK. DBPSK has two points on the I-axis: 0 at (1,0) and 1 at (-1,0). DQPSK has four points: 00 at (1,0), 01 at (0,1), 10 at (0,-1), and 11 at (-1,0). D8PSK has eight points: 000 at (1,0), 001 at (0.707, 0.707), 010 at (0,1), 011 at (-0.707, 0.707), 100 at (0.707, -0.707), 101 at (0, -1), 110 at (-0.707, -0.707), and 111 at (-1, 0). The axes are labeled I (horizontal) and Q (vertical). For DQPSK and D8PSK, the first bit is labeled Msb and the second is Lsb.](04c52bd4e8f924f176fa4d9dcc138e85_img.jpg) + +Figure 7-10 shows three constellation diagrams for differential modulation: DBPSK, DQPSK, and D8PSK. DBPSK has two points on the I-axis: 0 at (1,0) and 1 at (-1,0). DQPSK has four points: 00 at (1,0), 01 at (0,1), 10 at (0,-1), and 11 at (-1,0). D8PSK has eight points: 000 at (1,0), 001 at (0.707, 0.707), 010 at (0,1), 011 at (-0.707, 0.707), 100 at (0.707, -0.707), 101 at (0, -1), 110 at (-0.707, -0.707), and 111 at (-1, 0). The axes are labeled I (horizontal) and Q (vertical). For DQPSK and D8PSK, the first bit is labeled Msb and the second is Lsb. + +Figure 7-10 – DBPSK, DQPSK and D8PSK mapping + +The next equation defines the $M$ -ary DPSK constellation of $M$ phases: + +$$s_k = Ae^{j\theta_k}$$ + +where: + +$k$ is the frequency index representing the $k$ -th subcarrier in an OFDM symbol. + +$k = 1$ corresponds to the phase reference pilot subcarrier. + +$s_k$ is the modulator output (a complex number) for the $k$ -th given subcarrier. + +$\theta_k$ stands for the absolute phase of the modulated signal obtained as follows: + +$$\theta_k = (\theta_{k-1} + (2\pi/M)\Delta b_k) \bmod 2\pi$$ + +This equation applies for $k > 1$ in the payload, the $k = 1$ subcarrier being the phase reference pilot. When the header is transmitted, the pilot allocated in the $k$ -th subcarrier is used as a phase reference for the data allocated in the $k+1$ -th subcarrier. + +- $\Delta b_k \in \{0, 1, \dots, M-1\}$ represents the information coded in the phase increment, as supplied by the constellation encoder. + +- $M = 2, 4, \text{ or } 8$ in the case of DBPSK, DQPSK or D8PSK, respectively. + +$A$ represents the ring radius from the centre of the constellation. + +The OFDM symbol can be expressed in mathematical form: + +$$c_i(n) = \left\{ \sum_{k=86}^{182} s(k-85, i) \exp\left(\frac{j2\pi 2}{512}(n - N_{CP})\right) + \sum_{k=330}^{426} s(427-k, i) \exp\left(\frac{j2\pi 2}{512}(n - N_{CP})\right) \right\}$$ + +$i$ is the time index representing the $i$ -th OFDM symbol; $i = 0, 1, \dots, M+1$ + +$n$ is the sample index; $48 \leq n \leq 559$ $s(k, i)$ is the complex value from the subcarrier modulation block and the symbol $*$ denotes complex conjugate. + +If a complex 512-point IFFT is used, the 96 subcarriers shall be mapped as shown in Figure 7-11. The symbol '\*' represents complex conjugate. + +![Diagram of subcarrier mapping for an IFFT block. A large central rectangle is labeled 'IFFT'. On the left, 'Frequency domain inputs' are mapped to specific input ports. Ports are numbered from 0 at the bottom to 511 at the top. Mapping is as follows: Port 0: Null; Port 85: Null; Port 86: #1; Port 182: #97; Port 183: Null; Port 329: Null; Port 330: #97*; Port 426: #1*; Port 427: Null; Port 511: Null. Vertical dots indicate ranges between these points. On the right, 'Time domain outputs' are numbered from 0 at the bottom to 511 at the top. Ports 0, 1, and 2 are explicitly shown at the bottom, and port 511 at the top, with vertical dots in between.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +G.9955(11)\_FB-11 + +Diagram of subcarrier mapping for an IFFT block. A large central rectangle is labeled 'IFFT'. On the left, 'Frequency domain inputs' are mapped to specific input ports. Ports are numbered from 0 at the bottom to 511 at the top. Mapping is as follows: Port 0: Null; Port 85: Null; Port 86: #1; Port 182: #97; Port 183: Null; Port 329: Null; Port 330: #97\*; Port 426: #1\*; Port 427: Null; Port 511: Null. Vertical dots indicate ranges between these points. On the right, 'Time domain outputs' are numbered from 0 at the bottom to 511 at the top. Ports 0, 1, and 2 are explicitly shown at the bottom, and port 511 at the top, with vertical dots in between. + +**Figure 7-11 – Subcarrier mapping** + +After the inverse Fourier transform, the symbol is cyclically extended by 48 samples to create the cyclic prefix ( $N_{CP}$ ). + +## **7.9 Electrical specification of the transmitter** + +### **7.9.1 General** + +The following requirements establish the minimum technical transmitter requirements for interoperability and adequate transmitter performance. These requirements are specified in [ITU-T G.9901]. + +### **7.9.2 Transmit PSD** + +See clause C.4.2 of [ITU-T G.9901]. + +### **7.9.3 Error vector magnitude (EVM)** + +The quality of the injected signal with regard to the artificial mains network impedance shall be measured in order to validate the transmitter device. Accordingly, a vector analyser that provides EVM measurements (EVM meter) shall be used, see Annex A for an EVM definition. The test set-up described in Figures 4 and 6 of [EN 50065-1] shall be used in the case of single-phase devices and three-phase devices transmitting simultaneously on all phases, respectively. + +![Block diagram of an EVM meter showing BPF, ADC, and EVM processing blocks.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +``` + +graph LR + M --- BPF + G --- BPF + subgraph EVM_meter + BPF[BPF] --> ADC[ADC] + ADC --> EVM[EVM processing] + end + +``` + +G.9904(12)\_F7-12 + +Block diagram of an EVM meter showing BPF, ADC, and EVM processing blocks. + +**Figure 7-12 – EVM meter (block diagram)** + +The EVM meter shall include a band pass filter with an attenuation of 40 dB at 50 Hz that ensures anti-aliasing for the analogue-to-digital converter (ADC). + +The minimum performance of the ADC is 1 MSPS, 14-bit effective number of bits (ENOB). The ripple and the group delay of the band pass filter must be accounted for in EVM calculations. + +### 7.9.4 Conducted disturbance limits + +See clause C.4.3 of [ITU-T G.9901]. + +## 7.10 PHY service specification + +### 7.10.1 General + +The PHY shall have a single 20-bit free-running clock incremented in steps of 10 $\mu$ sec. The clock counts from 0 to 1048575, then overflows back to 0. As a result the period of this clock is 10.48576 seconds. The clock is never stopped or restarted. Time measured by this clock is the one to be used in some PHY primitives to indicate a specific instant in time. + +### 7.10.2 PHY data plane primitives + +#### 7.10.2.1 General + +![Overview of PHY primitives between MAC and PHY blocks.](2834bdd6eb8540277e609decbb924003_img.jpg) + +``` + +sequenceDiagram + participant MAC + participant PHY + PHY->>MAC: PHY_DATA.indication + MAC->>PHY: PHY_DATA.request + PHY->>MAC: PHY_DATA.confirm + +``` + +G.9955(11)\_FB-15bis + +Overview of PHY primitives between MAC and PHY blocks. + +**Figure 7-13 – Overview of PHY primitives** + +The request primitive is passed from the MAC to the PHY to request the initiation of a service. + +The indication and confirm primitives are passed from the PHY to the MAC to indicate an internal PHY event that is significant to MAC. This event may be logically related to a remote service request or may be caused by an event internal to PHY. + +#### 7.10.2.2 PHY\_DATA.request + +##### 7.10.2.2.1 Function + +The PHY\_DATA.request primitive is passed to the PHY layer entity to request the sending of a PPDU to one or more remote PHY entities using the PHY transmission procedures. It also allows setting the time at which the transmission shall be started. + +##### 7.10.2.2.2 Structure + +The semantics of this primitive are as follows: + +PHY\_DATA.request{*MPDU*, *Length*, *Level*, *Scheme*, *Time*}. + +The *MPDU* parameter specifies the MAC protocol data unit to be transmitted by the PHY layer entity. It is mandatory for implementations to byte-align the MPDU across the PHY-SAP. This implies 2 extra bits (due to the non-byte-aligned nature of the MAC layer header) to be located at the beginning of the header. + +The *Length* parameter specifies the length of the MPDU in bytes. The length shall be 2 bytes long. + +The *Level* parameter specifies the output signal level according to which the PHY layer transmits the MPDU. It may take one of eight values: + +- 0: maximal output level (MOL) +- 1: MOL –3 dB +- 2: MOL –6 dB +- ... +- 7: MOL –21 dB. + +The *Scheme* parameter specifies the transmission scheme to be used for the MPDU. It may have any of the following values: + +- 0: DBPSK +- 1: DQPSK +- 2: D8PSK +- 3: not used +- 4: DBPSK + convolutional code +- 5: DQPSK + convolutional code +- 6: D8PSK + convolutional code +- 7: not used. + +The *Time* parameter specifies the instant in time in which the MPDU has to be transmitted. It is expressed in tens of $\mu$ sec and may take values from 0 to $2^{20} - 1$ . + +The *Time* parameter shall be calculated by the MAC, taking into account the current PHY time obtained by PHY\_timer.get primitive. The MAC shall account for the fact that no part of the PPDU can be transmitted during beacon slots and CFP periods granted to other devices in the network. If the *Time* parameter is set such that these rules are violated, the PHY will return a fail in PHY\_Data.confirm. + +##### 7.10.2.2.3 Use + +The primitive is generated by the MAC layer entity whenever data is to be transmitted to a peer MAC entity or entities. + +The reception of this primitive will cause the PHY entity to perform all the PHY-specific actions and pass the properly formed PPDU for transfer to the peer PHY layer entity or entities. The next transmission shall start when *Time* = Timer. + +#### 7.10.2.3 PHY\_DATA.confirm + +##### 7.10.2.3.1 Function + +The PHY\_DATA.confirm primitive has only local significance and provides an appropriate response to a PHY\_DATA.request primitive. The PHY\_DATA.confirm primitive tells the MAC layer entity whether or not the MPDU of the previous PHY\_DATA.request has been successfully transmitted. + +##### 7.10.2.3.2 Structure + +The semantics of this primitive are as follows: + +PHY\_DATA.confirm{*Result*}. + +The *Result* parameter is used to pass status information back to the local requesting entity. It is used to indicate the success or failure of the previous associated PHY\_DATA.request. Some results will be standard for all implementations: + +- 0: success +- 1: too late (the time for transmission has passed) +- 2: invalid length +- 3: invalid scheme +- 4: invalid level +- 5: buffer overrun +- 6: busy channel +- 7-255: proprietary + +##### 7.10.2.3.3 Use + +The primitive is generated in response to a PHY\_DATA.request. + +It is assumed that the MAC layer has sufficient information to associate the confirm primitive with the corresponding request primitive. + +#### 7.10.2.4 PHY\_DATA.indication + +##### 7.10.2.4.1 Function + +This primitive defines the transfer of data from the PHY layer entity to the MAC layer entity. + +##### 7.10.2.4.2 Structure + +The semantics of this primitive are as follows: + +PHY\_DATA.indication{*PSDU, Length, Level, Scheme, Time*}. + +The *PSDU* parameter specifies the PHY service data unit as received by the local PHY layer entity. It is mandatory for implementations to byte-align the MPDU across the PHY-SAP. This implies two extra bits (due to the non-byte-aligned nature of the MAC layer header) to be located at the beginning of the header. + +The *Length* parameter specifies the length of the received PSDU in bytes. The length shall be 2 bytes long. + +The *Level* parameter specifies the signal level on which the PHY layer received the PSDU. It may take one of sixteen values: + +- 0: $\leq 70$ dBuV +- 1: $\leq 72$ dBuV +- 2: $\leq 74$ dBuV +- ... +- 15: $> 98$ dBuV + +The *Scheme* parameter specifies the scheme with which the PSDU is received. It may have any of the following values: + +- 0: DBPSK +- 1: DQPSK +- 2: D8PSK +- 3: not used +- 4: DBPSK + convolutional code +- 5: DQPSK + convolutional code +- 6: D8PSK + convolutional code +- 7: not used + +The *Time* parameter is the time of receipt of the preamble associated with the PSDU. + +##### 7.10.2.4.3 Use + +The PHY\_DATA.indication is passed from the PHY layer entity to the MAC layer entity to indicate the arrival of a valid PPDU. + +### 7.10.3 PHY control plane primitives + +Figure 7-14 shows the general structure of PHY control plane primitives. Each primitive may have "set", "get" or "confirm" fields. Table 7-3 lists the control plane primitives and the fields associated with each of them. Each row lists a control plane primitive. An "X" in a column indicates that the associated field is used in the primitive described in that row. + +![Figure 7-14: Overview of PHY control plane primitives. The diagram shows two interaction sequences between MAC and PHY layers. The top sequence shows MAC sending a PHY_XXX.set primitive to PHY, and PHY responding with a PHY_XXX.confirm primitive. The bottom sequence shows MAC sending a PHY_XXX.get primitive to PHY, and PHY responding with a PHY_XXX.confirm primitive. A label G.9955(11)_FB-15ter is present at the bottom right.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +G.9955(11)\_FB-15ter + +Figure 7-14: Overview of PHY control plane primitives. The diagram shows two interaction sequences between MAC and PHY layers. The top sequence shows MAC sending a PHY\_XXX.set primitive to PHY, and PHY responding with a PHY\_XXX.confirm primitive. The bottom sequence shows MAC sending a PHY\_XXX.get primitive to PHY, and PHY responding with a PHY\_XXX.confirm primitive. A label G.9955(11)\_FB-15ter is present at the bottom right. + +**Figure 7-14 – Overview of PHY control plane primitives** + +**Table 7-3 – Fields associated with PHY control plane primitives** + +| | set | get | confirm | +|-----------|------------|------------|----------------| +| PHY_AGC | X | X | X | +| PHY_Timer | | X | X | +| PHY_CD | | X | X | +| PHY_NL | | X | X | +| PHY_SNR | | X | X | +| PHY_ZCT | | X | X | + +#### 7.10.3.1 PHY\_AGC.set + +##### 7.10.3.1.1 Function + +The PHY\_AGC.set primitive is passed to the PHY layer entity by the MAC layer entity to set the automatic gain mode of the PHY layer. + +##### 7.10.3.1.2 Structure + +The semantics of this primitive are as follows: + +PHY\_AGC.set {Mode, Gain}. + +The *Mode* parameter specifies whether or not the PHY layer operates in automatic gain mode. It may take one of two values: + +- 0: Auto +- 1: Manual + +The *Gain* parameter specifies the initial receiving gain in auto mode. It may take one of *N* values: + +- 0: min\_gain dB +- 1: min\_gain + step dB +- 2: min\_gain + 2 × step dB +- ... +- N* - 1: min\_gain + (*N* - 1) × step dB + +where min\_gain and *N* depend on the specific implementation. "step" is also an implementation issue but it shall not be more than 6 dB. The maximum Gain value min\_gain + (*N* - 1) × step shall be at least 21 dB. + +##### 7.10.3.1.3 Use + +The primitive is generated by the MAC layer when the receiving gain mode has to be changed. + +#### 7.10.3.2 PHY\_AGC.get + +##### 7.10.3.2.1 Function + +The PHY\_AGC.get primitive is passed to the PHY layer entity by the MAC layer entity to get the automatic gain mode of the PHY layer. + +##### 7.10.3.2.2 Structure + +The semantics of this primitive are as follows: + +PHY\_AGC.get{}. + +##### 7.10.3.2.3 Use + +The primitive is generated by the MAC layer when it needs to know the receiving gain mode that has been configured. + +#### 7.10.3.3 PHY\_AGC.confirm + +##### 7.10.3.3.1 Function + +The PHY\_AGC.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_AGC.set or PHY\_AGC.get command. + +##### 7.10.3.3.2 Structure + +The semantics of this primitive are as follows: + +PHY\_AGC.confirm {*Mode*, *Gain*}. + +The *Mode* parameter specifies whether or not the PHY layer is configured to operate in automatic gain mode. It may take one of two values: + +- 0: auto +- 1: manual + +The *Gain* parameter specifies the current receiving gain. It may take one of *N* values: + +0: min\_gain dB + +1: min\_gain + step dB + +2: min\_gain + 2 × step dB + +... + +*N* – 1: min\_gain + (*N* – 1) × step dB + +where min\_gain and *N* depend on the specific implementation. The parameter step shall not be more than 6 dB. The maximum gain value min\_gain + (*N* – 1) × step will be at least 21 dB. + +#### 7.10.3.4 PHY\_Timer.get + +##### 7.10.3.4.1 Function + +The PHY\_Timer.get primitive is passed to the PHY layer entity by the MAC layer entity to get the time at which the transmission has to be started. + +##### 7.10.3.4.2 Structure + +The semantics of this primitive are as follows: + +PHY\_Timer.get {}. + +##### 7.10.3.4.3 Use + +The primitive is generated by the MAC layer to know the transmission start. + +#### 7.10.3.5 PHY\_Timer.confirm + +##### 7.10.3.5.1 Function + +The PHY\_Timer.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_Timer.get command. + +##### 7.10.3.5.2 Structure + +The semantics of this primitive are as follows: + +PHY\_Timer.confirm {*Time*} + +The *Time* parameter is specified in tens of microseconds. It may take values of between 0 and 220 – 1 . + +#### 7.10.3.6 PHY\_CD.get + +##### 7.10.3.6.1 Function + +The PHY\_CD.get primitive is passed to the PHY layer entity by the MAC layer entity to look for the carrier detect signal. The carrier detection algorithm shall be based on preamble detection and header recognition (see clause 7.4). + +##### 7.10.3.6.2 Structure + +The semantics of this primitive are as follows: + +PHY\_CD.get {}. + +##### 7.10.3.6.3 Use + +The primitive is generated by the MAC layer when it needs to know whether or not the physical medium is free. + +#### 7.10.3.7 PHY\_CD.confirm + +##### 7.10.3.7.1 Function + +The PHY\_CD.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_CD.get command. + +##### 7.10.3.7.2 Structure + +The semantics of this primitive are as follows: + +PHY\_CD.confirm {*cd, rssi, Time, header*}. + +The *cd* parameter may take one of two values: + +- 0: no carrier detected +- 1: carrier detected. + +The *rssi* parameter is the received signal strength indication and refers to the preamble. It is only relevant when *cd* equals 1. It may take one of sixteen values: + +- 0: $\leq 70$ dBuV +- 1: $\leq 72$ dBuV +- 2: $\leq 74$ dBuV +- ... +- 15: $> 98$ dBuV + +The *Time* parameter indicates the instant at which the present PPDU will finish. It is only relevant when *cd* equals 1. When *cd* equals 0, the time parameter will take a value of 0. If *cd* equals 1 but the duration of the whole PPDU is still not known (i.e., the header has not yet been processed), the header parameter will take a value of 1 and the time parameter will indicate the instant at which the header will finish, specified in tens of microseconds. In any other case the value of the time parameter is the instant at which the present PPDU will finish and it is specified in tens of microseconds. Time parameter refers to an absolute point in time so it is referred to the system clock. + +The *header* parameter may take one of two values: + +- 1: if a preamble has been detected but the duration of the whole PPDU is not yet known from decoding the header +- 0: in any other case. + +#### 7.10.3.8 PHY\_NL.get + +##### 7.10.3.8.1 Function + +The PHY\_NL.get primitive is passed to the PHY layer entity by the MAC layer entity to get the floor noise level value. + +##### 7.10.3.8.2 Structure + +The semantics of this primitive are as follows: + +PHY\_NL.get {}. + +##### 7.10.3.8.3 Use + +The primitive is generated by the MAC layer when it needs to know the noise level present in the power line. + +#### 7.10.3.9 PHY\_NL.confirm + +##### 7.10.3.9.1 Function + +The PHY\_NL.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_NL.get command. + +##### 7.10.3.9.2 Structure + +The semantics of this primitive are as follows: + +PHY\_NL.confirm {*noise*}. + +The *noise* parameter may take one of sixteen values: + +0: $\leq 50$ dBuV + +1: $\leq 53$ dBuV + +2: $\leq 56$ dBuV + +... + +15: $> 92$ dBuV + +#### 7.10.3.10 PHY\_SNR.get + +##### 7.10.3.10.1 Function + +The PHY\_SNR.get primitive is passed to the PHY layer entity by the MAC layer entity to get the value of the signal-to-noise ratio, defined as the ratio of the measured received signal level to noise level of the last received PPDU. The calculation of the SNR is described in Annex A. + +##### 7.10.3.10.2 Structure + +The semantics of this primitive are as follows: + +PHY\_SNR.get {} + +##### 7.10.3.10.3 Use + +The primitive is generated by the MAC layer when it needs to know the SNR in order to analyse channel characteristics and invoke management procedures for robustness, if required. + +#### 7.10.3.11 PHY\_SNR.confirm + +##### 7.10.3.11.1 Function + +The PHY\_SNR.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_SNR.get command. + +##### 7.10.3.11.2 Structure + +The semantics of this primitive are as follows: + +PHY\_SNR.confirm {*SNR*} + +The *SNR* parameter refers to the signal-to-noise ratio, defined as the ratio of the measured received signal level to noise level of the last received PPDU. It may take one of eight values. The mapping of the 3-bit index to the actual SNR value, as calculated in Annex A is given below: + +0: $\leq 0$ dB + +1: $\leq 3$ dB + +2: $\leq 6$ dB + +... + +7: $> 18$ dB + +#### 7.10.3.12 PHY\_ZCT.get + +##### 7.10.3.12.1 Function + +The PHY\_ZCT.get primitive is passed to the PHY layer entity by the MAC layer entity to get the zero cross time of the mains and the time between the last transmission or reception and the zero cross of the mains. + +##### 7.10.3.12.2 Structure + +The semantics of this primitive are as follows: + +PHY\_ZCT.get {} + +##### 7.10.3.12.3 Use + +The primitive is generated by the MAC layer when it needs to know the zero cross time of the mains, e.g., in order to calculate the phase to which the node is connected. + +#### 7.10.3.13 PHY\_ZCT.confirm + +##### 7.10.3.13.1 Function + +The PHY\_ZCT.confirm primitive is passed to the MAC layer entity by the PHY layer entity in response to a PHY\_ZCT.get command. + +##### 7.10.3.13.2 Structure + +The semantics of this primitive are as follows: + +PHY\_ZCT.confirm {*Time*}. + +The *Time* parameter is the instant in time at which the last zero-cross event took place. + +### 7.10.4 PHY management primitives + +PHY layer management primitives enable the PHY layer to interface to the MAC layer. Implementation of these primitives is optional. Refer to Figure 7-14 for the general structure of the PHY layer management primitives. + +**Table 7-4 – PHY layer management primitives** + +| Primitive | set | get | confirm | +|---------------|-----|-----|---------| +| PLME_RESET | X | | X | +| PLME_SLEEP | X | | X | +| PLME_RESUME | X | | X | +| PLME_TESTMODE | X | | X | +| PLME_GET | | X | X | + +#### 7.10.4.1 PLME\_RESET.request + +##### 7.10.4.1.1 Function + +The PLME\_RESET.request primitive is invoked to request the PHY layer to reset its present functional state. As a result of this primitive, the PHY should reset all internal states and flush all buffers to clear any queued receive or transmit data. All the SET primitives are invoked by the PLME, and addressed to the PHY to set parameters in the PHY. The GET primitive is also sourced by the PLME, but is used only to read PHY parameters. + +##### **7.10.4.1.2 Structure** + +The semantics of this primitive are as follows: + +PLME\_RESET.request{}. + +##### **7.10.4.1.3 Use** + +The upper layer management entities will invoke this primitive to tackle any system level anomalies that require aborting any queued transmissions and restart all operations from the initialization state. + +#### **7.10.4.2 PLME\_RESET.confirm** + +##### **7.10.4.2.1 Function** + +The PLME\_RESET.confirm is generated in response to a corresponding PLME\_RESET.request primitive. It provides indication if the requested reset was performed successfully or not. + +##### **7.10.4.2.2 Structure** + +The semantics of this primitive are as follows: + +PLME\_RESET.confirm{*Result*}. + +The *Result* parameter shall have one of the following values: + +0: Success + +1: Failure (the requested reset failed due to internal implementation issues). + +##### **7.10.4.2.3 Use** + +The primitive is generated in response to a PLME\_RESET.request. + +#### **7.10.4.3 PLME\_SLEEP.request** + +##### **7.10.4.3.1 Function** + +The PLME\_SLEEP.request primitive is invoked to request the PHY layer to suspend its present activities including all reception functions. The PHY layer should complete any pending transmission before entering into a sleep state. + +##### **7.10.4.3.2 Structure** + +The semantics of this primitive are as follows: + +PLME\_SLEEP.request{}. + +##### **7.10.4.3.3 Use** + +This primitive is designed to help optimize power consumption. + +#### **7.10.4.4 PLME\_SLEEP.confirm** + +##### **7.10.4.4.1 Function** + +The PLME\_SLEEP.confirm is generated in response to a corresponding PLME\_SLEEP.request primitive and provides information if the requested sleep state has been entered successfully or not. + +##### **7.10.4.4.2 Structure** + +The semantics of this primitive are as follows: + +PLME\_SLEEP.confirm{*Result*}. + +The *Result* parameter shall have one of the following values: + +- 0: success +- 1: failure (the requested sleep failed due to internal implementation issues) +- 2: PHY layer is already in sleep state. + +##### 7.10.4.4.3 Use + +The primitive is generated in response to a PLME\_SLEEP.request + +#### 7.10.4.5 PLME\_RESUME.request + +##### 7.10.4.5.1 Function + +The PLME\_RESUME.request primitive is invoked to request the PHY layer to resume its suspended activities. As a result of this primitive, the PHY layer shall start its normal transmission and reception functions. + +##### 7.10.4.5.2 Structure + +The semantics of this primitive are as follows: + +PLME\_RESUME.request{} + +##### 7.10.4.5.3 Use + +This primitive is invoked by upper layer management entities to resume normal PHY layer operations, assuming that the PHY layer is presently in a suspended state as a result of previous PLME\_SLEEP.request primitive. + +#### 7.10.4.6 PLME\_RESUME.confirm + +##### 7.10.4.6.1 Function + +The PLME\_RESUME.confirm is generated in response to a corresponding PLME\_RESUME.request primitive and provides information about the requested resumption status. + +##### 7.10.4.6.2 Structure + +The semantics of this primitive are as follows: + +PLME\_RESUME.confirm{*Result*}. + +The *Result* parameter shall have one of the following values: + +- 0: success +- 1: failure (the requested resume failed due to internal implementation issues) +- 2: PHY layer is already in fully functional state. + +##### 7.10.4.6.3 Use + +The primitive is generated in response to a PLME\_RESUME.request + +#### 7.10.4.7 PLME\_TESTMODE.request + +##### 7.10.4.7.1 Function + +The PLME\_TESTMODE.request primitive is invoked to enter the PHY layer into test mode (specified by the mode parameter). A specific functional mode out of the various possible modes is provided as an input parameter. Following the receipt of this primitive, the PHY layer should complete any pending transmissions in its buffer before entering the requested test mode. + +##### 7.10.4.7.2 Structure + +The semantics of this primitive are as follows: + +PLME\_TESTMODE.request{*enable, mode, modulation, pwr\_level*}. + +The *enable* parameter starts or stops the test mode and may take one of two values: + +- 0: stop test mode and return to normal functional state +- 1: transit from present functional state to test mode. + +The *mode* parameter enumerates specific functional behaviours to be exhibited while the PHY is in test mode. It may have either of the two values: + +- 0: continuous transmit +- 1: transmit with 50% duty cycle. + +The *modulation* parameter specifies which modulation scheme is used during transmissions. It may take any of the following 8 values: + +- 0: DBPSK +- 1: DQPSK +- 2: D8PSK +- 3: not used +- 4: DBPSK + convolutional code +- 5: DQPSK + convolutional code +- 6: D8PSK + convolutional code +- 7: not used + +The *pwr\_level* parameter specifies the relative level at which the test signal is transmitted. It may take either of the following values: + +- 0: maximal output level (MOL) +- 1: MOL – 3 dB +- 2: MOL – 6 dB +- ... +- 7: MOL – 21 dB + +##### 7.10.4.7.3 Use + +This primitive is invoked by a management entity when specific tests are required to be performed. + +#### 7.10.4.8 PLME\_TESTMODE.confirm + +##### 7.10.4.8.1 Function + +The PLME\_TESTMODE.confirm is generated in response to a corresponding PLME\_TESTMODE.request primitive to indicate if the transition to "Testmode" was successful or not. + +##### 7.10.4.8.2 Structure + +The semantics of this primitive are as follows: + +PLME\_TESTMODE.confirm{*Result*}. + +The *Result* parameter shall have one of the following values: + +- 0: success +- 1: failure (transition to "Testmode" failed due to internal implementation issues) +- 2: PHY layer is already in "Testmode" + +##### 7.10.4.8.3 Use + +The primitive is generated in response to a PLME\_TESTMODE.request. + +#### 7.10.4.9 PLME\_GET.request + +##### 7.10.4.9.1 Function + +The PLME\_GET.request queries information about a given PIB attribute. + +##### 7.10.4.9.2 Structure + +The semantics of this primitive are as follows: + +PLME\_GET.request{*PIBAttribute*} + +The *PIBAttribute* parameter identifies specific attributes as enumerated in ID fields of tables that enumerate PIB attributes. + +##### 7.10.4.9.3 Use + +This primitive is invoked by the management entity to query one of the available PIB attributes. + +#### 7.10.4.10 PLME\_GET.confirm + +##### 7.10.4.10.1 Function + +The PLME\_GET.confirm primitive is generated in response to the corresponding PLME\_GET.request primitive. + +##### 7.10.4.10.2 Structure + +The semantics of this primitive are as follows: + +PLME\_GET.confirm{*status*, *PIBAttribute*, *PIBAttributeValue*} + +The *status* parameter reports the result of requested information and can have one of the values in Table 7-5. + +**Table 7-5 – Values of the status parameter in PLME\_GET.confirm primitive** + +| Result | Description | +|-------------|---------------------------------------------------------------| +| Done = 0 | Parameter read successfully | +| Failed = 1 | Parameter read failed due to internal implementation reasons. | +| BadAttr = 2 | Specified PIBAttribute is not supported | + +The *PIBAttribute* parameter identifies specific attributes as enumerated in ID fields of tables that enumerate PIB attributes. + +The *PIBAttributeValue* parameter specifies the value associated with a given "*PIBAttribute*". + +##### 7.10.4.10.3 Use + +This primitive is generated by the PHY layer in response to a PLME\_GET.request primitive. + +# 8 Data link layer specifications + +## 8.1 Overview + +A subnetwork can be logically seen as a tree structure with two types of nodes: the base node and service nodes. + +- Base node: it is at the root of the tree structure and acts as a master node that provides all subnetwork elements with connectivity. It manages the subnetwork resources and connections. There is only one base node in a subnetwork. The base node is initially the subnetwork itself and any other node should follow a registration process to enrol itself on the subnetwork. +- Service nodes: they are either leaves or branch points of the tree structure. They are initially in a disconnected functional state and follow the registration process in clause 8.6.1 to become part of the subnetwork. Service nodes have two functions in the subnetwork: keeping connectivity to the subnetwork for their application layers and switching other nodes' data to propagate connectivity. + +Devices elements that exhibit base node functionality continue to do so as long as they are not explicitly reconfigured by mechanisms that are beyond the scope of this Recommendation. Service nodes, on the other hand, change their behaviour dynamically from "terminal" functions to "switch" functions and vice-versa. The changing of functional states occurs in response to certain pre-defined events on the network. Figure 8-1 shows the functional state transition diagram of a service node. + +The three functional states of a service node are disconnected, terminal and switch. + +- Disconnected: is the initial functional state for all service nodes. When disconnected, a service node is not able to communicate data or switch other nodes' data; its main function is to search for a subnetwork within its reach and try to register on it. +- Terminal: when in this functional state a service node is able to establish connections and communicate data, but it is not able to switch other nodes' data. +- Switch: when in this functional state a service node is able to perform all terminal functions. Additionally, it is able to forward data to and from other nodes in the same subnetwork. It is a branch point on the tree structure. + +![Figure 8-1 – Service node states. A state transition diagram showing three states: Switch, Terminal, and Disconnected. Transitions are: Switch to Terminal (Demote), Terminal to Switch (Promote), Terminal to Disconnected (Unregister), Disconnected to Terminal (Register), and Switch to Disconnected (Unregister).](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +``` +graph TD; Switch[Switch] -- Demote --> Terminal[Terminal]; Terminal -- Promote --> Switch; Terminal -- Register --> Disconnected[Disconnected]; Disconnected -- Unregister --> Terminal; Switch -- Unregister --> Disconnected; +``` + +Figure 8-1 – Service node states. A state transition diagram showing three states: Switch, Terminal, and Disconnected. Transitions are: Switch to Terminal (Demote), Terminal to Switch (Promote), Terminal to Disconnected (Unregister), Disconnected to Terminal (Register), and Switch to Disconnected (Unregister). + +Figure 8-1 – Service node states + +The events and associated processes that trigger changes from one functional state to another are given below. + +- Registration: the process by which a service node includes itself in the base node's list of registered nodes. Its successful completion means that the service node is part of a subnetwork. Thus, it represents the transition between disconnected and terminal. +- Unregistration: the process by which a service node removes itself from the base node's list of registered nodes. Unregistration may be initiated by either the service node or base node. A service node may unregister itself to find a better point of attachment, i.e., change the switch node through which it is attached to the network. A base node may unregister a registered service node as a result of failure of any of the MAC procedures. Its successful completion means that the service node is disconnected and no longer part of a subnetwork. +- Promotion: the process by which a service node is qualified to switch (repeat, forward) data traffic from other nodes and act as a branch point on the subnetwork tree structure. A successful promotion represents the transition between terminal and switch. When a service node is disconnected it cannot directly transition to switch. +- Demotion: the process by which a service node ceases to be a branch point on the subnetwork tree structure. A successful demotion represents the transition between switch and terminal. + +## 8.2 Addressing + +### 8.2.1 General + +Each node has a 48-bit universal MAC address, defined in [IEEE 802-2001] and called EUI-48. Every EUI-48 is assigned during the manufacturing process and it is used to uniquely identify a node during the registration process. + +The EUI-48 of the base node uniquely identifies its subnetwork. This EUI-48 is called the subnetwork address (SNA). + +The local switch identifier (LSID) is a unique 8-bit identifier for each switch node inside a subnetwork. The subnetwork base node assigns an LSID during the promotion process. A switch node is universally identified by the SNA and LSID. LSID = 0x00 is reserved for the base node. LSID = 0xFF is reserved to mean "unassigned" or "invalid" in certain specific fields (see Table 8-13). This special use of the 0xFF value is always made explicit when describing those fields and it shall not be used in any other field. + +During its registration process, every service node receives a 14-bit local node identifier (LNID). The LNID identifies a single service node among all service nodes that directly depend on a given switch. The combination of a service node's LNID and SID (its immediate switch's LSID) forms a 22-bit node identifier (NID). The NID identifies a single service node in a given subnetwork. LNID = 0x0000 cannot be assigned to a terminal, as it refers to its immediate switch. LNID = 0x3FFF is reserved for broadcast and multicast traffic (see clause 8.2.3 for more information). In certain specific fields, the LNID = 0x3FFF may also be used as "unassigned" or "invalid" (see Tables 8-1 and 8-9). This special use of the 0x3FFF value is always made explicit when describing the said fields and it shall not be used in this way in any other field. + +During connection establishment a 9-bit local connection identifier (LCID) is reserved. The LCID identifies a single connection in a node. The combination of NID and LCID forms a 31-bit connection identifier (CID). The CID identifies a single connection in a given subnetwork. Any connection is universally identified by the SNA and CID. LCID values are allocated with the following rules: + +LCID=0x000 to 0x0FF, for connections requested by the base node. The allocation shall be made by the base node. + +LCID=0x100 to 0x1FF, for connections requested by a service node. The allocation shall be made by a service node. + +The full addressing structure and field lengths are shown in Figure 8-2. + +![Figure 8-2: Addressing structure diagram showing the layout of a 128-bit address. The address is divided into four main fields: SNA (48 bits), LSID (8 bits), LNID (14 bits), and LCID (9 bits). The SNA field is preceded by a Most Significant Bit (MSB). The LSID, LNID, and LCID fields are grouped together by a bracket labeled 'NID (22 bits)'. The entire address structure is further bracketed by a bracket labeled 'CID (31 bits)'. The Least Significant Bit (LSB) is indicated within the LCID field.](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) + +| | | | | | +|---------------|---------|--------|---------|--------| +| MSB | 48 bits | 8 bits | 14 bits | 9 bits | +| | SNA | LSID | LNID | LCID | +| LSB | | | | | +| NID (22 bits) | | | | | +| CID (31 bits) | | | | | + +Figure 8-2: Addressing structure diagram showing the layout of a 128-bit address. The address is divided into four main fields: SNA (48 bits), LSID (8 bits), LNID (14 bits), and LCID (9 bits). The SNA field is preceded by a Most Significant Bit (MSB). The LSID, LNID, and LCID fields are grouped together by a bracket labeled 'NID (22 bits)'. The entire address structure is further bracketed by a bracket labeled 'CID (31 bits)'. The Least Significant Bit (LSB) is indicated within the LCID field. + +**Figure 8-2 – Addressing structure** + +When a service node in terminal state starts promotion process, the base node allocates a unique switch identifier which is used by this device after transition to the switch state as SID of this switch. The promoted service node continues to use the same NID that it used before promotion, i.e., it maintains the SID of its next level switch for addressing all traffic generated/destined to its local application processes. To maintain distinction between the two switch identifiers, the switch identifier allocated to a service node during its promotion is referred to as a local switch identifier (LSID). Note that the LSID of a switch device will be an SID of devices that connects to the subnetwork through it. + +Each service node has a level in the topology tree structure. Service nodes which are directly connected to the base node have level 0. The level of any service node not directly connected to the base node is the level of its immediate switch plus one. + +### 8.2.2 Example of address resolution + +Figure 8-3 shows an example where disconnected service nodes are trying to register on the base node. In this example, addressing will have the following nomenclature: (SID, LNID). Initially, the only node with an address is base node A, which has an NID=(0, 0). + +![Figure 8-3: Example of address resolution: phase 1. The diagram shows a base node A at the top, labeled 'A: Base Node S=(0, 0)'. Below it, there are two rows of disconnected nodes. The first row contains nodes B, C, D, and E, each labeled 'B:Disconnected', 'C:Disconnected', 'D:Disconnected', and 'E:Disconnected' respectively. The second row contains nodes F, G, and H, each labeled 'F:Disconnected', 'G:Disconnected', and 'H:Disconnected' respectively. All nodes are shown in rectangular boxes.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +Figure 8-3: Example of address resolution: phase 1. The diagram shows a base node A at the top, labeled 'A: Base Node S=(0, 0)'. Below it, there are two rows of disconnected nodes. The first row contains nodes B, C, D, and E, each labeled 'B:Disconnected', 'C:Disconnected', 'D:Disconnected', and 'E:Disconnected' respectively. The second row contains nodes F, G, and H, each labeled 'F:Disconnected', 'G:Disconnected', and 'H:Disconnected' respectively. All nodes are shown in rectangular boxes. + +**Figure 8-3 – Example of address resolution: phase 1** + +Every other node of the subnetwork will try to register on the base node. Only B, C, D and E nodes are able to register on this subnetwork and get their NIDs. Figure 8-4 shows the status of nodes after the registration process. Since they have registered on the base node, they get the SID of the base node and a unique LNID. The level of newly registered nodes is 0 because they are connected directly to the base node. + +![Figure 8-4: Example of address resolution: phase 2. A hierarchical diagram showing a Base Node A at the top with S=(0, 0). It is connected to four nodes at Level 0: B (Terminal, T=(0, 3)), C (Terminal, T=(0, 1)), D (Terminal, T=(0, 4)), and E (Terminal, T=(0, 2)). Below these, nodes F, G, and H are shown as 'Disconnected' in separate boxes.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +``` + +graph TD + A["A: Base Node +S=(0, 0)"] --> B["B: Terminal +T=(0, 3)"] + A --> C["C: Terminal +T=(0, 1)"] + A --> D["D: Terminal +T=(0, 4)"] + A --> E["E: Terminal +T=(0, 2)"] + B -.-> F["F:Disconnected"] + C -.-> G["G:Disconnected"] + D -.-> H["H:Disconnected"] + E --- L0["Level = 0"] + +``` + +Figure 8-4: Example of address resolution: phase 2. A hierarchical diagram showing a Base Node A at the top with S=(0, 0). It is connected to four nodes at Level 0: B (Terminal, T=(0, 3)), C (Terminal, T=(0, 1)), D (Terminal, T=(0, 4)), and E (Terminal, T=(0, 2)). Below these, nodes F, G, and H are shown as 'Disconnected' in separate boxes. + +**Figure 8-4 – Example of address resolution: phase 2** + +Nodes F, G and H cannot connect directly to the base node which is currently the only switch in the subnetwork. F, G and H will send promotion needed PDU (PNPDU) broadcast requests which will result in nodes B and D requesting promotion for themselves in order to extend the subnetwork range. During promotion, they will both be assigned unique SIDs. Figure 8-5 shows the new status of the network after the promotion of nodes B and D. Each switch node will still use the NID that was assigned to it during the registration process for its own communication as a terminal node. The new SID shall be used for all switching functions. + +![Figure 8-5: Example of address resolution: phase 3. Similar to Figure 8-4, but nodes B and D have been promoted to Switch nodes. B now has T=(0, 3) and S=(1, 0). D now has T=(0, 4) and S=(2, 0). Nodes F, G, and H remain 'Disconnected'.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +graph TD + A["A: Base Node +S=(0, 0)"] --> B["B: Switch +T=(0, 3)S=(1, 0)"] + A --> C["C: Terminal +T=(0, 3)"] + A --> D["D: Switch +T=(0, 4)S=(2, 0)"] + A --> E["E: Terminal +T=(0, 2)"] + B -.-> F["F:Disconnected"] + C -.-> G["G:Disconnected"] + D -.-> H["H:Disconnected"] + E --- L0["Level = 0"] + +``` + +Figure 8-5: Example of address resolution: phase 3. Similar to Figure 8-4, but nodes B and D have been promoted to Switch nodes. B now has T=(0, 3) and S=(1, 0). D now has T=(0, 4) and S=(2, 0). Nodes F, G, and H remain 'Disconnected'. + +**Figure 8-5 – Example of address resolution: phase 3** + +On completion of the B and D promotion process, nodes F, G and H shall start their registration process and have a unique LNID assigned. Every node on the subnetwork will then have a unique NID to communicate like a terminal, and switch nodes will have unique SIDs for switching purposes. The level of newly registered nodes is 1 because they register with level 0 nodes. On the completion of topology resolution and address allocation, the example subnetwork would be as shown in Figure 8-6. + +![Figure 8-6: Example of address resolution: phase 4. The final network topology. Base Node A is connected to Level 0 nodes B (Switch), C (Terminal), D (Switch), and E (Terminal). Level 1 nodes are now connected: F (Terminal, T=(1, 1)) is connected to B; G (Terminal, T=(1, 2)) is connected to C; H (Terminal, T=(2, 1)) is connected to D.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +``` + +graph TD + A["A: Base Node +S=(0, 0)"] --> B["B: Switch +T=(0, 3)S=(1, 0)"] + A --> C["C: Terminal +T=(0, 1)"] + A --> D["D: Switch +T=(0, 4)S=(2, 0)"] + A --> E["E: Terminal +T=(0, 2)"] + B --> F["F: Terminal +T=(1, 1)"] + C --> G["G: Terminal +T=(1, 2)"] + D --> H["H: Terminal +T=(2, 1)"] + E --- L0["Level = 0"] + H --- L1["Level = 1"] + +``` + +Figure 8-6: Example of address resolution: phase 4. The final network topology. Base Node A is connected to Level 0 nodes B (Switch), C (Terminal), D (Switch), and E (Terminal). Level 1 nodes are now connected: F (Terminal, T=(1, 1)) is connected to B; G (Terminal, T=(1, 2)) is connected to C; H (Terminal, T=(2, 1)) is connected to D. + +**Figure 8-6 – Example of address resolution: phase 4** + +### 8.2.3 Broadcast and multicast addressing + +Multicast and broadcast addresses are used for communicating data to multiple nodes. There are several broadcast and multicast address types depending on the context associated with the traffic flow. Table 8-1 describes different broadcast and multicast addressing types and the SID and LNID fields associated with each one. + +**Table 8-1 – Broadcast and multicast address** + +| Type | LNID | Description | +|-----------|-----------------------|-----------------------------------------------------------------------------------------------------------------| +| Broadcast | 0x3FFF | Using this address as a destination, the packets should reach every node of the subnetwork. | +| Multicast | 0x3FFE | This type of address refers to multicast groups. The multicast group is defined by the LCID. | +| Unicast | not 0x3FFF not 0x3FFE | The address of this type refers to the only node of the subnetwork whose SID and LNID match the address fields. | + +## 8.3 MAC functional description + +### 8.3.1 Service node start-up + +A service node is initially disconnected. The only functions that may be performed in a disconnected functional state are: reception of any beacons on the channel and sending of the PNPDU. Each service node shall maintain a switch table that is updated with the reception of a beacon from any new switch node. Based on local implementation policies, a service node may select any switch node from the switch table and proceed with the registration process with that switch node. The criteria for selecting a switch node from the switch table is beyond the scope of this Recommendation. + +A service node shall listen on the channel for at least *macMinSwitchSearchTime* before deciding that no beacon is being received. It may optionally add some random variation to *macMinSwitchSearchTime*, but this variation cannot be more than 10per cent of *macMinSwitchSearchTime*. If no beacons are received in this time, the service node shall broadcast a PNPDU. The PNPDU shall be broadcast with the most robust modulation scheme to ensure maximum coverage. A service node seeking promotion of any of the terminal nodes in its proximity shall not transmit more than *macMaxPromotionPdu* PNPDU per *macPromotionPduTxPeriod* units of time. The service nodes shall also ensure that the broadcast of PNPDU is randomly spaced. There must always be a random time separation between successive broadcasts. + +So as not to flood the network with PNPDU, especially in cases where several devices are powered up at the same time, the terminal nodes shall reduce the PNPDU transmission rate by a factor of PNPDU received from other sources. For example, if a node receives one PNPDU when it is transmitting its own PNPDU, it shall reduce its own transmissions to no more than *macMaxPromotionPdu/2* per *macPromotionPduTxPeriod* units of time. Likewise, if it receives PNPDU from two different sources, it shall slow down its rate to no more than *macMaxPromotionPdu/3* per *macPromotionPduTxPeriod* units of time. + +On the selection of a specific switch node, a service node shall start a registration process by transmitting the REG control packet (clause 8.4.5.3) to the base node. The switch node through which the service node intends to carry out its communication is indicated in the REG control packet. + +### 8.3.2 Starting and maintaining subnetworks + +Base nodes are primarily responsible for setting up and maintaining a subnetwork. In order to execute the latter, the base node shall perform the following: + +- **Beacon transmission:** The base node and all the switch nodes on the subnetwork shall broadcast beacons at fixed intervals of time. The base node shall always transmit exactly one beacon per frame. Switch nodes shall transmit beacons with a frequency prescribed by the base node at the time of their promotion. +- **Promotion and demotion of terminals and switches:** All promotion requests generated by terminal nodes upon receipt of the PNPDU are directed to the base node. The base node maintains a table of all the switch nodes on the subnetwork and allocates a unique SID to new incoming requests. Upon receipt of multiple promotion requests, the base node can, at its own discretion, reject some of the requests. Likewise, the base node is responsible for demoting registered switch nodes. The demotion may either be initiated by the base node (based on an implementation-dependent decision process) or be requested by the switch node itself. +- **Registration management:** The base node receives registration requests from all new nodes trying to be part of the subnetwork it manages. The base node shall process each registration request it receives and respond with an accept or reject message. When the base node accepts the registration of a service node, it shall allocate a unique NID to it to be used for all subsequent communication on the subnetwork. Likewise, the base node is responsible for deregistering any registered service nodes. The unregistration may be initiated by the base node (based on an implementation-dependent decision process) or requested by the service node itself. +- **Connection set-up and management:** The MAC layer specified in this Recommendation is connection-oriented, implying that data exchange is necessarily preceded by connection establishment. The base node is always required for all connections on the subnetwork, either as an end point of the connection or as a facilitator (direct connections; clause 8.3.6) of the connection. +- **Channel access arbitration:** The usage of the channel by devices conforming to this Recommendation may be controlled and contention-free at certain times and open and contention-based at others. The base node prescribes which usage mechanism shall be in force at what time and for how long. Furthermore, the base node shall be responsible for assigning the channel to specific devices during contention-free access periods. +- **Distribution of random sequence for deriving encryption keys:** When using security profile 1 (see clause 8.3.8.2.2), all control messages in this MAC specification shall be encrypted before transmission. Besides control messages, data transfers may be optionally encrypted as well. The encryption key is derived from a 128-bit random sequence. The base node shall periodically generate a new random sequence and distribute it to the entire subnetwork, thus helping to maintain the subnetwork security infrastructure. +- **Multicast group management:** The base node shall maintain all multicast groups on the subnetwork. This shall require the processing of all join and leave requests from any of the service nodes and the creation of unsolicited join and leave messages from base node application requests. + +Additional information regarding promotion and connection procedures can be found in clauses 8.6.3 and 8.6.6. + +### 8.3.3 Channel access + +#### 8.3.3.1 General + +Devices on a subnetwork access the channel based on specific guidelines laid down in this clause. Time is divided into composite units of abstraction for channel usage, called MAC frames. The service nodes and base node on a subnetwork can access the channel in the shared-contention period (SCP) or request a dedicated contention-free period (CFP). + +CFP channel access needs devices to request allocation from the base node. Depending on channel usage status, the base node may grant access to the requesting device for a specific duration or deny the request. + +SCP channel access does not require any arbitration. However, the transmitting devices need to respect the SCP timing boundaries in a MAC frame. The composition of a MAC frame in terms of SCP and CFP is communicated in every frame as part of the beacon. + +A MAC frame is comprised of one or more beacons, one shared-contention period and zero or one contention-free period (CFP). When present, the length of the CFP is indicated in the BPDU. + +![Diagram of a MAC frame structure showing five beacon slots followed by a shared-contention period (SCP) and a contention-free period (CFP).](82fbb97c1145cac89ac72dd080fad17a_img.jpg) + +| | | | | | | | +|----------|----------|----------|----------|----------|-----|-----| +| Beacon 0 | Beacon 1 | Beacon 2 | Beacon 3 | Beacon 4 | SCP | CFP | +|----------|----------|----------|----------|----------|-----|-----| + +Diagram of a MAC frame structure showing five beacon slots followed by a shared-contention period (SCP) and a contention-free period (CFP). + +Figure 8-7 – Structure of a MAC frame + +#### 8.3.3.2 Beacon + +##### 8.3.3.2.1 General + +A BPDU is transmitted by the base node every $(MACFrameLength - MACBeaconLength)$ symbols. The switch nodes also transmit the BPDU to maintain their part of the subnetwork. They transmit BPDUs at regular times, but the transmission frequency does not need to be the same as that of the base node, i.e., a switch node may not transmit its BPDU in every frame. + +A beacon is always $MACBeaconLength$ symbols long. This length is the beacon duration excluding the PHY PREAMBLE overhead. Since the BPDU is to be received by all devices in the originating switch domain, it is transmitted with the most robust PHY modulation scheme and FEC coding at the maximum output power level implemented in the device. Details of the BPDU structure and contents are given in clause 8.4.4. + +All service nodes shall track beacons as explained in clause 8.3.4.1. + +##### 8.3.3.2.2 Beacon slots + +A single frame may contain *macBeaconsPerFrame* BPDUs. The unit of time in which a BPDU is transmitted, is referred to as a beacon slot. All beacon slots are located at the beginning of a frame, as shown in Figure 8-7 above. The first beacon slot in every frame is reserved for the base node. The number of beacon slots in a frame may change from one frame to another and is indicated by the base node in its BPDU. + +The switch nodes are allocated a beacon slot at the time of their promotion. Following the PRO control packet, the base node transmits the BSI control packet that would list specific details on which beacon slot should be used by the new switch device. + +The number of beacon slots in a frame should be increased from 1 to at least 2 on the promotion of the first switch device on a subnetwork by the base node. Similarly, a base node cannot decrease the number of beacon slots in the subnetwork to 1 when there is a switch node on its subnetwork. + +With the registration of each new switch on the subnetwork, the base node may change the beacon slot or BPDU transmission frequency (or both) of already registered switch devices. When such a change occurs, the base node transmits a beacon slot information (BSI) control packet to each individual switch device that is affected. The switch device addressed in the BSI packet sends an acknowledgement back to the base node. Switch devices are required to relay the BSI control packet that is addressed to switch devices connected through them. During the reorganization of beacon slots, if there is a change in the beacon-slot count per frame, the base node should transmit an FRA (FRame) control packet to the entire subnetwork. The FRA control packet is an indication of change in the overall frame structure. In this specific case, it would imply an increase in SCP slots and a decrease in the number of beacon slots. + +Switch devices that receive an FRA control packet should relay it to their entire control domain because FRA packets are broadcast information about changes to frame structures. + +This is required for the entire subnetwork to have a common understanding of frame structure, especially in regions where the controlling switch devices transmit BPDUs at frequencies below once per frame. + +Figure 8-8 below shows a sample beacon-slot change sequence for an existing switch device. The example shows a beacon-slot change triggered by the promotion of a terminal device (PRO\_ACK). In this case, the promotion is followed by a change in both the number of beacon slots per frame and of the specific beacon-slot parameters already allocated to a switch. + +![Sequence diagram showing control packet sequencing following a promotion. The diagram involves three entities: Terminal, Base Node, and Switch. The sequence of messages is: 1. Terminal sends PRO_ACK to Base Node. 2. Base Node sends FRA_BCN_IND to Terminal and Switch. 3. Terminal sends BSI_IND to Base Node. 4. Base Node sends BSI_IND to Switch. 5. Terminal sends BSI_ACK to Base Node. 6. Switch sends BSI_ACK to Base Node.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant Base Node + participant Switch + Terminal->>Base Node: PRO_ACK + Base Node->>Terminal: FRA_BCN_IND + Base Node->>Switch: FRA_BCN_IND + Terminal->>Base Node: BSI_IND + Base Node->>Switch: BSI_IND + Terminal->>Base Node: BSI_ACK + Switch->>Base Node: BSI_ACK + +``` + +Sequence diagram showing control packet sequencing following a promotion. The diagram involves three entities: Terminal, Base Node, and Switch. The sequence of messages is: 1. Terminal sends PRO\_ACK to Base Node. 2. Base Node sends FRA\_BCN\_IND to Terminal and Switch. 3. Terminal sends BSI\_IND to Base Node. 4. Base Node sends BSI\_IND to Switch. 5. Terminal sends BSI\_ACK to Base Node. 6. Switch sends BSI\_ACK to Base Node. + +**Figure 8-8 – Example of control packet sequencing following a promotion** + +##### 8.3.3.2.3 Beacon-slot allocation policy + +The beacon-slot allocation policy shall ensure that during promotion a service node never receives a BSI control packet that enforces it to transmit a beacon consecutive to every beacon of the node it is registered to. + +This behaviour shall be ensured if the BSI information follows one or more of the following rules (BCN represents the information of the beacons the service node is registered to): + +- BSI.SLT is not consecutive to BCN.POS +- BSI.SEQ is not equal to any BCN.SEQ in a superframe +- BSI.FRQ is greater than BCN.FRQ. + +##### 8.3.3.2.4 Beacon superframes + +When changing the frame structure, to add or remove beacon slots or to change which beacon slot a switch should use, it is necessary to indicate when such a change should occur. All nodes must change at the same time otherwise there will be collisions with the beacons etc. + +To solve this problem a beacon superframe is defined. Each beacon contains a 5 bit sequence number. Thus 32 frames form a superframe. Any messages which contain changes to the structure or usage of the frame include a sequence number for when the change should occur. The changes requested should only happen when the beacon sequence number matches the sequence number in the change request. + +#### 8.3.3.3 Shared-contention period + +##### 8.3.3.3.1 General + +Shared-contention period (SCP) is the time when any of the devices on the subnetwork can transmit data. The SCP starts immediately after the end of the beacon slot(s) in a frame. Collisions resulting from simultaneous attempt to access the channel are avoided by the CSMA-CA mechanism specified in this clause. + +The length of the SCP may change from one frame to another and is indicated by information in the beacon. At all times, the SCP is at least *MACMinSCPLength* symbols long. The maximum permissible length of an SCP in a frame is $(MACFrameLength - MACBeaconLength)$ symbols. Maximum length SCPs can only occur when there are no dedicated channel access grants to any of the devices (no CFP) on a subnetwork that has no switch nodes (only one beacon slot). + +The use of SCP is not restricted to frames in which beacons are received. In lower levels of the subnetwork, the controlling switch node may transmit beacons at a much lower frequency than once per frame. For these parts of the subnetwork, the frame structure would still continue to be the same in frames where no beacons are transmitted. Thus, the service nodes in that segment may still use SCP at their discretion. + +##### 8.3.3.3.2 CSMA-CA algorithm + +The CSMA-CA algorithm implemented in devices works as shown in Figure 8-9. + +Implementations start with a random backoff time (*macSCPRBO*) based on the priority of data queued for transmission. *MACPriorityLevels* levels of priority need to be defined in each implementation, with a lower value indicating higher priority. In the case of data aggregation, the priority of aggregate bulk is governed by the highest priority data it contains. The *MacSCPRBO* for a transmission attempt is given below: + +$$macSCPRBO = \text{random} (0, \text{MIN} ((2^{(\text{Priority} + \text{txAttempts})} + 1), (\text{macSCPLength}/2)))$$ + +Before a backoff period starts, a device should ensure that the remaining SCP time is long enough to accommodate the backoff, the number of iterations for channel-sensing (based on data priority) and the subsequent data transmission. If this is not the case, backoff should be aborted till the SCP starts in the next frame. Aborted backoffs that start in a subsequent frame should not carry *macSCPRBO* values of earlier attempts. *macSCPRBO* values should be regenerated on the resumption of the transmission attempt in the SCP time of the next frame. + +![Flow chart for the CSMA-CA algorithm. The process starts with 'CSMA-CA Req', followed by initialization of txAttempts, chSenseCount, and burstLen to 0. It then calculates macSCPChSenseCount = Priority + 1. A loop begins with calculating macSCPRBO as a random value between 0 and MIN((2^(Priority+txAttempts)+1), (macSCPLength/2)). A decision diamond checks if (macSCPRBO + Iteration delay + Tx time) is less than or equal to the remaining SCP. If NO, it waits for the start of the next SCP. If YES, it delays for macSCPRBO symbol times and queries the channel state. A decision 'Is Channel Idle?' follows. If NO, it checks if txAttempts equals macSCPMaxTxAttempts. If YES, it sends a failure notice. If NO, it increments txAttempts and burstLen (if indicated by PHY), resets chSenseCount to 0, and loops back to the macSCPRBO calculation. If YES to 'Is Channel Idle?', it checks if chSenseCount equals macSCPChSenseCount. If YES, it transmits data. If NO, it increments chSenseCount, delays for 3msec, and loops back to the macSCPRBO calculation.](e8e818455bb0d1a6153299a388b94868_img.jpg) + +``` + +graph TD + Start[CSMA-CA Req] --> Init1{txAttempts = 0 +chSenseCount = 0 +burstLen = 0} + Init1 --> Init2{macSCPChSenseCount = Priority + 1} + Init2 --> CalcRBO{macSCPRBO = random (0, MIN ((2^(Priority+txAttempts)+1), (macSCPLength/2)))} + CalcRBO --> Decision1{(macSCPRBO + Iteration delay + Tx time) ≤ remaining SCP} + Decision1 -- NO --> WaitNext[Wait for start of next SCP] + WaitNext --> CalcRBO + Decision1 -- YES --> DelayRBO[Delay for macSCPRBO symbol times] + DelayRBO --> QueryState[Query channel state] + QueryState --> Decision2{Is Channel Idle?} + Decision2 -- NO --> Decision3{txAttempts == macSCPMaxTxAttempts} + Decision3 -- YES --> Failure[Failure notice] + Decision3 -- NO --> IncAttempts{txAttempts = txAttempts + 1} + IncAttempts --> SetBurstLen{burstLen = Length of ongoing burst (indicated by PHY)} + SetBurstLen --> ResetChSense{chSenseCount = 0} + ResetChSense --> CalcRBO + Decision2 -- YES --> Decision4{chSenseCount == macSCPChSenseCount} + Decision4 -- YES --> TxData([Tx data]) + Decision4 -- NO --> IncChSense{chSenseCount = chSenseCount + 1} + IncChSense --> Delay3ms[Delay for 3msec] + Delay3ms --> CalcRBO + +``` + +Flow chart for the CSMA-CA algorithm. The process starts with 'CSMA-CA Req', followed by initialization of txAttempts, chSenseCount, and burstLen to 0. It then calculates macSCPChSenseCount = Priority + 1. A loop begins with calculating macSCPRBO as a random value between 0 and MIN((2^(Priority+txAttempts)+1), (macSCPLength/2)). A decision diamond checks if (macSCPRBO + Iteration delay + Tx time) is less than or equal to the remaining SCP. If NO, it waits for the start of the next SCP. If YES, it delays for macSCPRBO symbol times and queries the channel state. A decision 'Is Channel Idle?' follows. If NO, it checks if txAttempts equals macSCPMaxTxAttempts. If YES, it sends a failure notice. If NO, it increments txAttempts and burstLen (if indicated by PHY), resets chSenseCount to 0, and loops back to the macSCPRBO calculation. If YES to 'Is Channel Idle?', it checks if chSenseCount equals macSCPChSenseCount. If YES, it transmits data. If NO, it increments chSenseCount, delays for 3msec, and loops back to the macSCPRBO calculation. + +**Figure 8-9 – Flow chart for the CSMA-CA algorithm** + +On completion of the *macSCPRBO* symbol time, implementations perform channel-sensing. Channel sensing shall be performed one or more times depending on the priority of data to be transmitted. The number of times for which an implementation has to perform channel-sensing (*macSCPChSenseCount*) is defined by the priority of the data to be transmitted with the following relation: + +$$macSCPChSenseCount = Priority + 1$$ + +and each channel sense should be separated by a 3 ms delay. + +When a channel is sensed to be idle on all *macSCPChSenseCount* occasions, an implementation may conclude that the channel status is idle and carry out its transmission immediately. + +During any of the *macSCPChSenseCount* channel-sensing iterations, if the channel is sensed to be occupied, implementations should reset all working variables. The local counter tracking the number of times a channel is found to be busy should be incremented by one and the CSMA-CA process should restart by generating a new *macSCPRBO*. The remaining steps, starting with the backoff, should follow as above. + +If the CSMA-CA algorithm restarts *macSCPMaxTxAttempts* number of times due to ongoing transmissions from other devices on the channel, the transmission shall abort by informing the upper layers of CSMA-CA failure. + +##### 8.3.3.3.3 MAC control packets + +MAC control packets should be transmitted in the SCP with a priority of one. Refer to priorities in clause 8.4.2.3. + +#### 8.3.3.4 Contention-free period + +Each MAC frame may optionally have a contention-free period where devices are allocated channel time on an explicit request to do so. If no device on a subnetwork requests contention-free channel access, the CFP\_ALC\_REQ\_S may be entirely absent and the MAC frame would only comprise the SCP. All CFP\_ALC\_REQ\_S requests coming from terminal or switch nodes are addressed to the base node. Intermediate switch nodes along the transmission path merely act on the allocation decision by the base node. A single MAC frame may contain up to *MACCFPMaxAlloc* non-overlapping contention-free periods. + +Base nodes may allocate overlapping times to multiple requesting service nodes. Such allocations may lead to potential interference. Thus, a base node should make such allocations only when devices that are allocated channel access for concurrent usage are sufficiently separated. + +Service nodes make channel allocation requests in a CFP MAC control packet. The base node acts on this request and responds with a request acceptance or denial. In the case of request acceptance, the base node shall respond with the location of allocation time within the MAC frame, the length of allocation time and number of future MAC frames from which the allocation pattern will take effect. The allocation pattern remains effective unless there is an unsolicited location change of the allocation period from the base node (as a result of a channel allocation pattern reorganization) or the requesting service node sends an explicit de-allocation request using a CFP MAC control packet. + +Changes resulting from action taken on a CFP MAC control message that impact overall MAC frame structure are broadcast to all devices using an FRA MAC control message. + +In a multi-level subnetwork, when a service node that is not directly connected to the base node makes a request for the CFP, the base node shall allocate CFPs to all the intermediate switch nodes so that the entire transit path from the source service node to the base node has contention-free time-slots reserved. The base node shall transmit multiple CFP control packets. The first of these CFP\_ALC\_IND will be for the requesting service node. Each of the rest will be addressed to an intermediate switch node. + +### 8.3.4 Tracking switches and peers + +#### 8.3.4.1 Tracking switches + +Service nodes should keep track of all neighbouring switch nodes by maintaining a list of the beacons received. Such tracking shall keep a node updated on reception signal quality from switch nodes other than the one to which it is connected, thus making it possible to change connection points (switch node) to the subnetwork if link quality to the existing point of connectivity degrades beyond an acceptable level. + +Note that such a change of point of connectivity may be complex for switch nodes because of devices connected through them. However, at certain times, network dynamics may justify a complex reorganization rather than continue with existing limiting conditions. + +#### 8.3.4.2 Tracking disconnected nodes + +Terminals shall process all received PNPDUs. When a service node is disconnected, it does not have information on current MAC frame structure so the PNPDUs may not necessarily arrive during the SCP. Thus, terminals shall also keep track of PNPDUs during the CFP or beacon slots. + +On processing a received PNPDU, a terminal node may decide to ignore it and not generate any corresponding promotion request (PRO\_REQ\_S). A terminal node shall ignore no more than *MACMaxPRNIgnore* PNPDUs from the same device. Receiving multiple PNPDUs from the same device indicates that there is no other device in the vicinity of the disconnected node, implying that there will be no possibility of this new device connecting to any subnetwork if the terminal node does not request promotion for itself. + +### 8.3.5 Switching + +#### 8.3.5.1 General + +On a subnetwork, the base node cannot communicate with every node directly. Switch nodes relay traffic to/from the base node so that every node on the subnetwork is effectively able to communicate with the base node. Switch nodes selectively forward traffic that originates from or is destined to one of the service nodes in its control hierarchy. All other traffic is discarded by switches, thus reducing traffic flow on the network. + +Different names of MAC header and packets are used in this clause. Please refer to clause 8.4.2 to find their complete specification. + +#### 8.3.5.2 Switching table + +Each switch node maintains a table of other switch nodes that are connected to the subnetwork through it. Maintaining this information is sufficient for switching because traffic to/from the terminal nodes will also contain the identity of their respective switch nodes (PKT.SID). Thus, the switching function is simplified in that maintaining an exhaustive listing of all terminal nodes connected through it is not necessary. + +Switch nodes start with no entries in their switching table. The switching table is dynamically updated by keeping track of promotion and demotion control packets flowing on the network. A new entry is created for every promotion acknowledgement (PRO\_ACK) that has a PKT.SID matching either the SID of the switch node itself or any of the existing entries in the switching table. Likewise, an entry corresponding to a PRO.NSID field is deleted when a demotion request is acknowledged (PRO\_DEM\_x). + +![Figure 8-10: Switching tables example. A hierarchical tree diagram showing nodes A through L. Node A is the Base Node at Level 0 with S=(0, 0). Below it are Level 0 nodes: B (Switch, T=(0, 3), S=(1, 0)), C (Terminal, T=(0, 1)), D (Switch, T=(0, 4), S=(2, 0)), and E (Terminal, T=(0, 2)). Level 1 nodes are children of B: F (Terminal, T=(1, 1)), G (Terminal, T=(1, 2), S=(3, 0)), and H (Terminal, T=(2, 1)). Level 2 nodes are children of G: I (Terminal, T=(3, 1)) and J (Terminal, T=(3, 2), S=(4, 0)). Level 3 nodes are children of J: K (Terminal, T=(4, 1)) and L (Terminal, T=(4, 2)). Grey boxes indicate LSIDs: above A are B(LSID=1), D(LSID=2), G(LSID=3), J(LSID=4); above B are G(LSID=3), J(LSID=4); above G is J(LSID=4).](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +graph TD + A["A: Base Node +S=(0, 0)"] --> B["B: Switch +T=(0, 3) +S=(1, 0)"] + A --> C["C: Terminal +T=(0, 1)"] + A --> D["D: Switch +T=(0, 4) +S=(2, 0)"] + A --> E["E: Terminal +T=(0, 2)"] + B --> F["F: Terminal +T=(1, 1)"] + B --> G["G: Terminal +T=(1, 2) +S=(3, 0)"] + B --> H["H: Terminal +T=(2, 1)"] + G --> I["I: Terminal +T=(3, 1)"] + G --> J["J: Terminal +T=(3, 2) +S=(4, 0)"] + J --> K["K: Terminal +T=(4, 1)"] + J --> L["L: Terminal +T=(4, 2)"] + +``` + +Figure 8-10: Switching tables example. A hierarchical tree diagram showing nodes A through L. Node A is the Base Node at Level 0 with S=(0, 0). Below it are Level 0 nodes: B (Switch, T=(0, 3), S=(1, 0)), C (Terminal, T=(0, 1)), D (Switch, T=(0, 4), S=(2, 0)), and E (Terminal, T=(0, 2)). Level 1 nodes are children of B: F (Terminal, T=(1, 1)), G (Terminal, T=(1, 2), S=(3, 0)), and H (Terminal, T=(2, 1)). Level 2 nodes are children of G: I (Terminal, T=(3, 1)) and J (Terminal, T=(3, 2), S=(4, 0)). Level 3 nodes are children of J: K (Terminal, T=(4, 1)) and L (Terminal, T=(4, 2)). Grey boxes indicate LSIDs: above A are B(LSID=1), D(LSID=2), G(LSID=3), J(LSID=4); above B are G(LSID=3), J(LSID=4); above G is J(LSID=4). + +**Figure 8-10 – Switching tables example** + +Figure 8-10 shows an example subnetwork where entries in the switching table of individual switch nodes are highlighted. In this example, when service node G receives a PRO\_REQ\_B packet for promotion, it turns into a switch node. Its switch identifier will be (PRO.NSID, 0) = (3, 0). The receipt and acceptance of PRO\_REQ\_B is acknowledged with a PRO\_ACK by G. The intermediate switch node B will sniff HDR.DO=0, PKT.CTYPE=3, PKT.SID=1 and PRO.N=0, to conclude that this is a PRO\_ACK from one of the service nodes in its own switching hierarchy. Node B will forward this packet towards the base node and it will add PRO.NSID to its switching table, as shown in Figure 8-11. + +![Figure 8-11: Fill in the switching table. A sequence diagram showing the interaction between Base Node A, Switch Node B, and Terminal G. A PRO_REQ_B packet (with HDR.DO=1, PRO.N=0, PRO.NSID=3) is sent from A to G via B. Terminal G receives it and becomes Switch G. Switch G sends a PRO_ACK packet (with HDR.DO=0, PRO.N=0, PRO.NSID=3) back to B. Switch B receives the PRO_ACK, adds the PRO.NSID to its switching table, and then forwards the PRO_ACK packet to Base Node A.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant A as BASE A + participant B as SWITCH B + participant G as TERMINAL G + A->>B: PRO_REQ_B (HDR.DO=1, PRO.N=0, PRO.NSID=3) + B->>G: PRO_REQ_B + Note over G: SWITCH G + G->>B: PRO_ACK (HDR.DO=0, PRO.N=0, PRO.NSID=3) + Note over B: Add PRO.NSID to the switching table + B->>A: PRO_ACK + +``` + +Figure 8-11: Fill in the switching table. A sequence diagram showing the interaction between Base Node A, Switch Node B, and Terminal G. A PRO\_REQ\_B packet (with HDR.DO=1, PRO.N=0, PRO.NSID=3) is sent from A to G via B. Terminal G receives it and becomes Switch G. Switch G sends a PRO\_ACK packet (with HDR.DO=0, PRO.N=0, PRO.NSID=3) back to B. Switch B receives the PRO\_ACK, adds the PRO.NSID to its switching table, and then forwards the PRO\_ACK packet to Base Node A. + +**Figure 8-11 – Fill in the switching table** + +Removing a switch table entry is more complex because of retries. Upon receipt of a demotion acknowledgement (PRO\_DEM\_x), the switching table entry corresponding to the LSID is marked as to be removed and a timer is started with a value of $((macMaxCtlRetx + 1) \times macCtlRetxTimer)$ seconds. This timer ensures that all retransmit packets which might use the LSID have left the subnetwork. When the timer expires the switch table entry is removed. + +#### 8.3.5.3 Switching process + +Switch nodes forward traffic to their control domain in a selective manner. The received data shall fulfil the conditions listed below for it to be switched. If the conditions are not met, the data shall be silently discarded. + +Downlink packets (HDR.DO=1) shall meet any of the following conditions in order to be switched: + +- Destination node of the packet is connected to the subnetwork through this switch node, i.e., PKT.SID is equal to this switch node's SID or its switching table contains an entry for PKT.SID. +- The packet has broadcast destination (PKT.LNID = 0x3FFF) and was sent by the switch this node is registered through (PKT.SID=SID of this switch node). +- The packet has a multicast destination (PKT.LNID=0x3FFE), it was sent by the switch this node is registered through (PKT.SID=SID of this switch node) and at least one of the service nodes connected to the subnetwork through this switch node is a member of the said multicast group, i.e., LCID specifies a group that is requested by any downstream node in its hierarchy. + +Uplink packets (HDR.DO=0) shall meet either of the following conditions in order to be switched: + +- The packet source node is connected to the subnetwork through this switch node, i.e. PKT.SID is equal to this switch node's SID or its switching table contains an entry for PKT.SID. +- The packet has a broadcast or multicast destination (PKT.LNID = 0x3FFF or 0x3FFE) and was transmitted by a node registered through this switch node (PKT.SID=LSID of this switch node). + +If a packet meets previous conditions, it shall be switched. For unicast packets, the only operation to be performed during switching is queueing it to be resent in a MAC PDU with the same HDR.DO. + +In the case of broadcast or multicast packets, the PKT.SID must be replaced with: + +- the switch node's LSID for downlink packets +- the switch node's SID for uplink packets. + +#### 8.3.5.4 Switching of broadcast packets + +The switching of broadcast MAC frames operates in a different manner to the switching of unicast MAC frames. Broadcast MAC frames are identified by PKT.LNID=0x3FFF. + +When HDR.DO=0, i.e., the packet is an uplink packet, it is unicast to the base node. A switch which receives such a packet should apply the scope rules to ensure that it comes from a lower level and, if so, switch it upwards towards the base. The rules given in clause 8.3.5.3 must be applied. + +When HDR.DO=1, i.e., the packet is a downlink packet, it is broadcast to the next level. A switch which receives such a packet should apply the scope rules to ensure that it comes from the higher level and, if so, switch it further to its subnetwork. The most robust PHY modulation scheme and FEC coding at the maximum output power level implemented in the device should be used so that all the devices directly connected to the switch node can receive the packet. The rules given in clause 8.3.5.3 must be applied. The service node should also pass the packet up to its MAC SAP to applications which have registered to receive broadcast packets using the MAC\_JOIN service. + +When the base node receives a broadcast packet with HDR.DO=0, it should pass the packet up its MAC SAP to applications which have registered to receive broadcast packets. The base node should also transmit the packet as a downlink packet, i.e., HDR.DO=1, using the most robust PHY modulation scheme and FEC coding at the maximum output power level and following the rules given in clause 8.3.5.3. + +#### 8.3.5.5 Switching of multicast packets + +##### 8.3.5.5.1 General + +Multicast packet switching operates in a very similar way to broadcast packet switching. Multicast is an extension of broadcast. If a switching node does not implement multicasting, it should handle all multicast packets as broadcast packets. + +Different names of MAC header and packets are used in this clause. Refer to clause 8.4.2 to find proper definitions. + +##### 8.3.5.5.2 Multicast switching table + +Switch nodes which implement multicast should maintain a multicast switching table. This table contains a list of multicast group LCIDs that have members connected to the subnetwork through the switch node. The LCID of multicast traffic in both downlink and uplink directions is checked for a matching entry in the multicast switching table. Multicast traffic is only switched if an entry corresponding to the LCID is available in the table; otherwise, the traffic is silently discarded. + +A multicast switching table is established and managed by examining the multicast join and leave messages (MUL control packet) which pass through the switch. Note that multiple service nodes from a switch node's control hierarchy may be members of the same group. + +On a successful group join from a service node in its control hierarchy, a switch node adds a new multicast switch entry for the group LCID, where necessary. + +When a successful group leave is indicated, the switch removes the NID from the multicast switch entry. If the multicast switch entry then has no NID associated with it, the multicast switch entry is immediately removed. + +switch nodes shall also examine the Keep-Alive packets being passed upwards. When a service node that is also a member of a multicast group fails the Keep-Alive process, its NID is removed from any multicast switch entries and, if necessary, the multicast switch entry is removed. + +Switch nodes should use a timer to trigger the actual removal of switch entries. The timer is started when it is decided that an entry should be removed. This timer has the value $((macMaxCtlReTx + 1) \times macCtlReTxTimer)$ . Only once the timer has expired is the multicast switch entry removed. This allows the terminal node a short amount of time to flush any remaining multicast packets before the connection is removed and the switch node implementation is simplified since it only needs to process MUL\_LEAVE\_B or MUL\_LEAVE\_S (refers to clause 8.4.5.9), but not both. + +##### 8.3.5.5.3 Switching process of multicast packets + +The multicast packet switching process depends on the packet direction. + +When HDR.DO=0 and PKT.LNID=0x3FFE, i.e., the packet is an uplink multicast packet, it is unicast towards the base node. A switch node that receives such a packet should apply the scope rules to ensure it comes from a lower hierarchical level and, if so, switch it upwards towards the base node. No LCID-based filtering is performed. All multicast packets are switched, regardless of any multicast switch entries for the LCID. The coding rate most applicable to the unicast may be used and the rules given in clause 8.3.5.3 shall be applied. + +When HDR.DO=1 and PKT.LNID=0x3FFE, i.e., the packet is a downlink multicast packet, the multicast switching table is used. If there is an entry with the LCID corresponding to PKT.LCID in the packet, the packet is switched downwards to the part of subnetwork controlled by this switch. The most robust PHY modulation scheme and FEC coding at the maximum output power level should be used so that all its devices in the lower level can receive the packet. The rules given in clause 8.3.5.3 shall be applied. If the service node is also a member of the multicast group, it should also pass the packet up its MAC SAP to applications which have registered to receive the multicast packets for that group. + +When the base node receives a multicast packet with HDR.DO=0 and it is a member of the multicast group, it should pass the packet up its MAC SAP to applications which have registered to receive multicast packets for that group. The base node should switch the multicast packet if there is an appropriate entry in its multicast switching table for the LCID, transmitting the packet as a downlink packet, i.e., HDR.DO=1, using the most robust PHY modulation scheme and FEC coding at the maximum output power level. The rules given in clause 8.3.5.3 shall be used. + +### **8.3.6 Direct connections** + +#### **8.3.6.1 Direct connection establishment** + +The direct connection establishment is a little different from a normal connection although the same packets and processes are used. It is different because the initial connection request may not be acknowledged until it is already acknowledged by the target node. It is also different because the CON\_REQ\_B packets shall carry information for the "direct switch" to update the "direct switching table". + +A direct switch is not different from a general switch. It is only a logical distinction of identifying the first common switch between two service nodes that need to communicate with each other. Note that in the absence of such a common switch, the base node would be the direct switch. + +There are two different scenarios for using directed connections. These scenarios use the network shown in Figure 8-12. + +The first is when the source node does not know the destination service node's EUI-48 address. The service node initiates a connection to the base node and the base node convergence layer redirects the connection to the correct service node. + +![Sequence diagram showing the establishment of a direct connection between Node I and Node F via Node B (direct switch) and Node G. The diagram includes messages like CON_REQ_S, MAC_CON_ESTABLISH.indication, MAC_CON_REDIRECT.response, and CON_REQ_B with detailed header information.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +The diagram illustrates the following sequence of events: + +- Node I** sends a **CON\_REQ\_S** message to **Node G**. The message contains: + - HDR.DO=0 + - PKT.SID=3 + - PKT.LNID=1 + - CON.LCID=M + - CON.D=0 + - CON.EUI48=SNA +- Node G** forwards the **CON\_REQ\_S** message to **Node B (direct switch)**. +- Node B** receives the **CON\_REQ\_S** message and sends a **MAC\_CON\_ESTABLISH.indication** to **Convergence BASE A**. +- Convergence BASE A** responds with a **MAC\_CON\_REDIRECT.response** to **Node B**. +- Node B** then sends a **CON\_REQ\_B** message to **Node F**. The message contains: + - HDR.DO=1 + - PKT.SID=1 + - PKT.LNID=1 + - CON.LCID=N + - CON.EUI48=node i + - CON.D=1 + - CON.DSSID=node b + - CON.DCNAD=0 + - CON.DCSID=3 + - CON.DCLNID=1 + - CON.DCLCID=M +- Node F** receives the **CON\_REQ\_B** message and sends a **CON\_REQ\_S** message back to **Node B**. The message contains: + - HDR.DO=0 + - PKT.SID=1 + - PKT.LNID=1 + - CON.LCID=N + - CON.D=0 + - CON.EUI48=node i +- Node B** receives the **CON\_REQ\_S** message and sends a **CON\_REQ\_B** message to **Node G**. The message contains: + - HDR.DO=1 + - PKT.SID=3 + - PKT.LNID=1 + - CON.LCID=M + - CON.EUI48=node f + - CON.D=1 + - CON.DSSID=node b + - CON.DCNAD=1 + - CON.DCSID=1 + - CON.DCLNID=1 + - CON.DCLCID=N +- Node G** forwards the **CON\_REQ\_B** message to **Node I**. + +Sequence diagram showing the establishment of a direct connection between Node I and Node F via Node B (direct switch) and Node G. The diagram includes messages like CON\_REQ\_S, MAC\_CON\_ESTABLISH.indication, MAC\_CON\_REDIRECT.response, and CON\_REQ\_B with detailed header information. + +**Figure 8-12 – Directed connection to an unknown service node** + +The steps to establish a direct connection, as shown in Figure 8-12, shall be: + +- When node I tries to establish a connection with node F, it shall send a normal connection request (CON\_REQ\_S). +- Then, due to the fact that the base node knows that F is the target service node, it should send a connection request to F (CON\_REQ\_B). This packet will carry information for direct switch B to include the connection in its direct switching table. +- F may accept the connection. (CON\_REQ\_S). +- Now that the connection with F is fully established, the base node will accept the connection with I (CON\_REQ\_B). This packet will carry information for the direct switch B to include in its direct switching table. + +After finishing this connection-establishment process, the direct switch (node B) should contain a direct switching table with the entries shown in Table 8-2. + +**Table 8-2 – Direct connection example: node B's direct switching table** + +| Uplink | | | Downlink | | | | +|--------|------|------|----------|-------|-------|-----| +| SID | LNID | LCID | DSID | DLNID | DLCID | NAD | +| 1 | 1 | N | 3 | 1 | M | 0 | +| 3 | 1 | M | 1 | 1 | N | 1 | + +The direct switching table should be updated every time a switch receives a control packet that meets the following requirements: + +- it is CON\_REQ\_B packet: HDR.DO=1, CON.TYPE=1 and CON.N=0 +- it contains "direct" information: CON.D=1 +- the direct information is for itself: CON.DSSID is the SID of the switch itself. + +Then, the direct switching table is updated with the information: + +- uplink (SID, LNID, LCID) = (PKT.SID, PKT.LNID, CON.LCID); +- downlink (SID, LNID, LCID, NAD) = (CON.DCSID, CON.DCLNID, CON.DCLCID, CON.DCNAD). + +The connection closing packets should be used to remove the entries. + +The second scenario for using directed connections is when the initiating service node already knows the destination service node's EUI-48 address. In this case, rather than using the base node's address, it uses the service node's address. In this case, the base node convergence layer is not involved. The base node MAC layer connects service node I directly to service node F. The resulting switch table entries are identical to the previous example. The exchange of signals is shown in Figure 8-13. + +![Sequence diagram showing connection establishment between Node I and Node F via Node B (direct switch).](c0c7f65c51c83fbe595b47326f6b089a_img.jpg) + +The diagram illustrates the exchange of control packets for connection establishment between Node I and Node F, mediated by Node B (labeled as a direct switch). The sequence of events is as follows: + +- Node I** sends a **CON\_REQ\_S** packet to **Node G**. The packet contains: HDR.DO=0, PKT.SID=3, PKT.LNID=1, CON.LCID=M, CON.D=0, CON.EUI48=node f. +- Node G** forwards the **CON\_REQ\_S** packet to **Node B**. +- Node B** receives the **CON\_REQ\_S** packet and sends a **CON\_REQ\_B** packet to **Node F**. The packet contains: HDR.DO=1, PKT.SID=1, PKT.LNID=1, CON.LCID=N, CON.EUI48=node i, CON.D=1, CON.DSSID=node b, CON.DCNAD=0, CON.DCSID=3, CON.DCLNID=1, CON.DCLCID=M. +- Node F** receives the **CON\_REQ\_B** packet and sends a **CON\_REQ\_S** packet back to **Node B**. The packet contains: HDR.DO=0, PKT.SID=1, PKT.LNID=1, CON.LCID=N, CON.D=0, CON.EUI48=node i. +- Node B** receives the **CON\_REQ\_S** packet and sends a **CON\_REQ\_B** packet to **Node I**. The packet contains: HDR.DO=1, PKT.SID=3, PKT.LNID=1, CON.LCID=M, CON.EUI48=node f, CON.D=1, CON.DSSID=node b, CON.DCNAD=1, CON.DCLSID=1, CON.DCLNID=1, CON.DCLCID=N. + +Sequence diagram showing connection establishment between Node I and Node F via Node B (direct switch). + +**Figure 8-13 – Example of direct connection: connection establishment to a known service node** + +#### 8.3.6.2 Direct connection release + +The release of a direct connection is shown in Figure 8-14. The signalling is very similar to connection establishment for a direct connection. The D fields are used to tell the direct switch which entries it should remove. The direct switching table should be updated every time a switch receives a control packet that meets the following requirements: + +- it is CON\_CLOSE\_B packet: HDR.DO=1, CON.TYPE=1 and CON.N=1 +- it contains "direct" information: CON.D=1 +- the direct information is for itself: CON.DSSID is the SID of the switch itself. + +Then, the direct switching table entry with the following information is removed: + +- uplink (SID, LNID, LCID) = (PKT.SID, PKT.LNID, CON.LCID); +- downlink (SID, LNID, LCID, NAD) = (CON.DCSID, CON.DCLNID, CON.DCLCID, CON.DCNAD). + +![Sequence diagram showing the release of a direct connection between BASE A and NODE I via intermediate nodes B, F, and G. The diagram illustrates the exchange of CON_CLS_S and CON_CLS_B control packets with their respective header and connection information fields.](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +The diagram illustrates the release of a direct connection between BASE A and NODE I. The sequence of events is as follows: + +- BASE A to NODE B:** BASE A sends a **CON\_CLS\_S** packet to NODE B (direct switch). +- NODE B to NODE G:** NODE B receives the packet and forwards it as a **CON\_CLS\_S** packet to NODE G. +- NODE G to NODE I:** NODE G receives the packet and forwards it as a **CON\_CLS\_S** packet to NODE I. The packet contains the following fields: + - HDR.DO=0 + - PKT.SID=3 + - PKT.LNID=1 + - CON.LCID=M + - CON.D=0 +- BASE A to NODE B:** BASE A sends a **CON\_CLS\_B** packet to NODE B. The packet contains the following fields: + - HDR.DO=1 + - PKT.SID=1 + - PKT.LNID=1 + - CON.LCID=N + - CON.D=1 + - CON.DSSID=node b + - CON.DCNAD=0 + - CON.DCSID=3 + - CON.DCLNID=1 + - CON.DCLCID=M +- NODE B to NODE F:** NODE B receives the packet and forwards it as a **CON\_CLS\_B** packet to NODE F. The packet contains the following fields: + - HDR.DO=0 + - PKT.SID=1 + - PKT.LNID=1 + - CON.LCID=N + - CON.D=0 +- BASE A to NODE B:** BASE A sends another **CON\_CLS\_B** packet to NODE B. The packet contains the following fields: + - HDR.DO=1 + - PKT.SID=3 + - PKT.LNID=1 + - CON.LCID=M + - CON.D=1 + - CON.DSSID=node b + - CON.DCNAD=1 + - CON.DCSID=1 + - CON.DCLNID=1 + - CON.DCLCID=N +- NODE B to NODE G:** NODE B receives the packet and forwards it as a **CON\_CLS\_B** packet to NODE G. +- NODE G to NODE I:** NODE G receives the packet and forwards it as a **CON\_CLS\_B** packet to NODE I. + +Sequence diagram showing the release of a direct connection between BASE A and NODE I via intermediate nodes B, F, and G. The diagram illustrates the exchange of CON\_CLS\_S and CON\_CLS\_B control packets with their respective header and connection information fields. + +Figure 8-14 – Release of a direct connection + +#### 8.3.6.3 Direct connection switching + +As explained in clause 8.3.5.3, the normal switching mechanism is intended to be used for forwarding communication data between the base node and each service node. The "direct switching" is a mechanism to let two nodes communicate with each other, switching the packets in a local way, i.e., without passing through the base node. It is not a different form of packet-switching, but rather an additional feature of the general switching process. + +The first shared switch in the paths that go from two service nodes to the base node will be called the "direct switch" for the connections between the said nodes. This is the switch that will have the possibility of performing the direct switching to make the two nodes communicate efficiently. As a special case, every switch is the "direct switch" between itself and any node that is lower down in the hierarchy. + +The "direct switching table" is a table every switch should contain in order to perform direct switching. Each entry on this table is a direct connection that must be switched directly. It is represented by the origin CID and the destination CID of the direct connection. It is not a record of every connection identifier lower down in its hierarchy, but contains only those that should be directly switched by it. The destination node's ability to receive aggregated packets shall also be included in the "direct switching table" in order to fill the PKT.NAD field. + +#### 8.3.6.4 Direct switching operation + +If a switch receives an uplink (HDR.DO=0) MAC frame that is to be switched (see clause 8.3.5.3 for the requirements) and its address is in the direct switching table, then the procedure is as follows: + +- change the (SID, LNID, LCID, NAD) by the downlink part of the entry in the direct switching table; +- queue the packet to be transmitted as a downlink packet (HDR.DO=1). + +### 8.3.7 Packet aggregation + +#### 8.3.7.1 General + +The GPDU may contain one or more packets. The functionality of including multiple packets in a GPDU is called packet aggregation. Packet aggregation is an optional part of this Recommendation and devices do not need to implement it for compliance with this Recommendation. It is however suggested that devices should implement packet aggregation in order to improve MAC efficiency. + +To maintain compatibility between devices that implement packet aggregation and ones that do not, there must be a guarantee that no aggregation takes place for packets whose data transit path from/to the base node crosses (an) intermediate service node(s) that do(es) not implement this function. Information about the aggregation capability of the data transit path is exchanged during the registration process (8.6.1). A registering service node notifies this capability to the base node in the REG.CAP\_PA field (1 bit, see Table 8-8) of its REG\_REQ message. It gets feedback from the base node on the aggregation capability of the whole Downlink transit path in the REG.CAP\_PA field of the REG\_RSP message. + +Based on initial information exchanged on registration, each subsequent data packet in either direction contains aggregation information in the PKT.NAD field. In the Downlink direction, the base node will be responsible for filling PKT.NAD based on the value it communicated to the destination service node in the REG.CAP\_PA field of the REG\_RSP message. Likewise, for uplink data, the source service node will fill PKT.NAD based on the REG.CAP\_PA field received in the initial REG\_RSP from the base node. The last switch shall use the PKT.NAD field to avoid packet aggregation when forwarding the packet to destination service nodes without packet aggregation capability. Intermediate switch nodes should have information about the aggregation capability in their switching table and shall not aggregate packets when it is known that next level switch node does not support this feature. + +Devices that implement packet aggregation shall ensure that the size of the MSDU comprising the aggregates does not exceed the maximum capacity of the most robust transmission scheme of a PHY burst. The most robust transmission scheme refers to the most robust combination of modulation scheme and convolutional coding. + +#### 8.3.7.2 Packet aggregation when switching + +Switch nodes maintain information on the packet aggregation capability of all entries in their switching table, i.e., of all switches that are connected to the subnetwork through them. This capability information is then used during traffic switching to/from the connected switch nodes. + +The packet aggregation capability of a connecting switch node is registered at each transit switch node at the time of its promotion by sniffing relevant information in the PRO\_ACK message. + +- If the PKT.SID in a PRO\_ACK message is the same as the switching node, the node being promoted is connected directly to the said switch node. The aggregation capability of this new switch node is registered as the same as indicated in PKT.NAD of the PRO\_ACK packet. +- If the PKT.SID in a PRO\_ACK message is different from the SID of the switching node, it implies that the node being promoted is indirectly connected to this switch. The aggregation capability for this new switch node will thus be the same as the aggregation capability registered for its immediate switch, i.e., PKT.SID. + +Aggregation while switching packets in the uplink direction is performed if the node performing the switch knows that its uplink path is capable of handling aggregated packets, based on capability information exchanged during registration (REG.CAP\_PA field in REG\_RSP message). + +Downlink packets are aggregated by analysing the following: + +- If the PKT.SID is the same as the switching node, then it is the last switching level and the packet will arrive at its destination. In this case, the packet may be aggregated if PKT.NAD=0. +- If the PKT.SID is different, this is not the last level and another switch will receive the packet. The information of whether or not the packet could be aggregated should be extracted from the switching table. + +### 8.3.8 Security + +#### 8.3.8.1 General + +The security functionality provides the MAC layer with privacy, authentication and data integrity through a secure connection method and a key management policy. All packets must use the negotiated security profile. The only exceptions to this rule are the REG and SEC control messages, and the BPDU and PNPDU PDUs which are transferred non-encrypted. + +#### 8.3.8.2 Security profiles + +Several security profiles are provided for managing different security needs, which can arise in different network environments. This version of the Recommendation lists two security profiles and leaves scope for adding up to two new security profiles in future versions. + +##### 8.3.8.2.1 Security profile 0 + +Communications which have the security profile 0 are based on the transmission of MAC SDUs without encryption. This profile may be used in application scenarios where either sufficient security is provided by upper communication layers or where security is not a major requirement for application use-case. + +##### 8.3.8.2.2 Security profile 1 + +###### 8.3.8.2.2.1 General + +Security profile 1 is based on 128-bit AES encryption of data and its associated CRC. This profile is specified with the aim of fulfilling all security requirements: + +- Privacy is guaranteed by the encryption itself and by the fact that the encryption key is kept secret. +- Authentication is guaranteed by the fact that each node has its own secret key known only by the node itself and the base node. +- Data integrity is guaranteed by the fact that the payload CRC is encrypted. + +###### 8.3.8.2.2.2 Cryptographic primitives + +The cryptographic algorithm used in this Recommendation is the AES, as specified in [PUB 197]. The specification describes the algorithm with three possible key sizes; the 128-bit secret key represents a good level of security for preserving privacy up to 2030 and beyond, as specified in [SP 800-57], page 66, Table 4. + +AES is used according to the so-called ECB, as specified in [SP 800-38A]. It is a block-ciphering mode where plain text is divided into 128-bit blocks. Padding is applied if the last block is smaller than 128 bits. Padding is implemented with the addition of a bit equal to 1 and as many zeroes as necessary to reach a length of the string to be encrypted as a multiple of 128 bits. Encryption is performed one block at a time using the same working key for all the data. + +###### 8.3.8.2.2.3 Key derivation algorithm + +The method for deriving working keys from secret keys is to apply the AES algorithm to a constant (C) as plain text and generation key (GK) as an encryption key. If the constant is shorter than 128 bits, it must be aligned to the LSB, as shown in Figure 8-15. The various key derivation equations specified in the following clauses follow the convention: + +$$\text{Generated Key} = \text{AES\_enc} (\text{Generation Key}, \text{Constant})$$ + +![Diagram illustrating the key derivation concept. A 'Constant' block (with 'Padding' on its left) is input to an 'AES' block. A 'Generation Key' is also input to the 'AES' block. The output of the 'AES' block is the 'Generated Key'.](42c65f5cb106938992fc73c05c8713d2_img.jpg) + +The diagram shows a 'Constant' block at the top, which is divided into 'Padding' and 'Constant'. An arrow points from the 'Constant' part of this block down to an 'AES' block. To the left of the 'AES' block, an arrow labeled 'Generation Key' points into it. An arrow points from the bottom of the 'AES' block down to a 'Generated Key' block at the bottom. + +Diagram illustrating the key derivation concept. A 'Constant' block (with 'Padding' on its left) is input to an 'AES' block. A 'Generation Key' is also input to the 'AES' block. The output of the 'AES' block is the 'Generated Key'. + +Figure 8-15 – Key derivation concept + +#### 8.3.8.3 Negotiation of the security profile + +All MAC data, including signalling PDUs (all MAC control packets defined in clause 8.4.5) use the same security profile. This profile is negotiated during the device registration. In the REG\_REQ message the terminal indicates a security profile it is able to support in the field REG.SPC. The base node may accept this security profile and so accept the registration, sending back a REG\_RSP with the same REG.SPC value. The base node may also accept the registration, however it sets REG.SPC to 0 indicating that security profile 0 is to be used. Alternatively, the base node may reject the registration if the terminal does not provide an acceptable security profile. + +It is recommended that the terminal first attempts to register using the highest security profile it supports and only use lower security profiles when the base node rejects the registration request. + +#### 8.3.8.4 Key hierarchy + +##### 8.3.8.4.1 Security profile 0 + +Not applicable. + +##### 8.3.8.4.2 Security profile 1 + +Service nodes and base nodes use a set of three working keys to encrypt all data. The keys and their respective usage are: + +Initial working key (WK0): This key has limited scope and is used to decrypt the REG.SNK and REG.AUK fields of the REG\_RSP message. The WK0 is thus used by a service node in a disconnected functional state. This key is computed using the following formula: + +$$WK0 = \text{AES\_enc} (USK, 0)$$ + +Working key (WK): This key is used to encrypt all the unicast data that is transmitted from the base node to a service node and vice versa. Each registered service node would have a unique WK that is known only to the base node and itself. The WK is computed as follows: + +$$WK = \text{AES\_enc} (USK, \text{Random sequence received in SEC.RAN})$$ + +Subnetwork working key (SWK): The SWK is shared by the entire subnetwork. To ensure the security of this key, it is never transmitted over the physical channel, but is computed from other keys which are transmitted encrypted in REG and non-encrypted in SEC control packets. The SWK shall be used to encrypt the following: + +- broadcast data, including MAC broadcast control packets +- multicast data +- unicast data that is transacted over direct connections, i.e., not involving the base node. + +The SWK is computed as follows: + +$$SWK = \text{AES\_enc} (SNK, \text{Random sequence received in SEC.SNK})$$ + +The WK and the SWK have a limited validity time related to the random sequence generation period. The random sequence is regenerated and distributed by the base node at least every *MACRandSeqChgTime* seconds through the SEC control packet. If a device does not receive an update of a random sequence within $2 \times \text{MACRandSeqChgTime}$ , it should consider the WK and SWK as no longer valid. Lack of availability of WK will render service node to very limited functionality of unregistering from the subnetwork. It is therefore advised that in such cases, service nodes should unregister from the network and initiate a re-registration procedure. + +The key derivation procedures have been designed to be indirect and multi-staged to ensure security. The parameters involved in the derivation of the working keys are defined below. + +Master key (MK1, MK2). Two master keys (MK1 and MK2) are defined in this Recommendation. MK1 is used to compute the DSK. MK2 is used to compute the KDIV. Both of these keys are administered on the base node by implementation-dependent means that are beyond the scope of this Recommendation. Specifying two master keys makes the USK generation a two stage process, i.e., derivation of DSK and KDIV in the first stage and using them to derive the USK in the second stage. Note that the DSK and KDIV are unique to each registering service node. + +Device secret key (DSK). DSK is unique to each service node on the subnetwork and is hard-coded in the device during production. The DSK is constant for the entire life of the service node. The base node uses MK1 to derive service node-specific DSK using the following equation: + +$$DSK = \text{AES\_enc} (MK1, \text{UI})$$ + +Key diversifier (KDIV). This quantity is also unique to each service node, but unlike DSK, it does not have to be a fixed constant for the entire life of the service node. The KDIV is provisioned on each service node by means that are beyond the scope of this Recommendation. The base node computes device-specific KDIV using the equation: + +$$KDIV = \text{AES\_enc} (MK2, UI)$$ + +Unique secret key (USK). The USK is used to derive WK0 and WK as defined in the above equations. The USK is in turn computed by applying AES to KDIV, using DSK as the generation key, as shown in the equation below. Note that this is a single-step process in service nodes because both KDIV and DSK are already known or provisioned, but a three-step process in the base node. The first two steps in the base node comprise deriving the DSK and KDIV using the MK1 and MK2, respectively. + +$$USK = \text{AES\_enc} (DSK, KDIV)$$ + +Unique identifier (UI): The UI of a service node shall be its EUI-48. + +#### 8.3.8.5 Key distribution and management + +The security profile for data traffic is negotiated when a device is registered. The REG control packet contains specific fields to indicate the security profile for respective devices. All connections to/from the device would be required to follow the security profile negotiated at the time of registration. There cannot be a difference in security profiles across multiple connections involving the same device. The only exception to this would be the base node. + +The SWK used as a working key for non-unicast traffic and direct connections is never transmitted in non-encrypted form over the physical channel. The SEC broadcast messages transmitted by the base node (and relayed by all switch nodes) at regular intervals contain random keys for both unicast and non-unicast traffic. When a device initially registers on a subnetwork, the REG response from the base node contains the random sequence used to derive WK for unicast traffic. The REG message is followed by a unicast SEC message from the base node to the registering device. + +#### 8.3.8.6 Encryption + +##### 8.3.8.6.1 Security profile 0 + +Not applicable. + +##### 8.3.8.6.2 Security profile 1 + +Connections working with "Security profile 1" would always transmit a CRC with every packet. This field shall be called SCRC (security CRC) and is calculated over the unencrypted packet payload. The SCRC helps confirm the integrity of the packet on its decryption at the receiving end. + +The SCRC shall be calculated as the remainder of the division (Modulo 2) by the generator polynomial $g(x)=x^8+x^2+x+1$ of the polynomial $x_8$ multiplied by the unencrypted packet payload. + +The data block obtained by the concatenation of the unencrypted payload of the packet and the calculated SCRC is padded with a 1 followed by as many zeroes as necessary to reach a multiple of 128 and then divided into 128-bit blocks. The 1 inserted as the first padding bit is useful to detect the start of the padding at the receiver without notification of the number of padded bits. + +Each 128-bit block is encrypted with the AES algorithm using a valid working key. The result of this encryption process is the encrypted payload of the packet. + +![Figure 8-16: Security profile 1 encryption algorithm diagram. The diagram shows the process of encrypting a packet. At the top, a 'Packet header' is followed by a 'Clear packet payload', which is then followed by 'SCRC' and '10.. PAD'. A bracket under the 'Clear packet payload' and 'SCRC' labels it as 'Data to encrypt'. This data is input to an 'AES' block. The output of the 'AES' block is 'Encrypted data'. At the bottom, the 'Packet header' is followed by the 'Encrypted packet payload'.](c2c4e63ebb9afc1ab64e39a159890e0f_img.jpg) + +Figure 8-16: Security profile 1 encryption algorithm diagram. The diagram shows the process of encrypting a packet. At the top, a 'Packet header' is followed by a 'Clear packet payload', which is then followed by 'SCRC' and '10.. PAD'. A bracket under the 'Clear packet payload' and 'SCRC' labels it as 'Data to encrypt'. This data is input to an 'AES' block. The output of the 'AES' block is 'Encrypted data'. At the bottom, the 'Packet header' is followed by the 'Encrypted packet payload'. + +Figure 8-16 – Security profile 1 encryption algorithm + +## 8.4 MAC PDU format + +### 8.4.1 General + +There are different types of MAC PDUs for different purposes. + +### 8.4.2 Generic MAC PDU + +#### 8.4.2.1 General + +Most subnetwork traffic comprises generic MAC PDUs (GPDU). GPDUs are used for all data traffic and most control traffic. All MAC control packets are transmitted as GPDUs. + +GPDU composition is shown in Figure 8-17. It is composed of a generic MAC header followed by one or more MAC packets and a 32 bit CRC appended at the end. + +![Figure 8-17: Generic MAC PDU format diagram. The diagram shows a sequence of fields: 'Generic MAC header', 'Packet 1', 'Packet 2', '...', 'Packet N', and 'CRC'.](b5987d63203a5fa601921039922ac520_img.jpg) + +Figure 8-17: Generic MAC PDU format diagram. The diagram shows a sequence of fields: 'Generic MAC header', 'Packet 1', 'Packet 2', '...', 'Packet N', and 'CRC'. + +Figure 8-17 – Generic MAC PDU format + +#### 8.4.2.2 Generic MAC header + +The generic MAC header format is represented in Table 8-3. The size of the generic MAC header is 3 bytes. Table 8-3 enumerates each field of a generic MAC header. + +![Figure 8-18: Generic MAC header diagram. The diagram shows a 3-byte header structure. The first byte is split into 'Unused' (MSB) and 'HDR.DO' (LSB). The second byte is split into 'HDR.HT' (MSB) and 'Reserved' (LSB). The third byte is split into 'HDR.LEVEL' (MSB) and 'HDR.HCS' (LSB).](9dd03da031e134bfc9ecc730dd5f6583_img.jpg) + +| | | | | | | +|-----------------|--------|---------|--|-----------------|--| +| MSB | | | | | | +| Unused | | HDR.HT | | Reserved | | +| Reserved | HDR.DO | | | HDR.LEVEL | | +| | | HDR.HCS | | | | +| | | | | LSB | | + +Figure 8-18: Generic MAC header diagram. The diagram shows a 3-byte header structure. The first byte is split into 'Unused' (MSB) and 'HDR.DO' (LSB). The second byte is split into 'HDR.HT' (MSB) and 'Reserved' (LSB). The third byte is split into 'HDR.LEVEL' (MSB) and 'HDR.HCS' (LSB). + +Figure 8-18 – Generic MAC header + +**Table 8-3 – Generic MAC header fields** + +| Name | Length | Description | +|-----------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unused | 2 bits | Unused bits which are always 0; included for alignment with MAC_H field in the PPDU header (see clause 7.4.3). | +| HDR.HT | 2 bits | Header type
HDR.HT = 0 for GPDU | +| Reserved | 5 bits | Always 0 for this version of the Recommendation. Reserved by ITU-T. | +| HDR.DO | 1 bit | Downlink/uplink
  • HDR.DO=1 if the MAC PDU is downlink
  • HDR.DO=0 if the MAC PDU is uplink
| +| HDR.LEVEL | 6 bits | Level of the PDU in switching hierarchy
The packets between the level 0 and the base node are of HDR.LEVEL=0. The packets between levels k and k-1 are of HDR.LEVEL=k.
  • If HDR.DO=0, HDR.LEVEL represents the level of the transmitter of this packet.
  • If HDR.DO=1, HDR.LEVEL represents the level of the receiver of this packet.
| +| HDR.HCS | 8 bits | Header check sequence
A field for detecting errors in the header and checking that this MAC PDU is from this subnetwork. The transmitter shall calculate the CRC of the SNA concatenated with the first 2 bytes of the header and insert the result into the HDR.HCS field (the last byte of the header). The CRC shall be calculated as the remainder of the division (Modulo 2) of the polynomial $M(x) \cdot x^8$ by the generator polynomial $g(x)=x^8+x^2+x+1$ . $M(x)$ is the input polynomial, which is formed by the bit sequence of the concatenation of the SNA and the header excluding the HDR.HCS field, and the MSB of the bit sequence is the coefficient of the highest order of $M(x)$ . | + +#### 8.4.2.3 Packet structure + +A packet is comprised of a packet header and packet payload. Figure 8-19 shows the structure. + +![](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +| | | +|---------------|----------------| +| Packet header | Packet payload | +|---------------|----------------| + +**Figure 8-19 – Packet structure** + +Packet header is 6 bytes in length and its composition is shown in Figure 8-20. Table 8-4 enumerates the description of each field. + +![](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +MSB + +| | | | | | | | | +|----------------|---------|----------|----------|-----------------------|--|--|--| +| Reserved | PKT.NAD | PKT.PRIO | PKT.C | PKT.LCID or PKT.CTYPE | | | | +| PKT.SID | | | | PKT.LNID[13..6] | | | | +| PKT.LNID[5..0] | | | PKT.SPAD | PKT.LEN | | | | + +LSB + +**Figure 8-20 – Packet header** + +To simplify, the text contains references to the PKT.NID fields as the composition of the PKT.SID and PKT.LNID. The field PKT.CID is also described as the composition of the PKT.NID and the PKT.LCID. The composition of these fields is described in Figure 8-21. + +![Diagram of PKT.CID structure showing three fields: PKT.SID (8 bits), PKT.LNID (14 bits), and PKT.LCID (9 bits). PKT.SID is labeled MSB and PKT.LCID is labeled LSB. PKT.NID (22 bits) is the concatenation of PKT.SID and PKT.LNID. PKT.CID (31 bits) is the concatenation of PKT.NID and PKT.LCID.](7e14467740b2570a44379b347a697921_img.jpg) + +Diagram of PKT.CID structure showing three fields: PKT.SID (8 bits), PKT.LNID (14 bits), and PKT.LCID (9 bits). PKT.SID is labeled MSB and PKT.LCID is labeled LSB. PKT.NID (22 bits) is the concatenation of PKT.SID and PKT.LNID. PKT.CID (31 bits) is the concatenation of PKT.NID and PKT.LCID. + +**Figure 8-21 – PKT.CID structure** + +**Table 8-4 – Packet header fields** + +| Name | Length | Description | +|-------------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 3 bits | Always 0 for this version of the Recommendation. Reserved by ITU-T. | +| PKT.NAD | 1 bit | No aggregation at destination
  • If PKT.NAD=0 the packet may be aggregated with other packets at destination.
  • If PKT.NAD=1 the packet may not be aggregated with other packets at destination.
| +| PKT.PRIO | 2 bits | Indicates a packet priority between 0 and 3 | +| PKT.C | 1 bits | Control
  • If PKT.C=0 it is a data packet.
  • If PKT.C=1 it is a control packet.
| +| PKT.LCID /
PKT.CTYPE | 9 bits | Local connection identifier or control type
  • If PKT.C=0, PKT.LCID represents the local connection identifier of a data packet.
  • If PKT.C=1, PKT.CTYPE represents the type of the control packet.
| +| PKT.SID | 8 bits | Switch identifier
  • If HDR.DO=0, PKT.SID represents the SID of the packet source.
  • If HDR.DO=1, PKT.SID represents the SID of the packet destination.
| +| PKT.LNID | 14 bits | Local node identifier
  • If HDR.DO=0, PKT.LNID represents the LNID of the packet source.
  • If HDR.DO=1, PKT.LNID represents the LNID of the packet destination.
| +| PKT.SPAD | 1bit | Indicates if padding is inserted while encrypting payload. Note that this bit is only of relevance when security profile 1 (see clause 8.3.8.2.2) is used. | +| PKT.LEN | 9 bits | Length of the packet payload in bytes | + +#### 8.4.2.4 CRC + +The CRC is the last field of the GPDU. It is 32 bits long. It is used to detect transmission errors. The CRC shall cover the concatenation of the SNA with the GPDU except for the CRC field itself. + +The input polynomial $M(x)$ is formed as a polynomial whose coefficients are bits of the data being checked (the first bit to check is the highest order coefficient and the last bit to check is the coefficient of order zero). The generator polynomial for the CRC is $G(x)=x^{32}+x^{26}+x^{23}+x^{22}+x^{16}+x^{12}+x^{11}+x^{10}+x^8+x^7+x^5+x^4+x^2+x+1$ . The remainder $R(x)$ is calculated as the remainder from the division of $M(x)\cdot x^{32}$ by $G(x)$ . The coefficients of the remainder will then be the resulting CRC. + +### 8.4.3 Promotion needed PDU + +If a node is disconnected and it does not have connectivity with any existing switch node, it shall send notifications to its neighbours to indicate the need for the promotion of any available terminal node. Figure 8-22 represents the promotion needed MAC PDU (PNPDU) that must be sent on an irregular basis in this situation. + +![Figure 8-22: Promotion need MAC PDU structure diagram. The diagram shows a grid of 14 bytes (7 rows of 2 bytes each). Row 1: Unused (2 bits), HDR.HT (2 bits), Reserved (4 bits), PNH.SNA[0] (8 bits). Row 2: PNH.SNA[1] (8 bits), PNH.SNA[2] (8 bits). Row 3: PNH.SNA[3] (8 bits), PNH.SNA[4] (8 bits). Row 4: PNH.SNA[5] (8 bits), PNH.PNA[0] (8 bits). Row 5: PNH.PNA[1] (8 bits), PNH.PNA[2] (8 bits). Row 6: PNH.PNA[3] (8 bits), PNH.PNA[4] (8 bits). Row 7: PNH.PNA[5] (8 bits), PNH.HCS (8 bits). MSB is top-left, LSB is bottom-right.](107c8e1abcb7033ad244e30e7a910045_img.jpg) + +| | | | | | | | | +|--------------------|-------------|----------------------|--|-----------------|--|--|--| +| MSB | | | | | | | | +| Unused (2b) | HDR.HT (2b) | Reserved (4b) | | PNH.SNA[0] (8b) | | | | +| PNH.SNA[1] (8b) | | | | PNH.SNA[2] (8b) | | | | +| PNH.SNA[3] (8b) | | | | PNH.SNA[4] (8b) | | | | +| PNH.SNA[5] (8b) | | | | PNH.PNA[0] (8b) | | | | +| PNH.PNA[1] (8b) | | | | PNH.PNA[2] (8b) | | | | +| PNH.PNA[3] (8b) | | | | PNH.PNA[4] (8b) | | | | +| PNH.PNA[5] (8b) | | | | PNH.HCS (8b) | | | | +| | | | | LSB | | | | + +Figure 8-22: Promotion need MAC PDU structure diagram. The diagram shows a grid of 14 bytes (7 rows of 2 bytes each). Row 1: Unused (2 bits), HDR.HT (2 bits), Reserved (4 bits), PNH.SNA[0] (8 bits). Row 2: PNH.SNA[1] (8 bits), PNH.SNA[2] (8 bits). Row 3: PNH.SNA[3] (8 bits), PNH.SNA[4] (8 bits). Row 4: PNH.SNA[5] (8 bits), PNH.PNA[0] (8 bits). Row 5: PNH.PNA[1] (8 bits), PNH.PNA[2] (8 bits). Row 6: PNH.PNA[3] (8 bits), PNH.PNA[4] (8 bits). Row 7: PNH.PNA[5] (8 bits), PNH.HCS (8 bits). MSB is top-left, LSB is bottom-right. + +Figure 8-22 – Promotion need MAC PDU + +Table 8-5 shows the promotion need MAC PDU fields. + +Table 8-5 – Promotion need MAC PDU fields + +| Name | Length | Description | +|-----------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unused | 2 bits | Unused bits which are always 0; included for alignment with MAC_H field in the PPDU header (see clause 7.4.3). | +| HDR.HT | 2 bits | Header type
HDR.HT = 1 for the promotion need MAC PDU | +| Reserved | 4 bits | Always 0 for this version of the Recommendation. Reserved by ITU-T. | +| PNH.SNA | 48 bits | Subnetwork address
The EUI-48 of the base node of the subnetwork the service node is trying to connect to. FF:FF:FF:FF:FF:FF to ask for the promotion in any available subnetwork.
SNA[0] is the most significant byte of the OUI/IAB and SNA[5] is the least significant byte of the extension identifier, as defined in:
http://standards.ieee.org/regauth/oui/tutorials/EUI-48.html .
The above notation is applicable to all EUI-48 fields in the specification. | +| PNH.PNA | 48 bits | Promotion need address. The EUI-48 of the node that needs the promotion. It is the EUI-48 of the transmitter. | +| PNH.HCS | 8 bits | Header check sequence. A field for detecting errors in the header. The transmitter shall calculate the PNH.HCS of the first 13 bytes of the header and insert the result into the PNH.HCS field (the last byte of the header). It shall be calculated as the remainder of the division (Modulo 2) of the polynomial $M(x) \cdot x^8$ by the generator polynomial $g(x)=x^8+x^2+x+1$ . M ( x ) is the input polynomial, which is formed by the bit sequence of the header excluding the PNH.HCS field, and the MSB of the bit sequence is the coefficient of the highest order of M ( x ). | + +As it is always transmitted by unsynchronized nodes and therefore, prone to creating collisions, it is a special reduced size header. It is broadcast to any other terminal node and shall therefore be transmitted with the most robust scheme of the PHY layer. + +### 8.4.4 Beacon PDU + +Beacon PDU (BPDU) is transmitted by every switch device on the subnetwork, including the base node. The purpose of this PDU is to circulate information on MAC frame structure and therefore channel access to all devices that are part of this subnetwork. The BPDU is transmitted at definite fixed intervals of time and is also used as a synchronization mechanism by service nodes. Figure 8-23 below shows contents of a beacon transmitted by the base node and each switch device. + +![](52c40e2f443985dc63f45dec57d90c8c_img.jpg) + +MSB + +| | | | | | | | | | +|----------|--------|------------|----------|-------------|---------|------------|--|---------| +| Unused | HDR.HT | Reserved | BCN.QLTY | | | BCN.SID | | | +| BCN.CNT | | BCN.POS | | | | BCN.CFP | | | +| Reserved | | BCN.LEVEL | | | BCN.SEQ | | | BCN.FRQ | +| | | BCN.SNA[0] | | | | BCN.SNA[1] | | | +| | | BCN.SNA[2] | | | | BCN.SNA[3] | | | +| | | BCN.SNA[4] | | | | BCN.SNA[5] | | | +| | | BCN.UPCOST | | | | BCN.DNCOST | | | +| | | | | CRC[31..16] | | | | | +| | | | | CRC[15..0] | | | | | + +LSB + +Figure 8-23 – Beacon PDU structure + +Table 8-6 shows the beacon PDU fields. + +Table 8-6 – Beacon PDU fields + +| Name | Length | Description | +|-----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Unused | 2 bits | Unused bits which are always 0; included for alignment with MAC_H field in the PPDU header (see clause 7.4.3). | +| HDR.HT | 2 bits | Header type
HDR.HT = 2 for Beacon PDU | +| Reserved | 1 bit | Always 0 for this version of the Recommendation. Reserved by ITU-T. | +| BCN.QLTY | 3 bits | Quality of round-trip connectivity from this switch node to the base node.
BCN.QLTY=7 for best quality (base node or very good switch node),
BCN.QLTY=0 for worst quality (switch having unstable connection to subnetwork) | +| BCN.SID | 8 bits | Switch identifier of transmitting switch | +| BCN.CNT | 3 bits | Number of beacon slots in this frame | +| BCN.SLT | 3 bits | Beacon slot in which this BPDU is transmitted
BCN.SLT=0 is reserved for the base node | +| BCN.CFP | 10 bits | Offset of CFP from start of frame
BCN.CFP=0 indicates absence of CFP in a frame. | +| Reserved | 1 bit | Always 0 for this version of the Recommendation. Reserved by ITU-T. | +| BCN.LEVEL | 6 bits | Hierarchy of transmitting switch in the subnetwork | + +**Table 8-6 – Beacon PDU fields** + +| Name | Length | Description | +|------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BCN.SEQ | 5 bits | Sequence number of this BPDU in the superframe. Incremented for every beacon the base node sends and is propagated by switch through its BPDU so that the entire subnetwork has the same notion of sequence number at a given time. | +| BCN.FRQ | 3 bits | Transmission frequency of this BPDU. Values are interpreted as follows:
0 = 1 beacon every frame
1 = 1 beacon every 2 frames
2 = 1 beacon every 4 frames
3 = 1 beacon every 8 frames
4 = 1 beacon every 16 frames
5 = 1 beacon every 32 frames
6 = Reserved by ITU-T
7 = Reserved.by ITU-T. | +| BCN.SNA | 48 bits | Subnetwork identifier in which the switch transmitting this BPDU is located. | +| BCN.UPCOST | 8 bits | Total uplink cost from the transmitting switch node to the base node. The cost of a single hop is calculated based on the modulation scheme used on that hop in the uplink direction. Values are derived as follows:
8PSK = 0
QPSK = 1
BPSK = 2
8PSK_F = 1
QPSK_F = 2
BPSK_F = 4.
The base node will transmit in its beacon a BCN.UPCOST of 0. A switch node will transmit in its beacon the value of BCN.UPCOST received from its upstream switch node, plus the cost of the upstream uplink hop to its upstream switch. When this value is larger than what can be held in BCN.UPCOST the maximum value of BCN.UPCOST should be used. | +| BCN.DNCOST | 8 bits | Total downlink cost from the base node to the transmitting switch node. The cost of a single hop is calculated based on the modulation scheme used on that hop in the downlink direction. Values are derived as follows:
8PSK 0
QPSK 1
BPSK 2
8PSK_F 1
QPSK_F 2
BPSK_F 4.
The base node will transmit in its beacon a BCN.DNCOST of 0. A switch node will transmit in its beacon the value of BCN.DNCOST received from its upstream switch node, plus the cost of the upstream downlink hop from its upstream switch. When this value is larger than what can be held in BCN.DNCOST the maximum value of BCN.DNCOST should be used. | +| CRC | 32 bits | The CRC shall be calculated with the same algorithm as the one defined for the CRC field of the MAC PDU (see clause 8.4.2.4 for details). This CRC shall be calculated over the complete BPDU except for the CRC field itself. | + +The BPDU is also used to detect when the uplink switch is no longer available either by a change in the characteristics of the medium or because of failure etc. If a service node fails to receive Nmiss-beacon in a row it should declare the link to its switch as unusable. The service node should stop sending beacons itself if it is acting as a switch. It should close all existing MAC connections. The service node then enters the initial unregistered functional state and searches for a subnetwork join. This mechanism complements the keep-alive mechanism which is used by a base node and its switches to determine when a service node is lost. + +### 8.4.5 MAC control packets + +#### 8.4.5.1 General + +MAC control packets enable a service node to communicate control information with their switch node, base node and vice versa. A control packet is transmitted as a GPDU and is identified with the PKT.C bit set to 1 (See clause 8.4.2 for more information about the fields of the packets). + +There are several types of control messages. Each control message type is identified by the field PKT.CTYPE. Table 8-7 lists the types of control messages. The packet payload (see clause 8.4.2.3) shall contain the information carried by the control packets. This information differs depending on the packet type. + +**Table 8-7 – MAC control packet types** + +| Type
(PKT.CTYPE) | Packet
name | Packet description | +|---------------------|----------------|--------------------------------| +| 1 | REG | Registration management | +| 2 | CON | Connection management | +| 3 | PRO | Promotion management | +| 4 | BSI | Beacon slot indication | +| 5 | FRA | Frame structure change | +| 6 | CFP | Contention-free period request | +| 7 | ALV | Keep-alive | +| 8 | MUL | Multicast management | +| 9 | PRM | PHY robustness management | +| 10 | SEC | Security information | + +#### 8.4.5.2 Control packet retransmission + +For recovery from lost control messages, a retransmit scheme is defined. MAC control transactions comprising of exchange of more than one control packet may follow the retransmission mechanism described in this clause. + +The retransmission scheme shall be applied to the following packets when they require a response: + +- CON\_REQ\_S, CON\_REQ\_B +- CON\_CLS\_S, CON\_CLS\_B +- REG\_RSP +- PRO\_REQ\_B +- BSI\_IND +- MUL\_JOIN\_S, MUL\_JOIN\_B +- MUL\_LEAVE\_S, MUL\_LEAVE\_B. + +Devices involved in a MAC control transaction using the retransmission mechanism shall keep count of the number of times a message has been retransmitted and maintain a retransmit timer. + +At the requester of a control message transaction: + +- When the first message in a transaction is transmitted, the retransmit timer is started with the value *macCtlRetxTimer* and the retransmit count is set to 0. + +If a response message is received the retransmit timer is stopped and the transaction is considered complete. Note that it is possible to receive further response messages. These would be messages that encountered network delays. + +- If the retransmit timer expires, the retransmit counter is incremented. If the retransmit counter is less than *macMaxCtlRetx* the control message is retransmitted. If the counter is equal to the maximum number of retransmits, the failure result corresponding to the respective MAC-SAP should be returned to the calling entity. Implementations may also choose to inform their local management entity of such a failure. If the retransmission is done by the service node, the device should return to the disconnected state. + +At the responder of a control message transaction: + +- The receiver of a message must determine itself if this message is a retransmit. If so, no local action is needed other than sending a reply to the response. + +If the received message is not a retransmit, the message should be processed and a response returned to the sender. + +- For transactions which use three messages in the transaction, e.g., promotion as shown in clause 8.6.3, the responder should perform retransmits in exactly the same way as the requester. This ensures that if the third message in the transaction is lost, the message will be retried and the transaction completed. + +The following message sequence charts show some examples of retransmission. Figure 8-24 shows two successful transactions without requiring retransmits. + +![Sequence diagram showing two successful control message transactions between a BASE, SWITCH, and NODE without retransmits.](a04291a026e9ac4a7b644e556a0672b4_img.jpg) + +The diagram illustrates two successful control message transactions between three entities: BASE, SWITCH, and NODE. The sequence of messages is as follows: + +- Transaction 1:** + - BASE sends **CON\_REQ\_S** to SWITCH. + - SWITCH sends **CON\_REQ\_B** to NODE. The message includes headers: `HDR.DO=1`, `CON.N=0`, `CON.LCID=K`, `CON.EUI48=SNA`. + - NODE receives **CON\_REQ\_B** and responds with **CON\_REQ\_S**. The message includes headers: `HDR.DO=0`, `CON.N=0`, `CON.LCID=K`, `CON.EUI48=SNA`. + - SWITCH receives **CON\_REQ\_S** and responds with **CON\_REQ\_B** to BASE. The message includes headers: `HDR.DO=1`, `CON.N=0`, `CON.LCID=K`, `CON.EUI48=SNA`. + - BASE receives **CON\_REQ\_B**. +- Transaction 2:** + - BASE sends **CON\_REQ\_S** to SWITCH. + - SWITCH sends **CON\_REQ\_B** to NODE. The message includes headers: `HDR.DO=1`, `CON.N=0`, `CON.LCID=L`, `CON.EUI48=SNA`. + - NODE receives **CON\_REQ\_B** and responds with **CON\_REQ\_S**. The message includes headers: `HDR.DO=0`, `CON.N=0`, `CON.LCID=L`, `CON.EUI48=SNA`. + - SWITCH receives **CON\_REQ\_S** and responds with **CON\_REQ\_B** to BASE. The message includes headers: `HDR.DO=1`, `CON.N=0`, `CON.LCID=L`, `CON.EUI48=SNA`. + - BASE receives **CON\_REQ\_B**. + +Sequence diagram showing two successful control message transactions between a BASE, SWITCH, and NODE without retransmits. + +Figure 8-24 – Two transactions without requiring retransmits + +Figure 8-25 shows a more complex example, where messages are lost in both directions causing multiple retransmits before the transaction completes. + +![Sequence diagram for Figure 8-25 showing a transaction with packet loss and retransmits between a Base, Switch, and Node.](29fbbed4c4aff19e9ac5bf98e0c9b24d_img.jpg) + +This sequence diagram illustrates a transaction between a BASE, a SWITCH, and a NODE. The interaction involves multiple retransmits due to packet loss in both directions. + +- Initial Request:** The NODE sends a **CON\_REQ\_S** message to the SWITCH. The message details are: + - HDR.DO=0 + - CON.N=0 + - CON.LCID=K + - CON.EUI48=SNA +- Loss and Retransmit (Node to Switch):** The SWITCH does not receive the message. The NODE retransmits the **CON\_REQ\_S** message. This second attempt is received by the SWITCH. +- Loss and Retransmit (Switch to Base):** The SWITCH attempts to forward the message to the BASE but loses it. The SWITCH retransmits the **CON\_REQ\_S** message to the BASE, which is received. +- Loss and Retransmit (Base to Node):** The BASE sends a response **CON\_REQ\_B** to the NODE. The message details are: + - HDR.DO=1 + - CON.N=0 + - CON.LCID=K + - CON.EUI48=SNA + The NODE does not receive this message. The BASE retransmits the **CON\_REQ\_B** message, which is received by the NODE. + +Sequence diagram for Figure 8-25 showing a transaction with packet loss and retransmits between a Base, Switch, and Node. + +Figure 8-25 – Transaction with packet loss requiring retransmits + +Figure 8-26 shows the case of a delayed response causing duplication at the initiator of the control transaction. + +![Sequence diagram for Figure 8-26 showing duplicate packet detection and elimination between a Base, Switch, and Node.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +This sequence diagram illustrates a transaction between a BASE, a SWITCH, and a NODE, showing duplicate packet detection and elimination due to a delayed response. + +- Initial Request:** The NODE sends a **CON\_REQ\_S** message to the SWITCH. +- Forwarding:** The SWITCH receives the message and forwards it to the BASE as **CON\_REQ\_S**. +- Response:** The BASE sends a response **CON\_REQ\_B** to the SWITCH. +- Delay:** The SWITCH receives the response but delays forwarding it to the NODE. +- Retransmit:** Due to the delay, the BASE retransmits the **CON\_REQ\_S** message to the SWITCH. +- Duplicate Detection:** The SWITCH receives the retransmitted **CON\_REQ\_S** message. It recognizes this as a duplicate of the previously forwarded request and eliminates it, preventing duplication at the initiator (BASE). +- Final Response:** The SWITCH then forwards the original **CON\_REQ\_B** response to the NODE. + +Sequence diagram for Figure 8-26 showing duplicate packet detection and elimination between a Base, Switch, and Node. + +Figure 8-26 – Duplicate packet detection and elimination + +#### 8.4.5.3 REG control packet (PKT.CTYPE=1) + +This control packet is used to negotiate the registration process. The description of data fields of this control packet is described in Table 8-8 and Figure 8-27. The meaning of the packets differs depending on the direction of the packet. This packet interpretation is explained in Table 8-9. These packets are used during the registration and unregistration processes, as explained in clauses 8.6.1 and 8.6.2. + +The PKT.SID field is used in this control packet as the switch where the service node is registering. The PKT.LNID field is used in this control packet as the local node identifier being assigned to the service node during the registration process negotiation. + +The REG.CAP\_PA field is used to indicate the packet aggregation capability as discussed in clause 8.3.7. In the uplink direction, this field is an indication from the registering terminal node about its own capabilities. For the downlink response, the base node evaluates whether or not all the devices in the cascaded chain from itself to this terminal node have the packet-aggregation capability. If they do, the base node shall set REG.CAP\_PA=1; otherwise REG.CAP\_PA=0. + +MSB + +| REG.N | REG.R | REG.SPC | Reserved | REG.CAP_SW | REG.CAP_PA | REG.CAP_CFP | REG.CAP_DC | REG.CAP_MC | REG.CAP_PRM | REG.CAP_ARQ | REG.TIME | | | | | | | +|-------------------|-------|---------|----------|------------|------------|-------------------|------------|------------|-------------|-------------|----------|--|--|--|--|--|--| +| REG.EUI48[47..40] | | | | | | REG.EUI48[39..32] | | | | | | | | | | | | +| REG.EUI48[31..24] | | | | | | REG.EUI48[23..16] | | | | | | | | | | | | +| REG.EUI48[15..8] | | | | | | REG.EUI48[7..0] | | | | | | | | | | | | +| REG.SNK[127..112] | | | | | | | | | | | | | | | | | | +| REG.SNK[111..96] | | | | | | | | | | | | | | | | | | +| REG.SNK[95..80] | | | | | | | | | | | | | | | | | | +| REG.SNK[79..64] | | | | | | | | | | | | | | | | | | +| REG.SNK[63..48] | | | | | | | | | | | | | | | | | | +| REG.SNK[47..32] | | | | | | | | | | | | | | | | | | +| REG.SNK[31..16] | | | | | | | | | | | | | | | | | | +| REG.SNK[15..0] | | | | | | | | | | | | | | | | | | +| REG.AUK[127..112] | | | | | | | | | | | | | | | | | | +| REG.AUK[111..96] | | | | | | | | | | | | | | | | | | +| REG.AUK[95..80] | | | | | | | | | | | | | | | | | | +| REG.AUK[79..64] | | | | | | | | | | | | | | | | | | +| REG.AUK[63..48] | | | | | | | | | | | | | | | | | | +| REG.AUK[47..32] | | | | | | | | | | | | | | | | | | +| REG.AUK[31..16] | | | | | | | | | | | | | | | | | | +| REG.AUK[15..0] | | | | | | | | | | | | | | | | | | + +G.9904(12)\_F8-27 + +Figure 8-27 – REG control packet structure + +**Table 8-8 – REG control packet fields** + +| Name | Length | Description | +|-----------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REG.N | 1 bit | Negative
  • REG.N=1 for the negative register
  • REG.N=0 for the positive register
(see Table 8-9) | +| REG.R | 1 bit | Roaming
  • REG.R=1 if node already registered and wants to perform roaming to another switch.
  • REG.R=0 if node not yet registered and wants to perform a clear registration process.
| +| REG.SPC | 2 bits | Security profile capability for data PDUs:
  • REG.SPC=0 No encryption capability
  • REG.SPC=1 Security profile 1 capable device
  • REG.SPC=2 Security profile 2 capable device (not yet specified)
  • REG.SPC=3 Security profile 3 capable device (not yet specified).
| +| Reserved | 2 bits | Reserved by ITU-T. Should be set to 0 for this version of the protocol. | +| REG.CAP_SW | 1 bit | Switch capable
1 if the device is able to behave as a switch node
0 if the device is not | +| REG.CAP_PA | 1 bit | Packet aggregation capability
1 if the device has packet aggregation capability (uplink)
if the data transit path to the device has packet aggregation capability (downlink);
0 otherwise. | +| REG.CAP_CFP | 1 bit | Contention-free period capability
1 if the device is able to perform the negotiation of the CFP;
0 if the device cannot use the contention-free period in a negotiated way. | +| REG.CAP_DC | 1 bit | Direct connection capability
1 if the device is able to perform direct connections
0 if the device is not able to perform direct connections | +| REG.CAP_MC | 1 bit | Multicast capability
1 if the device is able to use multicast for its own communications
0 if the device is not able to use multicast for its own communications | +| REG.CAP_PRM | 1 bit | PHY robustness management capable
1 if the device is able to perform PHY robustness management
0 if the device is not able to perform PHY robustness management | +| REG.CAP_ARQ | 1 bit | ARQ capable
1 if the device is able to establish ARQ connections
0 if the device is not able to establish ARQ connections | + +**Table 8-8 – REG control packet fields** + +| Name | Length | Description | +|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REG.TIME | 3 bits | Time to wait for an ALV_B messages before assuming the service node has been unregistered by the base node. For all messages except REG_RSP this field should be set to 0. For REG_RSP its value means:
ALV.TIME = 0 => 32 seconds
ALV.TIME = 1 => 64 seconds
ALV.TIME = 2 => 128 seconds ~ 2.1 minutes
ALV.TIME = 3 => 256 seconds ~ 4.2 minutes
ALV.TIME = 4 => 512 seconds ~ 8.5 minutes
ALV.TIME = 5 => 1024 seconds ~ 17.1 minutes
ALV.TIME = 6 => 2048 seconds ~ 34.1 minutes
ALV.TIME = 7 => 4096 seconds ~ 68.3 minutes. | +| REG.EUI-48 | 48 bit | EUI-48 of the node
EUI-48 of the node requesting the registration | +| REG.SNK | 128 bits | Encrypted subnetwork key that shall be used to derive the subnetwork working key | +| REG.AUK | 128 bits | Encrypted authentication key. This is a random sequence meant to act as an authentication mechanism. | + +**Table 8-9 – REG control packet types** + +| Name | HDR.DO | PKT.LNID | REG.N | REG.R | Description | +|-----------|--------|----------|-------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| REG_REQ | 0 | 0x3FFF | 0 | R | Registration request
  • If R=0 any previous connection from this node should be lost;
  • If R=1 any previous connection from this node should be maintained.
| +| REG_RSP | 1 | < 0x3FFF | 0 | R | Registration response. This packet assigns the PCK.LNID to the service node. | +| REG_ACK | 0 | < 0x3FFF | 0 | R | Registration acknowledged by the service node. | +| REG_REJ | 1 | 0x3FFF | 1 | 0 | Registration rejected by the base node. | +| REG_UNR_S | 0 | < 0x3FFF | 1 | 0 |
  • After a REG_UNR_B: unregistration acknowledge
  • Alone: unregistration request initiated by the node
| +| REG_UNR_B | 1 | < 0x3FFF | 1 | 0 |
  • After a REG_UNR_S: unregistration acknowledge
  • Alone: unregistration request initiated by the base node
| + +Fields REG.SNK and REG.AUK are of significance only for REG\_RSP and REG\_ACK messages with security profile 1 (REG.SCP=1). For all other message-exchange variants using the REG control packet, these fields shall not be present reducing the length of payload. + +In REG\_RSP message, the REG.SNK and REG.AUK shall always be inserted encrypted with WK0. + +In the REG\_ACK message, the REG.SNK field shall be set to zero. The contents of the REG.AUK field shall be derived by decrypting the received REG\_RSP message with WK0 and re-encrypting the decrypted REG.AUK field with SWK derived from the decrypted REG.SNK and random sequence previously received in SEC control packets. + +#### 8.4.5.4 CON control packet (PKT.CTYPE = 2) + +This control packet is used for negotiating the connections. The description of the fields of this packet is given in Table 8-10 and Figure 8-28. The meaning of the packet differs depending on the direction of the packet and on the values of the different types. Table 8-11 shows the different interpretation of the packets. The packets are used during the connection establishment and closing. These processes are explained in more detail in clause 8.6.6. + +![Figure 8-28 – CON control packet structure. This diagram shows the layout of a CON control packet. It starts with a header containing four 1-bit flags: CON.N, CON.D, CON.ARQ, and CON.E. This is followed by a 'Reserved' field. The main part of the packet contains several fields: CON.LCID, six octets of CON.EUI48 (labeled [0] through [5]), CON.DCLCID, CON.DCLNID, CON.DSSID, CON.DCSID, CON.TYPE, and CON.DLEN. There are also 'Reserved' fields. Brackets on the right indicate that the CON.EUI48 and CON.DCLCID fields are present if CON.E=1, and the CON.DCNAD, CON.DSSID, CON.DCLNID, CON.DCLID, CON.DCSID, and the reserved field between CON.DCNAD and CON.DSSID are present if CON.D=1. The diagram is labeled MSB at the top left and LSB at the bottom right.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Figure 8-28 – CON control packet structure. This diagram shows the layout of a CON control packet. It starts with a header containing four 1-bit flags: CON.N, CON.D, CON.ARQ, and CON.E. This is followed by a 'Reserved' field. The main part of the packet contains several fields: CON.LCID, six octets of CON.EUI48 (labeled [0] through [5]), CON.DCLCID, CON.DCLNID, CON.DSSID, CON.DCSID, CON.TYPE, and CON.DLEN. There are also 'Reserved' fields. Brackets on the right indicate that the CON.EUI48 and CON.DCLCID fields are present if CON.E=1, and the CON.DCNAD, CON.DSSID, CON.DCLNID, CON.DCLID, CON.DCSID, and the reserved field between CON.DCNAD and CON.DSSID are present if CON.D=1. The diagram is labeled MSB at the top left and LSB at the bottom right. + +Figure 8-28 – CON control packet structure + +Note that Figure 8-28 shows the complete message with all optional parts. When CON.D is 0, CON.DCNAD, CON.DSSID, CON.DCLNID, CON.DCLID, CON.DCSID and the reserved field between CON.DCNAD and CON.DSSID will not be present in the message. Thus, the message will be 6 octets smaller. Similarly, when CON.E is zero, the field CON.EUI-48 will not be present, making the message 6 octets smaller. + +Table 8-10 – CON control packet fields + +| Name | Length | Description | +|---------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CON.N | 1 bit | Negative
  • • CON.N=1 for the negative connection
  • • CON.N=0 for the positive connection
| +| CON.D | 1 bit | Direct connection
  • • CON.D=1 if information about direct connection is carried by this packet
  • • CON.D=0 if information about direct connection is not carried by this packet
| +| CON.ARQ | 1 bit | ARQ mechanism enable
  • • CON.ARQ=1 if ARQ mechanism is enabled for this connection
  • • CON.ARQ=0 if ARQ mechanism is not enabled for this connection
| + +**Table 8-10 – CON control packet fields** + +| Name | Length | Description | +|------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CON.E | 1 bit | EUI-48 presence
  • • CON.E = 1 to have a CON.EUI-48
  • • CON.E = 0 to not have a CON.EUI-48 so that this connection establishment is for reaching the base node CL.
| +| Reserved | 3 bits | Reserved by ITU-T.
This shall be 0 for this version of the protocol. | +| CON.LCID | 9 bits | Local connection identifier
The LCID is reserved in the connection request. LCIDs from 0 to 255 are assigned by the connection requests initiated by the base node. LCIDs from 256 to 511 are assigned by the connection requests initiated by the local node.
This is the identifier of the connection being managed with this packet. This is not the same as the PKT.LCID of the generic header, which does not exist for control packets. | +| CON.EUI-48 | 48 bits
(Present if CON.E=1) | EUI-48 of destination/source service node/base node for connection request
When not performing a directed connection, this field should not be included. When performing a directed connection, it may contain the SNA, indicating that the base node convergence layer should determine the EUI-48.
  • • CON.D = 0, Destination EUI-48
  • • CON.D = 1, Source EUI-48
| +| Reserved | 7 bits
(Present if CON.D=1) | Reserved by ITU-T.
This shall be 0 for this version of the protocol. | +| CON.DCLCID | 9 bits
(Present if CON.D=1) | Direct connection LCID
This field represents the LCID of the connection identifier to which the one being established shall be directly switched. | +| CON.DCNA | 1 bit
(Present if CON.D=1) | Reserved by ITU-T. Direct connection not aggregated at destination.
This field represents the content of the PKT.NAD field after a direct connection switch operation. | +| Reserved | 1 bits
(Present if CON.D=1) | Reserved by ITU-T.
This shall be 0 for this version of the protocol. | +| CON.DCLNID | 14 bits
(Present if CON.D=1) | Direct connection LNID
This field represents the LNID part of the connection identifier to which the one being established shall be directly switched. | +| CON.DSSID | 8 bits
(Present if CON.D=1) | Direct switch SID
This field represents the SID of the switch that should learn this direct connection and perform direct switching. | +| CON.DCSID | 8 bits
(Present if CON.D=1) | Direct connection SID
This field represents the SID part of the connection identifier to which the one being established shall be directly switched. | + +**Table 8-10 – CON control packet fields** + +| Name | Length | Description | +|----------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CON.TYPE | 8 bits | Connection type
The connection type (see Annex C) specifies the convergence layer to be used for this connection. They are treated transparently through the MAC common part sublayer and are used only to identify which convergence layer may be used. | +| CON.DLEN | 8 bits | Length of CON.DATA field in bytes | +| CON.DATA | (variable) | Connection specific parameters
These connection specific parameters are convergence layer specific. They should be defined in each convergence layer to define the parameters that are specific to the connection. These parameters are handled in a transparent way by the common part sublayer. | + +**Table 8-11 – CON control packet types** + +| Name | HDR.DO | CON.N | Description | +|-----------|--------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CON_REQ_S | 0 | 0 | Connection establishment request initiated by the service node. | +| CON_REQ_B | 1 | 0 | The base node will consider that the connection is established with the identifier CON.LCID.
  • After a CON_REQ_S: connection accepted
  • Alone: Connection establishment request
| +| CON_CLS_S | 0 | 1 | The service node considers this connection closed:
  • After a CON_REQ_B: connection rejected by the node
  • After a CON_CLS_B: connection closing acknowledge
  • Alone: connection closing request
| +| CON_CLS_B | 1 | 1 | The base node will consider that the connection is no longer established.
  • After a CON_REQ_S: connection establishment rejected by the base node
  • After a CON_CLS_S: connection closing acknowledge
  • Alone: connection closing request
| + +#### 8.4.5.5 PRO control packet (PKT.CTYPE = 3) + +This control packet is used to promote a service node from the terminal function to switch function. The description of the fields of this packet is given in Table 8-12, Figures 8-29 and 8-30. The meaning of the packet differs depending on the direction of the packet and on the values of the different types. Table 8-13 shows the different interpretation of the packets. The promotion process is explained in more detail in 8.6.3. + +![](8c3eb53c927f55acd19723cfcd0c43b6_img.jpg) + +MSB + +| | | | | | | | | +|-----------------|-----|--------|----------|-----------------|------------|------------|-------------| +| PRO.N | Res | PRO.RQ | PRO.TIME | PRO.NSID | | | | +| PRO.PNA[47..40] | | | | PRO.PNA[39..32] | | | | +| PRO.PNA[31..24] | | | | PRO.PNA[23..16] | | | | +| PRO.PNA[15..8] | | | | PRO.PNA[7..0] | | | | +| PRO.UPCOST | | | | PRO.DNCOST | | | | +| | | | | Reserved | PRO.SWC_DC | PRO.SWC_MC | PRO.SWC_PRM | +| | | | | LSB | | | | + +Figure 8-29 – PRO\_REQ\_S control packet structure + +![](d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg) + +MSB + +| | | | | | | | | +|-------|-----|--------|----------|----------|--|--|--| +| PRO.N | Res | PRO.RQ | PRO.TIME | PRO.NSID | | | | +| | | | | LSB | | | | + +Figure 8-30 – PRO control packet structure + +Note that Figure 8-29 includes all fields as used by a PRO\_REQ\_S message. All other messages are much smaller, containing only PRO.N, PRO.RQ, PRO.TIME and PRO.NSID as shown in Figure 8-30. + +Table 8-12 – PRO control packet fields + +| Name | Length | Description | +|------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRO.N | 1 bit | Negative
PRO.N=1 for the negative promotion
PRO.N=0 for the positive promotion | +| Reserved | 1 bit | Reserved by ITU-T.
This shall be 0 for this version of the protocol. | +| PRO.RQ | 3 bits | Receive quality of the PNPDU message received from the service node requesting the terminal to promote. | +| PRO.TIME | 3 bits | The ALV.TIME which is being used by the terminal which will become a switch. Upon receipt of this time in a PRO_REQ_B the service node should reset the keep-alive timer in the same way as receiving an ALV_B. | +| PRO.NSID | 8 bits | New switch identifier.
This is the assigned switch identifier of the node whose promotion is being managed with this packet. This is not the same as the PKT.SID of the packet header, which must be the SID of the switch this node is connected to, as a terminal node. | +| PRO.PNA | 0 or 48 bits | Promotion need address, contains the EUI-48 of the terminal requesting the service node promotes to become a switch.
This field is only included in the PRO_REQ_S message. | +| PRO.UPCOST | 0 or 8 bits | Total uplink cost from the terminal node to the base node. This value is calculated in the same way a switch node calculates the value it places into its own beacon PDU.
This field is only included in the PRO_REQ_S message. | + +**Table 8-12 – PRO control packet fields** + +| Name | Length | Description | +|-------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRO.DNCOST | 0 or 8 bits | Total downlink cost from the base node to the terminal node. This value is calculated in the same way a switch node calculates the value it places into its own beacon PDU.
This field is only included in the PRO_REQ_S message. | +| Reserved | 4 bits | Reserved by ITU-T. Should be set to 0 for this version of the protocol. | +| PRO.SWC_DC | 1 bit | Direct connection switching capability
1 if the device is able to behave as a direct switch in direct connections
0 otherwise | +| PRO.SWC_MC | 1 bit | Multicast switching capability
1 if the device is able to manage the multicast traffic when behaving as a switch
0 otherwise | +| PRO.SWC_PRM | 1 bit | PHY robustness management switching capability
1 if the device is able to perform PRM for the terminal nodes when behaving as a switch.
0 if the device is not able to perform PRM when behaving as a switch. | +| PRO.SWC_ARQ | 1 bit | ARQ buffering switching capability
1 if the device is able to perform buffering for ARQ connections while switching.
0 if the device is not able to perform buffering for ARQ connections while switching. | + +**Table 8-13 – PRO control packet types** + +| Name | HDR.DO | PRO.N | PRO.NSID | Description | +|-----------|--------|-------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRO_REQ_S | 0 | 0 | 0xFF | Promotion request initiated by the service node. | +| PRO_REQ_B | 1 | 0 | < 0xFF | The base node will consider that the service node has promoted with the identifier PRO.NSID.
  • After a PRO_REQ: promotion accepted
  • Alone: promotion request initiated by the base node
| +| PRO_ACK | 0 | 0 | < 0xFF | Promotion acknowledge | +| PRO_REJ | 1 | 1 | 0xFF | The base node will consider that the service node is demoted. It is sent after a PRO_REQ to reject it. | +| PRO_DEM_S | 0 | 1 | < 0xFF | The service node considers that it is demoted:
  • After a PRO_DEM_B: demotion accepted
  • After a PRO_REQ_B: promotion rejected
  • Alone: demotion request.
| +| PRO_DEM_B | 1 | 1 | < 0xFF | The base node considers that the service node is demoted.
  • After a PRO_DEM_S: demotion accepted
  • Alone: demotion request
| + +##### BSI control packet (PKT.CTYPE = 4) + +The beacon slot information (BSI) control packet is only used by the base node and switch nodes. It is used to exchange information that is further used by a switch node to transmit its beacon. The description of the fields of this packet is given in Table 8-14 and Figure 8-31. The meaning of the packet differs depending on the direction of the packet and on the values of the different types. Table 8-15 represents the different interpretation of the packets. The promotion process is explained in more detail in clause 8.6.3. + +![Figure 8-31 – BSI control packet structure diagram showing fields: Reserved (5 bits), BSI.FRQ (3 bits), BSI.SLT (3 bits), and BSI.SEQ (5 bits). MSB is at the start and LSB is at the end.](3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg) + +| | | | | | +|-----------------|--|--|---------|---------| +| MSB | | | | | +| Reserved | | | BSI.FRQ | BSI.SLT | +| BSI.SEQ | | | | | +| LSB | | | | | + +Figure 8-31 – BSI control packet structure diagram showing fields: Reserved (5 bits), BSI.FRQ (3 bits), BSI.SLT (3 bits), and BSI.SEQ (5 bits). MSB is at the start and LSB is at the end. + +Figure 8-31 – BSI control packet structure + +Table 8-14 – BSI control packet fields + +| Name | Length | Description | +|----------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 5 bits | Reserved by ITU-T. In this version, this field should be initialized to 0. | +| BSI.FRQ | 3 bits | Transmission frequency of Beacon slot, encoded as:
FRQ = 0 => 1 beacon every frame
FRQ = 1 => 1 beacon every 2 frames
FRQ = 2 => 1 beacon every 4 frames
FRQ = 3 => 1 beacon every 8 frames
FRQ = 4 => 1 beacon every 16 frames
FRQ = 5 => 1 beacon every 32 frames
FRQ = 6 => Reserved by ITU-T
FRQ = 7 => Reserved by ITU-T. | +| BSI.SLT | 3 bits | Beacon slot to be used by target switch | +| BSI.SEQ | 5 bits | The Beacon sequence number when the specified change takes effect. | + +Table 8-15 – BSI control message types + +| Name | HDR.DO | Description | +|---------|--------|---------------------------------------------------| +| BSI_ACK | 0 | Acknowledgement of receipt of BSI control message | +| BSI_IND | 1 | Beacon-slot change command | + +#### 8.4.5.6 FRA control packet (PKT.CTYPE = 5) + +This control packet is broadcast from the base node and relayed by all switch nodes to the entire subnetwork. It is used to circulate information on the change of frame structure at a specific time in future. The description of fields of this packet is given in Table 8-16 and Figure 8-32. Table 8-17 shows the different interpretation of the packets. + +![Figure 8-32 – FRA control packet structure diagram showing fields: FRA.TYP (1 bit), Reserved (7 bits), FRA.CFP (8 bits), FRA.SEQ (8 bits), and FRA.BCN (8 bits). MSB is at the start and LSB is at the end.](b82b870697ef3993804c839b298c0f4f_img.jpg) + +| | | | | | | | | | | | | | | | | +|---------|-----------------|--|--|--|--|--|--|---------|--|--|--|---------|--|--|--| +| MSB | | | | | | | | | | | | | | | | +| FRA.TYP | Reserved | | | | | | | FRA.CFP | | | | | | | | +| | | | | | | | | FRA.SEQ | | | | FRA.BCN | | | | +| LSB | | | | | | | | | | | | | | | | + +Figure 8-32 – FRA control packet structure diagram showing fields: FRA.TYP (1 bit), Reserved (7 bits), FRA.CFP (8 bits), FRA.SEQ (8 bits), and FRA.BCN (8 bits). MSB is at the start and LSB is at the end. + +Figure 8-32 – FRA control packet structure + +**Table 8-16 – FRA control packet fields** + +| Name | Length | Description | +|----------|---------|----------------------------------------------------------------------------| +| FRA.TYP | 2 bits | 0: Beacon count change
1: CFP duration change | +| Reserved | 4 bits | Reserved by ITU-T. In this version, this field should be initialized to 0. | +| FRA.CFP | 10 bits | Offset of CFP from the start of frame | +| FRA.SEQ | 5 bits | The beacon sequence number when the specified change takes effect. | +| FRA.BCN | 3 bits | Number of beacons in a frame | + +**Table 8-17 – FRA control packet types** + +| Name | FRA.TYP | Description | +|-------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| FRA_BCN_IND | 0 | Indicates changes to frame structure due to change in the beacon-slot count | +| FRA_CFP_IND | 1 | Indicates changes to frame structure due to change in CFP duration as a result of grant of CFP or end of CFP period for any requesting service node in the subnetwork. | + +#### 8.4.5.7 CFP control packet (PKT.CTYPE = 6) + +This control packet is used for dedicated contention-free channel access time allocation to individual terminal or switch nodes. The description of the fields of this packet is given in Table 8-18 and Figure 8-33. The meaning of the packet differs depending on the direction of the packet and on the values of the different types. Table 8-19 represents the different interpretation of the packets. + +![Figure 8-33 – CFP control packet structure diagram showing a 16-bit packet layout with fields CFP.N, CFP.DIR, CFP.SEQ, PKT.LCID, CFP.LEN, CFP.POS, CFP.TYPE, and CFP.LNID. MSB is at the top-left and LSB is at the bottom-right.](bc6f20871b4f01c61470306c304fc9fe_img.jpg) + +| | | | | | | | | | | | | | | | | +|----------|----------|---------|--|--|--|--|----------|--|--|--|--|--|--|--|--| +| MSB | | | | | | | | | | | | | | | | +| CFP.N | CFP.DIR | CFP.SEQ | | | | | PKT.LCID | | | | | | | | | +| CFP.LEN | | | | | | | CFP.POS | | | | | | | | | +| CFP.TYPE | CFP.LNID | | | | | | | | | | | | | | | +| LSB | | | | | | | | | | | | | | | | + +Figure 8-33 – CFP control packet structure diagram showing a 16-bit packet layout with fields CFP.N, CFP.DIR, CFP.SEQ, PKT.LCID, CFP.LEN, CFP.POS, CFP.TYPE, and CFP.LNID. MSB is at the top-left and LSB is at the bottom-right. + +**Figure 8-33 – CFP control packet structure** + +**Table 8-18 – CFP control message fields** + +| Name | Length | Description | +|----------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CFP.N | 1 bit | 0: denial of allocation/de-allocation request
1: acceptance of allocation/de-allocation request | +| CFP.DIR | 1 bit | Indicate direction of allocation.
0: allocation is applicable to uplink (towards base node) direction
1: allocation is applicable to downlink (towards service node) direction | +| CFP.SEQ | 5 bits | The beacon sequence number when the specified change takes effect. | +| CFP.LCID | 9 bits | LCID of requesting connection | +| CFP.LEN | 7 bits | Length (in symbols) of requested/allocated channel time per frame. | +| CFP.POS | 9 bits | Offset (in symbols) of allocated time from beginning of frame. | + +**Table 8-18 – CFP control message fields** + +| Name | Length | Description | +|----------|---------|---------------------------------------------------------------------------------------------| +| CFP.TYPE | 2 bits | 0: channel allocation packet
1: channel de-allocation packet
2: channel change packet | +| CFP.LNID | 14 bits | LNID of service node that is the intended user of the allocation. | + +**Table 8-19 – CFP control packet types** + +| Name | CFP.TYP | HDR.DO | Description | +|---------------|---------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CFP_ALC_REQ_S | 0 | 0 | Service node makes channel allocation request | +| CFP_ALC_IND | 0 | 1 |
  • After a CFP_ALC_REQ_S: requested channel is allocated
  • Alone: unsolicited channel allocation by base node
| +| CFP_ALC_REJ | 0 | 1 | Requested channel allocation is denied | +| CFP_DALC_REQ | 1 | 0 | Service node makes channel de-allocation request | +| CFP_DALC_RSP | 1 | 1 | Base node confirms de-allocation | +| CFP_CHG_IND | 2 | 1 | Change of location of allocated channel within the CFP | + +#### 8.4.5.8 ALV control packet (PKT.CTYPE = 7) + +The ALV control message is used for keep-alive signalling between a service node, the service nodes above it and the base node. The message exchange is bidirectional, that is, a message is periodically exchanged in each direction. The structure of these messages are shown in Figure 8-34 and Table 8-20. The different keep-alive message types are shown in Table 8-21. These messages are sent periodically, as described in clause 8.6.5. + +![Diagram of ALV control packet structure showing fields ALV.RX CNT, ALV.TX CNT, Reserved, ALV.TIME, and ALV.SSID with MSB and LSB markers.](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +The diagram illustrates the structure of an ALV control packet. It is a 16-bit word. The first byte contains ALV.RX CNT, the second byte contains ALV.TX CNT. The next two bytes are Reserved. The fifth byte contains ALV.TIME. The final six bits are ALV.SSID. The Most Significant Bit (MSB) is at the top left, and the Least Significant Bit (LSB) is at the bottom right. + +| | | | | | | | | | | | | | | | | +|------------|------------|-----------------|--|--|--|--|--|----------|--|----------|--|--|--|--|--| +| MSB | | | | | | | | | | | | | | | | +| ALV.RX CNT | ALV.TX CNT | Reserved | | | | | | | | ALV.TIME | | | | | | +| | | | | | | | | ALV.SSID | | | | | | | | +| | | LSB | | | | | | | | | | | | | | + +Diagram of ALV control packet structure showing fields ALV.RX CNT, ALV.TX CNT, Reserved, ALV.TIME, and ALV.SSID with MSB and LSB markers. + +**Figure 8-34 – ALV control packet structure** + +**Table 8-20 – ALV control message fields** + +| Name | Length | Description | +|------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ALV.RX CNT | 3 bits | Modulo 8 counter to indicate the number of received ALV messages. | +| ALV.TX CNT | 3 bits | Modulo 8 counter to indicate the number of transmitted ALV messages. | +| Reserved | 7 bits | Reserved by ITU-T. Should always be encoded as 0 in this version of the Recommendation. | +| ALV.TIME | 3 bits | Time to wait for ALV_B messages before assuming the service node has been unregistered by the base node.
ALV.TIME = 0 => 32 seconds
ALV.TIME = 1 => 64 seconds
ALV.TIME = 2 => 128 seconds ~ 2.1 minutes
ALV.TIME = 3 => 256 seconds ~ 4.2 minutes
ALV.TIME = 4 => 512 seconds ~ 8.5 minutes
ALV.TIME = 5 => 1024 seconds ~ 17.1 minutes
ALV.TIME = 6 => 2048 seconds ~ 34.1 minutes
ALV.TIME = 7 => 4096 seconds ~ 68.3 minutes | +| ALV.SSID | 8 bits | For a terminal, this should be 0xFF. For a switch, this is its switch identifier. | + +**Table 8-21 – Keep-alive control packet types** + +| Name | HDR.DO | Description | +|-------|--------|----------------------------------------| +| ALV_S | 0 | Keep-alive message from a service node | +| ALV_B | 1 | Keep-alive message from the base node | + +#### **8.4.5.9 MUL control packet (PKT.CTYPE = 8)** + +The MUL message is used to control multicast group membership. The structure of this message and the meanings of the fields are described in Table 8-22 and Figure 8-35. The message can be used in different ways as described in Table 8-23. + +![Diagram of MUL control packet structure showing fields MUL.N, Reserved, MUL.LCID, MUL.TYPE, and MUL.DLEN with MSB and LSB markers.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +The diagram illustrates the structure of a MUL control packet. It is a 16-bit word with the following fields: + + +- MUL.N**: 1 bit (MSB) +- Reserved**: 7 bits +- MUL.LCID**: 8 bits +- MUL.TYPE**: 8 bits +- MUL.DLEN**: 8 bits + + The packet is shown as a grid of 16 cells. The first cell contains 'MUL.N'. The next 7 cells are grouped under the label 'Reserved'. The next 8 cells are split into two groups of 4: 'MUL.LCID' and 'MUL.DLEN'. The 9th cell (first of the MUL.TYPE group) contains 'MUL.TYPE'. The 16th cell (last of the MUL.DLEN group) is labeled 'LSB'. + +Diagram of MUL control packet structure showing fields MUL.N, Reserved, MUL.LCID, MUL.TYPE, and MUL.DLEN with MSB and LSB markers. + +**Figure 8-35 – MUL control packet structure** + +**Table 8-22 – MUL control message fields** + +| Name | Length | Description | +|----------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MUL.N | 1 bit | Negative
  • • MUL.N = 1 for the negative multicast connection, i.e., multicast group leave.
  • • MUL.N = 0 for the positive multicast connection, i.e., multicast group join.
| +| Reserved | 6 bits | Reserved by ITU-T.
This shall be 0 for this version of the protocol. | +| MUL.LCID | 9 bits | Local connection identifier
The LCID indicates which multicast distribution group is being managed with this message. | +| MUL.TYPE | 8 bits | Connection type
The connection type specifies the convergence layer to be used for this connection. They are treated transparently through the MAC common part sublayer and are used only to identify which convergence layer may be used. See Annex C. | +| MUL.DLEN | 8 bits | Length of data in bytes in the MUL.DATA field | +| MUL.DATA | (variable) | Connection specific parameters
These connection specific parameters are convergence layer specific. They should be defined in each convergence layer to define the parameters that are specific to the connection. These parameters are handled in a transparent way by the common part sublayer. | + +**Table 8-23 – MUL control message types** + +| Name | HDR.DO | MUL.N | Description | +|-------------|--------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MUL_JOIN_S | 0 | 0 | Multicast group join request initiated by the service node, or an acknowledgement when sent in response to a MUL_JOIN_B. | +| MUL_JOIN_B | 1 | 0 | The base node will consider that the group has been joined with the identifier MUL.LCID.
  • • After a MUL_JOIN_S: join accepted
  • • Alone: group join request
| +| MUL_LEAVE_S | 0 | 1 | The service node leaves the multicast group:
  • • After a MUL_JOIN_B: join rejected by the node
  • • After a MUL_LEAVE_B: group leave acknowledge
  • • Alone: group leave request.
| +| MUL_LEAVE_B | 1 | 1 | The base node will consider that the service node is no longer a member of the multicast group.
  • • After a MUL_JOIN_S: group join rejected by the base node
  • • After a MUL_LEAVE_S: group leave acknowledge
  • • Alone: group leave request.
| + +#### 8.4.5.10 PRM control packet (PKT.CTYPE = 9) + +The PHY robustness management packets are used to control the parameters that affect the robustness and efficiency of the PHY. These packets are sent to notify to the peer of the need to improve robustness of the transmission, or to notify the peer that the reception quality is so good that a less robust and so more efficient modulation scheme can be transmitted. + +The fields of the PRM control packet are described in Table 8-24 and Figure 8-36 and the types of messages are described in Table 8-25. + +![Figure 8-36 – PHY control packet structure diagram showing a byte with 8 bits. The first bit is PRM.R (MSB), the second is PRM.N, the next three are Reserved, and the last three are PRM.SNR (LSB).](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +| | | | | | | | | +|-------|-------|-----------------|--|--|---------|--|--| +| MSB | | | | | | | | +| PRM.R | PRM.N | Reserved | | | PRM.SNR | | | +| LSB | | | | | | | | + +Figure 8-36 – PHY control packet structure diagram showing a byte with 8 bits. The first bit is PRM.R (MSB), the second is PRM.N, the next three are Reserved, and the last three are PRM.SNR (LSB). + +Figure 8-36 – PHY control packet structure + +Table 8-24 – PRM control message fields + +| Name | Length | Description | +|----------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PRM.R | 1 bit | Response
  • PRM.R=1 if this message is a response
  • PRM.R=0 if this message is a request
| +| PRM.N | 1 bit | Negative
  • PRM.N=1 if the operation could not be performed
  • PRM.N=0 if the operation was performed
| +| Reserved | 3 bits | Reserved by ITU-T. Should always be encoded as 0 in this version of the Recommendation. | +| PRM.SNR | 3 bits | Indicates the SNR at the end that initiates a change request, obtained using PHY_SNR primitive (see clause 7.10.3.10). | + +Table 8-25 – PRM control message types + +| Name | PRM.R | PRM.N | Description | +|---------|-------|-------|---------------------------------------| +| PRM_REQ | 0 | 0 | PHY modulation management request | +| PRM_ACK | 1 | 0 | PHY modulation management acknowledge | +| PRM_REJ | 1 | 1 | PHY modulation management rejected | + +#### 8.4.5.11 SEC control packet (PKT.CTYPE = 10) + +The SEC control message is broadcast unencrypted by the base node and all switch nodes to the rest of the subnetwork in order to circulate the random sequence used to generate working keys. The random sequence used by devices in a subnetwork is dynamic and changes from time to time to ensure a robust security framework. The structure of this message is shown in Table 8-26 and Figure 8-37. Further details of security mechanisms are given in clause 8.3.8. + +![Diagram of SEC control packet structure showing fields SEC.RAN[127...112] through SEC.RAN[15...0], SEC.SNK[127...112] through SEC.SNK[15...0], Reserved, SEC.USE, and SEC.SEQ. MSB is at the top left, LSB is at the bottom right.](0adfaa8c2562a9fe3a8a96165d7d59a3_img.jpg) + +The diagram illustrates the structure of a SEC control packet. It is a grid of fields. The top part consists of 16 rows of 128-bit sequences. The first 8 rows are SEC.RAN, with ranges [127...112], [111...96], [95...80], [79...64], [63...48], [47...32], [31...16], and [15...0] from top to bottom. The next 8 rows are SEC.SNK with the same ranges. Below these is a row containing 'Reserved' (2 bits), 'SEC.USE' (1 bit), and 'SEC.SEQ' (5 bits). The 'MSB' (Most Significant Bit) is indicated at the top left, and 'LSB' (Least Significant Bit) is at the bottom right. A reference code 'G.9904(12)\_F8-37' is at the bottom right. + +Diagram of SEC control packet structure showing fields SEC.RAN[127...112] through SEC.RAN[15...0], SEC.SNK[127...112] through SEC.SNK[15...0], Reserved, SEC.USE, and SEC.SEQ. MSB is at the top left, LSB is at the bottom right. + +**Figure 8-37 – SEC control packet structure** + +**Table 8-26 – SEC control message fields** + +| Name | Length | Description | +|----------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SEC.RAN | 128 bits | Random sequence to be used to derive WK. | +| SEC.SNK | 128 bits | Random sequence to be used to derive SWK. | +| Reserved | 2 bits | Reserved by ITU-T. Should always be encoded as 0 in this version of the Recommendation. | +| SEC.USE | 1 bits | When 1 indicates the random sequences are already in use.
When 0 indicates that SE.SEQ should be used to determine when to start using these random sequences. | +| SEC.SEQ | 5 bits | The beacon sequence number when the specified change takes effect. | + +## 8.5 MAC service access point + +### 8.5.1 General + +The MAC service access point provides several primitives to allow the convergence layer to interact with the MAC layer. This clause aims to explain how the MAC may be used. An implementation of the MAC may not use all the primitives listed here; it may use other primitives; or it may have a function-call based interface rather than message-passing, etc. These are all implementation issues which are beyond the scope of this Recommendation. + +The .request primitives are passed from the CL to the MAC to request the initiation of a service. The .indication and .confirm primitives are passed from the MAC to the CL to indicate an internal MAC event that is significant to the CL. This event may be logically related to a remote service request or may be caused by an event internal to the local MAC. The .response primitive is passed from the CL to the MAC to provide a response to a .indication primitive. Thus, the four primitives are used in pairs, the pair .request and .confirm and the pair .indication and .response. This is shown in Figures 8-38 to 8-41. + +![Sequence diagram for Figure 8-38: Establishment of a connection. It shows two CS (Customer Service) nodes interacting with their respective MAC (Media Access Control) nodes. The sequence starts with MAC_ESTABLISH.request from the first CS to its MAC. The MAC then sends MAC_ESTABLISH.indication to the second CS. The second CS responds with MAC_ESTABLISH.response to its MAC. Finally, the first MAC sends MAC_ESTABLISH.confirm to the first CS. Dashed lines connect the two MAC nodes.](e776395ba1d4a6d568f08b406d784abd_img.jpg) + +Sequence diagram for Figure 8-38: Establishment of a connection. It shows two CS (Customer Service) nodes interacting with their respective MAC (Media Access Control) nodes. The sequence starts with MAC\_ESTABLISH.request from the first CS to its MAC. The MAC then sends MAC\_ESTABLISH.indication to the second CS. The second CS responds with MAC\_ESTABLISH.response to its MAC. Finally, the first MAC sends MAC\_ESTABLISH.confirm to the first CS. Dashed lines connect the two MAC nodes. + +Figure 8-38 – Establishment of a connection + +![Sequence diagram for Figure 8-39: Failed establishment of a connection. It shows a CS node sending a MAC_ESTABLISH.request to its MAC node. The MAC node attempts to send a MAC_ESTABLISH.confirm back to the CS, but this message is shown as being lost or failed, indicated by a dashed line with an 'X' at the end.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +Sequence diagram for Figure 8-39: Failed establishment of a connection. It shows a CS node sending a MAC\_ESTABLISH.request to its MAC node. The MAC node attempts to send a MAC\_ESTABLISH.confirm back to the CS, but this message is shown as being lost or failed, indicated by a dashed line with an 'X' at the end. + +Figure 8-39 – Failed establishment of a connection + +![Sequence diagram for Figure 8-40: Release of a connection. It shows two CS nodes interacting with their respective MAC nodes. The sequence starts with MAC_RELEASE.request from the first CS to its MAC. The MAC then sends MAC_RELEASE.indication to the second CS. The second CS responds with MAC_RELEASE.response to its MAC. Finally, the first MAC sends MAC_RELEASE.confirm to the first CS. Dashed lines connect the two MAC nodes.](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +Sequence diagram for Figure 8-40: Release of a connection. It shows two CS nodes interacting with their respective MAC nodes. The sequence starts with MAC\_RELEASE.request from the first CS to its MAC. The MAC then sends MAC\_RELEASE.indication to the second CS. The second CS responds with MAC\_RELEASE.response to its MAC. Finally, the first MAC sends MAC\_RELEASE.confirm to the first CS. Dashed lines connect the two MAC nodes. + +Figure 8-40 – Release of a connection + +![Sequence diagram for Figure 8-41: Transfer of data. It shows a CS node sending a MAC_DATA.request to its MAC node. The MAC node then sends a MAC_DATA.indication to the second CS node. Dashed lines connect the two MAC nodes.](afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg) + +Sequence diagram for Figure 8-41: Transfer of data. It shows a CS node sending a MAC\_DATA.request to its MAC node. The MAC node then sends a MAC\_DATA.indication to the second CS node. Dashed lines connect the two MAC nodes. + +Figure 8-41 – Transfer of data + +Table 8-27 represents the list of available primitives in the MAC-SAP: + +Table 8-27 – List of MAC primitives + +| Service node primitives | Base node primitives | +|--------------------------|--------------------------| +| MAC_ESTABLISH.request | MAC_ESTABLISH.request | +| MAC_ESTABLISH.indication | MAC_ESTABLISH.indication | +| MAC_ESTABLISH.response | MAC_ESTABLISH.response | +| MAC_ESTABLISH.confirm | MAC_ESTABLISH.confirm | +| MAC_RELEASE.request | MAC_RELEASE.request | +| MAC_RELEASE.indication | MAC_RELEASE.indication | +| MAC_RELEASE.response | MAC_RELEASE.response | +| MAC_RELEASE.confirm | MAC_RELEASE.confirm | +| MAC_JOIN.request | MAC_JOIN.request | +| MAC_JOIN.Response | MAC_JOIN.response | +| MAC_JOIN.indication | MAC_JOIN.indication | +| MAC_JOIN.confirm | MAC_JOIN.confirm | +| MAC_LEAVE.request | MAC_LEAVE.request | + +**Table 8-27 – List of MAC primitives** + +| Service node primitives | Base node primitives | +|-------------------------|-----------------------| +| MAC_LEAVE.indication | MAC_LEAVE.indication | +| MAC_LEAVE.confirm | MAC_LEAVE.confirm | +| MAC_DATA.request | MAC_REDIRECT.response | +| MAC_DATA.confirm | MAC_DATA.request | +| MAC_DATA.indication | MAC_DATA.confirm | +| | MAC_DATA.indication | + +### 8.5.2 Service node and base node signalling primitives + +#### 8.5.2.1 General + +The following subclauses describe primitives which are available in both the service node and base node MAC-SAP. These are signalling primitives only and they are used for establishing and releasing MAC connections. + +#### 8.5.2.2 MAC\_ESTABLISH + +##### 8.5.2.2.1 General + +The MAC\_ESTABLISH primitives are used to manage a connection establishment. + +##### 8.5.2.2.2 MAC\_ESTABLISH.request + +The MAC\_ESTABLISH.request primitive is passed to the MAC layer entity to request the connection establishment. + +The semantics of this primitive are as follows: + +**MAC\_ESTABLISH.request{EUI-48, Type, Data, DataLength, ARQ, CfBytes}** + +The EUI-48 parameter of this primitive is used to specify the address of the node to which this connection will be addressed. The MAC will internally transfer this to an address used by the MAC layer. When the CL of a service node wishes to connect to the base node, it uses the EUI-48 00:00:00:00:00:00. However, when the CL of a service node wishes to connect to another service node on the subnetwork, it uses the EUI-48 of that service node. This will then trigger a direct connection establishment. However, whether a normal or a directed connection is established is transparent to the service node MAC SAP. As the EUI-48 of the base node is the SNA, the connection could also be requested from the base node using the SNA. + +The *Type* parameter is an identifier used to define the type of the convergence layer that should be used for this connection (see Annex C). This parameter is 1 byte long and will be transmitted in the CON.TYPE field of the connection request. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the local CL and the remote CL. This parameter will be transmitted in the CON.DATA field of the connection request. + +The *DataLength* parameter is the length of the *Data* parameter in bytes. + +The *ARQ* parameter indicates whether or not the ARQ mechanism should be used for this connection. It is a Boolean type with a value of true indicating that ARQ will be used. + +The *CfBytes* parameter is used to indicate whether or not the connection should use the contention or contention-free channel access scheme. When *CfBytes* is zero, contention-based access should be used. When *CfBytes* is not zero, it indicates how many bytes per frame should be allocated to the connection using CFP packets. + +##### 8.5.2.2.3 MAC\_ESTABLISH.indication + +The MAC\_ESTABLISH.indication is passed from the MAC layer to indicate that a connection establishment was initiated by a remote node. + +The semantics of this primitive are as follows: + +**MAC\_ESTABLISH.indication{ConHandle, EUI-48, Type, Data, DataLength, CfBytes}** + +The *ConHandle* is a unique identifier interchanged to uniquely identify the connection being indicated. It only has a valid meaning in the MAC SAP, and is used to have a reference to this connection between different primitives. + +The *EUI-48* parameter indicates which device on the subnetwork wishes to establish a connection. + +The *Type* parameter is an identifier used to define the type of the convergence layer that should be used for this connection. This parameter is 1 byte long and it is received in the CON.TYPE field of the connection request. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the local CL. This parameter is received in the CON.DATA field of the connection request. + +The *DataLength* parameter is the length of the data parameter in bytes. + +The *CfBytes* parameter is used to indicate if the connection should use the contention or contention-free channel access scheme. When *CfBytes* is zero, contention-based access will be used. When *CfBytes* is not zero, it indicates how many bytes per frame the connection would like to be allocated. + +##### 8.5.2.2.4 MAC\_ESTABLISH.response + +The MAC\_ESTABLISH.response is passed to the MAC layer to respond with a MAC\_ESTABLISH.indication. + +The semantics of this primitive are as follows: + +*MAC\_ESTABLISH.response{ConHandle, Answer, Data, DataLength}* + +The *ConHandle* parameter is the same as the one that was received in the MAC\_ESTABLISH.indication. + +The *Answer* parameter is used to notify the MAC of the action to be taken for this connection establishment. This parameter may have one of the values in Table 8-28. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the local CL. This parameter is received in the CON.DATA field of the connection response. + +The *DataLength* parameter is the length of the data parameter in bytes. + +Data may be passed to the caller even when the connection is rejected, i.e., answer has the value 1. The data may then optionally contain more information as to why the connection was rejected. + +**Table 8-28 – Values of the answer parameter in MAC\_ESTABLISH.response primitive** + +| Answer | Description | +|------------|-------------------------------------------| +| Accept = 0 | The connection establishment is accepted. | +| Reject = 1 | The connection establishment is rejected. | + +##### **8.5.2.2.5 MAC\_ESTABLISH.confirm** + +The MAC\_ESTABLISH.confirm is passed from the MAC layer as the remote answer to a MAC\_ESTABLISH.request. + +The semantics of this primitive are as follows: + +*MAC\_ESTABLISH.confirm{ConHandle, Result, EUI-48, Type, Data, DataLength}* + +The *ConHandle* is a unique identifier to uniquely identify the connection being indicated. It has a valid meaning only in the MAC SAP, used to have a reference to this connection between different primitives. The value is only valid if the *Result* parameter is 0. + +The *Result* parameter indicates the result of the connection establishment process. It may have one of the values in Table 8-29. + +The *EUI-48* parameter indicates which device on the subnetwork wishes to establish a connection. + +The *Type* parameter is an identifier used to define the type of the convergence layer that should be used for this connection. This parameter is 1 byte long and it is received in the CON.TYPE field of the connection request. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the local CL. This parameter is received in the CON.DATA field of the connection response. + +The *DataLength* parameter is the length of the data parameter in bytes. + +Data may be passed to the caller even when the connection is rejected, i.e., the result has the value 1. The data may then optionally contain more information as to why the connection was rejected. + +**Table 8-29 – Values of the result parameter in MAC\_ESTABLISH.confirm primitive** + +| Result | Description | +|---------------------|--------------------------------------------------------------------------------------| +| Success = 0 | The connection establishment was successful. | +| Reject = 1 | The connection establishment failed because it was rejected by the remote node. | +| Timeout = 2 | The connection establishment process timed out. | +| No bandwidth = 3 | There is insufficient available bandwidth to accept this contention-free connection. | +| No Such Device = 4 | A device with the destination address cannot be found. | +| Redirect failed = 5 | The base node attempted to perform a redirect which failed. | +| Not Registered = 6 | The service node is not registered. | +| No More LCIDs = 7 | All available LCIDs have been allocated. | + +#### 8.5.2.3 MAC\_RELEASE + +##### 8.5.2.3.1 General + +The MAC\_RELEASE primitives are used to release a connection. + +##### 8.5.2.3.2 MAC\_RELEASE.request + +The MAC\_RELEASE.request is a primitive used to initiate the release process of a connection. + +The semantics of this primitive are as follows: + +$$MAC\_RELEASE.request\{ConHandle\}$$ + +The *ConHandle* parameter specifies the connection to be released. This handle is the one that was obtained during the MAC\_ESTABLISH primitives. + +##### 8.5.2.3.3 MAC\_RELEASE.indication + +The MAC\_RELEASE.indication is a primitive used to indicate that a connection is being released. It may be released because of a remote operation or because of a connectivity problem. + +The semantics of this primitive are as follows: + +$$MAC\_RELEASE.indication\{ConHandle, Reason\}$$ + +The *ConHandle* parameter specifies the connection being released. This handle is the one that was obtained during the MAC\_ESTABLISH primitives. + +The *Reason* parameter may have one of the values given in Table 8-30. + +**Table 8-30 – Values of the reason parameter in MAC\_RELEASE.indication primitive** + +| Reason | Description | +|-------------|----------------------------------------------------------------| +| Success = 0 | The connection release was initiated by a remote service. | +| Error = 1 | The connection was released because of a connectivity problem. | + +##### 8.5.2.3.4 MAC\_RELEASE.response + +The MAC\_RELEASE.response is a primitive used to respond to a connection release process. + +The semantics of this primitive are as follows: + +$$MAC\_RELEASE.response\{ConHandle, Answer\}$$ + +The *ConHandle* parameter specifies the connection being released. This handle is the one that was obtained during the MAC\_ESTABLISH primitives. + +The *Answer* parameter may have one of the values given in Table 8-31. This parameter may not have the value "Reject = 1" because a connection release process cannot be rejected. + +**Table 8-31 – Values of the answer parameter in MAC\_RELEASE.response primitive** + +| Answer | Description | +|------------|-------------------------------------| +| Accept = 0 | The connection release is accepted. | + +After sending the MAC\_RELEASE.response the ConHandle is no longer valid and should not be used. + +##### 8.5.2.3.5 MAC\_RELEASE.confirm + +The MAC\_RELEASE.confirm primitive is used to confirm that the connection release process has finished. + +The semantics of this primitive are as follows: + +$$MAC\_RELEASE.confirm\{ConHandle, Result\}$$ + +The *ConHandle* parameter specifies the connection released. This handle is the one that was obtained during the MAC\_ESTABLISH primitives. + +The *Result* parameter may have one of the values given in Table 8-32. + +**Table 8-32 – Values of the result parameter in MAC\_RELEASE.confirm primitive** + +| Result | Description | +|--------------------|-------------------------------------------| +| Success = 0 | The connection release was successful. | +| Timeout = 2 | The connection release process timed out. | +| Not Registered = 6 | The service node is no longer registered. | + +After the reception of the MAC\_RELEASE.confirm the ConHandle is no longer valid and should not be used. + +#### 8.5.2.4 MAC\_JOIN + +##### 8.5.2.4.1 General + +The MAC\_JOIN primitives are used to join to a broadcast or multicast connection and allow the reception of such packets. + +##### 8.5.2.4.2 MAC\_JOIN.request + +The MAC\_JOIN.request primitive is used: + +- by all nodes to join broadcast traffic of a specific CL and start receiving these packets; +- by service nodes to join a particular multicast group; +- by the base node to invite a service node to join a particular multicast group. + +Depending on which device makes the join-request, this SAP can have two different variants. The first variant shall be used on base nodes and the second on service nodes. + +The semantics of this primitive are as follows: + +$$MAC\_JOIN.request\{Broadcast, ConHandle, EUI-48, Type, Data, DataLength\}$$ +$$MAC\_JOIN.request(Broadcast, Type, Data, Datalength)$$ + +The *Broadcast* parameter specifies whether the JOIN operation is being performed for a broadcast connection or for a multicast operation. It should be 1 for a broadcast operation and 0 for a multicast operation. In the case of broadcast operation, EUI-48, Data, DataLength are not used. + +ConHandle indicates the handle to be used with for this multicast join. In case of first join request for a new multicast group, ConHandle will be set to 0. For any subsequent EUI additions to an existing multicast group, ConHandle will serve as index to respective multicast group. + +The *EUI-48* parameter is used by the base node to specify the address of the node to which this join request will be addressed. The MAC will internally transfer this to an address used by the MAC layer. When the CL of a service node initiates the request, it uses the EUI-48 00:00:00:00:00:00. + +The *Type* parameter defines the type of the convergence layer that will send/receive the data packets. This parameter is 1 byte long and will be transmitted in the MUL.TYPE field of the join request. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the local CL. This parameter is received in the MUL.DATA field of the connection request. In case the CL supports several multicast groups, this Data parameter will be used to uniquely identify the group + +The *DataLength* parameter is the length of the Data parameter in bytes. + +If "Broadcast" is 1, the MAC will immediately issue a MAC\_JOIN.confirm primitive, as it does not need to perform any end-to-end operation. For a multicast operation the MAC\_JOIN.confirm is only sent once signalling with the uplink service node/base node is complete. + +##### 8.5.2.4.3 MAC\_JOIN.confirm + +The MAC\_JOIN.confirm primitive is received to confirm that the MAC\_JOIN.request operation has finished. + +The semantics of this primitive are as follows: + +*MAC\_JOIN.confirm{ConHandle, Result}* + +The *ConHandle* is a unique identifier to uniquely identify the connection being indicated. It has a valid meaning only in the MAC SAP, used to have a reference to this connection between different primitives. The value is only valid if the result parameter is 0. When the MAC receives packets on this connection, they will be passed upwards using the MAC\_DATA.indication primitive with this *ConHandle*. + +The *Result* parameter indicates the result of multicast group join process. It may have one of the values given in Table 8-33. + +**Table 8-33 – Values of the Result parameter in MAC\_JOIN.confirm primitive** + +| Result | Description | +|-------------|-----------------------------------------------------------------------------------------------------| +| Success = 0 | The connection establishment was successful. | +| Reject = 1 | The connection establishment failed because it was rejected by the upstream service node/base node. | +| Timeout = 2 | The connection establishment process timed out. | + +##### 8.5.2.4.4 MAC\_JOIN.indication + +On the base node, the MAC\_JOIN.indication is passed from the MAC layer to indicate that a multicast group join was initiated by a service node. On a service node, it is used to indicate that the base node is inviting to join a multicast group. + +Depending on the device type, this primitive shall have two variants. The first variant below shall be used in base nodes and the second variant is for service nodes: + +*MAC\_JOIN.indication{ConHandle, EUI-48, Type, Data, DataLength}* + +*MAC\_JOIN.indication(ConHandle, Type, Data, Datalen)* + +The *ConHandle* is a unique identifier interchanged to uniquely identify the multicast group being indicated. It has a valid meaning only in the MAC SAP, used to have a reference to this connection between different primitives. + +The *EUI-48* parameter indicates which device on the subnetwork wishes to establish a connection. + +The *Type* parameter is an identifier used to define the type of the convergence layer that should be used for this request. This parameter is 1 byte long and it is received in the MUL.TYPE field of the connection request. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the local CL. This parameter is received in the MUL.DATA field of the connection request. + +The *DataLength* parameter is the length of the Data parameter in bytes. + +##### 8.5.2.4.5 MAC\_JOIN.response + +The MAC\_JOIN.response is passed to the MAC layer to respond with a MAC\_JOIN.indication. Depending on the device type, this primitive could have either of the two forms given below. The first one shall be used in service node and the second on in base node implementations. + +The semantics of this primitive are as follows: + +$$MAC\_JOIN.response\{ConHandle, Answer\}$$ +$$MAC\_JOIN.response (ConHandle, EUI, Answer)$$ + +The *ConHandle* parameter is the same as the one that was received in the MAC\_JOIN.indication. + +*EUI* is the EUI-48 of the service node that requested the multicast group join. + +The *Answer* parameter is used to notify the MAC of the action to be taken for this join request. This parameter may have one of the values depicted below. + +**Table 8-34 – Values of the answer parameter in MAC\_ESTABLISH.response primitive** + +| Answer | Description | +|------------|---------------------------------------| +| Accept = 0 | The multicast group join is accepted. | +| Reject = 1 | The multicast group join is rejected. | + +#### 8.5.2.5 MAC\_LEAVE + +##### 8.5.2.5.1 General + +The MAC\_LEAVE primitives are used to leave a broadcast or multicast connection. + +##### 8.5.2.5.2 MAC\_LEAVE.request + +The MAC\_LEAVE.request primitive is used to leave multicast or broadcast traffic. Depending on the device type, this primitive could have either of the two forms given below. The first one shall be used in service node and the second on in base node implementations. + +The semantics of this primitive are as follows: + +$$MAC\_LEAVE.request\{ConHandle\}$$ +$$MAC\_LEAVE.request\{ConHandle, EUI\}$$ + +The *ConHandle* parameter specifies the connection to be left. This handle is the one that was obtained during the MAC\_JOIN primitives. + +*EUI* is the EUI-48 of the service node that has requested to be removed from the multicast group. + +##### 8.5.2.5.3 MAC\_LEAVE.confirm + +The MAC\_LEAVE.confirm primitive is received to confirm that the MAC\_LEAVE.request operation has finished. + +The semantics of this primitive are as follows: + +*MAC\_LEAVE.confirm{ConHandle, Result}* + +The *ConHandle* parameter specifies the connection released. This handle is the one that was obtained during the *MAC\_JOIN* primitives. + +The *Result* parameter may have one of the values in Table 8-35. + +**Table 8-35 – Values of the result parameter in *MAC\_LEAVE.confirm* primitive** + +| Result | Description | +|-------------|-----------------------------------------| +| Success = 0 | The connection leave was successful. | +| Timeout = 2 | The connection leave process timed out. | + +After the reception of the *MAC\_LEAVE.confirm*, the *ConHandle* is no longer valid and should not be used. + +##### 8.5.2.5.4 *MAC\_LEAVE.indication* + +The *MAC\_LEAVE.indication* primitive is used to leave multicast or broadcast traffic. Depending on the device type, this primitive could have either of the two forms given below. The first one shall be used in service node and the second one in base node implementations. + +The semantics of this primitive are as follows: + +*MAC\_LEAVE.indication{ConHandle}* + +*MAC\_LEAVE.indication{ConHandle, EUI}* + +The *ConHandle* parameter is the same as that received in *MAC\_JOIN.confirm* or *MAC\_JOIN.indication*. This handle is the one that was obtained during the *MAC\_JOIN* primitives. + +*EUI* is the EUI-48 of the service node that has requested to be removed from the multicast group. + +### 8.5.3 Base node signalling primitives + +#### 8.5.3.1 General + +This clause specifies *MAC-SAP* primitives that are only available in the base node. + +#### 8.5.3.2 *MAC\_REDIRECT.response* + +The *MAC\_REDIRECT.response* primitive is used to answer to a *MAC\_ESTABLISH.indication* and redirects the connection from the base node to another service node on the subnetwork. + +The semantics of this primitive are as follows: + +*MAC\_REDIRECT.response{ConHandle, EUI-48, Data, DataLength}* + +The *ConHandle* is the one passed in the *MAC\_ESTABLISH.indication* primitive to which it is replying. + +*EUI-48* indicates the service node to which this connection establishment should be forwarded. The base node should perform a direct connection set-up between the source of the connection establishment and the service node indicated by *EUI-48*. + +The *Data* parameter is a general purpose buffer to be interchanged for the negotiation between the remote CL and the base node CL. This parameter is received in the *CON.DATA* field of the connection request. + +The *DataLength* parameter is the length of the data parameter in bytes. + +Once this primitive has been used, the *ConHandle* is no longer valid. + +### 8.5.4 Service and base nodes data primitives + +#### 8.5.4.1 General + +The following subclauses describe how a service node or base node passes data between the convergence layer and the MAC layer. + +#### 8.5.4.2 MAC\_DATA.request + +The MAC\_DATA.request primitive is used to initiate the transmission process of data over a connection. + +The semantics of the primitive are as follows: + +*MAC\_DATA.request{ConHandle, Data, DataLength, Priority}* + +The *ConHandle* parameter specifies the connection to be used for the data transmission. This handle is the one that was obtained during the connection establishment primitives. + +The *Data* parameter is a buffer of octets that contains the CL data to be transmitted through this connection. + +The *DataLength* parameter is the length of the data parameter in octets. + +*Priority* indicates the priority of the data to be sent when using the CSMA access scheme, i.e., the parameter only has meaning when the connection was established with CfBytes = 0. + +#### 8.5.4.3 MAC\_DATA.confirm + +The MAC\_DATA.confirm primitive is used to confirm that the transmission process of the data has completed. + +The semantics of the primitive are as follows: + +*MAC\_DATA.confirm{ConHandle, Data, Result}* + +The *ConHandle* parameter specifies the connection that was used for data transmission. This handle is the one that was obtained during the connection establishment primitives. + +The *Data* parameter is a buffer of octets that contains the CL data to be transmitted through this connection. + +The *Result* parameter indicates the result of the transmission. This can take one of the values given in Table 8-36. + +**Table 8-36 – Values of the result parameter in MAC\_DATA.confirm primitive** + +| Result | Description | +|-------------|-----------------------------| +| Success = 0 | The send was successful. | +| Timeout = 2 | The send process timed out. | + +#### 8.5.4.4 MAC\_DATA.indication + +The MAC\_DATA.indication primitive notifies the reception of data through a connection to the CL. + +The semantics of the primitive are as follows: + +*MAC\_DATA.indication{ConHandle, Data, DataLength}* + +The *ConHandle* parameter specifies the connection where the data was received. This handle is the one that was obtained during the connection establishment primitives. + +The *Data* parameter is a buffer of octets that contains the CL data received through this connection. + +The *DataLength* parameter is the length of the *Data* parameter in octets. + +### 8.5.5 MAC layer management entity SAPs + +#### 8.5.5.1 General + +The following primitives are all optional. + +The aim is to allow an external management entity to control registration and promotion of the service node, and demotion and unregistration of a service node. The MAC layer would normally perform this automatically, however, in some situations/applications it could be advantageous if this could be externally controlled. Indications are also defined so that an external entity can monitor the status of the MAC. + +#### 8.5.5.2 MLME\_REGISTER + +##### 8.5.5.2.1 General + +The MLME\_REGISTER primitives are used to perform registration and to indicate when registration has been performed. + +##### 8.5.5.2.2 MLME\_REGISTER.request + +The MLME\_REGISTER.request primitive is used to trigger the registration process to a subnetwork through a specific switch node. This primitive may be used for enforcing the selection of a specific switch node that may not necessarily be used if the selection is left automatic. The base node MLME function does not export this primitive. + +The semantics of the primitive could be either of the following: + +$$MLME\_REGISTER.request\{ \}$$ + +Invoking this primitive without any parameter simply invokes the registration process in the MAC and leaves the selection of the subnetwork and switch node to MAC algorithms. Using this primitive enables the MAC to perform fully automatic registration if such a mode is implemented in the MAC. + +$$MLME\_REGISTER.request\{SNA\}$$ + +The *SNA* parameter specifies the subnetwork to which registration should be performed. Invoking the primitive in this format commands the MAC to only register to the specified subnetwork. + +$$MLME\_REGISTER.request\{SID\}$$ + +The *SID* parameter is the SID (switch identifier) of the switch node through which registration needs to be performed. Invoking the primitive in this format commands the MAC to register only to the specified switch node. + +##### 8.5.5.2.3 MLME\_REGISTER.confirm + +The MLME\_REGISTER.confirm primitive is used to confirm the status of completion of the registration process that was initiated by an earlier invocation of the corresponding request primitive. The base node MLME function does not export this primitive. + +The semantics of the primitive are as follows: + +$$MLME\_REGISTER.confirm\{Result, SNA, SID\}$$ + +The *Result* parameter indicates the result of the registration. This can take one of the values given in Table 8-37. + +**Table 8-37 – Values of the result parameter in MLME\_REGISTER.confirm primitive** + +| Result | Description | +|-------------|---------------------------------------------------------------------------------------| +| Done = 0 | Registration to a specified SNA through a specified switch is completed successfully. | +| Timeout = 2 | Registration request timed out. | +| Rejected=1 | Registration request is rejected by the base node of a specified SNA. | +| NoSNA=8 | Specified SNA is not within range. | +| NoSwitch=9 | Switch node with specified EUI-48 is not within range. | + +The *SNA* parameter specifies the subnetwork to which registration is performed. This parameter is of significance only if *Result*=0. + +The *SID* parameter is the SID (switch identifier) of the switch node through which registration is performed. This parameter is of significance only if *Result*=0. + +##### 8.5.5.2.4 MLME\_REGISTER.indication + +The MLME\_REGISTER.indication primitive is used to indicate a status change in the MAC. The service node is now registered to a subnetwork. + +The semantics of the primitive are as follows: + +*MLME\_REGISTER.indication{SNA, SID}* + +The *SNA* parameter specifies the subnetwork to which registration is performed. + +The *SID* parameter is the SID (switch identifier) of the switch node through which registration is performed. + +#### 8.5.5.3 MLME\_UNREGISTER + +##### 8.5.5.3.1 General + +The MLME\_UNREGISTER primitives are used to perform deregistration and to indicate when deregistration has been performed. + +##### 8.5.5.3.2 MLME\_UNREGISTER.request + +The MLME\_UNREGISTER.request primitive is used to trigger the unregistration process. This primitive may be used by management entities if they require the node to unregister for some reason (e.g., register through another switch node or to another subnetwork). The base node MLME function does not export this primitive. + +The semantics of the primitive are as follows: + +*MLME\_UNREGISTER.request{}* + +##### 8.5.5.3.3 MLME\_UNREGISTER.confirm + +The MLME\_UNREGISTER.confirm primitive is used to confirm the status of the completion of the unregister process initiated by an earlier invocation of the corresponding request primitive. The base node MLME function does not export this primitive. + +The semantics of the primitive are as follows: + +*MLME\_UNREGISTER.confirm{Result}* + +The *Result* parameter indicates the result of the registration. This can take one of the values given in Table 8-38. + +**Table 8-38 – Values of the result parameter in MLME\_UNREGISTER.confirm primitive** + +| Result | Description | +|--------------|---------------------------------------------------------------------------------------| +| Done = 0 | Unregister process completed successfully. | +| Timeout = 2 | Unregister process timed out. | +| Redundant=10 | The node is already in disconnected functional state and does not need to unregister. | + +On generation of MLME\_UNREGISTER.confirm, the MAC layer shall not perform any automatic actions that may invoke the registration process again. In such cases, it is up to the management entity to restart the MAC functionality with appropriate MLME\_REGISTER primitives. + +##### 8.5.5.3.4 MLME\_UNREGISTER.indication + +The MLME\_UNREGISTER.indication primitive is used to indicate a status change in the MAC. The service node is no longer registered to a subnetwork. + +The semantics of the primitive are as follows: + +*MLME\_UNREGISTER.indication{}* + +#### 8.5.5.4 MLME\_PROMOTE + +##### 8.5.5.4.1 General + +The MLME\_PROMOTE primitives are used to perform promotion and to indicate when promotion has been performed. + +##### 8.5.5.4.2 MLME\_PROMOTE.request + +The MLME\_PROMOTE.request primitive is used to trigger the promotion process in a service node that is in a terminal functional state. This primitive may be used by management entities to enforce promotion in cases where the node's default functionality does not automatically start the process. Implementations may use such triggered promotions to improve the subnetwork topology from time to time. + +The semantics of the primitive are as follows: + +*MLME\_PROMOTE.request{}* + +The value of PRO.PNA in the promotion message sent to the base node is undefined and implementation-specific. + +##### 8.5.5.4.3 MLME\_PROMOTE.confirm + +The MLME\_PROMOTE.confirm primitive is used to confirm the status of completion of a promotion process that was initiated by an earlier invocation of the corresponding request primitive. + +The semantics of the primitive are as follows: + +*MLME\_PROMOTE.confirm{Result}* + +The *Result* parameter indicates the result of the registration. This can take one of the values given in Table 8-39. + +**Table 8-39 – Values of the result parameter in MLME\_PROMOTE.confirm primitive** + +| Result | Description | +|--------------|------------------------------------------------------| +| Done = 0 | Node is promoted to switch function successfully. | +| Timeout =1 | Promotion process timed out. | +| Rejected=2 | The base node rejected promotion request. | +| Redundant=10 | This device is already functioning as a switch node. | + +##### **8.5.5.4.4 MLME\_PROMOTE.indication** + +The MLME\_PROMOTE.indication primitive is used to indicate a status change in the MAC. The service node is now operating as a switch. + +The semantics of the primitive are as follows: + +*MLME\_PROMOTE.indication{}* + +#### **8.5.5.5 MLME\_DEMOTE** + +##### **8.5.5.5.1 General** + +The MLME\_DEMOTE primitives are used to perform demotion and to indicate when demotion has been performed. + +##### **8.5.5.5.2 MLME\_DEMOTE.request** + +The MLME\_DEMOTE.request primitive is used to trigger a demotion process in a service node that is in a switch functional state. This primitive may be used by management entities to enforce demotion in cases where the node's default functionality does not automatically perform the process. + +The semantics of the primitive are as follows: + +*MLME\_DEMOTE.request{}* + +##### **8.5.5.5.3 MLME\_DEMOTE.confirm** + +The MLME\_DEMOTE.confirm primitive is used to confirm the status of completion of a demotion process that was initiated by an earlier invocation of the corresponding request primitive. + +The semantics of the primitive are as follows: + +*MLME\_DEMOTE.confirm{Result}* + +The *Result* parameter indicates the result of the demotion. This can take one of the values given in Table 8-40. + +**Table 8-40 – Values of the result parameter in MLME\_DEMOTE.confirm primitive** + +| Result | Description | +|--------------|--------------------------------------------------------| +| Done = 0 | Node is demoted to terminal function successfully. | +| Timeout =1 | Demotion process timed out. | +| Redundant=10 | This device is already functioning as a terminal node. | + +When a demotion has been triggered using the MLME\_DEMOTE.request, the terminal will remain demoted. + +##### 8.5.5.5.4 MLME\_DEMOTE.indication + +The MLME\_DEMOTE.indication primitive is used to indicate a status change in the MAC. The service node is now operating as a terminal. + +The semantics of the primitive are as follows: + +*MLME\_DEMOTE.indication{}* + +#### 8.5.5.6 MLME\_RESET + +##### 8.5.5.6.1 General + +The MLME\_RESET primitives are used to reset the MAC into a known "good" status. + +##### 8.5.5.6.2 MLME\_RESET.request + +The MLME\_RESET.request primitive results in the flushing of all transmit and receive buffers and the resetting of all state variables. As a result of invoking of this primitive, a service node will transit from its present functional state to the disconnected functional state. + +The semantics of the primitive are as follows: + +*MLME\_RESET.request{}* + +##### 8.5.5.6.3 MLME\_RESET.confirm + +The MLME\_RESET.confirm primitive is used to confirm the status of the completion of a reset process that was initiated by an earlier invocation of the corresponding request primitive. On the successful completion of the reset process, the MAC entity shall restart all functions starting from the search for a subnetwork (clause 8.3.1). + +The semantics of the primitive are as follows: + +*MLME\_RESET.confirm{Result}* + +The *Result* parameter indicates the result of the reset. This can take one of the values given below. + +**Table 8-41 – Values of the result parameter in MLME\_RESET.confirm primitive** + +| Result | Description | +|------------|----------------------------------------------------------| +| Done = 0 | MAC reset completed successfully. | +| Failed = 1 | MAC reset failed due to internal implementation reasons. | + +#### 8.5.5.7 MLME\_GET + +##### 8.5.5.7.1 General + +The MLME\_GET primitives are used to retrieve individual values from the MAC, such as statistics. + +##### 8.5.5.7.2 MLME\_GET.request + +The MLME\_GET.request queries information about a given PIB attribute. + +The semantics of the primitive are as follows: + +*MLME\_GET.request{PIBAttribute}* + +The PIBAttribute parameter identifies specific attributes as listed in the *Id* fields of tables that list PIB attributes (clause 10.2.3). + +##### 8.5.5.7.3 MLME\_GET.confirm + +The MLME\_GET.confirm primitive is generated in response to the corresponding MLME\_GET.request primitive. + +The semantics of this primitive are as follows: + +$$MLME\_GET.confirm\{status, PIBAttribute, PIBAttributeValue\}$$ + +The *status* parameter reports the result of requested information and can have one of the values given in Table 8-42. + +**Table 8-42 – Values of the status parameter in MLME\_GET.confirm primitive** + +| Result | Description | +|------------|---------------------------------------------------------------| +| Done = 0 | Parameter read successfully. | +| Failed = 1 | Parameter read failed due to internal implementation reasons. | +| BadAttr=11 | Specified PIBAttribute is not supported. | + +The *PIBAttribute* parameter identifies specific attributes as listed in *Id* fields of tables that list PIB attributes (clause 10.2.2). + +The *PIBAttributeValue* parameter specifies the value associated with a given *PIBAttribute*. + +#### 8.5.5.8 MLME\_LIST\_GET + +##### 8.5.5.8.1 General + +The MLME\_LIST\_GET primitives are used to retrieve a list of values from the MAC. + +##### 8.5.5.8.2 MLME\_LIST\_GET.request + +The MLME\_LIST\_GET.request queries a list of values pertaining to a specific class. This special class of PIB attributes are listed in clause 10.2.3.5. + +The semantics of the primitive are as follows: + +$$MLME\_LIST\_GET.request\{PIBListAttribute\}$$ + +The *PIBListAttribute* parameter identifies a specific list that is requested by the management entity. The possible values of *PIBListAttribute* are listed in clause 10.2.3.5. + +##### 8.5.5.8.3 MLME\_LIST\_GET.confirm + +The MLME\_LIST\_GET.confirm primitive is generated in response to the corresponding MLME\_LIST\_GET.request primitive. + +The semantics of this primitive are as follows: + +$$MLME\_LIST\_GET.confirm\{status, PIBListAttribute, PIBListAttributeValue\}$$ + +The *status* parameter reports the result of requested information and can have one of the values given in Table 8-43. + +**Table 8-43 – Values of the status parameter in MLME\_LIST\_GET.confirm primitive** + +| Result | Description | +|------------|---------------------------------------------------------------| +| Done = 0 | Parameter read successfully. | +| Failed = 1 | Parameter read failed due to internal implementation reasons. | +| BadAttr=11 | Specified PIBListAttribute is not supported. | + +The *PIBListAttribute* parameter identifies a specific list as listed in the *Id* field of Table 10-7. + +The *PIBListAttributeValue* parameter contains the actual listing associated with a given *PIBListAttribute*. + +#### 8.5.5.9 MLME\_SET + +##### 8.5.5.9.1 General + +The MLME\_SET primitives are used to set configuration values in the MAC. + +##### 8.5.5.9.2 MLME\_SET.request + +The MLME\_SET.request requests information about a given PIB attribute. + +The semantics of the primitive are as follows: + +*MLME\_SET.request{PIBAttribute, PIBAttributeValue}* + +The *PIBAttribute* parameter identifies a specific attribute as listed in the *Id* fields of tables that list PIB attributes (clause 10.2.3). + +The *PIBAttributeValue* parameter specifies the value associated with given *PIBAttribute*. + +##### 8.5.5.9.3 MLME\_SET.confirm + +The MLME\_SET.confirm primitive is generated in response to the corresponding MLME\_SET.request primitive. + +The semantics of this primitive are as follows: + +*MLME\_SET.confirm{Result}* + +The *Result* parameter reports the result of requested information and can have one of the values given in Table 8-44. + +**Table 8-44 – Values of the result parameter in MLME\_SET.confirm primitive** + +| Result | Description | +|---------------|---------------------------------------------------------| +| Done = 0 | Given value successfully set for specified attribute. | +| Failed = 1 | Failed to set the given value for specified attribute. | +| BadAttr=11 | Specified PIBAttribute is not supported. | +| OutOfRange=12 | Specified PIBAttributeValue is out of acceptable range. | +| ReadOnly=13 | Specified PIBAttributeValue is read only. | + +## 8.6 MAC procedures + +### 8.6.1 Registration + +The initial service node start-up (clause 8.3.1) is followed by a registration process. A service node in a disconnected functional state shall transmit a REG control packet to the base node in order to get itself included in the subnetwork. Since no LNID or SID is allocated to a service node at this stage, the PKT.LNID field shall be set to all-ones and the PKT.SID field shall contain the SID of the switch node through which it seeks attachment to the subnetwork. + +Base nodes may use a registration request as an authentication mechanism. However this Recommendation does not recommend or forbid any specific authentication mechanism and leaves this choice to implementations. + +For all successfully accepted registration requests, the base node shall allocate an LNID that is unique within the domain of the switch node through which the attachment is realized. This LNID shall be indicated in the PKT.LNID field of response (REG\_RSP). The assigned LNID, in combination with the SID of the switch node through which the service node is registered, would form the NID of the registering node. + +Registration is a three-way process. The REG\_RSP shall be acknowledged by the receiving service node with a REG\_ACK message. + +Figure 8-42 represents a successful registration process and Figure 8-43 shows a registration request that is rejected by the base node. Details on specific fields that distinguish one registration message from the other are given in Table 8-9. + +The REG control packet, in all its usage variants, is transmitted unencrypted, but specified fields (REG.SNK and REG.AUK) are encrypted with context-specific encryption keys as explained in clause 8.4.5.3. The encryption of REG.AUK in REG\_RSP, its decryption at the receiving end and subsequent encrypted retransmission using a different encryption key authenticates that the REG\_ACK is from the intended destination. + +![Sequence diagram of the registration process accepted. It shows three vertical lifelines: BASE, SWITCH - j, and NODE. The sequence of messages is: 1. NODE sends REG_REQ to SWITCH - j. 2. SWITCH - j forwards REG_REQ to BASE. 3. BASE sends REG_RSP to SWITCH - j. 4. SWITCH - j forwards REG_RSP to NODE. 5. NODE sends REG_ACK to SWITCH - j. 6. SWITCH - j forwards REG_ACK to BASE. The REG_REQ message from NODE contains: HDR.DO=0, PKT.LNID=0x3FFF, PKT.SID=j, REG.N=0. The REG_RSP message from BASE contains: HDR.DO=1, PKT.LNID=K, PKT.SID=j, REG.N=0. The REG_ACK message from NODE contains: HDR.DO=0, PKT.LNID=K, REG.SID=j, REG.N=0.](20e1585db1a707a774877194c689de82_img.jpg) + +``` +sequenceDiagram + participant NODE + participant SWITCH_j as SWITCH - j + participant BASE + Note right of NODE: REG_REQ + NODE->>SWITCH_j: REG_REQ + Note right of SWITCH_j: REG_REQ + SWITCH_j->>BASE: REG_REQ + Note right of BASE: REG_RSP + BASE->>SWITCH_j: REG_RSP + Note right of SWITCH_j: REG_RSP + SWITCH_j->>NODE: REG_RSP + Note right of NODE: REG_ACK + NODE->>SWITCH_j: REG_ACK + Note right of SWITCH_j: REG_ACK + SWITCH_j->>BASE: REG_ACK +``` + +Sequence diagram of the registration process accepted. It shows three vertical lifelines: BASE, SWITCH - j, and NODE. The sequence of messages is: 1. NODE sends REG\_REQ to SWITCH - j. 2. SWITCH - j forwards REG\_REQ to BASE. 3. BASE sends REG\_RSP to SWITCH - j. 4. SWITCH - j forwards REG\_RSP to NODE. 5. NODE sends REG\_ACK to SWITCH - j. 6. SWITCH - j forwards REG\_ACK to BASE. The REG\_REQ message from NODE contains: HDR.DO=0, PKT.LNID=0x3FFF, PKT.SID=j, REG.N=0. The REG\_RSP message from BASE contains: HDR.DO=1, PKT.LNID=K, PKT.SID=j, REG.N=0. The REG\_ACK message from NODE contains: HDR.DO=0, PKT.LNID=K, REG.SID=j, REG.N=0. + +Figure 8-42 – Registration process accepted + +![Sequence diagram of a rejected registration process. A NODE sends a REG_REQ packet to a SWITCH-j, which then forwards it to a BASE. The BASE responds with a REG_REJ packet to the SWITCH-j, which in turn forwards it to the NODE. The REG_REQ packet contains HDR.DO=0, PKT.LNID=0x3FFF, PKT.SID=j, and REG.N=0. The REG_REJ packet contains HDR.DO=1, PKT.LNID=0x3FFF, PKT.SID=j, and REG.N=1.](3a006a7c9c9934695f0fc731344eff8a_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH-j + participant NODE + NODE->>SWITCH-j: REG_REQ (HDR.DO=0, PKT.LNID=0x3FFF, PKT.SID=j, REG.N=0) + SWITCH-j->>BASE: REG_REQ + BASE->>SWITCH-j: REG_REJ (HDR.DO=1, PKT.LNID=0x3FFF, PKT.SID=j, REG.N=1) + SWITCH-j->>NODE: REG_REJ + +``` + +Sequence diagram of a rejected registration process. A NODE sends a REG\_REQ packet to a SWITCH-j, which then forwards it to a BASE. The BASE responds with a REG\_REJ packet to the SWITCH-j, which in turn forwards it to the NODE. The REG\_REQ packet contains HDR.DO=0, PKT.LNID=0x3FFF, PKT.SID=j, and REG.N=0. The REG\_REJ packet contains HDR.DO=1, PKT.LNID=0x3FFF, PKT.SID=j, and REG.N=1. + +**Figure 8-43 – Registration process rejected** + +When assigning an LNID, the base node shall not reuse an LNID released by an unregister process until after $(macMaxCtlReTx + 1) \times macCtlReTxTimer$ seconds, to ensure that all retransmit packets have left the subnetwork. Similarly, the base node shall not reuse an LNID freed by the keep-alive process until $T_{keep\_alive}$ seconds have passed, using the last known acknowledged $T_{keep\_alive}$ value, or if larger, the last unacknowledged $T_{keep\_alive}$ , for the service node using the LNID. + +During network start-up where the whole network is powered on at once, there will be considerable contention for the medium. It is recommended, but optional, that randomness is added to the first transmission of REQ\_REQ and all subsequent retransmissions. A random delay of maximum duration of 10% of $macCtlReTxTimer$ may be imposed before the first REG\_REQ message and a similar random delay of up to 10% of $macCtlReTxTimer$ may be added to each retransmission. + +### 8.6.2 Unregistration process + +At any point in time, either the base node or the service node may decide to close an existing registration. This version of the Recommendation does not provide provision for rejecting an unregister request. The service node or base node that receives an unregister request shall acknowledge its receipt and take appropriate actions. + +Following a successful unregister, a service node shall move back from its present functional state to a disconnected functional state and the base node may re-use any resources that were reserved for the unregistering node. + +Figure 8-44 shows a successful unregister process initiated from a service node and Figure 8-45 shows an unregister process initiated from the base node. Details on specific fields that identify unregister requests in REG control packets are given in Table 8-9 + +![Sequence diagram of an unregister process initiated by a terminal node (NODE). The NODE sends a REG_UNR_S packet to a SWITCH, which then forwards it to a BASE. The BASE responds with a REG_UNR_B packet to the SWITCH, which in turn forwards it to the NODE. The REG_UNR_S packet contains HDR.DO=0, PKT.LNID=K, and REG.N=1. The REG_UNR_B packet contains HDR.DO=1, PKT.LNID=K, and REG.N=1.](468be155058fd5d2862919eb8ec35496_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant NODE + NODE->>SWITCH: REG_UNR_S (HDR.DO=0, PKT.LNID=K, REG.N=1) + SWITCH->>BASE: REG_UNR_S + BASE->>SWITCH: REG_UNR_B (HDR.DO=1, PKT.LNID=K, REG.N=1) + SWITCH->>NODE: REG_UNR_B + +``` + +Sequence diagram of an unregister process initiated by a terminal node (NODE). The NODE sends a REG\_UNR\_S packet to a SWITCH, which then forwards it to a BASE. The BASE responds with a REG\_UNR\_B packet to the SWITCH, which in turn forwards it to the NODE. The REG\_UNR\_S packet contains HDR.DO=0, PKT.LNID=K, and REG.N=1. The REG\_UNR\_B packet contains HDR.DO=1, PKT.LNID=K, and REG.N=1. + +**Figure 8-44 – Unregistering process initiated by a terminal node** + +![Sequence diagram showing the unregistering process initiated by the base node. The diagram involves three entities: BASE, SWITCH, and NODE. The process starts with the BASE node sending a REG_UNR_B packet to the SWITCH node. The SWITCH node then forwards this packet to the NODE node. The NODE node responds with a REG_UNR_S packet back to the SWITCH node, which in turn forwards it back to the BASE node. The REG_UNR_B packet contains HDR.DO=1, PKT.LNID=K, and REG.N=1. The REG_UNR_S packet contains HDR.DO=0, PKT.LNID=K, and REG.N=1.](21ea5add6a61cc951b5c43ddffefb3ff_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant NODE + Note left of BASE: + BASE->>SWITCH: REG_UNR_B + + Note right of BASE: HDR.DO=1 + + PKT.LNID=K + + REG.N=1 + SWITCH->>NODE: REG_UNR_B + Note right of NODE: + NODE-->>SWITCH: REG_UNR_S + + Note right of NODE: HDR.DO=0 + + PKT.LNID=K + + REG.N=1 + SWITCH-->>BASE: REG_UNR_S + +``` + +Sequence diagram showing the unregistering process initiated by the base node. The diagram involves three entities: BASE, SWITCH, and NODE. The process starts with the BASE node sending a REG\_UNR\_B packet to the SWITCH node. The SWITCH node then forwards this packet to the NODE node. The NODE node responds with a REG\_UNR\_S packet back to the SWITCH node, which in turn forwards it back to the BASE node. The REG\_UNR\_B packet contains HDR.DO=1, PKT.LNID=K, and REG.N=1. The REG\_UNR\_S packet contains HDR.DO=0, PKT.LNID=K, and REG.N=1. + +**Figure 8-45 – Unregistering process initiated by the base node** + +### 8.6.3 Promotion process + +A node that cannot reach any existing switch may send promotion-needed frames so that a terminal can be promoted and begin to switch. During this process, a node that cannot reach any existing switch may send PNPDU so that a nearby terminal can be promoted and begin to act as a switch. During this process, a terminal will receive PNPDU and at its discretion, generate PRO\_REQ control packets to the base node. + +The base node examines the promotion requests during a period of time. It may use the address of the new terminal, provided in the promotion-request packet, to decide whether or not to accept the promotion. It will decide which node shall be promoted, if any, sending a promotion response. The other nodes will not receive any answer to the promotion request to avoid subnetwork saturation. Eventually, the base node may send a rejection if any special situation occurs. If the subnetwork is specially preconfigured, the base node may send terminal node promotion requests directly to a terminal node. + +When a terminal node requests promotion, the PRO.NSID field in the PRO\_REQ\_S message shall be set to all-ones. The PRO.NSID field shall contain an LSID allocated to the promoted node in the PRO\_REQ\_B message. The acknowledging switch node shall set the PRO.NSID field in its PRO\_ACK to the newly allocated LSID. This final PRO\_ACK shall be used by intermediate switch nodes to update their switching tables as described in clause 8.3.5.2. + +When reusing LSIDs that have been released by a demotion process, the base node should not allocate the LSID until after $(macMaxCtlReTx + 1) \times macCtlReTxTimer$ seconds to ensure all retransmit packets that might use that LSID have left the subnetwork. Similarly, the base node shall not reuse an LNID freed by the keep-alive process until $T_{keep\_alive}$ seconds have passed, using the last known acknowledged $T_{keep\_alive}$ value, or if larger, the last unacknowledged $T_{keep\_alive}$ , for the service node using the LNID. + +![Sequence diagram for Figure 8-46: Promotion process initiated by a service node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO_REQ_S, PRO_REQ_B, PRO_ACK, BSI_IND, and BSI_ACK messages, with a BCN message from the NODE.](df803281854ce2cbde7019b5aeefd8cd_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant TERMINAL + participant NODE + + NODE->>TERMINAL: PRN + TERMINAL->>SWITCH: PRO_REQ_S + Note right of TERMINAL: HDR.DO=0 +PRO.N=0 +PRO.NSID=0xFF + SWITCH->>BASE: PRO_REQ_S + BASE->>SWITCH: PRO_REQ_B + Note left of BASE: HDR.DO=1 +PRO.N=0 +PRO.NSID=K + SWITCH->>TERMINAL: PRO_REQ_B + TERMINAL->>SWITCH: PRO_ACK + Note right of SWITCH: HDR.DO=0 +PRO.N=0 +PRO.NSID=K + SWITCH->>BASE: PRO_ACK + BASE->>SWITCH: BSI_IND + SWITCH->>TERMINAL: BSI_IND + TERMINAL->>SWITCH: BSI_ACK + TERMINAL->>NODE: BCN + SWITCH->>BASE: BSI_ACK + +``` + +Sequence diagram for Figure 8-46: Promotion process initiated by a service node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO\_REQ\_S, PRO\_REQ\_B, PRO\_ACK, BSI\_IND, and BSI\_ACK messages, with a BCN message from the NODE. + +**Figure 8-46 – Promotion process initiated by a service node** + +![Sequence diagram for Figure 8-47: Promotion process rejected by the base node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO_REQ_S and PRO_REJ messages.](235e996e83e7d5198cf9d909f5713cdd_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant TERMINAL + participant NODE + + NODE->>TERMINAL: PRN + TERMINAL->>SWITCH: PRO_REQ_S + Note right of TERMINAL: HDR.DO=0 +PRO.N=0 +PRO.NSID=0xFF + SWITCH->>BASE: PRO_REQ_S + BASE->>SWITCH: PRO_REJ + Note left of BASE: HDR.DO=1 +PRO.N=1 +PRO.NSID=0xFF + SWITCH->>TERMINAL: PRO_REJ + +``` + +Sequence diagram for Figure 8-47: Promotion process rejected by the base node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO\_REQ\_S and PRO\_REJ messages. + +**Figure 8-47 – Promotion process rejected by the base node** + +![Sequence diagram for Figure 8-48: Promotion process initiated by the base node. Lifelines: BASE, SWITCH, TERMINAL, SWITCH, NODE. The process involves PRO_REQ_B, PRO_ACK, BSI_IND, BSI_ACK, and BCN messages.](bd33d5bc49161429f4c7da76529bcd18_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH1 as SWITCH + participant TERMINAL + participant SWITCH2 as SWITCH + participant NODE + + BASE->>SWITCH1: PRO_REQ_B +HDR.DO=1 +PRO.N=0 +PRO.NSID=K + SWITCH1->>TERMINAL: PRO_REQ_B + TERMINAL->>SWITCH2: PRO_ACK +HDR.DO=0 +PRO.N=0 +PRO.NSID=K + SWITCH2->>SWITCH1: PRO_ACK + SWITCH1->>BASE: PRO_ACK + BASE->>SWITCH1: BSI_IND + SWITCH1->>TERMINAL: BSI_IND + TERMINAL->>SWITCH2: BSI_ACK + SWITCH2->>NODE: BCN + SWITCH1->>BASE: BSI_ACK + +``` + +Sequence diagram for Figure 8-48: Promotion process initiated by the base node. Lifelines: BASE, SWITCH, TERMINAL, SWITCH, NODE. The process involves PRO\_REQ\_B, PRO\_ACK, BSI\_IND, BSI\_ACK, and BCN messages. + +Figure 8-48 – Promotion process initiated by the base node + +![Sequence diagram for Figure 8-49: Promotion process rejected by a service node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO_REQ_B, PRO_ACK, and PRO_DEM_S messages.](6d697ce8828ba75fddee0a1b7767a7ca_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant TERMINAL + participant NODE + + BASE->>SWITCH: PRO_REQ_B +HDR.DO=1 +PRO.N=0 +PRO.NSID=K + SWITCH->>TERMINAL: PRO_REQ_B + TERMINAL->>SWITCH: PRO_DEM_S +HDR.DO=0 +PRO.N=1 +PRO.NSID=K + SWITCH->>BASE: PRO_DEM_S + +``` + +Sequence diagram for Figure 8-49: Promotion process rejected by a service node. Lifelines: BASE, SWITCH, TERMINAL, NODE. The process involves PRO\_REQ\_B, PRO\_ACK, and PRO\_DEM\_S messages. + +Figure 8-49 – Promotion process rejected by a service node + +### 8.6.4 Demotion process + +The base node or a switch node may decide to discontinue a switching function at any time. The demotion process provides such a mechanism. The PRO control packet is used for all demotion transactions. + +The PRO.NSID field shall contain the SID of the switch node that is being demoted as part of the demotion transaction. The PRO.PNA field is not used in any demotion process transaction and its contents are not interpreted at either end. + +Following the successful completion of a demotion process, a switch node shall immediately stop the transmission of beacons and change from a switch functional state to a terminal functional state. The base node may reallocate the LSID and beacon slot used by the demoted switch after $(macMaxCtlReTx + 1) \times macCtlReTxTimer$ seconds to other terminal nodes requesting promotion. + +The present version of this Recommendation does not specify any explicit message to reject a demotion requested by a peer at the other end. + +![Sequence diagram for Figure 8-50: Demotion process initiated by a service node. The diagram shows three vertical lifelines: BASE, SWITCH, and SWITCH (connected to TERMINAL). The process starts with a PRO_DEM_S message from the right SWITCH to the left SWITCH. The left SWITCH then sends a PRO_DEM_B message to the BASE node. The BASE node responds with a PRO_DEM_B message containing HDR.DO=1, PRO.N=1, and PRO.NSID=K. The left SWITCH receives this and forwards a PRO_DEM_B message to the right SWITCH. The right SWITCH then sends a PRO_DEM_S message to the TERMINAL. The TERMINAL responds with a PRO_DEM_S message containing HDR.DO=0, PRO.N=1, and PRO.NSID=K. The right SWITCH receives this and forwards a PRO_DEM_S message to the left SWITCH. The left SWITCH receives this and forwards a PRO_DEM_S message to the BASE node.](9687bd5e8b62cadba093b0d1b70536cd_img.jpg) + +Sequence diagram for Figure 8-50: Demotion process initiated by a service node. The diagram shows three vertical lifelines: BASE, SWITCH, and SWITCH (connected to TERMINAL). The process starts with a PRO\_DEM\_S message from the right SWITCH to the left SWITCH. The left SWITCH then sends a PRO\_DEM\_B message to the BASE node. The BASE node responds with a PRO\_DEM\_B message containing HDR.DO=1, PRO.N=1, and PRO.NSID=K. The left SWITCH receives this and forwards a PRO\_DEM\_B message to the right SWITCH. The right SWITCH then sends a PRO\_DEM\_S message to the TERMINAL. The TERMINAL responds with a PRO\_DEM\_S message containing HDR.DO=0, PRO.N=1, and PRO.NSID=K. The right SWITCH receives this and forwards a PRO\_DEM\_S message to the left SWITCH. The left SWITCH receives this and forwards a PRO\_DEM\_S message to the BASE node. + +**Figure 8-50 – Demotion process initiated by a service node** + +![Sequence diagram for Figure 8-51: Demotion process initiated by the base node. The diagram shows three vertical lifelines: BASE, SWITCH, and SWITCH (connected to TERMINAL). The process starts with a PRO_DEM_B message from the BASE node to the left SWITCH. The left SWITCH then sends a PRO_DEM_B message to the right SWITCH. The right SWITCH then sends a PRO_DEM_S message to the TERMINAL. The TERMINAL responds with a PRO_DEM_S message containing HDR.DO=0, PRO.N=1, and PRO.NSID=K. The right SWITCH receives this and forwards a PRO_DEM_S message to the left SWITCH. The left SWITCH receives this and forwards a PRO_DEM_S message to the BASE node.](238754529581b74f0696943d436494bb_img.jpg) + +Sequence diagram for Figure 8-51: Demotion process initiated by the base node. The diagram shows three vertical lifelines: BASE, SWITCH, and SWITCH (connected to TERMINAL). The process starts with a PRO\_DEM\_B message from the BASE node to the left SWITCH. The left SWITCH then sends a PRO\_DEM\_B message to the right SWITCH. The right SWITCH then sends a PRO\_DEM\_S message to the TERMINAL. The TERMINAL responds with a PRO\_DEM\_S message containing HDR.DO=0, PRO.N=1, and PRO.NSID=K. The right SWITCH receives this and forwards a PRO\_DEM\_S message to the left SWITCH. The left SWITCH receives this and forwards a PRO\_DEM\_S message to the BASE node. + +**Figure 8-51 – Demotion process initiated by the base node** + +### 8.6.5 Keep-alive process + +The keep-alive process is used to detect when a service node has left the subnetwork because of changes to the network configuration or because of fatal errors it cannot recover from. + +When the service node receives the REG\_RSP packet it uses the REG.TIME field to start a timer $T_{\text{keep\_alive}}$ . For every ALV\_B it receives, it restarts this timer using the value from ALV.TIME. It should also send an ALV\_S to the base node. If the timer ever expires, the service node assumes it has been unregistered by the base node. The message PRO\_REQ does also reset the keep-alive timer to the PRO.TIME value. + +Each switch along the path of an ALV\_B message should keep a copy of the PRO.TIME and then ALV.TIME for each switch node below it in the tree. When the switch does not receive an ALV\_S message from a service node below it for $T_{\text{keep\_alive}}$ as defined in PRO.TIME and ALV.TIME it should remove the switch node entry from its switch table. See clause 8.3.5.2 for more information on the switching table. Additionally a switch node may use the REG.TIME and ALV.TIME to also consider every service node registration status and take it into account for the switching table. + +For every ALV\_S or ALV\_B message sent by the base node or service node, the counter ALV.TX CNT should be incremented before the message is sent. This counter is expected to wrap around. For every ALV\_B or ALV\_S message received by the service node or the base node the counter ALV.RX CNT should be incremented. This counter is also expected to wrap around. These two counters are placed into the ALV\_S and ALV\_B messages. The base node should keep an ALV.TX CNT and ALV.RX CNT separated counter for each service node. These counters are reset to zero in the registration process. + +The algorithm used by the base node to determine when to send ALV\_B messages to registered service nodes and how to determine the value ALV.TIME and REG.TIME is not specified here. + +### 8.6.6 Connection management + +#### 8.6.6.1 Connection establishment + +Connection establishment works end-to-end, connecting the application layers of communicating peers. Owing to the tree topology, most connections in a subnetwork will involve the base node at one end and a service node at the other. However, there may be cases when two service nodes within a subnetwork need to establish connections. Such connections are called direct connections and are described in clause 8.3.6. + +All connection establishment messages use the CON control packet. The various control packets types and specific fields that unambiguously identify them are given in Table 8-11. + +Each successful connection established on the subnetwork is allocated an LCID. The base node shall allocate an LCID that is unique for a given LNID. + +NOTE – Either of the negotiating ends may decide to reject a connection establishment request. The receipt of a connection rejection does not amount to any restrictions on making future connection requests; it may however be advisable. + +![Sequence diagram for connection establishment initiated by a service node.](863f4c0af0db9c27290338ff76162c06_img.jpg) + +This sequence diagram illustrates the connection establishment process initiated by a service node (NODE) in a network with a BASE node and a SWITCH node. The sequence of messages is as follows: 1. NODE sends a CON\_REQ\_S packet to SWITCH. The packet header includes HDR.DO=0, CON.N=0, and CON.LCID=K. 2. SWITCH forwards the request to BASE as a CON\_REQ\_B packet. The header for CON\_REQ\_B includes HDR.DO=1, CON.N=0, and CON.LCID=K. 3. BASE responds with a CON\_REQ\_S packet back to SWITCH. The header for this response includes HDR.DO=1, CON.N=0, and CON.LCID=K. 4. SWITCH then forwards the response to NODE as a CON\_REQ\_B packet. + +Sequence diagram for connection establishment initiated by a service node. + +Figure 8-52 – Connection establishment initiated by a service node + +![Sequence diagram for connection establishment rejected by the base node.](3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg) + +This sequence diagram shows the connection establishment process initiated by a service node (NODE) that is rejected by the base node (BASE). The sequence of messages is: 1. NODE sends a CON\_REQ\_S packet to SWITCH (HDR.DO=0, CON.N=0, CON.LCID=K). 2. SWITCH forwards it to BASE as a CON\_REQ\_B packet (HDR.DO=1, CON.N=0, CON.LCID=K). 3. BASE rejects the request with a CON\_CLS\_B packet back to SWITCH (HDR.DO=1, CON.N=1, CON.LCID=K). 4. SWITCH then forwards the rejection to NODE as a CON\_CLS\_B packet. + +Sequence diagram for connection establishment rejected by the base node. + +Figure 8-53 – Connection establishment rejected by the base node + +![Sequence diagram for connection establishment initiated by the base node.](b33756b534bb4d9e9ceb8d0af4617768_img.jpg) + +This sequence diagram illustrates the connection establishment process initiated by the base node (BASE). The sequence of messages is: 1. BASE sends a CON\_REQ\_B packet to SWITCH (HDR.DO=1, CON.N=0, CON.LCID=K). 2. SWITCH forwards the request to NODE as a CON\_REQ\_S packet (HDR.DO=0, CON.N=0, CON.LCID=K). 3. NODE responds with a CON\_REQ\_S packet back to SWITCH. The header for this response includes HDR.DO=0, CON.N=0, and CON.LCID=K. 4. SWITCH then forwards the response to BASE as a CON\_REQ\_B packet. + +Sequence diagram for connection establishment initiated by the base node. + +Figure 8-54 – Connection establishment initiated by the base node + +![Sequence diagram for connection establishment rejected by a service node. Lifelines: BASE, SWITCH, NODE. BASE sends CON_REQ_B to SWITCH. SWITCH forwards CON_REQ_B to NODE. NODE responds with CON_CLS_S to SWITCH. SWITCH forwards CON_CLS_S to BASE. Message details: CON_REQ_B (HDR.DO=1, CON.N=0, CON.LCID=K); CON_CLS_S (HDR.DO=0, CON.N=1, CON.CID=K).](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant NODE + BASE->>SWITCH: CON_REQ_B (HDR.DO=1, CON.N=0, CON.LCID=K) + SWITCH->>NODE: CON_REQ_B + NODE-->>SWITCH: CON_CLS_S (HDR.DO=0, CON.N=1, CON.CID=K) + SWITCH-->>BASE: CON_CLS_S + +``` + +Sequence diagram for connection establishment rejected by a service node. Lifelines: BASE, SWITCH, NODE. BASE sends CON\_REQ\_B to SWITCH. SWITCH forwards CON\_REQ\_B to NODE. NODE responds with CON\_CLS\_S to SWITCH. SWITCH forwards CON\_CLS\_S to BASE. Message details: CON\_REQ\_B (HDR.DO=1, CON.N=0, CON.LCID=K); CON\_CLS\_S (HDR.DO=0, CON.N=1, CON.CID=K). + +**Figure 8-55 – Connection establishment rejected by a service node** + +#### 8.6.6.2 Connection closing + +Either peer at both ends of a connection may decide to close the connection at any time. The CON control packet is used for all messages exchanged in the process of closing a connection. Only the CON.N field in the CON control packet is relevant in closing an active connection. + +A connection closure request from one end is acknowledged by the other end before the connection is considered closed. The present version of this Recommendation does not have any explicit message for rejecting a connection termination requested by a peer at the other end. + +Figures 8-56 and 8-57 show message exchange sequences in a connection closing process. + +![Sequence diagram for disconnection initiated by a service node. Lifelines: BASE, SWITCH, NODE. NODE sends CON_CLS_S to SWITCH. SWITCH forwards CON_CLS_S to BASE. BASE responds with CON_CLS_B to SWITCH. SWITCH forwards CON_CLS_B to NODE. Message details: CON_CLS_S (HDR.DO=0, CON.N=1, CON.LCID=k); CON_CLS_B (HDR.DO=1, CON.N=1, CON.LCID=k).](7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant NODE + NODE->>SWITCH: CON_CLS_S (HDR.DO=0, CON.N=1, CON.LCID=k) + SWITCH->>BASE: CON_CLS_S + BASE-->>SWITCH: CON_CLS_B (HDR.DO=1, CON.N=1, CON.LCID=k) + SWITCH-->>NODE: CON_CLS_B + +``` + +Sequence diagram for disconnection initiated by a service node. Lifelines: BASE, SWITCH, NODE. NODE sends CON\_CLS\_S to SWITCH. SWITCH forwards CON\_CLS\_S to BASE. BASE responds with CON\_CLS\_B to SWITCH. SWITCH forwards CON\_CLS\_B to NODE. Message details: CON\_CLS\_S (HDR.DO=0, CON.N=1, CON.LCID=k); CON\_CLS\_B (HDR.DO=1, CON.N=1, CON.LCID=k). + +**Figure 8-56 – Disconnection initiated by a service node** + +![Sequence diagram for disconnection initiated by the base node. Lifelines: BASE, SWITCH, NODE. BASE sends CON_CLS_B to SWITCH. SWITCH forwards CON_CLS_B to NODE. NODE responds with CON_CLS_S to SWITCH. SWITCH forwards CON_CLS_S to BASE. Message details: CON_CLS_B (HDR.DO=1, CON.N=1, CON.LCID=k); CON_CLS_S (HDR.DO=0, CON.N=1, CON.LCID=k).](23d9fcc2863a6b0548d6b4e8abf15106_img.jpg) + +``` + +sequenceDiagram + participant BASE + participant SWITCH + participant NODE + BASE->>SWITCH: CON_CLS_B (HDR.DO=1, CON.N=1, CON.LCID=k) + SWITCH->>NODE: CON_CLS_B + NODE-->>SWITCH: CON_CLS_S (HDR.DO=0, CON.N=1, CON.LCID=k) + SWITCH-->>BASE: CON_CLS_S + +``` + +Sequence diagram for disconnection initiated by the base node. Lifelines: BASE, SWITCH, NODE. BASE sends CON\_CLS\_B to SWITCH. SWITCH forwards CON\_CLS\_B to NODE. NODE responds with CON\_CLS\_S to SWITCH. SWITCH forwards CON\_CLS\_S to BASE. Message details: CON\_CLS\_B (HDR.DO=1, CON.N=1, CON.LCID=k); CON\_CLS\_S (HDR.DO=0, CON.N=1, CON.LCID=k). + +**Figure 8-57 – Disconnection initiated by the base node** + +### 8.6.7 Multicast group management + +#### 8.6.7.1 General + +The joining and leaving of a multicast group can be initiated by the base node or the service node. The MUL control packet is used for all messages associated with multicast and the usual retransmit mechanism for control packets is used. These control messages are unicast between the base node and the service node. + +#### 8.6.7.2 Group join + +Multicast group join may be initiated from either the base node or service node. A device shall not start a new join procedure before an existing join procedure started by itself is completed. + +Certain applications may require the base node to selectively invite certain service nodes to join a specific multicast group. In such cases, the base node starts a new group and invites service nodes as required by application. + +Successful and failed group joins initiated from the base node are shown in Figures 8-58 and 8-59. + +![Sequence diagram of a successful group join initiated by the base node. The diagram shows the interaction between a Base node and a Service Node across their CL and MAC layers. The Base node sends a MAC_JOIN.req to its MAC layer, which then sends a MUL_JOIN_B message to the Service Node's MAC layer. The Service Node's MAC layer creates a handle (H_S1) and sends a MAC_JOIN.ind to its CL layer. The CL layer interprets the data and, if the handle is not found, accepts the join. The Service Node's CL layer then sends a MAC_JOIN.resp to its MAC layer, which sends a MAC_JOIN_S message back to the Base node's MAC layer. Finally, the Base node's MAC layer sends a MAC_JOIN.conf to its CL layer, indicating success and providing the handle (H_B or Handle_CL).](737abf1e655afd3324b6b3987945d913_img.jpg) + +The diagram illustrates the sequence of messages for a successful group join initiated by the base node: + +- Base CL to Base MAC:** *MAC\_JOIN.req* (Broadcast, Handle\_CL, EUI, Type, Data, Datalen) +- Base MAC internal:** If Handle\_CL==0, allocate LCID (=LCID\_B) and create handle (=H\_B) +- Base MAC to Service Node MAC:** *MUL\_JOIN\_B* (HDR.DO=1, MUL.N=0, MUL.LCID=LCID\_B) +- Service Node MAC internal:** Create Handle (=H\_S1) +- Service Node MAC to Service Node CL:** *MAC\_JOIN.ind* (Handle=H\_S1, Type, Data, Datalen) +- Service Node CL internal:** Interpret "Data". If existing handle NOT found, accept join. +- Service Node CL to Service Node MAC:** *MAC\_JOIN.resp* (Handle=H\_S1, Accept) +- Service Node MAC to Base MAC:** *MAC\_JOIN\_S* (HDR.DO=0, MUL.N=0, MUL.LCID=LCID\_B) +- Base MAC to Base CL:** *MAC\_JOIN.conf* (H\_B or Handle\_CL, Success) + +Sequence diagram of a successful group join initiated by the base node. The diagram shows the interaction between a Base node and a Service Node across their CL and MAC layers. The Base node sends a MAC\_JOIN.req to its MAC layer, which then sends a MUL\_JOIN\_B message to the Service Node's MAC layer. The Service Node's MAC layer creates a handle (H\_S1) and sends a MAC\_JOIN.ind to its CL layer. The CL layer interprets the data and, if the handle is not found, accepts the join. The Service Node's CL layer then sends a MAC\_JOIN.resp to its MAC layer, which sends a MAC\_JOIN\_S message back to the Base node's MAC layer. Finally, the Base node's MAC layer sends a MAC\_JOIN.conf to its CL layer, indicating success and providing the handle (H\_B or Handle\_CL). + +Figure 8-58 – Successful group join initiated by the base node + +![Sequence diagram showing a failed group join initiated by the base node. The diagram is split into two columns: Base and Service Node. The Base column has CL and MAC lifelines. The Service Node column has MAC and CL lifelines. The sequence starts with MAC_JOIN.req from Base CL to Base MAC. Base MAC checks if Handle_CL==0, allocates LCID (=LCID_B) and creates handle (=H_B). Base MAC sends MUL_JOIN_B to Service Node MAC. Service Node MAC creates handle (=H_S). Service Node MAC sends MAC_JOIN.ind to Service Node CL. Service Node CL interprets 'Data' and rejects the join because an existing handle was found or an admin reason. Service Node CL sends MAC_JOIN.resp with Handle=H_S and Reject. Service Node MAC destroys handle (=H_S). Service Node MAC sends MAC_LEAVE_S to Base MAC. Base MAC checks if Handle_CL==0, destroys handle (=H_B), and deallocates LCID_B. Base MAC sends MAC_JOIN.conf to Base CL with Handle_CL and Reject.](c7111699f84f3e2bc4016b7876f10de6_img.jpg) + +``` + +sequenceDiagram + participant Base + participant Service Node + Note left of Base: Base (CL, MAC) + Note right of Service Node: Service Node (MAC, CL) + + Base->>Base: MAC_JOIN.req +Broadcast +Handle_CL +EUI +Type +Data +DataLen + Note right of Base: If Handle_CL==0, allocate LCID (=LCID_B) and create handle (=H_B) + Base->>Service Node: MUL_JOIN_B +HDR.DO=1 +MULN=0 +MULLCID=LCID_B + Note right of Service Node: Create Handle (=H_S) + Service Node->>Service Node: MAC_JOIN.ind +Handle=H_S +Type +Data +DataLen + Note right of Service Node: Interpret "Data". If existing handle found or admin reason reject join. + Service Node->>Service Node: MAC_JOIN.resp +Handle=H_S +Reject + Note right of Service Node: Destroy Handle (=H_S) + Service Node->>Base: MAC_LEAVE_S +HDR.DO=0 +MULN=1 +MULLCID=LCID_B + Note right of Base: If Handle_CL==0, Destroy Handle (=H_B), Deallocate LCID_B + Base->>Base: MAC_JOIN.conf +Handle_CL +Reject + +``` + +Sequence diagram showing a failed group join initiated by the base node. The diagram is split into two columns: Base and Service Node. The Base column has CL and MAC lifelines. The Service Node column has MAC and CL lifelines. The sequence starts with MAC\_JOIN.req from Base CL to Base MAC. Base MAC checks if Handle\_CL==0, allocates LCID (=LCID\_B) and creates handle (=H\_B). Base MAC sends MUL\_JOIN\_B to Service Node MAC. Service Node MAC creates handle (=H\_S). Service Node MAC sends MAC\_JOIN.ind to Service Node CL. Service Node CL interprets 'Data' and rejects the join because an existing handle was found or an admin reason. Service Node CL sends MAC\_JOIN.resp with Handle=H\_S and Reject. Service Node MAC destroys handle (=H\_S). Service Node MAC sends MAC\_LEAVE\_S to Base MAC. Base MAC checks if Handle\_CL==0, destroys handle (=H\_B), and deallocates LCID\_B. Base MAC sends MAC\_JOIN.conf to Base CL with Handle\_CL and Reject. + +**Figure 8-59 – Failed group join initiated by the base node** + +Successful and failed group joins initiated from the service node are shown in Figures 8-60 and 8-61. + +![Sequence diagram showing a successful group join initiated by the service node. The diagram involves two main entities: Service Node and Base, each with CL (Control Layer) and MAC (Media Access Control) layers. The process starts with a MAC_JOIN.req from Service Node CL to Service Node MAC. Service Node MAC sends a MUL_JOIN_S to Base MAC. Base MAC allocates LCID (=LCID_B1) and creates Handle (=H_B1). Base MAC sends a MAC_JOIN.ind to Base CL. Base CL interprets the data and maps it to the existing handle. Base CL sends a MAC_JOIN.resp to Base MAC. Base MAC checks if H_B1 != H_B2; if so, it deallocates LCID_B1 and destroys H_B1, using H_B2 specific LCID (say LCID_B2). Base MAC sends a MAC_JOIN_B to Service Node MAC. Service Node MAC creates Handle (=H_S). Service Node MAC sends a MAC_JOIN.conf to Service Node CL. Service Node CL receives ConHandle = H_S and Success.](68b20651884fcd557e865537f0803de5_img.jpg) + +``` + +sequenceDiagram + participant SN as Service Node + participant B as Base + Note left of SN: CL + Note left of SN: MAC + Note right of B: MAC + Note right of B: CL + + SN->>SN: MAC_JOIN.req +Broadcast +Type +Data +Datalen + SN->>B: MUL_JOIN_S +HDR.DO=1 +MULN=0 +MULLCID=0 + B->>B: Allocate LCID (=LCID_B1) and create Handle (=H_B1) + B->>B: MAC_JOIN.ind +Handle=H_B1 +EUI +Type +Data +Datalen + B->>B: Interpret "Data" & if possible, map to existing handle + B->>B: MAC_JOIN.resp +Handle=H_B2 +EUI +Accept + B->>B: If (H_B1 != H_B2), deallocate LCID_B1 and destroy H_B1. Use H_B2 specific LCID (say LCID_B2) + B->>SN: MAC_JOIN_B +HDR.DO=0 +MULN=0 +MULLCID=LCID_B + SN->>SN: Create Handle (=H_S) + SN->>SN: MAC_JOIN.conf +ConHandle = H_S +Success + +``` + +Sequence diagram showing a successful group join initiated by the service node. The diagram involves two main entities: Service Node and Base, each with CL (Control Layer) and MAC (Media Access Control) layers. The process starts with a MAC\_JOIN.req from Service Node CL to Service Node MAC. Service Node MAC sends a MUL\_JOIN\_S to Base MAC. Base MAC allocates LCID (=LCID\_B1) and creates Handle (=H\_B1). Base MAC sends a MAC\_JOIN.ind to Base CL. Base CL interprets the data and maps it to the existing handle. Base CL sends a MAC\_JOIN.resp to Base MAC. Base MAC checks if H\_B1 != H\_B2; if so, it deallocates LCID\_B1 and destroys H\_B1, using H\_B2 specific LCID (say LCID\_B2). Base MAC sends a MAC\_JOIN\_B to Service Node MAC. Service Node MAC creates Handle (=H\_S). Service Node MAC sends a MAC\_JOIN.conf to Service Node CL. Service Node CL receives ConHandle = H\_S and Success. + +Figure 8-60 – Successful group join initiated by the service node + +![Sequence diagram showing a failed group join initiated by the service node. The diagram involves two nodes: Service Node and Base, each with CL and MAC layers. The Service Node's CL layer sends a MAC_JOIN.req to its MAC layer, which then sends a MUL_JOIN_S to the Base node's MAC layer. The Base node's MAC layer allocates an LCID and handle, then sends a MAC_JOIN.ind to its CL layer. The Base node's CL layer interprets the data and attempts to map it to an existing handle, but fails (Reject). It then sends a MAC_JOIN.resp to the Base node's MAC layer, which deallocates the LCID and handle. Finally, the Base node's MAC layer sends a MAC_LEAVE_B to the Service Node's MAC layer, which checks if Handle_CL is 0 and destroys the handle, then sends a MAC_JOIN.conf back to the Service Node's CL layer.](0f007a07756791edf7be50672cb010a4_img.jpg) + +``` + +sequenceDiagram + participant SN as Service Node + participant B as Base + Note left of SN: CL + Note left of SN: MAC + Note right of B: MAC + Note right of B: CL + + SN->>SN: MAC_JOIN.req (Broadcast, Type, Data, Datalen) + SN->>B: MUL_JOIN_S (HDR.DO=1, MUL.N=0, MUL.LCID=0) + B->>B: Allocate LCID (=LCID_B1) and create Handle (=H_B1) + B->>B: MAC_JOIN.ind (Handle=H_B1, EUI, Type, Data, Datalen) + B->>B: Interpret "Data" & if possible, map it to existing handle + B-->>B: MAC_JOIN.resp (Handle=H_B2, EUI, Reject) + B->>B: Deallocate LCID_B1 and destroy H_B1 + B->>SN: MAC_LEAVE_B (HDR.DO=0, MUL.N=1, MUL.LCID=0) + Note left of SN: If Handle_CL==0, Destroy Handle (=H_B), Deallocate LCID_B + SN->>SN: MAC_JOIN.conf (ConHandle=0, Reject) + +``` + +Sequence diagram showing a failed group join initiated by the service node. The diagram involves two nodes: Service Node and Base, each with CL and MAC layers. The Service Node's CL layer sends a MAC\_JOIN.req to its MAC layer, which then sends a MUL\_JOIN\_S to the Base node's MAC layer. The Base node's MAC layer allocates an LCID and handle, then sends a MAC\_JOIN.ind to its CL layer. The Base node's CL layer interprets the data and attempts to map it to an existing handle, but fails (Reject). It then sends a MAC\_JOIN.resp to the Base node's MAC layer, which deallocates the LCID and handle. Finally, the Base node's MAC layer sends a MAC\_LEAVE\_B to the Service Node's MAC layer, which checks if Handle\_CL is 0 and destroys the handle, then sends a MAC\_JOIN.conf back to the Service Node's CL layer. + +Figure 8-61 – Failed group join initiated by the service node + +#### 8.6.7.3 Group leave + +Leaving a multicast group operates in the same way as connection removal. Either the base node or service node may decide to leave the group. A notable difference in the group leave process as compared to a group join is that there is no message sequence for rejecting a group leave request. + +![Sequence diagram for leave initiated by the service node. The diagram shows three vertical lifelines: BASE, SWITCH, and NODE. The sequence of messages is: 1. NODE sends MUL_LEAVE_S to SWITCH. The message contains HDR.DO=0, MUL.N=1, and MUL.LCID=k. 2. SWITCH sends MUL_LEAVE_S to BASE. 3. BASE sends MUL_LEAVE_B to SWITCH. The message contains HDR.DO=1, MUL.N=1, and MUL.LCID=k. 4. SWITCH sends MUL_LEAVE_B to NODE.](52ed951cbf3a5e682e913881bc0d13c5_img.jpg) + +Sequence diagram for leave initiated by the service node. The diagram shows three vertical lifelines: BASE, SWITCH, and NODE. The sequence of messages is: 1. NODE sends MUL\_LEAVE\_S to SWITCH. The message contains HDR.DO=0, MUL.N=1, and MUL.LCID=k. 2. SWITCH sends MUL\_LEAVE\_S to BASE. 3. BASE sends MUL\_LEAVE\_B to SWITCH. The message contains HDR.DO=1, MUL.N=1, and MUL.LCID=k. 4. SWITCH sends MUL\_LEAVE\_B to NODE. + +Figure 8-62 – Leave initiated by the service node + +![Sequence diagram for leave initiated by the base node. The diagram shows three vertical lifelines: BASE, SWITCH, and NODE. The sequence of messages is: 1. BASE sends MUL_LEAVE_B to SWITCH. The message contains HDR.DO=1, MUL.N=1, and MUL.LCID=k. 2. SWITCH sends MUL_LEAVE_B to NODE. 3. NODE sends MUL_LEAVE_S to SWITCH. The message contains HDR.DO=0, MUL.N=1, and MUL.LCID=k. 4. SWITCH sends MUL_LEAVE_S to BASE.](d3162014eae89d17bf0117dabb0c8796_img.jpg) + +Sequence diagram for leave initiated by the base node. The diagram shows three vertical lifelines: BASE, SWITCH, and NODE. The sequence of messages is: 1. BASE sends MUL\_LEAVE\_B to SWITCH. The message contains HDR.DO=1, MUL.N=1, and MUL.LCID=k. 2. SWITCH sends MUL\_LEAVE\_B to NODE. 3. NODE sends MUL\_LEAVE\_S to SWITCH. The message contains HDR.DO=0, MUL.N=1, and MUL.LCID=k. 4. SWITCH sends MUL\_LEAVE\_S to BASE. + +Figure 8-63 – Leave initiated by the base node + +### 8.6.8 PHY robustness management + +#### 8.6.8.1 General + +The PHY layer has several parameters that affect the performance of the transmission: power transmission, modulation schema (constellation mapping and convolutional encoding). The transmitter needs feedback about the reception quality to adjust its transmission parameters. This feedback is sent using PRM control packets. + +#### 8.6.8.2 Use of the PHY robustness notification for detecting robustness needs + +There are several sources of information that may be used to detect whether or not the robustness of the PHY is the right one: + +- received packets with invalid CRC; +- ARQ retransmissions; +- control packet retransmissions; +- PRM requests sent by other nodes to the same switch node (in the case of node-to-switch notifications); +- PRM responses. + +This information may be used to decide when to notify that the robustness of the PHY should be changed. This notification may be performed from a service node to a switch node and from a switch node to a service node. For this purpose, the base node works as the root switch in exactly the same way the other switch nodes do. + +#### 8.6.8.3 PHY robustness notification + +![Sequence diagrams for PHY robustness management requested by the switch node.](7e12e1e0d03a03790d2e9d74c3454bff_img.jpg) + +The diagram illustrates two sequence interactions for PHY robustness management requested by the switch node. The participants are BASE, SWITCH, and NODE. + +**Top Sequence:** + +- The SWITCH node sends a **PRM\_REQ** message to the NODE node. The message header contains: `HDR.DO=1`, `PRM.R=0`, and `PRM.N=0`. +- The NODE node responds with a **PRM\_ACK** message. The message header contains: `HDR.DO=0`, `PRM.R=1`, and `PRM.N=0`. + +**Bottom Sequence:** + +- The SWITCH node sends a **PRM\_REQ** message to the NODE node. The message header contains: `HDR.DO=1`, `PRM.R=0`, and `PRM.N=0`. +- The NODE node responds with a **PRM\_REJ** message. The message header contains: `HDR.DO=0`, `PRM.R=1`, and `PRM.N=1`. + +Sequence diagrams for PHY robustness management requested by the switch node. + +Figure 8-64 – PHY robustness management requested by the switch node + +![Sequence diagrams for PHY robustness management requested by the service node.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +The diagram illustrates two sequence interactions for PHY robustness management requested by the service node. The participants are BASE, SWITCH, and NODE. + +**Top Sequence:** + +- The NODE node sends a **PRM\_REQ** message to the SWITCH node. The message header contains: `HDR.DO=0`, `PRM.R=0`, and `PRM.N=0`. +- The SWITCH node responds with a **PRM\_ACK** message. The message header contains: `HDR.DO=1`, `PRM.R=1`, and `PRM.N=0`. + +**Bottom Sequence:** + +- The NODE node sends a **PRM\_REQ** message to the SWITCH node. The message header contains: `HDR.DO=0`, `PRM.R=0`, and `PRM.N=0`. +- The SWITCH node responds with a **PRM\_REJ** message. The message header contains: `HDR.DO=1`, `PRM.R=1`, and `PRM.N=1`. + +Sequence diagrams for PHY robustness management requested by the service node. + +Figure 8-65 – PHY robustness management requested by the service node + +#### 8.6.8.4 PHY robustness changing + +From the PHY point of view there are several parameters that may be adjusted and which affect the transmission robustness: the transmission power and modulation parameters (convolutional encoding and constellation). As a general rule the following rules should be followed: + +- Increase robustness: increase the power and if it is not possible, improve the modulation scheme robustness (reducing throughput). +- Reduce robustness: reduce the modulation scheme robustness (increasing throughput) and if it is not possible, reduce the transmission power. + +### 8.6.9 Channel allocation and de-allocation + +Figure 8-66 below shows a successful channel allocation sequence. All channel allocation requests are forwarded to the base node. Note that in order to assure a contention-free channel allocation along the entire path, the base node allocates non-overlapping times to intermediate switch nodes. In a multi-level subnetwork, the base node may also reuse the allocated time at different levels. While reusing the said time, the base node needs to ensure that the levels that use the same time slots have sufficient separation so that there is no possible interference. + +![Sequence diagram for Figure 8-66: Successful allocation of a CFP period. Lifelines: BASE, SWITCH, NODE. The sequence starts with CFP_ALC_REQ_S from NODE to SWITCH, then from SWITCH to BASE. BASE responds with FRA_CFP_IND to SWITCH, then SWITCH to NODE. BASE also sends CFP_ALC_IND to SWITCH (labeled CFP.LNID=SWITCH) and to NODE (labeled CFP.LNID=NODE). SWITCH then forwards FRA_CFP_IND to NODE.](cf93ada09f25903eceb97d1a89649d36_img.jpg) + +Sequence diagram for Figure 8-66: Successful allocation of a CFP period. Lifelines: BASE, SWITCH, NODE. The sequence starts with CFP\_ALC\_REQ\_S from NODE to SWITCH, then from SWITCH to BASE. BASE responds with FRA\_CFP\_IND to SWITCH, then SWITCH to NODE. BASE also sends CFP\_ALC\_IND to SWITCH (labeled CFP.LNID=SWITCH) and to NODE (labeled CFP.LNID=NODE). SWITCH then forwards FRA\_CFP\_IND to NODE. + +**Figure 8-66 – Successful allocation of a CFP period** + +Figure 8-67 below shows a channel de-allocation request from a terminal device and the resulting confirmation from the base node. + +![Sequence diagram for Figure 8-67: Successful channel de-allocation sequence. Lifelines: Base Node, Switch, Terminal-1. Terminal-1 sends CFP_DALC_REQ to Switch, which is forwarded to Base Node. Base Node responds with CFP_DALC_RSP_Y to Switch, which is forwarded to Terminal-1. Base Node also sends FRA_CFP_IND to Switch, which is forwarded to Terminal-1.](ef0faba51289e3a364ba51e5ef4d1a43_img.jpg) + +Sequence diagram for Figure 8-67: Successful channel de-allocation sequence. Lifelines: Base Node, Switch, Terminal-1. Terminal-1 sends CFP\_DALC\_REQ to Switch, which is forwarded to Base Node. Base Node responds with CFP\_DALC\_RSP\_Y to Switch, which is forwarded to Terminal-1. Base Node also sends FRA\_CFP\_IND to Switch, which is forwarded to Terminal-1. + +**Figure 8-67 – Successful channel de-allocation sequence** + +Figure 8-68 below shows a sequence of events that may lead to a base node re-allocation contention-free slot to a terminal device that already has slots allocated to it. In this example, a de-allocation request from Terminal-2 resulted in two changes: firstly, in the global frame structure, this change is conveyed to the subnetwork in the FRA\_CFP\_IND packet; secondly, it is specific to the time slot allocated to Terminal-1 within the CFP. + +![Sequence diagram showing the de-allocation of a channel. A Base Node sends CFP_DALC_RSP_Y, FRA_CFP_IND, and CFP_CHG_IND messages to a Switch. The Switch then forwards these messages to Terminal-1 and Terminal-2.](3349dc82c6333221b0610be6ee7250b6_img.jpg) + +``` + +sequenceDiagram + participant Base Node + participant Switch + participant Terminal-1 + participant Terminal-2 + Note left of Base Node: De-allocation of channel + Base Node->>Switch: CFP_DALC_RSP_Y + Base Node->>Switch: FRA_CFP_IND + Base Node->>Switch: CFP_CHG_IND + Switch->>Terminal-1: CFP_DALC_RSP_Y + Switch->>Terminal-2: CFP_DALC_RSP_Y + Switch->>Terminal-1: FRA_CFP_IND + Switch->>Terminal-2: FRA_CFP_IND + Switch->>Terminal-1: CFP_CHG_IND + Switch->>Terminal-2: CFP_CHG_IND + +``` + +Sequence diagram showing the de-allocation of a channel. A Base Node sends CFP\_DALC\_RSP\_Y, FRA\_CFP\_IND, and CFP\_CHG\_IND messages to a Switch. The Switch then forwards these messages to Terminal-1 and Terminal-2. + +**Figure 8-68 – De-allocation of channel to one device results in the change of the CFP allocated to another** + +## 8.7 Automatic repeat request (ARQ) + +### 8.7.1 General + +Devices complying with this Recommendation may either implement an ARQ scheme as described in this clause or no ARQ at all. This Recommendation provides low-complexity switch and terminal devices that choose not to implement any ARQ mechanism at all. + +### 8.7.2 Initial negotiation + +ARQ is a connection property. During the initial connection negotiation, the originating device indicates its preference for ARQ or non-ARQ in the CON.ARQ field. The responding device at the other end can indicate its acceptance or rejection of the ARQ in its response. If both devices agree to use ARQ for the connection, all traffic in the connection will use ARQ for acknowledgements, as described in clause 8.7.3. If the responding device rejects the ARQ in its response, the data flowing through this connection will not use ARQ. + +### 8.7.3 ARQ mechanism + +#### 8.7.3.1 General + +The ARQ mechanism works between directly connected peers (original source and final destination), as long as both of them support ARQ implementation. This implies that even for a connection between the base node and a terminal (connected via one or more intermediate switch devices), ARQ works on an end-to-end basis. The behaviour of switch nodes in an ARQ-enabled connection is described in clause 8.7.4. When using ARQ, a unique packet identifier is associated with each packet, to aid in acknowledgement. The packet identifier is 6 bits long and can therefore denote 64 distinct packets. ARQ windowing is supported, with a maximum window size of 32 (5 bits), as described in clause 8.7.3.3. + +#### 8.7.3.2 ARQ PDU + +##### 8.7.3.2.1 General + +The ARQ subheader is placed inside the data packets, after the packet header and before the ORIGINAL packet payload. + +![](315e87b80426782bb6e06222d653f515_img.jpg) + +| | | | +|--------------------|---------------|----------------| +| Generic MAC header | ARQ Subheader | Packet payload | +|--------------------|---------------|----------------| + +**Figure 8-69 – MAC data PDU with ARQ subheader** + +For an ARQ PDU, the PKT.LEN field in the packet header will be set as the ARQ subheader length plus the original packet payload length. By doing this, the intermediate switching node can correctly parse the whole PDU length without the knowledge that this PDU is ARQ-enabled, so that it can transparently relay the ARQ PDU based on the addressing information alone. + +The ARQ subheader contains a set of bytes; each byte containing different subfields. The most significant bit of each byte, the M bit, indicates if there are more bytes in the ARQ subheader. + +![](2d548db0b26b7bf33244320322d5ee2c_img.jpg) + +| | | | | | | | | | | +|---------------|---------------|--|--|--|-----------|--|--|-----|--| +| MSB | | | | | | | | LSB | | +| ARQ.
M = 0 | ARQ.
FLUSH | | | | ARQ.PKTID | | | | | + +**Figure 8-70 – ARQ subheader only with the packet id** + +Figure 8-70 shows an ARQ subheader with the first M bit of 0 and so the subheader is a single byte and contains only the packet ID for the transmitted packet. + +![](ceb9a4217df4b6e301712b3b88b09c69_img.jpg) + +| | | | | | | | | | | +|---------------|---------------|--|--|--|-----------|--|--|-------------------------------------|--| +| MSB | | | | | | | | LSB | | +| ARQ.
M = 1 | ARQ.
FLUSH | | | | ARQ.PKTID | | | ARQ.INFO (variable amount of bytes) | | + +**Figure 8-71 – ARQ subheader with ARQ.INFO** + +Figure 8-71 has the M bit in the first byte of the ARQ subheader set, and so the subheader contains multiple bytes. The first byte contains the packet ID of the transmitted packet and then follows the ARQ.INFO which is a list of one or more bytes, where each byte could have one of the following meanings: + +![](5953341e6a100b62c000fca825371797_img.jpg) + +| | | | | | | | | | | +|---------------|---|--|--|--|-----------|--|--|-----|--| +| MSB | | | | | | | | LSB | | +| ARQ.
M = 0 | 0 | | | | ARQ.ACKID | | | | | + +**Figure 8-72 – ARQ.ACK byte fields** + +![](7d0629aa168bf800e491bcbd1979f262_img.jpg) + +| | | | | | | | | | | +|---------------|---|-----|--|--|-------------|--|--|-----|--| +| MSB | | | | | | | | LSB | | +| ARQ.
M = 1 | 0 | Res | | | ARQ.WINSIZE | | | | | + +**Figure 8-73 – ARQ.WIN byte fields** + +![](6308d51a4454ddd3509eba3e3b6a11a5_img.jpg) + +| | | | | | | | | | | +|-------|---|--|--|--|------------|--|--|-----|--| +| MSB | | | | | | | | LSB | | +| ARQ.M | 1 | | | | ARQ.NACKID | | | | | + +**Figure 8-74 – ARQ.NACK byte fields** + +If there are multiple packets lost, an ARQ.NACK is sent for each of them, from the first packet lost to the last packet lost. When there are several ARQ.NACK they implicitly acknowledge the packets before the first ARQ.NACK, and the packets in between the ARQ.NACKs. If an ARQ.ACK is present, it must be placed at the end of the ARQ subheader, and should refer to an ARQ.ACKID that is later than any other ARQ.NACKID, if present. If there is at least an ARQ.NACK and an ARQ.ACK they also implicitly acknowledge any packet in the middle between the last ARQ.NACKID and the ARQ.ACK. + +For interoperability, a device should be able to receive any well-formed ARQ subheader and should process at least the first ARQ.ACK or ARQ.NACK field. + +The subfields have the following meanings as described in Table 8-45. + +**Table 8-45 – ARQ fields** + +| Field | Description | +|-------------|-------------------------------------------------------------------------------------------------------------------------| +| ARQ.FLUSH | ARQ.FLUSH = 1 If an ACK must be sent immediately.
ARQ.FLUSH = 0 If an ACK is not needed. | +| ARQ.PKTID | TheID of the current packet, if the packet is empty (with no data) this is the ID of the packet that will be sent next. | +| ARQ.ACKID | The identifier with the next packet expected to be received. | +| ARQ.WINSIZE | The window size available from the last acknowledged packet. After a connection is established its window is 1. | +| ARQ.NACKID | Ids of the packets that need to be retransmitted. | + +##### 8.7.3.2.2 ARQ subheader example + +| | | | | | | | | | +|-----|---------------|-------------------|-----------------|---------------|---|-----|------------------|-----| +| MSB | ARQ.
M = 1 | ARQ.
FLUSH = 1 | ARQ.PKTID = 23 | ARQ.
M = 1 | 0 | Res | ARQ.WINSIZE = 16 | LSB | +| | ARQ.
M = 1 | 1 | ARQ.NACKID = 45 | ARQ.
M = 1 | 1 | | ARQ.NACKID = 47 | | +| | ARQ.
M = 1 | 1 | ARQ.NACKID = 48 | ARQ.
M = 1 | 1 | | ARQ.NACKID = 52 | | +| | ARQ.
M = 1 | 1 | ARQ.NACKID = 55 | ARQ.
M = 1 | 1 | | ARQ.NACKID = 56 | | +| | ARQ.
M = 1 | 1 | ARQ.NACKID = 57 | ARQ.
M = 0 | 0 | | ARQ.ACKID = 60 | | + +**Figure 8-75 – Example of an ARQ subheader with all the fields present** + +In this example all the ARQ subheader fields are present. To make it understandable, since both nodes are both transmitters and receivers, the side receiving this header will be called A and the other side transmitting B. The message has the packet ID of 23 if it contains data; otherwise the next data packet to be sent has the packet ID of 23. Since the flush bit is set it needs to be ACKed/NACKed. + +B requests the retransmission of packets 45, 47, 48, 52, 55, 56 and 57. ACK = 60, so it has received packets <45, 46, 49, 50, 51, 53, 54, 58 and 59. + +The window is 16 and it has received and processed up to packet 44 (first NACK = 45), so A can send all packets <= 60; that is, as well as sending the requested retransmits, it can also send packet ID = 60. + +#### 8.7.3.3 Windowing + +A new connection between two peer devices starts with an implicit initial receiver window size of 1 and a packet identifier 0. This window size is a limiting case and the transaction (to start with) would behave like a "Stop and Wait" ARQ mechanism. + +Upon receipt of an ARQ.WIN, the sender would adapt its window size to *ARQ.WINSIZE*. This buffer size is counted from the first packet completely ACK-ed, so if there is a NACK list and then an ACK the window size defines the number of packets from the first NACK-ed packet that could be sent. If there is just an ACK in the packet (without any NACK) the window size determines the number of packets that can be sent from that ACK. + +An *ARQ.WINSIZE* value of 0 may be transmitted back by the receiver to indicate congestion at its end. In such cases, the transmitting end should wait for at least *ARQCongClrTime* before re-transmitting its data. + +#### 8.7.3.4 Flow control + +The transmitter must manage the ACK sending algorithm by the flush bit; it is up to it having a proper ARQ communication. The receiver is only forced to send ACKs when the transmitter has sent a packet with the flush bit set, although the receiver could send more ACKs even if not forced to do it, because the flow control is only a responsibility of the transmitter. + +These are the requisites to be interoperable, but the algorithm is up to the manufacturer. It is strongly recommended to piggyback data-ACK information in outgoing packets, to avoid the transmission of unnecessary packets just for ACK-ing. + +#### 8.7.3.5 Algorithm recommendation + +No normative algorithm is specified. + +#### 8.7.3.6 Usage of ARQ in resource limited devices + +Resource-limited devices may have a low memory and simple implementation of ARQ. They may want to use a window of 1 packet. They will work as a "Stop and Wait" mechanism. + +The ARQ subheader to be generated may be one of the following: + +If there is nothing to acknowledge: + +![](a48594f1a3fecef5e047a7c3a63b1220_img.jpg) + +| | | | | | | | | | | | | | | +|---------------|-----------------|--|--|--|--|--|--|-----------|--|--|--|-----|--| +| MSB | | | | | | | | | | | | LSB | | +| ARQ.
M = 0 | ARQ.
FLUSH=1 | | | | | | | ARQ.PKTID | | | | | | + +**Figure 8-76 – Stop and wait ARQ subheader with only packet ID** + +If there is something to acknowledge carrying data: + +![](461ef997feb933486effd3b0d3504016_img.jpg) + +| | | | | | | | | | | | | | | | | | | | +|---------------|-----------------|--|--|--|--|--|--|-----------|--|--|---------------|-----|--|--|--|-----------|--|--| +| MSB | | | | | | | | | | | | LSB | | | | | | | +| ARQ.
M = 1 | ARQ.
FLUSH=1 | | | | | | | ARQ.PKTID | | | ARQ.
M = 0 | 0 | | | | ARQ.ACKID | | | + +**Figure 8-77 – Stop and wait ARQ subheader with an ACK** + +If there is something to acknowledge but without any data in the packet: + +![](f3a012f283609ae9109e6471db1a9621_img.jpg) + +| | | | | | | | | | | | | | | | | | | | +|---------------|-----------------|--|--|--|--|--|--|-----------|--|--|---------------|-----|--|--|--|-----------|--|--| +| MSB | | | | | | | | | | | | LSB | | | | | | | +| ARQ.
M = 1 | ARQ.
FLUSH=0 | | | | | | | ARQ.PKTID | | | ARQ.
M = 0 | 0 | | | | ARQ.ACKID | | | + +**Figure 8-78 – Stop and wait ARQ subheader without data and with an ACK** + +The ARQ.WINSIZE is not generally transmitted because the window size is already 1 by default, it may only be transmitted to handle congestion and to resume the transmission again. + +### 8.7.4 ARQ packets switching + +All switch nodes shall support transparent bridging of ARQ traffic, whether or not they support ARQ for their own transmission and reception. In this mode, switch nodes are not required to buffer the packets of the ARQ connections for retransmission. + +Some switch nodes may buffer the packets of the ARQ connections, and perform retransmission in response to NACKs for these packets. The following general principles shall be followed: + +- The acknowledged packet identifiers shall have end-to-end coherency. +- The buffering of packets in switch nodes and their retransmissions shall be transparent to the source and destination nodes, i.e., a source or destination node shall not be required to know whether or not an intermediate switch has buffered packets for switched data. + +# 9 Convergence layer + +## 9.1 Overview + +Figure 9-1 shows the overall structure of the convergence layer. + +![Diagram of the convergence layer structure showing Service Specific Convergence Sublayer (SSCS) and Common Part Convergence Sublayer (CPCS).](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +The diagram illustrates the structure of the convergence layer. It is a nested box diagram. The outermost box is labeled "Convergence Layer". Inside this box, there are two main sublayers. The top sublayer is labeled "Service Specific Convergence Sublayer (SSCS)" and contains five boxes: "IEC - 432 SSCS", "IPv4 SSCS", "IPv6 SSCS", "NULL SSCS", and a shaded box labeled "“New Protocol” SSCS". The bottom sublayer is labeled "Common Part Convergence Sublayer (CPCS)" and contains a single box labeled "Segmentation and Reassembly (SAR)". + +Diagram of the convergence layer structure showing Service Specific Convergence Sublayer (SSCS) and Common Part Convergence Sublayer (CPCS). + +Figure 9-1 – Structure of the convergence layer + +The convergence layer is separated into two sublayers. The common part convergence sublayer (CPCS) provides a set of generic services. The service-specific convergence sublayer (SSCS) contains services that are specific to one communication profile. There are several SSCSs, typically one per communication profile, but only one CPCS. The use of CPCS services is optional in that a certain SSCS will use the services it needs from the CPCS, and omit services which are not needed. + +## 9.2 Common part convergence sublayer (CPCS) + +### 9.2.1 General + +This Recommendation defines only one CPCS service: segmentation and reassembly (SAR). + +### 9.2.2 Segmentation and reassembly (SAR) + +#### 9.2.2.1 General + +CPCS SDUs which are larger than 'CIMTUSize-1' bytes are segmented at the CPCS. CPCS SDUs which are equal or smaller than 'CIMTUSize-1' bytes may also optionally be segmented. Segmentation means breaking up a CPCS SDU into smaller parts to be transferred by the MAC layer. At the peer CPCS, the smaller parts (segments) are put back together (i.e., reassembled) to form the complete CPCS SDU. All segments except the last segment of a segmented SDU must be the same size and at most *CIMTUSize* bytes in length. Segments may be decided to be smaller than 'CIMTUSize-1' bytes, e.g., when the channel is poor. The last segment may of course be smaller than 'CIMTUSize-1' bytes. + +In order to keep SAR functionality simple, the *CIMTUSize* is a constant value for all possible modulation/coding combinations at the PHY layer. The value of *CIMTUSize* is such that with any modulation/coding combination it is always possible to transmit a single segment in one PPDU. Therefore, there is no need for discovering a specific MTU between peer CPCSs or modifying the SAR configuration for every change in the modulation/coding combination. In order to increase efficiency, a service node which supports packet aggregation may combine multiple segments into one PPDU when communicating with its peer. + +Segmentation always adds a 1-byte header to each segment. The first 2 bits of an SAR header identify the type of segment. The semantics of the rest of the header information then depend on the type of segment. The structure of different header types is shown in Figure 9-2 and individual fields are explained in Table 9-1. Not all fields are present in each SAR header. Either SAR.NSEGS or SAR.SEQ is present, but not both. + +![Figure 9-2 shows two diagrams of SAR header structures. The left diagram shows a header with SAR.TYPE (0b00) and SAR.NSEGS fields. The right diagram shows a header with SAR.TYPE (0b01 & 0b10) and SAR.SEQ fields. Both diagrams indicate MSB (Most Significant Bit) and LSB (Least Significant Bit) positions.](b99ddca16383b6f00fc70050d695a235_img.jpg) + +The diagram shows two byte structures for SAR headers. Both are 1 byte (8 bits) long. The left header has the first 2 bits as SAR.TYPE (0b00) and the remaining 6 bits as SAR.NSEGS. The right header has the first 2 bits as SAR.TYPE (0b01 & 0b10) and the remaining 6 bits as SAR.SEQ. Both diagrams indicate the MSB (Most Significant Bit) at the left and LSB (Least Significant Bit) at the right. + +Figure 9-2 shows two diagrams of SAR header structures. The left diagram shows a header with SAR.TYPE (0b00) and SAR.NSEGS fields. The right diagram shows a header with SAR.TYPE (0b01 & 0b10) and SAR.SEQ fields. Both diagrams indicate MSB (Most Significant Bit) and LSB (Least Significant Bit) positions. + +**Figure 9-2 – Segmentation and reassembly headers** + +**Table 9-1 – SAR header fields** + +| Name | Length | Description | +|-----------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SAR.TYPE | 2 bits | Type of segment.
  • • 0b00: first segment
  • • 0b01: intermediate segment
  • • 0b10: last segment
  • • 0b11: reserved by ITU-T.
| +| SAR.NSEGS | 6 bits | 'Number of Segments' – 1 | +| SAR.SEQ | 6 bits | Sequence number of segment | + +Every segment (except for the first one) includes a sequence number so that the loss of a segment could be detected in reassembly. The sequence numbering shall start from zero with every new CPCS SDU. The first segment which contains an SAR.SEQ field must have SAR.SEQ = 0. All subsequent segments from the same CPCS SDU shall increase this sequence number so that the SAR.SEQ field adds one with every transmission. + +The value SAR.NSEGS indicates the total number of segments, minus one. So when SAR.NSEGS = 0, the CPCS SDU is sent in one segment. SAR.NSEGS = 63 indicates there will be 64 segments to form the full CPCS SDU. When SAR.NSEGS = 0, it indicates that this first segment is also the last segment. No further segment with SAR.TYPE = 0b01 or 0b10 is to be expected for this one-segment CPCS SDU. + +SAR at the receiving end shall buffer all segments and deliver only fully reassembled CPCS SDUs to the SSCS above. Should reassembly fail due to a segment not being received or too many segments being received, etc., SAR shall not deliver any incomplete CPCS SDU to the SSCS above. + +#### 9.2.2.2 SAR constants + +Table 9-2 shows the constants for the SAR service. + +**Table 9-2 – SAR constants** + +| Constant | Value | +|-----------------|-----------------------------------| +| CIMTUSize | 256 bytes | +| CIMaxAppPktSize | Max value (SAR.NSEGS) x CIMTUSize | + +## 9.3 NULL specific service convergence sublayer (NULL SSCS) + +### 9.3.1 Overview + +Null SSCS provides the MAC layer with a transparent path to upper layers, being as simple as possible and minimizing overheads. It is intended for applications that do not need any special convergence capability. + +The unicast and multicast connections of this SSCS shall use the SAR service, as defined in clause 9.2.2. If they do not need the SAR service, they shall still include the SAR header (notifying just one segment). + +The CON.TYPE and MUL.TYPE (see Annex C) for unicast connections and multicast groups shall use the same type that has already been defined for the application that makes use of this null SSCS. + +### 9.3.2 Primitives + +Null SSCS primitives are just a direct mapping of the MAC primitives. A full description of every primitive is avoided, because the mapping is direct and they will work as the ones of the MAC layer. + +The directly mapped primitives have exactly the same parameters as the ones in the MAC layer and perform the same functionality. The set of primitives that are directly mapped are shown below. + +**Table 9-3 – Primitive mapping between the null SSCS primitives and the MAC layer primitives** + +| Null SSCS mapped to ... | ... a MAC primitive | +|------------------------------|--------------------------| +| CL_NULL_ESTABLISH.request | MAC_ESTABLISH.request | +| CL_NULL_ESTABLISH.indication | MAC_ESTABLISH.indication | +| CL_NULL_ESTABLISH.response | MAC_ESTABLISH.response | +| CL_NULL_ESTABLISH.confirm | MAC_ESTABLISH.confirm | +| CL_NULL_RELEASE.request | MAC_RELEASE.request | +| CL_NULL_RELEASE.indication | MAC_RELEASE.indication | +| CL_NULL_RELEASE.response | MAC_RELEASE.response | +| CL_NULL_RELEASE.confirm | MAC_RELEASE.confirm | +| CL_NULL_JOIN.request | MAC_JOIN.request | +| CL_NULL_JOIN.indication | MAC_JOIN.indication | +| CL_NULL_JOIN.response | MAC_JOIN.response | +| CL_NULL_JOIN.confirm | MAC_JOIN.confirm | +| CL_NULL_LEAVE.request | MAC_LEAVE.request | +| CL_NULL_LEAVE.indication | MAC_LEAVE.indication | +| CL_NULL_LEAVE.response | MAC_LEAVE.response | +| CL_NULL_LEAVE.confirm | MAC_LEAVE.confirm | +| CL_NULL_DATA.request | MAC_DATA.request | +| CL_NULL_DATA.indication | MAC_DATA.indication | +| CL_NULL_DATA.confirm | MAC_DATA.confirm | +| CL_NULL_SEND.request | MAC_SEND.request | +| CL_NULL_SEND.indication | MAC_SEND.indication | +| CL_NULL_SEND.confirm | MAC_SEND.confirm | + +## 9.4 IPv4 specific service convergence sublayer (IPv4 SSCS) + +### 9.4.1 Overview + +The IPv4 SSCS provides an efficient method for transferring IPv4 packets over the ITU-T G.9904 subnetworks. Several conventions do apply: + +- A service node can send IPv4 packets to the base node or to other service nodes. +- It is assumed that the base node acts as a router between the ITU-T G.9904 subnetwork and any other network. The base node could also act as an NAT. How the base node connects to the other networks is beyond the scope of this Recommendation. +- In order to keep implementations simple, only one single route is supported per local IPv4 address. +- Service Nodes may use statically configured IPv4 addresses or DHCP to obtain IPv4 addresses. +- The base node performs IPv4 to EUI-48 address resolution. Each service node registers its IPv4 address and EUI-48 address with the base node (see clause 9.4.2). Other service nodes can then query the base node to resolve an IPv4 address into an EUI-48 address. This requires the establishment of a dedicated connection with the base node for address resolution. +- The IPv4 SSCS performs the routing of IPv4 packets. In other words, the IPv4 SSCS will decide whether the packet should be sent directly to another service node or forwarded to the configured gateway. +- Although IPv4 is a connectionless protocol, the IPv4 SSCS is connection-oriented. Once address resolution has been performed, a connection is established between the source and destination service node for the transfer of IPv4 packets. This connection is maintained while traffic is being transferred and may be closed after a period of inactivity. +- The CPCS (see clause 9.2) SAR sublayer shall always be present with the IPv4 convergence layer. Generated MSDUs are at most 'CIMTUSize' bytes long and upper layer PDU messages are not expected to be longer than CIMaxAppPktSize. +- Optionally TCP/IPv4 headers may be compressed. Compression is negotiated as part of the connection establishment phase. +- The broadcasting of IPv4 packets is supported using the MAC broadcast mechanism. +- The multicasting of IPv4 packets is supported using the MAC multicast mechanism. + +The IPv4 SSCS has a number of connection types. For address resolution there is a connection to the base node. For IPv4 data transfer there is one connection per destination node: with the base node that acts as the IPv4 gateway to other networks or to/with any other node in the same subnetwork. This is shown in Figure 9-3. + +![Diagram illustrating IPv4 SSCS connections between a Base node and various service nodes (Switches and Terminals).](34b381406f073080ef510a32772b2612_img.jpg) + +The diagram shows a central 'A: Base node' at the top. Below it are two rows of service nodes. The first row contains 'B: Switch', 'C: Terminal', 'D: Switch', and 'E: Terminal'. The second row contains 'F: Terminal', 'G: Terminal', and 'H: Terminal'. Solid lines represent 'IPv4 SSCS address resolution connection' and connect the Base node to every service node. Dashed lines represent 'IPv4 SSCS data transfer connection' and connect service nodes to each other: B to F, C to G, D to H, and E to G. + +—— IPv4 SSCS address resolution connection +- - - - IPv4 SSCS data transfer connection + +G.9904(12)\_F9-3 + +Diagram illustrating IPv4 SSCS connections between a Base node and various service nodes (Switches and Terminals). + +Figure 9-3 – IPv4 SSCS connection example + +Here, nodes B, E and F have address resolution connections to the base node. Node E has a data connection to the base node and node F. Node F also has a data connection to node B. The figure does not show broadcast and multicast connections. + +### **9.4.2 Address resolution** + +#### **9.4.2.1 General** + +The IPv4 layer will present the IPV4 SSCS with an IPv4 packet to be transferred. The IPV4 SSCS is responsible for determining which service node the packet should be delivered to using the IPv4 addresses in the packet. The IPV4 SSCS must then establish a connection to the destination if one does not already exist so that the packet can be transferred. Three classes of IPv4 addresses can be used and the following subclauses describe how these addresses are resolved into EUI-48 addresses. + +#### **9.4.2.2 Unicast addresses** + +##### **9.4.2.2.1 General** + +IPv4 unicast addresses must be resolved into unicast EUI-48 addresses. The base node maintains a database of IPv4 addresses and EUI-48 addresses. Address resolution then operates by querying this database. A service node must establish a connection to the address resolution service running on the base node, using the connection type value TYPE (see Annex C) TYPE\_CL\_IPv4\_AR. No data should be passed in the connection establishment. Using this connection, the service node can use two mechanisms as defined in the following paragraphs. + +##### **9.4.2.2.2 Address registration and unregistration** + +A service node uses the AR\_REGISTER\_S message to register an IPv4 address and the corresponding EUI-48 address; this means a request from the base node to record inside its registration table, the IPv4 address and its corresponding service node EUI-48. The base node will acknowledge an AR\_REGISTER\_B message. The service node may register multiple IPv4 addresses for the same EUI-48 address. + +A service node uses the AR\_DEREGISTER\_S message to unregister an IPv4 address and the corresponding EUI-48 address; this means requests from the base node to delete inside its registration table, the entry corresponding to the concerned IPv4 address. The base node will acknowledge it with an AR\_DEREGISTER\_B message. + +When the IPv4 address resolution connection between the service node and the base node is closed, the base node should remove all addresses associated with that connection. + +##### **9.4.2.2.3 Address look-up** + +A service node uses the AR\_LOOKUP\_S message to perform a look-up. The message contains the IPv4 address to be resolved. The base node will respond with an AR\_LOOKUP\_B message that contains an error code and, if there is no error, the EUI-48 address associated with the IPv4 address. If the base node has multiple entries in its database for the same IPv4 address, the possible returned EUI-48 address is undefined. + +#### **9.4.2.3 Broadcast address** + +The IPv4 broadcast address 255.255.255.255 maps to a MAC broadcast connection with an LCID equal to LCI\_CL\_IPv4\_BROADCAST. All IPv4 broadcast packets will be sent to this connection. When an IPv4 broadcast packet is received on this connection, the IPv4 address should be examined to determine if it is a broadcast packet for the subnetwork in which the node has an IPv4 address. Only broadcast packets from member subnets should be passed up the IPv4 protocol stack. + +#### 9.4.2.4 Multicast addresses + +Multicast IPv4 addresses are mapped to an ITU-T G.9904 MAC multicast connection by the base node using an address resolution protocol. + +To join a multicast group, AR\_MCAST\_REG\_S is sent from the service node to the base node with the IPv4 multicast address. The base node will reply with an AR\_MCAST\_REG\_B that contains the LCID value assigned to the said multicast address. However, the base node may also allocate other LCIDs which are not in use. The service node can then join a multicast group (see clause 8.6.7.2) for the given LCID to receive IPv4 multicast packets. These LCID values can be reused so that multiple IPv4 destination multicast addresses can be seen on the same LCID. To leave the multicast group, AR\_MCAST\_UNREG\_S is sent from the service node to the base node with the IPv4 multicast address. The base node will acknowledge it with an AR\_MCAST\_UNREG\_B message. + +When a service node wants to send an IPv4 multicast datagram, it just uses the appropriate LCID. If the service node has not joined the multicast group, it first needs to learn the LCID to be used. The process with AR\_MCAST\_REG\_{S|B} messages as described above can be used. While IPv4 multicast packets are still being sent, the service node remains registered to the multicast group. $T_{\text{mcast\_reg}}$ after the last IPv4 multicast datagram was sent, the service node should unregister from the multicast group, by means of AR\_MCAST\_UNREG\_{S|B} messages. The nominal value of $T_{\text{mcast\_reg}}$ is 10 minutes; however, other values may be used. + +#### 9.4.2.5 Retransmission of address resolution packets + +The connection between the service node and the base node for address resolution is not reliable if the MAC ARQ is not used. The service node is responsible for making retransmissions if the base node does not respond in one second. It is not considered an error when the base node receives the same registration requests multiple times or is asked to remove a registration that does not exist. These conditions can be the result of retransmissions. + +### 9.4.3 IPv4 packet transfer + +For packets to be transferred, a connection needs to be established between the source and destination nodes. The IPV4 SSCS will examine each IPv4 packet to determine the destination EUI-48 address. If a data connection to the destination already exists, the packet is sent. To establish this, IPv4 SSCS keeps a table for each connection, with the information shown in Table 9-4 (see [IETF RFC 1144]). To use this table, it is first necessary to determine if the IPv4 destination address is in the local subnetwork or if a gateway has to be used. The netmask associated with the local IPv4 address is used to determine this. If the IPv4 destination address is not in the local subnetwork, the address of the default gateway is used instead of the destination address when the table is searched. + +**Table 9-4 – IPV4 SSCS table entry** + +| Parameter | Description | +|-----------------------|-----------------------------------------------| +| CL_IPv4_Con.Remote_IP | Remote IPv4 address of this connection | +| CL_IPv4_Con.ConHandle | MAC connection handle for the connection | +| CL_IPv4_Con.LastUsed | Timestamp of last packet received/transmitted | +| CL_IPv4_Con.HC | Header compression scheme being used | +| CL_IPv4_CON.RxSeq | Next expected receive sequence number | +| CL_IPv4_CON.TxSeq | Sequence number for next transmission | + +The IPV4 SSCS may close a connection when it has not been used for an implementation-defined time period. When the connection is closed the entry for the connection is removed at both ends of the connection. + +When a connection to the destination does not exist, more work is necessary. The address resolution service is used to determine the EUI-48 address of the remote IPv4 address if it is local or the gateway associated with the local address if the destination address is in another subnetwork. When the base node replies with the EUI-48 address of the destination service node, a MAC connection is established with the remote device. The TYPE value of this connection is TYPE\_CL\_IPv4\_UNICAST. The data passed in the request message is defined in clause 9.4.7.4. The local IPv4 address is provided so that the remote device can add the new connection to its cache of connections for sending data in the opposite direction. The use of Van Jacobson (VJ) header compression is also negotiated as part of the connection establishment. Once the connection has been established, the IPv4 packet can be sent. + +When the packet is addressed to the IPv4 broadcast address, the packet has to be sent using the MAC broadcast service. When the IPV4 SSCS is opened, a broadcast connection is established for transferring all broadcast packets. The broadcast IPv4 packet is simply sent to this connection. Any packet received on this broadcast connection is passed to the IPv4 protocol stack. + +### 9.4.4 Segmentation and reassembly + +The IPV4 SSCS should support IPv4 packets with an MTU of 1500 bytes. This requires the use of SAR (see clause 9.2.2). + +### 9.4.5 Header compression + +Van Jacobson TCP/IP header compression is an optional feature in the IPv4 SSCS. The use of VJ compression is negotiated as part of the connection establishment phase of the connection between two service nodes. + +VJ compression is designed for use over a point-to-point link layer that can inform the decompressor when packets have been corrupted or lost. When there are errors or lost packets, the decompressor can then resynchronize with the compressor. Without this resynchronization process, erroneous packets will be produced and passed up the IPv4 stack. + +The MAC layer does not provide the facility of detecting lost packets or reporting corrupt packets. Thus, it is necessary to add this functionality in the IPV4 SSCS. The IPV4 SSCS maintains two sequence numbers when VJ compression is enabled for a connection. These sequence numbers are 8 bits in size. When transmitting an IPv4 packet, the CL\_IPv4\_CON.TxSeq sequence number is placed in the packet header, as shown in clause 9.4.3. The sequence number is then incremented. Upon receipt of a packet, the sequence number in the received packet is compared against CL\_IPv4\_CON.RxSeq. If they differ, TYPE\_ERROR, as defined in [IETF RFC1144], is passed to the decompressor. The CL\_IPv4\_CON.RxSeq value is always updated to the value received in the packet header. + +Header compression should never be negotiated for broadcast or multicast packets. + +### 9.4.6 Quality of service mapping + +The ITU-T G.9904 MAC specifies that the contention-based access mechanism supports four priority levels (1-4). Level 1 is used for MAC signalling messages, but not exclusively so. + +IPv4 packets include a type of service (TOS) field in the header to indicate the QoS the packet would like to receive. Three bits of the TOS indicate the IP precedence. The following table specifies how the IP precedence is mapped into the ITU-T G.9904 MAC priority. + +**Table 9-5 – Mapping IPv4 precedence to ITU-T G.9904 MAC priority** + +| IP precedence | MAC priority | +|----------------------------|--------------| +| 000 – Routine | 4 | +| 001 – Priority | 4 | +| 010 – Immediate | 3 | +| 011 – Flash | 3 | +| 100 – Flash Override | 2 | +| 101 – Critical | 2 | +| 110 – Internetwork Control | 1 | +| 111 – Network Control | 1 | + +### **9.4.7 Packet formats and connection data** + +#### **9.4.7.1 General** + +This clause defines the format of IPV4 SSCS PDUs. + +#### **9.4.7.2 Address resolution PDUs** + +##### **9.4.7.2.1 General** + +The following PDUs are transferred over the address resolution connection between the service node and the base node. The following clauses define AR.MSG values in the range of 0 to 11. All higher values are reserved for later versions of this Recommendation. + +##### **9.4.7.2.2 AR\_REGISTER\_S** + +Table 9-6 shows the address resolution register message sent from the service node to the base node. + +**Table 9-6 – AR\_REGISTER\_S message format** + +| Name | Length | Description | +|-----------|---------|---------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_REGISTER_S = 0
| +| AR.IPv4 | 32-bits | IPv4 address to be registered | +| AR.EUI-48 | 48-bits | EUI-48 to be registered | + +##### **9.4.7.2.3 AR\_REGISTER\_B** + +Table 9-7 shows the address resolution register acknowledgment message sent from the base node to the service node. + +**Table 9-7 – AR\_REGISTER\_B message format** + +| Name | Length | Description | +|-----------|---------|---------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_REGISTER_B = 1
| +| AR.IPv4 | 32-bits | Registered IPv4 address | +| AR.EUI-48 | 48-bits | EUI-48 registered | + +The AR.IPv4 and AR.EUI-48 fields are included in the AR\_REGISTER\_B message so that the service node can perform multiple overlapping registrations. + +##### 9.4.7.2.4 AR\_UNREGISTER\_S + +Table 9-8 shows the address resolution unregister message sent from the service node to the base node. + +**Table 9-8 – AR\_UNREGISTER\_S message format** + +| Name | Length | Description | +|-----------|---------|---------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type.
• For AR_UNREGISTER_S = 2 | +| AR.IPv4 | 32-bits | IPv4 address to be unregistered | +| AR.EUI-48 | 48-bits | EUI-48 to be unregistered | + +##### 9.4.7.2.5 AR\_UNREGISTER\_B + +Table 9-9 shows the address resolution unregister acknowledgment message sent from the base node to the service node. + +**Table 9-9 – AR\_UNREGISTER\_B message format** + +| Name | Length | Description | +|-----------|---------|--------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_UNREGISTER_B = 3 | +| AR.IPv4 | 32-bits | Unregistered IPv4 address | +| AR.EUI-48 | 48-bits | Unregistered EUI-48 | + +The AR.IPv4 and AR.EUI-48 fields are included in the AR\_UNREGISTER\_B message so that the service node can perform multiple overlapping unregistrations. + +##### 9.4.7.2.6 AR\_LOOKUP\_S + +Table 9-10 shows the address resolution look-up message sent from the service node to the base node. + +**Table 9-10 – AR\_LOOKUP\_S message format** + +| Name | Length | Description | +|---------|---------|----------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_LOOKUP_S = 4 | +| AR.IPv4 | 32-bits | IPv4 address to look up | + +##### 9.4.7.2.7 AR\_LOOKUP\_B + +Table 9-11 shows the address resolution look-up response message sent from the base node to the service node. + +**Table 9-11 – AR\_LOOKUP\_B message format** + +| Name | Length | Description | +|-----------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_LOOKUP_B = 5
| +| AR.IPv4 | 32-bits | IPv4 address looked up | +| AR.EUI-48 | 48-bits | EUI-48 for IPv4 address | +| AR.Status | 8-bits | Look-up status, indicating if the address was found or an error occurred:
  • 0 = found, AR.EUI-48 valid
  • 1 = unknown, AR.EUI-48 undefined.
| + +The look-up may fail if the requested address has not been registered. In that case, AR.Status will have a value other than zero and the contents of AR.EUI-48 will be undefined. The look-up is only successful when AR.Status is zero. In that case, the EUI-48 field contains the resolved address. + +##### 9.4.7.2.8 AR\_MCAST\_REG\_S + +Table 9-12 shows the multicast address resolution register message sent from the service node to the base node. + +**Table 9-12 – AR\_MCAST\_REG\_S message format** + +| Name | Length | Description | +|---------|---------|----------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_MCAST_REG_S = 8
| +| AR.IPv4 | 32-bits | IPv4 multicast address to be registered | + +##### 9.4.7.2.9 AR\_MCAST\_REG\_B + +Table 9-13 shows the multicast address resolution register acknowledgment message sent from the base node to the service node. + +**Table 9-13 – AR\_MCAST\_REG\_B message format** + +| Name | Length | Description | +|----------|---------|----------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_MCAST_REG_B = 9
| +| AR.IPv4 | 32-bits | IPv4 multicast address registered | +| Reserved | 2-bits | Reserved by ITU-T. Should be encoded as 0 | +| AR.LCID | 6-bits | LCID assigned to this IPv4 multicast address | + +The AR.IPv4 field is included in the AR\_MCAST\_REG\_B message so that the service node can perform multiple overlapping registrations. + +##### 9.4.7.2.10 AR\_MCAST\_UNREG\_S + +Table 9-14 shows the multicast address resolution unregister message sent from the service node to the base node. + +**Table 9-14 – AR\_MCAST\_UNREG\_S message format** + +| Name | Length | Description | +|---------|---------|----------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_MCAST_UNREG_S = 10 | +| AR.IPv4 | 32-bits | IPv4 multicast address to be unregistered | + +##### **9.4.7.2.11 AR\_MCAST\_UNREG\_B** + +Table 9-15 shows the multicast address resolution unregister acknowledgment message sent from the base node to the service node. + +**Table 9-15 – AR\_MCAST\_UNREG\_B message format** + +| Name | Length | Description | +|---------|---------|----------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_MCAST_UNREG_B = 11 | +| AR.IPv4 | 32-bits | IPv4 multicast address unregistered | + +The AR.IPv4 field is included in the AR\_MCAST\_UNREG\_B message so that the service node can perform multiple overlapping unregistrations. + +#### **9.4.7.3 IPv4 packet format** + +##### **9.4.7.3.1 General** + +The following PDU formats are used for transferring IPv4 packets between service nodes. Two formats are defined. The first format is for when header compression is not used. The second format is for Van Jacobson header compression. + +##### **9.4.7.3.2 IPv4 packet format, no negotiated header compression** + +When no header compression has been negotiated, the IPv4 packet is simply sent as is, without any header. + +**Table 9-16 – IPv4 packet format without negotiated header compression** + +| Name | Length | Description | +|----------|----------|-----------------| +| IPv4.PKT | n-octets | The IPv4 packet | + +##### **9.4.7.3.3 IPv4 packet format with VJ header compression** + +With Van Jacobsen header compression, a one-octet header is needed before the IPv4 packet. + +**Table 9-17 – IPv4 packet format with VJ header compression negotiated** + +| Name | Length | Description | +|-----------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IPv4.Type | 2-bits | Type of compressed packet:
• IPv4.Type = 0 – TYPE_IP
• IPv4.Type = 1 – UNCOMPRESSED_TCP
• IPv4.Type = 2 – COMPRESSED_TCP
• IPv4.Type = 3 – TYPE_ERROR. | +| IPv4.Seq | 6-bits | Packet sequence number | +| IPv4.PKT | n-octets | The IPv4 packet | + +The IPv4.Type value TYPE\_ERROR is never sent. It is a pseudo packet type used to tell the decompressor that a packet has been lost. + +#### 9.4.7.4 Connection data + +##### 9.4.7.4.1 General + +When a connection is established between service nodes for the transfer of IPv4 packets, data is also transferred in the connection request packets. This data allows the negotiation of compression and notification of the IPv4 address. + +##### 9.4.7.4.2 Connection data from the initiator + +Table 9-18 shows the connection data sent by the initiator. + +**Table 9-18 – Connection signalling data sent by the initiator** + +| Name | Length | Description | +|-----------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 6-bits | Reserved by ITU-T. Should be encoded as 0 in this version of the IPV4 SSCS protocol. | +| Data.HC | 2-bit | Header compression
  • • Data.HC = 0 – No compression requested
  • • Data.HC = 1 – VJ Compression requested
  • • Data.HC = 2, 3 – Reserved by ITU-T.
| +| Data.IPv4 | 32-bits | IPv4 address of the initiator | + +If the device accepts the connection, it should copy the Data.IPv4 address into a new table entry along with the negotiated Data.HC value. + +##### 9.4.7.4.3 Connection data from the responder + +Table 9-19 shows the connection data sent in response to the connection request. + +**Table 9-19 – Connection signalling data sent by the responder** + +| Name | Length | Description | +|----------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 6-bits | Should be encoded as zero in this version of the IPV4 SSCS protocol. | +| Data.HC | 2-bit | Header compression negotiated:
  • • Data.HC = 0 – No compression permitted
  • • Data.HC = 1 – VJ Compression negotiated
  • • Data.HC = 2,3 – Reserved by ITU-T.
| + +A header compression scheme can only be used when it is supported by both service nodes. The responder may only set Data.HC to 0 or the same value as that received from the initiator. When the same value is used, it indicates that the requested compression scheme has been negotiated and will be used for the connection. Setting Data.HC to 0 allows the responder to deny the request for that header compression scheme or force the use of no header compression. + +### 9.4.8 Service access point + +#### 9.4.8.1 General + +This clause defines the service access point used by the IPv4 layer to communicate with the IPV4 SSCS. + +#### 9.4.8.2 Opening and closing the IPv4 SSCS + +##### 9.4.8.2.1 General + +The following primitives are used to open and close the IPv4 SSCS. The IPv4 SSCS may be opened once only. The IPv4 layer may close the IPv4 SSCS when the IPv4 interface is brought down. The IPv4 SSCS will also close the IPv4 SSCS when the underlying MAC connection to the base node has been lost. + +##### 9.4.8.2.2 CL\_IPv4\_ESTABLISH.request + +The CL\_IPv4\_ESTABLISH.request primitive is passed from the IPv4 layer to the IPV4 SSCS. It is used when the IPv4 layer brings the interface up. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_ESTABLISH.request{}* + +On receiving this primitive, the IPV4 SSCS will form the address resolution connection to the base node and join the broadcast group used for receiving/transmitting broadcast packets. + +##### 9.4.8.2.3 CL\_IPv4\_ESTABLISH.confirm + +The CL\_IPv4\_ESTABLISH.confirm primitive is passed from the IPV4 SSCS to the IPv4 layer. It is used to indicate that the IPv4 SSCS is ready to access IPv4 packets to be sent to peers. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_ESTABLISH.confirm{}* + +Once the IPv4 SSCS has established all the necessary connections and is ready to transmit and receive IPv4 packets, this primitive is passed to the IPv4 layer. If the IPV4 SSCS encounters an error while opening, it responds with a CL\_IPv4\_RELEASE.confirm primitive, rather than a CL\_IPv4\_ESTABLISH.confirm. + +##### 9.4.8.2.4 CL\_IPv4\_RELEASE.request + +The CL\_IPv4\_RELEASE.request primitive is used by the IPv4 layer when the interface is put down. The IPV4 SSCS closes all connections so that no more IPv4 packets are received and all resources are released. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_RELEASE.request{}* + +Once the IPV4 SSCS has released all its connections and resources it returns a CL\_IPv4\_RELEASE.confirm. + +##### 9.4.8.2.5 CL\_IPv4\_RELEASE.confirm + +The CL\_IPv4\_RELEASE.confirm primitive is used by the IPv4 SSCS to indicate to the IPv4 layer that the IPv4 SSCS has been closed. This can be as a result of a CL\_IPv4\_RELEASE.request primitive, a CL\_IPv4\_ESTABLISH.request primitive, or because the MAC layer indicates the address resolution connection has been lost, or the service node itself is no longer registered. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_RELEASE.confirm{Result}* + +The result parameter has the meanings defined in Table C.3. + +#### 9.4.8.3 Unicast address management + +##### 9.4.8.3.1 General + +The primitives defined here are used for address management, i.e., the registration and unregistration of IPv4 addresses associated with this IPv4 SSCS. + +When there are no IPv4 addresses associated with the IPv4 SSCS, the IPv4 SSCS will only send and receive broadcast and multicast packets; unicast packets may not be sent. However, this is sufficient for BOOTP/DHCP operation to allow the device to gain an IPv4 address. Once an IPv4 address has been registered, the IPv4 layer can transmit unicast packets that have a source address equal to one of its registered addresses. + +##### 9.4.8.3.2 CL\_IPv4\_REGISTER.request + +This primitive is passed from the IPv4 layer to the IPv4 SSCS to register an IPv4 address. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_REGISTER.request{IPv4, netmask, gateway}* + +The IPv4 address is the address to be registered. + +The netmask is the network mask, used to mask the network number from the address. The netmask is used by the IPv4 SSCS to determine whether the packet should be delivered directly or the gateway should be used. + +The gateway is an IPv4 address of the gateway to be used for packets with the IPv4 local address but the destination address is not in the same subnetwork as the local address. + +Once the IPv4 address has been registered to the base node, a CL\_IPv4\_REGISTER.confirm primitive is used. If the registration fails, the CL\_IPv4\_RELEASE.confirm primitive will be used. + +##### 9.4.8.3.3 CL\_IPv4\_REGISTER.confirm + +This primitive is passed from the IPv4 SSCS to the IPv4 layer to indicate that a registration has been successful. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_REGISTER.confirm{IPv4}* + +The IPv4 address is the address that was registered. + +Once registration has been completed, the IPv4 layer may send IPv4 packets using this source address. + +##### 9.4.8.3.4 CL\_IPv4\_UNREGISTER.request + +This primitive is passed from the IPv4 layer to the IPv4 SSCS to unregister an IPv4 address. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_UNREGISTER.request{IPv4}* + +The IPv4 address is the address to be unregistered. + +Once the IPv4 address has been unregistered to the base node, a CL\_IPv4\_UNREGISTER.confirm primitive is used. If the unregistration fails, the CL\_IPv4\_RELEASE.confirm primitive will be used. + +##### 9.4.8.3.5 CL\_IPv4\_UNREGISTER.confirm + +This primitive is passed from the IPv4 SSCS to the IPv4 layer to indicate that an unregistration has been successful. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_UNREGISTER.confirm{IPv4}* + +The IPv4 address is the address that was unregistered. + +Once unregistration has been completed, the IPv4 layer may not send IPv4 packets using this source address. + +#### 9.4.8.4 Multicast group management + +##### 9.4.8.4.1 General + +This clause describes the primitives used to manage multicast groups. + +##### 9.4.8.4.2 CL\_IPv4\_IGMP\_JOIN.request + +This primitive is passed from the IPv4 layer to the IPv4 SSCS. It contains an IPv4 multicast address that is to be joined. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_IGMP\_JOIN.request{IPv4 }* + +The IPv4 address is the IPv4 multicast group that is to be joined. + +When the IPv4 SSCS receives this primitive, it will arrange for IPv4 packets sent to this group to be multicast in the ITU-T G.9904 network and receive packets using this address to be passed to the IPv4 stack. If the IPv4 SSCS cannot join the group, it uses the CL\_IPv4\_IGMP\_LEAVE.confirm primitive. Otherwise the CL\_IPv4\_IGMP\_JOIN.confirm primitive is used to indicate success. + +##### 9.4.8.4.3 CL\_IPv4\_IGMP\_JOIN.confirm + +This primitive is passed from the IPv4 SSCS to the IPv4. It contains a result status and an IPv4 multicast address that was joined. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_IGMP\_JOIN.confirm{IPv4}* + +The IPv4 address is the IPv4 multicast group that was joined. The IPv4 SSCS will start forwarding IPv4 multicast packets for the given multicast group. + +##### 9.4.8.4.4 CL\_IPv4\_IGMP\_LEAVE.request + +This primitive is passed from the IPv4 layer to the IPv4 SSCS. It contains an IPv4 multicast address to be left. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_IGMP\_LEAVE.request{IPv4}* + +The IPv4 address is the IPv4 multicast group to be left. The IPv4 SSCS will stop forwarding IPv4 multicast packets for this group and may leave the ITU-T G.9904 MAC multicast group. + +##### 9.4.8.4.5 CL\_IPv4\_IGMP\_LEAVE.confirm + +This primitive is passed from the IPv4 SSCS to the IPv4. It contains a result status and an IPv4 multicast address that was left. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_IGMP\_LEAVE.confirm{IPv4, Result}* + +The IPv4 address is the IPv4 multicast group that was left. The IPv4 SSCS will stop forwarding IPv4 multicast packets for the given multicast group. + +The result takes a value from Table C.3. + +This primitive can be used by the IPv4 SSCS as a result of a CL\_IPv4\_IGMP\_JOIN.request, CL\_IPv4\_IGMP\_LEAVE.request or because of an error condition resulting in the loss of the ITU-T G.9904 MAC multicast connection. + +#### **9.4.8.5 Data transfer** + +##### **9.4.8.5.1 General** + +The following primitives are used to send and receive IPv4 packets. + +##### **9.4.8.5.2 CL\_IPv4\_DATA.request** + +This primitive is passed from the IPv4 layer to the IPv4 SSCS. It contains one IPv4 packet to be sent. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_DATA.request{IPv4\_PDU}* + +The IPv4\_PDU is the IPv4 packet to be sent. + +##### **9.4.8.5.3 CL\_IPv4\_DATA.confirm** + +This primitive is passed from the IPv4 SSCS to the IPv4 layer. It contains a status indication and an IPv4 packet that has just been sent. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_DATA.confirm{IPv4\_PDU, Result}* + +The IPv4\_PDU is the IPv4 packet that was to be sent. + +The result value indicates whether the packet was sent or an error occurred. It takes a value from Table C.3. + +##### **9.4.8.5.4 CL\_IPv4\_DATA.indicate** + +This primitive is passed from the IPv4 SSCS to the IPv4 layer. It contains an IPv4 packet that has just been received. + +The semantics of this primitive are as follows: + +*CL\_IPv4\_DATA.indicate{IPv4\_PDU}* + +The IPv4\_PDU is the IPv4 packet that was received. + +## **9.5 IEC 61334-4-32 specific service convergence sublayer (IEC 61334-4-32 SSCS)** + +### **9.5.1 General** + +For all the service required, the IEC 61334-4-32 SSCS supports the DL\_DATA primitives as defined in the IEC 61334-4-32 standard. IEC 61334-4-32 should be read at the same time as this clause, which is not standalone text. + +### 9.5.2 Overview + +The IEC 61334-4-32 SSCS provides convergence functions for applications that use IEC 61334-4-32 services. Implementations conforming to this SSCS shall offer all LLC basic and management services as specified in [IEC 61334-4-32], clauses 2.2.1 and 2.2.3. Additionally, the IEC 61334-4-32 SSCS specified in this clause provides extra services that help mapping this connection-less IEC 61334-4-32 LLC protocol to the connection-oriented nature of the MAC. + +- A service node can only exchange data with the base node and not with other service nodes. This meets all the requirements of [IEC 61334-4-32], which has similar restrictions. +- Each IEC 61334-4-32 SSCS session establishes a dedicated ITU-T G.9904 MAC connection for exchanging unicast data with the base node. +- The service node SSCS session is responsible for initiating this connection to the base node. The base node SSCS cannot initiate a connection to a service node. +- Each IEC 61334-4-32 SSCS listens to an ITU-T G.9904 broadcast MAC connection dedicated to the transfer of IEC 61334-4-32 broadcast data from the base node to the service nodes. This broadcast connection is used when applications in the base node using IEC 61334-4-32 services make a transmission request with the Destination\_address used for broadcast or the broadcast SAP functions are used. When there are multiple SSCS sessions within a service node, one ITU-T G.9904 broadcast MAC connection is shared by all the SSCS sessions. +- A CPCS session is always present with an IEC 61334-4-32 SSCS session. The SPCS sublayer functionality is as specified in clause 9.2.2. Thus, the MSDUs generated by IEC 61334-4-32 SSCS are always less than CIMTUSize bytes and application messages shall not be longer than CIMaxAppPktSize. + +### 9.5.3 Address allocation and connection establishment + +Each 4-32 connection will be identified with the "Application unique identifier" that will be communicating through this 4-32 connection. It is the scope of the communication profile based on these lower layers to define the nature and rules for, this unique identifier. As long as the specification of the 4-32 convergence layer concerns this identifier, it will be called the "Device Identifier". + +The protocol stack as defined in IEC 61334 defines a destination address to identify each device in the network. This destination address is specified beyond the scope of the IEC 61334-4-32 document. However, it is used by the document. So that ITU-T G.9904 devices can make use of the 4-32 layer, this destination address is also required and is specified here. For more information about this destination address, please see [IEC 61334-4-1] clause 4.3, MAC addresses. + +The destination address has a scope of one ITU-T G.9904 subnetwork. The base node 4-32 SSCP layer is responsible for allocating these addresses dynamically and associating the device identifier of the service nodes SSCP session device with the allocated destination address, according to the IEC 61334-4-1 standard. The procedure is as follows: + +When the service node IEC 61334-4-32 SSCS session is opened by the application layer, it passes the device identifier of the device. The IEC 61334-4-32 SSCS session then establishes its unicast connection to the base node. This unicast connection uses the ITU-T G.9904 MAC TYPE value TYPE\_CL\_432, as defined in Table C.1. The connection request packet sent from the service node to the base node contains a data parameter. This data parameter contains the device identifier. The format of this data is specified in clause 9.5.4.2. + +On receiving this connection request at the base node, the base node allocates a unique subnetwork destination address to the service nodes SSCS session. The base node sends back an ITU-T G.9904 MAC connection response packet that contains a data parameter. This data parameter contains the allocated destination address and the address being used by the base node itself. The format of this + +data parameter is defined in clause 9.5.4.2. A 4-32 CL SAP primitive is used in the base node to indicate this new service node SSCS session mapping of the device identifier and Destination\_address to the 4-32 application running in the base node. + +On receiving the connection establishment and the Destination\_address passed in the ITU-T G.9904 MAC connection establishment packet, the 4-32 SSCS session confirms to the application that the convergence layer session has been opened and indicates the Destination\_address allocated to the service node SSCS session and the address of the base node. The service node also opens an ITU-T G.9904 MAC broadcast connection with the LCID equal to LCI\_CL\_432\_BROADCAST, as defined in Table C.2, if no other SSCS session has already opened such a broadcast connection. This connection is used to receive broadcast packets sent by the base node 4-32 convergence layer to all service node 4-32 convergence layer sessions. + +If the base node has allocated all its available Destination\_addresses, due to the exhaustion of the address space or implementation limits, it should simply reject the connection request from the service node. The service node may try to establish the connection again. However, to avoid overloading the ITU-T G.9904 subnetwork with such requests, it should limit such connection establishments to one attempt per minute when the base node rejects a connection establishment. + +When the unicast connection between a service node and the base node is closed (e.g., because the convergence layer on the service node is closed or the ITU-T G.9904 MAC level connection between the service node and the base node is lost), the base node will de-allocate the Destination\_address allocated to the service node SSCS session. The base node will use a 4-32 CL SAP (CL\_432\_Leave.indication) primitive to indicate the de-allocation of the Destination\_address to the 4-32 application running on the base node. + +### 9.5.4 Connection establishment data format + +#### 9.5.4.1 General + +As described in clause 9.5.3, the MAC ITU-T G.9904 connection data is used to transfer the device identifier to the base node and the allocated Destination\_address to the service node SSCS session. This clause describes the format used for this data. + +#### 9.5.4.2 Service node to base node + +The service node session passes the device identifier to the base node as part of the connection establishment request. The format of this message is shown in Table 9-20. + +**Table 9-20 – Connection signalling data sent by the service node** + +| Name | Length | Description | +|---------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Data.SN | n-Octets | Device identifier
"COSEM logical device name" of the "Management logical device" of the DLMS/COSEM device as specified in the DLMS/COSEM, which will be communicating through this 4-32 connection. | + +#### 9.5.4.3 Base node to service node + +The base node passes the allocated Destination\_address to the service node session as part of the connection establishment request. It also gives its own address to the service node. The format of this message is shown in Table 9-21. + +**Table 9-21 – Connection signalling data sent by the base node** + +| Name | Length | Description | +|-----------------|---------|-------------------------------------------------------------------------------------| +| Reserved | 4-bits | Reserved by ITU-T. Should be encoded as zero in this version of the Recommendation. | +| Data.DA | 12-bits | Destination_address allocated to the service node | +| Reserved | 4-bits | Reserved by ITU-T. Should be encoded as zero in this version of the Recommendation. | +| Data.BA | 12-bits | Base_address used by the base node | + +### **9.5.5 Packet format** + +The packet formats are used as defined in [IEC 61334-4-32], clause 4, LLC protocol data unit structure (LLC\_PDU). + +### **9.5.6 Service access point** + +#### **9.5.6.1 Opening and closing the convergence layer at the service node** + +##### **9.5.6.1.1 CL\_432\_ESTABLISH.request** + +This primitive is passed from the application to the 4-32 convergence layer. It is used to open a convergence layer session and initiate the process of registering the device identifier with the base node and the base node allocating a Destination\_address to the service node session. + +The semantics of this primitive are as follows: + +*CL\_432\_ESTABLISH.request{ DeviceIdentifier }* + +The device identifier is that of the device to be registered with the base node. + +If the device identifier is registered and the convergence layer session is successfully opened, the primitive CL\_432\_ESTABLISH.confirm is used. If an error occurs the primitive CL\_432\_RELEASE.confirm is used. + +##### **9.5.6.1.2 CL\_432\_ESTABLISH.confirm** + +This primitive is passed from the 4-32 convergence layer to the application. It is used to confirm the successful opening of the convergence layer session and that data may now be passed over the convergence layer. + +The semantics of this primitive are as follows: + +*CL\_432\_ESTABLISH.confirm{ DeviceIdentifier, Destination\_address, Base\_address }* + +The device identifier is used to identify which CL\_432\_ESTABLISH.request this CL\_432\_ESTABLISH.confirm is for. + +The Destination\_address is the address allocated to the service node 4-32 session by the base node. + +The Base\_address is the address being used by the base node. + +##### **9.5.6.1.3 CL\_432\_RELEASE.request** + +This primitive is passed from the application to the 4-32 convergence layer. It is used to close the convergence layer and release any resources it may be holding. + +The semantics of this primitive are as follows: + +*CL\_432\_RELEASE.request{Destination\_address}* + +The Destination\_address is the address allocated to the service node 4-32 session which is to be closed. + +The convergence layer will use the primitive CL\_432\_RELEASE.confirm when the convergence layer session has been closed. + +##### 9.5.6.1.4 CL\_432\_RELEASE.confirm + +This primitive is passed from the 4-32 convergence layer to the application. The primitive tells the application that the convergence layer session has been closed. This could be because of a CL\_432\_RELEASE.request or because an error has occurred, forcing the closure of the convergence layer session. + +The semantics of this primitive are as follows: + +*CL\_432\_RELEASE.confirm{Destination\_address, Result}* + +The handle identifies the session which has been closed. + +The result parameter has the meanings defined in Table C.3. + +#### 9.5.6.2 Opening and closing the convergence layer at the base node + +No service access point primitives are defined at the base node for opening or closing the convergence layer. None are required since the 4-32 application in the base node does not need to pass any information to the 4-32 convergence layer in the base node. + +#### 9.5.6.3 Base node indications + +##### 9.5.6.3.1 General + +The following primitives are used in the base node 4-32 convergence layer to indicate events to the 4-32 application in the base node. They indicate when a service node session has joined or left the network. + +##### 9.5.6.3.2 CL\_432\_JOIN.indicate + +*CL\_432\_JOIN.indicate{Device Identifier, Destination\_address}* + +The device identifier is that of the device connected to the service node that has just joined the network. + +The Destination\_address is the address allocated to the service node by the base node. + +##### 9.5.6.3.3 CL\_432\_LEAVE.indicate + +*CL\_432\_LEAVE.indicate{Destination\_address}* + +The Destination\_address is the address of the service node session that has just left the network. + +#### 9.5.6.4 Data transfer primitives + +The data transfer primitives are used as defined in [IEC 61334-4-32], clauses 2.2, 2.3, 2.4 and 2.11, LLC service specification. As stated earlier, ITU-T G.9904 SSCS make the use of IEC 61334-4-32 DL\_Data service (.req, .conf, .ind) for carrying out all the data involved during data transfer. + +## 9.6 IPv6 service-specific convergence sublayer (IPv6 SSCS) + +### 9.6.1 Overview + +#### 9.6.1.1 General + +The IPv6 convergence layer provides an efficient method for transferring IPv6 packets over the ITU-T G.9904 network. + +A service node can pass IPv6 packets to the base node or directly to other service nodes. + +By default, the base node acts as a router between the ITU-T G.9904 subnetwork and the backbone network. All the base nodes must have at least this connectivity capability. Any other node inside the subnetwork can also act as a gateway. The base node could also act as an NAT router. However given the abundance of IPv6 addresses this is not expected. How the base node connects to the backbone is beyond the scope of this standard. + +#### **9.6.1.2 IPv6 unicast addressing assignment** + +- IPv6 service nodes (and base nodes) shall support the standard IPv6 protocol, as described in [IETF RFC 2460]. +- IPv6 service nodes (and base nodes) shall support the standard IPv6 addressing architecture, as described in [IETF RFC 4291]. +- IPv6 service nodes (and base nodes) shall support global unicast IPv6 addresses, link-local IPv6 addresses and multicast IPv6 addresses, as described in [IETF RFC 4291]. +- IPv6 service nodes (and base nodes) shall support automatic address configuration using stateless address configuration [IETF RFC 2462]. They may also support automatic address configuration using stateful address configuration [IETF RFC 3315] and they may support manual configuration of IPv6 addresses. The decision for which address configuration scheme to use is deployment specific. +- The service node shall support DHCPv6 client, when base nodes have to support a DHCPv6 server as described in [IETF RFC 3315] for stateless address configuration. + +#### **9.6.1.3 Address management in ITU-T G.9904 subnetworks** + +Packets are routed in ITU-T G.9904 subnetworks according to the node identifier NID. The node identifier is a combination of a service node's LNID and SID (see clause 8.2). The base node is responsible for assigning the LNID to service nodes. During the registration process which leads to LNID assignment to the related service node, the base node registers the service node EUI-48, and the assigned LNID together with the SID. + +At the convergence layer level, addressing is performed using the EUI-48 of the related service node. The role of the convergence sublayer is to resolve the IPv6 address into EUI-48 of the service node. This is done using the address resolution service set of the base node. + +#### **9.6.1.4 Role of the base node** + +At the convergence sublayer level, the base node maintains a table containing all the IPv6 unicast addresses and the EUI-48 related to them. One of the roles of the base node is to perform IPv6 to EUI-48 address resolution. Each service node belonging to the subnetwork managed by the base node registers its IPv6 address and EUI-48 address with the base node. Other service nodes can then query the base node to resolve an IPv6 address into an EUI-48 address. This requires the establishment of a dedicated connection to the base node for address resolution, which is shared by both IPv4 and IPv6 address resolution. + +Optionally UDP/IPv6 headers may be compressed. Compression is negotiated as part of the connection establishment phase. Currently, there is one header compression technique described in the present Recommendation that is used for the transmission of IPv6 packets over IEEE 802.15.4 networks, as defined in [SP 800-57]. This is also known as LOWPAN\_IPHC1. + +The multicasting of IPv6 packets is supported using the MAC multicast mechanism. + +### 9.6.2 IPv6 convergence layer + +#### 9.6.2.1 Overview + +##### 9.6.2.1.1 General + +The convergence layer has a number of connection types. For address resolution there is a connection to the base node. For IPv6 data transfer there is one connection per destination node: the base node that acts as the IPv6 gateway to the outside world or another node in the same subnetwork. This is shown in Figure 9-4. + +![Diagram illustrating IPv6 connections between a base node and various service nodes (Switches and Terminals).](a83c022a6dac411615bcc38b7cd0d573_img.jpg) + +The diagram shows a hierarchical network structure. At the top is node A, labeled 'Base node S=(0, 0)'. Below it are two rows of nodes. The first row contains node B ('Switch'), node C ('Terminal'), node D ('Switch'), and node E ('Terminal'). The second row contains node F ('Terminal'), node G ('Terminal'), and node H ('Terminal'). Node F is connected to node B. Node G is connected to node F. Node H is connected to node D. Node E is connected to node D. Solid lines represent 'Address resolution connection' and dashed lines represent 'IPv6 data connection'. Node A has solid lines to nodes B, C, and D, and a dashed line to node E. Node B has a solid line to node F and a dashed line to node E. Node D has a dashed line to node E and a dashed line to node H. Node F has a dashed line to node G. Node G has a dashed line to node H. A legend at the bottom left identifies the line types. The text 'G.9904(12)\_F9-4' is in the bottom right. + +Diagram illustrating IPv6 connections between a base node and various service nodes (Switches and Terminals). + +**Figure 9-4 – Example of IPv6 connection** + +Here, nodes B, E and F have address resolution connections to the base node. Node E has a data connection to the base node and node F. Node F also has a data connection to node B. The figure does not show broadcast-traffic and multicast-traffic connections. + +##### 9.6.2.1.2 Routing in the subnetwork + +Routing IPv6 packets is the scope of the convergence layer. In other words, the convergence layer will decide whether the packet should be sent directly to another service node or forwarded to the configured gateway depending on the IPv6 destination address. + +Although IPv6 is a connectionless protocol, the IPv6 convergence layer is connection-oriented. Once address resolution has been performed, a connection is established between the source and destination service nodes for the transfer of IP packets. This connection is maintained all the time that the traffic is being transferred and may be removed after a period of inactivity. + +##### 9.6.2.1.3 SAR + +The CPCS sublayer shall always be present with the IPv6 convergence layer allowing segmentation and reassembly facilities. The SAR sublayer functionality is given in clause 9.2. Thus, the MSDUs generated by the IPv6 convergence layer are always less than CIMTUSize bytes and application messages are expected to be no longer than CIMaxAppPktSize. + +### 9.6.3 IPv6 address configuration + +#### 9.6.3.1 Overview + +The service nodes may use statically configured IPv6 addresses, link local addresses, stateless or stateful auto-configuration according to [IETF RFC 2462], or DHCPv6 to obtain IPv6 addresses. All the nodes shall support the unicast link local address, in addition to other configured addresses below, and multicast addresses, if ever the node belongs to multicast groups. + +#### **9.6.3.2 Interface identifier** + +In order to make use of stateless address auto configuration and link local addresses it is necessary to define how the interface identifier, as defined in [IETF RFC 4291], is derived. Each ITU-T G.9904 node has a unique EUI-48. This EUI-48 is converted into an EUI-64 in the same way as for Ethernet networks as defined in [IETF RFC 2464]. This EUI-64 is then used as the interface identifier. + +#### **9.6.3.3 IPv6 link local address configuration** + +The IPv6 link local address of an ITU-T G.9904 interface is formed by appending the interface identifier as defined above to the prefix FE80::/64. + +#### **9.6.3.4 Stateless address configuration** + +An IPv6 address prefix used for stateless auto configuration, as defined in [IETF RFC4862], of an ITU-T G.9904 interface shall have a length of 64 bits. The IPv6 prefix is obtained by the service nodes from the base node via router advertisement messages, which are sent periodically or on request by the base node. + +#### **9.6.3.5 Stateful address configuration** + +An IPv6 address can be alternatively configured using DHCPv6, as described in [IETF RFC 3315]. DHCPv6 can provide a device with addresses assigned by a DHCPv6 server and other configuration information, which are carried in options. + +#### **9.6.3.6 Multicast address** + +IPv6 service nodes (and base nodes) shall support the multicast IPv6 addressing, as described in [IETF RFC 4291], clause 2.7. + +#### **9.6.3.7 Address resolution** + +##### **9.6.3.7.1 Overview** + +The IPv6 layer will present the convergence layer with an IPv6 packet to be transferred. The convergence layer is responsible for determining which service node the packet should be delivered to, using the IPv6 addresses in the packet. The convergence layer shall then establish a connection to the destination if one does not already exist so that the packet can be transferred. Two classes of IPv6 addresses can be used and the following clause describes how these addresses are resolved into G.9904 EUI-48 addresses. It should be noted that IPv6 does not have a broadcast address. However broadcasting is possible using multicast all nodes addresses. + +##### **9.6.3.7.2 Unicast address** + +###### **9.6.3.7.2.1 General** + +IPv6 unicast addresses shall be resolved into ITU-T G.9904 unicast EUI-48 addresses. The base node maintains a central database node of IPv6 addresses and EUI-48 addresses. Address resolution functions are performed by querying this database. The service node shall establish a connection to the address resolution service running on the base node, using the TYPE value TYPE\_CL\_IPv6\_AR. No data should be passed in the connection establishment signalling. Using this connection, the service node can use two mechanisms as defined in the present Recommendation. + +###### **9.6.3.7.2.2 Address registration and deregistration** + +A service node uses the AR\_REGISTERv6\_S message to register an IPv6 address and the corresponding EUI-48 address. The base node will acknowledge an AR\_REGISTERv6\_B message. The service node may register multiple IPv6 addresses for the same EUI-48. + +A service node uses the AR\_UNREGISTERv6\_S message to unregister an IPv6 address and the corresponding EUI-48 address. The base node will acknowledge an AR\_UNREGISTERv6\_B message. + +When the address resolution connection between the service node and the base node is closed, the base node should remove all addresses associated with that connection. + +###### 9.6.3.7.2.3 Address look-up + +A service node uses the AR\_LOOKUPv6\_S message to perform a look-up. The message contains the IPv6 address to be resolved. The base node will respond with an AR\_LOOKUPv6\_B message that contains an error code and, if there is no error, the EUI-48 associated with the IPv6 address. If the base node has multiple entries in its database node for the same IPv6 address, the possible EUI-48 returned is undefined. + +It should be noted that, for the link local addresses, due to the fact that the EUI-48 can be obtained from the IPv6 address, the look-up can simply return this value by extracting it from the IPv6 address. + +##### 9.6.3.7.3 Multicast address + +Multicast IPv6 addresses are mapped to connection handles (ConnHandle) by the convergence layer. + +To join a multicast group, CL uses the MAC\_JOIN.request primitive with the IPv6 address specified in the data field. A corresponding MAC\_JOIN.confirm primitive will be generated by the MAC after completion of the join process. The MAC\_JOIN.confirm primitive will contain the result (success/failure) and the corresponding ConnHandle to be used by the CL. The MAC layer will handle the transfer of data for this connection using the appropriate LCIDs. To leave the multicast group, the CL at the service node shall use the MAC\_LEAVE.request{ConnHandle} primitive. + +To send an IPv6 multicast packet, the CL will simply send the packet to the group using the allocated ConnHandle. The ConnHandle is maintained while there are more packets to be sent. However, after Tmcast\_reg seconds of not sending an IPv6 multicast packet to the group, the node should release the ConnHandle by using the MAC\_LEAVE.request primitive. The nominal value of Tmcast\_reg is 10 minutes; however, other values may be used. + +##### 9.6.3.7.4 Retransmission of address resolution packets + +The connection between the service node and the base node for address resolution is not reliable. The MAC ARQ is not used. The service node is responsible for making retransmissions if the base node does not respond in one second. It is not considered an error when the base node receives the same registration requests multiple times or is asked to remove a registration that does not exist. These conditions can be the result of retransmissions. + +### 9.6.4 IPv6 packet transfer + +For packets to be transferred, a connection needs to be established between the source and destination nodes. The IPv6 convergence layer will examine each IP packet to determine the destination EUI-48 address. If a connection to the destination has already been established, the packet is simply sent. To establish this, the convergence layer keeps a table for each connection it has with the information shown in Table 9-22. To use this table, it is first necessary to determine if the remote address is in the local subnetwork or if a gateway has to be used. The netmask associated with the local IP address is used to determine this. If the destination address is not in the local subnetwork, the address of the gateway is used instead of the destination address when the table is searched. + +**Table 9-22 – IPv6 convergence layer table entry** + +| Parameter | Description | +|-----------------------|-----------------------------------------------| +| CL_IPv6_Con.Remote_IP | Remote IP address of this connection | +| CL_IPv6_Con.ConHandle | MAC connection handle for the connection | +| CL_IPv6_Con.LastUsed | Timestamp of last packet received/transmitted | +| CL_IPv6_Con.HC | Header compression scheme being used | + +The convergence layer may close a connection when it has not been used for an implementation-defined time period. When the connection is closed, the entry for the connection is removed at both ends of the connection. + +When a connection to the destination does not exist, more work is necessary. The address resolution service is used to determine the EUI-48 address of the remote IP address if it is local or the gateway associated with the local address if the destination address is in another subnetwork. When the base node replies with the EUI-48 address of the destination service node, a MAC connection is established to the remote device. The TYPE value of this connection is TYPE\_CL\_IPv6\_UNICAST. The data passed in the request message is defined in clause 9.6.8.3. The local IP address is provided so that the remote device can add the new connection to its cache of connections for sending data in the opposite direction. The use of header compression is also negotiated as part of the connection establishment. Once the connection has been established, the IP packet can be sent. + +### 9.6.5 Segmentation and reassembly + +The IPv6 convergence layer should support IPv6 packets with an MTU of 1500 bytes. This requires the use of the common part convergence sublayer segmentation and reassembly service. + +### 9.6.6 Compression + +It is assumed that any ITU-T G.9904 device is capable of LOWPAN\_IPHC IPv6 header compression/decompression. It may also be capable of performing UDP compression/decompression. Thus UDP/IPv6 compression is negotiated. + +No negotiation can take place for multicast packet. Nodes can only make use of mandatory compression capabilities. + +Depending of the type of IPv6 address carried by the packet and the capabilities which are negotiated between the nodes involved in the data exchanges, IPv6 header compression is performed. + +All the service nodes and the base node shall support IPv6 header compression using source and destination addresses stateless compression as defined in [SP 800-57]. Source and destination IPv6 addresses using stateful compression and IPv6 next header compression are negotiable. + +### 9.6.7 Quality of service mapping + +The ITU-T G.9904 MAC specifies that the contention-based access mechanism supports four priority levels (1-4). Level 1 is used for MAC signalling messages, but not exclusively so. + +IPv6 packets include a traffic class field in the header to indicate the QoS the packet would like to receive. This traffic class can be used in the same way as IPv4 TOS (see [IETF RFC 791]). That is, three bits of the TOS indicate the IP precedence. The following table specifies how the IP precedence is mapped into the ITU-T G.9904 MAC priority. + +**Table 9-23 – Mapping IPv6 precedence to ITU-T G.9904 MAC priority** + +| IP Precedence | MAC Priority | +|----------------------------|--------------| +| 000 – Routine | 4 | +| 001 – Priority | 4 | +| 010 – Immediate | 3 | +| 011 – Flash | 3 | +| 100 – Flash override | 2 | +| 101 – Critical | 2 | +| 110 – Internetwork control | 1 | +| 111 – Network control | 1 | + +NOTE – At the MAC layer level the priority as stated in the packet header field is the value assigned in this table minus 1, as the range of PKT.PRIO field is from 0 to 3. + +### 9.6.8 Packet formats and connection data + +#### 9.6.8.1 Overview + +This clause defines the format of convergence layer PDUs. + +#### 9.6.8.2 Address resolution PDU + +##### 9.6.8.2.1 General + +The following PDUs are transferred over the address resolution connection between the service node and the base node. The following clauses define a number of AR.MSG values. All other values are reserved for later versions of this standard. + +##### 9.6.8.2.2 AR\_REGISTERv6\_S + +Table 9-24 shows the address resolution register message sent from the service node to the base node. + +**Table 9-24 – AR\_REGISTERv6\_S message format** + +| Name | Length | Description | +|-----------|----------|---------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_REGISTERv6_S = 16 | +| AR.IPv6 | 128-bits | IPv6 address to be registered | +| AR.EUI-48 | 48-bits | EUI-48 to be registered | + +##### 9.6.8.2.3 AR\_REGISTERv6\_B + +Table 9-25 shows the address resolution register acknowledgment message sent from the base node to the service node. + +**Table 9-25 – AR\_REGISTERv6\_B message format** + +| Name | Length | Description | +|-----------|----------|---------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_REGISTERv6_B = 17 | +| AR.IPv6 | 128-bits | IPv6 address registered | +| AR.EUI-48 | 48-bits | EUI-48 registered | + +The AR.IPv6 and AR.EUI-48 fields are included in the AR\_REGISTERv6\_B message so that the service node can perform multiple overlapping registrations. + +##### 9.6.8.2.4 AR\_UNREGISTERv6\_S + +Table 9-26 shows the address resolution unregister message sent from the service node to the base node. + +**Table 9-26 – AR\_UNREGISTERv6\_S message format** + +| Name | Length | Description | +|-----------|----------|-----------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_UNREGISTERv6_S = 18 | +| AR.IPv6 | 128-bits | IPv6 address to be unregistered | +| AR.EUI-48 | 48-bits | EUI-48 to be unregistered | + +##### 9.6.8.2.5 AR\_UNREGISTERv6\_B + +Table 9-27 shows the address resolution unregister acknowledgment message sent from the base node to the service node. + +**Table 9-27 – AR\_UNREGISTERv6\_B message format** + +| Name | Length | Description | +|-----------|----------|-----------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_UNREGISTERv6_B = 19 | +| AR.IPv6 | 128-bits | IPv6 address unregistered | +| AR.EUI-48 | 48-bits | EUI-48 unregistered | + +The AR.IPv6 and AR.EUI-48 fields are included in the AR\_UNREGISTERv6\_B message so that the service node can perform multiple overlapping unregistrations. + +##### 9.6.8.2.6 AR\_LOOKUPv6\_S + +Table 9-28 shows the address resolution look-up message sent from the service node to the base node. + +**Table 9-28 – AR\_LOOKUPv6\_S message format** + +| Name | Length | Description | +|---------|----------|-------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
• For AR_LOOKUPv6_S = 20 | +| AR.IPv6 | 128-bits | IPv6 address to look up | + +##### 9.6.8.2.7 AR\_LOOKUPv6\_B + +Table 9-29 shows the address resolution look-up response message sent from the base node to the service node. + +**Table 9-29 – AR\_LOOKUPv6\_B message format** + +| Name | Length | Description | +|-----------|----------|---------------------------------------------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_LOOKUPv6_B = 21
| +| AR.IPv6 | 128-bits | IPv6 address looked up | +| AR.EUI-48 | 48-bits | EUI-48 for IPv6 address | +| AR.Status | 8-bits | Look-up status, indicating if the address was found or an error occurred.
0 = found, AR.EUI-48 valid
1 = unknown, AR.EUI-48 undefined | + +The look-up may fail if the requested address has not been registered. In this case, AR.Status will have a value equal to 1, and the contents of AR.EUI-48 will be undefined. The look-up is only successful when AR.Status is zero. In that case, the EUI-48 field contains the resolved address. + +##### 9.6.8.2.8 AR\_MCAST\_REGv6\_S + +Table 9-30 shows the multicast address resolution register message sent from the service node to the base node. + +**Table 9-30 – AR\_MCAST\_REGv6\_S message format** + +| Name | Length | Description | +|---------|----------|-----------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_MCAST_REGv6_S = 24
| +| AR.IPv6 | 128-bits | IPv6 multicast address to be registered | + +##### 9.6.8.2.9 AR\_MCAST\_REGv6\_B + +Table 9-31 shows the multicast address resolution register acknowledgment message sent from the base node to the service node. + +**Table 9-31 – AR\_MCAST\_REGv6\_B message format** + +| Name | Length | Description | +|-----------------|----------|-----------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • For AR_MCAST_REGv6_B = 25
| +| AR.IPv6 | 128-bits | IPv6 multicast address registered | +| Reserved | 2-bits | Reserved by ITU-T. Should be encoded as 0 | +| AR.LCID | 6-bits | LCID assigned to this IPv6 multicast address | + +The AR.IPv6 field is included in the AR\_MCAST\_REGv6\_B message so that the service node can perform multiple overlapping registrations. + +##### 9.6.8.2.10 AR\_MCAST\_UNREGv6\_S + +Table 9-32 shows the multicast address resolution unregister messages sent from the service node to the base node. + +**Table 9-32 – AR\_MCAST\_UNREGv6\_S message format** + +| Name | Length | Description | +|---------|----------|---------------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • • For AR_MCAST_UNREGv6_S = 26
| +| AR.IPv6 | 128-bits | IPv6 multicast address to be unregistered | + +##### 9.6.8.2.11 AR\_MCAST\_UNREGv6\_B + +Table 9-33 shows the multicast address resolution unregister acknowledgment message sent from the base node to the service node. + +**Table 9-33 – AR\_MCAST\_UNREGv6\_B message format** + +| Name | Length | Description | +|---------|----------|---------------------------------------------------------------------------------------------------------------| +| AR.MSG | 8-bits | Address resolution message type
  • • For AR_MCAST_UNREGv6_B = 27
| +| AR.IPv6 | 128-bits | IPv6 multicast address unregistered | + +The AR.IPv6 field is included in the AR\_MCAST\_UNREGv6\_B message so that the service node can perform multiple overlapping unregistrations. + +#### 9.6.8.3 IPv6 packet format + +##### 9.6.8.3.1 General + +The following PDU formats are used for transferring IPv6 packets between service nodes. + +##### 9.6.8.3.2 No negotiated header compression + +When no header compression takes place, the IP packet is simply sent as it is, without any header. + +**Table 9-34 – IPv6 packet format without negotiated header compression** + +| Name | Length | Description | +|----------|----------|-----------------| +| IPv6.PKT | n-octets | The IPv6 packet | + +##### 9.6.8.3.3 Header compression + +When LOWPAN\_IPHC1 header compression takes place, and the next header compression is negotiated, the UDP/IPv6 packet is sent as shown in Table 9-35. + +**Table 9-35 – UDP/IPv6 packet format with LOWPAN\_IPHC1 header compression and LOWPAN\_NHC** + +| Name | Length | Description | +|------------------|------------|---------------------------------------------------------------------------------------------------------------| +| IPv6.IPHC | 2-octet | Dispatch + LOWPAN_IPHC encoding. With bit 5=1 indicating that the next is compressed, using LOWPAN_NHC format | +| IPv6.ncIPv6 | n.m-octets | Non-compressed IPv6 fields (or elided) | +| IPv6.HC_UDP | 1-octet | Next header encoding | +| IPv6.ncUDP | n.m-octets | Non-compressed UDP fields | +| Padding | 0.m-octets | Padding to byte boundary | +| IPv6.DATA | n-octets | UDP data | + +Note that these fields are not necessarily aligned to byte boundaries. For example the IPv6.ncIPv6 field can be any number of bits. The IPv6.IPHC\_UDP field follows directly afterwards, without any padding. Padding is only applied at the end of the complete compressed UDP/IPv6 header so that the UDP data is byte aligned. + +When the IPv6 packet contains data other than UDP the following packet format is used as shown in Table 9-36. + +**Table 9-36 – IPv6 packet format with LOWPAN\_IPHC negotiated header compression** + +| Name | Length | Description | +|------------------|------------|----------------------------------------------------------------------------------| +| IPv6.IPHC | 2-octet | HC encoding. Bits 5 contain 0 indicating the next header byte is not compressed. | +| IPv6.ncIPv6 | n.m-octets | Non-compressed IPv6 fields | +| Padding | 0.m-octets | Padding to byte boundary | +| IPv6.DATA | n-octets | IP data | + +#### 9.6.8.4 Connection data + +##### 9.6.8.4.1 Overview + +When a connection is established between service nodes for the transfer of IP packets, data is also transferred in the connection request packets. This data allows the negotiation of compression and notification of the IP address. + +##### 9.6.8.4.2 Connection data from the initiator + +Table 9-37 shows the connection data sent by the initiator. + +**Table 9-37 – IPv6 connection signalling data sent by the initiator** + +| Name | Length | Description | +|-----------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 6-bits | Reserved by ITU-T. Should be encoded as zero in this version of the convergence layer protocol | +| Data.HCNH | 2-bit | Header compression negotiated
  • Data.HC = 0 – No compression requested
  • Data.HC = 1 – LOWPAN_NH
  • Data.HC = 2 – stateful address compression
  • Data.HC = 3 – LOWPAN_NH and stateful address compression
| +| Data.IPv6 | 128-bits | IPv6 address of the initiator | + +If the device accepts the connection, it should copy the Data.IPv6 address into a new table entry along with the negotiated Data.HC value. + +##### 9.6.8.4.3 Connection data from the responder + +Table 9-38 shows the connection data sent in response to the connection request. + +**Table 9-38 – IPv6 connection signalling data sent by the responder** + +| Name | Length | Description | +|-----------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 6-bits | Reserved by ITU-T. Should be encoded as zero in this version of the convergence layer protocol | +| Data.HC | 2-bit | Header compression negotiated
  • Data.HC = 0 – No compression requested: NOTE – When stateless address compression is used, all nodes shall support it. When the stateless address compression is not used then the node notifies by this value, its compression capability.
  • Data.HC = 1 – LOWPAN_NH
  • Data.HC = 2 – stateful address compression
  • Data.HC = 3 – LOWPAN_NH and stateful address compression
| + +All nodes support stateless address compression. + +The next header compression scheme and stateful address compression can only be used when it is supported by both service nodes. The responder may only set Data.HC to the same value as that received from the initiator or a value lower than the one received. When the same value is used, it indicates that the requested compression scheme has been negotiated and will be used for the connection. Setting Data.HC to a lower value allows the responder to deny the request for that header compression scheme. + +### 9.6.9 Service access point + +#### 9.6.9.1 Overview + +This clause defines the service access point used by the IPv6 layer to communicate with the IPv6 convergence layer. + +#### 9.6.9.2 Opening and closing the convergence layer + +The following primitives are used to open and close the convergence layer. The convergence layer may be opened once only. The IPv6 layer may close the convergence layer when the IPv6 interface is brought down. The convergence layer will also close the convergence layer when the underlying MAC connection to the base node has been lost. + +##### 9.6.9.2.1 CL\_IPv6\_Establish.request + +The CL\_IPv6\_ESTABLISH.request primitive is passed from the IPv6 layer to the IPv6 convergence layer. It is used when the IPv6 layer brings the interface up. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_ESTABLISH.request{}* + +On receiving this primitive, the convergence layer will form the address resolution connection to the base node. + +##### 9.6.9.2.2 CL\_IPv6\_Establish.confirm + +The CL\_IPv6\_ESTABLISH.confirm primitive is passed from the IPv6 convergence layer to the IPv6 layer. It is used to indicate that the convergence layer is ready to access IPv6 packets to be sent to peers. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_ESTABLISH.confirm{}* + +Once the convergence layer has established all the necessary connections and is ready to transmit and receive IPv6 packets, this primitive is passed to the IPv6 layer. If the convergence layer encounters an error while opening, it responds with a CL\_IPv6\_RELEASE.confirm primitive, rather than a CL\_IPv6\_ESTABLISH.confirm. + +##### 9.6.9.2.3 CL\_IPv6\_Release.request + +The CL\_IPv6\_RELEASE.request primitive is used by the IPv6 layer when the interface is put down. The convergence layer closes all connections so that no more IPv6 packets are received and all resources are released. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_RELEASE.request{}* + +Once the convergence layer has released all its connections and resources it returns a CL\_IPv6\_RELEASE.confirm. + +##### 9.6.9.2.4 CL\_IPv6\_Release.confirm + +The CL\_IPv6\_RELEASE.confirm primitive is used by the IPv6 convergence layer to indicate to the IPv6 layer that the convergence layer has been closed. This can be as a result of a CL\_IPv6\_RELEASE.request primitive, a CL\_IPv6\_ESTABLISH.request primitive, or because the MAC layer indicates the address resolution connection has been lost, or the service node itself is no longer registered. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_RELEASE.confirm{Result}* + +The result parameter has the meanings defined in Table C.3. + +#### 9.6.9.3 Unicast address management + +##### 9.6.9.3.1 General + +The primitives defined here are used for address management, i.e., the registration and unregistration of IPv6 addresses associated with this convergence layer. + +When there are no IPv6 addresses associated with the convergence layer, the convergence layer will only send and receive multicast packets; unicast packets may not be sent. However, this is sufficient for various address discovery protocols to be used to gain an IPv6 address. Once an IPv6 address has been registered, the IPv6 layer can transmit unicast packets that have a source address equal to one of its registered addresses. + +##### 9.6.9.3.2 CL\_IPv6\_Register.request + +This primitive is passed from the IPv6 layer to the IPv6 convergence layer to register an IPv6 address. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_REGISTER.request{ipv6, netmask, gateway}* + +The IPv6 address is the address to be registered. + +The netmask is the network mask, used to mask the network number from the address. The netmask is used by the convergence layer to determine whether the packet should deliver directly or the gateway should be used. + +The IPv6 address of the gateway, to which packets with destination addresses that are not in the same subnetwork as the local address, are to be sent. + +Once the IPv6 address has been registered to the base node, a CL\_IPv6\_REGISTER.confirm primitive is used. If the registration fails, the CL\_IPv6\_RELEASE.confirm primitive will be used. + +##### 9.6.9.3.3 CL\_IPv6\_Register.confirm + +This primitive is passed from the IPv6 convergence layer to the IPv6 layer to indicate that a registration has been successful. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_REGISTER.confirm{ipv6}* + +The IPv6 address is the address that was registered. + +Once registration has been completed, the IPv6 layer may send IPv6 packets using this source address. + +##### 9.6.9.3.4 CL\_IPv6\_Unregister.request + +This primitive is passed from the IPv6 layer to the IPv6 convergence layer to unregister an IPv6 address. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_UNREGISTER.request{ipv6}* + +The IPv6 address is the address to be unregistered. + +Once the IPv6 address has been unregistered to the base node, a CL\_IPv6\_UNREGISTER.confirm primitive is used. If the registration fails, the CL\_IPv6\_RELEASE.confirm primitive will be used. + +##### 9.6.9.3.5 Unregister.confirm + +This primitive is passed from the IPv6 convergence layer to the IPv6 layer to indicate that unregistration has been successful. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_UNREGISTER.confirm{ipv6}* + +The IPv6 address is the address that was unregistered. + +Once unregistration has been completed, the IPv6 layer may not send IPv6 packets using this source address. + +#### **9.6.9.4 Multicast group management** + +##### **9.6.9.4.1 General** + +This clause describes the primitives used to manage multicast groups. + +##### **9.6.9.4.2 CL\_IPv6\_MUL\_Join.request** + +This primitive is passed from the IPv6 layer to the IPv6 convergence layer. It contains an IPv6 multicast address that is to be joined. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_MUL\_JOIN.request{IPv6 }* + +The IPv6 address is the IPv6 multicast group that is to be joined. + +When the convergence layer receives this primitive, it will arrange for IP packets sent to this group to be multicast in the ITU-T G.9904 network and receive packets using this address to be passed to the IPv6 stack. If the convergence layer cannot join the group, it uses the *CL\_IPv6\_MUL\_LEAVE.confirm* primitive. Otherwise the *CL\_IPv6\_MUL\_JOIN.confirm* primitive is used to indicate success. + +##### **9.6.9.4.3 CL\_IPv6\_MUL\_Join.confirm** + +This primitive is passed from the IPv6 convergence layer to the IPv6. It contains a result status and an IPv6 multicast address that was joined. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_MUL\_JOIN.confirm{IPv6}* + +The IPv6 address is the IPv6 multicast group that was joined. The convergence layer will start forwarding IPv6 multicast packets for the given multicast group. + +##### **9.6.9.4.4 CL\_IPv6\_MUL\_Leave.request** + +This primitive is passed from the IPv6 layer to the IPv6 convergence layer. It contains an IPv6 multicast address to be left. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_MUL\_LEAVE.request{IPv6}* + +The IPv6 address is the IPv6 multicast group to be left. The convergence layer will stop forwarding IPv6 multicast packets for this group and may leave the ITU-T G.9904 MAC multicast group. + +##### **9.6.9.4.5 CL\_IPv6\_MUL\_Leave.confirm** + +This primitive is passed from the IPv6 convergence layer to the IPv6. It contains a result status and an IPv6 multicast address that was left. + +The semantics of this primitive are as follows: + +*CL\_IPv6\_MUL\_LEAVE.confirm{IPv6, Result}* + +The IPv6 address is the IPv6 multicast group that was left. The convergence layer will stop forwarding IPv6 multicast packets for the given multicast group. + +The result takes a value from Table C.3. + +This primitive can be used by the convergence layer as a result of a CL\_IPv6\_MUL\_JOIN.request, CL\_IPv6\_MUL\_LEAVE.request or because of an error condition resulting in the loss of the ITU-T G.9904 MAC multicast connection. + +#### **9.6.9.5 Data transfer** + +##### **9.6.9.5.1 General** + +The following primitives are used to send and receive IPv6 packets. + +##### **9.6.9.5.2 CL\_IPv6\_DATA.request** + +This primitive is passed from the IPv6 layer to the IPv6 convergence layer. It contains one IPv6 packet to be sent. + +The semantics of this primitive are as follows: + +$$CL\_IPv6\_DATA.request\{IPv6\_PDU\}$$ + +The IPv6\_PDU is the IPv6 packet to be sent. + +##### **9.6.9.5.3 CL\_IPv6\_DATA.confirm** + +This primitive is passed from the IPv6 convergence layer to the IPv6 layer. It contains a status indication and an IPv6 packet that has just been sent. + +The semantics of this primitive are as follows: + +$$CL\_IPv6\_DATA.confirm\{IPv6\_PDU, Result\}$$ + +The IPv6\_PDU is the IPv6 packet that was to be sent. + +The result value indicates whether the packet was sent or an error occurred. It takes a value from Table C.3. + +##### **9.6.9.5.4 CL\_IPv6\_DATA.indicate** + +This primitive is passed from the IPv6 convergence layer to the IPv6 layer. It contains an IPv6 packet that has just been received. + +The semantics of this primitive are as follows: + +$$CL\_IPv6\_DATA.indicate\{IPv6\_PDU\}$$ + +The IPv6\_PDU is the IPv6 packet that was received. + +# **10 Management plane** + +## **10.1 Introduction** + +This clause specifies the management plane functionality. Figure 10-1 below highlights the position of the management plane in the overall protocol architecture. + +![Diagram of the Management plane structure showing layers from Applications down to PHY Layer, with a vertical Management Plane on the right side.](defe20e5056d0c3552de2d50ce88c5cb_img.jpg) + +The diagram illustrates the Management plane structure across five layers: + +- Applications:** Contains boxes labeled #1, #2, ..., and Firmware Upgrade. The Firmware Upgrade box has a double-headed arrow pointing to the Management Plane. +- Service Specific Convergence Sublayer (SSCS):** Contains boxes for IEC - 432 SSCS, IPv4 SSCS, IPv6 SSCS, NULL SSCS, and "New Protocol" SSCS. +- Common Part Convergence Sublayer (CPCS):** Contains a box for Segmentation and Reassembly (SAR). +- Convergence Layer:** The label for the layer containing the CPCS and SSCS sublayers. +- MAC Layer:** Contains a box for MAC PIB, which has a double-headed arrow pointing to the Management Plane. +- PHY Layer:** Contains a box for PHY PIB, which has a double-headed arrow pointing to the Management Plane. + +A vertical grey bar on the right is labeled **Management Plane**. + +Diagram of the Management plane structure showing layers from Applications down to PHY Layer, with a vertical Management Plane on the right side. + +**Figure 10-1 – Management plane: Introduction** + +All nodes shall implement the management plane functionality enumerated in this clause. The management plane enables a local or remote control entity to perform actions on a node. + +The present version of this Recommendation enumerates management plane functions for node management and firmware upgrade. Future versions may include additional management functions. + +- To enable access to management functions on a service node, the base node shall open a management connection after successful completion of registration (refer to clause 10.4). +- The base node may open such a connection either immediately on successful registration or some time later. +- Unicast management connections shall be identified with CON.TYPE = TYPE\_CL\_MGMT. +- Multicast management connections can also exist. At the time of writing, multicast management connections shall only be used for firmware upgrade. +- There shall be no broadcast management connection. +- In case a service node supports ARQ connections, the base node shall preferentially try to open an ARQ connection for management functions. +- Management plane functions shall use NULL SSCS as specified in clause 9.3. + +## 10.2 Node management + +### 10.2.1 General + +Node management is accomplished through a set of attributes. Attributes are defined for both PHY and MAC layers. The set of these management attributes is called a PLC information base (PIB). Some attributes are read-only while others are read-write. + +PIB attribute identifiers are 16 bit values. This allows up to 65535 PIB attributes to be specified. + +- PIB attribute identifier values from 0 to 32767 are open to be standardized. No proprietary attributes may have identifiers in this range. +- Values in the range 32768 to 65535 are open for vendor-specific usage. + +PIB attribute identifiers in the standard range (0 to 32767) that are not specified in this version are reserved for future use. + +NOTE – The PIB attribute tables below indicate the types of each attribute. For integer types the size of the integer has been specified in bits. An implementation may use a larger integer for an attribute; however, it must not use a smaller size. + +### 10.2.2 PHY PIB attributes + +#### 10.2.2.1 General + +The PHY layer implementation in each device may optionally maintain a set of attributes which provide detailed information about its working. The PHY layer attributes are part of the PLC information base (PIB). + +#### 10.2.2.2 Statistical attributes + +The PHY may provide statistical information for management purposes. The next table lists the statistics that the PHY should make available to management entities across the PLME\_GET primitive. TheID field in this table is the service parameter of the PLME\_GET primitive specified in clause 7.10.4.9. + +**Table 10-1 – PHY read-only variables that provide statistical information** + +| Attribute name | Size (in bits) | Id | Description | +|---------------------------|----------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| phyStatsCRCIncorrectCount | 16 | 0x00A0 | Number of bursts received on the PHY layer for which the CRC was incorrect. | +| phyStatsCRCFailCount | 16 | 0x00A1 | Number of bursts received on the PHY layer for which the CRC was correct, but the Protocol field of the PHY header had an invalid value. This count would reflect the number of times corrupt data was received and the CRC calculation failed to detect it. | +| phyStatsTxDropCount | 16 | 0x00A2 | Number of times that the PHY layer received new data to transmit (PHY_DATA.request) and had to either overwrite existing data in its transmit queue or drop the data in new requests due to a full queue. | +| phyStatsRxDropCount | 16 | 0x00A3 | Number of times when the PHY layer received new data on the channel and had to either overwrite existing data in its receive queue or drop the newly received data due to full queue. | +| phyStatsRxTotalCount | 32 | 0x00A4 | Total number of PPDU correctly decoded. Useful for PHY layer test cases, to estimate the FER. | + +**Table 10-1 – PHY read-only variables that provide statistical information** + +| Attribute name | Size (in bits) | Id | Description | +|-------------------|----------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| phyStatsBlkAvgEvm | 16 | 0x00A5 | Exponential moving average of the EVM over the past 16 PPDU, as returned by the PHY_SNR primitive. Note that the PHY_SNR primitive returns a 3-bit number in dB scale. So first each 3-bit dB number is converted to linear scale (number k goes to $2^{(k/2)}$ ), yielding a 7 bit number with 3 fractional bits. The result is just accumulated over 16 PPDU and reported. | +| phyEmaSmoothing | 8 | 0x00A8 | Smoothing factor divider for values that are updated as the exponential moving average (EMA). Next value is
$V_{next} = S \times NewSample + (1-S) \times V_{prev}$
Where
$S = 1 / (2^{phyEMASmoothing})$ | + +#### 10.2.2.3 Implementation attributes + +It is possible to implement PHY functions conforming to this Recommendation in multiple ways. The multiple implementation options provide some degree of unpredictability for the MAC layers. PHY implementations may optionally provide specific information on parameters which are of interest to the MAC across the PLME\_GET primitive. A list of such parameters which maybe queried across the PLME\_GET primitives by the MAC is provided in Table 10-2. All of the attributes listed in Table 10-2 are implementation constants and shall not be changed. + +**Table 10-2 – PHY read-only parameters, providing information on specific implementation** + +| Attribute name | Size (in bits) | Id | Description | +|----------------------|----------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| phyTxQueueLen | 10 | 0x00B0 | Number of concurrent MPDU that the PHY transmit buffers can hold. | +| phyRxQueueLen | 10 | 0x00B1 | Number of concurrent MPDU that the PHY receive buffers can hold. | +| phyTxProcessingDelay | 20 | 0x00B2 | Time elapsed from the instance when data is received on the MAC-PHY communication interface to the time when it is put on the physical channel. This shall not include communication delay over the MAC-PHY interface.
Value of this attribute is in unit of microseconds. | +| phyRxProcessingDelay | 20 | 0x00B3 | Time elapsed from the instance when data is received on the physical channel to the time when it is made available to the MAC across the MAC-PHY communication interface. This shall not include communication delay over the MAC-PHY interface.
Value of this attribute is in unit of microseconds. | +| phyAgcMinGain | 8 | 0x00B4 | Minimum gain for the AGC $\leq 0\text{dB}$ . | + +**Table 10-2 – PHY read-only parameters, providing information on specific implementation** + +| Attribute name | Size (in bits) | Id | Description | +|------------------|----------------|--------|----------------------------------------------------------------------------------------------------------------------------| +| phyAgcStepValue | 3 | 0x00B5 | Distance between steps in dB $\leq 6$ dB. | +| phyAgcStepNumber | 8 | 0x00B6 | Number of steps so that $\text{phyAgcMinGain} + ((\text{phyAgcStepNumber} - 1) \times \text{phyAgcStepValue}) \geq 21$ dB. | + +### 10.2.3 MAC PIB attributes + +#### 10.2.3.1 General + +NOTE – Note that the "M"(Mandatory) column in the tables below specifies if the PIB attributes are mandatory for all devices (both service node and base node, specified as "All"), only for service nodes ("SN"), only for base nodes ("BN") or not mandatory at all ("No"). + +#### 10.2.3.2 MAC variable attributes + +MAC PIB variables include the set of PIB attributes that influence the functional behaviour of an implementation. These attributes may be defined externally to the MAC, typically by the management entity and implementations may allow changes to their values during normal running, i.e., even after the device start-up sequence has been executed. + +An external management entity can have access to these attributes through the MLME\_GET (clause 8.5.5.7) and MLME\_SET (clause 8.5.5.9) set of primitives. TheID field in the following table would be the PIBAttribute that needs to be passed to the MLME SAP while working on these parameters. + +**Table 10-3 – Table of MAC read-write variables** + +| Attribute name | Id | Type | M | Valid range | Description | Def. | +|-------------------------|--------|----------|----|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| macMinSwitchSearch Time | 0x0010 | Integer8 | No | 16-32 seconds | Minimum time for which a service node in the disconnected status should scan the channel for beacons before it can broadcast PNPDUs. This attribute is not maintained in base nodes. | 24 | +| macMaxPromotionPdu | 0x0011 | Integer8 | No | 1-4 | Maximum number of PNPDUs that may be transmitted by a service node in a period of macPromotionPduTx Period seconds. This attribute is not maintained in base nodes. | 2 | + +**Table 10-3 – Table of MAC read-write variables** + +| Attribute name | Id | Type | M | Valid range | Description | Def. | +|--------------------------|--------|----------|----|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| macPromotionPduTx Period | 0x0012 | Integer8 | No | 2-8 seconds | Time quantum for limiting a number of PNPDU s transmitted from a service node. No more than macMaxPromotionPdu may be transmitted in a period of macPromotionPduTx Period seconds. | 5 | +| macBeaconsPerFrame | 0x0013 | Integer8 | BN | 1-5 | Maximum number of beacon slots that may be provisioned in a frame.
This attribute is maintained in base nodes. | 5 | +| macSCPMaxTxAttempts | 0x0014 | Integer8 | No | 2-5 | Number of times the CSMA algorithm would attempt to transmit requested data when a previous attempt was withheld due to the PHY indicating channel busy. | 5 | +| macCtlReTxTimer | 0x0015 | Integer8 | No | 2-20 seconds | Number of seconds for which a MAC entity waits for acknowledgement of receipt of the MAC control packet from its peer entity. On expiry of this time, the MAC entity may retransmit the MAC control packet. | 15 | +| macMaxCtlReTx | 0x0018 | Integer8 | No | 3-5 | Maximum number of times a MAC entity will try to retransmit an unacknowledged MAC control packet. If the retransmit count reaches this maximum, the MAC entity shall abort further attempts to transmit the MAC control packet. | 3 | + +**Table 10-3 – Table of MAC read-write variables** + +| Attribute name | Id | Type | M | Valid range | Description | Def. | +|-----------------|--------|----------|-----|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| macEMASmoothing | 0x0019 | Integer8 | All | 0-7 | Smoothing factor divider for values that are updated as the exponential moving average (EMA). Next value is
$V_{next} = S \times NewSample + (1 - S) \times V_{prev}$
Where
$S = 1 / (2^{macEMASmoothing})$ . | 3 | + +**Table 10-4 – Table of MAC read-only variables** + +| Attribute name | Id | Type | M | Valid range | Description | Def. | +|--------------------|--------|----------|----|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| macSCPRBO | 0x0016 | Integer8 | No | 1-15 symbols | Random backoff period for which an implementation should delay the start of channel-sensing iterations when attempting to transmit data in the SCP.
This is a 'read-only' attribute. | – | +| macSCPChSenseCount | 0x0017 | Integer8 | No | 2-5 | Number of times for which an implementation has to perform channel-sensing.
This is a 'read-only' attribute. | – | + +#### 10.2.3.3 Functional attributes + +Some PIB attributes belong to the functional behaviour of the MAC. They provide information on specific aspects. A management entity can only read their present value using the MLME\_GET primitives. The value of these attributes cannot be changed by a management entity through the MLME\_SET primitives. + +The ID field in the table below would be the *PIBAttribute* that needs to be passed MLME\_GET SAP for accessing the value of these attributes. + +**Table 10-5 – Table of MAC read-only variables that provide functional information** + +| Attribute name | Id | Type | M | Valid range | Description | +|------------------------|--------|-----------|----|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| macLNID | 0x0020 | Integer16 | SN | 0-16383 | LNID allocated to this node at time of its registration. | +| MacLSID | 0x0021 | Integer8 | SN | 0-255 | LSID allocated to this node at time of its promotion. This attribute is not maintained if a node is in a terminal functional state. | +| MacSID | 0x0022 | Integer8 | SN | 0-255 | SID of the switch node through which this node is connected to the subnetwork. This attribute is not maintained in a base node. | +| MacSNA | 0x0023 | EUI-48 | SN | | Subnetwork address to which this node is registered.
The base node returns the SNA it is using. | +| MacState | 0x0024 | Enumerate | SN | | Present functional state of the node | +| | | | | 0 | DISCONNECTED | +| | | | | 1 | TERMINAL | +| | | | | 2 | SWITCH | +| | | | | 3 | BASE | +| MacSCPLength | 0x0025 | Integer16 | SN | | The SCP length, in symbols, in the present frame. | +| MacNodeHierarchy Level | 0x0026 | Integer8 | SN | 0-63 | Level of this node in subnetwork hierarchy. | +| MacBeaconSlotCount | 0x0027 | Integer8 | SN | 0-7 | Number of beacon slots provisioned in the present frame structure. | +| macBeaconRxSlot | 0x0028 | Integer8 | SN | 0-7 | Beacon slot on which this device's switch node transmits its beacon. This attribute is not maintained in a base node. | +| MacBeaconTxSlot | 0x0029 | Integer8 | SN | 0-7 | Beacon slot in which this device transmits its beacon. This attribute is not maintained in service nodes that are in a terminal functional state. | +| MacBeaconRxFrequency | 0x002A | Integer8 | SN | 0-31 | Number of frames between the reception of two successive beacons. A value of 0x0 indicates beacons are received in every frame. This attribute is not maintained in base nodes. | + +**Table 10-5 – Table of MAC read-only variables that provide functional information** + +| Attribute name | Id | Type | M | Valid range | Description | +|----------------------|--------|-----------|-----|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MacBeaconTxFrequency | 0x002B | Integer8 | SN | 0-31 | Number of frames between transmissions of two successive beacons. A value of 0x0 indicates beacons are transmitted in every frame. This attribute is not maintained in service nodes that are in a terminal functional state. | +| MacCapabilities | 0x002C | Integer16 | All | Bit-map | Bitmap of MAC capabilities of a given device. This attribute shall be maintained on all devices. Bits in sequence of right-to-left shall have the following meaning:
Bit 0: switch capable;
Bit 1: packet aggregation;
Bit 2: contention-free period;
Bit 3: direct connection;
Bit 4: multicast;
Bit 5: PHY robustness management;
Bit 6: ARQ;
Bit 7: reserved by ITU-T;
Bit 8: direct connection switching;
Bit 9: multicast switching capability;
Bit 10: PHY robustness management switching capability;
Bit 11: ARQ buffering switching capability;
Bits 12 to 15: reserved by ITU-T. | + +#### 10.2.3.4 Statistical attributes + +The MAC layer shall provide statistical information for management purposes. Table 10-6 lists the statistics that the MAC shall make available to management entities across the MLME\_GET primitive. + +The ID field in the table below would be the *PIBAttribute* that needs to be passed to the MLME\_GET SAP for accessing the value of these attributes. + +**Table 10-6 – Table of MAC read-only variables that provide statistical information** + +| Attribute name | Id | M | Type | Description | +|--------------------|--------|----|-----------|--------------------------------------------------------------------------------------------------| +| macTxDataPktCount | 0x0040 | No | Integer32 | Count of successfully transmitted MSDUs. | +| MacRxDataPktCount | 0x0041 | No | Integer32 | Count of successfully received MSDUs whose destination address was this node. | +| MacTxCtrlPktCount | 0x0042 | No | Integer32 | Count of successfully transmitted MAC control packets. | +| MacRxCtrlPktCount | 0x0043 | No | Integer32 | Count of successfully received MAC control packets whose destination address was this node. | +| MacCSMAFailCount | 0x0044 | No | Integer32 | Count of failed CSMA transmitted attempts. | +| MacCSMACHBusyCount | 0x0045 | No | Integer32 | Count of number of times this node had to back off SCP transmission due to a channel busy state. | + +#### 10.2.3.5 MAC list attributes + +The MAC layer shall make certain lists available to the management entity across the MLME\_LIST\_GET primitive. These lists are given in Table 10-7. Although a management entity can read each of these lists, it cannot change the contents of any of them. + +The ID field in the table below would be the *PIBListAttribute* that needs to be passed to the MLME\_LIST\_GET primitive for accessing the value of these attributes. + +**Table 10-7 – Table of read-only lists made available by MAC layer through the management interface** + +| List attribute Name | Id | M | Description | | | +|---------------------|--------|----|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------------------------------| +| macListRegDevices | 0x0050 | BN | List of registered devices. This list is maintained by the base node only. Each entry in this list shall comprise the following information. | | | +| | | | Entry element | Type | Description | +| | | | regEntryID | EUI-48 | EUI-48 of the registered node | +| | | | regEntryLNID | Integer16 | LNID allocated to this node | +| | | | regEntryState | TERMINAL=1,
SWITCH=2 | Functional state of this node | +| | | | regEntryLSID | Integer16 | SID allocated to this node | +| | | | regEntrySID | Integer16 | SID of switch through which this node is connected | +| | | | regEntryLevel | Integer8 | Hierarchy level of this node | + +**Table 10-7 – Table of read-only lists made available by MAC layer through the management interface** + +| List attribute Name | Id | M | Description | | | +|---------------------|--------|----|---------------------------------------------------------------------------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | | | +| | | | regEntryTCap | Integer8 | Bitmap of MAC capabilities of terminal functions in this device
Bits in sequence of right-to-left shall have the following meaning:
Bit 0: switch capable;
Bit 1: packet aggregation;
Bit 2: contention-free period;
Bit 3: direct connection;
Bit 4: multicast;
Bit 5: PHY robustness management;
Bit 6: ARQ;
Bit 7: reserved by ITU-T. | +| | | | regEntrySwCap | Integer8 | Bitmap of MAC switching capabilities of this device
Bits in sequence of right-to-left shall have the following meaning:
Bit 0: direct connection switching capability;
Bit 1: multicast switching;
Bit 2: PHY robustness management switching capability;
Bit 3: ARQ buffering switching capability;
Bit 4 to 7: reserved by ITU-T. | +| macListActiveConn | 0x0051 | BN | List of active non-direct connections. This list is maintained by the base node only. | | | +| | | | Entry element | Type | Description | +| | | | connEntrySID | Integer16 | SID of switch through which the service node is connected. | +| | | | connEntryLNID | Integer16 | NID allocated to service node | +| | | | connEntryLCID | Integer8 | LCID allocated to this connection | +| | | | connEntryID | EUI-48 | EUI-48 of service node | + +**Table 10-7 – Table of read-only lists made available by MAC layer through the management interface** + +| List attribute Name | Id | M | Description | | | +|----------------------------|-----------|----------|----------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------| +| macListMcast Entries | 0x0052 | No | List of entries in multicast switching table. This list is not maintained by service nodes in a terminal functional state. | | | +| | | | | | | +| | | | Entry element | Type | Description | +| | | | mcastEntryLCID | Integer8 | LCID of the multicast group | +| | | | mcastEntry Members | Integer16 | Number of child nodes (including the node itself) that are members of this group. | +| macListSwitchTable | 0x0053 | SN | List the switch table. This list is not maintained by service nodes in a terminal functional state. | | | +| | | | | | | +| | | | Entry element | Type | Description | +| | | | stblEntryLSID | Integer16 | SID of attached switch node | +| macListDirectConn | 0x0054 | No | List of direct connections that are active. This list is maintained only in the base node. | | | +| | | | | | | +| | | | Entry element | Type | Description | +| | | | dconnEntrySrcSID | Integer16 | SID of switch through which the source service node is connected | +| | | | dconEntrySrcLNID | Integer16 | NID allocated to the source service node | +| | | | dconnEntrySrcLCID | Integer8 | LCID allocated to this connection at the source | +| | | | dconnEntrySrcID | EUI-48 | EUI-48 of source service node | +| | | | dconnEntryDstSID | Integer16 | SID of switch through which the destination service node is connected | +| | | | dconnEntryDstLNID | Integer16 | NID allocated to the destination service node | +| | | | dconnEntryDstLCID | Integer8 | LCID allocated to this connection at the destination | +| | | | dconnEntryDstID | EUI-48 | EUI-48 of destination service node | +| | | | dconnEntryDSID | Integer16 | SID of switch that is the direct switch | +| | | | dconnEntryDID | EUI-48 | EUI-48 of direct switch | + +**Table 10-7 – Table of read-only lists made available by MAC layer through the management interface** + +| List attribute Name | Id | M | Description | | | +|----------------------------|-----------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------| +| macListDirectTable | 0x0055 | No | List the direct switch table | | | +| | | | Entry element | Type | Description | +| | | | dconnEntrySrcSID | Integer16 | SID of switch through which the source service node is connected | +| | | | dconEntrySrcLNID | Integer16 | NID allocated to the source service node | +| | | | dconnEntrySrcLCID | Integer8 | LCID allocated to this connection at the source | +| | | | dconnEntryDstSID | Integer16 | SID of switch through which the destination service node is connected | +| | | | dconnEntryDstLNID | Integer16 | NID allocated to the destination service node | +| | | | dconnEntryDstLCID | Integer8 | LCID allocated to this connection at the destination | +| | | | dconnEntryDID | EUI-48 | EUI-48 of direct switch | +| macListAvailable Switches | 0x0056 | SN | List of switch nodes whose beacons are received. | | | +| | | | Entry Element | Type | Description | +| | | | slistEntrySNA | EUI-48 | EUI-48 of the subnetwork | +| | | | slistEntryLSID | Integer16 | SID of this switch | +| | | | slistEntryLevel | Integer8 | Level of this switch in subnetwork hierarchy | +| | | | slistEntryRxLvl | Integer8EMA | Received signal level for this switch | +| | | | slistEntryRxSNR | Integer8 EMA | Signal to noise ratio for this switch | +| macListPhyComm | 0x0057 | All | List of PHY communication parameters. This table is maintained in every node. For terminal nodes it contains only one entry for the switch the node is connected through. For other nodes this contains also entries for every directly connected child node. | | | +| | | | Entry element | Type | Description | +| | | | phyCommEUI | EUI-48 | EUI-48 of the other device | +| | | | phyCommTxPwr | Integer8 | Tx power of GPDU packets sent to the device | +| | | | phyCommTxCod | Integer8 | Tx coding of GPDU packets sent to the device | +| | | | phyCommRxCod | Integer8 | Rx coding of GPDU packets received from the device | + +**Table 10-7 – Table of read-only lists made available by MAC layer through the management interface** + +| List attribute Name | Id | M | Description | | | +|---------------------|----|---|------------------|-------------|---------------------------------------------------------| +| | | | phyCommRxBvl | Integer8EMA | Rx power level of GPDU packets received from the device | +| | | | phyCommSNR | Integer8EMA | SNR of GPDU packets received from the device | +| | | | phyCommTxPwr Mod | Integer8 | Number of times the Tx power was modified | +| | | | phyCommTxCod Mod | Integer8 | Number of times the Tx coding was modified | +| | | | phyCommRxCod Mod | Integer8 | Number of times the Rx coding was modified | + +#### 10.2.3.6 Action PIB attributes + +Some of the conformance tests require triggering certain actions on service nodes. The following table lists the set of action attributes that need to be supported by all implementations. + +**Table 10-8 – Action PIB attributes** + +| Attribute name | Id | M | Size (in bits) | Description | +|---------------------|--------|----|----------------|-----------------------------------------------------------------------------------| +| MACActionTxData | 0x0060 | SN | 8 | Total number of PPDU correctly decoded. Useful for the PHY layer to estimate FER. | +| MACActionConnClose | 0x0061 | SN | 8 | Trigger to close one of the open connections | +| MACActionRegReject | 0x0062 | SN | 8 | Trigger to reject incoming registration request | +| MACActionProReject | 0x0063 | SN | 8 | Trigger to reject incoming promotion request | +| MACActionUnregister | 0x0064 | SN | 8 | Trigger to unregister from the subnetwork | + +### 10.2.4 Application PIB attributes + +The following PIB attributes are used for general administration and maintenance of an ITU-T G.9904 compliant device. These attributes do not affect the communication functionality, but enable easier administration. + +These attributes shall be supported by both base node and service node devices. + +**Table 10-9 – Applications PIB attributes** + +| Attribute Name | Size (in bits) | Id | Description | +|----------------|----------------|--------|-----------------------------------------------------------| +| AppFwVersion | 128 | 0x0075 | Textual description of firmware version running on device | +| AppVendorId | 16 | 0x0076 | PRIME Alliance-assigned unique vendor identifier | +| AppProductId | 16 | 0x0077 | Vendor-assigned unique identifier for specific product | + +## 10.3 Firmware upgrade + +### 10.3.1 General + +The present clause specifies firmware upgrade. Devices supporting ITU-T G.9904 may have several firmware inside them, at least one supporting the application itself, and one related to the ITU-T G.9904 protocol. Although it is possible that the application can perform the firmware upgrade of all the firmware images of the device, for instance DLMS/COSEM image transfer, using COSEM image transfer object, supporting ITU-T G.9904 firmware upgrade is mandatory in order to process the ITU-T G.9904 firmware upgrade independently of the application. + +### 10.3.2 Requirements and features + +This clause specifies the firmware upgrade application, which is unique and mandatory for base nodes and service nodes. + +The most important features of the firmware upgrade mechanism are listed below. See the following clauses for more information. The following refer to the FU mechanism: + +- It shall be a part of the management plane and therefore use the NULL SSCS, as specified in clause 9.3. +- It is able to work in unicast (default mode) and multicast (optional mode). The control messages are always sent using unicast connections, whereas data can be transmitted using both unicast and multicast. No broadcast should be used to transmit data. +- It may change the data packet sizes according to the channel conditions. The packet size will not be changed during the download process. +- It is able to request basic information from the service nodes at any time, such as device model, firmware version and FU protocol version. +- It shall be able to be aborted at any time. +- It shall check the integrity of the downloaded FW after completing the reception. In case of failure, the firmware upgrade application shall request a new retransmission. +- The new firmware shall be executed in the service nodes only if they are commanded to do so. The FU application shall have to be able to set the moment when the reset takes place. +- Must be able to reject the new firmware after a "test" period and switch to the old version. The duration of this test period has to be fixed by the FU mechanism. + +### **10.3.3 General description** + +#### **10.3.3.1 General** + +The firmware upgrade mechanism is able to work in unicast and multicast modes. All control messages are sent using unicast connections, whereas the data can be sent via unicast (by default) or multicast (only if supported by the manufacturer). Note that in order to ensure correct reception of the FW when service nodes from different vendors are upgraded, data packets shall not be sent via broadcast. Only unicast and multicast are allowed. A node will reply only to messages sent via unicast. See clause 10.3.5 for a detailed description of the control and information messages used by the FU mechanism. + +The unicast and multicast connections are set up by the base node. In the case of supporting multicast, the base node shall request the nodes from a specific vendor to join a specific multicast group, which is exclusively created to perform the firmware upgrade and is removed after finishing it. + +As said before, it is up to the vendor to use unicast or multicast for transmitting the data. In the case of unicast data transmission, please note that the use of ARQ is an optional feature. Some examples showing the traffic between the base node and the service nodes in unicast and multicast are provided in clause 10.3.6. + +After completing the firmware download, each service node is committed by the base node to perform an integrity check on it. The firmware download will be restarted if the firmware image results are corrupted. In another case, the service nodes will wait until they are commanded by the base node to execute the new firmware. + +The FU mechanism can set up the instant when the recently downloaded firmware is executed on the service nodes. Thus, the base node can choose to restart all nodes at the same time or in several steps. After restart, each service node runs the new firmware for a time period specified by the FU mechanism. If this period expires without receiving any confirmation from the base node, or the base node decides to abort the upgrade process, the service nodes will reject the new firmware and switch to the old version. In any other case (a confirmation message is received) the service nodes will consider the new firmware as the only valid version and delete the old one. + +This is done in order to leave an "open back-door" in case the new firmware is defect or corrupt. Please note that the service nodes are not allowed to discard any of the stored firmware versions until the final confirmation from the base node arrives or until the safety time period expires. The two last firmware upgrade steps explained above are shown in clause 10.3.5. See clause 10.3.5.3 for a detailed description of the control messages. + +![Sequence diagram showing a firmware upgrade process between a Base node and two Service nodes. The Base node initiates the upgrade from version 1 to version 2. Service node 1 (TW version 1) and Service node 2 (TW version 1) receive FU_EXEC_REQ. Service node 1 responds with FU_STATE_RSP and starts a RestartTimer. Service node 2 also responds with FU_STATE_RSP and starts a RestartTimer. Service node 1 then transitions to Service node 1 (TW version 2) and sends FU_ONFIRM_REQ to the Base node. Service node 2 transitions to Service node 2 (TW version 2) and starts a SafetyTimer. Service node 2 then transitions back to Service node 2 (TW version 1) and sends FU_STATE_RSP to the Base node. The diagram also shows the Base node sending FU_EXEC_REQ and FU_STATE_RSP messages. A note at the bottom right indicates G.9904(12)_F10-2.](bdee2715697a4142d16a360549fa7c7f_img.jpg) + +Sequence diagram showing a firmware upgrade process between a Base node and two Service nodes. The Base node initiates the upgrade from version 1 to version 2. Service node 1 (TW version 1) and Service node 2 (TW version 1) receive FU\_EXEC\_REQ. Service node 1 responds with FU\_STATE\_RSP and starts a RestartTimer. Service node 2 also responds with FU\_STATE\_RSP and starts a RestartTimer. Service node 1 then transitions to Service node 1 (TW version 2) and sends FU\_ONFIRM\_REQ to the Base node. Service node 2 transitions to Service node 2 (TW version 2) and starts a SafetyTimer. Service node 2 then transitions back to Service node 2 (TW version 1) and sends FU\_STATE\_RSP to the Base node. The diagram also shows the Base node sending FU\_EXEC\_REQ and FU\_STATE\_RSP messages. A note at the bottom right indicates G.9904(12)\_F10-2. + +NOTE – In normal circumstances, both service nodes should either accept or reject the new firmware version. Both possibilities are shown above simultaneously for academic purposes. + +**Figure 10-2 – Restarting the nodes and running the new firmware** + +#### 10.3.3.2 Segmentation + +The firmware image is the information to be transferred, in order to process a firmware upgrade. The size of the firmware image will be called "*ImageSize*", and is measured in bytes. This image is divided into smaller elements called pages that are easier to be transferred in packets. The "*PageSize*" may be one of the following: 32 bytes, 64 bytes, 128 bytes or 192 bytes. This implies that the number of pages in a firmware image is calculated by the following formula: + +$$PageCount = \left\lceil \frac{ImageSize}{PageSize} \right\rceil + 1$$ + +Every page will have a size specified by *PageSize*, except the last one that will contain the remaining bytes up to *ImageSize*. + +The *PageSize* is configured by the base node and notified during the initialization of the firmware upgrade process, and imposes a condition in the size of the packets being transferred by the protocol. + +### 10.3.4 Firmware upgrade PIB attributes + +The following PIB attributes shall be supported by service nodes to support the firmware download application. + +**Table 10-10 – FU PIB attributes** + +| Attribute name | Size (in bits) | Id | Description | +|-------------------|----------------|--------|--------------------------------------------------------------------------------------------------------------------------| +| AppFwdlRunning | 16 | 0x0070 | Indicates if a firmware download is in progress or not.
0 = No firmware download
1 = Firmware download in progress | +| AppFwdlRxPktCount | 16 | 0x0071 | Count of firmware download packets that have been received until the time of query | + +### 10.3.5 State machine + +#### 10.3.5.1 General + +A service node using the firmware upgrade service will be in one of five possible states: *Idle*, *Receiving*, *Complete*, *Countdown* and *Upgrade*. These states, the events triggering them and the resulting actions/output messages are detailed below. + +**Table 10-11 – FU state machine** + +| FU State | Description | Event | Output (or action to be performed) | Next state | +|-------------|--------------------------------------|------------------------|------------------------------------|------------------| +| Idle | The FU application is doing nothing. | Receive FU_INFO_REQ | FU_INFO_RSP. | Idle | +| | | Receive FU_STATE_REQ | FU_STATE_RSP (.State = 0). | Idle | +| | | Receive FU_MISS_REQ | FU_STATE_RSP (.State = 0). | Idle | +| | | Receive FU_CRC_REQ | FU_STATE_RSP (.State = 0). | Idle | +| | | Receive FU_INIT_REQ | FU_STATE_RSP (.State = 1). | Receiving | +| | | Receive FU_DATA | (ignore). | Idle | +| | | Receive FU_EXEC_REQ | FU_STATE_RSP (.State = 0). | Idle | +| | | Receive FU_CONFIRM_REQ | FU_STATE_RSP (.State = 0). | Idle | +| | | Receive FU_KILL_REQ | FU_STATE_RSP (.State = 0). | Idle | + +**Table 10-11 – FU state machine** + +| FU State | Description | Event | Output (or action to be performed) | Next state | +|-------------------------|-----------------------------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------|------------------| +| Receiving | The FU application is receiving the firmware image. | Complete FW received and CRC OK | (if CRC of the complete image is OK, switch to Complete without sending any additional messages) | Complete | +| | | Receive FU_INFO_REQ | FU_INFO_RSP. | Receiving | +| | | Receive FU_STATE_REQ | FU_STATE_RSP (.State = 1). | Receiving | +| | | Receive FU_MISS_REQ | FU_MISS_LIST or FU_MISS_BITMAP. | Receiving | +| | | Receive FU_CRC_REQ | FU_CRC_RSP (FU_STATE_RSP if the Bitmap is not complete) | Receiving | +| | | Receive FU_INIT_REQ | FU_STATE_RSP (.State = 1) | Receiving | +| | | Receive FU_DATA | (receiving data, normal behaviour). | Receiving | +| | | Receive FU_EXEC_REQ | FU_STATE_RSP (.State = 1). | Receiving | +| | | Receive FU_CONFIRM_REQ | FU_STATE_RSP (.State = 1). | Receiving | +| | | Receive FU_KILL_REQ | FU_STATE_RSP (.State = 0); (switch to Idle ). | Idle | + +**Table 10-11 – FU state machine** + +| FU State | Description | Event | Output (or action to be performed) | Next state | +|------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------------------------------------------------------|------------------| +| Complete | Upgrade completed, image integrity OK, the service node is waiting to reboot with the new FW version. | Receive FU_INFO_REQ | FU_INFO_RSP. | Complete | +| | | Receive FU_STATE_REQ | FU_STATE_RSP (.State = 2). | Complete | +| | | Receive FU_MISS_REQ | FU_STATE_RSP (.State = 2). | Complete | +| | | Receive FU_CRC_REQ | FU_STATE_RSP (.State = 2). | Complete | +| | | Receive FU_INIT_REQ | FU_STATE_RSP (.State = 2). | Complete | +| | | Receive FU_DATA | (ignore). | Complete | +| | | Receive FU_EXEC_REQ with RestartTimer != 0 | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_EXEC_REQ with RestartTimer = 0 | FU_STATE_RSP (.State = 4). | Upgrade | +| | | Receive FU_CONFIRM_REQ | FU_STATE_RSP (.State = 2). | Complete | +| | | Receive FU_KILL_REQ | FU_STATE_RSP (.State = 0); (switch to Idle ). | Idle | +| Countdown | Waiting until RestartTimer expires. | RestartTimer expires | (switch to Upgrade ). | Upgrade | +| | | Receive FU_INFO_REQ | FU_INFO_RSP. | Countdown | +| | | Receive FU_STATE_REQ | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_MISS_REQ | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_CRC_REQ | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_INIT_REQ | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_DATA | (ignore). | Countdown | +| | | Receive FU_EXEC_REQ with RestartTimer != 0 | FU_STATE_RSP (.State = 3); (update RestartTimer and SafetyTimer). | Countdown | +| | | Receive FU_EXEC_REQ with RestartTimer = 0 | FU_STATE_RSP (.State = 4); (update RestartTimer and SafetyTimer). | Upgrade | +| | | Receive FU_CONFIRM_REQ | FU_STATE_RSP (.State = 3). | Countdown | +| | | Receive FU_KILL_REQ | FU_STATE_RSP (.State = 0); (switch to Idle ). | Idle | + +**Table 10-11 – FU state machine** + +| FU State | Description | Event | Output (or action to be performed) | Next state | +|-----------------------|----------------------------------------------------------------------------------------------|----------------------------|-------------------------------------------------------------------|----------------| +| Upgrade | The FU mechanism reboots using the new FW image and tests it for SafetyTimer seconds. | SafetyTimer expires | FU_STATE_RSP (.State = 0); (switch to Idle , FW rejected). | Idle | +| | | Receive FU_INFO_REQ | FU_INFO_RSP. | Upgrade | +| | | Receive FU_STATE_REQ | FU_STATE_RSP (.State = 4). | Upgrade | +| | | Receive FU_MISS_REQ | FU_STATE_RSP (.State = 4). | Upgrade | +| | | Receive FU_CRC_REQ | FU_STATE_RSP (.State = 4). | Upgrade | +| | | Receive FU_INIT_REQ | FU_STATE_RSP (.State = 4). | Upgrade | +| | | Receive FU_DATA | (ignore). | Upgrade | +| | | Receive FU_EXEC_REQ | FU_STATE_RSP (.State = 0). | Upgrade | +| | | Receive FU_CONFIRM_REQ | FU_STATE_RSP (.State = 0); (switch to Idle , FW accepted). | Idle | +| | | Receive FU_KILL_REQ | FU_STATE_RSP (.State = 0); (switch to Idle , FW rejected). | Idle | + +The state diagram is represented below. Please note that only the most relevant events are shown in the state transitions. See clause 10.3.5 for a detailed description of each state's behaviour and the events and actions related to them. A short description of each state is provided in clause 10.3.5.2. + +![State diagram for firmware upgrade mechanism showing states IDLE, UPGRADE, RECEIVING, COMPLETE, and COUNTDOWN with transitions for messages like FU_CONFIRM_REQ, FU_KILL_REQ, FU_DATA, FU_EXEC_REQ, and internal events like SafetyTimer expired or RestartTimer expired.](88c92858439684b2103e88cb143fb98e_img.jpg) + +The diagram illustrates the firmware upgrade mechanism state transitions. The states are IDLE, UPGRADE, RECEIVING, COMPLETE, and COUNTDOWN. Transitions are triggered by messages (FU\_CONFIRM\_REQ, FU\_KILL\_REQ, FU\_DATA, FU\_EXEC\_REQ) and internal events (SafetyTimer expired, RestartTimer expired). The legend indicates that FU\_KILL\_REQ and FU\_EXEC\_REQ are BN → SN messages, while FU\_STATE\_RSP is a SN → BN message. Internal events are labeled 'Receive'. Running FW version is indicated by [FW i]. + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> RECEIVING: FU_INIT_REQ (Receive) + IDLE --> IDLE: FU_KILL_REQ (FU_STATE_RSP) + RECEIVING --> COMPLETE: Reception completed and CRC ok + RECEIVING --> IDLE: FU_KILL_REQ (FU_STATE_RSP) + RECEIVING --> RECEIVING: FU_DATA (Receive data CRC / not ok) + COMPLETE --> IDLE: FU_KILL_REQ (FU_STATE_RSP) + COMPLETE --> COUNTDOWN: FU_EXEC_REQ.RestartTimer = 0 (FU_STATE_RSP) + COUNTDOWN --> IDLE: FU_KILL_REQ (FU_STATE_RSP) + COUNTDOWN --> UPGRADE: FU_EXEC_REQ.RestartTimer != 0 (FU_STATE_RSP) + COUNTDOWN --> COUNTDOWN: FU_EXEC_REQ.RestartTimer != 0 (FU_STATE_RSP) + UPGRADE --> IDLE: FU_CONFIRM_REQ (FU_STATE_RSP) + UPGRADE --> IDLE: FU_KILL_REQ (FU_STATE_RSP) + UPGRADE --> COUNTDOWN: SafetyTimer expired + UPGRADE --> RECEIVING: FU_KILL_REQ (FU_STATE_RSP) + UPGRADE --> UPGRADE: FU_EXEC_REQ.RestartTimer != 0 (FU_STATE_RSP) + +``` + +State diagram for firmware upgrade mechanism showing states IDLE, UPGRADE, RECEIVING, COMPLETE, and COUNTDOWN with transitions for messages like FU\_CONFIRM\_REQ, FU\_KILL\_REQ, FU\_DATA, FU\_EXEC\_REQ, and internal events like SafetyTimer expired or RestartTimer expired. + +Figure 10-3 – Firmware upgrade mechanism, state diagram + +#### 10.3.5.2 State description + +##### 10.3.5.2.1 Idle + +The service nodes are in "Idle" state when they are not performing a firmware upgrade. The reception of an FU\_INIT\_REQ message is the only event that forces the service node to switch to the next state ("Receiving"). FU\_KILL\_REQ aborts the upgrade process and forces the service nodes to switch from any state to "Idle". + +##### 10.3.5.2.2 Receiving + +The service nodes receive the firmware image via FU\_DATA messages. Once the download is complete, the integrity of the image is checked by the base node using FU\_CRC\_REQ and the service node responds with FU\_CRC\_RSP. This final CRC on the complete FW image is mandatory. If the CRC results are OK, the service node responds with FU\_CRC\_RSP and then switches to "Complete" state. If the CRC is wrong, the service node reports this to the base node via FU\_CRC\_RSP, drops the complete FW image, updates the bitmap accordingly and waits for packet retransmission. + +Please remember that the service node will change from "Receiving" to "Complete" state only if the complete FW has been downloaded and the CRC has been successful. + +##### 10.3.5.2.3 Complete + +A service node in "Complete" state waits until the reception of an FU\_EXEC\_REQ message. The service node may switch either to "Countdown" or "Upgrade" depending on the field *RestartTimer*, which specifies in which instant the service node has to reboot using the new firmware. If *RestartTimer* = 0, the service node immediately switches to "Upgrade"; else, the service node switches to "Countdown". + +##### 10.3.5.2.4 Countdown + +A service node in "Countdown" state waits a period of time specified in the *RestartTimer* field of a previous FU\_EXEC\_REQ message. When this timer expires, it automatically switches to "Upgrade". + +FU\_EXEC\_REQ can be used in "Countdown" state to reset *RestartTimer* and *SafetyTimer*. In this case, both timers have to be specified in FU\_EXEC\_REQ because both will be overwritten. Note that it is possible to force the node to immediately switch from the "Countdown" to "Upgrade" state setting *RestartTimer* to zero. + +##### 10.3.5.2.5 Upgrade + +A service node in "Upgrade" state shall run the new firmware during a time period specified in FU\_EXEC\_REQ.*SafetyTimer*. If it does not receive any confirmation at all before this timer expires (or if it receives an FU\_KILL\_REQ message), the service node discards the new FW, reboots with the old version and switches to "Idle" state. In any other case it discards the old FW version and switches to "Idle" state. + +#### 10.3.5.3 Control packets + +##### 10.3.5.3.1 FU\_INIT\_REQ + +The base node sends this packet in order to configure a service node for the Firmware upgrade. If the service node is in "Idle" state, it will change its state from "Idle" to "Receiving" and will answer with FU\_STATE\_RSP. In any other case it will just answer by sending FU\_STATE\_RSP. + +The content of FU\_INIT\_REQ is shown below. + +**Table 10-12 – Fields of FU\_INIT\_REQ** + +| Field | Length | Description | +|-----------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 0 = FU_INIT_REQ. | +| Version | 2 bits | 0 for this version of the protocol | +| PageSize | 2 bits | 0 for a PageSize=32
1 for a PageSize=64
2 for a PageSize=128
3 for a PageSize=192 | +| ImageSize | 32 bits | Size of the firmware upgrade image in bytes | +| CRC | 32 bits | CRC of the firmware upgrade Image
The input polynomial $M(x)$ is formed as a polynomial whose coefficients are bits of the data being checked (the first bit to check is the highest order coefficient and the last bit to check is the coefficient of order zero). The generator polynomial for the CRC is
$G(x)=x^{32}+x^{26}+x^{23}+x^{22}+x^{16}+x^{12}+x^{11}+x^{10}+x^8+x^7+x^5+x^4+x^2+x+1$ . The remainder $R(x)$ is calculated as the remainder from the division of $M(x) \cdot x^{32}$ by $G(x)$ . The coefficients of the remainder will then be the resulting CRC. | + +##### 10.3.5.3.2 FU\_EXEC\_REQ + +This packet is used by the base node to command a service node in "*Complete*" state to restart using the new firmware, once the complete image has been received by the service node. FU\_EXEC\_REQ specifies when the service node has to restart and how long the "safety" period shall be, as explained in clause 10.3.5.2.5. Additionally, FU\_EXEC\_REQ can be used in "*Countdown*" state to reset the restart and the safety timers. + +Depending on the value of *RestartTimer*, a service node in "*Complete*" state may change either to "*Countdown*" or to "*Upgrade*" state. In any case, the service node answers with FU\_STATE\_RSP. + +In "*Countdown*" state, the base node can reset *RestartTimer* and *SafetyTimer* with an FU\_EXEC\_REQ message (both timers must be specified in the message because both will be overwritten). + +The content of this packet is described below. + +**Table 10-13 – Fields of FU\_EXEC\_REQ** + +| Field | Length | Description | +|--------------|---------|----------------------------------------------------------------------------------------------------| +| Type | 4 bits | 1 = FU_EXEC_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| RestartTimer | 16 bits | 0..65536 seconds; time before restarting with new FW | +| SafetyTimer | 16 bits | 0..65536 seconds; time to test the new FW. It starts when the " Upgrade " state is entered. | + +##### 10.3.5.3.3 FU\_CONFIRM\_REQ + +This packet is sent by the base node to a service node in "*Upgrade*" state to confirm the current FW. If the service node receives this message, it discards the old FW version and switches to "*Idle*" state. The service node answers with FU\_STATE\_RSP when receiving this message. + +In any other state, the service node answers with FU\_STATE\_RSP without performing any additional actions. + +This packet contains the fields described below. + +**Table 10-14 – Fields of FU\_CONFIRM\_REQ** + +| Field | Length | Description | +|-----------------|--------|------------------------------------| +| Type | 4 bits | 2 = FU_CONFIRM_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | + +##### 10.3.5.3.4 FU\_STATE\_REQ + +This packet is sent by the base node in order to get the firmware upgrade state of a service node. The service node will answer with FU\_STATE\_RSP. + +This packet contains the fields described below. + +**Table 10-15 – Fields of FU\_STATE\_REQ** + +| Field | Length | Description | +|----------|--------|------------------------------------| +| Type | 4 bits | 3 = FU_STATE_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | + +##### **10.3.5.3.5 FU\_KILL\_REQ** + +The base node sends this message to terminate the firmware upgrade process. A service node receiving this message will automatically switch to "Idle" state and optionally delete the downloaded data. The service node replies sending FU\_STATE\_RSP. + +The content of this packet is described below. + +**Table 10-16 – Fields of FU\_KILL\_REQ** + +| Field | Length | Description | +|----------|--------|------------------------------------| +| Type | 4 bits | 4 = FU_KILL_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | + +##### **10.3.5.3.6 FU\_STATE\_RSP** + +This packet is sent by the service node as an answer to FU\_STATE\_REQ, FU\_KILL\_REQ, FU\_EXEC\_REQ, FU\_CONFIRM\_REQ or FU\_INIT\_REQ messages received through the unicast connection. It is used to notify the firmware upgrade state in a service node. + +Additionally, FU\_STATE\_RSP is used as a default response to all events that happen in states where they are not foreseen (e.g., FU\_EXEC\_REQ in "Receiving" state, FU\_INIT\_REQ in "Upgrade"...). + +This packet contains the fields described below. + +**Table 10-17 – Fields of FU\_STATE\_RSP** + +| Field | Length | Description | +|----------|---------|-------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 5 = FU_STATE_RSP | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| State | 4 bits | 0 for idle
1 for receiving
2 for complete
3 for countdown
4 for upgrade
5 to 15 reserved by ITU-T. | +| Reserved | 4 bits | Reserved by ITU-T and set to 0. | +| CRC | 32 bits | CRC as the one received in the CRC field of FU_INIT_REQ. | +| Received | 32 bits | Number of received pages (this field should only be present if the state is "Receiving"). | + +##### 10.3.5.3.7 FU\_DATA + +This packet is sent by the base node to transfer a page of the firmware image to a service node. No answer is expected by the base node. + +This packet contains the fields described below. + +**Table 10-18 – Fields of FU\_DATA** + +| Field | Length | Description | +|-----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 6 = FU_DATA | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| PageIndex | 32 bits | Index of the page being transmitted | +| Reserved | 8 bits | Padding byte for 16-bit devices. Set to 0 by default. | +| Data | Variable | Data of the page
The length of this data is PageSize (32, 64, 128 or 192) bytes for every page, except the last one that will have the remaining bytes of the image. | + +##### 10.3.5.3.8 FU\_MISS\_REQ + +This packet is sent by the base node to a service node to request information about the pages that are still to be received. + +If the service node is in "*Receiving*" state it will answer with an FU\_MISS\_BITMAP or FU\_MISS\_LIST message. If the service node is in any other state it will answer with an FU\_STATE\_RSP. + +This packet contains the fields described below. + +**Table 10-19 – Fields of FU\_MISS\_REQ** + +| Field | Length | Description | +|-----------------|---------|----------------------------------------------------------| +| Type | 4 bits | 7 = FU_MISS_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| PageIndex | 32 bits | Starting point to gather information about missing pages | + +##### 10.3.5.3.9 FU\_MISS\_BITMAP + +This packet is sent by the service node as an answer to an FU\_MISS\_REQ. It carries the information about the pages that are still to be received. + +This packet will contain the fields described below. + +**Table 10-20 – Fields of FU\_MISS\_BITMAP** + +| Field | Length | Description | +|-----------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 8 = FU_MISS_BITMAP | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| PageIndex | 32 bits | Page index of the page represented by the first bit of the bitmap. It should be the same as the PageIndex field in FU_MISS_REQ messages, or a posterior one. If it is posterior, it means that the pages in between are already received. In this case, if all pages after the PageIndex specified in FU_MISS_REQ have been received, the service node shall start looking from the beginning ( PageIndex = 0). | +| Bitmap | Variable | This bitmap contains the information about the status of each page. The first bit (most significant bit of the first byte) represents the status of the page specified by PageIndex . The next bit represents the status of the PageIndex +1 and so on.
A '1' represents that a page is missing, a '0' represents that the page is already received.
After the bit that represents the last page in the image, it is allowed to overflow including bits that represent the missing status of the page with index zero.
The maximum length of this field is PageSize bytes. | + +It is up to the service node to decide to send this type of packet or an FU\_MISS\_LIST message. It is usually more efficient to transmit this kind of packet when the number of missing packets is not very low. But it is up to the implementation to transmit one type of packet or the other. The base node should understand both. + +##### 10.3.5.3.10 FU\_MISS\_LIST + +This packet is sent by the service node as an answer to an FU\_MISS\_REQ. It carries the information about the pages that are still to be received. + +This packet will contain the fields described below. + +**Table 10-21 – Fields of FU\_MISS\_LIST** + +| Field | Length | Description | +|-----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 9 = FU_MISS_LIST | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| PageIndexList | Variable | List of pages that are still to be received. Each page is represented by its PageIndex , coded as a 32 bit integer.
These pages should be sorted in ascending order (low to high), being possible to overflow to the PageIndex equal to zero to continue from the beginning.
The first page index should be the same as the PageIndex field in FU_MISS_REQ, or a posterior one. If it is posterior, it means that the pages in between are already received (by posterior it is allowed to overflow to the page index zero, to continue from the beginning).
The maximum length of this field is PageSize bytes. | + +It is up to the service node to decide to transmit this packet type or an FU\_MISS\_BITMAP message. It is usually more efficient to transmit this kind of packet when the missing packets are very sparse, but it is implementation-dependent to transmit one type of packet or the other. The base node should understand both. + +##### 10.3.5.3.11 FU\_INFO\_REQ + +This packet is sent by a base node to request information from a service node, such as manufacturer, device model, firmware version and other parameters specified by the manufacturer. The service node will answer with one or more FU\_INFO\_RSP packets. + +This packet contains the fields described below. + +**Table 10-22 – Fields of FU\_INFO\_REQ** + +| Field | Length | Description | +|-----------------|----------|------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 10 = FU_INFO_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| InfoIdList | Variable | List of identifiers with the information to retrieve
Each identifier is 1 byte long.
The maximum length of this field is 32 bytes. | + +The following identifiers are defined: + +**Table 10-23 – InfoId possible values** + +| InfoId | Name | Description | +|---------|------------------------------|------------------------------------------------| +| 0 | Manufacturer | Universal identifier of the manufacturer | +| 1 | Model | Model of the product working as service node | +| 2 | Firmware | Current firmware version being executed | +| 128-255 | Manufacturer specific | Range of values that are manufacturer specific | + +##### 10.3.5.3.12 FU\_INFO\_RSP + +This packet is sent by a service node as a response to an FU\_INFO\_REQ message from the base node. A service node may have to send more than one FU\_INFO\_RSP when replying to an information request by the base node. + +This packet contains the fields described below. + +**Table 10-24 – Fields of FU\_INFO\_RSP** + +| Field | Length | Description | +|-----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 11 = FU_INFO_RSP | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| InfoData | 0-192 bytes | Data with the information requested by the base node. It may contain several entries (one for each requested identifier), each entry has a maximum size of 32 bytes. The maximum size of this field is 192 bytes (6 entries). | + +The InfoData field can contain several entries, the format of each entry is specified below. + +**Table 10-25 – Fields of each entry of InfoData in FU\_INFO\_RSP** + +| Field | Length | Description | +|-----------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| InfoId | 8 bits | Identifier of the information as specified in 0 | +| Reserved | 3 bits | Reserved by ITU-T and set to 0. | +| Length | 5 bits | Length of the data field (If length is 0 it means that the specified InfoId is not supported by the specified device). | +| Data | 0-30 bytes | Data with the information provided by the service node.
Its content may depend on the meaning of the InfoId field. No value may be longer than 30 bytes. | + +##### **10.3.5.3.13 FU\_CRC\_REQ** + +FU\_CRC\_REQ is sent by the base node to command a service node to perform a CRC on the complete firmware image. The CRC on the complete FW image is mandatory. The CRC specified in FU\_CRC\_REQ.CRC is the same as in FU\_INIT\_REQ. + +The service node replies with FU\_CRC\_RSP if it is in "*Receiving*" state, in any other case it replies with FU\_STATE\_RSP. The base node shall not send an FU\_CRC\_REQ if the image download is not complete (that is, the bitmap is not complete). Should the base node have an abnormal behaviour and send FU\_CRC\_REQ before completing the FW download, the service node would reply with FU\_STATE\_RSP. + +Please note that in "*Idle*" state, the CRC field from FU\_STATE\_RSP will be a dummy (because no FU\_INIT\_REQ has been received yet). The base node will ignore this field if the service node is in "*Idle*" state. + +This packet contains the fields described below. + +**Table 10-26 – Fields of FU\_CRC\_REQ** + +| Field | Length | Description | +|-----------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type | 4 bits | 12 = FU_CRC_REQ | +| Version | 2 bits | 0 for this version of the protocol | +| Reserved | 2 bits | Reserved by ITU-T and set to 0. | +| SectionSize | 32 bits | Size of the firmware upgrade image in bytes | +| CRC | 32 bits | CRC of the firmware upgrade image
The input polynomial $M(x)$ is formed as a polynomial whose coefficients are bits of the data being checked (the first bit to check is the highest order coefficient and the last bit to check is the coefficient of order zero). The generator polynomial for the CRC is $G(x)=x^{32}+x^{26}+x^{23}+x^{22}+x^{16}+x^{12}+x^{11}+x^{10}+x^8+x^7+x^5+x^4+x^2+x+1$ . The remainder $R(x)$ is calculated as the remainder from the division of $M(x) \cdot x^{32}$ by $G(x)$ . The coefficients of the remainder will then be the resulting CRC. | + +##### **10.3.5.3.14 FU\_CRC\_RSP** + +This packet is sent by the service node as a response to an FU\_CRC\_REQ message sent by the base node. + +This packet contains the fields described below. + +**Table 10-27 – Fields of FU\_CRC\_RSP** + +| Field | Length | Description | +|-----------------|--------|---------------------------------------------------------| +| Type | 4 bits | 13 = FU_CRC_RSP | +| Version | 2 bits | 0 for this version of the protocol | +| CRC_Result | 1 bit | Result of the CRC:
"0" check failed
"1" check OK. | +| Reserved | 1 bit | Reserved by ITU-T and set to 0. | + +### 10.3.6 Examples + +The figures below are examples of the traffic generated between the base node and the service node during the firmware upgrade process. + +![Sequence diagram showing the interaction between a Base Node and Service Node A for firmware upgrade. The diagram illustrates the flow of messages: FU_INFO_REQ, FU_INFO_RSP, MUL_JOIN_B, MUL_JOIN_S, FU_INIT_REQ, INIT_RESP, FU_DATA, FU_MISS_REQ, FU_MISS_BITMAP, FU_MISS_LIST, FU_CRC_REQ, and FU_CRC_RSP. Service Node A's state transitions from IDLE to RECEIVING to COMPLETE are shown on the right.](4851479cde0f63d07f4db536c69bbdef_img.jpg) + +The diagram illustrates the sequence of operations between a Base Node and Service Node A for a firmware upgrade. The interaction is as follows: + +- Base Node** sends **FU\_INFO\_REQ** (with *InfoIdList = 0,1,2*) to **Service Node A**. The purpose is to "Get manufacturer, device model and firmware version". +- Service Node A** responds with **FU\_INFO\_RSP**. +- Base Node** sends **MUL\_JOIN\_B** to **Service Node A** to "Join multicast group". +- Service Node A** responds with **MUL\_JOIN\_S**. +- Base Node** sends **FU\_INIT\_REQ** to **Service Node A** to "Setup Node for Firmware Upgrade". +- Service Node A** responds with **INIT\_RESP**. +- Base Node** sends **FU\_DATA** to **Service Node A**. +- Service Node A** sends **FU\_MISS\_REQ** to **Base Node**. +- Base Node** responds with **FU\_MISS\_BITMAP**. +- Base Node** sends **FU\_DATA** to **Service Node A**. +- Service Node A** sends **FU\_MISS\_REQ** to **Base Node**. +- Base Node** responds with **FU\_MISS\_LIST**. +- Base Node** sends **FU\_CRC\_REQ** to **Service Node A** to verify the "CRC of the complete image ok". +- Service Node A** responds with **FU\_CRC\_RSP**. + +On the right side, the state of **Service Node A** is shown: + +- Initial state: **IDLE** (red line). +- Transition to **RECEIVING** state (purple line) after **FU\_INIT\_REQ**. +- Transition to **COMPLETE** state (orange line) after **FU\_CRC\_RSP**. + +Sequence diagram showing the interaction between a Base Node and Service Node A for firmware upgrade. The diagram illustrates the flow of messages: FU\_INFO\_REQ, FU\_INFO\_RSP, MUL\_JOIN\_B, MUL\_JOIN\_S, FU\_INIT\_REQ, INIT\_RESP, FU\_DATA, FU\_MISS\_REQ, FU\_MISS\_BITMAP, FU\_MISS\_LIST, FU\_CRC\_REQ, and FU\_CRC\_RSP. Service Node A's state transitions from IDLE to RECEIVING to COMPLETE are shown on the right. + +**Figure 10-4 – Init service node and complete FW image** + +Figure 10-4 shows the initialization of the process, the FW download and the integrity check of the image. In the example above, the downloaded FW image is supposed to be complete before sending the last FU\_MISS\_REQ. The base node sends it to verify its bitmap. In this example, FU\_MISS\_LIST has an empty *PageIndexList* field, which means that the FW image is complete. + +![Sequence diagrams for Delayed and Immediate Firmware restart. Both show interactions between Base Node and Service Node A. The Delayed restart path includes MUL_LEAVE_B, MUL_LEAVE_S, FU_EXEC_REQ (RestartTimer != 0), FU_STATE_RSP, FU_CONFIRM_REQ (new FW confirmed!!), and FU_STATE_RSP. The Immediate restart path includes MUL_LEAVE_B, MUL_LEAVE_S, FU_EXEC_REQ (RestartTimer = 0), FU_STATE_RSP, FU_KILL_REQ (new FW rejected!!), and FU_STATE_RSP. State transitions for Service Node A are shown on the right: COMPLETE, COUNTDOWN, UPGRADE, and IDLE.](7e1f88e0cc7be8060240e12252a833d1_img.jpg) + +The diagram illustrates two sequence interactions between a Base Node and Service Node A for firmware updates. + +**Delayed Firmware restart:** + +- Base Node sends **MUL\_LEAVE\_B** to Service Node A. +- Service Node A responds with **MUL\_LEAVE\_S**. +- Base Node sends **FU\_EXEC\_REQ** (RestartTimer != 0) to Service Node A. +- Service Node A responds with **FU\_STATE\_RSP**. +- Service Node A transitions through state **COUNTDOWN** (indicated by a vertical line and a crossed-out timer symbol). +- Base Node sends **FU\_CONFIRM\_REQ** (new FW confirmed!!) to Service Node A. +- Service Node A responds with **FU\_STATE\_RSP**. +- Service Node A transitions through state **UPGRADE** (indicated by a vertical line and a timer symbol). +- Service Node A reaches state **IDLE**. + +**Immediate Firmware restart:** + +- Base Node sends **MUL\_LEAVE\_B** to Service Node A. +- Service Node A responds with **MUL\_LEAVE\_S**. +- Base Node sends **FU\_EXEC\_REQ** (RestartTimer = 0) to Service Node A. +- Service Node A responds with **FU\_STATE\_RSP**. +- Service Node A transitions through state **UPGRADE** (indicated by a vertical line and a timer symbol). +- Service Node A reaches state **IDLE**. + +Vertical state lines on the right indicate the Service Node A (SN) state transitions: **COMPLETE** (orange), **COUNTDOWN** (pink), **UPGRADE** (blue), and **IDLE** (red). + +Sequence diagrams for Delayed and Immediate Firmware restart. Both show interactions between Base Node and Service Node A. The Delayed restart path includes MUL\_LEAVE\_B, MUL\_LEAVE\_S, FU\_EXEC\_REQ (RestartTimer != 0), FU\_STATE\_RSP, FU\_CONFIRM\_REQ (new FW confirmed!!), and FU\_STATE\_RSP. The Immediate restart path includes MUL\_LEAVE\_B, MUL\_LEAVE\_S, FU\_EXEC\_REQ (RestartTimer = 0), FU\_STATE\_RSP, FU\_KILL\_REQ (new FW rejected!!), and FU\_STATE\_RSP. State transitions for Service Node A are shown on the right: COMPLETE, COUNTDOWN, UPGRADE, and IDLE. + +**Figure 10-5 – Execute upgrade and confirm/reject new FW version** + +Figure 10-5 shows how to proceed after completing the FW download. The base node commands the service node to reboot either immediately ("Immediate Firmware Start", *RestartTimer* = 0) or after a defined period of time ("Delayed Firmware start", *RestartTimer* != 0). After reboot, the base node can either confirm the recently downloaded message sending an **FU\_CONFIRM\_REQ** or reject it (sending an **FU\_KILL\_REQ** or letting the safety period expire by doing nothing). + +## 10.4 Management interface description + +### 10.4.1 General + +Management functions defined in earlier clauses shall be available over an abstract management interface specified in this clause. The management interface can be accessed over diverse media. Each physical media shall specify its own management plane communication profile over which management information is exchanged. It is mandatory for implementations to support the ITU-T G.9904 management plane communication profile. All other "management plane communication profiles" are optional and may be mandated by certain "application profiles" to use in specific cases. + +This Recommendation describes two communication profiles, one of which is over this specification's NULL SSCS and the other over a serial link. + +With these two communication profiles, it shall be possible to address the following use-cases: + +1. Remote access of management interface over NULL SSCS. This shall enable base node's use as a supervisory gateway for all devices in a subnetwork. +2. Local access of management interface (over peripherals like RS232, USBSerial etc.) in a service node. Local access shall fulfil cases where a co-processor exists for supervisory control of the processor or when manual access is required over the local physical interface for maintenance. + +Management data comprises of a 2 byte header followed by payload information corresponding to the type of information carried in the message. The header comprises of a 10 bit length field and a 6 bit message\_id field. + +![Diagram of Management data frame format showing a 10-bit LEN field, a 6-bit TYPE field, and a variable-length Payload.](909e1cd5419742a8ea8a95a16a40d849_img.jpg) + +The diagram illustrates the structure of a management data frame. It consists of three fields: LEN (10 bits), TYPE (6 bits), and Payload ('LEN' Bytes). The LEN and TYPE fields are part of a 2-byte header, while the Payload is the variable-length data following the header. + +| | | | | | | +|---------|--|--------|--|-------------|--| +| 10 bits | | 6 bits | | 'LEN' Bytes | | +| LEN | | TYPE | | Payload | | + +Diagram of Management data frame format showing a 10-bit LEN field, a 6-bit TYPE field, and a variable-length Payload. + +**Figure 10-6 – Management data frame format** + +**Table 10-28 – Management data frame fields** + +| Name | Length | Description | +|-----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MGMT.LEN | 10 bits | Length of payload data following the 2 byte header.
LEN=0 implies there is no payload data following this header and the TYPE field contains all required information to perform appropriate action.
NOTE – The length field may be redundant in some communication profiles (e.g., when transmitted over ITU-T G.9904), but it is required in others. Therefore for the sake of uniformity, it is always included in management data. | +| MGMT.TYPE | 6 bits | Type of management information carried in corresponding data. Some message_ids have standard semantics which should be respected by all ITU-T G.9904 compliant devices while others are reserved for local use by vendors.
0x00 – Get PIB attribute query
0x01 – Get PIB attribute response
0x02 – Set PIB attribute command
0x03 – Reset all PIB statistics attributes
0x04 – Reboot destination device
0x05 – Firmware upgrade protocol message
0x06 – 0x0F: Reserved by ITU-T. Vendors should not use these values for local purposes.
0x10 – 0x3F: Reserved for vendor-specific use | + +### 10.4.2 Payload format of management information + +#### 10.4.2.1 Get PIB attribute query + +This query is issued by a remote management entity that is interested in knowing the values of PIB attributes maintained on a compliant device with this Recommendation. + +The payload may comprise of a query on either a single PIB attribute or multiple attributes. For reasons of efficiency queries on multiple PIB attributes may be aggregated in one single command. + +Given that the length of a PIB attribute identifier is constant, the number of attributes requested in a single command is derived from the overall MGMT.LEN field in the header. + +The format of payload information is shown in the following figure. + +![Figure 10-7: Get PIB attribute query load diagram.](b43ec8e53bbe827c4572d9fd80ebc21a_img.jpg) + +The diagram shows a sequence of fields representing a query load. It starts with 'PIB attribute 1' (2 bytes) followed by 'index' (1 byte). This is followed by 'PIB attribute 2' (2 bytes) and 'index' (1 byte). A dashed line indicates repetition, ending with 'PIB attribute ‘n’' (2 bytes) and 'index' (1 byte). Above each field, the length is indicated: 2 bytes for attributes and 1 byte for indices. + +Figure 10-7: Get PIB attribute query load diagram. + +**Figure 10-7 – Get PIB attribute query load** + +Fields of a GET request are summarized in the table below: + +**Table 10-29 – GET PIB attribute request fields** + +| Name | Length | Description | +|------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PIB attribute ID | 2 bytes | 16 bit PIB attribute identifier | +| Index | 1 byte | Index of entry to be returned for corresponding PIB attributeIDs. This field is only of relevance while returning PIB list attributes.
Index = 0; if PIB attribute is not a list
Index = 1 to 255; return list record at given index | + +#### 10.4.2.2 Get PIB attribute response + +This data is sent out from a compliant device of this Recommendation in response to a query of one or more PIB attributes. If a certain queried PIB attribute is not maintained on the device, it shall still respond to the query with a value field containing all-ones in the response. + +The format of the payload is shown in the following figure. + +![Figure 10-8: Get PIB attribute response payload diagram.](9507bf8a743ef8e70785692053d75e7c_img.jpg) + +The diagram shows the structure of a response payload. It consists of 'PIB attribute 1' (2 bytes), followed by 'index' (1 byte), then 'PIB attribute 1 “value”' (2 bytes), and finally a 'next' field (1 byte). Lengths are indicated above each field. + +Figure 10-8: Get PIB attribute response payload diagram. + +**Figure 10-8 – Get PIB attribute response payload** + +Fields of a GET request are summarized in table below: + +**Table 10-30 – GET PIB attribute response fields** + +| Name | Length | Description | +|---------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PIB attribute ID | 2 bytes | 16 bit PIB attribute identifier | +| Index | 1 byte | Index of entry returned for corresponding PIB attributeIDs. This field is only of relevance while returning PIB list attributes.
Index = 0; if PIB attribute is not a list
Index = 1 to 255; returned list record is at given index | +| PIB attribute value | 'a' bytes | Values of requested PIB attributes. In the case of a list attribute, the value shall comprise of an entire record corresponding to a given index of PIB attributes. | + +**Table 10-30 – GET PIB attribute response fields** + +| Name | Length | Description | +|------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Next | 1 byte | Index of next entry returned for corresponding PIB AttributeIDs. This field is only of relevance while returning PIB list attributes.
Next = 0; if PIB attribute is not a list or if no records follow the one being returned for a list PIB attribute, i.e., given record is last entry in list.
Next = 1 to 255; index of next record in list maintained for given PIB attribute. | + +Response to a PIB attribute query can span across several MAC GPDUs. This shall always be the case when an aggregated (comprising of several PIB attributes) PIB query's response if longer than the maximum segment size is allowed to be carried over the NULL SCSS. + +#### 10.4.2.3 Set PIB attribute + +This management data shall be used to set specific PIB attributes. Such management payload comprises of a 2 byte PIB attribute identifier, followed by the relevant length of PIB attribute information corresponding to that identifier. For reasons of efficiency, it shall be possible to aggregate a SET command on several PIB attributes in one GPDU. The format of such an aggregated payload is shown in Figure 10-9 below: + +![Figure 10-9 – Set PIB attribute query payload diagram](e33485d4301404e5a43a61e4cfb96fcc_img.jpg) + +The diagram shows the structure of an aggregated SET command payload. It consists of repeating blocks of attribute identifiers and values: + +| | | | | | | | | | +|-----------------|--|--------------------------------|--|-----|-------------------|--|----------------------------------|--| +| 2 bytes | | 'a' bytes | | | 2 bytes | | 'a' bytes | | +| PIB attribute 1 | | PIB attribute 1 "value" | | ... | PIB attribute 'n' | | PIB attribute 'n' "value" | | + +Figure 10-9 – Set PIB attribute query payload diagram + +**Figure 10-9 – Set PIB attribute query payload** + +For cases where the corresponding PIB attribute is only a trigger (all ACTION PIB attributes), there shall be no associated value and the request data format shall be as shown below: + +![Figure 10-10 – Set PIB attribute response payload diagram](b2448ec0a23090beb4402121beeff751_img.jpg) + +The diagram shows the structure for ACTION PIB attributes, consisting only of identifiers: + +| | | | | +|-----------------|-----------------|-----|-------------------| +| 2 bytes | 2 bytes | | 2 bytes | +| PIB attribute 1 | PIB attribute 2 | ... | PIB attribute 'n' | + +Figure 10-10 – Set PIB attribute response payload diagram + +**Figure 10-10 – Set PIB attribute response payload** + +It is assumed that the management entity sending out this information has already determined if the corresponding attributes are supported at the target device. This may be achieved by a previous query and its response. + +#### 10.4.2.4 Reset statistics + +This command has optional payload. In case there is no associated payload, the receiving device shall reset all of its PIB statistical attributes. + +For cases when a remote management entity only intends to perform the reset of selective PIB statistical attributes, the payload shall contain a list of attributes that need to be reset. The format shall be the same as shown in clause 10.4.2.1. + +Since there is no confirmation message going back from the device complying with this Recommendation, the management entity needs to send a follow-up PIB attribute query, in case it wants to confirm the successful completion of appropriate action. + +#### 10.4.2.5 Reboot device + +There is no corresponding payload associated with this command. The command is complete in itself. The receiving compliant device with this Recommendation shall reboot itself upon receipt of this message. + +It is mandatory for all implementations compliant with this Recommendation to support this command and its corresponding action. + +#### 10.4.2.6 Firmware upgrade + +The payload in this case shall comprise of firmware upgrade commands and responses described in clause 10.3 of the Recommendation. + +### 10.4.3 NULL SSCS communication profile + +This communication profile enables the exchange of management information described in previous clauses over the NULL SSCS. + +The management entities at both transmitting and receiving ends are applications making use of the NULL SSCS enumerated in clause 9.3 of this Recommendation. Data is therefore exchanged as MAC generic PDUs. + +### 10.4.4 Serial communication profile + +#### 10.4.4.1 Physical layer + +The PHY layer may be any serial link (e.g., RS232, USB Serial). The serial link is required to work 8N1 configuration at one of the following data rates: + +9600 bps, 19200 bps, 38400 bps, 57600 bps + +#### 10.4.4.2 Data encapsulation for management messages + +In order to ensure robustness, the stream of data is encapsulated in HDLC-type frames which include a 2 byte header and a 4 byte CRC. All data is encapsulated between a starting flag-byte 0x7E and an ending flag-byte 0x7E as shown in Figure 10-11 below: + +![Diagram of data encapsulation for management messages showing a frame structure with fields: Flag (1 byte), Header (2 bytes), Payload ('n' bytes), CRC (4 bytes), and Flag (1 byte).](2fbbd361d3aff2374a19eb4fe03983bd_img.jpg) + +| | | | | | +|--------|---------|-----------|---------|--------| +| 1 byte | 2 bytes | 'n' bytes | 4 bytes | 1 byte | +| 7E | Header | Payload | CRC | 7E | + +Diagram of data encapsulation for management messages showing a frame structure with fields: Flag (1 byte), Header (2 bytes), Payload ('n' bytes), CRC (4 bytes), and Flag (1 byte). + +Figure 10-11 – Data encapsulation for management messages + +If any of the intermediate data characters has the value 0x7E, it is preceded by an escape byte 0x7D, followed by a byte derived from XORing the original character with byte 0x20. The same is done if there is a 0x7D within the character stream. An example of such a case is shown here: + +``` +Msg to Tx: 0x01 0x02 0x7E 0x03 0x04 0x7D 0x05 0x06 +Actual Tx sequence: 0x01 0x02 0x7D 0x5E 0x03 0x04 0x7D 0x5D 0x05 0x06 + Escape Escape + sequence sequence +``` + +The 32 bit CRC at the end of the frame covers both 'Header' and 'Payload' fields. The CRC is calculated over the original data to be transmitted, i.e., before byte stuffing of the escape sequences described above is performed. The CRC calculation is as follows: + +The input polynomial $M(x)$ is formed as a polynomial whose coefficients are bits of the data being checked (the first bit to check is the highest order coefficient and the last bit to check is the coefficient of order zero). The generator polynomial for the CRC is $G(x)=x^{32}+x^{26}+x^{23}+x^{22}+x^{16}+x^{12}+x^{11}+x^{10}+x^8+x^7+x^5+x^4+x^2+x+1$ . The remainder $R(x)$ is calculated as the remainder from the division of $M(x)\cdot x^{32}$ by $G(x)$ . The coefficients of the remainder will then be the resulting CRC. + +## 10.5 List of mandatory PIB attributes + +### 10.5.1 General + +PIB attributes listed in this clause shall be supported by all implementations. PIB attributes that are not listed in this clause are optional and vendors may implement them at their choice. In addition to the PIB attributes, the management command to reboot a certain device (as specified in clause 10.4.2.5) shall also be universally supported. + +### 10.5.2 Mandatory PIB attributes common to all device types + +#### 10.5.2.1 PHY PIB attribute + +(See Table 10-1.) + +**Table 10-31 – PHY PIB common mandatory attributes** + +| Attribute name | Id | +|----------------------|--------| +| phyStatsRxTotalCount | 0x00A4 | +| phyStatsBlkAvgEvm | 0x00A5 | +| phyEmaSmoothing | 0x00A8 | + +#### 10.5.2.2 MAC PIB attributes + +(See Tables 10-3, 10-5 and 10-7.) + +**Table 10-32 – MAC PIB common mandatory attributes** + +| Attribute name | Id | +|-----------------|--------| +| macEMASmoothing | 0x0019 | +| macCapabilities | 0x002C | +| macListPhyComm | 0x0057 | + +#### 10.5.2.3 Application PIB attributes + +(See Table 10-9.) + +**Table 10-33 – Applications PIB common mandatory attributes** + +| Attribute name | Id | +|----------------|--------| +| appFwVersion | 0x0075 | +| appVendorId | 0x0076 | +| appProductId | 0x0077 | + +### 10.5.3 Mandatory base node attributes + +#### 10.5.3.1 MAC PIB attributes + +(See Tables 10-3 and 10-7.) + +**Table 10-34 – MAC PIB base node mandatory attributes** + +| Attribute name | Id | +|--------------------|--------| +| macBeaconsPerFrame | 0x0013 | +| macListRegDevices | 0x0050 | +| macListActiveConn | 0x0051 | + +### 10.5.4 Mandatory service node attributes + +#### 10.5.4.1 MAC PIB attributes + +(See Tables 10-5, 10-7 and 10-8.) + +**Table 10-35 – MAC PIB service node mandatory attributes** + +| Attribute name | Id | +|--------------------------|--------| +| macLNID | 0x0020 | +| macLSID | 0x0021 | +| macSID | 0x0022 | +| macSNA | 0x0023 | +| macState | 0x0024 | +| macSCPLength | 0x0025 | +| macNodeHierarchyLevel | 0x0026 | +| macBeaconSlotCount | 0x0027 | +| macBeaconRxSlot | 0x0028 | +| macBeaconTxSlot | 0x0029 | +| macBeaconRxFrequency | 0x002A | +| macBeaconTxFrequency | 0x002B | +| macListSwitchTable | 0x0053 | +| macListAvailableSwitches | 0x0056 | +| MACActionTxData | 0x0060 | +| MACActionConnClose | 0x0061 | +| MACActionRegReject | 0x0062 | +| MACActionProReject | 0x0063 | +| MACActionUnregister | 0x0064 | + +#### 10.5.4.2 Application PIB attributes + +(See Table 10-10.) + +**Table 10-36 – APP PIB service node mandatory attributes** + +| Attribute name | Id | +|-----------------------|-----------| +| appFwdllRunning | 0x0070 | +| appFwdllRxPktCount | 0x0071 | + +# Annex A + +## EVM and SNR calculation + +(This annex forms an integral part of this Recommendation.) + +This annex describes calculations of the EVM by a reference receiver, assuming accurate synchronization and FFT window placement. + +Let + +$\{r_k^i; k = 1, 2, \dots, 97\}$ denotes that the FFT output for symbol $i$ and $k$ are the frequency tones. + +$\Delta b_k \in \{0, 1, \dots, M-1\}$ represents the decision on the received information symbol coded in the phase increment. + +$M = 2, 4$ or $8$ in the case of DBPSK, DQPSK or D8PSK, respectively. + +The EVM definition is then given by; + +$$EVM = \frac{\sum_{i=1}^L \sum_{k=2}^{97} \left[ \text{abs} \left( r_k^i - r_{k-1}^i e^{-\left(\frac{j2\pi}{M}\right)\Delta b_{k-1}} \right) \right]^2}{\sum_{i=1}^L \sum_{k=2}^{97} [\text{abs}(r_k^i)]^2}$$ + +In the above, $\text{abs}(\cdot)$ refers to the magnitude of a complex number. $L$ is the number of OFDM symbols in the payload of the most recently received PPDU, over which the EVM is calculated. + +The SNR is then defined as the reciprocal of the EVM above. + +# Annex B + +## MAC layer constants + +(This annex forms an integral part of this Recommendation.) + +This clause defines all the MAC layer constants. + +**Table B.1 – Table of MAC constants** + +| Constant | Value | Description | +|--------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| MACBeaconLength | 4 symbols | Length of beacon in symbols | +| MACMinSCPLength | 64 symbols | Minimum length of SCP | +| MACPriorityLevels | 4 | Number of levels of priority supported by the system | +| MACCFPMaxAlloc | 32 | Maximum contention-free periods that may be allocated within a frame | +| MACFrameLength | 276 symbols | Length of a frame in number of symbols | +| MACRandSeqChgTime | 32767 seconds
(approx 9 hours) | Maximum duration of time after which the base node should circulate a new random sequence to the subnetwork for encryption functions. | +| MACMaxPRNIgnore | 3 | Maximum number of promotion-needed messages a terminal can ignore. | +| N miss-beacon | 5 | Number of times a service node does not receive an expected beacon before considering its switch node as unavailable. | +| ARQMaxTxCount | 5 | Maximum transmission count before declaring a permanent failure. | +| ARQCongClrTime | 2 sec | When the receiver has indicated congestion, this time must be waited before retransmitting the data. | +| ARQMaxCongInd | 7 | After ARQMaxCongInd consecutive transmissions which failed due to congestion, the connection should be declared permanently dead. | +| ARQMaxAckHoldTime | 7 sec | Time the receiver may delay sending an ACK in order to allow consolidated ACKs or piggyback the ACK with a data packet. | + +# Annex C + +## Convergence layer constants + +(This annex forms an integral part of this Recommendation.) + +The following TYPE values are defined for use by the convergence layers from clause 9. + +**Table C.1 – TYPE value assignments** + +| TYPE symbolic name | Value | +|----------------------|-------| +| TYPE_CL_IPv4_AR | 1 | +| TYPE_CL_IPv4_UNICAST | 2 | +| TYPE_CL_432 | 3 | +| TYPE_CL_MGMT | 4 | +| TYPE_CL_IPv6_AR | 5 | +| TYPE_CL_IPv6_UNICAST | 6 | + +The following LCID values apply for broadcast connections defined by the convergence layers from clause 9. + +**Table C.2 – LCID value assignments** + +| LCID Symbolic Name | Value | MAC scope | +|-----------------------|-------|------------| +| LCI_CL_IPv4_BROADCAST | 1 | Broadcast. | +| LCI_CL_432_BROADCAST | 2 | Broadcast. | + +The following result values are defined for convergence layer primitives. + +**Table C.3 – Result values for convergence layer primitives** + +| Result | Description | +|--------------------|-------------------------------------------------------------------| +| Success = 0 | The SSCS service was successfully performed. | +| Reject = 1 | The SSCS service failed because it was rejected by the base node. | +| Timeout = 2 | A timed out occurs during the SSCS service processing. | +| Not Registered = 6 | The service node is not currently registered to a subnetwork. | + +# Appendix I + +## Examples of CRC + +(This appendix does not form an integral part of this Recommendation.) + +The table below gives the CRCs calculated for several specified strings. + +**Table I.1 – Examples of CRCs calculated +for various ASCII strings** + +| String | CRC-8 | +|---------------|--------------| +| 'T' | 0xab | +| "THE" | 0xa0 | +| 0x03, 0x73 | 0x61 | +| 0x01, 0x3f | 0xa8 | +| "123456789" | 0xf4 | + +# Appendix II + +## Interleaving matrices + +(This appendix does not form an integral part of this Recommendation.) + +Header interleaving matrix: + +| | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----| +| 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | +| 36 | 35 | 34 | 33 | 32 | 31 | 30 | 29 | 28 | 27 | 26 | 25 | +| 48 | 47 | 46 | 45 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | +| 60 | 59 | 58 | 57 | 56 | 55 | 54 | 53 | 52 | 51 | 50 | 49 | +| 72 | 71 | 70 | 69 | 68 | 67 | 66 | 65 | 64 | 63 | 62 | 61 | +| 84 | 83 | 82 | 81 | 80 | 79 | 78 | 77 | 76 | 75 | 74 | 73 | + +DBPSK (FEC ON) interleaving matrix: + +| | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----| +| 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | +| 36 | 35 | 34 | 33 | 32 | 31 | 30 | 29 | 28 | 27 | 26 | 25 | +| 48 | 47 | 46 | 45 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | +| 60 | 59 | 58 | 57 | 56 | 55 | 54 | 53 | 52 | 51 | 50 | 49 | +| 72 | 71 | 70 | 69 | 68 | 67 | 66 | 65 | 64 | 63 | 62 | 61 | +| 84 | 83 | 82 | 81 | 80 | 79 | 78 | 77 | 76 | 75 | 74 | 73 | +| 96 | 95 | 94 | 93 | 92 | 91 | 90 | 89 | 88 | 87 | 86 | 85 | + +DQPSK (FEC ON) interleaving matrix: + +| | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | +| 36 | 35 | 34 | 33 | 32 | 31 | 30 | 29 | 28 | 27 | 26 | 25 | +| 48 | 47 | 46 | 45 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | +| 60 | 59 | 58 | 57 | 56 | 55 | 54 | 53 | 52 | 51 | 50 | 49 | +| 72 | 71 | 70 | 69 | 68 | 67 | 66 | 65 | 64 | 63 | 62 | 61 | +| 84 | 83 | 82 | 81 | 80 | 79 | 78 | 77 | 76 | 75 | 74 | 73 | +| 96 | 95 | 94 | 93 | 92 | 91 | 90 | 89 | 88 | 87 | 86 | 85 | +| 108 | 107 | 106 | 105 | 104 | 103 | 102 | 101 | 100 | 99 | 98 | 97 | +| 120 | 119 | 118 | 117 | 116 | 115 | 114 | 113 | 112 | 111 | 110 | 109 | +| 132 | 131 | 130 | 129 | 128 | 127 | 126 | 125 | 124 | 123 | 122 | 121 | +| 144 | 143 | 142 | 141 | 140 | 139 | 138 | 137 | 136 | 135 | 134 | 133 | +| 156 | 155 | 154 | 153 | 152 | 151 | 150 | 149 | 148 | 147 | 146 | 145 | +| 168 | 167 | 166 | 165 | 164 | 163 | 162 | 161 | 160 | 159 | 158 | 157 | +| 180 | 179 | 178 | 177 | 176 | 175 | 174 | 173 | 172 | 171 | 170 | 169 | +| 192 | 191 | 190 | 189 | 188 | 187 | 186 | 185 | 184 | 183 | 182 | 181 | + +D8PSK (FEC ON) interleaving matrix: + +| | | | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +| 36 | 35 | 34 | 33 | 32 | 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | +| 54 | 53 | 52 | 51 | 50 | 49 | 48 | 47 | 46 | 45 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | +| 72 | 71 | 70 | 69 | 68 | 67 | 66 | 65 | 64 | 63 | 62 | 61 | 60 | 59 | 58 | 57 | 56 | 55 | +| 90 | 89 | 88 | 87 | 86 | 85 | 84 | 83 | 82 | 81 | 80 | 79 | 78 | 77 | 76 | 75 | 74 | 73 | +| 108 | 107 | 106 | 105 | 104 | 103 | 102 | 101 | 100 | 99 | 98 | 97 | 96 | 95 | 94 | 93 | 92 | 91 | +| 126 | 125 | 124 | 123 | 122 | 121 | 120 | 119 | 118 | 117 | 116 | 115 | 114 | 113 | 112 | 111 | 110 | 109 | +| 144 | 143 | 142 | 141 | 140 | 139 | 138 | 137 | 136 | 135 | 134 | 133 | 132 | 131 | 130 | 129 | 128 | 127 | +| 162 | 161 | 160 | 159 | 158 | 157 | 156 | 155 | 154 | 153 | 152 | 151 | 150 | 149 | 148 | 147 | 146 | 145 | +| 180 | 179 | 178 | 177 | 176 | 175 | 174 | 173 | 172 | 171 | 170 | 169 | 168 | 167 | 166 | 165 | 164 | 163 | +| 198 | 197 | 196 | 195 | 194 | 193 | 192 | 191 | 190 | 189 | 188 | 187 | 186 | 185 | 184 | 183 | 182 | 181 | +| 216 | 215 | 214 | 213 | 212 | 211 | 210 | 209 | 208 | 207 | 206 | 205 | 204 | 203 | 202 | 201 | 200 | 199 | +| 234 | 233 | 232 | 231 | 230 | 229 | 228 | 227 | 226 | 225 | 224 | 223 | 222 | 221 | 220 | 219 | 218 | 217 | +| 252 | 251 | 250 | 249 | 248 | 247 | 246 | 245 | 244 | 243 | 242 | 241 | 240 | 239 | 238 | 237 | 236 | 235 | +| 270 | 269 | 268 | 267 | 266 | 265 | 264 | 263 | 262 | 261 | 260 | 259 | 258 | 257 | 256 | 255 | 254 | 253 | +| 288 | 287 | 286 | 285 | 284 | 283 | 282 | 281 | 280 | 279 | 278 | 277 | 276 | 275 | 274 | 273 | 272 | 271 | + + + +# 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.991.2-200312-I_PDF-E/raw.md b/marked/G/T-REC-G.991.2-200312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1f4c3dd18d299893b909189c65fc1f91dbf09de0 --- /dev/null +++ b/marked/G/T-REC-G.991.2-200312-I_PDF-E/raw.md @@ -0,0 +1,7268 @@ + + +![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.991.2** + +(12/2003) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital sections and digital line system – Access networks + +--- + +**Single-pair high-speed digital subscriber line +(SHDSL) transceivers** + +ITU-T Recommendation G.991.2 + +--- + +# ITU-T G-SERIES RECOMMENDATIONS **TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100–G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200–G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300–G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400–G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450–G.499 | +| TESTING EQUIPMENTS | G.500–G.599 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.600–G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700–G.799 | +| DIGITAL NETWORKS | G.800–G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900–G.999 | +| 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 | +| 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.* + +## Single-pair high-speed digital subscriber line (SHDSL) transceivers + +## Summary + +This Recommendation describes a transmission method for data transport in telecommunications access networks. SHDSL transceivers are designed primarily for duplex operation over mixed gauge two-wire twisted metallic pairs. Optional multi-pair operation is supported for extended reach applications. Optional signal regenerators for both single-pair and multi-pair operation are specified, as well. SHDSL transceivers are capable of supporting selected symmetric user data rates in the range of 192 kbit/s to 2312 kbit/s using a Trellis Coded Pulse Amplitude Modulation (TCPAM) line code. Optional extensions described in Annex F allow user data rates up to 5696 kbit/s. SHDSL transceivers are designed to be spectrally compatible with other transmission technologies deployed in the access network, including other DSL technologies. SHDSL transceivers do not support the use of analogue splitting technology for coexistence with either POTS or ISDN. Regional requirements, including both operational differences and performance requirements, are specified in Annexes A, B and C. Requirements for signal regenerators are specified in Annex D. Annex E describes application-specific framing modes that may be supported by SHDSL transceivers. + +See Annex H/G.992.1 [1] for specifications of transceivers for use in networks with existing TCM-ISDN service (as specified in Appendix III/G.961, in Bibliography [B1]). + +## History + +With respect to the previous version 1 (2001), this version 2 introduces the following additions and modifications: + +- The optional four-wire mode has been extended to a more general multi-pair mode which provides optional support for up to four-pair connections. See 7.2.1.5. Note that the integrity of the optional 4-wire mode in revision 1 is preserved. The four-wire mode is identical to *M*-pair mode with *M* = 2, except for the method of assigning ordinal numbers to the wire pairs. In four-wire mode, the ordinal numbers (the wire pair identification number) are assigned as described in 6.3, while in *M*-pair mode the ordinal numbers are assigned to wire pairs as described in 7.2.1.5. +- The loops and test conditions specified in Annex B have been updated (see B.3.3), and Appendix IV, Tabulation of Annex B Noise Profiles, has been added. +- Optional extensions, described in Annex F, allow user data rates up to 5696 kbit/s. +- Deactivation and warm-start, as specified in Annex H, have been added. +- Support for Dynamic Rate Repartitioning has been added to Dual-Bearer mode. See E.10.3. +- TPS-TC definitions have been added for Packet Transfer Mode (E.11), Synchronous Transfer Mode with a Dedicated Signalling Channel (E.12), and V5 Encapsulated ISDN or POTS (E.13). + +## Source + +ITU-T Recommendation G.991.2 was approved on 14 December 2003 by ITU-T Study Group 15 (2001-2004) under the ITU-T Recommendation A.8 procedure. + +# FOREWORD + +The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. + +The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. + +Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. + +## INTELLECTUAL PROPERTY RIGHTS + +ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. + +As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2004 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +# CONTENTS + +| | | Page | +|------|------------------------------------------------|------| +| 1 | Scope ..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions and abbreviations ..... | 2 | +| 3.1 | Definitions ..... | 2 | +| 3.2 | Abbreviations ..... | 3 | +| 4 | Reference models..... | 6 | +| 4.1 | STU-x functional model ..... | 6 | +| 4.2 | User plane protocol reference model..... | 7 | +| 4.3 | Application models..... | 7 | +| 5 | Transport capacity ..... | 8 | +| 6 | PMD layer functional characteristics..... | 8 | +| 6.1 | Data mode operation..... | 8 | +| 6.2 | PMD activation sequence ..... | 12 | +| 6.3 | PMD pre-activation sequence..... | 16 | +| 6.4 | G.994.1 pre-activation sequence ..... | 20 | +| 7 | PMS-TC layer functional characteristics..... | 23 | +| 7.1 | Data mode operation..... | 23 | +| 7.2 | PMS-TC activation..... | 28 | +| 8 | TPS-TC layer functional characteristics..... | 30 | +| 8.1 | Payload block data structure..... | 30 | +| 8.2 | Data interleaving in M -pair mode..... | 31 | +| 9 | Management ..... | 32 | +| 9.1 | Management reference model ..... | 32 | +| 9.2 | SHDSL performance primitives ..... | 33 | +| 9.3 | SHDSL line related performance parameters..... | 34 | +| 9.4 | Performance data storage ..... | 35 | +| 9.5 | Embedded operations channel ..... | 35 | +| 10 | Clock architecture ..... | 58 | +| 10.1 | Reference clock architecture ..... | 58 | +| 10.2 | Clock accuracy ..... | 59 | +| 10.3 | Definitions of clock sources ..... | 60 | +| 10.4 | Synchronization to clock sources ..... | 60 | +| 11 | Electrical characteristics ..... | 60 | +| 11.1 | Longitudinal balance ..... | 61 | +| 11.2 | Longitudinal output voltage ..... | 62 | +| 11.3 | Return loss ..... | 62 | +| 11.4 | Transmit power testing ..... | 64 | + +| | Page | +|-------------------------------------------------------------------------------------------------------------|------| +| 11.5 Signal transfer delay ..... | 65 | +| 12 Conformance testing..... | 66 | +| 12.1 Micro-interruptions..... | 66 | +| Annex A – Regional requirements – Region 1 ..... | 67 | +| A.1 Scope ..... | 67 | +| A.2 Test loops..... | 67 | +| A.3 Performance Tests ..... | 68 | +| A.4 PSD masks..... | 82 | +| A.5 Region-specific functional characteristics..... | 89 | +| Annex B – Regional requirements – Region 2 ..... | 96 | +| B.1 Scope ..... | 96 | +| B.2 Test loops..... | 96 | +| B.3 Performance testing ..... | 99 | +| B.4 PSD masks..... | 117 | +| B.5 Region-specific functional characteristics..... | 122 | +| Annex C – Regional requirements – Region 3 ..... | 125 | +| Annex D – Signal regenerator operation..... | 125 | +| D.1 Reference diagram..... | 125 | +| D.2 Start-up procedures..... | 126 | +| D.3 Symbol rates ..... | 130 | +| D.4 PSD masks..... | 130 | +| Annex E – Application-specific TPS-TC framing..... | 130 | +| E.1 TPS-TC for clear channel data ..... | 130 | +| E.2 TPS-TC for clear channel byte-oriented data..... | 131 | +| E.3 TPS-TC for unaligned DS1 transport..... | 132 | +| E.4 TPS-TC for aligned DS1/fractional DS1 transport ..... | 133 | +| E.5 TPS-TC for European 2048 kbit/s digital unstructured leased line
(D2048U)..... | 134 | +| E.6 TPS-TC for unaligned European 2048 kbit/s digital structured leased line
(D2048S) ..... | 134 | +| E.7 TPS-TC for aligned European 2048 kbit/s digital structured leased line
(D2048S) and fractional ..... | 135 | +| E.8 TPS-TC for synchronous ISDN basic access ..... | 136 | +| E.9 TPS-TC for ATM transport ..... | 154 | +| E.10 Dual-bearer TPS-TC mode..... | 161 | +| E.11 TPS-TC for PTM transport..... | 176 | +| E.12 TPS-TC for STM with a Dedicated Signalling Channel (DSC)..... | 182 | +| E.13 TPS-TC for LAPV5 enveloped POTS or ISDN..... | 184 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------|------| +| Annex F – Region 1 requirements for payload data rates up to 5696 kbit/s..... | 188 | +| F.1    Scope ..... | 188 | +| F.2    Data rate..... | 189 | +| F.3    Mapper..... | 191 | +| F.4    PSD masks..... | 192 | +| F.5    Crosstalk interference requirements ..... | 194 | +| F.6    Functional characteristics ..... | 195 | +| Annex G – Reserved for Region 2 requirements for data rates between 2320 kbit/s and
**max rate** ..... | 196 | +| Annex H – Deactivation and warm-start procedure..... | 196 | +| H.1    Deactivation to reduced power mode ..... | 196 | +| H.2    Warm-start activation ..... | 198 | +| Appendix I – Test circuit examples ..... | 203 | +| I.1    Example crosstalk injection test circuit..... | 203 | +| I.2    Example coupling circuits for longitudinal balance and longitudinal
output voltage ..... | 203 | +| I.3    Return loss test circuit ..... | 204 | +| I.4    Transmit PSD/total power measurement test circuit ..... | 205 | +| Appendix II – Typical characteristics of cables..... | 205 | +| II.1    Typical characteristics of cables for Annex B..... | 205 | +| Appendix III – Signal regenerator start-up description ..... | 206 | +| III.1    STU-R initiated Start-up..... | 207 | +| III.2    STU-C initiated start-up ..... | 208 | +| III.3    SRU initiated start-up ..... | 209 | +| III.4    Collisions and retrains ..... | 209 | +| III.5    Diagnostic mode activation ..... | 210 | +| Appendix IV – Tabulation of Annex B noise profiles ..... | 210 | +| BIBLIOGRAPHY ..... | 223 | + + + +# Single-pair high-speed digital subscriber line (SHDSL) transceivers + +# 1 Scope + +This Recommendation describes a transmission method for providing Single-pair High-speed Digital Subscriber Line (SHDSL) service as a means for data transport in telecommunications access networks. This Recommendation does not specify all the requirements for the implementation of SHDSL transceivers. Rather, it serves only to describe the functionality needed to assure interoperability of equipment from various manufacturers. The definitions of physical user interfaces and other implementation-specific characteristics are beyond the scope of this Recommendation. + +For interrelationships of this Recommendation with other G.99x-series ITU-T Recommendations, see ITU-T Rec. G.995.1 in Bibliography [B2] (informative). + +The principal characteristics of this Recommendation are as follows: + +- provisions for duplex operation over one (or, optionally, multiple) mixed gauge two-wire twisted metallic pairs; +- specification of the physical layer functionality, e.g., line codes and forward error correction; +- specification of the data link layer functionality, e.g., frame synchronization and framing of application, as well as Operations, Administration and Maintenance (OAM) data; +- provisions for optional use of repeaters for extended reach; +- provisions for spectral compatibility with other transmission technologies deployed in the access network; +- provisions for regional requirements, including functional differences and performance requirements. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [1] ITU-T Recommendation G.992.1 (1999), *Asymmetric Digital Subscriber Line (ADSL) transceivers*. +- [2] ITU-T Recommendation G.994.1 (2003), *Handshake procedures for digital subscriber line (DSL) transceivers, plus Amendment 1 (2004)*. +- [3] ITU-T Recommendation G.997.1 (2003), *Physical layer management for digital subscriber line (DSL) transceivers*. +- [4] IETF RFC 1662 (1994), *PPP in HDLC-like Framing*. +- [5] ISO 8601:2000, *Data elements and interchange formats – Information interchange – Representation of dates and times*. + +- [6] ITU-T Recommendation G.996.1 (2001), *Test procedures for Digital Subscriber Line (DSL) transceivers*. +- [7] IEC 60950 (1999), *Information technology equipment – Safety*. +- [8] ITU-T Recommendation I.432.1 (1999), *B-ISDN user-network interface – Physical layer specification: General characteristics*. +- [9] ETSI EN 300 324-1 (1994), *V Interfaces at the digital Local Exchange (LE); V5.1 interface for the support of Access Network (AN); Part 1: V5.1 Interface specification*. +- [10] ETSI EG 201 900-1 V1.1.1 (2001), *Services and Protocols for Advanced Networks (SPAN); Narrowband Services over ATM; Loop Emulation Service (LES) using AAL2; Part 1: LES interface specification [ATM Forum Specification af-vmoa-0145.000 (2000), modified]*. +- [11] Coded Identification of Equipment Entities of the North American Telecommunications System for Information Exchange [Revision of T1.213-1990 (R1996)], May 2001. + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +This Recommendation defines the following terms: + +- 3.1.1 bit-error ratio:** The ratio of the number of bits in error to the number of bits sent over a period of time. +- 3.1.2 downstream:** STU-C to STU-R direction (central office to remote terminal). +- 3.1.3 loopback:** A reversal in the direction of the payload (i.e., the user data) at a specified SHDSL network element. +- 3.1.4 mapper:** A device for associating a grouping of bits with a transmission symbol. +- 3.1.5 micro-interruption:** A temporary line interruption. +- 3.1.6 modulo:** A device having limited value outputs (not the same as the mathematical modulo operation). +- 3.1.7 payload block:** One of the sections of a frame containing user data. +- 3.1.8 plesiochronous:** A clocking scheme in which the SHDSL frame is based on the input transmit clock but the symbol clock is based on another independent clock source. +- 3.1.9 precoder:** A device in the transmitter for equalizing some of the channel impairments. +- 3.1.10 precoder coefficients:** Coefficients of the filter in the precoder that are generated in the receiver and transferred to the transmitter. +- 3.1.11 remote terminal:** A terminal located downstream from a central office switching system. +- 3.1.12 scrambler:** A device to randomize a data stream. +- 3.1.13 segment:** The portion of a span between two terminations (either STUs or SRUs). +- 3.1.14 SHDSL network element:** An STU-R, STU-C or SRU. +- 3.1.15 span:** The link between STU-C and STU-R, including regenerators. +- 3.1.16 spectral shaper:** A device that reshapes the frequency characteristics of a signal. +- 3.1.17 stuff bits:** Bits added to synchronize independent data streams. +- 3.1.18 synchronous:** A clocking scheme in which the SHDSL frame and symbol clocks are based on the STU-C input transmit clock or a related network timing source. + +**3.1.19 upstream:** STU-R to STU-C direction (remote terminal to central office). + +## **3.2 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|--------------------|-----------------------------------------------------------------------------------------| +| $\alpha$ | The interface between the PMS-TC and TPS-TC layers in an STU-C | +| $\beta$ | The interface between the PMS-TC and TPS-TC layers in an STU-R | +| $\gamma_C$ | The interface between the TPS-TC layer and the application specific section in an STU-C | +| $\gamma_R$ | The interface between the TPS-TC layer and the application specific section in an STU-R | +| $a_k$ | Convolutional Encoder Coefficients | +| AFE | Analogue Front End | +| AGC | Automatic Gain Control | +| $b_k$ | Convolutional Encoder Coefficients | +| BER | Bit Error Ratio | +| bit/s | Bits per Second | +| $C_k$ | The $k$ th Precoder Coefficient | +| CLEI TM | Common Language Equipment Identifier | +| CMRR | Common Mode Rejection Ratio | +| CO | Central Office | +| CPE | Customer Premises Equipment | +| CRC | Cyclic Redundancy Check | +| CRC-6 | CRC of Order 6 (used in SHDSL frame) | +| $crc(X)$ | CRC Check Polynomial | +| DAC | Digital-to-Analogue Converter | +| dBm | dB reference to 1 mW, i.e., 0 dBm = 1 mW | +| DC | Direct Current | +| DLL | Digital Local Line | +| DRR | Dynamic Rate Repartitioning | +| DS | Downstream | +| DSC | Dedicated Signalling Channel | +| DSL | Digital Subscriber Line | +| DUT | Device Under Test | +| EOC | Embedded Operations Channel | +| ES | Errored Second | +| $f_s$ | Sampling rate | +| $f_{sym}$ | Symbol rate | +| FCS | Frame Check Sequence | + +| | | +|-------------|------------------------------------------------------------| +| FEC | Forward Error Correction | +| FEFT | Far-End CrossTalk | +| FSW | Frame Synchronization Word | +| $g(X)$ | Generating Polynomial for CRC | +| HDLC | High-level Data Link Control | +| HW | Hardware | +| I/F | Interface | +| kbit/s | Kilobits per second | +| LB | Longitudinal Balance | +| LCL | Longitudinal Conversion Loss | +| losd | Bit indicating Loss of signal at the application interface | +| LOSW | Loss Of Sync Word failure | +| LSB | Least Significant Bit | +| LT | Line Termination | +| $m(X)$ | Message Polynomial for CRC | +| Mbit/s | Megabits per second | +| MSB | Most Significant Bit | +| MTU | Maintenance Termination Unit | +| NEXT | Near-End CrossTalk | +| NT | Network Termination | +| OAM | Operations, Administration and Maintenance | +| OH | Overhead | +| PAM | Pulse Amplitude Modulation | +| 2-PAM | PAM having two levels (used at startup) | +| PBO | Power Back-Off | +| PL-OAM | Physical Layer – OAM | +| PMD | Physical Medium Dependent | +| PMMS | Power Measurement Modulation Session (Line Probe) | +| PMS-TC | Physical Medium-Specific TC Layer | +| ppm | Parts Per Million | +| PPP | Point-to-Point Protocol | +| ps | Power status bit | +| PSD | Power Spectral Density | +| PTD | Path Terminating Device (CO side terminating equipment) | +| PTM | Packet Transfer Mode | +| REG | Signal Regenerator | +| rms | Root mean square | + +| | | +|-------------|-----------------------------------------------------------------------------------------------------| +| RSP | Regenerator Silent Period bit | +| RX | Receiver | +| S/T | Logical interface between the STU-R and attached user terminal equipment | +| sb | stuff bit | +| sbid | stuff bit identified indicator bit | +| sega | segment anomaly indicator bit | +| segd | segment defect indicator bit | +| SES | Severely Errored Second | +| SHDSL | Single-Pair High-Speed DSL | +| SNR | Signal-to-Noise Ratio | +| SRU | SHDSL Regenerator Unit | +| STU | SHDSL Transceiver Unit | +| STU-C | STU at the Central Office | +| STU-R | STU at the Remote End | +| TBD | To Be Determined | +| TC | Transmission Convergence layer | +| TCM | Trellis Coded Modulation | +| TCM-ISDN | Time-Compression Multiplexed ISDN (specified in Appendix III/G.961 [B1]) | +| TCPAM | Trellis Coded PAM (used in data mode) | +| TPS-TC | Transmission Protocol-Specific TC Layer | +| TX | Transmitter | +| U-C | Loop Interface – Central Office end | +| U-R | Loop Interface – Remote Terminal end | +| UAS | Unavailable Second | +| US | Upstream | +| UTC | Unable to Comply | +| V | Logical interface between STU-C and a digital network element such as one or more switching systems | +| xDSL | a collective term referring to any of the various types of DSL technologies | + +# 4 Reference models + +## 4.1 STU-x functional model + +![Figure 4-1/G.991.2 – STU-x functional model. A block diagram showing the functional model of an SHDSL Transceiver Unit (STU). It consists of two main units: STU-R (Remote) and STU-C (Central). Each unit is divided into an 'Application specific section' and an 'Application invariant section'. The STU-R has interfaces labeled γr and β. The STU-C has interfaces labeled α and γc. Between the units is an 'optional' SRU (Signal Regenerator). The diagram shows internal components like I/F (Interface), TPS-TC, PMS-TC, and PMD layers. The STU-R's application specific section contains I/F and TPS-TC. The application invariant section contains PMS-TC and PMD. The STU-C's application invariant section contains PMD and PMS-TC. The application specific section contains TPS-TC and I/F. Optional signal regenerators (SRU) are shown between the units.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +Figure 4-1/G.991.2 – STU-x functional model. A block diagram showing the functional model of an SHDSL Transceiver Unit (STU). It consists of two main units: STU-R (Remote) and STU-C (Central). Each unit is divided into an 'Application specific section' and an 'Application invariant section'. The STU-R has interfaces labeled γr and β. The STU-C has interfaces labeled α and γc. Between the units is an 'optional' SRU (Signal Regenerator). The diagram shows internal components like I/F (Interface), TPS-TC, PMS-TC, and PMD layers. The STU-R's application specific section contains I/F and TPS-TC. The application invariant section contains PMS-TC and PMD. The STU-C's application invariant section contains PMD and PMS-TC. The application specific section contains TPS-TC and I/F. Optional signal regenerators (SRU) are shown between the units. + +G.991.2\_F4-1 + +**Figure 4-1/G.991.2 – STU-x functional model** + +Figure 4-1 is a block diagram of an SHDSL Transceiver Unit (STU) transmitter showing the functional blocks and interfaces that are referenced in this Recommendation. It illustrates the basic functionality of the STU-R and the STU-C. Each STU contains both an application invariant section and an application specific section. The application invariant section consists of the PMD and PMS-TC layers, while the application specific aspects are confined to the TPS-TC layer and device interfaces. As shown in the figure, one or more optional signal regenerators may also be included in an SHDSL span. Management functions, which are typically controlled by the operator's network management system, are not shown in the figure. See clause 9 for details on management. Remote power feeding, which is optionally provided across the span by the STU-C, is not illustrated in the figure. + +The functions at the central office side constitute the STU-C (or Line Termination (LT)). The STU-C acts as the master both to the customer side functions of the STU-R (or Network Termination (NT)) and to any regenerators. + +The STU-C and STU-R, along with the DLL (Digital Local Line) and any regenerators, make up an SHDSL span. The DLL may consist of a single copper twisted pair, or, in optional configurations, multiple copper twisted pairs. In the multi-pair cases, each STU contains multiple separate PMD layers, interfacing to a common PMS-TC layer. If enhanced transmission range is required, one or more signal regenerators may be inserted into the loop at intermediate points. These points shall be chosen to meet applicable criteria for insertion loss and loop transmission characteristics. + +The principal functions of the PMD layer are: + +- symbol timing generation and recovery; +- coding and decoding; +- modulation and demodulation; +- echo cancellation; +- line equalization; +- link startup. + +The PMD layer functionality is described in detail in clause 6. + +The PMS-TC layer contains the framing and frame synchronization functions, as well as the scrambler and descrambler. The PMS-TC layer is described in clause 7. + +The PMS-TC is connected across the $\alpha$ and $\beta$ interfaces in the STU-C and the STU-R, respectively, to the TPS-TC layer. The TPS-TC is application specific and consists largely of the packaging of user data within the SHDSL frame. See clause 8 for details. This may include multiplexing, demultiplexing, and timing alignment of multiple user data channels. Supported TPS-TC user data framing formats are described in Annex E. + +The TPS-TC layer communicates with the Interface blocks across the $\gamma_R$ and $\gamma_C$ interfaces. Depending upon the specific application, the TPS-TC layer may be required to support one or more channels of user data and associated interfaces. The definition of these interfaces is beyond the scope of this Recommendation. + +Note that the $\alpha$ , $\beta$ , $\gamma_R$ and $\gamma_C$ interfaces are only intended as logical separations and need not be physically accessible. + +## 4.2 User plane protocol reference model + +![Figure 4-2/G.991.2 – User plane protocol reference model](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +This diagram illustrates the layered protocol structure for the user plane. On the left side (STU-R), a 'User data interface' (labeled S/T) connects to a stack. The stack includes a 'Not specified' block and a protocol stack consisting of 'PMD', 'PMS-TC', and 'TPS-TC'. Above 'TPS-TC' is a 'Transport protocol (e.g., SDH)' block, which receives input from 'NT1, NT2/I'. The 'TPS-TC' layer connects to the 'Physical transmission media' (labeled U) via the $\beta$ interface, and the 'Transport protocol' connects via the $\gamma_R$ interface. On the right side (STU-C), the 'Physical transmission media' connects to another stack: 'PMD', 'PMS-TC', and 'TPS-TC'. Above this is another 'Transport protocol (e.g., SDH)' block, which receives input from 'LT'. The 'TPS-TC' layer connects to the 'Internal interface' (labeled LT internal interface) via the $\alpha$ interface, and the 'Transport protocol' connects via the $\gamma_C$ interface. The 'Internal interface' connects to a 'Not specified' block. The diagram is labeled G.991.2\_F4-2. + +Figure 4-2/G.991.2 – User plane protocol reference model + +**Figure 4-2/G.991.2 – User plane protocol reference model** + +The User Plane Protocol Reference Model, shown in Figure 4-2, is an alternate representation of the information shown in Figure 4-1. This figure is included to emphasize the layered nature of this Recommendation and to provide a view that is consistent with the generic xDSL models shown in ITU-T Rec. G.995.1 [B2]. + +## 4.3 Application models + +![Figure 4-3/G.991.2 – Application model](a7c51c18111139f9aca2805114108565_img.jpg) + +This diagram shows the application model for the user plane. On the left, multiple 'User terminal' blocks (connected via S/T interfaces) are shown. One is in a dashed box labeled '(Optional)'. These connect to an 'STU-R' block. The 'STU-R' block is connected to a dashed box labeled '(Optional)' which contains a sequence of 'DLL', 'U-R', 'U-C', 'SRU', 'U-R', 'U-C', '...', 'U-R', 'DLL', 'U-C' blocks. The 'STU-R' (or the optional SRU chain) connects to the 'STU-C' block. The 'STU-C' block connects to a 'CO network' via the 'V' interface. The diagram is labeled G.991.2\_F4-3. + +Figure 4-3/G.991.2 – Application model + +**Figure 4-3/G.991.2 – Application model** + +Figure 4-3 is an application model for a typical SHDSL system, showing reference points and attached equipment. In such an application, an STU-R will typically connect to one or more user terminals, which may include data terminals, telecommunications equipment, or other devices. These connections to these pieces of terminal equipment are designated S/T reference points. The connection between STU-R and STU-C may optionally contain one or more SHDSL signal regenerators (SRUs). The connections to the DLLs that interconnect STUs and SRUs are designated U reference points. For each STU-x and SRU, the Network side connection is termed the U-R interface and the Customer side connection is termed the U-C interface. The STU-C typically connects to a Central Office network at the V reference point. + +# 5 Transport capacity + +This Recommendation specifies a two-wire operational mode for SHDSL transceivers that is capable of supporting user (payload) data rates from 192 kbit/s to 2.312 Mbit/s in increments of 8 kbit/s. The allowed rates are given by $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . For $n = 36$ , $i$ is restricted to the values of 0 or 1. See Annexes A and B for details of specific regional requirements. Note that optional extensions described in Annex F allow user data rates up to 5696 bit/s. + +This Recommendation also specifies an optional $M$ -pair operational mode that is capable of supporting user (payload) data rates from $M \times 192$ kbit/s to $M \times 2.312$ Mbit/s in increments of $M \times 8$ kbit/s, where $1 \leq M \leq 4$ . Note that optional extensions described in Annex F allow user data rates up to $M \times 5696$ kbit/s. Four-wire mode is identical to M-pair mode with $M = 2$ , except for the method of assigning ordinal numbers to the wire pairs. In four-wire mode the ordinal numbers (the wire pair identification number) are assigned as described in 6.3, while in M-pair mode the ordinal numbers are assigned to wire pairs as described in 7.2.1.5. Again, see Annexes A and B for details of specific regional requirements and Annex F for extended data rates. + +# 6 PMD layer functional characteristics + +## 6.1 Data mode operation + +### 6.1.1 STU data mode PMD reference model + +A reference model of the data mode PMD layer of an STU-C or STU-R transmitter is shown in Figure 6-1. + +![Figure 6-1/G.991.2 – Data mode PMD reference model. The diagram shows a block diagram of the transmitter chain. It starts with 'input from framer' labeled f(n) entering a 'Scrambler' block. The output of the scrambler is s(n), which enters a 'TCM encoder' block. The output of the TCM encoder is x(m), which enters a 'Precoder' block. The output of the precoder is y(m), which enters a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is labeled 'output at loop interface'.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` + +graph LR + Input["input from framer f(n)"] --> Scrambler[Scrambler] + Scrambler --> S["s(n)"] + S --> TCM["TCM encoder"] + TCM --> X["x(m)"] + X --> Precoder["Precoder"] + Precoder --> Y["y(m)"] + Y --> Spectral["Spectral shaper"] + Spectral --> Output["z(t) output at loop interface"] + +``` + +Figure 6-1/G.991.2 – Data mode PMD reference model. The diagram shows a block diagram of the transmitter chain. It starts with 'input from framer' labeled f(n) entering a 'Scrambler' block. The output of the scrambler is s(n), which enters a 'TCM encoder' block. The output of the TCM encoder is x(m), which enters a 'Precoder' block. The output of the precoder is y(m), which enters a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is labeled 'output at loop interface'. + +G.991.2\_F6-1 + +Figure 6-1/G.991.2 – Data mode PMD reference model + +The time index $n$ represents the bit time, the time index $m$ represents the symbol time, and $t$ represents analogue time. The input from the framer is $f(n)$ , and $s(n)$ is the output of the scrambler. Both the framer and the scrambler are contained within the PMS-TC layer and are shown here for clarity. $x(m)$ is the output of the TCM (Trellis Coded Modulation) encoder, $y(m)$ is the output of the channel precoder, and $z(t)$ is the analogue output of the spectral shaper at the loop interface. When transferring $K$ information bits per one-dimensional PAM symbol, the symbol duration is $K$ times the bit duration, so the $K$ values of $n$ for a given value of $m$ are $\{mK + 0, mK + 1, \dots, mK + K - 1\}$ . + +In the optional $M$ -pair mode, $M$ separate PMD sublayers are active – one for each wire pair. In this case, $n$ represents the bit time for each wire pair rather than the aggregate system line rate. + +#### 6.1.1.1 PMD rates + +The operation of the PMD layer at the specified information rate shall be as specified in A.5.1 or B.5.1. The operation of the PMD layer at the optional extended rates specified in Annex F shall be as specified in F.2. + +### 6.1.2 TCM encoder + +The block diagram of the TCM encoder is shown in Figure 6-2. The serial bit stream from the scrambler, $s(n)$ , shall be converted to a $K$ -bit parallel word at the $m$ th symbol time, then processed by the convolutional encoder. The resulting $K + 1$ -bit word shall be mapped to one of $2^{K+1}$ pre-determined levels forming $x(m)$ . + +![Block diagram of the TCM encoder. A serial bit stream s(n) enters a 'Serial to parallel' block. The output of this block is a K-bit parallel word where the bits are s(mK + K - 1) = X_K(m), ..., s(mK + 1) = X_2(m), and s(mK + 0) = X_1(m). The bit X_1(m) is fed into a 'Convolutional encoder' block, which produces two output bits, Y_1(m) and Y_0(m). All K bits from the serial-to-parallel converter and the two bits from the convolutional encoder are fed into a 'Mapper' block. The Mapper outputs the final signal x(m). The diagram is labeled G.991.2_F6-2.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +Block diagram of the TCM encoder. A serial bit stream s(n) enters a 'Serial to parallel' block. The output of this block is a K-bit parallel word where the bits are s(mK + K - 1) = X\_K(m), ..., s(mK + 1) = X\_2(m), and s(mK + 0) = X\_1(m). The bit X\_1(m) is fed into a 'Convolutional encoder' block, which produces two output bits, Y\_1(m) and Y\_0(m). All K bits from the serial-to-parallel converter and the two bits from the convolutional encoder are fed into a 'Mapper' block. The Mapper outputs the final signal x(m). The diagram is labeled G.991.2\_F6-2. + +Figure 6-2/G.991.2 – Block diagram of the TCM encoder + +#### 6.1.2.1 Serial-to-parallel converter + +The serial bit stream from the scrambler, $s(n)$ , shall be converted to a $K$ -bit parallel word $\{X_1(m) = s(mK + 0), X_2(m) = s(mK + 1), \dots, X_K(m) = s(mK + K - 1)\}$ at the $m$ th symbol time, where $X_1(m)$ is the first input bit in time. + +#### 6.1.2.2 Convolutional encoder + +Figure 6-3 shows the feedforward non-systematic convolutional encoder, where $T_s$ is a delay of one symbol time, " $\oplus$ " is binary exclusive-OR, and " $\otimes$ " is binary AND. $X_1(m)$ shall be applied to the convolutional encoder, $Y_1(m)$ and $Y_0(m)$ shall be computed, then $X_1(m)$ shall be shifted into the shift register. + +![Block diagram of the convolutional encoder. The diagram shows two parallel processing paths for bits a_i and b_i. The top path for b_i consists of multipliers (circles with X) followed by adders (circles with +). The bottom path for a_i also consists of multipliers followed by adders. A central horizontal line represents the input sequence X_1(m) entering a series of delay blocks (T_s). At each delay stage, the signal is tapped off to a multiplier for both the top and bottom paths. The outputs of the multipliers are accumulated through a chain of adders to produce the final outputs Y_1(m) and Y_0(m). The diagram is labeled G.991.2_F6-3.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +Block diagram of the convolutional encoder. The diagram shows two parallel processing paths for bits a\_i and b\_i. The top path for b\_i consists of multipliers (circles with X) followed by adders (circles with +). The bottom path for a\_i also consists of multipliers followed by adders. A central horizontal line represents the input sequence X\_1(m) entering a series of delay blocks (T\_s). At each delay stage, the signal is tapped off to a multiplier for both the top and bottom paths. The outputs of the multipliers are accumulated through a chain of adders to produce the final outputs Y\_1(m) and Y\_0(m). The diagram is labeled G.991.2\_F6-3. + +**Figure 6-3/G.991.2 – Block diagram of the convolutional encoder** + +The binary coefficients $a_i$ and $b_i$ shall be passed to the encoder from the receiver during the activation phase specified in 7.2.1.3. A numerical representation of these coefficients is $A$ and $B$ where: + +$$A = a_{20} \cdot 2^{20} + a_{19} \cdot 2^{19} + a_{18} \cdot 2^{18} + \dots + a_0 \cdot 2^0; \text{ and}$$ + +$$B = b_{20} \cdot 2^{20} + b_{19} \cdot 2^{19} + b_{18} \cdot 2^{18} + \dots + b_0 \cdot 2^0$$ + +The choice of encoder coefficients is vendor specific. They shall be chosen such that the system performance requirements are satisfied (see Annex A and/or Annex B for performance requirements). + +#### 6.1.2.3 Mapper + +The $K + 1$ bits $Y_K(m), \dots, Y_1(m)$ , and $Y_0(m)$ shall be mapped to a level $x(m)$ . Table 6-1 gives the bit to level mapping for 16-level mapping. + +**Table 6-1/G.991.2 – Mapping of bits to PAM levels** + +| Y3(m) | Y2(m) | Y1(m) | Y0(m) | x(m) for 16-PAM | +|-------------------------|-------------------------|-------------------------|-------------------------|------------------------| +| 0 | 0 | 0 | 0 | -15/16 | +| 0 | 0 | 0 | 1 | -13/16 | +| 0 | 0 | 1 | 0 | -11/16 | +| 0 | 0 | 1 | 1 | -9/16 | +| 0 | 1 | 0 | 0 | -7/16 | +| 0 | 1 | 0 | 1 | -5/16 | +| 0 | 1 | 1 | 0 | -3/16 | +| 0 | 1 | 1 | 1 | -1/16 | +| 1 | 1 | 0 | 0 | 1/16 | +| 1 | 1 | 0 | 1 | 3/16 | +| 1 | 1 | 1 | 0 | 5/16 | +| 1 | 1 | 1 | 1 | 7/16 | +| 1 | 0 | 0 | 0 | 9/16 | +| 1 | 0 | 0 | 1 | 11/16 | +| 1 | 0 | 1 | 0 | 13/16 | +| 1 | 0 | 1 | 1 | 15/16 | + +### 6.1.3 Channel precoder + +The block diagram of channel precoder is shown in Figure 6-4, where $T_s$ is a delay of one symbol time. + +![Block diagram of the channel precoder. The input x(m) is summed with a feedback signal v(m) to produce u(m), which is then processed by a Modulo block to produce y(m). The feedback signal v(m) is generated by a precoder filter that takes delayed versions of y(m) (y(m-1), y(m-2), ..., y(m-N)) and multiplies them by coefficients C1, C2, ..., CN-1, CN respectively, then sums the results.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +The diagram illustrates the channel precoder structure. An input signal $x(m)$ is added to a feedback signal $v(m)$ at a summing junction to produce $u(m)$ . This $u(m)$ is passed through a 'Modulo' block to generate the output $y(m)$ . The output $y(m)$ is also fed back through a series of delay blocks $T_s$ to produce delayed signals $y(m-1)$ , $y(m-2)$ , and $y(m-N)$ . These delayed signals are multiplied by coefficients $C_1$ , $C_2$ , $C_{N-1}$ , and $C_N$ (as shown in the diagram's order) and then summed at another junction to produce the feedback signal $v(m)$ . The entire feedback section is labeled 'Precoder filter'. + +Block diagram of the channel precoder. The input x(m) is summed with a feedback signal v(m) to produce u(m), which is then processed by a Modulo block to produce y(m). The feedback signal v(m) is generated by a precoder filter that takes delayed versions of y(m) (y(m-1), y(m-2), ..., y(m-N)) and multiplies them by coefficients C1, C2, ..., CN-1, CN respectively, then sums the results. + +Figure 6-4/G.991.2 – Block diagram of the channel precoder + +The coefficients of the precoder filter, $C_k$ , shall be transferred to the channel precoder as described in 7.2.1.2. The output of the precoder filter, $v(m)$ , shall be computed as follows: + +$$v(m) = \sum_{k=1}^N C_k y(m-k)$$ + +Where $128 \leq N \leq 180$ . The function of the modulo block shall be to determine $y(m)$ as follows: for each value of $u(m)$ , find an integer, $d(m)$ , such that: + +$$-1 \leq u(m) + 2d(m) < 1$$ + +and then + +$$y(m) = u(m) + 2d(m)$$ + +### 6.1.4 Spectral shaper + +The choice of spectral shape shall be region-specific. The details of PSDs for Regions A and B are given in A.4 and B.4. The details of PSDs for the optional extended rates in Annex F are given in F.4. + +### 6.1.5 Power backoff + +SHDSL devices shall implement Power Backoff, as specified in this clause. The selected power backoff value shall be communicated during pre-activation through the use of G.994.1 parameter selections. + +The power backoff value shall be selected to meet the requirements shown in Table 6-2. The power backoff calculations are based on Estimated Power Loss (EPL), which is defined as: + +Estimated Power Loss (dB) = TX Power (dBm) – Estimated RX Power (dBm), +evaluated for the data mode PSD. + +No explicit specification is given herein for the method of calculating Estimated RX Power. Depending upon the application, this value may be determined based on line probe results, *a priori* knowledge, or G.994.1 tone levels. + +The Power Backoff that is applied shall be no less than the Default Power Backoff, and it shall not exceed the Maximum Power Backoff Value. + +**Table 6-2/G.991.2 – Required power backoff values** + +| Estimated power loss (dB) | Maximum power backoff (dB) | Default power backoff (dB) | +|---------------------------|----------------------------|----------------------------| +| $EPL > 6$ | 31 | 0 | +| $6 \geq EPL > 5$ | 31 | 1 | +| $5 \geq EPL > 4$ | 31 | 2 | +| $4 \geq EPL > 3$ | 31 | 3 | +| $3 \geq EPL > 2$ | 31 | 4 | +| $2 \geq EPL > 1$ | 31 | 5 | +| $1 \geq EPL > 0$ | 31 | 6 | + +## 6.2 PMD activation sequence + +This clause describes waveforms at the loop interface and associated procedures during activation mode. The direct specification of the performance of individual receiver elements is avoided when possible. Instead, the transmitter characteristics are specified on an individual basis and the receiver performance is specified on a general basis as the aggregate performance of all receiver elements. Exceptions are made for cases where the performance of an individual receiver element is crucial to interoperability. In 6.2.2, "convergence" refers to the state where all adaptive elements have reached steady-state. The declaration of convergence by a transceiver is therefore vendor dependent. Nevertheless, actions based on the state of convergence are specified to improve interoperability. + +### 6.2.1 PMD activation reference model + +The reference model of the activation mode of an STU-C or STU-R transmitter is shown in Figure 6-5. + +![Figure 6-5/G.991.2 – Activation reference model. The diagram shows a block diagram of the activation sequence. Inputs include 'logical ones' (d(m)) and 'precoder coefficients, encoder coefficients'. The 'logical ones' and the output of the 'Activation framer' (f(m)) are combined via a switch. The output of the switch goes to a 'Scrambler' block, which outputs s(m). s(m) goes to a 'Mapper' block, which outputs y(m). y(m) goes to a 'Spectral shaper' block, which outputs z(t). z(t) is the 'output at loop interface'. A small note 'G.991.2_F6-5' is present in the bottom right corner of the diagram area.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +Figure 6-5/G.991.2 – Activation reference model. The diagram shows a block diagram of the activation sequence. Inputs include 'logical ones' (d(m)) and 'precoder coefficients, encoder coefficients'. The 'logical ones' and the output of the 'Activation framer' (f(m)) are combined via a switch. The output of the switch goes to a 'Scrambler' block, which outputs s(m). s(m) goes to a 'Mapper' block, which outputs y(m). y(m) goes to a 'Spectral shaper' block, which outputs z(t). z(t) is the 'output at loop interface'. A small note 'G.991.2\_F6-5' is present in the bottom right corner of the diagram area. + +G.991.2\_F6-5 + +**Figure 6-5/G.991.2 – Activation reference model** + +The time index $m$ represents the symbol time, and $t$ represents analogue time. Startup uses 2-PAM modulation, so the bit time is equivalent to the symbol time. The output of the activation framer is $f(m)$ , the framed information bits. The output of the scrambler is $s(m)$ . Both the framer and the scrambler are contained within the PMS-TC layer and are shown here only for clarity. The output of the mapper is $y(m)$ , and the output of the spectral shaper at the loop interface is $z(t)$ . $d(m)$ is an initialization signal that shall be logical ones for all $m$ . The modulation format shall be uncoded 2-PAM, at the symbol rate selected for data mode operation. + +In devices supporting the optional $M$ -pair mode, the core activation procedure shall be considered as an independent procedure for each pair. Such devices shall be capable of detecting the completion of activation for all pairs and upon completion shall initiate the transmission of user data over all pairs. + +### 6.2.2 PMD activation sequence description + +The timing diagram for the activation sequence is given in Figure 6-6. The state transition diagram for the startup sequence is given in Figure 6-7. Each signal in the activation sequence shall satisfy the tolerance values listed in Table 6-3. + +![Figure 6-6/G.991.2 – Timing diagram for activation sequence. This diagram shows the timing relationships between signals at the STU-C (Customer Side Unit) and STU-R (Remote Side Unit). At the STU-C, the sequence starts with a silence state S_c, followed by a transition state T_c, then a failure state F_c, and finally data transmission Data_c. At the STU-R, the sequence starts with a reset state C_r, followed by a silence state S_r, then a transition state T_r, and finally data transmission Data_r. Key timing parameters are defined: t_act (total activation time from start of C_r to start of Data_c), t_cr (duration of C_r), t_crsc (time from end of C_r to start of S_c), t_csr (time from end of C_r to start of S_r), and t_p-total (total duration of pre-activation phase).](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 6-6/G.991.2 – Timing diagram for activation sequence. This diagram shows the timing relationships between signals at the STU-C (Customer Side Unit) and STU-R (Remote Side Unit). At the STU-C, the sequence starts with a silence state S\_c, followed by a transition state T\_c, then a failure state F\_c, and finally data transmission Data\_c. At the STU-R, the sequence starts with a reset state C\_r, followed by a silence state S\_r, then a transition state T\_r, and finally data transmission Data\_r. Key timing parameters are defined: t\_act (total activation time from start of C\_r to start of Data\_c), t\_cr (duration of C\_r), t\_crsc (time from end of C\_r to start of S\_c), t\_csr (time from end of C\_r to start of S\_r), and t\_p-total (total duration of pre-activation phase). + +Figure 6-6/G.991.2 – Timing diagram for activation sequence + +Figure 6-6a shows the total activation sequence at a high level for G.991.2, which includes pre-activation and core activation. Included as an example in the pre-activation phase are two sessions of handshake per ITU-T Rec. G.994.1 and line probe. + +![Figure 6-6a/G.991.2 – G.991.2 total activation sequence. This high-level diagram illustrates the total activation sequence. It is divided into two main phases: pre-activation (t_pre_activation) and core activation (t_core_activation). The pre-activation phase includes two sessions of G.994.1 handshake and a line probing session. The core activation phase includes the actual data transmission. The total duration of the pre-activation phase is less than or equal to t_p-total. The total duration of the core activation phase is less than or equal to t_act. The global activation time (t_act_global) is the sum of the pre-activation and core activation times.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 6-6a/G.991.2 – G.991.2 total activation sequence. This high-level diagram illustrates the total activation sequence. It is divided into two main phases: pre-activation (t\_pre\_activation) and core activation (t\_core\_activation). The pre-activation phase includes two sessions of G.994.1 handshake and a line probing session. The core activation phase includes the actual data transmission. The total duration of the pre-activation phase is less than or equal to t\_p-total. The total duration of the core activation phase is less than or equal to t\_act. The global activation time (t\_act\_global) is the sum of the pre-activation and core activation times. + +Figure 6-6a/G.991.2 – G.991.2 total activation sequence + +The global activation time is the sum of the pre-activation and core activation times. Therefore, from Figure 6-6a, + +$$t_{pre\_activation} + t_{core\_activation} \leq t_{act\_global}$$ + +where $t_{pre\_activation}$ is the combined duration of the G.994.1 sessions (see 6.4) and line probing (see 6.3), $t_{core\_activation}$ is the core activation duration (see 6.2). The values for $t_{act}$ and $t_{act\_global}$ are defined in Table 6-3. The value for $t_{p-total}$ is given in Table 6-5. + +Table 6-3/G.991.2 – Timing for activation signals + +| Time | Parameter | Reference | Nominal value | Tolerance | +|--------------------|-----------------------------------------------------------------------------|-----------|-----------------------------------|---------------------| +| $t_{cr}$ | Duration of $C_r$ | 6.2.2.1 | $1 \times \beta \text{ s}^{a)}$ | $\pm 20 \text{ ms}$ | +| $t_{crsc}$ | Time from end of $C_r$ to beginning of $S_c$ | 6.2.2.2 | 500 ms | $\pm 20 \text{ ms}$ | +| $t_{csr}$ | Time from end of $C_r$ to beginning of $S_r$ | 6.2.2.3 | $1.5 \times \beta \text{ s}^{a)}$ | $\pm 20 \text{ ms}$ | +| $t_{act}$ | Maximum time from start of $C_r$ to $Data_r$ | | $15 \times \beta \text{ s}^{a)}$ | | +| $t_{payloadValid}$ | Maximum time from start of $Data_c$ or $Data_r$ to valid SHDSL payload data | | 1 s | | +| $t_{silence}$ | Minimum silence time from exception | | 2 s | | + +**Table 6-3/G.991.2 – Timing for activation signals** + +| Time | Parameter | Reference | Nominal value | Tolerance | +|-------------------|-----------------------------------------------------------------------|-----------|---------------|-----------| +| | condition to start of train | | | | +| $t_{PLL}$ | Maximum time from start of $S_c$ to STU-R PLL lock | | 5 s | | +| $t_{act\_global}$ | Time from start of initial pre-activation session (6.3) to $Data_r^b$ | | 30 s | | + +a) $\beta$ is dependent on bit rate. $\beta = 1$ for $n > 12$ , $\beta = 2$ for $n \leq 12$ , where $n$ is defined in clause 5. +b) In the majority of the cases, $t_{act\_global}$ will be less than 30 seconds. However, since the definition of the handshake mechanism in ITU-T Rec. G.994.1 is outside the scope of this Recommendation, a maximum value $t_{act\_global}$ cannot be assured. + +![STU-C and STU-R transmitter activation state transition diagram. The diagram shows two parallel state transition paths for STU-C and STU-R. Both start with 'Power on' leading to 'Pre-activation per 6.3'. STU-C path: 'Pre-activation per 6.3' -> 'C_r detected' -> 'S_c' -> 'Receiver converged on S_r and S_c sent > t_PLL' -> 'T_c' -> 'T_r detected' -> 'F_c' -> 'Data_c'. STU-R path: 'Pre-activation per 6.3' -> 'C_r' -> 'S_r' -> 'T_c detected' -> 'T_r' -> 'F_c detected' -> 'Data_r'. Both paths have an 'Exception state' with transitions for 'Not converged on S_r', 'T_r not detected', 'Exception detected' for STU-C and 'Not converged on T_c or T_c not detected', 'F_c not detected', 'Exception detected' for STU-R.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) + +``` + +graph TD + subgraph STU-C + STU-C_PowerOn[Power on] --> STU-C_PreAct((Pre-activation per 6.3)) + STU-C_PreAct -- "Cr detected" --> STU-C_Sc((Sc)) + STU-C_Sc -- "Receiver converged on Sr and Sc sent > tPLL" --> STU-C_Tc((Tc)) + STU-C_Tc -- "Tr detected" --> STU-C_Fc((Fc)) + STU-C_Fc --> STU-C_Datac((Datac)) + STU-C_Sc -- "Not converged on Sr" --> STU-C_Exception((Exception state)) + STU-C_Tc -- "Tr not detected" --> STU-C_Exception + STU-C_Fc -- "Exception detected" --> STU-C_Exception + STU-C_Exception --> STU-C_PreAct + end + subgraph STU-R + STU-R_PowerOn[Power on] --> STU-R_PreAct((Pre-activation per 6.3)) + STU-R_PreAct --> STU-R_Cr((Cr)) + STU-R_Cr --> STU-R_Sr((Sr)) + STU-R_Sr -- "Tc detected" --> STU-R_Tr((Tr)) + STU-R_Tr -- "Fc detected" --> STU-R_Datar((Datar)) + STU-R_Sr -- "Not converged on Tc or Tc not detected" --> STU-R_Exception((Exception state)) + STU-R_Tr -- "Fc not detected" --> STU-R_Exception + STU-R_Datar -- "Exception detected" --> STU-R_Exception + STU-R_Exception --> STU-R_PreAct + end + +``` + +STU-C and STU-R transmitter activation state transition diagram. The diagram shows two parallel state transition paths for STU-C and STU-R. Both start with 'Power on' leading to 'Pre-activation per 6.3'. STU-C path: 'Pre-activation per 6.3' -> 'C\_r detected' -> 'S\_c' -> 'Receiver converged on S\_r and S\_c sent > t\_PLL' -> 'T\_c' -> 'T\_r detected' -> 'F\_c' -> 'Data\_c'. STU-R path: 'Pre-activation per 6.3' -> 'C\_r' -> 'S\_r' -> 'T\_c detected' -> 'T\_r' -> 'F\_c detected' -> 'Data\_r'. Both paths have an 'Exception state' with transitions for 'Not converged on S\_r', 'T\_r not detected', 'Exception detected' for STU-C and 'Not converged on T\_c or T\_c not detected', 'F\_c not detected', 'Exception detected' for STU-R. + +G.991.2\_F6-7 + +**Figure 6-7/G.991.2 – STU-C and STU-R transmitter activation state transition diagram** + +#### 6.2.2.1 Signal $C_r$ + +After exiting the pre-activation sequence (per ITU-T Rec. G.994.1 [2], see 6.3 for details), the STU-R shall send $C_r$ . Waveform $C_r$ shall be generated by connecting the signal $d(m)$ to the input of the STU-R scrambler as shown in Figure 6-5. The PSD mask for $C_r$ shall be the upstream PSD mask, as negotiated during pre-activation sequence. $C_r$ shall have a duration of $t_{cr}$ and shall be sent 0.3 s after the end of pre-activation. + +NOTE – The end of pre-activation can be defined in two ways according to ITU-T Rec. G.994.1. For the purpose of this Recommendation, the end of pre-activation will be from the end of the ACK(1) message transmission plus the required timers. The minimum and maximum values of those timers are 0.04 and 1.0 second. Therefore, the total time between the end of the ACK(1) message and the beginning of $C_r$ should be between 0.34 and 1.3 seconds. + +#### 6.2.2.2 Signal $S_c$ + +After detecting $C_r$ , the STU-C shall send $S_c$ . Waveform $S_c$ shall be generated by connecting the signal $d(m)$ to the input of the STU-C scrambler as shown in Figure 6-5. The PSD mask for $S_c$ shall be the downstream PSD mask, as negotiated during pre-activation sequence. $S_c$ shall be sent $t_{crsc}$ after the end of $C_r$ . If the STU-C does not converge while $S_c$ is transmitted, it shall enter the exception state (6.2.2.8). + +#### 6.2.2.3 Signal $S_r$ + +The STU-R shall send $S_r$ , beginning $t_{crsr}$ after the end of $C_r$ . Waveform $S_r$ shall be generated by connecting the signal $d(m)$ to the input of the STU-R scrambler as shown in Figure 6-5. The PSD mask for $S_r$ shall be the same as for $C_r$ . If the STU-R does not converge and detect $T_c$ while $S_r$ is transmitted, it shall enter the exception state (6.2.2.8). The method used to detect $T_c$ is vendor dependent. In timing modes supporting loop timing, waveform $S_r$ and all subsequent signals transmitted from the STU-R shall be loop timed, i.e., the STU-R symbol clock shall be locked to the STU-C symbol clock. + +#### 6.2.2.4 Signal $T_c$ + +Once the STU-C has converged and has been sending $S_c$ for at least $t_{PLL}$ (Table 6-3), it shall send $T_c$ . Waveform $T_c$ contains the precoder coefficients and other system information. $T_c$ shall be generated by connecting the signal $f(m)$ to the input of the STU-C scrambler as shown in Figure 6-5. The PSD mask for $T_c$ shall be the same as for $S_c$ . The signal $f(m)$ is the activation frame information as described in 7.2.1. If the STU-C does not detect $T_r$ while sending $T_c$ , it shall enter the exception state (6.2.2.8). The method used to detect $T_r$ is vendor dependent. + +#### 6.2.2.5 Signal $T_r$ + +Once the STU-R has converged and has detected the $T_c$ signal, it shall send $T_r$ . Waveform $T_r$ contains the precoder coefficients and other system information. $T_r$ shall be generated by connecting the signal $f(m)$ to the input of the STU-R scrambler as shown in Figure 6-5. The PSD mask for $T_r$ shall be the same as for $C_r$ . The signal $f(m)$ is the activation frame information as described in 7.2.1. If the STU-R does not detect $F_c$ while sending $T_r$ , it shall enter the exception state (6.2.2.8). The method used to detect $F_c$ is vendor dependent. + +#### 6.2.2.6 Signal $F_c$ + +Once the STU-C has detected $T_r$ and completed sending the current $T_c$ frame, then it shall send $F_c$ . The first bit of the first $F_c$ frame shall follow contiguously the last bit of the last $T_c$ frame. Signal $F_c$ shall be generated by connecting the signal $f(m)$ to the input of the STU-C scrambler as shown in Figure 6-5. The PSD mask for $F_c$ shall be the same as for $S_c$ . The signal $f(m)$ is the activation frame information as described in 7.2.1 with the following exceptions: the frame sync word shall be reversed in time, and the payload information bits shall be set to arbitrary values. The CRC shall be calculated on this arbitrary-valued payload. The signal $F_c$ shall be transmitted for exactly two activation frames. As soon as the first bit of $F_c$ is transmitted, the payload data in the $T_r$ signal shall be ignored. + +#### 6.2.2.7 $Data_c$ and $Data_r$ + +Within 200 symbols after the end of the second frame of $F_c$ , the STU-C shall enter data mode and send $Data_c$ , and the STU-R shall enter data mode and send $Data_r$ . These TCPAM signals are described in 6.1. The PSD mask for $Data_r$ and for $Data_c$ shall be according to A.4 or B.4, as + +negotiated during the pre-activation sequence. There is no required relationship between the end of the activation frame and any bit within the SHDSL data-mode frame. $t_{\text{payloadValid}}$ (Table 6-3) after the end of $F_c$ , the SHDSL payload data shall be valid at the $\alpha$ or $\beta$ interface. + +#### 6.2.2.8 Exception state + +If activation is not achieved within $t_{\text{act}}$ (Table 6-3) or if any exception condition occurs, then the exception state shall be invoked. During the exception state the STU shall be silent for at least $t_{\text{silence}}$ (Table 6-3), then wait for transmission from the far end to cease, then return to the corresponding initial startup state; the STU-R and STU-C shall begin pre-activation, as per 6.3. + +#### 6.2.2.9 Exception condition + +An exception condition shall be declared during activation if any of the timeouts in Table 6-3 expire or if any vendor-defined abnormal event occurs. An exception condition shall be declared during data mode if a vendor-defined abnormal event occurs. A vendor-defined abnormal event shall be defined as any event that requires a loop restart for recovery. + +### 6.2.3 Framer and scrambler + +The activation mode framer and scrambler are described in 7.2. + +### 6.2.4 Mapper + +The output bits from the scrambler, $s(m)$ , shall be mapped to the output level, $y(m)$ , as follows: + +**Table 6-4/G.991.2 – Bit-to-level mapping** + +| Scrambler output $s(m)$ | Mapper output level, $y(m)$ | Data mode index | +|-------------------------|-----------------------------|-----------------| +| 0 | $-9/16$ | 0011 | +| 1 | $+9/16$ | 1000 | + +These levels, corresponding to the scrambler outputs 0 and 1, shall be identical to the levels in the 16-TCPAM constellation (Table 6-1) corresponding to indexes 0011 and 1000, respectively. + +### 6.2.5 Spectral shaper + +The same spectral shaper shall be used for data mode and activation mode as described in A.4 or B.4. For the optional extended rates in Annex F, the same spectral shaper shall be used for data mode and activation mode as described in F.4. + +### 6.2.6 Timeouts + +Table 6-3 shows the system timeouts and their values. $t_{\text{act}}$ shall be the maximum time from the start of $C_r$ to the start of $Data_r$ . It controls the overall time of the train. $t_{\text{payloadValid}}$ is the time between the start of data mode and the instant at which the SHDSL payload data is valid (this accounts for settling time, data flushing, frame synchronization, etc). $t_{\text{silence}}$ shall be the minimum time in the exception state in which the STU-C or STU-R is silent before returning to pre-activation (per ITU-T Rec. G.994.1 [2], see 6.3 for details). $t_{\text{PLL}}$ shall be the time allocated for the STU-R to pull in the STU-C timing. The STU-C shall transmit $S_c$ for at least $t_{\text{PLL}}$ . + +## 6.3 PMD pre-activation sequence + +This clause describes waveforms at the loop interface and associated procedures during pre-activation mode. The direct specification of the performance of individual receiver elements is avoided when possible. Instead, the transmitter characteristics are specified on an individual basis and the receiver performance is specified on a general basis as the aggregate performance of all receiver elements. Exceptions are made for cases where the performance of an individual receiver element is crucial to interoperability. + +In the optional 4-wire mode, Pair 1 and Pair 2 shall be determined during the pre-activation sequence per the procedures defined in Annex B/G.994.1 entitled, "Operation over multiple wire pairs". Pair 1 shall be defined as the pair on which the final G.994.1 transaction is conducted. + +Four-wire mode is identical to *M*-pair mode with *M* = 2, except for the method of assigning ordinal numbers to the wire pairs. In the optional *M*-pair mode, the ordering of wire pairs shall be determined as per 7.2.1.5. + +### 6.3.1 PMD pre-activation reference model + +The reference model of the pre-activation mode of an STU-C or STU-R transmitter is shown in Figure 6-8. + +![Figure 6-8/G.991.2 – Pre-activation reference model. This block diagram shows the signal processing path for a transmitter. It starts with 'logical ones' input to a 'Scrambler' block, which outputs s(m). This is followed by a 'Mapper' block outputting y(m), and a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is sent to a 'Probe' and a 'Handshake' mechanism at the 'loop interface'. A label 'G.991.2_F6-8' is present in the bottom right corner of the diagram area.](e354b57563dae469c00b412b2abdf765_img.jpg) + +Figure 6-8/G.991.2 – Pre-activation reference model. This block diagram shows the signal processing path for a transmitter. It starts with 'logical ones' input to a 'Scrambler' block, which outputs s(m). This is followed by a 'Mapper' block outputting y(m), and a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is sent to a 'Probe' and a 'Handshake' mechanism at the 'loop interface'. A label 'G.991.2\_F6-8' is present in the bottom right corner of the diagram area. + +Figure 6-8/G.991.2 – Pre-activation reference model + +The time index *m* represents the symbol time, and *t* represents analogue time. Since the probe signal uses 2-PAM modulation, the bit time is equivalent to the symbol time. The output of the scrambler is *s(m)*. The scrambler used in the PMD pre-activation may differ from the PMS-TC scrambler used in activation and data modes. See 6.3.3 for details of the pre-activation scrambler. The output of the mapper is *y(m)*, and the output of the spectral shaper at the loop interface is *z(t)*. *d(m)* is an initialization signal that shall be logical ones for all *m*. The probe modulation format shall be uncoded 2-PAM, with the symbol rate, spectral shape, duration and power backoff selected by ITU-T Rec. G.994.1. Probe results shall be exchanged by ITU-T Rec. G.994.1. + +In the optional *M*-pair mode, the G.994.1 exchange shall follow the defined procedures for multi-pair operation. In this case, Signals *Pri* and *Pci*, as described below, shall be sent in parallel on all wire pairs. + +### 6.3.2 PMD pre-activation sequence description + +A typical timing diagram for the pre-activation sequence is given in Figure 6-9. Each signal in the pre-activation sequence shall satisfy the tolerance values listed in Table 6-5. + +![Figure 6-9/G.991.2 – Typical timing diagram for pre-activation sequence. This diagram shows the timing of signals between an STU-C and an STU-R. The STU-C side contains a 'G.994.1' block. The STU-R side shows a sequence of signals: P_r1, P_r2, P_r3, P_c1, and P_c2. Timing parameters are indicated: t_hp (handshake period), t_prd (probe duration), t_ps (probe start), t_pcd (probe center), and t_ph (probe end). A label 'G.959.1_F6-9' is present in the bottom right corner of the diagram area.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +Figure 6-9/G.991.2 – Typical timing diagram for pre-activation sequence. This diagram shows the timing of signals between an STU-C and an STU-R. The STU-C side contains a 'G.994.1' block. The STU-R side shows a sequence of signals: P\_r1, P\_r2, P\_r3, P\_c1, and P\_c2. Timing parameters are indicated: t\_hp (handshake period), t\_prd (probe duration), t\_ps (probe start), t\_pcd (probe center), and t\_ph (probe end). A label 'G.959.1\_F6-9' is present in the bottom right corner of the diagram area. + +Figure 6-9/G.991.2 – Typical timing diagram for pre-activation sequence + +**Table 6-5/G.991.2 – Timing for pre-activation signals (Note)** + +| Time | Parameter | Nominal value | Tolerance | +|---------------|--------------------------------------------------------------------------------------------------------|--------------------------------|-------------| +| $t_{hp}$ | Time from end of handshake to start of remote probe | 0.2 s | $\pm 10$ ms | +| $t_{prd}$ | Duration of remote probe | Selectable from 50 ms to 3.1 s | $\pm 10$ ms | +| $t_{ps}$ | Time separating two probe sequences | 0.2 s | $\pm 10$ ms | +| $t_{pre}$ | Time separating last remote and first central probe sequences | 0.2 s | $\pm 10$ ms | +| $t_{pcd}$ | Duration of central probe | Selectable from 50 ms to 3.1 s | $\pm 10$ ms | +| $t_{ph}$ | Time from end of central probe to start of handshake | 0.2 s | $\pm 10$ ms | +| $t_{p-total}$ | Total probe duration, from end of the first G.994.1 session to the start of the second G.994.1 session | 10 s maximum | | + +NOTE – Tolerances are relative to the nominal or ideal value. They are not cumulative across the pre-activation sequence. + +#### 6.3.2.1 Signal $P_{ri}$ + +If the optional line probe is selected during the G.994.1 session (see ITU-T Rec. G.994.1 [2] for details), the STU-R shall send the remote probe signal. The symbol rate for the remote probe signal shall be negotiated during the G.994.1 session, and shall correspond to the symbol rate used during activation for the specified data rate. If multiple remote probe symbol rates are negotiated during the G.994.1 session, then multiple probe signals will be generated, starting with the lowest symbol rate negotiated and ending with the highest symbol rate negotiated. If both symmetric and asymmetric PSD probe signals are selected, the symmetric PSD probe signals shall be sent first, in order of ascending symbol rate, followed by the asymmetric PSD probe signals in order of ascending symbol rate. If symmetric PSD probe signals are selected from both Annexes A and F, then the symmetric PSD probe signals from Annex A will be sent first, followed by the symmetric PSD probe signals from Annex F, all in order of ascending symbol rate. If "transmit silence" is negotiated, then a probe signal consisting of transmitted silence will precede all other probe signals. $P_{ri}$ is the $i$ th probe signal (corresponding to the $i$ th symbol rate negotiated or silence). Waveform $P_{ri}$ shall be generated by connecting the signal $d(m)$ to the input of the STU-R scrambler as shown in Figure 6-8. The PSD mask for $P_{ri}$ shall be the upstream PSD mask used for signal $C_r$ at the same symbol rate, and shall be selectable between the PSDs for activating at data rates of 192 kbit/s to 2304 kbit/s in steps of 64 kbit/s. Note that optional extensions described in Annex F allow the selection of $P_{ri}$ masks corresponding to data rates up to 5696 kbit/s. Alternatively, waveform $P_{ri}$ can be selected to transmit silence. The duration ( $t_{prd}$ ) and power backoff shall be the same for all $P_{ri}$ , and shall be negotiated during the G.994.1 session. The duration shall be selectable between 50 ms and 3.1 s in steps of 50 ms, and the power backoff shall be selectable between 0 dB and 15 dB in steps of 1 dB. The probe signal power backoff can be selected using either the received G.994.1 signal power or *a priori* knowledge. If no information is available, implementors are encouraged to select a probe power backoff of at least 6 dB. The first remote probe signal shall begin $t_{hp}$ after the end of the G.994.1 session. There shall be a $t_{ps}$ second silent interval between successive remote probe signals. + +In the optional $M$ -pair mode, $P_{ri}$ shall be sent in parallel on all wire pairs. + +#### 6.3.2.2 Signal $P_{ci}$ + +The STU-C shall send the central probe signal $t_{pre}$ after the end of the last remote probe signal. The symbol rate for the central probe signal shall be negotiated during the G.994.1 session, and shall + +correspond to the symbol rate used during activation for the specified data rate. If multiple central probe symbol rates are negotiated during the G.994.1 session, then multiple probe signals will be generated, starting with the lowest symbol rate negotiated and ending with the highest symbol rate negotiated. If both symmetric and asymmetric PSD probe signals are selected, the symmetric PSD probe signals shall be sent first, in order of ascending symbol rate, followed by the asymmetric PSD probe signals in order of ascending symbol rate. If symmetric PSD probe signals are selected from both Annexes A and F, then the symmetric PSD probe signals from Annex A will be sent first, followed by the symmetric PSD probe signals from Annex F, all in order of ascending symbol rate. If "transmit silence" is negotiated, then a probe signal consisting of transmitted silence will precede all other probe signals. $P_{ci}$ is the $i$ th probe signal (corresponding to the $i$ th symbol rate negotiated or silence). Waveform $P_{ci}$ shall be generated by connecting the signal $d(m)$ to the input of the STU-C scrambler as shown in Figure 6-8. The PSD mask for $P_{ci}$ shall be the downstream PSD mask used for signal $S_c$ at the same symbol rate, and shall be selectable between the PSDs for activating at data rates of 192 kbit/s to 2304 kbit/s in steps of 64 kbit/s. Note that optional extensions described in Annex F allow the selection of $P_{ci}$ masks corresponding to data rates up to 5696 kbit/s. Alternatively, waveform $P_{ci}$ can be selected to transmit silence. The duration ( $t_{pcd}$ ) and power backoff shall be the same for all $P_{ci}$ , and shall be negotiated during the G.994.1 session. The duration shall be selectable between 50 ms and 3.1 s in steps of 50 ms, and the power backoff shall be selectable between 0 dB and 15 dB in steps of 1 dB. The probe signal power backoff can be selected using either the received G.994.1 signal power or *a priori* knowledge. If no information is available, implementors are encouraged to select a probe power backoff of at least 6 dB. There shall be a $t_{ps}$ silent interval between successive central probe signals, and there shall be a $t_{ph}$ second silent interval between the last central probe signal and the start of the following G.994.1 session. + +In the optional $M$ -pair mode, $P_{ci}$ shall be sent in parallel on all wire pairs. + +### 6.3.3 Scrambler + +The pre-activation mode scrambler shall have the same basic structure as the data mode scrambler, but may employ a different scrambler polynomial. During the G.994.1 session, the scrambler polynomial for the line probe sequence shall be selected by the receiver from the set of allowed scrambler polynomials listed in Table 6-6. The transmitter shall support all the polynomials in Table 6-6. During the line probe sequence, the transmit scrambler shall use the scrambler polynomial selected by the receiver during the G.994.1 session. The scrambler shall be initialized to all zeros. + +**Table 6-6/G.991.2 – Pre-activation scrambler polynomials** + +| Polynomial index
( $i_2, i_1, i_0$ ) | STU-C polynomial | STU-R polynomial | +|-----------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------| +| 0 0 0 | $s(m) = s(m-5) \oplus s(m-23) \oplus d(m)$ | $s(m) = s(m-18) \oplus s(m-23) \oplus d(m)$ | +| 0 0 1 | $s(m) = s(m-1) \oplus d(m)$ | $s(m) = s(m-1) \oplus d(m)$ | +| 0 1 0 | $s(m) = s(m-2) \oplus s(m-5) \oplus d(m)$ | $s(m) = s(m-3) \oplus s(m-5) \oplus d(m)$ | +| 0 1 1 | $s(m) = s(m-1) \oplus s(m-6) \oplus d(m)$ | $s(m) = s(m-5) \oplus s(m-6) \oplus d(m)$ | +| 1 0 0 | $s(m) = s(m-3) \oplus s(m-7) \oplus d(m)$ | $s(m) = s(m-4) \oplus s(m-7) \oplus d(m)$ | +| 1 0 1 | $s(m) = s(m-2) \oplus s(m-3)$
$\oplus s(m-4) \oplus s(m-8) \oplus d(m)$ | $s(m) = s(m-4) \oplus s(m-5)$
$\oplus s(m-6) \oplus s(m-8) \oplus d(m)$ | +| 1 1 0 | Reserved | Reserved | +| 1 1 1 | Not Allowed | Not Allowed | + +### 6.3.4 Mapper + +The output bits from the scrambler, $s(m)$ , shall be mapped to the output level, $y(m)$ , as described in 6.2.4. + +### 6.3.5 Spectral shaper + +The same spectral shaper shall be used for data mode and activation mode as described in 6.1.4. + +### 6.3.6 PMMS target margin + +PMMS target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for $\text{BER} = 10^{-7}$ is greater than or equal to target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. + +The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current-conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. + +The negotiation of the target margins is done as follows: + +The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. + +To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. + +This procedure is applicable to both the current-condition and the worst-case target margins. + +## 6.4 G.994.1 pre-activation sequence + +As noted in 6.3, ITU-T Rec. G.994.1 [2] shall be used to begin the pre-activation sequence. A second G.994.1 sequence shall follow the pre-activation line probe, as described in that clause. The G.994.1 protocol shall be the mechanism for exchanging capabilities and negotiating the operational parameters for each SHDSL connection. The use of a line probe sequence, as described in 6.3, is optional. If each STU has sufficient *a priori* knowledge of the line characteristics and the capabilities of the other STU, either from a previous connection or from user programming, the line probe sequence may be bypassed. In this case, the G.994.1 sequence will be followed by SHDSL activation, as described in 6.2. + +### 6.4.1 G.994.1 code point definitions + +The following definitions shall be applied to the SHDSL parameters specified in ITU-T Rec. G.994.1: + +**6.4.1.1 base data rate/PSD:** These octets are used as follows: + +- for PMMS, they indicate rates for line probing segments; +- for training, they indicate payload data rates; + +Separate bits are provided for symmetric and asymmetric PSDs. + +NOTE – In CLR, upstream training parameters indicate what data mode rates the STU-R is capable of transmitting, and downstream training parameters indicate what data mode rates the STU-R is capable of receiving. In CL, downstream training parameters indicate what data mode rates the STU-C is capable of transmitting, and upstream training parameters indicate what data mode rates the STU-C is capable of receiving. If optional line probe is used, the receiver training parameters will be further limited by the probe results. If repeaters are used, the training parameters of the SRU-R will be further limited by the training parameters of all downstream SRUs and the STU-R. + +**6.4.1.2 clock modes:** Set to indicate clock mode, as defined in Table 10-1. + +**6.4.1.3 diagnostic mode:** Set to indicate a diagnostic mode train (for use with SRUs). + +**6.4.1.4 DRR support:** Indicates whether DRR is supported. See E.10.3. + +**6.4.1.5 four-wire:** Set to indicate four-wire operation. + +**6.4.1.6 lead time:** Indicates the lead time of DRR protocol responses, measured as a number of SHDSL frames. The range of supported values is from 1 to 15. See E.10.3.5. + +**6.4.1.7 low latency:** Set to indicate that low latency operation, as defined in 11.5, is required. If not set, an STU may choose a higher latency encoding scheme. + +**6.4.1.8 *M*-pair count:** Indicates the number of pairs used in the optional *M*-pair mode. + +**6.4.1.9 multiple-pair operation:** Set to indicate *M*-pair mode. Four-wire mode is identical to *M*-pair mode with *M* = 2, except for the method of assigning ordinal numbers to the wire pairs. In four-wire mode, the ordinal numbers (i.e., the wire pair identification number) are assigned as described in 6.3; while in *M*-pair mode, the ordinal numbers are assigned to wire pairs as described in 7.2.1.5. + +**6.4.1.10 PBO:** Power Backoff (in 1.0 dB increments). + +**6.4.1.11 PMMS duration:** The length of each line probe (PMMS) segment (in 50 ms increments). + +**6.4.1.12 PMMS mode:** An indication that an STU (or SRU) is prepared to begin a PMMS ("Power Measurement Modulation Session", or Line Probe) using the associated parameters. + +**6.4.1.13 PMMS scrambler:** The scrambler polynomial used during line probe (PMMS). See 6.3.3. + +**6.4.1.14 PMMS target margin:** If worst-case target margin is selected, target margin is relative to reference worst-case crosstalk specified in Tables A.13 and B.14. If current-condition target margin is selected, specified target margin is relative to noise measured during line probe. The 5-bit target margin is specified by (bits 5-1 $\times$ 1.0 dB) – 10 dB. For example, 101112 in the worst-case PMMS target margin octet corresponds to 15 dB – 10 dB = 5 dB target margin relative to reference worst-case noise. + +If the capability for PMMS mode is indicated in a G.994.1 CLR/CL capabilities exchange, both target margin octets shall be sent. The specific values for target margin shall be ignored during the capabilities exchange, as all STUs (and SRUs) shall be capable of evaluating the results of PMMS using both types of target margin. + +**6.4.1.15 Regenerator Silent Period (RSP):** A bit used to force an STU or SRU into a 1-minute silent interval to facilitate startup of spans including regenerators. + +**6.4.1.16 SRU:** Set to indicate that the unit is a Signal Regenerator and not an STU. + +**6.4.1.17 stuff bits:** Indicates the value that the upstream and downstream *stb1* – *stb4* bits shall take on. See 7.1.2.7 for details. + +**6.4.1.18 sub-data rate:** For symmetric PSDs, the data rate octets indicate the base data rate in 64 kbit/s increments ( $n \times 64$ kbit/s). The sub-data rate bits indicate additional 8 kbit/s increments ( $i \times 8$ kbit/s) of data. The total payload data rate is set by: base data rate + sub-data rate. The sub-data rate bits do not apply to the asymmetric 2.048 Mbit/s, and 2.304 Mbit/s PSDs (from Annex B). For the asymmetric 768 or 776 kbit/s and asymmetric 1.536 or 1.544 Mbit/s PSDs (from Annex A), the base data rate bits indicate 768 kbit/s or 1.536 Mbit/s, and the sub-data rate bits for 0 and 8 kbit/s are valid for selecting the total payload data rate. + +**6.4.1.19 sync word:** Indicates the value that the upstream and downstream *sw1* – *sw14* bits shall take on. See 7.1.2.1 for details. + +**6.4.1.20 TPS-TC:** The TPS-TC mode is selected from the set of modes specified in Annex E. + +**6.4.1.21 training mode:** An indication that an STU (or SRU) is prepared to begin SHDSL activation using the associated parameters. + +**6.4.1.22 warm-start enable:** Set to indicate that warm-start is available. See Annex H. + +### **6.4.2 G.994.1 tone support** + +SHDSL devices shall support half-duplex mode G.994.1 operation using the A4 carrier set from the 4 kHz signalling family. Manufacturers are encouraged to support additional carrier sets, the 4.3125 kHz signalling family, and full-duplex operation of G.994.1 to provide interoperable handshake sequences with other types of DSL equipment. + +### **6.4.3 G.994.1 transactions** + +If no *a priori* capabilities information is available to the STU-R, it should begin the G.994.1 session by initiating Transaction C (CLR/CL). Otherwise, it may begin immediately with one of the mode selection transactions (e.g., A or B). In this capabilities exchange (CLR/CL sequence), each unit shall indicate the functions that it is currently capable of performing. This means that user options that have been disabled shall not be indicated as capabilities of the unit. If a unit's capabilities change due to user option settings or other causes, that unit shall cause a capabilities exchange to occur during the next G.994.1 session. + +If both the STU-R and STU-C indicate the capability for line probing and no *a priori* information exists concerning the characteristics of the loop, the STU-R should initiate Transaction D (MP/MS/Ack(1)) by sending an MP with the G.991.2 line probe mode selected. This MP message shall include parameters for the downstream line probe sequence. The STU-C shall then issue a corresponding MS message containing the upstream line probe parameters and an echo of the downstream line probe parameters. Following an Ack(1) from the STU-R, the units shall exit G.994.1 and enter the G.991.2 line probe mode, as described in 6.3. Following the completion of line probing, the STU-C shall initiate a new G.994.1 session. The STU-R shall then initiate a Transaction C (CLR/CL) capabilities exchange to indicate the results of the line probe. Each unit shall, in this exchange, indicate the intersection of its capabilities and the capabilities of the loop, as determined during the line probe sequence. The PBO octet shall be used to indicate the desired received Power Backoff. Following this second capabilities exchange, the units may use any valid transaction to select operational SHDSL parameters. + +Following the selection of the G.991.2 parameter set, G.994.1 shall terminate and the SHDSL activation sequence (6.2) shall begin. + +### **6.4.4 Operation with signal regenerators** + +In general, SRUs will act as STUs during G.994.1, as described in 6.4.3. In some situations, however, they are required to issue "Regenerator Silent Period" (via the G.994.1 RSP bit) mode selections rather than selecting a G.991.2 operational mode, as described in Annex D and Appendix II. The parameters that SRUs report during capabilities exchanges are also slightly different. The advertised capabilities of an SRU-R shall be the intersection of its own capabilities + +and those reported across the regenerator's internal interface as indicative of the capabilities of the downstream units and line segments. The lone exception to this rule shall be the PBO octet, which shall be considered as a local parameter for each segment. + +# 7 PMS-TC layer functional characteristics + +## 7.1 Data mode operation + +### 7.1.1 Frame structure + +Table 7-1 summarizes the SHDSL frame structure. Complete bit definitions may be found in 7.1.2. + +The size of each payload block is defined as $k$ bits, where $k = 12 (i + n \times 8)$ . The payload data rate is set by: $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . For $n = 36$ , $i$ is restricted to the values of 0 or 1. Note that optional extensions described in Annex F allow values of $n$ up to 89. The value of $i$ shall be negotiated during startup, and shall apply to all values of $n$ . The selected value of $i$ applies to all values of $n$ , will be negotiated during pre-activation, and does not include the 8 kbit/s framing overhead. + +In the optional $M$ -pair mode, $M$ separate PMS-TC sublayers are active – one for each wire pair. In this case, the above formula represents the payload data rate for each pair rather than the aggregate payload rate. All pairs shall operate at the same payload rate, and the transmitters for all pairs shall maintain frame alignment within specified limits. In the STU-C, the symbol clocks for each pair shall be derived from a common source. The maximum differential delay between the start of STU-C frames shall be no greater than four (4) symbols at the line side of each SHDSL transmitter. In the STU-R, symbol clocks may be derived from loop timing on each pair, so these clocks shall be locked in frequency but shall have an arbitrary phase relationship. The maximum differential delay between the start of STU-R frames shall be no greater than six (6) symbols at the line side of each SHDSL transmitter. + +**Table 7-1/G.991.2 – SHDSL frame structure** + +| Time | Frame bit # | Over-head bit # | Name | Description | Notes | +|------|---------------|-----------------|------------------|------------------------------------------|---------------------------| +| 0 ms | 1-14 | 1-14 | sw1-sw14 | Frame Sync Word | | +| | 15 | 15 | fbt1/losd | Fixed Indicator bit #1 (Loss of Signal) | | +| | 16 | 16 | fbt2/sega | Fixed Indicator bit #2 (Segment Anomaly) | | +| | 17 → $k + 16$ | ----- | b1 | Payload block #1 | | +| | $k + 17$ | 17 | eoc01 | EOC bit #1 | | +| | $k + 18$ | 18 | eoc02 | EOC bit #2 | | +| | $k + 19$ | 19 | eoc03 | EOC bit #3 | | +| | $k + 20$ | 20 | eoc04 | EOC bit #4 | | +| | $k + 21$ | 21 | crc1 | Cyclic Redundancy Check #1 | CRC-6 | +| | $k + 22$ | 22 | crc2 | Cyclic Redundancy Check #2 | CRC-6 | +| | $k + 23$ | 23 | fbt3/ps | Fixed Indicator bit #3 (Power Status) | | +| | $k + 24$ | 24 | sbid1 | Stuff bit ID #1 | Spare in synchronous mode | + +**Table 7-1/G.991.2 – SHDSL frame structure** + +| Time | Frame bit # | Over-head bit # | Name | Description | Notes | +|----------------------|-------------------------------|-----------------|------------------|--------------------------------------------|--------------------------------------| +| | $k + 25$ | 25 | eoc05 | EOC bit #5 | | +| | $k + 26$ | 26 | eoc06 | EOC bit #6 | | +| | $k + 27 \rightarrow 2k + 26$ | ----- | b2 | Payload block #2 | | +| | $2k + 27$ | 27 | eoc07 | EOC bit #7 | | +| | $2k + 28$ | 28 | eoc08 | EOC bit #8 | | +| | $2k + 29$ | 29 | eoc09 | EOC bit #9 | | +| | $2k + 30$ | 30 | eoc10 | EOC bit #10 | | +| | $2k + 31$ | 31 | crc3 | Cyclic Redundancy Check #3 | CRC-6 | +| | $2k + 32$ | 32 | crc4 | Cyclic Redundancy Check #4 | CRC-6 | +| | $2k + 33$ | 33 | fbt4/segd | Fixed Indicator bit #4
(Segment Defect) | | +| | $2k + 34$ | 34 | eoc11 | EOC bit #11 | | +| | $2k + 35$ | 35 | eoc12 | EOC bit #12 | | +| | $2k + 36$ | 36 | sbid2 | Stuff bit ID #2 | Spare in synchronous mode | +| | $2k + 37 \rightarrow 3k + 36$ | ----- | b3 | Payload block #3 | | +| | $3k + 37$ | 37 | eoc13 | EOC bit #13 | | +| | $3k + 38$ | 38 | eoc14 | EOC bit #14 | | +| | $3k + 39$ | 39 | eoc15 | EOC bit #15 | | +| | $3k + 40$ | 40 | eoc16 | EOC bit #16 | | +| | $3k + 41$ | 41 | crc5 | Cyclic Redundancy Check #5 | CRC-6 | +| | $3k + 42$ | 42 | crc6 | Cyclic Redundancy Check #6 | CRC-6 | +| | $3k + 43$ | 43 | eoc17 | EOC bit #17 | | +| | $3k + 44$ | 44 | eoc18 | EOC bit #18 | | +| | $3k + 45$ | 45 | eoc19 | EOC bit #19 | | +| | $3k + 46$ | 46 | eoc20 | EOC bit #20 | | +| $6 - 3/ (k + 12)$ ms | $3k + 47 \rightarrow 4k + 46$ | ----- | b4 | Payload block #4 | | +| | $4k + 47$ | 47 | stb1 | Stuff bit #1 | Vendor dependent in synchronous mode | +| 6 ms nominal | $4k + 48$ | 48 | stb2 | Stuff bit #2 | Vendor dependent in synchronous mode | +| | $4k + 49$ | 49 | stb3 | Stuff bit #3 | Not present in synchronous mode | +| $6 + 3/ (k + 12)$ ms | $4k + 50$ | 50 | stb4 | Stuff bit #4 | Not present in synchronous mode | + +### 7.1.2 Frame bit definitions + +In Table 7-1, the bit sequence of the SHDSL frame (prior to scrambling at the transmit side and after descrambling at the receive side) is presented. The frame structures are identical in both upstream and downstream directions of transmission. Spare bits in either direction shall be set to 1. + +The following frame bit definitions are used: + +#### 7.1.2.1 *sw1 – sw14* (Frame Sync Word) + +The frame synchronization word (FSW) enables SHDSL receivers to acquire frame alignment. The FSW (bits *sw1 – sw14*) is present in every frame and is specified independently for the upstream and downstream directions. + +#### 7.1.2.2 *b1 – b4* (Payload Blocks) + +Used to carry user data. The internal structure of the payload blocks is defined in 8.1. + +#### 7.1.2.3 *eoc01 – eoc20* (Embedded Operations Channel) + +20 bits (*eoc01... eoc20*) are provided as a separate maintenance channel. See 9.5 for details. In *M*-pair mode, *eoc01 – eoc20* on Pair 1 shall carry the primary EOC data. The corresponding Pair 2 to Pair *M* *eoc* bits shall be duplicates of the Pair 1 *eoc* bits. + +#### 7.1.2.4 *crc1 – crc6* (Cyclic Redundancy Check code) + +Six bits assigned to a cyclic redundancy check (CRC) code (see 7.1.3). + +#### 7.1.2.5 *fbit1 – fbit4* (Fixed Indicator bits) + +Used for the indication of time-critical framing information. Specific bit definitions are given below. + +##### 7.1.2.5.1 *fbit1 = losd* (Loss of Signal) + +Used to indicate the loss of signal from the application interface. Loss of Signal = 0, Normal = 1. Definition of the conditions causing the indication of *losd* is vendor specific and beyond the scope of this Recommendation. In *M*-pair mode, *losd* on Pair 1 shall carry the primary *losd* indication. The *losd* bit on all other pairs shall be duplicates of the Pair 1 bit. + +##### 7.1.2.5.2 *fbit2 = sega* (Segment Anomaly) + +Used to indicate a CRC error on the incoming SHDSL frame. A segment anomaly indicates that a regenerator operating on a segment has received corrupted data and therefore the regenerated data is unreliable. The purpose of segment anomaly is to ensure internal performance monitoring integrity; it is not intended to be reported to an external management entity. CRC Error = 0, Normal = 1. + +###### 7.1.2.5.2.1 STU operation + +The STU shall set the *sega* bit to 1. + +###### 7.1.2.5.2.2 SRU operation + +If a CRC error is declared for an incoming frame, an SRU shall set the *sega* bit to 0 in the next available outgoing frame in the forward direction, i.e., in the direction of the data over which the CRC error was observed. If no CRC error is declared, then an SRU shall pass the *sega* bit without modification. + +##### 7.1.2.5.3 *fbit3 = ps* (Power Status) + +The power status bit *ps* is used to indicate the status of the local power supply in the STU-R. The power status bit is set to 1 if power is normal and to 0 if the power has failed. On loss of power at the STU-R, there shall be enough power left to send the *ps* bit in at least one and preferably + +three consecutive frames towards the STU-C. Note that, in the event of a power failure, the *ps* bit should be set to 0 for as many frames as possible before deactivation. If the *ps* bit is set for less than three frames, it is up to the application at the STU-C to determine the validity of the message. Regenerators shall pass this bit transparently. In *M*-pair mode, *ps* on Pair 1 shall carry the primary power status indication. The *ps* bit on all other pairs shall be duplicates of the Pair 1 *ps* bit. + +##### 7.1.2.5.4 *fbit4* = *segd* (Segment Defect) + +Used to indicate a loss of sync on the incoming SHDSL frame. A segment defect indicates that a regenerator has lost synchronization and therefore the regenerated data is unavailable. This bit is typically reported to an external management entity and is used to ensure timely protection switching, alarm filtering, etc. Loss of Sync = 0, Normal = 1. + +###### 7.1.2.5.4.1 STU operation + +The STU shall set the *segd* bit to 1. + +###### 7.1.2.5.4.2 SRU operation + +If a LOSW-Defect is declared, an SRU shall set the *segd* bit to 0 in the next available outgoing frame in the forward direction, i.e., in the direction of the data over which the LOSW-Defect was observed. If no LOSW-Defect is declared, then an SRU shall pass the *segd* bit without modification. + +#### 7.1.2.6 *sbid1*, *sbid2* (Stuff Indicator bits) + +In plesiochronous mode, the stuff indicator bits indicate whether or not a stuffing event occurs in the frame. Both bits shall be set to 1 if the four stuff bits are present at the end of the current frame. Both bits shall be set to 0 if there are no stuff bits at the end of the current frame. In synchronous mode, *sbid1* and *sbid2* are spare bits. + +#### 7.1.2.7 *stb1* – *stb4* (Stuffing Bits) + +In plesiochronous mode, these bits are used together. Either zero or four stuffing bits are inserted, depending on the relation of the timing between the upstream and downstream channels. In synchronous framing mode, *stb1* and *stb2* are present in every frame, and *stb3* and *stb4* are not present. The values of *stb1* – *stb4* are specified independently for the upstream and downstream directions. + +### 7.1.3 CRC Generation (*crc1* ... *crc6*) + +A cyclic redundancy check (CRC) shall be generated for each frame and transmitted on the following frame. The six CRC bits (*crc1* to *crc6*) shall be the coefficients of the remainder polynomial after the message polynomial, multiplied by $D^6$ , is divided by the generating polynomial. The message polynomial shall consist of all bits in the frame except for the synchronization word, CRC bits, and the stuff bits. (There are thus $4k + 26$ message bits in a frame that are covered by the CRC check.) The message bits shall be ordered as in the frame itself, i.e., $m_0$ is the first bit, $m_1$ is the second bit, etc. The CRC check bits shall be calculated according to the equation: + +$$crc(D) = m(D)D^6 \bmod g(D)$$ + +where: + +$$m(D) = m_0 D^{4k+25} \oplus m_1 D^{4k+24} \oplus \dots \oplus m_{4k+24} D \oplus m_{4k+25}$$ + +is the message polynomial, + +$$g(D) = D^6 \oplus D \oplus 1$$ + +is the generating polynomial, + +$$crc(D) = crc1 D^5 \oplus crc2 D^4 \oplus \dots \oplus crc5 D \oplus crc6$$ + +is the CRC check polynomial, $\oplus$ indicates modulo-2 addition (exclusive OR), and $D$ is the delay operator. + +### 7.1.4 Frame synchronization + +In plesiochronous clocking mode, SHDSL uses a variable length PMS-TC frame and bit stuffing to synchronize the PMS-TC frame rate with the incoming payload rate. Quick acquisition of frame synchronization and the ability to maintain frame synchronization in the presence of errors are important properties of the frame structure. + +Three types of bit fields are provided for use in frame synchronization: Frame Sync Word, Stuff Bits, and Stuff Bit IDs. The Frame Sync Word is 14 bits long and is present on every frame. The stuff bits are four contiguous bits which are present only at the end of long frames. Stuff Bit IDs are two bits distributed within the frame which indicate whether the current frame contains the four stuffing bits. These distributed bits provide improved immunity to frame alignment errors caused by burst errors. + +The precise manner in which this information is used to acquire or maintain frame synchronization is the choice of the receiver designer. Since different frame synchronization algorithms may require different values for the bits of the FSW and Stuff Bits, a provision has been made to allow the receiver to inform the far end transmitter of the particular values that are to be used for these fields in the transmitted PMS-TC frame. + +### 7.1.5 Scrambler + +The scrambler in the STU-C and the STU-R transmitters shall operate as shown in Figures 7-1 and 7-2, respectively. In these figures, $T_b$ indicates a delay of one bit duration and $\oplus$ is the binary exclusive-OR operation. The frame sync word bits and the stuff bits in the SHDSL data mode frame (Table 7-1) shall not be scrambled. While the frame sync word bits and stuff bits are present at $f(n)$ , the scrambler shall not be clocked, and $f(n)$ shall be directly connected to $s(n)$ . + +#### 7.1.5.1 STU-C scrambler + +The block diagram of the STU-C scrambler is shown in Figure 7-1. + +![Block diagram of the STU-C scrambler showing a feedback shift register with a bypass switch for sync/stuff bits.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) + +The diagram illustrates the STU-C scrambler logic. The input $f(n)$ enters an XOR gate (represented by a circle with a plus sign). The output of this XOR gate is fed into a series of delay blocks, each labeled $T_b$ . The output after the first delay is $s(n-1)$ . After several more delays, the signal reaches a point labeled $s(n-5)$ , which is tapped and fed into a second XOR gate. The delay chain continues until the final output $s(n-23)$ , which is also fed into the second XOR gate. The output of this second XOR gate is fed back to the first XOR gate. A switch, controlled by the condition "Frame sync word bits or stuff bits present" (indicated by a dashed arrow), allows the input $f(n)$ to bypass the scrambling logic and connect directly to the output $s(n)$ when the condition is met. The diagram is labeled with G.991.2\_F7-1 at the bottom right. + +Block diagram of the STU-C scrambler showing a feedback shift register with a bypass switch for sync/stuff bits. + +**Figure 7-1/G.991.2 – Block diagram of the STU-C scrambler** + +#### 7.1.5.2 STU-R scrambler + +The block diagram of the STU-R scrambler is shown in Figure 7-2. + +![Block diagram of the STU-R scrambler. The input f(n) is added to a feedback signal at a summer. The output of this summer is s(n), which is also the input to a series of delay blocks labeled T_b. The output of the last delay block is s(n-23). This signal is added to the output of another delay block, s(n-18), at a second summer. The output of the second summer is fed back to the first summer. A dashed line points to the output s(n) with the text 'Frame sync word bits or stuff bits present'. The diagram is labeled G.991.2_F7-2.](1142ba0197b158bb198186fe8baccc32_img.jpg) + +``` + +graph LR + fn("f(n)") --> sum1(("+")) + sum1 --> sn("s(n)") + sn --> Tb1["Tb"] + Tb1 --> sn1("s(n-1)") + sn1 --> Tb2["Tb"] + Tb2 --> dots1("...") + dots1 --> Tb18["Tb"] + Tb18 --> sn18("s(n-18)") + sn18 --> Tb19["Tb"] + Tb19 --> dots2("...") + dots2 --> Tb23["Tb"] + Tb23 --> sn23("s(n-23)") + sn18 --> sum2(("+")) + sn23 --> sum2 + sum2 --> sum1 + sync("Frame sync word bits or +stuff bits present") -.-> switch + switch --> sn + +``` + +Block diagram of the STU-R scrambler. The input f(n) is added to a feedback signal at a summer. The output of this summer is s(n), which is also the input to a series of delay blocks labeled T\_b. The output of the last delay block is s(n-23). This signal is added to the output of another delay block, s(n-18), at a second summer. The output of the second summer is fed back to the first summer. A dashed line points to the output s(n) with the text 'Frame sync word bits or stuff bits present'. The diagram is labeled G.991.2\_F7-2. + +Figure 7-2/G.991.2 – Block diagram of the STU-R scrambler + +### 7.1.6 Differential delay buffer + +In the optional $M$ -pair mode, it is understood that the characteristics of the $M$ wire pairs may differ. Differences in wire diameter, insulation type, length, number and length of bridged taps and exposure to impairments may result in differences in transmission time between pairs. It is recommended that such differences in signal transfer delay between any two pairs be limited to a maximum of $50\ \mu\text{s}$ at $150\ \text{kHz}$ , corresponding to about $10\ \text{km}$ difference in line length between STU-R and STU-C. + +In transceivers supporting $M$ -pair mode, a delay difference buffer shall be implemented to compensate for any difference in total transmission time of the SHDSL frames on different pairs. Such delay differences may be due to the pair differences described above, as well as to delays due to signal processing in the SHDSL transceivers in the STU-C, STU-R and possible signal regenerators. The function of this delay difference buffer is to align the SHDSL frames so that frames can be correctly reassembled. This buffer shall be capable of absorbing a delay difference of at least 6 symbols + $50\ \mu\text{s}$ at the line side of each SHDSL receiver. + +## 7.2 PMS-TC activation + +### 7.2.1 Activation frame + +The format of the activation frame is shown in Table 7-2. A $T_c$ or $T_r$ signal shall be generated by repetitively applying the activation frame information shown in Table 7-2 to the STU scrambler as shown in Figure 6-5. The activation frame contents shall be constant during the transmission of $T_c$ and $T_r$ . The activation frame sync bits are not scrambled, so they shall be applied directly to the uncoded 2-PAM constellation. The total number of bits in the activation frame is 4227. The activation frame shall be sent starting with bit 1 and ending with bit 4227. + +In the optional $M$ -pair mode, activation shall proceed in parallel on each of the $M$ wire pairs. + +**Table 7-2/G.991.2 – Activation frame format** + +| Activation frame bit LSB:MSB | Definition | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 1:14 | Frame Sync for $T_c$ and $T_r$ : 11111001101011 2 , where the left-most bit is sent first in time | +| | Frame Sync for $F_c$ : 11010110011111 2 , where the left-most bit is sent first in time | +| 15:36 | Precoder Coefficient 1: 22 bit signed two's complement format with 17 bits after the binary point, where the LSB is sent first in time | +| 37:58 | Precoder Coefficient 2 | +| 59:3952 | Precoder Coefficients 3-179 | +| 3953:3974 | Precoder Coefficient 180 | +| 3975:3995 | Encoder Coefficient A: 21 bits where the LSB is sent first in time | +| 3996:4016 | Encoder Coefficient B: 21 bits where the LSB is sent first in time | +| 4017:4144 | Vendor Data: 128 bits of proprietary information | +| 4145:4146 | M -pair mode: STU-C: Number of wire pairs/STU-R: Ordering of wire pairs | +| 4147:4211 | Reserved: 65 bits set to logical zeros | +| 4212:4227 | CRC: $c_1$ sent first in time, $c_{16}$ sent last in time | + +#### 7.2.1.1 Frame sync + +The frame sync for $T_c$ and $T_r$ is a 14-bit code. In binary, the code shall be 11111001101011, and shall be sent from left to right. For $F_c$ , the frame sync shall be 11010110011111, or the reverse of the frame sync for $T_c$ and $T_r$ . + +#### 7.2.1.2 Precoder coefficients + +The precoder coefficients are represented as 22-bit two's complement numbers, with the five most significant bits representing integer numbers from $-16$ (10000) to $+15$ (01111), and the remaining 17 bits are the fractional bits. The coefficients are sent sequentially, starting with coefficient $C_1$ and ending with coefficient $C_N$ (from Figure 6-4), and the least significant bit of each coefficient is sent first in time. The minimum number of precoder coefficients shall be 128 and the maximum number shall be 180. If fewer than 180 precoder coefficients are used, the remaining bits in the field shall be set to zero. + +#### 7.2.1.3 Encoder coefficients + +Referring to Figure 6-3, the coefficients for the programmable encoder are sent in the following order: $a_0$ is sent first in time, followed by $a_1, a_2, \dots$ , and $b_{20}$ is sent last in time. + +#### 7.2.1.4 Vendor data + +These 128 bits are reserved for vendor-specific data. + +#### 7.2.1.5 *M*-pair mode: Ordering of wire pairs + +In the optional *M*-pair mode these two bits are used to define the order of the *M* wire pairs. They are used to determine how user data is split into *M* loops at the transmitter and combined in the receiver as specified in 7.1.1. The assignment of loop 1 to loop *M* is vendor-specific. + +Bits 4145 to 4146 in the activation frame of the STU-C device are used to specify the number *M* of wire pairs. LSB first. $M = 1: 00_2$ ; $M = 2: 10_2$ ; $M = 3: 01_2$ ; $M = 4: 11_2$ . This activation frame entry is identical on all *M* wire pairs. + +Bits 4145 to 4146 of the activation frame of the STU-R device are used to identify the ordinal number of each of the $M$ wire pairs. LSB first. Wire pair 1: $00_2$ ; wire pair 2: $10_2$ ; wire pair 3: $01_2$ ; wire pair 4: $11_2$ . This activation frame entry is different on each of the $M$ wire pairs. + +If the system is not operating in $M$ -pair mode, these two bits shall be set to logical zeros. In four-wire mode, the ordinal numbers are assigned as described in 6.3, and bits 4145 to 4146 of the activation frame shall be set to zero. + +#### 7.2.1.6 Reserved + +These 65 bits are reserved for future use and shall be set to logical zeros. + +#### 7.2.1.7 CRC + +The sixteen CRC bits ( $c_1$ to $c_{16}$ ) shall be the coefficients of the remainder polynomial after the message polynomial, multiplied by $D^{16}$ , is divided by the generating polynomial. The message polynomial shall be composed of the bits of the activation frame, where $m_0$ is bit 15 and $m_{4196}$ is bit 4211 of the activation frame, such that: + +$$crc(D) = m(D)D^{16} \bmod g(D)$$ + +where: + +$$m(D) = m_0D^{4196} \oplus m_1D^{4195} \oplus \dots \oplus m_{4195}D \oplus m_{4196}$$ + +is the message polynomial, + +$$g(D) = D^{16} \oplus D^{12} \oplus D^5 \oplus 1$$ + +is the generating polynomial, + +$$crc(D) = c_1D^{15} \oplus c_2D^{14} \oplus \dots \oplus c_{15}D \oplus c_{16}$$ + +is the CRC check polynomial, $\oplus$ indicates modulo-2 addition (exclusive OR), and $D$ is the delay operator. + +### 7.2.2 Activation scrambler + +The scrambler in the STU-C and the STU-R transmitters (see Figure 6-5) shall operate as shown in Figures 7-1 and 7-2, where $T_b$ is a delay of one bit duration, and $\oplus$ is binary exclusive-OR. The frame sync bits in the activation frame shall not be scrambled. While the frame sync bits are present at $f(n)$ , the scrambler shall not be clocked, and $f(n)$ shall be directly connected to $s(n)$ . + +# 8 TPS-TC layer functional characteristics + +## 8.1 Payload block data structure + +Each payload block shall consist of 12 Sub-blocks, and shown in Figure 8-1. The size of each payload sub-block is defined as $k_s$ , where $k_s = i + n \times 8$ [bits]. As stated in 7.1, the payload data rate is set by: $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . For $n = 36$ , $i$ is restricted to the values of 0 or 1. Note that optional extensions described in Annex F allow values of $n$ up to 89. All structure of data within payload sub-blocks (i.e., support for clear broadband channels, subchannels, and region-specific services) is specified in Annex E. + +![Diagram showing the structure of payload blocks. A horizontal sequence of fields includes Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. A callout from the first Payload block shows it is composed of 12 vertical sub-blocks labeled Sub-Block 1 through Sub-Block 12.](77959075c823bb5169480d7b8ff82a63_img.jpg) + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + + + +| | +|--------------| +| Sub-Block 1 | +| Sub-Block 2 | +| Sub-Block 3 | +| Sub-Block 4 | +| Sub-Block 5 | +| Sub-Block 6 | +| Sub-Block 7 | +| Sub-Block 8 | +| Sub-Block 9 | +| Sub-Block 10 | +| Sub-Block 11 | +| Sub-Block 12 | + +G.991.2\_F8-1 + +Diagram showing the structure of payload blocks. A horizontal sequence of fields includes Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. A callout from the first Payload block shows it is composed of 12 vertical sub-blocks labeled Sub-Block 1 through Sub-Block 12. + +**Figure 8-1/G.991.2 – Structure of payload blocks** + +## 8.2 Data interleaving in *M*-pair mode + +In the optional *M*-pair mode, interleaving of payload data between pairs is necessary. This shall be accomplished by interleaving within payload sub-blocks among all pairs. $k_s$ bits in each sub-block shall be carried on Pair 1, and an additional $k_s$ bits shall be carried on each of the other pairs, as shown in Figure 8-2 for the case of $M = 2$ . The size of each payload sub-block is defined as $M \times k_s$ , where $k_s = i + n \times 8$ . As stated in 7.1, the payload data rate per pair is set by: $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . For $n = 36$ , $i$ is restricted to the values of 0 or 1. Note that optional extensions described in Annex F allow values of $n$ up to 89. All structure of data within payload sub-blocks (i.e., support for clear broadband channels, subchannels, and region-specific services) is specified in Annex E. + +![Diagram showing data interleaving within payload blocks. A top-level frame containing sync, OH, and payload blocks is expanded into 12 sub-blocks. These sub-blocks are then mapped into two separate payload data streams for Pair 1 (bits 1 to k_s) and Pair 2 (bits k_s + 1 to 2k_s).](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +Aligned Pair 1 and Pair 2 frames + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + + + +Pair 1 and Pair 2 + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + + + +Pair 1 + +| | +|-------------------------------| +| Payload data, bits 1 to $k_s$ | +|-------------------------------| + +Pair 2 + +| | +|----------------------------------------| +| Payload data, bits $k_s + 1$ to $2k_s$ | +|----------------------------------------| + +G.991.2\_F8-2 + +Diagram showing data interleaving within payload blocks. A top-level frame containing sync, OH, and payload blocks is expanded into 12 sub-blocks. These sub-blocks are then mapped into two separate payload data streams for Pair 1 (bits 1 to k\_s) and Pair 2 (bits k\_s + 1 to 2k\_s). + +**Figure 8-2/G.991.2 – Data interleaving within payload blocks** + +# 9 Management + +## 9.1 Management reference model + +![Management reference model diagram. It shows a linear path of devices: Customer Premises Equipment (CPE) connected to STU-R, which connects through two SRUs to STU-C, and finally to a Path Terminating Device (PTD). Above the STU-R, SRUs, and STU-C are labels for 'N Side' (Network) and 'C Side' (Customer) with curved arrows pointing to the respective interfaces. Below the devices, horizontal spans are labeled: 'Application specific' (between CPE and STU-R, and between STU-C and PTD), 'SHDSL segment' (between STU-R/SRU and SRU/STU-C), 'SHDSL span' (covering the three SHDSL segments), and 'User data path' (covering the entire span from CPE to PTD).](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +G.991.2\_F9-1 + +Management reference model diagram. It shows a linear path of devices: Customer Premises Equipment (CPE) connected to STU-R, which connects through two SRUs to STU-C, and finally to a Path Terminating Device (PTD). Above the STU-R, SRUs, and STU-C are labels for 'N Side' (Network) and 'C Side' (Customer) with curved arrows pointing to the respective interfaces. Below the devices, horizontal spans are labeled: 'Application specific' (between CPE and STU-R, and between STU-C and PTD), 'SHDSL segment' (between STU-R/SRU and SRU/STU-C), 'SHDSL span' (covering the three SHDSL segments), and 'User data path' (covering the entire span from CPE to PTD). + +NOTE – N = Network, C = Customer. + +**Figure 9-1/G.991.2 – Management reference model** + +Figure 9-1 shows the Management Reference Model for user data transport over SHDSL. This example includes two regenerator units for informative purposes. The presence of two regenerators is not intended to be a requirement or limit. An SHDSL segment is characterized by a metallic transmission medium utilizing an analogue coding algorithm, which provides both analogue and digital performance monitoring at the segment entity. An SHDSL segment is delimited by its two end points, known as segment terminations. An SHDSL segment termination is the point at which the analogue coding algorithms end and the subsequent digital signal is monitored for integrity. + +All SHDSL performance monitoring data is transported over the EOC. The fixed indicator bits in the SHDSL frame are used for rapid communication of interface or SHDSL segment defects, which may lead to protection switching. In addition, the fixed indicator bits may be used for rapid alarm filtering SHDSL segment failures. + +## 9.2 SHDSL performance primitives + +### 9.2.1 Cyclical Redundancy Check Anomaly (CRC Anomaly) + +A CRC anomaly shall be declared when the CRC bits generated locally on the data in the received SHDSL frame do not match the CRC bits (*crc1* – *crc6*) received from the transmitter. A CRC anomaly only pertains to the frame over which it was declared. + +### 9.2.2 Segment Anomaly (SEGA) + +An upstream segment anomaly shall be declared when any SRU declares a CRC anomaly for an SHDSL frame moving in the direction from STU-R to STU-C. A downstream segment anomaly shall be declared when any SRU declares a CRC anomaly for an SHDSL frame moving in the direction from STU-C to STU-R. A segment anomaly indicates that a regenerator operating on a segment has received corrupted data and therefore the regenerated data is unreliable. The purpose of segment anomaly is to ensure internal SHDSL PMD integrity; it is not intended to be reported to an external management entity. A segment anomaly is indicated via the *sega* bit in the SHDSL frame (7.1.2.5.2). + +### 9.2.3 Loss of Sync Defect (LOSW defect) + +In plesiochronous mode, an LOSW defect shall be declared when at least three consecutive received frames contain one or more errors in the framing bits. The term framing bits shall refer to that portion of Frame Sync Word, Stuff Bits and Stuff Bit Ids, which are used for frame synchronization. An LOSW defect shall be cleared when at least two consecutive received frames contain no errors in the framing bits. + +In synchronous mode, an LOSW defect shall be declared when at least three consecutive received frames contain one or more bit errors in the Frame Sync Word. An LOSW defect shall be cleared when at least two consecutive received frames contain no errors in the Frame Sync Word. + +### 9.2.4 Segment Defect (SEGD) + +An upstream segment defect shall be declared when any SRU declares a LOSW defect for data moving in the direction from STU-R to STU-C. A downstream segment defect shall be declared when any SRU declares a LOSW defect for data moving in the direction from STU-C to STU-R. A segment defect indicates that a regenerator has lost SHDSL synchronization and therefore the regenerated data is unavailable. A segment defect shall be cleared when all SRUs have no LOSW defects. This primitive is typically reported to an external management entity and is used to ensure timely protection switching, alarm filtering, etc. A segment defect is indicated via the *segd* bit in the SHDSL frame (7.1.2.5.4). + +### **9.2.5 Loop attenuation defect** + +A Loop Attenuation Defect shall be declared when the observed Loop Attenuation is at a level higher than the configured threshold (9.5.5.7.5). + +### **9.2.6 SNR margin defect** + +An SNR Margin Defect shall be declared when the observed SNR Margin is at a level lower than the configured threshold (9.5.5.7.5). SNR Margin is defined as the maximum dB increase in equalized noise or the maximum dB decrease in equalized signal that a system can tolerate and maintain a BER of $10^{-7}$ . + +### **9.2.7 Loss of Sync Word Failure (LOSW failure)** + +An LOSW failure shall be declared after $2.5 \pm 0.5$ s of contiguous LOSW defect. The LOSW failure shall be cleared when the LOSW defect is absent between 2 and 20 s. The minimum hold time for indication of LOSW failure shall be 2 s. + +## **9.3 SHDSL line related performance parameters** + +### **9.3.1 Code Violation (CV)** + +The SHDSL parameter Code Violation is defined as a count of the SHDSL CRC anomalies occurring during the accumulation period. This parameter is subject to inhibiting – see 9.3.6. + +### **9.3.2 Errored Second (ES)** + +The SHDSL parameter Errored Second is defined as a count of 1-second intervals during which one or more CRC anomalies are declared and/or one or more LOSW defects are declared. This parameter is subject to inhibiting – see 9.3.6. + +### **9.3.3 Severely Errored Second (SES)** + +The SHDSL parameter Severely Errored Second is defined as a count of 1-second intervals during which at least 50 CRC anomalies are declared or one or more LOSW defects are declared. (50 CRC anomalies during a 1-second interval is equivalent to a 30% errored frame rate for a nominal frame length.) This parameter is subject to inhibiting – see 9.3.6. + +### **9.3.4 LOSW Second (LOSWS)** + +The SHDSL parameter LOSW Second is defined as a count of 1-second intervals during which one or more SHDSL LOSW defects are declared. + +### **9.3.5 Unavailable Second (UAS)** + +The SHDSL parameter Unavailable Second is a count of 1-second intervals for which the SHDSL line is unavailable. The SHDSL line becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time. Once unavailable, the SHDSL line becomes available at the onset of 10 contiguous seconds with no SESs. The 10 s with no SESs are excluded from unavailable time. + +### **9.3.6 Inhibiting rules** + +- UAS parameter counts shall not be inhibited. +- ES and SES shall be inhibited during UAS. Inhibiting shall be retroactive to the onset of unavailable time and shall end retroactively to the end of unavailable time. +- The CV parameter shall be inhibited during SES. + +Further information on inhibiting rules and how ES and SES are decremented can be found in IETF RFC 2495: Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types [B9]. + +## 9.4 Performance data storage + +In order to support SHDSL performance history storage at the STU-C, each SHDSL network element shall monitor performance and maintain a modulo counter for each performance parameter that is specified in 9.5.5.7.14 and 9.5.5.7.15, as appropriate. No initialization of these modulo counters is specified or necessary. By comparing the current reading of the modulo counter with the previous reading stored in memory, the data base manager in the STU-C can determine the number of counts to add to the appropriate performance history bin. (Note that the number of counts may decrease under some fault conditions – see 9.3 for additional information.) The modulo counters are reported in the SHDSL Performance Status Messages (9.5.5.7.14 and 9.5.5.7.15). + +The STU-C shall collect performance history by polling each SHDSL network element with a time interval that precludes overflow of the modulo counter. For example, the modulo counter for Errored Seconds is 8 bits which allows a maximum of 255 s between polls before overflow may occur. Note that the polling that is referred to herein is implemented by the internal database manager in the STU-C rather than an external network manager. + +The STU-C shall maintain performance history bins for each SHDSL segment endpoint. The performance history bins shall include the total collected counts for the current 15-minute period, 32 previous 15-minute periods, current 24-hour period, and 7 previous 24-hour periods. + +## 9.5 Embedded operations channel + +### 9.5.1 Management reference model + +The STU-C shall maintain a management information database for external access by network management or via craft interface. + +Optionally, the STU-R may maintain a management information database, which can be locally accessed (through a craft interface). This is particularly useful when the STU-C, due to fault conditions, is unreachable via the EOC. + +Access to the management information database from craft interfaces on attached units shall be provided through a virtual-terminal interface. + +### 9.5.2 EOC overview and reference model + +The EOC allows terminal units to maintain information about the span. There are two basic flows of data, differentiated by which terminal unit initiates the data flow (and subsequently stores the information for external access). The data flow initiating from the STU-C is mandatory. The data flow initiating from the STU-R is optional, but all units must respond to requests in either direction of data flow. In all cases the "master database" shall be stored at the STU-C and all conflicts shall be resolved in favour of the STU-C (i.e., the information at the STU-C takes precedence). The data flows are illustrated in Table 9-1 for a two regenerator link (Q denotes a query or command message, R denotes a response message). Up to eight regenerators are supported by the protocol definition. Asterisks denote optional message transmissions. A block diagram example of a link with two regenerators is shown in Figure 9-1. + +**Table 9-1/G.991.2 – Illustration of EOC flow with two regenerators** + +| Messages from STU-C Msg(src,dest) | Messages from SRU1 Msg(src,dest) | Messages from SRU2 Msg(src,dest) | Messages from STU-R Msg(src,dest) | +|-----------------------------------|----------------------------------|----------------------------------|-----------------------------------| +| Q(1,3) → | → Process | | | +| Process ← | ← R(3,1) | | | +| Q(1,4) → | → Forward → | → Process | | +| Process ← | ← Forward ← | ← R(4,1) | | +| Q(1,2) → | → Forward → | → Forward → | → Process | +| Process ← | ← Forward ← | ← Forward ← | ← R(2,1) | +| | | | | +| | | Process ← | ← Q(2,3)* | +| | | R(3,2) → | → Process | +| | Process ← | ← Forward ← | ← Q(2,4)* | +| | R(4,2) → | → Forward → | → Process | +| Process ← | ← Forward ← | ← Forward ← | ← Q(2,1)* | +| R(1,2) → | → Forward → | → Forward → | → Process | + +\* Indicates optional messages. + +The data link layer of SHDSL EOC checks the FCS and if valid passes the packet to the network layer. If the CRC is invalid the entire packet is ignored. The network layer consists of three possible actions: Process, Forward, and Ignore/Terminate. Process means that the source address and HDLC information field are passed on to the application layer. Forward means that the packet is sent onward to the next SHDSL element. (Note that only SRUs will forward packets.) Ignore/Terminate means that the HDLC packet is ignored and is not forwarded. An SRU may both process and forward a packet in the case of a broadcast message. If the segment is not active in the forwarding direction, the SRU shall discard the packet instead. When the segment is active in the forwarding direction, the maximum forwarding delay in an SRU shall be 300 ms. All retransmission and flow control is administered by the endpoints, the STUs. + +To accommodate the dual data flows, SHDSL regenerators have dual addresses as shown in Table 9-1. One address is for communication with the STU-C and the other address is for communication with the STU-R. During Discovery, the STU-C and optionally the STU-R send discovery probe messages, which propagate across the span and allow the SRUs to be numbered via a hop count field in the message. This process is explained in detail below. + +The SHDSL terminal units communicate unidirectionally and thus have only one address. The STU-C is assigned a fixed address of 1 and the STU-R is assigned a fixed address of 2. At power-up, each SRU is assigned the address of 0 for each direction. Under a LOSW failure condition, the SRU shall reset its source address to 0 for the direction in which the LOSW failure exists. The SRU source address shall be changed from 0 if and only if a discovery probe message is received and processed. In this way, a regenerator will only communicate in the direction of a database. For instance, if a regenerator receives a probe message from the STU-C and not from the STU-R, then its address will remain 0 in the direction towards the remote. + +### 9.5.3 EOC startup + +After loop activation, the SHDSL EOC goes through three initialization stages: Discovery, Inventory and Configuration. During Discovery, the STU-C and optionally the STU-R will learn if any mid-span regenerators exist and their addresses will be determined. During Inventory, the STU-C will poll each SRU and the STU-R to establish inventory information on each element for + +the terminal unit's database. (Similarly, the STU-R may poll each SRU and the STU-C to establish its own database, although this is optional.) During Configuration, the STU-C configures the STU-R and any SRUs for alarm thresholds, signal characteristics, etc. There is no enforcement of the order or time of the Inventory and Configuration phases; the initiating STU is in control. + +Table 9-12 is an example of Discovery starting from the STU-C and then followed by an optional Discovery initiated by the STU-R. Although these are shown sequentially in this example, they are actually independent; it is not necessary for the STU-R to wait until it received the probe from the STU-C before initiating its own Discovery phase. The STU-R may send its probe as soon as its EOC is active. The Discovery Response contains the current hop count, the vendor ID, EOC version and an indication of LOSW in the forward direction (i.e., in the direction of EOC flow that is opposite to the direction that the Discovery Response is sent). + +**Table 9-2/G.991.2 – Illustration of EOC discovery phase** + +| Messages from STU-C
Msg(src,dest,h) | Messages from SRU1
Msg(src,dest,h) | Messages from SRU2
Msg(src,dest,h) | Messages from STU-R
Msg(src,dest,h) | +|------------------------------------------------|-----------------------------------------------|-----------------------------------------------|------------------------------------------------| +| DP(1,0,0) → | | | | +| | ← DR(3,1,1) | | | +| | DP(0,0,1) → | | | +| | ← Forward ← | ← DR(4,1,2) | | +| | | DP(0,0,2) → | | +| | ← Forward ← | ← Forward ← | ← DR(2,1,3) | +| | | | ← DP(2,0,0) | +| | | DR(3,2,1) → | | +| | | ← DP(4,0,1) | | +| | DR(4,2,2) → | → Forward → | | +| | ← DP(3,0,2) | | | +| DR(1,2,3) → | → Forward → | → Forward → | | + +NOTE – h = hop count, DP = Discovery Probe, DR = Discovery Response. + +After the Initiator (STU-C and optionally STU-R) has received a Discovery Response message from an element, it shall then begin the Inventory phase for that particular element. This is accomplished by polling that particular element for its inventory information. After the Initiator has received the inventory information for a unit, it shall then begin the Configuration phase by sending the appropriate configuration information to the corresponding element. The Inventory and Configuration Phases operate independently for each responding terminal/regenerator unit. + +To ensure interoperability, the behaviour of slave or responding units is carefully specified by this Recommendation. The particular method for handling dropped packets or no response is left to the discretion of the initiating STU. + +Table 9-3 shows the EOC state table for the network side of an SRU. Note that an identical, but independent, state machine exists for the customer side of an SRU to support messages originating from the STU-R. + +The state machine consists of three states: Offline, Discovery and EOC Online. The Offline state is characterized by LOSW failure (a loss of SHDSL sync). The Discovery state is characterized by an unknown address. Once the address is learned through the Discovery message, the SRU enters the EOC online or active state. At this point, the SRU will respond to inventory, configuration, maintenance, or other messages from the STU-C. + +**Table 9-3/G.991.2 – SRU network EOC state table** + +#### **Offline state** + +| Event | Action | +|------------------|-----------------------------| +| Network LOSW = 0 | EOC State = Discovery Ready | + +#### **Discovery ready state** + +| Event | Action | +|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Network LOSW = 1 | Network EOC Address = 0
Network EOC State = Offline | +| Discovery probe message received from the Network side | Increment Hop Count
Set Network EOC address to Hop Count +2
Compose and present Discovery message to Customer side application layer
Send Discovery Response to STU-C
Network EOC State = EOC Online | +| Message with address not equal to unit's address received from the Network side. | Request forwarding of the message from the Customer side network layer | +| Message Forwarding Requested from Customer side | Send requested message toward Network if EOC not offline | + +#### **EOC online state** + +| Event | Action | +|-------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Network LOSW = 1 | Network EOC Address = 0
Network EOC State = Offline | +| Discovery message received from the Network side | Increment Hop Count
Set Network EOC address to Hop Count +2
Compose and present Discovery message to Customer side application layer
Send Discovery Response to STU-C | +| Message with broadcast destination address received from the Network side | Process the message
Request the Customer side EOC network layer to forward the message | +| Message with unit's destination address or address 0 received from the Network side | Process the message | +| Message with address not equal to unit's address received from the Network side | Request forwarding of message from the Customer side network layer | +| Message forwarding requested from Customer side network layer | Send requested message toward Network if EOC not offline | + +### 9.5.4 Remote management access + +The STU-C shall maintain the master management database for the entire SHDSL span. (An optional second database is maintained at the STU-R.) Other units are only required to store enough information to accurately send information via the EOC. The information contained in the master database shall be accessible from any SHDSL unit that has a craft port and from network management if it is available. The craft access is in the form of a virtual-terminal interface (or virtual-craft-port interface). This interface is defined so that it can be used by any attached unit to access the terminal screen of another unit on the same SHDSL span. Support for this feature is optional, with the exception of the STU-C, which shall support the "host" side of at least one remote terminal connection. (Whether this interface can be active simultaneously with local craft access to the STU-C is a vendor decision and beyond the scope of this Recommendation.) The virtual-terminal interface consists of connect, disconnect, keyboard, and screen messages. After a connection has been established, input characters from the craft port are sent in Keyboard data messages to the "host" unit. The host unit, in turn, shall send information in the form of ASCII text, ASCII control codes, and screen control functions in Screen messages, whose contents are transmitted back to the craft port. The host unit shall echo characters. + +The method for determining that remote access through the local craft port is desired or should be terminated is vendor specific, and beyond the scope of this Recommendation. Whatever method is used, capability for transmitting all valid key sequences (ASCII characters and control codes) shall be provided. + +### 9.5.5 EOC transport + +The EOC shall be transported in the SHDSL frame in bits *eoc1* through *eoc20*. Five octets are contained in each two SHDSL frames, with specified alignment. The least significant bit (LSB) of the octets are located in bits 1, 9, and 17 of the EOC bits in the first frame and bits 5 and 13 of the second frame; each octet is transmitted LSB first. Octet alignment across frames is achieved through detection of the alignment of the HDLC Sync pattern ( $7E_{16}$ ). + +For optional M-pair operation, each EOC message shall be sent in parallel such that redundant and identical messages are sent over all M loops. + +#### 9.5.5.1 EOC data format + +Numerical data and strings are placed in the EOC with octet alignment. Data items that are not an integral number of octets have been packed together to minimize message sizes. + +Numerical Fields shall be transmitted most significant octet first, least significant bit first within an octet. (This is consistent with "network octet ordering" as in IETF RFC 1662: PPP in HDLC-like Framing [4].) + +Strings shall be represented in the data stream with their first character (octet) transmitted first. Strings shall be padded with spaces or terminated with a NULL ( $00_{16}$ ) to fill the allocated field size. String fields are fixed length so characters after a NULL in a string data field are "don't care". + +#### 9.5.5.2 EOC frame format + +The EOC channel shall carry messages in an HDLC-like format as defined in 6.3/G.997.1 [3]. The channel shall be treated as a stream of octets; all messages shall be an integral number of octets. + +The frame format uses a compressed form of the HDLC header, as illustrated in Table 9-4. The destination address field shall be the least significant 4 bits of octet 1; the source address field shall occupy the most significant 4 bits of the same octet (the address field). There is no control field. One or more sync octets ( $7E_{16}$ ) shall be present between each frame. Inter-frame fill shall be accomplished by inserting sync octets as needed. Discovery probe messages shall be preceded by at least 5 sync octets to assure proper detection of octet alignment. The Information Field contains exactly one Message as defined below. The maximum length of a frame shall be 75 octets, not including the sync pattern or any octets inserted for data transparency. + +**Table 9-4/G.991.2 – Frame format for SHDSL EOC** + +| Octet # | MSB | LSB | | | +|---------|---------------------------|-------------------------------|----------------------|--| +| | Contents | | | | +| | Sync pattern $7E_{16}$ | | | | +| | Source address bits 7..4 | Destination address bits 3..0 | | | +| 1 | Message ID per Table 9-6. | | Information
field | | +| 2 | Message Content – Octet 2 | | | | +| ... | ... | | | | +| L | Message Content – Octet L | | | | +| | FCS octet 1 | | | | +| | FCS octet 2 | | | | +| | Sync pattern $7E_{16}$ | | | | + +#### 9.5.5.3 Data transparency + +Transparency for the information payload to the sync pattern ( $7E_{16}$ ) and the control escape pattern $7D_{16}$ shall be achieved by octet stuffing. + +Before transmission: + +- octet pattern $7E_{16}$ is encoded as two octets $7D_{16}$ , $5E_{16}$ ; +- octet pattern $7D_{16}$ is encoded as two octets $7D_{16}$ , $5D_{16}$ . + +At reception: + +- octet sequence $7D_{16}$ , $5E_{16}$ is replaced by octet $7E_{16}$ ; +- octet sequence $7D_{16}$ , $5D_{16}$ is replaced by octet $7D_{16}$ ; +- any other two-octet sequence beginning with $7D_{16}$ aborts the frame. + +#### 9.5.5.4 Frame check sequence + +The frame check sequence (FCS) shall be calculated as specified in IETF RFC 1662 [4]. (Note that the FCS is calculated before data transparency.) The FCS shall be transmitted as specified in IETF RFC 1662. + +#### 9.5.5.5 Unit addresses + +Each unit uses one source and destination address when communicating with upstream units and a separate, independent source and destination address when communicating with downstream units. Each address shall have a value between $0_{16}$ and $F_{16}$ . Units shall be addressed in accordance with Table 9-5. Address $F_{16}$ may only be used as a destination address and shall specify that the message is addressed to all units. Address $0_{16}$ is used to address the next attached or adjacent unit. + +**Table 9-5/G.991.2 – Device addresses** + +| Address ( $Base_{16}$ ) | Device | +|-------------------------|------------------------------------| +| 0 | Adjacent device | +| 1 | STU-C | +| 2 | STU-R | +| 3-A | Regenerators 1-8 | +| B-E | Reserved (D and E not allowed) | +| F | Broadcast message, to all stations | + +NOTE – This Recommendation is not intended to indicate how many regenerators can or should be supported by a product; only how to identify them if they exist. + +#### 9.5.5.6 Message IDs + +Table 9-6 summarizes message ID. Message IDs are listed as decimal numbers. Messages 0-64 represent request messages. Messages 128-192 represent messages that are sent in response to request messages. Each request message is acknowledged with the corresponding response. Request/Response Message IDs usually differ by an offset of 128. + +**Table 9-6/G.991.2 – Summary of message IDs** + +| Message ID (decimal) | Message type | Initiating unit | Reference | +|----------------------|--------------------------------------------------|--------------------|------------| +| 0 | Reserved | | | +| 1 | Discovery Probe | STU-C, STU-R*, SRU | 9.5.5.7.1 | +| 2 | Inventory Request | STU-C, STU-R* | 9.5.5.7.3 | +| 3 | Configuration Request – SHDSL | STU-C | 9.5.5.7.5 | +| 4 | Reserved for Application Interface Configuration | | | +| 5 | Configuration Request – Loopback Timeout | STU-C, STU-R* | 9.5.5.7.6 | +| 6 | Virtual Term. Connect Req. | STU-R*, SRU* | 9.5.5.7.16 | +| 7 | Virtual Terminal Disc. Req. | STU-R*, SRU* | 9.5.5.7.16 | +| 8 | Keyboard data message | STU-R*, SRU* | 9.5.5.7.17 | +| 9 | Maintenance request – System Loopback | STU-C, STU-R* | 9.5.5.7.18 | +| 10 | Maintenance request – Element Loopback | STU-C, STU-R* | 9.5.5.7.19 | +| 11 | Status Request | STU-C, STU-R* | 9.5.5.7.11 | +| 12 | Full Status Request | STU-C, STU-R* | 9.5.5.7.12 | + +**Table 9-6/G.991.2 – Summary of message IDs** + +| Message ID (decimal) | Message type | Initiating unit | Reference | +|-----------------------------|--------------------------------------------------------------------|------------------------|--------------------| +| 13-14 | Reserved | | | +| 15 | Soft restart/Power backoff disable Request | STU-C | 9.5.5.7.21 | +| 16 | Reserved (Future) | | | +| 17 | ATM Cell Status Request | STU-C, STU-R* | E.9.4.7 | +| 18 | STU-R Configuration Request – Management | STU-C | 9.5.5.7.9 | +| 19 | Reserved for Voice Transport Request (Future) | Undefined | | +| 20 | ISDN Request | STU-C, STU-R | E.8.7.1,
E.13.3 | +| 21 | LAPV5 POTS and ISDN Setup Request | STU-C | E.13.6 | +| 22 | Deactivation Request | STU-C, STU-R | H.1.3.1 | +| 23 | Mapping Request | STU-C, STU-R* | 9.5.5.7.27 | +| 23-63 | Reserved (Future) | | | +| 64-88 | Reserved for Line management Request | Undefined | 9.5.5.7.22 | +| 89-111 | Reserved | | | +| 112-119 | Proprietary Message | Undefined | 9.5.5.7.23 | +| 120 | External Message | Undefined | 9.5.5.7.24 | +| 121 | G.997.1 Message | STU-C*, STU-R* | 9.5.5.7.25 | +| 122-124 | Reserved | | | +| 125-127 | Excluded (7D 16 , 7E 16 , 7F 16 ) | | | +| 128 | Reserved | | | +| 129 | Discovery Response | All | 9.5.5.7.2 | +| 130 | Inventory Response | All | 9.5.5.7.4 | +| 131 | Configuration Response – SHDSL | STU-R, SRU | 9.5.5.7.7 | +| 132 | Reserved for Application Interface Configuration | | | +| 133 | Configuration Response – Loopback Timeout | All | 9.5.5.7.8 | +| 134 | Virtual Terminal Connect Response | STU-C, SRU*,
STU-R* | 9.5.5.7.16 | +| 135 | Reserved | | | +| 136 | Screen data message | STU-C, SRU*,
STU-R* | 9.5.5.7.17 | +| 137 | Maintenance Status | All | 9.5.5.7.20 | +| 138 | Reserved | | | +| 139 | Status/SNR | All | 9.5.5.7.13 | +| 140 | Performance Status SHDSL Network Side | SRU, STU-R | 9.5.5.7.14 | + +**Table 9-6/G.991.2 – Summary of message IDs** + +| Message ID (decimal) | Message type | Initiating unit | Reference | +|----------------------|--------------------------------------------------------------------|-----------------|--------------------| +| 141 | Performance Status SHDSL Customer Side | STU-C, SRU | 9.5.5.7.15 | +| 142 | Reserved for Application Interface Performance | | | +| 143 | Reserved (Future) | | | +| 144 | Generic Unable to Comply (UTC) | | 9.5.5.7.26 | +| 145 | ATM Cell Status Information | All | E.9.4.8 | +| 146 | Configuration Response – Management | STU-R, SRU | 9.5.5.7.10 | +| 147 | Reserved for Voice Transport Response (Future) | Undefined | | +| 148 | ISDN Response | STU-C, STU-R | E.8.7.1,
E.13.3 | +| 149 | LAPV5 POTS and ISDN Set-up | STU-R | E.13.6 | +| 150 | Deactivation Response | STU-C, STU-R | H.1.3.2 | +| 151 | Mapping Response | All | 9.5.5.7.28 | +| 152-191 | Reserved (Future) | | | +| 192-216 | Segment Management Response (reserved) | Undefined | 9.5.5.7.22 | +| 217-239 | Reserved (Future) | | | +| 240-247 | Proprietary message Response | Undefined | 9.5.5.7.23 | +| 248-252 | Reserved | | | +| 253-255 | Excluded (FD 16 , FE 16 , FF 16 ) | | | + +\* Denotes optional support. A unit may initiate this message. + +#### 9.5.5.7 Message contents + +Each message shall have the contents in the format specified in Tables 9-7 through 9-31. If any message has a message length longer than expected and is received in a frame with a valid FCS, then the known portion of the message shall be used and the extra octets discarded. This will permit addition of new fields to existing messages and maintain backward compatibility. New data fields shall only be placed in reserved bits after the last previously defined data octet. Reserved bits and octets shall be filled with the value 0016 for forward compatibility. + +Response messages may indicate UTC (Unable to Comply). Note that this is not an indication of non-compliance. UTC indicates that the responding unit was unable to implement the request. + +##### 9.5.5.7.1 Discovery probe – Message ID 1 + +The discovery probe message shall be assigned Message ID 1, and is used to allow an STU to determine how many devices are present and assign addresses to those units. + +**Table 9-7/G.991.2 – Discovery probe information field** + +| Octet # | Contents | Data type | Reference | +|---------|-----------|---------------|-----------| +| 1 | 1 | Message ID | | +| 2 | Hop Count | Unsigned char | 9.5.3 | + +##### **9.5.5.7.2 Discovery response – Message ID 129** + +The discovery response message shall be assigned Message ID 129. This message shall be sent in response to a discovery probe message. The hop count field shall be set to 1 larger than the value received in the discovery probe message causing the response. (The full receive state machine is described in Table 9-3.) Forward LOSW indication means that the segment is down in the forward direction from the SRU. In the case of optional *M*-pair operation, Forward LOSW indication means that all *M* loops are down in the forward direction from the SRU. In either case, the SRU is unable to forward the Discovery Probe message to the adjacent unit and it reports this fact to the initiating STU. The Forward LOSW octet field shall be set to 0016 for responses from an STU. + +The Vendor ID field is used to identify the system integrator, as specified in 9.5.5.7.4. + +The SHDSL version number indicates the SHDSL standard to which the system was built. For the present version of this Recommendation (12/2003), these bits shall be set to 00001000. + +The vendor EOC software version number shall be assigned by the system vendor as identified by the vendor ID. Software version numbers are to be incremented for each new SHDSL standard. + +**Table 9-8/G.991.2 – Discovery response information field** + +| Octet # | Contents | Data type | Reference | +|--------------|--------------------------------------------------------------|---------------|----------------------------------| +| 1 | 129 | Message ID | | +| 2 | Hop Count | Unsigned char | 9.5.3 | +| 3 | Reserved | | | +| 4-11 | Vendor ID (ordered identically to bits in G.994.1 Vendor ID) | | | +| 12 | Vendor EOC Software Version | Unsigned char | | +| 13 | SHDSL Version # | Unsigned char | | +| 14 bits 7..1 | Reserved | | | +| 14 bit 0 | Forward LOSW indication, EOC unavailable | Bit | 1 = Unavailable
0 = Available | + +##### **9.5.5.7.3 Inventory request – Message ID 2** + +The inventory request message shall be assigned Message ID 2. This message is used to request an inventory response from a particular unit. It shall only be transmitted by STU devices. There shall be no octets of content for this message. + +**Table 9-9/G.991.2 – Inventory request information field** + +| Octet # | Contents | Data type | Reference | +|---------|----------|------------|-----------| +| 1 | 2 | Message ID | | + +##### **9.5.5.7.4 Inventory response – Message ID 130** + +The inventory response message shall be assigned Message ID 130. This message shall be sent in response to an inventory request message. + +The SHDSL version number indicates the SHDSL standard to which the system was built. For G.shdsl.bis (draft), these bits shall be set to 00001000. + +The Vendor ID field is used to specify the system integrator. In this context, the system integrator usually refers vendor of the smallest field-replaceable unit. This typically is also the entity pointed to by the Unit Identification Code (CLEI™) Field. As such, the Vendor ID field contents may not be the same as the Vendor ID indicated within ITU-T Rec. G.994.1, which relates to the manufacturer of the physical layer interface. The serial number, model number, issue number, list number, and software revision number shall all be assigned with respect to the system integrator. + +Special unit identification codes are used in North America. These CLEI (Common Language Equipment Identifier) codes are used by network service providers for inventory, spare-part ordering, provisioning and maintenance operations. In North America, CLEI codes are used as a vendor's product ID. CLEI codes conform to ANSI T1.213, Coded Identification of Equipment Entities of the North American Telecommunications System for Information Exchange. In regions outside North America, these fields may be set to zero. + +Information on the modem software version, the vendor list (modem hardware version), the modem issue, the model number, and the modem serial number are specific to the system. Therefore, this information shall be assigned by the system vendor as identified by the vendor ID. + +The vendor software version indicates the version of the software of the SHDSL system. The vendor software version is not necessarily identical to the EOC software version in 9.5.5.7.2. The vendor list number indicates the version number of the system hardware. The vendor issue field indicates the particular usage of the unit. The vendor model number is a unique number for the particular type of unit. The vendor serial number is a number that identifies every unit individually. + +**Table 9-10/G.991.2 – Inventory response information field** + +| Octet # | Contents | Data type | Reference | +|---------|--------------------------------------------------------------|-----------------|-----------| +| 1 | 130 | Message ID | | +| 2 | SHDSL Version # | Unsigned char | | +| 3-5 | Vendor List # | 3-octet string | | +| 6-7 | Vendor Issue # | 2-octet string | | +| 8-13 | Vendor Software Version | 6-octet string | | +| 14-23 | Unit Identification Code (CLEI™) | 10-octet string | | +| 24 | Reserved | | | +| 25-32 | Vendor ID (ordered identically to bits in G.994.1 Vendor ID) | | | +| 33-44 | Vendor model # | 12-octet string | | +| 45-56 | Vendor serial # | 12-octet string | | +| 57-68 | Other vendor information | 12-octet string | | + +##### 9.5.5.7.5 Configuration request – SHDSL: Message ID 3 + +The configuration request – SHDSL message is transmitted by the STU-C to configure the SHDSL interface(s) of attached units. This message may be broadcast or addressed to specific units. It is acknowledged with a configuration response – SHDSL message. For SHDSL, SNR is measured internal to the transceiver decision device as opposed to the external segment termination. The "Off" setting indicates that threshold crossings are not reported. Loop attenuation and SNR margin are local alarms that are reported in Messages 140 and 141. In addition, these alarms may be physically indicated on the equipment. SHDSL loop attenuation shall be defined as follows: + +$$LoopAtten_{SHDSL}(H) = \frac{2}{f_{sym}} \left( \int_0^{\frac{f_{sym}}{2}} 10 \times \log_{10} \left[ \sum_{n=0}^1 S(f - n f_{sym}) \right] df - \int_0^{\frac{f_{sym}}{2}} 10 \times \log_{10} \left[ \sum_{n=0}^1 S(f - n f_{sym}) H(f - n f_{sym})^2 \right] df \right)$$ + +where $f_{sym}$ is the symbol rate, $\frac{1}{H(f)}$ is the insertion loss of the loop, and $S(f)$ is the nominal transmit PSD. + +**Table 9-11/G.991.2 – Configuration request – SHDSL information field** + +| Octet # | Contents | Data type | Reference | +|-------------|---------------------------------------|------------|--------------------------| +| 1 | 3 | Message ID | | +| 2 bit 7 | Config Type | Bit | 0-normal,
1-Read only | +| 2 bits 6..0 | SHDSL Loop Attenuation threshold (dB) | Enumerated | 0 = off, 1 to 127 | +| 3 bits 7..4 | SHDSL SNR Margin threshold (dB) | Enumerated | 0 = off, 1 to 15 | +| 3 bits 3..0 | Reserved | | Set to 0 | + +##### 9.5.5.7.6 Configuration request – loopback timeout: Message ID 5 + +The configuration request – loopback timeout message is transmitted by the STU-C (and optionally the STU-R) to set loopback timeouts for individual elements. If a loopback is not cleared before the expiration of the timeout, then the element shall revert to normal operation. This message may be broadcast or addressed to specific units. It is acknowledged with a configure response – loopback timeout message. If date and time information is sent in octets 4-21, then these strings shall conform to ISO 8601 [5]. If date and time information is not sent, then these fields shall be filled with zeros. + +**Table 9-12/G.991.2 – Configuration request – loopback timeout information field** + +| Octet # | Contents | Data type | Reference | +|---------------|------------------|-------------------------|-------------------------------| +| 1 | 5 | Message ID | | +| 2 bit 7 | Config Type | Bit | 0 = normal,
1 = Read-only. | +| 2 bits 6..4 | Reserved | | | +| 2 bits 3..0-3 | Loopback timeout | 12-bit unsigned integer | In minutes, 0 = no timeout | +| 4-13 | YYYY-MM-DD | 10-octet date string | ISO 8601 | +| 14-21 | HH:MM:SS | 8-octet time string | ISO 8601 | + +##### 9.5.5.7.7 Configuration response – SHDSL: Message ID 131 + +The configuration response – SHDSL message is transmitted to the STU-C in response to a configuration request – SHDSL message. This response is sent after the applicable configuration changes have been made. The values of the response shall be set to the new values, after they have been applied. If a transceiver unit is unable to comply with the request, the bit in the compliance octet is set and the current settings are reported. If the config request message was received with a config type of "Read-Only," then no changes are made to the current configuration and the current values are reported. + +**Table 9-13/G.991.2 – Configuration response – SHDSL information field** + +| Octet # | Contents | Data type | Reference | +|-------------|---------------------------------------|------------|-------------------| +| 1 | 131 | Message ID | | +| 2 bits 7..1 | Reserved | | | +| 2 bit 0 | UTC (Unable to Comply) | Bit | 0 = OK, 1 = UTC | +| 3 | SHDSL Loop Attenuation threshold (dB) | Char | 0 = off, 1 to 127 | +| 4 bits 7..4 | SHDSL SNR Margin threshold (dB) | Enumerated | 0 = off, 1 to 15 | +| 4 bits 3..0 | Reserved | | Set to 0 | + +##### 9.5.5.7.8 Configuration response – loopback timeout: Message ID 133 + +The configuration response – loopback timeout message is transmitted to acknowledge the configuration request – loopback timeout message. This response is sent after the applicable configuration changes have been made. The values of the response shall be set to the new values, after they have been applied. If a transceiver unit is unable to comply with the request, the bit in the compliance octet is set and the current settings are reported. If the config request message was received with a config type of "Read-Only," then no changes are made to the current configuration and the current values are reported. + +**Table 9-14/G.991.2 – System Loopback Timeout Response information field** + +| Octet # | Information Field | Data type | Reference | +|---------------|------------------------|-------------------------|-------------------------------| +| 1 | 133 | Message ID | | +| 2 bits 7..1 | Reserved | | | +| 2 bit 0 | UTC (Unable to Comply) | Bit | 0 = OK, 1 = UTC | +| 3 bits 7..4 | Reserved | | | +| 3 bits 3..0-4 | Loopback timeout | 12-bit unsigned integer | In minutes,
0 = no timeout | +| 5-14 | YYYY-MM-DD | 10-octet date string | ISO 8601 [5] | +| 15-22 | HH:MM:SS | 8-octet time string | ISO 8601 | + +##### 9.5.5.7.9 STU-R config – management: Message ID 18 + +The config request – management message is transmitted by the STU-C to enable or disable STU-R initiated management flow. The destination address shall be F16 to indicate this is a broadcast message. STU-R initiated management flow is enabled by default. When disabled, an SRU shall not respond to any STU-R-initiated request messages, and the STU-R shall not issue any such messages (messages 2-12). Config type of Read-Only indicates that the addressed unit ignore the subsequent values in the message and report back its current configuration. + +**Table 9-14a/G.991.2 – Configuration request – management information field** + +| Octet # | Contents | Data type | Reference | +|-------------|---------------------------------|------------|-----------------------| +| 1 | Message ID 18 | Message ID | | +| 2 bit 7 | ConfigType | Bit | 0-normal, 1-Read-Only | +| 2 bits 6..1 | Reserved | | | +| 2 bit 0 | STU-R Initiated Management Flow | Bit | 0-Enable, 1-Disabled | + +##### **9.5.5.7.10 Config response – management message: Message ID 146** + +Config response – management message is sent by all units to acknowledge to the config request – management message. + +**Table 9-14b/G.991.2 – Configuration response – management information field** + +| Octet # | Contents | Data type | Reference | +|-------------|----------------------------------------|------------|-----------------------| +| 1 | Message ID 146 | Message ID | | +| 2 bits 7..1 | Reserved | | | +| 2 bit 0 | UTC (Unable to Comply) | Bit | 0-OK, 1-UTC | +| 3 bits 7..1 | Reserved | | | +| 3 bit 0 | STU-R Initiated Management Flow Status | Bit | 0-Enabled, 1-Disabled | + +##### **9.5.5.7.11 Status request – Message ID 11** + +The status request message is used to poll an element for alarm and general performance status. + +The polled unit will respond with one or more of the following status response messages: + +- Status/SNR response – 139 (9.5.5.7.13). +- SHDSL network side performance status – 140 (9.5.5.7.14). +- SHDSL customer side performance status – 141 (9.5.5.7.15). +- Maintenance status – 137 (9.5.5.7.20). + +In the optional *M*-pair mode, messages 139, 140, and 141 contain status information that is specific to a particular pair. In this case, *M* messages each (one corresponding to each pair) of types 139, 140, and 141 may be sent by the polled unit in response to a status request message. The responding element shall provide the loop ID information in EOC messages 139, 140, and 141. The responding element shall first provide the information relating to loop 1, followed shortly thereafter with the requested information for loop 2 (if $M \geq 2$ ), then loop 3 (if $M \geq 3$ ), then loop 4 (if $M = 4$ ). + +If active alarm, fault or maintenance conditions exist then the polled unit shall respond with the messages that correspond to the active conditions. + +If there has been any change in performance status other than SNR margin since the last time a unit was polled, then the unit shall respond with the messages which contain the change in performance status. + +Otherwise, the polled unit shall respond with the status/SNR response – 139 (9.5.5.7.13). + +**Table 9-15/G.991.2 – Status request information field** + +| Octet # | Information field | Data type | +|---------|-------------------|------------| +| 1 | Message ID 11 | Message ID | + +##### 9.5.5.7.12 Full status request – Message ID 12 + +The full status request message is used to poll an element for its complete current status. The following messages shall be sent in response to the full status request: + +- SHDSL network side performance status (9.5.5.7.14). +- SHDSL customer side performance status (9.5.5.7.15). +- Maintenance status (9.5.5.7.20). + +In the optional *M*-pair mode, the following messages shall be sent in response to the full status request: + +- SHDSL network side performance status (9.5.5.7.14) – related to Loop 1. +- SHDSL network side performance status – for Loop 2 to Loop *M* (one message per loop). +- SHDSL customer side performance status (9.5.5.7.15) – related to Loop 1. +- SHDSL customer side performance status – for Loop 2 to Loop *M* (one message per loop). +- Maintenance status (9.5.5.7.20). + +**Table 9-16/G.991.2 – Full Status Request information field** + +| Octet # | Information field | Data type | +|---------|-------------------|------------| +| 1 | Message ID 12 | Message ID | + +##### 9.5.5.7.13 Status response/SNR – Message ID 139 + +The performance status/SNR message shall be sent in response to the status request message under the conditions specified in 9.5.5.7.9. The reported integer represents dB SNR noise margin values rounded up. Because each STU only connects to one SHDSL segment, the application interface side SNR margin data shall be 0 (i.e., the network side SNR margin shall be 0 at the STU-C and the customer side SNR shall be 0 at the STU-R). + +**Table 9-17/G.991.2 – Status response OK/SNR information field** + +| Octet # | Information field | Data type | +|---------|-------------------------------|----------------------------------------------------------------| +| 1 | Message ID 139 | Message ID | +| 2 | Network Side SNR Margin (dB) | Signed char (127 = Not Available) | +| 3 | Customer Side SNR Margin (dB) | Signed char (127 = Not Available) | +| 4 | Loop ID | Unsigned char (1 = Loop 1, 2 = Loop 2, 3 = Loop 3, 4 = Loop 4) | + +##### 9.5.5.7.14 SHDSL network side performance status – Message ID 140 + +This message provides the SHDSL network side performance status. Device fault shall be used to indicate hardware or software problems on the addressed unit. The definition of device fault is vendor dependent but is intended to indicate diagnostic or self-test results. DC continuity fault shall be used to indicate conditions that interfere with span powering such as short and open circuits. The definition of DC continuity fault is vendor dependent. + +In octet 11, bits 7..4 are used to indicate that an overflow or reset has occurred in one or more of the modulo counters. Bits 7 and 5 shall indicate that an overflow has occurred since the last SHDSL network side status response. For example, if more than 256 errored seconds occur between SHDSL network side status responses, then the ES modulo counter will overflow. Bits 6 and 4 shall be used to indicate that one or more of the modulo counters have been reset for any reason (e.g., system powerup or a non service-affecting reset.) Bits 7 and 6 shall be cleared to 0 after a SHDSL network + +side status response is sent to the STU-C. Bits 5 and 4 shall be cleared to 0 after a SHDSL network side status response is sent to the STU-R. + +**Table 9-18/G.991.2 – SHDSL-network side performance status information field** + +| Octet # | Contents | Data type | Reference | +|--------------|-----------------------------------------------|-------------------------|---------------------------------------------------------| +| 1 | Message ID 140 | Message ID | | +| 2 bit 7 | Reserved | | | +| Bit 6 | N – Power Backoff Status | Bit | 0 = default
1 = selected | +| Bit 5 | Device Fault | Bit | 0 = OK, 1 = Fault | +| Bit 4 | N – DC Continuity Fault | Bit | 0 = OK, 1 = Fault | +| Bit 3 | N – SNR Margin alarm | Bit | 0 = OK, 1 = alarm | +| Bit 2 | N – Loop Attenuation Alarm | Bit | 0 = OK, 1 = alarm | +| Bit 1 | N – SHDSL LOSW Failure Alarm | Bit | 0 = OK, 1 = alarm | +| Bit 0 | Reserved | | Set to 0 | +| 3 | N – SHDSL SNR Margin (dB) | Signed char (127 = NA) | | +| 4 | N – SHDSL Loop Attenuation (dB) | Signed char (–128 = NA) | | +| 5 | N – SHDSL ES Count modulo 256 | Unsigned char | | +| 6 | N – SHDSL SES Count modulo 256 | Unsigned char | | +| 7-8 | N – SHDSL CRC Anomaly Count modulo 65536 | Unsigned int | | +| 9 | N – SHDSL LOSW Defect Second Count modulo 256 | Unsigned char | | +| 10 | N – SHDSL UAS Count modulo 256 | Unsigned char | | +| 11 bit 7 | N – Counter Overflow Indication to STU-C | | 0 = OK
1 = Overflow | +| 11 bit 6 | N – Counter Reset Indication to STU-C | | 0 = OK
1 = Reset | +| 11 bit 5 | N – Counter Overflow Indication to STU-R | | 0 = OK
1 = Overflow | +| 11 bit 4 | N – Counter Reset Indication to STU-R | | 0 = OK
1 = Reset | +| 11 bits 3..0 | N-Power Back-Off Base Value (dB) | Unsigned char | 0 .. 15 | +| 12 bit 7 | N-Power Back-Off Extension (dB) | Bit | 0→ PBO = Base Value +0 dB
1→ PBO = Base Value +16 dB | +| 12 bits 6..3 | Reserved | | | +| 12 bits 2..0 | Loop ID | Unsigned char | 1 = Loop 1
2 = Loop 2
3 = Loop 3
4 = Loop 4 | + +##### 9.5.5.7.15 SHDSL customer side performance status – Message ID 141 + +This message provides the SHDSL Customer Side Performance Status. Device Fault shall be used to indicate hardware or software problems on the addressed unit. The definition of Device Fault is vendor dependent but is intended to indicate diagnostic or self-test results. DC Continuity Fault shall be used to indicate conditions that interfere with span powering such as short and open circuits. The definition of DC Continuity Fault is vendor dependent. + +In octet 11, bits 7..4 are used to indicate that an overflow or reset has occurred in one or more of the modulo counters. Bits 7 and 5 shall indicate that an overflow has occurred since the last SHDSL Customer Side status response. For example, if more than 256 Errored Seconds occur between SHDSL Customer Side status responses, then the ES modulo counter will overflow. Bits 6 and 4 shall be used to indicate that one or more of the modulo counters have been reset for any reason (e.g., system powerup or a non-service-affecting reset). Bits 7 and 6 shall be cleared to 0 after a SHDSL Customer Side status response is sent to the STU-C. Bits 5 and 4 shall be cleared to 0 after a SHDSL Customer Side status response is sent to the STU-R. + +**Table 9-19/G.991.2 – SHDSL-customer side performance status information field** + +| Octet # | Contents | Data type | Reference | +|----------|-----------------------------------------------|------------------------|-----------------------------| +| 1 | Message ID 141 | Message ID | | +| 2 bit 7 | Reserved | | | +| Bit 6 | C – Power Backoff Status | Bit | 0 = default
1 = selected | +| Bit 5 | Device Fault | Bit | 0 = OK, 1 = Fault | +| Bit 4 | C – DC Continuity Fault | Bit | 0 = OK, 1 = Fault | +| Bit 3 | C – SNR Margin alarm | Bit | 0 = OK, 1 = alarm | +| Bit 2 | C – Loop Attenuation Alarm | Bit | 0 = OK, 1 = alarm | +| Bit 1 | C – SHDSL LOSW Failure Alarm | Bit | 0 = OK, 1 = alarm | +| Bit 0 | Reserved | | Set to 0 | +| 3 | C – SHDSL SNR Margin (dB) | Signed char (127 = NA) | | +| 4 | C – SHDSL Loop Attenuation (dB) | Signed char (128 = NA) | | +| 5 | C – SHDSL ES Count modulo 256 | Unsigned char | | +| 6 | C – SHDSL SES Count modulo 256 | Unsigned char | | +| 7-8 | C – SHDSL CRC Anomaly Count modulo 65536 | Unsigned int | | +| 9 | C – SHDSL LOSW Defect Second Count modulo 256 | Unsigned char | | +| 10 | C – SHDSL UAS Count modulo 256 | Unsigned char | | +| 11 bit 7 | C – Counter Overflow Indication to STU-C | | 0 = OK
1 = Overflow | +| 11 bit 6 | C – Counter Reset Indication to STU-C | | 0 = OK
1 = Reset | +| 11 bit 5 | C – Counter Overflow Indication to STU-R | | 0 = OK
1 = Overflow | +| 11 bit 4 | C – Counter Reset Indication to STU-R | | 0 = OK
1 = Reset | + +**Table 9-19/G.991.2 – SHDSL-customer side performance status information field** + +| Octet # | Contents | Data type | Reference | +|-----------------|----------------------------------|---------------|-----------------------------------------------------------| +| 11
bits 3..0 | C-Power Back-Off Base Value (dB) | Unsigned char | 0 .. 15 | +| 12 bit 7 | C-Power Back-Off Extension (dB) | Bit | 0→ PBO = Base Value + 0 dB
1→ PBO = Base Value + 16 dB | +| 12
bits 6..3 | Reserved | | | +| 12
bits 2..0 | Loop ID | Unsigned char | 1 = Loop 1
2 = Loop 2
3 = Loop 3
4 = Loop 4 | + +##### 9.5.5.7.16 Virtual terminal connect/disconnect request/response (Msg. IDs 6, 7, 134) + +Three messages are used to maintain (establish, tear down) virtual terminal sessions between units. A unit may request a connection but must wait for "connect" status response before using the connection. The connection shall remain until a disconnect request is processed or, if implemented, a timeout occurs. At least one session shall be supported by the STU-C. STU-R and SRU may silently ignore the connect request or may respond with a "no connect" status if terminal screens are not supported. + +The connect/disconnect process is necessary for handling the case where keyboard messages are received from more than one device. If a unit cannot accommodate another connect request, it shall send the "no connect" response. + +The connect request message can be sent to cause a refresh of the current screen. When a connect request is accepted the "connect" response shall be transmitted, followed by screen messages with the current screen. If this is a new connection then the first screen shall be sent. The end unit that issues the connect request (Message 6) shall issue the corresponding request (Message 7) to terminate the virtual terminal session. A far-end unit shall respond with Virtual Terminal "no connect" status (Message 134) when it receives a keyboard message from the near-end unit that terminates a virtual terminal session. (This lets the near-end know that the far-end has terminated the connection.) If the far-end unit has dropped the terminal session and a keyboard message is received, the far-end unit shall respond with Message 134 – "no connect". + +For any keyboard character that has special meaning at the near-end (e.g., and escape command), means shall be provided to send that keyboard character to the far end. (This is analogous to the CTRL-] escape command used in TELNET sessions. When one has escaped in a TELNET session to the local terminal, one can typically issue a "send escape" command or similar to send the CTRL-] character to the far end.) + +**Table 9-20/G.991.2 – Virtual terminal connect** + +| Octet # | Contents | Data type | Reference | +|---------|-----------------------------------------|------------|-----------| +| 1 | Message ID 6 – Virtual Terminal Connect | Message ID | | + +**Table 9-21/G.991.2 – Virtual terminal disconnect** + +| Octet # | Contents | Data type | Reference | +|---------|--------------------------------------------|------------|-----------| +| 1 | Message ID 7 – Virtual Terminal Disconnect | Message ID | | + +**Table 9-22/G.991.2 – Virtual terminal connect response** + +| Octet # | Contents | Data type | Reference | +|---------|----------------------------------------------------|------------|---------------------------------| +| 1 | Message ID 134 – Virtual Terminal Connect Response | Message ID | | +| 2 | Connection status | | 1 = connected
0 = no connect | + +##### **9.5.5.7.17 Screen message/keyboard message (Msg. IDs 8, 136)** + +Keyboard and screen messages are only sent over an active connection between units. Keyboard messages shall be 1 to 8 data octets per message. Queuing of keystrokes from the customer may affect user response times and should be done with care. Screen messages shall be 1 to 24 data octets per message, and their contents are vendor defined. See 9.5.6 for more information on Screen/Keyboard messages. + +**Table 9-23/G.991.2 – Keyboard information field** + +| Octet # | Contents | Data type | Reference | +|-------------|-----------------------------------------|------------|-----------| +| 1 | Message ID 8 – Keyboard | Message ID | | +| 2.. (L + 1) | ASCII character(s) and escape sequences | char array | | + +**Table 9-24/G.991.2 – Screen information field** + +| Octet # | Contents | Data type | Reference | +|-------------|---------------------------------------|------------|-----------| +| 1 | Message ID 136 – Screen | Message ID | | +| 2.. (L + 1) | ASCII characters and escape sequences | char array | | + +##### **9.5.5.7.18 Maintenance Request – System Loopback Messages (9)** + +The Maintenance Request – System Loopback Message contains loopback commands for all of the elements on the span. The contents of the Maintenance Request – System Loopback message are shown in Table 9-25. The System Loopback message shall have a broadcast destination address when sent from the STU-C. When optionally sent from the STU-R, the System Loopback message shall have the STU-C as its destination address. Upon reception of this message, each SRU and STU shall comply with its corresponding command field and respond to the sender with the Maintenance Status message. Note that the SRUs are numbered consecutively beginning with closest SRU to the STU-C. Each SRU shall determine its number by subtracting 2 from its network side EOC address. Since the network side EOC addresses must be known, the STU-R shall not use the System Loopback Message if the STU-C is offline. To invoke SRU loopbacks while the STU-C is offline, the STU-R shall use the Maintenance Request-Element Loopback message. (Maintenance request messages may also be used by the STU devices to poll for current loopback status, using the unchanged bit flags.) + +**Table 9-25/G.991.2 – Maintenance Request – System Loopback information field** + +| Octet # | Contents | Data type | Reference | +|---------|----------------------------------------------------|-----------|------------| +| 1 | Message ID 9 – Maintenance Request-System Loopback | | | +| 2 | STU-C Loopback Commands | Bit flags | Table 9-26 | +| 3 | STU-R Loopback Commands | Bit flags | Table 9-26 | +| 4 | SRU #1 Loopback Commands | Bit flags | Table 9-26 | +| 5 | SRU #2 Loopback Commands | Bit flags | Table 9-26 | +| 6 | SRU #3 Loopback Commands | Bit flags | Table 9-26 | +| 7 | SRU #4 Loopback Commands | Bit flags | Table 9-26 | +| 8 | SRU #5 Loopback Commands | Bit flags | Table 9-26 | +| 9 | SRU #6 Loopback Commands | Bit flags | Table 9-26 | +| 10 | SRU #7 Loopback Commands | Bit flags | Table 9-26 | +| 11 | SRU #8 Loopback Commands | Bit flags | Table 9-26 | + +**Table 9-26/G.991.2 – Loopback command bit flag definitions** + +| Bit positions | Definition | +|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| 7 | Reserved | +| 6 | Clear All Maintenance States (including any proprietary states) | +| 5 | Initiate Special Loopback | +| 4 | Terminate Special Loopback | +| 3 | Initiate Loopback toward the Network | +| 2 | Initiate Loopback toward the Customer | +| 1 | Terminate Loopback toward the Network | +| 0 | Terminate Loopback toward the Customer | +| NOTE – Bit set to 1 – perform action, Bit Set to 0 – no action taken, report current status. | | + +##### **9.5.5.7.19 Maintenance Request – Element Loopback Message ID 10** + +The Maintenance Request – Element Loopback Message contains loopback commands for an individual element. The contents of the Maintenance Request – Element Loopback message are shown in Table 9-27. The Element Loopback message shall have an individual unit's destination address according to the data flow addresses described in 9.5.2. Upon reception of the Element Loopback message, the addressed unit shall comply with the loopback commands and reply with the Maintenance Status Response message. + +**Table 9-27/G.991.2 – Maintenance Request – Element Loopback information field** + +| Octet # | Contents | Data type | Reference | +|---------|-------------------------------------|------------|------------| +| 1 | Message ID 10 – Maintenance Request | Message ID | | +| 2 | Loopback Commands | Bit flags | Table 9-26 | + +##### 9.5.5.7.20 Maintenance Status Response Message ID 137 + +Maintenance status is sent in response to the Maintenance Request – System Loopback, Maintenance Request – Element Loopback, Status Request, and Full Status Request query messages. The "Special loopback" is defined for the STU-R as a Maintenance Termination Unit (MTU) loopback; it is not defined at other units. + +**Table 9-28/G.991.2 – Maintenance Status information field** + +| Octet # | Contents | Data type | Reference | +|---------|----------------------------------------------|------------|---------------------------------------| +| 1 | Message ID 137 – Maintenance Status-Loopback | Message ID | | +| 2 bit 7 | Loopback Timeout Status | Bit | 0 = unchanged,
1 = changed | +| 2 bit 6 | Proprietary Maintenance State active | Bit | 0 = off, 1 = on | +| 2 bit 5 | Special loopback active | Bit | 0 = off, 1 = on | +| 2 bit 4 | Loopback active toward STU-R | Bit | 0 = off, 1 = on | +| 2 bit 3 | Loopback active toward STU-C | Bit | 0 = off, 1 = on | +| 2 bit 2 | Local or span-powered unit | Bit | 0 = span powered
1 = local powered | +| 2 bit 1 | Customer Tip/Ring Reversal | Bit | 0 = normal
1 = reversed | +| 2 bit 0 | Network Tip/Ring Reversal | Bit | 0 = normal
1 = reversed | + +##### 9.5.5.7.21 Soft restart/power backoff disable Message ID 15 + +The purpose of this message is to switch a receiver between the default and selected modes of power backoff. If default mode is set, PBO shall be set to the default value. Otherwise, in selected mode, PBO may be negotiated through G.994.1 to another value. In order for a change in power backoff mode to take effect, the receiver must reactivate. The Soft Restart request shall cause the receiving unit to terminate the corresponding SHDSL connection and enter the Exception State (Figure 6-7). The connection shall not be terminated unless the corresponding Soft Restart bit is set in this message. The receiving unit shall wait $5 \pm 1$ s before terminating the SHDSL connection. + +This message carries the command to set the power backoff mode. The power backoff mode received in this message shall be maintained as long as power is applied to the unit. Maintaining the power backoff mode in non-volatile storage is optional. Note that the configuration of power backoff mode applies to the receiver; i.e., the receiver requests a PSD mask based on both the received power and the configuration of its power backoff mode. + +**Table 9-29/G.991.2 – Soft restart information field** + +| Octet # | Contents | Data type | Reference | +|-------------|----------------------------------------|------------|-------------------------------| +| 1 | Message ID 15 – Soft Restart/Backoff | Message ID | | +| 2 bits 7..2 | Reserved | | | +| 2 bit 1 | Network Side Power Backoff Setting | Bit | 0 = default
1 = selected | +| 2 bit 0 | Network Side Soft Restart (after 5 s) | Bit | 0 = no Restart
1 = Restart | +| 3 bits 7..2 | Reserved | | | +| 3 bit 1 | Customer Side Power Backoff Setting | Bit | 0 = default
1 = selected | +| 3 bit 0 | Customer Side Soft Restart (after 5 s) | Bit | 0 = no Restart
1 = Restart | + +##### **9.5.5.7.22 Segment management message – (IDs 64-88, 192-216)** + +A range of Message IDs is reserved for segment management (e.g., continuous precoder update). + +##### **9.5.5.7.23 Proprietary messages (IDs 112-119, 240-247)** + +A range of Message IDs is reserved for proprietary messages. It is the responsibility of the STU to address Proprietary Messages to the appropriate destination. An SRU shall either process or forward a proprietary message. A proprietary message shall not be broadcast. + +##### **9.5.5.7.24 Proprietary external message (ID 120)** + +Support for external data ports is optional. No interface for an external data port is specified in this Recommendation. If an STU does not have an external data port, then it shall ignore any received Proprietary External Messages. + +**Table 9-30/G.991.2 – External information field** + +| Octet # | Contents | Data type | Reference | +|-------------|----------------------------------|---------------|-----------| +| 1 | Message ID 120 – External | Message ID | | +| 2 | Logical Port Number | Unsigned char | | +| 3.. (N + 2) | External message data (N octets) | | | + +##### **9.5.5.7.25 G.997.1 external message (ID 121)** + +Support for G.997.1 [3] external messaging is optional. The interface for G.997.1 messages is beyond the scope of this Recommendation. If an STU does not have an interface for G.997.1 messaging, it shall ignore any received G.997.1 External Messages. + +Logical port number FF16 is reserved for indicating the transport of SNMP packets, as described in 6.4/G.997.1. SNMP packets may be transmitted using one or more such messages. + +**Table 9-31/G.991.2 – G.997.1 external information field** + +| Octet # | Contents | Data type | Reference | +|-------------|------------------------------------------|---------------|-----------| +| 1 | Message ID 121 | Message ID | | +| 2 | Logical Port Number | Unsigned char | | +| 3.. (N + 2) | G.997.1 External message data (N octets) | | | + +##### 9.5.5.7.26 Generic Unable to Comply (UTC) Message (ID 144) + +The Generic UTC message should be sent back to the source unit in the event that the destination unit is unable to comply with the request. In this case, the definition of UTC is vendor dependent. Note that this message is not meant to replace the UTC bit in those response messages that contain a UTC bit. + +**Table 9-32/G.991.2 – Generic Unable to Comply (UTC) information field** + +| Octet # | Contents | Data type | Reference | +|---------|-------------------------------|---------------|-----------| +| 1 | Message ID 144 – Generic UTC | Message ID | | +| 2 | Message ID of request message | Unsigned char | | + +##### 9.5.5.7.27 Mapping Request – Message ID 23 + +The Mapping Request Message is used to determine the mapping between the physical pair (or loop) number labelled on the equipment and the logical wire pair (or loop) ordinal number (7.2.1.5). While this mapping is vendor specific, this information is useful for troubleshooting circuits. The response to this request shall be message ID 151. + +**Table 9-32a/G.991.2 – Mapping Request information field** + +| Octet # | Contents | Data type | Reference | +|---------|----------|------------|-----------| +| 1 | 23 | Message ID | | + +##### 9.5.5.7.28 Mapping Response – Message ID 151 + +The Mapping Response Message is sent in response to a Mapping Request Message (message ID 23). It is used to determine the mapping between the physical pair (or loop) number and the logical wire pair (or loop) ordinal number. The physical pair number is the number labelled externally on the equipment. The logical wire pair number is determined from bits 4145 to 4146 of the activation frame from the STU-R device as specified in 7.2.1.5. The physical pair number is composed of two octets, with the first octet containing the most significant byte, and the second octet containing the least significant byte. For example, if the 16-bit number in octets 3/4 contains the value 4, then logical wire pair 1 from 7.2.1.5 is transported over the equipment's physical pair labelled number 4. If the responding unit is a repeater, then the mapping response information for the network side of the repeater will be sent first with bit 3 of octet two set to zero, followed immediately by the mapping response information for the customer side of the repeater with bit 3 of octet two set to one. + +**Table 9-32b/G.991.2 – Mapping Response information field** + +| Octet # | Contents | Data type | Reference | +|----------------------------------------|----------------------------------------------------------------------------|---------------|---------------------------------------------------------------| +| 1 | 151 | Message ID | | +| 2 bit 7 | Response Side | Bit | 0 = network side information
1 = customer side information | +| 2 bits 6-3 | Reserved | | | +| 2 bits 2-0 | Number of Wire Pairs, M | Unsigned | 1 = 1 pair
2 = 2 pair
3 = 3 pair
4 = 4 pair | +| 3-4 | Physical Pair Number Corresponding to Logical Wire Pair 1 (7.2.1.5) | Unsigned Char | | +| 5-6 | Physical Pair Number Corresponding to Logical Wire Pair 2 (7.2.1.5) | Unsigned Char | | +| | . | . | | +| | . | . | | +| | . | . | | +| $2 \times M + 1 -$
$2 \times M + 2$ | Physical Pair Number Corresponding to Logical Wire Pair M (7.2.1.5) | Unsigned Char | | + +### 9.5.6 Examples of virtual terminal control functions + +This informative note gives examples of some common ANSI X3.4-1986 (R1997) [B3] escape sequences. + +**Table 9-33/G.991.2 – Examples of ANSI X3.4-1986 (R1997) control functions** + +| Description | Format | Comments | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------| +| Erase entire screen (ED) | ESC [ 2 J | | +| Position cursor (CUP) | ESC [ RR;CCH | (Note) | +| Position cursor (in column 1) | ESC [ RRH | Subset of Position cursor | +| Home cursor | ESC [ H | Subset of Position cursor | +| NOTE – ESC has the value of 1B 16 . RR is the row number; CC is the column number expressed as ASCII digits. As an example, row 4 column 12 would encode as ESC [ 4;12H. The hexadecimal equivalent of this sequence is 1B 16 5B 16 34 16 3B 16 31 16 32 16 48 16 . The screen starts with row 1, column 1. | | | + +# 10 Clock architecture + +## 10.1 Reference clock architecture + +Due to the multiple applications and variable bit rates called for in SHDSL, a flexible clocking architecture is required. The STU-C and STU-R symbol clocks are described in terms of their allowed synchronization references. + +The SHDSL reference configuration permits the flexibility to provide a symbol clock reference based on the sources shown in Figure 10-1. It illustrates the clock reference options in the context of a simplified SHDSL reference model. Table 10-1 lists the normative synchronization configurations as well as example applications. + +![Figure 10-1/G.991.2 – Reference clock architecture. The diagram shows two SHDSL transceivers, STU-C and STU-R, connected by a bidirectional link. STU-C (left) has inputs for Transmit clk, Transmit data, Receive clk, and Receive data. It also has a 'Transmit symbol clock reference' input from a multiplexer. The multiplexer selects between 'Network reference clk' and 'Local oscillator'. STU-R (right) has inputs for Receive clk, Receive data, Transmit clk, and Transmit data. It also has a 'Transmit symbol clock reference' input from a multiplexer. This multiplexer selects between 'Local oscillator (Start-up mode only)' and 'Receive symbol clk'.](649d03e4c5c42598e91826f372146f65_img.jpg) + +Figure 10-1/G.991.2 – Reference clock architecture. The diagram shows two SHDSL transceivers, STU-C and STU-R, connected by a bidirectional link. STU-C (left) has inputs for Transmit clk, Transmit data, Receive clk, and Receive data. It also has a 'Transmit symbol clock reference' input from a multiplexer. The multiplexer selects between 'Network reference clk' and 'Local oscillator'. STU-R (right) has inputs for Receive clk, Receive data, Transmit clk, and Transmit data. It also has a 'Transmit symbol clock reference' input from a multiplexer. This multiplexer selects between 'Local oscillator (Start-up mode only)' and 'Receive symbol clk'. + +**Figure 10-1/G.991.2 – Reference clock architecture** + +**Table 10-1/G.991.2 – Clock synchronization configurations** + +| Mode number | STU-C symbol clock reference | STU-R symbol clock reference | Example application | Mode | +|-------------|------------------------------------------------|------------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------| +| 1 | Local oscillator | Received symbol clock | "Classic" HDSL | Plesiochronous | +| 2 | Network reference clock | Received symbol clock | "Classic" HDSL with embedded timing reference | Plesiochronous with timing reference | +| 3a | Transmit data clock or network reference clock | Received symbol clock | Main application is synchronous transport in both directions | Synchronous | +| 3b | Transmit data clock | Received symbol clock | Synchronous downstream transport and bit-stuffed upstream is possible | Hybrid:
downstream:
synchronous
upstream:
plesiochronous | + +## 10.2 Clock accuracy + +At all rates, the transmit symbol clock during data mode from any SHDSL device shall be accurate to within $\pm 32$ ppm of the nominal frequency. During activation, the STU-C shall maintain $\pm 32$ ppm accuracy of its transmit symbol clock, but the STU-R transmit symbol clock may vary up to $\pm 100$ ppm. + +## 10.3 Definitions of clock sources + +The following definitions shall apply to the clock sources shown in Figure 10-1. + +### 10.3.1 Transmit symbol clock reference + +A reference clock from which the actual transmit symbol clock is derived (i.e., the STU's transmit symbol clock is synchronized to this reference). + +### 10.3.2 Local oscillator + +A clock derived from an independent local crystal oscillator. + +### 10.3.3 Network reference clock + +A primary reference clock derived from the network. + +### 10.3.4 Transmit data clock + +A clock that is synchronous with the transmitted data at the application interface. + +### 10.3.5 Receive symbol clock + +A clock that is synchronous with the downstream received symbols at the SHDSL line interface. This clock is used as the transmit symbol clock reference in the STU-R. + +### 10.3.6 Receive clock + +A clock that is synchronous with the received data at the application interface. + +## 10.4 Synchronization to clock sources + +In synchronous mode, the STU-C can be synchronized to the transmit data clock or to a network reference clock. If a network reference clock is used, the transmit data clock must be synchronized to the network reference clock. (The various transmit data rates are independent of the reference clock frequency.) + +When available, the network reference clock shall be either a fundamental 8 kHz network clock or a related reference clock at some multiple of 8 kHz. Such reference clocks are typically 1544 MHz or 2048 MHz, although in some applications other frequencies, such as 64 kHz, may be available. These related clocks include implicit 8 kHz1 timing signals. Selection of a specific network clock reference frequency shall be application dependent. + +# 11 Electrical characteristics + +This clause specifies conformance tests for SHDSL equipment. These out-of-service tests verify the electrical characteristics of SHDSL metallic interfaces. + +--- + +1 The 6 ms SHDSL frame for synchronous data transport and the network 8 kHz clock have a fixed relationship. Each SHDSL frame contains $48(1 + i + n \times 8)$ bits ( $i = 0 \dots 7$ and $n = 3 \dots 36$ , or, optionally, $n = 37 \dots 89$ , as described in Annex F). The relationship can be calculated with: $T = 6 \text{ ms}/48 = 125 \text{ } \mu\text{s}$ and $f = 1/T = 8 \text{ kHz}$ . At the STU-R, an 8 kHz clock signal can be derived from the synchronous 6 ms frame. + +## 11.1 Longitudinal balance + +Longitudinal balance or longitudinal conversion loss (LCL) is a figure of merit describing the coupling between longitudinal $V_L$ (common mode) and metallic $V_M$ (normal mode) signal components. This term is equivalent to the familiar common mode rejection ratio (CMRR) and defined as follows: + +$$\text{Longitudinal Balance (dB)} = 20 \log \left| \frac{V_L}{V_M} \right|$$ + +Longitudinal balance at the SHDSL loop interface shall be measured with a coupling circuit having a metallic termination of $135 \Omega$ and a longitudinal termination of $33.8 \Omega$ (Figure 11-1). Example coupling circuits are shown in Appendix I. This test shall be performed with the DUT transmitter turned off (quiet mode) and with span power circuitry (in either CO and RT units) activated by an appropriate external DC current source/sink. The active power feed requirement may be waived for locally powered systems. + +![Figure 11-1/G.991.2 – Longitudinal balance measurement circuit diagram. A coupling circuit on the left is connected to a DC current source/sink and a SHDSL Device Under Test (DUT) on the right via Tip and Ring wires. The coupling circuit includes a metallic termination of 135 Ω and a longitudinal termination of 33.8 Ω. A voltage source V_L is connected between the coupling circuit and ground. A voltage V_M is measured across the Tip and Ring wires. Two 3.3 μF (min) capacitors are shown in series with the Tip and Ring wires. The local building earth ground is connected to the coupling circuit and the DUT.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +Figure 11-1/G.991.2 – Longitudinal balance measurement circuit diagram. A coupling circuit on the left is connected to a DC current source/sink and a SHDSL Device Under Test (DUT) on the right via Tip and Ring wires. The coupling circuit includes a metallic termination of 135 Ω and a longitudinal termination of 33.8 Ω. A voltage source V\_L is connected between the coupling circuit and ground. A voltage V\_M is measured across the Tip and Ring wires. Two 3.3 μF (min) capacitors are shown in series with the Tip and Ring wires. The local building earth ground is connected to the coupling circuit and the DUT. + +**Figure 11-1/G.991.2 – Longitudinal balance measurement** + +The measured longitudinal balance at the SHDSL loop interface shall lie above the specified limit mask defined in Figure 11-2. The values of the parameters in the figure are region-specific and are specified in A.5.4 and B.5.4. The longitudinal test circuit shall be calibrated such that when a $135 \Omega$ resistor (placed across tip and ring) is substituted for the device under test and the DC current source/sink is disconnected, the measured longitudinal balance shall be at least 20 dB above the limit mask. The longitudinal balance shall be measured over the frequency range of 20 kHz to 2 MHz. + +![Figure 11-2/G.991.2 – Longitudinal balance limit mask graph. The y-axis is Longitudinal balance (dB) and the x-axis is Frequency (Hz). The mask is defined by a horizontal line at LB_MIN between frequencies f1 and f2, and two 20 dB/decade rolloff slopes. The rolloff starts at f1 and ends at f2.](2ff3bb4f3d116d00cea2366069aa94aa_img.jpg) + +Figure 11-2/G.991.2 – Longitudinal balance limit mask graph. The y-axis is Longitudinal balance (dB) and the x-axis is Frequency (Hz). The mask is defined by a horizontal line at LB\_MIN between frequencies f1 and f2, and two 20 dB/decade rolloff slopes. The rolloff starts at f1 and ends at f2. + +**Figure 11-2/G.991.2 – Longitudinal balance limit mask** + +## 11.2 Longitudinal output voltage + +Longitudinal output voltage at the SHDSL loop interface shall be measured with a coupling circuit having a metallic termination of 135 Ω and a longitudinal termination of 33.8 Ω as shown in Figure 11-3. Example coupling circuits are shown in Appendix I. This test shall be performed with the transmitter active (sending random data) and the span power circuitry (in either CO and RT units) activated by an appropriate external DC current source/sink. The active power feed requirement may be waived for locally powered systems. + +![Figure 11-3/G.991.2 – Longitudinal output voltage measurement diagram.](b35ea3e304aad7d350a9902270413930_img.jpg) + +The diagram shows the test setup for measuring longitudinal output voltage. A 'Coupling circuit' block is connected to an 'SHDSL Device Under Test (DUT)' via 'Tip' and 'Ring' lines. Inside the coupling circuit, there is a 'Metallic term. = 135 Ω' and a 'Longitudinal term. = 33.8 Ω'. A 'High-impedance frequency selective voltmeter (or spectrum analyser)' is connected to the circuit through a 0.15 μF capacitor and a 100 Ω resistor. The voltmeter measures voltage \$V\$. Between the coupling circuit and the DUT, there are two 3.3 μF (min) capacitors on the Tip and Ring lines. A 'DC current source/sink' is connected across the lines between these capacitors and the DUT. The voltage across the lines at the coupling circuit is labeled \$V\_M\$. The system is connected to 'Local building earth ground'. The diagram is indexed as G.991.2\_F11-3. + +Figure 11-3/G.991.2 – Longitudinal output voltage measurement diagram. + +**Figure 11-3/G.991.2 – Longitudinal output voltage measurement** + +The measured longitudinal output rms voltage at the SHDSL loop interface shall be less than –50 dBV over any 4 kHz frequency band when averaged over one second periods. The measurement frequency range is region-specific and is specified in A.5.5 and B.5.5. + +## 11.3 Return loss + +This test measures return loss at the SHDSL loop interface with respect to a 135 Ω reference (line) impedance. In SHDSL applications, return loss is generally used as a measure of termination impedance distortion (deviation in both magnitude and phase from the reference impedance value). Return loss limits are necessary to prevent large termination mismatches between equipment from compliant vendors. Return loss may be measured directly using an impedance analyser or indirectly as a voltage output in a bridge circuit. For either method, care must be taken to prevent measurement errors from possible unintentional circuit paths between the common ground of the measuring instrument(s) and the DUT power feed circuitry. In addition, when measuring under span powered conditions, the test instrument must be galvanically isolated from the loop interface to prevent damaging the test equipment with the high voltage DC power feed. For measurements performed with an impedance analyser return loss is defined as follows: + +$$\text{Return Loss}(f) = 20 \log \left| \frac{Z_{TEST}(f) + Z_{REF}}{Z_{TEST}(f) - Z_{REF}} \right|$$ + +where: + +$Z_{TEST}(f)$ measured complex impedance at frequency $f$ at the DUT loop interface + +$Z_{REF}$ reference impedance (135 Ω). + +![Figure 11-4/G.991.2 – Return loss impedance analyser test method. The diagram shows an Impedance analyser (grounded isolated input) connected to the Ring and Tip lines of an SHDSL Device Under Test (DUT) via a Loop interface. Two 3.3 µF (min) capacitors are in series with the lines. A DC current source/sink is connected between the Ring and Tip lines at the Loop interface. Text below indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'. The diagram is labeled G.991.2_F11-4.](99698c448635861b7dc8d352f87a1b2b_img.jpg) + +Figure 11-4/G.991.2 – Return loss impedance analyser test method. The diagram shows an Impedance analyser (grounded isolated input) connected to the Ring and Tip lines of an SHDSL Device Under Test (DUT) via a Loop interface. Two 3.3 µF (min) capacitors are in series with the lines. A DC current source/sink is connected between the Ring and Tip lines at the Loop interface. Text below indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'. The diagram is labeled G.991.2\_F11-4. + +**Figure 11-4/G.991.2 – Return loss impedance analyser test method** + +For measurements performed with a test bridge the return loss is defined as follows: + +$$\text{Return Loss}(f) = 20 \log \left| \frac{V_{IN}(f)}{V_{OUT}(f)} \right|$$ + +An example return loss test bridge is shown in Appendix I. + +![Figure 11-5/G.991.2 – Return loss bridge test method. The diagram shows a Return loss test bridge (135 Ω) connected to the Ring and Tip lines of an SHDSL Device Under Test (DUT) via a Loop interface. Two 3.3 µF (min) capacitors are in series with the lines. A DC current source/sink is connected between the Ring and Tip lines at the Loop interface. An AC voltage source V_IN is connected to the input of the test bridge, and a high-impedance frequency selective voltmeter (or spectrum analyser) measures V_OUT across the bridge. Text below indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'. The diagram is labeled G.991.2_F11-5.](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +Figure 11-5/G.991.2 – Return loss bridge test method. The diagram shows a Return loss test bridge (135 Ω) connected to the Ring and Tip lines of an SHDSL Device Under Test (DUT) via a Loop interface. Two 3.3 µF (min) capacitors are in series with the lines. A DC current source/sink is connected between the Ring and Tip lines at the Loop interface. An AC voltage source V\_IN is connected to the input of the test bridge, and a high-impedance frequency selective voltmeter (or spectrum analyser) measures V\_OUT across the bridge. Text below indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'. The diagram is labeled G.991.2\_F11-5. + +**Figure 11-5/G.991.2 – Return loss bridge test method** + +The return loss test shall be performed with the DUT transmitter turned off (quiet mode). The DUT may be tested span powered or locally powered as required by the intended application of the DUT. For span powered applications, if the DUT is an STU-C the test shall be performed with the span power supply activated and an appropriate DC current sink (with high AC impedance) attached to the test circuit. If the DUT is an STU-R, the test shall be performed with power (DC voltage) applied at the loop interface (TIP/RING) by an external voltage source feeding through an AC blocking impedance. Note that the DC current source/sink must present a high impedance (at signal frequencies) to common ground. + +The nominal driving point impedance of the SHDSL loop interface shall be 135 Ω. Return loss shall be measured with either the impedance analyser method of Figure 11-4 or the bridge method of Figure 11-5. The measured return loss values relative to 135 Ω shall lie above the limit mask specified in Figure 11-6. The values of the parameters are region-specific, and are specified in A.5.2 and B.5.2. The loop interface return loss shall be measured over the frequency range of 1 kHz to 2 MHz. + +![Figure 11-6/G.991.2 – Return loss limit mask. A graph showing Return loss (dB) on the y-axis versus Frequency (Hz) on the x-axis. The y-axis has a label 0 at the origin and RL_MIN at the top. The x-axis has labels f0, f1, f2, and f3. The graph shows a trapezoidal shape: a line with a 20 dB/decade rolloff from (f0, 0) to (f1, RL_MIN), a horizontal line from (f1, RL_MIN) to (f2, RL_MIN), and a line with a 20 dB/decade rolloff from (f2, RL_MIN) to (f3, 0). Vertical dashed lines connect the corners at f1 and f2 to the x-axis. The label G.991.2_F11-6 is at the bottom right.](de7b700c44b3911907685dffd54fc50f_img.jpg) + +Figure 11-6/G.991.2 – Return loss limit mask. A graph showing Return loss (dB) on the y-axis versus Frequency (Hz) on the x-axis. The y-axis has a label 0 at the origin and RL\_MIN at the top. The x-axis has labels f0, f1, f2, and f3. The graph shows a trapezoidal shape: a line with a 20 dB/decade rolloff from (f0, 0) to (f1, RL\_MIN), a horizontal line from (f1, RL\_MIN) to (f2, RL\_MIN), and a line with a 20 dB/decade rolloff from (f2, RL\_MIN) to (f3, 0). Vertical dashed lines connect the corners at f1 and f2 to the x-axis. The label G.991.2\_F11-6 is at the bottom right. + +**Figure 11-6/G.991.2 – Return loss limit mask** + +## 11.4 Transmit power testing + +The total average transmit power may be tested while span powered or locally powered as required by the intended application of the DUT. For span powered applications, if the DUT is an STU-C the test shall be performed with the span power supply activated and an appropriate DC current sink (with high AC impedance) attached to the test circuit. If the DUT is an STU-R, the test shall be performed with power (DC voltage) applied at the loop interface (TIP/RING) by an external voltage source feeding through an AC blocking impedance. The test circuit must contain provisions for DC power feed and possibly transformer isolation for the measurement instrumentation. Note that the DC current source/sink must present a high impedance (at signal frequencies) to common ground. + +![Figure 11-7/G.991.2 – PSD/total power measurement set-up. A circuit diagram showing a voltage source V_OUT connected to a 135 Ω termination (grounded isolated input). This is connected via two 3.3 μF (min) capacitors to a DC current source/sink. The current source/sink is connected to a pair of wires labeled Tip and Ring. A return loss measurement point is indicated on the wires with the text 'Return loss (135 Ω reference) as per calibration template'. The wires are connected to an SHDSL Device Under Test (DUT), which is grounded. The label G.991.2_F11-7 is at the bottom right.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +Figure 11-7/G.991.2 – PSD/total power measurement set-up. A circuit diagram showing a voltage source V\_OUT connected to a 135 Ω termination (grounded isolated input). This is connected via two 3.3 μF (min) capacitors to a DC current source/sink. The current source/sink is connected to a pair of wires labeled Tip and Ring. A return loss measurement point is indicated on the wires with the text 'Return loss (135 Ω reference) as per calibration template'. The wires are connected to an SHDSL Device Under Test (DUT), which is grounded. The label G.991.2\_F11-7 is at the bottom right. + +**Figure 11-7/G.991.2 – PSD/total power measurement set-up** + +### 11.4.1 Test circuit + +The test circuit must contain provisions for DC power feed and possibly transformer isolation for the measurement instrumentation. Transformer isolation of the instrumentation input prevents measurement errors from unintentional circuit paths through the common ground of the instrumentation and the DUT power feed circuitry. When the driving point impedance of the test circuit meets the calibration requirements defined in 11.4.2, the test circuit will not introduce more than $\pm 0.25$ dB error with respect to a perfect $135\ \Omega$ test load. An example test circuit is shown in Appendix I. Note that the same circuit may be used for measuring total transmit power and transmit PSD. + +### 11.4.2 Test circuit calibration + +The nominal driving point impedance of the test circuit shall be $135\ \Omega$ . The minimum return loss with respect to $135\ \Omega$ over the frequency band of 3 kHz to 3 MHz shall be 35 dB from 10 kHz to 500 kHz with a slope of 20 dB/decade below and above these corner frequencies. + +NOTE – 35 dB return loss will allow $\pm 0.20$ dB measurement error with respect to the nominal $135\ \Omega$ value. + +### 11.4.3 Total transmit power requirement + +The average transmit power of the STU-C shall be measured while continuously sending either signal $S_c$ (6.2.2.2) or signal $Data_c$ (6.2.2.7). If $Data_c$ is used, the total power measured into $135\ \Omega$ shall fall in the range $(P_{SHDSL} \pm 0.5\ \text{dB})$ as specified in A.4 and B.4. If $S_c$ is used, the total power measured into $135\ \Omega$ shall fall in the range $(P_{SHDSL} - 0.2\ \text{dB} \pm 0.5\ \text{dB})$ . The average transmit power of the STU-R shall be measured while continuously sending either signal $S_r$ (6.2.2.3) or signal $Data_r$ (6.2.2.7). If $Data_r$ is used, the total power measured into $135\ \Omega$ shall fall in the range $(P_{SHDSL} \pm 0.5\ \text{dB})$ as specified in A.4 and B.4. If $S_r$ is used, the total power measured into $135\ \Omega$ shall fall in the range $(P_{SHDSL} - 0.2\ \text{dB} \pm 0.5\ \text{dB})$ . This power measurement in activation mode will be 0.2 dB lower than the associated data mode transmit power due to the 2-PAM constellation definition. + +The transmit power spectral density of the STU-C shall be measured while continuously sending either signal $S_c$ (6.2.2.2) or signal $Data_c$ (6.2.2.7). The transmit power spectral density of the STU-R shall be measured while continuously sending either signal $S_r$ (6.2.2.3) or signal $Data_r$ (6.2.2.7). If $Data_c$ or $Data_r$ is used, the measured transmit PSD into $135\ \Omega$ shall remain below the corresponding $PSDMask(f)$ from A.4 and B.4. If $S_c$ or $S_r$ is used, the measured transmit PSD into $135\ \Omega$ shall remain below the corresponding $PSDMask(f)$ from A.4 and B.4 reduced by 0.2 dB in the passband (i.e., $PSDMask(f)$ with PBO increased by 0.2 dB). + +#### 11.4.3.1 Transmit power spectral density test procedure + +The transmit power spectral density (PSD) may be tested span powered or locally powered as required by the intended application of the DUT. For span powered applications, if the DUT is an STU-C the test shall be performed with the span power supply activated and an appropriate DC current sink (with high AC impedance) attached to the test circuit. If the DUT is an STU-R, the test shall be performed with power (DC voltage) applied at the loop interface (TIP/RING) by an external voltage source feeding through an AC blocking impedance. + +The transmit power spectral density for the STU-C and STU-R shall be measured with signals as defined in 11.4.3. The transmit power spectral density shall be measured over the frequency range of 1 kHz to 3 MHz. The STU-C transmit signal shall be compliant with the appropriate A.4 or B.4 PSD requirements. The STU-R transmit signal shall be compliant with the appropriate A.4 or B.4 PSD requirements. + +#### 11.4.3.2 PSD test circuit and calibration + +The test circuit must contain provisions for DC power feed and possibly transformer isolation for the measurement instrumentation. Transformer isolation of the instrumentation input prevents measurement errors from unintentional circuit paths through the common ground of the instrumentation and the DUT power feed circuitry. The test circuit shall meet the requirements of 11.4.2. + +## 11.5 Signal transfer delay + +The STU shall be capable of providing PMD-layer one-way, single-span latency of 500 $\mu\text{s}$ or less for user data rates of 1.5 Mbit/s and above, and 1.25 ms or less for user data rates below 1.5 Mbit/s as measured between the $\alpha$ and $\beta$ interfaces. + +# 12 Conformance testing + +## 12.1 Micro-interruptions + +A micro-interruption is a temporary interruption due to external mechanical action on the copper wires constituting the transmission segment, for example, at a cable splice. Splices can be hand-made wire-to-wire junctions, and during cable life oxidation phenomena and mechanical vibrations can induce micro-interruptions at these critical points. Example causes of this impairment include a large motor vehicle driving over a buried cable installation or an aerial cable movement from wind forces. + +The effect of a micro-interruption on the transmission system can be a failure of the digital transmission link, together with a failure of the span power feeding (if provided) for the duration of the micro-interruption. The operating objective is that in the presence of a micro-interruption of specified maximum length the system shall not reset, and the system shall automatically reactivate with a complete start-up procedure if a reset occurs due to an interruption. + +The configuration for micro-interruption susceptibility testing is shown in Figure 12-1. In this arrangement, a periodic trigger signal $S$ stimulates a normally closed micro-relay device inducing periodic micro-interruptions on the transmission link. Note that the micro-interruptions are induced on one termination at a time. The test loops shall be composed of 1.5 km of 0.4 mm (or 5000' of 26 AWG) copper wire, and the tests shall be conducted at the maximum supported data rate. Using the test arrangement as described in Figure 12-1 with local powering on, the SHDSL transceivers shall not be reset by a micro-interruption of at least $t = 10$ ms when stimulated with a signal of period $T = 5$ s for a test interval of 60 s at a single termination. The micro-interruptions shall be induced at both the STU-C and STU-R terminations. This test shall be repeated with span-powering on and a micro-interruption of at least $t = 1$ ms. + +![Figure 12-1/G.991.2 – Micro-interruption test circuit diagram. The diagram shows a block diagram of the test setup and a timing diagram. The block diagram consists of an STU-C block on the left, a 'Test loop' block in the center, and an STU-R block on the right. Two lines connect the STU-C block to the Test loop, and two lines connect the Test loop to the STU-R block. Each connection line has a switch symbol. A dashed box encloses the Test loop and the switches on its right side. Below the dashed box is an 'Impulse generator' block, with a dashed arrow pointing from it to the switches. The timing diagram below shows a signal 'S' as a periodic square wave. The pulse width is labeled 't' and the period is labeled 'T'.](a634891d16b60b21df90a35c2af72c67_img.jpg) + +The diagram illustrates the micro-interruption test circuit. At the top, a block diagram shows an STU-C (Subscriber Terminal Unit - C) connected to a 'Test loop', which is in turn connected to an STU-R (Subscriber Terminal Unit - R). Each connection between the STU and the Test loop is made via a pair of lines, each containing a switch. A dashed box surrounds the Test loop and the switches on the STU-R side. Below this box, an 'Impulse generator' is shown, with a dashed arrow pointing to the switches, indicating it provides the triggering signal. Below the block diagram is a timing diagram for the signal 'S'. It shows a square wave with a pulse width labeled 't' and a period labeled 'T'. + +Figure 12-1/G.991.2 – Micro-interruption test circuit diagram. The diagram shows a block diagram of the test setup and a timing diagram. The block diagram consists of an STU-C block on the left, a 'Test loop' block in the center, and an STU-R block on the right. Two lines connect the STU-C block to the Test loop, and two lines connect the Test loop to the STU-R block. Each connection line has a switch symbol. A dashed box encloses the Test loop and the switches on its right side. Below the dashed box is an 'Impulse generator' block, with a dashed arrow pointing from it to the switches. The timing diagram below shows a signal 'S' as a periodic square wave. The pulse width is labeled 't' and the period is labeled 'T'. + +Figure 12-1/G.991.2 – Micro-interruption test circuit + +# Annex A + +## Regional requirements – Region 1 + +## A.1 Scope + +This annex describes those specifications that are unique to SHDSL systems operating under conditions such as those typically encountered within the North American network. The clauses in this annex provide the additions and modifications to the corresponding clauses in the main body. + +## A.2 Test loops + +The primary constants for the following test loops are listed in Annex A/G.996.1 [6]. Note that the test loops shown in Figure A.1 are PIC and specified at 70° F (21.1° C). Loop 0 is the null loop: $\leq 10'$ and $\leq 26$ AWG. + +![Diagram showing six test loop configurations (Loop S, Loop BT1-C, Loop BT1-R, Loop BT2-C, Loop BT2-R, Loop C4) between STU-R and STU-C units. Each loop consists of various lengths of 26 AWG and 24 AWG wire segments.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +The diagram illustrates six test loop configurations between an STU-R (Sender/Receiver) and an STU-C (Codec) unit. Each loop is labeled on the left and shows the wire segments and their lengths between the two units. + +- Loop S:** A single horizontal segment of $L \times 1000'$ of 26 AWG wire connects STU-R and STU-C. +- Loop BT1-C:** A horizontal segment of $L \times 1000'$ of 26 AWG wire connects STU-R to a junction point near STU-C. From this junction, an 800' bridged tap of 24 AWG wire extends vertically. The main line continues to STU-C. +- Loop BT1-R:** A horizontal segment of $L \times 1000'$ of 26 AWG wire connects STU-R to STU-C. Near STU-R, there is a junction point from which an 800' bridged tap of 24 AWG wire extends vertically. +- Loop BT2-C:** A horizontal segment of $L \times 1000'$ of 26 AWG wire connects STU-R to STU-C. Near STU-C, there is a junction point from which a 1500' bridged tap of 26 AWG wire extends vertically. +- Loop BT2-R:** A horizontal segment of $L \times 1000'$ of 26 AWG wire connects STU-R to STU-C. Near STU-R, there is a junction point from which a 1500' bridged tap of 26 AWG wire extends vertically. +- Loop C4:** A complex series of segments connects STU-R to STU-C. From STU-R, there is an 800' segment of 26 AWG wire to a junction point. From this junction, an 800' bridged tap of 26 AWG wire extends vertically. The main line continues with a 6250' segment of 26 AWG wire to a second junction point. From this second junction, a 400' bridged tap of 26 AWG wire extends vertically. The main line then concludes with a 550' segment of 26 AWG wire to STU-C. + +G.991.2\_FA-1 + +Diagram showing six test loop configurations (Loop S, Loop BT1-C, Loop BT1-R, Loop BT2-C, Loop BT2-R, Loop C4) between STU-R and STU-C units. Each loop consists of various lengths of 26 AWG and 24 AWG wire segments. + +NOTE – AWG = American Wire Gauge; 26 AWG = 0.4 mm, 24 AWG = 0.5 mm. +Distances in feet ('): 1000' = 0.3048 km. + +**Figure A.1/G.991.2 – Test loops** + +## A.3 Performance Tests + +This clause specifies performance tests for SHDSL equipment. These out-of-service tests verify the performance of SHDSL in impaired environments. + +Figure A.2 shows the test set-up for measuring the performance of SHDSL systems in the presence of noise impairments. The test system consists of an SHDSL central office transceiver (STU-C) and a remote end transceiver (STU-R). The SHDSL transceivers are connected by a test loop. Simulated noise is locally injected into the test loop through the specified coupling circuit at the receiving transceiver. + +Bit error ratio (BER) measurement is performed by applying a pseudo-random binary sequence (PRBS) test signal at one transceiver input and detecting errors in the received PRBS data stream of the other transceiver. The PRBS signal shall have a minimum period of $2^{23} - 1$ . BER measurement shall be performed for both directions of transmission and the tests in each direction shall be performed in full-duplex mode with both SHDSL transceivers simultaneously transmitting data. In all cases these noise impairment tests shall be performed one unit at a time (i.e., the STU-C and STU-R are not impaired simultaneously) and with noise from only one impairment source active at a time. + +![Block diagram of the crosstalk margin and impulse noise test set-up. Two SHDSL Transceivers are connected via a Test Loop. Each transceiver is connected to a PRBS Pattern Generator and a PRBS Pattern Receiver, which in turn connect to an Error Count. Noise sources (White Noise Source, Impulse Waveform Generator, Power-Related Metallic Noise Source, and Power-Related Longitudinal Source) are connected to Hi-Z or Hi-Z* coupling circuits, which are then connected to a Variable Attenuator and a NEXT/FEXT Filter. The output of the filter is connected to the Test Loop via a switch and a summing junction.](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +The diagram illustrates the test setup for SHDSL performance testing under noise impairments. It features two SHDSL Transceivers connected by a central Test Loop. Each transceiver is paired with a PRBS Pattern Generator and a PRBS Pattern Receiver, which are further connected to an Error Count block. On the left side, four noise sources are shown: White Noise Source, Impulse Waveform Generator, Power-Related Metallic Noise Source, and Power-Related Longitudinal Source. The first three are connected to Hi-Z coupling blocks, while the fourth is connected to a Hi-Z\* coupling block. These coupling blocks feed into a Variable Attenuator and a NEXT/FEXT Filter. The output of the filter is connected to a switch that can select different noise sources. The switch output is connected to a summing junction (represented by a circle with a cross) which is also connected to the Test Loop. This setup allows for the injection of various simulated noise types into the test loop to evaluate the transceivers' performance. + +Block diagram of the crosstalk margin and impulse noise test set-up. Two SHDSL Transceivers are connected via a Test Loop. Each transceiver is connected to a PRBS Pattern Generator and a PRBS Pattern Receiver, which in turn connect to an Error Count. Noise sources (White Noise Source, Impulse Waveform Generator, Power-Related Metallic Noise Source, and Power-Related Longitudinal Source) are connected to Hi-Z or Hi-Z\* coupling circuits, which are then connected to a Variable Attenuator and a NEXT/FEXT Filter. The output of the filter is connected to the Test Loop via a switch and a summing junction. + +\*Longitudinal Coupling Circuit + +G.991.2\_FA-2 + +Figure A.2/G.991.2 – Crosstalk margin and impulse noise test set-up + +### A.3.1 Crosstalk margin tests + +#### A.3.1.1 Crosstalk noise injection + +Simulated crosstalk (NEXT and FEXT) is introduced by injecting a calibrated, filtered Gaussian noise source into the test circuit. The crosstalk shall be locally injected into the test loop at the receiving transceiver through a balanced high-impedance parallel-connected feed network. The high-impedance parallel-connected feed network allows injection of the desired crosstalk power level without disturbing the transmission characteristics or driving point impedance of the test loop. The injection circuit shall have a Thevenin output impedance of at least 4 k $\Omega$ . An example crosstalk signal injection circuit is shown in Figure I.1. + +#### A.3.1.2 Calibration accuracy of crosstalk generator + +The simulated crosstalk shall have the total power and the power spectral density (PSD) defined in A.3.3. However, if the method of generating simulated crosstalk is as defined in Figure A.2, then the power level and PSD accuracy will depend on the accuracy of the filters designed to shape the white noise for each injected crosstalk source. The highest level of accuracy is required within the frequency band (or bands) corresponding to the largest values of the PSD for each crosstalk source. + +For each specified crosstalk source, the accuracy of the simulated PSD obtained shall be $\pm 1.0$ dB within the ideal PSD template (defined by the equations in A.3.3) over the frequency band(s) where the ideal PSD template is within 30 dB of its maximum value. The measured average power (integral of the crosstalk PSD function) for each specified crosstalk source shall be within $\pm 0.25$ dB of the integrated power of the ideal specified crosstalk PSD template (A.3.3). + +The white noise source of Figure A.2 shall cover the frequency band from DC to 1.5 MHz and have a Gaussian amplitude distribution with a crest factor of at least 5.0. + +#### A.3.1.3 Calibration measurement of crosstalk generator + +The PSD and average power for each crosstalk test scenario shall be calibrated by measuring the output of the crosstalk injection circuit with the test loop replaced by a load of two parallel 135 $\Omega$ resistors (67.5 $\Omega$ ) and no connected terminal equipment. The two parallel 135 $\Omega$ resistors simulate the terminating load of a zero-length loop. The crosstalk signal shall be measured as a voltage by a high-impedance frequency-selective voltmeter (i.e., spectrum analyser) and converted into a power level assuming a 135 $\Omega$ reference impedance. This procedure effectively measures the crosstalk power fed into a single resistor (one side of the loop only). The measured crosstalk PSD(s) and average crosstalk power(s) coupled into the calibration load must remain within the limits defined in A.3.1.2 for each specified crosstalk scenario defined in A.3.1.6. + +NOTE – The injected noise is intended to match the theoretical noise PSD when the transceiver under test is connected to the loop. On Loop S for payload rates of 1024 kbit/s and below, and on all loops for payload rate of 192 kbit/s, it has been found that impedance mismatch could generate an increased noise PSD at low frequencies. One method of compensation is to modify the factor, $\Delta$ , defined in A.3.1.4 by replacing the theoretical noise, $N(f)$ , in step 3 of A.3.1.4 with the noise PSD measured when connected to the loop under test. A second method is to place a passive circuit, consisting of a resistor $R$ in parallel with a capacitor $C$ , in series with each wire of the noise generator output pair. The RC values of $R = 1.2$ k $\Omega$ and $C = 1$ $\mu$ F are suggested and should be adjusted for each noise generator such that the injected noise matches the theoretical noise PSD. A third method is to calibrate the noise generator waveform into the loop under test such that when connected to the loop under test, the theoretical noise waveform is present at the transceiver terminals. + +#### A.3.1.4 Calibration of loop simulator + +There is significant variation in loop insertion loss for the same loop model on loop simulators from both different and identical manufacturers. Typical loop simulators may exhibit insertion loss variations greater than $\pm 1.0$ dB of the ideal loop model over the SHDSL signal band. Insertion loss variation of loop simulators may cause significant variation of measured system noise margin. To + +minimize measurement variation caused by the loop simulator, the crosstalk generator output power may be adjusted to maintain a consistent SNR at the receiver input. The calibration procedure is as follows: + +- 1) Given the discrete form of the DFE-based SNR formula, $SNR_{dB}$ , given below: + +$$SNR_{dB} = \frac{1}{M} \sum_{k=1}^M 10 \log_{10} \left( 1 + \frac{S(f_{sym} - f_k) |H(f_{sym} - f_k)|^2}{N(f_{sym} - f_k)} + \frac{S(f_k) |H(f_k)|^2}{N(f_k)} + \frac{S(2f_{sym} - f_k) |H(2f_{sym} - f_k)|^2}{N(2f_{sym} - f_k)} + \frac{S(f_{sym} - f_k) |H(f_{sym} - f_k)|^2}{N(f_{sym} - f_k)} \right)$$ + +calculate $SNR1$ , the ideal receive signal-to-noise ratio, by setting $SNR1$ equal to $SNR_{dB}$ where $S(f)$ shall be the nominal far-end transmit signal power spectral density (*NominalPSD(f)* from A.4), $|H(f)|^2$ shall be the magnitude squared of the ideal loop insertion gain function, $N(f)$ shall be the injected crosstalk noise power spectral density (*PSDCase-n(f)* from A.3.3.9), and $f_{sym}$ shall be the transmit symbol rate. For this application use $f_k = k \times 1000$ , $k = 1 \dots M$ , where $M$ is the maximum value of $k$ such that $M \times 1000 < f_{sym} \leq (M + 1) \times 1000$ . The ideal loop insertion gain function shall be calculated from the primary constants of twisted pair copper as defined in Annex A/G.996.1 [6]. + +- 2) Measure the insertion loss of the loop simulator with 135 $\Omega$ terminations at points $f_k$ defined in step 1. Note that the termination return loss with respect to 135 $\Omega$ should be greater than 35 dB from 20 kHz to $f_{sym}$ to ensure insertion loss measurement accuracy within 0.25 dB over the main part of the SHDSL signal band. An example insertion loss measurement set-up is shown in Figure A.3. The measured loss in dB of the loop at each frequency shall be within 5% (in dB) of the theoretical loop insertion loss function as calculated in step 1. As the measurements for the calibration procedure are easily made with error, the return loss measurement set used to verify the 35 dB return loss of the test fixture terminations shall be calibrated with a known return loss test load of at least 55 dB over the range of 20 kHz to 500 kHz. In addition, the line simulator should exhibit a longitudinal balance of 35 dB or better for frequencies in the range of 0 to $f_{sym}$ . + +![Figure A.3/G.991.2 – Example loop insertion loss measurement set-up. The diagram shows a 'Zero-length reference loop' connected to a 'Loop simulator (DUT)'. The reference loop is connected to a 'Tracking gen. Input (V2)' and a 'Spectrum analyser'. The DUT is connected to a 'Balun' (50 Ω : 135 Ω) and a 'Balun' (135 Ω : 50 Ω). The formula for insertion gain is given as 20log10(V2TEST/V2REF).](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +The diagram illustrates the measurement setup for loop insertion loss. A 'Zero-length reference loop' is shown at the top, connected to a 'Tracking gen. Input (V2)' and a 'Spectrum analyser'. Below it, a 'Loop simulator (DUT)' is connected to two 'Balun' units. The left Balun is labeled '50 Ω : 135 Ω' and the right one is '135 Ω : 50 Ω'. The DUT is connected to the Baluns via 'REF' and 'TEST' points. The formula for insertion gain is given as $20 \log_{10}(V_{2TEST}/V_{2REF})$ . The diagram also shows the connection to a 'Spectrum analyser' and the 'Tracking gen. output'. + +Figure A.3/G.991.2 – Example loop insertion loss measurement set-up. The diagram shows a 'Zero-length reference loop' connected to a 'Loop simulator (DUT)'. The reference loop is connected to a 'Tracking gen. Input (V2)' and a 'Spectrum analyser'. The DUT is connected to a 'Balun' (50 Ω : 135 Ω) and a 'Balun' (135 Ω : 50 Ω). The formula for insertion gain is given as 20log10(V2TEST/V2REF). + +G.991.2\_FA-3 + +Figure A.3/G.991.2 – Example loop insertion loss measurement set-up + +- 3) Calculate $SNR2$ , the measured receive signal-to-noise ratio, by setting $SNR2$ equal to $SNR_{dB}$ from step 1 where $|H(f)|^2$ is the magnitude squared of the measured loop insertion gain function from step 2 above, and $S(f)$ , $N(f)$ , $f_{sym}$ , and $f_k$ are the same as in step 1 above. +- 4) Adjust the noise margin target in Table A.1 by $\Delta = (SNR2 - SNR1)$ dB. Note that a negative difference corresponds to a decrease in crosstalk generator power. Note that this procedure assumes the crosstalk generator was previously calibrated as per A.3.1.2 and A.3.1.3. All crosstalk power adjustments shall be limited to 3.0 dB maximum. Test set-ups requiring greater than 3.0 dB crosstalk power adjustment shall not be valid. + +#### A.3.1.5 Crosstalk margin compliance procedure + +The SHDSL transceivers shall have noise margins that meet or exceed the values listed in Table A.1 for the specified test loop and crosstalk combinations. The definitions of the test loops are given in Figure A.1, and specifications for the crosstalk PSDs are given in A.3.3. The test for noise margin compliance shall be defined as follows: + +- 1) Calibrate the crosstalk injection circuit (using the calibration load of 67.5 $\Omega$ ) to the corresponding PSD and total power value specified in A.3.3. +- 2) Increase the injected crosstalk power by the corresponding noise margin value specified in Table A.1. +- 3) Using the test set-up from Figure A.2, activate the SHDSL transceivers and allow a minimum 5-minute fine-tuning period. +- 4) Measure the BER over a minimum of $10^9$ bits. +- 5) The measured BER at each end shall be less than $10^{-7}$ . + +#### A.3.1.6 Crosstalk interference requirements + +Table A.1 shows the minimum set of test loops and crosstalk combinations required for testing SHDSL margins. A compliant unit shall pass the BER test described in A.3.1.5 for all crosstalk scenarios and test loops defined in Table A.1. 0 dB Power Backoff shall be used for both the STU-C and STU-R. + +**Table A.1/G.991.2 – Crosstalk scenarios & required SHDSL noise margins (Note)** + +| Test | Test loop (from Figure A.1) | $L$ ( $\times 1000'$ ) | Test unit | Payload data rate (kbit/s) | PSD | Interferer combination | Required margin (dB) | +|------|-----------------------------|------------------------|-----------|----------------------------|------------|------------------------|----------------------| +| 1 | C4 | – | STU-C | 1544 | Asymmetric | 24T1 + 24 SHDSL | $5 + \Delta^*$ | +| 2 | C4 | – | STU-C | 1544 | Asymmetric | 39 SHDSL | $5 + \Delta^*$ | +| 3 | C4 | – | STU-C | 1544 | Asymmetric | 24 FDD ADSL + 24 HDSL | $5 + \Delta^*$ | +| 4 | S | 9.0 | STU-C | 1544 | Asymmetric | 24T1 + 24 SHDSL | $5 + \Delta^*$ | +| 5 | S | 9.0 | STU-C | 1544 | Asymmetric | 39 SHDSL | $5 + \Delta^*$ | +| 6 | S | 9.0 | STU-C | 1544 | Asymmetric | 24 FDD ADSL + 24 HDSL | $5 + \Delta^*$ | +| 7 | C4 | – | STU-R | 1544 | Asymmetric | 24T1 + 24 SHDSL | $5 + \Delta^*$ | +| 8 | S | 9.0 | STU-R | 1544 | Asymmetric | 24T1 + 24 SHDSL | $5 + \Delta^*$ | + +**Table A.1/G.991.2 – Crosstalk scenarios & required SHDSL noise margins (Note)** + +| Test | Test loop (from Figure A.1) | $L$ ( $\times 1000'$ ) | Test unit | Payload data rate (kbit/s) | PSD | Interferer combination | Required margin (dB) | +|------|-----------------------------|------------------------|-----------|----------------------------|-----------|----------------------------------|----------------------| +| 9 | S | 6.3 | STU-C | 2304 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 10 | BT1-C | 5.2 | STU-C | 2304 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 11 | BT1-C | 5.2 | STU-C | 2304 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 12 | S | 6.3 | STU-R | 2304 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 13 | BT1-R | 5.2 | STU-R | 2304 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 14 | BT1-R | 5.2 | STU-R | 2304 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 15 | S | 6.8 | STU-C | 2048 | Symmetric | 24-SHDSL + 24-FDD ADSL | $5 + \Delta^*$ | +| 16 | BT1-C | 5.6 | STU-C | 2048 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 17 | BT1-C | 5.6 | STU-C | 2048 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 18 | S | 6.8 | STU-R | 2048 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 19 | BT1-R | 5.6 | STU-R | 2048 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 20 | BT1-R | 5.6 | STU-R | 2048 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 21 | S | 7.9 | STU-C | 1544 | Symmetric | 39-SHDSL asym 1544 | $5 + \Delta^*$ | +| 22 | BT1-C | 6.4 | STU-C | 1544 | Symmetric | 24-FDD ADSL + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 23 | BT1-C | 6.4 | STU-C | 1544 | Symmetric | 24-SHDSL + 24-FDD ADSL | $5 + \Delta^*$ | +| 24 | S | 7.9 | STU-R | 1544 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 25 | BT1-R | 6.4 | STU-R | 1544 | Symmetric | 24-T1 + 24 SHDSL asym 1544 | $5 + \Delta^*$ | +| 26 | BT1-R | 6.4 | STU-R | 1544 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 27 | S | 11.0 | STU-C | 768 | Symmetric | 49-HDSL | $5 + \Delta^*$ | +| 28 | BT1-C | 10.2 | STU-C | 768 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 29 | BT1-C | 10.2 | STU-C | 768 | Symmetric | 49-HDSL | $5 + \Delta^*$ | +| 30 | S | 11.0 | STU-R | 768 | Symmetric | 49-HDSL | $5 + \Delta^*$ | +| 31 | BT1-R | 10.2 | STU-R | 768 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 32 | BT1-R | 10.2 | STU-R | 768 | Symmetric | 49-HDSL | $5 + \Delta^*$ | + +**Table A.1/G.991.2 – Crosstalk scenarios & required SHDSL noise margins (Note)** + +| Test | Test loop (from Figure A.1) | $L$ ( $\times 1000'$ ) | Test unit | Payload data rate (kbit/s) | PSD | Interferer combination | Required margin (dB) | +|------|-----------------------------|------------------------|-----------|----------------------------|------------|------------------------|----------------------| +| 33 | S | 11.2 | STU-C | 768 | Asymmetric | 49-HDSL | $5 + \Delta^*$ | +| 34 | BT1-C | 10.4 | STU-C | 768 | Asymmetric | 49-HDSL | $5 + \Delta^*$ | +| 35 | BT1-C | 10.4 | STU-C | 768 | Asymmetric | 24-FDD ADSL + 24-HDSL | $5 + \Delta^*$ | +| 36 | S | 11.2 | STU-R | 768 | Asymmetric | 24-T1 + 24 HDSL | $5 + \Delta^*$ | +| 37 | BT1-R | 10.4 | STU-R | 768 | Asymmetric | 24-T1 + 24-SHDSL | $5 + \Delta^*$ | +| 38 | BT1-R | 10.4 | STU-R | 768 | Asymmetric | 39-FDD ADSL | $5 + \Delta^*$ | +| 39 | S | 14.8 | STU-C | 384 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 40 | BT2-C | 13.8 | STU-C | 384 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 41 | BT2-C | 13.8 | STU-C | 384 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 42 | S | 14.8 | STU-R | 384 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 43 | BT2-R | 13.8 | STU-R | 384 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 44 | BT2-R | 13.8 | STU-R | 384 | Symmetric | 49-SHDSL | $5 + \Delta^*$ | +| 45 | S | 17.2 | STU-C | 256 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 46 | BT2-C | 16.4 | STU-C | 256 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 47 | BT2-C | 16.4 | STU-C | 256 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 48 | S | 17.2 | STU-R | 256 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 49 | BT2-R | 16.4 | STU-R | 256 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 50 | BT2-R | 16.4 | STU-R | 256 | Symmetric | 24-SHDSL + 24-DSL | $5 + \Delta^*$ | +| 51 | S | 19.8 | STU-C | 192 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 52 | BT2-C | 19.1 | STU-C | 192 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 53 | BT2-C | 19.1 | STU-C | 192 | Symmetric | 24-DSL + 24 SHDSL | $5 + \Delta^*$ | +| 54 | S | 19.8 | STU-R | 192 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 55 | BT2-R | 19.1 | STU-R | 192 | Symmetric | 49-DSL | $5 + \Delta^*$ | +| 56 | BT2-R | 19.1 | STU-R | 192 | Symmetric | 24-DSL + 24 SHDSL | $5 + \Delta^*$ | + +NOTE – The crosstalk scenarios listed in this table were developed under the assumption of a 50-pair cable binder. Cable binders of other sizes are for further study. + +\* The indicated noise margins in Table A.1 shall have a tolerance of 1.25 dB due to the aggregate effect of crosstalk generator tolerance and calibrated loop simulator tolerance. The offset $\Delta$ is defined in A.3.1.4. + +All interferers are assumed to be co-located. The notation 24 or 49 SHDSL refers to SHDSL at the same rate and PSD as the system under test. All interferer PSDs are described in A.3.3.9. + +The process for selecting which tests to perform for a specific G.991.2 device under test (DUT) is determined by following each of these 6 steps in order: + +- 1) Determine the set of rates which are in common between the set of supported payload data rates and the following set of payload data rates: (symmetric PSD: 192, 256, 384, 768, 1544, 2048, 2304 kbit/s; asymmetric PSD: 768, 1544 kbit/s). Call the resulting list of common rates the intersection list. +- 2) If 1544 kbit/s asymmetric is in the intersection list, then test the DUT with test cases 1-8 in Table A.1. +- 3) If 768 kbit/s asymmetric is in the intersection list, then test the DUT with test cases 33-38 in Table A.1. +- 4) If 1544 kbit/s symmetric is in the intersection list, then test the DUT with test cases 21-26. +- 5) For the highest and the lowest symmetric PSD rate in the intersection list, test the DUT with all six cases associated with that rate. For example, if 192 kbit/s symmetric is the lowest rate and 2304 kbit/s symmetric is the highest rate, then test with test cases 51-56 and 9-14 in Table A.1. +- 6) For all remaining rates in the intersection list that have not been tested, test using the cases involving only Loop S. For example, if 256, 384, 768 and 2048 kbit/s symmetric are the remaining rates, then test with the additional test cases 48, 45, 42, 39, 30, 27, 18 and 15. + +If all rates are implemented by the DUT, there will be a total of 40 tests. + +### A.3.2 Impulse noise tests + +#### A.3.2.1 Impulse noise test procedure + +The impulse noise waveform $V(t)$ (hereafter called the "test impulse") is defined as: + +$$V(t) = \begin{cases} K|t|^{-3/4} & t > 0 \\ 0 & t = 0 \\ -K|t|^{-3/4} & t < 0 \end{cases}$$ + +where $t$ is time given in units of seconds and $K$ is a constant defined numerically in Table A.2. If the pulse is realized using discrete samples of $V(t)$ , the waveform should be sampled at $t = (2n-1)\frac{T}{2}$ , + +where $T$ is the sampling period and $(1/T)$ should be at least twice the symbol rate of the system under test. The sampled peak-to-peak amplitude will vary with sampling rate. It can be calculated + +using the following formula: $V_{p-p} = 2K\left|\frac{T}{2}\right|^{-\frac{3}{4}}$ . + +**Table A.2/G.991.2 – Impulse noise peak-to-peak voltage requirement** + +| $K$ | $V_{p-p}$ of the test impulse sampled at 2 Msamples/s | +|------------------------|-------------------------------------------------------| +| $1.775 \times 10^{-6}$ | 320 mV | + +For a sampling rate of 2 Msamples/s, a minimum of 8000 samples is required with an amplitude accuracy of at least 12 bits. Figure A.4 shows the test impulse sampled at 2 Msamples/s. The injection circuit shall be identical to that described in A.3.1. + +![Figure A.4/G.991.2 – Time domain representation of the test pulse sampled at 2 Msamples/s. The graph shows Amplitude (mV) on the y-axis (from -200 to 200) versus Time (μs) on the x-axis (from -50 to 50). A sharp negative pulse is visible at 0 μs, reaching approximately -150 mV, followed by a positive overshoot reaching approximately 160 mV, and then a gradual decay towards 0 mV. The label G.991.2_FA-4 is present in the bottom right corner.](8d5d2817d93a53bb48da3a869f6aa149_img.jpg) + +Figure A.4/G.991.2 – Time domain representation of the test pulse sampled at 2 Msamples/s. The graph shows Amplitude (mV) on the y-axis (from -200 to 200) versus Time (μs) on the x-axis (from -50 to 50). A sharp negative pulse is visible at 0 μs, reaching approximately -150 mV, followed by a positive overshoot reaching approximately 160 mV, and then a gradual decay towards 0 mV. The label G.991.2\_FA-4 is present in the bottom right corner. + +**Figure A.4/G.991.2 – Time domain representation of the test pulse sampled at 2 Msamples/s** + +#### A.3.2.2 Impulse noise test performance + +A compliant unit shall pass the impulse noise test specified in Table A.3. The minimum test period shall be 10 s. Each SHSDL termination shall be tested independently, i.e., the impulse noise waveform is not injected at both terminations simultaneously. + +**Table A.3/G.991.2 – Impulse noise test criteria** + +| Test loop | Test pulse $V_{P-P}$ when sampled at 2 Msamples/s | Test pulse repetition rate | Bit error ratio upper limit | +|---------------------|---------------------------------------------------|----------------------------|-----------------------------| +| Loop C4 | 320 mV | 10 Hz | $5.0 \times 10^{-4}$ | +| Loop S, $L = 9000'$ | 320 mV | 10 Hz | $5.0 \times 10^{-4}$ | + +NOTE – The entries in this table only correctly apply to the 1544 kbit/s asymmetric case. Appropriate values for other rates and PSDs are for further study. + +### A.3.3 Power spectral density of crosstalk disturbers + +#### A.3.3.1 Simulated HDSL PSD + +The PSD of HDSL disturbers shall be expressed as: + +$$PSD_{HDSL} = K_{HDSL} \times \frac{2}{f_0} \times \left[ \frac{\sin\left(\frac{\pi f}{f_0}\right)}{\left(\frac{\pi f}{f_0}\right)} \right]^2 \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^8}, f_{3dB} = 196 \text{ kHz}, 0 \leq f < \infty$$ + +where + +$$f_0 = 392 \text{ kHz}, K_{HDSL} = \frac{5}{9} \times \frac{V_p^2}{R}, V_p = 2.70 \text{ V}, \text{ and } R = 135 \Omega$$ + +This equation gives the single-sided PSD; that is, the integral of PSD, with respect to $f$ , from 0 to infinity, gives the power in Watts. $PSD_{HDSL}$ is the PSD of a 392 ksymbols/s 2B1Q signal with random equiprobable levels, with full-band square-topped pulses and with 4th order Butterworth filtering ( $f_{3dB} = 196 \text{ kHz}$ ). + +#### A.3.3.2 Simulated T1 line PSD + +The PSD of the T1 line disturber is assumed to be the 50% duty-cycle random Alternate Mark Inversion (AMI) code at 1.544 Mbit/s. The single-sided PSD shall be expressed as: + +$$PSD_{T1} = \frac{V_p^2}{R_L} \times \frac{2}{f_0} \times \left[ \frac{\sin\left(\frac{\pi f}{f_0}\right)}{\left(\frac{\pi f}{f_0}\right)} \right]^2 \sin^2\left(\frac{\pi f}{2f_0}\right) \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^6} \times \frac{f^2}{f^2 + f_c^2}, 0 \leq f < \infty$$ + +where + +$$V_p = 3.6 \text{ V}, R_L = 100 \Omega, \text{ and } f_0 = 1.544 \text{ MHz}.$$ + +The formula assumes that transmitted pulses are passed through a low-pass shaping filter. The shaping filter is chosen as a 3rd order low-pass Butterworth filter with 3 dB point at 3.0 MHz. The filter magnitude squared transfer function is: + +$$\left| H_{shaping}(f) \right|^2 = \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^6}$$ + +The formula also models the coupling transformer as a high-pass filter with 3 dB point at 40 kHz using: + +$$\left| H_{Transformer}(f) \right|^2 = \frac{f^2}{f^2 + f_c^2}$$ + +#### A.3.3.3 Simulated ADSL downstream Frequency Division Duplex (FDD) PSD + +The ADSL Downstream FDD PSD is based on the ATU-C transmitter PSD mask for reduced NEXT defined in Figure A.2/G.992.1 [1]. The simulated PSD used for SHDSL performance testing shall be defined as this G.992.1 mask reduced by 3.5 dBm/Hz over all frequencies. + +#### A.3.3.4 Simulated ADSL upstream PSD + +The ADSL Upstream PSD is based on the ATU-R transmitter PSD mask defined in Figure A.3/G.992.1 [1]. The simulated PSD used for SHDSL performance testing shall be defined as this G.992.1 mask reduced by 3.5 dBm/Hz over all frequencies. + +#### A.3.3.5 Simulated SHDSL upstream PSD + +The SHDSL Upstream PSD masks are defined in A.4. The simulated PSD used for SHDSL performance testing shall be the worst-case ensemble summation of the nominal upstream PSDs from A.4, with PBO set to 0 dB. The nominal PSD is given by the expression *NominalPSD(f)* in A.4.1, A.4.2 and A.4.3. + +#### A.3.3.6 Simulated SHDSL downstream PSD + +The SHDSL Downstream PSD masks are defined in A.4. The simulated PSD used for SHDSL performance testing shall be the worst-case ensemble summation of the nominal downstream PSDs from A.4, with PBO set to 0 dB. The nominal PSD is given by the expression *NominalPSD(f)* in A.4.1, A.4.2 and A.4.3. + +#### A.3.3.7 Simulated DSL PSD + +The power spectral density (PSD) of basic access DSL disturbers is expressed as: + +$$PSD_{DSL-Disturber} = K_{DSL} \times \frac{2}{f_0} \times \left[ \frac{\sin\left(\frac{\pi f}{f_0}\right)}{\left(\frac{\pi f}{f_0}\right)} \right]^2 \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^4}, f_{3dB} = 80 \text{ kHz}, 0 \leq f < \infty$$ + +where + +$$f_0 = 80 \text{ kHz}, K_{DSL} = \frac{5}{9} \times \frac{V_p^2}{R}, V_p = 2.50 \text{ V}, \text{ and } R = 135 \Omega$$ + +This equation gives the single-sided PSD; that is, the integral of PSD, with respect to $f$ , from 0 to infinity, gives the power in Watts. $PSD_{DSL-Disturber}$ is the PSD of an 80 ksymbols/s 2B1Q signal with random equiprobable levels, with full-band square-topped pulses and with 2nd order Butterworth filtering ( $f_{3dB} = 80 \text{ kHz}$ ). + +#### A.3.3.8 NEXT + +The NEXT power transfer function uses the two-piece Unger model which has a slope of 14 dB/decade for frequencies greater than 20 kHz and a slope of 4 dB/decade for frequencies less than or equal to 20 kHz. This is defined as follows where $N$ is the total number of NEXT disturbers: + +$$|H_{NEXT-2-Piece}(f, N)|^2 = \begin{cases} 4.6288 \times 10^{-10} \times f^{0.4} \times N^{0.6}, & f \leq 20 \text{ kHz} \\ 2.3144 \times 10^{-14} \times f^{1.4} \times N^{0.6}, & f > 20 \text{ kHz} \end{cases}$$ + +The two-piece Unger model shall be used to model crosstalk when evaluating performance of the 1.536 or 1.544 Mbps asymmetric PSD. + +The one-piece model for NEXT power transfer function is defined as follows where $N$ is the total number of NEXT disturbers: + +$$|H_{NEXT-1-Piece}(f, N)|^2 = 0.8536 \times 10^{-14} \times f^{1.5} \times N^{0.6}$$ + +The one-piece model shall be used to model crosstalk when evaluating performance for all rates and PSDs except the 1.536 or 1.544 Mbit/s asymmetric PSD. + +The model for FEXT power transfer function is defined as follows where $N$ is the total number of FEXT disturbers: + +$$|H_{FEXT}(f, N, L, D)|^2 = |L(f)|^2 \times D \times 7.744 \times 10^{-21} \times f^2 \times N^{0.6}$$ + +where $L(f)$ is the insertion loss of the loop through which the interferer passes while the interferer and the signal under test are adjacent in the same binder, and $D$ is the length of the loop in feet. The FEXT model shall be used to model crosstalk from asymmetric interferers (specifically 1.544 Mbit/s asymmetric and ADSL). + +#### A.3.3.9 Crosstalk PSD definitions + +The following PSD definitions are to be used to generate the crosstalk interferer combinations used for performance testing in Table A.1. + +$$PSD_{Case-1} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 24, L_{C4}, 7600)|^2$$ + +$$PSD_{Case-2} = PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{NEXT-2-Piece}(f, 39)|^2 +$$ + +$$PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 39, L_{C4}, 7600)|^2$$ + +$$PSD_{Case-3} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{HDSL}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{ADSL-Up}(f) \times |H_{FEXT}(f, 24, L_{C4}, 7600)|^2$$ + +$$PSD_{Case-4} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{ADSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 24, L_{S9.0}, 9000)|^2$$ + +$$PSD_{Case-5} = PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{NEXT-2-Piece}(f, 39)|^2 +$$ + +$$PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 39, L_{S9.0}, 9000)|^2$$ + +$$PSD_{Case-6} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{HDSL}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{ADSL-Up}(f) \times |H_{FEXT}(f, 24, L_{S9.0}, 9000)|^2$$ + +$$PSD_{Case-7} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{C4}, 7600)|^2$$ + +$$PSD_{Case-8} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{NEXT-2-Piece}(f, 48)|^2 +$$ + +$$PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{S9.0}, 9000)|^2$$ + +$$PSD_{Case-9} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 24, L_{S6.3}, 6300)|^2$$ + +$$PSD_{Case-10} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 24, L_{BT1-C5.2}, 5200)|^2$$ + +$$PSD_{Case-11} = PSD_{SHDSL-2304-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-12} = PSD_{SHDSL-2304-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-13} = PSD_{SHDSL-2304-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-14} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{BT1-R5.2}, 5200)|^2$$ + +$$PSD_{Case-15} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{SHDSL-2048-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{ADSL-Up}(f) \times |H_{FEXT}(f, 24, L_{S6.8}, 6800)|^2$$ + +$$PSD_{Case-16} = PSD_{SHDSL-2048-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-17} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 24, L_{BT1-C5.6}, 5600)|^2$$ + +$$PSD_{Case-18} = PSD_{SHDSL-2048-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-19} = PSD_{SHDSL-2048-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-20} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{BT1-R5.6}, 5600)|^2$$ + +$$PSD_{Case-21} = PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{NEXT-1-Piece}(f, 39)|^2 + PSD_{SHDSL-1544-Asym-Up}(f) \times |H_{FEXT}(f, 39, L_{S7.9}, 7900)|^2$$ + +$$PSD_{Case-22} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{SHDSL-1544-Asym-Down}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + \frac{24 \times PSD_{ADSL-Up}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{FEXT}(f, 48, L_{BT1-C6.4}, 6400)|^2$$ + +$$PSD_{Case-23} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{SHDSL-1544-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{ADSL-Up}(f) \times |H_{FEXT}(f, 24, L_{BT1-C6.4}, 6400)|^2$$ + +$$PSD_{Case-24} = PSD_{SHDSL-1544-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-25} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-1544-Asym-Up}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{SHDSL-1544-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{BT1-R6.4}, 6400)|^2$$ + +$$PSD_{Case-26} = PSD_{SHDSL-1544-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-27} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-28} = PSD_{SHDSL-768-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-29} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-30} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-31} = PSD_{SHDSL-768-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-32} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-33} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-34} = PSD_{HDSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-35} = \frac{24 \times PSD_{ADSL-Down}(f) + 24 \times PSD_{HDSL}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + PSD_{ADSL-Up}(f) \times |H_{FEXT}(f, 24, L_{BT1-C10.4}, 10400)|^2$$ + +$$PSD_{Case-36} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{HDSL}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-37} = \frac{24 \times PSD_{T1}(f) + 24 \times PSD_{SHDSL-768-Asym-Up}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2 + \\ PSD_{SHDSL-768-Asym-Down}(f) \times |H_{FEXT}(f, 24, L_{BT1-R10.4}, 10400)|^2$$ + +$$PSD_{Case-38} = PSD_{ADSL-Up}(f) \times |H_{NEXT-1-Piece}(f, 39)|^2 + \\ PSD_{ADSL-Down}(f) \times |H_{FEXT}(f, 39, L_{BT1-R10.4}, 10400)|^2$$ + +$$PSD_{Case-39} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-384-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-40} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-384-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-41} = PSD_{SHDSL-384-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-42} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-384-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-43} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-384-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-44} = PSD_{SHDSL-384-Sym}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-45} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-46} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-47} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-256-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-48} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-49} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-50} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-256-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-51} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-52} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-53} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-192-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +$$PSD_{Case-54} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-55} = PSD_{DSL}(f) \times |H_{NEXT-1-Piece}(f, 49)|^2$$ + +$$PSD_{Case-56} = \frac{24 \times PSD_{DSL}(f) + 24 \times PSD_{SHDSL-192-Sym}(f)}{48} \times |H_{NEXT-1-Piece}(f, 48)|^2$$ + +## A.4 PSD masks + +For all data rates, the measured transmit PSD of each STU shall not exceed the PSD masks specified in this clause ( $PSDMASK_{SHDSL}(f)$ ), and the measured total power into 135 $\Omega$ shall fall within the range specified in this clause ( $P_{SHDSL} \pm 0.5$ dB). + +The inband PSD for $0 < f < 1.5$ MHz shall be measured with a 10 kHz resolution bandwidth. + +NOTE – Large PSD variations over narrow frequency intervals (for example near the junction of the main lobe with the noise floor) might require a smaller resolution bandwidth (RBW) to be used. A good rule of thumb is to choose RBW such that there is no more than 1 dB change in the signal PSD across the RBW. + +Support for the symmetric PSDs specified in A.4.1 shall be mandatory for all supported data rates. Support for the asymmetric PSDs specified in A.4.2 and A.4.3 shall be optional. + +### A.4.1 Symmetric PSD masks + +For all values of framed data rate available in the STU, the following set of PSD masks ( $PSDMASK_{SHDSL}(f)$ ) shall be selectable: + +$$PSDMASK_{SHDSL}(f) = \left\{ \begin{array}{l} 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_{sym}} \times \frac{\left[ \sin\left(\frac{\pi f}{N f_{sym}}\right) \right]^2}{\left(\frac{\pi f}{N f_{sym}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times 10^{\frac{MaskedOffsetdB(f)}{10}}, f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5}, f_{int} \leq f \leq 1.1 \text{ MHz} \end{array} \right\}$$ + +where $MaskedOffsetdB(f)$ is defined as: + +$$MaskedOffsetdB(f) = \begin{cases} 1 + 0.4 \times \frac{f_{3dB} - f}{f_{3dB}}, & f < f_{3dB} \\ 1, & f \geq f_{3dB} \end{cases}$$ + +$f_{int}$ is the frequency where the two functions governing $PSDMASK_{SHDSL}(f)$ intersect in the range 0 to $f_{sym}$ . PBO is the power backoff value in dB. $K_{SHDSL}$ , $Order$ , $N$ , $f_{sym}$ , $f_{3dB}$ , and $P_{SHDSL}$ are defined in Table A.4. $P_{SHDSL}$ is the range of power in the transmit PSD with 0 dB power backoff. $R$ is the payload data rate. + +**Table A.4/G.991.2 – Symmetric PSD parameters** + +| Payload data rate, $R$ (kbit/s) | $K_{SHDSL}$ | Order | $N$ | $f_{sym}$ (ksymbol/s) | $f_{3dB}$ | $P_{SHDSL}$ (dBm) | +|---------------------------------|-------------|-------|-----|-----------------------|------------------------|----------------------------------| +| $R < 1536$ | 7.86 | 6 | 1 | $(R + 8)/3$ | $1.0 \times f_{sym}/2$ | $P1(R) \leq P_{SHDSL} \leq 13.5$ | +| 1536 or 1544 | 8.32 | 6 | 1 | $(R + 8)/3$ | $0.9 \times f_{sym}/2$ | 13.5 | +| $R > 1544$ | 7.86 | 6 | 1 | $(R + 8)/3$ | $1.0 \times f_{sym}/2$ | 13.5 | + +$P1(R)$ is defined as follows: + +$$P1(R) = 0.3486 \log_2(R \times 1000 + 8000) + 6.06 \text{ dBm}$$ + +For 0 dB power backoff, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5 \text{ dB}$ . For power backoff values other than 0 dB, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5 \text{ dB}$ minus the power backoff value in dB. The measured transmit PSD into 135 $\Omega$ shall remain below $PSDMASK_{SHDSL}(f)$ . + +Figure A.5 shows the PSD masks with 0 dB power backoff for payload data rates of 256, 512, 768, 1536, 2048 and 2304 kbit/s. + +![Figure A.5/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -30) against Frequency (MHz) on the x-axis (from 0 to 1.1). Six curves are shown, representing different payload data rates: 256, 512, 768, 1536, 2048, and 2304 kbit/s. All curves start at a flat level between -35 and -40 dBm/Hz at low frequencies and then roll off sharply. The roll-off point shifts to lower frequencies as the data rate increases. The curves level off at a noise floor of approximately -105 dBm/Hz for frequencies above 0.8 MHz. A label 'G.991.2_FA-5' is in the bottom right corner.](f618f0a44c7807c81c70cf7ec2e5e717_img.jpg) + +Figure A.5/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -30) against Frequency (MHz) on the x-axis (from 0 to 1.1). Six curves are shown, representing different payload data rates: 256, 512, 768, 1536, 2048, and 2304 kbit/s. All curves start at a flat level between -35 and -40 dBm/Hz at low frequencies and then roll off sharply. The roll-off point shifts to lower frequencies as the data rate increases. The curves level off at a noise floor of approximately -105 dBm/Hz for frequencies above 0.8 MHz. A label 'G.991.2\_FA-5' is in the bottom right corner. + +**Figure A.5/G.991.2 – PSD masks for 0 dB power backoff** + +The equation for the nominal PSD measured at the terminals is: + +$$NominalPSD(f) = \left\{ \begin{aligned} & 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_{sym}} \times \frac{\left[ \sin\left(\frac{\pi f}{N f_{sym}}\right) \right]^2}{\left(\frac{\pi f}{N f_{sym}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times \frac{f^2}{f^2 + f_c^2}, f < f_{int} \\ & 0.5683 \times 10^{-4} \times f^{-1.5}, f_{int} \leq f \leq 1.1 \text{ MHz} \end{aligned} \right\}$$ + +where $f_c$ is the transformer cut-off frequency, assumed to be 5 kHz. Figure A.6 shows the nominal transmit PSDs with 13.5 dBm power for payload data rates of 256, 512, 768, 1536, 2048 and 2304 kbit/s. + +NOTE 1 – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations (see A.3.3.5 and A.3.3.6) as representative of typical implementations. + +![Figure A.6/G.991.2 – Nominal PSDs for 0 dB power backoff. The graph plots Power Spectral Density (PSD) in dBm/Hz on the y-axis (from -110 to -30) against Frequency in MHz on the x-axis (from 0 to 1.0). Six curves are shown, representing different payload data rates: 256, 512, 768, 1536, 2048, and 2304 kbit/s. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and roll off as frequency increases. The 256 kbit/s curve is the highest, followed by 512, 768, 1536, 2048, and 2304 kbit/s, which is the lowest. The curves level off at higher frequencies, with the 256 kbit/s curve remaining around -100 dBm/Hz at 1.0 MHz.](7171c98a283e7be269152129ea8e9173_img.jpg) + +Figure A.6/G.991.2 – Nominal PSDs for 0 dB power backoff. The graph plots Power Spectral Density (PSD) in dBm/Hz on the y-axis (from -110 to -30) against Frequency in MHz on the x-axis (from 0 to 1.0). Six curves are shown, representing different payload data rates: 256, 512, 768, 1536, 2048, and 2304 kbit/s. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and roll off as frequency increases. The 256 kbit/s curve is the highest, followed by 512, 768, 1536, 2048, and 2304 kbit/s, which is the lowest. The curves level off at higher frequencies, with the 256 kbit/s curve remaining around -100 dBm/Hz at 1.0 MHz. + +**Figure A.6/G.991.2 – Nominal PSDs for 0 dB power backoff** + +NOTE 2 – In this clause, $PSDMASK(f)$ and $NominalPSD(f)$ are in units of W/Hz, and $f$ is in units of Hz. + +### A.4.2 Asymmetric 1.536 or 1.544 PSD mask + +The asymmetric PSD mask set specified in A.4.2.1 and A.4.2.2 shall optionally be supported for 1.536 and 1.544 Mbit/s payload data rates (1.544 and 1.552 Mbit/s framed data rates) in North America. The PSD masks are described for the 0 dB power backoff case. For other values of power backoff, the passband PSD masks shall shift, but the out-of-band mask shall remain constant. Power and power spectral density is measured into a load impedance of 135 Ω. + +#### A.4.2.1 PSD mask for STU-C + +For 0 dB power backoff, the output power of the STU-C during data mode shall be $(16.8 \pm 0.5)$ dBm in the frequency band from 0 to 440 kHz and shall be limited by the mask of Figure A.7. Table A.5 provides the numerical values for the mask of Figure A.7. The PSD mask is created by linear interpolation of the frequency and power (dBm/Hz) entries of Table A.5. + +![Figure A.7/G.991.2 – STU-C PSD mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis from -100 to -30 and Frequency (MHz) on the x-axis from 0 to 1. The curve starts at -40 dBm/Hz at 0 MHz, dips to -46.2 dBm/Hz at 0.236 MHz, rises to -35.7 dBm/Hz at 0.28 MHz, stays flat until 0.4 MHz, then drops sharply to -68.2 dBm/Hz at 0.44 MHz, and continues to decrease to -89.2 dBm/Hz at 1 MHz. A label 'G.991.2_FA-7' is in the bottom right corner.](d155a1511db57a83e3f7f7c6172e1939_img.jpg) + +Figure A.7/G.991.2 – STU-C PSD mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis from -100 to -30 and Frequency (MHz) on the x-axis from 0 to 1. The curve starts at -40 dBm/Hz at 0 MHz, dips to -46.2 dBm/Hz at 0.236 MHz, rises to -35.7 dBm/Hz at 0.28 MHz, stays flat until 0.4 MHz, then drops sharply to -68.2 dBm/Hz at 0.44 MHz, and continues to decrease to -89.2 dBm/Hz at 1 MHz. A label 'G.991.2\_FA-7' is in the bottom right corner. + +**Figure A.7/G.991.2 – STU-C PSD mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff** + +**Table A.5/G.991.2 – STU-C PSD mask values for 1.536 or 1.544 Mbit/s with 0 dB power backoff** + +| Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | +|-----------------|------------------------|-----------------|------------------------|-----------------|------------------------| +| ≤1 | −54.2 − PBO | 280 | −35.7 − PBO | 1000 | −89.2 | +| 2 | −42.2 − PBO | 375 | −35.7 − PBO | 2000 | −99.7 | +| 12 | −39.2 − PBO | 400 | −40.2 − PBO | ≥3000 | −108 | +| 190 | −39.2 − PBO | 440 | −68.2 | | | +| 236 | −46.2 − PBO | 600 | −76.2 | | | + +The STU-C PSD mask shall be calculated by subtracting *PBO* (the Power Backoff value, in dB) from each PSD value in Table A.5 for frequencies less than or equal to 400 kHz, then by linear interpolation of the frequency and power (dBm/Hz) over all frequencies. The output power of the STU-C during data mode shall be $(16.8 - PBO \pm 0.5)$ dBm in the frequency band from 0 to 440 kHz. The power level during start-up shall be $(16.6 - PBO \pm 0.5)$ dBm. The nominal PSD (*NominalPSD(f)*) is defined as the PSD mask with *PBO* set to 1 dB. + +NOTE – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations (see A.3.3.5 and A.3.3.6) as representative of typical implementations. + +#### A.4.2.2 PSD mask for STU-R + +For 0 dB power backoff, the output power of the STU-R during data mode shall be $(16.5 \pm 0.5)$ dBm in the frequency band from 0 to 300 kHz and shall be limited by the mask of Figure A.8. Table A.6 provides the numerical values for the mask of Figure A.8. The PSD mask is created by linear interpolation of the frequency and power (dBm/Hz) entries of Table A.6. + +![Figure A.8/G.991.2 – STU-R PSD Mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -100 to -30) versus Frequency (MHz) on the x-axis (from 0 to 1). The mask starts at -54.2 dBm/Hz at 0 MHz, rises to -37.8 dBm/Hz at 0.175 MHz, stays flat until 0.276 MHz, then drops sharply to -77.6 dBm/Hz at 0.3 MHz, and continues to decrease linearly to -108 dBm/Hz at 1 MHz. The label G.991.2_FA-8 is in the bottom right corner.](08e28b34a19ebd5402953188378292ec_img.jpg) + +Figure A.8/G.991.2 – STU-R PSD Mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -100 to -30) versus Frequency (MHz) on the x-axis (from 0 to 1). The mask starts at -54.2 dBm/Hz at 0 MHz, rises to -37.8 dBm/Hz at 0.175 MHz, stays flat until 0.276 MHz, then drops sharply to -77.6 dBm/Hz at 0.3 MHz, and continues to decrease linearly to -108 dBm/Hz at 1 MHz. The label G.991.2\_FA-8 is in the bottom right corner. + +Figure A.8/G.991.2 – STU-R PSD Mask for 1.536 or 1.544 Mbit/s with 0 dB power backoff + +Table A.6/G.991.2 – STU-R PSD mask values for 1.536 or 1.544 Mbit/s with 0 dB power backoff + +| Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | +|-----------------|------------------------|-----------------|------------------------|-----------------|------------------------| +| $\leq 1$ | $-54.2 - PBO$ | 220 | $-34.4 - PBO$ | 555 | -102.6 | +| 2 | $-42.1 - PBO$ | 255 | $-34.4 - PBO$ | 800 | -105.6 | +| 10 | $-37.8 - PBO$ | 276 | $-41.1 - PBO$ | 1400 | -108 | +| 175 | $-37.8 - PBO$ | 300 | -77.6 | $\geq 2000$ | -108 | + +The STU-R PSD mask shall be calculated by subtracting *PBO* (the Power Backoff value, in dB) from each PSD value in Table A.6 for frequencies less than or equal to 276 kHz, then by linear interpolation of the frequency and power (dBm/Hz) over all frequencies. The output power of the STU-R during data mode shall be $(16.5 - PBO \pm 0.5)$ dBm in the frequency band from 0 to 300 kHz. The power level during start-up shall be $(16.3 - PBO \pm 0.5)$ dBm. The nominal PSD (*NominalPSD(f)*) is defined as the PSD mask with *PBO* set to 1 dB. + +NOTE – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations (see A.3.3.5 and A.3.3.6) as representative of typical implementations. + +### A.4.3 Asymmetric PSD masks for 768 or 776 kbit/s data rates + +The asymmetric PSD mask set specified in A.4.3.1 and A.4.3.2 shall optionally be supported for the 768 kbit/s and 776 kbit/s payload data rates (776 and 784 kbit/s framed data rates) in North America. The PSD masks are described for the 0 dB power backoff case. For other values of power backoff, the passband PSD masks shall shift, but the out-of-band mask shall remain constant. Power and power spectral density is measured into a load impedance of 135 $\Omega$ . + +#### A.4.3.1 PSD mask for STU-C + +For 0 dB power backoff, the output power of the STU-C during data mode shall be $(14.1 \pm 0.5)$ dBm in the frequency band from 0 to 600 kHz and shall be limited by the mask of Figure A.9. Table A.7 provides the numerical values for the mask of Figure A.9. The PSD mask is created by linear interpolation of the frequency and power (dBm/Hz) entries of Table A.7. + +![Figure A.9/G.991.2 – STU-C PSD mask for 768 or 776 kbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -100 to -30) versus Frequency (kHz) on the x-axis (from 0 to 1000). The mask starts at -36.5 dBm/Hz at 0 kHz, drops to -57 dBm/Hz at 105 kHz, rises to -37.5 dBm/Hz at 155 kHz, drops to -50.5 dBm/Hz at 250 kHz, rises to -39.5 dBm/Hz at 400 kHz, and then decreases linearly to -89.2 dBm/Hz at 1000 kHz.](20a3341414fc04b0b453a682746b9c31_img.jpg) + +Figure A.9/G.991.2 – STU-C PSD mask for 768 or 776 kbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -100 to -30) versus Frequency (kHz) on the x-axis (from 0 to 1000). The mask starts at -36.5 dBm/Hz at 0 kHz, drops to -57 dBm/Hz at 105 kHz, rises to -37.5 dBm/Hz at 155 kHz, drops to -50.5 dBm/Hz at 250 kHz, rises to -39.5 dBm/Hz at 400 kHz, and then decreases linearly to -89.2 dBm/Hz at 1000 kHz. + +Figure A.9/G.991.2 – STU-C PSD mask for 768 or 776 kbit/s with 0 dB power backoff + +Table A.7/G.991.2 – STU-C PSD mask values for 768 or 776 kbit/s with 0 dB power backoff + +| Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | Frequency (kHz) | Maximum power (dBm/Hz) | +|-----------------|------------------------|-----------------|------------------------|-----------------|------------------------| +| $\leq 50$ | $-36.5 - \text{PBO}$ | 135 | $-45.5 - \text{PBO}$ | 250 | $-50.5 - \text{PBO}$ | +| 80 | $-39.5 - \text{PBO}$ | 145 | $-39.5 - \text{PBO}$ | 400 | $-45.5 - \text{PBO}$ | +| 90 | $-44 - \text{PBO}$ | 150 | $-37.5 - \text{PBO}$ | 600 | $-70$ | +| 105 | $-57 - \text{PBO}$ | 155 | $-36.5 - \text{PBO}$ | 1000 | $-89.2$ | +| 110 | $-57 - \text{PBO}$ | 200 | $-39.25 - \text{PBO}$ | 2000 | $-99.7$ | +| | | 210 | $-42 - \text{PBO}$ | $\geq 3000$ | $-108$ | + +The STU-C PSD mask shall be calculated by subtracting *PBO* (the Power Backoff value, in dB) from each PSD value in Table A.7 for frequencies less than or equal to 400 kHz, then by linear interpolation of the frequency and power (dBm/Hz) over all frequencies. The output power of the STU-C during data mode shall be $(14.1 - PBO \pm 0.5)$ dBm in the frequency band from 0 to 600 kHz. The power level during start-up shall be $(13.9 - PBO \pm 0.5)$ dBm. The nominal PSD (*NominalPSD(f)*) is defined as the PSD mask with *PBO* set to 1 dB, multiplied by $f^2/(f^2 + f_c^2)$ where *f* is the frequency in Hz and *fc* is 5000 Hz, the nominal transformer cut-off frequency. + +NOTE – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations (see A.3.3.5 and A.3.3.6) as representative of typical implementations. + +#### A.4.3.2 PSD mask for STU-R + +For 0 dB power backoff, the output power of the STU-R during data mode shall be $(14.1 \pm 0.5)$ dBm in the frequency band from 0 to 300 kHz and shall be limited by the mask of Figure A.10. Table A.8 provides the equations for the mask of Figure A.10. + +![Figure A.10/G.991.2 – STU-R PSD mask for 768 or 776 kbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis from -100 to -30 and Frequency (kHz) on the x-axis from 0 to 1000. The mask starts at -36 dBm/Hz at 0 kHz, stays flat until approximately 125 kHz, then drops linearly to -90 dBm/Hz at 300 kHz, and remains flat at -90 dBm/Hz until 1000 kHz.](5c1059b19e142ca5a6d58f18f3767b97_img.jpg) + +| Frequency (kHz) | PSD (dBm/Hz) | +|-----------------|--------------| +| 0 | -36 | +| 125 | -36 | +| 300 | -90 | +| 1000 | -90 | + +Figure A.10/G.991.2 – STU-R PSD mask for 768 or 776 kbit/s with 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis from -100 to -30 and Frequency (kHz) on the x-axis from 0 to 1000. The mask starts at -36 dBm/Hz at 0 kHz, stays flat until approximately 125 kHz, then drops linearly to -90 dBm/Hz at 300 kHz, and remains flat at -90 dBm/Hz until 1000 kHz. + +Figure A.10/G.991.2 – STU-R PSD mask for 768 or 776 kbit/s with 0 dB power backoff + +**Table A.8/G.991.2 – STU-R PSD mask values for 768 or 776 kbit/s with 0 dB power backoff** + +| Frequency, $f$ (Hz) | Maximum power (dBm/Hz) | +|------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| $0 < f \leq 50\,000$ | $-36 - PBO$ | +| $50\,000 < f \leq 125\,000$ | $-36 - PBO - ((f - 50\,000)/75\,000)$ | +| $125\,000 < f \leq 130\,000$ | $-37 - PBO$ | +| $130\,000 < f \leq 307\,000$ | $-37 - PBO - 142 \log_{10}(f/130\,000)$ | +| $307\,000 < f \leq 1\,221\,000$ | $-90$ | +| $1\,221\,000 < f \leq 1\,630\,000$ | $-90$ peak, with max power in the $[f, f + 1\text{ MHz}]$ window of $(-90 - 48 \log_2(f/1\,221\,000) + 60)$ dBm | +| $f > 1\,630\,000$ | $-90$ peak, with max power in the $[f, f + 1\text{ MHz}]$ window of $-50$ dBm | + +The STU-R PSD mask shall be calculated by subtracting $PBO$ (the Power Backoff value, in dB) from each PSD value in Table A.8 for frequencies less than or equal to 307 kHz, then by evaluation of the equations for power (dBm/Hz) over all frequencies. The output power of the STU-R during data mode shall be $(14.1 - PBO \pm 0.5)$ dBm in the frequency band from 0 to 307 kHz. The power level during start-up shall be $(13.9 - PBO \pm 0.5)$ dBm. The nominal PSD ( $NominalPSD(f)$ ) is defined as the PSD mask with $PBO$ set to 1 dB, multiplied by $f^2/(f^2 + f_c^2)$ where $f$ is the frequency in Hz and $f_c$ is 5000 Hz, the nominal transformer cut-off frequency. + +NOTE – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations (see A.3.3.5 and A.3.3.6) as representative of typical implementations. + +## A.5 Region-specific functional characteristics + +### A.5.1 Data rate + +The operation of the STU in data mode at the specified information rate shall be as specified in Table A.9. + +**Table A.9/G.991.2 – Framed data mode rates** + +| Payload data rate, $R$ (kbit/s) | Modulation | Symbol rate (ksymbol/s) | $K$ (Bits per symbol) | +|----------------------------------|------------|-------------------------|-----------------------| +| $R = n \times 64 + (i) \times 8$ | 16-TCPAM | $(R + 8) \div 3$ | 3 | + +For devices supporting Annex A functionality, no additional limitation on data rates shall be placed beyond the limitations stated in clause 5 and reiterated in 7.1.1, 8.1 and 8.2. + +### A.5.2 Return loss + +For devices supporting Annex A functionality, return loss shall be specified based on the methodology of 11.3 and the limitations of Figure 11-6. The following definitions shall be applied to the quantities shown in Figure 11-6: + +$$RL_{MIN} = 12\text{ dB}$$ + +$$f_0 = 12.56\text{ kHz}$$ + +$$f_1 = 50\text{ kHz}$$ + +$$f_2 = f_{\text{sym}}/2$$ + +$$f_3 = 1.99 f_{\text{sym}}$$ + +where $f_{\text{sym}}$ is the symbol rate. + +### A.5.3 Span powering + +The capability for an STU-C to provide power over a span to an STU-R is optional. However, if this capability is provided, the STU-C shall meet the requirements of A.5.3.1. The capability for an STU-R (or an SRU) to be remotely powered over the span is optional. However, if this capability is provided, the STU-R or SRU shall meet the requirements of A.5.3.2. Segments that do not support span powering or that have it disabled may optionally provide wetting (sealing) current, as defined in A.5.3.3. + +The STU-C, STU-R and SRU shall comply with all applicable industry safety standards that are consistent with their deployment. In particular, it is highly desirable that SHDSL equipment comply with ITU-T Rec. K.50 [B4]. + +If an STU-R is deployed as CPE (i.e., it is part of a subscriber's installation), then span powering shall be disabled at the STU-C. The STU-C may optionally provide wetting current, as specified in A.5.3.3. + +When implemented, SHDSL span powering shall support DC powering of remote terminal units over single-span loop resistances from 0 to 1800 $\Omega$ . The maximum span resistance shall include the worst-case loop resistance plus the wiring inside the central office and remote site. The STU-C span power supply shall be designed as a voltage source and shall be considered a voltage-limited circuit in the application of all referenced standards. + +The span powering requirements defined herein are intended for use across a single segment from an STU-C to either an STU-R or an SRU. Application of these requirements in the STU-C to SRU case shall result in the termination of span powering voltages at the SRU. Succeeding segments may optionally support wetting current. Powering across multiple spans is not prohibited; however, the requirements are for further study. Wetting current may optionally be supported across any segment (STU-R to STU-C, STU-C to SRU, SRU to STU-R or SRU to SRU-R). + +To ensure interoperability and reliable operation, the STU-C and STU-R (or SRU) shall meet the following requirements when span powering is implemented: + +#### A.5.3.1 STU-C span powering source + +##### A.5.3.1.1 Output voltage + +The maximum potential between tip and ring shall be 200 V. The minimum potential between tip and ring shall be 160 V. + +##### A.5.3.1.2 Power + +The minimum steady-state power output capability shall be 15 W. + +##### A.5.3.1.3 Polarity + +The negative potential shall be applied to the terminal designated "ring" or "R". The potential from tip-to-ground should be zero or negative. + +##### A.5.3.1.4 Slew Rate + +The supply voltage power-up slew rate at the STU-C loop interface (rise time of $V_{\text{TEST}}$ ) shall be at least 1 V/ms but no greater than 30 V/ms when measured in the test circuit of Figure A.11 under all test conditions defined in Table A.10. + +![Figure A.11/G.991.2 – STU-C power-up slew rate test circuit. The diagram shows an 'STU-C Device Under Test' on the left connected to a 'Load test circuit' on the right. The device is represented by a voltage source labeled V_STU-C. The load circuit consists of a resistor R_TEST and a capacitor C_TEST connected in parallel. The voltage across the load is labeled V_TEST. The reference code G.991.2_FA-11 is shown in the bottom right corner.](a37adbbe12ec735a20ead2466363d07a_img.jpg) + +Figure A.11/G.991.2 – STU-C power-up slew rate test circuit. The diagram shows an 'STU-C Device Under Test' on the left connected to a 'Load test circuit' on the right. The device is represented by a voltage source labeled V\_STU-C. The load circuit consists of a resistor R\_TEST and a capacitor C\_TEST connected in parallel. The voltage across the load is labeled V\_TEST. The reference code G.991.2\_FA-11 is shown in the bottom right corner. + +**Figure A.11/G.991.2 – STU-C power-up slew rate test circuit** + +**Table A.10/G.991.2 – Test conditions for STU-C slew rate** + +| $C_{TEST}$ ( $\mu F$ ) | $R_{TEST}$ ( $\Omega$ ) | +|------------------------|-------------------------| +| 1.0 | 100 | +| 1.0 | 1800 | +| 15 | 100 | +| 15 | 1800 | + +NOTE (informative) – On a 900 $\Omega$ loop, the STU-C output voltage specification results in a maximum remote power load of 7.1 W. + +##### A.5.3.1.5 Power feeding oscillation + +The STU-C power supply should be designed to ensure that power feeding oscillation (a condition that could result in excessive noise coupling into other wire pairs in the cable) does not occur for the electrical characteristics shown for the protection circuit in Figure A.12. + +![Figure A.12/G.991.2 – Power oscillation example circuit. The diagram shows an 'STU-C' device on the left connected to an 'STU-R' device on the right via 'Tip' and 'Ring' wires. The STU-C device contains a transformer with a primary winding connected to a voltage source V_S and a capacitor. The secondary windings are connected to the Tip and Ring wires through resistors R_L. The STU-R device contains two inductors, each labeled '25', connected to the Tip and Ring wires. A 75 V breakover device is connected between the Ring wire and ground. The reference code G.991.2_FA-12 is shown in the bottom right corner.](014daefdecf9d847ca82cb5b9f50731f_img.jpg) + +Figure A.12/G.991.2 – Power oscillation example circuit. The diagram shows an 'STU-C' device on the left connected to an 'STU-R' device on the right via 'Tip' and 'Ring' wires. The STU-C device contains a transformer with a primary winding connected to a voltage source V\_S and a capacitor. The secondary windings are connected to the Tip and Ring wires through resistors R\_L. The STU-R device contains two inductors, each labeled '25', connected to the Tip and Ring wires. A 75 V breakover device is connected between the Ring wire and ground. The reference code G.991.2\_FA-12 is shown in the bottom right corner. + +NOTE (informative) – With appropriate current (to ground) restrictions, these requirements are not in conflict with the criteria of the Class 2 Voltage limits contained in [B5]. + +**Figure A.12/G.991.2 – Power oscillation example circuit** + +#### A.5.3.2 STU-R (and SRU) powering + +##### A.5.3.2.1 Input voltage + +The STU-R (or SRU) shall operate properly over the range of input voltages from 80 V to 200 V. The STU-R (or SRU) may operate with input voltages less than 80 V. + +##### A.5.3.2.2 Polarity + +An STU-R (or SRU) shall function normally independent of the polarity of the line power input voltage. Note that tip/ring reversal is indicated via the EOC by the Maintenance Status Response message (9.5.5.7.20). + +##### A.5.3.2.3 Capacitance + +The capacitance of the STU-R (or SRU) shall be less than or equal to 15 $\mu\text{F}$ . + +##### A.5.3.2.4 Load characteristic + +In order to guarantee power system stability during power-up and steady-operation, STU-R (or SRU) shall present a load characteristic which produces the following observable measurements when inserted in the test circuit shown in Figure A.13. + +While $V_{\text{LINE}}$ is ramped up from 0 V to the specified maximum voltage at the specified slew rate, the values of $V_{\text{LINE}}$ and $V_{\text{LOAD}}$ shall be observed and recorded. Set $t_0$ as the recorded time point during the power-up sequence when $V_{\text{LOAD}} = V_{\text{LINE}}/2$ . The load characteristic of the STU-R (or SRU) device under test (DUT) shall be such that for all time $t > t_0$ , $V_{\text{LOAD}} > V_{\text{LINE}}/2$ . This criteria shall be met for all test conditions defined in Table A.11. + +![Figure A.13/G.991.2 – Test circuit for STU-R turn-on load characteristic. The diagram shows a DC voltage source labeled V_LINE connected in series with a resistor labeled R_SPAN. This series combination is connected to a block labeled 'STU-R Device Under Test'. The voltage across the device is labeled V_LOAD.](df935fc9efbd024af4ba77e46bb0bb19_img.jpg) + +G.991.2\_FA-13 + +Figure A.13/G.991.2 – Test circuit for STU-R turn-on load characteristic. The diagram shows a DC voltage source labeled V\_LINE connected in series with a resistor labeled R\_SPAN. This series combination is connected to a block labeled 'STU-R Device Under Test'. The voltage across the device is labeled V\_LOAD. + +Figure A.13/G.991.2 – Test circuit for STU-R turn-on load characteristic + +Table A.11/G.991.2 – Test conditions for STU-R turn-on load characteristic + +| $V_{\text{LINE}}$ slew rate (V/ms) | $V_{\text{LINE}}$ maximum voltage | $R_{\text{SPAN}}$ ( $\Omega$ ) | +|------------------------------------|-----------------------------------|--------------------------------| +| 1.0 | 200 | 100 | +| 1.0 | 160 | 1800 | +| 30.0 | 200 | 100 | +| 30.0 | 160 | 1800 | + +The test power supply used to generate $V_{\text{LINE}}$ should have a minimum load capacity of 20 W at all output voltages up to 200 V. The test power supply should use linear voltage regulation to minimize transient output voltage effects (observed at $V_{\text{LINE}}$ ) in the presence of test load variations. + +#### A.5.3.3 Wetting current + +The STU-R (or SRU-R) shall be capable of drawing between 1.0 and 20 mA of wetting (sealing) current from the remote feeding circuit when span powering is disabled or is not supported. The maximum rate of change of the wetting current shall be no more than 20 mA per second. + +The STU-C (or SRU-C) may optionally supply power to support wetting current if span powering is disabled or is not supported. When enabled, this power source should produce a nominal $-48\text{ V}$ potential measured at ring with respect to tip. The maximum voltage of the power source (if provided) should be limited to $-56.5\text{ V}$ . The minimum voltage should be high enough to ensure a + +voltage of at least $-39\text{ V}$ at the inputs of the STU-R (or SRU-R), measured at ring with respect to tip, to guarantee that the STU-R (or SRU-R) metallic termination will turn on and allow wetting current to flow. In no case shall the wetting current source apply a potential greater than $-72\text{ V}$ between ring and tip. The potential at tip with respect to ground should be zero or negative. + +#### **A.5.3.4 Metallic termination** + +A metallic termination at the STU-R shall be provided in conjunction with the use of wetting current (A.5.3.3). The SRU-R shall meet the same requirements specified in this clause for an STU-R. + +Table A.12 and Figure A.14 give characteristics that apply to the DC metallic termination of the STU-R. The metallic termination provides a direct current path from tip to ring at the STU-R, providing a path for sealing current. By exercising the non-linear functions of the metallic termination, a network-side test system may identify the presence of a conforming STU-R on the customer side of the interface. The characteristics of the metallic termination shall not be affected by whether the STU-R is powered in any state, or unpowered. + +There are two operational states of the DC metallic termination: + +- a) the ON or conductive state; and +- b) the OFF or non-conductive state. + +##### **A.5.3.4.1 ON state** + +The application of a voltage across the metallic termination greater than $V_{AN}$ , the activate/non-activate voltage, for a duration greater than the activate time shall cause the termination to transition to the ON state. The activate/non-activate voltage shall be in the range of $30.0$ to $39.0\text{ V}$ . The activate time shall be in the range of $3.0$ to $50.0\text{ ms}$ . If a change of state is to occur, the transition shall be completed within $50\text{ ms}$ from the point where the applied voltage across the termination first exceeds $V_{AN}$ . Application of a voltage greater than $V_{AN}$ for a duration less than $3.0\text{ ms}$ shall not cause the termination to transition to the ON state. See Table A.12 and Figure A.14. + +While in the ON state, when the voltage across the termination is $15\text{ V}$ , the current shall be greater than or equal to $20\text{ mA}$ . The metallic termination shall remain in the ON state as long as the current is greater than the threshold $I_{HR}$ (see Table A.12 and Figure A.14) whose value shall be in the range of $0.1$ to $1.0\text{ mA}$ . Application of $90.0\text{ V}$ through $200$ to $4000\ \Omega$ (for a maximum duration of $2\text{ s}$ ) shall result in a current greater than $9.0\text{ mA}$ . + +##### **A.5.3.4.2 OFF state** + +The metallic termination shall transition to the OFF state if the current falls below the threshold $I_{HR}$ whose value shall be in the range of $0.1$ to $1.0\text{ mA}$ for a duration greater than the "guaranteed release" time ( $100\text{ ms}$ ) (see Table A.12 and Figure A.14). If a change of state is to occur, the transition shall be completed within $100\text{ ms}$ from the point where the current first falls below $I_{HR}$ . If the current falls below $I_{HR}$ for a duration less than $3.0\text{ ms}$ , the termination shall not transition to the OFF state. While in the OFF state, the current shall be less than $5.0\ \mu\text{A}$ whenever the voltage is less than $20.0\text{ V}$ . The current shall not exceed $1.0\text{ mA}$ while the voltage across the termination remains less than the activate voltage. + +Descriptive material can be found in Table A.12 and Figure A.14. + +##### **A.5.3.4.3 STU-R capacitance** + +While the metallic termination is OFF, the tip-to-ring capacitance of the STU-R when measured at a frequency of less than $100\text{ Hz}$ shall be $1.0\ \mu\text{F} \pm 10\%$ . + +##### A.5.3.4.4 Behaviour of the STU-R during metallic testing + +During metallic testing, the STU-R shall behave as follows: + +- when a test voltage of up to 90 V2 is applied across the loop under test, the STU-R shall present its DC metallic termination as defined in A.5.3.4, Table A.12 and Figure A.14, and not trigger any protective device that will mask this signature. The series resistance (test system + test trunk + loop + margin) can be from 200 to 4000 Ω (balanced between the two conductors); +- the STU-R may optionally limit current in excess of 25 mA (20 mA maximum sealing current + 5 mA implementation margin). + +**Table A.12/G.991.2 – Characteristics of DC metallic termination at the STU-R** + +| | | +|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| Type of operation | Normally OFF DC termination. Turned ON by application of metallic voltage. Held ON by loop current flow. Turned OFF by cessation of loop current flow. | +| Current in the ON state and at 15 V | $\geq 20$ mA | +| DC voltage drop (when ON) at 20 mA current | $\leq 15$ V | +| DC current with application of 90 V through 4000 Ω for up to 2 s. | min 9 mA (Note). See Figure A.14. | +| DC leakage current (when OFF) at 20 V | $\leq 5.0$ μA | +| Activate/non-activate voltage | $30.0$ V DC $\leq V_{AN} \leq 39.0$ V DC | +| Activate (breakover) current at $V_{AN}$ | $\leq 1.0$ mA | +| Activate time for voltage $\geq V_{AN}$ | 3 ms to 50 ms | +| Hold/release current | $0.1$ mA $\leq I_{HR} \leq 1.0$ mA | +| Release/non-release time for current $\leq I_{HR}$ | 3 ms to 100 ms | +| NOTE – This requirement is intended to ensure a termination consistent with test system operation. | | + +2 One test system in common use today applies 70 V DC plus 10 Vrms AC (84.4 V peak) to one conductor of the loop while grounding the other conductor. + +![Figure A.14/G.991.2 – Illustration of DC characteristics of the STU-R (Bilateral switch and holding current). The graph plots Current (I_L) on a logarithmic y-axis (0 to 1 A) against Voltage (E) on a linear x-axis (0 to 90 V). It shows the ON STATE, OFF STATE, and Transition region. Key parameters marked include (V_ON, I_TST), (V_TST, I_LK), I_Lmin, V_AN, I_BO, I_HR, and a curve E = 90 - 200 * I_L (90 V, 200 Ω source, 0 Ω loop). A point (54 V, 9 mA) is also indicated.](5dd117defe429c6c5620c4bb9ce20b0a_img.jpg) + +Figure A.14/G.991.2 – Illustration of DC characteristics of the STU-R (Bilateral switch and holding current). The graph plots Current (I\_L) on a logarithmic y-axis (0 to 1 A) against Voltage (E) on a linear x-axis (0 to 90 V). It shows the ON STATE, OFF STATE, and Transition region. Key parameters marked include (V\_ON, I\_TST), (V\_TST, I\_LK), I\_Lmin, V\_AN, I\_BO, I\_HR, and a curve E = 90 - 200 \* I\_L (90 V, 200 Ω source, 0 Ω loop). A point (54 V, 9 mA) is also indicated. + +**DC Characteristics (EITHER POLARITY)** + +| Parameter | Meaning | Limit | Condition | Meaning | +|------------|-------------------------------|--------------------------------------------------|-----------------------------|--------------| +| $I_{LK}$ | Leakage current | $I_{LT} \leq 5 \mu\text{A}$ | $V_{TST} = 20 \text{ V}$ | Test voltage | +| $V_{AN}$ | Activate/Non-activate voltage | $30 \text{ V} \leq V_{AN} \leq 39 \text{ V}$ | | | +| $I_{BO}$ | Break over current | $I_{BO} \leq 1.0 \text{ mA}$ | | | +| $I_{HR}$ | Hold/Release current | $0.1 \text{ mA} \leq I_{HR} \leq 1.0 \text{ mA}$ | | | +| $V_{ON}$ | ON voltage | $V_{ON} \leq 15 \text{ V}$ | $I_{TST} = 20 \text{ V mA}$ | Test current | +| $I_{Lmin}$ | Minimum ON current | 9 mA | 54 V | | + +G.991.2\_FA-14 + +**Figure A.14/G.991.2 – Illustration of DC characteristics of the STU-R (Bilateral switch and holding current)** + +### A.5.4 Longitudinal Balance + +For devices supporting Annex A functionality, longitudinal balance shall be specified based on the methodology of 11.1 and the limitations of Figure 11-2. The following definitions shall be applied to the quantities in Figure 11-2. + +$$LB_{MIN} = 40 \text{ dB}$$ + +$$f_1 = 20 \text{ kHz}$$ + +$$f_2 = f_{sym}/2$$ + +where $f_{sym}$ is the symbol rate. + +### A.5.5 Longitudinal output voltage + +For devices supporting Annex A functionality, longitudinal output voltage shall be specified based on the methodology of 11.2. The measurement frequency range shall be between 20 kHz and 450 kHz. + +### A.5.6 PMMS target margin + +If the optional line probe is selected during the G.994.1 session, the receiver shall use the negotiated target margin. If worst-case PMMS target margin is selected, then the receiver shall assume the disturbers of Table A.13 to determine if a particular rate can be supported. Reference crosstalk shall be computed as defined in A.3.3 with the FEXT components in A.3.3.9 ignored. The reference crosstalk specified in this clause may not be representative of worst-case conditions in all networks. Differences between crosstalk environments may be compensated by adjusting the target margin. + +**Table A.13/G.991.2 – Reference disturbers used during PMMS for worst-case target margin** + +| Rate (kbit/s) | PSD (direction) | Reference disturber | +|---------------|-------------------|------------------------------| +| All | Symmetric (US/DS) | 49 SHDSL | +| 768/776 | Asymmetric (US) | 49 HDSL | +| 768/776 | Asymmetric (DS) | 24 T1 + 24 HDSL | +| 1536/1544 | Asymmetric (US) | 39 SHDSL (NEXT only) | +| 1536/1544 | Asymmetric (DS) | 24 T1 + 24 SHDSL (NEXT only) | + +### A.5.7 Span powering in *M*-pair mode + +In the optional *M*-pair mode, the requirements for remote power feeding or wetting current for each of the *M* pairs shall be identical to the requirements for a single pair specified in A.5.3. + +NOTE – This implies that the powering/wetting current is provided by a potential difference between tip and ring on each of the *M* pairs. + +# Annex B + +## Regional requirements – Region 2 + +## B.1 Scope + +This annex describes those specifications that are unique to SHDSL systems operating under conditions such as those typically encountered within European networks. The clauses in this annex provide the additions and modifications to the corresponding clauses in the main body. + +## B.2 Test loops + +### B.2.1 Functional description + +The test loops in Figure B.1 are based on the existing HDSL test loops. The length of the individual loops are chosen such that the transmission characteristics of all loops are comparable. The purpose is to stress the equalizer of the SHDSL unit under test similarly over all loops when testing SHDSL at a specific bit rate. The total length of each loop is described in terms of *physical* length, and the length of the individual sections as a fixed fraction of this total. If implementation tolerances of one test loop causes its resulting *electrical* length to be out of specification, then its total physical length shall be scaled accordingly to correct this error. One test loop includes bridged taps to achieve rapid + +variations in amplitude and phase characteristics of the cable transfer function. In some access networks, these bridge taps have been implemented in the past, which stresses the SHDSL modem under test differently. + +Loop #1 is a symbolic name for a loop with zero (or near zero) length, to prove that the SHDSL transceiver under test can handle the potentially high signal levels when two transceivers are directly interconnected. + +### B.2.2 Test loop topology + +The topology of the test loops is specified in Figure B.1. The basic test cable characteristics, the transfer function of the test loops specified using these cables and the variation of input impedance of the test loops are shown in Appendix II. + +![Figure B.1/G.991.2 – Test loop topology. The diagram shows seven test loop topologies (LOOP #1 to LOOP #7) connected between an STU-R (Sender) and an STU-C (Receiver). Each loop is represented by a horizontal line with various cable segments and bridge taps, with their lengths, attenuation values, and characteristic impedances specified.](c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg) + +The diagram illustrates the test loop topologies for seven different configurations: + +- LOOP #1:** STU-R connected directly to STU-C via a 0 dB cable. +- LOOP #2:** STU-R connected to STU-C via a cable labeled L2 with characteristic impedance 120 Ω (PE04). +- LOOP #3:** STU-R connected to STU-C via four cable segments: 0.1834\*L3 (~0.25\*Y dB) with 120 Ω (PE04), 0.2866\*L3 (~0.25\*Y dB) with 106 Ω (PE06), 0.3466\*L3 (~0.25\*Y dB) with 159 Ω (PE05), and 0.1834\*L3 (~0.25\*Y dB) with 120 Ω (PE04). +- LOOP #4:** STU-R connected to STU-C via three cable segments: 0.2866\*L4 (~0.25\*Y dB) with 106 Ω (PE06), 0.3668\*L4 (~0.50\*Y dB) with 120 Ω (PE04), and 0.3466\*L4 (~0.25\*Y dB) with 159 Ω (PE05). +- LOOP #5:** STU-R connected to STU-C via three cable segments: 100 m (~0.10\*Y dB) with 73 Ω (PVC04), L5-200 m (~0.80\*Y dB) with 124 Ω (PE08), and 100 m (~0.10\*Y dB) with 73 Ω (PVC04). +- LOOP #6:** STU-R connected to STU-C via two cable segments with bridge taps: 0.2857\*L6 (~0.20\*Y dB) with 120 Ω (PE04) and 0.7143\*L6 (~0.60\*Y dB) with 120 Ω (PE04). Each segment is preceded by a bridge tap of 500 m (PE04). +- LOOP #7:** STU-R connected to STU-C via four cable segments: 300 m (PVC063) with 67 Ω, 0.3865\*(L7-350m) (~0.20\*Y dB) with 159 Ω (PE05), 0.6135\*(L7-350m) (~0.60\*Y dB) with 120 Ω (PE04), and 50 m (PVC032) with 75 Ω. + +G.991.2\_FB-1 + +Figure B.1/G.991.2 – Test loop topology. The diagram shows seven test loop topologies (LOOP #1 to LOOP #7) connected between an STU-R (Sender) and an STU-C (Receiver). Each loop is represented by a horizontal line with various cable segments and bridge taps, with their lengths, attenuation values, and characteristic impedances specified. + +NOTE 1 – The values for Y and L are to be found in Table B.1. + +NOTE 2 – Due to mismatches and bridged taps, the total attenuation of the test loops differs from the sum of the attenuation of the parts. + +NOTE 3 – The impedances are for information only. They refer to the characteristic impedances of the test cables as defined in Appendix II measured at 300 kHz. + +Figure B.1/G.991.2 – Test loop topology + +### B.2.3 Test loop length + +The length of each test loop for SHDSL transmission systems is specified in Table B.1. The specified insertion loss $Y$ at the specified test frequency measured with a $135 \Omega$ termination (*electrical* length) is mandatory. If implementation tolerances of one test loop causes that its resulting *electrical* length is out of specification, then its total *physical* length shall be scaled accordingly to adjust this error. + +The test frequency $f_T$ is chosen to be a typical mid-band frequency in the spectrum of long range SHDSL systems. The length is chosen to be a typical maximum value that can be handled correctly by the SHDSL transceiver under test. This value is bit rate dependent; the higher the payload bit rate, the lower is the insertion loss that can be handled in practice. + +**Table B.1/G.991.2 – Values of the electrical length $Y$ of the SHDSL noise test loops, when testing SHDSL at noise model A** + +| Payload bit rate [kbit/s] | $f_T$ [kHz] | $Y$ [dB] @ $f_T$ , @ $135 \Omega$ | L1 [m] | L2 [m] | L3 [m] | L4 [m] | L5 [m] | L7 [m] | $f_T$ [kHz] | $Y$ [dB] @ $f_T$ , @ $135 \Omega$ | L6 [m] | +|---------------------------|-------------|-----------------------------------|--------|--------|--------|--------|--------|--------|-------------|-----------------------------------|--------| +| 384 | 150 | 43.0 | <3 | 4106 | 5563 | 5568 | 11 064 | 4698 | 115 | 40.5 | 3165 | +| 512 | 150 | 37.0 | <3 | 3535 | 4787 | 4789 | 9387 | 3996 | 115 | 35.0 | 2646 | +| 768 | 150 | 29.0 | <3 | 2773 | 3747 | 3753 | 7153 | 3062 | 275 | 34.5 | 1904 | +| 1024 | 150 | 25.5 | <3 | 2439 | 3285 | 3291 | 6174 | 2668 | 275 | 30.0 | 1547 | +| 1280 | 150 | 22.0 | <3 | 2105 | 2829 | 2837 | 5193 | 2266 | 275 | 26.0 | 1284 | +| 1536 | 150 | 19.0 | <3 | 1820 | 2453 | 2455 | 4357 | 1900 | 250 | 21.5 | 1052 | +| 2048 (s) | 200 | 17.5 | <3 | 1558 | 2046 | 2052 | 3285 | 1550 | 250 | 18.5 | 748 | +| 2304 (s) | 200 | 15.5 | <3 | 1381 | 1815 | 1820 | 2789 | 1331 | 250 | 16.5 | 583 | +| 2048 (a) | 250 | 21.0 | <3 | 1743 | 2264 | 2272 | 3618 | 1726 | 250 | 21.0 | 1001 | +| 2304 (a) | 250 | 18.0 | <3 | 1494 | 1927 | 1937 | 2915 | 1402 | 250 | 18.0 | 702 | + +NOTE – The electrical length $Y$ (insertion loss at specified frequency $f_T$ ) is mandatory, the (estimated) physical lengths L1-L7 are informative. +(s) those electrical lengths apply to the symmetric PSD. +(a) those electrical lengths apply to the asymmetric PSD. + +**Table B.2/G.991.2 – Values of the electrical length $Y$ of the SHDSL noise test loops, when testing SHDSL at noise model B, C, or D** + +| Payload bit rate [kbit/s] | $f_T$ [kHz] | $Y$ [dB] @ $f_T$ , @ $135 \Omega$ | L1 [m] | L2 [m] | L3 [m] | L4 [m] | L5 [m] | L7 [m] | $f_T$ [kHz] | $Y$ [dB] @ $f_T$ , @ $135 \Omega$ | L6 [m] | +|---------------------------|-------------|-----------------------------------|--------|--------|--------|--------|--------|--------|-------------|-----------------------------------|--------| +| 384 | 150 | 50.0 | <3 | 4773 | 6471 | 6477 | 13 021 | 5508 | 115 | 47.5 | 3859 | +| 512 | 150 | 44.0 | <3 | 4202 | 5692 | 5698 | 11 344 | 4814 | 115 | 41.5 | 3261 | +| 768 | 150 | 35.5 | <3 | 3392 | 4592 | 4596 | 8970 | 3815 | 275 | 42.0 | 2536 | +| 1024 | 150 | 32.0 | <3 | 3058 | 4135 | 4141 | 7990 | 3403 | 275 | 38.0 | 2223 | +| 1280 | 150 | 28.5 | <3 | 2725 | 3678 | 3684 | 7011 | 3006 | 275 | 33.5 | 1816 | +| 1536 | 150 | 25.5 | <3 | 2439 | 3285 | 3291 | 6174 | 2673 | 250 | 29.0 | 1680 | +| 2048 (s) | 200 | 24.0 | <3 | 2135 | 2812 | 2820 | 4886 | 2271 | 250 | 25.5 | 1426 | +| 2304 (s) | 200 | 21.5 | <3 | 1913 | 2509 | 2518 | 4257 | 2010 | 250 | 23.0 | 1208 | + +**Table B.2/G.991.2 – Values of the electrical length Y of the SHDSL noise test loops, when testing SHDSL at noise model B, C, or D** + +| Payload bit rate [kbit/s] | $f_T$ [kHz] | Y [dB] @ $f_T$ , @135 Ω | L1 [m] | L2 [m] | L3 [m] | L4 [m] | L5 [m] | L7 [m] | $f_T$ [kHz] | Y [dB] @ $f_T$ , @135 Ω | L6 [m] | +|---------------------------|-------------|-------------------------|--------|--------|--------|--------|--------|--------|-------------|-------------------------|--------| +| 2048 (a) | 250 | 28.0 | <3 | 2323 | 3030 | 3034 | 5189 | 2389 | 250 | 28.0 | 1607 | +| 2304 (a) | 250 | 25.0 | <3 | 2075 | 2699 | 2705 | 4514 | 2102 | 250 | 25.0 | 1387 | + +NOTE – The electrical length Y (insertion loss at specified frequency $f_T$ ) is mandatory, the (estimated) physical lengths L1-L7 are informative. +(s) those electrical lengths apply to the symmetric PSD. +(a) those electrical lengths apply to the asymmetric PSD. + +## B.3 Performance testing + +The purpose of transmission performance tests is to stress SHDSL transceivers in a way that is representative to a high penetration of systems scenario in operational access networks. This high penetration approach enables operators to define deployment rules that apply to most operational situations. It means also that in individual operational cases, characterized by lower noise levels and/or insertion loss values, the SHDSL system under test may perform better than tested. + +The design impedance $R_V$ is 135 Ω. All spectra are representing single sided power spectral densities (PSD). + +### B.3.1 Test procedure + +The purpose of this clause is to provide an unambiguous specification of the test set-up, the insertion path and the way signal and noise levels are defined. The tests are focused on the noise margin, with respect to the crosstalk noise or impulse noise levels when SHDSL signals under test are attenuated by standard test-loops and interfered with standard crosstalk noise or impulse noise. This noise margin indicates what increase of crosstalk noise or impulse noise level is allowed under specific operational conditions to ensure sufficient transmission quality. + +### B.3.2 Test set-up definition + +Figure B.2 illustrates the functional description of the test set-up. It includes: + +- A bit error ratio test set (BERTS) applies a $2^{15} - 1$ pseudo-random bit sequence (PRBS) test signal to the transmitter in the direction under test at the bit rate required. The transmitter in the opposing direction shall be fed with a similar PRBS signal, although the reconstructed signal in this path need not be monitored. +- The test loops, as specified in B.2. +- An adding element to add the (common mode and differential mode) impairment noise (a mix of random, impulsive and harmonic noise), as specified in B.3.5. +- An impairment generator, as specified in B.3.5, to generate both the differential mode and common mode impairment noise, that are fed to the adding element. +- A high impedance, and well-balanced differential voltage probe (e.g., better than 60 dB across the whole band of the SHDSL system under test) connected with level detectors such as a spectrum analyser or a true RMS voltmeter. +- A high impedance, and well-balanced common mode voltage probe (e.g., better than 60 dB across the whole band of the SHDSL system under test) connected with level detectors such as a spectrum analyser or a true RMS voltmeter. + +![Functional description of the set-up of the performance tests diagram](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +The diagram illustrates the functional description of the set-up of the performance tests. At the top, two 'Application interface' blocks are shown. The left one connects to a 'Modem under test' and a 'PRBS pattern generator'. The right one connects to a 'BERTS receiver' and another 'Modem under test'. These modems are connected to a 'Test loop' consisting of a 'Test "Cable"' and an 'Adding element'. The test loop has two main lines. On the left, the 'Tx' (Transmitter) port is connected to node pairs [A1] and [B1]. On the right, the 'Rx' (Receiver) port is connected to node pairs [A2] and [B2]. Below the test loop, there are several monitoring and impairment components. An 'Impairment generator' is connected to the bottom line. A 'Differential voltage probe' is connected to the top line and leads to a 'Level detector'. A 'Voltage probe $U_1$ ' is connected to the top line and leads to a 'Level detector', which is then connected to 'GND'. A 'Voltage probe $U_2$ ' is connected to the bottom line and leads to a 'Level detector', which is also connected to 'GND'. The diagram is labeled 'G.991.2\_FB-2' at the bottom right. + +Functional description of the set-up of the performance tests diagram + +NOTE – To allow test reproducibility, the testing equipment and the Termination Units (STU-C and STU-R) should refer to an artificial earth. If the Termination Units have no earth terminal, the test should be performed while the Termination Units are placed on a metal plate (of sufficient large size) connected to earth. + +**Figure B.2/G.991.2 – Functional description of the set-up of the performance tests** + +The two-port characteristics (transfer function, impedance) of the test-loop, as specified in B.2, are defined between port TX (node pairs A1, B1) and port RX (node pair A2, B2). The consequence is that the two-port characteristics of the test "cable" in Figure B.2 must be properly adjusted to take full account of non-zero insertion loss and non-infinite shunt impedance of the adding element and impairment generator. This is to ensure that the insertion of the generated impairment signals does not appreciably load the line. + +The balance about earth, observed at port TX, at port RX, and at the tips of the voltage probe shall exhibit a value that is 10 dB greater than the transceiver under test. This is to ensure that the impairment generator and monitor function do not appreciably deteriorate the balance about earth of the transceiver under test. + +The signal flow through the test set-up is from port TX to port RX, which means that measuring upstream and downstream performance requires an interchange of transceiver position and test "cable" ends. + +The received signal level at port RX is the level, measured between node A2 and B2, when port TX as well as port RX are terminated with the SHDSL transceivers under test. The impairment generator is switched off during this measurement. + +Test Loop #1, as specified in B.2, shall always be used for calibrating and verifying the correct settings of generators G1-G7, as specified in B.3.5, when performing performance tests. + +The transmitted signal level at port TX is the level, measured between node A1 and B1, under the same conditions. + +The impairment noise shall be a mix of random, impulsive and harmonic noise, as defined in B.3.5. The level that is specified in B.3.5 is the level at port RX, measured between node A2 and B2 (and includes both differential mode and common mode impairments), while port TX as well as port RX are terminated with the design impedance $R_V$ . These impedances shall be passive when the transceiver impedance in the switched-off mode is different from this value. + +NOTE – The injected noise is intended to match the theoretical noise PSD when the transceiver under test is connected to the loop. On loop #2 and #3 for payload rates of 1024 kbit/s and below, it has been found that impedance mismatch could generate an increased noise PSD at low frequencies. One method of compensation is to modify the factor, $\Delta$ , defined in A.3.1.4, by replacing the theoretical noise, $N(f)$ , in step 3 of A.3.1.4 with the noise PSD measured when connected to the loop under test. A second method is to place a passive circuit, consisting of a resistor $R$ in parallel with a capacitor $C$ , in series with each wire of the noise generator output pair. The RC values of $R = 1.2$ Kohms and $C = 1 \mu\text{F}$ are suggested and should be adjusted for each noise generator such that the injected noise matches the theoretical noise PSD. A third method is to calibrate the noise generator waveform into the loop under test such that when connected to the loop under test, the theoretical noise waveform is present at the transceiver terminals. + +### B.3.3 Signal and noise level definitions + +The signal and noise levels are probed with a well-balanced differential voltage probe, and the differential impedance between the tips of the probe shall be higher than the shunt impedance of 100 k $\Omega$ in parallel with 10 pF. Figure B.2 shows the probe position when measuring the RX signal level at the STU-C or STU-R receiver. Measuring the TX signal level requires the connection of the tips to node pair [A1, B1]. + +The various PSDs of signals and noises specified in this Recommendation are defined at the TX or RX side of the set-up. The levels are defined when the set-up is terminated, as described above, with design impedance $R_V$ or with transceivers under test. + +Probing an rms-voltage $U_{\text{rms}}$ [V] in this set-up, over the full signal band, means a power level of $P[\text{dBm}]$ that equals: + +$$P = 10 \times \log_{10} \left( \frac{U_{\text{rms}}^2}{R_V} \times 1000 \right) [\text{dBm}]$$ + +Probing an rms-voltage $U_{\text{rms}}$ [V] in this set-up, within a small frequency band of $\Delta f$ (in Hertz), corresponds to an average spectral density level of $P[\text{dBm/Hz}]$ within that filtered band that equals: + +$$P = 10 \times \log_{10} \left( \frac{U_{\text{rms}}^2}{R_V} \times \frac{1000}{\Delta f} \right) [\text{dBm/Hz}]$$ + +The bandwidth $\Delta f$ identifies the noise bandwidth of the filter, and not the $-3$ dB bandwidth. + +#### B.3.3.1 Noise injection network + +##### B.3.3.1.1 Differential mode injection + +The noise injector for differential mode noise (which is the portion of the Adding Element shown in Figure B.2 that is used to couple differential impairments to the test cable) is a two-port network in nature, and may have additional ports connected to the impairment generator. The Norton equivalent circuit diagram is shown in Figure B.2a. The current source $I_x$ is controlled by the impairment generator. The parasitic shunt impedance $Z_{\text{inj}}$ shall have a value of $|Z_{\text{inj}}| > 4 \text{ k}\Omega$ in the frequency range from 100 Hz to 2 MHz. + +![Figure B.2a/G.991.2 – Norton equivalent circuit diagram for differential mode noise injection. The diagram shows a parallel combination of an impedance Z_inj and a current source I_x connected between two ports labeled L_x-port and R_x-port. The diagram is labeled G.991.2_FB-2A.](c7111699f84f3e2bc4016b7876f10de6_img.jpg) + +Figure B.2a/G.991.2 – Norton equivalent circuit diagram for differential mode noise injection. The diagram shows a parallel combination of an impedance Z\_inj and a current source I\_x connected between two ports labeled L\_x-port and R\_x-port. The diagram is labeled G.991.2\_FB-2A. + +**Figure B.2a/G.991.2 – Norton equivalent circuit diagram for differential mode noise injection** + +##### B.3.3.1.2 Common mode injection + +The specification of this injection network is for further study. + +#### B.3.3.2 Noise levels calibration + +##### B.3.3.2.1 Differential mode noise calibration + +The differential mode noise injection is calibrated using the configuration shown in Figure B.2b. During calibration the RX side of the noise injector is terminated by the design impedance $R_V$ ( $= 135 \Omega$ ) and the LX (Test Loop interface) side of the noise injector is terminated by an impedance $Z_{LX}$ . The noise levels given in B.3.5 specify the PSD dissipated in $R_V$ on the RX side when $Z_{LX}$ on the LX side is equal to the calibration impedance $Z_{cal}$ . The impedance $Z_{cal}$ is defined in Figure B.2c. + +![Figure B.2b/G.991.2 – Configuration for noise level calibration. The diagram shows a yellow box labeled 'Differential mode noise injection network' connected between an L_x-port and an R_x-port. The L_x-port is terminated with impedance Z_LX. The R_x-port is terminated with impedance R_V and voltage U_x. An 'Impairment generator' is connected to the bottom of the network box. The diagram is labeled G.991.2_FB-2B.](98d9a07b2cfa04ebea4e5a4b556d184a_img.jpg) + +Figure B.2b/G.991.2 – Configuration for noise level calibration. The diagram shows a yellow box labeled 'Differential mode noise injection network' connected between an L\_x-port and an R\_x-port. The L\_x-port is terminated with impedance Z\_LX. The R\_x-port is terminated with impedance R\_V and voltage U\_x. An 'Impairment generator' is connected to the bottom of the network box. The diagram is labeled G.991.2\_FB-2B. + +**Figure B.2b/G.991.2 – Configuration for noise level calibration** + +![Figure B.2c/G.991.2 – Calibration impedance Z_cal. The diagram shows a series combination of three resistors: 120 Ω, 150 Ω, and 750 Ω. Two capacitors, 47 μF and 150 μF, are connected in parallel across the 150 Ω and 750 Ω resistors respectively. The diagram is labeled G.991.2_FB-2C.](2277d0ec6e1001b063d4f06dc3842e92_img.jpg) + +Figure B.2c/G.991.2 – Calibration impedance Z\_cal. The diagram shows a series combination of three resistors: 120 Ω, 150 Ω, and 750 Ω. Two capacitors, 47 μF and 150 μF, are connected in parallel across the 150 Ω and 750 Ω resistors respectively. The diagram is labeled G.991.2\_FB-2C. + +**Figure B.2c/G.991.2 – Calibration impedance $Z_{cal}$** + +The impedance $Z_{LX}$ on the LX side of the noise injection circuit is equal to the calibration impedance $Z_{cal}$ as given in Figure B.2c. The PSD dissipated in the impedance $R_V$ shall be equal to the differential noise PSD $P_{xn}(f)$ defined in B.3.5.1. + +NOTE – This is theoretically equivalent to the following: For an arbitrary value of the impedance $Z_{LX}$ , the PSD dissipated in $R_V$ is equal to: + +$$P_{cal}(f) = G(f, Z_{LX}) P_{xn}(f)$$ + +where $G(f, Z_{LX})$ is the impedance dependent correction factor, which is specified as: + +$$G(f, Z_{LX}) = \left| \frac{\frac{1}{Z_{LX}} + \frac{1}{Z_{inj}} + \frac{1}{R_V}}{\frac{1}{Z_{cal}} + \frac{1}{Z_{inj}} + \frac{1}{R_V}} \right|^2$$ + +where $Z_{cal}$ is the calibration impedance given in Figure B.2c, $Z_{inj}$ is the Norton equivalent impedance of the noise injection circuit (see Figure B.2a), and $R_V = 135 \Omega$ is the SHDSL design impedance. + +The noise generator gain settings determined during calibration shall be used during performance testing. During performance testing the noise injection circuit will be configured as shown in Figure B.2. Because the loop impedance and the impedance of the modem under test may differ from the impedance's $Z_{LX}$ and $R_V$ used during calibration, the voltage over the RX port of the modem may differ from the voltage $U_X$ observed during calibration. + +##### B.3.3.2.2 Common mode noise calibration + +This calibration method is for further study. + +### B.3.4 Performance test procedure + +The test performance of the SHDSL transceiver shall be such that the bit error ratio (BER) on the disturbed system is less than $10^{-7}$ , while transmitting a pseudo-random bit sequence. The BER should be measured after at least $10^9$ bits have been transmitted. + +The tests are carried out with a margin which indicates what increase of noise is allowed to ensure sufficient transmission quality. Network operators may calculate their own margins for planning purposes based on a knowledge of the relationship between this standard test set and their network characteristics. + +A test sequence as specified in Table B.3 shall be concluded. The test loops referred to are specified in Figure B.1. The test loops are characterized by the insertion loss $Y$ and/or the cable length $L$ , which depend on the data rate to be transported and have to be scaled adequately. + +In Table B.3, upstream and downstream only determine the topology of the test loop. The STU-C must pass all tests 1 through 12. The STU-R must pass all tests 1 through 12. + +A test is defined as the measurement of a given BER associated with a single test path, direction, test noise, rate and margin. The ensemble of tests associated with a particular value of N in Table B.3 is defined as a test set. + +**Table B.3/G.991.2 – Test sequence for performance testing** + +| N | Test path | Direction (Note 6) | Comments | +|----|-------------|--------------------|---------------------------------------------------------------------------------------------------------------------| +| 1 | #1 (Note 1) | Upstream | $Y = 0$ dB; Test noise A (Notes 5, 7) | +| 2 | #2 | Upstream | $Y = Y1$ (Note 2); Test noise A, C and D (Notes 7, 8) | +| 3 | #3 | Upstream | $Y = Y1$ ; Test noise D (Notes 5, 7, 8) | +| 4 | #4 | Downstream | $Y = Y1$ ; Test noise A and C (Notes 5, 7, 8) | +| 5 | #5 | Upstream | $Y = Y1$ ; Test noise B (Notes 5, 7, 8) | +| 6 | #6 | Downstream | $Y = Y1$ ; Test noise A and C (Notes 5, 7, 8) | +| 7 | #7 | Downstream | $Y = Y1$ ; Test noise A, B, C and D (Notes 5, 7, 8) | +| 8 | | | Common mode rejection test (Note 4) | +| 9 | (Note 3) | (Note 3) | $Y = Y2$ ; Test noise is the noise corresponding to the test with the highest BER in test sets 1 through 7 (Note 7) | +| 10 | (Note 3) | (Note 3) | $Y = Y3$ ; No added impairment; Worst path of tests 1 to 7; $BER < 10^{-8}$ | +| 11 | #2 | Upstream | $Y = Y1$ ; Impulse test as described in B.3.5.3.7 | +| 12 | As | | Micro-interruption test as described in 12.1 | + +**Table B.3/G.991.2 – Test sequence for performance testing** + +NOTE 1 – Test Path = #1 means that the path under test shall be connected with test loop #1 as defined in Figure B.1. + +NOTE 2 – Y1 = Y dB (as specified in Table B.2 for noise models B, C and D and in Table B.1 for noise model A), Y2 = Y1 – 10 dB, Y3 = Y1 + 3 dB. + +NOTE 3 – The tests (for any data rate) are carried out on the loop that gives the highest BER (for that data rate) in test sets 1 through 7, when the test noise is increased by 6 dB. If no errors in 109 bits are recorded for all the tests in test sets 1 through 7, then loop #3 upstream is used for this test set by default. + +NOTE 4 – The measuring arrangement for this test is specified in ITU-T Rec. O.9 [B8]. + +NOTE 5 – Only tested for lowest and highest data rate in Table B.1 or Table B.2 (that the equipment supports) and for asymmetric PSDs when supported. + +NOTE 6 – Upstream means that the unit under test is connected to the STU-C end of the test loop and downstream means that the unit under test is connected to the STU-R end of the test loop. For example, test set 5 for an STU-C would connect the STU-C under test to the STU-C end of the loop as shown in Figure B.1 and apply noise model X.C.B to the STU-C end of the loop. The same test for an STU-R would connect the STU-R under test to the STU-C end of the loop as shown in Figure B.1 and apply noise model X.R.B to the STU-C end of the loop. + +NOTE 7 – The BER shall be less than 10-7 when the test noise is increased by 6 dB (this is equivalent to 6 dB of margin). + +NOTE 8 – In order to reduce the number of noise shapes used, a mandatory noise shape substitution rule is given in B.3.5.5. + +NOTE 9 – To test the *M*-pair mode, while one path is under test, the other path(s) must be connected to loop(s). The characteristics of the other loop(s) must not be worse than the ones of the path under test. Furthermore, the differential delay between the path under test and the path(s) connected to the second loop should not exceed the value of the differential delay buffer specified in 7.1.6. + +### **B.3.5 Impairment generator** + +The noise that the impairment generator injects into the test set-up is frequency dependent, is dependent on the length of the test loop and is also different for downstream performance tests and upstream performance tests. Figure B.3 illustrates this for the *alien* noise (other than the SHDSL modem under test), as described in B.3.5.4.1, for the case that the length of test loop #1 is fixed at 3 km, using the crosstalk models described in B.3.5.2. Figure B.4 illustrates this for various loop lengths for the case that the *alien* noise of model "B" is applied. These figures are restricted to alien noise only. The self noise (of SHDSL) shall be combined with this alien noise. + +![Two line graphs showing alien noise spectra for models A, B, and C at 3 km length. The left graph is for the STU-C side and the right graph is for the STU-R side. Both plots show PSD (dBm/Hz) on the y-axis from -130 to -70 and Frequency (kHz) on the x-axis from 0 to 1000. In the STU-C side graph, model A is the highest, followed by C, then B. In the STU-R side graph, model A peaks around 300 kHz and then drops, while model C is relatively flat and model B has a deep dip around 600 kHz.](a8b996bf7955a9de9fa97920af076a10_img.jpg) + +Two line graphs showing alien noise spectra for models A, B, and C at 3 km length. The left graph is for the STU-C side and the right graph is for the STU-R side. Both plots show PSD (dBm/Hz) on the y-axis from -130 to -70 and Frequency (kHz) on the x-axis from 0 to 1000. In the STU-C side graph, model A is the highest, followed by C, then B. In the STU-R side graph, model A peaks around 300 kHz and then drops, while model C is relatively flat and model B has a deep dip around 600 kHz. + +NOTE – This is the noise resulting from three of the four noise models for SHDSL in the case that the length of test loop #2 is fixed at 3 km. + +G.991.2\_FB-3 + +**Figure B.3/G.991.2 – Examples of alien noise spectra that are to be injected into the test set-up, while testing SHDSL systems** + +![Two line graphs showing alien noise spectra for model B at various lengths (1, 2, 3, and 4 km). The left graph is for the STU-C side and the right graph is for the STU-R side. Both plots show PSD (dBm/Hz) on the y-axis from -130 to -70 and Frequency (kHz) on the x-axis from 0 to 1000. The STU-C side graph shows a single curve for model B. The STU-R side graph shows four curves for lengths 1 km, 2 km, 3 km, and 4 km, where the 4 km curve is the lowest and the 1 km curve is the highest.](f1f445db94c2431cfd01f85b2ad610e2_img.jpg) + +Two line graphs showing alien noise spectra for model B at various lengths (1, 2, 3, and 4 km). The left graph is for the STU-C side and the right graph is for the STU-R side. Both plots show PSD (dBm/Hz) on the y-axis from -130 to -70 and Frequency (kHz) on the x-axis from 0 to 1000. The STU-C side graph shows a single curve for model B. The STU-R side graph shows four curves for lengths 1 km, 2 km, 3 km, and 4 km, where the 4 km curve is the lowest and the 1 km curve is the highest. + +NOTE – This is the alien noise, resulting from noise model B for SHDSL, in the case that the length of test loop #2 varies from 1 km to 4 km. This demonstrates that the test noise is length dependent, to represent the FEXT in real access network cables. + +G.991.2\_FB-4 + +**Figure B.4/G.991.2 – Examples of alien noise spectra that are to be injected into the test set-up, while testing SHDSL systems** + +The definition of the impairment noise for SHDSL performance tests is very complex and for the purposes of this Recommendation it has been broken down into smaller, more easily specified components. These separate, and uncorrelated, impairment "generators" may therefore be isolated and summed to form the impairment generator for the SHDSL system under test. The detailed specifications for the components of the noise model(s) are given in this clause, together with a brief explanation. + +#### B.3.5.1 Functional description + +Figure B.5 defines a functional diagram of the composite impairment noise. It defines a functional description of the combined impairment noise as it must be probed at the receiver input of the SHDSL transceiver under test. The probing is described in B.3.3. + +The functional diagram has the following elements: + +- The seven impairment "generators" G1 to G7 generate noise as defined in B.3.5.3.1 to B.3.5.3.7. Their noise characteristics are independent from the test loops and bit rates. +- The transfer function $H_1(f, L)$ models the length and frequency dependency of the NEXT impairment, as specified in B.3.5.3.1. The transfer function is independent of the test loops, but changes with the electrical length of the test loop. Its transfer function changes with the frequency $f$ , roughly according to $f^{0.75}$ . +- The transfer function $H_2(f, L)$ models the length and frequency dependency of the FEXT impairment, as specified in B.3.5.3.2. Its transfer function is independent of the test loops, but changes with the electrical length of the test loop. Its transfer function changes with the frequency $f$ , roughly according to $f$ times the cable transfer function. +- Switches S1-S7 determine whether or not a specific impairment generator contributes to the total impairment during a test. +- Amplifier A1 models the property to increase the level of some generators simultaneously to perform the noise margin tests. A value of $x$ dB means a frequency independent increase of the level by $x$ dB over the full band of the SHDSL system under test, from $f_L$ to $f_H$ . Unless otherwise specified, its gain is fixed at 0 dB. + +In a practical implementation of the test set-up, there is no need to give access to any of the internal signals of the diagram in Figure B.5. These functional blocks may be incorporated with the test loop and the adding element as one integrated construction. + +![Functional diagram of the composition of the impairment noise. The diagram shows seven noise generators (G1-G7) connected to switches (S1-S7) and then to summing nodes (Σ). Generators G1 and G2 are crosstalk noise generators with transfer functions H1(f, L) and H2(f, L). Generators G3, G4, G5, G6, and G7 are independent noise generators. The output of the summing node for G1, G2, and G3 is multiplied by A1. The output of A1 and the outputs of G4, G5, and G6 are summed to produce the 'Probe level' for 'Differential mode'. The output of G7 is summed with the outputs of G5 and G6 to produce the 'Probe level' for 'Common mode'.](d7996c295c6d5c251be4bce3dea03f2e_img.jpg) + +The diagram illustrates the functional composition of impairment noise for SHDSL testing. It features seven noise generators (G1-G7) and their respective transfer functions or characteristics: + +- Independent noise generators:** G3 (Background noise, Cable independent), G4 (White noise, Cable independent), G5 (Broadcast RF noise, Cable independent, Fixed powers, fixed freq), G6 (Amateur RF noise, Cable independent, Fixed power, variable freq), and G7 (Impulsive noise, Cable independent, Bursty in nature). +- Crosstalk transfer functions:** G1 (NEXT noise) with $H_1(f, L)$ and G2 (FEXT noise) with $H_2(f, L)$ . + +The generators are connected via switches (S1-S7) to summing nodes (Σ). The output of the summing node for G1, G2, and G3 is multiplied by $A_1$ . The output of $A_1$ and the outputs of G4, G5, and G6 are summed to produce the 'Probe level' for 'Differential mode'. The output of G7 is summed with the outputs of G5 and G6 to produce the 'Probe level' for 'Common mode'. + +G.991.2\_FB-5 + +Functional diagram of the composition of the impairment noise. The diagram shows seven noise generators (G1-G7) connected to switches (S1-S7) and then to summing nodes (Σ). Generators G1 and G2 are crosstalk noise generators with transfer functions H1(f, L) and H2(f, L). Generators G3, G4, G5, G6, and G7 are independent noise generators. The output of the summing node for G1, G2, and G3 is multiplied by A1. The output of A1 and the outputs of G4, G5, and G6 are summed to produce the 'Probe level' for 'Differential mode'. The output of G7 is summed with the outputs of G5 and G6 to produce the 'Probe level' for 'Common mode'. + +NOTE 1 – Generator G7 is the only one that is symbolically shown in the time domain. + +NOTE 2 – The precise definition of impulse noise margin is for further study. + +**Figure B.5/G.991.2 – Functional diagram of the composition of the impairment noise** + +This functional diagram will be used for impairment tests in downstream and upstream direction. Several scenarios have been identified to be applied to SHDSL testing. These scenarios are intended to be representative of the impairments found in metallic access networks. + +Each scenario (or noise model) results in a length-dependent and test loop-dependent PSD description of noise. Each noise model is subdivided into two parts: one to be injected at the STU-C side, and another to be injected at the STU-R side of the SHDSL modem link under test. Therefore, seven individual impairment generators G1 to G7 can represent different values for each noise model they are used in. Specifically, G1 and G2 are dependent on which unit, STU-R or STU-C, is under test. + +Generators G1-G4 represent crosstalk noise. The spectral power $P_{xn}(f)$ for crosstalk noise is characterized by the sum: + +$$P_{xn}(f) = |A_1|^2 \times \{ |H_1(f, L)|^2 \times P_{G1}(f) + |H_2(f, L)|^2 \times P_{G2}(f) + P_{G3}(f) \} + P_{G4}(f)$$ + +Each component of this sum is specified in the following clauses. Only the noise generators that are active during testing should be included during calibration. This combined impairment noise is applied to the receiver under test, at either the STU-C (for upstream) or STU-R (for downstream) ends of the test-loop. + +Generators G5 and G6 represent ingress noise. + +#### B.3.5.2 Cable crosstalk models + +The purpose of the cable crosstalk models is to model both the length and frequency dependency of crosstalk measured in real cables. These crosstalk transfer functions adjust the level of the noise generators in Figure B.5 when the electrical length of the test loops is changed. The frequency and length dependency of these functions is in accordance with observations from real cables. The specification is based on the following constants, parameters and functions: + +- Variable $f$ identifies the frequency in Hz. +- Constant $f_0$ identifies a chosen reference frequency, which was set to 1 MHz. +- Variable $L$ identifies the physical length of the actual test loop in metres. This physical length is calculated from the cable models in Appendix II from the specified electrical length. Values are summarized in Tables B.1 and B.2 for each combination of payload bit rate, noise model, and test loop. +- Constant $L_0$ identifies a chosen reference length, which was set to 1 km. +- Function $s_{T0}(f, L)$ represents the frequency and length dependent amplitude of the insertion loss of the actual test loop terminated into 135 $\Omega$ . +- Constant $K_{xn}$ identifies an empirically obtained number that scales the NEXT transfer function $H_1(f, L)$ . The resulting transfer function represents a power summed crosstalk model of the NEXT as it was observed in a test cable. Although several disturbers and wire pairs were used, this function $H_1(f, L)$ is scaled down as if it originates from a single disturber in a single wire pair. +- Constant $K_{xf}$ identifies an empirically obtained number that scales the FEXT transfer function $H_2(f, L)$ . The resulting transfer function represents a power summed crosstalk model of the FEXT as it was observed in a test cable. Although several disturbers and wire pairs were used, this function $H_2(f, L)$ is scaled down as if it originates from a single disturber in a single wire pair. + +The transfer functions in Table B.4 shall be used as crosstalk transfer functions in the impairment generator. + +**Table B.4/G.991.2 – Definition of the crosstalk transfer functions** + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $H_1(f, L) = K_{xn} \times \left( \frac{f}{f_0} \right)^{0.75} \times \sqrt{1 - s_{T0}(f, L) ^4}$ $H_2(f, L) = K_{xf} \times \left( \frac{f}{f_0} \right) \times \sqrt{\frac{L}{L_0}} \times s_{T0}(f, L) $ | +| $K_{xn} = 10^{(-50/20)} \approx 0.0032, f_0 = 1 \text{ MHz}$
$K_{xf} = 10^{(-45/20)} \approx 0.0056, L_0 = 1 \text{ km}$
$s_{T0}(f, L) = \text{test loop insertion loss}$ | + +#### B.3.5.3 Individual impairment generators + +##### B.3.5.3.1 Equivalent NEXT disturbance generator [G1.xx] + +The NEXT noise generator represents the equivalent disturbance of all impairment that is identified as crosstalk noise from a predominantly near end origin. This noise, filtered by the NEXT crosstalk coupling function of B.3.5.2, will represent the contribution of all NEXT to the composite impairment noise of the test. + +The PSD of this noise generator is one of the PSD profiles, as specified in B.3.5.4. For testing upstream and downstream performance, different PSD profiles shall be used, as specified below. + +$$\text{G1.C.\#} = \text{X.C.\#}$$ + +$$\text{G1.R.\#} = \text{X.R.\#}$$ + +The symbols in this expression, refer to the following: + +- Symbol "\#" is a placeholder for noise model "A", "B", "C" or "D". +- Symbols "X.C.\#" and "X.R.\#" refer to the crosstalk profiles, as defined in B.3.5.4. + +This PSD is not related to the cable because the cable portion is modelled separately as transfer function $H_1(f, L)$ , as specified in B.2.2. + +The noise of this noise generator shall be uncorrelated with all the other noise sources in the impairment generator, and uncorrelated with the SHDSL system under test. The noise shall be random in nature and near Gaussian distributed, as specified in B.3.5.4.2. + +##### **B.3.5.3.2 Equivalent FEXT disturbance generator [G2.xx]** + +The FEXT noise generator represents the equivalent disturbance of all impairment that is identified as crosstalk noise from a predominantly far end origin. This noise, filtered by the FEXT crosstalk coupling function of B.3.5.2, will represent the contribution of all FEXT to the composite impairment noise of the test. + +The PSD of this noise generator is one of the PSD profiles, as specified in B.3.5.4.1. For testing upstream and downstream performance, different PSD profiles shall be used, as specified below. + +$$\text{G2.C.\#} = \text{X.R.\#}$$ + +$$\text{G2.R.\#} = \text{X.C.\#}$$ + +The symbols in this expression, refer to the following: + +- Symbol "\#" is a placeholder for noise model "A", "B", "C" or "D". +- Symbols "X.C.\#" and "X.R.\#" refer to the crosstalk profiles, as defined in B.3.5.4. + +This PSD is not related to the cable because the cable portion is modelled separately as transfer function $H_2(f, L)$ , as specified in B.2.2. + +The noise of this noise generator shall be uncorrelated with all the other noise sources in the impairment generator, and uncorrelated with the SHDSL system under test. The noise shall be random in nature and near Gaussian distributed, as specified in B.3.5.4.2. + +##### **B.3.5.3.3 Background noise generator [G3]** + +The background noise generator is inactive and set to zero. + +##### **B.3.5.3.4 White noise generator [G4]** + +The white noise generator has a fixed, frequency independent value, and is set to a level between $-140$ and $-120$ dBm/Hz, into $135\ \Omega$ . The output signal of this noise generator shall be uncorrelated with all the other noise sources in the impairment generator, and uncorrelated with the SHDSL system under test. The noise shall be random in nature and near Gaussian distributed, as specified in B.3.5.4.2. + +##### **B.3.5.3.5 Broadcast RF noise generator [G5]** + +NOTE 1 – Work on a specification dealing with generic RFI testing methods is ongoing. It is expected that a future version of this Recommendation will contain a complete RFI testing specification, which will be mandatory. This clause is currently for information only. + +The broadcast RF noise generator represents the discrete-tone line interference caused by amplitude modulated broadcast transmissions in the SW, MW and LW bands, which ingress into the cable. These interference sources have more temporal stability than the amateur (ham) interference (see B.3.5.3.6) because their carriers are not suppressed. Ingress causes differential mode as well as common mode interference. + +The ingress noise signal for differential mode impairment (or common mode impairment) is a superposition of random modulated carriers (AM). The total voltage $U(t)$ of this signal is defined as: + +$$U(t) = \sum_{\mathbf{k}} U_{\mathbf{k}} \times \cos(2\pi \cdot f_{\mathbf{k}} \times t + \varphi_{\mathbf{k}}) \times (1 + m \times \alpha_{\mathbf{k}}(t))$$ + +The individual components of this ingress noise signal $U(t)$ are defined as follows: + +- $U_{\mathbf{k}}$ – The voltage $U_{\mathbf{k}}$ of each individual carrier should be as specified in Table B.5 as power level $P$ (dBm) into a resistive load $R$ , equal to the design impedance $R_V = 135 \Omega$ . Note that spectrum analysers will detect levels that are slightly higher than the values specified in Table B.5 when their resolution bandwidths are set to 10 kHz or more, since they will detect the modulation power as well. +- $f_{\mathbf{k}}$ – The frequency $f_{\mathbf{k}}$ of each individual carrier should be as specified in Table B.5. The frequency values in Table B.5 do not represent actual broadcast frequencies but are chosen such that they cover the frequency range that is relevant for SHDSL modems. Note that the harmonic relation between the carriers in Table B.5 is minimal. +- $\varphi_{\mathbf{k}}$ – The phase offset $\varphi_{\mathbf{k}}$ of each individual carrier shall have a random value that is uncorrelated with the phase offset of every other carrier in the ingress noise signal. +- $m$ – The modulation depth $m$ of each individually modulated carrier shall be $m = 0.32$ , to enable a modulation index of at least 80 % during the peak levels of the modulation signal $m \times \alpha_{\mathbf{k}}(t)$ . +- $\alpha_{\mathbf{k}}(t)$ – The normalized modulation noise $\alpha_{\mathbf{k}}(t)$ of each individually modulated carrier shall be random in nature, shall be Gaussian distributed in nature, shall have an rms value of $\alpha_{\text{rms}} = 1$ , shall have a crest factor of 2.5 or more, and shall be uncorrelated with the modulation noise of each other modulated carrier in the ingress noise signal. +- $\Delta b$ – The modulation width $\Delta b$ of each modulated carrier shall be at least $2 \times 5$ kHz. This is equivalent to creating $\alpha_{\mathbf{k}}(t)$ from white noise, filtered by a low-pass filter with a cut-off frequency at $\Delta b/2 = 5$ kHz. This modulation width covers the full modulation band used by AM broadcast stations. + +NOTE 2 – The precise specification of the spectral shape requirements of the modulation signal is for further study. + +**Table B.5/G.991.2 – Average minimum RFI noise power versus frequency** + +| | | | | | | | | | | | +|------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|------| +| frequency (kHz) | 153 | 207 | 270 | 531 | 603 | 711 | 801 | 909 | 981 | 1296 | +| power (dBm) | –70 | –44 | –70 | –70 | –49 | –70 | –70 | –44 | –70 | –49 | + +##### B.3.5.3.6 Amateur RF noise generator [G6] + +The amateur radio noise generator is identical to the broadcast RF noise generator with different frequency and power values. These values are for further study. + +##### B.3.5.3.7 Impulse noise generator [G7] + +A test with this noise generator is required to prove the burst noise immunity of the SHDSL transceiver. This immunity shall be demonstrated on short and long loops and noise to model crosstalk and RFI. + +#### B.3.5.4 Profiles of the individual impairment generators + +Crosstalk noise represents all impairment that originates from systems connected to adjacent wire pairs that are bundled in the same cable. Their wires are coupled to the wires of the xDSL system under test, causing this spectrum of crosstalk noise to vary with the electrical length of the test loop. + +To simplify matters, the definition of crosstalk noise has been broken down into smaller, more easily specified components. The two generators G1 and G2 represent the "equivalent disturbance". Their noise level originate from a mixture of many disturbers in a real scenario, as if all disturbers are collocated at the ends of the test loops. + +This equivalent disturbance, filtered by the NEXT and FEXT coupling functions, will represent the crosstalk noise that is to be injected in the test set-up. This approach has isolated their definition from the NEXT and FEXT coupling functions of the cable. The noise generated by these two equivalent disturbers is specified in this clause in the frequency domain as well as in the time domain. + +The frequency domain characteristics of each generator G1 and G2 is defined by a spectral profile, so each noise model has its own pair of spectral profiles. + +- The profiles X.C.# in this clause describe the total equivalent disturbance of a technology mix that is virtually colocated at the STU-C end of the test loop. This noise is represented by equivalent disturbance generator G1, when stressing upstream signals, and by equivalent disturbance generator G2 when stressing downstream signals. +- The profiles X.R.# in this clause describe the total equivalent disturbance of a technology mix that is virtually colocated at the STU-R end of the test loop. This noise is represented by equivalent disturbance generator G2, when stressing upstream signals, and by equivalent disturbance generator G1 when stressing downstream signals. + +Note that the PSD levels of equivalent disturbance generator G1 and G2 are interchanged when changing from upstream testing to downstream testing. + +##### B.3.5.4.1 Frequency domain profiles for SHDSL + +This subclause specifies the PSD profiles X.R.# and X.C.# that apply for the equivalent disturbers G1 and G2 when testing SHDSL systems. In this nomenclature, "#" is used as a placeholder for noise model "A", "B" , "C" and "D". + +Four noise models have been defined for SHDSL: + +- **Type "A" models** are intended to represent a high penetration scenario where the SHDSL system under test is placed in a distribution cable (up to hundreds of wire pairs) that is filled with many other (potentially incompatible) transmission systems. +- **Type "B" models** are intended to represent a medium penetration scenario where the SHDSL system under test is placed in a distribution cable (up to tens of wire pairs) that is filled with many other (potentially incompatible) transmission systems. +- **Type "C" models** are intended to represent a legacy scenario that accounts for systems such as ISDN-PRI (HDB3), in addition to the medium penetration scenario of model "B". +- **Type "D" models** are intended as reference scenario to demonstrate the difference between a cable filled with SHDSL only, or filled with a mixture of SHDSL techniques. + +The PSD profiles for each noise model are build up by a weighed sum of two individually defined profiles: self and alien crosstalk profiles. + +$$X.C.\# = (XS.C.\# \blacklozenge XA.C.\#)$$ + +$$X.R.\# = (XS.R.\# \blacklozenge XA.R.\#)$$ + +The symbols in this expression refer to the following: + +- Symbols "# " is used as a placeholder for noise model "A", "B", "C" or "D". +- Symbols "XS.C.#" and "XS.R.#" refer to the self crosstalk profiles, as defined in B.3.5.4.1.1. +- Symbol "XA.C.#" and "XA.R.#" refer to the alien crosstalk profiles, as defined in B.3.5.4.1.2. +- Symbol " $\blacklozenge$ " refers to the crosstalk sum of two PSDs, defined as $P_X = (P_{XS}^{K_n} + P_{XA}^{K_n})^{1/K_n}$ where $P$ denotes the PSDs in W/Hz, and $K_n = 1/0.6$ . + +These profiles shall be met for all frequencies between 1 kHz to 1 MHz. + +###### B.3.5.4.1.1 Self crosstalk profiles + +The noise profiles XS.C.# and XS.R.#, representing the equivalent disturbance of self crosstalk, are specific to the PSD parameters of the SHDSL system under test, defined by the specific payload, symmetry and power-back-off features. For compliance with the requirements of this Recommendation, the appropriate nominal PSD from B.4 shall be used. + +For testing SHDSL, four noise models for self crosstalk have been defined. The STU-R and STU-C profiles are specified in Table B.6. + +In this nomenclature, "# " is a placeholder for model "A", "B", "C" or "D". "SHDSL.dn" is the signal spectrum that SHDSL transmits in downstream direction, and "SHDSL.up" in upstream direction. + +**Table B.6/G.991.2 – Definition of the self crosstalk for SHDSL testing** + +| | Model A (XS.#.A) | Model B (XS.#.B) | Model C (XS.#.C) | Model D (XS.#.D) | +|---------------------------------------------------------------|----------------------|---------------------|---------------------|----------------------| +| XS.C#: | "SHDSL.dn" + 11.7 dB | "SHDSL.dn" + 7.1 dB | "SHDSL.dn" + 7.1 dB | "SHDSL.dn" + 10.1 dB | +| XS.R#: | "SHDSL.up" + 11.7 dB | "SHDSL.up" + 7.1 dB | "SHDSL.up" + 7.1 dB | "SHDSL.up" + 10.1 dB | +| NOTE – The different noise models use different Gain factors. | | | | | + +###### B.3.5.4.1.2 Alien crosstalk profiles + +The noise profiles XA.C.# and XA.R.#, representing the equivalent disturbance of alien crosstalk, are implementation specific for the SHDSL system under test. For testing SHDSL, four noise models for alien crosstalk have been defined. The STU-C profiles are specified in Table B.7 and the STU-R profiles in Table B.8. Each PSD profile originates from a mix of disturbers. The alien noise in model D is made inactive, to achieve one pure self crosstalk scenario. + +**Table B.7/G.991.2 – Break frequencies of the "XA.C.#" PSD profiles that specify the equivalent disturbance spectra of alien disturbers** + +| XA.C.A
[Hz] | 135 Ω
[dBm/Hz] | XA.C.B
[Hz] | 135 Ω
[dBm/Hz] | XA.C.C
[Hz] | 135 Ω
[dBm/Hz] | XA.C.D
[Hz] | 135 Ω
[dBm/Hz] | +|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------| +| 1 | -20.0 | 1 | -25.7 | 1 | -25.7 | | | +| 15 k | -20.0 | 15 k | -25.7 | 15 k | -25.7 | | | +| 30 k | -21.5 | 30 k | -27.4 | 30 k | -27.4 | ALL | -∞ | +| 67 k | -27.0 | 45 k | -30.3 | 45 k | -30.3 | | | +| 125 k | -27.0 | 70 k | -36.3 | 70 k | -36.3 | | | +| 138 k | -25.7 | 127 k | -36.3 | 127 k | -36.3 | | | +| 400 k | -26.1 | 138 k | -32.1 | 138 k | -32.1 | | | +| 1104 k | -26.1 | 400 k | -32.5 | 400 k | -32.5 | | | +| 2.5 M | -66.2 | 550 k | -32.5 | 550 k | -32.5 | | | +| 4.55 M | -96.5 | 610 k | -34.8 | 610 k | -34.8 | | | +| 30 M | -96.5 | 700 k | -35.4 | 700 k | -35.3 | | | +| | | 1104 k | -35.4 | 1104 k | -35.3 | | | +| | | 4.55 M | -03.0 | 1.85 M | -58.5 | | | +| | | 30 M | -103.0 | 22.4 M | -103.0 | | | +| | | | | 30 M | -103.0 | | | + +NOTE – The PSD profiles are constructed with straight lines between these break frequencies, when plotted against a *logarithmic* frequency scale and a *linear* dBm scale. The levels are defined with a 135 Ω resistive load. + +**Table B.8/G.991.2 – Break frequencies of the "XA.R.#" PSD profiles that specify the equivalent disturbance spectra of alien disturbers** + +| XA.R.A
[Hz] | 135 Ω
[dBm/Hz] | XA.R.B
[Hz] | 135 Ω
[dBm/Hz] | XA.R.C
[Hz] | 135 Ω
[dBm/Hz] | XA.R.D
[Hz] | 135 Ω
[dBm/Hz] | +|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------| +| 1 | -20.0 | 1 | -25.7 | 1 | -25.7 | | | +| 15 k | -20.0 | 15 k | -25.7 | 15 k | -25.7 | | | +| 60 k | -25.2 | 30 k | -26.8 | 30 k | -26.8 | ALL | -∞ | +| 276 k | -25.8 | 67 k | -31.2 | 67 k | -31.2 | | | +| 500 k | -51.9 | 142 k | -31.2 | 142 k | -31.2 | | | +| 570 k | -69.5 | 156 k | -32.7 | 156 k | -32.7 | | | +| 600 k | -69.9 | 276 k | -33.2 | 276 k | -33.2 | | | +| 650 k | -62.4 | 400 k | -46.0 | 335 k | -42.0 | | | +| 763 k | -62.4 | 500 k | -57.9 | 450 k | -47.9 | | | +| 1.0 M | -71.5 | 570 k | -75.7 | 750 k | -45.4 | | | +| 2.75 M | -96.5 | 600 k | -76.0 | 1040 k | -45.5 | | | +| 30 M | -96.5 | 650 k | -68.3 | 2.46 M | -63.6 | | | +| | | 763 k | -68.3 | 23.44 M | -103.0 | | | + +**Table B.8/G.991.2 – Break frequencies of the "XA.R.#" PSD profiles that specify the equivalent disturbance spectra of alien disturbers** + +| XA.R.A
[Hz] | 135 Ω
[dBm/Hz] | XA.R.B
[Hz] | 135 Ω
[dBm/Hz] | XA.R.C
[Hz] | 135 Ω
[dBm/Hz] | XA.R.D
[Hz] | 135 Ω
[dBm/Hz] | +|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------|------------------------|---------------------------| +| | | 1.0 M | -77.5 | 30 M | -103.0 | | | +| | | 2.8 M | -103.0 | | | | | +| | | 30 M | -103.0 | | | | | + +NOTE – The PSD profiles are constructed with straight lines between these break frequencies, when plotted against a *logarithmic* frequency scale and a *linear* dBm scale. The levels are defined with a 135 Ω resistive load. + +##### B.3.5.4.2 Time domain profiles of generators G1-G4 + +The noise, as specified in the frequency domain in B.3.5.3.1 to B.3.5.3.4, shall be random in nature and near Gaussian distributed. This means that the amplitude distribution function of the combined impairment noise injected at the adding element shall lie between the two boundaries as illustrated in Figure B.6, where the non-shaded area is the allowed region. The boundaries of the mask are specified in Table B.9. + +It is expected that noise generators will generate signals that are approximately Gaussian. Therefore, the upper bound of Figure B.6 is lost. PDFs of signals generated by noise generators are expected to be well below the upper bound allowed by the PDF mask shown in Table B.9. + +The amplitude distribution function $F(a)$ of noise $u(t)$ is the fraction of the time that the absolute value of $u(t)$ exceeds the value " $a$ ". From this definition, it can be concluded that $F(0) = 1$ and that $F(a)$ monotonically decreases up to the point where " $a$ " equals the peak value of the signal. From there on, $F(a)$ vanishes: + +$$F(a) = 0, \text{ for } a \geq |u_{peak}|$$ + +The boundaries on the amplitude distribution ensure that the noise is characterized by peak values that are occasionally significantly higher than the rms-value of that noise (up to 5 times the rms-value). + +![Figure B.6/G.991.2 – Mask for the amplitude distribution function. The graph shows the probability of noise amplitude being greater than 'a' on a logarithmic y-axis (from 10^0 to 10^-8) against the normalized amplitude 'a/sigma' on the x-axis (from 0 to 7). Two curves are shown: an upper boundary labeled F_upper and a lower boundary labeled F_lower. The area between the curves is shaded with vertical lines. The F_lower curve drops to zero at a/sigma = 5. The F_upper curve is constant at 10^-2 for a/sigma > 5. The label G.991.2_FB-6 is in the bottom right corner.](bf75873135451beba5183f06879a4839_img.jpg) + +Figure B.6/G.991.2 – Mask for the amplitude distribution function. The graph shows the probability of noise amplitude being greater than 'a' on a logarithmic y-axis (from 10^0 to 10^-8) against the normalized amplitude 'a/sigma' on the x-axis (from 0 to 7). Two curves are shown: an upper boundary labeled F\_upper and a lower boundary labeled F\_lower. The area between the curves is shaded with vertical lines. The F\_lower curve drops to zero at a/sigma = 5. The F\_upper curve is constant at 10^-2 for a/sigma > 5. The label G.991.2\_FB-6 is in the bottom right corner. + +Figure B.6/G.991.2 – Mask for the amplitude distribution function + +Table B.9/G.991.2 – Upper and lower boundaries of the amplitude distribution function of the noise + +| Boundary ( $\sigma$ = rms value of noise) | Interval | Parameter | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------|-----------------------------------------------------| +| $F_{\text{lower}}(a) = (1 - \varepsilon) \cdot \{1 - \text{erf}((a/\sigma)/\sqrt{2})\}$
$F_{\text{lower}}(a) = 0$ | $0 \leq a/\sigma < CF$
$CF \leq a/\sigma < \infty$ | Crest factor
Gaussian gap | $CF = 5$
$\varepsilon = 0.1$
$A = CF/2 = 2.5$ | +| $F_{\text{upper}}(a) = (1 + \varepsilon) \cdot \{1 - \text{erf}((a/\sigma)/\sqrt{2})\}$
$F_{\text{upper}}(a) = (1 + \varepsilon) \cdot \{1 - \text{erf}(A/\sqrt{2})\}$ | $0 \leq a/\sigma < A$
$A \leq a/\sigma < \infty$ | | | + +The meaning of the parameters in Table B.9 is as follows: + +- $CF$ denotes the minimum crest factor of the noise, that characterizes the ratio between the absolute peak value and rms value ( $CF = |u_{\text{peak}}|/u_{\text{rms}}$ ). +- $\varepsilon$ denotes the Gaussian gap that indicates how "close" near Gaussian noise approximates true Gaussian noise. +- $A$ denotes the point beyond which the upper limit is alleviated to allow the use of noise signals of practical repetition length. + +#### B.3.5.5 Mandatory noise shape substitution rule + +The strict application of the test procedure requires a different noise shape for each test although some of the noise shapes are very similar. In order to reduce the number of possible noise shapes, the following substitution rule is mandatory. It reduces the number of noise shapes from 280 to 22. + +Table B.9a tabulates the noise substitution rule. The following nomenclature is used to describe a shape: + +"Side (C or R) Rate (384 to 2304) PSDType(s for symmetric) NoiseModel (A to D)" + +Example 1: C384sA2 represents the noise shape on the STU-C side for the 384 kbit/s rate using the symmetric PSD corresponding to noise model A and loop 2. + +Example 2: C384sAX represents the noise shape on the STU-C side for the 384 kbit/s rate using the symmetric PSD corresponding to noise model A and any loop. + +Example 3: Rule 7 requires that the following noise shapes: R384sA1, R384sA2, R384sA3, R384sA4, R384sA5, R384sA6, R384sA7, R512sA1, R512sA2, R512sA3, R512sA4, R512sA5, R512sA6, R512sA7 be replaced by the single noise shape R768sA2. + +Example 4: Conducting Test Set 3 of Table B.3 for 384 kbit/s at the STU-C end. The loop and transceiver would be set up as per the test description (Loop #3 upstream set to 43 dB @ 150 kHz, which is equivalent to a length of 5563 m). The transceiver would be set to 384 kbit/s. The noise shape injected would be 'R768sC2' rather than 'C384sD3' (rule 9). + +**Table B.9a/G.991.2 – Noise shape substitution rule** + +| Rule # | This shape | Replaces those shapes (on a row by row basis) | | | | | | +|--------|------------|-----------------------------------------------|------------|------------|------------|------------|------------| +| 1 | 'C768sA2' | 'C384sAX' | 'C512sAX' | | | | | +| 2 | 'C768sC2' | 'C384sBX' | 'C512sBX' | 'C384sCX' | 'C512sCX' | | | +| 3 | 'C1536sA2' | 'C768sAX' | 'C1024sAX' | 'C1280sAX' | | | | +| 4 | 'C1536sC2' | 'C768sBX' | 'C1024sBX' | 'C1280sBX' | 'C768sCX' | 'C1024sCX' | 'C1280sCX' | +| 5 | 'C2304sA2' | 'C1536sAX' | 'C2048sAX' | 'C2304sAX' | 'C1536sAX' | | | +| 6 | 'C2304sC2' | 'C1536sBX' | 'C2048sBX' | 'C2304sBX' | 'C1536sCX' | 'C2048sCX' | 'C2304sCX' | +| 7 | 'R768sA2' | 'R384sAX' | 'R512sAX' | | | | | +| 8 | 'R768sB2' | 'R384sBX' | 'R512sBX' | | | | | +| 9 | 'R768sC2' | 'R384sCX' | 'R512sCX' | 'C384sDX' | 'R384sDX' | 'C512sDX' | 'R512sDX' | +| 10 | 'R1536sA2' | 'R768sAX' | 'R1024sAX' | 'R1280sAX' | 'R1536sAX' | | | +| 11 | 'R1536sB2' | 'R768sBX' | 'R1024sBX' | 'R1280sBX' | 'R1536sBX' | | | +| 12 | 'R1536sC2' | 'R768sCX' | 'R1024sCX' | 'R1280sCX' | 'R1536sCX' | | | +| 13 | 'R2048sA2' | 'R2048sAX' | | | | | | +| 14 | 'R2048sB2' | 'R2048sBX' | | | | | | +| 15 | 'R2048sC2' | 'R2048sCX' | | | | | | +| 16 | 'R2304sA2' | 'R2304sAX' | | | | | | +| 17 | 'R2304sB2' | 'R2304sBX' | | | | | | +| 18 | 'R2304sC2' | 'R2304sCX' | | | | | | +| 19 | 'C1280sD2' | 'C768sDX' | 'R768sDX' | 'C1280sDX' | 'R1280sDX' | | | +| 20 | 'C1536sD2' | 'C1024sDX' | 'R1024sDX' | 'C1536sDX' | 'R1536sDX' | | | +| 21 | 'C2048sD2' | 'C2048sDX' | 'R2048sDX' | | | | | +| 22 | 'C2304sD2' | 'C2304sDX' | 'R2304sD' | | | | | + +#### B.3.5.6 Measurement of noise margin + +At start-up, the level and shape of crosstalk noise or impulse noise are adjusted, while their level is probed at port RX to meet the impairment level specification in B.3.4. This relative level is referred to as 0 dB. The transceiver link is subsequently activated, and the bit error ratio of the link is monitored. + +##### B.3.5.6.1 Measurement of crosstalk noise margin + +For measuring the crosstalk margin, the crosstalk noise level of the impairment generator as defined in B.3.5.4.1 shall be increased by adjusting the gain of amplifier A1 in Figure B.5, equally over the full frequency band of the SHDSL system under test, until the bit error ratio is higher than $10^{-7}$ . This BER will be achieved at an increase of noise of $x$ dB, with a small uncertainty of $\Delta$ dB. This value $x$ is defined as the crosstalk noise margin with respect to a standard noise model. The indicated noise margins shall have a tolerance of 1.25 dB due to the aggregate effect of crosstalk generator tolerance and calibrated loop simulator tolerance. The offset $\Delta$ is defined using the same procedure as in A.3.1.4. + +The noise margins shall be measured (after allowing a minimum 5-minute fine tuning period) using the test loops specified in Figure B.1 and scaled according to Tables B.1 and B.2. + +NOTE – Currently, the injected noise, for the purpose of crosstalk noise margin measurement, consists of the sum of generators G1, G2 and G4 as described in B.3.5.1. Appendix IV tabulates the values of the injected noise corresponding to 0 dB margin and a white noise generator value of $-140$ dBm/Hz. The injected noise should be measured as per B.3.3. The mandatory test cases are described in B.3.4. A mandatory noise substitution rule is described in B.3.5.5. + +##### B.3.5.6.2 Measurement of impulse noise margin + +For further study. + +## B.4 PSD masks + +For all data rates, the measured transmit PSD of each STU shall not exceed the PSD masks specified in this clause ( $PSDMASK_{SHDSL}(f)$ ), and the measured total power into $135\ \Omega$ shall fall within the range specified in this clause ( $P_{SHDSL} \pm 0.5$ dB). + +Support for the symmetric PSDs specified in B.4.1 shall be mandatory for all supported data rates. Support for the asymmetric PSDs specified in B.4.2 shall be optional. + +Table B.10 lists the supported PSDs and the associated constellation sizes. + +**Table B.10/G.991.2 – PSD and constellation size** + +| Symmetric PSDs | | Asymmetric PSDs | | | | +|----------------|----------|-----------------|----------|-------------------|----------| +| DS | US | DS | US | DS | US | +| 16-TCPAM | 16-TCPAM | 16-TCPAM | 16-TCPAM | 8-TCPAM | 16-TCPAM | +| Mandatory | | Optional | | For further study | | + +For the 16-TCPAM upstream and downstream constellations shown in Table B.10, the details of payload data rate, the associated symbol rate, and the mapping of bits per symbol are specified in Table B.11. + +**Table B.11/G.991.2 – Framed data mode rates** + +| Payload data rate, $R$ (kbit/s) | Modulation | Symbol rate (ksymbol/s) | $K$ (Bits per symbol) | +|----------------------------------|------------|-------------------------|-----------------------| +| $R = n \times 64 + (i) \times 8$ | 16-TCPAM | $(R + 8) \div 3$ | 3 | + +As specified in clause 5, the allowed rates are given by $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . For $n = 36$ , $i$ is restricted to the values of 0 or 1. + +### B.4.1 Symmetric PSD masks + +For all values of framed data rate available in the STU, the following set of PSD masks ( $PSDMASK_{SHDSL}(f)$ ) shall be selectable: + +$$PSDMASK_{SHDSL}(f) = \begin{cases} 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_{sym}} \times \frac{\left[\sin\left(\frac{\pi f}{N f_{sym}}\right)\right]^2}{\left(\frac{\pi f}{N f_{sym}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times 10^{\frac{MaskedOffsetdB(f)}{10}}, & f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5}, & f_{int} \leq f \leq 1.5 \text{ MHz} \\ -90 \text{ dBm/Hz peak with maximum power in a } [f, f+1\text{MHz}] \text{ window of } -50 \text{ dBm}, & 1.5 \text{ MHz} < f \leq 11.04 \text{ MHz} \end{cases}$$ + +where $MaskOffsetdB(f)$ is defined as: + +$$MaskOffsetdB(f) = \begin{cases} 1 + 0.4 \times \frac{f_{3dB} - f}{f_{3dB}}, & f < f_{3dB} \\ 1, & f \geq f_{3dB} \end{cases}$$ + +The inband PSD for $0 < f < 1.5$ MHz shall be measured with a 10 kHz resolution bandwidth. + +NOTE 1 – Large PSD variations over narrow frequency intervals (for example near the junction of the main lobe with the noise floor) might require a smaller resolution bandwidth (RBW) to be used. A good rule of thumb is to choose RBW such that there is no more than 1 dB change in the signal PSD across the RBW. + +$f_{int}$ is the frequency where the two functions governing $PSDMASK_{SHDSL}(f)$ intersect in the frequency range from 0 to $N f_{sym}$ . PBO is the power backoff value in dB. $K_{SHDSL}$ , $Order$ , $N$ , $f_{sym}$ , $f_{3dB}$ , and $P_{SHDSL}$ are defined in Table B.12. $P_{SHDSL}$ is the range of power in the transmit PSD with 0 dB power backoff. $R$ is the payload data rate. + +**Table B.12/G.991.2 – Symmetric PSD parameters** + +| Payload data rate, $R$ (kbit/s) | $K_{SHDSL}$ | $Order$ | $N$ | Symbol rate $f_{sym}$ (ksymbol/s) | $f_{3 dB}$ | $P_{SHDSL}$ (dBm) | +|---------------------------------|-------------|---------|-----|-----------------------------------|------------------------|----------------------------------| +| $R < 2048$ | 7.86 | 6 | 1 | $(R + 8)/3$ | $1.0 \times f_{sym}/2$ | $P1(R) \leq P_{SHDSL} \leq 13.5$ | +| $R \geq 2048$ | 9.90 | 6 | 1 | $(R + 8)/3$ | $1.0 \times f_{sym}/2$ | 14.5 | + +$P1(R)$ is defined as follows: + +$$P1(R) = 0.3486 \log_2(R \times 1000 + 8000) + 6.06 \text{ dBm}$$ + +For 0 dB power backoff, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5$ dB. For power backoff values other than 0 dB, the measured transmit power into 135 $\Omega$ + +shall fall within the range $P_{SHDSL} \pm 0.5$ dB minus the power backoff value in dB. The measured transmit PSD into $135 \Omega$ shall remain below $PSDMASK_{SHDSL}(f)$ . + +Figure B.7 shows the PSD masks with 0 dB power backoff for payload data rates of 256, 512, 768, 1536, 2048 and 2304 kbit/s. + +![Figure B.7/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis from -110 to -30 against Frequency (MHz) on the x-axis from 0 to 1.0. Six curves are shown, representing different payload data rates. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and roll off as frequency increases. The curve for the lowest data rate (256 kbit/s) has the highest PSD at high frequencies, while the curve for the highest data rate (2304 kbit/s) has the lowest PSD at high frequencies. All curves converge towards a common noise floor around -105 dBm/Hz at 1.0 MHz. The label 'G.991.2_FB-7' is in the bottom right corner.](188a44725b154c1f37855797d6a174f4_img.jpg) + +Figure B.7/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis from -110 to -30 against Frequency (MHz) on the x-axis from 0 to 1.0. Six curves are shown, representing different payload data rates. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and roll off as frequency increases. The curve for the lowest data rate (256 kbit/s) has the highest PSD at high frequencies, while the curve for the highest data rate (2304 kbit/s) has the lowest PSD at high frequencies. All curves converge towards a common noise floor around -105 dBm/Hz at 1.0 MHz. The label 'G.991.2\_FB-7' is in the bottom right corner. + +**Figure B.7/G.991.2 – PSD masks for 0 dB power backoff** + +The equation for the nominal PSD measured at the terminals is: + +$$Nominal\ PSD(f) = \begin{cases} 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_{sym}} \times \frac{\left[ \sin\left(\frac{\pi f}{N f_{sym}}\right) \right]^2}{\left(\frac{\pi f}{N f_{sym}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times \frac{f^2}{f^2 + f_c^2}, & f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5}, & f_{int} \leq f \leq 1.5\ \text{MHz} \\ -90\ \text{dBm/Hz peak with maximum power in a } [f, f+1\ \text{MHz}] \text{ window of} & \\ -50\ \text{dBm}, & 1.5\ \text{MHz} < f \leq 11.04\ \text{MHz} \end{cases}$$ + +where $f_c$ is the transformer cut-off frequency, assumed to be 5 kHz. Figure B.8 shows the nominal transmit PSDs with 13.5 dBm power for payload data rates of 256, 512, 768, 1536, 2048 and 2304 kbit/s. + +NOTE 2 – The nominal PSD is given for information only. + +![Figure B.8/G.991.2 – Nominal symmetric PSDs for 0 dB power backoff. The graph shows Power Spectral Density (PSD) in dBm/Hz on the y-axis (from -110 to -30) versus Frequency in MHz on the x-axis (from 0 to 1.0). Multiple curves are plotted, representing different symmetric PSD masks. All curves start at a peak around 0.1 MHz and then roll off as frequency increases. The curves are labeled with G.991.2_FB-8.](9c78e9637a378e4f3a1e7d4abb9bccd2_img.jpg) + +Figure B.8/G.991.2 – Nominal symmetric PSDs for 0 dB power backoff. The graph shows Power Spectral Density (PSD) in dBm/Hz on the y-axis (from -110 to -30) versus Frequency in MHz on the x-axis (from 0 to 1.0). Multiple curves are plotted, representing different symmetric PSD masks. All curves start at a peak around 0.1 MHz and then roll off as frequency increases. The curves are labeled with G.991.2\_FB-8. + +**Figure B.8/G.991.2 – Nominal symmetric PSDs for 0 dB power backoff** + +NOTE 3 – In this clause, $PSDMASK(f)$ and $NominalPSD(f)$ are in units of W/Hz unless otherwise specified, and $f$ is in units of Hz. + +### B.4.2 Asymmetric 2.048 Mbit/s and 2.304 Mbit/s PSD masks + +The asymmetric PSD mask set specified in this clause shall optionally be supported for the 2.048 Mbit/s and the 2.304 Mbit/s payload data rate. Power and power spectral density is measured into a load impedance of 135 Ω. + +For the 2.048 Mbit/s and the 2.304 Mbit/s payload data rates available in the STU, the following set of PSD masks ( $PSDMASK_{SHDSL}(f)$ ) shall be selectable: + +$$PSDMASK_{SHDSL}(f) = \begin{cases} 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_x} \times \frac{\left[ \sin\left(\frac{\pi f}{f_x}\right) \right]^2}{\left(\frac{\pi f}{f_x}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times 10^{\frac{MaskedOffsetdB(f)}{10}}, & f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5}, & f_{int} \leq f \leq 1.5 \text{ MHz} \\ -90 \text{ dBm/Hz peak with maximum power in a } [f, f+1 \text{ MHz}] \text{ window of} & \\ -50 \text{ dBm}, & 1.5 \text{ MHz} < f \leq 11.04 \text{ MHz} \end{cases}$$ + +where $MaskOffsetdB(f)$ is defined as: + +$$MaskOffsetdB(f) = \begin{cases} 1 + 0.4 \times \frac{f_{3dB} - f}{f_{3dB}}, & f < f_{3dB} \\ 1, & f \geq f_{3dB} \end{cases}$$ + +The inband PSD for $0 < f < 1.5 \text{ MHz}$ shall be measured with a 10 kHz resolution bandwidth. + +NOTE 1 – Large PSD variations over narrow frequency intervals (for example near the junction of the main lobe with the noise floor) might require a smaller resolution bandwidth (RBW) to be used. A good rule of thumb is to choose RBW such that there is no more than 1 dB change in the signal PSD across the RBW. + +$f_{int}$ is the frequency where the two functions governing $PSDMASK_{SHDSL}(f)$ intersect in the frequency range from 0 to $f_x$ . PBO is the power backoff value in dB. $K_{SHDSL}$ , *Order*, $f_x$ , $f_{3dB}$ and $P_{SHDSL}$ are defined in Table B.13. $P_{SHDSL}$ is the range of power in the transmit PSD with 0 dB power backoff. $R$ is the payload data rate. + +**Table B.13/G.991.2 – Asymmetric PSD parameters** + +| Payload data rate (kbit/s) | Transmitter | $K_{SHDSL}$ | Order | $f_x$ (Hz) | $f_{3dB}$ (Hz) | $P_{SHDSL}$ (dBm) | +|----------------------------|-------------|-------------|--------------|------------|----------------|-------------------| +| 2048 | STU-C | 16.86 | 7 | 1 370 667 | 548 267 | 16.25 | +| 2048 | STU-R | 15.66 | 7 | 685 333 | 342 667 | 16.50 | +| 2304 | STU-C | 12.48 | 7 | 1 541 333 | 578 000 | 14.75 | +| 2304 | STU-R | 11.74 | 7 | 770 667 | 385 333 | 15.25 | + +For 0 dB power backoff, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5$ dB. For power backoff values other than 0 dB, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5$ dB minus the power backoff value in dB. The measured transmit PSD into 135 $\Omega$ shall remain below $PSDMASK_{SHDSL}(f)$ . + +Figure B.9 shows the PSD masks with 0 dB power backoff for payload data rates of 2048 and 2304 kbit/s. + +![Figure B.9/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -30) against Frequency (MHz) on the x-axis (from 0 to 1.1). Four curves are shown, representing the PSD masks for 2048 and 2304 kbit/s data rates for both STU-C and STU-R transmitters. All curves start at a flat level between -35 and -40 dBm/Hz at 0 MHz and then roll off. The 2304 kbit/s curves (STU-C and STU-R) roll off more sharply than the 2048 kbit/s curves (STU-C and STU-R). The 2048 kbit/s STU-R curve remains flat until approximately 0.6 MHz before rolling off. The 2304 kbit/s STU-C curve rolls off starting around 0.3 MHz. The 2304 kbit/s STU-R curve rolls off starting around 0.4 MHz. The 2048 kbit/s STU-C curve rolls off starting around 0.5 MHz. The 2048 kbit/s STU-R curve rolls off starting around 0.6 MHz. All curves show a steep decline in PSD as frequency increases beyond their respective roll-off points.](195a7292cef79c869e13c3a9ead173f1_img.jpg) + +Figure B.9/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -30) against Frequency (MHz) on the x-axis (from 0 to 1.1). Four curves are shown, representing the PSD masks for 2048 and 2304 kbit/s data rates for both STU-C and STU-R transmitters. All curves start at a flat level between -35 and -40 dBm/Hz at 0 MHz and then roll off. The 2304 kbit/s curves (STU-C and STU-R) roll off more sharply than the 2048 kbit/s curves (STU-C and STU-R). The 2048 kbit/s STU-R curve remains flat until approximately 0.6 MHz before rolling off. The 2304 kbit/s STU-C curve rolls off starting around 0.3 MHz. The 2304 kbit/s STU-R curve rolls off starting around 0.4 MHz. The 2048 kbit/s STU-C curve rolls off starting around 0.5 MHz. The 2048 kbit/s STU-R curve rolls off starting around 0.6 MHz. All curves show a steep decline in PSD as frequency increases beyond their respective roll-off points. + +**Figure B.9/G.991.2 – PSD masks for 0 dB power backoff** + +The equation for the nominal PSD measured at the terminals is: + +$$NominalPSD(f) = \begin{cases} 10^{\frac{-PBO}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_x} \times \frac{\left[\sin\left(\frac{\pi f}{f_x}\right)\right]^2}{\left(\frac{\pi f}{f_x}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times Order}} \times \frac{f^2}{f^2 + f_c^2}, & f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5}, & f_{int} \leq f \leq 1.5 \text{ MHz} \\ -90 \text{ dBm/Hz peak with maximum power in a } [f, f+1\text{MHz}] \text{ window of} & \\ -50 \text{ dBm}, & 1.5 \text{ MHz} < f \leq 11.04 \text{ MHz} \end{cases}$$ + +where $f_c$ is the transformer cut off frequency, assumed to be 5 kHz. Figure B.10 shows the nominal transmit PSDs with 0 dB power backoff for payload data rates of 2048 and 2304 kbit/s. + +NOTE 2 – The nominal PSD is given for information only. + +![Figure B.10/G.991.2 – Nominal asymmetric PSDs for 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -110 to -30) versus Frequency (MHz) on the x-axis (from 0 to 1.1). Three curves are plotted, representing different payload data rates. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and remain relatively flat until a certain frequency, after which they drop sharply. The curve for 2048 kbit/s (top) drops around 0.4 MHz. The curve for 2304 kbit/s (middle) drops around 0.5 MHz. The curve for the lowest rate (bottom) drops around 0.6 MHz and reaches a floor of -100 dBm/Hz by 0.7 MHz.](b5b42d36b1cc063e6afb6ece6413c0a4_img.jpg) + +Figure B.10/G.991.2 – Nominal asymmetric PSDs for 0 dB power backoff. The graph shows PSD (dBm/Hz) on the y-axis (from -110 to -30) versus Frequency (MHz) on the x-axis (from 0 to 1.1). Three curves are plotted, representing different payload data rates. All curves start at a high PSD (around -35 to -40 dBm/Hz) at low frequencies and remain relatively flat until a certain frequency, after which they drop sharply. The curve for 2048 kbit/s (top) drops around 0.4 MHz. The curve for 2304 kbit/s (middle) drops around 0.5 MHz. The curve for the lowest rate (bottom) drops around 0.6 MHz and reaches a floor of -100 dBm/Hz by 0.7 MHz. + +**Figure B.10/G.991.2 – Nominal asymmetric PSDs for 0 dB power backoff** + +NOTE 3 – In this clause, $PSDMASK(f)$ and $NominalPSD(f)$ are in units of W/Hz unless otherwise specified, and $f$ is in units of Hz. + +## B.5 Region-specific functional characteristics + +### B.5.1 Data rate + +For devices supporting Annex B functionality, no additional limitation on data rates shall be placed beyond the limitations stated in clause 5 and reiterated in 7.1.1, 8.1 and 8.2. For details of the supported symbol rates and their association with PSDs, see B.4. + +### B.5.2 Return loss + +For devices supporting Annex B functionality, return loss shall be specified based on the methodology of 11.3 and the limitations of Figure 11-6. The following definitions shall be applied to the quantities shown in Figure 11-6: + +$$RL_{MIN} = 12 \text{ dB}$$ + +$$f_0 = 12.56 \text{ kHz}$$ + +$$f_1 = 50 \text{ kHz}$$ + +$$f_2 = f_{sym}/2$$ + +$$f_3 = 1.99f_{sym}$$ + +where $f_{sym}$ is the symbol rate. + +NOTE – The intention of the return loss specification is to maintain some power constraint, even under severe mismatched conditions, when SHDSL modems are connected to real cables. A minimum return loss bounds the (complex) output impedance $Z_s$ within a restricted range around the design impedance $R_v = 135 \Omega$ , and thus the maximum available power from that source. Therefore it is expected that the power dissipated into a complex load impedance $Z_L$ should never exceed the appropriate PSD masks and maximum aggregate powers for all values $Z_L$ in the range of $10 \Omega < |Z_L| < 2000 \Omega$ , as specified for $R_v = 135 \Omega$ in B.4 and Tables B.12 and B.13. The extension of the existing power constraints to the severely mismatched case is for further study. + +### B.5.3 Span powering + +#### B.5.3.1 General + +This clause deals with power feeding of the STU-R, regenerators (if required) and the provision of power to the application interface for narrow-band services under restricted conditions (life line circuit). The requirements given in this clause imply compliance to IEC 60950 [7]. + +#### B.5.3.2 Power feeding of the STU-R + +The STU-R shall be able to consume power from the remote power feeding circuit when the local power supply fails. + +NOTE – The remote feeding strategy may not be applicable for extremely long lines or lines including regenerators. In those cases specific feeding methods may be applied, which are for further study. + +The STU-R shall be able to draw up to a maximum of 10 mA as wetting current from the remote feeding circuit when the STU-R is being powered locally. When the local power fails, the maximum current drawn by the STU-R from the remote feeding circuit shall be limited to the value specified in IEC 60950 [7]. + +It is optional for the STU-C to provide wetting current. + +#### B.5.3.3 Power feeding of the interface for narrow-band services + +When simultaneous telephone service is provided by the STU-R, feeding of restricted mode power for life line service has to be provided for at least one telephone set in case of local power failure. + +NOTE – The remote feeding strategy may not be applicable for extremely long lines or lines including regenerators. In those cases, specific feeding methods may be applied which are for further study. + +#### **B.5.3.4 Feeding power from the STU-C** + +The feeding power shall be limited to the values specified by the TNV requirements in IEC 60950 [7]. + +NOTE – This means that the sum of the DC- and AC-voltage at the STU-R may not exceed 120 V. The safety standards may for extraordinary cases with long lines or regenerators allow higher power to be supplied from the STU-C. This is left for further study. It is likely that supporting long lines and/or regenerators may imply floating (not connected to ground) power feeding circuits. + +#### **B.5.3.5 Power available at the STU-R** + +The STU-R shall be able to deal with any polarity. With a minimum voltage of 45 V (see Note) at the input of the STU-R, it shall enter a full operational state. + +NOTE – This value depends on the supply voltage and is for further study. + +When remote power feeding is provided by the network, the STU-R and the side of the SRU directed towards the STU-C shall enter a high impedance state within 2 s after interruption of the remote current fed towards the STU-R or the SRU respectively. This state shall be maintained as long as the voltage on the line stays below 18 V (DC + AC peak). In this state the leakage current shall be less than 10 $\mu\text{A}$ and the capacitance shall be greater than 2 $\mu\text{F}$ . A guard time of at least 2 s between removing the remote power and applying a test voltage is necessary. + +### **B.5.4 Longitudinal balance** + +For devices supporting Annex B functionality, longitudinal balance shall be specified based on the methodology of 11.1 and the limitations of Figure 11-2. The following definitions shall be applied to the quantities in Figure 11-2. + +$$LB_{\text{MIN}} = 40 \text{ dB}$$ + +$$f_1 = 5 \text{ kHz}$$ + +$$f_2 = f_{\text{sym}}/2$$ + +where $f_{\text{sym}}$ is the symbol rate. + +### **B.5.5 Longitudinal output voltage** + +For devices supporting Annex B functionality, longitudinal output voltage shall be specified based on the methodology of 11.2. The measurement frequency range shall be between 100 Hz and 400 kHz. + +### **B.5.6 PMMS target margin** + +If the optional line probe is selected during the G.994.1 session, the receiver shall use the negotiated target margin. If worst-case PMMS target margin is selected, then the receiver shall assume the disturbers of Table B.14 to determine if a particular rate can be supported. Reference crosstalk shall be computed using the cable crosstalk models of B.3.5.2, assuming infinite loop length so that FEXT components are ignored and NEXT is independent of loop length. The reference crosstalk specified in this clause may not be representative of worst-case conditions in all networks. Differences between crosstalk environments may be compensated by adjusting the target margin. + +**Table B.14/G.991.2 – Reference disturbers used during PMMS +for worst-case target margin** + +| Rate (kbit/s) | PSD (direction) | Reference disturber | +|---------------|-------------------|---------------------------------------------------------| +| All | Symmetric (US/DS) | 49 SHDSL | +| 2048 | Asymmetric (US) | 49 SHDSL-SYM with $f_{\text{sym}} = 685\,333\text{ Hz}$ | +| 2048 | Asymmetric (DS) | 49 SHDSL-SYM with $f_{\text{sym}} = 685\,333\text{ Hz}$ | +| 2304 | Asymmetric (US) | 49 SHDSL-SYM with $f_{\text{sym}} = 770\,667\text{ Hz}$ | +| 2304 | Asymmetric (DS) | 49 SHDSL-SYM with $f_{\text{sym}} = 770\,667\text{ Hz}$ | + +### B.5.7 Span powering in *M*-pair mode + +In the optional *M*-pair mode, the requirements for remote power feeding or wetting current for each of the *M* pairs shall be identical to the requirements for a single pair specified in B.5.3. + +NOTE – This implies that the powering/wetting current is provided by a potential difference between tip and ring on each of the *M* pairs. + +# Annex C + +## Regional requirements – Region 3 + +See Annex H/G.992.1 [1] for specifications of transceivers for use in networks with existing TCM-ISDN service (as specified in Appendix III/G.961 [B1]). + +# Annex D + +## Signal regenerator operation + +In order to achieve data transmission over greater distances than are achievable over a single SHDSL segment, one or more signal regenerators (SRUs) may be employed. In the optional *M*-pair mode, *M*-pair regenerators may be used when this reach extension is required. This annex specifies operational characteristics of signal regenerators and the start-up sequence for SHDSL spans containing signal regenerators. Additional explanatory text is included in Appendix III. + +## D.1 Reference diagram + +Figure D.1 is a reference diagram of a SHDSL span containing two regenerators. Up to eight (8) regenerators per span are supported within the EOC addressing scheme (9.5.5.5), and no further limitation is intended herein. Each SRU shall consist of two parts: an SRU-R for interfacing with the STU-C (or a separate SRU-C), and an SRU-C for interfacing with the STU-R (or a separate SRU-R). An internal connection between the SRU-R and SRU-C shall provide the communication between the two parts during start-up and normal operation. An SHDSL span containing *X* regenerators shall contain *X* + 1 separated SHDSL segments, designated TR1 (STU-C to SRU1), TR2 (SRUX-C to STU-R), and RRn (SRUn-C to SRUn+1-R, where $1 \leq n \leq X-1$ ). Each segment shall follow the general principles described in 6.2, 6.3 and 7.2 for the pre-activation and activation procedures. Additional requirements specific to spans containing regenerators are described in this annex. + +![Block diagram of a SHDSL span with two signal regenerators (SRU1 and SRU2) between a STU-R and a STU-C. The diagram shows segments TR2, RR1, and TR1, and the overall SHDSL span. The diagram is labeled G.991.2_FD-1.](792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg) + +The diagram illustrates a SHDSL span between a STU-R (left) and a STU-C (right). Two signal regenerators, SRU2 and SRU1, are placed in series between them. Each SRU is divided into an SRU-C (Client) and an SRU-R (Remote) section. The segments are labeled as follows: Segment TR2 between STU-R and SRU2, Segment RR1 between SRU2 and SRU1, and Segment TR1 between SRU1 and STU-C. The entire span from STU-R to STU-C is labeled 'SHDSL span'. The diagram is identified by the label G.991.2\_FD-1 at the bottom right. + +Block diagram of a SHDSL span with two signal regenerators (SRU1 and SRU2) between a STU-R and a STU-C. The diagram shows segments TR2, RR1, and TR1, and the overall SHDSL span. The diagram is labeled G.991.2\_FD-1. + +**Figure D.1/G.991.2 – Block diagram of a SHDSL span with two signal regenerators** + +## D.2 Start-up procedures + +### D.2.1 SRU-C + +Figure D.2 shows the State Transition Diagram for SRU-C start-up and operation. The SRU-C begins in the "Idle" state and, in the case of an STU-R initiated start-up, transitions first to the "Wait for STU-C" state. For an STU-C initiated start-up, the SRU-C moves from "Idle" to the "G.994.1 Session 1" state. An SRU initiated start-up shall function identically to an STU-C initiated start-up from the perspective of the SRU-C. + +The SRU-C shall communicate "Capabilities Available" status and transfer a list of its capabilities to the SRU-R across the regenerator's internal interface upon entering the "Wait for STU-C" state. The SRU-C's capabilities list, as transferred to the SRU-R, shall be the intersection of its own capabilities, the capabilities list it received from the STU-R (or SRU-R) in its G.994.1 session, and the segment capabilities determined by the line probe, if used. + +The SRU-C shall receive mode selection information from the SRU-R in association with the "SRU-R Active" indication. In the subsequent G.994.1 session, the SRU-C shall select the same mode and parameter settings for the SHDSL session. + +The timer $T_{\text{SRUC}}$ shall be set to 4 minutes. If $T_{\text{SRUC}}$ expires before the SRU-C reaches the "Active" state, the SRU-C shall return to the "Idle" state and shall indicate link failure to the SRU-R across the internal interface. The SRU-C shall also indicate failure and return to the "Idle" state if a G.994.1 initiation is unsuccessful after 30 s. + +The "Diagnostic Mode" bit, if set in the G.994.1 Capabilities Exchange, shall cause an SRU-C to function as an STU-C if the subsequent segment fails. This implies that an internal failure indication received while in the "Wait for STU-C" state shall cause the SRU-C to select an operational mode, initiate a G.994.1 session, and transition to state "G.994.1 Session 2". + +![SRU-C state transition diagram showing states Idle, G.994.1 session 1, Wait for STU-R, Wait for STU-C, G.994.1 Session 2, and Active with various transitions.](e47d450f315d0b633906c03cc91f90ef_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Idle : G.994.1 failure + Idle --> G.994.1 session 1 : Receive internal "Link Initiation" indication, Initiate G.994.1 session + Idle --> Wait for STU-R : T_SRUC timeout + Idle --> Wait for STU-C : Internal failure Indication and not diagnostic mode + Idle --> G.994.1 Session 2 : Receive G.994.1 initiation, G.994.1 session, Capabilities exchange (Line probe), (Second G.994.1 session) (Capabilities exchange), Send MS with "Silent Period" = 1, Start T_SRUC + G.994.1 session 1 --> Idle : G.994.1 failure + G.994.1 session 1 --> Wait for STU-R : Receive MS with "Silent Period" = 1, Complete G.994.1 session, Start T_SRUC + Wait for STU-R --> Idle : G.994.1 failure + Wait for STU-R --> Wait for STU-C : T_SRUC timeout + Wait for STU-R --> G.994.1 Session 2 : Receive G.994.1 initiation, G.994.1 session, Capabilities exchange (Line probe), (Second G.994.1 session) (Capabilities exchange), Send MS with "Silent Period" = 1, Restart T_SRUC + Wait for STU-C --> Idle : G.994.1 failure + Wait for STU-C --> G.994.1 Session 2 : Internal failure Indication and Diagnostic Mode, Initiate G.994.1 Session + Wait for STU-C --> G.994.1 Session 2 : Receive G.994.1 initiation, G.994.1 session, MS with "Silent Period" = 1 + G.994.1 Session 2 --> Idle : G.994.1 failure + G.994.1 Session 2 --> Active : Complete G.994.1 session with mode selection, SHDSL Activation + G.994.1 Session 2 --> Wait for STU-R : Receive internal "SRU-R Active" indication, Initiate G.994.1 session + G.994.1 Session 2 --> Wait for STU-C : Receive capabilities exchange, Capabilities exchange (Line probe), (Second G.994.1 session) (Capabilities exchange), Send MS with "Silent Period" = 1, Restart T_SRUC + G.994.1 Session 2 --> [*] : Disconnect, failure, or retrain + +``` + +G.991.2\_FD-2 + +SRU-C state transition diagram showing states Idle, G.994.1 session 1, Wait for STU-R, Wait for STU-C, G.994.1 Session 2, and Active with various transitions. + +**Figure D.2/G.991.2 – SRU-C state transition diagram** + +### D.2.2 SRU-R + +Figure D.3 shows the State Transition Diagram for SRU-R start-up and operation. The SRU-R begins in the "Idle" state and, in the case of an STU-R initiated train, transitions first to the "G.994.1 Session 1" state. For an STU-C initiated train, the SRU-C moves from "Idle" to the "G.994.1 Session 2" state. + +The SRU-R shall communicate "Link Initiation" status to the SRU-C across the regenerator's internal interface upon entering the "Wait for STU-R" state. Upon entering the "Active" state, it shall communicate "SRU-R Active" status to the SRU-C. If plesiochronous operation (Clock Mode 1; see clause 10) is selected, the SRU-R may optionally indicate its entry into the "Active" state to the SRU-C prior to the completion of the SHDSL activation sequence. If synchronous or network referenced plesiochronous clocking is selected (Clock Modes 2, 3a or 3b; see clause 10), the SRU-R shall not indicate entry into the "Active" state until the SHDSL activation sequence has been completed. + +The SRU-R shall receive a list of capabilities from the SRU-C across the regenerator's internal interface in association with the "Capabilities Available" indication. The SRU-R's capabilities list, as indicated in the subsequent G.994.1 session, shall be the intersection of its own capabilities with the capabilities list it received from the SRU-C. + +The SRU-R shall provide mode selection information to the SRU-C in association with the "SRU-R Active" indication, based on the selections it has received in the G.994.1 session. + +The timer $T_{\text{SRUR}}$ shall be set to 4 minutes. If $T_{\text{SRUR}}$ expires before the SRU-R reaches the "Active" state, the SRU-R shall return to the "Idle" state and shall indicate link failure to the SRU-C across the internal interface. The SRU-R shall also indicate failure and return to the "Idle" state if a G.994.1 initiation is unsuccessful after 30 s. + +The "Diagnostic Mode" bit, if set in the G.994.1 Capabilities Exchange, shall cause an SRU-R to function as an STU-R if the subsequent segment fails. This implies that an internal failure indication received while in the "Wait for STU-R" state shall cause the SRU-R to initiate a G.994.1 session and transition to state "G.994.1 Session 2". + +![SRU-R state transition diagram showing states Idle, G.994.1 session 1, Wait for STU-R, G.994.1 session 2, Check for start, Wait for STU-C, and Active. Transitions include G.994.1 initiation, session completion, timeouts, and internal indications.](79403f771ea4876ca26ecee2f288b1d1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> G.994.1 session 1 : Receive G.994.1 initiation, Begin G.994.1 session, Send MS with "Silent Period" = 1 + Idle --> G.994.1 session 2 : Receive internal "Capabilities Available" indication, Initiate G.994.1 session + Idle --> [*] : T_SRUR timeout, G.994.1 failure + G.994.1 session 1 --> Idle : Internal failure Indication and not diagnostic mode + G.994.1 session 1 --> Wait for STU-R : Receive Ack(1), Complete G.994.1 session, Start T_SRUR + G.994.1 session 1 --> [*] : Disconnect, failure or retrain + Wait for STU-R --> Idle : Internal failure Indication and not diagnostic mode + Wait for STU-R --> G.994.1 session 2 : Receive internal "Capabilities Available" indication, Initiate G.994.1 session + Wait for STU-R --> [*] : Disconnect, failure or retrain + G.994.1 session 2 --> Idle : Internal failure Indication and not diagnostic mode + G.994.1 session 2 --> Check for start : Start G.994.1 session normally, Capabilities exchange (Line probe) (Second G.994.1 session) (Capabilities exchange) + G.994.1 session 2 --> [*] : Disconnect, failure or retrain + Check for start --> Idle : Internal failure Indication and not diagnostic mode + Check for start --> Wait for STU-C : Receive MS with "Silent Period" = 1, Start T_SRUR + Check for start --> Active : Receive mode selection, SHDSL activation + Check for start --> [*] : Disconnect, failure or retrain + Wait for STU-C --> Idle : Internal failure Indication and not diagnostic mode + Wait for STU-C --> Active : Receive G.994.1 initiation, Select mode, SHDSL activation + Wait for STU-C --> [*] : Disconnect, failure or retrain + Active --> Idle : Internal failure Indication and not diagnostic mode + Active --> [*] : Disconnect, failure or retrain + +``` + +SRU-R state transition diagram showing states Idle, G.994.1 session 1, Wait for STU-R, G.994.1 session 2, Check for start, Wait for STU-C, and Active. Transitions include G.994.1 initiation, session completion, timeouts, and internal indications. + +G.991.2\_FD-3 + +**Figure D.3/G.991.2 – SRU-R state transition diagram** + +### D.2.3 STU-C + +In order to support operation with regenerators, each STU-C shall support the Regenerator Silent Period (RSP) bit, as specified in ITU-T Rec. G.994.1. Second, the STU-C shall not indicate a training failure or error until it has been forced into "silent" mode for at least 5 consecutive minutes. + +### D.2.4 STU-R + +In order to support operation with regenerators, each STU-R shall support the Regenerator Silent Period (RSP) bit, as specified in ITU-T Rec. G.994.1. The STU-R shall not indicate a training failure or error until it has been forced into "silent" mode for at least 5 consecutive minutes. + +### D.2.5 Segment failures and retrains + +In the case of a segment failure or a retrain, each segment of the span shall be deactivated, with each SRU-C and each SRU-R returning to its "Idle" state. The restart may then be initiated by the SRU, the STU-R, or the STU-C. + +## D.3 Symbol rates + +For Annex A operational modes, signal regenerators may transmit at symbol rates up to and including 280 ksymbols/s in either two-wire or the optional *M*-pair mode. This corresponds, for 16-TCPAM, to maximum user data rates (not including framing overhead) of 832 kbit/s and $M \times 832$ kbit/s for two-wire and *M*-pair operation, respectively. Operation at higher symbol rates is for further study. + +For Annex B operational modes, signal regenerators may transmit at symbol rates up to and including 685.33 ksymbols/s in either two-wire or the optional *M*-pair mode. This corresponds, for 16-TCPAM, to maximum user data rates (not including framing overhead) of 2.048 Mbit/s and $M \times 2.048$ Mbit/s for two-wire and *M*-pair operation, respectively. Operation at higher symbol rates is for further study. + +In either case, each STU and SRU on a span shall select the same operational data rate. + +## D.4 PSD masks + +Any of the PSDs from Annex A or Annex B may be used for the TR1 segment (STU-C to SRU1-R), as appropriate to the given region. All other segments shall employ one of the appropriate symmetric PSDs, as described in either A.4.1 or B.4.1. The selection of PSD shall be limited by the symbol rate considerations of D.3. + +# Annex E + +## Application-specific TPS-TC framing + +This annex provides implementation details for the various types of TPS-TC framing that may be supported by SHDSL transceivers. The TPS-TC framing mode is selected during pre-activation, but the criteria for selecting a particular TPS-TC mode are application-specific and are beyond the scope of this Recommendation. + +## E.1 TPS-TC for clear channel data + +In Clear Channel mode, there shall be no specified relationship between the structure of the user data and its positioning within the Payload Sub-Blocks. $k_s$ bits of contiguous user data shall be contained within each Sub-Block, as specified in 8.1. The temporal relationship between the user data stream and the data within the Sub-Blocks shall be maintained such that the order of bits in time from the user data stream shall match the order of transmission within the SHDSL Payload Sub-Blocks. Any additional structure within the user data shall be maintained by an unspecified higher layer protocol and is outside the scope of this Recommendation. + +In the optional $M$ -pair mode, clear channel data will be carried over all pairs using interleaving, as described in 8.2. The bitstream of the user data consisting of $M \times k_s$ bits is mapped to the $M$ pairs by placing alternating bitstreams consisting of $k_s$ bits of contiguous user data in each of the $M$ SHDSL channels. $k_s$ bits of contiguous user data shall be contained within a Sub-Block on Pair 1, and the following sets of $k_s$ bits of contiguous user data shall be contained within the corresponding Sub-Blocks of subsequent pairs. As noted above, any additional structure within the user data shall be maintained by an unspecified higher layer protocol and is outside the scope of this Recommendation. + +## E.2 TPS-TC for clear channel byte-oriented data + +In the byte-oriented clear channel mode, the input byte stream shall be aligned within the SHDSL Payload Sub-Block such that the byte boundaries are preserved. Each Payload Sub-Block is treated as containing $n$ 8-bit time slots. Each byte from the input data stream is mapped LSB-first into the next available time slot. The first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ... , time slot $n$ . A total of $k_s$ bits (or $n$ bytes) of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . Note that optional extensions described in Annex F allow values of $n$ up to 89. See Figure E.1 for additional details. + +![Diagram of clear channel byte-oriented framing structure. The top row shows a sequence of fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below the first Payload block, a callout shows a vertical stack of 12 Sub-Blocks, labeled Sub-Block 1 through Sub-Block 12. Below this stack, a callout shows a horizontal row of time slots labeled TS1, TS2, ..., TSn. The text 'Payload data, bits 1 to ks' is placed above the time slots. The diagram is labeled G.991.2_FE-1 at the bottom.](93bd00a00fa28558486f0664550699b1_img.jpg) + +G.991.2\_FE-1 + +Diagram of clear channel byte-oriented framing structure. The top row shows a sequence of fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below the first Payload block, a callout shows a vertical stack of 12 Sub-Blocks, labeled Sub-Block 1 through Sub-Block 12. Below this stack, a callout shows a horizontal row of time slots labeled TS1, TS2, ..., TSn. The text 'Payload data, bits 1 to ks' is placed above the time slots. The diagram is labeled G.991.2\_FE-1 at the bottom. + +**Figure E.1/G.991.2 – Clear channel byte-oriented framing** + +In the optional $M$ -pair mode, byte-oriented data is carried over all $M$ pairs using interleaving, as described in 8.2. A total of $M \times k_s$ bits ( $M \times n$ bytes) of byte-oriented data shall be transported per SHDSL Payload Sub-Block. $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . Note that optional extensions described in Annex F allow values of $n$ up to 89. Only numbers of time slots divisible by $M$ may be supported in $M$ -pair mode. The input byte stream shall be aligned within the SHDSL Payload Sub-Block such that the byte boundaries are preserved. Each Payload Sub-Block is treated as containing $M \times n$ 8-bit time slots. Each byte from the input data stream is mapped LSB-first into the next available time slot. The first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ... , time slot $n$ . A total of $M \times k_s$ bits (or + +$M \times n$ bytes) of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . The bytes from the input data stream shall be interleaved among all $M$ pairs, such that pair $M$ carries the $m$ th byte out of every block of $M$ bytes. See Figure E.2 for additional details. + +![Diagram illustrating M-pair framing for byte-oriented clear channel for the M=2 case. It shows the hierarchy from aligned frames down to individual time slots (TS) for Pair 1 and Pair 2, with payload data distribution across sub-blocks.](3fa5b988fc31a30231724a06f3567c54_img.jpg) + +The diagram illustrates the framing structure for $M=2$ pairs. At the top, 'Aligned Pair 1 and Pair 2 frames' are shown as a sequence of fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a zoomed-in view of a 'Payload block' shows it contains 12 'Sub-Block' units, labeled Sub-Block 1 through Sub-Block 12. Below the sub-blocks, the payload data is split into two pairs. 'Pair 1' contains time slots $TS_1, TS_3, \dots, TS_{n-1}$ , corresponding to 'Payload data, bits 1 to $k_s$ '. 'Pair 2' contains time slots $TS_2, TS_4, \dots, TS_n$ , corresponding to 'Payload data, bits $k_s + 1$ to $2k_s$ '. Lines connect the payload blocks to the sub-blocks and then to the specific time slots for each pair. + +Diagram illustrating M-pair framing for byte-oriented clear channel for the M=2 case. It shows the hierarchy from aligned frames down to individual time slots (TS) for Pair 1 and Pair 2, with payload data distribution across sub-blocks. + +G.991.2\_FE-2 + +**Figure E.2/G.991.2 – $M$ -pair framing for byte-oriented clear channel (for the $M = 2$ case)** + +## E.3 TPS-TC for unaligned DS1 transport + +Much of the data within the North American network is structured as "DS1" data streams, which, for purposes of this Recommendation, can be described as 1.544 Mbit/s data streams containing 8 kHz framing, with each frame containing 24 8-bit time slots and one framing bit. Details of DS1 framing and associated data structure can be found in 2.1/G.704 [B6]. + +In Unaligned DS1 mode, there shall be no specified relationship between the DS1 frames and their positioning within the Payload Sub-Blocks. A total of $k_s$ bits of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $n = 24$ and $i = 1$ . The DS1 framing clocks shall be synchronized to the SHDSL clocks such that the DS1 frame always appears in the same position within each SHDSL Payload Sub-Block; however, no particular alignment is specified. The temporal relationship between the DS1 data stream and the data within the Sub-Blocks shall be maintained, such that the order of bits in time from the DS1 data stream shall match the order of transmission within the SHDSL Payload Sub-Blocks. The optional $M$ -pair mode will not support Unaligned DS1 transport. + +## E.4 TPS-TC for aligned DS1/fractional DS1 transport + +As noted in E.3, "DS1" data streams consist of 1.544 Mbit/s data streams containing 8 kHz framing, with each frame containing 24 8-bit time slots and one framing bit. In some cases, "Fractional DS1" data streams are used, where DS1 frames contain less than the normal 24 8-bit time slots. Aligned DS1/Fractional DS1 mode is also applicable to 1.544 Mbit/s PRI (Primary Rate ISDN), as described in 4.2/I.431 [B10]. + +In Aligned DS1/Fractional DS1 mode, each DS1 frame shall be aligned within the SHDSL Payload Sub-Block such that the DS1 framing bit occupies the first bit position within the Payload Sub-Block, followed by time slot 1, time slot 2, ..., time slot $n$ . A total of $k_s$ bits of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 1$ . In DS1 applications, $n = 24$ , and, in Fractional DS1 applications, $3 \leq n < 24$ . The DS1 framing clocks shall be synchronized to the SHDSL clocks such that the DS1 frame always appears in the defined position within each SHDSL Payload Sub-Block. See Figure E.3 for additional details. + +![Diagram of Aligned DS1/fractional DS1 framing structure showing the hierarchy from the overall frame to the sub-block and then to the DS1 frame bits.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +The diagram illustrates the framing structure for Aligned DS1/fractional DS1 transport. At the top, a horizontal sequence of blocks represents the overall frame structure: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a vertical stack of 12 blocks represents the SHDSL Payload Sub-Blocks, labeled Sub-Block 1 through Sub-Block 12. Lines connect the first Payload block of the top frame to the first Sub-Block and the last Payload block to the last Sub-Block. Below the Sub-Blocks, a horizontal sequence of bits represents the DS1 frame structure: F (Framing bit), TS1 (Time slot 1), TS2 (Time slot 2), ..., TSn (Time slot n). Lines connect the first and last bits of the DS1 frame to the first and last bits of the first Sub-Block, with the label "Payload data, bits 1 to $k_s$ " indicating the data carried in each sub-block. + +G.991.2\_FE-3 + +Diagram of Aligned DS1/fractional DS1 framing structure showing the hierarchy from the overall frame to the sub-block and then to the DS1 frame bits. + +**Figure E.3/G.991.2 – Aligned DS1/fractional DS1 framing** + +In the optional $M$ -pair mode, DS1/Fractional DS1 data will be carried over all $M$ pairs using interleaving, as described in 8.2. A total of $M \times (k_s - 1) + 1$ bits of DS1/Fractional DS1 data shall be transported per SHDSL Payload Sub-Block. $k_s = i + n \times 8$ , and, in this mode, $i = 1$ . In DS1 applications, $n = 24/M$ , and in Fractional DS1 applications, $3 \leq n < 24/M$ . In $M$ -pair mode only multiples of $M$ DS1 time slots may be supported. Each DS1 frame shall be aligned within the SHDSL Payload Sub-Block such that the DS1 framing bit occupies the first bit position within the Payload Sub-Block on each of the $M$ wire pairs. The time slots of the DS1 frame shall be interleaved among all $M$ wire pairs, such that pair $M$ carries the $m$ th time slot out of every block of $M$ slots. See Figure E.4 for additional details. + +![Diagram illustrating M-Pair framing for DS1/fractional DS1 for the M=2 case. The diagram shows a top-level frame structure consisting of Frame Sync, OH, Payload Block, OH, Payload Block, OH, Payload Block, OH, Payload Block, and Stb. A Payload Block is expanded to show 12 Sub-Blocks. These Sub-Blocks are further divided into Pair 1 and Pair 2 data. Pair 1 contains bits 1 to k_s, organized as F, TS_1, TS_3, ..., TS_{n-1}. Pair 2 contains bits k_s + 1 to 2k_s - 1, organized as F, TS_2, TS_4, ..., TS_n.](beda549cc2a4e2b9ac7f74fe9ed72b67_img.jpg) + +Aligned +Pair 1 and +Pair 2 +Frames + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame Sync | OH | Payload Block | OH | Payload Block | OH | Payload Block | OH | Payload Block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +Pair 1 and +Pair 2 + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + +Payload Data, Bits 1 to $k_s$ + +Pair 1 + +| | | | | | +|---|-----------------|-----------------|-----|-------------------| +| F | TS 1 | TS 3 | ... | TS n-1 | +|---|-----------------|-----------------|-----|-------------------| + +Pair 2 + +| | | | | | +|---|-----------------|-----------------|-----|-----------------| +| F | TS 2 | TS 4 | ... | TS n | +|---|-----------------|-----------------|-----|-----------------| + +Payload Data, Bits $k_s + 1$ to $2k_s - 1$ + +G.991.2\_FE-4 + +Diagram illustrating M-Pair framing for DS1/fractional DS1 for the M=2 case. The diagram shows a top-level frame structure consisting of Frame Sync, OH, Payload Block, OH, Payload Block, OH, Payload Block, OH, Payload Block, and Stb. A Payload Block is expanded to show 12 Sub-Blocks. These Sub-Blocks are further divided into Pair 1 and Pair 2 data. Pair 1 contains bits 1 to k\_s, organized as F, TS\_1, TS\_3, ..., TS\_{n-1}. Pair 2 contains bits k\_s + 1 to 2k\_s - 1, organized as F, TS\_2, TS\_4, ..., TS\_n. + +**Figure E.4/G.991.2 – *M*-Pair framing for DS1/fractional DS1 (for the *M* = 2 case)** + +## E.5 TPS-TC for European 2048 kbit/s digital unstructured leased line (D2048U) + +D2048U data streams contain unstructured 2.048 Mbit/s data with no specified framing. These data streams shall be carried using the Clear Channel TPS-TC described in E.1. + +## E.6 TPS-TC for unaligned European 2048 kbit/s digital structured leased line (D2048S) + +Much of the data within the European network is structured as D2048S data streams, which, for purposes of this Recommendation, can be described as 2.048 Mbit/s data streams containing 8 kHz framing, with each frame containing 32 8-bit time slots. Details of D2048S framing and associated data structure can be found in 2.3/G.704 [B6]. + +In Unaligned D2048S mode, there shall be no specified relationship between the D2048S frames and their positioning within the Payload Sub-Blocks. A total of $k_s$ bits of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n imes 8$ , and, in this mode, $n = 32$ and $i = 0$ . The D2048S framing clocks shall be synchronized to the SHDSL clocks such that the D2048S frame always appears in the same position within each SHDSL Payload Sub-Block; however, no particular alignment is specified. The temporal relationship between the D2048S data stream and the data within the Sub-Blocks shall be maintained, such that that the order of bits in time from the D2048S data stream shall match the order of transmission within the SHDSL Payload Sub-Blocks. The optional *M*-pair mode will not support Unaligned D2048S transport. + +## E.7 TPS-TC for aligned European 2048 kbit/s digital structured leased line (D2048S) and fractional + +As noted in E.6, D2048S data streams consist of 2048 Mbit/s data streams containing 8 kHz framing, with each frame containing 32 8-bit time slots. In some cases, Fractional D2048S data streams are used, where frames contain less than the normal 32 8-bit time slots. Aligned D2048S mode is also applicable to 2.048 Mbit/s PRI (Primary Rate ISDN), as described in 5.2/I.431 [B10]. + +In the aligned D2048S mode, each D2048S frame shall be aligned within the SHDSL Payload Sub-Block such that the first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ..., time slot $n$ . A total of $k_s$ bits of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ . In D2048S applications, $n = 32$ , and, in Fractional D2048S applications, $3 \leq n < 32$ . The D2048S framing clocks shall be synchronized to the SHDSL clocks such that the D2048S frame always appears in the defined position within each SHDSL Payload Sub-Block. See Figure E.5 for additional details. + +![Diagram of Aligned D2048S/fractional D2048S framing showing the mapping from SHDSL frame payload blocks to sub-blocks and then to time slots.](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +The diagram illustrates the framing structure. At the top, an SHDSL frame is shown with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. A single Payload block is expanded into 12 Sub-Blocks, labeled Sub-Block 1 through Sub-Block 12. Each Sub-Block is further expanded to show its content: "Payload data, bits 1 to $k_s$ ", which consists of a sequence of time slots: $TS_1$ , $TS_2$ , ..., $TS_n$ . + +Diagram of Aligned D2048S/fractional D2048S framing showing the mapping from SHDSL frame payload blocks to sub-blocks and then to time slots. + +G.991.2\_FE-5 + +**Figure E.5/G.991.2 – Aligned D2048S/fractional D2048S framing** + +In the optional $M$ -pair mode, D2048S/Fractional D2048S data will be carried over all $M$ pairs using interleaving, as described in 8.2. A total of $M \times k_s$ bits of D2048S/Fractional D2048S data shall be transported per SHDSL Payload Sub-Block. $k_s = i + n \times 8$ , and, in this mode, $i = 0$ . In D2048S applications, $n = 32/M$ , and in Fractional DS1 applications, $3 \leq n < 32/M$ . In $M$ -pair mode, only multiples of $M$ D2048S time slots may be supported. The time slots of the D2048S frame shall be interleaved among all $M$ wire pairs, such that pair $M$ carries the $m$ th time slot out of every block of $M$ slots. See Figure E.6 for additional details. + +![Diagram showing the hierarchical mapping of SHDSL frames. A top-level frame with OH and Payload blocks is expanded into 12 sub-blocks, which are then further divided into two pairs (Pair 1 and Pair 2) containing interleaved time slots (TS1, TS3... and TS2, TS4...).](5ee80a63ec53c60d7306b5a44984afcf_img.jpg) + +Aligned Pair 1 and Pair 2 frames + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + + + +Pair 1 and Pair 2 + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + + + +Payload data, bits 1 to $k_s$ + +Pair 1 + +| | | | | +|-----------------|-----------------|-----|-------------------| +| TS 1 | TS 3 | ... | TS n-1 | +|-----------------|-----------------|-----|-------------------| + + + +Pair 2 + +| | | | | +|-----------------|-----------------|-----|-----------------| +| TS 2 | TS 4 | ... | TS n | +|-----------------|-----------------|-----|-----------------| + +Payload data, bits $k_s + 1$ to $2k_s$ + +Diagram showing the hierarchical mapping of SHDSL frames. A top-level frame with OH and Payload blocks is expanded into 12 sub-blocks, which are then further divided into two pairs (Pair 1 and Pair 2) containing interleaved time slots (TS1, TS3... and TS2, TS4...). + +G.991.2\_FE-6 + +**Figure E.6/G.991.2 – *M*-Pair framing for aligned D2048S/fractional D2048S +(for the *M* = 2 case)** + +## E.8 TPS-TC for synchronous ISDN basic access + +In this TPS-TC mode, the mapping of the ISDN customer data channels to SHDSL payload channels is specified for synchronous transport of multiple ISDN BAs (Basic Access) using clock mode 3a (see 10.1). + +The ISDN customer data channels are embedded into the payload data within the SHDSL frames. ISDN channels and SHDSL frames (and any other TPS-TC if Dual-Bearer mode is utilized – see E.10) are synchronized to the same clock domain. + +### E.8.1 ISDN BA over SHDSL frames + +Figure E.7 illustrates typical transport of ISDN BAs within the SHDSL frames. The basic characteristics of this transport are as follows: + +- B-channels and D-channels are mapped on SHDSL payload channels. +- The ISDN BA does not need a separate synchronization since the SHDSL frames are synchronized to the same clock domain. Therefore, the ISDN frame word (12 kbit/s) is not needed. +- The ISDN M-channel transports ISDN line status bits, transmission control information as well as signalling to control the ISDN connection. Only the ISDN M-channel functions which are needed to control the interface to the ISDN terminal equipment are transported over a messaging channel (SHDSL EOC or fast signalling channel). + +### E.8.2 Mapping of ISDN B- and D-channels on SHDSL payload channels + +The ISDN B- and D- channels are transported within the SHDSL payload sub-blocks. The SHDSL payload data is structured within the SHDSL frames as follows: + +- Each payload sub-block contains $k_s = i + n \times 8$ bits ( $i = 0..7$ and $n = 3..36$ , or, optionally, $n = 37..89$ , as described in Annex F). +- Each sub-block is ordered in the following way: $i$ 1-bit time slots followed by $n$ 8-bit time slots. +- 1-bit time slots are referred to as Z-bits, and 8-bit time slots are referred to as $TS_1 \dots TS_n$ . + +![Diagram showing the mapping of ISDN B- and D-channels onto SHDSL payload sub-blocks. The top part shows a frame structure with sync, overhead (OH), payload blocks, and a stop (Stb) indicator. The middle part shows 12 sub-blocks. The bottom part shows the mapping of Z-bits and time slots (TS) to ISDN B and D channels. Z-bits are mapped to D16 channels, and time slots are mapped to B1 and B2 channels, which are then grouped into ISDN BA1 and ISDN BAm.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +The diagram illustrates the mapping of ISDN channels onto SHDSL frames. At the top, a frame structure is shown with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a callout shows a detailed view of a payload block containing 12 sub-blocks, labeled Sub-Block 1 through Sub-Block 12. Below the sub-blocks, a callout shows the internal structure of payload data, bits 1 to $k_s$ , which are organized into Z-bits ( $Z_1, Z_2, \dots, Z_{n-1}, Z_n$ ) and time slots ( $TS_1, TS_2, \dots, TS_{n-1}, TS_n$ ). Further down, the mapping is shown: Z-bits are grouped into $D_{16}$ channels, and time slots are grouped into $B_1$ and $B_2$ channels. These are then mapped to ISDN B and D channels, specifically ISDN $BA_1$ and ISDN $BA_m$ . + +Diagram showing the mapping of ISDN B- and D-channels onto SHDSL payload sub-blocks. The top part shows a frame structure with sync, overhead (OH), payload blocks, and a stop (Stb) indicator. The middle part shows 12 sub-blocks. The bottom part shows the mapping of Z-bits and time slots (TS) to ISDN B and D channels. Z-bits are mapped to D16 channels, and time slots are mapped to B1 and B2 channels, which are then grouped into ISDN BA1 and ISDN BAm. + +G.991.2\_FE-7 + +**Figure E.7/G.991.2 – Mapping of ISDN B- and D-channels** + +The payload sub-blocks are composed of combinations of $n \times 8$ bit-TS time slots and $i \times 1$ -bit Z-time slots: + +- $n$ corresponds to the number of 64 kbit/s payload channels; +- $i$ corresponds to the number of 8 kbit/s channels + +This payload structure allows efficient mapping of ISDN BA channels on SHDSL frames. + +- Data channels (64 kbit/s each, designated $B_1 - B_y$ ) are mapped onto 64 kbit/s TS-channels. +- Signalling channels (16 kbit/s each, designated $D_1 - D_x$ ) are mapped onto two 8 kbit/s Z-channels each.3 + +3 If four or more ISDN BAs are transported, four $D_{16}$ channels are mapped on one 64 kbit/s B-channel. + +A general example of this mapping technique is shown in Figure E.7. + +### E.8.3 Multi-ISDN BAs + +The transport of up to six ISDN BAs is described in detail in the next paragraphs. Figure E.8 shows a mapping example for two ISDN BAs. + +![Diagram illustrating the framing example for 2 x ISDN BA. The top part shows a frame structure with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a detailed view shows 12 sub-blocks (Sub-Block 1 to 12) containing payload data bits 1 to k_s. These sub-blocks are mapped to Z-channels (Z1, Z2, Z3, Z4) and TS-channels (TS1, TS2, TS3, TS4). The Z-channels are further mapped to D16 channels, and the TS-channels are mapped to B1 and B2 channels. The bottom part shows the mapping of these channels to ISDN BA1 and ISDN BA_m.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +G.991.2\_FE-8 + +Diagram illustrating the framing example for 2 x ISDN BA. The top part shows a frame structure with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a detailed view shows 12 sub-blocks (Sub-Block 1 to 12) containing payload data bits 1 to k\_s. These sub-blocks are mapped to Z-channels (Z1, Z2, Z3, Z4) and TS-channels (TS1, TS2, TS3, TS4). The Z-channels are further mapped to D16 channels, and the TS-channels are mapped to B1 and B2 channels. The bottom part shows the mapping of these channels to ISDN BA1 and ISDN BA\_m. + +**Figure E.8/G.991.2 – Framing example: 2 × ISDN BA** + +The transport of the customer data channels of each ISDN BA requires 144 kbit/s bandwidth. Table E.1 shows the number of required TS- and Z-channels. + +**Table E.1/G.991.2 – K × ISDN BA** + +| Number of ISDN BA
K | Payload bit rate
$K \times (128 \text{ kbit/s} + 16 \text{ kbit/s})$ | Application | TS-channels
(64 kbit/s)
n | Z-channels
(8 kbit/s)
i | +|-------------------------------|-------------------------------------------------------------------------|-------------|----------------------------------------|--------------------------------------| +| 1 | 144 | 1 ISDN BA | 2 | 2 | +| 2 | 288 | 2 ISDN BA | 4 | 4 | +| 3 | 432 | 3 ISDN BA | 6 | 6 | +| 4 | 576 | 4 ISDN BA | 9 | 0 | +| 5 | 720 | 5 ISDN BA | 11 | 2 | +| 6 | 864 | 6 ISDN BA | 13 | 4 | + +### E.8.4 ISDN BA for lifeline service + +Lifeline service in case of local power failure can be provided by one ISDN BA. The lifeline BA always is that one which is transported over the first time slots of each payload sub-block (e.g., $Z_1$ , $Z_2$ , $TS_1$ , $TS_2$ ). Remote power feeding is provided by the central office such that the transceiver can operate in a reduced power mode. + +### E.8.5 Time slot positions of ISDN B- and D16-channels (EOC signalling) + +If multiple ISDN BAs are transported over SHDSL, certain data channels in the SHDSL payload blocks must be assigned to each ISDN BA. Tables E.2 to E.5 show the allocation of the ISDN data channels of up to 4 BAs. The signalling is transmitted over the SHDSL EOC. + +In order to avoid unnecessary shifting of ISDN D- and B-bits, the respective D-bits are transmitted after their B-bits in the subsequent SHDSL payload sub-block (B-bits in *Nth* payload sub-block and D-bits in *N + 1th* payload sub-block; if the B-bits are transmitted in the last payload sub-block of an SHDSL frame, the D-bits are transmitted in the first payload sub-block of the next SHDSL frame). + +**Table E.2/G.991.2 – Time slot allocation for 1 ISDN BA** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | $Z_1 + Z_2$ | + +**Table E.3/G.991.2 – Time slot allocation for 2 ISDN BAs** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | $Z_1 + Z_2$ | +| 2 | TS 3 | TS 4 | $Z_3 + Z_4$ | + +**Table E.4/G.991.2 – Time slot allocation for 3 ISDN BAs** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | $Z_1 + Z_2$ | +| 2 | TS 3 | TS 4 | $Z_3 + Z_4$ | +| 3 | TS 5 | TS 6 | $Z_5 + Z_6$ | + +**Table E.5/G.991.2 – Time slot allocation for 4 ISDN BAs** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 2 | TS 3 | TS 1 (Bits 1 and 2) | +| 2 | TS 4 | TS 5 | TS 1 (Bits 3 and 4) | +| 3 | TS 6 | TS 7 | TS 1 (Bits 5 and 6) | +| 4 | TS 8 | TS 9 | TS 1 (Bits 7 and 8) | + +**E.8.5.1 Time slot positions of ISDN B- and D16-channels (EOC signalling) in *M*-pair mode** + +In the optional *M*-pair mode, the allocation of up to 3 ISDN BAs to time slots and Z-bits shall be as shown in Tables E.2 to E.4. The allocation for 4 ISDN BAs is shown in Table E.5a. + +**Table E.5a/G.991.2 – Time slot allocation for 4 ISDN BAs** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | Z 1 + Z 2 | +| 2 | TS 3 | TS 4 | Z 3 + Z 4 | +| 3 | TS 5 | TS 6 | Z 5 + Z 6 | +| 4 | TS 7 | TS 8 | Z 7 + Z 8 | + +The Z-bits and time slots shall be interleaved among all *M* wire pairs. See Figure E.8a for additional details. + +![Figure E.8a/G.991.2 – M-pair framing for ISDN BA (for the M = 2 case)](677895e18a11676be0d822ac49108de3_img.jpg) + +The diagram illustrates the framing structure for ISDN BA in a 2-pair (M=2) configuration. At the top, a frame consists of 'Frame sync', 'OH' (Overhead), 'Payload block', 'OH', 'Payload block', 'OH', 'Payload block', 'OH', 'Payload block', and 'Stb' (Stuff bit). A single 'Payload block' is expanded to show it contains 12 sub-blocks (Sub-Block 1 to Sub-Block 12). These sub-blocks are further detailed for Pair 1 and Pair 2. Pair 1 payload data (bits 1 to ks) contains Z1, ..., Z2n-1, TS1, ..., TS2n-1. Pair 2 payload data (bits ks + 1 to 2 ks) contains Z2, ..., Z2n, TS2, ..., TS2n. The Z-bits (Z1, Z2, etc.) map to D16 channels, and the TS bits map to B1 and B2 channels. Specifically, Z1 and Z2 are shown mapping to ISDN BA1, while TS1 and TS2 map to B1 and B2 respectively. The diagram indicates a general mapping for ISDN BAn as well. + +**Figure E.8a/G.991.2 – *M*-pair framing for ISDN BA (for the *M* = 2 case)** + +Figure E.8a/G.991.2 – M-pair framing for ISDN BA (for the M = 2 case) + +**E.8.6 Time slot positions of ISDN B- and D16-channels and the optional fast signalling channel** + +The optional 8 kbit/s fast signalling channel is always conveyed in Z1, as shown in Figure E.9. If this fast signalling channel is used, up to 6 ISDN BAs can be transported over SHDSL. + +140 ITU-T Rec. G.991.2 (12/2003) + +In order to avoid unnecessary shifting of ISDN D- and B-bits, the respective D-bits are transmitted after their B-bits in the subsequent SHDSL payload sub-block (B-bits in *Nth* payload sub-block and D-bits in *N + 1th* payload sub-block; if the B-bits are transmitted in the last payload sub-block of an SHDSL frame, the D-bits are transmitted in the first payload sub-block of the next SHDSL frame). + +![Diagram illustrating the mapping of ISDN B- and D-channels with a fast signalling channel. The top part shows a frame structure with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, Stb. The first payload block is expanded into 12 sub-blocks (Sub-Block 1 to 12). Below this, a row of time slots is shown: Z1, Z2, Z3, ..., Zn-1, Zn, TS1, TS2, ..., TSn-1, TSn. Lines connect Z1, Z2, Z3 to an 'ISDN fast signalling channel' and D16. Lines connect Zn-1, Zn to another D16. Lines connect TS1, TS2 to B1, B2. Lines connect TSn-1, TSn to B1, B2. At the bottom, 'ISDN BA1' and 'ISDN BAm' are shown, with lines connecting them to the time slots. A label 'G.991.2_FE-9' is in the bottom right.](08f5fade508b5badd6175fa5e482132f_img.jpg) + +Diagram illustrating the mapping of ISDN B- and D-channels with a fast signalling channel. The top part shows a frame structure with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, Stb. The first payload block is expanded into 12 sub-blocks (Sub-Block 1 to 12). Below this, a row of time slots is shown: Z1, Z2, Z3, ..., Zn-1, Zn, TS1, TS2, ..., TSn-1, TSn. Lines connect Z1, Z2, Z3 to an 'ISDN fast signalling channel' and D16. Lines connect Zn-1, Zn to another D16. Lines connect TS1, TS2 to B1, B2. Lines connect TSn-1, TSn to B1, B2. At the bottom, 'ISDN BA1' and 'ISDN BAm' are shown, with lines connecting them to the time slots. A label 'G.991.2\_FE-9' is in the bottom right. + +Figure E.9/G.991.2 – Mapping of ISDN B- and D-channels with a fast signalling channel + +Table E.6/G.991.2 – Time slot allocation for 1 ISDN BA using the fast signalling channel + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | + +Table E.7/G.991.2 – Time slot allocation for 2 ISDN BAs using the fast signalling channel + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | +| 2 | TS 3 | TS 4 | Z 4 + Z 5 | + +**Table E.8/G.991.2 – Time slot allocation for 3 ISDN BAs using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | +| 2 | TS 3 | TS 4 | Z 4 + Z 5 | +| 3 | TS 5 | TS 6 | Z 6 + Z 7 | + +**Table E.9/G.991.2 – Time slot allocation for 4 ISDN BAs using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 2 | TS 3 | TS 1 (Bits 1 and 2) | +| 2 | TS 4 | TS 5 | TS 1 (Bits 3 and 4) | +| 3 | TS 6 | TS 7 | TS 1 (Bits 5 and 6) | +| 4 | TS 8 | TS 9 | TS 1 (Bits 7 and 8) | + +**Table E.10/G.991.2 – Time slot allocation for 5 ISDN BAs +using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 2 | TS 3 | Z 2 + Z 3 | +| 2 | TS 4 | TS 5 | TS 1 (Bits 1 and 2) | +| 3 | TS 6 | TS 7 | TS 1 (Bits 3 and 4) | +| 4 | TS 8 | TS 9 | TS 1 (Bits 5 and 6) | +| 5 | TS 10 | TS 11 | TS 1 (Bits 7 and 8) | + +**Table E.11/G.991.2 – Time slot allocation for 6 ISDN BAs +using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 2 | TS 3 | Z 2 + Z 3 | +| 2 | TS 4 | TS 5 | Z 4 + Z 5 | +| 3 | TS 6 | TS 7 | TS 1 (Bits 1 and 2) | +| 4 | TS 8 | TS 9 | TS 1 (Bits 3 and 4) | +| 5 | TS 10 | TS 11 | TS 1 (Bits 5 and 6) | +| 6 | TS 12 | TS 13 | TS 1 (Bits 7 and 8) | + +#### **E.8.6.1 Time slot positions of ISDN B- and D16-channels (fast signalling) in *M*-pair mode** + +In the optional *M*-pair mode, the allocation of up to 3 ISDN BAs to Time Slots and Z-bits shall be as shown in Tables E.6 to E.8. The allocation for 4 to 6 ISDN BAs is shown in Tables E.11a to Table E.11c. + +**Table E.11a/G.991.2 – Time slot allocation for 4 ISDN BAs +using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|---------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | +| 2 | TS 3 | TS 4 | Z 4 + Z 5 | +| 3 | TS 5 | TS 6 | Z 6 + Z 7 | +| 4 | TS 7 | TS 8 | Z 8 + Z 9 | + +**Table E.11b/G.991.2 – Time slot allocation for 5 ISDN BAs +using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|-----------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | +| 2 | TS 3 | TS 4 | Z 4 + Z 5 | +| 3 | TS 5 | TS 6 | Z 6 + Z 7 | +| 4 | TS 7 | TS 8 | Z 8 + Z 9 | +| 5 | TS 9 | TS 10 | Z 10 + Z 11 | + +**Table E.11c/G.991.2 – Time slot allocation for 6 ISDN BAs +using the fast signalling channel** + +| ISDN BA number | ISDN B 1 time slot | ISDN B 2 time slot | ISDN D 16 time slots | +|----------------|-------------------------------|-------------------------------|-----------------------------------| +| 1 | TS 1 | TS 2 | Z 2 + Z 3 | +| 2 | TS 3 | TS 4 | Z 4 + Z 5 | +| 3 | TS 5 | TS 6 | Z 6 + Z 7 | +| 4 | TS 7 | TS 8 | Z 8 + Z 9 | +| 5 | TS 9 | TS 10 | Z 10 + Z 11 | +| 6 | TS 11 | TS 12 | Z 12 + Z 13 | + +In fast signalling mode, the time slots and Z-bits frame shall be aligned within the SHDSL Payload Sub-Block such that the Z1 fast signalling bit occupies the first bit position within the Payload Sub-Block on each of the *M* pairs. The remaining Z-bits and time slots shall be interleaved alternating among all *M* pairs. See Figure E.9a for additional details. + +![Diagram of M-pair framing for ISDN BA (for the M = 2 case).](b8dd9521b601d25e46c5effa0a59b7e1_img.jpg) + +The diagram illustrates the framing structure for ISDN BA, specifically for the $M = 2$ case. It shows a hierarchical breakdown of frames into sub-blocks and individual bits. + +- Aligned Pair 1 and Pair 2 frames:** The top level shows a frame sequence: [Frame sync] [OH] [Payload Block] [OH] [Payload block] [OH] [Payload block] [OH] [Payload block] [Stb]. +- Pair 1 and Pair 2 Sub-blocks:** A Payload Block is expanded into 12 vertical slices labeled Sub-Block 1 through Sub-Block 12. +- Payload data, bits 1 to $k_s$ (Pair 1):** Shows a sequence of bits: $Z_1, Z_2, \dots, Z_{2n}, TS_1, \dots, TS_{2n-1}$ . These are grouped into two $B_1$ blocks. +- Payload data, bits $k_s + 1$ to $2k_s$ (Pair 2):** Shows a sequence of bits: $Z_1, Z_3, \dots, Z_{2n+1}, TS_2, \dots, TS_{2n}$ . These are grouped into two $B_2$ blocks. +- ISDN fast signalling channel:** Lines connect specific $Z$ bits ( $Z_2, Z_3, \dots$ ) to the 'ISDN fast signalling channel' block. +- ISDN $Ba_1$ and $Ba_n$ :** These are connected to $D_{16}$ labels and the $B_1/B_2$ payload blocks. + +The diagram is identified by the reference G.991.2\_FE-9A. + +Diagram of M-pair framing for ISDN BA (for the M = 2 case). + +**Figure E.9a/G.991.2 – $M$ -pair framing for ISDN BA (for the $M = 2$ case)** + +### E.8.7 Signalling over the SHDSL EOC or the fast signalling channel + +The ISDN status signalling information can be optionally transmitted over two different channels: + +- SHDSL EOC. +- Fast signalling channel. + +In both cases, SHDSL EOC messages with their HDLC-like format are used to transport the ISDN message code. The STU-C as well as the STU-R unit can initiate EOC messages. Generally, the ISDN related EOC messages are transported over the SHDSL EOC. In some applications, it is necessary to set up an additional fast signalling channel with 8 kbit/s bandwidth for these ISDN related EOC messages. This is the case when more than four ISDN BAs are used. It may also be used when low latency signalling is required or when another TPS-TC's signalling (e.g., ATM) has substantially restricted the use of the SHDSL EOC channel. + +#### E.8.7.1 SHDSL EOC messages + +The EOC messages number 20 and 148 are used to transmit the ISDN maintenance and control functions as well as the other ISDN EOC messages. + +**Table E.12/G.991.2 – ISDN Request – Message ID 20** + +| Octet # | Contents | Data type | Reference | +|------------|-------------------|---------------|--------------------------| +| 1 | Message ID 20 | Message ID | | +| 2 bits 4-7 | ISDN BA Number | Unsigned char | | +| 2 bits 0-3 | Unused | | Set to 0000 2 | +| 3 | ISDN message code | | | + +**Table E.13/G.991.2 – ISDN Response – Message ID 148** + +| Octet # | Contents | Data type | Reference | +|------------|-------------------|---------------|--------------------------| +| 1 | Message ID 148 | Message ID | | +| 2 bits 4-7 | ISDN BA Number | Unsigned char | | +| 2 bits 0-3 | Unused | | Set to 0000 2 | +| 3 | ISDN message code | | | + +**ISDN BA Number:** Each ISDN BA can be addressed independently. To each ISDN BA, a four-digit number is assigned (BA 1 = 0000, ... BA 6 = 0101). + +#### E.8.7.2 ISDN message codes + +The message codes which are contained as an octet in the SHDSL EOC message "ISDN Requests" are listed in Table E.14. The message codes which are contained as an octet in the SHDSL EOC message "ISDN Response" are listed in Table E.15. + +**Table E.14/G.991.2 – ISDN message codes commands** + +| Function | Message | EOC message code | Comment | +|-------------------------|---------|------------------|---------------------------------------------------------------------------| +| S-Bus Control | SIA | 0001 0000 | S-interface activate
(STU-C → STU-R) | +| | SID | 0001 0001 | S-interface deactivate
(STU-C → STU-R) | +| | SAI | 0001 0010 | S-interface activated
(STU-R → STU-C) | +| | SDI | 0001 0011 | S-interface deactivated
(STU-R → STU-C) | +| ISDN Transceiver Status | ACT | 0000 0001 | Readiness for layer 2 communication
(STU-C → STU-R)
(STU-R → STU-C) | +| | DEA | 0000 0010 | Intention to deactivate
(STU-C → STU-R) | +| | CSO | 0000 0011 | Cold start only
(STU-R → STU-C) | +| BA Termination Reset | S reset | 0000 0000 | Reset of ISDN control unit at STU-R
(STU-C → STU-R) | + +**Table E.14/G.991.2 – ISDN message codes commands** + +| Function | Message | EOC message code | Comment | +|-------------------|------------------------------------|------------------|-----------------| +| ISDN EOC Messages | Operate 2B + D loopback | 0011 0001 | (STU-C → STU-R) | +| | Operate B1-channel loopback (Note) | 0011 0010 | (STU-C → STU-R) | +| | Operate B2-channel loopback (Note) | 0011 0011 | (STU-C → STU-R) | +| | Return to normal | 0011 1111 | (STU-C → STU-R) | +| | Hold state | 0011 0000 | (STU-C → STU-R) | + +NOTE – The use of B1- and B2-channel loopbacks is optional. However, the loopback codes are reserved for these functions. + +**Table E.15/G.991.2 – ISDN Message codes responses** + +| Function | Message | EOC message code | Comment | +|-------------------------|-------------|------------------|-------------------------------------| +| S-Bus Control | SIA | 1001 0000 | S-interface activated | +| | SIAF | 1101 0000 | S-interface activation failed | +| | SID | 1001 0001 | S-interface deactivated | +| | SIDF | 1101 0001 | S-interface deactivation failed | +| | SAI | 1001 0010 | S-interface activated | +| | SDI | 1001 0011 | S-interface deactivated | +| ISDN Transceiver Status | ACT | 1000 0001 | Readiness for layer 2 communication | +| | DEA | 1000 0010 | Intention to deactivate | +| | CSO | 1000 0011 | Cold start only | +| BA Termination Reset | S reset ack | 1000 0000 | Reset of ISDN control unit at STU-R | + +**Table E.15/G.991.2 – ISDN Message codes responses** + +| Function | Message | EOC message code | Comment | +|-------------------|---------------------------------------|------------------|-------------------------------------------------------------------------------| +| ISDN EOC Messages | Operate 2B + D loopback (success) | 1011 0001 | S-interface activate with loop2 | +| | Operate 2B + D loopback (failure) | 1111 0001 | | +| | Operate B1-channel loopback (success) | 1011 0010 | Operate B1-channel loop can be requested whenever the SHDSL link is activated | +| | Operate B1-channel loopback (failure) | 1111 0010 | | +| | Operate B2-channel loopback (success) | 1011 0011 | Operate B2-channel loop can be requested whenever the SHDSL link is activated | +| | Operate B2-channel loopback (failure) | 1111 0011 | | +| | Return to normal (success) | 1011 1111 | | +| | Return to normal (failure) | 1111 1111 | | +| | Hold state | 1011 0000 | | +| | Unable to comply acknowledgement | 1111 0100 | | + +### E.8.8 S-bus control + +The ISDN S-buses which connect the ISDN terminals with the STU-R can be controlled independently with the respective message codes (SIA, SID, SAI, SDI) for each S-bus. The STU-C side can activate and deactivate the S bus and gets status information. These messages are transmitted as SHDSL EOC messages. + +The S-interfaces of each ISDN BA can be addressed independently. To each ISDN BA a four-digit number is (BA 1 = 0000, ... BA 6 = 0101) contained in the ISDN related SHDSL EOC messages. + +**SIA:** In STU-C to STU-R direction, this function is used to request the STU-R to activate the interface at the S reference point. If the interface at the S reference point is to be activated, this message may be sent. In STU-R to STU-C direction the respective response is SIA (S-Interface Activated). + +**SID:** In STU-C to STU-R direction, this function is used to request the STU-R to deactivate the interface at the S reference point. If the interface at the S reference point is to be deactivated, this message may be sent. In STU-R to STU-C direction the respective response is SID (S-Interface Deactivated). + +**SAI:** In STU-R to STU-C direction, this message is used to inform the STU-C that the S-interface and S-bus have been activated. + +**SDI:** In STU-R to STU-C direction, this message is used to inform the STU-C that the S-interface and S-bus have been deactivated. + +### E.8.9 BA termination reset + +The status and condition of each ISDN BA and its S-interface at the STU-R side can be individually monitored from the STU-C side. If a failure or blocking at one ISDN BA is detected, this situation can be resolved by a reset. "BA termination reset" puts the control unit of the S-interface to its default state (the deactivated state). Other BAs or other services are not affected. + +![Sequence diagram for ISDN BA activation initiated by the exchange (Figure E.9b/G.991.2).](6a2b92323d788c2e7e9e570025885181_img.jpg) + +This sequence diagram illustrates the interaction between an LT (STU-C), an NT (STU-R), and a TE (Terminal Equipment) for ISDN BA activation initiated by the exchange. The sequence starts with the LT sending an SIA (Request) to the NT via FE1. The NT responds with SIA (Response) to the LT. The NT then sends INFO2 and INFO3 to the TE. Next, the LT sends an ACT (Request) to the NT, which responds with ACT (Response). The NT sends INFO4 to the TE. Finally, the LT sends another ACT (Request) to the NT, which responds with ACT (Response) via FE4. The diagram is labeled G.991.2\_FE-9B. + +Sequence diagram for ISDN BA activation initiated by the exchange (Figure E.9b/G.991.2). + +Figure E.9b/G.991.2 – ISDN BA activation initiated by the exchange + +![Sequence diagram for ISDN BA activation initiated by the terminal equipment (Figure E.9c/G.991.2).](1ff58ab75ff926ead7067453006a75fe_img.jpg) + +This sequence diagram illustrates the interaction between an LT (STU-C), an NT (STU-R), and a TE (Terminal Equipment) for ISDN BA activation initiated by the terminal equipment. The sequence starts with the TE sending INFO1, INFO2, INFO3, and INFO4 to the NT. The NT then sends a SAI (Request) to the LT via FE2, which responds with SAI (Response) to the NT. The NT sends an ACT (Request) to the LT, which responds with ACT (Response). The NT sends another ACT (Request) to the LT, which responds with ACT (Response) via FE4. The diagram is labeled G.991.2\_FE-9C. + +Sequence diagram for ISDN BA activation initiated by the terminal equipment (Figure E.9c/G.991.2). + +Figure E.9c/G.991.2 – ISDN BA activation initiated by the terminal equipment + +![Sequence diagram for ISDN BA activation initiated by the terminal equipment (Figure E.9d/G.991.2).](819f1d00e68b342a246b64fa888a97f9_img.jpg) + +This sequence diagram illustrates the interaction between an LT (STU-C), an NT (STU-R), and a TE (Terminal Equipment) for ISDN BA activation initiated by the terminal equipment. The sequence starts with the TE sending INFO0 to the NT. The NT then sends a SID (Request) to the LT via FE5, which responds with SID (Response) to the NT via FE6. The NT sends another INFO0 to the TE. The diagram is labeled G.991.2\_FE-9D. + +Sequence diagram for ISDN BA activation initiated by the terminal equipment (Figure E.9d/G.991.2). + +Figure E.9d/G.991.2 – ISDN BA activation initiated by the terminal equipment + +**Table E.16/G.991.2 – State transition table for the NT** + +| State number | NT1.1 | NT1.2 | NT1.3 | NT1.4 | NT1.5 | NT1.5A | NT1.6 | NT1.7 | NT1.8 | NT1.9 | NT2.0 | NT2.0A | NT2.1 | +|-------------------------|-------|--------------------------|-------------------------|-----------------------|---------------------------|----------------------|------------------------|----------------------|----------------------|------------------------|----------------------|-----------------------|----------------------| +| State name | Reset | ISDN service deactivated | ISDN service activation | | | | ISDN service activated | | | | Loopback 2 | | | +| | | | Initiated | T interface activated | T interface activated ack | Active pending | Active | LOS/LFA at T pending | LOS/LFA at T | Deactivation initiated | Loopback pending | Loopback activate ack | Loopback operated | +| INFO sent (CP-IWF → TE) | INFO0 | INFO0 | INFO0 | INFO2 | INFO2 | INFO2 | INFO4 | INFO2 | INFO2 | INFO0 | INFO2 | INFO2 | INFO4 | +| Internal state
Event | G1 | G1 | G1 | G2 | G2 | G2 | G3 | G2 | G2 | G4 | G4 | G4 | G4 | +| Receiving INFO0 | – | – | – | – | – | – | NT1.7 SDI (Request) | – | – | NT1.2 | – | – | – | +| Receiving INFO1 | – | NT1.3 SAI (Request) | – | – | – | – | – | – | – | – | – | – | – | +| Receiving INFO3 | – | – | – | NT1.5 ACT (Request) | – | – | – | – | NT1.5 ACT (Request) | – | NT2.1 ACT (Request) | – | – | +| LOS/LFA at T | – | – | – | – | – | – | NT1.7 SDI (Request) | – | – | – | – | – | – | +| SIA (Request) | – | NT1.4 SIA (Response) | – | – | – | – | – | – | – | NT1.4 SIA (Response) | – | – | – | +| SAI (Response) | – | – | NT1.4 | – | – | – | – | – | – | – | – | – | – | +| SID (Request) | – | – | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | – | NT1.9 SID (Response) | NT1.9 SID (Response) | NT1.9 SID (Response) | +| ACT (Response) | – | – | – | – | NT1.5 | – | – | – | – | – | – | NT2.1 | – | +| ACT (Request) | – | – | – | – | – | NT1.6 ACT (Response) | – | – | – | – | – | – | – | + +**Table E.16/G.991.2 – State transition table for the NT** + +| State number | NT1.1 | NT1.2 | NT1.3 | NT1.4 | NT1.5 | NT1.5A | NT1.6 | NT1.7 | NT1.8 | NT1.9 | NT2.0 | NT2.0A | NT2.1 | +|--------------------------------------|-------|-----------------------------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------|---------------------------------| +| State name | Reset | ISDN service deactivated | ISDN service activation | | | | ISDN service activated | | | | Loopback 2 | | | +| | | | Initiated | T interface activated | T interface activated ack | Active pending | Active | LOS/LFA at T pending | LOS/LFA at T | Deactivation initiated | Loopback pending | Loopback activate ack | Loopback operated | +| Operate 2B+D loopback (Request) | – | NT2.0
Operate 2B+D loopback (success) (Response) | – | – | – | – | – | – | – | – | – | – | – | +| S reset (Request) | – | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | NT1.1
S reset ack (Response) | +| SDI (Response) | – | – | – | – | – | – | – | NT1.8 | – | – | – | – | – | +| SHDSL: Data f not reached | – | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | NT1.1 | +| SHDSL: Data f reached | NT1.2 | – | – | – | – | – | – | – | – | – | – | – | – | + +**Table E.16a/G.991.2 – State transition table for the LT** + +| State number | LT1.1 | LT1.2 | LT1.3 | LT1.4 | LT1.5 | LT1.6 | LT1.7 | LT1.8 | LT2.0 | LT2.1 | LT2.2 | +|------------------------------------------|-------|---------------------------------------------------|------------------------------------|---------------------------------------------|---------------------------------------------------|---------------------------------------------------|---------------------------------------------|------------------------|------------------------------------|------------------------------------|------------------------------------| +| State name | Reset | ISDN service deactivated | ISDN service activation | | | ISDN service activated | | | Loopback 2 | | | +| | | | Initiated | T interface activated | Active pending | Active | LOS/LFA at T | Deactivation initiated | Loopback requested | Loopback pending | Loopback operated | +| FE sent
(CO-IWF
→ ET)

Event | FE7 | FE6 | FE2 | FE2 | FE3 | FE4 | FE12 | (Note) | FE3 | FE3 | FE4 | +| | | | | | | | | | | | | +| FE1 | – | LT1.3 SIA
(Request) | | – | – | – | – | LT1.3 SIA
(Request) | – | – | – | +| FE5 | – | – | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | – | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | Start T2
LT1.8 SID
(Request) | +| FE8 | – | LT2.0
Operate
2B+D
loopback
(Request) | | | LT2.0
Operate
2B+D
loopback
(Request) | LT2.0
Operate
2B+D
loopback
(Request) | | | | | | +| S reset | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | +| SAI
(Request) | – | LT1.4 SAI
(Response) | LT1.3 SAI
(Response) | – | – | – | – | – | – | – | – | +| ACT
(Request) | – | – | – | LT1.5 ACT
(Response)
ACT
(Request) | – | – | LT1.5 ACT
(Response)
ACT
(Request) | – | – | LT2.2
ACT
(Response) | – | +| SDI
(Request) | – | – | – | – | – | LT1.7 SDI
(Response) | – | – | – | – | – | +| SIA
(Response) | | – | LT1.4 | | – | – | | | – | – | – | + +**Table E.16a/G.991.2 – State transition table for the LT** + +| State number | LT1.1 | LT1.2 | LT1.3 | LT1.4 | LT1.5 | LT1.6 | LT1.7 | LT1.8 | LT2.0 | LT2.1 | LT2.2 | +|--------------------------------------------|-------|--------------------------|-------------------------|-----------------------|----------------|------------------------|--------------|------------------------|--------------------|------------------|-------------------| +| State name | Reset | ISDN service deactivated | ISDN service activation | | | ISDN service activated | | | Loopback 2 | | | +| | | | Initiated | T interface activated | Active pending | Active | LOS/LFA at T | Deactivation initiated | Loopback requested | Loopback pending | Loopback operated | +| SID (Response) | – | – | – | – | – | – | – | LT1.2 | – | – | – | +| ACT (Response) | – | – | – | – | LT1.6 | – | | – | | – | – | +| Operate 2B+D loopback (success) (Response) | – | – | – | – | – | – | | | LT2.1 | – | – | +| S reset ack (Response) | LT1.2 | – | – | – | – | – | – | | – | – | – | +| SHDSL: Data c failed | / | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | LT1.1 | +| SHDSL: Data c reached | LT1.2 | – | – | – | – | – | – | – | – | – | – | +| Expiry Timer 2 | | – | – | – | – | – | | LT1.3 | – | – | – | + +**Table E.16b/G.991.2 – Legend for the State transition tables** + +| Name | Description | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No state change | +| / | Impossible by definition of peer-to-peer physical layer procedures or system internal reasons. | +| | Impossible by definition of the physical layer service. | +| Start T2 | Start Timer T2
A description of timer T2 can be found in Note 2 to Table 6 of ETSI ETS 300 012: "Timer 2 (T2) prevents unintentional reactivation. Ist value is 25 ms ≤ value ≤ 100 ms. This implies that the TE has to recognize INFO0 and to react on it within 25 ms. If the NT is able to unambiguously recognize INFO1, then the value of timer 2 may be 0, and an MPH-DEACTIVATE REQUEST would cause a direct transition from state G2 or G3 to G1. It should be noted that the unambiguous detection of INFO1 may not be possible in passive bus configurations, considering all possible implementations." | +| Note | The FE sent to the network is identical to the FE sent prior to the issue of FE5 from the network. | +| FE1 | (LT ← ET) Activate access | +| FE2 | (LT → ET) Access activation initiated | +| FE3 | (LT → ET) Access digital section activated | +| FE4 | (LT → ET) Access or loopback activated | +| FE5 | (LT ← ET) Deactivate access | +| FE6 | (LT → ET) Access deactivated | +| FE7 | (LT → ET) LOS/LFA in DS or loss of power in NT1 | +| FE8 | (LT ← ET) Activate loopback 2 | +| FE12 | (LT → ET) LOS/LFA at T reference point | + +**Table E.17/G.991.2 – Reset Request** + +| Message | EOC message code | Comment | +|---------|------------------|---------| +| S reset | 0000 0000 | | + +**Table E.18/G.991.2 – Reset Response** + +| Message | EOC message code | Comment | +|---------------------|------------------|---------| +| S reset acknowledge | 1000 0000 | | + +### **E.8.10 Transport of ISDN EOC messages over SHDSL EOC** + +Table E.19 shows the six of the eight codes of the EOC functions which are defined in the ISDN standard. (The two messages concerning the corrupted CRC are not required.) + +**Table E.19/G.991.2 – ISDN EOC message codes** + +| Message | Message code | Network | STU-R1 | REG | +|------------------------------------|--------------|---------|--------|-------| +| Operate 2B + D loopback | 0011 0001 | o | d | t/d | +| Operate B1-channel loopback (Note) | 0011 0010 | o | d | t/d | +| Operate B2-channel loopback (Note) | 0011 0011 | o | d | t/d | +| Return to normal | 0011 1111 | o | d | t/d | +| Hold state | 0011 0000 | d/o | o/d | o/d/t | + +Origin (o) & destination (d) & transfer (t) +NOTE – The use of B1- and B2-channel loopbacks is optional. However, the loopback codes are reserved for these functions. + +## **E.9 TPS-TC for ATM transport** + +### **E.9.1 Definitions** + +ATM Asynchronous Transfer Mode + +HEC Header Error Check + +### **E.9.2 Reference model for ATM transport** + +The ATM TC layer for SHDSL is consistent with ITU-T Rec. I.432.1 [8]. It shall provide the following functions, as defined in ITU-T Rec. I.432.1: + +- Rate decoupling between ATM layer and the synchronous (or plesiochronous) PMS-TC layer. +- Insertion/Extraction4 of Idle cells. +- Insertion/Extraction5 of ATM Header Error Check (HEC) byte. +- Cell payload scrambling/descrambling for SDH-based systems. +- Cell delineation in the receive channel. +- Bit timing and ordering (MSB sent first with bit timing synchronous to the STU-C downstream timing base). + +The HEC covers the entire cell header. The code used for this function is capable of either: + +- single bit error correction; or +- multiple bit error detection. + +Error detection shall be implemented as defined in ITU-T Rec. I.432.1 [8] with the exception that any HEC error shall be considered as a multiple bit error, and therefore, HEC error correction shall not be performed. + +Figure E.10 shows the logical interface between the ATM Layer, the ATM-TC and the SHDSL PMS-TC function. + +4 An idle cell inserted at the transmit side has to be extracted at the remote side. + +5 A HEC byte inserted at the transmit side has to be extracted at the remote side. + +![Diagram of the ATM-TC logical interface to PMS-TC and TPS-TC ATM layer. The diagram shows a stack of layers: ATM layer at the top, ATM cell TC in the middle, and SHDSL PMS-TC and PMD at the bottom. A bidirectional arrow labeled 'Utopia level 2' connects the ATM layer and ATM cell TC. Between ATM cell TC and SHDSL PMS-TC and PMD, there are several signal lines: OAM, Data, Clock, and Frame clock. To the left, there are two vertical lines labeled 'Rx Ref (8 kHz Note 1)' and 'Tx Ref (8 kHz Note 2)' spanning from the top boundary to the bottom block. The interface between the middle and bottom blocks is labeled 'α or β interface'. The entire middle section is labeled 'ATM TPS-TC'.](40d0aaaa3afa0a9fabe637941ca250bb_img.jpg) + +``` + +graph TD + ATM[ATM layer] <-->|Utopia level 2| TC[ATM cell TC] + subgraph ATM_TPS_TC [ATM TPS-TC] + TC + end + TC --- OAM[OAM] + TC --- Data[Data] + TC --- Clock[Clock] + TC --- Frame[Frame clock] + OAM --- PMS[SHDSL PMS-TC and PMD] + Data --- PMS + Clock --- PMS + Frame --- PMS + PMS --- Interface[α or β interface] + RxRef[Rx Ref 8 kHz Note 1] --- PMS + TxRef[Tx Ref 8 kHz Note 2] --- PMS + +``` + +G.991.2\_FE-10 + +Diagram of the ATM-TC logical interface to PMS-TC and TPS-TC ATM layer. The diagram shows a stack of layers: ATM layer at the top, ATM cell TC in the middle, and SHDSL PMS-TC and PMD at the bottom. A bidirectional arrow labeled 'Utopia level 2' connects the ATM layer and ATM cell TC. Between ATM cell TC and SHDSL PMS-TC and PMD, there are several signal lines: OAM, Data, Clock, and Frame clock. To the left, there are two vertical lines labeled 'Rx Ref (8 kHz Note 1)' and 'Tx Ref (8 kHz Note 2)' spanning from the top boundary to the bottom block. The interface between the middle and bottom blocks is labeled 'α or β interface'. The entire middle section is labeled 'ATM TPS-TC'. + +NOTE 1 – RxRef may be present at the STU-R. + +NOTE 2 – TxRef may be present at the STU-C. + +**Figure E.10/G.991.2 – ATM-TC logical interface to PMS-TC and TPS-TC ATM layer** + +An ATM Utopia level 2 interface connects the ATM-TC to the ATM Layer. This interface may also be realized logically. Byte boundaries, at the ATM Utopia interface, shall be preserved in the SHDSL payload. Bytes are transmitted MSB first, in accordance with ITU-T Rec. I.432.1 [8]. + +#### E.9.2.1 Framing + +The PMS-TC provides a clear channel to the ATM-TC and cells are mapped into the SHDSL payload on a byte-by-byte basis. At the STU-C, cells are mapped across the logical $\alpha$ interface while at the STU-R, cells cross the logical $\beta$ interface, as identified in 4.1. At the $\alpha$ and $\beta$ interface, logical data and clock lines are present. Cell alignment to the frame is optional. The ATM stream shall be aligned within the SHDSL Payload Sub-Block such that the byte boundaries are preserved. Each Payload Sub-Block is treated as containing $n$ 8-bit time slots. Each byte from the input ATM data stream is mapped MSB-first into the next available time slot. The first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ..., time slot $n$ . A total of $k_s$ bits (or $n$ bytes) of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . Note that optional extensions described in Annex F allow values of $n$ up to 89. See Figure E.10a for additional details. + +![Diagram of ATM framing structure showing the hierarchy from the ATM stream to the frame structure.](b5ce6d659e1431289c2e79b01bf38a15_img.jpg) + +The diagram illustrates the ATM framing process. At the top, a horizontal sequence of fields is shown in a frame: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. One Payload block is expanded into a vertical stack of 12 Sub-Blocks, labeled Sub-Block 1 through Sub-Block 12. A line labeled 'Payload data, bits 1 to $k_s$ ' connects the payload blocks to the sub-blocks. At the bottom, a horizontal sequence of bytes from the ATM stream is shown: $b_m$ , $b_{m+1}$ , an ellipsis, and $b_{m+n-1}$ . The text 'G.991.2\_FE10A' is located to the right of the bottom byte sequence. + +Diagram of ATM framing structure showing the hierarchy from the ATM stream to the frame structure. + +**Figure E.10a/G.991.2 – ATM framing** + +In the optional $M$ -pair mode, ATM data is carried over all pairs using interleaving, as described in 8.2. In $M$ -pair mode only multiples of $M$ time slots may be supported. The input ATM stream shall be aligned within the SHDSL Payload Sub-Block such that the byte boundaries are preserved. Each Payload Sub-Block is treated as containing $M \times n$ 8-bit time slots. Each byte from the input ATM data stream is mapped MSB-first into the next available time slot. The first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ... , time slot $n$ . A total of $M \times k_s$ bits (or $M \times n$ bytes) of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . Note that optional extensions described in Annex F allow values of $n$ up to 89. The bytes from the input ATM data stream shall be interleaved among all $M$ pairs, such, where byte $b_m$ is carried on Pair $m$ , byte $b_{m+1}$ is carried in the corresponding time slot on Pair $m + 1$ . Thus, pair $M$ carries the $m$ th time slot out of every block of $M$ time slots. See Figure E.10b for additional details. + +![Diagram illustrating M-pair framing for ATM for the M=2 case. The diagram shows the mapping of an ATM stream into two pairs of frames. At the top, a frame structure is shown with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. A single payload block is expanded into 12 sub-blocks. These sub-blocks are then mapped into two pairs. Pair 1 contains payload data bits 1 to k_s, represented by bytes b_m, b_{m+2}, ..., b_{m+2n-2}. Pair 2 contains payload data bits k_s + 1 to 2k_s, represented by bytes b_{m+1}, b_{m+3}, ..., b_{m+2n-1}. The bottom indicates these bytes originate from an ATM stream.](54f73f693f36dcbd300fa21ac4e410e8_img.jpg) + +Aligned Pair 1 and Pair 2 frames + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +Pair 1 and Pair 2 + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + +Payload data, bits 1 to $k_s$ + +Pair 1 + +| | | | | +|-------|-----------|-----|--------------| +| $b_m$ | $b_{m+2}$ | ... | $b_{m+2n-2}$ | +|-------|-----------|-----|--------------| + +Payload data, bits $k_s + 1$ to $2k_s$ + +Pair 2 + +| | | | | +|-----------|-----------|-----|--------------| +| $b_{m+1}$ | $b_{m+3}$ | ... | $b_{m+2n-1}$ | +|-----------|-----------|-----|--------------| + +Bytes from ATM stream + +G.991.2\_FE-10B + +Diagram illustrating M-pair framing for ATM for the M=2 case. The diagram shows the mapping of an ATM stream into two pairs of frames. At the top, a frame structure is shown with fields: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. A single payload block is expanded into 12 sub-blocks. These sub-blocks are then mapped into two pairs. Pair 1 contains payload data bits 1 to k\_s, represented by bytes b\_m, b\_{m+2}, ..., b\_{m+2n-2}. Pair 2 contains payload data bits k\_s + 1 to 2k\_s, represented by bytes b\_{m+1}, b\_{m+3}, ..., b\_{m+2n-1}. The bottom indicates these bytes originate from an ATM stream. + +**Figure E.10b/G.991.2 – $M$ -pair framing for ATM (for the $M = 2$ case)** + +#### E.9.2.2 Timing + +STUs shall be operated in either synchronous or plesiochronous mode; however, in most applications synchronous operation is preferred. In either case, the STU-C frame clock is locked to network timing. + +The provision of Network Timing Reference from the STU-C to the STU-R for ATM is optional; however, if an NTR is provided, the SHDSL PMS-TC shall operate in clock synchronization mode 3a (see 10.1). The network timing reference shall be an 8 kHz marker from which clocks at other frequencies could easily be derived. In this clock mode, both the frame and symbol clocks at the STU-C are locked to the NTR. The STU-R may extract the NTR from the received Frame Synchronization Word (FSW). Referring to Figure E.10, the TxRef (in the STU-C) lines carries NTR directly to the PMS-TC, while RxRef (in the STU-R) carries the NTR to the ATM Layer from PMS-TC. Synchronization to the NTR shall be as described in 10.4. + +#### E.9.2.3 IMA using the ATM TPS-TC (Informative) + +The ATM TPS-TC, as defined in E.9, is intended to be compatible with Inverse Multiplexing for ATM (IMA) Specification, as defined in af-phy-0086.001 [B12]. IMA is a protocol that provides for inverse multiplexing of an ATM cell stream over multiple physical layer transmission links. It operates by multiplexing the ATM cell stream between the links on a cell-by-cell basis and then inserting special IMA Control Protocol (ICP) cells into each of the individual ATM cell streams. Since the IMA cell stream for each link is structurally identical to a stream of normal ATM cells, IMA cell streams may be carried without modification using the SHDSL ATM TPS-TC. Note that the IMA Specification assumes that the ATM TPS-TC will be compatible with the IMA exceptions to the Interface Specific Transmission Convergence Sublayer, as defined in the IMA Specification, 5.2.1 (specifically, items R-3 and R-4). + +The IMA Specification (9.1) indicates that the differential delay from the IMA transmitter to the loop interface (U-R or U-C) is to be no greater than 2.5 cells. Clause 7.1.6 recommends a maximum differential signal transfer delay between non-repeated SHDSL wire pairs of no more than 50 $\mu$ s at 150 kHz. With regard to repeaters, note that this Recommendation (9.5.5.5) allows up to 8 repeaters in an access link; however, it does not define the delay through the repeater. Also note that the number of repeaters deployed in a loop is dependent on network-specific conditions. Implementers are encouraged to take into account the various sources of differential delay, including differential latencies introduced by repeaters (if present), in the design of IMA systems. + +### E.9.3 Transport capacity and flow control + +An STU transporting ATM shall support $N \times 64$ kbit/s data rates. The payload data rate shall be: $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $i = 0$ . This restriction applies to the data rate and payload block size, as specified in 7.1.1, 8.1 and 8.2. Note that optional extensions described in Annex F allow values of $n$ up to 89. + +In the optional $M$ -pair mode, the rates specified shall apply per pair. + +The ATM-TC shall provide flow control, allowing the STU-C and STU-R to control the cell flow from the ATM layer. This functionality is implemented through the TX\_Cell Handshake and RX\_Cell handshake at the ATM Utopia bus interface. A cell may be transferred to the ATM-TC layer only after the completion of a TX\_Cell Handshake. Similarly, a cell may be transferred from the ATM-TC to the ATM Layer only after the STU has completed an RX\_Cell\_Handshake. This functionality is important to avoid cell overflow and underflow at the TU layer. + +### E.9.4 Operations and maintenance + +The ATM-TC requires Operations, Administration and Maintenance (OAM) functionality. The messaging protocol and format should be handled in accordance with clause 9. The OAM functions notify the OAM entity at the opposite end of the line upon the status of the cell delineation process (e.g., Header Error Check (HEC) anomalies and Loss of Cell Delineation defects (LCD)). Performance parameters are derived from anomalies and defects. + +#### E.9.4.1 ATM data path related near-end anomalies + +*Near-end No Cell Delineation (nncd) anomaly:* An *nncd* anomaly occurs immediately after ATM-TC start-up, when ATM data is received and the cell delineation process is in HUNT or PRESYNC state. Once cell delineation is acquired, subsequent losses of cell delineation shall be considered *nocd* anomalies. + +*Near-end Out of Cell Delineation (nocd) anomaly:* An *nocd* anomaly occurs when the cell delineation process in operation transitions from the SYNC state to HUNT state. An *nocd* anomaly terminates when the cell delineation process transition from PRESYNC to SYNC state or when *nlcd* defect maintenance status is entered. + +*Near-end Header Error Control (nhec) anomaly:* An *nhec* anomaly occurs when an ATM cell header error control fails. + +#### E.9.4.2 ATM data path related near-end defects + +*Near-end Loss of Cell Delineation (nlcd) defect:* An *nlcd* defect occurs when at least one *nocd* is present in 9 consecutive SHDSL frames and no *losw* defect (loss of synchronization word) is detected. An *nlcd* defect terminates after the cell delineation process has entered and remained in the SYNC state in 9 consecutive SHDSL frames. + +#### E.9.4.3 ATM data path related far-end anomalies + +*Far-end No Cell Delineation (fncd) anomaly:* An *fncd* anomaly is an *nncd* anomaly that is reported from the far end by the NCD indicator in the EOC ATM Cell Status Information message. An *fncd* anomaly occurs immediately after start-up and terminates if the received NCD indicator is coded 0. + +Note that, since the far end reports the NCD indicator only on request, the *fncd* anomaly may be inaccurate for derivation of the far-end NCD failure. Therefore, the NCD failure is autonomously reported from the far end. + +*Far-end Out of Cell Delineation (focd) anomaly:* A *focd* anomaly is a *nocd* anomaly, that is reported from the far end by the OCD indicator in the EOC ATM Cell Status Information message. The OCD indicator shall be coded 0 to indicate no *nocd* anomaly has occurred since last reporting and shall be coded 1 to indicate that at least one *nocd* anomaly has occurred since last reporting. An *focd* anomaly occurs if no *fncd* anomaly is present and a received OCD indicator is coded 1. An *focd* anomaly terminates if a received OCD indicator is coded 0. + +*Far-end Header Error Control (fhec) anomaly:* An *fhec* anomaly is an *nhec* anomaly, that is reported from the far end by the HEC indicator in the EOC ATM Cell Status Information message. The HEC indicator shall be coded 0 to indicate no *nhec* anomaly has occurred since last reporting and shall be coded 1 to indicate that at least one *nhec* anomaly has occurred since last reporting. An *fhec* anomaly occurs if a received HEC indicator is coded 1. An *fhec* anomaly terminates if a received HEC indicator is coded 0. + +#### E.9.4.4 ATM data path related far-end defects + +*Far-end Loss of Cell Delineation (flcd) defect:* An *flcd* defect is an *nlcd* that is reported from the far end of the line by the LCD indicator in the EOC ATM Cell Status Information message. The LCD indicator shall be coded 0 to indicate no *nlcd* defect has occurred since last reporting and shall be coded 1 to indicate that at least one *nlcd* defect has occurred since last reporting. An *flcd* defect occurs when the LCD indicator is coded 1. An *flcd* defect terminates when the LCD indicator is coded 0. + +Note that, since the far end reports the LCD indicator only on request, the *flcd* defect may be inaccurate for derivation of the far-end LCD failure. Therefore, the LCD failure is autonomously reported from the far end. + +#### E.9.4.5 ATM cell level protocol performance information collection + +*HEC violation count (hvc):* An *hvc* performance parameter is the count of the number of *nhec* anomalies modulo 65536. + +*HEC total count (htc):* An *htc* performance parameter is the count of the total number of cells passed through the cell delineation process, while operating in the SYNC state, since the last reporting. + +These values shall be counted, such that the Management system is able to retrieve current counts on a 15-minute and 24-hour basis. + +#### E.9.4.6 Failures and performance parameters + +*nncd* failures and *nlcd* failures relate to persistent *nncd* anomalies and persistent *nlcd* defects, respectively. The definitions below are derived from 7.1.2/G.997.1 [3]. These failures are reported in the ATM Cell Status Information message. + +##### E.9.4.6.1 ATM data path related near-end failures + +The following near-end failure indications shall be provided by the STU-C and the STU-R: + +###### E.9.4.6.1.1 Near-End No Cell Delineation (*nncd*) failure + +An *nncd* failure is declared when an *nncd* anomaly persists for more than $2.5 \pm 0.5$ s after the start of Data Mode. An *nncd* failure terminates when no *nncd* anomaly is present for more than $10 \pm 0.5$ s. + +###### E.9.4.6.1.2 Near-End Loss of Cell Delineation (*nlcd*) failure + +An *nlcd* failure is declared when an *nlcd* defect persists for more than $2.5 \pm 0.5$ s. An *nlcd* failure terminates when no *nlcd* defect is present for more than $10 \pm 0.5$ s. + +##### E.9.4.6.2 ATM data path related far-end failures + +The following far-end failure indications shall be provided at the STU-C (the STU-R is at the far end), and are optional at the STU-R (the STU-C is at the far end). + +###### E.9.4.6.2.1 Far-End No Cell Delineation (*fncd*) failure + +An *fncd* failure is declared when an *fncd* anomaly persists for more than $2.5 \pm 0.5$ s after the start of Data Mode. An *fncd* failure terminates when no *fncd* anomaly is present for more than $10 \pm 0.5$ s. + +###### E.9.4.6.2.2 Far-End Loss of Cell Delineation (*flcd*) failure + +An *flcd* failure is declared when an *flcd* defect persists for more than $2.5 \pm 0.5$ s. An *flcd* failure terminates when no *flcd* defect is present for more than $10 \pm 0.5$ s. + +#### E.9.4.7 EOC ATM Cell Status Request message format – Message ID 17 + +The ATM Cell Status Request/Confirmation message is used for two purposes. This message is used as ATM Cell Status Request message to get the STU-R ATM Status. For this purpose, the whole information of EOC ATM Cell Status Information message – Message ID 145 shall be sent in response to this message. If an unexpected receipt of ATM Cell Status message – Message ID 145 is received including NCD or LCD failure indication, this message may be used to confirm the reception and stop future autonomous transmission of the ATM Cell Status message – Message ID 145 due to the current failure condition. + +**Table E.20/G.991.2 – ATM Cell Status Request information field** + +| Octet # | Information field | Data type | +|---------|-------------------|------------| +| 1 | Message ID 17 | Message ID | + +#### E.9.4.8 EOC ATM Cell Status Information message format – Message ID 145 + +The ATM Cell Status Information message shall be sent in response to the ATM Cell Status Request message and shall be sent autonomously upon the occurrence of an *nlcd* Failure or an *nncd* Failure. Table E.21 shows the OAM message bit encoding for an ATM Cell Status Information message. The HEC Indicator is implicitly defined as set to 1 if the HEC violation count has changed since last reporting and set to 0 otherwise. If sent autonomously, Message ID 145 is sent once every second until a Message ID 17 is received from the STU-C or the failure is cleared. + +The NCD, OCD, and LCD Indicator bits shall indicate the state of *nncd* anomaly, *nocd* anomaly, and *nlcd* defect, respectively. NCD Failure and LCD Failure bits shall serve as indications of *nncd* failure and *nlcd* failure, respectively. + +**Table E.21/G.991.2 – ATM cell status information message** + +| Octet # | Contents | Data type | Reference | +|----------------------------------------------------------------------------------|------------------------------------|------------|------------------------------| +| 1 | Message ID 145 | Message ID | | +| 2, bit 7 | NCD Indicator (Note) | Bit | 0 = OK, 1 = alarm | +| 2, bit 6 | OCD Indicator (Note) | Bit | 0 = OK, 1 = alarm | +| 2, bit 5 | LCD Indicator (Note) | Bit | 0 = OK, 1 = alarm | +| 2, bits 4-2 | Reserved | | | +| 2, bit 1 | NCD Failure | Bit | 0 = OK, 1 = alarm | +| 2, bit 0 | LCD Failure | Bit | 0 = OK, 1 = alarm | +| 3 | HEC violation count ( hvc ) | MS Byte | 16-bit counter, modulo 65536 | +| 4 | HEC violation count ( hvc ) | LS Byte | 16-bit counter, modulo 65536 | +| NOTE – Only one of the NCD, OCD, and LCD Indicators can be set to 1 at any time. | | | | + +## E.10 Dual-bearer TPS-TC mode + +The TPS-TC modes in E.1 through E.9 and E.11 through E.13 are described as operating in Single-Bearer Mode; i.e., the payload is treated as a single data stream, and the TPS-TC uses all of the bits in each Payload Sub-Block. In some applications, however, it is desirable to split the payload into separate data streams supporting multiple user interfaces or different data types. Dual-Bearer Mode provides support for these cases. + +Support for Dual-Bearer Mode is optional, as is support for each of the Dual-Bearer TPS-TC combinations specified in Table E.22. + +In Dual-Bearer Mode, each Payload Sub-Block is split between two separate TPS-TC instances. The TPS-TC modes are negotiated independently in ITU-T Rec. G.994.1, and there is no direct interaction between them. TPS-TCa is assigned the first $k_{sa}$ bits of each Payload Sub-Block, and TPS-TCb is assigned the last $k_{sb}$ bits of each Payload Sub-Block (see Figure E.11). For each of the two TPS-TCs, the $k_s$ bits assigned to it are treated as if they constituted a complete Payload Sub-Block, and appropriate framing is applied, as described in E.1 to E.9 and E.11 to E.13 associated with the selected TPS-TC. + +![](bdee2715697a4142d16a360549fa7c7f_img.jpg) + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +Diagram illustrating Dual-bearer mode TPS-TC framing. The top row shows the frame structure: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, Stb. The middle row shows 12 sub-blocks (Sub-Block 1 to Sub-Block 12) being mapped into the payload blocks. The bottom row shows the payload data for two bearers: TPS-TCa (bits $l_a$ to $k_{sa}$ ) and TPS-TCb (bits $l_b$ to $k_{sb}$ ). + +G.991.2\_FE-11 + +**Figure E.11/G.991.2 – Dual-bearer mode TPS-TC framing** + +Figure E.12 shows an example of a Dual-Bearer mode in which Fractional DS1 is TPS-TCa and ATM is TPS-TCb. + +![](1fd763be1b7a05b52e554f0583617642_img.jpg) + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame Sync | OH | Payload Block | OH | Payload Block | OH | Payload Block | OH | Payload Block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +Diagram illustrating an example of dual-bearer mode TPS-TC framing. The top row shows the frame structure: Frame Sync, OH, Payload Block, OH, Payload Block, OH, Payload Block, OH, Payload Block, Stb. The middle row shows 12 sub-blocks (Sub-Block 1 to Sub-Block 12) being mapped into the payload blocks. The bottom row shows the payload data for two bearers: TPS-TCa (bits $l_a$ to $k_{sa}$ ) and TPS-TCb (bits $l_b$ to $k_{sb}$ ). The payload data is further detailed as a sequence of timeslots: Fa, TS1a, TS2a, ..., TSna, TS1b, TS2b, ..., TSnb. + +G.991.2\_FE-12 + +**Figure E.12/G.991.2 – Example of dual-bearer mode TPS-TC framing** + +In the optional *M*-pair mode, the same procedure is followed for Dual-Bearer Mode. The first $k_{sa}$ bits on each pair are assigned to TPS-TCa, and the last $k_{sb}$ bits on each pair are assigned to TPS-TCb. The appropriate *M*-pair TPS-TC framing is then applied, as described in E.1 through E.9 and E.11 through E.13. + +## E.10.1 Dual-bearer clock synchronization + +In Dual-Bearer Mode, it is assumed that timing for the two Bearer Channels is derived from a common source and that the two data streams thus have a definite clocking relationship. As such, no mechanism is provided within the payload blocks to maintain synchronization between the Bearer Channels, regardless of the clock mode that is selected (10.1). + +Note that some TPS-TCs have limitations on the clock modes that are supported. Specifically, ATM using NTR (E.9.2) and Synchronous ISDN BA (E.8) are only defined for Clock Mode 3a (see 10.1). When either of these TPS-TCs is used as part of a Dual-Bearer Mode, the system shall operate in Clock Mode 3a. + +### E.10.2 Dual-bearer mode types + +The following three types of dual-bearer modes are supported within SHDSL: + +Type 1 – STM + Broadband. + +Type 2 – STM + Cell/Packet. + +Type 3 – STM + Clear Channel. + +For each type of dual-bearer mode, separate specification bits are provided within ITU-T Rec. G.994.1 for the selection of the two TPS-TCs to be used. Table E.22 lists the combinations that are supported. Other supported types are for further study. + +**Table E.22/G.991.2 – Supported TPS-TCs in dual-bearer mode** + +| Type | Description | TPS-TC a | TPS-TC b | +|------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | STM + Broadband | Synchronous ISDN BA (E.8)
LAPV5 Enveloped POTS or ISDN (E.13) (Note 2)
STM with DSC (E.12) | Clear Channel (E.1)
Clear Channel Byte-Oriented (E.2)
Unaligned DS1 (E.3) (Note 1)
Aligned DS1/Fractional DS1 (E.4) (Note 1)
Unaligned D2048U (E.5) (Note 2)
Unaligned D2048S (E.6) (Note 2)
Aligned D2048S/Fractional D2048S (E.7) (Note 2)
ATM (E.9)
PTM (E.11) | +| 2 | STM + Cell/Packet | Unaligned DS1 (E.3) (Note 1)
Aligned DS1/Fractional DS1 (E.4) (Note 1)
Unaligned D2048U (E.5) (Note 2)
Unaligned D2048S (E.6) (Note 2)
Aligned D2048S/Fractional D2048S (E.7) (Note 2) | ATM (E.9)
PTM (E.11) | + +**Table E.22/G.991.2 – Supported TPS-TCs in dual-bearer mode** + +| Type | Description | TPS-TC a | TPS-TC b | +|------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| 3 | STM + Clear Channel | Unaligned DS1 (E.3) (Note 1)
Aligned DS1/Fractional DS1 (E.4) (Note 1)
Unaligned D2048U (E.5) (Note 2)
Unaligned D2048S (E.6) (Note 2)
Aligned D2048S/Fractional D2048S (E.7) (Note 2) | Clear Channel (E.1)
Clear Channel Byte-Oriented (E.2) | + +NOTE 1 – Denotes TPS-TC modes that typically apply only in North American networks. + +NOTE 2 – Denotes TPS-TC modes that typically apply only in European networks. + +**E.10.3 Dynamic rate repartitioning** + +Dynamic Rate Repartitioning (DRR) is the procedure for temporarily allocating time slots between the STM Bearer and the Broadband Bearer. The DRR protocol is a master/slave protocol based on messaging, at a rate of one message per superframe. Either the STU-C or the STU-R may be the DRR master; this is configured through ITU-T Rec. G.994.1 [2] during pre-activation. The DRR protocol will be triggered and controlled by a higher layer management entity, denoted in this clause as a supervisory entity. + +![Diagram of dual-bearer mode framing with DRR. The top part shows a frame structure: [Frame sync] [OH] [Payload block] [OH] [Payload block] [OH] [Payload block] [OH] [Payload block] [Stb]. Below this, a zoomed-in view shows 12 sub-blocks (Sub-Block 1 to 12). The bottom part shows the mapping of these sub-blocks to two transport paths: TPS-TCa and TPS-TCb. TPS-TCa carries payload data bits 1a to ksa, and TPS-TCb carries payload data bits 1b to ksb. A separate DRR control channel (1 bit) is shown, containing DRR, DSC, and time slots (TS).](38b35511a4152c6ac1260c489ce24c88_img.jpg) + +The diagram illustrates the framing structure for dual-bearer mode with DRR. At the top, a frame is shown with the following components: Frame sync, OH, Payload block, OH, Payload block, OH, Payload block, OH, Payload block, and Stb. Below this, a zoomed-in view shows 12 sub-blocks (Sub-Block 1 to 12). The bottom part shows the mapping of these sub-blocks to two transport paths: TPS-TCa and TPS-TCb. TPS-TCa carries payload data bits 1a to *ksa*, and TPS-TCb carries payload data bits 1b to *ksb*. A separate DRR control channel (1 bit) is shown, containing DRR, DSC, and time slots (TS). The DRR control channel is labeled 'DRR control channel 1 bit'. The time slots are labeled: TS1a, TS2a, ..., TSna, TS1b, TS2b, ..., TSnb. The payload data for TPS-TCa is labeled 'Payload data, bits 1a to *ksa*' and for TPS-TCb is labeled 'Payload data, bits 1b to *ksb*'. The diagram is labeled 'G.991.2\_FE-13'. + +Diagram of dual-bearer mode framing with DRR. The top part shows a frame structure: [Frame sync] [OH] [Payload block] [OH] [Payload block] [OH] [Payload block] [OH] [Payload block] [Stb]. Below this, a zoomed-in view shows 12 sub-blocks (Sub-Block 1 to 12). The bottom part shows the mapping of these sub-blocks to two transport paths: TPS-TCa and TPS-TCb. TPS-TCa carries payload data bits 1a to ksa, and TPS-TCb carries payload data bits 1b to ksb. A separate DRR control channel (1 bit) is shown, containing DRR, DSC, and time slots (TS). + +**Figure E.13/G.991.2 – Dual-bearer mode framing with DRR** + +Figure E.13 shows an example of a dual-bearer mode with a dedicated DRR control channel, for transport of the DRR protocol messages. These messages control the activation and de-activation of time slots in the STM Bearer, and the corresponding de-allocation/allocation to the Broadband Bearer. The Dedicated Signalling Channel (DSC) carries signalling information for telephony. Its + +bandwidth depends on the application, and can be 0. This example shows 1 bit dedicated to DRR in each Sub-Block, which corresponds to 8 kbit/s capacity. Adding more DRR bits increases the capacity of the DRR control channel. + +### E.10.3.1 Message structure + +The DRR message structure is shown in Figure E.14. These messages will be sent between the DRR master and the DRR slave. The messages consist of one leading Control octet, followed by Channel-ID octet(s). There is one Channel-ID octet for every 8 time slots to be managed by the DRR procedure. The Control octet has 4 bits for the message type, followed by 4 bits for the sequence number. Each bit of the Channel-ID octets corresponds to one time slot, the time slots following, in the frame, the same order as the Channel-ID bits: + +- "1": The corresponding time slot is currently active as part of the STM bearer channel, or is in the process of being activated. +- "0": The corresponding time slot is not in use, and is thus available for broadband data. + +| Octet #1
(Control) | | Octet #2
(Channel ID) | | Octet #3
(Channel ID) | | Octet #4
(Channel ID) | | +|-----------------------|--------------|--------------------------|---------|--------------------------|-------------|--------------------------|-------------| +| b b b b | b b b b | b b b b | b b b b | b b b b | b b b b | b b b b | b b b b | +| Message type | Sequence No. | 1 2 3 4
Time slots | 5 6 7 8 | 9 10 11 12 | 13 14 15 16 | 17 18 19 20 | 21 22 23 24 | + +**Figure E.14/G.991.2 – DRR message structure** + +NOTE – This example assumes the SHDSL system is managing 24 time slots under DRR. + +Each message has a sequence number that is used to control the DRR protocol. The exact usage is given in the description of each state; however, in general it serves to indicate either how many times a particular message has been sent in a sequence; or, in a responding message, to which message number it is responding. Particularly, in an environment in which line disturbance can cause protocol delays, the sequence number can be used to ensure synchronization of framing change. + +The complete set of DRR messages is shown in Table E.23. + +**Table E.23/G.991.2 – Messages used in DRR protocol** + +| DRR message type | Code | Direction | +|------------------|------|----------------------------------| +| MONITOR | 1111 | Master-to-Slave, Slave-to-Master | +| DEMAND | 1110 | Master-to-Slave | +| DEMAND ACK | 1101 | Slave-to-Master | +| DEMAND NAK | 1011 | Slave-to-Master | +| EXEC | 0001 | Master-to-Slave | +| EXEC ACK | 0100 | Slave-to-Master | +| REQUEST | 1100 | Slave-to-Master | + +### E.10.3.2 Message flow for DRR + +Figure E.15 shows a typical message flow for a DRR event. + +| Downstream | | | | Upstream | | | +|------------------------|--------------|---------------------------|--|-----------------------|--------------|----------------------------| +| Message sent by Master | Sequence No. | Message received by Slave | | Message sent by Slave | Sequence No. | Message received by Master | +| Monitor | <0> | Monitor | | Monitor | <0> | Monitor | +| Demand | <1> | Demand | | Monitor | <0> | Monitor | +| Demand | <2> | Demand | | Demand Ack | <1> | Demand Ack | +| Demand | <3> | Demand | | Demand Ack | <1> | Demand Ack | +| Exec | <1> | Exec | | Demand Ack | <1> | Demand Ack | +| Exec | <2> | Exec | | Exec Ack | <1> | Exec Ack | +| Exec | <3> | Exec | | Exec Ack | <2> | Exec Ack | +| Monitor | <0> | Monitor | | Exec Ack | <3> | Exec Ack | +| Monitor | <0> | Monitor | | Monitor | <0> | Monitor | +| Monitor | <0> | Monitor | | Monitor | <0> | Monitor | + +NOTE – Shading change indicates change of framing. + +**Figure E.15/G.991.2 – Message flow, assuming STU-C is DRR Master, $j = 2$** + +### E.10.3.3 Error protection + +Each DRR message is stated 3 times within the same SHDSL superframe, and the correct message is determined by a 2-out-of-3 majority decision at the recipient's end. + +### E.10.3.4 DRR control channel + +The DRR messages are carried by a DRR control channel, a dedicated channel made up of one or more Z-bits (8 kbit/s channel). Each Z-bit provides 48 bits (6 octets) per superframe. Since each message is sent 3 times in the same superframe, each Z-bit provides for 2 octets of message. A 1 Z-bit channel can manage up to 8 time slots, while a 2 Z-bit channel, with 4 octets of message, can manage up to 24 time slots. Messages sent from the DRR master to the DRR slave are referred to as "downstream", and messages from the DRR slave to the DRR master are referred to as "upstream". The number of Z-bits to be used must be configured during pre-activation through ITU-T Rec. G.994.1 [2]. Channel-ID bits that are in excess of the number of managed time slots will not be used. + +### E.10.3.5 Lead time + +The lead time $j$ used in the countdown is the number of downstream superframes starting with EXEC <1> and ending just before the first downstream superframe with the new framing. This will be the same as the number of upstream superframes starting with EXEC ACK <1> and ending just before the first upstream superframe with the new framing. The value of $j$ is to be negotiated during pre-activation through ITU-T Rec. G.994.1 [2]. + +### E.10.3.6 The DRR Protocol – Finite state machine description + +The state diagrams for master and slave are given in Figures E.16 and E.17, respectively. The states are shown as bubbles. The name of the state is given in the upper half of the bubble in *italic* font. The message which is transmitted during the state is given in the lower half of the bubble in CAPITAL letters. Incoming messages which trigger state transition are given in CAPITAL letters as well. Information, commands and notifications to/from the supervisory entity are underlined. Logical operation (i.e., **and**, **or**) are given in **bold** letters as well. These rules also apply to the textual description. Notifications to/from the supervisory entity are primitives and are used for illustrative purposes only. Supervisory actions are out of the scope of this Recommendation. + +![State diagram of the master showing four states: Idle (MONITOR), Initiation (DEMAND), Go Ahead-1 (EXEC), and Go Ahead-2 (EXEC). Transitions are triggered by 'Reset', 'External DRR Initiation or REQUEST', 'DEMAND ACK', 'EXEC ACK', and 'Receive Framer Ready'. Outgoing messages include 'External DRR Initiation or REQUEST', 'DEMAND NAK', and 'DEMAND ACK'.](88c92858439684b2103e88cb143fb98e_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle : Reset + Idle --> Initiation : External DRR Initiation or REQUEST + Initiation --> Idle : DEMAND NAK + Initiation --> Go_Ahead_1 : DEMAND ACK + Go_Ahead_1 --> Go_Ahead_2 : EXEC ACK + Go_Ahead_2 --> Idle : Receive Framer Ready + + state Idle { + Idle_text: Idle + MONITOR: MONITOR + } + state Initiation { + Initiation_text: Initiation + DEMAND: DEMAND + } + state Go_Ahead_1 { + Go_Ahead_1_text: Go Ahead-1 + EXEC1: EXEC + } + state Go_Ahead_2 { + Go_Ahead_2_text: Go Ahead-2 + EXEC2: EXEC + } + +``` + +G.991.2\_FE-16 + +State diagram of the master showing four states: Idle (MONITOR), Initiation (DEMAND), Go Ahead-1 (EXEC), and Go Ahead-2 (EXEC). Transitions are triggered by 'Reset', 'External DRR Initiation or REQUEST', 'DEMAND ACK', 'EXEC ACK', and 'Receive Framer Ready'. Outgoing messages include 'External DRR Initiation or REQUEST', 'DEMAND NAK', and 'DEMAND ACK'. + +**Figure E.16/G.991.2 – State diagram of the master, showing state, outgoing message and trigger conditions** + +![State diagram of the slave for G.991.2. The diagram shows seven states: Not Ready, Idle, Slave Req, Confirmation, Go Ahead, Wait for Monitor, and Wait for Framer. Transitions are triggered by messages like MONITOR, DEMAND, EXEC, and Framer Ready, leading to states like DEMAND NAK, REQUEST, DEMAND ACK, EXEC ACK, or back to Idle.](5f7b02749ab85c5e65d6762767ab6d97_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle : Reset + Idle --> Not Ready : DEMAND and Not Ready for new DRR + Not Ready --> Idle : MONITOR + Idle --> Slave Req : Slave Request and Ready for new DRR + Slave Req --> Idle : Ready for new DRR + Slave Req --> Confirmation : DEMAND + Idle --> Confirmation : DEMAND and Ready for new DRR + Confirmation --> Idle : MONITOR + Confirmation --> Go Ahead : EXEC + Go Ahead --> Wait for Monitor : Framer Ready + Go Ahead --> Wait for Framer : MONITOR or DEMAND + Wait for Monitor --> Idle : MONITOR or DEMAND + Wait for Framer --> Idle : Framer Ready + state "Not Ready" as Not Ready + state "Idle" as Idle + state "Slave Req" as Slave Req + state "Confirmation" as Confirmation + state "Go Ahead" as Go Ahead + state "Wait for Monitor" as Wait for Monitor + state "Wait for Framer" as Wait for Framer + + Not Ready : DEMAND NAK + Idle : MONITOR + Slave Req : REQUEST + Confirmation : DEMAND ACK + Go Ahead : EXEC ACK + Wait for Monitor : EXEC ACK + Wait for Framer : EXEC ACK + +``` + +State diagram of the slave for G.991.2. The diagram shows seven states: Not Ready, Idle, Slave Req, Confirmation, Go Ahead, Wait for Monitor, and Wait for Framer. Transitions are triggered by messages like MONITOR, DEMAND, EXEC, and Framer Ready, leading to states like DEMAND NAK, REQUEST, DEMAND ACK, EXEC ACK, or back to Idle. + +**Figure E.17/G.991.2 – State diagram of the slave, showing state, outgoing message and trigger conditions** + +### E.10.3.7 DRR Master state machine + +**Table E.24/G.991.2 – Idle state of the Master** + +| | | | +|-----------------------------------------------|------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Any | Reset from supervisory entity | | +| Go Ahead-2 | Receiver Framer Ready from master | | +| Initiation | DEMAND NAK | | +| | | | +| Action: | | | +| Transmission of MONITOR <0> | | | +| | | | +| Exit: | | | +| Trigger conditions | Target state | Notification | +| External DRR initiation, or
REQUEST | Initiation | | + +Fail-safe precaution: In the event of a mismatch in the time-slot settings in the Channel-ID octets of the MONITOR upstream and downstream messages, the notification Time-Slot Alarm is issued. + +**Table E.25/G.991.2 – Initiation state of the Master** + +| | | | +|---------------------------------------------|---------------------------------------------------------------------------------|--------------------------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Idle | External DRR initiation, or
REQUEST | | +| | + | | +| Action: | | | +| Transmission of DEMAND
D > | n D begins with 1, and increments until the first trigger condition. | | +| | | | +| Exit: | | | +| Trigger conditions | Target state | Notification | +| DEMAND ACK | Go Ahead-1 | Initiation of Transmit Framer | +| DEMAND NAK | Idle | Slave not ready for DRR | + +Fail-safe precaution: If nD reaches 15, it no longer increments. This could happen if recognition of DEMAND ACK or DEMAND NAK is delayed, due to disturbance on the line. The notification Sequence Number Overflow is issued, and the message DEMAND <15> continues to be transmitted. The master stays in this state until a valid slave response is received, unless there is supervisory intervention. + +**Table E.26/G.991.2 – Go Ahead-1 state of the Master** + +| | | | +|--------------------------------------------|------------------------------------------------------------------------|--------------------------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Initiation | DEMAND ACK | | +| | | | +| Action: | | | +| Transmission of EXEC $\langle n_E \rangle$ | $n_E$ begins with 1, and increments until the first trigger condition. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| EXEC ACK | Go Ahead-2 | Initiation of Receiver Framer | + +Fail-safe precaution: If $n_E$ reaches 15, it no longer increments. This could happen if recognition of the first EXEC ACK is delayed, due to disturbance on the line. The notification Sequence Number Overflow is issued, and the message EXEC $\langle 15 \rangle$ continues to be transmitted. The master stays in this state until a valid slave response is received, unless there is supervisory intervention. + +**Table E.27/G.991.2 – Go Ahead-2 state of the Master** + +| | | | +|--------------------------------------------|--------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Go Ahead State-1 | EXEC ACK | | +| | | | +| Action: | | | +| Transmission of EXEC $\langle n_E \rangle$ | $n_E$ is fixed at the value it had when exiting Go Ahead-1 State. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| Receive Framer Ready | Idle | DRR complete | + +### E.10.3.8 DRR Slave state machine + +An upper-layer supervisory entity also controls the DRR procedure at the DRR slave side. This entity continually asserts a notification, stating whether the slave is ready to accept a new DRR or not (Ready for new DRR, Not Ready for new DRR). + +**Table E.28/G.991.2 – *Idle* state of the Slave** + +| | | | +|---------------------------------------------------|-------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Any | Reset from supervisory entity | | +| Confirmation | MONITOR | | +| Not Ready | MONITOR | | +| Wait for Monitor | MONITOR, or DEMAND | | +| Wait for Framer | Framer Ready | | +| | | | +| Action: | | | +| Transmission of MONITOR <0> | | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| DEMAND and Ready for new DRR | Confirmation | | +| Slave Request and Ready for new DRR | Slave Request | | +| DEMAND and Not Ready for new DRR | Not Ready | | + +**Table E.29/G.991.2 – *Slave Request* state of the Slave** + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Idle | Slave Request and Ready for new DRR | | +| | | | +| Action: | | | +| Transmission of REQUEST R > | n R begins with 1, and increments until the first trigger condition. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| DEMAND | Confirmation | | +| NOTE – In applications with tight timing requirements, it is recommended that the Slave Request State not be used. Instead, the system should be configured with the Dedicated Signalling Channel (DSC, see E.10.3) to allow normal telephony signalling to inform the master of the need for a DRR. | | | + +**Table E.30/G.991.2 – Confirmation state of the Slave** + +| | | | +|-----------------------------------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Idle | DEMAND $\langle n_D \rangle$ and Ready for new DRR | | +| Slave Request | DEMAND $\langle n_D \rangle$ | | +| | | | +| Action: | | | +| Transmission of DEMAND ACK $\langle n_{DA} \rangle$ | $n_{DA}$ is fixed at the sequence number $n_D$ of the triggering DEMAND. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notifications | +| EXEC | Go Ahead | Send both:
– Initiation of Receive and Transmit Framer
– Sequence Number of First Received EXEC (for synchronization purposes) | + +**Table E.31/G.991.2 – Not Ready state of the Slave** + +| | | | +|-----------------------------------------------------|-------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Idle | DEMAND $\langle n_D \rangle$ and Not Ready for new DRR | | +| | | | +| Action: | | | +| Transmission of DEMAND NAK $\langle n_{DN} \rangle$ | $n_{DN}$ is fixed at the sequence number $n_D$ of the triggering DEMAND | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| MONITOR | Idle | DRR aborted | + +**Table E.32/G.991.2 – Go Ahead state of the Slave** + +| | | | +|---------------------------------------------------|---------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Confirmation | EXEC | | +| | | | +| Action: | | | +| Transmission of EXEC ACK $\langle n_{EA} \rangle$ | $n_{EA}$ begins with 1, and increments until the first trigger condition. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| Framer Ready | Wait for Monitor | | +| MONITOR, or DEMAND | Wait for Framer | | + +Fail-safe precaution: If $n_{EA}$ reaches 15, it no longer increments. This could happen if recognition of the first MONITOR or DEMAND is delayed, due to disturbance on the line. The notification Sequence Number Overflow is issued, and the message EXEC ACK <15> continues to be transmitted. The slave stays in this state until a valid master message is received, unless there is supervisory intervention. + +**Table E.33/G.991.2 – Wait for Monitor state of the Slave** + +| | | | +|---------------------------------------------------|---------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Go Ahead | Framer Ready | | +| | | | +| Action: | | | +| Transmission of EXEC ACK $\langle n_{EA} \rangle$ | $n_{EA}$ is fixed at the value it had when exiting Go Ahead State. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| MONITOR, or DEMAND | Idle | DRR complete | + +**Table E.34/G.991.2 – Wait for Framer state of the Slave** + +| | | | +|---------------------------------------------------|---------------------------------------------------------------------------|---------------------| +| Entrance: | | | +| From state | Trigger condition | | +| Go Ahead | MONITOR, or DEMAND | | +| | | | +| Action: | | | +| Transmission of EXEC ACK $\langle n_{EA} \rangle$ | $n_{EA}$ is fixed at the value it had when exiting Go Ahead State. | | +| | | | +| Exit: | | | +| Trigger condition | Target state | Notification | +| Framer Ready | Idle | DRR complete | + +### E.10.3.9 Result of DRR procedure + +Figure E.11 shows the TPS-TC framing for the Dual-Bearer mode. Figure E.18 demonstrates how the mapping of the payload sub-block will be changed by the DRR procedure, in a typical application example. In the initial configuration of this example, the eight 8-bit time slots $TS_{xa}$ that belong to TPC-TCa carry STM (voice) and the $n$ 8-bit time slots $TS_{xb}$ that belong to TPS-TCb carry ATM. When the supervisory entity recognizes that time slot $TS_{2a}$ is not currently carrying voice samples, it instigates a DRR procedure which temporarily repartitions $TS_{2a}$ to the ATM bearer: then seven time slots are carrying STM data, and $(n + 1)$ are carrying ATM data. + +Also shown is the DRR control channel and the Dedicated Signalling Channel (DSC) in Figure E.18. In this example, the DRR control channel uses only 1 Z-bit, which is enough to manage eight time slots (see E.10.3.4). The Dedicated Signalling Channel (DSC) carries the higher-layer telephony signalling for the STM time slots (e.g., per Telcordia GR-303 [B14] or ETSI V5 [9] & [B16]); in applications using channel associated signalling (CAS), and without tight timing constraints, the DSC is optional. + +![Diagram illustrating DRR repartitions TS2a from STM bearer to ATM bearer. The top part shows the initial mapping where time slots TS1a, TS2a, and TS3a are assigned to TPS-TCa, and TS8a, TS1b, and TS2b are assigned to TPS-TCb. The bottom part shows the repartitioned mapping where time slots TS1a, TS2a, and TS3a are assigned to TPS-TCa, and TS8a, TS1b, and TS2b are assigned to TPS-TCb. The diagram shows that after the DRR, time slot TS2a carries ATM data for TPS-TCb. The diagram is labeled G.991.2_FE-18.](3af2fc22afa44863b4fdcb07aa719bc9_img.jpg) + +After the DRR, time slot TS2a carries ATM data for TPS-TCb + +Diagram illustrating DRR repartitions TS2a from STM bearer to ATM bearer. The top part shows the initial mapping where time slots TS1a, TS2a, and TS3a are assigned to TPS-TCa, and TS8a, TS1b, and TS2b are assigned to TPS-TCb. The bottom part shows the repartitioned mapping where time slots TS1a, TS2a, and TS3a are assigned to TPS-TCa, and TS8a, TS1b, and TS2b are assigned to TPS-TCb. The diagram shows that after the DRR, time slot TS2a carries ATM data for TPS-TCb. The diagram is labeled G.991.2\_FE-18. + +**Figure E.18/G.991.2 – DRR repartitions TS2a from STM bearer to ATM bearer (example)** + +### E.10.3.10 Dual-bearer mode types for DRR + +DRR is appropriate for use with some Dual-Bearer Type 1 and Type 2 TPS-TC combinations, as specified in E.10.2 and Table E.22. In particular, DRR may be used with the set of TPS-TCa and TPS-TCb combinations shown in Table E.34a. + +**Table E.34a/G.991.2 – TPS-TCs from dual-bearer mode Types 1 and 2 for which DRR is supported** + +| Type | Description | TPS-TC a | TPS-TC b | +|------|-------------------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | STM + Broadband | Synchronous ISDN BA (E.8)
LAPV5 Enveloped POTS or ISDN (E.13)
STM with DSC (E.12) | Clear Channel Byte-Oriented (E.2)
Aligned DS1/Fractional DS1 (E.4)
Aligned D2048S/Fractional D2048S (E.7)
ATM (E.9)
PTM (E.11) | +| 2 | STM + Cell/Packet | Aligned DS1/Fractional DS1 (E.4)
Aligned D2048S/Fractional D2048S (E.7) | ATM (E.9)
PTM (E.11) | + +NOTE – See Table E.22 for the complete definitions of TPS-TC Types for Dual-Bearer Mode. + +### E.10.3.11 Payload block ordering with DRR + +The clauses describing each of the TPS-TCs define the arrangement of bits within each TPS-TC. As noted in E.10.3.4, the DRR control channel occupies 1 to 3 single-bit time slots (referred to as Z-bits). In addition, an ISDN or LAPV5 TPS-TC may use one or more Z-bits (E.8 and E.13), and a DSC (Dedicated Signalling Channel), if used, may occupy 1 to 7 Z-bits or may be mapped into the first 8-bit time slot (referred to as a B-channel). This clause defines how the different channels are mapped into the TPS-TCs. + +![Diagram of SHDSL payload block ordering with DRR. It shows the hierarchical breakdown of a 48*(1+i+n*8) bit payload block into specific channels (TPS-TCa, TPS-TCb) and sub-channels (Signalling, POTS, ISDN BA, Broadband). It further details the Z-bit mapping to DRR, EOC, DSC, and ISDN D16, and illustrates how Z-bits are combined into a B-channel when their count exceeds 7.](3100b9f8708f586e472f3d9e44f10e52_img.jpg) + +$48 * (1 + i + n * 8)$ bits + +| | | | | | | | | | | | +|-----------|----|---------------------|----|--------------------|----|--------------------|----|--------------------|-------|--------| +| 14 | 2 | $12 * (i + n * 8)$ | 10 | $12 * (i + n * 8)$ | 10 | $12 * (i + n * 8)$ | 10 | $12 * (i + n * 8)$ | 2 | [bits] | +| Sync word | OH | P01 P02 P03 ... P12 | OH | P13 ... P24 | OH | P25 ... P36 | OH | P37 ... P48 | Spare | | + +0 ms Payload block $n * 8, n = 3 … 36$ 6 ms + +--- + +TPS-TCa channel TPS-TCb channel [bits] + +| | | | | | | | | | | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----|----------------|--------|-----|----------------|----------------|-----|-----|----------------| +| Z 1 | Z 2 | Z 3 | Z 4 | Z 5 | Z 6 | Z 7 | B 1 | ... | B n | B(n+1) | ... | B m | B 5 | ... | ... | B n | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----|----------------|--------|-----|----------------|----------------|-----|-----|----------------| + +Signalling Channel(s) (DRR, eoc, D16 channel(s)) | POTS | ISDN BA (B-channel(s)) | Broadband + +--- + +| | | | | | | | | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| Z 1 | Z 2 | Z 3 | Z 4 | Z 5 | Z 6 | Z 7 | Z 8 | Z 9 | Z 10 | Z 11 | Z 12 | Z 13 | Z 14 | +|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|-----------------|-----------------|-----------------|-----------------|-----------------| + +DRR control channel | Fast EOC | DSC | ISDN D16 channel(s) + +← Counting direction — + +| | | | | | | | +|----------------|----------------|----------------|----------------|----------------|----------------|----| +| Z 1 | Z 2 | Z 3 | Z 4 | Z 5 | Z 6 | B1 | +|----------------|----------------|----------------|----------------|----------------|----------------|----| + +G.991.2\_FE-18a + +▦ Required Z-bits are >7 result in combining the bits to one B-channel + +Diagram of SHDSL payload block ordering with DRR. It shows the hierarchical breakdown of a 48\*(1+i+n\*8) bit payload block into specific channels (TPS-TCa, TPS-TCb) and sub-channels (Signalling, POTS, ISDN BA, Broadband). It further details the Z-bit mapping to DRR, EOC, DSC, and ISDN D16, and illustrates how Z-bits are combined into a B-channel when their count exceeds 7. + +**Figure E.18a/G.991.2 – SHDSL payload block ordering with DRR** + +Figure E.18a shows how to combine the Z-bit time slots if their number exceeds 7. The formula is based on the number of required Z-bits modulo 8. + +## E.11 TPS-TC for PTM transport + +### E.11.1 Packetized data transport + +#### E.11.1.1 Functional model + +The functional mode of packetized data transport is presented in Figure E.19. In the transmit direction, the PTM entity obtains data packets to be transported over SHDSL from the application layer interface. The PTM entity processes each packet and applies it to the $\gamma$ -interface for packetized data transport. The PTM TPS-TC receives the packet from $\gamma$ -interface, encapsulates it into a special frame (PTM-TC frame) and maps it into PMS-TC frame (transmission frame) for transmission over the SHDSL link. + +In the receive direction, the PTM-TC frame extracted from the received PMS-TC frame is directed into the PTM-TC. The PTM-TC recovers the transported packet and delivers it to the PTM entity via the $\gamma$ -interface. + +The PTM path-related OAM data, including information on errored packets, shall be presented to the TPS-TC management entity providing all necessary OAM functions to support the PTM-TC. + +![Functional model of PTM transport diagram](5d4a347586c10e5732b7913c2bc79f2b_img.jpg) + +The diagram illustrates the functional model of PTM transport. At the top, a box labeled 'PTM entity' is connected via a double-headed arrow labeled 'packets' to a central box labeled 'Packet TPS-TC (PTM TPS-TC)'. This connection is separated by a dashed horizontal line labeled ' $\gamma$ -interface'. To the right of the central box, a box labeled 'TPS-TC management' is connected via a double-headed arrow labeled 'OAM data'. Below the central box, three vertical double-headed arrows labeled 'OAM', 'Clock', and 'Data' connect it to a bottom box labeled 'SHDSL PMS-TC and PMD'. This connection is separated by a dashed horizontal line labeled ' $\alpha$ or $\beta$ interface'. The label 'G.991.2\_FE-19' is located at the bottom right of the diagram. + +Functional model of PTM transport diagram + +**Figure E.19/G.991.2 – Functional model of PTM transport** + +The $\gamma$ -interface is described in E.11.3.1. The $\alpha/\beta$ -interfaces are application independent and thus have the same format as for other TPS-TCs (see E.11.3.2). + +### E.11.2 Transport of PTM data + +The bit rates of PTM data transport in the RX and TX direction on the SHDSL link are identical and may be set to any eligible value which is less than (Dual-Bearer application) or equal to the assigned maximum payload bit rate. This bit rate is set during the system configuration. + +The PTM-TC shall provide full transparent data transfer between $\gamma_{STU-C}$ and $\gamma_{STU-R}$ interfaces (except non-correctable errors in the PMD sublayer due to the noise in the loop). The PTM-TC shall provide packet integrity over the assigned bearer channel. + +### E.11.3 Interface description + +#### E.11.3.1 $\gamma$ -Interface + +The $\gamma_C$ and $\gamma_R$ reference points define the interfaces between the PTM entity and the PTM-TC at the STU-C and STU-R, respectively, as shown in Figure E.19. These interfaces are functionally identical and are independent of the contents of the transported packets. The interfaces are defined by the following flows of signals between the PTM entity and the PTM-TC sublayer: + +- data flow; +- synchronization flow; +- control flow; +- OAM flow. + +##### E.11.3.1.1 Data flow + +The data flow shall consist of two contra-directional octet-based streams of packets: transmit packets (Tx\_PTM) and receive packets (Rx\_PTM). The packets transported in either direction over the $\gamma$ -interface may be of variable length. Bits within an octet are labelled $a_1$ through $a_8$ , with $a_1$ being the LSB and $a_8$ being the MSB. If either of data streams is transmitted serially, the first octet of the packet shall be transmitted first and bit $a_1$ of each octet shall be transmitted first as shown in Figure E.21. The Data Flow signal description is presented in Table E.35. + +**Table E.35/G.991.2 – PTM-TC: $\gamma$ -interface data, synchronization and control flows signal summary** + +| Flow | Signal | Description | Direction | +|-------------------------|---------|---------------------------------------------------------------------|--------------| +| Transmit signals | | | | +| Data | Tx_PTM | Transmit Data | PTM → PTM-TC | +| Control | Tx_Enbl | Asserted by PTM-TC, indicates that PTM may push packets to PTM-TC | PTM ← PTM-TC | +| Control | Tx_Err | Errored transmit packet (request to abort) | PTM → PTM-TC | +| Sync | Tx_Avbl | Asserted by the PTM entity if data is available for transmission | PTM → PTM-TC | +| Sync | Tx_Clk | Clock signal asserted by the PTM entity | PTM → PTM-TC | +| Sync | Tx_SoP | Start of the Transmit Packet | PTM → PTM-TC | +| Sync | Tx_EoP | End of the Transmit Packet | PTM → PTM-TC | +| Receive signals | | | | +| Data | Rx_PTM | Receive Data | PTM ← PTM-TC | +| Control | Rx_Enbl | Asserted by PTM-TC, indicates that PTM may pull packets from PTM-TC | PTM ← PTM-TC | +| Control | Rx_Err | Received error signals including FCS error, Invalid frame and OK | PTM ← PTM-TC | +| Sync | Rx_Clk | Clock Signal asserted by PTM entity | PTM → PTM-TC | +| Sync | Rx_SoP | Start of the Receive Packet | PTM ← PTM-TC | +| Sync | Rx_EoP | End of the Receive Packet | PTM ← PTM-TC | + +#### **E.11.3.1.2 Synchronization flow** + +This flow provides synchronization between the PTM entity and the PTM-TC sublayer and contains the necessary timing to provide packet integrity during the transport. The synchronization flow shall consist of the following signals as presented in Table E.35: + +- Transmit and receive timing signals (Tx\_Clk, Rx\_Clk), both asserted by PTM entity. +- Start of packet signals (Tx\_SoP, Rx\_SoP): asserted by PTM entity and by PTM-TC respectively and intended to identify the beginning of the transported packet in the corresponding direction of transmission. +- End of packet signals (Tx\_EoP, Rx\_EoP), asserted by PTM entity and by PTM-TC respectively and intended to identify the end of the transported packet in the corresponding direction of transmission. +- Transmit Packet Available Signal (Tx\_Avbl), asserted by PTM entity to indicate that data for transmission in Tx direction is ready. + +#### **E.11.3.1.3 Control flow** + +Control signals are used to improve robustness of data transport between the PTM entity and the PTM-TC and are presented in Table E.35: + +- Enable Signals (Tx\_Enbl, Rx\_Enbl): asserted by PTM-TC and indicates that data may be respectively sent from PTM entity to PTM-TC or pulled from PTM-TC to PTM entity. +- Transmit Error (Tx\_Err): asserted by PTM entity and indicates that the packet or part of the packet already transported from PTM entity to PTM-TC is errored or undesirable for transmission (abort of transmitted packet). +- Receive Error (Rx\_Err): asserted by PTM-TC to indicate that an errored packet is transported from PTM-TC to PTM entity. + +Handling of packet errors is described in E.11.4.2. + +#### **E.11.3.1.4 OAM flow** + +The OAM Flow across the $\gamma$ -interface exchanges OAM information between the OAM entity and its PTM related TPS-TC management functions. OAM flow is bidirectional. + +The OAM flow primitives are for further study. + +#### **E.11.3.2 $\alpha/\beta$ interface** + +The $\alpha$ and $\beta$ reference points define interfaces between the PTM-TC and PMS-TC at the STU-C and STU-R respectively. Both interfaces are functional, application independent, and should comply with the generic definition for all TPS-TCs as specified in clause 8. + +### **E.11.4 PTM TPS-TC functionality** + +The following PTM TPS-TC functionality should be applied to both Rx and Tx direction. + +#### **E.11.4.1 Packet encapsulation** + +For packet encapsulation an HDLC type mechanism shall be used with detailed characteristics as specified in the following clauses. + +##### **E.11.4.1.1 Frame structure** + +The PTM-TC frame format shall be as shown in Figure E.20. The opening and the closing Flag Sequences shall be set to 7E16. They identify the start and the end of the frame. Only one Flag Sequence is required between two consecutive frames. + +![](0317016f1967843fe2643d09bd7bee9d_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Bits | +|---------------------|---|---|---|---|---|---|---|-----------------------| +| $7E_{16}$ | | | | | | | | Opening flag sequence | +| Default = $FF_{16}$ | | | | | | | | Address field | +| Default = $03_{16}$ | | | | | | | | Control field | +| Data | | | | | | | | Information field | +| FCS-1 | | | | | | | | First octet of FCS | +| FCS-2 | | | | | | | | Second octet of FCS | +| $7E_{16}$ | | | | | | | | Closing flag sequence | + +G.991.2\_FE-20 + +**Figure E.20/G.991.2 – PTM-TC frame format** + +The Address and Control octets are intended for auxiliary information. They shall be set to their default values of hexadecimal $FF_{16}$ and $03_{16}$ respectively if not used. + +NOTE 1 – The address and Control fields may be used for different auxiliary OAM functions. The usage of these fields is for further study. + +The information field shall be filled with the transported packet data. Prior to encapsulation the octets of the data shall be numbered sequentially. Octets shall be transmitted in ascending numerical order. + +The frame check sequence (FCS) octets are used for packet level error monitoring, and shall be set as described in E.11.4.1.3. + +After encapsulation, bits within an octet are labelled $b_1$ through $b_8$ , as defined in Figure E.21. If the $\alpha(\beta)$ interface is serial by implementation, bit $b_8$ of each octet shall be transmitted first. + +NOTE 2 – In keeping with existing labelling convention for the $\alpha(\beta)$ interface, bit $b_8$ (MSB) is transmitted first. The PTM-TC functionality defines a correspondence between $a_1$ and $b_8$ , $a_2$ and $b_7$ , etc., in order to conform to the HDLC convention of transmitting bit $a_1$ first. + +![Diagram of PTM-TC data flow showing the mapping of data octets into an HDLC frame structure between the gamma and alpha(beta) interfaces.](1d9db146e81fd7b66f1a05cce57c7112_img.jpg) + +| | | | | | | | | | +|---------|----------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------| +| Octet # | $a_8$ | $a_7$ | $a_6$ | $a_5$ | $a_4$ | $a_3$ | $a_2$ | $a_1$ | +| Data-1 |
MSBLSB
| | | | | | | | +| Data-2 | | | | | | | | | +| | | | | | | | | | +| Data-N | | | | | | | | | + +$\gamma$ -interface + $a_1$ transmitted +first + +⇅ + +| | | | | | | | | | | +|-----------|------------------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------|-------|-------|-------|-----------------------| +| | $b_1$ | $b_2$ | $b_3$ | $b_4$ | $b_5$ | $b_6$ | $b_7$ | $b_8$ | HDLC
Encapsulation | +| Flag | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | | +| $FF_{16}$ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | | +| $03_{16}$ | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | | +| Data-1 |
a_8a_1
| | | | | | | | | +| Data-2 | | | | | | | | | | +| | | | | | | | | | | +| Data-N | | | | | | | | | | +| FCS-1 |
MSB
FCS
| | | | | | | | | +| FCS-2 |
LSB
FCS
| | | | | | | | | +| Flag | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | | + +$\alpha(\beta)$ -interface + $b_8$ transmitted +first + +↓ + +G.991.2\_FE-21 + +Diagram of PTM-TC data flow showing the mapping of data octets into an HDLC frame structure between the gamma and alpha(beta) interfaces. + +**Figure E.21/G.991.2 – PTM-TC data flow** + +#### E.11.4.1.2 Octet transparency + +To prevent failures due to false frame synchronization, any octet inside the PTM-TC frame that is equal to $7E_{16}$ (the Flag Sequence) or $7D_{16}$ (the Control Escape) shall be escaped as described below. + +After FCS computation, the transmitter examines the entire frame between the opening and the closing Flag Sequences. Any data octets which are equal to Flag Sequence or the Control Escape shall be replaced by a two-octet sequence consisting of the Control Escape octet followed by the original octet exclusive-OR'ed with $20_{16}$ . In summary, the following substitutions shall be made. + +- Any data octet of $7E_{16}$ – encoded as two octets $7D_{16}$ , $5E_{16}$ . +- Any data octet of $7D_{16}$ – encoded as two octets $7D_{16}$ , $5D_{16}$ . + +On reception, prior to FCS computation, each Control Escape octet shall be removed and the following octet shall be exclusive OR'ed with $20_{16}$ (unless the following octet is $7E_{16}$ which is the flag and indicates the end of the frame, and therefore an abort has occurred). In summary, the following substitutions are made: + +- any sequence of $7D_{16}$ , $5E_{16}$ – replaced by the data octet $7E_{16}$ . +- any sequence of $7D_{16}$ , $5D_{16}$ – replaced by the data octet $7D_{16}$ . +- a sequence of $7D_{16}$ , $7E_{16}$ aborts the frame. + +NOTE – Since octet stuffing is used, the PTM-TC frame is guaranteed to have an integer number of octets. + +#### E.11.4.1.3 Frame check sequence + +The FCS shall be calculated over all bits of the address, control, and information fields of the PTM-TC frame as defined in ISO/IEC 13239 [B13], i.e., it shall be the one's complement of the sum (modulo 2) of: + +- 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 opening flag and the first bit of the FCS, excluding octets inserted for transparency (E.11.4.1.2); and +- 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 opening flag and the first bit of the FCS, excluding octets inserted for transparency. + +The FCS is 16 bits (2 octets) in length and occupies fields FCS-1, FCS-2 of the PTM-TC frame. The FCS shall be mapped into the frame so that bit $a_1$ ( $b_8$ ) of FCS-1 shall be the MSB of the calculated FCS, and bit $a_8$ ( $b_1$ ) of the FCS-2 shall be the LSB of the calculated FCS (Figure E.21). + +The register used to calculate the FCS at the transmitter shall be initialized to the value $FFFF_{16}$ . + +NOTE – 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 ONEs and is then modified by division by the generator polynomial, as described above, 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 ONEs. The final remainder, after multiplication by $x^{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. + +#### E.11.4.2 Packet error monitoring + +Packet error monitoring includes detection of invalid and errored frames at receive side. + +##### E.11.4.2.1 Invalid frames + +The following conditions result in an invalid frame: + +- Frames which are less than 4 octets in between flags not including transparency octets (Flag Sequence and Control Escape). These frames shall be discarded. +- Frames which contain a Control Escape octet followed immediately by a Flag (i.e., $7D_{16}$ followed by $7E_{16}$ ). These frames shall be passed across the $\gamma$ -interface to the PTM entity. +- Frames which contain control escape sequences other than $7D_{16}$ , $5E_{16}$ and $7D_{16}$ , $5D_{16}$ . These frames shall be passed across the $\gamma$ -interface to the PTM entity. + +All invalid frames shall not be counted as FCS errors. The receiver shall immediately start looking for the opening flag of a subsequent frame upon detection of an invalid frame. A corresponding receive error message (Rx\_Err – E.11.3.1.3) shall be sent across the $\gamma$ -interface to the PTM entity. + +##### E.11.4.2.2 Errored frames + +A received frame shall be qualified as an errored frame (FCS-errored) if the CRC calculation result for this frame is different from the one described in E.11.4.1.3. Errored frames shall be passed across the $\gamma$ -Interface. A corresponding receive error message (Rx\_Err – E.11.3.1.3) shall be sent across the $\gamma$ -interface to the PTM entity. + +#### E.11.4.3 Data rate decoupling + +Data rate decoupling is accomplished by filling the time gaps between transmitted PTM-TC frames with additional Flag Sequences ( $7E_{16}$ ). Additional Flag Sequences shall be inserted at the transmit side between the closing Flag Sequence of the last transmitted PTM-TC frame and the subsequent opening Flag Sequence of the next PTM-TC frame, and discarded at the receive side respectively. + +#### E.11.4.4 Frame delineation + +The PTM-TC frames should be delineated by detecting of Flag Sequence. The incoming stream is examined on an octet-by-octet basis for the value $7E_{16}$ . Two (or more) consecutive flag sequences constitute an empty frame (frames), which shall be discarded, and not counted as a FCS error. + +#### E.11.4.5 Mapping to the SHDSL framing + +The PMS-TC provides a clear channel to the PTM-TC and packets are mapped into the SHDSL payload on a byte-by-byte basis. At the STU-C, packets are mapped across the logical $\alpha$ interface while at the STU-R, packets cross the logical $\beta$ interface. At the alpha and beta interface, logical data and clock lines are present. Packet alignment to the SHDSL frame is optional. The provided bandwidth by the PMS-TC is $k_s = i + n \times 8$ with $0 \leq i < 7$ and $3 \leq n \leq 36$ . For $n = 36$ , $i$ is restricted to values of 0 and 1. Note that optional extensions described in Annex F allow values of $n$ up to 89. + +In the optional $M$ -pair mode, PTM data is carried over all pairs using interleaving, as described in 8.2. In $M$ -pair mode only multiples of $M$ time slots may be supported. Each Payload Sub-Block is treated as containing $M \times n$ 8-bit time slots. Each byte from the input PTM data stream is mapped MSB-first into the next available time slot. The first time slot begins at the first bit position within the Payload Sub-Block, followed by time slot 2, time slot 3, ..., time slot $n$ . A total of $M \times k_s$ bits (or $M \times n$ bytes) of contiguous data shall be contained within each Sub-Block, as specified in 8.1, where $k_s = i + n \times 8$ , and, in this mode, $i = 0$ and $3 \leq n \leq 36$ . Note that optional extensions described in Annex F allow values of $n$ up to 89. The bytes from the input PTM data stream shall be interleaved among all $M$ pairs, such, where byte $b_k$ is carried on Pair 1, byte $b_{k+1}$ is carried in the corresponding time slot on Pair 2, etc. Byte $b_{k+M-1}$ is carried in the corresponding time slot on Pair $M$ . + +#### E.12 TPS-TC for STM with a Dedicated Signalling Channel (DSC) + +In certain STM applications, including some channelized voice and data applications, a dedicated channel is desired to carry higher-layer telephony signalling for the STM time slots (e.g., per Telcordia GR-303 [B14] or ETSI V5 [9] and [B16]). This TPS-TC defines a transport format for channelized STM with a Dedicated Signalling Channel (DSC). + +Figure E.22 shows the alignment of STM time slots and the DSC within the SHDSL frame. Each Payload Sub-Block contains a DSC ( $i$ bits in length, where $1 \leq i \leq 7$ ), followed by $n$ 8-bit time slots referred to as $TS_1 \dots TS_n$ . Note that the details of the protocols used over the DSC are beyond the scope of this Recommendation. + +![Diagram of STM framing with a dedicated signalling channel. It shows a hierarchical breakdown from a frame level to sub-block bit level.](25b2ef5bcf30bfa9a31d59f48fddb3a7_img.jpg) + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + +Payload data, bits 1 to $k_s$ + +| | | | | | +|----------|-----------------|-----------------|-----|-----------------| +| DSC | TS 1 | TS 2 | ... | TS n | +| i | 8 | 8 | | 8 | +| bits | bits | bits | | bits | + +G.991.2\_FE-22 + +Diagram of STM framing with a dedicated signalling channel. It shows a hierarchical breakdown from a frame level to sub-block bit level. + +**Figure E.22/G.991.2 – STM framing with a dedicated signalling channel** + +In the optional $M$ -pair mode, both the STM and the DSC are carried over all $M$ pairs using interleaving, as described in 8.2. A total of $M \times n$ time slots shall be transported per SHDSL Payload Sub-Block. The STM time slots shall be interleaved among all $M$ wire pairs, such that pair $m$ carries the $m$ th time slot out of every block of $M$ time slots. The DSC is interleaved among the $M$ pairs such that it occupies the first $i$ bit positions within each Payload Sub-Block on each of the $M$ wire pairs. $i$ may take any value in the range $1 \leq i \leq 7$ , so a total of $M \times i$ bits make up the DSC. $i$ bits of contiguous DSC data shall be contained within a Sub-Block on Pair 1, and the following sets of $i$ bits of contiguous DSC data shall be contained within the corresponding Sub-Blocks of subsequent pairs. See Figure E.23 for additional details. + +![Diagram of M-pair STM framing with a dedicated signalling channel for M=2 and i=1. It shows the frame structure with sync, OH, payload blocks, and Stb. Below, sub-blocks 1-12 are shown. Pair 1 and Pair 2 time slots are detailed, with DSC (1 bit), TS (8 bits), and payload data (bits 1 to k_s-1 and k_s to 2k_s-1).](33d95af6c9ade7cf0415756cc5ea9803_img.jpg) + +Aligned Pair 1 and Pair 2 frames + +| | | | | | | | | | | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| +| Frame sync | OH | Payload block | OH | Payload block | OH | Payload block | OH | Payload block | Stb | +|------------|----|---------------|----|---------------|----|---------------|----|---------------|-----| + +Pair 1 and Pair 2 + +| | | | | | | | | | | | | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| +| Sub-Block 1 | Sub-Block 2 | Sub-Block 3 | Sub-Block 4 | Sub-Block 5 | Sub-Block 6 | Sub-Block 7 | Sub-Block 8 | Sub-Block 9 | Sub-Block 10 | Sub-Block 11 | Sub-Block 12 | +|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|--------------|--------------|--------------| + +Payload data, bits 1 to $k_s-1$ + +Pair 1 + +| | | | | | +|------------------|-----------------|-----------------|-----|--------------------| +| DSC 1 | TS 1 | TS 3 | ... | TS 2n-1 | +|------------------|-----------------|-----------------|-----|--------------------| + +Payload Data, Bits $k_s$ to $2k_s-1$ + +Pair 2 + +| | | | | | +|------------------|-----------------|-----------------|-----|------------------| +| DSC 2 | TS 2 | TS 4 | ... | TS 2n | +|------------------|-----------------|-----------------|-----|------------------| + +1 8 8 8 bits bits bits bits + +G.991.2\_FE-23 + +Diagram of M-pair STM framing with a dedicated signalling channel for M=2 and i=1. It shows the frame structure with sync, OH, payload blocks, and Stb. Below, sub-blocks 1-12 are shown. Pair 1 and Pair 2 time slots are detailed, with DSC (1 bit), TS (8 bits), and payload data (bits 1 to k\_s-1 and k\_s to 2k\_s-1). + +**Figure E.23/G.991.2 – $M$ -pair STM framing with a dedicated signalling channel +(for the case where $M = 2$ and $i = 1$ )** + +### E.13 TPS-TC for LAPV5 enveloped POTS or ISDN + +The mapping and time slot allocation of STM based, LAPV5 controlled, PSTN and ISDN-BA transport is specified, which is for ISDN an alternative procedure to the simple use of D-channel messages as described in E.8. It is not expected that the TPS-TC described in this clause will be used simultaneously with the ISDN transport described in E.8 or the POTS transport described in E.13. + +This clause describes the transport of POTS and ISDN over a combination of the SHDSL EOC, Z-channels, and B-channels. Control and signalling information is transported over either the EOC, Z, or first B-channels using frame-based V5 wrappings. The POTS voice and ISDN B-channels are transported over STM based pre-assigned SHDSL B-channels. + +#### E.13.1 Signalling channel + +Signalling as well as the other POTS or ISDN related messages are transported over a common signalling channel. Depending on the required amount of signalling and port control information, either a portion of the SHDSL EOC or a portion of the payload sub-block may be used for this signalling transport. If the SHDSL EOC is used for the signalling transport, then the V5 signalling messages are wrapped using SHDSL EOC Message IDs. If the SHDSL EOC is not used for this transport, then within the SHDSL frame, the signalling bits are either mapped into 1 to 7 Z-channel(s), or are mapped into the first B-channel time slot of each sub-block. + +In order to transport signalling information, the STU-C and STU-R must agree on the particular signalling channel to be used. The signalling channel is identified using parameter ( $N_{\text{sig}}$ ) with a range of 0 to 8 plus the value 16. The value 0 indicates that the signalling is on the SHDSL EOC. The values 1 through 7 indicate that there are 1 through 7 Z-channel bits present and that the signalling is to be transported there. A value of 8/16 indicates that the signalling is transported in the first one/two B-channel time slots of each sub-block. Other values of $N_{\text{sig}}$ , such as 24 and 32, are for future study. + +### E.13.2 Mapping of 64 kbit/s payload channels + +One or multiple 64 kbit/s POTS voice channels and/or one or multiple ISDN B-channel pairs are mapped onto B-channels in the SHDSL sub-frame. The POTS channels are mapped sequentially into the first B-channels of each sub-frame after any signalling B-channels. The ISDN B-channel pairs are mapped into the first B-channels of each sub-frame after any signalling or POTS B-channels. These mappings are similar to those in E.8 and E.12. + +In order to transport payload information, both the STU-C and STU-R have to agree as to how many POTS and ISDN BA circuits to allocate B-channels for. The number of channels shall be the same for both directions. The number of POTS circuits shall be specified as an integer ( $N_{\text{pots}}$ ) with a range of 0 to 35. The number of ISDN circuits shall be specified as an integer ( $N_{\text{isdn}}$ ) with a range of 0 to 17. (Other values are for future study.) + +The total number of B-channels consumed for the control and payload transport is (1 or 2 if $N_{\text{sig}} = 8$ or 16, else 0) + $N_{\text{pots}}$ + (2 × $N_{\text{isdn}}$ ). The remaining B-channels are available for the underlying application. + +### E.13.3 Signalling and port control + +In the case where the common signalling channel is carried over the SHDSL EOC, (that is $N_{\text{sig}} = 0$ ), the TPS-TC is addressed by the ISDN Message IDs within the EOC (IDs 20 and 148, see 9.5.5.6). Octet 2 is not used and octets 3 through $n$ contain the LAPV5 message. The message content is enveloped by LAPV5-EF. Envelope functions and message contents are specified in ETSI EN 300 324-1 [9] and ETSI EG 201 900-1 [10]. See Tables E.36 and E.37 for details. + +**Table E.36/G.991.2 – ISDN Request – Message ID 20** + +| Octet # | Contents | Data type | Reference | +|----------|--------------------|------------|-----------| +| 1 | 20 | Message ID | | +| 2 | Not used | | | +| 3 to $n$ | LAPV5 message code | | | + +**Table E.37/G.991.2 – ISDN Response – Message ID 148** + +| Octet # | Contents | Data type | Reference | +|----------|--------------------|------------|-----------| +| 1 | 148 | Message ID | | +| 2 | Not used | | | +| 3 to $n$ | LAPV5 message code | | | + +In ETSI EN 300 324-1 [9] clause 9.1.5, the maximum frame size is specified as 533 octets. In the SHDSL EOC, the limit is 75 octets. Applications which require control and signalling frames larger than 76 octets should choose $N_{\text{sig}} > 0$ . + +In the case where the common signalling channel is carried over the Z- or B-channel, (that is $N_{sig} > 0$ ), the message format is as specified in ETSI EN 300 324-1 [9], clause 9. This mode shall use all of clause 9, including subclauses for the flag sequence, interframe fill time, transparency, frame check sequence, format conversion, and invalid frames which are not used in the EOC mode above. + +#### E.13.4 Protocol architecture for LAPV5 enveloped POTS and ISDN + +Table E.38 shows the layered structure for LAPV5 enveloped POTS and ISDN services. Note that the left lower column is for EOC signalling transport and the right lower column is for Z- or B-channel signalling transport. + +**Table E.38/G.991.2 – Protocol architecture** + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------|--|--| +| POTS signalling
ETSI EN 300 324-1 [9],
clause 13 | POTS/ISDN port control
ETSI EN 300 324-1 [9],
clause 14 | ISDN signalling | | | +| LAPV5-DL
ETSI EN 300 324-1 [9], clause 10 | | LAPD | | | +| | | | | | +| LAPV5-EF address
ETSI EN 300 324-1 [9], clause 9.1.4 | LAPV5-EF
ETSI EN 300 324-1 [9], clause 9 | | | | +| TPS-TC
Message ID: LAPV5 enveloped POTS and ISDN | Signalling Z- or B-channels | | | | +| PMD-TC, PMS-TC | | | | | +| NOTE – The ISDN signalling (LAPD and layer 3) is part of the ISDN-TE functionality and outside the scope of this Recommendation. | | | | | + +The LAPV5-EF envelope address (ETSI EN 300 324-1 [9], clause 9) envelopes the frames for signalling of an individual ISDN access, or for POTS signalling or for POTS/ISDN port control. + +For the reliable transport of POTS signalling and POTS/ISDN port control messages, the data link protocol LAPV5-DL is used which is a simplified version of LAPD. The LAPV5-DL protocol is specified as in ETSI EN 300 324-1 [9], clause 10. + +As in ETSI EG 201 900-1 [10] (Loop Emulation Service using AAL2), the following differences with respect to ETSI EN 300 324-1 [9] exist: + +- Only one common instance of LAPV5-DL is used for both the POTS signalling and the POTS/ISDN port control. +- The LAPV5-DL address takes the value of all zeros. +- POTS signalling messages and POTS/ISDN port control messages are distinguished by means of the Message type information element. +- A common error handling procedure for "unrecognized message type" errors is used for both the PSTN and Control protocol: Whenever an unrecognized message is received, the protocol entity shall generate an internal error indication and ignore the message. +- ISDN signalling is conveyed via frame relay as described in ETSI EN 300 324-1 [9], clause 11. This means that the customer's D-channel data link layer protocol is not fully terminated. + +NOTE – The existing TPS-TC for ISDN as described in E.8 remains unchanged. It provides a lean alternative for networks where no POTS, but only ISDN is provided. + +### E.13.5 System procedures + +#### E.13.5.1 System start-up + +With regard to the remainder of this subclause, actions required for any items that are not provisioned shall be ignored. + +NOTE – The procedures are derived from 5.4.4.1 and 5.4.4.2 of af-vmoa-0145.000 [B15]. + +##### E.13.5.1.1 Preconditions + +The initial states of the various Finite State Machines (FSM) involved in the start-up are as follows: + +**Table E.39/G.991.2 – Initial states of finite state machines** + +| FSM | Initial state | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| +| Port Control Protocol FSM | Out of Service (AN0/LE0) | +| PSTN Port Status FSM | Blocked (AN1.0/LE1.0) | +| ISDN BA Port Status FSM | Blocked (AN1.0/LE1.0) | +| PSTN Protocol FSM | Port Blocked (AN6/LE6) | +| NOTE – These FSMs are defined in the V5 specifications ETSI EN 300 324-1 [9]. The "LE" states relate to the STU-C side and the "AN" states relate to the STU-R side of the connection. | | + +##### E.13.5.1.2 Normal procedure + +- Activation of LAPV5-DL: MDL-Establish-Request shall be sent to the LAPV5-DL. +- When MDL-ESTABLISH-CONFIRM or MDL-ESTABLISH-INDICATION is received from the LAPV5-DL, START-TRAFFIC shall be sent to the port control protocol FSMs. +- Entering the normal state. +- Post-processing: The STU-C side shall initiate the coordinated unblock procedure for all relevant user ports. The STU-R side shall not initiate unblocking at this time. + +##### E.13.5.1.3 Exceptional procedures in case of failure in system start-up + +When the system start-up cannot be continued for some reason (e.g., LAPV5-DL failure) and is unable to enter the normal state, system restart shall be performed. + +#### E.13.5.2 System restart + +System restart refers to the re-starting of a single LAPV5-DL protocol instance between a STU-C side and a STU-R side. Under system restart the following actions apply: + +- The interface shall be brought into a state in which no established LAPV5-DL exists. + +NOTE 1 – The remote side takes this as a trigger for system restart. + +- Timer TL1 shall be started. +- On expiry of TL1 system start-up shall be performed. + +Timer TL1 shall have a predefined value of 20 seconds. + +NOTE 2 – Timer TL1 triggers system start-up. It is needed to guarantee that the release of the LAPV5-DL is recognized at the remote side and hence both the STU-R side and STU-C side undergo system start-up. This timer is started when the system has been stopped for any reason during the system start-up or normal operation. It shall also be run prior to invoking the system start-up when performing a cold start. + +Situations where system restart shall be applied: + +- Reception of Release-Indication of LAPV5-DL. +- Under request by the Management System. + +### E.13.6 $N_{\text{sig}}$ , $N_{\text{pot}}$ and $N_{\text{isdn}}$ + +In order to support interoperability, the STU-C and STU-R need to agree on the values of the parameters $N_{\text{sig}}$ , $N_{\text{pot}}$ and $N_{\text{isdn}}$ . This agreement may be by prior agreement outside the scope of this annex. + +Alternatively, the STU-C may configure the STU-R via the SHDSL EOC. To support this, there is a Message ID for LAPV5 POTS and ISDN Set-up. The purpose is to specify the values for $N_{\text{sig}}$ , $N_{\text{pot}}$ and $N_{\text{isdn}}$ . The Message ID 21 is the Request from the STU-C to the STU-R and Message ID 149 is the Response from the STU-R to the STU-C. See Tables E.40 and E.41 for details. + +The request message allows the STU-C to configure the STU-R with the values of $N_{\text{sig}}$ , $N_{\text{pot}}$ and $N_{\text{isdn}}$ . The response message is an acknowledge from the STU-R to STU-C. If octets 2, 3, and 4 of the response match those in the request, then the response indicates that the STU-R accepts the values sent by the STU-C. If the STU-R does not accept the values proposed by the STU-C, it may respond with the octets 2, 3, and/or 4 modified to contain an acceptable value and also the MSB of each octet in question set. The STU-R should respond to a request within 500 ms. In the event that the STU-R does not respond, the STU-C will try at least three times before concluding that the option cannot be supported. + +**Table E.40/G.991.2 – LAPV5 POTS and ISDN Set-up Request – Message ID 21** + +| Octet # | Contents | Data type | Note | +|---------|-------------------|---------------|------| +| 1 | 21 | Message ID | | +| 2 | $N_{\text{sig}}$ | Unsigned char | | +| 3 | $N_{\text{pot}}$ | Unsigned char | | +| 4 | $N_{\text{isdn}}$ | Unsigned char | | + +**Table E.41/G.991.2 – LAPV5 POTS and ISDN Set-up Response – Message ID 149** + +| Octet # | Contents | Data type | Note | +|---------|-------------------|---------------|------| +| 1 | 149 | Message ID | | +| 2 | $N_{\text{sig}}$ | Unsigned char | | +| 3 | $N_{\text{pot}}$ | Unsigned char | | +| 4 | $N_{\text{isdn}}$ | Unsigned char | | + +## Annex F + +### Region 1 requirements for payload data rates up to 5696 kbit/s + +#### F.1 Scope + +The clauses in this annex provide the additions and modifications to the corresponding clauses in the main body and Annex A for payload data rates up to 5696 kbit/s. Support for this annex is optional. + +NOTE – Some countries have standards for spectrum management requirements that limit the length of the lines for transmission of certain signal levels in this annex, for example Spectrum Management Standard T1.417 applies in the United States access network. + +## F.2 Data rate + +The operation of the STU in data mode at the specified information rate shall be as specified in Table F.1. + +**Table F.1/G.991.2 – Framed data mode rates** + +| Payload data rate, $R$ (kbit/s) | Modulation | Symbol rate (ksymbol/s) | $K$ (Bits per symbol) | +|----------------------------------|------------|-------------------------|-----------------------| +| $R = n \times 64 + (i) \times 8$ | 16-TCPAM | $(R + 8) \div 3$ | 3 | +| $R = n \times 64 + (i) \times 8$ | 32-TCPAM | $(R + 8) \div 4$ | 4 | + +As specified in the main body (per clause 5, reiterated in 7.1.1, 8.1 and 8.2), the allowed single-pair rates are given by $n \times 64 + i \times 8$ kbit/s, where $3 \leq n \leq 36$ and $0 \leq i \leq 7$ . In these clauses, the allowed values $i$ are further restricted to 0 or 1 for $n = 36$ . These definitions correspond to (payload) data rates from 192 kbit/s to 2.312 Mbit/s in increments of 8 kbit/s. + +This annex extends those rates. It is applicable for single-pair rates given by $n \times 64 + i \times 8$ kbit/s. For 16-TCPAM, $36 \leq n \leq 60$ and $0 \leq i \leq 7$ . For 16-TCPAM and $n = 36$ , the applicable values of $i$ are $2 \leq i \leq 7$ . For 16-TCPAM and $n = 60$ , the applicable value of $i$ is 0. This corresponds to (payload) data rates from 2320 kbit/s to 3840 kbit/s in increments of 8 kbit/s for 16-TCPAM. For 32-TCPAM, $12 \leq n \leq 89$ and $0 \leq i \leq 7$ . For 32-TCPAM and $n = 89$ , the applicable value of $i$ is 0. This corresponds to (payload) data rates from 768 kbit/s to 5696 kbit/s in increments of 8 kbit/s for 32-TCPAM. + +This annex is also applicable for optional operation on more than one pair ( $M$ -pair mode). + +### F.2.1 Support for multiple encodings + +Support for the data rates specified in this annex is optional, and, as such, an STU supporting this annex is not required to support all specified data rates. For each rate that an STU-R supports, it shall support all available encodings (i.e., both 16- and 32-TCPAM for rates where both encodings are specified). Support for multiple encodings is optional at the STU-C. + +### F.2.2 G.994.1 Pre-activation sequence + +As specified in 6.4, ITU-T Rec. G.994.1 is used to begin the pre-activation sequence. + +To support a wide range of data rates and multiple encodings, this clause introduces a new way to encode data rates in G.994.1 code points. This method of encoding rates is used for both the PMMS rates and the training rates. Data rates are encoded as a set of ranges, where each range is expressed as a 3-tuple (minimum, maximum, step). The 3-tuple represents all rates of the form $(m + k \times s) \times (64 \text{ kbit/s})$ where $m$ is the minimum value, $s$ is the step value, and $k$ is the set of all integers greater than or equal to zero such that $m + k \times s$ is less than or equal to the maximum value. Thus, for example, the 3-tuple (40, 70, 10) represents the rates $40 \times 64 \text{ kbit/s}$ , $50 \times 64 \text{ kbit/s}$ , $60 \times 64 \text{ kbit/s}$ , and $70 \times 64 \text{ kbit/s}$ . + +Each data rate parameter in this annex can be expressed as a set of between 1 to 8 ranges, where the supported rates are the union of those supported by the individual ranges. Thus, for example, the 3-tuples (20, 30, 4), (40, 70, 10) represent the rates $20 \times 64$ kbit/s, $24 \times 64$ kbit/s, $28 \times 64$ kbit/s, $40 \times 64$ kbit/s, $50 \times 64$ kbit/s, $60 \times 64$ kbit/s, and $70 \times 64$ kbit/s. If all bits of the extended base data rate minimum and maximum are set to zero, then those rates are not supported for line probe. If only one range of rates is required, then only the octets associated with (min1, max1, step1) shall be sent. + +Also, in many cases, the values in the data range 3-tuple can be less than or equal to 89 (representing the maximum payload data rate of 5696 supported in this annex). When using G.994.1 code point representation, only 6 bits are available for the value of an NPar(3). To support numbers greater than 63, the value must be split across multiple octets. When encoding a data range using G.994.1, 4 octets are used, where the first octet contains the highest order bit from each of the values in the 3-tuple. This is illustrated in Table 11.16.10/G.994.1. + +The complete set of rate capabilities shall be the union of the extended rates specified in Annex F (G.994.1 Table 11.16.0.1 bits 4-6 and Table 11.16.0.2 bits 1-3) with the non-extended rates specified in Annex A (G.994.1 Table 11.16 bits 1-4). + +Ranges of rates may overlap and may contain some rates which are identical. For example, the 3-tuples (40, 60, 10) and (50, 70, 5) would be a valid set of ranges. In this case, the union of these two 3-tuples would be the rates $40 \times 64$ kbit/s, $50 \times 64$ kbit/s, $55 \times 64$ kbit/s, $60 \times 64$ kbit/s, $65 \times 64$ kbit/s, and $70 \times 64$ kbit/s. Note that, for PMMS, if two ranges contain some rates which are identical, the probe waveforms associated with these identical rates are only sent once. + +The following definition is added to the G.994.1 code point definitions in 6.4.1 for the support of the extended data rates specified in this annex. + +**Extended Base Data Rate:** These octets are used to specify payload rates for this annex, as follows: + +- The PMMS octets indicate rates for line probing segments. Note that while PMMS uses 2-PAM modulation, the PMMS symbol rates are specified assuming 32 TCPAM encoding, so the PMMS symbol rate (in ksymbols/s) would be equal to the (payload data rate (kbit/s) + 8 kbit/s)/4. If both symmetric and asymmetric PSDs are indicated, then all of the indicated symmetric PSDs shall be sent first, followed by all of the indicated asymmetric PSDs. Valid values for min and max shall be between 49 and 89, inclusive, and valid values for step shall be between 1 and 40, inclusive. The variables j5 and j6 associated with the PMMS rates shall be independent, and shall range from 1 to 8, inclusive. If only one range of rates is required, then only the octets associated with (min1, max1, step1) shall be sent. +- The training parameter octets indicate extended payload data rates supported. +- In CLR, upstream training parameters indicate which data mode rates the STU-R is capable of transmitting and downstream training parameters indicate which data mode rates the STU-R is capable of receiving. If the optional line probe is used, the receiver training parameters will be further limited by the probe results. Valid values for minimum and maximum shall be between 36 and 60, inclusive, for 16-TCPAM and between 12 and 89, inclusive, for 32-TCPAM. Valid values for step shall be between 1 and 89, inclusive. The variables j1, j2, j3 and j4 associated with the training rates shall be independent, and shall range from 1 to 8, inclusive. The STU-R shall indicate support for both 16- and 32-TCPAM for all supported rates for which both encodings are defined in this annex. + +- In CL, downstream training parameters indicate which data mode rates the STU-C is capable of transmitting and upstream training parameters indicate which data mode rates the STU-C is capable of receiving. Valid values for minimum and maximum shall be between 36 and 60, inclusive, for 16-TCPAM and between 12 and 89, inclusive, for 32-TCPAM. Valid values for step shall be between 1 and 89, inclusive. The variables j1, j2, j3 and j4 associated with the training rates shall be independent, and shall range from 1 to 8, inclusive. If optional line probe is used, the receiver training parameters will be further limited by the probe results. +- Data rate selections shall be specified in MP and MS messages by setting the maximum and minimum rates to the same value. + +### F.3 Mapper + +The $K + 1$ bits $Y_K(m)$ , ..., $Y_1(m)$ , and $Y_0(m)$ shall be mapped to a level $x(m)$ . In 6.1.2.3, the mapper function is specified for 16-TCPAM. This annex extends that mapping to include both 16- and 32-TCPAM encodings. Table F.2 shows the bit to level mapping for 16- and 32-level mapping. + +**Table F.2/G.991.2 – Mapping of bits to PAM levels** + +| $Y_4(m)$ | $Y_3(m)$ | $Y_2(m)$ | $Y_1(m)$ | $Y_0(m)$ | 32-PAM (5 bits) | 16-PAM (4 bits) | +|----------|----------|----------|----------|----------|-----------------|-----------------| +| 0 | 0 | 0 | 0 | 0 | -31/32 | -15/16 | +| 0 | 0 | 0 | 0 | 1 | -29/32 | -13/16 | +| 0 | 0 | 0 | 1 | 0 | -27/32 | -11/16 | +| 0 | 0 | 0 | 1 | 1 | -25/32 | -9/16 | +| 0 | 0 | 1 | 0 | 0 | -23/32 | -7/16 | +| 0 | 0 | 1 | 0 | 1 | -21/32 | -5/16 | +| 0 | 0 | 1 | 1 | 0 | -19/32 | -3/16 | +| 0 | 0 | 1 | 1 | 1 | -17/32 | -1/16 | +| 0 | 1 | 1 | 0 | 0 | -15/32 | 1/16 | +| 0 | 1 | 1 | 0 | 1 | -13/32 | 3/16 | +| 0 | 1 | 1 | 1 | 0 | -11/32 | 5/16 | +| 0 | 1 | 1 | 1 | 1 | -9/32 | 7/16 | +| 0 | 1 | 0 | 0 | 0 | -7/32 | 9/16 | +| 0 | 1 | 0 | 0 | 1 | -5/32 | 11/16 | +| 0 | 1 | 0 | 1 | 0 | -3/32 | 13/16 | +| 0 | 1 | 0 | 1 | 1 | -1/32 | 15/16 | +| 1 | 1 | 0 | 0 | 0 | 1/32 | – | +| 1 | 1 | 0 | 0 | 1 | 3/32 | – | +| 1 | 1 | 0 | 1 | 0 | 5/32 | – | +| 1 | 1 | 0 | 1 | 1 | 7/32 | – | +| 1 | 1 | 1 | 0 | 0 | 9/32 | – | +| 1 | 1 | 1 | 0 | 1 | 11/32 | – | +| 1 | 1 | 1 | 1 | 0 | 13/32 | – | +| 1 | 1 | 1 | 1 | 1 | 15/32 | – | +| 1 | 0 | 1 | 0 | 0 | 17/32 | – | +| 1 | 0 | 1 | 0 | 1 | 19/32 | – | + +**Table F.2/G.991.2 – Mapping of bits to PAM levels** + +| Y4(m) | Y3(m) | Y2(m) | Y1(m) | Y0(m) | 32-PAM (5 bits) | 16-PAM (4 bits) | +|-------------------------|-------------------------|-------------------------|-------------------------|-------------------------|------------------------|------------------------| +| 1 | 0 | 1 | 1 | 0 | 21/32 | – | +| 1 | 0 | 1 | 1 | 1 | 23/32 | – | +| 1 | 0 | 0 | 0 | 0 | 25/32 | – | +| 1 | 0 | 0 | 0 | 1 | 27/32 | – | +| 1 | 0 | 0 | 1 | 0 | 29/32 | – | +| 1 | 0 | 0 | 1 | 1 | 31/32 | – | + +**F.4 PSD masks** + +For symmetric PSDs using 16-TCPAM payload data rates greater than or equal to 2320 kbit/s, and for symmetric PSDs using 32-TCPAM payload data rates greater than or equal to 768 kbit/s, the measured transmit PSD of each STU shall not exceed the PSD masks specified in this clause (*PSDMASKSHDSL(f)*), and the measured total power into 135 Ω shall fall within the range specified in this clause (*PSHDSL ± 0.5 dB*). + +The inband PSD for 0 < f < 2.0 MHz shall be measured with a 10 kHz resolution bandwidth. + +NOTE 1 – Large PSD variations over narrow frequency intervals (for example near the junction of the main lobe with the noise floor) might require a smaller resolution bandwidth (RBW) to be used. A good rule of thumb is to choose RBW such that there is no more than 1 dB change in the signal PSD across the RBW. + +For all values of framed data rate available in the STU, the following set of PSD masks (*PSDMASKSHDSL(f)*) shall be selectable: + +$$\text{PSDMASK}_{\text{SHDSL}}(f) = \begin{cases} 10^{\frac{-PBO}{10}} \times \frac{K_{\text{SHDSL}}}{135} \times \frac{1}{f_{\text{sym}}} \times \frac{\left[ \sin\left(\frac{\pi f}{N f_{\text{sym}}}\right) \right]^2}{\left(\frac{\pi f}{N f_{\text{sym}}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3\text{dB}}}\right)^{2 \times \text{Order}}} \times 10^{\frac{\text{MaskedOffsetdB}(f)}{10}} \text{ W/Hz}, & f < f_{\text{int}} \\ -90 \text{ dBm/Hz peak, with max power in the } [f, f + 1 \text{ MHz}] \text{ window of } [10 \log_{10} (0.5683 \times 10^{-4} \times f^{-1.5}) + 90] \text{ dBm}, & f_{\text{int}} \leq f \leq 3.184 \text{ MHz} \\ -90 \text{ dBm/Hz peak, with max power in the } [f, f + 1 \text{ MHz}] \text{ window of } -50 \text{ dBm}, & 3.184 \text{ MHz} \leq f \leq 12 \text{ MHz} \end{cases}$$ + +where *MaskedOffsetdB(f)* is defined as: + +$$\text{MaskedOffsetdB}(f) = \begin{cases} 1 + 0.4 \times \frac{f_{3\text{dB}} - f}{f_{3\text{dB}}}, & f < f_{3\text{dB}} \\ 1 \text{ dB}, & f \geq f_{3\text{dB}} \end{cases}$$ + +*fint* is the frequency where the two functions governing *PSDMASKSHDSL(f)* intersect in the range 0 to *fsym*. *PBO* is the power backoff value in dB. *KSHDSL*, *Order*, *N*, *fsym*, *f3dB*, and *PSHDSL* are defined in Table F.3. *PSHDSL* is the range of power in the transmit PSD with 0 dB power backoff. *R* is the payload bit rate. The variables *f*, *fsym*, *fint*, and *f3dB* in the equations are in units of Hz. + +**Table F.3/G.991.2 (Part 1) – Symmetric PSD parameters, 16-TCPAM** + +| Payload bit rate, $R$ (kbit/s) | $K_{SHDSL}$ | Order | $N$ | $f_{sym}$ (ksymbol/s) | $f_{3dB}$ | $P_{SHDSL}$ (dBm) | +|--------------------------------|-------------|-------|-----|-----------------------|------------------------|-------------------| +| $2320 \leq R \leq 3840$ | 7.86 | 6 | 1 | $(R + 8)/3$ | $1.0 \times f_{sym}/2$ | 13.5 | + +**Table F.3/G.991.2 (Part 2) – Symmetric PSD parameters, 32-TCPAM** + +| Payload bit rate, $R$ (kbit/s) | $K_{SHDSL}$ | Order | $N$ | $f_{sym}$ (ksymbol/s) | $f_{3dB}$ | $P_{SHDSL}$ (dBm) | +|--------------------------------|-------------|-------|-----|-----------------------|------------------------|-------------------| +| $768 \leq R \leq 5696$ | 7.86 | 6 | 1 | $(R + 8)/4$ | $1.0 \times f_{sym}/2$ | 13.5 | + +For 0 dB power backoff, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5$ dB. For power backoff values other than 0 dB, the measured transmit power into 135 $\Omega$ shall fall within the range $P_{SHDSL} \pm 0.5$ dB minus the power backoff value in dB. The measured transmit PSD into 135 $\Omega$ shall remain below $PSDMASK_{SHDSL}(f)$ . + +Figure F.1 shows the PSD masks with 0 dB power backoff for payload data rates of 3840 (16-TCPAM) and 5696 (32-TCPAM) kbit/s. + +![Figure F.1/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -40) against Frequency (kHz) on the x-axis (from 0 to 2000). Two curves are shown: one for 3840 kbit/s / 16-TCPAM and another for 5696 kbit/s / 32-TCPAM. Both curves start at approximately -42 dBm/Hz at 0 kHz and remain relatively flat until about 400 kHz, after which they roll off sharply. The 3840 kbit/s curve drops to -100 dBm/Hz around 1200 kHz, while the 5696 kbit/s curve drops to -100 dBm/Hz around 1400 kHz. Beyond these points, both curves remain at -100 dBm/Hz up to 2000 kHz. Vertical dashed lines are present at 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, and 2000 kHz. A label 'G.991.2_FF-1' is in the bottom right corner.](d2485914dcdbf42b642c42d5e28ab9d4_img.jpg) + +Figure F.1/G.991.2 – PSD masks for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -40) against Frequency (kHz) on the x-axis (from 0 to 2000). Two curves are shown: one for 3840 kbit/s / 16-TCPAM and another for 5696 kbit/s / 32-TCPAM. Both curves start at approximately -42 dBm/Hz at 0 kHz and remain relatively flat until about 400 kHz, after which they roll off sharply. The 3840 kbit/s curve drops to -100 dBm/Hz around 1200 kHz, while the 5696 kbit/s curve drops to -100 dBm/Hz around 1400 kHz. Beyond these points, both curves remain at -100 dBm/Hz up to 2000 kHz. Vertical dashed lines are present at 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, and 2000 kHz. A label 'G.991.2\_FF-1' is in the bottom right corner. + +**Figure F.1/G.991.2 – PSD masks for 0 dB power backoff** + +The equation for the nominal PSD measured at the terminals is: + +$$\text{NominalPSD}(f) \begin{cases} 10^{\frac{-P_{BO}}{10}} \times \frac{K_{SHDSL}}{135} \times \frac{1}{f_{sym}} \times \frac{\left[ \sin\left(\frac{\pi f}{N f_{sym}}\right) \right]^2}{\left(\frac{\pi f}{N f_{sym}}\right)^2} \times \frac{1}{1 + \left(\frac{f}{f_{3dB}}\right)^{2 \times \text{Order}}} \times \frac{f^2}{f^2 + f_c^2} \text{ W/Hz} , & f < f_{int} \\ 0.5683 \times 10^{-4} \times f^{-1.5} \text{ W/Hz} , & f_{int} \leq f \leq 3.184 \text{ MHz} \\ -100 \text{ dBm/Hz} , & 3.184 \text{ MHz} \leq f \leq 12 \text{ MHz} \end{cases}$$ + +where $f_c$ is the transformer cut-off frequency, assumed to be 5 kHz. The variables $f$ , $f_{sym}$ , $f_{int}$ , and $f_{3dB}$ in the equations are in units of Hz. Figure F.2 shows the nominal transmit PSDs with 13.5 dBm power for payload data rates of 3840 (16-TCPAM) and 5696 (32-TCPAM) kbit/s. + +NOTE 2 – The nominal PSD is intended to be informative in nature; however, it is used for purposes of crosstalk calculations as representative of typical implementations. + +![Figure F.2/G.991.2 – Nominal PSDs for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -40) against Frequency (kHz) on the x-axis (from 0 to 2000). Two curves are shown: one for 3840 kbit/s / 16-TCPAM and another for 5696 kbit/s / 32-TCPAM. Both curves start at approximately -45 dBm/Hz at 0 kHz and remain relatively flat until about 600 kHz, after which they drop sharply. The 3840 kbit/s curve drops to about -105 dBm/Hz by 1200 kHz, while the 5696 kbit/s curve drops more steeply to about -110 dBm/Hz by 1400 kHz. Both curves remain flat at their respective levels until 2000 kHz. The label 'G.991.2_FF-2' is in the bottom right corner.](f106645198833980b601154c2ef98438_img.jpg) + +Figure F.2/G.991.2 – Nominal PSDs for 0 dB power backoff. The graph plots PSD (dBm/Hz) on the y-axis (from -110 to -40) against Frequency (kHz) on the x-axis (from 0 to 2000). Two curves are shown: one for 3840 kbit/s / 16-TCPAM and another for 5696 kbit/s / 32-TCPAM. Both curves start at approximately -45 dBm/Hz at 0 kHz and remain relatively flat until about 600 kHz, after which they drop sharply. The 3840 kbit/s curve drops to about -105 dBm/Hz by 1200 kHz, while the 5696 kbit/s curve drops more steeply to about -110 dBm/Hz by 1400 kHz. Both curves remain flat at their respective levels until 2000 kHz. The label 'G.991.2\_FF-2' is in the bottom right corner. + +**Figure F.2/G.991.2 – Nominal PSDs for 0 dB power backoff** + +### F.5 Crosstalk interference requirements + +Table F.4 shows the minimum set of test loops and crosstalk combinations required for testing SHDSL margins. A compliant unit shall pass the BER test described in A.3.1 for all crosstalk scenarios and test loops defined in Table F.4 for all supported data rates and modulation type (e.g., 16-TCPAM or 32-TCPAM). 0 dB Power Backoff shall be used for both the STU-C and STU-R. The calibration procedure and testing methods used shall be identical to those used for Annex A. The test loops and disturbers are identical to the corresponding cases in Annex A. + +**Table F.4/G.991.2 – Crosstalk scenarios and required SHDSL noise margins (Note)** + +| Test | Test loop (from Figure A.1) | L (× 1000') | Test unit | Payload data rate (kbit/s) | Modulation | PSD | Interferer combination | Required margin (dB) | +|------|-----------------------------|-------------|-----------|----------------------------|------------|-----------|----------------------------|----------------------| +| 1 | S | 4.5 | STU-C | 3840 | 16-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 4) | $5 + \Delta^*$ | +| 2 | S | 4.5 | STU-R | 3840 | 16-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 14) | $5 + \Delta^*$ | +| 3 | S | 4.9 | STU-C | 3392 | 16-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 4) | $5 + \Delta^*$ | +| 4 | S | 4.9 | STU-R | 3392 | 16-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 14) | $5 + \Delta^*$ | +| 5 | S | 5.7 | STU-C | 2560 | 16-TCPAM | Symmetric | 49 SHDSL sym 2304 | $5 + \Delta^*$ | + +**Table F.4/G.991.2 – Crosstalk scenarios and required SHDSL noise margins (Note)** + +| Test | Test loop (from Figure A.1) | L (× 1000') | Test unit | Payload data rate (kbit/s) | Modulation | PSD | Interferer combination | Required margin (dB) | +|------|-----------------------------|-------------|-----------|----------------------------|------------|-----------|--------------------------------|----------------------| +| | | | | | | | (Case 11) | | +| 6 | S | 5.7 | STU-R | 2560 | 16-TCPAM | Symmetric | 49 SHDSL sym 2304 (Case 11) | $5 + \Delta^*$ | +| 7 | S | 2.8 | STU-C | 5696 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 4) | $5 + \Delta^*$ | +| 8 | S | 2.8 | STU-R | 5696 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 14) | $5 + \Delta^*$ | +| 9 | S | 3.1 | STU-C | 5056 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 4) | $5 + \Delta^*$ | +| 10 | S | 3.1 | STU-R | 5056 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 14) | $5 + \Delta^*$ | +| 11 | S | 4.2 | STU-C | 3392 | 32-TCPAM | Symmetric | 49 SHDSL sym 2304 (Case 11) | $5 + \Delta^*$ | +| 12 | S | 4.2 | STU-R | 3392 | 32-TCPAM | Symmetric | 49 SHDSL sym 2304 (Case 11) | $5 + \Delta^*$ | +| 13 | S | 5.0 | STU-C | 2560 | 32-TCPAM | Symmetric | 49 SHDSL sym 2048 (Case 16) | $5 + \Delta^*$ | +| 14 | S | 5.0 | STU-R | 2560 | 32-TCPAM | Symmetric | 49 SHDSL sym 2048 (Case 16) | $5 + \Delta^*$ | +| 15 | S | 2.3 | STU-C | 5696 | 32-TCPAM | Symmetric | 24 FDD ADSL + 24 HDSL (Case 6) | $5 + \Delta^*$ | +| 16 | BT1-C | 1.9 | STU-C | 5696 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 4) | $5 + \Delta^*$ | +| 17 | BT1-R | 1.9 | STU-R | 5696 | 32-TCPAM | Symmetric | 24 HDSL2 + 24 T1 (Case 14) | $5 + \Delta^*$ | +| 18 | BT2-C | 3.9 | STU-C | 2560 | 32-TCPAM | Symmetric | 49 HDSL sym 2048 (Case 16) | $5 + \Delta^*$ | +| 19 | BT2-R | 3.9 | STU-R | 2560 | 32-TCPAM | Symmetric | 49 HDSL sym 2048 (Case 16) | $5 + \Delta^*$ | + +NOTE – The crosstalk scenarios listed in this table were developed under the assumption of a 50 pair cable binder. Cable binders of other sizes are for further study. + +\* The indicated noise margins in Table F.4 shall have a tolerance of 1.25 dB due to the aggregate effect of crosstalk generator tolerance and calibrated loop simulator tolerance. The offset $\Delta$ is defined in A.3.1.4. + +All interferers are assumed to be co-located. All interferer PSDs are described in A.3.3.9. The disturbers used for these tests are identical to those used in Annex A. For example, test 1 in Table F.4 uses the identical disturber shape as case 4 from Annex A, exactly as described by $PSD_{Case-4}$ in A.3.3.9. + +## F.6 Functional characteristics + +Functional characteristics return loss, Span Powering, Longitudinal Balance, and Longitudinal Output Voltage shall be as described in A.5. + +## Annex G + +### Reserved for Region 2 requirements for data rates between 2320 kbit/s and \*\*max rate\*\* + +## Annex H + +### Deactivation and warm-start procedure + +Support of the reduced power mode, the deactivation and the warm-start is optional. + +NOTE – Frequent transitions to/from the reduced power mode introduce a non-stationary noise environment, the effect of which on deployed xDSL systems is not fully known. Because of this, regional access restrictions regarding this procedure might apply. + +#### H.1 Deactivation to reduced power mode + +This clause describes waveforms at the loop interface and associated procedures during deactivation. Figure H.1 illustrates the deactivation sequence. + +##### H.1.1 Deactivation sequence + +The deactivation can be initiated by the STU-R or by the STU-C. EOC signalling is used to initiate the deactivation. The initiating side is called unit A, the other side is called unit B. + +The standard sequence is as follows: Upon receiving the EOC message "Deactivation Request", unit B responds by the EOC message "Deactivation Response" or by "Generic Unable To Comply (UTC)". After sending the "Deactivation Response" containing an acceptance to the deactivation (Deactivation Acknowledge bit = "1"), unit B continues transmitting and waits for the deactivation of unit A. After receiving the acceptance to the deactivation request, unit A stops transmitting and enters the reduced power mode. After detecting that unit A has stopped transmitting, e.g., by detecting an LOSW error, unit B stops transmitting and enters the reduced power mode as well. + +The EOC messages "Deactivation Request" and "Deactivation Response" indicate the ability of the sender for the deactivation to the reduced power mode and a subsequent warm-start. + +![Sequence diagram illustrating the Deactivation sequence between Unit A and Unit B. The process starts with a Deactivation request from the TPS-TC layer to Unit A. Unit A freezes coefficients and sends an EOC message Deactivation Request to Unit B. Unit B freezes coefficients and responds with an EOC message Deactivation Response (Acknowledge bit = 1). Unit A receives the response, ceases transmission, and powers down. Unit B detects a LOSW defect due to 'no signal' from Unit A, ceases transmission, and powers down, sending a Deactivation Indication to its TPS-TC layer. The diagram is labeled G.991.2_FH-1.](955eff49369c0dcaa1a0e8ed9bfd8342_img.jpg) + +``` + +sequenceDiagram + participant TPS-TC_A as TPS-TC layer + participant Unit_A as Unit A + participant Unit_B as Unit B + participant TPS-TC_B as TPS-TC layer + + Note left of TPS-TC_A: Deactivation request + TPS-TC_A->>Unit_A: + Unit_A->>Unit_A: freeze coefficients + Unit_A->>Unit_B: EOC message Deactivation Request + Unit_B->>Unit_B: freeze coefficients + Unit_B->>Unit_A: EOC message Deactivation Response (Acknowledge bit = 1) + Unit_A->>Unit_A: cease transmission + Unit_A-->>Unit_B: no signal + Unit_A->>Unit_A: Power down + Note right of Unit_B: LOSW defect + Unit_B-->>Unit_A: no signal + Unit_B->>Unit_B: cease transmission + Unit_B->>Unit_B: Power down + Unit_B->>TPS-TC_B: Deactivation Indication + +``` + +Sequence diagram illustrating the Deactivation sequence between Unit A and Unit B. The process starts with a Deactivation request from the TPS-TC layer to Unit A. Unit A freezes coefficients and sends an EOC message Deactivation Request to Unit B. Unit B freezes coefficients and responds with an EOC message Deactivation Response (Acknowledge bit = 1). Unit A receives the response, ceases transmission, and powers down. Unit B detects a LOSW defect due to 'no signal' from Unit A, ceases transmission, and powers down, sending a Deactivation Indication to its TPS-TC layer. The diagram is labeled G.991.2\_FH-1. + +**Figure H.1/G.991.2 – Deactivation sequence** + +## H.1.2 Deactivation inhibiting + +With messages "Deactivation Request" and "Deactivation Acknowledge", however, each transceiver can also inhibit or stop an initiated deactivation process by setting bit OK to "0" in the relevant EOC message. This is useful when during or after the transmission of the "Deactivation Request" it becomes apparent that the data link is about to be used. + +In warm-start the transmission shall be active for at least time $t_{\text{active}}$ to minimize effects of non-stationary crosstalk to systems sharing the same binder. + +## H.1.3 Deactivation EOC messages + +### H.1.3.1 Deactivation Request message: Message ID 22 + +The Deactivation Request message is transmitted to request a deactivation or to withdraw an issued deactivation request. The destination address shall be F16 to indicate this is a broadcast message. + +**Table H.1/G.991.2 – Deactivation Request** + +| Octet # | Contents | Data type | Reference | +|-------------|----------------------|------------|----------------------------------------------------------------| +| 1 | 22 | Message ID | | +| 2 bits 7..1 | Reserved | | Set to 0 | +| 2 bit 0 | Deactivation Request | Bit | 0 = Deactivation request
1 = Deactivation request cancelled | +| 3 | Reserved | | Set to 0 | + +**H.1.3.2 Deactivation Response Message: Message ID 150** + +The deactivation response message is used to confirm the deactivation command or to refuse a deactivation request. + +**Table H.2/G.991.2 – Deactivation Acknowledge** + +| Octet # | Contents | Data type | Reference | +|-------------|--------------------------|------------|------------------------------------------------------| +| 1 | 150 | Message ID | | +| 2 bits 7..1 | Reserved | | Set to 0 | +| 2 bit 0 | Deactivation Acknowledge | Bit | 0 = Deactivation OK
1 = Deactivation not possible | +| 3 | Reserved | | Set to 0 | + +**H.2 Warm-start activation** + +The warm-start can be initiated by the STU-R or the STU-C. This clause describes waveforms at the loop interface and associated procedures during warm-start. The direct specification of the performance of individual receiver elements is avoided when possible. Instead, the transmitter characteristics are specified on an individual basis and the receiver performance is specified on a general basis as the aggregate performance of all receiver elements. Exceptions are made for cases where the performance of an individual receiver element is crucial to inter-operability. + +In contrast to the activation described in 6.2, a warm-start makes use of all settings stored in a previous successful activation to achieve a minimum start-up time. An activation is successful if convergence has been achieved and the data mode has been reached (see 6.1). All settings (i.e., negotiated configuration in the pre-activation, all data in the activation frame, and all values in adaptive filters) have to be stored before deactivating the transmission. The warm-start relies on the fact that all previously stored settings such as the transfer characteristics of the receive and transmit path and the timing relation between receive and transmit signals are still relevant. Small changes (e.g., due to variations of ambient temperature) should not inhibit the warm-start activation; however, if the equipment or the loop characteristics have changed significantly, the warm-start activation may fail, and a cold-start will be performed instead. + +**H.2.1 Warm-start activation PMD reference model** + +The block diagram of the warm-start activation PMD layer of an STU-C and STU-R transmitter is shown in Figure H.2. + +![Figure H.2/G.991.2 – Warm-start activation PMD reference model. This block diagram shows the signal flow from logical inputs to the output at the loop interface. Two inputs, 'logical ones -d1(m)' and 'logical zeros -d0(m)', enter a 'Scrambler' block. The output of the scrambler is s(m), which enters a 'Mapper' block. The output of the mapper is x(m), which enters a 'Channel precoder' block. The output of the channel precoder is y(m), which enters a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is the 'Output at loop interface'. A block labeled 'G.994.1' is connected to the output of the spectral shaper. The entire process is labeled 'G.991.2_FH-2'.](4562b7df9e2e257eac16ccb0e5eb8932_img.jpg) + +Figure H.2/G.991.2 – Warm-start activation PMD reference model. This block diagram shows the signal flow from logical inputs to the output at the loop interface. Two inputs, 'logical ones -d1(m)' and 'logical zeros -d0(m)', enter a 'Scrambler' block. The output of the scrambler is s(m), which enters a 'Mapper' block. The output of the mapper is x(m), which enters a 'Channel precoder' block. The output of the channel precoder is y(m), which enters a 'Spectral shaper' block. The output of the spectral shaper is z(t), which is the 'Output at loop interface'. A block labeled 'G.994.1' is connected to the output of the spectral shaper. The entire process is labeled 'G.991.2\_FH-2'. + +**Figure H.2/G.991.2 – Warm-start activation PMD reference model** + +The time index $m$ represents the symbol time, and $t$ represents analogue time. Since activation uses 2-PAM modulation, the bit time is equivalent to the symbol time. The output of the scrambler is $s(m)$ . The output of the mapper is $y(m)$ , and the output of the spectral shaper at the loop interface is $z(t)$ . $d_1(m)$ is an initialization signal that shall be logical ones for all $m$ . $d_0(m)$ is an initialization signal that shall be logical zeros for all $m$ . The modulation format shall be Tomlinson-coded 2-level signal, with the full symbol rate selected for data mode operation. During activation, the timing reference for the activation signals have a tolerance of $\pm 32$ ppm at the STU-C and $\pm 100$ ppm at the STU-R. + +The output bits from the scrambler $s(m)$ shall be mapped to an output level $y(m)$ as follows: + +**Table H.3/G.991.2 – Bit-to-level mapping** + +| Scrambler output $s(m)$ | Mapper output level $y(m)$ | Data mode index | +|-------------------------|----------------------------|-----------------| +| 0 | $-9/16$ | 0011 | +| 1 | $+9/16$ | 1000 | + +The levels corresponding to a 0 and 1 at the output of the scrambler shall be identical to the levels of the 16-TCPAM constellation corresponding to indexes 0011 and 1000 respectively. + +## H.2.2 Warm-start activation sequence + +The sequence and timing diagram for the warm-start activation sequence is given in Figure H.3. + +![Figure H.3/G.991.2 – Timing diagram for the warm-start activation sequence. This diagram shows the activation sequence for STU-R and STU-C. The STU-R line shows a sequence of events: W_WUN (only if activation initiated by STU-R), t_WUN, t_WS, t_WUL, t_WS, t_ECN, t_WS, t_SYN, W_ECN, W_SH, W_OKN, and Data. The STU-C line shows a sequence of events: W_WUL, t_WS, t_ECN, t_WS, t_SYN, W_SH, W_OKL, and Data. The time interval between the start of W_WUN and the start of W_SH is labeled t_WSact. The time interval between the start of W_WUL and the start of W_SH is labeled 'Half-duplex segments'. The diagram also indicates 'STU-R in operational status' and 'STU-C and STU-R in operational status'.](6f4bd55b0d89291b2a29d9cd6de54bc2_img.jpg) + +Figure H.3/G.991.2 – Timing diagram for the warm-start activation sequence. This diagram shows the activation sequence for STU-R and STU-C. The STU-R line shows a sequence of events: W\_WUN (only if activation initiated by STU-R), t\_WUN, t\_WS, t\_WUL, t\_WS, t\_ECN, t\_WS, t\_SYN, W\_ECN, W\_SH, W\_OKN, and Data. The STU-C line shows a sequence of events: W\_WUL, t\_WS, t\_ECN, t\_WS, t\_SYN, W\_SH, W\_OKL, and Data. The time interval between the start of W\_WUN and the start of W\_SH is labeled t\_WSact. The time interval between the start of W\_WUL and the start of W\_SH is labeled 'Half-duplex segments'. The diagram also indicates 'STU-R in operational status' and 'STU-C and STU-R in operational status'. + +**Figure H.3/G.991.2 – Timing diagram for the warm-start activation sequence** + +**Table H.4/G.991.2 – Durations and tolerances for activation signals** + +| Signal | Parameter | Reference | Nominal value | Tolerance | +|---------------------|----------------------------------------------------------|-----------|---------------|------------| +| $t_{\text{WUN}}$ | Duration of $W_{\text{WUN}}$ | H.2.4.1 | 12 ms | $\pm 2$ ms | +| $t_{\text{WS}}$ | Guard time to prevent overlapping signals | | 6 ms | $\pm 2$ ms | +| $t_{\text{WUL}}$ | Duration of $W_{\text{WUL}}$ | H.2.4.2 | 20 ms | $\pm 2$ ms | +| $t_{\text{ECN}}$ | Duration of the half-duplex segment of the STU-R | H.2.4.3 | 40 ms | $\pm 2$ ms | +| $t_{\text{SYN}}$ | Minimum Duration of the half-duplex segment of the STU-C | | 100 ms | $\pm 2$ ms | +| $t_{\text{WSact}}$ | Maximum activation time | | 500 ms | | +| $t_{\text{active}}$ | Minimum time the link has to remain active | | 5 min | | + +NOTE – The maximum time for activation, occurring after a deactivation without any intervening loopback or powering action and without any change in cable characteristic for a metallic pair cable transmission system is $t_{\text{WSact}}$ . This value for activation time is understood as a 95%-value when testing with line models specified for the digital transmission system. + +### H.2.3 State Transition Diagram + +The state transition diagram for the warm-start activation of the STU-R and the STU-C is given in Figure H.4. + +![Figure H.4/G.991.2 – STU-C and STU-R transmitter warm-start state transition diagram. The diagram is split into two vertical columns. The left column, 'Activation of STU-R', shows a sequence of states: Power down, W_WUN, Wait t_WS, W_ECN, Wait t_SYN+t_WS, W_SN, W_OKN, Data. Transitions include 'Warm-start Req. by STU-R', 'W_WUL detected', 'C-tone detected', 'STU-R converged', and 'W_OKL detected'. The right column, 'Activation of STU-C', shows states: Power Down, W_WUL, Wait t_ECN+2*t_WS, W_SL, W_OKL, Data. Transitions include 'Warm-start Req. by STU-C or W_WUN detected', 'R-tone detected', 'STU-C converged and W_OKN detected', and 'W_OKL detected'. Both columns lead to a 'Pre-activation' state and then a 'Warm-start Exception state' if an exception condition occurs. Asterisks (*) indicate optional or error paths.](39729be7ec83c3de8e480061966e4505_img.jpg) + +**Activation of STU-R** + +States: Power down, $W_{WUN}$ , Wait $t_{WS}$ , $W_{ECN}$ , Wait $t_{SYN}+t_{WS}$ , $W_{SN}$ , $W_{OKN}$ , Data + +Transitions: Warm-start Req. by STU-R, $W_{WUL}$ detected, C-tone detected, STU-R converged, $W_{OKL}$ detected + +**Activation of STU-C** + +States: Power Down, $W_{WUL}$ , Wait $t_{ECN}+2*t_{WS}$ , $W_{SL}$ , $W_{OKL}$ , Data + +Transitions: Warm-start Req. by STU-C or $W_{WUN}$ detected, R-tone detected, STU-C converged and $W_{OKN}$ detected, $W_{OKL}$ detected + +Common states: Pre-activation, Warm-start Exception state + +Exception condition (e.g., missed detection of expected signal) + +G.991.2\_FH-4 + +Figure H.4/G.991.2 – STU-C and STU-R transmitter warm-start state transition diagram. The diagram is split into two vertical columns. The left column, 'Activation of STU-R', shows a sequence of states: Power down, W\_WUN, Wait t\_WS, W\_ECN, Wait t\_SYN+t\_WS, W\_SN, W\_OKN, Data. Transitions include 'Warm-start Req. by STU-R', 'W\_WUL detected', 'C-tone detected', 'STU-R converged', and 'W\_OKL detected'. The right column, 'Activation of STU-C', shows states: Power Down, W\_WUL, Wait t\_ECN+2\*t\_WS, W\_SL, W\_OKL, Data. Transitions include 'Warm-start Req. by STU-C or W\_WUN detected', 'R-tone detected', 'STU-C converged and W\_OKN detected', and 'W\_OKL detected'. Both columns lead to a 'Pre-activation' state and then a 'Warm-start Exception state' if an exception condition occurs. Asterisks (\*) indicate optional or error paths. + +Figure H.4/G.991.2 – STU-C and STU-R transmitter warm-start state transition diagram + +## H.2.4 Signals used in warm-start activation + +### H.2.4.1 Signal $W_{WUN}$ + +The STU-R initiated warm-start shall start with the STU-R sending the warm-start wake up signal, $W_{WUN}$ for a duration of $t_{WUN}$ . The waveform and the transmit power of $W_{WUN}$ is the same as of the 12 kHz R-Tone used in ITU-T Rec. G.994.1 [2]. + +#### H.2.4.2 Signal $W_{WUL}$ + +The wake-up signal for the STU-C initiated warm-start shall be the $W_{WUL}$ . If the warm-start is initiated by the STU-R, the STU-C shall send the signal $W_{WUL}$ after detecting the signal $W_{WUN}$ . $W_{WUL}$ shall have a duration of $t_{WUL}$ . The waveform and the transmit power of $W_{WUL}$ is the same as of the 20 kHz C-Tone used in ITU-T Rec. G.994.1 [2]. + +#### H.2.4.3 Signal $W_{ECN}$ + +The STU-R shall send $W_{ECN}$ , beginning $t_{WS}$ after the end of $W_{WUL}$ . Waveform $W_{ECN}$ shall be generated by connecting logical ones to the input of the STU-R scrambler as shown in Figure H.2. The transmit power, symbol rate and PSD mask for $W_{ECN}$ shall be as for signal $W_{SL}$ . + +Half-duplex signal $W_{ECN}$ shall be sent for time $t_{ECN}$ . + +#### H.2.4.4 Signal $W_{SL}$ + +The STU-C shall send $W_{SL}$ beginning $t_{WS}$ after the end of $W_{ECN}$ . Waveform $W_{SL}$ shall be generated by connecting logical ones to the input of the STU-C scrambler as shown in Figure H.2. The transmit power, symbol rate and PSD mask for $W_{SL}$ shall be as negotiated during the pre-activation sequence. + +#### H.2.4.5 Signal $W_{SN}$ + +The STU-R shall start transmitting $W_{SN}$ beginning $t_{WS} + t_{SYN}$ after the end of $W_{ECN}$ . Waveform $W_{SN}$ shall be generated by connecting logical ones to the input of the STU-R scrambler as shown in Figure H.2. The transmit power, symbol rate and PSD mask for $W_{SN}$ shall be as negotiated during the pre-activation sequence. + +#### H.2.4.6 Signal $W_{OKN}$ + +The STU-R shall start transmitting $W_{OKN}$ when the STU-R achieves full operational status. Full operational status of the STU-R means that the STU-R is ready to enter data mode. Waveform $W_{OKN}$ shall be generated by connecting logical zeros to the input of the STU-R scrambler as shown in Figure H.2. The transmit power, symbol rate and PSD mask for $W_{OKN}$ shall be as for signal $W_{SN}$ . + +#### H.2.4.7 Signal $W_{OKL}$ + +The STU-C shall send $W_{OKL}$ when the STU-C has both detected $W_{OKL}$ and achieves full operational status. Full operational status of the STU-C means that the STU-C is ready to enter data mode. Waveform $W_{OKL}$ shall be generated by connecting logical zeros signal to the input of the STU-C scrambler as shown in Figure H.2. The transmit power, symbol rate and PSD mask for $W_{OKL}$ shall be the same as for $W_{SL}$ . $W_{OKL}$ shall be sent for exactly 256 symbols. + +#### H.2.4.8 $Data_c$ and $Data_r$ + +Within 200 symbols after the end of $W_{OKL}$ , the STU-C shall send $Data_c$ and STU-R shall send $Data_r$ . These signals are described in 6.2.2.7. There is no required relationship between the end of $W_{OKL}$ and any bit within the SHDSL data-mode frame. The SHDSL payload data shall be valid $T_{payloadValid}$ (see Table H.5) after the end of $W_{OKL}$ . + +#### H.2.4.9 Warm-start exception condition + +An exception condition shall be declared during warm-start if the timeout values given in Table H.5 expire or if any vendor-defined abnormal event occurs. + +#### H.2.4.10 Warm-start exception state + +If an exception condition is declared during warm-start, the STU-C or STU-R enters the exception state and warm-start is aborted. During the exception state, the STU shall be silent for at least $T_{\text{silence}}$ (see Table H.5), wait for transmission from the far end to cease, then return to the corresponding initial start-up state. The STU-R and STU-C shall begin pre-activation, as per 6.3. + +#### H.2.4.11 Timeouts + +Table H.5 shows the system timeouts and their values. + +**Table H.5/G.991.2 – Timeout values** + +| Name | Parameter | Value | +|---------------------------|------------------------------------------------------------------------------------------------------------------------|---------------| +| $T_{\text{silence}}$ | Minimum time in the warm-start exception state where the STU-C or STU-R are silent before the start of pre-activation. | See Table 6-3 | +| $T_{\text{payloadValid}}$ | Time from start of $\text{Data}_c$ or $\text{Data}_r$ to valid SHDSL payload data | See Table 6-3 | + +### Appendix I + +#### Test circuit examples + +##### I.1 Example crosstalk injection test circuit + +Figure I.1 is an example of a high-impedance crosstalk injection circuit. + +![Figure I.1/G.991.2 – Example high-impedance crosstalk injection circuit. The diagram shows a transformer with a 50 Ω unbalanced primary and a 1.8 kΩ balanced secondary. The secondary is connected to a 2.2 kΩ resistor and two 5.1 kΩ resistors leading to a test loop. The test loop is terminated with Z = 11 kΩ. Below the main circuit, a calibration section shows two 135 Ω resistors (R_LOOP and R_REC) in parallel, with an input resistance R_IN = 67.5 Ω.](3baef64ba57070d61b536cf90c6fcda5_img.jpg) + +The diagram illustrates a high-impedance crosstalk injection circuit. At the top, a transformer is shown with its primary winding connected to a 50 Ω unbalanced source and its secondary winding connected to a 1.8 kΩ balanced load. The secondary is also connected to a 2.2 kΩ resistor and two 5.1 kΩ resistors that lead to a 'To test loop' output. The test loop is terminated with an impedance $Z = 11 \text{ k}\Omega$ . Below the main circuit, a calibration section is shown, featuring two 135 Ω resistors, labeled $R_{\text{LOOP}} = 135 \Omega$ and $R_{\text{REC}} = 135 \Omega$ , connected in parallel. The input resistance for this calibration section is given as $R_{\text{IN}} = 67.5 \Omega$ . The diagram is labeled 'G.991.2\_FI-1'. + +Figure I.1/G.991.2 – Example high-impedance crosstalk injection circuit. The diagram shows a transformer with a 50 Ω unbalanced primary and a 1.8 kΩ balanced secondary. The secondary is connected to a 2.2 kΩ resistor and two 5.1 kΩ resistors leading to a test loop. The test loop is terminated with Z = 11 kΩ. Below the main circuit, a calibration section shows two 135 Ω resistors (R\_LOOP and R\_REC) in parallel, with an input resistance R\_IN = 67.5 Ω. + +**Figure I.1/G.991.2 – Example high-impedance crosstalk injection circuit** + +##### I.2 Example coupling circuits for longitudinal balance and longitudinal output voltage + +Longitudinal balance and longitudinal output voltage may be measured using the coupling circuits described in ANSI/IEEE Standard 455-1985 [B7] and ITU-T Rec. O.9 [B8]. The coupling circuit in Figure I.2 is based upon the measurement method defined in ANSI/IEEE Standard 455-1985. In order to provide sufficient measurement resolution the resistors must be matched within 0.05 % tolerance. The coupling circuit in Figure I.3 is based on the measurement method described in ITU-T Rec. O.9. This test circuit uses precision balanced (bifilar wound) transformers/baluns and + +does not require precision matched resistors. The balun circuit is often more convenient for high-frequency measurements. + +![Figure I.2/G.991.2 – Example resistive coupling circuit. The diagram shows a central node with two resistors, each labeled 67.5 Ω, connected to it. Arrows point to the right from each resistor, indicating output ports. The label G.991.2_FI-2 is present.](3e8b6c66edbfbca22863e12c1062afac_img.jpg) + +Figure I.2/G.991.2 – Example resistive coupling circuit. The diagram shows a central node with two resistors, each labeled 67.5 Ω, connected to it. Arrows point to the right from each resistor, indicating output ports. The label G.991.2\_FI-2 is present. + +Figure I.2/G.991.2 – Example resistive coupling circuit + +![Figure I.3/G.991.2 – Example balun coupling circuit. The diagram shows a balun transformer with an inductor labeled L > 25 mH. A 33.8 Ω resistor is connected to the primary winding. The secondary winding is connected to a 135 Ω resistor. Arrows point to the right from the 135 Ω resistor, indicating output ports. The label G.991.2_FI-3 is present.](9f5f9afcedaa0d9b7991976f5000865c_img.jpg) + +Figure I.3/G.991.2 – Example balun coupling circuit. The diagram shows a balun transformer with an inductor labeled L > 25 mH. A 33.8 Ω resistor is connected to the primary winding. The secondary winding is connected to a 135 Ω resistor. Arrows point to the right from the 135 Ω resistor, indicating output ports. The label G.991.2\_FI-3 is present. + +Figure I.3/G.991.2 – Example balun coupling circuit + +### I.3 Return loss test circuit + +The test circuit in Figure I.4 is based upon the traditional return loss bridge with added components to accommodate the DC power feed voltage and provide transformer isolation for the measurement instrumentation. Transformer isolation of both test signal source and meter load prevent measurement errors from unintentional circuit paths through the common ground of the instrumentation and the DUT power feed circuitry. Input $V_{IN}$ is connected to a sweeping sine wave generator ( $50 \Omega$ source) and $V_{OUT}$ is connected to a high-impedance frequency selective voltmeter (or spectrum analyser). For this test circuit, the return loss is defined as follows: + +$$\text{Return Loss}(f) = 20 \log \left| \frac{Z_{TEST}(f) + Z_{REF}}{Z_{TEST}(f) - Z_{REF}} \right|$$ + +![Figure I.4/G.991.2 – Example return loss bridge test circuit (ground isolated). The diagram shows a complex test setup. On the left, an input voltage source V_IN is connected to a 1:1 transformer. The secondary of this transformer is connected to a precision balanced inductor (L > 20 mH). This inductor is part of a bridge circuit. A switch labeled 'Set' and 'Test' is used to connect the bridge to a reference impedance Z_REF = 135 Ω ± 0.5%. The bridge output is connected to a DC current source/sink through a 3.3 µF (min) capacitor. The output of the current source/sink is connected to the 'Ring' terminal of an SHDSL Device Under Test (DUT). The 'Tip' terminal of the DUT is connected to another 3.3 µF (min) capacitor, which is then connected to the output voltage source V_OUT. The DUT is shown as a block with 'Ring' and 'Tip' terminals, connected to ground. The label G.991.2_FI-4 is present. A note at the bottom indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'.](f86fbc9826e1910a39e36f7e62b568c2_img.jpg) + +Figure I.4/G.991.2 – Example return loss bridge test circuit (ground isolated). The diagram shows a complex test setup. On the left, an input voltage source V\_IN is connected to a 1:1 transformer. The secondary of this transformer is connected to a precision balanced inductor (L > 20 mH). This inductor is part of a bridge circuit. A switch labeled 'Set' and 'Test' is used to connect the bridge to a reference impedance Z\_REF = 135 Ω ± 0.5%. The bridge output is connected to a DC current source/sink through a 3.3 µF (min) capacitor. The output of the current source/sink is connected to the 'Ring' terminal of an SHDSL Device Under Test (DUT). The 'Tip' terminal of the DUT is connected to another 3.3 µF (min) capacitor, which is then connected to the output voltage source V\_OUT. The DUT is shown as a block with 'Ring' and 'Tip' terminals, connected to ground. The label G.991.2\_FI-4 is present. A note at the bottom indicates: 'Current sink required for testing STU-C' and 'Current source required for testing STU-R'. + +Figure I.4/G.991.2 – Example return loss bridge test circuit (ground isolated) + +#### I.4 Transmit PSD/total power measurement test circuit + +The test circuit in Figure I.5 is designed to measure total transmit power and transmit PSD. The test contains provisions for DC power feed and transformer isolation for the measurement instrumentation. Transformer isolation of the instrumentation input prevents measurement errors from unintentional circuit paths through the common ground of the instrumentation and the DUT power feed circuitry. $V_{OUT}$ is connected to a high-impedance wideband rms voltmeter (or spectrum analyser). + +![Figure I.5/G.991.2 – Example ground-isolated power/PSD measurement test circuit. The diagram shows a test circuit for measuring transmit power and PSD. On the left, an AC voltage source V_OUT (to high-impedance load) is connected to the primary of a 1:1 ±1% transformer. The primary has a 20 mH (min) inductor. The secondary is connected to a 135 Ω resistor and a DC current source/sink. Two 3.3 µF (min) capacitors are in series with the secondary. The output is connected to the Tip and Ring of an SHDSL Device Under Test (DUT). A return loss measurement (135 Ω reference) as per calibration template is indicated. The diagram is labeled G.991.2_FI-5.](d5439b040187c5a1e89ad438ef535141_img.jpg) + +``` + +graph LR + subgraph Measurement_Instrumentation + VOUT((V_OUT)) --- L1[20 mH min] + L1 --- T1_P[Transformer Primary] + end + T1_P -. 1:1 +/-1% .-> T1_S[Transformer Secondary] + subgraph Test_Circuit + T1_S --- R1[135 Ω] + R1 --- C1[3.3 μF min] + R1 --- C2[3.3 μF min] + C1 --- DC[DC current source/sink] + C2 --- DC + DC --- RL[Return loss 135 Ω reference] + end + RL --- Tip + RL --- Ring + subgraph DUT + Tip --- SHDSL[SHDSL Device Under Test] + Ring --- SHDSL + end + +``` + +Figure I.5/G.991.2 – Example ground-isolated power/PSD measurement test circuit. The diagram shows a test circuit for measuring transmit power and PSD. On the left, an AC voltage source V\_OUT (to high-impedance load) is connected to the primary of a 1:1 ±1% transformer. The primary has a 20 mH (min) inductor. The secondary is connected to a 135 Ω resistor and a DC current source/sink. Two 3.3 µF (min) capacitors are in series with the secondary. The output is connected to the Tip and Ring of an SHDSL Device Under Test (DUT). A return loss measurement (135 Ω reference) as per calibration template is indicated. The diagram is labeled G.991.2\_FI-5. + +Figure I.5/G.991.2 – Example ground-isolated power/PSD measurement test circuit + +## Appendix II + +### Typical characteristics of cables + +#### II.1 Typical characteristics of cables for Annex B + +NOTE – Parameters in this appendix differ from those specified in ITU-T Rec. G.996.1 [B11] for PE 04 and PE 05 cable. + +Table II.1/G.991.2 – PE cable constants + +| freq
[Hz]
$\times 10^3$ | PE04 | | | PE05 | | | PE06 | | | PE08 | | | +|-------------------------------|------------------------------------------|---------------------------------|----------------------------------|------------------------------------------|---------------------------------|----------------------------------|------------------------------------------|---------------------------------|----------------------------------|------------------------------------------|---------------------------------|----------------------------------| +| | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | +| 0 | 268 | 680 | 45.5 | 172 | 680 | 25 | 119 | 700 | 56 | 67 | 700 | 37.8 | +| 10 | 268 | 678 | 45.5 | 172 | 678 | 25 | 120 | 695 | 56 | 70.0 | 700 | 37.8 | +| 20 | 269 | 675 | 45.5 | 173 | 675 | 25 | 121 | 693 | 56 | 72.5 | 687 | 37.8 | +| 40 | 271 | 669 | 45.5 | 175 | 667 | 25 | 125 | 680 | 56 | 75.0 | 665 | 37.8 | +| 100 | 282 | 650 | 45.5 | 190 | 646 | 25 | 146 | 655 | 56 | 91.7 | 628 | 37.8 | +| 150 | 295 | 642 | 45.5 | 207 | 637 | 25 | 167 | 641 | 56 | 105 | 609 | 37.8 | +| 200 | 312 | 635 | 45.5 | 227 | 629 | 25 | 189 | 633 | 56 | 117 | 595 | 37.8 | +| 400 | 390 | 619 | 45.5 | 302 | 603 | 25 | 260 | 601 | 56 | 159 | 568 | 37.8 | +| 500 | 425 | 608 | 45.5 | 334 | 592 | 25 | 288 | 590 | 56 | 177.5 | 560 | 37.8 | +| 700 | 493 | 593 | 45.5 | 392 | 577 | 25 | 340 | 576 | 56 | 209 | 553 | 37.8 | +| 1000 | 582 | 582 | 45.5 | 466 | 572 | 25 | 405 | 570 | 56 | 250 | 547 | 37.8 | +| 2000 | 816 | 571 | 45.5 | 655 | 565 | 25 | 571 | 560 | 56 | 353 | 540 | 37.8 | + +**Table II.2/G.991.2 – PVC cable constants** + +| freq
[Hz]
$\times 10^3$ | PVC032 | | | PVC04 | | | PVC063 | | | +|-------------------------------|------------------------------------------|---------------------------------|----------------------------------|------------------------------------------|---------------------------------|----------------------------------|------------------------------------------|---------------------------------|----------------------------------| +| | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | Rs
[ $\Omega/m$ ]
$\times 10^{-3}$ | Ls
[H/m]
$\times 10^{-9}$ | Cp
[F/m]
$\times 10^{-12}$ | +| 0 | 419 | 650 | 120 | 268 | 650 | 120 | 108 | 635 | 120 | +| 10 | 419 | 650 | 120 | 268 | 650 | 120 | 108 | 635 | 120 | +| 20 | 419 | 650 | 120 | 268 | 650 | 120 | 108 | 635 | 120 | +| 40 | 419 | 650 | 120 | 268 | 650 | 120 | 111 | 630 | 120 | +| 100 | 427 | 647 | 120 | 281 | 635 | 120 | 141 | 604 | 120 | +| 150 | 453 | 635 | 120 | 295 | 627 | 120 | 173 | 584 | 120 | +| 200 | 493 | 621 | 120 | 311 | 619 | 120 | 207 | 560 | 120 | +| 400 | 679 | 577 | 120 | 391 | 592 | 120 | 319 | 492 | 120 | +| 500 | 750 | 560 | 120 | 426 | 579 | 120 | 361 | 469 | 120 | +| 700 | 877 | 546 | 120 | 494 | 566 | 120 | 427 | 450 | 120 | +| 1000 | 1041 | 545 | 120 | 584 | 559 | 120 | 510 | 442 | 120 | +| 2000 | 1463 | 540 | 120 | 817 | 550 | 120 | 720 | 434 | 120 | + +## Appendix III + +### Signal regenerator start-up description + +This appendix describes the start-up sequence used on spans employing regenerators. The sequence applies to spans with an arbitrary number of regenerators (up to 8), but for simplicity, the description here assumes a two-regenerator link. The use of line probing is optional, but its use is assumed for the purpose of this description. + +The basic premise is that capability lists and line probe results propagate from the STU-R toward the STU-C and that the SHDSL training begins at the STU-C and propagates in the direction toward the STU-R. The Regenerator Silent Period (RSP) bit in ITU-T Rec. G.994.1 is used to hold off segments while the start-up process propagates across the span. + +The block diagram in Figure III.1 shows a typical SHDSL span with two regenerators as a reference for the start-up sequences described below. + +![Block diagram of a SHDSL span with two signal regenerators. The diagram shows a sequence of components from left to right: STU-R, SRU2 (containing SRU-C and SRU-R), SRU1 (containing SRU-C and SRU-R), and STU-C. Arrows indicate signal flow between adjacent components. Below the components, three segments are labeled: Segment TR2 (between STU-R and SRU2), Segment RR1 (between SRU2 and SRU1), and Segment TR1 (between SRU1 and STU-C). A long double-headed arrow at the bottom spans the entire distance from STU-R to STU-C and is labeled 'SHDSL span'. The diagram is identified by the text 'G.991.2_FIII-1' in the bottom right corner.](58584484e1b78db31cf28c342cb7ac74_img.jpg) + +Block diagram of a SHDSL span with two signal regenerators. The diagram shows a sequence of components from left to right: STU-R, SRU2 (containing SRU-C and SRU-R), SRU1 (containing SRU-C and SRU-R), and STU-C. Arrows indicate signal flow between adjacent components. Below the components, three segments are labeled: Segment TR2 (between STU-R and SRU2), Segment RR1 (between SRU2 and SRU1), and Segment TR1 (between SRU1 and STU-C). A long double-headed arrow at the bottom spans the entire distance from STU-R to STU-C and is labeled 'SHDSL span'. The diagram is identified by the text 'G.991.2\_FIII-1' in the bottom right corner. + +**Figure III.1/G.991.2 – Block diagram of a SHDSL span with two signal regenerators** + +### III.1 STU-R initiated Start-up + +In most typical SHDSL installations, the STU-R can be expected to initiate the start-up process. The proposed SHDSL start-up process for STU-R initiation is described in the text below and shown graphically in Table III.1. + +In this mode, the STU-R triggers the start-up process by initiating a G.994.1 session with the regenerator closest to it (over segment TR2). The STU-R and the SRU2-C then exchange capabilities and optionally perform a line probe and a second capabilities exchange. The units do not have enough information to begin SHDSL activation at this point, so the SRU2-C issues an MS with the RSP bit set to hold off the STU-R while the start-up process propagates across the span. The G.994.1 session terminates normally, and the STU-R begins its waiting period. + +Next, the SRU2-C conveys the capabilities from Segment TR2 to the SRU2-R across the regenerator's internal interface. The SRU2-R then initiates a G.994.1 session with the SRU1-C and performs the same capabilities exchange and line probing sequence described above for the first segment. The capabilities expressed by the SRU2-R are the intersection of its own capabilities with the capabilities it has received for Segment TR2. The units still do not have sufficient information to begin SHDSL activation, so, again, the SRU1-R issues an MS with the RSP bit set. The G.994.1 session terminates normally, and the SRU2-R begins its waiting period. + +As before, the SRU1-C then conveys the capabilities from Segment RR1 (including the information from Segment TR2) to the SRU1-R across the regenerator's internal interface. The SRU1-R initiates a G.994.1 session with the STU-C and performs a capabilities exchange. Optionally, a line probe and a second capabilities exchange may be used. As before, the capabilities expressed by the SRU1-R are the intersection of its own capabilities with the capabilities it has received for Segments RR1 and TR2. At this point, the STU-C possesses all of the required information to select the span's operational parameters. The data rate and other parameters are selected, just as in a normal (non-regenerator) pre-activation sequence and then the SHDSL activation begins for Segment TR1. + +When the STU-C/SRU1-R link (over Segment TR1) has completed the SHDSL activation sequence (or the G.994.1 session, if clock mode 1 is selected), the SRU1-R communicates the selected operational parameters to the SRU1-C across the regenerator's internal interface. At this point, the SRU1-C initiates a G.994.1 session with the SRU2-R over Segment RR1. Parameters are selected – there should be no need for another CLR-CL exchange at this point – and the units perform the normal SHDSL activation. If clock mode 1 is selected (classic plesiochronous), there is no need to lock symbol timing to a network clock reference. In this case, the SRU1-C/SRU2-R G.994.1 session and activation should begin as soon as the STU-C/SRU1-R G.994.1 sessions complete. In clock modes 2, 3a, and 3b, such a network or data clock reference is necessary for establishing symbol timing. In these modes, the SRU1-C will delay the initiation of its G.994.1 session until the STU-C/SRU1-R activation is complete. In this way, the required reference clock will be available for symbol timing on the SRU1-C/SRU2-R segment. + +When the SRU1-C/SRU2-R link (over Segment RR1) has completed the SHDSL activation sequence (or the G.994.1 session, if clock mode 1 is selected), the SRU2-R communicates the selected operational parameters to the SRU2-C across the regenerator's internal interface. The SRU2-C initiates a G.994.1 session with the STU-R over Segment TR2. Parameters are selected and the units perform the normal SHDSL activation. When this activation sequence is complete, the span can become fully operational. + +**Table III.1/G.991.2 – STU-R initiated start-up sequence** + +| Segment TR2
(STU-R/SRU2-C) | Segment RR1
(SRU2-R/SRU1-C) | Segment TR1
(SRU1-R/STU-C) | +|--------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------| +| G.994.1 Start → | | | +| Capabilities exchange | | | +| Line probe | | | +| Capabilities exchange | | | +| ← MS (RSP) | | | +| | G.994.1 Start → | | +| | Capabilities exchange | | +| | Line probe | | +| | Capabilities exchange | | +| | ← MS (RSP) | | +| | | G.994.1 Start → | +| | | Capabilities exchange | +| | | Line probe | +| | | Capabilities exchange | +| | | Mode Selection | +| | | SHDSL activation | +| | ← G.994.1 Start | | +| | Mode Selection | | +| | SHDSL activation | | +| ← G.994.1 Start | | | +| Mode Selection | | | +| SHDSL activation | | | + +### III.2 STU-C initiated start-up + +In some cases, it may be desirable for the STU-C to initiate the start-up process. The proposed SHDSL start-up process for STU-C initiation is described in the text below and shown graphically in Table III.2. + +In this mode, the STU-C triggers the start-up process by initiating a G.994.1 session with the regenerator closest to it (over segment TR1). The SRU2-C issues an MS with the RSP bit set to hold off the STU-C while the start-up process propagates across the span. The G.994.1 session terminates normally, and the STU-C begins its wait period. Next, the SRU1-C initiates a G.994.1 session with the SRU2-R, which, again is terminated following an MS from the SRU2-R with the RSP bit set. + +The SRU2-C next initiates a G.994.1 session with the STU-R. From this point on, the start sequence is as described in III.1 for the STU-R initiated start-up. + +**Table III.2/G.991.2 – STU-C initiated start-up sequence** + +| Segment TR2
(STU-R/SRU2-C) | Segment RR1
(SRU2-R/SRU1-C) | Segment TR1
(SRU1-R/STU-C) | +|--------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------| +| | | ← G.994.1 Start | +| | | MS (RSP) → | +| | ← G.994.1 Start | | +| | MS (RSP) → | | +| ← G.994.1 Start | | | +| Capabilities exchange | | | +| Line probe | | | +| Capabilities exchange | | | +| ← MS (RSP) | | | +| | G.994.1 Start → | | +| | Capabilities exchange | | +| | Line probe | | +| | Capabilities exchange | | +| | ← MS (RSP) | | +| | | G.994.1 Start → | +| | | Capabilities exchange | +| | | Line probe | +| | | Capabilities exchange | +| | | Mode Selection | +| | | SHDSL activation | +| | ← G.994.1 Start | | +| | Mode Selection | | +| | SHDSL activation | | +| ← G.994.1 Start | | | +| Mode Selection | | | +| SHDSL activation | | | + +**III.3 SRU initiated start-up** + +In some limited applications (including some maintenance and retrain scenarios), it may be desirable for a regenerator to initiate the start sequence. In this mode, the SRU will initiate the train in the downstream direction – i.e., toward the STU-R in the same manner that it would have for the corresponding segment of the STU-C Start-up Procedure (as described in III.2). The STU-R will then initiate the capabilities exchange and line probing procedure toward the STU-C, as in a normal STU-C initiated start-up. The start-up sequence begins with the initiating SRU-C and propagating toward the STU-R. + +**III.4 Collisions and retrains** + +Collisions (equivalent to "glare" conditions in voice applications) can occur in cases where both the STU-C and the STU-R attempt to initiate connections simultaneously. Using the process described above, these collisions are resolved by specifying that R-to-C capabilities exchanges and probes will always take precedence over C-to-R train requests. G.994.1 sessions inherently resolve collisions on individual segments. + +In ITU-T Rec. G.994.1, the RSP timeout is specified as approximately 1 minute. For spans with no more than one regenerator, this is ideal. For multi-regenerator spans, however, an STU may time out and initiate a new G.994.1 session before the SRU is prepared to begin the next phase of the train. In such cases, the SRU should respond to the G.994.1 initiation and issue an MS message with the RSP bit set to hold off the STU once again. For its part, the SRU should implement an internal timer and should not consider a start-up to have failed until that timer has expired. The timer should be started when the SRU receives a RSP bit in an MS message and should not expire for at least 4 minutes. + +If any segment must retrain due to line conditions or other causes, each segment of the span shall be deactivated and the full start-up procedure shall be reinitiated. + +### **III.5 Diagnostic mode activation** + +If a segment fails, the start-up procedure will also fail for the entire span. This would normally be characterized at the STU by being told to enter a silent interval via the RSP bit and never receiving another G.994.1 request. Without some diagnostic information, the service provider would have no easy way to test the integrity of the various segments. + +This concern is resolved by the use of the "Diagnostic Mode" in ITU-T Rec. G.994.1 to trigger a diagnostic training mode. This bit, when set, causes an SRU connected to a failed segment to act as an STU and allow the start-up procedure to finish. In this way, all of the segments before the failed segment may be tested using loopbacks and EOC-initiated tests, allowing network operators to quickly isolate the segment where the failure has occurred. + +## **Appendix IV** + +### **Tabulation of Annex B noise profiles** + +Appendix IV tabulates the total noise profile (sum of self and alien) corresponding to 0 dB of margin for all the Annex B test cases. Those noise PSDs were used during the theoretical computation of the margin. The tabulated noise profiles should be measured into the calibrating impedance (see B.3.3.1). + +Noise Profile Nomenclature: ABBBCDE + +A: Side (either C or R) + +BBB: Rate + +C: PSD type (either s for symmetric or a for asymmetric) + +D: Noise Type (A ,B, C or D) + +E: Loop Number (from 2 to 7). + +The noise shapes used for test #1 will be identical to Noise A of test #2 + +Table IV.1/G.991.2 – STU-C side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | +| C384sA2 | 114.9 | 99.2 | 95.0 | 93.1 | 92.5 | 92.3 | 92.9 | 93.9 | 93.4 | 92.7 | 92.0 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C384sC2 | 120.6 | 104.6 | 100.4 | 98.4 | 97.7 | 97.6 | 98.7 | 101.8 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C384sD2 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | +| C512sA2 | 114.9 | 99.4 | 95.3 | 93.4 | 92.8 | 92.3 | 92.0 | 91.9 | 92.0 | 92.2 | 91.9 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C512sC2 | 120.6 | 104.9 | 100.8 | 98.8 | 98.1 | 97.7 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C512sD2 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | +| C768sA2 | 114.9 | 99.6 | 95.6 | 93.7 | 93.3 | 92.8 | 92.4 | 91.9 | 91.2 | 90.7 | 90.3 | 88.1 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C768sC2 | 120.6 | 105.2 | 101.2 | 99.3 | 98.8 | 98.4 | 98.0 | 97.5 | 97.0 | 96.6 | 96.4 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C768sD2 | 134.2 | 107.3 | 102.2 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | +| C1024sA2 | 114.9 | 99.7 | 95.7 | 93.9 | 93.6 | 93.2 | 92.8 | 92.3 | 91.5 | 90.8 | 90.3 | 87.5 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C1024sC2 | 120.6 | 105.3 | 101.4 | 99.6 | 99.2 | 99.0 | 98.7 | 98.2 | 97.5 | 96.9 | 96.4 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C1024sD2 | 135.0 | 108.5 | 103.3 | 100.6 | 98.8 | 97.5 | 96.4 | 95.5 | 94.9 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | +| C1280sA2 | 114.9 | 99.7 | 95.8 | 93.9 | 93.8 | 93.5 | 93.1 | 92.6 | 91.8 | 91.1 | 90.4 | 87.3 | 86.0 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C1280sC2 | 120.6 | 105.4 | 101.5 | 99.7 | 99.5 | 99.4 | 99.3 | 98.8 | 98.0 | 97.4 | 96.8 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C1280sD2 | 135.7 | 109.4 | 104.3 | 101.5 | 99.7 | 98.3 | 97.2 | 96.3 | 95.5 | 94.9 | 94.4 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | +| C1536sA2 | 115.0 | 99.7 | 95.8 | 94.0 | 93.8 | 93.6 | 93.3 | 92.8 | 92.0 | 91.2 | 90.6 | 87.3 | 85.8 | 84.7 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | +| C1536sC2 | 120.6 | 105.4 | 101.5 | 99.8 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.3 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | +| C1536sD2 | 136.1 | 110.2 | 105.0 | 102.3 | 100.4 | 99.0 | 97.9 | 96.9 | 96.1 | 95.5 | 94.9 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | +| C2048sA2 | 115.0 | 99.7 | 95.7 | 93.9 | 93.8 | 93.6 | 93.3 | 92.8 | 91.9 | 91.2 | 90.5 | 87.2 | 85.5 | 84.3 | 83.5 | 82.8 | 82.1 | 79.4 | 77.6 | +| C2048sC2 | 120.6 | 105.4 | 101.5 | 99.8 | 99.6 | 99.7 | 99.7 | 99.4 | 98.5 | 97.8 | 97.2 | 93.1 | 91.6 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.8 | +| C2048sD2 | 136.3 | 110.4 | 105.2 | 102.5 | 100.6 | 99.1 | 98.0 | 97.0 | 96.2 | 95.5 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | +| C2304sA2 | 115.0 | 99.7 | 95.8 | 94.0 | 93.8 | 93.6 | 93.4 | 92.9 | 92.0 | 91.2 | 90.6 | 87.2 | 85.5 | 84.3 | 83.4 | 82.7 | 82.0 | 79.4 | 77.6 | +| C2304sC2 | 120.6 | 105.4 | 101.5 | 99.8 | 99.7 | 99.9 | 100.0 | 99.7 | 98.8 | 98.1 | 97.4 | 93.2 | 91.6 | 90.4 | 89.5 | 88.9 | 88.4 | 87.8 | 86.8 | +| C2304sD2 | 136.6 | 110.9 | 105.7 | 102.9 | 101.0 | 99.6 | 98.4 | 97.4 | 96.6 | 95.9 | 95.3 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | + +Table IV.1/G.991.2 – STU-C side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| C384sD3 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C512sD3 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C768sD3 | 134.1 | 107.3 | 102.2 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C1024sD3 | 135.0 | 108.5 | 103.3 | 100.6 | 98.8 | 97.4 | 96.4 | 95.5 | 94.8 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C1280sD3 | 135.6 | 109.4 | 104.2 | 101.5 | 99.7 | 98.3 | 97.2 | 96.2 | 95.5 | 94.9 | 94.3 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | | +| C1536sD3 | 136.1 | 110.1 | 105.0 | 102.3 | 100.4 | 99.0 | 97.8 | 96.9 | 96.1 | 95.4 | 94.8 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | | +| C2048sD3 | 136.3 | 110.3 | 105.2 | 102.4 | 100.5 | 99.1 | 97.9 | 96.9 | 96.1 | 95.4 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | | +| C2304sD3 | 136.6 | 110.8 | 105.6 | 102.9 | 101.0 | 99.5 | 98.3 | 97.4 | 96.5 | 95.8 | 95.2 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | | +| C384sA4 | 114.9 | 99.2 | 95.0 | 93.1 | 92.5 | 92.3 | 92.9 | 93.9 | 93.4 | 92.7 | 92.0 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C384sC4 | 120.6 | 104.6 | 100.4 | 98.4 | 97.7 | 97.6 | 98.7 | 101.8 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C512sA4 | 114.9 | 99.4 | 95.3 | 93.4 | 92.8 | 92.3 | 92.0 | 91.9 | 92.0 | 92.2 | 91.9 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C512sC4 | 120.6 | 104.9 | 100.8 | 98.8 | 98.1 | 97.7 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C768sA4 | 114.9 | 99.5 | 95.6 | 93.7 | 93.3 | 92.8 | 92.4 | 91.8 | 91.2 | 90.6 | 90.3 | 88.0 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C768sC4 | 120.6 | 105.2 | 101.2 | 99.3 | 98.7 | 98.4 | 98.0 | 97.5 | 97.0 | 96.6 | 96.4 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1024sA4 | 114.9 | 99.6 | 95.7 | 93.8 | 93.6 | 93.2 | 92.8 | 92.2 | 91.5 | 90.8 | 90.2 | 87.5 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1024sC4 | 120.6 | 105.3 | 101.4 | 99.6 | 99.2 | 99.0 | 98.7 | 98.2 | 97.5 | 96.9 | 96.4 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1280sA4 | 114.9 | 99.6 | 95.7 | 93.9 | 93.7 | 93.4 | 93.1 | 92.5 | 91.7 | 91.0 | 90.4 | 87.3 | 86.0 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1280sC4 | 120.6 | 105.3 | 101.5 | 99.7 | 99.4 | 99.4 | 99.2 | 98.8 | 98.0 | 97.3 | 96.8 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1536sA4 | 114.9 | 99.6 | 95.7 | 93.9 | 93.8 | 93.5 | 93.2 | 92.7 | 91.9 | 91.2 | 90.5 | 87.3 | 85.8 | 84.7 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1536sC4 | 120.6 | 105.3 | 101.5 | 99.8 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.3 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C2048sA4 | 115.0 | 99.6 | 95.6 | 93.9 | 93.7 | 93.5 | 93.2 | 92.6 | 91.8 | 91.0 | 90.4 | 87.1 | 85.5 | 84.3 | 83.5 | 82.8 | 82.1 | 79.4 | 77.6 | | +| C2048sC4 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.7 | 99.7 | 99.3 | 98.4 | 97.7 | 97.1 | 93.1 | 91.5 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.8 | | +| C2304sA4 | 115.0 | 99.6 | 95.6 | 93.9 | 93.7 | 93.5 | 93.2 | 92.7 | 91.8 | 91.1 | 90.4 | 87.1 | 85.4 | 84.2 | 83.4 | 82.7 | 82.0 | 79.4 | 77.6 | | +| C2304sC4 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.8 | 99.9 | 99.5 | 98.7 | 98.0 | 97.3 | 93.2 | 91.6 | 90.4 | 89.5 | 88.9 | 88.4 | 87.8 | 86.8 | | + +Table IV.1/G.991.2 – STU-C side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|------|------|------|------|------|------|------|------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| C384sB5 | 120.4 | 104.6 | 100.3 | 98.4 | 97.7 | 97.6 | 98.7 | 101.7 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C512sB5 | 120.4 | 104.9 | 100.7 | 98.8 | 98.0 | 97.6 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C768sB5 | 120.4 | 105.1 | 101.1 | 99.2 | 98.6 | 98.3 | 97.9 | 97.4 | 96.9 | 96.5 | 96.3 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1024sB5 | 120.4 | 105.2 | 101.2 | 99.4 | 99.0 | 98.8 | 98.5 | 98.0 | 97.4 | 96.8 | 96.3 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1280sB5 | 120.4 | 105.2 | 101.3 | 99.5 | 99.2 | 99.1 | 99.0 | 98.6 | 97.8 | 97.2 | 96.7 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1536sB5 | 120.4 | 105.1 | 101.2 | 99.5 | 99.3 | 99.3 | 99.3 | 98.9 | 98.2 | 97.5 | 97.0 | 93.2 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C2048sB5 | 120.4 | 105.0 | 101.1 | 99.3 | 99.1 | 99.1 | 99.1 | 98.7 | 97.9 | 97.3 | 96.7 | 93.0 | 91.5 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.9 | | +| C2304sB5 | 120.5 | 104.9 | 101.0 | 99.2 | 99.0 | 99.1 | 99.1 | 98.8 | 98.1 | 97.4 | 96.8 | 93.0 | 91.5 | 90.4 | 89.5 | 88.9 | 88.4 | 87.8 | 86.9 | | +| C384sA6 | 114.9 | 99.2 | 95.0 | 93.1 | 92.5 | 92.3 | 92.9 | 93.9 | 93.4 | 92.7 | 92.0 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C384sC6 | 120.6 | 104.6 | 100.4 | 98.4 | 97.7 | 97.6 | 98.7 | 101.8 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C512sA6 | 114.9 | 99.4 | 95.3 | 93.4 | 92.8 | 92.3 | 92.0 | 91.9 | 92.0 | 92.2 | 91.9 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C512sC6 | 120.6 | 104.9 | 100.8 | 98.8 | 98.1 | 97.7 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C768sA6 | 114.9 | 99.6 | 95.6 | 93.7 | 93.3 | 92.9 | 92.4 | 91.9 | 91.2 | 90.7 | 90.3 | 88.0 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C768sC6 | 120.6 | 105.2 | 101.2 | 99.3 | 98.8 | 98.4 | 98.0 | 97.5 | 97.0 | 96.6 | 96.4 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1024sA6 | 115.0 | 99.7 | 95.7 | 93.9 | 93.6 | 93.2 | 92.8 | 92.3 | 91.5 | 90.9 | 90.3 | 87.5 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1024sC6 | 120.6 | 105.3 | 101.4 | 99.6 | 99.2 | 99.0 | 98.7 | 98.2 | 97.5 | 96.9 | 96.4 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1280sA6 | 115.0 | 99.7 | 95.8 | 94.0 | 93.8 | 93.5 | 93.2 | 92.7 | 91.9 | 91.2 | 90.5 | 87.3 | 86.0 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1280sC6 | 120.6 | 105.4 | 101.5 | 99.7 | 99.5 | 99.4 | 99.3 | 98.8 | 98.1 | 97.4 | 96.8 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1536sA6 | 115.1 | 99.8 | 95.8 | 94.0 | 93.9 | 93.7 | 93.4 | 92.9 | 92.1 | 91.4 | 90.7 | 87.3 | 85.7 | 84.8 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1536sC6 | 120.6 | 105.4 | 101.5 | 99.8 | 99.6 | 99.8 | 99.8 | 99.4 | 98.6 | 97.9 | 97.3 | 93.3 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C2048sA6 | 115.4 | 100.0 | 95.9 | 94.0 | 93.9 | 93.7 | 93.4 | 93.0 | 92.1 | 91.4 | 90.7 | 87.2 | 85.5 | 84.4 | 83.5 | 82.8 | 82.1 | 79.4 | 77.6 | | +| C2048sC6 | 120.7 | 105.4 | 101.5 | 99.8 | 99.7 | 99.8 | 99.8 | 99.5 | 98.6 | 97.9 | 97.3 | 93.1 | 91.5 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.8 | | +| C2304sA6 | 115.6 | 100.2 | 96.0 | 94.1 | 94.0 | 93.8 | 93.6 | 93.1 | 92.3 | 91.5 | 90.9 | 87.3 | 85.5 | 84.4 | 83.4 | 82.7 | 82.0 | 79.4 | 77.6 | | +| C2304sC6 | 120.7 | 105.4 | 101.5 | 99.8 | 99.7 | 100.0 | 100.1 | 99.8 | 99.0 | 98.3 | 97.6 | 93.2 | 91.6 | 90.4 | 89.6 | 88.9 | 88.4 | 87.8 | 86.8 | | + +Table IV.1/G.991.2 – STU-C side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| C384sA7 | 114.9 | 99.2 | 95.0 | 93.1 | 92.5 | 92.3 | 92.9 | 93.9 | 93.4 | 92.7 | 92.0 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C384sB7 | 120.6 | 104.6 | 100.4 | 98.4 | 97.7 | 97.6 | 98.7 | 101.8 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C384sC7 | 120.6 | 104.6 | 100.4 | 98.4 | 97.7 | 97.6 | 98.7 | 101.8 | 102.6 | 102.0 | 101.3 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C384sD7 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C512sA7 | 114.9 | 99.4 | 95.3 | 93.4 | 92.8 | 92.3 | 92.0 | 91.9 | 92.0 | 92.2 | 91.9 | 88.1 | 86.3 | 85.0 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C512sB7 | 120.6 | 104.9 | 100.8 | 98.8 | 98.1 | 97.7 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C512sC7 | 120.6 | 104.9 | 100.8 | 98.8 | 98.1 | 97.7 | 97.4 | 97.5 | 98.3 | 100.0 | 100.9 | 94.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C512sD7 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C768sA7 | 114.9 | 99.5 | 95.6 | 93.7 | 93.3 | 92.8 | 92.4 | 91.8 | 91.2 | 90.7 | 90.3 | 88.1 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C768sB7 | 120.6 | 105.2 | 101.2 | 99.3 | 98.7 | 98.4 | 98.0 | 97.5 | 97.0 | 96.6 | 96.4 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C768sC7 | 120.6 | 105.2 | 101.2 | 99.3 | 98.7 | 98.4 | 98.0 | 97.5 | 97.0 | 96.6 | 96.4 | 94.4 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C768sD7 | 134.1 | 107.2 | 102.1 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C1024sA7 | 114.9 | 99.6 | 95.7 | 93.8 | 93.6 | 93.2 | 92.8 | 92.2 | 91.5 | 90.8 | 90.3 | 87.5 | 86.3 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1024sB7 | 120.6 | 105.3 | 101.4 | 99.6 | 99.2 | 99.0 | 98.7 | 98.2 | 97.5 | 96.9 | 96.4 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1024sC7 | 120.6 | 105.3 | 101.4 | 99.6 | 99.2 | 99.0 | 98.7 | 98.2 | 97.5 | 96.9 | 96.4 | 93.5 | 92.7 | 91.4 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1024sD7 | 135.0 | 108.4 | 103.3 | 100.6 | 98.8 | 97.4 | 96.4 | 95.5 | 94.9 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | | +| C1280sA7 | 114.9 | 99.6 | 95.7 | 93.9 | 93.7 | 93.4 | 93.1 | 92.6 | 91.8 | 91.1 | 90.4 | 87.3 | 86.0 | 84.9 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1280sB7 | 120.6 | 105.3 | 101.5 | 99.7 | 99.4 | 99.4 | 99.2 | 98.8 | 98.0 | 97.4 | 96.8 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1280sC7 | 120.6 | 105.3 | 101.5 | 99.7 | 99.4 | 99.4 | 99.2 | 98.8 | 98.0 | 97.4 | 96.8 | 93.2 | 92.2 | 91.3 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1280sD7 | 135.7 | 109.4 | 104.2 | 101.5 | 99.7 | 98.3 | 97.2 | 96.3 | 95.5 | 94.9 | 94.3 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | | +| C1536sA7 | 115.0 | 99.7 | 95.7 | 93.9 | 93.8 | 93.6 | 93.3 | 92.8 | 91.9 | 91.2 | 90.6 | 87.3 | 85.8 | 84.8 | 83.8 | 82.9 | 82.1 | 79.4 | 77.6 | | +| C1536sB7 | 120.6 | 105.3 | 101.5 | 99.8 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.3 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.9 | | +| C1536sC7 | 120.6 | 105.3 | 101.5 | 99.8 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.3 | 91.9 | 91.1 | 90.2 | 89.3 | 88.5 | 87.8 | 86.8 | | +| C1536sD7 | 136.1 | 110.1 | 105.0 | 102.2 | 100.4 | 99.0 | 97.8 | 96.9 | 96.1 | 95.5 | 94.9 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | | + +Table IV.1/G.991.2 – STU-C side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|------|------|------|------|------|------|------|------|------|------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| C2048sA7 | 115.0 | 99.7 | 95.7 | 93.9 | 93.7 | 93.5 | 93.2 | 92.7 | 91.9 | 91.2 | 90.5 | 87.2 | 85.5 | 84.4 | 83.5 | 82.8 | 82.1 | 79.4 | 77.6 | | +| C2048sB7 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.1 | 91.6 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.9 | | +| C2048sC7 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.7 | 99.7 | 99.3 | 98.5 | 97.8 | 97.2 | 93.1 | 91.6 | 90.4 | 89.7 | 89.2 | 88.5 | 87.8 | 86.8 | | +| C2048sD7 | 136.3 | 110.3 | 105.1 | 102.4 | 100.5 | 99.1 | 98.0 | 97.0 | 96.2 | 95.5 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | | +| C2304sA7 | 115.1 | 99.7 | 95.7 | 93.9 | 93.8 | 93.6 | 93.3 | 92.8 | 92.0 | 91.2 | 90.6 | 87.2 | 85.5 | 84.3 | 83.4 | 82.7 | 82.0 | 79.4 | 77.6 | | +| C2304sB7 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.8 | 99.9 | 99.6 | 98.8 | 98.1 | 97.4 | 93.2 | 91.6 | 90.4 | 89.6 | 88.9 | 88.4 | 87.8 | 86.9 | | +| C2304sC7 | 120.6 | 105.3 | 101.4 | 99.7 | 99.6 | 99.8 | 99.9 | 99.6 | 98.8 | 98.1 | 97.4 | 93.2 | 91.6 | 90.4 | 89.6 | 88.9 | 88.4 | 87.8 | 86.8 | | +| C2304sD7 | 136.6 | 110.8 | 105.6 | 102.9 | 101.0 | 99.5 | 98.4 | 97.4 | 96.6 | 95.9 | 95.3 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | | + +Table IV.2/G.991.2 – STU-C side/asymmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|------|------|------|------|------|------|------|-------|-------|-------|-------|-------|--| +| | 1 | 20 | 40 | 60 | 80 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 500 | 600 | 700 | 800 | 1000 | 1200 | 1400 | | +| C2048aA2 | 115.0 | 95.8 | 93.9 | 93.5 | 92.1 | 90.7 | 87.2 | 85.5 | 84.2 | 83.2 | 82.3 | 81.5 | 80.3 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2048aC2 | 120.6 | 101.6 | 99.8 | 100.1 | 99.0 | 97.5 | 93.2 | 91.5 | 90.2 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2048aD2 | 136.6 | 105.8 | 101.2 | 98.6 | 96.7 | 95.3 | 92.8 | 91.0 | 89.8 | 88.8 | 88.1 | 87.6 | 87.9 | 93.1 | 101.7 | 110.3 | 126.3 | 138.0 | 138.0 | | +| C2304aA2 | 115.0 | 95.8 | 94.0 | 93.8 | 92.5 | 91.1 | 87.5 | 85.7 | 84.4 | 83.4 | 82.5 | 81.8 | 80.4 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2304aC2 | 120.6 | 101.6 | 100.0 | 100.9 | 100.1 | 98.7 | 93.7 | 92.0 | 90.6 | 89.6 | 88.7 | 87.9 | 86.6 | 87.6 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2304aD2 | 137.5 | 107.5 | 102.9 | 100.3 | 98.5 | 97.0 | 94.5 | 92.8 | 91.5 | 90.5 | 89.7 | 89.1 | 88.7 | 92.0 | 99.6 | 107.6 | 122.5 | 135.2 | 138.0 | | +| C2048aD3 | 136.6 | 105.7 | 101.1 | 98.5 | 96.6 | 95.2 | 92.7 | 91.0 | 89.8 | 88.8 | 88.1 | 87.6 | 87.9 | 93.1 | 101.7 | 110.3 | 126.3 | 138.0 | 138.0 | | +| C2304aD3 | 137.5 | 107.4 | 102.8 | 100.2 | 98.3 | 96.9 | 94.4 | 92.7 | 91.5 | 90.5 | 89.7 | 89.1 | 88.7 | 92.0 | 99.6 | 107.6 | 122.5 | 135.2 | 138.0 | | +| C2048aA4 | 114.9 | 95.7 | 93.8 | 93.4 | 92.0 | 90.6 | 87.2 | 85.5 | 84.2 | 83.2 | 82.3 | 81.5 | 80.3 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | + +Table IV.2/G.991.2 – STU-C side/asymmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|------|------|------|------|------|------|------|-------|-------|-------|-------|-------|--| +| | 1 | 20 | 40 | 60 | 80 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 500 | 600 | 700 | 800 | 1000 | 1200 | 1400 | | +| C2048aC4 | 120.6 | 101.5 | 99.7 | 100.0 | 98.8 | 97.4 | 93.2 | 91.5 | 90.1 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2304aA4 | 115.0 | 95.7 | 93.9 | 93.6 | 92.3 | 90.9 | 87.4 | 85.7 | 84.4 | 83.4 | 82.5 | 81.8 | 80.4 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2304aC4 | 120.6 | 101.5 | 99.9 | 100.8 | 99.9 | 98.5 | 93.7 | 92.0 | 90.6 | 89.6 | 88.7 | 87.9 | 86.6 | 87.6 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2048aB5 | 120.4 | 101.1 | 99.2 | 99.3 | 98.2 | 97.0 | 93.1 | 91.4 | 90.1 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.7 | 86.9 | 85.4 | 88.2 | 94.5 | | +| C2304aB5 | 120.4 | 101.1 | 99.3 | 99.9 | 99.1 | 97.9 | 93.5 | 91.9 | 90.6 | 89.5 | 88.7 | 87.9 | 86.6 | 87.6 | 87.7 | 86.9 | 85.4 | 88.2 | 94.5 | | +| C2048aA6 | 115.2 | 95.8 | 94.0 | 93.6 | 92.3 | 90.9 | 87.3 | 85.5 | 84.2 | 83.2 | 82.3 | 81.5 | 80.3 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2048aC6 | 120.6 | 101.6 | 99.8 | 100.2 | 99.1 | 97.6 | 93.2 | 91.5 | 90.2 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2304aA6 | 115.4 | 96.0 | 94.1 | 94.0 | 92.8 | 91.3 | 87.5 | 85.7 | 84.5 | 83.4 | 82.5 | 81.8 | 80.4 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2304aC6 | 120.7 | 101.6 | 100.0 | 101.1 | 100.3 | 98.8 | 93.7 | 92.0 | 90.6 | 89.6 | 88.7 | 87.9 | 86.6 | 87.6 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2048aA7 | 115.0 | 95.7 | 93.8 | 93.4 | 92.1 | 90.7 | 87.2 | 85.5 | 84.2 | 83.2 | 82.3 | 81.5 | 80.3 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2048aB7 | 120.6 | 101.5 | 99.7 | 100.1 | 98.9 | 97.5 | 93.2 | 91.5 | 90.2 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.7 | 86.9 | 85.4 | 88.2 | 94.5 | | +| C2048aC7 | 120.6 | 101.5 | 99.7 | 100.1 | 98.9 | 97.5 | 93.2 | 91.5 | 90.2 | 89.1 | 88.2 | 87.5 | 86.5 | 87.7 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2048aD7 | 136.6 | 105.7 | 101.1 | 98.5 | 96.7 | 95.3 | 92.7 | 91.0 | 89.8 | 88.8 | 88.1 | 87.6 | 87.9 | 93.1 | 101.7 | 110.3 | 126.3 | 138.0 | 138.0 | | +| C2304aA7 | 115.1 | 95.8 | 93.9 | 93.7 | 92.4 | 91.0 | 87.5 | 85.7 | 84.4 | 83.4 | 82.5 | 81.8 | 80.4 | 79.4 | 78.4 | 77.6 | 76.1 | 79.0 | 85.6 | | +| C2304aB7 | 120.6 | 101.5 | 99.9 | 100.9 | 100.0 | 98.6 | 93.7 | 92.0 | 90.6 | 89.6 | 88.7 | 87.9 | 86.6 | 87.6 | 87.7 | 86.9 | 85.4 | 88.2 | 94.5 | | +| C2304aC7 | 120.6 | 101.5 | 99.9 | 100.9 | 100.0 | 98.6 | 93.7 | 92.0 | 90.6 | 89.6 | 88.7 | 87.9 | 86.6 | 87.6 | 87.6 | 86.8 | 85.3 | 87.9 | 93.8 | | +| C2304aD7 | 137.5 | 107.4 | 102.8 | 100.2 | 98.4 | 97.0 | 94.5 | 92.7 | 91.5 | 90.5 | 89.7 | 89.1 | 88.7 | 92.0 | 99.6 | 107.6 | 122.5 | 135.2 | 138.0 | | + +Table IV.3/G.991.2 – STU-R side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| R384sA2 | 114.9 | 99.2 | 95.3 | 93.7 | 92.6 | 92.1 | 92.3 | 92.4 | 91.8 | 91.0 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 123.1 | 115.4 | | +| R384sC2 | 120.6 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R384sD2 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R512sA2 | 114.9 | 99.4 | 95.7 | 94.1 | 92.9 | 92.1 | 91.6 | 91.1 | 90.9 | 90.8 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 122.5 | 115.4 | | +| R512sC2 | 120.6 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.4 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R512sD2 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R768sA2 | 114.9 | 99.6 | 96.0 | 94.5 | 93.4 | 92.6 | 91.9 | 91.0 | 90.4 | 89.8 | 89.3 | 87.9 | 86.1 | 84.8 | 87.3 | 93.0 | 98.0 | 117.7 | 114.9 | | +| R768sC2 | 120.6 | 105.2 | 101.0 | 98.9 | 98.1 | 97.5 | 96.9 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R768sD2 | 134.2 | 107.3 | 102.2 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1024sA2 | 114.9 | 99.7 | 96.1 | 94.7 | 93.7 | 92.9 | 92.2 | 91.3 | 90.6 | 89.9 | 89.3 | 87.4 | 86.1 | 84.8 | 87.3 | 93.0 | 97.8 | 113.4 | 113.5 | | +| R1024sC2 | 120.6 | 105.3 | 101.2 | 99.1 | 98.5 | 97.9 | 97.3 | 96.7 | 95.9 | 95.3 | 94.7 | 93.5 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1024sD2 | 135.0 | 108.5 | 103.3 | 100.6 | 98.8 | 97.5 | 96.4 | 95.5 | 94.9 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1280sA2 | 114.9 | 99.7 | 96.1 | 94.8 | 93.9 | 93.1 | 92.5 | 91.6 | 90.8 | 90.1 | 89.5 | 87.2 | 85.9 | 84.7 | 87.2 | 92.8 | 97.4 | 108.6 | 110.3 | | +| R1280sC2 | 120.6 | 105.4 | 101.3 | 99.2 | 98.7 | 98.2 | 97.7 | 97.1 | 96.2 | 95.5 | 94.9 | 93.2 | 92.8 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1280sD2 | 135.7 | 109.4 | 104.3 | 101.5 | 99.7 | 98.3 | 97.2 | 96.3 | 95.5 | 94.9 | 94.4 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | | +| R1536sA2 | 115.0 | 99.7 | 96.1 | 94.9 | 94.0 | 93.3 | 92.6 | 91.7 | 90.9 | 90.2 | 89.6 | 87.2 | 85.6 | 84.6 | 87.1 | 92.6 | 96.8 | 104.4 | 106.2 | | +| R1536sC2 | 120.6 | 105.4 | 101.3 | 99.3 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.3 | 92.4 | 91.8 | 94.7 | 99.6 | 101.4 | 99.8 | 96.9 | | +| R1536sD2 | 136.1 | 110.2 | 105.0 | 102.3 | 100.4 | 99.0 | 97.9 | 96.9 | 96.1 | 95.5 | 94.9 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | | +| R2048sA2 | 115.0 | 99.7 | 96.1 | 94.8 | 94.0 | 93.2 | 92.6 | 91.7 | 90.9 | 90.1 | 89.5 | 87.1 | 85.4 | 84.2 | 86.2 | 90.4 | 94.7 | 100.6 | 102.0 | | +| R2048sC2 | 120.6 | 105.4 | 101.3 | 99.3 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.1 | 92.0 | 91.0 | 92.6 | 96.2 | 100.1 | 99.7 | 96.9 | | +| R2048sD2 | 136.3 | 110.4 | 105.2 | 102.5 | 100.6 | 99.1 | 98.0 | 97.0 | 96.2 | 95.5 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | | +| R2304sA2 | 115.0 | 99.7 | 96.1 | 94.8 | 94.0 | 93.3 | 92.7 | 91.8 | 90.9 | 90.2 | 89.6 | 87.1 | 85.4 | 84.1 | 85.8 | 88.5 | 91.3 | 98.0 | 99.1 | | +| R2304sC2 | 120.6 | 105.4 | 101.3 | 99.3 | 98.8 | 98.4 | 98.0 | 97.5 | 96.6 | 95.9 | 95.2 | 93.2 | 92.0 | 90.9 | 92.2 | 93.9 | 96.7 | 99.7 | 96.8 | | +| R2304sD2 | 136.6 | 110.9 | 105.7 | 102.9 | 101.0 | 99.6 | 98.4 | 97.4 | 96.6 | 95.9 | 95.3 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | | + +Table IV.3/G.991.2 – STU-R side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| R384sD3 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R512sD3 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R768sD3 | 134.1 | 107.3 | 102.2 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1024sD3 | 135.0 | 108.5 | 103.3 | 100.6 | 98.8 | 97.4 | 96.4 | 95.5 | 94.8 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1280sD3 | 135.6 | 109.4 | 104.2 | 101.5 | 99.7 | 98.3 | 97.2 | 96.2 | 95.5 | 94.9 | 94.3 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | | +| R1536sD3 | 136.1 | 110.1 | 105.0 | 102.3 | 100.4 | 99.0 | 97.8 | 96.9 | 96.1 | 95.4 | 94.8 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | | +| R2048sD3 | 136.3 | 110.3 | 105.2 | 102.4 | 100.5 | 99.1 | 97.9 | 96.9 | 96.1 | 95.4 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | | +| R2304sD3 | 136.6 | 110.8 | 105.6 | 102.9 | 101.0 | 99.5 | 98.3 | 97.4 | 96.5 | 95.8 | 95.2 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | | +| R384sA4 | 114.9 | 99.2 | 95.3 | 93.7 | 92.6 | 92.1 | 92.3 | 92.4 | 91.8 | 91.0 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 123.1 | 115.4 | | +| R384sC4 | 120.6 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R512sA4 | 114.9 | 99.4 | 95.6 | 94.0 | 92.9 | 92.1 | 91.6 | 91.0 | 90.9 | 90.8 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 122.8 | 115.4 | | +| R512sC4 | 120.6 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.4 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R768sA4 | 114.9 | 99.5 | 95.9 | 94.5 | 93.4 | 92.6 | 91.9 | 91.0 | 90.3 | 89.8 | 89.3 | 87.9 | 86.1 | 84.8 | 87.3 | 93.0 | 98.0 | 119.3 | 115.2 | | +| R768sC4 | 120.6 | 105.2 | 101.0 | 98.9 | 98.1 | 97.5 | 96.9 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1024sA4 | 114.9 | 99.6 | 96.1 | 94.7 | 93.7 | 92.9 | 92.2 | 91.3 | 90.5 | 89.9 | 89.3 | 87.4 | 86.1 | 84.8 | 87.3 | 93.0 | 97.9 | 115.1 | 114.3 | | +| R1024sC4 | 120.6 | 105.3 | 101.2 | 99.1 | 98.5 | 97.9 | 97.3 | 96.7 | 95.9 | 95.3 | 94.7 | 93.5 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1280sA4 | 114.9 | 99.6 | 96.1 | 94.8 | 93.9 | 93.1 | 92.4 | 91.5 | 90.7 | 90.0 | 89.4 | 87.2 | 85.9 | 84.7 | 87.2 | 92.9 | 97.5 | 110.0 | 111.6 | | +| R1280sC4 | 120.6 | 105.3 | 101.2 | 99.2 | 98.7 | 98.1 | 97.6 | 97.0 | 96.2 | 95.5 | 94.9 | 93.2 | 92.8 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1536sA4 | 114.9 | 99.6 | 96.1 | 94.8 | 93.9 | 93.2 | 92.6 | 91.7 | 90.8 | 90.1 | 89.5 | 87.2 | 85.6 | 84.6 | 87.1 | 92.6 | 96.9 | 105.5 | 107.7 | | +| R1536sC4 | 120.6 | 105.3 | 101.3 | 99.3 | 98.8 | 98.3 | 97.9 | 97.3 | 96.4 | 95.7 | 95.1 | 93.2 | 92.4 | 91.8 | 94.7 | 99.6 | 101.4 | 99.8 | 96.9 | | +| R2048sA4 | 115.0 | 99.6 | 96.0 | 94.7 | 93.9 | 93.1 | 92.5 | 91.6 | 90.8 | 90.1 | 89.4 | 87.0 | 85.4 | 84.2 | 86.1 | 90.4 | 94.6 | 100.8 | 102.6 | | +| R2048sC4 | 120.6 | 105.3 | 101.2 | 99.2 | 98.7 | 98.3 | 97.9 | 97.3 | 96.4 | 95.7 | 95.0 | 93.1 | 92.0 | 91.0 | 92.6 | 96.2 | 100.1 | 99.8 | 96.9 | | +| R2304sA4 | 115.0 | 99.6 | 96.0 | 94.7 | 93.9 | 93.2 | 92.6 | 91.7 | 90.8 | 90.1 | 89.5 | 87.0 | 85.3 | 84.1 | 85.8 | 88.4 | 91.2 | 98.1 | 99.5 | | +| R2304sC4 | 120.6 | 105.3 | 101.2 | 99.2 | 98.8 | 98.4 | 98.0 | 97.4 | 96.6 | 95.8 | 95.2 | 93.2 | 92.0 | 90.9 | 92.1 | 93.9 | 96.7 | 99.7 | 96.8 | | + +Table IV.3/G.991.2 – STU-R side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|------|------|------|------|------|------|------|------|------|------|------|------|------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| R384sB5 | 120.4 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 129.0 | 121.3 | | +| R512sB5 | 120.4 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.3 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 129.0 | 121.3 | | +| R768sB5 | 120.4 | 105.1 | 100.9 | 98.8 | 98.0 | 97.4 | 96.8 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 128.7 | 121.3 | | +| R1024sB5 | 120.4 | 105.2 | 101.1 | 99.0 | 98.3 | 97.8 | 97.2 | 96.6 | 95.9 | 95.2 | 94.7 | 93.5 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 128.1 | 121.3 | | +| R1280sB5 | 120.4 | 105.2 | 101.1 | 99.0 | 98.5 | 98.0 | 97.5 | 96.9 | 96.1 | 95.5 | 94.8 | 93.2 | 92.8 | 92.1 | 93.9 | 98.2 | 101.9 | 126.1 | 121.2 | | +| R1536sB5 | 120.4 | 105.1 | 101.1 | 99.0 | 98.6 | 98.1 | 97.7 | 97.2 | 96.3 | 95.6 | 95.0 | 93.2 | 92.3 | 91.8 | 93.8 | 98.2 | 101.9 | 122.8 | 120.8 | | +| R2048sB5 | 120.4 | 105.0 | 100.9 | 98.9 | 98.4 | 98.0 | 97.6 | 97.1 | 96.2 | 95.5 | 94.9 | 93.0 | 91.9 | 90.9 | 92.2 | 95.7 | 100.2 | 115.8 | 118.4 | | +| R2304sB5 | 120.5 | 104.9 | 100.9 | 98.8 | 98.4 | 98.0 | 97.7 | 97.2 | 96.3 | 95.6 | 95.0 | 93.0 | 91.9 | 90.9 | 91.7 | 93.6 | 96.7 | 111.7 | 115.7 | | +| R384sA6 | 114.9 | 99.2 | 95.3 | 93.7 | 92.6 | 92.1 | 92.3 | 92.4 | 91.8 | 91.0 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 122.6 | 115.4 | | +| R384sC6 | 120.6 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R512sA6 | 114.9 | 99.4 | 95.6 | 94.1 | 92.9 | 92.1 | 91.6 | 91.1 | 90.9 | 90.8 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.0 | 120.2 | 115.2 | | +| R512sC6 | 120.6 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.4 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R768sA6 | 114.9 | 99.6 | 95.9 | 94.5 | 93.4 | 92.6 | 91.9 | 91.1 | 90.4 | 89.8 | 89.3 | 87.9 | 86.1 | 84.8 | 87.3 | 93.0 | 97.8 | 111.7 | 112.2 | | +| R768sC6 | 120.6 | 105.2 | 101.0 | 98.9 | 98.1 | 97.5 | 96.9 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1024sA6 | 115.0 | 99.7 | 96.1 | 94.7 | 93.8 | 92.9 | 92.3 | 91.4 | 90.6 | 89.9 | 89.4 | 87.4 | 86.1 | 84.8 | 87.3 | 92.8 | 97.3 | 106.6 | 107.9 | | +| R1024sC6 | 120.6 | 105.3 | 101.2 | 99.1 | 98.5 | 97.9 | 97.3 | 96.7 | 96.0 | 95.3 | 94.7 | 93.5 | 93.4 | 92.1 | 94.8 | 99.7 | 101.4 | 99.8 | 96.9 | | +| R1280sA6 | 115.0 | 99.7 | 96.1 | 94.9 | 93.9 | 93.2 | 92.5 | 91.6 | 90.8 | 90.1 | 89.5 | 87.2 | 85.8 | 84.7 | 87.2 | 92.6 | 96.7 | 102.9 | 103.8 | | +| R1280sC6 | 120.6 | 105.4 | 101.2 | 99.2 | 98.7 | 98.2 | 97.7 | 97.1 | 96.3 | 95.5 | 94.9 | 93.2 | 92.8 | 92.1 | 94.8 | 99.6 | 101.3 | 99.8 | 96.9 | | +| R1536sA6 | 115.1 | 99.8 | 96.2 | 94.9 | 94.1 | 93.3 | 92.7 | 91.8 | 91.0 | 90.3 | 89.6 | 87.2 | 85.6 | 84.6 | 87.2 | 92.2 | 95.8 | 99.6 | 100.5 | | +| R1536sC6 | 120.6 | 105.4 | 101.3 | 99.3 | 98.8 | 98.4 | 97.9 | 97.3 | 96.5 | 95.8 | 95.1 | 93.2 | 92.3 | 91.8 | 94.7 | 99.5 | 101.2 | 99.7 | 96.9 | | +| R2048sA6 | 115.4 | 100.0 | 96.3 | 94.9 | 94.1 | 93.3 | 92.7 | 91.8 | 91.0 | 90.3 | 89.6 | 87.1 | 85.4 | 84.3 | 86.3 | 90.0 | 93.5 | 96.1 | 95.8 | | +| R2048sC6 | 120.7 | 105.4 | 101.3 | 99.3 | 98.8 | 98.4 | 98.0 | 97.4 | 96.5 | 95.8 | 95.1 | 93.1 | 91.9 | 91.0 | 92.6 | 96.1 | 99.9 | 99.6 | 96.8 | | +| R2304sA6 | 115.6 | 100.2 | 96.4 | 95.0 | 94.2 | 93.4 | 92.8 | 91.9 | 91.1 | 90.4 | 89.7 | 87.1 | 85.4 | 84.3 | 86.0 | 88.3 | 90.8 | 93.8 | 93.8 | | +| R2304sC6 | 120.7 | 105.4 | 101.3 | 99.3 | 98.9 | 98.5 | 98.1 | 97.5 | 96.7 | 95.9 | 95.2 | 93.2 | 92.0 | 91.0 | 92.2 | 93.8 | 96.6 | 99.4 | 96.7 | | + +Table IV.3/G.991.2 – STU-R side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| R384sA7 | 114.9 | 99.2 | 95.3 | 93.7 | 92.6 | 92.1 | 92.3 | 92.4 | 91.8 | 91.0 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 123.1 | 115.4 | | +| R384sB7 | 120.6 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 129.0 | 121.3 | | +| R384sC7 | 120.6 | 104.6 | 100.2 | 98.1 | 97.3 | 96.9 | 97.3 | 98.2 | 97.6 | 96.9 | 96.2 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R384sD7 | 131.8 | 104.4 | 99.5 | 97.1 | 95.8 | 95.3 | 96.4 | 100.5 | 107.0 | 114.2 | 121.6 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R512sA7 | 114.9 | 99.4 | 95.6 | 94.0 | 92.9 | 92.1 | 91.6 | 91.0 | 90.9 | 90.8 | 90.4 | 87.9 | 86.2 | 84.8 | 87.3 | 93.1 | 98.1 | 122.9 | 115.4 | | +| R512sB7 | 120.6 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.4 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 129.0 | 121.3 | | +| R512sC7 | 120.6 | 104.9 | 100.6 | 98.4 | 97.6 | 96.9 | 96.5 | 96.3 | 96.4 | 96.5 | 96.1 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R512sD7 | 132.8 | 105.6 | 100.6 | 98.0 | 96.4 | 95.4 | 94.8 | 94.8 | 95.8 | 98.7 | 103.2 | 131.4 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R768sA7 | 114.9 | 99.5 | 95.9 | 94.5 | 93.4 | 92.6 | 91.9 | 91.0 | 90.3 | 89.8 | 89.3 | 87.9 | 86.1 | 84.8 | 87.3 | 93.1 | 98.0 | 120.5 | 115.3 | | +| R768sB7 | 120.6 | 105.2 | 101.0 | 98.9 | 98.1 | 97.5 | 96.9 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 128.8 | 121.3 | | +| R768sC7 | 120.6 | 105.2 | 101.0 | 98.9 | 98.1 | 97.5 | 96.9 | 96.3 | 95.6 | 95.1 | 94.7 | 94.4 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R768sD7 | 134.1 | 107.2 | 102.1 | 99.5 | 97.7 | 96.5 | 95.5 | 94.8 | 94.3 | 93.9 | 93.8 | 102.6 | 120.9 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1024sA7 | 114.9 | 99.6 | 96.0 | 94.7 | 93.7 | 92.9 | 92.2 | 91.3 | 90.6 | 89.9 | 89.3 | 87.4 | 86.1 | 84.8 | 87.3 | 93.0 | 97.9 | 117.3 | 114.8 | | +| R1024sB7 | 120.6 | 105.3 | 101.2 | 99.1 | 98.5 | 97.9 | 97.3 | 96.7 | 95.9 | 95.3 | 94.7 | 93.5 | 93.4 | 92.1 | 93.9 | 98.2 | 102.0 | 128.3 | 121.3 | | +| R1024sC7 | 120.6 | 105.3 | 101.2 | 99.1 | 98.5 | 97.9 | 97.3 | 96.7 | 95.9 | 95.3 | 94.7 | 93.5 | 93.4 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1024sD7 | 135.0 | 108.4 | 103.3 | 100.6 | 98.8 | 97.4 | 96.4 | 95.5 | 94.9 | 94.3 | 93.9 | 93.6 | 102.1 | 115.8 | 130.8 | 138.0 | 138.0 | 138.0 | 138.0 | | +| R1280sA7 | 114.9 | 99.6 | 96.1 | 94.8 | 93.9 | 93.1 | 92.5 | 91.5 | 90.8 | 90.1 | 89.5 | 87.2 | 85.9 | 84.8 | 87.3 | 92.9 | 97.7 | 113.2 | 113.3 | | +| R1280sB7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.7 | 98.1 | 97.7 | 97.1 | 96.2 | 95.5 | 94.9 | 93.2 | 92.8 | 92.1 | 93.9 | 98.2 | 101.9 | 127.0 | 121.2 | | +| R1280sC7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.7 | 98.1 | 97.7 | 97.1 | 96.2 | 95.5 | 94.9 | 93.2 | 92.8 | 92.1 | 94.8 | 99.7 | 101.5 | 99.8 | 96.9 | | +| R1280sD7 | 135.7 | 109.4 | 104.2 | 101.5 | 99.7 | 98.3 | 97.2 | 96.3 | 95.5 | 94.9 | 94.3 | 92.8 | 94.0 | 101.7 | 112.6 | 124.2 | 136.9 | 138.0 | 138.0 | | +| R1536sA7 | 115.0 | 99.7 | 96.1 | 94.8 | 93.9 | 93.2 | 92.6 | 91.7 | 90.9 | 90.2 | 89.6 | 87.2 | 85.6 | 84.6 | 87.2 | 92.8 | 97.3 | 108.8 | 110.3 | | +| R1536sB7 | 120.6 | 105.3 | 101.3 | 99.3 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.2 | 92.4 | 91.8 | 93.9 | 98.2 | 101.9 | 124.9 | 121.0 | | +| R1536sC7 | 120.6 | 105.3 | 101.3 | 99.3 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.2 | 92.4 | 91.8 | 94.7 | 99.6 | 101.4 | 99.8 | 96.9 | | +| R1536sD7 | 136.1 | 110.1 | 105.0 | 102.2 | 100.4 | 99.0 | 97.8 | 96.9 | 96.1 | 95.5 | 94.9 | 92.9 | 92.3 | 94.4 | 101.4 | 110.4 | 119.9 | 138.0 | 138.0 | | + +Table IV.3/G.991.2 – STU-R side/symmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|-------|-------|------|------|------|------|------|------|------|------|------|------|------|-------|-------|-------|--| +| | 1 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 600 | 800 | | +| R2048sA7 | 115.0 | 99.7 | 96.0 | 94.7 | 93.9 | 93.2 | 92.6 | 91.7 | 90.8 | 90.1 | 89.5 | 87.1 | 85.4 | 84.2 | 86.2 | 90.6 | 95.4 | 104.5 | 106.2 | | +| R2048sB7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.1 | 92.0 | 91.0 | 92.2 | 95.8 | 100.4 | 121.1 | 120.2 | | +| R2048sC7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.8 | 98.3 | 97.9 | 97.3 | 96.5 | 95.7 | 95.1 | 93.1 | 92.0 | 91.0 | 92.6 | 96.3 | 100.2 | 99.8 | 96.9 | | +| R2048sD7 | 136.3 | 110.3 | 105.1 | 102.4 | 100.5 | 99.1 | 98.0 | 97.0 | 96.2 | 95.5 | 94.8 | 92.6 | 91.3 | 90.7 | 91.2 | 94.1 | 99.8 | 128.9 | 138.0 | | +| R2304sA7 | 115.1 | 99.7 | 96.1 | 94.8 | 93.9 | 93.2 | 92.6 | 91.7 | 90.9 | 90.2 | 89.6 | 87.1 | 85.4 | 84.2 | 86.0 | 88.7 | 91.8 | 102.1 | 103.6 | | +| R2304sB7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.8 | 98.4 | 98.0 | 97.5 | 96.6 | 95.9 | 95.2 | 93.2 | 92.0 | 91.0 | 91.8 | 93.7 | 96.9 | 116.6 | 118.9 | | +| R2304sC7 | 120.6 | 105.3 | 101.2 | 99.2 | 98.8 | 98.4 | 98.0 | 97.5 | 96.6 | 95.9 | 95.2 | 93.2 | 92.0 | 91.0 | 92.2 | 93.9 | 96.8 | 99.8 | 96.9 | | +| R2304sD7 | 136.6 | 110.8 | 105.6 | 102.9 | 101.0 | 99.5 | 98.4 | 97.4 | 96.6 | 95.9 | 95.3 | 92.9 | 91.5 | 90.7 | 90.4 | 91.3 | 94.4 | 118.1 | 138.0 | | + +Table IV.4/G.991.2 – STU-R side/asymmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|------|------|------|------|------|------|------|------|------|-------|-------|-------|-------|-------|-------|-------|--| +| | 1 | 20 | 40 | 60 | 80 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 500 | 600 | 700 | 800 | 1000 | 1200 | 1400 | | +| R2048aA2 | 115.0 | 96.0 | 93.6 | 92.0 | 90.3 | 88.9 | 86.5 | 84.9 | 83.8 | 85.4 | 89.5 | 94.8 | 100.7 | 103.2 | 104.0 | 105.0 | 107.4 | 113.3 | 121.7 | | +| R2048aC2 | 120.6 | 101.1 | 98.4 | 97.2 | 95.6 | 94.2 | 92.2 | 91.0 | 90.1 | 91.2 | 94.8 | 99.8 | 101.7 | 99.8 | 98.0 | 96.9 | 95.5 | 97.3 | 99.6 | | +| R2048aD2 | 135.1 | 103.3 | 98.6 | 96.0 | 94.2 | 92.9 | 90.6 | 89.3 | 88.7 | 89.0 | 92.2 | 98.9 | 113.0 | 124.8 | 134.6 | 137.6 | 138.0 | 138.0 | 138.0 | | +| R2304aA2 | 115.0 | 96.1 | 93.9 | 92.6 | 90.8 | 89.4 | 87.0 | 85.3 | 84.1 | 85.6 | 87.9 | 91.2 | 97.7 | 99.6 | 100.2 | 101.0 | 102.6 | 108.2 | 116.8 | | +| R2304aC2 | 120.6 | 101.3 | 98.8 | 97.8 | 96.4 | 95.0 | 93.0 | 91.8 | 90.7 | 91.6 | 93.1 | 96.4 | 101.5 | 99.7 | 98.0 | 96.9 | 95.5 | 97.3 | 99.6 | | +| R2304aD2 | 136.2 | 105.0 | 100.4 | 97.8 | 95.9 | 94.6 | 92.2 | 90.8 | 89.9 | 89.6 | 90.4 | 93.8 | 106.4 | 118.0 | 129.7 | 136.4 | 138.0 | 138.0 | 138.0 | | +| R2048aD3 | 135.1 | 103.3 | 98.6 | 96.0 | 94.2 | 92.9 | 90.6 | 89.3 | 88.7 | 89.0 | 92.2 | 98.9 | 113.1 | 125.2 | 135.0 | 137.7 | 138.0 | 138.0 | 138.0 | | +| R2304aD3 | 136.2 | 105.0 | 100.3 | 97.7 | 95.9 | 94.5 | 92.2 | 90.8 | 89.9 | 89.6 | 90.4 | 93.8 | 106.4 | 118.2 | 130.1 | 136.6 | 138.0 | 138.0 | 138.0 | | +| R2048aA4 | 114.9 | 95.9 | 93.5 | 92.0 | 90.2 | 88.9 | 86.5 | 84.9 | 83.8 | 85.4 | 89.4 | 94.7 | 100.6 | 103.3 | 104.2 | 105.4 | 107.9 | 113.9 | 122.2 | | +| R2048aC4 | 120.6 | 101.1 | 98.4 | 97.1 | 95.6 | 94.2 | 92.2 | 91.0 | 90.1 | 91.2 | 94.8 | 99.8 | 101.7 | 99.8 | 98.0 | 96.9 | 95.5 | 97.3 | 99.6 | | + +Table IV.4/G.991.2 – STU-R side/asymmetric PSDs + +| Noise profile | Magnitude of the noise in dBm per Hz (sign is always negative) as a function of frequency in kHz | | | | | | | | | | | | | | | | | | | +|---------------|--------------------------------------------------------------------------------------------------|-------|-------|------|------|------|------|------|------|------|------|-------|-------|-------|-------|-------|-------|-------|-------| +| | 1 | 20 | 40 | 60 | 80 | 100 | 150 | 200 | 250 | 300 | 350 | 400 | 500 | 600 | 700 | 800 | 1000 | 1200 | 1400 | +| R2304aA4 | 115.0 | 96.0 | 93.8 | 92.5 | 90.7 | 89.4 | 86.9 | 85.2 | 84.0 | 85.6 | 87.9 | 91.0 | 97.5 | 99.4 | 100.2 | 101.0 | 102.8 | 108.4 | 117.1 | +| R2304aC4 | 120.6 | 101.2 | 98.7 | 97.8 | 96.4 | 94.9 | 92.9 | 91.7 | 90.7 | 91.6 | 93.1 | 96.4 | 101.5 | 99.7 | 98.0 | 96.9 | 95.5 | 97.3 | 99.6 | +| R2048aB5 | 120.4 | 100.8 | 98.1 | 96.9 | 95.5 | 94.1 | 92.1 | 90.9 | 90.0 | 90.9 | 94.5 | 99.9 | 109.9 | 117.5 | 117.8 | 119.3 | 124.5 | 128.9 | 132.5 | +| R2304aB5 | 120.4 | 100.9 | 98.4 | 97.6 | 96.2 | 94.8 | 92.8 | 91.7 | 90.6 | 91.3 | 92.9 | 96.3 | 106.7 | 113.3 | 115.1 | 116.9 | 121.1 | 126.2 | 131.8 | +| R2048aA6 | 115.2 | 96.0 | 93.7 | 92.1 | 90.4 | 89.0 | 86.5 | 84.9 | 83.8 | 85.5 | 89.3 | 94.0 | 100.2 | 99.1 | 100.6 | 99.6 | 100.0 | 105.0 | 112.9 | +| R2048aC6 | 120.6 | 101.1 | 98.4 | 97.2 | 95.6 | 94.3 | 92.2 | 91.0 | 90.1 | 91.2 | 94.7 | 99.6 | 101.7 | 99.7 | 98.0 | 96.8 | 95.5 | 97.3 | 99.6 | +| R2304aA6 | 115.4 | 96.3 | 94.0 | 92.7 | 90.9 | 89.6 | 87.0 | 85.3 | 84.1 | 85.7 | 87.7 | 90.6 | 96.6 | 95.4 | 97.3 | 95.4 | 94.9 | 99.4 | 106.7 | +| R2304aC6 | 120.7 | 101.3 | 98.8 | 97.9 | 96.4 | 95.0 | 93.0 | 91.7 | 90.7 | 91.7 | 93.1 | 96.3 | 101.4 | 99.6 | 98.0 | 96.8 | 95.5 | 97.3 | 99.6 | +| R2048aA7 | 115.0 | 95.9 | 93.5 | 92.0 | 90.3 | 88.9 | 86.5 | 84.9 | 83.8 | 85.5 | 89.6 | 95.2 | 102.5 | 106.9 | 107.0 | 108.3 | 110.8 | 116.4 | 124.1 | +| R2048aB7 | 120.6 | 101.1 | 98.4 | 97.1 | 95.6 | 94.2 | 92.2 | 91.0 | 90.1 | 91.0 | 94.5 | 100.1 | 111.2 | 122.3 | 119.5 | 120.5 | 125.9 | 129.7 | 132.6 | +| R2048aC7 | 120.6 | 101.1 | 98.4 | 97.1 | 95.6 | 94.2 | 92.2 | 91.0 | 90.1 | 91.2 | 94.8 | 99.8 | 101.8 | 99.8 | 98.1 | 96.9 | 95.5 | 97.3 | 99.6 | +| R2048aD7 | 135.1 | 103.3 | 98.6 | 96.0 | 94.2 | 92.9 | 90.6 | 89.3 | 88.7 | 89.0 | 92.2 | 98.9 | 113.6 | 127.0 | 135.9 | 137.8 | 138.0 | 138.0 | 138.0 | +| R2304aA7 | 115.1 | 96.0 | 93.8 | 92.5 | 90.8 | 89.4 | 87.0 | 85.3 | 84.1 | 85.7 | 88.1 | 91.4 | 99.8 | 102.7 | 103.2 | 104.5 | 105.8 | 111.3 | 119.7 | +| R2304aB7 | 120.6 | 101.2 | 98.7 | 97.8 | 96.4 | 95.0 | 92.9 | 91.7 | 90.7 | 91.4 | 93.0 | 96.5 | 108.3 | 118.2 | 118.3 | 119.4 | 124.0 | 128.5 | 132.3 | +| R2304aC7 | 120.6 | 101.2 | 98.7 | 97.8 | 96.4 | 95.0 | 92.9 | 91.7 | 90.7 | 91.7 | 93.1 | 96.4 | 101.6 | 99.8 | 98.0 | 96.9 | 95.5 | 97.3 | 99.6 | +| R2304aD7 | 136.2 | 105.0 | 100.3 | 97.7 | 95.9 | 94.6 | 92.2 | 90.8 | 89.9 | 89.6 | 90.4 | 93.9 | 106.7 | 119.4 | 131.9 | 137.2 | 138.0 | 138.0 | 138.0 | + +## BIBLIOGRAPHY + +- [B1] ITU-T Recommendation G.961 (1993), *Digital transmission system on metallic local lines for ISDN basic rate access*. +- [B2] ITU-T Recommendation G.995.1 (2001), *Overview of digital subscriber line (DSL) Recommendations*. +- [B3] ANSI X3.4-1986 (R1997), *Information Systems – Coded Character Sets – 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII)*. +- [B4] ITU-T Recommendation K.50 (2000), *Safe limits of operating voltages and currents for telecommunication systems powered over the network*. +- [B5] Telcordia Technologies, GR-1089-CORE: *Electromagnetic Compatibility and Electrical Safety Generic Criteria for Network Telecommunications Equipment*, February 1999. +- [B6] ITU-T Recommendation G.704 (1998), *Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels*. +- [B7] ANSI/IEEE Std 455-1985: *IEEE Standard Test Procedure for Measuring Longitudinal Balance of Telephone Equipment Operating in the Voice Band*. +- [B8] ITU-T Recommendation O.9 (1999), *Measuring arrangements to assess the degree of unbalance about earth*. +- [B9] IETF RFC 2495 (1999), *Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types*. +- [B10] ITU-T Recommendation I.431 (1993), *Primary rate user-network interface – Layer 1 specification*. +- [B11] ITU-T Recommendation G.996.1 (2001), *Test procedures for Digital Subscriber Line (DSL) transceivers*. +- [B12] The ATM Technical Forum Committee, af-phy-0086.001: *Inverse Multiplexing for ATM (IMA) Specification, Version 1.1*, March 1999. +- [B13] ISO/IEC 13239:2002, *Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures*. +- [B14] Telcordia, GR-303-CORE Issue 4 – *Integrated Digital Loop Carrier System Generic Requirements, Objectives and Interface*, December 2000. +- [B15] The ATM Forum af-vmoa-0145.000: *Voice and Multimedia over ATM – Loop Emulation service Using AAL2*, July 2000. +- [B16] ETSI ETS 300 347-1: *V interfaces at the digital Local Exchange (LE); V5.2 interface for the support of Access Network (AN); Part 1: V5.2 Interface specification – September 1994*. + + + + + +## 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.992.2-199907-I_PDF-E/raw.md b/marked/G/T-REC-G.992.2-199907-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..24ead6e2cf02a98e3ed4a2118b7495fe7dd31a8c --- /dev/null +++ b/marked/G/T-REC-G.992.2-199907-I_PDF-E/raw.md @@ -0,0 +1,5954 @@ + + +![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.992.2** + +(06/99) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Digital transmission systems – Digital sections and digital +line system – Access networks + +--- + +**Splitterless asymmetric digital subscriber line +(ADSL) transceivers** + +ITU-T Recommendation G.992.2 + +(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 | | +| 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.989 | +| Access networks | G.990–G.999 | + +For further details, please refer to ITU-T List of Recommendations. + +# **SPLITTERLESS ASYMMETRIC DIGITAL SUBSCRIBER LINE (ADSL) TRANSCEIVERS** + +## **Summary** + +This Recommendation describes the interface between the telecommunications network and the customer installation in terms of their interaction and electrical characteristics. This Recommendation allows the transmission of POTS and V-series data services simultaneously with a digital channel over a single mixed gauge twisted metallic pair. Annex C defines the procedures to operate in a TCM-ISDN noise environment. Operation in the frequency band over BRA-ISDN is for further study. + +This Recommendation includes procedures to allow provisioning without the need for "splitters", typically installed at the ingress to the customer premises. Additionally, power management procedures and link states are specified to achieve power savings at the central office and customer premises. + +###### **Source** + +ITU-T Recommendation G.992.2 was prepared by ITU-T Study Group 15 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 22 June 1999. + +## FOREWORD + +ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. + +The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. + +The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. + +In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. + +## NOTE + +In this Recommendation, the 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 not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. + +© ITU 2000 + +All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. + +## CONTENTS + +###### Page + +| | | | +|-------|-----------------------------------------------------------------------|----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions and abbreviations ..... | 2 | +| 3.1 | Definitions ..... | 2 | +| 3.2 | Abbreviations..... | 3 | +| 4 | Reference models..... | 6 | +| 4.1 | System reference model..... | 6 | +| 4.2 | ATU reference model ..... | 7 | +| 5 | Transport capacity..... | 8 | +| 6 | ATU interfaces..... | 9 | +| 6.1 | ATU interface for ATM transport..... | 9 | +| 6.2 | ATU PMD to TC logical interface..... | 9 | +| 7 | ATU functional characteristics ..... | 10 | +| 7.1 | ATM transport protocol specific functionalities..... | 10 | +| 7.1.1 | Payload transfer delay..... | 10 | +| 7.1.2 | ATM cell specific functionality..... | 10 | +| 7.1.3 | Framing structure for ATM transport..... | 12 | +| 7.2 | Network Timing Reference..... | 12 | +| 7.2.1 | Optional NTR capability..... | 12 | +| 7.2.2 | Transport of the NTR ..... | 12 | +| 7.3 | Framing..... | 13 | +| 7.3.1 | Relationship to G.992.1 framing ..... | 13 | +| 7.3.2 | Bit ordering..... | 13 | +| 7.3.3 | Data framing and reference points..... | 13 | +| 7.4 | Scrambler ..... | 17 | +| 7.5 | Reed-Solomon Forward Error Correction ..... | 17 | +| 7.5.1 | Reed-Solomon coding ..... | 18 | +| 7.5.2 | Reed-Solomon Forward Error Correction superframe synchronization..... | 18 | +| 7.6 | Interleaver ..... | 18 | +| 7.7 | Tone ordering..... | 19 | +| 7.8 | Constellation encoder ..... | 19 | +| 7.8.1 | Bit extraction ..... | 19 | +| 7.8.2 | Constellation encoder ..... | 19 | +| 7.9 | Gain scaling ..... | 22 | +| 7.10 | Modulation..... | 22 | + +| | Page | +|--------------------------------------------------------------------------|-------------| +| 7.10.1 Subcarriers ..... | 23 | +| 7.10.2 Modulation by the inverse discrete Fourier transform (IDFT) ..... | 23 | +| 7.10.3 Synchronization symbol ..... | 24 | +| 7.10.4 Upstream data pattern ..... | 24 | +| 7.10.5 Downstream data pattern ..... | 24 | +| 7.11 Cyclic prefix..... | 25 | +| 7.12 Transmitter dynamic range ..... | 25 | +| 7.12.1 Maximum clipping rate ..... | 25 | +| 7.12.2 Noise/Distortion floor..... | 25 | +| 7.12.3 Transmitter spectral masks ..... | 26 | +| 8 Embedded Operations Channel (eoc) ..... | 26 | +| 8.1 eoc introduction ..... | 26 | +| 8.1.1 eoc messages overview..... | 26 | +| 8.1.2 eoc protocol overview..... | 26 | +| 8.2 eoc message encoding..... | 27 | +| 8.2.1 ADDRESS field (# 1)..... | 27 | +| 8.2.2 DATA or OPCODE field (# 2)..... | 27 | +| 8.2.3 BYTE PARITY field (# 3) ..... | 28 | +| 8.2.4 AUTONOMOUS MESSAGE field (# 4) ..... | 28 | +| 8.2.5 INFORMATION field (# 5) ..... | 28 | +| 8.3 eoc message description..... | 28 | +| 8.3.1 Latching bidirectional eoc messages ..... | 31 | +| 8.3.2 End of Data message (EOD)..... | 31 | +| 8.3.3 Dying Gasp message (DGASP)..... | 31 | +| 8.3.4 Autonomous messages ..... | 32 | +| 8.3.5 Data registers in the ATU-R ..... | 32 | +| 8.4 eoc protocol..... | 33 | +| 8.4.1 Outstanding eoc messages ..... | 34 | +| 8.4.2 eoc state transitions..... | 37 | +| 8.5 Clear eoc ..... | 40 | +| 9 ADSL overhead channel ..... | 40 | +| 9.1 The ADSL Overhead Control (aoc) channel introduction ..... | 40 | +| 9.1.1 Bit swap channel..... | 40 | +| 9.1.2 Superframe counting..... | 40 | +| 9.2 aoc message encoding..... | 41 | +| 9.2.1 aoc message header encoding..... | 41 | +| 9.2.2 Profile Management Request..... | 41 | +| 9.2.3 Profile Management Acknowledge ..... | 42 | + +| | Page | +|---------------------------------------------------------------------------------|-------------| +| 9.2.4 Bit swap request message encoding..... | 42 | +| 9.2.5 Extended bit swap request message encoding ..... | 43 | +| 9.2.6 Bit swap acknowledge message encoding ..... | 43 | +| 9.3 Bit swap operation ..... | 44 | +| 9.3.1 Bit swap – Receiver ..... | 44 | +| 9.3.2 Bit swap – Transmitter ..... | 45 | +| 9.4 aoc protocol..... | 45 | +| 10 In-service performance monitoring and surveillance..... | 45 | +| 10.1 ADSL line related primitives ..... | 47 | +| 10.1.1 ADSL line related near-end anomalies ..... | 47 | +| 10.1.2 ADSL line related far-end anomalies ..... | 47 | +| 10.1.3 ADSL line related near-end defects ..... | 47 | +| 10.1.4 ADSL line related far-end defects ..... | 47 | +| 10.2 ATM data path related primitives ..... | 48 | +| 10.2.1 ATM data path related near-end anomalies ..... | 48 | +| 10.2.2 ATM data path related far-end anomalies ..... | 48 | +| 10.2.3 ATM data path related near-end defects..... | 49 | +| 10.2.4 ATM data path related far-end defects ..... | 49 | +| 10.3 Other ADSL indicators, parameters and signals ..... | 49 | +| 10.3.1 Other near-end primitives ..... | 49 | +| 10.3.2 Other far-end primitives ..... | 49 | +| 10.3.3 Failure count parameters..... | 49 | +| 10.4 Test parameters ..... | 49 | +| 10.4.1 Near-end test parameters ..... | 50 | +| 10.4.2 Far-end test parameters..... | 50 | +| 10.5 Other failures and parameters ..... | 50 | +| 11 Initialization ..... | 50 | +| 11.1 Overview..... | 50 | +| 11.1.1 Basic functions of initialization..... | 50 | +| 11.1.2 Transparency to methods of separating upstream and downstream signals .. | 51 | +| 11.1.3 Initialization Reset Procedure..... | 52 | +| 11.2 Handshake – ATU-C..... | 52 | +| 11.3 Handshake – ATU-R..... | 53 | +| 11.4 Handshake power levels ..... | 55 | +| 11.5 Escape from Handshake to Fast Retrain ..... | 55 | +| 11.5.1 C-QUIET-EF1 ..... | 56 | +| 11.5.2 R-QUIET-EF1 ..... | 56 | +| 11.6 Power levels in Transceiver Training, Channel Analysis and Exchange..... | 56 | + +| | Page | | +|---------|------------------------------------|----| +| 11.7 | Transceiver training – ATU-C ..... | 56 | +| 11.7.1 | C-QUIET2 ..... | 57 | +| 11.7.2 | C-PILOT1 ..... | 57 | +| 11.7.3 | C-PILOT1A ..... | 57 | +| 11.7.4 | C-QUIET3A ..... | 58 | +| 11.7.5 | C-REVERB1 ..... | 58 | +| 11.7.6 | C-PILOT2 ..... | 59 | +| 11.7.7 | C-ECT..... | 59 | +| 11.7.8 | C-REVERB2 ..... | 59 | +| 11.7.9 | C-QUIET5 ..... | 59 | +| 11.7.10 | C-PILOT3 ..... | 59 | +| 11.7.11 | C-REVERB3 ..... | 59 | +| 11.8 | Transceiver training – ATU-R ..... | 59 | +| 11.8.1 | R-QUIET2 ..... | 59 | +| 11.8.2 | R-REVERB1 ..... | 60 | +| 11.8.3 | R-QUIET3 ..... | 60 | +| 11.8.4 | R-ECT..... | 60 | +| 11.8.5 | R-REVERB2 ..... | 60 | +| 11.9 | Channel analysis (ATU-C)..... | 61 | +| 11.9.1 | C-SEGUE1 ..... | 61 | +| 11.9.2 | C-RATES1..... | 61 | +| 11.9.3 | C-CRC1 ..... | 63 | +| 11.9.4 | C-MSG1..... | 63 | +| 11.9.5 | C-CRC2 ..... | 64 | +| 11.9.6 | C-MEDLEY..... | 65 | +| 11.10 | Channel analysis (ATU-R)..... | 65 | +| 11.10.1 | R-SEGUE1 ..... | 65 | +| 11.10.2 | R-REVERB3 ..... | 65 | +| 11.10.3 | R-SEGUE2 ..... | 65 | +| 11.10.4 | R-RATES1..... | 65 | +| 11.10.5 | R-CRC1 ..... | 66 | +| 11.10.6 | R-MSG1..... | 66 | +| 11.10.7 | R-CRC2 ..... | 67 | +| 11.10.8 | R-MEDLEY..... | 68 | +| 11.10.9 | R-REVERB4 ..... | 68 | +| 11.11 | Exchange – ATU-C..... | 68 | +| 11.11.1 | C-REVERB4 ..... | 70 | +| 11.11.2 | C-SEGUE2 ..... | 70 | +| 11.11.3 | C-RATES-RA..... | 70 | + +| | Page | +|-----------------------------------------------|-------------| +| 11.11.4 C-CRC-RA1 ..... | 71 | +| 11.11.5 C-MSG-RA ..... | 71 | +| 11.11.6 C-CRC-RA2 ..... | 72 | +| 11.11.7 C-REVERB-RA ..... | 72 | +| 11.11.8 C-SEGUE-RA ..... | 72 | +| 11.11.9 C-MSG2 ..... | 72 | +| 11.11.10 C-CRC3 ..... | 73 | +| 11.11.11 C-RATES2 ..... | 73 | +| 11.11.12 C-CRC4 ..... | 74 | +| 11.11.13 C-B&G ..... | 74 | +| 11.11.14 C-CRC5 ..... | 75 | +| 11.11.15 C-REVERB5 ..... | 75 | +| 11.11.16 C-SEGUE3 ..... | 75 | +| 11.12 Exchange – ATU-R ..... | 75 | +| 11.12.1 R-SEGUE3 ..... | 75 | +| 11.12.2 R-MSG-RA ..... | 76 | +| 11.12.3 R-CRC-RA1 ..... | 77 | +| 11.12.4 R-RATES-RA ..... | 77 | +| 11.12.5 R-CRC-RA2 ..... | 77 | +| 11.12.6 R-REVERB-RA ..... | 77 | +| 11.12.7 R-SEGUE-RA ..... | 78 | +| 11.12.8 R-MSG2 ..... | 78 | +| 11.12.9 R-CRC3 ..... | 79 | +| 11.12.10 R-RATES2 ..... | 79 | +| 11.12.11 R-CRC4 ..... | 79 | +| 11.12.12 R-REVERB5 ..... | 80 | +| 11.12.13 R-SEGUE4 ..... | 80 | +| 11.12.14 R-B&G ..... | 80 | +| 11.12.15 R-CRC5 ..... | 81 | +| 11.12.16 R-REVERB6 ..... | 81 | +| 11.12.17 R-SEGUE5 ..... | 81 | +| 11.13 Details of initialization timing ..... | 81 | +| 12 Fast Retrain ..... | 84 | +| 12.1 Fast Retrain overview ..... | 84 | +| 12.1.1 Profile requirements ..... | 84 | +| 12.2 Definition of Fast Retrain signals ..... | 84 | +| 12.2.1 Fast Retrain Signal power levels ..... | 86 | +| 12.3 Fast Retrain Procedure ..... | 87 | +| 12.3.1 ATU-C initiated from SHOWTIME ..... | 87 | + +| | Page | +|---------------------------------------------------------------------------------|-------------| +| 12.3.2 ATU-R initiated from SHOWTIME..... | 90 | +| 12.3.3 Channel measurement..... | 90 | +| 12.3.4 Selection of Tx power levels ..... | 91 | +| 12.3.5 Transceiver retraining..... | 91 | +| 12.3.6 Profile exchange ..... | 91 | +| 12.4 Fast Retrain Procedure – Unknown Profile Transition..... | 92 | +| 12.5 Fast Retrain Procedure – Initiated from L3 or Recommendation G.994.1 ..... | 92 | +| 12.6 Abort of Fast Retrain ..... | 93 | +| 12.6.1 Abort of an ATU-C initiated Fast Retrain Request ..... | 93 | +| 12.6.2 Abort of an ATU-R initiated Fast Retrain Request ..... | 93 | +| 12.7 Fast Retrain Truncate..... | 93 | +| 12.8 Fast Retrain Reset Procedure..... | 93 | +| 13 Power management..... | 93 | +| 13.1 Introduction..... | 93 | +| 13.2 ADSL link states ..... | 94 | +| 13.3 Link state transitions ..... | 94 | +| 13.4 Link transition procedures ..... | 96 | +| 13.4.1 Transitions from L0 to L0 (T0a, T0b, T0c) ..... | 96 | +| 13.4.2 Transition from L0 to L1 (T0d)..... | 96 | +| 13.4.3 Transitions from L1 to L0 (T1a, T1b, T1c, T1d)..... | 97 | +| 13.4.4 Transitions from L0 or L1 to L3 (T0e, T0f, T1e, T1f) ..... | 97 | +| 13.4.5 Transitions from L3 to L0 (T3a, T3b) ..... | 98 | +| 13.5 eoc Handshake ..... | 98 | +| 13.5.1 ATU-R initiated eoc Handshake..... | 98 | +| 13.5.2 ATU-C initiated eoc Handshake..... | 99 | +| Annex A – Non-overlapped spectrum operation ..... | 99 | +| A.1 ATU-R transmitter PSD mask ..... | 99 | +| A.1.1 Passband PSD ripple and group delay ..... | 100 | +| A.1.2 Transmit power spectral density and aggregate power level ..... | 100 | +| A.2 ATU-C transmitter PSD mask ..... | 102 | +| A.2.1 Passband PSD ripple and group delay ..... | 103 | +| A.2.2 Transmit power spectral density and aggregate power level ..... | 103 | +| Annex B – Overlapped spectrum operation ..... | 105 | +| B.1 ATU-R transmitter PSD mask ..... | 105 | +| B.1.1 Passband PSD ripple and group delay ..... | 106 | +| B.1.2 Transmit power spectral density and aggregate power level ..... | 106 | + +| | Page | +|--------------------------------------------------------------------------------------|-------------| +| B.2 ATU-C transmitter PSD mask ..... | 108 | +| B.2.1 Passband PSD ripple and group delay ..... | 109 | +| B.2.2 Transmit power spectral density and aggregate power level ..... | 109 | +| Annex C – ADSL above POTS co-existing in the same binder as TCM-ISDN DSL ..... | 111 | +| C.1 Scope..... | 111 | +| C.2 Definitions and abbreviations ..... | 111 | +| C.2.1 Definitions ..... | 111 | +| C.2.2 Abbreviations..... | 112 | +| C.3 Reference models..... | 112 | +| C.3.1 ATU-C transmitter reference model (replaces figure in 4.2)..... | 112 | +| C.3.2 ATU-R transmitter reference model (replaces figure in 4.2)..... | 113 | +| C.3.3 ATU transmitter timing model (new) ..... | 114 | +| C.4 ATU interfaces..... | 116 | +| C.4.1 ATM interface for ATM transport (replaces figure in 6.1) ..... | 116 | +| C.5 ATU functional characteristics (pertains to clause 7)..... | 117 | +| C.5.1 Payload transfer delay (supplements 7.1.1) ..... | 117 | +| C.5.2 Framing (pertains to 7.3) ..... | 117 | +| C.5.3 Modulation (pertains to 7.10) ..... | 122 | +| C.5.4 Transmitter spectral mask (replaces 7.12.3) ..... | 123 | +| C.5.5 Dual Bitmap (new) ..... | 123 | +| C.5.6 Rate Converter (new)..... | 123 | +| C.5.7 FEXT Bitmap (new) ..... | 123 | +| C.6 aoc on-line adaptation and reconfiguration (pertains to clause 9) ..... | 124 | +| C.6.1 Bit swap request message encoding (replaces 9.2.4)..... | 124 | +| C.6.2 Extended bit swap request message encoding (supplements 9.2.5) ..... | 125 | +| C.6.3 Bit swap acknowledge message encoding (supplements 9.2.6) ..... | 125 | +| C.7 In-service performance monitoring and surveillance (pertains to clause 10) ..... | 125 | +| C.7.1 ADSL line related primitives (pertains to 10.1) ..... | 125 | +| C.7.2 Test parameters (supplements 10.4) ..... | 126 | +| C.8 Initialization ..... | 126 | +| C.8.1 Initialization with Hyperframe (new) ..... | 126 | +| C.8.2 Escape from Handshake to Fast Retrain (replaces 11.5) ..... | 129 | +| C.8.3 Transceiver training – ATU-C (supplements 11.7) ..... | 130 | +| C.8.4 Transceiver training – ATU-R (supplements 11.8) ..... | 131 | +| C.8.5 Channel analysis (ATU-C) (supplements 11.9)..... | 132 | +| C.8.6 Channel analysis (ATU-R) (supplements 11.10)..... | 134 | +| C.8.7 Exchange – ATU-C (supplements 11.11)..... | 136 | +| C.8.8 Exchange – ATU-R (supplements 11.12)..... | 139 | + +| | Page | +|-----------------------------------------------------------------------------------------------------------------------------------|-------------| +| C.9 Fast retraining (supplements clause 12)..... | 140 | +| C.9.1 Fast Retrain overview (pertains to 12.1)..... | 141 | +| C.9.2 Definition of Fast Retrain signals (supplements 12.2) ..... | 141 | +| C.9.3 Fast Retrain procedure (supplements 12.3) ..... | 141 | +| C.9.4 Initiated from L3 or Recommendation G.994.1 (replaces 12.5)..... | 145 | +| C.10 Power management (pertains to clause 13)..... | 145 | +| C.10.1 Transition from L0 to L1 (T0d) (pertains to 13.4.2)..... | 145 | +| Annex D – System performance for North America..... | 145 | +| D.1 System performance for North America..... | 145 | +| D.1.1 Required test cases..... | 146 | +| D.1.2 Extended reach cases ..... | 146 | +| Annex E – System performance for Europe..... | 147 | +| E.1 System performance for Europe ..... | 147 | +| Appendix I..... | 147 | +| Appendix II – Guide to scenarios for the implementation of the various procedures in
Recommendations G.994.1 and G.992.2 ..... | 148 | +| Appendix III – Compatibility with other Customer Premises Equipment ..... | 164 | + +**SPLITTERLESS ASYMMETRIC DIGITAL SUBSCRIBER +LINE (ADSL) TRANSCEIVERS** + +*(Geneva, 1999)* + +## **1 Scope** + +This Recommendation describes the interface between the telecommunications network and the customer installation in terms of their interaction and electrical characteristics. The requirements of the Recommendation apply only to a single asymmetric digital subscriber line (ADSL). ADSL allows the provision of voiceband services, including POTS and V-series data services, and a number of digital channels. + +The transmission system is designed to operate on mixed gauge two-wire twisted metallic pairs over the existing copper facilities and over the customer premises wiring. The transmission system is based on the use of loop plant cables without loading coils. Bridged taps in the loop plant are acceptable in all but a few unusual situations. + +Operation in the frequency band over ISDN is for further study. + +An overview of Digital Subscriber Line Transceivers can be found in Recommendation 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; 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 I.361 (1999), *B-ISDN ATM layer specification*. +- [2] ITU-T Recommendations I.432 x-series, *B-ISDN user-network interface – Physical layer specification*. +- [3] ITU-T Recommendation G.703 (1998), *Physical/electrical characteristics of hierarchical digital interfaces*. +- [4] ITU-T Recommendation G.707 (1996), *Network node interface for the synchronous digital hierarchy (SDH)*. +- [5] ITU-T Recommendation G.961 (1993), *Digital transmission system on metallic local lines for ISDN basic rate access*. +- [6] ITU-T Recommendation G.994.1 (1999), *Handshake procedures for digital subscriber line (DSL) transceivers*. +- [7] ITU-T Recommendation G.992.1 (1999), *Asymmetric digital subscriber line (ADSL) transceivers*. +- [8] ITU-T Recommendation G.996.1 (1999), *Test procedures for digital subscriber line (DSL) transceivers*. +- [9] ITU-T Recommendation G.997.1 (1999), *Physical layer management for digital subscriber line (DSL) transceivers*. + +- [10] CCITT Recommendation T.35 (1991), *Procedure for the allocation of CCITT defined codes for non-standard facilities*. +- [11] ITU-T Recommendation O.41 (1994), *Psophometer for use on telephone-type circuits*. + +### 3 Definitions and abbreviations + +#### 3.1 Definitions + +This Recommendation defines the following terms: + +- 3.1.1 **data frame**: A frame of bytes that compose part of the superframe. +- 3.1.2 **downstream**: The transport of data in the ATU-C to ATU-R direction. +- 3.1.3 **DMT symbol**: A collection of analog samples that constitute a modulated Data Frame. +- 3.1.4 **mux data frame**: A data entity consisting of AS0/LS0 and the Sync Byte (SB). +- 3.1.5 **AS0**: The data channel from the ATU-C to the ATU-R. +- 3.1.6 **superframe**: A data entity consisting of 68 Data Frames and one Sync Frame. +- 3.1.7 **LS0**: The data channel from the ATU-R to the ATU-C. +- 3.1.8 **sync byte**: A byte of data in the Mux Data Frame that contains either aoc, eoc or IB bits. +- 3.1.9 **sync symbol**: A DMT symbol modulated with a constant data pattern. +- 3.1.10 **sync frame**: A frame of bytes that compose part of the superframe. +- 3.1.11 **FEC output frame**: A frame of data presented to the constellation encoder after Reed-Solomon encoding. +- 3.1.12 **upstream**: The transport of data in the ATU-R to ATU-C direction. +- 3.1.13 **indicator bits**: Bits used for OAM purposes. +- 3.1.14 **subcarrier**: A particular complex valued input, $Z_i$ , to the IDFT. +- 3.1.15 **splitter**: A filter that separates the high frequency signals (ADSL) from the voiceband signals (frequently called POTS splitter). +- 3.1.16 **voiceband**: The frequency band from 0 to 4 kHz. +- 3.1.17 **voiceband services**: POTS and all data services that use the voiceband or part of it. +- 3.1.18 **network timing reference**: An 8 kHz timing marker used to support the distribution of a timing reference over the network. + +#### Power Cutback definitions + +- 3.1.19 **absolute downstream fast retrain power cutback**: The addition of Fast Retrain Politeness Power Cutback and Relative Downstream Fast Retrain Power Cutback. +- 3.1.20 **absolute upstream fast retrain power cutback**: A power cutback at the ATU-R transmitter relative to ATU-R Nominal Level. Transmitted to the ATU-C in R-MSG-FR1. +- 3.1.21 **fast retrain politeness power cutback**: A power cutback relative to the Nominal Level at the ATU-C as applied to the previous C-REVERB-FR1 signal. Transmitted in C-MSG-FR1. +- 3.1.22 **initialization politeness power cutback**: A power cutback at the ATU-C transmitter as a result of measurement of the average upstream loop attenuation during R-REVERB1. +- 3.1.23 **nominal level**: Nominal transmit level at the ATU-R shall be $-38$ dBm/Hz. Nominal transmit level at the ATU-C shall be $-40$ dBm/Hz. + +**3.1.24 relative downstream fast retrain power cutback:** An additional power cutback to the ATU-C transmit power that is requested by the ATU-R. This power cutback shall be relative to: (ATU-C Nominal Level – the ATU-C Fast Retrain Politeness Power Cutback). Transmitted to the ATU-C in R-MSG-FR1. + +## **3.2 Abbreviations** + +This Recommendation uses the following abbreviations: + +| | | +|-------|------------------------------------------------------------------------------------------------------------------------------| +| ADSL | Asymmetric Digital Subscriber Line | +| AFE | Analog Front End | +| AGC | Automatic Gain Control | +| ANSI | American National Standards Institute | +| aoc | ADSL Overhead Control | +| AS0 | Downstream data channel | +| ATM | Asynchronous Transfer Mode | +| ATN | Attenuation | +| ATU | ADSL Transceiver Unit | +| ATU-C | ATU at the Central Office | +| ATU-R | ATU at the Remote End | +| BER | Bit Error Rate | +| C-B&G | Central Office Bits and Gains Information | +| CLP | Cell Loss Priority | +| CO | Central Office | +| CRC | Cyclic Redundancy Check | +| DAC | Digital-to-Analog Converter | +| dBn | Ratio (in decibels) of a power level with respect to a reference power of 1 picowatt (equivalent –90 dBm) (see Annex A/O.41) | +| DF | Data Frame | +| DMT | Discrete MultiTone | +| DPRD | Downstream Pseudo Random Data | +| EC | Echo Cancellation | +| eoc | Embedded Operations Channel | +| FDM | Frequency Division Multiplex | +| FEFE | Far-end Block Error | +| FEC | Forward Error Correction | +| FECC | Far-end Echo Cancellation | +| FFEC | Far-end Forward Error Correction | +| FHEC | Far-end Header Error Check | +| FLCD | Far-end Loss of Cell Delineation | + +| | | +|-----------------|--------------------------------------------------| +| FNCD | Far-end No Cell Delineation | +| FOCD | Far-end Out of Cell Delineation | +| GF | Galois Field | +| GNTPDN | Grant Power Down | +| GSTN | General Switched Telephone Network | +| HEC | Header Error Control | +| IB | Indicator Bit | +| IDFT | Inverse Discrete Fourier Transform | +| ISDN | Integrated Services Digital Network | +| K | Number of bytes in a Mux Data Frame | +| LCD | Loss of Cell Delineation | +| LOF | Loss of Frame | +| los | Loss of Signal | +| lpr | Loss of Power | +| LS0 | Upstream data channel | +| LSB | Least Significant Bit | +| LTR | Local Timing Reference | +| MC | Maximum Count indication | +| MSB | Most Significant Bit | +| N | Number of bytes in an FEC Output Data Frame | +| NCD | No Cell Delineation | +| $N_{CP}$ | Number of cyclic prefix values | +| $N_{downi}$ | Size of constellation in bits for subcarrier i | +| $N_{FEC}$ | Number of bytes in a Reed-Solomon Codeword | +| $N_{IDFT}$ | Number of output values of the IDFT | +| NMS | Network Management System | +| $N_{SC}$ | Number of subcarriers | +| NT | Network Termination | +| NTR | Network Timing Reference | +| $N_{updownmax}$ | Maximum number of bits assigned per subcarrier | +| OCD | Out of Cell Delineation | +| OSS | Operations Support System | +| PDU | Protocol Data Unit | +| PHY | Physical | +| PMD/TC | Physical media dependent/transmission conversion | +| POTS | Plain Old Telephone Service | + +| | | +|--------|--------------------------------------------------| +| ppm | parts per million | +| PRD | Pseudo-random Downstream Sequence | +| PRU | Pseudo-random Upstream Sequence | +| PSD | Power Spectrum Distribution | +| QAM | Quadrature Amplitude Modulation | +| R | Number of parity bytes per Reed-Solomon codeword | +| R-B&G | Remote End Bits and Gains Information | +| RDI | Remote Defect Indication | +| REJPDN | Reject Power Down | +| REQPDN | Request Power Down | +| RFI | Indication Remote Failure | +| RRSI | A field in an C/R-RATES and C/R-RATES-RA message | +| RS | Reed-Solomon | +| Rx | Receiver | +| S | DMT symbols per Reed-Solomon codeword | +| SB | Sync Byte | +| SEF | Severely Errored Frame | +| SF | Sync Frame | +| SM | Service Module | +| SNR | Signal-to-Noise Ratio | +| T-R | T reference point at the remote end | +| Tx | Transmitter | +| U-C | U reference point at the CO end | +| UPRD | Upstream Pseudo-Random Data | +| UTC | Unable To Comply | +| V-C | V reference point at the central office | + +## 4 Reference models + +### 4.1 System reference model + +The system reference model shown in Figure 1 describes the functional blocks required to provide ADSL service. + +![System reference model diagram for ADSL showing connections between Broadband network, Narrowband network, ATU-C, ATU-R, Customer premises wiring, and various terminals like SM and telephone sets.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the system reference model for ADSL. On the left, a 'Broadband network' connects to a block containing 'P H Y' and a symbol for a coupler, which then connects to an 'ATU-C'. Below this, a 'Narrowband network' connects via 'GSTN or ISDN' to a 'Splitter C' block. This block contains 'h-p' and 'l-p' components and has interfaces labeled 'U-C 2', 'U-C', and 'U-R'. A 'loop' connects the 'Splitter C' to the 'Customer premises wiring' block. The 'Customer premises wiring' block has an 'U-R' interface and connects to an 'optional' 'l-p' block, which in turn connects to a 'Telephone set, voiceband modem, or ISDN terminal'. On the right, a block contains 'NT T-R', 'ATU-R', 'P H Y', and 'h-p' components. It has interfaces labeled 'T/S', 'U-R', and 'U-C'. This block connects to a 'Home network' which includes two 'SM' (Set Management) blocks. A legend at the bottom left indicates that solid lines represent 'Signal lines' and dashed lines represent 'Interfaces'. The identifier 'T1533300-99' is located in the bottom right corner of the diagram area. + +System reference model diagram for ADSL showing connections between Broadband network, Narrowband network, ATU-C, ATU-R, Customer premises wiring, and various terminals like SM and telephone sets. + +NOTE – An optional ATU-R splitter may be utilized to isolate customer premises wiring and voiceband equipment from the ADSL signal. + +Figure 1/G.992.2 – System reference model + +## 4.2 ATU reference model + +Figure 2 is a block diagram of an ADSL Transceiver Unit (ATU) transmitter showing the functional blocks and interfaces that are referenced in this Recommendation for the transport of ATM data. + +![Figure 2/G.992.2 – ATU reference transmitter model. A block diagram showing the signal flow from ATM0 and NTR (ATU-C) OAM inputs through ATM TC, Mux/Sync Control, crc, Scrambler and FEC, Inter-leaver, Tone Ordering, Constellation Encoder and Gain Scaling, IDFT, Output Serial/Parallel Buffer, and finally DAC and Analog Processing. Key interfaces include PMD/TC Interface, AS0 (ATU-C), and LS0 (ATU-R). Specific data points are marked: A (Mux Data Frame), B (FEC Output Data Frame), and C (Constellation Encoder Input Data Frame). Output of the constellation encoder is Z'_i for i=1 to N_SC-1. Output of the IDFT is X_n for n=0 to N_IDFT-1.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) + +``` + +graph LR + ATM0 <--> ATM_TC[ATM TC] + NTR_OAM[NTR ATU-C OAM] --> Mux_Sync[Mux/Sync Control] + ATM_TC <--> Mux_Sync + Mux_Sync --> A[A: Mux Data Frame] --> CRC[crc] + CRC --> B[B: FEC Output Data Frame] --> Scrambler[Scrambler and FEC] + Scrambler --> Interleaver[Inter-leaver] + Interleaver --> ToneOrdering[Tone Ordering] + ToneOrdering --> C[C: Constellation Encoder Input Data Frame] --> Constellation[Constellation Encoder and Gain Scaling] + Constellation --> Z_i["Z'_i, i=1 to N_SC-1"] --> IDFT[IDFT] + IDFT --> X_n["X_n, n=0 to N_IDFT-1"] --> Buffer[Output Serial/Parallel Buffer] + Buffer --> DAC[DAC and Analog Processing] --> Output + + subgraph Interfaces + PMD_TC[PMD/TC Interface] + AS0[AS0 ATU-C] + LS0[LS0 ATU-R] + end + PMD_TC -.- ATM_TC + AS0 -.- ATM_TC + LS0 -.- ATM_TC + +``` + +Figure 2/G.992.2 – ATU reference transmitter model. A block diagram showing the signal flow from ATM0 and NTR (ATU-C) OAM inputs through ATM TC, Mux/Sync Control, crc, Scrambler and FEC, Inter-leaver, Tone Ordering, Constellation Encoder and Gain Scaling, IDFT, Output Serial/Parallel Buffer, and finally DAC and Analog Processing. Key interfaces include PMD/TC Interface, AS0 (ATU-C), and LS0 (ATU-R). Specific data points are marked: A (Mux Data Frame), B (FEC Output Data Frame), and C (Constellation Encoder Input Data Frame). Output of the constellation encoder is Z'\_i for i=1 to N\_SC-1. Output of the IDFT is X\_n for n=0 to N\_IDFT-1. + +**Figure 2/G.992.2 – ATU reference transmitter model** + +Support of ATM is required. The following requirements shall be supported: + +- Byte boundaries at the V-C and T-R interface shall be preserved in the ADSL data frame. +- Outside the AS0/LS0 serial interfaces, data bytes are transmitted MSB first in accordance with Recommendations I.361 and I.432. All serial processing in the ADSL frame (e.g. crc, scrambling, etc.) shall, however, be performed LSB first, with the outside world MSB considered by the ADSL as LSB. As a result, the first incoming bit (outside world MSB) will be the first processed bit inside the ADSL (ADSL LSB) (see Figure 3), and the CLP bit of the ATM cell header will be carried in the MSB of the ADSL frame byte (i.e. processed last). +- ADSL equipment shall support bearer channel AS0 downstream and bearer channel LS0 upstream as defined in clause 5. + +![Diagram illustrating byte flipping between the TC Layer and the PMD Layer across the PMD/TC Layer Interface. The TC Layer byte format shows bits A0 (LSB) to A7 (MSB). The PMD Layer byte format shows bits D7 (MSB) to D0 (LSB). Arrows indicate that A0 becomes D0 and A7 becomes D7 at the interface. The PMD Layer bits then go to a CRC/Scrambler. Reference T1533320-99 is noted.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +``` + +graph TD + subgraph TC_Layer [Byte Format in TC Layer] + A0[A0 LSB] --- A1[A1] --- A2[A2] --- A3[A3] --- A4[A4] --- A5[A5] --- A6[A6] --- A7[A7 MSB] + end + + Interface[------------------ PMD/TC Layer Interface ------------------] + + subgraph PMD_Layer [Byte Format in PMD Layer] + D7[D7 MSB] --- D6[D6] --- D5[D5] --- D4[D4] --- D3[D3] --- D2[D2] --- D1[D1] --- D0[D0 LSB] + end + + A0 <--> D7 + A1 <--> D6 + A2 <--> D5 + A3 <--> D4 + A4 <--> D3 + A5 <--> D2 + A6 <--> D1 + A7 <--> D0 + + D0 --> Scrambler[To CRC, Scrambler] + +``` + +Diagram illustrating byte flipping between the TC Layer and the PMD Layer across the PMD/TC Layer Interface. The TC Layer byte format shows bits A0 (LSB) to A7 (MSB). The PMD Layer byte format shows bits D7 (MSB) to D0 (LSB). Arrows indicate that A0 becomes D0 and A7 becomes D7 at the interface. The PMD Layer bits then go to a CRC/Scrambler. Reference T1533320-99 is noted. + +T1533320-99 + +- The first serial bit handed from the TC layer to the PMD layer across the PMD/TC interface is the LSB of each PMD layer byte. +- The first serial bit handed from the PMD layer to the TC layer across the PMD/TC interface is the MSB of each TC layer byte. + +**Figure 3/G.992.2 – Illustration of byte flipping** + +## 5 Transport capacity + +The ATU shall transport a single duplex bearer channel. The bearer channel data rate shall be programmable in multiples of 32 kbit/s. + +The maximum net data rate transport capacity of the ATU will depend on the characteristics of the loop on which the system is deployed, and on certain configurable options that affect overhead (see Note). The ATU bearer channel rate shall be configured during the initialization and training procedures. + +The transport capacity of the ATU system is defined only as that of the bearer channel. When, however, an ADSL system is installed on a line that also carries POTS or TCM-ISDN signals, the overall capacity is that of POTS or ISDN plus ADSL. + +In addition, the ATU-C may transport a Network Timing Reference (NTR). The means for doing this are specified in 7.2. + +Bearer channel AS0 shall support the transport of data at all integer multiples of 32 kbit/s from 64 kbit/s to 1.536 Mbit/s. Bearer channel LS0 shall support all integer multiples of 32 kbit/s from 32 kbit/s to 512 kbit/s. + +NOTE – One part of the ATU initialization and training sequence estimates the loop characteristics to determine whether the number of bytes per Discrete MultiTone (DMT) symbol required for the requested configuration's aggregate data rate can be transmitted across the given loop. The net data rate is then the aggregate data rate minus system overhead. Part of the system overhead is dependent on the configurable options. + +**Table 1/G.992.2 – Data rate terminology for ATM transport** + +| Data rate | | | | | Equation (kbit/s) | Ref. point | +|-----------------------|----------|-------------------------|---|-----------------------|-------------------------------------------|------------| +| $53 \times 8$ | $\times$ | ATM cell rate | = | "Net data rate" | $(B_l) \times 32$ | AS0, LS0 | +| "Net data rate" | + | Frame overhead rate | = | "Aggregate data rate" | $\sum(K_l) \times 32$ | A | +| "Aggregate data rate" | + | RS Coding overhead rate | = | Line rate | $\sum(N_l) \times 32 = \sum b_l \times 4$ | B, U | + +## 6 ATU interfaces + +### 6.1 ATU interface for ATM transport + +The functional data interfaces at the ATU for ATM are shown in Figure 4. + +Flow control functionality shall be available on the interface to allow the ATU (i.e. the physical layer) to control the cell flow to and from the ATM layer. This functionality is represented by Tx\_Cell\_Handshake and Rx\_Cell\_Handshake. A cell may be transferred from the ATM to the PHY layer only after the ATU-C has activated the Tx\_Cell\_Handshake. Similarly, a cell may be transferred from the PHY layer to the ATM layer only after the Rx\_Cell\_Handshake. + +![Diagram of ATU functional interface for ATM showing connections between Digital Network, ATM layer, PORT 0, ATM0, and ATU.](a3472689858b068ef469213682965325_img.jpg) + +The diagram illustrates the functional interfaces of an ATU for ATM transport. On the left, a 'Digital Network' block contains an 'ATM layer' which connects to a 'PORT 0'. 'PORT 0' is connected to an 'ATM0' block. The 'ATM0' block contains four sub-components: 'Tx\_ATM0', 'Tx\_Cell\_Handshake0', 'Rx\_ATM0', and 'Rx\_Cell\_Handshake0'. These components connect to an 'ATU' block on the right. The connections are as follows: 'Tx\_ATM0' and 'Tx\_Cell\_Handshake0' connect to the ATU via solid lines; 'Rx\_ATM0' and 'Rx\_Cell\_Handshake0' connect from the ATU via solid lines. Below the ATM0 block, there are three additional connections to the ATU: 'NTR (ATU-C)' (dashed line), 'NTR (ATU-R)' (dashed line), and 'Operations, administration, maintenance and control' (solid line). A vertical dashed line separates the ATM0 block from the ATU block, labeled 'V-C or T-R Interface' at the bottom. The diagram is labeled 'T1533330-99' at the bottom right. + +Diagram of ATU functional interface for ATM showing connections between Digital Network, ATM layer, PORT 0, ATM0, and ATU. + +NOTE – Dashed lines indicate optional functions. + +**Figure 4/G.992.2 – ATU functional interface for ATM** + +### 6.2 ATU PMD to TC logical interface + +The functional data interface between the PMD and ATM TC layers of the ATU are shown in Figure 5. This interface is a logical interface only and does not imply a physical implementation. + +The PMD to TC logical interface is byte-oriented. The bit ordering and timing are described in 4.2 and 7.1.2.4. + +![Diagram of the PMD to TC logical interface showing data and timing signals between an ATM TC and a PMD.](e69b9188aa2c14ec6b21c83f711fef65_img.jpg) + +The diagram illustrates the logical interface between an ATM TC (Transport Concentrator) and a PMD (Physical Medium Dependent). The ATM TC is on the left and the PMD is on the right. The following signals are shown: + +- AS0 Data:** A solid arrow pointing from the ATM TC to the PMD. +- AS0 Timing:** A solid arrow pointing from the PMD to the ATM TC. +- LS0 Data:** A solid arrow pointing from the PMD to the ATM TC. +- LS0 Timing:** A solid arrow pointing from the PMD to the ATM TC. +- Operations, administration, maintenance and control:** A solid arrow pointing from the PMD to the ATM TC. +- NTR (ATU-C):** A dashed arrow pointing from the PMD to the ATM TC. + +T1533340-99 + +Diagram of the PMD to TC logical interface showing data and timing signals between an ATM TC and a PMD. + +**Figure 5/G.992.2 – PMD to TC logical interface** + +## 7 ATU functional characteristics + +### 7.1 ATM transport protocol specific functionalities + +#### 7.1.1 Payload transfer delay + +The one-way transfer delay (excluding cell specific functionalities) for payload bits from the V reference point at central office end (V-C) to the T reference point at remote end (T-R) should be less than or equal to $(4 + (S - 1)/4 + (S \times D)/4)$ ms. One-way payload transfer delay shall be less than $10 + (S \times D)/4$ . The same requirement applies in the opposite direction, from the T-R reference point to the V-C reference point. + +The additional delay introduced by the ATM cell specific functionality is implementation specific. + +#### 7.1.2 ATM cell specific functionality + +##### 7.1.2.1 Idle cell insertion + +Idle cells shall be inserted in the transmit direction for cell rate de-coupling. Idle cells are identified by the standardized pattern for the cell header given in Recommendation I.432. + +Idle cells shall be discarded by an ATU receiver. + +##### 7.1.2.2 Header Error Control (HEC) generation + +The HEC byte shall be generated in the transmit direction as described in Recommendation I.432, including the recommended modulo 2 addition (XOR) of the pattern binary 01010101b to the HEC bits. + +The generator polynomial coefficient set used and the HEC sequence generation procedure shall be in accordance with Recommendation I.432. + +##### 7.1.2.3 Cell payload scrambling + +Scrambling of the cell payload field shall be used in the transmit direction to improve the security and robustness of the HEC cell delineation mechanism. The self synchronizing scrambler polynomial $x^{43} + 1$ and procedures defined in Recommendation I.432 shall be implemented. + +The cell payload shall be descrambled by an ATU receiver. + +#### 7.1.2.4 Bit timing and ordering + +When interfacing ATM data bytes to the AS0/LS0 bearer channel, the most significant bit (MSB) shall be sent first. The AS0 and LS0 bearer channel data rates shall be integer multiples 32 kbit/s, with bit timing synchronous with the ADSL downstream modem timing base. + +#### 7.1.2.5 Cell delineation + +The cell delineation function permits the identification of cell boundaries in the payload. It uses the HEC field in the cell header. + +Cell delineation shall be performed using a coding law checking the HEC field in the cell header according to the algorithm described in Recommendation I.432. The ATM cell delineation state machine is shown in Figure 6. The details of the state diagram are described below: + +- In the HUNT state, the delineation process is performed by checking bit by bit for the correct HEC. Once such an agreement is found, it is assumed that one header has been found, and the method enters the PRESYNC state. When byte boundaries are available, the cell delineation process may be performed byte by byte. +- In the PRESYNC state, the delineation process is performed by checking cell by cell for the correct HEC. The process repeats until the correct HEC has been confirmed DELTA (see Note) times consecutively. If an incorrect HEC is found, the process returns to the HUNT state. +- In the SYNC state the cell delineation will be assumed to be lost if an incorrect HEC is obtained ALPHA times consecutively. + +![ATM cell delineation state machine diagram showing three states: HUNT, PRESYNC, and SYNC. Transitions are based on HEC correctness and consecutive counts (ALPHA, DELTA).](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` +stateDiagram-v2 + [*] --> HUNT + HUNT --> PRESYNC : Correct HEC + PRESYNC --> HUNT : Incorrect HEC + PRESYNC --> SYNC : DELTA consecutive correct HEC + SYNC --> HUNT : ALPHA consecutive incorrect HEC +``` + +The diagram illustrates the ATM cell delineation state machine with three states: HUNT, PRESYNC, and SYNC. Transitions are as follows: HUNT to PRESYNC on 'Correct HEC'; PRESYNC to HUNT on 'Incorrect HEC'; PRESYNC to SYNC on 'DELTA consecutive correct HEC'; and SYNC to HUNT on 'ALPHA consecutive incorrect HEC'. Labels 'Bit-by-bit', 'Cell-by-cell', and 'Cell-by-cell' are associated with the HUNT, PRESYNC, and SYNC states respectively. A reference code 'T1533350-99' is present in the bottom right. + +ATM cell delineation state machine diagram showing three states: HUNT, PRESYNC, and SYNC. Transitions are based on HEC correctness and consecutive counts (ALPHA, DELTA). + +Figure 6/G.992.2 – ATM cell delineation state machine + +NOTE – With reference to Recommendation I.432, no recommendation is made for the values of ALPHA and DELTA as the choice of these values is not considered to effect interoperability. However, it should be noted that the use of the values suggested in Recommendation I.432 (ALPHA = 7, DELTA = 6) may be inappropriate due to the particular transmission characteristics of ADSL. + +#### 7.1.2.6 Header Error Control verification + +The HEC covers the entire cell header. The code used for this function is capable of: + +- either single bit error correction; +- or multiple bit error detection. + +Error detection shall be implemented as defined in Recommendation I.432 with the exception that any HEC error shall be considered as a multiple bit error, and therefore, HEC error correction shall not be performed. + +### 7.1.3 Framing structure for ATM transport + +The ATU-C transmitter shall preserve V-C and T-R interface byte boundaries (explicitly present or implied by ATM cell boundaries) at the U-C interface. + +## 7.2 Network Timing Reference + +### 7.2.1 Optional NTR capability + +To support the distribution of a timing reference over the network, an ATU-C may optionally transport an 8 kHz timing marker as NTR. The 8 kHz timing marker is input to the ATU-C as part of the interface at the V-C reference point. + +### 7.2.2 Transport of the NTR + +If included, an ATU-C shall transport the NTR as follows: + +The ATU-C shall generate an 8 kHz local timing reference (LTR) by dividing its sampling clock by the appropriate integer. It shall transmit the change in phase offset between the input NTR and LTR (measured in cycles of a 1.104 MHz clock in units of approximately 905 ns) from the previous superframe to the present one. The phase offset shall be encoded into four bits ntr3-ntr0 (with ntr3 the MSB), representing a signed integer in the -8 to +7 range in twos-complement notation. The bits ntr3-ntr0 shall be carried in the indicator bits 23 (ntr3) to 20 (ntr0); see Table 4. + +NOTE 1 – A positive value of the change of phase offset, $\Delta^2\phi$ , shall indicate that the LTR is higher in frequency than the NTR. + +NOTE 2 – The NTR has a maximum frequency variation of $\pm 32$ ppm. The LTR, as specified in 7.2.2, has a maximum frequency variation of $\pm 50$ ppm. The maximum mismatch is therefore $\pm 82$ ppm. This would result in an average change of phase offset in one 17 ms superframe of approximately $\pm 1.75$ clock cycles, which can be mapped into four overhead bits. + +NOTE 3 – One method that the ATU-C may use to measure this change of phase offset is shown in Figure 7. + +NOTE 4 – Alternatively, the ATU-C may choose to lock its downstream sampling clock (1.104 MHz) to 138 times the NTR frequency; in that case it shall encode $\Delta^2\phi$ to zero. + +![Block diagram of the Δ²φ measurement implementation. It shows an NTR input and a 1.104 MHz clock input. The clock is divided by 138 to produce MC, which is then divided by 136 to produce another MC. The NTR is sampled by a register clocked by the 1.104 MHz clock. The output of this register is sampled by another register clocked by MC. The output of this second register is compared with the output of a third register (also clocked by MC) via a summation node (Σ) to produce Δ²φ. The third register's input is the output of the second register. The diagram includes labels for 9-bit buses and a reference number T1533360-99. A note below states '(MC is maxcount indication before foldover to 0)'.](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +(MC is maxcount indication before foldover to 0) + +Block diagram of the Δ²φ measurement implementation. It shows an NTR input and a 1.104 MHz clock input. The clock is divided by 138 to produce MC, which is then divided by 136 to produce another MC. The NTR is sampled by a register clocked by the 1.104 MHz clock. The output of this register is sampled by another register clocked by MC. The output of this second register is compared with the output of a third register (also clocked by MC) via a summation node (Σ) to produce Δ²φ. The third register's input is the output of the second register. The diagram includes labels for 9-bit buses and a reference number T1533360-99. A note below states '(MC is maxcount indication before foldover to 0)'. + +Figure 7/G.992.2 – Example implementation of the $\Delta^2\phi$ measurement + +## 7.3 Framing + +### 7.3.1 Relationship to G.992.1 framing + +The framing is equivalent to the "reduced overhead mode with merged fast and sync bytes" as defined in Recommendation 7.4.4.2/G.992.1 using only the "interleave buffer" definition. Only a single duplex channel is supported, consisting of a simplex AS0 downstream channel and a simplex LS0 upstream channel. + +### 7.3.2 Bit ordering + +External to the AS0/LS0 serial interfaces data bytes are transmitted MSB first in accordance with Recommendations G.703, G.709, I.361 and I.432. All serial processing in the superframe (e.g. crc, scrambling, etc.) shall, however, be performed LSB first, with the outside world MSB considered as the LSB. As a result, the first incoming bit (outside world MSB) will be the first bit processed by the ATU (ATU LSB). + +### 7.3.3 Data framing and reference points + +Figure 2 shows a functional block diagram of the ATU transmitter with reference points for data framing. A cyclic redundancy check (crc), scrambling, forward error correction (FEC) coding and interleaving shall be applied to the contents of the superframe. The data stream shall then be tone ordered as defined in 7.7, and combined into a data symbol that is input to the constellation encoder. After constellation encoding the data shall be modulated to produce an analog signal for transmission across the customer loop. + +DMT symbol boundaries are delineated by the cyclic prefix inserted by the modulator (see 7.11). Superframe boundaries are delineated by the Sync Symbol, which shall also be inserted by the modulator, and which carries no user data (see 7.3.3.1). + +Because of the addition of FEC redundancy bytes and data interleaving, the data symbols (i.e. bit-level data prior to constellation encoding) have different structural appearance at the three reference points through the transmitter. As shown in Figure 2, the reference points for which data framing will be described in the following subclauses are: + +**A: Mux Data Frame:** The synchronized data after the crc has been inserted (crc is specified in 7.3.3.1.2). Mux Data Frames shall be generated at a nominal 4 kHz rate. Each Mux Data Frame shall contain $K$ bytes. + +**B: FEC Output Data Frame:** The data frame generated at the output of the FEC encoder at the DMT symbol rate, where an FEC block may span more than one DMT symbol period. Each FEC Output Data Frame shall contain $N$ bytes [ $N = K + (R/S)$ ]. + +**C: Constellation Encoder Input Data Frame:** The data frame presented to the constellation encoder. + +#### 7.3.3.1 Superframe structure + +The superframe structure is shown in Figure 8. Each superframe is composed of 68 "Data Frames" (DF), numbered from 0 to 67, which are encoded and modulated into DMT symbols, followed by a "Sync Frame" (SF), which carries no user or overhead bit-level data and is inserted by the modulator to establish superframe boundaries. From the bit-level and user data perspective, the DMT symbol rate is 4000 (period = 250 $\mu\text{s}$ ), but in order to allow for the insertion of the SF the transmitted DMT symbol rate is $69/68 \times 4000$ . + +![Diagram of Superframe structure showing the hierarchy from individual data frames to a 17ms superframe.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +The diagram illustrates the Superframe structure for G.992.2. At the top, a horizontal double-headed arrow indicates a "superframe 17 ms" duration. Below this, a row of frames is shown: DF 0, DF 1, DF 2, followed by a break (indicated by wavy lines), then DF 34, DF 35, another break, then DF 66, DF 67, and finally SF (Sync Frame). Below this row, three horizontal double-headed arrows indicate the duration of "FEC output data frame #0", "FEC output data frame #1", and "FEC output data frame #S - 1". Above each of these arrows is the formula $N = K + (R/S)$ bytes. Below the FEC output frames, another row shows "Mux data frame #0", "Mux data frame #1", a break, "Mux data frame #S - 1", and "FEC bytes". Above "Mux data frame #0" and "Mux data frame #1" are arrows labeled $K$ bytes. Above "Mux data frame #S - 1" is an arrow labeled $K$ bytes, and above "FEC bytes" is an arrow labeled $R$ bytes. At the bottom, a detailed view of a "Mux data frame (ref. point A)" is shown, consisting of an "SB" (Sync Byte) labeled "1 byte" and "Data from AS0/LS0 (payload)" labeled $B_l(AS0)/B_l(LS0)$ bytes. The text "T1533370-99" is located at the bottom right of the diagram. + +Diagram of Superframe structure showing the hierarchy from individual data frames to a 17ms superframe. + +**Figure 8/G.992.2 – Superframe structure** + +### 7.3.3.1.1 Use of Sync Byte (SB) + +The crc, Indicator Bits, eoc and aoc functions shall be carried in the SB assigned to separate DFs within the superframe structure. The crc is transmitted in frame 0 and the Indicator Bits in frames 1, 34 and 35. The aoc and eoc bytes are assigned to alternate pairs of frames. The assignment of overhead functions to the SB shall be as shown in Table 2. + +**Table 2/G.992.2 – Sync Byte functions** + +| Data Frame (DF) | Sync Byte contents | +|-----------------------------------------------------|--------------------| +| 0 | crc | +| 1 | IB0-7 | +| 34 | IB8-15 | +| 35 | IB16-23 | +| $4n + 2, 4n + 3$
with $n = 0 \dots 16, n \neq 8$ | eoc | +| $4n, 4n + 1$
with $n = 1 \dots 16$ | aoc | + +NOTE – The only allowable eoc synchronization code is "no synchronization action". + +#### 7.3.3.1.1.1 eoc byte encoding + +The eoc bits transported in the SB shall contain either eoc bits or the hexadecimal value of $XX0011X0_6$ in downstream and $000011X0_6$ in upstream (with X vendor discretionary) indicating "no synchronization action". The "no synchronization action" byte shall be used as fill when there is no eoc channel data to be transmitted. When transporting eoc data, the SB eoc bytes shall be encoded as in Figure 9. + +| | | | | | | | | | +|---------------------------|-------|-------|-------|-------|------|------|------|----------------| +| Even-numbered data frames | eoc6 | eoc5 | eoc4 | eoc3 | eoc2 | eoc1 | r1 | 1 b | +| | MSB | | | | | | | LSB | +| Odd-numbered data frames | eoc13 | eoc12 | eoc11 | eoc10 | eoc9 | eoc8 | eoc7 | 1 b | + +**Figure 9/G.992.2 – Sync Byte encoding for transport of eoc bytes** + +In all frames, bit 7 is MSB and bit 0 is LSB. Bit 0 shall be set to 1b to indicate that the eoc byte contains an eoc message. Bit r1 shall be set to 1b. The use of r1 is reserved by the ITU-T. + +#### 7.3.3.1.1.2 aoc byte encoding + +The aoc bytes transported in the SB shall contain the aoc channel data as described in clause 9. When no aoc data is available for transmission in the superframe, the aoc byte shall contain the stuffing byte defined in 9.4. + +In all frames, bit 7 is MSB and bit 0 is LSB (Figure 10). + +| | | | | | | | | | +|-----------------|------|------|------|------|------|------|------|------| +| All data frames | MSB | | | | | | | LSB | +| | aoc7 | aoc6 | aoc5 | aoc4 | aoc3 | aoc2 | aoc1 | aoc0 | + +**Figure 10/G.992.2 – Sync Byte encoding for transport of aoc bytes** + +#### 7.3.3.1.2 Cyclic redundancy check (crc) + +Eight bits per superframe shall be used for the crc on the superframe (crc0-crc7). As shown in Table 2, the "Sync Byte" (SB) carries the crc check bits for the previous superframe in frame 0. + +The crc bits are computed from the k message bits using the equation: + +$$\text{crc}(D) = M(D) D^8 \text{ modulo } G(D)$$ + +where: + +$M(D) = m_0 D^{k-1} + m_1 D^{k-2} + \dots + m_{k-2} D + m_{k-1}$ is the message polynomial + +$G(D) = D^8 + D^4 + D^3 + D^2 + 1$ is the generating polynomial + +$\text{crc}(D) = c_0 D^7 + c_1 D^6 + \dots + c_6 D + c_7$ is the check polynomial + +and D is the delay operator. + +That is, the crc is the remainder when $M(D) D^8$ is divided by $G(D)$ . Each byte shall be clocked into the crc least significant bit first. In all frames, bit 7 = MSB and bit 0 = LSB. The bits covered by the crc are listed in Table 3. + +**Table 3/G.992.2 – crc coverage** + +| Data Frame (DF) | crc coverage | +|-----------------|------------------------------------------------| +| 0 | AS0 and LS0 bytes | +| 1-67 | Sync Byte (SB), followed by AS0 and LS0 bytes. | + +### 7.3.3.1.3 Indicator Bits (IB0-IB23) + +As shown in Table 2, the SB carries Indicator Bits in Data Frames 1, 34 and 35. The indicator bits are defined in Table 4. + +A description of the use of the indicator bits can be found in clause 10. + +**Table 4/G.992.2 – Definition of indicator bits, ATU-C transmitter** + +| Indicator bit (see Note 1) | Definition | +|--------------------------------------------------------------------------------------------------------|------------------------------------| +| IB0-IB7 | Reserved by the ITU-T (see Note 1) | +| IB8 | febe-i | +| IB9 | fecc-i | +| IB10 | Reserved by the ITU-T | +| IB11 | Reserved by the ITU-T | +| IB12 | los | +| IB13 | RDI | +| IB14 | ncd-i | +| IB15 | Reserved by the ITU-T | +| IB16 | hec-i | +| IB17-19 | Reserved by the ITU-T | +| IB20-23 | NTR bits (see 7.2.2 and Note 2) | +| NOTE 1 – Reserved bits are set to 1 b because all indicator bits are defined as active low. | | +| NOTE 2 – If the NTR is not transported, IB20-23 shall be set to 1 b . | | + +## 7.4 Scrambler + +The binary data streams (LSB of each byte first) at reference point A shall be scrambled using the following algorithm: + +$$d'_n = d_n \oplus d'_{n-18} \oplus d'_{n-23}$$ + +where $d_n$ is the $n$ -th input to the scrambler, and $d'_n$ is the $n$ -th output from the scrambler. This is illustrated in Figure 11. + +![Block diagram of a scrambler. A 'Byte input (from CRC block)' enters a 'Par/Ser LSB first' block. The output is labeled d_n. This signal enters a summation node (circle with a cross). The output of this node is labeled d'_n. This signal then enters a 'Ser/Par LSB first' block, which produces the 'Byte output (from RS coder block)'. A feedback path branches off from the d'_n signal and passes through a series of delay blocks (squares). The outputs of these delays are labeled d'_{n-1}, d'_{n-2}, ..., d'_{n-18}, ..., d'_{n-23}. The d'_{n-18} and d'_{n-23} signals enter a second summation node. The output of this second node is fed back into the first summation node.](474a819357587e34949a3e110ff19b30_img.jpg) + +Block diagram of a scrambler. A 'Byte input (from CRC block)' enters a 'Par/Ser LSB first' block. The output is labeled d\_n. This signal enters a summation node (circle with a cross). The output of this node is labeled d'\_n. This signal then enters a 'Ser/Par LSB first' block, which produces the 'Byte output (from RS coder block)'. A feedback path branches off from the d'\_n signal and passes through a series of delay blocks (squares). The outputs of these delays are labeled d'\_{n-1}, d'\_{n-2}, ..., d'\_{n-18}, ..., d'\_{n-23}. The d'\_{n-18} and d'\_{n-23} signals enter a second summation node. The output of this second node is fed back into the first summation node. + +Figure 11/G.992.2 – Scrambler + +## 7.5 Reed-Solomon Forward Error Correction + +$R/S$ bytes shall be added to the Mux Data Frame (reference point A) after scrambling to produce the FEC Output Data Frame (reference point B), where $R$ is given in the C/R-RATES1, C/R-RATES-RA and C/R-MSG-FR2 options used during initialization and Fast Retrain. + +The Reed-Solomon coder shall take in $S$ Mux Data Frames and append $R$ Reed-Solomon FEC redundancy bytes to produce the Reed-Solomon codeword of length $N_{FEC} = S \times K + R$ bytes. The FEC Output Data Frames shall contain $K + (R/S)$ bytes. $(R/S)$ shall be an integer. When $S > 1$ , then for the $S$ frames in a Reed-Solomon codeword, the FEC Output Data Frame (reference point B) shall partially overlap two Mux Data Frames for all except the last frame, which shall contain the last Mux Data Frame and $R$ FEC redundancy bytes. + +The ATU shall support transmission and reception with at least any combination of the Reed-Solomon FEC coding capabilities shown in Table 5. + +**Table 5/G.992.2 – Minimum FEC coding capabilities for ATU** + +| Parameter | Capabilities | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| Parity bytes per R-S codeword | Mandatory: R = 0, 4, 8
Optional: R = 16
(see Note) | +| DMT symbols per R-S codeword | Mandatory: S = 1, 2, 4 and 8
Optional: S = 16 | +| Interleave depth | Mandatory:
D = 1, 2, 4, 8 and 16 (downstream)
D = 1, 2, 4, 8 (upstream) | +| NOTE – R shall be an integer multiple of S . | | + +### 7.5.1 Reed-Solomon coding + +When *R* = 0, no check bytes are appended and the FEC Output Data Frames are equivalent to the Mux Data Frames. For all other values of *R*, the following encoding procedures shall be used. + +*R* redundant check bytes *c*0, *c*1, ..., *c**R*–2, *c**R*–1 shall be appended to (*K* × *S*) message bytes *m*0, *m*1, ..., *m**K*\**S*–2, *m**K*\**S*–1 to form a Reed-Solomon codeword of size *N*FEC = *S* × *K* + *R* bytes. The check bytes are computed from the message byte using the equation: + +$$C(D) = M(D) D^R \text{ modulo } G(D)$$ + +where: + +$$M(D) = m_0 D^{S*K-1} + m_1 D^{S*K-2} \dots + m_{S*K-2} D + m_{S*K-1}$$ + +is the message polynomial, + +$$C(D) = c_0 D^{R-1} + c_1 D^{R-2} + \dots + c_{R-2} D + c_{R-1}$$ + +is the check polynomial, and + +$$G(D) = \prod (D + \alpha^i)$$ + +is the generator polynomial of the Reed-Solomon code, where the index of the product runs from *i* = 0 to *R*–1. That is, *C*(*D*) is the remainder obtained from dividing *M*(*D*) *D**R* by *G*(*D*). The arithmetic is performed in the Galois Field GF(256), where $\alpha$ is a primitive element that satisfies the primitive binary polynomial $x^8 + x^4 + x^3 + x^2 + 1$ . A data byte (*d*7, *d*6, ..., *d*1, *d*0) is identified with the Galois Field element $d_7\alpha^7 + d_6\alpha^6 \dots + d_1\alpha + d_0$ . + +### 7.5.2 Reed-Solomon Forward Error Correction superframe synchronization + +After completion of Initialization and Fast Retrain, the ATU shall align the first byte of the first Reed-Solomon codeword with the first data byte of DF 0. + +## 7.6 Interleaver + +The Reed-Solomon codewords shall be convolutionally interleaved. The interleaving depth shall always be a power of 2. Convolutional interleaving is defined by the rule: + +Each of the *N*FEC bytes *B*0, *B*1, ..., *B**N*–1 in a Reed-Solomon codeword is delayed by an amount that varies linearly with the byte index. More precisely, byte *B**i* (with index *i*) is delayed by (*D* – 1) × *i* bytes, where *D* is the interleave depth. + +An example for *N*FEC = 5, *D* = 2 is shown in Table 6, where *B**j**i* denotes the *i*-th byte of the *j*-th codeword. + +**Table 6/G.992.2 – Convolutional interleaving example for $N_{FEC} = 5, D = 2$** + +| | | | | | | | | | | | +|---------------------------|-----------|---------------|-----------|---------------|-----------|---------------|---------------|---------------|---------------|---------------| +| Interleaver input | $B_{0}^j$ | $B_{1}^j$ | $B_{2}^j$ | $B_{3}^j$ | $B_{4}^j$ | $B_{0}^{j+1}$ | $B_{1}^{j+1}$ | $B_{2}^{j+1}$ | $B_{3}^{j+1}$ | $B_{4}^{j+1}$ | +| Interleaver output | $B_{0}^j$ | $B_{3}^{j-1}$ | $B_{1}^j$ | $B_{4}^{j-1}$ | $B_{2}^j$ | $B_{0}^{j+1}$ | $B_{3}^j$ | $B_{1}^{j+1}$ | $B_{4}^j$ | $B_{2}^{j+1}$ | + +With the above-defined rule, and the chosen interleaving depths (powers of 2), the output bytes from the interleaver always occupy distinct time slots when $N_{FEC}$ is odd. When $N_{FEC}$ is even, a dummy byte shall be added at the beginning of the codeword at the input to the interleaver. The resultant odd-length codeword is then convolutionally interleaved, and the dummy byte shall then be removed from the output of the interleaver. + +## 7.7 Tone ordering + +The bit table $b'_i$ shall be calculated based upon the original bit table $b_i$ as follows: + +There is no ordering for the number of bits allocated to the subcarriers. Therefore, the first bit is assigned to the lowest frequency used subcarriers and the last bit is assigned to the highest frequency used subcarriers (i.e. $b_i = b'_i$ ). + +## 7.8 Constellation encoder + +An algorithmic constellation encoder shall be used to construct constellations with a maximum number of bits equal to $N_{updownmax}$ , where $8 \leq N_{updownmax} \leq 15$ . + +### 7.8.1 Bit extraction + +Data bits from the DMT symbol buffer shall be extracted according to a re-ordered bit allocation table $b'_i$ , least significant bit first. The number of bits per tone, $b'_i$ , can take any non-negative integer values not exceeding $N_{updownmax}$ with the exception of $b'_i = 1$ . For a given tone $b'_i = b$ bits are extracted from the DMT symbol buffer, and these bits form a binary word $\{v_{b-1}, v_{b-2}, \dots, v_1, v_0\}$ . The first bit extracted shall be $v_0$ , the LSB. + +### 7.8.2 Constellation encoder + +For a given sub-channel, the encoder shall select an odd-integer point (X,Y) from the square-grid constellation based on the $b$ bits $\{v_{b-1}, v_{b-2}, \dots, v_1, v_0\}$ . For convenience of description, these $b$ bits are identified with an integer label whose binary representation is $(v_{b-1}, v_{b-2}, \dots, v_1, v_0)$ . For example, for $b = 2$ , the four constellation points are labelled 0, 1, 2, 3 corresponding to $(v_1, v_0) = (0,0), (0,1), (1,0), (1,1)$ , respectively. + +NOTE – $v_0$ is the first bit extracted from the buffer. + +#### 7.8.2.1 Even values of $b$ + +For even values of $b$ , the integer values X and Y of the constellation point (X,Y) shall be determined from the $b$ bits $\{v_{b-1}, v_{b-2}, \dots, v_1, v_0\}$ as follows. X and Y are the odd integers with twos-complement binary representations $(v_{b-1}, v_{b-3}, \dots, v_1, 1)$ and $(v_{b-2}, v_{b-4}, \dots, v_0, 1)$ , respectively. The most significant bits (MSBs), $v_{b-1}$ and $v_{b-2}$ , are the sign bits for X and Y, respectively. Figure 12 shows example constellations for $b = 2$ and $b = 4$ . + +![Figure 12/G.992.2 – Constellation labels for b = 2 and b = 4. The left diagram shows a 2-bit constellation with labels 0, 1, 2, 3. The right diagram shows a 4-bit constellation with labels 0 through 15 arranged in a 4x4 grid.](48a08e5cabec8b75386679d8a57dec3e_img.jpg) + +Figure 12/G.992.2 shows two constellation diagrams. The left diagram represents a 2-bit constellation with labels arranged as: top-left (2), top-right (0), bottom-left (3), bottom-right (1). The right diagram represents a 4-bit constellation with labels 0 through 15 in a 4x4 grid. The labels are: Top row (9, 11, 1, 3), Second row (8, 10, 0, 2), Third row (13, 15, 5, 7), Bottom row (12, 14, 4, 6). A small text 'T1533390-99' is visible below the right diagram. + +Figure 12/G.992.2 – Constellation labels for b = 2 and b = 4. The left diagram shows a 2-bit constellation with labels 0, 1, 2, 3. The right diagram shows a 4-bit constellation with labels 0 through 15 arranged in a 4x4 grid. + +**Figure 12/G.992.2 – Constellation labels for $b = 2$ and $b = 4$** + +The 4-bit constellation can be obtained from the 2-bit constellation by replacing each label $n$ by a $2 \times 2$ block of labels as shown in Figure 13. + +![Figure 13/G.992.2 – Expansion of point n into the next larger square constellation. The diagram shows a 2x2 block of labels: 4n+1, 4n+3, 4n, 4n+2.](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +Figure 13/G.992.2 illustrates the expansion of a point $n$ into the next larger square constellation. It shows a 2x2 block of labels: top-left ( $4n+1$ ), top-right ( $4n+3$ ), bottom-left ( $4n$ ), and bottom-right ( $4n+2$ ). A small text 'T1533400-99' is visible below the diagram. + +Figure 13/G.992.2 – Expansion of point n into the next larger square constellation. The diagram shows a 2x2 block of labels: 4n+1, 4n+3, 4n, 4n+2. + +**Figure 13/G.992.2 – Expansion of point $n$ into the next larger square constellation** + +The same procedure can be used to construct the larger even-bit constellations recursively. The constellations obtained for even values of $b$ are square in shape. + +### 7.8.2.2 Odd values of $b$ , $b = 3$ + +Figure 14 shows the constellation for the case $b = 3$ . + +![Figure 14/G.992.2 – Constellation labels for b = 3. The diagram shows a 3-bit constellation with labels 0 through 7 arranged in a cross shape.](c3e1070b4f3194b1fb1b9d5300dac25f_img.jpg) + +Figure 14/G.992.2 shows a 3-bit constellation with labels 0 through 7. The labels are arranged in a cross shape: top (5), bottom (6), far-left (4), far-right (7). Near the center: top-left (2), top-right (0), bottom-left (3), bottom-right (1). A small text 'T1533410-99' is visible below the diagram. + +Figure 14/G.992.2 – Constellation labels for b = 3. The diagram shows a 3-bit constellation with labels 0 through 7 arranged in a cross shape. + +**Figure 14/G.992.2 – Constellation labels for $b = 3$** + +### 7.8.2.3 Odd values of $b$ , $b > 3$ + +If $b$ is odd and greater than three, the two MSBs of $X$ and the 2 MSBs of $Y$ are determined by the five MSBs of the $b$ bits. Let $c = (b + 1)/2$ , then $X$ and $Y$ have the twos-complement binary representations $(X_c, X_{c-1}, v_{b-4}, v_{b-6}, \dots, v_3, v_1, 1)$ and $(Y_c, Y_{c-1}, v_{b-5}, v_{b-7}, v_{b-9}, \dots, v_2, v_0, 1)$ , where $X_c$ and $Y_c$ are the sign bits of $X$ and $Y$ respectively. The relationship between $X_c, X_{c-1}, Y_c, Y_{c-1}$ and $v_{b-1}, v_{b-2}, \dots, v_{b-5}$ is shown in Table 7. + +**Table 7/G.992.2 – Determining the top 2 bits of $X$ and $Y$** + +| $v_{b-1}, v_{b-2}, \dots, v_{b-5}$ | $X_c, X_{c-1}$ | $Y_c, Y_{c-1}$ | +|------------------------------------|-----------------|-----------------| +| 00000 b | 00 b | 00 b | +| 00001 b | 00 b | 00 b | +| 00010 b | 00 b | 00 b | +| 00011 b | 00 b | 00 b | +| 00100 b | 00 b | 11 b | +| 00101 b | 00 b | 11 b | +| 00110 b | 00 b | 11 b | +| 00111 b | 00 b | 11 b | +| 01000 b | 11 b | 00 b | +| 01001 b | 11 b | 00 b | +| 01010 b | 11 b | 00 b | +| 01011 b | 11 b | 00 b | +| 01100 b | 11 b | 11 b | +| 01101 b | 11 b | 11 b | +| 01110 b | 11 b | 11 b | +| 01111 b | 11 b | 11 b | +| 10000 b | 01 b | 00 b | +| 10001 b | 01 b | 00 b | +| 10010 b | 10 b | 00 b | +| 10011 b | 10 b | 00 b | +| 10100 b | 00 b | 01 b | +| 10101 b | 00 b | 10 b | +| 10110 b | 00 b | 01 b | +| 10111 b | 00 b | 10 b | +| 11000 b | 11 b | 01 b | +| 11001 b | 11 b | 10 b | +| 11010 b | 11 b | 01 b | +| 11011 b | 11 b | 10 b | +| 11100 b | 01 b | 11 b | +| 11101 b | 01 b | 11 b | +| 11110 b | 10 b | 11 b | +| 11111 b | 10 b | 11 b | + +Figure 15 shows the constellation for the case $b = 5$ . + +| | | | | | | | +|-------------|----|----|--|----|----|----| +| | 24 | 26 | | 20 | 22 | | +| | 19 | 09 | | 01 | 03 | 17 | +| | 18 | 08 | | 00 | 02 | 16 | +| | 31 | 13 | | 05 | 07 | 29 | +| | 30 | 12 | | 04 | 06 | 28 | +| | 25 | 27 | | 21 | 23 | | +| T1533420-99 | | | | | | | + +**Figure 15/G.992.2 – Constellation labels for $b = 5$** + +The 7-bit constellation shall be obtained from the 5-bit constellation by replacing each label $n$ by the $2 \times 2$ block of labels as shown in Figure 13. + +Again, the same procedure shall be used to construct the larger odd-bit constellations recursively. + +### 7.9 Gain scaling + +For the transmission of ATU data symbols, a gain scaling, $g_i$ , shall be applied to all tones as requested by the ATU receiver during initialization and possibly updated during SHOWTIME via the bit swap procedure. Only values of $g_i$ within a range of approximately 0.19 to 1.33 (i.e. from $-14.5$ dB to $+2.5$ dB) may be used. For the transmission of synchronization symbols, gain scaling shall be applied as defined in Annexes A, B and C. + +The $g_i$ values are constrained by additional limits defined in Annexes A and B. + +Each point, $(X_i, Y_i)$ , or complex number, $Z_i = X_i + jY_i$ , output from the encoder is multiplied by $g_i$ : $Z'_i = g_i Z_i$ . + +### 7.10 Modulation + +Modulation shall use the maximum number of subcarriers $N_{SC}$ . Table 8 defines parameters for the upstream and downstream modulation referenced in the modulation sub-paragraphs. + +The actual number of subcarriers employed to modulate data may be less than the maximum and is determined during the initialization sequence. The transmitter shall designate a subset of the maximum subcarriers available for a connection during the C-REVERB1 or R-REVERB1 signals. The receiver shall designate a further subset of the transmitted subcarriers used for data modulation during the C-B&G and R-B&G signals. + +ATU-R receivers shall be capable to receive the maximum set of subcarriers $N_{SC-DN}$ . + +**Table 8/G.992.2 – Parameters for upstream and downstream modulation** + +| Symbol | Description | Upstream | Downstream | +|------------|-------------------------------------------------------------|--------------------|---------------------| +| $N_{SC}$ | Number of subcarriers | $N_{SC-UP} = 32$ | $N_{SC-DN} = 128$ | +| $N_{IDFT}$ | Number of output values of the IDFT ( $= 2 \times N_{SC}$ ) | $N_{IDFT-UP} = 64$ | $N_{IDFT-DN} = 256$ | +| $N_{CP}$ | Number of cyclic prefix values ( $= N_{SC}/8$ ) | $N_{CP-UP} = 4$ | $N_{CP-DN} = 16$ | + +### 7.10.1 Subcarriers + +The frequency spacing, $\Delta f$ , between subcarriers is 4.3125 kHz, with a tolerance of $\pm 50$ ppm. The subcarriers at frequencies $f = n\Delta f$ are numbered $n = 1, 2 \dots N_{SC}$ . + +#### 7.10.1.1 Data subcarriers + +The initialization signals defined in clause 11 allow for a maximum of $N_{SC} - 1$ subcarriers, from $n = 1$ to $N_{SC} - 1$ . + +The maximum number of data subcarriers may be reduced. The lower limit of $n$ depends upon the presence of an optional POTS splitter, PSD masks, implementation specific filters and service options. In any case, the range of useable $n$ is determined during channel analysis. + +#### 7.10.1.2 Downstream Pilot subcarrier + +In the downstream direction, subcarrier $n = 64$ ( $f = 64 \times \Delta f$ kHz) shall be reserved for a pilot; that is $b(64) = 0$ and $g(64) = g_{sync}$ . The pilot is transmitted from the ATU-C. The value $g_{sync}$ represents the gain scaling applied to the sync symbol as defined in Annexes A, B and C. + +The data modulated onto the pilot subcarrier shall be a constant $\{0,0\}$ generating the $\{+,+\}$ constellation point. Use of this pilot allows resolution of sample timing in a receiver modulo-4 modulator output values. Therefore a gross timing error that is an integer multiple of four modulator output values could still persist after a micro-interruption (e.g. a temporary short-circuit, open circuit or severe line hit); correction of such timing errors is made possible by the use of the synchronization symbol defined in 7.10.3. + +#### 7.10.1.3 Nyquist frequency subcarrier + +The Nyquist frequency subcarrier $n = N_{SC}$ shall not be used for data. Uses other than data are for further study. + +#### 7.10.1.4 DC component + +The DC component ( $n = 0$ ) shall not be used and shall contain no energy. + +### 7.10.2 Modulation by the inverse discrete Fourier transform (IDFT) + +The modulating transform defines the relationship between the $N_{IDFT}$ real values $x_n$ and the values $Z_i$ . + +The encoder and gain scaling generate only $N_{SC} - 1$ complex values of $Z'_i$ . These input values shall be augmented so that the vector $Z''_i$ has Hermitian symmetry in order to generate real values of $x_n$ . That is: + +$$Z''_0 = 0 \text{ (the DC component)}$$ + +$$Z''_i = Z'_i \text{ for } i = 1 \text{ to } N_{SC} - 1$$ + +$$Z''_{N_{SC}} = \text{the Nyquist frequency subcarrier which is for further study, and}$$ + +$$Z''_i = \text{conj}(Z_{N_{IDFT}-i}) \text{ for } i = N_{SC} + 1 \text{ to } N_{IDFT} - 1$$ + +The real valued output sequence $x_n$ of the modulator is generated using the IDFT transform: + +$$x_n = \sum_{i=0}^{N_{IDFT}-1} \exp(j\pi K_i/N_{SC}) Z''_i$$ + +### 7.10.3 Synchronization symbol + +The synchronization symbol permits recovery of the frame boundary after micro-interruptions that might otherwise force retraining. A synchronization symbol shall be inserted after every 68 data symbols. The synchronization symbol shall be constructed using a data pattern $d_n$ , $n = 1$ to $2 \times N_{sc}$ with the following encoding method. + +The first pair of bits ( $d_1$ and $d_2$ ) shall be used for the dc component ( $i = 0$ ) and the Nyquist frequency subcarrier ( $i = N_{sc}$ ) (the power assigned to them is, of course, zero, so the bits are effectively ignored); the first and second bits of subsequent pairs are then used to define the $X_i$ and $Y_i$ for $i = 1$ to $N_{sc} - 1$ as shown in Table 9. No gain scaling shall be applied. + +**Table 9/G.992.2 – Mapping of two data bits into a 4-QAM constellation** + +| $d_{2i} + 1, d_{2i} + 2$ | Decimal label
(see Note) | $X_i, Y_i$ | +|---------------------------------|-----------------------------|------------| +| 0 b , 0 b | 0 | ++ | +| 0 b , 1 b | 1 | +− | +| 1 b , 1 b | 3 | −− | +| 1 b , 0 b | 2 | −+ | + +NOTE – This is different from the mapping in Figure 12, since $d_{2i} + 1$ is the first and least significant bit. + +The minimum set of subcarriers to be used is the set used for data transmission (i.e. those for which $b_i > 0$ ); subcarriers for which $b_i = 0$ may be used at a reduced PSD as defined in A.2.2.3 and B.2.2.3. The data modulated onto each subcarrier shall be as defined above; it shall not depend on which subcarriers are used. + +### 7.10.4 Upstream data pattern + +The data pattern used in the upstream synchronization symbol shall be the pseudo-random sequence UPRD $d_n$ , for $n = 1$ to $2 \times N_{SC-UP}$ , defined by: + +$$d_n = 1 \quad \text{for } n = 1 \text{ to } 6$$ + +$$d_n = d_{n-5} \oplus d_{n-6} \quad \text{for } n = 7 \text{ to } 2 \times N_{SC-UP}$$ + +The bits $d_1$ - $d_6$ are re-initialized for each symbol, so each symbol uses the same data. + +### 7.10.5 Downstream data pattern + +The data pattern used in the downstream synchronization symbol shall be the pseudo-random sequence DPRD $d_n$ , for $n = 1$ to $2 \times N_{SC-DN}$ , defined by: + +$$d_n = 1 \quad \text{for } n = 1 \text{ to } 9$$ + +$$d_n = d_{n-4} \oplus d_{n-9} \quad \text{for } n = 10 \text{ to } 2 \times N_{SC-DN}$$ + +The bits $d_1$ - $d_9$ are re-initialized for each symbol, so each symbol uses the same data. + +In the downstream direction, bits 129 and 130, which modulate the pilot carrier, shall be overwritten by {0,0} generating the {+,+} constellation. + +### 7.11 Cyclic prefix + +The last $N_{CP}$ samples of the output of the IDFT $x_n$ , for $n = (N_{IDFT} - N_{CP}$ to $N_{IDFT} - 1)$ shall be prepended to the block of $N_{IDFT}$ samples and read out to the digital-to-analog converter (DAC) in sequence. That is, the subscripts, $n$ , of the DAC samples in sequence are as shown in Table 10. + +**Table 10/G.992.2 – Output sample order to DAC** + +| | Output sample to DAC | | +|--------------------------|----------------------|----------------------------| +| Cyclic prefix samples | $N_{IDFT} - N_{CP}$ | ← First sample transmitted | +| | ... | | +| | $N_{IDFT} - 1$ | | +| Modulator output samples | 0 | | +| | 1 | | +| | 2 | | +| | ... | | +| | $N_{IDFT} - 1$ | ← Last sample transmitted | + +T1533430-99 + +The cyclic prefix shall be used for data and synchronization symbols beginning with the C-RATES1 and R-REVERB3 segment of the initialization sequence, as defined in clause 11. + +### 7.12 Transmitter dynamic range + +The transmitter includes all analog transmitter functions: The DAC, the anti-aliasing filter, the hybrid circuitry, and the POTS splitter. The transmitted signal shall conform to the frequency requirements as described in 7.10.1 for frequency spacing. + +#### 7.12.1 Maximum clipping rate + +The maximum output signal of the transmitter shall be such that the output signal shall be clipped no more than 0.00001% of the time. + +#### 7.12.2 Noise/Distortion floor + +The signal-to-noise plus distortion ratio of the transmitted signal in a given subcarrier is specified as the ratio of the rms value of the tone in that subcarrier to the rms sum of all the non-tone signals in the 4.3125 kHz frequency band centered on the subcarrier frequency. This ratio is measured for each subcarrier used for transmission using a MultiTone Power Ratio (MTPR) test as shown in Figure 16. + +![Figure 16/G.992.2 – MTPR test. A graph showing dBm per bin on the y-axis and Frequency on the x-axis. It displays a comb of tones with one tone suppressed, and a non-linear distortion component indicated by a dashed line.](71c152ac7a8ce3d70adcd78b3363a65e_img.jpg) + +The figure shows a plot of power density (dBm per bin) versus frequency. A series of vertical lines represent a comb of tones spaced by $\Delta f$ . One of these tones is missing, indicated by a dashed vertical line. A bracket below the x-axis labels the group of tones as 'A comb of $\Delta f$ -spaced tones with one tone suppressed'. An arrow points to a small, lower-amplitude signal between the main tones, labeled 'Non-linear distortion component'. The x-axis is labeled 'Frequency' and the y-axis is labeled 'dBm per bin'. A small code 'T1533440-99' is present in the bottom right of the graph area. + +Figure 16/G.992.2 – MTPR test. A graph showing dBm per bin on the y-axis and Frequency on the x-axis. It displays a comb of tones with one tone suppressed, and a non-linear distortion component indicated by a dashed line. + +**Figure 16/G.992.2 – MTPR test** + +Over the transmission frequency band, the MTPR of the transmitter in any subcarrier shall be no less than $(3N_{\text{downi}} + 20)$ dB, where $N_{\text{downi}}$ is defined as the size of the constellation (in bits) to be used on subcarrier $i$ . The minimum transmitter MTPR shall be at least 38 dB (corresponding to an $N_{\text{downi}}$ of 6) for any subcarrier. + +NOTE – Signals transmitted during normal initialization and data transmission cannot be used for this test because the DMT symbols have a cyclic prefix appended, and the PSD of a non-repetitive signal does not have nulls at any subcarrier frequencies. A gated FFT-based analyser could be used, but this would measure both the non-linear distortion and the linear distortion introduced by the transmit filter. Therefore this test will require that the transmitter be programmed with special software – probably to be used during development only. The subject of an MTPR test that can be applied to a production modem is for further study. + +### 7.12.3 Transmitter spectral masks + +Spectral masks for the two service options are defined in Annexes A and B. For Non-Overlapped Spectrum operation, see Annex A. For Overlapped Spectrum operation, see Annex B. + +NOTE – The band from 25 to 552 kHz that is referred to is the widest possible band (used for ADSL over POTS implemented with echo cancelling). Limits defined within this band apply also to any narrower bands used. + +## 8 Embedded Operations Channel (eoc) + +### 8.1 eoc introduction + +An embedded operations channel for communication between the ATU-C and ATU-R shall be supported for in-service and out-of-service maintenance and for the retrieval of ATU-R status information and performance monitoring parameters. + +This subclause defines the messages and protocols of the eoc channel. In addition, this subclause describes the "clear eoc channel". The encoding of these messages is defined in 8.2. The insertion of eoc messages into the superframe structure is defined in 7.3.3.1.1.1. + +#### 8.1.1 eoc messages overview + +The eoc messages are organized into four basic types: + +- 1) Bidirectional eoc messages are sent by the ATU-C and require the use of the eoc command protocol. +- 2) ATU-C to ATU-R messages are sent by the ATU-C as part of the eoc read protocol. +- 3) ATU-R to ATU-C messages are sent by the ATU-R as eoc command protocol responses or autonomous messages. +- 4) Clear eoc messages: These messages are transmitted as autonomous messages and may be sent by either the ATU-C or ATU-R. + +#### 8.1.2 eoc protocol overview + +eoc protocol actions are dependent upon which state the protocol is in Figures 18 and 19 (in 8.4.2) illustrate the various eoc protocol states for both the ATU-C and ATU-R. + +The eoc protocol allows the ATU-C (acting as master) to invoke eoc commands and the ATU-R (acting as slave) to respond to the commands. As the master, the ATU-C determines the rate of eoc commands over the link. + +The eoc channel may also transmit autonomous messages in both the upstream and downstream direction. Using autonomous messages, the ATU-R can signal the ATU-C of events and initiate certain eoc commands. In addition, autonomous messages allow the ATU-C and ATU-R to exchange the clear eoc channel information. + +During periods of no eoc activity, the eoc channel may be filled with either a HOLD or RTN eoc message as described in 8.3 or by a "no synchronization action" as described in 7.3.3.1.1.1. + +If the ATU-R receives an eoc command that it cannot comply with, the ATU-R shall reply with a "Unable to Comply" message as described in 8.3. + +## 8.2 eoc message encoding + +The 13 bits of an eoc message are partitioned into five fields, which are summarized in Table 11. + +**Table 11/G.992.2 – eoc message fields** + +| Field # | Bit(s) | Field | Notes | +|---------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| +| 1 | 1, 2 | ADDRESS field | Can address four locations | +| 2 | 3 | DATA (0 b ) or OPCODE (1 b ) field | | +| 3 | 4 | BYTE PARITY field
Odd (binary 1) or even (0 b ) | Byte order indication for multi-byte transmission | +| 4 | 5 | AUTONOMOUS MESSAGE field
ATU-C: Set to 1 b for ATU-C commands sent to ATU-R, set to 0 b for autonomous transfers.
ATU-R: Set to 1 b for response to ATU-C command, set to 0 b for autonomous transfers. | | +| 5 | 6-13 | INFORMATION field | See Table 13 | + +### 8.2.1 ADDRESS field (# 1) + +The two bits of the ADDRESS field can address up to four locations. Only two locations are presently defined (Table 12). + +**Table 12/G.992.2 – ADDRESS field encoding** + +| Address bit (1, 2) | Location | +|--------------------|-------------------| +| 00 b | ATU-R | +| 01 b | Reserved by ITU-T | +| 10 b | Reserved by ITU-T | +| 11 b | ATU-C | + +The ATU-C shall address messages to the ATU-R by setting the ADDRESS field equal to the ATU-R address. When responding to an eoc message from the ATU-C, the ATU-R shall keep the ADDRESS field equal to its own ATU-R address. Only when sending an autonomous message to the ATU-C shall the ATU-R set the ADDRESS field equal to the ATU-C address. + +### 8.2.2 DATA or OPCODE field (# 2) + +A 0b in this field indicates that the INFORMATION field of the current eoc message contains a data byte; a 1b indicates that it contains an operation code for an eoc message. See Table 13. + +**Table 13/G.992.2 – INFORMATION field functions** + +| DATA
(Bit 3) | AUTONOMOUS MESSAGE
(Bit 5) | Function of INFORMATION field | +|-------------------------|---------------------------------------|----------------------------------------------------------| +| 0 b | 0 b | Data carries a clear eoc data octet. | +| 0 b | 1 b | Data used for read or write. | +| 1 b | 0 b | Data carries an autonomous message opcode. See Table 11. | +| 1 b | 1 b | Data carries an eoc command opcode. See Table 11. | + +### **8.2.3 BYTE PARITY field (# 3)** + +When using the Next Byte opcode to read or write the first data byte of an eoc register, this bit shall be set to 1b to indicate "odd" byte. For the next byte, it shall be set to 0b to indicate "even" byte and so on, alternately. + +The BYTE PARITY field shall always be set to 1b if the eoc message is an autonomous message or if the information field carries an opcode different from the Next Byte opcode. The BYTE PARITY field may be set to 0b otherwise. + +### **8.2.4 AUTONOMOUS MESSAGE field (# 4)** + +The ATU-C sets this field to a 1b to indicate that the current eoc message is an eoc protocol command (master) message, and sets it to a 0b to indicate that the eoc message is an autonomous message. The ATU-R sets this field to a 1b to indicate that the current eoc message is an eoc protocol response (slave) message, and sets it to a 0b to indicate that it is an autonomous message. See Table 13. + +### **8.2.5 INFORMATION field (# 5)** + +The function of the INFORMATION field depends upon the settings of other message fields. The encoding indicated by DATA field and AUTONOMOUS MESSAGE field together (bits 3 and 5) indicate the function of the INFORMATION field. The valid encodings are summarized in Table 13. + +## **8.3 eoc message description** + +Valid eoc messages and their opcodes are summarized in Table 14. The opcode values are given in hex (MSB left, LSB right) with the MSB mapping to bit eoc13 and the LSB to bit eoc6. The Direction D/U indicates that the message may be sent both in the downstream and upstream direction. The Direction D or U indicates that the message is transmitted in the downstream or upstream direction respectively. + +**Table 14/G.992.2 – eoc message opcodes** + +| Bidirectional eoc messages | | | | +|-----------------------------------|---------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Value | Abbreviation | Direction | Opcode meaning | +| 01 16 | HOLD | D/U | The message "Hold" tells the ATU-R to transition to the idle state and maintain any previously latched operations. This message may also be transmitted during the idle state. | +| F0 16 | RTN | D/U | The message "Return to Normal" releases all outstanding eoc-controlled operations (latched conditions) at the ATU-R and returns the eoc protocol system to the idle state. This message may also be transmitted during the idle state. | +| 02 16 | SLFTST | D/U | The message "Self Test" requests the ATU-R to perform a self test. The result of the self test shall be stored in the self-test data result register. | +| 07 16 | REQCOR | D/U | The message requests the ATU-R to send corrupt crc bits to the ATU-C until cancelled by the "Request End of Corrupt crc" or "Return to Normal" message. This command shall be latching as per 8.3.1. | +| 08 16 | REQEND | D/U | The message requests the ATU-R to stop sending corrupt crc bits to the ATU-C. | +| 0B 16 | NOTCOR | D/U | The message notifies the ATU-R that the ATU-C shall send corrupt crc bits until cancellation is indicated by "Notify End of Corrupted crc" or "Return to Normal". This command shall be latching as per 8.3.1. | +| 0D 16 | NOTEND | D/U | The message notifies the ATU-R that the ATU-C has stopped sending corrupt crc bits. | +| 0E 16 | EOD | D/U | The message "End of Data" is sent by the ATU-C as part of the eoc write protocol after it has sent all bytes of data to the ATU-R.
This message has a slightly different meaning when sent by the ATU-R, as defined in 8.3.2. | +| 13 16 | REQTPU | D/U | This message requests the ATU-R to update the test parameter set as defined in 10.2. Test parameters supported by the ATU-R shall be updated and stored in a data register within 10 s after the request is received. | +| 16 16 | GNTPDN | D/U | This message is sent by the ATU-C to acknowledge a REQPDN from the ATU-R or to initiate a power down request itself. When the ATU-R receives GNTPDN, it uses the value of data register A to determine the power management link state granted by the ATU-C. See 13.4. | +| 83 16 | REJPDN | D/U | This message is sent by the ATU-C to acknowledge a REQPDN from the ATU-R. When the ATU-R receives REJPDN, it cancels its REQPDN request, and remains in the current link state. See 13.5.1. | + +**Table 14/G.992.2 – eoc message opcodes (continued)** + +| Bidirectional eoc messages | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Value | Abbreviation | Direction | Opcode meaning | +| (20 16 , 23 16 ,
25 16 , 26 16 )
(29 16 , 2A 16 ,
2C 16 , 2F 16 )
(31 16 , 32 16 ,
34 16 , 37 16 )
(38 16 , 3B 16 ,
3D 16 , 3E 16 ) | WRITE | D/U | This write or receive message directs the ATU-R to enter the Data Write Protocol state, receive data, and write it in the data register specified by the Opcode. Opcode 20 16 , and 3E 16 , correspond to data register 0 16 , and F 16 , respectively. | +| (40 16 , 43 16 ,
45 16 , 46 16 )
(49 16 , 4A 16 ,
4C 16 , 4F 16 )
(51 16 , 52 16 ,
54 16 , 57 16 )
(58 16 , 5B 16 ,
5D 16 , 5E 16 ) | READ | D/U | This read or send message directs the ATU-R to enter the Data Read Protocol state, read data from the data register specified by the Opcode, and transmit it to the ATU-C. Opcode 40 16 and 5E 16 correspond to data register 0 16 and F 16 , respectively. | +| ATU-C to ATU-R (downstream) messages | | | | +| Value | Abbreviation | Direction | Opcode meaning | +| 10 16 | NEXT | D/U | This message is sent multiply by the ATU-C (toggling bit four for multi-byte data until all data has been sent) while it is in Data Read Protocol state (i.e. after the ATU-R has acknowledged the previously sent Receive/Write Data command). | +| ATU-R to ATU-C (upstream) messages | | | | +| Value | Abbreviation | Direction | Opcode meaning | +| 15 16 | REQPDN | U | This is an autonomous message sent by the ATU-R to initiate a transition to a new power management link state. REQPDN is acknowledged by the ATU-C by optionally writing the value of the granted link state into data register A, and sending GNTPDN. Or, the ATU-C can send REJPDN to reject the requested link state. See 13.5.1. | +| E7 16 | DGASP | U | This is an autonomous (i.e. unsolicited) message that the ATU-R may send to indicate the pending loss of link because the ATU-R has lost power; see 8.3.3. | +| 04 16 | UTC | U | This is a message is sent by the ATU-R to acknowledge receipt of eoc message that it cannot perform. | + +**Table 14/G.992.2 – eoc message opcodes (concluded)** + +| Reserved Opcodes | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Value | Abbreviation | Direction | Opcode meaning | +| (19 16 , 1A 16 ,
1C 16 , 1F 16 ) | | D/U | Four message opcodes are reserved for vendor proprietary use. The ATU-C shall read the Vendor ID (identification) code data register of the ATU-R to ensure compatibility between ATUs before using proprietary opcodes. | +| (80 16 , 85 16 ,
86 16 , 89 16 ,
8A 16 , 8C 16 ,
8F 16 ) | | | Reserved by ITU-T. | + +### 8.3.1 Latching bidirectional eoc messages + +Some of the bidirectional eoc messages transmitted by the ATU-C are "latching" commands, meaning that a subsequent eoc message, transmitted from the ATU-C, shall be required to release the ATU-R from that state. Thus, multiple eoc-initiated actions can be in effect simultaneously. A separate command, "Return To Normal", is used to unlatch all latched states. This command is also used to bring the eoc protocol system to a known state, the Idle State, when no commands are active in the ATU-R location. To maintain the latched condition, the command "Hold State" shall be sent to bring the eoc protocol system to a known state, the Idle State. + +### 8.3.2 End of Data message (EOD) + +This message is sent by the ATU-C as part of the eoc write protocol after it has sent all bytes of data to the ATU-R. + +This message may have a slightly different meaning when sent by the ATU-R. This message may be sent by the ATU-R: + +- in response to an "End of Data" message from the ATU-C; +- in response to a "Next Byte" message from the ATU-C that is received after all bytes have been read from the currently addressed ATU-R register; or +- in response to a message from the ATU-C that contains a data byte after all bytes have been written to the currently addressed ATU-R register. + +### 8.3.3 Dying Gasp message (DGASP) + +The ATU-R shall have the ability to detect when the electrical power has been shut off. After such detection of a near-end Loss of Power (lpr) defect (see 10.3.2), the ATU-R shall insert priority eoc messages into the upstream data to implement a "dying gasp" as an lpr indicator. + +At least six contiguous dying gasp eoc messages shall be inserted in the next (at least twelve) available upstream bytes available for eoc beginning with an even-numbered frame, regardless of the number of eoc frames received in the downstream channel. + +The ATU-C shall not send a response to a "dying gasp" message back to the ATU-R. An lpr indicator is present at the ATU-C if at least four "dying gasp" messages are received within the last twelve contiguous upstream bytes available for eoc, beginning with the even-numbered frame (see Loss of Power primitive definition in 10.3.2). Sending the "dying gasp" shall not cause the ATU-R to change the eoc protocol state, nor shall receiving it cause the ATU-C to immediately change state. + +### 8.3.4 Autonomous messages + +Autonomous messages are unsolicited data transfers that can be initiated by either the ATU-C or ATU-R. + +Autonomous messages can be inserted regardless of the state of the eoc protocol state machine and do not affect the eoc protocol state. An autonomous message allows for the transport of a single byte of data. Consecutive autonomous messages can be issued as soon as appropriate eoc bytes in the superframe are available. The flow of autonomous messages may be interrupted at any time for bidirectional, ATU-C to ATU-R or ATU-R to ATU-C eoc messages. + +### 8.3.5 Data registers in the ATU-R + +Table 15 summarizes the ATU-R data registers and their applications. The register numbers are given in hexadecimal. Use of some registers is restricted as read only. Some registers are multi-byte and shall be read most significant byte first. Registers $9_{16}$ and $B_{16}$ through $F_{16}$ are reserved for future use by the ITU-T. The ATU-R shall respond with a UTC (Unable to Comply) if requested to read from or write to one of these registers. + +**Table 15/G.992.2 – ATU-R data registers** + +| Number | Use | Length | Description | +|----------|------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $0_{16}$ | Read | 8 bytes | ATU-R Vendor ID | +| $1_{16}$ | Read | Vendor discretionary | ATU-R Revision number | +| $2_{16}$ | Read | 32 bytes | ATU-R Serial number (32 bytes): The format of the ATU-R Serial number is vendor discretionary. | +| $3_{16}$ | Read | Vendor discretionary | Self Test Results: The most significant byte of the Self Test Results shall be $00_{16}$ if the selftest passed, and 01 hex if it failed (the meaning of "failure" is vendor discretionary); other values are reserved for future use. The length and syntax of the remainder are vendor discretionary. | +| $4_{16}$ | Read/Write | Vendor discretionary | Vendor discretionary | +| $5_{16}$ | Read/Write | Vendor discretionary | Vendor discretionary | +| $6_{16}$ | Read | 1 byte | Line attenuation: The line attenuation is defined in 10.4. | +| $7_{16}$ | Read | 1 byte | SNR Margin: The SNR margin is defined in 10.4. | + +**Table 15/G.992.2 – ATU-R data registers (concluded)** + +| Number | Use | Length | Description | +|-------------------|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 8 16 | Read | 30 bytes |

ATU-R configuration: The ATU-R configuration data, as defined in 7.3, shall be read (one byte for each variable) in the following order:

Downstream:

Reserved, BI(AS0), reserved, reserved,
Reserved, reserved, reserved, reserved,
Reserved, reserved, reserved, reserved,
Reserved, reserved, reserved.

Upstream:

Reserved, BI(LS0), reserved, reserved,
reserved, reserved, reserved.

Downstream:

Reserved, RSI, S, D (RSI = RI/S)

Upstream:

Reserved, RSI, S, D (RSI = RI/S),
Reserved bytes shall be set to 0016.

| +| 9 16 | Reserved | Reserved | | +| A 16 | Read/Write | 1 byte |

Link State: When a link state transition request is pending from the ATU-R, then the value of register A shall be set to the requested link state. At all other times, the value of register A shall contain the current power management link state.

Link State encoding (hexadecimal):

L0: 0016
L1: 0116
L3: 0316

Reserved by the ITU-T: 0216 and 04-7F16

| +| B-F 16 | Reserved | Reserved | | + +#### 8.4 eoc protocol + +The eoc protocol operates in a repetitive command and response mode. The ATU-C acts as the master and issues bidirectional eoc messages. The ATU-R acts as slave and responds to the bidirectional messages issued by the ATU-C by echoing the message back to the ATU-C. + +Three identical properly-addressed consecutive (i.e. no other eoc messages are received in between) messages shall be received before an action is initiated (both at ATU-C and ATU-R). Only one command and only three or fewer messages, under the control of the ATU-C, shall be outstanding (i.e. unacknowledged) at any one time. + +NOTE – This restriction on the number of messages guarantees that an ATU-R with fewer opportunities to insert eoc frames into the upstream path will be able to acknowledge all eoc messages from the ATU-C. + +Autonomous messages are transmitted transparent to the eoc protocol and do not change the protocol state at the ATU-R and ATU-C. + +#### 8.4.1 Outstanding eoc messages + +The procedure for dealing with outstanding messages at the ATU-C is shown in Figure 17. The ATU-C may only begin transmission of a new eoc message after reception of three consecutive ATU-R echoes of any current outstanding eoc message. When one or two messages are outstanding, the ATU-C may only repeat the previous message sent; thereby ensuring that all outstanding messages will be identical. Upon initialization, the ATU-C shall have no outstanding messages. + +![ATU-C state diagram for outstanding eoc messages showing four states: 3 outstanding messages, 2 outstanding messages, 1 outstanding message, and 0 outstanding messages (see Note). Transitions are labeled S (Send new message), R (Repeat last message), E (EOC message received), and DC (Dummy code).](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) + +``` +stateDiagram-v2 + [*] --> S0 : 0 outstanding messages (see Note) + S0 --> S1 : S + S1 --> S2 : R + S2 --> S3 : R + S3 --> S0 : E + S3 --> S2 : E + S2 --> S1 : E + S1 --> S0 : E + S3 --> S3 : DC +``` + +S Send new message +R Repeat last message +E EOC message received +DC Dummy code + +ATU-C state diagram for outstanding eoc messages showing four states: 3 outstanding messages, 2 outstanding messages, 1 outstanding message, and 0 outstanding messages (see Note). Transitions are labeled S (Send new message), R (Repeat last message), E (EOC message received), and DC (Dummy code). + +T1533450-99 + +NOTE – Immediately after initialization the ATU-C shall have no outstanding messages. + +**Figure 17/G.992.2 – ATU-C state diagram for outstanding eoc messages** + +For E, R, and S all the eoc messages with bit 5 set to 1b shall be considered. Other eoc messages shall not cause a change of state in the eoc state machine. + +Whenever there are three outstanding messages, the ATU-C shall stop sending messages and stuff the available eoc bandwidth with "no synchronization action" bytes or autonomous message bytes. Sending eoc messages may be resumed after receiving one or more acknowledgements (echoes) from the ATU-R. Only one command shall be outstanding at any time. Therefore, all outstanding eoc messages shall be identical. To deal with eoc messages that are not echoed by the ATU-R (e.g. those that are erased from the line due to impulse noise and will therefore remain outstanding), the ATU-C shall implement an adequate error recovery mechanism. This mechanism does not affect interoperability and is therefore outside the scope of this Recommendation. + +The eoc protocol state diagrams of the ATU-R and ATU-C shall be as shown in Figures 18 and 19. + +![State machine diagram for the eoc receiver at ATU-R. It includes states: Data Read State (odd), Data Read State (even), Pre-read state, Idle state, UTC state, Pre-write state, Data Write State (odd), and Data Write State (even). Transitions are labeled with conditions like # 'NEXT odd' == 3, # 'NEXT even' == 3, # 'READ' == 3, # 'any message' == 3, # 'WRITE' == 3, # 'DATA odd' == 3, # 'DATA even' == 3, # 'EOD' == 3, # 'RTN' == 3, # 'HOLD' == 3, # 'not supported message' == 3, and i++. States contain logic for reading, writing, and handling messages based on odd/even parity and length constraints.](5db6545aedab79741ebae9b27bb363b3_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle state + Idle state --> Data Read State (odd): # "NEXT odd" == 3 + Idle state --> Data Read State (even): # "NEXT even" == 3 + Idle state --> UTC state: # "any message" == 1 + Idle state --> Pre-read state: # "READ" == 3 + Idle state --> Pre-write state: # "WRITE" == 3 + Idle state --> Data Write State (odd): # "DATA odd" == 3 + Idle state --> Data Write State (even): # "DATA even" == 3 + Idle state --> [*]: # "EOD" == 3 + Data Read State (odd) --> Data Read State (even): # "NEXT even" == 3, i++ + Data Read State (even) --> Data Read State (odd): # "NEXT odd" == 3 + Data Read State (odd) --> Pre-read state: (# "RTN" == 3) || (# "HOLD" == 3) + Data Read State (even) --> Pre-read state: (# "RTN" == 3) || (# "HOLD" == 3) + Data Read State (odd) --> [*]: # "NEXT odd" == 3 + Data Read State (even) --> [*]: # "NEXT even" == 3 + Pre-read state --> Idle state: # "READ" == 3 + Pre-read state --> Data Read State (odd): # "NEXT odd" == 3 + Pre-read state --> Data Read State (even): # "NEXT even" == 3 + Pre-read state --> [*]: (# "RTN" == 3) || (# "HOLD" == 3) + UTC state --> Idle state: # "any message" == 1 + UTC state --> [*]: # "not supported message" == 3 + UTC state --> [*]: from any state + Pre-write state --> Idle state: # "WRITE" == 3 + Pre-write state --> Data Read State (odd): # "NEXT odd" == 3 + Pre-write state --> Data Read State (even): # "NEXT even" == 3 + Pre-write state --> [*]: # "EOD" == 3 + Data Write State (odd) --> Data Write State (even): # "DATA even" == 3, i++ + Data Write State (even) --> Data Write State (odd): # "DATA odd" == 3 + Data Write State (odd) --> [*]: # "DATA odd" == 3 + Data Write State (even) --> [*]: # "DATA even" == 3 + Data Write State (odd) --> Pre-read state: # "RTN" == 3 + Data Write State (even) --> Pre-read state: # "RTN" == 3 + Data Write State (odd) --> [*]: # "HOLD" == 3 + Data Write State (even) --> [*]: # "HOLD" == 3 + + state "Data Read State (odd)" as Data Read State (odd) { + if (# "NEXT odd" >= 3) + { if (i <= LENGTH) + return("DATA odd",d[i]) + else return("EOD"); + } else echo(message); + } + state "Data Read State (even)" as Data Read State (even) { + if (# "NEXT even" >= 3) + { if (i <= LENGTH) + return("DATA even",d[i]) + else return("EOD"); + } else echo(message); + } + state "Pre-read state" as Pre-read state { + i = 1; + echo (message); + } + state "Idle state" as Idle state { + if (# "any message" == 3) + execute(message); + echo(message); + } + state "UTC state" as UTC state { + return("UTC"); + } + state "Pre-write state" as Pre-write state { + i = 1; + echo(message); + } + state "Data Write State (odd)" as Data Write State (odd) { + if (# "DATA odd" >= 3) + { if (i <= LENGTH) + { read("DATA odd",d[i]) + echo message; + } else return("EOD"); + } else echo(message); + } + state "Data Write State (even)" as Data Write State (even) { + if (# "DATA even" >= 3) + { if (i <= LENGTH) + { read("DATA even",d[i]) + echo(message); + } else return("EOD"); + } else echo(message); + } + +``` + +State machine diagram for the eoc receiver at ATU-R. It includes states: Data Read State (odd), Data Read State (even), Pre-read state, Idle state, UTC state, Pre-write state, Data Write State (odd), and Data Write State (even). Transitions are labeled with conditions like # 'NEXT odd' == 3, # 'NEXT even' == 3, # 'READ' == 3, # 'any message' == 3, # 'WRITE' == 3, # 'DATA odd' == 3, # 'DATA even' == 3, # 'EOD' == 3, # 'RTN' == 3, # 'HOLD' == 3, # 'not supported message' == 3, and i++. States contain logic for reading, writing, and handling messages based on odd/even parity and length constraints. + +T1533460-99 + +Figure 18/G.992.2 – eoc receiver state machine at ATU-R + +![State machine diagram for eoc receiver at ATU-C. States include Data Read State (odd), Data Read State (even), Pre-read state, Idle state, UTC state, Pre-write state, Data Write State (odd), and Data Write State (even). Transitions are triggered by messages like # 'DATA odd'==3, # 'DATA even'==3, # 'READ'==3, # 'WRITE'==3, # 'any message'==1, # 'EOD'==3, # 'UTC'==3, or conditions like i++, i ≤ LENGTH, or logical combinations of RTN and HOLD signals.](38cbce07f83fba6d5a7c46605bd5743f_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Idle state + Idle state --> Pre-read state: # "READ"==3 + Pre-read state --> Idle state + Pre-read state --> Data Read State (odd): # "DATA odd"==3 + Data Read State (odd) --> Data Read State (even): # "DATA even"==3, i++ + Data Read State (even) --> Data Read State (odd): # "DATA odd"==3 + Data Read State (odd) --> Pre-read state: (# "RTN"==3) || (# "HOLD"==3) + Data Read State (even) --> Pre-read state: (# "RTN"==3) || (# "HOLD"==3) + Idle state --> UTC state: # "any message"==1 + UTC state --> Idle state: # "UTC"==3 + UTC state --> [*]: from any state + Idle state --> Pre-write state: # "WRITE"==3 + Pre-write state --> Idle state + Pre-write state --> Data Write State (odd): # "DATA odd"==3 + Data Write State (odd) --> Data Write State (even): # "DATA even"==3, i++ + Data Write State (even) --> Data Write State (odd): # "DATA odd"==3 + Data Write State (odd) --> Pre-read state: (# "RTN"==3) || (# "HOLD"==3) + Data Write State (even) --> Pre-read state: (# "RTN"==3) || (# "HOLD"==3) + Data Write State (odd) --> Idle state: # "EOD"==3 + Data Write State (even) --> Idle state: # "EOD"==3 + + state "Data Read State (odd)" as Data Read State (odd) { + if (# "DATA odd">=3) + { if (i ≤ LENGTH) + return("DATA odd",d[i]) + } + } + state "Data Read State (even)" as Data Read State (even) { + if (# "DATA even">=3) + { if (i ≤ LENGTH) + return("DATA even",d[i]) + } + } + state "Pre-read state" as Pre-read state { + i = 1; + } + state "Idle state" as Idle state + state "UTC state" as UTC state + state "Pre-write state" as Pre-write state { + i = 1; + } + state "Data Write State (odd)" as Data Write State (odd) + state "Data Write State (even)" as Data Write State (even) + +``` + +State machine diagram for eoc receiver at ATU-C. States include Data Read State (odd), Data Read State (even), Pre-read state, Idle state, UTC state, Pre-write state, Data Write State (odd), and Data Write State (even). Transitions are triggered by messages like # 'DATA odd'==3, # 'DATA even'==3, # 'READ'==3, # 'WRITE'==3, # 'any message'==1, # 'EOD'==3, # 'UTC'==3, or conditions like i++, i ≤ LENGTH, or logical combinations of RTN and HOLD signals. + +T1533470-99 + +Figure 19/G.992.2 – eoc receiver state machine at ATU-C + +#### 8.4.2 eoc state transitions + +The following shall govern state changes as shown in Figures 18 and 19. + +- 1) The protocol state changes are performed based on received messages. At the ATU-C, received messages are responses from the ATU-R to messages sent from the ATU-C. Depending on the ATU-C receiver protocol state, the ATU-C transmitter message set may be restricted. It is left up to the ATU-C transmitter to organize and send a sequence of message such that the right response from the ATU-R is achieved based on the receiver protocol state machines. +- 2) (#"message" = N) is true if and only if the previously received N messages are identical (i.e. all 13 bits equal) and properly addressed (i.e. having ATU-R address). (#"message" = 1) means the most recently received message is different (in at least 1 out of 13 bits) from the immediately preceding message and is properly addressed. +- 3) Moving to another state (based on the message received) shall be considered first, then the (same or new) state shall be executed. At the ATU-R, execution of commands in the Idle state shall be as described in 8.3 (invoking latching, unlatching or self test). +- 4) All the eoc messages with bit 5 set to 1b shall be considered as received messages and cause an eoc response message at the ATU-R. Other eoc messages shall not cause a change of state in the eoc state machine and shall not cause an eoc response message at the ATU-R. + +The responses allowed from the ATU-R fall into three categories: + +- 1) message/echo-response protocol states: Idle State and EXE State; +- 2) message/Unable-to-Comply-response protocol state: UTC State; +- 3) message/data-response protocol states: Data Read States and Data Write States; +- 4) (Data Read States includes Pre-Read, Data Read odd and Data Read even states) +(Data Write State includes Pre-Write, Data Write odd and Data Write even states). + +Autonomous messages do not effect the eoc protocol states. The reception of the DGASP message at the ATU-C may however cause a reset at the ATU-C leading to an eoc state change at the ATU-C (e.g. to Idle State). + +The eoc protocol shall enter the Message/Echo-response protocol state (Idle State) when the ATUs transition from the initialization and training sequence to steady state transmission. In order to cause the desired action in the ATU-R, the ATU-C shall repeat the message (without exceeding the limit of outstanding messages) until it receives three identical consecutive eoc message echoes from the ATU-R. This completes the command and response protocol, but the ATU-C may continue to send the same message thereafter. The command and response protocol for that message must be completed before a new message (containing a new command), which may induce a different protocol state in the ATU-R, may be issued. + +At the ATU-R, depending on the state it is in, various restricted sets of eoc messages shall be acceptable. These sets shall be as shown in Table 16. Reception of other, inapplicable, messages shall result in an Unable to Comply (UTC) response to the ATU-C. + +**Table 16/G.992.2 – eoc messages acceptable at the ATU-R** + +| ATU-R state | eoc messages acceptable at the ATU-R | | | | +|----------------------|--------------------------------------|-----------|-----|------| +| Idle | All messages acceptable | | | | +| UTC | All messages acceptable | | | | +| Data pre-read | Read | NEXT odd | RTN | HOLD | +| Data read odd, even | NEXT odd | NEXT even | RTN | HOLD | +| Data pre-write | WRITE | DATA odd | EOD | | +| Data write odd, even | DATA odd | DATA even | EOD | | + +#### 8.4.2.1 Message/Echo-response protocol state + +This state is identical to the Idle state shown in Figures 18 and 19. To initiate an action at the ATU-R, the ATU-C shall begin sending eoc messages with the Data/opcode set to 1b and with the appropriate message opcode in the information field. + +The ATU-R shall initiate action when, and only when, three identical, consecutive, and properly addressed eoc frames that contain a message recognized by the ATU-R have been received. The ATU-R shall respond to all received messages. The response shall be an echo of the received ADSL eoc message. The combination of the ATU-C sending an ADSL eoc frame and the ATU-R echoing the frame back comprises the Message/Echo-response protocol state. + +For the ATU-C to confirm correct reception of the message by the ATU-R, the message/echo-response ADSL eoc protocol state is repeated until the ATU-C receives three identical and consecutive echoes. This serves as an implicit acknowledgement to the ATU-C that the ATU-R has correctly received the transmitted message and is acting on it. This completes the Message/Echo-response protocol state. + +The ATU-C continuously sends the activating message after the receipt of the three valid echoes, or alternatively, it may switch to sending the "Hold State" message. If the message was one of the latching commands, then the ATU-R shall maintain the commanded condition until the ATU-C issues the appropriate command that ends the specific latched condition or until the ATU-C issues the "Return to Normal" command (at which time all latched conditions in the ATU-R shall be terminated). + +#### 8.4.2.2 Message/Unable-to-Comply response protocol state + +When the ATU-R does not support a message that it has received three times identically and consecutively, it shall respond with the Unable to Comply (UTC) ADSL eoc response message with its own address in lieu of a third identical and consecutive echo. In this manner the ATU-R will switch to the message/UTC-response protocol state. + +The transmission by the ATU-R and reception by the ATU-C of three identical, consecutive, properly-addressed Unable to Comply messages constitutes notification to the ATU-C that the ATU-R does not support the requested function, at which time the ATU-C may abandon its attempt. + +#### 8.4.2.3 Data Read State + +To read data from the ATU-R, the ATU-C shall issue a bidirectional READ eoc message to the ATU-R that specifies the register to be read. + +The ATU-C shall then request the first byte to be sent from the ATU-R by sending "Next Byte" messages with bit 4 set to 1b, indicating a request for an "odd" byte. The ATU-R shall respond to these "Next Byte" messages by echoing them until it has received three such messages consecutively, identically and properly addressed. Beginning with the third such reception, the ATU-R shall respond to the read request by sending the first byte of the register in the + +INFORMATION field of the "Next Byte" echo message. The ATU-C continues to send the "Next Byte" message and the ATU-R continues to respond with the "Next Byte" echo message containing the first byte of data in the INFORMATION field until the ATU-C has received at least three consecutive, identical and properly addressed data frames with bit 4 set to indicate "odd byte". + +If there are more data to be read, the ATU-C shall request the second byte of data by sending "Next Byte" messages with bit 4 set to 0b ("even byte"), repeating the procedure defined above for reading the first byte from the register. + +The procedure using the "Next Byte" message continues for the third and all subsequent bytes with the value of bit 4 toggling from "odd byte" to "even byte" or vice versa, on each succeeding byte. Each time bit 4 is toggled, the ATU-R echoes for two correct frames, and starts sending the data frame on the third reception. The process ends only when all data in the register has been read. + +To continue reading data, once the ATU-R is in the Data Read odd or even State, the only message that the ATU-C is allowed to send is the "Next Byte" message with bit 4 toggling. To end the data read state abnormally, the ATU-C sends either "Hold State" or "Return to Normal", depending on whether any latched states are to be retained. If the ATU-R receives any other message three times consecutively, identically and properly addressed while it is in Data Read odd or even State, it shall go into the UTC State. + +If, after all bytes have been read from the ATU-R register, the ATU-C continues to send the "Next Byte" message with bit 4 toggled, then the ATU-R shall send an "End of Data" message (with bit 3 set to 1b indicating opcode) beginning with the third such reception. + +For the ATU-C, the data read state ends either when the ATU-C has received the last requested data byte three times consecutively, identically and properly addressed, or when the ATU-C has received three consecutive, identical and properly addressed "End of Data" messages with bit 3 set to 1b. The ATU-C shall then switch itself and the ATU-R over to the Idle State with the "Hold State" or "Return to Normal" message, and the ATU-R shall release the register and leave the Data Read State after receiving three identical, consecutive and properly addressed "Hold State" or "Return to Normal" messages. + +#### **8.4.2.4 Data Write State** + +To write data to the ATU-R's memory, the ATU-C shall issue a bidirectional WRITE eoc message to the ATU-R that specifies the register to be written. When the ATU-R acknowledges with three consecutive, identical and properly addressed echo messages, the ATU-C sends the first byte of data by transmitting the DATA eoc message. The ATU-R shall acknowledge the receipt of the byte with an echo of the message. After the ATU-C is satisfied with three identical, consecutive and properly addressed echo responses, it shall start sending the next byte of data. Each time the ATU-C receives at least three identical and consecutive correct data echo responses, it shall switch to sending the next byte of data. It shall also toggle the "odd/even" bit accordingly. The ATU-C shall end the Data Write State with the EOD eoc message indicating to the ATU-R to return to the Idle State. + +To continue writing data, once the ATU-R is in the Data Write odd or even State, the only message that the ATU-C is allowed to send is the DATA eoc message. If the ATU-R receives any other message three times consecutively, identically and properly addressed while it is in Data Write state, it shall go into the UTC state. + +If, after all bytes have been written to the ATU-R register, the ATU-C continues to send a next byte of data, then the ATU-R shall send an EOD eoc message beginning with the third such reception. + +## 8.5 Clear eoc + +Support of the autonomous data messages is mandatory. It provides the channel defined in 6.1/G.997. The channel is provided in both the upstream and the downstream direction by transmission of autonomous messages with eoc field settings as shown in Table 13. + +These autonomous data messages may be transmitted from either the ATU-C or the ATU-R and are transparent to the current state of the eoc states machine. That is, these autonomous data messages transporting clear channel data can be inserted regardless of the current state of the eoc state machine. There is no requirement that these autonomous data messages be inserted contiguously. That is, other eoc messages may be inserted between any two autonomous data messages. There is also no requirement for any specific rate of insertion of autonomous data messages into the eoc. + +When a clear eoc data byte is received, the byte payload is placed in a buffer on the receiving ATU. Assembly into PDUs is defined in Recommendation G.997.1. + +The clear eoc does not support flow control. It is assumed that a higher level protocol implemented over this data path will support a flow control mechanism if required. Additionally, any system implementing a stack and application using the clear eoc (such as that defined in Recommendation G.997.1) should disable, at the higher layers, the further sending of autonomous data frames should a significant number of these higher layer messages be left without response from the receiver. + +## 9 ADSL overhead channel + +### 9.1 The ADSL Overhead Control (aoc) channel introduction + +Thirty-two bytes are allocated per superframe for transmission of aoc data. The multiplexing of the aoc channel into the superframe is described in 7.3.3.1.1.2. The aoc channel is used for bit-swapping and fast retrain profile management. Bit swapping enables an ADSL system to change the number of bits assigned to a subcarrier, or change the transmit energy of a subcarrier without interrupting data flow. Fast retrain allows the ATU transceivers to quickly change transmission characteristics during changing line conditions. + +All bit swap actions taken upon the ATU transceivers, after acknowledgement from the aoc channel, are coordinated between the ATU receiver and ATU transmitter by superframe counting. + +#### 9.1.1 Bit swap channel + +The bit swap process uses the aoc channel. All bit swap messages shall be repeated five consecutive times over the aoc channel. + +#### 9.1.2 Superframe counting + +The transceivers coordinate bit swapping at the receiver and transmitter by counting superframes. The ATU transmitters and receivers shall start superframe counters immediately upon entering SHOWTIME from either initialization or fast retrain. + +Superframe counting starts with the first superframe at beginning of SHOWTIME being superframe 0. Each transmitter shall increment its counter after transmission of a superframe. Superframe counting is performed MOD 256 in both transmitter and receiver. + +Synchronization of the corresponding transmitter and receiver superframe counters is maintained using the synchronization symbol in the superframe structure. Any form of restart that requires a transition from initialization or fast retrain to SHOWTIME shall reset the superframe counter. + +## 9.2 aoc message encoding + +An aoc message consists of an aoc header and an aoc message field as shown in Figure 20. + +![Diagram of an aoc message structure showing a 1-byte header and n-byte(s) message field(s).](789ee0a267b24f34bd1f45313e86c9a4_img.jpg) + +The diagram shows a horizontal bar representing an aoc message. It is divided into two parts by a vertical dashed line. The left part is labeled 'header' and has a dimension line above it labeled '1 byte'. The right part is labeled 'message field(s)' and has a dimension line above it labeled 'n byte(s)'. + +Diagram of an aoc message structure showing a 1-byte header and n-byte(s) message field(s). + +T1533480-99 + +Figure 20/G.992.2 – aoc message encoding + +### 9.2.1 aoc message header encoding + +The type of aoc message is identified by an eight-bit header. Table 17 summarizes valid aoc message headers. For example, in the case of a bit swap, the aoc header binary 11111111b will be detected, and the next byte of aoc data shall determine whether the message is a bit swap request or a bit swap acknowledge. A block of aoc header values (binary 1100xxxxb) is reserved for vendor-specific aoc messages. + +Table 17/G.992.2 – aoc message headers + +| aoc message header | aoc message field total length including aoc message header (bytes) | Interpretation | +|-----------------------|---------------------------------------------------------------------|-----------------------------------| +| 00001111 b | Undefined | Reserved by ITU-T | +| 1100xxxx b | Undefined | Vendor-specific message | +| 11110000 b | 1 | Unable to comply message (UTC) | +| 11111100 b | 13 | Extended bit swap request message | +| 11111111 b | 9 | Bit swap request message | +| 11111111 b | 3 | Bit swap acknowledge message | +| 00000011 b | 3 | Profile management request | +| 00000011 b | 3 | Profile management acknowledge | + +The header byte values are given in binary format (MSB left, LSB right) and represent aoc7-aoc0 bits (MSB in bit 7, LSB in bit 0) as carried in the SB. All other bytes in the aoc message shall be mapped according to the same convention. + +### 9.2.2 Profile Management Request + +The Profile Management Request message (Table 18) is sent by the ATU-R (or ATU-C) to request the ATU-C (or ATU-R) to save the current settings in a profile. Allowed values for yyyyb are from 0000b to 1111b corresponding to profile 0 and profile 15 respectively. + +**Table 18/G.992.2 – Format of the Profile Management Request message** + +| Message header | Message field | | +|-----------------------------------------------------------------------|-----------------------------------|-----------------------------------| +| | Command | Data | +| 00000011 b
(1 byte) | 00000001 b
(1 byte) | 0000yyyy b
(1 byte) | +| Interpretation: Save current profile as profile n = yyyy b | | | + +**9.2.3 Profile Management Acknowledge** + +The Profile Management Acknowledge message (Table 19) is sent by the ATU-C or ATU-R to acknowledge a Profile Management Request message from the ATU-R or ATU-C. The acknowledge message shall contain the same save profile number (n = yyyyb) as in the corresponding Profile Management Request message. Allowed values for xxxxb and yyyyb are from 0000b to 1111b corresponding to profile 0 and profile 15 respectively. + +**Table 19/G.992.2 – Format of the Profile Management Acknowledgement message** + +| Message header | Message field | | +|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------| +| | Command | Data | +| 00000011 b
(1 byte) | 00000010 b
(1 byte) | xxxxyyyy b
(1 byte) | +| Interpretation: Current profile saved as profile n = yyyy b . Highest profile number supported is m = xxxx b . | | | + +If the ATU-C (or ATU-R) cannot perform the requested save operation (e.g. because of too high a requested n value), an UTC message shall be returned. + +**9.2.4 Bit swap request message encoding** + +This message tells the transmitter which subcarriers are to be modified. The format of the request is shown in Table 20. + +**Table 20/G.992.2 – Format of the bit swap request message** + +| Message header | Message fields 1-4 | | +|-----------------------------------|--------------------|------------------| +| | Command | Subcarrier index | +| 11111111 b
(1 byte) | (1 byte) | (1 byte) | + +The request shall comprise nine bytes as follows: + +- An aoc message header consisting of eight binary ones. +- Message fields 1-4, each of which each consists of an eight-bit command followed by a related eight-bit subcarrier index. Valid eight-bit commands for the bit swap message shall be as shown in Table 21. The eight-bit subcarrier index is counted from low to high frequencies with the lowest frequency subcarrier having the number zero. The subcarrier index zero shall not be used. + +**Table 21/G.992.2 – Bit swap request commands** + +| Value | Interpretation | +|-----------------------|----------------------------------------------| +| 00000000 b | Do nothing | +| 00000001 b | Increase the number of allocated bits by one | +| 00000010 b | Decrease the number of allocated bits by one | +| 00000011 b | Increase the transmitted power by 1 dB | +| 00000100 b | Increase the transmitted power by 2 dB | +| 00000101 b | Increase the transmitted power by 3 dB | +| 00000110 b | Reduce the transmitted power by 1 dB | +| 00000111 b | Reduce the transmitted power by 2 dB | +| 00001xxx b | Reserved for vendor-discretionary commands | + +To avoid $g_i$ divergence between ATU-C and ATU-R after several bit swaps, for a $g_i$ update of $\Delta$ dB the new $g_i$ value should be given by: + +$$g_i' = (1/512) \times \text{round} (512 \times g_i \times 10^{(\Delta/20)})$$ + +### 9.2.5 Extended bit swap request message encoding + +Any on-line adaptation may be encoded in an extended bit swap request. However, because a single-bit subcarrier is not allowed, an extended bit swap request containing six fields shall be used when decreasing the number of bits on a subcarrier from two to zero, or when increasing the number of bits on a subcarrier from zero to two. The format of this extended bit swap request is similar to that of the bit swap request, but the number of message fields is increased to six, and a different message header is used. The format of the request is shown in Table 22. + +**Table 22/G.992.2 – Format of the extended bit swap request message** + +| Message header | Message fields 1-6 | | +|-----------------------------------|---------------------|------------------------------| +| 11111100 b
(1 byte) | Command
(1 byte) | Subcarrier index
(1 byte) | + +The receiver shall initiate an extended bit swap by sending an extended bit swap request message to the transmitter. This request tells the transmitter which subcarriers are to be modified. The extended bit swap request message shall comprise 13 bytes as follows: + +- an eight bit extended bit swap request message header of 11111100b; +- six message fields, one to six, each of which is defined as in Table 22. + +The receiver shall use two identical message fields to request a zero-to-two increase or a two-to-zero decrease of the number of bits on a subcarrier, according to the allowable bit-swap commands defined in Table 21. + +### 9.2.6 Bit swap acknowledge message encoding + +A bit swap acknowledge message (Table 23) shall contain the following: + +- a bit swap acknowledge message header coded 11111111b; + +- one message field, which consists of an eight-bit bit swap acknowledge command followed by an eight-bit superframe counter number. The acknowledge command shall be coded as 11111111b. The superframe counter number indicates when the bit swap is to take place. This number shall be at least 47 greater than the counter number when the request was received (this corresponds to a minimum wait time of 800 ms). + +The new bit and/or transmit power table(s) shall then take effect starting from the first frame (frame 0) of an ADSL superframe, after the specified superframe counter number has been reached. That is, if the bit swap superframe counter number contained in the bit swap acknowledge message is $n$ , then the new table(s) shall take effect starting from frame 0 of the $(n + 1)$ th ADSL superframe. + +**Table 23/G.992.2 – Format of the bit swap acknowledge** + +| Message header | Message field | | +|-----------------------------------|----------------------------------------------------------|----------------------------------------------------------| +| 11111111 b
(1 byte) | Acknowledge command
11111111 b
(1 byte) | Bit swap superframe
Counter number
$n$
(1 byte) | + +### 9.3 Bit swap operation + +Either ATU may initiate a bit swap by transmitting the bit swap request message. The bit swapping procedures in the upstream and downstream channels are independent, and may take place simultaneously. + +An ATU receiver is the initiator of a bit swap procedure. It may transmit a bit swap (extended or simple) request message and receives the bit swap acknowledge message. The ATU transmitter responds to the reception of a bit swap request message and shall transmit either the bit swap acknowledge or the Unable to Comply message. + +#### 9.3.1 Bit swap – Receiver + +The receiver shall start a time-out of $500 \pm 20$ ms from the moment it sends a bit swap request message. When neither an acknowledgement nor an UTC message has been detected in this time-out interval, the receiver shall resend a bit swap request message (which shall have the same parameters) and restart the timeout. Only when an acknowledgement has been detected within the time-out interval shall the receiver prepare for a bit swap at the time specified in the acknowledge message. + +The receiver shall then wait until the superframe counter equals the value specified in the bit swap acknowledge message. Then, beginning with frame 0 of the next ADSL superframe, the receiver shall change the bit assignment of the appropriate subcarriers and perform tone reordering based on the new subcarrier bit assignment and update applicable receiver parameters of the appropriate subcarriers to account for a change in their transmitted energy. + +Upon time-out, the bit swap message shall be re-transmitted. However, after a finite (implementation dependent) number of unsuccessful retries, the receiver shall take recovery actions to restore the aoc channel. + +A new bit swap request shall only be sent after the previous bit swap has taken place or has been denied by a UTC message or when the $500 \pm 20$ ms time-out has occurred while waiting for a bit swap acknowledge. + +### 9.3.2 Bit swap – Transmitter + +Within 400 ms after reception of the bit swap request, the transmitter shall send either a bit swap acknowledge message or a UTC (Unable to Comply) message. The transmitter should and is recommended to send the bit swap acknowledge message in case the aoc protocol is operating in a reliable environment e.g. with a filter as shown in this Recommendation's reference model or a splitter as shown in the Recommendation G.992.1 reference model. In other cases, the transmitter may send a UTC message. Mandating the transmitter to send a bit swap acknowledge message is for further study. + +After transmitting the bit swap acknowledge, the transmitter shall wait until the superframe counter equals the value specified in the bit swap acknowledge. Then, beginning with DF 0 of the next ADSL superframe, the transmitter shall change the bit assignment of the appropriate subcarriers, and perform tone re-ordering based on the new subcarrier bit assignment and change the transmit energy in the appropriate subcarriers by the desired factor. + +If the transmitter receives a new bit swap request message while waiting for the superframe counter to equal the value specified in the last bit swap acknowledge message, it shall immediately stop waiting and update the superframe counter for bit swap according to the new message. It shall restart the process for the newly arrived bit swap request message assuming that the new message equals the previous. + +## 9.4 aoc protocol + +When the aoc channel is idle, i.e. there are no aoc messages to be transported, the aoc shall insert 00000000b as a stuffing pattern in the aoc SB bytes. Hence, an aoc message begins with a non-zero byte. + +aoc messages shall be transmitted five consecutive times (i.e. five concatenated and identical messages without aoc stuffing patterns in between) for extra reliability. At least 20 aoc stuffing patterns shall be inserted between two consecutive groups of five concatenated and identical messages. + +An ATU receiving an aoc message shall act on that aoc message only if it has received three identical messages in a time period spanning five of that particular message. When an ATU receives an unrecognizable command, it shall take no action. + +In the case when a function is requested but cannot be performed by either the ATU-C or the ATU-R for any reason (e.g. to save a profile with profile number greater than support) an unable to comply message ("11110000b") shall be issued. + +There shall be a maximum of one downstream and one upstream aoc message outstanding at any time. + +## 10 In-service performance monitoring and surveillance + +The following terminology is used in this clause for description of the in-service performance monitoring and surveillance functions (see Figure 21): + +- *Near-end*: Near-end means performance of the loop-side received signal at the input of the ATU. +- *Far-end*: Far-end means performance of the downstream loop-side received signal at the input of the ATU-R, where this performance is reported to the ATU-C in upstream indicator bits or performance of the upstream loop-side received signal at the input of the ATU-C, where this performance is reported to the ATU-R in downstream overhead indicator bits; this case is a mirror image of the above. + +- *Primitives:* Primitives are basic measures of performance, usually obtained from digital signal line codes and frame formats, or as reported in overhead indicator bits from the far-end. Performance primitives are categorized as events, anomalies and defects. Primitives may also be basic measures of other quantities (e.g. ac or battery power), usually obtained from equipment indicators. +- *Anomalies:* An anomaly is a discrepancy between the actual and the desired characteristics of an item. The desired characteristics 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. Performance anomalies are defined in 10.1. +- *Defects:* A defect is 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 as a defect. +- *Thresholds:* See clause 8/G.997.1. +- *Threshold Crossing Alert:* See Recommendation G.997.1. +- *Indicator:* An indicator is the message or bits that are transmitted from the ATU-R to signal a far-end primitive anomaly or defect. + +![Diagram of in-service surveillance of the ADSL link from the ATU-C standpoint. The diagram shows a flow from Servers to Network, then into an ADSL Link containing ATU-C, Loop plant, and ATU-R. ATU-C is connected to Service modules. Arrows indicate data flow: Downstream (top) from ATU-C to ATU-R, and Upstream (bottom) from ATU-R to ATU-C. Numbered callouts describe monitoring functions: 1. Detect near-end primitives at ATU-R; 2. Set indicators for reporting of primitives in overhead; 3. Report indicators (including loss of ATU-R AC power); 4. Detect far-end primitives at ATU-C from indicators; 5. Support near-end and far-end monitoring at ATU-C. A legend at the bottom left shows a right-pointing arrow for Downstream and a left-pointing arrow for Upstream. Text at the bottom center describes 'Composite ADSL Digital Signals each with overhead (and embedded operations channel – eoc)'. A small code 'T1533490-99' is in the bottom right.](7d929ba1b7d09ea8e00b9e7abbbe50c9_img.jpg) + +ADSL Link + +1 Detect near-end primitives at ATU-R + +Services Samples + +Full + +Duplex + +Service modules + +T1533490-99 + +2 Set indicators for reporting of primitives in overhead + +3 Report indicators (including loss of ATU-R AC power) + +ATU-C + +Loop plant + +ATU-R + +1 Detect near-end primitives at ATU-C + +4 Detect far-end primitives at ATU-C from indicators + +5 Support near-end and far-end monitoring at ATU-C + +| ATU-C ↔ ATU-R | + +Composite ADSL Digital Signals each with overhead (and embedded operations channel – eoc) + +→ Downstream + +← Upstream + +Servers + +Network + +Diagram of in-service surveillance of the ADSL link from the ATU-C standpoint. The diagram shows a flow from Servers to Network, then into an ADSL Link containing ATU-C, Loop plant, and ATU-R. ATU-C is connected to Service modules. Arrows indicate data flow: Downstream (top) from ATU-C to ATU-R, and Upstream (bottom) from ATU-R to ATU-C. Numbered callouts describe monitoring functions: 1. Detect near-end primitives at ATU-R; 2. Set indicators for reporting of primitives in overhead; 3. Report indicators (including loss of ATU-R AC power); 4. Detect far-end primitives at ATU-C from indicators; 5. Support near-end and far-end monitoring at ATU-C. A legend at the bottom left shows a right-pointing arrow for Downstream and a left-pointing arrow for Upstream. Text at the bottom center describes 'Composite ADSL Digital Signals each with overhead (and embedded operations channel – eoc)'. A small code 'T1533490-99' is in the bottom right. + +**Figure 21/G.992.2 – In-service surveillance of the ADSL link shown from the standpoint of the ATU-C** + +ADSL systems have been designed to deliver packet/cell-based payloads. The performance monitoring capabilities required to maintain those systems are imbedded within the packet/cell systems. The ADSL system shall support the data path monitoring requirements as required by the specific payload technology. + +## 10.1 ADSL line related primitives + +### 10.1.1 ADSL line related near-end anomalies + +Two near-end anomalies are defined: + +- *Forward error correction (fec)-i*: An fec-i anomaly occurs when a received FEC codeword for the data stream indicates that errors have been corrected; +- *Cyclic redundancy check (crc)-i*: A crc-i anomaly occurs when a received CRC-8 code for the superframe is not identical to the corresponding locally generated code. + +### 10.1.2 ADSL line related far-end anomalies + +Two far-end anomalies are defined: + +- *Far-end forward error correction (ffec)-i*: An ffec-i anomaly is an fec-i anomaly detected at the far-end that is reported once per superframe by the fecc-i indicator bit. The fecc-i indicator bit shall be set to 1b to indicate that no fec-i anomaly is present in the previous superframe and shall be set to 0b to indicate that at least one fec-i anomaly is present in the previous superframe. An ffec-i anomaly occurs when a received fecc-i indicator bit is coded to 0b. A ffec-i anomaly terminates when a received fecc-i indicator bit is coded to 1b. +- *Far-end Block Error (febe-i) anomaly*: A febe-i anomaly is a crc-i anomaly detected at the far-end and is reported once per superframe by the febe-i indicator bit. The febe-i indicator shall be set to 1b to indicate that no crc-i anomaly is present in the previous superframe and shall be set to 0b to indicate that a crc-i anomaly is present in the previous superframe. A febe-i anomaly occurs when a received febe-i indicator is coded to 0b. A febe-i anomaly terminates when a received febe-i indicator is coded to 1b. + +### 10.1.3 ADSL line related near-end defects + +Two near-end defects are defined: + +- *Loss of signal (los)*: A reference power is established by averaging the ADSL power over a 0.1 s period and over a subset of tones after the start of steady state data transmission (i.e. after initialization), and a threshold shall be set at 6 dB below this. A los defect occurs when the level of the received ADSL power, averaged over a 0.1 s period and over the same subset of tones, is lower than the threshold, and terminates when measured in the same way it is at or above the threshold. The subset of tones over which the ADSL power is averaged, is implementation discretionary and may be restricted at the ATU-R to only the downstream pilot tone. +- *Severely errored frame (sef)*: An sef defect occurs when the content of two consecutively received synchronization symbols does not correlate with the expected content over a subset of the tones. An sef defect terminates when the content of two consecutively received synchronization symbols correlate with the expected contents over the same subset. The correlation method, the selected subset of tones, and the threshold for declaring these defect conditions are implementation discretionary. + +### 10.1.4 ADSL line related far-end defects + +Two far-end defects are defined: + +- *Far-end Loss of signal (los)*: A far-end los defect is a los defect detected at the far-end and is reported by the los indicator bit. The los indicator bit shall be set to 1b to indicate that no los defect is being reported and shall be set to 0b for six consecutive superframes to indicate that a los defect is being reported. A far-end los defect occurs when four or more out of six + +contiguous los indicators are received coded as 0b. A far-end los defect terminates when four or more out of six contiguously received los indicators are coded as 1b. + +- *Far-end Remote defect indication (rdi)*: An rdi defect is a sef defect detected at the far-end and is reported once per superframe by the rdi indicator bit. The rdi indicator bit shall be set to 1b to indicate that no sef defect is present in the previous superframe and shall be set to 0b to indicate that a sef defect is present in the previous superframe. An rdi defect occurs when a received rdi indicator is coded as 0b. An rdi defect terminates when a received rdi indicator is coded as 1b. + +## 10.2 ATM data path related primitives + +### 10.2.1 ATM data path related near-end anomalies + +Three near-end anomalies are defined: + +- *No Cell Delineation (ncd-i) anomaly*: An ncd-i anomaly occurs immediately after ATM Cell TC start-up when ATM data are allocated to the data buffer and as long as the cell delineation process operating on this data is in the HUNT or PRESYNC state. Once cell delineation is acquired, subsequent losses of cell delineation shall be considered ocd-i anomalies. +- *Out of Cell Delineation (ocd-i) anomaly*: An ocd-i anomaly occurs when the cell delineation process operating on these data transitions from SYNC to HUNT state. An ocd-i anomaly terminates when the cell delineation process transitions from PRESYNC to SYNC state or when the lcd-i defect maintenance state is entered. +- *Header Error Check (hec-i) anomaly*: An hec-i anomaly occurs when an ATM cell header error check fails on the interleaved data. + +### 10.2.2 ATM data path related far-end anomalies + +Three far-end anomalies are defined: + +- *Far-end No Cell Delineation (fncd-i) anomaly*: An fncd-i anomaly is a ncd-i anomaly detected at the far-end and is reported once per superframe by the ncd-i indicator bit. The ncd-i indicator bit shall be set to 1b to indicate no ncd-i anomaly or ocd-i anomaly or lcd-i defect is present in the previous superframe and shall be set to 0b to indicate that at least one ncd-i anomaly or ocd-i anomaly or lcd-i defect is present in the previous superframe. An fncd-i anomaly occurs immediately after ATU start-up and terminates if a received ncd-i indicator is coded as 1b. +- *Far-end Out of Cell Delineation (focd-i) anomaly*: An focd-i anomaly is an ocd-i anomaly detected at the far-end and is reported once per superframe by the ncd-i indicator. An focd-i anomaly occurs if no fncd-i anomaly is present and a received ncd-i indicator bit is coded as 0b. A focd-i anomaly terminates if a received ncd-i indicator bit is coded set to 1b. +- *Far-end Header Error Check (fhec-i) anomaly*: An fhec-i anomaly is an hec-i anomaly detected at the far-end and is reported once per superframe by the hec-i indicator. The hec-i indicator shall be set to 1b to indicate that no hec-i anomaly is present in the previous superframe and shall be set to 0b to indicate that at least one hec-i anomaly is present in the previous superframe. An fhec-i anomaly occurs when a received hec-i indicator bit is coded as 0b. An fhec-i anomaly terminates when a received hec-i indicator is coded as 1b. + +NOTE – The hec-i anomalies are reported once per superframe. This results in a low granularity of hec anomaly reporting since hundreds of ATM cells may be received over a one superframe time period. + +### 10.2.3 ATM data path related near-end defects + +One near-end defect is defined: + +- *Loss of Cell Delineation (lcd-i) defect:* An lcd-i defect occurs when at least one ocd-i anomaly is present in each of four consecutive superframes and no sef defect is present. An lcd-i defect terminates when no ocd-i anomaly is present in four consecutive superframes. + +### 10.2.4 ATM data path related far-end defects + +One far-end defect is defined: + +- *Far-end Loss of Cell Delineation (flcd-i) defect:* An flcd-i defect is an lcd-i defect detected at the far-end and is reported by the ncd-i indicator bit. An flcd-i defect occurs when an fcod-i anomaly is present and four consecutively received ncd-i indicators are coded 0b and no rdi defect is present. An flcd-i defect terminates if four consecutively received ncd-i indicators are coded as 1b. + +## 10.3 Other ADSL indicators, parameters and signals + +### 10.3.1 Other near-end primitives + +One near-end primitive is defined: + +- *Loss-of-power (lpr):* An lpr primitive occurs when the ATU electrical supply (mains) power drops to a level equal to or below the manufacturer-determined minimum power level required to ensure proper operation of the ATU. An lpr primitive terminates when the power level exceeds the manufacturer-determined minimum power level. + +### 10.3.2 Other far-end primitives + +One far-end primitive is defined: + +- *Far-end Loss-of-power (lpr):* A far-end lpr primitive is an lpr primitive detected at the far-end and is reported by the lpr indicator. The lpr indicator shall be coded with emergency priority in the next six available outgoing eoc messages (see the eoc protocol for "dying gasp"). A far-end lpr primitive occurs when an lpr indicator is received. A far-end lpr primitive terminates if for a period of 0.5 s no lpr indicator is received and no near-end los defect is present. The condition for an lpr indicator being received is defined in the eoc protocol for "dying gasp". + +### 10.3.3 Failure count parameters + +The ATU-C shall provide near-end and far-end failure counters for each near-end and far-end failure defined in Recommendation G.997.1. The ATU-R may optionally provide near-end and far-end failure counters. See Recommendation G.997.1. + +A particular failure count is the number of occurrences of a particular failure event, where a failure event occurs when the failure is declared, and ends when the failure clears. + +## 10.4 Test parameters + +The attenuation (ATN) and signal-to-noise ratio (SNR) margin test parameters apply to on-demand test requests; e.g. to check for adequate physical media performance margin at acceptance and after repair verification, or at any other time following the execution of initialization and training sequence of the ADSL system. ATN and SNR, as measured by the receivers at both the ATU-C and the ATU-R shall be externally accessible from the ATU-C, but they are not required to be continuously monitored. They are made available on demand as defined in 8.3. + +### 10.4.1 Near-end test parameters + +The following near-end test parameters shall be provided at the ATU-C and the ATU-R: + +- **Attenuation (ATN):** The attenuation is the difference in dB between the power received at the near-end and that transmitted from the far-end. Received signal power in dBm is the sum of all data-carrying (i.e. $b_i > 0$ ) DMT subcarrier powers averaged over a 1 s period. Transmitted signal power is $-3.65 - 2n + 10\log(\sum g_i^2)$ dBm, summed over the data-carrying subcarriers. The attenuation ranges from 0 to 63.5 dB with 0.5 dB steps. +- **Signal-to-Noise Ratio (SNR) margin:** The signal-to-noise ratio margin represents the amount of increased received noise (in dB) relative to the noise power that the system is designed to tolerate and still meet the target BER of $10^{-7}$ , accounting for all coding (e.g. trellis coding, RS FEC) gains included in the design. The SNR margin ranges from -64.0 dB to +63.5 dB with 0.5 dB steps. + +### 10.4.2 Far-end test parameters + +The following far-end test parameters shall be provided at the ATU-C: + +- **Far-end Attenuation (ATN):** The far-end attenuation is the attenuation measured at the far-end. It can be read from the EOC ATN register using the EOC command set (see 8.3.5). The EOC ATN register shall be coded as an unsigned integer, ranging from 0 to 127, corresponding to a 0 to 63.5 dB attenuation (0.5 dB steps). +- **Far-end Signal-to-Noise Ratio (SNR) margin:** The far-end signal-to-noise ratio margin is the signal-to-noise ratio margin measured at the far-end. It can be read from the EOC SNR register using the EOC command set (see 8.3.5). The EOC SNR register shall be coded as a twos complement signed integer, ranging from -128 to +127, corresponding to a -64 to +63.5 dB signal-to-noise ratio margin (0.5 dB steps). + +## 10.5 Other failures and parameters + +Other failure, performance monitoring functions, network element configuration, test, diagnostic and status parameters are defined in Recommendation G.997.1. + +# 11 Initialization + +## 11.1 Overview + +### 11.1.1 Basic functions of initialization + +ADSL transceiver initialization is required in order for a physically connected ATU-R and ATU-C pair to establish a communications link. The timeline of Figure 22 provides an overview of the procedure. The first part of initialization is the Handshake procedure which is specified in Recommendation G.994.1. + +![Timeline diagram showing the initialization sequence between ATU-C and ATU-R. The sequence consists of four stages: Handshake (see Rec. G.994.1), Transceiver training, Channel analysis, and Exchange. ATU-C performs Handshake, Transceiver training (see 11.7), Channel analysis (see 11.9), and Exchange (see 11.11). ATU-R performs Handshake (see Rec. G.994.1), Transceiver training (see 11.8), Channel analysis (see 11.10), and Exchange (see 11.12). A time arrow points to the right.](9cd7ec4a653f07d02def283cb6f2309e_img.jpg) + +| | | | | | +|-------|---------------------------------|------------------------------------|---------------------------------|-------------------------| +| ATU-C | Handshake
(see Rec. G.994.1) | Transceiver training
(see 11.7) | Channel analysis
(see 11.9) | Exchange
(see 11.11) | +| ATU-R | Handshake
(see Rec. G.994.1) | Transceiver training
(see 11.8) | Channel analysis
(see 11.10) | Exchange
(see 11.12) | + +time→ + +Timeline diagram showing the initialization sequence between ATU-C and ATU-R. The sequence consists of four stages: Handshake (see Rec. G.994.1), Transceiver training, Channel analysis, and Exchange. ATU-C performs Handshake, Transceiver training (see 11.7), Channel analysis (see 11.9), and Exchange (see 11.11). ATU-R performs Handshake (see Rec. G.994.1), Transceiver training (see 11.8), Channel analysis (see 11.10), and Exchange (see 11.12). A time arrow points to the right. + +Figure 22/G.992.2 – Overview of initialization + +In subsequent parts of the initialization, in order to maximize the throughput and reliability of this link, ADSL transceivers shall determine certain relevant attributes of the connecting channel and establish transmission and processing characteristics suitable to that channel. During initialization each receiver can determine the relevant attributes of the channel through the transceiver training and channel analysis procedures. Certain processing and transmission characteristics can also be established at each receiver during this time. During the exchange process each receiver shares with its corresponding far-end transmitter certain transmission settings that it expects to see. Specifically, each receiver communicates to its far-end transmitter the number of bits and relative power levels to be used on each DMT subcarrier, as well as any messages and final data rates information. For highest performance these settings should be based on the results obtained through the transceiver training and channel analysis procedures. + +Determination of channel attribute values and establishment of transmission characteristics requires that each transceiver produces, and appropriately responds to, a specific set of precisely-timed signals. This subclause describes these initialization signals, along with the rules that determine the proper starting and ending time for each signal. This description is made through the definition of initialization signalling states in which each transceiver will reside, and the definition of initialization signals that each transceiver will generate. A state and the signal generated while in that state have the same name, which may sometimes, for clarity, be prefixed by "state" or "signal". + +The sequence of generated downstream and upstream states/signals for a successful initialization procedure is shown by the time-lines of Figures 24 to 26. Details of the timing of the states are shown in Figure 27. The dashed arrows indicate that the change of state in the ATU at the head of the arrow is caused by a successful reception of the last signal shown in the box at the base of the arrow. For example, in Figure 25, the ATU-R stays in state R-REVERB3 until it finishes receiving C-CRC2, at which point it moves on to R-SEGUE2 after an appropriate delay (see 11.10.2). + +NOTE – The figures show the sequence of events in a successful initialization. + +The description of a signal will consist of three parts: + +- 1) The first part is a description of the voltage waveform that the transmitter shall produce at its output when in the corresponding state. The output voltage waveform of a given initialization signal is described using the DMT transmitter reference model shown in Figure 2. +- 2) The second is a statement of the required duration, expressed in DMT symbol periods, of the signal. This signal duration may be a constant or may depend upon the detected signalling state of the far-end transceiver. The duration of a single DMT symbol period depends on whether the cyclic prefix is being used; some initialization signals contain a cyclic prefix, and some do not. ATU-C signals up to and including C-SEGUE1 are transmitted without a cyclic prefix; those from C-RATES1 on are transmitted with a prefix. Similarly, ATU-R signals up to and including R-SEGUE1 do not use a prefix; those from R-REVERB3 onward do. The duration of any signal in seconds is therefore the defined number of DMT symbol periods times the duration of the DMT symbol being used. +- 3) The third part of a signal's description is a statement of the rule specifying the next state. + +### **11.1.2 Transparency to methods of separating upstream and downstream signals** + +Manufacturers may choose to implement this Recommendation using either non-overlapped spectrum mode (Annex A), or overlapped spectrum mode (Annex B). The initialization procedure described here ensures compatibility between these different implementations by specifying all upstream and downstream control signals to be in the appropriate, but narrower, frequency bands that would be used by an non-overlapped transceiver, and by defining a time period during which an overlapped spectrum transceiver can train its echo canceller. + +### 11.1.3 Initialization Reset Procedure + +If errors or malfunctions are detected or timeout limits are exceeded at various points in the initialization sequence, an Initialization Reset Procedure shall be executed. An ATU executes an Initialization Reset Procedure by transitioning to Recommendation G.994.1. An ATU-R invoking the Initialization Reset Procedure shall transition to R-SILENT0. An ATU-C invoking the Initialization Reset Procedure shall transition to C-SILENT1. + +If errors occur during SHOWTIME, an Initialization Reset Procedure may also be invoked. + +## 11.2 Handshake – ATU-C + +The detailed procedures for handshake at the ATU-C are defined in Recommendation G.994.1. An ATU-C, after power-up, loss of signal, recovery from errors during the initialization procedure, Fast Retrain request abort, Fast Retrain truncate, Fast Retrain unknown profile, events that trigger power management transitions requiring the initialization procedure or optional self test, shall enter the initial G.994.1 state C-SILENT1. The ATU-C may transition to the Initialization Reset Procedure under instruction from the network. From either state, operation shall proceed according to the procedures defined in Recommendation G.994.1. + +If the G.994.1 procedures select this Recommendation as the mode of operation, the ATU-C shall transition to state C-QUIET2 at the conclusion of G.994.1 operation. + +If the G.994.1 procedures select "Escape to Fast Retrain" as the mode of operation, the ATU-C shall transition to state C-QUIET-EF1 at the conclusion of G.994.1 operation. + +An ATU-C wishing to indicate G.992.2 capabilities during in a G.994.1 CL message shall do so by setting to 1b at least one of the Level 1 {SPar(1)} G.992.2 bits as defined in Table 11/G.994.1. For each Level 1 {SPar(1)} bit for G.992.2 set to 1b, a corresponding {NPar(2)} field shall also be present. The {NPar(2)} field corresponding to the "G.992.2 – A/B" Level 1 bit is defined in Table 11-g/G.994.1. The {NPar(2)} field corresponding to the "G.992.2 – Annex C" Level 1 bit is defined in Table 11-i/G.994.1. The Level 2 bits have the following definitions in a CL message: + +| | | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R-ACK1 | Always set to 1 b in a CL message. Signifies that the ATU-C is capable of sending C-PILOT1A, C-QUIET3A, C-PILOT2 and C-QUIET5 during transceiver training. | +| R-ACK2 | Always set to 1 b in a CL message. Signifies that the ATU-C is capable of sending C-PILOT1, C-PILOT2 and C-PILOT3 during transceiver training. | +| RS16 | Set to 1 b if the ATU-C transmitter and receiver have the capability to use Reed-Solomon parameters R = 16 and S = 16. | +| Fast Retrain | Always set to 1 b in a CL message. | +| EOC Clear OAM | If set to 1 b , signifies that the ATU-C supports transmission and reception of G.997.1 OAM frames. | +| DBM | If set to 0 b , this bit shall indicate Bitmap-NR and Bitmap-NC are enabled (Dual Bitmap mode) and are used to transmit data. If set to 1 b , this bit shall indicate Bitmap-NR and Bitmap-NC are disabled (FEXT Bitmap mode), i.e. only Bitmap-FR and Bitmap-FC are used to transmit data by ATU-C and ATU-R respectively. This mode selection shall be only performed by the ATU-C. If it is set to 1 b in a CL message, it must be set to 1 b in subsequent MS messages from either the ATU-C or ATU-R. | + +An ATU-C selecting a G.992.2 mode of operation in a G.994.1 MS message shall do so by setting to 1b the appropriate of the Level 1 {SPar(1)} G.992.2 bit as defined in Table 11/G.994.1. For each level 1 {SPar(1)} bit for G.992.2 set to 1b, a corresponding {Npar(2)} field shall also be present. The {NPar(2)} field corresponding to this bit, as defined in Table 11-h/G.994.1 or Table 11-i/G.994.1, shall also be present in the message. The Level 2 bits have the following definitions in an MS message from the ATU-C: + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| R-ACK1 | Signifies that the ATU-C shall send C-PILOT1A, C-QUIET3A, C-PILOT2 and C-QUIET5 during transceiver training. | +| R-ACK2 | Signifies that the ATU-C shall send C-PILOT1, C-PILOT2 and C-PILOT3 during transceiver training. | +| RS16 | Set to 1 b if and only if RS16 was set to 1 b in both the last previous CL message and the last previous CLR message. It signifies the capability to use Reed-Solomon parameters R = 16 and S = 16 is available in both the upstream and downstream direction. | +| Fast Retrain | Signifies that the ATU-C requires the ATU-R to start an escape to Fast Retrain procedure. | +| EOC Clear OAM | Set to 1 b , if and only this bit was set to 1 b in both the last previous CL message and the last previous CLR message. Signifies that both ATU-C and ATU-R may transmit and receive G.997.1 OAM frames. | +| DBM | If set to 0 b , this bit shall indicate Bitmap-NR and Bitmap-NC are enabled (Dual Bitmap mode) and are used to transmit data. If set to 1 b , this bit shall indicate Bitmap-NR and Bitmap-NC are disabled (FEXT Bitmap mode), i.e. only Bitmap-FR and Bitmap-FC are used to transmit data by ATU-C and ATU-R respectively. This mode selection shall be only performed by ATU-C. This bit shall be set to 1 b E if it was set to 1 b in a previous CL message. | + +One and only one of the bits R-ACK1 and R-ACK2 shall be set to 1b in an MS message sent from the ATU-C. If both bits are enabled in the CL and CLR message, the R-ACK1 or R-ACK2 selection is at the ATU-C's discretion. + +### 11.3 Handshake – ATU-R + +The detailed procedures for handshake at the ATU-R are defined in Recommendation G.994.1. An ATU-R, after power-up, loss of signal, errors during the initialization procedure, fast retrain request abort, fast retrain truncate, fast retrain unknown profile, events that trigger power management transitions requiring the initialization procedure, or optional self test, shall enter the initial G.994.1 state R-SILENT0. Upon command from the host controller, the ATU-R shall initiate handshaking by invoking the Initialization Reset Procedure. Operation shall then proceed according to the procedures defined in Recommendation G.994.1. + +If the G.994.1 procedures select this Recommendation as the mode of operation, the ATU-R shall transition to state R-QUIET2 at the conclusion of G.994.1 operation. + +If the G.994.1 procedures select "Escape to Fast Retrain" as the mode of operation, the ATU-R shall transition to state R-QUIET-EF1 at the conclusion of G.994.1 operation. + +An ATU-R wishing to indicate G.992.2 capabilities in a G.994.1 CLR message shall do so by setting to 1b at least one of the Level 1 {SPar(1)} G.992.2 bits as defined in Table 11/G.994.1. For each Level 1 {SPar(1)} bit for G.992.2 set to ONE, a corresponding {NPar(2)} field shall also be present. The {NPar(2)} field corresponding to the "G.992.2 – A/B" Level 1 bit is defined in Table 11-g/G.994.1. The {NPar(2)} field corresponding to the "G.992.2 – Annex C" Level 1 bit is defined in Table 11-i/G.994.1. The Level 2 bits have the following definitions in a CLR message: + +R-ACK1 Signifies that the ATU-R is capable of interworking with ATU-Cs which send C-PILOT1A, C-QUIET3A, C-PILOT2, and C-QUIET5 during transceiver training (see 11.7.3, 11.7.4, 11.7.6 and 11.7.9). + +R-ACK2 Signifies that the ATU-R is capable of interworking with ATU-Cs which send C-PILOT1, C-PILOT2, and C-PILOT3 during transceiver training (see 11.7.2, 11.7.6 and 11.7.10). + +RS16 Set to 1b if the ATU-R transmitter and receiver has the capability to use Reed-Solomon parameters R = 16 and S = 16. + +Fast Retrain Always set to 1b in a CLR message. + +EOC Clear OAM If set to 1b, signifies that the ATU-R support transmission and reception of G.997.1 OAM frames. + +DBM This bit shall echo the setting of the CL message, or this bit shall be ignored. + +Either R-ACK2, R-ACK1, or both shall be set to 1b in a CLR message. + +An ATU-R selecting a G.992.2 mode of operation in a G.994.1 MS message shall do so by setting to 1b the appropriate of the Level 1 {SPar(1)} G.992.2 bit as defined in Table 11/G.994.1. For each Level 1 {SPar(1)} bit for G.992.2 set to 1b, a corresponding {NPar(2)} field shall also be present. The {NPar(2)} field corresponding to this bit, as defined in Table 11-g/G.994.1 or Table 11-i/G.994.1, shall also be present in the message. The Level 2 bits have the following definitions in an MS message from the ATU-R: + +R-ACK1 Signifies that the ATU-R requires the ATU-C to send C-PILOT1A, C-QUIET3A, C-PILOT2, and C-QUIET5 during transceiver training (see 11.7.3, 11.7.1, 11.7.6 and 11.7.9) + +R-ACK2 Signifies that the ATU-R requires the ATU-C to send C-PILOT1, C-PILOT2, and C-PILOT3 during transceiver training (see 11.7.2, 11.7.6 and 11.7.10). + +RS16 Set to 1b if and only if RS16 was set to 1b in both the last previous CL message and the last previous CLR message. It signifies that the capability to use Reed-Solomon parameters R = 16 and S = 16 is available in both the upstream and downstream directions. + +Fast Retrain Signifies that the ATU-R requires the ATU-C to start an escape to fast retrain. + +EOC Clear OAM Set 1b if and only if this bit was set to 1b in both the last previous CL message and the last previous CLR message. Signifies that both the ATU-C and ATU-R may transmit and receive G.997.1. OAM frames. + +DBM If set to 0b, this bit shall indicate that Bitmap-NR and Bitmap-NC are enabled (Dual Bitmap mode) and are used to transmit data. If set to 1b, this bit shall indicate that Bitmap-NR and Bitmap-NC are disabled (FEXT Bitmap mode), i.e. only Bitmap-FR and Bitmap-FC are used to transmit data by ATU-C and ATU-R respectively. This mode selection shall be only performed by ATU-C. This bit shall be set to 1b if it was set to 1b in a previous CL message. + +One and only one of the bits R-ACK1 or R-ACK2 shall be set to 1b in an MS message sent from the ATU-R. If both bits are enabled in the CL and CLR message, the R-ACK1 or R-ACK2 selection is at the ATU-R's discretion. + +#### 11.4 Handshake power levels + +When Recommendation G.994.1 (Handshake) is invoked outside of a G.992.2 session or in order to change modes of operation, the PSD levels at the ATU-R and ATU-C shall be as specified in Recommendation G.994.1. When Handshake is invoked from the procedures described in this Recommendation, the power levels shall be as specified in Table 24. + +**Table 24/G.992.2 – Handshake power levels** + +| Prior G.992.2 state | ATU-C power level (dBm/Hz) | ATU-R power level (dBm/Hz) | +|----------------------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------| +| Fast Retrain Request Abort | Nominal | Nominal | +| Fast Retrain Truncate | – 40 – Absolute Downstream Fast Retrain Power Cutback | – 38 – Absolute Upstream Fast Retrain Power Cutback | +| Fast Retrain Unknown Profile | – 40 – Absolute Downstream Fast Retrain Power Cutback | – 38 – Absolute Upstream Fast Retrain Power Cutback | +| Initialization Reset Procedure from errors, malfunctions or timeouts | Nominal | Nominal | +| L3 to L0 Power Management Transition T3a | Nominal | Nominal | +| L0 to L0 Power Management Transition T0a or t0c | Nominal | Nominal | +| L1 to L0 Power Management Transition T1a or T1c | Nominal | Nominal | + +#### 11.5 Escape from Handshake to Fast Retrain + +If the escape to Fast Retrain mode is selected during the G.994.1 procedure, the ATUs shall perform a Fast Retrain instead of entering the Transceiver Training phase. + +It is recommended that, in cases other than when the Handshake procedure has been initiated from a Fast Retrain Truncate or Fast Retrain Unknown Profile, the Handshake procedure request an escape to Fast Retrain (see Figure 23). + +![Timing diagram of escape to Fast Retrain showing signal sequences for ATU-C and ATU-R. ATU-C sequence: G.994.1, C-QUIET-EF1 (duration ≥ 128, ≤ 2048), C-RECOV, C-REVERB-FR1 (duration ≤ C-TO2), C-PILOT-FR1. ATU-R sequence: G.994.1, R-QUIET-EF1 (duration ≤ 8000), R-RECOV (duration ≤ R-T1, ≥ 128), R-REVERB-FR1. Arrows indicate timing relationships: R-T1 from R-RECOV start to C-RECOV start; C-TO1 from C-RECOV start to start of grey block; C-TO2 from C-RECOV start to start of grey block. Grey blocks indicate periods of inactivity or specific timing constraints. Vertical ellipses indicate additional signals. Reference T1533500-99 is noted.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +Timing diagram of escape to Fast Retrain showing signal sequences for ATU-C and ATU-R. ATU-C sequence: G.994.1, C-QUIET-EF1 (duration ≥ 128, ≤ 2048), C-RECOV, C-REVERB-FR1 (duration ≤ C-TO2), C-PILOT-FR1. ATU-R sequence: G.994.1, R-QUIET-EF1 (duration ≤ 8000), R-RECOV (duration ≤ R-T1, ≥ 128), R-REVERB-FR1. Arrows indicate timing relationships: R-T1 from R-RECOV start to C-RECOV start; C-TO1 from C-RECOV start to start of grey block; C-TO2 from C-RECOV start to start of grey block. Grey blocks indicate periods of inactivity or specific timing constraints. Vertical ellipses indicate additional signals. Reference T1533500-99 is noted. + +Figure 23/G.992.2 – Timing diagram of escape to Fast Retrain + +### 11.5.1 C-QUIET-EF1 + +C-QUIET-EF1 begins at the termination of Recommendation G.994.1. The minimum duration of C-QUIET-EF1 is 128 symbols. The maximum duration of C-QUIET-EF1 is 2048 symbols. + +### 11.5.2 R-QUIET-EF1 + +R-QUIET-EF1 begins at the termination of Recommendation G.994.1. The minimum duration of R-QUIET-EF1 is 128 DMT symbols after the detection of C-RECOV. The ATU-R shall progress to R-RECOV only after it has detected any part of the C-RECOV signal that is needed for reliable detection. The maximum duration of R-QUIET-EF1 is 8000 symbols. + +## 11.6 Power levels in Transceiver Training, Channel Analysis and Exchange + +All ATU-R signals defined in Transceiver Training, Channel Analysis and Exchange except R-ECT, shall be transmitted using the PSD level of the previous G.994.1 session with one exception: if Recommendation G.994.1 was invoked outside of a G.992.2 session or in order to change modes of operation, all ATU-R signals defined in Transceiver Training, Channel Analysis and Exchange except R-ECT shall be transmitted at Nominal PSD level. + +C-PILOT1 and C-PILOT1A shall be transmitted using the PSD level of the previous G.994.1 session with one exception: if G.994.1 was invoked outside of a Recommendation G.992.2 session or in order to change modes of operation C-PILOT1 and C-PILOT1A shall be transmitted at Nominal PSD level. C-REVERB1 and subsequent ATU-C signals defined Transceiver Training, Channel Analysis and Exchange, unless otherwise noted, shall be transmitted at the PSD level calculated as defined in 11.7.5. + +C/R-QUIET signals are defined as zero output voltage from the DAC of Figure 2. + +Because C-ECT and R-ECT are vendor-defined signals, the above PSD specification shall only be interpreted as a maximum. + +## 11.7 Transceiver training – ATU-C + +This subclause and subclause 11.8 describe the signals transmitted during transceiver training by the ATU-C and ATU-R, respectively (see Figure 24). Synchronization of the mutual training begins with the transmission of R-REVERB1 (see 11.8.2) and is maintained throughout training by both transceivers counting the number of symbols from that point on. + +ATU-C + +![Timing diagram showing state transitions for ATU-C and ATU-R. ATU-C states: C-QUIET2, C-PILOT1/C-PILOT1A and C-QUIET3A, C-REVERB1, C-PILOT2, C-ECT, C-REVERB2, C-QUIET5/C-PILOT3, C-REVERB3. ATU-R states: R-QUIET2, R-REVERB1, R-QUIET3, R-ECT, R-REVERB2. Arrows indicate synchronization from ATU-R to ATU-C.](b5b908b453ca50ed3b4cca88aef080fa_img.jpg) + +| | | | | | | | | +|----------|-------------------------------|-----------|----------|-------|-----------|----------|-----------| +| C-QUIET2 | C-PILOT1 | C-REVERB1 | C-PILOT2 | C-ECT | C-REVERB2 | C-QUIET5 | C-REVERB3 | +| | C-PILOT1A
and
C-QUIET3A | | | | | C-PILOT3 | | + +ATU-R + +| | | | | | +|----------|-----------|----------|-------|-----------| +| R-QUIET2 | R-REVERB1 | R-QUIET3 | R-ECT | R-REVERB2 | +|----------|-----------|----------|-------|-----------| + +Time → + +(See Note) + +T1533510-99 + +Timing diagram showing state transitions for ATU-C and ATU-R. ATU-C states: C-QUIET2, C-PILOT1/C-PILOT1A and C-QUIET3A, C-REVERB1, C-PILOT2, C-ECT, C-REVERB2, C-QUIET5/C-PILOT3, C-REVERB3. ATU-R states: R-QUIET2, R-REVERB1, R-QUIET3, R-ECT, R-REVERB2. Arrows indicate synchronization from ATU-R to ATU-C. + +NOTE – Because the ATU-C and ATU-R states are synchronized from this point on, no more "cause-and-effect" arrows are shown. + +**Figure 24/G.992.2 – Timing diagram of transceiver training (see 11.7-11.8)** + +### 11.7.1 C-QUIET2 + +C-QUIET2 begins after termination of Recommendation G.994.1. The minimum duration of C-QUIET2 is 128 symbols. The maximum duration of C-QUIET2 is 2048 symbols. + +The state that the ATU-C enters following C-QUIET2 depends upon parameters negotiated in the G.994.1 procedure. + +### 11.7.2 C-PILOT1 + +During C-PILOT1 or C-PILOT1A as appropriate, the ATU-C shall measure the aggregate received upstream power on subcarriers 7-18 of R-REVERB1, and thereby calculate a downstream PSD. + +Within 16 symbols after detection of the first symbol of R-REVERB1 the ATU-C shall start a timer. This establishes synchronization of the subsequent transitions between states at ATU-C and ATU-R. After 512 symbols, as measured by this timer, the ATU-C shall go to C-REVERB1. Thus the minimum duration of C-PILOT1 is 512 symbols, but it will exceed this by the round-trip propagation and signal-processing time plus the amount of time required by ATU-R to detect C-PILOT1 and respond by transmitting R-REVERB1 (see 11.8.2). + +C-REVERB1 follows C-PILOT1. + +C-PILOT1 is a single frequency sinusoid at 276 kHz defined as: + +$$X_k = \begin{cases} 0 & \text{for } k \neq 64, 0 \leq k \leq 127 \\ A_{C-PILOT1} & \text{for } k = 64 \end{cases}$$ + +$A_{C-PILOT1}$ shall be such that PSD level is as defined in 11.6. The duration of C-PILOT1 can be up to 4436 symbols + +C-REVERB1 follows C-PILOT1. + +### 11.7.3 C-PILOT1A + +C-PILOT1A is the same transmitted signal as C-PILOT1. The duration of C-PILOT1A can be up to 4000 symbols. The exact duration of C-PILOT1A depends upon the duration of R-QUIET2. + +Within 16 symbols after detection of the first symbol of R-REVERB1 the ATU-C shall start a timer (this establishes synchronization of the subsequent transitions between states at the ATU-C and ATU-R) and shall proceed to C-QUIET3A. + +C-QUIET3A follows C-PILOT1A. + +#### 11.7.4 C-QUIET3A + +Within 512 to 516 symbols after detection of the first symbol of R-REVERB1, the ATU-C shall go to C-REVERB1. Thus, the minimum duration of C-QUIET3A is 512-16 (496) symbols; the maximum is 516 symbols. The total duration of C-QUIET3A and C-PILOT1A is a minimum of 512 symbols, but it will exceed this (up to a maximum duration of 4436 symbols) by the round-trip propagation and signal processing time plus the amount of time required by ATU-R to detect C-PILOT1A and respond by transmitting R-REVERB1. + +C-REVERB1 follows C-QUIET3A. + +#### 11.7.5 C-REVERB1 + +C-REVERB1 is a signal that allows the ATU-C and ATU-R receiver to adjust its automatic gain control (AGC) to an appropriate level. + +The C-REVERB1 signal shall modulate a contiguous range of subcarriers from $n$ to $m$ , where $n \leq 37$ and $m \geq 68$ . Subsequent C-REVERB and C-SEGUE signals shall use the same range of subcarriers as C-REVERB1. The value of $n$ and $m$ are CO vendor discretionary. All ATU-R receivers, during Initialization, shall tolerate the maximum number of subcarriers allowed by the overlapped spectrum mask defined in Annex B. + +The data pattern used in C-REVERB1 shall be the pseudo-random downstream sequence DPRD, $d_n$ for $n = 1$ to $2 \times N_{SC-DN}$ and encoding method defined in 7.10.3. + +The bits shall be used as follows: The first pair of bits ( $d_1$ and $d_2$ ) are used for the dc and Nyquist subcarriers (the power assigned to them is, of course, zero, so the bits are effectively ignored); then the first and second bits of subsequent pairs are used to define the $X_i$ and $Y_i$ for $i = 1$ to $N_{SC-DN} - 1$ as defined in Table 9. + +The period of PRD is 511 bits. The bits $d_1$ to $d_9$ shall be re-initialized for each symbol, so each symbol of C-REVERB1 is identical. Bits 129 and 130, which modulate the pilot carrier, shall be overwritten by {0,0} generating the {+,+} constellation. + +The transmit PSD for C-REVERB1 shall be the Reference PSD level of $(-40 - 2n)$ dBm/Hz, with $2n =$ the maximum of either the Absolute Downstream Fast Retrain Power Cutback or the Initialization Politeness Power Cutback. The Initialization Politeness Power Cutback is obtained using Table 25, based on the average upstream loop attenuation measured during R-REVERB1. This reference PSD level shall become the reference level for all subsequent gain calculations. The average upstream loop attenuation is defined as the difference between the upstream reference power in dBm and the total upstream power measured on subcarriers 7 through 18 during R-REVERB1. The upstream reference power is defined as the total transmit power on subcarriers 7 through 18, using the R-REVERB1 reference transmit PSD level. + +**Table 25/G.992.2 – Initialization Politeness Power Cutback: Downstream PSD as a function of average upstream loop attenuation** + +| | | | | | | | | +|----------------------------------------------|----|----|----|----|----|----|----| +| Average upstream loop attenuation (dB) | >6 | >5 | >4 | >3 | >2 | >1 | >0 | +| Initialization Politeness Power Cutback (dB) | 0 | 2 | 4 | 6 | 8 | 10 | 12 | + +The duration of C-REVERB1 is 512 (repeating) symbols without cyclic prefix. C-PILOT2 follows C-REVERB1. + +The C-REVERB1 signal should be sufficiently wideband in order to probe the transmission channel in such a way that the C-REVERB1 signal does not sufficiently lengthen the estimated channel impulse response as measured using C-REVERB1. + +#### **11.7.6 C-PILOT2** + +The C-PILOT2 signal is the same as C-PILOT1; the duration is 3072 symbols. C-ECT follows C-PILOT2. + +#### **11.7.7 C-ECT** + +C-ECT is a vendor-defined signal that is used to train the echo canceller at ATU-C for EC implementations. Vendors of FDM and EC versions have complete freedom to define their C-ECT signal given the power constraints defined in Annexes A and B. The duration of C-ECT, however, is fixed at 512 symbols. The receiver at ATU-R should ignore this signal. C-REVERB2 follows C-ECT. + +#### **11.7.8 C-REVERB2** + +C-REVERB2 is a signal that allows the ATU-R receiver to perform synchronization and to train any receiver equalizer. C-REVERB2 is the same as C-REVERB1 (see 11.7.5). The duration of C-REVERB2 is 1536 (repeating) symbols without cyclic prefix. The state following C-REVERB2 depends upon negotiated parameters in the G.994.1 procedure. + +#### **11.7.9 C-QUIET5** + +The duration of C-QUIET5 is 512 symbols. C-REVERB3 follows C-QUIET5. + +#### **11.7.10 C-PILOT3** + +C-PILOT3 signal is the same as C-PILOT1 (see 11.7.2). The duration of C-PILOT3 is 512 symbols. C-REVERB3 follows C-PILOT3. + +#### **11.7.11 C-REVERB3** + +C-REVERB3 is a second training signal, which allows the ATU-R receiver to perform or maintain synchronization and to further train any receiver equalizer. C-REVERB3 is the same as C-REVERB2 (see 11.7.8). The duration of C-REVERB3 is 1024 (repeating) symbols without cyclic prefix. This is the last segment of transceiver training. C-SEGUE1 follows immediately. + +### **11.8 Transceiver training – ATU-R** + +#### **11.8.1 R-QUIET2** + +R-QUIET2 begins after termination of Recommendation G.994.1. The minimum duration of R-QUIET2 is 128 DMT symbols after the detection of C-PILOT1/1A. The ATU-R shall progress to R-REVERB1 only after it has detected any part of the following C-QUIET3A or C-PILOT1/1A that is needed for reliable detection. The maximum duration of R-QUIET2 is 8000 symbols. + +Loop timing is defined as the combination of the slaving of an ADC clock to the received signal (i.e. to the other transceiver's DAC clock), and tying the local DAC and ADC clocks together. Loop timing shall always be performed at the ATU-R and be acquired while transmitting R-QUIET2 and before the last 512 symbols of R-REVERB1. An ATU-C may train its equalizer during the last 512 symbols of R-REVERB1. Such equalizer training, at the ATU-C, requires sufficient sampling clock stability at the ATU-R transmitter. After loop timing is acquired at the ATU-R, the ATU-R shall re-acquire loop timing after a period with free running timing (i.e. no C-PILOT over maximum + +512 symbols) within 512 symbols after the C-PILOT re-appearing. This applies to C-QUIET5 and may also apply to C-QUIET3A and C-ECT. + +NOTE – The delay in the ATU-R in going from C-QUIET2 to R-REVERB1 is to allow the possibility that the ATU-R may fully synchronize its time base before sending R-REVERB1. + +### **11.8.2 R-REVERB1** + +R-REVERB1 is used to allow the ATU-C to: + +- 1) measure the upstream wideband power in order to adjust the ATU-C transmit power level; +- 2) adjust its receiver gain control; +- 3) synchronize its receiver and train its equalizer. + +The data pattern used in R-REVERB1 is UPRD defined in 7.10.4. + +R-REVERB1 is a periodic signal, without cyclic prefix, that is transmitted consecutively for 4096 symbols. The first 512 symbols coincide with C-QUIET3A or C-PILOT1 signal in time, the second 512 symbols coincide with C-REVERB1, and the last 3072 symbols coincide with C-PILOT2. R-QUIET3 immediately follows R-REVERB1. + +### **11.8.3 R-QUIET3** + +The duration of R-QUIET3 is 2048 symbols, of which the first 512 symbols coincide with C-ECT in time, and the next 1536 symbols coincide with C-REVERB2. The final symbol of R-QUIET3 may be shortened by any number of samples to accommodate transmitter to receiver frame alignment. R-ECT immediately follows R-QUIET3. + +### **11.8.4 R-ECT** + +R-ECT, similar to C-ECT, is a vendor-defined signal that may be used to train an echo canceller at the ATU-R. Vendors of FDM and EC versions have absolute freedom to define R-ECT signal given the power constraints defined in Annexes A and B. The duration of R-ECT is however, fixed at 512 DMT symbols. The receiver at the ATU-C ignores this signal. R-REVERB2 follows R-ECT. + +### **11.8.5 R-REVERB2** + +The signal R-REVERB2 is the same as R-REVERB1 (see 11.8.2); it can be used by ATU-C to perform timing recovery and receiver equalizer training. The duration of R-REVERB2 shall be between 1024 and 1056 symbols. This signal is the last segment of transceiver training. ATU-R then begins channel analysis and starts transmitting R-SEGUE1. + +## 11.9 Channel analysis (ATU-C) + +See Figure 25. + +![Timing diagram of channel analysis showing ATU-C and ATU-R signal sequences over time. ATU-C sequence: C-SEGUE1, C-RATES1, C-CRC1, C-MSGS1 AND C-CRC2, C-MEDLEY, C-REVERB4. ATU-R sequence: R-SEGUE1, R-REVERB3, R-SEGUE2, R-RATES1, R-CRC1, R-MSGS1 and R-CRC2, R-MEDLEY, R-REVERB4. A downward arrow indicates the transition from ATU-C to ATU-R. A horizontal arrow at the bottom indicates the direction of time.](7f7211748473542096717109ebe5a9d6_img.jpg) + +``` + +ATU-C ++-----------+-------------------+-----------------------+-------------+ +| C-SEGUE1 | C-RATES1, C-CRC1, | C-MEDLEY | C-REVERB4 | +| | C-MSGS1 AND C-CRC2| | | ++-----------+-------------------+-----------+-----------+-------------+ + | + v +ATU-R ++---------+-----------+---------+-------------------+-----------+-------------+ +| R-SEGUE1| R-REVERB3 | R-SEGUE2| R-RATES1, R-CRC1, | R-MEDLEY | R-REVERB4 | +| | | | R-MSGS1 and R-CRC2| | | ++---------+-----------+---------+-------------------+-----------+-------------+ + Time → + +``` + +Timing diagram of channel analysis showing ATU-C and ATU-R signal sequences over time. ATU-C sequence: C-SEGUE1, C-RATES1, C-CRC1, C-MSGS1 AND C-CRC2, C-MEDLEY, C-REVERB4. ATU-R sequence: R-SEGUE1, R-REVERB3, R-SEGUE2, R-RATES1, R-CRC1, R-MSGS1 and R-CRC2, R-MEDLEY, R-REVERB4. A downward arrow indicates the transition from ATU-C to ATU-R. A horizontal arrow at the bottom indicates the direction of time. + +Figure 25/G.992.2 – Timing diagram of channel analysis (see 11.7-11.8) + +During channel analysis the synchronization between ATU-C and ATU-R may be broken during R-REVERB3, which has an indefinite duration; this potential timeout is described in 11.10.2. Furthermore, if during channel analysis any crc check sum indicates an error in any of the control data, this shall invoke the Initialization Reset Procedure. + +### 11.9.1 C-SEGUE1 + +Except for the pilot tone, C-SEGUE1 shall be generated from a tone-by-tone 180-degree phase reversal of C-REVERB1 (i.e. + maps to –, and – maps to +, for each of the 4-QAM signal constellation). The duration of C-SEGUE1 is ten (repeating) symbol periods. Following C-SEGUE1, ATU-C enters state C-RATES1. + +### 11.9.2 C-RATES1 + +C-RATES1 is the first ATU-C signal for which a cyclic prefix (defined in 7.11) is used. The purpose of C-RATES1 is to transmit four options for data rates and formats to the ATU-R. Each option consists of three fields: + +- The $B_F$ field is not applicable to this Recommendation. $B_F$ contains a total of 80 bits organized as 10 entries each of eight bits. All bits shall be set to $0_b$ . +- The $B_I$ field contains the number of bytes in a DF allocated to the AS0 (downstream) and LS0 (upstream) channel. $B_I$ contains a total of 80 bits organized as 10 entries each of eight bits. The first entry in $B_I$ contains the number of bytes in a DF allocated to AS0. The eighth entry in $B_I$ contains the number of bytes in a DF allocated to LS0. All other bits in $B_I$ shall be set to $0_b$ . +- The RRSI field contains Reed-Solomon FEC and interleaver parameters. The RRSI field contains a total of 80 bits organized as 10 entries each of eight bits. The second entry in the RRSI field contains the parameter $RS_I$ : The number of parity bytes per symbol in the downstream transmission direction with $RS_I$ equal to R/S. The third entry in the RRSI field contains the parameter $S$ : $S$ is the number of DFs per Reed-Solomon codeword in the downstream transmission direction. The fourth entry contains the parameter $I$ : The downstream interleave depth in codewords. The seventh entry in the RRSI field contains the + +parameter $RS_I$ : The number of parity bytes per symbol in the upstream transmission direction with $RS_I$ equal to $R/S$ . The eighth entry in the RRSI field contains the parameter $S$ ; $S$ is the number of DFs per Reed-Solomon codeword in the upstream transmission direction. The ninth entry contains the parameter $I$ : The upstream interleave depth in codewords. All other bits in RRSI shall be set to $0_b$ . + +The four options are transmitted in order of decreasing preference. C-RATES1 is preceded by a 4-byte prefix of $\{55\ 55\ 55\ 55_{16}\}$ . Table 26 summarizes C-RATES1 and Table 27 summarizes RRSI fields of C-RATES1. + +**Table 26/G.992.2 – C-RATES1 message** + +| | Prefix | Option 1 | | | Option 2 | | | Option 3 | | | Option 4 | | | +|-----------------|--------|----------|-------|------|----------|-------|------|----------|-------|------|----------|-------|------| +| | | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | +| Number of bytes | 4 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | + +**Table 27/G.992.2 – RRSI fields of C-RATES1** + +| Entry # | Field | | bits | | | | | | | | +|---------|-----------|------------|---------------------------------------------------------|-------|------------------------------------------|-------|-------|-------|-------|-------| +| | | | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| 1 | $RS_F$ | Downstream | N/A to Recommendation G.992.2 – set to $\{00000000_b\}$ | | | | | | | | +| 2 | $R$ | | $0_b$ | $0_b$ | value of $R$ [MSB $\leftrightarrow$ LSB] | | | | | | +| 3 | $S$ | | $0_b$ | $0_b$ | value of $S$ [MSB $\leftrightarrow$ LSB] | | | | | | +| 4 | $I$ | | $I_7$ | $I_6$ | $I_5$ | $I_4$ | $I_3$ | $I_2$ | $I_1$ | $I_0$ | +| 5 | $FS(LS2)$ | | N/A to Recommendation G.992.2 – set to $\{00000000_b\}$ | | | | | | | | +| 6 | $RS_F$ | Upstream | N/A to Recommendation G.992.2 – set to $\{00000000_b\}$ | | | | | | | | +| 7 | $R$ | | $0_b$ | $0_b$ | value of $R$ [MSB $\leftrightarrow$ LSB] | | | | | | +| 8 | $S$ | | $0_b$ | $0_b$ | value of $S$ [MSB $\leftrightarrow$ LSB] | | | | | | +| 9 | $I$ | | $I_7$ | $I_6$ | $I_5$ | $I_4$ | $I_3$ | $I_2$ | $I_1$ | $I_0$ | +| 10 | $FS(LS2)$ | | N/A to Recommendation G.992.2 – set to $\{00000000_b\}$ | | | | | | | | + +Only one bit of information is transmitted in each symbol of C-RATES1: A zero bit is encoded to one symbol of C-REVERB1 and a one bit is encoded to one symbol of C-SEGUE1. Since there are a total of 992 bits of C-RATES1 information, the duration of C-RATES1 is 992 symbols. The 992 bits are to be transmitted in the order shown in Table 26 with the least significant bit first. That is, the least significant bit of option 1, $B_F$ , is to be transmitted during the 33rd symbol of C-RATES1, after the prefix. Following C-RATES1, the ATU-C shall enter state C-CRC1. + +### 11.9.3 C-CRC1 + +C-CRC1 is a cyclic redundancy check for detection of errors in the reception of C-RATES1 at the ATU-R. The crc bits are computed from the C-RATES1 bits using the equation: + +$$c(D) = a(D) D^{16} \text{ modulo } g(D),$$ + +where: + +$$a(D) = a_0 D^{959} + a_1 D^{958} \dots + a^{959}$$ + +is the message polynomial formed from the 960 bits of C-RATES1, with $a_0$ the least significant bit of the first byte of C-RATES1 (i.e. option 1 $B_F$ ); + +$$g(D) = D^{16} + D^{12} + D^5 + 1$$ + +is the crc generator polynomial, and + +$$c(D) = c_0 D^{15} + c_1 D^{14} \dots + c_{14} D + c_{15}$$ + +is the crc check polynomial. + +The 16 bits $c_0$ - $c_{15}$ are transmitted ( $c_0$ first and $c_{15}$ last) in 16 symbol periods using the method described in 11.9.2. Following C-CRC1, the ATU-C shall enter state C-MSG1. + +### 11.9.4 C-MSG1 + +C-MSG1 transmits a 48-bit message signal to the ATU-R. This message includes ATU-C transmit power level used, echo canceller option, etc. The message, $m$ , is defined by: + +$$m = \{m_{47}, m_{46}, \dots, m_1, m_0\}$$ + +with $m_0$ being transmitted first. The message components are defined in the following subclauses, and their assigned positions within the composite message, $m$ , are defined in Table 28. A total of 48 symbol periods are used to communicate the 48-bit message, using the encoding method described in 11.9.2. Following C-MSG1, the ATU-C shall enter signalling state C-CRC2. + +**Table 28/G.992.2 – Assignment of 48 bits of C-MSG1** + +| Suffix(es) of $m_i$ (Note 1) | Parameter (Note 3) | +|------------------------------|--------------------------------------------------| +| 47-44 | ATU target noise margin (Note 2) | +| 43-17 | Reserved by ITU-T | +| 16 | Echo cancellation option | +| 15 | Unused (shall be set to 1 b ) | +| 14-12 | Reserved by ITU-T | +| 11 | NTR | +| 10, 9 | Framing mode | +| 8-6 | Initialization Politeness Power Cutback | +| 5, 4 | Reserved by ITU-T | +| 3, 2, 1, 0 | Maximum numbers of bits per subcarrier supported | + +NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts. +NOTE 2 – A positive number of dB; binary coded 0-15 dB. +NOTE 3 – All reserved bits shall be set to 0b. + +#### 11.9.4.1 Minimum required SNR margin – Bits 47-44 + +Binary coded 0 to 15 dB. + +#### 11.9.4.2 Echo cancellation option – Bit 16 + +$m_{16} = 0_b$ indicates no echo cancellation, $m_{16} = 1_b$ indicates echo cancellation. + +#### 11.9.4.3 Unused – Bit 15 + +$m_{15}$ shall be set to $1_b$ . + +#### 11.9.4.4 NTR – Bit 11 + +$m_{11} = 1_b$ indicates that the ATU-C will use indicator bits IB23 to IB20 as defined in Table 4 for the transport of the NTR. + +#### 11.9.4.5 Framing mode – Bits 10, 9 + +$m_{10}$ and $m_9$ shall both be set to $1_b$ . + +#### 11.9.4.6 Initialization Politeness Power Cutback – Bits 8, 7, 6 + +The ATU-C shall report the level of Initialization Politeness Power Cutback as a result of the calculation described in 11.7.5. The encoding rules for $m_8, m_7, m_6$ are shown in Table 29. + +**Table 29/G.992.2 – C-MSG1 encoding rules for Initialization Politeness Power Cutback (dB)** + +| $m_8$ | $m_7$ | $m_6$ | Initialization Politeness Power Cutback (dB) | +|-------|-------|-------|----------------------------------------------| +| $1_b$ | $1_b$ | $1_b$ | 0 | +| $1_b$ | $1_b$ | $0_b$ | 2 | +| $1_b$ | $0_b$ | $1_b$ | 4 | +| $1_b$ | $0_b$ | $0_b$ | 6 | +| $0_b$ | $1_b$ | $1_b$ | 8 | +| $0_b$ | $1_b$ | $0_b$ | 10 | +| $0_b$ | $0_b$ | $1_b$ | 12 | + +#### 11.9.4.7 Maximum numbers of bits per subcarrier supported – Bits 3-0 + +The $N_{\text{downmax}}$ (transmit) capability shall be binary encoded onto $\{m_3 \dots m_0\}$ (e.g. $1101_b = 13_{10}$ ). The maximum number of bits for the upstream data, $N_{\text{upmax}}$ , that the ATU-C receiver can support need not be signalled to the ATU-R; it will be implicit in the bits and gains message, C-B&G, which is transmitted after channel analysis. + +### 11.9.5 C-CRC2 + +C-CRC2 is a cyclic redundancy check for detection of errors in the reception of C-MSG1 at the ATU-R. The crc generator polynomial is as defined in 11.9.3. The crc message polynomial is as constructed in 11.9.3, with $m_0$ corresponding to $a_0$ and $m_{47}$ corresponding to $a_{47}$ . The crc check polynomial is generated in the same way as defined in 11.9.3. These 16 bits are transmitted in 16 symbol periods using the method described in 11.9.3. Following C-CRC2, the ATU-C shall enter signalling state C-MEDLEY. + +### 11.9.6 C-MEDLEY + +C-MEDLEY is a wideband pseudo-random signal used for estimation at the ATU-R of the downstream SNR. The data to be transmitted are derived from the pseudo-random sequence, PRD, and modulated as defined in 11.7.5. In contrast to C-REVERB1, however, the cyclic prefix is used and the data sequence continues from one symbol to the next (i.e. $d_1$ to $d_9$ are not re-initialized for each symbol); since PRD is of length 511, and 512 bits are used for each symbol, the subcarrier vector for C-MEDLEY therefore changes from one symbol period to the next. The pilot subcarrier is over-written by the (+,+ ) signal constellation. C-MEDLEY is transmitted for 16 384 symbol periods. Following C-MEDLEY the ATU-C shall enter the state C-REVERB4. + +## 11.10 Channel analysis (ATU-R) + +During channel analysis there are two situations where the ATU-R shall invoke the Initialization Reset Procedure: a timeout and a detected error in the received control data. A timeout occurs if the time in R-REVERB3 exceeds the limit of 4000 symbols. Also, if any C-CRC checksum indicates that there is an error in the received control data, then it shall invoke the Initialization Reset Procedure. + +### 11.10.1 R-SEGUE1 + +R-SEGUE1 is generated from a tone-by-tone 180-degree phase reversal of R-REVERB1 (i.e.+ maps to -, and - maps to +, for each of the 4-QAM signal constellation). The duration of R-SEGUE1 is 10 symbol periods. Following R-SEGUE1 the ATU-R shall enter state R-REVERB3. + +### 11.10.2 R-REVERB3 + +R-REVERB3 is similar to R-REVERB1 (see 11.8.2); the only difference is that R-REVERB3 is the first ATU-R signal with the addition of a cyclic prefix to every symbol (defined in 7.11). The duration of R-REVERB3 is not fixed but has a maximum of 4000 symbols. If C-CRC2 is not detected within 4000 symbols, the ATU-R shall invoke the Initialization Reset Procedure. After detection of C-RATES1-C-CRC2, the ATU-R shall continue to send R-REVERB3 for 20 additional symbols before entering R-SEGUE2. + +### 11.10.3 R-SEGUE2 + +The signal R-SEGUE2 is similar to R-SEGUE1 (see 11.10.1). The only difference is the addition of the cyclic prefix. Following R-SEGUE2 the ATU-R shall enter state R-RATES1. + +### 11.10.4 R-RATES1 + +See Table 30. + +**Table 30/G.992.2 – R-RATES1** + +| | Prefix | Option 1 | | | Option 2 | | | Option 3 | | | Option 4 | | | +|-----------------|--------|----------------|----------------|------|----------------|----------------|------|----------------|----------------|------|----------------|----------------|------| +| | | B F | B I | RRSI | B F | B I | RRSI | B F | B I | RRSI | B F | B I | RRSI | +| Number of bytes | 4 | 3 | 3 | 5 | 3 | 3 | 5 | 3 | 3 | 5 | 3 | 3 | 5 | + +The purpose of R-RATES1 for the upstream channel is the same as that of C-RATES1 for the downstream channel (see 11.9.2). Each option consists of three fields: + +- The BF field is not applicable to this Recommendation. BF contains a total of 24 bits organized as three entries each of eight bits. All bits shall be set to 0b. + +- The $B_I$ field contains the number of bytes in a DF allocated to the LS0 (upstream) channel. $B_I$ contains a total of 24 bits organized as three entries each of eight bits. The first entry in $B_I$ contains the number of bytes in a DF allocated to LS0. All other bits in $B_I$ shall be set to $0_b$ . +- The RRSI field contains Reed-Solomon FEC and interleaver parameters. The RRSI field contains a total of 40 bits organized as five entries each of eight bits (see Table 31). The second entry in the RRSI field contains the parameter $RS_I$ : The number of parity bytes per symbol in the upstream transmission direction with $RS_I$ equal to $R/S$ . The third entry in the RRSI field contains the parameter $S$ ; $S$ is the number of DFs per Reed-Solomon codeword in the upstream transmission direction. The fourth entry contains the parameter $I$ : The eight least significant bits of the upstream interleave depth in codewords. All other bits in RRSI shall be set to $0_b$ . + +**Table 31/G.992.2 – RRSI fields of R-RATES1** + +| Entry # | Field | ← bits → | | | | | | | | +|---------|-----------|---------------------------------------------------------|-------|--------------------------|-------|-------|-------|-------|-------| +| | | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| 1 | $RS_F$ | N/A to Recommendation G.992.2 – set to {00000000 $_b$ } | | | | | | | | +| 2 | $R$ | $0_b$ | $0_b$ | value of $R$ [MSB ↔ LSB] | | | | | | +| 3 | $S$ | $0_b$ | $0_b$ | value of $S$ [MSB ↔ LSB] | | | | | | +| 4 | $I$ | $I_7$ | $I_6$ | $I_5$ | $I_4$ | $I_3$ | $I_2$ | $I_1$ | $I_0$ | +| 5 | $FS(LS2)$ | N/A to Recommendation G.992.2 – set to {00000000 $_b$ } | | | | | | | | + +The four options are transmitted in order of decreasing preference. The ATU-C has control over all the data rates, so R-RATES1 is copied from the appropriate fields of C-RATES1. + +Only one bit of information is transmitted during each symbol period of R-RATES1: A zero bit is encoded to one symbol of R-REVERB1 and a one bit is encoded to one symbol of R-SEGUE1 (with addition of cyclic prefix). Since there are a total of 384 bits of RATES1 information, the length of R-RATES1 is 384 symbols. The 384 bits are to be transmitted in the order shown in Table 30, with the least significant bit first. That is, the least significant bit of option 1, $B_F$ (see Table 30) is to be transmitted during the 33rd symbol of R-RATES1, after the prefix. Following R-RATES1, the ATU-R shall enter state R-CRC1. + +### 11.10.5 R-CRC1 + +R-CRC1 is a cyclic redundancy check intended for detection of an error in the reception of R-RATES1 at the ATU-C. The crc polynomial $c(D)$ and generator polynomial $g(D)$ are the same as for C-CRC1 (see 11.9.3). The 16 bits $c_0$ to $c_{15}$ are transmitted ( $c_0$ first and $c_{15}$ last) in 16 symbol periods using the same method as R-RATES1 (see 11.10.4). Following R-CRC1, the ATU-R shall enter state R-MSG1. + +### 11.10.6 R-MSG1 + +R-MSG1 transmits a 48-bit message signal to the ATU-C. This message includes echo canceller option, etc. The message, $m$ , is defined by: + +$$m = \{m_{47}, m_{46}, \dots, m_1, m_0\}$$ + +with $m_0$ , the least significant bit, being transmitted first. The message components are defined in the following subclauses, and their assigned positions within the composite message, $m$ , are defined in Table 32. + +A total of 48 symbol periods are used to communicate the 32-bit message, using the encoding method described in 11.10.4. Following R-MSG1, the ATU-R shall enter signalling state R-CRC2. + +**Table 32/G.992.2 – Assignment of 48 bits of R-MSG1** + +| Suffix(es) of $m_i$ (Note 1) | Parameter (Note 2) | +|--------------------------------------------------------------------------------------------|--------------------------------------------------| +| 47-17 | Reserved by ITU-T | +| 16 | Echo cancellation option | +| 15 | Unused (shall be set to $1_b$ ) | +| 14-12 | Reserved by ITU-T | +| 11 | Network timing reference | +| 10, 9 | Framing mode | +| 8-4 | Reserved by ITU-T | +| 3-0 | Maximum numbers of bits per subcarrier supported | +| NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts. | | +| NOTE 2 – All reserved bits shall be set to $0_b$ . | | + +#### 11.10.6.1 Echo cancellation option – Bit 16 + +$m_{16} = 0_b$ indicates no echo cancellation; $m_{16} = 1_b$ indicates echo cancellation. + +#### 11.10.6.2 Unused – Bit 15 + +$m_{15}$ shall be set to $1_b$ . + +#### 11.10.6.3 Framing mode – Bits 10, 9 + +$m_{10}$ and $m_9$ shall both be set to $1_b$ . + +#### 11.10.6.4 Network timing reference – Bit 11 + +$m_{11} = 1_b$ indicates the ATU-R supports reconstruction of the network timing reference from the downstream indicator bits 23-20. + +#### 11.10.6.5 Maximum numbers of bits per subcarrier supported – Bits 3-0 + +The $N_{upmax}$ (transmit) capability is encoded onto $\{m_3 \dots m_0\}$ with a conventional binary representation (e.g. $1101_b = 13_{10}$ ). + +NOTE – The maximum number of bits for the downstream data, $N_{downmax}$ , that the ATU-R receiver can support need not be signalled to the ATU-C; it will be implicit in the bits and gains message, R-B&G, which is transmitted after channel analysis. + +#### 11.10.7 R-CRC2 + +R-CRC2 is a cyclic redundancy check for detection of errors in the reception of R-MSG1 at the ATU-C. The crc generator polynomial is as defined in 11.10.5. The crc message polynomial is as constructed in 11.10.5, with $m_0$ corresponding to $a_0$ and $m_{47}$ corresponding to $a_{47}$ . The crc check polynomial is generated in exactly the same way as described in 11.10.5. These 16 bits are + +transmitted in 16 symbol periods using the method described in 11.10.5. Following R-CRC2, the ATU-R shall enter state R-MEDLEY. + +#### **11.10.8 R-MEDLEY** + +R-MEDLEY is a wideband pseudo-random signal used for estimation of the upstream SNR at the ATU-C. The data to be transmitted are derived from UPRD defined in 7.10.4. In contrast to R-REVERB1, however, the cyclic prefix is used and the data sequence continues from one symbol to the next (i.e. $d_1$ to $d_6$ are not re-initialized for each symbol). Because the sequence is of length 63, and 64 bits are used for each symbol, the subcarrier vector for R-MEDLEY changes from one symbol period to the next. R-MEDLEY is transmitted for 16 384 symbol periods. Following R-MEDLEY the ATU-R enters signalling state R-REVERB4. + +#### **11.10.9 R-REVERB4** + +R-REVERB4 is the same as R-REVERB3 (see 11.10.2). The duration of R-REVERB4 is 128 symbols. This signal marks the end of channel analysis, and R-SEGUE3 immediately follows R-REVERB4. + +### **11.11 Exchange – ATU-C** + +The timing diagram of exchange is shown in Figure 26. + +![Timing diagram of exchange between ATU-C and ATU-R. The diagram shows a sequence of states and messages exchanged between the two entities. ATU-C (left) transitions through C-REVERB4, C-SEGUE2, C-RATES-RA, C-REVERB-RA, C-SEGUE-RA, C-MSG2, C-REVERB5, and C-SEGUE3. ATU-R (right) transitions through R-SEGUE3, R-MSG-RA, R-REVERB-RA, R-SEGUE-RA, R-MSG2, R-REVERB5, R-SEGUE4, R-B&G, R-REVERB6, and R-SEGUE5. Arrows indicate synchronization points between the two sides.](e404de9a69c05473fbd6af28ee32311b_img.jpg) + +The diagram illustrates the timing of message exchanges between ATU-C (left) and ATU-R (right), represented by vertical dashed lines. Boxes represent states or message blocks. Arrows indicate the flow of synchronization: from R-MSG-RA to C-SEGUE2; from C-RATES-RA to R-REVERB-RA; from R-SEGUE-RA to C-REVERB-RA; from C-SEGUE-RA to R-REVERB5; from R-MSG2 to C-REVERB5; from C-REVERB5 to R-SEGUE4; from R-B&G to C-SEGUE3; and from C-SEGUE3 to R-REVERB6. + +Timing diagram of exchange between ATU-C and ATU-R. The diagram shows a sequence of states and messages exchanged between the two entities. ATU-C (left) transitions through C-REVERB4, C-SEGUE2, C-RATES-RA, C-REVERB-RA, C-SEGUE-RA, C-MSG2, C-REVERB5, and C-SEGUE3. ATU-R (right) transitions through R-SEGUE3, R-MSG-RA, R-REVERB-RA, R-SEGUE-RA, R-MSG2, R-REVERB5, R-SEGUE4, R-B&G, R-REVERB6, and R-SEGUE5. Arrows indicate synchronization points between the two sides. + +T1533530-99 + +**Figure 26/G.992.2 – Timing diagram of exchange** + +During exchange there are three events that shall cause the ATU-C to invoke the Initialization Reset Procedure: Timeouts, no acceptable options in a C-RATES2 message, and error detection by a crc checksum. The exchange procedure is partly synchronized between ATU-C and ATU-R, and partly interactive. During the interactive part (C-REVERB4, C-REVERB5, C-REVERB-RA) a timeout shall occur when the time in the C-REVERB4 state exceeds 6000 symbols or when the time in C-REVERB-RA or C-REVERB5 state exceeds 4000 symbols. + +### 11.11.1 C-REVERB4 + +C-REVERB4 is similar to C-REVERB2 (see 11.7.8), the only difference being the addition of a cyclic prefix on every symbol, and a maximum duration of 6000 symbols. C-REVERB4 continues into the exchange procedure, and its duration is not fixed. The timeout features of C-REVERB4 are defined in this subclause. + +If the ATU-C does not detect R-CRC-RA2 within 6000 symbols, it shall time out and reset to C-QUIET1. After detection of R-SEGUE3 through R-CRC-RA2, the ATU-C shall continue to transmit C-REVERB4 for another 80 symbols before progressing to state C-SEGUE2. + +### 11.11.2 C-SEGUE2 + +The signal C-SEGUE2 is the same as C-SEGUE1 (see 11.9.1); the only difference is the addition of the cyclic prefix. The duration of C-SEGUE2 is ten symbol periods. Following C-SEGUE2 the ATU-C shall enter state C-RATES-RA to begin a second exchange of rates. + +### 11.11.3 C-RATES-RA + +C-RATES-RA is used to send four new options for transport configuration for both upstream and downstream. These options will, in general, be closer to the optimum bit rate for the channel than those in C-RATES1, and should be based on the channel information received in R-MSG-RA. A C-RATES-RA message content is not constrained by previous messages, e.g. C-RATES1 and R-MSG-RA. + +The format of C-RATES-RA is the same as that of C-RATES1, except that the four-byte prefix ( $55\ 55\ 55\ 55_{16}$ ) is not transmitted, and the signal is transmitted eight bits per symbol, as defined for C-MSG2 (see 11.11.9). The duration of C-RATES-RA is 120 symbols. + +The $\{RS_F, R, S, I, FS(LS2)\}$ shall have the following syntax. It is a ten-byte quantity comprising (one byte each): + +- The RRSI field contains Reed-Solomon FEC and interleaver parameters. The RRSI field contains a total of 80 bits organized as ten entries each of eight bits. The second entry in the RRSI field contains the parameter $RS_I$ : The number of parity bytes per symbol in the downstream transmission direction with $RS_I$ equal to R/S in bits 5 (MSB) to 0 (LSB). The third entry in the RRSI field contains the parameter S; S is the number of DFs per Reed-Solomon codeword in the downstream transmission direction in bits 5 (MSB) to 0 (LSB). The fourth entry contains the parameter I: The downstream interleave depth in codewords. The seventh entry in the RRSI field contains the parameter $RS_I$ : The number of parity bytes per symbol in the upstream transmission direction with $RS_I$ equal to R/S in bits 5 (MSB) to 0 (LSB). The eighth entry in the RRSI field contains the parameter S; S is the number of DFs per Reed-Solomon codeword in the upstream transmission direction in bits 5 (MSB) to 0 (LSB). The ninth entry contains the parameter I: The upstream interleave depth in codewords. All other bits in RRSI shall be set to 0b. + +The four options are transmitted in order of decreasing preference. Table 33 summarizes C-RATES-RA and Table 34 summarizes the RRSI fields of C-RATES-RA. + +**Table 33/G.992.2 – C-RATES-RA** + +| | Option 1 | | | Option 2 | | | Option 3 | | | Option 4 | | | +|-----------------|----------|-------|------|----------|-------|------|----------|-------|------|----------|-------|------| +| | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | $B_F$ | $B_I$ | RRSI | +| Number of bytes | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | + +**Table 34/G.992.2 – RRSI fields of C-RATES-RA** + +| Entry # | Field | <-----bits-----> | | | | | | | | +|---------|-----------------|-----------------------------------------------------------------|----------------|------------------------|----------------|----------------|----------------|----------------|----------------| +| | | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| 1 | RS F | Downstream | | | | | | | | +| 2 | R | 0 b | 0 b | value of R [MSB ↔ LSB] | | | | | | +| 3 | S | 0 b | 0 b | value of S [MSB ↔ LSB] | | | | | | +| 4 | I | I 7 | I 6 | I 5 | I 4 | I 3 | I 2 | I 1 | I 0 | +| 5 | FS(LS2) | N/A to Recommendation G.992.2 – set to {00000000 b } | | | | | | | | +| 6 | RS F | Upstream | | | | | | | | +| 7 | R | 0 b | 0 b | value of R [MSB ↔ LSB] | | | | | | +| 8 | S | 0 b | 0 b | value of S [MSB ↔ LSB] | | | | | | +| 9 | I | I 7 | I 6 | I 5 | I 4 | I 3 | I 2 | I 1 | I 0 | +| 10 | FS(LS2) | N/A to Recommendation G.992.2 – set to {00000000 b } | | | | | | | | + +#### 11.11.4 C-CRC-RA1 + +C-CRC-RA1 is a cyclic redundancy check for detection of errors in the reception of C-RATES-RA1 at the ATU-R. Its relation to C-RATES-RA1 is the same as that of C-CRC3 to C-MSG2 (see 11.11.10). Its 16 bits shall be transmitted in two symbols (see 11.11.9). Following C-CRC-RA1, the ATU-C shall enter state C-MSG-RA. + +#### 11.11.5 C-MSG-RA + +C-MSG-RA is the same in format as C-MSG1; the bit assignment is as shown in Table 35. + +**Table 35/G.992.2 – Assignment of 48 bits of C-MSG-RA** + +| Suffix(es) of mi (Note 1) | Parameter (Note 2) | +|---------------------------------------------|---------------------------------------------| +| 47-44 | New ATU-R target noise margin | +| 43-38 | ATU-R minimum noise margin (–32 to + 31 dB) | +| 37-32 | ATU-R maximum noise margin (–32 to + 31 dB) | +| 31-0 | Reserved by ITU-T | + +NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts. +NOTE 2 – All reserved bits shall be set to 0b. +NOTE 3 – Minimum and maximum values are defined in Recommendation G.997.1. +NOTE 4 – Only the minimum and maximum ATU-R noise margins are communicated to the ATU-R. This information is needed for the downstream B&G table calculation at the ATU-R. The minimum and maximum ATU-C noise margins are used locally at the ATU-C for the upstream B&G table calculation. + +The 48 bits are transmitted in six symbols (see 11.11.9) Following C-MSG-RA the ATU-C shall enter state C-CRC-RA2. + +### 11.11.6 C-CRC-RA2 + +C-CRC-RA2 is a cyclic redundancy check for detection of errors in the reception of C-MSG-RA at the ATU-R. Its relation to C-MSG-RA is the same as that of C-CRC3 to C-MSG2 (see 11.11.10). Its 16 bits shall be transmitted in two symbols. Following C-CRC-RA2, the ATU-C shall enter state C-REVERB-RA. + +### 11.11.7 C-REVERB-RA + +C-REVERB-RA is the same as C-REVERB4. After detection of R-CRC4 the ATU-C shall continue to transmit C-REVERB-RA for at least another 80 symbols before moving to state C-SEGUE-RA. + +### 11.11.8 C-SEGUE-RA + +C-SEGUE-RA is the same as C-SEGUE2. Following C-SEGUE-RA the ATU-C shall enter state C-MSG2. + +### 11.11.9 C-MSG2 + +C-MSG2 transmits a 32-bit message signal to the ATU-R. This message includes the total number of bits per symbol supported, the estimated upstream loop attenuation, and the performance margin with the selected rate option. The message, *m*, is defined by: + +$$m = \{m_{31}, m_{30}, \dots, m_1, m_0\}$$ + +with $m_0$ being transmitted first. The message components are defined in the following sub-clauses, and their assigned positions within the composite message, *m*, are defined in Table 36. + +**Table 36/G.992.2 – Assignment of 32 bits of C-MSG2** + +| Suffix(es) of $m_i$ (Note 1) | Parameter (Note 2) | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| 31-26 | Estimated average loop attenuation | +| 25-22 | Reserved by ITU-T | +| 21 | Erase all stored profiles | +| 20-16 | Performance margin with selected rate option | +| 15-9 | Reserved by ITU-T | +| 8-0 | Total number of bits supported | +| NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts.
NOTE 2 – All reserved bits shall be set to 0 b . | | + +A total of four symbol periods are used to communicate the 32-bit message, with eight bits transmitted on each symbol. Two bits are encoded onto each of the subcarriers numbered 43 through 46 using the 4-QAM constellation labelling given in 7.10.3 (for the synchronization symbol) and 11.7.5 (for C-REVERB1). The same two bits are also encoded in the same way onto a set of backup carriers, namely, subcarriers 91 through 94. The least significant byte of the message is transmitted in the first symbol of C-MSG2, with the two least significant bits of each byte encoded onto carriers 43 and 91. In addition, the pilot, subcarrier 64, shall be modulated with (+,+). Following C-MSG2, the ATU-C shall enter signalling state C-CRC3. + +#### 11.11.9.1 Estimated average upstream loop attenuation + +During channel analysis the ATU-C receiver estimates the upstream channel gain of each subcarrier in preparation for computing the SNR for each tone; it shall also calculate the average loop attenuation. This attenuation is defined as the difference between the maximum aggregate transmit + +power of 12.5 dBm minus any power cutback currently in effect and the total received power, rounded to the nearest 0.5 dB. + +The attenuation is encoded into bits 31-26 of C-MSG2 as the integer binary representation of twice the attenuation (e.g. if the average attenuation is 21.5 dB, then $\{m_{31}, \dots, m_{26}\} = 101011_b$ ). + +#### **11.11.9.2 Erase all stored profiles** + +If the ATU-C sets this bit to 1b, then all profiles as defined in 12.1.1 at the ATU-R shall be erased. + +#### **11.11.9.3 Performance margin with selected rate option** + +The ATU-C receiver shall select one of the rate options sent from the ATU-C during C-RATES-RA with a satisfactory upstream performance margin. This selected option is encoded in C-RATES2. This margin (rounded to the nearest dB) is encoded into bits 20-16 of C-MSG2 using a conventional binary representation (e.g. if the margin is 9 dB then $\{m_{20}, \dots, m_{16}\} = 01001_b$ ). + +#### **11.11.9.4 Total number of bits per symbol supported** + +The ATU-C receiver shall also calculate the maximum number of bits per symbol that the upstream channel can support with the performance margin defined in C-MSG-RA at an error rate of $10^{-7}$ . This number is encoded into bits 8-0 using a conventional binary representation (e.g. if the maximum number of bits that can be supported is 127 (data rate = 508 kbit/s), $\{m_8, \dots, m_0\} = 001111111_b$ ). + +#### **11.11.10 C-CRC3** + +C-CRC3 is a cyclic redundancy check for detection of errors in the reception of C-MSG2 at the ATU-R. The crc polynomial $c(D)$ and generator polynomial $g(D)$ are the same as for C-CRC1, as defined in 11.9.3. These 16 bits shall be transmitted in two symbol periods using the method described in 11.11.9. Following C-CRC3, the ATU-C shall enter state C-RATES2. + +#### **11.11.11 C-RATES2** + +C-RATES2 is the reply to R-RATES-RA. It combines the selected downstream option with the selected upstream option. It thus transmits the final decision on the rates that will be used in both directions. + +The ATU-C shall not change the downstream option from that selected in R-RATES2. + +The length of C-RATES2 is eight bits, and the bit pattern for C-RATES2 is shown in Table 37. Other bit patterns that are not specified in the table are reserved for future use. If none of the options requested during C-RATES1 or C-RATES-RA can be implemented, ATU-C then invokes the Initialization Reset Procedure for retraining. One symbol period is used to transmit these eight bits using the method described in 11.11.9. Following C-RATES2, the ATU-C shall enter signalling state C-CRC4. + +**Table 37/G.992.2 – Bit pattern for C-RATES2** + +| (Downstream, upstream) | Bit pattern for C-RATES2 (MSB first) (Note 1) | +|-------------------------------|------------------------------------------------------| +| (option 1, option 1) | 00010001 b | +| (option 1, option 2) | 00010010 b | +| (option 1, option 3) | 00010100 b | +| (option 1, option 4) | 00011000 b | +| (option 2, option 1) | 00100001 b | +| (option 2, option 2) | 00100010 b | +| (option 2, option 3) | 00100100 b | +| (option 2, option 4) | 00101000 b | +| (option 3, option 1) | 01000001 b | +| (option 3, option 2) | 01000010 b | +| (option 3, option 3) | 01000100 b | +| (option 3, option 4) | 01001000 b | +| (option 4, option 1) | 10000001 b | +| (option 4, option 2) | 10000010 b | +| (option 4, option 3) | 10000100 b | +| (option 4, option 4) | 10001000 b | +| all options fail | 00000000 b | + +NOTE – All other bit patterns that are not shown are reserved for future use by ITU-T. + +If it is determined that none of the four options can be implemented with the connection the ATU-C shall invoke the Initialization Reset Procedure for retraining. + +### 11.11.12 C-CRC4 + +C-CRC4 is a cyclic redundancy check for detection of errors in the reception of C-RATES2 at the ATU-R. Its relation to C-RATES2 is the same as that of C-CRC3 to C-MSG2. Its 16 bits shall be transmitted in two symbols (see 11.11.11). Following C-CRC4, the ATU-C shall enter state C-B&G. + +### 11.11.13 C-B&G + +C-B&G shall be used to transmit to the ATU-R the bits and gains information, $\{b_1, g_1, b_2, g_2, \dots, b_{31}, g_{31}\}$ , that are to be used on the upstream carriers. $b_i$ indicates the number of bits to be coded by the ATU-R transmitter onto the $i$ th upstream carrier; $g_i$ indicates the scale factor, relative to the gain that was used for that carrier during the transmission of R-MEDLEY, that shall be applied to the $i$ th upstream carrier. Because no bits or energy will be transmitted at dc or one-half the sampling rate, $b_0, g_0, b_{32}$ and $g_{32}$ are all presumed to be zero and shall not be transmitted. + +Each $b_i$ shall be represented as an unsigned 4-bit integer, with valid $b_i$ s lying in the range of zero to $N_{\text{upmax}}$ , the maximum number of bits that the ATU-R is prepared to modulate onto any subcarrier, which is communicated in R-MSG1. + +Each $g_i$ shall be represented as an unsigned 12-bit fixed-point quantity, with the binary point assumed just to the right of the third most significant bit. For example, a $g_i$ with binary representation (most significant bit listed first) 001b.010000000b would instruct the ATU-R to scale + +the constellation for carrier $i$ , by a gain factor of 1.25, so that the power in that carrier shall be 1.94 dB higher than it was during R-MEDLEY. + +For subcarriers on which no data are to be transmitted, and the receiver will never allocate bits (e.g. out-of-band subcarriers) both $b_i$ and $g_i$ shall be set to zero ( $0000_b$ and $00000000.0000_b$ , respectively) For subcarriers on which no data are to be currently transmitted, but the receiver may allocate bits later (e.g. as a result of an SNR improvement), the $b_i$ shall be set to zero and the $g_i$ to a value in the 0.19 to 1.33 range ( $000.001100000_b$ to $001.010101011_b$ ). + +The C-B&G information shall be mapped in a 496-bit (62 byte) message $m$ defined by: + +$$m = \{m_{495}, m_{494}, \dots, m_1, m_0\} = \{g_{31}, b_{31}, \dots, g_1, b_1\},$$ + +with the MSB of $b_i$ and $g_i$ in the higher $m$ index and $m_0$ being transmitted first. The message $m$ shall be transmitted in 62 symbols, using the transmission method as described in 11.11.9. + +Following C-B&G, the ATU-C shall enter the state C-CRC5. + +#### 11.11.14 C-CRC5 + +C-CRC5 is a cyclic redundancy check for detection of errors in the reception of C-B&G at the ATU-R. Its relation to C-B&G is the same as that of C-CRC3 to C-MSG2. Its 16 bits shall be transmitted in two symbols (see 11.11.9). Following C-CRC5, the ATU-C shall enter state C-REVERB5. + +#### 11.11.15 C-REVERB5 + +C-REVERB5 is the same as C-REVERB4 (see 11.11.1). The only difference is the maximum duration of 4000 symbols. The duration of C-REVERB5 depends upon the state of the ATU-R and the internal processing of the ATU-C. The ATU-C shall transmit C-REVERB5 until it has received, checked the reliability of, and established in the ATU-C transmitter, the downstream bits and gains information contained in R-B&G. If bits and gains information is not received, checked and established within 4000 symbols, the ATU-C shall timeout and invoke the Initialization Reset Procedure. The ATU-C shall enter state C-SEGUE3 as soon as it is prepared to transmit according to the conditions specified in R-B&G. + +#### 11.11.16 C-SEGUE3 + +C-SEGUE3 is used to notify the ATU-R that the ATU-C is about to enter the steady-state signalling state C-SHOWTIME. The signal C-SEGUE3 is the same as C-SEGUE2 (see 11.11.2). The duration of C-SEGUE3 is ten symbol periods. Following C-SEGUE3 the ATU-C has completed initialization and shall enter state C-SHOWTIME. + +### 11.12 Exchange – ATU-R + +During exchange there are three cases when the ATU-R shall reset itself: Timeouts, no acceptable options in an R-RATES2 message, and error detection by a crc checksum. Both shall invoke the Initialization Reset Procedure. The exchange procedure is partly synchronized between ATU-C and ATU-R, and partly interactive. During the interactive parts (R-REVERB-RA, R-REVERB5 and R-REVERB6) a timeout shall occur when the time in either state exceeds 4000 symbols. + +#### 11.12.1 R-SEGUE3 + +The signal R-SEGUE3 is the same as R-SEGUE2 (see 11.10.3). The duration of R-SEGUE3 is ten symbol periods. Following R-SEGUE3 the ATU-R shall enter state R-MSG-RA to begin a second exchange of rates. + +## 11.12.2 R-MSG-RA + +R-MSG-RA is a similar to R-MSG2, but expanded by 48 bits. The bit assignments are as shown in Table 38. + +**Table 38/G.992.2 – Assignment of 80 bits of R-MSG-RA** + +| Suffix(es) of $m_i$ (Note 1) | Parameter (Note 2) | +|------------------------------|---------------------------------------------------| +| 79-56 | Reserved by ITU-T | +| 55-49 | Number of RS overhead bytes, (R) | +| 48-40 | Number of RS payload bytes, K | +| 39-32 | Number of tones carrying data (ncloaded) | +| 31-25 | Estimated average loop attenuation | +| 24-21 | Coding gain | +| 20-16 | Performance margin with selected rate option | +| 15-14 | Reserved by ITU-T | +| 13-12 | Reserved by ITU-T | +| 11-0 | Total number of bits per DMT symbol, $B_{\max}$ . | + +NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts. +NOTE 2 – All reserved bits shall be set to 0b. + +### 11.12.2.1 Number or RS overhead bytes (R) + +This is the $R$ (as defined in 7.5) parameter used to calculate $B_{\max}$ . This parameter shall be calculated with $S = 1$ . + +### 11.12.2.2 Number of RS payload bytes (K) + +This is the $K$ (as defined in 7.3.3) parameter used to calculate $B_{\max}$ . This parameter shall be calculated with $S = 1$ . + +### 11.12.2.3 Number or tones carrying data (ncloaded) + +This is the number of subcarriers with $b_i > 0$ used to calculate $B_{\max}$ . + +### 11.12.2.4 Estimated average loop attenuation + +This parameter shall be defined as in R-MSG2; see 11.12.8. + +### 11.12.2.5 Coding gain + +The coding gain of RS FEC coding is used to calculate $B_{\max}$ . The coding gain is expressed in steps of 0.5 dB in the 0 to 7.5 dB range. + +### 11.12.2.6 Performance margin with selected rate option + +This parameter shall be defined as in R-MSG2; see 11.12.8. If R-RATES-RA indicates "no option selected", then this parameter shall be set to 0 or reflect the performance margin in dB corresponding to $B_{\max}$ (which may be 0 to 3 dB above the minimum requested SNR margin). This field is encoded as in 11.12.8.3. + +### 11.12.2.7 Total number of bits supported ( $B_{\max}$ ) + +This parameter shall be defined as in R-MSG2; see 11.12.8. + +### 11.12.3 R-CRC-RA1 + +R-CRC-RA1 is a cyclic redundancy check for detection of errors in the reception of R-MSG-RA. Its relation to R-MSG-RA is the same as that of R-CRC3 to R-MSG2. Following R-CRC-RA1, the ATU-R shall enter state R-RATES-RA. + +### 11.12.4 R-RATES-RA + +R-RATES-RA is the reply to C-RATES1 based on the results of the downstream channel analysis and is similar to R-RATES2. Instead of listing the data rates and formats as in C-RATES1, the ATU-R does one of the following: + +- Sends back only the option number of the highest data rate that can be supported based on the measured SNR of the downstream channel (not taking into account impulse noise resilience). +- Indicates that no option selection was made at this time, but will be made later based on C-RATES-RA information. +- Indicates none of the options requested during C-RATES1 can be implemented. + +As in R-RATES2, four bits are used for the option number. A total of eight bits are used for R-RATES-RA, and the bit patterns are shown in Table 39. Other bit patterns that are not specified in the table are reserved for future use. One symbol period is used to transmit these eight bits using the method described in 11.12.8. Following R-RATES-RA, the ATU-R shall enter state R-CRC-RA2. + +The format of R-RATES-RA is the same as R-RATES2, except for the additional bit pattern used to indicate "no option selected". + +**Table 39/G.992.2 – Bit pattern for R-RATES-RA** + +| Downstream | Bit pattern for R-RATES2 (MSB first) | +|--------------------|--------------------------------------| +| option 1 | 00010001 b | +| option 2 | 00100010 b | +| option 3 | 01000100 b | +| option 4 | 10001000 b | +| no option selected | 00000001 b | +| all options fail | 00000000 b | + +NOTE – All other bit patterns that are not shown are reserved by ITU-T. + +### 11.12.5 R-CRC-RA2 + +R-CRC-RA2 is a cyclic redundancy check for detection of errors in the reception of R-RATES-RA. Its relation to R-RATES-RA is the same as that of R-CRC3 to R-MSG2. Following R-CRC-RA2, the ATU-R shall enter state R-REVERB-RA. + +### 11.12.6 R-REVERB-RA + +R-REVERB-RA is the same as R-REVERB3 (see 11.10.2) The duration of R-REVERB-RA depends upon the signalling state of the ATU-C and the internal processing of the ATU-R, but has a maximum of 4000 symbols. The ATU-R shall transmit R-REVERB-RA until it has received and checked the reliability of the upstream bits and gains information contained in C-RATES-RA. After the ATU-R has received C-CRC-RA2, it shall continue to transmit R-REVERB-RA for another 64 symbols. It shall then enter R-SEGUE-RA. + +If it has not successfully detected all the control signals within 4000 symbols it shall time out and invoke the Initialization Reset Procedure. + +### 11.12.7 R-SEGUE-RA + +R-SEGUE-RA is the same as R-SEGUE4. Following R-SEGUE-RA the ATU-R shall enter state R-MSG2. + +### 11.12.8 R-MSG2 + +R-MSG2 transmits a 32-bit message signal to the ATU-C. This message includes the total number of bits per symbol supported, the estimated downstream loop attenuation, and the performance margin with the selected rate option. The message, $m$ , is defined by: + +$$m = \{m_{31}, m_{30}, \dots, m_1, m_0\}$$ + +with $m_0$ being transmitted first. The message components are defined in the following subclauses, and their assigned positions within the composite message, $m$ , are defined in Table 40. + +**Table 40/G.992.2 – Assignment of 32 bits of R-MSG2** + +| Suffix(es) of $m_i$ (Note 1) | Parameter (Note 2) | +|------------------------------|----------------------------------------------| +| 31-25 | Estimated average loop attenuation | +| 24-22 | Reserved by ITU-T | +| 21 | Erase all stored profiles | +| 20-16 | Performance margin with selected rate option | +| 15-12 | Reserved by ITU-T | +| 11-0 | Total number of bits supported | + +NOTE 1 – Within the separate fields the least significant bits have the lowest subscripts. +NOTE 2 – All reserved bits shall be set to 0b. + +A total of four symbol periods are used to communicate the 32-bit message, with eight bits transmitted on each symbol. Two bits are encoded onto each of the subcarriers numbered 10 through 13 using the 4-QAM constellation labelling given in 7.10.3 (for the synchronization symbol) and 11.7.5 (for C-REVERB1). The same two bits are also encoded in the same way onto a set of backup carriers, namely, subcarriers 20 through 23. The least significant byte of the message is transmitted in the first symbol of R-MSG2, with the two least significant bits of each byte encoded onto carriers 10 and 20. Following R-MSG2, the ATU-R shall enter state R-CRC3. + +#### 11.12.8.1 Estimated average downstream loop attenuation + +During channel analysis, the ATU-R receiver estimates the downstream channel gain of each subcarrier in preparation for computing the SNR for each tone; it shall also calculate the average loop attenuation. This attenuation is defined as the difference between ATU-C maximum aggregate transmit power of 17.2 dBm minus any power cutback currently in effect and the total received power, rounded to the nearest 0.5 dB. + +The attenuation is encoded into bits 31-25 of R-MSG2 as the integer binary representation of twice the attenuation (e.g. if the average attenuation is 21.5 dB, then $\{m_{31}, \dots, m_{25}\} = 0101011_b$ ). + +#### 11.12.8.2 Erase all stored profiles + +If the ATU-R sets this bit to 1b, then all profiles as defined in 12.1.1 at the ATU-C shall be erased. + +### 11.12.8.3 Performance margin with selected rate option + +The ATU-R receiver shall select one of the rates options sent from the ATU-C during C-RATES-RA with a satisfactory downstream margin. This selected option is encoded in R-RATES2. This margin (rounded to the nearest dB) is encoded into bits 20-16 of R-MSG2 using a conventional binary representation (e.g. if the margin is 9 dB, then $\{m_{20}, \dots, m_{16}\} = 01001_b$ ). + +### 11.12.8.4 Total number of bits per symbol supported + +The ATU-R receiver shall also calculate the maximum number of bits per symbol that the downstream channel can support with the performance margin defined in C-MSG-RA (at an error rate of $10^{-7}$ ). This number is encoded into bits 11-0 using a conventional binary representation (e.g. if the maximum number of bits that can be supported is 1724 (data rate = 6896 kbit/s), $\{m_{11}, \dots, m_0\} = 11010111100_b$ ). + +### 11.12.9 R-CRC3 + +R-CRC3 is a cyclic redundancy check for detection of errors in the reception of R-MSG2 at the ATU-C. The crc polynomial $c(D)$ and generator polynomial $g(D)$ are as described in 11.9.3. These bits are transmitted in two symbol periods using the method described in 11.12.8. Following R-CRC3, the ATU-R shall enter state R-RATES2. + +### 11.12.10 R-RATES2 + +R-RATES2 is the reply to C-RATES-RA based on the results of the downstream channel analysis. Instead of listing the data rates and formats as in C-RATES1, the ATU-R sends back only the option number of the selected data rate that can be supported based on the measured SNR of the downstream channel (not taking into account impulse noise resilience). As in C-RATES2, four bits are used for the option number. A total of eight bits are used for R-RATES2, and the bit patterns are shown in Table 41. If none of the options requested during C-RATES1 can be implemented, the ATU-R shall invoke the Initialization Reset Procedure. One symbol period is used to transmit these eight bits using the method described in 11.12.8. Following R-RATES2, the ATU-R shall enter state R-CRC4. + +**Table 41/G.992.2 – Bit pattern for R-RATES2** + +| Downstream | Bit pattern for R-RATES2 (MSB first) | +|-------------------------------------------------------------------------|--------------------------------------| +| option 1 | 00010001 b | +| option 2 | 00100010 b | +| option 3 | 01000100 b | +| option 4 | 10001000 b | +| all options fail | 00000000 b | +| NOTE – All other bit patterns that are not shown are reserved by ITU-T. | | + +If it is determined that none of the four options can be implemented with the connection, the ATU-R shall invoke the Initialization Reset Procedure for retraining. + +### 11.12.11 R-CRC4 + +R-CRC4 is a cyclic redundancy check for detection of errors in the reception of R-RATES2 at the ATU-C. Its relation to R-RATES2 is the same as that of R-CRC3 to R-MSG2. Following R-CRC4, the ATU-R shall enter state R-REVERB5. + +### 11.12.12 R-REVERB5 + +R-REVERB5 is the same as R-REVERB3 (see 11.10.2). The duration of R-REVERB5 depends upon the signalling state of the ATU-C and the internal processing of the ATU-R, but has a maximum of 4000 symbols. The ATU-R shall transmit R-REVERB5 until it has received and checked the reliability of the upstream bits and gains information contained in C-B&G. After the ATU-R has received C-CRC5, it shall continue to transmit R-REVERB5 for another 64 symbols. It shall then enter R-SEGUE4. If it has not successfully detected all the control signals within 4000 symbols, it shall timeout and invoke the Initialization Reset Procedure. + +### 11.12.13 R-SEGUE4 + +The purpose of R-SEGUE4 is to notify the ATU-C that the ATU-R is about to enter R-B&G. R-SEGUE4 is the same as R-SEGUE3 (see 11.12.1). The duration of R-SEGUE4 is ten symbol periods. Following R-SEGUE4 the ATU-R shall enter state R-B&G. + +### 11.12.14 R-B&G + +The purpose of R-B&G is to transmit to the ATU-C the bits and gains information, $\{b_1, g_1, b_2, g_2, \dots, b_{127}, g_{127}\}$ , to be used on the downstream subcarriers. $b_i$ indicates the number of bits to be coded by the ATU-C transmitter onto the $i$ th downstream subcarrier; $g_i$ indicates the scale factor that shall be applied to the $i$ th downstream subcarrier, relative to the gain that was used for that carrier during the transmission of C-MEDLEY. Because no bits or energy will be transmitted at DC or one-half the sampling rate, $b_0, g_0, b_{128}$ , and $g_{128}$ are all presumed to be zero, and are not transmitted. Because subcarrier 64 is reserved as the pilot tone, $b_{64}$ shall be set to 0 and $g_{64}$ shall be set to $g_{\text{sync}}$ . The value $g_{\text{sync}}$ represents the gain scaling applied to the sync symbol and is defined in Annexes A, B and C. + +Each $b_i$ is represented as an unsigned four-bit integer, with valid $b_i$ lying in the range of zero to $N_{\text{downmax}}$ , the maximum number of bits that the ATU-C is prepared to modulate onto any subcarrier, which is communicated in C-MSG1. + +Each $g_i$ is represented as an unsigned 12-bit fixed-point quantity, with the binary point assumed just to the right of the third most significant bit. For example, a $g_i$ with binary representation (most significant bit listed first) 001.010000000b would instruct the ATU-C to scale the constellation for carrier $i$ by a gain factor of 1.25, so that the power in that carrier shall be 1.94 dB higher than it was during C-MEDLEY. + +For subcarriers on which no data are to be transmitted, and the receiver will never allocate bits (e.g. out-of-band subcarriers) both $b_i$ and $g_i$ shall be set to zero (0000b and 00000000.0000b, respectively). For subcarriers on which no data are to be currently transmitted, but the receiver may allocate bits later (e.g. as a result of an SNR improvement), the $b_i$ shall be set to zero and the $g_i$ to a value in the 0.19 to 1.33 range (000.001100000b to 001.010101011b). + +The R-B&G information shall be mapped in a 4080-bit (510 byte) message $m$ defined by: + +$$m = \{m_{4079}, m_{4078}, \dots, m_1, m_0\} = \{g_{255}, b_{255}, \dots, g_1, b_1\},$$ + +with the MSB of $b_i$ and $g_i$ in the higher $m$ index and $m_0$ being transmitted first. The message $m$ shall be transmitted in 510 symbols, using the transmission method as described in 11.12.8. + +The $b_i$ and $g_i$ values for $i \geq 129$ and $i \leq 255$ shall be set to 0. + +Following R-B&G, the ATU-C shall enter the state R-CRC5. + +#### **11.12.15 R-CRC5** + +R-CRC5 is a cyclic redundancy check for detection of errors in the reception of R-B&G at the ATU-C. Its relation to R-B&G is the same as that of R-CRC3 to R-MSG2. Following R-CRC5, the ATU-R shall enter state R-REVERB6. + +#### **11.12.16 R-REVERB6** + +R-REVERB6 is the same as R-REVERB3 (see 11.10.2). The duration of R-REVERB6 depends upon the signalling state of the ATU-C and the internal processing of the ATU-R, but has a maximum of 4000 symbols. The ATU-R shall transmit R-REVERB6 until it has detected all ten symbols of C-SEGUE3; it shall then enter R-SEGUE5. If it has not successfully detected C-SEGUE3 within 4000 symbols, it shall time out and invoke the Initialization Reset Procedure. + +#### **11.12.17 R-SEGUE5** + +The purpose of R-SEGUE5 is to notify the ATU-C that the ATU-R is about to enter the steady-state signalling state R-SHOWTIME. R-SEGUE5 is identical to R-SEGUE3 (see 11.12.1). The duration of R-SEGUE5 is ten symbol periods. Following R-SEGUE5 the ATU-R has completed initialization and shall enter state R-SHOWTIME. + +### **11.13 Details of initialization timing** + +The requirements for the initialization sequence (as defined in 11.1 through 11.12) are shown in Figures 27 and 28. Figure 27 shows the first part of the initialization sequence, up to C-MEDLEY and R-MEDLEY. Figure 28 shows the rest of the initialization sequence. + +![](7b7596fb5ef925025341a9aacb6f2be7_img.jpg) + +| | | | | | | | | +|---------------------------|----------------------------------------------|-----------|--|-------------------------------------------------------|----------------------------------|--|----------------------------| +| | G.994.1 | | | | G.994.1 | | | +| $\geq 128$
$\leq 2048$ | C-QUIET2 | | | | R-QUIET2 | | $\leq 8000$ | +| $\leq 8516$ | C-PILOT1 | C-PILOT1A | | $\geq 128$ | | | | +| | | C-QUIET3A | | $\leq 16$ | | | | +| | | | | $\geq 496$
$\leq 512$ | R-REVERB1 | | 4096 | +| 512 | C-REVERB1 | | | $\geq 512$
$\leq 516$ | | | | +| 3072 | C-PILOT2 | | | | | | | +| 512 | C-ECT | | | | R-QUIET3 | | $\geq 2047$
$\leq 2048$ | +| 1536 | R-REVERB2 | | | | | | | +| 512 | R-ACK2 then C-PILOT3
R-ACK1 then C-QUIET5 | | | Last symbol may be shortened by any number of samples | C-ECT | | 512 | +| 1024 | R-REVERB3 | | | | R-REVERB2 | | $\geq 1024$
$\leq 1056$ | +| 10 | C-SEGUE1 | | | Introduction of cyclic prefix | C-SEGUE1 | | 10 | +| 1072 | C-RATES1/C-CRC1
C-MSG1/C-CRC2 | | | | R-REVERB3 | | $\geq 1092$
$\leq 4000$ | +| | C-MEDLEY | | | $\geq 20$
$\leq 2928$ | | | | +| 16 384 | | | | | C-SEGUE2 | | 10 | +| | | | | | C-RATES1/C-CRC1
C-MSG1/C-CRC2 | | 464 | +| | | | | | R-MEDLEY | | 16 384 | + +T1533540-99 + +Figure 27/G.992.2 – Timing diagram of initialization sequence (part 1) + +![Timing diagram of initialization sequence (part 2) showing various signal states and timing constraints between C-REVERB4, C-SEGUE2, C-RATES-RA, C-REVERB-RA, C-SEGUE-RA, C-REVERB5, C-SEGUE3, and SHOWTIME signals.](7ec36a0a9788e1cb33df5372695498c8_img.jpg) + +The diagram illustrates the initialization sequence for various audio processing components. It shows the relationship between different signal states and the timing constraints for their transitions. + +**Signal States and Timing Constraints:** + +- C-REVERB4:** $\geq 727 \leq 6000$ . This state is associated with R-MEDLEY, R-REVERB4 (128), R-SEGUE3 (10), and R-MSG-RA/R-CRC-RA1 R-RATES-RA/R-CRC-RA2 (15). A transition from this state to R-REVERB-RA has a constraint of $\geq 80 \leq 2413$ . +- C-SEGUE2:** Value 10. +- C-RATES-RA/C-CRC-RA1 C-MSG-RA/C-CRC-RA2:** Value 130. +- C-REVERB-RA:** $\geq 163 \leq 4000$ . This state is associated with R-REVERB-RA ( $\geq 288 \leq 4000$ ), R-SEGUE-RA (10), and R-MSG2/R-CRC-3 R-RATES2/R-CRC4 (9). A transition from this state to R-REVERB5 has a constraint of $\geq 64 \leq 1447$ . +- C-SEGUE-RA:** Value 10. +- C-MSG2/C-CRC3 C-RATES2/C-CRC4:** Value 9. +- C-B&G/C-CRC5:** Value 64. +- C-REVERB5:** $\geq 586 \leq 4000$ . This state is associated with R-REVERB5 ( $\geq 227 \leq 4000$ ), R-SEGUE4 (10), and R-B&G/R-CRC5 (512). A transition from this state to R-REVERB6 has a constraint of $\leq 2095$ . +- C-SEGUE3:** Value 10. +- SHOWTIME:** This state is associated with R-SEGUE5 (10) and SHOWTIME. A transition from C-SEGUE3 to SHOWTIME has a constraint of $\leq 1895$ . The maximum initialization time for SHOWTIME is 11.3 s. + +T1533550-99 + +Timing diagram of initialization sequence (part 2) showing various signal states and timing constraints between C-REVERB4, C-SEGUE2, C-RATES-RA, C-REVERB-RA, C-SEGUE-RA, C-REVERB5, C-SEGUE3, and SHOWTIME signals. + +Figure 28/G.992.2 – Timing diagram of initialization sequence (part 2) + +## 12 Fast Retrain + +### 12.1 Fast Retrain overview + +A Fast Retrain Procedure is defined to adapt transmission characteristics to changing line conditions caused by e.g. phone on/off hook transitions. The Fast Retrain Procedure is also used in an Escape from Handshake to Fast Retrain and in Power Management transitions. + +Figure 29 shows the flowchart of the various components of the Fast Retrain Procedure and how it relates to the Initialization procedures in clause 11. + +If errors occur during SHOWTIME, a Fast Retrain Procedure may also be invoked. + +![Flowchart of Fast Retrain procedure](a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg) + +``` +graph TD; Start(( )) --> G9941[G.994.1]; G9941 --> G9922[G.992.2 Initialization Procedure]; G9922 --> SHOWTIME[SHOWTIME]; G9941 --> FR[Fast Retrain Request]; FR --> CM[Channel measurement & TX PSD level selection]; CM --> TR[Transceiver Retrain & Profile selection]; TR --> SHOWTIME; TR --> UP[Unknown Profile]; TR --> KP[Known Profile]; UP --> G9941; KP --> SHOWTIME; SHOWTIME --> FR; FR --> FRA[Fast Retrain Request Abort]; FRA --> G9941; G9941 --> FT[Fast Retrain Truncate]; FT --> CM; +``` + +The flowchart illustrates the Fast Retrain procedure. It begins with an entry point leading to the G.994.1 block. From G.994.1, the flow proceeds to the G.992.2 Initialization Procedure, which then leads to the SHOWTIME block. Alternatively, from G.994.1, the flow can proceed to the Fast Retrain Request block. This block leads to Channel measurement & TX PSD level selection, which then leads to Transceiver Retrain & Profile selection. From Transceiver Retrain & Profile selection, the flow proceeds to the SHOWTIME block. There are also two branches from Transceiver Retrain & Profile selection: Unknown Profile, which loops back to G.994.1, and Known Profile, which leads to the SHOWTIME block. From the SHOWTIME block, the flow can proceed to the Fast Retrain Request block. From the Fast Retrain Request block, the flow can proceed to the Fast Retrain Request Abort block, which loops back to G.994.1. From the Fast Retrain Request block, the flow can also proceed to the Fast Retrain Truncate block, which loops back to Channel measurement & TX PSD level selection. A label 'Escape to Fast Retrain' is shown above the Fast Retrain Request block. A label 'T1533560-99' is shown at the bottom right of the diagram. + +Flowchart of Fast Retrain procedure + +Figure 29/G.992.2 – Flowchart of Fast Retrain + +#### 12.1.1 Profile requirements + +The Fast Retrain Procedure is based on the concept of stored profiles. + +The ATU shall support a minimum of two profiles, being profiles zero and one. A maximum of 16 profiles may be supported, the highest profile number being 15. + +The profiles shall at least contain the following information: + +- B&G tables (as defined in 11.11.13 and 11.12.14); +- FEC parameters R and S (as defined in 7.5); +- Interleaver depth D (as defined in 7.6). + +## 12.2 Definition of Fast Retrain signals + +The following signals are used in the Fast Retrain Procedure and are defined as: + +- R-RECOV is a single tone signal corresponding to subcarrier 20 without cyclic prefix. +- C-RECOV is a single tone signal corresponding to subcarrier 68 without cyclic prefix accompanied by the pilot subcarrier 64. + +- C-REVERB-FR1 is similar to C-REVERB1. +- R-MSG-FR1 is a 16-bit message modulated using one bit per symbol modulation in the same manner as R-MSG1 in 11.10.6. +- The R-MSG-FR1 message, $m$ , is defined by: + +$$m = \{u_7, \dots, u_1, u_0, d_7, \dots, d_1, d_0\}$$ + +Bits $d_4$ to $d_0$ (LSB) indicate the Relative Downstream Fast Retrain Power Cutback PSD level and represent the power cutback in 2-dB steps (maximum of 62 dB power cutback). Bit $d_5$ is the "Fast Retrain Truncate" bit (see 12.7) and is used to indicate that the ATU-R requests to truncate the fast retrain sequence and exit to the full initialization sequence. Bits $d_7$ and $d_6$ are reserved and set to 0b. The least significant bit $d_0$ is transmitted first. Table 42 defines the relationship between the PSD level and the values for $\{d_4, d_3, d_2, d_1, d_0\}$ . + +**Table 42/G.992.2 – Relative Downstream Fast Retrain Power Cutback** + +| Decimal value of
$\{d_4, d_3, d_2, d_1, d_0\}$ | Relative Downstream Fast
Retrain Power Cutback (dB) | +|---------------------------------------------------|--------------------------------------------------------| +| 0 | 0 | +| 1 | 2 | +| ... | ... | +| 31 | 62 | + +Bits $u_4$ to $u_0$ (LSB) indicate the Absolute Upstream Fast Retrain Power Cutback PSD level and represent the power cutback in 2-dB steps (maximum of 62 dB power cutback). Bits $u_7$ to $u_5$ are reserved and set to 0b. The least significant bit, $u_0$ , is transmitted first. Table 43 defines the relationship between the PSD levels and the values for $\{u_4, u_3, u_2, u_1, u_0\}$ . + +**Table 43/G.992.2 – Absolute Upstream Fast Retrain Power Cutback** + +| Decimal value of
$\{u_4, u_3, u_2, u_1, u_0\}$ | Absolute Upstream Fast
Retrain Power Cutback (dB) | +|---------------------------------------------------|------------------------------------------------------| +| 0 | 0 | +| 1 | 2 | +| ... | ... | +| 31 | 62 | + +- R-CRC-FR1 relates to R-MSG-FR1 as R-CRC2 relates to R-MSG1. +- C-MSG-FR1 is a 16-bit message modulated using one bit per symbol modulation, in the same manner as C-MSG1 in 11.9.4. + +The message, $m$ , is defined by: + +$$m = \{b_{15}, \dots, b_1, b_0\}$$ + +Bits $b_4$ to $b_0$ indicate the Fast Retrain Politeness Power Cutback (maximum of 62 dB power cutback) with respect to the Nominal downstream PSD Level as used by the preceding C-REVERB-FR1 signal. Bit $b_5$ is the "Fast Retrain Truncate" bit and is used to indicate that the ATU-C requests to truncate the Fast Retrain Procedure and exit to the Initialization procedure. The other bits are reserved and set to 0b. The least significant bit, $b_0$ , is + +transmitted first. Table 44 defines the relationship between the Fast Retrain Politeness Power Cutback levels and the values for $\{b_4, b_3, b_2, b_1, b_0\}$ . + +**Table 44/G.992.2 – Fast Retrain Politeness Power Cutback** + +| Decimal value of
$\{b_4, b_3, b_2, b_1, b_0\}$ | Fast Retrain Politeness
Power Cutback
(dB) | +|---------------------------------------------------|--------------------------------------------------| +| 0 | 0 | +| 1 | 2 | +| ... | ... | +| 31 | 62 | + +- C-CRC-FR1 relates to C-MSG-FR1 as C-CRC2 relates to C-MSG1 in 11.10.6. +- R-MSG-FR2 is a 16-bit message indicating the downstream line profile selected by the ATU-R. The modulation method is identical to R-MSG-FR1. + +The message, $m$ , is defined by: + +$$m = \{m_{15}, m_{14}, \dots, m_1, m_0\}$$ + +Bits $m_3$ to $m_0$ represent the line profile index (up to 16 profiles, with profile index LSB in $m_0$ ). Bit $m_4$ is used to indicate a "Known Profile" ( $0_b$ ) or an "Unknown Profile" ( $1_b$ ). The other bits are reserved and set to $0_b$ . The least significant bit, $m_0$ , is transmitted first. + +- R-CRC-FR2 relates to R-MSG-FR2 as R-CRC2 relates to R-MSG1. +- C-MSG-FR2 is a 16-bit message indicating the upstream line profile selected by the ATU-C. The modulation method is identical to C-MSG-FR1. + +The message, $m$ , is defined by: + +$$m = \{m_{15}, m_{14}, \dots, m_1, m_0\}$$ + +with $m_0$ being the least significant bit, being transmitted first. Bits $m_3$ to $m_0$ represent the line profile index (up to 16 profiles, with profile index LSB in $m_0$ ). Bit $m_4$ is used to indicate a "Known Profile" ( $0_b$ ) or an "Unknown Profile" ( $1_b$ ). The other bits are reserved and set to $0_b$ . The least significant bit, $m_0$ , is transmitted first. + +- C-CRC-FR2 relates to C-MSG-FR2 as C-CRC2 relates to C-MSG1. + +## 12.2.1 Fast Retrain Signal power levels + +### 12.2.1.1 ATU-C Fast Retrain Signal power levels + +C-RECOV shall be transmitted at Nominal level. + +C-REVERB-FR1 shall be transmitted at $(-40 - \text{Fast Retrain Politeness Power Cutback})$ dBm/Hz level. The Fast Retrain Politeness Power Cutback level is obtained using Table 25. For this purpose, the average upstream loop attenuation may be estimated on measurement of R-REVERB1, R-RECOV and/or the ATU-R G.994.1 tones. + +C-PILOT-FR1, C-REVERB-FR2, C-SEGUE-FR1, C-MSG-FR1 and C-CRC-FR1 are sent at the C-REVERB-FR1 PSD level. + +All signals starting at C-REVERB-FR3 through C-SEGUE-FR4 are transmitted at $(-40 - \text{Absolute Downstream Fast Retrain Power Cutback})$ dBm/Hz PSD level. However, because C-ECT-FR is a vendor-defined signal, the PSD specification shall only be interpreted as a maximum. + +#### **12.2.1.2 ATU-R Fast Retrain Signal power levels** + +R-RECOV shall be transmitted at Nominal level. + +All signals starting at R-REVERB-FR1 through R-CRC-FR1 are transmitted at vendor-discretionary PSD levels less than or equal to $-38$ dBm/Hz. + +All signals starting at R-REVERB-FR3 through R-SEGUE-FR5 are transmitted at $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback})$ dBm/Hz PSD level. However, because R-ECT-FR is a vendor-defined signal, the PSD specification shall only be interpreted as a maximum. + +### **12.3 Fast Retrain Procedure** + +#### **12.3.1 ATU-C initiated from SHOWTIME** + +Figures 30 and 31 show the timing diagrams for the Fast Retrain with the ATU-C initiating the procedure. Time-outs C-TO1, C-TO2, C-TO3, R-TO1 are vendor discretionary. It is advisable to make these durations as short as possible, to keep the interruption of the physical layer to a minimum. + +![Timing diagram of the Fast Retrain Procedure, ATU-C initiated from SHOWTIME (part 1).](3481cde1adf61b0452dd6489dada6d6a_img.jpg) + +The diagram illustrates the sequence of events and timing parameters for the Fast Retrain Procedure initiated by ATU-C from SHOWTIME. It is divided into two main columns: ATU-C and ATU-R. + +**ATU-C Sequence:** + +- C-SHOWTIME**: Initial state. +- C-RECOV**: Initiated by Fast Retrain Request. Duration $\leq \text{C-TO1}$ . +- C-REVERB-FR1**: Part of Channel Measurement. Duration $\leq \text{C-TO2}$ . +- C-PILOT-FR1**: Part of Channel Measurement. Duration $\leq \text{C-TO3}$ . Total duration of this phase is $750 \pm 6$ symbols. +- C-REVERB-FR2** (64 symbols): Part of Message for Fast Retrain Truncate. +- C-SEGUE-FR1** (10 symbols): Part of Message for Fast Retrain Truncate. +- C-MSG-FR1 / C-CRC-FR1** (32 symbols): Part of Introduction ATU-C Tx power. +- C-REVERB-FR3** (192 symbols): Part of Introduction ATU-C Tx power. +- C-PILOT-FR2** (1024 symbols): Part of Retrain ATU-C Equalizer. +- C-REVERB-FR4** (32 symbols): Part of Retrain ATU-C Echo canceller. +- C-ECT-FR** (512 symbols): Part of Retrain ATU-C Echo canceller. +- C-REVERB-FR5** (1056 symbols): Part of Retrain ATU-C Echo canceller. Note: Last symbol may be shortened by n samples. +- R-ACK2 then C-PILOT-FR3** (512 symbols) / **R-ACK1 then C-QUIET-FR**. + +**ATU-R Sequence:** + +- R-SHOWTIME**: Initial state. +- R-T1**: Response to C-RECOV. +- R-RECOV**: Duration $\leq \text{R-TO1}$ . +- R-REVERB-FR1** (256 symbols): Part of Channel Measurement. +- R-SEGUE-FR1** (10 symbols): Part of Channel Measurement. +- R-LINE PROBE** (512 symbols): Vendor discretionary. +- R-REVERB-FR2** (16 symbols): Part of Channel Measurement. +- R-SEGUE-FR2** (10 symbols): Part of Channel Measurement. +- R-MSG-FR1 / R-CRC-FR1** (32 symbols): Message for ATU-C Tx power. +- R-QUIET-FR1**: Response phase. +- R-REVERB-FR3** (1216 symbols): Part of Introduction ATU-R Tx power. +- R-QUIET-FR2** (512 symbols): Part of Retrain ATU-R Equalizer. +- R-REVERB-FR4** (32 symbols): Part of Retrain ATU-R Echo canceller. +- R-ECT-FR** (512 symbols): Part of Retrain ATU-R Echo canceller. + +**Timing and Control Annotations:** + +- Fast Retrain Request**: Triggering event at the start. +- Channel Measurement**: Phase involving FR1 and FR2 frames. +- Retrain AGC**: Horizontal interaction during the FR3 exchange. +- Retrain ATU-R Equalizer**: Associated with 1024 symbol duration. +- Retrain ATU-R Echo canceller**: Associated with 512 symbol duration. + +Timing diagram of the Fast Retrain Procedure, ATU-C initiated from SHOWTIME (part 1). + +**Figure 30/G.992.2 – Timing Diagram of the Fast Retrain Procedure, ATU-C initiated from SHOWTIME (*part 1*)** + +![Timing diagram showing the sequence of frames for ATU-C and ATU-R during a fast retrain procedure. The diagram is split into two columns by dashed vertical lines. The left column represents ATU-C frames, and the right column represents ATU-R frames. Arrows indicate the flow of information between them. ATU-C starts with C-REVERB-FR6 (128), C-SEGUE-FR2 (10), C-MEDLEY-FR (1024), C-REVERB-FR7 (134), C-SEGUE-FR3 (10), C-MSG-FR2/C-CRC-FR2 (32), C-REVERB-FR8 (400), C-SEGUE-FR4 (10), and C-SHOWTIME. ATU-R starts with R-REVERB-FR5 (≥ 128, ≤ 160), R-SEGUE-FR3 (10), R-MEDLEY-FR (1024), R-REVERB-FR6 (16), R-SEGUE-FR4 (10), R-MSG-FR2/R-CRC-FR2 (32), C-REVERB-FR7 (518), R-SEGUE-FR5 (10), and R-SHOWTIME. An arrow from C-SEGUE-FR2 to R-SEGUE-FR3 is labeled 'Introduction of cyclic prefix'. Another arrow from C-SEGUE-FR4 to R-SEGUE-FR5 is labeled 'Resume showtime with restart of superframe counter'. A small code 'T1533580-99' is at the bottom right.](9faa3512b2ff7973283e76192e91bf65_img.jpg) + +| | | | | | +|------|------------------------|----------------------------------------------------|------------------------|----------------| +| 128 | C-REVERB-FR6 | | R-REVERB-FR5 | ≥ 128
≤ 160 | +| 10 | C-SEGUE-FR2 | Introduction of cyclic prefix | R-SEGUE-FR3 | 10 | +| 1024 | C-MEDLEY-FR | | R-MEDLEY-FR | 1024 | +| | | | R-REVERB-FR6 | 16 | +| 134 | C-REVERB-FR7 | | R-SEGUE-FR4 | 10 | +| | | | R-MSG-FR2
R-CRC-FR2 | 32 | +| 10 | C-SEGUE-FR3 | | | | +| 32 | C-MSG-FR2
C-CRC-FR2 | | C-REVERB-FR7 | 518 | +| 400 | C-REVERB-FR8 | | | | +| 10 | C-SEGUE-FR4 | Resume showtime with restart of superframe counter | R-SEGUE-FR5 | 10 | +| | C-SHOWTIME | | R-SHOWTIME | | + +T1533580-99 + +Timing diagram showing the sequence of frames for ATU-C and ATU-R during a fast retrain procedure. The diagram is split into two columns by dashed vertical lines. The left column represents ATU-C frames, and the right column represents ATU-R frames. Arrows indicate the flow of information between them. ATU-C starts with C-REVERB-FR6 (128), C-SEGUE-FR2 (10), C-MEDLEY-FR (1024), C-REVERB-FR7 (134), C-SEGUE-FR3 (10), C-MSG-FR2/C-CRC-FR2 (32), C-REVERB-FR8 (400), C-SEGUE-FR4 (10), and C-SHOWTIME. ATU-R starts with R-REVERB-FR5 (≥ 128, ≤ 160), R-SEGUE-FR3 (10), R-MEDLEY-FR (1024), R-REVERB-FR6 (16), R-SEGUE-FR4 (10), R-MSG-FR2/R-CRC-FR2 (32), C-REVERB-FR7 (518), R-SEGUE-FR5 (10), and R-SHOWTIME. An arrow from C-SEGUE-FR2 to R-SEGUE-FR3 is labeled 'Introduction of cyclic prefix'. Another arrow from C-SEGUE-FR4 to R-SEGUE-FR5 is labeled 'Resume showtime with restart of superframe counter'. A small code 'T1533580-99' is at the bottom right. + +**Figure 31/G.992.2 – Timing Diagram of the Fast Retrain Procedure, ATU-C initiated from SHOWTIME (part 2)** + +### 12.3.1.1 ATU-C Fast Retrain Request + +The ATU-R leaves R-SHOWTIME on request from the ATU-C within R-T1 symbols after reception of C-RECOV and begins transmission of R-RECOV. + +After the reception of R-RECOV, the ATU-C shall send C-RECOV for a minimum period of 64 symbols, after which it starts to transmit C-REVERB-FR1 (with no cyclic prefix). + +Time duration R-T1 is vendor discretionary. It is advisable to make these durations as short as possible because, during an on-off hook event, the R-SHOWTIME signal with a high power level is sent to the telephone set. This could lead to sound levels at the speaker which are unacceptable to the user, especially in the case of headset use. + +### 12.3.2 ATU-R initiated from SHOWTIME + +Figure 32 shows the timing diagram for the Fast Retrain mechanism as initiated by the ATU-R. + +![Timing diagram for the Fast Retrain Procedure, ATU-R initiated from SHOWTIME. The diagram shows two vertical timelines for ATU-C and ATU-R. ATU-R starts in R-SHOWTIME and switches to R-RECOV. ATU-C starts in C-SHOWTIME, receives R-RECOV, switches to C-RECOV (64 symbols), then to C-REVERB-FR1. ATU-R receives C-REVERB-FR1 (≥ 256 symbols) and switches to R-REVERB-FR1. ATU-C receives R-REVERB-FR1 (≤ 32 symbols) and switches to C-PILOT-FR1. Vertical double-headed arrows on the left and right indicate 'Fast Retrain Request' and 'Channel Measurement' phases. Timeouts C-TO1, C-TO2, C-TO3, R-TO1 are indicated. Reference T1533590-99 is at the bottom right.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) + +Timing diagram for the Fast Retrain Procedure, ATU-R initiated from SHOWTIME. The diagram shows two vertical timelines for ATU-C and ATU-R. ATU-R starts in R-SHOWTIME and switches to R-RECOV. ATU-C starts in C-SHOWTIME, receives R-RECOV, switches to C-RECOV (64 symbols), then to C-REVERB-FR1. ATU-R receives C-REVERB-FR1 (≥ 256 symbols) and switches to R-REVERB-FR1. ATU-C receives R-REVERB-FR1 (≤ 32 symbols) and switches to C-PILOT-FR1. Vertical double-headed arrows on the left and right indicate 'Fast Retrain Request' and 'Channel Measurement' phases. Timeouts C-TO1, C-TO2, C-TO3, R-TO1 are indicated. Reference T1533590-99 is at the bottom right. + +NOTE – Time-outs C-TO1, C-TO2, C-TO3, R-TO1 are vendor discretionary. It is advisable to make these durations as short as possible, to keep the interruption of the physical layer to a minimum. + +**Figure 32/G.992.2 – Timing diagram of the Fast Retrain Procedure, ATU-R initiated from SHOWTIME** + +#### 12.3.2.1 ATU-R Fast Retrain Request + +The Fast Retrain request is started by the ATU-R leaving R-SHOWTIME autonomously and beginning the transmission of R-RECOV. + +After the reception of R-RECOV, the ATU-C leaves C-SHOWTIME and starts C-RECOV within C-T1 symbols after reception of R-RECOV. C-RECOV is transmitted for a period of 64 symbols after which it starts to transmit C-REVERB-FR1 (with no cyclic prefix). + +The ATU-R shall detect a minimum of 256 symbols of C-REVERB-FR1 before switching from R-RECOV to R-REVERB-FR1. The ATU-C switches to C-PILOT-FR1 within 32 symbols after reception of the transition of R-RECOV to R-REVERB-FR1. The other parts of the Fast Retrain are identical to the ATU-C initiated case. + +NOTE – Time duration C-T1 is vendor discretionary. It is advisable to make these durations as short as possible because, during an on-off hook event, the C-SHOWTIME, C-RECOV and C-REVERB-FR1 signals with high power levels are sent to the telephone set. This could lead to sound levels at the speaker which are unacceptable to the user, especially in the case of headset use. + +#### 12.3.3 Channel measurement + +The next part of the Fast Retrain procedure consists of a channel measurement. + +The ATU-R shall detect a minimum of 256 symbols of C-REVERB-FR1 before switching from R-RECOV to R-REVERB-FR1. The ATU-C switches to C-PILOT-FR1 within 32 symbols after reception of the transition of R-RECOV to R-REVERB-FR1. The R-REVERB-FR1 signal (with no cyclic prefix) is sent for 256 symbols and followed by ten symbols of R-SEGUE-FR1. + +The ATU-R follows the R-SEGUE-FR1 signal with 512 symbols of R-LINE PROBE. This signal allows the ATU-R to measure the echo/reflections to appropriately set the upstream Tx power. + +#### 12.3.4 Selection of Tx power levels + +The second part of the Fast Retrain procedure consists of the selection of the Tx power levels. + +After R-LINE-PROBE, the ATU-R sends the R-MSG-FR1 message indicating the new Absolute Upstream Fast Retrain Power Cutback and Relative Downstream Fast Retrain Power Cutback PSD levels via the sequence of 16 symbols of R-REVERB-FR2, ten symbols of R-SEGUE-FR2, and R-MSG-FR1/R-CRC-FR1 (32 symbols). It is followed by R-QUIET-FR1, which is terminated $750 \pm 6$ symbols after start of R-SEGUE-FR1, after which transmission R-REVERB-FR3 is begun. + +At the ATU-C, the C-PILOT-FR1 signal is terminated 612 symbols after reception of R-SEGUE-FR1, after which the ATU-C sends a message indicating a Fast Retrain Truncate bit, via the sequence of 64 symbols of C-REVERB-FR2, ten symbols of C-SEGUE-FR1, and C-MSG-FR1/C-CRC-FR1 (32 symbols). Next, the transmission of C-REVERB-FR3 is begun. + +#### 12.3.5 Transceiver retraining + +The third part of the Fast Retrain procedure consists of retraining of the transceiver. + +At the ATU-R, the R-REVERB-FR3 signal is sent for 1216 symbols, followed by 1536 symbols of R-QUIET-FR2 and 32 symbols of R-REVERB-FR4. The final symbol of R-QUIET-FR2 may be shortened by any number of samples (at a sampling rate of 276 kHz) in order to accommodate the transmitter to receiver frame alignment. R-REVERB-FR4 is immediately followed by 512 symbols of R-ECT-FR, a minimum of 128 and a maximum of 160 symbols of R-REVERB-FR5 and ten symbols of R-SEGUE-FR3. + +At the ATU-C, the C-REVERB-FR3 signal is sent for 192 symbols, followed by 1024 of C-PILOT-FR2, 32 symbols of C-REVERB-FR4, 512 symbols of C-ECT-FR, 1056 symbols of C-REVERB-FR5, 512 symbols of C-PILOT-FR3 or C-QUIET-FR, depending on whether R-ACK2 or R-ACK1 was received during a preceding normal initialization procedure, 128 symbols of C-REVERB-FR6 and ten symbols of C-SEGUE-FR2. + +The ATU-C after C-SEGUE-FR2 and the ATU-R after R-SEGUE-FR3, introduces the cyclic prefix and switches to transmitting the MEDLEY signal. The signals C-MEDLEY-FR and R-MEDLEY-FR are transmitted for 1024 symbols. This part of the Fast Retrain is intended for SNR measurement. + +#### 12.3.6 Profile exchange + +The last part of the Fast Retrain Procedure consists of profile exchange. + +Following R-MEDLEY-FR, the ATU-R line profile selection is exchanged using 16 symbols of R-REVERB-FR6, followed by ten symbols of R-SEGUE-FR4 and the R-MSG-FR2/R-CRC-FR2 (32 symbols). + +Following C-MEDLEY-FR, the ATU-C line profile selection is exchanged using 134 symbols of C-REVERB-FR7, followed by ten symbols of C-SEGUE-FR3 and the C-MSG-FR2/C-CRC-FR2 (32 symbols). Both the ATU-C and the ATU-R have independent profile selections, namely the ATU-C for upstream respectively the ATU-R for downstream. + +The ATU-C sends the final sequence consisting of 400 symbols of C-REVERB-FR8, followed by 10 symbols of C-SEGUE-FR4, after which the C-SHOWTIME is resumed with restart of the superframe counter. + +The ATU-R sends the final sequence consisting of 518 symbols of R-REVERB-FR7, which is followed by ten symbols of R-SEGUE-FR5. After this the R-SHOWTIME is resumed with restart of the superframe counter. + +The PSD level used in SHOWTIME shall be the level communicated in R-MSG-FR1, even if the PSD level during which the profile was established is different. + +### **12.4 Fast Retrain Procedure – Unknown Profile Transition** + +If an "Unknown Profile" indicator is exchanged in R-MSG-FR2 and/or C-MSG-FR2, the Fast Retrain procedure is executed up to (and including) C-SEGUE-FR4/R-SEGUE-FR5. + +Upon receiving an "Unknown Profile" bit the ATU-R shall invoke the Initialization Reset Procedure instead of resuming SHOWTIME. Upon receiving an "Unknown Profile" bit the ATU-C shall invoke the Initialization Reset Procedure. + +### **12.5 Fast Retrain Procedure – Initiated from L3 or Recommendation G.994.1** + +A Fast Retrain Procedure initiated from an idle link state or via an Escape from Handshake, shall be according to 13.4.5 or 11.5, except for a longer time duration for R-TO1 of the R-RECOV signal. This will allow for re-acquisition of loop timing at the ATU-R (see Figures 33 and 34). + +![Timing diagram of the Fast Retrain Procedure, ATU-C initiated from L3. The diagram shows signal exchanges between ATU-C and ATU-R. ATU-C sends C-RECOV, followed by C-REVERB-FR1 and C-PILOT-FR1. ATU-R responds with R-RECOV and R-REVERB-FR1. Timing constraints include C-RECOV duration ≥ 64, C-REVERB-FR1 duration ≤ C-TO2 and ≥ 256, gap between C-RECOV and C-REVERB-FR1 ≤ 32, and R-RECOV duration ≤ R-TO1.](6d67eee81b97a14e06a6fe57a95aff36_img.jpg) + +The diagram illustrates the signal flow between ATU-C and ATU-R. ATU-C transmits C-RECOV (duration $\geq 64$ ), then after a gap of $\leq 32$ , it transmits C-REVERB-FR1 (duration $\leq C-TO2$ and $\geq 256$ ) and C-PILOT-FR1. ATU-R responds with R-RECOV (duration $\leq R-TO1$ ) starting after C-RECOV begins, and then transitions to R-REVERB-FR1. Vertical dotted lines indicate continuation of signals. The diagram is labeled with T1533600-99. + +Timing diagram of the Fast Retrain Procedure, ATU-C initiated from L3. The diagram shows signal exchanges between ATU-C and ATU-R. ATU-C sends C-RECOV, followed by C-REVERB-FR1 and C-PILOT-FR1. ATU-R responds with R-RECOV and R-REVERB-FR1. Timing constraints include C-RECOV duration ≥ 64, C-REVERB-FR1 duration ≤ C-TO2 and ≥ 256, gap between C-RECOV and C-REVERB-FR1 ≤ 32, and R-RECOV duration ≤ R-TO1. + +**Figure 33/G.992.2 – Timing diagram of the Fast Retrain Procedure, ATU-C initiated from L3** + +![Timing diagram of the Fast Retrain Procedure, ATU-R initiated from L3. The diagram shows signal exchanges between ATU-C and ATU-R. ATU-R initiates with R-RECOV, followed by R-REVERB-FR1. ATU-C responds with C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-RECOV duration of 64, C-REVERB-FR1 duration ≤ C-TO2 and ≥ 256, and gap between C-RECOV and C-REVERB-FR1 ≤ 32.](da5a8f834706c8119a47c5eb732feabe_img.jpg) + +The diagram illustrates the signal flow between ATU-C and ATU-R when initiated by ATU-R. ATU-R transmits R-RECOV, then transitions to R-REVERB-FR1. ATU-C responds with C-RECOV (duration 64), then after a gap of $\leq 32$ , it transmits C-REVERB-FR1 (duration $\leq C-TO2$ and $\geq 256$ ) and C-PILOT-FR1. Vertical dotted lines indicate continuation of signals. The diagram is labeled with T1533610-99. + +Timing diagram of the Fast Retrain Procedure, ATU-R initiated from L3. The diagram shows signal exchanges between ATU-C and ATU-R. ATU-R initiates with R-RECOV, followed by R-REVERB-FR1. ATU-C responds with C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-RECOV duration of 64, C-REVERB-FR1 duration ≤ C-TO2 and ≥ 256, and gap between C-RECOV and C-REVERB-FR1 ≤ 32. + +**Figure 34/G.992.2 – Timing diagram of the Fast Retrain Procedure, ATU-R initiated from L3** + +**12.6 Abort of Fast Retrain****12.6.1 Abort of an ATU-C initiated Fast Retrain Request** + +If, during the transmission of C-RECOV of an ATU-C initiated Fast Retrain Request, a R-TONES-REQ signal is detected by the ATU-C, the ATU-C shall abort the C-RECOV signal and repond with an Initialization Reset Procedure starting with C-TONES (i.e. HSTU-R initiated duplex startup procedure as defined in Recommendation G.994.1). + +**12.6.2 Abort of an ATU-R initiated Fast Retrain Request** + +If, during the transmission of R-RECOV of an ATU-R initiated Fast Retrain Request, a C-TONES signal is detected by the ATU-R, the ATU-R shall abort the R-RECOV signal and respond with an Initialization Reset Procedure starting with R-TONES-REQ (i.e. HSTU-C initiated duplex startup procedure as defined in Recommendation G.994.1). + +**12.7 Fast Retrain Truncate** + +If an ATU-R has no valid profiles, it may truncate the Fast Retrain Procedure prematurely after R-CRC-FR1, by setting the Fast Retrain Truncate bit in R-MSG-FR1. + +If an ATU-C has no valid profiles, it may truncate the Fast Retrain Procedure prematurely after C-CRC-FR1, by setting the Fast Retrain Truncate bit in C-MSG-FR1. + +If the Fast Retrain Truncate bit is set to 1b in R-MSG-FR1 or C-MSG-FR1, the Fast Retrain Procedure is executed up to (and including) C-CRC-FR1 and R-QUIET-FR1. + +Instead of continuing with the Fast Retrain Procedure, the ATU-R or ATU-C shall invoke the Initialization Reset Procedure. + +**12.8 Fast Retrain Reset Procedure** + +If errors or malfunctions are detected or time-out limits are exceeded at various points in the Fast Retrain sequence, either an Initialization Reset Procedure or a Fast Retrain Reset Procedure shall be executed. An ATU executes a Fast Retrain Reset Procedure by transitioning to the Fast Retrain Request. An ATU-R invoking the Fast Retrain Reset Procedure shall transition to R-RECOV. An ATU-C invoking the Fast Retrain Reset Procedure shall transition to C-RECOV. + +**13 Power management****13.1 Introduction** + +Power management defines a set of power management states for the ADSL link and the use of the eoc channel to coordinate power management between the ATUs. Power reduction can be achieved by minimizing the energy transmitted by the ATU onto the U-C and U-R reference points as well as by reducing the power consumed by the ATU (e.g. reducing clock speed, turning off drivers). This subclause defines a set of stable ADSL link states between the ATU-R and ATU-C by specifying the signals that are active on the link in each state. In addition, link transition events and procedures are defined in the subclause. The details of the ATU coordination with system power management functions are outside the scope of this Recommendation. + +### 13.2 ADSL link states + +ADSL link states are defined to allow an ATU to enter a low power state without totally disconnecting the link. These states are stable states and are generally not expected to be transitory. An ATU must support the ADSL link states shown as mandatory in Table 45. + +**Table 45/G.992.2 – G.992.2 Power management states** + +| State | Name | Support | Description | +|--------------|-------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| L0 | Full On | Mandatory | The ADSL link is fully functional. | +| L1 | Low Power | Optional | The L1 state maintains full L0 state functionality at a lower net data rate (except for power management transitions).
Power reduction in L1 can be achieved by methods provided in the exchange entry procedure (e.g. reduced data rate, reduced number of tones, and reduced power per tone). The reductions are implementation specific. | +| L2 | | | Reserved for use by ITU-T. | +| L3 | Idle | Mandatory | There is no signal transmitted at the U-C and U-R reference points. The ATU may be powered or unpowered in L3. | + +States L2 and L4 to L127 are reserved for use by ITU-T. States L128 to L255 are reserved for vendor-specific implementation. + +### 13.3 Link state transitions + +Link state transitions are initiated by various events. Events may arise from functions specified in this Recommendation (e.g. loss of power) or from functions outside the Recommendation's scope (e.g. changes in the line conditions that cause need for fast retrain or higher level requests to change power management states). + +The following events are identified as potentially leading to link transitions: + +- **Grant** – This is a negotiated event and results from the successful *eoc* handshake result (see 13.5). The reason for initiating the *eoc* handshake (e.g. the request to enter into a lower power state) is outside the scope of the Recommendation. An unsuccessful *eoc* handshake does not result in a grant event. +- **Command** – This event results from an unconditional request to change states. The reason for requesting to change state (e.g. the request to move from idle to *full on* state) is outside the scope of the Recommendation. +- **Change in line condition** – This event results when the receiver detects that conditions have changed sufficiently to merit an initialization or fast retrain procedure. The method that the receiver uses to determine this (e.g. loss of suitable equalization, decrease of margin) is outside the scope of the Recommendation. +- **Failure** – This event is one of the defined failures in clause 10 (e.g. "loss of power" failure). + +The allowed state transitions are listed in Table 46, and each is assigned a label string. The labelled power management transitions are shown in Figure 35. + +**Table 46/G.992.2 – G.992.2 Power management transitions** + +| Label | Starting State | Resulting State | Event | Procedure | +|--------------|-----------------------|------------------------|------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| T0a | L0 | L0 | Change in line conditions require initialization at ATU-R or ATU-C. | Upon detection of initialization signals by ATU-R or ATU-C, the initialization procedure proceeds. | +| T0b | L0 | L0 | Change in line conditions require fast retrain at ATU-R or ATU-C. | Upon detection of fast retrain signals by ATU-R or ATU-C, the fast retrain procedure proceeds. | +| T0c | L0 | L0 | ATU-C or ATU-R is commanded to change link via the initialization procedure. | Same as procedure for T0a. | +| T0d | L0 | L1 | Grant event | Following successful eoc handshake initiated by the ATU-C or ATU-R, the exchange entry procedure is used. | +| T0e | L0 | L3 | Grant event | Following successful eoc handshake initiated by the ATU-C or ATU-R, the ATUs enter L3. | +| T0f | L0 | L3 | ATU-R detects "loss of power" failure. | Following detection of "loss of power" failure by the ATU-R, the ATU-R sends the corresponding indicator per clauses 8 and 10 and enter L3. The ATU-C enters L3 upon detection of the loss of power indication. | +| T1a | L1 | L0 | Change in line conditions require initialization at ATU-R or ATU-C. | Same as procedure for T0a. | +| T1b | L1 | L0 | Change in line conditions require fast retrain at ATU-R or ATU-C. | Same as procedure for T0b. | +| T1c | L1 | L0 | ATU-C or ATU-R is commanded to change link via the initialization procedure. | Same as procedure for T0a. | +| T1d | L1 | L0 | Grant event | Following successful eoc handshake initiated by the ATU-C or ATU-R, the fast retrain procedure is initiated by the ATU-R. | +| T1e | L1 | L3 | Grant event | Same as procedure for T0e. | +| T1f | L1 | L3 | ATU-R detects "loss of power" failure. | Same as procedure for T0f. | +| T3a | L3 | L0 | ATU-C or ATU-R is commanded to move to L0 via initialization. | Same as procedure for T0a. | +| T3b | L3 | L0 | ATU-C or ATU-R is commanded to move to L0 via fast retrain. | Upon detection of fast retrain signals by ATU-R or ATU-C, the fast retrain procedure proceeds as in 12.5. | + +![Diagram of Power management states showing transitions between FULL ON (L0), IDLE (L3), and LOW POWER (L1 (optional)). Transitions are labeled with codes like T3a, T3b, T0e, T0f, T1e, T1f, T1a, T1b, T1c, T1d, and T0d.](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +``` + +stateDiagram-v2 + [*] --> L0: FULL ON + L0 --> L3: IDLE + L0 --> L1: LOW POWER (optional) + L3 --> L0: T3a, T3b: command to move to full on with initialization or fast retrain + L3 --> L0: T0e, T0f: move to idle or "loss of power" failure + L3 --> L1: T1e, T1f: move to idle or "loss of power" failure + L1 --> L0: T1a, T1b, T1c, T1d: grant or command to move to full on, or change in line conditions + L1 --> L0: T0d: grant to move to low power + +``` + +T1533620-99 + +Diagram of Power management states showing transitions between FULL ON (L0), IDLE (L3), and LOW POWER (L1 (optional)). Transitions are labeled with codes like T3a, T3b, T0e, T0f, T1e, T1f, T1a, T1b, T1c, T1d, and T0d. + +**Figure 35/G.992.2 – Power management states** + +The ATU-R and ATU-C coordinate transitions between power states using the procedures defined in 13.4 (e.g. eoc handshake, exchange entry procedure, fast retrain). + +### 13.4 Link transition procedures + +The transitions in this subclause shall be used when the corresponding power management events occur. Following completion of each of these procedures, the ATU-R shall update the Link State data register if the register does not conform to the current ADSL link state. + +#### 13.4.1 Transitions from L0 to L0 (T0a, T0b, T0c) + +The transitions T0a, T0b and T0c transitions are not strictly part of power management, but they have been included in this subclause for completeness and to discuss potential transitions to ADSL link state L3. + +Transitions labelled T0a and T0c involve execution of the initialization procedure in clause 11. Successful execution of the initialization procedure will result in the ATU SHOWTIME state and power management state L0. However, if the initialization procedure cannot be successfully completed for some reason (e.g. there is no response to the initialization signals, repeated error conditions), a transition to power management state L3 may be initiated based upon vendor-discretionary methods. + +The transition labelled T0b involves execution of the Fast Retrain Procedure. Successful execution results in the ATU SHOWTIME state and power management state L0. Additionally, the Fast Retrain Procedure may invoke the initialization procedure. If the initialization procedure cannot be completed for some reason, a transition to power management state L3 may be initiated based upon vendor-discretionary method. + +#### 13.4.2 Transition from L0 to L1 (T0d) + +The ATU-C or ATU-R may initiate the transition from L0 to L1 by using the eoc handshake (see 13.5). + +Upon successful termination of the eoc handshake (indicated by the grant event), the Exchange entry procedure shall be used to adjust the parameters provided in the Exchange portion of the initialization procedure (e.g. data rate, number of tones, and power per tone). + +### **13.4.2.1 Exchange entry procedure** + +This subclause defines the Exchange entry procedure. This procedure reuses states, signals, and rules for determining the next state contained within clause 11 as defined in the following steps: + +- 1) After successful termination of the eoc handshake procedure, the ATU-R shall transmit R-QUIET-PM. R-QUIET-PM is defined as no transmitted signal onto the U-R interface. The ATU-R shall maintain loop timing and symbol timing during the R-QUIET-PM signal. +- 2) The ATU-C shall detect R-QUIET-PM, and respond by sending C-REVERB4 within N1 symbols on a symbol boundary. C-REVERB4 is defined in 11.11.1. +- 3) The ATU-R shall detect C-REVERB4 and respond by sending R-REVERB4 within TBD symbols (TBD to be sufficiently small so that loss of signal defect does not occur – Working value is 40). R-REVERB4 is defined in 11.10.9. The exchange portion of the initialization procedure defined in 11.11 and 11.12 shall continue from this point (i.e. the ATU-R shall send R-SEQU3 after 128 symbols of R-REVERB4). During R-MSG-RA, the ATU-R shall use the "no options selected" message. + +N1 is an implementation-specific number of symbols and shall be sufficiently small so that loss of signal defect does not occur at the ATU-C. Otherwise, the ATU-C implementation shall include a means that blocks the loss of signal defect during exchange entry procedure. + +### **13.4.3 Transitions from L1 to L0 (T1a, T1b, T1c, T1d)** + +The ATU-C or ATU-R may initiate the transition labelled T1d from L1 to L0 by using the eoc handshake. + +Upon successful termination of the eoc handshake (indicated by the grant event) the ATU-R shall begin the fast retrain procedure defined in clause 12 (i.e. start to transmit the R-RECOV signal). + +In addition, either ATU may start the initialization procedure or Fast Retrain Procedure to move to L0 using transitions labelled T1a, T1b, and T1c. The reasons for generating the command events corresponding to these transitions are outside the scope of the Recommendation. Upon successful termination of the procedures, the ADSL link state is L0. However, if the initialization or Fast Retrain Procedures cannot be successfully completed for some reason (e.g. repeated error conditions), a transition to power management state L3 may be initiated based upon vendor discretionary methods. + +### **13.4.4 Transitions from L0 or L1 to L3 (T0e, T0f, T1e, T1f)** + +#### **13.4.4.1 Orderly shutdown procedure** + +The ATU-C or ATU-R may initiate the transitions to L3 labelled T0e and T1e by using the eoc handshake. These transitions should be used for orderly power-down procedure. + +Upon successful termination of the eoc handshake (indicated by the grant event), the ATU-R shall stop transmitting. Upon detecting this, the ATU-C shall also stop transmitting. + +#### **13.4.4.2 Disorderly shutdown procedure** + +The ATU-R may initiate the transitions to L3 labelled T0f and T1f. These transitions should only be used if power is unexpectedly removed from the ATU-R. + +Upon detection of the "loss of power" failure by the ATU-R, it shall send the dying gasp eoc command (see 8.3.3). Upon detection of the loss of signal indication, the ATU-C shall stop transmitting and enter L3. + +### **13.4.5 Transitions from L3 to L0 (T3a, T3b)** + +Either ATU may start the initialization procedure to move to L0 using transitions labelled T3a. Alternately, the ATUs may initiate a fast retrain procedure as in the transition labelled T3b. The reasons for generating the command events corresponding to these transitions are outside the scope of the Recommendation. + +For transition T3b, the ATUs shall use the fast retrain procedure with provision to recover timing when starting from the idle conditions, including the possibility to terminate the procedure as described in clause 12 for some reason (e.g. profiles were not maintained during off power condition in L3). + +Upon successful termination of the procedures, the ADSL link state is L0. However, if the initialization or fast retrain procedures cannot be successfully completed for some reason (e.g. no response to training signals), the power management state is unchanged. + +## **13.5 eoc Handshake** + +The eoc Handshake is used for power management coordination between the ATUs. + +The eoc Handshake ends in either a successful or unsuccessful result. The successful result is defined as a grant event used to enable a power management state transition. The unsuccessful result does not trigger a state transition and the power management state is unchanged. + +The handshake procedure includes a sequence of eoc commands defined in clause 8. If any of the eoc command, read, or write protocols used in the eoc handshake detects an eoc protocol error condition, the eoc handshake terminates in the unsuccessful result. + +### **13.5.1 ATU-R initiated eoc Handshake** + +The ATU-R initiates the handshake using the following procedure. + +- 1) The ATU-R shall write the value of the requested ADSL link state into the Link State data register. +- 2) The ATU-R sends a REQPDN eoc autonomous message. +- 3) After receiving a REQPDN message from the ATU-R, the ATU-C shall respond by reading the requested power down state from the Link State data register using the eoc read protocol. +- 4) After receiving the REQPDN message, the ATU-C may optionally propose an alternate ADSL link state by writing a different value into Link State data register using the eoc write protocol. +- 5) After determining that it can grant the state transition request, the ATU-C shall issue the GNTPDN eoc command using the eoc command protocol. If the eoc command protocol completes by receiving the echo of the command, the handshake ends with a successful result. If the eoc command protocol completes by receiving the UTC message, the handshake ends with an unsuccessful result. + +If no response to the REQPDN eoc autonomous message is received from the ATU-C within 5 s, then the ATU-R shall resend the REQPDN message. If the ATU-R is in the middle of a multibyte read or write eoc protocol sequence, then the time-out count shall not begin until the end of the multi-byte sequence. Upon time-out, the ATU-R may send the REQPDN message up to four more times, after which the handshake procedure terminates with an unsuccessful result. + +If the ATU-C is in the middle of a multi-byte read or write sequence when a REQPDN message is received, then the ATU-C may choose to terminate the multi-byte sequence or delay response until the end of the sequence. + +If the ATU-C cannot grant the power down request for some reason (e.g. it does not support the requested state), it shall send the REJPDN eoc command using the eoc command protocol. After the ATU-R receives the REJPDN eoc command, the handshake ends with an unsuccessful result. + +If the ATU-R cannot support the granted link state for some reason (e.g. the ATU-C responds via the optional write with a different ADSL link state, or the ATU-R no longer needs to go into the granted power down state), it shall respond to GNTPDN command with the UTC eoc message using the eoc command protocol. + +### 13.5.2 ATU-C initiated eoc Handshake + +The ATU-C initiates the eoc Handshake using the following procedure: + +- 1) The ATU-C writes the value of the new ADSL link state into Link State data register using the eoc write protocol. +- 2) The ATU-C shall end the handshake sequence by issuing the GNTPDN eoc command using the eoc command protocol. If the eoc command protocol completes by receiving the echo of the command, the handshake ends with a successful result. If the eoc command protocol completes by receiving the UTC message, the handshake ends with an unsuccessful result. + +If the ATU-R cannot support the granted link state for some reason (e.g. the ATU-R does not support the ADSL link state), then it shall respond to GNTPDN command with the UTC eoc message using the eoc command protocol. + +## ANNEX A + +### Non-overlapped spectrum operation + +#### A.1 ATU-R transmitter PSD mask + +Figure A.1 shows the Power Spectral Density (PSD) mask for an ATU-R transmitter operating in non-overlapped spectrum mode. The low frequency stop band is defined as the voice band. The high frequency stop band is defined as frequencies greater than 138 kHz. The slopes shown are approximate; refer to the equations for the exact slopes. + +![Figure A.1/G.992.2 – ATU-R transmitter PSD mask. The graph plots PSD in dBm/Hz on the y-axis against Frequency in kHz on the x-axis. The y-axis has labels at -97.5, 15 dBm (0-4 kHz), and -92.5 dBm/Hz peak. The x-axis has labels at 0, 4, 25.875, 138, 307, 1221, 1630, and 11040. The PSD curve starts at -97.5 dBm/Hz from 0 to 4 kHz, rises with a 21.5 dB/octave slope to -34.5 dBm/Hz peak at 25.875 kHz, remains flat until 138 kHz, then falls with a -48 dB/octave slope to -90 dBm/Hz peak at 307 kHz. From 307 kHz to 11040 kHz, the PSD is flat at -90 dBm/Hz peak, with a dashed line indicating a -50 dBm power limit in any 1 MHz sliding window above 1630 kHz.](b75a63931e12664477d42609b4f5de31_img.jpg) + +Figure A.1/G.992.2 – ATU-R transmitter PSD mask. The graph plots PSD in dBm/Hz on the y-axis against Frequency in kHz on the x-axis. The y-axis has labels at -97.5, 15 dBm (0-4 kHz), and -92.5 dBm/Hz peak. The x-axis has labels at 0, 4, 25.875, 138, 307, 1221, 1630, and 11040. The PSD curve starts at -97.5 dBm/Hz from 0 to 4 kHz, rises with a 21.5 dB/octave slope to -34.5 dBm/Hz peak at 25.875 kHz, remains flat until 138 kHz, then falls with a -48 dB/octave slope to -90 dBm/Hz peak at 307 kHz. From 307 kHz to 11040 kHz, the PSD is flat at -90 dBm/Hz peak, with a dashed line indicating a -50 dBm power limit in any 1 MHz sliding window above 1630 kHz. + +Figure A.1/G.992.2 – ATU-R transmitter PSD mask + +| Frequency band (kHz) | Equation for line (dBm/Hertz) | Impedance (Ohm) | Resolution bandwidth (kHz) | +|----------------------|------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------| +| 0-4 | -97.5 | 100 | | +| | with +15 dBm power in 0-4 kHz window | 600 | 4 | +| > 4-25.875 | $-92.5 + 21.5 \times \log(f/4)/\log(2)$ | 100 | | +| 25.875-138 | -34.5 | 100 | 10 | +| 138-307 | $-34.5 - 48 \times \log(f/138)/\log(2)$ | 100 | 10 | +| 307-1221 | -90 | 100 | 10 | +| 1221-1630 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of $(-90 - 48 \times \log(f/1221)/\log(2) + 60) \text{ dBm}$ | 100 | 1000 | +| 1630-11 040 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of -50 dBm | 100 | 1000 | + +#### A.1.1 Passband PSD ripple and group delay + +The average PSD within the used passband shall be no greater than -38 dBm/Hz reduced by power cutback in steps of 2 dB. The lower end of the passband is implementation dependent. The upper end of the passband depends on whether the signal is for initialization (see A.1.2.1) or steady state (see A.1.2.3). + +The passband ripple shall be no greater than +3.5 dB above the specified reference level; the maximum PSD $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback} + 3.5) \text{ dBm/Hz}$ applies across the whole band from 25.875 kHz to 138 kHz. + +The group delay variation over the pass band shall not exceed 50 $\mu\text{s}$ . + +#### A.1.2 Transmit power spectral density and aggregate power level + +The power emitted by the ATU-R is limited by the specifications in this subclause. In addition, the ATU-R transmitter shall comply with national requirements on emission of electromagnetic energy. + +##### A.1.2.1 All initialization signals (except R-ECT) starting with R-REVERB1 + +The nominal PSD in the band from 25.875 to 138 kHz shall be set at -38 dBm/Hz for a nominal transmit power not greater than 12.5 dBm. The reference PSD in the band from 25.875 to 138 kHz shall be $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ for a reference aggregate transmit power of not greater than $(12.5 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm}$ . + +During the R-REVERB and R-SEGUE signals, all subcarriers from index $i$ to 31 shall be transmitted, with $i$ vendor discretionary. However, at the vendor's discretion, one or more of these subcarriers may not be transmitted during the R-MEDLEY signal. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the reference PSD level. The maximum transmit PSD shall therefore be no higher than $(-37 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ . + +##### A.1.2.2 R-ECT + +Because R-ECT is a vendor-defined signal, the PSD specification shall be interpreted only as a maximum. This maximum level is $(-3 - 37 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ . + +Cutback) dBm/Hz for the band from 25.875 to 138 kHz. Subcarriers 1 to 5 may be used, but the power in these carriers shall conform to the specification give in A.1. + +### A.1.2.3 Steady State data signal + +The nominal PSD in the band from 25.875 to 138 kHz shall be set at $-38$ dBm/Hz. The nominal aggregate power shall be set at $-1.65 + 10\log(\text{ncup})$ , where $\text{ncup}$ is the number of subcarriers used (i.e. with $b_i > 0$ ) (12.5 dBm if all subcarriers are used). The reference PSD in the band from 25.875 to 138 kHz shall be $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback})$ dBm/Hz. The reference aggregate power shall be set at $(-1.65 - \text{Absolute Upstream Fast Retrain Power Cutback} + 10\log(\text{ncup}))$ , where $\text{ncup}$ is the number of subcarriers used (12.5 $- \text{Absolute Upstream Fast Retrain Power Cutback}$ dBm if all subcarriers are used). The transmit PSD and aggregate power may, however, be changed from their reference values in either of the following circumstances: + +- The bits and gains table received from the ATU-C during initialization and possibly updated through bit swaps, may not allocate bits to some subcarriers and may finely adjust (i.e. within a $-14.5$ to $+2.5$ dB range) the transmit PSD level of others in order to equalize expected error rates on each of those subcarriers. +- Vendor discretionary transmit PSD levels for unused subcarriers (i.e. with $b_i = 0$ ). The maximum transmit PSD for these subcarriers is specified in b) and c) below. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the finely adjusted reference PSD level. The maximum transmit PSD shall therefore be no higher than $(-34.5 - \text{Absolute Upstream Fast Retrain Power Cutback})$ dBm/Hz. + +The transmit PSD of each subcarrier is defined as follows: + +- For the subcarriers with $(b_i > 0)$ , the ATU-R transmitter shall transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at R-MEDLEY transmit PSD level). The aggregate transmit power in these subcarriers shall not exceed $-1.65 + 10\log(\text{ncup}_1)$ dBm by more than 0.7 dB, where $\text{ncup}_1$ is the number of these subcarriers (i.e. with $b_i > 0$ ). +- For the subcarriers with $(b_i = 0 \text{ and } g_i > 0)$ , the ATU-R transmitter should and is recommended to transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at R-MEDLEY level), with a 4-QAM constellation point (which may change from symbol to symbol). The ATU-R receiver cannot assume any particular PSD levels on those subcarriers. The transmit PSD levels of those subcarriers shall be no higher than the C-REVERB1 transmit PSD level $+ 10\log(g_i^2)$ dB. The aggregate transmit power in these subcarriers shall not exceed $-1.65 + 10\log(\text{ncup}_2)$ dBm, where $\text{ncup}_2$ is the number of these subcarriers (i.e. with $b_i = 0 \text{ and } g_i > 0$ ). +- For the subcarriers with $(b_i = 0 \text{ and } g_i = 0)$ , the ATU-R transmitter should and is recommended to transmit no power on those subcarriers. The ATU-C receiver cannot assume any particular PSD level on those subcarriers. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +The aggregate transmit power over the 25.875 to 138 kHz band shall be no higher than 12.5 dBm, which is equivalent to an average transmit PSD of no higher than $-38$ dBm/Hz. + +NOTE – It is recommended that the $g_i$ values for subcarriers with $g_i > 0$ are constrained within $\pm 2.5$ dB with respect to $g\_sync$ , during initialization and subsequent bitswaps to avoid cyclostationary interference from the synchronization symbol. + +#### A.1.2.4 Synchronization symbol + +At Initialization, the sync symbol reference transmit PSD level shall be set at $-38 - \text{Absolute Upstream Fast Retrain Power Cutback} + 10\log(g_{\text{sync}}^2)$ dBm/Hz, with $g_{\text{sync}}^2$ defined as the average $g_i^2$ value over the used (i.e. $b_i > 0$ ) subcarriers. The sync symbol reference transmit PSD shall not be updated with user subcarrier gain changes during SHOWTIME. + +The transmit PSD level for those subcarriers with $g_i > 0$ shall be the sync symbol reference transmit PSD level. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +Since the $g_i$ are applied only to the data symbols, the transmit PSD of a synchronization symbol differs from the transmit PSD of a data symbol. These $g_i$ are calculated for the multipoint constellations in order to equalize the expected error rate on all subcarriers, and are therefore irrelevant for most of the 4-QAM modulated subcarriers of the synchronization symbol. + +#### A.2 ATU-C transmitter PSD mask + +Figure A.2 shows the Power Spectral Density (PSD) mask for an ATU-C transmitter operating in non-overlapped spectrum mode. The low frequency stop band is defined as frequencies below 138 kHz. The high frequency stop band is defined as frequencies greater than 552 kHz. The slopes shown are approximate; refer to the equations for the exact slopes. + +![Figure A.2/G.992.2 – ATU-C transmitter PSD mask. The graph shows PSD in dBm/Hz on the y-axis versus Frequency in kHz on the x-axis. The mask starts at -97.5 dBm/Hz from 0 to 4 kHz, then rises with a 4.63 dB/octave slope to -72.5 dBm/Hz at 80 kHz. It continues to rise with a 36 dB/octave slope to a peak of -36.5 dBm/Hz at 138 kHz. From 138 kHz to 552 kHz, it rises with a 36 dB/octave slope to a peak of -44.2 dBm/Hz. Between 552 kHz and 956 kHz, it falls with a 36 dB/octave slope to -65 dBm/Hz. From 956 kHz to 1800 kHz, it falls with a -72 dB/octave slope to -90 dBm/Hz. Above 1800 kHz, the PSD is constant at -90 dBm/Hz until 11 040 kHz. A dashed line indicates a -50 dBm power limit in any 1 MHz sliding window above 4545 kHz. Frequency markers on the x-axis include 0, 4, 80, 138, 552, 956, 1800, 2290, 3093, 4545, and 11 040 kHz. PSD markers on the y-axis include -97.5, -72.5, -36.5, -44.2, -65, and -90 dBm/Hz. A label '+15 dBm 0-4 kHz' is also present.](781e51b6995a56b5b3d47d057c795532_img.jpg) + +Figure A.2/G.992.2 – ATU-C transmitter PSD mask. The graph shows PSD in dBm/Hz on the y-axis versus Frequency in kHz on the x-axis. The mask starts at -97.5 dBm/Hz from 0 to 4 kHz, then rises with a 4.63 dB/octave slope to -72.5 dBm/Hz at 80 kHz. It continues to rise with a 36 dB/octave slope to a peak of -36.5 dBm/Hz at 138 kHz. From 138 kHz to 552 kHz, it rises with a 36 dB/octave slope to a peak of -44.2 dBm/Hz. Between 552 kHz and 956 kHz, it falls with a 36 dB/octave slope to -65 dBm/Hz. From 956 kHz to 1800 kHz, it falls with a -72 dB/octave slope to -90 dBm/Hz. Above 1800 kHz, the PSD is constant at -90 dBm/Hz until 11 040 kHz. A dashed line indicates a -50 dBm power limit in any 1 MHz sliding window above 4545 kHz. Frequency markers on the x-axis include 0, 4, 80, 138, 552, 956, 1800, 2290, 3093, 4545, and 11 040 kHz. PSD markers on the y-axis include -97.5, -72.5, -36.5, -44.2, -65, and -90 dBm/Hz. A label '+15 dBm 0-4 kHz' is also present. + +Figure A.2/G.992.2 – ATU-C transmitter PSD mask + +| Frequency band (kHz) | Equation for line (dBm/Hz) | Impedance (Ohm) | Resolution Bandwidth (kHz) | +|----------------------|--------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------| +| 0-4 | -97.5 | 100 | | +| | with +15 dBm power in 0-4 kHz window | 900 | 4 | +| 4-80 | $-92.5 + 4.63 \times \log(f/4)/\log(2)$ | 100 | | +| 80-138 | $-72.5 + 36 \times \log(f/80)/\log(2)$ | 100 | 10 | +| 138-552 | -36.5 | 100 | 10 | +| 552-956 | $-36.5 - 36 \times \log(f/552)/\log(2)$ | 100 | 10 | +| 956-1800 | -65 | 100 | 10 | +| 1800-2290 | $-65 - 72 \times \log(f/1800)/\log(2)$ | 100 | 10 | +| 2290-3093 | -90 | 100 | 10 | +| 3093-4545 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of $(-36.5 - 36 \times \log(f/1104)/\log(2) + 60) \text{ dBm}$ | 100 | 1000 | +| 4545-11 040 | < 90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of -50 dBm | 100 | 1000 | + +### A.2.1 Passband PSD ripple and group delay + +The average PSD within the used passband shall be no greater than -36.5 dBm/Hz reduced by power cutback in steps of 2 dB. The lower end of the passband is implementation dependent. The upper end depends on whether the signal is for initialization (see A.2.2.1) or steady state (see A.2.2.3). + +The passband ripple shall be no greater than +3.5 dB above the specified nominal level; the maximum PSD of $(-40 - 2n + 3.5) \text{ dBm/Hz}$ applies across the whole band from 25 kHz to 552 kHz, where $2n$ is defined in 11.7.5. + +The group delay variation over the passband shall not exceed 50 $\mu\text{s}$ . + +### A.2.2 Transmit power spectral density and aggregate power level + +The power emitted by the ATU-C is limited by the specifications in this subclause. In addition, the ATU-C transmitter shall comply with national requirements on emission of electromagnetic energy. + +#### A.2.2.1 All initialization signals (except C-ECT) starting with C-REVERB1 + +The nominal PSD in the band from 138 to 552 kHz shall be set at -40 dBm/Hz for a nominal transmit power in the band not greater than 16.2 dBm. In the other frequency bands the nominal PSD shall not exceed the mask represented in Figure A.2. The reference PSD in the band from 138 to 552 kHz shall be set at $(-40 - 2n) \text{ dBm/Hz}$ for reference transmit power in that band not greater than $16.2 - 2n \text{ dBm}$ , with $2n$ as defined in 11.7.5. In the other frequency bands the reference PSD shall not exceed the mask represented in Figure A.2 reduced by $2n$ . + +During the C-REVERB and C-SEGUE signals, all subcarriers from index $i$ to 127 shall be transmitted, with vendor discretionary. However, at the vendor's discretion, one or more of these subcarriers may not be transmitted during the C-MEDLEY signal. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the nominal PSD level. The maximum transmit PSD shall therefore be no higher than $-39 - 2n \text{ dBm/Hz}$ . + +### A.2.2.2 C-ECT + +Because C-ECT is a vendor-defined signal, the PSD specification shall be interpreted only as a maximum. This maximum level is $-39 - 2n$ dBm/Hz for the band from 138 to 552 kHz. Subcarriers 1 to 31 may be used, but the power in these carriers shall conform to the specification given in A.2. + +### A.2.2.3 Steady-state data signal + +The nominal PSD in the band from 138 to 552 kHz shall be set at $-40$ dBm/Hz. The nominal aggregate power shall be set at $-3.65 + 10\log(nc_{\text{down}})$ , where $nc_{\text{down}}$ is the number of subcarriers used (i.e. with $b_i > 0$ ) (16.2 dBm if all subcarriers are used). The reference PSD in the band from 138 to 552 kHz shall be set at $(-40 - 2n)$ dBm/Hz, where $2n$ is defined in 11.7.5. The transmit PSD and aggregate power may, however, be changed from their reference values in either of the following circumstances: + +- The bits and gains table (received from the ATU-R during initialization and possibly updated through bit swaps, may not allocate bits to some subcarriers and may finely adjust (i.e. within a $-14.5$ to $+2.5$ dB range) the transmit PSD level of others in order to equalize expected error rates on each of those subcarriers. +- Vendor-discretionary transmit PSD levels for unused subcarriers (i.e. with $b_i = 0$ ). The maximum transmit PSD for these subcarriers is specified in b) and c) below. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the finely adjusted reference PSD level. The maximum transmit PSD shall therefore be no higher than $-36.5 - 2n$ dBm/Hz. + +The transmit PSD of each subcarrier is defined as follows: + +- For the subcarriers with ( $b_i > 0$ ), the ATU-C transmitter shall transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at C-MEDLEY transmit PSD level). The aggregate transmit power in these subcarriers shall not exceed $-3.65 + 10\log(nc_{\text{down1}}) - 2n$ dBm by more than 0.7 dB, where $nc_{\text{down1}}$ is the number of these subcarriers (i.e. with $b_i > 0$ ). +- For the subcarriers with ( $b_i = 0$ and $g_i > 0$ ), the ATU-C transmitter should and is recommended to transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at C-MEDLEY level), with a 4-QAM constellation point (which may change from symbol to symbol). The ATU-R receiver cannot assume any particular PSD levels on those subcarriers. The transmit PSD levels of those subcarriers shall be no higher than the C-REVERB1 transmit PSD level $+ 10\log(g_i^2)$ dB. The aggregate transmit power in these subcarriers shall not exceed $-3.65 + 10\log(nc_{\text{down2}}) - 2n$ dBm, where $nc_{\text{down2}}$ is the number of these subcarriers (i.e. with $b_i = 0$ and $g_i > 0$ ). +- For the subcarriers with ( $b_i = 0$ and $g_i = 0$ ), the ATU-C transmitter should and is recommended to transmit no power on those subcarriers. The ATU-R receiver cannot assume any particular PSD level on those subcarriers. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +The aggregate transmit power over the 138 to 552 kHz band shall be no higher than $16.2 - 2n$ dBm, which is equivalent to an average transmit PSD of no higher than $-40 - 2n$ dBm/Hz (with $n$ indicating power cutback, $n = 0$ to 6). + +NOTE – It is recommended that the $g_i$ values for subcarriers with $g_i > 0$ are constrained within $\pm 2.5$ dB with respect to $g\_sync$ , during initialization and subsequent bitswaps to avoid cyclostationary interference from the synchronization symbol. + +#### A.2.2.4 Synchronization symbol + +At Initialization, the sync symbol reference transmit PSD level shall be set at $-40 - 2n + 10\log(g_{sync}^2)$ dBm/Hz, with $g_{sync}^2$ defined as the average $g_i^2$ value over the used (i.e. $b_i > 0$ ) subcarriers. The sync symbol reference transmit PSD shall not be updated with used subcarrier gain changes during SHOWTIME. + +The transmit PSD level for those subcarriers with $g_i > 0$ shall be sync symbol reference transmit PSD level. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the sub carrier is above the lowest used subcarrier. + +Since the $g_i$ are applied only to the data symbols, the transmit PSD of a synchronization symbol differs from the transmit PSD of a data symbol. These $g_i$ are calculated for the multipoint constellations in order to equalize the expected error rate on all subcarriers, and are therefore irrelevant for most of the 4-QAM modulated subcarriers of the synchronization symbol. + +### ANNEX B + +#### Overlapped spectrum operation + +##### B.1 ATU-R transmitter PSD mask + +Figure B.1 shows the Power Spectral Density (PSD) mask for an ATU-R transmitter operating in overlapped spectrum mode. The low frequency stop band is defined as the voice band. The high frequency stop band is defined as frequencies greater than 138 kHz. The slopes shown are approximate; refer to the equations for the exact slopes. + +![Figure B.1/G.992.2 – ATU-R transmitter PSD mask. The graph plots PSD in dBm/Hz on the y-axis against Frequency in kHz on the x-axis. The y-axis has labels at -97.5 and 15 dBm. The x-axis has labels at 0, 4, 25.875, 138, 307, 1221, 1630, and 11 040. The PSD mask starts at -97.5 dBm/Hz from 0 to 4 kHz, then rises with a 21.5 dB/octave slope to a peak of -92.5 dBm/Hz at 25.875 kHz. It then rises to a peak of -34.5 dBm/Hz at 138 kHz and remains flat until 307 kHz. From 307 kHz, it falls with a -48 dB/octave slope to -90 dBm/Hz at 1221 kHz. At 1221 kHz, there is a dashed line indicating a -50 dBm power limit in any 1 MHz sliding window above 1630 kHz. The PSD level is -90 dBm/Hz from 1221 kHz to 1630 kHz, then drops to -97.5 dBm/Hz at 1630 kHz and remains flat until 11 040 kHz. A label 'T1533650-99' is at the bottom right.](283a20145f621f42832049d62a49dc79_img.jpg) + +Figure B.1/G.992.2 – ATU-R transmitter PSD mask. The graph plots PSD in dBm/Hz on the y-axis against Frequency in kHz on the x-axis. The y-axis has labels at -97.5 and 15 dBm. The x-axis has labels at 0, 4, 25.875, 138, 307, 1221, 1630, and 11 040. The PSD mask starts at -97.5 dBm/Hz from 0 to 4 kHz, then rises with a 21.5 dB/octave slope to a peak of -92.5 dBm/Hz at 25.875 kHz. It then rises to a peak of -34.5 dBm/Hz at 138 kHz and remains flat until 307 kHz. From 307 kHz, it falls with a -48 dB/octave slope to -90 dBm/Hz at 1221 kHz. At 1221 kHz, there is a dashed line indicating a -50 dBm power limit in any 1 MHz sliding window above 1630 kHz. The PSD level is -90 dBm/Hz from 1221 kHz to 1630 kHz, then drops to -97.5 dBm/Hz at 1630 kHz and remains flat until 11 040 kHz. A label 'T1533650-99' is at the bottom right. + +Figure B.1/G.992.2 – ATU-R transmitter PSD mask + +| Frequency band (kHz) | Equation for line (dBm/Hertz) | Impedance (Ohm) | Resolution bandwidth (kHz) | +|----------------------|------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------| +| 0-4 | -97.5 | 100 | | +| | with +15 dBm power in 0-4 kHz window | 600 | 4 | +| >4-25.875 | $-92.5 + 21.5 \times \log(f/4)/\log(2)$ | 100 | | +| 25.875-138 | -34.5 | 100 | 10 | +| 138-307 | $-34.5 - 48 \times \log(f/138)/\log(2)$ | 100 | 10 | +| 307-1221 | -90 | 100 | 10 | +| 1221-1630 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of $(-90 - 48 \times \log(f/1221)/\log(2) + 60) \text{ dBm}$ | 100 | 1000 | +| 1630-11 040 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f+1 \text{ MHz}]$ window of -50 dBm | 100 | 1000 | + +### B.1.1 Passband PSD ripple and group delay + +The average PSD within the used passband shall be no greater than -38 dBm/Hz reduced by power cutback in steps of 2 dB. The lower end of the passband is implementation dependent. The upper end of the passband depends on whether the signal is for initialization (see B.1.2.1) or steady state (see B.1.2.3). + +The passband ripple shall be no greater than +3.5 dB above the specified reference level; the maximum PSD $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback} + 3.5) \text{ dBm/Hz}$ applies across the whole band from 25.875 kHz to 138 kHz. + +The group delay variation over the passband shall not exceed 50 $\mu\text{s}$ . + +### B.1.2 Transmit power spectral density and aggregate power level + +The power emitted by the ATU-R is limited by the specifications in this subclause. In addition, the ATU-R transmitter shall comply with national requirements on emission of electromagnetic energy. + +#### B.1.2.1 All initialization signals (except R-ECT) starting with R-REVERB1 + +The nominal PSD in the band from 25.875 to 138 kHz shall be set at -38 dBm/Hz for a nominal transmit power not greater than 12.5 dBm. The reference PSD in the band from 25.875 to 138 kHz shall be $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ for a reference aggregate transmit power of not greater than $(12.5 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm}$ . + +During the R-REVERB and R-SEGUE signals, all subcarriers from index $i$ to 31 shall be transmitted, with $i$ vendor discretionary. However, at the vendor's discretion, one or more of these subcarriers may not be transmitted during the R-MEDLEY signal. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the reference PSD level. The maximum transmit PSD shall therefore be no higher than $(-37 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ . + +#### B.1.2.2 R-ECT + +Because R-ECT is a vendor-defined signal, the PSD specification shall be interpreted only as a maximum. This maximum level is $(-37 - \text{Absolute Upstream Fast Retrain Power Cutback}) \text{ dBm/Hz}$ + +for the band from 25.875 to 138 kHz. Subcarriers 1 to 5 may be used, but the power in these carriers shall conform to the specification given in A.1. + +### B.1.2.3 Steady State data signal + +The nominal PSD in the band from 25.875 to 138 kHz shall be set at $-38$ dBm/Hz. The nominal aggregate power shall be set at $-1.65 + 10\log(\text{ncup})$ , where $\text{ncup}$ is the number of subcarriers used (i.e. with $b_i > 0$ ) (12.5 dBm if all subcarriers are used). The reference PSD in the band from 25.875 to 138 kHz shall be $(-38 - \text{Absolute Upstream Fast Retrain Power Cutback})$ dBm/Hz. The reference aggregate power shall be set at $(-1.65 - \text{Absolute Upstream Fast Retrain Power Cutback} + 10\log(\text{ncup}))$ , where $\text{ncup}$ is the number of subcarriers used (12.5 – Absolute Upstream Fast Retrain Power Cutback dBm if all subcarriers are used). The transmit PSD and aggregate power may, however, be changed from their nominal values in either of the following circumstances: + +- The bits and gains table (received from the ATU-C during initialization and possibly updated through bit swaps, (see R-B&G in TBD) may not allocate bits to some subcarriers and may finely adjust (i.e. within a $-14.5$ to $+2.5$ dB range) the transmit PSD level of others in order to equalize expected error rates on each of those subcarriers. +- Vendor-discretionary transmit PSD levels for unused subcarriers (i.e. with $b_i = 0$ ). The maximum transmit PSD for these subcarriers is specified in b) and c) below. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the finely adjusted nominal PSD level. The maximum transmit PSD shall therefore be no higher than $(-34.5 - \text{Absolute Upstream Fast Retrain Power Cutback})$ dBm/Hz. + +The transmit PSD of each subcarrier is defined as follows: + +- For the subcarriers with $(b_i > 0)$ , the ATU-R transmitter shall transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at R-MEDLEY transmit PSD level). The aggregate transmit power in these subcarriers shall not exceed $-1.65 + 10\log(\text{ncup}_1)$ dBm by more than 0.7 dB, where $\text{ncup}_1$ is the number of these subcarriers (i.e. with $b_i > 0$ ). +- For the subcarriers with $(b_i = 0 \text{ and } g_i > 0)$ , the ATU-R transmitter should and is recommended to transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at R-MEDLEY level), with a 4-QAM constellation point (which may change from symbol to symbol). The ATU-R receiver cannot assume any particular PSD levels on those subcarriers. The transmit PSD levels of those subcarriers shall be no higher than the R-REVERB1 transmit PSD level $+ 10\log(g_i^2)$ dB. The aggregate transmit power in these subcarriers shall not exceed $-1.65 + 10\log(\text{ncup}_2)$ dBm, where $\text{ncup}_2$ is the number of these subcarriers (i.e. with $b_i = 0 \text{ and } g_i > 0$ ). +- For the subcarriers with $(b_i = 0 \text{ and } g_i = 0)$ , the ATU-R transmitter should and is recommended to transmit no power on those subcarriers. The ATU-C receiver cannot assume any particular PSD level on those subcarriers. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +The aggregate transmit power over the 25.875 to 138 kHz band shall be no higher than 12.5 dBm, which is equivalent to an average transmit PSD of no higher than $-38$ dBm/Hz. + +NOTE – It is recommended that the $g_i$ values for subcarriers with $g_i > 0$ are constrained within $\pm 2.5$ dB with respect to $g\_sync$ , during initialization and subsequent bitswaps to avoid cyclostationary interference from the synchronization symbol. + +### B.1.2.4 Synchronization symbol + +At Initialization, the sync symbol reference transmit PSD level shall be set at $-38 - \text{Absolute Upstream Fast Retrain Power Cutback} + 10\log(g_{\text{sync}}^2)$ dBm/Hz, with $g_{\text{sync}}^2$ defined as the average $g_i^2$ value over the used (i.e. $b_i > 0$ ) subcarriers. The sync symbol reference transmit PSD shall not be updated with user subcarrier gain changes during SHOWTIME. + +The transmit PSD level for those subcarriers with $g_i > 0$ shall be the sync symbol reference transmit PSD level. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference (i.e. nominally $-38 - \text{Absolute Upstream Fast Retrain Power Cutback}$ ) transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +Since the $g_i$ are applied only to the data symbols, the transmit PSD of a synchronization symbol differs from the transmit PSD of a data symbol. These $g_i$ are calculated for the multipoint constellations in order to equalize the expected error rate on all subcarriers, and are therefore irrelevant for most of the 4-QAM modulated subcarriers of the synchronization symbol. + +## B.2 ATU-C transmitter PSD mask + +Figure B.2 shows the power spectral density (PSD) mask for an ATU-C transmitter operating in overlapped spectrum mode. The low frequency stop band is defined the voice band. The high frequency stop band is defined as frequencies greater than 552 kHz. The slopes shown are approximate; refer to the equations for the exact slopes. + +![Figure B.2/G.992.2 – ATU-C transmitter PSD mask. A graph showing PSD in dBm/Hz versus Frequency in kHz. The mask starts at -97.5 dBm/Hz from 0 to 4 kHz, rises with a 21 dB/octave slope to a peak of -36.5 dBm/Hz at 25.875 kHz, then drops with a -36 dB/octave slope to -65 dBm/Hz at 956 kHz. It then drops with a -72 dB/octave slope to -90 dBm/Hz at 1800 kHz, and finally levels off at -50 dBm power in any 1 MHz sliding window above 4545 kHz. Key frequency markers include 0, 4, 25.875, 552, 956, 1800, 2290, 3093, 4545, and 11 040 kHz.](fcc9f55a1ee28f957d6f5661661ae64b_img.jpg) + +PSD in dBm/Hz + +21 dB/octave + +-36.5 dBm/Hz peak + +-36 dB/octave + +-65 dBm/Hz peak + +-72 dB/octave + +-90 dBm/Hz peak + +-50 dBm power in any 1 MHz sliding window above 4545 kHz + ++15 dBm 0-4 kHz + +-97.5 + +-92.5 dBm/Hz peak + +0 4 25.875 552 956 1800 2290 3093 4545 11 040 + +Frequency in kHz + +T1533660-99 + +Figure B.2/G.992.2 – ATU-C transmitter PSD mask. A graph showing PSD in dBm/Hz versus Frequency in kHz. The mask starts at -97.5 dBm/Hz from 0 to 4 kHz, rises with a 21 dB/octave slope to a peak of -36.5 dBm/Hz at 25.875 kHz, then drops with a -36 dB/octave slope to -65 dBm/Hz at 956 kHz. It then drops with a -72 dB/octave slope to -90 dBm/Hz at 1800 kHz, and finally levels off at -50 dBm power in any 1 MHz sliding window above 4545 kHz. Key frequency markers include 0, 4, 25.875, 552, 956, 1800, 2290, 3093, 4545, and 11 040 kHz. + +Figure B.2/G.992.2 – ATU-C transmitter PSD mask + +| Frequency band (kHz) | Equation for line (dBm/Hz) | Impedance (Ohm) | Resolution Bandwidth (kHz) | +|----------------------|----------------------------------------------------------------------------------------------------------------------|-----------------|----------------------------| +| 0-4 | -97.5 | 100 | | +| | with +15 dBm power in 0-4 kHz window | 900 | 4 | +| >4-25.875 | $-92.5 + 21.5 \times \log(f/4)/\log(2)$ | 100 | | +| 25.875-552 | -34.5 | 100 | 10 | +| 552-956 | $-36.5 - 36 \times \log(f/552)/\log(2)$ | 100 | 10 | +| 956-1800 | -65 | 100 | 10 | +| 1800-2290 | $-65 - 72 \times \log(f/1800)/\log(2)$ | 100 | 10 | +| 2290-3093 | -90 | 100 | 10 | +| 3093-4545 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f + 1 \text{ MHz}]$ window of $(-36.5 - 36 \times \log(f/1104)/\log(2) + 60) \text{ dBm}$ | 100 | 1000 | +| 4545-11 040 | < -90 peak | 100 | 10 | +| | with max power in the $[f, f + 1 \text{ MHz}]$ window of -50 dBm | 100 | 1000 | + +### B.2.1 Passband PSD ripple and group delay + +The average PSD within the used passband shall be no greater than -36.5 dBm/Hz reduced by power cutback in steps of 2 dB. The lower end of the passband is implementation dependent. The upper end depends on whether the signal is for initialization (see B.2.2.1) or steady state (see B.2.2.3). + +The passband ripple shall be no greater than +3.5 dB above the specified nominal level; the maximum PSD of $(-40 - 2n + 3.5) \text{ dBm/Hz}$ applies across the whole band from 25 kHz to 552 kHz where $2n$ is defined in 11.7.5. + +The group delay variation over the pass band shall not exceed 50 $\mu\text{s}$ . + +### B.2.2 Transmit power spectral density and aggregate power level + +The power emitted by the ATU-C is limited by the specifications in this subclause. In addition, the ATU-C transmitter shall comply with national requirements on emission of electromagnetic energy. + +#### B.2.2.1 All initialization signals (except C-ECT) starting with C-REVERB1 + +The nominal PSD in the band from 25.875 to 552 kHz shall be set at -40 dBm/Hz for a nominal aggregate transmit power not greater than 17.2 dBm. The reference PSD in the band from 138 to 552 kHz shall be set at $(-40 - 2n) \text{ dBm/Hz}$ for reference aggregate transmit power not greater than $16.2 - 2n \text{ dBm}$ , with $2n$ as defined in 11.7.5 + +During the C-REVERB and C-SEGUE signals, all subcarriers from index $i$ to 127 shall be transmitted, with $i$ vendor discretionary. However, at the vendor's discretion, one or more of these subcarriers may not be transmitted during the C-MEDLEY signal. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the nominal PSD level. The maximum transmit PSD shall therefore be no higher than $-39 - 2n \text{ dBm/Hz}$ . + +#### B.2.2.2 C-ECT + +Because C-ECT is a vendor-defined signal, the PSD specification shall be interpreted only as a maximum. This maximum level is $-39 - 2n \text{ dBm/Hz}$ for the band from 25.875 to 552 kHz. + +Subcarriers 1 to 5 may be used, but the power in these carriers shall conform to the specification given in B.2. + +### B.2.2.3 Steady-state data signal + +The nominal PSD in the band from 25.875 to 552 kHz shall be set at $-40$ dBm/Hz. The nominal aggregate power shall be set at $-3.65 + 10\log(nc_{\text{down}})$ , where $nc_{\text{down}}$ is the number of subcarriers used (i.e. with $b_i > 0$ ) (17.2 dBm if all subcarriers are used). The reference PSD in the band from 138 to 552 kHz shall be set at $(-40 - 2n)$ dBm/Hz, where $2n$ is defined in 11.7.5. The transmit PSD and aggregate power may, however, be changed from their reference values in either of the following circumstances: + +- The bits and gains table (received from the ATU-R during initialization and possibly updated through bit swaps) may not allocate bits to some subcarriers and may finely adjust (i.e. within a $-14.5$ to $+2.5$ dB range) the transmit PSD level of others in order to equalize expected error rates on each of those subcarriers. +- Vendor-discretionary transmit PSD levels for unused subcarriers (i.e. with $b_i = 0$ ). The maximum transmit PSD for these subcarriers is specified in b) and c) below. + +To allow for non-ideal transmit filter effects (e.g. passband ripple and transition band rolloff), the maximum transmit PSD shall be no more than 1 dB above the finely adjusted reference PSD level. The maximum transmit PSD shall therefore be no higher than $-36.5 - 2n$ dBm/Hz. + +The transmit PSD of each subcarrier is defined as follows: + +- a) For the subcarriers with ( $b_i > 0$ ), the ATU-C transmitter shall transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at C-MEDLEY transmit PSD level). The aggregate transmit power in these subcarriers shall not exceed $-3.65 + 10\log(nc_{\text{down1}}) - 2n$ dBm by more than 0.7 dB, where $nc_{\text{down1}}$ is the number of these subcarriers (i.e. with $b_i > 0$ ). +- b) For the subcarriers with ( $b_i = 0$ and $g_i > 0$ ), the ATU-C transmitter should and is recommended to transmit at PSD levels equal to that specified by the $g_i$ (e.g. $g_i = 1$ , then transmit at C-MEDLEY level), with a 4-QAM constellation point (which may change from symbol to symbol). The ATU-R receiver cannot assume any particular PSD levels on those subcarriers. The transmit PSD levels of those subcarriers shall be no higher than the C-REVERB1 transmit PSD level $+ 10\log(g_i^2)$ dB. The aggregate transmit power in these subcarriers shall not exceed $-3.65 + 10\log(nc_{\text{down2}}) - 2n$ dBm, where $nc_{\text{down2}}$ is the number of these subcarriers (i.e. with $b_i = 0$ and $g_i > 0$ ). +- c) For the subcarriers with ( $b_i = 0$ and $g_i = 0$ ), the ATU-R transmitter should and is recommended to transmit no power on those subcarriers. The ATU-C receiver cannot assume any particular PSD level on those subcarriers. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +The aggregate transmit power over the 138 to 552 kHz band shall be no higher than $16.2 - 2n$ dBm, which is equivalent to an average transmit PSD of no higher than $-40 - 2n$ dBm/Hz (with $n$ indicating power cutback, $n = 0$ to 6). + +NOTE – It is recommended that the $g_i$ values for subcarriers with $g_i > 0$ are constrained within $\pm 2.5$ dB with respect to $g_{\text{sync}}$ , during initialization and subsequent bitswaps to avoid cyclostationary interference from the synchronization symbol. + +#### B.2.2.4 Synchronization symbol + +At Initialization, the sync symbol reference transmit PSD level shall be set at $-40 - 2n + 10\log(g_{\text{sync}}^2)$ dBm/Hz, with $g_{\text{sync}}^2$ defined as the average $g_i^2$ value over the used (i.e. $b_i > 0$ ) subcarriers. The sync symbol reference transmit PSD shall not be updated with used subcarrier gain changes during SHOWTIME. + +The transmit PSD level for those subcarriers with $g_i > 0$ shall be the sync symbol reference transmit PSD level. The transmit PSD levels of those subcarriers with $g_i = 0$ shall be at least 10 dB below the sync symbol reference transmit PSD level if the subcarrier is below the lowest used subcarrier (lowest $i$ with $b_i > 0$ ) and shall be below the sync symbol reference transmit PSD level if the subcarrier is above the lowest used subcarrier. + +Since the $g_i$ are applied only to the data symbols, the transmit PSD of a synchronization symbol differs from the transmit PSD of a data symbol. These $g_i$ are calculated for the multipoint constellations in order to equalize the expected error rate on all subcarriers, and are therefore irrelevant for most of the 4-QAM modulated subcarriers of the synchronization symbol. + +### ANNEX C + +#### ADSL above POTS co-existing in the same binder as TCM-ISDN DSL + +#### C.1 Scope + +This annex describes those specifications that are unique to an ADSL system co-existing in the same binder as TCM-ISDN as defined in Appendix III/G.961. The subclauses in this annex provide the additions and modifications to the corresponding clauses in the main body. The modifications described in this annex provide a performance improvement over the Splitterless ADSL system specified in main body in an environment co-existing with TCM-ISDN. It is preferred that ADSL system implementing this annex also implements the main body. + +#### C.2 Definitions and abbreviations + +##### C.2.1 Definitions + +**C.2.1.1 Dual Bitmap:** The Dual Bitmap method has dual bit rates under the FEXT and NEXT noise from TCM-ISDN. + +**C.2.1.2 FEXT Bitmap:** Similar to the Dual Bitmap method; however, transmission only occurs during FEXT noise from TCM-ISDN. + +**C.2.1.3 Hyperframe:** Five Superframes structure which synchronized TTR. + +**C.2.1.4 Bitmap-FR:** ATU-C transmitter bitmap under TCM-ISDN FEXT noise generated at ATU-R. + +**C.2.1.5 Bitmap-NR:** ATU-C transmitter bitmap under TCM-ISDN NEXT noise generated at ATU-R. + +**C.2.1.6 Bitmap-FC:** ATU-R transmitter bitmap under TCM-ISDN FEXT noise generated at ATU-C. + +**C.2.1.7 Bitmap-NC:** ATU-R transmitter bitmap under TCM-ISDN NEXT noise generated at ATU-C. + +**C.2.1.8 FEXTR duration:** TCM-ISDN FEXT duration at ATU-R estimated by the ATU-C. + +- C.2.1.9 **NEXTR duration:** TCM-ISDN NEXT duration at ATU-R estimated by the ATU-C. +- C.2.1.10 **FEXTC duration:** TCM-ISDN FEXT duration at ATU-C estimated by the ATU-R. +- C.2.1.11 **NEXTC duration:** TCM-SDN NEXT duration at ATU-C estimated by the ATU-R. +- C.2.1.12 **FEXTR symbol:** DMT symbol transmitted by ATU-C during TCM-ISDN FEXT. +- C.2.1.13 **NEXTR symbol:** DMT symbol transmitted by ATU-C during TCM-ISDN NEXT. +- C.2.1.14 **FEXTC symbol:** DMT symbol transmitted by ATU-R during TCM-ISDN FEXT. +- C.2.1.15 **NEXTC symbol:** DMT symbol transmitted by ATU-R during TCM-ISDN NEXT. +- C.2.1.16 **NSWF:** Sliding window frame counter. + +## C.2.2 Abbreviations + +| | | +|------------------|--------------------------------| +| TTR | TCM- ISDN Timing Reference | +| TTR C | Timing Reference used in ATU-C | +| TTR R | Timing Reference used in ATU-R | +| UI | Unit Interval | + +## C.3 Reference models + +### C.3.1 ATU-C transmitter reference model (replaces figure in 4.2) + +![Block diagram of the ATU-C transmitter reference model for ATM transport. The diagram shows the signal flow from input ATM0 through various processing stages to the output U-C. The stages include Cell TC, Mux/sync control, crc, scram and FEC, Inter-leaver, Rate converter, Natural tone ordering, Constellation encoder and gain scaling, IDFT, Output parallel/serial buffer, and DAC and analog processing. Reference points V-C, A, B, C, and U-C are marked along the bottom. Timing references TTR and NTR are shown. The IDFT stage has multiple outputs labeled 255, 254, 240, n=1, and n=0, which are fed into the Output parallel/serial buffer. The buffer also receives inputs Z_i for i=1 to 127. The DAC and analog processing block takes the output from the buffer and produces the final U-C output.](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +The diagram illustrates the ATU-C transmitter reference model for ATM transport. The signal flow is as follows: + + +- ATM0** input enters a **Cell TC** block, which outputs **AS0**. +- AS0** and **NTR** (Timing Reference) are inputs to the **Mux/sync control** block. +- The output of **Mux/sync control** passes through a **crc** block. +- The output of **crc** passes through a **scram and FEC** block. +- The output of **scram and FEC** passes through an **Inter-leaver** block. +- The output of **Inter-leaver** passes through a **Rate converter** block. +- The output of **Rate converter** passes through a **Natural tone ordering** block. +- The output of **Natural tone ordering** passes through a **Constellation encoder and gain scaling** block. +- The output of **Constellation encoder and gain scaling** passes through an **IDFT** block. +- The **IDFT** block has multiple outputs labeled 255, 254, 240, n=1, and n=0, which are fed into the **Output parallel/serial buffer** block. +- The **Output parallel/serial buffer** block also receives inputs $Z_i$ for $i = 1$ to $127$ . +- The output of the **Output parallel/serial buffer** block passes through a **DAC and analog processing** block, which produces the final **U-C** output. +- TTR** (Timing Reference) is shown as a reference point for the **Rate converter**, **Natural tone ordering**, and **Constellation encoder and gain scaling** blocks. +- OAM** (Operations, Administration, and Management) is shown as an input/output for the **Mux/sync control** block. +- Reference points are marked along the bottom: **V-C** (ATM0 input), **A** (Mux data frame), **B** (FEC output data frame), **C** (Constellation encoder input data frame), and **U-C** (final output). + +Block diagram of the ATU-C transmitter reference model for ATM transport. The diagram shows the signal flow from input ATM0 through various processing stages to the output U-C. The stages include Cell TC, Mux/sync control, crc, scram and FEC, Inter-leaver, Rate converter, Natural tone ordering, Constellation encoder and gain scaling, IDFT, Output parallel/serial buffer, and DAC and analog processing. Reference points V-C, A, B, C, and U-C are marked along the bottom. Timing references TTR and NTR are shown. The IDFT stage has multiple outputs labeled 255, 254, 240, n=1, and n=0, which are fed into the Output parallel/serial buffer. The buffer also receives inputs Z\_i for i=1 to 127. The DAC and analog processing block takes the output from the buffer and produces the final U-C output. + +NOTE – The TTR may be generated in the ATU-C without being provided from the V-C reference point TCM-ISDN clock. + +**Figure C.1/G.992.2 – ATU-C transmitter reference model for ATM transport** + +### C.3.2 ATU-R transmitter reference model (replaces figure in 4.2) + +![Block diagram of the ATU-R transmitter reference model for ATM transport. The diagram shows the signal flow from ATM0 input through various processing stages to the U-R output. Key components include Cell TC, Mux/sync control, crc, scram and FEC, Inter-leaver, Rate converter, Natural tone ordering, Constellation encoder and gain scaling, IDFT, Output parallel/serial buffer, and DAC and analog processing. Reference points T-R, A, B, C, and U-R are marked along the signal path. A TTR_R input is shown for the Rate converter, Natural tone ordering, and Constellation encoder blocks. The IDFT block has 63 inputs, with indices 62, 59, n=1, and n=0 explicitly labeled. The output of the IDFT is connected to the Output parallel/serial buffer and also to a DAC and analog processing block. The DAC and analog processing block has 31 outputs, indexed i=1 to 31, and produces the final U-R output. The OAM signal is shown as a bidirectional connection to the Mux/sync control block. The LS0 signal is an output of the Cell TC block. The reference points are defined as: T-R (between ATM0 and Cell TC), A (between Mux/sync control and crc), B (between crc and scram and FEC), C (between Rate converter and Natural tone ordering), and U-R (after the DAC and analog processing block). The diagram also includes labels for 'Reference points', 'Mux data frame', 'FEC output data frame', and 'Constellation encoder input data frame'.](1d62ade6b682fdfb8e192d10a06246a4_img.jpg) + +The diagram illustrates the ATU-R transmitter reference model for ATM transport. The signal flow is as follows: + +- ATM0** input enters a **Cell TC** block, which outputs **LS0**. +- LS0** and **OAM** (bidirectional) enter the **Mux/sync control** block. +- The output of **Mux/sync control** passes through a **crc** block (Reference point **A**). +- It then enters a **scram and FEC** block (Reference point **B**). +- The output of **scram and FEC** goes to an **Inter-leaver** block. +- The output of **Inter-leaver** enters a **Rate converter** block, which also receives $\overline{\text{TTR}_\text{R}}$ . +- The output of **Rate converter** passes through **Natural tone ordering** (Reference point **C**). +- The output of **Natural tone ordering** enters the **Constellation encoder and gain scaling** block, which also receives $\overline{\text{TTR}_\text{R}}$ . +- The output of **Constellation encoder and gain scaling** is labeled $Z_i$ for $i = 1$ to 31. +- These signals enter the **IDFT** block, which has 63 inputs (indices 63, 62, 59, $n = 1$ , $n = 0$ are shown). +- The output of **IDFT** goes to the **Output parallel/serial buffer** and also to a **DAC and analog processing** block. +- The **DAC and analog processing** block has 31 outputs ( $i = 1$ to 31) and produces the final **U-R** output (Reference point **U-R**). + +Reference points are marked as follows: + +- T-R**: Between ATM0 and Cell TC. +- A**: Between Mux/sync control and crc. +- B**: Between crc and scram and FEC. +- C**: Between Rate converter and Natural tone ordering. +- U-R**: After the DAC and analog processing block. + +Other labels include: + +- Reference points**: A horizontal line with markers for T-R, A, B, C, and U-R. +- Mux data frame**: Located below reference point A. +- FEC output data frame**: Located below reference point B. +- Constellation encoder input data frame**: Located below reference point C. +- T1533680-99**: A small text label in the bottom right corner. + +Block diagram of the ATU-R transmitter reference model for ATM transport. The diagram shows the signal flow from ATM0 input through various processing stages to the U-R output. Key components include Cell TC, Mux/sync control, crc, scram and FEC, Inter-leaver, Rate converter, Natural tone ordering, Constellation encoder and gain scaling, IDFT, Output parallel/serial buffer, and DAC and analog processing. Reference points T-R, A, B, C, and U-R are marked along the signal path. A TTR\_R input is shown for the Rate converter, Natural tone ordering, and Constellation encoder blocks. The IDFT block has 63 inputs, with indices 62, 59, n=1, and n=0 explicitly labeled. The output of the IDFT is connected to the Output parallel/serial buffer and also to a DAC and analog processing block. The DAC and analog processing block has 31 outputs, indexed i=1 to 31, and produces the final U-R output. The OAM signal is shown as a bidirectional connection to the Mux/sync control block. The LS0 signal is an output of the Cell TC block. The reference points are defined as: T-R (between ATM0 and Cell TC), A (between Mux/sync control and crc), B (between crc and scram and FEC), C (between Rate converter and Natural tone ordering), and U-R (after the DAC and analog processing block). The diagram also includes labels for 'Reference points', 'Mux data frame', 'FEC output data frame', and 'Constellation encoder input data frame'. + +NOTE – The $\text{TTR}_\text{R}$ shall be generated in the ATU-R from the received $\text{TTR}_\text{C}$ , and shall be locked to 690 periods of upstream sampling clock (276 kHz). + +**Figure C.2/G.992.2 – ATU-R transmitter reference model for ATM transport** + +### C.3.3 ATU transmitter timing model (new) + +#### C.3.3.1 TCM-ISDN crosstalk timing model (new) + +Figure C.3 shows the timing chart of the crosstalk from TCM-ISDN. + +![Timing chart of the TCM-ISDN cross-talk showing various signal levels and timing parameters across different network components.](b71190d39f5e641548d0f091e94e663d_img.jpg) + +The timing chart illustrates the relationship between various signals and timing parameters in a TCM-ISDN network. The vertical axis lists the following components and signals from top to bottom: + +- TTR**: TCM-ISDN Timing reference. A horizontal line with a double-headed arrow indicating a 377 UI period. +- CO**: Central Office. It has two shaded regions: 'transmit ISDN' in the first half and 'receive ISDN' in the second half of the TTR period. +- RT**: Remote Terminal. It also has two shaded regions: 'receive ISDN' in the first half and 'transmit ISDN' in the second half. +- Propagation Delay**: Indicated between CO and RT as $0 \leq \text{propagation delay} \leq 16 \text{ UI}$ . +- Offset**: $S_C$ is the offset from TTR to $TTR_C$ . +- $TTR_C$** : Timing reference used in ATU-C. A horizontal line starting at the beginning of the first half of the TTR period. +- $TTR_R$** : Timing reference used in ATU-R. A horizontal line starting at the beginning of the second half of the TTR period. +- Received $TTR_C$** : Received $TTR_C$ at ATU-R. A horizontal line starting at the beginning of the first half of the TTR period. +- Offset**: $S_R$ is the offset from received $TTR_C$ to $TTR_R$ . +- ATU-C Tx**: ATU-C Transmitter. It shows 'Frame' blocks and a dashed line. A propagation delay of $0 \leq \text{propagation delay} \leq 18.5 \text{ UI}$ is indicated from the start of the first frame to the start of the second frame. +- ATU-R Tx**: ATU-R Transmitter. It also shows 'Frame' blocks and a dashed line. +- Crosstalk Signals**: + - $FEXT_R$** : Far End Crosstalk from RT to ATU-C in the first half of the TTR period. + - $NEXT_R$** : Near End Crosstalk from RT to ATU-C in the second half of the TTR period. + - $NEXT_C$** : Near End Crosstalk from CO to ATU-R in the first half of the TTR period. + - $FEXT_C$** : Far End Crosstalk from CO to ATU-R in the second half of the TTR period. + +Timing chart of the TCM-ISDN cross-talk showing various signal levels and timing parameters across different network components. + +1 UI = 3.125 $\mu\text{s}$ + +$FEXT_R$ and $NEXT_R$ are estimated by the ATU-C + +$FEXT_C$ and $NEXT_C$ are estimated by the ATU-R + +TTR TCM-ISDN Timing reference + +$TTR_C$ Timing reference used in ATU-C + +Received $TTR_C$ Received $TTR_C$ at ATU-R + +$TTR_R$ Timing reference used in ATU-R + +$S_C$ $55 \times 0.9058 \mu\text{s}$ : Offset from TTR to $TTR_C$ + +$S_R$ $-42 \times 0.9058 \mu\text{s}$ : Offset from received $TTR_C$ to $TTR_R$ + +**Figure C.3/G.992.2 – Timing chart of the TCM-ISDN cross-talk** + +The data stream of TCM-ISDN transmitted in a TTR period. The TCM-ISDN CO transmits the symbols in the first half of the TTR period and the TCM-ISDN RT transmits in the second half of the TTR period. The ATU-C receives NEXT noise from ISDN in the first half of the TTR period and FEXT noise from ISDN in the second half of the TTR period. On the other hand, the ATU-R receives FEXT noise from the TCM-ISDN in the first half of the TTR period and NEXT noise from the ISDN in the second half of the TTR period. + +As defined in C.5.2.2 and in C.8, the ATU-C shall estimate the $FEXT_{R}$ and $NEXT_{R}$ duration at ATU-R, and ATU-R shall estimate $FEXT_{C}$ and $NEXT_{C}$ duration at ATU-C taking propagation delay on the subscriber line into consideration. + +The ATU-C shall transmit any symbol by synchronizing with the $TTR_{C}$ . The ATU-R shall transmit any symbol by synchronizing with the $TTR_{R}$ generated from received $TTR_{C}$ . + +### C.3.3.2 Sliding Window (new) + +Figure C.4 shows the timing chart of the downstream transmission. + +![Figure C.4: Timing chart of the downstream transmission showing the Sliding Window operation.](6b0035ff72f9d3c2ef6141caf9a6c743_img.jpg) + +The diagram illustrates the timing of downstream transmission over a Hyperframe of 345 symbols. At the top, the $TTR_{C}$ (400 Hz) signal is shown as a square wave. Below it, the 'Crosstalk period' is divided into $FEXT_{R}$ and $NEXT_{R}$ intervals. The 'ATU-C Tx frame' row shows the alignment of transmission frames. The 'SWB' (Symbol Window Boundary) row at the bottom shows a sequence of symbol blocks. A legend indicates that shaded blocks are $FEXT_{R}$ symbols and unshaded blocks are $NEXT_{R}$ symbols. An arrow points to the 'Sliding Window' boundary between symbols. + +Figure C.4: Timing chart of the downstream transmission showing the Sliding Window operation. + +**Figure C.4/G.992.2 – Sliding Window** + +The "Sliding Window" operation defines the procedures to transmit symbols under the crosstalk noise environment synchronized to the period of the $TTR$ . The $FEXT_{C/R}$ symbol represents the symbol completely inside the $FEXT_{C/R}$ duration. The $NEXT_{C/R}$ symbol represents the symbol containing any $NEXT_{C/R}$ duration. Thus, there are more $NEXT_{C/R}$ symbols than $FEXT_{C/R}$ symbols. + +The ATU-C decides which transmission symbol is a $FEXT_{R}$ or $NEXT_{R}$ symbol according to the Sliding Window and transmits it with the corresponding bit table. Similarly, ATU-R decides which transmission symbol is a $FEXT_{C}$ or $NEXT_{C}$ and transmits it with the corresponding bit table. Although the phase of the Sliding Window is asynchronous with the $TTR_{C/R}$ , the pattern is fixed to the 345 frames of the hyperframe (see C.5.2.2). + +### C.3.3.3 ATU-C symbol synchronization to $TTR_{C}$ (new) + +The time duration of 345 symbols is equal to 34 cycles of $TTR_{C}$ (or 32 cycles of $TTR_{C}$ for symbols without a cyclic prefix). This implies a PLL lock at the ATU-R. + +### C.3.3.4 Dual Bitmap switching (new) + +The ATU-C transmits $FEXT_{R}$ symbols using Bitmap-FR (in $FEXT_{R}$ duration), and transmits $NEXT_{R}$ symbols using Bitmap-NR (in $NEXT_{R}$ duration) according to the result of initialization. The ATU-R transmits $FEXT_{C}$ symbols using Bitmap-FC (in $FEXT_{C}$ duration), and transmits $NEXT_{C}$ symbols using Bitmap-NC (in $NEXT_{C}$ duration) in the same manner. + +The ATU-C shall have the capability to disable transmission during $NEXT_{C/R}$ (see Table 11-i/G.994.1). In this case, the ATU-C shall transmit only the pilot tone as $NEXT_R$ symbol, and ATU-R shall transmit silence as the $NEXT_C$ symbol (see C.5.5 and C.5.7). + +### C.3.3.5 Loop timing at ATU-R (new) + +The phase relation between received symbol and transmitted symbol of ATU-R at reference point U-R shall meet the phase tolerances as shown in Figure C.5. + +![Timing diagram for ATU-R loop timing. It shows two horizontal timelines. The top timeline is labeled 'ATU-R receive DMT symbol' and has five empty rectangular boxes. The bottom timeline is labeled 'ATU-R transmit DMT symbol' and also has five empty rectangular boxes. A vertical dashed line labeled '(point U-R)' passes through the third box of both timelines. A horizontal double-headed arrow between the start of the third box on the receive timeline and the start of the third box on the transmit timeline is labeled '±4.5 μs + S_R'. The text 'T1533710-99' is in the bottom right corner.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +Timing diagram for ATU-R loop timing. It shows two horizontal timelines. The top timeline is labeled 'ATU-R receive DMT symbol' and has five empty rectangular boxes. The bottom timeline is labeled 'ATU-R transmit DMT symbol' and also has five empty rectangular boxes. A vertical dashed line labeled '(point U-R)' passes through the third box of both timelines. A horizontal double-headed arrow between the start of the third box on the receive timeline and the start of the third box on the transmit timeline is labeled '±4.5 μs + S\_R'. The text 'T1533710-99' is in the bottom right corner. + +Figure C.5/G.992.2 – Loop timing for ATU-R + +## C.4 ATU interfaces + +### C.4.1 ATM interface for ATM transport (replaces figure in 6.1) + +The functional data interface at the ATU for ATM transport are shown in Figure C.6. + +![Functional interface diagram for ATM transport. On the left, a box labeled 'Digital network' contains a dashed box 'ATM layer' which contains a box 'PORT0'. On the right is a box labeled 'ATU'. Between them is a dashed box 'ATM0'. Arrows show data flow: 'Tx_ATM0' and 'Tx_Cell_Handshake0' from PORT0 to ATU; 'Rx_ATM0' and 'Rx_Cell_Handshake0' from ATU to PORT0. Below ATM0, arrows show 'Operations, administration, maintenance and control' from PORT0 to ATU; 'NTR(ATU-C)' and 'TTR(ATU-C)' from ATU to PORT0; and 'NTR(ATU-R)' from PORT0 to ATU. A vertical dashed line separates the ATM0 box from the ATU box, labeled 'V-C or T-R interface' at the bottom. The text 'T1533720-99' is in the bottom right corner.](3dcf40a20068ca8624a8d8bbc79bdb87_img.jpg) + +Functional interface diagram for ATM transport. On the left, a box labeled 'Digital network' contains a dashed box 'ATM layer' which contains a box 'PORT0'. On the right is a box labeled 'ATU'. Between them is a dashed box 'ATM0'. Arrows show data flow: 'Tx\_ATM0' and 'Tx\_Cell\_Handshake0' from PORT0 to ATU; 'Rx\_ATM0' and 'Rx\_Cell\_Handshake0' from ATU to PORT0. Below ATM0, arrows show 'Operations, administration, maintenance and control' from PORT0 to ATU; 'NTR(ATU-C)' and 'TTR(ATU-C)' from ATU to PORT0; and 'NTR(ATU-R)' from PORT0 to ATU. A vertical dashed line separates the ATM0 box from the ATU box, labeled 'V-C or T-R interface' at the bottom. The text 'T1533720-99' is in the bottom right corner. + +NOTE – The TTR may be generated in the ATU-C without being provided from the V-C reference point. + +Figure C.6/G.992.2 – ATU functional interfaces to the ATM layer at the V or T reference point + +## C.5 ATU functional characteristics (pertains to clause 7) + +### C.5.1 Payload transfer delay (supplements 7.1.1) + +The one-way transfer delay (excluding cell specific functionalities) for payload bits from the V reference point at the central office end (V-C) to the T reference point at remote the end (T-R) shall be as specified in 7.1.1 with an additional 5 ms for transfer delay attributed to the rate converter. The same requirement applies in the opposite direction, from the T-R reference point to the V-C reference point. + +The maximum rate converter delay specified in the above text shall not apply to bit rates of 32 kbit/s and 64 kbit/s. + +### C.5.2 Framing (pertains to 7.3) + +#### C.5.2.1 Superframe structure (supplements 7.3.3.1) + +Since the rate converter reorders the user data and overhead bit-level data to create hyperframes, the input data frames to the constellation encoder are different than those defined in 7.3.3.1. + +#### C.5.2.2 Hyperframe structure (new) + +This annex uses the hyperframe structure shown in Figures C.7 and C.8. Both figures show the phase relationship between the $TTR_{C/R}$ and the hyperframe at the point U-C and U-R. Each hyperframe is composed of five superframes, which are numbered from 0 to 4. In order to indicate the boundary of the hyperframe, the inverse synch symbol is used for the $N_{inv}$ -th superframe, which is generated from a tone-by-tone 180-degree phase reversal of the synchronization symbol (see C.5.3.1) except for the pilot tone. $N_{inv}$ -th is defined as: + +$$N_{inv}\text{-th} = \begin{array}{l} 3 \text{ (SPF\#3) for downstream} \\ 0 \text{ (SPF\#0) for upstream} \end{array}$$ + +The FEC Output Frame from the interleaver is put into the rate-converter. The bit-level data stream from the rate-converter is extracted according to the size of $Bitmap-F_{R/C}$ and $Bitmap-N_{R/C}$ using the Sliding Window (see C.3.3.2 and C.3.3.4). + +In order to make the bit rate to be a multiple of 32 kbit/s, the dummy bits are inserted at the end of hyperframe by the rate converter (see C.5.6). The hyperframe is composed of 345 DMT symbols, numbered from 0 to 344. Each symbol is assigned as a $FEXT_{R/C}$ or $NEXT_{R/C}$ symbol in a $FEXT_{R/C}$ or $NEXT_{R/C}$ duration (see C.3.3.1). The following numerical formula gives the information which duration $N_{dmt}$ -th DMT symbol belongs to at ATU transmitter. + +Downstream data (see Figure C.9): + +For ( $N_{dmt} = 0, 1, \dots, 344$ ) + +$$S = 272 \times N_{dmt} \bmod 2760$$ + +| | | +|-----------------------------------------|----------------------| +| if { $(S + 271 < a)$ or $(S > a + b)$ } | then $FEXT_R$ symbol | +| else | then $NEXT_R$ symbol | + +where $a = 1243$ , $b = 1461$ + +Upstream data (see Figure C.10): + +For ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +$$S = 272 \times N_{\text{dmt}} \bmod 2760$$ + +| | | +|------------------------------------------|-------------------------------| +| if { $(S > a)$ and $(S + 271 < a + b)$ } | then FEXT C symbol | +| else | then NEXT C symbol | + +where $a = 1315$ , $b = 1293$ + +Thus, 128 DMT symbols are allocated in the FEXTR/C duration (FEXTC/R symbols), and 217 DMT symbols are allocated in the NEXTR/C duration (NEXTC/R symbols). The symbols are composed of: + +FEXTC/R symbol: + +- Number of symbols using Bitmap-FR/C = 126 +- Number of synch symbols = 1 +- Number of inverse synch symbols = 1 + +NEXTC/R symbol: + +- Number of symbols using Bitmap-NR/C = 214 +- Number of synch symbols = 3 + +During FEXT Bitmap mode, the ATU-C shall transmit only the pilot tone as NEXTR symbol and the ATU-R shall not transmit any signal as NEXTC symbol. + +![Diagram of Hyperframe structure for downstream showing timing and symbol sequences.](f431b5db0c635c95318cff1adbe10c05_img.jpg) + +(point B) + +5 superframes (= 340 frames) + +1 superframe = 68 frames (17 ms) + +1 frame = 250 $\mu$ s + +Rate converter + +(point U-C, including synch symbol) + +TC#0 (2.5 ms) + +TC#27 + +TC#33 + +TTRC + +ATU-R crosstalk + +FEXT + +NEXT + +Hyperframe = 345 symbols (85 ms) + +ATU-C transmit DMT symbol + +Superframe (SPF#0) = 69 symbols (17 ms) + +SPF#1 + +SPF#2 + +SPF#3 + +SPF#4 + +F F F F N N N N N N F F S S S N F I F F N S + +Sliding window + +FEXTR duration + +T1533730-99 + +1 symbol = 246 $\mu$ s (272 samples) + +- I Inverse synch symbol +- S NEXTR synch symbol +- F Symbol using Bitmap-FR (FEXTR symbol bitmap) +- N Symbol using Bitmap-NR (NEXTR symbol bitmap) +- S FEXTR synch symbol + +The diagram illustrates the downstream hyperframe structure. At the top, at point B, 5 superframes (340 frames) are shown. One superframe consists of 68 frames (17 ms), and one frame lasts 250 μs. These frames pass through a rate converter. At point U-C, including the synch symbol, the timing is shown with TC#0 (2.5 ms), TC#27, and TC#33. The TTRC signal is shown as a square wave. ATU-R crosstalk (FEXT and NEXT) is indicated. The hyperframe consists of 345 symbols (85 ms). The ATU-C transmit DMT symbol is shown as a sequence of superframes: SPF#0 (69 symbols, 17 ms), SPF#1, SPF#2, SPF#3, and SPF#4. The symbol sequence for SPF#0 is: F F F F N N N N N N F F S S S N F I F F N S. A sliding window is shown over the first few symbols. The FEXTR duration is indicated. A legend defines the symbol types: I (Inverse synch symbol), S (NEXTR synch symbol), F (Symbol using Bitmap-FR), N (Symbol using Bitmap-NR), and S (FEXTR synch symbol). One symbol lasts 246 μs (272 samples). The diagram is labeled T1533730-99. + +Diagram of Hyperframe structure for downstream showing timing and symbol sequences. + +**Figure C.7/G.992.2 – Hyperframe structure for downstream** + +![Diagram of Hyperframe structure for upstream showing timing and symbol sequences at points B and U-R.](4ef412e08808c40e0beb7808d36b9379_img.jpg) + +(point B) + +5 superframes (= 340 frames) + +1 superframe = 68 frames (17 ms) + +1 frame = 250 $\mu$ s + +Rate converter + +(point U-R, including synch symbol) + +TC#0 (2.5 ms) + +TC#6 + +TC#33 + +TTRR + +ATU-C crosstalk + +NEXT + +FEXT + +Hyperframe = 345 symbols (85 ms) + +ATU-R transmit DMT symbol + +Superframe (SPF#0) = 69 symbols (17 ms) + +SPF#1 + +SPF#2 + +SPF#3 + +SPF#4 + +N N N N N F F F F N N N + +N F F I F N S S S S + +Sliding window + +FEXTC duration + +1 symbol = 246 $\mu$ s (68 samples) + +T1533740-99 + +- I Inverse synch symbol +- S NEXTC synch symbol +- F Symbol using Bitmap-FC (FEXTC symbol bitmap) +- N Symbol using Bitmap-NC (NEXTC symbol bitmap) +- S FEXTC synch symbol + +The diagram illustrates the upstream data flow and timing. At point B, 5 superframes (340 frames) are shown, with 1 superframe containing 68 frames (17 ms) and 1 frame lasting 250 μs. These frames pass through a rate converter. At point U-R, the timing is shown in terms of Transmission Cycles (TC#0, TC#6, TC#33) and a Hyperframe (345 symbols, 85 ms). The TTRR signal is shown as a square wave. ATU-C crosstalk (NEXT and FEXT) is indicated. The ATU-R transmit DMT symbol sequence is shown for Superframe 0 (SPF#0) and subsequent superframes (SPF#1 to SPF#4). SPF#0 consists of 69 symbols (17 ms) with a sequence of N, F, N. A sliding window is shown over the first few symbols. SPF#1 to SPF#4 show a sequence of N, F, I, F, N, S, S, S, S. The FEXTC duration is indicated. A legend defines the symbol types: I (Inverse synch symbol), S (NEXTC synch symbol), F (Symbol using Bitmap-FC), N (Symbol using Bitmap-NC), and S (FEXTC synch symbol). The diagram is labeled T1533740-99. + +Diagram of Hyperframe structure for upstream showing timing and symbol sequences at points B and U-R. + +**Figure C.8/G.992.2 – Hyperframe structure for upstream** + +![A grid diagram showing symbol patterns in a hyperframe with cyclic prefix for downstream. The grid has 34 rows (0-33) and 12 columns. Symbols are numbered 0-343. Special symbols include ISS (Inverse synch), SS (FEXT_R and NEXT_R synch), and data symbols (FEXT_R and NEXT_R). A vertical dashed line at column 5 separates the cyclic prefix from the main data. TTR_C is indicated at the top left.](85654cf9ade709ea02f5e9929ff8671b_img.jpg) + +TTRC + +| | | | | | | | | | | | | +|----|-----|------------|-----|-----------|-----|-----------|-----|-----|-----------|-----|-----------| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | | +| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | | +| 1 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | | +| 2 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | | +| 3 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | +| 4 | | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | +| 5 | | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | +| 6 | | 61 | 62 | 63 | 64 | 65 | 66 | 67 | SS | 69 | 70 | +| 7 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | | +| 8 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | | +| 9 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | +| 10 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | +| 11 | | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | +| 12 | | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | +| 13 | 132 | 133 | 134 | 135 | 136 | SS | 138 | 139 | 140 | 141 | | +| 14 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | | +| 15 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | | +| 16 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | +| 17 | | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | +| 18 | | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | +| 19 | | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | +| 20 | 203 | 204 | 205 | SS | 207 | 208 | 209 | 210 | 211 | 212 | | +| 21 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | | +| 22 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | | +| 23 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | +| 24 | | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | +| 25 | | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | +| 26 | | 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | 273 | +| 27 | 274 | ISS | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | | +| 28 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | | +| 29 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | | +| 30 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | +| 31 | | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | +| 32 | | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | +| 33 | | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | SS | + +T1535240-00 + +**ISS** Inverse synch symbol    +**SS** FEXTR Synch symbol    +**SS** NEXTR Synch symbol + +FEXTR Data symbol    + NEXTR Data symbol + +A grid diagram showing symbol patterns in a hyperframe with cyclic prefix for downstream. The grid has 34 rows (0-33) and 12 columns. Symbols are numbered 0-343. Special symbols include ISS (Inverse synch), SS (FEXT\_R and NEXT\_R synch), and data symbols (FEXT\_R and NEXT\_R). A vertical dashed line at column 5 separates the cyclic prefix from the main data. TTR\_C is indicated at the top left. + +Figure C.9/G.992.2 – Symbol pattern in a hyperframe with cyclic prefix – Downstream + +![A grid showing the symbol pattern in a hyperframe with cyclic prefix for Upstream. The grid has 34 rows (0-33) and 11 columns. Rows 0-4 are marked as TTR_R. The grid contains numbered cells (0-343) and special symbols: ISS (Inverse synch symbol), SS (FEXT_C Synch symbol), and SS (NEXT_C Synch symbol). Shaded cells represent FEXT_C Data symbols, and white cells represent NEXT_C Data symbols. Vertical dashed lines divide the grid into segments. A label 'T1536250-00' is at the bottom right of the grid.](5c2fb18df09421d12f6ba9370b90d925_img.jpg) + +T1536250-00 + +ISS Inverse synch symbol + +FEXTC Data symbol + +SS FEXTC Synch symbol + +SS NEXTC Synch symbol + +NEXTC Data symbol + +A grid showing the symbol pattern in a hyperframe with cyclic prefix for Upstream. The grid has 34 rows (0-33) and 11 columns. Rows 0-4 are marked as TTR\_R. The grid contains numbered cells (0-343) and special symbols: ISS (Inverse synch symbol), SS (FEXT\_C Synch symbol), and SS (NEXT\_C Synch symbol). Shaded cells represent FEXT\_C Data symbols, and white cells represent NEXT\_C Data symbols. Vertical dashed lines divide the grid into segments. A label 'T1536250-00' is at the bottom right of the grid. + +**Figure C.10/G.992.2 – Symbol pattern in a hyperframe with cyclic prefix – Upstream** + +### C.5.3 Modulation (pertains to 7.10) + +#### C.5.3.1 Inverse Synchronization Symbol (new) + +Except for the pilot tone, the Inverse Synchronization symbol shall be generated from a tone-by-tone 180-degree phase reversal of Synchronization symbol (i.e. + maps to -, and - maps to +, for each of the 4-QAM signal constellation). + +### C.5.3.2 Gain scaling of synchronization symbol + +At Initialization, the sync symbol reference transmit PSD level shall be set at the reference PSD level $+10\log(g_{\text{sync}}^2)$ dBm/Hz, with $g_{\text{sync}}^2$ defined as the average $g_i^2$ value over the used (i.e. $b_i > 0$ ) subcarriers in the NEXT or FEXT bitmap, whichever results in the highest average gain. The sync symbol reference transmit PSD shall not be updated with used subcarrier gain changes during SHOWTIME. + +### C.5.4 Transmitter spectral mask (replaces 7.12.3) + +The spectral mask of this annex shall use the same masks as Annex A or Annex B. When C-MSG1 bit 16 is 0b, the PSD mask specified in Annex A shall be used. When C-MSG1 bit 16 is 1, the PSD mask specified in Annex B shall be used. + +### C.5.5 Dual Bitmap (new) + +The Dual Bitmap method has individual bit rates under the FEXT and NEXT noise, and this needs an additional bit and gain table, $\{b_i, g_i\}$ . The dual bitmaps are switched synchronized with the sliding window pattern of NEXT/FEXT symbols. + +### C.5.6 Rate Converter (new) + +The output of the interleaver is input to the rate converter. The rate converter buffering changes the data frame boundaries between the reference points B and C according to Bitmap-FR/C, Bitmap-NR/C and the Sliding Window. However for the difference of the data rates between the reference points B and C, and to make the bit rate to be a multiple of 32 kbit/s, the dummy bits are inserted at the end of the hyperframe. The number of the dummy bits shall be: + +$$\# \text{dummy}_R = (f_R \times 126 + n_R \times 214) - (t_R \times 340) \quad \text{for downstream data}$$ + +$$\# \text{dummy}_C = (f_C \times 126 + n_C \times 214) - (t_C \times 340) \quad \text{for upstream data}$$ + +where $t_R$ is the number of allocated bits in one frame at the reference point B in ATU-C transmitter, $f_R$ and $n_R$ are the numbers of bits in Bitmap-FR and Bitmap-NR, respectively. Similarly, where $t_C$ is the number of allocated bits in one frame at the reference point B in ATU-R transmitter, $f_C$ and $n_C$ are the numbers of bits in Bitmap-FC and Bitmap-NC, respectively. During FEXT Bitmap mode, $n_R$ and $n_C$ are zero. + +At the receiver, the inserted dummy bits shall be removed. + +The receiver shall determine Bitmap-FR/C and Bitmap-NR/C so that the number of dummy bits is less than 126 in initialization sequence. + +### C.5.7 FEXT Bitmap (new) + +The FEXT Bitmap mode uses the Dual Bitmap technique (see C.5.5) only during FEXT. When Bitmap-NR and Bitmap-NC are disabled (see Table 11-i/G.994.1), the ATU-C shall transmit only the pilot tone as NEXTR symbol and the ATU-R shall not transmit any signal as NEXTC symbol (see Figures C.7 and C.8). + +The Dual versus FEXT bit mapping mode is selected during G.994.1 using bit "DBM" (see 11.2 and 11.3). + +## C.6 aoc on-line adaptation and reconfiguration (pertains to clause 9) + +### C.6.1 Bit swap request message encoding (replaces 9.2.4) + +This message tells the transmitter which subcarriers are to be modified. The format of the request is shown in Table C.1. + +**Table C.1/G.992.2 – Format of the bit swap request message** + +| Message header | Message field 1-4 | | | +|--------------------------------------|-------------------------|---------------------|------------------------------| +| {11111111 b }
(8 bits) | Bitmap index
(1 bit) | Command
(7 bits) | Subcarrier index
(8 bits) | + +The request shall comprise nine bytes as follows: + +- An aoc message header consisting of eight binary ones. +- Message fields 1-4, each of which each consists of a one-bit bitmap index, a seven-bit command followed by a related eight-bit subcarrier index. One-bit bitmap index and valid seven-bit commands for the bit swap message shall be as shown in Table C.2. In Table C.2, the MSB for the bit swap request command represents the bitmap index. In the Bitmap index, 0 indicates Bitmap $F_R$ , and 1b indicates $N_R$ for downstream data. Similarly, 0 indicates Bitmap $F_C$ and 1b indicates $N_C$ for upstream data. The eight-bit subcarrier index is counted from low to high frequencies with the lowest frequency subcarrier having the number zero. The subcarrier index zero shall not be used. +- The bit swap between FEXTC/R symbols and NEXTC/R symbols is not allowed. + +**Table C.2/G.992.2 – Bit swap request command** + +| Value
(8 bit) | Interpretation | +|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| +| y0000000 b | Do nothing | +| y0000001 b | Increase the number of allocated bits by one | +| y0000010 b | Decrease the number of allocated bits by one | +| y0000011 b | Increase the transmitted power by 1 dB | +| y0000100 b | Increase the transmitted power by 2 dB | +| y0000101 b | Increase the transmitted power by 3 dB | +| y0000110 b | Reduce the transmitted power by 1 dB | +| y0000111 b | Reduce the transmitted power by 2 dB | +| y0001xxx b | Reserved for vendor discretionary commands | +| NOTE – y is "0 b " for FEXT C/R symbols, and "1 b " for NEXT C/R symbols of the Sliding Window. | | + +To avoid $g_i$ divergence between ATU-C and ATU-R after several bit swaps, for a $g_i$ update of $\Delta$ dB the new $g_i$ value should be given by: + +$$g_i' = (1/512) \times \text{round}(512 \times g_i \times 10 \exp(\Delta/20))$$ + +### C.6.2 Extended bit swap request message encoding (supplements 9.2.5) + +The format of the extended bit swap request is shown in Table C.3. + +**Table C.3/G.992.2 – Format of the bit swap request message** + +| Message header | Message field 1-6 | | | +|--------------------------------------|-------------------------|---------------------|------------------------------| +| {11111100 b }
(8 bits) | Bitmap index
(1 bit) | Command
(7 bits) | Subcarrier index
(8 bits) | + +In the same manner as the bit swap request, each of the message fields of the extended bit swap request consists of a one-bit bitmap index, a seven-bit command followed by a related eight-bit subcarrier index. + +### C.6.3 Bit swap acknowledge message encoding (supplements 9.2.6) + +The bit swap superframe counter number shall only indicate the last superframe (SPF#4) of a hyperframe. + +The new bit and/or transmit power table(s) shall then take effect starting from the first frame (frame 0) of SPF#0 of a hyperframe. + +If the bit swap superframe counter number contained in the received bit swap acknowledge message does not indicate SPF#4, then the new table(s) shall take effect starting from frame 0 of SPF#0 of the next hyperframe. + +## C.7 In-service performance monitoring and surveillance (pertains to clause 10) + +### C.7.1 ADSL line related primitives (pertains to 10.1) + +#### C.7.1.1 ADSL line related near-end defects (supplements 10.1.3) + +Two near-end defects are defined: + +- *Loss of signal (LOS)*: ADSL power shall be measured only in the FEXTC duration at ATU-C, or only in the FEXTR duration at ATU-R. +- *Severely Errored Frame (SEF)*: A SEF defect occurs when the content of two consecutively received ADSL synchronization symbols in the FEXTC duration at ATU-C, or in the FEXTR duration at ATU-R, does not correlate with the expected content over a subset of the tones. A SEF defect terminates when the content of two consecutively received ADSL synchronization symbols in the FEXTC duration at ATU-C, or in the FEXTR duration at ATU-R, correlate with the expected contents over the same subset. The correlation method, the selected subset of tones, and the threshold for declaring these defect conditions are implementation discretionary. + +#### C.7.1.2 ADSL line related far-end defects (supplements 10.1.4) + +*Far-end Loss of signal (LOS)*: The ADSL power shall be measured only in the FEXTC duration at ATU-C, or only in the FEXTR duration at ATU-R. + +## C.7.2 Test parameters (supplements 10.4) + +### C.7.2.1 Near-end test parameters (supplements 10.4.1) + +The following near-end test parameters are defined: + +- *Attenuation (ATN)*: The received signal power shall be measured only in the $FEXT_C$ duration at ATU-C, or only in the $FEXT_R$ duration at ATU-R. +- *Signal-to-Noise ratio (SNR)* margin: During the FEXT Bitmap mode, this primitive represents the SNR margin in the $FEXT_C$ duration at ATU-C, or in the $FEXT_R$ duration at ATU-R. + +### C.7.2.2 Far-end test parameters (supplements 10.4.2) + +The following far-end test parameters are defined: + +- *Attenuation (ATN)*: The received signal power shall be measured only in the $FEXT_C$ duration at ATU-C, or only in the $FEXT_R$ duration at ATU-R. +- *Signal-to-Noise ratio (SNR)* margin: During the FEXT Bitmap mode, this primitive represents the SNR margin in the $FEXT_C$ duration at ATU-C, or in the $FEXT_R$ duration at ATU-R. + +## C.8 Initialization + +### C.8.1 Initialization with Hyperframe (new) + +The exchange of messages between ATU-C and ATU-R are performed using $FEXT_C$ and $FEXT_R$ symbols. The initialization sequence has two symbol rates. One is 4.3125 kbaud for the symbol without a cyclic prefix, and the other is $4 \times 69/68$ kbaud for the symbol with a cyclic prefix. 32 TTR cycles have the same period as 345 times 4.3125 kHz DMT symbols, and 34 TTR cycles have the same period as 345 times $4 \times 69/68$ kHz DMT symbols. + +During FEXT Bitmap mode, the ATU-R shall not transmit any signal as the $NEXT_C$ symbols and the ATU-C shall transmit the pilot tone as the $NEXT_R$ symbols except: + +- C-PILOT1 (C-PILOT1A): accompanied by $A_{48}$ signal (see C.8.3.1); +- C-QUIETn: not transmit any signal. + +The ATU-C shall enter C-PILOT1 at the beginning of the hyperframe. The ATU-C transmits information regarding the phase of the $TTR_C$ to ATU-R during C-PILOT1. The ATU-R shall enter R-REVERB1 at the beginning of the hyperframe without cyclic prefix. + +From C-PILOT1 to C-SEGUE1, the following numerical formula gives the information which duration $N_{\text{dmt}}$ -th DMT symbol belongs to (see Figure C.11): + +For ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +$$S = 256 \times N_{\text{dmt}} \bmod 2760$$ + +| | | +|-----------------------------------------|----------------------| +| if { $(S + 255 < a)$ or $(S > a + b)$ } | then $FEXT_R$ symbol | +| else | then $NEXT_R$ symbol | + +where $a = 1243$ , $b = 1461$ + +In order to enter C-RATES1 at the beginning of the hyperframe with cyclic prefix, the number of symbols from C-PILOT1 to C-SEGUE1 shall be a multiple of 345 DMT symbols. + +From R-REVERB1 to R-SEGUE1, the following numerical formula gives the information which duration $N_{\text{dmt}}$ -th DMT symbol belongs to (see Figure C.12): + +For $S = 256 \times N_{\text{dmt}} \bmod 2760$ ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +| | | +|------------------------------------------|-------------------------------| +| if { $(S > a)$ and $(S + 255 < a + b)$ } | then FEXT C symbol | +| else | then NEXT C symbol | + +where $a = 1315$ , $b = 1293$ + +From C-RATES1 to C-SEGUE3, the number of symbols is a multiple of 345 DMT symbols. The following numerical formula gives the information which duration $N_{\text{dmt}}$ -th DMT symbol belongs to. ATU-C transmits the message data in FEXTR symbols (see Figure C.9). + +For ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +$S = 272 \times N_{\text{dmt}} \bmod 2760$ + +| | | +|-----------------------------------------|-------------------------------| +| if { $(S + 271 < a)$ or $(S > a + b)$ } | then FEXT R symbol | +| else | then NEXT R symbol | + +where $a = 1243$ , $b = 1461$ + +The ATU-R enters R-REVERB3 at the beginning of the hyperframe with cyclic prefix, which is extracted from received signal. From R-REVERB3 to R-SEGUE5 the number of symbols is a multiple of 345 DMT symbols. The following numerical formula gives the information which duration $N_{\text{dmt}}$ -th DMT symbol belongs to. ATU-R transmits the message data in FEXTC symbols (see Figure C.10). + +For ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +$S = 272 \times N_{\text{dmt}} \bmod 2760$ + +| | | +|------------------------------------------|-------------------------------| +| if { $(S > a)$ and $(S + 271 < a + b)$ } | then FEXT C symbol | +| else | then NEXT C symbol | + +where $a = 1315$ , $b = 1293$ + +![](c8963539c3bd0eb59ea725eec790dc18_img.jpg) + +TTRC + +| | | | | | | | | | | | | | +|----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | | +| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | | +| 1 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | | +| 2 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | | +| 3 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | | +| 4 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | | +| 5 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | | +| 6 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | | | +| 7 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | | +| 8 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | | +| 9 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | | +| 10 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | | +| 11 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | | | +| 12 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | | +| 13 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | | +| 14 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | | +| 15 | | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | +| 16 | | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | | +| 17 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | | +| 18 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | | +| 19 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | | +| 20 | | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | | +| 21 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | | +| 22 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | | +| 23 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | | +| 24 | | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | +| 25 | | | 270 | 271 | 272 | 273 | 274 | 275 | 276 | 277 | 278 | 279 | +| 26 | 280 | 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | | +| 27 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | | +| 28 | | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | +| 29 | | 313 | 314 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | | +| 30 | 323 | 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | | +| 31 | 334 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | | + +T1535260-00 + +  FEXTR Training symbol        NEXTR Training symbol + +**Figure C.11/G.992.2 – Symbol pattern in a hyperframe without cyclic prefix – Downstream** + +![A grid diagram showing the symbol pattern in a hyperframe without cyclic prefix for Upstream. The grid has 32 rows (0-31) and 11 columns. Rows 0-31 are labeled on the left. Columns are numbered 0-10. The first column (0) contains symbols 0, 11, 22, 32, 43, 54, 65, 75, 86, 97, 108, 119, 129, 140, 151, 162, 173, 183, 194, 205, 216, 226, 239, 248, 259, 270, 280, 291, 302, 313, 323, 334. The second column (1) contains 1, 12, 23, 33, 44, 55, 66, 76, 87, 98, 109, 120, 130, 141, 152, 163, 174, 184, 195, 206, 217, 227, 238, 249, 260, 271, 281, 292, 303, 314, 324, 335. The third column (2) contains 2, 13, 24, 34, 45, 56, 67, 77, 88, 99, 110, 121, 131, 142, 153, 164, 175, 185, 196, 207, 218, 228, 239, 250, 261, 272, 282, 293, 304, 315, 325, 336. The fourth column (3) contains 3, 14, 25, 35, 46, 57, 68, 78, 89, 100, 111, 122, 132, 143, 154, 165, 176, 186, 197, 208, 219, 229, 240, 251, 262, 273, 283, 294, 305, 316, 326, 337. The fifth column (4) contains 4, 15, 26, 36, 47, 58, 69, 79, 90, 101, 112, 123, 133, 144, 155, 166, 177, 187, 198, 209, 220, 230, 241, 252, 263, 274, 284, 295, 306, 317, 327, 338. The sixth column (5) contains 5, 16, 27, 37, 48, 59, 70, 80, 91, 102, 113, 124, 134, 145, 156, 167, 178, 188, 199, 210, 221, 231, 242, 253, 264, 275, 285, 296, 307, 318, 328, 339. The seventh column (6) contains 6, 17, 28, 38, 49, 60, 71, 81, 92, 103, 114, 125, 135, 146, 157, 168, 179, 189, 200, 211, 222, 232, 243, 254, 265, 276, 286, 297, 308, 319, 329, 340. The eighth column (7) contains 7, 18, 29, 39, 50, 61, 72, 82, 93, 104, 115, 126, 136, 147, 158, 169, 180, 190, 201, 212, 223, 233, 244, 255, 266, 277, 287, 298, 309, 320, 330, 341. The ninth column (8) contains 8, 19, 30, 40, 51, 62, 73, 83, 94, 105, 116, 127, 137, 148, 159, 170, 181, 191, 202, 213, 224, 234, 245, 256, 267, 278, 288, 299, 310, 321, 331, 342. The tenth column (9) contains 9, 20, 31, 41, 52, 63, 74, 84, 95, 106, 117, 128, 138, 149, 160, 171, 182, 192, 203, 214, 225, 235, 246, 257, 268, 279, 289, 300, 311, 322, 332, 343. The eleventh column (10) contains 10, 21, 31, 42, 53, 64, 74, 85, 96, 107, 118, 128, 139, 150, 161, 172, 182, 193, 204, 215, 225, 236, 247, 258, 269, 279, 290, 301, 312, 322, 333, 344. A legend at the bottom indicates that grey cells represent FEXT_C Training symbols and white cells represent NEXT_C Training symbols. The diagram is labeled T1535270-00.](203988c6150d338f305f6edcfb6e66a6_img.jpg) + +A grid diagram showing the symbol pattern in a hyperframe without cyclic prefix for Upstream. The grid has 32 rows (0-31) and 11 columns. Rows 0-31 are labeled on the left. Columns are numbered 0-10. The first column (0) contains symbols 0, 11, 22, 32, 43, 54, 65, 75, 86, 97, 108, 119, 129, 140, 151, 162, 173, 183, 194, 205, 216, 226, 239, 248, 259, 270, 280, 291, 302, 313, 323, 334. The second column (1) contains 1, 12, 23, 33, 44, 55, 66, 76, 87, 98, 109, 120, 130, 141, 152, 163, 174, 184, 195, 206, 217, 227, 238, 249, 260, 271, 281, 292, 303, 314, 324, 335. The third column (2) contains 2, 13, 24, 34, 45, 56, 67, 77, 88, 99, 110, 121, 131, 142, 153, 164, 175, 185, 196, 207, 218, 228, 239, 250, 261, 272, 282, 293, 304, 315, 325, 336. The fourth column (3) contains 3, 14, 25, 35, 46, 57, 68, 78, 89, 100, 111, 122, 132, 143, 154, 165, 176, 186, 197, 208, 219, 229, 240, 251, 262, 273, 283, 294, 305, 316, 326, 337. The fifth column (4) contains 4, 15, 26, 36, 47, 58, 69, 79, 90, 101, 112, 123, 133, 144, 155, 166, 177, 187, 198, 209, 220, 230, 241, 252, 263, 274, 284, 295, 306, 317, 327, 338. The sixth column (5) contains 5, 16, 27, 37, 48, 59, 70, 80, 91, 102, 113, 124, 134, 145, 156, 167, 178, 188, 199, 210, 221, 231, 242, 253, 264, 275, 285, 296, 307, 318, 328, 339. The seventh column (6) contains 6, 17, 28, 38, 49, 60, 71, 81, 92, 103, 114, 125, 135, 146, 157, 168, 179, 189, 200, 211, 222, 232, 243, 254, 265, 276, 286, 297, 308, 319, 329, 340. The eighth column (7) contains 7, 18, 29, 39, 50, 61, 72, 82, 93, 104, 115, 126, 136, 147, 158, 169, 180, 190, 201, 212, 223, 233, 244, 255, 266, 277, 287, 298, 309, 320, 330, 341. The ninth column (8) contains 8, 19, 30, 40, 51, 62, 73, 83, 94, 105, 116, 127, 137, 148, 159, 170, 181, 191, 202, 213, 224, 234, 245, 256, 267, 278, 288, 299, 310, 321, 331, 342. The tenth column (9) contains 9, 20, 31, 41, 52, 63, 74, 84, 95, 106, 117, 128, 138, 149, 160, 171, 182, 192, 203, 214, 225, 235, 246, 257, 268, 279, 289, 300, 311, 322, 332, 343. The eleventh column (10) contains 10, 21, 31, 42, 53, 64, 74, 85, 96, 107, 118, 128, 139, 150, 161, 172, 182, 193, 204, 215, 225, 236, 247, 258, 269, 279, 290, 301, 312, 322, 333, 344. A legend at the bottom indicates that grey cells represent FEXT\_C Training symbols and white cells represent NEXT\_C Training symbols. The diagram is labeled T1535270-00. + +Figure C.12/G.992.2 – Symbol pattern in a hyperframe without cyclic prefix – Upstream + +## C.8.2 Escape from Handshake to Fast Retrain (replaces 11.5) + +See Figure C.13. + +### C.8.2.1 C-QUIET-EF1 (replaces 11.5.1) + +C-QUIET-EF1 begins at the termination of G.994.1. The minimum duration of C-QUIET-EF1 is 128 symbols. The maximum duration of C-QUIET-EF1 is 2048 symbols. The ATU-C terminates C-QUIET-EF1 and enters C-RECOV at the beginning of the hyperframe. + +### C.8.2.2 R-QUIET-EF1 (replaces 11.5.2) + +R-QUIET-EF1 begins at the termination of G.994.1. The minimum duration of R-QUIET-EF1 is 128 DMT symbols after the detection of C-RECOV. The ATU-R shall progress to R-RECOV only after it has detected any part of the C-RECOV signal that is needed for reliable detection. The ATU-R enters R-RECOV2 synchronized with the hyperframe after the synchronization of ADC clock with the received C-RECOV signal. + +Time-outs C-TO2, R-TO1, R-TO3 are vendor discretionary. It is advisable to make these duration as short as possible. + +![Timing diagram of Escape to Fast Retrain showing states for ATU-C and ATU-R with durations and transitions.](9ba75f891de20483c291538e38701d96_img.jpg) + +The diagram illustrates the state transitions for ATU-C and ATU-R during the Escape to Fast Retrain process. The states are arranged vertically for each unit, with horizontal arrows indicating transitions and durations. + +- ATU-C States:** + - G.994.1 + - C-QUIET-EF1 (Duration: $128 \leq, \leq 2048$ ) + - C-RECOV (Duration: $= 345n + 65$ where $0 \leq n \leq 45$ ) + - C-REVERB-FR1 (Duration: $\leq C-TO2$ ) + - C-PILOT-FR1 +- ATU-R States:** + - G.994.1 + - R-QUIET-EF1 (Duration: $\leq 15\,500$ ) + - R-RECOV (Duration: $\leq R-TO1$ ) + - R-RECOV2 (Duration: $\leq R-TO3$ ) + - R-REVERB-FR1 + +**Transitions and Timing:** + +- ATU-C transitions from G.994.1 to C-QUIET-EF1. +- ATU-C transitions from C-QUIET-EF1 to C-RECOV at the "Beginning of hyperframe". +- ATU-R transitions from G.994.1 to R-QUIET-EF1. +- ATU-R transitions from R-QUIET-EF1 to R-RECOV after a duration of $128 \leq, \leq R-T1$ . +- ATU-R transitions from R-RECOV to R-RECOV2 after a duration of $= 65$ . +- ATU-R transitions from R-RECOV2 to R-REVERB-FR1 at the "Beginning of hyperframe" (synchronized with ATU-C). +- ATU-C transitions from C-RECOV to C-REVERB-FR1 after a duration of $= 280 + 345n$ where $n \geq 0$ . +- ATU-C transitions from C-REVERB-FR1 to C-PILOT-FR1 after a duration of $= 32$ . + +T1533750-99 + +Timing diagram of Escape to Fast Retrain showing states for ATU-C and ATU-R with durations and transitions. + +Figure C.13/G.992.2 – Timing diagram of Escape to Fast Retrain + +### C.8.3 Transceiver training – ATU-C (supplements 11.7) + +During transceiver training from C-REVERB1 to C-SEGUE1 except C-PILOTn and C-QUIETn, the ATU-C shall transmit both FEXTR and NEXTR symbols when Bitmap-NR is enabled (Dual Bitmap mode), and shall not transmit NEXTR symbols except the pilot tone when Bitmap-NR is disabled (FEXT Bitmap mode). The duration of each state is defined in Figure C.18. + +#### C.8.3.1 C-PILOT1 (supplements 11.7.2) + +The ATU-C shall start its NSWF counter immediately after entering C-PILOT1, and then increment the NSWF counter with modulo 345 from 0 when it transmits each DMT symbol. According to the sliding window function and this counter, the ATU-C decides to transmit all of the subsequent symbols in either FEXTR or NEXTR symbols (see Figures C.11 and C.9). + +C-PILOT1 has two subcarriers. One is the pilot tone as a single frequency sinusoid at 276 kHz (see 11.7.2). + +A second carrier ( $A_{48}$ : 48-th carrier) is used to transmit $\text{NEXT}_R/\text{FEXT}_R$ information. The ATU-R can detect the phase information of the $\text{TTR}_C$ from the $A_{48}$ signal. The constellation encoding of the 48-th carrier with 2-bit constellation shall be as the follows: + +$(+, +)$ ; indicates a $\text{FEXT}_R$ symbol + +$(+, -)$ ; indicates a $\text{NEXT}_R$ symbol + +**C.8.3.2 C-PILOT1A (supplements 11.7.3)** + +C-PILOT1A has two subcarriers and it is the same transmitted signal as C-PILOT1 (see C.8.3.1). + +**C.8.3.3 C-REVERB3 (supplements 11.7.11)** + +In order to synchronize the first symbol of C-RATES1 with the beginning of the hyperframe and to inform the entering timing of C-RATES1 to ATU-R, the first symbol of C-SEGUE1 shall be transmitted inside of the $\text{FEXT}_R$ duration. Therefore, the duration of C-REVERB3 is 3628 DMT symbols (see Figure C.14). + +![Timing diagram showing the sequence of signals: TTR_C, C-REVERB3, C-SEGUE1, C-RATES1, R-SEGUE1, and R-REVERB3. It includes annotations for '20 symbols' and 'time to detect'.](7a39393bfdcab04923e964701df5eb5f_img.jpg) + +The diagram illustrates the timing sequence of various signals. At the top, a square wave labeled $\text{TTR}_C$ is shown. Below it, a horizontal timeline is divided into segments. The first segment is labeled C-REVERB3. The second segment is labeled C-SEGUE1, with a double-headed arrow above it indicating a duration of '20 symbols'. The third segment is labeled C-RATES1. Below the C-SEGUE1 segment, another double-headed arrow labeled 'time to detect' indicates a specific interval. Further down, another timeline shows segments labeled R-SEGUE1 and R-REVERB3. Vertical lines align the boundaries of these segments across the different signal levels. A small code 'T1533760-99' is visible in the bottom right corner of the diagram area. + +Timing diagram showing the sequence of signals: TTR\_C, C-REVERB3, C-SEGUE1, C-RATES1, R-SEGUE1, and R-REVERB3. It includes annotations for '20 symbols' and 'time to detect'. + +**Figure C.14/G.992.2 – Timing diagram of C-SEGUE1 to C-RATES1** + +**C.8.4 Transceiver training – ATU-R (supplements 11.8)** + +During transceiver training from R-REVERB1 to R-SEGUE1 except R-QUIETn, the ATU-R shall transmit both $\text{FEXT}_C$ and $\text{NEXT}_C$ symbols when Bitmap- $N_C$ is enabled (Dual Bitmap mode) and shall not transmit $\text{NEXT}_C$ symbols when Bitmap- $N_C$ is disabled ( $\text{FEXT}$ Bitmap mode). The duration of each state is defined in Figure C.18. + +**C.8.4.1 R-QUIET2 (supplements 11.8.1)** + +The ATU-R enters R-REVERB1 after it completes timing recovery and Hyperframe synchronization from C-PILOT1/C-PILOT1A. + +**C.8.4.2 R-REVERB1 (supplements 11.8.2)** + +The ATU-R shall start its $N_{\text{SWF}}$ counter immediately after entering R-REVERB1, and then increment the $N_{\text{SWF}}$ counter modulo 345 from 0 when it transmits each DMT symbol. The ATU-C and ATU-R shall have the same value since hyperframe alignment between the ATU-C and ATU-R shall be maintained. According to the sliding window and this counter, the ATU-R decides to transmit all of the subsequent symbols in either the $\text{FEXT}_C$ or the $\text{NEXT}_C$ symbol. + +#### **C.8.4.3 R-QUIET3 (replaces 11.8.3)** + +The final symbol of R-QUIET3 accommodates the frame alignment of the transmitter to that of the receiver. It may be shortened by any number of samples. The maximum duration of R-QUIET3 is 6145 DMT symbols. + +#### **C.8.4.4 R-REVERB2 (supplements 11.8.5)** + +After ATU-R detects C-SEGUE1, the ATU-R enters R-SEGUE1. The maximum duration of R-REVERB2 is 3643 DMT symbols. + +### **C.8.5 Channel analysis (ATU-C) (supplements 11.9)** + +The ATU-C shall transmit the $\text{FEXT}_R$ symbols, and shall not transmit the $\text{NEXT}_R$ symbols except the pilot tone from C-RATES1 to C-CRC2. In C-MEDLEY, ATU-C shall transmit both $\text{FEXT}_R$ and $\text{NEXT}_R$ symbols, when Bitmap- $\text{N}_R$ is enabled (Dual Bitmap mode). ATU-C shall not transmit $\text{NEXT}_R$ symbols except pilot tone, when Bitmap- $\text{N}_R$ is disabled ( $\text{FEXT}$ Bitmap mode). The duration of each state is defined in Figure C.18. + +#### **C.8.5.1 C-SEGUE1 (supplements 11.9.1)** + +The duration of C-SEGUE1 is 20 symbols in order that the first symbol of C-SEGUE1 shall be inside of the $\text{FEXT}_R$ duration (see Figure C.14). + +#### **C.8.5.2 C-MEDLEY (supplements 11.9.6)** + +The definition of C-MEDLEY is the same as in 11.9.6, except for the duration of the SNR estimation at ATU-R for the downstream. With the periodical noise of TCM- ISDN, the SNR also changes in the same cycle, as shown in Figure C.15. ATU-C transmits the signal in both of $\text{FEXT}_R$ and $\text{NEXT}_R$ symbols and ATU-R estimates two SNRs from the received $\text{NEXT}_R$ and $\text{FEXT}_R$ symbols, respectively, as defined in Figure C.16. + +The following numerical formula gives the information that received $N_{\text{dmt}}$ -th DMT symbol at ATU-R belongs to: + +For ( $N_{\text{dmt}} = 0, 1, \dots, 344$ ) + +$$S = 272 \times N_{\text{dmt}} \bmod 2760$$ + +if { $(S + 271 < a)$ or $(S > d)$ } then symbol for estimation of $\text{FEXT}_R$ SNR + +if { $(S > b)$ and $(S + 271 < c)$ } then symbol for estimation of $\text{NEXT}_R$ SNR + +where $a = 1243$ , $b = 1403$ , $c = 2613$ , $d = 2704$ + +When Bitmap- $\text{N}_R$ is disabled ( $\text{FEXT}$ Bitmap mode), ATU-C shall transmit only the pilot tone as $\text{NEXT}_R$ symbol. + +![Timing diagram for signal-to-noise ratio estimation showing TTR, crosstalk, and bitmap sequences.](d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg) + +The diagram illustrates the timing for signal-to-noise ratio estimation across four horizontal timelines: + +- TTR:** A square wave signal. +- TCM-ISDN crosstalk at ATU-R receiver:** Shows a sequence of blocks labeled **FEXT** (shaded) and **NEXT** (white). +- TCM-ISDN crosstalk at ATU-C receiver:** Shows a sequence of blocks labeled **NEXT** (white) and **FEXT** (shaded). +- Estimation of signal-to-noise ratio:** A long block labeled **C/R-MEDLEY (49 152 symbols)**. +- Bitmap for downstream / Bitmap for upstream:** Below the medley block, two rows of bitmaps are shown. The first row is **Bitmap for downstream** with segments **Bitmap-NR** and **Bitmap-FR**. The second row is **Bitmap for upstream** with segments **Bitmap-FC** and **Bitmap-NC**. These bitmaps are aligned with the start of the C/R-MEDLEY block. + +A reference label **T1533770-99** is present at the bottom right of the diagram. + +Timing diagram for signal-to-noise ratio estimation showing TTR, crosstalk, and bitmap sequences. + +**Figure C.15/G.992.2 – Estimation of periodic Signal-to-Noise Ratio** + +![Solid gray box White box Hatched box](ab2a5275a42ec52f632cfd5359673118_img.jpg) + +TTRC + +| | | | | | | | | | | | +|----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| +| 0 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | +| 1 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | +| 2 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | +| 3 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | +| 4 | | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | +| 5 | | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | +| 6 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | +| 7 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | +| 8 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | +| 9 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | +| 10 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | +| 11 | | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | +| 12 | | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | +| 13 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | +| 14 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | +| 15 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | +| 16 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | +| 17 | | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | +| 18 | | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | +| 19 | | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | +| 20 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | +| 21 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | +| 22 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | +| 23 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | +| 24 | | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | +| 25 | | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | +| 26 | | 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | +| 27 | 274 | 275 | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | +| 28 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | +| 29 | 294 | 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | +| 30 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | +| 31 | | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | +| 32 | | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | +| 33 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | + +T1535280-00 + +Symbol for estimation of FEXTR S/N + Symbol not used for S/N estimation + Symbol for estimation of NEXTR S/N + +Solid gray box White box Hatched box + +Figure C.16/G.992.2 – Symbol pattern in a hyperframe for S/N estimation – Downstream + +C.8.6 Channel analysis (ATU-R) (supplements 11.10) + +From R-RATES1 to R-CRC2, the ATU-R shall transmit the FEXTC symbols and shall not transmit the NEXTC symbols. In R-SEGUE2 and R-MEDLEY, the ATU-R shall transmit both FEXTC and NEXTC symbols when Bitmap-NC is enabled (Dual Bitmap mode) and shall not transmit NEXTC + +symbols when Bitmap-NC is disabled (FEXT Bitmap mode). The duration of each state is defined in Figure C.18. + +#### **C.8.6.1 R-SEGUE1 (supplements 11.10.1)** + +The maximum duration of R-SEGUE1 is 14 symbols (see Figure C.14). + +#### **C.8.6.2 R-REVERB3 (supplements 11.10.2)** + +The ATU-R shall start R-REVERB3 aligned with the beginning of a Hyperframe. + +#### **C.8.6.3 R-SEGUE2 (supplements 11.10.3)** + +The duration of R-SEGUE2 is 13 symbols. + +#### **C.8.6.4 R-MEDLEY (supplements 11.10.8)** + +The definition of R-MEDLEY is the same as in 11.10.8, except for the duration of the SNR estimation at the ATU-C for the upstream channel. With the periodic noise of TCM- ISDN, the SNR also changes in the same cycle, as shown in Figure C.15. The ATU-R shall transmit the signal in both of FEXTC and NEXTC symbols, and ATU-C shall estimate two SNRs from the received NEXTC and FEXTC symbols, respectively, as defined in Figure C.17. + +The following numerical formula gives the information that received Ndmt-th DMT symbol at ATU-C belongs to: + +For Ndmt = 0, 1, ..., 344 + +$$S = 272 \times N_{\text{dmt}} \bmod 2760$$ + +| | | +|----------------------------------|-----------------------------------------------------| +| if { (S > b) and (S + 271 < c) } | then symbol for estimation of FEXT C SNR | +| if { (S + 271 < a) } | then symbol for estimation of NEXT C SNR | + +where a = 1148, b = 1315, c = 2608 + +When Bitmap-NC is disabled (FEXT Bitmap mode), ATU-R shall not transmit NEXTC symbol. + +![A grid showing symbol patterns for S/N estimation in a hyperframe. The grid has 34 rows (0-33) and 11 columns. Rows 0-33 are labeled TTR_R on the left. Columns are numbered 0-10. Symbols are numbered 0-344. Legend: Gray square = Symbol for estimation of FEXT_C S/N; White square = Symbol not used for S/N estimation; Hatched square = Symbol for estimation of NEXT_C S/N. The pattern repeats every 16 rows. Symbols 0-3, 10-13, 20-23, 30-33, 41-44, 51-54, 61-64, 71-74, 81-84, 91-94, 101-104, 112-115, 122-125, 132-135, 142-145, 152-155, 162-165, 173-176, 183-186, 193-196, 203-206, 213-216, 223-226, 233-236, 244-247, 254-257, 264-267, 274-277, 284-287, 294-297, 304-307, 315-318, 325-328, 335-338 are hatched. Symbols 5-9, 15-19, 25-29, 35-39, 45-49, 55-59, 65-69, 75-79, 85-89, 95-99, 105-109, 116-120, 126-130, 136-140, 146-150, 156-160, 166-170, 177-181, 187-191, 197-201, 207-211, 217-221, 227-231, 237-241, 248-252, 258-262, 268-272, 278-282, 288-292, 298-302, 308-312, 319-323, 329-333, 339-343 are gray. Symbols 1, 2, 3, 11, 12, 13, 21, 22, 23, 31, 32, 33, 41, 42, 43, 51, 52, 53, 61, 62, 63, 71, 72, 73, 81, 82, 83, 91, 92, 93, 101, 102, 103, 112, 113, 114, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 173, 174, 175, 183, 184, 185, 193, 194, 195, 203, 204, 205, 213, 214, 215, 223, 224, 225, 233, 234, 235, 244, 245, 246, 254, 255, 256, 264, 265, 266, 274, 275, 276, 284, 285, 286, 294, 295, 296, 304, 305, 306, 315, 316, 317, 325, 326, 327, 335, 336, 337 are white.](4e6c20042176be3226a98da9c80ff426_img.jpg) + +T1535290-00 + +Symbol for estimation of FEXTC S/N + Symbol not used for S/N estimation + +Symbol for estimation of NEXTC S/N + +A grid showing symbol patterns for S/N estimation in a hyperframe. The grid has 34 rows (0-33) and 11 columns. Rows 0-33 are labeled TTR\_R on the left. Columns are numbered 0-10. Symbols are numbered 0-344. Legend: Gray square = Symbol for estimation of FEXT\_C S/N; White square = Symbol not used for S/N estimation; Hatched square = Symbol for estimation of NEXT\_C S/N. The pattern repeats every 16 rows. Symbols 0-3, 10-13, 20-23, 30-33, 41-44, 51-54, 61-64, 71-74, 81-84, 91-94, 101-104, 112-115, 122-125, 132-135, 142-145, 152-155, 162-165, 173-176, 183-186, 193-196, 203-206, 213-216, 223-226, 233-236, 244-247, 254-257, 264-267, 274-277, 284-287, 294-297, 304-307, 315-318, 325-328, 335-338 are hatched. Symbols 5-9, 15-19, 25-29, 35-39, 45-49, 55-59, 65-69, 75-79, 85-89, 95-99, 105-109, 116-120, 126-130, 136-140, 146-150, 156-160, 166-170, 177-181, 187-191, 197-201, 207-211, 217-221, 227-231, 237-241, 248-252, 258-262, 268-272, 278-282, 288-292, 298-302, 308-312, 319-323, 329-333, 339-343 are gray. Symbols 1, 2, 3, 11, 12, 13, 21, 22, 23, 31, 32, 33, 41, 42, 43, 51, 52, 53, 61, 62, 63, 71, 72, 73, 81, 82, 83, 91, 92, 93, 101, 102, 103, 112, 113, 114, 122, 123, 124, 132, 133, 134, 142, 143, 144, 152, 153, 154, 162, 163, 164, 173, 174, 175, 183, 184, 185, 193, 194, 195, 203, 204, 205, 213, 214, 215, 223, 224, 225, 233, 234, 235, 244, 245, 246, 254, 255, 256, 264, 265, 266, 274, 275, 276, 284, 285, 286, 294, 295, 296, 304, 305, 306, 315, 316, 317, 325, 326, 327, 335, 336, 337 are white. + +**Figure C.17/G.992.2 – Symbol pattern in a hyperframe for S/N estimation – Upstream** + +### C.8.7 Exchange – ATU-C (supplements 11.11) + +During C-RATESn, C-MSGn, C-B&G, and C-CRCn, the ATU-C shall transmit the FEXTR symbol. In the other signals, the ATU-C shall transmit both FEXTR and NEXTR symbols when Bitmap-NR is enabled (Dual Bitmap mode), and shall not transmit the NEXTR symbols except pilot tone when Bitmap-NR is disabled (FEXT Bitmap mode). The duration of each state is defined in Figure C.19. + +![Timing diagram of the initialization sequence (part 1) for ATU-C and ATU-R. The diagram shows a sequence of fields and their durations in samples. ATU-C fields include G.994.1, C-QUIET2, C-PILOT1 (with sub-fields if R-ACK2, C-PILOT1A, C-QUIET3A), C-REVERB1, C-PILOT2, C-ECT, C-REVERB2, R-ACK2 then C-PILOT3 / R-ACK1 then C-QUIET5, C-REVERB3, C-SEGUE1, C-RATES1/C-CRC1 / C-MSG1/C-CRC2, and C-MEDLEY. ATU-R fields include G.994.1, R-QUIET2, R-REVERB1, R-QUIET3, R-ECT, R-REVERB2, R-SEGUE1, R-REVERB3, R-SEGUE2, R-RATES1/R-CRC1 / R-MSG1/R-CRC2, and R-MEDLEY. Timing constraints and notes are provided for various durations.](a76fd8608a1490167e6c1a4ed32b38e6_img.jpg) + +| ATU-C | | ATU-R | | | | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------|-----------|---------------------------------------------------------------------|--| +| G.994.1 | | G.994.1 | | | | | +| $128 \leq, \leq 2048$ | C-QUIET2 | R-QUIET2 | $\leq 15\,500$ | | | | +| (Note 5)
$345n$ |
if R-ACK2
C-PILOT1		 If R-ACK1
C-PILOT1A
C-QUIET3A
| if R-ACK2
C-PILOT1 | If R-ACK1
C-PILOT1A | C-QUIET3A | Beginning of hyperframe
$345n$ $(1 \leq n)$
$\leq 32$
1725 | | +| if R-ACK2
C-PILOT1 | If R-ACK1
C-PILOT1A | | | | | | +| | C-QUIET3A | | | | | | +| (Note 2) 1536 | C-REVERB1 | R-REVERB1 | Beginning of hyperframe
12 477 | | | | +| (Note 5) 9216 | C-PILOT2 | R-QUIET3 | (Note 4) | | | | +| (Note 2) 1536 | C-ECT | | $\geq 6144$
$\leq 6145$ | | | | +| 4608 | C-REVERB2 | Last symbol may be shortened by n samples
R-ECT | 1536 | | | | +| (Note 5) 1536 | R-ACK2 then C-PILOT3
R-ACK1 then C-QUIET5 | | | | | | +| (Note 2) 3628 | C-REVERB3 | R-REVERB2 | $\geq 3634$
$\leq 3643$ | | | | +| 20 | C-SEGUE1 | R-SEGUE1 | $5 \leq, \leq 14$ | | | | +| (Note 1) 2884 | C-RATES1/C-CRC1
C-MSG1/C-CRC2 | Introduction of guard time
R-REVERB3 | $345n - 13$
$(9 \leq n \leq 16)$ | | | | +| (Note 2) 49 152 | C-MEDLEY | $345n + 208$
$(0 \leq n \leq 7)$
R-SEGUE2 | 13 | | | | +| | | R-RATES1/R-CRC1
R-MSG1/R-CRC2 | 1254 (Note 3) | | | | +| | | R-MEDLEY | 49 152 (Note 4) | | | | + +T1533780-99 + +Timing diagram of the initialization sequence (part 1) for ATU-C and ATU-R. The diagram shows a sequence of fields and their durations in samples. ATU-C fields include G.994.1, C-QUIET2, C-PILOT1 (with sub-fields if R-ACK2, C-PILOT1A, C-QUIET3A), C-REVERB1, C-PILOT2, C-ECT, C-REVERB2, R-ACK2 then C-PILOT3 / R-ACK1 then C-QUIET5, C-REVERB3, C-SEGUE1, C-RATES1/C-CRC1 / C-MSG1/C-CRC2, and C-MEDLEY. ATU-R fields include G.994.1, R-QUIET2, R-REVERB1, R-QUIET3, R-ECT, R-REVERB2, R-SEGUE1, R-REVERB3, R-SEGUE2, R-RATES1/R-CRC1 / R-MSG1/R-CRC2, and R-MEDLEY. Timing constraints and notes are provided for various durations. + +**Figure C.18/G.992.2 – Timing diagram of the initialization sequence (part 1)** + +![Timing diagram of the initialization sequence (part 2) showing ATU-C and ATU-R communication. The diagram is divided into two main columns: ATU-C on the left and ATU-R on the right. Vertical arrows indicate time intervals in symbols (n) or seconds. Horizontal arrows show the sequence of messages. ATU-C messages include C-REVERB4, C-SEGUE2, C-RATES-RA/C-CRC-RA1, C-MSG-RA/C-CRC-RA2, C-REVERB-RA, C-SEGUE-RA, C-MSG2/C-CRC-3, C-RATES2/C-CRC4, C-B&G/C-CRC5, C-REVERB5, C-SEGUE3, and SHOWTIME. ATU-R messages include R-MEDLEY, R-REVERB4, R-SEGUE3, R-MSG-RA/R-CRC-RA1, R-RATES-RA/R-CRC-RA2, R-REVERB-RA, R-SEGUE-RA, R-MSG2/R-CRC-3, R-RATES2/R-CRC4, R-REVERB5, R-SEGUE4, R-B&G/R-CRC5, R-REVERB6, R-SEGUE5, and SHOWTIME. Gray shaded areas represent reserved or unused symbol periods. Notes 1, 2, 3, and 4 are referenced at various points.](28e47e64ac18ca4d8924dab65cedc2d8_img.jpg) + +The diagram illustrates the timing sequence for initialization between ATU-C and ATU-R. The vertical axis represents time in symbols (n) or seconds. Horizontal arrows indicate the sequence of messages. ATU-C messages include C-REVERB4, C-SEGUE2, C-RATES-RA/C-CRC-RA1, C-MSG-RA/C-CRC-RA2, C-REVERB-RA, C-SEGUE-RA, C-MSG2/C-CRC-3, C-RATES2/C-CRC4, C-B&G/C-CRC5, C-REVERB5, C-SEGUE3, and SHOWTIME. ATU-R messages include R-MEDLEY, R-REVERB4, R-SEGUE3, R-MSG-RA/R-CRC-RA1, R-RATES-RA/R-CRC-RA2, R-REVERB-RA, R-SEGUE-RA, R-MSG2/R-CRC-3, R-RATES2/R-CRC4, R-REVERB5, R-SEGUE4, R-B&G/R-CRC5, R-REVERB6, R-SEGUE5, and SHOWTIME. Gray shaded areas represent reserved or unused symbol periods. Notes 1, 2, 3, and 4 are referenced at various points. + +Maximum initialization time 26.9 s + +T1533790-99 + +Timing diagram of the initialization sequence (part 2) showing ATU-C and ATU-R communication. The diagram is divided into two main columns: ATU-C on the left and ATU-R on the right. Vertical arrows indicate time intervals in symbols (n) or seconds. Horizontal arrows show the sequence of messages. ATU-C messages include C-REVERB4, C-SEGUE2, C-RATES-RA/C-CRC-RA1, C-MSG-RA/C-CRC-RA2, C-REVERB-RA, C-SEGUE-RA, C-MSG2/C-CRC-3, C-RATES2/C-CRC4, C-B&G/C-CRC5, C-REVERB5, C-SEGUE3, and SHOWTIME. ATU-R messages include R-MEDLEY, R-REVERB4, R-SEGUE3, R-MSG-RA/R-CRC-RA1, R-RATES-RA/R-CRC-RA2, R-REVERB-RA, R-SEGUE-RA, R-MSG2/R-CRC-3, R-RATES2/R-CRC4, R-REVERB5, R-SEGUE4, R-B&G/R-CRC5, R-REVERB6, R-SEGUE5, and SHOWTIME. Gray shaded areas represent reserved or unused symbol periods. Notes 1, 2, 3, and 4 are referenced at various points. + +Figure C.19/G.992.2 – Timing diagram of the initialization sequence (part 2) + +### Notes to Figures C.18 and C.19 + +NOTE 1 – The ATU-C shall transmit the FEXTR symbols, and shall not transmit the NEXTR symbols except pilot tone. + +NOTE 2 – The ATU-C shall transmit both FEXTR and NEXTR symbols, when Bitmap-NR is enabled (Dual Bitmap mode). ATU-C shall not transmit the NEXTR symbols except pilot tone, when Bitmap-NR is disabled (FEXT Bitmap mode). + +NOTE 3 – ATU-R shall transmit the FEXTC symbols, and shall not transmit the NEXTC symbols. + +NOTE 4 – ATU-R shall transmit both FEXTC and NEXTC symbols, when Bitmap-NC is enabled (Dual Bitmap mode). ATU-R shall not transmit NEXTC symbols, when Bitmap-NC is disabled (FEXT Bitmap mode). + +NOTE 5 – ATU-C shall transmit both FEXTR and NEXTR symbols. + +### C.8.7.1 C-MSG2 (supplements to 11.11.9) + +#### C.8.7.1.1 Total number of bits per symbol supported (supplements 11.11.9.4) + +The maximum number of bits per symbol is defined at the reference point B, that is calculated from the FEXTC and NEXTC upstream channel performance. (E.g. if the maximum numbers of bits that can be supported in FEXTC and NEXTC symbols are 111 and 88, {Total number of bits per symbol supported} = (111 × 126 + 88 × 214)/340 = 96). + +The number of symbols per hyperframe is 340. The number of FEXT symbols per hyperframe is 126. The number of NEXT symbols per hyperframe is 214. + +#### C.8.7.2 C-B&G (replaces 11.11.13) + +C-B&G shall be used to transmit to the ATU-R the bits and gains information, Bitmap-FC { $b_1, g_1, b_2, g_2, \dots, b_{31}, g_{31}$ }, and Bitmap-NC { $b_{33}, g_{33}, b_{34}, g_{34}, \dots, b_{63}, g_{63}$ }, that are to be used on the upstream carriers. $b_i$ of Bitmap-FC indicates the number of bits to be coded by ATU-R transmitter onto the $i$ -th upstream carrier in FEXTC symbols; $g_i$ of Bitmap-FC indicates the scale factor, relative to the gain that was used for that carrier during the transmission of R-MEDLEY, that shall be applied to the $i$ -th upstream carrier in FEXTC symbols. Similarly, $b_i$ of Bitmap-NC indicates the number of bits onto the $(i - 32)$ -th upstream carrier in NEXTC symbols; $g_i$ of Bitmap-NC indicates the scale factor that shall be applied to the $(i - 32)$ -th upstream carrier in NEXTC symbols. + +Because no bits or energy will be transmitted at dc or one-half the sampling rate, $b_0, g_0, b_{32}, g_{32}, b_{64},$ and $g_{64}$ are all presumed to be zero and shall not be transmitted. + +The C-B&G information shall be mapped in a 992-bit (124 byte) message $m$ defined by: + +$$m = \{m_{991}, m_{990}, \dots, m_1, m_0\} = \{g_{63}, b_{63}, \dots, g_{33}, b_{33}, g_{31}, b_{31}, \dots, g_1, b_1\},$$ + +with the MSB of $b_i$ and $g_i$ in the higher $m$ index and $m_0$ being transmitted first. The message $m$ shall be transmitted in 124 symbols, using the transmission method as described in 11.11.9. + +When Bitmap-NC is disabled (FEXT Bitmap mode), $b_i$ and $g_i$ of Bitmap-NC shall be set to zero. + +#### C.8.7.3 C-SEGUE3 (supplements 11.11.16) + +The duration of C-SEGUE3 is 18 symbols. Following C-SEGUE-3, ATU-C completes the initialization and enters C-SHOWTIME. In C-SHOWTIME, ATU-C shall transmit the signal using Bitmap-FR and Bitmap-NR with the sliding window. + +### C.8.8 Exchange – ATU-R (supplements 11.12) + +The ATU-R shall transmit only the FEXTC symbols in R-MSGn, R-RATESn, R-B&G, R-CRCn. In other signals, the ATU-R shall transmit both FEXTC and NEXTC symbols when Bitmap-NC is enabled (Dual Bitmap mode) and shall not transmit NEXTC symbols when Bitmap-NC is disabled (FEXT Bitmap mode). The duration of each state is defined in Figure C.19. + +### C.8.8.1 R-MSG-RA (related to 11.12.2) + +#### C.8.8.1.1 Total number of bits supported ( $B_{\max}$ ) (replaces 11.12.2.7) + +This parameter shall be defined as in R-MSG2; see C.8.8.2. + +### C.8.8.2 R-MSG2 (supplements 11.12.8) + +#### C.8.8.2.1 Total number of bits per symbol supported (supplements 11.12.8.4) + +The maximum number of bits per symbol is defined at the reference point B, that is calculated from the $\text{FEXT}_R$ and $\text{NEXT}_R$ downstream channel performance. + +### C.8.8.3 R-B&G (replaces 11.12.14) + +The purpose of R-B&G is to transmit to ATU-C the bits and gains information, $\text{Bitmap-F}_R \{b_1, g_1, b_2, g_2, \dots, b_{255}, g_{255}\}$ , and $\text{Bitmap-N}_R \{b_{257}, g_{257}, b_{258}, g_{258}, \dots, b_{511}, g_{511}\}$ , to be used on the downstream subcarriers. $b_i$ of $\text{Bitmap-F}_R$ indicates the number of bits to be coded by ATU-C transmitter onto the $i$ -th downstream subcarrier in $\text{FEXT}_R$ symbols; $g_i$ of $\text{Bitmap-F}_R$ indicates the scale factor that shall be applied to the $i$ -th downstream subcarrier in $\text{FEXT}_R$ symbols, relative to the gain that was used for that carrier during the transmission of C-MEDLEY. Similarly, $b_i$ of $\text{Bitmap-N}_R$ indicates the number of bits onto the $(i - 256)$ -th downstream carrier in $\text{NEXT}_R$ symbols; $g_i$ of $\text{Bitmap-N}_R$ indicates the scale factor that shall be applied to the $(i - 256)$ -th downstream carrier in $\text{NEXT}_R$ symbols. Because no bits or energy will be transmitted at DC or one-half the sampling rate, $b_0, g_0, b_{256}, g_{256}, b_{512}$ , and $g_{512}$ are all presumed to be zero, and are not transmitted. Because subcarrier 64 is reserved as the pilot tone, $b_{64}$ and $b_{320}$ , shall be set to 0b, $g_{64}$ and $g_{320}$ shall be set to $g_{\text{sync}}$ . The value $g_{\text{sync}}$ represents the gain scaling applied to the sync symbol. + +The R-B&G information shall be mapped in a 8160-bit (1020 byte) message $m$ defined by: + +$$m = \{m_{8159}, m_{8158}, \dots, m_1, m_0\} = \{g_{511}, b_{511}, \dots, g_{257}, b_{257}, g_{255}, b_{255}, \dots, g_1, b_1\},$$ + +with the MSB of $b_i$ and $g_i$ in the higher $m$ index and $m_0$ being transmitted first. The message $m$ shall be transmitted in 1020 symbols, using the transmission method as described in 11.12.8. + +Values of $b_i$ and $g_i$ shall be set to 0 for values of $127 < i < 256$ , and $383 < i < 512$ . + +When $\text{Bitmap-N}_R$ is disabled ( $\text{FEXT}$ Bitmap mode), $b_i$ and $g_i$ of $\text{Bitmap-N}_R$ shall be set to zero. + +### C.8.8.4 R-SEGUE5 (replaces 11.12.17) + +The duration of R-SEGUE5 is 13 symbols. Following R-SEGUE-5, ATU-R completes the initialization and enters R-SHOWTIME. In R-SHOWTIME, ATU-R shall transmit the signal using $\text{Bitmap-F}_C$ and $\text{Bitmap-N}_C$ with the sliding window. + +## C.9 Fast retraining (supplements clause 12) + +The definition of Fast Retrain procedure is the same as main body except for the definition of C-RECOV, the introduction of R-RECOV2, and duration of symbols which includes the Sliding Window operation. The definition of C-RECOV and R-RECOV2 are defined in C.9.2. The duration of each state is defined in Figure C.22. + +### **C.9.1 Fast Retrain overview (pertains to 12.1)** + +#### **C.9.1.1 Profile requirement (supplements 12.1.1)** + +B&G tables of profile contain both Bitmap-FR and Bitmap-NR in the ATU-C, and both Bitmap-FC and Bitmap-NC in the ATU-R. + +### **C.9.2 Definition of Fast Retrain signals (supplements 12.2)** + +C-RECOV signal is changed and the signal R-RECOV2 is added. + +- C-RECOV consists of a single tone signal corresponding to subcarrier 68 without cyclic prefix accompanied by the C-PILOT1 signal which contains subcarrier 64 and 48 (see C.8.3.1). ATU-C shall transmit the signal which includes 64, 68 and 48th subcarrier as FEXTR symbol, and shall transmit the signal which includes 64 and 48th subcarrier as NEXTR symbol. This signal allows the ATU-R to perform or maintain timing recovery and hyperframe synchronization. +- R-RECOV2 is single tone signal corresponding to subcarrier 22 without cyclic prefix. The PSD level to be used for R-RECOV2 shall be the same as R-RECOV. ATU-R transmits R-RECOV2 both FEXTR and NEXTR symbols. + +### **C.9.3 Fast Retrain procedure (supplements 12.3)** + +#### **C.9.3.1 ATU-C initiated from SHOWTIME (supplements 12.3.1)** + +Figures C.20 and C.21 show the timing diagrams for the Fast Retrain with the ATU-C initiating the procedure. + +Time-outs C-TO2, C-TO3, R-TO1, R-TO3 are vendor discretionary. It is advisable to make these durations as short as possible. + +The following issues are different from main body and transition state timing is similar to initialization (see C.8). + +- The ATU-C shall enter C-RECOV at the beginning of the hyperframe without cyclic prefix. +- The ATU-C shall transmit the pilot tone as the NEXTR symbols in C-MSG-n and C-CRC-n. +- When Bitmap-NR is disabled (FEXT Bitmap mode) in preceding SHOWTIME, the ATU-C shall transmit the pilot tone as NEXTR symbols, except C-RECOV and C-QUIET-FR. +- The ATU-C enters C-MEDLEY-FR at the beginning of the hyperframe with cyclic prefix. +- The ATU-R shall enter R-RECOV2 at the beginning of the hyperframe without cyclic prefix after the synchronization of ADC clock with the received C-RECOV signal. Last symbol of R-RECOV may be shortened. +- The ATU-R shall not transmit any signal as the NEXTC symbols in R-MSG-n and R-CRC-n. +- When Bitmap-NC is disabled (FEXT Bitmap mode) in preceding SHOWTIME, the ATU-R shall not transmit the NEXTC symbols, except R-RECOV and R-RECOV2. +- The ATU-R enters R-MEDLEY-FR at the beginning of the hyperframe with cyclic prefix. + +#### **C.9.3.2 ATU-R initiated from SHOWTIME (supplements 12.3.2)** + +Figure C.22 shows the timing diagram for the Fast Retrain with the ATU-R initiating the procedure. + +Time-outs C-TO2, R-TO2, R-TO3 are vendor discretionary. It is advisable to make these durations as short as possible. + +![Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 1).](3eb2af31c2e61e2595c8440d726f5d4e_img.jpg) + +The diagram illustrates the timing sequence for the Fast Retrain procedure, initiated by the ATU-C from the SHOWTIME state. It shows the exchange of various frames between the ATU-C and ATU-R over time, with specific durations and timing constraints indicated. + +**ATU-C Sequence:** + +- C-SHOWTIME** (Starts at the beginning of a hyperframe) +- C-RECOV** (Duration: $345n + 65$ samples, where $0 \leq n \leq 33$ ) +- C-REVERB-FR1** (Duration: $\leq C-TO2$ ) +- C-PILOT-FR1** (Duration: $\leq C-TO3$ ) +- C-REVERB-FR2** (Duration: 64 samples) +- C-SEGUE-FR1** (Duration: 10 samples) +- C-MSG-FR1 / C-CRC-FR1** (Duration: 78 samples) +- C-REVERB-FR3** (Duration: 675 samples) +- C-PILOT-FR2** (Duration: 3711 samples) +- C-REVERB-FR4** (Duration: 40 samples) +- C-ECT-FR** (Duration: 1536 samples) +- C-REVERB-FR5** (Duration: 3637 samples) +- R-ACK2 then C-PILOT-FR3 / R-ACK1 then C-QUIET-FR** (Duration: 1536 samples) +- C-REVERB-FR6** (Duration: 625 samples) +- C-SEGUE-FR2** (Duration: 20 samples) +- C-MEDLEY-FR** (Duration: 2760 samples) + +**ATU-R Sequence:** + +- R-SHOWTIME** (Received from ATU-C) +- R-RECOV** (Received from ATU-C) +- R-RECOV2** (Duration: $280 + 345n$ samples, where $n \geq 0$ ) +- R-REVERB-FR1** (Duration: 601 samples) +- R-SEGUE-FR1** (Duration: 10 samples) +- R-LINE PROBE** (Vendor discr., Duration: 1801 samples) +- R-REVERB-FR2** (Duration: 11 samples) +- R-SEGUE-FR2** (Duration: 10 samples) +- R-MSG-FR1 / R-CRC-FR1** (Duration: 87 samples) +- R-QUIET-FR1** (Duration: 226 samples) +- R-REVERB-FR3** (Duration: 4390 samples) +- R-QUIET-FR2** (Duration: 1536 samples) +- R-REVERB-FR4** (Duration: 32 samples) +- R-ECT-FR** (Duration: 1536 samples) +- R-REVERB-FR5** (Duration: $631 \leq, \leq 640$ samples) +- R-SEGUE-FR3** (Duration: $5 \leq, \leq 14$ samples) +- R-MEDLEY-FR** (Duration: 2760 samples) + +**Timing and Control Annotations:** + +- (Note 2)**: Beginning of hyperframe (ATU-C side) +- (Note 5)**: Fast Retrain Request (ATU-C side) +- (Note 2)**: Channel measurement (ATU-C side) +- (Note 1)**: Message for Fast Retrain truncate (ATU-C side) +- (Note 2)**: Introduction ATU-C Tx power (ATU-C side) +- (Note 2)**: Retrain ATU-C equalizer (ATU-C side) +- (Note 2)**: Retrain ATU-C echo canceller (ATU-C side) +- (Note 4)**: Retrain ATU-R timing recovery and hyperframe synchronization (ATU-R side) +- (Note 6)**: Fast Retrain request (ATU-R side) +- (Note 4)**: Channel measurement (ATU-R side) +- (Note 3)**: Message for ATU-C Tx power (ATU-R side) +- (Note 4)**: Introduction ATU-R Tx power (ATU-R side) +- (Note 4)**: Retrain ATU-R equalizer (ATU-R side) +- (Note 4)**: Retrain ATU-R echo canceller (ATU-R side) +- Other annotations**: R-T1, Beginning of hyperframe (ATU-R side), Last symbol may be shortened by n samples, Introduction of cyclic prefix (ATU-R side), Retrain AGC (ATU-R side). + +Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 1). + +**Figure C.20/G.992.2 – Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 1)** + +![Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 2).](defe20e5056d0c3552de2d50ce88c5cb_img.jpg) + +The diagram illustrates the timing sequence for a Fast Retrain procedure between an ATU-C (Client) and an ATU-R (Remote). The sequence starts with the ATU-C in the C-SHOWTIME state. Upon receiving a signal (Note 2), it transitions through a series of states: C-SEGUE-FR4 (18), C-REVERB-FR8 (394), C-MSG-FR2/C-CRC-FR2 (83), C-SEGUE-FR3 (10), C-REVERB-FR7 (185), and C-MEDLEY-FR. A transition arrow labeled 'Resume showtime with restart of superframe counter' leads to the ATU-R. The ATU-R then transitions through R-SHOWTIME, R-SEGUE-FR5 (13), R-REVERB-FR7 (566), R-MSG-FR2/R-CRC-FR2 (84), R-SEGUE-FR4 (10), R-REVERB-FR6 (17), and finally R-MEDLEY-FR. Vertical lines with arrows indicate the flow of time and signaling between the two units. Notes 1, 2, 3, and 4 are referenced throughout the sequence. + +| ATU-C State | Duration | Notes | ATU-R State | Duration | Notes | +|------------------------|----------|----------|------------------------|----------|----------| +| C-MEDLEY-FR | | (Note 2) | R-MEDLEY-FR | | | +| | | | R-REVERB-FR6 | 17 | (Note 4) | +| | | | R-SEGUE-FR4 | 10 | | +| C-REVERB-FR7 | 185 | | R-MSG-FR2
R-CRC-FR2 | 84 | (Note 3) | +| C-SEGUE-FR3 | 10 | | | | | +| C-MSG-FR2
C-CRC-FR2 | 83 | (Note 1) | R-REVERB-FR7 | 566 | (Note 4) | +| C-REVERB-FR8 | 394 | | | | | +| C-SEGUE-FR4 | 18 | | R-SEGUE-FR5 | 13 | | +| C-SHOWTIME | | (Note 2) | R-SHOWTIME | | | + +T1533810-99 + +Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 2). + +**Figure C.21/G.992.2 – Timing diagram of the Fast Retrain procedure, ATU-C initiated from SHOWTIME (part 2)** + +![Timing diagram of the Fast Retraining procedure, ATU-R initiated from SHOWTIME. The diagram shows two sequences of events between ATU-C and ATU-R. The top sequence starts with ATU-C sending a Fast Retrain request (Note 5) at the beginning of a hyperframe. ATU-R responds with R-SHOWTIME, then R-RECOV, R-RECOV2, and R-REVERB-FR1. ATU-C responds with C-SHOWTIME, C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-T1 = 345n + 65, C-RECOV = 345n, C-REVERB-FR1 = 280 + 345n, and C-PILOT-FR1 = 32. The bottom sequence shows ATU-R initiating the retrain from SHOWTIME. ATU-R sends R-RECOV, R-RECOV2, and R-REVERB-. ATU-C responds with C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-RECOV = 345n + 65, C-REVERB-FR1 = 280 + 345n, and C-PILOT-FR1 = 3. Various notes (2, 4, 5, 6) and timing parameters (TO1, TO2, TO3) are indicated.](af4f213abb5ad1891a43425e0d758021_img.jpg) + +Timing diagram of the Fast Retraining procedure, ATU-R initiated from SHOWTIME. The diagram shows two sequences of events between ATU-C and ATU-R. The top sequence starts with ATU-C sending a Fast Retrain request (Note 5) at the beginning of a hyperframe. ATU-R responds with R-SHOWTIME, then R-RECOV, R-RECOV2, and R-REVERB-FR1. ATU-C responds with C-SHOWTIME, C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-T1 = 345n + 65, C-RECOV = 345n, C-REVERB-FR1 = 280 + 345n, and C-PILOT-FR1 = 32. The bottom sequence shows ATU-R initiating the retrain from SHOWTIME. ATU-R sends R-RECOV, R-RECOV2, and R-REVERB-. ATU-C responds with C-RECOV, C-REVERB-FR1, and C-PILOT-FR1. Timing constraints include C-RECOV = 345n + 65, C-REVERB-FR1 = 280 + 345n, and C-PILOT-FR1 = 3. Various notes (2, 4, 5, 6) and timing parameters (TO1, TO2, TO3) are indicated. + +**Figure C.22/G.992.2 – Timing diagram of the Fast Retraining procedure, ATU-R initiated from SHOWTIME** + +### Notes to Figures C.21 and C.22 + +NOTE 1 – ATU-C shall transmit the $FEXT_R$ symbols, and shall not transmit the $NEXT_R$ symbols except pilot tone. + +NOTE 2 – ATU-C shall transmit both $FEXT_R$ and $NEXT_R$ symbols, when Bitmap- $N_R$ is enabled (Dual Bitmap mode). ATU-C shall not transmit the $NEXT_R$ symbols except pilot tone, when Bitmap- $N_R$ is disabled ( $FEXT$ Bitmap mode). + +NOTE 3 – ATU-R shall transmit the $FEXT_C$ symbols, and shall not transmit the $NEXT_C$ symbols. + +NOTE 4 – ATU-R shall transmit both $FEXT_C$ and $NEXT_C$ symbols, when Bitmap- $N_C$ is enabled (Dual bitmap mode). ATU-R shall not transmit $NEXT_C$ symbols, when Bitmap- $N_C$ is disabled ( $FEXT$ Bitmap mode). + +NOTE 5 – ATU-C shall transmit both $FEXT_R$ and $NEXT_R$ symbols. However, the transmission signal is different between $FEXT_R$ and $NEXT_R$ symbol (see C.9.2). + +NOTE 6 – ATU-R shall transmit both $FEXT_C$ and $NEXT_C$ symbols. + +#### **C.9.4 Initiated from L3 or Recommendation G.994.1 (replaces 12.5)** + +A Fast Retrain Procedure initiated from an idle link state or via an Escape from Handshake shall be according to C.9.3.1 or C.9.3.2 except for a longer time duration for R-TO1 or R-TO2 of the R-RECOV signal. This will allow for re-acquisition of loop timing and hyperframe synchronization with the received C-RECOV signal at the ATU-R. + +#### **C.10 Power management (pertains to clause 13)** + +##### **C.10.1 Transition from L0 to L1 (T0d) (pertains to 13.4.2)** + +###### **C.10.1.1 Exchange entry procedure (replaces 13.4.2.1)** + +This subclause defines the Exchange entry procedure. This procedure reuses states, signals, and rules for determining the next state contained within C.8.6 as defined in the following steps. + +- 1) After successful termination of the eoc handshake procedure, the ATU-R shall start R-QUIET-PM at the Hyperframe boundary. R-QUIET-PM is defined as no transmitted signal onto the U-R interface. The ATU-R shall maintain loop timing and Hyperframe synchronization during the R-QUIET-PM signal. +- 2) After the detection of R-QUIET-PM, the ATU-C shall start C-REVERB4 at next 287th symbol (frame 286) of the hyperframe. In this procedure, the duration of C-REVERB4 is $345n - 304$ ( $3 \leq n \leq 9$ ). +- 3) After the detection of C-REVERB4, the ATU-R responds by sending R-REVERB4 at next 37th symbol (frame 36) of the hyperframe. The exchange portion of the initialization procedure defined in C.8.6 shall continue from this point (i.e. the ATU-R shall send R-SEGUE after 296 symbols of R-REVERB4). During R-MSG-RA, the ATU-R shall use the "no options selected" message. The ATU-C implementation shall include a means that blocks the loss of signal defect during exchange entry procedure. + +### **ANNEX D** + +#### **System performance for North America** + +##### **D.1 System performance for North America** + +All test cases specified in this annex shall be used for the main body of this Recommendation and testing shall conform to the following: + +- No power cutback on upstream transmitter. +- Margin = 4 dB. +- BER = $10^{-7}$ . +- Background noise = -140 dBm/Hz. +- Data rates, except where noted, are to be measured in the absence of a customer premises wiring. +- Data rates listed are the net payload data rate. (ATM cell overhead is included within the listed bit rates, but framing, eoc, and RS code overheads are not included within the listed bit rates.) +- For testing purposes, one-way payload transfer delay shall be less than $10 + (S \times D)/4$ ms. +- Loop environmental temperature = 25° C. + +A Recommendation G.992.2 Annex D compliant system (ATU-C and ATU-R) shall meet the following minimum performance requirements: + +### D.1.1 Required test cases + +**Table D.1/G.992.2 – Required test cases** + +| Case # | Loop | Downstream net data rate | Upstream net data rate | Noise | +|--------|------------------------------------------|--------------------------|------------------------|----------------------| +| 1 | Null Loop | 1536 kbit/s | 512 kbit/s | None | +| 2 | T #7 | 1536 kbit/s | 224 kbit/s | 49 Annex A/G.992.2 | +| 3 | T #7 | 1536 kbit/s | 224 kbit/s | 24 DSL | +| 4 | T #13 | 1184 kbit/s | 224 kbit/s | 49 Annex A/G.992.2 | +| 5 | T #13 | 1184 kbit/s | 224 kbit/s | 24 DSL | +| 6 | Shortened T #7 | 1184 kbit/s | 256 kbit/s | 10 HDSL | +| 7 | Shortened T #7 | 512 kbit/s | 512 kbit/s | 5 adjacent binder T1 | +| 8 | T #8 | 256 kbit/s | 96 kbit/s | 24 Annex A/G.992.2 | +| 9 | T #8 | 256 kbit/s | 96 kbit/s | 10 DSL | +| 10 | T #13
In-home wiring model #1 G.996.1 | 768 kbit/s | 192 kbit/s | 49 Annex A/G.992.2 | +| 11 | T #13
In-home wiring model #1 G.996.1 | 768 kbit/s | 192 kbit/s | 24 DSL | + +In addition to the above loops, a Recommendation G.992.2 Annex D compliant system (ATU-C and ATU-R) should meet the following performance points in order to provide extended loop reach. + +### D.1.2 Extended reach cases + +For the extended reach test cases #12 and #13 margin testing shall be performed without the check that the ADSL unit can train at the 4 dB margin level. + +**Table D.2/G.992.2 – Extended reach test cases** + +| Case # | Loop | Downstream net data rate | Upstream net data rate | Noise | +|--------|----------------|--------------------------|------------------------|--------------------| +| 12 | T #1 | 256 kbit/s | 96 kbit/s | 3 Annex A/G.992.2 | +| 13 | T #2 | 256 kbit/s | 96 kbit/s | 24 Annex A/G.992.2 | +| 14 | T #5 | 768 kbit/s | 256 kbit/s | 49 Annex A/G.992.2 | +| 15 | T #5 | 768 kbit/s | 256 kbit/s | 24 DSL | +| 16 | T #9 | 1536 kbit/s | 256 kbit/s | 49 Annex A/G.992.2 | +| 17 | T #9 | 1536 kbit/s | 256 kbit/s | 24 DSL | +| 18 | Shortened T #7 | 1536 kbit/s | 256 kbit/s | 24 HDSL | + +NOTE 1 – A goal of future enhancements of this Recommendation is to make the "Extended Reach Cases" mandatory. + +NOTE 2 – Performance levels do not reflect the effect of customer premise wiring, which is expected to reduce data rate. + +## ANNEX E + +### System performance for Europe + +#### E.1 System performance for Europe + +This annex specifies European performance requirements for this Recommendation over short, medium and long loops without inclusion of premises wiring or phone models. + +The one-way payload transfer delay shall be below $10 + (S \times D)/4$ ms for the ADSL Line (excluding ATM TC). + +The performance points in Table E.1 must be met with a BER of $10^{-7}$ at 6 dB margin. The ATU-C and ATU-R shall be connected directly via the specified loop (no home network or phone model present). + +**Table E.1/G.992.2 – Proposed European required Test Loops and Performance Targets for G.992.2 FDM and overlapped spectrum implementations** + +| Case # | Loop (see Rec. G.996.1) | Loop Insertion loss @ 300 kHz | Nominal length (km) | Down net data rate (kbit/s) | Up net data rate (kbit/s) | Noise @ ATU-C | Noise @ ATU-R | +|--------|-------------------------|-------------------------------|---------------------|-----------------------------|---------------------------|---------------|---------------| +| 1 | ETSI-0 | 0 dB | 0 | 1536 | 512 | No | No | +| 2 | ETSI-1 | 40 dB | 2.80 | 1536 | 256 | Euro-K | ETSI-A | +| 3 | ETSI-1 | 50 dB | 3.50 | 1536 | 96 | Euro-K | ETSI-A | +| 4 | ETSI-1 | 40 dB | 2.80 | 1536 | 448 | ETSI-A | ETSI-A | +| 5 | ETSI-1 | 50 dB | 3.50 | 1536 | 256 | ETSI-A | ETSI-A | +| 6 | ETSI-1 | 60 dB | 4.20 | 512 | 96 | ETSI-A | ETSI-A | +| 7 | ETSI-1 | 60 dB | 4.20 | 1536 | 512 | AWGN-140 | AWGN-140 | + +## APPENDIX I + +In anticipation of future revisions of this Recommendation, manufacturers are encouraged to implement and investigate the performance of trellis coding in a splitterless environment as defined in Recommendation G.992.1. + +Implementers wishing to investigate the use of trellis coding should negotiate its use via the Non-Standard Facilities (NSF) capabilities of Recommendation G.994.1. + +## APPENDIX II + +### Guide to scenarios for the implementation of the various procedures in Recommendations G.994.1 and G.992.2 + +#### Scope + +This informative appendix is intended to guide implementers through multiple scenarios of using Recommendation G.994.1 and this Recommendation together in an implementation. The scenarios exemplify procedures that conform to Recommendation G.994.1 and this Recommendation. The scenarios are not intended to limit Recommendation G.994.1 and this Recommendation but rather are intended to assist implementers in understanding the relationship between the various procedures defined in Recommendations G.994.1 and G.992.2. + +#### Definitions and abbreviations + +- UC G.992.2 Absolute Upstream Fast Retrain Power Cutback, transmitted by the CP in the R-MSG-FR1 bits $u_4-u_0$ . +- RDC G.992.2 Relative Downstream Fast Retrain Power Cutback, transmitted by the CP in the R-MSG-FR1 bits $d_4-d_0$ . +- DPI G.992.2 Initialization Politeness Power Cutback, transmitted by the CO in the C-MSG1 bits 8-6. +- DPF G.992.2 Fast Retrain Politeness Power Cutback, transmitted by the CO in the C-MSG-FR1 bits $b_4-b_0$ . +- UMAX G.994.1 maximum power for an upstream signal, defined in Recommendation G.994.1. +- DMAX G.994.1 maximum power for a downstream signal, defined in Recommendation G.994.1. +- $g_i$ G.992.2 Gain scaling values applied during modulation in either the upstream or downstream direction. + +In the definitions of acronyms above, the letters U and D of the acronyms represent upstream and downstream, respectively. The letter R represents relative, and the letter C represents cutback. The letters I and F represent initialization and "fast retrain," respectively. + +#### Note on the use of PSD level + +This appendix often describes PSD levels of particular signals in either G.992.2 or G.994.1. In all cases, the PSD level described should be referenced back to the defining document to determine the exact method of measuring the power. + +For signals that are composed of single or multiple continuous subcarriers, the PSD level must be interpreted as a power number per subcarrier rather than a density. For G.992.2 maximum levels, Table II.1 should be used (). Other cutback values for G.992.2 and G.994.1 have similar relationship between the PSD level and the power per subcarrier. + +**Table II.1/G.992.2 – PSD level and power per Subcarrier** + +| PSD Level | Power | +|------------|----------------------| +| -38 dBm/Hz | -1.65 dBm/subcarrier | +| -40 dBm/Hz | -3.65 dBm/subcarrier | + +## Scenarios + +The scenarios included in this appendix are organized into several categories for convenience. Each scenario is presented with a list of successive steps the ATU pair might execute. These steps are examples only and do not provide an exhaustive listing of all allowable steps. + +Each scenario is also presented in a timeline similar to those used in the main body of this Recommendation. The timeline shows the progression of ATU states, power levels used at each transmitter, and references to the appropriate clauses of Recommendation G.994.1 and this Recommendation. + +Following the timeline of some scenarios that invoke various power cutback levels, hypothetical examples are provided to illustrate various conditions that effect the scenario's power cutback levels. + +### Activation scenarios + +These scenarios represent situations in which the ADSL link is activated with one or the other end having no memory of any prior activation. + +#### First Successful On-hook Activation + +This scenario describes a sequence that might occur during the first activation of the ADSL link from power management states L3 to L0. Both ATUs are assumed installed and ready to operate. The ATUs have no memory of past activation. + +For convenience in describing the scenario, the ATU state sequence is broken into several blocks as given in Table II.2. The step numbers in the table refer to the paragraph numbers that follow in this subclause. + +**Table II.2/G.992.2 – Blocks of First Successful On-Hook Activation Scenario** + +| Block | Steps | +|--------------------------|-------| +| First G.994.1 | 1-3 | +| Aborted Fast Retrain | 4-5 | +| Second G.994.1 | 6-8 | +| Second Fast Retrain | 9-13 | +| Third G.994.1 | 14-16 | +| Initialization Procedure | 17-21 | +| SHOWTIME | 22 | + +The scenario proceeds as described in the following steps and as depicted in Figure II.1. The duration of states C-SILENT1 and R-SILENT0 described in this section and as shown in Figure II.1 may be unnoticeably small at the receiving ATU. + +| CO Transmitter Downstream | | | | CP Transmitter Upstream | | +|---------------------------|---------------------------------------------------------------|----------------------------|---------------------------------|-------------------------|----------------------------------------------------------------| +| dbm/Hz | State | Block | Step | dbm/Hz | State | +| n/a | CSILENT-1 | First G.994.1 | 1 | n/a | RSILENT-0 | +| ≤ DMAX | C-TONES | | 2 | ≤ UMAX | R-TONES-REQ | +| ≤ DMAX
(same) | various G.994.1
states ending in
C-FLAG2 | | 3 | ≤ UMAX
(same) | various G.994.1
states ending in
R-FLAG2 | +| n/a | C-QUIET-EF1 | Aborted
Fast
Retrain | 4 | n/a | R-QUIET-EF1 | +| -40 | C-RECOV | | 5 | | | +| n/a | C-SILENT1 | Second G.994.1 | 6 | -38 | R-TONES-REQ | +| -40 | C-TONES | | 7 | | | +| -40 | various G.994.1
states ending in
C-FLAG2 | | 8 | | | +| n/a | C-QUIET-EF1 | Second Fast
Retrain | 9 | n/a | R-QUIET-EF1 | +| -40 | C-RECOV | | 10 | | | +| -40 – DPF | C-REVERB-FR1 | | 11 | -38 | R-RECOV | +| -40 – DPF | sequence of fast
retrain states
ending in
C-CRC-FR1 | | 12 | | | +| n/a | C-SILENT1 | Third G.994.1 | 13 | ≤ -38 | sequence of fast
retrain states
ending in
R-QUIET-FR1 | +| -40 | C-TONES | | 14 | n/a | R-SILENT0 | +| - DPF – RDC | various G.994.1
states ending in
C-FLAG2 | | 15 | -38
– UC | R-TONES-REQ | +| n/a | C-QUIET2 | Initialization Procedure | 16 | -38
– UC | various G.994.1
states ending in
R-FLAG2 | +| -40 | C-PILOT1 | | 17 | n/a | R-QUIET2 | +| - DPF – RDC | C-REVERB1 | | 18 | -38
– UC | R-REVERB1 | +| - max (DPI,
DPF + RDC) | sequence of
initialization states
ending in
C-SEGUE3 | | 19 | | | +| -40 | SHOWTIME | | 20 | -38
– UC | sequence of
initialization states
ending in
R-SEGUE5 | +| - max (DPI,
DPF + RDC) | SHOWTIME | 21 | -38
– UC
+ g i | SHOWTIME | | +| + g i | | | | | 22 | + +T1535300-00 + +Figure II.1/G.992.2 – First time activation scenario + +### First G.994.1 + +- 1 The ATU-R initiates G.994.1 by transmitting R-TONES-REQ at no greater than the maximum G.994.1 power level for upstream (UMAX). +- 2 The ATU-C responds with G.994.1 by transmitting C-TONES at no greater than the maximum G.994.1 power level for downstream (DMAX). + +- 3 Both ATUs continue the G.994.1 procedure using the same power levels and terminate the G.994.1 procedure using a mode select transaction with a G.992.2 code point asserted and the escape to fast retrain bit asserted. + +#### **Aborted Fast Retrain** + +- 4 Both ATUs observe the quiet period requirement of the escape to fast retrain procedure. +- 5 The ATU-C initiates the fast retrain procedure by transmitting the C-RECOV signal at $-40$ dBm/Hz. + +#### **Second G.994.1** + +- 6 The ATU-R aborts the fast retrain by again transmitting R-TONES-REQ at $-38$ dBm/Hz so that the G.994.1 procedures will be repeated at nominal power levels specified by G.992.2 to facilitate average power level measurement at the CO. +- 7 The ATU-C restarts G.994.1 by transitioning to C-SILENT1 and transmitting C-TONES at $-40$ dBm/Hz level. +- 8 Both ATUs continue with G.994.1 procedure using the same power levels and again terminate using a mode select transaction with a G.992.2 code point asserted and the escape to fast retrain bit asserted. The ATU-C measures the G.994.1 average received power per tone during the procedure. + +#### **Second Fast Retrain** + +- 9 Both ATUs observe the quiet period requirement of the escape to fast retrain procedure. +- 10 The ATU-C initiates the fast retrain procedure by transmitting C-RECOVER signal at $-40$ dBm/Hz. +- 11 The ATU-R responds with the fast retrain procedure by transmitting the R-RECOV signal at $-38$ dBm/Hz, and the ATU-C measures the received power. This power measurement and the measurements made during G.994.1 are combined in a vendor discretionary manner at the CO to form an "average". The "average" is used by the ATU-C to determine the fast retrain politeness power cutback (DPF) of 0, 2, 4, 6, 8, 10, or 12 dB. +- 12 ATU-C continues the fast retrain procedure by transmitting C-REVERB-FR1 at $-40 - \text{DPF}$ dBm/Hz. +- 13 Both ATUs truncate the fast retrain procedure using the bits in R-MSG-FR1 and C-MSG-FR1. The ATU-C transmits at a power level of $-40 - \text{DPF}$ dBm/Hz. The ATU-R transmits at a single vendor discretionary power level less than or equal to $-38$ dBm/Hz. During the messages exchanged in this fast retrain procedure, the ATU-R commands the ATU-C of the relative downstream power fast retrain power cutback (RDC) that shall be used and informs the ATU-C of the absolute upstream fast retrain power cutback (UC) that it shall use. The ATU-C informs the ATU-R of the fast retrain politeness cutback (DPF) that was used during the fast retrain procedure. + +#### **Third G.994.1** + +- 14 The ATU-R initiates G.994.1 by transitioning to R-SILENT0 and transmitting R-TONES-REQ at $-38 - \text{UC}$ dBm/Hz. +- 15 The ATU-C responds with G.994.1 by transitioning to C-SILENT1 and transmitting C-TONES at $-40 - \text{DPF} - \text{RDC}$ dBm/Hz. +- 16 Both ATUs continue with the G.994.1 procedure and terminate it using a mode select transaction with a G.992.2 code point asserted (and the escape to fast retrain bit is not asserted). + +### Initialization Procedure + +- 17 Both ATUs observe the quiet period required at the start of the G.992.2 initialization procedure. +- 18 The ATU-C continues the initialization procedure by transmitting C-PILOT at $-40 - \text{DPF} - \text{RDC}$ dBm/Hz. +- 19 The ATU-R responds by transmitting R-REVERB1 at $-38 - \text{UC}$ dBm/Hz, and the ATU-C measures the received power in 12 tones to determine a new initialization politeness power cutback (DPI) of 0, 2, 4, 6, 8, 10, or 12 dB. +- 20 The ATU-C starts transmitting C-REVERB1 at $-40 - 2n$ . The value of $2n$ is the maximum of the value of $(\text{DPF} + \text{RDC})$ and the value of DPI. +- 21 Both ATUs finish the initialization procedure and go to SHOWTIME. During the messages exchanged in this initialization procedure, the ATU-C informs the ATU-R of the value of DPI that was determined (but the value $2n$ is the absolute power cutback used by the ATU-C). Both ATUs signal that they have lost all profiles, and both ATU erase any profile information currently stored. + +### SHOWTIME + +- 22 During SHOWTIME, both ATUs save profile #0 using the aoc protocol. The ATU-C transmits at $-40 - 2n$ dBm/Hz. The ATU-R transmits at $-38 - \text{UC}$ dBm/Hz. + +This scenario conforms to G.992.2 for all cases of short and long loops, on-hook and off-hook conditions, and with or without in-line filters. However, the effect of power cutback varies considerably in each of these cases. Several examples are provided to clarify the effect of power cutback in these cases. Each example is summarized with a table that depicts the same state flow of both ATUs as shown in Figure II.1. The template for the example is shown in Table II.3. + +**Table II.3/G.992.2 – Summary of First Time Install Scenario** + +| ATU-C Block | dBm/Hz | Steps | ATU-R Block | dBm/Hz | +|-----------------------------------------------------------|---------------------------------------------------------|-------|------------------------------------------|-------------------------| +| First G.994.1 | $\leq \text{DMAX}$ | 1-3 | First G.994.1 | $\leq \text{UMAX}$ | +| Aborted First Fast Retrain | $-40$ | 4-5 | N/A | | +| Second G.994.1 | $-40$ | 6-8 | Second G.994.1 | $-38$ | +| Second Fast Retrain
C-RECOV | $-40$ | 9-11 | Second Fast Retrain
R-RECOV | $-38$ | +| Remainder of Second Fast
Retrain | $-40 - \text{DPF}$ | 12-13 | Remainder of Second Fast
Retrain | $\leq -38$ | +| Third G.994.1 | $-40 - \text{DPF} - \text{RDC}$ | 14-16 | Third G.994.1 | $-38 - \text{UC}$ | +| C-PILOT | $-40 - \text{DPF} - \text{RDC}$ | 17-19 | R-REVERB1 | $-38 - \text{UC}$ | +| C-REVERB1 and
Remainder of Initialization
Procedure | $-40 - \max(\text{DPI}, \text{DPF} + \text{RDC})$ | 20-21 | Remainder of
Initialization Procedure | $-38 - \text{UC}$ | +| SHOWTIME | $-40 - \max(\text{DPI}, \text{DPF} + \text{RDC}) + g_i$ | 22 | SHOWTIME | $-38 - \text{UC} + g_i$ | + +### Example with Long Loop and In-line Filters + +During the scenario in this example with long loops and no effect from telephony devices, there will be no politeness or fast retrain power cutbacks. A numeric example of the various power levels is summarized in Table II.4. + +**Table II.4/G.992.2 – Power Levels for Install Case with Long Loop with In-Line Filters** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|--------------------|---------------------------------------|--------------------| +| First G.994.1 | $\leq \text{DMAX}$ | First G.994.1 | $\leq \text{UMAX}$ | +| Aborted First Fast Retrain | -40 | N/A | | +| Second G.994.1 | -40 | Second G.994.1 | -38 | +| Second Fast Retrain C-RECOV | -40 | Second Fast Retrain R-RECOV | -38 | +| Remainder of Second Fast Retrain | -40 | Remainder of Second Fast Retrain | $\leq -38$ | +| Third G.994.1 | -40 | Third G.994.1 | -38 | +| C-PILOT | -40 | R-REVERB1 | -38 | +| C-REVERB1 and Remainder of Initialization Procedure | -40 | Remainder of Initialization Procedure | -38 | +| SHOWTIME | $-40 + g_i$ | SHOWTIME | $-38 + g_i$ | + +### Example with Short Loop and In-line Filters + +During the scenario in this case, the two politeness cutbacks will be active and there will be no fast retrain power cutback. A numeric example of the various power levels is shown in Table II.5. In this example, the value of DPF is 10 dB, and the value of DPI is 12 dB. + +**Table II.5/G.992.2 – Power Levels for Install Case with Short Loop with In-Line Filters** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|--------------------|---------------------------------------|--------------------| +| First G.994.1 | $\leq \text{DMAX}$ | First G.994.1 | $\leq \text{UMAX}$ | +| Aborted First Fast Retrain | -40 | N/A | | +| Second G.994.1 | -40 | Second G.994.1 | -38 | +| Second Fast Retrain C-RECOV | -40 | Second Fast Retrain R-RECOV | -38 | +| Remainder of Second Fast Retrain | -50 | Remainder of Second Fast Retrain | $\leq -38$ | +| Third G.994.1 | -40 | Third G.994.1 | -38 | +| C-PILOT | -40 | R-REVERB1 | -38 | +| C-REVERB1 and Remainder of Initialization Procedure | -52 | Remainder of Initialization Procedure | -38 | +| SHOWTIME | $-52 + g_i$ | SHOWTIME | $-38 + g_i$ | + +### Example with Short Loop and Non-ideal Telephone Devices + +During the scenario in this case, the politeness power cutbacks will be active and there will be fast retrain power cutbacks in each direction. A numeric example of the various power levels is shown in Table II.6. In this example, the value of DPF is 4 dB, and the value of DPI is 2 dB. The values of RDC and UC are 12 and 10 dB, respectively. + +**Table II.6/G.992.2 – Power Levels for Install Case with Short Loop +with Non-ideal Telephone Devices** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|--------------------|---------------------------------------|--------------------| +| First G.994.1 | $\leq \text{DMAX}$ | First G.994.1 | $\leq \text{UMAX}$ | +| Aborted First Fast Retrain | -40 | N/A | | +| Second G.994.1 | -40 | Second G.994.1 | -38 | +| Second Fast Retrain C-RECOV | -40 | Second Fast Retrain R-RECOV | -38 | +| Remainder of Second Fast Retrain | -44 | Remainder of Second Fast Retrain | $\leq -38$ | +| Third G.994.1 | -56 | Third G.994.1 | -48 | +| C-PILOT | -56 | R-REVERB1 | -48 | +| C-REVERB1 and Remainder of Initialization Procedure | -56 | Remainder of Initialization Procedure | -48 | +| SHOWTIME | $-56 + g_i$ | SHOWTIME | $-48 + g_i$ | + +**Example with Long Loop and Non-ideal Telephone Devices** + +During the scenario in this case, there will be no politeness cutbacks but there will be fast retrain power cutbacks in each direction. A numeric example of the various power levels is shown in Table II.7. In this example, the value of RDC and UC are 4 and 12 dB, respectively. + +**Table II.7/G.992.2 – Power Levels for Install Case with Long Loop +with Non-ideal Telephone Devices** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|--------------------|---------------------------------------|--------------------| +| First G.994.1 | $\leq \text{DMAX}$ | First G.994.1 | $\leq \text{UMAX}$ | +| Aborted First Fast Retrain | -40 | N/A | | +| Second G.994.1 | -40 | Second G.994.1 | -38 | +| Second Fast Retrain C-RECOV | -40 | Second Fast Retrain R-RECOV | -38 | +| Remainder of Second Fast Retrain | -40 | Remainder of Second Fast Retrain | $\leq -38$ | +| Third G.994.1 | -44 | Third G.994.1 | -50 | +| C-PILOT | -44 | R-REVERB1 | -50 | +| C-REVERB1 and Remainder of Initialization Procedure | -44 | Remainder of Initialization Procedure | -50 | +| SHOWTIME | $-44 + g_i$ | SHOWTIME | $-50 - g_i$ | + +**Normal Operating Scenarios** + +These scenarios represent situations that will normally occur while operating in the SHOWTIME L0 and L1 link states. + +**First Off-hook Condition** + +This scenario describes a sequence that might occur during the first off-hook condition following activation of the ADSL link. Both ATUs are assumed to be operating in the SHOWTIME state. The ATUs have only profile #0 stored associated with the present SHOWTIME configuration. A non-ideal telephone device without an in-line filter is assumed to go to its off-hook state in this scenario. + +For convenience in describing the scenario, the ATU state sequence is broken into several blocks as given in Table II.8. The step numbers in the table refer to the paragraph numbers that follow in this subclause. + +**Table II.8/G.992.2 – Blocks of First Off-Hook Scenario** + +| Block | Steps | +|--------------------------|--------------| +| First SHOWTIME | | +| Fast Retrain | 1-5 | +| G.994.1 | 6-8 | +| Initialization Procedure | 9-13 | +| Second SHOWTIME | 14 | + +The scenario proceeds as described in the steps below and as depicted in Figure II.2. The duration of states C-SILENT1 and R-SILENT0 described in this subclause and as shown in Figure II.2 may be unnoticeably small at the receiving ATU. + +| CO Transmitter Downstream | | Block | Step | CP Transmitter Upstream | | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------|------|--------------------------|-----------------------------------------------------------------------------------------------------| +| dbm/Hz | State | | | dbm/Hz | State | +| -40
- max (DPI,
DPF + RDC)
+ $g_i$ | SHOWTIME | First
SHOWTIME | | -38
- UC
+ $g_i$ | SHOWTIME | +| -40 | C-RECOV | Fast Retrain | 1 | -38 | R-RECOV | +| -40
- DPF' | C-REVERB-FR1 | | 2 | | | +| -40
- DPF' | sequence of fast
retrain states
ending in
C-CRC-FR1 | | 3 | | | +| | | | 4 | $\leq -38$ | sequence of fast
retrain states
ending in
R-QUIET-FR1 | +| -40
- DPF' - RDC' | sequence of fast
retrain states
starting with
C-REVERB-FR3
and ending in
C-SEGUE-FR4 | | 5 | -38
- UC' | sequence of fast
retrain states
starting with
R-REVERB-FR3
and ending in
R-SEGUE-FR5 | +| n/a | C-SILENT1 | G.994.1 | 6 | n/a | R-SILENT0 | +| -40
- DPF' - RDC' | C-TONES | | 7 | -38
- UC' | R-TONES-REQ | +| -40
- DPF' - RDC' | various G.994.1
states ending in
C-FLAG2 | | 8 | -38
- UC' | various G.994.1
states ending in
R-FLAG2 | +| n/a | C-QUIET2 | Initialization Procedure | 9 | n/a | R-QUIET2 | +| -40
- DPF' - RDC' | C-PILOT1 | | 10 | -38
- UC' | R-REVERB1 | +| -40
- max (DPI',
DPF' + RDC') | C-REVERB1 | | 11 | | | +| | | | 12 | | | +| -40
- max (DPI',
DPF' + RDC') | sequence of
initialization states
ending in
C-SEGUE3 | | 13 | -38
- UC' | sequence of
initialization states
ending in
R-SEGUE5 | +| -40
- max (DPI',
DPF' + RDC')
+ $g_i'$ | SHOWTIME | Second
SHOWTIME | 14 | -38
- UC'
+ $g_i'$ | SHOWTIME | +| | | | | | | + +T1535310-00 + +Figure II.2/G.992.2 – First off-hook telephone scenario + +## Fast Retrain + +- 1 The ATU-R initiates the fast retrain procedure by transmitting R-RECOV signal at $-38 \text{ dBm/Hz}$ . In this example, the ATU-C does not measure the received power of the tone to calculate DPF as in the install scenario in First Successful On-hook Activation. +- 2 The ATU-C initiates the fast retrain procedure by transmitting C-RECOV signal at $-40 \text{ dBm/Hz}$ . +- 3 The ATU-C transmits C-REVERB-FR1 at $-40 - \text{DPF}$ . In this example, the ATU-C sets DPF to the previous value of DPI unlike the install scenario in First Successful On-hook Activation. +- 4 In this example, both ATUs execute the first portion of the fast retrain procedure (through C-CRC-FR1 and R-QUIET-FR1). The ATU-C transmits at a power level of $-40 - \text{DPF} \text{ dBm/Hz}$ . The ATU-R transmits at a single vendor discretionary power level of less than or equals $-38 \text{ dBm/Hz}$ . During the messages exchanged in this fast retrain procedure, the ATU-R commands the ATU-C of the value of RDC that shall be used and informs the ATU-C of the value of UC that it shall use. The ATU-C informs the ATU-R of the value of DPF that it has been using. +- 5 Both ATUs complete the fast retrain procedure. The ATU-C transmits at a power level of $-40 - \text{DPF} - \text{RDC} \text{ dBm/Hz}$ . The ATU-R transmits at a power level of $-38 - \text{UC} \text{ dBm/Hz}$ . In this example, the ATUs both select the unknown profile during message exchanges of the fast retrain procedure. + +## G.994.1 + +- 6 The ATU-R initiates G.994.1 by transitioning to R-SILENT0 and transmitting R-TONES-REQ at $-38 - \text{UC} \text{ dBm/Hz}$ . +- 7 The ATU-C initiates G.994.1 by transitioning to C-SILENT1 and transmitting C-TONES at $-40 - \text{DPF} - \text{RDC} \text{ dBm/Hz}$ . +- 8 Both ATUs continue with the G.994.1 procedure and terminate it using a mode select transaction with a G.992.2 code point asserted. The escape to fast retrain bit is not asserted. + +## Initialization Procedure + +- 9 Both ATUs observe the quiet period required at the start of the G.992.2 initialization procedure. +- 10 The ATU-C continues the initialization procedure by transmitting C-PILOT at $-40 - \text{DPF} - \text{RDC} \text{ dBm/Hz}$ . +- 11 The ATU-R responds by transmitting R-REVERB1 at $-38 - \text{UC} \text{ dBm/Hz}$ , and the ATU-C measures the received power in 12 tones to determine a new value of $\text{DPI} = 0, 2, 4, 6, 8, 10, \text{ or } 12 \text{ dB}$ . +- 12 The ATU-C starts transmitting C-REVERB1 at $-40 - 2n$ . The value of $2n$ is the maximum of the value of $(\text{DPF} + \text{RDC})$ and the value of DPI. +- 13 Both ATUs finish the initialization procedure and go to SHOWTIME. During the messages exchanged in this initialization procedure, the ATU-C informs the ATU-R of the DPI cutback that was determined (but the value $2n$ is the absolute power cutback used by the ATU-C). Note that this is expected to be the same as the previous determination of DPI, but there could be variation. + +## Second SHOWTIME + +14 During SHOWTIME, both ATUs save profile #1 using the aoc protocol. + +This scenario conforms to G.992.2 for all cases of short and long loops. However, the effect of power cutback varies somewhat for each these cases. Examples are provided to clarify the effect of power cutback in these cases. Each example is summarized with a table that depicts the same state flow of both ATUs as shown in Figure II.2. The template for the example is shown in Table II.9. The apostrophe (') following names indicates the new values determined during the fast retrain and initialization procedures. + +**Table II.9/G.992.2 – Summary of First Off-Hook Condition Scenario** + +| ATU-C Block | dBm/Hz | Steps | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|----------------------------------------|-------|---------------------------------------|--------------------| +| First SHOWTIME | $-40 - \max(DPI, DPF + RDC) + g_i$ | | First SHOWTIME | $-38 - UC + g_i$ | +| Fast Retrain C-RECOV | $-40$ | 1-2 | Fast Retrain R-RECOV | $-38$ | +| First Portion of Fast Retrain | $-40 - DPF'$ | 3-4 | First Portion of Fast Retrain | $\leq -38$ | +| Remainder of Fast Retrain | $-40 - DPF' - RDC'$ | 5 | Remainder of Fast Retrain | $-38 - UC'$ | +| G.994.1 | $-40 - DPF' - RDC'$ | 6-8 | G.994.1 | $-38 - UC'$ | +| C-PILOT | $-40 - DPF' - RDC'$ | 9-11 | R-REVERB1 | $-38 - UC'$ | +| C-REVERB1 and Remainder of Initialization Procedure | $-40 - \max(DPI', DPF' + RDC')$ | 12-13 | Remainder of Initialization Procedure | $-38 - UC'$ | +| SHOWTIME | $-40 - \max(DPI', DPF' + RDC') + g_i'$ | 14 | SHOWTIME | $-38 - UC' + g_i'$ | + +## Example with Long Loop + +During the scenario in this case, no politeness cutbacks are active. A numeric example of the various power levels is shown in Table II.10. In this example, the new values of RDC and UC are 4 and 18 dB, respectively. The previous values of RDC and UC are 0 and 6 dB, respectively. + +**Table II.10/G.992.2 – Power Levels for Off-hook Operating Case with Long Loop** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|--------------|---------------------------------------|--------------| +| First SHOWTIME | $-40 + g_i$ | First SHOWTIME | $-44 + g_i$ | +| Fast Retrain C-RECOV | $-40$ | Fast Retrain R-RECOV | $-38$ | +| First Part of Fast Retrain | $-40$ | First Part of Fast Retrain | $\leq -38$ | +| Remainder of Fast Retrain | $-44$ | Remainder of Fast Retrain | $-56$ | +| G.994.1 | $-44$ | G.994.1 | $-56$ | +| C-PILOT | $-44$ | R-REVERB1 | $-56$ | +| C-REVERB1 and Remainder of Initialization Procedure | $-44$ | Remainder of Initialization Procedure | $-56$ | +| SHOWTIME | $-44 + g_i'$ | SHOWTIME | $-56 + g_i'$ | + +### Example with Short Loop + +During the scenario in this case, both politeness and fast retrain power cutbacks are active. A numeric example of the various power levels is shown in Table II.11. In this example, the new values of DPF and DPI are 6 and 8 dB, respectively. The new values of RDC and UC are 12 and 22 dB, respectively. The previous value of DPF and DPI are 10 and 6 dB, respectively. The previous values of RDC and UC are both 0. + +**Table II.11/G.992.2 – Power Levels for Off-hook Operating Case with Short Loop** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-----------------------------------------------------|-------------|---------------------------------------|--------------| +| First SHOWTIME | $-50 + g_i$ | First SHOWTIME | $-38 + g_i$ | +| Fast Retrain C-RECOV | -40 | Fast Retrain R-RECOV | -38 | +| First Part of Fast Retrain | -40 | First Part of Fast Retrain | -38 | +| Remainder of Fast Retrain | -58 | Remainder of Fast Retrain | -60 | +| G.994.1 | -58 | G.994.1 | -60 | +| C-PILOT | -58 | R-REVERB1 | -60 | +| C-REVERB1 and Remainder of Initialization Procedure | -58 | Remainder of Initialization Procedure | -60 | +| SHOWTIME | $-58 + g_i$ | SHOWTIME | $-60 + g_i'$ | + +### Return to On-hook Condition + +This scenario describes a sequence that might occur following an off-hook condition as the telephone device returns to the on-hook condition. The ATUs have profiles #0 stored, and #0 is associated with the previous on-hook condition. A non-ideal telephone device without an in-line filter is assumed to go to its on-hook condition in this scenario. + +For convenience in describing the scenario, the ATU state sequence is broken into several blocks as given in Table II.8. The step numbers in the table refer to the paragraph numbers that follow in this subclause. + +**Table II.12/G.992.2 – Blocks of Return to On-Hook Scenario** + +| Block | Steps | +|-----------------|-------| +| First SHOWTIME | | +| Fast Retrain | 1-5 | +| Second SHOWTIME | 6 | + +The scenario proceeds as described in the steps below and as depicted in Figure II.3. + +| CO Transmitter Downstream | | Block | Step | CP Transmitter Upstream | | +|---------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------|------|-------------------------|-----------------------------------------------------------------------------------------------------| +| dbm/Hz | State | | | dbm/Hz | State | +| -40
- max (DPI,
DPF + RDC)
+ $g_i$ | SHOWTIME | First
SHOWTIME | | -38
- UC
+ $g_i$ | SHOWTIME | +| -40 | C-RECOV | Fast Retrain | 1 | | | +| -40
- DPF' | C-REVERB-FR1 | | 2 | -38 | R-RECOV | +| -40
- DPF' | sequence of fast
retrain states
ending in
C-CRC-FR1 | | 3 | | | +| -40
- DPF' | sequence of fast
retrain states
starting with
C-REVERB-FR3
and ending in
C-SEGUE-FR4 | | 4 | $\leq -38$ | sequence of fast
retrain states
ending in
R-QUIET-FR1 | +| -40
- DPF' - RDC' | | Second
SHOWTIME | 5 | -38
- UC' | sequence of fast
retrain states
starting with
R-REVERB-FR3
and ending in
R-SEGUE-FR5 | +| -40
- DPF' - RDC'
+ $g_i'$ | SHOWTIME | | 6 | -38
- UC
+ $g_i$ | SHOWTIME | + +T1535320-00 + +**Figure II.3/G.992.2 – Return to On-Hook Scenario** + +### Fast Retrain + +- 1 The ATU-R initiates the fast retrain procedure by transmitting R-RECOV signal at -38 dBm/Hz. In this example, the ATU-C does not measure the received power of the tone to calculate DPF cutback as in the install scenario in First Successful On-hook Activation. +- 2 The ATU-C initiates the fast retrain procedure by transmitting C-RECOV signal at -40 dBm/Hz. +- 3 The ATU-C transmits C-REVERB-FR1 at -40 - DPF. In this example, the ATU-C sets DPF to the previous value of DPI unlike the install scenario in First Successful On-hook Activation. +- 4 Both ATUs execute the first portion of the fast retrain procedure (through C-CRC-FR1 and R-QUIET-FR1). The ATU-C transmits at a power level of -40 - DPF dBm/Hz. The ATU-R transmits at a power level of -38 dBm/Hz. During the messages exchanged in this fast retrain procedure, the ATU-R commands the ATU-C of the value of RDC that the ATU-C shall be used and informs the ATU-C of the value of UC that it shall use. The ATU-C informs the ATU-R of the value of DPF that it has been using. +- 5 Both ATUs complete the fast retrain. The ATU-C transmits at a power level of -40 - DPF - RDC dBm/Hz. The ATU-R transmits at a power level of -38 - UC dBm/Hz. In + +this example, the ATUs both select profile #0 during message exchanges of the fast retrain procedure. + +## Second SHOWTIME + +6 Both ATUs return to SHOWTIME. The ATU-C transmits at a power level of $-40 - \text{DPF} - \text{RDC}$ adjusted by the $g_i$ tables from the profile #0. Note that this is different that the downstream PSD equation in First Successful On-hook Activation and First Off-hook Condition. The ATU-R transmits at a power level of $-38 - \text{UC}$ adjusted by the $g_i$ tables from the profile #0. + +This scenario conforms to G.992.2 for all cases of short and long loops. However, the effect of power cutback varies somewhat for each these cases. Examples are provided to clarify the effect of power cutback in these cases. Each example is summarized with a table that depicts the same state flow of both ATUs as shown in Figure II.3. The template for the example is shown in Table II.13. The apostrophe (') following names indicates the new values determined during the fast retrain and initialization procedures. + +**Table II.13/G.992.2 – Summary Return to On-Hook Scenario** + +| ATU-C Block | dBm/Hz | Steps | ATU-R Block | dBm/Hz | +|-------------------------------|---------------------------------------------------------|-------|-------------------------------|---------------------------| +| First SHOWTIME | $-40 - \max(\text{DPI}, \text{DPF} + \text{RDC}) + g_i$ | | First SHOWTIME | $-38 - \text{UC} + g_i$ | +| Fast Retrain C-RECOV | -40 | 1-2 | Fast Retrain R-RECOV | -38 | +| First Portion of Fast Retrain | $-40 - \text{DPF}'$ | 3-4 | First Portion of Fast Retrain | $\leq -38$ | +| Remainder of Fast Retrain | $-40 - \text{DPF}' - \text{RDC}'$ | 5 | Remainder of Fast Retrain | $-38 - \text{UC}'$ | +| SHOWTIME | $-40 - \text{DPF}' - \text{RDC}' + g_i'$ | 6 | SHOWTIME | $-38 - \text{UC}' + g_i'$ | + +## Example with Long Loop + +During the scenario in this case, politeness cutbacks are not active. A numeric example of the various power levels is shown in Table II.14. In this example, the new values of RDC and UC are 0. The previous values of DPI, DPF, RDC, and UC are 0, 0, 6, and 12 dB, respectively. + +**Table II.14/G.992.2 – Power Levels for On-hook Operating Case with Long Loop** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-------------------------------|-------------|-------------------------------|-------------| +| First SHOWTIME | $-46 + g_i$ | First SHOWTIME | $-50 + g_i$ | +| Fast Retrain C-RECOV | -40 | Fast Retrain R-RECOV | -38 | +| First Portion of Fast Retrain | -40 | First Portion of Fast Retrain | $\leq -38$ | +| Remainder of Fast Retrain | -40 | Remainder of Fast Retrain | -38 | +| SHOWTIME | $-40 + g_i$ | SHOWTIME | $-38 + g_i$ | + +## Example with Short Loop + +During the scenario in this case, both politeness and fast retrain power cutbacks are active. A numeric example of the various power levels is shown in Table II.15. In this example, the new values of DPF, RDC and UC are 4, 2, and 0. The previous values of DPI, DPF, RDC, and UC are 6, 4, 14, and 24 dB, respectively. + +**Table II.15/G.992.2 – Power Levels for On-hook Operating Case with Short Loop** + +| ATU-C Block | dBm/Hz | ATU-R Block | dBm/Hz | +|-------------------------------|--------------|-------------------------------|--------------| +| First SHOWTIME | $-58 + g_i$ | First SHOWTIME | $-62 + g_i$ | +| Fast Retrain C-RECOV | -40 | Fast Retrain R-RECOV | -38 | +| First Portion of Fast Retrain | -44 | First Portion of Fast Retrain | $\leq -38$ | +| Remainder of Fast Retrain | -46 | Remainder of Fast Retrain | -38 | +| SHOWTIME | $-46 + g_i'$ | SHOWTIME | $-38 + g_i'$ | + +### Power Management Scenarios + +These scenarios represent situations that will normally occur while transitioning among the three defined power management states L0, L1, and L3 using the power management transitions described in this Recommendation. + +### Retrain Scenarios + +While in L0 or L1 SHOWTIME states, line conditions or external commands may lead to the desire to retrain the modems. The special cases of off-hook and on-hook L0 to L0 transitions has already been presented in Normal Operating Scenarios where fast retrain is first attempted followed by initialization if necessary. This also applies to the scenario of L0 to L0 and L1 to L0 transitions that require retraining for other reasons. The fast retrain followed by initialization provides all necessary power cutbacks, allows the modems to quickly return to SHOWTIME if any stored profile matches, and provides full initialization if not. + +### Wake-up Scenarios + +This situation occurs when one of the ATUs desires to wake the link from L3 state and return it to L0 state. Either ATU may initiate the wake-up procedure. If the initiating ATU has retained memory, it may begin with either the fast retrain procedure or the initialization procedure. If the initiating ATU has not retained memory, it will begin with the initialization procedure. If the responding ATU has lost memory, it will abort a fast retrain request and will begin the initialization procedure. + +A summary of these combinations is presented in Table II.16 and details of the procedures are explained in the indicated paragraphs. + +**Table II.16/G.992.2 – Scenarios for Waking from L3 Link State** + +| CO Memory | CP Memory | Initiator | Procedure First Used | Scenario | +|-----------|-----------|-----------|----------------------|-------------------------------------------------------------------------------------------| +| Retained | Retained | ATU-C | Initialization | Wake-up Starting with Initialization | +| | | ATU-C | Fast Retrain | Wake-up Starting With Fast Retrain | +| | | ATU-R | Initialization | Wake-up Starting with Initialization | +| | | ATU-R | Fast Retrain | Wake-up Starting With Fast Retrain | +| Retained | Lost | ATU-C | Initialization | First Successful On-hook Activation | +| | | ATU-C | Fast Retrain | ATU-R aborts fast retrain request and proceeds as in Wake-up Starting with Initialization | +| | | ATU-R | Initialization | Wake-up Starting with Initialization | + +**Table II.16/G.992.2 – Scenarios for Waking from L3 Link State (concluded)** + +| CO Memory | CP Memory | Initiator | Procedure First Used | Scenario | +|-----------|-----------|-----------|----------------------|-------------------------------------------------------------------------------------------| +| Lost | Retained | ATU-C | Initialization | Wake-up Starting with Initialization | +| | | ATU-R | Initialization | Wake-up Starting with Initialization | +| | | ATU-R | Fast Retrain | ATU-C aborts fast retrain request and proceeds as in Wake-up Starting with Initialization | +| Lost | Lost | ATU-C | Initialization | Wake-up Starting with Initialization | +| | | ATU-R | Initialization | Wake-up Starting with Initialization | + +### Wake-up Starting With Fast Retrain + +An ATU that has retained memory can begin the wake-up procedure using the fast retrain procedure. The ATU initiates either the C-RECOVER or R-RECOVER signals. The action taken by the responding ATU depends upon whether it has retained memory. + +### Responding ATU Has Retained Memory + +If the responding ATU has retained memory, it will respond with the C-RECOVER or R-RECOVER signal at nominal G.992.2 power level and attempt to recall a stored profile to return to link state L0. If the result is the unknown profile, the initialization procedure will follow. + +The scenario with the ATU-R initiating proceeds using exactly the same six steps as in Return to On-hook Condition. The state sequence is exactly as shown in Figure II.3, except that both ATUs start in a silent state. PSD levels to be used are as summarized in Table II.13. + +If an unknown profile were selected by the fast retrain in this scenario, then G.994.1 and the G.992.2 initialization procedure would be invoked using the fast retrain power cutbacks to return to L0 SHOWTIME. + +### Responding ATU Has Not Retained Memory + +If the responding ATU has not retained memory, there is little point to attempting to match a stored profile. However, the fast retrain procedure is useful to determine necessary power cutback levels. The ATU will respond with the C-RECOVER or R-RECOVER signal at nominal G.992.2 power levels and use the fast retrain truncate followed by the initialization procedure to return to the L0 link state. + +The scenario with the ATU-R initiating proceeds using exactly the same steps starting with step 11 as in First Successful On-hook Activation. The state sequence is exactly as shown in Figure II.1 starting from step 11. Both ATUs start in a silent state prior to step 11. PSD levels to be used are as summarized in Table II.3. + +### Wake-up Starting with Initialization + +If an ATU has not retained memory, it beings with the initialization procedure using G.994.1. Since it is unknown if the other side has retained memory, the responding G.994.1 power levels may not be G.992.2 nominal. Because of this, the procedure used for wake-up starting with initialization is as in First Successful On-hook Activation. + +The scenario with the ATU-R initiating proceeds using exactly the steps as in First Successful On-hook Activation. The PSD levels to be used are as summarized in Table II.3. + +### Error Recovery Scenarios + +These scenarios represent error conditions that may occur during the procedures. + +### **Unable to Install Scenario** + +In this scenario, two ATUs are assumed attached to the line. However, they are unable to reach the SHOWTIME state because of some malfunction. In this example, the malfunction is one that comes during the initialization procedure's exchange sequence. + +The scenario begins as in First Successful On-hook Activation. However, for this example, a malfunction occurs in step 21. The ATUs invoke the initialization reset procedure and begin G.994.1 at nominal power levels. Assuming the ATUs desire to attempt another connection, they again go through the sequence of First Successful On-hook Activation, except they may skip steps 1-5 because G.994.1 power levels are already known to be at nominal levels. This may continue for some time. If the SHOWTIME state cannot be reached repeatedly, the ATUs can use G.994.1 to select another common mode of operation or send a mode select command with all zero operation mode bits to terminate the attempts. + +The use of fast retrain followed by initialization provides all necessary power cutbacks for the repeated attempts to train that may occur with phone devices in various hook switch conditions. + +### **Unable to Fast Retrain** + +If a malfunction is detected while executing the fast retrain algorithm, the ATUs may either repeat the fast retrain a number of times or invoke the initialization procedure. Repeating the fast retrain a number of times may allow telephony device characteristics adequate settling time for the retrain to be successful. If continued malfunctions occur, the reset initialization procedure is invoked and the ATUs begin G.994.1 at nominal power levels. The ATUs again go through the sequence of First Successful On-hook Activation, except they may skip steps 1-5 because G.994.1 power levels are already known to be at nominal levels. + +### **SHOWTIME Error Recovery** + +If a malfunction is detected while in SHOWTIME, the ATUs invoke either the fast retrain procedure or the initialization reset procedure. When using the initialization reset procedure, the ATU's begin G.994.1 at nominal power levels. Assuming the ATUs desire to return to the L0 or L1 state, they go through the sequence of First Successful On-hook Activation, except they may skip steps 1-5 because G.994.1 power levels are already known to be at nominal levels. + +## **APPENDIX III** + +### **Compatibility with other Customer Premises Equipment** + +G.992.2 CPE transceivers may share the CPE wiring plant with other equipment, e.g. networking devices. + +Some networking devices can operate above 4 MHz on customer premises phone wiring. To prevent signals from such networking devices from aliasing into the G.992.2 frequency band, the inclusion of an adequate downstream receiver anti-aliasing filter in the G.992.2 device is recommended, collocated with the h-p filter in Figure 1. This filter may take the form of an external, in-line filter or may be integrated into the G.992.2 device. + +If a POTS splitter is used in the G.992.2 application to isolate the customer premises wiring from the ADSL signal as noted in Figure 1, then home networking devices may co-exist with voice terminals and non-voice terminals on the TELE/POTS port side (the port in Figure 1 that attaches to the wire leading to the telephone set or voice band modem) of the remote splitter. It is desirable in those cases that the remote POTS splitter be compatible with other customer premises wiring devices (e.g. the TELE/POTS port impedance above 4 MHz should be considered). + +Similarly, if an in-line low-pass filter is used in the G.992.2 application as shown in Figure 1, it is desirable that the in-line low-pass filter be compatible with other customer premises wiring devices (e.g. the in-line filter impedance above 4 MHz should be considered). + + + +## 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.9940-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d8969f805414689ab79cfd08c333d454d482b3 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636c3839edff955a5b6208530b05fa1c983ab153d90f00216517a7a99478b988 +size 7074 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29ba89c5945603fd13fc951c3cbdeca9b80ae5de --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52ae8b88d3d19ff519845cd50e6e4581885aeef09dc9c27802c063fe9ec0e833 +size 48134 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9ce2c0326d8a0363d69b9bcd05ff16ab21f1635 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6a6ba575345aed8524e0505be2c93a325a09ef40037f5a359bbda4561e225fd +size 89130 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f147d9c2807907ddd0b06129afac7b8c76ec4fcd --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f75e5d39d86d5f8fd70447e6ae3a4848a738e1bec7813c37dba017c78cc193c5 +size 81199 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d47923d6cdecb7b9d6bb1d2f265db85b6a8a483 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4599aa1c6b096c6678b48bb8cdd3950ad133a67ea092f62e9371af54b73c960 +size 61317 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f82b4aed3dcd75637ba91495752d979e7d1d549b --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:180bd905979b5b3d0d72298aafe92cd365b1184ae11a5416d152e9eb8e792695 +size 22504 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e774138b139ddc5231f76c51047e0e751373299f --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f9268836794124649febbe1621ae17423666ed46eed0ab30d8ed7fcdf4939e3 +size 46353 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b1b333f035804df6c92169eb3207560423c86da --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/5b8a756d9a71c35f17db8bcb90b438a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01503fb5f9f425d47e7934b9a742da1726a749bf02a812b0106c321c68b8d719 +size 45065 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64b85a4f765d8860b170375810bf5a4d44cd507c --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a7302123348f1fe9209addce4bdbaacc58bf71a5ea9dcdd0db85c7b9bc1d4dd +size 5620 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f2013147d250a91a37e824d93cbee75823ac3bd --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00914ef8bf08390195a845a1c8887a32acc47579aefbf2bb8646f03cfb3249b7 +size 52499 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24ac0e3da41001c1837b9a1129be10ae17d5906f --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d5d9c2803ec66051ea9df47b4512d3247b2e0869b5a85dbf77d3bedbc1e1c93 +size 100033 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..291d538f9c18d81572fe81ae07d26f4438b75852 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/c914f51f4427bc672dd0526cfc90ebe9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4f42a36393b586bf5d6be35b19f6f2a069720a310e584a84d218fd0902fd026 +size 56949 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40013bf62b976aa5c53d91f9d951ff0ab9bcf7d6 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e71e06e558701127a8ab43ecd82ba7fb6d17176e2d373117064a6fceeb7bff69 +size 51413 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa25bda60b549649e705715e2d22eb016ec5e60 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb352bbf037896b4c45691465ab338e25445f1c0d73db167404820692afc768b +size 26373 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba953ee3301cb563b9b90aa6d6fd6b2631bd1eb --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42917cf9732f00f3b64008024004c58d0582e454d158be075ee55a963ee679b9 +size 11740 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.9940-202312-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20be93a13d85670324df7509f86d60bff1b3ab08 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3d0e0d53fe8dea5ea406cad58a30549d7fa58d5c9d6691a708d617ff2a0266d +size 53909 diff --git a/marked/G/T-REC-G.9940-202312-I_PDF-E/raw.md b/marked/G/T-REC-G.9940-202312-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..93461a879863049a7941d2d798fd0d085f187e09 --- /dev/null +++ b/marked/G/T-REC-G.9940-202312-I_PDF-E/raw.md @@ -0,0 +1,819 @@ + + +# Recommendation**ITU-T G.9940 (12/2023)** + +SERIES G: Transmission systems and media, digital systems and networks + +Access networks – In premises networks + +--- + +# **High speed fibre-based in-premises transceivers – system architecture** + +![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 | +| 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.9940 + +# High speed fibre-based in-premises transceivers – system architecture + +## Summary + +Recommendation ITU-T G.9940 belongs to the family of ITU-T G.fin Recommendations. Recommendation G.9940 specifies the system architecture and requirements for high-speed fibre-based in-premises transceivers. + +## History\* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.9940 | 2023-12-02 | 15 | 11.1002/1000/15549 | + +## Keywords + +Fibre in-premises, G.fin, home network, requirement, small and medium enterprise, system 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 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 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 ..... | 1 | +| 3.1 | Terms defined elsewhere ..... | 1 | +| 3.2 | Terms defined in this Recommendation..... | 2 | +| 4 | Abbreviations and acronyms ..... | 3 | +| 5 | Conventions ..... | 4 | +| 6 | Architecture of the G.fin network..... | 5 | +| 6.1 | Network architecture ..... | 5 | +| 6.2 | Reference models ..... | 7 | +| 6.3 | Protocol reference model..... | 9 | +| 6.4 | Centralized coordination network architecture ..... | 10 | +| 7 | Service requirements ..... | 12 | +| 7.1 | Service types..... | 12 | +| 7.2 | Mean signal transfer delay..... | 12 | +| 7.3 | Maximum Ethernet packet size ..... | 12 | +| 7.4 | Synchronization features and quality ..... | 12 | +| 8 | Physical layer requirements..... | 12 | +| 8.1 | Bit rates..... | 12 | +| 8.2 | Maximum number of connected S-FTRs ..... | 13 | +| 8.3 | Fibre length..... | 13 | +| 8.4 | Optical link budget ..... | 13 | +| 8.5 | Operating wavelength..... | 13 | +| 8.6 | Indoor fibre distribution network (IFDN) ..... | 14 | +| 9 | System level requirements..... | 15 | +| 9.1 | Power saving and energy efficiency ..... | 15 | +| 9.2 | Security functions..... | 15 | +| 9.3 | Dynamic time assignment ..... | 15 | +| 9.4 | Quality of service (QoS)..... | 16 | +| 9.5 | Eye safety ..... | 16 | +| 10 | System management functions ..... | 16 | +| 10.1 | Management schemes..... | 16 | +| 10.2 | Management functions ..... | 17 | +| | Appendix I – Optical link budget analysis for G.fin network..... | 19 | +| I.1 | Optical path loss factors ..... | 19 | +| I.2 | Splitting architecture ..... | 20 | +| I.3 | Optical link budget consideration..... | 21 | +| | Bibliography..... | 22 | + + + +# Recommendation ITU-T G.9940 + +# High speed fibre-based in-premises transceivers – system architecture + +# 1 Scope + +This Recommendation specifies the system architecture (SA) and general requirements of high speed fibre-based in-premises networking systems. This Recommendation acts as the foundation for the technical specification of the physical layer (PHY), data link layer (DLL) and management. + +Specifically, this Recommendation defines: + +- system architecture and reference models; +- deployment environments and application scenarios; +- requirements for service support, optical transmission, system functionalities, and management. + +# 2 References + +The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. + +- [ITU-T G.652] Recommendation ITU-T G.652 (2016), *Characteristics of a single-mode optical fibre*. +- [ITU-T G.657] Recommendation ITU-T G.657 (2016), *Characteristics of a bending-loss insensitive single-mode optical fibre and cable*. +- [ITU-T G.671] Recommendation ITU-T G.671 (2019), *Transmission characteristics of optical components and subsystems*. +- [ITU-T L.109.1] Recommendation ITU-T L.109.1 (2022), *Type II optical/electrical hybrid cables for access points and other terminal equipment*. +- [IEC 60794-2] Standard IEC 60794-2:2017, *Optical fibre cables – Part 2: Indoor cables - Sectional specification*. +- [IEC 60825-2] Standard IEC 60825-2:2021, *Safety of laser products – Part 2: Safety of optical fibre communication systems (OFCs)*. +- [IEC 61753-031-2] Standard IEC 61753-031-2:2014, *Fibre optic interconnecting devices and passive components – Performance standard – Part 031-2: Non-connectorized single-mode $1 \times N$ and $2 \times N$ non-wavelength-selective branching devices for Category C – Controlled environment*. + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +None. + +## 3.2 Terms defined in this Recommendation + +This Recommendation defines the following terms: + +**3.2.1 controller:** A module comprising one or more coordinators within the main fibre unit (MFU) that dynamically collects network information from different network interfaces within the MFU and makes control plane decisions for those network interfaces. + +**3.2.2 fibre in-premises (FIP) network:** An in-premises communication network that uses an indoor fibre distribution network to connect the residential gateway with remote communication devices, providing extended connectivity. + +**3.2.3 G.fin network:** The part of a FIP network that provides a connection between a main fibre unit (MFU) and one or more sub fibre units (SFU) using G.fin. A G.fin network enables network functionalities, including Wi-Fi data backhauling, Wi-Fi coordination, and network management. A G.fin network is defined between the A-interface in the G.fin transceiver located in the MFU and the A-interface in the G.fin transceiver in each of the FIP network SFUs. + +**3.2.4 G.fin transceiver:** A high speed optical communication module, consisting of a transmitter and a receiver. The G.fin transceiver is specified in the physical layer and data link layer Recommendations. + +**3.2.5 IFDN splitting ratio:** The number of lines into which the optical signal in the downstream direction is distributed in the indoor fibre distribution network (IFDN). + +NOTE – For the case when a single optical splitter is used, splitting ratio and IFDN splitting ratio will be the same. + +**3.2.6 indoor fibre distribution network (IFDN):** An in-premises optical fibre infrastructure. An IFDN can be entirely passive, constructed with one or multiple interconnected optical splitters, and contains other passive optical components such as combiners and filters. The IFDN can also support remote power feed functionality to SFUs by using optical and electrical hybrid cables (OEHC). + +**3.2.7 local coordinator:** A peer module within the SFU that communicates with the controller in the MFU, providing it with the necessary information and implementing the actions decided by the controller. + +**3.2.8 main fibre unit (MFU):** A network element that terminates the access network at its northbound interface, includes gateway functionality, and includes a G.fin transceiver that provides a medium dependent interface (MDI) to communicate with one or more connected sub fibre units over the IFDN. + +**3.2.9 maximum differential fibre length:** The maximum difference in length between the shortest and longest MFU-to-SFU link distance in the IFDN. + +**3.2.10 maximum fibre length:** The maximum length of fibre between the G.fin transceiver in the MFU (M-FTR) and any G.fin transceiver in an SFU (S-FTR) in the IFDN. + +**3.2.11 optical and electrical hybrid cable (OEHC):** A hybrid cable comprising an optical fibre and metallic conductors. + +**3.2.12 optical and electrical hybrid splitter (OEHS):** A hybrid splitter that supports simultaneous transmission of an optical signal and electrical power when used with OEHCs. + +**3.2.13 optical splitter:** A passive optical component that distributes the optical signal into multiple lines in the downstream direction and combines the optical signals from multiple lines into a single signal in the upstream direction. + +**3.2.14 optical splitter with remote power feed:** An optical splitter with OEHC connections to support remote power feed. + +**3.2.15 splitting ratio:** The number of lines into which an optical splitter distributes the optical signal in the downstream direction. + +**3.2.16 sub fibre unit (SFU):** A network element with a G.ftn transceiver that provides a medium dependent interface (MDI) to communicate with the MFU over the IFDN. An SFU normally has a built-in Wi-Fi access point (AP). + +# **4 Abbreviations and acronyms** + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|-------|--------------------------------------------| +| AES | Advanced Encryption Standard | +| ALG | Application Level Gateway | +| AP | Access Point | +| APP | Application | +| AR | Augmented Reality | +| BH | Backhaul | +| CPE | Customer Premises Equipment | +| DLL | Data Link Layer | +| DLNA | Digital Living Network Alliance | +| DTA | Dynamic Time Assignment | +| EMS | Element Management System | +| ESMC | Ethernet Synchronization Messaging Channel | +| ETH | Ethernet | +| FH | Fronthaul | +| FIP | Fibre In-premises | +| HD | High-Definition | +| HDTV | High-Definition Television | +| HPNA | Home Phoneline Networking Alliance | +| IFDN | Indoor Fibre Distribution Network | +| IoT | Internet of Things | +| IP | Internet Protocol | +| IPTV | Internet Protocol TV | +| L2 | Layer 2 | +| LAN | Local Area Network | +| MAC | Media Access Control | +| MCE | MFU Controller Entity | +| MDI | Medium Dependent Interface | +| M-FTR | G.ftn transceiver in the MFU | +| MFU | Main Fibre Unit | +| MME | MFU Management Entity | + +| | | +|-------|----------------------------------------| +| MoCA | Multimedia over Coax Alliance | +| NAS | Network Attached Storage | +| NT | Network Terminal | +| ODN | Optical Distribution Network | +| OEHC | Optical and Electrical Hybrid Cable | +| OEHS | Optical and Electrical Hybrid Splitter | +| OLT | Optical Line Termination | +| ONU | Optical Network Unit | +| OPL | Optical Path Loss | +| P2MP | Point to Multi Point | +| PC | Personal Computer | +| PHY | Physical Layer | +| PLC | Power Line Communication | +| PMD | Physical Media Dependent | +| PON | Passive Optical Network | +| QoS | Quality of Service | +| RMS | Remote Management System | +| SA | System Architecture | +| SAP | Service Access Point | +| SME | SFU Management Entity | +| SCE | SFU Coordinator Entity | +| SFU | Sub Fibre Unit | +| S-FTR | G.fin transceiver in an SFU | +| STA | Station | +| TC | Transmission Convergence | +| TV | Television | +| UPnP | Universal Plug and Play | +| VR | Virtual Reality | +| VLC | Visible Light Communication | +| VoIP | Voice Over IP | +| WLAN | Wireless Local Area Network | +| xPON | x Passive Optical Network | +| XR | Extended Reality | + +# 5 Conventions + +None. + +# 6 Architecture of the G.fin network + +## 6.1 Network architecture + +Figure 6-1 shows a G.fin based fibre in-premises (FIP) network. Such a network includes a main fibre unit (MFU), an indoor fibre distribution network (IFDN), and one or more sub fibre units (SFUs). The MFU is directly connected to an access network, such as an x passive optical network (PON) on its northbound interface. The MFU and SFUs are connected to the IFDN using G.fin transceivers. The MFU and SFUs provide wireless (e.g., wireless local area network (WLAN)) and wireline network (e.g., Ethernet) interfaces for end user devices (e.g., laptops, smartphones). Adaptation devices such as set top boxes can also be connected to the MFU or SFUs to provide network services (e.g., Internet protocol TV) to end user devices (e.g., television). The MFU is the converging point for data, management, and control, providing point to multi point (P2MP) optical connections to SFUs. It is the network terminal (NT) of the access network and the starting point of the in-premises network. + +![Figure 6-1: Illustration of a G.fin-based FIP network. The diagram shows a Central office connected to an MFU, which is part of an Access network (e.g. xPON). The MFU is connected to an IFDN (Indoor Fibre Distribution Network) via a yellow splitter. The IFDN connects to three SFUs (Sub Fibre Units). Each SFU is connected to an End-user device via a wireless link. The MFU and SFUs are part of the Fibre in premises network. The diagram is labeled G.9940(23).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 6-1: Illustration of a G.fin-based FIP network. The diagram shows a Central office connected to an MFU, which is part of an Access network (e.g. xPON). The MFU is connected to an IFDN (Indoor Fibre Distribution Network) via a yellow splitter. The IFDN connects to three SFUs (Sub Fibre Units). Each SFU is connected to an End-user device via a wireless link. The MFU and SFUs are part of the Fibre in premises network. The diagram is labeled G.9940(23). + +Figure 6-1 – Illustration of a G.fin-based FIP network + +A G.fin-based FIP network can be used in one of two main environments, a home network or a small and medium enterprise, supporting different services and requiring dedicated network capabilities. + +### 6.1.1 Home environment + +![Figure 6-2: Application of G.fin in a home environment. The diagram shows a Central office connected to an MFU via an FTTH (Fibre to the Home) line. The MFU is connected to an IFDN (Indoor Fibre Distribution Network) via a 1:4~16 splitter. The IFDN connects to three SFUs (Sub Fibre Units) located in Bedroom 1, Bedroom 2, and Bedroom 3. Each SFU is connected to an End-user device via a wireless link. The End-user devices include VR/AR, Mobile phone, and HD camera. The MFU and SFUs are part of the Fibre in premises network (< 100 m). The diagram is labeled G.9940(23).](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +Figure 6-2: Application of G.fin in a home environment. The diagram shows a Central office connected to an MFU via an FTTH (Fibre to the Home) line. The MFU is connected to an IFDN (Indoor Fibre Distribution Network) via a 1:4~16 splitter. The IFDN connects to three SFUs (Sub Fibre Units) located in Bedroom 1, Bedroom 2, and Bedroom 3. Each SFU is connected to an End-user device via a wireless link. The End-user devices include VR/AR, Mobile phone, and HD camera. The MFU and SFUs are part of the Fibre in premises network (< 100 m). The diagram is labeled G.9940(23). + +Figure 6-2 – Application of G.fin in a home environment + +NOTE – Figure 6-2 is modified from Figure 13 of [b-ETSI GR F5G 008] with a change of terminology. + +Figure 6-2 shows the application (APP) of G.fin in a home environment. From the central office to the MFU, there is an access network system, such as an XG(S)-PON system (FTTH) that can deliver gigabit access throughputs from the service provider. From the MFU, a G.fin-based FIP network and Wi-Fi are used for the connectivity of end user devices within the home network. + +Within the home, devices such as mobile phones, high-definition televisions (HDTV), HD surveillance cameras and virtual reality (VR) / augmented reality (AR) head mounted displays need end to end stable connections to offer a good quality experience. The MFU establishes connections with the Wi-Fi access points (included in the SFUs) located in several rooms of the home through the G.fin network. In order to optimize the performance of the Wi-Fi network, coordination of the Wi-Fi access points (APs) is supported by the G.fin network. + +[b-ITU-T GSTP-FTTR] defines the detailed use cases and requirements for using G.fin for home applications, including in-home Wi-Fi backhauling, broadband deployment for the dense apartment building, Internet of things (IoT) support of smart homes, low latency services, network slicing, and east-west data transmission. + +### 6.1.2 Business environment + +![Diagram illustrating the application of G.fin in a small and medium enterprise (SME) environment. The diagram shows a Carrier network connected to an OLT, which is connected to an SME internal network via an MFU. The MFU is connected to a Splitter, which branches into an IFDN. The IFDN connects to three areas: Office area, Manager room, and Meeting room. Each area contains an SFU (Small Form-factor Unit) connected to various end-user devices. The Office area includes a laptop, printer, and smartphone. The Manager room includes a laptop and smartphone. The Meeting room includes a laptop, smartphone, and a video conferencing camera. The diagram is labeled G.9940(23).](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Diagram illustrating the application of G.fin in a small and medium enterprise (SME) environment. The diagram shows a Carrier network connected to an OLT, which is connected to an SME internal network via an MFU. The MFU is connected to a Splitter, which branches into an IFDN. The IFDN connects to three areas: Office area, Manager room, and Meeting room. Each area contains an SFU (Small Form-factor Unit) connected to various end-user devices. The Office area includes a laptop, printer, and smartphone. The Manager room includes a laptop and smartphone. The Meeting room includes a laptop, smartphone, and a video conferencing camera. The diagram is labeled G.9940(23). + +**Figure 6-3 – Application of G.fin in a small and medium enterprise environment** + +NOTE – Figure 6-3 is modified from Figure 15 of [b-ETSI GR F5G 008] with the change of terminology. + +Figure 6-3 shows an example of the application of G.fin in a small and medium enterprise environment. Optical and electric hybrid cable (OEHC) may be used for remote powering of SFUs, facilitating flexible deployment in various business sites, such as office areas, manager rooms, and meeting rooms. Compared with the home environment, more diversified device types and a larger number of end user devices are connected to the MFU and SFUs. + +[b-ITU-T G Suppl. 78] defines the detailed use cases and requirements for using G.fin for small and medium enterprise applications, including live applications, small offices, smart service halls, classrooms in schools, business buildings, indoor leisure and entertainment, advertising design and virtual effect processing, workshops and smart community. + +## 6.2 Reference models + +### 6.2.1 G.fin network + +A G.fin network is composed of an MFU, an IFDN and SFU(s) as illustrated in Figure 6-4. By making use of splitters for different fibre deployment solutions, an IFDN can cope with a variety of + +topologies, such as 1-tier symmetrical splitting, 2-tier symmetrical splitting and cascaded asymmetrical splitting. + +As shown in Figure 6-5, if there is only one SFU to be connected, the IFDN might not include any splitters, creating a direct link between the MFU and SFU. + +Traffic (including data and management information) transmission over the IFDN includes: + +- downstream transmissions from the MFU to the SFU(s); +- upstream transmissions from the SFU(s) to the MFU. + +Transmission between SFU(s) is first switched in the MFU at the layer 2 (L2)+ layer and is beyond the scope of this Recommendation. Direct exchange between SFU(s) at lower layers (PHY or DLL) is left for further study. + +Downstream and upstream transmission takes place over the same fibre and optical components operating in duplex. + +An IFDN may support remote powering of the SFUs, simultaneously distributing optical signals and electrical power to the SFU(s) using OEHCs and OEHSs. The power source connected to the OEHCs can be located in the MFU, in an OEHS, or in an external component. + +![Diagram of a G.fin network with multiple SFUs. A Central office connects to an MFU via an Access technology (e.g., xPON). The MFU is connected to an IFDN (dashed box) containing two splitters. The first splitter has one output connected to an SFU and another output connected to the second splitter. The second splitter has two outputs connected to two more SFUs. All three SFUs are connected to End user devices (e.g., tablet, PC) via Wireless and/or wireline interfaces. The MFU, IFDN, and SFUs are collectively labeled as a 'G.fin based FIP network'. A 'G.fin network' label spans from the MFU to the SFUs. A legend at the bottom defines the line types: solid for Fibre, dash-dot for Optional remote power, and dashed for LAN technology (e.g., Wi-Fi). The diagram is labeled G.9940(23).](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +Diagram of a G.fin network with multiple SFUs. A Central office connects to an MFU via an Access technology (e.g., xPON). The MFU is connected to an IFDN (dashed box) containing two splitters. The first splitter has one output connected to an SFU and another output connected to the second splitter. The second splitter has two outputs connected to two more SFUs. All three SFUs are connected to End user devices (e.g., tablet, PC) via Wireless and/or wireline interfaces. The MFU, IFDN, and SFUs are collectively labeled as a 'G.fin based FIP network'. A 'G.fin network' label spans from the MFU to the SFUs. A legend at the bottom defines the line types: solid for Fibre, dash-dot for Optional remote power, and dashed for LAN technology (e.g., Wi-Fi). The diagram is labeled G.9940(23). + +Figure 6-4 – G.fin network with multiple SFU(s) + +![Diagram of a G.fin network with a single SFU. The diagram shows a Central office connected to an MFU via an Access technology (e.g., xPON). The MFU is connected to an IFDN, which is connected to an SFU. The SFU is connected to End user devices (e.g., tablet, PC) via Wireless and/or wireline interfaces. The G.fin network is shown as a dashed line between the MFU and the SFU. The G.fin based FIP network is shown as a solid line between the MFU and the SFU. A legend at the bottom defines the line types: Fibre (solid line), Optional remote power, MFU provides power to SFUs through IFDN (dash-dot line), and LAN technology (e.g., Wi-Fi) (dashed line). The diagram is labeled G.9940(23) at the bottom right.](4801720824e4b5e2361a5564f91cfb70_img.jpg) + +Diagram of a G.fin network with a single SFU. The diagram shows a Central office connected to an MFU via an Access technology (e.g., xPON). The MFU is connected to an IFDN, which is connected to an SFU. The SFU is connected to End user devices (e.g., tablet, PC) via Wireless and/or wireline interfaces. The G.fin network is shown as a dashed line between the MFU and the SFU. The G.fin based FIP network is shown as a solid line between the MFU and the SFU. A legend at the bottom defines the line types: Fibre (solid line), Optional remote power, MFU provides power to SFUs through IFDN (dash-dot line), and LAN technology (e.g., Wi-Fi) (dashed line). The diagram is labeled G.9940(23) at the bottom right. + +**Figure 6-5 – G.fin network with single SFU** + +### 6.2.2 Functional architecture of a G.fin-based FIP network + +A communication link is established over the IFDN between the MFU and SFU(s) using G.fin transceivers. As shown in Figure 6-6, the functional architecture of a G.fin-based FIP network consists of a management plane, a control plane, and a data plane. The MFU conducts centralized management (via MFU management entity) and control (via MFU controller entity) on the entire G.fin network, managing and configuring the G.fin transceiver in the SFU via the SFU management entity (SME) and the SFU coordinator entity (SCE), respectively. + +#### a) Management plane + +The MFU should be able to manage the SFU(s) and maintain the G.fin transceiver through its southbound management interface. The MFU should report information for the entire G.fin network to the management system through its northbound interface. The management system monitors carriers' assets and device status and optimizes the G.fin network. + +The northbound management between the G.fin network and management system is beyond the scope of this Recommendation. It can be done using existing protocols such as [b-BBF TR-069] or [b-BBF TR-369], or by a proprietary solution provided by the service operator. The management between G.fin transceivers (such as quality of service configuration, device upgrade, device restart, and default setting restoration) shall follow the G.fin management Recommendation. G.fin shall provide a low latency channel to convey management information for other technologies, such as Wi-Fi. + +#### b) Control plane + +The G.fin transceiver in the MFU (M-FTR) collects G.fin-based FIP network information in real time through a centralized control mechanism. The MFU should use this information to define transmission strategies for the entire network. The MFU should use this mechanism to convey coordination information to the wireless interfaces in the SFU(s) and to define transmission policies in the FIP network to implement coordination between the optical and wireless networks. + +#### c) Data plane + +The data plane provides communication channels for exchanging service data, management data, and control data to ensure normal operation of G.fin connection and exchange control information between the M-FTR and the S-FTR(s). + +![Functional architecture of a G.fin-based FIP network diagram showing Management, Control, and Data planes across OLT, MFU, and SFU components.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg) + +The diagram illustrates the functional architecture of a G.fin-based FIP network, organized into three horizontal planes: Management plane, Control plane, and Data plane. + +- Management plane:** A Management system is connected to the MFU. Inside the MFU, the MME (Management and Control Entity) is connected to the Management system. The SME (Service Management Entity) in the SFU is also connected to the Management system. +- Control plane:** The MCE (Management and Control Entity) in the MFU and the SCE (Service Control Entity) in the SFU are connected via a Centralized coordination link. Downlink command/request flows from the MME to the MCE, and Uplink report flows from the SCE to the SME. Both MCE and SCE are part of a Management and control block. +- Data plane:** The OLT (Optical Line Terminal) is connected to the ODN (Optical Distribution Network), which in turn connects to the ONU (Optical Network Unit) in the MFU. The ONU is connected to an L2+ layer, which is connected to the DLL (Data Link Layer) and PHY (Physical Layer) of the M-FTR (Media Fusion Transceiver). The M-FTR is connected to the IFDN (Inter-Fiber Distribution Network). The IFDN connects to the S-FTR (Service Fusion Transceiver) in the SFU. The S-FTR contains its own PHY, DLL, L2+, Wi-Fi, and ETH (Ethernet) components. The MFU also contains ETH and Wi-Fi components connected to its L2+ layer. The SFU's L2+ layer is connected to its Wi-Fi and ETH components. + +Reference: G.9940(23) + +Functional architecture of a G.fin-based FIP network diagram showing Management, Control, and Data planes across OLT, MFU, and SFU components. + +**Figure 6-6 – Functional architecture of a G.fin-based FIP network** + +NOTE – G.fin network transmits service data based on a point-to-multipoint (P2MP) fibre topology. East-west data communication between G.fin transceivers is done by the MFU. + +## 6.3 Protocol reference model + +The protocol stack diagram of the data service is shown in Figure 6-7. In the MFU, Ethernet frames are bridged/routed through L2+ between the xPON transmission convergence (TC) layer and the G.fin DLL. Other access technologies may also be used to support the uplink of the G.fin-based FIP network. In the SFU, Ethernet (ETH) frames are bridged between the G.fin DLL and the Ethernet/Wi-Fi media access control (MAC) layer. + +It should be noted that there are several different interfaces that can take the place of an Ethernet/Wi-Fi MAC and PHY. These include the power line communication (PLC), visible light communication (VLC), multimedia over coax alliance (MoCA), home phoneline networking alliance (HPNA), and perhaps others yet to be devised. However, due to the Ethernet's pervasive nature, these alternative protocols are defined so that they operate in a way nearly the same as the Ethernet. + +G.fin transceivers are composed of a G.fin PHY and a G.fin DLL including their respective functionalities. G.fin transceivers in the MFU and SFUs are connected by IFDN. The G.fin PHY and G.fin DLL and corresponding management functions are specified in other Recommendations. + +![Figure 6-7: Protocol reference model of G.fin-based FIP network. The diagram shows two main components: MFU (Media Flow Unit) and SFU (Station Flow Unit). The MFU is connected to an OLT via a fibre link. It contains an L2+ layer, a PON TC, a PON PMD, a DLL, and a PHY. The SFU contains an L2 bridge, a MAC (ETH/Wi-Fi), and a PHY (ETH/Wi-Fi). Both units have a G.fin DLL and a G.fin PHY layer. The G.fin PHY layers of both units are connected to an IFDN (In-Premises Distribution Network). The IFDN is connected to end user devices via wireless/wireline links. The diagram is labeled G.9940(23).](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 6-7: Protocol reference model of G.fin-based FIP network. The diagram shows two main components: MFU (Media Flow Unit) and SFU (Station Flow Unit). The MFU is connected to an OLT via a fibre link. It contains an L2+ layer, a PON TC, a PON PMD, a DLL, and a PHY. The SFU contains an L2 bridge, a MAC (ETH/Wi-Fi), and a PHY (ETH/Wi-Fi). Both units have a G.fin DLL and a G.fin PHY layer. The G.fin PHY layers of both units are connected to an IFDN (In-Premises Distribution Network). The IFDN is connected to end user devices via wireless/wireline links. The diagram is labeled G.9940(23). + +**Figure 6-7 – Protocol reference model of G.fin-based FIP network** + +NOTE – The G.fin PHY sets requirements for the IFDN but specification of the IFDN is beyond the scope of the G.fin PHY Recommendation. + +## 6.4 Centralized coordination network architecture + +G.fin-based FIP networks intend to provide quality-assured in-premises network service to end users. To leverage the new capabilities of wireless links (e.g., Wi-Fi new deterministic MAC functions), a G.fin network shall support the coordination of resources and access to the channel between fibre links (i.e., using G.fin transceiver) and wireless links. Figure 6-8 shows a centralized coordination network architecture. + +The MFU contains a controller that dynamically collects the network transmission necessities and characteristics (data buffer status, traffic priority, latency requirements, etc.), identifies the network environment (such as channel status between the MFU and the SFU(s), interferences, etc.) and creates a strategy to coordinate the behaviour of the different networks connected to it. Due to this controller, fast network operation and control, including ordered medium access, global handover, and real-time link visibility can be achieved. + +The MFU is a system level device (shown in Figure 6-8), that includes a G.fin transceiver, a local area network (LAN) switch, a controller, and other related functionalities. + +NOTE – An MFU is equivalent to a residential gateway (RGW). + +![Diagram of Centralized coordination network architecture showing MFU, SFU, and End user device components and their interactions.](8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg) + +The diagram illustrates a centralized coordination network architecture. At the top, an **Access network** is connected to an **MFU** (Media Flow Unit). The MFU contains an **NT** (Network Terminal) connected to a **Controller**. The Controller is connected to three interfaces: **Eth** (Ethernet), **Wi-Fi AP** (Access Point), and **M-FTR** (Media Flow Translator). A dashed line with a triangle indicates a connection from the M-FTR to a second, identical setup below. + +Each setup consists of an **SFU** (Service Flow Unit) and an **End user device**. The SFU contains a **Local coordinator** connected to **S-FTR** (Service Flow Translator), **Eth**, and **Wi-Fi AP**. The End user device contains a **User app** connected to a **Wi-Fi STA** (Station). The Wi-Fi STA is connected to the Wi-Fi AP of the SFU. + +Three callouts provide additional information: + +- One or more coordinators that:** + - Coordinate AP transmissions + - Coordinate BH/FH characteristics +- Wi-Fi management/control SAP (Defined elsewhere)** + - QoS channels + - Scheduling/Time alignment + - Capabilities +- G.fin management/control SAP (Defined in G.fin Recommendation)** + - QoS channels + - Scheduling/Time alignment + - Capabilities + +The diagram is labeled **G.9940(23)** at the bottom right. + +Diagram of Centralized coordination network architecture showing MFU, SFU, and End user device components and their interactions. + +**Figure 6-8 – Centralized coordination network architecture** + +### 6.4.1 Centralized status collection + +Based on the quality of service (QoS) requirements of the services over the network, the controller in the MFU initiates requests to the functional modules in the SFU(s) (Wi-Fi, LAN switch, data buffer, etc.). The SFU(s) receiving the requests can collect the network status information and provide feedback to the MFU. The controller behaviour is vendor discretionary and is beyond the scope of the G.fin Recommendations. The controller in the MFU may also dynamically forward control commands over the G.fin network to the local coordinator in each SFU. The real-time configuration of the network interfaces by the controller within the MFU is vendor discretionary. The requests and collection of feedback over the G.fin network shall be carried over a latency controlled channel (see clause 6.4.3). + +### 6.4.2 Centralized network control + +The controller may have controlling functionalities over the fibre link, wireless link, etc. For example, the controller may calculate the optimal air time/frequency/space resources to optimize the use of the air interface. The controller may suggest transmission opportunities to be used over the fibre link to support QoS requirements of selected services over the network. The controller may coordinate global handover and data path switching. The control information exchanged between the coordinators in the MFU and the local coordinator in each SFU is addressed in a separate G.fin Recommendation. + +### 6.4.3 Latency controlled transmission mechanism + +The G.fin PHY and data link layer (DLL) shall support a priority specific information channel to support latency controlled transmissions, and to enable the upper layers to control the whole network access to the medium. Due to different control requirements of the technologies that can be connected to a G.fin-based FIP network, the round-trip latency on the channel should be less than 64 µs for extremely high demand coordination such as air interface signalling coordination. + +# 7 Service requirements + +## 7.1 Service types + +A G.fin network is required to support various services for residential subscribers, business customers, Wi-Fi backhauling, and other applications leveraging its high bit-rate capabilities. Furthermore, a G.fin network intends to provide better latency and jitter performance. + +The services supported by a G.fin network should include: + +- High-speed indoor networking: support high-speed networking of wired or wireless terminals (personal computer (PC), network attached storage (NAS), pad, mobile phone, etc.) within the in-premises. +- High-speed Internet: provide users with broadband Internet access services. +- High quality video: (IPTV, extended reality (XR), etc.): support high-definition (HD) IPTV and high-quality AR/VR or hologram transmissions in the future. +- Voice over IP (VoIP): provide users with IP telephony services. +- Others: support multiple interconnection protocols or interfaces such as a universal plug and play (UPnP), digital living network alliance (DLNA), and application level gateway (ALG) for cloud storage, multi-screen interaction, and IoT services. + +## 7.2 Mean signal transfer delay + +A G.fin network should accommodate services that require a mean signal transfer delay $\leq 1.5$ ms, between the A-interface of the M-FTR and the A-interface of the S-FTR(s). + +## 7.3 Maximum Ethernet packet size + +A G.fin network shall support Ethernet jumbo frames with lengths beyond 2 000 bytes and up to 9 000 bytes. If jumbo frames beyond 2 000 bytes are used for non-delay-sensitive services on the same IFDN, the delay-sensitive services shall not be degraded by jumbo frame transport. + +## 7.4 Synchronization features and quality + +A G.fin network shall provide mechanisms to allow the coordination of optical and wireless links, since accurate synchronization and low latency may be required. For this, the MFU may receive a high-quality timing clock to serve as a master timing source for the SFUs. The SFUs can use accurate timing/synchronization to feed the wireless interface and application requirements. + +Aspects of clock propagation, frequency and time of day synchronization scenarios, and Ethernet synchronization messaging channel (ESMC) messages transport over a G.fin network with [b-IEEE 1588], are left for further study. + +# 8 Physical layer requirements + +The G.fin PHY shall be specified to work over a single-fibre supporting bidirectional transmission. + +## 8.1 Bit rates + +G.fin should specify the following nominal line rate combinations per wavelength channel: + +- approximately 10 Gbit/s in the downstream and 10 Gbit/s in the upstream; +- approximately 2.5 Gbit/s in the downstream and 2.5 Gbit/s in the upstream. + +Other nominal line rate combination options are for further study. + +## 8.2 Maximum number of connected S-FTRs + +G.fin may be used in different environments. These environments usually need to support the following maximum number of connected S-FTRs: + +- 8 for the home environment, using an optical link type Ra; +- 32 for the small and medium enterprise environment, using an optical link type Rb. + +To cover these environments, G.fin M-FTRs shall support the connection of: + +- 8 S-FTRs at the physical layer when using an optical link type Ra; +- 32 S-FTRs at the physical layer when using an optical link type Rb; +- 64 S-FTRs at the data link layer. + +## 8.3 Fibre length + +The G.fin PHY shall support: + +- a maximum fibre length of at least 1 km; +- a maximum differential fibre length of up to 1 km. + +The G.fin DLL shall support: + +- a maximum fibre length of at least 2 km; +- a maximum differential fibre length of up to 2 km. + +## 8.4 Optical link budget + +The optical link budget mainly depends on the splitting ratio and splitting architecture. A G.fin transceiver shall support at least one of the two optical link types defined in Table 8-1. + +The detailed specifications of these two types will be addressed in the G.fin-PHY Recommendation. + +## 8.5 Operating wavelength + +G.fin transceivers shall use the wavelengths defined in Table 8-1, depending on the optical link type they are operating on. + +A G.fin transceiver operating with an optical link type Rb at the 10/10 Gbit/s line rate shall operate at one of the two specified wavelengths (Option 1 or 2) as specified in Table 8-1. + +**Table 8-1 – Overall relationship between optical link budget and wavelength set** + +| Optical link type | Optical link budget | Typical IFDN splitting ratio | Upstream / downstream wavelength set | | +|-------------------|----------------------------------------|------------------------------|----------------------------------------------------------|-----------------------------------------------------------------------| +| | | | 2.5/2.5 Gbit/s | 10/10 Gbit/s | +| Ra | 0-18 dB (home) | 1:8 | Up:
$1\,310 \pm 10$ nm
Down:
$1\,490 \pm 10$ nm | For further study | +| Rb | 13-28 dB (small and medium enterprise) | 1:32 | Up:
$1\,310 \pm 10$ nm
Down:
$1\,490 \pm 10$ nm | Option 1:
Up:
$1\,310 \pm 10$ nm
Down:
$1\,490 \pm 10$ nm | + +**Table 8-1 – Overall relationship between optical link budget and wavelength set** + +| Optical link type | Optical link budget | Typical IFDN splitting ratio | Upstream / downstream wavelength set | | +|-------------------|---------------------|------------------------------|--------------------------------------|-----------------------------------------------------------------------| +| | | | 2.5/2.5 Gbit/s | 10/10 Gbit/s | +| | | | | Option 2:
Up:
$1\,270 \pm 10$ nm
Down:
$1\,577 \pm 10$ nm | + +NOTE – Optical link type Ra is typically used in the home environment while type Rb is typically used in small and medium enterprise environments. + +Other wavelength combination options are for further study. + +## 8.6 Indoor fibre distribution network (IFDN) + +### 8.6.1 Fibre + +The G.fin PHY shall support communication over IFDNs built using optical fibre of G.657A or G.657B types (see [ITU-T G.657]). + +NOTE – These optical fibres have been chosen to overcome the bending loss due to complex cabling topologies during in-premises fibre deployments. + +### 8.6.2 Optical cable + +The G.fin PHY shall support communication over IFDNs built using passive optical cable (see [IEC 60794-2]) and OEHCs (see [ITU-T L.109.1]). + +NOTE – Transparent / invisible optical cables should be used in open field deployment, such as sticking to a wall. + +### 8.6.3 Optical splitter + +The G.fin network shall support the use of symmetric or asymmetric optical splitters in the IFDN (see Appendix I). + +NOTE – The splitting ratio of optical splitters depends on the deployment. The utilization of optical splitters is solution based and depends on the deployment scenario, splitting ratio, etc. + +### 8.6.4 Optical and electrical hybrid splitter (OEHS) + +Figure 8-1 shows an OEHS. G.fin shall support the use of OEHSs in an optical/electrical hybrid IFDN. + +NOTE – Such a splitter integrates the passive optical splitter (see [IEC 61753-031-2]) and the electrical power distribution function, enabling the capability to convey optical signals and power energy from the MFU to SFUs. The splitter provides a single physical connector for optical and electrical transmission and adapts to the connector of the optical and electrical hybrid cable (OEHC). + +![Diagram of an Optical Ethernet Hybrid Connector System (OEHS). At the top, an 'External power source (Optional)' is connected via a 'DC connector' to a power rail. Below this, an 'Optical splitter' (represented by a yellow triangle) is shown. On the left, an 'OEHC' (Optical Ethernet Hybrid Connector) is connected to the optical splitter. On the right, multiple 'Connector' blocks are shown, each connected to the optical splitter and having an 'OEHC' output. A legend at the bottom indicates that double lines represent 'Conductors' and single lines represent 'Fibre'. The reference 'G.9940(23)' is noted in the bottom right corner.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg) + +Diagram of an Optical Ethernet Hybrid Connector System (OEHS). At the top, an 'External power source (Optional)' is connected via a 'DC connector' to a power rail. Below this, an 'Optical splitter' (represented by a yellow triangle) is shown. On the left, an 'OEHC' (Optical Ethernet Hybrid Connector) is connected to the optical splitter. On the right, multiple 'Connector' blocks are shown, each connected to the optical splitter and having an 'OEHC' output. A legend at the bottom indicates that double lines represent 'Conductors' and single lines represent 'Fibre'. The reference 'G.9940(23)' is noted in the bottom right corner. + +**Figure 8-1 – OEHS** + +# 9 System level requirements + +## 9.1 Power saving and energy efficiency + +The G.fin PHY and DLL shall support power saving modes during specified time periods. Service quality and user experience should not be affected when using these power saving modes. + +NOTE – Power saving modes may be used to reduce power consumption during periods where service requirements are limited (e.g., during the daytime when home networks are less used). + +## 9.2 Security functions + +Since a point to multi-point architecture is used in G.fin networks, the medium (fibre) is shared by all SFUs. Each SFU receives the downstream data for all SFUs through this shared fibre, so it is important to protect the shared fibre against impersonation, spoofing and snooping of data. + +The G.fin DLL should support at least the following mechanisms to protect against impersonation: + +- identification of the serial number / password / MAC address of the SFU; +- authentication of the customer premises equipment (CPE); +- a strong authentication mechanism such as the digital certificate authentication. + +To protect against snooping at the SFUs, all unicast data transmitted by the M-FTR should be encrypted with a strong and well characterized algorithm (e.g., advanced encryption standard (AES)). Therefore, the G.fin DLL shall specify a reliable key exchange mechanism to start an encrypted communication. + +Authentication, identification, and encryption shall be optional functions that may be disabled by the users. The G.fin DLL should provide user-friendly procedures for setting up a secure network. + +## 9.3 Dynamic time assignment + +The M-FTR shall support dynamic time assignment (DTA) for efficient sharing of upstream time among the connected SFUs. The DTA algorithms running on a G.fin transceiver are vendor discretionary and are beyond the scope of the G.fin Recommendations. + +## 9.4 Quality of service (QoS) + +Quality of service (QoS) is a measure of the quality of delivery of services in the network, placing requirements on the transmission and queuing of traffic. Detailed methods for achieving QoS (such as priority based, or parameter based) in a G.fin network are left for further study. + +## 9.5 Eye safety + +Necessary mechanisms shall be provided to ensure that no eye damage is caused to the end users that are unaware of the risks, especially if the fibre is terminated inside the home. G.fin optical elements need to conform to the Class 1 defined in [IEC 60825-2]. + +# 10 System management functions + +## 10.1 Management schemes + +It is highly desirable from the network operation perspective to manage a G.fin network, with a similar approach to existing management platforms of access and home networks. A G.fin network may be managed in parallel via two paths as shown in Figure 10-1: + +NOTE – Avoiding management conflicts when using multiple management paths is left for further study. + +### 1) Using OMCI + +A G.fin network may be managed using OMCI (see [b-ITU-T G.988]) over the "I2" interface as shown in Figure 10-1. In this case, the MFU acts as an optical network unit (ONU) for registration and provisioning. The MFU uses the information received through OMCI to manage its own G.fin transceiver and the overall G.fin-based FIP network. + +NOTE – The optical line termination (OLT) is configured by the element management system (EMS), which is out of the scope of this Recommendation. + +The method to manage a G.fin transceiver from its SFUs via OMCI commands issued by the OLT is left for further study. + +### 2) Internet protocol (IP) path + +With the establishment of a link to the access network between the MFU and OLT, G.fin transceivers in the MFU and SFUs can be managed by existing IP based protocols like [b-BBF TR-069] or [b-BBF TR-369], or by a vendor-discretionary solution. + +Several interfaces are defined in Figure 10-1: + +- I1: The southbound management interface between the MFU and SFUs. The MFU manages the SFUs and maintains the G.fin link through I1. MFU management entity (MME) and SME are the management entities in the MFU and SFUs, respectively. +- I2: The northbound management interface between the OLT and the G.fin-based FIP network. The OMCI protocol is used at I2. +- I3: The northbound management interface between an operator's remote management system (RMS) and the G.fin-based FIP network. An IP based protocol is used at I3. + +![Diagram of management schemes of G.fin-based FIP network. At the top, EMS and RMS are connected to an OLT. The OLT is connected via interface I2 to an MFU and via interface I3 to an ONU. The MFU and ONU are part of a G.fin-based FIP network (indicated by a dashed box). Inside the network, the ONU is connected to an OMCI agent and a TR-069/369 agent, which are both connected to a Management connection. The Management connection is connected to an MME, which is connected to an M-FTR. The M-FTR is connected via interface I1 to a Fibre connection. The Fibre connection is connected to three SFUs. One SFU is connected to an S-FTR, which is connected to an SME. The other two SFUs are connected to the Fibre connection. The diagram is labeled G.9940(23).](c914f51f4427bc672dd0526cfc90ebe9_img.jpg) + +Diagram of management schemes of G.fin-based FIP network. At the top, EMS and RMS are connected to an OLT. The OLT is connected via interface I2 to an MFU and via interface I3 to an ONU. The MFU and ONU are part of a G.fin-based FIP network (indicated by a dashed box). Inside the network, the ONU is connected to an OMCI agent and a TR-069/369 agent, which are both connected to a Management connection. The Management connection is connected to an MME, which is connected to an M-FTR. The M-FTR is connected via interface I1 to a Fibre connection. The Fibre connection is connected to three SFUs. One SFU is connected to an S-FTR, which is connected to an SME. The other two SFUs are connected to the Fibre connection. The diagram is labeled G.9940(23). + +**Figure 10-1 – An example of management schemes of G.fin-based FIP network** + +## 10.2 Management functions + +The management of G.fin network is achieved by the collaboration of I1 and I2/I3. The management platform (such as EMS or RMS) triggers the management request through I2/I3 whilst I1 may assist in completing the various management functions. + +The following management functions should be included: + +- a) System visualization: to support visualization of key information of the G.fin network (e.g., the topology of the G.fin network, status of G.fin transceivers), and to transport management data gathered by the MFU/SFUs (e.g., interference metrics of Wi-Fi). +- b) System configuration: to support configuration of the G.fin transceivers and related network services, (e.g., authentication of G.fin transceivers at the MFU and SFU(s)), and to transport management information to the SFUs for the management of other interfaces (e.g., configuration of Wi-Fi, VLAN and QoS parameters). +- c) Collection of system performance metrics: to support performance management of the G.fin network (e.g., collecting performance metrics) and to transport performance metrics of other interfaces connected to the SFUs (e.g., collecting performance metrics of wireless/LAN interfaces). +- d) Fault management: to support fault management of the G.fin network (e.g., processing alarms from the G.fin network, diagnosing device and service faults). + +- e) Security management: to support security management of the G.fin network, e.g., authentication and authorization to management system users, and audit of management operations. + +# Appendix I + +## Optical link budget analysis for G.fin network + +(This appendix does not form an integral part of this Recommendation.) + +## I.1 Optical path loss factors + +The factors affecting the calculation of the optical path loss (OPL) for a G.fin network are optical fibre loss (including from splices), optical connector losses, and power splitter losses according to the following formulae. + +$$OPL_{max} = FibreLoss_{max} + ConnLoss_{max} + Loss_{PSmax} \quad (I.1)$$ + +$$OPL_{min} = FibreLoss_{min} + ConnLoss_{min} + Loss_{PSmin} \quad (I.2)$$ + +Figure I.1 shows the case with a single power splitter. For this case, $Loss_{PSmax}$ is the maximum insertion loss of the splitter for a given splitting ratio according to Table I.1, and the indoor fibre distribution network (IFDN) splitting ratio is the same as the splitting ratio. + +![Diagram of optical path loss for a G.fin network with a single power splitter. It shows an MFU (green box) connected via a connector (red bar) to a Splitter (blue triangle). The Splitter has multiple output paths, one of which is shown leading to an SFU (green box) via another connector (red bar). The diagram labels three components of optical path loss: Optical connector loss (ConnLoss) at the input and output connectors, Power splitter loss (Loss_PS) at the splitter, and Optical fibre loss (FibreLoss) along the fibre segments. A legend indicates that solid yellow lines represent Fibre, red bars represent Connectors, and dashed blue lines represent the Optical path. The diagram is labeled G.9940(23).](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +Diagram of optical path loss for a G.fin network with a single power splitter. It shows an MFU (green box) connected via a connector (red bar) to a Splitter (blue triangle). The Splitter has multiple output paths, one of which is shown leading to an SFU (green box) via another connector (red bar). The diagram labels three components of optical path loss: Optical connector loss (ConnLoss) at the input and output connectors, Power splitter loss (Loss\_PS) at the splitter, and Optical fibre loss (FibreLoss) along the fibre segments. A legend indicates that solid yellow lines represent Fibre, red bars represent Connectors, and dashed blue lines represent the Optical path. The diagram is labeled G.9940(23). + +**Figure I.1 – Optical path loss for a G.fin network with a single power splitter** + +The different attenuation coefficients for single mode fibre are: + +- 0.35 dB/km (maximum at 1 550 nm) and 0.4 dB/km (maximum at 1 625 nm) of fibre type G.652.B as described in [ITU-T G.652]. +- 0.4 dB/km (1 310 to 1 625 nm) and 0.3 dB/km (maximum at 1 530-1 565 nm) of fibre type G.652.D as described in [ITU-T G.652]. +- 0.4 dB/km (1 310 to 1 625 nm) and 0.3 dB/km (max at 1 530-1 565 nm) of fibre type G.657 (may be used for indoor cabling and/or drop section) as described in [ITU-T G.657]. + +Connector loss depends on the number of connectors. Insertion loss for each single fibre connector is a maximum of 0.5 dB as described in [ITU-T G.671]. + +Insertion loss of a power splitter depends on the splitting ratio (see [IEC 61753-031-2]). This may be the main contributor to the OPL. + +The practical usage of the IFDN splitting ratio is environment dependent. The following table shows the insertion loss (including connection loss between the splitter and fibre) of splitters for different splitting ratios. + +**Table I.1 – Insertion loss of splitters with a different splitting ratio** + +| Port configuration | | 1×2 | 1×4 | 1×8 | 1×16 | 1×32 | 1×64 | +|---------------------------|---------|---------------|-----|------|------|------|------| +| Operating wavelength (nm) | | 1 260 ~ 1 650 | | | | | | +| Insertion loss (dB) | Typical | 3.5 | 6.8 | 10.2 | 13.1 | 16.2 | 20.2 | +| | Maximum | 4.0 | 7.4 | 10.5 | 13.5 | 16.9 | 21.0 | +| Channel uniformity (dB) | | 0.5 | 0.7 | 1.0 | 1.4 | 1.8 | 2.0 | + +## I.2 Splitting architecture + +For different environments, the requirements of the IFDN splitting ratio may be different. According to the analysis of the different use cases covered by G.fin, an IFDN splitting ratio of 1:8 is enough for most cases in a home networking environment, whilst the optical link budget Ra can support up to 1:16. This clause analyses optical path loss for different splitting architectures. + +- a) 1-tier symmetric splitting for an IFDN splitting ratio of 1:16 + +![Diagram of 1-tier symmetric splitting with 1:16. An MFU (green rectangle) is connected via a connector (red vertical bar) to a 1:4 splitter (blue triangle). The 1:4 splitter has four output ports. The top and bottom ports are connected to SFU units (green rectangles) via connectors. The two middle ports are connected to vertical ellipsis dots, indicating further splitting to reach a total of 16 outputs. The diagram is labeled G.9940(23).](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Diagram of 1-tier symmetric splitting with 1:16. An MFU (green rectangle) is connected via a connector (red vertical bar) to a 1:4 splitter (blue triangle). The 1:4 splitter has four output ports. The top and bottom ports are connected to SFU units (green rectangles) via connectors. The two middle ports are connected to vertical ellipsis dots, indicating further splitting to reach a total of 16 outputs. The diagram is labeled G.9940(23). + +**Figure I.2 – 1-tier symmetric splitting with 1:16** + +For this architecture, 1 km transmission distance and two connectors are considered. Therefore, the maximum optical path loss is 14.9 dB. + +$$OPL_{max} = 0.4 \text{ dB} + 13.5 \text{ dB} + 0.5 \text{ dB} * 2$$ + +- b) 2-tier symmetric splitting for an IFDN splitting ratio of 1:16 + +For multi-tier symmetric splitting, $Loss_{PSmax}$ is the sum of the maximum insertion losses of the cascaded splitters for their given splitting ratios according to Table I.1. + +![Diagram showing two 2-tier symmetric splitting architectures. (a) 2-tier splitting with cascaded 1:4 splitter: An MFU is connected via a connector to a 1:4 splitter. Each of the four output ports of this first splitter is connected to another 1:4 splitter. Each of these four second splitters has four output ports, each connected to an SFU via a connector, for a total of 16 SFUs. (b) 2-tier splitting with cascaded 1:2 and 1:8 splitter: An MFU is connected via a connector to a 1:2 splitter. Each of the two output ports of this first splitter is connected to a 1:8 splitter. Each of these two second splitters has eight output ports, each connected to an SFU via a connector, for a total of 16 SFUs. Both diagrams include a legend for 'Connector' (red vertical bar) and are labeled G.9940(23).](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +Diagram showing two 2-tier symmetric splitting architectures. (a) 2-tier splitting with cascaded 1:4 splitter: An MFU is connected via a connector to a 1:4 splitter. Each of the four output ports of this first splitter is connected to another 1:4 splitter. Each of these four second splitters has four output ports, each connected to an SFU via a connector, for a total of 16 SFUs. (b) 2-tier splitting with cascaded 1:2 and 1:8 splitter: An MFU is connected via a connector to a 1:2 splitter. Each of the two output ports of this first splitter is connected to a 1:8 splitter. Each of these two second splitters has eight output ports, each connected to an SFU via a connector, for a total of 16 SFUs. Both diagrams include a legend for 'Connector' (red vertical bar) and are labeled G.9940(23). + +**Figure I.3 – 2-tier symmetric splitting architecture** + +For architecture a) of 2-tier splitting, 1 km transmission distance and two connectors are considered. Then, the maximum optical path loss is 16.2 dB. + +$$OPL_{max} = 0.4 \text{ dB} + 7.4 \text{ dB} + 7.4 \text{ dB} + 0.5 \text{ dB} * 2$$ + +For architecture b) of 2-tier splitting, 1 km transmission distance and two connectors are considered. Then, the maximum optical path loss is 15.9 dB. + +$$OPL_{max} = 0.4 \text{ dB} + 4 \text{ dB} + 10.5 \text{ dB} + 0.5 \text{ dB} * 2$$ + +c) 2-tier asymmetric splitting for an IFDN splitting ratio of 1:9 + +![Diagram of a 2-tier asymmetric splitting architecture for a 1:9 IFDN splitting ratio. An MFU (Medium Frequency Unit) is connected via a connector to a 1:5 splitter. The 1:5 splitter has five output ports: the top port is labeled 60% and leads to a second 1:5 splitter; the second, third, and fourth ports are each labeled 10% and lead to an SFU (Small Frequency Unit); the bottom port is labeled 10% and leads to another SFU. The second 1:5 splitter has five output ports: the top port is labeled 60% and leads to an SFU; the second, third, and fourth ports are each labeled 10% and lead to an SFU; the bottom port is labeled 10% and leads to an SFU. A legend indicates that a red vertical bar represents a 'Connector'. The diagram is labeled G.9940(23).](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +Diagram of a 2-tier asymmetric splitting architecture for a 1:9 IFDN splitting ratio. An MFU (Medium Frequency Unit) is connected via a connector to a 1:5 splitter. The 1:5 splitter has five output ports: the top port is labeled 60% and leads to a second 1:5 splitter; the second, third, and fourth ports are each labeled 10% and lead to an SFU (Small Frequency Unit); the bottom port is labeled 10% and leads to another SFU. The second 1:5 splitter has five output ports: the top port is labeled 60% and leads to an SFU; the second, third, and fourth ports are each labeled 10% and lead to an SFU; the bottom port is labeled 10% and leads to an SFU. A legend indicates that a red vertical bar represents a 'Connector'. The diagram is labeled G.9940(23). + +**Figure I.4 – 2 tier asymmetric splitting architecture for 1:9** + +For an architecture of 2 tier asymmetric splitting for 1:9, 1 km transmission distance and two connectors are considered. Then, the maximum optical path loss is 16 dB. + +$$OPL_{max} = 0.4 \text{ dB} + 3.2 \text{ dB} + 11.4 \text{ dB} + 0.5 \text{ dB} * 2$$ + +NOTE – The loss of 3.2 dB and 11.4 dB corresponds to 60% and 10% of the incoming optical signal for the respective ports of the splitter. + +d) Direct connection + +For the case where only one SFU is connected to the MFU in a home environment. The maximum optical path loss is 1.4 dB. The minimum link loss could be as low as 0 dB in an ideal case. + +$$OPL_{max} = 0.4 \text{ dB} + 0.5 \text{ dB} * 2$$ + +![Diagram of a direct connection case. An MFU (Medium Frequency Unit) is connected via a connector to an SFU (Small Frequency Unit). A legend indicates that a red vertical bar represents a 'Connector'. The diagram is labeled G.9940(23).](803776dff64331076ffc951fc95358ee_img.jpg) + +Diagram of a direct connection case. An MFU (Medium Frequency Unit) is connected via a connector to an SFU (Small Frequency Unit). A legend indicates that a red vertical bar represents a 'Connector'. The diagram is labeled G.9940(23). + +**Figure I.5 – Direct connection case** + +## I.3 Optical link budget consideration + +From the analysis of optical path loss with different splitting architecture, 16.5 dB is enough for an IFDN splitting ratio of 1:16 with a symmetric splitting architecture, and 1:9 with a 2-tier asymmetric splitting architecture. If a little extra margin for engineering is considered, 17 dB to 18 dB is sufficient for the home environment. + +The analysis for the small and medium enterprise environment is left for further study. + +# Bibliography + +- [b-ITU-T G.988] Recommendation ITU-T G.988 (2022), *ONU management and control interface (OMCI) specification*. +- [b-ITU-T G Suppl. 78] Supplement ITU-T G Suppl. 78 (2022), *Use case and requirements of fibre-to-the-room for small business applications*. +- [b-ITU-T GSTP-FTTR] Technical paper ITU-T GSTP-FTTR (2021), *Use cases and requirements of fibre-to-the-room (FTTR)*. +- [b-BBF TR-069] BBF TR-069 (2020), *CPE WAN Management Protocol*. +<> +- [b-BBF TR-369] BBF TR-369a3c1 (2023), *The User Services Platform (USP)*. +<> +- [b-ETSI GR F5G 008] ETSI GR F5G 008 V1.1.1 (2022), *Fifth Generation Fixed Network (F5G); F5G Use Cases Release #2*. +<> +- [b-IEEE 1588] IEEE 1588-2019, *IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control 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.9960-202306-I_PDF-E/000c903c2d17433f5ef183ff4edc62fd_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/000c903c2d17433f5ef183ff4edc62fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3cdae2fff3ebef44d959c3f443223b202f914e3 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/000c903c2d17433f5ef183ff4edc62fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:253bfa64413784a488db3cdd72e682d0ff4082419ba17e704a7353a7abe5440d +size 12694 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe5ebc301d81eb7434a6a735c4e288e310dec765 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ed0f935333aedb4bf63c121f0ea68d05dec7950d996b1e506b38152048027ef +size 42275 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/0348dd87efbccba766e98138b073b499_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/0348dd87efbccba766e98138b073b499_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0db98785b87bc9d6b4fc1c0e6364acb7d7c11be9 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/0348dd87efbccba766e98138b073b499_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52dbc2c20537d267a6309ea6fce3500c6b36565f9e77b0f8e9cdad4663c54348 +size 59939 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/04f7b8f64493f6d83188232f10f86fe2_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/04f7b8f64493f6d83188232f10f86fe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29e32b444cce96ce5de9e1d22d6e2518eef90fc1 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/04f7b8f64493f6d83188232f10f86fe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:410b1a5ccd9cd487644467572ab79e31832627585f9d7eedeabaecf8ca5bed91 +size 33443 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-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.9960-202306-I_PDF-E/0d8f6da9077a85e09077cdfbecae1838_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/0d8f6da9077a85e09077cdfbecae1838_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8385dd5ebd5f92b0c2153e36cbe7b3af552931e1 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/0d8f6da9077a85e09077cdfbecae1838_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bb0494cacac9eaf25179d338ec35975b1c53e7032057592af1799f955959fe7 +size 13286 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/0fec4b5689fcc9aa96a87f0c1bdaf200_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/0fec4b5689fcc9aa96a87f0c1bdaf200_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a82d734ce5d58d687ef57390a6873248a4cb5f87 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/0fec4b5689fcc9aa96a87f0c1bdaf200_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:956e6efac84711c24abaeaeb540cb2c69e14b7749b16f537b4b6fa6a7fb36428 +size 47906 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ee96f2dd831f7add96c7111788c80353930774 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a106e0f57a175371ec6f752ba093aa2924fad2c5f4a5a74e185e00f6752fbc0 +size 30103 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96d4af7c077720fcec50995642be8ec168963ab --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9efb4481af5a31c7dc86d2a04eec8820af6a8dfd4035ad11f9413c631bfbcf7 +size 39480 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/215e8d5e5ba38df215b55049d255b2ed_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/215e8d5e5ba38df215b55049d255b2ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81dcd1621676be10198244e10ad14be40290a089 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/215e8d5e5ba38df215b55049d255b2ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87dfe8907164c72c412d2e0742748a8375d530ef0b67f76bf879132fc2b14c2a +size 70622 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/23f62df20874b7423cbf7f29fcecf9ed_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/23f62df20874b7423cbf7f29fcecf9ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd8e802db02502923652082d7f536a4cd603d38b --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/23f62df20874b7423cbf7f29fcecf9ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84895310c7a764cb9bce063d84b6201ea8b291a7eedf16901fdca7ed372a1197 +size 6522 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d05fb0471758acd83e9996da6477cf6b76e34e --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce57566438610b2b83c6ab6335612571f0fc0734b0b81f0f96a1ca46368976a2 +size 23592 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e35ac040b76a2fd716d39bad7dc9d399662029d8 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ed99f935267af3de399345dfc65fccb249ae4f3588821685b507cd34e2ee4f9 +size 19484 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2a52834ffb60a618738d21bcc3ace1e3_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2a52834ffb60a618738d21bcc3ace1e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04c5db549cbfb655bf89b59564f173510b8a7e75 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2a52834ffb60a618738d21bcc3ace1e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1802abaa55dd0239a9d7605a9f9f4e48940f02b869ae9d7149894b51a16d8404 +size 24844 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..297c24859065d40e4b1be49d3d137e475126d896 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fed4c7b7b0f57343f4c015e33f5d9b758e5736e40c8b574fa6ec5e12acd2ee7 +size 50858 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2b767b048e388ae309771bc57d56e136_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2b767b048e388ae309771bc57d56e136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..361ee926497be24c5f8fb9a703933c60f868668b --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2b767b048e388ae309771bc57d56e136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7176261e43cf3fdccf1e671d57e309eb9d4f656a7ce33a994d5d722496fdb2a +size 67852 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e151fbb18b27cde889d21ce10e4a31376e1794e --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cdafee9b13f179051c9397c04d12dccfe60dd4a766e54a12a919a7445d7449b +size 23941 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef9e3d45b8e312479d24d8017b394fd4aa9124eb --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9de9c7009395d6ee3e59c35fef6909acd82b2bdd8921c8762b6a4b5b9a0bec29 +size 8017 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/409e3ccf9694772191dc84c49f3f7afb_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/409e3ccf9694772191dc84c49f3f7afb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e050023afdda199d38a49286faaa2576b6f88f62 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/409e3ccf9694772191dc84c49f3f7afb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d79dd884e7e5b73eeaa5478f62da3c960f77eed0ca91c440f48fb46e8758eaec +size 48784 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e4a5ef8dbf820a37b79d68851ca9f1b9cf3f434 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/4750bc46c043ee2e9d4524c36d9a54a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78402df8073e7ea655eb1a5c33ae1ef0888039d806b99a472e20f43bd91d7016 +size 14907 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19e6ddf558e7f508440d04572214baed70b925ad --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/4b48a3fdfe130217b1ff29b9b0592a45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbe53ad535b820f7d621b744c3214e3e2dcfb4c84d6edd7b09c848d43f23ed2d +size 7649 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/4faf621bddd7d6e9f24a27325de96015_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/4faf621bddd7d6e9f24a27325de96015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aafb607c880f8d67505884c5d77c022a09f0850a --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/4faf621bddd7d6e9f24a27325de96015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:240522f6dbe2b690b479ed19ee3c26e2b7a697d7a5950852111cc69ddb4e8f60 +size 9327 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..325fcf7bebe1573e7d2b33a2c3d16cb6e59d13aa --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/54a1e5d91d7f442361767b1f8c81c777_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cb7adc1e4c91377111bf30983b185ce9888916e80ae07cf8d46e0424763ef97 +size 45816 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8f63f249f092715626f2c17e5cd3f375b17d348 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/5525e7460947727851585808324e1f98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e331376eaa147f695d0ad3ba744ba3352585e94ee5cf2810a53cee10e803fd6 +size 56751 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/56887eb4a851f556d1b263bf90755686_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/56887eb4a851f556d1b263bf90755686_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..903925037f9387713764ac134ffa50a5692814dd --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/56887eb4a851f556d1b263bf90755686_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:576a99f06a378d5d01f2b1604229d0651588c011e4b415f7beba27f73951fc5d +size 16633 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0457171ba035ee2cefeb733be7041d9e09524417 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f415298a39a96eab90341baf7059ea1edf30173287565d9b7bec52597388b26a +size 28802 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/5ea288cb741dddda2a54203184649b5a_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/5ea288cb741dddda2a54203184649b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..150b9a280e3647a172f6f7270dc0b2f93fc9e8b3 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/5ea288cb741dddda2a54203184649b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fe2122d4fcbaca9b26e17e42bb10708d664efd9001e3c2be2cbe691ea1f5fc2 +size 25655 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/61887c08b198861558621bc776880d6d_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/61887c08b198861558621bc776880d6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdde46f3dd9fc074d920e217a9673f111080d336 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/61887c08b198861558621bc776880d6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dd5c0491b73bc9d5940d90e0fbae9a71d33ae0acef33f95a10975c350c236cd +size 53646 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/643e8a3c198571617894ece3f1c2e72d_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/643e8a3c198571617894ece3f1c2e72d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8fdaf0f560cd1667478abf4f40c65354328473d --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/643e8a3c198571617894ece3f1c2e72d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9d47c435445c7043eb9b9c7e375844c6036e21d972fba4d9d32973858f6ab62 +size 42123 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c9fe08db9b2f66776a0a9cfa40f209a0d977fd0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07c147aa1bd2404305fdb5084fb4b6c5710e1ccb8e70d60da547b19a2e058c30 +size 9306 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d5f7f3bb84387804bcf3babb6d449b1dba43e5a --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/6726e50ea08adfda77603ec4afa549e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:298ddba536ff4d845243a0641443b9eb2f1d3ab009eacb229f5f4c7e6b9c2b62 +size 40400 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5605e29630c9b6f55062f2dcf9c4e64be32670c1 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/692541e65db4dc852988ce77ebb60ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc5f3e44349c2554000210e3fe0f499f671af880607d398b06d67938546981be +size 46846 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/701f4311e49f346390759520fcd19af4_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/701f4311e49f346390759520fcd19af4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d53a3896b30e8ef6b865ba7d203b2556b596d483 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/701f4311e49f346390759520fcd19af4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84f3377f2012598357b9cd0218ced7211a0ae0344ed351baaa0b31c3c54a0eab +size 31429 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/709d81964e33e85c1e1f9edb30d395fd_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/709d81964e33e85c1e1f9edb30d395fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c73d64f723997d5c5a5fbb4c60a5bb4c25c499aa --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/709d81964e33e85c1e1f9edb30d395fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa904aa2ede47001b42f041927a286c6aee6838a11e0c5066e7f2b2190538b8a +size 29454 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..341a83290d2725705681689ca1ab87aa9f52a58d --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/72d375793611d82866edc20cb031d867_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a9a21666ddc705116ed0dd791010fadf65d60acc1a8d7079be1338b121f4c79 +size 43986 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d085643328023d97b84e8c75e3a4d56a17d7b42 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/7f5df81190b8dc50dad2604562ae0715_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12d14329ca8ee4a8b49b2c43ad7806023029b2f5becbfdb7f13166967db996a9 +size 5628 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13180ba2a8a8fe333345165852423ad74d160530 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/886963464425186f4a465fa8155d2a3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3fbf2c449fc4a87cae07a26ded7e3f623e18e17665c74210bca47f134d18d6c +size 26809 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6f42047befa2a5c22a34f212693a2c46aa176ca --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/88c92858439684b2103e88cb143fb98e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7b01997d94eed50bf0828dcccb26cf95c3264c4d6deeae5a01de8f8cc659b2 +size 39736 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a46641282003ea6d1875cef2071996b32fd925b4 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e54442fa82b857c5b5d9b40c99a00e34f76dacf948fd4525324dcb8c4f9d109 +size 15393 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba79dbd7720f83a01edbb041df6ec52c11a152ef --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/8c348bf9c2c81b018017ae1d19506a9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1205cd58813c97592f17e2c408764e90a1da92915db3884c5a4ec820ba7076da +size 69177 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/901755bf86813427f3a32efa0363a27c_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/901755bf86813427f3a32efa0363a27c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c06006fa333623473c9d9772981cca8269d0f5 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/901755bf86813427f3a32efa0363a27c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68839dd81b3f3222922bd0baa0f0fe357faa140c457b5027086aa1bd92b02dd8 +size 26651 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/978794771205b002dd72295a59de7919_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/978794771205b002dd72295a59de7919_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b29d0c54124deaba5a73023cda1cfcf9325154b7 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/978794771205b002dd72295a59de7919_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16041e55ec8708f4e8323be66e77bd2532ec141e9c7d8077b2c52defeb645162 +size 119201 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a5f4eae884cbe5d6a985476d2bda83ff87464ac --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:269148d36af5f18f97a6c7d42c52c27f35c91ca68b7c911cdb5487e57c8dd7c6 +size 69857 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6d956155720190ce92f4d6feb620c34b622ef7a --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912e9c613b271f090573ce9c829e986f46066107690705bdfa2f40aeb44f87d2 +size 19483 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..815eae72d805907af17fd818bdca89f93bdc47ef --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad98fc6b82193098359d456313b8d2eaa7f9b7384bdfcc2549d019875e6e9bd +size 22687 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/9f5f9afcedaa0d9b7991976f5000865c_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/9f5f9afcedaa0d9b7991976f5000865c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2746a412e9ad5335a4633055526811fba2058659 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/9f5f9afcedaa0d9b7991976f5000865c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea27c8e608d456081d2e3816d8f261a3f633078e5bf87c2ae41714d39235d215 +size 72261 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df6c6e9f43830ee44a1ee18a2b28a18b4b4f6212 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74962aebb7e7f9c6620bbaa28aa51ee9373e2feabe4049f8348941d231dd1a43 +size 15629 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61c865c025f34e1e17b572b8f671ecf6ac0d0d82 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3adceaca8f02f6dbb43880941781825a940ffd084e039ef3cb8df8650f87ada3 +size 25768 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bfab0b67be4095afee67383bac0ca99e00a4eae --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:254645644a400f97a582119bf30482dd5dd44433b841ba2e15b07f493099a3e7 +size 83310 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90cd1c07c7fdb71b0b4d5d04e23109f53b70d482 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:150e3d1c13805d0189369d56a38bd1c4ed965c3a96502cc0b7c4039b0f498768 +size 66434 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/b71ad9fc874230de9ba4480e12a216f7_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/b71ad9fc874230de9ba4480e12a216f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16777582f11c5b1d389742fa4b319fabae1d40ae --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/b71ad9fc874230de9ba4480e12a216f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65b58785074f95319f00d15cbd72e31ff989973e7ca363bf6e7d9e1844524d11 +size 19152 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fa78db08cf4f504abe5a3d4e13032d45dd91bfb --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/b8d855a06aad434aeafa2739bf62e7de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b072dbc08fdad87bdeef9e1e9f931153783f0e20df0878f62ca0af62d75836a +size 51297 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/bae1bd2b5dec0c7f0717e710ad5a3412_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/bae1bd2b5dec0c7f0717e710ad5a3412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..441480bfc111b24c2cda36a96ce471ff85df957c --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/bae1bd2b5dec0c7f0717e710ad5a3412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4101491e8eeeca7499019caaf649f9d446401ca1e9b445ded71e4919a70f956 +size 108027 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/c13dfef1bb16b40f3ee1955ea9a7bdbc_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/c13dfef1bb16b40f3ee1955ea9a7bdbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da633948e8cbfad6ee96e41bf35d9dd7b9d10db4 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/c13dfef1bb16b40f3ee1955ea9a7bdbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c883913492eedfb41f5c4e7ac353e3951480eca475a759936a14ddbb5b04f7a8 +size 26922 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/c2c45d2f2b1eecc0149f1b5b0ae82994_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/c2c45d2f2b1eecc0149f1b5b0ae82994_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6018119c0d3d5eabc54e082c9d2eb43db1afce2 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/c2c45d2f2b1eecc0149f1b5b0ae82994_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ebf2acff0d45e21fcc8c7066af7b6969fd642ba4a3a46a2f085fe12f3dd039b +size 35949 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68fd703ad04ac8ea855c84d677353e79956644dd --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:800fba9d323b55f44410b0783850f9402ab55683e20a7475bfcfc1316038a0fa +size 72061 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05ea340ab3714e1971aff97f8200c52076d864c0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/cbdfdade780e677eb1c1aef3081ce9ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:117ae81437893cd067074db10f911a298417474d48e6db3ecde656213da2cc1e +size 34466 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ae66cea715f9ed6fa67ff4b34598ec17a6b084 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e9cd5bba2ecc388240751f21b348eb2817cf947f6653152c5d9049160636b3d +size 28741 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/cf9b9abea4fbaa200888c82c924b769d_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/cf9b9abea4fbaa200888c82c924b769d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab59e2a073d3b2d9fc03fa94606a9c772288b8f0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/cf9b9abea4fbaa200888c82c924b769d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f7152511e075956966b715a6d596ed300240b629c07c3087c1ef369350e7ee3 +size 16660 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bed51a7e0ec7257f82d3350f2f190cd4b0acb43d --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0ff48be8154d36409707976980b9c9017f4f0da914a768f9829958a239d538 +size 18470 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bc91aa853c36dda73ef121b50e8e6444a1a8cf9 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/d1ad05f1189b0d80188fee24ae33c112_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d2604036421b7d0a6e29d13170df4f874a7c145713d99ace0b9c09d42ac45f9 +size 76581 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/d5439b040187c5a1e89ad438ef535141_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/d5439b040187c5a1e89ad438ef535141_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7593c52c5df25d3ef1fd72bce5402973c0f2537 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/d5439b040187c5a1e89ad438ef535141_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0571a279c44766e104a4c4d51912274c1e33c38754ef829b572a59284633835f +size 68511 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1acc687dbc72f39f8319f400b0f760fda2c678d1 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/dae88eec6d1005984029b794ff8b7a9e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:126820e5e4875f9c64a900c68333a5d0c898d66ac552bc6629ce18e1a545bff2 +size 77090 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/dafe1e070adde01b4d127609636af4e9_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/dafe1e070adde01b4d127609636af4e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ef521202b985ed7de4febd4772712e58dbe89db --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/dafe1e070adde01b4d127609636af4e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96d6ca705521870867aea7291b324a477cf4fc0eaee0fa93705cac5f2b223e62 +size 13483 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/df942da5e715e03b194b733d9f5998ad_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/df942da5e715e03b194b733d9f5998ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20fd81423ecdeb7bc2c69cb3e916b82fdd28e509 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/df942da5e715e03b194b733d9f5998ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89662a1c4aea49d98a9fe2c0ad12bd9c07e34b776de376a4ad8d592da28ea568 +size 33414 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d15cf9c2e51d76a1f8c2e7fe18c9374bc5cf910d --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/e3026761f1da20ee91832039701984dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bf63dc5d09b23feca24cc69f12e7ab6ebcca9474a964d847e026eec281e6121 +size 27448 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/e845d172f83764c1db7998397af2b9d5_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/e845d172f83764c1db7998397af2b9d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a5677f9c603a1cd25246275fd99e385758931c0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/e845d172f83764c1db7998397af2b9d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a0cb3aa8ad6e96c73fa9e2ddc7b1eb05d968b647f83281ccbb7e0976384f7e +size 17239 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0014c8151ad353efbc109f7b3a99c4128ce72f6 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:608ead09e0503679f4947a81ea903c3a421186f0c03d11a34de1e0c5ccfd0f4f +size 32292 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a44c2708801331d5475133033def317c25545b4 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:035dc42bfa0ad710ee11829de92d00c9229a74ae9db43f8ca4afd3f0229fab29 +size 41384 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbcab6816b0b73e93b9735629e598ba28b589b25 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/eda1a0f033926f48febc095bce470c58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7c72b971c32fcb35978b2af451756df54daa0e4041f684d66c03aaec6fb13ab +size 73098 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/ee6ac2449928fabca567921acb078fc0_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/ee6ac2449928fabca567921acb078fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63ce4e578f35e10ca623d18b2f574e60e3c71a33 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/ee6ac2449928fabca567921acb078fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebff1c5f18a3641a376a6036778b653c3554117033dcdb20400eaca0211cf367 +size 11730 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93d52bf6b4c53b979e2bb71f42b64a10603d38df --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcf8cc39fec156615a5d8f3976ac67adf372cf6ee35858376248fe7dad1a5f45 +size 18937 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47d49928867e52c36294dbd1bfa0aa63ead6a91d --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/efedc464aaba06e85f269d26c98fee90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1572f327020ad987546349e97cf670b4fb38a0cb2ccee8385ffbff299a6119de +size 8933 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aa9cdde1224cd00bdc4593068e6294_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aa9cdde1224cd00bdc4593068e6294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cc93019f95c8864cc38ab0a61ce016a395c513a --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aa9cdde1224cd00bdc4593068e6294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d0ccdae5c6a9b89a0708dbf7cd2472ab73345a92a19cf99cc7301a0bef4f3d2 +size 18374 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d050bc918dc53d77d8045796c68246c8f03d2a0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/f4aaee6522d9ab40472939a4a178e5a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fb3910dd8c0d045bd8059a421a04c2df51b076e938b51875b7e1c207ee6e00a +size 19387 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35f7b409183122278bbec3cc6bb0e77a6703efa0 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/f54b2e4444e410765295be668123f27a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f788de62bc096e3e1eda228421567faa3775d6947f33803bfa46bd06a08a110 +size 46030 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/f79cb254efa2e37d7facb055cf90086e_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/f79cb254efa2e37d7facb055cf90086e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d33b3eb586711a006938515104a5d0b85bc76195 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/f79cb254efa2e37d7facb055cf90086e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d20bd5db464502703fde070039fa9f8773e91afa255fe7d26ad5880f49a90ff +size 31004 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e87dfb7c0d3a66ae2a3e8774f007b74c3a5b8731 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/f9c64800d9bace9b4315646d1057be3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:070d10976dbecf86c1e12542597f925cd6fa678f0060d670377bcaafe27d9e36 +size 41898 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f194b7ac2bcccd97c4fd4279a9bdf66989a39392 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5a16d4692238ca5d190d8f67252cf17e8323d7f774b3db703a75193db790656 +size 84603 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/fc70bf3c1fbbe560de4704cb2b4182b1_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/fc70bf3c1fbbe560de4704cb2b4182b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d620c7bd9609c9362aac3d330cedc9bf697e74ad --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/fc70bf3c1fbbe560de4704cb2b4182b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:059af0c3493302103b517622162cdab143bc2259830768864f03510566e54c26 +size 31319 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/G/T-REC-G.9960-202306-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdec79db2625936093baf14acfdc03ffb937cef6 --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:890032df143e3b6b193d6e2814b19bdbad88f1a9dfbaac31981d7ac65bacc718 +size 16465 diff --git a/marked/G/T-REC-G.9960-202306-I_PDF-E/raw.md b/marked/G/T-REC-G.9960-202306-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7729972f0b116583b296ac061cbd29ff95b4afde --- /dev/null +++ b/marked/G/T-REC-G.9960-202306-I_PDF-E/raw.md @@ -0,0 +1,8087 @@ + + +# Recommendation **ITU-T G.9960 (06/2023)** + +SERIES G: Transmission systems and media, digital systems and networks + +Access networks – In premises networks + +--- + +## **Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification** + +![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 overlaid on the globe. + +ITU logo + +## ITU-T G-SERIES RECOMMENDATIONS **Transmission systems and media, digital systems and networks** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS | G.100-G.199 | +| GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS | G.200-G.299 | +| INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES | G.300-G.399 | +| GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES | G.400-G.449 | +| COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY | G.450-G.499 | +| TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS | G.600-G.699 | +| DIGITAL TERMINAL EQUIPMENTS | G.700-G.799 | +| DIGITAL NETWORKS | G.800-G.899 | +| DIGITAL SECTIONS AND DIGITAL LINE SYSTEM | G.900-G.999 | +| MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER-RELATED ASPECTS | G.1000-G.1999 | +| TRANSMISSION MEDIA CHARACTERISTICS | G.6000-G.6999 | +| DATA OVER TRANSPORT – GENERIC ASPECTS | G.7000-G.7999 | +| PACKET OVER TRANSPORT ASPECTS | G.8000-G.8999 | +| ACCESS NETWORKS | G.9000-G.9999 | +| Metallic access networks | G.9700-G.9799 | +| Optical line systems for local and access networks | G.9800-G.9899 | +| In premises networks | G.9900-G.9999 | + +*For further details, please refer to the list of ITU-T Recommendations.* + +# Recommendation ITU-T G.9960 + +## Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification + +## Summary + +Recommendation ITU-T G.9960 belongs to the family of ITU-T G.996x Recommendations. Recommendation ITU-T G.9960 specifies the system architecture and physical (PHY) layer for wireline-based home networking transceivers which are capable of operating over premises' wiring, including inside telephone wiring, coaxial cable, and power-line wiring. It complements the data link layer (DLL) specification in Recommendation ITU-T G.9961, and the power spectral density (PSD) specification in Recommendation ITU-T G.9964. + +This revision comprises ITU-T G.9960 (2018) plus its Corrigendum 1, Amendment 1, Amendment 2, Corrigendum 2 and Amendment 3, along with the specification of a new PHY frame type for use by ITU-T G.9991. + +## History \* + +| Edition | Recommendation | Approval | Study Group | Unique ID | +|---------|----------------------------|------------|-------------|--------------------| +| 1.0 | ITU-T G.9960 | 2009-10-09 | 15 | 11.1002/1000/9679 | +| 2.0 | ITU-T G.9960 | 2010-06-11 | 15 | 11.1002/1000/10704 | +| 3.0 | ITU-T G.9960 | 2011-12-16 | 15 | 11.1002/1000/11403 | +| 3.1 | ITU-T G.9960 (2011) Amd. 1 | 2014-01-13 | 15 | 11.1002/1000/12087 | +| 4.0 | ITU-T G.9960 | 2015-07-03 | 15 | 11.1002/1000/12400 | +| 4.1 | ITU-T G.9960 (2015) Cor. 1 | 2015-11-22 | 15 | 11.1002/1000/12538 | +| 4.2 | ITU-T G.9960 (2015) Amd. 1 | 2015-11-22 | 15 | 11.1002/1000/12537 | +| 4.3 | ITU-T G.9960 (2015) Cor. 2 | 2016-04-13 | 15 | 11.1002/1000/12824 | +| 4.4 | ITU-T G.9960 (2015) Amd. 2 | 2016-04-13 | 15 | 11.1002/1000/12818 | +| 4.5 | ITU-T G.9960 (2015) Cor. 3 | 2016-11-13 | 15 | 11.1002/1000/13111 | +| 4.6 | ITU-T G.9960 (2015) Cor. 4 | 2018-03-16 | 15 | 11.1002/1000/13558 | +| 5.0 | ITU-T G.9960 | 2018-11-29 | 15 | 11.1002/1000/13775 | +| 5.1 | ITU-T G.9960 (2018) Cor. 1 | 2019-09-29 | 15 | 11.1002/1000/14026 | +| 5.2 | ITU-T G.9960 (2018) Amd. 1 | 2020-02-07 | 15 | 11.1002/1000/14025 | +| 5.3 | ITU-T G.9960 (2018) Amd. 2 | 2020-07-22 | 15 | 11.1002/1000/14221 | +| 5.4 | ITU-T G.9960 (2018) Cor. 2 | 2020-10-29 | 15 | 11.1002/1000/14531 | +| 5.5 | ITU-T G.9960 (2018) Amd. 3 | 2022-02-13 | 15 | 11.1002/1000/14909 | +| 6.0 | ITU-T G.9960 | 2023-06-13 | 15 | 11.1002/1000/15555 | + +## Keywords + +Coaxial, home networking, in-premises networking, phoneline, physical layer, powerline, system 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 2023 + +All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. + +## Table of Contents + +###### Page + +| | | | +|------|-------------------------------------------------------------------|-----| +| 1 | Scope..... | 1 | +| 2 | References..... | 1 | +| 3 | Definitions ..... | 2 | +| 4 | Abbreviations and acronyms ..... | 6 | +| 5 | Home network architecture and reference models ..... | 9 | +| 5.1 | Home network architecture and topology ..... | 9 | +| 5.2 | Reference models ..... | 21 | +| 5.3 | Management-plane reference model ..... | 25 | +| 6 | Profiles..... | 26 | +| 6.1 | Low-complexity profile (LCP)..... | 27 | +| 6.2 | Standard profile ..... | 27 | +| 6.3 | Operational frequency band (OFB) ..... | 27 | +| 7 | Physical layer specification (PHY layer)..... | 28 | +| 7.1 | Medium independent specification..... | 28 | +| 7.2 | Medium dependent specification..... | 108 | +| 8 | Data link layer specification ..... | 115 | +| 9 | Security ..... | 115 | +| 10 | High capacity header physical layer specification (HCH-PHY) ..... | 116 | +| 10.1 | Medium independent specification..... | 116 | +| 10.2 | Medium dependent specification..... | 172 | +| | Annex A – Regional requirements for North America ..... | 177 | +| | Annex B ..... | 178 | +| | Annex C – Regional requirements for Japan ..... | 179 | +| C.1 | Scope ..... | 179 | +| C.2 | Medium dependent specification..... | 179 | +| | Annex D ..... | 183 | +| | Annex E ..... | 184 | +| | Annex F – Usage of ITU-T G.9960 for optical transmission ..... | 185 | +| F.1 | Scope ..... | 185 | +| F.2 | Media dependent specification ..... | 185 | +| | Annex G – Test vectors (PHY layer)..... | 187 | +| G.1 | PFH test vectors..... | 187 | +| G.2 | Scrambler test vectors..... | 187 | +| G.3 | FEC encoder test vectors ..... | 188 | +| G.4 | Constellation encoder test vectors ..... | 188 | +| G.5 | Constellation scrambler test vectors ..... | 189 | +| G.6 | Preamble generation test vectors ..... | 190 | + +| | Page | +|-------------------------------------------------------------------------------------|-------------| +| Annex H – Test vectors (HCH-PHY layer) ..... | 192 | +| Annex I ..... | 193 | +| Annex J – Interoperability between Profile 1 and Profile 2 OFB transmissions ..... | 194 | +| J.1 Rules for selection of transmission mode ..... | 194 | +| J.2 Rules for scheduling generation..... | 194 | +| Annex K to Annex Q ..... | 195 | +| Annex R – Use of reverse power feeding techniques for G.hn over coaxial media ..... | 196 | +| R.1 Scope ..... | 196 | +| R.2 References ..... | 196 | +| R.3 Definitions ..... | 196 | +| R.4 Abbreviations and acronyms ..... | 197 | +| R.5 Reference architecture ..... | 197 | +| R.6 Implementation of RPF ..... | 199 | +| Appendix I – Examples of home network topologies ..... | 205 | +| Appendix II – Spectral usage ..... | 209 | +| II.1 Scope ..... | 209 | +| II.2 Spectral usage in Japan..... | 209 | +| Appendix III – Priority mapping..... | 212 | +| Appendix IV ..... | 213 | +| Appendix V – Electric vehicle applications based on ITU-T G.9960 ..... | 214 | +| V.1 Introduction ..... | 214 | +| V.2 EVSE and EV devices ..... | 214 | +| V.3 Overall network architecture ..... | 217 | +| V.4 Authorization of an EV ..... | 218 | +| V.5 Charging an EV without an EVSE ..... | 218 | +| Bibliography..... | 219 | + +# Recommendation ITU-T G.9960 + +## Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification + +# 1 Scope + +This Recommendation specifies the system architecture and functionality for all components of the physical (PHY) layer of home network transceivers designed for the transmission of data over premises' wiring, including inside telephone wiring, coaxial cable, power-line wiring, plastic optical fibres, and any combinations of these. + +Specifically, this Recommendation defines: + +- the home network architecture and reference models +- the physical layer specification (PCS, PMA and PMD). + +These transceivers are intended to be compatible with other devices sharing in-premises wiring. + +Additionally, this Recommendation provides for spectrum notching for compatibility with amateur radio services. + +# 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.117] Recommendation ITU-T G.117 (1996), *Transmission aspects of unbalance about earth*. +- [ITU-T G.9961] Recommendation ITU-T G.9961 (2015), *Unified high-speed wire-line based home networking transceivers – Data link layer specification*. +- [ITU-T G.9964] Recommendation ITU-T G.9964 (2011), *Unified high-speed wireline-based home networking transceivers – Power spectral density specification*. +- [ITU-T O.9] Recommendation ITU-T O.9 (1999), *Measuring arrangements to assess the degree of unbalance about earth*. +- [ITU-T X.1035] Recommendation ITU-T X.1035 (2007), *Password-authenticated key exchange (PAK) protocol*. +- [IEEE 802.1Q] IEEE 802.1Q-2018, *IEEE Standard for Local and metropolitan area networks: Bridges and Bridged Networks*. +<> +- [FIPS 197] FIPS PUB 197 (2001), *Advanced encryption standard (AES)*. +- [NIST-SP800-38C] NIST-SP800-38C (2004), *Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality*. + +# 3 Definitions + +This Recommendation defines the following terms: + +**3.1 address association table (AAT):** A table that associates the MAC addresses of the application entities with the DEVICE\_ID of the nodes through which these application entities can be reached. + +**3.2 alien domain:** Any group of non-ITU-T G.9960 nodes connected to the same medium or which operate in close proximity. The bridging function to an alien domain, as well as coordination with an alien domain to avoid mutual interference is beyond the scope of this Recommendation. + +**3.3 Reserved:** This clause has been intentionally left blank. + +**3.4 baseband:** A frequency band defined by an up-convert frequency $F_{UC} = 0$ and an up-shift frequency $F_{US} = F_{SC} \times N/2$ (see Table 7-67). + +**3.5 bridge to alien domain/network:** An application device implementing an L2 or L3 bridging function to interconnect an ITU-T G.9960 domain to an alien domain (or alien network). Bridging to alien domains/networks is beyond the scope of this Recommendation. + +**3.6 broadcast:** A type of communication where a node sends the same frame simultaneously to all other nodes in the home network or in the domain. + +**3.7 carrier sense (CRS):** Generated by the receiver, CRS indicates that the medium is busy, i.e., a PHY frame, or sequence of PHY frames, or a special signal (e.g., INUSE, PR) is currently transmitted on the medium by another node. CRS may be either a physical carrier sense signal or a virtual carrier sense indicator. + +- Physical carrier sense is generated by analysing physical signals present on the medium. +- Virtual carrier sense is generated based on the information on the PHY frame duration or PHY frame sequence duration derived from the frame header or communicated to a node by other means (e.g., in another frame). + +**3.8 channel:** A transmission path between nodes. One channel is considered to be one transmission path. Logically, a channel is an instance of a communication medium used for the purpose of passing data between two or more nodes. + +**3.9 coding overhead:** A part of the overhead used to carry the coding redundancy (such as redundancy bits of error correction coding or cyclic redundancy check (CRC)). + +**3.10 crosstalk:** Disturbance (including frame collision) introduced by or due to operation of alien networks or other (independent) ITU-T G.9960 home networks. + +**3.11 data:** Bits or bytes transported over the medium or via a reference point that individually convey information. Data includes both user (application) data and any other auxiliary information (overhead, including control, management, etc.). Data does not include bits or bytes that, by themselves, do not convey any information, such as the preamble. + +**3.12 data rate:** The average number of bits communicated (transmitted) in a unit of time. The usual unit of time for data rate is 1 second. + +**3.13 DEVICE\_ID:** A unique identifier allocated to a node operating in the domain by the domain master during registration. + +**3.14 domain:** A part of an ITU-T G.9960 home network comprising the domain master and all those nodes that are registered with the same domain master. In the context of this Recommendation, use of the term "domain" without a qualifier means "ITU-T G.9960 domain", and use of the term "alien domain" means "non-ITU-T G.9960 domain". Additional qualifiers (e.g., "power-line") may be added to either "domain" or "alien domain". + +**3.15 domain access point (DAP):** The unique node in centralized mode (CM) that supports relay functionality through which all nodes communicate. + +**3.16 domain ID:** A unique identifier of a domain. + +**3.17 domain master (DM):** A node supporting the domain master functionality that manages (coordinates) all other nodes of the same domain (i.e., assigns bandwidth resources and manages priorities). Only one active domain master is allowed in a domain, and all nodes within a domain are managed (coordinated) by a single domain master. If a domain master fails, another node of the same domain, capable of operating as a domain master, should pick up the function of the domain master. + +**3.18 flow:** A unidirectional stream of data between two nodes related to a specific application and/or characterized by a set of QoS requirements. + +**3.19 FLOW\_ID:** An identifier allocated to a flow for which parameterized QoS is used for traffic delivery. FLOW\_IDs are assigned by and are unique to nodes that originate flows. + +**3.20 global master (GM):** A function that provides coordination between different domains (such as communication resources, priority setting, policies of domain masters, and crosstalk mitigation). A global master may also convey management functions initiated by the remote management system (e.g., the Broadband Forum CPE WAN management protocol) to support broadband access. Detailed specification and use of this function is for further study. + +**3.21 guard interval:** The time interval intended to mitigate corruption of data carried by the symbol due to inter-symbol interference (ISI) from the preceding symbols. In this Recommendation, the guard interval is implemented as a cyclic prefix. + +**3.22 hidden node:** A node that cannot communicate directly with some other nodes within a domain. + +NOTE – A hidden node may be able to communicate with another node or with a domain master using a relay node. A node that is hidden from a domain master uses a relay node as a proxy to communicate with the domain master. + +**3.23 home network:** Two or more nodes that can communicate with each other either directly or through a relay node at the physical layer, or through an inter-domain bridge above the physical layer. A home network consists of one or more domains. In the context of this Recommendation, use of the term "home network" means "ITU-T G.9960 home network". Use of the term "alien home network" means "non-ITU-T G.9960 home network". Use of the term "network" without a qualifier means any combination of "ITU-T G.9960 home network", "non-ITU-T G.9960 home network" and "access network". Use of the term "alien network" means any combination of "non-ITU-T G.9960 home network" and "access network". + +**3.24 inter-domain bridge:** A bridging function above the physical layer to interconnect nodes of two different domains. + +**3.25 jitter:** A measure of the latency variation above and below the mean latency value. The maximum jitter is defined as the maximum latency variation above and below the mean latency value. + +**3.26 latency:** A measure of the delay from the instant when the last bit of a frame has been transmitted through the assigned reference point of the transmitter protocol stack to the instant when a whole frame reaches the assigned reference point of the receiver protocol stack. Mean and maximum latency estimations are assumed to be calculated on the 99th percentile of all latency measurements. + +If retransmission is set for a specific flow, retransmission time is a part of the latency for the protocol reference points above the MAC. + +**3.27 logical (functional) interface:** An interface in which the semantic, syntactic, and symbolic attributes of information flows are defined. Logical interfaces do not define the physical properties of signals used to represent the information. It is defined by a set of primitives. + +**3.28 management overhead:** A part of the overhead used for management purposes (such as home network discovery, channel estimation, acknowledgement, and establishing and terminating the flow). + +**3.29 medium:** A wireline facility, of a single wire class, allowing physical connection between nodes. Nodes connected to the same medium may communicate on the physical layer, and may interfere with each other unless they use orthogonal signals (e.g., different frequency bands, different time periods). + +**3.30 multicast:** A type of communication where a node sends the same frame simultaneously to one or more other nodes in the home network. + +**3.31 net data rate:** The data rate available at the A-interface of the transceiver reference model. + +**3.32 node:** Any network device that contains an ITU-T G.9960 transceiver. In the context of this Recommendation, use of the term "node" without a qualifier means "ITU-T G.9960 node", and use of the term "alien node" means "non-ITU-T G.9960 node". Additional qualifiers (e.g., "relay") may be added to either "node" or "alien node". + +**3.33 operational modes of a domain:** + +– **peer-to-peer mode (PM):** A mode of domain operation in which all nodes use only peer-to-peer (P2P) communication with other nodes (without relay nodes). In peer-to-peer mode, no relay nodes are allowed; + +– **centralized mode (CM):** A mode of domain operation in which all nodes use relayed communication (REL) with a single relay node. In centralized mode, only one relay node is allowed and it is known as the domain access point (DAP). + +NOTE – A DAP is likely to serve also as a domain master. + +– **unified mode (UM):** A mode of domain operation in which all nodes within a domain communicate using P2P or REL, as necessary, while some of the relay nodes may have additional functionalities. Unified mode can be used to support hidden nodes. In unified mode, more than one relay node is allowed. + +NOTE – In UM, there is no domain access point defined. + +**3.33.1 operational frequency band (OFB):** Range of frequencies that is allowed to be used by a node to communicate with another node of the domain. + +**3.33.2 OFB profile:** Categorization of OFBs depending on the PHY frame format they use. Profile 1 OFBs use a normal PHY frame format for transmission of frames; Profile 2 OFBs use a high capacity header (HCH) PHY frame format for transmission of frames. + +**3.34 passband:** A frequency band defined by an up-convert frequency $F_{UC} = 0$ and an up-shift frequency $F_{US} \gg F_{SC} \times N/2$ (see Table 7-67). + +**3.35 peer-to-peer communication:** A type of communication within a domain in which direct signal traffic is established between nodes with no relay nodes. + +**3.36 physical interface:** An interface defined in terms of physical properties of the signals used to represent the information transfer. A physical interface is defined by signal parameters such as power (power spectrum density), timing, and connector type. + +- 3.36.1 primary node (PN):** In a full duplex transmission, the node that requests to initiate a full duplex communication. +- 3.37 primitives:** Basic measures of quantities obtained locally or reported by other nodes of the domain. Performance primitives are basic measurements of performance-related quantities, categorized as events, anomalies and defects. Primitives may also be basic measures of other quantities (e.g., a.c. or battery power). +- 3.38 priority:** A value assigned to the specific frame(s) that determines the relative importance of transmitting frame(s) during the upcoming opportunity to use the medium. +- 3.39 quality of service (QoS):** A set of quality requirements on the communications in the home network. Support of quality of service refers to mechanisms that can provide a different priority to different flows, or can guarantee a measurable level of performance for a flow based on a set of quality of service parameters. +- 3.40 radio frequency (RF):** A frequency band defined by an up-convert frequency $F_{UC} > 0$ and a centre frequency $F_C = F_{UC} + F_{US} \gg F_{SC} \times N/2$ (see Tables 7-67 and 7-68). +- 3.41 reference point:** A location in a signal flow, either logical or physical, that provides a common point for observation and/or measurement of the signal flow. +- 3.42 registration:** The process used by a node to join the domain. +- 3.43 relay node:** A node supporting relay functionality that acts as an intermediary node, through which other nodes of the same domain can pass their traffic (data, control, or management). +- 3.44 relayed communication (REL):** A type of communication within a domain in which a node can communicate with other nodes through a relay node. The relay node receives a signal from a node and forwards it to the addressee nodes. +- 3.45 residential gateway:** A device providing, among other functions, bridging between the access network and the home network. Residential gateways are beyond the scope of this Recommendation. +- 3.45.1 secondary node (SN):** In a full duplex transmission, the node that receives a request for a full duplex transmission. +- 3.46 stopband:** The portion of the frequency spectrum that is not allowed for transmission. +- 3.47 subcarrier (OFDM subcarrier):** The centre frequency of each orthogonal frequency division multiplexing (OFDM) subchannel on to which bits may be modulated for transmission over the subchannel. +- 3.48 subcarrier spacing:** The difference between frequencies of any two adjacent orthogonal frequency division multiplexing (OFDM) subcarriers. +- 3.49 subchannel (OFDM subchannel):** A fundamental element of orthogonal frequency division multiplexing (OFDM) modulation technology. The OFDM modulator partitions the channel bandwidth into a set of parallel subchannels. +- 3.50 symbol (OFDM symbol):** A fixed time-unit of an orthogonal frequency division multiplexing (OFDM) signal carrying one or more bits of data. An OFDM symbol consists of multiple sine-wave signals or subcarriers, each modulated by a number of data bits and transmitted during a fixed time called the symbol period. +- 3.51 symbol frame:** A frame composed of bits of a single orthogonal frequency division multiplexing (OFDM) symbol period. Symbol frames are exchanged over the $\delta$ -reference point between the physical medium attachment (PMA) and physical medium dependent (PMD) sublayers of the PHY. + +- 3.52 symbol rate:** The rate, in symbols per second, at which orthogonal frequency division multiplexing (OFDM) symbols are transmitted by a node on to a medium. Symbol rate is calculated only for time periods of continuous transmission. +- 3.53 throughput:** The amount of data transferred from the A-interface of a source node to the A-interface of a destination node over some time interval, expressed as the number of bits per second. +- 3.54 transmission overhead:** A part of the overhead used to support transmission over the line (e.g., samples of the cyclic prefix, inter-frame gaps, and silent periods). +- 3.55 unicast:** A type of communication where a node sends a frame to another single node. +- 3.56 wire class:** One of the classes of wire, which has the same general characteristics: coaxial cable, home electrical-power wire, telephone-line wire and Category 5 cable. +- 3.57 actual PSD (APSD):** PSD injected by a node during a transmission. It is lower than or equal to the TxPSD, and PSD ceiling, if specified. +- 3.58 maximum actual PSD (APSD\_MAX):** Highest value of the actual PSD across the spectrum used for transmission. This value is always less than or equal to PSD ceiling. +- 3.59 PSD ceiling (PSDC):** The PSD ceiling specifies the PSD level that is used to impose a limit (i.e., a ceiling function) on the transmit signal. The PSD ceiling is independent of frequency and indicated by a single value in dBm/Hz. +- 3.60 transmit PSD mask (TxPSD):** Maximum PSD that a node is allowed to inject across the spectrum used for the transmission (see clauses 7.1.5 and 10.1.5). This may be further limited by the PSD ceiling value. +- 3.61 transmitted power:** Integral of the actual PSD over the spectrum used for transmission. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|----------------------------------| +| AAT | Address Association Table | +| ACE | Additional Channel Estimation | +| ACK | Acknowledgement | +| ADP | Application Data Primitives | +| AE | Application Entity | +| AMI | Advanced Meter Infrastructure | +| APC | Application Protocol Convergence | +| ASC | Active Subcarriers | +| BAT | Bit Allocation Table | +| CATV | Community Antenna Television | +| CB | Coax Baseband | +| CM | Centralized Mode | +| CRC | Cyclic Redundancy Check | +| CRF | Coax Radio Frequency | +| CRS | Carrier Sense | +| DAP | Domain Access Point | + +| | | +|---------|-------------------------------------| +| DID | Destination node Identifier | +| DLL | Data Link Layer | +| DM | Domain Master | +| DME | DLL Management Entity | +| DOD | Domain identifier | +| DRI | Duration Indication | +| DSL | Digital Subscriber Line | +| EHI | Extended Header Indication | +| EMS | Energy Management System | +| ESC | Energy Services Channel | +| ESI | Energy Services Interface | +| EVCF | Electric Vehicle Charging Facility | +| EVM | Error Vector Magnitude | +| EVSE | Electrical Vehicle Supply Equipment | +| FACK | Frame Acknowledgement | +| FEC | Forward Error Correction | +| FDX | Full Duplex | +| FT | Frame Type | +| FTE | Frame Type Extension | +| FTSF | Frame-Type Specific Field | +| GM | Global Master | +| HAN | Home Area Network | +| HCH | High Capacity Header | +| HCS | Header Check Sequence | +| HDX | Half Duplex | +| HE | Head End | +| HIS | Header Segmentation Indication | +| HRE | Header Repetition Encoder | +| HT | Home Terminal | +| IDB | Inter-Domain Bridge | +| IDFT | Inverse Discrete Fourier Transform | +| IDPS | Inter-Domain Presence Signal | +| IHD | In-Home Display | +| ISC | Inactive Subcarrier | +| ISI | Inter-Symbol Interference | +| LCP | Low-Complexity Profile | +| LDPC-BC | Low-Density Parity-Check Block-Code | + +| | | +|------|--------------------------------------------| +| LED | Light Emitting Diode | +| LFSR | Linear Feedback Shift Register | +| LLC | Logical Link Control | +| LSB | Least Significant Bit | +| LSSN | Lowest Segment Sequence Number | +| LV | Low Voltage | +| MAC | Medium Access Control | +| MAP | Medium Access Plan | +| MDI | Medium-Dependent Interface | +| MI | Multicast Indication | +| MIC | Message Integrity Check | +| MLC | Multi-Level Coding | +| MPDU | Media access control Protocol Data Unit | +| MSB | Most Significant Bit | +| MSC | Masked Subcarrier | +| NACK | Negative Acknowledgement | +| NME | Node Management Entity | +| NMK | Network Master Key | +| NMS | Network Management System | +| NN | Node-to-Node | +| NTR | Network Time Reference | +| OFB | Operational Frequency Band | +| OFDM | Orthogonal Frequency Division Multiplexing | +| P2P | Peer-To-Peer Communication | +| PB | Power-line Baseband | +| PBC | Public Broadcast Channel | +| PCS | Physical Coding Sublayer | +| PEV | Plug-in Electric Vehicle | +| PFH | PHY-Frame Header | +| PHEV | Plug-in Hybrid Electric Vehicle | +| PM | Peer-to-peer Mode | +| PMA | Physical Medium Attachment | +| PMD | Physical Medium Dependent | +| PME | PHY Management Entity | +| PMI | Physical Medium-independent Interface | +| PMSC | Permanently Masked Subcarrier | +| PN | Primary Node | + +| | | +|------------|--------------------------------------------------| +| PON | Passive Optical Network | +| PR | Priority Resolution | +| PRE | Payload Repetition Encoder | +| PSD | Power Spectral Density | +| PSDC | Power Spectral Density Ceiling | +| QC-LDPC-BC | Quasi-Cyclic Low-Density Parity-Check Block-Code | +| QoS | Quality of Service | +| RCM | Robust Communication Mode | +| REL | Relayed communication | +| RG | Residential Gateway | +| RMAP | Relayed Medium Access Plan | +| RMAP-A | Relayed Active Medium Access Plan | +| RMAP-D | Relayed Default Medium Access Plan | +| RMSC | Regionally Masked Subcarrier | +| SC | Security Controller | +| SGA | Smart Grid Access | +| SGH | Smart Grid HAN | +| SI | Scrambler Initialization | +| SID | Source node Identifier | +| SI-POF | Step-Index Polymer/Plastic Optical Fibres | +| SM | Subcarrier Mark | +| SN | Secondary Node | +| UAN | Utility Access Network | +| UM | Unified Mode | + +# 5 Home network architecture and reference models + +## 5.1 Home network architecture and topology + +An architectural model of the home network is presented in Figure 5-1. The model includes one or more domains, inter-domain bridges (IDB), and bridges to alien domains such as a WiFi or Ethernet home network, or a DSL or PON access network. The global master function coordinates resources such as bandwidth reservations, flow priorities, and operational characteristics between domains, and may convey the relevant functions initiated by a remote management system (e.g., as specified in [b-TR-069]) to support broadband access. Detailed specification and use of the global master function is for further study. The specification of bridges to alien domains and to the access network is beyond the scope of this Recommendation. + +NOTE 1 – It is not necessary that all inter-domain bridges presented in Figure 5-1 be used. Depending on the application, domains could be daisy-chained, or star-connected, or could use another connection topology. Support of multi-route connections between domains is for further study. + +NOTE 2 – It is possible to install multiple ITU-T G.9960 home networks (i.e., not connected by inter-domain bridges) per dwelling. + +![Figure 5-1 – Home network architecture reference model. The diagram shows three domains (Domain 1, Domain 2, and Domain S) connected to a common horizontal medium. Domain 1 (green) contains four nodes and a domain master. Domain 2 (yellow) contains four nodes and a domain master. Domain S (blue) contains two nodes and a domain master. Each domain has an 'Inter-domain bridge (logical function)' connecting it to an 'Alien domain' via 'Any medium'. A 'Global master (logical function)' is shown connecting the domain masters across all domains. Arrows indicate 'Bridge to alien domain (not in scope)' for the inter-domain bridges.](fa859e4e468bfb2710a94527f2c504af_img.jpg) + +Figure 5-1 – Home network architecture reference model. The diagram shows three domains (Domain 1, Domain 2, and Domain S) connected to a common horizontal medium. Domain 1 (green) contains four nodes and a domain master. Domain 2 (yellow) contains four nodes and a domain master. Domain S (blue) contains two nodes and a domain master. Each domain has an 'Inter-domain bridge (logical function)' connecting it to an 'Alien domain' via 'Any medium'. A 'Global master (logical function)' is shown connecting the domain masters across all domains. Arrows indicate 'Bridge to alien domain (not in scope)' for the inter-domain bridges. + +**Figure 5-1 – Home network architecture reference model** + +A domain contains nodes connected to the same medium, where one node is acting as a domain master. Nodes of the same domain communicate via the medium over which the domain is established. Nodes connected to different domains communicate via inter-domain bridges (e.g., L2 or L3 bridging, see clause 5.1.6). + +A domain shall be capable of supporting at least 32 registered nodes and may optionally support up to 250 registered nodes. Each node shall be capable of supporting simultaneous communication sessions with at least eight other nodes using dedicated sets of transmission parameters (e.g., runtime bit allocation tables (BATs)), different from the predefined BATs described in clauses 7.1.4.2.2.1 and 10.1.4.2.2.1. + +The scope of this Recommendation is limited to transceivers of all nodes capable of operating either with extended capabilities (e.g., domain master (DM), domain access point (DAP), relay node, or combinations thereof) or without extended capabilities in any domain. Other parts of this Recommendation, including inter-domain bridges, RGs (as a bridge to the access network), and bridges to alien domains, are beyond the scope of this Recommendation; however, this Recommendation defines all necessary means to support their functionality and the exchange of relevant information. + +The domain master considers bridges to alien domains as application entities (AEs) of a node with certain requirements, while it considers inter-domain bridges as AEs of nodes whose interfaces (see clause 5.1.6) comply with this Recommendation. + +### 5.1.1 Domains + +#### 5.1.1.1 General rules of operation + +A domain as depicted in Figure 5-1 may include nodes with a range of capabilities including extended capabilities such as relay, domain master, and DAP functionality, as well as nodes with limited capabilities such as low-complexity profile (LCP) nodes. + +The function of the domain master is to assign and coordinate resources (bandwidth and priorities) of all nodes in its domain. The following rules apply for any domain: + +- 1) A home network may include one or more domains. +- 2) More than one domain may be established over the same medium, for example, by using orthogonal signals over different frequency bands. +- 3) The home network shall have a unique name. All domains of the same home network shall use this name. +- 4) The domain ID shall be used to identify a specific domain. Each domain in a home network shall have a unique domain ID. +- 5) All nodes within the same domain shall use the same domain ID. +- 6) Domains from independent home networks established over the same medium may interfere with each other (e.g., if they use the same frequency band). Coordination between domains of independent home networks sharing a common medium may be performed (see clause 8.14 in [[ITU-T G.9961](#)]). +- 7) All nodes in a domain shall be managed by a single domain master. +- 8) There shall be one and only one active domain master per domain. In case an active domain master is not assigned, fails, or is switched off, a domain master selection procedure is initiated to assign a new active domain master. +- 9) Nodes are not required to be domain master capable. That is, some nodes may not support the functionality necessary to become a domain master. +- 10) Nodes of the same home network that can communicate with each other directly at the physical layer (except crosstalk between closely routed wires) shall be assigned to the same domain. +- 11) The domain master shall assign a DEVICE\_ID to a node during the node's registration process. +- 12) All nodes within a domain shall support P2P and REL (REL is considered as a subset of P2P, where the first destination address for the node is a relay node). For both P2P and REL, bandwidth resources and priorities of all nodes within the domain are managed by the domain master. +- 13) A node shall keep track of the domain where it associates and shall discard in the payload of MSG type PHY frames with DOD value different from 0 received from domains other than its own. These frames can be distinguished by examination of the DOD field in the PHY frame headers that are transmitted for these types of frames. +- 14) A node is required to report the existence of neighbouring domains to its domain master when it receives one or more PHY-frame headers containing a DOD value other than the one used in its domain or when it receives PHY-frame headers containing a DOD value of 0 (see clause 8.14 of [[ITU-T G.9961](#)]). + +#### 5.1.1.2 Modes of operation + +A domain can operate in one of three modes: peer-to-peer mode (PM), centralized mode (CM), or unified mode (UM). Different domains within the home network can use different modes of operation, i.e., PM, CM, or UM. Examples of domains in different operational modes are presented in Appendix I. + +Broadcast and multicast shall be supported in any domain, independent of their operational mode (PM, CM or UM). + +In PM, only P2P shall be used in the domain. Thus, direct signal traffic is established between two communicating nodes. Figure 5-2 shows the use of P2P between nodes A and B. Frames addressed to nodes outside the domain are sent to the node associated with the inter-domain bridge (node C in Figure 5-2). + +![Diagram of a domain operating in peer-to-peer mode (PM).](ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg) + +The diagram shows a horizontal bus line representing the domain. On the left, a box labeled 'Inter-domain bridge' is connected to the bus, with 'Node C' connected to it. 'Node A' is also connected directly to the bus. On the right, a box labeled 'Domain master node D' is connected to the bus. Below the bus, 'Node B' is connected via a vertical line. A curved arrow originates from 'Node A' and points to 'Node B', indicating direct peer-to-peer communication. The label 'G.9960(10)\_F5-2' is located at the bottom right of the diagram. + +Diagram of a domain operating in peer-to-peer mode (PM). + +**Figure 5-2 – Domain operating in peer-to-peer mode (PM)** + +In CM, only REL shall be used. Thus, any node of the domain can communicate with another node only through the DAP. The DAP receives signals from all nodes of the domain and further forwards them to the corresponding addressee nodes. Frames addressed to nodes outside the domain are forwarded by the DAP to the node associated with the inter-domain bridge (node C in Figure 5-3). Usually, but not necessarily, the DAP also serves as a domain master (Figure 5-3). + +![Diagram of a domain operating in centralized mode (CM).](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +The diagram shows a horizontal bus line. On the left, 'Node C' is connected to the bus, with an 'Inter-domain bridge' box connected to it. 'Node A' is connected directly to the bus. On the right, 'Node D' is connected to the bus; this node contains two sub-components: 'DAP' and 'Domain master'. Below the bus, 'Node B' is connected via a vertical line. A curved arrow originates from 'Node A' and points to the 'DAP' component of 'Node D'. Another curved arrow originates from the 'DAP' component and points to 'Node B', indicating that all communication must pass through the DAP. The label 'G.9960(10)\_F5-3' is located at the bottom right of the diagram. + +Diagram of a domain operating in centralized mode (CM). + +**Figure 5-3 – Domain operating in centralized mode (CM)** + +In case of DAP failure, no communication between nodes in the domain is allowed. + +In UM, a hidden node in a domain can communicate with another node through a relay node as shown in Figure 5-4. In the example, two nodes within the same domain (node C and node H) that are hidden from each other communicate with each other via the relay node (node A). Both nodes are managed by the domain master (node D) and can communicate directly with all other nodes. Frames addressed to nodes outside the domain are sent to the node associated with the inter-domain bridge (node C in Figure 5-4). + +![Diagram of a domain operating in unified mode (UM) containing hidden nodes. A central horizontal bus line has four nodes connected to it: Node C (top-left), Node A (relay node, top-center), Domain master Node D (top-right), and Node H (far-right). Node B is connected to the bus line below Node A. Curved arrows indicate signal paths: from Node C to Node A, from Node A to Node D, and from Node A to Node H. The text 'G.9960(10)_F5-4' is in the bottom right corner of the diagram area.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +Diagram of a domain operating in unified mode (UM) containing hidden nodes. A central horizontal bus line has four nodes connected to it: Node C (top-left), Node A (relay node, top-center), Domain master Node D (top-right), and Node H (far-right). Node B is connected to the bus line below Node A. Curved arrows indicate signal paths: from Node C to Node A, from Node A to Node D, and from Node A to Node H. The text 'G.9960(10)\_F5-4' is in the bottom right corner of the diagram area. + +NOTE – Nodes C and H are hidden from each other. + +**Figure 5-4 – Domain operating in unified mode (UM) containing hidden nodes** + +#### 5.1.1.3 Relationship between domain and medium + +Figure 5-5 shows several examples of the relationships between domain, medium and wire class. Note that in Figure 5-5, each of the domains is shown to be associated with a single medium. This represents the focus of ITU-T G.9960; domains optimized to operate on a single wire class with multiple domains interconnected via inter-domain bridges. Figure 5-5 (A) shows an example segment of a home network comprising three different media: coax, telephone line and power line. A single domain exists on each medium and the domains are inter-connected by inter-domain bridges. Figure 5-5 (B) shows another example segment of a home network comprising telephone-line and power-line mediums. In this case, the telephone-line medium comprises two segments of telephone wire that are joined by splicing or at a connector. These two telephone-line segments are of a single wire class and therefore are a single medium. As shown in Figure 5-5 (A), there is a single domain on each medium and the domains are inter-connected by inter-domain bridges. Figure 5-5 (C) shows the example segment of a home network from Figure 5-5 (A), but also demonstrates the potential for having multiple domains on a medium. In Figure 5-5 (C), the telephone-line medium carries three domains and the power-line medium carries two domains. The multiple domains on each individual medium within a single network shall have orthogonal signalling to avoid interference. For example, on the power line, domain C5 must have signalling that is orthogonal to signalling on domain C6. These domains communicate via the same inter-domain bridges shown that connect the different media. These inter-domain bridges have multiple internal bridge ports to connect the domains operating on the same medium. Refer to Figure I.3 for an alternative representation of multiple domains on a single medium. + +NOTE – It is possible to passively couple wire classes and operate them under a single domain. However, it is expected that such scenarios would occur very infrequently and such practices will be avoided if possible. + +![Figure 5-5: Relationships between domain, medium and wire class. The diagram shows three examples (A, B, C) of domain structures. Each domain contains a 'Medium' and a 'Wire class'. Domains are connected by 'IDB' (Inter-domain bridge) or 'Conn' (Connector or splice connection) nodes. Example A shows Domain A1 (Medium: Coax), Domain A2 (Medium: Phone), and Domain A3 (Medium: Power) connected in series via IDB nodes. Example B shows Domain B1 (Medium: Phone) connected to Domain B2 (Medium: Power) via a Conn node and an IDB node. Example C shows Domain C1 (Medium: Coax), Domain C2 (Medium: Phone), Domain C3 (Medium: Phone), Domain C4 (Medium: Phone), Domain C5 (Medium: Power), and Domain C6 (Medium: Power) connected in series via IDB nodes.](b6671cfafda3820aafe9a24fa7a4d8c7_img.jpg) + +G9960(10)\_F5-5 + +Figure 5-5: Relationships between domain, medium and wire class. The diagram shows three examples (A, B, C) of domain structures. Each domain contains a 'Medium' and a 'Wire class'. Domains are connected by 'IDB' (Inter-domain bridge) or 'Conn' (Connector or splice connection) nodes. Example A shows Domain A1 (Medium: Coax), Domain A2 (Medium: Phone), and Domain A3 (Medium: Power) connected in series via IDB nodes. Example B shows Domain B1 (Medium: Phone) connected to Domain B2 (Medium: Power) via a Conn node and an IDB node. Example C shows Domain C1 (Medium: Coax), Domain C2 (Medium: Phone), Domain C3 (Medium: Phone), Domain C4 (Medium: Phone), Domain C5 (Medium: Power), and Domain C6 (Medium: Power) connected in series via IDB nodes. + +IDB Inter-domain bridge + Conn Connector or splice connection + +**Figure 5-5 – Relationships between domain, medium and wire class** + +### **5.1.2 Node functionality** + +The main functions and capabilities of a node are summarized in Table 5-1. + +**Table 5-1 – Main functions and capabilities of a node** + +| Function | Description and parameters | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| Medium access | Receives, interprets and acts upon the medium access plan (MAP) | +| Support of admission control protocol | Supports admission control protocol | +| Support of operational modes of the domain | Supports the operational mode (PM, CM, or UM)
Complies with spectrum compatibility settings for the domain | +| Support of medium access rules | Accesses medium using medium access rules coordinated with the domain master | +| Support of security | Supports authentication and encryption key management procedures | + +**Table 5-1 – Main functions and capabilities of a node** + +| Function | Description and parameters | +|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Collection and reporting of node information | Provides statistics:
  • – List of visible nodes
  • – List of addresses (AAT)
  • – List of capabilities supported by the node
  • – Performance statistics (data rate, error count, time stamps)
  • – Statistics on detected neighbouring home networks
| +| Request of bandwidth allocation |
  • – Performs flow set up
  • – Requests bandwidth allocations from the domain master in order to meet QoS requirements of flows
| +| Support of retransmissions | Provides acknowledgment and retransmission of data units that were received with error | +| Support of extended capabilities |
  • – Domain master
  • – Domain access point (DAP)
  • – Data relaying
  • – MAP repeating
  • – Domain master selection procedure
  • – Security controller (SC)
| +| Neighbouring domain interference mitigation | Supports using near-orthogonal signals for generating and detecting the preamble, PR, INUSE and NACK signals for cases of low interference from neighbouring domains.
Supports coordination between neighbouring domains in order to mitigate high interference (Note). | +| Inter-domain communication | Acts as a proxy for the domain master for inter-domain communication such as MAC cycle alignment and coordination with neighbouring domains for interference mitigation (Note). | +| Support of management | Support node management | +| Support of power saving modes | Support of optional power saving modes: L1, L2, L3, L4 | +| NOTE – These functionalities are specified in [ITU-T G.9961] . | | + +#### 5.1.2.1 Domain master functionality + +A domain master controls operation of the nodes in the domain. The main functions of a domain master are summarized in Table 5-2. + +**Table 5-2 – Domain master functionality** + +| Function | Description | +|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Indication of presence | Periodically communicates MAP to all nodes in the domain | +| Admission control | Admits new nodes to the domain
Limits the number of nodes in a domain
Facilitates departure of nodes from the domain | +| Determination of domain operation | Assigns mode of operation inside the domain (PM, CM, or UM)
Supports hidden nodes by assigning MAP repeaters
Supports synchronization of the MAC cycle to an external source (e.g., the a.c. line)
Facilitates spectrum compatibility for the domain by assigning relevant limits on:
  • – Frequency band
  • – Maximum transmit power
  • – PSD mask
| +| Bandwidth allocation and QoS support | Assigns medium access rules to all nodes of the domain to facilitate support of QoS | +| Monitor status of the domain | Collects statistics of domain operation:
  • – List of nodes in the domain
  • – Topology
  • – Performance statistics (data rate, error count)
  • – Statistics on neighbouring domains
| +| Communication with the global master (for further study) | Coordinates operation of the domain with other domains using the global master function | +| Backup master assignment | Assigning of a backup domain master to take over the domain master role | +| Neighbouring domain interference mitigation | Coordinates the usage of near-orthogonal signals for generating and detecting the preamble, PR, INUSE and NACK signals in the domain, in order to mitigate low interference from neighbouring domains.
Supports coordination between domain masters of neighbouring domains in order to mitigate high interference (Note). | +| Inter-domain communication | Communicates with domain masters of neighbouring domains (using nodes as proxy if necessary). Inter-domain communication includes MAC cycle alignment and coordination with neighbouring domains for interference mitigation (Note). | +| Support of management | Support domain master management | +| Support of power saving modes | Support of optional power saving modes: L1, L2, L3, L4 | +| NOTE – These functionalities are specified in [ITU-T G.9961] . | | + +At any given time, only one node is allowed to act as a domain master for a domain. All other nodes within the domain are managed (coordinated) by this domain master. If a domain master fails, another node of the same domain, capable of operating as a domain master, should pick up the function of the domain master. + +### 5.1.3 Global master function + +This clause provides an overview of the global master function. Detailed specification and use of this function are for further study. + +The global master (GM) function interacts with domains and coordinates their operation by exchanging relevant information with domain masters via the logical M-interface as shown in Figure 5-6. + +![Functional model of GM diagram](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the functional model of the Global Master (GM). At the top, a box labeled 'Function of global master' is connected by solid lines to three 'Master node of domain' boxes (labeled 'domain 1', 'domain 2', and 'domain S'). These master nodes are each inside a cloud representing their respective domains. A horizontal dashed line labeled 'M-interface' separates the 'Function of global master' from the domain master nodes. Below the master nodes, the domains are interconnected: 'Domain 1' is connected to an 'Inter-domain bridge function' box, which is then connected to 'Domain 2', which is connected via a dashed line to 'Domain S'. A small label 'G.9960(10)\_F5-6' is in the bottom right corner. + +Functional model of GM diagram + +**Figure 5-6 – Functional model of GM** + +The following rules apply to the GM: + +- 1) In a multi-domain home network, the GM may coordinate some or all domains. For coordination, the GM exchanges information with domain masters of all coordinated domains via the M-interface. The GM may retrieve relevant domain-related data from domain masters and send control signals and data for coordination between domains to domain masters. +- 2) The M-interface is functional; its physical implementation is vendor discretionary. In case a domain master is replaced (e.g., as a result of a failure), the GM shall interface to the newly selected domain master. +- 3) The information exchange protocol between the GM and a domain master is unified for all domains. + +NOTE – The GM does not limit the number of domains in the home network. + +### 5.1.4 Quality of service (QoS) + +Quality of service (QoS) is a measure of the quality of delivery of services in the home network, placing requirements on the transmission and queuing of traffic. This Recommendation supports two QoS methods: priority-based QoS and parameter-based QoS. + +The QoS requirements are supported between nodes inside the same domain and between nodes connected to different domains if services communicated between nodes belong to different domains. In the latter case, inter-domain bridges are expected to not compromise the QoS requirements (such as latency). Inter-domain bridges are also expected to facilitate provisioning of QoS between nodes connected to different domains. + +Parameter-based QoS mechanism operates per flow. Flows are set up, modified and terminated on a service basis. The characteristics of the service are used to select the QoS method used to deliver the traffic associated with the flow and to determine any relevant QoS parameters. Frames belonging to a specific flow are scheduled to be sent on to the medium in accordance with the defined QoS method. The ITU-T G.9960 QoS method handles both constant and variable data-rate traffic. + +Priority-based QoS refers to a mechanism that provides different priorities for medium access based on the priority of the incoming traffic. All ITU-T G.9960 transceivers shall support priority-based QoS. The number of supported priority levels associated with the incoming application data primitives (ADPs) (at the A-interface) shall be eight (denoted from 0 to 7). + +With priority-based QoS, the ITU-T G.9960 transceiver associates incoming frames with a certain priority queue, based on priority or other priority-related parameters associated with those frames. The ITU-T G.9960 priority-based QoS method defines the order in which frames from each queue will be sent to the medium and the order in which frames will be processed (and possibly dropped), based solely on the priority assigned to the queue. The number of supported priority queues may be less than eight. The mapping between the priority of the incoming frames and the associated priority queue shall be as recommended by [IEEE 802.1Q] for user priority to traffic class mappings, as shown in Appendix III. Other methods of classification are for further study. + +Parameter-based QoS refers to a mechanism that provides specific performance metrics (QoS parameters) for a given flow associated with the application (service), and resource allocation for medium access to meet these performance metrics. A set of these parameters may include, but is not limited to, data throughput, latency or jitter. + +With parameter-based QoS, the ITU-T G.9960 transceiver associates each flow with a set of QoS parameters related to the particular service and with a certain queue. The ITU-T G.9960 parameter-based QoS method provides appropriate resources (e.g., bandwidth) necessary to communicate each flow through the medium so that QoS parameters associated with this flow are met. It also determines the order in which frames from each queue will be sent to the medium and the order in which frames will be processed (and possibly dropped) based on the knowledge of traffic parameters. The minimum number of supported flows (queues) depends on the profile. + +### 5.1.5 Security function + +The security function addresses secured operation over shared media. Besides admission procedures, which ensure that only permitted nodes can join a home network via one of its domains, this Recommendation defines point-to-point security, allowing authentication of each pair of nodes prior to communication and unique encryption keys for each pair of communicating nodes or per DLL multicast group. + +NOTE – Point-to-point security generally improves security by building another layer of protection against an intruder that has broken through the admission control, and maintains full confidentiality for all communications within the home network. This makes ITU-T G.9960 suitable for installation in public places (hotels, small businesses, home offices) requiring at least the same grade of security and confidentiality as defined in the most recent specification for wireless LAN ([b-IEEE 802.11]). + +The security function provides the following main features: + +- encryption based on AES-128 [FIPS 197] and CCM mode [NIST-SP800-38C]. +- advanced authentication and secure admission of nodes into a domain, based on: + - For native authentication: + - [\[ITU-T X.1035\]](#); + - key management, including generation, secure communication, update, and termination of encryption keys; + - high confidentiality and integrity of all transactions, including point-to-point authentication and unique encryption keys; + +- support of secure operation in the presence of relay nodes; +- For external authentication: + - Authentication mechanism defined by external AEs (e.g., IEEE 802.1X); + - high confidentiality and integrity of all transactions, including encryption keys managed by AEs (e.g., IEEE 802.1X); +- allows simultaneous operation of distinct, separately secured domains on the same medium per the rules specified in clause 5.1.1.1; +- provides user-friendly procedures for setting up a secure network. + +Security procedures that are user-friendly may require the user to set a password for each node prior to installation. The rest of the procedures necessary to establish and maintain security are facilitated automatically by the security controller (SC) function, without involvement of the user. + +Nodes that do not include an appropriate user interface may use a unique manufacturer-set password. + +Security and mutual confidentiality between applications associated with the same node are supposed to be resolved at the higher layers of the protocol stack and are beyond the scope of this Recommendation. + +### 5.1.6 Inter-domain bridging + +The inter-domain bridge (IDB) function connects nodes of two domains. In Figure 5-7, application entities AE1 (service originator) and AE2 (service destination) are associated with nodes A1 and B2, respectively, of two domains. The communication path between nodes A1 and B2 goes through domain 1 and domain 2, and includes in-domain flows F1, F2 and the IDB function. Interfaces between nodes B1, A2 and the IDB are AE interfaces (A-interfaces, see clause 5.2.1). Communication paths routed through more than two domains operate in the same way. + +![Diagram illustrating the communication path between nodes of two different domains. Domain 1 contains nodes A1 and B1, with flow F1 between them. Domain 2 contains nodes A2 and B2, with flow F2 between them. The IDB function connects B1 and A2. AE1 is connected to A1, and AE2 is connected to B2.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +The diagram shows two domains, Domain 1 and Domain 2, connected by an IDB function. Domain 1 contains nodes A1 and B1, with a flow F1 from A1 to B1. Domain 2 contains nodes A2 and B2, with a flow F2 from A2 to B2. The IDB function is connected to B1 and A2. AE1 is connected to A1, and AE2 is connected to B2. The diagram is labeled G.9960(10)\_F5-7. + +Diagram illustrating the communication path between nodes of two different domains. Domain 1 contains nodes A1 and B1, with flow F1 between them. Domain 2 contains nodes A2 and B2, with flow F2 between them. The IDB function connects B1 and A2. AE1 is connected to A1, and AE2 is connected to B2. + +**Figure 5-7 – Communication path between nodes of two different domains** + +The protocol reference model for inter-domain communications shown in Figure 5-7 is presented in Figure 5-8. + +![Figure 5-8: Protocol stack of inter-domain communication. The diagram shows two domains, Medium - Domain 1 and Medium - Domain 2, connected by an IDB function. Domain 1 contains Node A1 (AE1, APC, LLC, MAC, PHY) and Node B1 (APC, LLC, MAC, PHY). Domain 2 contains Node A2 (APC, LLC, MAC, PHY) and Node B2 (AE2, APC, LLC, MAC, PHY). The IDB function is connected to Node B1 and Node A2.](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +G.9960(10)\_F5-8 + +Figure 5-8: Protocol stack of inter-domain communication. The diagram shows two domains, Medium - Domain 1 and Medium - Domain 2, connected by an IDB function. Domain 1 contains Node A1 (AE1, APC, LLC, MAC, PHY) and Node B1 (APC, LLC, MAC, PHY). Domain 2 contains Node A2 (APC, LLC, MAC, PHY) and Node B2 (AE2, APC, LLC, MAC, PHY). The IDB function is connected to Node B1 and Node A2. + +**Figure 5-8 – Protocol stack of inter-domain communication** + +In the case that the APC is implemented as an Ethernet convergence sublayer, the IDB function can be implemented as a standard IEEE 802.1Q bridge. The means to avoid loops between multiple domains are for further study. + +One case of inter-domain bridging relates to implementation of multimedia devices, which are equipped with more than one physical interface and, accordingly, can be connected to more than one domain. A scenario describing a two-media device is presented in Figure 5-9. The IDB connects the AE associated with the device to both domains (via nodes B1 and A2), and provides inter-domain connection (between nodes B1 and A2, similar to the one presented in Figure 5-7). The IDB interfaces to nodes B1 and A2 as an AE, and also bridges the AE to either or both of these nodes. + +![Figure 5-9: Example of communication with a two-media (domain) device. A central 'Two-media device' contains an 'IDB function' and an 'AE'. The IDB function is connected to Node B1 in Domain 1 and Node A2 in Domain 2. Node B1 is connected to Node A1 in Domain 1, which is connected to AE1. Node A2 is connected to Node B2 in Domain 2, which is connected to AE2. Arrows F1 and F2 indicate communication paths between the domains through the IDB function.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +G.9960(10)\_F5-9 + +Figure 5-9: Example of communication with a two-media (domain) device. A central 'Two-media device' contains an 'IDB function' and an 'AE'. The IDB function is connected to Node B1 in Domain 1 and Node A2 in Domain 2. Node B1 is connected to Node A1 in Domain 1, which is connected to AE1. Node A2 is connected to Node B2 in Domain 2, which is connected to AE2. Arrows F1 and F2 indicate communication paths between the domains through the IDB function. + +**Figure 5-9 – Example of communication with a two-media (domain) device** + +The protocol reference model corresponding to Figure 5-9 is presented in Figure 5-10. It assumes a vendor-proprietary interface between the IDB and the AE. However, a standard interface like IEEE 802.3 can also be used. + +![Figure 5-10: Protocol stack of inter-domain communication. This diagram extends Figure 5-8 by adding a 'Two-media device' scenario. Domain 1 contains Node A1 (AE1, APC, LLC, MAC, PHY) connected to Medium - Domain 1. Domain 2 contains Node B2 (AE2, APC, LLC, MAC, PHY) connected to Medium - Domain 2. A central 'IDB function' is connected to Node B1 (APC, LLC, MAC, PHY) in Domain 1 and Node A2 (APC, LLC, MAC, PHY) in Domain 2. The IDB function is also connected to an 'AE' via a 'Proprietary APC/LLC/MAC/PHY' interface.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +G.9960(10)\_F5-10 + +Figure 5-10: Protocol stack of inter-domain communication. This diagram extends Figure 5-8 by adding a 'Two-media device' scenario. Domain 1 contains Node A1 (AE1, APC, LLC, MAC, PHY) connected to Medium - Domain 1. Domain 2 contains Node B2 (AE2, APC, LLC, MAC, PHY) connected to Medium - Domain 2. A central 'IDB function' is connected to Node B1 (APC, LLC, MAC, PHY) in Domain 1 and Node A2 (APC, LLC, MAC, PHY) in Domain 2. The IDB function is also connected to an 'AE' via a 'Proprietary APC/LLC/MAC/PHY' interface. + +**Figure 5-10 – Protocol stack of inter-domain communication** + +#### 5.1.6.1 End-to-end QoS for multi-domain connections + +The end-to-end QoS requirements are defined by priority level (in case of priority-based QoS), or by traffic parameters such as data rate and latency (for parameterized QoS). See clause 5.1.4. In both cases, to meet end-to-end requirements, requirements are imposed on in-domain flows forming the connection and on the IDB. In Figure 5-7, the end-to-end QoS requirements for the service routed between nodes A1 and B2 determine QoS requirements for flow F1, carrying the service inside domain 1, and for flow F2, carrying the service inside domain 2, and for the delay introduced by the IDB. + +In the case of prioritized QoS, the end-to-end QoS requirements can be met if the IDB conveys priority requirements, so that the priority level applied to flow F1 in domain 1 corresponds to the priority level applied to flow F2 in domain 2. In the same way, prioritized QoS shall be supported for situations where the route for delivery of traffic between two nodes includes more than two domains. + +In the case of parameterized QoS, the end-to-end QoS parameters shall be distributed between in-domain flows and the IDBs. The rules of distribution of end-to-end QoS parameters between multiple domains are for further study. + +The IDB throughput shall be higher than the maximum throughput available in either of the domains connected by the IDB. The delay introduced by the IDB should be minimized (the maximum allowed values are for further study). The maximum number of IDBs in the path may be limited for certain service types. + +Other parameters of the IDB functionality are vendor discretionary. + +#### 5.1.6.2 Security in multi-domain connections + +For a multi-domain home network, secure operation is achieved by setting all its domains to secure mode. Communications between secure and non-secure domains shall not be allowed, unless special security measures are provided by the IDB (on higher protocol levels). These measures are beyond the scope of this Recommendation, as are security measures protecting the IDB from outside intrusion (i.e., when the intruder is one of the AEs connected to the IDB). + +## 5.2 Reference models + +### 5.2.1 Protocol reference model of a home network transceiver + +The protocol reference model of a home network transceiver is presented in Figure 5-11. It includes three main reference points: application interface (A-interface), physical medium-independent interface (PMI), and medium-dependent interface (MDI). Two intermediate reference points, x1 and x2, are defined in the data link layer, and two other intermediate reference points, $\alpha$ and $\delta$ , are defined in the PHY layer (Figure 5-11). + +The MDI is a physical interface defined in terms of the physical signals transmitted over a specific medium (see clauses 7.2 and 10.2) and mechanical connection to the medium. + +The PMI interface is both medium independent and application independent. It is defined in clause 5.2.2.2 as a functional interface, in terms of functional flows and logical signals. + +The A-interface is user application-protocol specific (e.g., Ethernet, IP). The functional description of the A-interface is presented in clause 5.2.2.1. + +All intermediate reference points are independent of the type of medium and are defined as functional (logical) interfaces in terms of the functional flows and logical signals. + +![Figure 5-11: Protocol reference model of a home network transceiver. The diagram shows the mapping between the OSI reference model layers and the transceiver sublayers. The OSI model includes the Network Layer, Data Link Layer, and Physical Layer. The transceiver sublayers are APC, LLC, MAC, PCS, PMA, and PMD. Interfaces are labeled: A-interface (between AE and APC), x1-reference point (between APC and LLC), x2-reference point (between LLC and MAC), PMI (between MAC and PCS), alpha-reference point (between PCS and PMA), delta-reference point (between PMA and PMD), and MDI (between PMD and Transmission medium). A legend defines the sublayers: APC (Application protocol convergence), LLC (Logical link control), MAC (Medium access control), PCS (Physical coding sub-layer), PMA (Physical medium attachment), PMD (Physical medium dependent), PMI (Physical medium-independent interface), and MDI (Medium-dependent interface).](8c348bf9c2c81b018017ae1d19506a9a_img.jpg) + +G.9960(10)\_F5-11 + +APC Application protocol convergence + LLC Logical link control + MAC Medium access control + PCS Physical coding sub-layer + PMA Physical medium attachment + PMD Physical medium dependent + PMI Physical medium-independent interface + MDI Medium-dependent interface + +Figure 5-11: Protocol reference model of a home network transceiver. The diagram shows the mapping between the OSI reference model layers and the transceiver sublayers. The OSI model includes the Network Layer, Data Link Layer, and Physical Layer. The transceiver sublayers are APC, LLC, MAC, PCS, PMA, and PMD. Interfaces are labeled: A-interface (between AE and APC), x1-reference point (between APC and LLC), x2-reference point (between LLC and MAC), PMI (between MAC and PCS), alpha-reference point (between PCS and PMA), delta-reference point (between PMA and PMD), and MDI (between PMD and Transmission medium). A legend defines the sublayers: APC (Application protocol convergence), LLC (Logical link control), MAC (Medium access control), PCS (Physical coding sub-layer), PMA (Physical medium attachment), PMD (Physical medium dependent), PMI (Physical medium-independent interface), and MDI (Medium-dependent interface). + +**Figure 5-11 – Protocol reference model of a home network transceiver** + +The application protocol convergence (APC) sublayer provides an interface with the application entity (AE), which operates with an application-specific protocol, such as Ethernet. The APC also provides the data rate adaptation between the AE and the home network transceiver. + +The logical link control (LLC) sublayer coordinates transmission of nodes in accordance with requests from the domain master. In particular, it is responsible for establishing, managing, resetting and terminating all connections of the node inside the domain. The LLC also facilitates quality of service (QoS) constraints of the flow, defined for its various connections. + +The MAC sublayer controls access of the node to the medium using various medium access protocols. + +The PCS provides data rate adaptation (data flow control) between the MAC and PHY and encapsulates transmit media access control protocol data units (MPDUs) into the PHY frame and adds PHY-related control and management overhead. The PMA provides encoding of PHY frame content for transmission over the medium. The PMD modulates and demodulates PHY frames for transmission over the medium using orthogonal frequency division multiplexing (OFDM). By implementation, the PMD may include medium-dependent adaptors for different media, including frequency shifting for passband transmission. + +The layers above the data link layer (above the A-interface) are beyond the scope of this Recommendation. Management functions are not presented in Figure 5-11. + +### 5.2.2 Interfaces – functional description + +This clause contains the functional description of the ITU-T G.9960 transceiver interfaces (A, PMI, and MDI) in terms of signal flows exchanged between corresponding entities. The description does not imply any specific implementation of the transceiver interfaces. + +#### 5.2.2.1 A-interface + +The A-interface is described in terms of primitives exchanged between the AE and the DLL. There are six general types of A-interface primitives, as shown in Table 5-3. Each primitive type may consist of one or more primitives, related to control or data, respectively. Data primitives represent the data path of the A-interface, while control primitives represent the control path. The format of the + +application data primitives (ADPs) is application specific, determined by the AE. See [ITU-T G.9961] for further description of the application protocol convergence (APC) specific sublayer. + +**Table 5-3 – A-interface primitive type summary** + +| Primitive type | Direction | Description | +|----------------|-----------|-------------------------------------| +| AIF_DATA.REQ | AE → DLL | Data from AE to DLL | +| AIF_DATA.CNF | DLL → AE | Data confirmation from DLL to AE | +| AIF_DATA.IND | DLL → AE | Data from DLL to AE | +| AIF_CTRL.REQ | AE → DLL | Control from AE to DLL | +| AIF_CTRL.CNF | DLL → AE | Control confirmation from DLL to AE | +| AIF_CTRL.IND | DLL → AE | Control from DLL to AE | + +#### 5.2.2.2 Physical medium-independent interface (PMI) + +The PMI is described in terms of primitives exchanged between the DLL and PHY layer presented in Table 5-4; the direction of each primitive flow indicates the entity originating the primitive. Both transmit and receive data primitives are exchanged in MAC protocol data units (MPDUs). + +**Table 5-4 – PMI primitive description** + +| Primitive | Direction | Description | +|--------------------|-----------|---------------------------------------------------------------| +| PMI_DATA.REQ | DLL → PHY | Flow of MPDUs for transmission | +| PMI_CTRL-RxDis.REQ | DLL → PHY | Disables receive of PHY frames | +| PMI_DATA.IND | PHY → DLL | Flow of received MPDUs | +| PMI_CTRL-ERR.IND | PHY → DLL | Error primitive that accompanies an MPDU received with errors | +| PMI_CTRL-CRS.IND | PHY → DLL | Carrier sense primitive | +| RX ENABLE | DLL → PHY | Enable receive function in the PHY layer | + +NOTE – Primitives presented in this table are exclusively for descriptive purposes and do not imply any specific implementation. + +#### 5.2.2.3 Medium-dependent interface (MDI) + +Functional characteristics of the MDI are described by two signal flows: + +- transmit signal (TX DATA) is the flow of frames transmitted on to the medium; +- receive signal (RX DATA) is the flow of frames received from the medium. + +### 5.2.3 Functional model of a home network transceiver + +The functional model of a home network transceiver is presented in Figure 5-12. It addresses nodes without extended capabilities, as well as nodes with extended capabilities such as domain master, and relaying (including DAP), which differ by their MAC, LLC and upper layer functionalities. + +The PMD function depends on the medium on which the transceiver operates. It can be configured to operate in different frequency bands. The PCS provides data rate adaptation (data flow control) between the MAC and the PHY and encapsulates transmit MAC protocol data units (MPDUs) into PHY frames. The transmit PHY frame is further encoded in the PMA to meet the corresponding PMD. The functionality of the PCS, and the PMA is the same for any medium, but their parameters are medium-specific. By appropriate parameter settings, any node can be configured to operate on any type of wiring in any allowed frequency. + +![Functional model of a home network transceiver diagram showing layers from Data primitives down to the Medium. The diagram includes Data primitives, Control primitives, APC, LLC, MAC, MPDU, PMI, PCS, PMA, PMD (passband/baseband), MDI, Tx / Rx frames, and Medium. Management blocks for DLL and PHY are shown on the right side.](11edb7fcedf09ac6a817f8d7b8c61eec_img.jpg) + +The diagram illustrates the functional model of a home network transceiver. At the top, 'Data primitives' and 'Control primitives' are shown. A dashed line labeled 'A' separates these from the main stack. The main stack consists of several layers: APC, LLC, and MAC. Below MAC is the 'MPDU' (Media Access Protocol Data Unit). A dashed line labeled 'PMI' separates the MAC/MPDU section from the PHY section. The PHY section includes PCS, PMA, and PMD (passband/baseband). Below PMD is the 'MDI' (Media Dependent Interface). A dashed line labeled 'MDI' separates the MDI from the 'Tx / Rx frames' which are then passed to the 'Medium'. On the right side, there are two management blocks: 'DLL management' which connects to the MAC and LLC layers, and 'PHY management' which connects to the PCS, PMA, and PMD layers. The diagram is labeled 'G.9960(10)\_F5-12' at the bottom right. + +Functional model of a home network transceiver diagram showing layers from Data primitives down to the Medium. The diagram includes Data primitives, Control primitives, APC, LLC, MAC, MPDU, PMI, PCS, PMA, PMD (passband/baseband), MDI, Tx / Rx frames, and Medium. Management blocks for DLL and PHY are shown on the right side. + +**Figure 5-12 – Functional model of a home network transceiver** + +The detailed description of the functional model of the PHY layer is presented in clause 7.1. The detailed description of the functional model of the HCS-PHY layer is presented in clause 10.1. The DLL is specified in [ITU-T G.9961]. + +### 5.2.4 Bit ordering convention + +A block of data composed of multiple octets shall be ordered by octet numbers in ascending order: "octet 0" for the first octet, "octet 1" for the second octet, and so on. If a block of data is segmented into multiple fields, the size of each field shall be expressed in terms of bits. The field is not necessarily an integer number of octets. The location of each field within a block of data shall be described as follows: + +- The octets of an $N$ -octet data block are ordered with numbers from 0 (first octet) to $N-1$ (last octet). +- The block is divided into non-overlapping groups of octets. Each group contains an integer number of consecutive octets, numbered from $J$ to $J+V-1$ , where $V$ is the size of the group, and is described as a bit string with "bit 0", the LSB of the octet with the smallest number ( $J$ ), and "bit $(8 \times V-1)$ ", the MSB of the octet with the largest number ( $J+V-1$ ). +- Each group is divided into one or more fields, where the boundaries of each field are determined by the LSB and the MSB of the bits of the group that contains this field. + +Any block of data or part of it shall be passed over the protocol stack with the octet having the smallest number, i.e., octet 0 shall be the first octet of the block to be passed. Within each group of octets, LSB (bit 0) of each octet shall be passed first. + +Table 5-5 shows an example of a field description used throughout this Recommendation. The "Octet" column represents the octet numbers for a group of octets to which a specific field belongs, and the "Bits" column represents the bit location within this group of octets. In the presented example, there are 4 groups of octets: + +- Group 1 = Octet 0, fields A, B, C, D +- Group 2 = Octets 1 and 2, fields E, F +- Group 3 = Octet 3, field G +- Group 4 = Octets 4 to 7, field H. + +Figure 5-13 illustrates a mapping of these fields on to corresponding octets based on the example given in Table 5-5. + +**Table 5-5 – An example of field description** + +| Field | Octet | Bits | Description | +|-------|---------|--------|-------------| +| A | 0 | [2:0] | ... | +| B | | [3] | ... | +| C | | [4] | ... | +| D | | [7:5] | ... | +| E | 1 and 2 | [1:0] | ... | +| F | | [15:2] | ... | +| G | 3 | [7:0] | ... | +| H | 4 to 7 | [31:0] | ... | + +![Diagram showing the mapping of fields A-H onto octets 0-7. Octet 0 contains fields D, C, B, and A. Octets 1 and 2 contain field F, with E in the lower bits of octet 1. Octet 3 contains field G. Octets 4, 5, 6, and 7 contain field H. A vertical arrow on the left indicates the order of transmission from octet 0 down to 7. A horizontal arrow at the top indicates the order of transmission from right to left (b0 to b7).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Order of transmission ← + +| Octet | b7 (MSB) | b6 | b5 | b4 | b3 | b2 | b1 | b0 (LSB) | +|-------|----------|----|----|----|----|----|----|----------| +| 0 | D | | | C | B | A | | | +| 1 | F | | | | | | | E | +| 2 | F | | | | | | | | +| 3 | G | | | | | | | | +| 4 | H | | | | | | | | +| 5 | H | | | | | | | | +| 6 | H | | | | | | | | +| 7 | H | | | | | | | | + +G.9960(10)\_F5-13 + +Diagram showing the mapping of fields A-H onto octets 0-7. Octet 0 contains fields D, C, B, and A. Octets 1 and 2 contain field F, with E in the lower bits of octet 1. Octet 3 contains field G. Octets 4, 5, 6, and 7 contain field H. A vertical arrow on the left indicates the order of transmission from octet 0 down to 7. A horizontal arrow at the top indicates the order of transmission from right to left (b0 to b7). + +**Figure 5-13 – An example of mapping fields on to groups of octets** + +## 5.3 Management-plane reference model + +Figure 5-14 illustrates data-, control-, and management-plane reference models for an ITU-T G.9960/G.9961 transceiver. Details of data- and control-plane reference models are shown in clause 5.2. The Q-interface provides the interface between the network management systems (NMS) and the node management entity (NME) at a node. The definition of parameters at the Q-interface and the transport of the management instrumentation over the Q-interface are outside the scope of this Recommendation. + +![Figure 5-14 – Management-plane reference model. The diagram shows three reference models: Data-plane, Control-plane, and Management-plane. The Data-plane contains a PHY and a DLL. The Control-plane contains a PHY management entity (PME) and a DLL management entity (DME). The Management-plane contains a Node management entity (NME). The Data-plane and Control-plane are connected by an MDI. The Control-plane and Management-plane are connected by an A interface. The Management-plane is connected to a Network management system (NMS) by a Q interface. The Data-plane and Control-plane are connected by a dashed line labeled 'Data-plane reference model' and 'Control-plane reference model'. The Management-plane is connected to the NMS by a dashed line labeled 'Management-plane reference model'. The NME is connected to the NMS by a dashed line labeled 'Q interface'. The MDI is connected to the PHY and PHY management entity (PME) by a dashed line labeled 'MDI'. The DME is connected to the NME by a dashed line labeled 'A interface'. The NMS is represented by a cloud shape.](692541e65db4dc852988ce77ebb60ce5_img.jpg) + +Figure 5-14 – Management-plane reference model. The diagram shows three reference models: Data-plane, Control-plane, and Management-plane. The Data-plane contains a PHY and a DLL. The Control-plane contains a PHY management entity (PME) and a DLL management entity (DME). The Management-plane contains a Node management entity (NME). The Data-plane and Control-plane are connected by an MDI. The Control-plane and Management-plane are connected by an A interface. The Management-plane is connected to a Network management system (NMS) by a Q interface. The Data-plane and Control-plane are connected by a dashed line labeled 'Data-plane reference model' and 'Control-plane reference model'. The Management-plane is connected to the NMS by a dashed line labeled 'Management-plane reference model'. The NME is connected to the NMS by a dashed line labeled 'Q interface'. The MDI is connected to the PHY and PHY management entity (PME) by a dashed line labeled 'MDI'. The DME is connected to the NME by a dashed line labeled 'A interface'. The NMS is represented by a cloud shape. + +**Figure 5-14 – Management-plane reference model** + +# 6 Profiles + +Profiles are intended to specify nodes with significantly different levels of complexity and functionality. For every domain type, a more complex profile is a superset of less complex profile and shall interoperate with that profile. A node shall be classified into particular profiles according to its degree of complexity and functionality. For compliance with this Recommendation, a node is required to support one profile, at a minimum. Profiles are summarized in Table 6-1. + +**Table 6-1 – Profiles** + +| Profile name | Domain type | Valid operational frequency bands (Note 1) | | +|------------------------|-------------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| +| | | Valid OFBs when using normal frame format (PHY) (Note 3,7) – Profile 1 OFBs | Valid OFBs when using high capacity header PHY frame format (HCH-PHY) (Note 4) – Profile 2 OFBs | +| Low-complexity profile | Power-line | 25 MHz | (Note 5) | +| Standard profile | Power-line | 50 MHz, 100 MHz | (Note 5) | +| | Telephone-line (Note 2) | 50 MHz-TB, 100 MHz-TB, 200 MHz-TB | K-OFB (Note 6) | +| | Coax | 50 MHz-CB, 100 MHz-CB, 200 MHz-CB | K-OFB (Note 6) | +| | Coax RF | 50 MHz-CRF, 100 MHz-CRF, 200 MHz-CRF | | + +NOTE 1 – In order to be compliant with a given profile, at least one operational frequency band shall be implemented. The 200 MHz-CRF operational frequency band is applicable to Annex C only. + +NOTE 2 – Telephone-line profiles are also applicable to any other pair-based copper cable (e.g., Cat5). + +NOTE 3 – PHY is defined in clause 7. + +NOTE 4 – HCH-PHY is defined in clause 10. + +NOTE 5 – The definition of OFBs using HCH-PHY for powerline is for further study. + +NOTE 6 – K-OFB is defined by the use of a $K_{min}$ parameter chosen by the transmitter for RCM transmissions (the bandwidth used during RCM transmissions is derived from $K_{min}$ as explained in clause 10.1.3.3.1). + +NOTE 7 – OFBs making use of SFH-PHY format are defined by a starting frequency and stop frequency to be used when calculating RCM parameters. Therefore, the OFBs are named following these boundaries (e.g., 50 MHz). + +## 6.1 Low-complexity profile (LCP) + +Table 6-2 describes the valid values of parameters for the low-complexity profile (LCP) that differentiate it from other profiles. + +**Table 6-2 – Valid parameters for the low-complexity profile** + +| Parameters | Description | +|----------------|----------------------------------------------------| +| EVM | See clauses 7.2.4 and 10.2.4 | +| BAT | Type 0, Type 1, Type 2, and Type 3 predefined BATs | +| FEC rate | Rate $\frac{1}{2}$ | +| FEC block size | 120 bytes (Payload) | + +## 6.2 Standard profile + +Table 6-3 describes the valid values of parameters for the standard profile that differentiate it from other profiles. + +**Table 6-3 – Valid parameters for the standard profile** + +| Parameters | Description | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EVM | See clauses 7.2.4, 10.2.4 and C.2.3.4 | +| BAT | Type 0, Type 1, Type 2 and Type 3 predefined BATs.
Supports at least a total of 8 simultaneous runtime BATs assuming no grouping (including transmit and receive BATs) | +| FEC rate | Rate $\frac{1}{2}$ , $\frac{2}{3}$ , $\frac{5}{6}$ , $\frac{16}{18}$ , and $\frac{20}{21}$ | +| FEC block size | 120 and 540 bytes (Payload) | + +## 6.3 Operational frequency band (OFB) + +An operational frequency band (OFB) is defined as a range of frequencies that is allowed to be used by a node to communicate with another node of the domain. + +The OFB is defined by: + +- **Profile 1 OFBs:** Both minimum and maximum frequencies available for communication are defined in the OFB. +- **Profile 2 OFBs:** The maximum frequency available for communication is not defined by OFB and is set by other means (e.g., capabilities of the modem). There is only an OFB in this category: K-OFB (see Table 6-1). + +When using a Profile 1 OFB, the node shall use the PHY layer specified in clause 7. + +When using a Profile 2 OFB, the node shall use the high capacity header PHY (HCH-PHY) layer specified in clause 10. + +Annex J of this Recommendation specifies the rules that a node shall follow to guarantee interoperability in a domain allowing both Profile 1 and Profile 2 OFBs. + +# 7 Physical layer specification (PHY layer) + +## 7.1 Medium independent specification + +### 7.1.1 Functional model of the PHY + +The functional model of the PHY is presented in Figure 7-1. The PMI and MDI are, respectively, two demarcation reference points between the PHY and MAC and between the PHY and the transmission medium. Internal reference points $\delta$ and $\alpha$ show separation between the PMD and PMA, and between the PCS and PMA, respectively. + +![Functional model of the PHY diagram showing data flow from MAC to Medium through PCS, PMA, and PMD sublayers, with control data from PHY management.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +The diagram illustrates the functional model of the PHY. It shows three main sublayers: Physical coding (PCS), Physical media attachment (PMA), and Physical medium dependent (PMD). Data flow is indicated by vertical arrows: 'MPDU in' enters the PCS from the MAC via the PMI; 'TX PHY frame' is passed from the PCS to the PMA at the $\alpha$ -reference point; 'TX symbol frames' are passed from the PMA to the PMD at the $\delta$ -reference point; and the data is transmitted over the 'Medium' via the MDI. In the receive direction, 'RX symbol frames' are received from the Medium through the PMD, 'RX PHY frame' is passed to the PMA, and 'MPDU out' is passed to the MAC via the PMI. Control data from 'PHY management' is shown being passed to each sublayer via horizontal arrows: 'PCS control data' to the PCS, 'PMA control data' to the PMA, and 'PMD control data' to the PMD. The diagram is labeled 'G.9960(10)\_F7-1' at the bottom right. + +Functional model of the PHY diagram showing data flow from MAC to Medium through PCS, PMA, and PMD sublayers, with control data from PHY management. + +**Figure 7-1 – Functional model of the PHY** + +In the transmit direction, data enters the PHY from the MAC via the PMI in blocks of bytes called MAC protocol data units (MPDUs). The incoming MPDU is mapped into a PHY frame in the PCS, scrambled and encoded in the PMA, modulated in the PMD, and transmitted over the medium using OFDM modulation with relevant parameters. In the PMD, a preamble is added to assist synchronization and channel estimation in the receiver. + +In the receive direction, frames entering from the medium via the MDI are demodulated and decoded. The recovered MPDUs are forwarded to the MAC via the PMI. The recovered PHY-frame headers are processed in the PHY to extract the relevant frame parameters specified in clause 7.1.2.3. + +### 7.1.2 Physical coding sublayer (PCS) + +The functional model of the PCS is presented in Figure 7-2. It is intended to describe in more detail the PCS functional block presented in Figure 7-1. + +![Functional model of PCS diagram showing transmit and receive paths between PMI, MPDU mapper/de-mapper, Header generation/processing, MUX (TDM), and PHY management.](f9c64800d9bace9b4315646d1057be3c_img.jpg) + +The diagram illustrates the functional model of the Physical Coding Sublayer (PCS). It is divided into two main sections: the transmit (TX) path on the left and the receive (RX) path on the right, separated by a vertical line representing the PHY management entity. + +In the TX path, an 'MPDU in' from the PMI enters an 'MPDU mapper'. The output of the mapper goes to a 'MUX (TDM)' and also to a 'Header generation' block. The 'MUX (TDM)' outputs a 'TX PHY frame' at the $\alpha$ -reference point. + +In the RX path, an 'RX PHY frame' enters from below the $\alpha$ -reference point into a 'Header processing' block. The output of this block goes to the 'PHY management' entity and also to an 'MPDU de-mapper'. + +The 'PHY management' entity sends 'PCS control data' to both the 'Header generation' and 'Header processing' blocks. + +The 'MPDU de-mapper' outputs an 'MPDU out' to the PMI. + +Dashed horizontal lines separate the PMI section at the top from the rest of the PCS, and the $\alpha$ -reference point section at the bottom. The diagram is labeled 'G.9960(10)\_F7-2'. + +Functional model of PCS diagram showing transmit and receive paths between PMI, MPDU mapper/de-mapper, Header generation/processing, MUX (TDM), and PHY management. + +**Figure 7-2 – Functional model of PCS** + +In the transmit direction, the incoming MPDU is mapped into a payload field of a PHY frame (clause 7.1.2.1) as described in clause 7.1.2.2. The PHY-frame header (clause 7.1.2.3) is then added to form a TX PHY frame. The TX PHY frame is passed across the $\alpha$ -reference point for further processing in the PMA. + +In the receive direction, the decoded PHY-frame payload and header are processed, and originally transmitted MPDUs are recovered from the payloads of received PHY frames and submitted to the PMI. Relevant control information conveyed in the PHY-frame header is processed and submitted to the PHY management entity. + +#### 7.1.2.1 PHY frame + +The format of the PHY frame is presented in Figure 7-3. The PHY frame at the $\alpha$ -reference point includes a header, and a payload. The preamble and additional channel estimation (ACE) symbols are added to the PHY frame in the PMD, as described in clauses 7.1.4.5 and 7.1.4.2.5, respectively. The preamble does not carry any user or management data and is intended for synchronization and initial channel estimation. + +![Format of the PHY frame diagram showing a horizontal bar with four segments: Preamble, Header (1, 2 or 4 symbols), Additional channel estimation symbols, and Payload.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +The diagram shows the format of a PHY frame as a horizontal bar divided into four segments. From left to right, the segments are: 'Preamble' (orange), 'Header 1, 2 or 4 symbols' (green), 'Additional channel estimation symbols' (orange), and 'Payload' (white). The diagram is labeled 'G.9960(10)\_F7-3'. + +Format of the PHY frame diagram showing a horizontal bar with four segments: Preamble, Header (1, 2 or 4 symbols), Additional channel estimation symbols, and Payload. + +**Figure 7-3 – Format of the PHY frame** + +The PHY-frame header and payload shall each contain an integer number of OFDM symbols. + +The PHY-frame header always fits into an integer number of symbols and is transmitted using a single predefined set of modulation and coding parameters (see clause 7.1.3.4). + +The presence of ACE symbols is frame type dependent (see clause 7.1.2.3). + +The length of the payload may vary from frame to frame; the payload may be of zero length. For the payload, different coding parameters and bit loading can be used in different frames, depending on the channel/noise characteristics and QoS requirements. + +The types of PHY frames used in this Recommendation are summarized in Table 7-1. + +**Table 7-1 – PHY frame types** + +| Frame type | Header | Payload | Description | Reference | +|------------|--------|---------|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------| +| MAP/RMAP | √ | √ | A frame carrying the MAP or RMAP; the payload contains an MPDU | Clause 7.1.2.3.2.1, clause 8.8 of [ ITU-T G.9961 ] | +| MSG | √ | √ | A frame carrying user data or management data or both; the payload contains an MPDU | Clause 7.1.2.3.2.2 | +| ACK | √ | None | An acknowledgement frame; the relevant ARQ data is communicated in the header | Clause 7.1.2.3.2.3 | +| RTS | √ | None | A request-to-send frame; the relevant data is communicated in the header | Clause 7.1.2.3.2.4 | +| CTS | √ | None | A clear-to-send frame; the relevant data is communicated in the header | Clause 7.1.2.3.2.5 | +| CTMG | √ | None | A frame carrying a short control message | Clause 7.1.2.3.2.6 | +| PROBE | √ | √ | A frame carrying probe symbols in its payload | Clause 7.1.2.3.2.7, clause 7.1.3.6 | +| ACKRQ | √ | None | An ACK retransmission request frame; the relevant data is communicated in the header | Clause 7.1.2.3.2.8 | +| BMSG | √ | √ | A bidirectional MSG frame | Clause 7.1.2.3.2.9, clause 8.3.7 of [ ITU-T G.9961 ] | +| BACK | √ | √ | A bidirectional ACK frame | Clause 7.1.2.3.2.10, clause 8.3.7 of [ ITU-T G.9961 ] | +| ACTMG | √ | None | An acknowledgment frame for a CTMG frame | Clause 7.1.2.3.2.11 | +| FTE | √ | Note | Frame type extension | Clause 7.1.2.3.2.16 | + +NOTE – Whether a payload is present or not depends on the definition of the extended frame type. + +#### 7.1.2.2 MPDU mapping + +MPDUs are passed to the PHY as an ordered sequence of bytes that are processed as an ordered string of bits from LSB to MSB within each byte. The first bit of the MPDU shall be the first transmitted bit of the payload. + +#### 7.1.2.3 PHY-frame header + +The core part of the PHY-frame header is PHYH bits long (see clause 7.1.3.2.2). It is transmitted over *D* (see clause 7.1.3.5.2) consecutive OFDM symbols, where *D* may be either 1 or 2. The core part of the PHY-frame header is composed of a common part and a variable part. The common part contains fields that are common for all PHY-frame types. The variable part contains fields according to the PHY-frame type. The PHY-frame type is indicated by the FT field. The PAD fields fit the length of the header of different PHY frame-types to the standard value of PHYH bits. The content of the core part is protected by the 16-bit header check sequence (HCS). + +The fields of the core part of the PHY-frame header are defined in Table 7-2. + +**Table 7-2 – Core part of the PHY-frame header** + +| Field | Octet | Bits | Description | Reference | +|----------|-----------|---------|----------------------------------------------------------------------------------------|--------------------| +| | | | | Common part | +| FT | 0 | [3:0] | Frame type | Clause 7.1.2.3.1.1 | +| DOD | | [7:4] | Domain ID | Clause 7.1.2.3.1.2 | +| SID | 1 | [7:0] | DEVICE_ID of the source node | Clause 7.1.2.3.1.3 | +| DID | 2 | [7:0] | DEVICE_ID, MULTICAST_ID or BROADCAST_ID of the destination node(s) | Clause 7.1.2.3.1.4 | +| MI | 3 | [0] | Multicast indication identifying whether the DID is a unicast or multicast destination | Clause 7.1.2.3.1.5 | +| DRI | | [1] | Duration indication identifying whether FTSF starts with a 16-bit duration field | Clause 7.1.2.3.1.6 | +| EHI | | [2] | Extended header indication | Clause 7.1.2.3.1.7 | +| HSI | | [3] | Header segmentation indication | Clause 7.1.2.3.1.8 | +| Reserved | | [7:4] | Reserved by ITU-T (Note) | | +| | | | | Variable part | +| FTSF | 4 to 18 | [119:0] | Frame-type specific field | Clause 7.1.2.3.2 | +| | | | | Common part | +| HCS | 19 and 20 | [15:0] | Header check sequence | Clause 7.1.2.3.1.9 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +Depending on the value of the extended header indication (EHI) field in the core part of the PHY-frame header, the PHY-frame header may be extended by additional PHYH bits that are transmitted over an additional *D* consecutive OFDM symbols. If the EHI bit is set to one, additional PHYH bits representing the extended part of the PHY-frame header are appended to the end of the core part of the PHY-frame header. The extended part of the PHY-frame header shall be encoded and segmented exactly the same way as the core part, as described in clauses 7.1.3.4 and 7.1.3.5.2. The content of the extended part is protected by the 16-bit extended header check sequence (E\_HCS). + +The core part and the extended part of the PHY-frame header shall be transmitted over separate OFDM symbols, as illustrated in Figure 7-4. + +(1) PHY-frame header core part transmitted over one OFDM symbol, i.e., HSI = 0 (D = 1), EHI = 0 + +![Diagram (1) shows a PHY frame structure with three parts: Preamble (blue), Header core part (yellow), and Payload (white).](7f5df81190b8dc50dad2604562ae0715_img.jpg) + +Diagram (1) shows a PHY frame structure with three parts: Preamble (blue), Header core part (yellow), and Payload (white). + +(2) PHY-frame header core part transmitted over two OFDM symbols, i.e., HSI = 1 (D = 2), EHI = 0 + +![Diagram (2) shows a PHY frame structure with four parts: Preamble (blue), Header core part (yellow), a second Header core part (yellow with diagonal lines), and Payload (white).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Diagram (2) shows a PHY frame structure with four parts: Preamble (blue), Header core part (yellow), a second Header core part (yellow with diagonal lines), and Payload (white). + +(3) PHY-frame header core and extended parts, each transmitted over one OFDM symbol, i.e., HSI = 0 (D = 1), EHI = 1 + +![Diagram (3) shows a PHY frame structure with four parts: Preamble (blue), Header core part (yellow), Header extended part (orange), and Payload (white).](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +Diagram (3) shows a PHY frame structure with four parts: Preamble (blue), Header core part (yellow), Header extended part (orange), and Payload (white). + +(4) PHY-frame header core and extended parts, each transmitted over two OFDM symbols, i.e., HSI = 1 (D = 2), EHI = 1 + +![Diagram (4) shows a PHY frame structure with six parts: Preamble (blue), Header core part (yellow), a second Header core part (yellow with diagonal lines), Header extended part (orange), a second Header extended part (orange with diagonal lines), and Payload (white).](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +Diagram (4) shows a PHY frame structure with six parts: Preamble (blue), Header core part (yellow), a second Header core part (yellow with diagonal lines), Header extended part (orange), a second Header extended part (orange with diagonal lines), and Payload (white). + +G.9960(10)\_F7-4 + +**Figure 7-4 – Allowed cases of PHY-frame header transmissions** + +##### 7.1.2.3.1 Common part fields + +###### 7.1.2.3.1.1 Frame type (FT) + +The Frame type (FT) field is a 4-bit field that indicates the type of PHY frame. + +Table 7-3 describes the PHY-frame types. + +**Table 7-3 – PHY-frame types** + +| Type | Value (b 3 b 2 b 1 b 0 ) | Description | Reference | +|----------|----------------------------------------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------| +| MAP/RMAP | 0000 | MAP/RMAP frame | Clause 7.1.2.3.2.1 | +| MSG | 0001 | Data and management frame | Clause 7.1.2.3.2.2 | +| ACK | 0010 | ACK control frame | Clause 7.1.2.3.2.3 | +| RTS | 0011 | RTS control frame | Clause 7.1.2.3.2.4 | +| CTS | 0100 | CTS control frame | Clause 7.1.2.3.2.5 | +| CTMG | 0101 | Short control frame | Clause 7.1.2.3.2.6 | +| PROBE | 0110 | PROBE frame | Clause 7.1.2.3.2.7 | +| ACKRQ | 0111 | ACK retransmission request frame | Clause 7.1.2.3.2.8 | +| BMSG | 1000 | Bidirectional MSG frame; contains data and management frames in the payload and ACK | Clause 7.1.2.3.2.9 | +| BACK | 1001 | Bidirectional ACK frame; contains ACK and data and management frames in the payload | Clause 7.1.2.3.2.10 | +| ACTMG | 1010 | Acknowledgment for CTMG frame | Clause 7.1.2.3.2.11 | +| Reserved | 1011 and 1100 | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | 1101 to 1110 | Reserved by ITU-T | Clause 7.1.2.3.2.12 and clause 7.1.2.3.2.13 | + +**Table 7-3 – PHY-frame types** + +| Type | Value
(b 3 b 2 b 1 b 0 ) | Description | Reference | +|------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------|---------------------| +| FTE | 1111 | Frame type extension;
This frame type is a pointer to a set of additional frame types | Clause 7.1.2.3.2.16 | + +###### **7.1.2.3.1.2 Domain ID (DOD)** + +The DOD field shall contain the domain ID to which the source and destination devices of the PHY frame belong. It shall be represented as a 4-bit unsigned integer with valid values in the range from 0 to 15. Value 0 is a special value reserved for inter-domain communication (see clause 8.14.6.1.2 in [[ITU-T G.9961](#)]). + +###### **7.1.2.3.1.3 Source ID (SID)** + +The SID field shall contain the DEVICE\_ID assigned to the source node of the PHY frame during its registration. It shall be represented as an 8-bit unsigned integer with valid values in the range from 0 to 251. Value 0 is a special value that shall be used by a node attempting to join the domain. Value 251 is a special value reserved for inter-domain communication (see clause 8.14.6.1 in [[ITU-TG.9961](#)]). + +###### **7.1.2.3.1.4 Destination ID (DID)** + +The DID field shall contain the value that identifies the destination node(s) of the PHY frame. It shall be represented as an 8-bit unsigned integer with valid values in the range from 0 to 250. + +###### **7.1.2.3.1.5 Multicast indication (MI)** + +If the multicast indication (MI) bit is set to zero, the DID field shall contain the DEVICE\_ID of the destination node (for unicast transmission). If the MI bit is set to one, the DID field shall contain a MULTICAST\_ID or BROADCAST\_ID of the destination nodes. + +###### **7.1.2.3.1.6 Duration indication (DRI)** + +If the DRI bit is set to one, the FTSF shall start with a duration field. If this bit is set to zero, the PHY frame shall not contain any payload (i.e., contains only preamble and PHY-frame header). + +The duration field contains the duration of a single PHY frame or PHY frame sequence. It shall be represented as a 16-bit unsigned integer with valid values in steps of 0.25 µs. It shall be the smallest integer larger than or equal to the actual duration. The duration field is defined separately depending on the frame type. If a node detects a PHY frame with unknown frame type, the node shall assume for its virtual carrier sense that the channel will be occupied for that duration. After that time there shall be an inter-frame gap equal to $T_{IFG\_MIN}$ . + +**Table 7-4 – Value of DRI for different frame types** + +| Frame type | Value of DRI | +|------------|--------------| +| MAP/RMAP | one | +| MSG | one | +| ACK | zero | +| RTS | one | +| CTS | one | +| PROBE | one | + +**Table 7-4 – Value of DRI for different frame types** + +| Frame type | Value of DRI | +|------------|--------------| +| ACKRQ | zero | +| BMSG | one | +| BACK | one | +| CTMG | zero | +| ACTMG | zero | +| FTE | zero or one | + +###### 7.1.2.3.1.7 Extended header indication (EHI) + +If the EHI field is set to one, the PHY frame header shall contain $2 \times \text{PHY}_H$ information bits. The additional $\text{PHY}_H$ information bits of the extended part of the PHY-frame header are specified in clause 7.1.2.3.3. If the EHI field is set to zero, the PHY-frame header shall contain $\text{PHY}_H$ information bits. The EHI field shall be set according to the frame type as shown in Table 7-5. + +**Table 7-5 – Value of EHI for different frame types** + +| Frame type | Value of EHI | +|------------|--------------| +| MAP/RMAP | zero | +| MSG | zero | +| ACK | zero or one | +| RTS | zero | +| CTS | zero | +| PROBE | zero | +| ACKRQ | zero | +| BMSG | zero or one | +| BACK | zero or one | +| CTMG | zero or one | +| FTE | zero or one | +| ACTMG | zero | + +###### 7.1.2.3.1.8 Header segmentation indication (HSI) + +The HSI field shall be set to the same value as the header segmentation field in the TXOP descriptor extension in the MAP (see Table 8-65 in [[ITU-T G.9961](#)]). + +###### 7.1.2.3.1.9 Header check sequence (HCS) + +The HCS field is intended for PHY-frame header verification. It is a 16-bit cyclic redundancy check (CRC) and shall be computed over all the fields of the PHY-frame header in the order they are transmitted, starting with the LSB of the first field of the PHY frame header (FT) and ending with the MSB of the last field of the FTSF. + +The HCS shall be computed using the following generator polynomial of degree 16: + +$$G(x) = x^{16} + x^{12} + x^5 + 1$$ + +The value of the HCS shall be the remainder after the contents (treated as a polynomial where the first input bit is associated with the highest degree, $X^{\text{PHY}_H-17}$ , where $\text{PHY}_H$ is the header length in bits, + +and the last input bit is associated with $X^0$ ) of the calculation field is multiplied by $x^{16}$ and then divided by $G(x)$ . + +The HCS field shall be transmitted starting with the coefficient of the highest order term. + +##### 7.1.2.3.2 Variable part fields + +This clause details the frame-type specific field (FTSF), a variable part of the PHY-frame header fields separately defined for each PHY-frame type. + +###### 7.1.2.3.2.1 MAP and RMAP PHY-frame type specific fields + +Table 7-6 lists the PHY-frame header fields which are specific to the MAP and RMAP frame type. + +**Table 7-6 – MAP and RMAP PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|------------------|-----------|---------|--------------------------------------------------|-----------------------| +| MAP_DUR | 0 and 1 | [15:0] | Duration for MAP frame | Clause 7.1.2.3.2.1.1 | +| NTR | 2 to 5 | [31:0] | Network time reference | Clause 7.1.2.3.2.1.2 | +| CYCSTART | 6 to 9 | [31:0] | MAC cycle start time | Clause 7.1.2.3.2.1.3 | +| RCMSS | 10 and 11 | [11:0] | RCM section size | Clause 7.1.2.3.2.1.4 | +| SI | | [15:12] | Scrambler initialization | Clause 7.1.2.3.2.1.5 | +| BLKSZ | 12 | [1:0] | Block size of FEC codeword for MAP frame payload | Clause 7.1.2.3.2.1.6 | +| REP | | [4:2] | Number of repetitions for encoding payload | Clause 7.1.2.3.2.1.7 | +| FCF | | [7:5] | FEC concatenation factor | Clause 7.1.2.3.2.1.8 | +| OFB_ID | 13 | [2:0] | OFB_ID | Clause 7.1.2.3.2.1.9 | +| MAP_TYPE | | [3] | MAP type | Clause 7.1.2.3.2.1.10 | +| RMAP_I | | [4] | RMAP indication | Clause 7.1.2.3.2.1.11 | +| APSD_MAX-MAP_LSB | | [7:5] | The LSB part of the APSD_MAX-MAP of a MAP frame | Clause 7.1.2.3.2.17 | +| NUM_HOPS | 14 | [3:0] | Number of hops from domain master | Clause 7.1.2.3.2.1.12 | +| APSD_MAX-MAP_MSB | | [5:4] | The MSB part of the APSD_MAX-MAP of a MAP frame | Clause 7.1.2.3.2.17 | +| APSD_MAX-MAP_EXT | | [6] | APSD_MAX-MAP extension | Clause 7.1.2.3.2.1.13 | +| Reserved | | [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.1.2.3.2.1.1 Duration for MAP frame (MAP\_DUR) + +The MAP\_DUR field shall contain the transmission time of the MAP frame. + +###### 7.1.2.3.2.1.2 Network time reference (NTR) + +The NTR field shall contain the time of the first sample of the first OFDM symbol (see Figure 7-24) of the preamble of a MAP or RMAP frame that is sent according to the domain master's transmit clock with a resolution of 10 ns. It is used for synchronizing nodes to the domain master transmit + +clock. It shall be represented as a 32-bit unsigned integer. The NTR value shall use modulo $2^{32}$ arithmetic. + +If a node other than the domain master transmits the frame, it shall use the best estimate of the domain master's NTR (see clause 7.1.6.2). + +###### 7.1.2.3.2.1.3 MAC cycle start time (CYCSTART) + +The CYCSTART field shall contain the start time of the next MAC cycle. It shall be represented as a 32-bit unsigned integer. It shall be based on the domain master's transmit clock with a resolution of 10 ns. The value of CYCSTART in a MAC cycle shall be equal to the value of CYCSTART in the previous MAC cycle plus the MAC cycle duration, indicated in the MAP header (see clause 8.8.3 of [[ITU-T G.9961](#)]). + +All MAP/RMAP frames transmitted during the MAC cycle ( $n$ ) shall contain the same CYCSTART value that defines the starting point of the MAC cycle ( $n + 1$ ). + +The CYCSTART value shall use modulo $2^{32}$ arithmetic. + +###### 7.1.2.3.2.1.4 RCM section size (RCMSS) + +The RCMSS field shall contain the size of the repetition block, B, used in the MAP frame (see clause 7.1.3.3.1). It shall be represented as a 12-bit unsigned integer with valid values in the range from 14 to 4094. + +###### 7.1.2.3.2.1.5 Scrambler initialization (SI) + +The SI field shall contain the value that was used by the domain master to initialize the scrambler for this frame. It is a 4-bit field $C_4C_3C_2C_1$ as described in clause 7.1.3.1. + +###### 7.1.2.3.2.1.6 Block size (BLKSZ) + +The BLKSZ field shall contain the information block size of the FEC codeword that is used for the payload of the MAP frame. It is a 2-bit field that shall be coded as shown in Table 7-7. + +**Table 7-7 – Interpretation of the BLKSZ field** + +| BLKSZ value
( $b_1b_0$ ) | Interpretation | +|-----------------------------|----------------------------------------------------------| +| 00 | For the 120-byte information block size used for payload | +| 01 | For the 540-byte information block size used for payload | +| 10 and 11 | Reserved by ITU-T | + +###### 7.1.2.3.2.1.7 Repetitions (REP) + +The REP field shall contain the number of repetitions that were used for encoding the payload in the MAP frame. It is a 3-bit field that shall be coded as shown in Table 7-8. + +**Table 7-8 – Repetitions field allowed values** + +| REP value
( $b_7b_6b_5$ ) | Interpretation
( $N_{REP}$ ) | +|------------------------------|---------------------------------| +| 000 | Reserved by ITU-T | +| 001 | 1 (no repetitions) | +| 010 | 2 | +| 011 | 3 | +| 100 | 4 | + +**Table 7-8 – Repetitions field allowed values** + +| REP value
(b 7 b 6 b 5 ) | Interpretation
( NREP ) | +|--------------------------------------------------------------|----------------------------------------------| +| 101 | 6 | +| 110 | 8 | +| 111 | Reserved by ITU-T | + +###### **7.1.2.3.2.1.8 FEC concatenation factor (FCF)** + +The FCF field shall contain the FEC concatenation factor. It is a 3-bit field that shall be coded as shown in Table 7-9. + +**Table 7-9 – FEC concatenation factor (FCF) allowed values** + +| FCF value
(b 2 b 1 b 0 ) | H | z | +|--------------------------------------------------------------|-------------------|-------------------| +| 000 | 1 | 0 | +| 001 | Reserved by ITU-T | Reserved by ITU-T | +| 010 | 2 | 0 | +| 011 | 2 | 1 | +| 100 | 4 | 0 | +| 101 | 4 | 1 | +| 110 | 4 | 2 | +| 111 | 4 | 3 | + +###### **7.1.2.3.2.1.9 Operational frequency band (OFB\_ID)** + +The OFB\_ID field shall contain the identifier for the bandplan used by the node. It is a 3-bit field that shall be coded as shown in Table 7-10. + +**Table 7-10 – OFB identifier** + +| OFB_ID value
(b 7 b 6 b 5 ) | Description | +|-----------------------------------------------------------------|-------------------| +| 000 | Reserved by ITU-T | +| 001 | 25 MHz | +| 010 | 50 MHz | +| 011 | 100 MHz | +| 100 | 200 MHz | +| 101 to 111 | Reserved by ITU-T | + +###### **7.1.2.3.2.1.10 MAP type (MAP\_TYPE)** + +If the MAP\_TYPE bit is set to zero, the default MAP (MAP-D) or default RMAP (RMAP-D) frame shall be used for transmission using predefined BAT Type 1 for the MAP/RMAP frame payload. If the MAP\_TYPE bit is set to one, the active MAP (MAP-A) or active RMAP (RMAP-A) frame shall be used for transmission using predefined BAT Type 2 for the MAP/RMAP frame payload. + +MAP-D and RMAP-D frames shall only use an FEC block size of 120 bytes. + +NOTE – For reasons of efficiency and robustness, MAP-A and RMAP-A frames should use an FEC block size of 120 bytes. + +For all MAP types, the MAP/RMAP frame shall use the default guard interval ( $N_{\text{GI-DF}}$ ), rate $\frac{1}{2}$ FEC coding, and the payload repetition scheme as specified in clause 7.1.3.3.1. + +###### 7.1.2.3.2.1.11 RMAP indication (RMAPI) + +If the RMAPI bit is set to zero, the MAP frame shall be used for transmission. If the RMAPI bit is set to one, the RMAP frame shall be used for transmission. + +###### 7.1.2.3.2.1.12 Number of hops from domain master (NUM\_HOPS) + +The NUM\_HOPS field shall contain the number of hops that the node sending this RMAP frame is from the domain master. A value of 0 shall indicate that the node receives PHY frames from the domain master directly; a value of 1 shall indicate that the node is two hops from the domain master; and so on. + +###### 7.1.2.3.2.1.13 APSD\_MAX-MAP\_EXT + +See clause 7.1.2.3.2.17. + +###### 7.1.2.3.2.2 MSG PHY-frame type specific fields + +Table 7-11 lists the PHY-frame header fields which are specific to the MSG frame type. + +**Table 7-11 – MSG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|---------------|---------|--------|---------------------------------------------------------------|----------------------------------| +| MSG_DUR | 0 and 1 | [15:0] | Duration for MSG frame | Clause 7.1.2.3.2.2.1 | +| BLKSZ | 2 | [1:0] | Block size of FEC codeword for MSG frame payload | Clause 7.1.2.3.2.2.2 | +| FEC_RATE | | [4:2] | FEC coding rate for MSG frame payload | Clause 7.1.2.3.2.2.3 | +| REP | | [7:5] | Number of repetitions used for encoding the MSG frame payload | Clause 7.1.2.3.2.2.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 7.1.2.3.2.2.5 | +| SI | | [6:3] | Scrambler initialization | Clause 7.1.2.3.2.2.6 | +| MDET | | [7] | Master is detected | Clause 7.1.2.3.2.2.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 7.1.2.3.2.2.8 | +| OFB_ID/GRP_ID | | [7:5] | OFB identifier/subcarrier grouping identifier | Clause 7.1.2.3.2.2.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 7.1.2.3.2.2.10 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of an MSG frame | Clause 7.1.2.3.2.2.11 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 7.1.2.3.2.2.12 | +| RPRQ | 7 | [1:0] | Reply required | Clause 7.1.2.3.2.2.13 | +| BRSTCnt | | [3:2] | Burst frame count | Clause 7.1.2.3.2.2.14 | +| BEF | | [4] | Burst end flag | Clause 7.1.2.3.2.2.15 | +| AIFG_IND | | [5] | AIFG indication | Clause 7.1.2.3.2.2.16 | +| Reserved | | [6] | Reserved | Reserved for use by ITU-T G.9963 | + +**Table 7-11 – MSG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|------------------|----------|--------|-------------------------------------------------------------------------|----------------------------------| +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 7.1.2.3.2.2.25 | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 7.1.2.3.2.2.17 | +| CNN_MNGMT | | [6:3] | Connection management | Clause 7.1.2.3.2.2.18 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note 1) | +| BRURQ | 9 and 10 | [15:0] | Bandwidth reservation update request | Clause 7.1.2.3.2.2.19 (Note 2) | +| START_SSN | 9 and 10 | [15:0] | Start segment sequence number | Clause 7.1.2.3.2.2.20 (Note 3) | +| CURRTS | 11 | [6:0] | Current TS | Clause 7.1.2.3.2.2.21 | +| BTXRQ | | [7] | Request for bidirectional transmission | Clause 7.1.2.3.2.2.22 | +| NUM_MCACK_SLOTS | 12 | [2:0] | Number of Mc-ACK slots | Clause 7.1.2.3.2.2.23 | +| ADVISED_WIN_SIZE | | [7:3] | In connection establishment this field may specify advised window size. | Clause 7.1.2.3.2.2.24 (Note 4) | +| Reserved | 13 | [0] | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | | [7:1] | Reserved | Reserved by ITU-T (Note 1) | +| Reserved | 14 | [7:0] | Reserved | Reserved by ITU-T (Note 1) | + +NOTE 1 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +NOTE 2 – The BRURQ field is defined when the START\_SSN field is not defined (see Note 3). + +NOTE 3 – The START\_SSN field is defined only when CNN\_MNGMT = 0001, CNN\_MNGMT = 0011, CNN\_MNGMT = 0101 or CNN\_MNGMT = 0111. Otherwise, the meaning of this field is BRURQ. + +NOTE 4 – The ADVISED\_WIN\_SIZE field is defined only when CNN\_MNGMT = 0101, otherwise these bits are reserved by ITU-T and shall be set to zero by the transmitter and ignored by the receiver. + +###### 7.1.2.3.2.2.1 Duration for MSG frame (MSG\_DUR) + +For an MSG frame where Imm-ACK or one or more Mc-ACKs do not follow the MSG frame, the duration field shall contain the transmission time of the MSG frame. + +For an MSG frame where Imm-ACK or one or more Mc-ACKs follow the MSG frame, the duration field shall contain the transmission time of the MSG frame plus the duration of the following AIFG. The MSG\_DUR field shall not exceed TMAX\_MSG\_DURATION. + +###### 7.1.2.3.2.2.2 Block size (BLKSZ) + +The BLKSZ field shall contain the information block size of the FEC codeword that is used for the payload of the MSG frame. It is a 2-bit field that shall be coded as shown in Table 7-7. + +###### 7.1.2.3.2.2.3 FEC coding rate (FEC\_RATE) + +The FEC\_RATE field shall contain the FEC coding rate that is used for encoding of the payload of the MSG frame. It is a 3-bit unsigned integer field that shall be coded as shown in Table 7-12. + +**Table 7-12 – Interpretation of the FEC\_RATE field** + +| FEC_RATE value
(b 4 b 3 b 2 ) | Interpretation | +|-------------------------------------------------------------------|-------------------| +| 000 | Reserved by ITU-T | +| 001 | 1/2 | +| 010 | 2/3 | +| 011 | 5/6 | +| 100 | 16/18 | +| 101 | 20/21 | +| 110 and 111 | Reserved by ITU-T | + +###### **7.1.2.3.2.2.4 Repetitions (REP)** + +The REP field shall contain the nominal number of repetitions that were used for encoding the payload in the MSG frame. It is a 3-bit field that shall be coded as shown in Table 7-8. + +###### **7.1.2.3.2.2.5 FEC concatenation factor (FCF)** + +The FCF field shall contain the values of parameters *H* and *z* (see clause 7.1.3.3.1). It is a 3-bit field that shall be coded as shown in Table 7-9. + +###### **7.1.2.3.2.2.6 Scrambler initialization (SI)** + +The SI field shall contain the value that was used to initialize the scrambler for this frame. It is a 4-bit field C4C3C2C1 as described in clause 7.1.3.1. + +###### **7.1.2.3.2.2.7 Master is detected indication (MDET)** + +The MDET bit shall indicate reception of a MAP. It is a 1-bit field that shall be set to one by a node, in each PHY-frame header that it transmits, when this node has received a MAP (either directly from the domain master or a repeated MAP) that the current MAC cycle is associated with. This indication shall be used by nodes (including the backup domain master if it exists) to determine whether the current domain master has failed. + +###### **7.1.2.3.2.2.8 Bit allocation table identifier (BAT\_ID)** + +The BAT\_ID field shall identify the bit allocation table (BAT) of the PHY frame. It shall be represented as a 5-bit unsigned integer with valid values as shown in Table 7-57. + +###### **7.1.2.3.2.2.9 OFB identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +For predefined BATs with uniform loading (type 0, type 1, type 2 and Type 3), the OFB\_ID/GRP\_ID field shall contain the identifier for the operational frequency band used by the node and shall be coded as shown in Table 7-10. Otherwise, it shall contain the subcarrier grouping (see clause 7.1.4.2.4) and shall be coded as shown in Table 7-13. + +**Table 7-13 – Format of the GRP\_ID field** + +| GRP_ID value
(b 7 b 6 b 5 ) | Description | +|-----------------------------------------------------------------|---------------------------------------| +| 000 | Default – No subcarrier grouping | +| 001 | Subcarrier grouping of 2 subcarriers | +| 010 | Subcarrier grouping of 4 subcarriers | +| 011 | Subcarrier grouping of 8 subcarriers | +| 100 | Subcarrier grouping of 16 subcarriers | +| 101 to 111 | Reserved by ITU-T | + +###### 7.1.2.3.2.2.10 Guard interval identifier (GI\_ID) + +The GI\_ID field shall identify the guard interval used for payload (see clause 7.1.4.4). It is a 3-bit field that shall be coded as shown in Table 7-14. + +**Table 7-14 – Format of the GI\_ID field** + +| GI_ID value
(b 2 b 1 b 0 ) | Description | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| 000 to 110 | $N_{GI}$ guard interval (samples) $k \times N/32$ , $k = 1, 2, 3, \dots, 7$
where
$k = \text{GI\_ID}+1$ ,
$N$ is the size of the DFT | +| 111 | $k = 8$ ( $\text{GI\_ID}=7$ )
$N_{GI} = N_{GI-DF} = N/4$ | + +###### 7.1.2.3.2.2.11 Maximum actual PSD of MSG frame (APSD\_MAX-M) + +The APSD\_MAX-M and APSD\_MAX-M\_EXT fields shall together indicate the APSD\_MAX for the PHY frame. It shall be represented as a 6-bit unsigned integer with valid values in the range from 0 to 50, plus 62 and 63. Values from 0 to 50 correspond to an APSD\_MAX in the range of –50 dBm/Hz to –100 dBm/Hz in 1 dB steps. + +The most significant 5 bits of the APSD\_MAX are conveyed in the APSD\_MAX-M field and the least significant bit of the APSD\_MAX is conveyed in the APSD\_MAX-M\_EXT field. + +The special values 62 and 63 shall indicate that the frame has been transmitted with an APSD\_MAX that is the minimum of: + +- Highest value of the transmit PSD allowed (i.e., TxPSD after applying PSD ceiling if applicable) +- Highest value of the PSD that the node is capable of transmitting. + +All other values are reserved by ITU-T. + +###### 7.1.2.3.2.2.12 Connection identifier (CONNECTION\_ID) + +The CONNECTION\_ID field shall identify the connection that the LPDUs contained in the PHY-frame belong to. It shall be represented as an 8-bit unsigned integer. If a PHY-frame contains only management LPDUs (i.e., LPDUs from a unicast management connection or a broadcast management connection) and no data LPDUs, this field shall be set to 251 in that PHY-frame. + +For connections associated with service flows, this field shall be set to the FLOW\_ID. For prioritized data connections, it shall be set to the recommended flow priority given by Table III.1, denoted as PRI-Q, which depends on the user priority and the number of priority queues (traffic classes) supported from the source node to the destination node. The value shall be set to 255 for broadcast data connections and to 252 for multicast connections. In the case that the CNN\_MNGMT field is set to 1111, CONNECTION\_ID shall be set to 255. + +The values 253 and 254 are reserved by ITU-T. + +###### 7.1.2.3.2.2.13 Reply required (RPRQ) + +The RPRQ field shall be used to instruct the receiver whether or not to respond with an acknowledgement for this PHY frame. It is a 2-bit field that shall be coded as shown in Table 7-15. + +**Table 7-15 – RPRQ field allowed values** + +| RPRQ value
(b 1 b 0 ) | Interpretation | +|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | The receiver shall not acknowledge this PHY frame. The PHY frame does not require acknowledgement. | +| 01 | When MI is set to zero (unicast), the receiver shall acknowledge via an Imm-ACK frame.
When MI is set to one (multicast), a slotted acknowledgement using multicast binding mechanism for slot assignment (see clause 8.9.2 of [ ITU-T G.9961 ]) shall follow the transmission of this multicast MSG PHY frame. NACK signalling shall not be used. This mode shall only be used if each receiving node in the multicast group is assigned a Mc-ACK slot. | +| 10 | When MI is set to zero (unicast), the receiver shall defer the acknowledgement of the frame (see clause 8.9.1.2 of [ ITU-T G.9961 ]).
When MI is set to one (multicast), this value is reserved by ITU-T. | +| 11 | When MI is set to zero (unicast), this value is reserved by ITU-T.
When MI is set to one (multicast), a slotted acknowledgement using multicast binding mechanism for slot assignment (see clause 8.9.2 of [ ITU-T G.9961 ]) shall follow the transmission of this multicast MSG PHY frame. All receivers in the multicast group not assigned an acknowledgement slot that fail to receive the transmission by criteria described in clause 8.9.2.1 of [ ITU-T G.9961 ] shall transmit a NACK in the NACK signalling slot. | + +###### 7.1.2.3.2.2.14 Burst frame count (BRSTCnt) + +The BRSTCnt field shall contain the sequence number of the PHY frame within a PHY frame burst, generated as described in clause 8.3.5 of [[ITU-T G.9961](#)]. It shall be represented as a 2-bit unsigned integer. + +The BRSTCnt field shall be set to zero in the first PHY frame of the burst and shall be incremented by one upon each additional PHY frame of the same burst. + +###### 7.1.2.3.2.2.15 Burst end flag (BEF) + +The BEF field shall indicate the end of a burst. It is a 1-bit field. The BEF shall be set to one in the last PHY frame of the burst and shall be set to zero in all other PHY frames. For bursts containing one frame (no bursting used) the BEF field shall be set to one. + +###### 7.1.2.3.2.2.16 AIFG indication (AIFG\_IND) + +For unicast, if the AIFG\_IND field is set to one, the "receiver-specific" AIFG value, $T_{\text{AIFG}}$ , shall be used by the transmitter. If the AIFG\_IND field is set to zero, the default AIFG, $T_{\text{AIFG-D}}$ shall be used. The receiver shall ACK this frame, whenever Imm-ACK is used, after either $T_{\text{AIFG}}$ or $T_{\text{AIFG-D}}$ , as indicated by AIFG\_IND. + +For multicast, the AIFG\_IND field shall always be set to zero. + +###### 7.1.2.3.2.2.17 ACE symbols (ACE\_SYM) + +The ACE\_SYM field shall contain the number of ACE symbols inserted between the header and payload of the MSG frame. It is a 3-bit field that shall be coded as shown in Table 7-16. + +**Table 7-16 – ACE\_SYM field values** + +| ACE_SYM value (b 2 b 1 b 0 ) | Interpretation | +|---------------------------------------------------------------|----------------| +| 000 | 0 ACE symbols | +| 001 | 1 ACE symbols | +| 010 | 2 ACE symbols | +| .... | .... | +| 111 | 7 ACE symbols | + +###### **7.1.2.3.2.2.18 Connection management (CNN\_MNGMT)** + +The CNN\_MNGMT field shall be used for the management of connections as defined in clause 8.12 of [[ITU-T G.9961](#)]. It is a 4-bit field that shall be coded as shown in Table 7-17. + +**Table 7-17 – CNN\_MNGMT field values** + +| CNN_MNGMT value (b 7 b 6 b 5 b 4 ) | Interpretation | +|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| 0000 | No action (may contain payload) | +| 0001 | Request to establish a management connection with acknowledgements (no payload allowed) | +| 0010 | Request to establish a management connection without acknowledgements (no payload allowed) | +| 0011 | Indication of reset of the management connection (no payload allowed) | +| 0100 | Indication of release of the management connection (no payload allowed) | +| 0101 | Request to establish a data connection with acknowledgements (no payload allowed) | +| 0110 | Request to establish a data connection without acknowledgements (no payload allowed) | +| 0111 | Indication of reset of the data connection (no payload allowed) | +| 1000 | Indication of release of a data connection (no payload allowed) | +| 1001 to 1110 | Reserved for ITU-T | +| 1111 | Payload does not belong to any connection | + +When this field is equal to 0001 or 0011, the value of the ACK\_TX\_RESET variable (see clause 8.9.4.2 of [[ITU-T G.9961](#)]) of the state machine of the management connection is one. ACK\_TX\_RESET is zero when this field is 0000. + +When this field is equal to 0101 or 0111, the value of the ACK\_TX\_RESET variable (see clause 8.9.4.2 of [[ITU-T G.9961](#)]) of the state machine of the data connection indicated by the CONNECTION\_ID field of this MSG is one. ACK\_TX\_RESET is zero when this field is 0000. + +###### **7.1.2.3.2.2.19 Bandwidth reservation update request (BRURQ)** + +The BRURQ field shall contain updates in the bandwidth reserved for this node connection. It is a 16-bit field that shall be coded as shown in Table 7-18. The domain master shall follow the BRURQ fields of all nodes (see clause 8.6.2.2 of [[ITU-T G.9961](#)]). + +**Table 7-18 – Format of the BRURQ field** + +| Field | Octet | Bits | Description | +|--------------|-------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ConnState | 0 | [7:0] | Contains the number of accumulated bytes in the connection queue. This value is specified in units of Kbytes, expressed as ceiling (number of bytes/1024). | +| FlowLineRate | 1 | [7:0] | Indicates the current PHY data rate in bytes/symbol. The range of valid values and the corresponding valid increments (see Table 7-19) depend on the medium. This value is expressed as floor (number of transmitted bytes per symbol/increment) (Note). | + +NOTE – Bytes/symbol value shall be calculated by applying the same formula and rules as Note 1 of Table 8-48 of [ITU-T G.9961](#) and multiplying the result by the symbol period ( $T_{\text{OFDM}}$ as defined in clause 7.1.4.4.4) and dividing by 8. DM shall consider this figure as an indication of the average throughput taking into account the different tone maps used in the MAC cycle. + +**Table 7-19 – Valid increments for BRURQ field** + +| Type | Increment | +|----------------|-----------| +| Power line | 32 bytes | +| Telephone line | 16 bytes | +| Coax | 4 bytes | + +###### **7.1.2.3.2.2.20 Start segment sequence number (START\_SSN)** + +The START\_SSN field shall contain the value of the ACK\_TX\_WINDOW\_START variable of the transmitter at the establishment or reset of a connection. The receiver shall set its ACK\_RX\_WINDOW\_START variable to this value. + +The START\_SSN field is defined only when CNN\_MNGMT = 0001, CNN\_MNGMT = 0011, CNN\_MNGMT = 0101 or CNN\_MNGMT = 0111 indicating the establishment or reset of a connection. + +###### **7.1.2.3.2.2.21 Current TS (CURRTS)** + +The CURRTS field shall contain the ordinal number of the TS in an STXOP that this MSG PHY frame is sent in as described in the MAP (see clause 8.8.5 of [ITU-T G.9961](#)). It shall be represented as a 7-bit unsigned integer. + +A PHY frame that is sent in the first TS for a STXOP as described in the MAP shall have the number 1 in its CURRTS field; a PHY frame that is sent in the second TS of the STXOP shall have number 2 in its CURRTS field; and so on. The valid range of values for CURRTS field, for a specific STXOP, shall be from 1 to $M$ , where $M$ is the number of TSs in that STXOP, as described in the MAP (i.e., the number of TXOP descriptors). + +A value of 0 shall be used for transmission not within an STXOP. + +###### **7.1.2.3.2.2.22 Request for bidirectional transmission (BTXRQ)** + +The BTXRQ bit shall be used to request the destination node to initiate bidirectional transmission with the source node of this MSG frame. It shall be set to one for a request and set to zero for no request (see clause 8.3.7 of [ITU-T G.9961](#)). + +###### 7.1.2.3.2.2.23 Number of Mc-ACK slots (NUM\_MCACK\_SLOTS) + +The NUM\_MCACK\_SLOTS field shall contain the number of slotted Mc-ACKs when MI is set to one and the value of the RPRQ field is 012 or 112 (see Table 7-15). It shall be represented as a 3-bit unsigned integer. + +The meaning of the NUM\_MCACK\_SLOTS field for other values of RPRQ when MI is set to one is reserved by ITU-T. When MI is set to zero, the NUM\_MCACK\_SLOTS field shall be set to zero and ignored by the receiver. + +###### 7.1.2.3.2.2.24 Advised Window Size (ADVISED\_WIN\_SIZE) + +During the establishment of a data connection with acknowledgement, the transmitter may use the ADVISED\_WIN\_SIZE field to advise the receiver for the needed RX window size. The advised size of the RX window is given in number of LPDUs that is represented by the value in ADVISED\_WIN\_SIZE multiplied by 32 for the range of values from 0116 to 1E16. A special value of 1F16 means that the window size is 1024 LPDUs. A special value of 0016 means that the transmitter does not advise any value. + +###### 7.1.2.3.2.2.25 APSD\_MAX-M extension + +See clause 7.1.2.3.2.2.11. + +##### 7.1.2.3.2.3 ACK PHY-frame type specific fields + +Table 7-20 lists the PHY-frame header fields which are specific to the core part of the PHY-frame header of the ACK frame type. + +**Table 7-20 – ACK PHY frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------------------------------|---------|---------|----------------------------------------------------------------------------------|----------------------------------| +| FLCTRL_CONN | 0 | [0] | Flow control connection flag | Clause 7.1.2.3.2.3.1 | +| FLCTRLT | | [1] | Flow control type | Clause 7.1.2.3.2.3.2 | +| FLCTRL | | [6:2] | Flow control | Clause 7.1.2.3.2.3.3 | +| FLCTRL_EXT | | [7] | Flow control extension | Clause 7.1.2.3.2.3.11 | +| RXRST_DATA | 1 | [0] | Data RX reset flag | Clause 7.1.2.3.2.3.5 | +| RXRST_MNGMT | | [1] | Management RX reset flag | Clause 7.1.2.3.2.3.6 | +| BAD_BURST | | [2] | Bad burst indication | Clause 7.1.2.3.2.3.7 | +| BTXRQ | | [3] | Request for bidirectional transmission | Clause 7.1.2.3.2.3.4 | +| EXTACKRQ | | [4] | Request for extended acknowledgement | Clause 7.1.2.3.2.3.10 | +| Reserved | | [7:5] | Reserved | Reserved for use by ITU-T G.9991 | +| ACK_CE_CTRL/
RX_CONN_WIN_SIZE | 2 | [6:0] | ACK channel estimation control/Receiver window size for the connection. (Note 1) | Clause 7.1.2.3.2.3.8 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T G.9963 | +| ACKDATA/MCACK_D | 3 to 14 | [90:0] | Acknowledgement data and Mc-ACK descriptor | Clause 7.1.2.3.2.3.9 | +| Reserved | | [94:91] | Reserved | Reserved for use by ITU-T G.9991 | + +**Table 7-20 – ACK PHY frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|-------|------|-------------|----------------------------| +| Reserved | | [95] | Reserved | Reserved by ITU-T (Note 2) | + +NOTE 1 – This field is interpreted as RX\_CONN\_WIN\_SIZE only when the ACK frame is sent as a reply for MSG frame requesting set-up or reset of either a data or a management connection (i.e., when CNN\_MNGMT in the MSG frame is 01012, 00012, 00112 or 01112). + +NOTE 2 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +###### 7.1.2.3.2.3.1 Flow control connection flag (FLCTRL\_CONN) + +The FLCTRL\_CONN field defines the interpretation of the FLCTRL and FLCTRLT fields. When the FLCTRL\_CONN field is set to zero, fields FLCTRL and FLCTRLT shall carry information about a data connection. When the FLCTRL\_CONN field is set to one, fields FLCTRL and FLCTRLT shall carry information about the management connection. + +###### 7.1.2.3.2.3.2 Flow control type (FLCTRLT) + +The FLCTRLT field shall contain the interpretation of the FLCTRL field according to Table 7-21. + +**Table 7-21 – FLCTRLT field values** + +| FLCTRLT value (b 1 ) | Interpretation | +|---------------------------------|----------------------| +| 0 | Status report | +| 1 | Hold time/management | + +###### 7.1.2.3.2.3.3 Flow control (FLCTRL) + +The FLCTRL field shall be used for flow control between the transmitter and the receiver as described in clause 8.12.4 of [[ITU-T G.9961](#)]. Interpretation of the FLCTRL field depends on the setting of the FLCTRLT field. + +If the FLCTRLT field is set to zero (status report), the FLCTRL field shall contain the number of LPDUs that the receiver can buffer for this flow. It is a 5-bit field that shall be coded as shown in Table 7-22. + +**Table 7-22 – FLCTRL field values for status report** + +| FLCTRL value (b 6 b 5 b 4 b 3 b 2 ) | Connections with 540 byte LPDUs | Connections with 120 byte LPDUs | +|--------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| 00000 | 4 | 6 | +| 00001 | 8 | 12 | +| 00010 | 12 | 18 | +| 00011 | 16 | 24 | +| 00100 | 20 | 30 | +| 00101 | 24 | 36 | +| 00110 | 28 | 42 | +| 00111 | 32 | 48 | + +**Table 7-22 – FLCTRL field values for status report** + +| FLCTRL value
(b 6 b 5 b 4 b 3 b 2 ) | Connections with
540 byte LPDUs | Connections with
120 byte LPDUs | +|-----------------------------------------------------------------------------------------------|------------------------------------|------------------------------------| +| 01000 | 40 | 60 | +| 01001 | 48 | 72 | +| 01010 | 56 | 84 | +| 01011 | 64 | 96 | +| 01100 | 72 | 108 | +| 01101 | 80 | 120 | +| 01110 | 88 | 132 | +| 01111 | 104 | 156 | +| 10000 | 120 | 180 | +| 10001 | 136 | 204 | +| 10010 | 152 | 228 | +| 10011 | 168 | 252 | +| 10100 | 184 | 276 | +| 10101 | 200 | 300 | +| 10110 | 216 | 324 | +| 10111 | 232 | 348 | +| 11000 | 248 | 372 | +| 11001 | 264 | 396 | +| 11010 | 280 | 420 | +| 11011 | 296 | 444 | +| 11100 | 312 | 468 | +| 11101 | 328 | 492 | +| 11110 | 344 | 516 | +| 11111 | 376 | 564 | + +If the FLCTRLT field is set to one (hold time/management), the FLCTRL field shall contain either the time period that the transmitter shall hold transmissions to this node, or connection management information (see clause 8.12 of [[ITU-T G.9961](#)]). It is a 5-bit field that shall be coded as shown in Table 7-23. + +**Table 7-23 – FLCTRL field values for hold time/management** + +| FLCTRL value
(b 6 b 5 b 4 b 3 b 2 ) | Interpretation | +|-----------------------------------------------------------------------------------------------|----------------------| +| Hold times | | +| 00000 | Until next MAC cycle | +| 00001 | 5 ms | +| 00010 | 10 ms | +| 00011 | 15 ms | +| 00100 | 20 ms | + +**Table 7-23 – FLCTRL field values for hold time/management** + +| FLCTRL value
(b 6 b 5 b 4 b 3 b 2 ) | Interpretation | +|-----------------------------------------------------------------------------------------------|-------------------------------| +| 00101 | 30 ms | +| 00110 | 40 ms | +| 00111 | 50 ms | +| 01000 to 11011 | Reserved by ITU-T | +| Management | | +| 11100 | Release acknowledgement | +| 11101 | Connection release indication | +| 11110 | Connection accepted | +| 11111 | Unavailability of resources | + +The receiver shall set the FLCTRLT field to one to convey the following connection management information (see clause 8.12 of [[ITU-T G.9961](#)]): + +- If the transmitter has requested the release of a connection, the receiver shall acknowledge the release by setting the FLCTRL field to 111002. +- If the receiver wants to release a connection, it shall inform the transmitter by setting the FLCTRL field to 111012. +- If the receiver accepts a requested connection, it shall inform the transmitter by setting the FLCTRL field to 111102. +- If the receiver does not have resources available for a requested connection, it shall inform the transmitter by setting the FLCTRL field to 111112. + +###### 7.1.2.3.2.3.4 Request for bidirectional transmission (BTXRQ) + +The BTXRQ bit shall be used to request bidirectional transmission. It shall be set to one for a request and set to zero for no request (see clause 8.3.7 of [[ITU-T G.9961](#)]). + +###### 7.1.2.3.2.3.5 Data RX reset flag (RXRST\_DATA) + +The RXRST\_DATA field shall contain the value of the ACK\_RX\_RESET variable of the state machine of the data connection that this ACK refers to (see clause 8.9.5.3 of [[ITU-T G.9961](#)]). + +###### 7.1.2.3.2.3.6 Management RX reset flag (RXRST\_MNGMT) + +The RXRST\_MNGMT field shall contain the value of the ACK\_RX\_RESET variable of the state machine of the management flow that this ACK refers to (see clause 8.9.5.3 of [[ITU-T G.9961](#)]). + +###### 7.1.2.3.2.3.7 Bad burst indication (BAD\_BURST) + +The BAD\_BURST field shall be used by the receiver to indicate to the transmitter that all LPDUs sent in the last PHY-frame burst were received in error. + +When all LPDUs of all frames (one or more) of the last PHY-frame burst have been received in error, the BAD\_BURST field shall be set to one; otherwise, it shall be set to zero. + +###### 7.1.2.3.2.3.8 ACK channel estimation control/Receiver window size for the connection (ACK\_CE\_CTRL/RX\_CONN\_WIN\_SIZE) + +In the case of an ACK frame sent in response to an MSG frame requesting the set-up or reset of a data or management connection with acknowledgements (i.e., when CNN\_MNGMT in the MSG frame is 01012, 00012, 00112 or 01112, see Table 7-17), this parameter is called + +RX\_CONN\_WIN\_SIZE and the value of this parameter shall indicate the maximum acknowledge window size (i.e., ACK\_RX\_CONF\_WINDOW\_SIZE in clause 8.9.4.3 of [ITU-T G.9961]) that the receiver can support for the connection being set up. The maximum acknowledge window size shall be 8 times the value of (RX\_CONN\_WIN\_SIZE+1) LPDUs. The valid values for the maximum acknowledge window size shall be 8, 16, 24 ... 1024 LPDUs. The indicated value of maximum acknowledge window size shall be less than or equal to ACK\_MAX\_WINDOW\_SIZE (1024 for data connections, 32 for management connections – see clause 8.9.4.1 of [ITU-T G.9961]). + +For all other ACK frames, this field is called ACK\_CE\_CTRL and is used for channel estimation control. It is a 7-bit field that consists of the ACK\_CE\_CTRL\_TYPE field and the RUNTIME\_BAT\_ID field as shown in Table 7-24. + +**Table 7-24 – Interpretation of the ACK\_CE\_CTRL field** + +| Field | Octet | Bits | +|---------------------------|-------|-------| +| ACK_CE_CTRL_TYPE | 0 | [1:0] | +| RUNTIME_BAT_ID | | [6:2] | +| Reserved for ITU-T G.9963 | | [7] | + +###### 7.1.2.3.2.3.8.1 ACK channel estimation control type (ACK\_CE\_CTRL\_TYPE) + +ACK\_CE\_CTRL\_TYPE is a 2-bit field that shall be coded as shown in Table 7-25. + +**Table 7-25 – ACK\_CE\_CTRL\_TYPE field values** + +| ACK_CE_CTRL_TYPE value
(b 1 b 0 ) | Interpretation | +|------------------------------------------------------------|-------------------------------------------| +| 00 | No ACK_CE_CTRL information is transmitted | +| 01 | RUNTIME_BAT_ID is invalid | +| 10 | Request PROBE frame transmission. | +| 11 | Reserved by ITU-T | + +If the ACK\_CE\_CTRL\_TYPE field is set to 012, the runtime BAT associated with the RUNTIME\_BAT\_ID shall not be used for transmission, as specified in clause 8.11.5 of [ITU-T G.9961]. + +In addition, if the ACK\_CE\_CTRL\_TYPE field is set to 102, a PROBE frame transmission is requested. + +Otherwise, the ACK\_CE\_CTRL\_TYPE field shall be set to 002. + +###### 7.1.2.3.2.3.8.2 Runtime BAT ID (RUNTIME\_BAT\_ID) + +If the ACK\_CE\_CTRL\_TYPE field is set to 012, this field shall contain a RUNTIME\_BAT\_ID (see Table 7-57). Otherwise, it shall be set to 000002. + +###### 7.1.2.3.2.3.9 Acknowledgement data and Mc-ACK descriptor (ACKDATA/MCACK\_D) + +If the MI field is set to zero (for unicast acknowledgement), this field shall contain a 91-bit ACKDATA field. + +If the MI field is set to one (for multicast acknowledgement), this field shall contain a 12-bit Mc-ACK descriptor (see clause 7.1.2.3.2.3.9.2) followed by a 79-bit ACKDATA field. + +###### 7.1.2.3.2.3.9.1 ACKDATA + +The ACKDATA field for different cases shall be coded as shown in Tables 7-26, 7-27, 7-28 and 7-29. + +**Table 7-26 – Unicast ACKDATA specific fields when MNMTP is set to zero** + +| Field | Octet | Bits | +|---------------------------|---------|---------| +| FACK | 0 to 11 | [2:0] | +| CONNECTION_ID | | [10:3] | +| MNMTP | | [11] | +| LSSN | | [23:12] | +| ACKI | | [90:24] | +| Reserved (See Table 7-20) | | [95:91] | + +**Table 7-27 – Unicast ACKDATA specific fields when MNMTP is set to one** + +| Field | Octet | Bits | +|---------------------------|---------|-------------------------------------| +| FACK | 0 to 11 | [2:0] | +| CONNECTION_ID | | [10:3] | +| MNMTP | | [11] | +| MNMT_LSSN | | [17:12] | +| MNMTL | | [22:18] | +| MNMT_ACKI | | [(MNMTL_VALUE+22):23] | +| LSSN | | [(MNMTL_VALUE+34):(MNMTL_VALUE+23)] | +| ACKI | | [90:(MNMTL_VALUE+35)] | +| Reserved (see Table 7-20) | | [95:91] | + +**Table 7-28 – Multicast ACKDATA specific fields when MNMTP is set to zero** + +| Field | Octet | Bits | +|------------------------------------|---------|---------| +| Mc-ACK descriptor (see Table 7-35) | 0 to 11 | [11:0] | +| FACK | | [14:12] | +| CONNECTION_ID | | [22:15] | +| MNMTP | | [23] | +| LSSN | | [35:24] | +| ACKI | | [90:36] | +| Reserved (see Table 7-20) | | [95:91] | + +**Table 7-29 – Multicast ACKDATA specific fields when MNMTP is set to one** + +| Field | Octet | Bits | +|------------------------------------|---------|-------------------------------------| +| Mc-ACK descriptor (see Table 7-35) | 0 to 11 | [11:0] | +| FACK | | [14:12] | +| CONNECTION_ID | | [22:15] | +| MNMTP | | [23] | +| MNMT_LSSN | | [29:24] | +| MNMTL | | [34:30] | +| MNMT_ACKI | | [(MNMTL_VALUE+34):35] | +| LSSN | | [(MNMTL_VALUE+46):(MNMTL_VALUE+35)] | +| ACKI | | [90:(MNMTL_VALUE+47)] | +| Reserved (see Table 7-20) | | [95:91] | + +The format of the FACK field shall be as described in clause 7.1.2.3.2.3.9.1.5. When selective acknowledgment is used, the FACK field shall indicate the format of the ACKI field. + +###### 7.1.2.3.2.3.9.1.1 Management LSSN presence indication (MNMTP) + +When MNMTP is set to zero, the format of the ACKDATA field shall be as described in Table 7-26 for unicast and Table 7-28 for multicast. When MNMTP is set to one, the format of the ACKDATA field shall be as described in Table 7-27 for unicast and Table 7-29 for multicast. + +###### 7.1.2.3.2.3.9.1.2 ACKDATA when MNMTP is set to zero + +The format of the LSSN field shall be as described in clause 7.1.2.3.2.3.9.1.6. + +The format of the ACKI field shall be as described in clause 7.1.2.3.2.3.9.1.7. + +###### 7.1.2.3.2.3.9.1.3 ACKDATA when MNMTP is set to one + +If MNMTP (see clause 7.1.2.3.2.3.9.1.1) is set to one, the LSSN field (see clause 7.1.2.3.2.3.9.1.6) and the ACKI (see clause 7.1.2.3.2.3.9.1.7) field shall refer to the receiver window corresponding to the data connection (see clauses 8.1.3.2.1.4 and 8.12 of [[ITU-T G.9961](#)]). + +###### 7.1.2.3.2.3.9.1.3.1 Management lowest SSN (MNMT\_LSSN) + +The MNMT\_LSSN field shall hold the six LSBs of the ACK\_RX\_WINDOW\_START of the receiver window corresponding to the management connection (see clauses 8.1.3.2.1.4 and 8.12 of [[ITU-T G.9961](#)]). + +###### 7.1.2.3.2.3.9.1.3.2 Management ACKI length (MNMTL) + +The MNMTL field shall contain the variable MNMTL\_VALUE representing the size in bits of the MNMT\_ACKI field. It shall be represented as a 5-bit unsigned integer with valid values in the range from 000002 to 111112. + +###### 7.1.2.3.2.3.9.1.3.3 Management bit map encoding (MNMT\_ACKI) + +If MNMTL > 0, the MNMT\_ACKI field shall contain a bit array indicating the correct reception of segments in the receiver window corresponding to the management connection (see clauses 8.1.3.2.1.4 and 8.12 of [[ITU-T G.9961](#)]). The bit corresponding to a segment shall be set to zero if the segment was received correctly. Otherwise, it shall be set to one. The first MNMT\_ACKI bit shall represent the reception status of the segment with SSN equal to ACK\_RX\_WINDOW\_START+1, the second MNMT\_ACKI bit shall represent the reception status of the segment with SSN equal to ACK\_RX\_WINDOW\_START+2, and so on until the last correctly received segment within the ACK\_RX\_CONF\_WINDOW. + +Segments for which the reception status was not reported in the MNMT\_ACKI shall be considered by the transmitter as not received correctly by the receiver. + +###### 7.1.2.3.2.3.9.1.4 Connection identifier (CONNECTION\_ID) + +The CONNECTION\_ID field shall identify the connection (see clause 7.1.2.3.2.2.12) corresponding to the LPDUs being acknowledged. It shall be represented as an 8-bit unsigned integer. The value 255 shall be used to indicate that no acknowledgement information is included in the ACKDATA field. If the ACKDATA field contains acknowledgement information about only the management connection, the CONNECTION\_ID shall be set to 251. If the ACKDATA field contains acknowledgement information about a multicast connection, the CONNECTION\_ID shall be set to 252. + +The values 253 and 254 are reserved by ITU-T. + +###### 7.1.2.3.2.3.9.1.5 Frame ACK (FACK) + +The FACK field shall be used to indicate the format of the ACKI field message included in the ACK message. It is a 3-bit field that shall be coded as shown in Table 7-30. + +**Table 7-30 – FACK field values** + +| FACK value
(b 2 b 1 b 0 ) | Interpretation | +|---------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| 000 | Selective acknowledgement – ACKI format is bit map | +| 001 | Selective acknowledgement – ACKI format is run-length encoded | +| 010 | Selective acknowledgement – ACKI format is group encoded | +| 011 to 110 | Reserved by ITU-T | +| 111 | All the fields of the FTSF of ACK PHY-frame, other than FACK, are not valid. This value shall only be used for ACK PHY-frame. | + +###### 7.1.2.3.2.3.9.1.6 Lowest SSN (LSSN) + +The LSSN field shall contain the 12 LSBs of the ACK\_RX\_WINDOW\_START of the receive window. + +###### 7.1.2.3.2.3.9.1.7 ACK information (ACKI) + +The reception status of data units consisting of one or more segments shall be indicated in the ACKI field by the receiver. The data unit corresponding to each indication in the ACKI field depends on the format of the ACKI field (see Table 7-30). The indication corresponding to a data unit shall be set to one if the data unit was not received correctly and shall be set to zero if the data unit was received correctly. For the cases of bit map encoding and group encoding, if there is no more information to encode, the remaining bits of this field (if any) shall be encoded by the receiver to indicate that the rest of the data units have been received with errors. For the case of run-length encoding, if there is no more information to encode, the remaining bits of this field (if any) shall be encoded to indicate that the rest of the groups in the field have a length of zero. The specific encoding for different formats of the ACKI field is as explained in the following clauses. + +If the number of bits in the ACKI field is not sufficient to indicate reception status of all the received segments, a receiver may choose to use compressed encoding or limit the indication to the number of available bits. Segments corresponding to data units for which the reception status was not reported shall be considered by the transmitter as either not received correctly by the receiver or in waiting-for-ack state. + +If the number of bits in the ACKI field is not sufficient, the receiver may indicate to the transmitter that it would like to use the extended ACK in future frames by setting the EXTACKRQ bit as described in clause 7.1.2.3.2.3.10. + +If the transmitter has already granted permission to the receiver to use extended ACK, the receiver may use extended ACK as described in clause 8.3.8 of [ITU-T G.9961]. The format of the ACK extension is as described in clause 7.1.2.3.3.1.4. + +###### 7.1.2.3.2.3.9.1.7.1 Bit map encoding + +When the FACK field indicates bit map encoding, the ACKI field shall be encoded as a bit array. + +The ACKI field shall contain an indication of the correct reception of segments in the receiver window. The first ACKI bit shall represent the reception status of the segment with SSN equal to ACK\_RX\_WINDOW\_START+1, the second ACKI bit shall represent the reception status of the segment with SSN equal to ACK\_RX\_WINDOW\_START+2, and so on until the last correctly received segment within the ACK\_RX\_CONF\_WINDOW. + +If there is no more information to encode, the remaining bits, if any, of the ACKI field shall be set to one by the receiver. + +###### 7.1.2.3.2.3.9.1.7.2 Compressed encoding + +In the compressed coding format, the reception status of the received segments shall be transmitted by groups. None of the segments received with errors shall be coded as correctly received. Correctly received segments may be encoded as incorrectly received. + +The grouping of segments shall start from the segment with SSN equal to ACK\_RX\_WINDOW\_START+1. + +If there is no more information to encode, the remaining bits of the ACKI field, if any, shall be encoded by the receiver indicating that the rest of the segments have been received with errors. + +###### 7.1.2.3.2.3.9.1.7.2.1 Run-length encoding + +With run-length encoding, the number of segments belonging to a group defines the length of the group. The GRPLGTH field shall indicate the length of each group, which is variable. It shall be represented as a 3-bit unsigned integer as shown in Table 7-31 and shall be coded as shown in Table 7-32. + +**Table 7-31 – ACKI subfields with run-length encoding** + +| Field | Size in bits | +|------------------|--------------| +| GRPLGTH | 3 | +| GRP 0 | GRPLGTH | +| ... | | +| GRP N | GRPLGTH | + +**Table 7-32 – Encoding of GRPLGTH values** + +| Value of the GRPLGTH field | GRPLGTH interpretation | +|----------------------------|------------------------| +| 0 | GRPLGTH=2 | +| 1 | GRPLGTH=3 | +| ... | ... | +| 7 | GRPLGTH=9 | + +The first group (GRP0) indicates the number of consecutive segments that have not been correctly received. + +If one group (GRPi) indicates the number of segments that have been received correctly, the next group (GRPi+1) shall indicate the number of segments that have been received incorrectly or not received. + +If one group (GRPi) indicates the number of segments that have been received incorrectly or not received, the next group (GRPi+1) shall indicate the number of segments that have been received correctly. + +If the length of ACKI field, excluding GRPLGTH field, ( $N_{\text{BitsForGroups}}$ ) is not multiple of the number of bits used to specify the length of the group (GRPLGTH interpretation, as defined in Table 7-31), the last $P = \text{remainder}(N_{\text{BitsForGroups}} / \text{GRPLGTH interpretation})$ bits of the ACKI field, , shall be considered as padding and shall be ignored by the transmitter. + +###### 7.1.2.3.2.3.9.1.7.2.2 Group encoding + +With group encoding, all groups shall have the same number of segments. The COMP\_RT field shall contain the number of segments that form a group. It shall be represented as a 3-bit unsigned integer as shown in Table 7-33 and shall be coded as shown in Table 7-34. + +The GRP\_MAP field shall be used to represent the status of all groups. Each bit of the field shall indicate the status of one group, where a one shall indicate that at least one segment in the group was not received correctly and a zero shall indicate that all segments in the group were received correctly. + +**Table 7-33 – ACKI subfields with group encoding** + +| Field | Size in bits | +|---------|-----------------------| +| COMP_RT | 3 | +| GRP_MAP | Rest of the ACKI bits | + +**Table 7-34 – Encoding of COMP\_RT values** + +| Value of the COMP_RT field | COMP_RT interpretation | +|----------------------------|------------------------| +| 0 | COMP_RT=2 | +| 1 | COMP_RT=3 | +| ... | ... | +| 7 | COMP_RT=9 | + +###### 7.1.2.3.2.3.9.2 Mc-ACK descriptor (MCACK\_D) + +The MCACK\_D field is only valid for multicast acknowledgement (Mc-ACK). It is a 12-bit field that shall be coded as shown in Table 7-35. + +**Table 7-35 – MCACK\_D fields description** + +| Field | Octet | Bits | Description | +|---------|-------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC_SID | 0 | [7:0] | DEVICE_ID of the multicast frame source that requested Mc-ACK | +| NUM_SLT | 1 | [2:0] | Number of Mc-ACK slots assigned after this Mc-ACK slot, represented as unsigned integer in the range between 0 and 6.
The value 7 is reserved by ITU-T. | +| NACKP | | [3] | Indicates presence of NACK (see Table 7-15):
0 – NACK signalling slot is not present
1 – NACK signalling slot is present | + +###### 7.1.2.3.2.3.10 Extended ACK requested (EXTACKRQ) + +If the EXTACKRQ field is set to one, it shall indicate that the node transmitting the ACK frame would like to send extended ACKs and the source node should allocate time for an extended ACK in future frames as described in clause 8.3.8 of [ITU-T G.9961]. If the EXTACKRQ field is set to zero, it shall indicate that the node transmitting the ACK frame will not be using extended ACKs and does not require the extra resources. + +###### 7.1.2.3.2.3.11 Flow control extension (FLCTRL\_EXT) + +The FLCTRL\_EXT field shall be used to indicate higher values of flow control between the transmitter and the receiver as described in clause 8.12.4 of [ITU-T G.9961], compared to those indicated by the field FLCTRL as described in clause 7.1.2.3.2.3.3. This field FLCTRL\_EXT shall be set to one only if the field FLCTRLT is set to 0 (see clause 7.1.2.3.2.3.2). If FLCTRL\_EXT is set to one, for connections with 540 byte LPDUs 408 is added and for connections with 120 byte LPDUs 612 is added to the value indicated by the FLCTRL (see clause 7.1.2.3.2.3.3) value to determine the actual number of LPDUs that the receiver can buffer for the flow. For example, for a connection with 540 byte LPDUs, if FLCTRL\_EXT is set and FLCTRL is set to 000112 the receiver indicates that it can buffer (408 + 16 = 424) LPDUs. + +###### 7.1.2.3.2.4 RTS PHY-frame type specific fields + +Table 7-36 lists the PHY-frame header fields which are specific to the RTS frame type: + +**Table 7-36 – RTS PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|--------|------------------------|----------------------------------| +| RTS_DUR | 0 and 1 | [15:0] | Duration for RTS frame | Clause 7.1.2.3.2.4.1 | +| CID | 2 | [7:0] | CTS proxy ID | Clause 7.1.2.3.2.4.2 | +| CURRTS | 3 | [6:0] | Current TS | Clause 7.1.2.3.2.4.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 4 | [1:0] | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | | [7:2] | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | 5 to 14 | [87:0] | Reserved | 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.1.2.3.2.4.1 Duration for RTS frame (RTS\_DUR) + +The RTS\_DUR field shall contain the total duration of the following sequence: + +- the transmission time of the RTS frame; +- duration of RCIFG between RTS and CTS frames; +- the transmission time of the CTS frame; +- the transmission time of the MSG frames that follow the CTS frame and the BIFGs that separate them; +- duration of CCIFG between CTS frame and MSG frame that follows CTS frame; +- if ACK is required, the duration of the AIFG and the ACK frames; +- if Mc-ACK is required, the duration of default AIFG gap and the Mc-ACK sequence duration. + +###### 7.1.2.3.2.4.2 CTS proxy ID (CID) + +The CID field shall contain the DEVICE\_ID of the node that should respond in CTS for multicast traffic. It shall be represented as an 8-bit unsigned integer with valid values in the range from 1 to 250. + +###### 7.1.2.3.2.4.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### 7.1.2.3.2.5 CTS PHY-frame type specific fields + +Table 7-37 lists the header fields which are specific to the CTS frame type. + +**Table 7-37 – Specific fields of the CTS PHY-frame type** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|------------------------|--------------------------| +| CTS_DUR | 0 and 1 | [15:0] | Duration for CTS frame | Clause 7.1.2.3.2.5.1 | +| Reserved | 2 to 14 | [103:0] | Reserved | 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.1.2.3.2.5.1 Duration for CTS frame (CTS\_DUR) + +The CTS\_DUR field shall repeat the duration expressed in the preceding RTS frame minus the RTS frame transmission time and the inter-frame gap that follows the RTS frame. + +###### 7.1.2.3.2.6 CTMG PHY-frame type specific fields + +Table 7-38 lists the PHY-frame header fields which are specific to the CTMG frame type. + +**Table 7-38 – CTMG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|--------|---------|---------|-----------------------------------|----------------------| +| IACKRQ | 0 | [0] | Immediate acknowledgment required | Clause 7.1.2.3.2.6.1 | +| CURRTS | | [7:1] | Current TS | Clause 7.1.2.3.2.6.3 | +| CTMGD | 1 to 14 | [111:0] | CTMG data | Clause 7.1.2.3.2.6.2 | + +###### 7.1.2.3.2.6.1 Immediate acknowledgment required (IACKRQ) + +When the IACKRQ field is set to one, the receiver shall follow the reception of the CTMG frame with an acknowledgement CTMG frame (ACTMG) $T_{AIFG-D}$ (see clause 8.4 of [ITU-T G.9961], and clause 7.1.2.3.2.6.2) after the end of the CTMG frame. All nodes in the domain shall refrain from transmission when an ACTMG frame is expected and within $T_{IFG\_MIN}$ following it. The sender shall plan its transmission so that the ACTMG that follows the transmitted CTMG frame is contained within the TXOP or TS assigned for the transmission. + +###### 7.1.2.3.2.6.2 CTMG data (CTMGD) + +If the EHI field is set to zero, the CTMGD field shall contain a single control message composed of a CMH and a CMPL field as shown in clause 8.10.2 of [ITU-T G.9961]. If the size of the control message is shorter than the size of CTMGD (112 bits), the remainder of the CTMGD field shall be padded with zeros. + +If the EHI field is set to one, concatenated CTMGD and CTMGD\_EXT fields (see clause 7.1.2.3.3.1.1.1) shall be considered as one field, the first byte (octet 0) of the CTMGD field being the first byte of the combined field and the last byte of the CTMGD\_EXT field being the last byte of the combined field. The combined field shall contain a single control message. In this case the size of the control message shall be less than or equal to the size of the combined field. The remainder of the CTMGD\_EXT field shall be padded with zeros. + +###### 7.1.2.3.2.6.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### 7.1.2.3.2.7 PROBE PHY-frame type specific fields + +The PROBE PHY-frame type specific field is composed of a common part and a variable part. The common part contains fields that are common for all PROBE PHY-frame types (PRBTYPES). The variable part contains fields that are specific to each PRBTYPE. + +The fields of the common part of the PROBE PHY-frame specific field are defined in Table 7-39. + +**Table 7-39 – PROBE PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------------|---------|--------|-----------------------------|----------------------------------| +| Common part | | | | | +| PRB_DUR | 0 and 1 | [15:0] | Duration for PROBE frame | Clause 7.1.2.3.2.7.1.1 | +| PRBTYPE | 2 | [3:0] | PROBE frame type | Clause 7.1.2.3.2.7.1.2 | +| PRBSYM | | [7:4] | Probe symbols | Clause 7.1.2.3.2.7.1.3 | +| APSD_MAX-P | 3 | [4:0] | APSD_MAX-P of a PROBE frame | Clause 7.1.2.3.2.7.1.4 | +| PRBGI | | [7:5] | PROBE guard interval | Clause 7.1.2.3.2.7.1.5 | +| CURRTS | 4 | [6:0] | Current TS | Clause 7.1.2.3.2.7.1.6 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T G.9963 | +| APSD_MAX-P_EXT | 5 | [0] | APSD_MAX-P extension | Clause 7.1.2.3.2.7.1.7 | +| Reserved | | [7:1] | Reserved | Reserved by ITU-T (Note) | +| Variable part | | | | | + +**Table 7-39 – PROBE PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-------|---------|--------|---------------------------------|----------------------| +| PFTSF | 6 to 14 | [71:0] | PROBE frame type specific field | Clause 7.1.2.3.2.7.2 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +###### 7.1.2.3.2.7.1 Common part fields + +###### 7.1.2.3.2.7.1.1 Duration for PROBE frame (PRB\_DUR) + +The PRB\_DUR field shall contain the transmission time of the PROBE frame. + +###### 7.1.2.3.2.7.1.2 PROBE frame type (PRBTYPE) + +The PRBTYPE field shall contain the type of the PROBE frame. It is a 4-bit field that shall be coded as shown in Table 7-40. + +**Table 7-40 – PRBTYPE field values** + +| PRBTYPE value
(b 3 b 2 b 1 b 0 ) | Interpretation | Reference | +|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| 0000 | Silent PROBE frame – a PHY frame in which the probe symbols composing the payload shall all be silent symbols, as specified in clause 7.1.3.6. | Clause 7.1.2.3.2.7.2.1 | +| 0001 | Channel estimation PROBE frame – a PHY frame in which the probe symbols composing the payload shall all be channel estimation probe symbols, as specified in clause 7.1.3.6. | Clause 7.1.2.3.2.7.2.2 | +| 0010 to 0111 | Reserved by ITU-T | | +| 1000 to 1011 | Reserved for use by ITU-T G.9963 | | +| 1100 to 1111 | Reserved by ITU-T | | + +###### 7.1.2.3.2.7.1.3 Probe symbols (PRBSYM) + +The PRBSYM field shall contain the number of OFDM payload symbols in the PROBE frame. It is a 4-bit field that shall be coded as shown in Table 7-41. + +**Table 7-41 – PRBSYM field values** + +| PRBSYM value
(b 7 b 6 b 5 b 4 ) | Interpretation | +|--------------------------------------------------------------------------------|--------------------| +| 0000 | 4 Payload symbols | +| 0001 | 8 Payload symbols | +| 0010 | 12 Payload symbols | +| .... | .... | +| 1111 | 64 Payload symbols | + +###### 7.1.2.3.2.7.1.4 Maximum actual PSD of PROBE frame (APSD\_MAX-P) + +The APSD\_MAX-P and APSD\_MAX-P\_EXT fields shall together indicate the APSD\_MAX for the PHY frame. It shall be represented as a 6-bit unsigned integer with valid values in the range from 0 + +to 50, plus 62 and 63. Values from 0 to 50 correspond to an APSD\_MAX in the range of –50 dBm/Hz to –100 dBm/Hz in 1 dB steps. + +The most significant 5 bits of the APSD\_MAX are conveyed in the APSD\_MAX-P field and the least significant bit of the APSD\_MAX is conveyed in the APSD\_MAX-P\_EXT field. + +The special values 62 and 63 shall indicate that the frame has been transmitted with an APSD\_MAX that is the minimum of: + +- Highest value of the transmit PSD allowed (i.e., TxPSD after applying PSD ceiling if applicable) +- Highest value of the PSD that the node is capable of transmitting. + +All other values are reserved by ITU-T. + +###### 7.1.2.3.2.7.1.5 PROBE symbol guard interval (PRBGI) + +The PRBGI field shall contain the guard interval value used for the payload of the PROBE frame. It shall be coded in the same way as described in Table 7-14 in clause 7.1.2.3.2.2.10. + +###### 7.1.2.3.2.7.1.6 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### 7.1.2.3.2.7.1.7 APSD\_MAX-P extension + +See clause 7.1.2.3.2.7.1.4. + +###### 7.1.2.3.2.7.2 PROBE frame type specific field + +This clause details the PROBE frame-type specific field (PFTSF), a variable part of the PROBE PHY-frame type specific field separately defined for each PROBE frame type (PRBTYPE). + +###### 7.1.2.3.2.7.2.1 Silent PROBE frame specific fields + +Table 7-42 lists the PROBE frame fields which are specific to the silent PROBE frame type. + +**Table 7-42 – Silent PROBE frame specific field values** + +| Field | Octet | Bits | Description | +|-------------------------------------------------------------------------------------------------------------|--------|--------|--------------------------| +| Reserved | 0 to 8 | [71:0] | 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.1.2.3.2.7.2.2 Channel estimation PROBE frame specific fields + +Table 7-43 lists the PROBE frame fields which are specific to the channel estimation PROBE frame type. + +**Table 7-43 – Channel estimation PROBE frame specific field values** + +| Field | Octet | Bits | Description | +|-------------------------------------------------------------------------------------------------------------|--------|--------|--------------------------| +| Reserved | 0 to 8 | [71:0] | 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. | | | | + +**Table 7-44 – Placeholder table** + +(This table has been intentionally left blank.) + +###### 7.1.2.3.2.8.8 ACKRQ PHY frame type specific fields + +Table 7-45 lists the PHY-frame header fields which are specific to the ACKRQ frame type. + +**Table 7-45 – ACKRQ PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|---------------|---------|--------|-----------------------|--------------------------| +| RX_WIN_TYPE | 0 | [1:0] | Requested RX window | Clause 7.1.2.3.2.8.1 | +| Reserved | | [7:2] | Reserved | Reserved by ITU-T (Note) | +| CONNECTION_ID | 1 | [7:0] | Connection identifier | Clause 7.1.2.3.2.8.2 | +| CURRTS | 2 | [6:0] | Current TS | Clause 7.1.2.3.2.8.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 3 to 14 | [95:0] | Reserved | 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.1.2.3.2.8.1 Requested RX window (RX\_WIN\_TYPE) + +The RX\_WIN\_TYPE field shall indicate which receiver window status is requested to be retransmitted according to Table 7-46. + +**Table 7-46 – RX\_WIN\_TYPE field allowed values** + +| RX_WIN_TYPE value (b 1 b 0 ) | Description | +|----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | The receiver shall only send the current status of the reception window of the data connection identified by the CONNECTION_ID field and the SID of the ACKRQ frame. | +| 01 | The receiver shall only send the current status of the reception window of the management connection from the SID of the ACKRQ frame. | +| 10 | The receiver shall send the current status of the reception windows of:
  • the management connection from the SID of the ACKRQ frame;
  • the data connection identified by the CONNECTION_ID and the SID of the ACKRQ frame.
| +| 11 | Reserved by ITU-T | + +###### 7.1.2.3.2.8.2 Connection identifier (CONNECTION\_ID) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.12, the CONNECTION\_ID field of the MSG frame. + +###### 7.1.2.3.2.8.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### 7.1.2.3.2.9 BMSG PHY-frame type specific fields + +Table 7-47 lists the fields which are specific to the core part of the PHY-frame header of the BMSG frame type. + +**Table 7-47 – BMSG PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|----------------|----------|--------|----------------------------------------------------------------|----------------------------------| +| BMSG_DUR | 0 and 1 | [15:0] | Duration for BMSG frame | Clause 7.1.2.3.2.9.1 | +| BLKSZ | 2 | [1:0] | Block size of FEC codeword for BMSG frame payload | Clause 7.1.2.3.2.9.2 | +| FEC_RATE | | [4:2] | FEC coding rate for BMSG frame payload | Clause 7.1.2.3.2.9.3 | +| REP | | [7:5] | Number of repetitions used for encoding the BMSG frame payload | Clause 7.1.2.3.2.9.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 7.1.2.3.2.9.5 | +| SI | | [6:3] | Scrambler initialization | Clause 7.1.2.3.2.9.6 | +| MDET | | [7] | Master is detected | Clause 7.1.2.3.2.9.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 7.1.2.3.2.9.8 | +| OFB_ID/GRP_ID | | [7:5] | OFB identifier/subcarrier grouping identifier | Clause 7.1.2.3.2.9.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 7.1.2.3.2.9.10 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of a BMSG frame | Clause 7.1.2.3.2.9.11 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 7.1.2.3.2.9.12 | +| RPRQ | 7 | [1:0] | Reply required | Clause 7.1.2.3.2.9.13 | +| BRSTCnt | | [3:2] | Burst frame count | Clause 7.1.2.3.2.9.14 | +| BEF | | [4] | Burst end flag | Clause 7.1.2.3.2.9.15 | +| AIFG_IND | | [5] | AIFG indication | Clause 7.1.2.3.2.9.16 | +| Reserved | | [6] | Reserved | Reserved for use by ITU-T G.9963 | +| EXTACKGR | | [7] | Extended ACK granted | Clause 7.1.2.3.2.9.25 | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 7.1.2.3.2.9.17 | +| CNN_MNGMT | | [6:3] | Connection management | Clause 7.1.2.3.2.9.18 | +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 7.1.2.3.2.9.27 | +| BRURQ | 9 and 10 | [15:0] | Bandwidth reservation update request | Clause 7.1.2.3.2.9.19 (Note 2) | +| START_SSN | 9 and 10 | [15:0] | Start segment sequence number | Clause 7.1.2.3.2.9.20 (Note 3) | +| CURRTS | 11 | [6:0] | Current TS | Clause 7.1.2.3.2.9.21 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note 1) | + +**Table 7-47 – BMSG PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|-------------|-----------|---------|-----------------------------------------|----------------------------| +| Reserved | 12 and 13 | [0] | Reserved | Reserved by ITU-T (Note 1) | +| BTXGL | | [8:1] | Bidirectional transmission grant length | Clause 7.1.2.3.2.9.22 | +| BTXEF | | [9] | Bidirectional transmission end flag | Clause 7.1.2.3.2.9.23 | +| P-DACK | | [10] | Piggybacked Delayed Acknowledgement | Clause 7.1.2.3.2.9.26 | +| Reserved | | [15:11] | Reserved | Reserved by ITU-T (Note 1) | +| ACK_CE_CTRL | 14 | [7:0] | ACK channel estimation control | Clause 7.1.2.3.2.9.24 | +| | | | | | + +NOTE 1 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. +NOTE 2 – The BRURQ field is defined when the START\_SSN field is not defined. +NOTE 3 – The START\_SSN field is defined only when CNN\_MNGMT = 0001, CNN\_MNGMT = 0011, CNN\_MNGMT = 0101 or CNN\_MNGMT = 0111. Otherwise, the meaning of this field is BRURQ. + +The PHY-frame header fields which are specific to the extended part of the header of the BMSG frame type are listed in Table 7-53. + +###### 7.1.2.3.2.9.1 Duration for BMSG frame (BMSG\_DUR) + +For a BMSG frame where Imm-ACK or a BACK does not follow the BMSG frame, the BMSG\_DUR field shall contain the transmission time of the BMSG frame. + +For a BMSG frame where Imm-ACK or BACK follows the BMSG frame, the BMSG\_DUR field shall contain the transmission time of the BMSG frame plus the duration of the following AIFG (for Imm-Ack) or BM2BAIFG (for BACK). The BMSG\_DUR field value shall not exceed TMAX\_MSG\_DURATION. + +###### 7.1.2.3.2.9.2 Block size (BLKSZ) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.2, the BLKSZ field of the MSG frame. + +###### 7.1.2.3.2.9.3 FEC coding rate (FEC\_RATE) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.3, the FEC\_RATE field of the MSG frame. + +###### 7.1.2.3.2.9.4 Repetitions (REP) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.4, the REP field of the MSG frame. + +###### 7.1.2.3.2.9.5 FEC concatenation factor (FCF) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.5, the FCF field of the MSG frame. + +###### **7.1.2.3.2.9.6 Scrambler initialization (SI)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.6, the SI field of the MSG frame. + +###### **7.1.2.3.2.9.7 Master is detected indication (MDET)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.7, the MDET field of the MSG frame. + +###### **7.1.2.3.2.9.8 Bit allocation table identifier (BAT\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.8, the BAT\_ID field of the MSG frame. + +###### **7.1.2.3.2.9.9 OFB identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.9, the OFB\_ID/GRP\_ID field of the MSG frame. + +###### **7.1.2.3.2.9.10 Guard interval identifier (GI\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.10, the GI\_ID field of the MSG frame. + +###### **7.1.2.3.2.9.11 Maximum actual PSD of BMSG frame (APSD\_MAX-M)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.11, the APSD\_MAX-M field of the MSG frame. + +###### **7.1.2.3.2.9.12 Connection identifier (CONNECTION\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.12, the CONNECTION\_ID field of the MSG frame. + +###### **7.1.2.3.2.9.13 Reply required (RPRQ)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.13, the RPRQ field of the MSG frame. + +###### **7.1.2.3.2.9.14 Burst frame count (BRSTCnt)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.14, the BRSTCnt field of the MSG frame. + +###### **7.1.2.3.2.9.15 Burst end flag (BEF)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.15, the BEF field of the MSG frame. + +###### **7.1.2.3.2.9.16 AIFG indication (AIFG\_IND)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.16, the AIFG\_IND field of the MSG frame. + +###### **7.1.2.3.2.9.17 ACE symbols (ACE\_SYM)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.17, the ACE\_SYM field of the MSG frame. + +###### **7.1.2.3.2.9.18 Connection management (CNN\_MNGMT)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.18, the CNN\_MNGMT field of the MSG frame. + +###### **7.1.2.3.2.9.19 Bandwidth reservation update request (BRURQ)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.19, the BRURQ field of the MSG frame. + +###### **7.1.2.3.2.9.20 Start segment sequence number (START\_SSN)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.20, the START\_SSN field of the MSG frame. + +###### **7.1.2.3.2.9.21 Current TS (CURRTS)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### **7.1.2.3.2.9.22 Bidirectional transmission grant length (BTXGL)** + +The BTXGL field shall contain the granted bidirectional transmission duration in multiples of 8 µs. It shall be represented as an 8-bit unsigned integer. + +A grant length value of zero shall indicate that bidirectional transmission is not granted. The granted duration shall encompass all transmissions from the receiver including ACK and BACK frames. + +###### **7.1.2.3.2.9.23 Bidirectional transmission end flag (BTXEF)** + +If the BTXEF field is set to one, it shall indicate that this is the last exchange in the current TXOP/TS. + +###### **7.1.2.3.2.9.24 ACK channel estimation control (ACK\_CE\_CTRL)** + +The interpretation of this field shall be as specified for the ACK\_CE\_CTRL field of the ACK frame in clause 7.1.2.3.2.3.8. + +###### **7.1.2.3.2.9.25 Extended ACK Granted (EXTACKGR)** + +If the EXTACKGR field is set to one, it shall indicate that this transmitter can process extended ACK and the receiver may use extended ACK as a response to the transmitted BMSG frame as described in clause 8.3.8 of [\[ITU-T G.9961\]](#). + +###### **7.1.2.3.2.9.26 Piggybacked Delayed Acknowledgement (P-DACK)** + +If the P-DACK field is set to one, it indicates that this BMSG includes delayed ACK information as described in clause 8.3.9 of [\[ITU-T G.9961\]](#). It shall be set to zero otherwise. + +When using bidirectional transmissions this field shall be set to zero. + +###### **7.1.2.3.2.9.27 APSD\_MAX-M extension** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.25, the APSD\_MAX-M\_EXT field of the MSG frame. + +###### **7.1.2.3.2.10 BACK PHY-frame type specific fields** + +Table 7-48 lists the fields which are specific to the core part of the PHY-frame header of the BACK frame type. + +**Table 7-48 – BACK PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|----------------|----------|--------|----------------------------------------------------------------------|----------------------------------| +| BACK_DUR | 0 and 1 | [15:0] | Duration for BACK frame | Clause 7.1.2.3.2.10.1 | +| BLKSZ | 2 | [1:0] | Block size of FEC codeword for BACK frame payload | Clause 7.1.2.3.2.10.2 | +| FEC_RATE | | [4:2] | FEC coding rate for BACK frame payload | Clause 7.1.2.3.2.10.3 | +| REP | | [7:5] | Number of repetitions used for encoding the BACK frame payload | Clause 7.1.2.3.2.10.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 7.1.2.3.2.10.5 | +| SI | | [6:3] | Scrambler initialization | Clause 7.1.2.3.2.10.6 | +| MDET | | [7] | Master is detected | Clause 7.1.2.3.2.10.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 7.1.2.3.2.10.8 | +| OFB_ID/GRP_ID | | [7:5] | Operational frequency band identifier/subcarrier grouping identifier | Clause 7.1.2.3.2.10.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 7.1.2.3.2.10.10 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of a BACK frame | Clause 7.1.2.3.2.10.11 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 7.1.2.3.2.10.12 | +| RPRQ | 7 | [1:0] | Reply required | Clause 7.1.2.3.2.10.13 | +| BRSTCnt | | [3:2] | Burst frame count | Clause 7.1.2.3.2.10.14 | +| BEF | | [4] | Burst end flag | Clause 7.1.2.3.2.10.15 | +| AIFG_IND | | [5] | AIFG indication | Clause 7.1.2.3.2.10.16 | +| Reserved | | [6] | Reserved | Reserved for use by ITU-T G.9963 | +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 7.1.2.3.2.10.21 | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 7.1.2.3.2.10.17 | +| CNN_MNGMT | | [6:3] | Connection management | Clause 7.1.2.3.2.10.18 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| BTXRL | 9 | [7:0] | Bidirectional transmission request length | Clause 7.1.2.3.2.10.19 | +| ACK_CE_CTRL | 10 | [6:0] | ACK channel estimation control | Clause 7.1.2.3.2.10.20 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T G.9963 | +| Reserved | 11 to 14 | [31:0] | Reserved | 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. + +The PHY-frame header fields which are specific to the extended part of the header of the BACK frame type are listed in Table 7-54. + +###### **7.1.2.3.2.10.1 Duration for BACK frame (BACK\_DUR)** + +For a BACK frame where Imm-ACK or a BMSG does not follow the BACK frame, the BACK\_DUR field shall contain the transmission time of the BACK frame. + +For a BACK frame where Imm-ACK or BMSG follows the BACK frame, the BACK\_DUR field shall contain the transmission time of the BACK frame plus the duration of the following AIFG (for Imm-Ack) or BA2BMIFG (for BMSG). The BACK\_DUR field value shall not exceed $T_{MAX\_MSG\_DURATION}$ . + +###### **7.1.2.3.2.10.2 Block size (BLKSZ)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.2, the BLKSZ field of the MSG frame. + +###### **7.1.2.3.2.10.3 FEC coding rate (FEC\_RATE)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.3, the FEC\_RATE field of the MSG frame. + +###### **7.1.2.3.2.10.4 Repetitions (REP)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.4, the REP field of the MSG frame. + +###### **7.1.2.3.2.10.5 FEC concatenation factor (FCF)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.5, the FCF field of the MSG frame. + +###### **7.1.2.3.2.10.6 Scrambler initialization (SI)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.6, the SI field of the MSG frame. + +###### **7.1.2.3.2.10.7 Master is detected indication (MDET)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.7, the MDET field of the MSG frame. + +###### **7.1.2.3.2.10.8 Bit allocation table identifier (BAT\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.8, the BAT\_ID field of the MSG frame. + +###### **7.1.2.3.2.10.9 OFB identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.9, the OFB\_ID/GRP\_ID field of the MSG frame. + +###### **7.1.2.3.2.10.10 Guard interval identifier (GI\_ID)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.10, the GI\_ID field of the MSG frame. + +###### **7.1.2.3.2.10.11 Maximum actual PSD of BACK frame (APSD\_MAX-M)** + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.11, the APSD\_MAX-M field of the MSG frame. + +###### 7.1.2.3.2.10.12 Connection identifier (CONNECTION\_ID) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.12, the CONNECTION\_ID field of the MSG frame. + +###### 7.1.2.3.2.10.13 Reply required (RPRQ) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.13, the RPRQ field of the MSG frame. + +###### 7.1.2.3.2.10.14 Burst frame count (BRSTCnt) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.14, the BRSTCnt field of the MSG frame. + +###### 7.1.2.3.2.10.15 Burst end flag (BEF) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.15, the BEF field of the MSG frame. + +###### 7.1.2.3.2.10.16 AIFG indication (AIFG\_IND) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.16, the AIFG\_IND field of the MSG frame. + +###### 7.1.2.3.2.10.17 ACE symbols (ACE\_SYM) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.17, the ACE\_SYM field of the MSG frame. + +###### 7.1.2.3.2.10.18 Connection management (CNN\_MNGMT) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.18, the CNN\_MNGMT field of the MSG frame. + +###### 7.1.2.3.2.10.19 Bidirectional transmission request length (BTXRL) + +The BTXRL field shall contain the requested bidirectional transmission duration in multiples of 8 µs. It shall be represented as an 8-bit unsigned integer. A request length value of zero shall indicate that the acknowledging node is not requesting bidirectional transmission. + +###### 7.1.2.3.2.10.20 ACK channel estimation control (ACK\_CE\_CTRL) + +The interpretation of this field shall be as specified for the ACK\_CE\_CTRL field of the ACK frame in clause 7.1.2.3.2.3.8. + +###### 7.1.2.3.2.10.21 APSD\_MAX-M extension + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.25, the APSD\_MAX-M\_EXT field of the MSG frame. + +###### 7.1.2.3.2.11 ACTMG PHY-frame type specific fields + +Table 7-49 lists the PHY-frame header fields which are specific to the ACTMG frame type. + +**Table 7-49 – ACTMG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-------------------------------------------------------------------------------------------------------------|---------|---------|---------------------|--------------------------| +| CTMGACK | 0 to 14 | [0] | CTMG acknowledgment | Clause 7.1.2.3.2.11.1 | +| Reserved | | [119:1] | Reserved | 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. | | | | | + +An ACTMG frame shall be sent following a CTMG frame that has its IACKRQ field set to one (see clause 7.1.2.3.2.6.1) indicating that immediate acknowledgment is required. + +###### 7.1.2.3.2.11.1 CTMG acknowledgment (CTMGACK) + +The CTMGACK field shall indicate the correct reception of the previously received CTMG frame that requested an immediate acknowledgment (see clause 7.1.2.3.2.6.1). + +This field shall be set to one only if both the HCS of the core part and E\_HCS of the extended part (if present) of the PHY-frame header of the CTMG frame are correct. + +###### 7.1.2.3.2.12 Reserved + +Reserved by ITU-T. + +###### 7.1.2.3.2.13 Reserved + +Reserved by ITU-T. + +###### 7.1.2.3.2.14 Reserved + +Reserved by ITU-T. + +###### 7.1.2.3.2.15 Reserved + +Reserved by ITU-T. + +###### 7.1.2.3.2.16 FTE PHY-frame type specific fields + +This frame type is used for adding additional frame types (i.e., frame type extension). + +Table 7-50 lists the PHY-frame header fields which are specific to the FTE frame type. + +**Table 7-50 – FTE PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-------------------------------------------------------------------------------------------------------------|---------|--------|------------------------|--------------------------| +| FTE_DUR | 0 and 1 | [15:0] | Duration for FTE frame | Clause 7.1.2.3.2.16.1 | +| CURRTS | 2 | [6:0] | Current TS | Clause 7.1.2.3.2.16.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| EFT_FLD | 3 to 14 | [95:0] | EFT specific fields | Clause 7.1.2.3.2.16.2 | +| NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. | | | | | + +###### 7.1.2.3.2.16.1 Duration for FTE frame (FTE\_DUR) + +The FTE\_DUR field shall contain the duration of a single PHY frame sequence in multiples of 0.25 µs. It shall be represented as a 16-bit unsigned integer. This field shall only be present if DRI = 1. + +###### 7.1.2.3.2.16.2 EFT specific fields (EFT\_FLD) + +This clause describes the fields that are specific to FTE frame type. The first field shall be a fixed-length subfield that identifies an extended frame type (EFT). The size of the EFT and other fields following the EFT are for further study. + +###### 7.1.2.3.2.16.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +###### 7.1.2.3.2.17 Maximum actual PSD of MAP frame (APSD\_MAX-MAP\_LSB and APSD\_MAX-MAP\_MSB) + +The APSD\_MAX-MAP\_LSB, APSD\_MAX-MAP\_MSB and the APSD\_MAX-MAP\_EXT fields shall together indicate the APSD\_MAX for the MAP PHY frame. It shall be represented as a 6-bits unsigned integer with valid values in the range from 0 to 50, plus special values 62 and 63. Values from 0 to 50 correspond to an APSD\_MAX in the range of -50 dBm/Hz to -100 dBm/Hz in 1 dB steps. + +The most significant 2 bits of the APSD\_MAX-MAP are conveyed in the APSD\_MAX-MAP\_MSB field, and the least significant 4 bits of the APSD\_MAX are conveyed in the APSD\_MAX-MAP\_LSB and the APSD\_MAX-MAP\_EXT: 3 bits in the APSD\_MAX-MAP\_LSB and 1 bit in the APSD\_MAX-MAP\_EXT, as shown in Figure 7-4.1. + +![Figure 7-4.1: APSD MAX-MAP bits mapping diagram. It shows a 6-bit word structure with MSB on the left and LSB on the right. The word is divided into three fields: APSD-MAX-MAP_MSB (2 bits), APSD-MAX-MAP_LSB (3 bits), and APSD-MAX-MAP_EXT (1 bit).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +| | | | | | +|------------------------------|--|------------------------------|--|-----------------------------| +| MSB | | | | LSB | +| APSD-MAX-MAP_MSB
(2 bits) | | APSD-MAX-MAP_LSB
(3 bits) | | APSD-MAX-MAP_EXT
(1 bit) | + +G.9960(18)-Cor.2(20)\_F7-4.1 + +Figure 7-4.1: APSD MAX-MAP bits mapping diagram. It shows a 6-bit word structure with MSB on the left and LSB on the right. The word is divided into three fields: APSD-MAX-MAP\_MSB (2 bits), APSD-MAX-MAP\_LSB (3 bits), and APSD-MAX-MAP\_EXT (1 bit). + +**Figure 7-4.1 – APSD MAX-MAP bits mapping** + +The special values 62 and 63 shall indicate that the frame has been transmitted with an APSD\_MAX that is the minimum of: + +- Highest value of the transmit PSD allowed (i.e., TxPSD after applying PSD ceiling if applicable) +- Highest value of the PSD that the node is capable of transmitting. + +All other values are reserved by ITU-T. + +##### 7.1.2.3.3 Extended header fields + +The extended part of the PHY-frame header is PHYH bits long and shall be composed of a common part and a variable part. The common part shall contain fields that are common to all PHY frame types. The variable part shall contain fields according to the PHY frame type. PHY frame type shall be indicated by the FT field in the core part of the PHY-frame header. The PAD fields shall fit the length of the header of different PHY frame types to the standard values of PHYH bits. The content of the extended part shall be protected by the 16-bit header check sequence (E\_HCS). + +The fields of the extended part of the PHY-frame header are defined in Table 7-51. + +**Table 7-51 – Extended part of PHY-frame header** + +| Field | Octet | Bits | Description | | +|--------|-----------|---------|--------------------------------------------|---------------| +| E_FTSF | 0 to 18 | [151:0] | Extended header frame-type specific fields | Variable part | +| E_HCS | 19 and 20 | [15:0] | Extended header check sequence | Common part | + +###### 7.1.2.3.3.1 Extended header frame-type specific fields (E\_FTSF) + +###### 7.1.2.3.3.1.1 E\_FTSF for a CTMG PHY frame + +Table 7-52 lists the E\_FTSF for a CTMG PHY frame. + +**Table 7-52 – E\_FTSF for a CTMG PHY frame type** + +| Field | Octet | Bits | Description | Reference | +|-----------|---------|---------|---------------------|------------------------| +| CTMGD_EXT | 0 to 18 | [151:0] | CTMG data extension | Clause 7.1.2.3.3.1.1.1 | + +###### 7.1.2.3.3.1.1.1 CTMG data extension (CTMGD\_EXT) + +This field is the extension of the CTMGD field. It shall be coded as described in clause 7.1.2.3.2.6.2. + +###### 7.1.2.3.3.1.2 E\_FTSF for a BMSG PHY frame + +Table 7-53 lists the E\_FTSF for a BMSG PHY frame. + +**Table 7-53 – E\_FTSF for a BMSG PHY frame type** + +| Field | Octet | Bits | Description | Reference | +|-------------------------------------------------------------------------------------------------------------|------------|---------|----------------------------------------|--------------------------| +| RXRST_DATA | 0
and 1 | [0] | Data RX reset flag | Clause 7.1.2.3.3.1.2.1 | +| RXRST_MNGMT | | [1] | Management RX reset flag | Clause 7.1.2.3.3.1.2.2 | +| FLCTRLT | | [2] | Flow control type | Clause 7.1.2.3.3.1.2.3 | +| FLCTRL | | [7:3] | Flow control | Clause 7.1.2.3.3.1.2.4 | +| Reserved | | [8] | Reserved | Reserved by ITU-T (Note) | +| FLCTRL_CONN | | [9] | Flow control connection flag | Clause 7.1.2.3.3.1.2.5 | +| Reserved | | [15:10] | Reserved | Reserved by ITU-T (Note) | +| ACKDATA_BM | 2 to 13 | [90:0] | Acknowledgement data of the BMSG frame | Clause 7.1.2.3.3.1.2.6 | +| Reserved | | [95:91] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 14 to 18 | [39:0] | Reserved | 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.1.2.3.3.1.2.1 Data RX reset flag (RXRST\_DATA) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.5, the RXRST\_DATA field of the ACK frame. + +###### 7.1.2.3.3.1.2.2 Management RX reset flag (RXRST\_MNGMT) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.6, RXRST\_MNGMT field of the ACK frame. + +###### 7.1.2.3.3.1.2.3 Flow control type (FLCTRLT) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.2, the FLCTRLT field of the ACK frame. + +###### 7.1.2.3.3.1.2.4 Flow control (FLCTRL) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.3, the FLCTRL field of the ACK frame. + +###### 7.1.2.3.3.1.2.5 Flow control connection flag (FLCTRL\_CONN) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.1, the FLCTRL\_CONN field of the ACK frame. + +###### 7.1.2.3.3.1.2.6 Acknowledgement data of the BMSG frame (ACKDATA\_BM) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.9, the ACKDATA/MCACK\_D field of the ACK frame for unicast acknowledgment (MI = 0). + +###### 7.1.2.3.3.1.3 E\_FTSF for a BACK PHY frame + +Table 7-54 lists the E\_FTSF for a BACK PHY frame. + +**Table 7-54 – E\_FTSF for a BACK PHY frame type** + +| Field | Octet | Bits | Description | Reference | +|-------------|------------|---------|----------------------------------------|--------------------------| +| RXRST_DATA | 0
and 1 | [0] | Data RX reset flag | Clause 7.1.2.3.2.10.21 | +| RXRST_MNGMT | | [1] | Management RX reset flag | Clause 7.1.2.3.2.10.22 | +| FLCTRLT | | [2] | Flow control type | Clause 7.1.2.3.2.10.23 | +| FLCTRL | | [7:3] | Flow control | Clause 7.1.2.3.2.10.24 | +| Reserved | | [8] | Reserved | Reserved by ITU-T (Note) | +| FLCTRL_CONN | | [9] | Flow control connection flag | Clause 7.1.2.3.2.10.25 | +| Reserved | | [15:10] | Reserved | Reserved by ITU-T (Note) | +| ACKDATA_BA | 2 to 13 | [90:0] | Acknowledgement data of the BACK frame | Clause 7.1.2.3.2.10.26 | +| Reserved | | [95:91] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 14 to 18 | [39:0] | Reserved | 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.1.2.3.3.1.3.1 Data RX reset flag (RXRST\_DATA) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.5, the RXRST\_DATA field of the ACK frame. + +###### 7.1.2.3.3.1.3.2 Management RX reset flag (RXRST\_MNGMT) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.6, the RXRST\_MNGMT field of the ACK frame. + +###### 7.1.2.3.3.1.3.3 Flow control type (FLCTRLT) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.2, the FLCTRLT field of the ACK frame. + +###### 7.1.2.3.3.1.3.4 Flow control (FLCTRL) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.3, the FLCTRL field of the ACK frame. + +###### 7.1.2.3.3.1.3.5 Flow control connection flag (FLCTRL\_CONN) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.1, the FLCTRL\_CONN field of the ACK frame. + +###### 7.1.2.3.3.1.3.6 Acknowledgement data of the BACK frame (ACKDATA\_BA) + +The interpretation of this field shall be as specified in clause 7.1.2.3.2.3.9, the ACKDATA/MCACK\_D field of the ACK frame for unicast acknowledgment (MI = 0). + +###### 7.1.2.3.3.1.4 E\_FTSF for ACK PHY-frame + +Table 7-54.1 lists the E\_FTSF for ACK PHY frame. + +**Table 7-54.1 – E\_FTSF for ACK PHY frame type** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|----------------------|----------------------------------| +| ACKI_EXT | 0 to 17 | [143:0] | ACKI field extension | Clause 7.1.2.3.3.1.4.1 | +| Reserved | 18 | [7:0] | Reserved | Reserved for use by ITU-T G.9991 | + +###### 7.1.2.3.3.1.4.1 ACKI field extension (ACKI\_EXT) + +This field is the extension of the ACKI field, and shall be concatenated to the ACKI field of the core part of the PHY-frame header of the ACK frame before decoding the reception status of data units as described in clause 7.1.2.3.2.3.9.1.7. + +###### 7.1.2.3.3.2 Extended header check sequence (E\_HCS) + +The E\_HCS field is intended for verification of the extended part of the PHY-frame header. The E\_HCS is a 16-bit cyclic redundancy check (CRC) and shall be computed over all the fields of the E\_FTSF in the order that they are transmitted, starting with the LSB of the first field and ending with the MSB of the last field of E\_FTSF. The same polynomial as specified in clause 7.1.2.3.1.9 shall be used. + +### 7.1.3 Physical medium attachment (PMA) sublayer + +The functional model of the PMA is presented in Figure 7-5. It is intended to describe in more detail the PMA functional block presented in Figure 7-1. + +In the transmit direction, the incoming PHY frame (except for preamble and channel estimation symbols) at the $\alpha$ -reference point has a format as defined in clause 7.1.2. Both the header bits and the payload bits of the incoming frame are scrambled as described in clause 7.1.3.1. The header bits of the incoming frame are encoded as described in clause 7.1.3.4. The payload bits are encoded, as described in clause 7.1.3.3. The parameters of payload encoder are controlled by the PHY management entity. + +After encoding, the header and payload are each segmented into an integer number of symbol frames as described in clause 7.1.3.5.1. The obtained symbol frames of the header and the payload are submitted to the PMD (at the $\delta$ -reference point) for modulation and transmission over the medium. + +In the receive direction, all necessary inverse operations of decoding, and de-scrambling are performed on the received symbol frames. The recovered PHY-frame header and payload are submitted to the $\alpha$ -reference point for further processing in the PCS. + +![Functional model of PMA sublayer diagram showing TX and RX PHY frame processing paths. TX path: TX PHY frame -> Scrambler -> Header FEC encoder and repetition encoder / Payload FEC encoder and repetition encoder -> Multiplexing (TDM) -> Segmentation to OFDM symbols -> TX symbol frames. RX path: RX symbol frames -> De-scrambler Header decoder Payload decoder Pad removal -> RX PHY frame. PHY management block is connected to both Scrambler and De-scrambler via PHY control data lines. Reference points alpha and delta are marked.](c6212a3b14736d6a8c81ace75ae94ccf_img.jpg) + +Functional model of PMA sublayer diagram showing TX and RX PHY frame processing paths. TX path: TX PHY frame -> Scrambler -> Header FEC encoder and repetition encoder / Payload FEC encoder and repetition encoder -> Multiplexing (TDM) -> Segmentation to OFDM symbols -> TX symbol frames. RX path: RX symbol frames -> De-scrambler Header decoder Payload decoder Pad removal -> RX PHY frame. PHY management block is connected to both Scrambler and De-scrambler via PHY control data lines. Reference points alpha and delta are marked. + +Figure 7-5 – Functional model of PMA sublayer + +#### 7.1.3.1 Scrambling + +All data starting from the first bit of the PHY-frame header (PFH) and ending by the last bit of the payload shall be scrambled with a pseudorandom sequence generated by the linear feedback shift register (LFSR) with the polynomial $p(x) = x^{23} + x^{18} + 1$ , as shown in Figure 7-6. + +![Scrambler diagram showing a 23-bit LFSR with cells C1 to C23. Data in is XORed with the output of C23 to produce Data out. The LFSR is initialized with PHY header bits (0 1 0 1 0 1 ... 1 0 1 0 1 0) and Payload bits (SI 1 1 ... 1 1 1 1 1 1).](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +| | | | | | | | | | | | | | | +|------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|-------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| +| | C 1 | C 2 | C 3 | C 4 | C 5 | C 6 | ----- | C 18 | C 19 | C 20 | C 21 | C 22 | C 23 | +| Initialization
PHY header | 0 | 1 | 0 | 1 | 0 | 1 | ----- | 1 | 0 | 1 | 0 | 1 | 0 | +| Payload | SI | | 1 | 1 | ----- | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | + +Scrambler diagram showing a 23-bit LFSR with cells C1 to C23. Data in is XORed with the output of C23 to produce Data out. The LFSR is initialized with PHY header bits (0 1 0 1 0 1 ... 1 0 1 0 1 0) and Payload bits (SI 1 1 ... 1 1 1 1 1 1). + +Figure 7-6 – Scrambler; $p(x) = x^{23} + x^{18} + 1$ + +The LFSR generator shall be initialized at the first bit of the header with the initialization vector equal to $2\text{AAAAA}_{16}$ (where the LSB corresponds to $C_1$ ); this initialization is used for the scrambling of the header data. If the SI field in the PHY-frame header is not equal to zero, a second initialization shall be performed for payload data, immediately after the last bit of the header is read from the scrambler and before the first bit of the payload is read from the scrambler. For the second initialization, the first four bits of the LFSR ( $C_1$ to $C_4$ ) shall be set to the value of SI (scrambler initialization), while all other bits $C_5$ to $C_{23}$ shall be initialized to 1. The value of $SI = C_4C_3C_2C_1$ is communicated in the header as described in clause 7.1.2.3. + +The first bit to be scrambled shall be XOR'ed with the first bit generated by the LFSR after initialization (i.e., $C_{18} \oplus C_{23}$ of the initialization vector). See Annex G for examples. + +The special value $0_{16}$ for SI indicates that the scrambler is not re-initialized between the header and payload. The initialization of the SI field to values other than the special value is optional. + +NOTE – The method for generating SI values is beyond the scope of this Recommendation. + +#### 7.1.3.2 FEC encoding + +The FEC encoding scheme is shown in Figure 7-7. The scheme consists of a systematic QC-LDPC-BC encoder and a puncturing mechanism. The parameters of the FEC encoding scheme are: + +- the number of incoming information bits, $K$ (information block of bits); +- the number of coded bits, $N_M$ (coded block of bits); +- the number of parity-check bits, $N_M - K$ ; +- the number of output bits, $N_{FEC} \leq N_M$ , (FEC codeword, whose size depends on the puncturing pattern); +- the mother code rate, $R_M = K/N_M$ , defined as the code rate before puncturing; +- the code rate, $R = K/N_{FEC}$ , defined as the code rate after puncturing. + +The information block size shall be one of the values specified in Table 7-56. + +![Figure 7-7 – FEC encoder block diagram. An input 'K-bit information block' enters an 'LDPC-BC encoder' block. The output of this block is a 'N_M bits coded block' consisting of 'K information bits + N_M - K parity-check bits'. This block then enters a 'Puncturing' block. The output of the puncturing block is 'N_FEC bits' labeled as 'FEC codeword'. A small label 'G9960(10)_F7-7' is present below the diagram.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +Figure 7-7 – FEC encoder block diagram. An input 'K-bit information block' enters an 'LDPC-BC encoder' block. The output of this block is a 'N\_M bits coded block' consisting of 'K information bits + N\_M - K parity-check bits'. This block then enters a 'Puncturing' block. The output of the puncturing block is 'N\_FEC bits' labeled as 'FEC codeword'. A small label 'G9960(10)\_F7-7' is present below the diagram. + +**Figure 7-7 – FEC encoder** + +The encoder shall support mother codes with rates $R_M = 1/2$ , $R_M = 2/3$ and $R_M = 5/6$ . From these mother codes, codes with higher code rates shall be obtained through puncturing, as described in clause 7.1.3.2.2. The puncturing block shall support patterns providing all code rates presented in Table 7-56. + +The codeword at the output of the puncturing block is of size $N_{FEC} \leq N_M$ . The bits shall be output in the ascending order of codeword indices determined by vector $\mathbf{v}'$ (see clause 7.1.3.2.2); with this order the first information bit input to the encoder will be the first at the output of the puncturing. + +##### 7.1.3.2.1 LDPC-BC encoder + +The code rate of the mother code, $R_M = K/N_M$ , is determined by a $(N_M - K) \times N_M$ size parity-check matrix $\mathbf{H}$ composed by an array of $c \times t$ circulant $b \times b$ sub-matrices $\mathbf{A}_{i,j}$ : + +$$\mathbf{H} = \begin{bmatrix} \mathbf{A}_{1,1} & \mathbf{A}_{1,2} & \cdots & \mathbf{A}_{1,t} \\ \mathbf{A}_{2,1} & \mathbf{A}_{2,2} & \cdots & \mathbf{A}_{2,t} \\ \vdots & \vdots & \ddots & \vdots \\ \mathbf{A}_{c,1} & \mathbf{A}_{c,2} & \cdots & \mathbf{A}_{c,t} \end{bmatrix}$$ + +The parameters $c, t$ ( $0 < c \leq t$ ) imply a rate $R_M = (t - c)/t$ . By selecting different sets of $c, t$ , different rates can be obtained. + +The sub-matrices $\mathbf{A}_{i,j}$ are either a rotated identity or a zero matrix and have a size of $b \times b$ , where parameter $b = N_M/t$ is called the expansion factor of $\mathbf{H}$ and controls the code block size, $N_M$ . + +The parity-check matrix, $\mathbf{H}$ , is described in its compact form: + +$$\mathbf{H}_c = \begin{bmatrix} a_{1,1} & a_{1,2} & \cdots & a_{1,t} \\ a_{2,1} & a_{2,2} & \cdots & a_{2,t} \\ \vdots & \vdots & \ddots & \vdots \\ a_{c,1} & a_{c,2} & \cdots & a_{c,t} \end{bmatrix}$$ + +A zero sub-matrix in position $(i,j)$ is labelled with $a_{i,j}=-1$ , and a rotated identity sub-matrix is labelled with a positive integer number $a_{i,j}$ defining the number of right column shifts of the identity matrix. + +This Recommendation defines one matrix for each mother code rate and block size. + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_H$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 336$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| -1 | -1 | -1 | 6 | -1 | -1 | 9 | 6 | -1 | -1 | 2 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 0 | -1 | -1 | -1 | 3 | -1 | 12 | 1 | -1 | -1 | 3 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 9 | 11 | -1 | -1 | 13 | -1 | -1 | 2 | 12 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 1 | -1 | -1 | 11 | -1 | -1 | 7 | -1 | -1 | -1 | 11 | -1 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 4 | 8 | -1 | -1 | -1 | -1 | -1 | 2 | 5 | 4 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 3 | 0 | -1 | -1 | 8 | -1 | -1 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 0 | 6 | -1 | -1 | -1 | -1 | 5 | 13 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 9 | -1 | -1 | 3 | -1 | -1 | 3 | 1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| 9 | 0 | 13 | -1 | -1 | 12 | -1 | -1 | 8 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| -1 | 5 | -1 | -1 | 1 | 4 | -1 | -1 | 5 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | +| -1 | -1 | -1 | 8 | -1 | -1 | 8 | -1 | -1 | 9 | 0 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| 10 | 11 | -1 | -1 | -1 | 3 | -1 | -1 | 0 | -1 | -1 | -1 | 4 | 8 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_S$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 1920$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 27 | -1 | -1 | -1 | 55 | 19 | -1 | 30 | -1 | -1 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 0 | -1 | 1 | -1 | 70 | -1 | 47 | -1 | 62 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 41 | -1 | -1 | -1 | 44 | -1 | -1 | 59 | 60 | 25 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 16 | 77 | -1 | -1 | 5 | -1 | 48 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 45 | -1 | 27 | -1 | 46 | 19 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 63 | -1 | -1 | -1 | 55 | -1 | -1 | -1 | 48 | 26 | 10 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 42 | -1 | 21 | -1 | 58 | -1 | 41 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 78 | 0 | -1 | 7 | 52 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | 29 | 9 | -1 | -1 | -1 | 37 | -1 | -1 | 35 | 21 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| -1 | -1 | 22 | 72 | -1 | -1 | 47 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | +| 35 | -1 | -1 | -1 | -1 | 13 | -1 | 35 | -1 | 70 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| -1 | 46 | 28 | -1 | -1 | -1 | 38 | -1 | -1 | -1 | 8 | -1 | 10 | 58 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_L$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 8640$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|----|-----|-----|-----|-----|----|-----|----|----|----|----|----|----|----|----|----|----| +| -1 | 34 | -1 | 95 | -1 | 279 | -1 | -1 | -1 | -1 | 248 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 0 | -1 | 0 | -1 | -1 | -1 | -1 | 134 | 356 | 275 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 51 | -1 | 27 | -1 | -1 | -1 | -1 | -1 | 22 | 152 | -1 | 57 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 124 | -1 | 290 | -1 | 281 | 15 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 340 | -1 | 99 | 336 | -1 | -1 | 1 | -1 | -1 | 67 | -1 | 33 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| 163 | -1 | 46 | -1 | -1 | -1 | -1 | -1 | -1 | 306 | -1 | 86 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | 185 | -1 | 24 | -1 | -1 | -1 | 94 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | 223 | -1 | 225 | 325 | -1 | -1 | -1 | -1 | -1 | 297 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| 46 | -1 | 314 | -1 | -1 | -1 | 59 | -1 | -1 | -1 | 120 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| -1 | -1 | 121 | -1 | -1 | -1 | 161 | -1 | 303 | -1 | 264 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | +| -1 | 303 | -1 | 8 | -1 | 185 | -1 | -1 | 138 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| -1 | -1 | 312 | -1 | -1 | -1 | 100 | -1 | -1 | 144 | -1 | 307 | 33 | 166 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $H_c$ of parity-check matrix $(2/3)_S$ corresponding to mother code with rate $R_M = 2/3$ ( $t = 24, c = 8$ ) and number of coded bits $N_M = 1440$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 49 | -1 | -1 | 21 | 31 | -1 | 57 | -1 | -1 | 19 | -1 | 29 | 2 | -1 | 19 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 7 | 22 | -1 | -1 | 37 | -1 | 32 | 10 | -1 | 26 | -1 | -1 | 59 | -1 | 48 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| 53 | -1 | -1 | 20 | 50 | -1 | -1 | 3 | 16 | -1 | 49 | -1 | -1 | 28 | 14 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | +| -1 | 58 | 23 | -1 | -1 | 15 | 54 | -1 | -1 | 5 | -1 | 18 | 49 | -1 | -1 | 13 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| 55 | -1 | -1 | 58 | -1 | 9 | -1 | 26 | 57 | -1 | 41 | -1 | 31 | -1 | 21 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| -1 | 10 | 49 | -1 | 59 | -1 | 7 | -1 | -1 | 30 | -1 | 18 | -1 | 48 | -1 | 7 | 59 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | +| 48 | -1 | -1 | 50 | 18 | -1 | -1 | 11 | 52 | -1 | 59 | -1 | -1 | 37 | -1 | 10 | 0 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| -1 | 24 | 16 | -1 | -1 | 0 | 53 | -1 | -1 | 41 | -1 | 38 | 51 | -1 | 58 | -1 | 59 | 8 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $H_c$ of parity-check matrix $(2/3)_L$ corresponding to mother code with rate $R_M = 2/3$ ( $t = 24, c = 8$ ) and number of coded bits $N_M = 6480$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|----|-----|----|----|----|----|----|----| +| 78 | -1 | -1 | 167 | 237 | -1 | 3 | -1 | 266 | -1 | -1 | 102 | 153 | -1 | -1 | 212 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 83 | 189 | -1 | -1 | 68 | -1 | 178 | -1 | 90 | 205 | -1 | -1 | 13 | 4 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | 226 | 147 | -1 | 46 | -1 | -1 | 76 | -1 | 116 | -1 | 211 | -1 | 112 | -1 | 118 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | +| 92 | -1 | -1 | 214 | -1 | 236 | 241 | -1 | 157 | -1 | 143 | -1 | 214 | -1 | 207 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| 144 | -1 | -1 | 258 | 264 | -1 | 53 | -1 | 114 | -1 | 172 | -1 | -1 | 82 | 262 | -1 | 62 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | +| -1 | 153 | 120 | -1 | -1 | 199 | -1 | 126 | -1 | 61 | -1 | 183 | 15 | -1 | -1 | 134 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | +| -1 | 100 | -1 | 141 | -1 | 36 | -1 | 17 | -1 | 156 | -1 | 124 | 162 | -1 | -1 | 57 | 0 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| 196 | -1 | 187 | -1 | 73 | -1 | 80 | -1 | 139 | -1 | 57 | -1 | -1 | 236 | 267 | -1 | 62 | 256 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $H_c$ of parity-check matrix $(5/6)_S$ corresponding to mother code with rate $R_M = 5/6$ ( $t = 24, c = 4$ ) and number of coded bits $N_M = 1152$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| -1 | 13 | 32 | 47 | 41 | 24 | -1 | 25 | 22 | 40 | 1 | 31 | 8 | 15 | 20 | 15 | 42 | 30 | 13 | 3 | -1 | 0 | -1 | -1 | +| 25 | 46 | 15 | 43 | 45 | 29 | 39 | 47 | 23 | 38 | 39 | 12 | -1 | 21 | -1 | 38 | 33 | 0 | 0 | -1 | 39 | 0 | 0 | -1 | +| 35 | 45 | 45 | 38 | 14 | 16 | 6 | 11 | -1 | 18 | 7 | 41 | 35 | 17 | 32 | 45 | 41 | -1 | 18 | 17 | 0 | -1 | 0 | 0 | +| 9 | 32 | 6 | 22 | 26 | 31 | 9 | 8 | 22 | 32 | 40 | 4 | 18 | 40 | 36 | -1 | -1 | 23 | 31 | 41 | 39 | 20 | -1 | 0 | + +The compact form $H_c$ of parity-check matrix $(5/6)_L$ corresponding to mother code with rate $R_M = 5/6$ ( $t = 24, c = 4$ ) and number of coded bits $N_M = 5184$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|----|----|----| +| -1 | 47 | 146 | 203 | 184 | 112 | -1 | 116 | 103 | 181 | 3 | 140 | 38 | 68 | 91 | 70 | 191 | 138 | 62 | 14 | -1 | 0 | -1 | -1 | +| 117 | 203 | 67 | 194 | 206 | 133 | 174 | 212 | 104 | 171 | 176 | 56 | -1 | 96 | -1 | 167 | 149 | 4 | 1 | -1 | 177 | 0 | 0 | -1 | +| 153 | 206 | 198 | 173 | 55 | 72 | 28 | 53 | -1 | 82 | 34 | 186 | 161 | 80 | 144 | 204 | 187 | -1 | 84 | 77 | 0 | -1 | 0 | 0 | +| 44 | 147 | 27 | 83 | 118 | 130 | 41 | 38 | 100 | 146 | 183 | 19 | 85 | 180 | 163 | -1 | -1 | 106 | 140 | 185 | 177 | 94 | -1 | 0 | + +###### 7.1.3.2.1.1 Encoding operation + +The encoder shall support the coded block sizes and rates presented in Table 7-56. The parity-check matrix $\mathbf{H}$ used to encode a block of information bits is selected according to the mother code indicated in Table 7-56. + +The encoding process shall be as follows: + +- 1) A group of incoming $K$ information bits $\mathbf{u} = [u_0, u_1, \dots, u_{K-1}]$ are collected and copied to the output of the encoder to form a block of systematic code bits. +- 2) $N_M - K$ parity-check bits, $\mathbf{p} = [p_0, \dots, p_{N_M - K - 1}]$ , are computed using the parity-check matrix $\mathbf{H}$ and the information block $\mathbf{u}$ . The resulting coded block $\mathbf{v} = [\mathbf{u} | \mathbf{p}]$ shall satisfy the parity check equations $\mathbf{vH}^T = \mathbf{0}$ . Here $\mathbf{0}$ is a zero row vector of dimension $N_M - K$ . +- 3) The $N_M - K$ parity check bits $\mathbf{p}$ are copied to the output of the encoder as a block of parity-check bits $\mathbf{p} = [p_0, \dots, p_{N_M - K - 1}]$ to form the output coded block $\mathbf{v} = [\mathbf{u} | \mathbf{p}] = [v_0, v_1, \dots, v_{N_M - 1}]$ . + +4) The output of the encoder **v** is the input to the puncturing block (see Figure 7-7). + +NOTE – One method of encoding is to determine a systematic generator matrix **G** from **H** such that **GH**T = **0**. A *K*-bit information block **u** = [*u*0, *u*1, ..., *u**K*-1] can be encoded by the systematic generator matrix **G** via the operation **v** = **uG** to become a *NM*-bit coded block **v** = [*v*0, *v*1, ..., *v**NM*-1] = [**u** | **p**], where **p** = [*p*0, ..., *p**NM*-*K*-1] are the parity-check bits. Encoding an LDPC code from **G** can be quite complex. However, the QC-LDPC-BC codes specified here are such that very low complexity encoding directly from **H** is possible. + +##### 7.1.3.2.2 Puncturing + +Puncturing shall discard some of the coded block bits to achieve a higher code rate (*R*). Puncturing is applied to both information and parity-check bits. The puncturing block uses the puncturing patterns specified in Table 7-55. The puncturing patterns are denoted as **pp***T*(*i*), where *T* is the length of the puncturing pattern and *i* is the number of zeros in the pattern. + +**Table 7-55 – Puncturing patterns** + +| | Puncturing pattern | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| pp 16 (0) | [1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1] | +| pp 1152 (72) | [ 1 1 ... 1 0 0 ... 0 1 1 ... 1 0 0 ... 0 ]
720                      36                      360                      36 | +| pp 5184 (324) | [ 1 1 ... 1 0 0 ... 0 1 1 ... 1 0 0 ... 0 1 1 ... 1 ]
3240                      162                      972                      162                      648 | +| pp 1152 (144) | [ 1 1 ... 1 0 0 ... 0 1 1 ... 1 0 0 ... 0 1 1 ... 1 ]
720                      48                      240                      96                      48 | +| pp 5184 (648) | [ 0 0 ... 0 1 1 ... 1 0 0 ... 0 1 1 ... 1 ]
216                      4320                      432                      216 | + +NOTE – The pattern **pp**16(0) does not result in any code rate changes and is introduced to be consistent with the puncturing notation. + +The coded block **v** input to the puncturing block shall be processed using the puncturing pattern **pp***T*(*i*) as follows: + +For the pattern **pp***T*(*i*) = [**pp**0(*i*), ..., **pp***T*-1(*i*)], the puncturing block shall omit all incoming coded bits *vt*, *t* = 0, ..., *NM* - 1 for which **pp***t* mod *T*(*i*) = 0. Hence, the resulting output FEC codeword will be **v'** = [*v'*0, *v'*1, ..., *v'**NFEC*-1] with *NFEC* ≤ *NM*. + +##### 7.1.3.2.3 FEC encoding parameters + +The FEC encoding scheme shall support the encoding parameters specified in Table 7-56. + +**Table 7-56 – FEC encoding parameters** + +| | Code rate, $R$ | Information block size, $K$ | Puncturing pattern, $pp$ | Mother code matrix | FEC codeword size, $N_{FEC}$ | +|-------------|----------------|-----------------------------|--------------------------|--------------------|------------------------------| +| For header | 1/2 | PHY H = 168 | $pp_{16}^{(0)}$ | $(1/2)_H$ | 336 | +| For payload | 1/2 | 960 | $pp_{16}^{(0)}$ | $(1/2)_S$ | 1920 | +| | 1/2 | 4320 | $pp_{16}^{(0)}$ | $(1/2)_L$ | 8640 | +| | 2/3 | 960 | $pp_{16}^{(0)}$ | $(2/3)_S$ | 1440 | +| | 2/3 | 4320 | $pp_{16}^{(0)}$ | $(2/3)_L$ | 6480 | +| | 5/6 | 960 | $pp_{16}^{(0)}$ | $(5/6)_S$ | 1152 | +| | 5/6 | 4320 | $pp_{16}^{(0)}$ | $(5/6)_L$ | 5184 | +| | 16/18 | 960 | $pp_{1152}^{(72)}$ | $(5/6)_S$ | 1080 | +| | 16/18 | 4320 | $pp_{5184}^{(324)}$ | $(5/6)_L$ | 4860 | +| | 20/21 | 960 | $pp_{1152}^{(144)}$ | $(5/6)_S$ | 1008 | +| | 20/21 | 4320 | $pp_{5184}^{(648)}$ | $(5/6)_L$ | 4536 | + +#### 7.1.3.3 Payload encoding + +The functional model of the payload encoder is presented in Figure 7-8. It contains an FEC encoder and a payload repetition encoder (PRE) to support robust communication mode (RCM). + +![Functional diagram of the payload encoder (set to normal mode). The diagram shows 'Payload bits' entering a box labeled 'FEC encoder'. The output of the FEC encoder is 'FEC codeword (N_FEC)'. This codeword then enters a large box labeled 'Payload encoder'. Inside this box, the codeword splits into two paths: one goes through a 'Payload repetition encoder' and the other goes through a 'Normal mode' block. Both paths converge to the output 'Encoded payload block'. A small label 'G.9960(10)_F7-8' is at the bottom right.](901755bf86813427f3a32efa0363a27c_img.jpg) + +Functional diagram of the payload encoder (set to normal mode). The diagram shows 'Payload bits' entering a box labeled 'FEC encoder'. The output of the FEC encoder is 'FEC codeword (N\_FEC)'. This codeword then enters a large box labeled 'Payload encoder'. Inside this box, the codeword splits into two paths: one goes through a 'Payload repetition encoder' and the other goes through a 'Normal mode' block. Both paths converge to the output 'Encoded payload block'. A small label 'G.9960(10)\_F7-8' is at the bottom right. + +**Figure 7-8 – Functional diagram of the payload encoder (set to normal mode)** + +The incoming PHY-frame payload shall be divided into sequential blocks of information bits, $K$ bits per block. Each block of information bits shall be encoded by the FEC, as described in clause 7.1.3.2. The valid values of $K$ , the coded block size $N_{FEC}$ , and the coding rate $R$ , are presented in Table 7-56. The bits of each information block shall be in the same order as they are in the payload; the payload bit to be transmitted first shall be the first in the corresponding information block. + +In normal mode of operation, indicated by REP = 001 in the PHY-frame header, PRE is disabled. The FEC codewords shall be passed directly to the output of the payload encoder and concatenated into + +the encoded payload block; their order shall be the same as the order of corresponding information blocks at the input of the payload encoder. + +In the case of RCM, each FEC codeword is further encoded by the PRE, as described in clause 7.1.3.3.1. The PRE-encoded FEC codewords are concatenated into the encoded payload block as defined in clause 7.1.3.3.1. + +##### 7.1.3.3.1 Payload repetition encoding + +Payload repetition encoder (PRE) shall support the number of repetitions $N_{REP}$ specified in Table 7-8. The used number of repetitions shall be advertised in the REP field in the PHY-frame header. + +The PRE shall operate as follows. Each incoming FEC codeword shall be first copied $N_{REP}$ times. Each copy shall be divided into $S$ sections, numbered from 0 to $S-1$ , with $B$ bits in each section, as follows: + +- Bits of the FEC codeword shall be mapped into sections in ascending sequential order; the bit of the FEC codeword to be transmitted first shall be the first bit ( $b_0$ ) of Section 0. +- If after all bits of the FEC codeword are mapped, the last $q$ bit positions of the last section remain empty, these positions shall be filled by the first $q$ bits of Section 0 in ascending sequential order. + +Mapping of an FEC codeword on to sections is shown in Figure 7-9. + +![Diagram illustrating the mapping of an FEC codeword onto sections. The diagram shows an FEC codeword of N_FEC bits being divided into S sections (SEC 0, SEC 1, ..., SEC S-1). Each section contains B bits. The first bit of the codeword (b_0) is mapped to the first bit of SEC 0. The last q bits of the codeword are mapped to the last q bits of SEC S-1. A red arrow labeled 'q-bits filling' shows the mapping of the last q bits of the codeword to the first q bits of SEC 0.](b71ad9fc874230de9ba4480e12a216f7_img.jpg) + +The diagram shows a horizontal bar at the top representing the 'FEC codeword' of length $N_{FEC}$ bits. Below it, several boxes represent sections: 'SEC 0', 'SEC 1', an ellipsis, and 'SEC S-1'. Each section is labeled with 'B bits'. Vertical arrows point from the codeword to the sections, indicating the sequential mapping of bits. A red curved arrow labeled 'q-bits filling' originates from the end of the codeword and points to the beginning of 'SEC 0', illustrating that the last $q$ bits of the codeword fill the end of 'SEC S-1' and then wrap around to the start of 'SEC 0'. + +Diagram illustrating the mapping of an FEC codeword onto sections. The diagram shows an FEC codeword of N\_FEC bits being divided into S sections (SEC 0, SEC 1, ..., SEC S-1). Each section contains B bits. The first bit of the codeword (b\_0) is mapped to the first bit of SEC 0. The last q bits of the codeword are mapped to the last q bits of SEC S-1. A red arrow labeled 'q-bits filling' shows the mapping of the last q bits of the codeword to the first q bits of SEC 0. + +**Figure 7-9 – Mapping of an FEC codeword on to sections** + +If $\text{floor}(k_P/N_{REP})$ is divisible by 4, the number of bits per section shall be set to $B = \text{floor}(k_P/N_{REP}) - 1$ ; otherwise, it shall be set to $B = \text{floor}(k_P/N_{REP})$ , where $k_P$ is the total number of bits that can be loaded on to the payload OFDM symbol according to the current BAT. The number of sections per FEC codeword is: $S = \text{ceiling}(N_{FEC}/B)$ . + +If the computed value of $S$ is 1, $H$ consecutive FEC codewords may be concatenated. The number of sections in this case shall be: $S = \text{ceil}(H \times N_{FEC}/B)$ , where $H$ is selected to provide $S > 1$ for the given values of $N_{FEC}$ , $N_{REP}$ and $k_P$ . Concatenation of codewords may only be applied when an FEC information block size of 960 is used. The total size of the concatenated codewords shall not exceed the maximum FEC codeword size. + +PRE parameters $N_{REP}$ and $H$ shall be selected such that $q < H \times N_{FEC}$ . + +If the number of FEC codewords in the payload is not a multiple of $H$ , the necessary $z < H$ dummy FEC codewords shall be added. These dummy codewords shall be copies of the last FEC codeword of the same payload. The values of $H$ (1, 2 and 4) and $z$ (0 to $H-1$ ) are indicated in the FCF field of the PHY-frame header (see Table 7-9). + +The PRE shall output sections sequentially, in groups of $S$ sections. Each group carries a copy of the FEC codeword. The number of groups per each FEC codeword is $N_{REP}$ . The order of bits in each section shall be the same as these bits appear in the incoming FEC codeword. + +The format of the encoded payload block with PRE enabled is presented in Figure 7-10. The total number of sections in the encoded payload block is $N_{REP} \times S$ . + +![Diagram of the encoded payload block structure. The top part shows a horizontal bar labeled 'Encoded payload block' containing 'PRE-encoded FEC codeword #1 (N_REP repetitions)', 'PRE-encoded FEC codeword #2 (N_REP repetitions)', an ellipsis, and 'PRE-encoded FEC codeword #J (N_REP repetitions)'. Below this, three groups of sections are shown: 'Group #1 of S sections (FEC copy #1)' containing sections 0, 1, ..., S-1; 'Group #2 of S sections (FEC copy #2)' containing sections CSS2, (CSS2 + 1) mod S, ...; and 'Group #N_REP of S sections (FEC copy #N_REP)' containing sections CSS_NREP, (CSS_NREP + 1) mod S, ... . Lines connect the first and last codewords to their respective section groups. A small label 'G.9960(10)_F7-10' is at the bottom right.](2b60ebe01f77d22e53da1fbe73083b01_img.jpg) + +Diagram of the encoded payload block structure. The top part shows a horizontal bar labeled 'Encoded payload block' containing 'PRE-encoded FEC codeword #1 (N\_REP repetitions)', 'PRE-encoded FEC codeword #2 (N\_REP repetitions)', an ellipsis, and 'PRE-encoded FEC codeword #J (N\_REP repetitions)'. Below this, three groups of sections are shown: 'Group #1 of S sections (FEC copy #1)' containing sections 0, 1, ..., S-1; 'Group #2 of S sections (FEC copy #2)' containing sections CSS2, (CSS2 + 1) mod S, ...; and 'Group #N\_REP of S sections (FEC copy #N\_REP)' containing sections CSS\_NREP, (CSS\_NREP + 1) mod S, ... . Lines connect the first and last codewords to their respective section groups. A small label 'G.9960(10)\_F7-10' is at the bottom right. + +**Figure 7-10 – The format of the encoded payload block +(payload consists of $J$ FEC codewords)** + +The order of sections in the first group shall be ascending, from 0 to $S-1$ ; the order of sections in all subsequent groups shall be cyclically shifted. The shift is defined by the cyclic section shift (CSS) vector $\{0, CSS_2, CSS_3, \dots, CSS_{N_{REP}}\}$ with a length of $N_{REP}$ , where $CSS_L$ is the sequential number of the section to be transmitted first in the $L$ th group of sections. The value of CSS shall be computed using the following rule: + +For $N_{REP} = 2$ : + +| | | +|----------------------|--------------| +| if $(S \bmod 2) = 0$ | CSS:= {0,1}; | +| else | CSS:= {0,0}; | + +For $N_{REP} = 4$ : + +| | | +|---------------------------|------------------| +| if $(S \bmod 4) = 0$ | CSS:= {0,1,2,3}; | +| else if $(S \bmod 2) = 0$ | CSS:= {0,0,1,1}; | +| else | CSS:= {0,0,0,0}; | + +For $N_{REP} = 3$ : + +| | | +|----------------------|----------------| +| if $(S \bmod 3) = 0$ | CSS:= {0,1,2}; | +| else | CSS:= {0,0,0}; | + +For $N_{REP} = 6$ : + +| | | +|---------------------------|----------------------| +| if $(S \bmod 6) = 0$ | CSS:= {0,1,2,3,4,5}; | +| else if $(S \bmod 3) = 0$ | CSS:= {0,0,1,1,2,2}; | +| else if $(S \bmod 2) = 0$ | CSS:= {0,0,0,1,1,1}; | +| else | CSS:= {0,0,0,0,0,0}; | + +For $N_{REP} = 8$ : + +| | | +|---------------------------|--------------------------| +| if $(S \bmod 8) = 0$ | CSS:= {0,1,2,3,4,5,6,7}; | +| else if $(S \bmod 4) = 0$ | CSS:= {0,0,1,1,2,2,3,3}; | +| else if $(S \bmod 2) = 0$ | CSS:= {0,0,0,0,1,1,1,1}; | + +else + +CSS := {0,0,0,0,0,0,0,0}; + +NOTE – As an example, with CSS = 3L for a group of $S = 4$ sections, these sections will be transmitted in the following order: 3, 0, 1, 2. The first group of sections, for comparison, is transmitted: 0, 1, 2, 3. + +#### 7.1.3.4 Header encoder + +The functional model of the header encoder is presented in Figure 7-11. It contains an FEC encoder and a header repetition encoder (HRE). + +![Functional diagram of the header encoder. The diagram shows a block labeled 'Header encoder' containing two sub-blocks: 'Header FEC encoder' and 'Header repetition encoder'. An arrow labeled 'Header bits' enters the 'Header FEC encoder' from the left. An arrow exits the 'Header FEC encoder' and enters the 'Header repetition encoder'. An arrow exits the 'Header repetition encoder' and is labeled 'Encoded header block'. The text 'G.9960(10)_F7-11' is written below the diagram.](d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg) + +Functional diagram of the header encoder. The diagram shows a block labeled 'Header encoder' containing two sub-blocks: 'Header FEC encoder' and 'Header repetition encoder'. An arrow labeled 'Header bits' enters the 'Header FEC encoder' from the left. An arrow exits the 'Header FEC encoder' and enters the 'Header repetition encoder'. An arrow exits the 'Header repetition encoder' and is labeled 'Encoded header block'. The text 'G.9960(10)\_F7-11' is written below the diagram. + +**Figure 7-11 – Functional diagram of the header encoder** + +The bits of the PHY-frame header shall be input into the header FEC encoder in their original order and encoded as described in clause 7.1.3.2. The size of the FEC codeword and the coding rate of the header FEC encoder are described in Table 7-56. + +The FEC codeword enters the HRE. The HRE shall operate as follows: + +- The FEC codeword shall be first copied $M$ times, where $M = \text{ceiling}(k_H/N_{FEC})$ , $k_H$ is the number of bits to be loaded on to the OFDM symbol carrying the header. +- The first encoded header block shall be formed by concatenation of $M$ copies of the header FEC encoder output. The bits ( $b_i$ ) within each codeword shall be cyclically shifted by 2 bits as follows: + - The 1st FEC codeword copy shall be formed as $\{b_0, b_1, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}\}$ . + - The 2nd FEC codeword copy shall be formed as $\{b_2, b_3, \dots, b_{N_{FEC}-1}, b_0, b_1\}$ . + - The 3rd FEC codeword copy shall be formed as $\{b_4, b_5, \dots, b_{N_{FEC}-1}, b_0, b_1, b_2, b_3\}$ . + - ... + - The $M$ th FEC codeword copy, where $M > 3$ , shall be formed as $\{b_{(2 \times M-2)}, b_{(2 \times M-1)}, \dots, b_{N_{FEC}-1}, b_0, b_1, \dots, b_{(2 \times M-4)}, b_{(2 \times M-3)}\}$ . +- The second encoded header block shall be formed by cyclic shifting of each copy by $N_{FEC}/2$ bits and concatenation of $M$ copies of the shifted FEC codeword. The bits ( $b_i$ ) within each codeword shall be cyclically shifted by 2 bits as follows: + - The 1st FEC codeword copy shall be formed as $\{b_{N_{FEC}/2}, b_{N_{FEC}/2+1}, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}, b_0, b_1, \dots, b_{N_{FEC}/2-2}, b_{N_{FEC}/2-1}\}$ . + - The 2nd FEC codeword copy shall be formed as $\{b_{N_{FEC}/2+2}, b_{N_{FEC}/2+3}, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}, b_0, b_1, \dots, b_{N_{FEC}/2}, b_{N_{FEC}/2+1}\}$ . + - The 3rd FEC codeword copy shall be formed as $\{b_{N_{FEC}/2+4}, b_{N_{FEC}/2+5}, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}, b_0, b_1, \dots, b_{N_{FEC}/2+2}, b_{N_{FEC}/2+3}\}$ . + - ... + - The $M$ th FEC codeword copy, where $M > 3$ , shall be formed as $\{b_{N_{FEC}/2+(2 \times M-2)}, b_{N_{FEC}/2+(2 \times M-1)}, \dots, b_{N_{FEC}-1}, b_0, b_1, \dots, b_{N_{FEC}/2+(2 \times M-4)}, b_{N_{FEC}/2+(2 \times M-3)}\}$ . + +NOTE – Since the coding rate used for header encoding is 1/2, the number of bits in the FEC codeword is always even, and the number of bits in the encoded header block is even. + +#### 7.1.3.5 Segmentation into symbol frames + +The encoded payload block from the output of payload encoder and the encoded header block from the output of the header encoder shall be segmented into symbol frames. The maximum number of bits in the symbol frame shall not exceed the values of $k_P$ for payload symbol frames and $k_H$ for header symbol frames. Payload and header symbol frames shall be passed to the PMD, as described in Figure 7-5. + +##### 7.1.3.5.1 Payload segmentation + +The encoded payload block shall be segmented into one or more symbol frames. + +In normal mode, the first symbol frame shall contain the first $k_P$ bits of the encoded payload block, the second frame shall contain the second $k_P$ bits of the encoded payload block and so on, until the last symbol frame. If the number of bits in the last symbol frame is less than $k_P$ , the unloaded supported subcarriers of the OFDM symbol for the last symbol frame shall be modulated by a pseudorandom sequence of bits, as described in clause 7.1.4.2.6. Payload segmentation is illustrated in Figure 7-12. + +In RCM, the first symbol frame shall contain the first $N_{REP}$ sections of the encoded payload block, the second frame shall contain the second $N_{REP}$ sections of the encoded payload block, and so on, until the last symbol frame. If the number of bits in $N_{REP}$ sections is less than $k_P$ , the unloaded supported subcarriers of the corresponding OFDM symbols shall be modulated by a pseudorandom sequence of bits, as described in clause 7.1.4.2.6. + +![Diagram illustrating payload segmentation. A 'Payload block' is shown at the top, divided into segments of 'k_p bits'. Below it, 'Symbol frame 1', 'Symbol frame 2', and 'Symbol frame M' are shown, each containing 'k_p bits'. An arrow labeled 'Unloaded SSCs' points to the right side of the payload block. The diagram is labeled 'G.9960(10)_F7-12'.](b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg) + +The diagram shows a 'Payload block' at the top, which is segmented into multiple 'Symbol frames' below. The first two symbol frames are labeled 'Symbol frame 1' and 'Symbol frame 2', and the last one is 'Symbol frame M'. Each symbol frame contains a segment of $k_p$ bits. Above the symbol frames, the payload block is divided into segments of $k_p$ bits. An arrow labeled 'Unloaded SSCs' points to the right side of the payload block. The diagram is labeled 'G.9960(10)\_F7-12'. + +Diagram illustrating payload segmentation. A 'Payload block' is shown at the top, divided into segments of 'k\_p bits'. Below it, 'Symbol frame 1', 'Symbol frame 2', and 'Symbol frame M' are shown, each containing 'k\_p bits'. An arrow labeled 'Unloaded SSCs' points to the right side of the payload block. The diagram is labeled 'G.9960(10)\_F7-12'. + +Figure 7-12 – Payload segmentation + +##### 7.1.3.5.2 Header segmentation + +The encoded header block shall be segmented into $D$ symbol frames (valid values of $D$ are 1 and 2). Selection of the value of $D$ is determined by the domain master (see clause 8.6.7 of [ITU-T G.9961]), indicated in the PHY-frame header (see clause 7.1.2.3.1.8) and in the TXOP descriptor (see Table 8-65 in [ITU-T G.9961]). + +The first $k_H$ bits of the first encoded header block shall be mapped into the first symbol frame of the header, so that $b_0$ is transmitted first. + +If $D = 2$ , the first $k_H$ bits of the second encoded header block shall be mapped into the second symbol frame of the header, so that $b_{N_{FEC}/2}$ is transmitted first. + +The rest of the bits of the first and the second encoded header blocks shall be discarded. + +Header segmentation is illustrated in Figure 7-13. + +![Figure 7-13 – Header segmentation. The diagram shows two header symbol frames, 'Header symbol frame 1' and 'Header symbol frame 2'. Each frame contains a 'Header block' of k_H bits and M 'Header FEC codeword copy' blocks. Bit positions are indicated at the top: bit 0, bit 2, bit 2M-4, and bit 2M-2 for the first frame, and bit N_FEC/2, bit N_FEC/2+2, bit N_FEC/2+2M-4, and bit N_FEC/2+2M-2 for the second frame. A small note 'G.9960(10)_F7-13' is at the bottom right.](dae88eec6d1005984029b794ff8b7a9e_img.jpg) + +Figure 7-13 – Header segmentation. The diagram shows two header symbol frames, 'Header symbol frame 1' and 'Header symbol frame 2'. Each frame contains a 'Header block' of k\_H bits and M 'Header FEC codeword copy' blocks. Bit positions are indicated at the top: bit 0, bit 2, bit 2M-4, and bit 2M-2 for the first frame, and bit N\_FEC/2, bit N\_FEC/2+2, bit N\_FEC/2+2M-4, and bit N\_FEC/2+2M-2 for the second frame. A small note 'G.9960(10)\_F7-13' is at the bottom right. + +**Figure 7-13 – Header segmentation** + +#### 7.1.3.6 PROBE frame + +The PROBE frame is intended for the channel estimation procedure. The header of the PROBE frame shall be as defined in clause 7.1.2.3 and its subclauses. The payload of the PROBE frame contains a number of probe symbols, i.e., symbol frames with no data, which can be of two types, as specified in clause 7.1.4.2.5.3: + +- Silent probe symbols, for which all subcarriers are considered MSCs (masked subcarriers). +- Channel estimation probe symbols, for which all supported subcarriers (SSCs) are considered inactive subcarriers (ISCs) and are modulated by a pseudorandom sequence. + +The number of probe symbols in each frame shall be indicated via the PRBSYM field in clause 7.1.2.3.2.7.1.3. + +Two probe frame types are specified and identified by the PRBTYPE field specified in clause 7.1.2.3.2.7.1.2 (Table 7-40): + +- The "Silent PROBE frame" (PRBTYPE 00002). The payload of this frame type is composed of silent symbols. +- The "Channel estimation PROBE frame" (PRBTYPE 00012). The payload of this frame type is composed of channel estimation probe symbols. + +### 7.1.4 Physical medium dependent (PMD) sublayer + +The functional model of the PMD is presented in Figure 7-14. In the transmit direction, the tone mapper divides the incoming symbol frames of the header and payload into groups of bits and associates each group of bits with a specific subcarrier on to which this group shall be loaded, as specified in clause 7.1.4.2. The constellation encoder converts each incoming group of bits into a complex number that represents the constellation point for this subcarrier. The constellation mapping process is described in clause 7.1.4.3.1. The unloaded supported subcarriers are modulated by a pseudorandom bit sequence generated as described in clause 7.1.4.2.6. + +![Functional model of the PMD diagram showing TX and RX symbol frame processing paths, including bit generators, tone mappers, constellation mappers, scramblers, modulators, and a medium-specific AFE connected to the MDI and Medium. It also shows PHY management and PMD control data interfaces.](d1ad05f1189b0d80188fee24ae33c112_img.jpg) + +The diagram illustrates the functional model of the PMD. It is divided into two main sections: TX (Transmit) and RX (Receive) symbol frame processing, separated by a dashed line labeled $\delta$ -reference point. + +TX path: TX symbol frames enter from the top and are processed by a Tone mapper. Simultaneously, a Bit generator for unused subcarriers provides input to a Constellation mapper and scaler. The output of the Tone mapper also goes to this mapper. The mapper's output goes to a Constellation scrambler, which also receives input from a Preamble generation block. The scrambler's output goes to an OFDM modulator. The output of the OFDM modulator goes to a Medium-specific AFE. The Medium-specific AFE also receives input $F_{UC}$ and is connected to the MDI (Media Dependent Interface) and the Medium. + +RX path: RX symbol frames enter from the top and are processed by a Symbol frames recovery block, which contains a Constellation decoder, a Demodulator, and a Preamble processing and carrier sense generation block. The output of the Preamble processing block goes to the PHY management. The output of the Demodulator goes to the Medium-specific AFE. + +Control: PMD control data is shown being exchanged between the PHY management and the Medium-specific AFE. + +Reference: G.9960(15) F7-14 + +Functional model of the PMD diagram showing TX and RX symbol frame processing paths, including bit generators, tone mappers, constellation mappers, scramblers, modulators, and a medium-specific AFE connected to the MDI and Medium. It also shows PHY management and PMD control data interfaces. + +**Figure 7-14 – Functional model of the PMD** + +The OFDM modulator (clause 7.1.4.4) converts the stream of the $N$ complex numbers at its input into the stream of $N$ complex valued time-domain samples. After adding the preamble, the transmit signal is up-shifted by $F_{US}$ . For RF applications, the transmit signal is further up-converted by $F_{UC}$ to fit the required spectrum of the transmit signal. The real part of the resultant signal is transmitted on to the medium. Parameters of the preamble (clause 7.1.4.5) are determined by the PHY management and depend on the type of the transmitted PHY frame. + +Frames are output on to the medium with inter-frame gaps. + +In the receive direction, the frames incoming from the medium are demodulated and decoded. The recovered symbol frames are transferred to the PMA via the $\delta$ -reference point. The preamble is processed and preamble data are passed to the PHY management entity. + +#### 7.1.4.1 Subcarrier spacing and indexing + +The subcarrier spacing $F_{SC}$ is the frequency spacing between any two adjacent subcarriers. Valid values of subcarrier spacing are presented in Table 7-67. + +The physical index $i$ corresponds to the order of subcarriers in ascending frequency. The subcarrier with physical index $i$ shall be centred at frequency $f = F_{UC} + F_{US} - (N/2 - i) \times F_{SC}$ . The index $i$ goes from 0 to $N - 1$ . + +The logical index $j$ indicates the order in which data is loaded on subcarriers. The index $j$ goes from 0 to $N - 1$ . + +Two indexing rules that relate the physical index and the logical index are defined: + +Rule #1: $i=j$ , i.e., the subcarriers are loaded in order of ascending frequency. + +The subcarrier with logical index $j$ shall be centred at frequency $f = F_{UC} + F_{US} - (N/2 - j) \times F_{SC}$ . + +Rule #2: $i = N/2 + j/2$ for even values of $j$ , $i = N/2 - (j + 1)/2$ for odd values of $j$ . + +The subcarriers with even logical indices from $j = 0$ to $j = N - 2$ shall be centred at frequencies $f = F_{UC} + F_{US} + (j/2) \times F_{SC}$ while those with odd logical indices from $j = 1$ to $j = N - 1$ shall be centred at frequencies $f = F_{UC} + F_{US} - ((j + 1)/2) \times F_{SC}$ . + +Logical indexing rules shall be applied in accordance with the domain type and the operational frequency band, as specified in Tables 6-1, 6-4 and 6-6 of [ITU-T G.9964]. Throughout the Recommendation, the term "subcarrier index" refers to the physical index, unless otherwise noted. + +Not all subcarriers may always be used for data transmission; some of them have to be switched off in special circumstances. Others may be only used with reduced power. The latter functions are performed by subcarrier masking and gain scaling (see clauses 5.1 and 5.2 of [ITU-T G.9964]). + +NOTE – The particular subcarriers used for data transmission between two particular nodes depend on channel characteristics, such as loop attenuation and noise, and on the specific spectrum-use requirements, such as notching of amateur radio bands; some subcarriers may be subject to PSD reduction, e.g., at high and low frequencies to share the medium with other services. + +#### 7.1.4.2 Tone mapper + +The tone mapper divides the incoming symbol frames of the header and payload into groups of bits (according to the BATs and subcarrier grouping being used) and associates each group of bits with specific subcarriers on to which these groups shall be loaded. This information along with subcarrier-specific gain scaling values as described in clause 7.1.4.3.2.3 are passed to the constellation encoder. + +##### 7.1.4.2.1 Summary of subcarrier types + +For the purpose of tone mapping, the following types of subcarriers are defined. + +- 1) Masked subcarriers (MSCs) are those on which transmission is not allowed, i.e., the gain on this subcarrier shall be set to zero. Two types of MSC are defined: + - Permanently masked subcarriers (PMSCs) – those that are never allowed for transmission. The list of PMSC forms a PMSC mask, which depends on the type of medium and is defined in clause 7.2. Data bits are never mapped on PMSC. + - Regionally masked subcarriers (RMSMs) – those that are not allowed for data transmission in some regions, while may be allowed in other regions. The list of RMSM forms a RMSM mask, which depends on the type of media and on the region/application. The RMSM set consists of the subcarriers corresponding to subcarrier masks defined in SM descriptor and masked amateur radio bands defined in amateur radio band descriptor (see clause 8.8.5.5 of [ITU-T G.9961]). The number of RMSMs, $\#RMSM = \#MSC - \#PMSC$ . +- 2) Supported subcarriers (SSCs) are those on which transmission is allowed under restrictions of the relevant PSD mask. The number of SSCs, $\#SSC = N - \#MSC$ . The following types of SSC are defined: + - Active subcarriers (ASCs) – those that have loaded bits ( $b \geq 1$ ) for data transmission. ASCs are subject to constellation point mapping, constellation scaling and constellation scrambling as described in clause 7.1.4.3. Data bits shall be mapped on ASCs as described in clause 7.1.4.2.2. + - Inactive subcarriers (ISCs) – those that do not have any data bits loaded (e.g., because SNR is low). The number of ISCs, $\#ISC = \#SSC - \#ASC$ . ISCs can be used for measurement purposes or other auxiliary purposes. ISCs are subject to transmit power shaping. The signals transmitted on ISC are defined in clause 7.1.4.2.6. + +##### 7.1.4.2.2 Bit allocation tables (BATs) + +Tone mapping is defined by a bit allocation table (BAT) that associates subcarrier indices with the number of bits to be loaded on the subcarrier. + +The BATs used by the node in the particular PHY frame shall be indicated to the receiving node(s) in the BAT\_ID field of the MSG PHY-frame type specific fields of the PHY-frame header, as described in clause 7.1.2.3.2.2.8. Up to 32 BATs with BAT\_ID values in the range from 0 to 31 can be defined. One or more BAT\_IDs can be assigned for each destination (per unicast or multicast DID, see clause 7.1.2.3.1.5). The assignment of BAT\_IDs shall be as shown in Table 7-57. + +**Table 7-57 – Assignment of BAT\_ID** + +| BAT_ID | Type of BAT | Reference | +|---------|---------------------------------------|--------------------| +| 0 | Predefined, Type 0 | Clause 7.1.4.2.2.1 | +| 1 | Predefined, Type 1 | | +| 2 | Predefined, Type 2 | | +| 3 | Predefined, Type 3 | | +| 4 to 7 | Reserved by ITU-T for predefined BATs | | +| 8 to 31 | Reserved by ITU-T for runtime BATs | Clause 7.1.4.2.2.2 | + +Every node shall support at least predefined BATs of Type 0, Type 1, Type 2 and Type 3. Support of other BATs is profile-dependent. + +###### 7.1.4.2.2.1 Predefined BATs + +The following predefined BATs are defined: + +- 1) Predefined BAT Type 0: uniform 1-bit loading on all subcarriers except the PMSC set. +- 2) Predefined BAT Type 1: uniform 2-bit loading on all subcarriers except the PMSC set. +- 3) Predefined BAT Type 2: uniform 2-bit loading on all subcarriers except the PMSC and the RMSM sets (a complete SSC set). +- 4) Predefined BAT Type 3: uniform 1-bit loading on all subcarriers except the PMSC set and the RMSM sets (a complete SSC set). + +NOTE – Predefined BAT Type 0, Type 1, Type 2, and Type 3 may be used when channel characteristics are unknown (i.e., no knowledge is available on whether particular subcarriers could be loaded with bits or not). + +###### 7.1.4.2.2.2 Runtime BATs + +A runtime BAT associates indices of SSCs with the number of bits to be loaded on each subcarrier. The subset of indices in the BAT with the number of loaded bits $b > 0$ identifies the ASC. Runtime BAT can be defined by the receiving node (receiver-defined BAT) or selected by the transmitting node (transmitter-determined BAT) for a specific unicast or multicast channel. Runtime BATs shall be communicated from the node that generates the BAT to the peer (e.g., a node sourcing multicast transmission to several other nodes will communicate the BAT to all receiving nodes prior to sending data) (see clauses 8.11 and 8.16 of [ITU-T G.9961]). + +The number of bits loaded on any subcarrier shall not exceed the maximum number of bits allowed (see clause 7.1.4.3). The number of bits shall also meet the bit loading capabilities of the communicating nodes, as advertised by them prior to communication. + +##### 7.1.4.2.3 Transmitter-determined and receiver-determined mapping + +Two types of tone mapping are defined: transmitter-determined and receiver-determined. With transmitter-determined mapping, the BAT is defined by the transmitter and shall be either a predefined BAT or it shall be communicated to all destination nodes prior to transmission using the channel estimation protocol for unicast transmission (see clause 8.11 of [ITU-T G.9961]) and in addition using the multicast binding protocol for multicast transmission (see clause 8.16 of + +[ITU-T G.9961]). With receiver-determined mapping, the BAT is defined by the receiver of the destination node and communicated to the transmitter using the channel estimation protocol. + +For unicast transmission, the node shall use either one of the predefined BATs (transmitter-determined) or a BAT defined by the receiver of the destination node for the PHY frame. For multicast transmission both predefined BATs (transmitter-determined) and runtime BATs can be used. If a runtime BAT is used, it shall be defined by the node sourcing the multicast (transmitter-determined); this node shall generate the BAT and communicate it to all multicast destinations (see clauses 8.11 and 8.16 of [ITU-T G.9961]). + +Both transmitter-determined and receiver-determined BATs may be defined that are valid for only specific portions of the MAC cycle. The portion of the MAC cycle for which a specific BAT is valid for is called a BAT region. In the case of receiver-determined BATs, the applicable BAT region(s) including the starting point and ending point of each of the BAT regions with respect to the MAC cycle are conveyed to the transmitter as a part of the channel estimation protocol. + +![Figure 7-15: A diagram showing an AC line cycle (50/60 Hz) and a MAC cycle (33.3/40 ms) for power line communication. The AC cycle is represented by a sine wave. The MAC cycle is a horizontal line segment spanning two AC cycles. The diagram is divided into four regions by vertical dashed lines, labeled T1, T2, T1, and T2 from left to right. T1 regions are centered around the peaks of the AC cycle, and T2 regions are centered around the zero crossings. The label 'G.9960(10)_F7-15' is in the bottom right corner.](df942da5e715e03b194b733d9f5998ad_img.jpg) + +Figure 7-15: A diagram showing an AC line cycle (50/60 Hz) and a MAC cycle (33.3/40 ms) for power line communication. The AC cycle is represented by a sine wave. The MAC cycle is a horizontal line segment spanning two AC cycles. The diagram is divided into four regions by vertical dashed lines, labeled T1, T2, T1, and T2 from left to right. T1 regions are centered around the peaks of the AC cycle, and T2 regions are centered around the zero crossings. The label 'G.9960(10)\_F7-15' is in the bottom right corner. + +**Figure 7-15 – An example of BAT regions in a MAC cycle for power line** + +Figure 7-15 illustrates multiple BAT regions for a power line when the MAC cycle duration is two AC cycles. In this example, the BAT regions are periodic about half AC line cycle and it has two BATs. BAT T1 is used around the peaks of the AC line cycle and BAT T2 is used around the zero crossings of the AC line cycle. The receiver shall inform the transmitter about the starting point and the ending point of each of the BAT regions with respect to the MAC cycle as a part of the channel estimation protocol. + +A node shall support both transmitter-determined and receiver-determined types of mapping, with the minimum number of simultaneously supported BATs depending on the profile. + +##### 7.1.4.2.4 BAT with subcarrier grouping + +A node shall be capable of defining any runtime BAT using a subcarrier grouping of $G = 1$ (no grouping), 2, 4, 8, and 16 subcarriers with subsequent frequencies. The default value of $G = 1$ . If grouping is used ( $G > 1$ ), all subcarriers of the same group shall use the same bit loading. The first group shall include $G$ subcarriers in ascending order of subcarrier indices defined in clause 7.1.4.1. If a group includes subcarriers that are masked (i.e., MSC) or extends beyond the applicable subcarrier set, the node shall apply the bit loading assigned for this group only to the applicable subcarrier set (i.e., SSC). + +The group index $G$ shall be indicated when the BAT is communicated (see clause 8.11 of [ITU-T G.9961]). Additional methods for BAT compression are for further study. + +##### 7.1.4.2.5 Special mappings + +###### 7.1.4.2.5.1 Tone mapping for PHY-frame header + +The PHY-frame header shall use a uniform loading of two bits per subcarrier on all subcarriers except the PMSC set. + +###### 7.1.4.2.5.2 Tone mapping for RCM + +Payload transmission in robust communication mode (RCM) shall use predefined BAT types with uniform two bits per subcarrier loading. + +###### 7.1.4.2.5.3 Tone mapping for the probe symbols + +Two types of probe symbols are specified: silent symbols and channel estimation probe symbols. Tone mapping shall apply to these symbols according to the following: + +- For silent symbols, all subcarriers shall be considered as MSCs (masked subcarriers). +- Channel estimation probe symbols shall be modulated using a uniform loading of two bits per subcarrier on all SSC sets. For these probe symbols, the ISC set shall be equal to the SSC set. All ISC subcarriers shall be modulated by a pseudorandom sequence of bits, as described in clause 7.1.4.2.6. + +###### 7.1.4.2.5.4 Tone mapping for ACE symbols + +The ACE symbol shall be modulated using a uniform loading of two bits per subcarrier on all SSC sets. For the ACE, ISC = SSC. All ISC subcarriers shall be modulated by a pseudorandom sequence of bits, as described in clause 7.1.4.2.6. + +##### 7.1.4.2.6 Modulation of unloaded supported subcarriers + +Supported subcarriers (SSCs) that are not loaded with encoded payload bits or that are partially loaded with encoded payload bits – that is, ISC and unloaded or partially loaded ASC (herein referred to as unloaded SSC) – shall be loaded with a pseudorandom sequence defined by the linear feedback shift register (LFSR) generator with the polynomial $p(x) = x^{23} + x^{18} + 1$ shown in Figure 7-16. The LFSR generator shall be initialized at the beginning of each OFDM symbol with a DM-generated seed received during registration of the node into the domain through the UnloadedSubcarrierInitialSeed field of the additional domain information auxiliary information field (see clause 8.8.5.15). The $i$ -th payload symbol shall use the seed $S_k$ where $k$ is equal to $(i-1, \text{ modulo } 64) + 1$ , where $i = 1, 2, 3, 4, \dots$ . $S_k$ is generated by advancing the LFSR by $8192^{*(k-1)}$ from the original DM-generated seed. An example of LFSR seeds for an initial seed of $7\text{FFFFF}_{16}$ is provided in Table 7-58. + +NOTE – Seeds $S_1$ to $S_{64}$ are used to initialize the LFSR for payload symbols 1-64, 65-128 and so on. The LSB of the seed $S_k$ corresponds to $c_1$ . + +The DM-generated seed shall be chosen among the pool of allowed seeds described in Table 7-57.1, depending on the value of the DOD of the domain. + +**Table 7-57.1 – Pool of allowed DM-generated seeds for unloaded supported subcarriers LFSR generator** + +| DOD | Allowed seeds | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 7FFFF 16 ; 003FE0 16 ; 7FC060 16 ; 7803F9 16 ; 0FF813 16 ; 7EFE80 16 ; 01FCFC 16 ; 40202F 16 ; 038638 16 | +| 1 | 7FFFF 16 ; 7DC2E0 16 ; 70874D 16 ; 401FB7 16 ; 61F327 16 ; 0F78B3 16 ; 3FDFD7 16 ; 0DC513 16 ; 1E73E7 16 | +| 2 | 7FFFF 16 ; 1EB138 16 ; 731F9B 16 ; 057B41 16 ; 4DE53C 16 ; 7099A3 16 ; 0080A6 16 ; 07BC5A 16 ; 0399C8 16 | +| 3 | 7FFFF 16 ; 3027C4 16 ; 1F8F1B 16 ; 30A762 16 ; 1D8A1F 16 ; 6FB79B 16 ; 6E3675 16 ; 78B9A1 16 ; 65F92E 16 | +| 4 | 7FFFF 16 ; 5EED10 16 ; 7F3F09 16 ; 16E6B5 16 ; 5FD0FF 16 ; 1EB13C 16 ; 6B8DD5 16 ; 7795D2 16 ; 3D222E 16 | +| 5 | 7FFFF 16 ; 0174B0 16 ; 79903D 16 ; 604F7B 16 ; 38638D 16 ; 698A2D 16 ; 7CE688 16 ; 50281F 16 ; 48E4C4 16 | +| 6 | 7FFFF 16 ; 7ABE59 16 ; 785321 16 ; 26D2B1 16 ; 0207F8 16 ; 0B6CAA 16 ; 306764 16 ; 096B52 16 ; 12757B 16 | +| 7 | 7FFFF 16 ; 734122 16 ; 1D29EE 16 ; 4D67BC 16 ; 073961 16 ; 763502 16 ; 7C58CE 16 ; 7B4816 16 ; 5E6F90 16 | +| 8 | 7FFFF 16 ; 0AFC72 16 ; 198299 16 ; 5AABBE 16 ; 1E8EDC 16 ; 618E01 16 ; 6E289F 16 ; 5B22F8 16 ; 416B07 16 | +| 9 | 7FFFF 16 ; 771574 16 ; 779791 16 ; 5D54B7 16 ; 479BCE 16 ; 1EBBF8 16 ; 09EBF4 16 ; 6926AD 16 ; 3B5461 16 | +| 10 | 7FFFF 16 ; 06764F 16 ; 2EC96F 16 ; 3BFA45 16 ; 316B09 16 ; 6876D1 16 ; 7FEF7B 16 ; 0ABF31 16 ; 600E3B 16 | +| 11 | 7FFFF 16 ; 5295BF 16 ; 3C064C 16 ; 48FB34 16 ; 272E4D 16 ; 32203C 16 ; 478CF6 16 ; 7330FC 16 ; 098416 16 | +| 12 | 7FFFF 16 ; 40E0C4 16 ; 6A49F1 16 ; 620823 16 ; 44153E 16 ; 3BD438 16 ; 0878EA 16 ; 57EB86 16 ; 3DA277 16 | +| 13 | 7FFFF 16 ; 12CF23 16 ; 730171 16 ; 164544 16 ; 1AB7C9 16 ; 74191A 16 ; 33A4AA 16 ; 68843A 16 ; 3CC639 16 | +| 14 | 7FFFF 16 ; 1A6FB3 16 ; 068AF6 16 ; 79DC09 16 ; 2E8D44 16 ; 0733A1 16 ; 24E0D0 16 ; 3F4001 16 ; 1D56D2 16 | +| 15 | 7FFFF 16 ; 68BC83 16 ; 612F91 16 ; 6E76A9 16 ; 51F4FC 16 ; 2B2C4D 16 ; 2C2B62 16 ; 05A54A 16 ; 28476E 16 | + +The first allowed value is common for all DODs and is called the default value for the unloaded supported subcarriers LFSR generator. + +The LFSR shall be advanced by two bits for each subcarrier (for both SSC and MSC) of each symbol of the payload. Two LFSR bits corresponding to the subcarrier index 0 are ( $c_1, c_2$ ) of the initialization seed. Two LFSR bits corresponding to the subcarrier index 1 are ( $c_1, c_2$ ) after two shifts, and so on. For modulation of unloaded subcarriers, ACE symbols shall be treated in the same manner as payload symbols. + +![Diagram of an LFSR for modulation of unloaded and partially loaded subcarriers. It shows a sequence of cells C1, C2, followed by a gap, then C16, C17, C18, C19, C20, C21, C22, C23. Above the cells, a feedback loop with an XOR gate (+) takes inputs from C22 and C23 and feeds back into C1. A bracket labeled 'Lower m bits used for padding' covers C1 and C2. Below the cells, an 'Initialization: (First payload symbol)' row shows bits 1, 1, followed by a gap, then 1, 1, 1, 1, 1, 1, 1, 1. Arrows point from this initialization row to the cells C1, C2, C16, C17, C18, C19, C20, C21, C22, C23. The diagram is labeled G.9960(10)_F7-16.](886963464425186f4a465fa8155d2a3c_img.jpg) + +Diagram of an LFSR for modulation of unloaded and partially loaded subcarriers. It shows a sequence of cells C1, C2, followed by a gap, then C16, C17, C18, C19, C20, C21, C22, C23. Above the cells, a feedback loop with an XOR gate (+) takes inputs from C22 and C23 and feeds back into C1. A bracket labeled 'Lower m bits used for padding' covers C1 and C2. Below the cells, an 'Initialization: (First payload symbol)' row shows bits 1, 1, followed by a gap, then 1, 1, 1, 1, 1, 1, 1, 1. Arrows point from this initialization row to the cells C1, C2, C16, C17, C18, C19, C20, C21, C22, C23. The diagram is labeled G.9960(10)\_F7-16. + +**Figure 7-16 – LFSR for modulation of unloaded and partially loaded subcarriers** + +**Table 7-58 – Example LFSR seeds for an initial DM-generated seed of 7FFFF16** + +| Seed index $k$ | Seed ( $S_k$ ) | +|----------------|----------------------| +| 1 | 7FFFF 16 | +| 2 | 26B489 16 | +| 3 | 278A91 16 | + +**Table 7-58 – Example LFSR seeds for an initial DM-generated seed of 7FFFFFF16** + +| Seed index k | Seed ( Sk ) | +|---------------------|-------------------------------| +| 4 | 15F4ED 16 | +| 5 | 5B4CB1 16 | +| 6 | 2F021F 16 | +| 7 | 7A64C1 16 | +| 8 | 414CD7 16 | +| 9 | 649D5E 16 | +| 10 | 134826 16 | +| 11 | 2A3DFC 16 | +| 12 | 2B9570 16 | +| 13 | 3C6777 16 | +| 14 | 757986 16 | +| 15 | 103962 16 | +| 16 | 0DB87B 16 | +| 17 | 076287 16 | +| 18 | 3E1A31 16 | +| 19 | 05DE6D 16 | +| 20 | 5C5B4E 16 | +| 21 | 596413 16 | +| 22 | 0613D9 16 | +| 23 | 19504A 16 | +| 24 | 50FDE0 16 | +| 25 | 5CD048 16 | +| 26 | 66C646 16 | +| 27 | 7169B3 16 | +| 28 | 480497 16 | +| 29 | 053FE3 16 | +| 30 | 51F1B1 16 | +| 31 | 7D2BA0 16 | +| 32 | 11E4D8 16 | +| 33 | 037144 16 | +| 34 | 278587 16 | +| 35 | 2CF7F7 16 | +| 36 | 027D46 16 | +| 37 | 70A7EB 16 | +| 38 | 4C622C 16 | +| 39 | 54DC68 16 | +| 40 | 01715E 16 | +| 41 | 274A7B 16 | +| 42 | 55238D 16 | + +**Table 7-58 – Example LFSR seeds for an initial DM-generated seed of 7FFFFFF16** + +| Seed index $k$ | Seed ( $S_k$ ) | +|----------------|----------------------| +| 43 | 008B06 16 | +| 44 | 3FA255 16 | +| 45 | 777A6A 16 | +| 46 | 5154DD 16 | +| 47 | 55C203 16 | +| 48 | 0D21F9 16 | +| 49 | 1BEDE6 16 | +| 50 | 608D6B 16 | +| 51 | 4B75D3 16 | +| 52 | 22BA64 16 | +| 53 | 7D0646 16 | +| 54 | 7F56E6 16 | +| 55 | 614333 16 | +| 56 | 4F1368 16 | +| 57 | 7359EF 16 | +| 58 | 2D86A9 16 | +| 59 | 25373D 16 | +| 60 | 258466 16 | +| 61 | 4CE92A 16 | +| 62 | 6B7E3D 16 | +| 63 | 760B34 16 | +| 64 | 761EA6 16 | + +The modulation of subcarriers that are not loaded with encoded payload bits shall be as follows: + +- 1) Starting at the beginning of the first payload OFDM symbol, each subcarrier from the ISC set shall be modulated with the two bits which are the LSBs of the LFSR, $c_1$ , and $c_2$ using the 2-bit constellation mapping defined in clause 7.1.4.3.1.1 ( $c_1$ is transmitted first). +- 2) In every OFDM symbol of payload, if the number of bits in the symbol frame does not fill the entire symbol, the bits from the LFSR shall be used to fill the remainder of the symbol frame, by taking the sequential groups of $m$ LSBs of the LFSR and mapping them on to the remaining subcarriers so that LSB of LFSR is transmitted first and in the order defined by the current BAT, where $m$ is the number of bits allocated for that subcarrier by the BAT. For the first padded subcarrier, if $n$ bits of the $m$ loaded bits are data bits ( $n < m$ ), these $n$ data bits shall be loaded as the LSBs of the group of bits mapped on the constellation point, and the $m - n$ bits of the LFSR shall be used as the MSBs of the group of bits mapped on the constellation point starting from LSB of LFSR. +- 3) In the case of a PROBE frame, starting at the beginning of the first payload OFDM symbol, each subcarrier from the ISC set shall be modulated with the two bits which are the LSBs of the LFSR, $c_1$ and $c_2$ , using 2-bit constellation mapping defined in clause 7.1.4.3.1.1 ( $c_1$ is transmitted first). + +The bits from LFSR are loaded on subcarriers in the order of logical indices (i.e., in the same way as data is loaded over payload symbols), according to subcarrier indexing defined in clause 7.1.4.1. + +Modulation of unloaded subcarriers shall start from the unloaded SSC with the lowest logical index of the first payload symbol, continue in ascending order of logical indices until the unloaded SSC with the highest logical index of the first payload symbol, continue with the unloaded SSC with the lowest logical index of the second payload symbol, continue in ascending order of logical indices until the unloaded SSC with the highest logical index of the second payload symbol, and continue until the unloaded SSC with the highest logical index of the last payload symbol. + +The ASCs from the SSC set are loaded according to the corresponding BAT as defined in clause 7.1.4.2.2. + +#### 7.1.4.3 Constellation encoder + +##### 7.1.4.3.1 Constellation mapping + +Constellation mapping associates every group of bits loaded on to a subcarrier, with the values of *I* (in-phase component) and *Q* (quadrature-phase component) of a constellation diagram. Each incoming group of *b* bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be associated with a specific value of *I* and *Q* computed as described in this clause. + +Each group of bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be mapped on to the constellation mapper with the LSB bit, *d*0, first. + +###### 7.1.4.3.1.1 Constellations for even number of bits + +If the number of bits, *b*, loaded on to the subcarrier is even (2, 4, 6, 8, 10, 12), square-shaped constellations with mappings described in this clause shall be used. Support of all the specified even order constellations (2, 4, 6, 8, 10 and 12) shall be mandatory at both the transmitter and the receiver. With square-shaped constellations, $2^b$ constellation points are set as a square, and $2^{b-2}$ points reside in each quadrant with odd values (positive or negative) of *I* and *Q*. + +Constellation and mapping for *b* = 2 shall be as presented in Figure 7-17 and described in Table 7-59. + +![Figure 7-17: Constellation diagram for b=2 (QPSK). The diagram shows a square constellation in the I-Q plane. The horizontal axis is labeled 'I' and has tick marks at -3, -1, 1, and 3. The vertical axis is labeled 'Q' and has tick marks at -3, -1, 1, and 3. Four points are plotted: '10' at (-1, 1), '11' at (1, 1), '00' at (-1, -1), and '01' at (1, -1). A small label 'G.9960(10)_F7-17' is present in the bottom right corner of the plot area.](ee6ac2449928fabca567921acb078fc0_img.jpg) + +Figure 7-17: Constellation diagram for b=2 (QPSK). The diagram shows a square constellation in the I-Q plane. The horizontal axis is labeled 'I' and has tick marks at -3, -1, 1, and 3. The vertical axis is labeled 'Q' and has tick marks at -3, -1, 1, and 3. Four points are plotted: '10' at (-1, 1), '11' at (1, 1), '00' at (-1, -1), and '01' at (1, -1). A small label 'G.9960(10)\_F7-17' is present in the bottom right corner of the plot area. + +Figure 7-17 – Constellation and mapping for *b* = 2 + +Table 7-59 – Mapping for *b* = 2 (QPSK) + +| Bit d 0 | I | Bit d 1 | Q | +|---------------------------|----------|---------------------------|----------| +| 0 | -1 | 0 | -1 | +| 1 | 1 | 1 | 1 | + +Constellation mapping for *b* = 4 shall be as described in Table 7-60. The first quadrant of the mapping is presented in Figure 7-18. + +![Figure 7-18: Constellation diagram for b=4 (first quadrant). The horizontal axis is labeled 'I' with values +1 and +3. The vertical axis is labeled 'Q' with values +1 and +3. Four points are plotted: (1, 3) labeled 0111, (3, 3) labeled 0101, (1, 1) labeled 1111, and (3, 1) labeled 1101. A small label 'G.9960(10)_F7-18' is at the bottom right.](efedc464aaba06e85f269d26c98fee90_img.jpg) + +Figure 7-18: Constellation diagram for b=4 (first quadrant). The horizontal axis is labeled 'I' with values +1 and +3. The vertical axis is labeled 'Q' with values +1 and +3. Four points are plotted: (1, 3) labeled 0111, (3, 3) labeled 0101, (1, 1) labeled 1111, and (3, 1) labeled 1101. A small label 'G.9960(10)\_F7-18' is at the bottom right. + +Figure 7-18 – Constellation and mapping for $b = 4$ (first quadrant) + +Table 7-60 – Mapping for $b = 4$ + +| Bits [ $d_1d_0$ ] | $I$ | Bit [ $d_3d_2$ ] | $Q$ | +|-------------------|-----|------------------|-----| +| 00 | -3 | 00 | -3 | +| 10 | -1 | 10 | -1 | +| 11 | 1 | 11 | 1 | +| 01 | 3 | 01 | 3 | + +Constellation mappings for even values of $b \geq 4$ shall be derived by the following steps: + +- 1) Divide the incoming group of $b$ bits into two equal subgroups, so that $b/2$ LSBs form the first subgroup ( $I$ -group) and $b/2$ MSBs form the second subgroup ( $Q$ -group); both subgroups are incoming LSBs (which are $d_0$ and $d_{b/2}$ , respectively) first. +- 2) Compute values of $I$ and $Q$ for the incoming group $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ as: + +$$I = \text{sgn}_I \times \text{val}_I$$ + +$$Q = \text{sgn}_Q \times \text{val}_Q$$ + +The values of $\text{sgn}$ and $\text{val}$ shall be computed as presented in Table 7-61 using bits of $I$ -group to compute $I$ and bits of $Q$ -group to compute $Q$ . + +Table 7-61 – Computation rule for $\text{sgn}$ and $\text{val}$ + +| $I$ – component | $Q$ – component | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| – compute $\text{sgn}_I = 2 \times d_0 - 1$
– compute $\text{val}_I = I_{b-2} - 2^{b/2-1} $ | – compute $\text{sgn}_Q = 2 \times d_{b/2} - 1$
– compute $\text{val}_Q = Q_{b-2} - 2^{b/2-1} $ | +| NOTE 1 – $I_{b-2}$ and $Q_{b-2}$ are the values of $I$ and $Q$ computed for the incoming $(b-2)$ -bit group $\{d_{b-1}, d_{b-2}, \dots, d_{b/2+1}, d_{b/2-1}, \dots, d_1\}$ , i.e., with $d_0$ and $d_{b/2}$ removed. | | +| NOTE 2 – The values of $I$ and $Q$ for 2-bit groups shall be as presented in Table 7-59. | | +| NOTE 3 – $ X $ is the absolute value of $X$ . | | + +###### 7.1.4.3.1.2 Constellations for odd number of bits + +If the number of bits, $b$ , loaded on to the subcarrier is odd (1, 3, 5, 7, 9, 11), constellations with mappings described in this clause shall be used. The support of all the specified odd order constellations (1, 3, 5, 7, 9 and 11) shall be mandatory at the transmitter. The support of all the specified odd order constellations with $b \geq 5$ , shall be optional at the receiver. + +For multicast transmission, odd constellations with $b \geq 5$ shall not be used. + +Constellation and mapping for $b = 1$ shall be as presented in Figure 7-19. + +![Figure 7-19: Constellation shape and mapping for b = 1. The diagram shows a 2D coordinate system with a horizontal I-axis and a vertical Q-axis. Two points are plotted on the I-axis: one at (-1, 0) labeled '0' and another at (1, 0) labeled '1'. Tick marks for +1 and -1 are shown on both axes. The text 'G.9960(10)_F7-19' is at the bottom right.](23f62df20874b7423cbf7f29fcecf9ed_img.jpg) + +Figure 7-19: Constellation shape and mapping for b = 1. The diagram shows a 2D coordinate system with a horizontal I-axis and a vertical Q-axis. Two points are plotted on the I-axis: one at (-1, 0) labeled '0' and another at (1, 0) labeled '1'. Tick marks for +1 and -1 are shown on both axes. The text 'G.9960(10)\_F7-19' is at the bottom right. + +Figure 7-19 – Constellation shape and mapping for $b = 1$ + +Constellation and mapping for $b = 3$ shall be as presented in Figure 7-20. + +![Figure 7-20: Constellation and mapping for b = 3. The diagram shows a 2D coordinate system with I and Q axes. Eight points are plotted and labeled with 3-bit binary values: 000 at (0, -3), 010 at (-1, -1), 100 at (-3, 1), 110 at (-1, 1), 011 at (1, -1), 111 at (1, 1), 101 at (1, 3), and 001 at (3, -1). Tick marks for -3, -1, +1, and +3 are on the I-axis; +1, +3, and -1, -3 are on the Q-axis. The text 'G.9960(10)_F7-20' is at the bottom right.](4750bc46c043ee2e9d4524c36d9a54a1_img.jpg) + +Figure 7-20: Constellation and mapping for b = 3. The diagram shows a 2D coordinate system with I and Q axes. Eight points are plotted and labeled with 3-bit binary values: 000 at (0, -3), 010 at (-1, -1), 100 at (-3, 1), 110 at (-1, 1), 011 at (1, -1), 111 at (1, 1), 101 at (1, 3), and 001 at (3, -1). Tick marks for -3, -1, +1, and +3 are on the I-axis; +1, +3, and -1, -3 are on the Q-axis. The text 'G.9960(10)\_F7-20' is at the bottom right. + +Figure 7-20 – Constellation and mapping for $b = 3$ + +For $b > 3$ cross-shaped constellations shall be used. First, $2^b$ constellation points shall be set as a rectangle, with $M_I = 2^{B1}$ columns ( $M_I$ points on the $I$ -axis) and $M_Q = 2^{B2}$ rows ( $M_Q$ points on the $Q$ -axis), where $B1 = \text{ceiling}(b/2)$ and $B2 = \text{floor}(b/2)$ . The mapping of these points shall be computed using the following steps: + +- 1) Divide the incoming group of bits into two subgroups, so that $B1$ LSBs form the first subgroup ( $I$ -group) and $B2$ MSBs form the second subgroup ( $Q$ -group); both subgroups are incoming LSBs (which are $d_0$ and $d_{B2+1}$ , respectively) first. +- 2) Compute values of $I$ and $Q$ of a rectangular constellation for the incoming group $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ as: + +$$I = \text{sgn}_I \times \text{val}_I$$ + +$$Q = \text{sgn}_Q \times \text{val}_Q$$ + +The values of $\text{sgn}$ and $\text{val}$ shall be computed as presented in Table 7-62 using bits of $I$ -group to compute $I$ and bits of $Q$ -group to compute $Q$ . + +**Table 7-62 – Computation rule for *sgn* and *val*** + +| I – component | Q – component | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| +| – compute $sgn_I = 2 \times d_0 - 1$ | – compute $sgn_Q = 2 \times d_{B1} - 1$ | +| – compute $val_I = I_{2 \times B1} $ | – compute $val_Q = Q_{2 \times B2} $ | +| NOTE 1 – $I_{2 \times B1}$ is the value of I for $(2 \times B1)$ -bit group $\{0, d_{b-1}, d_{b-2}, \dots, d_0\}$ computed as defined in Table 7-61. | | +| NOTE 2 – $Q_{2 \times B2}$ is the value of Q for $(2 \times B2)$ -bit group $\{d_{b-1}, d_{b-2}, \dots, d_1\}$ computed as defined in Table 7-61. | | +| NOTE 3 – $ X $ is the absolute value of X . | | + +- 3) Transform $s = (M_I - M_Q)/4$ columns of constellation points in each quadrant having highest absolute values of *I* (positive or negative) into rows of *Q* by changing their $\{I, Q\}$ coordinates to $\{I', Q'\}$ in the following way: +- $|Q'| = |I| - 2s$ , and $\text{sign}(Q') = \text{sign}(I)$ ; + - $|I'| = M_Q - |Q|$ , and $\text{sign}(I') = \text{sign}(Q)$ . + +The described transformation of $\{I, Q\}$ coordinates for $b = 7$ is presented in Figure 7-21 with $B1 = 4$ and $B2 = 3$ (the MSB and LSB in Figure 7-21 are separated by "/"). + +![Figure 7-21: Transformation of rectangular constellation into cross-shaped constellation for b = 7 (first quadrant). The plot shows a grid of points in the first quadrant of an I-Q plane. The horizontal axis (I) ranges from +1 to +15, and the vertical axis (Q) ranges from +1 to +11. A rectangular block of points at the top-left (Q=9 to 11, I=1 to 4) is shown being transformed into a rectangular block on the right (I=13 to 15, Q=1 to 7). Arrows indicate the mapping of points from the top-left block to the right block. Labels like '001/0001', '101/0001', etc., are placed near the points. A small text 'G.9960(10)_F7-21' is at the bottom right.](215e8d5e5ba38df215b55049d255b2ed_img.jpg) + +Figure 7-21: Transformation of rectangular constellation into cross-shaped constellation for b = 7 (first quadrant). The plot shows a grid of points in the first quadrant of an I-Q plane. The horizontal axis (I) ranges from +1 to +15, and the vertical axis (Q) ranges from +1 to +11. A rectangular block of points at the top-left (Q=9 to 11, I=1 to 4) is shown being transformed into a rectangular block on the right (I=13 to 15, Q=1 to 7). Arrows indicate the mapping of points from the top-left block to the right block. Labels like '001/0001', '101/0001', etc., are placed near the points. A small text 'G.9960(10)\_F7-21' is at the bottom right. + +**Figure 7-21 – Transformation of rectangular constellation into cross-shaped constellation for $b = 7$ (first quadrant)** + +##### 7.1.4.3.2 Constellation point scaling + +Each constellation point $(I, Q)$ , corresponding to the complex value $I + jQ$ at the output of the constellation mapper, shall be scaled by the power-normalization factor $\chi(b)$ , the frequency-domain spectrum shaping coefficient $tss$ , and the gain adjuster $g$ : + +$$Z = \chi(b) \times tss \times g \times (I + jQ)$$ + +###### 7.1.4.3.2.1 Power normalization factor + +The values $(I, Q)$ for each constellation point of each subcarrier shall be scaled such that all constellations, regardless of their size, have the same average power. The required scaling, $\chi(b)$ , for a subcarrier with $b$ -bit loading depends only on the value of $b$ and shall be set as presented in Table 7-63. + +**Table 7-63 – Power normalization factor** + +| Number of bits loaded ( $b$ ) | Scaling factor ( $\chi$ )
(linear scale) | +|-------------------------------|---------------------------------------------| +| 1 | 1 | +| 2 | $1/\sqrt{2}$ | +| 3 | $1/\sqrt{6}$ | +| 4 | $1/\sqrt{10}$ | +| 5 | $1/\sqrt{20}$ | +| 6 | $1/\sqrt{42}$ | +| 7 | $1/\sqrt{82}$ | +| 8 | $1/\sqrt{170}$ | +| 9 | $1/\sqrt{330}$ | +| 10 | $1/\sqrt{682}$ | +| 11 | $1/\sqrt{1322}$ | +| 12 | $1/\sqrt{2730}$ | + +###### 7.1.4.3.2.2 Transmit spectrum shaping + +Frequency-domain spectrum shaping of the transmit signal is achieved by a scaling factor $tss$ defined for each subcarrier. The $tss$ values are set by the transmitter and shall be in the range between 0 and $-30$ dB in steps of $-0.5$ dB. Smaller values of $tss$ provide attenuation and the value $tss = 0$ dB corresponds to no power attenuation on the particular subcarrier. If no spectrum shaping is applied, the $tss$ values shall be equal to 0 dB for all subcarriers. The values of $tss_i$ are relevant only for subcarriers that are actually transmitted (not masked), and shall be ignored for masked subcarriers (see clause 5.2 of [ITU-T G.9964]). + +The communication protocol to convey the $tss$ values used by the transmitter is for further study. + +###### 7.1.4.3.2.3 Gain adjustment + +The gain adjuster $g$ is intended for fine gain adjustment of the power transmitted at a particular subcarrier, which may be used to equalize the SNR margin over all subcarriers. + +The value of gain adjuster shall be set to one. Other values are left for further study. + +##### 7.1.4.3.3 Constellation scrambler + +The phase of constellation points generated by the constellation mapper shall be shifted in accordance with the pseudorandom sequence generated by a linear feedback shift register (LFSR) generator, as shown in Figure 7-22. + +![Diagram of a 13-bit LFSR generator. The register contains bits s1 through s13. The initial seed is 1111111111111. Feedback is taken from bits s8, s11, and s12, which are XORed together. The output of the XOR gate is fed back to the input of s1. A bracket labeled 'Bits used to determine phase shift' covers bits s1 and s2.](cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg) + +G.9960(10)\_F7-22 + +Diagram of a 13-bit LFSR generator. The register contains bits s1 through s13. The initial seed is 1111111111111. Feedback is taken from bits s8, s11, and s12, which are XORed together. The output of the XOR gate is fed back to the input of s1. A bracket labeled 'Bits used to determine phase shift' covers bits s1 and s2. + +Figure 7-22 – Constellation scrambler + +The LFSR generator shall implement the polynomial $g(x) = x^{13} + x^{12} + x^{11} + x^8 + 1$ and shall be advanced by 2 bits for each subcarrier. Bits shall be assigned to subcarriers in order of logical index (see clause 7.1.4.1). The two LSBs of the register shall be taken to determine the phase shift as shown in Table 7-64. + +For the header, ACE and payload, the shift of the LFSR for subcarrier index $i$ shall be $2i$ (for both SSC and MSC). Two LFSR bits corresponding to the subcarrier index 0 are $(s_1, s_2)$ of the initialization seed. Two LFSR bits corresponding to the subcarrier index 1 are $(s_1, s_2)$ after two shifts, and so on. For preamble, INUSE, PR and NACK signal, the shift of the LFSR for subcarrier index $(i \cdot k_m)$ shall be $2i$ where $k_m$ denotes the subcarrier spacing multiplier for preamble section $m$ (see clause 7.1.4.5.3.1.1). + +Table 7-64 – Constellation phase shift versus LFSR output + +| LFSR output | | Phase shift (rad) | +|-------------|----|-------------------| +| s2 | s1 | | +| 0 | 0 | 0 | +| 0 | 1 | $\pi/2$ | +| 1 | 0 | $\pi$ | +| 1 | 1 | $3\pi/2$ | + +The LFSR generator shall be initialized with the seed $1FFF_{16}$ for each OFDM symbol. The LSB of the seed corresponds to $s_1$ . The constellation scrambling shall be applied to the PHY-frame header, ACE and all payload symbols by rotating the originally mapped constellation point $Z_{i,l}^0$ by the phase shift $\theta$ to obtain the complex value for the $Z_{i,l}$ for input to the IFFT (see clause 7.1.4.4.1). + +$$Z_{i,l} = Z_{i,l}^0 \cdot \exp(j\theta)$$ + +#### 7.1.4.4 OFDM modulator + +The OFDM modulator consists of the following major parts: IDFT, cyclic extension, windowing, overlap and add, and frequency up-shift. The incoming signal to the modulator at the $l$ th OFDM symbol in the present frame for a single subcarrier, with index $i$ , is the complex value $Z_{i,l}$ generated by the constellation encoder as described in clause 7.1.4.3 (for symbols of the header and the payload) + +or by preamble generator as described in clause 7.1.4.5.3 (for symbols of the preamble). Time-domain samples generated by the IDFT, after adding the cyclic prefix and windowing, are frequency up-shifted by $F_{US}$ . The functional diagram of OFDM modulator is presented in Figure 7-23. The RF up-converter facilitates ITU-T G.9960 operation in the RF frequency range. + +![Functional model of the OFDM modulator block diagram. The diagram shows a sequence of processing blocks: IDFT, Cyclic prefix N_CP, Windowing, overlap and add, Frequency up-shift, and RF up-converter. The input Z_i,l enters the IDFT block. The output of the IDFT is X_n,l. This is followed by the Cyclic prefix N_CP block, which outputs V_n,l. The next block is Windowing, overlap and add, which outputs U_n. The Frequency up-shift block takes U_n and F_US as input and outputs S_n. Finally, the RF up-converter takes S_n as input and outputs S_out-HF and S_out-RF. The entire sequence from IDFT to Frequency up-shift is labeled as the 'OFDM modulator'. A reference label G.9960(10)_F7-23 is present in the bottom right.](701f4311e49f346390759520fcd19af4_img.jpg) + +Functional model of the OFDM modulator block diagram. The diagram shows a sequence of processing blocks: IDFT, Cyclic prefix N\_CP, Windowing, overlap and add, Frequency up-shift, and RF up-converter. The input Z\_i,l enters the IDFT block. The output of the IDFT is X\_n,l. This is followed by the Cyclic prefix N\_CP block, which outputs V\_n,l. The next block is Windowing, overlap and add, which outputs U\_n. The Frequency up-shift block takes U\_n and F\_US as input and outputs S\_n. Finally, the RF up-converter takes S\_n as input and outputs S\_out-HF and S\_out-RF. The entire sequence from IDFT to Frequency up-shift is labeled as the 'OFDM modulator'. A reference label G.9960(10)\_F7-23 is present in the bottom right. + +**Figure 7-23 – Functional model of the OFDM modulator** + +The presented functional diagram and other figures presented in this clause do not imply any specific implementation. All aspects of signal processing used in the modulator shall comply with the equations and textual descriptions. + +##### 7.1.4.4.1 IDFT + +The IDFT converts the stream of the $N$ complex numbers $Z_{i,l}$ at its input into the stream of $N$ complex time-domain samples $x_{n,l}$ . The input numbers represent the $N$ mapped blocks of data, where the $i$ th block of data represents the complex value $Z_{i,l}$ of the $i$ th modulated subcarrier of the OFDM signal, where $i = 0, 1, \dots, N-1$ is the subcarrier index and $l$ is the sequential number of the OFDM symbol within the current frame, excluding the preamble. The conversion shall be performed in accordance with the equation: + +$$x_{n,l} = \sum_{i=0}^{N-1} \exp\left(j \cdot 2\pi \cdot i \frac{n}{N}\right) \cdot Z_{i,l} \quad \text{for } n = 0 \text{ to } N-1, \quad l = 0 \text{ to } M_F - 1$$ + +where $M_F$ denotes the total number of OFDM symbols in the current frame excluding the preamble symbols, and the value of $N$ represents the maximum number of possibly modulated subcarriers in the OFDM spectrum and shall be a power of 2: $N = 2^k$ , where $k$ shall be an integer. The value of $Z_{i,l}$ for all masked subcarriers shall be set to 0. If some non-masked subcarriers with indices $i < N$ are not loaded with data bits, the corresponding values of $Z_{i,l}$ shall be generated as described in clause 7.1.4.2.6 + +##### 7.1.4.4.2 Cyclic extension + +The cyclic extension provides a guard interval between adjacent OFDM symbols. This guard interval is intended to protect against inter-symbol interference (ISI). + +In OFDM, the cyclic prefix of the $l$ th OFDM symbol in the frame shall be implemented by prepending the last $N_{CP}(l)$ samples of the IDFT output to its output $N$ samples to create a pre-overlapped OFDM symbol, as presented in Figure 7-24. The order of samples in the symbol shall be as follows: + +- The first sample of the symbol is the IDFT output sample $N - N_{CP}(l)$ . +- The last sample of the cyclic prefix is the IDFT output sample $N-1$ ; the next sample is the IDFT output sample 0. + +The $l$ th pre-overlapped OFDM symbol consists of $N$ IDFT samples and $N_{CP}(l)$ cyclic extension, samples, in total: + +$$N_H(l) = N + N_{CP}(l) \text{ [samples]}.$$ + +After cyclic extension as described above, time-domain samples at the reference point $v_{n,l}$ in Figure 7-23 shall comply with the following equations: + +$$v_{n,l} = x_{n-N_{CP}(l),l} = \sum_{i=0}^{N-1} Z_{i,l} \times \exp\left(j \cdot 2\pi \cdot i \frac{n - N_{CP}(l)}{N}\right) \quad \text{for } n = 0 \text{ to } N_W(l) - 1 = N + N_{CP}(l) - 1$$ + +The number of IDFT samples, $N$ , and the number of windowed samples, $\beta$ , shall be the same for all symbols of the same frame. The value of $N_{CP}(l)$ (and the duration of the pre-overlapped OFDM symbol $N_W(l)$ , accordingly) may change during the course of the frame, as follows: + +- All symbols of the header shall have the value of $N_{GI-HD} + \beta$ defined in clause 7.1.4.6. +- The first two symbols following the header shall have the default value $N_{GI-DF} + \beta$ , defined in clause 7.1.4.6. +- All the rest of the payload symbols shall have the same value $N_{GI} + \beta$ , where $N_{GI}$ is selected from the valid values defined in clause 7.1.4.6 and indicated in the header, as described in clause 7.1.2.1. + +##### 7.1.4.4.3 Symbol timing + +The PHY frame consists of a preamble followed by an integer number, $M_F$ , of OFDM symbols. The first symbol following the preamble (the first symbol of the PHY-header) shall have symbol count 0, and the last symbol of the frame shall have symbol count $M_F - 1$ . The time position of each symbol in the frame is defined by sample count. The first sample of the symbol with symbol count 0 shall have sample count $M(0) = N_{pr} - \beta$ , where $N_{pr}$ is the number of samples in the preamble. The count of the first sample of the $l$ th symbol ( $l = 1, 2, \dots, M_F - 1$ ) in the frame shall be: + +$$M(l) = N_{pr} - \beta + \sum_{k=0}^{l-1} N_S(k)$$ + +where $N_S(k) = N + N_{CP}(k) - \beta$ and $N_S(k)$ may be different for symbols of the header and payload, as described in clause 7.1.4.6. + +##### 7.1.4.4.4 Windowing, overlap and add + +![Figure 7-24: Structure of an OFDM symbol with cyclic extension and overlapped windowing. The diagram shows a time-domain signal with a window function applied. The total duration of the OFDM symbol is labeled as N_s = N + N_CP(l) - beta. The duration of the pre-overlapped OFDM symbol is labeled as N_W(l) samples. The duration of the cyclic prefix is labeled as N_CP(l). The duration of the guard interval is labeled as N_GI(l). The duration of the IDFT output is labeled as N. The duration of the windowed samples is labeled as beta. The diagram also shows the overlap between adjacent symbols, with the first beta samples of the cyclic prefix and last beta samples of the IDFT output being used for shaping the envelope of the transmitted signal.](2a52834ffb60a618738d21bcc3ace1e3_img.jpg) + +G.9960(11)\_F7-24 + +Figure 7-24: Structure of an OFDM symbol with cyclic extension and overlapped windowing. The diagram shows a time-domain signal with a window function applied. The total duration of the OFDM symbol is labeled as N\_s = N + N\_CP(l) - beta. The duration of the pre-overlapped OFDM symbol is labeled as N\_W(l) samples. The duration of the cyclic prefix is labeled as N\_CP(l). The duration of the guard interval is labeled as N\_GI(l). The duration of the IDFT output is labeled as N. The duration of the windowed samples is labeled as beta. The diagram also shows the overlap between adjacent symbols, with the first beta samples of the cyclic prefix and last beta samples of the IDFT output being used for shaping the envelope of the transmitted signal. + +**Figure 7-24 – Structure of an OFDM symbol with cyclic extension and overlapped windowing** + +The first $\beta$ samples of the cyclic prefix and last $\beta$ samples of the IDFT output shall be used for shaping the envelope of the transmitted signal (windowing). The window function facilitates PSD shaping: it allows sharp PSD roll-offs used to create deep spectral notches and reduction of the out-of-band PSD. The number of windowed samples, $\beta$ , shall be the same for all of the payload symbols of the same frame, as well as the PHY-header and preamble. + +To reduce the modulation overhead, the windowed samples of adjacent symbols shall overlap, as shown in Figure 7-24. The value of $N_{CP}(l) - \beta = N_{GI}(l)$ forms the guard interval. The duration of the $l$ th OFDM symbol after overlap is thus $N_S(l) = N + N_{CP}(l) - \beta$ . + +After applying the windowing and the overlap and add functions, the time-domain samples at the reference point $u_n$ in Figure 7-23 shall comply with the following equations: + +$$u_n = u_n^{(pr)} + \sum_{l=0}^{M_F-1} w(n - M(l), l) \times u_{n-M(l), l} \quad \text{for } n = 0 \text{ to } M(M_F - 1) + N_W(M_F - 1) - 1$$ + +where $u_n^{(pr)}$ is the $n$ th sample of the preamble, as defined in clause 7.1.4.5 (note that the signal $u_n^{(pr)}$ already includes windowing as necessary), $w(n, l)$ is the windowing function defined on $N_W(l)$ samples of the pre-overlapped OFDM symbol in the following way: + +$$w(n, l) = \begin{cases} w_\beta(n) & 0 \leq n < \beta \\ 1 & \beta \leq n < N_W(l) - \beta \\ w_\beta(N_W(l) - 1 - n) & N_W(l) - \beta \leq n < N_W(l) \\ 0 & \text{otherwise} \end{cases}$$ + +where $w_\beta(n)$ is the function describing the roll-off section of the window. The roll-off function $w_\beta(n)$ shall be vendor discretionary. + +However, $w_\beta(n)$ shall comply with the following rules: + +- $w_\beta(n) + w_\beta(\beta - n - 1) = 1$ for $0 \leq n < \beta$ . +- $0 \leq w_\beta(n) \leq 1$ . + +The symbol rate $f_{OFDM}$ (number of symbols per second) and symbol period $T_{OFDM}$ for the given value of $N_{CP}$ and $\beta$ shall be computed, respectively, as: + +$$f_{OFDM} = \frac{N \times F_{SC}}{N + N_{CP} - \beta}$$ + +and + +$$T_{OFDM} = 1/f_{OFDM}$$ + +##### 7.1.4.4.5 Frequency up-shift + +The frequency up-shift offsets the spectrum of the transmit signal shifting it by $F_{US}$ . The value of $F_{US}$ shall be a multiple of the subcarrier frequency $F_{SC}$ : + +$$F_{US} = m \cdot F_{SC}, \text{ where } m \text{ is an integer and } N/2 \leq m.$$ + +The valid values of $m$ are medium dependent and can be calculated from the values given in clause 7.2. + +The real and imaginary components of the signal after frequency up-shift (reference point $s_n$ in Figure 7-23) shall be as follows: + +$$s_n = u_{n/p} \times \exp\left(j \frac{2\pi mn}{Np}\right) = \text{Re}(s_n) + j \text{Im}(s_n) \quad \text{for } n = 0 \text{ to } [M(M_F - 1) + N_W(M_F - 1)] \times p - 1;$$ + +$$\text{Re}(s_n) = \text{Re}(u_{n/p}) \cos\left(\frac{2\pi mn}{Np}\right) - \text{Im}(u_{n/p}) \sin\left(\frac{2\pi mn}{Np}\right)$$ + +$$\text{Im}(s_n) = \text{Re}(u_{n/p}) \sin\left(\frac{2\pi mn}{Np}\right) + \text{Im}(u_{n/p}) \cos\left(\frac{2\pi mn}{Np}\right)$$ + +where $u_{n/p}$ is $u_n$ after interpolation with factor $p$ . The interpolation factor $p$ is vendor discretionary, and shall be equal to or higher than 2. + +NOTE 1 – The minimum value of $p$ sufficient to avoid distortions depends on the ratio between the up-shift frequency $F_{US}$ and the bandwidth of the transmit signal $BW = N \cdot F_{SC}$ . It is assumed that an appropriate low-pass filter is included to reduce imaging. + +NOTE 2 – The phase of the up-shift should be initialized to zero at the first sample of the preamble and be advanced by $\frac{2\pi m}{N_p}$ per each sample (after interpolation). + +##### 7.1.4.4.6 Output signal + +For all applications which do not use an RF up-converter (further referred to as HF-applications), the output signal of the modulator shall be the real component of $s_n$ : + +$$S_{out-HF} = \text{Re}(s_n)$$ + +For RF applications, the RF up-converter shall produce the following output signal: + +$$S_{out-RF}(t) = \text{Re}[s(t) \times \exp(j2\pi F_{UC}t)] = \text{Re}[s(t)] \times \cos(2\pi F_{UC}t) - \text{Im}[s(t)] \times \sin(2\pi F_{UC}t)$$ + +where $F_{UC}$ is the frequency shift introduced by the RF modulator. The range of $F_{UC}$ and its valid values are specified in clause 7.1.4.6. + +After RF up-conversion, the centre frequency around which the spectrum of the transmit OFDM signal will be placed is $F_C = F_{UC} + F_{US}$ . + +#### 7.1.4.5 Preamble, INUSE, PR, NACK and IDPS signals + +##### 7.1.4.5.1 General preamble structure + +The preamble is prepended to every PHY frame defined in clause 7.1.2.1. It is intended to assist the receiver in detecting, synchronizing to the frame boundaries, and acquiring the physical layer parameters such as channel estimation and OFDM symbol alignment. The preamble shall meet the same transmit PSD mask (i.e., notches, shapes) as the header and the payload symbols. + +Table 7-65 presents the general structure of the preamble. Each section $I$ comprises $N_I$ repetitions of an OFDM symbol ( $S_I$ ) employing subcarrier spacing $k_I \times F_{SC}$ , where $F_{SC}$ denotes the subcarrier spacing of the payload. A zero value for $N_I$ means that section $I$ is not included in the preamble. The values of $k_I$ shall be selected from the set 1, 2, 4 or 8. The preamble subcarriers of section $I$ shall be one in every $k_I$ subcarriers with respect to the subcarriers used for the payload OFDM symbol starting from subcarrier zero. Each preamble section shall be windowed as necessary in order to comply with the PSD mask. This is illustrated in Figure 7-25. + +**Table 7-65 – General structure of the preamble** + +| | 1st section | 2nd section | 3rd section | +|--------------------------------------------|-------------|-----------------------|-------------| +| Number of symbols ( $N_I$ ) (Note 1) | $N_1$ | $N_2$ | $N_3$ | +| Subcarrier spacing ( $k_I \times F_{SC}$ ) | $k_1$ | $k_2 = k_1$ (Note 2) | $k_3$ | +| OFDM symbol ( $S_I$ ) | $S_1$ | $S_2 = -S_1$ (Note 3) | $S_3$ | + +NOTE 1 – $N_I$ does not include windowing. +NOTE 2 – The subcarrier spacing of the 2nd section shall be equal to the subcarrier spacing of the 1st section. +NOTE 3 – The OFDM symbol of the 2nd section shall be an inverted time-domain waveform of the 1st section. + +Figure 7-25 shows the preamble waveform. + +![Figure 7-25 – Preamble waveform diagram showing four sections: 1st section (S1), 2nd section (S2), 3rd section (S3), and PHY-frame header (GL_HD). Each section has a tone spacing and number of symbols. The diagram also shows guard intervals (beta) and subcarrier spacing (beta/2).](b8d855a06aad434aeafa2739bf62e7de_img.jpg) + +The diagram illustrates the preamble waveform structure, divided into four main sections: + +- 1st section:** Contains $N_1$ repetitions of OFDM symbol $S_1$ with tone spacing $k_1 \times F_{sc}$ . Guard intervals of $\beta$ are shown between symbols, and $\beta/2$ at the start and end. +- 2nd section:** Contains $N_2$ repetitions of OFDM symbol $S_2$ with tone spacing $k_2 \times F_{sc}$ . It follows the 1st section with a $\beta/2$ guard interval. A note indicates $K_2 = K_1$ and $S_2 = -S_1$ . +- 3rd section:** Contains $N_3$ repetitions of OFDM symbol $S_3$ with tone spacing $k_3 \times F_{sc}$ . It follows the 2nd section with a $\beta/2$ guard interval. +- PHY-frame header:** Contains the PHY-frame header with tone spacing $F_{sc}$ and a guard interval $GI\_HD$ . + +The diagram is labeled G.9960(10)\_F7-25. + +Figure 7-25 – Preamble waveform diagram showing four sections: 1st section (S1), 2nd section (S2), 3rd section (S3), and PHY-frame header (GL\_HD). Each section has a tone spacing and number of symbols. The diagram also shows guard intervals (beta) and subcarrier spacing (beta/2). + +**Figure 7-25 – Preamble waveform** + +The number of repetitions of OFDM symbol $S_l$ ( $N_l$ ) in each of the preamble sections may be a non-integer number to incorporate an optional guard interval between sections provided that a fraction of $N_l$ is consistent with the guard interval specified in Table 7-67. The specific preamble types and construction methods are defined in clause 7.2. + +##### **7.1.4.5.2 INUSE, PR, NACK and IDPS signals general structure** + +The INUSE, PR, NACK and IDPS general structure (see clause 8.3.3.4 of [ITU-T G.9961]) is composed of a single section. + +**Table 7-66 – INUSE, PR, NACK and IDPS signal generation parameters** + +| Description | Symbol | +|-----------------------------------------------|-----------| +| Number of symbols
(Note) | $N_{PRS}$ | +| Subcarrier spacing
( $k_1 \times F_{SC}$ ) | $k_1$ | +| OFDM symbol | $S_{PRS}$ | +| NOTE – $N_{PRS}$ does not include windowing. | | + +The INUSE, PR, NACK and IDPS signals shall meet the same transmit PSD mask (i.e., notches, shapes) as the preamble symbols and shall be windowed as necessary in order to comply with the PSD mask. + +The INUSE, PR, NACK and IDPS signals consist of $N_{PRS}$ repetitions of an OFDM symbol ( $S_{PRS}$ ) that employs the same subcarrier spacing as the first section of the preamble ( $k_1 \times F_{SC}$ ). + +The values for the $N_{PRS}$ parameter are found in the medium specific sub-sections of clause 7.2. + +##### **7.1.4.5.3 Preamble, INUSE, PR NACK and IDPS signal generation** + +This clause contains the description of preamble, INUSE, PR, NACK and IDPS signal generation method, which is not medium dependent. The preamble, INUSE, PR, NACK and IDPS signal generation method specific to the type of medium is described under clause 7.2. + +###### **7.1.4.5.3.1 Frequency-domain symbol generation** + +###### **7.1.4.5.3.1.1 Preamble** + +The subcarriers of the $m$ th section of the preamble shall be those with indices 0, $k_m$ , $2k_m$ , $3k_m$ , etc. The preamble generator shall output complex values $Z_i$ for each subcarrier following the order given by + +logical indices $i$ with $i = 0, k_m, 2k_m, \dots$ to be modulated on to symbols of the preamble in accordance with the relevant subcarrier mask. + +###### 7.1.4.5.3.1.2 INUSE, PR, NACK and IDPS signals + +The subcarrier spacing of the INUSE, PR, NACK and IDPS signals shall be the same as the subcarrier spacing of the first section of the preamble ( $k_l \times F_{SC}$ ). The INUSE, PR, NACK and IDPS signal generator shall output complex values $Z'_i$ for each subcarrier following the order given by logical indices $i = 0, k_l, 2k_l, \dots$ to be modulated on to symbols of the INUSE, PR, NACK and IDPS signal in accordance with the relevant subcarrier mask. + +###### 7.1.4.5.3.2 Modulation + +###### 7.1.4.5.3.2.1 Modulation of the preamble + +For the non-masked subcarriers of the preamble, a bit sequence of all ones shall be mapped using the 1-bit constellation as specified in clause 7.1.4.3.1.2. Other bit sequences are for further study. + +The constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a seed that is section and medium dependent. The default value of the seed is defined in clause 7.2. Additional, domain-specific seeds are also defined in clause 7.2. The seed used shall either be the default seed or a domain-specific seed, as indicated in the "TXOP Attributes Extension Data" of the MAP (see clause 8.8.4.1.1 of [ITU-T G.9961]). Whenever usage of a domain-specific seed is indicated, the appropriate seed shall be selected from the pool of seeds in the tables in clause 7.2 based on the DOD (Domain ID). + +NOTE – This mechanism may be used by a DM whenever it detects the presence of a neighbouring network (regardless of the transmission technology being used by the neighbouring network) in order to reduce the level of interference to the neighbouring network. + +For preamble generation, the output of the mapper shall be subsequently rotated using the two bits that are the LSBs of the LFSR, $s_1$ and $s_2$ , as defined in Table 7-64 (constellation scrambler) resulting in constellation point $Z_i$ . + +The LFSR shall be advanced by two bits for each preamble's subcarrier (for both SSC and MSC) in the order specified in clause 7.1.4.3.3. + +###### 7.1.4.5.3.2.2 Modulation of the INUSE, PR, NACK and IDPS symbols + +The non-masked subcarriers of the INUSE, PR, NACK and IDPS signals shall be modulated using a BPSK sequence, of all ones ( $P_i$ ). The reference sequence shall be subsequently rotated as specified in clause 7.1.4.3.3 (Constellation scrambler). + +The constellation scrambler LFSR generator shall be initialized at the beginning of the INUSE, PR, NACK and IDPS signals to a seed that is medium dependent. The default value of the seed is defined in clause 7.2. Additional, domain-specific seeds are also defined in clause 7.2. The seed used shall either be the default seed or a domain-specific seed, as indicated in the "TXOP Attributes Extension Data" of the MAP (see clause 8.8.4.1.1 of [ITU-T G.9961]). Whenever usage of a domain-specific seed is indicated, the appropriate seed shall be selected from the pool of seeds in the tables of clause 7.2 based on the DOD (Domain ID). + +NOTE – This mechanism may be used by a DM whenever it detects the presence of a neighbouring network (regardless of the transmission technology being used by the neighbouring network) in order to reduce the level of interference to the neighbouring network. + +For non-masked subcarrier $i$ , $Z_i$ shall be generated by rotating $P_i$ using the two bits that are the LSBs of the LFSR, $s_1$ , and $s_2$ , as defined in Table 7-64. The LFSR shall be advanced by two bits for each applicable subcarrier (for both SSC and MSC) in the order specified in clause 7.1.4.3.3. + +$Z'_i$ is the complex conjugate of $Z_i$ and $Z'_i$ shall be used to generate the symbol $S_{PRS}$ used in the INUSE, PR, NACK and IDPS signals. + +###### 7.1.4.5.3.3 Time-domain symbol generation + +###### 7.1.4.5.3.3.1 Preamble + +The $Z_i$ values shall be modulated on to OFDM symbols as described in clause 7.1.4.4.1. + +The output time-domain symbol shall be repeated $N_I$ times where $N_I$ denotes the number of replicas within section $I$ . If either $N_1$ or $N_3$ are non-integer numbers, the fraction of the symbol replica shall be at the beginning of the section. If $N_2$ is a non-integer number, the fraction of the symbols replica shall be at the end of the section. + +The first, second and third sections of the preamble shall be windowed, overlapped and added as described below: + +- 1) First section: + - a) The first short symbol of the first section is cyclically extended by prepending $\beta/2$ samples. + - b) The last short symbol of the first section is cyclically extended by appending $\beta/2$ samples. + - c) The first and last $\beta$ samples of the extended first section are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ respectively. +- 2) Second section: + - a) The first short symbol of the second section is cyclically extended by prepending $\beta/2$ samples. + - b) The last short symbol of the second section is cyclically extended by appending $\beta/2$ samples. + - c) The first and last $\beta$ samples of the extended second section are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ respectively. +- 3) Third section: + - a) The beginning of the third section is cyclically extended by prepending $\beta$ samples. + - b) The first and last $\beta$ samples of the extended third section are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ respectively. +- 4) Overlap and add: + - a) The $\beta$ windowed samples at the end of the first section and at the beginning of the second section are overlapped and added. + - b) The $\beta$ windowed samples at the end of the second section and at the beginning of the third section are overlapped and added. + - c) The $\beta$ windowed samples at the end of the third section are overlapped and added with the $\beta$ windowed samples at the beginning of the PHY-frame header as described in clause 7.1.4.4.4. + +$w_\beta(n)$ shall comply with the rules specified in clause 7.1.4.4.4. + +This is illustrated in Figure 7-26. + +![Figure 7-26: Preamble time-domain generation diagram. It shows three horizontal timelines for preamble signals. The first timeline shows a sequence of short symbols S1, with the first and last ones being extended by beta/2 samples at each end. The total duration is labeled as N1 symbols. The second timeline shows a sequence of short symbols S2, also with beta/2 samples at each end, totaling N2 symbols. The third timeline shows a sequence of short symbols S3, with beta samples at each end, totaling N3 symbols. Below these is a 'Header' section. The diagram is labeled G.9960(10)_F7-26.](54a1e5d91d7f442361767b1f8c81c777_img.jpg) + +Figure 7-26: Preamble time-domain generation diagram. It shows three horizontal timelines for preamble signals. The first timeline shows a sequence of short symbols S1, with the first and last ones being extended by beta/2 samples at each end. The total duration is labeled as N1 symbols. The second timeline shows a sequence of short symbols S2, also with beta/2 samples at each end, totaling N2 symbols. The third timeline shows a sequence of short symbols S3, with beta samples at each end, totaling N3 symbols. Below these is a 'Header' section. The diagram is labeled G.9960(10)\_F7-26. + +**Figure 7-26 – Preamble time-domain generation** + +The number of samples at the Nyquist rate in the preamble shall be: + +$$N_{pr} = \beta + N_1 \frac{N}{k_1} + N_2 \frac{N}{k_2} + N_3 \frac{N}{k_3}$$ + +###### 7.1.4.5.3.3.2 INUSE, PR, NACK and IDPS signals + +For the INUSE, PR, NACK and IDPS signals, the output time domain symbol shall be repeated $N_{PRS}$ times, where $N_{PRS}$ denotes the number of replicas. The $Z'_i$ values shall be modulated on to OFDM symbols as described in clause 7.1.4.4.1. + +The INUSE, PR, NACK and IDPS signals shall be windowed as described below: + +- 1) The first short symbol of the INUSE, PR, NACK and IDPS signals is cyclically extended by prepending $\beta/2$ samples. +- 2) The last short symbol of the INUSE, PR, NACK and IDPS signals is cyclically extended by appending $\beta/2$ samples. +- 3) The first and last $\beta$ samples of the extended INUSE, PR, NACK and IDPS signals are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ , respectively. + +$w_\beta(n)$ shall comply with the rules specified in clause 7.1.4.4.4. + +This is illustrated in Figure 7-27. + +![Figure 7-27: INUSE, PR, NACK and IDPS signals in time domain diagram. It shows a horizontal timeline for a sequence of short symbols S_PRS. The first symbol is extended by beta/2 samples at the beginning, and the last symbol is extended by beta/2 samples at the end. The total duration is labeled as N_PRS symbols. The diagram is labeled G.9960(10)_F7-27.](e845d172f83764c1db7998397af2b9d5_img.jpg) + +Figure 7-27: INUSE, PR, NACK and IDPS signals in time domain diagram. It shows a horizontal timeline for a sequence of short symbols S\_PRS. The first symbol is extended by beta/2 samples at the beginning, and the last symbol is extended by beta/2 samples at the end. The total duration is labeled as N\_PRS symbols. The diagram is labeled G.9960(10)\_F7-27. + +**Figure 7-27 – INUSE, PR, NACK and IDPS signals in time domain** + +The number of samples at Nyquist rate in the INUSE, PR and NACK signals shall be: + +$$N_s = \beta + N_{PRS} \frac{N}{k_1}$$ + +#### 7.1.4.6 PMD control parameters + +Table 7-67 summarizes valid values of control parameters of the OFDM modulator described in the clauses above. This list is a superset of parameters used over different media; a list of valid values of modulation parameters and their valid combinations for particular media is presented in [ITU-T G.9964]. + +**Table 7-67 – Valid OFDM control parameters** + +| Notation | Parameter | Valid values or range | | | +|-------------|---------------------------------------|-----------------------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Telephone lines | Power lines | Coax cables | +| $N$ | Number of subcarriers | See Table 6-1 of [ITU-T G.9964] | See Table 6-4 of [ITU-T G.9964] | See Table 6-6 of [ITU-T G.9964] | +| $F_{SC}$ | Subcarrier spacing [kHz] | See Table 6-1 of [ITU-T G.9964] | See Table 6-4 of [ITU-T G.9964] | See Table 6-6 of [ITU-T G.9964] | +| $N_{GI}$ | Guard interval [samples] | See Table 6-1 of [ITU-T G.9964] | See Table 6-4 of [ITU-T G.9964] | See Table 6-6 of [ITU-T G.9964] | +| $N_{GI-HD}$ | Guard interval of the header | $N/4$ | | | +| $N_{GI-DF}$ | Default guard interval of the payload | $N/4$
(Note 1) | | | +| $\beta$ | Window size [samples] | Any even integer between 0 and $N/4$ (Note 2) | | | +| $F_{US}$ | Up-shift frequency, [kHz] | $m \times F_{SC}$ ,
$m \geq N/2$ | | | +| $F_{UC}$ | Up-convert frequency, [kHz] | N/A | N/A | $F_{UC} = l \times F_G$
where valid values for $l$ are a subset of the range of integers between 12 and $100 - (2 \times F_{US}/F_G)$ and $F_G = 25$ MHz (Note 4) | + +NOTE 1 – $N_{GI-DF} \geq N_{GI}$ + +NOTE 2 – Range 0 to $N/4$ + +NOTE 3 – $m$ is an integer; valid values of $m$ can be calculated from clause 7.2 + +NOTE 4 – RF applications. Additional constraints on $F_{UC}$ may be specified in regional annexes. In Annex C valid values for $l$ are a subset of the range of integers between 12 and $120 - (2 \times F_{US}/F_G)$ and $F_G = 25$ MHz + +Secondary parameters of the OFDM modulator are presented in Table 7-68. + +**Table 7-68 – Secondary parameters of the modulator** + +| Notation | Parameter | Note | +|------------|---------------------------------------------------|---------------------------------------------------------| +| $BW$ | Total bandwidth [Hz] | $BW = N \times F_{SC}$ | +| $N_W$ | Number of samples in a pre-overlapped OFDM symbol | $N_W = N + N_{CP}$ | +| $N_s$ | Number of samples in an OFDM symbol | $N_s = N + N_{CP} - \beta$ | +| $f_{OFDM}$ | Symbol rate [symbols/s] | $f_{OFDM} = \frac{N \times F_{SC}}{N + N_{CP} - \beta}$ | +| $T_{OFDM}$ | Symbol period [s] | $T_{OFDM} = 1/f_{OFDM}$ | +| $N_{GI}$ | Guard interval | $N_{GI} = N_{CP} - \beta$ | +| $F_C$ | Centre frequency | $F_C = F_{US} + F_{UC}$ | +| $f_s$ | Transmit clock | $f_s = N \times F_{SC}$ | + +#### 7.1.4.7 Symbol boost + +Symbols of the preamble and the PHY-frame header may be sent with higher power (boosted) relative to the ACE and payload symbols. For the PHY-frame header, only the first OFDM symbol is subject to symbol boost. The boosting shall be achieved by increasing the power of each active subcarrier in the boosted symbol by the same value in dB with the maximum boost of 3 dB (see Table 8-79.1 in [[ITU-T G.9961](#)]). + +A domain-wide symbol boost is controlled by the domain master using the same mechanism as the one used to update the PSD shaping as described in clause 8.8.5.5 of [[ITU-T G.9961](#)]. If the domain master has not indicated symbol boost, all nodes shall boost the preamble and the first OFDM symbol of the PHY-frame header by 0.8 dB (see Table 8-14 in [[ITU-T G.9961](#)]). The PSD ceiling carried in the PHY-frame header shall not include the amount of power boost. + +The domain-wide symbol boost setting parameters (see Table 8-79.1 in [[ITU-T G.9961](#)]) are not applicable to the transmission of MAP-D/RMAP-D frames. The preamble and the first OFDM symbol of the PHY-frame header of the MAP-D/RMAP-D frames shall each be boosted with a fixed value of 0.8 dB. + +The symbol boost shall be allowed only for power-line and telephone-line OFBs. + +### 7.1.5 Transmit PSD mask + +Transmit PSD mask (TxPSD) is determined by a subcarrier mask (SM), a PSD shaping mask (PSM), a notching of international amateur radio bands, the limit PSD mask (LPM) defined for each particular medium, and a regional PSD mask (RPM) if specified in a regional annex. Parameters to construct the TxPSD are broadcast by the MAP message (clause 8.8.5 of [[ITU-T G.9961](#)]). + +See clause 5 of [[ITU-T G.9964](#)] for the detailed specification of TxPSD. + +Notching of amateur radio bands (see clause 5.3 of [[ITU-T G.9964](#)]) is accomplished by configuring one or more SM bands (see clause 5.1 of [[ITU-T G.9964](#)]) coinciding with the amateur radio bands, or by using the amateur radio band descriptor (see clause 8.8.5 of [[ITU-T G.9961](#)]). + +The amateur radio band to be masked in a particular domain is specified in the MAP by the amateur radio band descriptor (see clause 8.8.5 of [[ITU-T G.9961](#)]). + +A PSD ceiling may be applied by the DM in addition to the TxPSD to the nodes of the domain to impose a limit (i.e., a ceiling function) on the transmit signal via the MAP (see clause 8.8.5.5 of [ITU-T G.9961]). + +APSD\_MAX is conveyed in the PHY frame header to the receiver.. + +### 7.1.6 Electrical specifications + +#### 7.1.6.1 Transmit clock tolerance + +The tolerance of the transmit clock (defined in Table 7-68) shall not exceed $\pm 50$ ppm, including aging. + +#### 7.1.6.2 Relative transmit clock accuracy + +All nodes shall synchronize the frequency of their transmit clocks to a domain master clock (see the NTR field of the PHY frame header in clause 7.1.2.3.2.1.2). If a node can decode the MAP frame reliably, it shall synchronize its transmit clock with that of the domain master, and the difference between the clocks shall not exceed $\pm 0.5$ ppm. Otherwise, it shall synchronize its transmit clock with that of the node transmitting the RMAP frame. In this case, the difference between the transmit clock frequency of this node and that of the node transmitting the RMAP frame shall not exceed $\pm 0.5$ ppm. + +Nodes that are not synchronized with a domain master either directly or through a relay node shall not transmit. + +These accuracy requirements shall apply to all OFBs and media types. + +#### 7.1.6.3 Up-convert frequency tolerance + +The up-convert frequency and transmit clock frequency shall be derived from the same reference clock source, hence they share the same tolerance requirement. + +## 7.2 Medium dependent specification + +### 7.2.1 Physical layer specification over telephone lines + +#### 7.2.1.1 Control parameters + +See clause 6.1.1 of [ITU-T G.9964]. + +#### 7.2.1.2 Preamble, INUSE, PR and NACK signals + +##### 7.2.1.2.1 Preamble structure + +Table 7-69 illustrates the preamble structure for a telephone line. + +**Table 7-69 – Preamble structure for transmission over telephone lines** + +| | 1st section | 2nd section | 3rd section | +|--------------------------------------------|-------------|-------------|-------------| +| Number of symbols ( $N_i$ ) | 8 | 2 | 0 | +| Subcarrier spacing ( $k_i \times F_{sc}$ ) | $k_i = 8$ | $k_i = 8$ | $k_i = 0$ | + +##### 7.2.1.2.2 INUSE, PR and NACK signal generation parameters for telephone lines + +Table 7-70 illustrates the INUSE, PR and NACK signal generation parameters for telephone lines. + +**Table 7-70 – INUSE, PR and NACK signal generation parameters for telephone lines** + +| Parameter | Value | +|--------------------------------------------|-------| +| Number of symbols ( $N_{PRS}$ ) | 7 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | 8 | + +##### 7.2.1.2.3 Modulation of the preamble for telephone lines + +When using a default seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed that is section dependent as defined in Table 7-71. + +When using a "domain-specific" seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM in the DM\_Defined\_Seed field of the additional domain information subfield (see clause 8.8.5.15 of [ITU-T G.9961]). The DM shall choose the seed from the set of seeds corresponding to the DOD of the domain, as specified in Table 7-71.1). + +**Table 7-71 – Default constellation scrambler initialization seed values for the preamble, for telephone lines** + +| Medium | 1st section | 3rd section | +|----------------|--------------------|-------------| +| Telephone line | 0127 16 | N/A | + +**Table 7-71.1 – Set of domain-specific constellation scrambler initialization seed values for the preamble, for telephone lines** + +| DOD (Domain ID) | 1st Section | 3rd Section | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 0 | 024E 16 ; 17A9 16 ; 0F53 16 ; 10F3 16 ;
1545 16 ; 01E6 16 ; 0A8A 16 ; 098E 16 | N/A | +| 1 | 06B2 16 ; 17C9 16 ; 00A7 16 ; 131C 16 ;
0D64 16 ; 0F93 16 ; 014F 16 ; 14FC 16 | N/A | +| 2 | 044C 16 ; 0B96 16 ; 040D 16 ; 0119 16 ;
037E 16 ; 0074 16 ; 1A7E 16 ; 0226 16 | N/A | +| 3 | 1E0E 16 ; 172C 16 ; 081B 16 ; 0232 16 ;
06FC 16 ; 00E8 16 ; 1C1D 16 ; 1ADE 16 | N/A | +| 4 | 1B5B 16 ; 05B3 16 ; 084F 16 ; 0029 16 ;
0637 16 ; 121E 16 ; 1EFB 16 ; 102F 16 | N/A | +| 5 | 154F 16 ; 14C7 16 ; 0CDE 16 ; 0880 16 ;
09AC 16 ; 096B 16 ; 0D6F 16 ; 0DAD 16 | N/A | +| 6 | 02D9 16 ; 0427 16 ; 1014 16 ; 131B 16 ;
180B 16 ; 043D 16 ; 1DF6 16 ; 005F 16 | N/A | +| 7 | 0A9E 16 ; 098F 16 ; 19BD 16 ; 1100 16 ;
1358 16 ; 12D7 16 ; 1016 16 ; 02DE 16 | N/A | + +**Table 7-71.1 – Set of domain-specific constellation scrambler initialization seed values for the preamble, for telephone lines** + +| DOD (Domain ID) | 1st Section | 3rd Section | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 8 | 0B14 16 ; 1437 16 ; 0AF6 16 ; 15CF 16 ;
1E04 16 ; 0CDF 16 ; 14AF 16 ; 1530 16 | N/A | +| 9 | 1B55 16 ; 085F 16 ; 0592 16 ; 1B2A 16 ;
1E42 16 ; 07E8 16 ; 1503 16 ; 0F10 16 | N/A | +| 10 | 038A 16 ; 0A34 16 ; 1878 16 ; 1170 16 ;
03E4 16 ; 1251 16 ; 0253 16 ; 0F66 16 | N/A | +| 11 | 0ADE 16 ; 069D 16 ; 0583 16 ; 08E9 16 ;
054A 16 ; 0397 16 ; 016F 16 ; 058A 16 | N/A | +| 12 | 0A1B 16 ; 157B 16 ; 1AE7 16 ; 0F02 16 ;
066F 16 ; 0A57 16 ; 0A98 16 ; 0DAA 16 | N/A | +| 13 | 042F 16 ; 12C9 16 ; 1D95 16 ; 01FC 16 ;
1C85 16 ; 0FD0 16 ; 0A06 16 ; 1E20 16 | N/A | +| 14 | 0715 16 ; 1469 16 ; 10F0 16 ; 02E1 16 ;
07C9 16 ; 04A3 16 ; 04A6 16 ; 1ECC 16 | N/A | +| 15 | 15BC 16 ; 0D3A 16 ; 0B06 16 ; 11D2 16 ;
0A95 16 ; 072F 16 ; 03F9 16 ; 1C49 16 | N/A | + +##### 7.2.1.2.4 Modulation of the INUSE, PR and NACK signals for telephone lines + +The constellation scrambler LFSR generator shall be initialized at the beginning of the INUSE, PR and NACK signals to the same seed used for the 1st preamble section, as defined in Tables 7-71 (default seed) and Table 7-71.1 (domain-specific seeds). + +#### 7.2.1.3 PSD mask specifications + +See clause 6.1.2 of [[ITU-T G.9964](#)]. + +#### 7.2.1.4 Permanently masked subcarriers + +See clause 6.1.3 of [[ITU-T G.9964](#)]. + +### 7.2.2 Physical layer specification over power lines + +#### 7.2.2.1 Control parameters + +See clause 6.2.1 of [[ITU-T G.9964](#)]. + +#### 7.2.2.2 Preamble, INUSE, PR, NACK and IDPS signal + +##### 7.2.2.2.1 Preamble structure + +Table 7-72 illustrates the preamble structure for transmission over power lines. + +**Table 7-72 – Preamble structure for transmission over power lines** + +| | 1st section | 2nd section | 3rd section | +|--------------------------------------------|-------------|-------------|-------------| +| Number of symbols ( $N_i$ ) | 7 | 2 | 0 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | $k_i = 8$ | $k_i = 8$ | $k_i = 0$ | + +##### 7.2.2.2.2 INUSE, PR, NACK and IDPS signal generation parameters for power lines + +Table 7-73 illustrates the INUSE, PR and NACK signal generation parameters for power line. + +**Table 7-73 – INUSE, PR, NACK and IDPS signal generation parameters for power line** + +| Parameter | Value | +|--------------------------------------------|-------| +| Number of symbols ( $N_{PRS}$ ) | 6 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | 8 | + +##### **7.2.2.2.3 Modulation of the preamble for power lines** + +When using a default seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed that is section dependent as defined in Table 7-74. + +When using a "domain-specific" seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM in the DM\_Defined\_Seed field of the additional domain information auxiliary information field (see clause 8.8.5.15 of [ITU-T G.9961]). The DM shall choose the seed from the set of seeds corresponding to the DOD of the domain, as specified in Table 7-75). + +**Table 7-74 – Default constellation scrambler initialization seed values for the preamble, for power lines** + +| Medium | 1st section | 3rd section | +|-----------------------|--------------------|-------------| +| Power-line (Baseband) | 05FA 16 | N/A | + +**Table 7-75 – Set of domain-specific constellation scrambler initialization seed values for the preamble, for power-line** + +| DOD (Domain ID) | 1st Section | 3rd Section | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 0 | 000A 16 ; 158A 16 ; 080D 16 ;
1BF7 16 ; 08B8 16 ; 087E 16 ;
0D53 16 ; 0201 16 | N/A | +| 1 | 0227 16 ; 08E8 16 ; 0D14 16 ;
0005 16 ; 10FE 16 ; 1B33 16 ;
150E 16 ; 145B 16 | N/A | +| 2 | 0408 16 ; 0507 16 ; 182E 16 ;
01AB 16 ; 0987 16 ; 1CCE 16 ;
08B0 16 ; 1A25 16 | N/A | +| 3 | 06E2 16 ; 05E8 16 ; 135C 16 ;
1907 16 ; 0113 16 ; 1635 16 ;
0A88 16 ; 19AB 16 | N/A | +| 4 | 07FD 16 ; 02A9 16 ; 0173 16 ;
19CD 16 ; 0936 16 ; 00CA 16 ;
0EC3 16 ; 1037 16 | N/A | +| 5 | 094D 16 ; 0F04 16 ; 1791 16 ;
16BA 16 ; 155A 16 ; 0895 16 ;
0537 16 ; 189B 16 | N/A | +| 6 | 0A98 16 ; 1EFE 16 ; 1DB9 16 ;
14D7 16 ; 0AF1 16 ; 1B73 16 ;
1C5E 16 ; 166F 16 | N/A | + +**Table 7-75 – Set of domain-specific constellation scrambler initialization seed values for the preamble, for power-line** + +| DOD (Domain ID) | 1st Section | 3rd Section | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 7 | 0B0E 16 ; 0B26 16 ; 0614 16 ;
1E7D 16 ; 089A 16 ; 1922 16 ;
1DD7 16 ; 1D91 16 | N/A | +| 8 | 0D0A 16 ; 1843 16 ; 0D12 16 ;
0F1D 16 ; 07BA 16 ; 19C0 16 ;
08E4 16 ; 0984 16 | N/A | +| 9 | 0F88 16 ; 10A8 16 ; 050C 16 ;
1B6C 16 ; 183F 16 ; 0509 16 ;
0FFA 16 ; 1221 16 | N/A | +| 10 | 12EE 16 ; 0BE8 16 ; 0F4B 16 ;
156E 16 ; 0D0C 16 ; 1312 16 ;
1A56 16 ; 0BD0 16 | N/A | +| 11 | 1300 16 ; 0E3A 16 ; 02D3 16 ;
003F 16 ; 18EF 16 ; 06AC 16 ;
0AB6 16 ; 0CF5 16 | N/A | +| 12 | 14F0 16 ; 1C18 16 ; 122A 16 ;
0233 16 ; 132F 16 ; 051F 16 ;
1973 16 ; 01AD 16 | N/A | +| 13 | 1A2D 16 ; 1ABF 16 ; 0988 16 ;
1DA4 16 ; 1DCB 16 ; 0CFB 16 ;
065B 16 ; 1FAA 16 | N/A | +| 14 | 1CCF 16 ; 138B 16 ; 1F00 16 ;
153B 16 ; 1D56 16 ; 008D 16 ;
01C4 16 ; 17CF 16 | N/A | +| 15 | 1CE7 16 ; 11D6 16 ; 0D59 16 ;
05CE 16 ; 18C4 16 ; 06CF 16 ;
0F68 16 ; 1782 16 | N/A | + +##### 7.2.2.2.4 Modulation of the INUSE, PR and NACK signals for power lines + +The constellation scrambler LFSR generator shall be initialized at the beginning of the INUSE, PR and NACK signals to the same seed used for the 1st preamble section, as defined in Table 7-74 (default seed) and Table 7-75 (domain-specific seeds). + +##### 7.2.2.2.5 Modulation of the IDPS signal for power lines + +The inter-domain presence signal (IDPS) is used for the neighbouring domain interference mitigation (NDIM) mechanism (see clause 8.14 in [[ITU-T G.9961](#)]). + +The IDPS signal shall be generated in the same way as INUSE, PR and NACK signals (see clauses 7.1.4.5.3.1.2, 7.1.4.5.3.2.2 and 7.1.4.5.3.3.2). + +The constellation scrambler LFSR generator shall be initialized at the beginning of the IDPS signal to the seed 166C16. + +#### 7.2.2.3 PSD mask specifications + +See clause 6.2.2 of [[ITU-T G.9964](#)]. + +#### 7.2.2.4 Permanently masked subcarriers + +See clause 6.2.3 of [[ITU-T G.9964](#)]. + +### 7.2.3 Physical layer specification over coax + +#### 7.2.3.1 Control parameters + +See clause 6.3.1 of [[ITU-T G.9964](#)]. + +#### 7.2.3.2 Preamble, PR signal, and INUSE signal + +##### 7.2.3.2.1 Preamble structure + +Table 7-76 illustrates the preamble structure for coax. + +**Table 7-76 – Preamble structure for transmission over coax** + +| | 1st section | 2nd section | 3rd section | +|--------------------------------------------|-------------|-------------|-------------| +| Number of symbols ( $N_i$ ) | 10 | 4 | 2.5 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | $k_i = 4$ | $k_i = 4$ | $k_i = 1$ | + +Table 7-77 illustrates the preamble structure for coax RF. + +**Table 7-77 – Preamble structure for RF transmission over coax** + +| | 1st section | 2nd section | 3rd section | +|--------------------------------------------|-------------|-------------|-------------| +| Number of symbols ( $N_i$ ) | 10 | 4 | 2.5 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | $k_i = 4$ | $k_i = 4$ | $k_i = 1$ | + +##### 7.2.3.2.2 INUSE, PR and NACK signal generation parameters for coax + +Table 7-78 illustrates the INUSE, PR and NACK signal generation parameters for coax. + +**Table 7-78 – INUSE, PR and NACK signal generation parameters for coax** + +| Parameter | Value | +|--------------------------------------------|-------| +| Number of symbols ( $N_{PRS}$ ) | 9 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | 4 | + +Table 7-79 illustrates the INUSE, PR and NACK signal generation parameters for coax RF. + +**Table 7-79 – INUSE, PR and NACK signal generation parameters for coax RF** + +| Parameter | Value | +|--------------------------------------------|-------| +| Number of Symbols ( $N_{PRS}$ ) | 9 | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | 4 | + +##### 7.2.3.2.3 Modulation of the preamble for coax + +When using a default seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed that is section dependent as defined in Table 7-80. + +When using a "domain-specific" seed, the constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a + +set of seeds defined by the DM in the DM\_Defined\_Seed field of the additional domain information subfield (see clause 8.8.5.15 of [ITU-T G.9961]). + +**Table 7-80 – Default constellation scrambler initialization seed values for the preamble, for coax** + +| Medium | 1st section | 3rd section | +|-----------------|--------------------|--------------------| +| Coax (Baseband) | 16E6 16 | 1105 16 | +| Coax (RF) | 1C62 16 | 12C4 16 | + +Domain-specific constellation scrambler initialization seed values for the preamble for both coax and coax RF are for further study. + +##### 7.2.3.2.4 Modulation of the INUSE, PR and NACK signals for coax + +The constellation scrambler LFSR generator (see clause 7.1.4.3.3) shall be initialized at the beginning of the INUSE, PR and NACK signals to the same seed used for the 1st preamble section, as defined in Table 7-80. + +#### 7.2.3.3 PSD mask specifications + +See clause 6.3.2 of [ITU-T G.9964]. + +#### 7.2.3.4 Permanently masked subcarriers + +See clause 6.3.3 of [ITU-T G.9964]. + +#### 7.2.3.5 Coexistence on coax + +See clause 6.3.4 of [ITU-T G.9964]. + +### 7.2.4 Transmitter EVM requirements + +The deviation of the actual transmit signal from the corresponding constellation point shall be estimated by the value of error vector magnitude (EVM) calculated as: + +$$EVM = 20 \log \frac{error\_vector\_RMS}{reference\_signal}$$ + +The interpretation of EVM components for a constellation point is illustrated in Figure 7-28. + +![Figure 7-28: Interpretation of EVM. A vector diagram showing the relationship between a reference signal, an actual transmitted signal, and an error vector. The reference signal is a vector pointing to a '+' symbol. The actual transmitted signal is a vector pointing to a point slightly offset from the reference signal. The error vector is the vector difference between the actual transmitted signal and the reference signal. The diagram is labeled G.9960(11)_F7-28.](000c903c2d17433f5ef183ff4edc62fd_img.jpg) + +Figure 7-28: Interpretation of EVM. A vector diagram showing the relationship between a reference signal, an actual transmitted signal, and an error vector. The reference signal is a vector pointing to a '+' symbol. The actual transmitted signal is a vector pointing to a point slightly offset from the reference signal. The error vector is the vector difference between the actual transmitted signal and the reference signal. The diagram is labeled G.9960(11)\_F7-28. + +**Figure 7-28 – Interpretation of EVM** + +The EVM for a subcarrier at the output of a transceiver (i.e., at the MDI reference point), for at least 90% of active subcarriers, shall not exceed values presented in Table 7-81 at the maximum transmit power that the transceiver is capable of transmitting within a transmit PSD mask. + +**Table 7-81 – Maximum EVM values for different media and OFBs** + +| Medium | EVM (Note 1) | +|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| Baseband power line (Note 2) | –33 dB for $f \leq 30$ MHz
–3 dB for $f > 30$ MHz | +| Telephone line | –40 dB | +| Baseband coax | –40 dB | +| RF coax | –28 dB | +| NOTE 1 – Values of EVM shall be verified using standard termination impedance for each type of medium (see clause 7.2.5). | | +| NOTE 2 – EVM for LCP shall be –20 dB for all frequency ranges. | | + +### 7.2.5 Termination impedance + +See clause 6.4 of [[ITU-T G.9964](#)]. + +### 7.2.6 Total transmit power + +See clause 6.5 of [[ITU-T G.9964](#)]. + +### 7.2.7 Receiver input impedance + +See clause 6.6 of [[ITU-T G.9964](#)]. + +### 7.2.8 Longitudinal conversion loss + +The longitudinal conversion loss (LCL) of telecommunication lines or telecommunication ports is a measure of the degree of unwanted transversal signal produced at the terminals of the G.hn device due to the presence of a longitudinal signal on the connecting leads. + +The longitudinal voltage ( $V_{cm}$ ) to transversal voltage ( $V_{diff}$ ) ratio shall be measured in accordance with [[ITU-T G.117](#)] and [[ITU-T O.9](#)]. During the measurement, the transceiver under test shall be powered, and in L1 mode (see clause 8.21 of [[ITU-T G.9961](#)]). + +$$LCL = 20 \log_{10} \left| \frac{V_{cm}}{V_{diff}} \right| \text{dB}$$ + +The specification of LCL for mediums other than phoneline is for further study. + +#### 7.2.8.1 LCL for phoneline + +The LCL of the G.hn transceiver shall be greater than or equal to 38 dB in the frequency band up to 12 MHz. The LCL above 12 MHz is for further study. The termination impedance of the transceiver for LCL measurement shall be the one corresponding to the phoneline medium as stated in Table 6-11 of [[ITU-T G.9964](#)]. The LCL shall be measured at the MDI interface. LCL shall be measured in the frequency band between the lowest frequency (StartSubCarrier) and the highest frequency (StopSubCarrier) used by the transmitter (see Table 8-16.6 of [[ITU-T G.9961](#)]). + +NOTE – The equipment balance should be better than the anticipated access network balance in order to minimize the unwanted emissions and susceptibility to external RFI. + +# 8 Data link layer specification + +See clause 8 of [[ITU-T G.9961](#)]. + +# 9 Security + +See clause 9 of [[ITU-T G.9961](#)]. + +# 10 High capacity header physical layer specification (HCH-PHY) + +## 10.1 Medium independent specification + +### 10.1.1 Functional model of the PHY + +See clause 7.1.1 + +**Figure 10-1 – See Figure 7-1** + +(This figure has been intentionally left blank) + +### 10.1.2 Physical coding sublayer (PCS) + +See clause 7.1.2. + +**Figure 10-2 – See Figure 7-2** + +(This figure has been intentionally left blank) + +#### 10.1.2.1 PHY frame + +The format of the PHY frame for the half duplex (HDX) mode of operation is presented in Figure 10-3 and for the full duplex (FDX) mode of operation in Figure 10-3.1. The PHY frame at the $\alpha$ -reference point includes a header, and a payload. The preamble and additional channel estimation (ACE) symbols are added to the PHY frame in the PMD, as described in clauses 10.1.4.5 and 10.1.4.2.5, respectively. The preamble does not carry any user or management data and is intended for synchronization and initial channel estimation. The format of the preamble and header are the same for HDX and FDX modes of operation. + +![Figure 10-3: Format of an HDX PHY frame. The diagram shows a horizontal bar representing the PHY frame, divided into two main sections: 'Common HDX/FDX part' and 'HDX specific part'. The 'Common HDX/FDX part' contains 'Preamble' (yellow) and 'Header 1 or 2 symbols' (green). The 'HDX specific part' contains 'Additional channel estimation symbols' (yellow) and 'Payload' (white). The text 'G.9960(18)-Cor.2(20)_F10-3' is at the bottom right.](2eeee46b99394d7a37c46cd876e6cbc2_img.jpg) + +G.9960(18)-Cor.2(20)\_F10-3 + +Figure 10-3: Format of an HDX PHY frame. The diagram shows a horizontal bar representing the PHY frame, divided into two main sections: 'Common HDX/FDX part' and 'HDX specific part'. The 'Common HDX/FDX part' contains 'Preamble' (yellow) and 'Header 1 or 2 symbols' (green). The 'HDX specific part' contains 'Additional channel estimation symbols' (yellow) and 'Payload' (white). The text 'G.9960(18)-Cor.2(20)\_F10-3' is at the bottom right. + +**Figure 10-3– Format of an HDX PHY frame** + +![Figure 10-3.1: Format of an FDX PHY frame. The diagram shows two horizontal bars representing PHY frames. The top bar is 'Primary node transmission' and the bottom bar is 'Secondary node transmission'. Both bars are divided into 'Common HDX/FDX part' and 'HDX/FDX specific part'. The 'Common HDX/FDX part' contains 'Preamble' (yellow) and 'Header 1 or 2 symbols' (green). The 'HDX/FDX specific part' for the primary node contains 'Additional channel estimation symbols' (yellow) and 'Payload primary' (white). For the secondary node, the 'HDX/FDX specific part' contains 'Additional channel estimation symbols' (yellow), 'Header 1 or 2 symbols' (green), and 'Payload secondary' (white). The text 'G.9960(18)-Cor.2(20)_F10-3.1' is at the bottom right.](72d375793611d82866edc20cb031d867_img.jpg) + +G.9960(18)-Cor.2(20)\_F10-3.1 + +Figure 10-3.1: Format of an FDX PHY frame. The diagram shows two horizontal bars representing PHY frames. The top bar is 'Primary node transmission' and the bottom bar is 'Secondary node transmission'. Both bars are divided into 'Common HDX/FDX part' and 'HDX/FDX specific part'. The 'Common HDX/FDX part' contains 'Preamble' (yellow) and 'Header 1 or 2 symbols' (green). The 'HDX/FDX specific part' for the primary node contains 'Additional channel estimation symbols' (yellow) and 'Payload primary' (white). For the secondary node, the 'HDX/FDX specific part' contains 'Additional channel estimation symbols' (yellow), 'Header 1 or 2 symbols' (green), and 'Payload secondary' (white). The text 'G.9960(18)-Cor.2(20)\_F10-3.1' is at the bottom right. + +**Figure 10-3.1 – Format of an FDX PHY frame** + +The PHY-frame header and payload shall each contain an integer number of OFDM symbols. + +The PHY-frame header always fits into an integer number of symbols and is transmitted using a single predefined set of modulation and coding parameters (see clause 10.1.3.4). + +The presence of ACE symbols is frame type and duplexing mechanism dependent (see clause 10.1.2.3). + +The length of the payload may vary from frame to frame; the payload may be of zero length. For the payload, different coding parameters and bit loading can be used in different frames, depending on the channel/noise characteristics and QoS requirements. + +The types of PHY frames used in this Recommendation are summarized in Table 10-1. + +**Table 10-1 – PHY frame types** + +| Frame type | Header | Payload | Description | Reference | +|--------------------------------------------------------------------------------------------------|--------|---------|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------| +| MAP/RMAP | √ | √ | A frame carrying the MAP or RMAP; the payload contains an MPDU | Clause 10.1.2.3.2.1, clause 8.8 of [ ITU-T G.9961 ] | +| MSG | √ | √ | A frame carrying user data or management data or both; the payload contains an MPDU | Clause 10.1.2.3.2.2 | +| ACK | √ | None | An acknowledgement frame; the relevant ARQ data is communicated in the header | Clause 10.1.2.3.2.3 | +| RTS | √ | None | A request-to-send frame; the relevant data is communicated in the header | Clause 10.1.2.3.2.4 | +| CTS | √ | None | A clear-to-send frame; the relevant data is communicated in the header | Clause 10.1.2.3.2.5 | +| CTMG | √ | None | A frame carrying a short control message | Clause 10.1.2.3.2.6 | +| PROBE | √ | √ | A frame carrying probe symbols in its payload | Clause 10.1.2.3.2.7, clause 10.1.3.6 | +| ACKRQ | √ | None | An ACK retransmission request frame; the relevant data is communicated in the header | Clause 10.1.2.3.2.8 | +| BMSG | √ | √ | A bidirectional MSG frame | Clause 10.1.2.3.2.9, clause 8.3.7 of [ ITU-T G.9961 ] | +| BACK | √ | √ | A bidirectional ACK frame | Clause 10.1.2.3.2.10 , clause 8.3.7 of [ ITU-T G.9961 ] | +| ACTMG | √ | None | An acknowledgment frame for a CTMG frame | Clause 10.1.2.3.2.11 | +| FTE | √ | Note | Frame type extension | Clause 10.1.2.3.2.16 | +| NOTE – Whether a payload is present or not depends on the definition of the extended frame type. | | | | | + +#### 10.1.2.2 MPDU mapping + +See clause 7.1.2.2 + +#### 10.1.2.3 PHY-frame header + +The core part of the PHY-frame header is PHYH bits long (see clause 10.1.3.2.2). It is transmitted over $D$ (see clause 10.1.3.5.2) consecutive OFDM symbols, where $D = 1$ . The core part of the PHY-frame header is composed of a common part and a variable part. The common part contains fields that are common for all PHY-frame types. The variable part contains fields according to the PHY-frame type. The PHY-frame type is indicated by the FT field. The PAD fields fit the length of the + +header of different PHY frame-types to the standard value of PHYH bits. The content of the core part is protected by the 16-bit header check sequence (HCS). + +Whenever sub-clauses of clause 10 reference clause 7, the term PHYH is replaced by PHYHCH. + +The fields of the core part of the PHY-frame header are defined in Table 10-2. + +**Table 10-2 – Core part of the PHY-frame header** + +| Field | Octet | Bits | Description | Reference | +|----------|-----------|---------|----------------------------------------------------------------------------------------|---------------------| +| | | | | Common part | +| FT | 0 | [3:0] | Frame type | Clause 10.1.2.3.1.1 | +| DOD | | [7:4] | Domain ID | Clause 10.1.2.3.1.2 | +| SID | 1 | [7:0] | DEVICE_ID of the source node | Clause 10.1.2.3.1.3 | +| DID | 2 | [7:0] | DEVICE_ID, MULTICAST_ID or BROADCAST_ID of the destination node(s) | Clause 10.1.2.3.1.4 | +| MI | 3 | [0] | Multicast indication identifying whether the DID is a unicast or multicast destination | Clause 10.1.2.3.1.5 | +| DRI | | [1] | Duration indication identifying whether FTSF starts with a 16-bit duration field | Clause 10.1.2.3.1.6 | +| Reserved | | [2] | Reserved for ITU-T | Clause 10.1.2.3.1.7 | +| HSI | | [3] | Header segmentation indication | Clause 10.1.2.3.1.8 | +| Reserved | | [7:4] | Reserved by ITU-T (Note) | | +| | | | | Variable part | +| FTSF | 4 to 45 | [335:0] | Frame-type specific field | Clause 10.1.2.3.2 | +| | | | | Common part | +| HCS | 46 and 47 | [15:0] | Header check sequence | Clause 10.1.2.3.1.9 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +**Figure 10-4 – Placeholder for Figure** + +(This figure has been intentionally left blank) + +##### 10.1.2.3.1 Common part fields + +###### 10.1.2.3.1.1 Frame type (FT) + +See clause 7.1.2.3.1.1 + +**Table 10-3 – See Table 7-3** + +(This table has been intentionally left blank) + +###### 10.1.2.3.1.2 Domain ID (DOD) + +See clause 7.1.2.3.1.2 + +###### 10.1.2.3.1.3 Source ID (SID) + +See clause 7.1.2.3.1.3 + +###### **10.1.2.3.1.4 Destination ID (DID)** + +See clause 7.1.2.3.1.4 + +###### **10.1.2.3.1.5 Multicast indication (MI)** + +See clause 7.1.2.3.1.5 + +###### **10.1.2.3.1.6 Duration indication (DRI)** + +If the DRI bit is set to one, the FTSF shall start with a duration field. If this bit is set to zero, the PHY frame shall not contain any payload (i.e., contains only preamble and PHY-frame header). + +The duration field contains the duration of a single PHY frame or PHY frame sequence. It shall be represented as a 16-bit unsigned integer with valid values in steps of 0.25 $\mu$ s. It shall be the smallest integer larger than or equal to the actual duration. The duration field is defined separately depending on the frame type. If a node detects a PHY frame with unknown frame type, the node shall assume for its virtual carrier sense that the channel will be occupied for that duration. After that time there shall be an inter-frame gap equal to the $T_{\text{IFG\_MIN}}$ corresponding to that TXOP + +**Table 10-4 – Value of DRI for different frame types** + +| Frame type | Value of DRI | +|-------------------|---------------------| +| MAP/RMAP | one | +| MSG | one | +| ACK | zero | +| RTS | one | +| CTS | one | +| PROBE | one | +| ACKRQ | zero | +| BMSG | one | +| BACK | one | +| CTMG | zero | +| ACTMG | zero | +| FTE | zero or one | + +###### **10.1.2.3.1.7 Reserved** + +**Table 10-5 – Placeholder for table** + +(This table has been intentionally left blank) + +###### **10.1.2.3.1.8 Header segmentation indication (HSI)** + +See clause 7.1.2.3.1.8 + +###### **10.1.2.3.1.9 Header check sequence (HCS)** + +See clause 7.1.2.3.1.9 + +##### **10.1.2.3.2 Variable part fields** + +See clause 7.1.2.3.2 + +### 10.1.2.3.2.1 MAP and RMAP PHY-frame type specific fields + +Table 10-6 lists the PHY-frame header fields which are specific to the MAP and RMAP frame type. + +**Table 10-6 – MAP and RMAP PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|-----------|---------|--------------------------------------------------|------------------------| +| MAP_DUR | 0 and 1 | [15:0] | Duration for MAP frame | Clause 10.1.2.3.2.1.1 | +| NTR | 2 to 5 | [31:0] | Network time reference | Clause 10.1.2.3.2.1.2 | +| CYCSTART | 6 to 9 | [31:0] | MAC cycle start time | Clause 10.1.2.3.2.1.3 | +| Reserved | 10 and 11 | [11:0] | Reserved by ITU-T | | +| SI | | [15:12] | Scrambler initialization | Clause 10.1.2.3.2.1.5 | +| BLKSZ | 12 | [1:0] | Block size of FEC codeword for MAP frame payload | Clause 10.1.2.3.2.1.6 | +| REP | | [4:2] | Number of repetitions for encoding payload | Clause 10.1.2.3.2.1.7 | +| FCF | | [7:5] | FEC concatenation factor | Clause 10.1.2.3.2.1.8 | +| OFB_ID | 13 | [2:0] | Operational Frequency Band Identifier | Clause 10.1.2.3.2.1.9 | +| MAP_TYPE | | [3] | MAP type | Clause 10.1.2.3.2.1.10 | +| RMAPI | | [4] | RMAP indication | Clause 10.1.2.3.2.1.11 | +| Reserved | | [7:5] | Reserved by ITU-T (Note) | | +| NUM_HOPS | 14 | [3:0] | Number of hops from domain master | Clause 10.1.2.3.2.1.12 | +| Reserved | | [7:4] | Reserved by ITU-T (Note) | | +| KMIN | 15 | [7:0] | $k_{min}$ for payload repetition encoding | Clause 10.1.2.3.2.1.13 | +| Reserved | 16 to 41 | [207:0] | 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. + +#### 10.1.2.3.2.1.1 Duration for MAP frame (MAP\_DUR) + +See clause 7.1.2.3.2.1.1 + +#### 10.1.2.3.2.1.2 Network time reference (NTR) + +See clause 7.1.2.3.2.1.2 + +#### 10.1.2.3.2.1.3 MAC cycle start time (CYCSTART) + +See clause 7.1.2.3.2.1.3 + +#### 10.1.2.3.2.1.4 Reserved + +#### 10.1.2.3.2.1.5 Scrambler initialization (SI) + +See clause 7.1.2.3.2.1.5 + +#### 10.1.2.3.2.1.6 Block size (BLKSZ) + +See clause 7.1.2.3.2.1.6 + +**Table 10-7 – See Table 7-7** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.1.7 Repetitions (REP)** + +See clause 7.1.2.3.2.1.7 + +**Table 10-8 – See Table 7-8** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.1.8 FEC concatenation factor (FCF)** + +See clause 7.1.2.3.2.1.8 + +**Table 10-9 – See Table 7-9** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.1.9 Operational Frequency Band identifier (OFB\_ID)** + +The OFB\_ID field shall contain the identifier for the operational frequency band used by the node. It is a 3-bit field that shall be coded as shown in Table 10-10. + +**Table 10-10 – Operational Frequency Band identifier** + +| OFB_ID value
(b7b6b5) | Description | +|-------------------------------------------------------------------|--------------------| +| 000 | Reserved by ITU-T | +| 001 | 25 MHz | +| 010 | 50 MHz | +| 011 | 100 MHz | +| 100 | 200 MHz | +| 101 | K-OFB | +| 110 and 111 | Reserved by ITU-T | + +#### **10.1.2.3.2.1.10 MAP type (MAP\_TYPE)** + +See clause 10.1.2.3.2.1.10 + +#### **10.1.2.3.2.1.11 RMAP indication (RMAP\_I)** + +See clause 7.1.2.3.2.1.11 + +#### **10.1.2.3.2.1.12 Number of hops from domain master (NUM\_HOPS)** + +See clause 7.1.2.3.2.1.12 + +#### **10.1.2.3.2.1.13 kmin for payload repetition encoding** + +The KMIN field shall contain the value to be used to calculate the number of OFDM symbols needed to transmit the RCM encoded codeword (see clause 10.1.3.3.1). + +The value of KMIN field shall be coded as shown in table 10-10.1 + +**Table 10-10.1 – Possible values of kmin** + +| Value of KMIN field | Kmin | +|--------------------------------------|-------------------| +| 00 16 | 1024 | +| 01 16 | 2048 | +| 02 16 | 3072 | +| 03 16 | 4096 | +| 04 16 | 6144 | +| 05 16 | 8192 | +| 06 16 | 12288 | +| 07 16 | 17408 | +| 08 16 to FF 16 | Reserved by ITU-T | + +#### 10.1.2.3.2.2 MSG PHY-frame type specific fields + +Table 10-11 lists the PHY-frame header fields which are specific to the MSG frame type. + +**Table 10-11 – MSG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|---------------|---------|--------|-----------------------------------------------------------------------------|----------------------------| +| MSG_DUR | 0 and 1 | [15:0] | Duration for MSG frame | Clause 10.1.2.3.2.2.1 | +| BLKSZ/LPDUSZ | 2 | [1:0] | Block size of FEC codeword for MSG frame payload/LPDU size for a connection | Clause 10.1.2.3.2.2.2 | +| FEC_RATE | | [4:2] | FEC coding rate for MSG frame payload | Clause 10.1.2.3.2.2.3 | +| REP | | [7:5] | Number of repetitions used for encoding the MSG frame payload | Clause 10.1.2.3.2.2.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 10.1.2.3.2.2.5 | +| SI | | [6:3] | Scrambler initialization | Clause 10.1.2.3.2.2.6 | +| MDET | | [7] | Master is detected | Clause 10.1.2.3.2.2.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 10.1.2.3.2.2.8 | +| OFB_ID/GRP_ID | | [7:5] | Operational Frequency Band identifier/subcarrier grouping identifier | Clause 10.1.2.3.2.2.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 10.1.2.3.2.2.1
0 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of an MSG frame | Clause 10.1.2.3.2.2.1
1 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 10.1.2.3.2.2.1
2 | +| RPRQ | 7 | [1:0] | Reply required | Clause 10.1.2.3.2.2.1
3 | + +**Table 10-11 – MSG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|------------------|-----------|-------------|-------------------------------------------------------------------------------|-------------------------------------| +| BRSTCnt | | [3:2] | Burst frame count | Clause 10.1.2.3.2.2.1
4 | +| BEF | | [4] | Burst end flag | Clause 10.1.2.3.2.2.1
5 | +| AIFG_IND | | [5] | AIFG indication | Clause 10.1.2.3.2.2.1
6 | +| Reserved | | [6] | Reserved | Reserved for use by
ITU-T G.9963 | +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 10.1.2.3.2.2.2
5 | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 10.1.2.3.2.2.1
7 | +| CNN_MNGMT | | [6:3] | Connection management | Clause 10.1.2.3.2.2.1
8 | +| Reserved | | [7] | Reserved | Reserved by ITU-T
(Note 1) | +| BRURQ | 9 and 10 | [15:0] | Bandwidth reservation update
request | Clause 10.1.2.3.2.2.1
9 (Note 2) | +| START_SSN | 9 and 10 | [15:0] | Start segment sequence number | Clause 10.1.2.3.2.2.2
0 (Note 3) | +| CURRTS | 11 | [6:0] | Current TS | Clause 10.1.2.3.2.2.2
1 | +| BTXRQ | | [7] | Request for bidirectional
transmission | Clause 10.1.2.3.2.2.2
2 | +| NUM_MCACK_SLOTS | 12 | [2:0] | Number of Mc-ACK slots | Clause 10.1.2.3.2.2.2
3 | +| ADVISED_WIN_SIZE | | [7:3] | In connection establishment this
field may specify advised
window size. | Clause 10.1.2.3.2.2.2
4 (Note 4) | +| Reserved | 13 | [0] | Reserved | Reserved for use by
ITU-T G.9991 | +| AIFGD_TYPE | | [1] | AIFGD Type | Clause
10.1.2.3.2.2.16 | +| Reserved | | [7:2] | Reserved | Reserved by ITU-T
(Note 1) | +| KMIN | 14 | [7:0] | $k_{min}$ for payload repetition
encoding | Clause
10.1.2.3.2.2.27 | +| Reserved | 15 and 41 | [215:
0] | Reserved | Reserved by ITU-T
(Note 1) | + +NOTE 1 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +NOTE 2 – The BRURQ field is defined when the START\_SSN field is not defined (see Note 3). + +NOTE 3 – The START\_SSN field is defined only when CNN\_MNGMT = 0001, CNN\_MNGMT = 0011, CNN\_MNGMT = 0101 or CNN\_MNGMT = 0111. Otherwise, the meaning of this field is BRURQ. + +**Table 10-11 – MSG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------|-------------|-----------| +| NOTE 4 – The ADVISED_WIN_SIZE field is defined only when CNN_MNGMT = 0101, otherwise these bits are reserved by ITU-T and shall be set to zero by the transmitter and ignored by the receiver. | | | | | + +**10.1.2.3.2.2.1 Duration for MSG frame (MSG\_DUR)** + +See clause 7.1.2.3.2.2.1 + +**10.1.2.3.2.2.2 Block size/LPDU size (BLKSZ/LPDUSZ)** + +For frames not involved in the establishment of a connection this field contains BLKSZ, the information block size of the FEC codeword that is used for the payload of the MSG frame. It is a 2-bit field that shall be coded as shown in Table 10-7. + +For frames involved in the establishment of a connection (CNN\_MNGMT = 0001, CNN\_MNGMT = 0010, CNN\_MNGMT = 0101 or CNN\_MNGMT = 0110) this field contains LPDUSZ, indicating the LPDU size selected for a new connection during the establishment of connections as defined in clause 8.12 of [[ITU-T G.9961](#)]. + +LPDUSZ is a 2-bit field that shall be coded as shown in Table 10-11.1. + +**Table 10-11.1 – LPDUSZ field values** + +| LPDUSZ value (b 1 b 0 ) | Interpretation | +|-----------------------------------------------|--------------------| +| 00 | 120-byte LPDU | +| 01 | 540-byte LPDU | +| 10 | 2160-byte LPDU | +| 11 | Reserved for ITU-T | + +**10.1.2.3.2.2.3 FEC coding rate (FEC\_RATE)** + +See clause 7.1.2.3.2.2.3 + +**Table 10-12 – See Table 7-12** + +(This table has been intentionally left blank) + +**10.1.2.3.2.2.4 Repetitions (REP)** + +See clause 7.1.2.3.2.2.4 + +**10.1.2.3.2.2.5 FEC concatenation factor (FCF)** + +See clause 7.1.2.3.2.2.5 + +**10.1.2.3.2.2.6 Scrambler initialization (SI)** + +See clause 7.1.2.3.2.2.6 + +**10.1.2.3.2.2.7 Master is detected indication (MDET)** + +See clause 7.1.2.3.2.2.7 + +#### **10.1.2.3.2.2.8 Bit allocation table identifier (BAT\_ID)** + +See clause 7.1.2.3.2.2.8 + +#### **10.1.2.3.2.2.9 Operational frequency band identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +For predefined BATs with uniform loading (type 0, type 1, type 2 and Type 3), the OFB\_ID/GRP\_ID field shall contain the identifier for the operational frequency band used by the node and shall be coded as shown in Table 10-10. Otherwise, it shall contain the subcarrier grouping (see clause 10.1.4.2.4) and shall be coded as shown in Table 10-13. + +**Table 10-13 – Format of the GRP\_ID field** + +| GRP_ID value
(b7b6b5) | Description | +|-------------------------------------------------------------------|---------------------------------------| +| 000 | Default – No subcarrier grouping | +| 001 | Subcarrier grouping of 2 subcarriers | +| 010 | Subcarrier grouping of 4 subcarriers | +| 011 | Subcarrier grouping of 8 subcarriers | +| 100 | Subcarrier grouping of 16 subcarriers | +| 101 | Subcarrier grouping of 32 subcarriers | +| 110 | Subcarrier grouping of 64 subcarriers | +| 111 | Reserved by ITU-T | + +#### **10.1.2.3.2.2.10 Guard interval identifier (GI\_ID)** + +See clause 7.1.2.3.2.2.10 + +**Table 10-14 – See Table 7-14** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.2.11 Maximum actual PSD of MSG frame (APSD\_MAX-M)** + +See clause 7.1.2.3.2.2.11. + +#### **10.1.2.3.2.2.12 Connection identifier (CONNECTION\_ID)** + +See clause 7.1.2.3.2.2.12. + +#### **10.1.2.3.2.2.13 Reply required (RPRQ)** + +See clause 7.1.2.3.2.2.13 + +**Table 10-15 – See Table 7-15** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.2.14 Burst frame count (BRSTCnt)** + +See clause 7.1.2.3.2.2.14. + +#### **10.1.2.3.2.2.15 Burst end flag (BEF)** + +See clause 7.1.2.3.2.2.15. + +#### **10.1.2.3.2.2.16 AIFG indication (AIFG\_IND)** + +For unicast, if the AIFG\_IND field is set to one, the receiver-specific AIFG value, $T_{\text{AIFG}}$ , shall be used by the transmitter. If the AIFG\_IND field is set to zero, a default AIFG shall be used. The receiver shall ACK this frame, whenever Imm-ACK is used, after either $T_{\text{AIFG}}$ , $T_{\text{AIFG-D}}$ or one of the default AIFGs (see clause 10.1.2.3.2.2.26) as indicated by AIFG\_IND. + +For multicast, the AIFG\_IND field shall always be set to zero. + +#### **10.1.2.3.2.2.17 ACE symbols (ACE\_SYM)** + +See clause 7.1.2.3.2.2.17. + +#### **Table 10-16 – See Table 7-16** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.2.18 Connection management (CNN\_MNGMT)** + +See clause 7.1.2.3.2.2.18. + +#### **Table 10-17 – See Table 7-17** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.2.19 Bandwidth reservation update request (BRURQ)** + +The BRURQ field shall contain updates in the bandwidth reserved for this node connection. It is a 16-bit field that shall be coded as shown in Table 10-18. The domain master shall follow the BRURQ fields of all nodes (see clause 8.6.2.2 of [[ITU-T G.9961](#)]). + +**Table 10-18 – Format of the BRURQ field** + +| Field | Octet | Bits | Description | +|--------------|-------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ConnState | 0 | [7:0] | Contains the number of accumulated bytes in the connection queue. This value is specified in units of Kbytes, expressed as ceiling (number of bytes/1024). | +| FlowLineRate | 1 | [7:0] | Indicates the current PHY data rate in bytes/symbol. The range of valid values and the corresponding valid increments (see Table 10-19) depend on the medium. This value is expressed as floor (number of transmitted bytes per symbol/increment) (Note). | + +NOTE – Bytes/symbol value shall be calculated by applying the same formula and rules as Note 1 of Table 8-48 of [ITU-T G.9961](#) and multiplying the result by the symbol period ( $T_{\text{OFDM}}$ as defined in clause 10.1.4.4.4) and dividing by 8. DM shall consider this figure as an indication of the average throughput taking into account the different tone maps used in the MAC cycle. + +**Table 10-19 – Valid increments for BRURQ field** + +| Type | Increment | +|---------------------------------|-----------| +| Power line | 32 bytes | +| Telephone line (Profile 1 OFBs) | 16 bytes | +| Telephone line (Profile 2 OFBs) | 128 bytes | +| Coax (Profile 1 OFBs) | 4 bytes | +| Coax (Profile 2 OFBs) | 32 bytes | + +**10.1.2.3.2.2.20 Start segment sequence number (START\_SSN)** + +See clause 7.1.2.3.2.2.20. + +**10.1.2.3.2.2.21 Current TS (CURRTS)** + +See clause 7.1.2.3.2.2.21. + +**10.1.2.3.2.2.22 Request for bidirectional transmission (BTXRQ)** + +See clause 7.1.2.3.2.2.22. + +**10.1.2.3.2.2.23 Number of Mc-ACK slots (NUM\_MCACK\_SLOTS)** + +See clause 7.1.2.3.2.2.23. + +**10.1.2.3.2.2.24 Advised Window Size (ADVISED\_WIN\_SIZE)** + +See clause 7.1.2.3.2.2.24. + +**10.1.2.3.2.2.25 APSD\_MAX-M extension** + +See clause 10.1.2.3.2.2.11. + +**10.1.2.3.2.2.26 AIFGD\_TYPE** + +For unicast, if the AIFGD\_TYPE field is set to one, the per receiver default AIFG value $T_{\text{AIFG-DR}}$ assigned to the receiver, shall be used by the transmitter. If the AIFGD\_TYPE field is set to zero, the default AIFG value $T_{\text{AIFG-D}}$ , shall be used. + +For multicast, the AIFGD\_TYPE field shall always be set to zero. + +#### 10.1.2.3.2.2.27 $k_{min}$ for payload repetition encoding + +See clause 10.1.2.3.2.1.13. + +#### 10.1.2.3.2.3 ACK PHY-frame type specific fields + +Table 10-20 lists the PHY-frame header fields which are specific to the core part of the PHY-frame header of the ACK frame type. + +**Table 10-20 – ACK PHY frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------------------------------|----------|-----------|----------------------------------------------------------------------------------|----------------------------------| +| FLCTRL_CONN | 0 | [0] | Flow control connection flag | Clause 10.1.2.3.2.3.1 | +| FLCTRLT | | [1] | Flow control type | Clause 10.1.2.3.2.3.2 | +| FLCTRL | | [6:2] | Flow control | Clause 10.1.2.3.2.3.3 | +| FLCTRL_EXT | | [7] | Flow control extension | Clause 10.1.2.3.2.3.1
1 | +| RXRST_DATA | 1 | [0] | Data RX reset flag | Clause 10.1.2.3.2.3.5 | +| RXRST_MNGMT | | [1] | Management RX reset flag | Clause 10.1.2.3.2.3.6 | +| BAD_BURST | | [2] | Bad burst indication | Clause 10.1.2.3.2.3.7 | +| BTXRQ | | [3] | Request for bidirectional transmission | Clause 10.1.2.3.2.3.4 | +| Reserved | | [4] | Reserved | Reserved by ITU-T (Note 2) | +| Reserved | | [7:5] | Reserved | Reserved for use by ITU-T G.9991 | +| ACK_CE_CTRL/
RX_CONN_WIN_SIZE | 2 | [6:0] | ACK channel estimation control/Receiver window size for the connection. (Note 1) | Clause 10.1.2.3.2.3.8 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T G.9963 | +| ACKDATA/MCACK_D | 3 to 23 | [163:0] | Acknowledgement data and Mc-ACK descriptor | Clause 10.1.2.3.2.3.9 | +| Reserved | | [166:164] | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | | [167] | Reserved | Reserved by ITU-T (Note 2) | +| Reserved | 24 to 41 | [143:0] | Reserved | Reserved by ITU-T (Note 2) | + +NOTE 1 – This field is interpreted as RX\_CONN\_WIN\_SIZE only when the ACK frame is sent as a reply for MSG frame requesting set-up or reset of either a data or a management connection (i.e., when CNN\_MNGMT in the MSG frame is 01012, 00012, 00112 or 01112). + +NOTE 2 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +##### 10.1.2.3.2.3.1 Flow control connection flag (FLCTRL\_CONN) + +See clause 7.1.2.3.2.3.1. + +##### 10.1.2.3.2.3.2 Flow control type (FLCTRLT) + +See clause 7.1.2.3.2.3.2 + +**Table 10-21 – See Table 7-21** + +(This table has been intentionally left blank) + +**10.1.2.3.2.3.3 Flow control (FLCTRL)** + +The FLCTRL field shall be used for flow control between the transmitter and the receiver as described in clause 8.12.4 of [[ITU-T G.9961](#)]. Interpretation of the FLCTRL field depends on the setting of the FLCTRLT field. + +If the FLCTRLT field is set to zero (status report), the FLCTRL field shall contain the number of LPDUs that the receiver can buffer for this flow. It is a 5-bit field that shall be coded as shown in Table 10-22. + +**Table 10-22 – FLCTRL field values for status report** + +| FLCTRL value
(b6b5b4b3b2) | Connections with
2160 byte LPDUs | Connections with
540 byte LPDUs | Connections with
120 byte LPDUs | +|---------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------------------------|--------------------------------------------| +| 00000 | 2 | 4 | 6 | +| 00001 | 4 | 8 | 12 | +| 00010 | 6 | 12 | 18 | +| 00011 | 8 | 16 | 24 | +| 00100 | 10 | 20 | 30 | +| 00101 | 12 | 24 | 36 | +| 00110 | 14 | 28 | 42 | +| 00111 | 16 | 32 | 48 | +| 01000 | 20 | 40 | 60 | +| 01001 | 24 | 48 | 72 | +| 01010 | 28 | 56 | 84 | +| 01011 | 32 | 64 | 96 | +| 01100 | 36 | 72 | 108 | +| 01101 | 40 | 80 | 120 | +| 01110 | 44 | 88 | 132 | +| 01111 | 52 | 104 | 156 | +| 10000 | 60 | 120 | 180 | +| 10001 | 68 | 136 | 204 | +| 10010 | 76 | 152 | 228 | +| 10011 | 84 | 168 | 252 | +| 10100 | 92 | 184 | 276 | +| 10101 | 100 | 200 | 300 | +| 10110 | 108 | 216 | 324 | +| 10111 | 116 | 232 | 348 | +| 11000 | 124 | 248 | 372 | +| 11001 | 132 | 264 | 396 | +| 11010 | 140 | 280 | 420 | +| 11011 | 148 | 296 | 444 | + +**Table 10-22 – FLCTRL field values for status report** + +| FLCTRL value
(b 6 b 5 b 4 b 3 b 2 ) | Connections with
2160 byte LPDUs | Connections with
540 byte LPDUs | Connections with
120 byte LPDUs | +|-----------------------------------------------------------------------------------------------|-------------------------------------|------------------------------------|------------------------------------| +| 11100 | 156 | 312 | 468 | +| 11101 | 164 | 328 | 492 | +| 11110 | 172 | 344 | 516 | +| 11111 | 188 | 376 | 564 | + +If the FLCTRLT field is set to one (hold time/management), the FLCTRL field shall contain either the time period that the transmitter shall hold transmissions to this node, or connection management information (see clause 8.12 of [[ITU-T G.9961](#)]). It is a 5-bit field that shall be coded as shown in Table 10-23. + +**Table 10-23 – FLCTRL field values for hold time/management** + +| FLCTRL value
(b 6 b 5 b 4 b 3 b 2 ) | Interpretation | +|-----------------------------------------------------------------------------------------------|-------------------------------| +| Hold times | | +| 00000 | Until next MAC cycle | +| 00001 | 5 ms | +| 00010 | 10 ms | +| 00011 | 15 ms | +| 00100 | 20 ms | +| 00101 | 30 ms | +| 00110 | 40 ms | +| 00111 | 50 ms | +| 01000 to 11011 | Reserved by ITU-T | +| Management | | +| 11100 | Release acknowledgement | +| 11101 | Connection release indication | +| 11110 | Connection accepted | +| 11111 | Unavailability of resources | + +The receiver shall set the FLCTRLT field to one to convey the following connection management information (see clause 8.12 of [[ITU-T G.9961](#)]): + +- If the transmitter has requested the release of a connection, the receiver shall acknowledge the release by setting the FLCTRL field to 111002. +- If the receiver wants to release a connection, it shall inform the transmitter by setting the FLCTRL field to 111012. +- If the receiver accepts a requested connection, it shall inform the transmitter by setting the FLCTRL field to 111102. +- If the receiver does not have resources available for a requested connection, it shall inform the transmitter by setting the FLCTRL field to 111112. + +#### **10.1.2.3.2.3.4 Request for bidirectional transmission (BTXRQ)** + +See clause 7.1.2.3.2.3.4. + +#### **10.1.2.3.2.3.5 Data RX reset flag (RXRST\_DATA)** + +See clause 7.1.2.3.2.3.5. + +#### **10.1.2.3.2.3.6 Management RX reset flag (RXRST\_MNGMT)** + +See clause 7.1.2.3.2.3.6. + +#### **10.1.2.3.2.3.7 Bad burst indication (BAD\_BURST)** + +See clause 7.1.2.3.2.3.7. + +#### **10.1.2.3.2.3.8 ACK channel estimation control/Receiver window size for the connection (ACK\_CE\_CTRL/RX\_CONN\_WIN\_SIZE)** + +See clause 7.1.2.3.2.3.8 + +### **Table 10-24 – See Table 7-24** + +(This table has been intentionally left blank) + +### **Table 10-25 – See Table 7-25** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.3.8.1 ACK channel estimation control type (ACK\_CE\_CTRL\_TYPE)** + +See clause 7.1.2.3.2.3.8.1. + +#### **10.1.2.3.2.3.8.2 Runtime BAT ID (RUNTIME\_BAT\_ID)** + +See clause 7.1.2.3.2.3.8.2. + +#### **10.1.2.3.2.3.9 Acknowledgement data and Mc-ACK descriptor (ACKDATA/MCACK\_D)** + +See clause 7.1.2.3.2.3.9. + +##### **10.1.2.3.2.3.9.1 ACKDATA** + +The ACKDATA field for different cases shall be coded as shown in Tables 10-26, 10-27, 10-28 and 10-29. + +**Table 10-26 – Unicast ACKDATA specific fields when MNMTP is set to zero** + +| Field | Octet | Bits | +|----------------------------|--------------|-------------| +| FACK | 0 to 38 | [2:0] | +| CONNECTION_ID | | [10:3] | +| MNMTP | | [11] | +| LSSN | | [23:12] | +| ACKI | | [163:24] | +| Reserved (See Table 10-20) | | [311:64] | + +**Table 10-27 – Unicast ACKDATA specific fields when MNMTP is set to one** + +| Field | Octet | Bits | +|----------------------------|---------|-------------------------------------| +| FACK | 0 to 38 | [2:0] | +| CONNECTION_ID | | [10:3] | +| MNMTP | | [11] | +| MNMT_LSSN | | [17:12] | +| MNMTL | | [22:18] | +| MNMT_ACKI | | [(MNMTL_VALUE+22):23] | +| LSSN | | [(MNMTL_VALUE+34):(MNMTL_VALUE+23)] | +| ACKI | | [163:(MNMTL_VALUE+35)] | +| Reserved (see Table 10-20) | | [311:164] | + +**Table 10-28 – Multicast ACKDATA specific fields when MNMTP is set to zero** + +| Field | Octet | Bits | +|------------------------------------|---------|-----------| +| Mc-ACK descriptor (see Table 7-35) | 0 to 38 | [11:0] | +| FACK | | [14:12] | +| CONNECTION_ID | | [22:15] | +| MNMTP | | [23] | +| LSSN | | [35:24] | +| ACKI | | [163:36] | +| Reserved (see Table 10-20) | | [311:164] | + +**Table 10-29 – Multicast ACKDATA specific fields when MNMTP is set to one** + +| Field | Octet | Bits | +|-------------------------------------|---------|-------------------------------------| +| Mc-ACK descriptor (see Table 10-35) | 0 to 38 | [11:0] | +| FACK | | [14:12] | +| CONNECTION_ID | | [22:15] | +| MNMTP | | [23] | +| MNMT_LSSN | | [29:24] | +| MNMTL | | [34:30] | +| MNMT_ACKI | | [(MNMTL_VALUE+34):35] | +| LSSN | | [(MNMTL_VALUE+46):(MNMTL_VALUE+35)] | +| ACKI | | [163:(MNMTL_VALUE+47)] | +| Reserved (see Table 10-20) | | [311:164] | + +The format of the FACK field shall be as described in clause 10.1.2.3.2.3.9.1.5. When selective acknowledgment is used, the FACK field shall indicate the format of the ACKI field. + +#### 10.1.2.3.2.3.9.1.1 Management LSSN presence indication (MNMTP) + +See clause 7.1.2.3.2.3.9.1.1. + +#### 10.1.2.3.2.3.9.1.2 ACKDATA when MNMTP is set to zero + +See clause 7.1.2.3.2.3.9.1.2. + +#### **10.1.2.3.2.3.9.1.3 ACKDATA when MNMTP is set to one** + +See clause 7.1.2.3.2.3.9.1.3. + +##### **10.1.2.3.2.3.9.1.3.1 Management lowest SSN (MNMT\_LSSN)** + +See clause 7.1.2.3.2.3.9.1.3.1 + +##### **10.1.2.3.2.3.9.1.3.2 Management ACKI length (MNMTL)** + +See clause 7.1.2.3.2.3.9.1.3.2. + +##### **10.1.2.3.2.3.9.1.3.3 Management bit map encoding (MNMT\_ACKI)** + +See clause 7.1.2.3.2.3.9.1.3.3. + +#### **10.1.2.3.2.3.9.1.4 Connection identifier (CONNECTION\_ID)** + +See clause 7.1.2.3.2.3.9.1.4. + +#### **10.1.2.3.2.3.9.1.5 Frame ACK (FACK)** + +See clause 7.1.2.3.2.3.9.1.5 + +### **Table 10-30 – See Table 7-30** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.3.9.1.6 Lowest SSN (LSSN)** + +See clause 7.1.2.3.2.3.9.1.6. + +#### **10.1.2.3.2.3.9.1.7 ACK information (ACKI)** + +The reception status of data units consisting of one or more segments shall be indicated in the ACKI field by the receiver. The data unit corresponding to each indication in the ACKI field depends on the format of the ACKI field (see Table 10-30). The indication corresponding to a data unit shall be set to one if the data unit was not received correctly and shall be set to zero if the data unit was received correctly. For the cases of bit map encoding and group encoding, if there is no more information to encode, the remaining bits of this field (if any) shall be encoded by the receiver to indicate that the rest of the data units have been received with errors. For the case of run-length encoding, if there is no more information to encode, the remaining bits of this field (if any) shall be encoded to indicate that the rest of the groups in the field have a length of zero. The specific encoding for different formats of the ACKI field is as explained in the following clauses. + +If the number of bits in the ACKI field is not sufficient to indicate reception status of all the received segments, a receiver may choose to use compressed encoding or limit the indication to the number of available bits. Segments corresponding to data units for which the reception status was not reported shall be considered by the transmitter as either not received correctly by the receiver or in waiting-for-ack state. + +##### **10.1.2.3.2.3.9.1.7.1 Bit map encoding** + +See clause 7.1.2.3.2.3.9.1.7.1. + +##### **10.1.2.3.2.3.9.1.7.2 Compressed encoding** + +See clause 7.1.2.3.2.3.9.1.7.2. + +###### **10.1.2.3.2.3.9.1.7.2.1 Run-length encoding** + +See clause 7.1.2.3.2.3.9.1.7.2.1. + +#### **Table 10-31 – See Table 7-31** + +(This table has been intentionally left blank) + +#### **Table 10-32 – See Table 7-32** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.3.9.1.7.2.2 Group encoding** + +See clause 7.1.2.3.2.3.9.1.7.2.2 + +#### **Table 10-33 – See Table 7-33** + +(This table has been intentionally left blank) + +#### **Table 10-34 – See Table 7-34** + +(This table has been intentionally left blank) + +#### **10.1.2.3.2.3.9.2 Mc-ACK descriptor (MCACK\_D)** + +See clause 7.1.2.3.2.3.9.2. + +#### **Table 10-35 – See Table 7-35** + +(This Table has been intentionally left blank) + +#### **10.1.2.3.2.3.10 Reserved** + +#### **10.1.2.3.2.3.11 Flow control extension (FLCTRL\_EXT)** + +The FLCTRL\_EXT field shall be used to indicate higher values of flow control between the transmitter and the receiver as described in clause 8.12.4 of [\[ITU-T G.9961\]](#), compared to those indicated by the field FLCTRL as described in clause 10.1.2.3.2.3.3. This field FLCTRL\_EXT shall be set to one only if the field FLCTRLT is set to 0 (see clause 10.1.2.3.2.3.2). If FLCTRL\_EXT is set to one, for connections with 2160 byte LPDUs 204 is added, for connections with 540 byte LPDUs 408 is added and for connections with 120 byte LPDUs 612 is added to the value indicated by the FLCTRL (see clause 10.1.2.3.2.3.3) value to determine the actual number of LPDUs that the receiver can buffer for the flow. For example, for a connection with 540 byte LPDUs, if FLCTRL\_EXT is set and FLCTRL is set to 000112 the receiver indicates that it can buffer (408 + 16 = 424) LPDUs. + +#### **10.1.2.3.2.4 RTS PHY-frame type specific fields** + +Table 10-36 lists the PHY-frame header fields which are specific to the RTS frame type: + +**Table 10-36 – RTS PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|------------------------|----------------------------------| +| RTS_DUR | 0 and 1 | [15:0] | Duration for RTS frame | Clause 10.1.2.3.2.4.1 | +| CID | 2 | [7:0] | CTS proxy ID | Clause 10.1.2.3.2.4.2 | +| CURRTS | 3 | [6:0] | Current TS | Clause 10.1.2.3.2.4.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 4 | [7:0] | Reserved | Reserved for use by ITU-T G.9991 | +| Reserved | 5 to 41 | [295:0] | Reserved | 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. + +#### 10.1.2.3.2.4.1 Duration for RTS frame (RTS\_DUR) + +See clause 7.1.2.3.2.4.1 + +#### 10.1.2.3.2.4.2 CTS proxy ID (CID) + +See clause 7.1.2.3.2.4.2 + +#### 10.1.2.3.2.4.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +#### 10.1.2.3.2.5 CTS PHY-frame type specific fields + +Table 10-37 lists the header fields which are specific to the CTS frame type. + +**Table 10-37 – Specific fields of the CTS PHY-frame type** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|------------------------|--------------------------| +| CTS_DUR | 0 and 1 | [15:0] | Duration for CTS frame | Clause 10.1.2.3.2.5.1 | +| Reserved | 2 to 41 | [319:0] | Reserved | 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. + +#### 10.1.2.3.2.5.1 Duration for CTS frame (CTS\_DUR) + +See clause 7.1.2.3.2.5.1. + +#### 10.1.2.3.2.6 CTMG PHY-frame type specific fields + +Table 10-38 lists the PHY-frame header fields which are specific to the CTMG frame type. + +**Table 10-38 – CTMG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|-----------------------------------|--------------------------| +| IACKRQ | 0 | [0] | Immediate acknowledgment required | Clause 10.1.2.3.2.6.1 | +| CURRTS | | [7:1] | Current TS | Clause 10.1.2.3.2.6.3 | +| Reserved | 1 to 4 | [31:0] | Reserved | Reserved by ITU-T (Note) | +| CTMGD | 5 to 41 | [295:0] | CTMG data | Clause 10.1.2.3.2.6.2 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +#### 10.1.2.3.2.6.1 Immediate acknowledgment required (IACKRQ) + +See clause 7.1.2.3.2.6.1. + +#### 10.1.2.3.2.6.2 CTMG data (CTMGD) + +CTMGD field shall contain a single control message composed of a CMH and a CMPL field as shown in clause 8.10.2 of [ITU-T G.9961]. If the size of the control message is shorter than the size of CTMGD (296 bits), the remainder of the CTMGD field shall be padded with zeros. + +#### 10.1.2.3.2.6.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +#### 10.1.2.3.2.7 PROBE PHY-frame type specific fields + +The PROBE PHY-frame type specific field is composed of a common part and a variable part. The common part contains fields that are common for all PROBE PHY-frame types (PRBTYPES). The variable part contains fields that are specific to each PRBTYPE. + +The fields of the common part of the PROBE PHY-frame specific field are defined in Table 10-39. + +**Table 10-39 – PROBE PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-------------------------------------------------------------------------------------------------------------|----------|---------|---------------------------------|----------------------------------| +| Common part | | | | | +| PRB_DUR | 0 and 1 | [15:0] | Duration for PROBE frame | Clause 10.1.2.3.2.7.1.1 | +| PRBTYPE | 2 | [3:0] | PROBE frame type | Clause 10.1.2.3.2.7.1.2 | +| PRBSYM | | [7:4] | Probe symbols | Clause 10.1.2.3.2.7.1.3 | +| APSD_MAX-P | 3 | [4:0] | APSD_MAX-P of a PROBE frame | Clause 10.1.2.3.2.7.1.4 | +| PRBGI | | [7:5] | PROBE guard interval | Clause 10.1.2.3.2.7.1.5 | +| CURRTS | 4 | [6:0] | Current TS | Clause 10.1.2.3.2.7.1.6 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T G.9963 | +| APSD_MAX-P_EXT | 5 | [0] | APSD_MAX-P extension | Clause 10.1.2.3.2.7.1.7 | +| Reserved | | [7:1] | Reserved | Reserved by ITU-T (Note) | +| Variable part | | | | | +| PFTSF | 6 to 14 | [71:0] | PROBE frame type specific field | Clause 10.1.2.3.2.7.2 | +| Reserved | 15 to 41 | [215:0] | Reserved | Reserved by ITU-T | +| NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. | | | | | + +#### 10.1.2.3.2.7.1 Common part fields + +##### 10.1.2.3.2.7.1.1 Duration for PROBE frame (PRB\_DUR) + +See clause 7.1.2.3.2.7.1.1. + +##### 10.1.2.3.2.7.1.2 PROBE frame type (PRBTYPE) + +See clause 7.1.2.3.2.7.1.2. + +**Table 10-40 – See Table 7-40** + +(This table has been intentionally left blank) + +**10.1.2.3.2.7.1.3 Probe symbols (PRBSYM)** + +See clause 7.1.2.3.2.7.1.3. + +**Table 10-41 – See Table 7-41** + +(This table has been intentionally left blank) + +**10.1.2.3.2.7.1.4 Maximum actual PSD of PROBE frame (APSD\_MAX-P)** + +See clause 7.1.2.3.2.7.1.4. + +**10.1.2.3.2.7.1.5 PROBE symbol guard interval (PRBGI)** + +See clause 7.1.2.3.2.7.1.5. + +**10.1.2.3.2.7.1.6 Current TS (CURRTS)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +**10.1.2.3.2.7.1.7 APSD\_MAX-P extension** + +See clause 7.1.2.3.2.7.1.7. + +**10.1.2.3.2.7.2 PROBE frame type specific field** + +See clause 7.1.2.3.2.7.2. + +**10.1.2.3.2.7.2.1 Silent PROBE frame specific fields** + +See clause 7.1.2.3.2.7.2.1 + +**Table 10-42 – See Table 7-42** + +(This table has been intentionally left blank) + +**10.1.2.3.2.7.2.2 Channel estimation PROBE frame specific fields** + +See clause 7.1.2.3.2.7.2.2 + +**Table 10-43 – See Table 7-43** + +(This table has been intentionally left blank) + +**Table 10-44 – See Table 7-44** + +(This table has been intentionally left blank) + +### 10.1.2.3.2.8 ACKRQ PHY frame type specific fields + +Table 10-45 lists the PHY-frame header fields which are specific to the ACKRQ frame type. + +**Table 10-45 – ACKRQ PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|---------------|---------|---------|-----------------------|--------------------------| +| RX_WIN_TYPE | 0 | [1:0] | Requested RX window | Clause 10.1.2.3.2.8.1 | +| Reserved | | [7:2] | Reserved | Reserved by ITU-T (Note) | +| CONNECTION_ID | 1 | [7:0] | Connection identifier | Clause 10.1.2.3.2.8.2 | +| CURRTS | 2 | [6:0] | Current TS | Clause 10.1.2.3.2.8.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| Reserved | 3 to 41 | [311:0] | Reserved | 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. + +#### 10.1.2.3.2.8.1 Requested RX window (RX\_WIN\_TYPE) + +See clause 7.1.2.3.2.8.1 + +**Table 10-46 – See Table 7-46** + +(This table has been intentionally left blank) + +#### 10.1.2.3.2.8.2 Connection identifier (CONNECTION\_ID) + +See clause 7.1.2.3.2.8.2. + +#### 10.1.2.3.2.8.3 Current TS (CURRTS) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +### 10.1.2.3.2.9 BMSG PHY-frame type specific fields + +Table 10-47 lists the fields which are specific to the core part of the PHY-frame header of the BMSG frame type. + +**Table 10-47 – BMSG PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|--------|----------------------------------------------------------------|-----------------------| +| BMSG_DUR | 0 and 1 | [15:0] | Duration for BMSG frame | Clause 10.1.2.3.2.9.1 | +| BLKSZ | 2 | [1:0] | Block size of FEC codeword for BMSG frame payload | Clause 10.1.2.3.2.9.2 | +| FEC_RATE | | [4:2] | FEC coding rate for BMSG frame payload | Clause 10.1.2.3.2.9.3 | +| REP | | [7:5] | Number of repetitions used for encoding the BMSG frame payload | Clause 10.1.2.3.2.9.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 10.1.2.3.2.9.5 | + +**Table 10-47 – BMSG PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|----------------|-----------|---------|----------------------------------------------------------------------|------------------------------------| +| SI | | [6:3] | Scrambler initialization | Clause 10.1.2.3.2.9.6 | +| MDET | | [7] | Master is detected | Clause 10.1.2.3.2.9.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 10.1.2.3.2.9.8 | +| OFB_ID/GRP_ID | | [7:5] | Operational frequency band identifier/subcarrier grouping identifier | Clause 10.1.2.3.2.9.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 10.1.2.3.2.9.10 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of a BMSG frame | Clause 10.1.2.3.2.9.11 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 10.1.2.3.2.9.12 | +| RPRQ | 7 | [1:0] | Reply required | Clause 10.1.2.3.2.9.13 | +| BRSTCnt | | [3:2] | Burst frame count | Clause 10.1.2.3.2.9.14 | +| BEF | | [4] | Burst end flag | Clause 10.1.2.3.2.9.15 | +| AIFG_IND | | [5] | AIFG indication | Clause 10.1.2.3.2.9.16 | +| Reserved | | [6] | Reserved | Reserved for use by ITU-T G.9963 | +| Reserved | | [7] | Reserved | Reserved for use by ITU-T (Note 1) | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 10.1.2.3.2.9.17 | +| CNN_MNGMT | | [6:3] | Connection management | Clause 10.1.2.3.2.9.18 | +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 10.1.2.3.2.9.27 | +| BRURQ | 9 and 10 | [15:0] | Bandwidth reservation update request | Clause 10.1.2.3.2.9.19 (Note 2) | +| START_SSN | 9 and 10 | [15:0] | Start segment sequence number | Clause 10.1.2.3.2.9.20 (Note 3) | +| CURRTS | 11 | [6:0] | Current TS | Clause 10.1.2.3.2.9.21 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note 1) | +| Reserved | 12 and 13 | [0] | Reserved | Reserved by ITU-T (Note 1) | +| BTXGL | | [8:1] | Bidirectional transmission grant length | Clause 10.1.2.3.2.9.22 | +| BTXEF | | [9] | Bidirectional transmission end flag | Clause 10.1.2.3.2.9.23 | +| P-DACK | | [10] | Piggybacked Delayed Acknowledgement | Clause 10.1.2.3.2.9.26 | +| Reserved | | [15:11] | Reserved | Reserved by ITU-T (Note 1) | + +**Table 10-47 – BMSG PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------|-------------------------------------------|----------------------------| +| ACK_CE_CTRL | 14 | [7:0] | ACK channel estimation control | Clause 10.1.2.3.2.9.24 | +| RXRST_DATA | 15
and 16 | [0] | Data RX reset flag | Clause 10.1.2.3.2.9.28 | +| RXRST_MNGMT | | [1] | Management RX reset flag | Clause 10.1.2.3.2.9.29 | +| FLCTRLT | | [2] | Flow control type | Clause 10.1.2.3.2.9.30 | +| FLCTRL | | [7:3] | Flow control | Clause 10.1.2.3.2.9.31 | +| Reserved | | [8] | Reserved | Reserved by ITU-T (Note 1) | +| FLCTRL_CONN | | [9] | Flow control connection flag | Clause 10.1.2.3.2.9.32 | +| Reserved | 17 to 28 | [15:10] | Reserved | Reserved by ITU-T (Note 1) | +| ACKDATA_BM | | [90:0] | Acknowledgement data of the BMSG frame | Clause 10.1.2.3.2.9.33 | +| Reserved | | [95:91] | Reserved | Reserved by ITU-T (Note 1) | +| AIFGD_TYPE | 29 | [0] | AIFGD Type | Clause 10.1.2.3.2.9.34 | +| Reserved | | [7:1] | Reserved | Reserved by ITU-T (Note 1) | +| KMIN | 30 | [7:0] | $k_{min}$ for payload repetition encoding | Clause 10.1.2.3.2.9.35 | +| Reserved | 31 to 41 | [87:0] | Reserved | Reserved by ITU-T (Note 1) | +| NOTE 1 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver.
NOTE 2 – The BRURQ field is defined when the START_SSN field is not defined.
NOTE 3 – The START_SSN field is defined only when CNN_MNGMT = 0001, CNN_MNGMT = 0011, CNN_MNGMT = 0101 or CNN_MNGMT = 0111. Otherwise, the meaning of this field is BRURQ. | | | | | + +#### **10.1.2.3.2.9.1 Duration for BMSG frame (BMSG\_DUR)** + +See clause 7.1.2.3.2.9.1. + +#### **10.1.2.3.2.9.2 Block size (BLKSZ)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.2, the BLKSZ field of the MSG frame. + +#### **10.1.2.3.2.9.3 FEC coding rate (FEC\_RATE)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.3, the FEC\_RATE field of the MSG frame. + +#### **10.1.2.3.2.9.4 Repetitions (REP)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.4, the REP field of the MSG frame. + +#### **10.1.2.3.2.9.5 FEC concatenation factor (FCF)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.5, the FCF field of the MSG frame. + +#### **10.1.2.3.2.9.6 Scrambler initialization (SI)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.6, the SI field of the MSG frame. + +#### **10.1.2.3.2.9.7 Master is detected indication (MDET)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.7, the MDET field of the MSG frame. + +#### **10.1.2.3.2.9.8 Bit allocation table identifier (BAT\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.8, the BAT\_ID field of the MSG frame. + +#### **10.1.2.3.2.9.9 Operational frequency band identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.9, the OFB\_ID/GRP\_ID field of the MSG frame. + +#### **10.1.2.3.2.9.10 Guard interval identifier (GI\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.10, the GI\_ID field of the MSG frame. + +#### **10.1.2.3.2.9.11 Maximum actual PSD of BMSG frame (APSD\_MAX-M)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.11, the APSD\_MAX-M field of the MSG frame. + +#### **10.1.2.3.2.9.12 Connection identifier (CONNECTION\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.12, the CONNECTION\_ID field of the MSG frame. + +#### **10.1.2.3.2.9.13 Reply required (RPRQ)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.13, the RPRQ field of the MSG frame. + +#### **10.1.2.3.2.9.14 Burst frame count (BRSTCnt)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.14, the BRSTCnt field of the MSG frame. + +#### **10.1.2.3.2.9.15 Burst end flag (BEF)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.15, the BEF field of the MSG frame. + +#### **10.1.2.3.2.9.16 AIFG indication (AIFG\_IND)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.16, the AIFG\_IND field of the MSG frame. + +#### **10.1.2.3.2.9.17 ACE symbols (ACE\_SYM)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.17, the ACE\_SYM field of the MSG frame. + +#### **10.1.2.3.2.9.18 Connection management (CNN\_MNGMT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.18, the CNN\_MNGMT field of the MSG frame. + +#### **10.1.2.3.2.9.19 Bandwidth reservation update request (BRURQ)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.19, the BRURQ field of the MSG frame. + +#### **10.1.2.3.2.9.20 Start segment sequence number (START\_SSN)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.20, the START\_SSN field of the MSG frame. + +#### **10.1.2.3.2.9.21 Current TS (CURRTS)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +#### **10.1.2.3.2.9.22 Bidirectional transmission grant length (BTXGL)** + +See clause 7.1.2.3.2.9.22. + +#### **10.1.2.3.2.9.23 Bidirectional transmission end flag (BTXEF)** + +See clause 7.1.2.3.2.9.23. + +#### **10.1.2.3.2.9.24 ACK channel estimation control (ACK\_CE\_CTRL)** + +The interpretation of this field shall be as specified for the ACK\_CE\_CTRL field of the ACK frame in clause 10.1.2.3.2.3.8. + +#### **10.1.2.3.2.9.25 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.2.9.26 Piggybacked Delayed Acknowledgement (P-DACK)** + +See clause 7.1.2.3.2.9.26. + +#### **10.1.2.3.2.9.27 APSD\_MAX-M extension** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.25, the APSD\_MAX-M\_EXT field of the MSG frame. + +#### **10.1.2.3.2.9.28 Data RX reset flag (RXRST\_DATA)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.5, the RXRST\_DATA field of the ACK frame. + +#### **10.1.2.3.2.9.29 Management RX reset flag (RXRST\_MNGMT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.6, RXRST\_MNGMT field of the ACK frame. + +#### **10.1.2.3.2.9.30 Flow control type (FLCTRLT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.2, the FLCTRLT field of the ACK frame. + +#### **10.1.2.3.2.9.31 Flow control (FLCTRL)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.3, the FLCTRL field of the ACK frame. + +#### **10.1.2.3.2.9.32 Flow control connection flag (FLCTRL\_CONN)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.1, the FLCTRL\_CONN field of the ACK frame. + +#### 10.1.2.3.2.9.33 Acknowledgement data of the BMSG frame (ACKDATA\_BM) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.9, the ACKDATA/MCACK\_D field of the ACK frame for unicast acknowledgment (MI = 0). + +#### 10.1.2.3.2.9.34 AIFG Type (AIFGD\_TYPE) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.26. + +#### 10.1.2.3.2.9.35 $k_{min}$ for payload repetition encoding + +See clause 10.1.2.3.2.1.13. + +#### 10.1.2.3.2.10 BACK PHY-frame type specific fields + +Table 10-48 lists the fields which are specific to the core part of the PHY-frame header of the BACK frame type. + +**Table 10-48 – BACK PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|----------------|---------|--------|----------------------------------------------------------------------|----------------------------------| +| BACK_DUR | 0 and 1 | [15:0] | Duration for BACK frame | Clause 10.1.2.3.2.10.1 | +| BLKSZ | 2 | [1:0] | Block size of FEC codeword for BACK frame payload | Clause 10.1.2.3.2.10.2 | +| FEC_RATE | | [4:2] | FEC coding rate for BACK frame payload | Clause 10.1.2.3.2.10.3 | +| REP | | [7:5] | Number of repetitions used for encoding the BACK frame payload | Clause 10.1.2.3.2.10.4 | +| FCF | 3 | [2:0] | FEC concatenation factor | Clause 10.1.2.3.2.10.5 | +| SI | | [6:3] | Scrambler initialization | Clause 10.1.2.3.2.10.6 | +| MDET | | [7] | Master is detected | Clause 10.1.2.3.2.10.7 | +| BAT_ID | 4 | [4:0] | Bit allocation table identifier | Clause 10.1.2.3.2.10.8 | +| OFB_ID/GRP_ID | | [7:5] | Operational frequency band identifier/subcarrier grouping identifier | Clause 10.1.2.3.2.10.9 | +| GI_ID | 5 | [2:0] | Guard interval identifier | Clause 10.1.2.3.2.10.10 | +| APSD_MAX-M | | [7:3] | APSD_MAX-M of a BACK frame | Clause 10.1.2.3.2.10.11 | +| CONNECTION_ID | 6 | [7:0] | Connection identifier | Clause 10.1.2.3.2.10.12 | +| RPRQ | 7 | [1:0] | Reply required | Clause 10.1.2.3.2.10.13 | +| BRSTCnt | | [3:2] | Burst frame count | Clause 10.1.2.3.2.10.14 | +| BEF | | [4] | Burst end flag | Clause 10.1.2.3.2.10.15 | +| AIFG_IND | | [5] | AIFG indication | Clause 10.1.2.3.2.10.16 | +| Reserved | | [6] | Reserved | Reserved for use by ITU-T G.9963 | +| APSD_MAX-M_EXT | | [7] | APSD_MAX-M extension | Clause 10.1.2.3.2.10.21 | +| ACE_SYM | 8 | [2:0] | Number of ACE symbols | Clause 10.1.2.3.2.10.17 | + +**Table 10-48 – BACK PHY-frame type specific fields – core part** + +| Field | Octet | Bits | Description | Reference | +|-------------|----------|---------|-------------------------------------------|----------------------------| +| CNN_MNGMT | | [6:3] | Connection management | Clause 10.1.2.3.2.10.18 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| BTXRL | 9 | [7:0] | Bidirectional transmission request length | Clause 10.1.2.3.2.10.19 | +| ACK_CE_CTRL | 10 | [6:0] | ACK channel estimation control | Clause 10.1.2.3.2.10.20 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| RXRST_DATA | 11 | [0] | Data RX reset flag | Clause 10.1.2.3.2.10.21 | +| RXRST_MNGMT | and 12 | [1] | Management RX reset flag | Clause 10.1.2.3.2.10.22 | +| FLCTRLT | | [2] | Flow control type | Clause 10.1.2.3.2.10.23 | +| FLCTRL | | [7:3] | Flow control | Clause 10.1.2.3.2.10.24 | +| Reserved | | [8] | Reserved | Reserved by ITU-T (Note) | +| FLCTRL_CONN | | [9] | Flow control connection flag | Clause 10.1.2.3.2.10.25 | +| Reserved | | [15:10] | Reserved | Reserved by ITU-T (Note) | +| ACKDATA_BA | 13 to 24 | [90:0] | Acknowledgement data of the BACK frame | Clause 10.1.2.3.2.10.26 | +| Reserved | | [95:91] | Reserved | Reserved by ITU-T (Note) | +| AIFGD_TYPE | 25 | [0] | AIFGD Type | Clause 10.1.2.3.2.10.27 | +| Reserved | | [7:1] | Reserved | Reserved by ITU-T (Note 1) | +| KMIN | 26 | [7:0] | $k_{min}$ for payload repetition encoding | Clause 10.1.2.3.2.10.28 | +| Reserved | 27 to 41 | [119:0] | Reserved | 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. + +#### 10.1.2.3.2.10.1 Duration for BACK frame (BACK\_DUR) + +See clause 7.1.2.3.2.10.1. + +#### 10.1.2.3.2.10.2 Block size (BLKSZ) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.2, the BLKSZ field of the MSG frame. + +#### 10.1.2.3.2.10.3 FEC coding rate (FEC\_RATE) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.3, the FEC\_RATE field of the MSG frame. + +#### 10.1.2.3.2.10.4 Repetitions (REP) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.4, the REP field of the MSG frame. + +#### 10.1.2.3.2.10.5 FEC concatenation factor (FCF) + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.5, the FCF field of the MSG frame. + +#### **10.1.2.3.2.10.6 Scrambler initialization (SI)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.6, the SI field of the MSG frame. + +#### **10.1.2.3.2.10.7 Master is detected indication (MDET)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.7, the MDET field of the MSG frame. + +#### **10.1.2.3.2.10.8 Bit allocation table identifier (BAT\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.8, the BAT\_ID field of the MSG frame. + +#### **10.1.2.3.2.10.9 Operational frequency band identifier/subcarrier grouping identifier (OFB\_ID/GRP\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.9, the OFB\_ID/GRP\_ID field of the MSG frame. + +#### **10.1.2.3.2.10.10 Guard interval identifier (GI\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.10, the GI\_ID field of the MSG frame. + +#### **10.1.2.3.2.10.11 Maximum actual PSD of BACK frame (APSD\_MAX-M)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.11, the APSD\_MAX-M field of the MSG frame. + +#### **10.1.2.3.2.10.12 Connection identifier (CONNECTION\_ID)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.12, the CONNECTION\_ID field of the MSG frame. + +#### **10.1.2.3.2.10.13 Reply required (RPRQ)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.13, the RPRQ field of the MSG frame. + +#### **10.1.2.3.2.10.14 Burst frame count (BRSTCnt)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.14, the BRSTCnt field of the MSG frame. + +#### **10.1.2.3.2.10.15 Burst end flag (BEF)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.15, the BEF field of the MSG frame. + +#### **10.1.2.3.2.10.16 AIFG indication (AIFG\_IND)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.16, the AIFG\_IND field of the MSG frame. + +#### **10.1.2.3.2.10.17 ACE symbols (ACE\_SYM)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.17, the ACE\_SYM field of the MSG frame. + +#### **10.1.2.3.2.10.18 Connection management (CNN\_MNGMT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.18, the CNN\_MNGMT field of the MSG frame. + +#### **10.1.2.3.2.10.19 Bidirectional transmission request length (BTXRL)** + +See clause 7.1.2.3.2.10.19. + +#### **10.1.2.3.2.10.20 ACK channel estimation control (ACK\_CE\_CTRL)** + +See clause 7.1.2.3.2.10.20. + +#### **10.1.2.3.2.10.21 APSD\_MAX-M extension** + +See clause 7.1.2.3.2.10.21. + +#### **10.1.2.3.2.10.22 Data RX reset flag (RXRST\_DATA)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.5, the RXRST\_DATA field of the ACK frame. + +#### **10.1.2.3.2.10.23 Management RX reset flag (RXRST\_MNGMT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.6, the RXRST\_MNGMT field of the ACK frame. + +#### **10.1.2.3.2.10.24 Flow control type (FLCTRLT)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.2, the FLCTRLT field of the ACK frame. + +#### **10.1.2.3.2.10.25 Flow control (FLCTRL)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.3, the FLCTRL field of the ACK frame. + +#### **10.1.2.3.2.10.26 Flow control connection flag (FLCTRL\_CONN)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.1, the FLCTRL\_CONN field of the ACK frame. + +#### **10.1.2.3.2.10.27 Acknowledgement data of the BACK frame (ACKDATA\_BA)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.3.9, the ACKDATA/MCACK\_D field of the ACK frame for unicast acknowledgment (MI = 0). + +#### **10.1.2.3.2.10.28 AIFG Type (AIFGD\_TYPE)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.26. + +#### **10.1.2.3.2.10.29 $k_{min}$ for payload repetition encoding** + +See clause 10.1.2.3.2.1.13. + +### **10.1.2.3.2.11 ACTMG PHY-frame type specific fields** + +Table 10-49 lists the PHY-frame header fields which are specific to the ACTMG frame type. + +**Table 10-49 – ACTMG PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-------------------------------------------------------------------------------------------------------------|---------|---------|---------------------|--------------------------| +| CTMGACK | 0 to 41 | [0] | CTMG acknowledgment | Clause 10.1.2.3.2.11.1 | +| Reserved | | [335:1] | Reserved | 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. | | | | | + +An ACTMG frame shall be sent following a CTMG frame that has its IACKRQ field set to one (see clause 10.1.2.3.2.6.1) indicating that immediate acknowledgment is required. + +#### **10.1.2.3.2.11.1 CTMG acknowledgment (CTMGACK)** + +See clause 7.1.2.3.2.11.1. + +#### **10.1.2.3.2.12 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.2.13 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.2.14 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.2.15 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.2.16 FTE PHY-frame type specific fields** + +This frame type is used for adding additional frame types (i.e., frame type extension). + +Table 10-50 lists the PHY-frame header fields which are specific to the FTE frame type. + +**Table 10-50 – FTE PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|---------|---------|------------------------|--------------------------| +| FTE_DUR | 0 and 1 | [15:0] | Duration for FTE frame | Clause 10.1.2.3.2.16.1 | +| CURRTS | 2 | [6:0] | Current TS | Clause 10.1.2.3.2.16.3 | +| Reserved | | [7] | Reserved | Reserved by ITU-T (Note) | +| EFT_FLD | 3 to 41 | [311:0] | EFT specific fields | Clause 10.1.2.3.2.16.2 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +##### **10.1.2.3.2.16.1 Duration for FTE frame (FTE\_DUR)** + +See clause 7.1.2.3.2.16.1. + +##### **10.1.2.3.2.16.2 EFT specific fields (EFT\_FLD)** + +See clause 7.1.2.3.2.16.2. + +##### **10.1.2.3.2.16.3 Current TS (CURRTS)** + +The interpretation of this field shall be as specified in clause 10.1.2.3.2.2.21, the CURRTS field of the MSG frame. + +#### **10.1.2.3.3 Reserved** + +Reserved by ITU-T. + +**Table 10-51 – Placeholder for table** +(This table has been intentionally left blank) + +#### **10.1.2.3.3.1 Reserved** + +##### **10.1.2.3.3.1.1 Reserved** + +Reserved by ITU-T. + +**Table 10-52 – Placeholder for table** + +(This table has been intentionally left blank) + +**10.1.2.3.3.1.1.1 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2 Reserved** + +Reserved by ITU-T. + +**Table 10-53 – Placeholder for table** + +(This table has been intentionally left blank) + +--- + +**10.1.2.3.3.1.2.1 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2.2 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2.3 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2.4 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2.5 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.2.6 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.3 Reserved** + +**Table 10-54 – Placeholder for table** + +(This table has been intentionally left blank) + +--- + +**10.1.2.3.3.1.3.1 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.3.2 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.3.3 Reserved** + +Reserved by ITU-T. + +**10.1.2.3.3.1.3.4 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.3.1.3.5 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.3.1.3.6 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.3.1.4 Reserved** + +Table 10-54.1 lists the E\_FTSF for ACK PHY frame. + +**Table 10-54.1 – Placeholder for a table** +(This table has been intentionally left blank) + +#### **10.1.2.3.3.1.4.1 Reserved** + +Reserved by ITU-T. + +#### **10.1.2.3.3.2 Reserved** + +Reserved by ITU-T. + +### **10.1.3 Physical medium attachment (PMA) sublayer** + +See clause 7.1.3. + +**Figure 10-5 – See Figure 7-5** +(This figure has been intentionally left blank) + +#### **10.1.3.1 Scrambling** + +See clause 7.1.3.1. + +**Figure 10-6 – See Figure 7-6** +(This figure has been intentionally left blank) + +#### **10.1.3.2 FEC encoding** + +See clause 7.1.3.2. + +**Figure 10-7 – See Figure 7-7** +(This Figure has been intentionally left blank) + +#### **10.1.3.2.1 LDPC-BC encoder** + +The code rate of the mother code, $R_M = K/N_M$ , is determined by a $(N_M - K) \times N_M$ size parity-check matrix **H** composed by an array of $c \times t$ circulant $b \times b$ sub-matrices $\mathbf{A}_{i,j}$ : + +$$\mathbf{H} = \begin{bmatrix} \mathbf{A}_{1,1} & \mathbf{A}_{1,2} & \cdots & \mathbf{A}_{1,t} \\ \mathbf{A}_{2,1} & \mathbf{A}_{2,2} & \cdots & \mathbf{A}_{2,t} \\ \vdots & \vdots & \ddots & \vdots \\ \mathbf{A}_{c,1} & \mathbf{A}_{c,2} & \cdots & \mathbf{A}_{c,t} \end{bmatrix}$$ + +The parameters $c, t$ ( $0 < c \leq t$ ) imply a rate $R_M = (t - c)/t$ . By selecting different sets of $c, t$ , different rates can be obtained. + +The sub-matrices $\mathbf{A}_{i,j}$ are either a rotated identity or a zero matrix and have a size of $b \times b$ , where parameter $b = N_M/t$ is called the expansion factor of $\mathbf{H}$ and controls the code block size, $N_M$ . + +The parity-check matrix, $\mathbf{H}$ , is described in its compact form: + +$$\mathbf{H}_c = \begin{bmatrix} a_{1,1} & a_{1,2} & \cdots & a_{1,t} \\ a_{2,1} & a_{2,2} & \cdots & a_{2,t} \\ \vdots & \vdots & \ddots & \vdots \\ a_{c,1} & a_{c,2} & \cdots & a_{c,t} \end{bmatrix}$$ + +A zero sub-matrix in position $(i,j)$ is labelled with $a_{i,j} = -1$ , and a rotated identity sub-matrix is labelled with a positive integer number $a_{i,j}$ defining the number of right column shifts of the identity matrix. + +This Recommendation defines one matrix for each mother code rate and block size. + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_{\text{HCH}}$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 768$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 19 | 18 | -1 | -1 | -1 | 19 | 12 | -1 | -1 | -1 | 6 | 20 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 10 | -1 | 7 | 29 | 22 | -1 | -1 | -1 | 28 | 13 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 14 | 20 | 19 | 23 | -1 | -1 | 0 | 28 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 13 | -1 | 18 | 28 | 7 | -1 | -1 | -1 | 1 | 4 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 9 | 27 | -1 | -1 | -1 | 0 | 31 | -1 | -1 | -1 | 2 | 6 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| 22 | 19 | -1 | -1 | -1 | 23 | 3 | 5 | -1 | -1 | 30 | -1 | 15 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| 7 | -1 | -1 | -1 | 2 | 24 | 2 | 15 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| 15 | -1 | -1 | 3 | 3 | -1 | -1 | -1 | 31 | 29 | 29 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 16 | -1 | 19 | 6 | -1 | -1 | 17 | 18 | 6 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| 12 | -1 | 2 | 20 | 16 | -1 | -1 | 2 | -1 | 5 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | +| -1 | -1 | -1 | 5 | 3 | 21 | -1 | -1 | 4 | 3 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| -1 | -1 | -1 | 1 | 11 | 27 | 19 | -1 | -1 | 11 | 21 | -1 | 15 | 25 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | + +Whenever sub-clauses of clause 10 reference clause 7, the term $(1/2)_{\text{H}}$ is replaced by $(1/2)_{\text{HCH}}$ . + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_{\text{S}}$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 1920$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| 27 | -1 | -1 | -1 | 55 | 19 | -1 | 30 | -1 | -1 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 0 | -1 | 1 | -1 | 70 | -1 | 47 | -1 | 62 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 41 | -1 | -1 | -1 | 44 | -1 | -1 | 59 | 60 | 25 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 16 | 77 | -1 | -1 | -1 | 5 | -1 | 48 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 45 | -1 | 27 | -1 | 46 | 19 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 63 | -1 | -1 | -1 | 55 | -1 | -1 | -1 | 48 | 26 | 10 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 42 | -1 | 21 | -1 | 58 | -1 | 41 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | -1 | 78 | 0 | -1 | 7 | 52 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | +| -1 | 29 | 9 | -1 | -1 | -1 | 37 | -1 | -1 | 35 | 21 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | +| -1 | -1 | 22 | 72 | -1 | -1 | 47 | -1 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | +| 35 | -1 | -1 | -1 | -1 | 13 | -1 | 35 | -1 | 70 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | +| -1 | 46 | 28 | -1 | -1 | -1 | 38 | -1 | -1 | -1 | 8 | -1 | 10 | 58 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | + +The compact form $\mathbf{H}_c$ of parity-check matrix $(1/2)_{\text{L}}$ corresponding to mother code with rate $R_M = 1/2$ ( $t = 24, c = 12$ ) and number of coded bits $N_M = 8640$ shall be: + +| | | | | | | | | | | | | | | | | | | | | | | | | +|-----|-----|----|-----|-----|-----|----|----|----|-----|-----|-----|----|----|----|----|----|----|----|----|----|----|----|----| +| -1 | 34 | -1 | 95 | -1 | 279 | -1 | -1 | -1 | -1 | 248 | -1 | -1 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | -1 | 0 | -1 | 0 | -1 | -1 | -1 | -1 | 134 | 356 | 275 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| 51 | -1 | 27 | -1 | -1 | -1 | -1 | -1 | 22 | 152 | -1 | 57 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 124 | -1 | 290 | -1 | 281 | 15 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | -1 | +| -1 | 340 | -1 | 99 | 336 | -1 | -1 | 1 | -1 | -1 | -1 | 33 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | -1 | +| 163 | -1 | 46 | -1 | -1 | -1 | -1 | -1 | -1 | 306 | -1 | 86 | -1 | -1 | -1 | -1 | -1 | 0 | 0 | -1 | -1 | -1 | -1 | -1 | + +``` + +-1 185 -1 24 -1 -1 -1 94 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 0 0 -1 -1 -1 -1 +-1 223 -1 225 325 -1 -1 -1 -1 -1 297 -1 -1 -1 -1 -1 -1 -1 -1 0 0 -1 -1 -1 -1 +46 -1 314 -1 -1 -1 59 -1 -1 67 -1 120 -1 -1 -1 -1 -1 -1 -1 -1 0 0 -1 -1 +-1 -1 121 -1 -1 -1 -1 161 -1 303 -1 264 -1 -1 -1 -1 -1 -1 -1 -1 0 0 -1 +-1 303 -1 8 -1 185 -1 -1 138 -1 -1 -1 0 -1 -1 -1 -1 -1 -1 -1 -1 0 0 +-1 -1 312 -1 -1 -1 100 -1 -1 144 -1 307 33 166 -1 -1 -1 -1 -1 -1 -1 -1 -1 0 + +``` + +The compact form $H_c$ of parity-check matrix $(2/3)_S$ corresponding to mother code with rate $R_M = 2/3$ ( $t = 24, c = 8$ ) and number of coded bits $N_M = 1440$ shall be: + +``` + +49 -1 -1 21 31 -1 57 -1 -1 19 -1 29 2 -1 19 -1 -1 0 -1 -1 -1 -1 -1 -1 +-1 7 22 -1 -1 37 -1 32 10 -1 26 -1 -1 59 -1 48 -1 0 0 -1 -1 -1 -1 -1 +53 -1 -1 20 50 -1 -1 3 16 -1 49 -1 -1 28 14 -1 -1 -1 0 0 -1 -1 -1 -1 +-1 58 23 -1 -1 15 54 -1 -1 5 -1 18 49 -1 -1 13 -1 -1 -1 0 0 -1 -1 -1 +55 -1 -1 58 -1 9 -1 26 57 -1 41 -1 31 -1 21 -1 -1 -1 -1 0 0 -1 -1 +-1 10 49 -1 59 -1 7 -1 -1 30 -1 18 -1 48 -1 7 59 -1 -1 -1 -1 0 0 -1 +48 -1 -1 50 18 -1 -1 11 52 -1 59 -1 -1 37 -1 10 0 -1 -1 -1 -1 -1 0 0 +-1 24 16 -1 -1 0 53 -1 -1 41 -1 38 51 -1 58 -1 59 8 -1 -1 -1 -1 -1 0 + +``` + +The compact form $H_c$ of parity-check matrix $(2/3)_L$ corresponding to mother code with rate $R_M = 2/3$ ( $t = 24, c = 8$ ) and number of coded bits $N_M = 6480$ shall be: + +``` + +78 -1 -1 167 237 -1 3 -1 266 -1 -1 102 153 -1 -1 212 -1 0 -1 -1 -1 -1 -1 -1 +-1 83 189 -1 -1 68 -1 178 -1 90 205 -1 -1 13 4 -1 -1 0 0 -1 -1 -1 -1 -1 +-1 226 147 -1 46 -1 -1 76 -1 116 -1 211 -1 112 -1 118 -1 -1 0 0 -1 -1 -1 -1 +92 -1 -1 214 -1 236 241 -1 157 -1 143 -1 214 -1 207 -1 -1 -1 -1 0 0 -1 -1 -1 +144 -1 -1 258 264 -1 53 -1 114 -1 172 -1 -1 82 262 -1 62 -1 -1 -1 0 0 -1 -1 +-1 153 120 -1 -1 199 -1 126 -1 61 -1 183 15 -1 -1 134 -1 -1 -1 -1 -1 0 0 -1 +-1 100 -1 141 -1 36 -1 17 -1 156 -1 124 162 -1 -1 57 0 -1 -1 -1 -1 -1 0 0 +196 -1 187 -1 73 -1 80 -1 139 -1 57 -1 -1 236 267 -1 62 256 -1 -1 -1 -1 -1 0 + +``` + +The compact form $H_c$ of parity-check matrix $(5/6)_S$ corresponding to mother code with rate $R_M = 5/6$ ( $t = 24, c = 4$ ) and number of coded bits $N_M = 1152$ shall be: + +``` + +-1 13 32 47 41 24 -1 25 22 40 1 31 8 15 20 15 42 30 13 3 -1 0 -1 -1 +25 46 15 43 45 29 39 47 23 38 39 12 -1 21 -1 38 33 0 0 -1 39 0 0 -1 +35 45 45 38 14 16 6 11 -1 18 7 41 35 17 32 45 41 -1 18 17 0 -1 0 0 +9 32 6 22 26 31 9 8 22 32 40 4 18 40 36 -1 -1 23 31 41 39 20 -1 0 + +``` + +The compact form $H_c$ of parity-check matrix $(5/6)_L$ corresponding to mother code with rate $R_M = 5/6$ ( $t = 24, c = 4$ ) and number of coded bits $N_M = 5184$ shall be: + +``` + +-1 47 146 203 184 112 -1 116 103 181 3 140 38 68 91 70 191 138 62 14 -1 0 -1 -1 +117 203 67 194 206 133 174 212 104 171 176 56 -1 96 -1 167 149 4 1 -1 177 0 0 -1 +153 206 198 173 55 72 28 53 -1 82 34 186 161 80 144 204 187 -1 84 77 0 -1 0 0 +44 147 27 83 118 130 41 38 100 146 183 19 85 180 163 -1 -1 106 140 185 177 94 -1 0 + +``` + +#### 10.1.3.2.1.1 Encoding operation + +See clause 7.1.3.2.1.1. + +#### 10.1.3.2.2 Puncturing + +See clause 7.1.3.2.2. + +**Table 10-55 – See Table 7-55** + +(This table has been intentionally left blank) + +### 10.1.3.2.3 FEC encoding parameters + +The FEC encoding scheme shall support the encoding parameters specified in Table 10-56. + +**Table 10-56 – FEC encoding parameters** + +| | Code rate, $R$ | Information block size, $K$ | Puncturing pattern, $pp$ | Mother code matrix | FEC codeword size, $N_{FEC}$ | +|-------------|----------------|-----------------------------|--------------------------|--------------------|------------------------------| +| For header | 1/2 | $PHY_{HCH} = 384$ | $pp_{16}^{(0)}$ | $(1/2)_{HCH}$ | 768 | +| For payload | 1/2 | 960 | $pp_{16}^{(0)}$ | $(1/2)_S$ | 1920 | +| | 1/2 | 4320 | $pp_{16}^{(0)}$ | $(1/2)_L$ | 8640 | +| | 2/3 | 960 | $pp_{16}^{(0)}$ | $(2/3)_S$ | 1440 | +| | 2/3 | 4320 | $pp_{16}^{(0)}$ | $(2/3)_L$ | 6480 | +| | 5/6 | 960 | $pp_{16}^{(0)}$ | $(5/6)_S$ | 1152 | +| | 5/6 | 4320 | $pp_{16}^{(0)}$ | $(5/6)_L$ | 5184 | +| | 16/18 | 960 | $pp_{1152}^{(72)}$ | $(5/6)_S$ | 1080 | +| | 16/18 | 4320 | $pp_{5184}^{(324)}$ | $(5/6)_L$ | 4860 | +| | 20/21 | 960 | $pp_{1152}^{(144)}$ | $(5/6)_S$ | 1008 | +| | 20/21 | 4320 | $pp_{5184}^{(648)}$ | $(5/6)_L$ | 4536 | + +### 10.1.3.3 Payload encoding + +There are two supported modes of Payload encoding: the full mode and the multi-level coding (MLC) mode. + +A transmitter may only use the MLC mode for transmission when the receiver of the transmission has indicated it supports such mode in its node capabilities. + +In full mode, the functional model of the payload encoder is presented in Figure 10-8. It contains an FEC encoder and a payload repetition encoder (PRE) to support robust communication mode (RCM). + +![Functional diagram of the payload encoder (set to normal mode). The diagram shows 'Payload bits' entering a box labeled 'FEC encoder'. The output of the FEC encoder is labeled 'FEC codeword (N_FEC)'. This codeword enters a large box labeled 'Payload encoder'. Inside this box, the codeword splits into two paths: one goes through a 'Payload repetition encoder' and the other is labeled 'Normal mode'. Both paths rejoin and exit the 'Payload encoder' box as an 'Encoded payload block'. A small label 'G.9960(23)_F10-8' is at the bottom right of the diagram.](5ea288cb741dddda2a54203184649b5a_img.jpg) + +Functional diagram of the payload encoder (set to normal mode). The diagram shows 'Payload bits' entering a box labeled 'FEC encoder'. The output of the FEC encoder is labeled 'FEC codeword (N\_FEC)'. This codeword enters a large box labeled 'Payload encoder'. Inside this box, the codeword splits into two paths: one goes through a 'Payload repetition encoder' and the other is labeled 'Normal mode'. Both paths rejoin and exit the 'Payload encoder' box as an 'Encoded payload block'. A small label 'G.9960(23)\_F10-8' is at the bottom right of the diagram. + +**Figure 10-8 – Functional diagram of the payload encoder (set to normal mode)** + +The incoming PHY-frame payload shall be divided into sequential blocks of information bits, $K$ bits per block. Each block of information bits shall be encoded by the FEC, as described in clause 10.1.3.2. The valid values of $K$ , the coded block size $N_{FEC}$ , and the coding rate $R$ , are presented in Table 10- + +56. The bits of each information block shall be in the same order as they are in the payload; the payload bit to be transmitted first shall be the first in the corresponding information block. + +In normal mode of operation, indicated by REP = 001 in the PHY-frame header, PRE is disabled. The FEC codewords shall be passed directly to the output of the payload encoder and concatenated into the encoded payload block; their order shall be the same as the order of corresponding information blocks at the input of the payload encoder. + +In MLC mode, the payload encoder is presented in Figure 10-8.1. It contains an MLC Pre-Processor to support MLC and an FEC encoder. + +![Functional diagram of the MLC Payload Encoder showing the flow from payload bits through an MLC pre-processor and FEC encoder to produce encoded and non-coded payload blocks.](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) + +``` + +graph LR + PB[Payload bits] --> MLC[MLC pre-processor] + subgraph PE[Payload encoder MLC mode] + MLC --> |Coded bits| FEC[FEC encoder] + MLC --> |Non-coded bits| NCB_OUT[Non-coded payload block] + FEC --> |Parity bits indication| MLC + end + FEC --> EPB[Encoded payload block] + NCB_OUT --> NPB[Non-coded payload block] + +``` + +The diagram illustrates the internal structure of the MLC Payload Encoder. It shows 'Payload bits' entering the 'MLC pre-processor'. The pre-processor splits the bits into 'Coded bits', which go to the 'FEC encoder', and 'Non-coded bits', which bypass the FEC encoder. The FEC encoder outputs the 'Encoded payload block' and also provides a 'Parity bits indication' feedback signal to the MLC pre-processor. The non-coded bits form the 'Non-coded payload block'. The diagram is identified as G.9960(18)-Cor.2(20)\_F10-8.1. + +Functional diagram of the MLC Payload Encoder showing the flow from payload bits through an MLC pre-processor and FEC encoder to produce encoded and non-coded payload blocks. + +**Figure 10-8.1 – Functional diagram of the MLC Payload Encoder** + +The MLC pre-processor divides the incoming payload bits into two groups (non-coded bits and coded bits) according to the runtime BAT and subcarrier grouping being used in the following way: + +- As described in clause 10.1.4.2.2, the bit allocation table (BAT) associates subcarrier indices with the number of bits to be loaded on the subcarrier ( $b$ ). +- The maximum number of coded bits per subcarrier ( $\max\_coded\_bits$ ) is 6 in this mode. +- The MLC pre-processor groups the incoming payload bits in groups of $b$ bits (or $b-6$ in case the FEC encoder is issuing parity bits) and divides them between coded bits and non-coded bits. +- The FEC encoder shall signal to the ML pre-processor if the bits correspond to the parity check bits of an FEC block (parity bits indicator). +- The group of incoming bits is divided in coded and non-coded bits in the following way: + - In the general case (i.e., no parity bits indicator active): + - If $b \leq \max\_coded\_bits$ , all $b$ bits are classified as coded bits + - If $b > \max\_coded\_bits$ , the 6 LSB bits of the group are classified as coded bits and the remaining $b-6$ bits are classified as non-coded bits. + - When parity bits being issued by the FEC encoding (i.e., parity bits indicator active): + - No code bits are classified as coded bits + - $b-6$ (or zero if $b \leq 6$ ) bits are classified as non-coded bits + +Once the MLC pre-processor has divided the incoming payload bits into two groups, they are processed in the following way: + +- **Non-coded bits:** These bits are not encoded by the FEC encoder and are passed directly to output of the MLC payload encoder and concatenated into the non-coded payload block. The bits at the output of the MLC payload encoder shall be in the same order as they are in the payload. +- **Coded bits:** These bits are processed by the FEC encoder. The incoming coded bits sequence shall be divided into sequential blocks of information bits, $K$ bits per block. Each block of + +information bits shall be encoded by the FEC, as described in clause 10.1.3.2. The valid values of $K$ , the coded block size $N_{FEC}$ , and the coding rate $R$ , are presented in Table 10-56. The bits of each information block shall be in the same order as they are in the coded bits sequence; the coded bit to be transmitted first shall be the first in the corresponding information block. + +The FEC codewords shall be passed directly to the output of the payload encoder and concatenated into the encoded payload block; their order shall be the same as the order of corresponding information blocks at the input of the payload encoder. + +In the case of RCM, each FEC codeword is further encoded by the PRE, as described in clause 10.1.3.3.1. The PRE-encoded FEC codewords are concatenated into the encoded payload block as defined in clause 10.1.3.3.1. + +### 10.1.3.3.1 Payload repetition encoding + +Payload repetition encoder (PRE) shall support the number of repetitions $N_{REP}$ specified in Table 10-8. The used number of repetitions shall be advertised in the REP field in the PHY-frame header. + +The FEC codeword enters the PRE. The PRE shall operate as follows: + +- The FEC codeword shall be first copied $M$ times, where $M = \text{ceiling}(k_P/N_{FEC})$ , $k_P$ is the number of bits to be loaded onto the payload OFDM symbol according to the current BAT, which is fixed to BAT Type 1. If the FEC codeword is made of bits $(b_i)$ , this produces a sequence of bits $C$ as follows: + +$$C = \{b_0, b_1, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}\}_0, \{b_0, b_1, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}\}_1, \dots, \{b_0, b_1, \dots, b_{N_{FEC}-2}, b_{N_{FEC}-1}\}_{M-1} = \{b'_0, b'_1, \dots, b'_{M \times N_{FEC}-2}, b'_{M \times N_{FEC}-1}\}.$$ + +NOTE – As an example, if a node uses subcarriers 1200 to 1700 for transmission (0 Hz is subcarrier 0) in a network with first 11 subcarriers defined as PMSC, the modem $k_P$ will be $(1701 - 11) \times 2 = 3380$ bits. + +- The PRE encoder shall output $N_{sym}$ copies of the bit sequence $C$ . $N_{sym}$ is the number of OFDM symbols needed to transmit the RCM encoded FEC codeword, and it is computed as follows + +$$N_{sym} = \text{ceiling}\left(\frac{N_{FEC} \cdot N_{REP}}{k_{min}}\right)$$ + +Where $k_{min}$ is a value in bits that can be related to the minimum bandwidth $BW_{MIN}$ needed to have $N_{REP}$ complete repetitions of the FEC codeword. The used $k_{min}$ value shall be advertised in the KMIN field in the PHY-frame header (see clause 10.1.2.3.2.1.13), and shall be chosen from among the possible values specified in Table 10-10.1. + +The relation between $k_{min}$ and $BW_{min}$ is as follows: $BW_{min} = \frac{k_{min} \cdot F_{sc}}{2}$ , where $F_{sc}$ is the subcarrier spacing. + +- A right circular shift shall be applied to each copy of the bit sequence $C$ as follows: + +- The 1st copy of the bit sequence $C$ shall be output with no shift: + +$$C_1 = \{b'_0, b'_1, \dots, b'_{M \times N_{FEC}-2}, b'_{M \times N_{FEC}-1}\}.$$ + +- The 2nd copy of the bit sequence $C$ shall be output with a right circular shift of $N_{offset}$ bits: + +$$C_2 = \{b'_{M \times N_{FEC}-N_{offset}}, b'_{M \times N_{FEC}-N_{offset}+1}, \dots, b'_{M \times N_{FEC}-2}, b'_{M \times N_{FEC}-1}, b'_0, b'_1, \dots, b'_{M \times N_{FEC}-N_{offset}-2}, b'_{M \times N_{FEC}-N_{offset}-1}\}.$$ + +- The 3rd copy of the bit sequence $C$ shall be output with a right circular shift of $2 \times N_{offset}$ bits: + +$$C_3 = \{b'_{M \times N_{FEC} - 2 \times N_{offset}}, b'_{M \times N_{FEC} - 2 \times N_{offset} + 1}, \dots, b'_{M \times N_{FEC} - 2}, b'_{M \times N_{FEC} - 1}, b'_0, b'_1, \dots, b'_{M \times N_{FEC} - 2 \times N_{offset} - 2}, b'_{M \times N_{FEC} - 2 \times N_{offset} - 1}\}.$$ + +- And so on, until the $N_{sym}^{th}$ copy of the bit sequence $C$ , which shall be output with a right circular shift of $(N_{sym} - 1) \times N_{offset}$ bits: + +$$C_{N_{sym}} = \{b'_{M \times N_{FEC} - (N_{sym} - 1) \times N_{offset}}, b'_{M \times N_{FEC} - (N_{sym} - 1) \times N_{offset} + 1}, \dots, b'_{M \times N_{FEC} - 2}, b'_{M \times N_{FEC} - 1}, b'_0, b'_1, \dots, b'_{M \times N_{FEC} - (N_{sym} - 1) \times N_{offset} - 2}, b'_{M \times N_{FEC} - (N_{sym} - 1) \times N_{offset} - 1}\}.$$ + +The PRE encoding process is illustrated in Figure 10-9. + +![Figure 10-9: Mapping of FEC codeword in subcarriers and OFDM symbols. The diagram shows the mapping of N_FEC bits into M copies of a bit sequence C, which are then mapped into N_sym OFDM symbols. The mapping is shown in a grid where the horizontal axis represents subcarriers and the vertical axis represents OFDM symbols. The first row is the 'C sequence' with M copies. The subsequent rows are OFDM symbols C1, C2, C3, ..., C_Nsym. Arrows show the mapping of bits from the C sequence to the OFDM symbols. The offset between bits in the same subcarrier across consecutive OFDM symbols is N_offset. The total offset for the last symbol is (N_sym - 1) * N_offset. The diagram is labeled G.9960(18)-Cor.2(20)_F10-9.](991dd3ca8ff5bdb023220b1d44775e1d_img.jpg) + +Figure 10-9: Mapping of FEC codeword in subcarriers and OFDM symbols. The diagram shows the mapping of N\_FEC bits into M copies of a bit sequence C, which are then mapped into N\_sym OFDM symbols. The mapping is shown in a grid where the horizontal axis represents subcarriers and the vertical axis represents OFDM symbols. The first row is the 'C sequence' with M copies. The subsequent rows are OFDM symbols C1, C2, C3, ..., C\_Nsym. Arrows show the mapping of bits from the C sequence to the OFDM symbols. The offset between bits in the same subcarrier across consecutive OFDM symbols is N\_offset. The total offset for the last symbol is (N\_sym - 1) \* N\_offset. The diagram is labeled G.9960(18)-Cor.2(20)\_F10-9. + +**Figure 10-9 – Mapping of FEC codeword in subcarriers and OFDM symbols** + +The value $N_{offset}$ is calculated as follows: + +$$N_{offset} = 2 \cdot \text{floor} \left( \frac{N_{FEC}}{2N_{sym}} \right)$$ + +unless $2 \cdot \text{floor} \left( \frac{N_{FEC}}{2N_{sym}} \right)$ is divisible by 4, in which case + +$$N_{offset} = 2 \cdot \text{floor} \left( \frac{N_{FEC}}{2N_{sym}} \right) - 2$$ + +It can be checked that $(N_{sym} - 1) \times N_{offset} < N_{FEC}$ . The above expressions also ensures $N_{offset}$ is an even number. + +If the computed value of $N_{sym}$ is 1, $H$ consecutive FEC codewords may be concatenated. The number of $M$ copies in this case shall be $M = \text{ceiling} (k_P / (H \times N_{FEC}))$ + +$$\text{and } N_{sym} = \text{ceiling} \left( \frac{H \cdot N_{FEC} \cdot N_{REP}}{k_{min}} \right)$$ + +$$N_{offset} = 2 \cdot \text{floor} \left( \frac{H \cdot N_{FEC}}{2N_{sym}} \right)$$ + +unless $2 \cdot \text{floor}\left(\frac{H \cdot N_{FEC}}{2N_{sym}}\right)$ is divisible by 4, in which case + +$$N_{offset} = 2 \cdot \text{floor}\left(\frac{H \cdot N_{FEC}}{2N_{sym}}\right) - 2$$ + +The total size of the concatenated codewords shall not exceed the maximum FEC codeword size. + +If the number of FEC codewords in the payload is not a multiple of $H$ , the necessary $z < H$ dummy FEC codewords shall be added. These dummy codewords shall be copies of the last FEC codeword of the same payload. The values of $H$ (1, 2 and 4) and $z$ (0 to $H-1$ ) are indicated in the FCF field of the PHY-frame header (see Table 10-9). + +The format of the encoded payload block with PRE enabled is presented in Figure 10-10. + +![Figure 10-10: The format of the encoded payload block. The diagram shows an 'Encoded payload block' containing multiple 'PRE-encoded FEC codeword' segments, labeled #1, #2, ..., #J. Each segment is noted as having '(M x N_sym repetitions)'. Below the first codeword, a callout shows 'Group #1 of M FEC copies (C1)' with bits 0, 1, ..., M-1. Below the second codeword, a callout shows 'Group #1 of M FEC copies (C2)' with bits 0, 1, ..., M-1. Below the J-th codeword, a callout shows 'Group #N_sym of M FEC copies (C_NSYM)' with bits M-1, 0, 1, ....](5525e7460947727851585808324e1f98_img.jpg) + +G.9960(18)-Cor.2(20)\_F10-10 + +Figure 10-10: The format of the encoded payload block. The diagram shows an 'Encoded payload block' containing multiple 'PRE-encoded FEC codeword' segments, labeled #1, #2, ..., #J. Each segment is noted as having '(M x N\_sym repetitions)'. Below the first codeword, a callout shows 'Group #1 of M FEC copies (C1)' with bits 0, 1, ..., M-1. Below the second codeword, a callout shows 'Group #1 of M FEC copies (C2)' with bits 0, 1, ..., M-1. Below the J-th codeword, a callout shows 'Group #N\_sym of M FEC copies (C\_NSYM)' with bits M-1, 0, 1, .... + +**Figure 10-10 – The format of the encoded payload block (payload consists of $J$ FEC codewords)** + +#### 10.1.3.4 Header encoder + +See clause 7.1.3.4. + +**Figure 10-11 – See Figure 7-11** + +(This figure has been intentionally left blank) + +#### 10.1.3.5 Segmentation into symbol frames + +The encoded payload block from the output of the full payload encoder or the Encoded and Non-code payload blocks from the output of the MLC payload encoder and the encoded header block from the output of the header encoder shall be segmented into symbol frames. The maximum number of bits in the symbol frame shall not exceed the values of $k_P$ for payload symbol frames and $k_H$ for header symbol frames. Payload and header symbol frames shall be passed to the PMD, as described in Figure 10-5. + +##### 10.1.3.5.1 Payload segmentation + +The payload segmentation is described in clause 10.1.3.5.1.1 in the case of full encoding and 10.1.3.5.1.2 in the case of MLC encoding. + +### 10.1.3.5.1.1 Full mode payload segmentation + +The encoded payload block shall be segmented into one or more symbol frames. + +In normal mode, the first symbol frame shall contain the first $k_p$ bits of the encoded payload block, the second frame shall contain the second $k_p$ bits of the encoded payload block and so on, until the last symbol frame. If the number of bits in the last symbol frame is less than $k_p$ , the unloaded supported subcarriers of the OFDM symbol for the last symbol frame shall be modulated by a pseudorandom sequence of bits, as described in clause 10.1.4.2.6. Payload segmentation is illustrated in Figure 10-12. + +In RCM, the first symbol frame shall contain the first $k_p$ bits of the first group of $M \times N_{FEC}$ bits ( $C_1$ bit sequence) of the encoded payload block. The remaining $M \times N_{FEC} - k_p$ bits of the first group of $M \times N_{FEC}$ bits will be discarded. The second symbol frame shall contain the first $k_p$ bits of the second group of $M \times N_{FEC}$ bits ( $C_2$ bit sequence) of the encoded payload block. The remaining $M \times N_{FEC} - k_p$ bits of the second group of $M \times N_{FEC}$ bits will be discarded. And so on until the last symbol frame. + +NOTE – Depending on the actual subcarriers actually used for transmission by a given node, the first $Q$ bits out of the set of $k_p$ bits in each symbol frame might not be transmitted. The value $Q$ is determined by the number of subcarriers between the first non-PMSC subcarrier in the network, and the first subcarrier used for transmission by a given node. For example, if a node uses subcarriers 1200 to 1700 for transmission (0 Hz is subcarrier 0) in a network with first 11 subcarriers defined as PMSC, the first $Q = (1200 - 11) \times 2 = 2378$ bits out of the set of $k_p$ bits in each symbol frame will not be transmitted in the line by that node. + +![Diagram illustrating payload segmentation. A 'Payload block' is shown at the top, with 'LSB, octet 0' indicated at its start. Below it, the block is segmented into symbol frames. The first two frames are labeled 'Symbol frame 1' and 'Symbol frame 2', each containing a segment of 'k_p bits'. An ellipsis indicates intermediate frames. The last two frames are labeled 'Symbol frame M-1' and 'Symbol frame M'. 'Symbol frame M-1' contains a segment of 'k_p bits'. 'Symbol frame M' contains a segment of 'k_p bits' and a portion labeled 'Unloaded SSCs'. A dashed vertical line separates the 'k_p bits' segment from the 'Unloaded SSCs' segment in the final frame. The diagram is labeled 'G.9960(18)-Cor.2(20)_F10-12' at the bottom right.](e3026761f1da20ee91832039701984dd_img.jpg) + +Diagram illustrating payload segmentation. A 'Payload block' is shown at the top, with 'LSB, octet 0' indicated at its start. Below it, the block is segmented into symbol frames. The first two frames are labeled 'Symbol frame 1' and 'Symbol frame 2', each containing a segment of 'k\_p bits'. An ellipsis indicates intermediate frames. The last two frames are labeled 'Symbol frame M-1' and 'Symbol frame M'. 'Symbol frame M-1' contains a segment of 'k\_p bits'. 'Symbol frame M' contains a segment of 'k\_p bits' and a portion labeled 'Unloaded SSCs'. A dashed vertical line separates the 'k\_p bits' segment from the 'Unloaded SSCs' segment in the final frame. The diagram is labeled 'G.9960(18)-Cor.2(20)\_F10-12' at the bottom right. + +Figure 10-12 – Payload segmentation + +### 10.1.3.5.1.2 MLC mode payload segmentation + +The Encoded and Non-Coded payload blocks shall be segmented into one or more symbol frames. + +In this mode, the number of bits in the symbol frame $k_p$ shall be divided into two numbers: + +- $kenc_p$ : Number of Encoded bits in a symbol according to the current Runtime BAT +- $knon_p$ : Number of Non-Coded bits in a symbol according to the current Runtime BAT + +Regarding the Encoded payload block, the first symbol frame shall contain the first $kenc_p$ bits of the encoded payload block, the second frame shall contain the second $kenc_p$ bits of the encoded payload block and so on, until the last symbol frame. If the number of encoded bits in the last symbol frame is less than $kenc_p$ , the encoded bits of the unloaded supported subcarriers of the OFDM symbol for the last symbol frame shall be modulated by a pseudorandom sequence of bits, as described in clause 10.1.4.2.6. + +In a similar way, regarding the Non-coded payload block, the first symbol frame shall contain the first $knon_p$ bits of the encoded payload block, the second frame shall contain the second $knon_p$ bits of the encoded payload block and so on, until the last symbol frame. If the number of non-coded bits in the last symbol frame is less than $knon_p$ , the non-coded bits of the unloaded supported subcarriers of the OFDM symbol for the last symbol frame shall be modulated by a pseudorandom sequence of bits, as described in clause 10.1.4.2.6. + +MLC Payload segmentation is illustrated in Figure 10-12.1. + +![Diagram of MLC Payload segmentation showing Non-coded and Encoded payload blocks with symbol frames and bit labels.](f54b2e4444e410765295be668123f27a_img.jpg) + +The diagram illustrates the segmentation of an MLC payload into two main blocks: a 'Non-coded payload block' and an 'Encoded payload block'. The 'Non-coded payload block' contains $knon_{p}$ bits, which are further divided into 'Symbol frame 1', 'Symbol frame 2', an ellipsis, 'Symbol frame M-1', and 'Symbol frame M'. The 'Encoded payload block' contains $kenc_{p}$ bits. Arrows on the right side point to the non-coded bits as 'Unloaded SSCs (non-coded bits)' and to the encoded bits as 'Unloaded SSCs (encoded bits)'. The diagram is labeled 'LSB, octet 0' at the top and bottom left, and 'G.9960(18)-Cor.2(20)\_F10-12.1' at the bottom right. + +Diagram of MLC Payload segmentation showing Non-coded and Encoded payload blocks with symbol frames and bit labels. + +**Figure 10-12.1 – MLC Payload segmentation** + +### 10.1.3.5.2 Header segmentation + +See clause 7.1.3.5.2. + +**Figure 10-13 – See Figure 7-13** + +(This figure has been intentionally left blank) + +### 10.1.3.6 PROBE frame + +See clause 7.1.3.6. + +## 10.1.4 Physical medium dependent (PMD) sublayer + +See clause 7.1.4. + +**Figure 10-14 – See Figure 7-14** + +(This figure has been intentionally left blank) + +### 10.1.4.1 Subcarrier spacing and indexing + +See clause 7.1.4.1 with the exception that only indexing rule #1 is applicable to clause 10. + +### 10.1.4.2 Tone mapper + +See clause 7.1.4.2. + +#### 10.1.4.2.1 Summary of subcarrier types + +See clause 7.1.4.2.1. + +#### 10.1.4.2.2 Bit allocation tables (BATs) + +See clause 7.1.4.2.2. + +**Table 10-57 – See Table 7-57** + +(This table has been intentionally left blank) + +#### **10.1.4.2.2.1 Predefined BATs** + +See clause 7.1.4.2.2.1. + +#### **10.1.4.2.2.2 Runtime BATs** + +A runtime BAT associates indices of SSCs with the number of bits to be loaded on each subcarrier. The subset of indices in the BAT with the number of loaded bits $b > 0$ identifies the ASC. Runtime BAT can be defined by the receiving node (receiver-defined BAT) or selected by the transmitting node (transmitter-determined BAT) for a specific unicast or multicast channel. Runtime BATs shall be communicated from the node that generates the BAT to the peer (e.g., a node sourcing multicast transmission to several other nodes will communicate the BAT to all receiving nodes prior to sending data) (see clauses 8.11 and 8.16 of [[ITU-T G.9961](#)]). + +The number of bits loaded on any subcarrier shall not exceed the maximum number of bits allowed (see clause 10.1.4.3). The number of bits shall also meet the bit loading capabilities of the communicating nodes, as advertised by them prior to communication. + +#### **10.1.4.2.3 Transmitter-determined and receiver-determined mapping** + +See clause 7.1.4.2.3. + +### **Figure 10-15 – See Figure 7-15** + +(This figure has been intentionally left blank) + +#### **10.1.4.2.4 BAT with subcarrier grouping** + +See clause 7.1.4.2.4. + +#### **10.1.4.2.5 Special mappings** + +##### **10.1.4.2.5.1 Tone mapping for PHY-frame header** + +See clause 7.1.4.2.5.1. + +##### **10.1.4.2.5.2 Tone mapping for RCM** + +Payload transmission in robust communication mode (RCM) shall always use predefined BAT type 1. That is, uniform two bits loading on all subcarriers except those in the PMSC set. + +##### **10.1.4.2.5.3 Tone mapping for the probe symbols** + +See clause 7.1.4.2.5.3 + +##### **10.1.4.2.5.4 Tone mapping for ACE symbols** + +See clause 7.1.4.2.5.4. + +#### **10.1.4.2.6 Modulation of unloaded supported subcarriers** + +See clause 7.1.4.2.6. + +### **Table 10-57.1 – See Table 7-57.1** + +(This table has been intentionally left blank) + +**Figure 10-16 – See Figure 7-16** + +(This figure has been intentionally left blank) + +**Table 10-58 – See Table 7-58** + +(This table has been intentionally left blank) + +### 10.1.4.3 Constellation encoder + +#### 10.1.4.3.1 Constellation mapping + +When using full encoding, the constellation mapping shall follow clauses 10.1.4.3.1.1 and 10.1.4.3.1.2 for even and odd number of bits respectively. + +When using MLC encoding, the constellation mapping shall follow clauses 10.1.4.3.1.3 and 10.1.4.3.1.4 for even and odd number of bits respectively. + +##### 10.1.4.3.1.1 Constellations for even number of bits (full encoding) + +If the number of bits, $b$ , loaded on to the subcarrier is even (2, 4, 6, 8, 10, 12 and 14), square-shaped constellations with mappings described in this clause shall be used. Support of all the specified even order constellations (2, 4, 6, 8, 10 and 12) shall be mandatory at both the transmitter and the receiver. Support of the following even order constellation (14) shall be mandatory only at the transmitter. With square-shaped constellations, $2^b$ constellation points are set as a square, and $2^{b-2}$ points reside in each quadrant with odd values (positive or negative) of $I$ and $Q$ . + +Constellation and mapping for $b = 2$ shall be as presented in Figure 10-17 and described in Table 10-59. + +![Figure 10-17: Constellation and mapping for b = 2. The diagram shows a 2D coordinate system with I (horizontal) and Q (vertical) axes. The I-axis has tick marks at -3, -1, 1, and 3. The Q-axis has tick marks at -3, -1, 1, and 3. Four points are plotted: '10' at (-1, 1), '11' at (1, 1), '00' at (-1, -1), and '01' at (1, -1). A small label 'G.9960(18)-Cor.2(20)_F10-17' is at the bottom right.](dafe1e070adde01b4d127609636af4e9_img.jpg) + +Figure 10-17: Constellation and mapping for b = 2. The diagram shows a 2D coordinate system with I (horizontal) and Q (vertical) axes. The I-axis has tick marks at -3, -1, 1, and 3. The Q-axis has tick marks at -3, -1, 1, and 3. Four points are plotted: '10' at (-1, 1), '11' at (1, 1), '00' at (-1, -1), and '01' at (1, -1). A small label 'G.9960(18)-Cor.2(20)\_F10-17' is at the bottom right. + +**Figure 10-17 – Constellation and mapping for $b = 2$** + +**Table 10-59 – Mapping for $b = 2$ (QPSK)** + +| Bit $d_0$ | $I$ | | Bit $d_1$ | $Q$ | +|-----------|-----|--|-----------|-----| +| 0 | -1 | | 0 | -1 | +| 1 | 1 | | 1 | 1 | + +Constellation mapping for $b = 4$ shall be as described in Table 10-60. The first quadrant of the mapping is presented in Figure 10-18. + +![Figure 10-18: Constellation diagram for b=4 (first quadrant). The vertical axis is labeled Q with values +1 and +3. The horizontal axis is labeled I with values +1 and +3. Four points are plotted: (1, 3) labeled 0111, (3, 3) labeled 0101, (1, 1) labeled 1111, and (3, 1) labeled 1101. Below the diagram is the text G.9960(18)-Cor.2(20)_F10-18.](4faf621bddd7d6e9f24a27325de96015_img.jpg) + +Figure 10-18: Constellation diagram for b=4 (first quadrant). The vertical axis is labeled Q with values +1 and +3. The horizontal axis is labeled I with values +1 and +3. Four points are plotted: (1, 3) labeled 0111, (3, 3) labeled 0101, (1, 1) labeled 1111, and (3, 1) labeled 1101. Below the diagram is the text G.9960(18)-Cor.2(20)\_F10-18. + +Figure 10-18 – Constellation and mapping for $b = 4$ (first quadrant) + +Table 10-60 – Mapping for $b = 4$ + +| Bits [ $d_1d_0$ ] | $I$ | Bit [ $d_3d_2$ ] | $Q$ | +|-------------------|-----|------------------|-----| +| 00 | -3 | 00 | -3 | +| 10 | -1 | 10 | -1 | +| 11 | 1 | 11 | 1 | +| 01 | 3 | 01 | 3 | + +Constellation mappings for even values of $b \geq 4$ shall be derived by the following steps: + +- 1) Divide the incoming group of $b$ bits into two equal subgroups, so that $b/2$ LSBs form the first subgroup ( $I$ -group) and $b/2$ MSBs form the second subgroup ( $Q$ -group); both subgroups are incoming LSBs (which are $d_0$ and $d_{b/2}$ , respectively) first. +- 2) Compute values of $I$ and $Q$ for the incoming group $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ as: + +$$I = \text{sgn}_I \times \text{val}_I$$ + +$$Q = \text{sgn}_Q \times \text{val}_Q$$ + +The values of $\text{sgn}$ and $\text{val}$ shall be computed as presented in Table 10-61 using bits of $I$ -group to compute $I$ and bits of $Q$ -group to compute $Q$ . + +Table 10-61 – Computation rule for $\text{sgn}$ and $\text{val}$ + +| $I$ – component | $Q$ – component | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| – compute $\text{sgn}_I = 2 \times d_0 - 1$
– compute $\text{val}_I = I_{b-2} - 2^{b/2-1} $ | – compute $\text{sgn}_Q = 2 \times d_{b/2} - 1$
– compute $\text{val}_Q = Q_{b-2} - 2^{b/2-1} $ | +| NOTE 1 – $I_{b-2}$ and $Q_{b-2}$ are the values of $I$ and $Q$ computed for the incoming $(b-2)$ -bit group $\{d_{b-1}, d_{b-2}, \dots, d_{b/2+1}, d_{b/2-1}, \dots, d_1\}$ , i.e., with $d_0$ and $d_{b/2}$ removed. | | +| NOTE 2 – The values of $I$ and $Q$ for 2-bit groups shall be as presented in Table 7-59. | | +| NOTE 3 – $ X $ is the absolute value of $X$ . | | + +#### 10.1.4.3.1.2 Constellations for odd number of bits (full encoding) + +If the number of bits, $b$ , loaded on to the subcarrier is odd (1, 3, 5, 7, 9, 11 and 13), constellations with mappings described in this clause shall be used. The support of all the specified odd order constellations (1, 3, 5, 7, 9, 11 and 13) shall be mandatory at the transmitter. The support of all the specified odd order constellations with $b \geq 5$ , shall be optional at the receiver. + +For multicast transmission, odd constellations with $b \geq 5$ shall not be used. + +Constellation and mapping for $b = 1$ shall be as presented in Figure 10-19. + +![Figure 10-19: Constellation shape and mapping for b = 1. The diagram shows a 2D coordinate system with a horizontal I-axis and a vertical Q-axis. Two points are plotted on the I-axis: one at (-1, 0) labeled '0' and another at (1, 0) labeled '1'. The Q-axis has tick marks at +1 and -1. A small text label 'G.9960(18)-Cor.2(20)_F10-19' is at the bottom.](4b48a3fdfe130217b1ff29b9b0592a45_img.jpg) + +Figure 10-19: Constellation shape and mapping for b = 1. The diagram shows a 2D coordinate system with a horizontal I-axis and a vertical Q-axis. Two points are plotted on the I-axis: one at (-1, 0) labeled '0' and another at (1, 0) labeled '1'. The Q-axis has tick marks at +1 and -1. A small text label 'G.9960(18)-Cor.2(20)\_F10-19' is at the bottom. + +**Figure 10-19 – Constellation shape and mapping for $b = 1$** + +Constellation and mapping for $b = 3$ shall be as presented in Figure 10-20. + +![Figure 10-20: Constellation and mapping for b = 3. The diagram shows a 2D coordinate system with I and Q axes. Points are labeled with 3-bit binary strings: 100 at (-3, 1), 110 at (-1, 1), 101 at (1, 3), 111 at (1, 1), 010 at (-1, -1), 011 at (1, -1), 001 at (3, -1), and 000 at (0, -3). The I-axis has tick marks at -3, -1, 1, and 3. The Q-axis has tick marks at -3, -1, 1, and 3. A small text label 'G.9960(18)-Cor.2(20)_F10-20' is at the bottom.](56887eb4a851f556d1b263bf90755686_img.jpg) + +Figure 10-20: Constellation and mapping for b = 3. The diagram shows a 2D coordinate system with I and Q axes. Points are labeled with 3-bit binary strings: 100 at (-3, 1), 110 at (-1, 1), 101 at (1, 3), 111 at (1, 1), 010 at (-1, -1), 011 at (1, -1), 001 at (3, -1), and 000 at (0, -3). The I-axis has tick marks at -3, -1, 1, and 3. The Q-axis has tick marks at -3, -1, 1, and 3. A small text label 'G.9960(18)-Cor.2(20)\_F10-20' is at the bottom. + +**Figure 10-20 – Constellation and mapping for $b = 3$** + +For $b > 3$ cross-shaped constellations shall be used. First, $2^b$ constellation points shall be set as a rectangle, with $2^{B1}$ columns ( $2^{B1}$ points on the $I$ -axis) and $2^{B2}$ rows ( $2^{B2}$ points on the $Q$ -axis), where $B1 = \text{ceiling}(b/2)$ and $B2 = \text{floor}(b/2)$ . The mapping of these points shall be computed using the following steps: + +- 1) Divide the incoming group of bits into two subgroups, so that $B1$ LSBs form the first subgroup ( $I$ -group) and $B2$ MSBs form the second subgroup ( $Q$ -group); both subgroups are incoming LSBs (which are $d_0$ and $d_{B2+1}$ , respectively) first. +- 2) Compute values of $I$ and $Q$ of a rectangular constellation for the incoming group $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ as: + +$$I = \text{sgn}_I \times \text{val}_I$$ + +$$Q = \text{sgn}_Q \times \text{val}_Q$$ + +The values of $\text{sgn}$ and $\text{val}$ shall be computed as presented in Table 10-62 using bits of $I$ -group to compute $I$ and bits of $Q$ -group to compute $Q$ . + +**Table 10-62 – Computation rule for *sgn* and *val*** + +| I – component | Q – component | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| – compute $sgn_I = 2 \times d_0 - 1$
– compute $val_I = I_{2 \times B1} $ | – compute $sgn_Q = 2 \times d_{B1} - 1$
– compute $val_Q = Q_{2 \times B2} $ | +| NOTE 1 – $I_{2 \times B1}$ is the value of I for $(2 \times B1)$ -bit group $\{0, d_{b-1}, d_{b-2}, \dots, d_0\}$ computed as defined in Table 7-61.
NOTE 2 – $Q_{2 \times B2}$ is the value of Q for $(2 \times B2)$ -bit group $\{d_{b-1}, d_{b-2}, \dots, d_1\}$ computed as defined in Table 7-61.
NOTE 3 – $ X $ is the absolute value of X . | | + +- 3) Transform $s = (2^{B1} - 2^{B2})/4$ columns of constellation points in each quadrant having highest absolute values of *I* (positive or negative) into rows of *Q* by changing their $\{I, Q\}$ coordinates to $\{I', Q'\}$ in the following way: +- $|Q'| = |I| - 2s$ , and $\text{sign}(Q') = \text{sign}(I)$ ; + - $|I'| = M_Q - |Q|$ , and $\text{sign}(I') = \text{sign}(Q)$ . + +The described transformation of $\{I, Q\}$ coordinates for $b = 7$ is presented in Figure 7-21 with $B1 = 4$ and $B2 = 3$ (the MSB and LSB in Figure 10-21 are separated by "/"). + +![Figure 10-21: Transformation of rectangular constellation into cross-shaped constellation for b = 7 (first quadrant). The plot shows I on the x-axis and Q on the y-axis. A rectangular constellation of 16 points is shown on the left, with points at (1,1), (3,1), (5,1), (7,1), (9,1), (11,1), (1,3), (3,3), (5,3), (7,3), (9,3), (11,3), (1,5), (3,5), (5,5), (7,5), (9,5), (11,5), (1,7), (3,7), (5,7), (7,7), (9,7), (11,7), (1,9), (3,9), (5,9), (7,9), (9,9), (11,9), (1,11), (3,11), (5,11), (7,11), (9,11), (11,11). A cross-shaped constellation is shown on the right, with points at (13,1), (15,1), (13,3), (15,3), (13,5), (15,5), (13,7), (15,7), (13,9), (15,9), (13,11), (15,11), (13,13), (15,13), (13,15), (15,15). Arrows indicate the mapping of points from the rectangular constellation to the cross-shaped constellation. Labels like '001/0001', '101/0001', '111/0001', '011/0001' are present above some points. A small text 'G.9960(18)-Cor.2(20)_F10-21' is at the bottom right.](2b767b048e388ae309771bc57d56e136_img.jpg) + +Figure 10-21: Transformation of rectangular constellation into cross-shaped constellation for b = 7 (first quadrant). The plot shows I on the x-axis and Q on the y-axis. A rectangular constellation of 16 points is shown on the left, with points at (1,1), (3,1), (5,1), (7,1), (9,1), (11,1), (1,3), (3,3), (5,3), (7,3), (9,3), (11,3), (1,5), (3,5), (5,5), (7,5), (9,5), (11,5), (1,7), (3,7), (5,7), (7,7), (9,7), (11,7), (1,9), (3,9), (5,9), (7,9), (9,9), (11,9), (1,11), (3,11), (5,11), (7,11), (9,11), (11,11). A cross-shaped constellation is shown on the right, with points at (13,1), (15,1), (13,3), (15,3), (13,5), (15,5), (13,7), (15,7), (13,9), (15,9), (13,11), (15,11), (13,13), (15,13), (13,15), (15,15). Arrows indicate the mapping of points from the rectangular constellation to the cross-shaped constellation. Labels like '001/0001', '101/0001', '111/0001', '011/0001' are present above some points. A small text 'G.9960(18)-Cor.2(20)\_F10-21' is at the bottom right. + +**Figure 10-21 – Transformation of rectangular constellation into cross-shaped constellation for $b = 7$ (first quadrant)** + +**10.1.4.3.1.3 Constellations for even number of bits (MLC encoding)** + +When working in MLC mode, the steps described in clause 10.1.4.3.1.1 shall be followed if $b \leq \text{max\_coded\_bits}$ . + +If $b > \text{max\_coded\_bits}$ , the constellation mapping process is the following: + +- The following variables are defined: + - $b$ : Total number of bits of current constellation + - $M$ : Total number of points of current constellation + - $M = 2^b$ + - $c$ : Number of encoded bits (6) + - $M\_coded$ : Total number of points of encoded constellation + - $M\_coded = 2^c = 64$ + - $u$ : Number of non-coded bits. + - $M\_non\_coded$ : Total number of points of non-coded constellation + - $M\_non\_coded = 2^u$ + - $b = c + u$ +- $c$ encoded bits from the Encoded payload block shall be mapped into a $M\_coded$ -QAM constellation point ( $\{I_{cod}, Q_{cod}\}$ ) following the steps defined in clause 7.1.4.3.1.1 +- $u$ non-coded bits from the Non-coded payload block shall be mapped into a $M\_non\_coded$ -QAM constellation point ( $\{I_{non}, Q_{non}\}$ ) following the steps defined in clause 10.1.4.3.1.1 + - The resulting two constellation points shall be combined to obtain a unique M-QAM point +- The combination consists of two steps: the non-coded constellation point is scaled and then the coded constellation point is added to obtain the final M-QAM point: + +$$I = I_{non} * \text{sqr}(M\_coded) + I_{cod}$$ + +$$Q = Q_{non} * \text{sqr}(M\_coded) + Q_{cod}$$ + +#### 10.1.4.3.1.4 Constellations for odd number of bits (MLC encoding) + +When working in MLC mode, the steps described in clause 10.1.4.3.1.2 shall be followed if $b \leq \text{max\_coded\_bits}$ . + +If $b > \text{max\_coded\_bits}$ , the constellation mapping process is the following: + +- The following variables are defined: + - $b$ : Total number of bits of current constellation + - $M$ : Total number of points of current constellation + - $M = 2^b$ + - $c$ : Number of encoded bits (6) + - $M\_coded$ : Total number of points of encoded constellation + - $M\_coded = 2^c = 64$ + - $u$ : Number of non-coded bits. + - $M\_non\_coded$ : Total number of points of non-coded constellation + - $M\_non\_coded = 2^u$ + - $b = c + u$ +- $c$ encoded bits from the Encoded payload block shall be mapped into a $M\_coded$ -QAM constellation point ( $\{I_{cod}, Q_{cod}\}$ ) following the steps defined in clause 7.1.4.3.1.1 + +- u non-coded bits from the Non-coded payload block shall be mapped into a M\_non\_coded-QAM constellation ( $\{I_{\text{non}}, Q_{\text{non}}\}$ ) following next steps: + - $2^u$ constellation points shall be set as a rectangle, with $2^{U1}$ columns (or points on the $I$ -axis) and $2^{U2}$ rows (or points on the $Q$ -axis), where $U1 = \text{ceiling}(u/2)$ and $U2 = \text{floor}(u/2)$ . The mapping of these points shall be computed using the following steps: + - Divide the incoming group of bits into two subgroups, so that $U1$ LSBs form the first subgroup ( $I$ -group) and $U2$ MSBs form the second subgroup ( $Q$ -group); both subgroups are incoming LSBs (which are $d_0$ and $d_{U2+1}$ , respectively) first. + - Compute values of $I$ and $Q$ of a rectangular constellation for the incoming group $\{d_{u-1}, d_{u-2}, \dots, d_0\}$ as: + +$$I = \text{sgn}_I \times \text{val}_I$$ + +$$Q = \text{sgn}_Q \times \text{val}_Q$$ + +- The values of $\text{sgn}$ and $\text{val}$ shall be computed as presented in Table 10-62.1 using bits of $I$ -group to compute $I$ and bits of $Q$ -group to compute $Q$ . + +**Table 10-62.1 – Computation rule for $\text{sgn}$ and $\text{val}$** + +| I – component | Q – component | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| – compute $\text{sgn}_I = 2 \times d_0 - 1$ | – compute $\text{sgn}_Q = 2 \times d_{U1} - 1$ | +| – compute $\text{val}_I = I_{2 \times U1} $ | – compute $\text{val}_Q = Q_{2 \times U2} $ | +| NOTE 1 – $I_{2 \times U1}$ is the value of $I$ for $(2 \times U1)$ -bit group $\{0, d_{u-1}, d_{u-2}, \dots, d_0\}$ computed as defined in Table 7-61. | | +| NOTE 2 – $Q_{2 \times U2}$ is the value of $Q$ for $(2 \times U2)$ -bit group $\{d_{u-1}, d_{u-2}, \dots, d_1\}$ computed as defined in Table 7-61. | | +| NOTE 3 – $ X $ is the absolute value of $X$ . | | + +- The resulting two constellation points shall be combined to obtain a unique M-QAM point +- The combination consists of two steps: the non-coded constellation point is scaled and then the coded constellation point is added to obtain the final M-QAM point: + +$$I = I_{\text{non}} * \text{sqr}(M_{\text{coded}}) + I_{\text{cod}}$$ + +$$Q = Q_{\text{non}} * \text{sqr}(M_{\text{coded}}) + Q_{\text{cod}}$$ + +- This process results into a rectangular constellation. In order to optimize the constellation in terms of power, the rectangular constellation shall be transformed by changing their $\{I, Q\}$ coordinates to $\{I^*, Q^*\}$ in the following way: + - For $u > 1$ , transform $\{s = (2^{\text{ceiling}(b/2)} - 2^{\text{floor}(b/2)})/4\}$ columns of constellation points in the constellation sets of each quadrant to build a cross-shaped constellation following next steps: + +$$(I^*, Q^*) = \begin{cases} (I - 4s, Q + 8s), & \text{if } I > 6s, Q < -2s \\ (I - 4s, Q - 4s), & \text{if } I > 6s, -2s < Q < 0 \\ (I - 8s, Q + 4s), & \text{if } I > 6s, 0 < Q < 2s \\ (I - 8s, Q - 8s), & \text{if } I > 6s, Q > 2s \\ (I + 8s, Q + 8s), & \text{if } I < -6s, Q < -2s \\ (I + 8s, Q - 4s), & \text{if } I < -6s, -2s < Q < 0 \\ (I + 4s, Q + 4s), & \text{if } I < -6s, 0 < Q < 2s \\ (I + 4s, Q - 8s), & \text{if } I < -6s, Q > 2s \\ (I, Q), & \text{otherwise} \end{cases}$$ + +- For $u = 1$ , the following transformation shall be carried out to build a more power efficient constellation (diamond-shaped constellation in this case): + +$$b_I = \text{ceil}\left(\frac{b}{2}\right);$$ + +$$b_Q = \text{floor}\left(\frac{b}{2}\right);$$ + +$$imax = 2^{b_I};$$ + +$$qmax = 2^{b_Q};$$ + +$$(I', Q') = \begin{cases} (-\text{sign}(I) * (imax - \text{abs}(I)), Q + imax), & \text{if } Q < (\text{abs}(I) - qmax) \\ (I, Q), & \text{otherwise} \end{cases}$$ + +$$(I^*, Q^*) = (I', Q' - qmax + 1)$$ + +### 10.1.4.3.2 Constellation point scaling + +See clause 7.1.4.3.2. + +#### 10.1.4.3.2.1 Power normalization factor + +The values $(I, Q)$ for each constellation point of each subcarrier shall be scaled such that all constellations, regardless of their size, have the same average power. The required scaling, $\chi(b)$ , for a subcarrier with $b$ -bit loading depends only on the value of $b$ and shall be set as presented in Table 10-63. + +**Table 10-63 – Power normalization factor** + +| Number of bits loaded ( $b$ ) | Scaling factor ( $\chi$ )
(linear scale) | +|-------------------------------|---------------------------------------------| +| 1 | 1 | +| 2 | $1/\sqrt{2}$ | +| 3 | $1/\sqrt{6}$ | +| 4 | $1/\sqrt{10}$ | +| 5 | $1/\sqrt{20}$ | +| 6 | $1/\sqrt{42}$ | +| 7 | $1/\sqrt{82}$ | + +**Table 10-63 – Power normalization factor** + +| Number of bits loaded (b) | Scaling factor (\chi)
(linear scale) | +|-----------------------------------------|--------------------------------------------------------------| +| 8 | $1/\sqrt{170}$ | +| 9 | $1/\sqrt{330}$ | +| 10 | $1/\sqrt{682}$ | +| 11 | $1/\sqrt{1322}$ | +| 12 | $1/\sqrt{2730}$ | +| 13 | $1/\sqrt{5290}$ | +| 14 | $1/\sqrt{10922}$ | + +**10.1.4.3.2.2 Transmit spectrum shaping** + +See clause 7.1.4.3.2.2. + +**10.1.4.3.2.3 Gain adjustment** + +See clause 7.1.4.3.2.3. + +**10.1.4.3.3 Constellation scrambler** + +See clause 7.1.4.3.3. + +**Figure 10-22 – See Figure 7-22** + +(This figure has been intentionally left blank) + +**Table 10-64 – See Table 7-64** + +(This table has been intentionally left blank) + +**10.1.4.4 OFDM modulator** + +See clause 7.1.4.4. + +**10.1.4.4.1 IDFT** + +See clause 7.1.4.4.1. + +**Figure 10-23 – See Figure 7-23** + +(This figure has been intentionally left blank) + +**10.1.4.4.2 Cyclic extension** + +See clause 7.1.4.4.2. + +**10.1.4.4.3 Symbol timing** + +See clause 7.1.4.4.3. + +#### 10.1.4.4.4 Windowing, overlap and add + +See clause 7.1.4.4.4 + +**Figure 10-24 – See Figure 7-24** + +(This figure has been intentionally left blank) + +#### 10.1.4.4.5 Frequency up-shift + +See clause 7.1.4.4.5. + +#### 10.1.4.4.6 Output signal + +See clause 7.1.4.4.6. + +### 10.1.4.5 Preamble, INUSE, PR, NACK and IDPS signals + +#### 10.1.4.5.1 General preamble structure + +The preamble is prepended to every PHY frame defined in clause 10.1.2.1. It is intended to assist the receiver in detecting, synchronizing to the frame boundaries, and acquiring the physical layer parameters such as initial channel estimation and OFDM symbol alignment. In full-duplex communications, it also indicates the identity of the secondary node in a frame exchange. The preamble shall meet the same transmit PSD mask (i.e., notches, shapes) as the header and the payload symbols. + +Table 10-65 presents the general structure of the preamble. Each section $I$ comprises $N_I$ repetitions of an OFDM symbol ( $S_I$ ) employing subcarrier spacing $k_I \times F_{SC}$ , where $F_{SC}$ denotes the subcarrier spacing of the payload. A zero value for $N_I$ means that section $I$ is not included in the preamble. The values of $k_I$ shall be selected from the set 1, 2, 4 or 8. The preamble subcarriers of section $I$ shall be one in every $k_I$ subcarriers with respect to the subcarriers used for the payload OFDM symbol starting from subcarrier zero. Each preamble section shall be windowed as necessary in order to comply with the PSD mask. This is illustrated in Figure 10-25. + +**Table 10-65 – General structure of the preamble** + +| | 1st section | 2nd section | | +|--------------------------------------------|-------------|-----------------------|--| +| Number of symbols ( $N_I$ ) (Note 1) | $N_1$ | $N_2$ | | +| Subcarrier spacing ( $k_I \times F_{SC}$ ) | $k_1$ | $k_2 = k_1$ (Note 2) | | +| OFDM symbol ( $S_I$ ) | $S_1$ | $S_2 = -S_1$ (Note 3) | | + +NOTE 1 – $N_I$ does not include windowing. +NOTE 2 – The subcarrier spacing of the 2nd section shall be equal to the subcarrier spacing of the 1st section. +NOTE 3 – The OFDM symbol of the 2nd section shall be an inverted time-domain waveform of the 1st section. + +Figure 10-25 shows the preamble waveform. The specific preamble types and construction methods are defined in clause 10.2. + +![Figure 10-25 – Preamble waveform diagram showing three sections: 1st section (S1), 2nd section (S2), and PHY-frame header (GI_HD).](88c92858439684b2103e88cb143fb98e_img.jpg) + +The diagram illustrates the preamble waveform structure, divided into three main sections: + +- 1st section:** Contains $N_1$ symbols labeled $S_1$ . The tone spacing is $k_1 \times F_{SC}$ . The total duration is marked with a bracket and $\beta$ . +- 2nd section:** Contains $N_2$ symbols labeled $S_2$ . The tone spacing is $k_2 \times F_{SC}$ . The total duration is marked with a bracket and $\beta$ . +- PHY-frame header:** Contains a guard interval $GI\_HD$ and the PHY-frame header. The tone spacing is $F_{SC}$ . The total duration is marked with a bracket and $\beta$ . + +The diagram also shows the following parameters and notes: + +- Guard interval $GI\_HD$ duration is marked as $\beta/2$ . +- Overlap between sections is indicated by $\beta/2$ markers at the boundaries. +- NOTE: $K_2 = K_1$ , $S_2 = -S_1$ . +- Reference: G.9960(18)-Cor.2(20)\_F10-25. + +Figure 10-25 – Preamble waveform diagram showing three sections: 1st section (S1), 2nd section (S2), and PHY-frame header (GI\_HD). + +**Figure 10-25 – Preamble waveform** + +**10.1.4.5.2 INUSE, PR, NACK and IDPS signals general structure** + +See clause 7.1.4.5.2. + +**Table 10-66 – See table 7-66** + +(This table has been intentionally left blank) + +**10.1.4.5.3 Preamble, INUSE, PR NACK and IDPS signal generation** + +See clause 7.1.4.5.3. + +**10.1.4.5.3.1 Frequency-domain symbol generation** + +**10.1.4.5.3.1.1 Preamble** + +See clause 7.1.4.5.3.1.1. + +**10.1.4.5.3.1.2 INUSE, PR, NACK and IDPS signals** + +See clause 7.1.4.5.3.1.2. + +**10.1.4.5.3.2 Modulation** + +**10.1.4.5.3.2.1 Modulation of the preamble** + +For the non-masked subcarriers of the preamble, a bit sequence of all ones shall be mapped using the 1-bit constellation as specified in clause 10.1.4.3.1.2. Other bit sequences are for further study. + +Two constellation scrambler LFSR generators shall work in parallel for the modulation of the preamble: one for odd indexed subcarriers (first constellation scrambler LFSR generator, from now on) and the other one for even indexed subcarriers (second constellation scrambler LFSR generator, from now on). This way, the seed used for initializing the second constellation scrambler LFSR generator shall indicate the DEVICE\_ID of the secondary node in a full-duplex frame exchange. + +The first constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a seed that is section and medium dependent. The default value of the seed is defined in clause 10.2. Additional, domain-specific seeds are also defined in clause 10.2. The seed used shall either be the default seed or a domain-specific seed, as indicated in the "TXOP Attributes Extension Data" of the MAP (see clause 8.8.4.1.1 of [ITU-T G.9961]). Whenever usage of a domain-specific seed is indicated, the appropriate seed shall be selected from the pool of seeds in the tables in clause 10.2 based on the DOD (Domain ID). + +NOTE – This mechanism may be used by a DM whenever it detects the presence of a neighbouring network (regardless of the transmission technology being used by the neighbouring network) in order to reduce the level of interference to the neighbouring network. + +The second constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a seed with value DEFAULT\_SEC\_SCRAMBLER\_SEED. Additional 'device-id-specific' seeds may also be defined by the DM and conveyed to the nodes of the network through the additional domain information domain info sub-field of the MAP. The seed used shall either be the default seed or a device-id-specific seed. If the preamble belongs to a half-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized to the default seed. On the other hand, if the preamble belongs to a full-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized to a 'device-id-specific' seed indicating the DEVICE\_ID of the secondary node. A node shall not initiate a full duplex exchange if the 'device-id-specific' seed of the second constellation scrambler LFSR generator seed has not been communicated by the DM. + +For preamble generation, the output of the mapper shall be subsequently rotated using the two bits that are the LSBs of the LFSR, s1 and s2, as defined in Table 10-64 (constellation scrambler) resulting in constellation point $Z_i$ . The odd indexed subcarriers shall be rotated using the output of the first LFSR and the even indexed subcarriers shall be rotated using the output of the second LFSR. + +Both, the first and the second LFSR generators shall be advanced by two bits for each preamble's subcarrier (for both SSC and MSC) in the order specified in clause 10.1.4.3.3. + +The first constellation scrambler LFSR generator shall advance after processing an odd indexed subcarrier, while the second constellation scrambler LFSR generator shall advance after processing an even indexed subcarrier. + +#### **10.1.4.5.3.2.2 Modulation of the INUSE, PR, NACK and IDPS symbols** + +See clause 7.1.4.5.3.2.2. + +#### **10.1.4.5.3.3 Time-domain symbol generation** + +##### **10.1.4.5.3.3.1 Preamble** + +The $Z_i$ values shall be modulated on to OFDM symbols as described in clause 10.1.4.4.1. + +The output time-domain symbol shall be repeated $N_I$ times where $N_I$ denotes the number of replicas within section $I$ . + +The first and second sections of the preamble shall be windowed, overlapped and added as described below: + +- 1) First section: + - a) The first short symbol of the first section is cyclically extended by prepending $\beta/2$ samples. + - b) The last short symbol of the first section is cyclically extended by appending $\beta/2$ samples. + - c) The first and last $\beta$ samples of the extended first section are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ respectively. +- 2) Second section: + - a) The first short symbol of the second section is cyclically extended by prepending $\beta/2$ samples. + - b) The last short symbol of the second section is cyclically extended by appending $\beta/2$ samples. + - c) The first and last $\beta$ samples of the extended second section are windowed with a window function $w_\beta(n)$ and $w_\beta(\beta-n-1)$ respectively. + +3) Overlap and add: + +- a) The $\beta$ windowed samples at the end of the first section and at the beginning of the second section are overlapped and added. +- b) The $\beta$ windowed samples at the end of the second section are overlapped and added with the $\beta$ windowed samples at the beginning of the PHY-frame header as described in clause 10.1.4.4.4. + +$w_\beta(n)$ shall comply with the rules specified in clause 10.1.4.4.4. + +This is illustrated in Figure 10-26. + +![Figure 10-26 – Preamble time-domain generation. The diagram shows two horizontal timelines representing signal sections. The top timeline shows a sequence of symbols S1, S1, S1, ..., S1, S1, S1. The first S1 is preceded by a beta/2 samples window, and the last S1 is followed by a beta/2 samples window. The total duration of the S1 symbols is labeled N1 symbols. The overlap between the first S1 and the second S1 is labeled beta samples. The overlap between the last S1 and the next section is also labeled beta samples. The bottom timeline shows a sequence of symbols S2, S2, ..., S2, S2. Similar to the top timeline, it has beta/2 samples windows at the start and end, and a total duration of N2 symbols. The overlap between the last S2 and the next section is labeled beta samples. Below the bottom timeline, a curved arrow points to a section labeled 'Header'.](f79cb254efa2e37d7facb055cf90086e_img.jpg) + +Figure 10-26 – Preamble time-domain generation. The diagram shows two horizontal timelines representing signal sections. The top timeline shows a sequence of symbols S1, S1, S1, ..., S1, S1, S1. The first S1 is preceded by a beta/2 samples window, and the last S1 is followed by a beta/2 samples window. The total duration of the S1 symbols is labeled N1 symbols. The overlap between the first S1 and the second S1 is labeled beta samples. The overlap between the last S1 and the next section is also labeled beta samples. The bottom timeline shows a sequence of symbols S2, S2, ..., S2, S2. Similar to the top timeline, it has beta/2 samples windows at the start and end, and a total duration of N2 symbols. The overlap between the last S2 and the next section is labeled beta samples. Below the bottom timeline, a curved arrow points to a section labeled 'Header'. + +G.9960(18)-Cor.2(20)\_F10-26 + +**Figure 10-26 – Preamble time-domain generation** + +The number of samples at the Nyquist rate in the preamble shall be: + +$$N_{pr} = \beta + N_1 \frac{N}{k_1} + N_2 \frac{N}{k_2}$$ + +#### 10.1.4.5.3.3.2 INUSE, PR, NACK and IDPS signals + +See clause 7.1.4.5.3.3.2. + +#### 10.1.4.6 PMD control parameters + +See clause 7.1.4.6. + +**Table 10-67 – See Table 7-67** + +(This table has been intentionally left blank) + +**Table 10-68 – See Table 7-68** + +(This table has been intentionally left blank) + +#### 10.1.4.7 Symbol boost + +See clause 7.1.4.7. + +### 10.1.5 Transmit PSD mask + +See clause 7.1.5. + +### 10.1.6 Electrical specifications + +#### 10.1.6.1 Transmit clock tolerance + +See clause 7.1.6.1. + +#### 10.1.6.2 Relative transmit clock accuracy + +See clause 7.1.6.2. + +#### 10.1.6.3 Up-convert frequency tolerance + +See clause 7.1.6.3. + +## 10.2 Medium dependent specification + +### 10.2.1 Physical layer specification over telephone lines + +#### 10.2.1.1 Control parameters + +See clause 7.2.1.1. + +#### 10.2.1.2 Preamble, INUSE, PR and NACK signals + +##### 10.2.1.2.1 Preamble structure + +Table 10-69 illustrates the preamble structure for a telephone line. + +**Table 10-69 – Preamble structure for transmission over telephone lines** + +| | 1st section | 2nd section | | +|--------------------------------------------|-------------|-------------|--| +| Number of symbols ( $N_i$ ) | 8 | 2 | | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | $k_i = 8$ | $k_i = 8$ | | + +##### 10.2.1.2.2 INUSE, PR and NACK signal generation parameters for telephone lines + +See clause 7.2.1.2.2. + +**Table 10-70 – See Table 7-70** + +(This table has been intentionally left blank) + +##### 10.2.1.2.3 Modulation of the preamble for telephone lines + +When using a default seed, the first constellation scrambler LFSR generator (see clause 10.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed that is section dependent as defined in Table 10-71. + +When using a "domain-specific" seed, the first constellation scrambler LFSR generator (see clause 10.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM in the DM\_Defined\_Seed field of the additional domain information subfield (see clause 8.8.5.15 of [[ITU-T G.9961](#)]). The DM shall choose the seed from the set of seeds corresponding to the DOD of the domain, as specified in Table 10-71.1). + +When the preamble belongs to a half-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a default seed that is section dependent as defined in clause 10.1.4.5.3.2.1. + +When the preamble belongs to a full-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM depending on the DEVICE\_ID of the secondary node of the frame exchange (see clause 10.1.4.5.3.2.1). + +**Table 10-71 – Default first constellation scrambler initialization seed values for the preamble, for telephone lines** + +| Medium | 1st section | | +|----------------|--------------------|--| +| Telephone line | 0127 16 | | + +**Table 10-71.1 – Set of first domain-specific constellation scrambler initialization seed values for the preamble, for telephone lines** + +| DOD (Domain ID) | 1st Section | | +|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 0 | 024E 16 ; 17A9 16 ; 0F53 16 ; 10F3 16 ;
1545 16 ; 01E6 16 ; 0A8A 16 ; 098E 16 | | +| 1 | 06B2 16 ; 17C9 16 ; 00A7 16 ; 131C 16 ;
0D64 16 ; 0F93 16 ; 014F 16 ; 14FC 16 | | +| 2 | 044C 16 ; 0B96 16 ; 040D 16 ; 0119 16 ;
037E 16 ; 0074 16 ; 1A7E 16 ; 0226 16 | | +| 3 | 1E0E 16 ; 172C 16 ; 081B 16 ; 0232 16 ;
06FC 16 ; 00E8 16 ; 1C1D 16 ; 1ADE 16 | | +| 4 | 1B5B 16 ; 05B3 16 ; 084F 16 ; 0029 16 ;
0637 16 ; 121E 16 ; 1EFB 16 ; 102F 16 | | +| 5 | 154F 16 ; 14C7 16 ; 0CDE 16 ; 0880 16 ;
09AC 16 ; 096B 16 ; 0D6F 16 ; 0DAD 16 | | +| 6 | 02D9 16 ; 0427 16 ; 1014 16 ; 131B 16 ;
180B 16 ; 043D 16 ; 1DF6 16 ; 005F 16 | | +| 7 | 0A9E 16 ; 098F 16 ; 19BD 16 ; 1100 16 ;
1358 16 ; 12D7 16 ; 1016 16 ; 02DE 16 | | +| 8 | 0B14 16 ; 1437 16 ; 0AF6 16 ; 15CF 16 ;
1E04 16 ; 0CDF 16 ; 14AF 16 ; 1530 16 | | +| 9 | 1B55 16 ; 085F 16 ; 0592 16 ; 1B2A 16 ;
1E42 16 ; 07E8 16 ; 1503 16 ; 0F10 16 | | +| 10 | 038A 16 ; 0A34 16 ; 1878 16 ; 1170 16 ;
03E4 16 ; 1251 16 ; 0253 16 ; 0F66 16 | | +| 11 | 0ADE 16 ; 069D 16 ; 0583 16 ; 08E9 16 ;
054A 16 ; 0397 16 ; 016F 16 ; 058A 16 | | +| 12 | 0A1B 16 ; 157B 16 ; 1AE7 16 ; 0F02 16 ;
066F 16 ; 0A57 16 ; 0A98 16 ; 0DAA 16 | | +| 13 | 042F 16 ; 12C9 16 ; 1D95 16 ; 01FC 16 ;
1C85 16 ; 0FD0 16 ; 0A06 16 ; 1E20 16 | | +| 14 | 0715 16 ; 1469 16 ; 10F0 16 ; 02E1 16 ;
07C9 16 ; 04A3 16 ; 04A6 16 ; 1ECC 16 | | +| 15 | 15BC 16 ; 0D3A 16 ; 0B06 16 ; 11D2 16 ;
0A95 16 ; 072F 16 ; 03F9 16 ; 1C49 16 | | + +#### 10.2.1.2.4 Modulation of the INUSE, PR and NACK signals for telephone lines + +See clause 7.2.1.2.4. + +#### 10.2.1.3 PSD mask specifications + +See clause 7.2.1.3. + +#### 10.2.1.4 Permanently masked subcarriers + +See clause 7.2.1.4. + +### 10.2.2 Physical layer specification over power lines + +This clause is for further study. + +### 10.2.3 Physical layer specification over coax + +#### 10.2.3.1 Control parameters + +See clause 7.2.3.1. + +#### 10.2.3.2 Preamble, PR signal, and INUSE signal + +##### 10.2.3.2.1 Preamble structure + +Table 10-76 illustrates the preamble structure for coax. + +**Table 10-76 – Preamble structure for transmission over coax** + +| | 1st section | 2nd section | | +|--------------------------------------------|-------------|-------------|--| +| Number of symbols ( $N_i$ ) | 10 | 4 | | +| Subcarrier spacing ( $k_i \times F_{SC}$ ) | $k_i = 4$ | $k_i = 4$ | | + +**Table 10-77 – Placeholder for table** + +(This table has been intentionally left blank) + +##### 10.2.3.2.2 INUSE, PR and NACK signal generation parameters for coax + +See clause 7.2.3.2.2. + +**Table 10-78 – See table 7-78** + +(This table has been intentionally left blank) + +##### 10.2.3.2.3 Modulation of the preamble for coax + +When using a default seed, the constellation scrambler LFSR generator (see clause 10.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed that is section dependent as defined in Table 10-80. + +When using a "domain-specific" seed, the first constellation scrambler LFSR generator (see clause 10.1.4.3.3) shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM in the DM\_Defined\_Seed field of the additional domain information subfield (see clause 8.8.5.15 of [[ITU-T G.9961](#)]). + +When the preamble belongs to a half-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a default seed that is section dependent as defined in clause 10.1.4.5.3.2.1. + +When the preamble belongs to a full-duplex frame exchange, the second constellation scrambler LFSR generator shall be initialized at the beginning of each one of the used preamble sections to a seed defined by the DM depending on the DEVICE\_ID of the secondary node of the frame exchange (see clause 10.1.4.5.3.2.1). + +**Table 10-80 – Default first constellation scrambler initialization seed values for the preamble, for coax** + +| Medium | 1st section | +|--------|--------------------| +| Coax | 16E6 16 | + +Domain-specific constellation scrambler initialization seed values for the preamble for coax is for further study. + +#### 10.2.3.2.4 Modulation of the INUSE, PR and NACK signals for coax + +See clause 7.2.3.2.4. + +#### 10.2.3.3 PSD mask specifications + +See clause 7.2.3.3. + +#### 10.2.3.4 Permanently masked subcarriers + +See clause 7.2.3.4. + +#### 10.2.3.5 Coexistence on coax + +See clause 7.2.3.5. + +### 10.2.4 Transmitter EVM requirements + +The deviation of the actual transmit signal from the corresponding constellation point shall be estimated by the value of error vector magnitude (EVM) calculated as: + +$$EVM = 20 \log \frac{error\_vector\_RMS}{reference\_signal}$$ + +The interpretation of EVM components for a constellation point is illustrated in Figure 10-28. + +![Figure 10-28 – Interpretation of EVM. A vector diagram showing the relationship between a reference signal, an actual transmitted signal, and an error vector. The reference signal is a vector pointing to a point marked with a cross. The actual transmitted signal is a vector pointing to a point marked with a dot. The error vector is the vector difference between the actual transmitted signal and the reference signal, pointing from the cross to the dot. The diagram is labeled G.9960(18)-Cor.2(20)_F10-28.](0d8f6da9077a85e09077cdfbecae1838_img.jpg) + +Figure 10-28 – Interpretation of EVM. A vector diagram showing the relationship between a reference signal, an actual transmitted signal, and an error vector. The reference signal is a vector pointing to a point marked with a cross. The actual transmitted signal is a vector pointing to a point marked with a dot. The error vector is the vector difference between the actual transmitted signal and the reference signal, pointing from the cross to the dot. The diagram is labeled G.9960(18)-Cor.2(20)\_F10-28. + +**Figure 10-28 – Interpretation of EVM** + +The EVM for a subcarrier at the output of a transceiver (i.e., at the MDI reference point), for at least 90% of active subcarriers, shall not exceed values presented in Table 10-81 at the maximum transmit power that the transceiver is capable of transmitting within a transmit PSD mask. + +**Table 10-81 – Maximum EVM values for different media and operational frequency band** + +| Medium | EVM (Note 1) | +|----------------|------------------------------------------------------| +| Power line | –33 dB for $f \leq 30$ MHz
–3 dB for $f > 30$ MHz | +| Telephone line | –40 dB | +| Baseband coax | –40 dB | + +NOTE 1 – Values of EVM shall be verified using standard termination impedance for each type of medium (see clause 7.2.5). + +#### 10.2.5 Termination impedance + +See clause 7.2.5. + +#### 10.2.6 Total transmit power + +See clause 7.2.6. + +#### 10.2.7 Receiver input impedance + +See clause 7.2.7. + +#### 10.2.8 Longitudinal conversion loss + +See clause 7.2.8. + +##### 10.2.8.1 LCL for phoneline + +See clause 7.2.8.1. + +## **Annex A** + +### **Regional requirements for North America** + +(This annex forms an integral part of this Recommendation.) + +(This annex is only valid when using Profile 1 OFBs described in clause 7) + +For further study. + +## **Annex B** + +(This annex has been intentionally left blank.) + +## Annex C + +### Regional requirements for Japan + +(This annex forms an integral part of this Recommendation.) + +(This annex is only valid when using Profile 1 OFBs described in clause 7.) + +#### C.1 Scope + +This annex describes domestic practices, standards for each medium (coax cable, telephone line and power line) and the way to apply the ITU-T G.9960 system under those conditions in Japan. + +#### C.2 Medium dependent specification + +##### C.2.1 Physical layer specification over telephone lines + +For further study. + +##### C.2.2 Physical layer specification over power lines + +All nodes over power lines shall comply with national regulations in Japan [b-Regulations], which states that the frequency band that can be used without any licence is restricted to between 2 MHz and 30 MHz, and the interference level due to power-line communication is also restricted. Through experiments and evaluations, Japan set these regulations that are not the same as the description given in clause 7.2.2. + +Furthermore, the regulations give limitations of where they can be used; that is, the usage of power-line communications is only allowed inside buildings and is not allowed outside buildings. + +##### C.2.3 Physical layer specification over coax + +###### C.2.3.1 Operational frequency band + +In addition to the OFDM control parameters in Table 6-6 of [ITU-T G.9964], the OFDM control parameters shown in Table C.1 may be used. It should be noted that the ITU-T G.9960 signals over coax cables should not interfere with services offered in the coax cables to customers by the cable television operators, or with signals transmitted from receiving antennas of terrestrial and satellite broadcasting in the coax cables. + +Table C.1 – Optional OFDM control parameters for coax cables in Japan + +| Domain type | Coax RF | +|-------------|--------------------------------------------------------------------| +| OFB name | 200 MHz-CRF
(Notes 2, 3) | +| $N$ | 1024 | +| $F_{SC}$ | 195.3125 kHz | +| $N_{GI}$ | $K \times N/32$ , $k = 1, 2, 3, \dots, 8$ samples @ 200 Msamples/s | +| $N_{GI-HD}$ | $N/4 = 256$ samples @ 200 Msamples/s | +| $N_{GI-DF}$ | $N/4 = 256$ samples @ 200 Msamples/s | +| $\beta$ | 32 | +| $F_{US}$ | 100 MHz | +| $F_{UC}$ | $Z$ (Note 4) | + +**Table C.1 – Optional OFDM control parameters for coax cables in Japan** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| Domain type | Coax RF | +| OFB name | 200 MHz-CRF
(Notes 2, 3) | +| Subcarrier indexing rule (Note 1) | Rule #1 if $X = Y = Z$ , or
rule #2 if $X + 25 \text{ MHz} = Y + 50 \text{ MHz} = Z + 100 \text{ MHz}$
(Note 5) | +| NOTE 1 – See clause 7.1.4.1 for more details on subcarrier indexing rules.
NOTE 2 – The 200 MHz OFB on this table and the 50 MHz and 100 MHz OFBs shown in Table 6-6 of [ITU-T G.9964] may be used by nodes operating in the same coax RF domain.
NOTE 3 – The range of subcarrier frequencies is between $Z \text{ MHz}$ and $(Z + 200) \text{ MHz}$ .
NOTE 4 – The values of $F_{UC}$ shall be selected from the valid set defined in Table 7-67 and may be subject to regional spectrum management rules.
NOTE 5 – X and Y are $F_{UC}$ of OFB 50 MHz-CRF and 100 MHz-CRF respectively (see Table 6-6 of [ITU-T G.9964] ). | | + +**C.2.3.2 Preamble** + +This is the same as clause 7.2.3.2. + +**C.2.3.3 PSD mask specifications** + +Limit PSD masks for operation over RF coax are specified for the frequency range between 770 MHz and 1032 MHz and above 2070 MHz. Specifications of the limit PSD mask for other frequency bands are for further study. + +![Figure C.1: Limit PSD mask over RF coax for transceivers used between 770 MHz and 1032 MHz. The graph shows a trapezoidal PSD mask. The y-axis has levels -X and -Y. The x-axis is frequency in MHz with points f_L1, f_L2, f_H1, and f_H2. The mask starts at level -Y, rises linearly from f_L1 to f_L2 to reach level -X, remains flat at -X until f_H1, then falls linearly to level -Y at f_H2, and continues at -Y.](cf9b9abea4fbaa200888c82c924b769d_img.jpg) + +G9960(1 5)\_FC.1 + +Figure C.1: Limit PSD mask over RF coax for transceivers used between 770 MHz and 1032 MHz. The graph shows a trapezoidal PSD mask. The y-axis has levels -X and -Y. The x-axis is frequency in MHz with points f\_L1, f\_L2, f\_H1, and f\_H2. The mask starts at level -Y, rises linearly from f\_L1 to f\_L2 to reach level -X, remains flat at -X until f\_H1, then falls linearly to level -Y at f\_H2, and continues at -Y. + +**Figure C.1 – Limit PSD mask over RF coax for transceivers used between 770 MHz and 1032 MHz** + +The values of frequency spectrum parameters for coax are presented in Table C.2. It is assumed that interim points between those defined in Figure C.1 are obtained by linear interpolation (dB over linear frequency scale). + +**Table C.2 – Parameters of limit PSD mask over RF coax for transceivers used between 770 MHz and 1032 MHz** + +| Parameters | Frequency (MHz) | PSD (dBm/Hz) (Note) | Note/Description | +|---------------------------------------------------------|-----------------|---------------------|------------------| +| $F_C - f_{L1}$ | 130 | -Y | | +| $F_C - f_{L2}$ | 100 | -X | | +| $F_C$ | $M * 25$ MHz | -X | | +| $f_{H1} - F_C$ | 100 | -X | | +| $f_{H2} - F_C$ | 132 | -Y | | +| NOTE – $M = 36$ for 200 MHz, see Note 5 for other OFBs. | | | | + +NOTE 1 – In cases where additional spectrum shaping is used, as described in clause 5.2 of [ITU-T G.9964], the transmit PSD mask can be reduced in the relevant parts of this spectrum by switching subcarriers off or reducing their transmit power. + +NOTE 2 – More than one channel may be allocated within the limit PSD mask in Table C.2. In this case, out-of-band PSD of each channel should not interfere with other channels. The detailed requirements are for further study. + +NOTE 3 – Out-of-band spurious signals at the output of an ITU-T G.9960 node operating over coax in RF mode are supposed to meet the limit PSD mask defined in Table C.2. The limit for total power of out-of-band spurious signals is for further study. The requirements for in-band spurious signals are for further study. + +NOTE 4 – Specification of guard bands are for further study. + +NOTE 5 – Parameters of limit PSD mask over RF coax for OFBs 50 MHz and 100 MHz for Annex C should be the same as those in clause 6.3 of [ITU-T G.9964] PSD mask specifications with an arbitrary integer number of M, but not to exceed the PSD mask for Table C.2. + +NOTE 6 – Values for X and Y are for further study. + +![Figure C.2: Limit PSD mask over RF coax for transceivers used above 2070 MHz. The graph shows a trapezoidal PSD mask. The x-axis is frequency in MHz, with markers f_L1, f_L2, f_H1, and f_H2. The y-axis is PSD in dBm/Hz, with markers -X, -Z, and -Y. The mask starts at -Y dBm/Hz for frequencies below f_L1, rises linearly to -X dBm/Hz at f_L2, stays constant at -X dBm/Hz until f_H1, falls linearly to -Z dBm/Hz at f_H2, and then remains constant at -Z dBm/Hz for frequencies above f_H2.](f4aa9cdde1224cd00bdc4593068e6294_img.jpg) + +G9960(1.5)\_FC.2 + +Figure C.2: Limit PSD mask over RF coax for transceivers used above 2070 MHz. The graph shows a trapezoidal PSD mask. The x-axis is frequency in MHz, with markers f\_L1, f\_L2, f\_H1, and f\_H2. The y-axis is PSD in dBm/Hz, with markers -X, -Z, and -Y. The mask starts at -Y dBm/Hz for frequencies below f\_L1, rises linearly to -X dBm/Hz at f\_L2, stays constant at -X dBm/Hz until f\_H1, falls linearly to -Z dBm/Hz at f\_H2, and then remains constant at -Z dBm/Hz for frequencies above f\_H2. + +**Figure C.2 – Limit PSD mask over RF coax for transceivers used above 2070 MHz** + +**Table C.3 – Parameters of limit PSD mask over RF coax +for transceivers used above 2070 MHz** + +| Parameters | Frequency (MHz) | PSD (dBm/Hz) (Note) | Note/Description | +|------------------------------------------------------------------------|-----------------|---------------------|------------------| +| $f_{L1}$ | 2070 | –Y | | +| $f_{L2}$ | 2200 | –X | | +| $F_C$ | $M*25$ MHz | –X | | +| $f_{H1}$ | 2850 | –X | | +| $f_{H2}$ | 2950 | –Z | | +| NOTE – $M = 92$ or $110$ for $200$ MHz-RF. See Note 11 for other OFBs. | | | | + +NOTE 7 – In cases where additional spectrum shaping is used, as described in clause 5.2 of [ITU-T G.9964], the transmit PSD mask can be reduced in the relevant parts of this spectrum by switching subcarriers off or reducing their transmit power. + +NOTE 8 – More than one channel may be allocated within the limit PSD mask in Table C.3. In this case, the out-of-band PSD of each channel should not interfere with other channels. The detailed requirements are for further study. + +NOTE 9 – Out-of-band spurious signals at the output of ITU-T G.9960 node operating over coax in RF mode are supposed to meet the limit PSD mask defined in Table C.3. The limit for the total power of out-of-band spurious signals is for further study. The requirements for in-band spurious signals are for further study. + +NOTE 10 – Specification of guard bands are for further study. + +NOTE 11 – Parameters of limit PSD mask over RF coax for OFBs $50$ MHz and $100$ MHz for Annex C should be the same as those in clause 6.3 of [ITU-T G.9964] PSD mask specifications with arbitrary integer number of $M$ , but not to exceed the PSD mask for Table C.3. + +NOTE 12 – Values X, Y and Z are for further study. + +#### **C.2.3.4 Transmitter EVM requirements for coax RF** + +The EVM requirements are for further study. + +## **Annex D** + +(This annex has been intentionally left blank.) + +## **Annex E** + +(This annex has been intentionally left blank.) + +## Annex F + +### Usage of ITU-T G.9960 for optical transmission + +(This annex forms an integral part of this Recommendation.) + +(This annex is only valid when using the band limited profiles described in clause 7) + +#### F.1 Scope + +This annex describes the way to apply the ITU-T G.9960 system for optical transmission. + +#### F.2 Media dependent specification + +##### F.2.1 Physical layer specification over SI-POF (Step-index polymer/plastic optical fibres) + +The core parameters for an LED-based optical transmitter should be as described in Table F.1. + +**Table F.1 – Parameters for a LED-based optical transmitter** + +| Parameter | Value/Unit | +|-----------------------------------------|-----------------------------------------------------------| +| Centre wavelength | 640-660 nm | +| Maximum spectral width | 30 nm | +| Maximum optical transmit power | 0 dBm | +| Minimum optical bandwidth (–3 dB point) | 100 MHz for OFB 100 MHz-SB and 200 MHz for OFB 200 MHz-SB | + +The core parameters for the optical receiver should be as shown in Table F.2. + +**Table F.2 – Parameters for the optical receiver** + +| Parameter | Value/Unit | +|------------------------------|------------| +| Wavelength | 640-660 nm | +| Minimum receiver sensitivity | –20 dBm | + +NOTE 1 – Typically a cable will include one or two SI-POF. It is recommended that the cable will be compliant with categories A4a.1 and/or A4a.2 according to [b-IEC 60793-2-40]. + +NOTE 2 – For the cable connection to the optical receiver and the optical transmitter, a connector-less connection should be preferred. If connectors are used it is recommended that they will comply to standards such as SMI [b-IEC 61754-21] or SC/RJ [b-IEC 61754-24]. + +### F.2.2 Operational frequency band + +Table F.3 shows the valid OFDM control parameters for various bandplans defined for SI-POF: + +**Table F.3 – OFDM parameters for SI-POF** + +| Domain type | SI-POF | SI-POF | +|--------------------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| OFB name | 100 MHz – SB | 200 MHz – SB | +| $N$ | 512 | 1024 | +| $F_{SC}$ | 195.3125 kHz | 195.3125 kHz | +| $N_{GI}$ | $N/32 \times k$ for $k=1, \dots, 8$ samples @ 100 Msamples/s | $N/32 \times k$ for $k=1, \dots, 8$ samples @ 200 Msamples/s | +| $N_{GI-HD}$ | $N/4=128$ samples @ 100 Msamples/s | $N/4=256$ samples @ 200 Msamples/s | +| $N_{GI-DF}$ | $N/4=128$ samples @ 100 Msamples/s | $N/4=256$ samples @ 200 Msamples/s | +| $\beta$ | $N/32=16$ samples @ 100 Msamples/s | 32 | +| $F_{US}$ | 50 MHz | 100 MHz | +| $F_{UC}$ | 0 MHz | 0 MHz | +| Subcarrier indexing rule | Rule #1 | Rule #1 | +| NOTE – See clause 7.1.4.1 for more details on subcarrier indexing rules. | | | + + + + + + + +(0,1), (1,1), (1,1), (1,0), (0,1), (1,0), (1,0), (0,0), (0,0), (1,0), (0,0), (1,1), (1,0), (1,1), (0,0), (0,0), (0,1), (1,1), (0,0), (0,1), (0,0), (0,1), (0,1), (0,1), (1,1), (1,0), (1,1), (0,0), (1,0), (1,1), (1,1), (0,0), (1,1), (1,0), (1,0), (1,1), (1,0), (0,1), (1,0), (0,1), (1,0), (0,0), (1,0), (1,1), (1,1), (1,0), (0,1), (1,0), (1,0), (0,1), (0,0), (1,0), (0,0), (1,0), (0,0), (0,0), (0,0), (0,1), (0,1), (1,1)}. + +The *const\_scrambler\_sequence[i]* = (s1,s2) denotes the LFSR output for the subcarrier index *i*-1 (clause 7.1.4.3.3). That is, *const\_scrambler\_sequence*[1] = (1,1) corresponds to the subcarrier index 0, *const\_scrambler\_sequence*[2] = (0,0) to the subcarrier index 1, etc. + +**G.5.2 Constellation scrambler test vector 2** + +Using the test vector from clause G.4.1, the normalized constellation scrambler output corresponding to the first 512 subcarriers of the PFH of the PROBE frame considered in clause G.1.1 shall be: + +pfh\_cscram\_output[1:512] = $1/\sqrt{2}$ {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, -1-j, 1-j, 1-j, 1-j, -1-j, 1-j, -1-j, -1-j, -1-j, 1+j, -1+j, 1+j, 1+j, -1+j, 1+j, 1+j, 1-j, 1+j, -1-j, -1-j, -1-j, 1-j, -1-j, -1+j, 1-j, -1-j, -1+j, -1+j, 1+j, 1+j, 1+j, 1+j, -1-j, 1+j, -1-j, -1-j, 1-j, -1+j, -1+j, 1+j, 1-j, 1-j, -1-j, -1-j, 1+j, 1+j, 1-j, 1-j, -1+j, 1-j, -1-j, 1+j, 1+j, -1-j, 1-j, 1+j, -1+j, -1-j, -1-j, 1+j, 1-j, -1+j, 1+j, -1+j, 1+j, -1+j, 1+j, 1-j, -1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1-j, -1-j, -1-j, 1-j, 1-j, 1+j, -1+j, 1-j, 1+j, 1+j, 1+j, -1+j, -1+j, -1-j, -1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1-j, 1-j, 1+j, -1-j, 1-j, 1+j, 1-j, -1-j, 1+j, 1-j, 1-j, 1-j, 1-j, 1+j, -1-j, -1+j, -1+j, 1-j, 1+j, 1-j, 1-j, -1+j, -1+j, -1-j, -1+j, -1+j, 1-j, -1-j, -1+j, -1-j, -1-j, -1-j, -1+j, -1-j, -1+j, -1-j, -1+j, 1+j, -1-j, 1+j, -1-j, -1+j, 1-j, 1-j, -1-j, -1+j, -1-j, -1-j, 1-j, -1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1-j, -1+j, -1+j, -1-j, -1-j, -1-j, 1-j, 1-j, 1-j, 1-j, 1+j, 1-j, 1+j, 1-j, 1-j, 1+j, 1+j, 1+j, 1-j, 1-j, -1+j, -1-j, 1-j, -1-j, -1+j, -1-j, 1+j, -1-j, 1+j, -1-j, -1+j, 1-j, 1-j, -1-j, -1+j, -1-j, -1+j, 1-j, 1-j, 1+j, -1+j, -1+j, 1-j, 1+j, -1+j, -1-j, -1+j, 1-j, 1+j, 1+j, -1-j, 1-j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, -1-j, 1-j, -1+j, 1-j, -1+j, -1-j, -1-j, 1+j, -1+j, -1+j, -1+j, -1+j, 1+j, -1-j, -1-j, 1+j, -1+j, 1-j, 1-j, 1-j, -1-j, 1+j, 1+j, -1-j, -1+j, -1-j, 1-j, -1-j, 1-j, 1-j, 1-j, -1+j, -1-j, 1+j, 1-j, 1-j, -1+j, 1+j, -1+j, -1-j, 1-j, 1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1-j, 1+j, -1+j, -1+j, -1+j, -1+j, -1-j, -1+j, -1+j, -1-j, 1-j, 1+j, -1-j, 1+j, -1+j, 1+j, 1-j, 1-j, -1+j, -1+j, 1+j, -1-j, -1+j, -1-j, -1-j, -1+j, -1-j, -1-j, -1+j, -1-j, -1-j, -1-j, -1+j, -1-j, -1-j, 1-j, 1-j, -1+j, -1+j, 1-j, 1-j, 1+j, -1+j, 1-j, 1+j, -1-j, -1-j, 1-j, 1+j, 1+j, 1+j, -1+j, 1+j, 1+j, -1+j, -1+j, -1+j, -1+j, 1-j, 1-j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, 1-j, -1-j, 1-j, -1-j, 1-j, -1-j, -1+j, -1+j, -1+j, -1+j, -1+j, 1-j, -1-j, -1-j, -1-j, 1-j, -1-j, 1-j, -1-j, 1-j, -1-j, 1+j, -1+j, -1-j, -1-j, -1-j, 1-j, 1-j, 1-j, -1+j, 1-j, 1+j, 1-j, 1+j, 1-j, 1+j, 1+j, 1-j, 1-j, 1-j, 1+j, -1+j, -1-j, 1-j, -1+j, -1+j, 1+j, 1+j, -1+j, 1+j, -1-j, -1+j, 1-j, 1+j, -1+j, -1-j, 1+j, -1+j, 1+j, 1+j, -1+j, -1-j, -1+j, -1-j, 1-j, 1-j, 1-j, 1+j, -1+j, -1-j, 1-j, -1+j, -1-j, -1+j, -1-j, 1-j, 1-j, 1-j, 1-j, -1+j, 1+j, 1+j, 1-j, 1-j, 1-j, -1+j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j, 1+j, -1+j, -1+j}. + +The *pfh\_cscram\_output*[1] corresponds to the subcarrier index 0, *pfh\_cscram\_output*[2] to the subcarrier index 1, etc. + +**G.6 Preamble generation test vectors** +**G.6.1 Preamble generation test vector 1** + +The constellation scrambler is used to generate the preamble as defined in clause 7.1.4.5.3.2.1. The bit sequence generated by the LFSR of the constellation scrambler for the subcarriers of the first section of the preamble assuming 25 MHz-PB OFB shall be + +const\_scrambler\_sequence[1:128] = {(0,1), (0,0), (1,1), (1,0), (1,0), (0,0), (0,0), (0,0), (1,0), (1,0), (1,0), (0,1), (1,0), (1,0), (0,1), (1,1), (1,0), (0,0), (1,0), (1,1), (1,0), (0,0), (0,0), (1,0), (1,1), (0,1), (1,0), (1,1), (1,1), (0,0), (0,1), (0,1), (1,0), (1,1), (0,0), (1,0), (1,1), (0,0), (0,1), (1,1), (1,1), (1,0), (0,1), (0,0), (0,0), (1,1), (0,1), (0,0), (1,0), (1,1), (1,1), (1,0), (0,0), (1,1), (1,0), (0,1), (0,1), (0,1), (0,1), (0,1), (0,1), (0,1), (0,0), (0,0), (0,0), (0,0), (0,1), (1,1), (0,0), (0,0), (0,1), (0,1), (0,1), (0,0), (0,0), (1,1), (0,0), (0,1), (1,1), (1,1), (1,0), (0,1), (0,0), (1,0), (0,0), (0,0), (0,0), (0,0), (0,0), (1,1), (0,1), (0,0), (0,0), (1,1), (1,1), (1,0), (1,0), (1,1), (0,1), (0,0), (1,1), (0,1), (0,1), (1,1), (0,1), (1,1), (1,1), (1,1), (0,0), (0,1), (1,1), (0,1), (1,1), (0,0), (0,0), (0,0), (0,1), (0,0), (0,0), (0,1), (0,1), (1,0), (1,1), (0,1), (1,1), (1,1), (0,0), (0,0), (0,0)} + +190 Rec. ITU-T G.9960 (06/2023) + +The $\text{const\_scrambler\_sequence}[i] = (s1,s2)$ denotes the LFSR output for the subcarrier index $8(i-1)$ (clause 7.1.4.3.3). That is, $\text{const\_scrambler\_sequence}[1] = (0,1)$ corresponds to the subcarrier index 0, $\text{const\_scrambler\_sequence}[2] = (0,0)$ to the subcarrier index 8, etc. + +### G.6.2 Preamble generation test vector 2 + +Using the test vector from clause G.6.1, the normalized constellation scrambler output corresponding to the first section of the preamble assuming 25 MHz-PB OFB shall be: + +$\text{pre\_cscram\_output}[1:128] = \{0, 0, 0, 0, 0, 0, 0, 0, 0, 0, j, -1, j, j, -1, -j, j, 1, j, -j, j, 1, 1, j, -j, -1, j, -j, -j, 1, -1, -1, j, -j, 1, j, -j, 1, -1, -j, j, -1, 1, 1, -j, -1, 1, j, -j, -j, j, 1, -j, j, -1, -1, -1, -1, -1, -1, 1, 1, 1, 1, -1, -j, 1, 1, -1, -1, -1, 1, 1, -j, 1, -1, -j, -j, j, -1, 1, j, 1, 1, 1, 1, 1, -j, -1, 1, 1, -j, -j, j, j, -j, -1, 1, -j, -1, -1, -j, -1, -j, -j, -j, 1, -1, -j, -1, -j, 1, 1, 1, -1, 1, 1, -1, -1, j, -j, -1, -j, -j, 1, 1, 1\}$ + +The first non-zero output $\text{pre\_cscram\_output}[11] = j$ corresponds to the subcarrier index 80, $\text{pre\_cscram\_output}[12] = -1$ corresponds to the subcarrier index 88, etc. The PMSC set is given in clause 7.2.2.4. No RMS set is assumed. + +## **Annex H** + +### **Test vectors (HCH-PHY layer)** + +(This annex forms an integral part of this Recommendation.) + +(This annex is only valid when using the HCH-PHY layer described in clause 10.) + +This annex is for further study. + +## **Annex I** + +(This annex has been intentionally left blank.) + +## Annex J + +### Interoperability between Profile 1 and Profile 2 OFB transmissions + +(This annex forms an integral part of this Recommendation.) + +G.hn nodes implementing the HCH-PHY layer implemented in clause 10 may coexist in the same domain than nodes implementing the PHY layer described in clause 7 provided that the operating frequencies defined for the domain are consistent. + +The domain master of a G.hn domain shall ensure that each node in the network: + +- Transmits to its peers using the appropriate physical layer. +- Has enough information to determine which physical layer to use in every transmission + +The mechanisms for distributing this information are described in clause 8.18.3 of [ITU-T G.9961] + +#### J.1 Rules for selection of transmission mode + +A G.hn node shall determine before a transmission which physical layer (PHY, clause 7 or HCH-PHY, clause 10) it shall use. Once determined, the transmitting node shall always use this mode of transmission for the communications with the receiving nodes. The rules for determining the transmission mode are defined in [ITU-T G.9961] as shown in Table J.1: + +**Table J.1 – Transmission rules for interoperability** + +| Transmission type | [ITU-T G.9961] reference | +|-----------------------|-------------------------------------| +| MAP-D Transmission | See clause 8.18.4 of [ITU-T G.9961] | +| MAP-A Transmission | See clause 8.18.4 of [ITU-T G.9961] | +| Transmission in RCM | See clause 8.18.5 of [ITU-T G.9961] | +| Run-time transmission | See clause 8.18.5 of [ITU-T G.9961] | + +#### J.2 Rules for scheduling generation + +The DM of a domain where G.hn nodes with clauses 7 and 10 physical layer capabilities (or that accepts such a combination for registering nodes) shall comply with additional restrictions when building the scheduling of the domain, as presented in the following clauses. + +##### J.2.1 TXOP restrictions + +Profile 1 OFBs (clause 7) and Profile 2 OFBs (clause 10) shall not coexist within the same TXOP. The DM shall indicate in the field ALLOWED\_OFB of the TXOP descriptor (see clause 8.8.4) the OFB profile that the transmitter node may use during this transmission opportunity. + +A TXOP descriptor that does not indicate the OFBs that are allowed in this TXOP is considered to allow only Profile 1 OFBs. + +NOTE – The DM of a domain should schedule enough TXOPs for both types of OFBs to guarantee a fair access to the channel for all the nodes of the domain. + +## **Annex K to Annex Q** + +(Annex K to Annex Q have been intentionally left blank.) + +# Annex R + +## Use of reverse power feeding techniques for G.hn over coaxial media + +(This annex forms an integral part of this Recommendation.) + +### R.1 Scope + +This annex addresses reverse power feeding (RPF) over point-to-point coaxial links. + +NOTE – Extension to point-to-multipoint is for further study. + +One G.hn use case is the separation of the network termination and gateway through a high speed coaxial backhaul to allow the operator to position these elements in their optimal locations: + +- The network termination, near the entry point of the premises may be a good place to locate the WAN termination. +- The gateway should be located to optimize the Wi-Fi coverage. Normally this is done by placing the gateway in the living room. + +Whilst the gateway equipment is normally located in a position where it is easily powered, the network termination equipment may be in a location with difficult access to the electrical network due to the lack of sockets. (e.g., the equipment may be located outside the house to facilitate installation). In these cases, the use of RPF techniques may facilitate the installation and maintenance of this equipment by the service provider. + +The use of RPF allows the network termination to get the electrical power from the gateway equipment in the premises over the coaxial network. + +A reference model of such deployment is shown in Figure R.1. + +![Figure R.1 – Reference model for a RPF installation](709d81964e33e85c1e1f9edb30d395fd_img.jpg) + +``` +graph LR + subgraph WAN + A[Access technology xDSL, FO] --> NT[Network termination] + end + subgraph LAN + NT -- Coax P2P Coax extension --- GW[GW] + GW -- RFP Power ---> NT + GW -- LAN connectivity WiFi, powerline --- EUD[End user device] + end +``` + +The diagram shows a network architecture where a 'Network termination' box receives a WAN signal via access technology (xDSL, FO). It is connected to a 'GW' (Gateway) box via a 'Coax P2P' link (Coax extension). Power is fed back from the 'GW' to the 'Network termination' via 'RFP' (Reverse Power Feeding). The 'GW' then connects to an 'End user device' via LAN connectivity (WiFi, powerline). + +Figure R.1 – Reference model for a RPF installation + +**Figure R.1 – Reference model for a RPF installation** + +### R.2 References + +- [[ITU-T G.997.2](#)] ITU-T G.997.2(2019), *Physical layer management for G.fast transceivers*. +- [[IEEE 802.3bt](#)] IEEE 802.3bt-2018, *IEEE Standard for Ethernet Amendment 2: Physical Layer and Management Parameters for Power over Ethernet over 4 pairs*. +- [[TS-101 548-1](#)] ETSI TS-101 548-1, *Access, Terminals, Transmission and Multiplexing (ATTM); European Requirements for Reverse Powering of Remote Access Equipment*. + +### R.3 Definitions + +**R.3.1 PD node:** In this context, a G.hn node connected to a Powered Device for management purposes. + +**R.3.2 PSE node:** In this context, a G.hn node connected to a power sourcing equipment for management purposes. + +#### **R.4 Abbreviations and acronyms** + +| | | +|------|-----------------------------| +| ACM | Alternating Current Mains | +| BAT | Battery | +| BBA | Battery Back-up Available | +| CC | Core Conductor | +| DGL | Dying Gasp Loss | +| ELC | Error Line Condition | +| OAM | Operation And Maintenance | +| OSC | Outer Shield Conductor | +| PD | Powered Device | +| PoE | Power over Ethernet | +| POTS | Plain Old Telephone Service | +| PS | Power Splitter | +| PSE | Power Sourcing Equipment | +| PSU | Power Supply Unit | +| RPF | Reverse Power Feeding | +| WAN | Wide Area Network | + +#### **R.5 Reference architecture** + +In an RPF installation, the coaxial cable can convey at the same time several types of signals: + +- Electrical power, generated by an equipment including at least a G.hn interface and consumed by a network termination that also includes a G.hn interface. +- G.hn Data signal, transmitted over the coaxial cable between the G.hn interfaces in both sides of the communication path (e.g., network termination and gateway). +- Overlay data signal, generated by a non-G.hn network over a different spectrum but transmitted on the same physical coaxial media. + +This leads to several types of deployment architecture may be deployed as seen in Figure R.2 and Figure R.3 + +Figure R.2 shows a reference architecture where the coaxial cable is solely used for G.hn signal distribution in a point to point scenario. + +![Figure R.2: Reference architecture – Only G.hn service. This diagram shows two main components connected by a coaxial cable. On the left is the 'Network termination (PD device)', which contains a 'G.hn interface', an 'Access interface', and 'Additional functions'. It also includes a 'PS' (Power Splitter) and a 'PSU' (Power Supply Unit). The 'G.hn interface' is connected to the 'PS' via a dashed line (G.hn signal). The 'Access interface' and 'Additional functions' are connected to the 'PSU' via solid green lines (Power). The 'PS' is connected to the 'PSU' via a solid green line (Power). On the right is the 'GW (PSE device)', which contains a 'PS', a 'PSE', and 'Additional functions'. The 'PS' is connected to the 'PSE' via a solid green line (Power). The 'PSE' is connected to the 'G.hn interface' and 'Home area network interface' via solid green lines (Power). The 'G.hn interface' is connected to the 'PS' via a dashed line (G.hn signal). The 'PS' is connected to the 'Coax' cable via a solid blue line. The 'Coax' cable is connected to the 'Network termination' via a solid blue line. A legend at the bottom indicates: Power (solid green line), G.hn signal (dashed black line), Coax (solid blue line), and Access technology (xDSL, FO) (solid red line). The text 'G.9960(18)-Cor.2(20)_FR.2' is in the bottom right corner.](61887c08b198861558621bc776880d6d_img.jpg) + +Figure R.2: Reference architecture – Only G.hn service. This diagram shows two main components connected by a coaxial cable. On the left is the 'Network termination (PD device)', which contains a 'G.hn interface', an 'Access interface', and 'Additional functions'. It also includes a 'PS' (Power Splitter) and a 'PSU' (Power Supply Unit). The 'G.hn interface' is connected to the 'PS' via a dashed line (G.hn signal). The 'Access interface' and 'Additional functions' are connected to the 'PSU' via solid green lines (Power). The 'PS' is connected to the 'PSU' via a solid green line (Power). On the right is the 'GW (PSE device)', which contains a 'PS', a 'PSE', and 'Additional functions'. The 'PS' is connected to the 'PSE' via a solid green line (Power). The 'PSE' is connected to the 'G.hn interface' and 'Home area network interface' via solid green lines (Power). The 'G.hn interface' is connected to the 'PS' via a dashed line (G.hn signal). The 'PS' is connected to the 'Coax' cable via a solid blue line. The 'Coax' cable is connected to the 'Network termination' via a solid blue line. A legend at the bottom indicates: Power (solid green line), G.hn signal (dashed black line), Coax (solid blue line), and Access technology (xDSL, FO) (solid red line). The text 'G.9960(18)-Cor.2(20)\_FR.2' is in the bottom right corner. + +**Figure R.2 – Reference architecture – Only G.hn service** + +A power source equipment (PSE) included in an end user equipment is powered locally. This PSE feeds with electrical power the coaxial cable through a Power Splitter (PS) that combines G.hn signal and the electrical supply. + +On the network termination side, another PS divides the incoming signal between the G.hn signal that is directed to the G.hn interface, and the electrical power that arrives to the local power supply unit (PSU) that powers the different elements composing the network termination. + +Figure R.3 shows a reference architecture where the coaxial cable is shared with non-G.hn networks. + +![Figure R.3: Reference architecture – G.hn service coexistence with satellite. This diagram shows a more complex setup. On the far left is the 'Network termination' (PD device), identical to Figure R.2. It is connected to a 'Diplexer' via a coaxial cable (solid blue line). Above the first 'Diplexer' is a 'SAT' (Satellite) unit, also connected to it via a coaxial cable. The first 'Diplexer' is connected to a second 'Diplexer' via a coaxial cable. Above the second 'Diplexer' is an 'STB' (Set-Top Box) unit, also connected to it via a coaxial cable. The second 'Diplexer' is connected to the 'GW (PSE device)' via a coaxial cable. The 'GW (PSE device)' is identical to Figure R.2. A legend at the bottom indicates: Power (solid green line), G.hn signal (dashed black line), Coax (solid blue line), and Access technology (xDSL, FO) (solid red line). The text 'G.9960(18)-Cor.2(20)_FR.3' is in the bottom right corner.](0348dd87efbccba766e98138b073b499_img.jpg) + +Figure R.3: Reference architecture – G.hn service coexistence with satellite. This diagram shows a more complex setup. On the far left is the 'Network termination' (PD device), identical to Figure R.2. It is connected to a 'Diplexer' via a coaxial cable (solid blue line). Above the first 'Diplexer' is a 'SAT' (Satellite) unit, also connected to it via a coaxial cable. The first 'Diplexer' is connected to a second 'Diplexer' via a coaxial cable. Above the second 'Diplexer' is an 'STB' (Set-Top Box) unit, also connected to it via a coaxial cable. The second 'Diplexer' is connected to the 'GW (PSE device)' via a coaxial cable. The 'GW (PSE device)' is identical to Figure R.2. A legend at the bottom indicates: Power (solid green line), G.hn signal (dashed black line), Coax (solid blue line), and Access technology (xDSL, FO) (solid red line). The text 'G.9960(18)-Cor.2(20)\_FR.3' is in the bottom right corner. + +**Figure R.3 – Reference architecture – G.hn service coexistence with satellite** + +In this case, the functionality is similar to the previous case. The main difference is the presence of diplexers between the two entities that allow to inject/extract non-G.hn signals operating in a different spectrum (e.g., satellite) into/from the coaxial line. + +## R.6 Implementation of RPF + +### R.6.1 Introduction + +A G.hn-compliant RPF framework is composed of two main processes: + +- **Power feed:** The process through which a power supply equipment (PSE) device feeds with power a powered device (PD). +- **RPF management protocol:** Implementation of a management channel between the PSE device and the PD device through a G.hn management channel. + +### R.6.2 Power feed + +RPF over G.hn is aimed to support several processes for conveying the power from the equipment including the PSE and the equipment including the PSU. + +This process shall use: + +- **PoE-based electrical feed:** The electrical feed of the PD may be done using power over Ethernet (PoE) (see clause R.6.2.1) + +The use of other electrical feed protocols is for further study. + +The PSE device shall be able to power a single PD device in both mains-powered and battery-powered (when available) operation. + +#### R.6.2.1 Power feed through PoE + +The power feed through PoE shall follow the standard [IEEE 802.3bt]. Both PSE device and PD device shall implement type 3 implementation. + +## R.6.3 RPF management protocol + +### R.6.3.1 Protocol description + +The RPF management protocol allows to the PD device to manage the PSE device through the exchange between NMEs of G.hn management messages through the L3 interface (see Figure 6-2 of [ITU-T G.9962]). The information conveyed may be exposed to the application layers through the L1 management interface. Figure R.4 shows the RPF management over G.hn management channel. + +![Diagram illustrating RPF management over G.hn management channel. It shows two parallel stacks of layers. The left stack represents the PD device, with layers from top to bottom: AE (manages PSU), NME, DLL, and PHY. The right stack represents the PSE device, with layers from top to bottom: AE (manages PSE), NME, DLL, and PHY. A dashed horizontal line separates the AE layer from the NME layer in both stacks. Vertical double-headed arrows labeled L1 connect the AE layer to the NME layer in each stack. Vertical double-headed arrows labeled L4 connect the NME layer to the DLL layer in each stack. A horizontal double-headed arrow labeled L3 connects the NME layer of the PD device to the NME layer of the PSE device. At the bottom right of the diagram, the text 'G.9960(18)-Cor.2(20)_FR.4' is present.](fc70bf3c1fbbe560de4704cb2b4182b1_img.jpg) + +G.9960(18)-Cor.2(20)\_FR.4 + +Diagram illustrating RPF management over G.hn management channel. It shows two parallel stacks of layers. The left stack represents the PD device, with layers from top to bottom: AE (manages PSU), NME, DLL, and PHY. The right stack represents the PSE device, with layers from top to bottom: AE (manages PSE), NME, DLL, and PHY. A dashed horizontal line separates the AE layer from the NME layer in both stacks. Vertical double-headed arrows labeled L1 connect the AE layer to the NME layer in each stack. Vertical double-headed arrows labeled L4 connect the NME layer to the DLL layer in each stack. A horizontal double-headed arrow labeled L3 connects the NME layer of the PD device to the NME layer of the PSE device. At the bottom right of the diagram, the text 'G.9960(18)-Cor.2(20)\_FR.4' is present. + +**Figure R.4 – RPF management over G.hn management channel** + +The RPF management protocol is mapped into the following G.hn management messages: + +- **RPF\_OAMEventNotification.ind:** Management message used by the PSE node to alert a PD node of RPF events. + +- RPF\_OAMParameter.req: Management message used to request one or more RPF parameters +- RPF\_OAMParameter.cnf: Management message used to return one or more RPF parameters. + +Figure R.5 shows RPF management messages. + +![](f4aaee6522d9ab40472939a4a178e5a3_img.jpg) + +``` + +sequenceDiagram + participant PD as PD node + participant PSE as PSE node + PD->>PSE: RPF_Parameter.req + PSE->>PD: RPF_Parameter.cnf + PSE->>PD: RPF_OAMEventNotification.ind + +``` + +G.9960(18)-Cor.2(20)\_FR.5 + +**Figure R.5 – RPF management messages** + +#### R.6.3.1.1 Dying gasp + +The PSE node shall send a dying gasp indication to the PD after it has lost both mains and battery power (if available) and before it removes power from the line. + +The PSE shall provide the RPF dying gasp and indication primitives DGL, BAT, ACM and BBA defined in clause 6.3 of [TS-101 548-1]. + +The RPF dying gasp and indication primitives shall be sent to the PD node by using the RPF management protocol (see clause R.6.3). + +#### R.6.3.1.2 Error conditions + +The PSE shall comply with the requirements for start-up procedure described in [ETSI 101 548-1] with the following amendments: + +- Excluding the error conditions related to POTS exchange and phone error conditions. +- Redefining ELC0 to ELC2 as shown in Figure R.6 and Table R.1 +- ELC3 is not considered + +![Figure R.6 – Error conditions. A schematic diagram showing the connection between a Network termination (PD device) and a GW (PSE device). The PD device contains a G.hn interface and a PS (Power Source) block. The PSE device also contains a PS and a G.hn interface. Between them are two lines: CC and OSC. Three error line conditions (ELC) are illustrated: ELC2 voltage U_DC (represented as a voltage source in series with the OSC line), ELC1 short (represented as a resistor shorting CC and OSC), and ELC0 open (represented as an open switch on the OSC line). A resistance R_cc-osc is also indicated between the lines at the PSE side. The diagram is labeled G.9960(18)-Cor.2(20)_FR.6.](643e8a3c198571617894ece3f1c2e72d_img.jpg) + +Figure R.6 – Error conditions. A schematic diagram showing the connection between a Network termination (PD device) and a GW (PSE device). The PD device contains a G.hn interface and a PS (Power Source) block. The PSE device also contains a PS and a G.hn interface. Between them are two lines: CC and OSC. Three error line conditions (ELC) are illustrated: ELC2 voltage U\_DC (represented as a voltage source in series with the OSC line), ELC1 short (represented as a resistor shorting CC and OSC), and ELC0 open (represented as an open switch on the OSC line). A resistance R\_cc-osc is also indicated between the lines at the PSE side. The diagram is labeled G.9960(18)-Cor.2(20)\_FR.6. + +**Figure R.6 – Error conditions** + +**Table R.1 – Error line condition parameters and detection criteria** + +| Error line condition | Description | Parameter | Detection criteria | +|----------------------|--------------------|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| ELC 0 | Open
CC to OSC | $R_{Emin} = 1 \text{ M}\Omega$
$C_{Emax} = 100 \text{ nF}$ | $R_{cc-osc} \geq R_{Emin}$ for a duration exceeding 300ms (see note)
$C_{cc-osc} \leq C_{Emax}$ | +| ELC 1 | Short
CC to OSC | $R_{Emax} = 140 \Omega$ | $R_{cc-osc} \leq R_{Emax}$ | +| ELC 2 | Foreign DC voltage | $U_{cc-oscDCEmax} = 3 \text{ V}$ | $ U_{cc-oscDC} \geq U_{cc-oscDCEmax}$ | + +### R.6.3.2 Format of management messages for RPF + +#### R.6.3.2.1 Format of RPF\_OAMEventNotification.ind + +The message RPF\_OAMEventNotification.ind shall include the following TLVs: + +- One RPF\_PSE\_PD\_FlagsTLV TLV + +#### R.6.3.2.2 Format of RPF\_OAMParameter.req + +The message RPF\_OAMParameter.req shall include the following TLVs: + +- One RPF\_PD\_PSE\_FlagsTLV TLV +- One RPF\_ParameterRequestTLV + +#### R.6.3.2.3 Format of RPF\_OAMParameter.cnf + +The message RPF\_OAMParameter.cnf shall include the following TLVs: + +- One RPF\_PSE\_PD\_FlagsTLV TLV + +### R.6.3.3 TLV pool for RPF + +This annex defines the TLVs listed in Table R.2: + +**Table R.2 – List of TLVs for RPF** + +| TLV type | TLV name | Value field for the TLV | +|------------------|-------------------------|-------------------------| +| 08 16 | RPF_PD_PSE_FlagsTLV | See Table R.3 | +| 09 16 | RPF_PSE_PD_FlagsTLV | See Table R.4 | +| 0A 16 | RPF_ParameterRequestTLV | See Table R.6 | + +#### R.6.3.3.1 TLV value fields + +##### R.6.3.3.1.1 RPF\_PD\_PSE\_FlagsTLV TLV + +Table R.3 shows the format of the RPF\_PD\_PSE\_FlagsTLV field. + +**Table R.3 – Format of the RPF\_PD\_PSE\_FlagsTLV field** + +| Field | Octet | Bits | Description | +|-------------------------------------------------------------------------------------------------------------|-------|--------|--------------------------| +| Flags | 0-1 | [15:0] | 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. | | | | + +##### R.6.3.3.1.2 RPF\_PSE\_PD\_FlagsTLV TLV + +Table R.4 shows the format of the RPF\_PSE\_PD\_FlagsTLV field, and Table R.5 shows the RPF OAM flags field as sent by the PSE node. + +**Table R.4 – Format of the RPF\_PSE\_PD\_FlagsTLV field** + +| Field | Octet | Bits | Description | +|----------------------------------------------------------------------------------------------------------------------------|-------|--------|-------------------------------------| +| Flags | 0-1 | [15:0] | RPF OAM flags (Note). See Table R.5 | +| NOTE – The RPF OAM flag fields in Table R.3 are consistent with the indications defined in clause 6.3 of [ETSI TS 101 548] | | | | + +**Table R.5 – RPF OAM flags field as sent by the PSE node** + +| Bit(s) | Name | Description | +|--------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| 15-5 | Reserved | Reserved for use by ITU-T (Note) | +| 4 | PSE-DGL (dying gasp loss) | Set to ONE for indication of a PSE lost power dying gasp.
Set to ZERO otherwise. | +| 3 | Reserved | Reserved for use by ITU-T (Note) | +| 2 | PSE-BAT | Set to ONE for indication of a PSE operation on a battery.
Set to ZERO otherwise. | +| 1 | PSE-ACM (AC mains) | Set to ONE for indication of a PSE operation on mains power with no battery backup (BBA) available.
Set to ZERO otherwise. | +| 0 | PSE-BBA | Set to ONE for indication of a PSE operating on mains power with BBA.
Set to ZERO otherwise. | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +**R.6.3.3.1.3 RPF\_ParameterRequestTLV** + +Table R.6 shows the format of the RPF\_ParameterRequestTLV field. + +**Table R.6 – Format of the RPF\_ParameterRequestTLV field** + +| Field | Octet | Bits | Description | +|------------------------|--------------|--------|---------------------------------------------------------| +| Number of ParameterIds | 0 | [7:0] | Number of parameters (P) to be queried in this request | +| ParameterID[0] | 1 to 3 | [23:0] | First parameter to be queried (see Table R.7) | +| ... | ... | | | +| ParameterID[P-1] | (3P-2) to 3P | [23:0] | P th parameter to be queried (see Table R.7) | + +Table R.7 lists RPF OAM parameters: + +**Table R.7 – List of RPF OAM parameters** + +| Field | Octet | Bits | Description | +|-------------|---------|--------|-------------------------------------| +| LeafParam | 0 and 1 | [15:0] | Leaf Parameter ID (see Table R.8) | +| BranchParam | 2 | [7:0] | Branch Parameter ID (see Table R.8) | + +Table R.8 lists RPF OAM parameters. + +**Table R.8 – List of RPF OAM parameters** + +| Name | Branch param | Leaf param | Width | Description | +|--------------------------------------------|--------------------------------------|--------------------|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserved | 00 16 to 03 16 | Reserved | N/A | Reserved by ITU-T | +| Status | | | | | +| RPF-IFN
(intensity of current feed now) | 04 16 | 0001 16 | 02 16 | Average current feed now at the interface between PS and PSE, expressed in mA, and represented as a 16 bit unsigned integer with valid values 0 to 400 mA. The averaging time window and accuracy are defined are defined in [ETSI TS 101 548]. | +| Diagnostics | | | | | +| PSE-SUF | 05 16 | 0001 16 | 01 16 | Latest PSE Start-Up Failure indication, detected during "Start-Up". The octet is formatted as a bitmap, with a bit set to ONE if and only if the corresponding failure is detected. The bits are defined as follows (bit 0 lsb to bit 7 msb):
bit 0: ELC-0 (Open tip-to-ring);
bit 1: ELC-1 (Short tip-to-ring);
bit 2: ELC-2 (POTS Exchange (foreign) DC voltage)
bit 3: Reserved by ITU-T (Note 3)
bit 4: Reserved by ITU-T (Note 3);
bit 5: Unknown;
bit 6: Reserved by ITU-T (Note 3);
bit 7: Reserved by ITU-T (Note 3).
No more than 1 bit shall be set to ONE in the field. | +| PSE-SDC | 05 16 | 0002 16 | 01 16 | Latest PSE Shutdown Cause indication, detected during "Normal Operation". The octet is formatted as a bitmap, with a bit set to ONE if and only if the corresponding cause applies. The bits are defined as follows (bit 0 lsb to bit 7 msb):
bit 0: ELC-0 (Open tip-to-ring);
bit 1: ELC-1 (Short tip-to-ring);
bit 2: ELC-3 (Off-hook phone);
bit 3: Overload time violation (Note 1);
bit 4: Maintain power signature violation (Note 2);
bit 5: Unknown;
bit 6: Reserved by ITU-T (Note 3);
bit 7: Reserved by ITU-T (Note 3).
No more than 1 bit shall be set to ONE in the field. | +| PSE-IE | 05 16 | 0003 16 | 02 16 | Injected energy by the PSE at the interface between PS and PSE, while PSE is in the "Normal Operations" state, expressed in units of mWh and represented as a 16-bit unsigned integer. Valid values range from 0mWh to 65535 mWh. The value shall wrap on overflow. The accuracy is defined in [ETSI TS 101 548]. | +| Inventory | | | | | +| NTE-CPF
(network termination) | 06 16 | 0001 16 | 01 16 | 00 16 : PSE in physical entity separate from NT (not integrated). | + +**Table R.8 – List of RPF OAM parameters** + +| Name | Branch param | Leaf param | Width | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------|------------------|---------------------------------------------------------------------------------------------------------------------| +| equipment - common power feed) | | | | 01 16 : PSE in same physical entity with NT (integrated).
Other values are reserved for use by ITU-T. | +| Reserved | 07 16 to 9F 16 | Reserved | N/A | Reserved by ITU-T | +| Feeding | | | | | +| RPF type | A0 16 | 0000 16 | 01 16 | Type of RPF being used
01 16 : PoE-based RPF
Other values are reserved for use by ITU-T. | +| Reserved | A1 16 to FF 16 | Reserved | N/A | Reserved by ITU-T | +| NOTE 1 – Overload time is defined in Table 35 of [ETSI TS 101 548].
NOTE 2 – Maintain power signature is defined in Table 37 of [ETSI TS 101 548].
NOTE 3 – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. | | | | | + +## Appendix I + +### Examples of home network topologies + +(This appendix does not form an integral part of this Recommendation.) + +An example of a home network containing a single domain is shown in Figure I.1 where a single domain master coordinates nodes of the domain (i.e., assigns bandwidth resources and priority). In this example, the domain is bridged to the access network via node D (it is also a domain master) that is assumed to be part of the residential gateway. In PM, nodes A, B, C and D communicate directly with each other. In CM, one of the nodes is assigned as DAP (node D in this example), and all nodes can communicate with each other only via this node. In UM, each of the nodes A-D can communicate directly with each other or indirectly, via other nodes operating as relay nodes. In this example, node D (domain master) serves as a relay node, while other nodes use either P2P or node D as a relay if required. + +While in either PM, CM or UM, nodes A-D can transmit under limitation of bandwidth resources and priorities assigned by the domain master. + +![Diagram of a home network containing a single domain. A blue rectangular area labeled 'Domain' contains a horizontal black line labeled 'Medium'. Four orange rectangular nodes are connected to this medium: 'Domain master and relay node (Node D)' on the left, 'Node A' in the center-left, 'Node B' in the center-right, and 'Node C' on the right. Node D is connected to a green rectangular box labeled 'Bridge to access network'. This bridge is connected to an 'Access network' via a double-headed vertical arrow. The text 'G.9960(15)_FI.1' is in the bottom right corner of the diagram area.](c13dfef1bb16b40f3ee1955ea9a7bdbc_img.jpg) + +Diagram of a home network containing a single domain. A blue rectangular area labeled 'Domain' contains a horizontal black line labeled 'Medium'. Four orange rectangular nodes are connected to this medium: 'Domain master and relay node (Node D)' on the left, 'Node A' in the center-left, 'Node B' in the center-right, and 'Node C' on the right. Node D is connected to a green rectangular box labeled 'Bridge to access network'. This bridge is connected to an 'Access network' via a double-headed vertical arrow. The text 'G.9960(15)\_FI.1' is in the bottom right corner of the diagram area. + +**Figure I.1 – Example of a home network containing a single domain** + +An example of a home network containing a single domain that operates in UM using both P2P and REL is depicted in Figure I.2. The subset of nodes that use REL includes nodes B, C, D and F, where node D operates as a relay node for this group of nodes. All other nodes can communicate directly (i.e., using P2P) or via a relay node (i.e., using REL). A single domain master (in this case node A) coordinates the nodes of the domain. The domain is bridged to the access network via node A, which is assumed to be part of the residential gateway. While using either P2P or REL, nodes A to G can transmit under the limitation of bandwidth resources and priorities assigned by the domain master. Frames from nodes B, C and F addressed to nodes outside the domain are sent to node A via relay node D; node A is connected to the inter-domain bridge. Frames from nodes D, E and G addressed to nodes outside the domain are sent to node A directly. + +![Diagram of a single domain home network (Figure I.2).](6726e50ea08adfda77603ec4afa549e1_img.jpg) + +This diagram illustrates a single domain home network. A blue rectangular area labeled 'Domain' contains a horizontal black line labeled 'Medium'. Above the medium are three nodes: Node E (yellow), Node F (orange), and Node G (yellow). Below the medium are three nodes: Domain master (Node A) (purple), Relay node (Node D) (grey), and Node B (orange). To the left, a green box labeled 'Bridge to access network' is connected to the medium via a double-headed arrow labeled 'Access network'. Below the domain box, three colored boxes represent operational modes: 'CTR and PP' (purple), 'CTR' (orange), and 'PP' (yellow). The text 'G.9960(15)\_FI.2' is in the bottom right corner. + +Diagram of a single domain home network (Figure I.2). + +**Figure I.2 – Example of a home network containing a single domain operating in UM (using a combination of P2P and REL)** + +An example of a home network containing three domains with corresponding domain masters established on two different media is depicted in Figure I.3. Nodes of domain 1 and of domain 3 operate over the same medium (medium 1). In this example, it is assumed that domain 1 and domain 3 operate in different spectral bands. Those two domains are bridged via an inter-domain bridge (on layer 2 or layer 3). Domain 2 operates on a different medium (denoted as medium 2). Domains 1 and 2 are bridged to the access network. In Figure I.3 it is assumed that the domain master of domain 2 and node A of domain 1 are parts of the residential gateway. Domains 1 and 3 are connected by an inter-domain bridge. Each of the three domains can operate in either PM, UM or CM, independently of the operational mode used by other domains. + +![Diagram of a home network with three domains (Figure I.3).](9f5f9afcedaa0d9b7991976f5000865c_img.jpg) + +This diagram shows a home network with three domains. A green box on the left labeled 'Bridge to access network' is connected to an 'Access network' via a double-headed arrow. Domain 1 (orange background) contains Node A (blue), Domain master Node D (light blue), and Node B (blue) connected to 'Medium 1' (black line). Domain 2 (red background) contains Domain master Node B (yellow), Node A (yellow), and Node C (yellow) connected to 'Medium 2' (black line). Domain 3 (blue background) contains Domain master Node D (orange), Node A (orange), and Node B (orange) connected to 'Medium 1' (black line). An 'Inter-domain bridge' (green box) connects Medium 1 and Medium 2. Node C (blue) is connected to the inter-domain bridge, and Node C (orange) is connected to the inter-domain bridge. The text 'G.9960(15)\_FI.3' is in the bottom right corner. + +Diagram of a home network with three domains (Figure I.3). + +**Figure I.3 – Example of a home network comprising three domains** + +An example of a home network connected to an alien domain is shown in Figure I.4. The example shows a home network containing two domains (domains 1 and 2) with corresponding domain masters established on two different media, bridged via an inter-domain bridge (layer 2 or layer 3) to the alien domain. The alien domain is established on the same medium as domain 1. Nodes of domain 1 and of domain 2 in Figure I.4 operate over different media, while nodes A1-A3, which are alien nodes, share the same medium with domain 1. The domain master of domain 1 considers the alien domain as another AE connected to the corresponding node of domain 1. Operation of this alien domain and its interconnection with an ITU-T G.9960 home network is outside of the scope of this Recommendation. + +In this example, node A of domain 1 is bridged to the access network. This bridge is usually a part of the residential gateway. + +![Diagram of an ITU-T G.9960 network architecture showing two domains (Domain 1 and Domain 2) sharing a common medium (Medium 1) with an alien domain. Domain 1 includes nodes A, B, C, D (Domain master), and E. Domain 2 includes nodes A (Domain master), B, C, and E. The alien domain includes nodes A1, A2, and A3. Bridges connect Domain 1 to the access network and to the alien domain. The diagram is labeled G.9960(15) FI.4.](d5439b040187c5a1e89ad438ef535141_img.jpg) + +The diagram illustrates a network architecture with the following components and connections: + +- Access network:** Located at the top left, connected to Node A via a "Bridge to the access network". +- Alien domain:** A blue-shaded area at the top containing Node A1, Node A2, and Node A3. Node A1 and A2 are connected to "Medium 1". Node A3 is connected to a "Bridge to alien domain". +- ITU-T G.9960 domain 1:** An orange-shaded area containing Node A, Domain master (Node D), Node B, and Node C. Node A is connected to the "Bridge to the access network". Node D and Node B are connected to "Medium 1". Node C is connected to the "Bridge to alien domain". +- ITU-T G.9960 domain 2:** A red-shaded area at the bottom containing Domain master Node A, Node B, Node C, and Node E. Domain master Node A and Node B are connected to "Medium 2". Node C and Node E are connected to an "Inter-domain bridge". +- Mediums:** + - Medium 1:** A horizontal line connecting Node A1, A2, D, B, and the "Bridge to alien domain". + - Medium 2:** A horizontal line connecting Domain master Node A and Node B. +- Bridges:** + - Bridge to the access network:** Connects Node A (Domain 1) to the external access network. + - Bridge to alien domain:** Connects Node A3 (Alien domain) and Node C (Domain 1) to the alien domain. + - Inter-domain bridge:** Connects Node C and Node E (Domain 2) to the rest of the network. + +G.9960(15) FI.4 + +Diagram of an ITU-T G.9960 network architecture showing two domains (Domain 1 and Domain 2) sharing a common medium (Medium 1) with an alien domain. Domain 1 includes nodes A, B, C, D (Domain master), and E. Domain 2 includes nodes A (Domain master), B, C, and E. The alien domain includes nodes A1, A2, and A3. Bridges connect Domain 1 to the access network and to the alien domain. The diagram is labeled G.9960(15) FI.4. + +**Figure I.4 – Example of an ITU-T G.9960 domain sharing a medium with an alien domain** + +An example of a home network associated with residential broadband access is presented in Figure I.5. In the example, the home network includes three domains established over coax, telephone and power-line wiring. Alien domains are established by the residential gateway and may include WLAN IEEE 802.11, USB2, and IEEE 802.3 (Ethernet). The RG serves as a bridge allowing communication with alien domains (e.g., 802.11) and with an access network (e.g., PON or DSL). + +Each node in Figure I.5 is configured for the medium it is connected to. It can communicate with any other node of the same domain using either P2P or REL. Communication between nodes of different domains (e.g., between coax and telephone line in Figure I.5) is via inter-domain bridges or via the RG. Communication with alien nodes and with the access network is via bridges, which are a part of the RG. + +![Diagram of a home network architecture showing a Residential gateway connected to an Access network, an Ethernet switch, and various client devices via Coax, Power line, and Phone line connections.](eda1a0f033926f48febc095bce470c58_img.jpg) + +The diagram illustrates a home network architecture. At the top, an **Access network** is connected to a **Residential gateway**. The gateway contains a **DSL/PON port (access network)**. Below the gateway is an **Ethernet switch**. The switch has several ports: **Wm 1 port (master coax)**, **Wm 2 port (master power)**, **WiFi port (access point)**, **USB2**, and **100BaseT**. + +Connections from the switch: + +- The **Wm 1 port (master coax)** connects to a **Coax** line, which is connected to three **Node** devices and a **Bridge** device. The **Bridge** is connected to a **Node** device, which is then connected to a **Phone line**. +- The **Wm 2 port (master power)** connects to a **Power line**, which is connected to three **Node** devices and a **Master (phone)** device. The **Master (phone)** is also connected to the **Phone line**. +- The **WiFi port (access point)** connects to a dashed line representing a wireless network, which is connected to three **Alien node** devices. These nodes are labeled as **Wireless clients**. +- The **USB2** port connects to **USB clients**. +- The **100BaseT** port connects to **100BaseT clients**. + +At the bottom right, the text **G.9960(15) FI.5** is present. + +Diagram of a home network architecture showing a Residential gateway connected to an Access network, an Ethernet switch, and various client devices via Coax, Power line, and Phone line connections. + +**Figure I.5 – Example of a home network supporting residential broadband access** + +## Appendix II + +### Spectral usage + +(This appendix does not form an integral part of this Recommendation.) + +#### II.1 Scope + +This appendix describes information on spectral usage on each medium (coax cable, telephone line and power line). + +#### II.2 Spectral usage in Japan + +##### II.2.1 Frequency allocation for coax + +There are mainly three types of services which are mapped to in-home coax medium: + +- terrestrial broadcasting +- satellite broadcasting +- CATV services. + +The frequency allocations for all cases are shown in this clause. + +It should be noted that a coaxial home network connected to a cable access network should not interfere with services offered by the cable television operator to customers. The general use of the frequency by the cable television operator is 5 to 770 MHz. + +##### II.2.1.1 Terrestrial broadcast signal mapped to coax cable + +Table II.1 shows the frequency allocation for terrestrial TV broadcasting mapped to coax cable. Currently, both analogue TV broadcasting (VHF/UHF) and digital TV broadcasting (UHF) are in service [b-Spectrum]. But analogue TV broadcasting services were planned to be discontinued on 24 July 2011 [b-Schedule] [b-Announcement] and non-TV broadcasting and other telecommunications were planned to use these bands after that. ITU-T G.9960 is one of the candidate services for empty bands if available, but this is for further study. + +**Table II.1 – Frequency allocation for terrestrial broadcast signals mapped to a coax cable** + +| Frequency (MHz)
(Note) | Remarks | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 90 to 108 | Used for analogue TV broadcasting until 24 July 2011
The use after 25 July 2011 is not determined at the time of publication
Retransmission of terrestrial digital TV broadcasting (OFDM) | +| 108 to 170 | Retransmission of terrestrial digital TV broadcasting (OFDM) | +| 170 to 222 | Used for analogue TV broadcasting until 24 July 2011
The use after 25 July 2011 is not determined at the time of publication
Retransmission of terrestrial digital TV broadcasting (OFDM) | +| 222 to 470 | Retransmission of terrestrial digital TV broadcasting (OFDM) | +| 470 to 710 | Used for analogue TV broadcasting until 24 July 2011
Used for digital TV broadcasting
Retransmission of terrestrial digital TV broadcasting (OFDM) | + +**Table II.1 – Frequency allocation for terrestrial broadcast signals mapped to a coax cable** + +| Frequency (MHz)
(Note) | Remarks | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 710 to 770 | Used for TV broadcasting until 24 July 2012
The use after 25 July 2012 is not determined at the time of publication
Retransmission of terrestrial digital TV broadcasting (OFDM) | +| NOTE – Frequency band usage for ITU-T G.9960 including guard band is for further study. | | + +**II.2.1.2 Broadcast satellite (BS) and communication satellite (CS) signal mapped to coax cable** + +Satellite broadcasting (BS and CS) using around 12 GHz of frequency [b-Spectrum] are down-converted to intermediate frequency (BS-IF/CS-IF) at an antenna before transmission to a coax cable. The BS and CS need dedicated receiver antennas and there are various cases to use in-home coax cables depending on locations of antennas and connection points to an in-home coax system. Basically, BS-IF/CS-IF signals come from an antenna or CATV. Table II.2 shows satellite broadcast signals mapped to a coax cable. + +**Table II.2 – Frequency allocation for satellite broadcast signals mapped to a coax cable** + +| Satellite broadcasting services
(Note) | BS-IF/CS-IF
(MHz) | Remarks | +|-------------------------------------------------------------------------------------|----------------------|--------------------| +| BS | 1035.95-1331.50 | BS-IF transmission | +| 110° CS | 1596-2070 | CS-IF transmission | +| JC SAT-3,4 | 968-2055 | CS-IF transmission | +| Superbird C | 1020-2040 | CS-IF transmission | +| NOTE – ITU-T G.9960 frequency band usage including guard band is for further study. | | | + +**II.2.1.3 CATV services on coax cable** + +Table II.3 shows the frequency allocation of other services [b-CTBL] [b-STD-013]. Since frequencies below 770 MHz are currently used for the various services listed in Table II.3, their usage for other services such as ITU-T G.9960 is for further study. + +**Table II.3 – Frequency allocation of other services on coax cable** + +| Frequency
(MHz) | Usage | Remarks | +|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5 to 60
(Note 1) |
  • Upstream CATV signal (cable Internet signal, VoIP, VOD, relay broadcast, pilot signal, etc.)
| | +| 70 to 76
(Note 1) |
  • Downstream pilot signal, analogue HT (home terminal) control signal, monitoring signal of amplifier
| | + +**Table II.3 – Frequency allocation of other services on coax cable** + +| Frequency (MHz) | Usage | Remarks | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| 76 to 90
(Note 1) |
  • Retransmission of radio broadcasting on cable (FM radio signal)
| | +| 90 to 770
(Note 1) |
  • Analogue cable broadcasting (NTSC-VSB)
  • Digital cable broadcasting (64/256 QAM)
  • Retransmission of terrestrial analogue TV broadcasting (NTSC-VSB)
  • Retransmission of terrestrial digital TV broadcasting (OFDM)
  • Downstream cable Internet signal, VoIP, VOD control signal, etc.
|
  • Covered by regulation [b-CTBL]
| +| 770 to 1035
(Note 2) |
  • Alien home network services
| | +| 1035 to 2070
(Note 1) |
  • BS-IF/CS-IF retransmission
| | +| >2070
(Note 2) |
  • Currently not in use at the time of publication
| | + +NOTE 1 – ITU-T G.9960 frequency band usage including guard band is for further study. + +NOTE 2 – Candidate frequency band for ITU-T G.9960 including guard band. + +## II.2.2 Frequency allocation for telephone line + +For further study. + +## II.2.3 Frequency allocation for power line + +For further study. + +## Appendix III + +### Priority mapping + +(This appendix does not form an integral part of this Recommendation) + +The priority mapping recommended by [IEEE 802.1Q] (see clause 8.6.6 of [IEEE 802.1Q]) is presented in Table III.1. + +**Table III.1 – Recommended flow priority to priority queue mappings according to Table 8-5 of [IEEE 802.1Q]** + +| | | Number of available traffic classes | | | | | | | | +|----------------------|--------------------|--------------------------------------------|---|---|---|---|---|---|---| +| | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | +| User priority | 0 (default) | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | +| | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| | 2 | 0 | 0 | 0 | 1 | 1 | 2 | 2 | 2 | +| | 3 | 0 | 0 | 0 | 1 | 1 | 2 | 3 | 3 | +| | 4 | 0 | 1 | 1 | 2 | 2 | 3 | 4 | 4 | +| | 5 | 0 | 1 | 1 | 2 | 2 | 3 | 4 | 5 | +| | 6 | 0 | 1 | 2 | 3 | 3 | 4 | 5 | 6 | +| | 7 | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | + +## **Appendix IV** + +(This appendix has been intentionally left blank.) + +## Appendix V + +### Electric vehicle applications based on ITU-T G.9960 + +(This appendix does not form an integral part of this Recommendation.) + +#### V.1 Introduction + +This appendix describes how ITU-T G.9960 nodes can be used for applications related to plug-in electric vehicles (PEVs), including networking nodes installed into the electric vehicle supply equipment (EVSE) and nodes installed into the PEV, designated here as "EV nodes". These nodes, both in the EVSE and attached EV(s), form an electric vehicle charging facility (EVCF). + +To reduce the complexity and energy consumption of ITU-T G.9960 nodes in an EVCF, these nodes may be implemented using ITU-T G.9960 low-complexity profiles. Low-complexity profile nodes are fully interoperable with other ITU-T G.9960 nodes operating in the same domain. + +A simplified diagram of an EVCF including EVSE and an attached EV, showing the primary external connections, is presented in Figure V.1. + +![Diagram of an EVCF showing external links and internal components.](409e3ccf9694772191dc84c49f3f7afb_img.jpg) + +The diagram illustrates the connections within an Electric Vehicle Charging Facility (EVCF). On the left, a 'Residence electric meter with ESI' is connected to a 'Residence circuit breaker panel'. An arrow labeled 'To/From utility' points upwards from the meter. Another arrow labeled 'To/From HAN' points downwards from the circuit breaker panel. A yellow line labeled 'Feed to EVSE from circuit breaker panel' connects the circuit breaker panel to the EVSE. The EVSE is shown as a box containing an 'ITU-T G.9960 SG node' and a 'Sub-meter'. A green line labeled 'J-1772 cable' connects the EVSE to an 'Electric vehicle'. The electric vehicle contains an 'ITU-T G.9960 EV node'. The entire EVSE and Electric vehicle section is enclosed in a grey box labeled 'EV charging facility'. The diagram is labeled 'G.9960(15)\_FV.1' in the bottom right corner. + +Diagram of an EVCF showing external links and internal components. + +**Figure V.1 – EVCF with EVSE and one attached EV showing external links** + +#### V.2 EVSE and EV devices + +ITU-T G.9960 nodes embedded into EVs and EVSEs perform the following common functions: + +- establish a link between EVSE and EV nodes in a period that does not exceed five seconds; +NOTE 1 – Establishing a link includes at least registration and authentication of the EVSE node, registration and authentication of the EV node by using the EVSE node as a proxy, and getting authorization from the utility for the charging activity. +- operate in a mode where the EVSE node operates as a proxy for the EV node of the connected PEV, i.e., all the communications between the EV node and the outside world are exclusively through the EVSE node. +- The data exchanged between EVSE and EV nodes can be of three types: recharging/discharging management, EV maintenance, and multimedia data. The first type may only require low throughput, while the second and third types require relatively high data throughout (with a predominant amount downstream to the EV). Some EVs may only require the first two types of data. + +The EVSE device provides the following communications: + +- with the HAN domain master (or ESI, if ESI is the domain master in the residence) and the associated security controller; + +- with HAN nodes, directly or via an IDB if the HAN uses non-ITU-T G.9960 technology. The EVSE node should coexist with the HAN if it is unable to communicate with it directly; +- with the ESI of the residence, directly or via an IDB if the ESI uses non-ITU-T G.9960 technology. The EVSE node should coexist with the ESI if it is unable to communicate with it directly; + +NOTE 2 – In the event that an ESI is not present, the EVSE could communicate with the utility's servers through the broadband link that the HAN is connected to. + +- with the utility, via the ESI or over the HAN's broadband link (if present and utility allowed). These communications provide the EVSE with information such as billing rates, the maximum amount of current flow allowed, the allowed time for charging, the authorization of the specific vehicle to charge at this specific EVSE, and the meter readings related to the charge; +- with an EV node of any PEV attached to the EVSE's J-1772 cable(s). The EVSE node acts as a proxy for the EV node into the HAN and the ESI. + +An example of a connection between an EVSE and an EV node is presented in Figure V.2. The EVSE controller detects a J-1772 connection to an EV (via sense lead) and triggers EVSE node connection to the EV, as well as triggering electricity to flow over the cable once all authorization is completed. The EV controller manages the charging of the batteries in the EV and turns the EV node on and off depending on sense lead status or the option that the EV controller determines the EV is going to charge through a regular power outlet. + +![Diagram of a simple EVSE to EV link using a J-1772 cable. The EVSE (Electric Vehicle Supply Equipment) on the left is connected to a power feed through a coupler and sub-meter. It contains a Controller, an ITU-T G.9960 SG (Smart Grid) node, and a Coupler. A J-1772 cable connects the EVSE's Plug to the EV's Connector. The EV (Electric Vehicle) on the right contains a Controller, an ITU-T G.9960 EV node, a Coupler, and a Smart charger. The EV is connected to the EVSE via the J-1772 cable, which is approximately 10 metres long. The EVSE controller is connected to the EV controller via the sense lead (dashed line). The EVSE is labeled 'EVSE' and the EV is labeled 'PHEV'.](0fec4b5689fcc9aa96a87f0c1bdaf200_img.jpg) + +The diagram illustrates the connection between an EVSE and a PHEV. On the left, the EVSE is connected to a power feed through a coupler and sub-meter. It contains a Controller, an ITU-T G.9960 SG node, and a Coupler. A J-1772 cable connects the EVSE's Plug to the EV's Connector. The EV (labeled PHEV) on the right contains a Controller, an ITU-T G.9960 EV node, a Coupler, and a Smart charger. The EV is connected to the EVSE via the J-1772 cable, which is approximately 10 metres long. The EVSE controller is connected to the EV controller via the sense lead (dashed line). The EVSE is labeled 'EVSE' and the EV is labeled 'PHEV'. + +Diagram of a simple EVSE to EV link using a J-1772 cable. The EVSE (Electric Vehicle Supply Equipment) on the left is connected to a power feed through a coupler and sub-meter. It contains a Controller, an ITU-T G.9960 SG (Smart Grid) node, and a Coupler. A J-1772 cable connects the EVSE's Plug to the EV's Connector. The EV (Electric Vehicle) on the right contains a Controller, an ITU-T G.9960 EV node, a Coupler, and a Smart charger. The EV is connected to the EVSE via the J-1772 cable, which is approximately 10 metres long. The EVSE controller is connected to the EV controller via the sense lead (dashed line). The EVSE is labeled 'EVSE' and the EV is labeled 'PHEV'. + +**Figure V.2 – Simple EVSE to EV link using a J-1772 cable** + +For residential garages, it is anticipated that the EVSE will communicate with an estimated two vehicles simultaneously, over individual J-1772 cables from the EVSE, respectively. For deployment in public parking areas, it is envisioned that an EVSE will have the ability to handle up to four EVs concurrently, see Figure V.3. In both cases, the EVSE controller, with assistance of the EVSE node, will identify which EV is associated with which metre and J-1772 cable. + +![Diagram of an EVSE connected to four PHEVs. On the left, a 'Multi-vehicle EVSE' box contains a 'Feed' line, an 'ITU-T G.9960 SG' node, a 'Controller', and four 'Sub-meter' nodes. A label 'Power feed is common' points to the feed line. Each sub-meter connects via a 'J-1772 cable' (consisting of 'Plug' and 'Connector' components) to one of four 'PHEV' units on the right. Each PHEV unit contains an 'ITU-T G.9960 EV' node, a 'Controller', and a 'Smart charger'. A 'Sense' line connects the EVSE controller to each sub-meter. A label 'EV link cables' is at the bottom. A small code 'G.9960(15) EV/3' is in the bottom right corner.](978794771205b002dd72295a59de7919_img.jpg) + +Diagram of an EVSE connected to four PHEVs. On the left, a 'Multi-vehicle EVSE' box contains a 'Feed' line, an 'ITU-T G.9960 SG' node, a 'Controller', and four 'Sub-meter' nodes. A label 'Power feed is common' points to the feed line. Each sub-meter connects via a 'J-1772 cable' (consisting of 'Plug' and 'Connector' components) to one of four 'PHEV' units on the right. Each PHEV unit contains an 'ITU-T G.9960 EV' node, a 'Controller', and a 'Smart charger'. A 'Sense' line connects the EVSE controller to each sub-meter. A label 'EV link cables' is at the bottom. A small code 'G.9960(15) EV/3' is in the bottom right corner. + +**Figure V.3 – EVSE attached to four EVs** + +Typically, the vehicle needs to communicate with the far-end system (utility) for charging authorization and with other services using the EVSE as a proxy. The link between the EV and corresponding EVSE in the EVCF is secure, with a point-to-point key established using the regular ITU-T G.9960 AKM procedure. + +The EV node may have these characteristics: + +- Communicate to the HAN or ESI through the EVSE node, which may serve as a proxy for the EV node. +- EV node transmission power levels are controlled to prevent unnecessary EMI and unintended association between the EV of different J-1772 cables, using the standard ITU-T G.9960 power ceiling set-up procedure where lower power levels are established and maintained as default. +- The EV nodes are not expected to act as proxies, as relays, or as domain masters, and not expected to maintain large topology tables. +- The EV node transmission data rate is not expected to exceed 5 Mbit/s. +- The EV node receive data rate is not expected to exceed 20 Mbit/s. +- The EV node is not expected to have special requirement for low latency of data processing. + +Using one or more network nodes besides the EV node is for further study. In the example presented in Figure V.4, the plug-in hybrid electric vehicle (PHEV) nodes may be standard low complexity ITU-T G.9960 SG nodes and able to communicate with one another. + +![Diagram of multiple nodes within an electric vehicle (EV) connected to an EVSE via a J-1772 cable and an ITU-T G.9960 link.](c2c45d2f2b1eecc0149f1b5b0ae82994_img.jpg) + +The diagram illustrates the network architecture within an electric vehicle (EV). On the left, an external component labeled 'EVSE' is connected to the EV via a 'J-1772 cable'. Inside the EV, represented by a grey box, a red line labeled 'ITU-T G.9960 link' serves as the central communication bus. This link connects to four internal nodes: + +- An 'ITU-T G.9960 EV node' at the top left. +- An 'ITU-T G.9960 SG node' at the top right, which is further connected to a 'Video and Mp3 player'. +- An 'ITU-T G.9960 SG node' at the bottom left, which is further connected to 'Video and data storage'. +- An 'ITU-T G.9960 SG node' at the bottom right, which is further connected to a 'GPS'. + +The label 'Electric vehicle' is placed in the top right corner of the grey box. A small text label 'G.9960(15)\_FV.4' is located at the bottom right of the diagram. + +Diagram of multiple nodes within an electric vehicle (EV) connected to an EVSE via a J-1772 cable and an ITU-T G.9960 link. + +**Figure V.4 – Example of multiple nodes within an EV** + +A typical distance between the EV node and the EVSE node is 10 m, although this distance could be longer in a public parking area or in a multi-car garage. + +### V.3 Overall network architecture + +The EVSE nodes are connected to the HAN and the ESI based on the standard ITU-T G.9960 architecture (see Figure 5-1). The usual application uses a power line as a communication medium, see Figure V.5, although any other in-home wired medium is possible with ITU-T G.9960. + +![Figure V.5 – Illustration of smart grid HAN with EVCF implementation based on ITU-T G.9960. The diagram shows a Multi-domain HAN (yellow) connected to Domain B (green) via a bridge. Domain A (yellow) contains Non-SG ITU-T G.9960 nodes (DM A, EMS, and two others) and SGH ITU-T G.9960 nodes (EVSE, EMS, and two others). The EVSE node is connected to an EV (ITUT G.9960 node) via an EVCF. The EVSE node is also connected to an ESC (Energy Service Controller) and a PBC (Power Bridge Controller). The ESC is connected to an ESI (Energy Service Interface) node, which is connected to an SGA (Smart Grid Appliance) node. The SGA node is connected to an SGA meter, which is connected to a Residence boundary. The Residence boundary is connected to a Utility access (smart grid). A bridge between domains A and B is shown at the top. A bridge to alien domain (BB link) is shown between Domain A and Domain B. The diagram is labeled G.9960/151 EV5.](bae1bd2b5dec0c7f0717e710ad5a3412_img.jpg) + +Figure V.5 – Illustration of smart grid HAN with EVCF implementation based on ITU-T G.9960. The diagram shows a Multi-domain HAN (yellow) connected to Domain B (green) via a bridge. Domain A (yellow) contains Non-SG ITU-T G.9960 nodes (DM A, EMS, and two others) and SGH ITU-T G.9960 nodes (EVSE, EMS, and two others). The EVSE node is connected to an EV (ITUT G.9960 node) via an EVCF. The EVSE node is also connected to an ESC (Energy Service Controller) and a PBC (Power Bridge Controller). The ESC is connected to an ESI (Energy Service Interface) node, which is connected to an SGA (Smart Grid Appliance) node. The SGA node is connected to an SGA meter, which is connected to a Residence boundary. The Residence boundary is connected to a Utility access (smart grid). A bridge between domains A and B is shown at the top. A bridge to alien domain (BB link) is shown between Domain A and Domain B. The diagram is labeled G.9960/151 EV5. + +**Figure V.5 – Illustration of smart grid HAN with EVCF implementation based on ITU-T G.9960** + +NOTE – The SGH nodes and non-SG nodes relate to smart grid and non-smart grid applications, respectively, both complying with this Recommendation. + +The EVSE contains an SG node that may interface with the HAN (directly, or via an IDB, if the HAN is a non-ITU-T G.9960 network) and with the utility network via the ESI or via a broadband services provider through a HAN broadband gateway. + +#### V.4 Authorization of an EV + +The EV node, upon being notified of the active J-1772 link, seeks to establish connection to the nearest proxy node, in this case the EVSE. Once establishing communication with the EVSE node, the EV node uses the normal ITU-T G.9960 registration and authentication procedures through the EVSE node, using it as a proxy. The authorization is supported by the utility remotely through a trusted channel to the utility established from the EVSE via the ESI and access network. Through this trusted channel the utility validates the EV's identity credentials and authorizes its access in the EVCF as well as the EVSE to charge the EV at a certain maximum charge rate, for a certain time, and at a certain moment. The protocol of utility authorization is outside the scope of this Recommendation. + +#### V.5 Charging an EV without an EVSE + +In the event the EV is to be charged and no EVSE is available, the EV may have an option for plugging it in to a standard mains outlet using a cable other than a J-1772 cable. This option is for further study. + +## Bibliography + +- [b-ITU-T G.9963] Recommendation ITU-T G.9963 (2018), *Unified high-speed wireline-based home networking transceivers – Multiple input/multiple output specification*. +- [b-ITU-T J.112] Recommendation ITU-T J.112 (1998), *Transmission systems for interactive cable television services*. +- [b-ITU-T J.122] Recommendation ITU-T J.122 (2007), *Second-generation transmission systems for interactive cable television services – IP cable modems*. +- [b-ITU-T J.222.1] Recommendation ITU-T J.222.1 (2007), *Third-generation transmission systems for interactive cable television services – IP cable modems: Physical layer specification*. +- [b-TR-069] Broadband Forum TR-069 (2004), *CPE WAN management protocol*. +- [b-IEC CISPR 16-1-1] IEC CISPR 16-1-1:2010, *Specification for radio disturbance and immunity measuring apparatus and methods*. +- [b-IEC CISPR 22] IEC CISPR 22:2008, *Information technology equipment – Radio disturbance characteristics – Limits and methods of measurement*. +- [b-IEC 60793-2-40] International Standard IEC 60793-2-40:2009, *Optical fibres – Part 2-40: Product specifications – Sectional specification for category A4 multimode fibres*. +- [b-IEC 61754-21] International Standard IEC 61754-21:2005, *Fibre optic connector interfaces – Part 21: Type SMI connector family for plastic optical fibre*. +- [b-IEC 61754-24] International Standard IEC 61754-24:2009, *Fibre optic interconnecting devices and passive components – Fibre optic connector interfaces – Part 24: Type SC-RJ connector family*. +- [b-IEEE 802.11] IEEE 802.11-2007, *IEEE standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements – Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications*. +- [b-IEEE 802.1x] IEEE 802.1x-series, *IEEE standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks*. +- [b-Announcement] Japanese Ministry of Internal Affairs and Communications, *Announcement of channel plan for terrestrial digital TV broadcasting* (Japanese). +<[http://www.soumu.go.jp/s-news/2008/080331\\_11.html](http://www.soumu.go.jp/s-news/2008/080331_11.html)> +- [b-CTBL] Cable Television Broadcast Law (Japanese). +<> +- [b-Regulations] Radio Wave Law Enforcement Regulations Article 46-2 (Japanese). +<> +- [b-Schedule] Japanese Ministry of Internal Affairs and Communications, *Schedule* (Japanese). +<[http://www.soumu.go.jp/joho\\_tsusin/whatsnew/digital-broad/when\\_en.html](http://www.soumu.go.jp/joho_tsusin/whatsnew/digital-broad/when_en.html)> + +- [b-Spectrum] Japanese Ministry of Internal Affairs and Communications, *Spectrum Charts* (Japanese). +<> +- [b-STD-013] Japan Cable Television Engineering Association (JCTEA) STD-013-2.0, *Transmission System for MDU* (Japanese). +<> + + + +## 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.9962-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abda52cbb1047d6649f89e40c898a1c33bed7267 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_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.9962-202304-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a91f6d678861037817c8e337a93db432c953110 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/15e4a144a88176b71ea3eff2722253b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2158c10d16b00e71ba3bdaa1a1a7739f132bdf98fb92082496994e2b5ac635c9 +size 77759 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09ac5dabb47f46f42c64cf2046a6e2f03b7d4ded --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e062945cc56eb3df0210572d8a015fbca6ff4b92692dd75a38e76a91633ecfaa +size 12231 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..786722f9750e9e8feb7670d11bb5b95477e7996f --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e702a9472715d15405952668894df2f908784bea4d913cd45a8697b09dfcf020 +size 12346 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ed31b7b9ddd88e54659a0a0a0f2ae54dfa3eca2 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e383f0cf6e4b7f09b46421b915bb9c093b422ed928bf9d2e1177ee902e5fab62 +size 40367 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1aa3f60bbe87344e30080b10d70382eb6c0eaad1 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc052cde5d94d2542413f69daa8d1cc61b0a3e52894aaff13b1084599c7c611a +size 110118 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac9b186c754f30c57fb26d8a0bc7f7e9df948ab6 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/83852ec55d4802521a727926336bedab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:616f9cf82c550d092817b41faa888b61fa8ea9ed483ee27e436570604b201baa +size 12313 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a83b83243e70fc1f7050fed054014b0ab120052 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66be8f35ab1abd7d25bbcb8896e2de5d0f71e0bf6360eb8df3cdf07def245d27 +size 12049 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb1c98ccb4254be7a471313d976c31dbe1b54357 --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/cfda9df1319e04207eb28bcefd1dab7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:633fad24c9258326bc49d1860cb6546965b86ca346d9ea3792722e8376d42a38 +size 120888 diff --git a/marked/G/T-REC-G.9962-202304-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.9962-202304-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18183d306063d08cf0ed49382d2a048e27445d0f --- /dev/null +++ b/marked/G/T-REC-G.9962-202304-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf912523a37d5ece908fdcd191d73dbf17f5b797c31532a22669fc39c8cf88d3 +size 84789 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6e2587fbae5f6e5233c43369ee637dc9b94e331 --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:479d9f074c9e46c8d26f4e31876ff45836d8158322ecbb33715cbf0ccca47a9d +size 24142 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..529e4f72f14cdf7f41f56cfbfb26655bf8181c59 --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/a3dc41dc3df86ea68d266af2bf95cf5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb9e3ec6dfc8364cedc39a68cf796e9d3ff5529c79a1811eedeb12c6d6e7583 +size 3787 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0908b6c911defe9cb7cba10bc1c31538b073a0a --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f0702dbbd21a6770c2e3505ee010dc8689ffc7098d25818ee98f7c06395b05c +size 42154 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46546718457cacc38b67b5bb925ce2e1e5dcf9f1 --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b243570c2bb8cbeb343acc5b8bc7f7ee154e4dc4a2a05fba7241d5c4704948ee +size 42429 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4248f712f66eb28257af982ef0dfe1555e9c9dc5 --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f87078c926dba49a147126868f8d977a4171f114d98ca885e34580e4fda0374 +size 47201 diff --git a/marked/G/T-REC-G.9979-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/G/T-REC-G.9979-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5167378af3c65b1538e13c11f839b72ea6e961a --- /dev/null +++ b/marked/G/T-REC-G.9979-201811-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59526b0ef414ff44dd1c6d4a4e1a037cbb80c766ee24d6bd0dbedcc95a677a22 +size 50019 diff --git a/marked/G/T-REC-G.9992-201903-I_PDF-E/raw.md b/marked/G/T-REC-G.9992-201903-I_PDF-E/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dcc7ce66ad63cdf456fce4c03738b778ebecd906 --- /dev/null +++ b/marked/G/T-REC-G.9992-201903-I_PDF-E/raw.md @@ -0,0 +1,2412 @@ + + +**ITU-T** + +TELECOMMUNICATION +STANDARDIZATION SECTOR +OF ITU + +**G.9992** + +(03/2019) + +SERIES G: TRANSMISSION SYSTEMS AND MEDIA, +DIGITAL SYSTEMS AND NETWORKS + +Access networks – In premises networks + +--- + +**Indoor optical camera communication +transceivers – System architecture, physical +layer and data link layer specification** + +Recommendation ITU-T G.9992 + +# 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.992 + +# Indoor optical camera communication transceivers – System architecture, physical layer and data link layer specification + +## Summary + +Recommendation ITU-T G.992 specifies the system architecture, physical (PHY) layer and data link layer (DLL) for indoor optical camera communication transceivers. + +## History + +| Edition | Recommendation | Approval | Study Group | Unique ID* | +|---------|----------------|------------|-------------|---------------------------------------------------------------------------| +| 1.0 | ITU-T G.992 | 2019-03-22 | 15 | 11.1002/1000/13782 | + +## Keywords + +DLL, MIMO, OCC, PHY, SISO, UPPM, UPWM. + +--- + +\* 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..... | 2 | +| 4 Abbreviations and acronyms ..... | 3 | +| 5 Conventions ..... | 4 | +| 5.1 Bit ordering convention..... | 4 | +| 5.2 Endpoint node..... | 6 | +| 6 System architecture and reference models ..... | 6 | +| 6.1 System architecture and topology ..... | 6 | +| 6.2 Reference models ..... | 7 | +| 7 Profiles..... | 10 | +| 7.1 Reduced-complexity profile ..... | 11 | +| 7.2 Standard profile ..... | 11 | +| 8 Physical layer specification ..... | 11 | +| 8.1 SISO transmission ..... | 11 | +| 8.2 UPWM-based MIMO transmission..... | 36 | +| 8.3 UPPM-based MIMO transmission ..... | 43 | +| 8.4 Control parameters ..... | 56 | +| 9 Data link layer specification ..... | 57 | +| 9.1 Functional model of DLL and frame formats..... | 57 | +| 9.2 Addressing scheme ..... | 62 | +| Annex A – Application protocol convergence sublayer ..... | 64 | +| A.1 Ethernet APC..... | 64 | +| A.2 Other types of APC ..... | 66 | +| Bibliography..... | 67 | + + + +## Recommendation ITU-T G.992 + +## Indoor optical camera communication transceivers – System architecture, physical layer and data link layer specification + +# 1 Scope + +This Recommendation specifies the system architecture and functionality for all components of the physical layer (PHY) and data link layer (DLL) of optical camera communication (OCC) transceivers for in-premises applications. + +In particular, this Recommendation specifies: + +- the OCC system architecture and reference models; +- the physical layer (PCS, PMA and PMD); and +- the data link layer. + +# 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. + +- [IEEE 802.1ad] IEEE 802.1ad-2005, *IEEE Standard for Local and metropolitan area networks: Provider Bridges*. +- [IEEE 802.1D] IEEE 802.1D -2004, *IEEE Standard for Local and metropolitan area networks Media Access Control (MAC) Bridges*. +<> +- [IEEE 802.1Q] IEEE 802.1Q-2005, *IEEE Standard for Local and Metropolitan Area Networks – Virtual Bridged Local Area Networks – Revision*. +<> +- [IEEE 802.3] IEEE 802.3-2008, *IEEE Standard for Information technology-Specific requirements – Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications*. +<> + +# 3 Definitions + +## 3.1 Terms defined elsewhere + +This Recommendation uses the following terms defined elsewhere: + +**3.1.1 channel** [b-ITU-T G.9960]: A transmission path between nodes. One channel is considered to be one transmission path. Logically, a channel is an instance of a communication medium used for the purpose of passing data between two or more nodes. + +**3.1.2 coding overhead** [b-ITU-T G.9960]: A part of the overhead used to carry the coding redundancy (such as redundancy bits of error correction coding or cyclic redundancy check (CRC)). + +**3.1.3 data** [b-ITU-T G.9960]: Bits or bytes transported over the medium or via a reference point that individually convey information. Data includes both user (application) data and any other auxiliary information (overhead, including control, management, etc.). Data does not include bits or bytes that, by themselves, do not convey any information, such as the preamble. + +**3.1.4 data rate** [b-ITU-T G.9960]: The average number of bits communicated (transmitted) in a unit of time. The usual unit of time for data rate is 1 second. + +**3.1.5 logical (functional) interface** [b-ITU-T G.9960]: An interface in which the semantic, syntactic, and symbolic attributes of information flows are defined. Logical interfaces do not define the physical properties of signals used to represent the information. It is defined by a set of primitives. + +**3.1.6 physical interface** [b-ITU-T G.9960]: An interface defined in terms of physical properties of the signals used to represent the information transfer. A physical interface is defined by signal parameters such as power (power spectrum density), timing, and connector type. + +**3.1.7 primitives** [b-ITU-T G.9960]: Basic measures of quantities obtained locally or reported by other nodes of the domain. Performance primitives are basic measurements of performance-related quantities, categorized as events, anomalies and defects. Primitives may also be basic measures of other quantities (e.g., a.c. or battery power). + +**3.1.8 reference point** [b-ITU-T G.9960]: A location in a signal flow, either logical or physical, that provides a common point for observation and/or measurement of the signal flow. + +## **3.2 Terms defined in this Recommendation** + +This Recommendation defines the following terms: + +**3.2.1 alien domain:** Any group of non-ITU-T G.9992 nodes connected to the same medium or that operate in close proximity. + +NOTE – The bridging function to an alien domain, as well as coordination with an alien domain to avoid mutual interference is beyond the scope of this Recommendation. + +**3.2.2 domain:** An ITU-T G.9992 network comprising the domain master and all those nodes that are registered with the same domain master. + +NOTE – In the context of this Recommendation, use of the term "domain" without a qualifier means "ITU-T G.9992 domain". Additional qualifiers (e.g., "OCC") may be added to "domain". + +**3.2.3 domain master (DM):** A node supporting the domain master functionality that manages (coordinates) all other nodes of the same domain (i.e., assigns bandwidth resources and manages priorities). Only one active domain master is allowed in a domain, and all nodes within a domain are managed (coordinated) by a single domain master. + +**3.2.4 global master (GM):** A function that provides coordination between different domains (such as communication resources, policies of domain masters). A global master may also convey management functions initiated by the remote management system (e.g., the Broadband Forum CPE WAN management protocol) to support broadband access. + +**3.2.5 node:** Any network device that contains an ITU-T G.9992 transmitter/receiver/transceiver. + +NOTE – In the context of this Recommendation, use of the term "node" without a qualifier means "ITU-T G.9992 node". Additional qualifiers may be added to either "node". + +**3.2.6 unidirectional broadcasting node:** A node supporting the unidirectional broadcasting node functionality that broadcasts signals in an ITU-T G.9992 system that operates in a unidirectional broadcasting mode. + +# 4 Abbreviations and acronyms + +This Recommendation uses the following abbreviations and acronyms: + +| | | +|------|-----------------------------------------| +| AAT | Address Association Table | +| ADP | Application Data Primitive | +| AE | Application Entity | +| APC | Application Protocol Convergence | +| APDU | Application Protocol Data Unit | +| CRC | Cyclic Redundancy Check | +| DBM | Domain Based Mode | +| DC | Duty Cycle | +| DID | Destination ID | +| DLL | Data Link Layer | +| DM | Domain Master | +| DPI | Destination ID field Present Indication | +| DSL | Digital Subscriber Line | +| EDR | End Delimiter Region | +| FCS | Frame Check Sequence | +| FEC | Forward Error Correction | +| FLEN | Frame Length | +| FT | Frame Type | +| FTSF | Frame-Type Specific Field | +| GM | Global Master | +| GS | Global Shutter | +| HCS | Header Check Sequence | +| IDB | Inter-Domain Bridges | +| IDR | Interval Delimiter Region | +| LAAT | Local Address Association Table | +| LCDU | Link Control Data Unit | +| LFH | Logical link control Frame Header | +| LED | Light Emitting Diode | +| LLC | Logical Link Control | +| LNIR | LED Number Indicating Region | +| LSB | Least Significant Bit | +| MAC | Medium Access Control | +| MDI | Medium-Dependent Interface | +| MIMO | Multiple Input/Multiple Output | + +| | | +|------|-----------------------------------------| +| MMH | Management Message Header | +| MMPL | Management Message Parameter List | +| MPDU | Media access control Protocol Data Unit | +| MSB | Most Significant Bit | +| OCC | Optical Camera Communication | +| PB | Parity Bit | +| PCS | Physical Coding Sublayer | +| PFH | PHY-frame headers | +| PHY | Physical Layer | +| PI | Preamble Information | +| PL | Payload Length | +| PMA | Physical Medium Attachment | +| PMD | Physical Medium Dependent | +| PMI | Physical Medium-independent Interface | +| PON | Passive Optical Network | +| PSD | Power Spectral Density | +| PWM | Pulse Width Modulation | +| RAAT | Remote Address Association Table | +| RCP | Reduced-Complexity Profile | +| RS | Rolling Shutter | +| SDR | Start Delimiter Region | +| SID | Source ID | +| SISO | Single Input/Single Output | +| SS | Spatial Streams | +| UBM | Unidirectional Broadcasting Mode | +| UPPM | Undersampled Pulse Position Modulation | +| UPWM | Undersampled Pulse Width Modulation | +| VDR | Valid Data Region | + +# 5 Conventions + +## 5.1 Bit ordering convention + +A block of data composed of multiple octets shall be ordered by octet numbers in ascending order: 'octet 0' for the first octet, 'octet 1' for the second octet, and so on. If a block of data is segmented into multiple fields, the size of each field shall be expressed in terms of bits. The field might not be an integer number of octets. The location of each field within a block of data shall be described as follows: + +- The octets of an $N$ -octet data block are ordered with numbers from 0 (first octet) to $N-1$ (last octet). + +- The block is divided into non-overlapping groups of octets. Each group contains an integer number of consecutive octets, numbered from $J$ to $J+V-1$ , where $V$ is the size of the group, and is described as a bit string with 'bit 0', the least significant bit (LSB) of the octet with the smallest number ( $J$ ), and 'bit $(8 \times V - 1)$ ', the most significant bit (MSB) of the octet with the largest number ( $J+V-1$ ). +- Each group is divided into one or more fields, where the boundaries of each field are determined by the LSB and the MSB of the bits of the group that contains this field. + +Any block or partial block of data shall be passed over the protocol stack with the octet having the smallest number first, i.e., octet 0 shall be the first octet of the block to be passed. Within each group of octets, the LSB (bit 0) of each octet shall be passed first. + +Table 5-1 shows an example of a field description used throughout this Recommendation. The 'Octet' column represents the octet numbers for a group of octets to which a specific field belongs, and the 'Bits' column represents the bit location within this group of octets. In the example presented, there are 4 groups of octets: + +- Group 1 = Octet 0, fields A, B, C, D +- Group 2 = Octets 1 and 2, fields E, F +- Group 3 = Octet 3, field G +- Group 4 = Octets 4 to 7, field H. + +Figure 5-1 illustrates a mapping of these fields onto corresponding octets based on the example given in Table 5-1. + +**Table 5-1 – Example of field description** + +| Field | Octet | Bits | Description | +|-------|-------|--------|-------------| +| A | 0 | [2:0] | ... | +| B | 0 | [3] | ... | +| C | 0 | [4] | ... | +| D | 0 | [7:5] | ... | +| E | 1 | [1:0] | ... | +| F | 1-2 | [15:2] | ... | +| G | 3 | [7:0] | ... | +| H | 4-7 | [31:0] | ... | + +![Figure 5-1: Example of mapping fields onto groups of octets. The diagram shows a table with 8 octets (0-7) and 8 bits (b7 to b0). Fields A, B, C, D, E, F, and H are mapped to specific bit groups across the octets. Octets 4-7 are all H. Octet 3 is all G. Octet 2 is all F. Octet 1 is F (b7-b2) and E (b1-b0). Octet 0 is D (b7-b4), C (b3), B (b2), and A (b1-b0). Arrows indicate the order of transmission from top to bottom for octets and right to left for bits.](d4af765160d04ecef538e5066006dc77_img.jpg) + +| | ← Order of transmission | | | | | | | | +|----------------------------|-------------------------|----|----|----|----|----|----|-------------| +| | b7
(MSB) | b6 | b5 | b4 | b3 | b2 | b1 | b0
(LSB) | +| ↓
Order of transmission | 0 | D | | C | B | A | | | +| 1 | F | | | | | E | | | +| 2 | F | | | | | | | | +| 3 | G | | | | | | | | +| 4 | H | | | | | | | | +| 5 | H | | | | | | | | +| 6 | H | | | | | | | | +| 7 | H | | | | | | | | + +G.9992(19)\_F5-1 + +Figure 5-1: Example of mapping fields onto groups of octets. The diagram shows a table with 8 octets (0-7) and 8 bits (b7 to b0). Fields A, B, C, D, E, F, and H are mapped to specific bit groups across the octets. Octets 4-7 are all H. Octet 3 is all G. Octet 2 is all F. Octet 1 is F (b7-b2) and E (b1-b0). Octet 0 is D (b7-b4), C (b3), B (b2), and A (b1-b0). Arrows indicate the order of transmission from top to bottom for octets and right to left for bits. + +**Figure 5-1 – Example of mapping fields onto groups of octets** + +## 5.2 Endpoint node + +This term is used in this Recommendation according to the context to differentiate between the domain master node functionalities and non-domain master node functionalities in a DBM domain, or between the unidirectional broadcasting node functionalities and non-unidirectional broadcasting node functionalities for unidirectional broadcasting mode. + +# 6 System architecture and reference models + +## 6.1 System architecture and topology + +An architectural model of an ITU-T G.9992 home network is presented in Figure 6-1. The model includes one or more unidirectional broadcasting nodes, one or more domains, inter-domain bridges (IDB), and bridges to alien domains such as a Wi-Fi or Ethernet home network, or a digital subscriber line (DSL) or passive optical network (PON) access network. The global master function coordinates resources such as bandwidth reservations, flow priorities, and operational characteristics between domains, and may convey the relevant functions initiated by a remote management system (e.g., as specified in [b-TR-069]) to support broadband access. + +NOTE 1 – Detailed specification and use of the global master function is for further study. + +NOTE 2 – The specification of bridges to alien domains and to the access network is beyond the scope of this Recommendation. + +NOTE 3 – It is not necessary that all inter-domain bridges presented in Figure 6-1 be used. Depending on the application, domains could be daisy-chained, or star-connected, or could use another connection topology. Support of multi-route connections between domains is for further study. + +NOTE 4 – It is possible to install multiple ITU-T G.9992 home networks (i.e., not connected by bridges to alien domain and the alien domain) per dwelling. + +NOTE 3 – The unidirectional broadcasting nodes are not involved in the coordination performed by the global master. + +![Figure 6-1 – Home network architecture reference model. The diagram shows a 'Bridge to alien domain (not in scope)' connected to a 'Unidirectional broadcasting node'. This node is connected to an 'Alien domain' (represented by an oval labeled 'Any medium'). Inside the 'Alien domain', a 'Global master (logical function)' is indicated. Below the 'Alien domain', there are two domains: 'Domain 1' and 'Domain S'. Each domain contains a 'Domain master' (orange box) and one or more 'Node' units (orange boxes). The connections between the Domain master and the Nodes are shown with dashed lines, which are labeled as 'Optical wireless medium (i.e., visible light)'. The diagram is labeled 'G.9992(19)_F6-1'.](af7916c89a458fdab6c3f443217388ae_img.jpg) + +Figure 6-1 – Home network architecture reference model. The diagram shows a 'Bridge to alien domain (not in scope)' connected to a 'Unidirectional broadcasting node'. This node is connected to an 'Alien domain' (represented by an oval labeled 'Any medium'). Inside the 'Alien domain', a 'Global master (logical function)' is indicated. Below the 'Alien domain', there are two domains: 'Domain 1' and 'Domain S'. Each domain contains a 'Domain master' (orange box) and one or more 'Node' units (orange boxes). The connections between the Domain master and the Nodes are shown with dashed lines, which are labeled as 'Optical wireless medium (i.e., visible light)'. The diagram is labeled 'G.9992(19)\_F6-1'. + +**Figure 6-1 – Home network architecture reference model** + +A domain comprises a domain master (DM) and may contain one or more nodes registered with it. The domain master considers bridges to alien domains as application entities (AEs) of a node with certain requirements. + +### 6.1.1 Modes of operation + +An ITU-T G.9992 system can operate in one of the following two modes. A unidirectional broadcasting mode (UBM) and domain based mode (DBM). + +In UBM, only unidirectional transmissions are supported. The unidirectional broadcasting node broadcasts signals, while one or more endpoint nodes receive the signals. The establishment of a domain is not needed in a UBM. + +In the DBM, the operation of an ITU-T G.9992 system shall be based on the domain, which comprises a domain master and one or more endpoint nodes that registered to the same domain master. Broadcast shall be supported in any domain. + +NOTE – The detailed specification of DBM is for further study. + +### 6.1.2 Dual-channel operation + +An ITU-T G.9992 transceiver provides two independent channel to the application entity. A low-speed channel and a high-speed channel, and it may operate on any of the two channels, or on both of the two channels simultaneously. The selection of the operation channels shall be vendor discretionary or configured by the user. + +## 6.2 Reference models + +### 6.2.1 Protocol reference model of transceiver + +The protocol reference model of an ITU-T G.9992 transceiver is presented in Figure 6-2. For each channel, it includes two main reference points. An application interface (A-interface) and the physical medium-independent interface (PMI). The two channels shares the same medium-dependent interface (MDI). For each channel, two intermediate reference points, x1 and x2, are defined in the data link layer (DLL), and two other intermediate reference points, $\alpha$ and $\delta$ , are defined in the PHY layer (Figure 6-2). + +The MDI is a physical interface defined in terms of the physical signals transmitted over a specific medium (see clause 6.2.2.3). + +The PMI interface is both medium independent and application independent. It is defined in clause 6.2.2.2 as a functional interface, in terms of functional flows and logical signals. + +The A-interface is user application-protocol specific (e.g., Ethernet, IP). The functional description of the A-interface is presented in clause 6.2.2.1. The A-interfaces of the two channels are independent. + +All intermediate reference points are independent of the type of medium and are defined as functional (logical) interfaces in terms of the functional flows and logical signals. + +![Figure 6-2: Protocol reference model of an ITU-T G.992 transceiver. The diagram shows a stack of layers on the left aligned with the OSI reference model (Network Layer, Data Link Layer, Physical Layer). The Data Link Layer contains MAC, LLC, and APC sublayers. The Physical Layer contains PCS, PMA, and PMD sublayers. On the right, the same stack is shown. Interfaces are indicated by dashed lines: A-interface between the Application entity and the APC sublayer; PMI between the MAC sublayer and the PCS sublayer; MDI between the PMD sublayer and the Transmission medium. Reference points are marked: x1 between the APC and LLC sublayers; x2 between the LLC and MAC sublayers; alpha between the PCS and PMA sublayers; delta between the PMA and PMD sublayers. A legend at the bottom left defines the sublayers: APC (Application protocol convergence), LLC (Logical link control), MAC (Medium access control), PCS (Physical coding sub-layer), PMA (Physical medium attachment), PMD (Physical medium dependent), PMI (Physical medium-independent interface), MDI (Medium-dependent interface). The diagram is labeled G.992(19)_F6-2.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 6-2: Protocol reference model of an ITU-T G.992 transceiver. The diagram shows a stack of layers on the left aligned with the OSI reference model (Network Layer, Data Link Layer, Physical Layer). The Data Link Layer contains MAC, LLC, and APC sublayers. The Physical Layer contains PCS, PMA, and PMD sublayers. On the right, the same stack is shown. Interfaces are indicated by dashed lines: A-interface between the Application entity and the APC sublayer; PMI between the MAC sublayer and the PCS sublayer; MDI between the PMD sublayer and the Transmission medium. Reference points are marked: x1 between the APC and LLC sublayers; x2 between the LLC and MAC sublayers; alpha between the PCS and PMA sublayers; delta between the PMA and PMD sublayers. A legend at the bottom left defines the sublayers: APC (Application protocol convergence), LLC (Logical link control), MAC (Medium access control), PCS (Physical coding sub-layer), PMA (Physical medium attachment), PMD (Physical medium dependent), PMI (Physical medium-independent interface), MDI (Medium-dependent interface). The diagram is labeled G.992(19)\_F6-2. + +**Figure 6-2 – Protocol reference model of an ITU-T G.992 transceiver** + +The application protocol convergence (APC) sublayer provides an interface with the application entity (AE), which operates with an application-specific protocol, such as Ethernet. + +The logical link control (LLC) sublayer coordinates transmission of nodes. + +The medium access control (MAC) sublayer controls access of the node to the medium. + +The physical coding sublayer (PCS) encapsulates transmit media access control protocol data units (MPDUs) into the PHY frame and adds PHY-related control and management overhead. The physical medium attachment (PMA) provides encoding of PHY frame content for transmission over the medium. The PMD modulates and demodulates PHY frames for transmission using undersampled pulse width modulation (UPWM) or undersampled pulse position modulation (UPPM). + +The layers above the data link layer (above the A-interface) are beyond the scope of this Recommendation. Management functions are therefore not presented in Figure 6-2. + +### 6.2.2 Interfaces – functional description + +This clause contains the functional description of the ITU-T G.992 transceiver interfaces (A, PMI, and MDI) in terms of signal flows exchanged between corresponding entities. The description does not imply any specific implementation of the transceiver interfaces. + +#### 6.2.2.1 A-interface + +The A-interface is described in terms of primitives exchanged between the AE and the DLL. There are six general types of A-interface primitives, as shown in Table 6-1. Each primitive type may consist of one or more primitives, related to control or data, respectively. Data primitives represent the data path of the A-interface, while control primitives represent the control path. The format of the application data primitives (ADPs) is application specific, determined by the AE. + +**Table 6-1 – A-interface primitive type summary** + +| Primitive type | Direction | Description | +|----------------|-----------|-------------------------------------| +| AIF_DATA.REQ | AE → DLL | Data from AE to DLL | +| AIF_DATA.CNF | DLL → AE | Data confirmation from DLL to AE | +| AIF_DATA.IND | DLL → AE | Data from DLL to AE | +| AIF_CTRL.REQ | AE → DLL | Control from AE to DLL | +| AIF_CTRL.CNF | DLL → AE | Control confirmation from DLL to AE | +| AIF_CTRL.IND | DLL → AE | Control from DLL to AE | + +#### 6.2.2.2 Physical medium-independent interface + +The physical medium-independent interface (PMI) is described in terms of primitives exchanged between the DLL and PHY layer presented in Table 6-2. The direction of each primitive flow indicates the originating entity of the primitive. Both transmit and receive data primitives are exchanged in MPDUs. + +**Table 6-2 – PMI primitive description** + +| Primitive | Direction | Description | +|--------------------|-----------|---------------------------------------------------------------| +| PMI_DATA.REQ | DLL → PHY | Flow of MPDUs for transmission | +| PMI_CTRL-RxDis.REQ | DLL → PHY | Disables receive of PHY frames | +| PMI_DATA.IND | PHY → DLL | Flow of received MPDUs | +| PMI_CTRL-ERR.IND | PHY → DLL | Error primitive that accompanies an MPDU received with errors | +| RX ENABLE | DLL → PHY | Enable receive function in the PHY layer | + +NOTE – Primitives presented in this table are exclusively for descriptive purposes and do not imply any specific implementation. + +#### 6.2.2.3 Medium-dependent interface + +Functional characteristics of the medium-dependent interface (MDI) are described by two signal flows: + +- transmit signal (TX DATA) is the flow of frames transmitted on to the medium; +- receive signal (RX DATA) is the flow of frames received from the medium. + +### 6.2.3 Functional model of an ITU-T G.992 transceiver + +The functional model of an ITU-T G.992 transceiver is presented in Figure 6-3. It addresses nodes without extended capabilities, as well as nodes with extended capabilities such as domain master, and relaying (including DAP), which differ by their MAC, LLC and upper layer functionalities. + +The PMD function depends on the channels on which the transceiver operates. It can be configured for single-channel or dual-channel operation. The PCS encapsulates transmit MPDUs into PHY frames. The transmit PHY frame is further encoded in the PMA to meet the corresponding PMD. + +![Functional model of an ITU-T G.992 transceiver diagram showing Low speed channel, High speed channel, and Medium components with various management and data primitives.](5cab96b2d23174c25919840ecd50aa48_img.jpg) + +The diagram illustrates the functional model of an ITU-T G.992 transceiver. It is divided into three main vertical sections: Low speed channel (left), High speed channel (right), and Medium (center). At the top, 'Data primitives' and 'Control primitives' are shown entering the system. The Low speed channel contains a stack of blocks: APC, LLC, and MAC. The High speed channel contains a similar stack: APC, LLC, and MAC. Both channels feed into a central 'DLL management' block. Below the DLL management is a 'PHY management' block. The Low speed channel continues with 'MPDU' (Medium Protocol Data Unit) passing through 'PCS' and 'PMA' blocks. The High speed channel also has 'MPDU' passing through 'PCS' and 'PMA' blocks. Both 'PMA' blocks feed into a large 'PMD' block at the bottom. The 'PMD' block connects to the 'Medium' via 'Tx/Rx frames'. Interface points are marked with dashed lines: 'A' at the top, 'PMI' between the MAC and PCS blocks, and 'MDI' between the PMD and the Medium. The diagram is labeled 'G.992(19)\_F6-3' at the bottom right. + +Functional model of an ITU-T G.992 transceiver diagram showing Low speed channel, High speed channel, and Medium components with various management and data primitives. + +**Figure 6-3 – Functional model of an ITU-T G.992 transceiver** + +The detailed description of the functional model of the PHY layer is presented in clause 8.1.1. The DLL is specified in clause 9. + +# 7 Profiles + +Profiles are intended to specify nodes with significantly different levels of complexity and functionality. A more complex profile is a superset of a less complex profile and shall interoperate with that profile. A node shall be classified into particular profiles according to its degree of complexity and functionality. For compliance with this Recommendation, a node is required to support one profile, at a minimum. Profiles are summarized in Table 7-1. + +**Table 7-1 – Profiles** + +| Profile name | Transmission mode | Description | +|----------------------------|--------------------------------------------------|-------------------------------------| +| Reduced-complexity profile | Single input/single output (SISO) | Only low speed channel is supported | +| | UPWM-based multiple input/multiple output (MIMO) | | +| Standard profile | SISO | Dual channels are supported | +| | UPPM-based MIMO | | + +NOTE 1 – The classification of profiles is applicable to the transmit direction only. An ITU-T G.992 node shall be capable of receiving from nodes that are classified into any profile. +NOTE 2 – Regardless of profile, if multiple TX ports are used, the node shall only implement MIMO, and if only one TX port is used, the node shall only implement SISO. + +## 7.1 Reduced-complexity profile + +Table 7-2 describes the features and valid values of parameters for the reduced-complexity profile (RCP) that differentiate it from the standard profile. + +**Table 7-2 – Features and valid parameters for the reduced-complexity profile** + +| Parameter/feature | Description | +|----------------------------|-----------------| +| Modulation | UPWM | +| Maximum number of TX ports | 4096 | +| MIMO | UPWM-based MIMO | + +## 7.2 Standard profile + +Table 7-3 describes the features and valid values of parameters for the standard profile that differentiate it from the reduced-complexity profiles. + +**Table 7-3 – Features and valid parameters for the standard profile** + +| Parameters | Description | +|----------------------------|-----------------| +| Modulation | UPWM, UPPM | +| Maximum number of TX ports | 4 | +| MIMO | UPPM-based MIMO | + +# 8 Physical layer specification + +## 8.1 SISO transmission + +### 8.1.1 Functional model of the PHY + +The functional model of the PHY is represented in Figure 8-1. The PMI and DMI are, respectively, two demarcation reference points between the PHY and MAC and between the PHY and the transmission medium. Internal reference points $\delta$ and $\alpha$ show separation between the PMD and PMA, and between the PCS and PMA, respectively. + +![Functional model of the PHY diagram showing two parallel processing paths (1 and 2) for data transmission and reception. Path 1: MPDU1 in from PMI -> PCS (PHY-frame generation) -> TX1 PHY frame at alpha-reference point -> PMA (FEC, segmentation, padding) -> TX1 symbol frames at delta-reference point -> PMD (DC mapping, preamble, modulation) -> Medium via MDI. Path 2: Medium via MDI -> PMD -> RX2 symbol frames at delta-reference point -> PMA -> RX2 PHY frame at alpha-reference point -> PCS -> MPDU2 out to PMI. Control lines include PHY management, PCS control data, PMA control data, and PMD control data.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg) + +G.992(19)\_F8-1 + +Functional model of the PHY diagram showing two parallel processing paths (1 and 2) for data transmission and reception. Path 1: MPDU1 in from PMI -> PCS (PHY-frame generation) -> TX1 PHY frame at alpha-reference point -> PMA (FEC, segmentation, padding) -> TX1 symbol frames at delta-reference point -> PMD (DC mapping, preamble, modulation) -> Medium via MDI. Path 2: Medium via MDI -> PMD -> RX2 symbol frames at delta-reference point -> PMA -> RX2 PHY frame at alpha-reference point -> PCS -> MPDU2 out to PMI. Control lines include PHY management, PCS control data, PMA control data, and PMD control data. + +**Figure 8-1 – Functional model of the PHY** + +In the transmit direction, for each channel, data enters the PHY from the MAC via the PMI in blocks of bytes called MPDUs. The incoming MPDU is mapped into a PHY frame in the PCS, encoded in the PMA, modulated in the PMD, and transmitted over the medium. If the transceiver only operates on the low speed channel, the TX symbol frames are modulated using UPWM modulation with relevant parameters, and in the PMD, a preamble is added to assist synchronization and phase compensation in the receiver. If the transceiver operates on the high speed channel, the TX symbol frames are modulated using UPPM modulation with pre-defined duty cycles (DCs). If the transceiver operates on dual channels, the TX symbol frames of the high speed channel are modulated using UPPM modulation with the DCs obtained from the DC mapping of the TX symbol frames of the low speed channel. + +In the receive direction, frames entering from the medium via the MDI are demodulated and decoded. The recovered MPDUs are forwarded to the MAC via the PMI. The recovered PHY-frame headers are processed in the PHY to extract the relevant frame parameters specified in clause 8.1.2.3. + +For unidirectional broadcasting mode, only one of the directions is enabled for a particular node. + +### 8.1.2 Physical coding sublayer + +The functional model of the PCS is presented in Figure 8-2. It is intended to describe in more detail the PCS functional block presented in Figure 8-1. + +![Functional model of PCS diagram showing transmit and receive paths between PMI, MPDU mapper/de-mapper, Header generation/processing, MUX (TDM), and PHY management.](9c6461e1e94afae4dec455e69a2ce152_img.jpg) + +The diagram illustrates the functional model of the Physical Coding Sublayer (PCS). It is divided into two main paths: transmit (left) and receive (right), separated by a vertical line representing the PHY management entity. + +Transmit path: An arrow labeled 'MPDU in' enters from the top (PMI) into an 'MPDU mapper' block. The output of the mapper goes to a 'MUX (TDM)' block. A 'Header generation' block is connected to the MPDU mapper and the MUX (TDM). The output of the MUX (TDM) is labeled 'TX PHY frame' and passes through a dashed line labeled 'α-reference point'. + +Receive path: An arrow labeled 'RX PHY frame' enters from the bottom, passing through the 'α-reference point' into a 'Header processing' block. The output of the header processing block goes to an 'MPDU de-mapper' block, which then outputs 'MPDU out' to the PMI. + +PHY management: A vertical line on the right is labeled 'PHY management'. It receives 'PCS control data' from the 'Header processing' block and sends 'PCS control data' to the 'Header generation' block. + +Reference labels: 'G.9992(19)\_F8-2' is at the bottom right, and 'PMI' is at the top left. + +Functional model of PCS diagram showing transmit and receive paths between PMI, MPDU mapper/de-mapper, Header generation/processing, MUX (TDM), and PHY management. + +**Figure 8-2 – Functional model of PCS** + +In the transmit direction, the incoming MPDU is mapped into a payload field of a PHY frame (clause 8.1.2.1) as described in clause 8.1.2.2. The PHY-frame header (clause 8.1.2.3) is then added to form a TX PHY frame. The TX PHY frame is passed across the $\alpha$ -reference point for further processing in the PMA. + +In the receive direction, the decoded PHY-frame payload and header are processed, and originally transmitted MPDUs are recovered from the payloads of received PHY frames and submitted to the PMI. Relevant control information conveyed in the PHY-frame header is processed and submitted to the PHY management entity. + +#### 8.1.2.1 PHY frame + +The format of the PHY frame is presented in Figure 8-3. The PHY frame at the $\alpha$ -reference point includes a header, and a payload. The preamble is added to the PHY frame in the PMD, as described in clause 8.1.4.1.3. The preamble is intended for synchronization, phase-error detection and nonlinear information acquisition. It also carries some control information. + +![Format of the PHY frame diagram showing a horizontal bar divided into Preamble, Header, and Payload sections.](a734898ce18e972938949637c32a34f4_img.jpg) + +The diagram shows a horizontal bar representing the PHY frame format. It is divided into three sections: 'Preamble' (red), 'Header' (blue), and 'Payload' (white). The 'Preamble' section is on the left, followed by the 'Header' section, and then the 'Payload' section on the right. + +Format of the PHY frame diagram showing a horizontal bar divided into Preamble, Header, and Payload sections. + +G.9992(19)\_F8-3 + +**Figure 8-3 – Format of the PHY frame** + +All components of the PHY frame (preamble, header and the payload) consist of an integer number of UPWM symbols. + +The length of the PHY-frame header is variable. The modulation order for the header shall be the same as the payload. + +The payload is intended to carry one or more MPDUs and possible management information. The length of a payload may vary from frame to frame, and the payload may be of zero length, which means that a PHY frame may not include the payload. + +The types of PHY frames used in this Recommendation are summarized in Table 8-1. + +**Table 8-1 – PHY frame types** + +| Type | Header | Payload | Description | Reference | +|-------|--------|---------|----------------------------------------------------------|--------------------| +| ID | √ | None | ID frame | Clause 8.1.2.3.2.1 | +| MSG-D | √ | √ | Data and management frame, including ID information. | Clause 8.1.2.3.2.2 | +| MSG-S | √ | √ | Data and management frame, not including ID information. | Clause 8.1.2.3.2.3 | + +#### 8.1.2.2 MPDU mapping + +MPDUs are passed to the PHY as an ordered sequence of bytes that are processed as an ordered string of bits from LSB to MSB within each byte. The first bit of the MPDU shall be the first transmitted bit of the payload. + +#### 8.1.2.3 PHY-frame header + +The PHY frame header is composed of a common part and a variable part. The common part contains fields that are common for all PHY frame types (FTs). The variable part contains fields according to the PHY frame type. The type is indicated by the FT field. The variable part comprises a fixed length part (FTSF\_F), a parity bit (PB), and a variable length part (FTSF\_V). The content of the common part and the fixed length part of the variable part of the PHY frame header is protected by the parity bit, the content of the second part of the variable part of the PHY frame header is protected by an 8-bit header check sequence (HCS). The PHY frame header format is defined in Table 8-2. + +**Table 8-2 – PHY frame header format** + +| Field | Octet | Bits | Description | +|--------|-------|----------|--------------------------------------------------| +| FT | 0 | [2:0] | Frame type | +| FTSF_F | | [6:3] | The first part of the frame-type specific field | +| PB | | [7] | The parity bit | +| FTSF_V | var | Variable | The second part of the frame-type specific field | +| HCS | var | [7:0] | Header check sequence | + +The ordering of bits and bytes of the PFH is detailed in clause 8.1.2.3.3. + +##### 8.1.2.3.1 Common part fields + +###### 8.1.2.3.1.1 Frame type + +The frame type (FT) field is a 3-bit field which indicates the type of PHY frame as described in Table 8-3. + +**Table 8-3 – Encoding of the FT field** + +| Frame type | Value
(b 2 b 1 b 0 ) | +|------------|----------------------------------------------------------| +| ID | 000 | +| MSG-D | 001 | +| MSG-S | 010 | +| Reserved | 011-111 | + +###### 8.1.2.3.1.2 Header check sequence + +The HCS field is intended for PHY frame verification. The HCS is an 8-bit cyclic redundancy check (CRC) and shall be computed over the FTSF\_V field of the PHY-frame header in the order they are transmitted, starting with the LSB of the first field of the FTSF\_V and ending with the MSB of the last field of the FTSF\_V. + +The HCS shall be computed using the following generator polynomial of degree 8: + +$$G(x) = x^8 + x^7 + x^4 + x^3 + x + 1$$ + +The value of the HCS shall be the remainder after the contents (treated as a polynomial where the first input bit is associated with the highest degree, $X^{\text{PHYH}-17}$ , where PHYH is the header length in bits, and the last input bit is associated with $X^0$ ) of the calculation field is multiplied by $x^8$ and then divided by $G(x)$ . + +The HCS field shall be transmitted starting with the coefficient of the highest order term. + +##### 8.1.2.3.2 Variable part fields + +This clause details the frame-type specific field (FTSF), a variable part of the PHY-frame header fields separately defined for each PHY-frame type. + +###### 8.1.2.3.2.1 ID PHY-frame type specific fields + +Table 8-4 lists the PHY-frame header fields which are specific to the ID frame type. For the ID frame type, the FTSF\_F field is composed of the ID Length field and destination ID field present indication (DPI) field; the FTSF\_V field is composed of the source ID (SID) field and an optional destination ID (DID) field. + +**Table 8-4 – ID PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-----------|-------|-------|--------------------------------------------------------------------------|----------------------| +| ID Length | 0 | [5:3] | The length of the SID and DID field | Clause 8.1.2.3.2.1.1 | +| DPI | | [6] | Destination ID field present indication | Clause 8.1.2.3.2.1.2 | +| PB | | [7] | The odd parity bit | Clause 8.1.2.3.2.1.3 | +| SID | var | var | ID of the source node | Clause 8.1.2.3.2.1.4 | +| DID | var | var | ID of the source node. This field only exists when DPI field is set to 1 | Clause 8.1.2.3.2.1.5 | + +###### 8.1.2.3.2.1.1 ID Length + +The ID length field shall contain the length of the ID of the source node. If the DID field is present, the length of the ID of the destination node shall also be indicated by the ID length field. + +The ID length field shall be set as shown in Table 8-5. + +**Table 8-5 – Value of ID length** + +| Length of ID in bits | Value
(b 2 b 1 b 0 ) | Description | +|----------------------|----------------------------------------------------------|-------------------| +| 8 | 000 | An 8-bit ID | +| 16 | 001 | A 16-bit ID | +| 32 | 010 | A 32-bit ID | +| 48 | 011 | A 48-bit ID | +| 64 | 100 | A 64-bit ID | +| Reserved | 101-111 | Reserved by ITU-T | + +###### 8.1.2.3.2.1.2 Destination ID field present indication + +If the destination ID field present indication (DPI) bit is set to zero, the DID field shall not be contained in the PHY-frame header. If the DPI bit is set to one, the DID field shall contain the ID of the destination nodes. + +###### 8.1.2.3.2.1.3 Parity bit + +The PB field is an odd parity bit that is intended for PHY frame verification. The PB field shall be set to 1, if the count of bits in FT field, ID Length and DPI field with a value of 1 is even. The PB field shall be set to 0, if the count of bits in FT field, ID Length and DPI field with a value of 1 is odd. + +###### 8.1.2.3.2.1.4 Source ID + +The SID field shall contain the ID of the source node of the PHY frame. The length of the SID is vendor discretionary, and indicated by the ID Length field. + +###### 8.1.2.3.2.1.5 Destination ID + +The DID field shall contain the ID of the destination node of the PHY frame. This field only exists when DPI field is set to 1. The length of the DID shall be the same as that of the SID, and indicated by the ID Length field. + +###### 8.1.2.3.2.2 MSG-D PHY-frame type specific fields + +Table 8-6 lists the PHY-frame header fields which are specific to the MSG-D frame type. For the MSG-D frame type, the FTSF\_F field is composed of the ID Length field and DPI field. The FTSF\_V field is composed of the SID field, an optional DID field and the PL field. + +**Table 8-6 – MSG-D PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|-----------|-------|-------|--------------------------------------------------------------------------|----------------------| +| ID length | 0 | [5:3] | The length of the SID and DID field | Clause 8.1.2.3.2.2.1 | +| DPI | | [6] | Destination ID field present indication | Clause 8.1.2.3.2.2.2 | +| PB | | [7] | The odd parity bit | Clause 8.1.2.3.2.2.3 | +| SID | var | var | ID of the source node | Clause 8.1.2.3.2.2.4 | +| DID | var | var | ID of the source node. This field only exists when DPI field is set to 1 | Clause 8.1.2.3.2.2.5 | +| PL | var | [7:0] | The length of the payload of this PHY frame | Clause 8.1.2.3.2.2.6 | + +###### **8.1.2.3.2.2.1 ID length** + +The ID length field shall be as described in clause 8.1.2.3.2.1.1. + +###### **8.1.2.3.2.2.2 Destination ID field present indication** + +The DPI field shall be as described in clause 8.1.2.3.2.1.2. + +###### **8.1.2.3.2.2.3 Parity bit** + +The PB field shall be as described in clause 8.1.2.3.2.1.3. + +###### **8.1.2.3.2.2.4 Source ID** + +The SID field shall be as described in clause 8.1.2.3.2.1.4. + +###### **8.1.2.3.2.2.5 Destination ID** + +The DID field shall be as described in clause 8.1.2.3.2.1.5. + +###### **8.1.2.3.2.2.6 Payload length (PL)** + +The PL field shall indicate the length of the payload of this PHY frame and shall contain the value of the number of bytes in the payload. It shall be represented as an 8-bit unsigned integer with valid values in the range from 0016 to FF16. + +###### **8.1.2.3.2.3 MSG-S PHY-frame type specific fields** + +Table 8-7 lists the PHY-frame header fields which are specific to the MSG-S frame type. For the ID frame type, the FTSF\_F field is composed of the Reserved field; the FTSF\_V field is composed of the PL field. + +**Table 8-7 – MSG-S PHY-frame type specific fields** + +| Field | Octet | Bits | Description | Reference | +|----------|-------|-------|---------------------------------------------|----------------------| +| Reserved | 0 | [6:3] | Reserved by ITU-T (Note) | | +| PB | | [7] | The odd parity bit | Clause 8.1.2.3.2.3.1 | +| PL | 1 | [7:0] | The length of the payload of this PHY frame | Clause 8.1.2.3.2.3.2 | + +NOTE – Bits that are reserved by ITU-T shall be set to zero by the transmitter and ignored by the receiver. + +###### 8.1.2.3.2.3.1 Parity bit (PB) + +The PB field shall be as described in clause 8.1.2.3.2.1.3. + +###### 8.1.2.3.2.3.2 Payload length + +The PL field shall be as described in clause 8.1.2.3.2.2.6. + +### 8.1.3 Physical medium attachment sublayer + +The functional model of the PMA is presented in Figure 8-4. It is intended to describe in more detail the PMA functional block presented in Figure 8-1. + +In the transmit direction, the incoming PHY frame (except for preamble) at the $\alpha$ -reference point has a format as defined in clause 8.1.2. The header and payload are segmented into an integer number of symbol frames as described in clauses 8.1.3.1 and 8.1.3.2. The obtained symbol frames of the header and the payload are submitted to the PMD (at the $\delta$ -reference point) for modulation and transmission over the medium. + +In the receive direction, the received symbol frames are concatenated and then submitted to the $\alpha$ -reference point for further processing in the PCS. + +![Figure 8-4 – Functional model of PMA sublayer. The diagram shows the flow of data through the PMA sublayer. On the left, the 'TX PHY frame' enters from the top at the 'alpha-reference point' (indicated by a dashed line). It passes through a block labeled 'Segmentation to UPWM/UPPM symbols'. Below this block, the 'delta-reference point' (another dashed line) is shown, and the output is 'TX symbol frames'. On the right, 'RX symbol frames' enter from the bottom at the 'delta-reference point', pass through a 'Pad removal' block, and exit at the 'alpha-reference point' as 'RX PHY frame'. A vertical line on the far right represents 'PHY management', which sends 'PHY control data' to both the 'Segmentation to UPWM/UPPM symbols' block and the 'Pad removal' block. The diagram is labeled 'G.9992(19)_F8-4' at the bottom right.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +Figure 8-4 – Functional model of PMA sublayer. The diagram shows the flow of data through the PMA sublayer. On the left, the 'TX PHY frame' enters from the top at the 'alpha-reference point' (indicated by a dashed line). It passes through a block labeled 'Segmentation to UPWM/UPPM symbols'. Below this block, the 'delta-reference point' (another dashed line) is shown, and the output is 'TX symbol frames'. On the right, 'RX symbol frames' enter from the bottom at the 'delta-reference point', pass through a 'Pad removal' block, and exit at the 'alpha-reference point' as 'RX PHY frame'. A vertical line on the far right represents 'PHY management', which sends 'PHY control data' to both the 'Segmentation to UPWM/UPPM symbols' block and the 'Pad removal' block. The diagram is labeled 'G.9992(19)\_F8-4' at the bottom right. + +**Figure 8-4 – Functional model of PMA sublayer** + +#### 8.1.3.1 Segmentation to UPWM symbols + +The incoming TX PHY frame shall be segmented into symbol frames in sequence according to the modulation order $m$ . The number of bits in each symbol frames shall be $b$ . TX PHY frame segmentation is illustrated in Figure 8-5. + +If the modulation order is the integral power of 2, each symbol frame will be modulated to generate one UPWM symbols. The incoming TX PHY frame shall be segmented in sequence, the frame shall + +contain $b$ bits, where $b = \log_2 m$ . $N_{sf}$ symbol frames are obtained, and each of the $N_{sf}-1$ symbol frames shall contain $b$ bits, while the last symbol frame may contain $b$ bits or less than $b$ bits. If the last symbol frame contains less than $b$ bits, it shall be padded with zeros. + +If the modulation order is not the integral power of 2, each symbol frame will be modulated to generate two UPWM symbols. The incoming TX PHY frame shall be segmented in sequence, and the first frame shall contain the first $b$ bits, and the second frame shall contain the second $b$ bits and so on, until the last symbol frame, where $b = \text{floor}(\log_2 m^2)$ . $N_{sf}$ symbol frames are obtained, and each of the first $N_{sf}-1$ symbol frames shall contain $b$ bits, while the last symbol frame may contain $b$ bits or less than $b$ bits. If the last symbol frame contains less than $b$ bits, it shall be padded with zeros. + +![Diagram of TX PHY frame segmentation for UPWM. The diagram shows a frame structure starting with 'LSB, octet 0'. The frame is divided into 'Header' and 'Payload'. The 'Header' is split into two 'b bits' segments, which correspond to 'Symbol frame 1' and 'Symbol frame 2'. The 'Payload' is also split into 'b bits' segments, with an ellipsis indicating intermediate frames. The last payload segment corresponds to 'Symbol frame N_sf-1'. A 'Padding' section is shown at the end, with an arrow pointing to 'Symbol frame N_sf'. A label 'G.9992(19)_F8-5' is at the bottom right.](552265bdbcf6d43d341fd018a9076269_img.jpg) + +Diagram of TX PHY frame segmentation for UPWM. The diagram shows a frame structure starting with 'LSB, octet 0'. The frame is divided into 'Header' and 'Payload'. The 'Header' is split into two 'b bits' segments, which correspond to 'Symbol frame 1' and 'Symbol frame 2'. The 'Payload' is also split into 'b bits' segments, with an ellipsis indicating intermediate frames. The last payload segment corresponds to 'Symbol frame N\_sf-1'. A 'Padding' section is shown at the end, with an arrow pointing to 'Symbol frame N\_sf'. A label 'G.9992(19)\_F8-5' is at the bottom right. + +**Figure 8-5 – TX PHY frame segmentation for UPWM** + +#### 8.1.3.2 Segmentation to UPPM symbols + +The incoming TX PHY frame shall be segmented into even number of symbol frames in sequence according to the following parameters: + +- 1) DC $D_i$ either determined by the m-DC mapper (see clause 8.1.4.1.1) or a pre-defined value, which is vendor discretionary; +- 2) valid data region information (see clause 8.1.4.2.3.2) of a UPPM waveform segment. + +TX PHY frame segmentation is illustrated in Figure 8-6. + +The incoming TX PHY frame shall be segmented in sequence, $2N_{sf} + 2$ symbol frames are obtained. If the symbol frame is the first symbol frame (i.e., symbol frame 1), it shall contain $(N_{ppm} - 2) \times \log_2 M$ bits, where $N_{ppm}$ and $M$ are parameters determined by valid data region information (see clause 8.1.4.2.3.2) of a UPPM waveform segment, the second symbol frame shall contain $N_{ppm} \times \log_2 M$ bits. Symbol frame No. $2n + 1$ and symbol frame No. $2n + 2$ ( $n \geq 1$ ) shall contain the same number of bits. If symbol frame No. 1 contains less than $(N_{ppm} - 2) \times \log_2 M$ bits, both symbol No. 1 and No. 2 shall be padded with zeros. If only symbol frame No. 2 contains less than $N_{ppm} \times \log_2 M$ bits, it shall be padded with zeros. If symbol frame No. $2n + 1$ ( $n \geq 1$ ) contains less than $N_{ppm} \times \log_2 M$ bits, both symbol No. $2n + 1$ and No. $2n + 2$ shall be padded with zeros. If only symbol frame No. $2n + 2$ contains less than $N_{ppm} \times \log_2 M$ bits, it shall be padded with zeros. + +![Figure 8-6 shows two diagrams, (a) and (b), illustrating TX PHY frame segmentations for UPPM. Both diagrams show a frame structure with a Header and a Payload. The Header is divided into b1 bits and b2 bits. The Payload is divided into b2Nsf1+1 bits. The frame is segmented into Symbol frames. In (a), the first two symbol frames are labeled 'Symbol frame 1' and 'Symbol frame 2'. The last two symbol frames are labeled 'Symbol frame 2Nsf1 + 1' and 'Symbol frame 2Nsf1 + 2'. In (b), the first two symbol frames are labeled 'Symbol frame 1' and 'Symbol frame 2'. The last two symbol frames are labeled 'Symbol frame 2Nsf1 + 1' and 'Symbol frame 2Nsf1 + 2'. Both diagrams show a 'Padding' area at the end of the frame. The text 'G.9992(19)_F8-6' is present at the bottom right of diagram (b).](cbdfdade780e677eb1c1aef3081ce9ef_img.jpg) + +LSB, octet 0 + +Header Payload Padding + +$b_1$ bits $b_2$ bits $b_{2N_{sf1}+1}$ bits + +Symbol frame 1 Symbol frame 2 Symbol frame $2N_{sf1} + 1$ Symbol frame $2N_{sf1} + 2$ + +a) + +LSB, octet 0 + +Header Payload Padding + +$b_1$ bits $b_2$ bits + +Symbol frame 1 Symbol frame 2 Symbol frame $2N_{sf1} + 1$ Symbol frame $2N_{sf1} + 2$ + +b) G.9992(19)\_F8-6 + +Figure 8-6 shows two diagrams, (a) and (b), illustrating TX PHY frame segmentations for UPPM. Both diagrams show a frame structure with a Header and a Payload. The Header is divided into b1 bits and b2 bits. The Payload is divided into b2Nsf1+1 bits. The frame is segmented into Symbol frames. In (a), the first two symbol frames are labeled 'Symbol frame 1' and 'Symbol frame 2'. The last two symbol frames are labeled 'Symbol frame 2Nsf1 + 1' and 'Symbol frame 2Nsf1 + 2'. In (b), the first two symbol frames are labeled 'Symbol frame 1' and 'Symbol frame 2'. The last two symbol frames are labeled 'Symbol frame 2Nsf1 + 1' and 'Symbol frame 2Nsf1 + 2'. Both diagrams show a 'Padding' area at the end of the frame. The text 'G.9992(19)\_F8-6' is present at the bottom right of diagram (b). + +**Figure 8-6 – TX PHY frame segmentations for UPPM** + +### 8.1.4 Physical medium dependent sublayer + +The functional model of the physical medium dependent (PMD) is presented in Figure 8-7. In the transmit direction, the m-DC mapper maps the incoming TX1 symbol frames to m-ary DC sequences, as specified in clause 8.1.4.1.1. If only the low speed channel is enabled, the duty cycle (DC) sequences of the UPWM preamble and the DC sequences obtained from the m-DC mapping of the incoming TX1 symbol frames are fed into a UPWM modulator where non-flickering signals are generated as described in clause 8.1.4.1.2. After that, the generated UPWM signals, which contain the preamble, header and payload (as shown in Figure 8-3), are fed into a digital light emitting diode (LED) driver, and are transmitted using visible light. Parameters of the preamble are determined by the PHY management. If two channels are enabled, the DC sequences of the prepending preamble and the DC sequences obtained from the m-DC mapping of the incoming TX1 symbol frames are fed into the UPPM modulation selector. + +The incoming TX2 symbol frames are fed into a UPPM modulator where non-flickering signals are generated as described in clause 8.1.4.2.2. The UPPM modulation selector determines the UPPM modulation scheme. The DC of the final UPPM symbol may be determined in accordance with the current m-ary DC generated by the m-DC mapper or by a predefined DC. The preamble and delimiters signals are fed into the UPPM modulator to finalize the generation of the transmit signal, which is then fed into an LED driver and transmitted using visible light. + +NOTE – Either TX1 or TX2 symbol frames may both exist or exist by themselves depending on the enabled channels. PHY management also receives the following parameters from the PMD sub-layer to assist PMA sub-layer in carrying out its function, that is, the output of m-DC mapper, VPPM modulation order or pre-defined DC value, and UPPM preamble/delimiter/valid data timing information. + +Frames are output on to the medium without inter-frame gaps. + +In the receive direction, a camera with a frame rate of $f_c$ is employed to detect and record the optical signal. The receiver exposure duration can be set to $T_e$ to receive TX1 symbol frames from low-speed channel only. The receiver exposure duration can be set to $T_e'$ to receive TX1 and TX2 symbol frames from both low-speed and high-speed channels or to receive TX2 symbol frames only from the high-speed channel. When the exposure is set to $T_e'$ , if at least two UPPM waveform segments are received in a captured video frame, data from the high-speed channel can be obtained and a DC + +generated by a *m*-DC mapper from the low-speed channel may also be received. If at least two UPPM waveform segments cannot be received, the exposure duration may be changed to $T_e$ to detect the optical signal to receive symbol frames in low-speed channel only. With the help of the preamble detection and PI extraction, the undersampled-recorded UPWM data from low-speed channel are compensated and demodulated. If at least two UPPM waveform segments are received in a captured video frame, with the help of preamble and delimiter detection, the recorded stripes from high-speed channel are processed and the obtained VMPPM (e.g., V2PPM, V4PPM or V8PPM) signal are processed and demodulated, the DC mapper generated DCs from the low-speed channel may also be obtained if both high speed and low speed channels are enabled, then processed and demodulated. The recovered symbol frames from either the low-speed or the high-speed channel are transferred to the PMA via $\delta$ -reference point. The preamble are processed and the processing result are passed to the PHY management entity. + +![Functional model of the PMD diagram showing TX1, TX2, RX1, and RX2 symbol frame processing paths, including m-DC mapper, UPWM/UPPM modulators, preamble generation/detection, and the physical medium (Digital LED driver/Camera).](043e64d41a3368d138ace3816fd26469_img.jpg) + +The diagram illustrates the functional model of the PMD. It is divided into four main processing paths: TX1 symbol frames, TX2 symbol frames, RX1 symbol frames, and RX2 symbol frames. A vertical dashed line on the right represents the PHY management entity. A horizontal dashed line at the bottom represents the Medium interface (MDI). A horizontal dashed line near the top marks the $\delta$ -reference point. + +- TX1 symbol frames:** Enter from the top, pass through an **m-DC mapper**, then a **UPWM modulator**, and finally a **UPWM preamble generation** block. This path is enclosed in a dashed box. +- TX2 symbol frames:** Enter from the top, pass through a **UPPM modulation selector**, then a **UPPM modulator**, and finally a **UPPM delimiter/preamble generation** block. This path is also enclosed in a dashed box. +- RX1 symbol frames:** Enter from the bottom (Medium) through a **Camera**, then a **UPWM preamble detection and PI extraction** block, and finally a **UPWM demodulation** block. This path is enclosed in a dashed box. +- RX2 symbol frames:** Enter from the bottom (Medium) through a **Camera**, then a **UPPM preamble detection** block, and finally a **UPPM demodulation** block. This path is also enclosed in a dashed box. + +Control signals and data flow as follows: + +- PMD control data:** Bidirectional arrows connect the PHY management entity to the RX1 and RX2 demodulation blocks. +- UPWM/UPPM Modulation:** Arrows connect the TX1 and TX2 preamble generation blocks to their respective modulators. +- UPPM Modulation:** Arrows connect the TX1 modulator and the TX2 modulation selector to the TX2 modulator. +- UPPM Modulation:** Arrows connect the TX1 modulator and the TX2 modulation selector to the TX2 delimiter/preamble generation block. +- UPPM Modulation:** Arrows connect the TX1 modulator and the TX2 modulation selector to the RX2 preamble detection block. +- UPPM Modulation:** Arrows connect the TX1 modulator and the TX2 modulation selector to the RX2 demodulation block. +- UPPM Modulation:** Arrows connect the TX1 modulator and the TX2 modulation selector to the PHY management entity. + +Functional model of the PMD diagram showing TX1, TX2, RX1, and RX2 symbol frame processing paths, including m-DC mapper, UPWM/UPPM modulators, preamble generation/detection, and the physical medium (Digital LED driver/Camera). + +Figure 8-7 – Functional model of the PMD + +#### 8.1.4.1 UPWM modulation + +##### 8.1.4.1.1 *m*-DC mapping + +*m*-DC mapping associates every group of bits into one or two DCs. Each incoming group of *b* bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be associated with one or two specific DC values as described in this clause. Support of all the specified modulation orders ( $m = 2, 3, 4, 6, 8, 12, 16, 23, 32$ ) shall be mandatory at both the transmitter and the receiver. The relationship between valid *m* and *b* is described in Table 8-8. Each group of bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be mapped on to the *m*-DC mapper with the LSB bit, *d*0, first. + +**Table 8-8 – Relationship between $m$ and $b$** + +| $m$ | $b$ | Number of associated DCs for a specific 'b' | +|-----|-----|---------------------------------------------| +| 2 | 1 | 1 | +| 3 | 3 | 2 | +| 4 | 2 | 1 | +| 6 | 5 | 2 | +| 8 | 3 | 1 | +| 12 | 7 | 2 | +| 16 | 4 | 1 | +| 23 | 9 | 2 | +| 32 | 5 | 1 | + +When transmitting a PHY frame, the transmitter shall first obtain DCs for preamble, header and payload (if payload exists), respectively, which may be generated with one or more specific modulation orders. + +NOTE – The payload may be not present in some PHY frames, for example, in the ID frame. + +###### **8.1.4.1.1.1 $m$ -DC mapping when $m$ is the integral power of 2** + +If the modulation order $m$ is the integral power of 2, each incoming group of $b$ bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be associated with one specific value of DC, where $b = \log_2 m$ . DC mapping for $m = 2$ is presented in Table 8-9. + +**Table 8-9 – Mapping for $m = 2$** + +| Bit $d_0$ | DC | +|-----------|-------| +| 0 | 33.3% | +| 1 | 66.7% | + +DC mapping for $m = 4$ is presented in Table 8-10. + +**Table 8-10 – Mapping for $m = 4$** + +| Bit $d_1$ | Bit $d_0$ | DC | +|-----------|-----------|-----| +| 0 | 0 | 20% | +| 0 | 1 | 40% | +| 1 | 0 | 60% | +| 1 | 1 | 80% | + +DC mapping for $m = 8$ is presented in Table 8-11. + +**Table 8-11 – Mapping for $m = 8$** + +| Bit d_2 | Bit d_1 | Bit d_0 | DC | +|-----------------------------|-----------------------------|-----------------------------|-----------| +| 0 | 0 | 0 | 11.1% | +| 0 | 0 | 1 | 22.2% | +| 0 | 1 | 0 | 33.3% | +| 0 | 1 | 1 | 44.4% | +| 1 | 0 | 0 | 55.6% | +| 1 | 0 | 1 | 66.7% | +| 1 | 1 | 0 | 77.8% | +| 1 | 1 | 1 | 88.9% | + +DC mapping for $m = 16$ is presented in Table 8-12. + +**Table 8-12 – Mapping for $m = 16$** + +| Bit d_3 | Bit d_2 | Bit d_1 | Bit d_0 | DC | +|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------| +| 0 | 0 | 0 | 0 | 5.9% | +| 0 | 0 | 0 | 1 | 11.8% | +| 0 | 0 | 1 | 0 | 17.6% | +| 0 | 0 | 1 | 1 | 23.5% | +| 0 | 1 | 0 | 0 | 29.4% | +| 0 | 1 | 0 | 1 | 35.3% | +| 0 | 1 | 1 | 0 | 41.2% | +| 0 | 1 | 1 | 1 | 47.1% | +| 1 | 0 | 0 | 0 | 52.9% | +| 1 | 0 | 0 | 1 | 58.8% | +| 1 | 0 | 1 | 0 | 64.7% | +| 1 | 0 | 1 | 1 | 70.6% | +| 1 | 1 | 0 | 0 | 76.5% | +| 1 | 1 | 0 | 1 | 82.4% | +| 1 | 1 | 1 | 0 | 88.2% | +| 1 | 1 | 1 | 1 | 94.1% | + +DC mapping for $m = 32$ is presented in Table 8-13. + +**Table 8-13 – Mapping for $m = 32$** + +| Bit d_4 | Bit d_3 | Bit d_2 | Bit d_1 | Bit d_0 | DC | +|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------| +| 0 | 0 | 0 | 0 | 0 | 3.0% | +| 0 | 0 | 0 | 0 | 1 | 6.1% | +| 0 | 0 | 0 | 1 | 0 | 9.1% | +| 0 | 0 | 0 | 1 | 1 | 12.1% | +| 0 | 0 | 1 | 0 | 0 | 15.2% | +| 0 | 0 | 1 | 0 | 1 | 18.2% | + +**Table 8-13 – Mapping for $m = 32$** + +| Bit $d_4$ | Bit $d_3$ | Bit $d_2$ | Bit $d_1$ | Bit $d_0$ | DC | +|-----------|-----------|-----------|-----------|-----------|-------| +| 0 | 0 | 1 | 1 | 0 | 21.2% | +| 0 | 0 | 1 | 1 | 1 | 24.2% | +| 0 | 1 | 0 | 0 | 0 | 27.3% | +| 0 | 1 | 0 | 0 | 1 | 30.3% | +| 0 | 1 | 0 | 1 | 0 | 33.3% | +| 0 | 1 | 0 | 1 | 1 | 36.4% | +| 0 | 1 | 1 | 0 | 0 | 39.4% | +| 0 | 1 | 1 | 0 | 1 | 42.4% | +| 0 | 1 | 1 | 1 | 0 | 45.5% | +| 0 | 1 | 1 | 1 | 1 | 48.5% | +| 1 | 0 | 0 | 0 | 0 | 51.5% | +| 1 | 0 | 0 | 0 | 1 | 54.5% | +| 1 | 0 | 0 | 1 | 0 | 57.6% | +| 1 | 0 | 0 | 1 | 1 | 60.6% | +| 1 | 0 | 1 | 0 | 0 | 63.6% | +| 1 | 0 | 1 | 0 | 1 | 66.7% | +| 1 | 0 | 1 | 1 | 0 | 69.7% | +| 1 | 0 | 1 | 1 | 1 | 72.7% | +| 1 | 1 | 0 | 0 | 0 | 75.8% | +| 1 | 1 | 0 | 0 | 1 | 78.8% | +| 1 | 1 | 0 | 1 | 0 | 81.8% | +| 1 | 1 | 0 | 1 | 1 | 84.8% | +| 1 | 1 | 1 | 0 | 0 | 87.9% | +| 1 | 1 | 1 | 0 | 1 | 90.9% | +| 1 | 1 | 1 | 1 | 0 | 93.9% | +| 1 | 1 | 1 | 1 | 1 | 97.0% | + +###### 8.1.4.2.1.2 $m$ -DC mapping when $m$ is non-integral power of 2 + +If the modulation order $m$ is not the integral power of 2, each incoming group of $b$ bits $\{d_{b-1}, d_{b-2}, \dots, d_0\}$ shall be associated with two specific value of DC according to the mapping rules specified in this clause, where $b = \text{floor}(\log_2 m^2)$ . Each incoming group of $b$ bits shall be modulated to two consecutive UPWM symbols. DC I and DC II shall be used to generate the two UPWM symbols respectively. In the mapping rules, $2^b$ of the $m^2$ combinations of DCs are adopted. DC mapping for $m = 3$ is presented in Table 8-14. + +**Table 8-14 – Mapping for $m = 3$** + +| Bit d_2 | Bit d_1 | Bit d_0 | DC (I) | DC (II) | +|-----------------------------|-----------------------------|-----------------------------|---------------|----------------| +| 0 | 0 | 0 | 25% | 25% | +| 0 | 0 | 1 | 25% | 50% | +| 0 | 1 | 0 | 25% | 75% | +| 0 | 1 | 1 | 50% | 25% | +| 1 | 0 | 0 | 50% | 50% | +| 1 | 0 | 1 | 50% | 75% | +| 1 | 1 | 0 | 75% | 25% | +| 1 | 1 | 1 | 75% | 50% | + +DC mapping for $m = 6$ is presented in Table 8-15. + +**Table 8-15 – Mapping for $m = 6$** + +| Bit d_4 | Bit d_3 | Bit d_2 | Bit d_1 | Bit d_0 | DC (I) | DC (II) | +|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|---------------|----------------| +| 0 | 0 | 0 | 0 | 0 | 14.3% | 14.3% | +| 0 | 0 | 0 | 0 | 1 | 14.3% | 28.6% | +| 0 | 0 | 0 | 1 | 0 | 14.3% | 42.9% | +| 0 | 0 | 0 | 1 | 1 | 14.3% | 57.1% | +| 0 | 0 | 1 | 0 | 0 | 14.3% | 71.4% | +| 0 | 0 | 1 | 0 | 1 | 14.3% | 85.7% | +| 0 | 0 | 1 | 1 | 0 | 28.6% | 14.3% | +| 0 | 0 | 1 | 1 | 1 | 28.6% | 28.6% | +| 0 | 1 | 0 | 0 | 0 | 28.6% | 42.9% | +| 0 | 1 | 0 | 0 | 1 | 28.6% | 57.1% | +| 0 | 1 | 0 | 1 | 0 | 28.6% | 71.4% | +| 0 | 1 | 0 | 1 | 1 | 28.6% | 85.7% | +| 0 | 1 | 1 | 0 | 0 | 42.9% | 14.3% | +| 0 | 1 | 1 | 0 | 1 | 42.9% | 28.6% | +| 0 | 1 | 1 | 1 | 0 | 42.9% | 42.9% | +| 0 | 1 | 1 | 1 | 1 | 42.9% | 57.1% | +| 1 | 0 | 0 | 0 | 0 | 42.9% | 71.4% | +| 1 | 0 | 0 | 0 | 1 | 42.9% | 85.7% | +| 1 | 0 | 0 | 1 | 0 | 57.1% | 14.3% | +| 1 | 0 | 0 | 1 | 1 | 57.1% | 28.6% | +| 1 | 0 | 1 | 0 | 0 | 57.1% | 42.9% | +| 1 | 0 | 1 | 0 | 1 | 57.1% | 57.1% | +| 1 | 0 | 1 | 1 | 0 | 57.1% | 71.4% | +| 1 | 0 | 1 | 1 | 1 | 57.1% | 85.7% | +| 1 | 1 | 0 | 0 | 0 | 71.4% | 14.3% | +| 1 | 1 | 0 | 0 | 1 | 71.4% | 28.6% | +| 1 | 1 | 0 | 1 | 0 | 71.4% | 42.9% | + +**Table 8-15 – Mapping for $m = 6$** + +| Bit $d_4$ | Bit $d_3$ | Bit $d_2$ | Bit $d_1$ | Bit $d_0$ | DC (I) | DC (II) | +|-----------|-----------|-----------|-----------|-----------|--------|---------| +| 1 | 1 | 0 | 1 | 1 | 71.4% | 57.1% | +| 1 | 1 | 1 | 0 | 0 | 71.4% | 71.4% | +| 1 | 1 | 1 | 0 | 1 | 71.4% | 85.7% | +| 1 | 1 | 1 | 1 | 0 | 85.7% | 14.3% | +| 1 | 1 | 1 | 1 | 1 | 85.7% | 28.6% | + +DC mapping for $m = 12$ is presented in Table 8-16. + +**Table 8-16 – Mapping for $m = 12$** + +| Bits
$d_6 d_5 d_4 d_3 d_2 d_1 d_0$ | DC (I) | DC (II) | Bits
$d_6 d_5 d_4 d_3 d_2 d_1 d_0$ | DC (I) | DC (II) | +|---------------------------------------|--------|---------|---------------------------------------|--------|---------| +| 0000000 | 7.7% | 7.7% | 1000000 | 46.2% | 38.5% | +| 0000001 | 7.7% | 15.4% | 1000001 | 46.2% | 46.2% | +| 0000010 | 7.7% | 23.1% | 1000010 | 46.2% | 53.8% | +| 0000011 | 7.7% | 30.8% | 1000011 | 46.2% | 61.5% | +| 0000100 | 7.7% | 38.5% | 1000100 | 46.2% | 69.2% | +| 0000101 | 7.7% | 46.2% | 1000101 | 46.2% | 76.9% | +| 0000110 | 7.7% | 53.8% | 1000110 | 46.2% | 84.6% | +| 0000111 | 7.7% | 61.5% | 1000111 | 46.2% | 92.3% | +| 0001000 | 7.7% | 69.2% | 1001000 | 53.8% | 7.7% | +| 0001001 | 7.7% | 76.9% | 1001001 | 53.8% | 15.4% | +| 0001010 | 7.7% | 84.6% | 1001010 | 53.8% | 23.1% | +| 0001011 | 7.7% | 92.3% | 1001011 | 53.8% | 30.8% | +| 0001100 | 15.4% | 7.7% | 1001100 | 53.8% | 38.5% | +| 0001101 | 15.4% | 15.4% | 1001101 | 53.8% | 46.2% | +| 0001110 | 15.4% | 23.1% | 1001110 | 53.8% | 53.8% | +| 0001111 | 15.4% | 30.8% | 1001111 | 53.8% | 61.5% | +| 0010000 | 15.4% | 38.5% | 1010000 | 53.8% | 69.2% | +| 0010001 | 15.4% | 46.2% | 1010001 | 53.8% | 76.9% | +| 0010010 | 15.4% | 53.8% | 1010010 | 53.8% | 84.6% | +| 0010011 | 15.4% | 61.5% | 1010011 | 53.8% | 92.3% | +| 0010100 | 15.4% | 69.2% | 1010100 | 61.5% | 7.7% | +| 0010101 | 15.4% | 76.9% | 1010101 | 61.5% | 15.4% | +| 0010110 | 15.4% | 84.6% | 1010110 | 61.5% | 23.1% | +| 0010111 | 15.4% | 92.3% | 1010111 | 61.5% | 30.8% | +| 0011000 | 23.1% | 7.7% | 1011000 | 61.5% | 38.5% | +| 0011001 | 23.1% | 15.4% | 1011001 | 61.5% | 46.2% | +| 0011010 | 23.1% | 23.1% | 1011010 | 61.5% | 53.8% | + +**Table 8-16 – Mapping for $m = 12$** + +| Bits
$d_6 d_5 d_4 d_3 d_2 d_1 d_0$ | DC (I) | DC (II) | Bits
$d_6 d_5 d_4 d_3 d_2 d_1 d_0$ | DC (I) | DC (II) | +|---------------------------------------|--------|---------|---------------------------------------|--------|---------| +| 0011011 | 23.1% | 30.8% | 1011011 | 61.5% | 61.5% | +| 0011100 | 23.1% | 38.5% | 1011100 | 61.5% | 69.2% | +| 0011101 | 23.1% | 46.2% | 1011101 | 61.5% | 76.9% | +| 0011110 | 23.1% | 53.8% | 1011110 | 61.5% | 84.6% | +| 0011111 | 23.1% | 61.5% | 1011111 | 61.5% | 92.3% | +| 0100000 | 23.1% | 69.2% | 1100000 | 69.2% | 7.7% | +| 0100001 | 23.1% | 76.9% | 1100001 | 69.2% | 15.4% | +| 0100010 | 23.1% | 84.6% | 1100010 | 69.2% | 23.1% | +| 0100011 | 23.1% | 92.3% | 1100011 | 69.2% | 30.8% | +| 0100100 | 30.8% | 7.7% | 1100100 | 69.2% | 38.5% | +| 0100101 | 30.8% | 15.4% | 1100101 | 69.2% | 46.2% | +| 0100110 | 30.8% | 23.1% | 1100110 | 69.2% | 53.8% | +| 0100111 | 30.8% | 30.8% | 1100111 | 69.2% | 61.5% | +| 0101000 | 30.8% | 38.5% | 1101000 | 69.2% | 69.2% | +| 0101001 | 30.8% | 46.2% | 1101001 | 69.2% | 76.9% | +| 0101010 | 30.8% | 53.8% | 1101010 | 69.2% | 84.6% | +| 0101011 | 30.8% | 61.5% | 1101011 | 69.2% | 92.3% | +| 0101100 | 30.8% | 69.2% | 1101100 | 76.9% | 7.7% | +| 0101101 | 30.8% | 76.9% | 1101101 | 76.9% | 15.4% | +| 0101110 | 30.8% | 84.6% | 1101110 | 76.9% | 23.1% | +| 0101111 | 30.8% | 92.3% | 1101111 | 76.9% | 30.8% | +| 0110000 | 38.5% | 7.7% | 1110000 | 76.9% | 38.5% | +| 0110001 | 38.5% | 15.4% | 1110001 | 76.9% | 46.2% | +| 0110010 | 38.5% | 23.1% | 1110010 | 76.9% | 53.8% | +| 0110011 | 38.5% | 30.8% | 1110011 | 76.9% | 61.5% | +| 0110100 | 38.5% | 38.5% | 1110100 | 76.9% | 69.2% | +| 0110101 | 38.5% | 46.2% | 1110101 | 76.9% | 76.9% | +| 0110110 | 38.5% | 53.8% | 1110110 | 76.9% | 84.6% | +| 0110111 | 38.5% | 61.5% | 1110111 | 76.9% | 92.3% | +| 0111000 | 38.5% | 69.2% | 1111000 | 84.6% | 7.7% | +| 0111001 | 38.5% | 76.9% | 1111001 | 84.6% | 15.4% | +| 0111010 | 38.5% | 84.6% | 1111010 | 84.6% | 23.1% | +| 0111011 | 38.5% | 92.3% | 1111011 | 84.6% | 30.8% | +| 0111100 | 46.2% | 7.7% | 1111100 | 84.6% | 38.5% | +| 0111101 | 46.2% | 15.4% | 1111101 | 84.6% | 46.2% | +| 0111110 | 46.2% | 23.1% | 1111110 | 84.6% | 53.8% | +| 0111111 | 46.2% | 30.8% | 1111111 | 84.6% | 61.5% | + +For $m = 23$ , each incoming $b = 9$ bits are represented by a value (Value\_Bits) from 0 to 511. The DC I and DC II shall be calculated as presented in Table 8-17 and Table 8-18. + +**Table 8-17 – Mapping for $m = 23$ (DC I)** + +| floor (Value_Bits/23) | DC (I) | +|------------------------------|---------------| +| 0 | 4.2% | +| 1 | 8.3% | +| 2 | 12.5% | +| 3 | 16.7% | +| 4 | 20.8% | +| 5 | 25.0% | +| 6 | 29.2% | +| 7 | 33.3% | +| 8 | 37.5% | +| 9 | 41.7% | +| 10 | 45.8% | +| 11 | 50.0% | +| 12 | 54.2% | +| 13 | 58.3% | +| 14 | 62.5% | +| 15 | 66.7% | +| 16 | 70.8% | +| 17 | 75.0% | +| 18 | 79.2% | +| 19 | 83.3% | +| 20 | 87.5% | +| 21 | 91.7% | +| 22 | 95.8% | + +**Table 8-18 – Mapping for $m = 23$ (DC II)** + +| mod (Value_Bits, 23) | DC (II) | +|-----------------------------|----------------| +| 0 | 4.2% | +| 1 | 8.3% | +| 2 | 12.5% | +| 3 | 16.7% | +| 4 | 20.8% | +| 5 | 25.0% | +| 6 | 29.2% | +| 7 | 33.3% | +| 8 | 37.5% | + +**Table 8-18 – Mapping for $m = 23$ (DC II)** + +| mod (Value_Bits, 23) | DC (II) | +|-----------------------------|----------------| +| 9 | 41.7% | +| 10 | 45.8% | +| 11 | 50.0% | +| 12 | 54.2% | +| 13 | 58.3% | +| 14 | 62.5% | +| 15 | 66.7% | +| 16 | 70.8% | +| 17 | 75.0% | +| 18 | 79.2% | +| 19 | 83.3% | +| 20 | 87.5% | +| 21 | 91.7% | +| 22 | 95.8% | + +##### **8.1.4.1.2 UPWM modulator** + +The UPWM modulator shall generate a UPWM symbol for an incoming DC, for example, once a DC $D_i$ is received, a UPWM symbol $S_i$ shall be generated. + +The UPWM modulator consists of the following major parts: complementary operation, PWM segment generation, repetition and concatenation. The incoming signal to the modulator in the present frame with an index $i$ , is a DC value generated by the m-DC mapping module, as described in clause 8.1.4.1, or the preamble generator, as described in clause 8.1.4.1.3. The DC value $D_i$ and the complementary DC value $1-D_i$ are used for generating two PWM waveform segments respectively. The two PWM waveform segments are concatenated and duplicated to form a UPWM symbol $S_i$ . The functional diagram of an UPWM modulator is presented in Figure 8-8. + +![Functional diagram of the UPWM modulator. The input 'Duty cycle (Di)' enters a block labeled 'UPWM modulator'. Inside, the signal splits: one path goes directly to 'PWM segment generation' as Di, and the other goes through 'Complementary operation' to produce 1-Di, which also enters 'PWM segment generation'. The output of 'PWM segment generation' goes to 'Concatenation and repetition', which produces the final output Si. A label G.9992(19)_F8-8 is at the bottom right.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +Functional diagram of the UPWM modulator. The input 'Duty cycle (Di)' enters a block labeled 'UPWM modulator'. Inside, the signal splits: one path goes directly to 'PWM segment generation' as Di, and the other goes through 'Complementary operation' to produce 1-Di, which also enters 'PWM segment generation'. The output of 'PWM segment generation' goes to 'Concatenation and repetition', which produces the final output Si. A label G.9992(19)\_F8-8 is at the bottom right. + +**Figure 8-8 – Functional diagram of the UPWM modulator** + +###### **8.1.4.1.2.1 Complementary operation** + +For a given $D$ , the complementary operation is defined as: $1-D$ . The complementary DC $1-D_i$ shall be obtained by imposing the complementary operation on the incoming DC $D_i$ . + +###### 8.1.4.1.2.2 PWM segment generation + +Two segments of PWM waveform shall be generated using the input DC $D_i$ and the complementary DC $1-D_i$ , respectively. Each segment of PWM waveform shall have the same duration of $T_s$ , and shall contain multiple basic PWM cycles that have a duration of $T_p$ and a DC of $D_i$ or $1-D_i$ . + +Particularly, $T_s$ shall be equal to $T_c / (2k)$ , where $T_c$ is the reciprocal of the camera's frame rate $f_c$ , which shall be fixed to 120 fps, $k$ is an integer ( $k \geq 1$ ) to make sure $T_s$ is less than 5 ms. $T_p$ shall be lower or equal to $T_c / 5$ , which means that when a camera is used to shoot video of an LED which is emitting UPWM signal, the camera could receive at least 10 basic PWM cycles during each exposure period $T_c$ . + +NOTE – If a return channel exists, the frame rate of the camera of the receiver node can be adjusted on demand. The mechanism for frame rate negotiation is for further study. + +###### 8.1.4.1.2.3 Concatenation and repetition + +The two segments of PWM waveform, each of which has a duration of $T_s$ and a DC of $D_i$ and $1-D_i$ respectively, shall be concatenated sequentially, and then shall be repeated $k$ times. Finally, a UPWM symbol with a duration of $T_c$ shall be formed. Each UPWM symbol consists of $k$ segments of PWM waveform with a DC of $D_i$ , and $k$ segments of PWM waveform with a DC of $1-D_i$ . Each PWM waveform segment shall have the same duration of $T_c / (2k)$ , and each PWM waveform segment with a DC of $D_i$ shall be followed by a PWM waveform segment with a DC of $1-D_i$ . + +The $2k$ PWM segments forms a UPWM symbol with a duration of $T_c$ . The generated UPWM symbols are then transmitted via the LED of the transmitter. + +##### 8.1.4.1.3 UPWM preamble signal + +The preamble is prepended to every PHY frame defined in clause 8.1.2.1. It is intended to assist the receiver in detecting phase error, synchronizing to the frame boundaries, and acquiring the nonlinear information and physical layer parameters such as modulation order. + +Figure 8-9 shows the general structure of the preamble. The preamble is composed of three sections, both the first section and the third section include one UPWM symbol, while the second section includes $m$ UPWM symbols, where $m$ is the modulation order for the following part of the PHY frame. + +![Diagram of the preamble structure showing three sections: First section (S0), Second section (S1, S2, ..., Sm), and Third section (Sm+1).](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +The diagram illustrates the structure of the preamble. It is a horizontal sequence of cells. The first row contains labels: S0, S1, S2, ..., Sm, Sm+1. The second row contains labels: First section, Second section, Third section. The 'First section' label is under S0. The 'Second section' label is under S1, S2, ..., Sm. The 'Third section' label is under Sm+1. Below the labels, there are double-headed arrows indicating the extent of each section: the first arrow is under S0, the second is under S1, S2, ..., Sm, and the third is under Sm+1. The text 'G.9992(19)\_F8-9' is located at the bottom right of the diagram. + +| | | | | | | +|---------------|----------------|----|-----|----|---------------| +| S0 | S1 | S2 | ... | Sm | Sm+1 | +| First section | Second section | | | | Third section | + +G.9992(19)\_F8-9 + +Diagram of the preamble structure showing three sections: First section (S0), Second section (S1, S2, ..., Sm), and Third section (Sm+1). + +Figure 8-9 – The general structure of the preamble + +The DCs for generating each UPWM symbol of the preamble for each modulation order are presented in Table 8-19. The UPWM symbols of preamble shall be generated as specified in clause 8.1.4.2. + +**Table 8-19 – The structure of the preamble** + +| | First section | Second section | Third section | +|------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| +| m=2 | 0% | 33.3%, 66.7% | 100% | +| m=3 | 0% | 25%, 50%, 75% | 100% | +| m=4 | 0% | 20%, 40%, 60%, 80% | 100% | +| m=6 | 0% | 14.3%, 28.6%, 42.9%, 57.1%, 71.4%, 85.7% | 100% | +| m=8 | 0% | 11.1%, 22.2%, 33.3%, 44.4%, 55.6%, 66.7%, 77.8%, 88.9% | 100% | +| m=12 | 0% | 7.7%, 15.4%, 23.1%, 30.8%, 38.5%, 46.2%, 53.8%, 61.5%, 69.2%, 76.9%, 84.6%, 92.3% | 100% | +| m=16 | 0% | 5.9%, 11.8%, 17.6%, 23.5%, 29.4%, 35.3%, 41.2%, 47.1%, 52.9%, 58.8%, 64.7%, 70.6%, 76.5%, 82.4%, 88.2%, 94.1% | 100% | +| m=23 | 0% | 4.2%, 8.3%, 12.5%, 16.7%, 20.8%, 25.0%, 29.2%, 33.3%, 37.5%, 41.7%, 45.8%, 50.0%, 54.2%, 58.3%, 62.5%, 66.7%, 70.8%, 75.0%, 79.2%, 83.3%, 87.5%, 91.7%, 95.8% | 100% | +| m=32 | 0% | 3.0%, 6.1%, 9.1%, 12.1%, 15.2%, 18.2%, 1.2%, 24.2%, 27.3%, 30.3%, 33.3%, 36.4%, 39.4%, 42.4%, 45.5%, 48.5%, 51.5%, 54.5%, 57.6%, 60.6%, 63.6%, 66.7%, 69.7%, 72.7%, 75.8%, 78.8%, 81.8%, 84.8%, 87.9%, 90.9%, 93.9%, 97.0% | 100% | + +#### 8.1.4.2 UPPM modulation + +The UPPM modulator shall generate UPPM symbols for incoming symbol frames from only the high speed channel or incoming symbol frames from both the high speed and the low speed channels, depending on the enabled channels. + +For the generation of each UPPM symbol, the transmitter shall first determine a modulation scheme according to a DC $D_i$ . If only the high speed channel is enabled, the DC $D_i$ shall be a pre-defined value, which is vendor discretionary. If both high speed and low speed channels are enabled, the DC $D_i$ shall be generated by the m-DC mapper according to the incoming symbol frames from the low speed channel. + +Subsequently, according to the determined modulation scheme, the transmitter shall generate a UPPM symbol which shall contain even number of waveform segments with equal duration. The TX symbol frame of the high speed channel shall be divided into two parts which shall be conveyed by the first two adjacent waveform segments (i.e., the first and the second waveform segments) respectively. The following waveform segments are repetition of the first and the second waveform segments. All segments with an odd number shall be a waveform with the determined modulation scheme and an average DC of $D_i$ . All segments with an even number shall be a waveform with the same determined modulation scheme and an average DC of $1-D_i$ . + +##### 8.1.4.2.1 Determination of modulation schemes for UPPM + +The modulation schemes for UPPM waveform segments shall be determined by the corresponding DC $D_i$ generated by the m-DC mapper or the predefined DC $D_i$ according to the following criteria: + +- If $D_i$ falls within the interval of (0% ~ 12.5%) or [87.5% ~ 100%), V8PPM shall be adopted; + +- If $D_i$ falls within the interval of (12.5% ~ 25%) or [75% ~ 87.5%), V4PPM shall be adopted; +- If $D_i$ falls within the interval of (25% ~ 75%), V2PPM shall be adopted. + +###### 8.1.4.2.1.1 VMPPM modulation scheme + +Each generated symbol with different modulation schemes shall have a constant time duration of $T_{ppm}$ , and contain only one positive square pulse if the DC of this symbol is lower than or equals to 50%, or one negative square pulse if the DC of this symbol is higher than 50%. Each generated symbol with different modulation schemes shall be divided into 2, 4, or 8 time slots depending on the determined modulation scheme, and one square pulse shall be placed in one of the adjacent time slots to represent the 1, 2 or 3 bits base-band information data if V2PPM, V4PPM or V8PPM is adopted, respectively. + +If the DC $D_i$ or $D_i'$ , which is lower than or equals to 50%, varies within the defined range, the pulse rising edge shall be fixed at the beginning of one of the time slots, while the pulse width may shrink by shifting the falling edge left or right. Otherwise, if the DC $D_i$ or $D_i'$ , which is larger than 50%, varies within the defined range, the symbol shall be generated by flipping a symbol generated by a certain modulation scheme determined by $D_i$ or $D_i'$ with a complementary DC of $1-D_i$ or $1-D_i'$ in the up-down direction. + +An example of the VMPPM modulation is presented in Figure 8-9.1. + +![Figure 8-9.1: Examples of waveforms with different duty cycles of (a) V2PPM, (b) V4PPM, and (c) V8PPM. The figure consists of three sub-tables (a, b, and c) showing various pulse-width modulation waveforms for different bit values and duty cycle percentages. Waveform for (0) at 50% duty cycle: high then low. Waveform for (1) at 50% duty cycle: low then high. Waveform for (0) at 40% duty cycle: high then low. Waveform for (1) at 40% duty cycle: low then high. Waveform for (0) at 60% duty cycle: high then low. Waveform for (1) at 60% duty cycle: low then high. Waveform for (0, 0) at 25% duty cycle. Waveform for (0, 1) at 25% duty cycle. Waveform for (1, 0) at 25% duty cycle. Waveform for (1, 1) at 25% duty cycle. Waveform for (0, 0) at 15% duty cycle. Waveform for (0, 1) at 15% duty cycle. Waveform for (1, 0) at 15% duty cycle. Waveform for (1, 1) at 15% duty cycle. Waveform for (0, 0) at 85% duty cycle. Waveform for (0, 1) at 85% duty cycle. Waveform for (1, 0) at 85% duty cycle. Waveform for (1, 1) at 85% duty cycle. Waveform for (0, 0, 0) at 12.5% duty cycle. Waveform for (0, 0, 1) at 12.5% duty cycle. Waveform for (1, 1, 0) at 12.5% duty cycle. Waveform for (1, 1, 1) at 12.5% duty cycle. Waveform for (0, 0, 0) at 10% duty cycle. Waveform for (0, 0, 1) at 10% duty cycle. Waveform for (1, 1, 0) at 10% duty cycle. Waveform for (1, 1, 1) at 10% duty cycle. Waveform for (0, 0, 0) at 90% duty cycle. Waveform for (0, 0, 1) at 90% duty cycle. Waveform for (1, 1, 0) at 90% duty cycle. Waveform for (1, 1, 1) at 90% duty cycle.](bd4a5cf22b8d8060c4bf3577beb30df8_img.jpg) + +(a) + +| | (0) | (1) | +|-----|-----|-----| +| 50% | | | +| 40% | | | +| 60% | | | + +(b) + +| | (0, 0) | (0, 1) | (1, 0) | (1, 1) | +|-----|--------|--------|--------|--------| +| 25% | | | | | +| 15% | | | | | +| 85% | | | | | + +(c) + +| | (0, 0, 0) | (0, 0, 1) | ... | (1, 1, 0) | (1, 1, 1) | +|-------|-----------|-----------|-----|-----------|-----------| +| 12.5% | | | ... | | | +| 10% | | | ... | | | +| 90% | | | ... | | | + +G.9992(19)\_F8-9.1 + +Figure 8-9.1: Examples of waveforms with different duty cycles of (a) V2PPM, (b) V4PPM, and (c) V8PPM. The figure consists of three sub-tables (a, b, and c) showing various pulse-width modulation waveforms for different bit values and duty cycle percentages. Waveform for (0) at 50% duty cycle: high then low. Waveform for (1) at 50% duty cycle: low then high. Waveform for (0) at 40% duty cycle: high then low. Waveform for (1) at 40% duty cycle: low then high. Waveform for (0) at 60% duty cycle: high then low. Waveform for (1) at 60% duty cycle: low then high. Waveform for (0, 0) at 25% duty cycle. Waveform for (0, 1) at 25% duty cycle. Waveform for (1, 0) at 25% duty cycle. Waveform for (1, 1) at 25% duty cycle. Waveform for (0, 0) at 15% duty cycle. Waveform for (0, 1) at 15% duty cycle. Waveform for (1, 0) at 15% duty cycle. Waveform for (1, 1) at 15% duty cycle. Waveform for (0, 0) at 85% duty cycle. Waveform for (0, 1) at 85% duty cycle. Waveform for (1, 0) at 85% duty cycle. Waveform for (1, 1) at 85% duty cycle. Waveform for (0, 0, 0) at 12.5% duty cycle. Waveform for (0, 0, 1) at 12.5% duty cycle. Waveform for (1, 1, 0) at 12.5% duty cycle. Waveform for (1, 1, 1) at 12.5% duty cycle. Waveform for (0, 0, 0) at 10% duty cycle. Waveform for (0, 0, 1) at 10% duty cycle. Waveform for (1, 1, 0) at 10% duty cycle. Waveform for (1, 1, 1) at 10% duty cycle. Waveform for (0, 0, 0) at 90% duty cycle. Waveform for (0, 0, 1) at 90% duty cycle. Waveform for (1, 1, 0) at 90% duty cycle. Waveform for (1, 1, 1) at 90% duty cycle. + +**Figure 8-9.1 – Examples of waveforms with different duty cycles of (a) V2PPM, (b) V4PPM, and (c) V8PPM** + +##### 8.1.4.2.2 UPPM modulator + +The UPPM modulator consists of the following major parts: complementary operation, UPPM waveform segment generation, repetition and concatenation. There shall be four inputs for the UPPM modulator, which are UPPM DC, a selected VMPPM scheme (e.g., V2PPM, V4PPM or V8PPM), TX symbol frames of the high speed channel and UPPM delimiter/preamble which is described in clause 8.1.4.2.3. The functional diagram of a UPPM modulator is presented in Figure 8-10. + +In order to provide compatibility with UPWM and support non-flickering communication, the total number of UPPM waveform segments with odd number in a UPPM symbol shall be equal to that of the UPPM waveform segments with even number during the receiver sampling period. + +![](5eb69662cc4fa7d0d49b4eb22951c204_img.jpg) + +``` + +graph LR + DC[Duty cycle D_i] --> COMP[Complementary operation] + DC --> GEN[UPPM waveform segment generation] + COMP -->|1-D_i| GEN + SEL[UPPM modulation selector: V2PPM, V4PPM, V8PPM] --> GEN + TX[TX symbol frames] --> GEN + PRE[UPPM delimiter/preamble] --> GEN + GEN -->|W_i1| CONCAT[Concatenation and repetition] + GEN -->|W_i2| CONCAT + CONCAT --> UI[U_i] + subgraph UPPM modulator + COMP + GEN + CONCAT + end + +``` + +G.9992(19)\_F8-10 + +**Figure 8-10 – Functional diagram of the UPPM modulator** + +###### 8.1.4.2.2.1 Complementary operation + +See clause 8.1.4.1.2.1. + +###### 8.1.4.2.2.2 UPPM waveform segment generation + +Two segments of UPPM waveform ( $W_{i1}$ , $W_{i2}$ ) shall be generated with five inputs: DC $D_i$ , the complementary DC $1-D_i$ , a selected VMPPM scheme (see clause 8.1.4.2.1.1), TX symbol frames and UPPM delimiter/preamble (see clause 8.1.4.2.3). $W_{i1}$ , $W_{i2}$ shall have the same duration of $T_s$ and complementary average DC as determined by $D_i$ and $1-D_i$ . $W_{i1}$ , $W_{i2}$ shall also have the same structure: a start delimiter region (SDR), a valid data region (VDR) and an end delimiter region (EDR), as shown in Figure 8-11. In addition, each region in $W_{i1}$ , $W_{i2}$ shall use the same frequency, respectively. + +NOTE – It is assumed that a camera captures the same number of pulses for both $W_{i1}$ and $W_{i2}$ during the same sampling period. + +![](26e334e61dd059cff029338a2a604d8d_img.jpg) + +| | | | +|---------------------------|----------------------|-------------------------| +| Start delimiter (DC = D%) | Valid data (DC = D%) | End delimiter (DC = D%) | +| Segment ( $T_s$ ) | | | + +G.9992(19)\_F8-11 + +**Figure 8-11 – Structure of a UPPM waveform segment** + +The start delimiter and end delimiter are transmitted in the SDR and EDR, respectively, to facilitate the detection of the boundary of a waveform segment. In addition, the start delimiter also indicates the modulation scheme used in this waveform segment. + +The VDRs of the two segments of UPPM waveform ( $W_{i1}$ , $W_{i2}$ ) in Figure 8-11 shall be generated by an incoming TX symbol frame. The preamble may be prepended before the valid data waveform and transmitted in the VDR if the TX symbol frame is the first symbol frame of the PHY frame. + +The format of start delimiter, preamble, valid data and end delimiter waveforms shall be as specified in clause 8.1.4.2.3. + +###### 8.1.4.2.2.3 Concatenation and repetition + +The two segments of UPPM waveform ( $W_{i1}$ , $W_{i2}$ ), each of which has a duration of $T_s = T_c / (2k)$ and an average DC of $D_i$ and $1-D_i$ respectively, shall be concatenated sequentially, and then shall be + +repeated $k$ times. Finally, a UPPM symbol with a duration of $T_c$ shall be formed. Each UPPM symbol consists of $k$ segments of UPPM waveform with an average DC of $D_i$ , and $k$ segments of UPPM waveform with an average DC of $1-D_i$ . Each UPPM waveform segment with an average DC of $D_i$ shall be followed by a UPPM waveform segment with an average DC of $1-D_i$ . + +The $2k$ UPPM waveform segments forms a UPPM symbol with a duration of $T_c$ . The generated UPPM symbols are then transmitted via the LED of the transmitter. + +##### 8.1.4.2.3 UPPM preamble/delimiter/valid data waveforms + +###### 8.1.4.2.3.1 Start delimiter + +Each start delimiter of $W_{i1}$ , $W_{i2}$ shall comprise two sections, as shown in Figure 8-12. The first section shall be used to specify the starting position of the UPPM waveform segment, while the second section shall indicate the modulation scheme employed to modulate the incoming symbol frame and generate the valid data waveform. As shown in Figure 8-12, the average DC of both sections shall be equal to $D\%$ , which shall be identical to the average DC of the whole UPPM waveform segment ( $D_i$ or $1-D_i$ ). The first section of the start delimiter shall be a section of PWM waveform with a duration of $T_{ppm}$ , and the PWM cycle of the PWM pulse $T_{appm}$ . $T_{appm}$ shall be shorter than $T_c/3$ , where $T_c$ is the exposure duration for receiving UPPM symbol, to ensure that the receiver can receive at least 3 VMPPM symbols during each exposure period $T_c$ , guaranteeing a stripe with a brightness of $D\%$ can be captured. + +The second section shall consist of two V2PPM symbols, each of which shall have the same average DC of $D\%$ and the same duration of $T_{ppm}$ . + +![Figure 8-12: An example of the structure of start delimiter. The diagram shows a waveform with two main sections. The 'First section' is a PWM signal with a duration of T_ppm and a pulse width of T_appm. The 'Second section' consists of two V2PPM symbols, each with a duration of T_ppm, for a total duration of 2T_ppm. A label 'Start delimiter (DC = D%)' is placed above the entire waveform. The diagram is labeled G.9992(19)_F8-12.](8c880d6b715587bd710a9ba8414469b1_img.jpg) + +Figure 8-12: An example of the structure of start delimiter. The diagram shows a waveform with two main sections. The 'First section' is a PWM signal with a duration of T\_ppm and a pulse width of T\_appm. The 'Second section' consists of two V2PPM symbols, each with a duration of T\_ppm, for a total duration of 2T\_ppm. A label 'Start delimiter (DC = D%)' is placed above the entire waveform. The diagram is labeled G.9992(19)\_F8-12. + +Figure 8-12 –An example of the structure of start delimiter + +All valid values for the second section and the corresponding modulation schemes used to generate the valid data waveform in the valid data region that follows shall be as specified in Table 8-20. + +Table 8-20 – Modulation order indication + +| Data in the second section | Modulation schemes used in the following valid data region | +|----------------------------|------------------------------------------------------------| +| 01 | V2PPM | +| 00 | V4PPM | +| 11 | V8PPM | + +###### 8.1.4.2.3.2 Valid data + +The incoming symbol frame shall be divided into two parts. If the incoming symbol frame is not the first symbol frame of a PHY frame, these two parts shall have the same number of bits: $N_{ppm} \times \log_2 M_i$ , + +where $N_{ppm} = (T_s - 4T_{ppm}) / T_{ppm}$ . If the incoming symbol frame is the first symbol frame of a PHY frame, the second part shall have $2 \times \log_2 M$ bits more than the first part. The first part of the incoming symbol frame shall be mapped to VMPPM symbols which form the valid data of the UPPM waveform segment $W_{i1}$ . The second part of the incoming symbol frame shall be mapped to VMPPM symbols which form the valid data of the UPPM waveform segment $W_{i2}$ (see clause 8.1.4.2.1.1). There shall be integer number of VMPPM symbols in a valid data region. + +###### 8.1.4.2.3.3 End delimiter + +An end delimiter waveform shall be inserted following the valid data waveform to specify the ending position of this UPPM waveform segment as presented in Figure 8-11. The waveform in this region shall be the same as the waveform in the first 1 section of the start delimiter with the same average DC $D\%$ , $T_{ppm}$ and $T_{appm}$ . + +###### 8.1.4.2.3.4 UPPM preamble signal + +The preamble is prepended to every PHY frame defined in clause 8.1.2.1. It is intended to assist the receiver in detecting the start of a PHY frame. + +The preamble shall be a section of PWM waveform, which shares the same parameter of the PWM waveform in the first section of the start delimiter except a duration of $2T_{ppm}$ . + +### 8.1.5 PSD mask specifications + +No PSD mask is defined by this Recommendation since the power required to drive the emitting device may differ between implementations. + +### 8.1.6 Electrical specifications + +#### 8.1.6.1 Transmit clock tolerance + +The tolerance of the transmit clock shall not exceed $\pm 50$ ppm, including aging. + +### 8.1.7 Transmitter EVM requirements + +No EVM requirements are specified for this Recommendation. + +### 8.1.8 Termination impedance + +No termination impedance requirements are specified for this Recommendation. + +### 8.1.9 Total transmit power + +No total transmit power is defined by this Recommendation since the power required to drive the emitting device may differ between implementations. + +## 8.2 UPWM-based MIMO transmission + +### 8.2.1 Functional model of the PHY + +The functional model of the PHY layer of a UPWM-based MIMO transceiver, for cases of MIMO transmission, is presented in Figure 8-13. The physical medium-independent interface (PMI) and the medium-dependent interface MDI are, respectively, two demarcation reference points between the PHY and the medium access control, and between the PHY and transmission medium. Internal reference points $\delta$ and $\alpha$ show separation between the PMD and physical medium attachment (PMA), and between the physical coding sub-layer (PCS) and PMA, respectively. + +![Figure 8-13 – PHY functional model of the MIMO transceiver](798679874d1c29f8343506a156c79d7e_img.jpg) + +``` + +graph TD + PMI[PMI] --- PCS + PCS[Physical coding -PCS- + generation of PHY-frame, + mapping MPDUs into the PHY-frame] + PCS -- TX PHY frame --> PMA + PMA -- RX PHY frame --> PCS + PMA[Physical medium attachment -PMA- + generation of MIMO payload, MIMO header + insertion, segmentation to UPWM symbols, padding] + PMA -- TX symbol frames --> PMD + PMD -- RX symbol frames --> PMA + PMD[Physical medium dependent -PMD- + DC mapping, UPWM modulation, preamble + insertion, MMI symbol insertion] + PMD --- MDI[MDI] + MDI --- Medium[Medium] + + MPDUin[MPDU in] --> PCS + PCS --> MPDUout[MPDU out] + + PHYMgmt[PHY management] --- PCS_ctrl[PCS control data] + PCS_ctrl --- PCS + PHYMgmt --- PMA_ctrl[PMA control data] + PMA_ctrl --- PMA + PHYMgmt --- PMD_ctrl[PMD control data] + PMD_ctrl --- PMD + + subgraph LeftLabels + direction TB + L1[PMI] + L2[α] + L3[δ] + L4[MDI] + end + +``` + +Figure 8-13 – PHY functional model of the MIMO transceiver + +**Figure 8-13 – PHY functional model of the MIMO transceiver** + +In the transmit direction, $N_1$ MIMO PHY frames are generated and then transmitted through $N_1$ TX ports (e.g., LEDs). The incoming MPDU is mapped into a PHY frame in the PCS. The PHY frame is parsed into multiple spatial streams (SS) according to the MIMO mode (i.e., diversity mode and multiplexing mode), and a MIMO header is inserted for each stream, which are then segmented into UPWM symbol frames in the PMA. The symbol frames of each of the spatial streams is mapped to DCs, modulated and mapped to TX ports in the PMD and transmitted over the medium with relevant parameters. In the PMD, a preamble is added to assist synchronization and phase compensation in the receiver. Besides, an MMI symbol is added to indicate the MIMO mode. + +In the receive direction, frames entering from the medium via the MDI are demodulated and decoded. The recovered MPDUs are forwarded to the MAC via the PMI. The recovered PHY-frame headers (PFH) are processed in the PHY to extract the relevant frame parameters specified in clause 8.1.2.3. + +### 8.2.2 Physical coding sublayer + +The functional model of the physical coding sublayer (PCS) is presented in Figure 8-14. It is intended to describe in more detail the PCS functional block presented in Figure 8-13. + +![Figure 8-14 – Functional model of PCS. The diagram shows the flow of data through the PCS sublayer. In the transmit direction (top), 'MPDU in' enters the 'MPDU mapper', which outputs to a 'MUX (TDM)'. The 'MUX (TDM)' outputs a 'TX PHY frame' at the 'α-reference point'. A 'Header generation' block receives input from the 'MPDU mapper' and the 'MUX (TDM)' and sends 'PCS control data' to the 'PHY management' entity. In the receive direction (bottom), an 'RX PHY frame' enters the 'Header processing' block at the 'α-reference point'. The 'Header processing' block sends 'PCS control data' to the 'PHY management' entity and outputs to the 'MPDU de-mapper', which produces the final 'MPDU out'. The 'PHY management' entity is shown as a vertical line on the right side of the diagram. A dashed line separates the transmit and receive paths at the 'α-reference point'. The diagram is labeled 'G.992(19)_F8-14'.](cbb2d311b20781a595488445ded48d0a_img.jpg) + +Figure 8-14 – Functional model of PCS. The diagram shows the flow of data through the PCS sublayer. In the transmit direction (top), 'MPDU in' enters the 'MPDU mapper', which outputs to a 'MUX (TDM)'. The 'MUX (TDM)' outputs a 'TX PHY frame' at the 'α-reference point'. A 'Header generation' block receives input from the 'MPDU mapper' and the 'MUX (TDM)' and sends 'PCS control data' to the 'PHY management' entity. In the receive direction (bottom), an 'RX PHY frame' enters the 'Header processing' block at the 'α-reference point'. The 'Header processing' block sends 'PCS control data' to the 'PHY management' entity and outputs to the 'MPDU de-mapper', which produces the final 'MPDU out'. The 'PHY management' entity is shown as a vertical line on the right side of the diagram. A dashed line separates the transmit and receive paths at the 'α-reference point'. The diagram is labeled 'G.992(19)\_F8-14'. + +**Figure 8-14 – Functional model of PCS** + +In the transmit direction, the incoming MPDU is mapped into a payload field of a PHY frame (clause 8.2.2.1) as described in clause 8.2.2.2. The PHY-frame header (clause 8.8.2.3) is then added to form a TX PHY frame. The TX PHY frame is passed across the $\alpha$ -reference point for further processing in the PMA. + +In the receive direction, the decoded PHY-frame payload and header are processed and originally transmitted MPDUs are recovered from the payloads of received PHY frames and submitted to the PMI. Relevant control information conveyed in the PHY-frame header is processed and submitted to the PHY management entity. + +#### 8.2.2.1 PHY frame + +The PHY frame at the $\alpha$ -reference point includes a PHY header and PHY payload, as described in clause 8.1.2.1. The PHY frame shall be used to generate the MIMO payload (see clause 8.2.3.3). + +#### 8.2.2.2 MPDU mapping + +See clause 8.1.2.2. + +#### 8.2.2.3 PHY-frame header + +See clause 8.1.2.3. + +### 8.2.3 Physical medium attachment sublayer + +The functional model of the PMA is presented in Figure 8-15. It is intended to describe in more detail the PMA functional block presented in Figure 8-13. + +In the transmit direction, the incoming PHY frame (except for the preamble) at the $\alpha$ -reference point has a format as defined in clause 8.2.2.1. Both the header bits and the payload bits of the incoming frame are used to create the MIMO payload for each TX port as defined in 8.2.3.3. The MIMO header is generated as described in clause 8.2.3.2 and prepended before the MIMO payload. For each TX port, the MIMO header and MIMO payload are segmented into an integer number of symbol frames as described in clause 8.2.3.4. The obtained symbol frames of the MIMO header and the MIMO payload are submitted to the PMD (at the $\delta$ -reference point) for modulation and transmission over the medium. + +In the receive direction, the MIMO header for each TX port is processed, and all necessary inverse operations of MIMO payload spatial streams de-parsing are performed on the received symbol + +frames. The recovered PHY-frame header and payload are submitted to the $\alpha$ -reference point for further processing in the PCS. + +![Figure 8-15: Functional model of PMA. This block diagram shows the flow of data through the Physical Medium Attachment (PMA) layer. On the transmitter (TX) side, a 'TX PHY frame' enters from the top, passing the alpha-reference point. It goes through a 'Spatial streams parser', then a 'MIMO header generation and insertion' block, and finally a 'Segmentation to UPWM symbols' block. The output is 'TX symbol frames' which pass the delta-reference point. On the receiver (RX) side, 'RX symbol frames' enter from the bottom, passing the delta-reference point. They go through 'MIMO header processing pad removal', then a 'Spatial streams de-parser', and finally output as an 'RX PHY frame' passing the alpha-reference point. A 'PHY management' block on the right is connected to both the TX and RX paths via 'PHY control data' lines. The diagram is labeled G.9992(19)_F8-15.](878d9539700bd792e7d12ad6f1203c5d_img.jpg) + +Figure 8-15: Functional model of PMA. This block diagram shows the flow of data through the Physical Medium Attachment (PMA) layer. On the transmitter (TX) side, a 'TX PHY frame' enters from the top, passing the alpha-reference point. It goes through a 'Spatial streams parser', then a 'MIMO header generation and insertion' block, and finally a 'Segmentation to UPWM symbols' block. The output is 'TX symbol frames' which pass the delta-reference point. On the receiver (RX) side, 'RX symbol frames' enter from the bottom, passing the delta-reference point. They go through 'MIMO header processing pad removal', then a 'Spatial streams de-parser', and finally output as an 'RX PHY frame' passing the alpha-reference point. A 'PHY management' block on the right is connected to both the TX and RX paths via 'PHY control data' lines. The diagram is labeled G.9992(19)\_F8-15. + +**Figure 8-15 – Functional model of PMA** + +#### 8.2.3.1 UPWM-based MIMO PHY frame + +The format of the MIMO PHY frame for UPWM-based MIMO transmission is presented in Figure 8-16. The MIMO payload shall be created in the PMA, as either multiple spatial streams (i.e., multiplexing mode) or a single spatial stream (i.e., diversity mode). The preamble and MIMO mode indication (MMI) symbol are added to the PHY frame in the PMD. The preamble is intended for synchronization and phase compensation. Both the preamble and MMI symbol do not carry any user or management data. In addition, the MIMO header is inserted to the PHY frame in the PMA for the case where the MIMO mode is in multiplexing mode. At the MDI interface the transmission shall adhere to the following (as described in detail in clause 8.2.4): + +- The preamble/MMI symbol/MIMO header/payload shall be transmitted simultaneously on all TX ports. The presence of MIMO header is MIMO mode dependent (see clause 8.2.2.3). +- The preamble and the MMI symbol to be transmitted on the first TX port shall be copied to all other TX ports. + +![Figure 8-16: Format of the PHY frame in a UPWM-based MIMO transmission. This diagram shows the structure of PHY frames across multiple transmit (Tx) ports. Each port (Tx port #1, Tx port #2, ..., Tx port #N1) has a frame consisting of four parts: a blue 'Preamble', a green 'MMI symbol', an orange 'MIMO header' (indicated by a dashed box), and a white 'MIMO payload' (labeled #1, #2, ..., #N1). The preamble and MMI symbol are identical across all ports, while the MIMO header and payload are port-specific. The diagram is labeled G.9992(19)_F8-16.](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +Figure 8-16: Format of the PHY frame in a UPWM-based MIMO transmission. This diagram shows the structure of PHY frames across multiple transmit (Tx) ports. Each port (Tx port #1, Tx port #2, ..., Tx port #N1) has a frame consisting of four parts: a blue 'Preamble', a green 'MMI symbol', an orange 'MIMO header' (indicated by a dashed box), and a white 'MIMO payload' (labeled #1, #2, ..., #N1). The preamble and MMI symbol are identical across all ports, while the MIMO header and payload are port-specific. The diagram is labeled G.9992(19)\_F8-16. + +**Figure 8-16 – Format of the PHY frame in a UPWM-based MIMO transmission** + +The MIMO header (if it exists) and MIMO payload shall contain an integer number of UPWM symbols. The length of the MIMO payload may vary from frame to frame. + +#### 8.2.3.2 MIMO header + +The MIMO header shall be present only if the MMI symbol indicates multiplexing mode (see clause 8.2.4.4). The MIMO header format is defined in Table 8-21. + +**Table 8-21 – MIMO header format** + +| Field | Octet | Bits | Description | Reference | +|-------------|-------|-------|----------------------------------------------------------------|------------------| +| Ext_Ind | 0 | [0] | Indication of the presence of the PortID_Ext and PB_Ext fields | Clause 8.2.3.2.1 | +| LastPortInd | | [1] | Indication of the last port | Clause 8.2.3.2.2 | +| PortID | | [6:2] | The ID of the TX port | Clause 8.2.3.2.3 | +| PB | | [7] | The odd parity bit | Clause 8.2.3.2.4 | +| PortID_Ext | 1 | [6:0] | The extended part of the ID of the TX port | Clause 8.2.3.2.5 | +| PB_Ext | | [7] | The odd parity bit | Clause 8.2.3.2.6 | + +##### 8.2.3.2.1 Ext\_Ind + +If the Ext\_Ind field is set to one, the PortID\_Ext field and PB\_Ext field shall be present. If the Ext\_Ind field is set to zero, the PortID\_Ext field and PB\_Ext field shall not be present. + +##### 8.2.3.2.2 LastPortInd + +If the LastPortInd field is set to one, the decimal value of the PortID field shall be the number of the TX ports. If the LastPortInd field is set to zero, the decimal value of the PortID field shall be lower than the number of the TX ports. + +##### 8.2.3.2.3 PortID + +If the Ext\_Ind field is set to zero, the PortID field shall be set to the ID of the TX ports from which the MIMO PHY frame is transmitted. It shall be represented as a 5-bit unsigned integer. + +If the Ext\_Ind field is set to one, the PortID field shall be set to the least significant 5 bits of the ID of the TX ports from which the MIMO PHY frame is transmitted. + +##### 8.2.3.2.4 PB + +The PB field is an odd parity bit that is intended for MIMO PHY frame verification. The PB field shall be set to 1, if the count of bits in Ext\_Ind field, LastPortInd field and PortID field with a value of 1 is even. The PB field shall be set to 0, if the count of bits in Ext\_Ind field, LastPortInd field and PortID field with a value of 1 is odd. + +##### 8.2.3.2.5 PortID\_Ext + +The PortID\_Ext field shall be present only if the Ext\_Ind field is set to one. + +The PortID\_Ext field shall be set to the most significant 7 bits of the ID of the TX ports from which the MIMO PHY frame is transmitted. The ID of the TX port shall be represented as a 12-bit unsigned integer, combining with the PortID field. + +##### 8.2.3.2.6 PB\_Ext + +The PB\_Ext field shall be present only if the Ext\_Ind field is set to one. + +The PB\_Ext field is an odd parity bit that is intended for MIMO PHY frame verification. The PB\_Ext field shall be set to 1, if the count of bits in PortID\_Ext field with a value of 1 is even. The PB\_Ext field shall be set to 0, if the count of bits in PortID\_Ext field with a value of 1 is odd. + +#### 8.2.3.3 MIMO payload + +For the case where the MIMO mode is diversity mode, the MIMO payload of each stream shall be the same, and shall contain a PHY frame passed through $\alpha$ reference point, as described in clause 8.2.2.1. + +For the case where the MIMO mode is multiplexing mode, the TX PHY frame passed through $\alpha$ reference point shall be segmented into $N_1$ segments, where $N_1$ is the number of the TX ports. If the number of bits of the TX PHY frame $k_{PHY}$ is not an integral multiple of $N_1$ , $k_{pad}$ zeros shall be padding at the tail of the TX PHY frame to guarantee that $(k_{PHY} + k_{pad})/N_1$ is an integer. The incoming TX PHY frame shall be segmented in sequence, and the first segment shall contain the first $(k_{PHY} + k_{pad})/N_1$ bits, and the second frame shall contain the second $(k_{PHY} + k_{pad})/N_1$ bits and so on, until the last segment. Each segment shall be mapped to the corresponding TX port in numerical order, comprising the MIMO payload. + +NOTE – $k_{pad}$ should be as little as possible. + +#### 8.2.3.4 Segmentation to UPWM symbols + +For each TX port, the MIMO header and the MIMO payload shall be segmented into symbol frames in sequence according to the modulation order $m$ . The number of bits in each symbol frames shall be $b$ . The MIMO header and MIMO payload segmentation is illustrated in Figure 8-17. + +If the modulation order is the integral power of 2, each symbol frame will be modulated to generate one UPWM symbols. The MIMO Header and the MIMO payload shall be segmented in sequence, the frame shall contain $b$ bits, where $b = \log_2 m$ . $N_{sf}$ symbol frames are obtained, and each of the $N_{sf}-1$ symbol frames shall contain $b$ bits, while the last symbol frame may contain $b$ bits or less than $b$ bits. If the last symbol frame contains less than $b$ bits, it shall be padded with zeros. + +If the modulation order is not the integral power of 2, each symbol frame will be modulated to generate two UPWM symbols. The MIMO header and the MIMO payload shall be segmented in sequence, and the first frame shall contain the first $b$ bits, and the second frame shall contain the second $b$ bits and so on, until the last symbol frame, where $b = \text{floor}(\log_2 m^2)$ . $N_{sf}$ symbol frames are obtained, and each of the first $N_{sf}-1$ symbol frames shall contain $b$ bits, while the last symbol frame may contain $b$ bits or less than $b$ bits. If the last symbol frame contains less than $b$ bits, it shall be padded with zeros. + +![Diagram illustrating the segmentation of MIMO header and MIMO payload into symbol frames. The diagram shows a sequence of frames starting with the MIMO header and followed by the MIMO payload. The first frame is labeled 'Symbol frame 1' and contains 'b bits'. The second frame is labeled 'Symbol frame 2' and also contains 'b bits'. An ellipsis indicates subsequent frames. The second-to-last frame is labeled 'Symbol frame N_sf - 1' and contains 'b bits'. The final frame is labeled 'Symbol frame N_sf' and contains 'b bits'. A 'Padding' area is shown at the end of the sequence, indicated by an arrow pointing to the end of the last frame. The diagram is labeled 'G.9992(19)_F8-17' at the bottom right.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +The diagram illustrates the segmentation of a MIMO frame into symbol frames. At the top, 'LSB, octet 0' is indicated. Below this, a horizontal bar represents the frame structure, divided into 'MIMO header' and 'MIMO payload'. The 'MIMO header' is further divided into two 'b bits' segments. The 'MIMO payload' is also divided into 'b bits' segments. Below this bar, a sequence of symbol frames is shown: 'Symbol frame 1', 'Symbol frame 2', an ellipsis, 'Symbol frame Nsf - 1', and 'Symbol frame Nsf'. Each of these frames is shown to contain 'b bits'. A 'Padding' area is indicated at the end of the sequence, with an arrow pointing to the end of the 'Symbol frame Nsf'. The diagram is labeled 'G.9992(19)\_F8-17' at the bottom right. + +Diagram illustrating the segmentation of MIMO header and MIMO payload into symbol frames. The diagram shows a sequence of frames starting with the MIMO header and followed by the MIMO payload. The first frame is labeled 'Symbol frame 1' and contains 'b bits'. The second frame is labeled 'Symbol frame 2' and also contains 'b bits'. An ellipsis indicates subsequent frames. The second-to-last frame is labeled 'Symbol frame N\_sf - 1' and contains 'b bits'. The final frame is labeled 'Symbol frame N\_sf' and contains 'b bits'. A 'Padding' area is shown at the end of the sequence, indicated by an arrow pointing to the end of the last frame. The diagram is labeled 'G.9992(19)\_F8-17' at the bottom right. + +Figure 8-17 – MIMO header and the MIMO payload segmentation + +### 8.2.4 Physical medium dependent sublayer + +The functional model of the PMD is presented in Figure 8-18. In the transmit direction, the m-DC mapper maps the incoming symbol frames (for each spatial stream) to m-ary DC sequences, as specified in clause 8.2.4.1. The DC sequences for each spatial stream are fed into a UPWM modulator where non-flickering signals are generated as described in clause 8.2.4.2. After adding the preamble, the transmit signal for each spatial stream is fed into a digital LED driver, and is transmitted using visible light. Parameters of the preamble are determined by the PHY management. + +Frames are output on to the medium without inter-frame gaps. + +In the receive direction, a camera with a frame rate of $f_c$ and an exposure duration of $T_e$ is employed to detect and record the optical signal. With the help of the preamble detection and PI extraction, the undersampled-recorded data are compensated and demodulated. The recovered symbol frames are transferred to the PMA via $\delta$ -reference point. The preamble, MMI symbol and MIMO header are processed and the processing result are passed to the PHY management entity. + +![Functional model of the PMD diagram](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` + + graph TD + subgraph PMA_Layer [PMA Layer] + TX_Frames[TX symbol frames] + RX_Frames[RX symbol frames] + end + + subgraph PMD_Layer [PMD Layer] + direction TB + subgraph TX_Path [Transmit Path] + Mapper[m-DC mapper] + Modulator[UPWM modulator] + PreambleGen[Preamble and MMI symbol generation] + LEDDriver[Digital LED driver] + end + + subgraph RX_Path [Receive Path] + MIMO_Proc[MIMO mode determination +Demodulation +Compensation process +Preamble detection and PI extraction] + Camera[Camera] + end + end + + PHY_Mgmt[PHY management] + + TX_Frames --> Mapper + Mapper --> Modulator + PreambleGen --> Modulator + Modulator --> LEDDriver + LEDDriver --> Medium((Medium)) + + Medium --> Camera + Camera --> MIMO_Proc + MIMO_Proc --> RX_Frames + + MIMO_Proc -- "PMD control data" --> PHY_Mgmt + PHY_Mgmt -- "PMD control data" --> MIMO_Proc + +``` + +The diagram illustrates the functional model of the PMD. A dashed horizontal line labeled "δ-reference point" separates the PMA (top) from the PMD (bottom). In the transmit path, TX symbol frames enter the PMD, pass through an m-DC mapper, then a UPWM modulator (which also receives input from a Preamble and MMI symbol generation block), and finally a Digital LED driver. The signal exits the PMD through the MDI (dashed line) to the Medium. In the receive path, signals from the Medium enter via the Camera, then go to a block for MIMO mode determination, demodulation, compensation, and preamble/PI extraction, before exiting as RX symbol frames. This processing block exchanges PMD control data with the PHY management entity. + +Functional model of the PMD diagram + +**Figure 8-18 – Functional model of the PMD** + +#### 8.2.4.1 m-DC mapping + +See clause 8.1.4.1.1. + +#### 8.2.4.2 UPWM modulator + +See clause 8.1.4.1.2. + +#### 8.2.4.3 UPWM preamble signal + +See clause 8.1.4.1.3. + +#### 8.2.4.4 MMI symbol + +The MMI symbol is used to indicate the MIMO modes, which includes multiplexing mode and diversity mode. The MMI symbol comprises of one UPWM symbol, and for each PHY frame, the same UPWM symbol shall be transmitted as the MMI symbol at each TX port. The value of the DC for generating the MMI symbol shall be set according to the configured MIMO mode as shown in Table 8-22. + +**Table 8-22 – Value of DC for generating the MMI symbol** + +| MIMO mode | Value of DC | +|------------------|--------------------| +| Multiplexing | 100% | +| Diversity | 0% | + +### **8.2.5 PSD mask specifications** + +See clause 8.1.5. + +### **8.2.6 Electrical specifications** + +#### **8.2.6.1 Transmit clock tolerance** + +See clause 8.1.6.1. + +### **8.2.7 Transmitter EVM requirements** + +See clause 8.1.7. + +### **8.2.8 Termination impedance** + +See clause 8.1.8. + +### **8.2.9 Total transmit power** + +See clause 8.1.9. + +## **8.3 UPPM-based MIMO transmission** + +### **8.3.1 Functional model of the PHY** + +The functional model of the PHY layer of a UPPM-based MIMO transceiver, for cases of UPPM-based MIMO transmission, is presented in Figure 8-19. The physical medium-independent interface and the medium-dependent interface are, respectively, two demarcation reference points between the PHY and the medium access control, and between the PHY and transmission medium. Internal reference points $\delta$ and $\alpha$ show separation between the physical medium dependent and physical medium attachment, and between the physical coding sub-layer and PMA, respectively. + +![Figure 8-19 – PHY functional model of the UPPM-based MIMO transceiver. This block diagram illustrates the data flow and control signals within a PHY transceiver. At the top, 'PHY management' is connected to both the 'Physical coding (PCS)' and 'Physical medium attachment (PMA)' blocks. On the left (transmit side), 'MPDU1 in' enters the PCS from the 'PMI'. The PCS generates a 'PHY-frame' and sends 'PCS control data' to the PMA. The PMA performs 'Segmentation, padding' and outputs 'TX1 PHY frame' and 'TX1 symbol frames'. These frames pass through the 'α-reference point' and 'δ-reference point' respectively, into the 'Physical medium dependent (PMD)'. The PMD handles 'DC mapping, preamble insertion, UPWM modulation, determination of modulation schemes, UPPM modulation, pilot symbol insertion' and transmits data over the 'Medium' via the 'MDI'. On the right (receive side), 'RX2 symbol frames' are received from the medium, passing through the 'δ-reference point' and 'α-reference point' into the PMA. The PMA generates a 'MIMO payload' and sends 'PMA control data' to the PCS. The PCS then outputs 'MPDU2 out' to the 'PMI'. Various control data paths (PCS control data, PMA control data, PMD control data) are shown between the management, PCS, PMA, and PMD blocks.](5ee1bbbf85b473f78af9ec8368a4159a_img.jpg) + +Figure 8-19 – PHY functional model of the UPPM-based MIMO transceiver. This block diagram illustrates the data flow and control signals within a PHY transceiver. At the top, 'PHY management' is connected to both the 'Physical coding (PCS)' and 'Physical medium attachment (PMA)' blocks. On the left (transmit side), 'MPDU1 in' enters the PCS from the 'PMI'. The PCS generates a 'PHY-frame' and sends 'PCS control data' to the PMA. The PMA performs 'Segmentation, padding' and outputs 'TX1 PHY frame' and 'TX1 symbol frames'. These frames pass through the 'α-reference point' and 'δ-reference point' respectively, into the 'Physical medium dependent (PMD)'. The PMD handles 'DC mapping, preamble insertion, UPWM modulation, determination of modulation schemes, UPPM modulation, pilot symbol insertion' and transmits data over the 'Medium' via the 'MDI'. On the right (receive side), 'RX2 symbol frames' are received from the medium, passing through the 'δ-reference point' and 'α-reference point' into the PMA. The PMA generates a 'MIMO payload' and sends 'PMA control data' to the PCS. The PCS then outputs 'MPDU2 out' to the 'PMI'. Various control data paths (PCS control data, PMA control data, PMD control data) are shown between the management, PCS, PMA, and PMD blocks. + +**Figure 8-19 – PHY functional model of the UPPM-based MIMO transceiver** + +In the transmit direction, data enters the PHY from the MAC via the PMI in blocks of bytes called MPDUs. The incoming MPDU is mapped into a PHY frame in the PCS. The PHY frame is parsed into multiple spatial streams according to the number of the TX ports (i.e., LED lamps), then segmented into UPPM symbol frames in the PMA. The symbol frames of each of the spatial streams is modulated to UPPM symbols, and a pilot symbol is inserted for each spatial stream, then mapped to TX ports in the PMD and transmitted over the medium with relevant parameters. In the PMD, a preamble is added to assist synchronization and phase compensation in the receiver. + +In the receive direction, frames entering from the medium (reception is also done via multiple Rx ports) via the MDI are demodulated and decoded. The recovered MPDUs are forwarded to the MAC via the PMI. The recovered PHY-frame headers) are processed in the PHY to extract the relevant frame parameters specified in clause 8.1.2.3. + +### 8.3.2 Physical coding sublayer + +The functional model of the PCS is presented in Figure 8-20. It is intended to describe in more detail the PCS functional block presented in Figure 8-19. + +![Figure 8-20 – Functional model of PCS. This block diagram shows the internal structure of the Physical Coding Sublayer (PCS). 'MPDU in' enters from the 'PMI' and is processed by an 'MPDU mapper'. The output of the mapper goes to a 'MUX (TDM)' and also to a 'Header generation' block. The 'MUX (TDM)' outputs a 'TX PHY frame' at the 'α-reference point'. On the receive side, an 'RX PHY frame' enters from below the 'α-reference point' and is processed by a 'Header processing' block. The output of this block goes to an 'MPDU de-mapper', which then outputs 'MPDU out' to the 'PMI'. The 'Header processing' block also sends 'PCS control data' to 'PHY management'. The 'Header generation' block receives 'PCS control data' from 'PHY management' and sends it to the 'MPDU mapper'.](552328a9daaf3bc0069424b500025880_img.jpg) + +Figure 8-20 – Functional model of PCS. This block diagram shows the internal structure of the Physical Coding Sublayer (PCS). 'MPDU in' enters from the 'PMI' and is processed by an 'MPDU mapper'. The output of the mapper goes to a 'MUX (TDM)' and also to a 'Header generation' block. The 'MUX (TDM)' outputs a 'TX PHY frame' at the 'α-reference point'. On the receive side, an 'RX PHY frame' enters from below the 'α-reference point' and is processed by a 'Header processing' block. The output of this block goes to an 'MPDU de-mapper', which then outputs 'MPDU out' to the 'PMI'. The 'Header processing' block also sends 'PCS control data' to 'PHY management'. The 'Header generation' block receives 'PCS control data' from 'PHY management' and sends it to the 'MPDU mapper'. + +**Figure 8-20 – Functional model of PCS** + +In the transmit direction, the incoming MPDU is mapped into a payload field of a PHY frame (clause 8.3.2.1) as described in clause 8.3.2.2. The PHY-frame header is then added to form a TX PHY frame. The TX PHY frame is passed across the $\alpha$ -reference point for further processing in the PMA. + +In the receive direction, the decoded PHY-frame payload and header are processed and originally transmitted MPDUs are recovered from the payloads of received PHY frames and submitted to the PMD. Relevant control information conveyed in the PHY-frame header is processed and submitted to the PHY management entity. + +#### **8.3.2.1 PHY frame** + +The PHY frame at the $\alpha$ -reference point includes a PHY header and PHY payload as described in clause 8.1.2.1. The PHY frame shall be used to generate the MIMO payload (see clause 8.3.3.2). + +#### **8.3.2.2 MPDU mapping** + +See clause 8.1.2.2. + +#### **8.3.2.3 PHY-frame header** + +See clause 8.1.2.3. + +### **8.3.3 Physical medium attachment sublayer** + +The functional model of the PMA is presented in Figure 8-21. It is intended to describe in more detail the PMA functional block presented in Figure 8-19. + +In the transmit direction, the incoming PHY frame (except for the preamble) at the $\alpha$ -reference point has a format as defined in clause 8.3.2.1. Both the header bits and the payload bits of the incoming frame are used to create the MIMO payload for each TX port as defined in clause 8.3.3.2. The spatial stream parser divides the TX PHY frame into N blocks, where N is the number of the TX ports. For each TX port, the MIMO payload are segmented into an integer number of symbol frames as described in clause 8.3.3.3. The obtained symbol frames of the MIMO payload are submitted to the PMD (at the $\delta$ -reference point) for modulation and transmission over the medium. + +In the receive direction, all necessary inverse operations of MIMO payload spatial streams de-parsing are performed on the received symbol frames. The recovered PHY-frame header and payload are submitted to the $\alpha$ -reference point for further processing in the PCS. + +![Functional model of PMA diagram showing TX and RX paths with reference points alpha and delta.](2580688a4de0a29692805cc6ba4822d7_img.jpg) + +The diagram illustrates the functional model of the Physical Medium Attachment (PMA). It is divided into two main vertical paths: the Transmit (TX) path on the left and the Receive (RX) path on the right, with a central 'PHY management' block on the far right. + +- TX Path:** A 'TX PHY frame' enters from the top at the $\alpha$ -reference point (indicated by a dashed line). It passes through a 'Spatial streams parser' and then a 'Segmentation to UPPM symbols' block. Below the $\delta$ -reference point (another dashed line), the output is 'TX symbol frames'. +- RX Path:** 'RX symbol frames' enter from the bottom below the $\delta$ -reference point. They pass through 'Pad removal' and then a 'Spatial streams de-parser' block. Above the $\alpha$ -reference point, the output is an 'RX PHY frame'. +- PHY Management:** This block on the right is connected to both the 'Spatial streams parser' and the 'Spatial streams de-parser' via 'PHY control data' lines. +- Reference Points:** The $\alpha$ -reference point is at the top, and the $\delta$ -reference point is at the bottom, both marked by horizontal dashed lines. +- Text:** 'G.992(19)\_F8-21' is located in the bottom right corner of the diagram area. + +Functional model of PMA diagram showing TX and RX paths with reference points alpha and delta. + +**Figure 8-21 – Functional model of PMA** + +#### 8.3.3.1 UPPM-based MIMO PHY frame + +The format of the MIMO PHY frame for UPPM-based MIMO transmission is presented in Figures 8-22 and 8-23. The PHY frame at the $\alpha$ -reference point includes a PHY header (as described in clause 8.1.2.3) and PHY payload (as described in clause 8.1.2.1) specified for SISO transmission. The MIMO payload (as described in clause 8.3.3.2) shall be created by equally dividing the SISO header and PHY payload into $N_2$ spatial streams. If UPWM SISO transmission is adopted in the low speed channel for each TX port, a UPWM preamble shall be added to each UPPM-based MIMO payload stream in the PMD, and each TX port shall transmit the same UPWM SISO information in the PMD. If UPWM SISO transmission is not adopted in UPPM-based MIMO transmission, a pre-defined DC value which is vendor discretionary shall be given for generating UPPM symbol. The UPWM preamble is intended for UPWM SISO synchronization and phase compensation. The UPWM preamble do not carry any UPWM user or management data, however, it carries UPPM-based MIMO data. If UPWM SISO transmission is adopted in the low speed channel for each TX port, at the MDI interface the transmission shall adhere to the following (as described in detail in clause 8.3.4): + +- The UPWM preamble / UPPM-based MIMO payload shall be transmitted simultaneously on all TX ports. +- The UPWM preamble to be transmitted on the first TX port shall be copied to all other TX ports. + +![Figure 8-22: Format of the PHY frame in a UPPM-based MIMO transmission with UPWM SISO transmission. The diagram shows multiple Tx ports (1, 2, ..., N2). Each port transmits a frame consisting of a 'UPWM preamble' followed by a 'UPPM-based MIMO payload #n'.](4162c218fc7881cd90fc9574e07d2327_img.jpg) + +| | | | +|-------------------------|---------------|-----------------------------------------| +| Tx port #1 | UPWM preamble | UPPM-based MIMO payload #1 | +| Tx port #2 | UPWM preamble | UPPM-based MIMO payload #2 | +| ⋮ | | | +| Tx port #N 2 | UPWM preamble | UPPM-based MIMO payload #N 2 | + +Figure 8-22: Format of the PHY frame in a UPPM-based MIMO transmission with UPWM SISO transmission. The diagram shows multiple Tx ports (1, 2, ..., N2). Each port transmits a frame consisting of a 'UPWM preamble' followed by a 'UPPM-based MIMO payload #n'. + +G.992(19)\_F8-22 + +**Figure 8-22 – Format of the PHY frame in a UPPM-based MIMO transmission with UPWM SISO transmission** + +![Figure 8-23: Format of the PHY frame in a UPPM-based MIMO transmission without UPWM SISO transmission. Similar to Figure 8-22, but the frames consist only of the 'UPPM-based MIMO payload #n' without the preamble.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +| | | +|-------------------------|-----------------------------------------| +| Tx port #1 | UPPM-based MIMO payload #1 | +| Tx port #2 | UPPM-based MIMO payload #2 | +| ⋮ | | +| Tx port #N 2 | UPPM-based MIMO payload #N 2 | + +Figure 8-23: Format of the PHY frame in a UPPM-based MIMO transmission without UPWM SISO transmission. Similar to Figure 8-22, but the frames consist only of the 'UPPM-based MIMO payload #n' without the preamble. + +G.992(19)\_F8-23 + +**Figure 8-23 – Format of the PHY frame in a UPPM-based MIMO transmission without UPWM SISO transmission** + +The length of the MIMO payload may vary from frame to frame. + +#### 8.3.3.2 UPPM-based MIMO payload + +The TX PHY frame passed through $\alpha$ reference point shall be segmented into N2 segments, where N2 is the number of the TX ports. If the number of bits of the TX PHY frame $k_{PHY}$ is not an integral multiple of N2, $k_{pad}$ zeros shall be padding at the tail of the TX PHY frame to guarantee that $(k_{PHY} + k_{pad})/N_2$ is an integer. The incoming TX PHY frame shall be segmented in sequence, and the first segment shall contain the first $(k_{PHY} + k_{pad})/N_2$ bits, and the second frame shall contain the second $(k_{PHY} + k_{pad})/N_2$ bits and so on, until the last segment. Each segment shall be mapped to the corresponding TX port in numerical order, comprising the MIMO payload. + +NOTE – $k_{pad}$ should be as little as possible. + +#### 8.3.3.3 Segmentation to UPPM-based MIMO symbols + +For each TX port, the incoming UPPM-based MIMO PHY frame from each spatial stream shall be segmented into even number of symbol frames in sequence according to many parameters indicated by the PHY control data which are received through PHY management: + +- 1) DC $D_i$ either determined by the m-DC mapper (see clause 8.1.4.1.1) or a pre-defined value, which is vendor discretionary; +- 2) valid data region information (see clause 8.1.4.2.3.2) of a UPPM waveform segment. TX PHY frame segmentation is illustrated in Figure 8-24. + +For each TX port, the incoming TX PHY frame shall be segmented in sequence, $2N_{sfl} + 2$ symbol frames are obtained. If the symbol frame is the first symbol frame (i.e., symbol frame 1), it shall contain $(N_{ppm} - 2) \times \log_2 M$ bits, where $N_{ppm}$ and $M$ are parameters determined by valid data region information (see clause 8.1.4.2.3.2) of a UPPM waveform segment, the second symbol frame shall + +contain $N_{ppm} \times \log_2 M$ bits. Symbol frame No. $2n + 1$ and symbol frame No. $2n + 2$ ( $n \geq 1$ ) shall contain the same number of bits. If symbol frame No. 1 contains less than $(N_{ppm} - 2) \times \log_2 M$ bits, both symbol No. 1 and No. 2 shall be padded with zeros. If only symbol frame No. 2 contains less than $N_{ppm} \times \log_2 M$ bits, it shall be padded with zeros. If symbol frame No. $2n + 1$ ( $n \geq 1$ ) contains less than $N_{ppm} \times \log_2 M$ bits, both symbol No. $2n + 1$ and No. $2n + 2$ shall be padded with zeros. If only symbol frame No. $2n + 2$ contains less than $N_{ppm} \times \log_2 M$ bits, it shall be padded with zeros. + +![Figure 8-24: Two TX PHY frame segmentations for each UPPM-based MIMO transmission port. Diagram (a) shows a MIMO payload with bits b1, b2, ..., b_{2N_{sfl}+1} mapped to Symbol frames 1, 2, ..., 2N_{sfl}+1, with padding added to Symbol frame 2N_{sfl}+2. Diagram (b) shows a similar structure but with padding added to both Symbol frames 2N_{sfl}+1 and 2N_{sfl}+2.](b898dcb574f08ea237dd3326abecd185_img.jpg) + +Diagram (a) illustrates the first TX PHY frame segmentation. At the top, 'LSB, octet 0' is indicated. Below it, a 'MIMO payload' bar spans across. The payload is divided into segments: $b_1$ bits, $b_2$ bits, an ellipsis, and $b_{2N_{sfl}+1}$ bits. These segments are mapped to 'Symbol frame 1', 'Symbol frame 2', an ellipsis, 'Symbol frame $2N_{sfl} + 1$ ', and 'Symbol frame $2N_{sfl} + 2$ '. A 'Padding' label with arrows points to the 'Symbol frame $2N_{sfl} + 2$ '. + +Diagram (b) illustrates the second TX PHY frame segmentation. It follows a similar structure to (a), but the 'Padding' label with arrows points to both 'Symbol frame $2N_{sfl} + 1$ ' and 'Symbol frame $2N_{sfl} + 2$ '. + +G.9992(19)\_F8-24 + +Figure 8-24: Two TX PHY frame segmentations for each UPPM-based MIMO transmission port. Diagram (a) shows a MIMO payload with bits b1, b2, ..., b\_{2N\_{sfl}+1} mapped to Symbol frames 1, 2, ..., 2N\_{sfl}+1, with padding added to Symbol frame 2N\_{sfl}+2. Diagram (b) shows a similar structure but with padding added to both Symbol frames 2N\_{sfl}+1 and 2N\_{sfl}+2. + +**Figure 8-24 – Two TX PHY frame segmentations for each UPPM-based MIMO transmission port** + +### 8.3.4 Physical medium dependent sublayer + +The functional model of the PMD is presented in Figure 8-25. In the transmit direction, the m-DC mapper maps the incoming TX1 symbol frames to m-ary DC sequences, as specified in clause 8.1.4.1.1. The DC sequences of the prepending preamble and the DC sequences obtained from the m-DC mapping of the incoming TX1 symbol frames are fed into the UPPM modulation selector. + +The incoming TX2 symbol frames are fed into multiple UPPM modulators where non-flickering signals are generated as described in clause 8.1.4.2.2. The UPPM modulation selector determines the UPPM modulation scheme. The DC of all final UPPM symbols may be determined in accordance with the current m-ary DC generated by the m-DC mapper or by a predefined DC. The preamble and delimiters signals are fed into all UPPM modulators to generate the parallel transmit signals. Pilot symbols (as described in clause 8.3.4.1) shall then be prepended to each transmit channel, which is then fed into multiple LED drivers and transmitted using visible light. + +NOTE – TX1 symbol frames may exist depending on the enabled channels. + +Frames are output on to the medium without inter-frame gaps. + +In the receive direction, a camera with a frame rate of $f_c$ is employed to detect and record all optical signals. The receiver exposure duration can be set to $T_e'$ to receive TX1 and TX2 symbol frames from both low-speed and high-speed channels or to receive TX2 symbol frames only from the high-speed channel via UPPM-based MIMO link. When the exposure is set to $T_e'$ , if at least two UPPM waveform segments of a TX port are received in a captured video frame, pilot symbols are first detected. Thereafter, multiple data streams from the high-speed channel can be obtained and a DC generated by an m-DC mapper from the low-speed channel may also be received. If at least two UPPM + +waveform segments of a TX port cannot be received, the exposure duration may be changed to $T_e$ to detect the optical signal to receive symbol frames in low-speed channel only. With the help of the preamble detection and PI extraction, the undersampled-recorded UPWM data from low-speed channel are compensated and demodulated if at least two UPPM waveform segments of a TX port are received in a captured video frame. After the pilot symbol detection processing, multiple UPPM channels can be obtained, with the help of preamble and delimiter detection, parallel recorded stripes from high-speed channel are processed and the obtained $VMPPM$ (e.g., V2PPM, V4PPM or V8PPM) signal are processed and demodulated in parallel. The DC mapper generated DCs from the low-speed channel may also be obtained if both high speed and low speed channels are enabled, then processed and demodulated. The recovered symbol frames from either the low-speed or the high-speed channel are transferred to the PMA via $\delta$ -reference point. The preamble are processed and the processing result are passed to the PHY management entity. + +![Functional model of the PMD in a UPPM-based MIMO transmission. The diagram shows TX1 and TX2 symbol frames entering an alpha-reference point. TX1 frames pass through an m-DC mapper, then a UPWM modulator, and finally a UPWM preamble generation block. TX2 frames pass through a UPPM modulation selector, then a UPPM modulator, and finally a UPPM delimiter/preamble generation block. Both paths lead to Digital LED drivers, which are connected to the Medium. RX1 and RX2 symbol frames are received from the Medium via a Camera. RX1 frames pass through UPWM preamble detection and PI extraction, then UPWM demodulation. RX2 frames pass through Pilot symbol detection, then UPPM preamble detection, then UPPM demodulation. All demodulated signals are sent to the PHY management entity. PMD control data is shown between the PHY management entity and the demodulation blocks. The MDI (Medium Dependent Interface) is indicated by a dashed line separating the internal PMD components from the external LED drivers and Camera.](284768c5ee1a05aa1b9ce396f606a040_img.jpg) + +``` + +graph TD + subgraph Transmitter + TX1[TX1 symbol frames] --> Alpha[alpha-reference point] + TX2[TX2 symbol frames] --> Alpha + Alpha --> MDC[m-DC mapper] + Alpha --> UPPM_Sel[UPPM modulation selector] + MDC --> UPWM_Mod[UPWM modulator] + UPPM_Sel --> UPPM_Mod[UPPM modulator] + UPWM_Mod --> UPWM_Pre[UPWM preamble generation] + UPPM_Mod --> UPPM_Del[UPPM delimiter/preamble generation] + UPWM_Pre --> Pilot_Gen[Pilot symbol generation] + UPPM_Del --> Pilot_Gen + Pilot_Gen --> LED[Digital LED drivers] + end + + LED --> Medium[Medium] + Medium --> Cam[Camera] + + subgraph Receiver + Cam --> UPWM_Pre_Det[UPWM preamble detection and PI extraction] + Cam --> Pilot_Det[Pilot symbol detection] + UPWM_Pre_Det --> UPWM_Demod[UPWM demodulation] + Pilot_Det --> UPPM_Pre_Det[UPPM preamble detection] + UPPM_Pre_Det --> UPPM_Demod[UPPM demodulation] + UPWM_Demod --> RX1[RX1 symbol frames] + UPPM_Demod --> RX2[RX2 symbol frames] + end + + RX1 --> PHY[PHY management] + RX2 --> PHY + PHY --> PMD_Ctrl[PMD control data] + PMD_Ctrl --> UPWM_Demod + PMD_Ctrl --> UPPM_Demod + +``` + +Functional model of the PMD in a UPPM-based MIMO transmission. The diagram shows TX1 and TX2 symbol frames entering an alpha-reference point. TX1 frames pass through an m-DC mapper, then a UPWM modulator, and finally a UPWM preamble generation block. TX2 frames pass through a UPPM modulation selector, then a UPPM modulator, and finally a UPPM delimiter/preamble generation block. Both paths lead to Digital LED drivers, which are connected to the Medium. RX1 and RX2 symbol frames are received from the Medium via a Camera. RX1 frames pass through UPWM preamble detection and PI extraction, then UPWM demodulation. RX2 frames pass through Pilot symbol detection, then UPPM preamble detection, then UPPM demodulation. All demodulated signals are sent to the PHY management entity. PMD control data is shown between the PHY management entity and the demodulation blocks. The MDI (Medium Dependent Interface) is indicated by a dashed line separating the internal PMD components from the external LED drivers and Camera. + +G.9992(19)\_F8-25 + +**Figure 8-25 – Functional model of the PMD in a UPPM-based MIMO transmission** + +#### 8.3.4.1 Pilot symbol + +A pilot symbol shall be used to indicate the TX port number in UPPM-based MIMO system. All pilot symbols shall be different and each pilot symbol shall represent one TX port. In the transmitting node which contains $N_2$ independent TX ports (where $N_2$ is an integer standing for the total number of parallel channel which varies from 2 to 4), $N_2$ different pilot symbols along with $N_2 \times M1$ UPPM symbols (as described in clause 8.3.3) shall be generated, where $M1$ is an integer representing the number of UPPM symbols for each TX port ( $M1 \geq 1$ ). After that $N_2$ different pilot symbols shall be prefixed to these $N_2 \times M1$ UPPM symbols synchronously, as shown in Figure 8-26, to make sure each pilot symbol corresponds to a unique TX port. Finally $N_2$ Pilot symbols and $N_2 \times M1$ UPPM symbols shall be sent via $N_2$ TX port, more specifically, each LED shall send one pilot symbol followed by the corresponding $M1$ UPPM. + +![Figure 8-26: UPPM-based MIMO streams diagram. It shows multiple transmission ports (Tx port #1, Tx port #2, ..., Tx port #N2) over time (t). Each port has a pilot symbol (Pilot 1, Pilot 2, ..., Pilot N) followed by UPPM symbols. The duration of each pilot symbol is Tc, and the duration of each UPPM symbol is also Tc. The segments are numbered #1, #2, #3, ..., #M1.](a2251e3bbfcd726b68cc50b091e53b02_img.jpg) + +Figure 8-26: UPPM-based MIMO streams diagram. It shows multiple transmission ports (Tx port #1, Tx port #2, ..., Tx port #N2) over time (t). Each port has a pilot symbol (Pilot 1, Pilot 2, ..., Pilot N) followed by UPPM symbols. The duration of each pilot symbol is Tc, and the duration of each UPPM symbol is also Tc. The segments are numbered #1, #2, #3, ..., #M1. + +**Figure 8-26 – UPPM-based MIMO streams** + +The duration of each pilot symbol shall be the same as the ordinary UPPM symbol $T_c$ , which is the reciprocal of the frame rate of the camera. Each pilot symbol shall comprise of $W$ ( $W = 2k$ ) segments which are $k$ identical odd-indexed segments and $k$ identical even-indexed segments, e.g., as shown in Table 8-23, $W = 4$ . Each odd-indexed segment shall be followed by an even-indexed segment. The average DCs (DCs) of the odd-indexed segments and the even-indexed segments shall be complementary and determined by the DC generated by a $m$ -DC mapper or by a predefined DC (e.g., if the DC generated by the $m$ -DC mapper is $D\%$ , then the average DC of the odd-indexed segments shall be $D\%$ , the average DC of the even-indexed segments shall be $1-D\%$ ). + +Table 8-23 shows the proposed structure of the pilot symbols for different port numbers. For $N_2 = 2$ , each segment (odd-indexed and even-indexed) comprises three regions, which are, a start delimiter region , an LED number indicating region (LNIR) and an end delimiter region (EDR), each region contains a number of PWM cycles with the same DC which equals to the average DC of the corresponding segment. While for $N_2 = 3$ and 4, each segment comprises five regions, which are, a SDR, the first LED Number Indicating region (LNIR#1), an interval delimiter region (IDR), the 2nd LED number indicating region (LNIR#2), and an EDR. Similarly, each region contains a number of PWM cycles with the same DC which also equals to the average DC of the corresponding segment. Note that, for all types of pilot symbols, the SDR and EDR are employed to indicate the beginning and the end of a segment of the pilot symbol, respectively. The IDR is used to separate two LNIRs (if applicable), the LNIR(s) is/are used to indicate the TX port number in UPPM-based MIMO system (if applicable) by sending PWM signals at different frequencies ( $N_2 = 2$ ) or different frequency groups ( $N_2 = 3$ or 4). + +**Table 8-23 – Waveform diagram of pilot symbols in UPPM-based MIMO transmission** + +| Number of Ports (N) | Port ID | Pilot symbol | +|---------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $N_2 = 2$ | TX port #1 |

Image: Waveform diagram of pilot symbols for N2=2. It shows a sequence of regions: SDR, LNIR, EDR, SDR, LNIR, EDR. The first SDR, LNIR, and EDR are grouped as 'Pilot 1' with duration Tc. The frequencies for each region are: SDR (f0), LNIR (f1), EDR (f0), SDR (f0), LNIR (f1), EDR (f0).

| + +**Table 8-23 – Waveform diagram of pilot symbols in UPPM-based MIMO transmission** + +| Number of Ports (N) | Port ID | Pilot symbol | +|---------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | TX port #2 | Waveform diagram for TX port #2. Top part shows 'Pilot 2' pulse with duration Tc. Bottom part shows a sequence of frequency blocks: SDR (f0), LNIR (f2), EDR (f0), SDR (f0), LNIR (f2), EDR (f0). Reference: G.9992(19)_T8-23.2 | +| N 2 = 3 | TX port #1 | Waveform diagram for TX port #1. Top part shows 'Pilot 1' pulse with duration Tc. Bottom part shows a sequence of frequency blocks: SDR (f0), LNIR#1 (f1), IDR (f0), LNIR#2 (f0), EDR (f0), SDR (f0), LNIR#1 (f1), IDR (f0), LNIR#2 (f0), EDR (f0). Reference: G.9992(19)_T8-23.3 | +| | TX port #2 | Waveform diagram for TX port #2. Top part shows 'Pilot 2' pulse with duration Tc. Bottom part shows a sequence of frequency blocks: SDR (f0), LNIR#1 (f0), IDR (f0), LNIR#2 (f1), EDR (f0), SDR (f0), LNIR#1 (f0), IDR (f0), LNIR#2 (f1), EDR (f0). Reference: G.9992(19)_T8-23.4 | +| | TX port #3 | Waveform diagram for TX port #3. Top part shows 'Pilot 3' pulse with duration Tc. Bottom part shows a sequence of frequency blocks: SDR (f0), LNIR#1 (f1), IDR (f0), LNIR#2 (f1), EDR (f0), SDR (f0), LNIR#1 (f1), IDR (f0), LNIR#2 (f1), EDR (f0). Reference: G.9992(19)_T8-23.5 | + +**Table 8-23 – Waveform diagram of pilot symbols in UPPM-based MIMO transmission** + +| Number of Ports (N) | Port ID | Pilot symbol | +|---------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N 2 = 4 | TX port #1 | Waveform diagram for TX port #1 showing Pilot 1 and frequency segments f0, f1, f2.

The diagram for TX port #1 shows a sequence of segments: SDR, LNIR#1, IDR, LNIR#2, EDR, SDR, LNIR#1, IDR, LNIR#2, EDR. Above the first SDR segment is 'Pilot 1' with a duration Tc. Frequencies are indicated below the segments: f0, f1, f0, f2, f0, f0, f1, f0, f2, f0. The label G.9992(19)_T8-23.6 is at the bottom right.

| +| | TX port #2 | Waveform diagram for TX port #2 showing Pilot 2 and frequency segments f0, f2, f1.

The diagram for TX port #2 shows the same segment sequence as port #1. Above the first SDR segment is 'Pilot 2' with a duration Tc. Frequencies are indicated below the segments: f0, f2, f0, f1, f0, f0, f2, f0, f1, f0. The label G.9992(19)_T8-23.7 is at the bottom right.

| +| | TX port #3 | Waveform diagram for TX port #3 showing Pilot 3 and frequency segments f0, f1, f2.

The diagram for TX port #3 shows the same segment sequence as port #1. Above the first SDR segment is 'Pilot 3' with a duration Tc. Frequencies are indicated below the segments: f0, f1, f0, f1, f0, f0, f1, f0, f1, f0. The label G.9992(19)_T8-23.8 is at the bottom right.

| +| | TX port #4 | Waveform diagram for TX port #4 showing Pilot 4 and frequency segments f0, f2, f1.

The diagram for TX port #4 shows the same segment sequence as port #1. Above the first SDR segment is 'Pilot 4' with a duration Tc. Frequencies are indicated below the segments: f0, f2, f0, f2, f0, f0, f2, f0, f2, f0. The label G.9992(19)_T8-23.9 is at the bottom right.

| + +Table 8-24 shows the related attributes and parameters for each section of different cases in accordance to Table 8-23. All frequencies given in Table 8-24 shall follow the following restrictions: $f_0 > 3/T_e'$ , $200\text{Hz} < f_1 < 2/T_e'$ , $200\text{Hz} < f_2 < 2/T_e'$ , and $f_1 < f_2$ . All time durations shall follow the following + +restrictions: if $N_2 = 2$ , $2 \times T_{\text{ppm}} + T_{\text{lnir}} = T_s = T_c/2k$ , else if $N_2 = 3$ or $N_2 = 4$ , $3 \times T_{\text{ppm}} + T_{\text{lnir1}} + T_{\text{lnir2}} = T_s = T_c/2k$ . The time duration of SDR and IDR and EDR are the same equals to $T_{\text{ppm}}$ . If $N_2 = 2$ , $T_{\text{lnir}}$ is the duration of LNIR#1. Else if $N_2 = 3$ or 4, $T_{\text{lnir1}}$ and $T_{\text{lnir2}}$ are the duration of LNIR#1 and LNIR#2, respectively. The number of PWM pulses in each region shall be an integer. + +Note that $f_1$ and $f_2$ can be any different frequencies as long as they could ensure that the total number of PWM pulses within the same period of $T_{\text{lnir}}$ or $T_{\text{lnir1}}$ or $T_{\text{lnir2}}$ are different. + +If the receiver records two parallel signals, when $N_2 = 2$ (there is only one LNIR in the whole segment), the receiver could determine that the transmitter has two TX ports and know the port number of each TX port. Similarly, when $N_2 = 3$ or 4, due to the unique preamble waveform, the receiver could also determine the total number of TX ports as well as their corresponding port number. + +**Table 8-24 – Specific value of pilot symbols in UPPM-based MIMO transmission** + +| TX port total number | Segment | Parameter | SDR | LNIR#1 | IDR | LNIR#2 | EDR | +|----------------------|---------------------------------|-----------------|------------------|--------------------|------------------|--------------------|------------------| +| $N_2 = 2$ | TX port #1 odd-indexed segment | PWM frequency | $f_0$ | $f_1$ | N/A | N/A | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir}}$ | N/A | N/A | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | N/A | N/A | $D\%$ | +| | TX port #1 even-indexed segment | PWM frequency | $f_0$ | $f_1$ | N/A | N/A | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir}}$ | N/A | N/A | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | N/A | N/A | $1-D\%$ | +| | TX port #2 odd-indexed segment | PWM frequency | $f_0$ | $f_2$ | N/A | N/A | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir}}$ | N/A | N/A | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | N/A | N/A | $D\%$ | +| | TX port #2 even-indexed segment | PWM frequency | $f_0$ | $f_2$ | N/A | N/A | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir}}$ | N/A | N/A | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | N/A | N/A | $1-D\%$ | +| $N_2 = 3$ | TX port #1 odd-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_0$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #1 even-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_0$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | + +**Table 8-24 – Specific value of pilot symbols in UPPM-based MIMO transmission** + +| TX port total number | Segment | Parameter | SDR | LNIR#1 | IDR | LNIR#2 | EDR | +|----------------------|---------------------------------|-----------------|------------------|--------------------|------------------|--------------------|------------------| +| $N_2 = 4$ | TX port #2 odd-indexed segment | PWM frequency | $f_0$ | $f_0$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #2 even-indexed segment | PWM frequency | $f_0$ | $f_0$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | +| | TX port #3 odd-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #3 even-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | +| $N_2 = 4$ | TX port #1 odd-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_2$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #1 even-indexed segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_2$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | +| | TX port #2 odd-indexed segment | PWM frequency | $f_0$ | $f_2$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #2 even-indexed segment | PWM frequency | $f_0$ | $f_2$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | + +**Table 8-24 – Specific value of pilot symbols in UPPM-based MIMO transmission** + +| TX port total number | Segment | Parameter | SDR | LNIR#1 | IDR | LNIR#2 | EDR | +|----------------------|---------------------------------------|-----------------|------------------|--------------------|------------------|--------------------|------------------| +| | TX port #3
odd-indexed
segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #3
even-indexed
segment | PWM frequency | $f_0$ | $f_1$ | $f_0$ | $f_1$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | +| | TX port #4
odd-indexed
segment | PWM frequency | $f_0$ | $f_2$ | $f_0$ | $f_2$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $D\%$ | $D\%$ | $D\%$ | $D\%$ | $D\%$ | +| | TX port #4
even-indexed
segment | PWM frequency | $f_0$ | $f_2$ | $f_0$ | $f_2$ | $f_0$ | +| | | region duration | $T_{\text{ppm}}$ | $T_{\text{lnir1}}$ | $T_{\text{ppm}}$ | $T_{\text{lnir2}}$ | $T_{\text{ppm}}$ | +| | | PWM DC | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | $1-D\%$ | + +### 8.3.5 PSD mask specifications + +See clause 8.1.5. + +### 8.3.6 Electrical specifications + +#### 8.3.6.1 Transmit clock tolerance + +See clause 8.1.6.1. + +### 8.3.7 Transmitter EVM requirements + +See clause 8.1.7. + +### 8.3.8 Termination impedance + +See clause 8.1.8. + +### 8.3.9 Total transmit power + +See clause 8.1.9. + +## 8.4 Control parameters + +**Table 8-25 – Parameters for PCS, PMA, PMD** + +| Parameter | Description | Value | +|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m$ | Modulation order of UPWM | 2, 3, 4, 6, 8, 12, 16, 23, 32 | +| $b$ | The number of bits in a UPWM symbol frame | 1, 2, 3, 4, 5 | +| $N_{sf}$ | $N_{sf}$ UPWM symbol frames shall be obtained for a TX PHY frame after segmentation process | $N_{sf} \geq 1$ , integer | +| $N_{sfl}$ | $2N_{sfl} + 2$ UPPM symbol frames shall be obtained for a TX PHY frame after segmentation process | $N_{sfl} \geq 0$ , integer | +| $N_{ppm}$ | The number PPM symbols within a valid data waveform | $N_{ppm} \geq 2$ , integer | +| $f_c$ | Camera's frame rate | 120 fps | +| $T_e$ | Exposure duration for UPWM | $1/2000\text{s} - 1/1000\text{s}$ | +| $T_e'$ | Exposure duration for UPWM and UPPM | $1/30000\text{s} - 1/15000\text{s}$ | +| $T_s$ | The duration of a segment of PWM waveform | $\leq 5\text{ms}$ | +| $T_p$ | The duration of a basic PWM cycle of a UPWM symbol | $\leq T_e/5$ | +| $k$ | An integer to make sure $T_s$ is less than 5 ms
$T_s = T_c/(2k)$ | $1/(240 T_s)$ | +| $T_c$ | The duration of a UPWM symbol
$T_c$ is the reciprocal of the camera's frame rate $f_c$ | $1/120\text{ s}$ | +| $T_{appm}$ | The duration of the basic PWM cycle in the first section of start delimiter of a UPPM preamble | $< T_e'/3$ | +| $T_{ppm}$ | The duration of the basic PPM cycle in the second section of start delimiter of a UPPM preamble or the duration of the basic PPM cycle of the valid data region of a UPPM waveform segment $W_{i1}$ or $W_{i2}$ | $\leq T_e/5$ | +| $W$ | The number of segments in pilot symbol (UPPM-based MIMO streams) | $2k$ | +| $f_0$ | Frequency of SDR, IDR, EDR | $f_0 > 3/T_e'$ | +| $f_1$ | One frequency of LNIR | $200\text{ Hz} < f_1 < 2/T_e'$ , and $f_1 < f_2$ | +| $f_2$ | One frequency of LNIR | $200\text{ Hz} < f_2 < 2/T_e'$ , and $f_1 < f_2$ | +| $T_{lnir}$ | The duration of LNIR | if $N_2 = 2$ , $2 \times T_{ppm} + T_{lnir} = T_s = T_c/2k$ , else if $N_2 = 3$ or $N_2 = 4$ , $3 \times T_{ppm} + T_{lnir1} + T_{lnir2} = T_s = T_c/2k$ | +| $T_{lnir1}$ | The duration of LNIR#1 | if $N_2 = 2$ , $2 \times T_{ppm} + T_{lnir} = T_s = T_c/2k$ , else if $N_2 = 3$ or $N_2 = 4$ , $3 \times T_{ppm} + T_{lnir1} + T_{lnir2} = T_s = T_c/2k$ | + +**Table 8-25 – Parameters for PCS, PMA, PMD** + +| Parameter | Description | Value | +|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| $T_{lnir2}$ | The duration of LNIR#2 | if $N_2 = 2$ , $2 \times T_{ppm} + T_{lnir} = T_s = T_c/2k$ , else if $N_2 = 3$ or $N_2 = 4$ , $3 \times T_{ppm} + T_{lnir1} + T_{lnir2} = T_s = T_c/2k$ | + +# 9 Data link layer specification + +## 9.1 Functional model of DLL and frame formats + +The functional model of the DLL is presented in Figure 9-1. The A-interface and PMI are respectively, two demarcation reference points between the AE and DLL and between the DLL and PHY. Internal reference points x1 and x2 respectively, show logical separation between the APC and LLC and between the LLC and MAC. + +![Functional model of the DLL diagram showing layers: Application protocol convergence (APC), Logical link control (LLC), and Media access control (MAC). It illustrates data flow from ADP in to MPDU out, and management messages from the DLL management entity.](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg) + +The diagram illustrates the functional model of the Data Link Layer (DLL). It shows three main layers stacked vertically, separated by reference points: + +- Application protocol convergence (APC):** The top layer, which interfaces with the AE. It receives ADP in and sends ADP out. It generates AAT data and high-level management messages for the DLL management entity. +- Logical link control (LLC):** The middle layer, which generates LLC and LPDU. It receives APDU from the APC and sends LPDU to the MAC. It receives LCDU data from the DLL management entity. +- Media access control (MAC):** The bottom layer, which handles the assembling of MPDUs. It receives LPDU from the LLC and sends MPDU out. It receives media access control parameters from the DLL management entity. + +Reference points are indicated by dashed horizontal lines: + +- A-interface:** The demarcation point between the AE and the APC. +- x1 reference point:** The logical separation between the APC and the LLC. +- x2 reference point:** The logical separation between the LLC and the MAC. +- PMI:** The demarcation point between the MAC and the PHY. + +Data flow is shown with arrows: ADP in and ADP out at the top; APDU and LPDU between APC and LLC; LPDU and MPDU between LLC and MAC; and finally MPDU out at the bottom. Management messages (AAT data, high-level management messages, LCDU data, and media access control parameters) are shown flowing from the DLL management entity to each layer. + +Functional model of the DLL diagram showing layers: Application protocol convergence (APC), Logical link control (LLC), and Media access control (MAC). It illustrates data flow from ADP in to MPDU out, and management messages from the DLL management entity. + +**Figure 9-1 – Functional model of the DLL** + +In the transmit direction, application data primitives (ADPs) enter the DLL from the AE via the A-interface. Every incoming ADP set meets the format defined by the particular application protocol. For an Ethernet type AE, the ADP set has one of the standard Ethernet formats, as presented in Annex A (Ethernet APC). Each incoming ADP set is converted by the APC into application protocol data units (APDUs), which includes all parts of the ADP intended for communication to the destination node(s). The APC is responsible for forwarding APDUs to peers APCs. + +The APC transfers APDUs to the LLC via the x1 reference point which is application independent. The LLC also receives from the DLL management entity, sets of management data primitives for LLC control frames which are mapped into link control data units (LCDU). The LLC is responsible for establishing the exchange of LCDUs (management frames) between peer LLCs. + +In the LLC, the incoming APDU and LCDU are mapped into LLC frames. Each LLC frame is treated as an LLC protocol data units (LPDU) and then passed to the MAC via the x2 reference point. + +The MAC is responsible for concatenating LPDUs into MPDUs and then conveying these MPDUs to the PHY via the PMI. + +In the receive direction, MPDUs from the PHY enter via the PMI. The MAC disassembles the received MPDUs into LPDUs which are passed over the x2 reference point to the LLC. The LLC recovers the original APDUs and LCDUs from the received LPDUs, and conveys them to the APC and the LLC management entity, respectively. In the APC, the ADPs are recovered from the received APDUs and conveyed to the AE. + +NOTE – No assumptions should be made on the partitioning of APC, LLC, and MAC in particular implementations; x1 and x2 are reference points and serve exclusively for the convenience of system definition. + +### 9.1.1 Application protocol convergence sublayer + +The functional model of the application protocol convergence (APC) is presented in Figure 9-2. It is intended to describe in more detail the APC functional block presented in Figure 9-1. + +![Figure 9-2 – Functional model of the APC. This block diagram illustrates the data flow and functional components of the Application Protocol Convergence (APC) sublayer. At the top, 'ADP in' enters from the left, passing through an 'A-interface' (dashed line) into an 'ADP-to-APDU converter'. This converter outputs to a 'Queue mapper', which also receives a 'Destination DEVICE_ID' input. The 'Queue mapper' outputs 'TX APDU' at the bottom, crossing the 'x1 reference point' (dashed line). On the right side, 'RX APDU' enters from the bottom, crossing the 'x1 reference point' into a 'Dispatcher'. The 'Dispatcher' sends 'Local in-band message' and 'Remote in-band message' to a 'DLL management' entity at the top right. The 'Dispatcher' also outputs to an 'APDU-to-ADP converter', which produces 'ADP out' at the top, crossing the 'A-interface'. A central 'AAT (local and remote)' block receives 'AAT data' from the 'DLL management' entity and provides input to the 'ADP-to-APDU converter' and 'Queue mapper'. The 'DLL management' entity also receives 'Local in-band management' from the 'ADP out' path.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +Figure 9-2 – Functional model of the APC. This block diagram illustrates the data flow and functional components of the Application Protocol Convergence (APC) sublayer. At the top, 'ADP in' enters from the left, passing through an 'A-interface' (dashed line) into an 'ADP-to-APDU converter'. This converter outputs to a 'Queue mapper', which also receives a 'Destination DEVICE\_ID' input. The 'Queue mapper' outputs 'TX APDU' at the bottom, crossing the 'x1 reference point' (dashed line). On the right side, 'RX APDU' enters from the bottom, crossing the 'x1 reference point' into a 'Dispatcher'. The 'Dispatcher' sends 'Local in-band message' and 'Remote in-band message' to a 'DLL management' entity at the top right. The 'Dispatcher' also outputs to an 'APDU-to-ADP converter', which produces 'ADP out' at the top, crossing the 'A-interface'. A central 'AAT (local and remote)' block receives 'AAT data' from the 'DLL management' entity and provides input to the 'ADP-to-APDU converter' and 'Queue mapper'. The 'DLL management' entity also receives 'Local in-band management' from the 'ADP out' path. + +Figure 9-2 – Functional model of the APC + +In the transmit direction, the incoming ADP data unit is converted into an APDU as defined in Annex A. The queue mapper maps APDUs into queues depending on their destination DEVICE\_ID. After mapping, each APDU is sent to the LLC via the x1 reference point. + +The data units of the in-band management messages arriving across the A-interface and addressed to the local node are directed to the DLL management entity ("Local in-band management", at the bottom of Figure 9-2). The in-band management messages generated by DLL management entity for the remote AE are converted to APDUs, and sent across the x1 reference point ("Remote in-band management" at the top of Figure 9-2). + +In the receive direction, the APDUs incoming via the x1 reference point are converted back into the ADP set of the corresponding application protocol. + +If addressed to the node, APDUs carrying in-band management messages from the remote AE are dispatched to the DLL management entity ("Remote in-band management" at the bottom of Figure 9-2). If addressed to the local AE, APDUs carrying in-band management messages from the + +remote AE are converted to a standard ADP and passed to A-interface. The in-band management messages (e.g., responses) generated by DLL management entity for the local AE are sent to the AE across the A-interface as standard sets of data unit primitives ("Local in-band management" at the top of Figure 9-2). + +The local address association table (LAAT) contains in its first entry the MAC address of the node itself (i.e., REGID) and, in the rest of the table, the MAC addresses of the clients associated with the node. This data is collected from the incoming ADP data units. LAAT data is passed to the DLL management entity for network management purposes (see clause 8.5.3). + +The remote address association table (RAAT) stores MAC addresses of other nodes in the domain. + +The address association table (AAT) is formed by the aggregation of LAAT and RAAT. + +### 9.1.2 Logical link control sublayer + +The functional model of the LLC is presented in Figure 9-3. It is intended to describe in more detail the LLC functional block presented in Figure 9-1. + +![Figure 9-3 – Functional model of LLC. The diagram shows the flow of data through the LLC sublayer. On the left, 'APDU in' enters from the top, passing through the 'x1 reference point' (dashed line) into a block labeled 'Assembling of LLC frame'. Below this block, the data exits through the 'x2 reference point' (dashed line) as 'TX LPDU'. On the right, 'RX LPDU' enters from the bottom, passing through the 'x2 reference point' into a block labeled 'Removing LFH'. Above this block, the data exits through the 'x1 reference point' as 'APDU out'. A 'DLL management' block on the far right is connected to both the 'Assembling of LLC frame' and 'Removing LFH' blocks via 'TX LCDU data' and 'RX LCDU data' lines. A 'Generation of LCDU' block is also shown, connected to the 'Assembling of LLC frame' block. The diagram is labeled G.9992(19)_F9-3.](91134b9a38d7f73f03375473e7b706f9_img.jpg) + +Figure 9-3 – Functional model of LLC. The diagram shows the flow of data through the LLC sublayer. On the left, 'APDU in' enters from the top, passing through the 'x1 reference point' (dashed line) into a block labeled 'Assembling of LLC frame'. Below this block, the data exits through the 'x2 reference point' (dashed line) as 'TX LPDU'. On the right, 'RX LPDU' enters from the bottom, passing through the 'x2 reference point' into a block labeled 'Removing LFH'. Above this block, the data exits through the 'x1 reference point' as 'APDU out'. A 'DLL management' block on the far right is connected to both the 'Assembling of LLC frame' and 'Removing LFH' blocks via 'TX LCDU data' and 'RX LCDU data' lines. A 'Generation of LCDU' block is also shown, connected to the 'Assembling of LLC frame' block. The diagram is labeled G.9992(19)\_F9-3. + +**Figure 9-3 – Functional model of LLC** + +In the transmit direction, an LLC frame is formed from each APDU entering via the x1 reference point. Each LLC frame is treated as an LPDU. + +The LCDU carries management data and has a format as defined in clause 9.1.2.1.3. + +In the receive direction, the LPDUs disassembled from the incoming MPDU in the MAC and enter the LLC via the x2 reference point. The LLC then recovers the LLC frames from the received LPDUs. The payloads of the recovered LLC frames are passed to the APC via an x1 reference point, if they were carrying an APDU or to the DLL management, if they were carrying an LCDU. + +#### 9.1.2.1 LLC frame format + +The LLC frame is formed from either an APDU or an LCDU, with a format as described in Figure 9-4. + +![Diagram of LLC frame format showing the mapping of APDU or LCDU to the LLC frame structure. At the top, 'APDU at x1 reference point or LCDU' is shown. Below it, a box labeled 'APDU or LCDU' is split into two parts: 'LFH' (LLC frame header) and 'APDU or LCDU' (the data part). Arrows indicate the flow from the top APDU/LCDU to the LFH and the data part of the LLC frame. The diagram is labeled 'G.9992(19)_F9-4'.](fd8f5da2b60cdca94896f3cde8ee81f0_img.jpg) + +Diagram of LLC frame format showing the mapping of APDU or LCDU to the LLC frame structure. At the top, 'APDU at x1 reference point or LCDU' is shown. Below it, a box labeled 'APDU or LCDU' is split into two parts: 'LFH' (LLC frame header) and 'APDU or LCDU' (the data part). Arrows indicate the flow from the top APDU/LCDU to the LFH and the data part of the LLC frame. The diagram is labeled 'G.9992(19)\_F9-4'. + +**Figure 9-4 – LLC frame format** + +##### 9.1.2.1.1 LLC frame header + +The LLC frame header (LFH) shall be composed of the fields described in Table 9-1. The LFH is variable in length. Octet 0 shall be passed to the MAC first. + +**Table 9-1 – LFH fields format** + +| Field | Octet | Bits | Definition | +|-----------------|---------|--------|--------------------------------------------------------------------------------------------| +| LLCFT | 0 and 1 | [2:0] | LLC frame type | +| FLEN | | [15:3] | LLC frame body length in bytes | +| OriginatingNode | 2 | [7:0] | DEVICE_ID of the node that created the LLC frame | +| DestinationNode | 3 | [7:0] | Destination identifier that indicates the node(s) where the LLC frame is finally destined. | + +###### 9.1.2.1.1.1 LLC frame type (LLCFT) + +The LLCFT field is a 4-bit field that indicates the type of APDU that makes up the LLC frame. It is formatted as a 3-bit unsigned integer. Table 9-2 lists the valid LLC frame types. + +**Table 9-2 – LLC frame types** + +| LLC frame type | Value | +|-------------------------|-------| +| Padding frame | 0 | +| Management frame (LCDU) | 1 | +| Data frame (APDU) | 2 | +| Reserved | 3-7 | + +###### 9.1.2.1.1.2 Frame length + +The frame length (FLEN) field indicates the length in bytes of the frame contained within the LLC frame. This is the actual length of the LLC frame excluding the LFH. It is formatted as a 13-bit unsigned integer. + +###### 9.1.2.1.1.3 OriginatingNode + +The OriginatingNode field carries the DEVICE\_ID of the node that originated the LLC frame. For unidirectional broadcasting mode, the OriginatingNode field shall be set to 1, which indicates the DEVICE\_ID of the domain master. + +###### 9.1.2.1.1.4 DestinationNode + +The DestinationNode field indicates one or more nodes where the LLC frame is finally destined. It shall be set to BROADCAST\_ID by the originating node. + +##### 9.1.2.1.2 LCDU frame format + +The LCDU frame format, including the size of the fields, shall be as presented in Figure 9-5. + +| | LSB | MSB | +|------------------|---------------------------------|-----| +| 6 octets | Destination (MAC address) | | +| 6 octets | Source (MAC address) | | +| 2 octets | EtherType (22E3 16 ) | | +| 6 to 1500 octets | LCDU payload | | +| | PAD | | +| 4 octets | FCS | | + +G.9992(19)\_F9-5 + +**Figure 9-5 – LCDU format** + +The LCDU is identified at the destination node by its source/destination MAC address. The EtherType field is intended to identify the management message. The content of the EtherType field shall be 22E316. + +The PAD field shall complete the total length of LCDU to its minimum value of 64 bytes. The PAD field, if present, shall be set to zero. + +The frame check sequence (FCS) shall be computed over all LCDU fields, from the first bit (LSB) of the destination MAC address field to the last bit (MSB) of the PAD using the standard IEEE 802.3 Ethernet 32-bit FCS computation algorithm. The FCS field shall not be included when MIC is used in the LLC frame encapsulating the LCDU. + +Bits of LCDU shall be transmitted starting from the first octet of the destination MAC address. + +The encapsulation of LCDUs into LLC frames is described in Figure 9-6. + +NOTE – The format of the LCDU payload is for further study. + +![](a02b188a5fd52c99f84255322873bf29_img.jpg) + +| | | | | | +|------------------------|-------------------------------------------------------------------------|--------------------------------------|--|-----| +| LLC frame | | | | | +| LLC
frame
header | LCDU | | | | +| | Destination (MAC address)
Source (MAC address)
EtherType (0×22E3) | LCDU payload
(management message) | | FCS | +| MMH | Parameter list (MMPL) | | | | + +G.9992(19)\_F9-6 + +**Figure 9-6 – Encapsulation of an LCDU into an LLC frame** + +##### 9.1.2.1.3 APDU frame format + +APDU frame format are presented in Annex A. + +### 9.1.3 Medium access control sublayer + +The functional model of the MAC is presented in Figure 9-7. It is intended to describe in more detail the MAC functional block presented in Figure 9-1. + +![Figure 9-7: Functional model of MAC. This block diagram shows the flow of data through the MAC layer. On the left, 'LPDU in' enters from above the 'x2 reference point' (indicated by a dashed line). It goes into an 'MPDU assembler', which outputs to a 'Scheduler'. The 'Scheduler' outputs 'TX MPDU' below the 'PMI' (Physical Medium Interface) reference point. On the right, 'RX MPDU' enters from below the 'PMI' reference point, goes into an 'MPDU disassembler', which outputs 'LPDU out' above the 'x2 reference point'. A 'Media access control' line connects the 'MPDU assembler', 'Scheduler', and 'MPDU disassembler' to a 'DLL management' block on the far right. The diagram is labeled 'G.9992(19)_F9-7'.](15de63f0b5df62e6ab9164f2a72e2e33_img.jpg) + +Figure 9-7: Functional model of MAC. This block diagram shows the flow of data through the MAC layer. On the left, 'LPDU in' enters from above the 'x2 reference point' (indicated by a dashed line). It goes into an 'MPDU assembler', which outputs to a 'Scheduler'. The 'Scheduler' outputs 'TX MPDU' below the 'PMI' (Physical Medium Interface) reference point. On the right, 'RX MPDU' enters from below the 'PMI' reference point, goes into an 'MPDU disassembler', which outputs 'LPDU out' above the 'x2 reference point'. A 'Media access control' line connects the 'MPDU assembler', 'Scheduler', and 'MPDU disassembler' to a 'DLL management' block on the far right. The diagram is labeled 'G.9992(19)\_F9-7'. + +**Figure 9-7– Functional model of MAC** + +In the transmit direction, MPDUs are assembled from LPDUs passed over the x2 reference point. The MPDU is then passed to the PHY across the PMI. The octet 0 of the LPH of the LPDU#1 of the MPDU (see Figure 9-8) shall be passed to the PHY first. + +In the receive direction, the incoming MPDU is disassembled and the resulting LPDUs are passed to the LLC over the x2 reference point. + +#### 9.1.3.1 Assembling of MPDUs + +The process of assembling an MPDU from one or more LPDUs is presented in Figure 9-8. + +To form the MPDU, LPDUs are concatenated by the MAC in the same order as received across the x2 reference point + +![Figure 9-8: Assembling of an MPDU from LPDUs. This diagram shows the structure of an MPDU. At the top, an 'LPDU' is shown with two fields: 'LFH' (Logical Frame Header) and 'APDU or LCDU'. Below, the 'MPDU' structure is shown as a concatenation of multiple LPDUs: 'LPDU #1', 'LPDU #2', an ellipsis '...', 'LPDU #n', and a 'Padding LPDU' (highlighted in yellow). Dashed lines connect the 'LPDU' structure to the 'MPDU' structure. The diagram is labeled 'G.9992(19)_F9-8'.](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +Figure 9-8: Assembling of an MPDU from LPDUs. This diagram shows the structure of an MPDU. At the top, an 'LPDU' is shown with two fields: 'LFH' (Logical Frame Header) and 'APDU or LCDU'. Below, the 'MPDU' structure is shown as a concatenation of multiple LPDUs: 'LPDU #1', 'LPDU #2', an ellipsis '...', 'LPDU #n', and a 'Padding LPDU' (highlighted in yellow). Dashed lines connect the 'LPDU' structure to the 'MPDU' structure. The diagram is labeled 'G.9992(19)\_F9-8'. + +**Figure 9-8 – Assembling of an MPDU from LPDUs** + +Padding LPDUs, if present, shall be placed at the end of the MPDU, see Figure 9-8, and shall be indicated as "padding frame" in the LLC frame header (see clause 9.1.2.1.1.1). + +## 9.2 Addressing scheme + +### 9.2.1 Node identifier + +The following two node identification parameters shall be used: + +- DEVICE\_ID; +- BROADCAST\_ID. + +The DEVICE\_ID shall be represented by an 8-bit unsigned integer with valid values in the range from zero to 250 as presented in Table 9-3. When a node decides to start a new domain by becoming its domain master, it shall have an assigned DEVICE\_ID, which shall be 1. For unidirectional broadcasting mode, all the endpoint node shall set the DEVICE\_ID to the default DEVICE\_ID. A BROADCAST\_ID is a DEVICE\_ID with a fixed value of 255 and shall be used for broadcast transmission only. + +**Table 9-3 – Definition and valid values of node identification parameters** + +| Parameter | Valid values | Description | +|--------------|--------------|-----------------------------------------------------| +| DEVICE_ID | 0 | The default DEVICE_ID | +| | 1 | ID reserved for the domain master | +| | 2 to 254 | Reserved by ITU-T | +| BROADCAST_ID | 255 | A special value of DEVICE_ID reserved for broadcast | + +### 9.2.2 Address association table + +Each node can have one or more applications associated with its AE (above its A-interface). Each application is identified by a unique 6-octet MAC address. Each node shall maintain the full list of MAC addresses associated with applications above its A-interface as well as its own MAC address. This list is referred to as an LAAT. + +NOTE 1 – The list of MAC addresses associated with applications above its A-interface for a node can be populated by learning, or directly programmed by the DLL management entity. + +Each node shall also maintain the list of MAC addresses associated with the AEs of other nodes in the domain and the MAC addresses of those nodes. This list is referred to as an RAAT. + +The AAT is formed by the aggregation of the LAAT and the RAAT. + +NOTE 2 – The routing of ADPs is for further study. + +# Annex A + +## Application protocol convergence sublayer + +(This annex forms an integral part of this Recommendation.) + +The application protocol convergence (APC) specific sublayer maps the primitives of the application protocol used by the application entity (AE) into the native protocol of the data link layer. It is the responsibility of the APC to convert incoming data units of the particular application protocol used by the AE into application protocol data units (APDUs) and map them onto the queues. + +By default, APC shall support Ethernet, while other protocols can also be supported. + +The description of APC in this annex is partitioned into a data plane and a management plane. The data plane part specifies converging of the AE data units into APDUs and back. The functional model of the data plane is presented in Figures 9-1 and 9-2. The part dealing with management plane specifies APC primitives and protocols related to APC peer-to-peer management. + +## A.1 Ethernet APC + +The Ethernet APC (EAPC) is intended to operate with an Ethernet AE which supports IEEE bridging and switching protocols such as [IEEE 802.1D], [IEEE 802.1Q], [IEEE 802.1ad] (QinQ). Inter-domain bridging and bridging to alien domains implemented by the AE are beyond the scope of this Recommendation. The APC converts the standard set of primitives (at the MAC SAP, in terms of [IEEE 802.3], and those defined as internal sublayer services in terms of [IEEE 802.1]) at the A-interface into an APDU, which is further communicated through the domain to the peer APC. The APC shall accommodate the differences in primitive sets of different versions of [IEEE 802.3] and [IEEE 802.1] by substituting default values, as described in clause A.1.1. + +### A.1.1 Frame conversion + +The incoming set of primitives (AIF\_DATA.REQ) and the outgoing set of primitives (AIF\_DATA.IND) at the A-interface of EAPC represent a sequence of Ethernet frames, each defined as a set of IEEE 802.1 primitives of M\_UNITDATA.request and M\_UNITDATA.indication, respectively, Table A.1. + +**Table A.1 – A-interface primitives description** + +| AIF_DATA.REQ
(AE → EAPC) | AIF_DATA.IND
(EAPC → AE) | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M_UNITDATA.request
(
frame_type,
destination_address,
source_address,
mac_service_data_unit,
user_priority,
access_priority,
frame_check_sequence
) | M_UNITDATA.indication
(
frame_type,
destination_address,
source_address,
mac_service_data_unit,
user_priority,
frame_check_sequence
) | + +All unit-signal primitives specified in Table A.1 shall be interpreted in terms of clause 6.4 of [IEEE 802.1D]. Note that primitives frame\_type, user\_priority, access\_priority, and + +frame\_check\_sequence, may not be provided by the AE, and primitives frame\_type and user\_priority may not be requested by the AE. + +NOTE 1 – Clause 6.5.1 of [IEEE 802.1D] suggests that the "access priority" primitive be ignored and the frame\_type primitive be set to user\_data\_type for IEEE 802.3 MAC frames. + +NOTE 2 – The M\_UNITDATA.request description in [IEEE 802.1Q] differs from that in [IEEE 802.1D] as it omits the frame\_type and access\_priority parameters. The frame\_type is not required in [IEEE 802.1Q] as the receipt of a frame other than a user data frame does not cause a data indication, nor are such frames transmitted by the medium independent bridge functions. The mapping of M\_UNITDATA.request to particular access methods specified in [IEEE 802.1Q] includes derivation of the access\_priority parameter (for those media that require it) from the user\_priority parameter. + +NOTE 3 – The EM\_UNITDATA.request and EM\_UNITDATA.indication description in [IEEE 802.1ad] includes more quality of service related primitives, such as drop\_eligible and others. These primitives, similarly to those defined in clause 6.6.1 of [IEEE 802.1Q] should be accommodated in the corresponding tags fields of the APDU as described in Table A.1. + +If the frame\_check\_sequence primitive is provided by the AE, the incoming M\_UNITDATA.request primitives (described in Table A.1 for AIF\_DATA.REQ) shall be verified to be error free by computing their frame check sequence (FCS) as defined in clause 6.5.1 of [IEEE 802.1D]. If the computed FCS does not match the received value of the frame\_check\_sequence, the incoming primitive shall be discarded. If the frame\_check\_sequence primitive is not provided by the AE, the APC shall compute the FCS of the incoming M\_UNITDATA.request primitives as defined in clause 3.28 of [IEEE 802.3]. + +Error-free primitives described in Table A.1 for AIF\_DATA.REQ shall be converted into the APDU format presented in Figure A.1. The same APDU format shall be used for in-band management messages sourced by the local DLL management entity for the remote AE. + +| | | +|-----------------------|-------------------------------------| +| 6 octets | Destination address | +| 6 octets | Source address | +| 2 octets | MAC client length/EtherType | +| Application dependent | Service data unit
(APDU payload) | +| 4 octets | Frame check sequence (FCS) | + +**Figure A.1 – APDU format (TX and RX)** + +All fields shall have the same content as the corresponding fields of the MAC frame defined in [IEEE 802.3]. + +When sending a broadcast in-band management message (e.g., message addressed to all ITU-T G.9992 nodes), the EtherType tag shall be set to 22E316. + +Bits of APDU shall be transmitted starting from the first octet of the destination address. The least significant bit of each octet shall be transmitted first. The most significant octet of each field shall be transmitted first. + +The order of outgoing APDUs at the x1 reference point associated with a particular destination shall be the same as the order of incoming unit-data of the same destination. + +The M\_UNITDATA.indication primitives shall be derived from the APDUs received from the LLC across the x1 reference point as defined in clause 6.4.1 of [IEEE 802.1D], with the following additional rules: + +- The frame\_check\_sequence primitive, if FCS is not a part of APDU, it shall be computed as defined in clause 3.28 of [IEEE 802.3]. +- The frame\_check\_sequence primitive, if FCS is a part of APDU, it shall be verified as defined in clause 6.5.1 of [IEEE 802.1D]. APDUs that did not pass verification shall be discarded. + +The same rules shall also be used to derive the M\_UNITDATA.indication primitives for the in-band management messages sourced by the DLL management entity for the local AE. + +The payload of in-band management data units generated by the DLL management entity shall follow the link control data unit (LCDU) payload format defined in clause 9.1.2.1.2. + +### **A.1.2 Management plane** + +The management plane of the EAPC is for further study. + +## **A.2 Other types of APC** + +Other types of APC are for further study. + +# Bibliography + +- [b-ITU-T G.9960] Recommendation ITU-T G.9960 (2018), *Unified high-speed wireline-based home networking transceivers – System architecture and physical layer specification.* +- [b-TR-069]) Broadband Forum, Technical Report 069 (2018), *CPE WAN Management Protocol.* + + + + + +# 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