TUDA1 User Manual - TelecomParts.ru · User Manual TUDA1 © KEYMILE December 2015 EN/LZTBU 372...

User Manual

TUDA1tuda1_r2e

TDM data interfaces

XMC20

XMC20TUDA1 User Manual

Copyright and Confidentiality Copyright in this document vests in KEYMILE. This document contains confi-dential information which is the property of KEYMILE. It must be held in con-fidence by the recipient and may not be used for any purposes except those specifically authorised by contract or otherwise in writing by KEYMILE. This document may not be copied in whole or in part, or any of its contents dis-closed by the recipient to any third party, without the prior written agreement of KEYMILE.

Disclaimer KEYMILE has taken reasonable care in compiling this document, however KEYMILE accepts no liability whatsoever for any error or omission in the information contained herein and gives no other warranty or undertaking as to its accuracy.

KEYMILE reserves the right to amend this document at any time without prior notice.

Document PEC EN/LZTBU 372 123/2 RB

Document release XMC20 R4C/R6B | 11 December 2015

Published by KEYMILE

http://www.keymile.com

User ManualTUDA1

page 3 of 177© KEYMILE December 2015 EN/LZTBU 372 123/2 RB

Content

1 Preface 7

1.1 Precautions and Safety 7

1.2 Symbols and Notations 7

1.3 Interfaces and Circuit Categories 7

1.4 Document History 8

1.5 Target Audience 8

1.6 Definition of Terms 8

2 Introduction 9

2.1 General 9

2.2 Unit View 11

2.3 Block Diagram 12

3 Functions and Specifications 13

3.1 Feature Licences 13

3.2 Summary of Standards 14

3.3 DCE functions and Specifications 16

3.4 DCE physical Layers 20

3.5 MAC Bridging 24

3.6 General Functions and Specifications 25

4 Installation 27

4.1 Prerequisites 27

4.2 Slots and Deployment Scenarios for the TUDA1 Unit 28

4.3 Interoperability and Compatibility 29

4.4 Connections and Cables 32

5 Functional Description 38

5.1 Data Interface Functions 38

User ManualTUDA1


5.2 Network Applications 48

5.3 Conferencing 53

5.4 Data Handling 62

5.5 Control Signal Handling 67

5.6 Timing Handling 83

5.7 Protection 88

6 Commissioning 95

6.1 Profiles 95

6.2 Commissioning of a DCE Interface 97

6.3 Commissioning of a Conference 101

7 Operation 105

7.1 Unit optical Indicators 105

7.2 Loops 106

7.3 DCE Interface Line State Maintenance 109

7.4 DTE send and idle Time Restrictions 111

7.5 Maintenance 113

8 User Interface Reference 116

8.1 Introduction 116

8.2 Profiles 118

8.3 AP: / unit-x: TUDA1 120

8.4 AP: / unit-x / port-y, y = 1 … 4 129

8.5 AP: / unit-x / port-y, y = 5 152

8.6 AP: / unit-x / conf-z 163

8.7 AP: / unit-x / conf-z / part-a 165

9 Annex 176

9.1 Associated XMC20 Documents 176

9.2 Technical Support 177

9.3 Product Training 177

User ManualTUDA1


Figures

Figure 1: DTEs connected in a star network, with conference 9

Figure 2: TUDA1 unit view 11

Figure 3: TUDA1 functional block diagram 12

Figure 4: XMC25 subrack with 19 TUDA1 units and 1 STM14 unit 28

Figure 5: XMC23 subrack with 6 TUDA1 units and 1 SELI8 unit 28

Figure 6: Front view of the front panel connectors 33

Figure 7: Side view of the XMC25 cable tray and cables 37

Figure 8: RS485 2-wire and 4-wire modes 40

Figure 9: RS485 2-wire receive data driver control 41

Figure 10: Oversampling when DTE delivers a clock signal 45

Figure 11: Oversampling when DTE delivers no clock signal 45

Figure 12: WAN encapsulation 46

Figure 13: WAN encapsulation 46

Figure 14: Point-to-point application with TUDA1 48

Figure 15: Point-to-multipoint linear application with TUDA1 49

Figure 16: Point-to-multipoint star application with TUDA1 50

Figure 17: Multipoint-to-multipoint linear application with TUDA1 51

Figure 18: Multipoint-to-multipoint star application with TUDA1 52

Figure 19: Conference resource usage example with 4 conferences 55

Figure 20: PBUS resource usage example with 4 conferences 57

Figure 21: Local conference on TUDA1 59

Figure 22: Conference in the P2MP application 59

Figure 23: Conference in the MP2MP application 60

Figure 24: Data transport 62

Figure 25: Conference data transport, MP2MP 64

Figure 26: Conference data transport, P2MP 65

Figure 27: Control signal handling overview 68

Figure 28: Control signal status to SA, SB and S mapping 70

Figure 29: Frame alignment status to X mapping 72

Figure 30: Control signal status to a-bit and b-bit mapping 73

Figure 31: Control signal transport 74

Figure 32: Conference control signal transport, MP2MP 78

Figure 33: Conference control signal transport, P2MP 80

Figure 34: Codirectional timing 83

Figure 35: Contradirectional timing 83

Figure 36: Port timing signals 85

Figure 37: Transmit timing 86

Figure 38: Unidirectional 1+1 protection 89

Figure 39: 1+1 equipment protection 93

Figure 40: Fault indication LEDs on the TUDA1 unit 105

Figure 41: Loops 2b, 3b and 3c 106

Figure 42: Loop 2b 107

Figure 43: Loop 3b 107

Figure 44: Loop 3c 108

User ManualTUDA1


Figure 45: Send time and idle time supervision 112

Figure 46: MOM (managed object model) of the TUDA1 unit 116

User ManualTUDA1

page 7 of 177© KEYMILE December 2015 EN/LZTBU 372 123/2 RB177

Preface

1 Preface

1.1 Precautions and Safety

Before you handle any equipment you must comply with the safety advices.

Adherence to the safety instructions ensures compliance with the safety requirements as defined in EN 60950 (Safety of Information Technology Equipment).

Please refer to the following document:

[202] Safety Instructions “Precautions and safety”.

1.2 Symbols and Notations

This User Manual uses the following symbols:

Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.

→ Possible actions are given.

Please note:

Shows significant information.

→ Possible actions are given.

1.3 Interfaces and Circuit Categories

Table 1: Electrical interfaces and circuit categories

TUDA1 interface Circuit category according to EN 60950-1

Max. rating

Voltage Current

Local power supply TNV2 < 72 VDC < 0.2 A

V.35 / Appendix II SELV < 1 V < 10 mA

V.35 / V.28 SELV < 25 V < 100 mA

X.24 / V.11 TNV1 < 6 V < 150 mA

V.24 / V.28 SELV < 25 V < 100 mA

RS485 TNV1 < 6 V < 200 mA

Ethernet SELV < 3 V < 10 mA

User ManualTUDA1


Preface

1.4 Document History

1.5 Target Audience

This User Manual is targeted at persons who are entrusted with the installa-tion, provisioning, operation and administration of the system.

The persons targeted are

• the installation personnel, and/or

• the provisioning personnel, and/or

• the operation and administration personnel

Please note:

Only trained and skilled personnel (maintenance staff as per EN 60950) may install and maintain the system.

1.6 Definition of Terms

Table 2: Document history

KEYMILE PEC Date XMC20 Release

Changes since previous version

LZTBU 372 123/2 RB November 2015 R6B Revision for the XMC20 system releases R4C and R6B

LZTBU 372 123/2 RA March 2015 R6A Revision for the XMC20 system release R6A

LZTBU 372 123/1 RA February 2015 R4C First revision for the XMC20 system release R4C

Table 3: Specific terms

Term Explanation

Receive direction Direction from the DCE interface (TUDA1) towards the DTE

Transmit direction Direction from the DTE towards the DCE interface (TUDA1)

(DCE)DTE

receive

transmit TUDA1

User ManualTUDA1


Introduction

2 Introduction

2.1 General

This document describes the architecture and functions of the TUDA1 unit and shows, how this unit is commissioned and operated as part of the XMC20.

The TUDA1 unit is a 1-slot wide service unit of XMC20. It supports four data interfaces and one Ethernet bridge port.

Each data interface is independently configurable as DCE interface type

• V.24/V.28,

• V.35 (Appendix II),

• X.24/V.11, or

• RS485.

The DCE interfaces support the following transmission modes:

• Asynchronous mode for subrates from 0.6 kbit/s to 38.4 kbit/s.

• Synchronous mode for subrates from 0.6 kbit/s to 56 kbit/s.

• Synchronous mode for nx64 data rates from 1x64 kbit/s to 31x64 kbit/s.

• Oversampling mode for data rates from 0 kbit/s to 600 kbit/s.

The synchronous nx64 transmission modes provide the codirectional or con-tradirectional timing operation.

The Ethernet bridge port is implemented as 10BASE-T/100BASE-TX inter-face according to IEEE Std. 802.3-2002.

Beside the data access TUDA1 offers the possibility to establish data confer-ences with participants from the TUDA1 unit or any data circuit available in the XMC20.

Figure 1: DTEs connected in a star network, with conference

The TUDA1 unit as a XMC20 TDM unit provides PBUS (XMC20 TDM bus) access.

P12 transport unit

TDMNetwork

data data

TDMNetwork

data

DTE

DTE

DTE

XMC20 XMC20

TUDA1

Data Confer-ence

TUDA1

TUDA1

XMC20

User ManualTUDA1


Introduction

TUDA1 has an access capacity of 32 x 2 Mbit/s towards the XMC20 internal cross connection backplane, PBUS, allowing access of the four data user ports, the Ethernet bridge port and of up to 212 data conferences with up to 848 participants in total.

The following network features will help to enhance the systems availability:

• 1+1 linear trail protection switching.

• 1+1 linear subnetwork connection protection switching.

A more economical use of the network resources can be achieved by the features like:

• Point-to-multipoint linear networks (P2MP)

• Multipoint-to-multipoint linear networks (MP2MP)

The multipoint networks are using the data conferences.

TUDA1 is connected to a TDM transport unit as e.g. a STM14 unit via the PBUS in the backplane of XMC20.

User ManualTUDA1


Introduction

2.2 Unit View

Figure 2: TUDA1 unit view

Figure 2 "TUDA1 unit view" shows the TUDA1 unit hardware. On the front plate are two LEDs for the unit- and traffic failure indication. The connectors for the four data interfaces are of type Metral ® with 4x6 male contacts.

The Ethernet interface uses a standard RJ-45 connector.

User ManualTUDA1


Introduction

2.3 Block Diagram

Figure 3: TUDA1 functional block diagram

Host processor

Bac

kpla

ne a

cces

s

Power

Subrack internal

communication

Fro

nt C

onne

ctor

s

DCE interface- X.24/V.11- V.35- V.24/V.28- RS485

Ethernet interface

4

1

4 x P12

27 x P12

Subrate< 64 kbit /s

nx64 kbit/s- CAS time slot- 1+1 protection

Conferencing- 1+1 protection

CrossConnect

CrossConnect

2

3

nx64 kbit/s- 1+1 protection

1 x P12CrossConnect

PB

US

Acc

ess

PB

US

Acc

ess

PB

US

Acc

ess

User ManualTUDA1


Functions and Specifications

3 Functions and Specifications

The TUDA1 unit provides the following functions and conforms to the corre-sponding standards and recommendations (conformance to applicable parts of the standards).

3.1 Feature Licences

This unit is subject to one or several feature licences. The following licences are available for this unit.

For more information on feature licences please refer to [012] Release Note “XMC20” and to [915] Technical Bulletin “Feature Licences for XMC20”.

Table 4: Feature licences relevant for this unit

Licence ID Short Description Description

FL_Topt Lic TUDA1 options Feature Licence for 1+1 linear trail protection, (Multi-) Point-to-Multipoint operation with linear and centralized data conferenc-ing in various topologies, with TUDA1 - right to use per card.

User ManualTUDA1



3.2 Summary of Standards

Table 5: Standards

Feature Standard

Data transport - ETSI EN 300 417-5-1 V1.2.1, 2001-10Transmission and Multiplexing (TM); Generic requirements of transport functionality of equip-ment; Part 5-1: Plesiochronous Digital Hierarchy (PDH) path layer functions

- ETSI EN 300 417-2-1 V1.2.1, 2001-10Transmission and Multiplexing (TM); Generic requirements of transport functionality of equip-ment; Part 2-2: Synchronous Digital Hierarchy (SDH) and Plesiochronous Digital Hierarchy (PDH) physical section layer functions

- ETSI EN 300 417-1-1 V1.2.1, 2001-10Transmission and Multiplexing (TM); Generic requirements of transport functionality of equip-ment; Part 1-1: Generic processes and perfor-mance

r1a

- ITU-T I.460, 02/99Multiplexing, rate adaptation and support of exist-ing interfaces

- ITU-T V.14, 03/93Transmission of start-stop characters over syn-chronous bearer channels

- ITU-T V.110, 02/2000Support by an ISDN of data terminal equipments with V-Series type interfaces

ITU-T X.30, 03/93Support of X.21, X.21bis and X.20bis based Data Terminal Equipments (DTEs) by an Integrated Ser-vices Digital Network (ISDN)

r2e

User ManualTUDA1



Data interfaces - ITU-T V.11, X.27, 10/96Electrical characteristics for balanced double-cur-rent interchange circuits operating at data signal-ing rates up to 10 Mbit/s

- ITU-T V.24, 02/2000List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-ter-minating equipment (DCE)

- ITU-T V.28, 03/93Electrical characteristics for unbalanced double-current interchange circuits

- ITU-T V.35, 10/84Data transmission at 48 kilobits per second using 60-108 kHz group band circuits

- ITU-T X.21, 09/92Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchro-nous operation on public data networks

- ITU-T X.21bis, 11/88Use on public data networks of Data Terminal Equipment (DTE) which is designed for interfacing to synchronous V series modems

- ITU-T X.24, 11/88List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) on public data net-works

- TIA/EIA-485-A, 1998Electrical characteristics of generators and receiv-ers for use in balanced digital multipoint systems

r1a

- ITU-T X.20, 11/88Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for start-stop transmission services on public data net-works

- ITU-T X.20bis, 11/88Use on public data networks of Data Terminal Equipment (DTE) which is designed for interfacing to asynchronous duplex V-Series modems

r2e

Synchronization and timing - ISO/IEC 9543, 1989-04-01Information processing systems – Information exchange between systems – Synchronous trans-mission signal quality at DTE/DCE interfaces

r1a

- ISO/IEC 7480, 1991-12-15Information technology – Telecommunications and information exchange between systems – Start-stop transmission signal quality at DTE/DCE inter-faces

r2e

Table 5: Standards (continued)

Feature Standard

User ManualTUDA1



3.3 DCE functions and Specifications

Ethernet transport - ISO/IEC 13239Information technology -- Telecommunications and information exchange between systems -- High-level data link control (HDLC) procedures

- ANSI/IEEE Std 802.1D, 1998IEEE Standard for Information technology. Tele-communications and information exchange between systems. Local and metropolitan area networks. Common specifications Part 3: Media Access Control (MAC) Bridges

- IEEE Std 802.3-2002IEEE Standard for Information technology — Tele-communications and information exchange between systems — Local and metropolitan area networks — Specific requirements Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications

r2a

Ethernet management - RFC1493Definitions of Managed Objects for Bridges

- RFC2131Dynamic Host Configuration Protocol

- RFC2132Dynamic Host Configuration Protocol

- RFC2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions

- RFC3396Encoding Long Options in the Dynamic Host Con-figuration Protocol (DHCPv4)

- RFC3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4

- RFC3942Reclassifying Dynamic Host Configuration Proto-col version 4 (DHCPv4) Options

r2a

Performance parameters and limits - ITU-T G.826, 12/2002End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections

r1a

Maintenance functions - ITU-T V.54, 11/88Loop test devices for modems

- ITU-T X.150, 11/88Principles of maintenance testing for public data networks using Data Terminal Equipment (DTE) and Data Circuit terminating Equipment (DCE) test loops

r1a

Table 5: Standards (continued)

Feature Standard

User ManualTUDA1



Table 6: DCE functions and specifications

Feature Rating or standard Release

Number of available DCE interfaces 4 r1a

Type of interfaces individually selectable by the configuration manage-ment:X.24/V.11V.24/V.28V.35RS485 4-wireRS485 2-wire

User data rates of < 64 kbit/s synchronous0.6 to 56 kbit/s (X.30 or V.110)

Note: With 0.6 kbit/s according to V.110, only the 40 ms frame is supported.With 56 kbit/s a frame according to table 7b/V.110 or 7c/V.110 can be used. The alternative structure (table 7c/V.110) offers additional timing and control information.

r2e

User data rates of < 64 kbit/s asynchronous0.6 to 38.4 kbit/s (X.30 or V.110)

Note: Bit rates below 600 bit/s and between the offered standard bit rates can be transported using oversampling.

r2e

Selection between X.30 and V.110 framing according to the selected DCE interface type:X.24/V.11 → X.30V.24/V.28 → V.110V.35 → V.110

r2e

User data rates of nx64 kbit/s synchronousnx64 kbit/s, n = 1 to 31, without CASnx64 kbit/s, n = 1 to 30, with use of CAS for control signal transport

r1a

Synchronization r1a

- DCE interface synchronous mode Synchronized to the network element (NE) timing source.With X.24/V.11, V.24/V.28 and V.35 type interfaces:Contradirectional or codirectional timing

- DCE interface asynchronous mode Asynchronous subrate DCE signals adjusted to the network element (NE) timing source by manipulat-ing the stop bits.

r2e

DCE output jitter, < 64 kbit/s, synchronous (data, control and timing signals)

in accordance with ISO 9543 r2e

- jitter peak to peak S, 114, 115 ≤ 30%

- duty cycle of S, 114, 115 50 ± 10%

- timing displacement of the receive data and control signals (peak) in relation to S, 115 (OFF to ON)

≤ 20%

User ManualTUDA1



DCE output jitter, < 64 kbit/s, asynchronous(data signals)


- minimum duration of any start or data or parity signal element

≥ 60%

- average character interval (CI), averaged over 2 char-acters

≥ CI - 20% UI

- minimum character interval (CI) ≥ CI - 40% UI

DCE output jitter, nx64 kbit/s r1a

- Intrinsic jitter peak-peak on the clock signals ≤ 50 ns in the frequency range of 20 Hz to 100 kHz

- timing accuracy better than 50 ppm peak

DCE output jitter, nx64 kbit/s(data, control and timing signals)

in accordance with ISO 9543 r1a

- jitter peak-peak S, 114, 115 ≤ 30%

- duty cycle S, 114, 115 50 ± 10%

DCE jitter tolerance, < 64 kbit/s, synchronous(data, control and timing signals)


- jitter peak-peak X, 113 (ON to OFF) ≤ 1%

- duty cycle X, 113 50 ± 10%

- timing displacement of the transmit data and control signals (peak, codirectional timing) in relation to X, 113 (ON to OFF)

≤ 45%

- timing displacement of the transmit data and control signals (peak, contradirectional timing) in relation to 114 (OFF to ON)

≤ 30%

DCE jitter tolerance, < 64 kbit/s, asynchronous(data signals)

in accordance with ISO 7480. r2e

- minimum duration of any start or data or parity signal element

≥ 90%

- average character interval (CI), averaged over 2 char-acters

≥ CI - 8% UI

- minimum character interval (CI) ≥ CI - 16% UI

DCE jitter tolerance, nx64 kbit/s(data, control and timing signals)

in accordance with ISO 9543 r1a

- jitter peak-peak X, 113 (ON to OFF) ≤ 1%

- duty cycle X, 113 50 ± 10%

- timing displacement of the transmit data and control signals (peak, codirectional timing) in relation to X, 113 (ON to OFF)

≤ 45%

- timing displacement of the transmit data and control signals (peak, contradirectional timing) in relation to S, 114 (OFF to ON)

≤ 30%

DCE to DCE transfer delay Maximum one way transfer delay from DCE inter-face to DCE interface excluding any network delays

r1a

Table 6: DCE functions and specifications (continued)


User ManualTUDA1



- < 64 kbit/s, synchronous maximum one way transfer delay from DCE inter-face to DCE interface excluding any network delays600 bit/s:≤ 60 ms1200 bit/s:≤ 25 ms2400 bit/s:≤ 15 ms4800 bit/s:≤ 8 ms9600 bit/s:≤ 4 ms19200 bit/s:≤ 1.9 ms38400 bit/s:≤ 1.4 ms48000 bit/s:≤ 1.2 ms56000 bit/s:≤ 1.2 ms

r2e

- < 64 kbit/s, asynchronous maximum transfer delay from DCE interface to DCE interface excluding any network delays600 bit/s:≤ 60 ms1200 bit/s:≤ 25 ms2400 bit/s:≤ 15 ms4800 bit/s:≤ 8 ms9600 bit/s:≤ 4 ms19200 bit/s:≤ 2.5 ms38400 bit/s:≤ 1.4 ms

r2e

- nx64 kbit/s, contradirectional timing ≤ 600 μs with fixed transmit timing.≤ 600 μs + 250/n μs with phase adaptive transmit timing

r1a

- nx64 kbit/s, codirectional timing ≤ 600 μs + 250/n μs r1a

Table 6: DCE functions and specifications (continued)


User ManualTUDA1



3.4 DCE physical Layers

Table 7: V.24/V.28 DCE physical layer functions and specifications


Interface circuits V.24(unused circuits are kept in the OFF state)

- 102GNDsignal ground or common return- 103TxDtransmitted data - 104RxDreceived data- 105RTSrequest to send- 106CTSready for sending- 107DSRdata set ready - 108DTRdata terminal ready- 109DCDdata channel rec. line sig. det.- 113TTtransmitter signal element timing- 114STtransmitter signal element timing- 115RTreceiver signal element timing- 141LLlocal loopback - 142TM test indicator

r1a

- Signal direction to DCE circuits 103, 105, 108, 113, 141

- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142

Electrical characteristics r1a

- circuits 103, 105, 108, 113 and 141 as receivers according to V.28

- circuits 104, 106, 107, 109, 114, 115 and 142 as trans-mitters

according to V.28

Polarities r1a

- 103, 104 = 0- 103, 104 = 1

- UA> 3 V(system logic: level low)

- UA< -3 V(system logic: level high)

- all other circuits = ON- all other circuits = OFF



User data rates available nx64 kbit/s synchronous, n = 1 to 2nx64 kbit/s oversampling, n = 1 to 30, with CASnx64 kbit/s oversampling, n = 1 to 31, without CAS

r1a

< 64 kbit/s synchronous≤ 38.4 kbit/s asynchronous

r2e

Maximum line length at the maximum available data rate

15 m r1a

Table 8: X.24/V.11 DCE physical layer functions and specifications


Interface circuits X.24(unused circuits are kept in the OFF state)

- Gsignal ground or common return)- Ttransmit- Rreceive- Ccontrol- Iindication- Ssignal element timing- Bbyte timing - Fframe start indication- XDTE transmit signal element timing

r1a

- Signal direction to DCE circuits T, C, X

- Signal direction from DCE circuits R, I, S, B, F

User ManualTUDA1




- Circuits T, C and X as receivers- Equivalent terminating resistor

according to V.11 (X.27)125 Ω ± 10%.

- Circuits R, I, S, B and F as transmitters according to V.11 (X.27)

Polarities r1a

- R, T = 0- R, T = 1

- UA-UB≥ 0.3 V(system logic: level low)

- UA-UB≤ -0.3 V(system logic: level high)

- C, I, S, B, F, X = ON- C, I, S, B, F, X = OFF

- UA-UB≥ 0.3 V(system logic: level low)

- UA-UB≤ -0.3 V(system logic: level high)

User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CASnx64 kbit/s synchronous, n = 1 to 31, without CASnx64 kbit/s oversampling, n = 1 to 30, with CASnx64 kbit/s oversampling, n = 1 to 31, without CAS

r1a


r2e


15 m with contradirectional timing50 m with codirectional timing

r1a

Table 8: X.24/V.11 DCE physical layer functions and specifications (continued)


Table 9: V.35 DCE physical layer functions and specifications


Interface circuits V.35(unused circuits are kept in the OFF state)

- 102GNDsignal ground or common return- 103TxDtransmitted data - 104RxDreceived data- 105RTSrequest to send- 106CTSready for sending- 107DSRdata set ready- 108DTRdata terminal ready- 109DTRdata terminal ready- 113TTtransmitter signal element timing.- 114STtransmitter signal element timing- 115RTreceiver signal element timing- 141LLlocal loopback - 142TMtest indicator

Note: The signal list is according to ITU-T V.36, i.e. the signals 113, 141 and 142 are added to the sig-nal list of V.35. The signal 108 has been added from the V.24 signal list.

r1a

- Signal direction to DCE circuits 103, 105, 108, 113, 141

- Signal direction from DCE circuits 104, 106, 107, 109, 114, 115, 142


- Circuits 103 and 113 as receivers according to V.35

- Circuits 105, 108 and 141 as receivers according to V.28

- Circuits 104, 114 and 115 as transmitters according to V.35

- Circuits 106, 107, 109 and 142 as transmitters according to V.28

User ManualTUDA1



Polarities r1a

- 103, 104 = 0: - 103, 104 = 1:

- UA-UB> 0 V(system logic: level low)

- UA-UB< 0 V(system logic: level high)

- 113, 114, 115 = ON: - 113, 114, 115 = OFF:

- UA-UB> 0 V(system logic: level low)

- UA-UB< 0 V(system logic: level high)

- all other circuits = ON:- all other circuits = OFF:



User data rates available nx64 kbit/s synchronous, n = 1 to 30, with CASnx64 kbit/s synchronous, n = 1 to 31, without CASnx64 kbit/s oversampling, n = 1 to 30, with CASnx64 kbit/s oversampling, n = 1 to 31, without CAS

r1a


r2e


15 m with contradirectional timing50 m with codirectional timing20 m if V.28 signals are used

r1a

Table 9: V.35 DCE physical layer functions and specifications (continued)


Table 10: RS485 DCE physical layer functions and specifications


Interface circuits RS485 4-wire(unused circuits are kept in the OFF state)

- 102GNDsignal ground or common return- 103TxDtransmitted data - 104RxDreceived data

The signal 103 acts as a single receiver with multi-ple drivers (DTEs).The signal 104 acts as a single driver with multiple receivers (DTEs).

Note: The signals 103 and 104 shall not be con-nected together outside TUDA1.

r1a

Interface circuits RS485 2-wire(unused circuits are kept in the OFF state)

- 102GNDsignal ground or common return- 103/104TxD/RxD transmitted/received data

The signal 103 acts as a single receiver with multi-ple drivers (DTEs).The signal 104 acts as a single driver with multiple receivers (DTEs).

r1a

- Signal direction to DCE circuits 103

- Signal direction from DCE circuits 104


- Circuit 103 as receivers- Bus terminating resistor of the circuit 103

according to RS485125 Ω ± 10%

Note: It is assumed, that a second bus terminating resistor with the same value as above is placed at the end of the bus cables.

- Circuit 104 as transmitters according to RS485

User ManualTUDA1



Polarities r1a

- 103, 104 = 0: - 103, 104 = 1:

- UA-UB> 0.2 V(system logic: level low)

- UA-UB< -0.2 V(system logic: level high)

