tn-1c system description

323-1081-100

NORTEL NETWORKS

TN-1C/TN-1PSystem Description

Release 5.2 Standard (Revision 1) October 2001

TN-1C/TN-1P System Description

NORTEL NETWORKS


Document Number: 323-1081-100Document Status: Standard (Revision 1) Product Release Number: 5.2Date: October 2001

Copyright 1996 – 2001 Nortel Networks, All Rights Reserved.

Printed in England

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are trademarks of Nortel Networks.


iii

Publication historyOctober 2001

Release 5.1 Standard (Revision 1). Minor updates.

March 2001Release 5.2 Standard. 24 x 2 Mbit/s tributary extension card and single-slot TN-1C information added. PE10 router card references added.

September 2000Release 5.1 Standard. Release 5.1 features added.

November 1999Release 5 Standard. TN-1C and TN-1P documents combined, Release 5 features added.

January 1999Release 3 Standard (Revision 1). Minor amendments.

March 1998Release 3 Standard.

June 1997Release 2 Standard.

December 1996Release 1 Standard.


v

ContentsAbout this document xiiiTechnical support and information xiv

System overview 1-1TN-1C multiplexer 1-1TN-1P and TN-1PH headend multiplexers 1-2TN-1P Basestation multiplexer 1-2System configuration - TN-1C 1-7

Point-to-point terminal multiplexer 1-7Path protected 2-fibre ring 1-7ADM loop feeder 1-8ATU application 1-9

System configuration - TN-1P, TN-1PH 1-10Point-to-point terminal multiplexer 1-10Terminal multiplexer spur from an SDH ring 1-11Hub configuration 1-12ATU application 1-13

Mechanical description 1-15Enclosure types 1-15Mounting 1-15

Connectivity 1-18Channel numbering schemes 1-18Port/channel designations 1-20Types of connections 1-21User labels 1-23Traffic mode 1-23Path trace 1-24Signal label 1-25

Path protection switching 1-26Management and communications 1-26Rack alarm adaptor 1-27Software 1-27

Foundation software 1-27Application software 1-27Software download 1-28

Interfaces 1-28Fan 1-28Variants 1-29

TN-1C 1-29TN-1P 1-31

vi

323-1081-100 Release 5.2 Standard (Revision 1)

Equipment description 2-1Power supplies 2-5

External 2-5Internal power supply 2-5

Timing source 2-6Clock generator 2-6System clock 2-6

Controller platform 2-6Processor 2-6Restart 2-6Memory 2-6Serial communications 2-7

STM-1 interface 2-7Timeslot interchanger 2-7Multi-channel tributary block 2-8Extension card interface (TN-1C only) 2-8Traffic processing 2-8Path protection 2-13

Holdoff period 2-13Oscillation guard time 2-13Reversion 2-13Priority control 2-13PPS criteria 2-14Automatic laser shutdown 2-14

Loopbacks 2-15STM-1 local loopback 2-15STM-1 remote loopback 2-16Tributary local loopback 2-17Tributary remote loopback 2-17Simultaneous loopbacks 2-18

Single fibre working 2-18Built-in test facility 2-19

Non-service affecting tests 2-19Service affecting tests 2-20

Subrack end processor and craft access panel (TN-1PH only) 2-22LAN Interface 2-24Alarm handler 2-24RS-232 selector 2-24

Equipment management 3-1Alarms 3-1

Alarm monitoring 3-1Alarm handling 3-1Alarm masking 3-1External alarms 3-2Rack alarms 3-2

Management 3-3ATU channel 3-3LAN channel 3-4Real time clock 3-4RSOH/MSOH DCC 3-4Network addresses 3-5Communication limitations 3-5Inventory information 3-5

vii


Software 3-6Application software 3-6Configuration data 3-6

Power supply unit 4-1Functional description 4-1

Battery back-up 4-2Alarms and indications 4-2Connectors 4-3Construction 4-4

Synchronisation 5-1Sources 5-1

Synchronisation loss 5-1Synchronisation schemes 5-2

TN-1C 5-2TN-1P 5-3

Synchronisation source switch event 5-6Synchronisation source hierarchy 5-6Synchronisation settings 5-6Synchronisation switching mechanisms 5-7Synchronisation status messaging (SSM) 5-7

Synchronisation status messaging network examples 5-9SSM recommendations 5-11

Non-SSM synchronisation sourcing (TN-1C/TN-1P) 5-12Failure of synchronisation source 5-13

Wait to restore time 5-13Synchronisation alarms 5-13

Performance monitoring 6-1Parity error counts 6-1Performance monitoring counts 6-1Performance monitoring points 6-2

Disabling performance monitoring 6-3Performance anomalies and defects 6-3Performance monitoring periods 6-4Performance logs 6-5

15 minute logs 6-524 hour logs 6-6Early termination 6-7Warm restart 6-7Quality of service violation alarms 6-7Traffic type 6-8

User actions 6-9

System parameters 7-1Common 7-1

Electromagnetic compatibility 7-1Environmental conditions 7-1

Construction 7-2External dimensions 7-2Weight 7-2Supply voltage 7-2Fuses 7-2

viii


Maximum power consumption 7-3External interfaces 7-4

2 Mbit/s tributary interfaces 7-434 Mbit/s tributary interfaces (TN-1C only) 7-445 Mbit/s tributary interfaces (TN-1C only) 7-5STM-1 optical interfaces 7-52 Mbit/s external synchronisation input 7-7Craft Access Terminal interface 7-7LAN interface 7-7ATU interface 7-8External alarms 7-8

Power Supply Unit (TN-1C and standard TN-1P only) 7-9A.C. supply 7-9D.C. output 7-9Fuses 7-9Power consumption 7-9Power dissipation 7-9Recommended battery replacement period 7-9Alarm outputs 7-9

External interfaces 8-1D-type connectors 8-132 Mbit/s 75 Ω tributary interfaces 8-132 Mbit/s 120 Ω tributary interfaces 8-1334/45 Mbit/s tributary interfaces (TN-1C only) 8-14Optical interfaces 8-15Craft access terminal interface 8-15ATU interface (TN-1C Release 1 and 2 and TN-1C single-slot hardware and

TN-1P) 8-16ATU interface TN-1C (Release 3/5/5.1 hardware) 8-16Fan interface (TN-1C and TN-1P Release 5.1 hardware) 8-182 Mbit/s external synchronisation input 8-18External alarm interface 8-19Power and power alarm interface 8-21LAN interface 8-22Rack alarm adaptor 8-23Rack alarm bus connector 8-24Fuses 8-24

Ordering codes 9-1TN-1C only 9-1TN-1P only 9-3Common items 9-5Obsolete codes 9-6

Appendix A: Synchronous digital hierarchy 10-1Synchronous Digital Hierarchy 10-1

SDH multiplexing structure 10-2TN-1C multiplexing structure 10-4TN-1P multiplexing structure 10-4Mapping of a 2048 kbit/s signal into a VC-12 10-5Mapping of a 34.368 Mbit/s signal into a VC-3 10-6Mapping of a 44.736 Mbit/s signal into a VC-3 10-6Multiplexing of VC-12s into a TUG-2 10-7

ix


Multiplexing of TUG-2s into a TUG-3 10-7Multiplexing of a VC-3 into a TUG-3 10-9Mapping of TUG-3s into a VC-4 10-9Mapping of a VC-4 into a STM-1 via an AU-4/AUG 10-10Path overheads 10-10Section overhead 10-11

Index 11-1

List of figuresFigure 1-1 TN-1C general view 1-3Figure 1-2 TN-1P and single-slot TN-1C general view 1-4Figure 1-3 TN-1P Headend subrack general view 1-5Figure 1-4 TN-1P Basestation general view 1-6Figure 1-5 TN-1C point-to-point terminal 1-7Figure 1-6 TN-1C in a 2-fibre path protection ring 1-8Figure 1-7 TN-1C connected to an ADM STM-1 tributary 1-9Figure 1-8 Typical TN-1C ATU application 1-10Figure 1-9 TN-1P protected point-to-point STM-1 line system 1-11Figure 1-10 Terminal multiplexer spur 1-11Figure 1-11 Hub configuration 1-12Figure 1-12 Typical TN-1P ATU application 1-14Figure 1-13 Typical TN-1C/TN-1P installations 1-16Figure 1-14 Typical TN-1P Basestation installation 1-16Figure 2-1 TN-1C block diagram 2-3Figure 2-2 TN-1P block diagram 2-4Figure 2-3 TN-1C traffic processing 2-10Figure 2-4 TN-1P traffic processing 2-11Figure 2-5 STM-1 local loopback 2-16Figure 2-6 STM-1 remote loopback 2-17Figure 2-7 Tributary local loopback 2-17Figure 2-8 Tributary remote loopback 2-18Figure 2-9 Single fibre operation 2-18Figure 2-10 PRBS location 2-21Figure 2-11 SEP and CAP block diagram 2-23Figure 3-1 Software upgrade overview 3-7Figure 4-1 TN-1C PSU block diagram 4-2Figure 4-2 TN-1C and TN-1P multiplexer PSU layout 4-5Figure 5-1 TN-1C recommended synchronisation scheme 5-4Figure 5-2 TN-1P recommended synchronisation schemes 5-5Figure 5-3 SSM within a simple STM-1 ring with a single external source 5-9Figure 5-4 SSM within a simple STM-1 ring with two external sources 5-10Figure 5-5 SSM within a simple STM-1 chain with two external sources 5-11Figure 8-1 TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version)

Release 1 hardware 8-3Figure 8-2 TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version)

Release 3/5 hardware 8-4Figure 8-3 TN-1C connection panel (16 x 2 Mbit/s version) Release 1

hardware 8-5Figure 8-4 TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5

hardware 8-6Figure 8-5 TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1

hardware 8-7Figure 8-6 TN-1C optional 75 Ω interface cards for Release 5.1 hardware 8-8

x


Figure 8-7 TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware 8-9Figure 8-8 TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C

single-slot connection panel (8 x 2 Mbit/s) 8-10Figure 8-9 TN-1P Basestation (integral front panel connectors) 8-11Figure 8-10 TN-1PH connector panel 8-12Figure 8-11 Standard pin numbering for D-type connectors 8-13Figure 10-1 SDH generalized multiplexing structure 10-2Figure 10-2 STM-1 frame structure 10-4Figure 10-3 TN-1C multiplexing structure 10-4Figure 10-4 TN-1P multiplexing structure 10-4Figure 10-5 2.048 Mbit/s tributary/VC-12/TU-12 mapping 10-5Figure 10-6 34.368 Mbit/s tributary/VC-3 mapping 10-6Figure 10-7 44.736 Mbit/s tributary/VC-3 mapping 10-7Figure 10-8 Multplexing of TU-12 via a TUG-2 10-8Figure 10-9 TU-12/TUG-2/TUG-3 multiplexing 10-8Figure 10-10 Multiplexing of a TU-3 via a TUG-3 10-9Figure 10-11 Multiplexing of three TUG-3s into a VC-4 10-9Figure 10-12 Mapping of a VC-4 into an STM-1 via an AU-4/AUG 10-10Figure 10-13 VC-12 Path Overhead (V5 byte) 10-10Figure 10-14 Section overhead 10-12

List of tablesFigure 1-1 TN-1C general view 1-3Figure 1-2 TN-1P and single-slot TN-1C general view 1-4Figure 1-3 TN-1P Headend subrack general view 1-5Figure 1-4 TN-1P Basestation general view 1-6Figure 1-5 TN-1C point-to-point terminal 1-7Figure 1-6 TN-1C in a 2-fibre path protection ring 1-8Figure 1-7 TN-1C connected to an ADM STM-1 tributary 1-9Figure 1-8 Typical TN-1C ATU application 1-10Figure 1-9 TN-1P protected point-to-point STM-1 line system 1-11Figure 1-10 Terminal multiplexer spur 1-11Figure 1-11 Hub configuration 1-12Figure 1-12 Typical TN-1P ATU application 1-14Figure 1-13 Typical TN-1C/TN-1P installations 1-16Figure 1-14 Typical TN-1P Basestation installation 1-16Figure 2-1 TN-1C block diagram 2-3Figure 2-2 TN-1P block diagram 2-4Figure 2-3 TN-1C traffic processing 2-10Figure 2-4 TN-1P traffic processing 2-11Figure 2-5 STM-1 local loopback 2-16Figure 2-6 STM-1 remote loopback 2-17Figure 2-7 Tributary local loopback 2-17Figure 2-8 Tributary remote loopback 2-18Figure 2-9 Single fibre operation 2-18Figure 2-10 PRBS location 2-21Figure 2-11 SEP and CAP block diagram 2-23Figure 3-1 Software upgrade overview 3-7Figure 4-1 TN-1C PSU block diagram 4-2Figure 4-2 TN-1C and TN-1P multiplexer PSU layout 4-5Figure 5-1 TN-1C recommended synchronisation scheme 5-4Figure 5-2 TN-1P recommended synchronisation schemes 5-5Figure 5-3 SSM within a simple STM-1 ring with a single external source 5-9Figure 5-4 SSM within a simple STM-1 ring with two external sources 5-10Figure 5-5 SSM within a simple STM-1 chain with two external sources 5-11

xi


Figure 8-1 TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version) Release 1 hardware 8-3

Figure 8-2 TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version) Release 3/5 hardware 8-4

Figure 8-3 TN-1C connection panel (16 x 2 Mbit/s version) Release 1 hardware 8-5

Figure 8-4 TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5 hardware 8-6

Figure 8-5 TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1 hardware 8-7

Figure 8-6 TN-1C optional 75 Ω interface cards for Release 5.1 hardware 8-8Figure 8-7 TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware 8-9Figure 8-8 TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C

single-slot connection panel (8 x 2 Mbit/s) 8-10Figure 8-9 TN-1P Basestation (integral front panel connectors) 8-11Figure 8-10 TN-1PH connector panel 8-12Figure 8-11 Standard pin numbering for D-type connectors 8-13Figure 10-1 SDH generalized multiplexing structure 10-2Figure 10-2 STM-1 frame structure 10-4Figure 10-3 TN-1C multiplexing structure 10-4Figure 10-4 TN-1P multiplexing structure 10-4Figure 10-5 2.048 Mbit/s tributary/VC-12/TU-12 mapping 10-5Figure 10-6 34.368 Mbit/s tributary/VC-3 mapping 10-6Figure 10-7 44.736 Mbit/s tributary/VC-3 mapping 10-7Figure 10-8 Multplexing of TU-12 via a TUG-2 10-8Figure 10-9 TU-12/TUG-2/TUG-3 multiplexing 10-8Figure 10-10 Multiplexing of a TU-3 via a TUG-3 10-9Figure 10-11 Multiplexing of three TUG-3s into a VC-4 10-9Figure 10-12 Mapping of a VC-4 into an STM-1 via an AU-4/AUG 10-10Figure 10-13 VC-12 Path Overhead (V5 byte) 10-10Figure 10-14 Section overhead 10-12


xiii

About this documentThis document provides a system level description of the TN-1C, TN-1P, TN-1PH Headend and TN-1P Basestation multiplexers. This document provides a concise introduction to the equipment and is recommended reading for anyone working with the TN-1C, TN-1P, TN-1PH Headend or the TN-1P Basestation.

For details on the deployment of the optional Nortel Networks OPTera Packet Edge 10 (OPE-10) in a TN-1C multiplexer, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

Note: Unless otherwise specified, the term TN-1P is used to refer to the standard TN-1P, TN-1PH multiplexers and the TN-1P Basestation.

Indication of trademarks in this documentThe asterisk after a name denotes a trademarked item. The title page and back cover acknowledge all trademarked items.


xiv

Technical support and informationSo far as Nortel Networks is aware the information in this document is correct. If, however, you discover any errors or have comments regarding the presentation of the content, please send details by email to:

[email protected]

Nortel Networks provides a comprehensive technical support service for its customers. The Nortel Networks Service Desk may be contacted at any time on the following numbers:

United KingdomFreephone: 00800 8008 9009Fax within the United Kingdom: 020 8945 3456

InternationalWithin Europe: Freephone 00800 8008 9009Outside of Europe: +44 20 8920 4618Fax outside of the United Kingdom: +44 20 8945 3456

You can contact us via the Nortel Networks web site:

www.nortelnetworks.com

Select the link Customer Support.

EMC/Safety conformance

This product/product family complies with the provisions of the Low Voltage Directive 73/23/EEC, and with the essential protection requirements of the EMC Directive 89/336/EEC as amended by 92/31/EEC, when it is properly installed and maintained and when it is used for the purposes for which it is intended.


1-1

1

System overview 1-TN-1C multiplexer

The TN-1C is a stand-alone synchronous digital hierarchy (SDH) add/drop multiplexer (ADM). See Figure 1-1.

The TN-1C comprises a multiplexer assembly containing:

• 8 x 2 Mbit/s ADM multiplexer main card mounted in a frame, which provides electro-magnetic compatibility (EMC) screening

• a dummy or tributary extension card

• a connection panel

A single-slot TN-1C is available which comprises a multiplexer assembly containing:

• 8 x 2 Mbit/s ADM multiplexer main card mounted in a frame, which provides electro-magnetic compatibility (EMC) screening

• a connection panel

In the transmit direction, the TN-1C multiplexes plesiochronous electrical tributary input signals (2 Mbit/s, 34/45 Mbit/s) into an aggregate STM-1 signal. The TN-1C transmits the STM-1 signal over an optical fibre link. In the receive direction, the TN-1C demultiplexes incoming STM-1 signals from the fibre link to provide tributary outputs (2 Mbit/s, 34/45 Mbit/s).

The main TN-1C ADM card provides up to eight 2 Mbit/s tributaries. There are four variants of the tributary extension card, which provide the following additional interfaces:

• 8 x 2 Mbit/s interfaces

• 24 x 2 Mbit/s interfaces

• 1 x 34/45 Mbit/s interface

• 2 x 34/45 Mbit/s interfaces

Note: If a tributary extension card is not fitted, a dummy card must be fitted in its place to comply with electro-magnetic compatibility (EMC) requirements.

In addition to the tributary extension card, there is an optional high performance router card, which supports 10/100 BaseT LAN and a variety of

1-2 System overview


WAN interfaces. For a description of the TN-1C multiplexer Packet Edge 10 router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

TN-1P and TN-1PH headend multiplexersThe TN-1P is a stand-alone SDH point-to-point (terminal) multiplexer. The TN-1P comprises a multiplexer assembly containing a single 4 x 2 Mbit/s multiplexer card mounted in a frame, which provides EMC screening, and a connection panel (see Figure 1-2). You can upgrade the 4 x 2 Mbit/s Release 5.1 hardware version of the TN-1P to support 8 x 2 Mbit/s tributaries by replacing the 4 x 2 Mbit/s multiplexer card with an 8 x 2 Mbit/s ADM card. A TN-1P which contains an 8 x 2 Mbit/s ADM card operates as a single-slot TN-1C with limited functionality, and identifies itself to the element controller (EC-1) as a TN-1C.

The TN-1PH headend contains up to twelve multiplexers (each functionally equivalent to a TN-1P) mounted in a single headend subrack (see Figure 1-3).

In the transmit direction, the TN-1P multiplexes up to four plesiochronous 2 Mbit/s electrical tributary input signals into an aggregate STM-1 signal. The TN-1P transmits the STM-1 signal over an optical fibre link. In the receive direction, the TN-1P demultiplexes incoming STM-1 signals from the fibre link to provide up to four 2 Mbit/s tributary outputs.

TN-1P Basestation multiplexerThe TN-1P Basestation is a rack mounted, point-to-point SDH multiplexer, based on the TN-1P. The TN-1P Basestation has the following configurations:

• unprotected optics with 4 x 2 Mbit/s tributaries

• protected optics with 4 x 2 Mbit/s tributaries

• ADM with 8 x 2 Mbit/s tributaries (see note below)

You can upgrade the 4 x 2 Mbit/s versions of the TN-1P Basestation to support 8 x 2 Mbit/s tributaries by replacing the 4 x 2 Mbit/s multiplexer card with an 8 x 2 Mbit/s ADM card. A TN-1P Basestation which contains an 8 x 2 Mbit/s ADM card operates as a TN-1C with limited functionality, and identifies itself to the EC-1 as a TN-1C.

Note: Refer to the TN-1C/TN-1P Installation Procedures 323-1081-200 for information on how to upgrade the TN-1P and TN-1P Basestation.

The TN-1P Basestation is suitable for installations where equipment height is restricted and only front access is available.

The TN-1P Basestation comprises a rack-mounting shelf assembly containing a single multiplexer card mounted in a frame, which provides EMC screening, a rear connection panel and a front connection panel. See Figure 1-4.

System overview 1-3


1Figure 1-1TN-1C general view

ConnectorpanelFan

Secondary fan optional)

Main 8x2 Mbit/sADM card

EMCenclosure

Backplane connector

Secondary fan controller card (optional)

Note: The TN-1C illustrated is the 16 x 2 Mbit/s version. The secondary fan is an optional item for harsh environments.

Tributary extension card or PE10 router card

1-4 System overview


Figure 1-2TN-1P and single-slot TN-1C general view

Note 1: At Release 5, the TN-1P connection panel supports 4 x 2 Mbit/s tributaries. At Release 5.1, the TN-1P connection panel supports 8 x 2 Mbit/s tributaries.

Multiplexer unit

Connection panel

EMC screen

Fan

Note 2: The fan is not fitted to Release 5 hardware.

System overview 1-5


1Figure 1-3TN-1P Headend subrack general view

100_02a

Connection panel

Plug-in Unit area

Mounting flanges

Fibre tray position

1-6 System overview


Figure 1-4TN-1P Basestation general view

Shown with multiplexer card extended

Integral Left-hand mounting bracket

Rear connector panel

Integral Right-hand mounting bracket

Front connector panel

Integral fibre spool

Power connector

Craft Access Terminal(CAT)

Cable tie holders (as required)

2 Mbit/s tributaries (75 Ω BNC).Four pairs are used on the 4 x 2 Mbit/s versions.Eight pairs are used on the 8 x 2 Mbit/s ADM version.

Fan

Note: The fan is not fitted to Release 5 hardware.

System overview 1-7


1System configuration - TN-1CThe TN-1C multiplexer can operate in any of the following configurations:

• point-to-point terminal multiplexer

• path protected 2-fibre ring

• ADM loop feeder

Point-to-point terminal multiplexerThe TN-1C multiplexer can be used as a conventional terminal multiplexer in a point-to-point arrangement for delivery of a number of 2 Mbit/s or 34/45 Mbit/s tributary links over an STM-1 fibre link. Figure 1-5 shows a protected point-to-point system. The tributary input signals are multiplexed into an STM-1 signal, and transmitted over the fibre link to the other end where the 2 Mbit/s or 34/45 Mbit/s signals are reconstructed.

Figure 1-5TN-1C point-to-point terminal

Path protected 2-fibre ringThe path protected 2-fibre ring configuration provides diverse routing which overcomes common mode faults and thus provides protection against a fault in any optical path. Tributaries that require protection (e.g. Private Circuit [PC] traffic) are routed both ways around the ring. At the receiving multiplexer, traffic from the one of the aggregate ports is used unless there is a fault when traffic from the other aggregate port is used (see ‘Path protection switching’ on page 1-26 and ‘Path protection’ on page 2-13).

A possible application of this configuration is for feeding 2 Mbit/s and/or 34/45 Mbit/s signals in a local loop (‘loop feeder’) where one of the TN-1Cs is located in a central office site. Signals may be sourced from a switch (for example, DMS 100), connected to the multiple 2 Mbit/s interfaces in the TN-1C, and distributed to remote locations where switch remotes or primary multiplexers are located.

PartnerTN-1CRS232C

connection

Craft AccessTerminal

Tributary interfaces

EC-1LAN

Tributary interfaces

LocalTN-1C

1-8 System overview


Another possible application is to carry high-rate data services, such as 34 Mbit/s LAN interconnection. A ring can be used between several locations and provides high-speed data flow.

The ring may consist of TN-1Cs and (possibly) TN-1Xs or TN-1X/Ss. Figure 1-6 shows a path protected 2-fibre ring application.

Figure 1-6TN-1C in a 2-fibre path protection ring

ADM loop feederThe TN-1C can be used in an ADM loop feeder configuration to provide a spur from a SDH ring. In this configuration, the TN-1C operates as it would in the case of a point-to-point terminal multiplexer. This configuration can also be used to drop traffic from an ADM in a larger transport network to the TN-1C. Figure 1-7 shows a ADM loop feeder configuration.

RS232Cconnection

LAN2 Mbit/s and 34/45 Mbit/s

tributary interfaces

TN-1C

Craft Access Terminal

TN-1C

TN-1CTN-1C

TN-1C

EC-1

2 Mbit/s and 34/45 Mbit/s tributary interfaces

2 Mbit/s and 34/45 Mbit/s

tributary interfaces

System overview 1-9


1Figure 1-7TN-1C connected to an ADM STM-1 tributary

ATU applicationIn the TN-1C asynchronous telemetry unit (ATU) application, the TN-1C is used in an SDH ring with TN-1X ADMs (Figure 1-8). The ATU allows the transport of asynchronous management (telemetry) information over the SDH network.

The TN-1C is located in a street cabinet site with an external plesiochronous digital hierarchy (PDH) access multiplexer (for example a Nortel Networks PDMX-E or UE3000). The external equipment management system communications are passed through a headend ATU that maps the external equipment address to the respective TN-1C open systems interconnect (OSI) address. The messages are sent via the SDH system LAN and the SDH overhead to the TN-1C and are then passed to the equipment concerned through the TN-1C point-to-multipoint RS-485 port (RS-232 port on early hardware). This application provides a simple method of using a PDH access multiplexer as a feed to an SDH system.

The TN-1C supports two ATU protocols:

• High-level data link control (HDLC) for PDMX-E

TN-1C

LAN

TN-1C

EC-1

ST

M-1

o tr

ibut

ary

ST

M-1

o tr

ibut

ary

ST

M-1

o tr

ibut

ary

ADM

ADM

2 Mbit/s and 34/45 Mbit/s tributary interfaces

1-10 System overview


• Point-to-point protocol (PPP) for UE3000.

For information about the head-end ATU functionality and use, see TN-1X Asynchronous Telemetry Unit System Description, 323-1063-100.

Figure 1-8Typical TN-1C ATU application

System configuration - TN-1P, TN-1PHThe TN-1P multiplexer can operate in any of the following configurations:

• point-to-point terminal multiplexer

• terminal multiplexer spurred from an SDH ring

• terminal multiplexer or one of a number of terminal multiplexers in a hub type arrangement

In all configurations one multiplexer unit of a TN-1P Headend subrack is equivalent to a TN-1P although only one end of a point-to-point system can be a Headend TN-1P.

Point-to-point terminal multiplexerThe TN-1P multiplexer can be used as a conventional terminal multiplexer in a point-to-point arrangement for delivery of up to four (or eight with upgrade) 2 Mbit/s tributary links over an STM-1 fibre link. Figure 1-9 shows a protected point-to-point system. The tributary input signals are multiplexed into an STM-1 signal, and transmitted over the fibre link to the other end where the 2 Mbit/s signals are reconstructed.

RS-485 connector cable

LAN Headend ATU

External equipment manager

TN-1C

TN-1X

TN-1X

EC-1

External equipment

LAN

System overview 1-11


1For TN-1P, the path can be either protected or unprotected, depending on the TN-1P variant used (see page 1-31).

Figure 1-9TN-1P protected point-to-point STM-1 line system

Terminal multiplexer spur from an SDH ringThe TN-1P can be used as a terminal multiplexer spur from an SDH ring providing an unprotected or protected STM-1 spur. Figure 1-10 shows both applications.

Figure 1-10Terminal multiplexer spur

up to four (eight with upgrade) 2 Mbit/s

tributaries

A A

BB

Working

Standby

TN-1P TN-1P

up to four (eight with upgrade) 2 Mbit/s

tributaries

Headend

Unprotected spur

tributaries

1+1 Protected spur

tributariestributaries

ADM

ADM

ADM ADM

up to four (eight with upgrade)

2 Mbit/s tributaries

ADM

TN-1P TN-1P

STM-1 optical tributaries


up to four (eight with upgrade)

2 Mbit/s tributaries



Hub configurationThe TN-1P can be used in a hub configuration where a number of remote s from different locations are connected to a central network element.

Figure 1-11 shows both protected and an unprotected TN-1P links feeding a central office TN-1X hub which connects via an ADM into an STM-16 ring.

