stm-64 10062005 printed1

GR No.: GR/SDH-07/01.MAR.2005 for STM-64 Synchronous Multiplexer for Metro Networks

- 1 -

- 1 -

TRANSMISSION

Generic Requirements for STM-64 Synchronous Multiplexer for

ADM & TM Applications for Metro Networks

GENERIC REQUIREMENTS No.: GR/SDH-07/01.MAR.2005

TEC 2005 TELECOMMUNICATION ENGINEERING CENTRE

KHURSHID LAL BHAWAN, JANPATH NEW DELHI-110001.

INDIA.

All rights reserved and no part of this publication may be reproduced, stored in a retrieval sy stem or transmitted, in any form and by any means - electronic, mechanical, photocopying, recording, scanning or otherwise, without written permission from the Telecommunication Engineering Centre, New Delhi.

GR No.: GR /SDH-07/01.MAR.2005 for Synchronous Multiplexer at STM -64 bit rates

- 2 -

- 2 -

Document History

Name of the GR No. of the GR Remarks

STM-64 Synchronous Multiplexer for Terminal Multiplexer & ADM applications

GR/SDH-07/01.MAR.2005 First release


- 3 -

- 3 -

INDEX

Reference Documents ..............................................................................- 6 -

PART-I [GENERAL REQUIREMENTS]...............................................................- 9 -

1.0 Introduction..........................................................................- 9 -

1.3 Brief overview of services.........................................................- 9 -

2.0 Reference Documents ............................................................ - 14 -

3.0 Engineering requirements ....................................................... - 15 -

4.0 Operational Requirements....................................................... - 16 -

5.0 Quality Requirements ............................................................ - 16 -

6.0 Maintenance requirements ...................................................... - 17 -

7.0 Power Supply....................................................................... - 17 -

8.0 Accessories ......................................................................... - 18 -

9.0 Documentation .................................................................... - 18 -

10.0 Protection requirements......................................................... - 19 -

11.0 Optical Safety Requirements.................................................... - 19 -

12.0 Optical Access Port ............................................................... - 19 -

13.0 Operating Personnel Safety Requirements ................................... - 20 -

14.0 Electromagnetic Compatibility (EMC).......................................... - 20 -

PART-II [TECHNICAL REQUIREMENTS].......................................................... - 23 -

1.0 Functional requirements......................................................... - 23 -

1.5.1 Ethernet interfaces: Power-budget specification........................... - 23 -

1.15 Equipment Redundancy.......................................................... - 26 -

1.16 Construction Practice ............................................................ - 28 -

1.16.1 Expansion chassis ................................................................. - 28 -

1.16.2 Cross-connect architecture...................................................... - 28 -

1.16.3 Universal-slot architecture...................................................... - 28 -

2.0 Transport media................................................................... - 28 -

3.0 Performance Requirements ..................................................... - 28 -

4.0 Network Requirements........................................................... - 29 -

4.1 Application topologies............................................................ - 29 -


- 4 -

- 4 -

4.1.1 Classifications and application codes.......................................... - 29 -

4.2 Network topologies ............................................................... - 29 -

4.3 Equipment configuration......................................................... - 29 -

4.4 Resilience & Protection.......................................................... - 31 -

4.5 System Restoration ............................................................... - 34 -

4.6 Traffic interfaces in M-ADM/ADM/TM configuration......................... - 34 -

4.7 Cross-Connect Capability ........................................................ - 35 -

4.8 Type of connections on SDH path-layer ....................................... - 36 -

4.9 Loop-backs at SDH and MAC Layers ............................................ - 37 -

5.0 System Requirements ............................................................ - 37 -

5.1 Synchronisation.................................................................... - 37 -

5.2 Maintenance, Performance Monitoring and Alarm Signals ................. - 40 -

5.3 Order-wire and User-Data channel............................................. - 42 -

6.0 Technical Specifications in details ............................................. - 42 -

6.2.3 Tandem Connection Monitoring ................................................ - 45 -

6.2.4 Concatenation & Encapsulation mechanisms................................. - 45 -

6.2.4.2 Virtual Concatenation............................................................ - 45 -

6.2.5 Generic Framing Procedure ..................................................... - 45 -

6.2.6 Link Capacity Adjustment Scheme............................................. - 45 -

6.3 Ethernet Service requirements................................................. - 46 -

6.3.1 Layer 2 Service Implementation Requirements ............................. - 47 -

6.3.1.1 Service QoS Implementation .................................................... - 48 -

6.3.2 Layer 2 functionality details & specifications................................ - 49 -

6.3.3 Layer-2 Switching/Aggregation Implementation............................. - 50 -

6.3.4 Ethernet Provisioning – VCAT details .......................................... - 52 -

6.4 Network Node Interfaces - Details ............................................. - 52 -

6.5 Window of Operation............................................................. - 53 -

6.6 Optical Line Interface : STM-64 interface .................................... - 53 -

6.8 Jitter and Wander Performance................................................ - 54 -

6.9 Optical Tributary Interfaces..................................................... - 55 -


- 5 -

- 5 -

6.10 PDH Tributary Interfaces ........................................................ - 59 -

6.13 Ethernet over SDH (EoS) interface............................................. - 63 -

6.13.2 Transparent SAN interfaces ..................................................... - 64 -

7.0 Mechanical standards............................................................. - 64 -

8.0 Minimum equipment for testing ................................................ - 66 -

9.0 Field Trial........................................................................... - 67 -

Annexure I ITU-T Parametric Tables

Table 1/G.691 - Parameters for STM-64 optical interfaces................................ - 70 -

Table 2 – Parameters specified for STM-16 optical interfaces] - ITU-T/G.957 ........ - 71 -

Table-3 [Parameters specified for STM-4 optical interfaces] – ITU-T/G.957 ........... - 73 -

Table- 4 [Parameters specified for STM-1 optical interfaces] – ITU-T/G.957........... - 74 -

Annexure II Ordering Instructions ............................................................. - 76 -

APPENDIX I EMS Requirements ................................................................ - 77 -

1.0 Network Management Functions ............................................... - 83 -

1.1 General Functions................................................................. - 83 -

2.0 Configuration Management...................................................... - 83 -

3.0 Fault Management ................................................................ - 84 -

4.0 Performance Management....................................................... - 84 -

5.0 Security Management............................................................. - 85 -

6.0 Inventory management........................................................... - 86 -

7.0 Software Management............................................................ - 86 -

7.1 Software Download ............................................................... - 87 -

8.0 Management Interface............................................................ - 87 -

8.1 Southbound Interface ............................................................ - 87 -

8.2 Northbound Interface ............................................................ - 87 -

8.3 Local Management Interface.................................................... - 88 -

8.4 User Interface...................................................................... - 88 -

9.0 Embedded Control Channel ..................................................... - 88 -

APPENDIX II VLAN implementation in the M-ADM/ADM equipment ...................... - 92 -

GLOSSARY ....................................................................................... - 95 -


- 6 -

- 6 -

Reference Documents

ITU-T Rec.G.691 Optical interfaces for single-channel STM -64, STM-256 systems and other SDH systems with optical amplifiers.

ITU-T Rec.G.702 Digital hierarchy bit rates.

ITU-T Rec.G.703 Physical/electrical characteristics of hierarchical digital interfaces.

ITU-T Rec.G.707 Network node interface for the synchronous digital hierarchy (SDH).

ITU-T Rec.G.712 Transmission performance characteristics of pulse code modulation channels.

ITU-T Rec.G.773 Protocol suites for Q interfaces for management of transmission systems.

ITU-T Rec.G.774 Synchronous digital hierarchy (SDH) management information model for the network

ITU-T Rec.G.781 Synchronization layer function.

ITU-T Rec.G.783 Characteristics of SDH equipment functional blocks.

ITU-T Rec.G.784 Synchronous digital hierarchy (SDH) management.

ITU-T Rec.G.803 Architecture of transport networks based on the SDH.

ITU-T Rec.G.811 Timing characteristics of primary reference clocks.

ITU-T Rec.G.812 Timing requirements of slave clocks suitable for use as node clocks in synchronization.

ITU-T Rec.G.813 Timing characteristics of SDH equipment slave clocks (SEC)

ITU-T Rec.G.821 Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of integrated services digital network.

ITU-T Rec.G.823 The control of jitter and wander within digital networks which are based on the 2048 kb/s hierarchy.

ITU-T Rec.G.825 The control of jitter and wander within digital networks which are based on the synchronous digital Hierarchy (SDH)

ITU-T Rec.G.826 Error performance parameters and objectives for international constant bit rate digital paths at or above the primary rate.

ITU-T Rec.G.828 Error performance events for SDH paths

ITU-T Rec.G.829 Error performance events for SDH multiplex section and regenerator section

ITU-T Rec.G.841 Types and characteristics of SDH network protection architectures.

ITU-T Rec.G.957 Optical interfaces for equipments and systems relating to the synchronous digital hierarchy.


- 7 -

- 7 -

ITU-T Rec.Q.811 Lower layer protocol profiles for the Q3 and X interfaces

ITU-T Rec.Q.812 Upper layer protocol profiles for the Q3 and X interfaces

ITU-T Rec.M.2100 Performance limits for bringing into service and international PDH paths, sections and transmission systems.

ITU-T Rec.M.2101 Performance limits for bringing into service and maintenance of international SDH paths and multiplex sections.

ITU-T Rec.M.2120 PDH path, section and system and SDH path and multiplex section fault detection and localization procedures.

ITU-T Rec.M.3010 TMN conformance and TMN compliance.

ITU-T Rec.G.7041 Generic Framing Procedure

ITU-T Rec.G.7042 Link Capacity Adjustment Scheme

ITU-T Rec.G.7712 Architecture and specifications for data communication network for management information

ITU-T Rec.X.721 Information technology -Open systems Interconnection

IEC Publication 479-1 Guide on the effects of current passing through the human body

IEC Publication 215 Safety requirements of radio transmitting equipments

IEC Publication 1000-4-2 Testing and measurement techniques of Electrostatic discharge immunity test

IEC Publication 1000-4-3 Radiated RF electromagnetic field immunity test

IEC Publication 1000-4-4 Testing and measurement techniques of electrical fast transients/burst immunity test

IEC Publication 1000-4-6 Immunity to conducted disturbances

IS:8437 1993 Guide on the effects of current passing through the human body

IS:13252 1993 Safety of information technology equipment including electrical business equipment

IEEE 802.3 IEEE Ethernet standards series

IEEE 802.1 IEEE Ethernet Bridging standards series

TMF 814, TMF 608, TMF 513 TMN Forum Management Standards


- 8 -

- 8 -

Part I

General Requirements

- 9 -

GR No.: GR/SDH-07/01.MAR.2005 for Synchronous Multiplexer at STM-64 bit rates for metro applications - 9 -

Telecommunication Engineering Centre K.L. Bhawan, Janpath, New Delhi-110001.

Generic Requirements for Synchronous Multiplexer (ADM & TM) at STM-64 bit rates for Metro Applications

(GR No.:GR/SDH-07/01.MAR.2005)

PART-I [GENERAL REQUIREMENTS]

1.0 Introduction

1.1 This document describes generic requirements and technical specifications for

STM-64 Synchronous Multiplexer, for ADM and Terminal Multiplexer applications

in metro networks in Indian telecom network. The basic multiplexing principles

of the equipment shall be as per ITU-T Rec. G.707 specifications for SDH network

node interface (NNI). The equipment shall be designed to work on ITU-T Rec.

G.652 Single-Mode Fibre (SMF) as well as ITU-T Rec. G.655 Non-Zero Dispersion

Shifted fibre (NZ-DSF) at 1550nm window of operation. The equipment in TM and

ADM configurations shall provide a flexible combination of tributary interfaces as

listed in clause 4.6 in PART II of the GR. The offered equipment shall support all

the essential features and capabilities as outlined in this GR.

1.2 The equipment shall terminate a STM-64 ring on the aggregate interfaces as well

as it shall terminate multiple STM-1/4/16 rings at tributary ports subject to

cross-connection capacity in the system. An STM-64 aggregate ring formed with

the equipment shall consist of a flexible mix of TDM portion (drop/add of 2Mbps,

34Mbps/DS3, STM-1/4/16 tributaries), Point to point-VCAT channels, Point to

multipoint-VCAT channels and Multipoint to multipoint-VCAT channels. It is

recommended that the boundaries between these service-groups shall be

software provisioned using same interfaces/line-cards thus facilitating dynamic

adjustments based on service requirements.

1.3 Brief overview of services

Point to Point data services using GFP/VCAT entities shall be one of the

important applications of the equipment architecture; wherein the member-

channels forming a VCAT Group (VCG) shall be dynamically configured @VCn-Xv,

based on requirements. Packet data from one or more users shall also be

multiplexed on to a single VCAT (VCG) channel, as required, utilising a

centralised layer-2 aggregation (or layer-2 aggregation on Ethernet IO cards) in

the system, for greater network efficiency. Point to point, Point to multi-point

and Multi-point to multi-point services with EIR, CIR, EIR+CIR with configurable

- 10 -


burst duration shall be supported as per Metro Ethernet Forum (MEF) and ITU-T

Rec. 8010, G.8011, G.8011.x series standards.

1.3.1 The equipment shall facilitate the delivery of the following services:

§ Fixed-rate Ethernet Private Line (EPL) Services

§ Variable Rate (Burstable) Ethernet Virtual Private Line (EVPL) Services

§ Layer-2 Ethernet Transparent LAN Service (TLS) commonly called (E-LAN)

Services

§ TDM Private Line Services

§ Storage Area Networking (SAN) services.

The system shall provide OAM capability for various data services in accordance

with ITU-T Recs. G.8010, G.8011, and G.8011.x series (for EPL, EVPL, EVPLAN

etc.) and relevant MEF standards.

1.4 The equipment shall effectively combine LAN and WAN technologies in a flexible,

scalable, and cost-optimised solution. It is expected that architecture shall

address both Access and Metro Transport applications, enabling service providers

to cost-effectively deliver traditional & emerging data and TDM services over a

common Metro Ethernet Network (MEN) to both enterprises and residential

customers. It is envisioned that the equipment shall combine key features

outlined in various international standards to maximize bandwidth efficiency for

transporting data over a Metro Ethernet Network. These standards include IEEE

802.1 and 802.3 series, ITU-T VCAT, GFP & LCAS as per ITU-T Recs. G.707,

G.7041 & G.7042 respectively, Ethernet-Line/LAN service attributes and QoS

requirements as per ITU-T Recs. G.8010, G.8011, G.8011.x series as well as per

relevant MEF service standards.

1.5 At functional level, the STM-64 equipment shall broadly consist of the following

sub-systems:

§ SDH VC-4/VC-3/VC-12 cross-connect system

§ Layer-2 Ethernet MAC bridging & aggregation sub-system (on Ethernet IO cards

or a central Ethernet MAC switch)

§ Traffic ports (SDH, PDH, SAN & Ethernet etc.)

§ Clock reference sub-system

§ Traffic control & management sub-system

§ Local SOH & POH termination for auxiliary channels & OH access sub-system

§ Engineering Order-wire sub-system

§ Power-supply sub-system etc.

- 11 -


The traffic/line ports - STM-64/16/4/1, 45/34/2 Mbps, SAN (FICON, ESCON, FC,

DVB-ASI etc.) & Ethernet (Fast Ethernet & Gigabit Ethernet) interfaces, shall be

flexibly equipped upto 100% capacity of the equipment. The purchaser may

convey specific requirements for interfaces. But system shall be loaded with

100% capacity for testing. An illustration for interface loading is given in clause

8.0 in PART II of the GR for test purposes.

1.6 The equipment shall be configurable either as an ADM or as two Terminal

Multiplexers (TM’s) with software configurations only. The granularity of the

cross-connection shall be at VC-12, VC-3 and VC-4 in single-stage and the size of

cross-connect shall be as specified in the subsequent clauses of the document.

1.7 STM-64 Synchronous Multiplexer shall be an SDH based multiplexing equipment,

supporting the set of specifications for Synchronous Digital Hierarchy as per ITU-

T Rec. G.707 (2003 version), constituting a Network Element. The equipment

shall have the Network Node Interface (NNI) compliant to ITU-T Rec. G.707. The

Network Element shall meet various atomic and compound functions of the

multiplexing equipment as specified in ITU-T Rec. G.783, with extensive

management control capabilities as specified in ITU-T Rec. G.784.

1.8 The equipment shall provide optical line interfaces at 9953.280Mb/s with

standard optical interfaces as per ITU-T Rec. G.691 as detailed later. The

architecture of the equipment shall be as per ITU-T Rec. G.803 and the generic

functions of equipment shall be as per ITU-T Rec. G.805. On the tributary-side,

the Network Element shall provide access to the constituent electrical signals

through 2Mb/s, 34Mbps/DS3 (auto-sensed or configured) and 155.520Mb/s

electrical interfaces (STM-1e) as per ITU-T Rec. G.703, as well as standard

optical interfaces at STM-1, STM-4 and STM-16 bit-rates as per ITU-T Rec. G.957.

The purchaser shall communicate exact application-code requirements for STM-N

line and tributary interfaces.

1.9 The equipment shall provide TCM functionality at VC-4 paths (software-

configured for TCM monitoring) using N1 byte of Higher Order Path-Overhead, in

accordance with ITU-T Rec. G.707.

1.10 The equipment shall also support “Ethernet over SDH (EoS)” transport capability

at Fast Ethernet interfaces - 10/100BaseT & 100BaseFX@1310nm, optical GigE

interfaces at - 1000BaseSX multi-mode (optional to purchaser’s requirements),

1000BaseLX @1310nm and 1000BaseLH @1310nm using ITU-T G.7041 specified

GFP encapsulation. The equipment shall support both GFP variants i.e., GFP-F &

- 12 -


GFP-T, as per ITU-T Rec. G.7041. GFP-Framed mode shall be supported for

Ethernet clients and GFP-Transparent (GFP-T) mode shall be supported for block-

code oriented SAN payloads i.e., FICON, ESCON, FC, DVB-ASI etc. GFP-T is

recommended to be provided through a common-card along with GFP-F.

However, standalone SAN IO cards for GFP-T shall also be permitted. In case of a

common-card, for both GFP modes, the selection of particular GFP mode shall be

either auto-sensed or through LCT & EMS configuration.

1.11 In case of a common-card, for both GFP modes, the GFP-F and GFP-T

configuration shall be provided per client port basis.

1.12 The equipment shall provide layer-2 Ethernet bridging and aggregation

functionality as per IEEE 802.1D, with 802.1P priority and 802.1Q VLAN-ID

support per Ethernet user-port. The exact details for VLAN administration are

provided in Appendix II to the GR. The Layer-2 aggregation shall support Rapid

Spanning Tree Protocol (RSTP) as per IEEE 802.1s standard. The detailed

technical specifications for Ethernet switch are provided later in the GR. The

bandwidth granularity for Ethernet ports shall be 64Kb/s for Fast Ethernet and

1Mb/s for GigE ports. Further, it is envisaged that the equipment shall support

Link Capacity Adjustment Scheme (LCAS) for VCAT groups as per ITU-T Rec.

G.7042.

1.13 Virtual concatenation in the form of VC12-Xv and VC4-Xv as per ITU-T Rec. G.707

shall be provided in the equipment. VC3 based VCG’s shall be optional to

purchaser’s requirements. Contiguous concatenated payloads at VC4-4c, VC4-

16c, and VC4-64c (as applicable) for all STM-N ports irrespective of whether it is

tributary port or a line port, as per ITU-T Rec. G.707 shall also be supported for

termination as well as for cross-connection across the equipment.

1.14 The VCG (VCAT) channels shall be universal i.e., any VCG shall be composed of

VCn’s across any combination of STM-N interfaces in a non-blocking manner. Also

the VCGs as well as slots in the chassis shall be independent of service

provisioning i.e., there shall be no demarcation based on VCG’s for Fast

Ethernet, GigE, SAN interfaces etc.

1.15 In order to support the specified Ethernet requirements, there shall be adequate

no. of VCGs in the system supporting GFP-F and GFP-T encapsulation.

1.16 The system shall be engineered to support at least up to 32 Fast Ethernet ports

in TM mode and up to 64 ports for ADM mode. It is recommended that each IO

card for Fast Ethernet supports a minimum of 8 Ethernet ports @10/100BaseT or

- 13 -


100BaseFX. The system shall also provide integrated layer-2 switching &

aggregation, the requirements and specifications of which are given in clause 6.3

and sub-clauses thereof, in PART II of the GR.

1.17 In Ring topology, the equipment shall support both Multiplex Section Shared

Protection Ring (MS-SPRing) at STM-64 & STM-16 ports/interfaces as well as