User data rates available 0 to 600 kbit/s in oversampling modenx64 kbit/s oversampling, n = 1 to 30, with CASnx64 kbit/s oversampling, n = 1 to 31, without CAS

r1a


50 m r1a

Table 10: RS485 DCE physical layer functions and specifications (continued)


User ManualTUDA1



3.5 MAC Bridging

Table 11: MAC bridging functions and specifications


Ethernet ports r2a

- Number of Ethernet ports 1electrical

- Interface type 10BASE-T/100BASE-TX

- Interface mode Auto - MDI/MDI-X

- Electrical connection Connector RJ-45Impedance 100 ± 15 Ω for the frequency band from 1 to 100 MHz

Ethernet traffic layers r2a

- Ethernet modes - 10BASE-T half duplex- 10BASE-T full duplex- 100BASE-TX half duplex- 100BASE-TX full duplex- Autonegotiation

- Bridging Transparent MAC bridging according to IEEE 802.1D, using one bridge instance.Note: The spanning tree protocol is not supported.

- Packet forwarding Packets are forwarded from the LAN to the WAN port and vice versa, i.e. between the Ethernet inter-faces and the P0-nc channel.Packets that can not be forwarded are discarded:- filtered according to the information in the bridge

hash table.- lack of system resources

- MAC learning Dynamic MAC address table, 4000 entries.

- Frame format IEEE Std. 802.3-2005

- Frame size up to 1600 Bytes

- Ingress buffer sizes (towards TDM port) 4x 64 frames

- Egress buffer size (towards Ethernet port) 128 frames

- Number of ingress queues 4

- Number of egress queues 1

- Support of profiles for the ingress queue mapping

- Throughput over P0-31c, frame size 64 to 1’518 bytes 1.9 Mbit/s r2a

WAN protocols r2a

- HDLC HDLC is used as logical link control protocol as underlying layer of the MAC frames.

User ManualTUDA1



3.6 General Functions and Specifications

Table 12: General functions and specifications


Front connectors data interface Metral ®4x6 male contacts

r1a

Front connector Ethernet interface RJ-45 r1a

No hardware settable options on the unit All unit parameters are software settable with the element manager

r1a

Hot swapping You can replace a TUDA1 unit without interfering with any other units. No actions on powering, con-figuration or commissioning need to be taken if you remove/replace a TUDA1 unit

r1a

PBUS access 32 x P12 r1a

Cross connections Flexible cross connections to any other XMC20 TDM unit on the P0_nc traffic layer

r1a

Conferences Logical addition of the data signals:- Wired-ANDLogical addition of the CAS signalling signals:- Wired-AND

r1a

- Conference type Multipoint-to-multipoint,Point-to-multipoint

Conferences nx64 kbit/s r1a

- Maximum number of conferences per unit 212 with up to 4 participants, 1x64 kbit/s106 with up to 8 participants, 1x64 kbit/s53 with up to 16 participants, 1x64 kbit/s

- Maximum number of participants per conference 16, 1 … 31x64 kbit/s

- Maximum bandwidth per participant 31x64 kbit/s

- Maximum bandwidth per conference 496x64 kbit/s

- Maximum bandwidth per unit 848x64 kbit/s

Conferences subrate In addition to the nx64 kbit/s conferences r2e

- Maximum number of conferences per unit 3 with up to 4 participants1 with up to 8 participants1 with up to 12 participants

- Maximum number of participants per conference 12

Equipment protection r1a

- Switching type 1:1 equipment protection

- Protection mode non revertive

- Switching time 1 conference:< 6 s with removal of the active unit< 1 s with manual or forced switching212 conferences:< 60 s

User ManualTUDA1



Traffic protection r1a

- Linear trail protection 1+1 unidirectional, revertive1+1 unidirectional, non revertive

- SNC/I protection 1+1 unidirectional, revertive1+1 unidirectional, non revertive

- Switching time < 50 ms

Performance monitoring G.826 parametersOctet slipsProtection switchover events

r1a

MIB-2 statistics r2a

Alarm reporting ITU-T X.733 (1992)Information technology – open systems intercon-nection – systems management: Alarm reporting function

r1a

Maintenance r1a

- Test pattern insertion Per user port and conference participant

- Out of service Per user port and conference participant

Loops Data and signalling r1a

- Loop 2b Remote loop, back-to-back

- Loop 3b Local loop, front-to-front

- Loop 3c Local loop, front-to-front

Power consumption r1a

- Power supply range VBAT refer to [201] System Description “XMC20”

- Maximum current consumption, IVBATVBAT = -48 V

115 mA

- Maximum total power requirement from battery, PTOTVBAT = nominal voltage

5.5 W

Mechanical parameters r1a

- Construction practice 19 inch

- Height of unit (1 HU = 44.45 mm) 6 HU

- Width of unit (1 TE = 5.08 mm) 4 TE (1 slot)

- Size of the PCB (H x D) 233 mm x 220 mm

- Weight 400 grams

- RoHS Directive 2002/95/EC of the European Parliament and of the Council of 27.1.2003 on the Restriction of the use of certain hazardous substances in elec-trical and electronic equipment

- WEEE Directive 2002/96/EC of the European Parliament and of the Council of 27.1.2003 on waste electrical and electronic equipment

Reliability r1a

- Calculated MTTF at 35 °C (MIL-HDBK-217F) 77 years

Emission refer to [201] System Description “XMC20” r1a

Immunity refer to [201] System Description “XMC20” r1a

Safety refer to [201] System Description “XMC20” r1a

Ambient conditions refer to [201] System Description “XMC20” r1a

Table 12: General functions and specifications (continued)


User ManualTUDA1


Installation

4 Installation

4.1 Prerequisites

Before installing a TUDA1 unit take care to follow the safety advice as listed in [202] Safety Instructions “Precautions and safety”.

Valid combinations of hardware (HW) and embedded software (ESW) ver-sions are given in [012] Release Note “XMC20”.

For the installation of XMC20 HWrefer to [301] User Guide “XMC25 Installation”, orrefer to [310] User Guide “XMC23 Installation”, orrefer to [322] User Guide “XMC22 Installation”.

Please note:

The XMC22 subrack is not available in the system release R4C.

User ManualTUDA1


Installation

4.2 Slots and Deployment Scenarios for the TUDA1 Unit

The TUDA1 unit uses one slot in the XMC20 subrack.

In a XMC20, the TUDA1 unit can be operated in any of the following slots:

• XMC25: 1 … 10, 12 … 21.

• XMC23: 7 … 10, 12 … 14.

• XMC22: 9 … 10, 12.

Slot 11 is reserved for the working COGE5 unit.

In maximum 20 TUDA1 units (without network connection) can be operated in a XMC25. The number of TUDA1 units is reduced when using TDM trans-port units as connection to the TDM network.

Figure 4: XMC25 subrack with 19 TUDA1 units and 1 STM14 unit

The example above shows a XMC25 subrack equipped with 19 TUDA1 units, i.e. 76 user data ports, which can be transported over a number of 2 Mbit/s links over the TDM network.

Figure 5: XMC23 subrack with 6 TUDA1 units and 1 SELI8 unit

The example above shows a XMC23 subrack equipped with 6 TUDA1 units, i.e. 24 user data ports, which can be transported over a number of 2 Mbit/s Pseudo Wires through a packet network to another TDM network.

n x 2 Mbit /s

Slot1

Slot11

Slot21

TDMNetwork

XMC25

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

STM14

COGE5

n x 2 Mbit /s

Slot7

Slot11

Slot14

TDMNetwork

XMC23

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

TUDA1

COGE5

SELI8

User ManualTUDA1


Installation

4.3 Interoperability and Compatibility

4.3.1 XMC20 Units

The deployment of a TUDA1 unit in XMC20 is compatible with any other XMC20 unit.

4.3.1.1 Interoperability of TUDA1 configured as DCE

4.3.1.2 Interoperability of TUDA1 configured as MAC bridge

Table 13: Interoperability with SDSL8 + DTM, SDSL8 + DTU

Interworking Criteria Units to interwork with TUDA1

SDSL8 + DTM SDSL8 + DTU

DCE interfaces X.24/V.11 Yes (X.21) Yes (X.21)

V.35 Yes Yes

V.24/ V.28 Yes (n ≤ 2) No

RS485 No a

a. Interoperability is possible if the remote side DCE interface is not RS485.

No a

Interface rates n x 64 kbit/s Yes (n ≤ 31) Yes (n ≤ 31)

Subrates Yes No

Networkfunctions

SNCP/I Yes (n ≤ 31) Yes (n ≤ 31)

LTP No No

Point to multipoint No b

b. It is possible to connect a DTE attached to a SDSL8 port to a TUDA1 conference.

No b

Control signal trans-port 105 → 109

Yes No

Control signal trans-port 108 → 107

No No

Table 14: Interoperability with ETAG1, SDSL8 + DTM, SDSL8 + DTU

Interworking Criteria

Units to interwork with TUDA1

ETAG1 SDSL8 + DTM SDSL8 + DTU

LAN-WAN bridge HDLC

Supported Supported Supported

WAN-WAN bridge Supported Not supported Not supported

Maximum frame length

1500 1600 1600

WAN interface nx64 kbit/s

n ≤ 31 n ≤ 31 n ≤ 31

User ManualTUDA1


Installation

4.3.2 UMUX Units

4.3.2.1 Interoperability of TUDA1 configured as DCE

4.3.2.2 Interoperability of TUDA1 configured as MAC bridge

Table 15: Interoperability with DATAx, UNIDA, SULIC + NTU, STICx + DTM or DTU


DATAx UNIDA431 - 438

SULIC + NTU STICx + DTM STICx + DTU

DCE interfaces X.24/V.11 DATAS, DATAT, DATA1, DATA5

433/436/438 Yes Yes (X.21) Yes (X.21)

V.35 DATAS, DATAV, DATA3, DATA5

432/437 Yes Yes Yes

V.24/ V.28 DATAS, DATAR, DATA4, DATA5

431 Yes (n ≤ 2) Yes (n ≤ 2) No

RS485 DATAS, DATA5 No a No a No a No a

Interface rates n x 64 kbit/s Yes (n ≤ 31) Yes (n ≤ 31) Yes (n ≤ 2) Yes (n ≤ 31) Yes (n ≤ 31)

Subrates Yes Yes Yes Yes No

Networkfunctions

SNCP/I DATAS, DATAR, DATAT, DATAV

431, 432/437, 433/436

Yes (n ≤ 2) Yes (n ≤ 31) Yes (n ≤ 31)

LTP DATAS, DATAR, DATAT, DATAV

431, 432/437, 433/436

Yes (n ≤ 2) No No

Point to multi-point

DATAS, DATAR, DATAT, DATAV

431, 432/437, 433/436

Yes (n ≤ 2) Yes (n ≤ 31) Yes (n ≤ 31)

Control signal transport 105 → 109

Yes Yes Yes b Yes No

Control signal transport 108 → 107

Yes b Yes b Yes b No No

a. Interoperability is possible if the remote side DCE interface is not RS485.b. Control signal transport is available for subrates only.

Table 16: Interoperability with DATAx, ETER1, LAWA4, LEMU6, STICx + DTM or DTU


DATAx ETER1 LAWA4, LEMU6

STICx + DTM STICx + DTU

LAN-WAN bridge HDLC Supported Supported Not supported Supported Supported

WAN-WAN bridge Not supported Supported Supported Not supported Not supported

Maximum frame length 1600 1500 1500 1600 1600

WAN interface nx64 kbit/s n ≤ 31 n ≤ 31 n ≤ 31 n ≤ 31 n ≤ 31

User ManualTUDA1


Installation

4.3.3 Previous ESW Revisions

The TUDA1 unit with ESW release tuda1_r2e was first released for the XMC20 system release R4C. The ESW is compatible with the XMC20 sys-tem releases R6A and R6B.

User ManualTUDA1


Installation

4.4 Connections and Cables

4.4.1 Connectors and Signals

The TUDA1 unit provides individual connectors for each of the five front interfaces. The four DCE interface connectors use a 24 pin Metral connector, the Ethernet interface uses a RJ-45 connector.

The pin assignment of the five front panel connectors is shown in Figure 6 "Front view of the front panel connectors" and in Table 17 below.

The Ethernet interface connector exhibits 2 LEDs indicating the status of the Ethernet connection:

• Upper LED (yellow): Blinking when a packet is received (activity LED).

• Lower LED (green): Steady light when the link is up and running (link LED).

There is no difference in the indications if the link is half or full duplex or if the link speed is 10BASE-T or 100BASE-TX.

User ManualTUDA1


Installation

Figure 6: Front view of the front panel connectors

Please note:

The connectors of port-1 to port-5 are tilted by 39°.

The pin assignment of the DCE connector is dependent of the configured interface type:

Connectors port -1 to port -4untiltet front view

A B C D

1

2

3

4

5

6

Notch for the cable latching clip

R1A

37900358

port -1

port -2

port -3

port -4

port -5

pin 1

pin 8

Connector port -5untiltet front view

TU

Table 17: DCE interface connectors

Pin X.24/V.11 V.35 V.24/V.28 RS485

A1

A2 103a a

User ManualTUDA1


Installation

The pin assignment of the Ethernet connector is as follows:

4.4.2 DCE Cables

For each interface type, cables are available which provide the adaptation of the universal unit connector to the dedicated interface type connector:

Since no DCE connector is standardized for RS485 only the unterminated cable, i.e. without connector, is offered for the RS485 interface type.

A3 103b a

A4 Ta 103a 103

A5 Tb 103b

A6 Ground Ground Ground Ground

B1 141 141

B2 X/B/Fa 113a 113

B3 X/B/Fb 113b

B4 Ra 104a 104 104a b

B5 Rb 104b 104b b

B6 Ground Ground Ground Ground

C1 Ca 105 105

C2 Cb

C3 Ia 109 109

C4 Ib

C5 114a 114

C6 114b

D1 107 107

D2 108 108

D3 106 106

D4 142 142

D5 Sa 115a 115

D6 Sb 115b

a. In the RS485 2-wire mode this pin is used for transmit and receive.b. In the RS485 2-wire mode this pin is not used.

Table 18: Ethernet interface connector

Pin MDI MDI-X

1 Tx+ Rx+

2 Tx- Rx-

3 Rx+ Tx+

4 - -

5 - -

6 Rx- Tx-

7 - -

8 - -

Table 17: DCE interface connectors (continued)

Pin X.24/V.11 V.35 V.24/V.28 RS485

User ManualTUDA1


Installation

Cables are also offered without the dedicated interface connector, i.e. unter-minated.

For details on TUDA1 cables, please refer to [506] User Manual “XMC20 cables”.

Please note:

The latching clips of the unit side connectors must be positioned to the left side to insert the connector correctly.

4.4.2.1 Cable for X.24/V.11 interfaces

• Terminated cableA terminated cable is used to connect the X.24/V.11 data interface to the DTE. The DCE end of the X.24/V.11 cable uses a 15-pole D-sub female connector, according to ISO 4903.

• Unterminated cableAn open ended or unterminated cable with 8 pairs is used to connect the X.24/V.11 data interface to the MDF or can be equipped with a customer specific connector.

4.4.2.2 Cable for V.35 interfaces

• Terminated cableA terminated cable is used to connect the V.35 data interface to the DTE. The DCE end of the V.35 cable uses a 34-pole female connector, accord-ing to ISO 2593.

Please note:

The signal list of the V.35 interface is according to ITU-T V.36, i.e. the sig-nals 113, 141 and 142 are added to the signal list of V.35. The circuit 108 has been added from the V.24 signal list.

• Unterminated cableAn open ended or unterminated cable with 12 pairs is used to connect every pin of the data interface connector to the MDF or can be equipped with a customer specific connector.

4.4.2.3 Cable for V.24/V.28 interfaces

• Terminated cableA terminated cable is used to connect the V.24/V.28 data interface to the DTE. The DCE end of the X.24/V.11 cable uses a 25-pole D-sub female connector, according to ISO 2110.


User ManualTUDA1


Installation

4.4.2.4 Cable for RS485 interfaces

• Unterminated cableAn unterminated cable with 4 pairs is used to connect the RS485 data interface to the MDF or can be equipped with a customer specific con-nector.

Since no DCE connector is standardized for RS485 only the unterminated cable, i.e. without connector, is offered for the RS485 interface type

It is up to the customer to attach the desired type of connector.

4.4.2.5 Cable accessing every connector pin


4.4.3 Ethernet Cables

The Ethernet interface layout is per default according to the host layout, but implements automatic crossover functionality (MDI/MDI-X), i.e. it can adapt itself automatically to work with a host or a switch. The interface therefore works with crossover and straight cables.

The following media types are supported:

Please note:

A straight Ethernet cable is available from KEYMILE.

4.4.4 Fixing the Cables to the Cable Tray

The cables must be attached to the cable tray of the XMC25 or the corre-sponding device of the XMC23 or XMC22.

The figure below shows the cable/cable tray assembly of the XMC25.

Table 19: Ethernet media types

IEEE standard Distance Media type

10BASE-T 100 m Category 3 UTP or better

100BASE-TX 100 m Category 5 UTP or better

User ManualTUDA1


Installation

Figure 7: Side view of the XMC25 cable tray and cables

Please note:

The cable route on the cable tray should follow approximately the projection of the unit slot on the cable tray.

With the XMC23 and XMC22 the cable tray functionality is implemented dif-ferently and depends on the type of installation (rack-, wall-mounted).

For more information on fixing the cables with the XMC23 or XMC22 refer to [310] User Guide “XMC23 Installation” or refer to [322] User Guide “XMC22 Installation”.

Interface type

LengthNumber

Interface type

LengthNum

ber

Interface type

LengthNumber

285 mm

Interface typeLengthNumber



205 mm

175 mm

235 mm


265 mm

Interface type

LengthNumber

User ManualTUDA1


Functional Description

5 Functional Description

This chapter gives the detailed functional description of the TUDA1 unit in the XMC20 subrack.

5.1 Data Interface Functions

5.1.1 DCE Interfaces

Each data port of the TUDA1 unit is individually configurable to one of the following DCE interface types:

• X.24 / V.11

• V.35

• V.24 / V.28

• RS485 4-wire

• RS485 2-wire

The following data, control and timing signals are available, depending of the interface type and the transmission mode:

Table 20: Data, control and timing signals with their electrical characteristics a

Signal descriptionX.24 / V.24

Signal type

Signal direction

DCE interface typesynchronous

DCE interface typeasynchronous or oversampling

X.24/V.11

V.35 b V.24/V.28

RS485 X.24/V.11

V.35 b V.24/V.28

RS485

Signal ground or common return

- - G-

102-

102-

- G-

102-

102-

102-

Transmit / Transmitted data

Data to DCE

T(V.11)

103(V.35)

103(V.28)

- T(V.11)

103(V.35)

103(V.28)

103(RS485)

Receive / Received data Data from DCE

R(V.11)

104(V.35)

104(V.28)

- R(V.11)

104(V.35)

104(V.28)

104(RS485)

Control / Request to send Control to DCE

C(V.11)

105(V.28)

105(V.28)

- C(V.11)

105(V.28)

105(V.28)

-

- / Ready for sending Control from DCE

- 106(V.28)

106(V.28)

- - 106(V.28)

106(V.28)

-

- / Data set ready Control from DCE

- 107(V.28)

107(V.28)

- - 107(V.28)

107(V.28)

-

- / Data set to line Control to DCE

- 108(V.28)

108(V.28)

- - 108(V.28)

108(V.28)

-

Indication / Data channel received line signal detec-tor

Control from DCE

I(V.11)

109(V.28)

109(V.28)

- I(V.11)

109(V.28)

109(V.28)

-

User ManualTUDA1




The byte and frame timing signals should only be used with user signals with a bit rate ≤ 4x64 kbit/s. With higher user data rates the probability of timing problems is increased.

Please note:

The transmit data or timing signals can not be used to synchronize the net-work element.

The following table shows which functions are available in which combina-tions:

DTE transmit signal ele-ment timing / Transmitter signal element timing (DTE)

Timing to DCE

X c, d

(V.11)113 d

(V.35)113 d

(V.28)- - - - -

Signal element timing / Transmitter signal element timing (DCE)

Timing from DCE

S(V.11)

114(V.35)

114(V.28)

- - - - -

Signal element timing / Receiver signal element timing (DCE)

Timing from DCE

S(V.11)

115(V.35)

115(V.28)

- - - - -

Byte timing, Frame start identification / Transmitted character timing

Timing from DCE

B/F c, e

(V.11)- - - - - - -

- / Local loopback Control to DCE

- 141(V.28)

141(V.28)

- - 141(V.28)

141(V.28)

-

- / Test indicator Control from DCE

- 142(V.28)

142(V.28)

- - 142(V.28)

142(V.28)

-

a. Table entries in brackets designate the electrical interface characteristics.b. The signal list of the V.35 interface is according to ITU-T V.36, i.e. the signals 113, 141 and 142 are added to the signal

list of V.35. The circuit 108/1 has been added from the V.24 signal list.c. Only one of the X.24 signals X, B and F can be used at the same time since they all use the same connector pin.d. Not available with subratese. With subrates only B is available.

Table 20: Data, control and timing signals with their electrical characteristics a (continued)

Signal descriptionX.24 / V.24

Signal type

Signal direction

DCE interface typesynchronous

DCE interface typeasynchronous or oversampling

X.24/V.11

V.35 b V.24/V.28

RS485 X.24/V.11

V.35 b V.24/V.28

RS485

Table 21: Function relationship

Transmission mode

User data rate[kbit/s]

Timing signal [kHz]

Transport mode

DCE interface type

V.35X.24/V.11

V.24/V.28 RS485

Asynchronous 0.6 … 38.4 0.6 … 38.4 Subrate yes yes no

Synchronous 0.6 … 56 0.6 … 56 Subrate yes yes no

Synchronous nx64 nx64, n ≤ 2 nx64 kbit/s yes yes no

Synchronous nx64 nx64, n ≤ 31 a nx64 kbit/s yes no no

Oversampling 0 … 128 nx64, n ≤ 31 a, b nx64 kbit/s yes yes yes

Oversampling 0 … 600 nx64, n ≤ 31 a, b nx64 kbit/s yes no yes

User ManualTUDA1



The V.11 and RS485 receivers are terminated with a 125 Ω resistor.

The RS485 interface can be configured to 4-wire (full duplex mode) or to 2-wire (half duplex mode). In the 4-wire mode the circuit 103 and circuit 104 must be connected to separate wire pairs. In the 2-wire mode the connector pins of the transmit interface (103) are used:

Figure 8: RS485 2-wire and 4-wire modes

5.1.2 RS485 2-wire Control

With the RS485 2-wire interface type the receive and transmit data signals share the same wire pair. Only half duplex transmission mode is allowed for the DTE and the DCE.

As a consequence the receive data driver (R/104) is active only when receive data has to be applied to the line. During the receive idle phases the receive data driver is inactive, i.e. not driving.

The TUDA1 unit offers two possibilities to control the receive data driver:

• RTS controlled mode,

• Data controlled mode.

In order to avoid flow back of receive data to the transmit direction, the trans-mit data signal in the DCE is fixed to “1” as long as the receive data driver is active.

5.1.2.1 RTS controlled mode

In the RTS controlled mode the receive data driver is kept active as long as the control signal RTS (C, 105) from the remote end is active (“0”). The receive data driver is set to inactive as long as the control signal RTS from the remote end is inactive (“1”).

The RTS (C, 105) from the remote end is transported in the CAS bit a, i.e. control signal transport with CAS must be available and enabled.

Please note:

Control signal transport via CAS bits is a KEYMILE proprietary feature.

Please note:

The data port at the remote end must be configured to interface type X.24-V.11, V.24-V.28 or V.35, since the interface type RS485 does not support the control signal interfaces.

a. With CAS enabled the timing signal is n ≤ 30.b. This signal is only used internally to sample the data signal. On the DCE interface none of the timing interchange circuits

will be activated.

Transmit 103

Receive 104

RS485 2-wire

Transmit 103

Receive 104

RS485 4 -wireTUDA1 TUDA1

User ManualTUDA1



5.1.2.2 Data controlled mode

In the data controlled mode the receive data driver is kept active as long as the data is 0 and for a configurable timer period after the 0 to 1 data transi-tion. After the expiry of the timer the receive data driver is set to inactive.

Figure 9: RS485 2-wire receive data driver control

The timer period is configurable between 20 and 1500 samples of the over-sampling clock rate. The timer has to be set at least to the duration of the maximum continuous “1” period of the data signal, during which the driver must be kept enabled.

Example:Assume a data signal structure with a maximum of 9 consecutive “1” data bits. The data signal has a data rate of 64 kbit/s, the oversampling rate is 320 kbit/s.The timer has to be set at least to 320/64 * 9 = 45 samples

Please note:

The data controlled mode requires knowledge of the data signal structure, i.e. about the maximum length of “1” periods.

5.1.3 Transport Modes

5.1.3.1 Subrate transport mode

The TUDA1 DCE ports support synchronous and asynchronous subrates, i.e. user bit rates < 64 kbit/s, according to ITU-T V.110 and ITU-T X.30.

The subrate framing format is automatically set by TUDA1 according to the interface type configuration:

• With the V.35 and V.24/V.28 type interface, the subrate framing format is according to ITU-T V.110.

• With the X.24/V.11 type interface, the subrate framing format is according to ITU-T X.30.

Please note:

The mapping of the user data to the X.30 frame is only byte synchronous if the byte timing signal B is used.

timer periodReceive data R/104

Receive data driver enabled

timer expired

Table 22: Supported subrates and framing formats

User data rate[bit/s]

Synchronous Asynchronous ITU-T V.110 ITU-T X.30

600 yes yes yes yes

User ManualTUDA1



For the transport over the TDM network the subrate data signals are mapped to a synchronous frame according to ITU-T V.110 for the V-type interfaces and according to ITU-T X.30 for the X-type interfaces. The framed subrate signals have an intermediate signalling rate expressed by 2k x 8 kbit/s, where k = 0, 1, 2 or 3.


The user data rates 600, 1’200, 2’400 and 4’800 bit/s use all the same V.110 or X.30 subrate frame format.

→ A mismatch of the user data rates configured for two connected user ports or conference participants cannot be detected.

In a second step the X.30/V.110 frame is mapped into a 64 kbit/s time slot. Depending on the user data rate 1, 2, 4 or 8 bits within the 64 kbit/s time slot are used.

Please note:

The user bit rate 1’200 bit/s with X-type interfaces cannot provide the byte timing.

1’200 yes yes yes yes a

2’400 yes yes yes yes





48’000 yes no yes yes

56’000 yes no yes yes a

a. X.30 does not specify the user bit rate 1’200 bit/s, 19’200 bit/s, 38’400 bit/s and 56’000 bit/s. Nevertheless these user bit rates can be used with the TUDA1 unit also for the X-type interfaces.

Table 22: Supported subrates and framing formats


Synchronous Asynchronous ITU-T V.110 ITU-T X.30

Table 23: User data rate and bits used within a 64 kbit/s time slot


Intermediate rate[kbit/s]

Frame length[ms]

User data bits per frame

Time slot bits used

600 8 10 / 40 a

a. In order to maintain compatibility with the X.30 / 600 bit/s user rate, E7 is set to bi-nary 0 in every fourth 80-bit frame, providing a frame length of 40 ms.

6 / 24 1

1’200 8 10 12 1

2’400 8 10 24 1