Figure 1-11Hub configuration

TN-1PTN-1P

TN-1P*

TN-1P

TN-1P

STM-1

STM-1

STM-1STM-4

2 Mbit/stributaries

2 Mbit/stributaries

2 Mbit/stributaries

ADM

STM-16

Central Office

Location

STM-16


STM-4 aggregate

* TN-1P or TN-1P Headend or TN-1P Basestation variant within Central Office Location

2 Mbit/stributaries

STM-1

STM-1

STM-1TN-1XHub

TN-1P*



1ATU applicationIn the TN-1P ATU application, the TN-1P is used as a spur from a TN-1X ADM as part of an SDH network (Figure 1-12). The ATU allows the transport of asynchronous management (telemetry) information over the SDH network. The TN-1P uses an RS-232 port for the ATU application.

The TN-1P is located in a street cabinet site with an external PDH access multiplexer (for example a Nortel Networks PDMX-E or UE3000). The external equipment management system communications are passed through a headend ATU that maps the external equipment address to the respective TN-1P OSI address.

The messages are sent via the SDH system LAN and the SDH overhead to the TN-1P and are then passed to the equipment concerned through the TN-1P RS-232 ATU port. In addition to the external system messages, the TN-1P to TN-1X optical link has the capacity to carry up to eight 2 Mbit/s outputs from the external equipment to the SDH network. This provides a simple method of using a PDH access multiplexer as a feed to an SDH system.

The TN-1P supports two ATU protocols:

• High-level data link control (HDLC) for PDMX-E

• Point-to-point protocol (PPP) for UE3000.

For information on the Headend ATU functionality and use, see ‘TN-1X Asynchronous Telemetry Unit System Description, 323-1063-100’ .

Clear channel telemetryThe clear channel telemetry function allows equipment outside the transmission network to pass asynchronous ASCII messages at 19200 bit/s across the transmission network. This function is supported by TN-1C and TN-1P. The throughput is limited to four messages per second. See “Clear channel telemetry” on page 3-3 for more details.



Figure 1-12Typical TN-1P ATU application

LANHeadend ATU

card

LAN

External equipment manager

RS232 connectorcable

up to four (eight with upgrade) 2 Mbit/s tributaries

External equipment

TN-1X

TN-1X

TN-1X

TN-1P

EC-1

RS232/RS485 converter



1Mechanical descriptionThe TN-1C (see Figure 1-1) and standard TN-1P (see Figure 1-2) have the same mechanical construction, except that the TN-1C can contain an optional tributary extension card. If the tributary extension card is not fitted to a TN-1C, a dummy card is fitted in its place to provide EMC compliance. The TN-1P does not have the extension card. The single-slot TN-1C does not contain the optional tributary extension card and has the same mechanical construction as the TN-1P.

The TN-1P Headend (see Figure 1-3) is a subrack suitable for 19 inch or ETSI rack mounting. The TN-1P Headend contains up to 12 TN-1P Main Point-to-Point (MPP) units and a Subrack End Processor (SEP) unit. The backplane extends upwards above the MPP unit mounting area to provide a connection panel for all of the copper cabling, including the craft access terminal (CAT) and LAN connections. A craft access panel (CAP) is fitted on the right hand side of the subrack. The CAP provides local status indications, an alarm acknowledge push-button, and a display and push-button to select which of the MPP units is connected to the CAT socket. A fibre tray is provided immediately below the subrack for the management of optical aggregate fibres.

The TN-1P Basestation (see Figure 1-4) is based on the TN-1C/TN-1P platform. The main changes from the standard TN-1P are as follows:

• Horizontal mounting into a 19-inch or European Telecommunications Standards Institute (ETSI) rack or cabinet

• A backplane that supports 8 x 2 Mbit/s tributaries.

• Front access for 75 Ω tributaries, craft access terminal (CAT), power and optical connections.

• Fibre management is carried out externally.

Enclosure typesThe TN-1C or standard TN-1P is packaged in a single, lockable enclosure that can be mounted on a wall in customer premises, in a street cabinet, or in a rack. For Release 5.1 hardware, the enclosure is plastic (earlier releases can have either a plastic or metal enclosure). The enclosure contains an EMC frame with a connector panel fitted with the multiplexer card. The TN-1C can be fitted with an optional tributary extension card or router card.

The TN-1PH Headend has no enclosure and is mounted in a rack.

The TN-1P Basestation has no enclosure and is mounted in a street cabinet or in a rack. The TN-1P Basestation comprises a shelf which contains a front-access connection panel and an EMC frame fitted with the main multiplexer card and a connector panel.

MountingThe TN-1C or standard TN-1P enclosure can be rack mounted or wall mounted, depending on the environment in which it is deployed, see Figure 1-13. The TN-1C can be installed in a street cabinet.



A hardware pin located on the TN-1P/TN-1PH main card indicates whether the card is in a TN-1PH unit.

The TN-1P Basestation can be installed in a rack or street cabinet. See Figure 1-14 for typical deployment of a TN-1P Basestation.

Figure 1-13Typical TN-1C/TN-1P installations

Figure 1-14Typical TN-1P Basestation installation

Tributarycables

Tributarycables

Opticalfibres

d.c. powercable

a.c. powercable

Wall mounted multiplexer with power supply

Rack mounted multiplexer.The power supply is taken from

the rack

Multi-plexer

PSU

Optical fibres

Rack mounted multiplexer.The power supply is taken from the rack

Optical fibres

Tributarycables

d.c. power cable



1Wall mountingThe TN-1C and the standard TN-1P multiplexer can be used with a dedicated power supply unit (PSU) mounted in a matching enclosure, or can be powered from a suitable customer power supply. The units are neutrally coloured and designed to be unobtrusive in customer premises.

Rack mounting• When rack-mounted, the TN-1C and the standard TN-1P multiplexer are

held in the same enclosure as used for wall mounting and the entire enclosure is mounted on runners, in a standard ETSI or a 19 inch rack. In this situation, the multiplexer uses the rack PSU.

• TN-1P Basestation is mounted directly onto the framework structure in a standard ETSI or a 19 inch rack.

Street cabinet• TN-1C street cabinet installations (not illustrated) are wholly dependent

upon the street cabinet type. The TN-1C is mounted without the cover and can use the dual fan option (see page 1-28).

• TN-1P Basestation street cabinet installations (not illustrated) are wholly dependent upon the street cabinet type. TN-1P Basestation does not have a cover and can therefore be directly mounted without a fan.

TN-1PH rack mountingSufficient ventilation for a TN-1PH is provided through the fibre tray and upper (connection panel) part of the subrack, so that two TN-1PH subracks can be mounted in a 2.2 m rack (Figure 1-3). If two TN-1PH subracks are mounted in one 2.2 m ETSI rack, they must be mounted with a fibre tray between them, to maintain adequate ventilation. The two TN-1PH subracks must be fitted as near the top of the 2.2 m ETSI rack as possible so that future equipment can be installed.



ConnectivityChannel numbering schemes

The TN-1C and TN-1P use either the ITU-T ‘KLM’ or the ‘ETSI’ channel numbering schemes to identify aggregate payload instances. The user can enter aggregate payload instances using either the ‘KLM’ or ‘ETSI’ channel numbering scheme. All outputs from the TN-1C and TN-1P use the ‘KLM’ channel numbering scheme. When using the connection management facility on the Element Controller, the screens indicate the ‘KLM’ channel number and the equivalent ‘ETSI’ channel numbers.

KLM channel numberingThe ‘KLM’ channel numbering scheme uses a 3-figure vector (K, L, M) to represent channels within the virtual container (VC) payload structure:

• K = TUG-3 (1 to 3)

• L = TUG-2 (1 to 7)

• M = TU-12 (1 to 3)

The ‘KLM’ channel numbering scheme indicates the level of multiplexing, allowing a TUG-3 containing a single TU-3 to be distinguished from a TUG-3 containing seven TUG-2s. This allows, for example, differentiation of a VC-3 (34/45 Mbit/s) signal from a VC-12 (2 Mbit/s) signal:

• ‘1,2,3’ - indicates TUG-3 ‘1’, TUG-2 ‘2’, TU-1 ‘3’ (i.e. a 2 Mbit/s VC-12 signal)

• ‘2,0,0’ - indicates TUG-3 ‘2’ (i.e. a 34/45 Mbit/s VC-3 signal)

Table 1-1 provides cross-references between the ‘KLM’ numbering scheme and the ‘ETSI’ numbering scheme. The table also indicates the Nortel Networks numbering scheme which was used on previous releases.

Refer to ‘Appendix A: Synchronous digital hierarchy’ for further information about the SDH structure.



1Table 1-1Channel numbering schemes

TUG-3K

TUG-2L

TU-12M

ETSI(ITU-T)

Nortel TUG-3K

TUG-2L

TU-12M

Nortel ETSI(ITU-T)

111111111111111111111222222222222222222222333333333333333333333

111222333444555666777111222333444555666777111222333444555666777

123123123123123123123123123123123123123123123123123123123123123

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263

122434

25467

28491031521334551637581940612

23445

26478

29501132531435561738592041623

24456

27489

3051123354153657183960214263

123123123123123123123123123123123123123123123123123123123123123

111222333444555666777111222333444555666777111222333444555666777

111111111111111111111222222222222222222222333333333333333333333

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263

122434

25467

28491031521334551637581940612

23445

26478

29501132531435561738592041623

24456

27489

3051123354153657183960214263



Port/channel designationsConnections can be made to/from the following tributaries and aggregates.

Note: VC-3 operation is only possible for the TN-1C.

Tributary ports2 Mbit/s tributary ports are defined by the unit slot number and tributary instance in the form ‘Ss-n’ where:

• ‘s’ is the slot number within the multiplexer.

— for TN-1C, the slot numbers are ‘1’ for the main 8x2 Mbit/s ADM card and ‘2’ for the tributary extension card.

— for TN-1P, the slot number is always ‘1’.

• ‘n’ is the port number within the denoted slot. The available ports are as follows:

— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the main TN-1C ADM card.

— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the TN-1C 8 x 2 Mbit/s extension card.

— ‘1’ to ‘24’ for 2 Mbit/s tributaries on the TN-1C 24 x 2 Mbit/s extension card.

— ‘1’ or ‘2’ for 34/45 Mbit/s tributaries on the TN-1C 34/45 Mbit/s extension card

— ‘1’ to ‘4’ for 2 Mbit/s tributaries on the TN-1P 4 x 2 Mbit/s card.

— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the TN-1P 8 x 2 Mbit/s card.

For example:

• ‘S1-2’ is port 2 on the main TN-1C ADM card or the TN-1P.

• ‘S2-1’ is port 1 on the TN-1C extension card.

STM-1 aggregatesThe STM-1 aggregate channels can be defined using either the ‘KLM’ or the ‘ETSI’ numbering scheme.

• KLM numbering scheme

STM-1 aggregate channels are defined by the aggregate port and the KLM channel number in the form ‘sdh_port-J1-Kklm’.

Where:

— ‘sdh_port’ is either aggregate ‘A’ or ‘B’.

— ‘J1’ indicates the AU4 selection (always ‘J1’)

— ‘klm’ identifies a specific payload.

– for VC-12s, ‘k’= ‘1’ to ‘3’, ‘l’ = ‘1’ to ‘7’, ‘m’ = ‘1’ to ‘3’

– for VC-3s, ‘k’ = ‘1’ to ‘3’, ‘l’ = ‘0’, ‘m’ = ‘0’.



1For example,

— ‘A-J1-K261’ is TUG-3 ‘2’, TUG-2 ‘6’, TU-12 ‘1’ on aggregate A.

— ‘B-J1-K300’ is TUG-3 ‘3’ (i.e. a VC-3 signal) on aggregate B.

• ETSI numbering scheme

STM-1 aggregate channels are defined by the aggregate port and the ETSI channel number in the form ‘sdh_port-TUsize-payload_instance’.

Where:

— ‘sdh_port’ is either aggregate ‘A’ or ‘B’.

— ‘TU_size’ identifies the TU size and can be either ‘TU12’ or ‘TU3’.

Note: TU3 is not applicable to the TN-1P.

— ‘payload_instance’ is:

– ‘1’ to ‘63’ for TU-12s

– ‘1’ to ‘3’ for TU-3s

For example,

— ‘A-TU12-37’ is TU-12 ‘37’ on aggregate A.

— ‘B-TU3-3’ is TUG-3 ‘3’ (i.e. a VC-3 signal) on aggregate B.

High order payloadAggregate high order payloads identify the AU4 on an SDH aggregate (for VC-4 passthrough connections only). High order payloads are defined by the aggregate port in the form ‘sdh_port-J1’, where ‘sdh_port’ is either aggregate ‘A’ or ‘B’ (‘A-J1’ or ‘B-J1’).

Types of connectionsThe TN-1C and TN-1P support the following bidirectional connections:

• No connection:

If there is no connection, the channel is not in use. Therefore no low order path (LP) alarms and no TU alarms (TU-LOP and TU-AIS) are reported for this channel. No consequent actions will be initiated, and no performance monitoring (PM) logs relating to the channel are generated.

• Add/Drop connection:

A tributary signal is connected to a specific channel (TU) in the STM-1 signal. The 34/45 Mbit/s tributaries (TN-1C only) are associated with a TU-3, while the 2 Mbit/s tributaries are associated with TU-12s. For unprotected connections, the tributary is connected to one of the aggregate ports. For protected connections, an alternative payload instance in the other aggregate ports for path protection is specified.

Note: In the case of the protected connections, the same channel number must be used on the two aggregates.



• TU-12/TU-3 Through connection (TN-1C only):

A through connection connects matching channels between aggregates A and B.

• VC-4 passthrough connection:

A VC-4 passthrough connection connects the VC- 4 contained in the STM-1 signal between aggregates A and B. The VC-4 passthrough connection supports any traffic type carried by an STM-1 signal and when provisioned, all other path connections must be free. When a VC-4 passthrough connection is provisioned, only the RS, MS and AU-AIS alarms are enabled, all other traffic alarms are disabled and reported cleared. The VC-4s have no KLM numbers and are designated as A-J1 and B-J1.

Connection parametersThe connections are defined using the parameters ‘s_pl[&p_pl] d_pl [BI]’ where:

• ‘s_pl’ is the source payload instance.

• ‘&p_pl’ is the alternative source payload for protected connections.

• ‘d_pl’ is the destination.

— For add/drop tributary connections, the destination will be a tributary instance.

— For through connections (TN-1C only), the destination will be the same payload instance in the aggregate not selected for ‘s_pl’. For example, if A-J1-K261 is selected for the ‘s_pl’, B-J1-K261 should be selected for ‘d_pl’ to provide a through connection.

• ‘[BI]’ indicates bidirectional. As all connections on the TN-1C and TN-1P are bidirectional, this indicator can be omitted.

For example:

• ‘A-J1-K111 S1-1’ defines an unprotected add/drop connection between 2 Mbit/s tributary 1 on the TN-1C ADM or the TN-1P card and K111 in aggregate A.

• ‘A-J1-K200&B-J1-K200 S2-1’ defines a protected add/drop connection between tributary 1 on the TN-1C 34/45 Mbit/s extension card and TUG3 ‘2’ in aggregate A, with an alternative connection to TUG3 ‘2’ in aggregate B for path protection.

• ‘A-J1-K311 B-J1-K311’ defines a through connection between TUG-3 ‘3’, TUG-2 ‘1’, TU-12 ‘1’ in aggregate A and TUG-3 ‘3’, TUG-2 ‘1’, TU-12 ‘1’ in aggregate B.

• ‘A-J1 B-J1’ defines a bidirectional VC-4 passthrough connection between the VC-4 in aggregate A and the VC-4 in aggregate B.



1Default connectionsThe TN-1C (and TN-1P Basestation fitted with an 8 x 2 Mbit/s ADM card) defaults to having no connections. The TN-1P (4 x 2 Mbit/s tributaries) defaults to the following connections:

• Protected TN-1P

A-J1-K111&B-J1-K111 S1-1A-J1-K112&B-J1-K112 S1-2A-J1-K113&B-J1-K113 S1-3A-J1-K121&B-J1-K121 S1-4

• Unprotected TN-1P

A-J1-K111 S1-1A-J1-K112 S1-2A-J1-K113 S1-3A-J1-K121 S1-4

Note: The All Connect command can be used to make these default connections on a TN-1P. The command only works if there are no existing connections.

User labelsThe TN-1C and TN-1P provide a user label feature. This feature allows the user to give each connection a label consisting of up to 15 characters to assign customer names payloads or ports that are part of a connection. The allowable characters are the alpha-numeric characters (A to Z, a to z, 0 to 9), dash (-), and underscore (_). The user labels appear on all alarm and performance monitoring messages and reports associated with the connections. The display of user labels can be enabled or disabled by the user. The default labels associated with connections are as follows:

• For drop connections, the PDH port reference is used (for example, ‘S2-1’).

• For through connections (TN-1C only), the alternate aggregate payload reference is used (for example, ‘B-J1-K123’).

• For VC-4 through connections, the default user label is ‘J1’.

Traffic modeThe user can configure each TN-1C or TN-1P tributary input for one of four traffic modes:

• Traffic on

• Traffic off

• Traffic auto

• Traffic standby

The ‘traffic on’ state enables the tributary to carry traffic. The ‘traffic off’ state disables the traffic carrying capability and, with the exception of PPI-Unexp_Signal alarm, disables alarms associated with that particular tributary. In the ‘traffic off’ state, an AIS is sent towards the tributary line, and



a VC-UNEQ (i.e. the signal label ‘000’ for VC-12s or ‘0H’ for VC-3s) is sent towards the channel to which it is connected.

The ‘traffic auto’ state enables the tributary to carry traffic when it is part of a connection or is in the synchronization source hierarchy. When the tributary is not part of a connection and is not in the synchronization source hierarchy, PPI-AIS is sent and PPI performance monitoring (PM) counts are counted if traffic is present. Alarm behaviour is the same as the ‘traffic off’ mode. This is the default setting.

The ‘traffic standby’ mode allows a tributary that is part of a generally unused connection to carry traffic when the remote equipment is present. When a signal is detected, a PPI-Unexp_Signal alarm is raised. This alarm notifies the user to select ‘traffic auto’ mode for that tributary and the alarm is cancelled. When the signal is removed, a PPI-LOS alarm is raised, this notifies the user to reselect ‘traffic standby’ mode for the tributary. In the ‘traffic standby’ mode, PM counts are not counted for tributaries.

Path traceThe SDH path overhead provides a path trace capability which allows internal paths to be verified at the VC-4 level. The multiplexer allows the user to determine and display the contents of the path trace string. This is useful as a means of checking the optical fibre connections whenever changes are made.

The path trace identifier can be provisioned by the user for each STM-1 link and for each direction (receive/transmit) separately. The user can also display the actual received pattern for maintenance purposes. When a VC-4 passthrough connection is in operation, the path trace identifier for both aggregates can be viewed at the network element, although it can not be provisioned.

The VC-4 path overhead bytes contain a path trace byte (J1). This byte is used to cyclically transmit a 16 byte string. The string comprises a frame starter marker byte (which contains a CRC-7 calculation over the previous frame) and 15 user configurable bytes. The checksum can be either automatically generated by the system, or entered by the user. The incoming string is checked against the expected receive string, any discrepancy generates a HP-Path_Trace alarm.

Note: The default settings are ‘RX_UNALLOCATED_’ for the receive value and ‘TX_UNALLOCATED_’ for the transmit value.

For example, if two multiplexers (A and B) are connected together, the user may set the transmit value of multiplexer ‘A’ to ‘route_1_AtoB’ and the receive value of multiplexer ‘B’ to ‘route_1_AtoB’. Likewise, the transmit value of multiplexer ‘B’ may be set to ‘route _1_BtoA’ and the receive value of multiplexer ‘A’ to ‘route_1_BtoA’.

Refer to Browser User Guide, 323-1081-403 and Network Administration Procedures, 323-1081-310 for further details of the operation of the path trace facility.



1Note: The TN-1C and TN-1P do not process the RS path trace byte (J0) and the low order path trace byte (J2). Minor problems can occur when interconnecting with equipment that support these bytes (for example, the OPTera Metro 4100 supports the J0 byte on STM-1 tributary cards). The problems are related to service assurance and are not traffic or service affecting.

Signal labelThe path overhead of the SDH includes signal label information which indicates the composition of the signal. The signal labels (except VC-4) are automatically set according to the traffic status (on/off/auto/standby) as defined in Table 1-2.

If the received signal label is not as expected, a HP-PLM (VC-4) or LP-PLM (VC-12 and VC-3) alarm is raised.

Table 1-2Signal label data

VC level Traffic on Traffic off Traffic auto Traffic standby

Connection present or in sync hierarchy, traffic present

Connection present, traffic present

Connection present, no traffic

VC-12(bits 5 to 7 of V5 byte)

Transmit value

‘010’ - Asynchronous floating

‘000’ - Unequipped



‘000’ unequipped

Expected receive value

‘010’ - Asynchronous floatingor ‘001’ - Equipped non-specific

‘000’ - Unequipped




VC-3(C2 byte)(TN-1C only)

Transmit value

‘04H’ - Asynchronous Mapping of 34/45 Mbit/s

‘00H’ - Unequipped



‘00H’ unequipped


‘04H’ - Asynchronous Mapping of 34/45 Mbit/sor ‘01H’ - Equipped non-specific

‘00H’ - Unequipped




VC-4(C2 byte)

Transmit value

‘02H’ - TUG structure


‘02H’ - TUG structure‘01H’ - Equipped non-specificor‘13H’ - ATM mapping



Path protection switchingPath protection switching (PPS) is provided by the multiplexer. Switching occurs at the following levels to provide protection over the entire path:

• for 2 Mbit/s signals: TU-12 level,

• for 34/45 Mbit/s signals: TU-3 level

Note: The TU-3 level is applicable to the TN-1C multiplexer only.

The transmitting multiplexer sends the same data on both optical paths and the receiving multiplexer, demultiplexes the signals from both aggregates and monitors the validity of all incoming TU-12s and TU-3s.

On receipt of invalid TU-12s or TU-3s, the receiving network element switches to the equivalent TU-12 or TU-3 from the standby optical link, providing protection against a fault in the working path. Path protection switching is non-revertive, that is, when the failed link is restored, it becomes the standby; the receiving multiplexer only switches paths in the event of a path failure. The user may select (with the User Interface) which aggregate to use as the working path and, if required, may enable or disable PPS.

Further details of path protection switching are given in ‘Path protection’ on page 2-13.

Management and communicationsThe TN-1C and TN-1P network elements are managed using application software embedded within each network element. The configuration and status information is stored in each network element and not in the management tools used to control them.

The network element can be monitored and configured using the Browser User Interface or the Command Line User Interface. The Browser is an HTML interface to the network element application software and presents the results as an intuitive point-and-click interface inside the Netscape Navigator hypertext browser. The Command Line User Interface is accessed using terminal application software.

The Browser and the Command line User Interface can be accessed as follows:

• locally from a craft access terminal (CAT) connected directly or remotely to the network element,

• from the Element Controller EC-1

• via reach through from Nortel Networks Preside manager.

Communication with the EC-1 is via the embedded control channel (ECC) in the section overhead of the STM-1 signals and/or LANs. The EC-1 can manage TN-1C, TN-1P, TN-1X, and TN-4XE network elements and provides additional alarm and monitoring facilities. The EC-1 also interfaces to the higher level of network management such as Nortel Networks Preside.



1The CAT can be connected directly to each network element to manage its operation locally, or may be used to manage a remote ‘partner’ network element.

Rack alarm adaptorWhen the TN-1C or standard TN-1P are rack mounted, they can use an optional external rack alarm adaptor (RAA) that allows the TN-1C or TN-1P, via its external alarm facility, to drive a rack alarm system. The RAA provides two alarm status LEDs and an alarm receiving attention button. The RAA derives its power supply (–48 V d.c. at up to 120 mA) from the rack. The TN-1PH multiplexer has a built-in rack alarm adaptor.

A rack alarm adaptor is not used with TN-1P Basestation.

SoftwareEach TN-1P and TN-1C multiplexer card has two flash memory banks to hold software, banks ‘A’ and ‘B’. These flash memory banks hold individual copies of the application software. The boot sector of bank ‘A’ holds the foundation software.

There are two types of software associated with the multiplexer:

• foundation software

• application software

For more information, refer to “Software” on page 3-6.

Foundation softwareThe foundation software is executed at system start-up or reset. It is a short program that selects one of the two application software banks. The foundation software selects the bank as follows:

• after a cold (traffic affecting) restart, occurring at system switch-on or when the user requests a cold restart, the current bank is used.

• after a warm (non-traffic affecting) restart, the bank is selected by the user (default is current bank).

A checksum is performed on the selected software, if the test is successful, that software is run. If the first software bank fails the checksum, the second bank is tested; if this passes the test then it will be run. Failure of both software banks causes an error and the system is rendered inoperative.

Application softwareThe application software resides in two flash memory banks and can be functionally subdivided into two main areas:

• Operations software

• User interface software



The operations software controls the operation and equipment management functions of the multiplexer (e.g. multiplexing, communication, alarm monitoring and synchronisation).

The equipment management functions of the multiplexer are performed by the synchronous equipment management function (SEMF) of the multiplexer application software.

The user interface software is a hierarchical, text-based user interface which allows an operator to configure and control the method of operation of the network element. This is accessed using a CAT running VT-100 emulation software, or via the EC-1.

Software downloadDuring the operational life of the multiplexer, new versions of the application software can be downloaded using the user interface from the CAT or the EC-1.

InterfacesA connector panel provides the external connections to each multiplexer. For further information on connector panel configurations, refer to ‘External interfaces’ on page 8-1.

FanA fan is fitted to the EMC enclosure of the TN-1C, TN-1P (not at Release 5), TN-1P Basestation (not at Release 5). A fan is not fitted to the TN-PH.

The fan can be controlled automatically or manually:

• With automatic control: The fan switches on when the temperature exceeds 55° C and switches off when the temperature falls below 40° C.

• With manual control: The fan is switched on and off from the user interface (UI). With manual control, a short delay exists between the fan on/off command and the fan operation.

Where the TN-1C is operated in particularly harsh environments an optional second fan can be installed. The second fan only operates if the first fan fails, but does not clear the NE-Fan_Failed alarm. The second fan maintains the correct working temperature until an engineer replaces the first fan.

WARNINGRotating fan bladesTake care when the working on a TN-1C /TN-1P without a cover as the fan blades are accessible.



1VariantsTN-1C

Each TN-1C variant currently available can be either wall, rack or street cabinet mounted. The variants are summarized in Table 1-3.

Each variant can be supplied with the following optical interfaces:

• short reach (1310 nm) S1.1 optics.

• long reach (1310 nm) L1.1 optics.

• long reach (1550 nm) L1.2 optics.

Table 1-3TN-1C variants

Variant ADM card(see Note 3)

Tributary extension card(see Note 3)

Enclosure

8 x 2 Mbit/s 8 x 2 Mbit/s Dummy card Plastic

8 x 2 Mbit/s +1 x 34/45 Mbit/s

8 x 2 Mbit/s 1 x 34/45 Mbit/s Plastic


8 x 2 Mbit/s 2 x 34/45 Mbit/s Plastic

16 x 2 Mbit/s 8 x 2 Mbit/s 8 x 2 Mbit/s Plastic

32 x 2 Mbit/s 8 x 2 Mbit/s 24 x 2 Mbit/s Plastic (see note 1)

8 x 2 Mbit/s 8 x 2 Mbit/s Dummy card Metal (see note 2)

16 x 2 Mbit/s 8 x 2 Mbit/s 8 x 2 Mbit/s Metal (see note 2)


8 x 2 Mbit/s 1 x 34/45 Mbit/s Metal (see note 2)


8 x 2 Mbit/s 2 x 34/45 Mbit/s Metal (see note 2)

Note 1: Thirty-two 2 Mbit/s connections are only available when using 120 Ω connection interfaces. When using mixed 75 Ω/120 Ω connection interfaces, a maximum of twenty-four 2 Mbit/s connections are possible.

Note 2: This configuration is available as part of TN-1C Release 3/5 and cannot be ordered at Release 5.1.

Note 3: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s ADM card and the 8 x 2 Mbit/s tributary extension card are configurable to either 75 Ω or 120 Ω. The impedances for the first eight 2 Mbit/s tributaries of the 24 x 2 Mbit/s tributary extension card are configurable to either 75 Ω or 120 Ω, the remaining sixteen 2 Mbit/s tributaires are 120 Ω only.