SNC/N protection mechanisms at STM-1 & STM-4 ports/interfaces configured per

VC12, VC3, VC4 through EMS/LCT, as specified in the ITU-T Rec. G.841. The

equipment shall provide protection to the members of VCG also. The protection

by default for members of a VCG shall be ENABLED until configured otherwise.

1.18 The STM-1, STM-4 and STM-16 tributary ports in STM-64 ADM shall either be used

as linear tributary interfaces uplinked through STM-64 line interfaces as well as

shall be utilised to terminate STM-1/STM-4/STM-16 rings. It shall be possible to

add/drop tributaries, fully or partially, pertaining to these STM-1/4/16 tributary

rings across STM-64 aggregate ring terminated on the ADM, in a non-blocking

manner, subject to matrix capacity. Also, it shall be possible to cross-connect

the tributaries of these STM-1/STM-4/STM-16 tributary-rings and STM-64

aggregate ring to any of the AU/TU in the central cross-connect of M-ADM/ADM

for further transmission. The STM-1, STM-4 and STM-16 tributary-rings, stated

here-in-above, shall also support protection mechanisms as specified in their

respective TEC product-GRs.

1.19 In case, it is not possible to equip the equipment interfaces as per clause 8.0 in

PART II of the GR, in a single main-chassis; the use of only a single expansion-

chassis shall be permitted. There shall be neither cross-connections performed in

the expansion-chassis nor any control-card housed therein. In such cases, where

the expansion-chassis is used, redundant connectivity between main & expansion

chassis shall be provided. It is recommended than such redundant connectivity is

provided through system backplane.

1.20 In case, an expansion-shelf is used, the cross-connection of tributaries as residing

in the expansion-chassis shall also be made using central cross-connect in the

main-chassis. No subtended cross-connect, at expansion-chassis level, shall be

permitted. There shall be only one central cross-connect in the system providing

single-stage cross-connection, as specified in clause no. 4.7 in PART II of the GR.

Further, the system shall not provide any blockage as regards cross-connection

across any STM-N line to tributary interfaces (and vice-versa) and also tributary

to tributary interfaces. Also, the system shall provide VCG (VCAT) configuration

- 14 -


comprising of any VCn in the system spanning across any STM-N line interface and

tributary slot in the system.

1.21 The equipment shall support various types of SDH cross-connections, viz. - point

to point unidirectional and point to point bi-directional as well as point to multi-

point unidirectional and broadcast connections.

1.22 Provision shall exist to loop-back input digital signals at various higher or

equivalent hierarchical stages of SDH multiplex hierarchy through the

equipment. There shall also be provision for local and remote MAC layer loop-

backs.

1.23 The equipment shall have provision for synchronization with the timing-signal

extracted from SDH aggregate signals i.e., STM-N signals terminating at the

equipment, with minimum three user-defined priorities exercised through

LCT/EMS. The equipment shall also have a provision to be synchronized with

external 2MHz signal as well as 2048 Kb/s signal per ITU-T Rec. G.703. Also, the

equipment shall provide at least two external (one 2Mbps and the other as 2MHz)

timing output ports with accuracy traceable to the system synchronisation clock.

1.24 The EMS requirements for the system have been detailed in the Appendix-I.

1.25 In Add/Drop configuration, the equipment shall provide "Through payload cross-

connect" capability, "Local cross-connect" capability", “Drop and Continue" as

well as "Broadcast" capability.

1.26 The equipment is envisaged to be used mainly for metro applications, supporting

ITU-T G.691 shorthaul applications @1550nm window. In order to achieve the

specified span-coverage for shorthaul applications on ITU-T Rec. G.652 and

G.655 fibre, the use of Dispersion Compensation and Accommodation techniques

shall be permitted, if necessary, as specified in ITU-T Rec. G.691.

2.0 Reference Documents

2.1 Whatever technical specifications that have not been not been specifically stated

in this document, shall deem to be as per relevant, latest ITU-T specifications.

2.2 Some of relevant specifications are given in ‘Applicable Reference Documents’ in

the beginning of the GR.

2.3 All reference to TEC GRs implies for their latest issues.

- 15 -


3.0 Engineering requirements

3.1 The equipment shall be fully solid-state and adopt state-of-the-art technology.

3.2 The equipment shall be compact and composite in construction and shall be

light-weight. The actual dimensions and weight of the equipment shall be

furnished by the manufacturers.

3.3 All connectors shall be reliable and of standard type to ensure failure-free

operation over long periods under specified environmental conditions. All

components shall be CACT approved.

3.4 All connectors and cables used shall be of low-loss type and suitably shielded.

The type of connectors used at the application interfaces & the user- interfaces

shall be of wire-wrapping type or as per any other international industry

standard. No soldering shall be allowed for the connectors.

3.5 The equipment shall be housed in standard 19" or ETSI standard rack and shall

provide front access.

3.6 The equipment shall provide natural cooling arrangement which shall not involve

any forced cooling by using fans etc., either inside or outside the equipment. In

case, the natural cooling arrangement is not sufficient, the manufacturer may

use fans for cooling purposes provided:

§ Fan redundancy in hot-standby mode is provided.

§ The fan failure is reported through LCT/EMS.

§ Multiple fans are there in one tray with (N:1) redundancy.

§ Fans are located at convenient place in the equipment not disturbing the internal

equipment layout.

§ Fans are DC operated.

§ MTBF is better than 80,000 hours.

§ Inclusion of fans for cooling purposes does not deteriorate the MTBF values of the

equipment.

3.7 The supervisory indications, built-in test equipment (BITE), and other control/

switches shall be provided at convenient locations on the bay preferably at a

height of around 1500mm for ease of maintenance.

3.8 The plug-in units shall be hot-swappable as to allow their removal/ insertion

while the equipment is in energized condition.

3.9 The mechanical design and construction of each card/ unit shall be inherently

robust and rigid under all conditions of operation, adjustment, replacement,

- 16 -


storage & transport and shall conform to para-12 of BSNL-QA document no.: QM-

333 (issue-2:1998) - "Specifications for environmental testing of electronic

equipment for transmission and switching use". The equipment shall comply with

‘B2’ category for environmental conditions including vibration test.

3.10 Each sub-assembly shall be clearly marked with schematic references to show its

function, so as to be easily identifiable from the layout diagram in the handbook.

3.11 Each terminal block and individual tags shall be numbered suitably with clear

identifying code and shall correspond to the associated wiring drawings.

3.12 All controls, switches & indicators etc., shall be clearly marked to show their

circuit designation and functions.

4.0 Operational Requirements

4.1 The equipment shall be designed for continuous operation.

4.2 The equipment shall perform satisfactorily without any degradation up to an

altitude of 3000 meters above mean sea level. A test certificate from the

manufacturer shall be acceptable.

4.3 The equipment shall work without any degradation in saline atmosphere near

coastal areas and shall be protected against corrosion. A test certificate from the

manufacturer shall be acceptable.

4.4 Visual indication to show power ON/OFF status shall be provided.

4.5 Wherever visual indications are provided, ‘green colour’ for healthy and ‘red

colour’ for unhealthy conditions shall be used. Some other colour shall be used

for non-urgent alarms.

5.0 Quality Requirements

5.1 The manufacturer shall furnish the MTBF/MTTR values for the equipment. The

calculations shall be based on the guidelines in either BSNL-QA document no.:

QM-115 (January’ 1997) - "Reliability Methods and Predictions" or as per any other

international standard.

5.2 The equipment shall be manufactured in accordance with international quality

standards ISO-9001, ISO-9002 or ISO-9001:2000 for which the manufacturer shall

be duly accredited. A quality plan describing the quality assurance system

followed by the manufacturer shall be required to be submitted.

- 17 -


5.3 The equipment shall conform to the environmental requirements as specified in

BSNL-QA document no.: QM-333 (latest issue): "Specification for environmental

testing of electronic equipment for transmission and switching use". The

applicable tests shall be taken for environmental category ‘B2’ including

vibration test.

6.0 Maintenance requirements

6.1 Maintenance philosophy shall be to replace faulty units/subsystems after quick

on-line analysis through monitoring sockets, alarm indications and Built-in Test

Equipment. The actual repair shall be undertaken at centralized repair centres.

The corrective measures at the site shall involve replacement of faulty

units/sub-systems.

6.2 The equipment shall provide easy access for servicing and maintenance.

6.3 Extension of degraded paths to the test-access points for diagnostic work, after

traffic is switched over to the healthy path, shall be provided.

6.4 Suitable visual/audio alarms shall be provided for identification of faults in the

system as well as in faulty units. Suitable potential-free contacts (preferably)

or any other suitable method, shall be provided for extension of summary

alarms.

6.5 As and when bugs are found/determined in the software, the manufacturer

shall provide patches/firmware replacement, if involved, free of cost for three

years. Modified documentation, wherever applicable, shall also be supplied

free of cost or as mutually agreed between the vendor and the purchaser.

6.6 Ratings and types of fuses used shall be indicated by the supplier.

6.7 The manufacturer/supplier shall furnish the list of recommended spares for

three years’ maintenance.

6.8 The supplier shall have maintenance/repair facility in India.

6.9 Supplier shall guarantee the spares so long as the equipment is in service, at

least for 10 years from the date of supply. The purchaser shall like to stock

spares as and when the supplier decides to close-down the production of the

offered equipment. In such an event, supplier shall give a two years’ notice to

the purchaser so as to stock the spares.

7.0 Power Supply

The equipment shall be powered by the station power-plant and shall meet the

- 18 -


following requirements:

(a) Nominal power supply is -48V DC with a variation in the range -40V to -60V.

The equipment shall operate in this range without any degradation in

performance.

(b) The equipment shall be adequately protected against voltage variation beyond

the range specified in sub-clause (a) and also against reverse input polarity.

(c) The power consumption shall be minimal. The actual power-consumption shall

be furnished by the manufacturer.

(d) The derived DC voltages in the equipment shall have adequate protection

against over-voltage, short-circuit and overload.

(e) The equipment shall have a provision for redundancy of power supply cards.

8.0 Accessories

8.1 The supplier shall provide one complete set of:

a. All necessary interfaces, connectors, connecting cables and accessories

required for satisfactory and convenient operation of the equipment. Types

of connectors, adapters to be used and accessories of approved quality shall be

clearly indicated in the operating manuals which shall be in conformity with

the detailed list in the GR.

b. Software and the arrangement to load the software at site.

Note: Additional sets shall be ordered optionally.

8.2 Special tools, extender boards, extender cables and accessories as essential for

installation, operation and maintenance of the equipment shall be clearly

indicated and supplied along with the equipment.

8.3 Special tools, extender boards, extender cables and accessories as essential for

repair of the equipment shall be clearly indicated and supplied in case the

same are ordered.

9.0 Documentation

Technical literature in English language with complete layout, detailed block-

schematics and circuit-diagrams of various assemblies shall be supplied. The

repair philosophy of the equipment shall be specified by the manufacturer. All

aspects of installation, operation and maintenance shall be covered in the

manuals. The manuals shall include the following:

i) Installation, Operation and Maintenance Manual:

a) Safety measures to be observed in handling the equipment.

- 19 -


b) Precautions for installation, operation and maintenance.

c) Test jigs & fixtures required and procedures for routine maintenance,

preventive maintenance, troubleshooting and sub-assembly replacement.

d) Illustration of internal and external mechanical parts.

ii) Repair Manual (to be supplied when ordered):

a) List of replaceable parts used including their sources and the approving

authority shall be provided.

b) Detailed ordering information for all the replaceable parts shall be listed in

the manual to facilitate re-ordering of spares.

c) Procedure for trouble-shooting and sub-assembly replacement shall also be

provided. Test fixture and accessories required for repair shall also be

indicated. Systematic trouble-shooting chart (fault tree) shall be given for

the probable faults with their remedial actions.

10.0 Protection requirements

10.1 The equipment shall have a terminal for grounding the rack.

10.2 Protection against short-circuit/open-circuit in the accessible points shall be

provided.

10.3 All switches/controls on front panel shall have suitable safeguards against

accidental operation.

10.4 The equipment shall be adequately safeguarded to prevent entry of dust,

insects and lizards.

11.0 Optical Safety Requirements

The equipment shall meet optical safety requirements as per ITU-T Rec. G.664

and IEC-60825-1 (latest edition). The equipment shall have visual warning and

controls ensuring danger-free operation. Automatic Power Reduction (APR) or

Automatic Laser Shut-Down (ALSD) shall be provided at all optical line &

user/traffic interfaces as per ITU-T Rec. G.664.

12.0 Optical Access Port

The optical access ports shall be so designed as to protect themselves against

entry of dust when they are not occupied by an external fiber-optic

- 20 -


connection. The optical access port shall be located appropriately as to be easy

to operate. The optical access port shall be easy to clean by the user.

13.0 Operating Personnel Safety Requirements

The operating personnel shall be protected against shock hazards as per: IS:8437 1993: “Guide on the effects of current passing through the human

body” [equivalent to IEC publication 479-1 1984].

The equipment shall also conform to:

IS:13252 1992: “Safety of information technology equipment including

electrical business equipment”[equivalent to IEC publication 950 1986].

The equipment shall follow proper construction practice to minimize

unintended radiation due to leakage from any gap or monitoring points. All

unused ports and monitoring points shall be terminated. The power-flux density

shall not exceed 1mW/cm2 at a distance of 2.5 cms.

14.0 Electromagnetic Compatibility (EMC)

The equipment shall conform to the EMC requirements as per the following

standards and limits indicated therein. A test certificate and test report shall

be furnished for:

a) Conducted and radiated emissions: To comply with Class A or B [to be

specified in the GR as per the product requirement] of CISPR 22 2003 - "Limits

and methods of measurement of radio disturbance characteristics of

Information Technology Equipments";

b) Electrostatic discharge: To comply with IEC 61000-4-2 2001 - "Testing and

measurement techniques of Electrostatic discharge immunity test" under

following test levels:

Contact discharge level 2 ± 4 KV;

Air discharge level 3 ± 8 KV;

c) Fast-transients common-mode (burst): To comply with IEC 61000-4-4 1995

with Amendment 1 (2000) and Amendment 2 (2001) - "Testing and

measurement techniques of electrical fast transients/ burst immunity test"

under Level 2 1 KV for DC power lines; 1 KV for signal control lines;

d) Immunity: IEC 61000-4-32002 Radiated RF Electromagnetic Field Immunity

test under test level 2 (test field strength 3 V/m) for general purposes in

- 21 -


frequency range 80 MHz to 1000 MHz and under test level 3 (10 V/m) for

protection against digital radio telephones in frequency ranges 800 MHz to 960

MHz and 1.4 GHz to 2.0 GHz.

e) Surges line to earth coupling and line to line coupling: To comply with IEC

61000-4-52001Test & Measurement techniques for Surge immunity tests"

under test levels of 0.5 KV for line to line coupling and 1KV for line to earth

coupling;

f) Radio frequency common-mode: To comply with IEC 61000-4-

62001"Immunity to conducted disturbances, induced by radio frequency

fields" under the test level 2 3 Vrms clamp-injection method for DC lines and

Signal Control lines.

Note (i): Classification of the equipment: Class B: Class B is a category of apparatus which satisfies the class B disturbance

limits.

Class B is intended primarily for use in the domestic environment and may

include:

• Equipment with no fixed place of use; for example, portable equipment

powered by built in batteries;

• Telecommunication terminal equipment powered by the

telecommunication network;

• Personal computers and auxiliary connected equipment.

Note (ii): The domestic environment is an environment where the use of broadcast

radio and television receivers may be expected within a distance of 10 m of

the apparatus connected.

Class A: Class A is a category of all other equipment, which satisfies the class A limits

but not the class B limits.

Note (iii): For tests for checking compliance to above EMC requirements, the method

of measurements shall be in accordance with TEC standard No.:SD/EMI-

02/02.SEP.2001 and the references mentioned therein.]

Note (iv): A test certificate from autonomous & accredited lab shall be acceptable on

this account.

- 22 -


Part II Technical Requirements

- 23 -


PART-II [TECHNICAL REQUIREMENTS]

1.0 Functional requirements

1.1 It shall be possible to configure the ADM equipment as two back to back TM’s by

extracting/disabling the requisite hardware, and software settings. The

equipment shall not extend any alarm, upon disabling/extracting the hardware.

1.2 The hot-swapping of a card/unit shall not affect working of any other tributaries.

Hot-swapping capability shall be provided for all cards/units including power-

supplies. No EMS notification or system setting shall be required for extraction or

insertion of any unit/card.

1.3 It shall be possible to configure the network as unprotected and fully-protected in

case of MS-SPRing protection. In case of SNC protection, it shall be possible to

configure the network as fully-protected, partially-protected or unprotected. In

case of MS-SPRing protection, it shall be possible to transport extra-traffic over

protection-channels i.e., over protection VC4s during normal operation of a ring

as specified in ITU-T Rec. G.841. Upon failure, the working traffic shall switch-

over to these protection channels.

1.4 The equipment is envisaged to comply with S 64.2a or S 64.2b optical interfaces

@1550nm window as specified in ITU-T Rec. G.691. For test purposes, optical

tributary interfaces @ STM-1o and STM-4o shall be as per ITU-T Rec. G.957

shorthaul application (S 1.1 and S 4.1 respectively at 1310nm) while the purchaser

may ask for any other application-code. The exact requirements for optical

interfaces for tributaries and aggregate shall be specified by the purchaser.

1.5 Also, the equipment shall support optional colour wavelength at STM-16 and STM-

64 aggregate levels as specified in ITU-T Rec. G.694.1. The manufacturer shall

supply any of the wavelengths asked by the purchaser.

1.5.1 Ethernet interfaces: Power-budget specification

The reach and power budget requirements for this document for various Ethernet

interfaces shall be-

100BaseFX @1310nm 8dB power budget on G.652 fibre.

1000BaseSX1 (50µ multi-mode) interface Link power budget (multi-mode) 7.5dB

Operating distance (nominal) 550m

Channel insertion loss 3.56dB

- 24 -


Link power penalties 3.57dB

Unallocated margin in link power budget 0.37dB

1 Link penalties are used to calculate link budget and distances and is not intended to be tested. A wavelength

830nm is used to evaluate channel insertion loss, link power penalties, and unallocated margin. Attenuation for 50µ multi-mode fibre at 830nm is taken as 3.5dB/km and 1.5dB/km at 1310nm.

* 1000BaseSX interface is optional to purchaser’s requirements. The interface shall be supplied with multi-mode to single-mode adaptor as an integral part of the offer.

1000BaseLX2 (10µ single-mode @1310nm) interface Link power budget 8.0dB

Operating distance (nominal) 5000m





1270nm is used to evaluate channel insertion loss, link power penalties, and unallocated margin. Attenuation for 10µ single-mode fibre at 1300nm window is taken as 0.5dB/km.

1000BaseLH3 (10µ single-mode @1310nm) interface Link power budget 10.5dB

Operating distance (nominal) 10,000m





1270nm is used to evaluate channel insertion loss, link power penalties, and unallocated margin. Attenuation for 10µ single-mode fibre at 1300nm window is taken as 0.5dB/km.

1.6 Two bytes viz. E1 or E2 are assigned for EOW applications. Either of the two bytes

or both shall be used for the order-wire for the maintenance of the equipment,

supporting Multiplexing to Multiplexing stations calling with full-duplex selective-

calling facilities. VoIP based implementation for EOW shall be permitted subject

to-

1. Speech quality shall be equivalent to ITU-T Rec. G.712.

2. End to end packetized voice characteristics are with in ITU-T Rec. G.114 prescribed

limits.

3. Manufacturer is able to arrange the test methodology and test procedure at his/her

arrangements.

1.7 The order-wire shall be restored along with payload in case of system switching-

over from normal to protection-channel and vice-versa. No disconnection of call in

selective-calling mode shall take place in event of protection switching.

1.8 The equipment shall have the capability of providing the Timing Signal quality

information as per ITU-T Rec. G.707 using S1 byte.

- 25 -


125µs 30ms

Guard-band for design tolerance

Rejection range Desired continuous range for compensation

Acceptance range

50ms

TEC confidential

1.9 The power-supply failure/ Work Station/ Network Server break-down/ bugs in the

software shall not affect the current tributary-connection map. The

removal/replacement of any unit shall also not affect the existing connection map.

No reconfiguration is called for against this action.

1.10 Differential Delay for VCAT Implementation

Differential delay in reference to VCAT implementation refers to the maximum

delay in arrival times of different members of a VCAT group. The manufacturer

shall ensure that the system is capable to compensate for all values of differential

delay from 125µs right upto 30ms, as a continuous range.

The systems capable to compensate for less than 30ms differential delay, shall be