4’800 8 10 48 1

9’600 16 5 48 1 - 2

19’200 32 2.50 48 1 - 4

38’400 64 1.25 48 1 - 8

48’000 64 0.50 24 1 - 8

56’000 64 1.00 56 1 - 8

User ManualTUDA1



The X.30/V.110 frame contains overhead bits named S bits, E bits and X bit which are used to transport control signal states, the actual user data rate indication and a remote alarm indication. For further information please refer to section 5.5.2 Subrate Framing Signalling Transport (on page 69).

5.1.3.2 nx64 kbit/s transport mode

The TUDA1 DCE ports support synchronous nx64 kbit/s user data rates.

For the transport over the TDM network the nx64 kbit/s data signals are mapped to n time slots in a G.704 framed 2048 kbit/s signal.

Depending on the usage of CAS up to 30 time slots or up to 31 time slots are available for the user data transport.

5.1.4 Transmission Modes

5.1.4.1 Asynchronous transmission mode

With subrates up to 38.4 kbit/s, TUDA1 supports the asynchronous transmis-sion mode according to ITU-T V.14.

The following start-stop character formats are supported:

Please note:

The parity bit is not evaluated in TUDA1, it is transported transparently.

In transmit direction, the asynchronous user data rate is adapted to the net-work element timing (PETS) by deleting and adding stop bits. The maximum allowed frequency deviation is

• -2.5% to +1.0% with the basic range configuration, and

• -2.5% to +2.3% with the extended range configuration.

In receive direction, deleted stop bits are detected and regenerated by gen-erating eight (basic range) or four (extended range) stop bits with a reduced length.

Start-stop characters can follow each other without a gap or with a gap. Gaps are filled with stop bits.

With the asynchronous transmission mode, no timing signals (S/114/115, X/113, B, F) are available at the DCE interface.

5.1.4.2 Synchronous transmission mode

The synchronous transmission mode is supported by TUDA1 for all subrates from 0.6 kbit/s to 56 kbit/s and for the nx64 kbit/s user data rates.

In transmit direction, TUDA1 expects that the incoming user signal at the DCE interface is synchronous to the network element timing (PETS).

Table 24: Asynchronous start-stop character formats

1 start bit 7 or 8 data bits 0 or 1 parity bit 1 or 2 stop bits

User ManualTUDA1



The incoming subrate user data is mapped directly into the V.110/X.30 frame, i.e. without any bit rate adaptation. The V.110/X.30 frame occupies 1 to 8 bits in a 64 kbit/s time slot.

The incoming nx64 kbit/s user data is mapped directly to n 64 kbit/s time slots, i.e. without any bit rate adaptation.

In receive direction, the user data rate is derived from the network element timing. The data, control and clock signals are fed to the DCE interface with this user data rate.

With the interface type X.24/V.11 and subrate user data, TUDA1 supports the byte timing signal (B) at the DCE interface.

With the interface type X.24/V.11 and nx64 kbit/s user data, TUDA1 supports the byte timing (B) or frame timing (F) signal at the DCE interface.

Please note:

Since the same DCE connector pins are used for the byte timing (B), the frame timing (F) and the codirectional transmit signal element timing (X), only one of these three signals can be active at the same time.

5.1.4.3 Oversampling transmission mode

The oversampling transmission mode can be used to transport DCE signals with user data rates not corresponding to the configurable subrates or nx64 kbit/s data rates. The user data signals can be asynchronous (start-stop) signals or synchronous signals.

This mode can also be used to have low and constant delays with low user data rate signals.

In transmit direction, the data and control signals at the DCE interface are oversampled with a (synchronous) clock, which is the configured clock rate. The oversampling frequency has to be at least three to four times higher than the user data rate. The resulting isochronous distortion corresponds to the relation of the user data rate to the oversampling frequency, e.g. 19.5% with a 25 kbit/s user data rate, oversampled with 2x64 kHz = 128 kHz (25/128 = 0.195).

In receive direction, the data and control signals are output at the DCE inter-face with the oversampling clock.

The oversampling transmission mode can be used in point-to-point, point-to-multipoint and multipoint-to-multipoint network applications. Refer to section 5.2 Network Applications (on page 48).

Please note:

With the V.24/V.28 interface, the data signal rate is limited to 128 kbit/s.

Please note:

In oversampling mode, no clock signal is available at the DCE interface.

If the DTE is working in synchronous mode, i.e. with clock signals, two cases must be considered:

1 The DTE delivers a clock signal (X, 113): A second DCE interface must be used to oversample and transport the clock signal to the remote DTE in parallel to the data signal. The clock signal is handled the same as a data signal.

User ManualTUDA1



Figure 10: Oversampling when DTE delivers a clock signal

2 The DTE requires a clock signal (S, 114, 115): A second DCE interface must be used to oversample and transport the clock signal to the remote DTE. A third DCE interface must be used to generate the required user clock signal.This application is limited to the configurable user data rates of TUDA1 (0.6, 1.2, 2.4 …nx64 kbit/s).

Figure 11: Oversampling when DTE delivers no clock signal

Please note:

Specifically tailored cables have to be used for the above applications.

5.1.5 MAC Bridging

5.1.5.1 LAN modes

The port-5 on the front of the TUDA1 unit is a 10BASE-T/100BASE-TX Ethernet port supporting the following LAN modes:

Transmit T/104

Receive R/103

Clock X/113

oversampling

oversampling

DTE A

Transmit T/104

Receive R/103

Clock S/115DTE B

Clock S/115 Clock X/113

TDMNetwork

TDMNetwork

TUDA1 A TUDA1 B

Transmit T/104

Receive R/103

Clock S/114/115

oversampling

oversampling

user data rate

DTE ATransmit T/104

Receive R/103

Clock S/114/115

DTE BTDM

Network

TUDA1 A TUDA1 B

User ManualTUDA1



• Auto-negotiation

• 10 Mbit/s, Half duplex

• 10 Mbit/s, Full duplex

• 100 Mbit/s, Half duplex

• 100 Mbit/s, Full duplex


The LAN mode of the host connected to the TUDA1 Ethernet port must be configured to the same PHY mode as the TUDA1 Ethernet port, e.g. both ports configured to “auto-negotiation” or both ports configured to “100 Mbit/s full duplex”.

→ Mixed configurations result in a non operational state of the Ethernet interface.

5.1.5.2 WAN mode

The Ethernet frames are mapped to a nx64 kbit/s transport signal, constitut-ing the WAN port to the TDM network.

Depending on the usage of CAS up to 30 time slots or up to 31 time slots are available for the user data transport.

The WAN port encapsulates the MAC frames from the Ethernet port into HDLC frames.

Figure 12: WAN encapsulation

5.1.5.3 Queues and priority mappings

In direction from the Ethernet port to the WAN port the TUDA1 unit offers four queues with a size of 64 frames each. The queues can be used for the priorisation of the user traffic according to the 802.1p priority (VLAN priority) or the DSCP value.

In direction from the WAN port to the Ethernet port the TUDA1 unit offers one queue with a size of 128 frames.

Figure 13: WAN encapsulation

The assignment of priorities to the four queues is controlled by a QoS map-ping profile. Please refer to section 6.1 Profiles (on page 95) for information about the profile handling and refer to section 8.2 Profiles (on page 118) for the configuration of the profile parameters.

HDLC encapsulation at the WAN port

flag flagFCSMAC frame

Q1

TDMWAN port Q4

priority to queue mapping

Q2

Q3

Q

Ethernetport

TUDA1

PB

US

User ManualTUDA1



The TUDA1 unit supports four algorithms for the priority to queue mapping:

• IPThe DSCP field of the IP header determines the packet priority.

• MACThe 802.1p priority bits of the MAC header determine the packet priority. Untagged packets get the default priority assigned. The default priority value is configurable.

• IP Then MACThe DSCP field of the IP header, if it exists, determines the packet prior-ity. Otherwise the 802.1p priority bits determine the packet priority. Untagged packets get the default priority assigned.

• MAC Then IPThe 802.1p priority bits of the MAC header, if they exist, determine the packet priority. Otherwise the DSCP field of the IP header determines the packet priority.

The scheduling of the frames in the queues towards the TDM WAN interface uses the strict priority algorithm.

Packets in the higher priority queues are handled first. Packets in lower pri-ority queues are only processed when there are no packets left in the higher priority queue. Q1 is the highest priority queue, Q4 is the lowest priority queue.

Please note:

The priority mechanism does not modify the Ethernet frames.

User ManualTUDA1



5.2 Network Applications

The main network applications with the TUDA1 unit are

• TUDA1 in a point-to-point application.

• TUDA1 in a point-to-multipoint application.

• TUDA1 in a multipoint-to-multipoint application.

5.2.1 Point-to-Point (P2P)

The point-to-point application connects one data interface (data and signal-ling) with another data interface through a TDM network.

The connection can be protected with 1+1 SNC protection on the transport layer.

Figure 14: Point-to-point application with TUDA1

5.2.2 Point-to-Multipoint (P2MP)

In the point-to-multipoint mode of operation a master data terminal equip-ment (master DTE) communicates via a data interface to several subordi-nated DTEs, the so called slave DTEs through a TDM network.

Communication is established in the polling mode. The data signal from the master DTE is sent simultaneously to all slave DTEs. The master DTE addresses one specific slave DTE. This addressed DTE activates its trans-mit interface to respond to the polling request. After the complete message transfer the slave DTE deactivates its transmit interface.

Collisions must be prevented by using suitable communication protocols between the DTEs.

The slave DTEs can be distributed across several XMC20 sites. The maxi-mum number of slave DTEs is therefore practically limited only by the com-munication protocol applied.

Using the RS485 interface type up to 32 RS485 unit loads can be connected to one TUDA1 user port simultaneously.

P12 transport unit

Network element 1 Network element 2

datainterface

datainterface

TDMNetwork

TUDA1 unit

User ManualTUDA1



Using the V.35, X.24/V.11 or V.24/V.28 interface type only one DTE can be connected to one TUDA1 user port simultaneously.

The connection in the TDM network can be protected with 1+1 SNC protec-tion on the transport layer.

The combination of the data signals and the signalling is accomplished with one central conference (preferred solution for a star network) or with several conference circuits placed at all network elements with connected slave DTEs (preferred solution for a linear network).

Please note:

The point-to-multipoint network setup supports the multi-master type network topology.

5.2.2.1 Linear network setup

The point-to-multipoint application in a linear network connects one master data interface located at one end of the linear network with several slave data interfaces through a TDM network.

When the master terminal sends, it sends in direction towards the slaves, and all slave terminals can receive the sent signal.

When a slave terminal sends, it sends in direction towards the master, and only the master can receive the sent signal.

The connection between any two network elements can be protected with 1+1 SNC protection on the transport layer

It is also possible to implement a shared protection ring (SPR) for the protec-tion of the complete TUDA1 network. For further information please refer to [314] User Guide “TDM Services and Cross Connections in XMC20”.

Figure 15: Point-to-multipoint linear application with TUDA1

Network element 1 Network element n

datainterfacemaster

datainterface

Master Intermediate slave

Network element k

Tail end slave

TDMNetwork

TDMNetwork

to master

P12 transport unit

local

datainterface

to slave

TUDA1 unit

Conference on TUDA1 unit

User ManualTUDA1



5.2.2.2 Star network setup

The point-to-multipoint application in a star network connects one master data interface with several slave data interfaces through a TDM network.

When the master terminal sends, it broadcasts towards the slaves, and all slave terminals can receive the sent signal.

When a slave terminal sends, it sends in direction towards the master, and only the master can receive the sent signal.

In case that more than one DTE is connected to a slave network element a local conference can be setup at this location. This is shown in the Figure 16 "Point-to-multipoint star application with TUDA1" below at the Slave 3 net-work element.

The connection between any two network elements can be protected with 1+1 SNC protection on the transport layer

Figure 16: Point-to-multipoint star application with TUDA1

Slave 3to master

P12 transport unit

Master to slave or local

Slave 1

Slave 2

to master

TDMNetwork

TDMNetwork

TDMNetwork

1

1

1 2

1

1

3

2

to master

to master

datainterfacemaster

datainterface

datainterface

datainterface

datainterface

to slave or local

TUDA1 unit


User ManualTUDA1



5.2.3 Multipoint-to-Multipoint (MP2MP)

The multipoint-to-multipoint mode of operation is very similar to the point-to-multipoint mode of operation. Differences are outlined below.

Please note:

The multipoint-to-multipoint network setup supports the multi-master type network topology.

5.2.3.1 Linear network setup

In the multipoint-to-multipoint application, when a slave terminal sends, it sends in direction towards the master and towards the tail end slave, and all master and slave terminals can receive the sent signal.

Please note:

At an intermediate slave in the multipoint-to-multipoint application the differ-entiation between “to master” and “to slave” is done from a protocol point of view. The conferencing is the same for all participants, irrespective if they are “local”, “to master” or “to slave”.

Figure 17: Multipoint-to-multipoint linear application with TUDA1

5.2.3.2 Star network setup

In the multipoint-to-multipoint application, when a slave terminal sends, it sends in direction towards the master and towards the locally connected slaves, and the master forwards the received signal to all other slaves. All the master and slave terminals can receive the sent signal.

Network element 1 Network element n

datainterfacemaster

datainterface

Master Intermediate slave

Network element k

Tail end slave

TDMNetwork

TDMNetwork

to master

P12 transport unit

local

datainterface

to slave

TUDA1 unit


User ManualTUDA1



Figure 18: Multipoint-to-multipoint star application with TUDA1

Slave 3to master

P12 transport unit

Master to slave or local

Slave 1

Slave 2

to master

TDMNetwork

TDMNetwork

TDMNetwork

1

1

1 2

1

1

3

2

to master

to master

datainterfacemaster

datainterface

datainterface

datainterface

datainterface

to slave or local

TUDA1 unit


User ManualTUDA1



5.3 Conferencing

5.3.1 Resources

5.3.1.1 nx64 kbit/s conference resources

The TUDA1 unit has a fixed amount of resources available for nx64 kbit/s data conferences. Each conference that is created consumes resources according to the maximum number of conference participants and to the par-ticipants bandwidth.

• The maximum number of conference participants must be configured when the conference is created. The following values are available:

− Maximum number of participants p = 4, or


− Maximum number of participants p = 16.If later on a higher number of participants is required the conference must be deleted and newly created with the appropriate maximum number of participants.

• The conference participants bandwidth must be configured when the con-ference is created. The following values are available:

− Rate = 64 kbit/s, i.e. number of time slots n = 1, to

− Rate = 1984 kbit/s, i.e. number of time slots n = 31.The conference participants bandwidth can’t be modified.

The resources consumed by a conference is calculated withRC = p x n, where

− p = number of participants

− n = number of time slots per participant

Example:A conference with 8 participants and a participant bandwidth of 6x64=384 kbit/s requires conference resources of RC = 8 x 6 = 48 time slots.

The sum of all conference resources is restricted to 848 time slots per TUDA1 unit:

RU = Σ RC ≤ 848 time slots.

The maximum number of conferences with 4 participants is C4max = 848/4 = 212.



Due to the fact that the building block for data conferences is a 16 participant conference with a bandwidth of 1 time slot, one building block can be used to create

• one conference with 16 participants, or

• two conferences with 8 participants, or

• four conferences with 4 participants.

User ManualTUDA1



The following formulas apply for the calculation of the used conference resources, where np is the number of time slots used in conferences with p participants:

• Number of conferences with 4 participants = C4 = Σ n4 + Σ 2xn8 + Σ 4xn16

• Number of conferences with 8 participants = C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16

• Number of conferences with 16 participants = C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16

Example:Assume four conferences:

− conference 1 with 4 participants and 192 kbit/s (n=3),



− conference 4 with 16 participants and 1984 kbit/s (n=31),The used resources are as follows:C4 = Σ n4 + Σ 2xn8 + Σ 4xn16

= (3+10) + 2x5 + 4x31 = 147C8 = round-up (Σ n4/2) + Σ n8 + Σ 2xn16

= round-up ((3+10)/2) + 5 + 2x31 = 74C16 = round-up ((Σ n4/4) + (Σ n8/2)) + Σ n16

= round-up ((3+10)/4) + 5/2) + 31 = 37The remaining resources are as follows:C4 = 212 - 147 = 65, or

C8 = 106 - 74 = 32, or

C16 = 53 - 37 = 16.

User ManualTUDA1



Figure 19: Conference resource usage example with 4 conferences

Please note:

The remaining conference resources can be read from the TUDA1 unit sta-tus dialogue.

5.3.1.2 Subrate conference resources

In addition to the nx64 kbit/s conferences the TUDA1 unit offers subrate con-ferences. Also with subrate conferences the amount of resources available is fixed. Each conference that is created consumes resources according to the maximum number of conference participants.

• The maximum number of conference participants must be configured when the conference is created. The following values are available:



− Maximum number of participants p = 12.

conference, 4 participants, 1 time slotconference, 8 participants, 1 time slot

conference, 16 participants, 1 time slot

12345

10

15

20

25

30

35

40

45

Legend:

50

53

67

37

conference 1, 3 time slots conference 2, 10 time slots

conference 3, 5 time slots

conference 4, 31 time slots

remaining resources

building block (16 participants)

num

ber

of b

uild

ing

bloc

ks

User ManualTUDA1



If later on a higher number of participants is required the conference must be deleted and newly created with the appropriate maximum number of participants.

Please note:

The conference participants bandwidth must be configured when the confer-ence is created. The conference participants bandwidth can’t be modified.

The sum of all subrate conference participants is restricted to 12 per TUDA1 unit:

RU = Σ RC ≤ 12 participants

The following subrate conference configurations are possible:

• 1 conference with 12 participants, or

• 1 conference with 8 participants plus 1 conference with 4 participants, or

• 3 conferences with 4 participants.

Please note:

The remaining conference resources can be read from the TUDA1 unit sta-tus dialogue.

5.3.1.3 PBUS resources

The TUDA1 unit accesses the PBUS (XMC20 TDM bus) with a maximum capacity of 32 P12 signals, each having 32 time slots. Five P12 signals are reserved for the user ports and 27 P12 are reserved for the conference par-ticipants.

Each participant can only access one P12 signal, i.e. it is not possible to split the participants data signal to more than one P12 signal. This has the conse-quence that depending of the participants bandwidths not the full available PBUS bandwidth can be used.

In the example below the remaining PBUS resources are:

• 7 participants with maximum 31x64 = 1984 kbit/s,

• 1 participant with maximum 27x64 = 1728 kbit/s,

• 2 participants with maximum 4x64 = 256 kbit/s,

• 24 participants with maximum 1x64 = 64 kbit/s.

User ManualTUDA1



Figure 20: PBUS resource usage example with 4 conferences

Please note:

A P12 resource with 32 free timeslots is shown as two remaining resources:

→ 1 participant with maximum 31x64 = 1984 kbit/s, and

→ 1 participant with maximum 1x64 = 64 kbit/s.

To make best use of the available PBUS bandwidth, the resource usage strategy must be taken into account when creating conferences. The resource usage strategy is as follows:

• The P12 resources for conferences are grouped, according to the PBUS line usage. Each PBUS line multiplexes 4 P12 resources:

− group 1: P12-5 to P12-7 (only 3 P12 resources),

− group 2: P12-8 to P12-11,

− group 3: P12-12 to P12-15,

− group 4: P12-16 to P12-19,

− group 5: P12-20 to P12-23,

− group 6: P12-24 to P12-27,

− group 7: P12-28 to P12-31.

• The groups are populated with participants from group 1 to group 7. A new group is accessed when there are no remaining resources left for a participant.

• Each group is populated with participants

− first from the lowest numbered timeslot on any of the groups P12 to the highest numbered timeslot, and

− second from the groups lowest numbered P12 to the highest num-bered P12.

conference participant with 31 time slotsconference participant with 10 time slotsconference participant with 5 time slots

P12-00 31

P12-4

P12-9

P12-14

P12-19

P12-24

P12-29

Legend:

conference 4,16 participants,31 time slots,

remaining resources

P12

P12-31

TS

5 x P12 reserved for user ports




conference participant with 3 time slots

4 9 14 19 24 29

User ManualTUDA1



Example with conference 3 (8 participants, 5 timeslots):

• The group 1 is occupied with conference 1 and conference 2 as follows:

− P12-5: timeslot 0 to timeslot 15,

− P12-6: timeslot 0 to timeslot 22,

− P12-7: timeslot 0 to timeslot 12.

• Participant-1 of conference-3 is placed on timeslots 13 to 17 of P12-7.







• Participant-8 of conference-3 has to be placed in group 2 since the maxi-mum available resource in group 1 is 4 timeslots in P12-6 and P12-7. It is placed on timeslots 0 to 4 of P12-8.

Please note:

Only created participants make use of PBUS resources.

→ The parameter “maximum number of participants” of a conference does not influence the PBUS resource usage.

Please note:

The remaining PBUS resources usable for additional participants can be read from the TUDA1 unit status dialogue.

5.3.2 Local Conferences

Conferences are accessible for local participants, i.e. from TUDA1 ports or any other data unit in the network element. The conferences include also the participants from the “to master” and “to slave” direction, i.e. from other net-work elements, transported via the TDM network.

The data conference function performs the addition of the data signals. The data signals are combined with a wired-AND operation. The wired-AND requires all inactive terminals to send a continuous “1”-signal.

It is possible to control the data access of a participant to the conference by the associated C/105 control signal. Refer to section 5.3.5 Conference Con-trol (on page 60) for further information.

The control signals transported in the CAS a and b bits or in the subrate frame bits S, SA and SB of all participants are combined in a wired-AND function, i.e. if any of the participants exhibits an active state (CAS-bit = 0 or S, SA, SB bit = 0), this active state is inherited to the combined CAS signal.

User ManualTUDA1



Figure 21: Local conference on TUDA1

5.3.3 Conferences in the P2MP Application

Conferences in the point-to-multipoint application add the data and control signals of the local participants to the signal going towards the master. The Σ symbol stands for the wired-AND function.

There is no addition in the direction to the last slave or towards the local par-ticipants.

Figure 22: Conference in the P2MP application

5.3.4 Conferences in the MP2MP Application

Conferences in the multipoint-to-multipoint application consist of a number of sub-conferences. The number of sub-conferences corresponds to the num-ber of participants. The sub-conference of each participant adds the data and control signals of all participants except the own signal.

The designation “to master” or “to slave” has no relevance for the conference itself, since the setup is symmetrical in relation to the network directions. The

1+1 protection switching,cross connect

master /slave participants

local participants

AND

Data

CAS

DCE interface

1

4

local participants

remote participants

local participants

conference

nx64 kbit /sprocessing

AND

CAS

Data

Subrate< 64 kbit/s

64 kbit/s

subrate

AND

Control

Data

Control

subrate

64 kbit/s

TUDA1

TUDA1

SDSL8DTU/DTM

P12 transport,e.g. SELI8

P12 transport,e.g. SELI8

PB

US

local1

Σ

to master to slave

localn

PBUS

PBUS

User ManualTUDA1



“to master” and “to slave” participants are nevertheless required for the setup of the transport cross connections.

Figure 23: Conference in the MP2MP application

5.3.5 Conference Control

In a conference all inactive participants must access the conference with a constant “1” signal state. Only the active participant is allowed to access the conference with “1” and “0” signal states.

There are two methods to have the inactive participants in the constant “1” state:

• Intrinsic access:

− In the inactive state the connected DTEs must send constantly a “1” state.

− If a slave DTE is polled from the master DTE it immediately can start to send.

• Controlled access:

− In the inactive state the connected DTEs must set the C/105 control signal to OFF. The state of the C/105 control signal must be forwarded to the conference, i.e.-the ports control signal “105 (RTS, C)” must be set to “From-DTE”,-the ports “signalling to network” parameter must be set to “Yes”,-the participants “signalling to conference” parameter must be set to “Yes”,-the participants “signalling from conference” parameter must be set to “Yes”,-the participants “conditional interconnection” parameter must be set to “Yes”.The participants data signal entering the conference is set to “1”.

− If a slave DTE is polled from the master DTE it sets the C/105 control signal to ON. The DCE (i.e. TUDA1 port) responds by setting the I/109 control signal to ON with a configurable delay. Now the DTE can start to send. The participants data signal enters the conference transpar-ently.

local1

Σ

to master

localn

Σ

Σ Σ

1 2 3 n

1

3

12

42 3

4

n

4 1 2 3 n4

3

n

2

4

to slave

PBUS

PBUS

User ManualTUDA1



To permit the master DTE to synchronize it is recommended to transmit a short bit sequence (e.g. flag stream or idle code) from the slave DTE prior to the user data.

Please note:

The controlled access of a participant to a conference is only available if CAS is available (nx64 kbit/s data rate) or if the subrate frame bits S or SB are available (subrate).


With subrates the TUDA1 at the master site has to resynchronize its V.110/X.30 frame every time a slave DCE starts its transmission (e.g. at 0.6 kbit/s it takes more than a second to synchronize). This introduces a delay, depend-ing of the user data rate and can lead to problems since during resynchroni-zation the data sent to the master DTE is undefined.

→ Use the oversampling transmission mode instead.


There is a risk with subrates that data sent from the slave DTE to the master DTE will be lost if a slave DTE switches its control signal 105/C to OFF simultaneously with the last data byte. This is due to the delay in the V.110/X.30 subrate converter.

→ Use the oversampling transmission mode instead.

Please note:

If using the control signal 109/I to enable the DTE transmitter the delay time in the TUDA1 at the slave DTE location from control signal 105/C = ON to control signal 109/I = ON must be configured to at least 20 ms when using the oversampling transmission mode. With subrate transport the delay must be correspondingly longer.

The DCE interfaces of TUDA1 are able to supervise the send time and idle time of the DTE and to detach it from the connection point if the correspond-ing limits are exceeded. This prevents that the system will be locked by a slave DTE which continuously sends data. Refer to section 7.4 DTE send and idle Time Restrictions (on page 111).

User ManualTUDA1



5.4 Data Handling

5.4.1 Port Data Handling

With each of the 4 user ports the TUDA1 unit offers a DCE interface with data, control and timing signals. The data signals are the transmit signal T/103 and the receive signal R/104.

Figure 24: Data transport

The data handling can be configured with the following control and mainte-nance mechanisms:

• Interface mode 2-wire or 4-wire:The RS485 interface type can be configured to 2-wire mode, i.e. half duplex mode of the RS485 bus, or to 4-wire mode, i.e. full duplex mode of the RS485 bus.With the 2-wire mode the squelch function inserts a “1” signal in transmit direction as long as the driver in receive direction is active.All other interface types use the full duplex mode with separate transmit and receive signals.

Please note:

The signal monitoring status on the receive data signal shows the signal sta-tus before the buffer in receive direction.

→ With the RS485 2-wire interface type and RTS controlled mode there can be activity on the data signal also when the buffer in receive direc-tion is disabled. The activity is shown in the port status “To DTE” parameters.

• Data signal inversion (transmit signal T/103 and receive signal R/104):In order to be compatible with DTEs using inverted logic, the transmit and the receive data signal can be inverted.

• Consequent action (transmit signal T/103):On a detected failure in the transmit data signal T/103 or the transmit tim-ing signal X/113, the data is replaced with a “1” or “0” signal. The conse-quent action can be disabled.On a detected send or idle time filter violation the data is replaced with a “1” signal. The consequent action can be disabled.

Data signalto