ADM cardFour variants of ADM card are available:

• Release 1 hardware 8 x 2 Mbit/s

• Release 3/5/5.1 hardware 8 x 2 Mbit/s (short reach 1310 nm optics)

• Release 3/5/5.1 hardware 8 x 2 Mbit/s (long reach 1310 nm optics)

• Release 3/5/5.1 hardware 8 x 2 Mbit/s (long reach 1550 nm optics)

Note: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s ADM card are configurable to either 75 Ω or 120 Ω.

Tributary extension cardThe TN-1C tributary extension card can be one of the following:

• 8 x 2 Mbit/s tributaries (Release 1 hardware)

• 8 x 2 Mbit/s tributaries with enhanced performance monitoring (framed and CRC-4 functionality) (Release 3/5 hardware)

• 8 x 2 Mbit/s tributaries (Release 5.1 hardware)

• 24 x 2 Mbit/s tributaries (Release 5.1 hardware)

• 1 x 34/45 Mbit/s tributary (Release 3/5 hardware)

• 1 x 34/45 Mbit/s tributary with 45M AIS support (Release 5.1 hardware)

• 2 x 34/45 Mbit/s tributaries (Release 3/5 hardware)

• 2 x 34/45 Mbit/s tributaries with 45M AIS support (Release 5.1 hardware)

Note 1: If a tributary extension card is not fitted, a dummy card must be fitted in its place to comply with electro-magnetic compatibility (EMC) requirements.

Note 2: For details of the optional Packet Edge 10 router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

Note 3: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s tributary extension card are configurable to either 75 Ω or 120 Ω. The impedances for the first eight 2 Mbit/s tributaries of the 24 x 2 Mbit/s tributary extension card are configurable to either 75 Ω or 120 Ω, the remaining sixteen 2 Mbit/s tributaires are 120 Ω only.

Connector panelFor Release 5.1 hardware, there are two types of connector panel (one for TN-1C with extension slot and one for the single-slot TN-1C). For earlier releases, there are a number of different connector panels. For further information on connector panels, refer to ‘External interfaces’ on page 8-1.



1TN-1PThe following TN-1P variants are available at Release 5.1:

• TN-1P with 4 x 2 Mbit/s tributaries and an unprotected optical link (the multiplexer card has one electro-optical module).

• TN-1P with 4 x 2 Mbit/s tributaries and a protected optical link (the multiplexer card has two electro-optical modules to provide 1+1 protection).

• TN-1PH Headend with 4 x 2 Mbit/s tributaries and an unprotected optical link (the multiplexer card has one electro-optical module).

• TN-1PH headend with 4 x 2 Mbit/s tributaries and a protected optical link (the multiplexer card has two electro-optical modules to provide 1+1 protection).

• TN-1P Basestation with 4 x 2 Mbit/s tributaries and an unprotected optical link (the multiplexer card has one electro-optical module).

• TN-1P Basestation with 4 x 2 Mbit/s tributaries and a protected optical link (the multiplexer card has two electro-optical modules to provide 1+1 protection).

• TN-1P Basestation with 8 x 2 Mbit/s tributaries and a protected optical link (the multiplexer card has two electro-optical modules to provide 1+1 protection or ADM functionality).

All the TN-1P variants use short reach (1310 nm) S1.1 optics.

Connector panelFor Release 5.1 hardware, there is only one type of connector panel. Earlier releases, have different connector panels. For further information on connector panel variants, refer to ‘External interfaces’ on page 8-1

end of chapter


2-12

Equipment description 2-The TN-1C/TN-1P network element multiplexes tributary inputs into an STM-1 signal for transmission over an optical link to a remote network element or into an SDH network. In the receive direction, the TN-1C/TN-1P network element demultiplexes an incoming STM-1 signal from the optical link to provide tributary outputs.

Figure 2-1 and Figure 2-2 show simplified block diagrams of the TN-1C and TN-1P.

The TN-1C can provide any one of the following bi-directional electrical tributary options:

• eight 2 Mbit/s tributaries

• sixteen 2 Mbit/s tributaries

• thirty-two 2 Mbit/s tributaries

• eight 2 Mbit/s tributaries and one 34/45 Mbit/s tributary

• eight 2 Mbit/s tributaries and two 34/45 Mbit/s tributary

The TN-1C has two STM-1 optical inputs and outputs, to provide bidirectional protected operation.

Note: For details of the optional router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

The standard TN-1P has four 2 Mbit/s bidirectional tributaries in each direction. The standard TN-1P can have either one STM-1 input and output (unprotected) or two STM-1 inputs and outputs (protected).

The following versions of the TN-1P Basestation are available at Release 5.1:

• TN-1P Basestation with 4 x 2 Mbit/s unprotected multiplexer card and S1.1 optics

• TN-1P Basestation with 4 x 2 Mbit/s protected multiplexer card and S1.1 optics

• TN-1P Basestation with 8 x 2 Mbit/s ADM card and S1.1 optics

Note: The 4 x 2 Mbit/s versions can be upgraded to the 8 x 2 Mbit/s ADM version by replacing the multiplexer card.

2-2 Equipment description


The TN-1C and standard TN-1P are provided in a stand-alone enclosure. The enclosure may be wall-mounted with an a.c. mains driven d.c. power supply (or it may be powered from a suitable customer power supply), or mounted in a rack (in which case it is powered from the rack power supply). The nominal a.c. mains supply is 115/230 V.

The TN-1P Basestation has no enclosure. The TN-1P Basestation is mounted in a rack and powered from the rack power supply, nominally –48 V d.c. The multiplexers require an operating supply voltage in the range –20 V to –72 V d.c.

Note: This equates to nominal earthed battery station voltages between –24 V and –60 V.

The TN-1PH Headend subrack is also available, which contains the following:

• up to 12 TN-1P main point-to-point packs (MPP), each of which has the functionality of one TN-1P.

• a subrack end processor (SEP), which provides a LAN connection for an element controller EC-1 and consolidates the CAT access and alarms for the multiple TN-1P MPPs.

• a craft access panel (CAP), which provides:

— status indications,

— an alarm acknowledge push-button,

— a means of selecting the CAT to each individual TN-1P MPP.

• A connection panel which provides connections for all of the electrical tributaries, power, and support functions (CAT and LAN)

Equipment description 2-3


2

Figure 2-1TN-1C block diagram

Timing source

Power supply

VC-3

VC-12Timeslot

interchanger

VC-3

VC-12Timeslot

interchanger

STM-1interface

STM-1interface

Aggregate AAggregate B

STM-1 interface

Extension cardinterface

PDHMapper

PDH LineInterfaceT

ribut

ary

Ext

ensi

on c

ard*

STM-1 interface

G.703 interfaces

G.703 interfaces

Trib

utar

y bl

ock

PDHMapper

PDHLine

Interface

Con

trol

ler

plat

form

(C

PU

, FLA

SH

& D

RA

M m

emor

ies

& o

ther

per

iphe

rals

)

LAN

Inte

rfac

eC

AT

Inte

rfac

eA

TU

Inte

rfac

eE

xter

nal a

larm

s(R

S-2

32)

RS

-485

Inpu

ts &

Out

puts

Mai

n A

DM

car

d

Ext

erna

l syn

cin

terf

ace

* Not applicable to single-slot TN-1C variants.



Figure 2-2TN-1P block diagram

Timing source

Power supply

VC-12Timeslot

interchanger

VC-12Timeslot

interchanger

STM-1interface

STM-1interface

Aggregate AAggregate B

STM-1 interfaceSTM-1 interface

G.703 interfaces

Trib

utar

y bl

ock

Extension PDH

Mapper

PDHLine

Interface

Con

trol

ler

plat

form

(C

PU

, FLA

SH

& D

RA

M m

emor

ies

& o

ther

per

iphe

rals

)

LAN

Inte

rfac

eC

AT

Inte

rfac

eA

TU

Inte

rfac

eE

xter

nal a

larm

s(N

ote

2)(R

S-2

32)

RS

-485

Inpu

ts &

Out

puts

Ext

erna

l syn

cin

terf

ace

(Not

e 1)

Note 1: External Synchronisation input available only for a TN-1P upgraded to an 8 x 2 Mbit/s ADM.Note 2: LAN interface available only for a TN-1P Headend and a TN-1P upgraded to an 8 x 2 Mbit/s ADM.



2

Power suppliesExternal

The external power supply is wall mounted and is in a similar enclosure to the multiplexer unit. Its output voltage is –24 V d.c. A rack mounted multiplexer uses the rack power supply and does not require the external power supply unit. For more information see ‘Power supply unit’ on page 4-1.

Internal power supplyEach multiplexer unit, has its own point-of-use power supply (PUPS) which can operate with an input voltage in the range –20 V to –72 V d.c. The SEP in the TN-1PH also has a PUPS that can operate with an input voltage in the range –36 V to –72 V d.c. as follows:

• TN-1C and TN-1P (wall mount): a nominal –24 V d.c. from the external power supply (although it can accept voltages in the range –20 V to –72 V d.c.)

• TN-1C and TN-1P (rack mounted): a nominal –48 V d.c. from the rack power supply (although it can accept voltages in the range –20 V to –72 V d.c.).

• TN-1P Basestation (rack mounted): a nominal –48 V d.c. from the rack power supply (although it can accept voltages in the range –20 V to –72 V d.c.).

• TN-1P Headend: a nominal –48 V d.c. from the rack power supply (although it can accept voltages in the range –36 V to –72 V d.c.).

The PUPS is divided into two functional blocks. The two functional blocks are electrically isolated, power is supplied through a transformer and feedback through an opto-isolator:

• Primary power train — provides a.c. output to the secondary power train and protection against electromagnetic interference (EMI) and excessive start-up current. It also provides an indication of low input voltage from the external power supply.

• Secondary power train — provides a clean d.c. output which is compared to a reference, the error is fed back to the primary power train. It also provides output overvoltage protection.

CAUTIONIncorrect d.c. polarity on TN-1P HeadendEnsure that the correct polarity rack power supply is connected.



Timing sourceClock generator

The clock generator produces a timing source for the multiplexer from an incoming STM-1 signal, a selected 2 Mbit/s tributary or an external source (TN-1C and TN-1P ADM card upgrades only). The clock generator produces the system clock for system operation and data transmission.

System clockA voltage controlled crystal oscillator (VCXO) generates a 19.44 MHz system clock. This internal clock provides PDH compliant tributary signals, but when connected to an SDH network, external synchronization from the aggregate or an external source is the preferred option. The system clock also provides synchronization timing for the TN-1C tributary extension card.

Controller platformThe controller platform controls the operation of the whole multiplexer, including all configuration, provisioning, real-time and communication functions.

ProcessorThe processor is equipped with a watchdog function which ensures program integrity.

RestartTwo types of restart are provided on the multiplexer:

• cold restart - a hardware reset is performed on system power-up and held for 600 ms until power is stabilized. You can request a cold restart from the user interface. A cold restart is traffic affecting.

• warm restart - if a software fault or processor overload occurs, the software is reset. This does not affect the traffic. Warm restart can be initiated from the user interface. A warm restart is also started during the software upgrade process and the configuration upgrade process. For detailed descriptions of these processes, see System and System Administration Procedures, 323-1081-302.

0

MemoryThe multiplexer has four different areas of memory:

• volatile memory for microprocessor data stack functions (dynamic RAM).

• application memory - non-volatile memory that holds the multiplexer application software (two banks) of Flash - electrically erasable programmable read only memory (EEPROM).

• foundation memory - non-volatile memory that holds the multiplexer foundation software (stored in the same flash as the application memory).

• configuration memory - non-volatile memory (EEPROM) that holds the programmable configuration data.



2

The multiplexer allows two versions of application software to be stored in banks A and B of the non-volatile flash memory. Only one version of multiplexer application software is selected at any given time. The user can switch between the two versions of application software, until committing to the most recently loaded version. The new data is then written into both banks. Refer to ‘Equipment management’ on page 3-1 for further details.

Serial communicationsThe multiplexer has the following communication links:

• Software programmable serial channel on the embedded control channel (ECC) regenerator section and multiplex section overhead, which operates at either:

— 192 kbit/s and uses bytes D1 to D3 (regenerator section overhead)

— 576 kbit/s and uses bytes D4 to D12 (multiplex section overhead)

(see ‘Section overhead’ on page 10-11).

• RS-232 channel for CAT operation.

• one RS-232C interface (used by TN-1C Release 1 hardware and TN-1P to support the asynchronous telemetry unit (ATU) feature)

• one point-to-multipoint RS-485 interface (used by TN-1C Release 3 hardware to support the ATU feature)

• One 10BaseT LAN channel for remote network element management using a Element Controller (TN-1C, TN-PH and TN-1P ADM card upgrades only).

STM-1 interfaceThe STM-1 interface can be divided into three functional blocks:

• electro-optical interface - provides the conversion between electrical and optical signals.

• dual serial-to-parallel Interface (DSPI) - provides high speed conversion from 155.52 MHz serial to 19.44 MHz, 8 bit parallel data and vice-versa. The DSPI also provides a divide-by-eight clock, derived from the high frequency serial input. The parallel to serial conversion is buffered to compensate for differences between input clock and the derived clock.

• STM-1 processor - is an application specific integrated circuit (ASIC) which can receive and transmit STM-1 frames conforming to the SDH protocol. The receiver performs frame alignment and overhead termination. The transmitter performs overhead generation only.

Timeslot interchangerThe timeslot interchanger (TSI) is an ASIC which performs the following functions:

• Extracts the AU pointer which is used to locate the start of the VC-4 container.

• Extracts and processes the VC-4 path overhead bytes.

• Synchronizes the pointer of each TU to the local multiframe.



• Performs the TU reordering, if required. Dropped TUs are output to the PDH Mapper circuits. Insert TUs are combined with the through path TUs.

• Generates the VC-4 path overhead bytes and sets the AU pointer value.

Multi-channel tributary blockThe multi-channel tributary block carries out the interfacing and mapping of tributary PDH signals. It contains the following two blocks:

• PDH mapper - incorporates the functions of low-order path (VC-3/VC-12) path termination, generation, rate adaption, 34/45 Mbit/s and 2 Mbit/s mapping. VC-3 (34/45 Mbit/s) applicable to TN-1C only.

• PDH line interface - comprises a G.703 transmitter/receiver, line interface, and a pseudo random binary sequence (PRBS) generator/detector.

Extension card interface (TN-1C only)Note: The tributary extension card is not applicable to single-slot TN-1C variants.

The interface to the tributary extension card allows the drop/insert TU data to be processed by the appropriate tributary extension card. The user must equip the extension card by specifying the full card type. The card type consists of two parts:

• Major

This specifies the basic service provided by the card, for example an 8x2 Mbit/s tributary extension.

• Minor

This specifies the specialist characteristics of the card, for example a card that supports frame structured 2 Mbit/s signals.

If the actual card and the user specified card type are different, functionality is lost and alarms are raised. If the Major part is incorrect, an NE-Wrong_Card alarm is raised and no functionality is provided. If the minor part is incorrect, an NE-Minor_Card_Mismatch alarm is raised. Configuration changes are available only for the card type that is equipped. Functionality is limited to a subset of the actual card type and the equipped card type.

Traffic processingTN-1C options

The following options are available for the TN-1C (see Figure 2-3):

• up to eight 2 Mbit/s inputs/outputs using the ADM card

• up to eight 2 Mbit/s inputs/outputs using the ADM card and one 34/45 Mbit/s inputs/output using a 34/45 Mbit/s tributary extension card

• up to eight 2 Mbit/s inputs/outputs using the ADM card and up to two 34/45 Mbit/s inputs/outputs using a 2 x 34/45 Mbit/s tributary extension card

• up to eight 2 Mbit/s inputs/outputs using the ADM card and eight 2 Mbit/s inputs/outputs using a 8 x 2 Mbit/s tributary extension card



2

• up to eight 2 Mbit/s inputs/outputs using the ADM card and 24 x 2 Mbit/s inputs/outputs using a 24 x 2 Mbit/s tributary extension card

• 1+1 protected STM-1 interfaces

Note: For details of the optional router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

TN-1P optionsThe following options are available for the TN-1P (see Figure 2-4):

• up to four 2 Mbit/s inputs and outputs using the multiplexer card

• unprotected or 1+1 protected STM-1 interfaces.

TN-1P Basestation optionsThe following options are available for the TN-1P Basestation (see Figure 2-4):

• up to four 2 Mbit/s inputs and outputs using the multiplexer card, with unprotected or 1+1 protected STM-1 interfaces

• up to eight 2 Mbit/s inputs and outputs using the multiplexer card, with 1+1 protected STM-1 interfaces



Figure 2-3TN-1C traffic processing

PDH mapper

2 Mbit/s tributaries and line interface

2 Mbit/s electrical ports

Trib

utar

y bl

ock

Trib

utar

y E

xten

sion

car

d

PDH mapper

34/45 Mbit/s tributary

and line interface

TimeslotInter-

changer

STM-1Processor

Dual Serialto parallelinterface

Electro-optical

interface

STM-1o

STM-1Processor


Electro-optical

interface

STM-1 interface

Electro Optical ModuleElectro Optical Module

STM-1 interface

STM-1o

TimeslotInter-

changer

34/45 Mbit/s electrical ports

PDH mapper



PDH mapper


Trib

utar

y bl

ock


PDH mapper


2 Mbit/s electrical portsTr

ibut

ary

bloc

k

Option 1 Option 2Option 3

1x

34/4

5M

bit/s

or

2x

34/4

5M

bit/s

8 x

2M

bit/s

or

24 x

2M

bit/s

Trib

utar

y ex

tens

ion

card



2

Figure 2-4TN-1P traffic processing

Transmit traffic path (2 Mbit/s to STM-1)The tributary interface receives incoming signals in HDB3 format and converts these signals to four 2 Mbit/s binary data streams, which are passed to the PDH mapper. The PDH mapper then extracts a clock signal and synchronizes the signals and maps the signals asynchronously to VC-12 tributary format. The TU-12 overhead and pointers are generated and the signal is passed to the TSI.

Data arrives at the TSI ASIC in 8 kHz partially filled frames. The 19.44 MHz system clock is used to clock incoming data onto the gate array and the outgoing data to the output. Multiframe synchronization is used to indicate the first byte of the frame. The AU pointer is added and the data, in 8 kHz STM-1 frames with only the AU pointer in the overhead, is passed to the STM-1 processor ASIC.

The STM-1 processor ASIC multiplexes section overhead bytes onto the payload data and scrambles the data byte-by-byte. The data is then passed to the DSPI where it is re-organized into a 155.52 Mbit/s serial stream aligned to an internal high frequency clock (19.94 MHz). It is then passed to the electro-optical interface where it is converted to a 155.52 Mbit/s optical signal for transmission.

PDH mapper

Up to four 2 Mbit/s electrical ports(or up to eight in the TN-1P

Basestation with the ADM card fitted)

Trib

utar

y bl

ock

TimeslotInter-

changer

STM-1Processor


Electro-optical

interface

STM-1o

STM-1Processor


Electro-optical

interface

STM-1 interface

Electro Optical ModuleElectro Optical Module

STM-1 interface

STM-1o

TimeslotInter-

changer


Note: This figure shows a protected variant. The unprotected variant is similar but has only one electro-optical module.



The processor supports loopback of the receive signal to the transmit signal and vice versa.

0

Receive traffic path (STM-1 to 2 Mbit/s)The electro-optical module receives the STM-1 (155.52 Mbit/s) optical signal and converts it to a serial electrical signal. The DSPI ASIC then converts the electrical signal into an 8-bit 19.44 MHz parallel signal. The 19.44 MHz clock signal is extracted and the incoming STM-1 frames are aligned and descrambled. The overhead bytes are then terminated leaving the data as STM-1 frames with only AU pointers in the overhead. Differences in received line timing and local equipment timing are accommodated by the pointer processing unit. Output from the STM-1 processor is then passed to the TSI ASIC, aligned to the system clock and in multiframe synchronization.

The STM-1 processor provides a free running 8 kHz clock from the received optical byte clock, which is used to synchronize the system clock to the incoming signal.

The data is received from the STM-1 ASIC in 8 kHz STM-1 frames with only AU pointer bytes in the overhead. The AU-4 pointer information is extracted and used to locate the start of the VC-4. The VC-4 path overhead data is terminated and processed and the TUs are realigned to the local start of the VC-4 payload and new TU pointers are generated.

The TUs are reordered and sent to the PDH mapper in 8 kHz frames at 19.44 Mbyte/s. Here, overhead termination of the four TU-12s takes place, the pointers are extracted to locate the VC-12s which are then mapped asynchronously to 2 Mbit/s channels and converted from binary to HDB3 format in the 2 Mbit/s line interface.

Transmit traffic path (Tributary extension card, 34/45 Mbit/s to STM-1, TN-1C only)

Apart from the traffic being received in HDB3/B3ZS format respectively at the tributaries and the PDH mapping of the signals asynchronously to VC-3 tributary format, data is processed in exactly the same way as in the 2 Mbit/s transmit traffic path.

Receive traffic path (Tributary extension card, STM-1 to 34/45 Mbit/s, TN-1C only)

The operation of this receive traffic path of the tributary extension card is identical to that of the receive traffic path (STM-1 to 2 Mbit/s). However, in this particular case when the pointers are being extracted, it is the VC-3s which are mapped asynchronously to 34/45 Mbit/s channels and converted from binary to HDB3/B3ZS format respectively in the 34/45 Mbit/s line interface.

Transmit/Receive traffic path (Tributary extension card, 2 Mbit/s, TN-1C only)

The operation of the transmit/receive traffic path circuitry, on the tributary extension card, is identical to the 2 Mbit/s circuitry within the tributary block.



2

Path protectionPath protection switching (PPS) is not available on the TN-1P, TN-1PH or TH-1P Basestation unprotected variants.

The TN-1C and the protected variants of the TN-1P, which have two STM-1 interfaces, support PPS. PPS provides protection over the whole VC-12 path regardless of the SDH network in use. For the 34/45 Mbit/s variant of the TN-1C, PPS is provided also over the whole VC-3 path.

The multiplexer monitors the validity of the incoming TUs from the two STM-1 links, and uses a valid TU.

In the case of a failure in a TU-12 path, it is considered unavailable for use. If the selected path fails and the other path is available, then the data is switched to be received from the available path (i.e. it is now the selected path).

Holdoff periodSwitching is performed immediately by default although the user may set a holdoff period, which is a delay between detection of a fault and subsequent switching. No holdoff period is implemented if the detected defect is of RS/MS/AU/HP level. The holdoff time is selectable in the multiplexer between 0.1 and 20 seconds, and the holdoff operation can be enabled/disabled for each tributary.

Oscillation guard timeOscillation guard time is the length of time that PPS is disabled after an automatic protection switch. It prevents reversion to the original failed path before the system has stabilised and subsequent oscillation between the two paths. The oscillation guard time is between 1 and 30 seconds and is specified in seconds.

ReversionPath protection switching is non-revertive; after a switch and subsequent fault clearance, the operation is not switched back to the original user selected path. Switching only occurs when the selected path fails.

Priority controlFor path protected connections, a user interface command implicitly determines the source path and the alternative source path. Subsequent PPS changes the source path, but the following conditions apply:

• the configuration report shows the configured order and does not change as a result of a PPS.

• Software upgrades, warm restarts and configuration switch do not cause a PPS if the current source path is not the originally configured source path.



PPS criteriaTable 2-1 shows the criteria that will cause a path protection switch.

Automatic laser shutdown

The TN-1C and TN-1P optical aggregate units contain an automatic laser shutdown (ALS) circuit which shuts down the laser if an Optical Power High (OS-Optical_Power_High) alarm or an STM Loss of Signal (RS-LOS) alarm

Table 2-1PPS switching criteria

Alarm Explanation

PPS criteria causing a path protection switch on all TUs

RS-LOS STM-1 Loss of Incoming Signal

RS-LOF STM-1 Loss of Frame alignment

MS-AIS Multiplexer Section Alarm Indication Signal

MS-EXC Multiplexer Section Excessive Bit Error Signal

AU-AIS Administrative Unit Alarm Indication Signal

INT-AU-AIS Internal Administrative Unit Alarm Indication Signal

INT-AU-LOP Internal Administrative Unit Loss Of Pointer

HP-PLM High order Path Signal Label Mismatch (see Note 1)

HP-LOM High order Path Loss Of Multiframe

HP-TIM High order Path Trace Identifier Mismatch (see Note 1)

PPS criteria causing a path protection switch on individual TUs

TU-AIS Tributary Unit Alarm Indication Signal

TU-LOP Tributary Unit Loss Of Pointer

LP-EXC Low order Path Excessive BER (see Note 2)

Note 1: The Consequent Action configuration facility allows the user to disable switching on receipt of HP-PLM and HP-TIM alarms.

Note 2: The Consequent Action configuration facility allows the user to disable switching (on a per tributary port basis) on receipt of an LP-EXC alarm.

WARNINGLaser radiationDo not stare into a laser beam. Do not view fibres directly with optical instruments unless you are certain that the fibres are not active.



2

occurs. This prevents excessive optical power being radiated from a broken fibre or an unterminated optical connector.

The ALS operation is automatically disabled during the first 90s from a cold start. Using a UI command during the first 90s from a cold start, maintenance personnel may suspend the ALS operation permanently. This enables maintenance tasks to be carried out. After the maintenance tasks are carried out, the ALS operation may be returned to normal by a further command from the UI.

During fault-free operation, both multiplexers on both sides of the link have their optical unit lasers ‘on’. The laser shutdown mechanism operates independently for each STM-1 link and may activate for the following reasons:

• If either or both multiplexers detect an RS-LOS indication present for at least 550 ± 50 ms, its laser is shutdown. If the RS-LOS alarm clears (for at least 100 ± 20 ms), the laser is switched back on immediately.

• If either or both multiplexers detect an OS-Optical_Power_High alarm its laser is shutdown immediately. The laser can not be restarted until the unit is reset (e.g. removed and replaced in the subrack).

In certain networks it can be necessary for an engineer to be able to force the laser on at any time, to provide more convenient testing.

Only a system engineer has authority to force the laser on at any time. The following safety features are associated with the force laser on feature:

• The laser force on feature can only be used from a local login, by a craftsperson working at the TN-1C. The feature is not available from the element controller.

• An OS-Optical_Power_High alarm does not affect the use of the allow/disallow force feature, but the alarm does shut down the laser.

LoopbacksA loopback facility on the multiplexer enables the user to perform test procedures for fault finding. The following loopbacks may be initiated by the user:

STM-1 local loopbackA local (‘near-end’ or ‘loop to mux’) loopback can be performed on a selected STM-1 link, i.e. the outgoing (towards the optics) STM-1 data is routed back to the STM-1 receiver on the same link, as well as being transmitted towards the line. While an STM-1 local loopback is in operation, an RS-Loopback_On alarm is raised. This loopback should be activated with caution as it causes traffic loss.



An STM-1 local loopback is not permitted in an unprotected system. It is also not permitted on both aggregates in a protected system. Refer to Figure 2-5.

Note: When a local STM loopback is raised, the multiplexer detects a temporary loss of signal during the switch and raises an RS-LOS alarm (which clears after the switch). This causes PPS on all tributaries fed from this aggregate.

Figure 2-5STM-1 local loopback

STM-1 remote loopbackA remote (‘far-end’ or ‘loop to line’) loopback can be performed on a selected STM-1 link, i.e. the incoming (from the optics) STM-1 data is routed back to the optical connections on the same link, as well as being transmitted towards the line. While an STM-1 remote loopback is in operation, an RS-Loopback_On alarm is raised. Refer to Figure 2-6.

CAUTIONECC communication lossAn STM-1 local loopback must not be activated remotely as it leads to ECC communication loss and a site visit is required to remove the loopback condition.

CAUTIONLoss of trafficAn STM-1 local loopback causes traffic loss. Ensure that the aggregate to be looped back is not carrying traffic.

CAUTIONECC communication lossAn STM-1 remote loopback must not be activated remotely as it leads to ECC communication loss and a site visit will be required to remove the loopback condition.

CAUTIONLoss of trafficAn STM-1 remote loopback causes traffic loss, the user should ensure that the aggregate to be looped back is not carrying traffic.

Electro-OpticalModule

STM-1Section

TerminationSTM-1

x



2