liable for rejection. Similarly, on the higher-side, the systems capable to

compensate for >50ms differential delay, shall also be liable for rejection. The

range from 30-50ms has been kept as a ‘guard-band’ for implementation tolerance.

Figure 1: Illustration for differential-delay compensation limits

The same limit shall apply to all VCs i.e.- VC12, VC3 & VC4.

1.11 The manufacturer shall ensure MS-SPRing interworking with equipment of other

vendors.

1.12 There shall be no single point-of-failure in the system. For that objective, in ADM

mode, the East & West-side TX/RX STM-N interfaces for STM-64 aggregate as well

as STM-1/4/16 tributary rings shall be accommodated on two separate cards.

1.13 The provision for 100BaseFX Ethernet interface shall preferably be made through

IO cards in the system; however the use of separate media-converter for

conversion of electrical Fast Ethernet interface to 100BaseFX (and vice-versa) shall

also be acceptable. There shall be adequate arrangements provided for these

media-converters to be mounted in standard racks. The system engineering of the

- 26 -


equipment shall be well-planned to route the optical patch-cords from the

sideways of the equipment to avoid jumbling of patch-cords.

1.14 Network Applications of STM-64 multiplexer

The main applications of STM-64 equipment in a metro network shall be the

network-nodes where a lot of wide-band traffic from multiple lower-speed

tributaries needs to be consolidated, groomed and distributed towards high-speed

core network & vice-versa. It shall also offer data interfaces for terminating and

aggregating layer-2 traffic. The system shall also be used for Storage Area

Networking applications. In Terminal Multiplexer mode, STM-64 equipment may be

used to consolidate metro traffic on STM-64 interface constituting one channel of

DWDM ‘longhaul network’. The inclusion of STM-64 equipment at the Central Office

shall facilitate replacement of multiple ring-wise ADMs at Central Office for

flexible ring-interconnection in a non-blocking manner facilitating metro traffic

aggregation. It shall be possible to configure the equipment in various topologies

i.e., mesh connectivity, star connectivity as well as other network topologies.

The STM-64 equipment must support the following range of ‘Network Element’ applications:

1. Linear topologies with add/drop functions (chains) & hubbing operation.

2. Arbitrary mesh topology with a robust mesh restoration.

3. Ring topologies with support for termination of multiple rings on all optical

line/tributary ports.

The equipment shall be configured as a multi-line TM, as an ADM as well as a

stand-alone cross-connect for various network applications.

1.15 Equipment Redundancy

The equipment shall provide complete redundancy for–

1. Control/Processor

If the Control/Processor unit failure does not affect the working traffic, no

redundancy of Control/Processor unit shall be required.

However, if the Control/Processor unit failure does result in traffic failure, then

(1+1) hot-standby mode redundancy of Control/Processor shall be provided in the

equipment. Immediate upon insertion of a healthy card, the system shall revert to

its pre-failure NMS/EMS configuration.

- 27 -


There shall be support for dual-homing for EMS connectivity for no loss of EMS

connectivity, through two Gateway NEs (GNE’s) on a ring. Both GNEs shall have

control- card equipped. In case of total loss of EMS connectivity to the

system/network, the system design shall provide local storage of all performance &

fault data, as specified in Appendix I to GR, for all connections pertaining to all

NEs, in the sub-network. Such connectivity loss might happen due to control-card

failure at both GNE’s and/or failure of DCN link to EMS. In-built intelligence shall

be there in EMS for selection of appropriate GNE at distant end of a DCN link upon

failure of control card at one of the GNE’s, for EMS connectivity.

Note: The performance data as envisaged above for SDH connections shall also be

ensured for Ethernet clients.

2. Switch/Matrix

There shall be provision for a parallel hot-standby matrix unit as per details as in

clause 4.7 (for SDH connect) to take-over traffic during failure of the working card.

In case of centralised MAC SW, there shall be a backup MAC SW. For distributed

MAC switching on IO cards, it is recommended that there shall be a combined

backup IO card for both Fast and Gigabit Ethernet interfaces with capacity as

detailed later in the GR. The local Ethernet traffic after PHY termination in IO card

shall have autonomous path availability to the MAC fabric of this backup IO card

through backplane. The user Ethernet traffic shall be switched to this alternate

path if MAC fabric fails in an IO card.

The switching over time from working switch matrix to standby matrix (at SDH &

MAC layers) shall be completed within 50 ms.

3. Power Supply

If the power-supply is provided through a centralized power-supply unit at chassis-

level, a hot-standby power-supply shall be provided at chassis-level, to ensure

smooth working of the equipment during failures.

Further, there shall be provision for dual-feed arrangement to the chassis power-

supply, such that in case of failure of one feed, the system shall be able to

function in a healthy manner without traffic interruption.

4. There has to be complete redundancy for Timing Circuitry against failures.

* The changeover for all redundancy actions shall be completed with in 50ms.

- 28 -


1.16 Construction Practice

1.16.1 Expansion chassis

Solution shall be supplied as a single-chassis solution. Only one expansion-chassis

shall be permitted if the whole capacity as per clause 8.0 in PART II of the GR is

not accommodated in a single main-chassis. The expansion-chassis shall contain

only IO cards. There shall be single-stage (direct) and non-blocking access/visibility

of the central cross-connect to all IO cards irrespective of whether an IO card is in

main or expansion-chassis. There shall be no control-card and cross-connect card

equipped in the expansion-chassis. The expansion-chassis shall provide dual-

redundant connectivity to the main-chassis.

1.16.2 Cross-connect architecture

There shall be single-stage cross-connection in the equipment. For that, there shall

be no cross-connections performed in the expansion-chassis. The expansion-

chassis, if used, shall only serve as IO extension-cage. There shall be single-stage

4/3/1 cross-connection for all the IO cards in a non-blocking manner.

1.16.3 Universal-slot architecture

It is recommended that all slot positions except control-card, matrix, STM-N

optical and power supply slots shall be universal. Any interface unit shall be housed

in any slot.

2.0 Transport media

The equipment in the longhaul application shall use Standard Single-Mode Fibre

cable as per TEC GR Nos. -

1. GR/OFC-01/ 04.SEP.2003 (with all amendments) on Metal Free Optical Fibre Cable

2. GR/OFC-02/03 SEP.2003 (with amendments) on Armoured Optical Fibre Cable

3. GR/OFC-05/01.JUL.2000 (with amendments) on Metal-Free Optical Fibre Ribbon Cable.

4. GR/OFC-06/01.JAN.2001 (with amendments) on Armoured Optical Fibre Ribbon Cable.

5. GR/OFC-08/01.JUL.2003 (with amendments) on Metal-Free Optical Fibre NZ-DSF Cable.

3.0 Performance Requirements

The equipment shall be tested for error performance as follows:

a) In laboratory: BER performance over simulated hop shall be tested better than

1x10-10 for 48 hours on each channel at reference receive-level (nominal level).

Also IETF RFC 2544 compliance shall be tested for end-to-end Ethernet service.

- 29 -


b) In field: BER performance for 48 hours shall be established to conform to ITU-

T Recs. G.826 & G.828.

4.0 Network Requirements

4.1 Application topologies

The equipment is envisaged to work on shorthaul application code, S 64.2a or S

64.2b, as per ITU-T Rec. G.691.

4.1.1 Classifications and application codes

The STM-64 Synchronous Multiplexer shall support shorthaul S 64.2a or S 64.2b

optical line interface for G.652 fibre and S 64.5a or S 64.5b optical line interface

for G.655 fibre, as per ITU-T Rec. G.691.

The targeted distances are defined in Table-1 are based upon attenuation of

11dB/40 kms. at 1550nm as per ITU-T G.691. These limits are the worst-case

figures at the end of life and are based upon the design objective of a BER not

worse than 10-12.

The distance figures given in the Table-1 are between the optical Mux and Demux

without In-Line Amplifiers. System may implement FEC as per ITU-T Rec. G.707 or

G.709 to achieve application code requirements.

Table-1

Fibre Type G.652 G.652 G.655 G.655

Application Code S-64.2a S-64.2b S-64.5a S-64.2b

Target distance (km) 40 40 40 40

4.2 Network topologies

It shall be possible to configure the equipment to implement various network

topologies as detailed below-

1) Point to point/Linear-chain topology

2) Bus topology

3) Ring or Hub

4) Mesh topology.

Two-fibre application i.e., one dedicated fibre for transmit-direction and one for

receive-direction is envisaged for all network applications as above.

4.3 Equipment configuration

The equipment shall support the following configurations-

1) Terminal Multiplexer

- 30 -


Figure 2 – Single-Node Interconnected Rings

Node-1

Node-2

Figure 3- Two-node overlapping rings

2) Add/Drop Multiplexer.

4.3.1 Ring termination capability

The following ring inter-connection topologies shall be supported.

§ Single-Node Interconnected Rings

§ Two-Node Overlapping Rings

§ Two-Node Interconnected Rings

Single-Node Interconnected Rings

This topology uses one node to connect two separate rings. The interconnecting

node uses four optical ports (two for each ring). Each ring must use two ring-ports

on two separate modules (east and west).

Equipment shall support the following protection schemes in single-node inter-

connections-

• SNCP ring <–> SNCP ring.

• SNCP ring <–> MS-SPRing.

Two-Node Overlapping Rings

This topology connects two rings using a

single fiber between two optical modules.

At each interconnecting node there are

three optical ports: two east and a shared

west. Each ring shares the bandwidth of

the west port.

Equipment shall support the following protection schemes in two-node overlapping

ring interconnections:



- 31 -


Node-2

Node-1

Figure 4: Two-node interconnected rings

Two-Node Interconnected Rings

This topology uses four trunk ports in each node to connect two separate rings.

The east and west port of each ring must be on two separate modules.

Equipment shall support the following protection schemes in two-node ring

interconnections:



4.4 Resilience & Protection

4.4.1 Network Protection

The equipment shall provide configurable SNC/N path-protection at VC12, 3 & 4

hierarchical levels, in accordance with ITU-T Rec. G.841 at all STM-1, 4, 16 & 64

traffic interfaces. All electrical STM-1, optical STM-1, STM-4, STM-16 & STM-64

traffic ports shall participate in any combination of SNCP schemes as per ITU-T

Rec. G.841 configured by LCT/EMS. Traffic ports participating in the protection

schemes shall belong to same or different modules. The STM-16 and STM-64 traffic

ports/interfaces shall also participate in 2-fibre MS-SPRing protection as per ITU-T

Rec. G.841. A multiple of MS-SPRings at STM-16 interface (with 16 STM-1

equivalent tributaries) shall be terminated on the equipment subject to matrix

capacity constraints. Similarly, a multiple of SNC rings at STM-1, STM-4, STM-16

and STM-64 tributary ports shall be terminated by the equipment subject to matrix

capacity.

It shall be possible to provide SNC/N protection to all/selected tributaries

(emanating from a node) or no protection may be provided, at all, to any of the

tributaries. Similarly, there shall be provision for configuring selective/no

protection to individual multiplex-sections in a ring (aggregate & tributary rings) as

- 32 -


well as to various VCn’s within a multiplex-section. Such protection configurations

shall be possible through EMS/LCT.

The details for the equipment ports to provide support for network protection

mechanisms are:

SDH Layer

• Linear MSP for STM-1, STM-4 and STM-16 interfaces

• 2-fibre MS-SPRing with configurable E-NUT capability for STM-16 and STM-64

interfaces

• AU4/AU3/TU3/TU12 (1+1) SNCP protection at STM-1, STM-4, STM-16 and STM-64

interfaces in accordance with ITU-T Rec. G.841 with ‘Non-intrusive’ as well as

optional ‘Inherent’ monitoring’.

The following nesting (combination) of network protection switching shall be

supported:

• Nesting of a linear (1+1) MSP with SNCP for any order of VC i.e., VC4, VC3 &

VC12.

• Nesting of 2-fibre MS-SPRing with SNCP for any order of VC i.e., VC4, VC3 &

VC12.

• The equipment shall support termination for a multiple of SDH rings. Ring inter-

working and/or dual-homing shall be supported via ‘drop & continue’

functionality as described in clause no. 4.8.2 of the GR. The manufacturer shall

ensure MS-SPRing protection interworking with other vendors’ equipment.

MAC Layer

• In addition to SDH level protection; there shall also be configurable RSTP

protection @IEEE 802.1s, offered to packet traffic at MAC layer.

• The layer-2 protection shall be configurable through LCT & EMS per Ethernet

user-flow.

4.4.1.1 Multiplex Section Shared Protection Ring (MS-SPRing)

The equipment shall support the MS-SPRing @STM-64 and STM-16 interfaces,

applicable to the ring topology as defined in the ITU-T Rec. G.841 with two-fibre

working. In MS-Shared Protection Rings, the working channels shall carry ‘normal’

traffic while the protection channels shall be reserved for protection of this

traffic. The traffic shall be transported bi-directionally. The granularity of

- 33 -


protection shall be VC4. The configurable E-NUT capability for running extra traffic

on protection channels shall also be provisioned.

The equipment shall support the facility of disabling/enabling the MS-SPRing

feature for specific STM-N sections from the Network Manager of EMS.

4.4.1.2 Sub-Network Connection Protection Non- Intrusive (SNC-N)

SNC-N scheme shall be provided at -

1) VC-4 level

2) VC-3 level

3) VC-12 level.

This protection is applicable for ring configuration using two fibres. The container

generated from a PDH interface is mapped to form two virtual containers. Each of

these two containers has the same data payload and is independently transmitted

in both directions of transmission around the network. At the receiving end

multiplexer, both the VCs are received and monitored and the VC with better

performance is selected and de-mapped to the container level. As both the VCs are

continuously monitored the switch can switch the de-mapping process to the

second VC in the event of a signal failure or signal degradation of the selected VC.

It shall be possible to configure the network as fully protected network, partially

protected network and unprotected network via EMS. The purchaser may exercise

option for SNC-I protection.

4.4.2 Equipment Protection

The equipment shall support MSP [1+1] protection for all STM-N interfaces. It shall

be at user’s discretion to ask for it or not. The inter-connection of an expansion-

chassis to main-chassis, if any, shall compulsorily provide [1+1] protected

redundant connectivity.

All common cards e.g., control/processor, switching-matrix [SDH], timing-source,

power-supply etc., are envisaged as (1+1) hot-standby protected as per conditions

laid-down in clause 1.15 in PART II of the GR.

4.4.3 Protection Switching Time for MS-SPRing

In a ring (less than 1200 kms. in length) with no extra traffic and all nodes in the

idle-state (i.e. no detected failures, no active automatic or external commands,

and receiving only Idle K-bytes), the switch (ring and span) completion time for a

failure on a single-span shall be less than 50ms. On rings under all other conditions,

- 34 -


the switch completion time might exceed 50ms marginally (the specific interval is

under study) to allow time to remove extra-traffic, or to negotiate and

accommodate coexisting APS requests.

4.4.4 Protection Switching Time for SNC

The protection switching for LO-VCs and HO-VCs shall be completed within 50ms.

Protection switch completion time excludes the detection time necessary to

initiate the protection switch and the hold-off time.

4.5 System Restoration

The equipment shall provide system restoration as follows:

§ It shall identify the failures in the connected route by monitoring SDH Overhead

bytes.

§ It is recommended that there shall be end to end SNC protection in a mesh

network topology.

§ The memory shall be non-volatile to avoid any loss of data in case of total

system-failure. The restoration of the network shall be supported by the

management system offered with the equipment. The cross-connection map

shall acquire back its pre-failure condition after restoration of faults.

4.6 Traffic interfaces in M-ADM/ADM/TM configuration

It shall be possible to configure system to support the following types of SDH, PDH,

SAN and Ethernet payloads –

1. STM-64o (as part of STM-64 MS-SPRing/SNC aggregate ring)

2. STM-16o (as a point to point tributary or part of a STM-16 MS-SPRing/SNC ring)

3. STM-4o (as a point to point tributary or part of a STM-4 SNC ring)

4. STM-1o and STM-1e (as a point to point tributary or part of STM-1 SNC ring)

5. 34.368Mbps/DS-3 (44.736 Mbps) [auto-sensed or configurable]

6. 2048 Kbps PDH interface

7. Ethernet interface 10/100BaseT Cat-5 UTP

8. Ethernet interface 100BaseFX @1310nm single-mode interface.

9. Ethernet interface 1000BaseSX multi-mode interface optional.

10. Ethernet interface 1000BaseLX @1310 nm single mode interface.

11. Ethernet interface 1000BaseLH @1310nm single-mode interface.

12. Fibre Connection (FICON) SAN interface

13. Enterprise Systems Connection (ESCON) SAN interface

14. Fibre Channel (FC) SAN interface

15. Digital Video Broadcasting - Asynchronous Serial Interface (DVB-ASI) interface.

- 35 -


Note 1: Subscript “e” stands for electrical interface and “o” stands for optical.

Note 2: Use of 1310nm window shall be permitted at STM-1o, STM-4o & STM-16o tributary

interfaces for shorthaul applications. The purchaser is to indicate exact

application-code requirements for optical tributary interfaces.

4.7 Cross-Connect Capability

The STM-64 Synchronous Multiplexer shall provide cross-connect capability with a

granularity of VC-4, VC-3 and VC-12 bit rates. It shall be possible to provide

dynamic cross-connectivity between any hierarchical VC to any other VC at same

hierarchical-level across STM-64 aggregate ring as well as across terminating STM-

16 rings, STM-4 and STM-1 rings (terminated on tributary ports) in flexible and non-

blocking manner. Similarly, there shall also be possible provisioning between

tributary to tributary ports for all VC hierarchies, subject to capacity constraints.

The lower-order (LO) VC-3 and VC-12 cross-connect granularity shall be

implemented using an integrated approach i.e., using cross connections at VC-4,

VC-3 and VC-12 in the same equipment in single-stage. Equipment implementation

with two-stage cross-connection shall be liable for rejection. It shall be possible to

switch any VC-12/VC-3/VC-4 from any physical port to any other VC-12/VC-3/VC-4

of any physical port irrespective of whether is tributary port or aggregate port. The

granularity of switching shall be minimum VC-12.

The equipment shall implement the cross-connect size as-

As an ADM

§ 256x256 VC-4 equivalents at VC-4 hierarchical level i.e., a total of 512 VC-4s :

HOVC.

§ 128x128 VC-4 equivalent at VC-12 and VC-3 hierarchical level i.e., a total of 256

VC-4s, 256x3 VC-3s or 256x3x63 VC-12s : LOVC.

Each port in the above description is assumed as unidirectional and hence shall be

configured for any direction of transmission (TX or RX). The particular VC-4’s

granular up to VC-12 and VC-3 shall be dynamically configured out of all possible

STM-N’s in the system including aggregate (for both East & West) as well as

tributary ports through EMS. A total of 128 nos. bi-directional VC-4s, from ‘West’ &

‘East’ directions, shall be available for flexible termination physically in form of

E1/E3/DS3s as well as Ethernet & SAN tributaries and/or a mix of them.

• The TUs, in the ‘east’ port, the TUs in the ‘west’ port in aggregate ring as well as

the signals in the tributary ports shall be flexibly cross-connectable subject to

- 36 -


matrix capacity. This will facilitate rearrangement of TUs on the main STM-64

routes, thereby permitting efficient capacity utilisation.

• In addition, the equipment in ADM configuration shall support "Drop-and-Continue"

or "Broadcast" capability, where the connection of one TU to a tributary interface

will not restrict its continuation along the main STM-N route.

• The equipment shall also support local cross-connect capability between tributary

interfaces without having any interconnection with STM-N signals. This capacity

shall be subject to matrix capacity for such cross-connections at tributary level.

This is intended for remote provisioning of leased -line services.

4.8 Type of connections on SDH path-layer

The equipment shall provide support for the following types of connections:

4.8.1 Bi-directional connection

Bi-directional connections shall provide connectivity in both directions of flow of

signals at VC12, VC3 and VC4 for point to point applications. This shall be used for

normal two-way transmission of traffic.

4.8.2 ‘Drop & Continue’ connection

The equipment shall provide ‘Drop & Continue’ mode of connection where the

signals received from one port shall be dropped at a port and continued via a third

port, as per requirement, for onward transmission. Such configuration shall be

possible through management system control. This feature shall be provisioned

@VC12, VC3 and VC4 levels.

The ‘drop and continue’ channels may also be aggregated using VCAT to form a

‘drop & continue’ GFP-encapsulated point-to-multipoint VCAT packet transport.

4.8.3 Unidirectional Broadcast connection

The unidirectional broadcast connection shall support point to multi-point

transmission of the same signal. It shall be unidirectional. This type of connection

shall be suitable for video transmission applications. This feature shall be