Working data signal from

Protecting data signalfrom

2-wire /4-wire

Test pattern insertion

Protection switch

Loop 2b

01

Loop 3c

R/104

Loop 2b

Loop 3c

Processing

Processing

T/103

Loop 3b

Loop 3bSignal

monitorConsequent

action

01

1001

Consequent action

01

10

01

01

10

1

Out of service

Signal inversion

Squelch

1

Signalmonitor

1

1

Out of service

1

PBUS

PBUS

PBUS

User ManualTUDA1



Please note:

The level detection on the transmit data signal T/103 is not available for the RS485 2-wire interface type.

• Loop 3c:The maintenance function “Loop 3c” loops the transmit data signal back to the receive direction. For details please refer to section 7.2.3 Loop 3c (on page 108).

• Loop 2b:The maintenance function “Loop 2b” loops the receive data signal back to the transmit direction. For details please refer to section 7.2.1 Loop 2b (on page 106).

• Loop 3b:The maintenance function “Loop 3b” loops the transmit data signal back to the receive direction. For details please refer to section 7.2.2 Loop 3b (on page 107).

• Interface line state “out of service”:The maintenance function “out of service” of an interface replaces the transmit signal going to the PBUS by a “1” signal.In receive direction the data signal from the PBUS is replaced by a “1” signal.

• Interface line state “test pattern insertion”:The maintenance function “test pattern insertion” replaces in receive direction the data signal by a continuous test pattern “1010”.

• Protection switching:In receive direction a working and a protecting channel can be config-ured. Switching criteria are “trail signal fail” and “trail signal degrade” from the P12 transport unit. With CAS enabled in the CTP configuration, CAS AIS is an additional switching criterion.

• Consequent action (receive signal R/104):On a detected failure in the receive signal the data is replaced with a “0” or “1” signal.

5.4.2 Conference Data Handling

The TUDA1 unit offers conferences with a maximum of 16 participants per nx64 kbit/s conference or a maximum of 12 participants per subrate confer-ence. The transmit data signals of all participants are combined in a wired-AND function, i.e. if any of the participants exhibits an active state (“0”), this active state is inherited to the combined data signal.

With subrates the data signals are extracted from the X.30 or V.110 frame before the addition. The combined signal is reinserted into the X.30 or V.110 frame.

With X-interface type conferences the byte and frame timing is maintained.

In the multipoint-to-multipoint (MP2MP) application, all participants are han-dled identically. Each participant has its own sub-conference. The sub-con-ference of each participant adds the data signals of all participants except the own signal.

User ManualTUDA1



Figure 25: Conference data transport, MP2MP

In the point-to-multipoint (P2MP) application, only the participant “to master” has a sub-conference, adding the data signals of all other participants except the own signal. The other participants (“local” or “to slave”) receive their data signal from the “to master” participant.

P1

ΣP2P3

Pn

Participant 1:local orto master orto slave

P2

P3

Pn




Protection switch

Set out of service

data signalto 1

P1P3

Pn

P1P2

Pn

P1P2P3

101

Conditionalinterconnection

C/105

1

0



Participant n :local orto master orto slave

Signalling to conference

1

Consequent action

1

Σ




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1

Σ




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1

Σ




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

User ManualTUDA1



Figure 26: Conference data transport, P2MP

The data handling can be configured with the following control mechanisms:

• Participant configuration “signalling to conference”:The “signalling to conference” parameter allows to control the forwarding of control signals towards the conference. This parameter influences also the forwarding of the data signal in case of the conditional interconnection (see below). If “signalling to conference” is set to “No” the “conditional interconnection” parameter set to “Yes” disables the forwarding of the data signal.

• Participant configuration “conditional interconnection”:The conditional interconnection function allows to control the access of a participants data signal to the conference by the signal state of the con-trol signal C/105, which has to be available at the conference input, i.e. the port configuration must enable the forwarding of control signals to the network (“signalling to network” = “Yes”) and the participant configuration

P1

ΣP2P3

Pn

Participant 1:to master

P2

P3

Pn




Protection switch

Set out of service

data signalto 1

P1

P1

P1

101


C/105

1

0

Participant 2:local orto slave

Participant 3:local orto slave

Participant n :local orto slave


1

Consequent action

1




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1




Protection switch

Set out of service

data signalto 1

101


C/105

1

0


1

Consequent action

1

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

PBUS

User ManualTUDA1