Note: When a remote STM loopback is raised, the remote multiplexer may detect a temporary loss of signal (at the time of the switch) and raise an RS-LOS alarm (which will be cleared after the switch) causing a PPS on tributaries fed from that link.

Figure 2-6STM-1 remote loopback

Tributary local loopbackA local (‘near-end’ or ‘loop to mux’) loopback can be performed on the tributary level on the selected link, i.e. the outgoing (towards the metallic wires) PDH data is routed back to the PDH receiver on the same link, as well as being transmitted towards the line (refer to Figure 2-7). This loopback is implemented in the tributary line driver in TN-1C Release 3/5/5.1 and TN-1P hardware and in the tributary mapper in TN-1C Release 1 hardware. While a tributary local loopback is in operation, a PPI-Loopback_On alarm is raised.

Figure 2-7Tributary local loopback

Note: The loopback can only be applied when the tributary port is in the ‘traffic on’, ‘traffic auto’ or ‘traffic standby’ mode.

Tributary remote loopbackA remote (‘far-end’ or ‘loop to line’) loopback can be performed on the tributary level on the selected link, i.e. incoming tributary data (from the metallic wires) is routed back to the tributary lines on the same link, as well as being transmitted towards the PDH receiver in the mapper. This loopback is implemented in the tributary electrical line driver in TN-1C hardware from Release 3, in TN-1P hardware, and in the tributary mapper in TN-1C hardware from Release 1. While a tributary remote loopback is in operation, a PPI-Loopback_On alarm is raised.

Electro-OpticalModule

STM-1SectionTermination

STM-1

x

x

TributaryInterface

TributaryElectricalLine Driver

TributaryMapper



Figure 2-8Tributary remote loopback

Note: The loopback can only be applied when the tributary port is in the ‘traffic on’, ‘traffic auto’ or ‘traffic standby’ mode.

Simultaneous loopbacksSTM-1 loopbacks and tributary loopbacks can be performed independently. Although STM-1 loopbacks may be performed on both aggregates simultaneously, this must not be done remotely as all ECC communications are disabled and a site visit will be required to remove the loopback condition. On a specific tributary or STM-1 aggregate, local and remote loopbacks cannot be performed simultaneously.

Single fibre workingThe TN-1C or TN-1P multiplexer is capable of operating in a single fibre mode where a single optical fibre is used to carry bi-directional optical signals between adjacent multiplexers. The conversion between two fibre working and single fibre working is performed externally to the multiplexer by a 2-1 optical coupler (see Figure 2-9).

Figure 2-9Single fibre operation

In the event of a break in the single fibre, there is a possibility of the transmitted traffic being echoed by the 2-1 optical converter to the receive port on the same multiplexer. This signal must be recognized as faulty and AIS transmitted downstream. To recognize the echoed signal, the HO path trace facility should be used with the transmit and receive path trace settings set to different values and the consequent actions enabled.

TributaryMapper

TributaryElectricalLine Driver

TributaryInterface

x

TN-1C

Tx

Rx

2-1

Con

vert

er

2-1

Con

vert

er

TN-1C

Tx

RxSingleOpticalFibre



2

By using the path trace facility with the consequent actions enabled, an HP-TIM alarm will be raised and AIS transmitted downstream if a fibre break occurs.

Note: If the consequent action of HP-TIM alarm is enabled, the transmitted signal will have the HP-RDI set. This will be received in the echoed signal causing a HP-RDI alarm to be raised on the same multiplexer that generated it.

In the event of a broken fibre where the echo is sufficient to constitute a valid signal, the multiplexer does not behave in the normal manner to a Loss of Signal event. Instead a transient STM-LOF alarm will be raised while the multiplexer is achieving frame alignment to the echoed signal.

If the single fibre is used as a synchronization reference, a timing loop may develop. To avoid this, the HP-TIM alarm can be configured to invalidate the aggregate as a synchronization source. This is recommended in any multiplexer application except for a point-to-point application where, under certain circumstances, a timing loop may be deemed acceptable.

The RS-LOS alarm is used as a trigger for ALS. In the event of a broken fibre, if the echo is sufficient to constitute a valid signal, the RS-LOS will not be raised, therefore ALS is not supported when operating in a single fibre mode.

Built-in test facilityThe TN-1C or TN-1P multiplexer provides three types of tests: two automatic non-service affecting tests, and a manual test which is initiated by the user, via the user interface.

Note: A manual test affects traffic for a short period of time.

Non-service affecting testsPower-up testWhen the multiplexer is powered up, or after a ‘cold start’, the multiplexer performs a hardware test before any traffic flow is established. This examines the processor, memories, application software and other hardware components that are not available for test when the multiplexer is operating. If the test fails, the red ‘FAIL’ LED on the multiplexer connector panel remains lit.

After the tests are completed, the following message is sent to the UI, if no user is logged in at that time, the message is lost.

NORTEL TN1C, SW RELEASE = C515, BOOT = C515*********************************************RAM test passedClock 1 test passedClock 2 test passedClock 3 test passedSCC1 test passed



SCC2 test passedSCC3 test passed

Only the heading is sent after a warm restart.

Normal operating testsDuring normal operation, the multiplexer performs periodic tests to provide validation of the hardware operation. Tests are carried out on RAM, ASICs, software FLASH memories, and configuration non-volatile storage. Upon detection of a fault, a consequent action may be activated and an alarm raised.

Service affecting testsThe multiplexer includes a built-in test pattern generator and detector, operated through a user interface session. The test pattern is:

• PRBS15 for the 2 Mbit/s tributaries (TN-1C and TN-1P) as defined in ITU-T Recommendations 0.151 sec, 2.1

• PRBS23 for 34/45 Mbit/s tributary signals (TN-1C only) as defined in ITU-T Recommendations 0.151 sec, 2.2.

The test pattern may be injected towards the optical line on a specific path or towards the tributary line (one at a time per multiplexer). The tributaries must be in the ‘traffic on’, ‘traffic auto’ or ‘traffic standby’ state to perform this test. The test pattern overrides all the bits of the original signals (e.g. for 2 Mbit/s signal, all 256 bits per frame carry the PRBS15 bits).

A test pattern generator may be connected to the signal from the VC data or from the tributary line. The detector synchronizes to the PRBS test data, and once synchronized it starts counting the errors between the incoming bit-stream and the expected bit-stream. Errors are periodically read, and accumulated to derive the test results. The detector will detect bit error ratio up to 10-3, with an overflow indication in case of a higher BER.

Once synchronization is lost, a flag is raised and the receiver will attempt to re-synchronize.

The PRBS generator/detector is located between the PDH mapper and the PDH line drivers as shown in Figure 2-10. The PRBS generator/detector is shown for a single tributary, the PRBS generator/detector is common for all tributaries and can be switched to any tributary. Throughout a PRBS test, a PPI-Continuity_Test alarm is raised.



2

Figure 2-10PRBS location

Note 1: PRBS should not be injected towards the optical side when the same tributary is in ‘remote’ loopback. The test will fail due to a lack of clock source in that scenario and the test does not provide any value.

Note 2: For 34/45 Mbit/s tributaries (TN-1C only), PRBS to an optical line does not operate if a PPI-LOS alarm is detected on the tributary.

Note 3: PRBS can not be applied when the tributary port is in the ‘traffic off’ mode.

Note 4: PRBS cannot be applied when the tributary is in the synchronisation source hierarchy.

0

The test results are reported to the UI as follows:

• Test time - length of the test in the format hh:mm:ss (hours:minutes:seconds)

• Synchronization status - a sync/no sync attribute which specifies whether the detector was continuously synchronized to the incoming test pattern since the last report

• Error count - number of errors counted

• BER - The bit-error ratio is derived by the error count divided by the product of Test Time (in seconds) and N. N equals 2048000 for 2 Mbit/s tributary testing, 34368000 for 34 Mbit/s tributary testing and 44736000 for 45 Mbit/s tributary testing.

0

If the error count is inaccurate due to synchronization loss or error counter overflow in one or more intervals, then the error count for those intervals will be set to the hardware counter maximum count. Also the error count and BER parameters will be marked as ‘invalid’ for the whole test period. This is denoted by an asterisk ‘*’ after the report.

The user activates the PRBS by specifying a tributary to be tested and the report frequency. The report frequency has a default of 30 seconds if the user does not supply an alternative. Reports are displayed by the user interface.

PDHelectricalline driver

PDHmapper

PRBSGenerator

PRBSDetector

Tribtowardsoptical line



2

Subrack end processor and craft access panel (TN-1PH only)One subrack end processor (SEP) is fitted to each TN-1P Headend subrack in slot 13, to the right of the MPP units. It is not required in the TN-1C or TN-1P (wall/rack-mount unit). Its purpose is to consolidate the support functions of the individual TN-1P MPPs into one common facility.

The SEP provides the following four functions:

• IEE802.3 CSMA/CD hub for 12 ports

• Alarm interface circuits

• CAT interface circuit

• on-card PUPS

The craft access panel (CAP) is a small panel fixed to the right hand side of the TN-1PH subrack. It provides the front panel indications and controls required by the SEP, as follows:

• ‘Fail’ alarm LED (indicates the subrack alarm status)

• Active ‘RCU-ACK’ LED (indicates the subrack alarm status)

• Alarm Acknowledge (REC ATT) push-button

• MPP/CAT selection display

• CAT selector push-button0

Figure 2-11 shows a simplified block diagram of the SEP and CAP.



2

Figure 2-11SEP and CAP block diagram

+5 V

PUPS –48 V

To/fr

om T

N-1

P M

PP

s