provisioned @VC12, VC3 and VC4 levels.

The equipment shall also support aggregation of one or more unidirectional

broadcast connections using VCAT to form a Broadcast packet transport.

- 37 -


4.9 Loop-backs at SDH and MAC Layers

The equipment shall be capable of providing local as well as remote user-

configurable (transparent as well as non-transparent) loop-backs at the interface

ports, at the input of the matrix as well as at the output of the matrix. There shall

be no limitations on the loop-backs and the loop-backs at AU-4, AU-3, TU-3, TU-12,

VC-4, VC-3 & VC-12 levels shall be possible. It shall be possible to control/manage

the loop-backs using local craft terminal and EMS of the system.

There shall also be capability to provide loop at MAC layer for all Ethernet ports

(both local and remote loop-backs). The equipment shall also be capable for

necessary VLAN swapping for realizing a MAC layer loop for measurement purposes

through the equipment.

5.0 System Requirements

5.1 Synchronisation

The synchronisation of the system shall be done in accordance with ITU-T Rec.

G.783. The synchronisation network shall be based on Primary Reference Clock. The

internal and holdover-mode clock interfaces shall meet the timing requirements the

option-1 of ITU-T Rec. G.813. The SDH Equipment Clock (slave clock) shall meet the

requirements related to the SDH equipment as per ITU-T Rec. G.781 as well as Rec.

G.813.

5.1.1 Synchronisation References

The synchronisation references shall be in accordance with ITU-T Rec. G.783. The

SDH equipment Terminal Multiplexers, Add/Drop Multiplexers shall have provision of

deriving the timing references from the following types of inputs apart from its

internal oscillator-

1. Incoming STM-64 line.

2. Incoming STM-16 signal.

3. Incoming STM-4 signal.

4. Incoming STM-1 signal

5. External clock at 2048 KHz as per ITU-T Rec. G.703.

6. External clock at 2048 Kb/s as per ITU-T Rec. G.703.

It shall be possible for user to select minimum three timing-reference signals and

their priority shall be set through management software. The equipment shall

generate Timing Marker and shall be able to transfer it to other nodes via ‘S1’ byte

in the Section-Overhead.

- 38 -


In the event of selected reference-timing as mentioned above is lost, the SDH

equipment shall switch-over to next priority reference timing within 300ms to

1800ms.

It shall be possible to provide both manual and automatic-reversing timing-signal

through software. The WTR period for automatic reversing shall be as per ITU-T Rec.

G.781.

5.1.2 Frequency Accuracy

The frequency accuracy of the internal oscillator of the SDH equipment in free-

running condition shall be ±4.6 ppm (The test time shall be minimum 24 hours).

5.1.3 Hold-over mode accuracy

The holdover mode short term and long term accuracy shall be as per ITU-T Rec.

G.813.

5.1.4 Clock bandwidth

The clock bandwidth shall be in the range of 1~10 Hz as specified in ITU-T Rec.

G.813 for internal clock and hold-over mode and as per ITU-T Rec. G.812 for transit-

node and local-node clock.

5.1.5 Frequency pull-in and pull-out range

The minimum pull-in and pull-out range shall be ±20ppm for hold-over mode and

internal clock. For transit and local-node clocks it shall be as per ITU-T Recs. G.812

& G.813.

5.1.6 Timing output interface

The SDH equipment shall provide minimum two Timing-Output interfaces. One of

them shall be at 2048KHz and the other one at 2048Kbps, both per ITU-T Rec. G.703,

for external synchronisation. The output specifications shall conform to ITU-T Recs.

G.812 & 813 as applicable.

5.1.7 Specification of clock ports

The specification of the input and output port for 2048KHz shall be as under:

5.1.7.1 Specifications of 2048 KHz clock interface

5.1.7.1.1 Specification at input port

The received digital signal presented at the input port shall be modified by the

characteristics of the interconnecting cable. The attenuation of this cable shall be

assumed to follow √f law and the loss at a frequency 1024KHz shall be in range 0 to

6dB.

Return loss at the input port shall be >15 dB.

- 39 -


5.1.7.1.1.1 Jitter and wander specifications

The input jitter tolerance and input wander tolerance of holdover/internal clock

shall be as per ITU-T Rec. G.813. For transit and local node clocks it shall be as per

ITU-T Rec. G.812.

5.1.7.1.2 Specification at output port

The output port shall meet the specification as given in Table 11/ITU-T Rec. G.703

and shall meet the mask given in figure 20/ITU-T Rec. G.703. The port impedance

shall be 120Ω .


The output jitter and wander shall be as per ITU-T Rec. G.813 for holdover/internal

clock, and for transit as well as local node clocks shall be as per ITU-T Rec. G.812.

5.1.7.2 Specification of 2048 Kb/s interface

5.1.7.2.1 Specification at input port

The received digital signal presented at the input port shall be modified by the


assumed to follow √f law and the loss at a frequency 1024 KHz shall be in range 0 to

6 dB.

Return loss at the input port shall be as follows:


The jitter and wander at the input port shall be as per ITU-T Recs. G.812 and G.813

as applicable.

5.1.7.2.2 Specification of output port

The output port shall meet the specification as given in Table 7/G.703 and shall

meet the mask given in figure 15/G.703. The port impedance shall be 120Ω .

Return loss at the input port shall be as under:


The jitter and wander at the output port shall be as per ITU-T Recs. G.812 and G.813

as applicable.

Frequency range (KHz) Return Loss (dB)

51-102 12 102-2048 18

2048-3072 14

Frequency range (KHz) Return Loss (dB)

51-102 6 102-3072 8

- 40 -


5.1.8 Tributary Re-timing [optional requirement]

The equipment shall provide E1 tributary re-timing option w.r.t. local STM-N as-

1. Separate E1 IO card for re-timing option or;

2. Same card with per-E1 retiming configuration.

The specifications at the input port and output port shall be same as clause 5.1.7 as above.

5.2 Maintenance, Performance Monitoring and Alarm Signals

a) ITU-T designated overhead bytes shall provide in-service monitoring. Major alarm

signals such as Loss of Signal (LOS), Loss of Frame (LOF), and Loss of Pointer (LOP)

resulting in Alarm Indication Signal (AIS) are required to be transmitted downstream.

In response to different AIS signals, Remote Defect Indication (RDI)/Enhanced

Remote Defect Indication (E-RDI) as applicable is sent upstream. The remote

indication operation such as REI & RDI and AIS generation shall be as per Appendix II

of ITU-T Rec. G.806. The generation of Enhanced RDI shall be in accordance with

Appendix VII of ITU-T Rec. G.783. The generation of Signal Failure and Signal

Degradation shall be as per Appendix IV of ITU-T Rec. G.806.

The defects, anomalies, correlation, restoration, performance monitoring and

consequent actions shall be as defined in ITU-T Recs. G.783 and G.806. The detail of

alarms is as given in clause 5.2.1 PART II of the GR.

b) Performance monitoring at each level in the maintenance hierarchy is based on

Bit- Interleaved-Parity (BIP) checks calculated on frame by frame basis. These BIP

checks are inserted in the Overheads associated with the Section and Path. Errors

detected in the Higher Order (HO) Path and Lower Order (LO) Path BIPs cause the

respective Remote Error Indication (REI) signals to be sent upstream. The REI

generation and transmission shall be in accordance with Appendix III of ITU-T Rec.

G.806. It shall be possible to assign the programmable threshold to performance

monitoring mechanisms such as B1err, B2err, B3err and BIP-2err. The programming

of threshold shall be from 1 in 104 to 1 in 109 through software.

c) Details for section-level and path-level maintenance & performance monitoring

and signals provided by various byte functionalities shall be as specified in ITU-T

Rec. G.707.

d) The parameters to be monitored in the system shall be as given in ITU-T Rec.

G.783.

- 41 -


5.2.1 Alarms

It shall be possible to monitor the following alarms and consequent actions via EMS &

LCT of the equipment. For the classification of the alarms as

critical/major/minor/deferred shall be provisioned by different colour LEDs-

1. Loss of signal (LoS)

2. Loss of Frame (LoF)

3. RS-TIM

4. MS-AIS

5. B-2 Err*.(Excessive) 1x10¯3

6. MS-RDI

7. AU-AIS

8. AU-LOP

9. HP-UNEQ

10. HP-TIM

11. HP- RDI

12. B-3 Err. (Excessive) 1x10-3

13. LP- TU-AIS

14. LP- UNEQP

15. LP- TIM

16. TU- LOP

17. TU-LOM

18. V-5 Error*

19. LP- RDI

20. GFP alarms as per ITU-T G.7041-

§ LFD

§ CSF

§ TSF

§ EXM

§ UPM

21. TCM alarms as per ITU-T G.707-

§ Tandem Connection AIS

§ Tandem Connection Outgoing Defect Indication

§ Tandem Connection LOP failure

§ Tandem Connection RDI

22. LCAS alarms as per ITU-T Rec. G.7042.

- 42 -


5.2.2 Performance degradation counters

§ B1err, B2err, B3err, V5err § LP-REI § HP-REI § MS-REI.

The EMS equipment shall support monitoring of B-errors. Also the EMS shall support

monitoring of consequent actions due to Excessive-errors in the higher-order path

and lower- order path. On exceeding the B3 and V5 error thresholds, a remote-

error-indication (REI) anomaly shall be sent to the remote-end in the form of HP-

REI and LP-REI. Similarly, Remote Defect Indications anomalies shall also be

created due to defects at the receiving stations.

5.3 Order-wire and User-Data channel

5.3.1 Engineering Order-wire Channels

Only E1 or E2 bytes shall be used to provide order-wire channels for voice

communication between stations. No other byte shall be used for order-wire

applications. The order-wire shall have the facility of selective-calling. The

permissibility for VoIP EOW is already spelt out in clause 1.6 in PART II of the GR.

5.3.2 Order-wire Channel Performance

The order-wire channel shall be 64 Kb/s PCM channel (or emulated over IP for VoIP

EOW) and shall comply with performance requirements laid down in ITU-T Rec.

G.712.

5.3.3 User-Data Channels

5.3.3.1 F1 Byte

The F1 byte shall provide 64 Kb/s data channels for Path Layer user applications.

The physical interface for F-1 byte shall be RS-232/V.11/G.703.

5.3.3.2 F2 byte (Optional requirement)

The F2 byte shall provide 64 Kb/s data channels for Path Layer user applications.

F2 byte may also be used to map DCC information.

The interface for F-2 bytes shall be RS-232 /V.11/G.703.

6.0 Technical Specifications in details

6.1 SDH Multiplexing Structure

The SDH multiplexing structure shall be in accordance with ITU-T Rec. G.707, as

detailed in figure 6-1/ ITU-T Rec. G.707.

- 43 -


6.1.1 Multiplexing method

The equipment shall adopt the multiplexing methods for 64 nos. of AUGs into STM-

64 frame as per ITU-T Rec. G.707.

The various multiplexing options of Virtual Containers into STM-N and their position

in STM-64 frame shall be as per ITU-T Rec. G.707.

6.1.2 Pointer Applications

The equipment shall provide the pointer generation and pointer interpretations as

per Para 8/ G.707. The pointer shall accommodate the phase difference of VCn

and the SOH as well as differences in the frame rates. The equipment shall process

STM-16 AU-pointer, AU-4 pointer, AU-3 pointer, AU pointer of other mapped

tributaries - TU-3 pointer and TU12 pointer etc., (as applicable) as specified in

Para 8/ ITU-T Rec. G.707.

6.1.3 Section Overhead

The SOH shall be added to the payload to create an STM-16 signal. The SOH

information shall further be classified in to Regenerator Section Overhead RSOH

and Multiplex Section Overhead MSOH. The termination of Regenerator Section

Overhead shall be done at the Regenerator and Multiplexers; whereas the

termination of Multiplex Section Overhead shall only be done at Multiplexers.

The Section Overhead and its various functions shall follow the recommendations

given in Para 9/ ITU-T Rec. G.707.

6.1.4 Regenerator Section Over-Head (RSOH)

The Regenerator Section Overhead shall provide the following bytes as per ITU-T

Rec. G.707-

A1, A2 : Framing bytes

J0 : Regenerator-Section trace byte

B1 : BIP-8 , error monitoring byte

E1 : Engineering Order-wire byte

F1 : User channel byte

D1, D3 : 192 Kbps Regenerator-Section DCC bytes

6.1.5 Multiplex Section Over-Head (MSOH)

The Multiplex-Section Overhead shall provide the following bytes as per ITU-T Rec.

G.707-

B2 : BIP-Nx24, Error Monitoring bytes

K1, K2 : Automatic Protection switching, APS bytes

- 44 -


D4, D12 : 576 Kbps Multiplex-Section DCC bytes

E2 : Engineering Order-wire bytes

S1 : Synchronization Status Message byte

M1 : Multiplex Section Remote Error Indication byte

Z0 : Spare byte

The STM-16 Section Over-Head shall be as per figure 9-4/ITU-T Rec. G.707.

6.1.6 Virtual Container POH

Two categories of Virtual Container POH shall be supported by the SDH equipment.

6.1.6.1 Higher Order Virtual Container POH: VC-4/VC-3 POH

The VC-4 and VC-3 POH shall be located in the first column of the container VC-4

and VC-3 POH shall be as under-

J1 : Path trace byte

B3 : Path BIP8 byte

C2 : Signal Label byte

G1 : Path Status byte

F2 : Path User Channel byte

H4 : Position Indicator byte

F3 : Path User Channel byte

K3 : Automatic Protection Switching Channel byte

N1 : Network Operator TCM byte

6.1.6.2 Lower Order Virtual Container POH: VC-3/VC-12 POH

VC12 POH shall be as follows-

V5 : Error Monitoring byte

J2 : Path trace byte

N2 : Network operator TCM byte

K4 : Automatic Protection Switching byte

The exact function for K3, K4 shall be as decided by ITU-T but the equipment shall

support K3 & K4 bytes.

6.2 Mapping of Tributaries into Virtual Containers (VCs)

The accommodation of asynchronous and synchronous tributaries as defined in ITU-

T Rec. G.702 shall be possible. The equipment shall support asynchronous mapping

of 2Mbps, 34Mbps/DS3 PDH signals into their respective VCs as specified in Para

10/ITU-T Rec. G.707.

- 45 -


Also the equipment shall support byte synchronous mapping of 2048 Kb/s signals.

The system shall support TUG-3 structured multiplexing chain to form AU-4.

6.2.1 Information payload

The payload structure shall be organised in accordance with ITU-T

Recommendations given in Para 6.2.2/ITU-T Rec. G. 707.

6.2.2 Maintenance signals

The maintenance signals shall be as per Para 6.2.4/ITU-T Rec. G.707.

6.2.3 Tandem Connection Monitoring

The system shall support the Tandem Connection Monitoring at VC4 and VC4-Xc

level as per ITU-T Recs. G.707, G.783 and G.803, using N1 byte in Higher Order

Path. The path performance degradation and path failure alarms shall be provided

as per ITU-T Rec. G.707.

6.2.4 Concatenation & Encapsulation mechanisms

6.2.4.1 Contiguous Concatenation

The equipment shall support contiguous concatenation @VC4 level as specified in

Para 11.1/ITU-T Rec. G.707. The system shall support termination of VC4-4c, VC4-

16c interfaces and their cross-connection as well. The system shall provide an

optional capability for translation of a contiguous concatenated payload in to a

VCG (and vice-versa).

6.2.4.2 Virtual Concatenation

The equipment shall support virtual concatenation at VC12, VC3 and VC4 levels as

specified in Para 11.2/ITU-T Rec. G.707. The details of VCG shall be as per clause

6.5.4 in PART II of this GR.

6.2.5 Generic Framing Procedure

The equipment shall support the encapsulation of Ethernet and other higher-layers

clients’ data through GFP-Framed as well as GFP-Transparent as specified in ITU-T

Rec. G.7041. Preferably, the system shall provide per Ethernet port selection for

either GFP-F or GFP-T (as applicable). However, separate Ethernet cards for both

GFP encapsulations shall also be permitted.

6.2.6 Link Capacity Adjustment Scheme

The equipment shall support Link Capacity Adjustment Scheme as specified in ITU-

T Rec. G.7042. The addition/deletion of VCn’s from a VCG shall be hitless.

Implementation of LCAS in the system shall not introduce/contribute additional

latency in the data path.

- 46 -


6.2.6.1 LCAS requirements

LCAS signalling between peers shall be carried in the SDH path overhead as

outlined in ITU-T Recs. G.7042 and G.707. The following LCAS capabilities shall be

supported.

§ Basic LCAS Operation

§ LCAS and 1+1 Path Protection

§ LCAS Group Identifiers

§ Asymmetric LCAS

§ LCAS inter-working.

The LCAS feature specified above shall be applicable to all Virtually Concatenated

payloads configurable through EMS/LCT.

6.2.6.2 Asymmetric LCAS

Asymmetric LCAS arises when an LCAS-enabled VC bundle is configured with

different bandwidth in each direction. Equipment shall correctly transmit and

receive Ethernet data when some (but not all) of the members of the bundle are

unidirectional paths.

In addition, the equipment shall correctly transmit and receive Ethernet data when

some (but not all) of the members of the bundle are bi-directional paths that have

failed in only one direction.

6.2.6.3 LCAS Inter-working

When two nodes use virtual concatenation for a network connection, it shall be

possible that one side is configured to use LCAS on the connection, and the other

side is not (or does not support LCAS). That is, when a node is using LCAS on a VC

bundle (i.e. LCAS configuration is enabled), it shall send LCAS control-messages. If

a node does not receive any LCAS control messages, it shall assume that the peer is

not using LCAS.

6.3 Ethernet Service requirements

The following services shall be offered-

Point-to-Point Dedicated (P2PD)

A point-to-point dedicated service shall map Ethernet traffic into one transport

path and transport the traffic to another Ethernet interface on the far end. There

is no aggregation at either side of the network. Alternatively, the Ethernet traffic

from one port can be mapped on a module to another. The P2PD service is used to

offer dedicated Ethernet Private Line services.

- 47 -


Point-to-Point Shared (P2PS)

A point-to-point shared service shall map Ethernet traffic from multiple Ethernet

interfaces on one Ethernet IO module into one transport path and shall transport

the traffic across the network to another Ethernet module. The P2PS service is

used to offer “Ethernet Virtual Private Line” services.

Internet Access Service (IAS)

An Internet access service shall allow multiple subscribers access the hub-site

router for Internet access. This service shall aggregate traffic in two locations: at

the subscriber side and at the hub-site. On the subscriber site, the node shall

statistically multiplex Ethernet traffic from multiple Ethernet ports on the same

card onto a transport path. At the hub-site, the node shall statistically multiplex

traffic from multiple transport paths onto one single Ethernet interface. The IAS

service is used to offer shared Ethernet access to Internet services.

Transparent LAN Service (TLS)

A transparent LAN service shall allow multiple Ethernet devices in multiple

locations to appear as a single private LAN (virtual LAN or VLAN). Each device shall

attach to an Ethernet port on an individual node. Each node shall connect to

another node in a point-to-point or linear-chain topology. Each Ethernet device

can exchange data with any other device on the LAN with the same virtual

identifier (VLAN). The transparent LAN services can be configured for individual

customers (separate Ethernet devices) but shall share the trunk bandwidth

between nodes.

Apart from the same, there shall be support for point to point, point to multi-point

as well as multi-point to multi-point services on all Ethernet ports in accordance

with ITU-T & MEF standards, as defined previous and subsequent clauses in the GR.

6.3.1 Layer 2 Service Implementation Requirements

The equipment shall support VCAT/GFP over any of the SDH interfaces in the

equipment, and shall aggregate the packet traffic through packet-switching

subsystem (Ethernet MAC), and encapsulate the packet traffic within

GFP/VACT/LCAS channels and forward the same over various STM-N interfaces in

the system. This mechanism shall provide significant efficiency while transporting

data through the SDH network through the following features:

1. Right sizing the VCAT pipe for point to point Ethernet-Lines (EPL, EVPL etc.)

services.

- 48 -


2. Right sizing the VCAT pipe for multi-point to multi-point Ethernet-LAN (EPLAN,

EVPLAN etc.) services.

3. Idle packet suppression – only packets containing customer data shall be

transported through the ‘egress’ interface. This is to reduce the capacity

requirements of the ‘egress’ interfaces, number of such ‘egress’ interfaces, and

the capacity requirements on the Router interfaces that connect to the

equipment for further service creation.

4. Statistical multiplexing with SLA shall facilitate the purchaser to offer data

services at multiple QoS classes with different SLA contracts.

6.3.1.1 Service QoS Implementation

6.3.1.1.1 Fixed-rate Point to Point Ethernet Private Line service