must enable the forwarding of control signals to the conference (“signal-ling to conference” = “Yes”.

• Participant line state “out of service”:The maintenance function “out of service” of a participant replaces the transmit signal going to the PBUS by a “1” signal.In receive direction the data signal from the PBUS is replaced by a “1” signal.

• Participant line state “test pattern insertion”:The maintenance function “test pattern insertion” replaces in receive direction the data signal by a continuous test pattern “1010”.


• Consequent action (receive direction):On a detected failure in the receive signal the data is replaced with a “1” signal.

User ManualTUDA1



5.5 Control Signal Handling

5.5.1 Overview

Depending on the interface type used different control signals are available. Refer to Table 20: "Data, control and timing signals with their electrical char-acteristics" (on page 38).

• C/105 (to DCE)In normal operation the control signal C/105 is used by the DCE as an indication that the DTE is ready to transmit data.With subrates, the state of the control signal C/105 is transported to the remote DCE in the SB bit of the V.110 frame or S bit of the X.30 frame. Alternatively the state of the control signal 105 can be transported in the SA bit and the SB bit of the V.110 frame.When using CAS the state of the control signal C/105 can be transported to the remote DCE in the CAS a bit.

• 106 (from DCE)The control signal 106 informs the DTE that it can start to send data.The state of the control signal 106 can be controlled by the local control signal 105 with various delay settings. The delay time can be configured to

− 0, 10, 20 or 40 ms.The delay is active for the OFF to ON and ON to OFF state transitions.With subrates the state of the control signal 106 can be controlled by the remote DCE via the X bit of the V.110 or X.30 frame (loss of frame syn-chronization alarm). As long as the remote DCE has no synchronization failure the control signal 106 is in the ON state and the local DTE can transmit data.

• 107 (from DCE)The control signal 107 informs the DTE that the remote DTE is in fault free operation.With subrates the state of the control signal 107 can be controlled by the remote DTE via the SA bit of the V.110 frame which transports the remote state of the control signal 108.When using CAS the state of the control signal 107 can be controlled by the remote DCE via the CAS b bit which transports the remote state of the control signal 108.

• 108 (to DCE)The control signal 108 is used to inform the DCE that the DTE is fault free and in operation.With subrates and V-type interfaces, the state of the control signal 108 can be transported to the remote DCE in the SA bit of the V.110 frame.When using CAS the state of the control signal 108 can be transported to the remote DCE in the CAS b bit.

• I/109 (from DCE)The control signal I/109 is used to ready the DTE for receiving data from the DCE.The state of the control signal I/109 can be controlled by the local control signal C/105 with various delay settings. The delay time can be config-ured to

− 0, 10, 20 or 40 ms.

User ManualTUDA1



The delay is active for the OFF to ON and ON to OFF state transitions.With subrates the state of the control signal I/109 can be controlled by the remote DCE via the SB bit of the V.110 frame or the S bit of the X.30 frame which transports the remote state of the control signal C/105.When using CAS the state of the control signal 109/I can be controlled by the remote DCE via the CAS a bit which transports the remote state of the control signal C/105.

Figure 27: Control signal handling overview

The control signals can be configured according to the table below:

DTE

C/105 from DTEON

OFF

TDMNetwork

from DTE

ONOFF

ONOFF

ONOFF

ONOFF

CAS a bit

ΔT

V.110/SB bitX.30/S bit

V.110/SA bit

V.110/SA bit

CAS a bit

V.110/SB bitX.30/S bit

V.110/X bit

108

107

I/109

106

CAS b bit

CAS b bit

TUDA1

Table 25: Control signal handling

Control signal X.24 V.35 V.24

C/105 from DTE from DTE from DTE

ON, fixed ON, fixed ON, fixed

OFF, fixed OFF, fixed OFF, fixed

OFF, from defect a OFF, from defect a OFF, from defect a

106 - from local 105 from local 105

from X bit (V.110) from X bit (V.110)

ON, fixed ON, fixed

OFF, fixed OFF, fixed

OFF, from defect b OFF, from defect b

User ManualTUDA1



Please note:

The S bit, SA bit, SB bit and X bit are only available with subrates. The 56 kbit/s user data rate must use the V.110 framing with signalling.

Please note:

The a bit and the b bit are only transmitted to the PBUS when CAS is ena-bled, i.e. when the “signalling to network” parameter is set to “yes”.

Please note:

With active loops the control signals are controlled according to the specific loop.

→ Refer to section 7.2 Loops (on page 106).

Please note:

The RS485 interface type supports no control signals.

5.5.2 Subrate Framing Signalling Transport

The X.30 and the V.110 frames contain overhead bits named S bits, E bits and X bit which are used to transport control signal states, the actual user data rate indication and a remote alarm indication.

5.5.2.1 S bit usage

S bits are used to transport the status of selected DCE interface signals from the local DCE to the remote DCE.

107 - from SA bit (V.110) from SA bit (V.110)

from b bit (CAS) from b bit (CAS)

ON, fixed ON, fixed


OFF, from defect b OFF, from defect b

108 - from DTE from DTE

ON, fixed ON, fixed


OFF, from defect a OFF, from defect a

I/109 from local C from local 105 from local 105

from S bit (X.30) from SB bit (V.110) from SB bit (V.110)

from a bit (CAS) from a bit (CAS) from a bit (CAS)

ON, fixed ON, fixed ON, fixed

OFF, fixed OFF, fixed OFF, fixed

OFF, from defect b OFF, from defect b OFF, from defect b

a. The control signal towards the network is set to OFF as a consequent action when a defect is detected in the transmit data or clock signal from the DTE.

b. The control signal is set to OFF as a consequent action when a defect is detected in the receive signal from the network and the signal is not fixed to ON.

Table 25: Control signal handling (continued)

Control signal X.24 V.35 V.24

User ManualTUDA1



In transmit direction, in a first step the status of a control signal is mapped to an SA or SB indication (V.110) or to an S indication (X.30). In a second step the SA and SB indications are mapped to the S1 to S9 (= Sx) bits in the V.110 frame or the S indication is mapped to the SP, SQ and SR bits in the X.30 frame.

In receive direction the opposite procedure is used to control the correspond-ing DCE interface signal.

For interoperability of a V-type DCE with a X-type DCE the control signal 105 can be mapped to both the SA and SB indications.

Figure 28: Control signal status to SA, SB and S mapping

The number of available Sx bits depends of the bit rate:

Table 26: Control signal status to SA, SB and S mapping

DCE signal V.110mapped to

V.110mapped from

X.30mapped to

X.30mapped from

105 SB orSB + SA

107 SA

108 SA

109 SB

C S

I S

DTEA

105

108

SB

SAV.110

SB

SAV.110 DTE

B

109

107TDM

Network

DTEA

C S X.30 SX.30 DTEB

ITDMNetwork

DTEA

105

108

SB

SAV.110 X.30TDM

Network

S DTEB

I

TUDA1 A TUDA1 B

TUDA1 A TUDA1 B

TUDA1 A TUDA1 B

Table 27: SA, SB and S to Sx mapping

SA/SB/S V.110up to 38’400 bit/s

V.11048’000 bit/s

V.11056’000 bit/s

X.30

SA S1, S3, S6, S8 S1, S3 S3

SB S4, S9 S4 S4

S SP, SQ, SR

User ManualTUDA1



The frame formats of X.30 and V.110 are compatible. The S1 to S9 bits of the V.110 frame occupy the places of the SP, SQ and SR bits of the X.30 frame.


The S bit usage of the X-type interfaces is not compatible with the V-type interfaces.

→ Use the compatibility mode with the mapping of the control signal 105 to both the SA and SB bits.

5.5.2.2 E bit usage

With the user data rates up to 38’400 bit/s, the E1 to E3 bits are used to indi-cate the local user data rate to the far end. The transport of network inde-pendent clocking information in the E-bits E4 to E6 is not supported.

With the 600 bit/s user data rate the E7 bit is always used for the multiframe alignment according to ITU-T V.110, Table 5, Note 2.

5.5.2.3 X bit usage

The X bit in the V.110 and X.30 frame is used to transport the status of the X.30/V.110 frame synchronization to the remote DCE:

− Frame synchronization OK: X bit = 0.

− Frame synchronization failed: X bit = 1.

The received X bit can control the status of the DCE signal 106.

Table 28: E bit usage

User data rate [bit/s] E1 to E3

600 100

1’200 010

2’400 110

4’800 011

9’600 011

19’200 011

38’400 011

48’000 not available

56’000 not available

User ManualTUDA1



Figure 29: Frame alignment status to X mapping

5.5.3 CAS Signalling Transport

The CAS provides the four signalling bits abcd. The bits a and b can be used to transport the control signal status from the local DCE to the remote DCE.

DTEA

X X.30 XX.30 DTEB

framealignment

TDMNetwork

DTEA

X V.110 XV.110 DTEB

106

framealignment

TDMNetwork

TUDA1 A TUDA1 B

TUDA1 A TUDA1 B

Table 29: CAS bits usage

CAS bits abcd Description

1101 CAS bits not used (idle)

1xxx Control signal transport C to I (X-type),Control signal transport 105 to 109 (V-type),signal state OFF

0xxx Control signal transport C to I (X-type),Control signal transport 105 to 109 (V-type),signal state ON

x1xx Control signal transport 108 to 107 (V-type),signal state OFF

x0xx Control signal transport 108 to 107 (V-type),signal state ON

xx01 Default value

1111 Forward alarm indication (AIS)

User ManualTUDA1



Figure 30: Control signal status to a-bit and b-bit mapping

The abcd bits of a time slot are sampled every 2 ms in the P12 transport sig-nal.

Please note:

The control information is transported in the abcd bits only with the nx64 kbit/s transport mode.

→ With subrate signals the S bit or the SA and SB bits of the X.30/V.110 frame are used instead.

5.5.4 Port Control Signal Handling

With each of the 4 DCE interfaces the TUDA1 unit offers up to 3 control sig-nal inputs and up to 4 control signal outputs, refer to Table 20: "Data, control and timing signals with their electrical characteristics" (on page 38).

DTEA

105 a bitCAS

a bitCAS DTE

B

109

TDMNetwork

DTEA

C a bit CAS a bitCAS DTEB

ITDM

Network

108 b bit b bit 107

TUDA1 A

TUDA1 A

TUDA1 B

TUDA1 B

User ManualTUDA1



Figure 31: Control signal transport

The control signal handling can be configured with the following control and maintenance mechanisms:

• Consequent action on a failure of the T/103 data signal or of the X/113 timing signal:On a detected failure in the transmit signal the control signals C/105 and 108 towards the network are set to OFF.

• Configuration in transmit direction:The incoming control signals C/105 and 108 can be replaced by a fixed ON or OFF value.

• Loop 3c:The maintenance function “Loop 3c” loops the control signal 108 back to the control signal 107 and loops the control signal C/105 back to the con-trol signal I/109. In transmit direction the control signals C/105 and 108 are set to OFF. The loop is near the DCE interface. For details please refer to section 7.2.3 Loop 3c (on page 108).

1111

Loop 2bLoop 3c

C/105

OFF

OFF

1101

ΔT

108

OFF

Test patternOut of service

Protection switchLoop 3c

107

Loop 2b Loop 3b

OFF

Consequent action

1111

142

OFF

ON

Loop 3b

OFF

OFF

V/X compa-tibility

OFF

OFFON

OFFON

OFFON

Subrate

CAS b bit

V.110/SA

CAS a bit

V.110/SBX.30/S

V.110/X

Config

I/109

106

OFF

Failure on T/103

OFF

141 Loop3c

Loop state

Configuration

OFF

OFF

OFF

OFF

OFFOFF

OFF

OFF

Out of service

Signallingto network

Configuration

OFF

ON

OFF

ON

X.30 frame, S bitV.110 frame, SB bitto PBUS

V.110 frame, SA bitto PBUS

CAS signallingto PBUS

Working data signalfrom PBUS

Protecting data signalfrom PBUS

User ManualTUDA1



• Loop 2b:If the control signals C/105 or 108 are configured to “from DTE”, the maintenance function “Loop 2b” loops the control signal I/109 received from the network back to the control signal C/105 and loops the control signal 107 received from the network back to the control signal 108. If the control signals C/105 or 108 are not configured to “from DTE”, the control signals C/105 and 108 towards the network remain unchanged.In receive direction the control signals 107, I/109 and 106 are set to OFF. The loop is near the DCE interface. For details please refer to section 7.2.1 Loop 2b (on page 106).

• Loop 3b:The maintenance function “Loop 3b” loops the control signal 108 back to the control signal 107 and loops the control signal C/105 back to the con-trol signal I/109. In transmit direction the control signals C/105 and 108 are set to OFF. The loop is near the PBUS interface. For details please refer to section 7.2.2 Loop 3b (on page 107).

• Control signal transport, transmit direction:With subrates the state of the control signal C/105 is transported to the remote DCE via the SB bit of the V.110 frame or the S bit of the X.30 frame.In order to be compatible with a remote DCE of X-type, the state of the control signal C/105 can in addition also be transported via the SA bit of the V.110 frame. This is enabled with the “V/X compatibility mode” parameter set to “Yes”.With subrates the state of the control signal 108 is transported to the remote DCE via the SA bit of the V.110 frame.If CAS is used in the nx64 kbit/s mode the state of the control signal C/105 is transported to the remote DCE via the CAS a bit and the state of the control signal 108 is transported to the remote DCE via the CAS b bit. The CAS pattern is inserted in all positions of the used time slots.The transport of signalling information towards the network can be disa-bled with the “signalling to network” parameter set to “No”:

− With subrates the SA and SB bits of the V.110 frame or the S bit of the X.30 frame are set to OFF (“1”).

− In the nx64 kbit/s mode the CAS abcd pattern is the idle pattern “1101”.

• Interface line state “out of service”, transmit and receive direction:In transmit direction the maintenance function “out of service” of an inter-face activates the TSD and TSF signals. TSF and TSD are the XMC20 internal failure signals used to control the protection switching.With subrates the complete X.30 or V.110 frame is replaced by a “1” sig-nal, i.e. the control signals C/105 and 108 in the X.30 and V.110 frame are set to OFF.If CAS is used the AIS-CAS pattern (1111) is inserted in all positions of the used time slotsIn receive direction the control signals 106, 107 and I/109 are all set to OFF.


User ManualTUDA1



• Consequent action (receive control signals):On a detected failure in the receive signal the data is replaced with a “1” or “0” signal (refer to section 5.4.1 Port Data Handling (on page 62)). The CAS is replaced with the CAS-AIS pattern. Consequently all control sig-nals are set to OFF.

• Control signal transport, receive direction:With subrates the state of the control signal I/109 can be controlled from the remote DCE via the SB bit of the V.110 frame or the S bit of the X.30 frame.With subrates the state of the control signal 107 can be controlled from the remote DCE via the SA bit of the V.110 frame.With subrates the state of the control signal 106 can be controlled from the remote DCE via the X bit of the V.110 frame, indicating a loss of the V.110 frame alignment.If CAS is used in the nx64 kbit/s mode the state of the control signal I/109 can be controlled from the remote DCE via the CAS a bit and the state of the control signal 107 can be controlled from the remote DCE via the CAS b bit. The CAS pattern of the first used time slot is evaluated.

• Interface line state “test pattern insertion”:The maintenance function “test pattern insertion” sets in receive direction the control signals 106, 107 and I/109 to OFF.

• Configuration in receive direction:The outgoing control signal 106 can be replaced by a fixed ON or OFF value.The outgoing control signal 107 can be replaced by a fixed ON or OFF value or can be controlled by the control signal 108.The outgoing control signal I/109 can be replaced by a fixed ON or OFF value or can be controlled by the control signal C/105 with a configurable delay.

Please note:

The nx64 kbit/s mode not using CAS provides no means for the transport of control signals to the remote DCE.

→ Use CAS to enable control signal transport. This is a KEYMILE propri-etary feature.

→ CAS is enabled when the configuration parameter “Signalling to net-work” is set to “Yes”

Please note:

If a port requires CAS for the control signal transport CAS must be enabled on the P12 transport signal.

→ The termination mode of the P12 transport signal must be set to “PCM30” or “PCM30C”.


It is possible to create a cross connection from a TUDA1 port using CAS to another CTP not using CAS.

→ This would result in a non operational control signal transport.

User ManualTUDA1



5.5.5 Conference Control Signal Handling

The TUDA1 unit offers conferences with a maximum of 16 participants per nx64 kbit/s conference or a maximum of 12 participants per subrate confer-ence. The transmit control signals of all participants are combined in a wired-AND function, i.e. if any of the participants exhibits an active state (ON), this active state is inherited to the combined control signal.

With subrates the control signals are extracted from the X.30 or V.110 frame before the addition. The combined signal is reinserted into the X.30 or V.110 frame.

With nx64 kbit/s the control signals are extracted from the CAS a and b bits of the first used time slot. The combined signal is reinserted into the CAS a and b bits in all positions of the used time slots.

With X-interface type conferences the byte and frame timing is maintained.

In the multipoint-to-multipoint (MP2MP) application, all participants are han-dled identically. Each participant has its own sub-conference. The sub-con-ference of each participant adds the control signals of all participants except the own signal.

User ManualTUDA1



Figure 32: Conference control signal transport, MP2MP

Participant 1:local or to master or to slave

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101

&CB2CB3

CBn

&CA2CA3

CAn

CB1CA1

Participant 2:local or to master or to slave

Participant n :local or to master or to slave

Signalling from conference

Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF

CB1CB3

CBn

CA1CA3

CAn

CB1CB2

CA1CA2

CB2CA2

CBnCAn

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101

&

&


Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101

&

&


Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF



















User ManualTUDA1



In the point-to-multipoint (P2MP) application, only the participant “to master” has a sub-conference, adding the control signals of all other participants except the own signal. The other participants (“local” or “to slave”) receive their control signal from the “to master” participant.

User ManualTUDA1



Figure 33: Conference control signal transport, P2MP

Participant 1:to master

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101

&CB2CB3

CBn

&CA2CA3

CAn

CB1CA1

Participant 2:local or to slave

Participant n :local or to slave


Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF

CB1

CA1

CB1

CA1

CB2CA2

CBnCAn

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101


Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF

1111

Protection switch

OFF

Consequent action

1111

Out of service

Subrate

CAS b bit

CAS a bit

V.110/SBX.30/S

OFF

1101


Subrate framing


C/105

0


OFF

OFF

V.110/SAX.30/S

OFF

OFF

OFF

OFF



















User ManualTUDA1



The control signal handling can be configured with the following control mechanisms:


• Consequent action:On a detected failure in the receive signal the data is replaced with a “1” or “0” signal (refer to section 5.4.2 Conference Data Handling (on page 63)). The CAS is replaced with the CAS-AIS pattern. Consequently all control signals are set to OFF.

• Control signal transport, receive direction:With subrates the SA and SB bits are demapped from the V.110 frame or the S bits are demapped from the X.30 frame.Note that with the X.30 frame the S bits are interpreted as if they were SA and SB bits of a V.110 frame. This allows the interconnection with partici-pants connected to a V.110 type interface. It is up to the operator to con-figure the control signal 107 output at the data port correspondingly, e.g. set it to OFF.If CAS is used in the nx64 kbit/s mode the a and b bits are demapped from the CAS. The CAS pattern of the first used time slot is evaluated.The CAS a bit is alternatively used to the S or SB bit, the CAS b bit is alternatively used to the SA bit.Control signals can be blocked from accessing the conference circuit with the “signalling to conference” parameter set to “No”. In this case the con-trol signals are set to OFF.If the “conditional interconnection” parameter is set to “Yes”, the control signals are only forwarded to the conference if the SB bit or CAS a bit, corresponding to the control signal C/105, is ON.

• Participant state “out of service”:The maintenance function “out of service” of a participant simulates a fail-ure of the participant in receive and transmit direction.In transmit direction the maintenance function “out of service” of a partici-pant activates the TSD and TSF signals. TSF and TSD are the XMC20 internal failure signals used to control the protection switching.With subrates the control signals S, SA and SB are set to OFF in both directions.In the nx64 kbit/s mode the a and b bits are set to OFF in receive direc-tion. In transmit direction the CAS-AIS pattern (1111) is inserted in all positions of the used time slots.

• Participant state “test pattern insertion”:With subrates the control signals S, SA and SB are transparent in receive direction.If CAS is used in the nx64 kbit/s mode the a and b bits are set to OFF in receive direction.

• Control signal transport, transmit direction:With subrates the SA and SB bits are mapped to the V.110 frame or the S bit is mapped to the X.30 frame. In order to be compatible with a remote DCE of X-type, the state of the SB bit can in addition also be mapped to the SA positions of the V.110 frame. This is controlled with the Subrate framing” parameter set to “X.30”.If CAS is used in the nx64 kbit/s mode the a and b bits are mapped to the CAS. The CAS pattern is inserted in all positions of the used time slots.

User ManualTUDA1



Control signals can be blocked from accessing the network with the “sig-nalling from conference” parameter set to “No”:

− With subrates the S, SA and SB bits are set to OFF.

− In the nx64 kbit/s mode the CAS pattern in transmit direction is replaced by the default pattern (1101).

Please note:

The nx64 kbit/s mode not using CAS provides no means for the transport of control signals to the remote DCE.

→ Use CAS to enable control signal transport. This is a KEYMILE propri-etary feature.

→ CAS is enabled with the following configuration parameters set to “Yes”:“Signalling to conference”,“Signalling from conference”.

Please note:

If a conference participant requires CAS for the control signal transport CAS must be enabled on the P12 transport signal.

→ The termination mode of the P12 transport signal must be set to “PCM30” or “PCM30C”.

Please note:

The X bit of the V.110 subrate frame is not logically added in the conference function.

→ The X bit is set according to the frame loss state in the participants termination function.


It is possible to create a cross connection from a TUDA1 conference partici-pant using CAS to another CTP not using CAS.

→ This would result in a non operational control signal transport.

User ManualTUDA1



5.6 Timing Handling

5.6.1 DTE Synchronization

In the connection to a DTE, TUDA1 acts as a DCE.

5.6.1.1 Codirectional timing

With codirectional timing the data signal is in both directions, to and from the DTE, accompanied by its corresponding clock signal. The source for the receive timing signal is the DCE, the source for the transmit timing signal is the DTE.

Since the TUDA1 expects the transmit data signal to be synchronous to the network element timing (PETS), the transmit timing signal must be synchro-nized to the receive timing signal inside the DTE (loop timing).

Figure 34: Codirectional timing

5.6.1.2 Contradirectional timing

With contradirectional timing the DCE is the source for the transmit and the receive timing signals.

With the X.24/V.11 interface type, the byte timing or frame start identification signal is available.

Figure 35: Contradirectional timing

Transmitted data 103

DTEV-type

Transmitter signal element timing (DTE) 113

Received data 104Receiver signal element timing 115

Transmit T

DTEX-type

DTE transmit signal element timing X

Receive RSignal element timing S

TUDA1DCEV-type

TUDA1DCEX-type

Transmitted data 103

DTEV-type

Transmitter signal element timing (DCE) 114

Received data 104Receiver signal element timing 115

Transmit T

DTEX-type

Byte timing B or frame start identification F

Receive RSignal element timing S

TUDA1DCEV-type

TUDA1DCEX-type

User ManualTUDA1



Please note:

Contradirectional timing is problematic with higher user data rates, i.e. when the delay time on the interconnection from the DCE to the DTE and back to the DCE is in the range of a half unit interval (UI) of the user data rate. In this case the correct sampling of the data signal can not be guaranteed with the fixed timing configuration. The adaptive timing configuration should be used instead.

Please note:

The adaptive timing configuration should not be used together with the byte timing since the timing relationship between signal element timing and byte timing is then no more defined.

5.6.2 Port Timing Signals

Timing signals are used in the synchronous transmission mode of the DCE interface. With the asynchronous and oversampling transmission modes the timing signals are not used and are correspondingly disabled.

All timing signals generated by the TUDA1 unit, i.e. 114, 115, S, B and F are synchronous to the network element timing source, i.e. the PETS. The nx64 kHz and subrate timing signals are derived with appropriate dividers from the PETS.

The frame timing signal F is synchronous to the G.704 frame on the PBUS. Frame timing is only available for nx64 kbit/s signals.

The byte timing signal B is synchronous to the octet boundaries of the receive data signal.

Frame timing and byte timing are only available with the X-type DCE inter-faces. They are exclusively used with the DTE transmit timing signal X.

Please note:

Byte timing is not available with the user bit rate 1200 bit/s.

User ManualTUDA1



Figure 36: Port timing signals

The timing signals can be configured with the following control and mainte-nance mechanisms:

• Signal monitor and consequent action:The transmit timing signal X/113 is supervised for a loss of signal.A missing clock signal X/113 is detected when TUDA1 counts at least 4xn (n ≤ 10, i.e. rate ≤ 640 kbit/s) octet slips in 2.5 seconds. This corre-sponds to a clock offset of ± 200 ppm in relation to the network element timing. With n > 10, the number of octet slips to be counted is fixed to 40.As a consequent action a missing clock signal X/113 is replaced by the TUDA1 internal timing signal S/114.The consequent action on the transmit data signal can be enabled or dis-abled. If the consequent action is enabled

− the data signal T/103 is replaced by “1” or “0”,

− the control signals C/105 and 108 towards the network are set to “1” (i.e. “OFF”).

• B or F timing:With X-type interfaces with synchronous user data rates the B/F/X timing signal can be disabled, used as an input (X/113) or used as an output (B/F):

− None (B/F):The B/F timing signal output is disabled or configured as an input to the TUDA1 and used for the transmit signal synchronization.

− Byte Timing (B):The B/F/X timing signal is configured as an output to the DTE and sig-nals the last bit of each data byte sent to the DTE on the receive user data signal.

− Frame Timing (F):The B/F/X timing signal is configured as an output to the DTE and sig-nals the beginning of each frame of data bytes sent to the DTE on the receive user data signal.

Loop 2b

nx64

Bytetiming

Frametiming

X/B/F/113

B or Ftiming

Loop 2bConfiguration

OFF

Δφ

B/Ftiming

T/103

Transmit timing

B/F

X/113

Signalmonitor

Consequent action

S/115

1141x64

subrate

Subrate

Timing from PBUS

PBUS timing

User ManualTUDA1



• Transmit Timing

Figure 37: Transmit timing

The timing signal used for the TUDA1 internal sampling of the transmit user data signal T/103 can be configured to the following modes:

− Contradirectional fix: The transmit user data signal (T/103) is sampled with the timing signal S/114. The nominal delay from clocking out the receive data signal (R/104) to the sampling of the transmit data signal (T/103) is half a bit width.In this mode the signal X/113 is not used and the corresponding con-nector pins can be used as byte/frame timing (B/F) signal output.

− Contradirectional adaptive:The transmit user data signal (T/103) is sampled with a phase adjusted timing signal S/114. The sampling phase is adjusted to the signal state changes of the transmit signal T/103. The transmit user data signal can have any phase in relation to the transmit timing signal (S/114).In this mode the signal X/113 is not used.This mode is used for relatively long lines and high user data rates where the signal delay is of the same order of magnitude as the half bit width or more.

Please note:

The byte or frame timing (B/F) signal output can not be used since the phase relationship between the transmit data signal and the B/F timing signal can not be determined by TUDA1.

− Codirectional: The transmit user data signal (T/103) is sampled with the transmit tim-ing signal received from the DTE (X/113). Note that the receive timing signal (S/115) must be looped in the DTE so that the transmit timing signal (X/113) is synchronous to the network element timing.In this mode the signal X/113 is used and the corresponding connec-tor pins are configured as inputs. The timing circuit B/F can’t be used, i.e. the X.24 timing circuits must be configured to “None (B/F)”.

Please note:

With subrates the “contradirectional adaptive” and “codirectional” transmit timing modes are not available.

• Loop 2b:The maintenance function “Loop 2b” loops the receive timing signal S/115 back to the transmit direction where it replaces the transmit timing signal from the DTE X/113. With an active loop 2b the B or F timing sig-nal can be set to OFF. For details please refer to section 7.2.1 Loop 2b (on page 106).

1 = contradirectional adaptive2 = contradirectional fix3 = codirectional

R/104 Q D

QD

Δφ12

3

DTES/115S/114T/103

X/113

TUDA1

User ManualTUDA1



5.6.3 Conference Timing

All conference participants are synchronous to the network element timing source, i.e. the PETS.

There are no participant specific timing signals used in a conference.

User ManualTUDA1



5.7 Protection

5.7.1 Subnetwork Connection and linear Trail Protection

TUDA1 supports 1+1 linear trail protection and 1+1 inherently monitored subnetwork connection protection (SNCP/I). 1+1 protection is available for the DCE interfaces and for the conference participants.

The difference between the two protection scenarios lies in the availability of CAS.

• If CAS is available the CAS AIS failure can be detected, which represents then the 1+1 linear trail protection. Linear trail protection protects against server failures and disconnected matrix connections (via CAS AIS detec-tion).

• If CAS is not available only the server layer defects can be detected, which represents then the 1+1 SNCP/I protection. SNCP/I protects against server failures.

1+1 protection provides the 1+1 unidirectional protection. The operation type can be configured to revertive or non-revertive.

Please note:

Non-revertive operation is only available for subrates and for n=1 (64 kbit/s).

The switching of the working and the protecting channel is done in sink direction only. On the source side a fixed bridge is used.

Please note:

The loss of subrate frame alignment is not used as protection switching crite-rion.

User ManualTUDA1



Figure 38: Unidirectional 1+1 protection

5.7.1.1 Protection configuration

P0-nc protection switching takes place in the TUDA1 cross connect function.

Protection switching action can be driven by two different request types:

• Traffic signal requests:

− Signal fail (SF)The SF state is activated if the analysis of the incoming server signal on the transport unit reports a signal failure, e.g. loss of signal.

− CAS-AISThe CAS signalling pattern abcd of the received signal exhibits an AIS, i.e. abcd = 1111.

− Signal degraded (SD)The SD state is activated if the analysis of the incoming server signal

on the transport unit reports a degraded signal, e.g. BER 10-6.

• External command requests

− Forced switch to working

− Forced switch to protecting

− Manual switch to working

− Manual switch to protecting

Note that a forced switch is executed even when there is a failure on the tar-get signal. A manual switch is executed only if the target signal exhibits no degradation or a less severe degradation than the active signal.

The external command requests are maintenance functions, i.e. they are not stored in the units database.

P-12

P12 transport

P-12

P12 transport

P-12

P12 transport

working

protecting protecting

working

P-12

P12

Data

P12 transport

P12P12

P0ncP0-nc

Data

P0-nc

TDMNetwork

TUDA1 TUDA1

PBUS PBUS

User ManualTUDA1



It is possible to check the status of the protection switch (working, protecting circuit) via the CTP status function.

For more information on cross connections and protection switching please refer to [314] User Guide “TDM Services and Cross Connections in XMC20”.

5.7.2 Equipment Protection (EQP)

5.7.2.1 EQP features

To protect the TUDA1 functions against a failure on the TUDA1 unit, XMC20 offers the possibility to equip the subrack with a second TUDA1 unit as a protecting unit.

EQP protects the conference function. The DCE interfaces can not be pro-tected. If protection of the DCE interfaces is required, external equipment performing the switching of the interface signals between the working and the protecting unit must be used. Refer to section 5.7.2.5 DTE cabling for 1+1 equipment protection (on page 93).

In case of a failure on the active (working or protecting) unit the user traffic is rerouted from the failed TUDA1 unit to the standby TUDA1 (protecting or working) unit.

The working and the protecting TUDA1 units can be plugged in any free slot of the XMC20 subrack.

Please note:

The protection switching is non revertive, i.e. after the repair of a failed TUDA1 unit, the currently active TUDA1 unit remains the active unit irrespec-tive if it is the working or protecting unit.

Please note:

During a protection switching event the user traffic is interrupted for up to 6 s.

5.7.2.2 EQP prerequisites

To enable equipment protection for the TUDA1 unit some prerequisites must be met:

• The protecting TUDA1 unit must be in the unassigned state. Otherwise the unit will not be selectable in the EQP configuration in AP: /unit-x, Con-figuration - EQP: Create Group…, EQP Group Creation, Protecting Unit.

• The protecting unit must be hardware compatible with the working unit. Check the hardware compatibility status after the EQP group configura-tion in the AP: /unit-x, Status - EQP: Units Status, HW Compatible.The following requirements must be fulfilled that the two units are stated as hardware compatible:

− Identical unit function. The unit function is composed of the 5 first characters of the unit name, e.g. TUDA1. The unit name is available at the AP:/ Main - Equipment, Unit.

− Identical board identification, e.g. 349. The board identification is avail-able at the AP:/ Main - Inventory, Board ID.

User ManualTUDA1



− Identical hardware variant. The hardware variant is the truncation of the hardware key divided by 256, e.g. 1/256 = 0. The hardware key is available at the AP:/ Main - Inventory, Hardware Key.

• The protecting unit must be software compatible with the working unit. Check the software compatibility status after the EQP group configuration in the AP: /unit-x, Status - EQP: Units Status, SW Compatible.The following requirements must be fulfilled that the two units are stated as software compatible:

− Identical unit function. The unit function is composed of the 5 first characters of the software name, e.g. tuda1. The unit name is availa-ble at the AP:/ Main - Equipment, Software.

In order to guarantee the full compatibility of all features it is strongly rec-ommended to use the same software on the working and on the protect-ing unit.The compatible software must be installed on the TUDA1 unit before the EQP group creation.

• The unit configuration of an equipment protection group is always done on the active unit. The configuration on the standby unit is not possible.


The configuration of an equipment protection group must be saved (ECST NE menu or ECST tool bar: Save to NE).

→ Otherwise, in case of a protection switch event, the NE will load an outdated configuration from the internal configuration database and the NE configuration will be corrupted.

5.7.2.3 EQP configuration

The working TUDA1 unit of an EQP group is assigned and configured the same way as a stand alone TUDA1 unit.

The protecting TUDA1 unit is running with the same ESW as the working unit and must be in the unassigned state.

The 1+1 equipment protection group is configured on the working unit:

• AP: /unit-x, Configuration - EQP.

− Execute the command “Create Group…”.

− Select the Protecting unit, e.g. /unit-18.

− Execute “OK”.

• Save the NE configuration.

Further on any changes on the TUDA1 configuration must be done on the active unit. To find out which unit is the active unit check the AP tree or the unit status of the working or protecting TUDA1 unit.

5.7.2.4 EQP status

The unit status of the working and protecting units shows the actual status of the units belonging to the equipment protection group. The unit status offers also the commands for the EQP manipulation:

User ManualTUDA1



• Manual switchThe currently standby unit is set as active unit and the currently active unit is set as standby unit. This requires that the currently standby unit is in operational state, i.e.

− has no failure,

− is not isolated.A manual switch is possible if it is indicated with the “Manual Switch-Over Allowed” parameter.Note that this command can only be activated on the working unit status window.

• Forced switchThe currently standby unit is set as active unit, independent of the failure state of the currently standby unit.Note that there is a risk that the user traffic will be permanently inter-rupted if the currently standby unit is in a failure state.The currently active unit is set as standby unit. Note that this command can only be activated on the working unit status window.

• Isolate unitTo be able to perform a maintenance action, e.g. update of the embed-ded software, on an active unit without activating a protection switch-over, the working unit can be isolated. This means that the protection switching state machine is frozen and no protection switch will be done until the isolation of the unit is removed.Note that the isolate unit command can only be applied to the working unit.

• Join unitRemove the isolation of a previously isolated unit.Note that the join unit command can only be applied to the working unit.

The table in the EQP status window displays the following items:

• UnitMO address of the unit belonging to the EQP group.

• EQP unit modeThe working unit is the unit where the protection group has been config-ured.The protecting unit is the unit that has been set to the unassigned state before configuring the protection group.

• ActiveActive true means the unit is the active unit, i.e. it is the operational unit.Active false means the unit is the standby unit, i.e. it is not the operational unit.The active state can be changed with the “Manual Switch” and “Forced Switch” commands.

• FailureFailure true means the unit is in a failure state.Failure false means the unit is not in a failure state.The failure state can not be changed manually.

• SubstitutedSubstituted true on the working unit means the unit has been substituted by the protecting unit. A substituted unit is also in the “active false” state.Substituted false on the working unit means the unit has not been substi-tuted, i.e. it is the active unit or it has been isolated.

User ManualTUDA1



The substituted state of the protecting unit is always false.

• IsolatedIsolated true means the unit has been isolated with the “Isolate Unit” command. Isolated false means the unit is not isolated.The isolation state can be changed with the “Isolate Unit” and “Join Unit” commands.The isolated state of the protecting unit is always false.

• HW CompatibleHW compatible true means the working HW unit is compatible with the protecting HW unit. HW compatible false means the working HW unit is not compatible with the protecting HW unit. Equipment protection is not possible.

• SW CompatibleSW compatible true means the working unit embedded software (ESW) is compatible with the protecting unit ESW. SW compatible false means the working unit ESW is not compatible with the protecting unit ESW. Equipment protection is not possible.

• DB SavedDB saved true means the current configuration of the working or protect-ing unit has been saved to the XMC20 internal database.DB saved false means the current configuration of the working or protect-ing unit has not been saved to the XMC20 internal database. A protection switching event will load an outdated configuration and traffic will be dis-turbed.

5.7.2.5 DTE cabling for 1+1 equipment protection

Due to the fact that TUDA1 has front interfaces that are doubled when using the 1+1 equipment protection function, the DTE cabling must be set up accordingly.

1+1 equipment protection with TUDA1 works only with V.24/V.28, V.35 or X.24/V.11 type DTEs providing two separate interfaces. One of the inter-faces is the working interface while the other is in standby mode.

Figure 39: 1+1 equipment protection


When connecting a V.24/V.28, V.35 or X.24/V.11 type DTE to a working and protecting TUDA1 port in parallel the electrical interface parameters will be violated.

DTEworking

protecting

standby

active

TUDA1

TUDA1 PB

US

User ManualTUDA1



1+1 equipment protection with a RS485 type DTE is possible as long as the electrical interface parameters are not violated.

When using the Ethernet port of TUDA1 with 1+1 protection switching, the Ethernet cabling must be connected with an external switch box or a hub.

Great care should be taken when using additional switch boxes, as these devices must be considered as single points of failure in the sensitive path of the 1+1 equipment protection scheme.

User ManualTUDA1


Commissioning

6 Commissioning

In this section, you will find a commissioning example for the TUDA1 unit, a TUDA1 interface and a TUDA1 conference.

Please refer to [355] User Manual “ECST” for details on the general GUI aspects, and to [302] User Guide “XMC25/XMC23/XMC22” for specific char-acteristics of the XMC20.

6.1 Profiles

6.1.1 General

A profile is a set of configuration parameters that can be applied to a certain managed object.

Profiles are created offline with the CPS & Profile tool contained in the ECST GUI (Menu: Tools / CPS & Profile …) and then downloaded to the network element in order to make the profiles applicable.

For more information concerning profile handling please refer to [355] User Manual “ECST”.

Please note:

The creation of profiles is based upon templates that are provided with the ESW versions.

→ The templates are available only after importing the respective service unit’s ESW in ECST

Please note:

Make sure that you only use profiles from templates that have been installed with the ESW running on the respective unit. If you use profiles from other ESW versions, you may get an error message when trying to apply the pro-file to the unit’s configuration.


Applying a new profile will lead to a service interruption.

6.1.2 TUDA1 Profile Handling

The TUDA1 unit supports one profile type:

• QoS mapping profileThe QoS mapping profile defines the mapping of incoming frames to the four ingress queues according to the VLAN priority or the DSCP value

User ManualTUDA1


Commissioning

Please note:

TUDA1 supports the provisioning of up to 8 different QoS mapping profiles.

The profile is applicable to the managed objects according to the following table.

Table 30: Profile applicability to managed objects

Profile Profile type Applicable to MO

QoS mapping QoSMappingProfile_1.00.00 unit-x/port-5: 10/100BASE-TX

User ManualTUDA1


Commissioning

6.2 Commissioning of a DCE Interface

6.2.1 Prerequisites

Before starting the commissioning of a DCE interface on the TUDA1 unit, the following prerequisites need to be fulfilled.

6.2.1.1 COGE5 unit

In a XMC20, a COGE5 needs to be in operation in slot 11 of the XMC20 subrack.

6.2.1.2 TUDA1 unit

The TUDA1 service unit is inserted into a slot of the XMC20 subrack. Availa-ble slots are listed in section 4.2 Slots and Deployment Scenarios for the TUDA1 Unit (on page 28).

A valid ESW is installed on the TUDA1 unit. For the management of ESW, refer to [355] User Manual “ECST”. For details about compatible ESW ver-sions, refer to [012] Release Note “XMC20”.

Port-y of the TUDA1 unit is connected to a DTE with the matching interface type.

6.2.1.3 TDM transport unit (optional)

A TDM transport unit is inserted in the XMC20 and is running with a proper ESW:

− SELI8,

− SDSL8,

− STM14,

− NUSA1,

− NUSA2.

6.2.1.4 ECST

ECST needs to be installed on a PC, and a management connection from the ECST to the XMC20 needs to be up and running. For details about the installation and operation of the ECST, please refer to [355] User Manual “ECST” and [354] Quick Guide “ECST”.

The amount and accessibility of operations depend on the user profile with which you are logged in. For more information, please refer to [323] User Guide “Management Communication”.

6.2.1.5 PETS

The PETS on the XMC20 network element must be configured to an appro-priate synchronization clock source, i.e. a clock source traceable to a PRC.

User ManualTUDA1


Commissioning

For the PETS configuration refer to [314] User Guide “TDM Services and Cross Connections in XMC20”.

6.2.2 Configuration of a DCE Interface

For the configuration of the user port, the following steps have to be per-formed.

Port configuration This action list shows step by step how to configure a user port. The given example uses mostly the default values.

The following assumptions and identifiers are used:‒ The TUDA1 unit is assumed to be plugged in slot 7 of a XMC25.‒ The TUDA1 unit is assigned.‒ The port to be configured has the identifier port-1.‒ The interface type is V.35 with a synchronous transmission rate of

64 kbit/s.

Configure the port generalparameters

Proceed as follows:

1. Navigate to the general parameters:- AP:/unit-7/port-1, Configuration - General.

2. Select the interface type:- Interface Type = V.35.

3. Select the transmission mode:- Transmission = Synchronous.

4. Select the interface rate:- Rate = 64 kbit/s.

5. Disable the data signal inversion:- Data Signal Inversion = false.

6. Execute “Apply”.

Configure the port signalstructure parameters

Proceed as follows:

1. Navigate to the signal structure parameters:- AP:/unit-7/port-1, Configuration - Signal Structure.

2. Select the synchronous timing mode with contradirectional timing:- Timing = Contradirectional-Fix.


Configure the port control sig-nal parameters

Proceed as follows:

1. Navigate to the control signal parameters:- AP:/unit-7/port-1, Configuration - Control Signals.

2. Select the control signal parameters from DTE, all control signals set to ON, with control signal transport:- 105 (RTS,C) = ON,- 108 (DTR) = ON,- Signalling To Network = “Yes”.

User ManualTUDA1


Commissioning

3. Select the control signal parameters to DTE, all control signals set to ON or OFF:- 106 (CTS) = ON,- 107 (DSR) = ON,- 109 (DCD, I) = ON,- 142 (Loopback Indication) = OFF.

4. Select the delay time for the control signals:- 105 (RTS,C) -> 106 (CTS) / 109 (DCD, I) = 0 ms,


Configure the port error han-dling parameters

Proceed as follows:

1. Navigate to the error handling parameters:- AP:/unit-7/port-1, Configuration - Error Handling.

2. Select the receive failure error handling:- Consequent Action 104 (RXD, R) = 1.

3. Select the transmit failure error handling, no level detection:- Level Detection 103 (TXD, T) = False,- Consequent Action 103 (TXD, T) = None.

4. Select the transmit send time filter parameters, no send or idle time fil-ters:- DTE Max Send Time Filter = false.- DTE Max Idle Time Filter = false.- Execute “Apply”.

Configure the port test loopsparameters

Proceed as follows:

1. Navigate to the test loops parameters:- AP:/unit-7/port-1, Configuration - Test Loops.

2. Select the loop activation device, activation by the element manager:- Activation By = EM.

3. Select the transmit signal during loop 3c and loop 3b:- 103 (TXD, T) = 1.

4. Select the receive signal during loop 2b:- 104 (RXD, R) = 1.


Configure the port CTPparameters

Proceed as follows:

1. Navigate to the CTP parameters:- AP:/unit-7/port-1, Configuration - CTP.

2. The CTP parameters are implicitly set and fixed. All displayed parame-ters are read-only.

3. Configure the z-End:- Enable the Revertive Protection Switching = true.- Disable the CAS AIS Supervision = false.- Disable the Switch-Over Logging = false.- Execute “Apply”.

Result: The user port is completely configured.

User ManualTUDA1


Commissioning

Create the cross connection Proceed as follows:

1. Configure the cross connection from the user port to a time slot on a SELI8 unit. It is assumed that the connection termination point (CTP) on the SELI8 unit has been created before on port-8, time slot 1. Please note that the termination mode of the SELI8 port must be configured to PCM30 or PCM30C, i.e. using CAS.

2. Select the “Cross connections” view of the ECST.- Click on the “Connection Wizard” button:

- The “Create TDM Connection” dialogue opens.

3. Set the connection parameters:- Layer Rate = P0-nc.- Directionality = Bidirectional.- Protected = No.- Label 1 = <anyName>.- Label 2 = <anyName>.- Number = 1.

4. Execute “Next ->”.

5. Select the Z-End CTP:- Select the TUDA1 unit, port-1.


7. Select the A-End CTP:- Select the SELI8 unit, port-8/chan-1.

8. Execute “Create”.

Result: The bidirectional cross connection from the SELI8 channel to the TUDA1 port is created.

Activation Proceed as follows:

1. Set the administrative state of the port-1 to upAP:/unit-7/port-1, Main - Admin And Oper Status:- Set Administrative Status to “Up”.


→ The “Operational Status” changes to “Up”.

Result: The port is activated.

End of instruction

User ManualTUDA1


Commissioning

6.3 Commissioning of a Conference

6.3.1 Prerequisites

Refer to section 6.2.1 Prerequisites (on page 97).

6.3.2 Configuration of a Conference

For the configuration of a conference, the following steps have to be per-formed.

Conference configuration This action list shows step by step how to configure a conference. The given example uses mostly the default values.

The following assumptions and identifiers are used:‒ The TUDA1 unit is assumed to be plugged in slot 7 of a XMC25.‒ The TUDA1 unit is assigned.‒ The conference to be configured has the identifier conf-1.‒ The maximum number of participants is 4.‒ The initial number of participants is 3.‒ The rate is 64 kbit/s.‒ The conference is of the multipoint-to-multipoint type.‒ The conference has one “local” participant, one participant “to master”

and one participant “to slave”.‒ The participants use CAS for the control signal transport.‒ The participants data and control signals are interconnected without

conditional control.

Configure the unit parameters Proceed as follows:

1. Navigate to the conferencing parameters:- AP:/unit-7, Configuration - Conferencing.

2. Create a data conference:- Execute “Create Conference…”.- The “Create Conference” dialogue opens.

3. Enter the conference parameters:- Index = 1.- Maximum Number Of Participants = 4.- Initial Number Of Participants = 3.- Rate = 64 kbit/s.- Type = MP2MP.

4. Execute “OK”.

Result: The unit parameters are configured.

Configure the participant 1general parameters

Proceed as follows:

1. Navigate to the general parameters:- AP:/unit-7/conf-1/part-1, Configuration - General.

2. Enable the control signals towards the conference:- Signalling To Conference = Yes.

User ManualTUDA1


Commissioning

3. Enable the control signals from the conference:- Signalling From Conference = Yes.

4. Select the participants role:- Role = To Master.

5. Disable the conditional interconnection:- Conditional Interconnection = No.


Configure the participant 1CTP parameters

Proceed as follows:

1. Navigate to the CTP parameters:- AP:/unit-7/conf-1/part-1, Configuration - CTP.

2. The CTP parameters are implicitly set and fixed. All displayed parame-ters are read-only.

3. Configure the z-End:- Enable the Revertive Protection Switching = true.- Disable the CAS AIS Supervision = false.- Disable the Switch-Over Logging = false.- Execute “Apply”.

Result: The participant 1 is completely configured.

Configure the participant 2 Proceed as follows:

1. Configuration analogue to participant 1, but with the participants role set to “To Slave”.

Configure the participant 3 Proceed as follows:

1. Configuration analogue to participant 1, but with the participants role set to “Local”.

Create the cross connectionfor participant 1

Proceed as follows:

1. Configure the cross connection from the participant 1 to a time slot on a SELI8 unit. It is assumed that the connection termination point (CTP) on the SELI8 unit has been created before on port-1, time slot 1. Please note that the termination mode of the SELI8 port must be configured to PCM30 or PCM30C, i.e. using CAS.




User ManualTUDA1


Commissioning


5. Select the Z-End CTP:- Select the TUDA1 unit, part-1 of conf-1.




Result: The bidirectional cross connection between TUDA1 and SELI8 is configured.


Proceed as follows:

1. Configure the cross connection from the participant 2 to a time slot on a SELI8 unit. It is assumed that the connection termination point (CTP) on the SELI8 unit has been created before on port-2, time slot 1. Please note that the termination mode of the SELI8 port must be configured to PCM30 or PCM30C, i.e. using CAS.









Result: The bidirectional cross connection between TUDA1 and SELI8 is configured.


Proceed as follows:

1. Configure the cross connection from the participant 3 to a user port on the same TUDA1 unit (port-1).


User ManualTUDA1


Commissioning






7. Select the A-End CTP:- Select the TUDA1 unit, port-1.


Result: The bidirectional cross connection between TUDA1 port and conference participant is configured.

Activation Proceed as follows:

1. It is assumed that the administrative state of the port-1 has been set to up before.The conference and the participants don’t need any activation.

End of instruction

User ManualTUDA1


Operation

7 Operation

This section describes the operation functions of the TUDA1 unit.

Please note:

The operation functions described in this section assume a correctly config-ured and operational TUDA1 unit.

7.1 Unit optical Indicators

LEDs on the front of the TUDA1 unit are used to indicate to the user the alarm status summary of the unit and of the network traffic signals.

Figure 40: Fault indication LEDs on the TUDA1 unit

XXXXx R1B

37900374

UNIT TRAFFIC

Table 31: LED signalling on TUDA1

LED name Colour State Meaning

UNIT Red Failure Unit is not in service.The unit is not able to provide the requested function due to- equipment failure (total breakdown),- mismatch of HW and SW.Recovery from this error situation is done usually by replacement of unit HW or ESW.

Green / Red (blinking 1 Hz)

Booting or waiting

Unit has not been taken in service yet or the unit has not been pro-visioned.Recovery from this situation is done by taking this unit into service with ECST.

Green Running Unit is up and running, it is ready to provide the required service.

Off Failure System is not powered or outage of power supply on unit or outage of LED.

TRAFFIC Red Failure One or more active failures on the unit, independent of the sever-ity.More detailed information is provided by ECST.

Off Normal Normal (error free) operation.

User ManualTUDA1


Operation

7.2 Loops

For maintenance purposes TUDA1 offers for the DCE interfaces three differ-ent types of diagnostic loops.

Figure 41: Loops 2b, 3b and 3c

• Loop 2b (remote loop)The loop 2b redirects the received data from the network back to the net-work. The network connection between the local DCE and the remote DCE can be tested.

• Loop 3b (local loop)The loop 3b sends the user data transmitted by the DTE back to the DTE. The connection between DTE and local DCE can be tested.

• Loop 3c (local loop)The loop 3c sends the user data transmitted by the DTE back to the DTE without processing of the data signal. The connection between DTE and local DCE can be tested.

The loop signal conditions are according to ITU-T X.150. With V-type inter-faces the loops are according to ITU-T X.20bis, X.21bis and V.54. With X-type interfaces the loops are according to ITU-T X.20 and X.21.

Only one loop 2b or 3b or 3c can be active at the same time per port.

All loops can be activated by the element manager ECST. The loop 3c can also be activated from the DTE via the control signal 141. Loops can only be activated by the ECST or the DTE. This is done to prevent two users per-forming maintenance functions at the same time.

Please note:

An active loop 2b, 3b or 3c is traffic disturbing.

Please note:

An active loop generates the alarm “Maintenance Function Active”.

Please note:

There are no diagnostics loops available with MAC bridging.

7.2.1 Loop 2b

The loop 2b is the so called remote loop. The loop selector is located close to the DCE interface.

R/104

DTE

T/103

Loop 3cProcessingLoop 2b Loop 3b

TUDA1

PB

US

User ManualTUDA1


Operation

Figure 42: Loop 2b

The loop 2b at location B can be activated from the ECST at location B.

During an active loop 2b the signals towards the DTE A are as follows:

• The transmit data signal T/103 is replaced by the receive data signal R/104.

• The control signal C/105 is replaced by the received control signal I/109 if the control signal C/105 is configured to “From-DTE”. With another con-figuration the control signal is not modified.

• The control signal 108 is replaced by the received control signal 107 if the control signal 108 is configured to “From-DTE”. With another configura-tion the control signal is not modified.

• The transmit timing signal X/113, if used, is replaced by the receiver tim-ing signal S/115.

During an active loop 2b the signals towards the DTE B are as follows:

• The receive data signal R/104 is a fixed pattern, configurable to “1, “0” or “0101”

• The control signals I/109, 106 and 107 are all set to OFF.

• The control signal 142 is set to ON, indicating to the DTE that a test func-tion is active.

• The timing signals S/114 and S/115 remain active.

• The timing signal B/F remains active or can be set to OFF.

7.2.2 Loop 3b

The loop 3b is the so called local loop. The loop selector is located close to the PBUS interface of the TUDA1 unit.

Figure 43: Loop 3b

The loop 3b at location A can be activated from the ECST at location A.

During an active loop 3b the signals towards DTE A are as follows:

TDMNetwork

R/104

DTEA T/103

R/104

DTEB

T/103

fixed pattern

Processing Loop 2b

TUDA1 A,local

TUDA1 B,remote

TDMNetwork

R/104

DTEA T/103

R/104

DTEB

T/103

fixed pattern

Processing Loop 3b

TUDA1 A,local

TUDA1 B,remote

User ManualTUDA1


Operation

• The receive data signal R/104 is replaced by the transmit data signal T/103.

• The control signal I/109 is replaced by the transmitted control signal C/105 if the control signal I/109 is configured to “Remote-105”. With another configuration the control signal is not modified.

• The control signal 107 is replaced by the transmitted control signal 108 if the control signal 107 is configured to “Remote- 108”. With another con-figuration the control signal is not modified.

• The control signal 106 is not modified by a loop 3b.

• The control signal 142 is set to ON, indicating to the DTE that a test func-tion is active.

• The timing signals S/114, S/115 and B/F remain active.

During an active loop 3b the signals towards the DTE B are as follows:

• The transmit data signal T/103 is a fixed pattern, configurable to “1, “0” or “0101”

• The control signal C/105 is set to OFF.

• The control signal 108 is set to OFF.

Please note:

With subrates the transmit data signal towards the DTE B is not the fixed pattern, but the unchanged user data signal from DTE A.

→ The loop 3b with subrates is transparent.

7.2.3 Loop 3c

The loop 3c is the so called local loop. The loop selector is located close to the DCE interface of TUDA1.

Figure 44: Loop 3c

The loop 3c at location A can be activated

• from the ECST at location A

• from the DTE at location A with the control signal 141 = ON with V-type interfaces.

The data, control and timing signals towards DTE A and DTE B are the same as with the loop 3b.

Please note:

With higher user data rates and long cables, the timing condition of the data sampling in the DTE can not be fulfilled anymore since the looped data sig-nal is not resampled in TUDA1.

→ Use loop 3b instead.

TDMNetwork

R/104

DTEA T/103

R/104

DTEB

T/103

fixed pattern

Loop 3c Processing

TUDA1 A,local

TUDA1 B,remote

User ManualTUDA1


Operation

7.3 DCE Interface Line State Maintenance

The port and participant line state maintenance functions allow to take a DCE interface or a conference participant out of service or to insert a test pattern towards the front port or towards the conference.

The line state maintenance function provides the following parameters:

• In service:This parameter restores the normal operating state of the front port or of the conference participant.

• Out of service:Take a front port or a conference participant out of service, i.e. replace the data signal by an all-1 signal in receive and transmit direction, set all control signals towards the DTE to OFF, set the S, SA and SB bits in the X.30/V.110 frame to OFF and replace the signalling towards the network by an AIS (abcd = 1111) and activate the TSD and TSF signals. TSF and TSD are the XMC20 internal failure signals used to control the protection switching.The timing signals remain active.

− Port maintenance:This parameter can be used to simulate a failed path towards the front port.

− Participant maintenance:This parameter can be used to test the protection switching in a point-to-multipoint or multipoint-to-multipoint application due to a failed TUDA1 unit.

Please note:

The line states of both the “to master” and the “to slave” participants must be set to “out of service” to check the correct protection switching.

• Test pattern insertion:Replace the receive data signal at the front port or a conference partici-pants data signal by a test pattern 0101, set all control signals towards the DTE to OFF. The CAS signalling of a conference participant is set to OFF. The subrate S, SA and SB bits of a conference participant are transparent.The timing signals remain active.

− Port maintenance:This parameter provides an easy way to check the connection from the TUDA1 unit to a connected DTE.To insert a test pattern towards the TDM network, a loop 2b or an external hardware loop must be applied at the corresponding inter-face.

− Participant maintenance:This parameter provides an easy way to check the connection from the TUDA1 unit to any other conference participant.In a point-to-multipoint application a test pattern inserted at the “to master” participant is sent to all “local” and the “to slave” participants. A test pattern inserted at a “local” or “to slave” participant is sent to the “to master” participant.In a multipoint-to-multipoint application a test pattern inserted at any participant is sent to all other participants.

User ManualTUDA1


Operation

When applying a maintenance function the following signals are sent towards the front port or the conference and towards the PBUS:

For the location of the signal insertion points please refer to the figures in section 5.4.1 Port Data Handling (on page 62), section 5.4.2 Conference Data Handling (on page 63), section 5.5.4 Port Control Signal Handling (on page 73) and section 5.5.5 Conference Control Signal Handling (on page 77).

Please note:

Active maintenance functions generate the MFA alarm (maintenance func-tion active).

Please note:

Only one maintenance functions can be active at the same time on a port or conference participant.

Table 32: Maintenance function signal replacement

Function Signal Towards front port or conference

Towards PBUS

Out of service Data signal 1111’1111 1111’1111

Control signals OFF -

CAS - 1111

Failure signal - TSF, TSD a

a. TSF and TSD are the XMC20 internal failure signals used to control the protection switching

Insert test pattern Data signal 0101’0101 -

Control signals OFF b

b. With subrates the control signals towards a conference are transparent.

-

CAS - -

Failure signal - -

User ManualTUDA1


Operation

7.4 DTE send and idle Time Restrictions

A supervision circuit of the DTEs send and idle times helps to improve the network’s availability by preventing the network from remaining blocked as a result of a defective DTE. This function is mainly used in the point-to-multi-point and multipoint-to-multipoint applications.

The activity check of a DTE is done by checking the logic content of the transmit data signal T/103: A “0” means an active state, a “1” means an inac-tive state.

The send time supervision checks the number of consecutive seconds with observed activity of the DTE, i.e. each second containing a data bit with a logic “0” counts as a “send time second”. If the number of “send time sec-onds” exceeds the configured limit an alarm is activated.

The send time limit can be configured from 1 s to 255 s.

The idle time supervision checks the number of consecutive seconds with no observed activity of the DTE, i.e. each second containing only data bits with a logic “1” counts as an “idle time second”. If during the observation period the number of “idle time seconds” is below the configured limit an alarm is activated.

The idle time limit can be configured from 1 s to 255 s. The observation period for the idle time can be configured from 2 s to 65’535 s. The idle time limit is required to be smaller than the observation period.

User ManualTUDA1


Operation

Figure 45: Send time and idle time supervision

When one of the send time or idle time limits is violated the interface can be taken out of service (refer to section 8.4.3.4 AP: / unit-x / port-y, Configura-tion - Error Handling (on page 137)). All DTEs connected to this port will be detached in this case. The DTEs remain detached until the interface is taken into service again 30 s after the defect clearing or with the corresponding port status command, refer to section 8.4.6.2 AP: / unit-x / port-y, Status - Maintenance (on page 149).

Send time OK

Idle time violated

Interface in service

YN

Cs = 0Ci = Ci + 1

N NCi ≥ limit

Y

Co ≥ limit

Y

Counter for the send time seconds

Counter for the idle time secondsCounter for the idle time observation period

Cs:

Ci:Co:

Check activity for 1 s

Co = Co + 1

Activity

Cs = Cs + 1Ci = 0

Send time violated

NCs ≥ limit

Y

Idle time OK

Ci = 0Co = 0

Ci = 0Co = 0 Cs = 0

Cs = 0Ci = 0Co = 0

Interface out of serviceSend time OKIdle time OK

User ManualTUDA1


Operation

7.5 Maintenance

7.5.1 Inventory Data

It is possible to read inventory data from the TUDA1 unit via the ECST with the following access point:

AP: /unit-x, Main - Inventory.

7.5.2 Unit ESW Download

It is possible to update the embedded software (ESW) of the TUDA1 unit via software download.

Please refer to [355] User Manual “ECST” for the description of the ESW download.


The assignment of new embedded software restarts the TUDA1 unit.Thus, the installation of new ESW on the unit affects all traffic functions of the TUDA1 unit.

7.5.3 ESW Upgrade with EQP

When upgrading the ESW on 1:1 equipment protected TUDA1 units, care must be taken concerning the traffic interruptions and which unit will finally be the active unit. At the end of the upgrade procedure the working unit shall be the active unit.

It is assumed that the working unit is plugged in slot 7 and the protecting unit is plugged in slot 18 of the XMC25 subrack.

ESW upgrade procedure 1 The following procedure provides the upgrade process with one traffic inter-ruption of about 60 s.

Isolate the working unit Proceed as follows:

1. Isolate the working TUDA1 unit:- AP: /unit-7, Status – EQP.- Execute the “Isolate Unit” command.

Result: The working TUDA1 unit is isolated, i.e. it will not perform a pro-tection switchover.

ESW download and start Proceed as follows:

1. Configure the new ESW file for the working TUDA1 unit:- Menu Tools - Software Download ….- Click on the table row with ID “/unit-7”.- In the “Software to install” column select the software to be down-

loaded.- Tick the “Delete unused Software” box.

User ManualTUDA1


Operation

2. Configure the new ESW file for the protecting TUDA1:- Click on the table row with ID “/unit-18”.- In the “Software to install” column select the software to be down-


3. Execute the “Download and Start …” command.- The “Parameters for command Download and Start” dialogue opens.- Select the “Upgrade Units Only” algorithm.- Click “OK”.- The new ESW is downloaded and becomes active on the working

and the protecting units.- Traffic will be interrupted for about 60 s.

Result: The new ESW is active on the working and the protecting TUDA1 units. The working TUDA1 unit in slot 18 remains the active unit.

Join the working unit Proceed as follows:

1. Join the working TUDA1 unit:- AP: /unit-7, Status – EQP.- Execute the “Join Unit” command.

Result: The working TUDA1 unit is able again to perform a protection switchover.

End of instruction

ESW upgrade procedure 2 An alternative procedure requires two short interruptions of about 1 s instead of one long interruption. 1

ESW download Proceed as follows:

1. Configure the new ESW file for the working TUDA1 unit:- Menu Tools - Software Download ….- Click on the table row with ID “/unit-7”.- In the “Software to install” column select the software to be down-


2. Configure the new ESW file for the protecting TUDA1:- Click on the table row with ID “/unit-18”.- In the “Software to install” column select the software to be down-


3. Execute the “Download” command.- The new ESW is downloaded to the working and the protecting units.

Result: The ESW download is complete.

ESW upgrade on the protect-ing unit

Proceed as follows:

1. Apply the new ESW on the protecting TUDA1 unit:- AP: /unit-18, Main - Software- Select the downloaded software in the “Software” selection box.- Execute the “Apply” command.

1. The 1 s interruption time is valid for configurations with up to 1 conference only.With 212 conferences the interruption is up to 60 s.

User ManualTUDA1


Operation

2. Save the configuration:- Execute the “Save to NE” command.

3. Start the new ESW on the protecting TUDA1 unit:- AP: /unit-18, Main - Software- Execute the “Start Software” command.- The new ESW becomes active on the protecting unit. This takes

about 60 s.

Result: The ESW upgrade on the protecting unit is complete.

Manual switch to protectingunit

1. Perform a manual switch-over from the working to the protecting TUDA1 unit:- AP: /unit-7, Status - EQP- Execute the “Manual Switch-Over” command.- Traffic will be switched to the protecting unit.- Traffic will be interrupted for about 1 s.

2. Wait until the working unit has rebooted (about 60 s).

ESW upgrade on the workingunit

1. Apply the new ESW on the working TUDA1 unit:- AP: /unit-7, Main - Software- Select the downloaded software in the “Software” selection box.- Execute the “Apply” command.

2. Save the configuration:- Execute the “Save to NE” command.

3. Start the new ESW on the working TUDA1 unit:- AP: /unit-7, Main - Software- Execute the “Start Software” command.- The new ESW becomes active on the working unit.

4. Wait until the working unit has rebooted (about 60 s).

Manual switch to working unit 1. Perform a manual switch-over from the protecting to the working TUDA1 unit:- AP: /unit-7, Status - EQP- Execute the “Manual Switch-Over” command.- Traffic will be switched to the working unit.- Traffic will be interrupted for about 1 s.

2. Wait until the protecting unit has rebooted (about 60 s).

Result: The ESW upgrade is complete.

End of instruction

User ManualTUDA1


User Interface Reference

8 User Interface Reference

This section gives a complete reference of the managed objects, properties, and commands of the TUDA1 service unit as far as these are not covered in the generic descriptions in [302] User Guide “XMC25/XMC23/XMC22”.

For a description on how to configure and bring into operation the TUDA1 unit and its main functions, please refer to section 6 Commissioning (on page 95).

8.1 Introduction

Below, you will find a detailed description of all the configuration parameters and operations belonging to the managed objects model (MOM) for the TUDA1 service unit.

The Figure 46 "MOM (managed object model) of the TUDA1 unit" shows the access point (AP) tree for the TUDA1 unit with its managed objects.

Figure 46: MOM (managed object model) of the TUDA1 unit

With these managed objects (MOs) the following functions are covered:

Table 33: Managed objects (MOs) for TUDA1

MO Description of the management functions

unit-x: TUDA1 Rxx (tuda1_r2e)

Restart of the unit, management of the unit ESW, labelling, indication of equipment status, read of inventory data, access to logbooks. Configuration of unit parameters and equipment protection parameters, creating or deleting of data confer-ences.The detailed properties are described in section 8.3 AP: / unit-x: TUDA1 (on page 120).

<ap>

<ap>

port-y

<ap>0...20

5

<ap>conf-z

0...212

<ap>part-a

0...16

XMC20

unit-x: TUDA1

User ManualTUDA1



For each of the managed objects, properties and commands, the GUI “Tree Views” are given.

This reference section comprises the management functions:

• Overview,

• Main,

• Configuration,

• Fault Management,

• Performance Management, and

• Status.

Most of the APs only offer a part of the management functions listed above.

The order of appearance of the management function descriptions is in accordance with the APs in the ECST AP tree and the availability of the management functions of each AP.

In the tables of the sections below, the parameter default values for proper-ties are underlined.

Please note:

For better legibility of numbers in this user guide, inverted commas are used when the number’s size exceeds three digits (e.g. 40’000). In parameter entry fields of the ECST, these inverted commas must not be entered. Instead, the numbers are entered without these inverted commas (e.g. 40000).

Please note:

Screenshots presented in this reference are examples and show configura-tions or data that may not correspond to the view you see when managing your XMC20 equipment.

port-y Management of the DCE and Ethernet interface related func-tions, like the interface type, transmission mode, user bit rate and maintenance functions.The detailed properties are described in section 8.4 AP: / unit-x / port-y, y = 1 … 4 (on page 129)

conf-z Management of a data conference. Creating or deleting of con-ference participants.The detailed properties are described in section 8.6 AP: / unit-x / conf-z (on page 163)

part-a Management of a participant of a data conference. Parameters as e.g. participant role, signalling handling, maintenance func-tions.The detailed properties are described in section 8.7 AP: / unit-x / conf-z / part-a (on page 165)

Table 33: Managed objects (MOs) for TUDA1 (continued)

MO Description of the management functions

User ManualTUDA1



8.2 Profiles

For a detailed description of the profile creation and download to the NE please refer to [355] User Manual “ECST”.

Please note:

The profile templates are only available if the ESW of the TUDA1 unit has been imported into the ECST.

8.2.1 QoS Mapping Profile

Table 34: QoS mapping profile

Operation Name Parameter Name Range Description / Details

Profile Templates Template QoSMappingPro-file_1.00.00

Select the QoS mapping profile template as a base for the parameter editing.

Profile, Information Name 3 … 64 characters User editable name for the profile.Valid characters are a-z, A-Z, 0-9 and _.

Description 0 … ∞ characters User editable description for the profile.Valid characters are a-z, A-Z, 0-9 and _.

User ManualTUDA1



Profile, Data, Map-ping Profile, 802.1q Mapping

VLAN Tag Priority 0 … 7 Priority of a VLAN tagged packet or priority tagged MAC frame.

Priority Queue Q1 … Q4 Queue number for the ingress traffic.Q1 is the lowest priority queue,Q4 is the highest priority queue.

Profile, Data, Map-ping Profile, DSCP Mapping

DSCP Priority 0 … 63 Priority of an IP packet given by the Differenti-ated Services Codepoint (DSCP).

Priority Queue Q1 … Q4 Queue number for the ingress traffic.Q1 is the lowest priority queue,Q4 is the highest priority queue.

Table 34: QoS mapping profile (continued)


User ManualTUDA1



8.3 AP: / unit-x: TUDA1

8.3.1 AP: / unit-x, Overview

For a description of the

− “Overview - Alarms”, and

− “Overview - Cross Connections”

management functions, please refer to [302] User Guide “XMC25/XMC23/XMC22”.

8.3.2 AP: / unit-x, Main


− “Main - General”,

− “Main - Equipment”,

− “Main - Inventory”,

− “Main - Logbooks”, and

− “Main - Software”


8.3.3 AP: / unit-x, Configuration

8.3.3.1 AP: / unit-x, Configuration - Conferencing

“Create Conference” and “Delete Conference” dialogues:

Please note:

The maximum number of subrate conference participants is limited to 12.

User ManualTUDA1



Table 35: AP: / unit-x, Configuration - Conferencing


Create Conference …

Open the dialogue to create a confer-ence.

Create Conference Index 0 … 255 Select the conference index number.0 is a reserved value used for the auto-assignment of a conference index: The auto-assigned index is the lowest availa-ble index number.In the ECST GUI the default value is the autoassigned index number.

Maximum Number Of Participants

4 Maximum number of participants that can be assigned to the data conference.This maximum number is used for the unit internal resource handling.If the number of conference participants has to be increased above the configured maximum number the conference must be deleted and newly created.The maximum number of subrate confer-ence participants is limited to 12.

8

12

16

Initial Number Of Participants

0 … 3 …16 Number of participants initially assigned to the data conference. The initial number of participants must be smaller or equal than the maximum number of partici-pants.Note that the total number of participants per TUDA1 unit is limited.Please refer to section 5.3.1.1 nx64 kbit/s conference resources (on page 53) for a description of the available resources for conferences.

Rate 0.6 … 64 …1984 kbit/s Data rate of the conference in kbit/s. All participants of the conference are set up with this data rate.When using CAS the maximum data rate is limited to 1920 kbit/s.Note that the rate value influences the conference resource handling.Please refer to section 5.3.1.1 nx64 kbit/s conference resources (on page 53) for a description of the conference resource handling on the TUDA1 unit.

Type MP2MP The conference type can be configured to point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP) in linear network applications.Please refer to section 5.5.5 Conference Control Signal Handling (on page 77) and section 5.4.2 Conference Data Handling (on page 63) for a description of the data and signalling transport in the point-to-multipoint and multipoint-to-multipoint applications.

