अtनवाय‘ आव9यकताओं का अनुल#नक संo: टीईसी/एसडी/डीडी/टीसीपी-222/2.8/जलाई2021
ANNEXURES TO ERs
No.:TEC/SD/DD/TCP-xxxxxxxxxx
अिनवाय´ आवªकताओं म” इंअ गत मानकⴂ का अ ववरण
संªरण-2.8
DETAILS OF STANDARDS SPECIFIED IN ESSENTIAL REQUIREMENTS VERSION-2.8
© टीईसी 2021
© TEC 2021
भारतसरकार GOVERNMENT OF INDIA
द ू रसंचारअिभयांअ 7कीक” \
खुशf饍 लालभवन, जनपथ,नईईदWीी -110001, भारत
TELECOMMUNICATION ENGINEERING CENTRE KHURSHID LAL BHAWAN, JANPATH, NEW DELHI – 110001 www.tec.gov.in
1. INDEXINDEX ...... ii 2. Annexure-A1: Safety Requirement for Communication Equipment ...... 9 3. Annexure-A2: Safety Requirement for Battery in portable equipment ...... 10 4. Annexure-B: EMI/ EMC Requirement ...... 11 5. Annexure- B1: Emission limits as per CISPR22 ...... 20 6. Annexure-D: Parameters for 2-wire PSTN Lines, Trunks lines and CPEs connected thereon (INT2W & CPE2W) ...... 34 7. Annexure-G1: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands of 2.4 GHz and 5 GHz ...... 54 8. Annexure-G2: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands of 2.4 GHz and 5 GHz ...... 54 9. Annexure-G3: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands of 2.4 GHz and 5 GHz ...... 56 10. Annexure-H: Ethernet Interface Parameters...... 2 11. Annexure-I: PDH Interface Parameters ...... 4 12. Annexure-J1: xDSL Interface Parameters ...... 8 13. Annexure-J2: PON Interface Parameters ...... 10 14. Annexure-J3: PON Conformance Parameters ...... 20
Annexure to ERs – 2.8/ July2021 ii 15. Annexure J4 – DSLAM Functional Test ...... 23 16. Annexure-K: SDH Interface Parameters ...... 27 17. Annexure-P6: IP Conformance Parameters – IPV4 and Dual Stack – RFC 791 and RFC 4213...... 46 18. Annexure-P7: IPv6 Conformance Parameters ...... 49 1. Table-3: IPV6 as per RFC 2460 ...... 99 2. Table-4: IPV6 as per RFC 4861 ...... 100 3. Table-5: IPV6 as per RFC 4862 ...... 101 4. Table-6: IPV6 as per RFC 1981 ...... 102 5. Table-7: IPV6 as per RFC 4443 ...... 103
Annexure to ERs – 2.8/ July2021 iii
IMPORTANT NOTICE
1. The RFC documents of IETF are subject to periodic revision. Hence, wherever RFCs are mentioned in the ERs/ Annexures to ERs, the offered product shall meet either the referred RFC or its latest/ later version. Wherever, a feature of the RFC is mentioned, product shall comply with the part of the RFC specifying the feature.
2. Similarly, this applies to other standards of IEC, EN, CISPR, ETSI, ITU, IEEE, TEC etc.
DISCLAIMER
1. The Annexures and Appendices in this document are being reviewed and the updated version shall be uploaded on MTCTE Portal www.mtcte.tec.gov.in from time to time. 2. Feedback for corrections, if any, may be sent on email to [email protected] with copy to [email protected]
Annexure to ERs – 2.8/ July2021 iv Annexure-A1: Safety Requirement for Communication Equipment ParameterGroup: SAFETY
S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks A1.1 IT Equipment Safety IS 13252 part 1: 2010 Amd 2013 Compliance to clauses Older version of standard shall be &Amd 2015 “Information applicable to the EUT accepted if it was in force on the date of Technology Equipment –Safety- issue of report. Part 1: General Requirements” or equivalent IEC standard –EN/IEC 60950-1:2005+A1:2009+A2:2013 “Information Technology Equipment –Safety- Part 1: General Requirements
OR
EN/IEC 62368-1:2014
A1.2 Ingress Protection IEC 60529 Compliance to clauses As per offered product category applicable to the EUT
Annexure to ERs – 2.8/ July2021 9 Annexure-B: EMI/ EMC Requirement (Additional details, referred clauses and Tables in TEC EMI EMC document TEC/SD/DD/EMC-221/05/OCT-16) Parameter Group: EMC S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.1 Conducted emission - Class CISPR22 (2008)/ EN 55022 AC/ DC Power input/ output Conducted Emission for Class A A OR ports: equipment as per applicable clauses/ As per Table 7 of Annexure B1 ranges. CISPR32 (2015)/EN 55032 for CISPR 22 and applicable Table(s) in CISPR 32. Test reports as per CISPR 22 (2008)/ EN 55022 shall be acceptable only Telecom Ports: till 31.03.2020. As per Table 8B of Annexure B1 and applicable Table(s) in CISPR 32.
Annexure to ERs – 2.8/ July2021 10 B.2 Radiated emission - Class A CISPR22 (2008)/ EN 55022 For CISPR 22: Radiated Emission for Class A equipment as per applicable clauses/ OR i. For 10 m measuring ranges. distance: CISPR32 (2015)/EN 55032 As per Table 5a (Refer Annex Test reports as per CISPR 22 (2008)/ B1) for frequency range up to 1 EN 55022 shall be acceptable only GHz. till 31.03.2020.
ii. For 3 m measuring distance: As per Table 5a1 (Refer Annex- B1) for frequency range up to 1 GHz.
iii. For 3 m measuring distance: As per Table 5b (Refer Annex B1) frequency range beyond 1 GHz.
For CISPR 32:
Limits for Class A Radiated Emissions from applicable Tables of CISPR 32 for distances of 3m or 10m.
Note: For 3m measuring distance, EUT size should be as such it fits in a cylindrical area of diameter 1m.
For other equipment, measuring distance of 10m is applicable.
Annexure to ERs – 2.8/ July2021 11 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.3 Conducted emission - Class CISPR22 (2008)/ EN 55022 AC/ DC Power input/ output Conducted Emission for Class B B OR ports: equipment as per applicable clauses/ As per Table 6 of Annexure B1 ranges. CISPR32 (2015)/EN 55032 for CISPR 22/EN 55022 Test reports as per CISPR 22 (2008)/ Telecom Ports: EN 55022 shall be acceptable only As per Table 8A of Annexure till 31.03.2020. B1 for CISPR 22/EN 55022 and applicable Table(s) in CISPR 32/EN 55032
Annexure to ERs – 2.8/ July2021 12 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.4 Radiated emission - Class B CISPR22 (2008)/ EN 55022 For CISPR 22: Radiated Emission for Class B OR i. For 10 m measuring equipment as per applicable clauses/ distance: ranges. CISPR32 (2015)/EN 55032 As per Table 4a for frequency range up to 1 GHz. Test reports as per CISPR 22 (2008)/ EN 55022 shall be acceptable only ii. For 3 m measuring till 31.03.2020. distance: As per Table 4a1 for frequency range up to 1 GHz.
iii. For 3 m measuring distance: As per Table 4b for frequency range beyond 1 GHz.
For CISPR 32:
Limits for Class B Radiated Emissions from applicable Tables of CISPR 32 for distances of 3m or 10m.
Note: For 3m measuring distance, EUT size should be as such it fits in a cylindrical area of diameter 1m.
For other equipment, measuring distance of 10m is applicable.
Annexure to ERs – 2.8/ July2021 13 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.5 Conducted and Radiated CISPR14-1 (2016) Conducted and Radiated Emission Emission - Electrical applicable to Electricity Meter Appliances
B.6 Immunity to Electrostatic EN/IEC 61000-4-2(2008) Level 2 {± 4 kV}, or higher Discharge Contact discharge voltage; Performance Criteria B
B.7 Immunity to Electrostatic EN/IEC 61000-4-2(2008) Level 3 {± 8 kV} or higher Discharge Air discharge voltage; Performance Criteria B B.8 Immunity to Electrostatic EN/IEC 61000-4-2(2008) Level 4 {± 8 kV}; Applicable to Electricity Meter Discharge- Level-4 Contact Discharge Performance Criteria B
B.9 Immunity to Electrostatic EN/IEC 61000-4-2(2008) Level 4 {± 15 kV}; Applicable to Electricity Meter Discharge- Level-4 Air Discharge Performance Criteria B
B.10 Immunity to radiated RF EN/IEC 61000-4-3(2010) i. Test level 2 {Test field Clauses applicable to Telecom strength of 3 V/m} for Equipment or Telecom Terminal 80 MHz to 1 GHz; Equipment with voice interface. Performance Criteria A. ii. Test level 3 {Test field strength of 10 V/m} for 800 MHz to 960 MHz & 1.4 to 6.0 GHz,; Performance Criteria A B.11 Immunity to radiated RF EN/IEC 61000-4-3(2010) 80 MHz to 6.0 GHz: Clauses applicable to Telecom Test level 2 {Test field strength Terminal Equipment without voice of 3 V/m}: Performance Criteria interface. A
Annexure to ERs – 2.8/ July2021 14 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.12 Immunity to fast transients EN/IEC 61000-4-4(2012) Test Level 2 (1.0 kV): Not applicable for devices having in- (burst) AC/DC Power Lines Performance Criteria B built or replaceable battery
B.13 Immunity to fast transients EN/IEC 61000-4-4(2012) Test level 2 (0.5kV): Not applicable for mobile devices (burst) Signal/Control/Data/Teleco Performance Criteria B having only radio interface m Lines B.14 Immunity to surges EN/IEC 61000-4-5(2014) 2kV: Performance Criteria B Not applicable for devices having in- line to ground – power port built or replaceable battery
B.15 Immunity to surges EN/IEC 61000-4-5(2014) 1kV: Performance Criteria B Not applicable for devices having in- line to line – power port built or replaceable battery B.16 Immunity to surges EN/IEC 61000-4-5(2014) 2kV: Performance Criteria C Not applicable for mobile devices Common mode – telecom having only radio interface ports B.17 Immunity to conducted EN/IEC 61000-4-6(2013): Test level 2 {3 V r.m.s.}: Not applicable for mobile devices disturbance induced by Performance Criteria A having only radio interface Radio frequency fields AC/DC lines & signal control /telecom lines. 150 kHz to 80 MHz
B.18 Immunity to voltage dips & EN/IEC 61000-4-11(2004) Performance criteria B Applicable to AC power ports short interruption: Voltage dip corresponding to a reduction of supply voltage of 30% for 500ms (i.e. 70 % supply voltage for 500ms)
B.19 Immunity to voltage dips & EN/IEC 61000-4-11(2004) Performance criteria C Applicable to AC power ports short interruption: Voltage dip corresponding to a reduction of supply voltage of 60% for 200ms; (i.e. 40% supply voltage for 200ms).
Annexure to ERs – 2.8/ July2021 15 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.20 Immunity to voltage dips & EN/IEC 61000-4-11(2004) Performance criteria C Applicable to AC power ports short interruption: Voltage interruption corresponding to a reduction of supply voltage of > 95% for 5s. B.21 Immunity to voltage dips & EN/IEC 61000-4-11(2004) Performance criteria B Applicable to AC power ports. short interruption: Voltage interruption corresponding to a reduction of supply voltage of >95% for 10ms. B.22 Immunity to voltage dips & EN/IEC 61000-4-29 Performance criteria B Applicable to DC power ports short interruption: Voltage Interruption with 0% of supply for 10ms. B.23 Immunity to voltage dips & EN/IEC 61000-4-29 Performance criteria C Applicable to DC power ports short interruption: Voltage Interruption with 0% of supply for 30ms, 100ms, 300ms and 1000ms. B.24 Immunity to voltage dips & EN/IEC 61000-4-29 Performance criteria B Applicable to DC power ports short interruption: Voltage dip corresponding to 40% & 70% of supply for 10ms, 30 ms. B.25 Immunity to voltage dips & EN/IEC 61000-4-29 Performance criteria C Applicable to DC power ports short interruption: Voltage dip corresponding to 40% & 70% of supply for 100ms, 300ms and 1000 ms.
Annexure to ERs – 2.8/ July2021 16 S. No. Parameter Name Standard Limits/ Test Levels Applicability/ Remarks
B.26 Immunity to voltage dips & EN/IEC 61000-4-29 Performance criteria B Applicable to DC power ports short interruption: Voltage variations corresponding to 80% and 120% of supply for 100 ms to 10s as per Table 1c of IEC 61000-4-29
Note: Minimum required information related to EMI/EMC parameters has been captured in Annex-B to facilitate the applicants. However, for further details/clarity in this regard, TEC document for EMI/EMC standard – TEC/SD/DD/EMC-221/05/OCT-16 may kindly be referred to.
Conducted and Radiated Emissions will be as per Class A for chasis based OLT equipment and Class B for residential OLT equipment
In case of any conflict, the TEC document for EMI/EMC standard shall prevail.
Annexure to ERs – 2.8/ July2021 17
Note for IoT Devices 1. If Tracking Device come along with vehicle for testing then CISPR 25 / AIS 004-Part3 will be applicable. 2. Immunity to Surges - For Non- Rechargeable fixed battery operated device without any telecom or power port, this test is not applicable. 3. Conducted and Radiated Emission – If Smart Electricity Meter is to be tested along with communication module then CISPR 14-1 is applicable. 4. Immunity to Electrostatic Discharge: – Smart Electricity Meter For communication module limits as per standard IEC 61000-4-2 are applicable. If Smart Electricity Meter is to be tested along with communication module, then severity level should be 4 (As per standard of Smart electricity Meter IS 16444 which refer to IS 13779 & IS 15884) in both cases – Air and Contact Discharge. 5. Immunity to Radiated RF: – Smart Electricity Meter For communication module limits as per standard IEC 61000-4-3 are applicable. If Smart Electricity Meter is to be tested along with communication module, then severity level should be 4 and field strength is 10 V/m (As per standard of Smart electricity Meter IS 16444 which refer to IS 13779 & IS 15884). 6. Immunity to Fast Transients: – Smart Electricity Meter For communication module limits as per standard IEC 61000-4-4 (2012) are applicable. If Smart Electricity Meter is to be tested along with communication module, then severity level should be 3, ±4 kV (As per standard of Smart electricity Meter IS 16444 which refer to IS 13779 & IS 15884). 7. Immunity to Surges: – Smart Electricity Meter For communication module limits as per standard IEC 61000-4-5 (2014) are applicable. If Smart Electricity Meter is to be tested along with communication module, then ±5 kV and 5 Pulses each polarity at 60º, 240º only in differential mode. 8. General Safety Requirements: – Smart Electricity Meter For communication module standard IEC 60950/IS 13252 are applicable. If Smart Electricity Meter is to be tested along with communication module, then safety must be as per prevailing IS 16444.
Annexure to ERs – 2.8/ July2021 18
Annexure- B1: Emission limits as per CISPR22 Parameter Group: EMC The value of the limits from “CISPR 22 (2008)” at clause-6 [and reproduced below in tables 4(a), 4(b) & 5(a), 5(b)] shall be used for class B and class A equipment respectively. Further, the limits of table 5 may also be used for equipment in Telecommunication Centres. Alternatively, the Limits as per Table 4 (a1) & 5 (a1) for measuring distance of 3m are also acceptable , as applicable , in place of Table 4 (a) & 5 (a) respectively. a) Limits below 1 GHz
Table 4(a): Limits for unwanted radiated emission of “Class B” equipment at a measuring distance of 10m.
Frequency range Limits (quasi-peak) 30-230 MHz 30 dB (μV/m) 230- 1000 MHz 37dB (μ V/m) Note: 1) The lower limit shall apply at the transitionFrequency. Note: 2 ) Additional provisions may be required for cases where interference occurs.
Table 5(a): Limits for unwanted radiated emission of “Class A” equipment (for Telecommunication Centres) at a measuring distance of 10m.
Frequency range Limits (quasi-peak) 30-230 MHz 40 dB (μV/m) 230- 1000 MHz 47 dB (μV/m) Note: 1) The lower limit shall apply at the transition Frequency. Note: 2) Additional provisions may be required forcases where interference occurs.
Annexure to ERs – 2.8/ July2021 19 Note: Limits are shown here for a measurement distance of 10m. However, measurements made using alternative test sites are also acceptable in accordance with CISPR 22 including clause No. 10.4.5.
Table 4(a1): Limits for unwanted radiated emission of “Class B” Equipment at a measuring distance of 3 m.
Frequency range limits (quasi – peak)
30 – 230 MHz 40.5 dB ( V/m)
230 – 1000 MHz 47.5 dB ( V/m) Notes: 1. The lower limits shall apply at transition frequency 2. Additional provisions may be required for cases where interference occurs.
Table 5 (a1): Limits for unwanted radiated emission of “Class A” Equipment at a measuring distance of 3 m.
Frequency range limits (quasi – peak)
30 – 230 MHz 50.5 dB ( V/m)
230 – 1000 MHz 57.5 dB ( V/m) Notes:
1. The lower limits shall apply at transition frequency
2. Additional provisions may be required for cases where interference occurs.
Annexure to ERs – 2.8/ July2021 20 b) Limits above 1 GHz The EUT shall meet the following limits when measured in accordance with the prescribed method and the conditional testing procedure as described.
Table 4(b): Limits for radiated disturbance of “Class B” Eqpt. at a measurement distance of 3 m. Frequency range Average limit Peak limit
GHz dB ( V/m) dB ( V/m)
1 to 3 50 70 3 to 6 54 74
NOTE: The lower limit applies at the transition frequency.
Table 5(b): Limits for radiated disturbance of “Class A” Eqpt. at a measurement distance of 3 m.
Frequency range Average limit Peak limit GHz dB ( V/m) dB ( V/m) 1 to 3 56 76 3 to 6 60 80 NOTE :The lower limit applies at the transition frequency.
Annexure to ERs – 2.8/ July2021 21 Limits for conducted emission
For Class A equipment Table 7: Limit of conducted emission (disturbance) at the main ports of Class A Telecom Equipment
Frequency range Limit (Quasi -Peak) Limit (Average)
0.15 – 0.5 MHz 79 dB ( V) 66 dB ( V) 0.5-30 MHz 73 dB ( V) 60 dB ( V) Note: The lower limit shall apply at the transition Frequencies.
Table 8(B): Limits for conducted common mode (asymmetric mode) emissions from telecommunication ports of Class A equipment (intended for use in telecommunication centers only).
Voltage limits dB ( V) Current limits dB ( A) Frequency rangeMHz Quasi-peak Average Quasi-peak Average 0.15 to 0.5 97 to 87 84 to 74 53 to 43 40 to 30 0.5 to 30 87 74 43 30 Note 1: The limits decrease linearly with the logarithm of the frequency in the range 0.15 MHz to 0.5 MHz. Note 2: The current and voltage disturbance limits are derived foruse with an impedance stabilization network (ISN) which presents a common mode (asymmetric mode) impedance of 150 are telecommunication port under test (conversion factor is 20 log10150/1= 44 dB).
For Class B equipment
Annexure to ERs – 2.8/ July2021 22 Table 6: Limits of conducted emission (disturbance) at the mains ports of Class B Telecom Equipment
Frequency range Limit (Quasi -Peak) Limit (Average)
0.15 -0.5 MHz 66-56 dB ( V) 56-46 dB ( V) 0.5-5 MHz 56 dB ( V) 46 dB ( V) 5-30 MHz 60 dB ( V) 50 dB ( V) Note: 1) The lower limit shall apply at the transition Frequencies. Note: 2) The limits decreases linearly with logarithm of the Frequency in the range 0.15 MHz to 0.50 MHz.
Table 8(A): Limits for conducted common mode (asymmetric mode) emission from telecommunication ports for class B equipment.
Voltage limits dB (μV) Current limits dB (μA) Frequency rangeMHz Quasi-peak Average Quasi-peak Average 0.15 to 0.5 84 to 74 74 to 64 40 to 30 30 to 20 0.5 to 30 74 64 30 20 Note 1: The limits decrease linearly with the logarithm of the frequency in the range 0.15 MHz to 0.5 MHz. Note 2: The current and voltage disturbance limits are derived foruse with an impedance stabilization network (ISN) which presents a common mode (asymmetric mode) impedance of 150 are telecommunication port under test (conversion factor is 20 log10150/1= 44 dB).
Annexure to ERs – 2.8/ July2021 23 Conditional testing procedure for 1-6 GHz testing: a. The highest internal source of an EUT is defined as the highest frequency generated or used within the EUT or on which the EUT operates or tunes. b. If the highest frequency of the internal sources of the EUT is less than 108 MHz, the measurement shall only be made up to 1 GHz. c. If the highest frequency of the internal sources of the EUT is between 108 MHz and 500 MHz, the measurement shall only be made up to 2 GHz. d. If the highest frequency of the internal sources of the EUT is between 500 MHz, and 1 GHz, the measurement shall only be made up to 5 GHz. e. If the highest frequency of the internal sources of the EUT is above 1 GHz, the measurement shall be made up to 5 times the highest frequency or 6 GHz, whichever is less.
Class A and Class B equipment definition: a. Class B equipment: “Class B” Telecom equipment is intended primarily for use in the domestic environment and may include: i. equipment with no fixed place of use; for example, portable equipment powered by built- in batteries; ii. Telecommunication terminal equipment powered by a telecommunication network; iii. Personal computers and auxiliary connected equipment. b. Class A equipment: Class A Telecom equipment is a category of all other Telecom Equipments which satisfies class A Telecom Equipment limits but not the class B limits. Such equipment may cause Radio Interference in the domestic environment.
Annexure to ERs – 2.8/ July2021 24 Annexure-D: Parameters for 2-wire PSTN Lines, Trunks lines and CPEs connected thereon (INT2W & CPE2W) Parameter Group: 2-Wire Interface (INT2W) and CPEs connected on 2-Wire (CPE2W) S. No. Equipment Name Parameter Name Standard Limits/ Values Applicability/ Remarks D.1 2-Wire CPEs and Interfaces Longitudinal/ Transverse Q.552 Clause 2.2.2 & Figure As in Figure 2, Refer Note 1 Conversion Loss 2 / TBR.21 Clause 4.4.3 Annexure-D4 D.2 2-Wire CPEs and Interfaces Return Loss Q.552 Clause 2.2.1.2 and As in Figure 1, Figure 1 Annexure-D4 D.3 2-Wire CPEs and Interfaces Over Voltage/ Over Current K.21 Compliance Compliance of Protection this test only if port is connected to external lines e.g. in case of xDSL lines. D.4 2-Wire CPEs and Interfaces Maximum Loop Current ETSI EN 300 001 < 60 mA D.5 2-Wire CPEs and Interfaces Idle State Current ETSI EN 300 001 < 40 µA/ 130µA Without/ with CLIP display D.6 2-Wire CPEs and Interfaces Insulation Test ETSI EN 300 001 > 5 MΩ Refer Note 1 D.7 2-Wire CPEs and Interfaces Resistance to Earth TBR-21 Clause 4.4.4 > 10 MΩ D.8 2-wire Trunk Line DC Resistance ETSI TBR-21 Clause 4.4.1 > 1 MΩ D.9 2-wire Trunk Line Minimum Current on MGW ETSI EN 300 001 > 60 µA Trunk Line D.10 Telephones/ Fax with Handset Acoustic Shock Absorption P.360 Clause 4.1 Compliance D.11 Audio Conferencing Voice Conference Functional Test Compliance Equipment Verification D.12 Fax, Modem Transmit Power for Fax T.4 Clause 6 -3dBm to -15 Machine/ Modem dBm D.13 Fax Receiver Sensitivity for FAX T.4 Clause 7 > -43 dBm D.14 Modem Receiver Signal for Modem V.34 (para 6.6) > -43 dBm ON < -48 dBm OFF D.15 2-wire line and trunk Transmission of DTMF Q.23 Clause 6 and 7 Compliance Signals
Annexure to ERs – 2.8/ July2021 25 D.16 2- Wire Trunk Current on Junction/ Trunk < 60 mA Line in PABX Note 1: This test is exempted provided an undertaking should be submitted by the supplier that 2-wire equipment is not intended to be
connected to Earth. In case the 2- wire equipment is intended to be connected to Earth by any supplier then the test would be required
Annexure to ERs – 2.8/ July2021 26 Annexure-G1: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands Parameter Group: Radio Conformance (RADCONF) S. No. Parameter Name Standard/ Limits/ Values Applicability/Remarks Parameter G1.1 Frequency for WiFi equipment DoT WPC 2.4 GHZ Band: Wifi Interface GSR No. 2.4-2.4835 GHz as per WPC Test procedure as per Appendix-II Test-1 45(E), 1048(E) GSR 45(E) 5 GHz Band: 5.150-5.250 GHz, 5.250- 5.350 GHz, 5.470-5.725 GHz, 5.725-5.875 GHz as per WPC GSR 1048(E) G1.2 Frequency for PTP/ PMP Radio DoT WPC 2.4 GHZ Band: PTP/ PMP Wireless Access Equipment Interface GSR No. 2.4-2.4835 GHz as per WPC Test procedure as per Appendix-II Test-1 45(E), 1048(E) GSR 45(E) 5 GHz Band: 5.150-5.350 GHz, 5.250- 5.350 GHz, 5.470-5.725 GHz, 5.725-5.875 GHz as per WPC GSR 1048(E)
Annexure-G2: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands Parameter Group: Radio Conformance (RADCONF) S. No. Parameter Name Standard/ Limits/ Values Remarks Parameter G2.1 EIRP for all equipment operating Latest NFAP and < 4 W for outdoor usage Wifi Interface & PTP/PMP Wireless in 2.4 GHz GSRs issued by DoT < 200 mW for indoor usage Access Equipment in 2.4 GHz WPC Note: Testing as per EN 300 328 or Appendix- EIRP requirements shall be as II Test-1 per the latest NFAP and GSRs issued by WPC, DoT and the requirements in NFAP and GSRs supersede the requirements listed here.
Annexure to ERs – 2.8/ July2021 27 S. No. Parameter Name Standard/ Limits/ Values Remarks Parameter
G2.2 EIRP for RLAN/ WLAN Latest NFAP and As per WPC GSR 1048(E) Wifi Interface equipment operating in 5 GHz GSRs issued by DoT Note: Testing as per EN 301893 or Appendix- WPC EIRP requirements shall be as II Test-1 per the latest NFAP and GSRs issued by WPC and the requirements in NFAP and GSRs supersede the requirements listed here.
G2.3 EIRP for PTP/ PMP fixed Radio Latest NFAP and As per WPC GSR 1048(E) PTP/PMP Wireless Access Equipment systems operating in 5 GHz GSRs issued by DoT Note: in 5 GHz WPC EIRP requirements shall be as Testing as per EN 302 502 or Appendix- per the latest NFAP and GSRs II Test-1 issued by WPC and the requirements in NFAP and GSRs supersede the requirements listed here.
G2.4 EIRP for Cordless Telephone WPC GSR Cordless Phone
Annexure to ERs – 2.8/ July2021 28 Annexure-G3: Parameters for Radio Interfaces for equipment operating in delicensed frequency bands Parameter Group: Radio Conformance (RADCONF) S. No. Parameter Name Standard/ Parameter Applicability/Limits/ Values Remarks G3.1 Radio Conformance for all WiFi EN 300 328 Wifi Interface & equipment operating in 2.4 GHz or PTP/PMP Wireless FCC CFR47 Access Equipment in 2.4 Part15.247 GHz or FCC CFR47 Part 15.249 G3.2 Radio Conformance for EN 301 893 FCC CFR47 15.407 for 5.150- Wifi Interface RLAN/WLAN WiFi equipment or 5.350 GHz operating in 5 GHz FCC CFR47 Part 15.407 FCC CFR47 Part 15.249 for or 5.725-5.875 GHz FCC CFR47 Part 15.249 G3.3 Radio Conformance for PTP/PMP EN 302 502 Except clauses 4.2.4, 4.2.6 and 4.2.8 Wifi Interface & Wireless Access Equipment or of EN 302 502 in 5.825-5.875 GHz PTP/PMP Wireless operating in 5 GHz FCC CFR47 Part band) Access Equipment in 5 15.249 GHz Conformance to FCC CFR47 Part 15.249 for 5.725-5.875 GHz
Annexure to ERs – 2.8/ July2021 29 Annexure to ERs – Page 1
Annexure-H: Ethernet Interface Parameters Parameter Group: Ethernet Interface (INTETH) S. No. Interface Name Parameter Name Standard Limits/ Values Applicability/ Remarks
H.1 Gigabit Ethernet Link Speed and Auto IEEE 802.3 Appendix-II, Test4 Electrical or 10 100 1000 Negotiation GE Base T Ethernet H.2 Fast Ethernet Electrical Link Speed and Auto IEEE 802.3 Appendix-II, Test4 or 10/100 Base T Negotiation for GE Ethernet H.3 Gigabit Ethernet Optical Average Launch power for 1 GE IEEE 802.3z Opt Cl. 38
H.4 Gigabit Ethernet Optical Wavelength for 1 GE Opt IEEE 802.3z Cl. 38 H.5 Gigabit Ethernet Optical Receiver Sensitivity 1 GE Opt IEEE 802.3z Cl. 38
H.6 10 Gigabit Ethernet Wavelength for 10GE Int IEEE 802.3ae Optical Cl. 52 H.7 10 Gigabit Ethernet Receiver Sensitivity for 10GE IEEE 802.3ae Optical Int Cl. 52
H.8 10 Gigabit Ethernet Average Launch power for 10 IEEE 802.3ae Optical GE Opt Cl. 52
H.9 40 Gigabit Ethernet Average Launch power for 40 IEEE Optical GE Opt 802.3ba Cl. 86, 87
Annexure to ERs – Page 2 S. No. Interface Name Parameter Name Standard Limits/ Values Applicability/ Remarks
H.10 40 Gigabit Ethernet Wavelength for 40 GE Opt IEEE Optical 802.3ba Cl. 86, 87 H.11 40 Gigabit Ethernet Receiver Sensitivity 40 GE Opt IEEE Optical 802.3ba Cl. 86, 87 H.12 100 Gigabit Ethernet Average Launch power for 100 IEEE Optical GE Opt 802.3ba Cl. 86, 88 H.13 100 Gigabit Ethernet Wavelength for 100 GE Opt IEEE Optical 802.3ba Cl. 86, 88 H.14 100 Gigabit Ethernet Receiver Sensitivity 100 GE Opt IEEE Optical 802.3ba Cl. 86, 88 H.15 Fast Ethernet Optical Average Launch power for FE IEEE 802.3u Opt H.16 Fast Ethernet Optical Wavelength for FE Opt IEEE 802.3u H.17 Fast Ethernet Optical Receiver Sensitivity for FE Opt IEEE 802.3u
Annexure to ERs – Page 3 Annexure-I: PDH Interface Parameters Parameter Group: PDH Interface (INTPDH) S. No. Interface Name Parameter Name Standard/ Limits/ Values Applicability/ Parameter Remarks I.1 2Mbps-E1 Input Jitter Tolerance for 2 MBPS Int G.823 , ETSI TBR-4 Fig 13,Clause No.-7.1.2 I.2 2Mbps-E1 Input Return Loss for 2 MBPS Int G.703 , ETSI TBR-4 51 to 102 (KHz)-12dB Cl. 9.3.1 102 to 2048(KHz)- 18dB 2048 to 3072(KHZ)- 14dB I.3 2Mbps-E1 Nominal Bit Rate with Tolerance 2 MBPS G.703 , ETSI TBR-4 2048Kbps Int Cl. 9.2.3 I.4 2Mbps-E1 Output Jitter for 2 MBPS Int G.823 , ETSI TBR-4 20 to 100 kHz - 1.5(UIpp) 18 k to 100kHz- 0.2(UIpp) I.5 2Mbps-E1 Pulse Mask for 2 MBPS Int G.703, ETSI TBR-4 Figure 11-1,clause-11.2
Annexure to ERs – Page 4 Annexure-J1: xDSL Interface Parameters Parameter Group: DSL Interface (INTDSL) S. No. Interface Parameter Name Standard Clause Remarks Name J1.1 ADSLx Insulation Test for 2 wire Int ETSI EN 300 001 Cl. 2.2 J1.2 ADSLx Loop resistance for ADSLx ETSI EN 300 001 Table 2.3 J1.3 ADSLx G.992.3 Annexure A, B, I, J, PSD for ADSL Int G992.5 J1.4 ADSLx Bit Rate for ADSL Int ANSI.T1.413-2 J1.5 ADSLx Insulation Test for ADSL Int J1.6 ADSLx Impulse Noise Protection for ADSL Int G.992.3 Appendix V J1.7 ADSLx Transmitted Power At ATU-C for G.992.3 Annexure-P ADSLxInt J1.8 ADSLx Line Port impedance for ADSLxInt J1.9 VDSLx Insulation Test for 2 wire Int ETSI EN 300 001 J1.10 VDSLx Loop resistance for VDSLx ETSI EN 300 001 J1.11 VDSLx Profiles for VDSLx G.993.2 Cl. 7.2 J1.12 VDSLx Return Loss for VDSLx G.993.1 Cl. 6.5 J1.13 VDSLx PSD for VDSLxInt G.993.1 Cl. 6.2/ G.993.2 Cl. 7.2 J1.14 VDSLx Line Port impedance for VDSLxInt J1.15 VDSLx Transmitted Power At ATU-C for VDSLxInt J1.16 VDSLx Bit Rate for VDSLxInt G.993.1/ G993.2 J1.17 G.FAST PPPoE for G.FAST Int RFC 2516 Functional Test Annex-P11 J1.18 G.FAST PVC Support for G.FAST Int J1.19 G.FAST VPI-VCI Support for G.FAST Int J1.20 G.FAST Loop Resistance for G.FAST IntSLx ETSI EN 300 001 J1.21 G.FAST Insulation Test for G.FAST Int J1.22 G.FAST Impulse Noise Protection for G.FAST Int J1.23 G.FAST Throughput Test for G.FAST Int J1.24 G.FAST Profiles for G.FAST Int G.9700 J1.25 G.HN Profiles for G.HN Int G.9960
Annexure to ERs – Page 5 S. No. Interface Parameter Name Standard Clause Remarks Name J1.26 G.HN PSD for G.HN G.9964 J1.27 SHDSL PSD for SHDSL Int G.991.2 J1.28 SHDSL Return Loss for SHDSL G.991.2 J1.29 SHDSL Transmitted Power for SHDSL Int G.991.2 J1.30 SHDSL Impedance Unbalance About Earth for G.991.2 SHDSL Int J1.31 SHDSL Insulation Resistance for SHDSL int G.991.2 J1.32 SHDSL Throughput for SHDSL Interface G.991.2 J1.33 SHDSL LCL for SHDSL Interface G.991.2
Annexure to ERs – Page 6 Annexure-J2: PON Interface Parameters Parameter Group: PON Interface (INTPON) S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter J2.1 GPON Operating Wavelength G.984.2 Cl. 8.2.5.1 DS 1480-1500nm Trans for GPON Int J2.2 GPON Operating Wavelength G.984.2 Cl. 8.2.5.2 "US 1260-1360nm (Class B/B+) or Recv for GPON Int 1290-1330nm (Class C/C+/D) J2.3 GPON Opt Output Power for G.984.2 0 to +4dBm (A) GPON Int at OLT +5.0 to +9.0 dBm (B) +1.5 to +5.0 dBm (B+) +3.0 to +7.0 dBm (C/C+) +6.0 to +10.0 dBm (D) A,B,B+,C,C+ and ‘D’ are classes of optical link budget for PON Measured at 1490nm at OLT ‘s PON port i.e. Rx or D/L mode. Refer following Tables of ITU-T G.984.2: (1) Table 2c & Table 2f1 for Class A, Class B, Class C (2) Table A.1 for Class B+ (3) Table V.1 for Class C+, (4) Table V.2 for Class D
J2.4 GPON Opt Output Power for G.984.2 -3.0 to +2.0dBm (A) GPON Int at ONT -2.0 to +3.0 dBm (B) +0.5 to +5.0 dBm (B+) +2.0 to +7.0 dBm (C) +0.5 to +5.0 dBm (C+) +0.5 to +5.0 dBm (D) A,B,B+,C,C+ and ‘D’ are classes of optical link budget for PON Measured at 1490nm at OLT ‘s PON port i.e. Rx or D/L mode. Refer following Tables of ITU-T G.984.2: (1) Table 2c & Table 2f1 for Class A, Class B, Class C (2) Table A.1 for Class B+ (3) Table V.1 for Class C+, (4) Table V.2 for Class D
Annexure to ERs – Page 7 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter J2.5 GPON Receiver Sensitivity for G.984.2 -24dBm(minimum) (A) GPON Int at OLT -28 dBm(minimum) (B/B+) -29 dBm(minimum) (C) -32 dBm(minimum) (C+) -35 dBm(minimum) (D) A,B,B+,C,C+ and ‘D’ are classes of optical link budget for PON Measured at 1490nm at OLT ‘s PON port i.e. Rx or D/L mode. Refer following Tables of ITU-T G.984.2: (1) Table 2c & Table 2f1 for Class A, Class B, Class C (2) Table A.1 for Class B+ (3) Table V.1 for Class C+, (4) Table V.2 for Class D J2.6 GPON Receiver Sensitivity for G.984.2 -21dBm(minimum) (A) GPON Int at ONT -21 dBm(minimum) (B) -27 dBm(minimum) (B+) -28 dBm(minimum) (C) -30 dBm(minimum) (C+) -30 dBm(minimum) (D) A,B,B+,C,C+ and ‘D’ are classes of optical link budget for PON Measured at 1490nm at OLT ‘s PON port i.e. Rx or D/L mode. Refer following Tables of ITU-T G.984.2: (1) Table 2c & Table 2f1 for Class A, Class B, Class C (2) Table A.1 for Class B+ (3) Table V.1 for Class C+, (4) Table V.2 for Class D J2.7 GPON Protocol Test for GPON Int EthOGEM/ G.984.2x PICS Test as per Annexure V & VI of ITU-T G.983.1 with respect to GPON parameter and their reference valuesRefer List-1
Annexure to ERs – Page 8 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter J2.8 EPON Operating Wavelength IEEE 802.3ah DS 1480 -1500 nm Trans for EPON Int Refer TEC GR on EPON(2019) J2.9 EPON Operating Wavelength IEEE 802.3ah US 1260-1360 nm Recv for EPON Int Refer TEC GR on EPON(2019) J2.10 EPON Opt Output Power for IEEE 802.3ah +2 dbm to +7dbm EPON Int at OLT Refer TEC GR on EPON(2019) J2.11 EPON Opt Output Power for IEEE 802.3ah -1 dbm to +4dbm EPON Int at ONT Refer TEC GR on EPON(2019) J2.12 EPON Receiver Sensitivity for IEEE 802.3ah -27dbm(minimum)(for 1000Base- EPON Int at OLT PX20-D) - 30dbm(minimum)(1000Base-PX20E- D) Refer TEC GR on EPON(2019) J2.13 EPON Receiver Sensitivity for IEEE 802.3ah -24dbm(minimum)(for 1000Base- EPON Int at ONT PX20-U) - 27dbm(minimum)(1000Base-PX20E- U) Refer TEC GR on EPON(2019) J2.14 XGPON Operating Wavelength G.987.2 DS 1575 – 1580 nm Trans for XGPON Int J2.15 XGPON Operating Wavelength G.987.2 US 1260 – 1280 nm Recv for XGPON Int J2.16 XGPON Opt Output Power XGPON G.987.2 +2.0 to +6.0 dBm (N1) Int at OLT +4.0 to +8.0 dBm (N2a) +10.0 to +12.5 dBm (N2b) +6.0 to +10.0 dBm (E1) +8.0 to +12.0 dBm (E2a) +14.5.0 to +16.5 dBm (E2b)
N1, N2, E1 and E2 are classes of optical path loss. Refer following Table 9.3 of ITU-T G.987.2
Annexure to ERs – Page 9 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter J2.17 XGPON Opt Output Power XGPON G.987.2 +2.0 to +7.0 dBm (N1,N2,E1, E2) Int at ONT Refer following Table 9.4 of ITU-T G.987.2 J2.18 XGPON Receiver Sensitivity G.987.2 -27.5dBm for (N1) XGPON Int at OLT -29.5dBm for (N2) -31.5dBm for (E1) -33.5dBm for (E2) Refer following Table 9.4 of ITU-T G.987.2 J2.19 XGPON Receiver Sensitivity G.987.2 -28.0dBm for (N1) XGPON Int at ONT -28.0dBm for (N2a) -21.5dBm for (N2b) -28.0dBm for (E1) -28.0dBm for (E2a) -21.5dBm for (E2b) Refer following Table 9.3 of ITU-T G.987.2 J2.20 XGPON Protocol test for XGPON G.987.2, XGEMx PICS Test as per Annexure V & VI of Int ITU-T G.987.1 with respect to XGPON parameter and their reference valuesRefer List-2 J2.21 XGSPON Operating Wavelength G.9807.1 "DS i. 1 575 – 1 580 nm (Basic Trans XGSPON Int wavelength) ii. 1 480 to 1 500 nm (optional wavelength) XGS-PON systems come with two operating wavelength options Basic wavelength set: consists of XG- PON wavelength reuse, in which case the system has to accommodate both XGS-PON ONUs and legacy XG- PON ONUs Optional wavelength set: consists of G-PON wavelength reuse, for the
Annexure to ERs – Page 10 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter operators having no legacy Gigabit PON in the deployment area Refer ITU-T G.9807.1" J2.22 XGSPON Operating Wavelength G.9807.1 "US i. 1 260 – 1 280 nm (Basic Recv XGSPON Int wavelength) ii. 1 300 to 1 320 nm (optional wavelength)
XGS-PON systems come with two operating wavelength options Basic wavelength set: consists of XG- PON wavelength reuse, in which case the system has to accommodate both XGS-PON ONUs and legacy XG- PON ONUs Optional wavelength set: consists of G-PON wavelength reuse, for the operators having no legacy Gigabit PON in the deployment area Refer ITU-T G.9807.1" J2.23 XGSPON Opt Output Power G.9807.1 +2.0 to +5.0 dBm (N1) XGSPON Int at OLT +4.0 to +7.0 dBm (N2) +6.0 to +9.0 dBm (E1) N1, N2 and E1 are classes of optical link budget for PON. Refer Table B.9.3 of standard ITU-T G.9807.1 J2.24 XGSPON Opt Output Power G.9807.1 +4.0 to +9.0 dBm (N1,N2,E1) XGSPON Int at ONT Refer Table B.9.4 of standard ITU-T G.9807.1 J2.25 XGSPON Receiver Sensitivity G.9807.1 -26.0 dBm (N1) XGSPON Int at OLT -28.0 dBm (N2) -30.0 dBm (E1)
Annexure to ERs – Page 11 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter Refer Table B.9.4 of standard ITU-T G.9807.1 J2.26 XGSPON Receiver Sensitivity G.9807.1 -28dBm (N1, N2 and E1) XGSPON Int at ONT Refer Table B.9.3 of standard ITU-T G.9807.1 J2.27 XGSPON Protocol Test for XGSPON G.9807.1, XGEMx PICS Test as per Annexure V & VI of Int ITU-T G.983.1 with respect to XGPON parameter and their reference valuesRefer ist-3 J2.28 WDMPON Operating Wavelength G.694.1 US 1530nm-1560nm C-Band These are Trans WDMPON Int (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation J2.29 WDMPON Operating Wavelength G.694.1 DS 1530nm-1560nm C-Band These are Recv WDMPON Int (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation J2.30 WDMPON Opt Output Power G.694.1 +2.0 to +7.0 dBm These are WDMPON Int at OLT (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation J2.31 WDMPON Opt Output Power G.694.1 -2.0 to +2.0 dBm These are WDMPON Int at ONT (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation J2.32 WDMPON Receiver Sensitivity G.694.1 -24.0 dBm These are WDMPON Int at OLT (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation J2.33 WDMPON Receiver Sensitivity G.694.1 -17.0 dBm These are WDMPON Int at ONT (G.989.2/p2p Refer TEC GR on WDM-PON(2017) proprietary WDM) implementation
Annexure to ERs – Page 12 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter J2.34 WDMPON Throughput for WDMPON RFC2544 These are Int proprietary implementation J2.35 WDMPON Protocol test for G.694.1 PICS Test as per Annexure V & VI of These are WDMPON Int (G.989.2x/p2 ITU-T G.983.1 with respect to NGPON2 proprietary p WDM) parameter and their reference implementation valuesRefer List -2 J2.36 NGNPON2 Operating Wavelength G.989.2 DS 1596 -1603 nm Trans NGPON2Int Refer ITU-T G.989.2 J2.37 NGNPON2 Operating Wavelength G.989.2 US For TWDM PON Recv NGPON2Int 1524-1544nm for Wideband 1528-1540nm for Reduced band 1532-1540nm for Narrow band For PtP WDM PON 1524-1625nm for Expanded Spectrum 1603-1625nm for Shared spectrum Refer ITU-T G.989.2 J2.38 NGNPON2 Opt Output Power G.989.2 For 2.48832 Gbit/s downstream NGPON2Int at OLT Direction 0.0 to +4.0 dBm (N1) +2.0 to +6.0 dBm (N2) +4.0 to +8.0 dBm (E1) +6.0 to +10.0 dBm (E2) For 9.95328 Gbit/s downstream Direction +3.0 to +7.0 dBm (N1) +5.0 to +9.0 dBm (N2) +7.0 to +11.0 dBm (E1) +9.0 to +11.0 dBm (E2)
N1, N2, E1 and E2 are classes of optical link budget for PON
Annexure to ERs – Page 13 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter Refer following Table 11.4 & Table 11.5 of ITU-T G.989.2 J2.39 NGNPON2 Opt Output Power G.989.2 For 2.48832 Gbit/s upstream NGPON2Int at ONT Direction Type A link +4.0 to +9.0 dBm (N1,N2, E1, E2) Type B link 0 to +5.0 dBm (N1, N2, E1, E2) For 9.95328 Gbit/s upstream Direction Type A link +4.0 to +9.0 dBm (N1) +4.0 to +9.0 dBm (N2) +4.0 to +9.0 dBm (E1) NA (E2) Type B link +2.0 to +7.0 dBm (N1) +2.0 to +7.0 dBm (N2) +2.0 to +7.0 dBm (E1) +4.0 to +9.0 dBm (E2
Type A link values assume an unamplified OLT receiver Type B link values assume an amplified OLT receiver with the amplifier at the S/R-CG reference point Refer following Table 11.6 & Table 11.7 of ITU-T G.989.2 J2.40 NGNPON2 Receiver Sensitivity G.989.2 For 2.48832 Gbit/s NGPON2Int at OLT Type A link - 26.0 dBm (N1) -28.0 dBm (N2) -30.5 dBm (E1) -32.5 dBm(E2) Type B link
Annexure to ERs – Page 14 S. No. Interface Parameter Name Standard/ Limits/Values Remarks Name Parameter -30.0 dBm (N1) -32.0 dBm (N2) -34.5 dBm (E1) -36.5 dBm (E2)
For 9.95328 Gbit/s Type A link - 26.0 dBm (N1) -28.0 dBm (N2) -30.5 dBm (E1) Type B link - 28.0 dBm (N1) -30.0 dBm (N2) -32.5 dBm (E1) -32.5 dBm (E2)
Refer following Table 11.6 & Table 11.7 of ITU-T G.989.2 J2.41 NGNPON2 Receiver Sensitivity G.989.2 For 2.48832 Gbit/s NGPON2Int at ONT - 30.0 dBm (N1,N2, E1, E2)
For 9.95328 Gbit/s - 28.0 dBm (N1,N2, E1, E2)
Refer following Table 11.4 & Table 11.5 of ITU-T G.989.2 J2.42 NGNPON2 Protocol Test for G.989.2, RFC2544x PICS Test as per Annexure V & VI of NGPON2Int ITU-T G.983.1 with respect to NGPON2 parameter and their reference valuesRefer list -4 J2.43 RF Video RF Video Output 52-870 MHz, 14 dBmV, 0 dB Bandwidth, Level and Tilt- Values
Annexure to ERs – Page 15 J2.44 10G- EPON Operating Wavelength IEEE 802.3av. DS 1577nm, -2,+3nm Refer Table Recv for 10G-EPON Int Number 75-1 of IEEE 802.3 (2018). J2.45 10G- EPON Operating Wavelength IEEE 802.3av. 1310± 50 nm( for 1Gbps US) ; Refer Table Trans for 10G-EPON Int or Number 75-1 of 1270± 10 nm(for 10Gbps US) IEEE 802.3 (2018). J2.46 10G- EPON Opt Output Power for IEEE 802.3av. +2.0 to +5.0 dBm (Power Class Note: OEM will 10G-EPON Int at OLT PR10/PRX10/PR30/PRX30) support any one of OR the power class. +5.0 to +9.0 dBm (Power Class PR20/PRX20/PR40/PX40) Refer Table Number 75-5 of IEEE 802.3 (2018). J2.47 10G- EPON Opt Output Power for IEEE 802.3av. -1.0 to +4.0 dBm (PR10) Refer Table 10G-EPON Int at ONT OR Number 75-8 to 75- +4.0 to +9.0 dBm (PR30) 9 of IEEE 802.3 OR (2018). +6.0 to +9.0 dBm (PR40) OR -1.0 to +4.0 dBm (PRX10/PRX20) OR +0.6 to +5.6 dBm (PRX30) OR +2.0 to +6.0 dBm (PRX40). J2.48 10G- EPON Receiver Sensitivity for IEEE 802.3av. -24dBm (PR10/PRX10), OR -28dBm Refer Table 10G-EPON Int at OLT (PR20/PR30), OR -27dBm (PRX20), Number 75-6 to 75- OR -29.8dBm (PRX30), OR -29dBm 7 of IEEE 802.3 (PR40), OR -32dBm (PRX40), (2018). J2.49 10G- EPON Receiver Sensitivity for IEEE 802.3av. -20.5 dBm (Power Class Refer Table 10G-EPON Int at ONT PR10/PRX10/PR20/PRX20) Number 75-10 of OR IEEE 802.3 (2018). -28.5 dBm (Power Class PR30/PRX30) OR -29.5 dBm (Power Class PR40/PX40)
Annexure to ERs – Page 16 J2.50 10G-EPON Int Protocol test for 10G-EPON IEEE 802.3av. Refer List 5 All the Int “Mandatory’ parameters under Clause number 142.5, Cl 143.5 and Cl 144.5 of IEEE 802.3 (2018) J2.51 Nx25G- EPON Operating Wavelength IEEE 802.3ca. DS 1358 ± 2 nm, 1342 ± 2 nm. Note: OEM will support either Recv for Nx25G-EPON Note: one wavelength for 25Gbps and 25Gbps or 50Gbps. Int two wavelength for 50Gbps.
Refer Table Number 141-2 to 141-5 of IEEE 802.3ca. J2.52 Nx25G- EPON Operating Wavelength IEEE 802.3ca. US 1270± 10 nm, 1300± 10 nm, 1320 ± Note: OEM will Trans for Nx25G-EPON 2. support either Int Note: one wavelength for 10/25Gbps 25Gbps or 50Gbps. and two wavelength for 50Gbps. Refer Table Number 141-2 to 141-5 of IEEE 802.3ca. J2.53 Nx25G- EPON Opt Output Power for IEEE 802.3ca. Medium Power Class: Note: OEM will Nx25G-EPON Int at OLT +5.0 dBm (max) (for 25Gbps DS) OR support any one of +8.0 dBm (max) (for 50Gbps DS); the power class. OR High Power Class: +7.8 dBm (max) (for 25Gbps DS) OR Refer Table +10.8 dBm (max) (for 50Gbps DS); Number 141-15 to 141-16 of IEEE 802.3ca. J2.54 Nx25G- EPON Opt Output Power for IEEE 802.3ca. Medium Power Class: Note: OEM will Nx25G-EPON Int at ONT +9.0 dBm (max) (for 10Gbps US) OR support any one of +7.0 dBm (max) (for 25Gbps US) OR the power class. +10.0 dBm (max) (for 50Gbps US); OR Refer Table High Power Class: Number 141-19 to 141-20 of IEEE Annexure to ERs – Page 17 +9.0 dBm (max) (for 25Gbps US) OR 802.3ca. +12.0 dBm (max) (for 50Gbps US);
J2.55 Nx25G- EPON Receiver Sensitivity for IEEE 802.3ca. Medium Power Class: Refer Table Nx25G-EPON Int at OLT -28.0 dBm (for 10Gbps US) OR -22.7 Number 141-17 to dBm per channel; 141-18 of IEEE OR 802.3ca. High Power Class: -28.0 dBm (for 10Gbps US) OR -24.3 dBm per channel; J2.56 Nx25G- EPON Receiver Sensitivity for IEEE 802.3ca. Medium Power Class: Refer Table Nx25G-EPON Int at ONT -21.4 dBm per channel; Number 141-21 to OR 141-22 of IEEE High Power Class: 802.3ca. -24.1 dBm per channel; J2.57 Nx25G-EPON Protocol test for Nx25G- IEEE 802.3ca. Refer List 6 All the Int EPON Int “Mandatory’ parameters under Clause number 76.5 and Cl 77.5 of IEEE 802.3(2018) J2.58 ECR parameter ECR parameter TEC 74046:2020. No limit for ECR parameter.
J2.59 EP parameter EP parameter TEC 74046:2020. No Test Note: EP value will be generated by TEC based on ECR parameter.
Annexure to ERs – Page 18 Annexure-J3: PON Conformance Technical Parameters Parameter Group: PON Conformance (CONFPON)Technical Parameter
Note: it is to clarify that distributed architecture of PON is not much different from standalone functionality from ER testing perspective. The distributed PON products OLT, ONT, ONU, Servers etc. (including hardware and software), configured to perform PON applications shall be tested for technical parameters as given in PON ER. Additionally, Server and other additional nodes like LAN/WAN switches etc. used in the distributed architecture shall be tested for EMI/EMC, Safety and Interface tests as per existing TEC standards/ERs as done for standalone PON.
Therefore as an interim measure, distributed PON architecture shall be tested as proposed above and included in MTCTE certification till ER on COTS/Cloud server is finalized by TEC.
S. No. Parameter Name Standard Remarks J3.1 DOS Prevention, SSH v1-2 for CLI in ITU-T G.984.3 section V.2, SSH v2 RFC 4251. The denied Traffic streams PON should not pass through the OLT. J3.2 Frameloss of PON RFC 2544. Support a BER of better than or equal to 10-10 at the MAC service interface (or the frame loss ratio equivalent) J3.3 Latency of PON RFC 2544. <1.5 ms one way for 20Km of distance. refer Table I.1/G.984.1 J3.4 MAC Address Learning and Aging G.984.1. (For GPON OLT), IEEE 802.3ah (FOR Yes/No Control OLT EPON OLT), G.987.2 (FOR XGPON OLT), G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR WDMPON OLT), G.989.2 (FOR NGPON2 OLT) IEEE 802.3av (For 10G EPON OLT), IEEE
Annexure to ERs – Page 19 802.3ca (For Nx25G EPON) , IEEE 802.1Q (Testing Procedure) & 802.3
J3.5 MAC Address Limitation in PON IEEE 802.3. The data stream is received from only the number of streams specified. J3.6 Inbuilt port/ MAC Based 802.1x IEEE 802.1x. Authentication based on Authentication in PON IEEE 802.1x shall be supported. J3.7 MAC Learning Support at OLT IEEE 802.3.G.984.1. Yes/No J3.8 Maximum Bandwidth Limiting in PON G.984.3 Section 7.5 (For GPON OLT), IEEE max. 1Gbps (GPON) 802.3ah (FOR EPON OLT), G.987.2 (FOR XGPON OLT), G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR WDMPON OLT), G.989.2 (FOR NGPON2 OLT) IEEE 802.3av (For 10G EPON OLT), IEEE 802.3ca (For Nx25G EPON)
Annexure to ERs – Page 20 S. No. Parameter Name Standard Remarks J3.9 Minimum Guaranteed Bandwidth in PON G.984.3 Section 7.5. (For GPON OLT), IEEE minimum 512Kbps 802.3ah (FOR EPON OLT), G.987.2 (FOR XGPON OLT), G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR WDMPON OLT), G.989.2 (FOR NGPON2 OLT) IEEE 802.3av (For 10G EPON OLT), IEEE 802.3ca (For Nx25G EPON) J3.10 Minimum two classes of Classification in G.984.3 Section 7.5. (For GPON OLT), IEEE support of all TCONT-1, 2 PON 802.3ah (FOR EPON OLT), G.987.2 (FOR ,3, 4 types. XGPON OLT), G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR WDMPON OLT), G.989.2 (FOR NGPON2 OLT) IEEE 802.3av (For 10G EPON OLT), IEEE 802.3ca (For Nx25G EPON) J3.11 Password Based Authentication in PON ITU-T G.984.3 section 9.2.2, 12. Password based authentication should be supported. J3.12 Port-id Based VLAN Support at OLT G.984.1 (For GPON OLT), IEEE 802.3ah (FOR Yes/No Provision EPON OLT), G.987.2 (FOR XGPON OLT), of creating multiple port-id G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR based multiple VLAN WDMPON OLT), G.989.2 (FOR NGPON2 OLT) shall exist. IEEE 802.3av (For 10G EPON OLT), IEEE 802.3ca (For Nx25G EPON) & IEEE 802.1Q (Testing Procedure) J3.13 Switch Fabric Throughput Capability OLT G.984.1 (For GPON OLT), IEEE 802.3ah (FOR Demonstrate support for EPON OLT), G.987.2 (FOR XGPON OLT), full wired speed G.9807.1 (FOR XGSPON OLT), G.694.1 (FOR throughput by testing WDMPON OLT), G.989.2 (FOR NGPON2 traffic through one OLT), IEEE 802.3av (For 10G EPON OLT), randomly chosen port of IEEE 802.3ca (For Nx25G EPON) switch fabric then using this value coroborate with data sheet provided by chipset vendor.
Annexure to ERs – Page 21 J3.14 Max Throughput of PON RFC 2544 and respective standard i.e. 1)GPON- a) Nominal bit rate*. G.984.2/cl8.2.1, (2)XGPON- G.987.2/Cl 9.2.1,(3) When the OLT and the NGPON2-G.989.2/Cl 11.1.1,(4) XGSPON- end office are in their G.9807.1/Cl B.9.2.1, (5) EPON-IEEE 802.3ah (6) normal operating state 10G-EPON- Table Number 75-1 of IEEE 802.3 (accuracy of 1 x10-11) (2018). (7) Nx25G EPON- Table Number 141-2 to 141-5 of IEEE 802.3ca. b) Nominal bit rate*. When the end office is in its free-running mode (accuracy of 4.6 x10-6)
c) Nominal bit rate*. When the OLT is in its free- running mode (accuracy of 3.2 x10-5) J3.15 VLAN Stacking to Network Support at IEEE 802.1ad G.984.1, (For GPON OLT), IEEE Yes/No To test the OLT 802.3ah (FOR EPON OLT), G.987.2 (FOR double tagging support XGPON OLT), G.9807.1 (FOR XGSPON OLT), between ONT and OLT. G.694.1 (FOR WDMPON OLT), G.989.2 (FOR NGPON2 OLT) IEEE 802.3av (For 10G EPON OLT), IEEE 802.3ca (For Nx25G EPON) & IEEE 802.1Q(testing procedure). J3.16
*Nominal bit rate for different technology is defined in respective Standard
Annexure to ERs – Page 22
Annexure J4 – DSLAM Functional Test
Applicable to→ Standard IP- IP- Remarks DSLAM DSLAM Test Parameter↓ With splitter POTS SPLITTERS Y The broad specifications for splitter shall be: a. 600-ohm impedance b. ETSI harmonized impedance splitter (ETSI TR 101 728). IEEE Y Y To check if more than 1 vlan can be passed over VLAN Aggregation: 802.1p the same port in DSLAM The DSLAM shall terminate PVCs on DSL line and aggregate them over a single or multiple Customer- VLANs, Service-VLANs as well as a combination of them, at the uplink interface. It shall also implement 802.1p priority on the Ethernet flows. RFC Y Y Protocol Support 2131 DSLAM shall support DHCP based IP access with DHCP relay and DHCP option 82 for direct IP over Ethernet based access for video/gaming and other entertainment services. RFC 3046
Annexure to ERs – Page 23
PPPoE over ATM (U-interface): Figure 1 depicts the end- Y Y To check PPPoE session is established on the to-end protocol stacks associated with PPPoE access ADSL or VDSL system. Methodology is method mentioned in DSL forum technical report TR- 045. Annexure-E: group 3.3_test 1 & Test 2
may be carried out to cater this clause. It is
tested through protocol simulator. PTA or IP LAC PPP IWFIWF for for PPPoE IPoE PPP (Section 4.11.2) PPPoE Ethernet 802.1Q, PPPoE 802.1ad 802.1Q, 802.1ad Ethernet RFC Ethernet 2684 Ethernet
RFC 2684 ATM
ATM Some DSL Some 802.3 RG, DSL 802.3 Phy xTU-R Phy or t erminal xTU-R DSLAM BRAS Figure 1-
IPoE over ATM (U-interface): Figure 2 depicts the end- Y Y To check if IPOE is established on the ADSL or to-end protocol stacks associated with IPoE access VDSL system. Methodology is mentioned in method. DSL forum technical report TR-045. Annexure- E: group 3.3_test 1 & Test 2 may be carried out to cater this clause. It is tested through protocol simulator.
Annexure to ERs – Page 24
IP IWFforIWFfor IPoE IPoE IP IPI P
(Section4.9 &4.11.1)
Ethernet Ethernet 802.1Q, 802.1Q, Some 802.1ad 802.1ad mediamedia RFC RFC2684 Ethernet Ethernet 2684
ATM ATM ATM ATM
RG, RG, DSL DSL Some Some xTU-R or 802.3 Phy 802.3 Ph Phy or terminal xTU-R DSLAM BRAS Figure 2
Y Y 1. Limit the port on DSLAM to 1 mac and send Ethernet Scalability two mac traffic only one mac traffic which is 1. The device shall provide a means to limit the defined will run. number of MAC addresses learned on any given 2. Check more than 1 vlan can pass through the port. port 2. The device shall support placing all subscriber traffic into a single or multiple VLANs on an uplink. RFC Y Y Capability to be demonstrated as describes in Video application protocol support 2236 clause. IGMP Proxy
IGMPv2/v3 snooping RFC3376 Enable IGMP proxy and snooping and check if Further- multicast channel is learnt once the channel is 1. IGMP proxy shall handle multicast and control where the joint packets has to be replicated (in terms of specific customer VLANs or ports).
Annexure to ERs – Page 25 2. In upstream direction, IGMP proxy function shall forward IGMP messages from subscriber to multicast VLAN. 3. In downstream direction, multicast streams shall be multiplexed in to subscriber’s connection based on ‘Join’ messages received.
Filtering : The DSLAM shall allow the following filters Y Y Capability to be demonstrated as describes in to be defined: clause.
List of acceptable MAC destination addresses applicable to frames received at the upstream direction Set the MAC address to be allowed per port, send on bridged ports. traffic of that mac and see it is going through.
When attached to a bridged port, any frame received Send traffic of other mac and see that traffic is not with a destination MAC not specified in the list shall be going discarded. The DSLAM shall be capable of filtering L2 traffic configurable per Port/PVC/Service basis at least for the following parameters- a. Source IP and MAC Address per port, per PVC, per VLAN b. Destination IP and MAC Address per port, per PVC, per VLAN. Broadcast Handling: As far as Ethernet broadcast traffic Y Y Capability to be demonstrated as describes in is concerned, all downstream broadcast traffic shall be clause. discarded with the exception cases called for by DHCP Relay Agent, PPPoE Intermediate Agent, and IGMP Snooping/ IGMP Snooping and Proxy functions. Protection from ARP spoofing attacks Y Y 1. To check if DSLAM can block certain MAC. Source MAC Flooding 2. To check if broadcast mac can be controlled Broadcast control
Annexure to ERs – Page 26 L2 Peer to Peer (“hair-pin”) Forwarding 3. Communication on same vlan can be done or Source MAC Spoofing blocked. 4. To check if mac is learnt on the DSLAM
Note: Wherever RFC are referred, only ‘shall’ clauses given in the RFCs should be tested against the parameter referred in this ER.
Annexure-K: SDH Interface Parameters Parameter Group: PDH Interface (INTPDH) S. No. Interface Name Parameter Name Standard/ Limits/ Values Applicability/ Parameter Remarks K.1 STM-1 Electrical Input Jitter Tolerance STM-1 G.825 Table 4, Fig-1 clause-6.1.2.1 Electrical K.2 STM-1 Electrical Input Return Loss for STM-1 G.703 ≥15 dB over frequency range 8 Electrical MHz to 240 MHz K.3 STM-1 Electrical Nominal Bit Rate with G.703 155520 Kbps Tolerance STM-1 Electrical Int K.4 STM-1 Electrical Output Jitter for STM-1 G.825 500 to 1.3 MHz -1.5(UIpp) Electrical Int 65 k to 1.3 MHz-0.075 (UIpp) K.5 STM-1 Electrical Pulse Mask for STM-1 G.703 Fig 17-1 & 17-2 clause-17.4 Electrical Int K.6 STM-1 Optical Input Jitter Tolerance for STM- G.825 Fig. 1 ,clause-6.1.2.1 1 Opt K.7 STM-1 Optical Mean Launched Power for G.957 I-1,S-1.1, S-1.2: STM-1 Opt Int -8(max)& -15(min)(dBm)
Annexure to ERs – Page 27 S. No. Interface Name Parameter Name Standard/ Limits/ Values Applicability/ Parameter Remarks L-1.1,L-1.2, L-1.3: 0 (max)& - 5(min)(dBm) K.8 STM-1 Optical Nominal Bit Rate with G.957 155 520 Kbps Tolerance STM-1 Opt Int K.9 STM-1 Optical Operating Wavelength Range G.957 I-1: 1260a)-1360 for STM-1 Opt Int S-1.1: 1261a)- 1360 S-1.2: 1430-1576, 1430-1580 L-1.1: 1260a)-1360, 1263a)- 1360 L-1.2: 1480-1580 L-1.3: 1534-1566/1523-1577, 1480-1580 (nm) K.10 STM-1 Optical Output Jitter for STM-1 Opt Int G.783 0.5k to 1.3 MHz -0.30(UI) 65 k to 1.3MHz – 0.10 (UI) (1UI=6.43ns) K.11 STM-1 Optical Receiver Overload for STM-1 G.957 I-1,S-1.1, S-1.2: -8dBm Opt Int L-1.1,L-1.2, L-1.3: -10 dBm K.12 STM-1 Optical Receiver Sensitivity for STM-1 G.957 I-1: -23dBm Opt Int S-1.1, S-2.1: -28dBm L-1.1, L-1.2, L-1.3: -34 dBm
Annexure to ERs – Page 28 Annexure-P6: IP Conformance Parameters – IPV4 and Dual Stack – RFC 791 and RFC 4213 Parameter Group: IP Conformance (CONFIP) ( For IoT devices / gateways:- IPv4 / Dual IP parameters will be tested if feature is available. )
(Note 1: Product (OLT/ONU/ONT) comply either Dual stack test or IPv6 test.
Note 2: Bridge mode product (ONT) will demonstrate function test)
S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Applicability/ Remarks Section P6.1 IPV4 Parameters Set-A Model of operation RFC 791 Clause 2.2 MGW, SGW, PABX
P6.2 IPV4 Parameters Set-A Internet Header Format RFC 791 Clause 3.1 MGW, SGW, PABX, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P6.3 IPV4 Parameters Set-A Addressing RFC 791 Clause 3.2 MGW, SGW, PABX
P6.4 IPV4 Parameters Set-B Model of operation RFC 791 Clause 2.2 SBC
P6.5 IPV4 Parameters Set-B Gateways RFC 791 Clause 2.4 SBC, IoT Gateway
P6.6 IPV4 Parameters Set-B Interfaces RFC 791 Clause 3.3 SBC
P6.7 IPV4 Parameters Set-C Function Description RFC 791 Clause 2.3 SOFT SWITCH, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P6.8 IPV4 Parameters Set-C Gateways RFC 791 Clause 2.4 SOFT SWITCH
P6.9 IPV4 Parameters Set-C Interfaces RFC 791 Clause 3.3 SOFT SWITCH
Annexure to ERs – Page 29 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Applicability/ Remarks Section
P6.10 Dual IP layer operation: Dual IP layer operation: Address RFC 4213 Clause 2.1 WiFi Access Point, WiFi CPE, Address Configuration DSL NT Modem, ONU, ONT, SBC, IP Terminal, , IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
Product should demostrate support to all IPv6 services through respective RFCs and clause numbers. All Product variants should comply to either native IPv6 or Dual Stack test for PON devices.
P6.11 Dual IP layer operation: Dual IP layer operation: DNS RFC 4213 Clause 2.2 SBC, IP Terminal, PON ONT DNS Product should demostrate support to all IPv6 services through respective RFCs and clause numbers. All Product variants should comply to either native IPv6 or Dual Stack test for PON devices.
P6.12 Dual IP layer operation: Dual IP layer operation: Tunnelling RFC 4213 Clause 3 WiFi Access Point, WiFi CPE, Tunnelling DSL NT Modem, ONU, ONT, OLT, MGW, LMGW, PABX, SBC, Mobile Device, ONU, ONT,
Annexure to ERs – Page 30 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Applicability/ Remarks Section
CCNProduct should demostrate support to all IPv6 services through respective RFCs and clause numbers. All Product variants should comply to either native IPv6 or Dual Stack test for PON devices.
P6.13 Dual IP layer operation: Dual IP layer operation: Tunnelling RFC 4213 Clause 3.2.1 IoT Gateway, Feedback device, Tunnelling Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P6.14 Dual IP layer operation: Dual IP layer operation: RFC 4213 Clause 3.6 IoT Gateway, Feedback device, Decapsulation Decapsulation Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P6.15 Dual IP layer operation: Link Dual IP layer operation: Link Local RFC 4213 Clause 3.7 IoT Gateway, Feedback device, Local Address Address Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P6.16 Dual IP Layer Operation RFC Dual IP Layer Operation RFC 4213 - RFC 4213 Clause No. 3.2.1 4213 - Static Tunnel MTU Static Tunnel MTU
P6.17 Dual IP Layer Operation RFC Dual IP Layer Operation RFC 4213 - RFC 4213 Clause No. 3.6 4213 - Decapsulation Decapsulation
Annexure to ERs – Page 31 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Applicability/ Remarks Section
P6.18 Dual IP Layer Operation RFC Dual IP Layer Operation RFC 4213 - RFC 4213 Clause No. 3.7 4213 - Link-Local Addresses Link-Local Addresses
P6.19 Dual IP Layer Operation RFC Dual IP Layer Operation RFC 4213 - RFC 4213 Clause No. 3.8 4213 - Neighbor Discovery Neighbor Discovery over Tunnels over Tunnels
P6.20 Dual IP Layer Operation RFC Dual IP Layer Operation RFC 4213 - RFC 4213 Clause No. 5 4213 - Security Considerations Security Considerations
Annexure-P7: IPv6 Conformance Parameters Parameter Group: IP Conformance (CONFIP) ( For IoT devices / gateways:- IPv6 parameters will be tested if feature is available. )
S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Section Applicability/ Remarks
P7.1 IPV6 Header Parameters Header: Version Field RFC 2460 / Clause 3 SIP Terminal, SBC, RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.2 IPV6 Header Parameters Header: Traffic Class RFC 2460 / Clause 3 SIP Terminal, SBC, RFC 8200 Mobile Device, ONU,
Annexure to ERs – Page 32 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Section Applicability/ Remarks
ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.3 IPV6 Header Parameters Header: Flow Label RFC 2460 / Clause 3 SIP Terminal, SBC, RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.4 IPV6 Header Parameters Header: Payload Length RFC 2460 / Clause 3 SIP Terminal, SBC, RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.5 IPV6 Header Parameters Header: No next header after RFC 2460 / Clause 3 SIP Terminal, SBC, IPv6 Header RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT
Annexure to ERs – Page 33 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Section Applicability/ Remarks
Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.6 IPV6 Header Parameters Header: Hop Limit RFC 2460 / Clause 3 SIP Terminal, SBC, RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.7 IPV6 Header Parameters Header: Source and RFC 2460 / Clause 3 SIP Terminal, SBC, Destination Address RFC 8200 Mobile Device, ONU, ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.8 IPV6 Extn. Header Parameters IPv6 Extension Header Order RFC 2460 / Clause 4.1 Mobile Device, ONU, RFC 8200 ONT, OLT, CCN, IoT Gateway, Feedback device, Smart Electricity
Annexure to ERs – Page 34 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Section Applicability/ Remarks
meter, Tracking device, Smart camera, Smart Watch
P7.9 IPV6 Extn. Header Parameters IPv6 Extension Header Options RFC 2460 / Clause 4.2 Mobile Device, ONU, RFC 8200 ONT, OLT, CCN
P7.10 IPV6 Extn. Header Parameters IPv6 Extension Header Hop by RFC 2460 / Clause 4.3 Mobile Device, ONU, Hop Options RFC 8200 ONT, OLT, CCN
P7.11 IPV6 Extn. Header Parameters IPv6 Extension Header RFC 2460 / Clause 4.4 Mobile Device, ONU, Routing RFC 8200 ONT, OLT,CCN, IoT Gateway, Feedback device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.12 IPV6 Extn. Header Parameters IPV6 Extn. Header Fragment RFC 8200 Clause 4.5 IoT Gateway, Feedback Header device, Smart Electricity meter, Tracking device, Smart camera, Smart Watch
P7.13 IPV6 Packet Size Issues IPV6 Packet Size Issues RFC 8200 Clause 5 IoT Gateway parameter
P7.14 IPV6 Extension Header Order IPV6 Extension Header Order RFC 2460 / Clause No. 4, 5 RFC 8200 Annexure-P7
Annexure to ERs – Page 35 S. No. Parameter Name Individual Parameter Name IETF RFC Clause/ Section Applicability/ Remarks
Clause No. 4.1 RFC 4213
P7.15 IPV6 Options IPV6 Options RFC 2460 / Clause No. 4.2 RFC 8200 Annexure-P7
P7.16 IPV6 Routing Header IPV6 Routing Header RFC 2460 / Clause No. 4.4 RFC 8200 Annexure-P7
P7.17 IPV6 Fragment Header IPV6 Fragment Header RFC 2460 / Clause No. 4.5 RFC 8200 Annexure-P7
P7.18 IPV6 Destination Options IPV6 Destination Options RFC 2460 / Clause No. 4.6 Header Header RFC 8200 Annexure-P7
P7.19 IPV6 No Next Header IPV6 No Next Header RFC 2460 / Clause No. 4.7 RFC 8200 Annexure-P7
P7.20 IPV6 Packet Size Issues IPV6 Packet Size Issues RFC 2460 / Clause No. 5 RFC 8200 Annexure-P7
P7.21 IPV6 Upper-Layer Checksums IPV6 Upper-Layer Checksums RFC 2460 / Clause No. 8.1 RFC 8200 Annexure-P7
P7.22 IPV6 Responding to Packets IPV6 Responding to Packets RFC 2460 / Clause No. 8.4 Carrying Routing Headers Carrying Routing Headers RFC 8200 Annexure-P7
Annexure to ERs – Page 36 Annexure to ERs – Page 37
.
Appendix-I
IP Conformance Test Cases for RFCs
The Appendix-I consist of 11 tables, from Table -1 to Table - 11
Annexure to ERs – Page 38 Table-3: IPV6 as per RFC 2460 Parameter Group: IP Conformance (CONFIP)
RFC RFC Clause Remarks Section
IPv6 nodes must accept and attempt to process extension headers in any order and occurring any number of times 4.1 in the same packet, The Option Type identifiers are internally encoded such that their highest-order two bits specify the action that must be taken if the processing IPv6 node does not recognize the Option Type: 4.2 11 - discard the packet and, only if the packet's Destination Address was not a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type. The Option Type identifiers are internally encoded such that their highest-order two bits specify the action that 4.2 must be taken if the processing IPv6 node does not recognize the Option Type: 01 - discard the packet.
The Option Type identifiers are internally encoded such that their highest-order two bits specify the action that must be taken if the processing IPv6 node does not recognize the Option Type: 4.2 10 - discard the packet and, regardless of whether or not the packet's Destination Address was a multicast address, send an ICMP Parameter Problem, Code 2, message to the packet's Source Address, pointing to the unrecognized Option Type.
If Segments Left is zero, the node must ignore the Routing header and proceed to process the next header in the 4.4 packet, whose type is identified by the Next Header field in the Routing header.
Note: Wherever a particular IP test is implemented in a product through a RFC different from what is mentioned in ER, please obtain confirmation from Helpdesk before submitting application.
Annexure to ERs – Page 39 Table-4: IPV6 as per RFC 4861 Parameter Group: IP Conformance (CONFIP)
RFC RFC Clause Remarks Section A router MUST silently discard any received Router Solicitation messages that do not satisfy all of the following validity checks: 6.1.1 - The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router. A node MUST silently discard any received Router Advertisementmessages that do not satisfy all of the following validity checks: 6.1.2 - The IP Hop Limit field has a value of 255, i.e., the packetcould not possibly have been forwarded by a router. 6.2.2 A router MUST NOT send Router Advertisements out any interface that is not an advertising interface. A node MUST silently discard any received Neighbour Solicitation messages that do not satisfy all of the following validity checks: 7.1.1 - The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router. node MUST silently discard any received Neighbour Advertisementmessages that do not satisfy all of the following validity checks: 7.1.2 - The IP Hop Limit field has a value of 255, i.e., the packetcould not possibly have been forwarded by a router.
Note: Wherever a particular IP test is implemented in a product through a RFC different from what is mentioned in ER, please obtain confirmation from Helpdesk before submitting application.
Annexure to ERs – Page 40 Table-5: IPV6 as per RFC 4862 Parameter Group: IP Conformance (CONFIP)
RFC RFC Clause Remarks Section In order to improve the robustness of the Duplicate Address Detectionalgorithm, an interface MUST receive and process datagrams sent tothe all-nodes multicast address or solicited-node multicast addressof the tentative address 5.4.2 during the delay period. This does notnecessarily conflict with the requirement that joining the multicast group be delayed.
Duplicate Address Detection MUST NOT be performed on anycastaddresses (note that anycast addresses cannot 5.4 syntactically bedistinguished from unicast addresses). A node MUST silently discard any received Neighbour Solicitationmessages that do not satisfy all of the following validity checks: 7.1.1 - The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router. The contents of the Reserved field, and of any unrecognized options,MUST be ignored. Future, backward- 7.1.1 compatible changes to the protocol may specify the contents of the Reserved field or add new options;backward- incompatible changes may use different Code values. A node MUST silently discard any received Neighbour Advertisementmessages that do not satisfy all of the following validity checks: 7.1.2 - The IP Hop Limit field has a value of 255, i.e., the packet could not possibly have been forwarded by a router.
Note: Wherever a particular IP test is implemented in a product through a RFC different from what is mentioned in ER, please obtain confirmation from Helpdesk before submitting application.
Annexure to ERs – Page 41 Table-6: IPV6 as per RFC 1981 Parameter Group: IP Conformance (CONFIP)
RFC RFC Clause Remarks Section A node may receive a Packet Too Big message reporting anext-hop MTU that is less than the IPv6 minimum link 4 MTU. In thatcase, the node is not required to reduce the size of subsequentpackets sent on the path to less than the IPv6 minimum link MTU,
Note: Wherever a particular IP test is implemented in a product through a RFC different from what is mentioned in ER, please obtain confirmation from Helpdesk before submitting application.
Annexure to ERs – Page 42 Table-7: IPV6 as per RFC 4443 Parameter Group: IP Conformance (CONFIP)
RFC RFC Clause Remarks Section (a) If the message is a response to a message sent to one of thenode's unicast addresses, the Source Address of the 2.2 reply MUST bethat same address. If the message is a response to a message sent to any otheraddress, such as - a multicast group address, - an anycast address implemented by the node, or - a unicast address that does not belong to the node; the Source Address of the ICMPv6 packet MUST be a unicast address belonging to the node 2.4 If an ICMPv6 informational message of unknown type is received,it MUST be silently discarded. An ICMPv6 error message MUST NOT be originated as a result ofreceiving the following: 2.4 (e.3) A packet destined to an IPv6 multicast address. An ICMPv6 error message MUST NOT be originated as a result ofreceiving the following: 2.4 (e.6) A packet whose source address does not uniquely identify asingle node -- e.g., the IPv6 Unspecified Address, an IPv6multicast address, or an address known by the ICMP messageoriginator to be an IPv6 anycast address.
Note: Wherever a particular IP test is implemented in a product through a RFC different from what is mentioned in ER, please obtain confirmation from Helpdesk before submitting application.
Annexure to ERs – Page 43 List-1(GPON)
Table .1 Details mentioned Sl No Parameter under Clauses 1 G-PON transmission convergence (GTC) layer 1.0 2 GTC layer framing 2.0 3 GTC messages 3.0 4 Security 4.0 5 Network degradation check 5.0 6 Activation method 6.0
1.0 G-PON Transmission Convergence (GTC) layer 1. 1 GTC Protocol Stacks:
Reference Value/Comment Sl No Parameter in G.984.3 Protocol stack for the C/M- Meet the requirement of Cl 7.1.2 7.1.2 1. plane Meet the requirement of Cl 7.1.3 2. Protocol stack for the U-plane 7.1.3
1.2. GTC key functions: Sl No Parameter Reference Value/Comment in G.984.3 Media access control 7.2.1 Meet the requirement of Cl 1. 7.2.1 ONU registration 7.2.2 Meet the requirement of Cl 2. 7.2.2
1.3 Functions of Sublayers in GTC: Sl No Reference Value/Comment Parameter in G.984.3 Meet the requirement of Cl 1. GTC framing sublayer 7.3.1 7.3.1 Multiplexing and 7.3.1 Meet the requirement of Cl 2. demultiplexing 7.3.1
Annexure to ERs – Page 44 List-1(GPON)
Header creation and decoding 7.3.1 Meet the requirement of Cl 3. 7.3.1 Internal routing function based 7.3.1 Meet the requirement of Cl 4. on Alloc-ID 7.3.1 GTC adaptation sublayer and 7.3.2 Meet the requirement of Cl 5. interface for upper entities 7.3.2 GEM TC adapter 7.3.2 Meet the requirement of Cl 6. 7.3.2 OMCI adapter 7.3.2 Meet the requirement of Cl 7. 7.3.2
1.4 Dynamic Bandwidth Assignment: Sl No Reference Value/Comment Parameter in G.984.3 1. PON DBA abstraction 7.4.1 Meet the requirement of Cl 7.4.1 2. DBA methods 7.4.3 Meet the requirement of Cl 7.4.3 3. Alloc-ID traffic descriptors and 7.4.6 Meet the requirement of Cl T-CONT types 7.4.6 4. DBA performance 7.4.7 Meet the requirement of Cl requirements 7.4.7
1.5 Resource Allocation and Quality of Service (QoS):
Sl No Parameter Reference Value/Comment in G.984.3 Resource allocation and quality 7.5 Meet the requirement of Cl 7.5 1. of service (QoS)
2.0 GTC layer framing Parameters in this clause are for GTC layer framing for downstream and upstream directions. 2.1 Downstream GTC frame structure The following conformance parameters are described in this clause:
Annexure to ERs – Page 45 List-1(GPON)
Sl No Parameter Reference Value/Comment in G.984.3 1. Downstream GTC frame Figure 8-2 Meet the requirement of Figure structure 8-2 2. Bit and byte order 8.1.1 Meet the requirement of Cl 8.1.1 3. Scrambling of the downstream 8.1.2 Meet the requirement of Cl GTC frame 8.1.2 4. Physical control block Figure 8-3 Meet the requirement of Figure downstream (PCBd) 8-3 5. Physical synchronization Figure 8-4 Meet the requirement of Figure (PSync) field 8-4 6. Ident field Figure 8-5 Meet the requirement of Figure 8-5 7. PLOAMd field 8.1.3.3 Meet the requirement of Cl 8.1.3.3 8. BIP field 8.1.3.4 Meet the requirement of Cl 8.1.3.4 9. PLend field Figure 8-6 Meet the requirement of Figure 8-6 10. BWmap fields Figure 8-7 Meet the requirement of Figure 8-7 11. Allocation ID field 8.1.3.6.1 Meet the requirement of Cl 8.1.3.6.1 12. Flags field 8.1.3.6.2 Meet the requirement of Cl 8.1.3.6.2 13. StartTime field 8.1.3.6.3 Meet the requirement of Cl 8.1.3.6.3 14. StopTime field 8.1.3.6.4 Meet the requirement of Cl 8.1.3.6.4 15. CRC field 8.1.3.6.5 Meet the requirement of Cl 8.1.3.6.5 16. TC payload fields 8.1.4 Meet the requirement of Cl 8.1.4
2.2 Upstream burst structure The following conformance parameters are described in this clause: Sl No Parameter Reference Value/Comment in G.984.3 Annexure to ERs – Page 46 List-1(GPON)
1. Scrambling of the upstream 8.2.1 Meet the requirement of Cl burst 8.2.1 2. Physical layer overhead 8.2.2 Meet the requirement of Cl upstream (PLOu) 8.2.2 3. PLOAM upstream (PLOAMu) 8.2.3 Meet the requirement of Cl 8.2.3 4. Power levelling sequence 8.2.4 Meet the requirement of Cl upstream (PLSu) 8.2.4 5. Dynamic bandwidth report 8.2.5 Meet the requirement of Cl upstream (DBRu) 8.2.5 6. Upstream GTC payload section 8.2.6 Meet the requirement of Cl 8.2.6 2.3 Mapping of GEM frames into GTC payload The following conformance parameters are described in this clause: Sl No Parameter Reference Value/Comment in G.984.3 1. Mapping of GEM frames into Figure 8-10 Meet the requirement of Figure GTC payload 8-10 2. GEM header format Figure 8-11 Meet the requirement of Figure 8-11 3. GEM frame delineation and Figure 8-12 Meet the requirement of Figure synchronization 8-12 4. User frame fragmentation Figure 8-13 Meet the requirement of Figure 8-13 5. Mapping of user services into 8.3.4 Meet the requirement of Cl 8.3.4 GEM frame
2.4 Status reporting DBA signalling and configuration The following conformance parameters are described in this clause: Sl No Parameter Reference Value/Comment in G.984.3
Annexure to ERs – Page 47 List-1(GPON)
1. Definition of the DBRu 8.4.1 Meet the requirement of Cl 8.4.1 report 2. Buffer occupancy 8.4.2 Meet the requirement of Cl 8.4.2 representation 3. DBRu format modes 8.4.3 Meet the requirement of Cl 8.4.3 4. Options available to the 8.4.4 Meet the requirement of Cl 8.4.4 ONU and OLT 5. Backward compatibility 8.4.5 Meet the requirement of Cl 8.4.5 and handling of exceptional cases 6. Implementation note on 8.4.6 Meet the requirement of Cl 8.4.6 Mode 1 DBRu reporting
3.0 GTC messages: There are three methods to convey OAM information between the network management station the OLT on the one hand and the ONUs on the other hand: a) Embedded OAM channel b) Physical layer OAM (PLOAM) messaging channel c) ONU management and control interface (OMCI) 3.1 Downstream PLOAM structure The following conformance parameters are described in this clause: Reference Value/Comment Sl No Message name in G.984.3 1 Upstream_Overhead 9.2.1 Meet the requirement of Cl 9.2.1 2 Assign_ONU-ID 9.2.1 Meet the requirement of Cl 9.2.1 3 Ranging_Time 9.2.1 Meet the requirement of Cl 9.2.1 4 Deactivate_ONU-ID 9.2.1 Meet the requirement of Cl 9.2.1 5 Disable_Serial_Number 9.2.1 Meet the requirement of Cl 9.2.1 6 Encrypted_Port-ID 9.2.1 Meet the requirement of Cl 9.2.1 7 Request_Password 9.2.1 Meet the requirement of Cl 9.2.1 8 Assign_Alloc-ID 9.2.1 Meet the requirement of Cl 9.2.1 9 No message 9.2.1 Meet the requirement of Cl 9.2.1 10 POPUP 9.2.1 Meet the requirement of Cl 9.2.1 11 Request_Key 9.2.1 Meet the requirement of Cl 9.2.1 12 Configure Port-ID 9.2.1 Meet the requirement of Cl 9.2.1 Annexure to ERs – Page 48 List-1(GPON)
13 Physical_Equipment_ Error (PEE) 9.2.1 Meet the requirement of Cl 9.2.1 14 Change_Power_Level 9.2.1 Meet the requirement of Cl 9.2.1 15 PST message 9.2.1 Meet the requirement of Cl 9.2.1 16 BER Interval 9.2.1 Meet the requirement of Cl 9.2.1 17 Key_Switching_Time 9.2.1 Meet the requirement of Cl 9.2.1 18 Extended_Burst_ 9.2.1 Meet the requirement of Cl 9.2.1 Length
3.2 Upstream PLOAM structure The following conformance parameters are described in this clause: Reference Value/Comment Sl No Message name in G.984.3 1 Serial_Number_ONU 9.2.2 Meet the requirement of Cl 9.2.2 2 Password 9.2.2 Meet the requirement of Cl 9.2.2 3 Dying_Gasp 9.2.2 Meet the requirement of Cl 9.2.2 3 Dying_Gasp 9.2.2 Meet the requirement of Cl 9.2.2 4 No message 9.2.2 Meet the requirement of Cl 9.2.2 5 Encryption key 9.2.2 Meet the requirement of Cl 9.2.2 6 Physical_Equipment_Error (PEE) 9.2.2 Meet the requirement of Cl 9.2.2 7 PST message 9.2.2 Meet the requirement of Cl 9.2.2 8 Remote error indication (REI) 9.2.2 Meet the requirement of Cl 9.2.2 9 Acknowledge 9.2.2 Meet the requirement of Cl 9.2.2
3.3 Requirements of the management interface specification The OMCI is used by the OLT to control an ONT. This protocol allows the OLT to: a) establish and release connections across the ONT; b) manage the UNIs at the ONT; c) request configuration information and performance statistics; d) autonomously inform the system operator of events such as link failures. The following conformance parameters are described in this clause
Annexure to ERs – Page 49 List-1(GPON)
Sl No Parameter Reference Value/Comment in G.984.4 (or 988) 1. configuration management 7.1 Meet the requirement of Cl 7.1 2. configuration of equipment 7.1 Meet the requirement of Cl 7.1 3. configuration of the UNIs 7.1 Meet the requirement of Cl 7.1 4. configuration of the GEM port 7.1 Meet the requirement of Cl 7.1 network CTPs 5. configuration of interworking 7.1 Meet the requirement of Cl 7.1 termination points 6. configuration of the OAM 7.1 Meet the requirement of Cl 7.1 flows 7. configuration of the physical 7.1 Meet the requirement of Cl 7.1 ports 8. configuration of GAL profiles 7.1 Meet the requirement of Cl 7.1 9. configuration of service profiles 7.1 Meet the requirement of Cl 7.1 10. configuration of traffic 7.1 Meet the requirement of Cl 7.1 descriptors 11. configuration of AAL profile, 7.1 Meet the requirement of Cl 7.1 in a limited sense 12. fault management 7.2 Meet the requirement of Cl 7.2 13. performance management 7.3 Meet the requirement of Cl 7.3 14. security management 7.4 Meet the requirement of Cl 7.4 3.4 Protocol-independent MIB for the OMCI This Recommendation defines a protocol necessary to support capabilities identified by [ITU-T G.984.2] and [ITU-T G.984.3].
The following conformance parameters are described in this clause
Sl No Reference Value/Comment Parameter in G.984.4 (or 988) 1. Managed entities 8.1 Meet the requirement of Cl 8.1 Annexure to ERs – Page 50 List-1(GPON)
2. Managed entity relation 8.2 Meet the requirement of Cl 8.2 diagrams
4.0 Security This clause discusses the data security issues in PON. It discusses the threat model that the security is intended to counter. It then discusses the basic key exchange and activation method. The basic concern in PON is that the downstream data is broadcasted to all ONUs attached to the PON. If a malicious user were to re-programme his ONU, then the malicious user could listen to all the downstream data of all the users. It is this 'eavesdropping threat' that the PON security system is intended to counter. Specification The following conformance parameters are described in this clause: Sl No Parameter Reference Value/Comment in G.984.3 1. Encryption system 12.2 Meet the requirement of Cl 12.2 2. Data encryption key exchange 12.3 Meet the requirement of Cl 12.3 3. Data encryption key switch- 12.4 Meet the requirement of Cl 12.4 over
5.0 Network degradation check Alarms and performance monitoringFollowing parameters encompasses mechanisms to check that any telecom equipment does not degrade performance of existing network to which it is connected.detect link failure and monitor the health and performance of links. 5.1 Items detected at OLT The following conformance parameters are described in this clause Sl No Type Description Reference Value/Comment in G.984.3 1. LOSi Loss of signal for ONUi 11.1.1 Meet the requirement of Cl 11.1.1 2. LOS Loss of signal 11.1.1 Meet the requirement of Cl 11.1.1 3. LOFi Loss of frame of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 4. DOWi Drift of window of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 5. SFi Signal fail of ONUi 11.1.1 Meet the requirement of Cl 11.1.1
Annexure to ERs – Page 51 List-1(GPON)
6. SDi Signal degraded of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 7. LCDGi Loss of GEM channel 11.1.1 Meet the requirement delineation of Cl 11.1.1 8. RDIi Remote defect indication of 11.1.1 Meet the requirement ONUi of Cl 11.1.1 9. TF Transmitter failure 11.1.1 Meet the requirement of Cl 11.1.1 10. SUFi Start-up failure of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 11. DFi Deactivate failure of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 12. LOAi Loss of acknowledge with 11.1.1 Meet the requirement ONUi of Cl 11.1.1 13. DGi Receive dying-gasp of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 14. LOAMi Loss of PLOAM for ONUi 11.1.1 Meet the requirement of Cl 11.1.1 15. MEMi Message_Error message 11.1.1 Meet the requirement from ONUi of Cl 11.1.1 16. MISi Link mismatch of ONUi 11.1.1 Meet the requirement of Cl 11.1.1 17. PEEi Physical equipment error of 11.1.1 Meet the requirement ONUi of Cl 11.1.1 18. TIWi Transmission interference 11.1.1 Meet the requirement warning of Cl 11.1.1 19. TIA Transmission interference 11.1.1 Meet the requirement alarm of Cl 11.1.1 20. LOKi Loss of key synch with 11.1.1 Meet the requirement ONUi of Cl 11.1.1
5.2 Items detected at ONU The following conformance parameters are described in this clause Sl No Type Description Reference Value/Comment
Annexure to ERs – Page 52 List-1(GPON)
in G.984.3 1. LOS Loss of signal 11.1.2 Meet the requirement of Cl 11.1.2 2. LOF Loss of frame 11.1.2 Meet the requirement of Cl 11.1.2 3. SF Signal failed 11.1.2 Meet the requirement of Cl 11.1.2 4. SD Signal degraded 11.1.2 Meet the requirement of Cl 11.1.2 5. LCDG Loss of GEM channel 11.1.2 Meet the requirement delineation of Cl 11.1.2 6. TF Transmitter failure 11.1.2 Meet the requirement of Cl 11.1.2 7. SUF Start-up failure 11.1.2 Meet the requirement of Cl 11.1.2 8. MEM Message error message 11.1.2 Meet the requirement of Cl 11.1.2 9. DACT Deactivate ONU-ID 11.1.2 Meet the requirement of Cl 11.1.2 10. DIS Disabled ONU 11.1.2 Meet the requirement of Cl 11.1.2 11. MIS Link mismatching 11.1.2 Meet the requirement of Cl 11.1.2 12. PEE Physical equipment error 11.1.2 Meet the requirement of Cl 11.1.2 13. RDI Remote defect indication in 11.1.2 Meet the requirement ONU of Cl 11.1.2
6.0 Activation method The term "activation process" refers to the set of distributed procedures allowing an inactive ONU to join or resume operations on the PON. The activation process includes three phases: parameter learning, serial number acquisition and ranging. The following conformance parameters are described in this clause
Annexure to ERs – Page 53 List-1(GPON)
Reference Value/Comment Sl No Parameters in G.984.3 1. ONU activation states, timers 10.2.1 Meet the requirement of Cl and counters 10.2.1 2. ONU state specification 10.2.2 Meet the requirement of Cl 10.2.2 3. ONU state diagram 10.2.3 Meet the requirement of Cl 10.2.3 4. ONU functional transitions 10.2.4 Meet the requirement of Cl 10.2.4 5. ONU events 10.2.5 Meet the requirement of Cl 10.2.5 6. OLT common part 10.3.1 Meet the requirement of Cl 10.3.1 7. ONU-specific part 10.3.2 Meet the requirement of Cl 10.3.2 8. Quiet window creation 10.3.3 Meet the requirement of Cl 10.3.3 9. Activation process failure 10.3.4 Meet the requirement of Cl detection 10.3.4 10. Phase monitoring and updating 10.3.5 Meet the requirement of Cl equalization delay 10.3.5 11. Fibre distance measurement 10.3.6 Meet the requirement of Cl 10.3.6 12. Timing relationships during 10.4.2 Meet the requirement of Cl serial number acquisition 10.4.2 13. Size of the quiet window during 10.4.2.2 Meet the requirement of Cl serial number acquisition 10.4.2.2
Annexure to ERs – Page 54 List-2(XGPON)
List-2(XGPON) Sl No Clause in Parameter standard 1 Transmission Convergence Layer Structure 1.0 2 OAM, PLOAM and OMCI Implementation 2.0 3 ONU Activation 3.0 4 Security 4.0 5 Network degradation check 5.0 6 DBA 6.0
1.0 Transmission Convergence Layer Structure The XGTC layer is composed of three sublayers: the XGTC service adaptation sublayer, the XGTC framing sublayer, and the XGTC PHY adaptation sublayer. The following conformance parameters are described in this clause
1.1 XG-PON TC framing sublayer structure This clause specifies the structure of the downstream XGTC frame and upstream XGTC burst along with the format of the downstream XGTC frame header, upstream XGTC burst header, and upstream XGTC burst trailer. 1.1.1 Downstream XGTC framing The following conformance parameters are described in this clause
Annexure to ERs – Page 55 List-2(XGPON)
Sl Parameter Reference in Value/Comment No G.987.3 1. HLend structure 8.1.1 Meet the requirement of 8.1.1 2. BWmap partition 8.1.2 Meet the requirement of 8.1.2 3. Alloc-ID field 8.1.2.1 Meet the requirement of 8.1.2.1 4. Flags field 8.1.2.2 Meet the requirement of 8.1.2.2 5. StartTime field 8.1.2.3 Meet the requirement of 8.1.2.3 6. GrantSize field 8.1.2.4 Meet the requirement of 8.1.2.4 7. Forced wake-up indication 8.1.2.5 Meet the (FWI) bit requirement of 8.1.2.5 8. BurstProfile field 8.1.2.6 Meet the requirement of 8.1.2.6 9. HEC field 8.1.2.7 Meet the requirement of 8.1.2.7 10. PLOAMd partition 8.1.4 Meet the requirement of 8.1.4
1.1.2 Upstream XGTC framing The following conformance parameters are described in this clause Sl No Parameter Reference in G.987.3 Value/Comment
1. Upstream XGTC burst header 8.2.1 Meet the requirement of
Annexure to ERs – Page 56 List-2(XGPON)
8.2.1 2. ONU-ID field 8.2.1.1 Meet the requirement of 8.2.1.1 3. Ind field 8.2.1.2 Meet the requirement of 8.2.1.2 4. HEC field 8.2.1.3 Meet the requirement of 8.2.1.3 5. Upstream PLOAM (PLOAMu) 8.2.1.4 Meet the field requirement of 8.2.1.4 6. Allocation overhead 8.2.2 Meet the requirement of 8.2.2 7. BufOcc field 8.2.2.1 Meet the requirement of 8.2.2.1 8. CRC field 8.2.2.2 Meet the requirement of 8.2.2.2 9. Upstream XGTC burst trailer 8.2.3 Meet the requirement of 8.2.3
1.2 XG-PON TC service adaptation -XGEM structure: The following conformance parameters are described in this clause Sl No Parameter Reference in G.987.3 Value/Comment
1. XGEM framing 9.1 Meet the requirement of 9.1 2. XGTC payload structure 9.1.1 Meet the requirement of 9.1.1 3. XGEM frame header 9.1.2 Meet the requirement of 9.1.2 4. XGEM payload format 9.1.3 Meet the requirement of 9.1.3 5. Idle XGEM frame 9.1.4 Meet the
Annexure to ERs – Page 57 List-2(XGPON)
requirement of 9.1.4 6. XGEM frame delineation 9.2 Meet the requirement of 9.2 7. SDU fragmentation 9.3 Meet the requirement of 9.3 8. Mapping of services into XGEM 9.4 Meet the frames requirement of 9.4 9. Ethernet over XGEM 9.4.1 Meet the requirement of 9.4.1 10. MPLS over XGEM 9.4.2 Meet the requirement of 9.4.2
1.3 XG-PON TC PHY adaptation sublayer structure: This clause discusses structure of physical synchronization and delineation, forward error correction, and scrambling for the downstream and upstream transmission in XG- PON. The following conformance parameters are described in this clause Sl No Parameter Reference in G.987.3 Value/Comment
1. Downstream PHY frame 10.1 Meet the requirement of 10.1 2. Downstream physical 10.1.1 Meet the synchronization block (PSBd) requirement of 10.1.1 3. Physical synchronization 10.1.1.1 Meet the sequence (PSync) requirement of 10.1.1.1 4. Superframe counter structure 10.1.1.2 Meet the requirement of 10.1.1.2 5. PON-ID structure 10.1.1.3 Meet the requirement of 10.1.1.3 6. PSBd field scrambling 10.1.1.4 Meet the requirement of 10.1.1.4 7. ONU downstream 10.1.2 Meet the synchronization requirement of 10.1.2 8. Downstream PHY frame 10.1.3 Meet the Annexure to ERs – Page 58 List-2(XGPON)
payload requirement of 10.1.3 9. Upstream PHY frames and 10.2 Meet the upstream PHY bursts requirement of 10.2 10. Upstream physical 10.2.1 Meet the synchronization block requirement (PSBu) of 10.2.1 11. Upstream PHY burst 10.2.2 Meet the payload requirement of 10.2.2 12. Guard time 10.2.3 Meet the requirement of 10.2.3 13. Forward error correction 10.3 Meet the requirement of 10.3 14. Downstream FEC 10.3.1 Meet the requirement of 10.3.1 15. Upstream FEC 10.3.2 Meet the requirement of 10.3.2 16. Upstream FEC on/off 10.3.2.3 Meet the control requirement of 10.3.2.3 17. Scrambling 10.4 Meet the requirement of 10.4 18. Scrambling of the 10.4.1 Meet the downstream PHY frame requirement of 10.4.1 19. Scrambling of the 10.4.2 Meet the upstream PHY burst requirement of 10.4.2
2.0 OAM, PLOAM and OMCI Implementation The control, operation, and management information in an XG-PON system is carried over three channels: embedded OAM, PLOAM and OMCI. The embedded OAM and PLOAM channels manage the functions of the PMD and XGTC layers. OMCI provides a uniform system for managing higher (service-defining) layers. Annexure to ERs – Page 59 List-2(XGPON)
2.1 PLOAM message format: The PLOAM message structure with each field being further defined in the following sub-clauses 3.1.1 Downstream message formats: The following conformance parameters are described in this clause Sl Parameter Reference in Value/Comment No G.987.3 1. Downstream message formats 11.3.3 Meet the requirement of 11.3.3 2. Profile message 11.3.3.1 Meet the requirement of 11.3.3.1 3. Assign_ONU-ID message 11.3.3.2 Meet the requirement of 11.3.3.2 4. Ranging_Time message 11.3.3.3 Meet the requirement of 11.3.3.3 5. Deactivate_ONU-ID message 11.3.3.4 Meet the requirement of 11.3.3.4 6. Disable_Serial_Number message 11.3.3.5 Meet the requirement of 11.3.3.5 7. Request_Registration message 11.3.3.6 Meet the requirement of 11.3.3.6 8. Assign_Alloc-ID message 11.3.3.7 Meet the requirement of 11.3.3.7 9. Key_Control message 11.3.3.8 Meet the requirement of 11.3.3.8 10. Sleep_Allow message 11.3.3.9 Meet the requirement of 11.3.3.9
2.1.2 Upstream message formats: Annexure to ERs – Page 60 List-2(XGPON)
The following conformance parameters are described in this clause Sl Parameter Reference in Value/Comment No G.987.3 1. Serial_Number_ONU message 11.3.4.1 Meet the requirement of 11.3.4.1 2. Registration message 11.3.4.2 Meet the requirement of 11.3.4.2 3. Key_Report message 11.3.4.3 Meet the requirement of 11.3.4.3 4. Acknowledgment message 11.3.4.4 Meet the requirement of 11.3.4.4 5. Sleep_Request message 11.3.4.5 Meet the requirement of 11.3.4.5
2.2 OMCI specification The OMCI is used by the OLT to control an ONT. This protocol allows the OLT to: a) establish and release connections across the ONT; b) manage the UNIs at the ONT; c) request configuration information and performance statistics; d) autonomously inform the system operator of events such as link failures.
The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.988 15. Configuration management 7.1 Meet the requirement of 7.1 16. fault management 7.2 Meet the requirement of 7.2 17. performance management 7.3 Meet the requirement of 7.3 18. security management 7.4 Meet the Annexure to ERs – Page 61 List-2(XGPON)
requirement of 7.4 2.2.1 Protocol-independent MIB for the OMCI This Recommendation defines a protocol necessary to support capabilities identified by [ITU-T G.987.2] and [ITU-T G.987.3].
The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.988 3. Managed entities 8.1 Meet the requirement of 8.1 4. Managed entity relation diagrams 8.2 Meet the requirement of 8.2
3.0 ONU activation The term "activation process" refers to the set of distributed procedures allowing an inactive ONU to join or resume operations on the PON. The activation process includes three phases: synchronization, serial number acquisition, and ranging. The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.987.3 1. Power up 12.2.4 Meet the requirement of 12.2.4 2. Downstream synchronization 12.2.4 Meet the attained(LODS cleared) requirement of 12.2.4 3. Loss of downstream 12.2.4 Meet the synchronization(LODS) requirement of 12.2.4 4. Receive broadcast Profile 12.2.4 Meet the PLOAM requirement of 12.2.4 5. Receive unicast Profile PLOAM 12.2.4 Meet the requirement of 12.2.4 6. Receive broadcast Serial Number 12.2.4 Meet the grant requirement of 12.2.4 7. Receive Assign ONU ID PLOAM 12.2.4 Meet the (SN match) requirement of Annexure to ERs – Page 62 List-2(XGPON)
12.2.4 8. Receive Ranging grant 12.2.4 Meet the requirement of 12.2.4 9. Receive directed Ranging time 12.2.4 Meet the PLOAM requirement of 12.2.4 10. Receive broadcast Ranging time 12.2.4 Meet the PLOAM requirement of 12.2.4 11. TO1 expired 12.2.4 Meet the requirement of 12.2.4 12. Receive directed Deactivate ONU 12.2.4 Meet the ID PLOAM requirement of 12.2.4 13. Receive broadcast Deactivate 12.2.4 Meet the ONU ID PLOAM requirement of 12.2.4 14. Receive Disable PLOAM – 12.2.4 Meet the Disable specific SN option requirement of (SN match) 12.2.4 15. Receive Disable PLOAM 12.2.4 Meet the – Disable All option requirement of 12.2.4 16. Receive Disable PLOAM – 12.2.4 Meet the Enable specific SN option(SN requirement of match) 12.2.4 17. Receive Disable PLOAM 12.2.4 Meet the – Enable All option requirement of 12.2.4 18. TO2 expired 12.2.4 Meet the requirement of 12.2.4 19. Receive bandwidth grant with 12.2.4 Meet the data allocation requirement of 12.2.4 20. Receive directed PLOAM grant 12.2.4 Meet the requirement of Annexure to ERs – Page 63 List-2(XGPON)
12.2.4 21. Receive Request_ Registration 12.2.4 Meet the PLOAM requirement of 12.2.4 22. Receive Assign Alloc ID PLOAM 12.2.4 Meet the requirement of 12.2.4 23. Receive Key Control PLOAM 12.2.4 Meet the requirement of 12.2.4 24. Receive Sleep Allow PLOAM 12.2.4 Meet the requirement of 12.2.4
3.1 OLT and ONU timing relationships The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.987.3 1. Timing of ONU upstream 13.1.1 Meet the requirement transmissions of 13.1.1 2. Timing relationships and quiet 13.1.2 Meet the requirement window during serial number of 13.1.2 acquisition 3. Timing relationships and quiet 13.1.3 Meet the requirement window during ranging of 13.1.3
4.0 Security This clause discusses threat models characteristic for the XG-PON operating environment, and specifies authentication, data integrity, and privacy protection aspects of the system. XG-PON security is intended to protect against the following threats: a) Since downstream data is broadcast to all ONUs attached to the XG-PON OLT, a malicious user capable of replacing or re-programming an ONU would be capable of receiving all downstream data intended for all connected users. b) Since upstream data received by the optical line terminal (OLT) can originate from any ONU attached to the XG-PON optical distribution network (ODN), a malicious user capable of replacing or re-programming an ONU could forge packets so as to impersonate a different ONU (i.e., theft of service). c) An attacker could connect a malicious device at various points on the infrastructure (e.g., by tampering with street cabinets, spare ports, or fibre cables). Such a device could intercept and/or generate traffic. Depending on the location of such a device, it could impersonate an OLT or alternatively it could impersonate an ONU. d) A malicious user in any of the above scenarios could record packets transmitted on the passive optical network (PON) and replay them back onto the PON later, or conduct bit-flipping attacks. Annexure to ERs – Page 64 List-2(XGPON)
The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.987.3 1. Threat model for XG-PON 15.1 Meet the requirement of 15.1 2. Authentication 15.2 Meet the requirement of 15.2 3. Key derivation 15.3 Meet the requirement of 15.3 4. XGEM payload encryption system 15.4 Meet the requirement of 15.4 5. Data encryption key exchange and 15.5 Meet the requirement activation mechanism of 15.5 6. Integrity protection and data origin 15.6 Meet the requirement verification for PLOAM of 15.6 7. Integrity protection and data origin 15.7 Meet the requirement verification for OMCI of 15.7 8. Integrity and data origin verification 15.8 Meet the requirement key switching of 15.8 9. XG-PON systems with reduced data 15.9 Meet the requirement encryption strength of 15.9
5.0 Network degradation check: Following parameters encompasses mechanisms to check that any telecom equipment does not degrade performance of existing network to which it is connected.This clause focuses on mechanisms to detect link failure and monitor the health and performance of links. 5.1 Monitoring The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.987.3 1. PHY PM Table 14-1 Meet the requirement of 2. Corrected FEC bytes Table 14-1 Table 14-1 3. Corrected FEC codewords Table 14-1 4. Uncorrectable FEC codewords Table 14-1 5. Total FEC codewords Table 14-1
Annexure to ERs – Page 65 List-2(XGPON)
Sl No Reference in Parameter Value/ Reference G.987.3 6. Total received words protected by Table 14-1 BIP-32 7. BIP-32 errors Table 14-1 8. PSBd HEC error count Table 14-1 9. XGTC HEC error count Table 14-1 10. Unknown profile Table 14-1 11. XGEM PM Table 14-1 12. Transmitted XGEM frames Table 14-1 13. Transmitted XGEM frames per Table 14-1 XGEM port 14. Received XGEM frames Table 14-1 15. Received XGEM frames per Table 14-1 XGEM port 16. Count of the number of Table 14-1 transmitted XGEM frames with LF bit NOT set 17. XGEM frame header HEC errors Table 14-1 18. Count of XGTC frame words lost Table 14-1 due to GEM frame HEC error 19. XGEM key errors Table 14-1 20. PLOAM PM Table 14-1 21. SN grant count Table 14-1 22. PLOAM MIC errors Table 14-1 23. PLOAM timeouts Table 14-1 24. DG count Table 14-1 25. Downstream PLOAM message Table 14-1 count 26. Profile Table 14-1 27. Assign_ONU-ID Table 14-1
Annexure to ERs – Page 66 List-2(XGPON)
Sl No Reference in Parameter Value/ Reference G.987.3 28. Ranging_Time Table 14-1 29. Deactivate_ONU-ID Table 14-1 30. Disable_Serial_Number Table 14-1 31. Request_Registration Table 14-1 32. Assign_Alloc-ID Table 14-1 33. Key_Control Table 14-1 34. Sleep_Allow Table 14-1 35. Upstream PLOAM message count Table 14-1 36. Serial_Number_ONU Table 14-1 37. Registration Table 14-1 38. Key_Report Table 14-1 39. Acknowledgement Table 14-1 40. Sleep_Request Table 14-1 41. OMCI PM Table 14-1 42. OMCI baseline message count Table 14-1 43. OMCI extended message count Table 14-1 44. Autonomous messages Table 14-1 45. OMCI MIC errors Table 14-1 46. Energy conservation Table 14-1 47. Time spent in each of the Table 14-1 OLT/ONU low-power states, respectively
5.2 Defects This clause captures the required actions that are performed in the TC layer, as opposed to those left to the discretion of an implementer. 5.2.1 Items detected at OLT: The following conformance parameters are described in this clause
Annexure to ERs – Page 67 List-2(XGPON)
Sl No Reference in Parameter Value/ Reference G.987.3 1. Loss of burst for ONU i 14.2.1 Meet the 2. Loss of signal 14.2.1 requirement of 14.2.1 3. Transmission interference 14.2.1 warning for ONU i 4. Start-up failure of ONU i 14.2.1 5. Disable failure of ONU i. 14.2.1 6. Loss of PLOAM channel with 14.2.1 ONU i 7. Loss of OMCI channel with ONU 14.2.1 i
5.2.2 Items detected at ONU The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.987.3 1 Loss of downstream synchro- 14.2.2 nization.
6.0 DBA This clause recommends several DBA performance criteria that allow to evaluate a practical DBA implementation. The following conformance parameters are described in this clause
Sl No Reference in Value/Comment Parameter G.987.3 1. Stationary bandwidth assignment 7.4.1 Meet the requirement of 7.4.1 2. Assured bandwidth restoration time 7.4.2 Meet the requirement of 7.4.2 3. DBA convergence time 7.4.3 Meet the requirement of 7.4.3
Annexure to ERs – Page 68 List-3(XGS-PON)
List-3(XGS-PON)
Clause in Sl No Parameter standard 1 Transmission Convergence Layer Structure 1.0 2 OAM, PLOAM and OMCI Implementation 2.0 3 ONU Activation 3.0 4 Security 4.0 5 Network degradation check 5.0 6 DBA 6.0
1.0 Transmission Convergence Layer Structure The XGS-PON TC layer is composed of three sublayers: the XGS-PON TC service adaptation sublayer, the XGS-PON TC framing sublayer and the XGS-PON TC PHY adaptation sublayer. The following conformance parameters are described in this clause
1.1 XGS PON TC framing sublayer structure This clause specifies the structure of the downstream XGS TC frame and upstream XGS TC burst along with the format of the downstream XGS TC frame header, upstream XGSTC burst header, and upstream XGS TC burst trailer. 1.1.1 Downstream XGS-PON TC framing The following conformance parameters are described in this clause
Annexure to ERs – Page 69 List-3(XGS-PON)
Sl Parameter Reference Value/Comment No in G.9807.1 11. HLend structure C.8.1.1.1 Meet the requirement of C.8.1.1.1 12. BWmap partition C.8.1.1.2 Meet the requirement of C.8.1.1.2 13. Alloc-ID field C.8.1.1.2.1 Meet the requirement of C.8.1.1.2.1 14. Flags field C.8.1.1.2.2 Meet the requirement of C.8.1.1.2.2 15. StartTime field C.8.1.1.2.3 Meet the requirement of C.8.1.1.2.3 16. GrantSize field C.8.1.1.2.4 Meet the requirement of C.8.1.1.2.4 17. Forced wake-up C.8.1.1.2.5 Meet the indication (FWI) bit requirement of C.8.1.1.2.5 18. BurstProfile field C.8.1.1.2.6 Meet the requirement of C.8.1.1.2.6 19. HEC field C.8.1.1.2.7 Meet the requirement of C.8.1.1.2.7 20. PLOAMd partition C.8.1.1.4 Meet the requirement of C.8.1.1.4 21. FS frame trailer C.8.1.1.5 Meet the requirement of C.8.1.1.5
1.1.2 Upstream XGS-PON TC framing
Annexure to ERs – Page 70 List-3(XGS-PON)
The following conformance parameters are described in this clause Sl No Parameter Reference in Value/Comment G.9807.1 1. Upstream FS header C.8.1.2.1 Meet the requirement of C.8.1.2.1 2. ONU-ID field C.8.1.2.1.1 Meet the requirement of C.8.1.2.1.1 3. Ind field C.8.1.2.1.2 Meet the requirement of C.8.1.2.1.2 4. HEC field C.8.1.2.1.3 Meet the requirement of C.8.1.2.1.3 5. Upstream PLOAM C.8.1.2.1.4 Meet the (PLOAMu) field requirement of C.8.1.2.1.4 6. Allocation overhead C.8.1.2.2 Meet the requirement of C.8.1.2.2 7. BufOcc field C.8.1.2.2.1 Meet the requirement of C.8.1.2.2.1 8. CRC field C.8.1.2.2.3 Meet the requirement of C.8.1.2.2.3 9. Upstream FS burst trailer C.8.1.2.3 Meet the requirement of C.8.1.2.3
1.2 XGS-PON TC service adaptation sublayer -XGEM structure: The following conformance parameters are described in this clause Sl No Parameter Reference in Value/Comment G.9807.1 11. XGEM framing C.9.1 Meet the requirement of C.9.1
Annexure to ERs – Page 71 List-3(XGS-PON)
12. FS payload structure C.9.1.1 Meet the requirement of C.9.1.1 13. XGEM frame header C.9.1.2 Meet the requirement of C.9.1.2 14. XGEM payload format C.9.1.3 Meet the requirement of C.9.1.3 15. Idle XGEM frame C.9.1.4 Meet the requirement of C.9.1.4 16. XGEM frame delineation C.9.2 Meet the requirement of C.9.2 17. SDU fragmentation C.9.3 Meet the requirement of C.9.3 18. Mapping of services into C.9.4 Meet the XGEM frames requirement of C.9.4 19. Ethernet over XGEM C.9.4.1 Meet the requirement of C.9.4.1 20. MPLS over XGEM C.9.4.2 Meet the requirement of C.9.4.2
1.3 XGS-PON TC PHY adaptation sublayer structure: This clause discusses structure of physical synchronization and delineation, forward error correction, and scrambling for the downstream and upstream transmission in XGS- PON. The following conformance parameters are described in this clause Sl No Parameter Reference in Value/Comment G.9807.1 20. Downstream PHY frame C.10.1.1 Meet the requirement of C.10.1.1 21. Downstream physical C.10.1.1.1 Meet the
Annexure to ERs – Page 72 List-3(XGS-PON)
synchronization block requirement of (PSBd) C.10.1.1.1 22. Physical synchronization C.10.1.1.1.1 Meet the sequence (PSync) requirement of C.10.1.1.1.1 23. Superframe counter C.10.1.1.1.2 Meet the structure requirement of C.10.1.1.1.2 24. Operation control C.10.1.1.1.3 Meet the structure requirement of C.10.1.1.1.3 25. PSBd field scrambling C.10.1.1.2 Meet the requirement of C.10.1.1.2 26. ONU downstream C.10.1.1.3 Meet the synchronization requirement of C.10.1.1.3 27. Downstream PHY frame C.10.1.1.4 Meet the payload requirement of C.10.1.1.4 28. Upstream PHY frames C.10.1.2 Meet the and upstream PHY bursts requirement of C.10.1.2 29. Upstream physical C.10.1.2.1 Meet the synchronization block requirement of (PSBu) C.10.1.2.1 30. Upstream PHY burst C.10.1.2.2 Meet the payload requirement of C.10.1.2.2 31. Guard time C.10.1.2.3 Meet the requirement of C.10.1.2.3 32. Forward error correction C.10.1.3 Meet the requirement of C.10.1.3 33. Downstream FEC C.10.1.3.1 Meet the requirement of C.10.1.3.1
Annexure to ERs – Page 73 List-3(XGS-PON)
34. Upstream FEC C.10.1.3.2 Meet the requirement of C.10.1.3.2 35. Scrambling C.10.1.4 Meet the requirement of C.10.1.4 36. Scrambling of the C.10.1.4.1 Meet the downstream PHY frame requirement of C.10.1.4.1 37. Scrambling of the C.10.1.4.2 Meet the upstream PHY burst requirement of C.10.1.4.2
2.0 OAM, PLOAM and OMCI Implementation The control, operation, and management information in an XGS-PON system is carried over three channels: embedded OAM, PLOAM and OMCI. The embedded OAM and PLOAM channels manage the functions of the PMD and XGTC layers. OMCI provides a uniform system for managing higher (service-defining) layers.
2.1 PLOAM message format: The PLOAM message structure with each field being further defined in the following sub-clauses 2.1.1 Downstream message formats: The following conformance parameters are described in this clause
Annexure to ERs – Page 74 List-3(XGS-PON)
Sl Parameter Reference Value/Comment No in G.9807.1 11. Burst_Profile message C.11.3.3.1 Meet the requirement of C.11.3.3.1 12. Assign_ONU-ID message C.11.3.3.2 Meet the requirement of C.11.3.3.2 13. Ranging_Time message C.11.3.3.3 Meet the requirement of C.11.3.3.3 14. Deactivate_ONU-ID message C.11.3.3.4 Meet the requirement of C.11.3.3.4 15. Disable_Serial_Number message C.11.3.3.5 Meet the requirement of C.11.3.3.5 16. Request_Registration message C.11.3.3.6 Meet the requirement of C.11.3.3.6 17. Assign_Alloc-ID message C.11.3.3.7 Meet the requirement of C.11.3.3.7 18. Key_Control message C.11.3.3.8 Meet the requirement of C.11.3.3.8 19. Sleep_Allow message C.11.3.3.9 Meet the requirement of C.11.3.3.9
2.1.2 Upstream message formats: The following conformance parameters are described in this clause
Annexure to ERs – Page 75 List-3(XGS-PON)
Sl Parameter Reference Value/Comment No in G.9807.1 6. Serial_Number_ONU message C.11.3.4.1 Meet the requirement of C.11.3.4.1 7. Registration message C.11.3.4.2 Meet the requirement of C.11.3.4.2 8. Key_Report message C.11.3.4.3 Meet the requirement of C.11.3.4.3 9. Acknowledgement message C.11.3.4.4 Meet the requirement of C.11.3.4.4 10. Sleep_Request message C.11.3.4.5 Meet the requirement of C.11.3.4.5
2.2 OMCI specification The OMCI is used by the OLT to control an ONT. This protocol allows the OLT to: a) establish and release connections across the ONT; b) manage the UNIs at the ONT; c) request configuration information and performance statistics; d) autonomously inform the system operator of events such as link failures.
The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.988 19. Configuration management 7.1 Meet the requirement of 7.1 20. fault management 7.2 Meet the requirement of 7.2 21. performance management 7.3 Meet the requirement of 7.3
Annexure to ERs – Page 76 List-3(XGS-PON)
22. security management 7.4 Meet the requirement of 7.4 2.2.1 Protocol-independent MIB for the OMCI This Recommendation defines a protocol necessary to support capabilities identified by [ITU-T G.9807.1].
The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.988 5. Managed entities 8.1 Meet the requirement of 8.1 6. Managed entity relation diagrams 8.2 Meet the requirement of 8.2
3.0 ONU activation The term "activation process" refers to the set of distributed procedures allowing an inactive ONU to join or resume operations on the PON. The activation process includes three phases: synchronization, serial number acquisition, and ranging. The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.9807.1 25. Power up Table C.12.4 Meet the requirement of Table C.12.4 26. Downstream synchronization Table C.12.4 Meet the requirement of attained Table C.12.4 DSYNC 27. Loss of downstream Table C.12.4 Meet the requirement of synchronization LODS Table C.12.4 28. Initial Profile Acquired Table C.12.4 Meet the requirement of Table C.12.4 29. Timer TO1 expires Table C.12.4 Meet the requirement of Table C.12.4 30. Timer TO2 expires Table C.12.4 Meet the requirement of Table C.12.4 31. SN grant Table C.12.4 Meet the requirement of Table C.12.4 32. Directed PLOAM grant Table C.12.4 Meet the requirement of Table C.12.4
Annexure to ERs – Page 77 List-3(XGS-PON)
33. Data grant Table C.12.4 Meet the requirement of Table C.12.4 34. ONU-ID assignment Table C.12.4 Meet the requirement of Table C.12.4 35. EqD assignment Table C.12.4 Meet the requirement of Table C.12.4 36. Directed deactivate Table C.12.4 Meet the requirement of Table C.12.4 37. ONU-ID request Table C.12.4 Meet the requirement of Table C.12.4 38. Broadcast deactivate Table C.12.4 Meet the requirement of Table C.12.4 39. Enable SN request Table C.12.4 Meet the requirement of Table C.12.4 40. Burst_Profile Table C.12.4 Meet the requirement of Table C.12.4 41. Ranging_Time (relative Table C.12.4 Meet the requirement of adjustment) Table C.12.4 42. Request_Registration Table C.12.4 Meet the requirement of Table C.12.4 43. Assign_Alloc-ID Table C.12.4 Meet the requirement of Table C.12.4 44. Key_Control Table C.12.4 Meet the requirement of Table C.12.4 45. Sleep_Allow Table C.12.4 Meet the requirement of Table C.12.4
3.1 OLT and ONU timing relationships The following conformance parameters are described in this clause
Annexure to ERs – Page 78 List-3(XGS-PON)
Sl No Reference in Parameter Value/ Reference G.9807.1 4. Timing of ONU upstream C.13.1.1 Meet the requirement of transmissions C.13.1.1 5. Timing relationships and quiet C.13.1.2 Meet the requirement of window during serial number C.13.1.2 acquisition 6. Timing relationships and quiet C.13.1.3 Meet the requirement of window during ranging C.13.1.3
4.0 Security This clause discusses threat models characteristic for the XGS-PON operating environment, and specifies authentication, data integrity, and privacy protection aspects of the system. XGS-PON security is intended to protect against the following threats: • Since downstream data is broadcast to all ONUs attached to the OLT, a malicious user capable of replacing or re-programming an ONU would be capable of receiving all downstream data intended for all connected users. • Since upstream data received by the OLT can originate from any ONU attached to the XGS-PON optical distribution network (ODN), a malicious user capable of replacing or re-programming an ONU could forge packets so as to impersonate a different ONU (i.e., theft of service). • An attacker could connect a malicious device at various points on the infrastructure (e.g., by tampering with street cabinets, spare ports or fibre cables). Such a device could intercept and/or generate traffic. Depending on the location of such a device, it could impersonate an OLT or alternatively it could impersonate an ONU. • A malicious user in any of the above scenarios could record packets transmitted on the PON and replay them back onto the PON later, or conduct bit-flipping attacks.
The following conformance parameters are described in this clause
Annexure to ERs – Page 79 List-3(XGS-PON)
Sl No Reference in Parameter Value/ Reference G.9807.1 10. Threat model C.15.1 Meet the requirement of C.15.1 11. Authentication C.15.2 Meet the requirement of C.15.2 12. Key derivation C.15.3 Meet the requirement of C.15.3 13. XGEM payload encryption C.15.4 Meet the requirement of system C.15.4 14. Data encryption key exchange and C.15.5 Meet the requirement of activation mechanism C.15.5 15. Integrity protection and data C.15.6 Meet the requirement of origin verification for PLOAM C.15.6 16. Integrity protection and data C.15.7 Meet the requirement of origin verification for OMCI C.15.7 17. Integrity and data origin C.15.8 Meet the requirement of verification key switching C.15.8 18. XGS-PON systems with reduced C.15.9 Meet the requirement of data encryption strength C.15.9
5.0 Network degradation check Following parameters encompasses mechanisms to check that any telecom equipment does not degrade performance of existing network to which it is connected.This clause focuses on mechanisms to detect link failure and monitor the health and performance of links. 5.1 Monitoring The following conformance parameters are described in this clause
Sl No Reference in Parameter Value/ Reference G.9807.1 1. PHY PM Table C.14.1 Meet the requirement of 2. Corrected FEC bytes Table C.14.1 Table C.14.1 3. Corrected FEC codewords Table C.14.1 4. Uncorrectable FEC codewords Table C.14.1
Annexure to ERs – Page 80 List-3(XGS-PON)
5. Total FEC codewords Table C.14.1
6. Total received words protected by Table C.14.1 BIP-32 7. BIP-32 error count Table C.14.1 8. PSBd HEC error count Table C.14.1 9. FS HEC error count Table C.14.1 10. Unknown profile count Table C.14.1 11. LODS PM Table C.14.1 12. Total number of LODS events Table C.14.1 13. LODS events restored Table C.14.1 14. LODS events resulting in ONU Table C.14.1 reactivation without synchronization being reacquired 15. XGEM PM Table C.14.1 16. Transmitted XGEM frames Table C.14.1 17. Transmitted XGEM frames per Table C.14.1 XGEM port 18. Received XGEM frames Table C.14.1 19. Received XGEM frames per Table C.14.1 XGEM port 20. Count of the number of Table C.14.1 transmitted XGEM frames with LF bit NOT set 21. Count of XGEM frame header Table C.14.1 HEC errors 22. Count of FS frame words lost due Table C.14.1 to XGEM frame HEC error.
23. XGEM key error count Table C.14.1
24. UTILIZATION PM Table C.14.1 25. Transmitted bytes in non-idle Table C.14.1 XGEM frames
Annexure to ERs – Page 81 List-3(XGS-PON)
26. Received bytes in non-idle Table C.14.1 XGEM frames 27. Count of DBA inability to assign Table C.14.1 guaranteed bandwidth in the presence of demand 28. PLOAM PM Table C.14.1 29. SN grant count Table C.14.1 30. PLOAM MIC errors Table C.14.1 31. PLOAM timeouts Table C.14.1 32. DG count Table C.14.1 33. Downstream PLOAM message Table C.14.1 count
34. Burst_Profile Table C.14.1 message count 35. Assign_ONU-ID Table C.14.1 message count 36. Ranging_Time Table C.14.1 message count 37. Deactivate_ONU-ID Table C.14.1 message count 38. Disable Table C.14.1 _Serial_Number message count 39. Request_Registration Table C.14.1 message count 40. Assign_Alloc-ID Table C.14.1 message count 41. Key_Control Table C.14.1 message count 42. Sleep_Allow Table C.14.1 message count 43. Upstream PLOAM message count Table C.14.1 44. Serial_Number_ONU Table C.14.1 message count 45. Registration Table C.14.1 message count
Annexure to ERs – Page 82 List-3(XGS-PON)
46. Key_Report Table C.14.1 message count 47. Acknowledgement Table C.14.1 message count 48. Sleep_Request Table C.14.1 message count 49. Activation PM Table C.14.1 50. Non-discernible activation Table C.14.1 attempts 51. Table C.14.1 52. Foreign activation attempts Table C.14.1 53. Successful new activations Table C.14.1 54. OMCI PM Table C.14.1 55. OMCI baseline message count Table C.14.1 56. OMCI extended message count Table C.14.1 57. Autonomous messages Table C.14.1 58. OMCI MIC errors Table C.14.1 59. Power monitoring Table C.14.1 60. Transmit Optical power level Table C.14.1 61. Energy conservation Table C.14.1 62. Time spent in each of the OLT Table C.14.1 /ONU low-power states, respectively
5.2 Defects This clause captures the required actions that are performed in the TC layer, as opposed to those left to the discretion of an implementer. 5.2.1 Items detected at OLT: The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.9807.1 8. Loss of burst for ONUi C.14.2 Meet the requirement of 9. Loss of signal C.14.2 C.14.2 10. Transmission interference C.14.2 warning for ONU i 11. Start-up failure of ONUi. C.14.2
Annexure to ERs – Page 83 List-3(XGS-PON)
12. Disable failure of ONUi. C.14.2 13. Loss of PLOAM channel with C.14.2 ONUi. 14. Loss of OMCC channel with C.14.2 ONUi
5.2.2 Items detected at ONU The following conformance parameters are described in this clause Sl No Reference in Parameter Value/ Reference G.9807.1 1 Loss of downstream synchro- C.14.3 Meet the requirement of nization. C.14.3
6.0 DBA This clause recommends several DBA performance criteria that allow to evaluate a practical DBA implementation. The following conformance parameters are described in this clause
Sl No Reference in Value/Comment Parameter G.9807.1 4. Stationary bandwidth assignment C.7.4.1 Meet the requirement of C.7.4.1 5. Assured bandwidth restoration C.7.4.2 Meet the requirement of time C.7.4.2 6. DBA convergence time C.7.4.3 Meet the requirement of C.7.4.3
Annexure to ERs – Page 84 List-4 (NGPON2)
List 4 for NGPON2 Sl No Clause in Parameter standard 1 Transmission Convergence Layer Structure 1.0 2 OAM, PLOAM and OMCI Implementation 2.0 3 ONU activation 3.0 4 Security 4.0 5 Network degradation check 5.0 6 DBA 6.0
1.0 NG-PON2 transmission convergence layer structure A NG-PON2 system may contain a set of TWDM channels, a set of PtP WDM channels or both. The TWDM channels use a TC layer defined in clause 1.1-1.3. The PtP WDM channels use a TC layer described in clause 1.4-1.6. 1.1 TWDM TC service adaptation sublayer structure In a TWDM PON system, the SDUs, which include the user data frames and high-level PON management frames (OMCI), are transmitted in the FS payload sections of the downstream FS frames and upstream FS bursts using the XG-PON encapsulation method (XGEM). This clause specifies the structure of the FS payload section, the format of the XGEM frame header and payload, the XGEM frame delineation principles, as well as the mapping of different service types into XGEM frames. The following conformance parameters are described in this clause
Annexure to ERs – Page 85 List-4 (NGPON2)
Sl No Reference Parameter Value/ Reference in G.989.3 1. XGEM framing 9.1 Meet the requirement of 9.1 2. FS payload structure 9.1.1 Meet the requirement of 9.1.1 3. XGEM frame header 9.1.2 Meet the requirement of 9.1.2 4. XGEM payload format 9.1.3 Meet the requirement of 9.1.3 5. Idle XGEM frame 9.1.4 Meet the requirement of 9.1.4 6. XGEM frame delineation 9.2 Meet the requirement of 9.2 7. SDU fragmentation 9.3 Meet the requirement of 9.3 8. Mapping of services into XGEM 9.4 Meet the requirement of 9.4 frames 9. Ethernet over XGEM 9.4.1 Meet the requirement of 9.4.1 10. MPLS over XGEM 9.4.2 Meet the requirement of 9.4.2
1.2 TWDM TC framing sublayer structure This clause specifies the structure of the downstream FS frame and upstream FS burst along with the format of the downstream FS frame header, downstream FS frame trailer, upstream FS burst header and upstream FS burst trailer. The following conformance parameters are described in this clause
Sl No Reference Parameter Value/Comment in G.989.3 Downstream TWDM TC framing 8.1.1 Meet the requirement of 1. 8.1.1 Upstream TWDM TC framing 8.1.2 Meet the requirement of 2. 8.1.2
1.3 TWDM TC PHY adaptation sublayer structure This clause discusses matters of physical synchronization and delineation, forward error correction, and scrambling for the downstream and upstream transmission in TWDM PON. The following conformance parameters are described in this clause
Annexure to ERs – Page 86 List-4 (NGPON2)
Sl Reference No Parameter in Value/Comment G.989.3 1. Downstream PHY 10.1.1 Meet the frame requirement of 10.1.1 2. Downstream physical 10.1.1.1 Meet the synchronization block requirement of (PSBd) 10.1.1.1 3. PSBd field scrambling 10.1.1.2 Meet the requirement of 10.1.1.2 4. ONU downstream 10.1.1.3 Meet the synchronization requirement of 10.1.1.3 5. Downstream PHY 10.1.1.4 Meet the frame payload requirement of 10.1.1.4 6. Upstream PHY frames 10.1.2 Meet the and upstream PHY requirement of bursts 10.1.2 7. Upstream physical 10.1.2.1 Meet the synchronization block requirement of (PSBu) 10.1.2.1 8. Upstream PHY burst 10.1.2.2 Meet the payload requirement of 10.1.2.2 9. Guard time 10.1.2.3 Meet the requirement of 10.1.2.3 10. Forward error 10.1.3 Meet the correction requirement of 10.1.3 11. Downstream FEC 10.1.3.1 Meet the requirement of 10.1.3.1 12. Downstream FEC 10.1.3.1.1 Meet the codeword requirement of
Annexure to ERs – Page 87 List-4 (NGPON2)
10.1.3.1.1 13. Downstream FEC 10.1.3.1.2 Meet the on/off control requirement of 10.1.3.1.2 14. Upstream FEC 10.1.3.2 Meet the requirement of 10.1.3.2 15. Upstream FEC 10.1.3.2.1 Meet the codeword requirement of 10.1.3.2.1 16. Shortened last 10.1.3.2.2 Meet the codeword requirement of 10.1.3.2.2 17. BWmap considerations 10.1.3.2.3 Meet the requirement of 10.1.3.2.3 18. Upstream FEC on/off 10.1.3.2.4 Meet the control requirement of 10.1.3.2.4 19. Scrambling 10.1.4 Meet the requirement of 10.1.4 20. Scrambling of the 10.1.4.1 Meet the downstream PHY requirement of frame 10.1.4.1 21. Scrambling of the 10.1.4.2 Meet the upstream PHY burst requirement of 10.1.4.2
1.4 PtP WDM AMCC TC management service adaptation sublayer structure The AMCC TC management service adaptation sublayer is responsible for the upper layer MDU encapsulation, multiplexing and delineation in the course of transmission over PtP WDM. The following conformance parameters are described in this clause
Annexure to ERs – Page 88 List-4 (NGPON2)
Sl No Reference Parameter Value/ Reference in G.989.3 1. XGEM framing 9.1 Meet the requirement of 9.1 2. FS payload structure 9.1.1 Meet the requirement of 9.1.1 3. XGEM frame header 9.1.2 Meet the requirement of 9.1.2 4. XGEM payload format 9.1.3 Meet the requirement of 9.1.3 5. Idle XGEM frame 9.1.4 Meet the requirement of 9.1.4 6. XGEM frame delineation 9.2 Meet the requirement of 9.2 7. SDU fragmentation 9.3 Meet the requirement of 9.3
1.5 PtP WDM TC framing sublayer structure The AMCC TC management framing sublayer is responsible for the construction and parsing of the overhead fields that support the necessary PON management functionality. The following conformance parameters are described in this clause
Sl No Reference in Parameter Value/Comment G.989.3 1. PLOAM count 8.2.1 Meet the requirement of 8.2.1 2. Payload length 8.2.2 Meet the requirement of 8.2.2 3. SFC offset 8.2.3 Meet the requirement of 8.2.3 4. Ind field 8.2.4 Meet the requirement of 8.2.4 5. HEC field 8.2.5 Meet the requirement of 8.2.5 6. PLOAM partition 8.2.6 Meet the requirement of 8.2.6 7. PtP WDM management frame 8.2.7 Meet the requirement of trailer 8.2.7
1.6 PtP WDM TC PHY adaptation sublayer structure This clause discusses matters of physical synchronization and delineation, forward error correction and transcoding for the transmission at the PtP WDM management PHY Annexure to ERs – Page 89 List-4 (NGPON2)
adaptation sublayer. The following conformance parameters are described in this clause
Sl Reference No Parameter in Value/ Reference G.989.3 1. PtP WDM management 10.2.1 Meet the PHY frame requirement of 10.2.1 2. Physical 10.2.1.1 Meet the synchronization block requirement of (PSB) 10.2.1.1 3. Superframe counter 10.2.1.1.1 Meet the structure requirement of 10.2.1.1.1 4. Operation control 10.2.1.1.2 Meet the structure requirement of 10.2.1.1.2 5. AMCC frame 10.2.1.2 Meet the synchronization requirement of 10.2.1.2 6. Forward error correction 10.2.2 Meet the requirement of 10.2.2 7. Transcoding 10.2.3 Meet the requirement of 10.2.3
2.0 OAM, PLOAM and OMCI Implementation The ONU control, operation and management information in a NG PON2 system is carried over three channels: embedded OAM, PLOAM and OMCC. To set up PON-link between the OLT and the ONU, parameters in this clause shall be complied with. 2.1 Downstream PLOAM structure The PLOAM channel supports the following NG-PON2 TC layer management functions: – Profile announcement; – ONU activation; – ONU registration;
Annexure to ERs – Page 90 List-4 (NGPON2)
– Encryption key update exchange; – Protection switching signalling; – Power management; – ONU wavelength channel handover signalling. The following conformance parameters are described in this clause
Reference Sl No Message name Value/ Reference in G.989.3 1 Burst_Profile(Specific message 11.3.1 Meet the requirement of format) 11.3.1 2 Assign_ONU-ID(Invariant) 11.3.1 Meet the requirement of 11.3.1 3 Ranging_Time(TWDM only) 11.3.1 Meet the requirement of 11.3.1 4 Deactivate_ ONU-ID(Invariant) 11.3.1 Meet the requirement of 11.3.1 5 Disable_Serial_Number(Invariant) 11.3.1 Meet the requirement of 11.3.1 6 Request_Registration(TWDM only) 11.3.1 Meet the requirement of 11.3.1 7 Assign_Alloc-ID(TWDM only) 11.3.1 Meet the requirement of 11.3.1 8 Key_Control(Invariant) 11.3.1 Meet the requirement of 11.3.1 9 Sleep_Allow(TWDM only) 11.3.1 Meet the requirement of 11.3.1 10 Calibration_ Request(Invariant) 11.3.1 Meet the requirement of 11.3.1 11 Adjust_ Tx_Wavelength(Invariant) 11.3.1 Meet the requirement of 11.3.1 12 Tuning_Control(Invariant) 11.3.1 Meet the requirement of 11.3.1 13 System_Profile(Invariant) 11.3.1 Meet the requirement of 11.3.1
Annexure to ERs – Page 91 List-4 (NGPON2)
14 Channel_Profile(Specific message 11.3.1 Meet the requirement of format) 11.3.1 15 Protection_Control(Invariant) 11.3.1 Meet the requirement of 11.3.1 16 Change_Power _Level (Invariant) 11.3.1 Meet the requirement of 11.3.1 17 Power _Consumption _Inquire 11.3.1 Meet the requirement of (TWDM only) 11.3.1 18 Rate_Control (PtP WDM only) 11.3.1 Meet the requirement of 11.3.1
2.2 Upstream PLOAM structure The following conformance parameters are described in this clause
Reference Sl No Message name Value/ Reference in G.989.3 1 Serial_Number_ ONU 11.3.2 Meet the requirement of (Specific field formats) 11.3.2 2 Registration (TWDM only) 11.3.2 Meet the requirement of 11.3.2 3 Key_Report (Invariant) 11.3.2 Meet the requirement of 11.3.2 3 Acknowledgement (Invariant) 11.3.2 Meet the requirement of 11.3.2 4 Sleep_Request (TWDM only) 11.3.2 Meet the requirement of 11.3.2 5 Tuning_Response (Specific field 11.3.2 Meet the requirement of formats) 11.3.2 6 Power _Consumption _Report 11.3.2 Meet the requirement of (TWDM only) 11.3.2 7 Rate_Response (PtP WDM only) 11.3.2 Meet the requirement of 11.3.2
2.3 OMCI specification The OMCI is used by the OLT to control an ONT. This protocol allows the OLT to:
Annexure to ERs – Page 92 List-4 (NGPON2)
a) establish and release connections across the ONT; b) manage the UNIs at the ONT; c) request configuration information and performance statistics; d) autonomously inform the system operator of events such as link failures. The following conformance parameters are described in this clause
Sl No Reference Parameter Value/ Reference in G.988 23. Configuration management 7.1 Meet the requirement of 7.1 24. fault management 7.2 Meet the requirement of 7.2 25. performance management 7.3 Meet the requirement of 7.3 26. security management 7.4 Meet the requirement of 7.4 2.3.1 Protocol-independent MIB for the OMCI This Recommendation defines a protocol necessary to support capabilities identified by [ITU-T G.989.2] and [ITU-T G.989.3].
The following conformance parameters are described in this clause Sl No Reference Parameter Value/ Reference in G.988 7. Managed entities Meet the Meet the requirement of 8.1 requirement of 8.1 8. Managed entity relation diagrams 8.2 Meet the requirement of 8.2
3.0 ONU activation The activation proper includes three phases: downstream synchronization, serial number acquisition (ONU discovery), and ranging. 3.1 TWDM PON ONU activation cycle This clause specifies the TC layer behaviour of a TWDM PON ONU using a state machine. As a matter of convenience, the ONU activation cycle state machine can be partitioned into two blocks: (1) activation proper, and (2) operation and tuning. The following conformance parameters are described in this clause
Sl No Parameters Reference Value/ References Annexure to ERs – Page 93 List-4 (NGPON2)
in G.989.3 ONU activation cycle states Table 12-1 Meet the requirement of 1. Table 12-1 Initial state 12.1.4 Meet the requirement of 2. 12.1.4 O1/Off-Sync O1.1 12.1.4 Meet the requirement of 3. 12.1.4 O1/Profile Learning O1.2 12.1.4 Meet the requirement of 4. 12.1.4 Serial Number state 12.1.4 Meet the requirement of 5. 12.1.4 Ranging state 12.1.4 Meet the requirement of 6. 12.1.4 Operation state 12.1.4 Meet the requirement of 7. 12.1.4 O5/Associated O5.1 12.1.4 Meet the requirement of 8. 12.1.4 O5/Pending O5.2 12.1.4 Meet the requirement of 9. 12.1.4 Intermittent LODS state 12.1.4 Meet the requirement of 10. 12.1.4 Emergency Stop state 12.1.4 Meet the requirement of 11. 12.1.4 Downstream Tuning state 12.1.4 Meet the requirement of 12. 12.1.4 O8/Off-Sync O8.1 12.1.4 Meet the requirement of 13. 12.1.4 O8/Profile Learning O8.2 12.1.4 Meet the requirement of 14. 12.1.4 Upstream Tuning state 12.1.4 Meet the requirement of 15. 12.1.4 ONU activation cycle state Table 12-2 Meet the requirement of 16. machine timers Table 12-2 Discovery timer 12.1.4 Meet the requirement of 17. 12.1.4
Annexure to ERs – Page 94 List-4 (NGPON2)
Ranging timer 12.1.4 Meet the requirement of 18. 12.1.4 Loss of downstream 12.1.4 Meet the requirement of 19. synchronization (LODS) timer. 12.1.4 LODS protection timer 12.1.4 Meet the requirement of 20. 12.1.4 Downstream tuning timer 12.1.4 Meet the requirement of 21. 12.1.4 Upstream tuning timer 12.1.4 Meet the requirement of 22. 12.1.4 ONU activation cycle state Table 12-3 Meet the requirement of 23. machine inputs Table 12-3 DSYNC 12.1.4 Meet the requirement of 24. 12.1.4 LODS 12.1.4 Meet the requirement of 25. 12.1.4 SFC match 12.1.4 Meet the requirement of 26. 12.1.4 DWLCH ok to work 12.1.4 Meet the requirement of 27. 12.1.4 DWLCH not appropriate 12.1.4 Meet the requirement of 28. 12.1.4 TOZ expires 12.1.4 Meet the requirement of 29. 12.1.4 TO1 expires 12.1.4 Meet the requirement of 30. 12.1.4 TO2 expires 12.1.4 Meet the requirement of 31. 12.1.4 TO3 expires 12.1.4 Meet the requirement of 32. 12.1.4 TO4 expires 12.1.4 Meet the requirement of 33. 12.1.4 TO5 expires 12.1.4 Meet the requirement of 34. 12.1.4 SN grant 12.1.4 Meet the requirement of 35. Annexure to ERs – Page 95 List-4 (NGPON2)
12.1.4 Directed PLOAM grant 12.1.4 Meet the requirement of 36. 12.1.4 Data grant 12.1.4 Meet the requirement of 37. 12.1.4 ONU-ID Assignment 12.1.4 Meet the requirement of 38. 12.1.4 EqD Assignment 12.1.4 Meet the requirement of 39. 12.1.4 Deactivate ONU-ID request 12.1.4 Meet the requirement of 40. 12.1.4 Disable SN request 12.1.4 Meet the requirement of 41. 12.1.4 Enable SN request 12.1.4 Meet the requirement of 42. 12.1.4 Calibration request 12.1.4 Meet the requirement of 43. 12.1.4 Tuning request 12.1.4 Meet the requirement of 44. 12.1.4 US Tuning confirmation 12.1.4 Meet the requirement of 45. 12.1.4 System_Profile 12.1.4 Meet the requirement of 46. 12.1.4 Channel_Profile 12.1.4 Meet the requirement of 47. 12.1.4 Burst_Profile 12.1.4 Meet the requirement of 48. 12.1.4 Ranging_Time 12.1.4 Meet the requirement of 49. (relative adjustment) 12.1.4 Request_Registration 12.1.4 Meet the requirement of 50. 12.1.4 Assign_Alloc-ID 12.1.4 Meet the requirement of 51. 12.1.4 Key_Control 12.1.4 Meet the requirement of 52. 12.1.4
Annexure to ERs – Page 96 List-4 (NGPON2)
Sleep_Allow 12.1.4 Meet the requirement of 53. 12.1.4 Adust_Tx_Wavelength 12.1.4 Meet the requirement of 54. 12.1.4 Protection_Control 12.1.4 Meet the requirement of 55. 12.1.4 OLT support of the TWDM ONU 12.1.5 Meet the requirement of 56. activation 12.1.5 ONU power levelling 12.1.6 Meet the requirement of 57. 12.1.6
3.2 PtP WDM ONU activation cycle state machine The following conformance parameters are described in this clause
Sl No Parameters Reference in G.989.3 1. ONU activation cycle states 12.2.2 Meet the requirement of 12.2.2 2. Initial state 12.2.2 Meet the requirement of 12.2.2 3. O1/Off-Sync O1.1 12.2.2 Meet the requirement of 12.2.2 4. O1/Profile Learning O1.2 12.2.2 Meet the requirement of 12.2.2 5. Serial Number state 12.2.2 Meet the requirement of 12.2.2 6. Operation state 12.2.2 Meet the requirement of 12.2.2 7. Intermittent LODS state 12.2.2 Meet the requirement of 12.2.2 8. Emergency Stop state 12.2.2 Meet the requirement of 12.2.2 9. Downstream Tuning state 12.2.2 Meet the requirement of 12.2.2 10. O8/Off-Sync O8.1 12.2.2 Meet the requirement of
Annexure to ERs – Page 97 List-4 (NGPON2)
12.2.2 11. O8/Profile Learning O8.2 12.2.2 Meet the requirement of 12.2.2 12. Upstream Tuning state 12.2.2 Meet the requirement of 12.2.2 13. ONU activation cycle state 12.2.2 Meet the requirement of machine timers 12.2.2 14. Discovery timer 12.2.2 Meet the requirement of 12.2.2 15. Loss of downstream 12.2.2 Meet the requirement of synchronization (LODS) timer. 12.2.2 16. LODS Protection timer 12.2.2 Meet the requirement of 12.2.2 17. Downstream Tuning timer 12.2.2 Meet the requirement of 12.2.2 18. Upstream tuning timer 12.2.2 Meet the requirement of 12.2.2 19. ONU activation cycle state 12.2.2 Meet the requirement of machine inputs 12.2.2 20. DSYNC 12.2.2 Meet the requirement of 12.2.2 21. LODS 12.2.2 Meet the requirement of 12.2.2 22. SFC match 12.2.2 Meet the requirement of 12.2.2 23. DWLCH ok to work 12.2.2 Meet the requirement of 12.2.2 24. DWLCH not appropriate 12.2.2 Meet the requirement of 12.2.2 25. TOZ expires 12.2.2 Meet the requirement of 12.2.2 26. TO2 expires 12.2.2 Meet the requirement of 12.2.2 27. TO3 expires 12.2.2 Meet the requirement of 12.2.2
Annexure to ERs – Page 98 List-4 (NGPON2)
28. TO4 expires 12.2.2 Meet the requirement of 12.2.2 29. TO5 expires 12.2.2 Meet the requirement of 12.2.2 30. ONU-ID Assignment 12.2.2 Meet the requirement of 12.2.2 31. Deactivate ONU-ID request 12.2.2 Meet the requirement of 12.2.2 32. Disable SN request 12.2.2 Meet the requirement of 12.2.2 33. Enable SN request 12.2.2 Meet the requirement of 12.2.2 34. Tuning request 12.2.2 Meet the requirement of 12.2.2 35. US Tuning confirmation 12.2.2 Meet the requirement of 12.2.2 36. System_Profile 12.2.2 Meet the requirement of 12.2.2 37. Channel_Profile 12.2.2 Meet the requirement of 12.2.2 38. Burst_Profile 12.2.2 Meet the requirement of 12.2.2 39. Key_Control 12.2.2 Meet the requirement of 12.2.2 40. Sleep_Allow 12.2.2 Meet the requirement of 12.2.2 41. Adust_Tx_Wavelength 12.2.2 Meet the requirement of 12.2.2 42. Protection_Control 12.2.2 Meet the requirement of 12.2.2 43. Rate_Control 12.2.2 Meet the requirement of 12.2.2
3.3 NG-PON2 OLT and ONU timing relationships The following conformance parameters are described in this clause Annexure to ERs – Page 99 List-4 (NGPON2)
Sl No Parameters Reference Value/ References in G.989.3 1. Timing of ONU upstream 13.1.1 Meet the requirement of transmissions 13.1.1 2. Timing relationships and quiet 13.1.2 Meet the requirement of window during serial number 13.1.2 acquisition 3. Timing relationships and 13.1.3 Meet the requirement of quiet window during 13.1.3 ranging
4.0 Security This clause discusses threat models characteristic for the NG-PON2 operating environment, and specifies authentication, data integrity and privacy protection aspects of the system. NG-PON2 security is intended to protect against the following threats: 1) Since downstream data is broadcast to all ONUs attached to the NG-PON2 OLT CT, a malicious user capable of replacing or re-programming an ONU would be capable of receiving all downstream data intended for all connected users. 2) Since upstream data received by the OLT CT can originate from any ONU attached to the NG-PON2 optical distribution network (ODN), a malicious user capable of replacing or re-programming an ONU could forge packets so as to impersonate a different ONU (i.e., theft of service). 3) An attacker could connect a malicious device at various points on the infrastructure (e.g., by tampering with street cabinets, spare ports or fibre cables). Such a device could intercept and/or generate traffic. Depending on the location of such a device, it could impersonate an OLT CT or alternatively it could impersonate an ONU. 4) A malicious user in any of the above scenarios could record packets transmitted on the passive optical network (PON) and replay them back onto the PON later, or conduct bit-flipping attacks. The following conformance parameters are described in this clause
Annexure to ERs – Page 100 List-4 (NGPON2)
Sl No Reference Parameter Value/ References in G.989.3 4. Authentication 15.2 Meet the requirement of 15.2 5. Key derivation 15.3 Meet the requirement of 15.3 6. XGEM payload encryption 15.4 Meet the requirement of system 15.4 7. Data encryption key exchange and 15.5 Meet the requirement of activation mechanism 15.5 8. Integrity protection and data 15.6 Meet the requirement of origin verification for PLOAM 15.6 9. Integrity protection and data 15.7 Meet the requirement of origin verification for OMCI 15.7 10. Integrity and data origin 15.8 Meet the requirement of verification key switching 15.8 11. NG-PON2 systems with reduced 15.9 Meet the requirement of data encryption strength 15.9
5.0 Network degradation check Following parameters encompasses mechanisms to check that any telecom equipment does not degrade performance of existing network to which it is connected.This clause focuses on mechanisms to detect link failure and monitor the health and performance of the links. It does not cover functions that may utilize the performance monitoring information, such as station management, bandwidth allocation or provisioning. 5.1 Monitoring To facilitate troubleshooting, it is desirable that OLT channel termination and ONU maintain a variety of performance monitoring (PM) counters. The collected counter values may trigger actions ranging from threshold crossing alerts to alarms to protection switching, which are largely beyond the scope of this Recommendation. The following conformance parameters are described in this clause
Sl No. Parameter Reference Value/ References in G.989.3 1. PHY PM Meet the Meet the requirement of requireme 14.1 nt of 14.1 2. Corrected FEC bytes 14.1 Meet the requirement of 14.1
Annexure to ERs – Page 101 List-4 (NGPON2)
3. Corrected FEC codewords 14.1 Meet the requirement of 14.1 4. Uncorrectable FEC codewords 14.1 Meet the requirement of 14.1 5. Total FEC codewords 14.1 Meet the requirement of 14.1 6. Total received words protected by 14.1 Meet the requirement of BIP-32 14.1 7. BIP-32 error count 14.1 Meet the requirement of 14.1 8. PSBd HEC error count 14.1 Meet the requirement of 14.1 9. FS HEC error count 14.1 Meet the requirement of 14.1 10. Unknown profile count 14.1 Meet the requirement of 14.1 11. LODS PM 14.1 Meet the requirement of 14.1 12. Total number of LODS events 14.1 Meet the requirement of 14.1 13. LODS events restored in the 14.1 Meet the requirement of operating TWDM channel 14.1 14. LODS events restored in the pre- 14.1 Meet the requirement of configured protection TWDM 14.1 channel 15. LODS events restored in a 14.1 Meet the requirement of discretionary TWDM channel 14.1 16. LODS events resulting in ONU 14.1 Meet the requirement of reactivation without 14.1 synchronization being reacquired
Annexure to ERs – Page 102 List-4 (NGPON2)
17. LODS events resulting in ONU 14.1 Meet the requirement of reactivation after upstream 14.1 handshake failure in pre- configured TWDM channel. 18. LODS events resulting in ONU 14.1 Meet the requirement of reactivation after upstream 14.1 handshake failure in discretionary TWDM channel. 19. XGEM PM 14.1 Meet the requirement of 14.1 20. Transmitted XGEM frames 14.1 Meet the requirement of 14.1 21. Transmitted XGEM frames per 14.1 Meet the requirement of XGEM port 14.1 22. Received XGEM frames 14.1 Meet the requirement of 14.1 23. Received XGEM frames per 14.1 Meet the requirement of XGEM port 14.1 24. Count of the number of 14.1 Meet the requirement of transmitted XGEM frames with 14.1 LF bit NOT set 25. Count of XGEM frame header 14.1 Meet the requirement of HEC errors 14.1 26. Count of FS frame words lost due 14.1 Meet the requirement of to XGEM frame HEC error. 14.1 27. XGEM key error count 14.1 Meet the requirement of 14.1 28. UTILIZATION PM 14.1 Meet the requirement of 14.1 29. Transmitted bytes in non-idle 14.1 Meet the requirement of XGEM frames 14.1 30. Received bytes in non-idle 14.1 Meet the requirement of XGEM frames 14.1
Annexure to ERs – Page 103 List-4 (NGPON2)
31. Count of DBA inability to assign 14.1 Meet the requirement of guaranteed bandwidth in the 14.1 presence of demand 32. PLOAM PM 14.1 Meet the requirement of 14.1 33. SN grant count 14.1 Meet the requirement of 14.1 34. PLOAM MIC errors 14.1 Meet the requirement of 14.1 35. PLOAM timeouts 14.1 Meet the requirement of 14.1 36. DG count 14.1 Meet the requirement of 14.1 37. Downstream PLOAM message 14.1 Meet the requirement of count 14.1 38. System_Profile message count 14.1 Meet the requirement of 14.1 39. Channel_Profile message count 14.1 Meet the requirement of 14.1 40. Burst_Profile message count 14.1 Meet the requirement of 14.1 41. Assign_ONU-ID message count 14.1 Meet the requirement of 14.1 42. Ranging_Time message count 14.1 Meet the requirement of 14.1 43. Protection_Control message count 14.1 Meet the requirement of 14.1 44. Adjust_Tx_Wavelength message 14.1 Meet the requirement of count 14.1 45. Wavelength dithering 14.1 Meet the requirement of Adjust_Tx_Wavelength 14.1 message count
Annexure to ERs – Page 104 List-4 (NGPON2)
46. Adjust_Tx_Wavelength 14.1 Meet the requirement of adjustment amplitude 14.1 47. Unsatisfied 14.1 Meet the requirement of Adjust_Tx_Wavelength requests 48. Deactivate_ONU-ID message 14.1 Meet the requirement of count 14.1 49. Disable_Serial_Number message 14.1 Meet the requirement of count 14.1 50. Request_Registrationmessage 14.1 Meet the requirement of count 14.1 51. Assign_Alloc-ID message count 14.1 Meet the requirement of 14.1 52. Key_Control message count 14.1 Meet the requirement of 14.1 53. Sleep_Allow message count 14.1 Meet the requirement of 14.1 54. Tuning_Control message count, 14.1 Meet the requirement of Request operation code 14.1 55. Tuning_Control message count, 14.1 Meet the requirement of Complete_d operation code 14.1 56. Calibration_Request message 14.1 Meet the requirement of count 14.1 57. Upstream PLOAM message count 14.1 Meet the requirement of 14.1 58. Serial_Number_ONU (in- 14.1 Meet the requirement of band)message count 14.1 59. Serial_Number_ONU (AMCC) 14.1 Meet the requirement of message count 14.1 60. Registration message count 14.1 Meet the requirement of 14.1 61. Key_Report message count 14.1 Meet the requirement of 14.1
Annexure to ERs – Page 105 List-4 (NGPON2)
62. Acknowledgement message count 14.1 Meet the requirement of 14.1 63. Sleep_Request message count 14.1 Meet the requirement of 14.1 64. Tuning_Response message count, 14.1 Meet the requirement of ACK/NACK operation codes 14.1 65. Tuning_Response message count, 14.1 Meet the requirement of Complete_u/Rollback operation 14.1 codes 66. Power_Consumption _Report 14.1 Meet the requirement of message count 14.1 67. Activation PM 14.1 Meet the requirement of 14.1 68. Non-discernible activation 14.1 Meet the requirement of attempts (in-band) 14.1 69. Non-discernible activation 14.1 Meet the requirement of attempts (AMCC) 14.1 70. Foreign activation attempts (in- 14.1 Meet the requirement of band) 14.1 71. Foreign activation attempts 14.1 Meet the requirement of (AMCC) 14.1 72. Successful new activations (in- 14.1 Meet the requirement of band) 14.1 73. Successful new activations 14.1 Meet the requirement of (AMCC) 14.1 74. Successful pre-configured 14.1 Meet the requirement of TWDM channel handovers (in- 14.1 band) 75. Successful discretionary TWDM 14.1 Meet the requirement of channel handovers 14.1 (in-band)
Annexure to ERs – Page 106 List-4 (NGPON2)
76. Tuning Control PM 14.1 Meet the requirement of (for detailed failure condition 14.1 codepoint explanation see clause 17.3.2) 77. Tuning control requests for Rx 14.1 Meet the requirement of only or Rx and Tx 14.1 78. Tuning control requests for Tx 14.1 Meet the requirement of only 14.1 79. Tuning control requests rejected 14.1 Meet the requirement of on internal condition (not ready to 14.1 start transceiver tuning by specified time) 80. Tuning control requests rejected 14.1 Meet the requirement of on target downstream wavelength 14.1 channel inconsistency 81. Tuning control requests rejected 14.1 Meet the requirement of on downstream administrative 14.1 label inconsistency 82. Tuning control requests rejected 14.1 Meet the requirement of on void downstream wavelength 14.1 channel descriptor 83. Tuning control requests rejected 14.1 Meet the requirement of on channel partition violation 14.1 84. Tuning control requests rejected 14.1 Meet the requirement of due to target DS wavelength 14.1 channel being out of Rx tuning range. 85. Tuning control requests rejected 14.1 Meet the requirement of on downstream line rate 14.1 inconsistency 86. Tuning control requests rejected 14.1 Meet the requirement of on downstream line code 14.1 inconsistency
Annexure to ERs – Page 107 List-4 (NGPON2)
87. Tuning control requests rejected 14.1 Meet the requirement of on target upstream wavelength 14.1 channel inconsistency 88. Tuning control requests rejected 14.1 Meet the requirement of on upstream administrative label 14.1 inconsistency 89. Tuning control requests rejected 14.1 Meet the requirement of on void upstream wavelength 14.1 channel descriptor 90. Tuning control requests rejected 14.1 Meet the requirement of due to target US wavelength 14.1 channel being out of Tx tuning range. 91. Tuning control request rejected 14.1 Meet the requirement of due to insufficient calibration 14.1 accuracy 92. Tuning control requests rejected 14.1 Meet the requirement of on upstream optical link type 14.1 inconsistency 93. Tuning control requests rejected 14.1 Meet the requirement of on upstream line rate 14.1 inconsistency 94. Tuning control requests rejected 14.1 Meet the requirement of on upstream line code 14.1 inconsistency 95. Tuning control requests fulfilled 14.1 Meet the requirement of with ONU reacquired at target 14.1 channel 96. Tuning control requests failure 14.1 Meet the requirement of reason: target DS wavelength 14.1 channel not found.
Annexure to ERs – Page 108 List-4 (NGPON2)
97. Tuning control requests failure 14.1 Meet the requirement of reason: no tuning feedback in 14.1 target US wavelength channel. 98. Tuning control requests resolved 14.1 Meet the requirement of with ONU reacquired at 14.1 discretionary channel 99. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback due to 14.1 communication condition 100. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback due to 14.1 downstream target wavelength channel inconsistency 101. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback on 14.1 downstream administrative label inconsistency 102. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback on 14.1 downstream optical link type inconsistency 103. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback due to 14.1 upstream target wavelength channel parameter violation. 104. Tuning control requests failed 14.1 Meet the requirement of with ONU Rollback on upstream 14.1 administrative label violation 105. Tuning control requests rejected 14.1 Meet the requirement of on void upstream wavelength 14.1 channel descriptor 106. Tuning control requests rejected 14.1 Meet the requirement of on Tx tuning range violation. 14.1
Annexure to ERs – Page 109 List-4 (NGPON2)
107. Tuning control requests rejected 14.1 Meet the requirement of on upstream optical link type 14.1 violation. 108. Tuning control requests rejected 14.1 Meet the requirement of on upstream line rate violation 14.1 109. Tuning control requests rejected 14.1 Meet the requirement of on upstream line code violation 14.1 110. Tuning control requests failed 14.1 Meet the requirement of with ONU reactivation 14.1 111. Power Levelling PM 14.1 Meet the requirement of 14.1 112. Change_Power_Level messages 14.1 Meet the requirement of rejected due to Parameter Error 14.1 113. Change_Power_Level messages 14.1 Meet the requirement of without completion 14.1 acknowledgement 114. OMCI PM 14.1 Meet the requirement of 14.1 115. OMCI baseline message count 14.1 Meet the requirement of 14.1 116. OMCI extended message count 14.1 Meet the requirement of 14.1 117. Autonomous messages 14.1 Meet the requirement of 14.1 118. OMCI MIC errors 14.1 Meet the requirement of 14.1 119. Power Monitoring 14.1 Meet the requirement of 14.1 120. Transmit Optical power level 14.1 Meet the requirement of 14.1 121. Energy conservation 14.1 Meet the requirement of 14.1
Annexure to ERs – Page 110 List-4 (NGPON2)
122. Time spent in each of the OLT 14.1 Meet the requirement of CT/ONU low-power states, 14.1 respectively 5.2 Defects This clause captures the required actions that are performed in the TC layer, as opposed to those left to the discretion of an implementer. In particular, the effects of repeated defects of the same type are an implementation matter. 6.2.1 Items detected at OLT channel termination The following conformance parameters are described in this clause
Annexure to ERs – Page 111 List-4 (NGPON2)
Sl Type Description Reference Value/ No in References G.989.3
1. LOBi Loss of burst 14.2.1 Meet the for ONUi requirement of 14.2.1 2. LOS Loss of signal 14.2.1 Meet the requirement of 14.2.1 3. TIWi Transmission 14.2.1 Meet the interference requirement warning for of 14.2.1 ONU i 4. SUFi Start-up 14.2.1 Meet the failure of requirement ONUi. of 14.2.1 5. DFi Disable 14.2.1 Meet the failure of requirement ONUi. of 14.2.1 6. LOPCi Loss of 14.2.1 Meet the PLOAM requirement channel with of 14.2.1 ONUi. 7. LOOCi Loss of 14.2.1 Meet the OMCC requirement channel with of 14.2.1 ONUi 8. DOTXi Drift of 14.2.1 Meet the transmitter requirement wavelength of 14.2.1 warning 9. ALRFi Attenuation 14.2.1 Meet the level request requirement failure of 14.2.1
Annexure to ERs – Page 112 List-4 (NGPON2)
5.2.2 Items detected at ONU The following conformance parameters are described in this clause
Sl No Type Description Reference Value/ Reference in G.989.3 1 LODS Loss of downstream 14.2.2 Meet the requirement of synchro-nization. 14.2.2
6.0 DBA This clause recommends several DBA performance criteria that allow to evaluate a practical DBA implementation The following conformance parameters are described in this clause
Sl No Reference Value/Comment Parameter in G.989.3 1. Stationary bandwidth assignment 7.4.1 Meet the requirement of 7.4.1 2. Assured bandwidth restoration 7.4.2 Meet the requirement of time 7.4.2 3. DBA convergence time 7.4.3 Meet the requirement of 7.4.3
Annexure to ERs – Page 113 List-5(10G EPON)
PICS test List for 10G EPON
Annexure to ERs – Page 114 List-5(10G EPON)
Annexure to ERs – Page 115 List-5(10G EPON)
Annexure to ERs – Page 116 List-5(10G EPON)
Annexure to ERs – Page 117 List-5(10G EPON)
Annexure to ERs – Page 118 List-5(10G EPON)
Annexure to ERs – Page 119 List-5(10G EPON)
Annexure to ERs – Page 120 List-5(10G EPON)
Annexure to ERs – Page 121 List-5(10G EPON)
Annexure to ERs – Page 122 List-5(10G EPON)
Annexure to ERs – Page 123 List-5(10G EPON)
Annexure to ERs – Page 124 List-5(10G EPON)
Annexure to ERs – Page 125 List-5(10G EPON)
Annexure to ERs – Page 126 List-6 (Nx25G EPON)
PICS test List for Nx25G EPON
Annexure to ERs – Page 127 List-6 (Nx25G EPON)
Annexure to ERs – Page 128 List-6 (Nx25G EPON)
Annexure to ERs – Page 129 List-6 (Nx25G EPON)
Annexure to ERs – Page 130 List-6 (Nx25G EPON)
Annexure to ERs – Page 131 List-6 (Nx25G EPON)
Annexure to ERs – Page 132 List-6 (Nx25G EPON)
Annexure to ERs – Page 133 List-6 (Nx25G EPON)
Annexure to ERs – Page 134 List-6 (Nx25G EPON)
Annexure to ERs – Page 135 List-6 (Nx25G EPON)
Annexure to ERs – Page 136 List-6 (Nx25G EPON)
Annexure to ERs – Page 137 List-6 (Nx25G EPON)
Annexure to ERs – Page 138 List-6 (Nx25G EPON)
Annexure to ERs – Page 139 List-6 (Nx25G EPON)
Annexure to ERs – Page 140