Point to point data private-line service shall be offered through right-sized

GFP/VCAT with guaranteed bandwidth between the two end points.

6.3.1.1.2 Burtsable Ethernet Private Line & LAN service

Burtsable Ethernet Private Line & LAN service is a service instance wherein traffic

from multiple Ethernet user-ports shall be aggregated using 802.1Q & 802.1ad

defined Q-in-Q and transported through VCAT/GFP, for shared private line & LAN

services. This shall be an overbooked service. The devices shall offer layer-2 traffic

management and OAM features, such as port-rate limiting, ingress policing,

troubleshooting etc. The SLA (service level agreements) for such services shall

include CIR (Committed Information Rate), EIR (Excess Information Rate), COS

(upto 4 classes of service) with 802.1P classification.

This service shall facilitate node-based over-subscription. Thus bandwidth

allocation between two SDH nodes on a ring shall be allocated permanently (for

example STM1-2v), and traffic from multiple Ethernet customers shall be

multiplexed with CIR/EIR (as configured) overbooking through VCAT path.

6.3.1.1.3 Additional layer 2 service attributes

§ The system shall provide layer-2 encapsulation and forwarding through MPLS

using PWE3 as per RFC-3916 & IETF draft Martini draft-ietf-pwe3-ethernet-

encap-09.txt and related drafts. [optional requirement]

§ Solid demarcation point between provider and customer, in the form of MEF

UNI1.0. Per customer unique identifiers for SLA monitoring and service

identification. [optional requirement]

§ Ethernet OAM&P support for connectivity verification across the network, and

within the network.

- 49 -


§ IEEE 802.3ad link aggregation and protection on service and trunk ports.

6.3.2 Layer 2 functionality details & specifications

In order to realise the above-mentioned services, there shall be in-built layer-2

bridging & aggregation functionality as per IEEE 802.1D in the system. The

implementation for the same is described in clause 6.3.3. There shall be support

for VLAN stacking (Q-in-Q) per IEEE 802.1ad on all ports. The users shall be

identified based on MAC address/Physical port of arrival/VLAN-ID (C-VLAN) @IEEE

802.1q, as configured. There shall be customer and provider MAC address

separation and learning.

The transport-side VLAN (S-VLAN) shall be configured through LCT/EMS. For

Ethernet Virtual Private Lines (EVPL) & Ethernet Virtual Private LAN (EVPLAN)

services, multiple Ethernet user-ports shall share a configured VCG between two

points. The VCG selection shall be autonomous based on VLAN-ID, MAC based, and

port based which shall be configured through EMS & LCT. The VCG selection may

also be pre-configured through EMS. The purchaser shall convey exact

requirements. Also there shall be provision for non-shared VCAT bandwidths

against specific Ethernet ports which shall be used for Ethernet Private Lines (EPL).

Either the support for EPL, EVPL, EPLAN, and EVPLAN services shall be configurable

per Ethernet port on a common IO card or standalone Ethernet IO cards shall be

provided for shared and dedicated access.

The service requirements of MEF and ITU-T Recs. G.8010, G.8011, G.8011.x series

shall be complied for Ethernets services. Some of the service implementation

details are given in the following sections. Exact details regarding VLAN

administration for connectivity services are outlined in Appendix II of the GR.

Ethernet Private Line/LAN service

Each Fast Ethernet port shall be configured with a backhaul bandwidth VC12-Xv

where X=1 to 46 against a particular port, configured through EMS/LCT. The

support for VC3-Xv where X=1-2, shall be optional to purchaser’s requirements.

Similarly each GigE port shall be configured with a backhaul bandwidth VC4-Xv

where X = 1 to 7 configured through EMS/LCT. The virtual concatenation shall be

implemented in accordance with ITU-T Rec. G.707 at VC12, VC3 (optional) & VC4

and shall be configurable through EMS/NMS/LCT for each Ethernet port.

Virtual Private Line/LAN service

Same as for Ethernet Private Line/LAN service but with the following additional

requirements-

- 50 -


The system shall perform layer-2 aggregation of the Ethernet user-flows sensitive

to the C-VLAN’s carried in the terminated Ethernet flows at Ethernet user ports.

There shall be VLAN-based VCAT selection through EMS, for backhaul. Various

Ethernet flows across multiple Ethernet user-ports on an IO card with specific C-

VLAN shall be aggregated and backhauled through a configured VCAT group (VCG).

The QoS requirements are already spelt out before.

6.3.2.1 Details of Ethernet interface provisioning

The equipment shall support a minimum of 8 nos. of 10/100BaseT cards in ADM

mode. This assumes 8 nos. Fast Ethernet ports per IO card. Similarly, the

equipment shall support a minimum of up to 4 Gigabit Ethernet ports in ADM mode.

In case, no. of Ethernet ports supported per card is more, the quantity of Ethernet

IO cards shall go down accordingly.

6.3.3 Layer-2 Switching/Aggregation Implementation

The GR envisages layer-2 aggregation for Fast Ethernet interfaces and for Gigabit

Ethernet interfaces. Some of the possible provisions for Ethernet interfaces are-

1. IO cards with multiple Fast Ethernet (recommended minimum 8 ports for this

GR’s compliance) and one or more Gigabit Ethernet ports each.

2. Separate IO cards for Fast & Gigabit Ethernet interfaces.

The equipment shall implement layer-2 aggregation as a centralised switch.

However, implementation of layer-2 switch at Ethernet IO card-level shall also be

acceptable provided inter-IO card cross-connections at MAC layer are possible. In

case of MAC switch-fabric failure on one IO card, the system shall bridge local

Ethernet user traffic to a MAC switch fabric for layer-2 processing on a backup IO

card through autonomous arrangements.

In case of IO card level layer-2 aggregation, there may be a common backup IO

card provided, with redundancy in (N:1) mode for all Fast Ethernet IO cards and