P2MP

Delete Conference …

Open the dialogue to delete a confer-ence.

User ManualTUDA1



8.3.3.2 AP: / unit-x, Configuration - EQP

“Create EQP Group” and “Delete EQP Group” dialogues:

Please note:

With equipment protection of a TUDA1 unit it is only possible to protect the conferences on the unit.

→ Equipment connected to user ports can not be protected.

8.3.4 AP: / unit-x, Fault Management

For the a description of the general aspects of the

Delete Conference Conference All Delete all or a specific conference.

conf-1 … conf-n

Table 35: AP: / unit-x, Configuration - Conferencing (continued)


Table 36: AP: / unit-x, Configuration - EQP


Create EQP Group …

Open the dialogue for the creation of an equip-ment protection (EQP) group.A unit must be in the unassigned state to be selectable as a protecting unit.

EQP Group Crea-tion

Group Type 1:1 Type of the EQP group.

Working Unit /unit-x MO address of the working unit, e.g. /unit-4.In the ECST GUI the working unit MO address is read-only.

Protecting Unit - List of the MO addresses of all HW compatible units which are not assigned, e.g. /unit-20.Default is no unit selected.

/unit-y

Delete EQP Group Open the dialogue for the deletion of an existing equipment protection (EQP) group.Traffic on the protecting unit will be interrupted and services will be re-established on the work-ing unit.The protecting unit will become unassigned.

User ManualTUDA1



− “Fault Management - Status”, and

− “Fault Management - Configuration”

management functions, please refer to [302] User Guide “XMC25/XMC23/XMC22”. The following table lists the fault causes of the current AP.

Table 37: AP: / unit-x, Fault Management

ID Fault Cause Event Type Traffic Affecting

Default Severity

Description

SWM Software Mismatch Equipment Alarm

Minor The running ESW does not match the assigned ESW.

SSWNA Scheduled Software Not Available

Equipment Alarm

Minor The ESW that is scheduled for installa-tion is not available on the unit. Make sure that the ESW is downloaded to the unit.

SWIN Software Incompatible With Network Element

Equipment Alarm

Major The running ESW is not compatible with the version required by the NE type or version.

PRC PBUS Resource Con-flict

Processing Error Alarm

Major Unit has been plugged into a slot which conflicts with another unit, e.g. when using an outdated ESW on an ISDN-BA linecard.

EQM Equipment Malfunction Equipment Alarm

Critical The TUDA1 controller detects any anom-alies on the unit, e.g. a voltage is miss-ing, a chip does not respond, etc.

HWIC Hardware Incompatible With Configuration

Equipment Alarm

Major The plugged HW is not compatible with the unit configuration HW stored in the database. You may need to change the HW or re-create the configuration for the unit.

SWIC Software Incompatible With Configuration

Equipment Alarm

Major The ESW running on the unit is not com-patible with the unit configuration stored in the database. You may need to upgrade, or downgrade the ESW, or re-create the configuration with the cur-rently running ESW.

GSW General Software Alarm

Equipment Alarm

Major An ESW internal error has been detected that might inhibit the ESW from running correctly.

MFA Maintenance Function Active

Communica-tion Alarm

Warning A maintenance function has been acti-vated by the operator from the unit status dialogue.

UNAV Unit Not Available Equipment Alarm

Critical The unit that is configured is either not plugged or not recognized due to a fail-ure.

NSW No Application Soft-ware

Equipment Alarm

Major There is no application ESW installed on the unit, or the application ESW has not yet finished its boot process.

UNAS Unit Not Assigned Equipment Alarm

Warning The unit is not assigned and cannot be configured. To assign the unit, execute the “Assign” command in the “Main” function of the unit.

UIC Unit Incompatible Equipment Alarm

Major The inserted unit is not compatible with the assigned unit.

User ManualTUDA1



PWRSVE Battery Power Saving Equipment Alarm

Critical Power saving is active on the unit, i.e. it is kept in the “reset” state during battery power backup.

EQPUNV EQP Unit Not Available Equipment Alarm

Major The standby unit is not available, i.e. not plugged in or has an equipment failure.This alarm is available on the working and the protecting unit of an EQP group.

EQPHWI EQP Hardware Incom-patible With Configura-tion

Equipment Alarm

Major The actual hardware is not compatible with the hardware of the protecting unit.This alarm is available on the working unit of an EQP group only.

EQPSWI EQP Software Incom-patible With Configura-tion

Equipment Alarm

Major The running software (ESW) is not com-patible with the software on the protect-ing unit.This alarm is available on the working unit of an EQP group only.

EQPNPR EQP Group Not Pro-tected

Equipment Alarm

Major The working or the protecting unit is not available, i.e. not plugged in or has an equipment failure.This alarm is available on the working unit of an EQP group only.

EQPWUI EQP Working Unit Iso-lated

Equipment Alarm

Major The working unit has been isolated with the “Isolate Unit” status command.No protection is available in this state.This alarm is available on the working unit of an EQP group only.

EQPUNA EQP Working Unit Not Active

Equipment Alarm

Major An automatic protection switch or a “manual switch” or a “forced switch” to the protecting unit has been done.

Table 37: AP: / unit-x, Fault Management (continued)


Default Severity