10BaseT(to MPP #1)

4 EXT alarm

outputs

SELECTCARD

12

1 managed port

10BaseT

LED

displays

10BaseT(to MPP #12)

Encoder/decoderSelector& regenerator

Control

MAU

MAU

AIU

LAN Interface

1 EXT alarm

input

ControlDebounce

REC ATT

(REC ATT)

4 rack alarms

Debounce

Selector

Select button

RS-232repeater

RS-232

to MPPsTo CAT

display

RS-232 selector

Alarm handler

Craft Access Panel

SEP

button



LAN InterfaceThe medium attachment units (MAU) receives/transmits data to the individual MPPs and performs collision detection.

The attachment unit interface (AUI) receives/transmits data to the LAN manager workstation and sends/receives control signals to/from the hub.

The selector switches the active port to the encoder/decoder and regenerator and then routes it to the remaining ports. It also performs port partitioning when excessive numbers of collisions occur.

The encoder/decoder and regenerator implements the Manchester signalling format required by IEEE802.3. It also performs signal retiming and amplitude restoration. When a collision has been detected the regenerator notifies all ports by sending a jam sequence.

Alarm handlerThis consolidates the alarms from each MPP into a single standard rack alarm interface.

The alarm outputs from the MPPs are tied together on the TN-1PH Headend backplane, and then passed on to the alarm handler on the SEP. The rack alarm outputs from the SEP are:

• ‘Prompt/Deferred’ alarm to rack

• ‘In-Station’ alarm to rack

• ‘Receive Attention’ input

• ‘Fault Clear’ input

The Alarm handler also has the following connections to the CAP:

• Fail alarm LED

• Active ‘REC-ACK’ LED

• Alarm Acknowledge (REC ATT) push-button

RS-232 selectorThis block permits the selection of a local craft access terminal (CAT) to any one of the MPPs. The CAT is plugged into the CAT port on the TN-1PH connection panel. Selection is achieved by a single push-button on the CAP, pressing the button connects the next MPP slot in the subrack to the CAT. The MPP that is currently selected is identified on the two digit display on the CAP.

end of chapter


3-1

3Equipment management 3-

The equipment management functions of the TN-1C, TN-1P, TN-1PH and TN-1P Basestation multiplexer are performed by the synchronous equipment management function (SEMF) of the multiplexer embedded software.

AlarmsAlarm monitoring

Alarm monitoring is carried out in order to indicate the multiplexer status at any given time. Alarm reports are made to:

• all open sessions

• external alarm outputs (according to alarm association with the alarm outputs)

• the Element Controller EC-1 station (a brief report)0

In addition, the user can always request a list of the current active alarms. Details of the alarm indications, alarm sequences, and individual alarms are given in Alarm Clearing Procedures, 323-1081-543.

Alarm handlingEach alarm raised is monitored for a specific period after they are set/cleared in order to correlate any low level defect with the higher level defect that might have caused them. The time periods for which these defects are set vary, this is to avoid ‘alarm flooding’ before making a report. For reporting purposes, the alarms are further processed for correlation, detection and masking. All reported alarms are time stamped and logged.

Alarm maskingThe multiplexer software performs alarm masking, so that only the highest level alarm on any one traffic path is reported as set, while all other alarms are considered cleared. However, when the higher priority alarm is cleared, then the alarm with the next highest priority of the remaining alarms is reported.

3-2 Equipment management


External alarmsTN-1C and TN-1PThe multiplexer has twelve external alarms: eight input and four output.

The external alarms provide a means of collecting various indications from external devices (via input alarms; fire detector, door open etc.) and reports them to the management station. The output alarms can be set to activate external devices (i.e. fire extinguisher, traffic alarm etc.).

Each alarm name associated with the external alarm input(s) and output(s) can be set, by the user, to give a meaningful name i.e. ‘Fire’, etc.

An input alarm is set if it persists for longer than its predetermined time period of one second. Output alarms may be associated with any (one or more) alarm types. In this case, when at least one of the associated alarms is set, the appropriate external alarm will be set. An external alarm is cleared if none of its associated alarms is set.

The user may configure an external alarm into a certain state (Forced set/cleared). If forced into a state, the external alarm output will remain in this state regardless of any change in the associated alarms. Only after the user disables the forced state, will the associated alarms be able to affect the external alarm output state.

TN-1P HeadendIn the TN-1P Headend the external alarms are configured as follows:

• Each main point-to-point (MPP) uses four external alarm outputs and one external alarm input.

— The outputs are consolidated by the subrack end processor (SEP) into a standard rack alarm interface.

— The input is used to accept a pressing of the receive attention (REC-ACK) button.

• The remaining alarms are reserved for system use and are not available to the user.

0

Each MPP also maintains its own state machine for the rack alarm signals relating to its own status. The rack alarms indicate the alarm status of the local MPPs and do not indicate the status of alarms in any remote TN-1P.

The alarms are graded with three levels of severity: Prompt, Deferred, and In-Station. When passed on to the rack alarm bus, the Prompt and Deferred alarms from each MPP are combined into a single alarm with the Prompt level of severity.

Rack alarmsWhen used in a rack, the TN-1C or standard TN-1P can be used in conjunction with a rack alarms adaptor, this allows the four output alarms to be consolidated into the rack alarm system.

Equipment management 3-3


3

One input alarm (EAIn_8) is used to read the alarm receive attention button. In this situation, the external alarms feature can not be used.

The rack alarms adapter has two LEDs, a red LED labelled ‘Alarm’ and a green LED labelled ‘Receive Att’. When an unacknowledged alarm (of any severity) is present, the red LED is illuminated. If the alarm receive attention button is pressed, the alarm is acknowledged, the red LED is extinguished and the green LED is illuminated. If an acknowledged alarm is cleared, the red LED is illuminated again; at this stage both LEDs are illuminated. This means that an acknowledged alarm has been cleared but the clear has not yet been acknowledged. Once a cleared alarm has been acknowledged, both LEDs are extinguished.

Similar LEDs are situated on the rack alarm unit, although there are usually four, one confirming the power supply, a receive attention LED, one that is illuminated to show the presence of a Prompt or Deferred alarm and another that is illuminated to show the presence of an In station alarm or an acknowledged alarm clearing.

TN-1P Basestation variant has no rack alarm adaptor.

ManagementATU channel

The TN-1C and TN-1P multiplexers provide an ATU channel. This is for the use of external equipment that communicates with its management system via the TN-1C and TN-1P. Asynchronous data is packaged and transmitted over the ECC.

The auxiliary channel interface are as follows:

• TN-1C Release 1 hardware: RS-232 interface.

• TN-1C Release 3 onwards hardware: RS-485 point-to-multipoint interface.

• TN-1P auxiliary channel: RS-232 interface

The multiplexer is defined as a data termination equipment (DTE) for the TN-1C (Release 3 onwards) hardware and a data communications equipment (DCE) for TN-1C Release 1 hardware and the TN-1P.

Clear channel telemetry The clear channel telemetry feature allows equipment outside of the network to pass asynchronous ASCII messages across the network.

The clear channel telemetry functionality collects the incoming characters, packetizes these characters and stores them in a buffer having a capacity of up to 440 bytes.

The clear channel telemetry functions in a similar manner to the ATU message handling, but with the following differences:

• in clear channel telemetry, the user programs the destination,



• all ASCII characters are accepted (a start and stop sequence is not expected)

• as there are no pre-defined control characters, the transfer of a frame in an upstream direction (port to network) has only the following criteria:

— buffer full

— more than 0.25 seconds between characters

As the clear channel telemetry data is sent over the network in the same way as the ATU data, the transferred message is identified using a transport service access point ID (TSAP_ID) header.

LAN channelThe TN-1C, TN-1P (ADM upgrade only) and TN-1PH have a standard 10BaseT LAN interface which allows communication with the EC-1 or for connection to other appropriate equipment. When a TN-1C, TN-1P (ADM upgrade only) or TN-1PH network element is selected from the EC-1, the resident application software within that network element is accessed via a user interface window in the EC-1 screen.

Real time clockThe multiplexer contains a real time clock with an accuracy of ±5 seconds per day, this is primarily used for time stamping alarm and performance statistics. The user can view and update the date/time at any time during a Browser session. When the multiplexer is powered up or after a warm or cold restart, the clock aligns to a default date and time (January 1st 1995, 00:00).

The EC-1 updates the real time clock on the TN-1C and TN-1P upon EC-1 session setup, and daily thereafter.

RSOH/MSOH DCCThe data communications channel (DCC) provides a communications path to manage remote NEs. The multiplexer software supports the following:

• regenerator section overhead (RSOH) DCC (bits D1 to D3) at a rate of 192 kbit/s

• multiplexer section overhead (MSOH) DCC (bits D4 to D12) at a rate of 576 kbit/s.

The following limitations are applicable:

• Each STM-1 aggregate can operate on either RS DCC or MS DCC, but not both.

• There is no automatic selection of either RSOH or MSOH. The channel must be explicitly configured.

• A change of state requires a warm restart.

• For TN-1C, the add/drop multiplexer (ADM) hardware does not support DCC passthrough for other vendors’ management protocols.



3

More information about RSOH and MSOH is provided in ‘Section overhead’ in Appendix A: Synchronous digital hierarchy.

Network addressesEach multiplexer is identified by a unique address to allow communications between network elements using the ECC, and for network element identification by the EC-1.

The network address of the TN-1P and TN-1C is held on board. For the TN-1P the network address is held on the multiplexer card. For the TN-1C the network address is held on the ADM card.

The multiplexer supports the configuration of up to three manual area addresses in order to implement IS-IS (intermediate system to intermediate system) routing. One manual area address must be configured in the multiplexer at all times. The multiplexer also holds a ‘partner NE’ address, this allows users of the Command Line User Interface to rapidly access a user selected partner NE.

Communication limitationsThe Release 5/5.1 TN-1C, TN-1P, and TN-1PH NEs act as IS-IS Level-1 routers. In a data communications network (DCN), a Level-1 address area may contain a total of up to 250 elements, but no more than 150 IS-IS network elements. In their maximum configuration (12 TN-1PH cards and 24 TN-1P remote units), the TN-1P/TN-1PH units appear as 36 individual IS-IS routers. This must be considered when provisioning a network with Release 5/5.1 TN-1P/TN-1PH NEs.

Note: Release 2 TN-1P NEs behaved as end systems.

Inventory informationInventory information is held in on-board IDPROMs. The following data can be accessed with User Interface commands:

• network address

• PEC

• serial number

• card type

• extension card information (TN-1C): PEC, card type, serial number

• date of manufacture

CAUTIONChanging area addressesBefore changing the area addresses, ensure that you are aware of the consequences to the communications within your network. Changing an area address can cause other NEs to lose communications with the EC-1. Any changes must be carefully planned on a network wide basis.



• checksums for main and connector cards

SoftwareApplication software

One copy of the multiplexer application software is held in two ‘flash’ memory banks. The versions held in each bank should be the same at all times except during software upgrades. As only one flash memory copy can be selected by the multiplexer boot software at any given time, the software of the flash bank not selected can be upgraded while the other copy is running.

The multiplexer contains an automatic reversion facility, i.e. if the selected application software fails to start up successfully, an automatic reversion to the older software version is carried out. Alternatively, the user may request a return to the older software version after the first switch is made (refer to configuration data below). In the unlikely event that both flash banks fail, the multiplexer unit should be replaced and returned to Nortel Networks for reprogramming. Figure 3-1 shows the overview of the software upgrade procedure.

Configuration dataThe multiplexer has a set of configurable parameters that are required to accommodate various user preferences. The multiplexer incorporates two configuration databases, each associated with one software flash bank, and stored in non-volatile storage (NVS).

In normal operation, the two configuration data bases contain the same information, one is the operational bank and the other is the backup bank. However, when the application software is being upgraded, each configuration data base becomes associated with a flash application software bank. If the user changes the configuration using new software, and performs a backout, or commits to the new software after changing the configuration using the old software version, the recent configuration changes are lost.

The user may backup the current configuration data base settings into a file in the CAT or in the EC-1, and restore the settings if they are required (if they have been overwritten or if the multiplexer fails and is replaced by a new one).

If the user restores old configuration data from the CAT or EC-1, a copy of the data is stored in the unused configuration bank in the multiplexer. If the restored data is satisfactory, the user may commit to it and the multiplexer puts it into service. The user may also backout to the old configuration until the decision to commit is made to the new configuration, which means that it is copied to the two banks.

Note: A software upgrade can only start when the configuration status is stable, i.e. both banks contain the same data.



3

Figure 3-1Software upgrade overview

end of chapter

Start

New software available

Test new software

SoftwareOK

Yes

No

BackoutCommit to new

software

Old software in both banks

New software in both banks

Finish

Both software banks contain the original software.

Active Bank contains the original software and Inactive Bank now contains the new software.

If the new software is satisfactory, the user may decide to commit to it. If the new software proves unsatisfactory, then the user must backout, reverting to the original software. In either case, after the software has been tested, the version in each bank should be the same.

While the new software is being tested, the original software can remain in Active Bank. The user may switch between the different software in each bank.

During normal operation, it is important that both banks contain the same software version. If the software in each bank is different, this can interfere with the operation of configuration functions.

Switch to new software

Switch to original software

Download to TN-1C/TN-1P Inactive Bank


4-1

4

Power supply unit 4-Note: The power supply unit is not used with the TN-1P Basestation or TN-1PH Headend.

The power supply unit (PSU) for the TN-1C and TN-1P multiplexer is a dedicated external power supply unit, which is used in wall-mounted applications, to supply a nominal –24 V d.c. to the multiplexer. Matching enclosures are used to house the PSU and the multiplexer in this wall-mounted application. The rack mounted multiplexer is powered from the rack power supply.

The multiplexer PSU is powered from a nominal 115 Va.c. or 230 Va.c. supply and has a nominal power consumption of 33 W. Power is normally derived from the a.c. mains, but if a supply failure occurs, the multiplexer PSU will supply operating power to the multiplexer for approximately three hours from internal back-up batteries.

If the multiplexer PSU is assembled but is disconnected from the a.c. supply for a period in excess of three days, it is recommended that the batteries are removed from the unit.

Functional descriptionFigure 4-1 shows the block diagram of the multiplexer PSU.

The a.c. input is connected, via an IEC mains connector fitted with an in-line 2.5 A fuse, to the power supply unit. The fuse protects the power supply unit.

An a.c. input filter reduces conducted and radiated electromagnetic interference to within the limits specified by EN55022 (radiated and conducted emission) and EN50082 (EMC).

The output of the a.c. filter is fed to an a.c./d.c. converter and charger unit where the a.c. is stepped down and rectified to provide regulated power to charge the two PSU back-up batteries and to deliver power to the multiplexer. Over-voltage and over-current protection are provided for the output.

4-2 Power supply unit


The output from the converter and charger is also connected to a comparator which monitors the d.c. output and battery voltages and carries out the following actions:

• disconnects the batteries from the output, via a relay, if the battery voltage falls below a predetermined level. They are disconnected if the battery voltage falls below 19 V ± 0.5 V, and re-connected at 23.5 V ± 0.5 V.

• extinguishes the d.c. LED if the output voltage falls outside predetermined limits.

• sets alarm signals (PS-Power_Fail, PS-Battery_Low, PS-Door_Open) on the d.c./alarm connector.

0

Figure 4-1TN-1C PSU block diagram

The batteries are charged from the d.c. output supply and are protected against reverse connection and over-current at the output, by a protection diode and a 7.5 A fuse respectively.

Battery back-upThe two batteries contained in the multiplexer PSU are 12 V, nominally 6 AH, maintenance-free, sealed, rechargeable, lead-acid batteries connected in series. The batteries are charged, and capable of powering a multiplexer for approximately three hours should a mains supply failure occur.

Alarms and indicationsThe multiplexer PSU has two indicator LEDs and three alarm outputs.

d.c.LED

a.c.input

Fuse

a.c.inputfilter

a.c./d.c.converter& charger

Comparatorsand relay

0 V

Fuse 7.5 A

Batteries

–24 V

PS-Battery Low

PS-Power_Fail

–

ProtectionDiode

+

1

3

4

d.c.output

5

PS-Door_Alarm

Batteries failedLED (red)

6

Alarm earthcommon

+

–

2

9

Shield

Power supply unit 4-3


4

The indicator LEDs are fitted to the alarm/interface unit. They are not visible from the outside of the case, and are provided for maintenance purposes only:

• A red LED indicates that the battery voltage has dropped below 19 V ± 0.5 V, after the a.c. input voltage has been disconnected. If the voltage continues to drop below a predetermined level, the LED is extinguished.

• The green LED indicates that the nominal –28 V d.c. charger output supply is present and within tolerance. It is extinguished if the charger output voltage falls outside the limits of –24.9 V to –30 V d.c.

0

The alarm/interface panel contains a PSU ‘door open’ alarm microswitch.

The alarms are routed, via the d.c./alarm connector, to the multiplexer where they may be accessed via a local UI session. Alternatively, they are included in ECC overhead bytes and reported back to the CAT, via a remote UI session, or to the element controller EC-1.

The alarms are as follows:

ConnectorsThe 115 Va.c. or 230 Va.c. mains input is connected via an IEC connector assembly. This connector assembly also contains the mains fuse, filter, and a spare fuse.

The d.c. output and alarms are routed to a nine pin ‘Mate-n-lock’ connector. The pin-out of the connector is shown in Table 4-1.

Alarm Description Type Parameters

PS-Battery_Low Battery low voltage

Active low Set if d.c. battery voltage (absolute value) falls below 21 V ± 0.5 V

PS-Power_Fail Line Power Fail Active low Set if charger output d.c. voltage falls below 26.2 V ± 0.5 V

PS-Door_Open Door Alarm Active low Set if door is open

Table 4-1D.C./alarm connector pin-out

Pin Function Pin Function

1 d.c. feed return 0 V 6 Shielding

2 PS-Battery_Low Voltage 7 Not used

3 PS-Power_Fail 8 Not used

4 Alarm earth/common 9 PS-Door_Open

5 d.c. feed power –24 V

4-4 Power supply unit


ConstructionThe multiplexer PSU, which is designed for wall mounting, is housed in a case identical to the multiplexer unit case. The enclosure cover is locked and there are no customer field replaceable items. The unit comprises the following major components:

• multiplexer type case

• IEC a.c. input connector/fuse/filter unit

• a.c./d.c. converter/charger unit

• alarm/interface panel

• two 12 V back-up batteries0

All of the multiplexer PSU components are mounted on the backplate of the multiplexer PSU case, the layout of which is shown in Figure 4-2. The two 12 V batteries slot into shelves on the backplate and are connected to the charger unit by spade connectors.

The a.c. power lead plugs into an IEC connector at the bottom of the unit. The d.c. supply/alarm output cable connects to the d.c./alarm connector located on the alarm/interface panel below the converter/charger unit. The leads exit the case via cutouts in the bottom or top of the case.

Power supply unit 4-5


4

Figure 4-2TN-1C and TN-1P multiplexer PSU layout

end of chapter

Case backplatePSU backplate

a.c./d.c.

IEC a.c. mains input

Tyrap(8 positions)

Battery

Batterysupport

Battery

Batterysupport

d.c. supply/alarm output

converter andcharger unit

Alarm/interfacepanel

d.c./alarmconnector

spare d.c. fuse

d.c. fuse

cable

door openmicroswitch

connector assembly

a.c voltageselector


5-1

5

Synchronisation 5-For integration into an SDH network, the TN-1C, TN-1P, TN-1PH and TN-1P Basestation multiplexers can synchronize to any external signal traceable to a Primary Reference Clock (PRC):

SourcesThe multiplexer synchronisation can be derived from any one of the following sources:

• STM-1 optical aggregate input (aggregate A or B)

• 2 Mbit/s G.703 tributary input on the main multiplexer card

• 2 Mbit/s G.703 tributary input on a tributary extension card (TN-1C only)

• 34/45 Mbit/s tributary input on a tributary extension card (TN-1C only)

• 2 Mbit/s external synchronisation input (TN-1C and TN-1P ADM card upgrades only)

• remain in the last known frequency (‘Holdover’)

• internal ‘free-running’ clock

Note 1: If synchronisation is derived from a tributary input, the signal can be framed or unframed as the multiplexer derives an 8 kHz clock from the signal and does not reframe it.

Note 2: A tributary in the ‘traffic off’ or ‘traffic stand-by’ state cannot be used for synchronisation purposes.

Note 3: Use of the internal oscillator is not recommended when the multiplexer is connected to an SDH system. An external source is preferred.

Note 4: The use of synchronisation derived from the External Synchronisation Input (TN-1C and TN-1P ADM card upgrades only) is preferred to the use of the PDH port for synchronisation.

Synchronisation lossThe multiplexer interprets the following as loss of synchronisation signal:

• Loss of signal (RS-LOS or PPI-LOS)

• Receipt of an AIS (MS-AIS or PPI-AIS)

• Synchronisation source ‘out of limits’ (SYNC-Source_Fail)

• Loss of external synchronisation signal (SYNC_Ext_Sync_LOS)

5-2 Synchronisation


Note 1: For all the above synchronisation signal losses (except ‘out of limits’), the synchronisation signal becomes valid again if the defect is cleared for 10 seconds.

Note 2: A synchronisation source is considered ‘out of limits’ by the multiplexer when the multiplexer cannot synchronize to the source whilst it is in use. Synchronisation source ‘out of limits’ requires manual clearing by the operator.

Note 3: The internal oscillator is a standard SDH clock but synchronizing to an external clock is recommended. Therefore if a faulty synchronisation source becomes valid again, the multiplexer will re-synchronize to it even when reversion is off.

Note 4: Detection of an invalid external synchronisation source (TN-1C and TN-1P ADM card upgrades only) is only performed when the source becomes the reference. Ensure that a valid 2 Mbit/s signal is present on the external synchronisation input (do not connect a 34/45 Mbit/s signal).

It is also possible to specify the following optional criteria as loss of synchronisation signal in addition to the above.

• Excessive Bit Error Rate (MS-EXC or PPI-EXC)

• Loss of frame alignment (RS-LOF or PPI-LOF)

• Path Trace Mismatch (HP-TIM)

Synchronisation schemesTN-1C

The following synchronisation schemes are recommended for TN-1C applications and are designed to avoid possible synchronisation loops:

• Figure 5-1(a) shows a point-to-point application whose requirement is to deliver the signals, while providing a G.703 compliant signal at the tributaries (± 50 ppm for 2 Mbit/s). The multiplexer internal clock is sufficient for this requirement (if no timing is required to be carried between the two stations) although an external source is preferred. However, using loop timing in the other multiplexer reduces the need for pointer processing.

• Figure 5-1(b) shows a point-to-point application where one site (e.g. a ‘central office’) provides synchronisation to the other station, an external source should be used. The external source can be a tributary signal, which may or may not carry traffic, or the external synchronisation input. The remote multiplexer derives synchronisation from the incoming optical signal (± 20 ppm for STM-1) and uses it for aggregate and tributary transmission.

• Figure 5-1(c) shows a ring application which has one node synchronized to an external synchronisation source traceable to a PRS, that uses this clock for transmission. All other nodes derive timing from the feeding STM-1 link to use it for aggregate and tributary transmission.

Synchronisation 5-3


5

• Figure 5-1(d) shows a special case where an accurate reference signal exists on every node (traceable to a PRS). It may be beneficial to derive timing at the multiplexer from this accurate source in all nodes, rather than use the line timing (which may be traceable to a primary source, but with accumulated jitter and noise). The line timing may be used as a backup in case the external signal fails.

TN-1PThe following synchronisation schemes are recommended for TN-1P applications and are designed to avoid synchronisation loops:

• Figure 5-2 (a) shows a point-to-point application which merely requires the transport of 2048 kbit/s PDH signals between two sites, while providing a G.703 compliant 2048 kbit/s signal (± 50 ppm) at the tributaries. The TN-1P’s internal oscillator at one TN-1P is sufficient for this requirement. The second TN-1P derives its synchronisation from the aggregate input, hence synchronizing both TN-1Ps to a single clock, reducing the need for pointer processing.

• Figure 5-2 (b) shows a point-to-point application where one site (e.g. a ‘central office’) provides synchronisation via a 2 Mbit/s PDH port (ESI port is not available on the standard TN-1P, but is available for TN-1P ADM upgrades) to the other site. The tributary signal that is used may or may not carry traffic. The remote TN-1P derives synchronisation from its optical aggregates and uses it for aggregate and tributary transmission.

• Figure 5-2 (c) shows a TN-1P connected to an SDH add/drop multiplexer (ADM) (for example, a Nortel Networks TN-1X). In this case, the TN-1P should derive synchronisation from the STM-1 link(s) received from the SDH ADM (which is likely to have a more accurate clock signal). This signal is used for aggregate and tributary transmission.

CAUTIONSynchronisation timing loopsTake care when setting the synchronisation sources in a network in order to avoid timing loops. For example, if a single NE with a primary reference clock (see Figure 5-1) provides snchronisation for a ring application, none of the aggregates should be put in the synchronisation hierarchy in addition to the external port for that NE.

5-4 Synchronisation


Figure 5-1TN-1C recommended synchronisation scheme

TN-1C

Customer PremisesCustomer Premises

Site #2Site #1

(a) Point-to-point application - simple station

TN-1C

Customer PremisesCentral Office

(b) Point-to-point application - with Central Office station

TN-1C

TN-1C

TN-1C

TN-1C

(c) Ring application with Single Timing Reference

TN-1C

TN-1C

TN-1C

TN-1C

(d) Ring application - with 2 Mbit/s Reference at every node

Synchronisation source or reference signal

Synchronisation path and direction

TN-1C

TN-1C

INT

EXT(2 Mbit/s)

Synchronisation 5-5


5

Figure 5-2TN-1P recommended synchronisation schemes

(a) Point-to-point application - simple sites

(b) Point-to-point/Head-end application - with Central Office

SDH TN-1P

Customer Premisese.g. a Nortel Networks TN-1X

(c) ADM tributary application

ADM

multiplexer

Synchronisation source or reference signal.

Synchronisation path and direction.

TN-1P

Customer PremisesCustomer Premises

Site #2Site #1

TN-1P

INT

TN-1P

Customer PremisesCentral Office

TN-1P

(PDH port) (Note 1)EXT

Note: If the Central Office TN-1P is upgraded to an 8 x 2 Mbit/s ADM, it can deriveits synchronisation via its external synchronisation input port.

5-6 Synchronisation


Synchronisation source switch eventAfter a synchronisation source switch has occurred, the craft access terminal (CAT) or the EC-1 element controller displays a synchronisation source switch event when you access the network element. This is not an alarm but an indication that a changeover from one synchronisation source to another has occurred. If a sync source switch occurs, an alarm is raised if the new sync source is not the primary source. This alarm does not cause the red LED to light as it does not affect traffic.

Synchronisation source hierarchyThe basis for synchronisation source protection is the synchronisation source hierarchy. This is formed from three sources identified by the user. The first source has the highest priority for the user, with the third having the lowest. A stand-by signal is also available, which is always the internal oscillator. Only sources listed within this hierarchy are considered for use.

The selected synchronisation source is used until the source fails, or a decision to change sources is taken.

Synchronisation settingsThe use of the synchronisation source hierarchy is controlled by reversion and force settings as described in the following sections:

Reversion on/offReversion controls the selection of a source if a source fails:

• Reversion on. If a source fails, or a decision to change sources is made, both higher and lower priority sources can be selected for use. The higher priority source is only considered if that source has recovered.

• Reversion off. When a source fails, or a decision to change sources is made, only sources of a lower priority can be selected for use.

If a source fails, a non-reversion flag is set on this source to prevent its re-selection at a later stage. This flag must be cleared manually by the user before that source is available for selection again.

Note: Reversion settings are not used when a source is in forced use (i.e. force on).

Force on/offForce on/off allows the user to manually select the source to be used.

• Force on. Using this setting, one of the sources in the hierarchy, including one that is currently invalid, is selected for use. The multiplexer is not able to change to a different source while in this mode.

If a source becomes invalid while in this mode, or if an invalid source is selected for use, the multiplexer begins a ‘holdover period’. During this period, the multiplexer reproduces the absent synchronisation signal internally. This situation is resolved in either of the following ways:

— If the source becomes stable again during this time, the source is used as if had not been interrupted.

Synchronisation 5-7


5

— If the holdover period ends (typically after five seconds) without the source becoming available, the standby source (the internal oscillator) is used.

Note: When a source is in forced use, reversion settings are ignored.

• Force off. Using this setting cancels any existing forced source usage, and source selection comes under the control of reversion setting. Existing non-reversion flags are unaffected when this mode is selected.

Note: The circumstances under which a switch in synchronisation occurs depends on the implementation mechanism used.

Synchronisation switching mechanismsThe circumstances under which a switch in synchronisation occurs depends on the implementation mechanism used. There are two mechanisms:

• A Synchronisation Status Messaging (SSM) mechanism. This uses transmitted quality levels to determine the best source. See “Synchronisation status messaging (SSM)” on page 5-7.

• A non-SSM system.With this mechanism, changes to the selected synchronisation source only occur when a source fails, or if a manual change is performed. See “Non-SSM synchronisation sourcing (TN-1C/TN-1P)” on page 5-12.

Both of these mechanisms make use of the software settings described in “Synchronisation settings” on page 5-6

Synchronisation status messaging (SSM)Synchronisation status messaging (SSM) is based on the transmission of synchronisation quality messages between potential synchronisation sources.

Using this system, the TN-1C/TN-1P is able to evaluate which synchronisation source is the best for use. This evaluation is used under two circumstances:

• The best source will always be selected for use, subject to software settings restrictions (see “Synchronisation settings” on page 5-6). That is, if a better quality source is identified (and no source is in forced use), the current reversion settings will dictate whether this source can be selected for use.

• If a source fails, the best of the remaining sources will be selected for use, subject to software settings restrictions (see “Synchronisation settings” on page 5-6). If no source is available, the stand-by source is selected.

Note: The SSM mechanism can only select sources that are listed in the synchronisation source hierarchy.

The TN-1C and TN-1P support the transmission and reception of the Quality Level (QL) and use SSM for determining the synchronisation source.

The QL of a source is transmitted in the section overhead of all STM-1 signals as the S1 byte. QL has a possible range of 1 to 15, with 1 as the

5-8 Synchronisation


highest priority. In practice, a subset of these values is used by the multiplexer. This subset of QL values is defined in Table 5-1.

You can configure the QL settings for both RX and TX purposes. These manual settings override any QL values established by the TN-1C/TN-1P software.

Note: By default, the TN-1C and TN-1P transmits using its internal clock which has a QL of ‘11’ on the STM-1 ports.

The TN-1C/TN-1P transmits its QL on all STM-1 ports, except for the STM-1 port from which it receives its synchronisation source. The QL transmitted on this port is 15, which indicates to the source of the synchronisation that the TN-1C or TN-1P should not be used for synchronisation. This action prevents closed synchronisation loops, where two multiplexers each attempt to synchronise from the synchronisation signal of the other.

Table 5-1SSM quality levels

QL Meaning Description

0 Synchronisation quality unknown.

Included for backwards compatibility reasons. The multiplexer interprets QL = 0 as QL = 15.

2 Traceable to Primary Reference Clock (PRC).

The external timing source for the network.

4 Traceable to Transit Clock. A clock provided for equipment which does not connect with customer equipment. That is, it only connects to other nodes.

8 Traceable to Local Clock. A clock provided for equipment which connects directly with customer equipment.

11 Traceable to SDH Equipment Clock (SEC).

The internal oscillator of the multiplexer.Note: This is the default setting.

15 Do not use for synchronisation.

Prevents the multiplexer’s synchronisation source from being used by multiplexers that receive this value.

Synchronisation 5-9


5

Synchronisation status messaging network examplesSimple ring with a single reference source

Note: Applicable only to TN-1C and TN-1P fitted with the 8 x 2 Mbit/s ADM card.

An example simple ring network with a single reference source is shown in Figure 5-3.

Figure 5-3SSM within a simple STM-1 ring with a single external source

In the example in Figure 5-3, synchronisation is derived from the Primary Reference Clock (PRC). The PRC is the external (EXT) source with a QL=2 at TN-1C(A). The other TN-1Cs in the ring have their hierarchy set to derive synchronisation from the counter-clockwise TN-1C in preference to the clockwise TN-1C (i.e. on their B ports in preference to A). The QL = 2 clock is transmitted on all STM-1 ports for the TN-1C, with the exception of the return port of the synchronisation source, on which QL = 15 (‘do not use for synchronisation’) is transmitted. This prevents closed synchronisation loops.

Note: Before the PRC signal was introduced, all four TN-1Cs would have used the default QL setting of 11, which indicates the use of an internal oscillator (INT).

If a fibre break occurs, the TN-1Cs after the break will send a QL = 11 in the counter-clockwise direction. The last TN-1C in the ring will switch to the higher quality clock (QL = 2) being sent from the TN-1C with the PRC in the clockwise direction. The QL = 2 clock is then available from its clockwise port, so moving in a clockwise direction around the ring each TN-1C will switch to the PRC QL = 2 clock. The ring will then be synchronised to the highest available quality clock.

QL = 2

QL = 2TN-1C (A)

PRC

2

2

15

15

STM-N RING

(An EXTernal source)

Hierarchy=EXT

QL = 2TN-1C

Hierarchy=B, AQL = 2TN-1C

Hierarchy=B, A

QL = 2TN-1C

Hierarchy=B, A

2

15

2

2

A B

A

B

AB

A

B

5-10 Synchronisation


Simple ring with two reference sourcesNote: Applicable only to TN-1C and TN-1P Basestation fitted with the 8 x 2 Mbit/s ADM card.

An example simple ring network with a two reference sources is shown in Figure 5-4.

Figure 5-4SSM within a simple STM-1 ring with two external sources

Synchronisation is derived from the Primary Reference Clock (PRC). The PRC is the external (EXT) source with a QL=2 at TN-1C(A). There is also a Secondary Reference Clock (SRC) which is also external and has a QL = 3 at TN-1C(B). The other TN-1Cs in the ring have their hierarchy set to derive synchronisation from the counter-clockwise TN-1C in preference to the clockwise TN-1C, i.e. on their B ports in preference to A. The QL = 2 clock is transmitted on all STM-1 ports for the TN-1C, with the exception of the return port of the synchronisation source, on which QL = 15 (‘do not use for synchronisation’) is transmitted. This prevents closed synchronisation loops.

In the event of a failure of the primary reference source the TN-1C with the primary source switches to an internal clock with a QL = 11. This will propagate around the network until it reaches the TN-1C with the secondary reference source which will switch to the SRC and transmit a QL = 3. This will then propagate around the network in a clockwise direction with the other TN-1Cs synchronising to the secondary reference source.

QL = 2

QL = 2TN-1C(A)

PRC

2

2

15

15

STM-N RING

(An EXTernal source)

Hierarchy=EXT, B

QL = 2TN-1C

Hierarchy=B, AQL = 2TN-1C

Hierarchy=B, A

QL = 2TN-1C(B)

Hierarchy=B, EXT

2

15

2

2

QL = 3SRC (An EXTernal source)

A B

A

B

AB

A

B

Synchronisation 5-11


5

Note: The hierarchy on the TN-1Cs with the external sources are set so that one synchronises in a clockwise direction around the ring and the other in a counter-clockwise direction. This is to prevent synchronisation timing loops.

Chain network with two reference sourcesAn example simple chain network with a two reference sources is shown in Figure 5-5.

Figure 5-5SSM within a simple STM-1 chain with two external sources

For a chain network, there must be two reference sources, one at each end of the network. In normal operation, the chain will derive its synchronisation from the primary source. In the event of failure of the primary reference source, the chain will derive its synchronisation from the secondary reference source. In the event of a loss of a link, the chain will divide into two synchronisation islands, one using the primary reference source and the other the secondary reference source.

SSM recommendationsSSM can be used to increase the resilience of the synchronisation network to network faults such as fibre breaks. It can also be used where the network is carrying synchronisation sensitive services such as video.

SSM simplifies some operational aspects of synchronisation design, however, care must be taken to avoid timing loops during the transition to SSM. The following are recommendations regarding SSM:

1 If upgrading from an earlier TN-1C release where the synchronisation is operating correctly, do not use SSM.

2 If SSM is to be deployed:

a. Have a clear understanding of how you wish to configure SSM to operate in your network.

b. Develop a detailed plan for the configuration.

c. Set up the quality levels and priorities on each NE in the network first.

QL = 2

QL = 2TN-1C

PRC

2

15 15

2

15

2

QL = 3SRC

QL = 2TN-1C

QL = 2TN-1C

QL = 2TN-1C



d. Initiate SSM on the NE from which the synchronisation source is derived.

e. Initiate SSM on the next NE in the network.

f. Continue working around the network initiating SSM on each NE in turn.

3 Avoid timing loops:

— During SSM configuration, ensure that there are no NEs without SSM initiated between NEs that have SSM initiated.

— If some NEs do not support SSM, SSM should not be used in that ring or chain.

— Do not mix SSM on a port, i.e. a port should have both or neither RX override and TX override set to SSM.

— If RX override and TX override are not set to SSM, at least one must be set to a QL = 15, i.e. a fixed configured port may use a received synchronisation or transmit a usable synchronisation, but not both.

— Normally a STM tributary port should only be set to a fixed QL, i.e. non-SSM, because either the other end of the link does not support SSM or it is required not to use SSM over that link. This is the case at a network boundary, e.g. span of control limit, operator boundary, inter-link between rings.

4 When an NE uses its Internal synchronisation source as the reference source, it is recommended that the RX and TX override values for the aggregates of that NE are configured to a value of less than 11. This is because the non-configurable Internal source has an QL = 11, which is the same as the holdover QL value (for a digital PLL).

5 If a single NE brings the synchronisation into the network, do not have the aggregates in the synchronisation hierarchy at that NE. This avoids the situation where the aggregates receive a QL which is higher than all others and is consequently selected as the NE QL. In this situation, all NEs would be synchronised off aggregates, resulting in ‘timing loops’ and loss of the external reference source. To resolve this, the synchronisation hierarchy would need to be re-applied.

Non-SSM synchronisation sourcing (TN-1C/TN-1P)When the SSM system is not in use, changes to the selected synchronisation source only occur when a source fails, or if a manual change is performed. Changes due to source failure as subject to software settings restrictions (see “Synchronisation settings” on page 5-6). With SSM off, the TN-1C/TN-1P can operate in one of three modes dependent on the reversion and force settings.

• Manual-only selection mode (MANUAL). In this mode automatic selection of the synchronisation source is disabled. The synchronisation source is selected manually by the user. The user can select any available synchronisation source, no validity check is provided on the selected source. This mode is selected by setting force on and SSM off (the reversion setting has no effect).

Synchronisation 5-13


5

• Automatic switching with manual reversion mode (FALLBACK). In this mode the multiplexer switches to the next highest priority valid source if the selected synchronisation source fails. If a higher priority synchronisation source recovers, it is not automatically selected as the synchronisation source. To switch back to the higher priority source, the user must perform a manual reversion. This mode is selected by setting reversion off, force off and SSM off.

• Automatic switching with automatic reversion mode (REVERSION). In this mode the multiplexer switches to the highest priority valid source available. If a higher priority synchronisation source recovers, the source is automatically selected as the synchronisation source. This mode is selected by setting reversion on, force off and SSM off.

Failure of synchronisation sourceWhen automatic switching is selected (either with manual reversion or automatic reversion), the validity of the source is checked prior to switching. The following alarms and activity detectors are used to determine the validity of the source:

• STM-1 aggregate ports

— RS-LOS

— RS-LOF

— MS-AIS or AU-AIS

— MS-EXC

• 2048 kbit/s, 34368 kbit/s or 44736 kbit/s tributary ports

— PPI-LOS

— PPI-AIS (not applicable to 44376 kbit/s tributary ports)

— PPI-EXC

• External Sync Source Activity Detector

Wait to restore timeWhen a synchronisation source recovers, a check is performed to check that it has recovered for a period of time. The period of time, known as the “wait to restore time” is configurable via the user interface.

Synchronisation alarmsThere are six alarms associated with the synchronisation facility. These are:

• ‘SYNC-Holdover’ - indicates that the multiplexer has entered holdover (using the last known frequency) or free-run (using the internal clock). The alarm is not raised if the internal clock is selected as the primary source.

• ‘SYNC-Source_Fail’ - indicates failure of the currently selected source.

• ‘SYNC-Src_Not_Primary’ - indicates that the primary synchronisation source is not currently selected.

• ‘SYNC-Ext_ Sync_LOS’ - indicates that the external synchronisation source has failed.



• ‘SYNC-Source-Out-of-Limits’ - this alarm is raised against the port in the Signal Status Hierarchy that the Phase Lock Loop (PLL) fails to lock on to it.

• ‘SYNC-SSMB_Unstable’ - this alarm is raised when the QL of the aggregate is not stable (S1 defect is active). Applies only if the SSM_mode is ‘on’ and the aggregate is in the SS Hierarchy.

end of chapter


6-1

6

Performance monitoring 6-The TN-1C or TN-1P multiplexer generates performance monitoring (PM) information from various points in the network element, known as performance monitoring points (PMPs). PM data is not collected for tributaries that are in the ‘traffic off’ or ‘traffic stand-by’ modes.

The synchronous equipment management function (SEMF) of the multiplexer software collects and analyses PM data. The performance information is available to the user via all open sessions of the craft access terminal (CAT) or by the Element Controller EC-1 accessing the embedded user interface software.

PM reporting (to the EC-1) can be configured by the user to suppress zero reports and zero PMPs. This avoids loading network comms with unnecessary messages.

Parity error countsThe multiplexer uses block counts as the basis for PM parity error counts. Block counts are the sum of all bit-interleaved parity (BIP) blocks in error detected in the count period (nominally 1 second).

Performance monitoring countsThere are a number of performance counts that are accumulated within the multiplexer. The following categories of performance monitoring information are generated for each of the PMPs:

• errored seconds (ES). An ES is a second in which at least one anomaly (parity error/code violation) or performance defect (alarm) occurs. The total number of errors is not recorded. See Table 6-1 for a list of anomalies and defects.

• severely errored seconds (SES). An SES is a second in which either a threshold level of anomalies is exceeded or a performance defect occurs. The actual number of errors within this second is not recorded. An SES is also, by definition, an ES. The threshold number of errors which distinguish an ES from an SES can be configured by the user.

• background block error (BBE). A BBE is a block, not included in an SES, in which there is an anomaly.

6-2 Performance monitoring


• unavailable seconds (UAS). A UAS is any second which forms part of a period of unavailable time (UAT). A period of UAT starts with the onset of ten consecutive SESs (included in UAT). The period of UAT ends when there are ten consecutive non-SES seconds (not included in the UAT). UAS is only counted during an AS (assessed second).

Note: During periods of UAT, the ES, SES and BBE statistics are not recorded. The start of the UAT is indicated by ten consecutive SESs. Until this ten seconds is complete, however, it is unclear whether the ES, SES and BBE figures accumulated will be recorded. As a result, there is a ten second delay in all performance monitoring timestamps.

• assessed seconds (AS). The AS is the number of seconds during which the performance monitoring statistics were accumulated. This can be 0 for a particular monitoring point. Typically, this is equivalent to the length of the performance monitoring period. However, if the multiplexer is rebooted, or the performance monitoring period is terminated early, or the clock changes, the AS total may be shorter or longer than the performance period.

Performance monitoring pointsPerformance monitoring points (PMPs) are points at which performance data is collected. This data relates to the quality of the transmission path passing through that point.

Note 1: TN-1C and TN-1P hardware only provides monitoring at a traffic termination path. As a result, no performance data that relates to through traffic can be collected.

Note 2: PDH physical interface code violation (PPI-CV) performance monitoring must not be enabled for ports that have either PPI-AIS consequent actions or monitoring disabled for the port.

The PMPs supported by the TN-1C and TN-1P are:

• MS - multiplexer section

• HP - high-order path

• HP-TIM - high-order path trace identifier mismatch

• HP-FE - high-order path far end

• LP - low-order path

• LP-FE - Low-order path far end

• PPI-AIS - PDH physical interface (PPI) alarm indication signal

• PPI-CV - (PPI) code violations

• PPI-CRC4 - PPI cyclic redundancy check (2 Mbit/s tributaries only)

• PPI-Tx - PPI transmit

• PPI-FRAMED (2 Mbit/s tributaries only)

Performance monitoring 6-3


6

Disabling performance monitoringThe user can configure the multiplexer to enable or disable a PMP. The default value for all PMP instances is OFF. The user can disable the 15 minute and 24 hour PMPs separately on a per monitored point instance basis. If a PMP is disabled, it is not displayed on the current performance count.

Performance anomalies and defectsThe basis for determining performance anomalies and defects are detailed in Table 6-1.

Table 6-1PMP anomalies and defects

PMP Definition Anomalies Defects

MS B2, BIP-24 B2 Errors RS-LOSRS-LCFMS-AISMS-EXC

HP B3, BIP-8 B3 Errors All MS defectsAll RS defectsAU-AISHP-LOM (VC-12 only)INT-AU-AISINT-AU-LOP

HP-FE G1, REI, BIP-8 G1 Errors HP-RDI

LP (VC-12) V5 Bits 1, 2 BIP-2 V5 Errors All RS defectsAll MS defectsAll HP defectsTU-AISTU-LOPINT-TU-AISINT-TU-LOPLP-EXE (see Note 1)

LP (VC-3)(34/45 Mbit/s only)

B3, BIP-8 B3 Errors All RS defectsAll MS defectsAll HP defectsTU-AISTU-LOPINT-TU-AISINT-TU-LOPLP-EXE (see Note 1)

LP-FE (VC-12)

V5 Bit 3, REI, BIP-1 V5 Error HP-RDILP-RDI

LP-FE (VC-3)(34/45 Mbit/s only)

G1, REI, BIP-8 G1 Error HP-RDILP-RDI

PPI-CV(see Note 2)

HDB3 Code Violations(2 Mbit/s and 34 Mbit/s)B3ZS Code Violations(45 Mbit/s)

HDB3 CVB3ZS CV

PPI-LOSPPI-EXE

—continued—



Performance monitoring periodsPerformance monitoring data is accumulated over a performance monitoring period. There are two types of monitoring periods. These are:

• 24 hour monitoring period. Performance monitoring results can be calculated for any 24 hour period. The starting hour for such a period can be configured by the user, though the default start time is midnight.

• 15 minute monitoring period. Performance monitoring results are automatically calculated for each fifteen minute period of the day. The start and end times for 15 minute monitoring periods are fixed on quarter-hour boundaries.

Both 15 minute and 24 hour monitoring periods can be terminated prematurely. In this instance (like scheduled termination), performance results are stored as logs (see “Performance logs” on page 6-5), totals are reset, and a new monitoring period begins immediately.

Note: The exception to the above rule is when a terminated 15 minute period has less than half of its scheduled fifteen minutes remaining. In this instance, the new period will not end at the scheduled end of the current period, but will continue to the end of the next 15 minute period. As a result, the duration of the new period can be 22.5 minutes.

PPI-TX PPI-TF

PPI-FRAMED G704 frame alignment (2 Mbit/s)

G751 frame alignment (34/Mbit/s)

PPI-LOSPPI-EXCPPI-LOFPPI-AIS

PPI-CRC G706 errored blocks PPI-LOSPPI-EXCPPI-LOFPPI-AISPPI-LOM

Note 1: If configured for PPI AIS.

Note 2: PPI-CV performance monitoring must not be enabled for ports that have either PPI-AIS consequent actions or monitoring disabled for the port.

CAUTION15 minute performance monitoringThe wider range of performance monitoring options provides greater flexibility when monitoring service quality. 24 hour performance monitoring is used for normal performance monitoring measurements. 15 minute performance monitoring produces large quantities of data, and should only be used on a manual basis for specific maintenance measurements. Do NOT use it to collect performance monitoring data automatically.

Table 6-1PMP anomalies and defects (continued)

PMP Definition Anomalies Defects



6

Performance logsPerformance logs store the results of individual monitoring periods in which monitoring is active. The following performance logs are available:

• 15 minute performance log.

• 24 hour performance log.

• intermediate performance log.

• UAT performance log. This log displays unavailable time information.

If it is not possible to store a new performance log, the oldest will be deleted. To avoid loss of data, the EC-1 must upload performance monitoring results frequently.

Performance logs are numbered from 1 to 2147483647, with the latest logs having the highest log numbers. Upon reaching the highest log number, the next number returns to ‘1’. The user can also use log numbers between -1 and -16 (for 15 minute logs) and -1 or -2 (for 24 hour logs) to access the latest logs (-1 being the most current log).

15 minute logsThe TN-1C or TN-1P can store up to sixteen 15 minute performance logs. This is equivalent to four hours, assuming that no premature terminations are performed. For the 15 minute report, if a PMP is disabled or no errors are detected during the interval, no data is displayed for that PMP.

Changing the current timeIf the current time is changed during a 15 minute log, the duration of the log is never less than 7.5 minutes and never greater than 22.5 minutes. Table 6-2 summarizes the behaviour of the multiplexer if the start time or current time of the multiplexer are changed. Time changes are recorded in the performance monitoring report and no alarms are raised relating to time changes.

Note: If the log is terminated and the time remaining until the next standard time (quarter-hour boundary) is less than 7.5 minutes, the duration of the next log is also more than 7.5 minutes.

Table 6-215 minute log behaviour after current time change

Log duration until time change (mins.)

Time remaining until next start time

Expected behaviour

Duration of current log (mins)

Duration of next log (mins)

0 to 7.5 Not applicable Continue log 7.5 to 22.5 15

7.5 to 22.5 0 Early termination 7.5 to 22.5 15

15 to 22.5 Not applicable Early termination 15 to 22.5 7.5 to 22.5

7.5 to 15 0 to 7.5 Continue log 7.5 to 22.5 15

7.5 to 15 7.5 to 15 Early termination 7.5 to 15 7.5 to 15



Assessed seconds (AS) countPMPs that are only monitored for part of the duration show this in the AS column.

Log contents after restartsThe contents of the current log are not lost after a warm restart or a configuration switch. The system behaves the same way as for an early termination, except that no report is issued to the user. The log duration could be less than 7.5 minutes.

The contents of the current log are not saved after a cold restart, software release switch, software release upgrade/downgrade, or power up.

24 hour logsA maximum of two 24 hour logs can be stored: the current 24 hour log and the previous 24 hour log. The user can view the two previous logs if they exist. There is no similar zero suppression for the 24 hour logs. Zero counts are displayed if no errors are detected.

Changing start and stop timesIf the current time or start time is changed during a 24 hour log, the duration of the log can change. All time changes are recorded in the performance monitoring report and no alarms are raised relating to time changes. The duration of the 24 hour performance monitoring period can vary if either of the following is changed during that 24 hour period:

• start time of the 24 hour log period

• the time of the multiplexer

The duration of the 24 hour period cannot be less than 12 hours and cannot be greater than 36 hours ±15 minutes. When the start time next occurs, the log then reverts to a 24 hour period again. Table 6-3 summarizes the behaviour of the multiplexer if the start time or current time of the multiplexer are changed.

Table 6-324 hour log behaviour after start time or current time change

Log duration until time change (hours)

Time remaining until next start time

Expected behaviour

Duration of current log (hours)

Duration of next log (hours)

0 to 12 Not applicable Continue log 12 to 36 24

12 to 36 0 Early termination 12 to 36 24

24 to 36 Not applicable Early termination 24 to 36 12 to 36

12 to 24 0 to 12 Continue log 12 to 36 24

12 to 24 12 to 24 Early termination 12 to 24 12 to 24



6

Early terminationIf the user initiates an early termination, both the 15 minute and 24 hour logs are terminated. This causes additional reports for both monitoring periods to be generated at the time the early termination is initiated. Early termination does not affect the configured borders. Time changes that cause premature or non termination of a period, ignore early terminations that may have occurred during the current period in deciding when to terminate next.

The duration of the 24-hour period can be less that 12 hours as a result of an early termination.

Warm restartAfter a warm restart is performed, the system behaves the same as for an early termination, except that an early termination event is not reported.

The duration of the 24-hour period can be less than 12 hours as a result of a warm restart.

Quality of service violation alarmsQuality of service violation (QOSV) alarms are raised on a PMP if any of the ES, SES, BBE and UAS parameters exceed user configurable thresholds. These alarms, which can be enabled and disabled on a PMP basis, can only be raised if both monitoring and alarm raising are enabled for the affected PMP. QOSV thresholds can be defined by the user, on both a BIP and block basis.

Note 1: If alarm raising is disabled for a PMP, monitoring is unaffected. Error counts will still be collated, and results will be stored. These results, however, will not be used to trigger alarm events.

Note 2: If monitoring and alarm raising are enabled for a connection and the physical connector is not present, QOSV alarms will be raised for the PMP and will persist until the end of the current monitoring period.

The QOSV alarms are listed in the following table. For details of these alarms, refer to Alarm Clearing Procedures, 323-1081-543

QOSV alarms

HP-FE_QOSV_15M LP-QOSV_15M PPI-CV_QOSV_15M

HP-FE_QOSV_24H LP-QOSV_24H PPI-CV_QOSV_24H

HP-QOSV_15M MS-QOSV_15M PPI-Frm_QOSV_15M

HP-QOSV_24H MS-QOSV_24H PPI-Frm_QOSV_24H

LP-FE_QOSV_15M PPI-CRC_QOSV_15M PPI-Tx_QOSV_15M

LP-FE_QOSV_24H PPI-CRC_QOSV_24H PPI-Tx_QOSV_24H



The alarm reports the identity of the PMP instance but does not report the parameter type or the threshold value that is crossed. A QOSV alarm is provided for each PMP instance and for each 15-minute and 24-hour measurement period.

Under the following conditions, a delay of up to one minute can occur before the QOSV alarm is reported:

• if the alarm was previously clear and accumulated data exceeds the QOSV threshold for a PMP

• if instance monitoring for a PMP is changed to the ‘enable’ state

• if alarm monitoring is changed to ‘enable’

An alarm is automatically raised when an SES count exceeds the threshold and a PMP moves from AT (available time) to UAT (unavailable time). However, an alarm is not automatically raised when the PMP moves from UAT to AT, as the UAS period is decreased by ten seconds when moving to AT (i.e. when there are ten consecutive non-SES seconds, which are not included in the UAT period).

Enable/disable of QOSV alarmsThe user can enable or disable the reporting of QOSV alarms separately for the 15-minute and 24-hour measurement periods for each PMP. If an alarm is disabled for a PMP, the alarm is in the ‘clear’ state.

Clearing QOSV alarmsFor the 15-minute logs, a QOSV alarm is cleared if no QOSV thresholds are exceeded during the log. In the event of early termination, QOSV alarms for the 15-minute measurement period are cleared for PMP instances which have thresholds less than the QOSV threshold. As a result, 15 minute QOSV alarms can be cleared before the end of the 15 minute period.

Traffic typeThe performance monitoring log contains a traffic type field which can contain the following:

• 2M - 2 Mbit/s non-specific

• 34_45M - 34/45 dual tributary

• STM1o - STM-optical



6

User actionsThe following user actions are available through a user interface session.

• Change the starting time of the accumulation intervals with respect to midnight.

• Display any specific log in the buffer.

• Query for intermediate counts (i.e. before the interval ends) - this intermediate data is not logged.

• Perform early termination of counts - will cause the intermediate counts data to be stored in the logs. The current registers are cleared and the accumulation will continue from zero. This ‘new’ accumulation will terminate at the end of the interval.

• Enable or disable reporting of zero errored PM reports to the EC-1.

When a VC-4 passthrough connection is provisioned at the TN-1C or TN-1P, the high-order path (HP) and the low-order path (LP) related PMPs are disabled.

end of chapter


7-1

7

System parameters 7-This chapter provides system parameters for:

• the TN-1C and TN-1P multiplexers

• Power Supply Unit (PSU) (for TN-1C and standard TN-1P only)

• the TN-1PH headend subrack.

• TN-1P Basestation

CommonElectromagnetic compatibility

The TN-1C, TN-1P, TN-1PH and TN-1P Basestation power supply units (PSUs) comply with the Class B Electromagnetic Compatibility (EMC) requirements and with the Electrostatic Discharge (ESD) requirements defined in:

• EN 55022 - for radiated and conducted emissions

• EN 50082-1 - EMC for residential, commercial, and light industry

Note: To comply with Class B EMC, ferrite attenuators must be fitted to the cables as detailed in Installation Procedures, 323-1081-200.

Environmental conditionsThe TN-1C, TN-1P, TN-1PH and TN-1P Basestation PSU are designed to meet the requirement of ETSI standard ETS 300 019 in the following classes:

Storage (Class 1.2): –25ºC to +55ºC 10% to 100% RH

Transport (Class 2.3): –40ºC to +70ºC(including fast change of temperature)

Operation (Class 3.1): 0ºC to 45ºC5% to 85% RH, non-condensing

7-2 System parameters


ConstructionExternal dimensions

Plastic cased variants and PSU

Metal cased variants

TN-1PH

TN-1P Basestation

WeightTN-1C, TN-1C single-slot, TN-1PLess than 10 kg7.5 kg (PSU with batteries)2.5 kg (PSU without batteries)

TN-1PH8.5 kg (unequipped)20 kg (fully equipped)

TN-1P BasestationLess than 10 kg

Supply voltage–20 V d.c. to –72 V d.c.

Note: This equates to nominal earthed battery station voltages between -24 V and -60 V d.c.

FusesTN-1C Release 1 and 2 hardware3.5 A0.125 A

Height: 430 mm

Depth: 155 mmWidth 280 mm

Height: 430 mm


Height: 650 mm200 mm (fibre tray)


Height: 89 mm (2U)Depth: 300 mmWidth 450 mm

System parameters 7-3


7

TN-1C (Release 3/5/5.1), TN-1P (Release 5.1) and TN-1P Basestation (Release 5/5.1) hardware0.125 ACircuit breaker

TN-1P3 A (Release 3/5)

TN-1PH12 A slow-blow

Maximum power consumption TN-1C

Note: For details of the optional Packet Edge 10 router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

TN-1P

TN-1PH

TN-1P Basestation

Main ADM card 8 x 2 Mbit/s (Release 1 hardware) 24 W

Main ADM card 8 x 2 Mbit/s (Release 3/5/5.1 hardware) 20 W

34/45 Mbit/s tributary extension card 3.4 W

Dual 34/45 Mbit/s tributary extension card 4.5 W

8 x 2 Mbit/s tributary extension card (Release 1 hardware) 5 W

8 x 2 Mbit/s tributary extension card (Release 3/5 hardware) 6.4 W

8 x 2 Mbit/s tributary extension card (Release 5.1 hardware) 6.4 W

24 x 2 Mbit/s tributary extension card (Release 5.1 hardware) 6.4 W

Fan module 1.5 W

Unprotected TN-1P: 10 W maximum

Protected TN-1P: 13 W maximum

Unprotected TN-1PH 135 W (fully equipped with 12 mux and 1 SEP)

Protected TN-1PH 171 W (fully equipped with 12 mux and 1 SEP)

SEP: 15 W maximum

Unprotected TN-1P Basestation

10 W maximum

Protected TN-1P Basestation

13 W maximum



External interfaces2 Mbit/s tributary interfaces

Up to 32 x 2 Mbit/s tributary interfaces are supported, which conform to ITU-T recommendation G.703 and to ETS 300 166 as follows:

34 Mbit/s tributary interfaces (TN-1C only)Up to two 34 Mbit/s tributary interfaces are supported, which conform to ITU-T recommendation G.703 and to ETS 300 166 as follows:

Line rate: 2048 kbit/s ± 50 ppm

Line rate: HDB3

Output pulse height: ±2.37 V ± 10% (75 Ω) peak±3.0 V ± 10% (120 Ω) peak

Nominal pulse width:

244 ns

Cable loss to input: 0 dB to 6 dB at 1024 kHz,

typically: 280 m using 3002 cable330 m using 2002 cable470 m using 2003 cable

Input return loss: not less than 12 dBnot less than 18 dBnot less than 14 dB

(50 kHz to 100 kHz)(100 kHz to 2048 kHz)(2048 kHz to 3072 kHz)

Output return loss: not less than 6 dBnot less than 8 dB

(51.2 kHz to 102.4 kHz)(102.4 kHz to 3072 kHz)


Line code: HDB3

Output pulse height: 1.0 V ± 0.1 V peak

Nominal pulse width: 14.55 ns

Cable loss to input: 0 dB to 12 dB at 17184 kHz,(typically maximum of 250m of 2003 cable)

Input return loss not less than 12 dB (860 kHz to 1720 kHz)not less than 18 dB (1720 kHz to 34368 kHz)not less than 14 dB (34368 kHz to 51550 kHz)

Output return loss not less than 6 dB (859.2 kHz to 1718.4 kHz)not less than 8 dB (1718.4 kHz to 51552 kHz)



7

45 Mbit/s tributary interfaces (TN-1C only)Up to two 45 Mbit/s tributary interface are supported, which conform to ANSI DS-3/TR-NW-000499 definitions as follows:

STM-1 optical interfacesThe STM-1 optical inputs and outputs exceed ITU-T recommendation G.957 for 155.52 Mbit/s STM-1 signals. Three STM-1 optical interface variants are available, these are as follows:

• short reach 1310 nm (application code S-1.1)

• long reach 1310 nm (application code L-1.1) (TN-1C only)

• long reach 1550 nm (application code L-1.2) (TN-1C only)

The short reach 1310 nm (application code S-1.1) optical interface is as follows:

Line rate: 44736 kbit/s ±20ppm

Line code: B3ZS

Pulse height: 0.36 V - 0.85 V (isolated pulse)

Power Level: –4.7 dBm to +3.6 dBm (AIS signal)

Maximum reach in typical installation: 450 ft

Output power: –8 dBm (maximum)–11.5 dB (nominal)–15 dBm (minimum)

Receiver sensitivity: –28 dBm

Receiver overload: 0 dBm

Optical path penalty: 1 dB

Section loss: 0 dB to 12 dB (TN-1C/TN-1P to TN-1C/TN-1P)

Wavelength (nominal): 1310 nm

Operating wavelengthrange:

1270 nm to 1350 nm

Fibre type: monomode



The long reach 1310 nm (application code L-1.1) optical interface is as follows:

The long reach 1550 nm (application code L-1.2) optical interface is as follows:

Output power: 0 dBm maximum–2 dBm nominal–5 dBm minimum

Receiver sensitivity: –34 dBm (at BER of 10-10)

Receiver overload: -3dBm


Section loss: 3 dB to 28 dB (TN-1C to TN-1C)


Operating wavelength range:

1280 nm to 1335 nm

Fibre type: monomode

Output power: 0 dBm maximum–2 dBm nominal–5 dBm minimum

Receiver sensitivity: –34 dBm (at BER of 10-10)

Receiver overload: -3dBm


Section loss: 3 dB to 28 dB (TN-1C to TN-1C)


Operating wavelength range: 1530 nm to 1570 nm

Fibre type: monomode shifted



7

2 Mbit/s external synchronisation inputThe 2 Mbit/s external synchronisation input (TN-1C and TN-1P ADM card upgrades only) conforms to ITU-T recommendation G.703 and to ETS 300 166 as follows:

Craft Access Terminal interfaceA simple asynchronous start-stop protocol, using RS-232C compliant signals, are presented on a 9-pin D-type connector. On the TN-1PH the Craft Access Terminal (CAT) can be switched to any one of the 12 multiplexer units.

The CAT is defined as a data termination equipment (DTE) and the multiplexer is defined as a data communication equipment (DCE):

LAN interfaceA standard 10BaseT LAN interface conforming to IEEE802.3 is used in the TN-1C and TN-1PH and TN-1P ADM card upgrades.


Line rate: HDB3

Output pulse height: ±2.37 V ± 10% (75 Ω) peak

Nominal pulse width:

244 ns

Cable loss to input: 0 dB to 6 dB at 1024 kHz,

typically: 280 m using 3002 cable330 m using 2002 cable470 m using 2003 cable

Input return loss: not less than 12 dBnot less than 18 dBnot less than 14 dB

(50 kHz to 100 kHz)(100 kHz to 2048 kHz)(2048 kHz to 3072 kHz)

Output return loss: not less than 6 dBnot less than 8 dB

(51.2 kHz to 102.4 kHz)(102.4 kHz to 3072 kHz)

Baud rate: 19200 bit/s

Protocol: asynchronous start/stop

Word structure: 8 data bits, no parity, 1 stop bit (8N1)

Flow control: none



ATU interfaceTN-1C Release 1 and 2, TN-1C single-slot, and TN-1P hardware is equipped with an RS232C interface presented on a 9-pin D-type connector, that provides standard connection to telemetry equipment. The TN-1C and TN-1P are defined as data communications equipment (DCE). The RS-232 interface on the TN-1PH is a 25-way D-type connector.

TN-1C Release 3 (onwards) hardware is equipped with a point-to-multipoint RS-485 interface presented on a 5-way terminal block that provides standard connection to telemetry equipment. The TN-1C is a data terminal equipment (DTE).

External alarmsTN-1C and TN-1PEight earth-free inputs and four dry-contact outputs (presented on a 25-way D-type female connector), with the following characteristics:

TN-1PH:

Baud rate: 1200, 2400, 4800, 9600, 19200 bit/s

Protocol: asynchronous start/stop

Word structure: 8 data bits, no parity, 1 stop bit (8N1)

Flow control: none

Inputs: LS TTL with internal pull-up resistor, activated by connecting the alarm lead to the alarm common via a low resistance.

Alarm set: Contact closed, leakage current less than 10 mA at 5 V.

Alarm cleared: Contact open, residual voltage less than 0.5 V at 1 mA.

Outputs Dry-contact relays

Alarm set: Resistance between the leads less than 500 W.

Alarm cleared: Resistance between the leads greater than 100 kW.

Maximum permissible voltage: –60 V (open circuit).

Maximum permissible current: 35 mA (closed circuit).

Alarm set: Short circuit to rack power supply feed earth.

Alarm cleared: Open circuit

Resistance to earth: 25 MΩ (open circuit).

Voltage limits: -12 V to +20 V.



7

Power Supply Unit (TN-1C and standard TN-1P only)A.C. supply

D.C. output–24 V d.c. nominal, 4.5 A maximum

Fusesa.c. 2.5 Ad.c. 7.5 A

Power consumption42 W nominal (battery charged)125 W maximum (for less than 5 minutes, battery discharged).

Power dissipation25 W maximum (battery charging from fully discharged state)

Recommended battery replacement periodReplace at intervals recommended by the battery supplier, if no information is available, Nortel Networks recommend that batteries are replaced every four years.

Alarm outputs

end of chapter

Voltage: 230 V +10% –18% at 50 Hz (189 V to 253 V)115 V +14% –15% at 60 Hz (97.75 V to 131.1 V)

BLV(Battery Low Voltage):

Set if battery voltage falls below 21 V ± 0.5 V

LPF(Line Power Fail):

Set if the charger output d.c. voltage falls below 26.2 V ± 0.5 V

Door Open Alarm: Set if the PSU door is open.


8-1

8

External interfaces 8-The external electrical connections to the TN-1C, TN-1P and TN-1PH are made via their internal connector panels, see Figure 8-1 to Figure 8-7.

The external electrical connections to the TN-1P Basestation are made via the integral front panel connection panel see Figure 8-9. The front panel connectors are extended from their equivalent rear panel connectors via extension cables. Additional external electrical connections to the TN-1P Basestation are accessible (if used) via its internal connector panel, see Figure 8-8.

Note 1: For details of the optional router card external electrical connections, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

STM-1 optical connectors are mounted directly on the TN-1C and TN-1P main multiplexer card.

• Standard connectors are used for all external connectors. The TN-1C, TN-1P, TN-1PH and TN-1P Basestation have the following interfaces:

• 2 Mbit/s 75Ω tributaries

— Coaxial connectors, type 43

• 2 Mbit/s 120Ω tributaries

— 25-way, D-type

• 34/45 Mbit/s 75Ω tributaries (TN-1C only)

— Coaxial connectors, type 43

• STM-1 aggregates

— FC/PC connectors

• Craft access terminal (CAT) interface

— 9-way, D-type

• External alarm input/output interface

— 25-way, D-type (TN-1C and TN-1P only)

— 15-way, D-type (TN-1PH only)

• Power and power alarm interface

— 9-pin ‘Mate-n-lock’ connector (TN-1C and TN-1P only)

8-2 External interfaces


— 6-pin ‘Mate-n-lock’ connector (TN-1PH only)

• Local area network (LAN) interface

— RJ45 socket (10BaseT) (TN-1C, TN-1PH and TN-1P ADM card upgrades only)

• Asynchronous telemetry unit (ATU) interface

— 9-way, D-type (TN-1C Release 1 and TN-1P)

— RJ485 5-way, WAGO-type connector (TN-1C Release 3 onwards)

— 25-way D-type (TN-1PH only)

• External synchronisation input

— Coaxial connector, type 43 (TN-1C and TN-1P ADM card upgrades only)

For detailed information on connector types, part numbers, and connections, refer to ‘Installation Procedures’, 323-1081-200.

External interfaces 8-3


8

Figure 8-1TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version) Release 1 hardware

Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

Tx5 Rx5

Rx6

Rx7

Rx8

Tx6

Tx7

Tx8

Tx1 Rx1

Rx2Tx2

d.c.

a.c.

Lk 1

The earth connection of the tributary is set using a physical link. Here the link is set to the a.c. option.

Fan connector

Alarms

2 Mbit/s120 Ω tributary connectors (Tx) 8x2 Mbit/s ADM card

2 Mbit/s 120 Ω tributary connectors (Rx)8x2 Mbit/s ADM card

Telemetry B (not supported at this release)

Telemetry A (ATU)

LAN

CAT

34/45 Mbit/s tributary connectors, requires extension card

75 Ω a.c./d.c. selector links

2 Mbit/s 75 Ω tributary connectors8x2 Mbit/s ADM card

Microswitch(door alarm)

On/off switch

Fuse

d.c./alarms input



Figure 8-2TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version) Release 3/5 hardware