Gigabit Ethernet IO cards (provision option #2 as above). Similarly, there may be a

common backup IO card provided, with redundancy in (N:1) mode for all

Fast+Gigabit Ethernet IO cards (provision option #1 as above). The switch-fabric

capacity shall be as specified for a Gigabit Ethernet IO card (in case it is a

standalone card – refer provision option #2).

In such case, the configurations for the Ethernet traffic (for the IO card on which

MAC switch failure has occurred) shall be maintained. In case of layer-2

aggregation at IO card-level, the layer-2 switch-fabric for individual Fast Ethernet

- 51 -


IO cards shall be minimum 2.4Gb/s (assuming 8 Fast Ethernet ports per IO card).

The capacity shall increase on pro-rata basis if the number of Fast Ethernet ports is

more than 8 per IO card. If provided as combined 8 FE+1GigE per IO card, it shall

implement minimum 4.8Gb/s MAC switch-fabric. If there are standalone Gigabit

Ethernet IO cards, it shall provide a minimum of 6Gb/s MAC fabric.

The equipment shall support a minimum of 64 nos. of Fast Ethernet interfaces in

ADM mode & 32 nos. Fast Ethernet interfaces in TM mode. There shall be provision

in the system to provide up to 4 nos. of Gigabit Ethernet interfaces in ADM mode.

There shall be minimum 2 Gigabit Ethernet ports per GigE IO card.

The manufacturer shall ensure support for at least 1000BaseLX and LH @1310nm

interfaces. 1000BaseSX multi-mode interfaces shall be optional to purchaser’s

requirements. The purchaser shall communicate exact interface requirements for

1000BaseSX/LX/LH.

The switch fabric requirements in case of centralised MAC switch implementation

shall be 2.4*8 + 2*6~ 30Gb/s for ADM mode (for standalone cards for Fast & Gigabit

Ethernet) and 4.8*8 ~ 36Gb/s for combined Gigabit Ethernet IO card. There shall be

a hot-standby redundant MAC switch of equal capacity for failures.

The aggregated Ethernet traffic from central layer-2 switches or IO cards

(depending upon implementation) shall be encapsulated using GFP techniques and

mapped onto SDH payload through virtually concatenated VCn’s (VCGs) with

configurable LCAS implementation.

Note: The description of Ethernet switch-fabric considers each of the TX and RX direction

of an Ethernet interface as separate for calculation of switch-fabric. The TX & RX

direction of a Gigabit Ethernet interface is taken as equivalent of 1Gb/s in

calculating the fabric capacity. Similarly, each of the TX & RX direction of a Fast

Ethernet interface is taken as equivalent of 100Mb/s in calculating the fabric

capacity. And an over-subscription ratio @2:1 is assumed. According to this

description methodology, one GigE user-interface necessitates provision of 3Gb/s

MAC switch-fabric and similarly one Fast Ethernet interface necessitates provision

of 300Mb/s MAC switch-fabric.

6.3.3.1 Bridging specifications

1. VLAN IEEE 802.1Q support on all ports

2. VLAN priority IEEE 802.1P support on all ports

3. IEEE 802.1s RSTP support on all ports

4. IEEE 802.1ad Q-in-Q on all ports

- 52 -


5. IEEE 802.3ad LAG on all trunk ports for aggregation up to 4 ports.

6.3.3.2 Bandwidth granularity

@64kbps Fast Ethernet with rate limiting per port through LCT & EMS.

@1Mbps GigE with rate limiting per port through LCT & EMS.

6.3.4 Ethernet Provisioning – VCAT details

The Ethernet interface provisioning is envisaged through Ethernet interface cards.

In Ethernet Private Lines E-LINE/LAN E-LAN applications, a bandwidth in the

form of a Virtual Concatenated Group (VCG), VCn-Xv where n=12, 3 & 4 shall be

provided at the backhaul of these Ethernet interfaces as per the following details:

Fast Ethernet 10/100BaseT & 100BaseFX

§ VC12-Xv where X=1 to 46 and,

§ VC3-Xv where X=1 to 2 (optional to purchaser’s requirements).

Gigabit Ethernet 1000BaseSX/LX/LH

§ VC4-Xv where X=1 to 7 and,

§ VC3-Xv where X=1 to 21 (optional to purchaser’s requirements).

The bandwidth, so provisioned, for a particular Ethernet port shall be indicated

through GUI on

the NMS/EMS (or LCT) server as well as shall be available in printable format for

Service Level Agreement (SLA) obligations & for QoS certification.

Note: The unutilized bandwidth after Ethernet backhaul applications shall not be

blocked for other tributary applications.

6.4 Network Node Interfaces - Details

There shall be three types of Network Node Interfaces, namely-

1. SDH interfaces

The SDH interfaces for STM-1o, STM-4o, STM-16o and STM-64o shall conform to

ITU-T Recs. G.957 and G.783 and STM-1e shall conform to ITU-T Rec. G.703. The

shorthaul application code S 16.1, S 4.1 and S 1.1 shall be sufficient for SDH

interfaces at STM-16o, STM-4o and STM-1o respectively, for compliance to this

GR.

2. PDH interfaces

The 2Mbps, 34Mbps/DS-3 PDH electrical interfaces shall be compliant to ITU-T

Rec. G.703.

- 53 -


3. Ethernet on SDH interfaces

The equipment shall support IEEE 802.3 standard 10/100BaseT, 100BaseFX,

1000BaseSX* (optional), 1000BaseLX and 1000BaseLH (at 1310nm) single-mode

Ethernet interfaces for transport of over SDH in accordance with ITU-T Rec.

G.7041 (GFP). The provision for 1000BaseSX shall be optional to purchaser’s

requirements.

4. Transparent SAN interfaces

The equipment shall support Storage Area Network (SAN) interfaces - FC, FICON,

ESCON and DVB-ASI video interface. The encapsulation of SAN data shall be as per

GFP-T mode, specified in ITU-T Rec. G.7041.

6.5 Window of Operation

1550nm as per ITU-T G.957/G.691.

6.6 Optical Line Interface : STM-64 interface

The optical line interfaces are required to provide the interface between two line

equipments connected by an optical path, with possible intermediate

regeneration, if needed. It is intended to achieve transverse compatibility within

any signal in the optical-section. The equipment shall meet the optical interfaces

specifications @ S 64.2a or S 64.2b (on G.652 fibre) and S 64.5a or S 64.5b (on

G.655 fibre) at 1550 nm as per ITU-T Rec. G.691. The target distances supported

by this optical interface shall be 40kms. approximately based on ITU-T assumption

of fibre attenuation @ 0.275dB/Km. at 1550nm with a span loss of 11dB.

Note The distances are meant for classification only, and not for specification purpose.

The actual coverable distances will depend on the attenuation & dispersion

characteristics of the fibre.

6.7 Digital Signal

The STM-64 line shall be in accordance with ITU-T Recs. G.691, G.707 and G.783.

6.7.3 Nominal bit-rate

The nominal bit-rate in the synchronised mode shall be in accordance with ITU-T

Rec. G.811. The nominal bit rate in the free-running mode shall be as follows.

STM-64 9953.280Mb/s ± 4.6ppm (nominal).

- 54 -


6.7.4 Optical parameters

The optical parameter values for the specified application-code shall meet the

requirements given in ITU-T Rec. G.691 for the system operating wavelengths

specified therein.

6.7.5 Receiver Sensitivity

The values given in ITU-T Rec. G.691 against minimum sensitivity of receiver at

reference point "R" are worst case end-of-life EOL values for long haul

application. The beginning-of-the-life BOL values are specified to be 2-4dB

better than the given values in above referred tables.

6.7.6 Eye pattern

The shape of the optical pulse of the transmitter at reference point ‘S’, shall

conform to the eye pattern mask as given in ITU-T Rec. G.691.

Type of connectors

FC-PC/SC/LC connectors shall be provided at FDF/ODF end. In case, other than

FC-PC connectors viz., LC, SC, etc., are provided at the equipment-end, suitable

adapters/patch-cords etc., shall be provided by the manufacturer as an integral

part of the offer.

6.8 Jitter and Wander Performance

Jitter requirements for optical for optical interfaces at STM-64 level shall be as

given in Para15/ITU-T Rec. G.783. The STM-64 wander parameters shall be per

ITU-T Rec. G.813.

6.8.3 SDH interfaces - Jitter and Wander

The jitter and wander specifications of SDH interfaces at STM-64 aggregate level

shall be as per ITU-T Recs. G.783, G.825, G.811 and G.813 as applicable.

6.8.3.1 Jitter and Wander Generation

The output jitter and wander shall meet short-term stability as specified in table

6/ITU-T Rec. G.813 and table 7/ITU-T Rec. G.813. Further, the equipment shall

meet the jitter and wander limits as specified in ITU-T Rec. G.783.

6.8.3.2 Jitter and Wander Transfer

The jitter and wander transfer function of an SDH regenerator shall be under the

curve given in ITU-T Rec. G.783, when input sinusoidal jitter up to the mask level

specified in ITU-T Rec. G.783, is applied. The jitter and wander transfer

guidelines shall be as per Para 15/ ITU-T Rec. G.783.

- 55 -


6.8.3.3 Jitter and Wander Tolerance

SDH Terminals, ADM and regenerators shall meet the jitter tolerance

specifications given in ITU-T Rec. G.783, with reference to figure 15.2/ITU-T Rec.

G.783 with parameters specified for various types and bit rates.

6.8.3.4 Transfer of wander encoded in AU and TU pointer adjustments

Shall conform to Para 10.1.4/ ITU-T Rec. G.783.

6.9 Optical Tributary Interfaces

6.9.3 STM-16 optical interface

The STM-16 interface shall be in accordance with ITU-T Recs. G.957, G.707 and

G.783.

6.9.3.1 Nominal bit-rate

The nominal bit-rate in the synchronised mode shall be in accordance with ITU-T

Rec. G.811. The nominal bit rate in the free-running mode shall be as follows.

STM-16 2488.320 Mb/s ± 4.6ppm (nominal).

6.9.3.2 Optical parameters

The optical parameter values for the specified application code shall meet the

requirements given in table 4/ITU-T Rec. G.957 for system operating wavelengths

specified therein. The definitions of the various parameters are as given in Para

6/ITU-T Rec. G.957.

6.9.3.2.1 Receiver Sensitivity

The values given in the table 4/ ITU-T Rec. G.957 against minimum sensitivity of

receiver at reference point "R" are worst case end-of-life EOL values for long

haul application. The beginning-of-the-life BOL values are specified to be 2-4dB

better than the given values in above referred tables.

6.9.3.2.2 Eye pattern


conform to the eye pattern mask as given in Figure 2/ITU-T Rec. G.957.

Type of connectors

FC-PC/SC/LC connectors shall be provided at FDF/ODF end. In case, other than

FC-PC connectors viz., LC, SC, etc., are provided at the equipment-end, suitable


part of the offer.

- 56 -


6.9.3.3 Jitter and Wander Performance


given in Para15/ITU-T Rec. G.783. The STM-16 wander parameters shall be per

ITU-T Rec. G.813.


The STM-4 line signal shall be as per ITU-T Recs. G.707 & G.783.

Nominal bit-rate 622.080 Mb/s±4.6ppm (Nominal)

The STM-4 tributary signal shall be in accordance with ITU-T Recs. G.707 & G.783.

The nominal bit rate in the synchronized mode shall be traceable to ITU-T Rec.

G.811. The nominal bit-rate in the free-running mode shall be 155.520Mb/s +/-

4.6ppm.

6.9.4.1 Optical Parameters

The STM-4o traffic interfaces shall meet optical interface specifications for short-

haul inter-office application, S 4.1, as per ITU-T Rec. G.957 in 1330nm window

using ITU-T Rec. G.652 single mode fibre. However, S 4.2 application as per ITU-T

Rec. G.957, in 1550nm window, shall also be acceptable.

Note: However, the purchaser may demand other ITU-T Rec. G.957 application codes

i.e., long-haul inter-office applications in 1330nm and/or 1550nm window using

ITU-T Rec. G.652 single-mode fibre, @L 4.1 & L 4.2 respectively.

6.9.4.1.1 Eye Pattern Mask


conform to the eye pattern mask as given in figure 2/ITU-T Rec. G.957.

Type of connectors

FC-PC/LC/SC connectors shall be provided at FDF/ODF end. In case, any other

type of connectors viz., LC, SC etc., are provided at the equipment, suitable


part of the offer.


The receiver sensitivity values for the specified application-code shall meet the

requirements given in table-4/ITU-T Rec. G.957, as reproduced at the end of the

GR, for the system operating wavelengths specified therein. All values specified in

the table are end-of–life EOL values. The beginning of the life BOL values shall

- 57 -


be specified 2-4dB better than the given values. Receiver sensitivity shall be

provided as per S1.1 application at 1310nm or S1.2 at 1550nm application.



given in ITU-T Rec. G.783. The STM-4 wander parameters shall be per ITU-T Rec.

G.813.


The STM-1 line signal shall be as per ITU-T Recs. G.707 & G.783.

Nominal bit-rate 155.520 Mb/s.

The STM-1 line signal shall be in accordance with ITU-T Recs. G.707 & G.783. The

nominal bit-rate in the synchronized mode shall be traceable to ITU-T Rec. G.811.

The nominal bit- rate in the free-running mode shall be 155.520Mb/s +/- 4.6ppm.

6.9.5.1 Optical Parameters

The STM-1o traffic interfaces shall meet optical interface specifications for short-

haul inter-office application, S 1.1, as per ITU-T Rec. G.957 in 1330nm window

using ITU-T Rec. G.652 single mode fibre. However, S 1.2 application as per ITU-T

Rec. G.957, in 1550nm window, shall also be acceptable.

Note: However, the purchaser may demand other ITU-T Rec. G.957 application codes

i.e., long-haul inter-office applications in 1330nm and/or 1550nm window using

ITU-T Rec. G.652 single-mode fibre, @L 1.1 & L 1.2 respectively.

6.9.5.1.1 Eye Pattern Mask


conform to the eye pattern mask as given in figure 2/ITU-T Rec. G.957.

Type of connectors

FC-PC/LC/SC connectors shall be provided at FDF/ODF end. In case, any other

type of connectors viz., LC, SC etc., are provided at the equipment, suitable


part of the offer.


The receiver sensitivity values for the specified application code shall meet the

requirements given in table 4/ITU-T Rec. G.957, as reproduced at the end of the

GR, for the system operating wavelengths specified therein. All values specified in

the table are end of life values. The beginning of the life values shall be specified

- 58 -


2-4dB better than the given values. Receiver sensitivity shall be provided as per

S1.1 application at 1310nm or S1.2 at 1550nm application.



given in ITU-T Rec. G.783. The STM-1 wander parameters shall be per ITU-T

G.813.

6.9.6 STM-1 Electrical Interface

6.9.6.1 General Characteristics

The interface requirements for STM-1 tributary interface shall be as per Para 12/

ITU-T Rec. G.703.

Nominal bit rate : 155520 kb/s

Tolerance : ± 20ppm

Code : CMI (Code Mark Inversion)

Over-voltage protection : ITU-T Rec. K.41.

6.9.6.1.1 Specifications at the input ports

The digital signal presented at the input port should conform to table 11/ ITU-T

Rec. G.703 and figures 22 & 23/ITU-T Rec. G.703 modified by the characteristics

of the interconnecting coaxial pair. The attenuation of the coaxial cable should

be assumed to follow an approximate √f law and to have a maximum insertion loss

of 12.7dB at a frequency of 78 MHz. The return loss characteristics should be the

same as that specified for the output port.

6.9.6.1.2 Specifications at output ports

The specifications at the output port are given as below and as per figures 22 &

23/ ITU-T Rec. G.703.

Return Loss : ≥ 15 dB over freq. range 8 MHz to 240MHz.

6.9.6.1.3 Specifications at the Cross-Connect Points

The signal power level and eye diagram requirements shall be as specified in Para

15.4/ ITU-T Rec. G.703.

Type of connector: BNC/Spinner/SMA/SMB.

6.9.6.2 SDH interfaces - Jitter and Wander

Refer clause 8.1.2.3 in Part II of TEC GR No.: GR/SDH-10/02.MAR.2005 for STM-4

Synchronous Multiplexer.

- 59 -


6.10 PDH Tributary Interfaces

6.10.3 34 Mb/s Electrical Tributary Interface

The Interface requirements for the 34 Mb/s Tributary Interface shall be as per

ITU-T Rec. G.703.

6.10.3.1 General characteristics

Bit rate 34368 Kb/s ± 20ppm

Code HDB3.

6.10.3.2 Specification at output ports

The specification at output ports are given as below and as per figure 17/ITU-T

Rec. G.703.

(a) Pulse shape Nominally rectangular and conforming to the masks shown in Figure 17/ ITU-T Rec. G. 703, irrespective of sign.

(b) Pairs in each direction One coaxial pair (c) Test load impedance 75 ohms resistive (d) Peak voltage of a mask (pulse) 1.0 V ± 10% (e) Peak voltage of a space (no pulse) 1.0 V ± 10%

(f) Nom. pulse width 14.55 ns

(g) Ratio of the amplitudes of positive and negative pulses at the centre of a pulse interval

0.95 to 1.05

(h) Ratio of the width of positive and negative pulses at nominal half amplitude

0.95 to 1.05

Note: Refer to Figure 17 / ITU-T Rec G. 703 for (b) to (h) above.

Return Loss

The Return loss at output port shall be as follows-

Frequency Range (kHz)

Return Loss (dB)

860 to1720 6

1720 to 51550 8


6.10.3.3 Specifications at the input ports

The digital signal presented at the input port should conform to table 8/ITU-T

Rec. G.703 and figure 17/ITU-T Rec. G.703 modified by the characteristics of the

interconnecting coaxial pair. The attenuation of the coaxial cable should be

assumed to follow an approximate "square root of f" law and to have a maximum

insertion loss of in the range of 0 to 12 dB at a frequency of 17184 KHz.

The Return loss at the input port shall be as follows-

Frequency range Return Loss

860 KHz to 1720 KHz >12dB

- 60 -


720KHz to 34368 KHz >18dB

34368 to 51550KHz >14 dB

6.11 2 Mb/s Electrical Interface

The Interface requirements for the 2 Mbps Tributary Interface shall be as per ITU-

T Rec. G.703.

6.11.3 General Characteristics

Bit rate : 2048 kb/s ± 50 ppm

Code : HDB3.

6.11.4 Specification at the input ports

The digital signal presented at the input port shall be modified by the


assumed to follow √f law and the loss at a frequency 1024 KHz shall be in the

range 0 to 6 dB.

Return loss at the input port shall be as follows:

Frequency Range (kHz) Return Loss (dB)

51.2 KHz to 102.4KHz >12dB

102.4KHz to 2048 KHz >18dB

2048KHz to 3072KHz >14dB

6.11.5 Specification at output ports

The specifications at the output port are given as below and as per figure 15/ ITU-

T Rec. G.703.

Frequency Range (kHz) Return Loss (dB)

51 to102 6

102 to 3072 8

Type of connector

Wire-wrapping type, the wire-wrapping pin should be able to take wire 0.6 mm

diameter. Alternatively IDC type or D-type terminations shall also be acceptable.

The wire diameter in the case of IDC and D-type termination shall be min. 0.5 mm

diameter. The crimping tool and a minimum of 20m connection-cable shall be

supplied as an integral part of the offer.

6.12 44.736 Mb/s Electrical interfaces (DS-3)

The electrical interface of 44.736 Mb/s shall be as per clause 8 of ITU-T Rec.

G.703. The card for DS3 interface must be software configurable as a 34Mb/s card

- 61 -


to accept a 34Mb/s PDH signal as defined in ITU Rec. G.703. The electrical

interface for 34Mb/s signal shall be in accordance with ITU Rec. G.703 and the

multiplexing of 34 Mb/s signal to SDH hierarchy shall be as per ITU Rec. G.707.

Nominal line rate : 44. 736 Mb/s

6.12.3 Line-rate accuracy

In a self-timed, free-running mode, the line-rate tolerance shall be ±895bits/s (±

20ppm) or better.

6.12.4 Line code

B3ZS (bipolar with three-zero substitutions).

6.12.5 Frame structure

The signal shall have the frame structure defined in ITU-T Rec. G.752.

6.12.6 Medium

Unbalanced coaxial line shall be used for each direction of transmission.

6.12.7 Test load impedance

Unbalanced 75 ohms coaxial line shall be used for each direction of transmission.

6.12.8 Pulse shape

The shape of every pulse that approximates an isolated pulse (is preceded by two

zeros and followed by one or more zeros) shall conform to the mask in Figure 14

of ITU Rec. G.703. See clause 5.2 of ITU Rec. G.703 for allowable procedures to

be followed in checking conformance. This mask includes an allowance of ±3% of

the peak pulse amplitude at any point on the mask relative to the pulse mask in

the earlier version.

6.12.9 Power level

A wideband power measurement of an AIS signal (as defined in Recommendation

G.704) using a power level sensor with a working frequency range of 200 MHz

shall be between −4.7 dBm and +3.6dBm, including the effects of a range of

connecting cable lengths between 68.6 meters (225 feet) and 137.2 meters

(450 feet). A low-pass filter having a flat pass-band and cut-off frequency of

200 MHz shall be used. The roll-off characteristics of this filter are not

important;

or

an alternate power level specification of the power of an all-ones signal (Note 2/

ITU Rec. G.703) is useful for some equipment qualifications. It requires that the

power in a 3 kHz ± 1 kHz band centred at 22,368 kHz be between −1.8dBm and

- 62 -


+5.7 dBm. It further requires that the power in a 3 kHz ± 1 kHz band centred at

44,736 kHz be at least 20dB below that at 22 368 kHz.

6.12.10 Pulse imbalance

1. The ratio of amplitudes of positive and negative isolated pulses shall be

between 0.90 and 1.10.

2. Positive and negative isolated pulses shall both conform to the mask of

Figure 14/ ITU Rec. G.703.

6.12.11 DC power

There shall be no DC power applied at the interface.

6.12.12 Verification access

Access to the signal at the interface shall be provided for verification of signal

specifications.


6.12.13 PDH interfaces

6.12.14 Jitter and Wander – 2/34Mbps

6.12.14.1 Input Jitter and Wander Tolerance

The input jitter and wander tolerance shall be as per ITU-T Rec. G.823.

6.12.14.2 Jitter and Wander Transfer characteristics

The jitter and wander characteristics shall be per ITU-T Rec. G.823.

6.12.14.3 Jitter and Wander Generation

6.12.14.3.1 Jitter and Wander from tributary mapping

Jitter and wander from the tributary mapping shall be as specified in ITU-T Rec.

G.783.

6.12.14.3.2 Jitter and Wander from pointer adjustments

Jitter and wander from pointer adjustments shall be as specified in ITU-T Rec.

G.783.

6.12.14.3.3 Combined Jitter & Wander from tributary-mapping and pointer adjustments

Combined jitter and wander from tributary mapping and pointer adjustments shall

be as per ITU-T Rec. G.783.

6.12.15 DS-3 interface - Jitter and Wander

6.12.15.1 Maximum permissible jitter tolerance

The maximum permissible jitter tolerance shall be as per table-1/ITU-T Rec.

G.824.

- 63 -


6.12.15.2 Output wander

The wander at the output of interface shall not exceed the limits as specified in

table-3/ITU-T Rec. G.824.

6.12.15.3 Input jitter and wander tolerance

Input jitter and wander transfer characteristics shall be as per table-11 of ITU

Rec. G.824 and figure 9/ ITU-T Rec. G.824.

6.13 Ethernet over SDH (EoS) interface

The Ethernet services and implementation requirements have already been spelt

out in clauses 6.2 and 6.3 in PART II of the GR. The equipment shall support

Ethernet over SDH at 10/100BaseT, 100BaseFX@1310nm Fast Ethernet and

1000BaseSX (multi-mode) optional, 1000BaseLX & LH (both at 1310nm) Ethernet

interfaces in accordance with ITU-T Rec. G.7041 (GFP-F) encapsulation.

Ethernet tributaries (at electrical level) shall be terminated on Ethernet tributary

cards or extended to IO cards after termination at common termination panel,

using RJ-45 connectors with UTP Cat.5 cable or any other appropriate

international standard cable. International industry optical connectors shall be

provided for optical Ethernet ports.

Type of connector

Ethernet tributaries shall be terminated on Ethernet tributary cards using RJ-45

connectors with UTP Cat.5 or any other appropriate international standard cable

for respective Ethernet interfaces, e.g., 10/100BaseT at electrical interface. The

optical Ethernet connector shall be carrier-grade as per internationally industry

standard. The Ethernet interface termination may be either provided directly on

the IO cards at RJ-45/optical termination or may be terminated and extended to

IO cards through backplane.

Note: The exact nos. of 10/100BaseT, 100BaseFX, 1000BaseSX, 1000BaseLX and

1000BaseLH Ethernet interface cards shall be as per requirements of the

purchaser.

6.13.1 Ethernet Adapters: (Optional)

Ethernet Adapter shall be optionally provided for installation at Customer and

Central office ends as per networking requirements.

- 64 -


Figure 5: Ethernet Adaptor

The both side connectors and connecting patch-cords shall be the part of Ethernet

Adapter. # The purchaser may specify 10BaseT also.

6.13.2 Transparent SAN interfaces

6.13.2.1 Fibre Connection (FICON) interface

The payload and physical interface related requirements of Fibre Connection

interface shall meet the requirements of ANSIX3.230 and the mapping of Fibre

Connection payload shall transparently be done in accordance with ITU-T Rec.

G.7041. The type of coding, alarms, error handling mechanism and payload integrity

requirements shall be as per ITU-T Rec. G.7041.

6.13.2.2 Enterprise Systems Connection (ESCON) interface

The payload related specifications of Enterprise Systems Connection (ESCON) SAN

interface shall as per ANSIX3.296 and the mapping of the data shall be in

accordance wit ITU-T Rec. G.7041. The type of coding, error-handling mechanism,

alarms and payload integrity requirements shall be as per ITU-T Rec. G.7041.

6.13.2.3 Fibre Channel (FC) interface

The payload and physical interface related requirements of Fibre-Channel (FC) SAN

interface shall meet the requirements of ANSIX3.230 and the mapping of the data

shall be as per ITU-T Rec. G.7041. The type of coding, error-handling mechanism,

alarms and payload integrity requirements shall be as per ITU-T Rec. G.7041.

6.13.2.4 Digital Video Broadcasting - Asynchronous Serial Interface (DVB-ASI) interface

The payload and physical interface related requirements of DVB-ASI interface

requirements shall as per ANSIX3.230 the mapping of the data shall be as per ITU-T

Rec. G.7041. The type of coding, error-handling mechanism, alarms and payload

integrity requirements shall be as per ITU-T Rec. G.7041.

7.0 Mechanical standards

1. The equipment shall be housed in the standard sub-racks preferably 19'' width

or ETSI standard rack. The sub-rack/chassis shall be fitted with motherboard

duly masked to avoid short-circuiting. The sub-rack shall have protruded

impressions on the top and base-plate of sub-rack assembly to act as built-in

guides known as “CNC guide forming” for holding the PCBs in the sub-rack. The

Ethernet Adapter

IEEE 100Base FX To Central Office

IEEE 10/100BaseT

- 65 -


back and forth movement of PCBs shall be very smooth without any significant

play towards the sideways.

2. The guides in the sub-rack shall be made with CNC machines/tools. In case of

CNC tool being used to make guides, in order to maintain the accuracy, the

technique adopted shall use a single DIE punching. The plastic guides shall not

be permitted.

3. In order to avoid bending/sagging of top and base-plates during transportation,

installation and maintenance process, the metal-sheet used for these plates

shall be minimum 1.2 mm in thickness for mild-steel material, 1.5 mm for

Aluminium material and in case of stainless-steel material; the thickness of

metal-sheet shall be 1.0 mm.

4. The connectors used on the PCB and their mating connectors on the mother-

board shall have tight grip to avoid jacking problems. The connectors used shall

be professional grade telecom connectors of international industry standards.

(Euro-type or better).

5. The slots for interfaces in the sub-rack shall be universal, supporting any type

of PCBs in any position except for common control, matrix and line cards. No

damage shall take place to PCBs when loaded in the wrong slot except in

power-supply unit slots. The PCBs shall have the provision of locking/screwing

to the sub-rack.

6. The input/output terminations of tributary signals shall either follow extended

mother-board using connectorised connections or directly from proper

connectors at the mother-board.

7. The termination of 2048 Kb/s signals in each case shall adopt wire-wrapping,

IDC, D-type connectors. No soldering for connections shall be permitted. There

shall be proper covers on the sub-racks/main-racks or similar arrangements to

avoid the ingress of dust.

8. The height of main-rack shall be strictly as per this document till specified

otherwise. The main-rack shall be made from metal-sheet of minimum 2.0

mm thickness and shall be covered from three-side minimum, with top and

base covers. The thickness of the back-covers shall be 1.0 mm minimum. The

base-plate of the main-rack shall be 2.0 mm minimum.

9. The main-rack shall have adequate provision of holding/fixing the sub-racks in

their positions. It shall be ensured that there is no lateral movement of sub-

- 66 -


racks when fitted in main-rack. The main-rack shall have the proper fixing

arrangements on floor, preferably with a base-plate and expansion-bolts etc.

The thickness of base-plate shall be minimum 2.0 mm. The main-rack supplied

with equipment shall be uniform in size irrespective of the loading of the

equipment for all consignments by the manufacturer.

10. The manufacturer shall specify the mechanical standard of racks and sub-racks

in their manual and shall maintain the size and standard of racks, sub-racks,

connectors etc., during supply of the equipment. The main-rack shall have

sufficient space preferably in the sideways for running the input out cabling

etc. This shall specifically be ensured during the testing, field trial and QA of

the equipment.

11. The permanent wiring such as distribution of power-supply and grounding etc.

shall be pre-wired. During the testing and supply of the equipment the racks

and sub-racks quality supplied by the manufacturer shall be ensured.

12. The front opening of the sub-rack/main-rack is envisaged. No rear-side/side-

way opening shall be permitted. The access to data terminations shall be from

the front side only.

8.0 Minimum equipment for testing

One complete wired set of equipment with all functionalities as outlined in the GR

with equipped traffic interfaces [as follows in this clause] in a wired-rack for full

capacity of the equipment shall be offered for testing. An EMS/LCT loaded with

software along with test jigs and test & measurement instruments shall also be

offered to facilitate the testing.

Full-wired rack STM-16 interfaces STM-4 interfaces

STM-1e, o interfaces 2Mbps interfaces 34/DS-3 interfaces 10/100BaseT interfaces 100BaseFX @1310nm interfaces

1000BaseSX* interfaces 1000BaseLX @1310nm interfaces 1000BaseLH @1310nm interfaces EMS LCT

Test jigs, instruments & instrumentation * optional to purchaser’s requirements.

- 67 -


Interfaces to be offered for testing

Minimum 3 ADM nodes shall be offered for TAC testing with the loaded interfaces as follows-

STM-64 interfaces 2 nos. STM-16 interfaces 4 nos. STM-4 interfaces 20 no. STM1o interfaces 48 nos. STM-1e interfaces 16 nos. E1 tributary interfaces 63 nos. E3/DS3 tributary interfaces 3 nos. Ethernet 10/100BaseT interfaces 32 nos. Ethernet 100BaseFX at 1310nm 32 nos. 1000BaseSX*interfaces 2 nos. 1000BaseLX at 1310nm interfaces 2 nos. 1000BaseLH at 1310mn interfaces 2 nos.

Note: Each unit in above description infers a module providing one interface each for both

directions of traffic.

9.0 Field Trial

The equipment shall be subjected to field-trial for a minimum of 4 weeks with

working traffic. The equipment shall be loaded with maximum possible live-traffic

for the entire system capacity & the balance with simulated traffic to assess the

performance of the equipment.

_______________

- 68 -


ANNEXURE I ITU-T Parametric Tables

- 69 -


Tx

Rx

40 Kms.

Figure 1 – Schematic diagram for a STM-64 short-haul link.

- 70 -


Table 1/G.691 - Parameters for STM-64 optical interfaces

Unit S64.2a S-64.5a Transmitter at reference point MPLS Operating wavelength range Mean launched power -maximum -minimum Spectral characteristics -maximum-20dB width -chirp parameter , α -maximum spectral power density -minimum SMSR Minimum EX Main optical path, MPI-S to MPI-R Attenuation range -maximum -minimum Chromatic dispersion -maximum -minimum Passive dispersion compensation -maximum -minimum Maximum DGD Min ORL of cable plant at MPI-S, including any Connectors Maximum discrete reflectance between MPI-S and MPI-R Receiver at reference point MPI-R Minimum sensitivity (BER of 1*10-12)

Minimum overload Maximum optical path penalty Maximum reflectance of receiver, measured at MPI-R

nm

dBm dBm

nm Rad

mw/MHz dB dB

dB dB

ps/nm ps/nm

ps/nm ps/nm

ps dB

dB

dBm dBm dB dB

1530 -1565

-1 -5

0.1 * *

30 8.2

11 7

800 700

0 0

30 24

-27

-18 -8 2

-27

1530 -1565

-1 -5

0.1 * *

30 8.2

11 3

130 110

0 0

30 24

-27

-17 -8 1

-27

- 71 -


Table 2 – Parameters specified for STM-16 optical interfaces ITU-T/G.957

Unit Values

Digital signal

Nominal bit rate

kbit/s

STM-16 according to Recommendation G.707

2 488 320

Application code (Table 1) I-16 S-16.1 S-16.2 L-16.1 L-16.2 L-16.3

Operating wavelength range nm 1266a)-1360 1260a)-1360 1430-1580 1280-1335 1500-1580 1500-1580

Transmitter at reference point

‘S’ -

Source type MLM SLM SLM SLM SLM SLM

Spectral characteristics:

– maximum RMS width (σ) nm 4 – – – – –

– maximum –20 Db width nm – 1 < 1b) 1 < 1b) < 1b)

– minimum side mode

– suppression ratio

dB – 30 30 30 30 30

Mean launched power:

– maximum dBm −3 0 0 +3 +3 +3

– minimum dBm −10 −5 −5 −2 −2 −2

Minimum extinction ratio dB 8.2 8.2 8.2 8.2 8.2 8.2

Optical path between S and R

Attenuation rangec) dB 0-7 0-12 0-12 10-24e) 10-24e) 10-24e)

Maximum dispersion ps/nm 12 NA b) NA 1200-1600b),d) b)

Minimum optical return loss of

cable plant at S, including any

connectors

dB 24 24 24 24 24 24

Maximum discrete reflectance

Between S and R

dB −27 −27 −27 −27 −27 −27

Receiver at reference point R

Minimum sensitivityc) dBm −18 −18 −18 −27 −28 −27

Minimum overload dBm −3 0 0 −9 −9 −9

Maximum optical path penalty dB 1 1 1 1 2 1

Maximum reflectance of receiver,

measured at R

dB −27 −27 −27 −27 −27 −27

- 72 -


table 4/G.957 / ----contd.

a) Some Administrations may require a limit of 1270 nm. b) See 6.2.2. c) See clause 6. d) The indicated dispersion range corresponds to the approximate worst-case dispersion for 80 km G.652/G.654 fibre over the

wavelength range 1500-1580 nm: manufacturers shall ensure sufficient margins to guarantee proper operation over a target distance of

80 kms. e) To meet 10 dB minimum attenuation instead of 12 dB, it will be required to decrease the maximum output power, to increase the