Description

User ManualTUDA1



8.3.5 AP: / unit-x, Status

8.3.5.1 AP: / unit-x, Status - Conferences

Table 38: AP: / unit-x, Status - Conferences


Number Of Availa-ble Conferences a

Number Of Availa-ble 16 Participants Conferences

0 … 53 Available number of 64 kbit/s conferences with 16 participants on the TUDA1 unit.





Number Of Availa-ble 12 Participants Subrate Confer-ences

0 … 1 Available number of subrate conferences with 12 participants on the TUDA1 unit.





User ManualTUDA1



Please note:

Refer to section 5.3.1.1 nx64 kbit/s conference resources (on page 53) and to section 5.3.1.2 Subrate conference resources (on page 55) for a descrip-tion of the conference resource handling on the TUDA1 unit.

Please note:

Refer to section 5.3.1.3 PBUS resources (on page 56) for a description of the PBUS resource handling on the TUDA1 unit.

8.3.5.2 AP: / unit-x, Status - EQP

Available Partici-pant Resources, Participant Resource Table b

Max Participant Rate (kbit/s)

64 … 1984 Maximum participant rate available on the PBUS resources.It is only possible to create conference partici-pants with the maximum or a smaller rate.

Available 0 … 27 Available number of participants with the corre-sponding maximum participant rate.It is only possible to create conference partici-pants with the maximum rate up to the available number.Note that when creating conferences with smaller rates also the resources with higher rates can be used.

a. The number of available conferences shows the number of available conferences with 16 OR 8 OR 4 participants. The number of available subrate conferences shows the number of available conferences with 12 OR 8 OR 4 participants.

b. The participant resource table shows all available resources, it is NOT an OR operation.

Table 38: AP: / unit-x, Status - Conferences (continued)


User ManualTUDA1



Table 39: AP: / unit-x, Status - EQP


EQP Group Manual Switch-Over Allowed

Indication that the standby unit, i.e. the working or the protecting unit is operational and can take over the service.

Indication that the standby unit, i.e. the working or the protecting unit is not operational due to a failure or to isolation or that the database has not been saved. A manual protection switching with the “Manual Switch-Over” command is not possi-ble.

EQP Group - Units Status

Unit <MO address> MO address of the unit belonging to the EQP group.

EQP Unit Mode Undefined Mode Mode of a unit in the EQP group.

Working Unit

Protecting Unit

Active The unit is active (operational).

The unit is standby (not operational).

Failure The unit has detected failure(s).

Substituted The working unit has been substituted by the protecting unit.

Isolated The working unit has been isolated with the “Iso-late Unit” command.

HW Compatible The working unit is hardware compatible with the protecting unit in the EQP group.Please refer to section 5.7.2.2 EQP prerequisites (on page 90).

SW Compatible The working unit is embedded software compati-ble with the protecting unit in the EQP group.Please refer to section 5.7.2.2 EQP prerequisites (on page 90).

DB Saved The configuration of the unit has been saved.

Manual Switch-Over Manual switch of the unit in the EQP group.A switch over is performed only when the other unit is error free and is not isolated and the data-base has been saved.Refer to the “Manual Switch-Over Allowed” prop-erty above.Note: The traffic will be interrupted for about 1 s. a

Forced Switch-Over Forced switch of the unit in the EQP group.A switch over is performed independent of the error state of the other unit, but the unit must not be isolated.Note: The traffic will be interrupted for about 1 s. a

Note: Traffic will remain interrupted if the active unit is not operational.

User ManualTUDA1



Please note:

Automatic, manual and forced protection switching is available from the working to the protecting unit and vice versa.

→ Please refer to section 5.7.2 Equipment Protection (EQP) (on page 90).

Isolate Unit Isolate the working unit from the EQP group.An isolated working unit will not perform any pro-tection switch action. The protection switching state of the unit is frozen.

Join Unit Join the isolated working unit to the EQP group, i.e. remove the isolation.

a. The 1 s interruption time is valid for configurations with up to 1 conference only. With 212 conferences the interruption is up to 60 s.

Table 39: AP: / unit-x, Status - EQP (continued)


User ManualTUDA1



8.4 AP: / unit-x / port-y, y = 1 … 4

8.4.1 AP: / unit-x / port-y, Overview


− “Overview - Alarms”,

− “Overview - Cross Connections”, and

− “Overview - CTP”


8.4.2 AP: / unit-x / port-y, Main

8.4.2.1 AP: / unit-x / port-y, Main - General


− “Main - General”

management function, please refer to [302] User Guide “XMC25/XMC23/XMC22”.

8.4.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status

Table 40: AP: / unit-x / port-y, Main - Admin And Oper Status


Administrative Sta-tus

State Up Set the IETF administrative status of the port (RFC 2863).

Down

Operational Status State Up Display of the IETF operational status of the port (RFC 2863).

Down

Testing

Unknown

Dormant

Not Present

Lower Layer Down

User ManualTUDA1



8.4.3 AP: / unit-x / port-y, Configuration

Please note that the fields for some of the configuration parameters are con-text sensitive. Configuration parameters that are not available due to a higher-ranking configuration parameter are indicated as “NA” (not available).

The steering parameters for the port configuration are

• Interface Type

• Interface Transmission Mode

• Interface Rate

• Synchronous B/F Signal Usage

• CAS Usage

The configuration strategy to be followed is from the uppermost tab (Gen-eral) to the lowermost tab (CTP), and on the tabs from the top parameter downwards.

After completing the parameter configuration of a tab press the “Apply” but-ton to assign the applicable values to the lower-ranking parameters.

8.4.3.1 AP: / unit-x / port-y, Configuration - General

Table 41: AP: / unit-x / port-y, Configuration - General


Interface Interface Type V.35 Select the interface type of the DCE port.For valid combinations of the interface type and other configuration parameters refer to Table 21: "Function relationship" (on page 39).

X.24-V.11

V.24-V.28

RS485-2-wire

RS485-4-wire

Transmission Asynchronous Select the interface transmission mode.Please refer to section 5.1.4 Transmission Modes (on page 43) for a description of this parameter.

Synchronous

Oversampling

Rate 0.6 … 64 … 1984 kbit/s Select the interface rate in steps of 64 kbit/s.The rate corresponds to the number of time slots used, i.e. 1 … 31 time slots.Rates below 64 kbit/s use the subrate fram-ing according to V.110 or X.30.

Data Signal Inver-sion

Invert the logical state of the transmit and receive data signal.

User ManualTUDA1



Please note:

The V.24-V.28 interface type in Synchronous transmission mode only sup-ports interface rates up to 128 kbit/s.

Please note:

The RS485 interface types only support the Oversampling transmission mode.

Please note:

The Oversampling transmission mode is only available for interface rates at 64 kbit/s and above.

Please note:

The Asynchronous transmission mode is only available for subrates up to 38.4 kbit/s.

8.4.3.2 AP: / unit-x / port-y, Configuration - Signal Structure

User ManualTUDA1



Table 42: AP: / unit-x / port-y, Configuration - Signal Structure


Signal Structure Synchronous, Tim-ing

Contradirectional-Fix Use the contradirectional interface timing with fixed phase alignment.Only available with the Synchronous trans-mission mode.Please refer to section 5.6.2 Port Timing Sig-nals (on page 84).

Contradirectional-Adaptive Use the contradirectional interface timing with adaptive phase alignment.Only available with the Synchronous trans-mission mode and with interface rates at 64 kbit/s and above.

Codirectional Use the codirectional interface timing.Only available with the Synchronous trans-mission mode and with interface rates at 64 kbit/s and above.

NA NA (not available) is the only configurable value if the transmission mode is Oversam-pling or Asynchronous.

Synchronous, B/F None Use no byte (B) or frame (F) timing signal.Only available with the X.24-V.11 interface type and the Synchronous transmission mode.Please refer to section 5.6.2 Port Timing Sig-nals (on page 84).

Byte-Timing Use the byte (B) timing signal.Only available with the X.24-V.11 interface type and the Synchronous transmission mode and interface rates up to 256 kbit/s.

Frame-Timing Use the frame (F) timing signal.Only available with the X.24-V.11 interface type and the Synchronous transmission mode and interface rates between 64 and 256 kbit/s.

NA NA (not available) is the only configurable value- if the interface type is not X.24-V.11 or- if the transmission mode is not Synchro-

nous or - if the interface rate is above 256 kbit/s or- if the interface rate is 1.2 kbit/s.

Asynchronous, Data Bits

7 Use 7 or 8 data bits in the start-stop charac-ter.Please refer to section 5.1.4.1 Asynchro-nous transmission mode (on page 43).

8

NA NA (not available) is the only configurable value if the transmission mode is not Asyn-chronous

User ManualTUDA1



Please note:

The B/F signal output is only available with the Contradirectional timing modes.

Asynchronous, Stop Bits

1 Use 1 or 2 stop bits in the start-stop charac-ter.Please refer to section 5.1.4.1 Asynchro-nous transmission mode (on page 43).

2


Asynchronous, Par-ity Bit

No Use or don’t use a parity bit in the start-stop character.Note that the parity bit is not evaluated in TUDA1, it is transported transparently.Please refer to section 5.1.4.1 Asynchro-nous transmission mode (on page 43).

Yes


Asynchronous, Sig-nalling Rate Range

Basic Use the basic or extended rate adaptation range for the start-stop characters.Please refer to section 5.1.4.1 Asynchro-nous transmission mode (on page 43).

Extended


104 Control (RS485 2-wire), Control Mode

RTS-Control The CAS bit a, set by the control signal RTS (C/105) at the remote end, controls the trans-mitter circuit at the RS485 interface.The CAS usage limits the maximum interface rate to 1920 kbit/s.Refer to section 5.1.2.1 RTS controlled mode (on page 40).

Data-Control The activity of the receive data signal con-trols the transmitter circuit at the RS485 inter-face.Refer to section 5.1.2.2 Data controlled mode (on page 41).

NA NA (not available) is the only configurable value if the interface type is not RS485 2-wire.

104 Control (RS485 2-wire), Hold Active Time

20 … 1500 samples Time to keep the transmitter circuit active after the last 0 to 1 transition.

Table 42: AP: / unit-x / port-y, Configuration - Signal Structure (continued)


User ManualTUDA1



8.4.3.3 AP: / unit-x / port-y, Configuration - Control Signals

Table 43: AP: / unit-x / port-y, Configuration - Control Signals


Control Signals, From DTE

105 (RTS, C) ON Set the local control signal C/105 to 0.Please refer to section 5.5 Control Signal Handling (on page 67).

OFF Set the local control signal C/105 to 1.

From-DTE Set the local control signal C/105 according to the control signal state received from the DTE.

NA NA (not available) is the only configurable value if the interface type is RS485.

108 (DTR) ON Set the local control signal 108 to 0.Please refer to section 5.5 Control Signal Handling (on page 67).

OFF Set the local control signal 108 to 1.

From-DTE Set the local control signal 108 according to the control signal state received from the DTE.

NA NA (not available) is the only configurable value if the interface type is X.24-V.11 or RS485.

User ManualTUDA1



Signalling To Net-work

No Set the CAS a and b bits or the subrate frame S bit (X.30) or SA and SB bits (V.110) to 1 (OFF).Please refer to section 5.5.4 Port Control Sig-nal Handling (on page 73).

Yes Set the CAS a and b bits or the subrate frame S bit (X.30) or SA and SB bits (V.110) according to the C/105 and 108 control signal state.

NA NA (not available) is the only configurable value- if the interface type is RS485 or- if the interface rate is 1984 kbit/s (no CAS

available) or- if the interface rate is 56 kbit/s without sig-

nalling.

V/X Compatibility Mode

No Set the subrate frame SA and SB bits (V.110) according to the C/105 and 108 con-trol signal state.Please refer to section 5.5 Control Signal Handling (on page 67).

Yes Set both the subrate frame SA and SB bits (V.110) according to the C/105 control signal state.

NA NA (not available) is the only configurable value- if the interface type is X.24-V.11 or RS485

or- if the interface rate is 64 kbit/s or above or- if the interface rate is 56 kbit/s without sig-

nalling.

Control Signals, To DTE

106 (CTS) ON Set the control signal 106 to ON.Please refer to section 5.5 Control Signal Handling (on page 67).

OFF Set the control signal 106 to OFF.

Local-105 Set the control signal 106 according to the local control signal state C/105.The activation and deactivation of the control signal 106 can be without delay or with a configurable delay. Refer to the “105 (RTS, C) -> 106 (CTS) / 109 (DCD, I)” parameter below.

Remote-LFA Set the control signal 106 according to the received” remote loss of frame alignment” indication, transported in the X bit of the V.110 subrate frame.


Table 43: AP: / unit-x / port-y, Configuration - Control Signals (continued)


User ManualTUDA1



107 (DSR) ON Set the control signal 107 to ON.Please refer to section 5.5 Control Signal Handling (on page 67).


Local-108 Set the control signal 107 according to the local control signal state 108.

Remote-108 Set the control signal 107 according to the received CAS b bit or the subrate frame SA bit (V.110).


109 (DCD/I) ON Set the control signal I/109 to ON.Please refer to section 5.5 Control Signal Handling (on page 67).

OFF Set the control signal I/109 to OFF.

Local-105 Set the control signal I/109 according to the local control signal state C/105.The activation and deactivation of the control signal I/109 can be without delay or with a configurable delay. Refer to the “105 (RTS, C) -> 106 (CTS) / 109 (DCD, I)” parameter below.

Remote-105 Set the control signal I/109 according to the received CAS a bit or the subrate frame S bit (X.30) or SB bit (V.110).

NA NA (not available) is the only configurable value if the interface type is RS485.

142 (Loopback Indi-cation)

ON Set the control signal 142 to ON.Please refer to section 5.5 Control Signal Handling (on page 67).


From-DCE Set the control signal 142 according to the local loop state, i.e. - Back-To-Back-2b or- Front-To-Front-3b or- Front-To-Front-3c.


Control Signals, Delay Local Control Signals

105 (RTS, C) -> 106 (CTS) / 109 (DCD, I)

0 ms Propagation delay between the local control signal C/105 and the control signals 106 and I/109, if they are configured to “Local-105”.Please refer to section 5.5 Control Signal Handling (on page 67).

10 ms

20 ms

40 ms

Table 43: AP: / unit-x / port-y, Configuration - Control Signals (continued)


User ManualTUDA1



8.4.3.4 AP: / unit-x / port-y, Configuration - Error Handling

Table 44: AP: / unit-x / port-y, Configuration - Error Handling


Error Handling, Receive Failure

Consequent Action 104 (RXD, R)

0 Replace the receive data signal R/104 by a 0 or a 1 in case of a downstream failure (server-layer) or with a local subrate loss of frame alignment.

1

Consequent Action B/F

OFF Set the byte-timing or frame-timing signal to OFF in case of a downstream failure (server-layer) or with a local subrate loss of frame alignment.

Active Keep the byte-timing or frame-timing signal active also in case of a downstream failure.

NA NA (not available) is the only configurable value if the interface type is not X.24-V.11 or the B/F parameter is not configured to byte-timing or to frame-timing.

Error Handling, Transmit Failure

Level Detection 103 (TXD, T)

False Supervise the electrical signal levels on the transmit data signal T/103.Please refer to section 5.4.1 Port Data Han-dling (on page 62).

True

NA NA (not available) is the only configurable value if the interface type is RS485 2-wire.

User ManualTUDA1



Consequent Action 103 (TXD, T)

None Apply no consequent action in case of a detected failure on the transmit data signal T/103 or transmit clock signal X/113.

0 In case of a detected failure on the transmit data signal T/103 or transmit clock signal X/113 set the local transmit data signal to 0 or 1 and set the local control signals C/105 and 108 to OFF.The consequent action on the control signals affects only the control signal transport via the CAS or the subrate frame S bit (X.30) or SA and SB bits (V.110).Note that the “Level Detection 103 (TXD, T)” must be set to “True”.

1


Error Handling, Transmit Send Time Filter 103 (TXD, T)

DTE Max Send Time Filter

Supervise the maximum send time on the transmit data signal T/103, i.e. check for activity on the data signal.Please refer to section 7.4 DTE send and idle Time Restrictions (on page 111)

DTE Max Send Time

1 … 10 … 255 s Maximum allowed number of consecutive seconds with observed activity on the trans-mit data signal T/103.

DTE Min Idle Time Filter

Supervise the minimum idle time on the transmit data signal T/103, i.e. check for inactive periods on the data signal.Please refer to section 7.4 DTE send and idle Time Restrictions (on page 111)

DTE Min Idle Time 1 … 10 … 255 s Minimum required number of consecutive seconds with no activity during the observa-tion period on the transmit data signal T/103.

DTE Idle Time Win-dow

2 … 20 … 65’535 s Observation period for the minimum idle time.Note that the “DTE Idle Time Window” must be higher than “DTE Min Idle Time”.

Table 44: AP: / unit-x / port-y, Configuration - Error Handling (continued)


User ManualTUDA1



Please note:

The consequent action in case of a detected send or idle time failure over-rides the consequent action in case of a detected signal level failure.

8.4.3.5 AP: / unit-x / port-y, Configuration - Test Loops

Consequent Action On Port

None Apply no consequent action in case of a detected send or idle time failure on the transmit data signal T/103.

Persistent In case of a detected send or idle time failure on the transmit data signal T/103- set the local transmit data signal T/103 to 1,- set the local control signals C/105 and 108

to OFF,With “Persistent” the consequent action must be removed manually in the port status main-tenance dialogue. Refer to section 8.4.6.2 AP: / unit-x / port-y, Status - Maintenance (on page 149).With “Auto-Reset” the consequent action is automatically reset 30 s after the clearing of the failure.Note that the “DTE Max Send Time Filter” or the “DTE Min Idle Time Filter” must be set to “true” to be able to configure “Persistent” or “Auto-Reset”.

Auto-Reset

Table 44: AP: / unit-x / port-y, Configuration - Error Handling (continued)


Table 45: AP: / unit-x / port-y, Configuration - Test Loops


Test Loops, Loop Activation

Activation By EM All loops can be activated by the element manager (EM).The loop activation by the control signal 141 is blocked.

DTE The front-to-front loop 3c can be activated by the control signal 141.The loop activation of all loops by the ele-ment manager (EM) is blocked.

User ManualTUDA1



8.4.3.6 AP: / unit-x / port-y, Configuration - CTP

Please note:

All layer rate, number of time slots and time slot allocation parameters are read only.

→ To change a parameter the port has to be deleted and newly created with the modified parameters.

Test Loops, Signal States When Loop Active, Loop 3b, 3c

103 (TXD, T) 1 Replace the transmit data signal T/103 by a 0, a 1 or a 01 signal in case of an active loop 3b or loop 3c.

0

01


Test Loops, Signal States When Loop Active, Loop 2b

104 (RXD, R) 1 Replace the receive data signal R/104 by a 0, a 1 or a 01 signal in case of an active loop 2b.

0

01

B/F OFF Set the byte-timing or frame-timing signal to OFF in case of an active loop 2b.

Active Keep the byte-timing or frame-timing signal active also in case of an active loop 2b.

NA NA (not available) is the only configurable value if the interface type is not X.24-V.11 or the B/F parameter is not configured to byte-timing or to frame-timing.

Table 45: AP: / unit-x / port-y, Configuration - Test Loops (continued)


User ManualTUDA1



Table 46: AP: / unit-x / port-y, Configuration - CTP


CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is P0_nc, i.e. n x 64 kbit/s.The layer rate property of a TUDA1 port is fixed to P0_nc.

n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-sible range is from 1 to 32.The number of time slots of a TUDA1 port is fixed in the range 1 to 31.

Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of P0_nc, e.g. 1 … 31.The timeslot(s) property of a TUDA1 port is empty.

Connected to CTPs Remote CTP <MO address> Address string of a connections remote end. Without a connection the parameter is empty

Connection Index 0 … 65’535 Index of a connection assigned to the port. With-out a connection the parameter is empty

Directionality Bidirectional Directionality of the connection.

Unidirectional

Local Role z-End The port is the ending point of a connection.Please refer to [314] User Guide “TDM Ser-vices and Cross Connections in XMC20”

a-End Working The port is the working starting point of a pro-tected or unprotected connection.

a-End Protecting The port is the protecting starting point of a pro-tected connection.

Remote Role z-End The CTP at the connections remote end is the ending point of a connection.Please refer to [314] User Guide “TDM Ser-vices and Cross Connections in XMC20”

a-End Working The CTP at the connections remote end is the working starting point of a protected or unpro-tected connection.

a-End Protecting The CTP at the connections remote end is the protecting starting point of a protected connec-tion.

z-End Configuration Revertive Protection Switching

Enable revertive protection switching.The z-End will preferably select the working a-End.Non-revertive protection switching is only availa-ble for ports with the number of timeslots n=1.Non-revertive protection switching for n>1 will be available in a future release,

CAS AIS Supervi-sion

Use CAS AIS as protection switching criterion.The CAS AIS supervision can be disabled in the shared protection ring application, where the closed protection ring can have an AIS in the CAS, to prevent an alarm during normal opera-tion.

Switch-Over Log-ging

Enable the logging of the protection switch-over events.

User ManualTUDA1



Please note:

The z-End of a protected connection shows two entries in the “Connected to CTPs” table, one for the working and one for the protecting path.

8.4.4 AP: / unit-x / port-y, Fault Management





Table 47: AP: / unit-x / port-y, Fault Management


Default Severity

Description

LOS Loss Of Signal Communica-tion Alarm

Major Loss of the incoming transmit data sig-nal.Only available if the transmit data signal level detection is enabled in the port con-figuration dialogue.

LOC Loss Of Clock Communica-tion Alarm

Major Loss of the incoming transmit clock sig-nal, evaluated from the physical interface state and from octet slips.

DTESL DTE Send Time Limit Exceeded


Major The connected DTE send time period is longer than allowed.Only available if the send time limit supervision is enabled in the port config-uration dialogue.If the consequent action is set to “Persis-tent” the consequent action must be removed manually in the port status maintenance dialogue.

DTEIL DTE Idle Time Below Limit


Major The connected DTE idle time period is shorter than allowed during the observa-tion period.Only available if the idle time limit super-vision is enabled in the port configuration dialogue.If the consequent action is set to “Persis-tent” the consequent action must be removed manually in the port status maintenance dialogue.

LOF Loss Of Frame Communica-tion Alarm

Major Loss of the V.110 or X.30 frame align-ment.

RLOF Remote Loss Of Frame Communica-tion Alarm

Minor Loss of the V.110 or X.30 frame align-ment at the remote equipment. The alarm indication is transported in the X bit of the V.110 or X.30 frame.

User ManualTUDA1



Please note:

The monitoring of the TSF and RTSF alarms is disabled by default.


With the V.24-V.28 interface type and synchronous transmission mode, there can be crosstalk on the connected cable from the clock to the transmit data signal.

→ The “Loss Of Signal” alarm is possibly not detected.

NDPF Near End Degraded Performance

Quality Of Service Alarm

Warning SES ≥ 22 over a 24 hour interval at the near end.The alarm status is reset after a 24 hour interval with SES = 0.SES is a second with an active LOS or LOC fault cause.The alarm can be cleared by resetting the corresponding PM alarm counter.

NUPF Near End Unacceptable Performance

Quality Of Service Alarm

Warning SES ≥ 15 over a 15 min. interval at the near end.The alarm status is reset after a 15 min. interval with SES = 0.SES is a second with an active LOS or LOC fault cause.The alarm can be cleared by resetting the corresponding PM alarm counter.



Warning A maintenance function has been acti-vated by the operator from the port sta-tus dialogue.

TSF Trail Signal Failure Communica-tion Alarm

Major Trail signal fail (TSF) from the P12 trans-port unit is active, or CAS AIS active (only available if CAS is enabled), orLOF is active.In a protected connection the working AND the protecting path have failed.

RTSF Redundant Trail Signal Failure


Minor Trail signal fail (TSF) from the P12 trans-port unit is active, or CAS AIS active (only available if CAS is enabled), orLOF is active.In a protected connection the working OR the protecting path has failed.In an unprotected connection this fault cause is not applicable.

Table 47: AP: / unit-x / port-y, Fault Management (continued)


Default Severity

Description

User ManualTUDA1





→ A mismatch of the user data rates configured for two connected user ports or conference participants cannot be detected. The “Loss Of Frame” alarm is not activated.

8.4.5 AP: / unit-x / port-y, Performance Management

For the a description of the general aspects of the performance management (PM) functions, please refer to [302] User Guide “XMC25/XMC23/XMC22”.

The PM parameters are presented in different groups. The following counter groups are available for the TUDA1 ports:

• “Protection” group, see section 8.4.5.1 AP: / unit-x / port-y, Performance Management - Protection (on page 144),

• “G.826” group, see section 8.4.5.2 AP: / unit-x / port-y, Performance Man-agement - G.826 (on page 144),

• “Unfiltered Events” group, see section 8.4.5.3 AP: / unit-x / port-y, Perfor-mance Management - Unfiltered Events (on page 145),

The following counter intervals are available, depending of the counter group:

8.4.5.1 AP: / unit-x / port-y, Performance Management - Protection

8.4.5.2 AP: / unit-x / port-y, Performance Management - G.826

Table 48: PM counter interval availability

Counter interval Protection G.826 Unfiltered Events

User Counter yes yes yes

History 15min yes yes yes

History 24h yes yes yes

Alarm 15min no yes no

Alarm 24h no yes no

Table 49: PM group: Protection

PM parameter Description

Switch-Over The protection switch-over count gives information about the number and distribution of protection switching events.

Table 50: PM group: G.826


Near End SES Near end count of Severely Errored Seconds.A second with a defect signal (LOS or LOC) and not part of unavailable time (UAT).

User ManualTUDA1



8.4.5.3 AP: / unit-x / port-y, Performance Management - Unfiltered Events

Please note:

The octet slip count is limited to 150 slips per second. If the timing deviation of the transmit data signal is more than 1200 bit/s, i.e. more than 600 ppm, 150 octet slips are counted per second.

Near End UAT Near end count of Unavailable Time.Unavailable time starts with 10 consecutive SES (included in UAT) and ends with 10 consecutive error free seconds (not included in UAT).

Table 50: PM group: G.826 (continued)


Table 51: PM group: Unfiltered Events


Positive Slips Count of the positive octet slips between the incom-ing X/113 timing and the local S/114 timing.The DTE source clock is higher than the DCE source clock.

Negative Slips Count of the negative octet slips between the incom-ing X/113 timing and the local S/114 timing.The DTE source clock is lower than the DCE source clock.

User ManualTUDA1



8.4.6 AP: / unit-x / port-y, Status

8.4.6.1 AP: / unit-x / port-y, Status - General

Table 52: AP: / unit-x / port-y, Status - General


From DTE 103 (TXD, T) 1 Signal state of the transmit data signal T/103.Note that the state at the interface circuit is dis-played. The data signal inversion configuration does not influence the status indication.

0

Activity On 103 (TXD, T)

Yes Observed activity on the transmit data signal T/103 since the last status refresh.

No

User ManualTUDA1



105 (RTS,C) On Signal state of the control signal C/105.

Off

NA NA (not available) is the displayed if the interface type is RS485.

108 (DTR) On Signal state of the control signal 108.

Off

NA NA (not available) is displayed if the interface type is X.24-V.11 or RS485.

141 (LL) On Signal state of the control signal 141 (loop com-mand).