2 Mbit/s 120 Ω tributary connectors (Tx)8x2 Mbit/s ADM card

Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

Tx5 Rx5

Rx6

Rx7

Rx8

Tx6

Tx7

Tx8

Tx1 Rx1

Rx2Tx2


Fan connector

LAN

34/45 Mbit/s tributary connectors, requires extension card

Alarms

CAT

d.c./alarms input



2 Mbit/s 120 Ω tributary connectors (Rx)8x2 Mbit/s ADM card

2 Mbit/s 75 Ω tributary connectors8x2 Mbit/s ADM card

d.c. filter

ATU

Auxiliary telemetry(not currently supported)

External synchronization connectors (only input currently supported)

Circuit breaker

SH

OR

T

NO

RM

AL

SY

S D

OO

R

PW

R D

OO

R

The TN-1C and PSU door alarms are enabled or disabled using physical links. Here the SYS DOOR link (TN-1C) is set to the NORMAL option enabling the NE-Door_Open alarm. The PWR DOOR link (PSU) is set to the SHORT option disabling the PS-Door_Open alarm.

SY

S D

OO

R

PW

R D

OO

R

OUTPUT INPUT

DC

AC

LK1

SH

OR

T

NO

RM

AL

Fuse



8

Figure 8-3TN-1C connection panel (16 x 2 Mbit/s version) Release 1 hardware

2 Mbit/s tributary connectors (120Ω)requires extension card

34/45 Mbit/s tributary connectors (120Ω)requires extension card

Tx1 Rx1

Rx2Tx2

Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

Tx5 Rx5

Rx6

Rx7

Rx8

Tx6

Tx7

Tx8

Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

Tx5 Rx5

Rx6

Rx7

Rx8

Tx6

Tx7

Tx8

Rx

Tx

A

D C

B

d.c.

a.c.

Lk 1


Telemetry A: ATUTelemetry B,C,D: not supported in this release

2 Mbit/s tributary connectors (75Ω)8x2 Mbit/s ADM card

2 Mbit/s tributary connectors (75Ω)requires extension card

2 Mbit/s tributary connectors (120Ω)8x2 Mbit/s ADM card

External alarms

CAT

Fuse

d.c. alarms input

On/off switch

Fan connector

LANFuse



Figure 8-4TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5 hardware

Tx1 Rx1

Rx2Tx2

Rx

Tx


Fan connector

LAN

Fuse

2 Mbit/s tributary connectors (120 Ω)8x2 Mbit/s ADM card

2 Mbit/s tributary connectors (120 Ω)requires extension card

34/45 Mbit/s tributary connectors requires extension card

CAT

d.c./alarms inputCircuit breaker

2 Mbit/s tributary connectors (75 Ω)requires extension card

2 Mbit/s tributary connectors (75 Ω)8x2 Mbit/s ADM card

Note: Although sufficient physical connectors are available for sixteen (75 or 120 Ω) 2 Mbit/s and two 34/45 (75 Ω only) Mbit/s tributaries, these cannot be operated. Allowable configurations are sixteen 2 Mbit/s tributaries or eight 2 Mbit/s and one or two 34/45 Mbit/s tributaries.

Alarms


ATU

External synchronization connectors (only input currently supported)

The PSU door alarm is enabled or disabled using a physical link. Here the POWER DOOR link is set to the NORMAL option enabling the PS-Door_Open alarm.

PO

WE

R

INPUT

d.c.

a.c.Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

Tx5 Rx5

Rx6

Rx7

Rx8

Tx6

Tx7

Tx8

Tx9 Rx9

Rx10

Rx11

Rx12

Tx10

Tx11

Tx12

Tx13 Rx13

Rx14

Rx15

Rx16

Tx14

Tx15

Tx16

OUTPUT

SH

OR

T

NO

RM

AL

PO

WE

R D

OO

R

DO

OR

d.c. filter



8

Figure 8-5TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1 hardware

d.c./alarms input

Circuit breaker

Fan B(not used)

Fan Aconnector

2 Mbit/s tributary connectors (120 Ω)(requires extension card for more than 8 x 2 Mbit/s)

LAN

Alarms

CAT


34/45 Mbit/s tributary connectors requires extension card (two pairs)

ATU

External synchronisation connectors (output not supported)

CAL

SYNC in SYNC out

RX 120 Ω (1-8)

TX 120 Ω (1-8)

TX 120 Ω (25-32)

RX 120 Ω (25-32)

2 Mbit/s tributary connectors (120 Ω)(requires extension card)

RX 120 Ω (9-16)

TX 120 Ω (9-16)

RX 120 Ω (17-24)

TX 120 Ω (17-24)

TX

TX RX

F1Fuse

Microswitch (door alarm)

d.c filter

Connector for upper (second) Optional 75 Ω Interface Card

Mounting position of optional 8 x 75 Ω Interface Card

Connector for lower (first) Optional 75 Ω Interface Card

DC

AC


SHORT

NORMAL

POWER DOOR

Note: The PSU door alarm is enabled or disabled using a physical link. Here the POWER DOOR link is set to the NORMAL option enabling the PS-Door_Open alarm.

(See Note)

Interna calibration- manufacturing aid only.(Not used)

Norm

Short

RX

DC

AC



Figure 8-6TN-1C optional 75 ΩΩΩΩ interface cards for Release 5.1 hardware

16 Type 43 75 Ω tributary connectors (8 Pairs)

d.c.

a.c.

75 Ω a.c./d.c. selector links.The earth connection of the tributary is set using a physical link. Here the link is set to the a.c. option.

