System information

ManualsBrandsAastra ManualsComputer equipment675 XI

XMP1

XMP1 Release 5.5

System Description

FCD 901 48; Edition: R2A; 07.2009

Summary of content (374 pages)

PAGE 1
XMP1 XMP1 Release 5.5 System Description FCD 901 48; Edition: R2A; 07.
PAGE 2
A a str a N etw or k s G m b H D -7 15 2 2 B ac k n an g B lu m en s tra ss e 22 -2 4 D eu tsc h lan d h ttp ://w w w.A a str a.c om C op y rig ht 2 00 9 by A as tra N etw or k s G m b H Ä n de ru ng e n vo r be ha lten  G ed r uc k t in D e uts c hla nd A a st ra is t e in e ing e tr ag en es M a rk e nz eic h en de r A a str a Te c hn olo gie s L im ite d. A lle a nd er en e rw äh nte n W a re nz eic h en sin d E ig e ntum d er be treffe nd en B es itze r .
PAGE 3
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 4
XMP1 Release 5.5 System Description FCD 901 48 Issue R2A, 07.2009 Laser Warning If the XMP1 system is equipped with optical modules, always observe the safety regulations applicable when handling Laser Class 1 systems. In operation, the equipment units meet the conditions defined for LASER CLASS 1 systems. The laser is activated as soon as the optical modules are plugged in.
PAGE 5
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Table of Contents Table of Contents Chapter 1 Introduction to the XMP1 system 1-1 1.1 XMP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1.1 Performance features of the XMP1 Flexible Multiplexer . . . . . . . . . . . . . . . . . 1-3 1.1.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
XMP1 Release 5.5 System Description Table of Contents 2.4 2.5 2.6 2.7 2.8 FCD 901 48 Issue R2A, 07.2009 2.3.6 Clock configuration in the XMP1 network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.6.1 Central Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.6.2 Port modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.3.6.3 Preferring local clock sources . . . . . . . .
PAGE 7
FCD 901 48 Issue R2A, 07.2009 2.9 XMP1 Release 5.5 System Description Table of Contents Line Equipment for 2 Mbit/s Transmission Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79 2.9.1 Line equipment for fiber-optic cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79 2.10 Signal Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80 2.11 Performance Parameters of a Transmission Link . . . . . .
PAGE 8
XMP1 Release 5.5 System Description Table of Contents FCD 901 48 Issue R2A, 07.2009 3.8.2 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 3.8.2.1 Connection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 3.8.2.2 Interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26 3.8.2.3 Clock Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Table of Contents 5.4 Remote power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 5.5 Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11 5.6 Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 5.7 Alarms . .
PAGE 10
XMP1 Release 5.5 System Description Table of Contents FCD 901 48 Issue R2A, 07.2009 6.4.2 Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41 6.5 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42 6.6 Online Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-44 6.6.1 Node State . .
PAGE 11
FCD 901 48 Issue R2A, 07.2009 8.2 XMP1 Release 5.5 System Description Table of Contents Equipment with Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 8.2.1 Central Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 8.2.2 Redundancy modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 8.2.3 Ethernet adapter . . . . . . . . . . . . . .
PAGE 12
XMP1 Release 5.5 System Description Table of Contents 9.4 9.5 9.6 9.7 9.8 FCD 901 48 Issue R2A, 07.2009 9.3.4 Climatic conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Central Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 9.4.1 RS485 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 9.4.
PAGE 13
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Table of Contents 9.8.3 KZU SUB (8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19 9.8.4 KZU EX (8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20 DSK Modular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21 9.9.1 Mechanical dimensions . . . . . . .
PAGE 14
XMP1 Release 5.5 System Description Table of Contents FCD 901 48 Issue R2A, 07.2009 9.13.2.1Output voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33 9.13.2.2Remote supply ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33 9.13.2.3Supply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33 9.13.2.4Mechanical dimensions and weight . . . . . . . . . . . . . . . . . . . . . .
PAGE 15
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description List of Figures List of Figures Fig. 1.1 Interfaces of the XMP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Fig. 1.2 Logic view of the SOX multi-user system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18 Fig. 2.1 Block diagram of the XMP1 Flexible Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Fig. 2.2 Frame structure . . . . . . . . . . . . . . .
PAGE 16
XMP1 Release 5.5 System Description List of Figures FCD 901 48 Issue R2A, 07.2009 Fig. 2.26 Example of an 8-subscriber conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49 Fig. 2.27 Example of an 8-subscriber and 2 x 4-subscriber conference . . . . . . . . . . . . . . 2-50 Fig. 2.28 Cascading the analog conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64 Fig. 2.29 Analog conference in modem mode (without signalling) . . . . . . . . . . . .
PAGE 17
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description List of Figures Fig. 5.2 Power spectral density - SDSL 2048 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Fig. 5.3 Remote powering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 Fig. 5.4 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12 Fig. 6.1 SOX single-user system, one area . . . . .
PAGE 18
XMP1 Release 5.5 System Description List of Figures Page xviii Proprietary Information FCD 901 48 Issue R2A, 07.
PAGE 19
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description List of Tables List of Tables Tbl. 0.A Abreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-xxiii Tbl. 2.A Frame alignment signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Tbl. 2.B Service digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Tbl. 2.
PAGE 20
XMP1 Release 5.5 System Description List of Tables FCD 901 48 Issue R2A, 07.2009 Tbl. 3.G TTF-4 application functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34 Tbl. 3.H MSPTF-1 application functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35 Tbl. 3.I MSPTF-4 application functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 Tbl. 3.J HPX, LPX application functions . . . . . . .
PAGE 21
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description List of Tables Tbl. 9.A General characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Tbl. 9.B System parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Tbl. 9.C Climatic and EMC conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Tbl. 9.D Central Unit . . . . . . . . . . . . . .
PAGE 22
XMP1 Release 5.5 System Description List of Tables Page xxii Proprietary Information FCD 901 48 Issue R2A, 07.
PAGE 23
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Abbreviations Abbreviations Table 0.A: Abreviations ABBREVIATION MEANING AP Access Point, Management Access for SOX B B Alarm D D-Bit, Urgent Alarm M Mailing A A-Alarm B B-Blarm BER Bit Error Ratio B-No. Trunk Group No.
PAGE 24
XMP1 Release 5.5 System Description Abbreviations FCD 901 48 Issue R2A, 07.2009 Table 0.
PAGE 25
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Abbreviations Table 0.A: Abreviations ABBREVIATION MEANING PeC Persistance Check PLL Phase Locked Loop Px Port x, x = no. Q Acknowledgement QuP Source Port RAM Random Access Memory REP Repeater RF Radio Frequency RKW Frame Alignment Signal S Card Protection Switching SD System Bus Si and SiII Signalling Bits for Multiframe Sections SOX ServiceOn XMP1, Element Manager STRV Power Supply SUB Subscriber Subscr.
PAGE 26
XMP1 Release 5.5 System Description Abbreviations FCD 901 48 Issue R2A, 07.2009 Table 0.
PAGE 27
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Introduction to the XMP1 system Chapter 1 Introduction to the XMP1 system This document describes the basic functioning of the XMP1 cross-connect system including its network management options. 1.1 XMP1 The XMP1 system is an integrated flexible platform providing all customary interfaces and functions of a transmission system.
PAGE 28
XMP1 Release 5.5 System Description XMP1 FCD 901 48 Issue R2A, 07.
PAGE 29
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Performance features of the XMP1 Flexible Multiplexer 1.1.
PAGE 30
XMP1 Release 5.5 System Description Performance features of the XMP1 Flexible Multiplexer • • • • • • • • • • FCD 901 48 Issue R2A, 07.2009 Frame-synchronous processing of 2 Mbit/s signals; co-channel radio and ripple control signals can thus be transmitted all over the network.
PAGE 31
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Performance features of the XMP1 Flexible Multiplexer For more detailed information please refer to the Description and Operating Instruction XMP1-SL (05PHA00363AAU).
PAGE 32
XMP1 Release 5.5 System Description Interfaces FCD 901 48 Issue R2A, 07.2009 1.1.2 Interfaces The XMP1 system offers the user a great variety of interfaces for voice, ISDN, data and LAN services. The interfaces available are briefly described in the following sections. 1.1.2.
PAGE 33
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Service Units Subscriber interfaces for data (DSK) DSK modular - with modules Modular data interface (basic unit) for equipment with up to four modules. DSKmod basic unit for a mixed equipment with the following modules: • V.24 module • V.11 module • V.35 module • WT module DSKmod basic unit for a mixed equipment with the following modules: • • G703 module with codirectional interface G703 module with contradirectional interface V.
PAGE 34
XMP1 Release 5.5 System Description Line Units FCD 901 48 Issue R2A, 07.2009 Data interfaces (bit rate <= 1984 kbit/s) Port Nx64 2-port data interface to V.11 or V.35 • Data rate adjustable from 64 kbit/s to 1984 kbit/s in steps of 64 kbit/s Port LAN 2-port data interface to IEE 802.3 • • WAN data rate adjustable from 64 kbit/s to 1984 kbit/s in steps of 64 kbit/s 10Base2 and 10BaseT interfaces ISDN interfaces All ISDN modules are equipped with four interfaces.
PAGE 35
FCD 901 48 Issue R2A, 07.2009 • XMP1 Release 5.5 System Description Interfaces for SDH and Ethernet expansion Two electrical 6 dB equipment interfaces, 120 , bal. / 75 , coaxial Module 1F • Can be equipped with one or two optical single-fiber interface modules, 1310/ 1550 nm WDM, 25 dB field attenuation (62.7026.580.00-A001/A002) Module 2F • Can be equipped with one or two optical 2-fiber interface modules, 1310 nm with 25 dB field attenuation (62.7026.570.
PAGE 36
XMP1 Release 5.5 System Description SDSL Line Equipment FCD 901 48 Issue R2A, 07.2009 EoSCU module (Ethernet over SDH Core Unit) The two SDH interfaces and four Ethernet interfaces can be equipped with optical and electrical SFPs. STM-1 interfaces • • Up to two STM-1 interfaces per EoSCU, 1310 nm and 1550 nm (S1.1, L1.1 and L1.2) Up to. 2 x STM-1 interfaces per EoSCU, electrical STM-4 interfaces • Up to 2 x STM-4 interfaces per EoSCU, 1310 nm and 1550 nm (S4.1, L4.1 and L4.
PAGE 37
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock interface T3 and T4 SHDSL Repeater • • • • • • 1 pair Repeater acc. to ITU-T G.991.2 Connecting two 2 SDSL links Remote powering with RPS-XMP1 module Local powering Inverse operation possible, e. g. LT/NT interchange SW download via Z bit 1.1.2.5 Clock interface T3 and T4 The Central Unit and SCU-E provide the clock interfaces T3 and T4 for applying the 2048 kHz reference frequency and connecting a reference frequency distributor.
PAGE 38
XMP1 Release 5.5 System Description Central Unit interfaces FCD 901 48 Issue R2A, 07.2009 1.1.2.9 Central Unit interfaces V.24 interface (F interface) • • • Local connection of "ServiceOn XMP1" SOX NMS Local connection of the SOX LCT Connection of the Local Service PDA. RS485 interface (QD2-SSt.) • Connection of ServiceOn Access Ethernet interface (optional) Ethernet interface to connect the Central Unit to a LAN.
PAGE 39
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Local Craft Terminal SOX-LCT SDH expansion EoSDH expansion 6 x E1 4xEth Cl STM-1/4 EoSCU Eth.
PAGE 40
XMP1 Release 5.5 System Description Network Management System FCD 901 48 Issue R2A, 07.2009 1.2 Network Management System The XMP1 system can be configured, controlled and monitored by two network management systems: • ServiceOn XMP1 (SOX) • ServiceOn Access (SOA) Each NMS provides a local terminal for operation and maintenance. 1.2.
PAGE 41
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX Single-User application Basically, the system is divided up as follows: • Single-user application - Central management structure • Multi-user application - Distributed management structure Independent of the respective application, the management channel (DCN) is automatically routed, i.e.
PAGE 42
XMP1 Release 5.5 System Description SOX Single-User application FCD 901 48 Issue R2A, 07.2009 A special variant of the single-user application is the division of a network into several sub-networks (Areas) while maintaining the single-user concept. Access to an area is possible via V.24 and/or Ethernet interfaces. Access via the Ethernet is recommended. For this purpose, an Ethernet interface must be provided on the Central Unit (> V3.0) of the corresponding access nodes.
PAGE 43
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX Multi-User application 1.2.1.2 SOX Multi-User application The SOX multi-user version permits several users to access the database and XMP1 network simultaneously. Supported scenarios: • One user executes the configuration, while others use SOX as alarm monitoring station. • One user with a low authorization level monitors the alarms. If required, another user with a higher authorization level intervenes.
PAGE 44
XMP1 Release 5.5 System Description SOX Multi-User application FCD 901 48 Issue R2A, 07.2009 Windows Session (User A) Windows Session (User B) SOX Client SOX Client Windows Session (User C) SOX Client SOX Client TCP TCP TCP TCP TCP TCP DB Server SOX Server Service Level Service Level Figure 1.2: Logic view of the SOX multi-user system Communication between the SOX Clients and SOX Server requires a quick and reliable TCP connection.
PAGE 45
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 46
XMP1 Release 5.5 System Description ServiceOn Access Network Management System FCD 901 48 Issue R2A, 07.2009 1.2.2 ServiceOn Access Network Management System Optionally, it is possible to connect the ServiceOn Access System via the QD2 interface. Thus, XMP1 can be integrated into the management of large-scale heterogeneous networks. All necessary control and monitoring functions are implemented. With XMP1 version 5.0 and higher, the SOX-MSP must be used for local configuration.
PAGE 47
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Functioning Chapter 2 Functioning The XMP1 Flexible Multiplexer digitizes and multiplexes both voice and data information from subscribers. The data are transmitted to the XMP1 network and can be read, demultiplexed and sent again to the subscribers in each XMP1 node. 2.1 General Functions Transmit direction In the transmit direction, the voice information to be transmitted is digitized.
PAGE 48
XMP1 Release 5.5 System Description General Functions FCD 901 48 Issue R2A, 07.2009 demultiplexer synchronizes itself to the frame alignment signal and applies the 64 kbit/s signals to the system data bus. Controlled by the central control module on the Central Unit, the channel modules now extract their 64 kbit/s signals from the system data bus. The COFIs on the channel modules convert the digital signals again into analog signals and transmit them to the subscribers.
PAGE 49
Aastra Proprietary Information KZU KZU C O F I KZU O F I C System adapt. f2 f1 90 f 8,192 MHz f/4 Clock int. 32,768 MHz 2MHz clock trigger Central control module and memory Signalling line Control line System data bus Figure 2.1: Block diagram of the XMP1 Flexible Multiplexer 48 V/ 60 V Power supply Power supply bus F2in 2nd converter F2out F2in 1st converter F2out V.24 Ethernet KZU PO1 Clock recov. PC F1in F1out F1in F1out Operator Terminal Power supply bus PORT max.
PAGE 50
XMP1 Release 5.5 System Description Frame Structure and Synchronization FCD 901 48 Issue R2A, 07.2009 2.2 Frame Structure and Synchronization 2.2.1 Frame structure In the time-division multiplex procedure, the analog signals to be transmitted are first sampled, quantized and encoded. These analog signals are telephone signals (limited from 300 Hz to 3400 Hz) which are sampled at a rate of fA = 8000 Hz, i.e. the amplitude of the analog signal is sampled once every 125s.
PAGE 51
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Frame structure Pulse frame 256 bit / 125s 256 bit / 125s 8 bit / 3.9s 29 30 1 2 3 4 15 30 31 0 1 2 3 4 1617 29 30 15 16 1718 X 0 0 1 1 0 1 1 1 2 15 31 16 17 30 31 0 1 2 15 16 17 18 x 1 D N Y Y Y Y a b c d a b c d Frame alignment signal Signalling information Service digits Signalling information Channel no.
PAGE 52
XMP1 Release 5.5 System Description Frame structure FCD 901 48 Issue R2A, 07.2009 Service digits The service digits are transmitted in the frames which do not include the frame alignment signal. Table 2.B: Service digits Bit position 1 2 3 4 5 6 7 8 Binary value X 1 D N Y Y Y Y Bit X in position 1 is used for transmitting the CRC4 multiframe alignment signal. If the CRC4 procedure is not applied, bit X is set to logic 1.
PAGE 53
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Frame structure Frames 1 to 15 Frames 1 to 15 transmit the signalling information of the 30 individual channels (4 bits per channel). In these frames, the frame alignment signals for traffic channels 1 to 15 are transmitted in positions 1 to 4, those for traffic channels 16 to 30 in positions 5 to 8. Table 2.
PAGE 54
XMP1 Release 5.5 System Description CRC4 procedure FCD 901 48 Issue R2A, 07.2009 2.2.2 CRC4 procedure The CRC4 procedure (CRC= cyclic redundancy check) is used • to avoid malsynchronization due to pretended synchronization patterns (pretended frame alignment signals) • and to detect even low bit error ratios (BER = 10-6). The so-called CRC4 signature consists of four bits referred to as C1, C2, C3 and C4. These four bits are determined using the CRC4 algorithm.
PAGE 55
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description CRC4 procedure CRC4 frame structure The multiframe for the cyclic redundancy check (CRC) is composed of 16 frames. This multiframe is divided into section I and section II, each being composed of 8 frames. Thus, one multiframe section includes 2048 bits. It forms one block for the redundancy check. Figure 3-4 below gives a detailed overview of the CRC4 multiframe.
PAGE 56
XMP1 Release 5.5 System Description Synchronization FCD 901 48 Issue R2A, 07.2009 Transmission and evaluation of the CRC4 signature The calculated CRC4 signature is stored before it is sent to the receive side via the next multiframe section. The CRC4 signature bits C1 to C4 are transmitted in bit positions 1 of the frame alignment signals of the frames 0, 2, 4, 6 and 8, 10, 12, 14 respectively.
PAGE 57
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Synchronization Loss of sync When the frame alignment signal has been received incorrectly three times in a row, the frame alignment process is reinitiated. The evaluation can also involve bit 2 of the service digits, i.e. if this bit has been received as logic "0" three consecutive times, the frame is considered to be out of sync.
PAGE 58
XMP1 Release 5.5 System Description Synchronization FCD 901 48 Issue R2A, 07.2009 2 Mbit/s signal at F1in Bit synchronization Code conversion HDB3/binary Frame alignment CRC4 multiframe alignment Phase adaptation to the Tx frame Multiframe alignment Bus line Tx multiframe phase adaptation Tx frame CRC4 procedure Code conversion binary/HDB3 2 Mbit/s signal at F1out Figure 2.
PAGE 59
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock Supply 2.3 Clock Supply The PCM network represents a synchronous network. In such a network, a network node can supply the network clock. If this network clock source fails, another network node must take over network synchronization. However, it is also possible that individual or all network nodes recover their clock from T3in or use an Rx clock.
PAGE 60
XMP1 Release 5.5 System Description Assignment of clock priorities FCD 901 48 Issue R2A, 07.2009 The ports of clock interfaces T3in and T3out (T4) are implemented on a 9-pin D-Sub connector (male) of the Central Unit or - with the SDH expansion - on the the SCU module. Receive clocks at ports The 2 Mbit/s signals available at F1 inputs of the ports are used to recover the receive clock. For this purpose, the ports transmit their F1in sum signal via the TE clock line to the Central Unit.
PAGE 61
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock priority control 2.3.3 Clock priority control To control clock priorities, the number of the highest clock priority of the PCM network is sent out. The clock priority is transmitted in bit Y5 of the service digits. Each network node continuously polls the Y5 bits of the frame alignment signal of its ports and verifies as to whether it receives at one of its ports a clock priority higher than its own highest clock priority.
PAGE 62
XMP1 Release 5.5 System Description Clock priority control ISDN FCD 901 48 Issue R2A, 07.
PAGE 63
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock switchover 2.3.4 Clock switchover The internal clock of a node run at a reference clock such as the T3in clock or the Rx clock of a port is digitally detuned to the frequency of this reference clock. In doing this, a resolution of 1/8 Hz is achieved. If the reference clock fails, the node switches over to the detuned internal node clock.
PAGE 64
XMP1 Release 5.5 System Description Clock control for co-channel radio operation FCD 901 48 Issue R2A, 07.2009 2.3.5 Clock control for co-channel radio operation For transmitting co-channel radio signals or ripple control signals, a constant delay time is required for the corresponding channels. For this purpose, the delays in the elastic memories of the ports must be kept constant.
PAGE 65
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock configuration in the XMP1 network 2.3.6 Clock configuration in the XMP1 network Settings regarding the configuration of clock control in the XMP1 network are performed via the clock priority list and central or decentral card slot data of the modules. Clock control settings via the central or decentral card slot data are executed for the Central Units and port modules. 2.3.6.
PAGE 66
XMP1 Release 5.5 System Description Wander filter FCD 901 48 Issue R2A, 07.2009 In order to use such clock sources for clock recovery in the local node, the latter can be configured via the central card slot data (info no. 2) in such a way that the local clock sources (T3in or ports with configured clock priority) of this node are preferred. With this configuration, the node then uses the configured local clocks according to their clock priority.
PAGE 67
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Delay time reduction in linear networks 2.3.6.6 Delay time reduction in linear networks In linear networks, the delay time of the port can be reduced by about 60 µs compared with the statistical average value. This setting is made in the decentral card slot data of the ports using info no. 14 "Short delay time in a linear network". However, this function is also possible on line sections in meshed networks or star networks.
PAGE 68
XMP1 Release 5.5 System Description Configuring a clock tree with preferred priority FCD 901 48 Issue R2A, 07.2009 2.3.6.7 Configuring a clock tree with preferred priority Preferred port for priority 1 To switch off the automatic clock tree assignment function, it is possible to define a preferred port in XMP1 nodes. In order to ensure that a fixed path is observed for setting up the clock tree in a fully operational network, any port can be selected and configured as preferred port for priority 1.
PAGE 69
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuring a clock tree with preferred priority Note: If clock priority 1 was still passed on by node 3, it could arrive at port P1 in node 3 via node 2. This would lead to a clock loop and clock recovery in node 3 would continuously switch over between port P1 and P3. However, node 2 now receives clock priority 2 at ports P2 and P3.
PAGE 70
XMP1 Release 5.5 System Description Suppressing the clock priority (at F1in) FCD 901 48 Issue R2A, 07.2009 2.3.6.8 Suppressing the clock priority (at F1in) Using info no. 10 it is possible to suppress the evaluation of the clock priority at F1in of the port interface. Info no. 10 = 0: The clock priority is evaluated at F1in of the port interface (default setting). Info no. 10 = 1: The clock priority is not evaluated at F1in of the port interface.
PAGE 71
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Suppressing the clock priority (at F1in) Example 2: In the following example, transmission between XMP1 nodes 1 and 2 takes place via two SDH multiplexers. In these multiplexers, a retiming process is performed for the 2 Mbit/s signal. Thus, XMP1 node 2 receives a clock different from the one supplied by XMP1 node 1. This also applies to XMP1 node 1.
PAGE 72
XMP1 Release 5.5 System Description Regionalization of clock synchronization FCD 901 48 Issue R2A, 07.2009 2.3.6.9 Regionalization of clock synchronization In order to enable a preferred clock connection of nodes to nearby clock sources, a list of clock priority nos. can be defined for each node. In this case, the node uses the clock priorities contained in the list for clock control, irrespective of the highest clock priority identified by the node. Central card slot info no.
PAGE 73
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Regionalization of clock synchronization List 1 specifies that clock priorities 10 and 5 are to be preferred as local clock priorities by nodes 1 to 10 (sub-network 1). "Sub-network 1" List 1, 10, 5 List 2, 4, 12, 11, 8 Node 2 Node 3 Node 1 Prio 10 T3in Node.4 Node 9 Node.10 Node 6 Node 7 Node 5 Node 8 Prio 5 T3in Figure 2.
PAGE 74
XMP1 Release 5.5 System Description Regionalization of clock synchronization "Sub-network 1" "Sub-network 2" List 1, 4, 12 List 2, 10, 5, 3, 9, 1, 6 List 1, 10, 5 List 2, 4, 12, 11, 8 Node .2 Node 4 Node. 9 "Sub-network 3" List 1, 3, 9 List 2, 4, 12, 2, 7 Node 25 Prio 9 T3in Prio 4 T3in Node 3 Node 1 Prio 10 T3in FCD 901 48 Issue R2A, 07.2009 Node 11 Node.10 Node 6 Node.5 Node 7 Node 8 Prio 5 T3in Node 20 Prio 3 T3in Node.
PAGE 75
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description 2 Mbit/s Connections 2.4 2 Mbit/s Connections The structure of a PCM network is defined by the nodes and the 2 Mbit/s connections between the individual nodes. Each node available in the network is assigned a hardware number. This hardware number permits the node to be addressed within the network. The 2 Mbit/s connections are switched between two ports. 2 Mbit/s link 1st port Node no.: Card slot: Port no.: 1 15 3 Node no.
PAGE 76
XMP1 Release 5.5 System Description Setting options for the 2 Mbit/s connection FCD 901 48 Issue R2A, 07.2009 — The ECC8 is transmitted in the Sa7 and Sa8 bits of the system channel. The utilization of the ECC8 channel and signal for controlling the clock priority can be set independently of each other. System channel transmission can be re-routed from time slot TS0 to time slot TS30. Basically, the user can define as to whether the system channel shall be used or not.
PAGE 77
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Setting options for the 2 Mbit/s connection The following table shows the assignment of service digits to functions: Tab. 2.J: Service digits PAYLOAD IS SIGNAL FOR ECC8 IS TRANSMITTED IN SYSTEM CONTROLLING TRANSMITTED SERVICE BITS SA5...SA8 OF CLOCK CHANNEL IN SYSTEM DIGITS THE OUTGOING PRIORITY IS IS USED CHANNEL SERVICE DIGITS TRANSMITTED NOTE M_0 yes yes yes no M_1 yes yes yes yes * M_2 yes no yes no 3.
PAGE 78
XMP1 Release 5.5 System Description Circuit Connections FCD 901 48 Issue R2A, 07.2009 2.5 Circuit Connections The 64 kbit/s channel links must be defined within a node. The following operating modes are possible: • • • • • Standard Polling Ring polling Multi-polling Channel protection switching In the following description, the terms "converter address" and "port address" are used. These terms can be briefly described as follows: The converter address is defined by the card slot no.
PAGE 79
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Standard operation 2.5.1 Standard operation In this operating mode, the 64 kbit/s channel and signalling information contained in time slot 16 of a port interface are assigned to a converter. The diagram depicted below shows an example of standard operation. Port: Card slot no.: 15 Port no. : 3 Channel no.: 2 Converter: Card slot no. :14 Converter no.
PAGE 80
XMP1 Release 5.5 System Description Standard operation FCD 901 48 Issue R2A, 07.2009 Routing ISDN channels in the standard operating mode 64 kbit/s channels for ISDN interfaces are routed in the standard operating mode. On the ISDN module, the distribution of the 64 kbit/s channels to the eight converters is implemented by 16 variants which can be adjusted via the central card slot data of the ISDN module.
PAGE 81
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Polling 2.5.2 Polling The polling mode permits data transmission between a master station (polling master) and several sub-stations. Each sub-station monitors the data transmitted by the polling master (listening). In consequence of a "request to send" received from the polling master, each sub-station can communicate with the latter. Connections between sub-stations are not possible. Node 1 Node 2 P Converter Subscr.
PAGE 82
XMP1 Release 5.5 System Description Polling FCD 901 48 Issue R2A, 07.2009 4. The master station sends out the subscriber ID. 5. The calling sub-station detects this ID and answers (off-hook). The called sub-station sends an outgoing a-bit. 6. The master station receives the a-bit from the called sub-station and sends the outgoing b-bit. 7. All sub-stations receive the b-bit. 8. There is a connection between the called sub-station and the master station. For all other sub-stations, the link is occupied.
PAGE 83
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Ring polling 2.5.3 Ring polling The ring polling mode permits data transmission between subscribers connected to form a ring. In the ring polling mode, all subscribers are equal in priority, i.e. there is no master station. Data transmission takes place in a ring into both directions. Thus, transmission is ensured even if one direction is cut.
PAGE 84
XMP1 Release 5.5 System Description Ring polling FCD 901 48 Issue R2A, 07.2009 Setting up a ring polling connection 1. Subscriber 1 wishes to set up a connection to subscriber 2. 2. All converters are in standard operation (converter - port). 3. Subscriber 1 goes off-hook and transmits bit a in both directions of the ring. 4. Subscriber x and subscriber 2 receive bit a and set up a port-to-port connection. 5. The identification of the subscriber to be called is sent out in the ring. 6.
PAGE 85
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Multipolling 2.5.4 Multipolling In multipolling operation, which represents a special polling option, several converters located on one module can be involved in the polling function. The master station can request the sub-stations involved in multipolling to send their data. Only one sub-station can transmit data to the master station at a time.
PAGE 86
XMP1 Release 5.5 System Description Multipolling FCD 901 48 Issue R2A, 07.2009 Setting up a connection between the multipolling master and a subscriber 1. If the polling master wishes to communicate with a sub-station, it transmits a "request to send" in the 64 kbit/s data stream of the multipolling section. 2. All subscribers monitor these data. 3. The subscriber addressed by the multipolling master identifies the request to send and sets up a connection to the latter. 4.
PAGE 87
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Single-channel protection switching 2.5.5 Single-channel protection switching Single-channel protection switching is a special ring polling function. This function permits a protection path to be switched for a converter. Two channels that can be routed in the network via different paths must each be switched in the starting and end node to a converter.
PAGE 88
XMP1 Release 5.5 System Description Conference Circuits FCD 901 48 Issue R2A, 07.2009 2.6 Conference Circuits 2.6.1 Digital conference for data channels The channel modules permit a “digital conference” to be switched. In such a digital conference, several sub-stations (DTE) can be connected to one main station. This main station can then exchange data with the sub-stations (DTE). The identification of the desired DTE takes place via the protocols exchanged between the main station and the DTE.
PAGE 89
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Digital conference for data channels The following diagram shows an example of a digital conference. to further nodes Main station DSK Port Port Port Port Port Port Port Port Port Port DSK DSK DSK DSK DTE DTE DTE DTE Figure 2.24: Digital conference Configuring a digital conference See Figure 4-26. The DTE of sub-station 1 in node 2 must be connected to interface 5 of the DSK module.
PAGE 90
XMP1 Release 5.5 System Description Digital conference for data channels FCD 901 48 Issue R2A, 07.2009 Node 2 Node Knoten1 1 Port 2 Port 2 Port 1 Channel 6 Channel 6 to node 4 Channel 9 Conv. 1 2 3 4 5 6 7 8 Conv. 1 2 3 4 5 6 7 8 S DSK V.24 DSK V.24 IF 1 23 4 56 78 IF 1 23 4 56 78 IF 5 Main station Sub-station 1 DTE Figure 2.
PAGE 91
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Expanded Digital Conference 2.6.2 Expanded Digital Conference Using the "Expanded Digital Conference", several subscribers of an XMP1 network can be interconnected to form a conference. The subscriber signals are transmitted in a 64 kbit/s channel via the 2 Mbit/s links of the XMP1 network. The interfaces/converters of a module involved in an EDC are all equal in priority.
PAGE 92
XMP1 Release 5.5 System Description 8-subscriber/2 x 4-subscriber conference FCD 901 48 Issue R2A, 07.2009 8-subscriber conference In case of the 8-subscriber conference, all 8 sub-addresses available on a module can be used for one EDC. The connected subscribers are all involved in one conference. Node 1 Port Card slot 5 1 2 3 4 5 6 7 8 Converter Interface 1 2 3 4 5 6 7 8 8-subscr.
PAGE 93
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Use of sub-addresses 2.6.2.2 Use of sub-addresses If not all sub-addresses of a module are used for the EDC, please note the following: • If neither the converter nor interface side of a sub-address is involved in the conference, the corresponding channel can be used for normal operation. • If only the converter side or interface side of a sub-address is involved in the conference, the side not involved cannot be used.
PAGE 94
XMP1 Release 5.5 System Description Conference channel routing FCD 901 48 Issue R2A, 07.2009 If only one subscriber is connected in both end nodes of the main line, a simple conference with 1 converter/1 interface can be configured or the subscriber can be connected in the STANDARD operating mode (converter <-> port).
PAGE 95
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Examples 2.6.2.4 Examples The following EDC examples show a pure 8-subscriber conference and a mixed 8-subscriber and 2 x 4-subscriber conference. Example of an 8-subscriber conference All subscribers in this example participate in conference A. The subscribers of conference A are connected via a module configured for an 8-subscriber conference by means of the central card slot data.
PAGE 96
XMP1 Release 5.5 System Description Examples FCD 901 48 Issue R2A, 07.2009 Alternatively to this solution, a conference can also be configured in node 2. Here only the converters and no interfaces of the module will be involved in the conference. In this case, converters 1 and 2 are also connected to the corresponding ports for main line routing. Channel 14 (subscr. A-4) is applied to a free converter.
PAGE 97
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Examples For main line B, converters 1 and 2 of the modules are connected to the corresponding ports (64 kbit/s channel). In node 1, subscriber A-1 is connected to a module configured for a 2 x 4-subscriber conference. Node 1 is used as Central Station for conference A. In nodes 3 and 6, the subscribers A-3 and A-6 of conference A are connected. Here the module is configured for an 8-subscriber conference.
PAGE 98
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 2.6.2.5 Configuration The following section describes the setting options offered by the central and decentral card slot data of the modules for an "Expanded Digital Conference".
PAGE 99
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration Info no. 21: Exp. Dig. Conf. active Using this info no., the "Expanded Digital Conference" mode can be adjusted for the module. Note: In this case of application, info nos. 26 to 32 must not be used and have to be set to "0". Expanded Digital Conference active: Info no. 21 set to "1". Info no. 22: Exp. Dig. conf. div.: 8=0 2*4(1-4/5-8)=1 Using info no.
PAGE 100
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 In order to permit "ripping up" meshes, a tree must still be set up starting from a root. However, this tree is independent of traffic signal transmission. Info no. 23 set to "1". Info no. 24: Exp. Dig. conf: Root depends on C/RTS yes=1 For special cases of application, it is possible to configure several roots, i.e. Masters.
PAGE 101
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration Common conference circuit The schematic drawing depicted below shows a conference circuit with all subscribers participating in the same conference. Subscribers 1 to 6 in nodes 1, 2, 3 and 4 all participate in a common conference. Main line The main line of the conference is routed in channel 11 from node 1 via node 2, port 1, and node 2, port 3, to node 3.
PAGE 102
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 Subscriber 6 of node 4 is routed in channel 14, which is connected in node 2 from port 2 to converter 3. 8-subscriber conference 1 2 3 4 5 6 7 8 Interface Converter 1 2 3 4 Conf. subscr. 6 5 6 7 8 Card slot 6 Port 2-Mbit Node 4 Channel 14 2-Mbit 2-Mbit Channel 11 Channel 11 P1 Port P2 Card slot 5 1 2 3 4 5 6 7 P3 1 2 3 4 5 6 Conf. subscr.
PAGE 103
FCD 901 48 Issue R2A, 07.2009 • • XMP1 Release 5.5 System Description Configuration Info no. 28: Set to "1"; interface takes part in conference Info no. 29: without any meaning Node 2 for card slot 6 Central card slot data • Setting identical with that for node 1. Decentral card slot data SUB-ADDRESS 1: • • • Info no. 27: Set to "1"; converter takes part in conference Info no. 28: Set to "1"; interface takes part in conference Info no. 29: without any meaning SUB-ADDRESS 2: • • • Info no.
PAGE 104
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 Two separate conference circuits In the example depicted below, two separate conferences, i.e. conference A and conference B, are configured in the network. Conference A Subscribers A-1 to A-6 participate in conference A. Subscriber A-6 is connected to conference A in node 2 via port 2. Main line The main line of conference A is routed in channel 11 from node 1, port 1, via node 2, port 1 and port 3, to node 3, port 1.
PAGE 105
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 106
XMP1 Release 5.5 System Description Configuration • FCD 901 48 Issue R2A, 07.2009 Info no. 29: without any meaning SUB-ADDRESS 2 for conference A: • • • Info no. 27: Set to "0"; converter does not take part in conference Info no. 28: Set to "1"; interface takes part in conference Info no. 29: without any meaning SUB-ADDRESS 5 for conference B: • • • Info no. 27: Set to "1"; converter takes part in conference Info no. 28: Set to "1"; interface takes part in conference Info no.
PAGE 107
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration SUB-ADDRESS 5 for conference B: • • • Info no. 27: Set to "1"; converter takes part in conference Info no. 28: Set to "1"; interface takes part in conference Info no. 29: without any meaning SUB-ADDRESS 6 for conference B: • • • Info no. 27: Set to "1"; converter takes part in conference Info no. 28: Set to "1"; interface takes part in conference Info no.
PAGE 108
XMP1 Release 5.5 System Description Analog Conference FCD 901 48 Issue R2A, 07.2009 2.6.3 Analog Conference The "Analog Conference" option is supported by XMP1 version 3.8 and higher. It is implemented by a software package. This software runs on the processor of the KZU FEK (8) module (62.7040.250.00-A001, AN00113903). In the XMP1 node, this KZU FEK (8) module is mounted in any card slot of the XMP1 subrack.
PAGE 109
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Analog Conference CNF Analog conference on KZU FEK (8) module Conference channels 3 4 1 2 SUB SUB SUB SUB Sub.1 Sub. 2 Sub. 3 Sub. 4 Cascading Cascading the "CNF Analog Conference" module is possible. Thus, more than four conference subscribers can be interconnected to a conference. These modules can be mounted either in one or in several nodes.
PAGE 110
XMP1 Release 5.5 System Description Analog conference with signalling FCD 901 48 Issue R2A, 07.2009 The following diagram shows an example of such a cascade. CNF A Node 1 Node 2 CNF B CNF Analog Conference on KZU FEK (8) module CNF Analog Conference on KZU FEK (8) module Conference channels 3 4 1 2 Conference channels 3 4 1 2 Conference channels 3 4 1 2 [3] [1] [1] [1] [1] [2] [1] [3] SUB SUB SUB SUB 2 Mbit/s SUB Sub. 4 Sub. 5 Sub. 1 Sub. 2 Sub.
PAGE 111
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Analog conference with signalling channels, its sends an outgoing active a-bit=0 to all other subscribers connected to the conference. Then the conference is in the calling state. If a second active a-bit is now detected (one of the subscribers went off-hook; a-bit=0), the outgoing a-bits of the conference channels are switched passive by an incoming passive a-bit (traffic state).
PAGE 112
XMP1 Release 5.5 System Description Analog conference without signalling (modem mode) FCD 901 48 Issue R2A, 07.2009 2.6.3.2 Analog conference without signalling (modem mode) With XMP1 version 3.8.5 and higher, the "Analog conference" can be configured in such a way that a control function using the a-bit is no longer necessary. On all CNF modules involved in the "Analog conference", the central card slot data bit 1 "Modem mode (without signalling)" must be set to 1.
PAGE 113
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Analog conference without signalling (modem mode) Configuration The configuration of the analog conference is executed in the same way as a normal module configuration. 1. Define the run of the analog conference (nodes, card slots, ports, channels etc.). 2. Mount the KZU FEK (8) module(s) you want to use for the analog conference.
PAGE 114
XMP1 Release 5.5 System Description Branching function FCD 901 48 Issue R2A, 07.2009 2.6.4 Branching function In contrast to the conference configurations possible so far, a higher security can now be achieved by switching a conference in an arbitrarily meshed topology. Relevant in this case is the topology set up using 64 kbit/s channels switched between the ports of the corresponding conference nodes. To "rip up" meshes, a tree with an unambiguous root is set up automatically.
PAGE 115
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Branching function Defining the root (Master) For both applications, an externally connected subscriber unit can be defined as Master. This configuration is possible by setting the decentral card slot info. no. 29 to "Root possible at IF" for the DSK module and info no. 29 to "Root for (analog) conference" for the CNF module (FEK). All other external conference subscribers will then be used as Slaves.
PAGE 116
XMP1 Release 5.5 System Description Configuration example: one master, no preferred path FCD 901 48 Issue R2A, 07.2009 2.6.4.1 Configuration example: one master, no preferred path The following Fig. 2.30 shows a digital conference with one Master in Master/Slave operation. A preferred path is not configured. Master of the conference is conference subscriber 1. The Master is connected in node 1 to interface 1 of card slot 5. The Slaves are located in node 2, 3 and 4.
PAGE 117
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration example: one master, no preferred path Tab. 2.M: Configuration table, Digital conference - Master/Slave mode Node Card Subslot addr. 1 1 5 2 Central card slot info no. 21 22 23 24 1 0 0 0 Decentral card slot ino no.
PAGE 118
XMP1 Release 5.5 System Description Configuration example: one master, with preferred path FCD 901 48 Issue R2A, 07.2009 2.6.4.2 Configuration example: one master, with preferred path The following Fig. 2.30 shows a digital conference with one Master in Master/Slave operation. A preferred path is defined. Master of the conference is conference subscriber 1. The Master is connected in node 1 to interface 1 of card slot 5. The Slaves are located in node 2, 3 and 4.
PAGE 119
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration example: one master, with preferred path Configuration steps to be executed for this example: Tab. 2.P: Configuration table, Digital conference - Master/Slave mode Node Card Subslot addr.
PAGE 120
XMP1 Release 5.5 System Description Configuration example: multiple master defined FCD 901 48 Issue R2A, 07.2009 2.6.4.3 Configuration example: multiple master defined The following Fig. 2.30 shows a digital conference in Master/Slave operation with two possible Master. Conference subscriber 1 and 4 are possible master. Please not that only one Master may be active, the other Master operates as a slave. The Master must declare itself as Master by activating a control line.
PAGE 121
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration example: multiple master defined Tab. 2.Q: Configuration table, Digital conference - Master/Slave mode Node Card Subslot addr. Central card slot info no. 21 14 27 28 29 0 1 1 1 2 0 1 0 0 1 1 1 1 0 0 1 0 0 0 1 0 0 1 1 1 0 0 1 0 0 1 1 1 0 0 1 0 0 0 1 0 0 1 1 2 5 6 2 1 1 22 0 0 23 0 0 24 0 0 3 1 3 4 2 1 0 0 0 1 4 6 2 3 Aastra Decentral card slot ino no.
PAGE 122
XMP1 Release 5.5 System Description Protection Switching Configurations FCD 901 48 Issue R2A, 07.2009 2.7 Protection Switching Configurations In order to ensure optimum reliability and availability of XMP1 even in case of faults occurring in the network, the system offers the possibility of defining protection switching configurations. The following protection switching configurations are possible: • • Line protection switching Card protection switching 2.7.
PAGE 123
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description 2 Mbit/s card protection switching 2.7.2 2 Mbit/s card protection switching In a card protection switching configuration, two port modules are used for protection switching. In this case, an interface (priority) located on one port is protected by a standby interface located on a second port. For both ports, the same subaddress has to be used for both the preferred interface and standby interface.
PAGE 124
XMP1 Release 5.5 System Description Central Unit Redundancy FCD 901 48 Issue R2A, 07.2009 2.8 Central Unit Redundancy In order to protect the node from failure due to a defective Central Unit, the XMP1 system offers the possibility to double the Central Unit. With Central Unit redundancy, only one Central Unit is active at a time. In case of a fault, the system switches over to the passive Central Unit automatically and an alarm is generated.
PAGE 125
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Line Equipment for 2 Mbit/s Transmission Links 2.9 Line Equipment for 2 Mbit/s Transmission Links 2.9.1 Line equipment for fiber-optic cables If the 2 Mbit/s signals are to be routed via fiber-optic cables, Port LE2 OPT U modules must be provided. The Port LE2 OPT U module offers two electrical equipment interfaces and two optical card slots which can be flexibly equipped with 1F and 2F modules.
PAGE 126
XMP1 Release 5.5 System Description Signal Concentrator FCD 901 48 Issue R2A, 07.2009 2.10 Signal Concentrator In the XMP1 system, the signal concentrator module (62.7040.180.00-A001, AN00275454) provides interfaces (sensors and transmitters) to external units. This new module is generally referred to as "SIG II signal concentrator". It substitutes the signal concentrator module (62.7006.180.00-A001). Using the sensors, messages received from external devices can be processed.
PAGE 127
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Performance Parameters of a Transmission Link 2.11 Performance Parameters of a Transmission Link The performance criteria for the transmission of digital signals for different services and transmission links are defined by ITU-T Rec. G.821. 2 Mbit ports can be defined at which the performance parameters shall be determined on the basis of ITU-T Rec. 821. The SOX Network Manager requests and displays the parameters measured.
PAGE 128
XMP1 Release 5.5 System Description Performance Parameters of a Transmission Link FCD 901 48 Issue R2A, 07.2009 • degraded operation • severely degraded operation.
PAGE 129
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Switching Test Loops 2.12 Switching Test Loops For troubleshooting purposes, the operator can switch test loops on the modules listed below (A = analog loop D = digital loop). Table 2.R: Test loops KZU, KZU II, DSK DSK EX SUB FEK EX KZU II OSX SUB FEK KZU Loop no. 64k V24 X21 DSK modular WT V35 MDV MDG 1 Loop Internal 3c A A A A A A A loop ITU (F1) V.54 Loop 3c ITU V.54 Loop 3c ITU V.54 Loop 3c ITU V.54 Loop 3 ITU V.
PAGE 130
XMP1 Release 5.5 System Description Switching Test Loops FCD 901 48 Issue R2A, 07.2009 Table 2.T: Test loops SHDSL Loop no. SHDSL 1 LT SDSL loop NS direction 10 NT SDSL loop NS direction 11 NT E1 loop 12 Local E1 loop For a detailed loop description, please refer to the relevant module description.
PAGE 131
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDH Expansion in the XMP1 System Chapter 3 SDH Expansion in the XMP1 System 3.
PAGE 132
XMP1 Release 5.5 System Description Applications FCD 901 48 Issue R2A, 07.2009 The following drawing shows the general application as Terminal and Add/Drop Multiplexer. Add/Drop Mux STM-1/4 STM-1/4 XMP1 + SDH XMP1 + SDH Add/Drop-Mux 2 Mbit/s 64 kbit/s SDH PDH XMP1 + SDH Terminal Mux PDH XMP1 + SDH STM-1/4 STM-1/4 Add/Drop Mux PDH SDH PDH Figure 3.
PAGE 133
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Design of the SDH Expansion 3.2 Design of the SDH Expansion The SDH expansion is implemented in the XMP1 system by means of the following modules: • • SCU (SDH Core Unit) CU-E (Central Unit Expansion) The SDH expansion of the XMP1 system is implemented on the SCU module. This module occupies two card slots in the XMP1 subrack. The CU-E sub-module is used as control module. It is mounted on the Central Unit (62.7040.xxx.xx) of the node.
PAGE 134
XMP1 Release 5.5 System Description Design of the SDH Expansion FCD 901 48 Issue R2A, 07.2009 The SCU-B board includes the SCP ASIC (SDH Core Processor ASIC), the 2 Mbit/s Tributary ASIC (P12LPU), the interface to the XMP1 PDH system as well as a processor (PUC) for controlling the module. Furthermore, it provides a line interface as well as external and internal 2 Mbit/s interfaces. A second SCU-E board provides an additional line interface as well as internal and external 2 Mbit/s interfaces.
PAGE 135
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDH Functions 3.3 SDH Functions The SDH functions provided by the SDH expansion of the XMP1 system are made available by the SCP (SDH Core Processor). This SCP offers the line and cross-connect functions of an SDH multiplexer.
PAGE 136
XMP1 Release 5.5 System Description Interfaces FCD 901 48 Issue R2A, 07.2009 Optical STM-1/4 interfaces The optical interfaces are made available by the SIFU (SDH Interface Unit) via SFP modules. Up to two such SIFUs can be mounted on one SCU module. A mixed equipment with both STM-1 and STM-4 modules and with optical and electrical modules is possible. Connection is implemented using LC-type plug connectors. The following SIFU modules are available for Release 5.1: Tab. 3.
PAGE 137
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Interfaces Electrical STM-1 interfaces The following SIFU modules will be provided: • • STM-1 EL STM-1 Patch 2 m 05HAM00107AAE with SFP electrical 05HAM00108ACR with patch cable 2 m Tab. 3.B: Electrical STM-1 interfaces STM-1 EL 05HAM00107AAE with SFP electrical STM-1 Patch 2 m 05HAM00108ACR with patch cable 2 m Connections are implemented using coaxial 1.0/2.3-type plug connectors.
PAGE 138
XMP1 Release 5.5 System Description Functioning FCD 901 48 Issue R2A, 07.2009 3.5 Functioning 3.5.1 Switching interfaces SDH The SDH expansion provides the following interfaces for switching purposes: • • • • 2 STM-1 interfaces with 63 x 2 Mbit/s 2 STM-4 interfaces with 4 x 63 x 2 Mbit/s 10 external 2 Mbit/s interfaces 8 internal 2 Mbit/s interfaces to the PDH kernel PDH The PDH kernel provides the XMP1 interfaces already known. 3.5.1.
PAGE 139
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Multiplex structure 3.5.1.2 Multiplex structure Mapping The SDH expansion uses a subset of the multiplex structure as defined in ITU-T G.707. The diagram below shows the multiplex structure used in the SDH expansion. STM-1 AUG-1 AU-4 x1 x1 VC-4 x3 TUG-3 x7 Pointer processing TUG-2 Multiplexing x3 Aligning Mapping TU-12 VC-12 C-12 Figure 3.3: Multiplex structure of SDH expansion 3.5.
PAGE 140
XMP1 Release 5.5 System Description Traffic architecture FCD 901 48 Issue R2A, 07.2009 Connections between the SDH section and PDH kernel The SDH expansion provides the STM-1/4 interfaces and 10 x 2 Mbit/s interfaces for the connection of external 2 Mbit/s signals. In the PDH kernel direction, there are eight 2 Mbit/s interfaces for switching purposes. The 64kbit/s switching matrix is used to apply the data of the PDH kernel to the internal 2 Mbit/s interfaces (E12 internal) of the SDH expansion.
PAGE 141
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock Supply 3.6 Clock Supply For their internal switching process, the network elements included in an SDH network require a highly precise and stable clock (2048 kHz) which must be recovered from a reference timing source (Primary Reference Clock PRC). The SDH expansion in the XMP1 system provides a SETS functionality according to EN 300 417-6-1 (Synchronization Layer).
PAGE 142
XMP1 Release 5.5 System Description Synchronous Equipment Timing Source SETS FCD 901 48 Issue R2A, 07.2009 3.6.1 Synchronous Equipment Timing Source SETS In the Synchronous Digital Hierarchy, the clock generator is referred to as SETS (Synchronous Equipment Timing Source). In the XMP1 system, the SETS of the SDH expansion is located on the SCU module. It provides the following features and functions: • • • • • Clock generation and clock recovery according to G.813.
PAGE 143
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SCU redundancy The SSM value of outgoing STM-N signals can be set to 1111 (“Don´t use for sync”) manually. Otherwise these signals will be assigned the SSM value of the current clock quality of the internal T0 clock. In case of plesiochronous signals, a SSM value is not transmitted. However, for incoming plesiochronous signals configured as T2 reference timing source , the operator can enter a SSM value and thus define the quality manually.
PAGE 144
XMP1 Release 5.5 System Description Clock supplied to the XMP1 PDH kernel FCD 901 48 Issue R2A, 07.2009 Core Unit A Ext. Y-cable T3 SETG function T2 System clock T0 T4 Ext. Y-cable T1 9.72 MHz External clock T3 Inter-core sync Squelch control Core Unit B T3 T1 SETG function T2 External clock T4 T4 System clock T0 Figure 3.6: Clock with SCU redundancy 3.6.
PAGE 145
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clocks T3 and T4 NMS view T1 T2 T3 64k T2 64k T3 SETG function T4 T0 PET function 64k T4 64k T0 Setting: Use SDH clock If you want the clock network of the PDH network to remain independent, do not select the "Use SDH clock" setting. The PDH clock selection will then be independent of the SDH system clock T0. In this case, the current status of PDH clock selection will not be visible in the SOA.
PAGE 146
XMP1 Release 5.5 System Description Functioning of the SETS FCD 901 48 Issue R2A, 07.2009 3.6.6 Functioning of the SETS Reference timing sources The following diagram explains the functioning of the SETS in the SDH expansion. No clock TS(8) T3 TS(7) T2 TS(6) T1 TS(5) T1 TS(4) T1 TS(3) T1 TS(2) TS(1) SELECT A Autom.
PAGE 147
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Functioning of the SETS The SETG (Synchronous Equipment Timing Generator) receives the clock from SELECT B and uses it to generate clock T0 required by the network element itself and made available to the modules. SELECT A passes on the clock to the adjustable "Autom. squelch" switch. The latter decides whether the clock quality is sufficient and whether the clock will be switched through to selector switch SELECT C.
PAGE 148
XMP1 Release 5.5 System Description Protection FCD 901 48 Issue R2A, 07.2009 3.7 Protection The reliability and maintenance of transmisssion networks are important aspects to be taken into consideration when using multiplexers. In this conjunction, redundancy configurations are playing a decisive role. The redundancy of both transmission channels and certain multiplexer modules is reasonable.
PAGE 149
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SNCP Sub-Network Connection Protection SNCP can be configured for the following VC levels: • • • VC-4, VC-3, VC-12.
PAGE 150
XMP1 Release 5.5 System Description MSP Linear Multiplex Section Protection FCD 901 48 Issue R2A, 07.2009 3.7.1.2 MSP Linear Multiplex Section Protection With Multiplex Section Protection (MSP), the entire multiplex section between two multiplexers will be protected. Transmission takes place both via the operating path and protection path. In case of a failure of the operating path, switchover to the protection path takes place automatically in the far end.
PAGE 151
FCD 901 48 Issue R2A, 07.2009 • XMP1 Release 5.5 System Description MSP Linear Multiplex Section Protection A request received from the far end is executed either using the protocol in compliance with ITU-T G.841 or a proprietary K1/K2 protocol. These requests are valid only in the bi-directional mode.
PAGE 152
XMP1 Release 5.5 System Description MSP Linear Multiplex Section Protection FCD 901 48 Issue R2A, 07.2009 MSP with one SDH module SCU If an XMP1 node includes only one SCU module, MSP 1+1 can be configured as follows: Example 1: see Fig. 3.9 - STM-N West: Working channel - STM-N East: Protection channel Example 2: - STM-N West: - STM-N East: Protection channel Working channel Protection channel Working channel XMP1 node 1 STM-N West XMP1 node 2 STM-N West STM-N East SCU STM-N East SCU Figure 3.
PAGE 153
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description MSP Linear Multiplex Section Protection Working channel XMP1 node 1 XMP1 node 2 STM-N West STM-N West STM-N OST SCU-A STM-N East SCU-A Protection channel STM-N West STM-N West STM-N East SCU-B STM-N East SCU-B Figure 3.
PAGE 154
XMP1 Release 5.5 System Description 2 Mbit/s protection FCD 901 48 Issue R2A, 07.2009 3.7.1.3 2 Mbit/s protection Internal 2 Mbit/s ports For internal 2 Mbit/s ports, the 2 Mbit/s protection options supported by the PDH kernel can be configured.
PAGE 155
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Module protection 3.7.2 Module protection 3.7.2.1 SDH Core Unit Protection The SDH Core Unit Protection is a SCU protection implemented at the equipment level. This protection covers the functions of the switching matrix and the synchronization functions of the SDH Core Unit. Since the SDH Core Unit also supports the connection of external 2 Mbit/s signals, these signals will also be protected by a SDH Core Unit Protection configuration.
PAGE 156
XMP1 Release 5.5 System Description Management Functions FCD 901 48 Issue R2A, 07.2009 3.8 Management Functions 3.8.1 Fault Management The Fault Management in the SDH expansion is executed in compliance with ITU-T G.784. BW7R alarm signalling scheme The BW7R alarm signalling scheme is processed on the Central Unit. The required alarm information from the SDH expansion is routed via the CU-E sub-module to the Central Unit and processed by the latter. SDH alarms See Section 6.8.
PAGE 157
FCD 901 48 Issue R2A, 07.2009 • XMP1 Release 5.
PAGE 158
XMP1 Release 5.5 System Description Equipment Management FCD 901 48 Issue R2A, 07.2009 This non-volatile memory is composed of two banks, i.e. an active and a passive bank. The application software is downloaded to the passive bank via the XMP1 Central Unit. During the SCU startup process, the application software is loaded to the RAM of the SCU processor.
PAGE 159
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Remote inventory data (RID) • SFP module The following drawing shows the physical and logic view of the modules and sub-modules with their RID data.
PAGE 160
XMP1 Release 5.5 System Description Network Management FCD 901 48 Issue R2A, 07.2009 3.9 Network Management The existing PDH functionality and additional SDH expansion are described in a common information model. The PDH and SDH functionality are treated as network element. The information model is based on the existing function units for SDH and PDH. With release 5.
PAGE 161
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Function groups of the SDH expansion Table 3.D: Function groups of the SDH/Ethernet expansion FUNCTION GROUPS MEANING FG NO.
PAGE 162
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.2009 HOA Higher Order Assembler The HOA function scheme represents the multiplex structure. For each level (VC-4, VC-3, VC-2 and VC-12), the TP index is numbered serially starting from 1.
PAGE 163
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Function groups of the SDH expansion TTF-1 TP index=1 SPI OPTICAL Regenerator Termination Multiplex Termination AU4CTP HPX Flexible connectivity (bidirectional) TTF-1 application functions The following table gives an overview of the TTF-1 application functions. Table 3.F: TTF-1 application functions Aastra APPLICATION FUNCTIONS SPONT. EVENT REQU./RESP.
PAGE 164
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.
PAGE 165
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 166
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.2009 Table 3.H: MSPTF-1 application functions APPLICATION FUNCTIONS Page 3-36 SPONT. EVENT REQU./RESP.
PAGE 167
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 168
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.2009 Table 3.I: MSPTF-4 application functions APPLICATION FUNCTIONS SPONT. EVENT REQU./RESP.
PAGE 169
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 170
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.2009 HPX, LPX HPX VC4, LPX VC3 and LPX VC12 are switching matrices for different transmission rates. In principle, their behaviour is identical and a distinction is possible only by their function group numbers. The following table shows the application functions of these switching matrices. HPX, LPX application functions Table 3.J: HPX, LPX application functions APPLICATION FUNCTIONS SPONT. EVENT REQU.
PAGE 171
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Function groups of the SDH expansion SET2 application functions Table 3.K: SET2 application functions APPLICATION FUNCTIONS SPONT. EVENT REQU./RESP. COMMAND Alarm information X X - Alarm disabling and priority X X X Configuration X X X Operating status X X X Reference list - X - LOI2M Lower Order Interface 2 Mbit/s The function group LOI 2M offers a plesiochronous, electrical 2 Mbit/s interface (PPI ELECTRICAL).
PAGE 172
XMP1 Release 5.5 System Description Function groups of the SDH expansion FCD 901 48 Issue R2A, 07.2009 LOI 2M application functions Table 3.L: LOI 2M application functions Page 3-42 APPLICATION FUNCTIONS SPONT. EVENT REQU./RESP.
PAGE 173
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Function groups of the SDH expansion TTF-1 TTF-1 SPB-1 HPX VC4 TTF-1 TTF-4 LPX VC3 HOA MSPTF-4 MSPTF-1/4 TTF-1 RTF(E)-1/4 MSPTF-1 ETH nxVCx TTF-1 Eth-Port TTF-1 LOI 2M LPX VC12 IPMB 64/2 STU Span (Full) TDM (EPP2) TTF-1 EPPM 64/2 LOM 2 OPPM 64/2 DSK 64 IPMB 64/2 MODUL KZU BPX 64 xDSL-Extern ISDN EPG DATA SISA0 DATA nx64 E(O)PP 2 IPMB 64/2 PSW SET2 NEControl E(O)PP 2 Figure 3.
PAGE 174
XMP1 Release 5.5 System Description Management Connection FCD 901 48 Issue R2A, 07.2009 3.10 Management Connection 3.10.1 Overhead information The Section Overhead SOH forms an STM-N frame together with the payload. This frame includes all information required for frame synchronization, service purposes, performance monitoring and other functions. The SOH is composed of a block of 9 lines with N x 9 columns each (N = 1, 4, 16). The Path Overhead POH and container C4 are forming the virtual container VC4.
PAGE 175
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Management connection of the SDH expansion The SOX is connected via the LAN interface of the CU-E.
PAGE 176
XMP1 Release 5.5 System Description DCN migration FCD 901 48 Issue R2A, 07.2009 XMP1 network elements without SDH expansion, which are connected using 2 Mbit/s links, are managed via the XMP1-ECC. 3.10.3 DCN migration The following drawings show the migration in different network and management scenarios if the SDH expansion is added to these networks. The following scenario shows a pure XMP1 network without SDH expansion managed by means of SOX. This network is connected to SOX via IP or RS232.
PAGE 177
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description DCN migration The following scenario shows a pure XMP1 network with SDH expansion managed by means of SOX. This network is connected to SOX via IP. F F SMF SMF XMP1-SC 2/34M XMP1 XMP1 XMP1 XMP1 IP-DCC SDH SDH STM-1 SMF SMF F F Q IP-LAN Routing IP XMP1-SC SOX Figure 3.14: Managing an XMP1 network with SDH expansion by means of The following scenario shows an XMP1 network and an SDH network managed by means of SOX and SOA.
PAGE 178
XMP1 Release 5.5 System Description DCN migration FCD 901 48 Issue R2A, 07.2009 The following scenario shows an XMP1 network with SDH expansion and an SDH network managed by means of SOX and SOA.
PAGE 179
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Ethernet over SDH in the XMP1 System Chapter 4 Ethernet over SDH in the XMP1 System 4.1 Introduction The four Fast Ethernet ports available on the Ethernet over SDH Core Unit (EoSCU) module of the XMP1 system are provided for 'Transparent LAN Services' (TLS). They permit a point-to-point transmission of Ethernet signals between two units equipped with Ethernet interfaces via the SDH network.
PAGE 180
XMP1 Release 5.5 System Description Design of the EoSDH Expansion FCD 901 48 Issue R2A, 07.2009 4.2 Design of the EoSDH Expansion The Ethernet expansion is implemented in the XMP1 system by means of the following modules: • EoSCU (Ethernet over SDH Core Unit) • CU-E (Central Unit Expansion) The Ethernet expansion of the XMP1 system is implemented by the EoSCU module. This module occupies two card slots in the XMP1 subrack. The CU-E sub-module is used as control module.
PAGE 181
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Design of the EoSDH Expansion SCU-BETH The SCU-BETH board provides four Ethernet interfaces, one line interface as well as internal 2 Mbit/s interfaces. The four Ethernet interfaces can be equipped with electrical and optical SFPs. The following SFP types are available for this purpose: • • • 100Base TX electrical 100Base FX (optical fiber) STM-1 S1.
PAGE 182
XMP1 Release 5.5 System Description Ethernet Functions FCD 901 48 Issue R2A, 07.2009 4.
PAGE 183
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Ethernet Functions Auto-Negotiation The Auto-Negotiation function enables the Ethernet port and Ethernet unit connected to the latter to select the Ethernet connection parameters automatically based on the features of the equipment units connected. These parameters include - for example - the transmission rates possible as well as full-duplex or half-duplex operation.
PAGE 184
XMP1 Release 5.5 System Description Interfaces FCD 901 48 Issue R2A, 07.2009 4.
PAGE 185
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Interfaces The following SFPs are available: Table 4.B: SFPs for optical STM-1/4 interfaces STM-1 SFP STM-1 S1.1 SH 1300 1400729-0027 SFP STM-1 L1.1 LH 1300 1400744-0051 SFP STM-1 L1.2 LH 1550 1400744-0044 STM-4 SFP STM-4 S4.1 SH 1300 1400744-0010 SFP STM-4 L4.1 LH 1300 1400744-0028 SFP STM-4 L4.2 LH 1550 1400744-0036 Application class syntax (acc. to ITU-T G.
PAGE 186
XMP1 Release 5.5 System Description Interfaces FCD 901 48 Issue R2A, 07.2009 Connections are implemented using coaxial 1.0/2.3-type plug connectors. E1 interfaces The following interfaces are available for 2 Mbit/s signals: • • 8 x 2 Mbit/s to the XMP1 PDH kernel via the system bus 6 x 2 Mbit/s, 6 dB equipment interfaces (In-house) for the external connection of electrical 2 Mbit/s signals acc. to ITU-T G.703 (unstructured and structured acc. to ITU-T G.704).
PAGE 187
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Multiplex Structure 4.5 Multiplex Structure The following drawing shows the most important function blocks relevant for Ethernet-over-SDH transport. Ethernet PHY IF 1 Ethernet MAC Ethernet Encaps. Virtual Concat.
PAGE 188
XMP1 Release 5.5 System Description Traffic architecture • • • • • • FCD 901 48 Issue R2A, 07.2009 VCG configuration Adding VC to VCG Deleting VC from VCG Minimum number of VCs in VCG Actual, configured, maximum number of VCs Wait to restore time 4.5.1 Traffic architecture The Ethernet expansion is primarily based on the functions of the SDH Core Processor (SCP). The latter provides the functions required for data processing and switching.
PAGE 189
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Traffic architecture Connections between the SDH section and PDH kernel The Ethernet expansion provides four Ethernet interfaces, the STM-1/4 interfaces and a total of 6 x 2 Mbit/s interfaces for connecting external 2 Mbit/s signals. In the PDH kernel direction, eight 2 Mbit/s interfaces are available for switching purposes.
PAGE 190
XMP1 Release 5.5 System Description SDH Mapping/Concatenation FCD 901 48 Issue R2A, 07.2009 4.6 SDH Mapping/Concatenation • • • • • Ethernet data, consisting of consecutive frames of any valid size, can be mapped into either VC-12 or VC-3 of the STM-1 signal with the following conditions: — Mapping Ethernet data to nx VC-12 (n=1 to 63) for all Ethernet ports of the module. Maximal 63 VC-12 (STM-1 capacity) are supported.
PAGE 191
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDSL in XMP1 Chapter 5 SDSL in XMP1 5.1 General SDSL (international designation: SHDSL) is a further development of the HDSL technology introduced some years ago. The SDSL TC-PAM16 line code standardized by both ETSI and ITU permits nearly the same transmission range on one copper pair as HDSL on two pairs. With two pairs and high-quality cables, SDSL can span longer distances than HDSL.
PAGE 192
XMP1 Release 5.5 System Description SDSL extension in XMP1 FCD 901 48 Issue R2A, 07.2009 5.
PAGE 193
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDSL extension in XMP1 Typical reach: : 7.5 - 10 km, 1 pair, 0.9 mm, -40 dBm NEXT, without repeater ... ...
PAGE 194
XMP1 Release 5.5 System Description SDSL extension in XMP1 PS FSP ISHDSL FCD 901 48 Issue R2A, 07.2009 Central Unit PS FSP ISHDSL Central Unit ext. HDB3 1 2 3 4 5 6 7 8 ext.
PAGE 195
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Interfaces 5.3 Interfaces In the XMP1 system, the SDSL expansion provides the following interfaces: X600 SDSL Repeater ISHDSL 4 x SHDSL X500 SD bus 4 x E1 external PSPE 4 x E1 internal X601 Front cabling 4 x FSP X3 RPS-XMP1 X1 +UB -UB1-UB2 Figure 5.1: Interfaces - SDSL expansion 5.3.1 SHDSL The SDSL interface of the SHDSL line equipment can be configured for 1-pair operation (2-wire) or 2-wire Highspeed operation.
PAGE 196
XMP1 Release 5.5 System Description SHDSL FCD 901 48 Issue R2A, 07.2009 A transmission link with repeaters synchronizes itself section by section starting from the LT. During the standardized startup procedure, the units adapt themselves to the individual line parameters (e.g. attenuation, interference effects) and set up the EOC channel. The values determined in the course of this "line probing" can be called up by means of an equipment status request.
PAGE 197
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SHDSL Table 5.A: Transmission ranges - Approximate values CONDUCTOR DIAMETER KILOMETRICAL ATTENUATION @ 200 KHZ 0.4 mm 11 dB 0.6 mm 6 dB 0.9 mm 3.5 ... 4.5 dB 1.2 mm 2.5 ... 3.3 dB NOISE LEVEL CAUSED BY NEAR-END CROSS-TALK ATTENUATION (NEXT) MAX. RANGE WITH 1-PAIR OPERATION 2.2 km -40 dBm 4.2 km 5.5 ... 7 km 7.5 ...
PAGE 198
XMP1 Release 5.5 System Description E1 interface FCD 901 48 Issue R2A, 07.2009 5.3.2 E1 interface The ISHDSL module provides four external E1 interfaces and four internal E1 interfaces to the XMP1 kernel. If the SDSL line equipment is used as stand-alone system, only the external E1 interfaces are used. The E1 signal is passed on transparently to the SHDSL interface without CAS termination. The E1 interface complies with the classical ITU-T G.703/G.704 recommendations.
PAGE 199
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Remote power supply 5.4 Remote power supply The SDSL repeaters used in the SDSL line equipment can be remotely powered by the RPS-XMP1 remote power supply module or a local power supply. The RPS-XMP1 remote power supply module (05HAT00071AAN) provides four remote supply voltages of -116 V. In the XMP1 subrack, this module is mounted in a card slot adjacent to the ISHDSL module.
PAGE 200
XMP1 Release 5.5 System Description Remote power supply FCD 901 48 Issue R2A, 07.2009 The following table shows examples of the powering range in the 1-pair mode. Wires used Number of repeaters Coverage range with  0.9 mm Coverage range with  1.2 mm Coverage range with  1.4 mm 1 pair 1 19.2 km 36 km 49 km 1 pair 2 2 * 6.6 km 2 * 12 km 2 * 16 km 1 pair 3 3 * 2.9 km 3 * 5.3 km 3 * 7.
PAGE 201
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Clock 5.5 Clock The SHDSL extension uses the SHDSL clock mode 1 (plesiochronous). Internal 2 Mbit/s interfaces The internal 2 Mbit/s interfaces are synchronized using the XMP1 system clock.
PAGE 202
XMP1 Release 5.5 System Description Loops FCD 901 48 Issue R2A, 07.2009 5.6 Loops For testing purposes (e.g. troubleshooting), loopbacks can be switched at the LT/NT and the SHDSL repeaters. The diagram depicted in the figure below shows the position and direction of these test loops. 1 LT/NT loop - network side direction 2...
PAGE 203
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarms 5.7 Alarms The following alarms are supported for signalling operating and error statuses: • • • SDSL link alarms E1 link alarms Repeater alarms LT mode NT mode E1 Link alarms SDSL Link alarms Repeater 1 E1 Repeater 2 Repeater 3 Repeater 8 SDSL SDSL SDSL E1 SDSL Repeater alarms Rep. x; with x= 1 to 8 5.7.1 SDSL link alarms The following alarms (alarm no.
PAGE 204
XMP1 Release 5.5 System Description Repeater alarms • • • • • • • • FCD 901 48 Issue R2A, 07.2009 Link E1: LOS (Loss of Signal) Link E1: AIS Link E1: LOF (Loss of Frame) Link E1: CRC4 Link E1: BER -3 Link E1: BER -5/6 Link E1: D-bit received Link E1: N-bit received Alarm suppression Alarms detected Suppressed alarms LOS LOF, CRC4, BER-3, BER-5/6, D-bit AIS LOF, CRC4, BER-3, D-bit LOF CRC4, BER-3, BER-5/6, D-bit CRC4 BER-3, BER-5/6, D-bit BER-3 BER-5/6 BER-5/6 - DBit - 5.7.
PAGE 205
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Performance data 5.8 Performance data The following diagram shows the position of performance measuring points for the LT, NT and repeaters 1 to 8. LT mode NT mode Repeater 1 E1 Repeater 2 Repeater 3 Repeater 8 SDSL E1 SDSL NS CS NS CS NS CS NS CS D1CTP NS SHDSL PI SHDSL PI D1CTP NS Definition of 15-min/24-h SDSL performance counters Performance counter SDSL and repeater Table 5.
PAGE 206
XMP1 Release 5.5 System Description Online functions FCD 901 48 Issue R2A, 07.2009 5.9 Online functions The online functions of the operator software permit the following information to be requested for the ISHDSL module. • • • • • Page 5-16 Link State — Available Repeater Count [1 to 8] — Tip/Ring [reversed wires] — PSD Capability [symmetrical] — Transmission mode [ITU-T G.991.
PAGE 207
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Diagnostic Mode 5.10 Diagnostic Mode In order to startup the ISDSL port module with an LT initiated startup procedure the diagnostic mode has been established. The repeater establishes the transmission line even if in downstream direction no NT or further Repeater is connected. Because this is no normal operation mode an alarm will be generated to inform the user.
PAGE 208
XMP1 Release 5.5 System Description Diagnostic Mode Page 5-18 Proprietary Information FCD 901 48 Issue R2A, 07.
PAGE 209
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description ServiceOn XMP1 (SOX) Chapter 6 ServiceOn XMP1 (SOX) Nowadays network management plays an important role with regard to the operating costs of a system. To meet today’s requirements, Aastra offers with its ServiceOn XMP1 (SOX) a high-performance Network Management System for the XMP1 Cross-Connect Multiplexer.
PAGE 210
XMP1 Release 5.5 System Description Local Craft Terminal SOX - LCT • • • • • FCD 901 48 Issue R2A, 07.
PAGE 211
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX Network Manager SOX - NMS 6.1.2 SOX Network Manager SOX - NMS Functions The SOX Network Manager includes functions exceeding the Node Management functions. These permit the monitoring, control and configuration of a network.
PAGE 212
XMP1 Release 5.5 System Description SOX Network Manager SOX - NMS FCD 901 48 Issue R2A, 07.2009 The software supports the backup and restore function for the database; the SQL Enterprise Manager is not required. Copying, renaming and deleting of a database are supported. The conversion of the data of the last version is supported. System requirements Hardware PC • • • • • • • • • • • • Pentium 4 Processor 2.
PAGE 213
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX Architecture 6.2 SOX Architecture The Network Management System ServiceOn XMP1 (SOX) offers the following options for controlling and managing XMP1 networks. • Single-user system • Multi-user system Both systems will be described in the following sections. 6.2.1 Single-user system • • For networks up to 100 nodes Management System SOX, MS Windows XP Pro and SQL Server 2000 Standard on one high-end PC • Typically one user • V.
PAGE 214
XMP1 Release 5.5 System Description Single-user system FCD 901 48 Issue R2A, 07.2009 Splitup into sub-networks The XMP1 network can be split up into sub-networks (areas). These areas must be connected via Ethernet. For performance reasons, one area should not be assigned more than 70 nodes. In the Access Points to the individual areas, the Central Units (> Version 3.0) must be equipped with an additional module for IP connection. The individual sub-networks (areas) still form the overall XMP1 network.
PAGE 215
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX Multi-User Version 6.2.2 SOX Multi-User Version 6.2.2.1 The SOX multi-user version permits several users to access the database and XMP1 network simultaneously. Supported scenarios: • One user executes the configuration, while others use SOX as alarm monitoring station. • One user with a low authorization level monitors the alarms. If required, another user with a higher authorization level intervenes.
PAGE 216
XMP1 Release 5.5 System Description FCD 901 48 Issue R2A, 07.2009 Windows Session (User A) Windows Session (User B) SOX Client SOX Client Windows Session (User C) SOX Client SOX Client TCP TCP TCP TCP TCP TCP DB Server SOX Server Service Level Service Level Figure 6.3: Logic view of the SOX multi-user system Communication between the SOX Clients and SOX Server requires a quick and reliable TCP connection. Its use in a Wide Area Network (WAN) is not supported directly.
PAGE 217
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 218
XMP1 Release 5.5 System Description Parallel Configuration FCD 901 48 Issue R2A, 07.2009 Database to be used. In case of a connection of a new SOX Client, the SOX Server defines the authorization level of the SOX Client User and advises the SOX Client accordingly. The SOX Server also checks whether a valid dongle (WIBU-KEY) is available. SOX Client functions The SOX Client checks whether the software version used is compatible with the one used by the SOX Server.
PAGE 219
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Load Behavior SOX stores the original Database values. Before any changes will be saved to the Database, it is checked whether the Database still contains its original values. Only in this case, the changes will be executed (Optimistic Concurrency). Otherwise the action and thus the entire "Save" command will be rejected. Each modification of the data of a network element will result in a change of the configuration ID.
PAGE 220
XMP1 Release 5.5 System Description Safety FCD 901 48 Issue R2A, 07.2009 6.2.2.6 Safety Authentication Windows authentication The authentication function checks the user identity. The user authentication is executed by Microsoft Windows by means of the user name and password. Windows requires each user to log on with the password and user name. A user logon normally takes place in the Windows domain, i.e. the individual users are know within this domain.
PAGE 221
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 222
XMP1 Release 5.5 System Description Safety FCD 901 48 Issue R2A, 07.
PAGE 223
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Safety Authorization Authorization means that the program identifies as to which authorizations a user has and which actions the individual users may execute. Note: The user identity detected within the Windows authentication process is used by the SOX Server and SOX Database as basis for the authorization check.
PAGE 224
XMP1 Release 5.5 System Description Safety FCD 901 48 Issue R2A, 07.2009 SOX Server In the default configuration, an authorization check is not executed in the SOX Server. Each user has all rights. Optionally, it is possible to activate a check for user rights in the SOX Server. This is done via the configuration file or command line parameters. ’ See Section , SOX Server side . -> SecurityMode = azman. In this case, the SOX Server uses the Microsoft Authorization Manager (AzMan).
PAGE 225
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Safety Authorization without AzMan If the Windows Authorization Manager (AzMan) is not used, all users are authorized to send data to the XMP1 network. The default setting for the "SecurityMode" is "none", i.e. authorization without "azman".
PAGE 226
XMP1 Release 5.5 System Description Safety FCD 901 48 Issue R2A, 07.2009 With "AzMan", the SOX Server uses the Microsoft Authorization Manager to check the authorizations of SOX Client users. Thus, users not authorized are prevented from accessing the network.
PAGE 227
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Safety Note: The use of the Authorization Manager in SOX represents an option. Without the Authorization Manager, each user has full read and write access to the SOX Server. The Authorization Manager is an integrated part of the Windows 2003 Server. For Windows XP, the Windows Server 2003 Administration Tools Pack can be installed. The Authorization Manager is used optionally only by the SOX Server.
PAGE 228
XMP1 Release 5.5 System Description User Administration FCD 901 48 Issue R2A, 07.2009 6.2.2.7 User Administration SOX users are allocated to certain Windows User Groups depending on the authorization levels provided for them in the SOX. These Windows User Groups are used by the SOX Server and SQL Database Server to carry out the authorization check. These Windows User Groups are entered in the SQL Database Server as SQL Server Logons. For each SOX Database, database users must be defined.
PAGE 229
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description User Administration Windows User Groups SQL Database Server SQL Server logon In the SQL Database Server, a SQL Server logon is configured for each of the four Windows User Groups existing. This SQL Server logon is used to define as to which Windows User or User Group can access the SQL Database Server.
PAGE 230
XMP1 Release 5.5 System Description User Administration FCD 901 48 Issue R2A, 07.2009 SQL Server Logon Database users The database users to be granted access to the SOX database must be entered in the latter. Furthermore the database users must also be assigned database roles. These define the authorization level of a database user when accessing the database. This allocation must be performed for each database used.
PAGE 231
FCD 901 48 Issue R2A, 07.2009 Windows User Groups: -SoxReadOnlyGroup -SoxAlarmAcknowledgeGroup -SoxAlarmOperatorGroup -SoxConfiguratorGroup XMP1 Release 5.
PAGE 232
XMP1 Release 5.5 System Description User Administration FCD 901 48 Issue R2A, 07.2009 Authorization Manager (AzMan) The Microsoft Authorization Manager (AzMan) supports a role-based security model. Using the Authorization Manager, an own authorization system is implemented in the SOX Server. If the Microsoft Authorization Manager is used to check the authorization of the SOX Server, the Windows Users/User Groups must be assigned to the predefined SOX roles in the Microsoft Authorization Manager.
PAGE 233
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Installation 6.2.2.8 Installation The SOX Setup copies the files required for the Client, Server and Single-User Version into the installation directory. This directory should contain three *.exe files: Aastra.Sox.SoxKernelService.exe SoX Server as Windows Service – must be installed as Windows Service using the installutil.exe auxiliary program before being used. Aastra.Sox.SoxKernelConsole.
PAGE 234
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 6.2.2.9 Configuration Configuration files The configuration of the SOX multi-user version takes place with the installation using configuration files. The configuration files required for the SOX Server and SOX Client are different. In these configuration files, startup settings are defined for the SOX Server and SOX Client. The configuration files are located in the SOX installation directory.
PAGE 235
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration SOX Server side SoxKernelConsole.config file In the „Remoting“ section, the communication channels and Server Services will be specified. In the configuration file, only values regarding the TCP channel entry should be changed. Port The „port“ attribute specifies the TCP port to be opened by the SOX Server.
PAGE 236
XMP1 Release 5.5 System Description Configuration FCD 901 48 Issue R2A, 07.2009 DataBaseServer Specifies the Database Server. DatabaseName Specifies the Database in the Database Server. KernelSupervisonMinutes Specifies the time (in minutes) after which the SOX Server will check whether the connection to its SOX Clients is still existing. ImpersonateClients Defines the behavior of the SOX Server on entry of the commands "Delete alarms" or "Acknowledge alarms".
PAGE 237
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration SOX Client Side SoxUserInterface.exe.config file On the SOX Client side, the communication channel to the SOX Server must be described in the configuration file (Aastra.Sox.SoxUserInterface.exe.config). The SOX Server in turn directly informs the SOX Client on the Database used. url The two "url" attributes are used to indicate as to where the services of the SOX Server can be found.
PAGE 238
XMP1 Release 5.5 System Description Configuration tokenImpersonationLevel FCD 901 48 Issue R2A, 07.2009 Using the "tokenImpersonationLevel" attribute, the SOX Client can authorize the SOX Server to execute actions under the SOX Client User Account. Possible and relevant values for SOX applications are "Identification" and "Impersonation".
PAGE 239
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration PCs must have the „Trust for Delegation“ authorization in the ActiveDirectory. The SOX Client must give the SOX Server the authorization to delegate his user authorization to the Database Server. To allow this the entry „tokenImpersonationLevel“ in the SOX Client config file must be set to „Delegation“.
PAGE 240
XMP1 Release 5.5 System Description Connection of the XMP1 Network to SOX FCD 901 48 Issue R2A, 07.2009 6.3 Connection of the XMP1 Network to SOX This chapter describes the connection of the XMP1 system to ServiceOn XMP1. 6.3.1 General The XMP1 nodes and thus the XMP1 network are equipped with interfaces which permit the configuration, control and supervision of the XMP1 system via the ServiceOn XMP1 Management System.
PAGE 241
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SOX communication with network/nodes 6.3.2 SOX communication with network/nodes Depending on the hardware of the XMP1 Access Point, communication between the SOX and network can take place in different ways. • Directly via TCP/IP using an Ethernet adapter or CU-E on XMP1 Central Units (62.7040.xxx) or • using the XmpIpDrv software undertaking a TCP/IP to RS232 conversion.
PAGE 242
XMP1 Release 5.5 System Description Connection of SOX via TCP/IP FCD 901 48 Issue R2A, 07.2009 The following diagram shows the direct connection of the PC to the Ethernet adapter/CU-E by means of a connecting cable. Operator Terminal XMP1 Connecting cable, crossed X20 XMP1 Central Unit with -Ethernet adapter/CU-E -Ethernet address SOX LMT XMP1 XMP1 XMP1 RS232 -> X3 Central Unit XMP1 Note: Use a crossed connecting cable to set up a direct connection between the Ethernet interface and PC.
PAGE 243
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Connection of SOX via TCP/IP Connection to the Ethernet interface via LAN The following diagram shows how the PC can be connected via an existing LAN infrastructure. LAN Central unit with X20 Ethernet adapter/CU-E XMP1 Operator Terminal SOX LMT XMP1 X20 XMP1 Central Unit with -Ethernet adapter/CU-E -Ethernet address XMP1 XMP1 XMP1 RS232 -> X3 Central Unit The PC (SOX) is connected to an existing LAN.
PAGE 244
XMP1 Release 5.5 System Description Connection via F-interface (RS232) FCD 901 48 Issue R2A, 07.2009 6.3.2.2 Connection via F-interface (RS232) Direct access to the RS232 interface of a node The following diagram shows how the PC (SOX) can be directly connected to the RS232 interface (X3) of the Central Unit by means of a connecting cable. The XMPIpDrv software required for this type of connection is available on the PC besides the SOX software.
PAGE 245
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Connection via F-interface (RS232) Remote access via a remote PC using XMPIpDrv In the example described below, the SOX is connected to a XMP1 node via a remote PC. The SOX and remote PC are interconnected via a LAN. The remote PC is connected via a COM port to the RS232 interface of the XMP1 node. The remote PC must be loaded with the XMPIpDrv software and started up. In addition, the remote PC must be assigned an Ethernet address.
PAGE 246
XMP1 Release 5.5 System Description IP settings for the Ethernet adapter/CU-E FCD 901 48 Issue R2A, 07.2009 6.3.3 IP settings for the Ethernet adapter/CU-E If the XMP1 network is connected via an Ethernet adapter/CU-E, IP settings are required for the latter. The IP configuration data can be entered manually via the LSP PDA or WINLSP or via a BootP/DHCP server. The manual settings required can be made using LSP/WINLSP menu item 7: IP Settings.
PAGE 247
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description IP settings for the Ethernet adapter/CU-E Menu item 72: Enter Subnet Mask Using the subnet mask option, you can mask part of the IP address (Internet Protocol address). This leads to a splitup of the IP address into the network and host portion. Example: 255.255.0.0 Menu item 73: Enter DNS Address The IP address of the Domain Name Server (DNS) is entered via menu item 73. The DNS performs a translation between the host name and IP address.
PAGE 248
XMP1 Release 5.5 System Description Network Views in the SOX FCD 901 48 Issue R2A, 07.2009 6.4 Network Views in the SOX Using the ServiceOn XMP1 software, a network can be displayed either in the Graphical View or in a Tree View. 6.4.1 Graphical View The Graphical View offers the possibility to set up a network topology by means of layers and configure the network in a clear form. A layer represents a certain part of the network such as an area.
PAGE 249
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Tree View 6.4.2 Tree View In the Tree View, the network structure is displayed with its • • • Network elements Areas Reactions The following screenshot shows an example of a network displayed in the Tree View.
PAGE 250
XMP1 Release 5.5 System Description Database FCD 901 48 Issue R2A, 07.2009 6.5 Database The configuration data of XMP1 networks are stored in a MS SQL 2000 database. The MS SQL server should (in the current single-user version) be installed on the same PC as the SOX software. The MS SQL server can manage several (arbitrary) databases. The configuration data of a XMP1 network are always stored in a database. Currently, only one network is supported by each database.
PAGE 251
FCD 901 48 Issue R2A, 07.2009 Aastra XMP1 Release 5.
PAGE 252
XMP1 Release 5.5 System Description Online Functions FCD 901 48 Issue R2A, 07.2009 6.6 Online Functions The SOX online functions enable the user to request information from or undertake certain actions in the network. The following online functions are available: • Node state • Firmware • CoChannel Radio • Loop • Debugging • Inventory Data • Password • Signal concentrator • Line test These online functions are briefly described in the following section.
PAGE 253
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Node State 6.6.
PAGE 254
XMP1 Release 5.5 System Description Firmware FCD 901 48 Issue R2A, 07.2009 6.6.2 Firmware The "Firmware" mask displays information regarding the firmware loaded in the node. Here a distinction is made between the "active" and "passive" firmware. The firmware is identified by its firmware ID. Example: V37003c4bNZa In this mask, you can switch over between the "active" and "passive" firmware. 6.6.3 CoChannel Radio If the ports of a node are used to transmit co-channel radio data, the ports must be aligned.
PAGE 255
FCD 901 48 Issue R2A, 07.2009 Aastra XMP1 Release 5.
PAGE 256
XMP1 Release 5.5 System Description Loop FCD 901 48 Issue R2A, 07.2009 6.6.4 Loop On certain modules of the system, loops can be switched for testing purposes. This is possible via the "Loop" mask that can be called up in the "Online Functions" window. In case of modules composed of several boards, possible loops are displayed individually for each board provided that the expanded configuration option has been selected and the boards have been defined. Possible loops Table 6.
PAGE 257
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Loop Table 6.E: Loops ISDN Port Loop no.
PAGE 258
XMP1 Release 5.5 System Description Debugging FCD 901 48 Issue R2A, 07.2009 6.6.5 Debugging Using the debugging function, debug commands can be sent to the node. These commands can be used to make requests or settings in the node. There are debugging commands answered by the node with a return message and other ones without a return message from the node.
PAGE 259
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Inventory Data 6.6.6 Inventory Data The XMP1 modules and boards are equipped with an electronic nameplate (GBÜ-EPROM) which contains the RID data (remote inventory data). These can include all or part of the following data: • Company ID • Equipment short designation • Part no. • Software release • Equipment level • Revision level • Manufacturing no.
PAGE 260
XMP1 Release 5.5 System Description Password FCD 901 48 Issue R2A, 07.2009 6.6.7 Password To prevent unauthorized access to certain functions, it is possible to define passwords. A distinction is made between two different types of passwords: • Node number password • General password The "Node number password" is required by the user to modify the number of the node.
PAGE 261
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Line Test 6.6.8 Line Test Using the line test function it is possible to check and evaluate any port-to-port connection defined between two nodes. The transmission link between these nodes can include repeaters. Each repeater available on the link is unambiguously assigned to a node. The line test is used to detect a defective port, a fault that has occurred on the transmission link between two ports or a fault between a port and repeater.
PAGE 262
XMP1 Release 5.5 System Description Signal Concentrator FCD 901 48 Issue R2A, 07.2009 6.6.9 Signal Concentrator The signal concentrator provides the interfaces (sensors and transmitters) to external devices. Using the sensors, messages from external units can be processed. Control functions from external devices are possible via the transmitters.
PAGE 263
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Network Reactions 6.7 Network Reactions Using the "Network Reactions" option, you can configure a certain reaction to be triggered in a target in consequence of one or several alarms generated by a certain source. Alarms are considered as the source of a network reaction (Reaction). Note: The signal available at a signal concentrator input is also treated as an alarm.
PAGE 264
XMP1 Release 5.5 System Description Network Reactions FCD 901 48 Issue R2A, 07.2009 Reactions Network reactions are configured in the "Tree View" of the SOX Network Manager via the "Reactions" option. Normally, network reactions are configured in the structure hierarchically below a filter or observer. If a network reaction is defined in the structure directly below "Reactions", the alarms will not be filtered.
PAGE 265
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Network Reactions Node 1: The alarms of door contacts 1 to 3 in node 1 shall be applied to sensors 1 to 3 of the signal concentrator mounted in card slot 7. Node 2: The alarms of sensors 1, 2 and 3 of node 1 as well as the alarms of card slot 9, sub-address 1, ISDN S0F shall be made available as general alarm in node 2 via the signal concentrator mounted in card slot 12, transmitter 1.
PAGE 266
XMP1 Release 5.5 System Description Alarm Management FCD 901 48 Issue R2A, 07.2009 6.
PAGE 267
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm Management Alarm list In the alarm list, alarms are displayed in table form. It is possible to display the alarms of the current session, active alarms or an alarm history. In the alarm list, alarms can be deleted and acknowledged. The following diagram shows the ServiceOn XMP1 alarm list. For documentation purposes, the alarm list can be exported to an xml file. The following screenshot shows an extract from such an xml file.
PAGE 268
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 6.8.1 Alarm list Central faults Central faults are hardware faults which do no longer permit a dialog via the 2 Mbit/s interface. In this case, AIS must be sent to F1out provided that this is still possible. Analog connections are released and blocked. Central faults include: • • • failure of the central controller failure of bus lines failure of a non-redundant system power supply.
PAGE 269
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND SEVERITY ALARM DESCRIPTION ALARM CONTACT 020 n.T3 a Critical A and ZA (A) Loss of ext. clock T3in (act.) 021 RxCRec Minor A and ZA (A) Loss of Rx clock recovery 022 n.T3 i Minor B and ZA (B) Loss of ext. clock T3in (pass.
PAGE 270
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND ALARM DESCRIPTION SEVERITY ALARM CONTACT DEFAULT FOR ALARMREROUTING 060 EQPT Critical A and ZA (A) Equipping fault X 061 LOS Critical A and ZA (A) LOS at F1in X 062 AIS Critical ZA(A) AIS at F1in X 063 F-Loc Critical EL Dynamic fault location active X 064 FLext.
PAGE 271
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 272
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 273
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 274
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 275
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 276
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 277
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 278
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 279
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 280
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 281
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 282
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN.
PAGE 283
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND SEVERITY ALARM DESCRIPTION ALARM CONTACT 654 Minor Rep.1: SW/HW Incompatibility 655 Minor Rep.1: Error during software distribution 656 Critical Rep.2: Failure during configuration 657 Minor Rep.2: SNR margin Alarm NS 658 Minor Rep.2: excessive BER (10E-5/6) NS 659 Critical Rep.2: Loss of Signal, Loss of Frame CS 660 Minor Rep.
PAGE 284
XMP1 Release 5.5 System Description Alarm list FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND SEVERITY ALARM DESCRIPTION ALARM CONTACT 674 Minor Rep.4: excessive BER (10E-5/6) NS 675 Critical Rep.4: Loss of Signal, Loss of Frame CS 676 Minor Rep.4: SNR margin Alarm CS 677 Minor Rep.4: excessive BER (10E-5/6) CS 678 Minor Rep.4: SW/HW Incompatibility 679 Minor Rep.4: Error during software distribution 680 Critical Rep.
PAGE 285
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Alarm list Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND ALARM DESCRIPTION SEVERITY ALARM CONTACT 694 Minor Rep.6: SW/HW Incompatibility 695 Minor Rep.6: Error during software distribution 696 Critical Rep.7: Failure during configuration 697 Minor Rep.7: SNR margin Alarm NS 698 Minor Rep.7: excessive BER (10E-5/6) NS 699 Critical Rep.7: Loss of Signal, Loss of Frame CS 700 Minor Rep.
PAGE 286
XMP1 Release 5.5 System Description Alarm report FCD 901 48 Issue R2A, 07.2009 Table 6.G: List of alarms ALARM SHORT NO. DESIG. LED ON SIGN. PANEL AND SEVERITY ALARM DESCRIPTION ALARM CONTACT 1001 - Minor - Alarms purged. Alarm memory cleared; alarms partly deleted 2001 - Minor - Overflow in alarm handling. Messages were lost 2002 - Minor - Connection to database broken 2003 - Critical - Alarm(s) lost.
PAGE 287
FCD 901 48 Issue R2A, 07.2009 Aastra XMP1 Release 5.
PAGE 288
XMP1 Release 5.5 System Description Rerouting at Alarms FCD 901 48 Issue R2A, 07.2009 6.9 Rerouting at Alarms As of SOX Version 5.5 the alarm rerouting is supported. This function can be executed manually at a Single/Multi user system and automatically at a Multi user system. With this function it is possible to reroute circuits which are affected by alarms. For this Trunks are monitored for appropriate alarms. Which faults are activating the rerouting function is defined in the alarm list.
PAGE 289
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Rerouting at Alarms Note: With a single user system "rerouting" must be carried out manually Multi user system For a multi user system it is possible to configure that the „Reroute on Alarms function can be carried out automatically. The configuration will be done via the “Tree View” -> "Areas" -> "Rerouting on Alarms Service" menu. Prerequisites Carrying out the "Rerouting on Alarms" function automatically a service is used.
PAGE 290
XMP1 Release 5.5 System Description Rerouting at Alarms FCD 901 48 Issue R2A, 07.2009 Depending on the result of the analysis all Network elements affected by the rerouting will be locked for other users. Afterwards the configuration of the changed network elements will be transmitted as broadcast to the network and activated. Then the configuration is stored to the database. The lock of the network elements concerned is reset again. In case of a failure e.g.
PAGE 291
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Messages 6.10 Messages Messages exchanged between the SOX and network can be displayed. This is possible by means of the "Messages" function. Using this function, both incoming messages (Input) and outgoing messages (Output) can be displayed. Input: Messages sent from the network to SOX. Output: Messages sent from SOX to the network. The following screenshot shows an example of such messages.
PAGE 292
XMP1 Release 5.5 System Description Messages Page 6-84 Proprietary Information FCD 901 48 Issue R2A, 07.
PAGE 293
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Network Control Using ServiceOn Access Chapter 7 Network Control Using ServiceOn Access The present chapter describes how XMP1 can be controlled and monitored by the ServiceOn Access Network Management System. For more detailed information, please refer to the Operator Manuals for ServiceOn Access and the Operating Instructions for the SOX MSP Software. The XMP1 Flexible Multiplexer can be connected to a TMN in different ways.
PAGE 294
XMP1 Release 5.5 System Description Introduction to the SISA Network FCD 901 48 Issue R2A, 07.2009 In order to provide redundancy, it is possible to set up ring structures in a SISA network. The connection of the SISA network to the LAN/WAN of the ServiceOn Access Network Management System is set up via a QD2 gateway. ServiceOn Access can be connected to several QD2 gateways.
PAGE 295
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1 as network element 7.1.1 XMP1 as network element Within a TMN, the XMP1 node is considered as network element. Normally, a network element is composed of several units which can be addressed individually. It is possible to regard the network element from a logic functional or an equipment view.
PAGE 296
XMP1 Release 5.5 System Description Connecting options FCD 901 48 Issue R2A, 07.2009 7.1.2 Connecting options For connecting a PDH network element to a network management system, a Q-interface complying with ITU-T M.3010 is used. In the XMP1 Flexible Multiplexer, this Q-interface is made available by the QD2 Central Unit or the QD2 adapter. Due to the data exchange with the Central Unit functions, the respective QD2 part provides the convertible information and configuration data at the Q-interface.
PAGE 297
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Connecting options SOA RS-485 ECC64 ECC8 IP NE XMP1 With QD2 Master license: RS-485 ECC64 ECC8 Number of NEs: 0. . .30 SISA addr. no.: 1. . .30 Node no. equal/unequal to SISA node no. Number of NEs: 0. . .30 SISA addr. no.: 1. . .30 Node no. equal/unequal to SISA node no. Number of NEs: 0. . .30 SISA addr. no.: 1. . .254 Node no. = SISA node no.
PAGE 298
XMP1 Release 5.5 System Description Connecting options FCD 901 48 Issue R2A, 07.2009 ECC64 (optional) In this operating mode, a SISA network can be set up within the XMP1 network by switching a digital 64 kbit/s conference. The access node to SOA is configured as ECC64 Master. In this case, another SISA-V (5) appears below the SISA-V. Up to 30 network elements can be addressed via this SISA-V (5).
PAGE 299
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Connecting options Connection via ECC8) (optional) An alternative option, which permits the management channel to be routed in the XMP1 network, is the use of ECC8 with a data rate of 8 kbit/s. In this case, the management information is transmitted in time slot 0 of the PCM frame (E1) in bits 7 and 8. This must be taken into consideration during network planning with regard to the expected performance.
PAGE 300
XMP1 Release 5.5 System Description Connecting options FCD 901 48 Issue R2A, 07.2009 IP XMP1 Node 3 SISA-V XMP1 1 XQI 2 SISA-V RS485 SISA-V ECC8 3 4 1 30 XMP1 Node 5 SISA-V ECC64 Page 7-8 30 30 XMP1 Node 7 SISA-V XMP1 Menu code 76: "E.SISA Con. No." 5 1 1 Decentral card slot data: Sub-address 5 Central Unit -> ECC8 Menu code. 75: "E.Addr.
PAGE 301
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Commissioning 7.1.3 Commissioning The initial commissioning and new commissioning of XMP1 network expansions of version 5.1 and higher is executed using the SOX MSP. The commissioning process of the entire network element is performed according to the operating instructions of the individual modules and depending on the performance features of the SOX MSP version used.
PAGE 302
XMP1 Release 5.5 System Description Functional model FCD 901 48 Issue R2A, 07.2009 TTF-1 TTF-1 SPB-1 HPX VC4 TTF-1 TTF-4 LPX VC3 HOA MSPTF-4 MSPTF-1/4 TTF-1 RTF(E)-1/4 MSPTF-1 ETH nxVCx TTF-1 Eth-Port TTF-1 LOI 2M LPX VC12 IPMB 64/2 STU Span (Full) TDM (EPP2) TTF-1 EPPM 64/2 LOM 2 OPPM 64/2 DSK 64 IPMB 64/2 MODUL KZU BPX 64 xDSL-Extern ISDN EPG DATA SISA0 DATA nx64 E(O)PP 2 IPMB 64/2 PSW SET2 NEControl E(O)PP 2 Figure 7.
PAGE 303
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Configuration Using the SOX MSP 7.2 Configuration Using the SOX MSP 7.2.1 General The SOX MSP is a windows-based software which has been specially developed for the configuration and operation of the XMP1 node. The Service PC requires the LMT Operator Terminal XMP1 for SOX MSP (V5.1) and SOX MSP Software. The Service PC is connected to the XMP1 node. The LMT software is started and a connection to the network is set up via the network view.
PAGE 304
XMP1 Release 5.5 System Description Functional units of the SOX MSP software • Page 7-12 FCD 901 48 Issue R2A, 07.2009 Support of the signal concentrator card, display of signal statuses and manual control of output relays.
PAGE 305
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Mechanical Design, Equipment and Cabling Chapter 8 Mechanical Design, Equipment and Cabling 8.1 Design Three different types of XMP1 subracks are available for mounting plug-in modules. They differ from each other with respect to their number of card slots. • • • XMP1 Subrack (16), see Section 8.1.1, XMP1 Subrack (16), XMP1 Subrack (8) XMP1 Subrack (8), see Section 8.1.1, XMP1 Subrack (16), XMP1 Subrack (8) XMP1 Subrack (16/32), Section 8.
PAGE 306
XMP1 Release 5.5 System Description XMP1 Subrack (16), XMP1 Subrack (8) FCD 901 48 Issue R2A, 07.2009 Figure 8.1: XMP1 subrack Boreholes for ground contact Guiding rails Backplane Locking bar Rail mount Figure 8.
PAGE 307
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1 Subrack (16), XMP1 Subrack (8) The following figure shows the open XMP1 subrack (16). The following figure shows the open XMP1 subrack (8). The left-hand section of the XMP1 subrack includes the distribution strips (LSA-Plus strips) and trapezoidal connectors. Space for distribution strips (LSA-Plus strips) and trapezoidal connectors Figure 8.
PAGE 308
XMP1 Release 5.5 System Description XMP1 Subrack (16/32) FCD 901 48 Issue R2A, 07.2009 8.1.2 XMP1 Subrack (16/32) XMP1 subrack (16/32) (BFD 101 030/1) can be doubled to provide card slots for up to 32 modules. The connection between two XMP1 subracks (16/32) is set up using a connecting kit. The latter includes a cable duct and a connecting cable. Tab. 8.A: XMP1 subrack (16/32) DESIGNATION PART NO. NOTE XMP1 Subrack (16/32) BFD 101 030/1 For cascading, with front panel Bus termination 62.7026.140.
PAGE 309
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Modules 8.1.3 Modules The modules are composed of PCBs 250 mm high and 210 mm wide. They are connected to the backplane wiring of the XMP1 subrack via 64/96-pin plug connectors. Since all modules have a uniform connector assignment to the bus line on the backplane, the XMP1 subrack can be freely equipped. The only exception is made by the Central Unit (and the redundant Central Unit).
PAGE 310
XMP1 Release 5.5 System Description Equipment with Modules FCD 901 48 Issue R2A, 07.2009 8.2 Equipment with Modules 8.2.1 Central Units Depending on the individual case of application, the XMP1 node must be equipped with different Central Units. These must always be mounted in the extreme right of the XMP1 subrack. Thus, in XMP1 subrack (16), the Central Unit must be mounted in card slot 16 and in XMP1 subrack (8), it must be mounted in card slot 8. Table 8.
PAGE 311
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Redundancy modules Operation as terminal/add-drop station in the basic network with QD2 interface If the XMP1 Flexible Multiplexer is operated as terminal or add-drop station in a basic network monitored and manged by the ServiceOn Access, the Central Unit GN/QD2 (AN00239607) is required. 8.2.2 Redundancy modules Each Central Unit can be doubled.
PAGE 312
XMP1 Release 5.5 System Description Port modules FCD 901 48 Issue R2A, 07.2009 Table 8.C: Port modules DESIGNATION PART NO. Port Nx64k (V.11) with V.11 interface 62.7040.340.00-A001 AN00218363 Port Nx64k (V.11 + V.35) with V.11/V.35 interfaces 62.7040.340.00-A002 AN00224736 Port LE2 OPT U 62.7026.530.00-A001 AN00043311 - Module 2F (1270 to 1340 nm), (25 dB) 62.7026.570.00-A001 AN00120461 - Module 1F (Transmitter: 1270 to 1330 nm; Receiver: 1510 to 1590 nm) 62.7026.580.
PAGE 313
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Power supply unit 8.2.7 Power supply unit The following power supply is available for supplying the modules with the necessary operating voltages: Table 8.D: Power supply unit DESIGNATION IDENT. NO. 05HAT00080AAB PSU XMP1 8.2.8 SDH expansion The modules required for the SDH expansion of the XMP1 system are listed in the following table. Tab. 8.E: Components of SDH expansion DESIGNATION IDENT. NO.
PAGE 314
XMP1 Release 5.5 System Description Ethernet expansion FCD 901 48 Issue R2A, 07.2009 8.2.9 Ethernet expansion The modules required for the Ethernet expansion of the XMP1 system are listed in the following table. DESIGNATION IDENT. NO. NOTE EoSCU (Ethernet over SDH Core Unit) 05HAN00367AAV - CU-E (Central Unit Expansion) with IB cable 05HBA00006AAX Expansion module for Central Units version V3.
PAGE 315
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Video modules 8.2.10 Video modules The following modules are available for transmitting video signals. DESIGNATION IDENT. NO. NOTE Video encoder (2) 05HAT00063AAC 2 x video-in Video decoder (2) 05HAT00062AAA 2 x video-out IDENT. NO. NOTE ISHDSL (4) 05HAT00070AAL four SDSL IF., four external E1 IF four internal 2Mbit/s IF FSP IF.
PAGE 316
XMP1 Release 5.5 System Description Channel modules FCD 901 48 Issue R2A, 07.2009 8.2.12 Channel modules The following channel modules are available: Table 8.F: Channel modules MODULE TYPE IDENT. NO. KZU CHANNEL INTERFACE MODULES KZU OSX (4), 4 interfaces configurable as SU, EX, OB and OBG 05HAT00035AAL KZU SUB (8), with eight interfaces 05HAT00073AAS KZU EX (8), with eight interfaces 62.7040.210.00-A002 AN00274683 KZU FEK (8), with eight interfaces 62.7040.250.
PAGE 317
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description ServiceOn XMP1 - License 8.3 ServiceOn XMP1 - License Table 8.
PAGE 318
XMP1 Release 5.5 System Description Mounting the Modules in the XMP1 Subrack FCD 901 48 Issue R2A, 07.2009 8.4 Mounting the Modules in the XMP1 Subrack The modules are for exclusive use in the XMP1 system. Installation and settings must be executed by appropriately trained specialists and service personnel. Settings on modules may be performed only after extraction of the corresponding modules from the XMP1 subrack. Observe handling instructions. Components sensitive to electrostatic discharge.
PAGE 319
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Mounting the Modules in the XMP1 Subrack Connecting cable • • • Carefully strip the insulation in the area of the terminal strip below the modules (do not destroy the braided shield!). Secure the cable in position using a cable tie. Ensure that there is a good electrical contact between the shield and metallic comb rail. There must be a highly conductive connection between the braided shield and XMP1 subrack. Connect the interface cable.
PAGE 320
XMP1 Release 5.5 System Description SOX Connection FCD 901 48 Issue R2A, 07.2009 8.5 SOX Connection The connection of SOX to the network can be set up via a F-interface or Ethernet interface (optional). 8.5.1 F-interface The connection to the SOX computer is established via connector X3 (F-interface) of the Central Unit using a connecting cable. The connecting cable to be used for this purpose is V.24/V.28.
PAGE 321
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Ethernet interface 8.5.2 Ethernet interface An Ethernet interface for connecting the NMS is provided by the Ethernet Adapter sub-module or - with the SDH expansion - by the CU-E (Central Unit Expansion) sub-module. For using the Ethernet interface, the Central Unit must therefore be equipped with an Ethernet Adapter (AN00114784, 62.7040.303.00-A001) or - with the SDH expansion - with the CU-E sub-module (05HBA00006AAX).
PAGE 322
XMP1 Release 5.5 System Description XMP1 Subrack Installation FCD 901 48 Issue R2A, 07.2009 8.6 XMP1 Subrack Installation 8.6.1 19" cabinets The XMP1 subrack (8), (16) is appropriate for being mounted in 19" cabinets (with/without swing-out frame). The XMP1 subrack (8), (16) is secured in the cabinet or rack by means of cage nuts. For more detailed information, please refer to Section 8.7, XMP1 Subrack Grounding .
PAGE 323
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 324
XMP1 Release 5.5 System Description ETS racks FCD 901 48 Issue R2A, 07.2009 8.6.2 ETS racks The XMP1 subrack (8), (16) can also be mounted in ETS racks. In this case, it is necessary to exchange the flanges on the left-hand and right-hand side of the XMP1 subrack. These flanges can be turned and are thus appropriate for being mounted both in ETSI and 19" cabinets. The XMP1 subrack (8), (16) is secured by means of cage nuts. For more detailed information, please refer to Section 8.
PAGE 325
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description ETS racks Rack uprights Air circulation Pitch units: Cabling space Cabling space Aastra Proprietary Information Adapter set 19“/ETS, one per XMP1 Subrack S.No. AN0010791 (flat) or S.No. AN00021917 (cranked) Not necessary for subracks with swap flanges.
PAGE 326
XMP1 Release 5.5 System Description Remounting the flanges FCD 901 48 Issue R2A, 07.2009 8.6.3 Remounting the flanges For installation in a 19“ rack or system rack (ETS), the XMP1 subrack (16), (8) is equipped with a mounting flange on its left and right side. In the as-delivered state, these flanges are mounted for installation in a 19“ rack. If the XMP1 subrack shall be installed in a different rack type, the flanges must be remounted to adapt the mounting dimensions correspondingly.
PAGE 327
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1 Subrack Grounding 8.7 XMP1 Subrack Grounding Safety instructions CAUTION Grounding must comply with the relevant national regulations! In case of grounded racks or cabinets with unlacquered uprights, use cage nuts for securing the XMP1 subrack. If the XMP1 subrack is mounted in a grounded rack or cabinet with lacquered uprights, secure it by means of cage nuts with grounding claws.
PAGE 328
XMP1 Release 5.5 System Description Grounding bolt FCD 901 48 Issue R2A, 07.2009 8.7.3 Grounding bolt If the XMP1 subrack is separately mounted or if the conductivity within the housing is not sufficient, a grounding cable must be connected to the XMP1 subrack. For this purpose the grounding bolt is used. The grounding bolt is marked by a grounding symbol.
PAGE 329
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1-SL 8.8 XMP1-SL The XMP1-SL (05HAN00499AAC) is composed of a 19“ housing with the following dimensions: Width: 450 mm Height: 55 mm Depth: 300 mm. The XMP1-SL can be mounted in 19“ and ETSI racks. The unit is equipped with special mounting flanges appropriate for installation in both rack types. The XMP1-SL cable connections are set up via connectors located on the front side of the unit.
PAGE 330
XMP1 Release 5.5 System Description XMP1-SL FCD 901 48 Issue R2A, 07.2009 MAC Address Typ label Mounting flange Grounding bolt Mounting flange Switch for supply voltage range Cover plate Figure 8.
PAGE 331
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Technical Characteristics Chapter 9 Technical Characteristics Table 9.A: General characteristics 9.1 General Characteristics Supply voltages 48/60 V DC Power consumption depending on equipment with modules Dimensions (H x W x D) 19" design 310 x 480 x 235 mm Card slots XMP1 subrack (16): 16 card slots XMP1 subrack (8): 8 card slots XMP1 subrack (16/32): 16 (32) card slots Table 9.B: System parameters 9.
PAGE 332
XMP1 Release 5.5 System Description EMC, Equipment Safety, Climatic Conditions FCD 901 48 Issue R2A, 07.2009 Table 9.C: Climatic and EMC conditions 9.3 EMC, Equipment Safety, Climatic Conditions 9.3.1 Interference emission acc. to EN 55022 limiting value class B, EN 300386 9.3.2 Immunity to noise acc. to EN 55024, EN 300386 9.3.3 Equipment safety acc. to EN 60950 9.3.4 Climatic conditions Operation ETS 300019, Class T3.1e Class 3.2 for modules with drawing no. 62.7040 Storage ETS 300019, Class T1.
PAGE 333
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Central Unit Table 9.D: Central Unit 9.4 Central Unit 9.4.1 RS485 interface (Only with Central Unit QD2 and Central Unit GN/QD2) Electrical features EIA standard RS-485 (V.11) Bus system Serial bus system acc. to EIA-RS 485, half-duplex Length of drop line to bus subscriber max. 2.
PAGE 334
XMP1 Release 5.5 System Description Ethernet interface (optional with SOX) FCD 901 48 Issue R2A, 07.2009 Table 9.D: Central Unit 9.4.6 Ethernet interface (optional with SOX) Interface Provided by Ethernet Adapter and Central Unit Expansion CU-E sub-module Connector X20 RJ45, 8 pins Interface acc. to ANSI/IEEE 802.3, 1996 Edition 9.4.7 EMC The unit meets the EMC requirements defined in ETS 300 386-2.
PAGE 335
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDH Expansion Module SCU 9.5 SDH Expansion Module SCU 9.5.1 STM-1 interface 155 Mbit/s Laser class Laser Class 1 STM-1 interface Optical acc. to ITU-T G.957 and G.958 Transmission rate 155 520 kbit/s Code Binary NRZ (optical interface) Interfaces on the SCU module max. 2 Connector type LC (SFP module) Application class acc. to G.957: S1.1 L1.1 L1.
PAGE 336
XMP1 Release 5.5 System Description STM-4 interface 622 Mbit/s optical FCD 901 48 Issue R2A, 07.2009 9.5.3 STM-4 interface 622 Mbit/s optical Laser class 1 Laser class STM-4 interface acc. to ITU-T G.957 and G.958 Transmission rate 622 080 kbit/s Code binary NRZ (optical interface) Interfaces on the SCU module max. 2 Connector type LC (SFP module) Application class acc. to G.957: S4.1 L4.1 L4.
PAGE 337
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Interfaces on EoSCU module 9.6 Interfaces on EoSCU module 9.6.1 STM-1/4 interfaces See also Section 9.5, SDH Expansion Module SCU . 9.6.2 Ethernet interfaces Number of interfaces 4 9.6.2.1 100Base TX electrical RX+, RX-; TD+, TD- acc. to IEEE 802.3-2002 Insertion loss (1 to 100 MHz), typ. 0.6 dB Reflection loss 1 to 30 MHz: 16 dB 30 to 100 MHz: 10 dB Auto MDIX yes Connector type RJ45 Coverage range 100 m 9.6.2.2 STM-1 S1.
PAGE 338
XMP1 Release 5.5 System Description E1 interfaces FCD 901 48 Issue R2A, 07.2009 Spectral width FWHM Receiver Maximum optical input power (BER <10-10) – 14 dBm 9.6.3 E1 interfaces Interface features acc. to ITU-T G.703 Impedance, switchable 120 Ohms real (bal.), 75 Ohms coaxial (unbal.
PAGE 339
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Port Interfaces Table 9.E: Port interfaces 9.7 Port Interfaces 9.7.1 2 Mbit/s interfaces (ports) 9.7.1.1 2 Mbit/s equipment interface (HDB3 port) Interface characteristics to ITU-T G.703 Impedance 120 Ohms resistive (bal.) or 75 Ohms coaxial (unbal.) Bit rate 2,048  5 x 10-5 kbit/s Period duration T0 488 ns Signal code HDB3 Tx signal shape at F1out approx.
PAGE 340
XMP1 Release 5.5 System Description Port LE2 OPT U FCD 901 48 Issue R2A, 07.2009 Table 9.E: Port interfaces Optical 2 Mbit/s equipment interfaces 2F module; 2 Mbit/s optical line interface F1 62.7026.570.
PAGE 341
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Port LE2 OPT U Table 9.E: Port interfaces 2F module; 2 Mbit/s optical line interface F1, 62.7026.540.00-A001 1300 nm Laser class Laser class 1 Transmission path Fiber-optic cable Single-mode fiber 10/125m, Multimode fiber 50/125m separate for F1in/F1out Bit rate (2048 2x10-5) kbit/s Baud rate 4096 kBaud Signal code MCMI or MCMI inverted Transmit signal shape Rectangle Wavelength 1270 nm to 1340 nm Extinction factor < 0.
PAGE 342
XMP1 Release 5.5 System Description 34 Mbit/s interfaces FCD 901 48 Issue R2A, 07.2009 Table 9.
PAGE 343
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description MUX34 KX port Table 9.F: 34 Mbit/s interfaces 9.7.2.1 MUX34 KX port General version to ITU-T G.703.8 Transmission bit rate (34,368  2  10-5) kbit/s Interface code HDB3 Transmit signal pulse shape bipolar, approx. rectangular Impedance at F1in, F1out 75 , resistive Interface level UP0 1.
PAGE 344
XMP1 Release 5.5 System Description Port LE34OPT KX DK FCD 901 48 Issue R2A, 07.2009 Table 9.F: 34 Mbit/s interfaces 9.7.2.3 Port LE34OPT KX DK F1 interface 34GF optical Laser class Laser class 1 Transmission bit rate (34,368  2 * 10-5 ) kbit/s Line code MCMI (1B/2B) Wavelength 1,285 nm to 1,330 nm Baud rate 68,736 kBauds Transmitter characteristics Transmit signal pulse shape NRZ Optical transmit element Low-power single-mode laser Optical transmit power PS –10 dBm 0.
PAGE 345
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Port nx64 Table 9.F: 34 Mbit/s interfaces Cable Balanced conductor pair Table 9.G: Port nx64 9.7.2.4 Port nx64 General Data bit rate N x 64 kbit/s, where N=1 to 31 64, 128, 192 . . . . 1984 kbit/s Transmission of control line In 64 kbit/s channel or in service digits of PCM frame V.11 interface data Interface definition to ITU-T X.21 Electrical characteristics to ITU-T X.27/V.
PAGE 346
XMP1 Release 5.5 System Description Port nx64 FCD 901 48 Issue R2A, 07.2009 Table 9.G: Port nx64 V.35 interface data Interface definition ITU-T V.35 Electrical characteristics of control and signalling ITU-T V.28 Plug connector 25-pin (female) trapezoidal connector (DÜE) Voltages for clock lines and logic states of data lines Logic "1" - 0.55 V  20% Logic "0" + 0.55 V ± 20% Electrical interface V.28 Source voltage approx.
PAGE 347
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Port LAN Table 9.H: Port LAN 9.7.2.5 Port LAN The Port LAN module (62.7026.360.00-A001/A002) permits remote LAN networks based on Ethernet (IEEE 802.3) to be connected via the XMP1 system. Number of Ethernet channels Module A001: 2 Module A002: 1 Bandwidth 64 kbit/s. . . 1984 kbit/s Interface 10BaseT Frame structure acc. to IEEE 802.
PAGE 348
XMP1 Release 5.5 System Description KZU Channel Modules FCD 901 48 Issue R2A, 07.2009 Table 9.I: KZU channel modules 9.8 KZU Channel Modules 9.8.1 KZU OSX Number of interface on the module 4, configurable as SUB, EX, OB, OBG Transmission range for 10dB signal attenuation with 0.4 mm wire: 6.6 km (19.8 km 600 Ohms with addional amplifier) with 0.6 mm wire: 12.5 km (37.5 km 600 Ohms with additional amplifier) with 0.8 mm wire: 16.7 km (50.1 km 600 Ohms with additional amplifier) Impedance: Nom.
PAGE 349
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description KZU SUB (8) Table 9.I: KZU channel modules 4-wire 600 Ohms 1) 2-wire 600 Ohms 2-wire complex +6.7 dBm . . . –17.4 dBm +7.5 dBm . . . –16.7 dBm +5.1 dBm . . . –17.4 dBm 1) The module is designed so that an additional attenuation of 6 dB can be provided for each channel.
PAGE 350
XMP1 Release 5.5 System Description KZU EX (8) FCD 901 48 Issue R2A, 07.2009 Table 9.I: KZU channel modules Number of interface on the module 8 9.8.4 KZU EX (8) For 2-wire connections of CB subscribers to PBXs in conjunction with the KZU SUB channel module. The receivers for feeding current, ringing signals and meter pulses are integrated on the interface. VF band 300 to 3400 Hz Interface 2-wire, to exchange Transmit direction (from exchange) with balancing network: 600 Ohms: -8.0 dB to +7.
PAGE 351
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description DSK Modular Table 9.J: DSK Modular 9.9 DSK Modular Basic board for equipment with four modules (appropriate for V.24, V.11, V.35, WT and G.703 modules) 9.9.1 Mechanical dimensions DSK-Modular basic board 170 mm x 256 mm V.11, V.24, V.35, G.703 and WT modules 125 mm x 55 mm 9.9.
PAGE 352
XMP1 Release 5.5 System Description V.11 module FCD 901 48 Issue R2A, 07.2009 Table 9.J: DSK Modular Cable length: 104 103 1) Cable length in meters 2) 2 10 101 103 104 105 106 107 Transmission rate [bit/s] 1): Terminated interface line 2): Interface lines not terminated Asynchronous transmission Data rate 0 to 19.2 kbit/s, transparent Oversampling possible at 8 kHz, 16 kHz, 32 kHz and 64 kHz Control signals only with 64 kHz sampling rate Signal distortion  25 % without R.111, with R.
PAGE 353
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description V.24 module Table 9.J: DSK Modular Asynchronous (transparent) with oversampling Data rate 0 to 1200 bit/s as 8 kbit/s stream acc. to V.110 (sampling rate: 4800 Hz) up to 2400 bit/s as 16 kbit/s stream acc. to V.110 (sampling rate: 9600 Hz) up to 4800 bit/s as 32 kbit/s stream acc. to V.110 (sampling rate: 19200 Hz) up to 9600 bit/s as 64 kbit/s stream acc. to V.110 sampling rate: 48 kHz) Signal distortion  25 % without R.111, with R.
PAGE 354
XMP1 Release 5.5 System Description V.35 module FCD 901 48 Issue R2A, 07.2009 Table 9.J: DSK Modular Transmission with frame structure acc. to ITU-T V.110 synchr. (full-duplex) Synchronous (full-duplex) Synchronous (full-duplex) 600 bit/s 1200 bit/s 2400 bit/s 4800 bit/s as 8 kbit/s stream acc. to V.110 9600 bit/s as 16 kbit/s stream acc. to V.110 19200 bit/s as 32 kbit/s steam acc. to V.110 Data rate Transmission with frame structure acc. to ITU-T V.110 asynchr.
PAGE 355
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description V.35 module Table 9.J: DSK Modular  25 % without R.111, with R.111  6.25 % Signal distortion Transmission with frame structure acc. to ITU-T V.110 Synchronous (full-duplex) Data rate 600 bit/s 1200 bit/s 2400 bit/s 4800 bit/s as 8 kbit/s stream acc. to V.110 9600 bit/s as 16 kbit/s stream acc. to V.110 19200 bit/s as 32 kbit/s stream acc. to V.110 48 kbit/s as 64 kbit/s stream acc. to V.110 Signal distortion  25 % without R.
PAGE 356
XMP1 Release 5.5 System Description G.703 module, codirectional FCD 901 48 Issue R2A, 07.2009 Table 9.J: DSK Modular 9.9.6 G.703 module, codirectional Interface data Number of interfaces per module 2 Data lines in compliance with ITU-T G.703 Line port D2 4-wire, balanced Impedance 120 Ohms, resistive Reflection loss at 15 kHz to 150 kHz >16 dB Signal code pseudo-ternary Bit rate 64 kbit/s Baud rate 256 kBauds Pulse shape of the Tx signal at D2out approx.
PAGE 357
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description WT module Table 9.J: DSK Modular 9.9.8 WT module Interface data Number of interfaces per module 2 Data rate Asynchronous 0 to 9.6 kbit/s, transparent with 64 kHz oversampling Data rate up to 2.
PAGE 358
XMP1 Release 5.5 System Description ISDN Channel Modules FCD 901 48 Issue R2A, 07.2009 Table 9.K: ISDN channel modules 9.10 ISDN Channel Modules 9.10.1 ISDN S0F The ISDN S0F modules (with remote power supply) are used for setting up duplex point-to-point connections between ISDN PBXs via XMP1 or as subscriber extension of a PBX. Bit rate 192 kbit/s Interface 4-wire, capable for bus operation Impedance 100  Number of interfaces on the module 4 9.10.
PAGE 359
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Sensors EMC protection signal transmission units EN 60 834-1 9.11.4 Sensors Number of sensors 16 Permissible operating voltage < 60 V Polarity any Residual voltage without detection <4V Sensor voltage with detection > 7 V, < 8.5 V Sensor supply voltage 12 V or 24 V, adjustable in common Current limiting in sensor circuit >1 mA and < 2.5 mA Max.
PAGE 360
XMP1 Release 5.5 System Description Data/Control interfaces Data1/Ctl and Data2 FCD 901 48 Issue R2A, 07.2009 Tab. 9.L: Video modules Impedance 120 Ohms balanced or 75 Ohms unbalanced Tx signal amplitude across 120 Ohms 3 Vpp acc. to G.703 - Cable length at a level of 6 dB 100 m Tx signal amplitude across 75 Ohms 2.37 Vpp acc. to G.703 - Cable length at a level of 6 dB 20 m Clock signals internally recovered from the XMP1 system Connectors 9-pin SUB-D (front side) with M3 pin 9.12.
PAGE 361
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description SDSL Line Equipment Tab. 9.M: SDSL Line Equipment 9.13 SDSL Line Equipment 9.13.1 ISHDSL module 9.13.1.1 SDSL interface Interfaces per module 4 Standards ETS TS 101 524 and ITU-T G.991.2 Annex B The following interface modes are supported: 4 x 1 pair SHDSL (3..32 channels or unstructured) 2 x 1 pair SHDSL to (2x 2Mbit/s) 1 x 1 pair SHDSL to (2x 2Mbit/s) + 2 x 1 pair SHDSL (3..
PAGE 362
XMP1 Release 5.5 System Description Interface classification acc. to EN 60950-1 FCD 901 48 Issue R2A, 07.2009 Tab. 9.M: SDSL Line Equipment Weight 396 g 9.13.1.5 Interface classification acc. to EN 60950-1 SHDSL interface (X600) TNV-3 E1 interface (X500) TNV-1 RPS (X601) TNV-3 9.13.1.6 Environmental conditions Operation acc. ETS 300 019 Class 3.2 Transport acc. ETS 300 019 Class 2.1 Storage acc. ETS 300 019 Class 1.1 Operating altitude max. 3000 m 9.13.1.
PAGE 363
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description RPS-XMP1 Remote Power supply module 9.13.2 RPS-XMP1 Remote Power supply module 9.13.2.1 Output voltages Output FSP 1, FSP 2, FSP 3 and FSP 4 Nominal voltage [V] -116 Tolerance range [%] 3 Nominal load [A] 0.09 Pin tied to ground + 9.13.2.2 Remote supply ranges Wires used No. of Repeater Coverage range with  0.9 mm Coverage range with 1.2 mm Coverage range with 1.4 mm 1 DA 1 19.
PAGE 364
XMP1 Release 5.5 System Description Safety FCD 901 48 Issue R2A, 07.2009 9.13.2.7 Safety Safety of information technology equipment EN 60950-1 9.13.2.8 Environmental conditions Operation acc. ETSI EN 300 019-1-3 Environment Class 3.2 in the XMP1 system Storage acc. ETSI EN 300 019-1-1 Environment Class 1.1 Transport acc. ETSI EN 300 019-1-2 Environment Class 2.1 Table 9.N: Power supply 9.14 Power supply 9.14.
PAGE 365
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1-SL Table 9.O: XMP1-SL 9.15 XMP1-SL 9.15.1 Mechanical dimensions Length x width x Height [mm] 450 x 300 x 55 Weight approx. 3.55 kg Operating altitude 3000 m Card slot for one XMP1 Module Card slots 2 card slots (internal) for DSK Modules 9.15.2 Environmental data 9.15.2.1 Climate Storage acc. ETS 300 019 Class 1.2 Transport acc. ETS 300 019 Class 2.1, 2.3 with specific packaging Operation acc. ETS 300 019 Class 3.
PAGE 366
XMP1 Release 5.5 System Description Clock interfaces FCD 901 48 Issue R2A, 07.2009 Table 9.O: XMP1-SL Grounding Plus- or minus pole, preferably plus pole External automatic circuit breaker At each ungrounded pole of the power supply, the XMP1-SL supply voltage must be protected by an external automatic circuit breaker of up to 6 A T (slow-blow). 9.15.5 Clock interfaces 9-pin SubD, male Connector type 9.15.5.1 2048 kHz, T3 Frequency 2048 kHz Signal shape acc. ITU-T G.
PAGE 367
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description XMP1 modules Table 9.O: XMP1-SL 9.15.8 XMP1 modules 2 MBIT/S PORTS Port (4), with 4 HDB3 interfaces, 120 Ohms and 62.7026.350.00-A001 75 Ohms AN00059056 Port (2), with 2 HDB3 interfaces, 120 Ohms and 62.7026.353.00-A001 75 Ohms AN00059057 Port Nx64k with V.11 interface 62.7040.340.00-A001 AN00218363 Port Nx64k with V.11/V.35 interfaces 62.7040.340.00-A002 AN00224736 Port LE2 OPT U 62.7026.530.
PAGE 368
XMP1 Release 5.5 System Description XMP1 modules FCD 901 48 Issue R2A, 07.2009 Table 9.O: XMP1-SL -Module G.703, two G.703 interfaces 62.7040.420.00-A001 AN00098228 -Module WT, two WT interfaces 62.7040.425.00-A001 AN00099104 -Module G.703 contradirectional, two G.703 interfaces 62.7040.435.00-A001 AN00227950 ISDN INTERFACE MODULES: ISDN S0F, with remote power supply and four interfaces 62.7040.610.00-A001 AN00102511 ISDN UK0F (Q), with remote power supply and 62.7040.670.
PAGE 369
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Planning Values - Power Supply/Thermal Loss 9.16 Planning Values - Power Supply/Thermal Loss Legend: * withdrawn modules Table 9.P: Planning values for power supply and thermal loss of modules SHORT DESIGNATION MODULE TYPE THERMAL LOSS IN WATT POWER SOURCE/ A POWER SINK / A –UB +7V –8 V –UB +7V –8 V POWER SUPPLY MODULES 60V Power supply II 48/60 V 15.0 3.5 7 4 - - - 60V * Power supply 48/60 V 12.0 3.0 5.0 2.
PAGE 370
XMP1 Release 5.5 System Description Planning Values - Power Supply/Thermal Loss FCD 901 48 Issue R2A, 07.2009 Table 9.P: Planning values for power supply and thermal loss of modules SHORT DESIGNATION MODULE TYPE THERMAL LOSS IN WATT POWER SOURCE/ A POWER SINK / A –UB +7V –8 V –UB +7V –8 V LE2 * Port LE CU (2) 2.5 - - - - 0.3 - LE4 * Port LE CU (4) 2.5 - - - - 0.3 - LEU * LE, unframed (4) 2.5 - - - - 0.3 - PDK * Port DK (4) 2.5 - - - - 0.
PAGE 371
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.5 System Description Planning Values - Power Supply/Thermal Loss Table 9.P: Planning values for power supply and thermal loss of modules SHORT DESIGNATION MODULE TYPE THERMAL LOSS IN WATT POWER SOURCE/ A POWER SINK / A –UB +7V –8 V –UB +7V –8 V 6/8 + 6/8 KZU TELEBRAS 5.5 - - - - 0.35 0.35 2WR * 2WR KZU TELEBRAS 6.0 - - - - 0.4 0.4 E&M * E&M KZU 4.6 - - - - 0.25 0.35 FEK * FEK KZU 5.5 - - - - 0.35 0.
PAGE 372
XMP1 Release 5.5 System Description Planning Values - Power Supply/Thermal Loss FCD 901 48 Issue R2A, 07.2009 Table 9.P: Planning values for power supply and thermal loss of modules SHORT DESIGNATION MODULE TYPE THERMAL LOSS IN WATT POWER SOURCE/ A POWER SINK / A –UB +7V –8 V –UB +7V –8 V VEX * DSK V24/V28ext 3.0 - - - - 0.3 - V35 * DSK V.35 4.0 - - - - 0.4 - ISDN CHANNEL MODULES S0F S0F (4) with FSP 8.0 - - - 0.42 0.25 - UQF UK0 (Q) (4) with FSP 10.0 - - - 0.
PAGE 373
FCD 901 48 Issue R2A, 07.2009 XMP1 Release 5.
PAGE 374
XMP1 Release 5.