Off


To Network CAS 0000 … 1111 CAS abcd pattern sent towards the network. With a P0-nc data signal the CAS abcd pattern is sent with every time slot.The a bit can be controlled by the control signal C/105.The b bit can be controlled by the control signal 108.Note: With a P0-nc data signal with n=31 (1984 kbit/s) it is not possible to transport this CAS abcd pattern in a P12 transport signal.

S 0 Signal state of the sent subrate frame S bit (X.30).The S bit can be controlled by the control signal C.

1

NA NA (not available) is displayed if the interface rate is at 64 kbit/s or above, i.e. without subrates, or with the subrate 56 kbit/s without signalling or when the interface type is not X.24-V.11.

SA 0 Signal state of the sent subrate frame SA bit (V.110).The SA bit can be controlled by the control signal 108.

1

NA NA (not available) is the displayed if the interface rate is at 64 kbit/s or above, i.e. without subrates, or with the subrate 56 kbit/s without signalling or when the interface type is X.24-V.11.

SB 0 Signal state of the sent subrate frame SB bit (V.110).The SB bit can be controlled by the control signal 105.

1


Table 52: AP: / unit-x / port-y, Status - General (continued)


User ManualTUDA1



X 0 Signal state of the sent subrate frame X bit (X.30 or V.110).The X bit is controlled by the state of the subrate frame alignment.

1

NA NA (not available) is the displayed if the interface rate is at 64 kbit/s or above, i.e. without subrates or with the subrate 56 kbit/s without signalling.

From Network CAS 0000 … 1111 CAS abcd pattern received from the network. With a P0-nc data signal the CAS abcd pattern of the lowest numbered time slot is displayed.The a bit can control the control signal I/109.The b bit can control the control signal 107.

S 0 Signal state of the received subrate frame S bit (X.30).The S bit can control the control signal I.

1

NA NA (not available) is the displayed if the interface rate is at 64 kbit/s or above, i.e. without subrates, or with the subrate 56 kbit/s without signalling or when the interface type is V.24-V.28 or V.35.

SA 0 Signal state of the received subrate frame SA bit (V.110).The SA bit can control the control signal 107.

1


SB 0 Signal state of the received subrate frame SB bit (V.110).The SB bit can control the control signal 109.

1


X 0 Signal state of the received subrate frame X bit (X.30 or V.110).The X bit can control the control signal 106.

1

NA NA (not available) is the displayed if the interface rate is at 64 kbit/s or above, i.e. without subrates or with the subrate 56 kbit/s without signalling.

To DTE 104 (RXD, R) 1 Signal state of the receive data signal R/104.Note that the state before the interface circuit is displayed.

0

Activity On 104 (RXD, R)

Yes Observed activity on the receive data signal R/104 since the last status refresh.

No

106 (CTS) On Signal state of the control signal 106.

Off

NA NA (not available) is the displayed if the interface type is X.24-V.11 or RS485.



User ManualTUDA1



8.4.6.2 AP: / unit-x / port-y, Status - Maintenance

107 (DSR) On Signal state of the control signal 107.

Off


109 (DCD/I) On Signal state of the control signal 109.

Off

NA NA (not available) is displayed if the interface type is RS485.

142 (TM) On Signal state of the control signal 142 (loop indi-cation).

Off




Table 53: AP: / unit-x / port-y, Status - Maintenance


Line Status State In-Service Restore the normal operating state of the front port.

Test-Pattern-Insertion Insert a test pattern “01” towards the front port.Note that in the oversampling transmission mode the test pattern is generated with the sampling rate.For more information refer to section 7.3 DCE Interface Line State Maintenance (on page 109).

Out-Of-Service Simulate a failed TUDA1 unit.For more information refer to section 7.3 DCE Interface Line State Maintenance (on page 109).

User ManualTUDA1




When resetting the send time filter consequent action while the input signal still violates the filter conditions, traffic can be disturbed.

Please note:

The front-to-front loop 3b with subrates is transparent.

8.4.6.3 AP: / unit-x / port-y, Status - CTP

Loop Status State None Deactivate any loop.

Back-To-Back-2b Activate the back-to-back loop 2b.For more information refer to section 7.2 Loops (on page 106).

Front-To-Front-3b Activate the front-to-front loop 3b.For more information refer to section 7.2 Loops (on page 106).This loop is not available for the interface type RS485 2-wire.

Front-To-Front-3c Activate the front-to-front loop 3c.For more information refer to section 7.2 Loops (on page 106).This loop is not available for the interface type RS485 2-wire.

Reset Send Time Filter Consequent Action

Reset the consequent action from a violation of the transmit signal send time or idle time filter condition.The consequent action can be reset if the consequent action mode is set to “Persistent” or to “Auto-Reset”.

Table 53: AP: / unit-x / port-y, Status - Maintenance (continued)


User ManualTUDA1



Table 54: AP: / unit-x / port-y, Status - CTP


Trail Status Working Trail, Remote CTP

<MO Address> Managed object address of the CTP (connec-tion termination point) where the P0-nc signal is connected to, e.g. /unit-21/port-1/chan-1.

Working Trail, Sta-tus

OK No failure on the received signal.

SF Signal Fail status on the received signal.

CAS AIS CAS AIS status in the received signal, i.e. a “1111” signal in the signalling pattern of the first used time slot.

SD Signal Degraded status on the received signal.

Not Available The status of the received signal is not available, e.g. when the CTPs role is a-end in a unidirec-tional connection.

Protecting Trail, Remote CTP


Protecting Trail, Status






Active Trail Working The trail from the a-end working remote CTP has been selected.

Protecting The trail from the a-end protecting remote CTP has been selected.

Not Available There is no active trail.

External Request Request Release Automatic trail selection.

Force Working Force the selector to use the trail from the a-end working remote CTP.

Force Protecting Force the selector to use the trail from the a-end protecting remote CTP.

Manual Working Prefer the trail from the a-end working remote CTP. Use this trail only if the fault status is not worse than the fault status of the protecting trail.

Manual Protecting Prefer the trail from the a-end protecting remote CTP. Use this trail only if the fault status is not worse than the fault status of the working trail.

User ManualTUDA1



8.5 AP: / unit-x / port-y, y = 5

8.5.1 AP: / unit-x / port-y, Overview






8.5.2 AP: / unit-x / port-y, Main

8.5.2.1 AP: / unit-x / port-y, Main - General




8.5.2.2 AP: / unit-x / port-y, Main - Admin And Oper Status

Table 55: AP: / unit-x / port-y, Main - Admin And Oper Status


Administrative Sta-tus

State Up Set the IETF administrative status of the port (RFC 2863).

Down

Operational Status State Up Display of the IETF operational status of the port (RFC 2863).

Down

Testing

Unknown

Dormant

Not Present

Lower Layer Down

User ManualTUDA1



8.5.3 AP: / unit-x / port-y, Configuration

8.5.3.1 AP: / unit-x / port-y, Configuration - QoS

8.5.3.2 AP: / unit-x / port-y, Configuration - PHY

Table 56: AP: / unit-x / port-y, Configuration - QoS


QoS, Mapping Pro-file

Name <List of downloaded QoS map-ping profiles>

Select the appropriate profile from the drop down list.

Preview This command opens a window displaying the parameters of the actually selected pro-file. The contents are identical to those described in section 8.2 Profiles (on page 118).

Default Priority 0 … 7 Default 802.1p priority for untagged packets

Priority Source IP Check the DSCP field of the IP header to determine the priority of the packet.

MAC Check the 802.1p priority bits of the MAC header to determine the priority of the packet.

IP Then MAC Check the DSCP field if it exists, otherwise check the 802.1p priority bits to determine the priority of the packet.

MAC Then IP Check the 802.1p priority bits if they exist, otherwise check the DSCP field to determine the priority of the packet.

User ManualTUDA1




The LAN mode of the host connected to the TUDA1 Ethernet port must be configured to the same PHY mode as the TUDA1 Ethernet port, e.g. both ports configured to “auto-negotiation” or both ports configured to “100 Mbit/s full duplex”.

→ Mixed configurations result in a non operational state of the Ethernet interface.

8.5.3.3 AP: / unit-x / port-y, Configuration - TDM

Table 57: AP: / unit-x / port-y, Configuration - PHY


PHY Mode PHY Mode Autonegotiation Select the LAN mode of the Ethernet inter-face.

10 Mbit/s Full Duplex

10 Mbit/s Half Duplex

100 Mbit/s Full Duplex

100 Mbit/s Half Duplex

Table 58: AP: / unit-x / port-y, Configuration - TDM


TDM Rate 64 … 1984 kbit/s Select the transport rate of the TDM WAN interface.Values can be selected in steps of 64 kbit/s.

User ManualTUDA1



8.5.3.4 AP: / unit-x / port-y, Configuration - CTP

Please note:


→ To change a parameter the port has to be deleted and newly created with the modified parameters.

Table 59: AP: / unit-x / port-y, Configuration - CTP


CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is P0_nc, i.e. n x 64 kbit/s.The layer rate property of a TUDA1 Ethernet port is fixed to P0_nc.

n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-sible range is from 1 to 32.The number of time slots of a TUDA1 Ethernet port is fixed in the range 1 to 31.

Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of P0_nc, e.g. 1 … 31.The timeslot(s) property of a TUDA1 port is empty.


Connection Index 0 … 65’535 Index of a connection assigned to the port. With-out a connection the parameter is empty


Unidirectional

User ManualTUDA1



Please note:


8.5.4 AP: / unit-x / port-y, Fault Management





Local Role z-End The port is the ending point of a connection.Please refer to [314] User Guide “TDM Services and Cross Connections in XMC20”

a-End Working The port is the working starting point of a pro-tected or unprotected connection.

a-End Protecting The port is the protecting starting point of a pro-tected connection.

Remote Role z-End The CTP at the connections remote end is the ending point of a connection.Please refer to [314] User Guide “TDM Services and Cross Connections in XMC20”




Enable revertive protection switching.The z-End will preferably select the working a-End.Non-revertive protection switching is only availa-ble for ports with the number of timeslots n=1.Non-revertive protection switching for n>1 will be available in a future release,





Table 59: AP: / unit-x / port-y, Configuration - CTP (continued)


User ManualTUDA1



Please note:


8.5.5 AP: / unit-x / port-y, Performance Management


The PM parameters are presented in different groups. The following counter groups are available for the TUDA1 Ethernet port:

• “Protection” group, see section 8.5.5.1 AP: / unit-x / port-y, Performance Management - Protection (on page 158),

• “MIB-2 Ethernet Interface” group, see section 8.5.5.2 AP: / unit-x / port-y, Performance Management - MIB-2 Ethernet Interface (on page 158).

• “MIB-2 TDM Interface” group, see section 8.5.5.3 AP: / unit-x / port-y, Performance Management - MIB-2 TDM Interface (on page 159).

The following counter intervals are available, depending of the counter group:

Table 60: AP: / unit-x / port-y, Fault Management


Default Severity

Description

LOSETH Ethernet Link Down Communica-tion Alarm

Major Loss of the incoming Ethernet signal.

LOSTDM TDM Link Down Communica-tion Alarm

Major Loss of the incoming TDM data signal.The alarm is activated if no activity is detected in the TDM signal.Note: The alarm is also activated if the remote station sends no HDLC-flags in the idle state. In this case disable the alarm monitoring.


Major Trail signal fail (TSF) from the P12 trans-port unit is active, or CAS AIS active (only available if CAS AIS supervision is enabled).In a protected connection the working AND the protecting path have failed.



Minor Trail signal fail (TSF) from the P12 trans-port unit is active, or CAS AIS active (only available if CAS AIS supervision is enabled).In a protected connection the working OR the protecting path has failed.In an unprotected connection this fault cause is not applicable.


Counter interval Protection MIB-2 Ethernet Interface

MIB-2 TDM Inter-face

User Counter yes yes yes

History 15min yes yes yes

History 24h yes yes yes

User ManualTUDA1



8.5.5.1 AP: / unit-x / port-y, Performance Management - Protection

8.5.5.2 AP: / unit-x / port-y, Performance Management - MIB-2 Ethernet Interface

Alarm 15min no no no

Alarm 24h no no no

Table 61: PM counter interval availability (continued)

Counter interval Protection MIB-2 Ethernet Interface

MIB-2 TDM Inter-face




Table 63: PM group: MIB-2 Ethernet Interface


In Octets The total number of octets received on the interface, including framing characters

In Unicast Packets The number of unicast packets, i.e. packets with a single address delivered to a higher-layer protocol.

In Non-unicast Packets The number of multicast or broadcast packets deliv-ered to a higher-layer protocol.

In Discards The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for dis-carding such a packet could be to free up buffer space.

In Errors The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.

Out Octets The total number of octets transmitted out of the interface, including framing characters.

Out Unicast Packets The total number of unicast packets that higher-level protocols requested to be transmitted, including those that were discarded or not sent.

Out Non-unicast Packets The total number of multicast or broadcast packets that higher-level protocols requested to be transmit-ted, including those that were discarded or not sent.

Out Discards The number of outbound packets which were cho-sen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.

Out Errors The number of outbound packets that could not be transmitted because of errors.

User ManualTUDA1



8.5.5.3 AP: / unit-x / port-y, Performance Management - MIB-2 TDM Interface

8.5.6 AP: / unit-x / port-y, Status

8.5.6.1 AP: / unit-x / port-y, Status - PHY

Table 64: PM group: MIB-2 TDM Interface


In Octets The total number of octets received on the interface, including framing characters

In Unicast Packets The number of unicast packets, i.e. packets with a single address delivered to a higher-layer protocol.

In Non-unicast Packets The number of multicast or broadcast packets deliv-ered to a higher-layer protocol.

In Discards The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for dis-carding such a packet could be to free up buffer space.

In Errors The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.

Out Octets The total number of octets transmitted out of the interface, including framing characters.

Out Discards The number of outbound packets which were cho-sen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.

Out Errors The number of outbound packets that could not be transmitted because of errors.

Table 65: AP: / unit-x / port-y, Status - PHY


PHY State Speed Link Down Speed state of the Ethernet port.

100 Mbit/s

10 Mbit/s

Unknown

User ManualTUDA1



8.5.6.2 AP: / unit-x / port-y, Status - TDM

8.5.6.3 AP: / unit-x / port-y, Status - Bridge

Duplex Link Down Duplex state of the Ethernet port.

Full Duplex

Half Duplex

Unknown

IEEE 802.3 Flow Control

State of the flow control configuration.

Table 65: AP: / unit-x / port-y, Status - PHY (continued)


Table 66: AP: / unit-x / port-y, Status - TDM


Link Status State Up The TDM link status is up if there is activity on the TDM link.The TDM link status is down if there is no activity on the TDM link.Note that the port operational state follows the link status.

Down

Unknown

Table 67: AP: / unit-x / port-y, Status - Bridge


MAC Table MAC Address 00:00:00:00:00:00 … ff:ff:ff:ff:ff:ff

Shows the MAC address of the remote port.

Ingress Interface TDM Shows the local bridge ingress interface.

Ethernet

Expires In 0 … 300 [s] MAC address expiration time in seconds.The MAC address aging timer has a fixed value of 300 s.

User ManualTUDA1



8.5.6.4 AP: / unit-x / port-y, Status - CTP

Table 68: AP: / unit-x / port-y, Status - CTP





















User ManualTUDA1








Table 68: AP: / unit-x / port-y, Status - CTP (continued)


User ManualTUDA1



8.6 AP: / unit-x / conf-z

8.6.1 AP: / unit-x / conf-z, Overview


− “Overview - Alarms”, and

− “Overview - Cross Connections”


8.6.2 AP: / unit-x / conf-z, Main

8.6.2.1 AP: / unit-x / conf-z, Main - General




8.6.3 AP: / unit-x / conf-z, Configuration

8.6.3.1 AP: / unit-x / conf-z, Configuration - General

“Create Participant” and “Delete Participant” dialogues:

Table 69: AP: / unit-x / conf-z, Configuration - General


Create Participant …

Open the dialogue to add a participant to a conference.

Create Participant Index 0 … 255 Select the participant index number.0 is a reserved value used for the auto-assignment of a participant index: The auto-assigned index is the lowest available index number.In the ECST GUI the default value is the autoassigned index number.

User ManualTUDA1



Delete Participant …

Open the dialogue to delete a conference participant.

Delete Participant Participant All Delete all or a specific conference partici-pant.

part-1 … part-n

Table 69: AP: / unit-x / conf-z, Configuration - General (continued)


User ManualTUDA1



8.7 AP: / unit-x / conf-z / part-a

8.7.1 AP: / unit-x / conf-z / part-a, Overview






8.7.2 AP: / unit-x / conf-z / part-a, Main

8.7.2.1 AP: / unit-x / conf-z / part-a, Main - General




8.7.2.2 AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status

8.7.3 AP: / unit-x / conf-z / part-a, Configuration

Please note that the fields for some of the configuration parameters are con-text sensitive. Configuration parameters that are not available due to a higher-ranking configuration parameter are indicated as “NA” (not available).

Table 70: AP: / unit-x / conf-z / part-a, Main - Admin And Oper Status


Operational Status State Up Display of the IETF operational status of the par-ticipant (RFC 2863).The operational status is up when a cross con-nection to another CTP is configured.

Down

Testing

Unknown

Dormant

Not Present

Lower Layer Down

User ManualTUDA1



The steering parameters for the participant configuration are

• Conference Rate,

• CAS usage.

8.7.3.1 AP: / unit-x / conf-z / part-a, Configuration - General

Table 71: AP: / unit-x / conf-z / part-a, Configuration - General


Participant Signalling To Con-ference

Yes The control signal processing of a participant at the conference input can be enabled or disabled.Please refer to section 5.5.5 Conference Control Signal Handling (on page 77) for a description of this parameter.

No

NA NA (not available) is the only configurable value if the participant rate is 1984 kbit/s (no CAS available) or 56 kbit/s without signalling.

Signalling From Conference

Yes The control signal processing of a participant at the conference output can be enabled or disabled.Please refer to section 5.5.5 Conference Control Signal Handling (on page 77) for a description of this parameter.

No


User ManualTUDA1



8.7.3.2 AP: / unit-x / conf-z / part-a, Configuration - Subrate

Role Local In the point-to-multipoint and multipoint-to-multipoint linear network applications the conferences used in the different network elements (NE) have local connections, a con-nection towards the master NE head end and a connection towards the slave NE tail end.The connection role of a participant must be configured according to the NE type.Please refer to section 5.2 Network Applica-tions (on page 48) for a description of the dif-ferent NE types’ connections.

To-Master

To-Slave

Conditional Inter-connection

Yes This parameter allows to disconnect partici-pants from a conference input if the control signal C/105 is in the inactive state.Please refer to section 5.5.5 Conference Control Signal Handling (on page 77) for a description of this parameter.

No


Table 71: AP: / unit-x / conf-z / part-a, Configuration - General (continued)


Table 72: AP: / unit-x / conf-z / part-a, Configuration - Subrate


Subrate Subrate Framing V.110 Defines the subrate framing format.Please refer to section 5.5.5 Conference Control Signal Handling (on page 77) for a description of this parameter.

X.30

NA NA (not available) is the only configurable value if the participant rate is at 56 kbit/s without signalling or at 64 kbit/s or higher.

User ManualTUDA1



8.7.3.3 AP: / unit-x / conf-z / part-a, Configuration - CTP

Please note:


→ To change a parameter the conference has to be deleted and newly created with the modified parameters.

Table 73: AP: / unit-x / conf-z / part-a, Configuration - CTP


CTP Configuration Layer Rate P0_nc Layer rate of the connection termination point is P0_nc, i.e. n x 64 kbit/s.The layer rate property of a TUDA1 conference participant is fixed to P0_nc.

n 0 … 2 characters Number of timeslots in case of P0_nc. The pos-sible range is from 1 to 32.The number of time slots of a TUDA1 conference participant is fixed in the range 1 to 31.

Timeslot(s) 0 … 64 characters Used timeslots in a structured P12 in case of P0_nc, e.g. 1 … 31.The timeslot(s) property of a TUDA1 conference participant is empty.


Connection Index 0 … 65’535 Index of a connection assigned to the partici-pant. Without a connection the parameter is empty


Unidirectional

User ManualTUDA1



Please note:


8.7.4 AP: / unit-x / conf-z / part-a, Fault Management





Local Role z-End The participant is the ending point of a connec-tion.Please refer to [314] User Guide “TDM Ser-vices and Cross Connections in XMC20”

a-End Working The participant is the working starting point of a protected or unprotected connection.

a-End Protecting The participant is the protecting starting point of a protected connection.

Remote Role z-End The CTP at the connections remote end is the ending point of a connection.Please refer to [314] User Guide “TDM Ser-vices and Cross Connections in XMC20”




Enable revertive protection switching.The z-End will preferably select the working a-End.Non-revertive protection switching is only availa-ble for participants with the number of timeslots n=1.Non-revertive protection switching for n>1 will be available in a future release,





Table 73: AP: / unit-x / conf-z / part-a, Configuration - CTP (continued)


User ManualTUDA1



Please note:




→ A mismatch of the user data rates configured for two connected user ports or conference participants cannot be detected. The “Loss Of Frame” alarm is not activated.

8.7.5 AP: / unit-x / conf-z / part-a, Performance Management


The PM parameters are presented in different groups. The following counter group is available for the TUDA1 conference participants:

• “Protection” group, see section 8.7.5.1 AP: / unit-x / conf-z / part-a, Per-formance Management - Protection (on page 171),

The following counter intervals are available:

Table 74: AP: / unit-x / conf-z / part-a, Fault Management


Default Severity

Description



Warning A maintenance function has been acti-vated by the operator from the partici-pant status dialogue.


Major Trail signal fail (TSF) from the P12 trans-port unit is active, or - CAS AIS active (only available if CAS

is enabled), or- LOF is active.In a protected connection the working AND the protecting path have failed.



Minor Trail signal fail (TSF) from the P12 trans-port unit is active, or - CAS AIS active (only available if CAS

is enabled), or- LOF is active.In a protected connection the working OR the protecting path has failed.In an unprotected connection this fault cause is not applicable.

LOF Loss Of Frame Communica-tion Alarm

Major Loss of the V.110 or X.30 frame align-ment

RLOF Remote Loss Of Frame Communica-tion Alarm

Minor Loss of the V.110 or X.30 frame align-ment at the remote equipment. The alarm indication is transported in the X bit of the V.110 or X.30 frame.

User ManualTUDA1



8.7.5.1 AP: / unit-x / conf-z / part-a, Performance Management - Protection

8.7.6 AP: / unit-x / conf-z / part-a, Status

8.7.6.1 AP: / unit-x / conf-z / part-a, Status - General


Counter interval Protection

User Counter yes

History 15min yes

History 24h yes

Alarm 15min no

Alarm 24h no




User ManualTUDA1



Table 77: AP: / unit-x / conf-z / part-a, Status - General


To Conference Data 0 Logical state of the data signal going to the con-ference.

1

Activity On Data Yes Activity on the data signal going to the confer-ence since the last status refresh.With subrates the activity is checked on the framed data signal.

No

CAS 0000 … 1111 Signalling bits abcd going to the conference.

NA NA (not available) is displayed if CAS is disa-bled.

S 0 Logical state of the subrate frame S bit (X.30) going to the conference.

1

NA NA (not available) is displayed if the rate is at 64 kbit/s or above, i.e. without subrates, or when the subrate framing is V.110.

SA 0 Logical state of the subrate frame SA bit (V.110) going to the conference.

1

NA NA (not available) is displayed if the rate is at 64 kbit/s or above, i.e. without subrates, or when the subrate framing is X.30.

SB 0 Logical state of the subrate frame SB bit (V.110) going to the conference.

1


X 0 Logical state of the subrate frame X bit (X.30 or V.110) going to the conference.

1

NA NA (not available) is displayed if the rate is at 64 kbit/s or above, i.e. without subrates.

From Conference Data 0 Logical state of the data signal coming from the conference.

1

Activity On Data Yes Activity on the data signal coming from the con-ference since the last status refresh.With subrates the activity is checked on the framed data signal.

No

CAS 0000 … 1111 Signalling bits abcd coming from the conference.

NA NA (not available) is displayed if CAS is disa-bled.

S 0 Logical state of the subrate frame S bit (X.30) coming from the conference.

1

NA NA (not available) is displayed if the rate is at 64 kbit/s or above, i.e. without subrates, or when the subrate framing is V.110.

User ManualTUDA1



8.7.6.2 AP: / unit-x / conf-z / part-a, Status - Maintenance

SA 0 Logical state of the subrate frame SA bit (V.110) coming from the conference.

1


SB 0 Logical state of the subrate frame SB bit (V.110) coming from the conference.

1


X 0 Logical state of the subrate frame X bit (X.30 or V.110) coming from the conference.

1

NA NA (not available) is displayed if the rate is at 64 kbit/s or above, i.e. without subrates.

Table 77: AP: / unit-x / conf-z / part-a, Status - General (continued)


Table 78: AP: / unit-x / conf-z / part-a, Status - Maintenance


Line Status State In-Service Restore the normal operating state of the partici-pant.

Test-Pattern-Insertion Insert a test pattern “01” towards the participants conference.For more information refer to section 7.3 DCE Interface Line State Maintenance (on page 109).

Out-Of-Service Simulate a failed TUDA1 unit.For more information refer to section 7.3 DCE Interface Line State Maintenance (on page 109).

User ManualTUDA1



8.7.6.3 AP: / unit-x / conf-z / part-a, Status - CTP

Table 79: AP: / unit-x / conf-z / part-a, Status - CTP





















User ManualTUDA1








Table 79: AP: / unit-x / conf-z / part-a, Status - CTP (continued)


User ManualTUDA1


Annex

9 Annex

9.1 Associated XMC20 Documents

Any version(s) and/or release(s) indicated with the below listed document titles identify the specific state of the software and/or feature set at the crea-tion time of the present document. If the present document is published as part of a document collection, the hyperlinks might open a document valid for a newer version/release. That updated version is valid in the context of all units and features described in the document collection.

Please note:

For the HTML-based documentation site there are no interdocument hyper-links realized yet.

→ Please find the required document via the navigation tree on the left.

[012] Release Note “XMC20”

[201] System Description “XMC20”

[202] Safety Instructions “Precautions and safety”

[301] User Guide “XMC25 Installation”



[302] User Guide “XMC25/XMC23/XMC22”

[323] User Guide “Management Communication”

[354] Quick Guide “ECST”

[355] User Manual “ECST”

[314] User Guide “TDM Services and Cross Connections in XMC20”

[340] Quick Guide “TDM Services over PDH/SDH”

[447] User Manual “COGE5, COGE5-F co5ne_r2, co5un_r2”

[410] User Manual “SELI8 seli8_r5”

[433] User Manual “STM14 stm14_r3”

[506] User Manual “XMC20 cables”

User ManualTUDA1


Annex

[915] Technical Bulletin “Feature Licences for XMC20”

9.2 Technical Support

Please refer to the KEYMILE Extranet (via http://www.keymile.com) for sup-port contact information.

9.3 Product Training

Training courses are available for a wide range of KEYMILE products and applications.

For contact information, course descriptions, locations and dates, refer to the Website: http://www.keymile.com, then search for “product training”.



Date post:	12-Apr-2018
Category:	Documents
Upload:	dinhtram
View:	225 times
Download:	6 times