Second (optional) card fits over remaining four 120 Ω connectors (covers 34/45 Mbit/s connectors)Note: The numbering convention (at Release 5.1) for additional tributary port connections is right (bottom) to left (top).

TX1 RX1

RX2

RX3

RX5

RX6

RX7

RX8

TX2

TX3

TX4

TX5

TX6

TX7

TX8

RX 120 Ω (1-8)

TX 120 Ω (1-8)

TX 120 Ω (25-32)

RX 120 Ω (25-32)

RX 120 Ω (9-16)

TX 120 Ω (9-16)

RX 120 Ω (17-24)

TX 120 Ω (17-24)

TX

TX

RX

RX

F1

Mounting position of optional 8 x 75 Ω Interface Cards

TX1 RX1

RX2

RX3

RX4

RX5

RX6

RX7

RX8

TX2

TX3

TX4

TX5

TX6

TX7

TX8

First (optional) card fits over four 120 Ω connectors (leaving 34/45 Mbit/s connectors revealed)Note: The numbering convention (at Release 5.1) for additional tributary port connections is right (bottom) to left (top).

Mounting connector (right-hand half only)

RX4

Note:With no optional 75 Ω Interface Cards fitted:– up to 16 or 32 120 Ω 2 Mbit/s interfaces are available, or – up to 16 or 32 120 Ω 2 Mbit/s interfaces and one or two 34/45 Mbit/s interfaces are available.With one optional 75 Ω Interface Card fitted:– up to 8 75 Ω 2 Mbit/s interfaces and up to 16 120 Ω 2 Mbit/s interfaces are available, or– up to 8 75 Ω or 120 Ω 2 Mbit/s interfaces and one or two 34/45 Mbit/s interfaces are available.With two optional 75 Ω Interface Cards fitted up to 16 75 Ω 2 Mbit/s interfaces are available.

PORT LAYOUT DIFFERSFROM PREVIOUS RELEASES



8

Figure 8-7TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware

Tx1 Rx1

Rx2

Rx3

Rx4

Tx2

Tx3

Tx4

2 Mbit/s tributary connectors (75 Ω)

External alarmsconnector

120 Ω tributaryconnnectors (Tx)

120 Ω tributaryconnnectors (Rx)

Craft Access Terminal

Not used

120 Ω a.c./d.c. selector link

On/off switch


Fuse

d.c./alarms input

ATU connector


Not used



Figure 8-8TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C single-slot connection panel (8 x 2 Mbit/s)

RX

INO

UT

EX

T S

YN

C

TX

NO

RM

SH

OR

T

PWR DOOR

CAT

/C

CAT

/PT

X1

TX

8R

X8

RX

1C

AL

Fan connector LAN(see Note 1)

Circuit breaker

Fuse

SHORT

NORMAL

PW

R D

OO

R

External synchronisation connectors (see Note 1)

d.c.


DC filter

Internal calibration (manufacturing aid only)

Telemetry(ATU)

DC/alarms input

75 Ωtributary

connectors

Alarms

120 ΩTributaries

(Tx)

120 ΩTributaries

(Rx))

Craft accessterminal (CAT), see Note 2.

‘Lump Plug’ for low voltage –24 V d.c. connection. Provides connection to an a.c./d.c. rectifier(currently not used).

Physical link, for equipment identification purposes.Note: Default, factory setting is CAT/P

The PSU door alarm is enabled or disabled using a physical link. Here the POWER DOOR link is set to the NORMAL option enabling the PS-Door_Open alarm.Note: Normally set to ’short’.

a.c.

Note 2 : The TN-1P Basestation has front access for eight 75 Ω BNC pairs, CAT and Power connectors only (linked to the front connector panel via terminated extension cables).

Note 1 : TN-1P and TN-1P Basestation fitted with an 8 x 2 Mbit/s ADM card support LAN and External synchronisation input.



8

Figure 8-9TN-1P Basestation (integral front panel connectors)

Optical Interface Connectors

Power Connector

Craft AccessTerminal (CAT)

2 Mbit/s75 Ω Tributary Interfaces

Front View

Multiplexer

RxATxA

TX1 TX2 TX3 TX4 CAT POWER

Wrist strap earthing point

Only used if Multiplexer is upgraded (to 8 x 2 Mbit/s)

RX1 RX2 RX4RX3

Used for 1 +1 protected variant

TX1 TX2 TX3 TX4

RX1 RX2 RX4RX3

RxBTxB



Figure 8-10TN-1PH connector panel

Tx Rx1 Tx Rx2 Tx Rx3 Tx Rx4 Tx Rx5 Tx Rx6 Tx Rx7 Tx Rx8 Tx Rx9 Tx Rx10 Tx Rx11 Tx Rx12

2Mbi

t 120

Ω ΩΩΩ2M

bit 7

5 Ω ΩΩΩ

RE

CE

IVE

2Mbi

t 75

Ω ΩΩΩ T

RA

NS

MIT

POWER

RS

-232

TELEMETRY1-6 7-12

LANSHELF SYSTEM

ALARMS

1

2

3

4

1

2

3

4

DC AC

RAU



8

D-type connectorsThe TN-1C and TN-1P external interface D-type connectors follow standard pin numbering as shown in Figure 8-11.

Figure 8-11Standard pin numbering for D-type connectors

2 Mbit/s 75 ΩΩΩΩ tributary interfacesThe 2 Mbit/s 75Ω tributary interfaces use type 43 connectors to connect coaxial cables. Two connectors are used for each interface (receive and transmit).

LinksTransmit connectors - the shield is short circuited to the earth (d.c. coupled)

Receive connectors - the shield connection to the earth is selectable by a link giving the following options:

• d.c. coupled (short circuit)

• a.c. coupled (connected via an isolating capacitor)

2 Mbit/s 120 ΩΩΩΩ tributary interfacesTwo (or four in a 16 x 2 Mbit/s system) (or eight in a 32 x 2 Mbit/s system) 25-pin D-type connectors are used to carry the output and input 8 x 2 Mbit/s (or 16 x 2 Mbit/s) (or 32 x 2 Mbit/s) tributaries. The input connectors are male, while the output connectors are female.

CAUTIONRisk if operational problems.Do not remove or reposition links without referring to Nortel Networks engineers.

113

25 14

25-way D-type female

131

2514

25-way D-type male

Connectors are shown looking from the outside into the shell



34/45 Mbit/s tributary interfaces (TN-1C only)The two 34/45 Mbit/s 75Ω tributary interfaces use Type 43 connectors to connect to coaxial cables. Two connectors are used for each (receive and transmit).

LinksTransmit connectors - the shield is short circuited to the earth (d.c. coupled)

Receive connectors - the shield connection to the earth is selectable by a link giving the following options:



Table 8-12 Mbit/s 120 ΩΩΩΩ connector tributary allocation

Tributary number Pin number

main ADM card

with 8 x 2 Mbit/s or 24 x2 Mbit/s extension card

with 24 x 2 Mbit/s extension card

with 24 x 2 Mbit/s extension card

1 9 17 25 9 & 22

2 10 18 26 12 & 25

3 11 19 27 11 & 23

4 12 20 28 8 & 20

5 13 21 29 6 & 19

6 14 22 30 5 & 17

7 15 23 31 2 & 14

8 16 24 32 3 & 16

See note 1,4,7,10,13,15,18,21,24

Note: Some of these pins are routed to the extension slot for future support.

CAUTIONRisk of operational problemsDo not remove or reposition links without consulting Nortel Networks engineers.



8

Optical interfacesThe STM-1 optical interface is via standard FC-PC connectors mounted directly on the TN-1C or TN-1P multiplexer circuit board. The TN-1C or TN-1P (if 1+1 protected) is equipped with two electro-optical modules and four FC-PC connectors, i.e. two transmit connections and two receive connections.

The optical connectors are arranged vertically as follows:

TxARxATxBRxB

Craft access terminal interfaceThe TN-1C Craft Access Terminal (CAT) port is an RS-232C interface using a 9-way D-type connector and provides for a standard connection to a CAT. The CAT is defined as a data termination equipment (DTE), while the TN-1C is defined as a data communication equipment (DCE). The pin assignments of the CAT are shown in Table 8-2.

Table 8-2Craft access terminal connector pin assignments

CAT (9 way female D-type)

Pin No.

Signal name

Function Signal direction

1 not used

2 RxD Received data output from TN-1C

To CAT

3 TxD Transmit data from terminal to TN-1C

From CAT

4 not used

5 Common Signal Common Bidirectional

6 not used

7 RTS Request to send From CAT

8 CTS Clear to send To CAT

9 not used

1

5

6

9



ATU interface (TN-1C Release 1 and 2 and TN-1C single-slot hardware and TN-1P)

The ATU interface is an RS232C interface using a 9-way female D-type with ‘screw on’ locking capability that provides standard connection to telemetry equipment. The pin-out is shown in Table 8-3.

ATU interface TN-1C (Release 3/5/5.1 hardware)The ATU interface is an RS-485 interface using a 5-way terminal block. The pin-out is shown in Table 8-4.

Table 8-3TN-1C ATU interface connector pin-out

Telemetry (9 way female D-type)

Pin Signal name

Description Direction

1 not used

2 RxD Receive data output from TN-1C from TN-1C/TN-1P

3 TxD Transmit data to TN-1C to TN-1C/TN-1P

4 not used

5 Common Signal Common bi-directional

6 not used

7 RTS Request to send to TN-1C/TN-1P

8 CTS Clear to send from TN-1C/TN-1P

9 not used

Table 8-4TN-1C ATU interface connector pin-out

ATU interface (5-way terminal block)

Pin Signal name

Description Direction

5 GND Ground

4 TxA Transmit data A to TN-1C to TN-1C

3 TxB Transmit data B to TN-1C to TN-1C

2 RxA Receive data A from TN-1C from TN-1C

1 RxB Receive data B from TN-1C from TN-1C

1

5

6

9

54321

Wire receptacles

Releaselevers



8

TN-1P HeadendThe ATU interface is an RS232C interface using two 25-way female D-type connectors (female) with ‘screw on’ locking capability that provides standard connection to telemetry equipment. The pin-out is shown in Table 8-5.

Table 8-5TN-1PH ATU interface connector pin-out

Telemetry (25 way female D-types)

Pin Function Direction Connector 1

Connector 2

1 TxD To TN-1P MPP #1 MPP #7

2 RxD From TN-1P

3 RTS To TN-1P

4 CTS From TN-1P


6 RxD From TN-1P

7 RTS To TN-1P

8 CTS From TN-1P


10 RxD From TN-1P

11 RTS To TN-1P

12 CTS From TN-1P

13 Common


15 RxD From TN-1P

16 RTS To TN-1P

17 CTS From TN-1P


19 RxD From TN-1P

20 RTS To TN-1P

21 CTS From TN-1P


23 RxD From TN-1P

24 RTS To TN-1P

25 CTS From TN-1P

1

13

14

25



Fan interface (TN-1C and TN-1P Release 5.1 hardware) The fan interface is a 6-pin male ‘Mate-n-Lock’ mounted on the connection panel. As stated in Table 8-6, pins 3 and 6 must be linked on the fan connector.

2 Mbit/s external synchronisation inputThe 2 Mbit/s 75Ω external synchronisation input (TN-1C and TN-1P ADM card upgrades only) uses a type 43 connector to connect to the coaxial cable.

Note: The external synchronisation output is not used in current systems.

LinksReceive connectors - the shield connection to the earth is selectable by a link giving the following options:



Table 8-6Fan connector pin assignment

Fan (6 way male ‘Mate-n-Lock’)

Pin No.

Signal name Description

1 FAN_V+ +V to the fan

2 not connected not connected

3 GND Link to pin 6

4 FAN_V- -V to the fan

5 FAN_CON_IN FAN control

6 FAN_IN (Link to pin 3) FAN connected

CAUTIONRisk if operational problems.Do not remove or reposition links without referring to Nortel Networks engineers.

3 2 1

6 5 4



8

External alarm interfaceThe external alarm interface uses a 25-way D-type connector with ‘screw-on’locking capability. The pin assignments for TN-1C and TN-1P are shown in Table 8-7. The pin assignments for TN-1PH are shown in Table 8-8.

Table 8-7Pin assignments of the external alarm interface (TN-1C and TN-1P)

External alarms (25 way female D-type)

Pin Function

1 Alarm I/P 1

2 Alarm I/P 2

3 Alarm I/P 3

4 Alarm I/P 4

5 Alarm common

6 not connected

7 Alarm O/P 1+ (see note)

8 not connected

9 Alarm O/P 2+ (see note)

10 not connected (-48 V Release 3 hardware only)

11 Alarm O/P 3 + (see note)

12 not connected

13 Alarm O/P 4 + (see note)

14 Alarm I/P 5

15 Alarm I/P 6

16 Alarm I/P 7

17 Alarm I/P 8

18 not connected(0 V Release 3 hardware only)

19 Alarm O/P 1 – (see note)

20 not connected


22 not connected


24 not connected


Note: When the rack alarms mode is selected, the following alarms are designated:

Alarm O/P 1 — Prompt/DeferredAlarm O/P 2 — In StationAlarm O/P 3 — REC ATTAlarm O/P 4 — Fault Clear

1

13

14

25



Table 8-8Rack alarms connector pin-out (TN-1PH)

Pin Function

1 –12 V

2 Prompt alarm

3 not used

4 In Station alarm

5 reserved

6 –48RTN

7 –48RTN

8 –48RTN

9 reserved

10 Receive Attention

11 not used

12 Fault Clear

13 reserved

14 –48RTN

15 –48RTN

8 15

91



8

Power and power alarm interfacePower is supplied to the TN-1C and TN-1P via a 9-way male ‘Mate-n-Lock’ power connector. The pin assignments are shown in Table 8-9. The d.c. power feed to the TN-1C or TN-1P system (Release 1 and 2 hardware only) is enabled by a on/off switch on the connector panel. The switch is accessible after removal of the TN-1C or TN-1P cover. The pin assignments for the TN-1PH are shown in Table 8-10.

D.C. power feed to Release 3 hardware is enabled through a circuit breaker. The circuit breaker is also accessible after removal of the TN-1C cover.

Table 8-9D.C./alarm connector pin assignment (TN-1C and TN-1P)

TN-1C and PSU (9 way male ‘Mate-n-Lock’)

Pin No. Name Function

1 VS RTN d.c. return

2 BLV PS-Battery_Low_Voltage

3 LPF PS-Power_Fail

4 ALGND Alarm earth/common

5 VS Minus d.c. feed power –20 V to -72 V

6 Shield Shielding

7 — not used

8 — not used

9 DR_ALRM_PWR PS-Door_Open

Table 8-10D.C. connector assignment (TN-1PH)

6 way male ‘Mate-n-Lock’(positronix PLB06M900A1)

Pin Function

1 –48RTN

2 –48V

3 Shield (not connected)

4 not connected

5 not connected

6 Shield (not connected)

9 6 3

8 5 2

7 4 1

1

23

4

56



LAN interfaceFor the TN-1C, TN-1PH and TN-1P ADM card upgrades, an external 10BaseT LAN interface (as defined in IEEE802.3) is provided for connection of the element controller EC-1. For the TN-1PH, two RJ45 LAN connectors are provided (see Figure 8-10). Use the connector labelled ‘SYSTEM’.

Note: The connector labelled ‘SHELF’ is reserved for future use.

The LAN connector pinout is shown in Table 8-11.

Table 8-11LAN connector pin assignments (TN-1C, TN-1PH and TN-1P ADM card upgrades)

RJ45 Plug (10BaseT)

Pin No. Function

1 LAN output +

2 LAN output –

3 LAN input +

4 not connected

5 not connected

6 LAN input –

7 not connected

8 not connected

1 2 3 4 5 6 7 8



8

Rack alarm adaptorThe rack alarm adaptor (rack alarm adaptor to TN-1C and standard TN-1P) uses a 25-way male D-type connector with ‘screw-on’ locking capability. The pin assignments are shown in Table 8-12.

Table 8-12Pin assignments of the rack alarm adaptor

External Alarms Interface (25 way male D-type)

Pin Function

1 not used

2 not used

3 not used

4 not used

5 Alarm common

6 not used

7 EAOut_1+

8 not used

9 EAOut_2+

10 –48 V RAA supply (from rack)

11 EAOut_3+

12 not used

13 EAOut_4+

14 not used

15 not used

16 not used

17 EAIn_8

18 Ground (return to rack)

19 EAOut_1–

20 not used

21 EAOut_2–

22 not used

23 EAOut_3–

24 not used

25 EAOut_4–

Note: When the rack alarms mode is selected, the following alarms are designated:

Alarm O/P 1 — Prompt/DeferredAlarm O/P 2 — In StationAlarm O/P 3 — REC ATTAlarm O/P 4 — Fault Clear

1

13

14

25



Rack alarm bus connectorThe rack alarm bus connector (rack alarm adapter to rack alarm bus) uses a 15-way male D-type connector. The pin assignments are shown in Table 8-13.

FusesTN-1C Release 1 and 2 and TN-1P Release 5 hardware have the following fuses mounted on the connection panel:

3.5 A0.125 A

TN-1C (Release 3/5/5.1 hardware), TN-1P (Release 5.1 hardware), TN-1P Basestation (Release 5/5.1 hardware), and the single-slot TN-1C has the following mounted on the connection panel:

0.125 A fuseCircuit breaker

end of chapter

Table 8-13Pin assignments of the rack alarm bus connector

Pin No. Description

1 –12 V

2 Prompt alarm

3 not used

4 In station alarm

5 not used

6 0 V

7 0 V

8 0 V

9 not used

10 Receive attention

11 not used

12 Fault clear

13 –48 V (optional)

14 0 V

15 0 V


9-1

9

Ordering codes 9-TN-1C only

Each item has a unique eight character alphanumeric code.

Table 9-1 lists the main equipment versions for wall and rack mounted TN-1C applications. Table 9-2 to Table 9-5 lists the main units required for TN-1C applications. Table 9-14 details the Power Supply Unit and cables.

The software required to run the TN-1C, TN-1P and CAT is detailed in Table 9-15. The rack mounting kit is detailed in Table 9-16.

Table 9-19 lists obsolete codes (cannot be ordered) that are supported by the Release 5.2 software.

Note 1: A dummy card must be ordered with each unequipped unit, to comply with electro-magnetic compatibility (EMC) requirements.

Note 2: For 75 Ω operation with TN-1C Release 5.1 hardware, you must order the relevant number of 75 Ω I/O adaptors (see Table 9-5).

Note 3: For information on ordering the optional Packet Edge 10 router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.

Table 9-1TN-1C versions (Release 5.1 hardware)

Version Ordering code

All the units in this table are supplied in a plastic case and are upgradeable with an extension card to provide 32x2 Mbit/s tributaries, up to two 34/45 Mbit/s tributaries, or a Packet Edge 10 router.

TN-1C 8x2 ADM & Dummy card (S-1.1 optics)TN-1C 8x2 ADM & Dummy card (L-1.1 optics)TN-1C 8x2 ADM & Dummy card (L-1.2 optics)

NTFT52CA+NTFT32AA NTFT52CD+NTFT32AA NTFT52CG+NTFT32AA

TN-1C 8x2 ADM & 1x34/45 extension card (S-1.1 optics)TN-1C 8x2 ADM & 1x34/45 extension card (L-1.1 optics)TN-1C 8x2 ADM & 1x34/45 extension card (L-1.2 optics)

NTFT52CA+NTFT31AC NTFT52CD+NTFT31AC NTFT52CG+NTFT31AC

TN-1C 8x2 ADM & 2x34/45 extension card (S-1.1 optics) TN-1C 8x2 ADM & 2x34/45 extension card (L-1.1 optics)TN-1C 8x2 ADM & 2x34/45 extension card (L-1.2 optics)

NTFT52CA+NTFT31AD NTFT52CD+NTFT31AD NTFT52CG+NTFT31AD

—continued—

9-2 Ordering codes


TN-1C 16x2 (8x2 ADM & 8 x 2 Mbit/s extension card) (S-1.1 optics)TN-1C 16x2 (8x2 ADM & 8 x 2 Mbit/s extension card) (L-1.1 optics)TN-1C 16x2 (8x2 ADM 8 x 2 Mbit/s extension card) (L-1.2 optics)

NTFT52CA+NTFT08AC NTFT52CD+NTFT08ACNTFT52CG+NTFT08AC

TN-1C 32x2 (8x2 ADM & 24x2 extension card) (S-1.1 optics)TN-1C 32x2 (8x2 ADM & 24x2 extension card) (L-1.1 optics)TN-1C 32x2 (8x2 ADM & 24x2 extension card) (L-1.2 optics)

NTFT52CA+NTFT24BANTFT52CD+NTFT24BANTFT52CG+NTFT24BA

Note 1: A TN-1C PSU (Table 9-14) or a customer supplied d.c. supply is required unless the TN-1C is rack mounted and using the rack power supply.

Note 2: If the units are to be rack mounted, then a rack mounting kit (Table 9-16) is required.

Note 3: For 75 Ω operation on TN-1C Release 5.1 hardware, you must also order the relevant number of 75 Ω I/O adaptors. Order 1 adaptor (NTFT09AA) for 8x2 Mbit/s 75 Ω configurations or 2 adaptors (NTFT09AA) for 16x2 Mbit/s 75 Ω configurations. See Table 9-5 for details.

Table 9-2TN-1C multiplexers (Release 5.1 hardware)


8 x 2 Mbit/s ADM card with short range 1310 nm optics NTFT02BA

8 x 2 Mbit/s ADM card with long range 1310 nm optics NTFT02BB

8 x 2 Mbit/s ADM card with long range 1550 nm optics NTFT02BC

Table 9-3TN-1C extension cards (Release 5.1 hardware)


Dummy card NTFT32AA

1x34/45 extension card NTFT31AC

2x34/45 extension card NTFT31AD

8 x 2 Mbit/s extension card NTFT08AC

24 x 2 Mbit/s extension card NTFT24BA

Table 9-4TN-1C single-slot (Release 5.1 hardware)


TN-1C single slot with 1310 nm ADM pack NTFT51CD

TN-1C single slot with 1310 nm LH ADM pack NTFT51CE

TN-1C single slot with 1550 nm LH ADM pack NTFT51CF

Table 9-1TN-1C versions (Release 5.1 hardware) (continued)


Ordering codes 9-3


9

TN-1P onlyTable 9-6 and Table 9-7 list the main units required for protected and unprotected wall and rack-mounted TN-1P applications.

Table 9-8 lists the main units required for TN-1P protected and unprotected headend applications.

Table 9-9 to Table 9-11 list the main units required for TN-1P protected and unprotected Basestation applications.

The software required to run the TN-1P and CAT is detailed in Table 9-15. The rack mounting kit is detailed in Table 9-16.

Table 9-5TN-1C additional items (Release 5.1 hardware)

Item Ordering code

Dual fan kit NTFT06GA

75 Ω I/O adapter (8 x 2) (see Note) NTFT09AA

Note: For 75 Ω operation on TN-1C Release 5.1 hardware, order 1 adaptor for 8x2 Mbit/s configurations or 2 adaptors for 16x2 Mbit/s configurations.

Table 9-6Unprotected TN-1P

Item Code

TN-1P Release 5.1 NTFT51CA

Note 1: Requires TN-1P PSU (Table 9-14) or a customer supplied d.c. supply.

Note 2: Requires Rack mounting kit (Table 9-15) if rack mounted.

Table 9-71+1 protected TN-1P

Item Code

TN-1P (1+1) Release 5.1 NTFT51CB

Note 1: Requires TN-1P PSU (Table 9-14) or a customer supplied d.c. supply.

Note 2: Requires Rack mounting kit (Table 9-15) if rack mounted.

9-4 Ordering codes


Table 9-8TN-1P headend equipment

Item Code

TN-1P Subrack Release 5.1Comprising:Subrack End Processor NTFT10AA

CAP NTFT1302Backplane NTFT07ADCable (CAP to Backplane) TLFT0711Subrack chassis

NTFT07AA

TN-1P MPP (1 to 12 as required) NTFT01JC

TN-1P (1+1) MPP (1 to 12 as required) NTFT01JF

Fibre tray NTFT07AC

Interface area cover NTFT07AB

Table 9-9TN-1P Basestation (unprotected 4 x 2 Mbit/s)

Item Code

TN-1P Basestation (Release 5.1) NTFT51CC +NTFT01BC

Table 9-101+1 protected 4 x 2 Mbit/s TN-1P Basestation (1+1 protected 4 x 2 Mbit/s)

Item Code

TN-1P Basestation (Release 5.1) NTFT51CC +NTFT01BF

Table 9-11TN-1P Basestation (8 x 2 Mbit/s ADM)

Item Code

TN-1P Basestation (Release 5.1) NTFT51CC +NTFT02BA

Table 9-12TN-1P multiplexers

Version Code

unprotected 4 x 2 Mbit/s NTFT01BC

1+1 protected 4 x 2 Mbit/s NTFT01BF

Ordering codes 9-5


9

Upgrade itemsTable 9-11 lists the main units required to upgrade a 4 x 2 Mbit/s TN-1P Basestation to an 8 x 2 Mbit/s ADM with limited functionality.

Common itemsTable 9-14 to Table 9-18 list items common to the TN-1C and the TN-1P.

Table 9-13TN-1P Basestation (upgrade to 8 x 2 Mbit/s ADM)

Item Code

TN-1C 8x2 ADM card short range 1310 nm optics NTFT02BA

Tributary extension cable(8 required, for Release 5 upgrade only)

–

Table 9-14Power supply unit

Equipment description Ordering code

AC/DC power unit NTFT21AA

SLA battery (optional) NTFT24AA

AC cable (optional) NTFT15AB

Table 9-15Software

Software description Ordering code

Release 5.2 software

TN-1C and TN-1P Release 5.2 S/W kit (disk and tape) NTFT81EC

TN-1C and TN-1P Release 5.2 S/W (DAT tape) NTFT92EC

TN-1C and TN-1P Release 5.2 S/W (disk) NTFT93EC

TN-1C and TN-1P Release 5.2 S/W (download from Preside, DAT tape)

NTQJ32HE

Table 9-16Rack mounting kit


Rack mounting installation kit NTFT06AA

TEP-1e rack mount brackets NTFT06AD

Note: This rack mounting installation kit is to be used in conjunction with the equipment detailed in Table 9-2.

9-6 Ordering codes


Obsolete codesTable 9-19 lists codes that are obsolete and cannot be ordered, but are supported by the Release 5.2 software.

Table 9-17Rack alarm adaptor


Rack alarm adaptor NTFT06BA

Table 9-18Single fibre working coupler


Single fibre working coupler with tails NTKD0101

Note: The coupler is only required if single fibre working is required.

Table 9-19Obsolete codes


TN-1C (Release1/3/5 hardware)

TN-1C 8 x 2 Mbit/s ADM (Release 1) with S1.1 optics NTFT02AA

TN-1C 8 x 2 Mbit/s extension card NTFT08AB

TN-1C 1 x 34/45 Mbit/s extension card NTFT31AA

TN-1C 2 x 34/45 Mbit/s extension card NTFT31AB

TN-1C 8x2 ADM (S-1.1 optics)TN-1C 8x2 ADM (L-1.1 optics)TN-1C 8x2 ADM (L-1.2 optics) These units are supplied in a plastic case and are upgradeable to provide up to two 34/45 Mbit/s tributaries

NTFT52BANTFT52BKNTFT52BF

TN-1C 8x2 & 1x34/45M ADM (S-1.1 optics)TN-1C 8x2 & 1x34/45M ADM (L-1.1 optics)TN-1C 8x2 & 1x34/45M ADM (L-1.2 optics)These units are supplied in a plastic case and are upgradeable to provide two 34/45 Mbit/s tributaries

NTFT52BC NTFT52BMNTFT52BH

TN-1C 8x2 & 2x34/45 ADM (S-1.1 optics) TN-1C 8x2 & 2x34/45 ADM (L-1.1 optics)TN-1C 8x2 & 2x34/45 ADM (L-1.2 optics)These units are supplied in a plastic case

NTFT52BENTFT52BONTFT52BJ

TN-1C 16x2 ADM (S-1.1 optics)TN-1C 16x2 ADM (L-1.1 optics)TN-1C 16x2 ADM (L-1.2 optics)These units are supplied in a plastic case

NTFT52BBNTFT52BL NTFT52BG

Ordering codes 9-7


9