minimum overload, to use optical attenuators, or a combination thereof.

- 73 -


Table-3 [Parameters specified for STM-4 optical interfaces] – ITU-T G.957

Unit Values

Digital signal Nominal bit rate

kb/s

STM-4 according to Recommendation G.707 622 080

Application code (Table 1)

I-4 S-4.1 S-4.2 L-4.1 L-4.2 L-4.3

Operating wavelength range nm 1261a)-1360

1293-1334/ 1274-1356

1430-1580

1300-1325/ 1296-1330

1280-1335

1480-1580

1480-1580

Transmitter at reference point S

Source type MLM LED MLM SLM MLM SLM SLM SLM Spectral characteristics: – maximum RMS width (σ) nm 14.5 35 4/2.5 – 2.0/1.7 – – – – maximum –20 Db width nm – – – 1 – 1 < 1b) 1 – minimum side mode suppression ratio

dB – – – 30 – 30 30 30

Mean launched power: – maximum dBm −8 −8 −8 +2 +2 +2 – minimum dBm −15 −15 −15 −3 −3 −3 Minimum extinction ratio dB 8.2 8.2 8.2 10 10 10 Optical path between S and R

Attenuation rangec) dB 0-7 0-12 0-12 10-24 10-24 10-24 Maximum dispersion Ps/n

m 13 14 46/74 NA 92/109 NA b) NA

Minimum optical return loss of cable plant at S, including any connectors

dB NA NA 24 20 24 20

Maximum discrete reflectance between S and R

dB NA NA −27 −25 −27 −25


Minimum sensitivityc) dBm −23 −28 −28 −28 −28 −28

Minimum overload dBm −8 −8 −8 −8 −8 −8 Maximum optical path penalty

dB 1 1 1 1 1 1

Maximum reflectance of receiver, measured at R

dB NA NA −27 −14 −27 −14

a) Some Administrations may require a limit of 1270 nm. b) See 6.2.2 c) See clause 6.

- 74 -


Table- 4 [Parameters specified for STM-1 optical interfaces]

Unit Values Digital signal Nominal bit rate

kb/s

STM-1 according to Recommendation G.707 155 520

Application code (Table 1)

I-1 S-1.1 S-1.2 L-1.1 L-1.2 L-1.3

Operating wavelength range nm 1260a)-1360

1261a)-1360

1430-1576

1430-1580 1263a)-1360

1480-1580

1534-1566/ 1523-1577

1480-1580

Transmitter at reference point S

Source type MLM LED MLM MLM SLM MLM SLM SLM MLM SLM Spectral characteristics:

– maximum RMS width (σ)

nm 40 80 7.7 2.5 – 3 – – 3/2.5 –

– maximum −20 dB width

nm – – – – 1 – 1 1 – 1

– minimum side mode suppression ratio

dB – – – – 30 – 30 30 – 30

Mean launched power:

– maximum dBm −8 −8 −8 0 0 0 – minimum dBm −15 −15 −15 −5 −5 −5 Minimum extinction ratio

dB 8.2 8.2 8.2 10 10 10

Optical path between S and R

Attenuation rangeb) dB 0-7 0-12 0-12 10-28 10-28 10-28 Maximum dispersion

ps/nm 18 25 96 296 NA 246 NA NA 246/296 NA

Minimum optical return loss of cable plant at S, including any connectors

dB NA NA NA NA 20 NA

Maximum discrete reflectance between S and R

dB NA NA NA NA –25 NA


Minimum sensitivityb)

dBm −23 −28 −28 −34 −34 −34

Minimum overload dBm −8 −8 −8 −10 −10 −10 Maximum optical path penalty

dB 1 1 1 1 1 1

Maximum reflectance of receiver, measured at R

dB NA NA NA NA −25 NA

a) Some Administrations may require a limit of 1270 nm. b) See clause 6.

- 75 -


ANNEXURE II Ordering Instructions

- 76 -


Part I: General Requirements

Clause 1.1 Specify choice for ADM or TM.

Clause 1.13 Specify requirements, if any, for VC3 based VCGs.

Clause 1.14 Specify Ethernet/SAN interface option.

Part II: Technical Requirements

Clause 1.5.1 Specify application codes requirements for line and tributary interfaces.

Clause 4.1.1 Specify Ethernet interfaces choice.

Clause 4.4.1 Specify Inherent SNC protection requirements.

Clause 6.2.4.1 The system shall provide optional capability for translation of a contiguous

concatenated payload in to a VCG (and vice-versa). The choice may be

conveyed, if required.

Clause 6.3.2 The VCG selection shall either be autonomous based on VLAN-ID, MAC

based, port based which shall be configured through EMS & LCT or it may

also be pre-configured through EMS. The purchaser shall convey exact

requirements.

Clause 6.14.1 Ethernet media converter requirements may be spelt out.

Clause 5.1.8 Specify ‘Tributary Interface’ re-timing option.

Appendix I: EMS Requirements

Clause 2.1 The purchaser shall communicate requirements for (1+1) server backup or

internal constituents of server.

Appendix II: VLAN Administration

The purchaser shall communicate VLAN scalability requirements depending upon the deployed

network size.

- 77 -


APPENDIX I EMS Requirements

- 78 -


APPENDIX I - Part I

1.0 General Operational & Functional Requirements

1. The EMS shall be multi-user system and based on Graphical User Interface.

2. It should be possible to generate customized reports for various types of faults, performance history, security management etc. It should also be possible to generate up time-reports at 2Mbps, 34Mbps, DS-3, Ethernet, STM-1, STM-4, STM-16, STM-64 and SAN interfaces (as applicable) to facilitate monitoring of performance statistics in a pre-defined/customized format. It shall be possible to generate and define the formats at any time, based on network needs.

3. It should be possible to have a view of selected sub-networks/rings controlled by the Element Management System as per requirement. By zooming-in, it shall be possible to drill down up to module-level in each NE for configuration and fault management. The same shall be provided through user-friendly GUI commands.

4. The EMS shall be able to diagnose its own faults by running diagnostic software.

5. The Element Manager shall provide the complete view of the network elements and the interconnecting links. The EMS shall have the ability to include the network elements and the links in the visual/graphical map of the domain. The visual maps shall display the elements and the links in different colour depending upon the status of the links. It is preferable that green colour for healthy and amber/yellow colour for degraded condition and red for unhealthy condition is used.

6. It shall provide the ability to drill down to the individual element, then to subsystem, then to card and then to port level configuration template from the domain-map by clicking on the icon of the network element.

7. The Element Manager shall have suitable system level backup mechanism for taking backup of EMS data of at least one month. There shall be no magnetic tapes used for the objective, only DVD, CD-ROM shall be provided.

8. The information model shall be as per specified standards. The EMS shall support correlation (filtering and suppression) to avoid multiple alarms from a single source of failure within the sub-network. Single Alarm shall be provided for the events that are correlated and are due to a common cause.

9. The EMS shall provide the visual presentation of the Network Element’s status and the alarms. It shall also present the complete map of the network domain with suitable icons and in suitable colour like green for healthy, red for non-operational, yellow for degraded mode of operation etc.

10. It shall be possible to take any Network Element out-of-service & in-service from the EMS. It shall be possible to restart the Network Element from EMS.

11. The EMS shall carry out the systematic Health Monitoring of the elements of the Network. Check on the health of the card of any element of the Network shall be possible through command with settable periodicity - @ 24 Hrs, 1 week, 1 month.

12. It shall be possible to log recent commands and be re-displayed, and re-issued on request through GUI.

- 79 -


13. The configuration of the various network elements like creating, viewing, and editing shall be possible from the EMS. The configurations of the network elements shall also be stored at suitable place in EMS from where it can be retrieved in case of failure.

14. It shall provide the graphical layout of the network elements with modules drawn using different colours to indicate their status.

15. Manufacturer shall provide soft copy of his EMS on a CD on per-ink or per-ring basis (or as asked for by the purchaser). The setup/procedure to download the software shall be clearly mentioned in the system manual of the equipment.

16. Calendar Management

It shall be possible to execute any schedulable administrative command i.e.- NE backup, software download, performance, operator log-in/ log-out etc., at any time by attaching a time tag to the command and it shall be executed when the Network real time matches the time tag. It shall be possible to define both time and date. If no date is mentioned, the command shall be executed daily at the time indicated.

17. Messaging system

The EMS shall have a messaging system which will generate and send alert messages on telephone (fixed & mobile), e-mail or SMS to the designated personnel depending upon the location of NE, on generation of alarms..

18. It is recommended that the response time for query/command on any operator terminal, local or remote shall be 10 seconds or better. For updation on topological information on the terminals, the response time shall be better than 20 seconds under all conditions. The response time shall however, be reviewed depending upon total NE load and topology by purchaser during testing of EMS.

19. The supplier shall provide all necessary interface details (with the documents) for integration of its EMS with existing or proposed NMS (irrespective of its brand/make) and also provide time bound support for its integration, under obligation of a Non-Disclosure Agreement (NDA).

20. The supplier shall provide infrastructure requirements to the purchasers for setting up the EMS. The items of infrastructure include A/C power, Air conditioning load, space etc.

21. All critical components and units of the EMS i.e. – LAN interfaces, hard-disk, processor etc., shall be fault resilient.

22. It shall be possible to produce customized reports. The purchaser shall be free to ask for customization of reports based on the data available in the database from time to time.

23. It shall be desirable to interconnect a Disaster Recovery EMS with an existing EMS, in future, with possible manual switchover between them. The issues regarding hardware and software compatibility with regards to existing server platform shall be subject to a mutual understanding on the issue between purchaser and manufacturer.

24. Installation & commissioning of the EMS shall include supply & installation of cables, distribution frames, electrical switches etc.

25. Format for creation of database of rings, network elements, circuits, ADM/DXC/TMs etc., and their numbering scheme, details of built up points across various rings other commissioning details, supplementary information, order reference, dates etc. shall be prescribed by purchaser at the time of validation of EMS.

- 80 -


26. The purchaser shall validate all the components of EMS and features of EMS. All the instruments necessary foe carrying out validation test shall be arranged by supplier.

2.0 EMS Architecture & Server Specifications

2.1 Architecture

1. It shall be ensured that EMS connectivity to sub-network is not disrupted and there is no loss of EMS performance and fault data from the sub-network. To ensure EMS connectivity to the sub-network under control-card failure, there shall be provision to support dual-homed connectivity of EMS to two Gateway NEs (GNEs) in a sub-network. The performance and fault data for the sub-network shall be available even if the master control-card at one GNE fails. In case of total loss of EMS connectivity, the sub-network shall continue to provide the services without any deterioration.

2. In case of total loss of EMS connectivity, it is recommended that the performance data of the NE shall be stored in the controller card, and shall be sent to central EMS server upon restoration of EMS connectivity. it is recommended that 6400 performance and fault data messages containing a minimum of 100 alarms shall be stored by the system. The response time shall however, be reviewed depending upon total NE load and topology by purchaser during testing of EMS.

3. In case of loss of EMS connectivity, the LCT privilege shall remain for monitoring and for local configurations, as privileged by EMS administrator.

4. The centralized EMS may consist of standalone application server, database server and firewall server or it can be a standalone EMS server subject to scaling requirements. Any other server required for meeting the purchase requirements shall be quoted separately by the bidder.

5. LCT connectivity to EMS for privileged operation shall be through a log-in password.

6. As a cost effective measure, two display units are adequate for all the servers (application, database, and firewall servers). Purchaser is at discretion to convey any additional requirements. It shall be possible to access any server from any of the display.

7. The purchaser shall communicate requirements for (1+1) server backup or internal constituents of server.

2.2 Scalability Aspects

1. The EMS should be able to support at least 1000 NEs. The EMS application shall also be scaleable to 1000 NEs. Any more requirements may be communicated by purchaser.

2. Operating system and applications for EMS including database server shall be multi-user with minimum 25 concurrent users (including local terminals at EMS site and remote terminals i.e. LCTs). Any more requirements may be communicated by purchaser.

3. A minimum of four operator terminals will be provided at the EMS site. The EMS shall be equipped to connect to at least 10 local terminals at EMS site. It shall be upgradeable to 25 local terminals. The operator terminals at the EMS site are recommended to be PC Pentium IV with 80 GB HDD, 17” video display, Ethernet interface (10/100 Mbps) with industry standard operating system UNIX/Windows but having GUI.

- 81 -


2.3 EMS Server Specifications

A ‘Telecom Grade Enterprise Server’ from a reputed national/international vendor with broad specifications, as below, shall be provided at a minimum:

The multi-process EMS design is recommended which shall enable distribution of functions over multiple processors. In addition, the RMI inter-process communication enables distribution of functions over multiple servers. Consequently, increasing system capability can be achieved by upgrading the existing platform (e.g. adding CPUs) or adding new servers into the cluster. The manufacturer shall indicate limitations regarding processing requests, notifications, updates, Network-map view refreshing etc., in the supplied system.

Both Application and Database servers shall have UNIX based operating system.

The EMS shall be supplied with a Work Station offering Graphical User Interface (GUI) using 17” colour screen with key board and Mouse etc. The Work Station shall be of latest type of machine with very high processing speed as available on the date of procurement of equipment. The Work Station shall support Ethernet ports as 10BaseT, 100BaseT. The operating system shall be Windows 2000 or XP. The specifications are given in clause 2.7 of the Appendix I.

2.4 Application Server Specifications

The EMS application server shall multi-server based (with at least the two servers [1+1] to begin with), with each server having multi-processor (at least 2 processor), at least 1.5 GHz clock, 8 GB RAM, 512 KB cache memory, 80 GB HDD with CD-ROM/DVD-ROM, Ethernet LAN interfaces floppy drive, and shall operate in high availability cluster mode. However, the purchaser may choose single server as per network needs. Exact specifications may be issued by purchaser.

2.5 Database Server Specifications

The database server shall be multi-server based (desired with 2 servers for redundancy) each with 4 processors and expandable to minimum 8 processors, RISC based 64 bit system with at least 1.5 GHz clock, 8 GB RAM and one GB Cache memory. However, the purchaser may choose single server as per network needs. The system disc shall be 80 GB with OS and RDBMS mirroring 20/40 GB DAT drives shall be provided as back up devices. The system shall support at least 6X DVD for loading of software and configuration. The system shall have Hard-disk storage implemented on RAID 0, RAID 1, RAID 0+1 and RAID 5 architecture of Disk Storage which shall be site configurable. The RAID system shall be hardware based and shall have redundant Fibre based RAID controller. The Hard-Disk storage shall provide for no single point of failure. The server will operate in high availability cluster mode, on load sharing basis. Any alternate specifications may be issued by purchaser.

1. Database hard-disk memory shall be sufficient to store all the information as indicated in the document and any other necessary system for at least one month duration.

2. Each of the server i.e. EMS server and database server as well as firewall server shall have redundancy for control module, disk, power supply and LAN interface.

3. Industry standard relational database (RDBMS) for storing all the data related to the network and the system shall be used.

4. The database interface shall be open so that a centralized EMS at a future date is able to retrieve information from the EMS database using TCP/IP stack and do post processing. The data base structure for all the databases used in the system shall be provided.

- 82 -


5. The memory of the Database Server shall be sufficient to store the data of 1000 fully loaded equipment nodes (as per respective type/category of equipment) at a minimum. It shall be capable of storing performance/ fault history of 30 days of the network under its domain. This shall be ensured during the testing of the equipment.

2.6 Firewall Server [optional requirement]

§ In order to provide security to EMS from public networks, adual redundant hardware based Firewall system may be provided at each of the NMS locations for providing security to the various servers at the EMS. The Firewall System shall be as per TEC GR No.: GR/FWS-01. The Firewall System (FWS) shall have a capability of handling a concurrent sessions of around 20,000.

§ The Firewall System shall support 4 ports of 10/100BaseT expandable to 12 ports.

§ There shall be a common Firewall System. The firewall system shall be used for providing the security cover to the Web Based Customer Care System from the internet. The same Firewall system shall also provide the security to the EMS Database from the Internet and the Web Based Customer Care Users & the Systems.

§ The firewall shall be based on stateful connection-oriented firewalling and shall be appliance/hardware based. The firewall shall track the following parameters of each packet-source and destination address, Transmission Control Protocol (TCP) sequence numbers, port numbers and TCP flags.

2.7 Specifications for Local Crafts Terminal/Client Terminal/Work Station

The LCT desktop configuration as a PC or Laptop shall be as given below at a minimum-

§ Pentium IV 2 GHz and above § 17” Colour Monitor (for PC) and LCD/TFT display (for Laptop) § 40GB/256 MB RAM § 48X CD-ROM drive § 1.44 MB floppy drive § LAN port § Inbuilt Modem § 2 Nos. USB Ports § Printer port § Mouse port § PS-2 Keyboard port § Licensed Operating software preloaded/Recovery CDs. The Desktop/Laptop shall be supplied with the LCT software installed in it. The PC shall be from a reputed international/national PC manufacturer.

Note: No QM-333 environmental tests shall be conducted on the EMS Server/LCT PC.

- 83 -


APPENDIX I - Part II

FCAPS TEMPLATE FOR SDH TRASNMISION PRODUCTS 1.0 Network Management Functions

1.1 General Functions

The equipment EMS shall provide general management functions described in ITU-T Rec. G.784. The filters for performance and fault management shall also be as per ITU-T Rec. G.784. The other management functions as defined in ITU-T Rec. G.784 shall be as under:

1. Configuration Management 2. Fault Management 3. Performance Management 4. Security Management 5. Software Management 6. Inventory Management.

FCAPS shall be evaluated in terms of the circuits/connections which shall be identifiable in terms of ADM/TM/DXC based on addressing mechanism.

2.0 Configuration Management

The equipment EMS shall support configuration and provisioning capabilities as per ITU-T Recs. G.783 and G.784. The system shall support ‘Point & Click’ provisioning in a vendor’s sub-network, subject to clearance by Inventory Management, shall be supported as per the following configuration provisioning:

1. To partition the network as defined in ITU-T Rec. G.803 on request and control either in full or with limited network resources.

2. Network Element creation in the NE Management domain.

3. Programming of a multiple interface unit.

4. To create, update, delete and retrieve the managed network topology data.

5. Assigning the equipment protection to a unit/interface.

6. Selection of protection switching within the managed network and protection switching granularity.

7. Matrix connections.

8. Error detection thresholds.

9. Network Element configuration.

10. Software download (local & remote).

11. Protection switching enabling/disabling for individual traffic interface at virtual containers, i.e., VC4.

12. Ethernet/SAN interface bandwidth through VCAT and MAC configurations

13. Enabling/disabling of LCAS

14. Enabling/disabling of FEC (if implemented)

15. DCC multiple management configurations

16. Configuration related to multiple management options etc.

- 84 -


3.0 Fault Management

The equipment management system shall support ‘Fault Management Functions’ as described in the ITU-T Rec. G.784. The ‘Equipment Management Function’ within the Network Element shall perform a persistency check on the fault-cause, before it declares a fault causing failure. The time taken to declare the fault shall be as per ITU-T Rec. G.784. Each failure and clearance, thereof, shall be time-stamped. The atomic functions associated with the failure shall be as per ITU-T Rec. G.784.

The equipment shall do surveillance of alarms & their detection, reporting of relevant events and conditions that lead to the generation of alarm after filtering. The system shall support the alarm history as per ITU-T Rec. G.784. Further, the element management system shall support the following:

1. Path alarm notification to be generated and recorded, the alarm notification shall include: type, occurrence, severity, probable cause and clearing.

2. Path alarm shall be graphically shown by the EMS/LCT. 3. Alarm and status display. 4. Fault localization. 5. Fault correlation control. 6. Storing and processing of current alarm information, up to module/unit level. 7. Storing and processing of historical alarm information for 30 days minimum. The EMS/LCT

shall provide on-line logging capability for historical alarms and events with sufficient information such as managed resources, alarm/event type, alarm severity, day and time of occurrence etc. The retrieving functions with filtering capabilities for historical alarms and events shall be provided as well.

8. FCS errors for Ethernet clients. 9. Assigning alarm severity i.e., Critical, Major, Minor & Deferred.

4.0 Performance Management

The equipment shall support the ‘Performance Management’ functions in accordance with ITU-T Rec. G.784. The performance management shall consist of set of functions that evaluate and report on the behaviour of network element and their effectiveness relating to the communication taking place on the network. The performance management shall deal with definitions, evaluation and reporting of equipment performance.

It shall be possible to store all the performance and traffic statistics for a month. It shall also be possible to generate daily, weekly, monthly reports for the individual element as well as complete domain. The report generation shall be supported for text and graphic reports.