TN-1C 8x2 ADM (S-1.1 optics)TN-1C 8x2 ADM (L-1.1 optics)TN-1C 8x2 ADM (L-1.2 optics)These units are supplied in a metal case and are upgradeable to provide 16x2 Mbit/s tributaries or up to two 34/45 Mbit/s tributaries

NTFT52BDNTFT52BNNTFT52BI

TN-1C 8x2 & 1 x 34/45 ADM (S-1.1 optics)TN-1C 8x2 & 1 x 34/45 ADM (L-1.1 optics)TN-1C 8x2 & 1 x 34/45 ADM (L-1.2 optics)These units are supplied in a metal case and are upgradeable to provide 16x2 Mbit/s tributaries or two 34/45 Mbit/s tributaries

NTFT52BPNTFT52BQNTFT52BR

TN-1C 8x2 & 2 x 34/45 ADM (S-1.1 optics)TN-1C 8x2 & 2 x 34/45 ADM (L-1.1 optics)TN-1C 8x2 & 2 x 34/45 ADM (L-1.2 optics)

NTFT52BSNTFT52BTNTFT52BU

TN-1P

TN-1P Release 5 NTFT51BA

TN-1P (1+1) Release 5 NTFT51BB

TN-1P multiplexer PIU NTFT01AC

TN-1P multiplexer PIU (1+1) NTFT01AF

TN-1P Basestation (Release 5.0) NTFT51BC

TN-1P headend

TN-1P MPP NTFT01HC

TN-1P (1+1) MPP NTFT01HF

Table 9-19Obsolete codes (continued)



10-1

10

Appendix A: Synchronous digital hierarchy 10-Synchronous Digital Hierarchy

The Synchronous Digital Hierarchy (SDH), covered by ITU-T recommendations G.707, G.708, and G.709 (formally CCITT), details the international standards covering synchronous multiplexing and transmission.

• G.707 - Synchronous Digital Hierarchy Bit Rates

• G.708 - Network Node Interface for the Synchronous Digital Hierarchy

• G.709 - Synchronous Multiplexing Structure0

The standards propose a number of recommendations, including the transmission of Plesiochronous Digital Hierarchy (PDH) rates (except 8 Mbit/s). The tributary signals can be packaged into a standard sized container and located in an easily identifiable position within the multiplexed structure. The multiplexing structure includes provision for embedded network management channels.

The main advantages of the SDH are:

• Simplified multiplexing/demultiplexing techniques compared to PDH.

• Access to lower speed tributaries without the need to multiplex/demultiplex the entire high speed signal. This allows efficient drop and insert of channels and cross connect applications.

• Embedded network management channels which provide enhanced Operations, Administration, and Maintenance (OAM) capabilities, allowing efficiently controlled networks.

• Easy growth to higher multiplexing levels.

• Allows the transport of digital signals at the hierarchy bit rates specified in ITU-T recommendation G.702 (except 8 Mbit/s) and at broadband channel bit rates. This will allow SDH equipment to be introduced directly into existing networks and also allows the introduction of a wide range of services.

• The standard defines an optical interface which allows mid span fibre meets between equipment from different suppliers.

0

10-2 Appendix A: Synchronous digital hierarchy


SDH multiplexing structureThe first level of the SDH is at 155.52 Mbit/s and is known as a Synchronous Transport Module 1 (STM-1) signal. Higher rates are integer multiples of the first level bit rate and are denoted by the corresponding multiplication factor of the first level rate. At present, the following rates constitute the Synchronous Digital Hierarchy:

• STM-1: 155.52 Mbit/s

• STM-4: 622.08 Mbit/s

• STM-16: 2488.32 Mbit/s (2.5 Gbit/s)

• STM-64 9953.28 Mbit/s (10 Gbit/s)0

SDH allows for any of the current transmission rates (except 8 Mbit/s) to be mapped into containers, called Virtual Containers (VCs). The containers can be combined into standard formats in order to form the payload of the STM-1 signal. Different containers can be mixed, allowing for different rates to be carried simultaneously within the same structure.

The generalized multiplexing structure of the SDH is shown in Figure 10-1.

Figure 10-1SDH generalized multiplexing structure

The elements of the SDH are as follows:

Container (C-n), n=1 to 4This is the basic element of the STM signal consisting of a group of bytes allocated to carry the transmission rates defined in ITU-T recommendation G.702 (i.e. 1544 kbit/s and 2048 kbit/s transmission hierarchies).

Virtual Container (VC-n), n=1 to 4The lower order VC-ns (n=1 or 2) are built up of the basic container (C-n, n=1 or 2) plus additional capacity to carry Path Overhead (POH) information.

Note: VC-11 and VC-2 are not applicable to this equipment.

STM-N AUG AU-4 VC-4

AU-3 VC-3

TUG-3

TUG-2

TU-3 VC-3

C-3

TU-2 VC-2 C-2

TU-12 VC-12 C-12

TU-11 VC-11 C-11

C-4 140 Mbit/s

45 Mbit/s34 Mbit/s

6 Mbit/s

2 Mbit/s

1.5 Mbit/s

x1

x3

xN

x1

x1

x3

x3

x4

x7

x7

PointerProcessing

Multiplexing

Aligning

Mapping

Appendix A: Synchronous digital hierarchy 10-3


10

The higher order VC-ns (n=3 or 4) are built up of either a single basic container (C-n, n=3 or 4), or an assembly of Tributary Unit Groups (TUGs), together with the appropriate POH information.

The POH information includes VC path performance monitoring, signals for maintenance purposes, and alarm status indications. The POH information for the higher order VC-ns also includes multiplex structure indications which detail the VC composition.

Tributary Unit (TU-n), n=1 to 3This element consists of a VC plus a Tributary Unit pointer and provides adaptation between the lower order path layer and the higher order path layer. The pointer value indicates the phase alignment of the VC with respect to the TU POH added to it. The pointer location is fixed with respect to this higher level VC.

Tributary Unit Group (TUG-n), n=2 or 3This element is formed by a group of identical TUs or TUGs, allowing mixed capacity payloads to be constructed.

Administrative Unit (AU-n), n=3 or 4This element consists of a VC-n (n=3 or 4) plus an AU pointer and provides adaptation between the higher order paths and the multiplex section layer. The pointer value indicates the phase alignment of the VC-n with respect to the STM-1 frame. The location of the pointer is fixed within the STM-1 frame structure.

Administrative Unit Group (AUG)This element is formed by a group of byte interleaved AUs. The AUG has a fixed position in the STM payload.

Synchronous Transport Module Level 1 (STM-1)This is the basic element of the SDH and comprises a single AUG and the Section Overhead (SOH) information. The STM-1 frame structure comprises an array of 270 columns by 9 rows of 8-bit bytes as shown in Figure 10-2.

The frame length is 125µs. The order of transmission is from left to right, then from top to bottom. Within each byte, the most significant bit (bit 1) is transmitted first. The SOH information includes STM-1 framing, section performance monitoring, and other maintenance and operational information.



Figure 10-2STM-1 frame structure

Synchronous Transport Module Level N (STM-N)This element defines the Nth level of the SDH. An STM-N contains N AUGs together with SOH information. The N AUGs are one-byte interleaved and have a fixed phase relationship with respect to the STM-N.

TN-1C multiplexing structureThe TN-1C uses a subset of the SDH multiplexing structure as shown in Figure 10-3.

Figure 10-3TN-1C multiplexing structure

The procedure for assembling the STM-1 frame for the TN-1C and brief descriptions of the overhead bytes are given in the following sections.

TN-1P multiplexing structureThe TN-1P uses a subset of the SDH multiplexing structure as shown in Figure 10-4.

Figure 10-4TN-1P multiplexing structure

SOH

SOH

AU PTRs STM-1Payload

270 Columns (Bytes)

9 Rows

1 9 10 270

1

3

9

4

5

STM-N AUG AU-4 VC-4 TUG-3 TUG-2 TU-12 VC-12 C-12 2 Mbit/sx1xN x3 x7 x3

TU-3 VC-3 C-334 Mbit/s45 Mbit/s

x1

STM-N AUG AU-4 VC-4 TUG-3 TUG-2 TU-12 VC-12 C-12 2 Mbit/sx1xN x3 x7 x3



10

Mapping of a 2048 kbit/s signal into a VC-12The 2048 kbit/s tributary signal (C-12) is asynchronously mapped into a VC-12 signal (see Figure 10-5).

The additional fixed stuff bits and bytes maintain a defined size of 140 bytes for a 500µs TU multiframe (i.e. four STM-1 frames). Asynchronous mapping allows for justification of the tributary, allowing for variations between the tributary clock rates and the clock providing the timing for the synchronous network. The VC-12 signal contains a POH byte, which provides error checking, signal label, and path status information for the VC-12 path (see “VC-12 path overhead” on page 10-10).

Figure 10-52.048 Mbit/s tributary/VC-12/TU-12 mapping

V5

R

R

J2

R

Z6

R

Z7

R

32 Bytes

32 Bytes

32 Bytes

31 Bytes

C1 C2 O O O O R R

C1 C2 O O O O R R

C1 C2 O O O O R S1

S2 I I I I I I I

Asynchronous mappingfor 2048 kbit/s tributary

(Multiframe)

140

Byt

es

500

µ s

V1 (Ptr 1)

V2 (Ptr 2)

V3 (Ptr 3, Action)

V4 (Reserved)

V5

State ofH4 byte

XXXXXX00

XXXXXX01

XXXXXX10

XXXXXX11

144

Byt

es

Zero Ptroffset

I: Information BitC: Justification ControlR: Fixed StuffJ2: LO Path Trace

O: OverheadS: Justification OpportunityV5:VC1 Path OverheadZ6, Z7: Reserved

VC-12 TU-12



Mapping of a 34.368 Mbit/s signal into a VC-3 The 34368 kbit/s tributary signal (C-3) is asynchronously mapped into a VC-3 signal.

In addition to the VC-3 POH, the VC-3 consists of a payload of 9 x 84 bytes every 125µs. This payload is divided into three subframes, each subframe comprising information bits (I), two sets of justification control bits (C1, C2), two justification opportunity bits (S1, S2), and fixed stuff bits (R).

Figure 10-634.368 Mbit/s tributary/VC-3 mapping

Mapping of a 44.736 Mbit/s signal into a VC-3The 44.736 Mbit/s tributary signal (C3) is asynchronously mapped into a VC-3 signal.

This payload is divided into nine subframes. Each subframe comprises one byte of VC-3 POH, data bits, a set of justification control bits, one justification opportunity bit, and two overhead communication channel bits. The remaining bits are fixed stuff (R) bits. The O bits are reserved for future overhead communication purposes.

VC-3 POH

3 rows

3 rows

3 rows

841

3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x813x81 3x81 3x81 3x81 3x81 3x81CC

3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x813x81 3x81 3x81 3x81 3x81 3x81CC

3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x813x81 3x81 3x81 3x81 3x81 C 81A B

= RRRRRRRR

R Fixed stuff bitStuff control bitJustification opportunities bitInformation bit

C1,C2S1,S2I

RRRRRRC1C2 RRRRRRRS1 S2I I I I I I I

J1

B3C2

G1

F2

H4

Z3

K3

Z5

T1

T2

T3

125 µs



10

Figure 10-744.736 Mbit/s tributary/VC-3 mapping

Multiplexing of VC-12s into a TUG-2A pointer is added to the VC-12 signal to form a TU-12, the pointer indicates the phase alignment of the VC-12 with respect to the TU-12 (see Figure 10-8). If the timing of a VC causes it to slip with respect to the timing of the TUG, the pointer is adjusted to indicate the new alignment. Each TU-12 occupies four columns. shows a conceptual view of the mapping of three TU-12s into a TUG-2. In practice, the columns of each TU-12 are interleaved as shown in Figure 10-9.

Multiplexing of TUG-2s into a TUG-3The mapping of TUG-2s into a TUG-3 is a fixed mapping as shown in Figure 10-9. The inclusion of the TUG-3 is primarily to provide a structure for 34,368 kbit/s and 44,736 kbit/s transmission rates.

POH 8R 8R RRC

5 I 200 I 8 I 200 I 8 I 200 I

8R CCRRRRRR 8R CCRROORS

B3

J1

C2

G1

F2

H4

Z3

K3

Z5

R Fixed stuff bitC Justification bitS Justification opportunity bitI Information bitO Overhead bit

85



Figure 10-8Multplexing of TU-12 via a TUG-2

Figure 10-9TU-12/TUG-2/TUG-3 multiplexing

VCPtr

VCPtr

VCPtr

4 Columns

TU-129 Rows

TUG-212 Columns

1 2 3 4 5 6 7

1 2 3 45 6 7

1 2 3 4 5 6 7

1 2 3 4 5 6 7

1 2 3 4 5 6 7

1 2 3 4 5 6 7

CB

CBACBC

ABACBA

A

TU-12

TUG-2

TUG-3

(1) (2) (3) (7)

3Stuffing

12 4

56

78

9

1 2 3 4 5 6 7

858684



10

Multiplexing of a VC-3 into a TUG-3A pointer is added to the VC-3 signal to form a TU-3, the pointer indicates the phase alignment with respect to the TU-3 frame. The individual TU-3 pointers are contained within the H1, H2, and H3 bytes within the TUG-3, see Figure 10-10.

Figure 10-10Multiplexing of a TU-3 via a TUG-3

Mapping of TUG-3s into a VC-4The mapping of three TUG-3s into a VC-4 is fixed as shown in Figure 10-11. Column one of the VC-4 contains the nine POH bytes, which provide error checking, signal label, path status, and multiplexing structure information for the VC-4 path (see “Path overheads” on page 10-10). Columns two and three are fixed stuff.

Figure 10-11Multiplexing of three TUG-3s into a VC-4

Fix

ed s

tuff

TUG-3

VC-3

Container-3

J1

B3

C2

F2

H4

Z3

K3

Z5

VC-3 POH

G1

H1

H2

H3

86 columns

85 columns

A B CA B C

A B CA B C

TUG-3

VC-4

312 4

56

78

9

A B C

261

POH

1 1 186 86 86

TUG-3(A)

TUG-3(B)

TUG-3(C)



Mapping of a VC-4 into a STM-1 via an AU-4/AUGAn AU pointer is added to the VC-4 to form an AU-4, the pointer indicates the phase alignment of the VC-4 with respect to the STM-1 frame. The AU-4 pointers are in a fixed location in the STM-1 frame (see Figure 10-12). The AU-4 is placed directly in the AUG, which together with the SOH, forms the STM-1.

Figure 10-12Mapping of a VC-4 into an STM-1 via an AU-4/AUG

The Section Overhead (SOH) provides STM-1 framing, section performance monitoring and other maintenance functions pertaining to the section path (see “Section overhead” on page 10-11).

Path overheadsThe Path Overhead (POH) forms part of the relevant Virtual Container and provides information for use in the end-to-end management of a synchronous path.

VC-12 path overheadThe V5 byte in the VC-12 (see Figure 10-13) is the path overhead information pertaining to the VC-12 end-to-end path. The function of the V5 bits is shown in Figure 10-13 and is detailed in subsequent paragraphs:Figure 10-13VC-12 Path Overhead (V5 byte)

)

• BIP-2 (Bits 1 and 2). The Bit Interleaved Parity (BIP) bits are used to provide an error monitoring function for the VC-12 path.

1

2619

AU-4AUG

SOH

SOH

5

3

AU-4 PTR

VC-4

J1

B3

C2

F2

H4

Z3

K3

Z5VC-4 POH

G1

1 2 3 4 5 6 7 8

BIP-2 Signal Label

REI (FEBE) RFI RDI (FERF)



10

• REI (remote error indication) (Bit 3). The REI bit is used to communicate detected BIP-2 errors back to the VC-12 path originator. Also known as FEBE (far end block error)

• RFI (remote fail Indicator) (Bit 4). Not used in present applications.

• Signal label (Bits 5 to 7). These bits are used to indicate the payload mapping and equipped status.

• RDI (remote defect indication) (Bit 8). The RDI bit is used to indicate certain detected TU path alarms to the VC-12 path originator. Also known as FERF (far end receive failure).

VC-3/VC-4 path overheadThe VC-3/VC-4 path overhead consists of nine bytes as shown in Figure 10-14. The function of the nine bytes is as follows:

• Path trace (J1 byte). This byte is used to provide a fixed length string which is transmitted repetitively so that the receiving terminal can verify connection to the intended transmitter.

• Path BIP-8 (B3 byte). This byte provides an error monitoring function for the VC-3/VC-4 path.

• Signal label (C2 byte). This byte is used to indicate the composition of the VC-3/VC-4 payloads.

• Path status (G1 byte). This byte conveys path terminating status and performance information back to the VC-3/VC-4 path originator:

• Path user channel (F2 byte). This byte is for user communication purposes between path elements. Not used in present applications.

• Multiframe indicator (H4 byte). This byte provides a generalized multiframe indicator for payloads.

• APS (automatic protection switching) (K3 byte). This byte is for APS signalling for high order path protection. Not used in present applications.

• Spare (Z3 and Z5 bytes). Not used in present applications.

Section overheadThe Section Overhead (SOH) forms part of the STM-1 frame. The SOH is divided into two parts, the Multiplexer Section Overhead (MSOH) and the Regenerator Section Overhead (RSOH). The MSOH is only generated/terminated at each end of a multiplex section (i.e. where an STM is assembled/disassembled) and passes transparently through regenerators. The RSOH is assembled/terminated at each regenerator and at the end of a multiplex section. The section overhead bytes are detailed in Figure 10-14.



Figure 10-14Section overhead

The function of the RSOH bytes is as follows:

• Framing (A1 and A2 bytes). These bytes carry the frame alignment pattern.

• BIP-8 (B1 byte). This byte is used to provide an error monitoring function for a regenerator section. The byte is also used in the frame alignment process.

• Orderwire (E1 byte). This byte is used to provide an orderwire channel which can be accessed at regenerators and multiplexers. Not used in present applications.

• User channel (F1 byte). This byte is reserved for user purposes. Not used in present systems.

• DCCR (Data Communications Channel) (D1 to D3 bytes). The DCC bytes provide a 192 kbit/s regenerator data channel. These bytes can be used as a physical layer for the embedded communications channel (ECC).

• Regenerator Section Trace (J0 byte). Not used in present applications.0

The function of the MSOH bytes is as follows:

• BIP-24 (Byte B2). These bytes are used to provide an error monitoring function for the multiplex section.

• APS channel (K1, K2 bytes). The Automatic Protection Switching (APS) channel bytes are used for APS signalling. In present systems, the bytes are only used to communicate multiplex section AIS and RDI indications to the far multiplexer.

• DCCM (D4 to D12 bytes). The DCC bytes provide a 576 kbit/s multiplex data channel. These bytes can be used as a physical layer for the ECC.

• Orderwire (E2 byte). This byte is used to provide an orderwire channel which can be accessed only at multiplex section terminations. Not used in present applications.

D12D11D10

Z1S1 Z1 Z2 Z2 M1 E2

D7

D4

B2 B2 B2 K1

D5

D8 D9

D6

K2

H1 H1 H1 H2 H2 H2 H3 H3 H3

D3

F1

J0A2A2A2A1A1A1

B1

D1 D2

E1

A1, A2:B1, B2:J0:

D1 - D12:E1, E2:F1:H1, H2, H3:K1, K2:S1

Z1, Z2:M1:

FramingBit Error MonitoringRegenerator Section Trace - not currently usedData ChannelOrder WireUser ChannelAU-Pointer BytesAutomatic Protection SwitchingTiming Marker Byte - not currently usedSpareSection FEBE - not currently used

Bytes reserved for national use.All unmarked bytes are reserved for future international standardisation.

RSOH

AU-Pointer

MSOH



10

• Timing Marker Byte (S1 byte). Not used in present applications (set to 0Bh).

• Spare (Z1, Z2 bytes). Function not allocated. Not used in present applications.

• Section REI (FEBE) (M1 byte). Not used in present applications.

All other bytes in the RSOH and MSOH are either reserved for national use or for future international standardization and are not used in present systems.

end of chapter


11-1

11

Index 11-2 Mbit/s tributary interface 7-4

120 Ω 8-1375 Ω 8-13

34 Mbit/s tributary interface 7-4, 8-1445 Mbit/s tributary interface 7-5, 8-14

Aa.c. mains

parameters 7-9address

manual area 3-5network 3-5

ADM loop feederTN-1C 1-8

administrative unit (AU) 10-3administrative unit group (AUG) 10-3alarm handling 2-24alarms 3-1

external 3-2interface 7-8

handling 3-1masking 3-1monitoring 3-1power supply unit 4-2, 7-9QOSV 6-7rack 3-2

application memory 2-6application software 1-27, 3-6assessed seconds (AS) 6-2ATU 3-3

clear channel telemetry 1-13interface 7-8, 8-16TN-1C 1-9TN-1P 1-13

automatic laser shutdown 2-14

Bbackground block error (BBE) 6-1banks

flash memory 2-7, 3-6batteries

back-up 4-2replacement period 7-9

block diagramTN-1C network element 2-3TN-1P network element 2-4

broken fibresingle fibre working 2-19

browser 1-26built-in test 2-19

Cchannel numbering schemes 1-18clear channel telemetry 1-13clock 3-4

internal 2-6clock generator 2-6codes 9-1

ordering 9-1cold restart 2-6Command Line User Interface (CLUI) 1-26communication

serial links 2-7configuration data 3-6configuration table

memory 2-6configurations

TN-1CADM loop feeder 1-8ATU 1-9path protected 2-fibre ring 1-7point-to-point terminal 1-7

11-2 Index


TN-1PATU 1-13hub 1-12point-to-point terminal 1-10spur 1-11

connectionspath trace 1-24signal label 1-25traffic mode 1-23user labels 1-23

connectivity 1-18connector panel 8-3connectors 8-3construction 7-2

mechanical 1-15power supply unit 4-4

continuity tests 2-20craft access panel (CAP) 2-22craft access terminal

interface 7-7, 8-15serial communications 2-7

criteriapath protection switching 2-14

Ddata communications channel (DCC) 3-4dimensions

TN-1C 7-2TN-1P 7-2TN-1P Basestation 7-2TN-1PH 7-2

download 1-28

Eelectromagnetic compatibility 7-1electrostatic discharge 7-1embedded control channel (ECC) 1-26, 2-7enclosure types 1-15environmental conditions 7-1equipment codes 9-1errored second (ES) 6-1ETSI channel numbering scheme 1-18external alarms 3-2

interface 7-8, 8-19external interfaces 7-4, 8-1external synchronisation interface 7-7, 8-18

Ffan

interface 8-18TN-1C 1-28

flash memorybanks A and B 2-7, 3-6

foundation memory 2-6foundation software 1-27fuses 7-2, 8-24

power supply unit 7-9

Hhierarchy

synchronisation source 5-6holdoff period 2-13hub

TN-1P 1-12

Iinstallation

examples 1-16Integrated Network Manager (INM) 1-26interfaces 7-4

2 Mbit/s tributary 7-4, 8-1334 Mbit/s tributary 7-4, 8-1445 Mbit/s tributary 7-5, 8-14ATU 7-8, 8-16craft access terminal 7-7, 8-15external alarms 7-8, 8-19external synchronisation input 7-7, 8-18fan 8-18LAN 7-7, 8-22power 7-2, 8-21rack alarm adaptor 8-23rack alarm bus 8-24STM-1 optical 7-5, 8-15

internal clock 2-6inventory 3-5

KKLM channel numbering scheme 1-18

Index 11-3


11

LLAN

interface 2-24, 3-4, 7-7, 8-22laser

automatic shutdown 2-14local loopback

STM-1 2-15tributary 2-17

loopbacks 2-15ECC comms loss 2-18

Mmanagement 3-3manual area address 3-5mapping

2 Mbit/s to VC-12 10-534 Mbit/s to VC-3 10-645 Mbit/s to VC-3 10-6TUG-3 to VC-4 10-9

masking 3-1memory 2-6

banks 2-7, 3-6monitoring

alarms 3-1mounting

rack 1-17street cabinet 1-17TN-1P headend subrack 1-17wall 1-17

multiplexingTUG-2 into TUG-3 10-7VC-12 into TUG-2 10-7

multiplexing structure 10-4

Nnetwork address 3-5

Ooptical interfaces 8-15ordering codes 9-1oscillation guard time 2-13

Pparameters 7-1partner NE 1-27passthrough 6-9

pathoverheads 10-10protection switching 1-26, 2-13

criteria 2-14reversion 2-13

path protected 2-fibre ringTN-1C 1-7

path trace 1-24PDH ports

designations 1-20performance monitoring 6-1, 6-9

anomalies and defects 6-3counts 6-1

parity error 6-1disabling 6-3early termination 6-7logs 6-5

15 minute 6-524 hour 6-6

periods 6-4points (PMP) 6-2, 6-9QOSV alarms 6-7VC-4 passthrough 6-9warm restart 6-7zero suppression 6-1

point-to-point terminalTN-1C 1-7TN-1P 1-10

port designations 1-20power consumption

power supply unit 7-9TN-1C 7-3TN-1P 7-3TN-1P Basestation 7-3TN-1PH 7-3

power supplyinterface 8-21internal 2-5

power supply unit 4-1a.c. supply 7-9alarms 7-9connectors 4-3construction 4-4external 2-5output voltage 2-5parameters 7-9power consumption 7-9

power-up test 2-19protection switching

path 1-26, 2-13

11-4 Index


Qquality levels 5-7quality of service violation (QOSV)

alarms 6-7

Rrack alarm adaptor 1-27, 3-2, 9-6

interface 8-23rack alarm bus 8-24rack alarms 3-2rack mounting 1-17remote loopback

STM-1 2-16tributary 2-17

restartcold 2-6warm 2-6

reversionpath protection switching 2-13

RS-232CAT channel 2-7selector 2-24

SSDH multiplexing structure 10-2section overhead 10-11severely errored second (SES) 6-1signal label 1-25

VC-12 10-11VC-3 10-11

single fibre working 2-18software 1-27, 3-6

application 1-27, 3-6download 1-28foundation 1-27reversion 3-6upgrade 3-7

spurTN-1P 1-11

STM-1 aggregate channelsdesignations 1-20

STM-1 signalstructure 10-3

STM-1interface 2-7, 7-5

supply voltage 7-2a.c. (PSU) 7-9

synchronisation 5-1loss 5-1quality levels 5-7schemes 5-2

TN-1C 5-2TN-1P 5-3

settings 5-6single fibre working 2-19source hierarchy 5-6source switch 5-6sources 5-1

failure 5-13synchronisation status messaging 5-7

synchronous digital hierarchy (SDH) 10-1multiplexing structure 10-2

synchronous equipment management function (SEMF) 3-1

system clock 2-6system parameters 7-1

Ttelemetry (ATU)

clear channel 1-13test

continuity 2-20facilities 2-19power-up 2-19results 2-21

timeslot interchanger 2-7timing source

clock generator 2-6internal clock 2-6

TN-1C network elementblock diagram 2-3configurations 1-7construction 1-15dimensions 7-2general view 1-3multiplexing structure 10-4power consumption 7-3traffic processing 2-8weight 7-2

TN-1P Basestation network elementconstruction 1-15dimensions 7-2general view 1-6power consumption 7-3weight 7-2

Index 11-5


11

TN-1P network elementblock diagram 2-4configurations 1-10construction 1-15dimensions 7-2general view 1-4multiplexing structure 10-4power consumption 7-3traffic processing 2-11variants 1-31weight 7-2

TN-1PH network elementconstruction 1-15dimensions 7-2mounting 1-17power consumption 7-3weight 7-2

traffic 2-7processing

TN-1C network element 2-8TN-1P network element 2-11

user labels 1-23traffic mode 1-23tributary unit group (TUG) 10-3

Uunavailable second (UAS) 6-2unavailable time (UAT) 6-2user labels 1-23

Vvariants

TN-1P 1-31virtual container (VC) 10-2volatile memory 2-6voltage

a.c. 7-9d.c. 7-2

Wwall mounting 1-17warm restart 2-6weight

TN-1C 7-2TN-1P 7-2TN-1P Basestation 7-2TN-1PH 7-2

International Optical NetworksTechnical Documentation GroupNortel NetworksOakleigh Road SouthLondon, N11 1HB

So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are trademarks of Nortel Networks.

NORTEL NETWORKS


Copyright 1996 – 2001 Nortel Networks, All Rights Reserved.

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Document Number: 323-1081-100Product Release Number: 5.2Document Status: Standard (Revision 1) Date: October 2001Printed in England

tn-1c system description

Documents