These functions shall be implemented using information flows at the reference points S1 & S2 and filtering functions as described in ITU-T Rec. G.783. The performance monitoring shall conform to ITU-T Recs. M.2100, M.2101, M.2120, G.821, G.826, G.828 and G.829. The near-end performance monitoring, far-end performance monitoring, performance data collection and performance history shall be as per ITU-T Rec. G.784. Performance history for minimum 30 days shall be supported with configurable launch-time and performance evaluation/integration period. The main performance functionality to be provided shall be as under:

• Configuration of threshold concerning the error counters. • Performance reporting and monitoring. • Performance history (data logging)

The EMS shall store the performance data of the sub-network in terms of configured circuits. In addition to, the following shall also be some of the different parameters that shall be stored -

- 85 -


§ The collection of the performance counters shall be performed at pre-assigned rate as per ITU-T Rec. G.784.

§ The EMS shall support configurable scheduling of the performance measurement, collection, storage and transfer of the performance statistics. It shall also support presentation of the performance statistics in graphical and text mode as and when requested and at repeated interval automatically.

5.0 Security Management

The management system shall provide adequate security to the data and for the access to the management system as per the following details:

1. The EMS shall have the capability of supporting the management of Network through local

and remote Operators. The authorizations and the privileges of the operators (Remote and Local) shall depend upon the Login and Password.

a. Low level protection for read only access to faults and performance information. b. Medium level protection for access to configuration status and features. c. High level protection for control of access to change in the configuration and control

parameters.

2. Network management security features shall include operator authentication, command, menu-restriction and operator privileges. The EMS shall support multi-level passwords as below-

a. EMS shall allow the System Administrator to define the level of access to the network capabilities or feature for each assigned password. It shall be desirable that the EMS shall block the access to the operator in case of unauthorized commands being tried for five consecutive times. Also it is desirable that the EMS shall also not allow the entry into the EMS in case wrong password is provided more than five consecutive times during the login.

b. The system administrator shall be able to monitor and log all operator activities in the EMS and Local Craft Terminal.

c. The dynamic password facility shall be provided in which the operator may change his password at any time.

3. All log-in and log-out attempts shall be logged in the security log file of the EMS system.

4. The network and the management system shall be protected against intentional or accidental abuse, unauthorized access and loss of communication.

5. The man-machine communication programs shall have the facility of restricting the use of certain commands or procedures to certain passwords and terminals.

6. The LCTs shall normally operate through the centralized EMS. Only in the case of failure of link between the LCT location and the EMS, the LCT should be able to supervise/monitor the local assigned to it.

7. It should be mandatory for the system to have a record of all log-ins for a period of at least six months after which a back up should be possible under system administrator command.

8. It shall be possible to connect EMS and the network elements to the IP-MPLS network. The EMS and components of the existing/proposed Network Management layer (NML)/Service Management Layer (SML) of a purchaser shall be part of the common MPLS-VPN providing the inherent security required for the Management information in addition to the login and Password based authorization for the operators of the Network Manager.

9. Back up for programmes and data.

- 86 -


10. The EMS shall be able to back up and restore the data base to and from external storage media;

11. External Security Measures Optional Requirements

Network security may require deployment of external devices/machines/ firm-ware at the network operation centre [NOC], like-

1. firewalls 2. access control servers 3. data encryption devices/use of PKI keys 4. anti-virus packages. 5. in the data communication network (DCN) for management system, VLAN tags/MPLS

labels may be used for security to information flows from Gateway NEs (GNEs) to DCN Gateways with IPSec, PKI security options.

The purchaser may communicate requirements as per his network security needs.

6.0 Inventory management

1. It shall indicate the absence or presence of any physical module in hardware elements. It shall also indicate the usage of module i.e. how many ports are in use, which interface is in use and which are free to be used etc.

2. The EMS shall be able to discover and keep the device information

3. The EMS shall be able to keep track on any change in the network inventory reported chronologically.

4. The EMS shall provide the inventory information to the Network Management layer (NML)/Service Management Layer (SML) so that SML is able to create and activate a service to the customer automatically. This shall also assist SML in providing the network inventory to which the SML shall add the customer identification and maintain this information in its database.

5. The EML shall be able to show inventory based on the available device inventory in terms of circuits’ utilization.

6. The EMS shall provide the complete view of the network elements and the interconnecting links.

7.0 Software Management

It shall be possible to carry out the following tasks under the software management function:

1. Loading of new system software.

2. Manage different versions of software.

3. Shall have the capability of managing multiple versions of software for individual elements. In this case, one software version shall remain active and other versions shall be passive.

4. Installation of software patches.

5. Examine contents of all system memory and disk memory.

6. At the time of downloading the software, the message shall be displayed that the software has been downloaded successfully or failed and at what stage.

7. The EMS shall support FTP/TFTP for downloading of Software, configuration, patches etc., to the Network Element.

8. The operator terminals (local & remote) shall not allow loading of any software without the terminal administrator’s authorization.

- 87 -


9. The EMS shall enable operations like changing the system configuration, reconfiguration of input and output devices, loading a new software package, etc. Both automatic and manual reconfiguration capabilities shall be available.

10. All commands which are executed over the EMS program or data shall be logged in a file (read only) and it shall be possible to retrieve the same on demand whenever required, using Man-Machine Commands. The file usage of up to 50%, 75% and 90% shall generate alerts in the server platform, of suitable category prompting the operator to initiate the backup operation.

11. It shall be possible through a single Man-Machine Command to obtain a list and the total number of equipment of a particular domain in a state (e.g. in-service, blocked etc.).

12. While working on system level commends, it shall be possible to store at least the last 20 commands on the screen and by scrolling and editing any command shall be re-executable.

7.1 Software Download Local & remote software download via management system to NEs and LCT shall be possible, including the means of identification of software module versions. No loss of data/traffic & connection-map shall take place during the software down-loading process.

8.0 Management Interface

The complete details of the management interface and the protocols, as pertaining to each layer of the protocol-stack implemented in the management system, shall be made available, for the purpose of integrating the local management capabilities with the centralized NMS at a later date. The requirements, in brief, shall be:

• Protocol details at all layers of TCP/IP stack. • PHY I/F at each layer. • Database structures. • Number formats. • Node addressing system. • Complete application software details etc. • EMS software check-sum.

8.1 Southbound Interface

The system shall provide at least one remote management interface and one Local Management Interface at each Network Element as conforming to ITU-T Rec. G.773.

The system shall provide an SNMP version2c [or later interface] with standard MIBs Browzer. It shall be implemented on UDP/IP stack at all Gateway NEs (GNEs) to interact with a centralized Element Management System (EMS). Or else ITU-T specified Qx or Bellcore specified TL1 interface implemented on TCP/IP, remote management interface shall also be acceptable.

Note 1: The equipment shall provide an Ethernet port for Work Station/Network Server connectivity with standard RJ-45 connector.

Note 2: The purchaser may validate vendor’s claim for management functions as well as protocol

compliance for Qx or SNMPv2c interface (or later interface) through NMS Protocol Analyzer etc. 8.2 Northbound Interface

For remote management purposes, the equipment shall provide remote and local management interfaces at NEs as outlined in the GR. The northbound interface of the EMS towards NMS layer shall be TMF 814 CORBA [version 3.0].

- 88 -


And the southbound interface towards NEs shall be SNMPv2c [or later interface] implemented on UDP/IP stack. The purchaser may verify SNMP MIBs and CORBA IDLs during their testing.

8.3 Local Management Interface

The manufacturer shall provide a Work Station/Network Server, which shall act as a manager of management activities, i.e. monitoring and controlling NEs within its management domain. The Local Craft Terminal i.e., a Personal Computer shall support the local management of NEs. The Local Craft Terminal and Network Server shall be operating simultaneously.

The inter–office communication shall be facilitated through DCC channels or dedicated data-link. The equipment shall provide V.24/V.28/RS232/RS-485 for connecting a PC-server as a Local Craft Terminal.

8.4 User Interface

The management system shall be provided with user-friendly interfaces based on Windows/UNIX icons & menus and mouse to accomplish management function that needs user interventions. The EMS start-up and shut-down shall be user friendly, and shall provide on-line help. The EMS shall be able to provide an on-screen nested geographical view of the managed network in the management domain of the manufacturer. It shall be possible to access any managed node with in the whole network in the managed domain. The EMS shall be able to depict the failure state of each link and node in the displayed network.

Further, it shall also be possible from the EMS system to get the details of status of an individual managed NE, such as equipment presence, settings, alarm status etc.

9.0 Embedded Control Channel

Twelve bytes D1 to D12 shall be used for Embedded Control Channel (ECC) protocol stack in accordance with the ITU-T Rec. G.784. There shall be additional requirement for multiple management options using DCC channels as outlined in the following clause.

10.0 Multiple Management Options

The equipment shall support Embedded Control Channels (ECC) transported over DCC bytes viz., D1 to D12 to be used for transfer of management information, in accordance with ITU-T Rec. G.784. Each of STM-N (whether it is line or tributary) shall have accompanying ECC. The equipment shall provide handling of all the ECC/DCC from/to all STM-N interfaces. The flow of protocols between the Work Station/Server and SDH equipment NE to NE shall strictly flow through Embedded Control Channels D1 to D12 with additional functionalities as below-

• D1-D3 bytes of RSOH - DCCr

• D4-D12 bytes of MSOH - DCCm

The configuration for the above shall be provided through EMS. It shall be possible to allow DCC bytes which are unused by the equipment to flow transparently through the equipment.

It shall be possible to map/retrieve DCC information to/from D1-D3 and D4-D12, local Ethernet Qx/SNMP management port, embedded VC12 in STM-N ports or physical E1 ports at local end. It shall be possible to transparently pass through D1-D3 and D4-D12. This is

- 89 -


required for allo cation of one of the sets to IP or OSI-DCC. Otherwise dual stack IP/OSI DCC shall be provided.

It shall be possible to allow DCC bytes which are unused by the equipment to flow transparently through the equipment.

The equipment shall provide multiple management options, in addition to the conventional use of DCC bytes, to allow greater scope for inter-vendor interoperability and simplification of operation, administration & management of the network.

The following options shall be provided in the equipment for physical access to the DCC information on STM-N line-

1. Tunnelling DCC in to assigned VC-12 embedded in outgoing STM-N line frame or, 2. Termination of DCC at E1 interface/s as part of an external DCN or 3. Termination at Ethernet traffic interface/s as part of an external DCN. 4. Termination at remote management interface at Gateway NEs (GNEs) on Ethernet

interface.

Or else, the equipment shall provide dual IP or OSI DCC routing stack in accordance with ITU-T Rec. G.7712. In such cases, configuration of DDCr (D1-D3) and DCCm (D4-D12) shall be provided as either IP-DCC or OSI-DCC through EMS. The equipment shall provide in-built intelligence to auto-sense as to which DCC block is relevant to it. The other DCC block shall be transparently tunnelled across, either at physical layer through one (and more VC12) or routed through IP/OSI stack. Termination of DCC at Qx/SNMP/TL-1 remote management interface at GNE #1 & 2 at Ethernet interface/s shall essentially be provided.

Regarding tributary STM-1/4/16 DCC termination, the system shall provide physical layer transparent tunnelling of DCC information across desired STM-N aggregate lines.

11.0 Extending DCC to central EMS Sever

The ports and the bandwidth requirements for DCC connectivity to an IP/MPLS network for extending the connectivity of network elements to the centralized EMS shall be indicated by manufacturer to the purchaser. Bandwidth requirement per NE/EMS shall also be specifically indicated by the manufacturer.

12.0 List of Constituents for a DCN

Dual-stack (IP and OSI) Routers The quantity shall be conveyed by purchaser. LAN Switches The quantity shall be conveyed by purchaser. Interface converters between Ethernet/E1 G.703

The quantity shall be conveyed by purchaser.

Ethernet adaptors 100BaseFX @1310nm The quantity shall be conveyed by purchaser.

12.1 Specifications

Broad specifications of LAN Switch and Routers are outlined in the following, whereas the purchaser is at discretion to issue alternate specifications as per networking needs.

12.1.1 LAN Switch

LAN switches may be used to terminate Ethernet interfaces from NEs at a transmission centre and to aggregate at uplink WAN ports towards a router. The LAN switch shall provide 10BaseT or Fast Ethernet interfaces towards NEs. The LAN switch for DCN shall be middle range LAN

- 90 -


switch as per TEC GR No.: G/LSW-01/01.JUN.2000. The middle range LAN switch (LAN SWITCH-1) may be used in case 16 ports supporting 10/100 Mbps is the requirement.

Similarly, LAN switches may also be used at EMS location for connecting various servers, firewalls etc.

The exact network design and architecture for a DCN is out of scope for this document.

12.1.2 Router

A router may be required to interconnect various transmission centres in a city and finally to connect to an IP/MPLS network for providing regional/national connectivity over MPLS-VPNs. In order to integrate existing NEs based on OSI management model, the router shall provide dual-stack (IP+OSI) i.e. - CLNP for Q3-based NEs and IP [OSPF/RIP] for TCP/IP-based NEs. Or else, the operator may choose to work at physical layer which makes the implementation transparent from higher layers. The router for DCN networking in a city may use Ethernet over SDH transport to connect to IP/MPLS network. However, other possibilities are not ruled out.

It is suggested to use –48V (-40V-60V) DC operated low range routers as per TEC GR No.: GR/TCP-01/ equipped with at least 2 Ethernet interfaces, one serial interface as LAN interfaces and 2 WAN Ports (which can be Nx64 Kbps or Ethernet). If the LAN ports are felt short of requirement, a LAN switch may be used, as above, to aggregate the transmission centers’ management traffic on fewer Ethernet ports. The exact network design and architecture for a DCN is out of scope for this document.

____________

- 91 -


APPENDIX II

VLAN implementation in M-ADM/ADM equipment

- 92 -


VLAN implementation in the M-ADM/ADM equipment

Introduction

Customers cannot be restricted for use of VLANs in their networks. Hence either translation of customer VLAN in to a S-VLAN unique in the aggregation network or issuance of VLAN to customers unique within service provider’s network are the possible solutions. Another compulsion is to maintain transparency to customer services. Hence VLAN stacking is inevitable.

There needs be a separate VLAN for services and for service providers. This VLAN is relevant to the WAN-side. No visibility of customer changes (new entries or churns) shall be there if LAN is decoupled from MAN. Customer MAC to/from VLAN mapping is decoupled from LAN to WAN. There can be any MAC address behind an M-ADM/ADM. It shall give networking flexibility. Service segregation in aggregation transport network

Two types of customer segregation are possible-

1. Customer based 2. Network based.

Service identification may be based on source/destination MAC or IP addresses of the IP service-edges. Single VLAN carriage of customer traffic, in such case, is possible only with network-based service segregation. This simplifies customers’ access network but suffers from QoS issues. In customer-based segregation, VLANs are separate for various services.

VLANs can be used for QoS differentiation or service segregation. A standard Ethernet network deploys Ethernet (VLAN) bridging. A VLAN bridge makes use of multiple separate virtual bridge instances. An incoming Ethernet frame is assigned to a particular virtual bridge based on its VLAN-ID. The VLAN-ID is a 12-bit field of the IEEE 802.1Q tag. For untagged frames (i.e., frames that are not 802.1Q tagged), the virtual bridge can be chosen based on either the port on which the Ethernet frame arrived or the Ethertype of the Ethernet frame. Each virtual bridge then performs an independent Ethernet forwarding process, deciding on which bridge (ports) to forward Ethernet frames to, based on the frames’ MAC destination address and its own MAC address forwarding table. Traffic cannot be exchanged between two virtual bridges. To obtain more flexible and more scalable use of VLAN-IDs, the IEEE 802.1ad stacked VLANs shall be used. This allows the tagging of Ethernet frames with two VLAN tags: the original VLAN tag, now called customer VLAN (C-VLAN) tag and a completely new service VLAN (S-VLAN) tag.

For upstream traffic, the Transport node shall assign the user Ethernet frame to a VLAN based on – 1. The port/VLAN, or 2. The VLAN tag (if the frame is already tagged), or 3. The protocol carried inside the Ethernet frame.

Next, the virtual bridge corresponding to this VLAN forwards the Ethernet frame to one or more of the Ethernet ports, based on the frame’s MAC destination address. The outgoing frame carries a VLAN tag. In the intelligent bridging model, traffic from multiple subscribers gets VLAN tagged with the same VLAN-ID. Typically, the VLAN-ID will be unique per Transport node (not per subscriber).

The VLAN tag that is applied is either a customer VLAN tag (C-TAG), or a service VLAN tag (S-TAG). Both tags have an identical structure, but are identified by a different Ethertype. C-VLANs will be used in combination with legacy VLAN-aware Ethernet switches in the aggregation network, while S-VLANs will be deployed in “provider-bridged” networks. It is also possible to apply a so-called VLAN stack i.e., a combination of a C-VLAN and an S-VLAN. This last solution makes it possible, for example, to use the C-VLAN tag for service differentiation on the ‘last mile’. Figure 2 shows an example of the ‘intelligent bridging’ model. The right side shows that Ethernet traffic from the ‘black’ and the ‘red’ virtual access-

- 93 -


port gets tagged with a ‘blue’ VLAN (VLAN 1), while traffic from the ‘blue’ virtual access-port gets tagged with an ‘orange’ VLAN (VLAN 2).

Note The structure of C-VLAN and S-VLAN shall be same as IEE 802.1p/q. Only the roles are different.

Virtual port 1 line 1 VLAN1 Virtual port 2 line 1 VLAN2 Virtual port 1 line 2 VLAN1

802.1q or 802.1ad

802.3

ETHERNET

802.3

RFC 2516

ATM

DSL

Access Link Transport Uplink

Figure 1 - Cross-connect model Mapping of Figure 1 shall be primarily implemented for SME/SOHO connectivity services- EPL/EVPL/EVPLAN/EPLAN/VPLS/IP-VPNs etc.

802.1q or 802.1ad

802.3

ETHERNET

802.3

RFC 2516

ATM

DSL

Access Link Transport uplink

Virtual port 1 line 1 VLAN1 Virtual port 2 line 1 VLAN2 Virtual port 1 line 2 VLAN1

Figure 2 - Intelligent bridging model

Mapping of Figure 2 shall be implemented for residential-service aggregation mainly. Any other use, however, not ruled out. Scalability statement of the network

A C-VLAN unique to M-ADM/ADM shall be appended to customer’s Ethernet frame to identify the customer in aggregation network. 4094 customers per M-ADM/ADM ring shall thus be possible. In order to scale beyond this limit, VLAN stacking shall be used appending a service provider VLAN i.e., S-VLAN (unique to M-ADM/ADM) which shall be flexible used to identify M-ADM/ADM, a particular service or a particular service provider. There shall be 4094 customers possible per S-VLAN distinguished by unique (per M-ADM/ADM) C-VLAN. Theoretically, the number of S-VLAN’s per M-ADM/ADM shall be = 4094/(No. of M-ADM/ADM on the ring).

- 94 -


Total C-VLANs (unique to a packet ring) supported in ring

= 4094

Per ring VLAN support (with VLAN stacking) = 4094 x 4094

Theoretical no. of customers possible on a packet ring = 4094 x 4094

The purchaser shall communicate VLAN scalability requirements depending upon deployed network size.

____________

- 95 -


GLOSSARY AIS Alarm Indicating Signal BIP Bit Interleaved Parity BITE Built-In Test Equipment

CRT Cathode Ray Tube DCC Data Communication Channel ECC Embedded Control Channel EMC Electro-Magnetic Compatibility EMS Element Management System

GDMO General Definition of Managed Objects HOP Higher Order Path HP-UNEQ Higher Path Unequipped LOF Loss of Frame LOP Loss of Pointer

LOP Lower Order Path LOS Loss of Signal LP-UNEQ Lower Path Unequipped MDU Multi-Dwelling Unit MIB Management Information Base

MTU Multi-Tenant Unit MDU Multi-Dwelling Unit MS-AIS Multiplex Section Alarm Indicating Signal MSOH Multiplex Section Over Head MS-RDI Multiplex Section Remote Defect Indication

MTBF Mean Time Between Failure MTTR Mean Time To Restore NE Network Element NMS Network Management System OSI Open System Interconnection

PCM Pulse Code Modulation PICS Protocol Information Compliance Statement POH Path Over Head QA Quality Assurance REI Remote Error Indication

SDH Synchronous Digital Hierarchy SNC-N Sub-Network Connection Non-intrusive STM-1e STM 1 Electrical STM-1o STM 1 Optical TMN Telecommunication Management Network

TSA Time Slot Assignment TSI Time Slot Interchange TUs Tributary Units VC Virtual Container

-------END OF DOCUMENT------