Part 1

ascom
UMUX from Ascom, covers all your

communication requirements in one
system.
Technical Descriptions Systems

(UCST R5A)
Preface to
Technical System Description
UMUX 1500/1200
EN/LZVBU 221 115/1 RA

Note: This document does not claim integrity and accuracy in detail.
This document is protected by copyright. All rights in this c onnection remain

with Ascom Transmission AG.
We reserve the right to make changes at any time without prior notice.
Order number:
Ascom Transmission AG
Belpstrasse 37
CH-3000 Bern 14
Switzerland © August 2001 by Ascom Transmission AG
ascom
Table of contents i
About this document 1- 1
Purpose 1- 1
The products 1- 1
The technical description 1- 2
Information on pictographs 1- 3
Leading pictographs 1- 3
Complementary pictographs 1- 4
Finding information ... 1- 6
... on referenced documents 1- 6
... on equipment and functions 1- 6
... on cables 1- 7
... on software 1- 7
... on ordering 1- 8
References 1- 9
Internal references and documentation 1- 9
... sorted by “Ref. No.” 1- 12
... sorted by “Commercial Customer Documentation” 1- 15
Glossary 1- 20
Compatibility of UCST/UMUX with Windows® 1- 37
Support 1- 38
Sales contact address: 1- 38
Technical support: 1- 38
Time tables 1- 38
Repairs 1- 38
Declarations of Conformity 2- 1
CE declaration 2- 2
AD 2000 declaration of conformity 2- 3
EN/LZVBU 221 115/1 RA Technical Descriptions System, Preface iii

ascom
About this document 1

Purpose
The products The UMUX 1500 and UMUX 1200 are Multi-service Access Systems
with an enhanced architecture providing higher capacity and more flexi-
bility than the UMUX 1300 and UMUX 1100(E).
Although featuring new functionalities, the UMUX 1500 and UMUX 1200
still preserve compatibility to the existing equipment, units and manage-
ment systems. The enhanced architecture allows ATR to continuously in-
troduce new types of high capacity PBUS and SBUS traffic units. The
UMUX 1500 and UMUX 1200 provide software download for all these
units and an enhanced inventory management. The UMUX 1200 has vari-
ous powering options including mains powering with battery backup.
The operation and maintenance concept for the UMUX platform relies on
the UCST and UNEM management software:
• The UCST software is the basic management tool for the commissioning,
operation and performance monitoring of the UMUX multi-service access
systems and all the other equipment of the UMUX and xDSL equipment
family.
It is possible to connect the UCST locally (local craft device) or from
remote (via modem) to the NEs. The UCST is required for the basic
configuration and commissioning of each NE, including the configura-
tion required, to establish a suitable communication with the man-
agement network. It is possible to use the UCST for the management
and performance control of the NEs in small networks.
The UCST software (32-bit versions / R5<X>) runs on PC/computers
under the Windows operating systems
− ME
− 98
− 2000
− NT4
While the UCST R5<X> manages the UMUX 1500 and UMUX 1200
Multi-service Access Systems, it supports all the other equipment of
the UMUX platform and all related products (xDSL systems, desktop
units).
• The UNEM software offers additional functions, such as network
management, more performance and automatic polling of the NEs
and is required to manage and control the performance of medium to
large networks.
EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-1

ascom About this document
The UNEM is based on HP workstations (UNIX). The UNEM relies on a

sophisticated GUI which features multi-windows technique and user
friendly mouse driven “point & click” dialogues. For network related
operations such as fault and performance management, the UNEM
features a graphical network overview, with icons associated to the
UMUXs and NEs.
The technical description The technical descriptions provide technical data and descriptions of fea-
tures, functions and architecture of the UMUX multi-service access sys-
tems and their units.
The Technical Description released with the UCST R5A is an update to the
Technical Description released with the UCST R4E and consists of 2 new
binders:
1 Technical Descriptions System: Part 1
Updates UCST R5A
This binder provides updated technical system descriptions for the
− UMUX 1500
− UMUX 1200
within the above mentioned scope and is completed with informa-
tion for system evaluation and system application.
2 Technical Descriptions Unit: Part 1
Updates UCST R5A
This binder provides updated technical descriptions for selected
units
− Control units (UMUX 1500/1200)
− PBUS units
− SBUS units
− Special units
within the above mentioned scope and is completed with informa-
tion for unit application.
Please note that
• the UCST R5A binders contain updated versions of the sys-
tem and selected unit descriptions.
The UCST R5A documentation is an amendment to the cus-
tomer documentation released with the UCST R4E. For all
topics without a specific UCST R5A update, the UCST R4E
documentation is also valid for the UCST R5A.
• The above TDs (1 + 2) are contained in one physical binder
(EN/LZABU …).
1-2 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Ascom About this document
Information on pictographs
Leading pictographs
The STOP pictograph warns from risk of injury. The instructions
provided with the symbol have to be adhered to strictly, in or-
der to reduce or eliminate the risk. A complementary picto-
graph (not shown here, refer to paragraphs below) specifies the
kind of risk.
Ignoring the instructions provided with the STOP pictograph
may create danger to life!
The CAUTION pictograph warns from risk of system damage

and/or service interruption. The instructions provided with the
symbol have to be adhered to, in order reduce or eliminate that
risk. A complementary pictograph (not shown here, refer to
paragraphs below) specifies the kind of risk.
Ignoring the instructions provided wit the CAUTION pictograph
may lead to system damage and/or service interruptions!
The NOTE pictograph points out information, that is important
for system operation or that is not evident.
Ignoring information provided with the NOTE pictograph may
lead to service degradation and/or interruptions!

Complementary pictographs Complementary pictographs follow the leading pictograph and mediate
information on the kind of danger or on the nature of the warning sig-
nalled by the leading pictograph (NOTE has no complementary picto-
graph). The pictographs provided signal
• risks of injury
• functional risks
• general information on risks and important aspects of installation,
maintenance and environmental
The lists following provide an overview over the most important comple-
mentary pictographs used in the UMUX customer documentation.
Risks of injury
Signals hazardous voltages and warns from touching equipment
or parts thereof carrying hazardous voltages!
Generic sign which signals the presence of hazardous voltages!
Signals the presence of invisible laser radiation!
Signals danger for your eyes due to physically (laser), chemically

and/or mechanically active substances!
Signals activities and/or procedures which carry a significant po-

tential of injury!
Functional risks
Signals the immediate danger of
• a system and/or subsystem crash
• loss of a function.
Signals possible bugs and/or malfunctions.

Installation, maintenance and

environmental
Danger of electrical arc-over, disruptive discharges or short cir-
cuits.
Danger of flammable or potentially explosive gas mixtures.
ESD sensitive, related to ESD.
EMC sensitive, related to EMC.
Grounding sensitive, related to grounding.
General information on maintenance.
Temperature sensitive, related to temperatures.
Distance sensitive, related to distances.
Restricted access, related to access permissions.

Finding information ...

... on referenced documents Documents are referenced with a 3-digit code which is valid throughout
the UMUX customer documentation.
This preface provides a summary of references resolving the internal 3-
digit code to the titles and identification/ordering numbers of the corre-
sponding documents. The summary additionally provides information on
the commercial documentation that contains these documents.
... on equipment and The customer documentation for the UMUX is organised by subjects
functions (overviews, system descriptions, user guides) on the logical level and by
systems/units on the equipment level.
• Overviews provide descriptions for groups of systems and their inter-
action (application) or for a group of similar systems/units.
• Technical descriptions are available on the system and unit level. The
technical descriptions include functional descriptions, and detailed
technical data. The technical system descriptions additionally provide
information on compatibility of system and units/software and on sys-
tem design.
• User guides provide instructions, procedures and information for in-
stallation, commissioning and operation of equipment and related
functions. The user guides include in particular descriptions of the
dialogues produced by the EM for corresponding functions. User
guides are available on system, unit and on functional level.
The Technical (System) Descriptions provide all the technical
data/specifications (and selected ordering information) that ap-
ply for the corresponding system or unit!
The following steps will help you to find and collect the information you
need:
1. Determine the topic of information you need (planning/application,
technical data, ordering, installation, operation, maintenance).
2. Determine which system/unit contains the function(s) of which you
need information.
3. Select the appropriate document:
- Overviews and technical descriptions for network and
system planning.
- Technical descriptions for system design and unit data
- User guides for installation, operation and maintenance
of the equipment
4. Determine the commercial customer documentation containing the
selected documents.
Depending on the function, the equipment and the aspect of which you
need information (e.g. system and unit), you have to consult one or sev-
eral documents.
For the identification of the documents within the commercial customer
documentation, refer to the paragraphs on references below.

... on cables Throughout the UMUX customer documentation (UMUX 1500 and
UMUX 1200), cables are identified with an internal reference code. This
internal reference allows expressive and logical identification of the cables
with respect to their application and the physical location of the corre-
sponding connector.
The syntax of the internal reference complies with the following rules:
UnitName/Cx.y-z (example: COBUX/C1.1-2)
C: Designs an electrical cable reference
F: Designs an optical fibre cable
x: Connector frame of the unit (front view: bottom left first, top right
last)
y: Connector module within connector frame (front view: bottom first)
z: Version number of the cable (optional), if there are several versions
of cables for the same connector frame/module available.
Please note that:
• It is not possible to use the internal cable reference for or-
dering!
• The <UnitName> does not necessarily match the name of
the unit with which you use the cable. Some of the cables
are compatible with several units!
... on software There is software available for the UMUX 1500/1200 and their subsystems
as follows:
• UCST software
is required to implement the EM for the basic configuration and op-
eration control of the NEs.
• UNEM software
is required to implement the EMS for the network management and
the configuration and operation of the NEs.
• Embedded software (unit SW)
to download to the NEs is required for units featuring software
download.
The user guide [401] provides information on installation, features and
generic functions of the UCST.
The system and unit user guides provide detailed information on the UCST
dialogues which allow you to control and mange the unit specific func-
tions and applications.
The technical system description [202] and the release note [043] provide
detailed information on the functional units (unit hardware and ESW)
available with the UCST R5A as well as information on compatibility. The
user guide [302] describes the procedures for the installation of the Em-
bedded SW (ESW).
The chapter on “System and Ordering Information” in the technical sys-
tem description [202] provides general information on features, designa-
tion, compatibility and availability.

... on ordering The chapter on “System and Ordering Information” in the technical sys-
tem description [202] provides general information on features, designa-
tion, compatibility and availability. The UMUX 1500 and 1200 technical
system descriptions provide a resolution table for the cable references and
ordering numbers (chapter "System and Ordering Information").
For detailed information and ordering, please contact your sales represen-
tative.

References
Internal references and Documents are referenced with a 3-digit code which is valid throughout
documentation the UMUX customer documentation (UMUX 1500 and UMUX 1200). This
code may reference to a
• commercial customer documentation
• printed matter integrated as an element into a commercial documentation
Please note that:
• Reference numbers in the range [001] ... [099] refer to gen-
eral documentation ATR. The numbers [101] ... [999] specify
printed matter (documents) in conformity with the UMUX
customer documentation principles.
• In most cases it is not possible to use the specified document
numbers for ordering, since the commercial customer
documentation consists of sets of documents. The reference
numbers are used for identification of the documents within
these sets. This number is printed on each page of the
document (bottom left).
• For ordering information for the commercial customer
documentation, refer also to the release notes.
The two types of tables below resolve the internal references as follows:
1 List of documents sorted by their reference number.
2 List of documents sorted according to the structure of the
commercial customer documentation.
The columns in the tables below provide information as follows (header of rows):
Ref. 3-digit reference number (in-
ternal to the customer docu-
mentation).
Document Number Identification or ordering
number (if applicable) of the
document or documentation
(on each page bottom left).
RS Release State of the document
(printed with the document
number on each page).
Vol./Sect. Short name for the volume or
the section within the volume
(internal for information and
orientation only!)
Title Title of the docu-
ment/documentation
Structural Doc. Id Identifier which steers the inte-
gration of the document within
the commercial documentation
(binders etc.).
This identifier is provided for in-
formation and orientation only!

Please note that:

• The structural documentation identifier is valid for a particu-
lar release of the customer documentation only! It may
change to the next release of the customer documentation!
• Not all documents provide a structural documentation iden-
tifier. Commercial customer documents never provide such
identifier.
The Structural Documentation Identifier is read as follows:
TDS.u15.1.3.7
Rank within section

Section within volume
Volume
Product identification
Type of documentation
Short names and abbreviations used in the

• “Structural Doc. Id” row:
− Type of documentation:
NEM UNEM document
TDS Technical Description System
TDU Technical Description Units
UGS User Guide System
UGU User Guide Units
UGX User Guide UMUX general
RNO Release notes and Overviews
− Product type identification:
bp basic package
np network package
nem network element manager
u13 UMUX 1300/1100(E)
u15 UMUX 1500/1200
• “Vol./Sect”: row
Cust. Doc. Customer Documentation
Rel. Release
SD System Description (optional: Short name)
Sect. Section (optional: Short name)
SM System Manual (optional: Short name)
UG User Guide (optional: Short name)

Please note that the customer documentation for the UCST & UNEM
R5A consists of 2 complementary documentations:
• UCST & UNEM R5A updates for the system and selected unit User
Guides.
• UCST & UNEM R4E customer documentation for systems and units
that are functionally not affected.
To provide the full set of references that is used in the customer docu-
mentation, you find below for each table type ("sorted by reference
number", "sorted according to the structure of the commercial customer
documentation") 2 tables:
• Table that resolves the internal references for the UCST R5A updates
• Table that resolves the internal references for the UCST R4E docu-
mentation.
For the system operation with the UNEM / UCST R5A the UCST
& UNEM R5A updates replace the corresponding UCST &
UNEM R4E versions.

... sorted by “Ref. No.” Tab. 1-1: UCST & UNEM R5A updated and new documents
sorted by “Ref." number
Ref. Document Number RS Vol./Sect. Title Structural Doc. Id
[010] EN/LZTBU 110 101/2 RA SD UNEM UNEM Basic Package: System Description NEM.bp.1.1.1
[011] EN/LZTBU 310 101/2 RA UG UNEM UNEM Basic Package: User Guide NEM.bp.3.1.1
[012] EN/LZTBU 210 101/3 RA SM UNEM UNEM Basic Package: System Manual NEM.bp.2.1.1
[043] EN/LZTBU 980 404 RA Rel. note Release Note UCST R5A & UNEM R5A RNO.nem.2.0.4
[141] EN/LZTBU 990 105 RA Rel. note Limitations UCST & UNEM R5A and related functions RNO.nem.8.0.4
[202] 4/EN/LZTBU 220 115/1 RA Technical System Description UMUX 1500 TDS.u15.11.2.1
[220] EN/LZTBU 260 101/2 RA TD SYNIO 165, 605 TDU.u15.11.5.4
[221] EN/LZTBU 260 102/2 RA TD SYNIF 164, 604 & SYNIC 118, 168 TDU.u15.11.5.3
[222] EN/LZTBU 260 103/1 RC TD SYNAC 163 TDU.u15.11.5.1
[226] EN/LZTBU 260 104 RC TD SYNAM 116 TDU.u15.11.5.2
[231] EN/LZTBU 230 103 RB TD COBUL 215 TDU.u15.11.1.3
[233] EN/LZTBU 240 106 RA TD LECAF 070 TDU.u15.11.6.2
[234] EN/LZTBU 240 107 RA TD TUNOF 284 TDU.u15.11.6.3
[237] EN/LZTBU 250 503 RA TD LESA8 085 & LESAP 095 TDU.u15.11.4.3
[302] 4/EN/LZTBU 320 115/1 RA UG System UMUX 1500 UGS.u15.11.2.1
[320] EN/LZTBU 360 101/2 RA UG SYNIO 165, 605 UGU.u15.21.2.4
[321] EN/LZTBU 360 102/2 RA UG SYNIF 164, 604 & SYNIC 118, 168 UGU.u15.21.2.3
[322] EN/LZTBU 360 103/1 RC UG SYNAC 163 UGU.u15.21.2.1
[326] EN/LZTBU 360 104 RC UG SYNAM 116 UGU.u15.21.2.2
[331] EN/LZTBU 330 103 RB UG COBUL 215 UGU.u15.11.1.3
[333] EN/LZTBU 340 106 RA UG LECAF 070 UGU.u15.21.3.2
[334] EN/LZTBU 340 107 RA UG TUNOF 284 UGU.u15.21.3.3
[337] EN/LZTBU 350 503 RA UG LESA8 085 & LESAP 095 UGU.u15.21.1.1
[401] 4/EN/LZTBU 310 101/1 RA UCST/System Operation Basics R5A UGS.u15.11.4.1
[501] EN/LZTBU 330 901 RA UG 75 Ohm Patch Panel
[502] EN/LZTBU 880 101/1 RA POTS Splitter, Application note
[701] EN/LZTBU 380 201/1 RA SM MUSIC MUSIC 100, User Manual

Tab. 1-2: UCST & UNEM R4E documents

sorted by “Ref." number
[001] EN/LZBBU 301 013/11 RD UG U1300 User's Guide Part 1: System description, Installation, UCST UGS.u13.1.0.0
U1100 and Guidelines
[002] EN/LZBBU 341 013/11 RC UG Units User's Guide Part 2: Units Vol. 1/2 UGU.u13.21.0.0
[002] EN/LZBBU 341 013/12 RB UG Units User's Guide Part 2: Units Vol. 2/2 UGU.u13.22.0.0
[003] Cust. Doc. UMUX system: Reliability data summary
[011] EN/LZTBU 310 101/1 RC UG UNEM UNEM Basic Package: UG NEM.bp.3.1.1
[012] EN/LZTBU 210 101/2 RB SM UNEM UNEM Basic Package: System Manual NEM.bp.2.1.1
[013] EN/LZTBU 313 101/1 RA UG UNEM Glossary of Alarms UMUX NEM.bp.3.1.2
[040] EN/LZTBU 980 401 RA Rel. note Release Note UCST R4C & UNEM R4 RNO.nem.2.0.0
[041] EN/LZTBU 980 402 RC Rel. note Release Note UCST R4D & UNEM R4D RNO.nem.2.0.1
[042] EN/LZTBU 980 403 RC Rel. note Release Note UCST R4E & UNEM R4E RNO.nem.2.0.3
[100] EN/LZTBU 120 101 RA Overview UMUX System Overview and Applications RNO.nem.1.0.0
[211] EN/LZTBU 230 501 RC TD POSUS 106 TDU.u15.11.2.1
[212] EN/LZTBU 250 301/2 RB TD PHLC1 125 TDU.u15.11.4.6
[213] EN/LZTBU 230 102/2 RC TD COBUQ 144 TDU.u15.11.1.1
[214] EN/LZTBU 250 101/3 RA TD PCONV 121,131,143 TDU.u15.11.4.4
[215] EN/LZTBU 230 101/3 RA TD COBUV 137,237 & COBUX 145,146 TDU.u15.11.1.2
[216] EN/LZTBU 250 201/3 RA TD LOMIF 101, 120, 140 & LOMI4 150 TDU.u15.11.4.3
[218] EN/LZTBU 240 101/1 RB TD ISBUQ 130 TDU.u15.11.3.2
[219] EN/LZTBU 250 102/1 RA TD PCON2 115,142 TDU.u15.11.4.5
[220] EN/LZTBU 260 101/1 RA TD SYNIO 165 TDU.u15.11.5.4
[221] EN/LZTBU 260 102/1 RA TD SYNIF 164 & SYNIC 118 TDU.u15.11.5.3
[222] EN/LZTBU 260 103/1 RB TD SYNAC 163 TDU.u15.11.5.1
[224] EN/LZTBU 240 102/1 RA TD LECA2 056 & LE2Q2 244 TDU.u15.11.3.1
[225] EN/LZTBU 240 104 RC TD ISBUT 110 TDU.u15.11.3.3
[226] EN/LZTBU 260 104 RA TD SYNAM 116 TDU.u15.11.5.2
[227] EN/LZTBU 250 501/1 RA TD LEMU6 236 & LEMQ6 148 TDU.u15.11.4.2
[228] EN/LZTBU 250 502/1 RA TD LAWA4 235 TDU.u15.11.4.1
[229] EN/LZTBU 230 502 RA TD POSUA 206 & BATMO TDU.u15.11.2.2
[230] EN/LZTBU 250 303 RA TD PHLC3 126 TDU.u15.11.4.8
[232] EN/LZTBU 240 105 RA TD TUNOL 299 & TUNOR TDU.u15.11.3.4
[235] EN/LZTBU 230 503 RA TD PODIS 033 & POSUR TDU.u15.11.2.3
[236] EN/LZTBU 290 101 RA TD ETHUB 193, 194 TDU.u15.11.6.1
[302] 4/EN/LZTBU 320 115 RE UG System UMUX 1500 UGS.u15.11.2.1
[303] 4/EN/LZTBU 320 112 RA UG System UMUX 1200 UGS.u15.11.3.1
[311] EN/LZTBU 330 501 RC UG POSUS 106 UGU.u15.11.2.1
[312] EN/LZTBU 350 301/2 RA UG PHLC1 125 UGU.u15.21.1.6
[313] EN/LZTBU 330 102/2 RC UG COBUQ 144 UGU.u15.11.1.1
[314] EN/LZTBU 350 101/3 RA UG PCONV 121, 131, 143 UGU.u15.21.1.4
[315] EN/LZTBU 330 101/3 RA UG COBUV 137, 237 & COBUX 145, 146 UGU.u15.11.1.2
[316] EN/LZTBU 350 201/3 RA UG LOMIF 101, 120, 140 & LOMI4 150 UGU.u15.21.1.3
[317] EN/LZTBU 350 302/2 RB UG PHLC2 129 UGU.u15.21.1.7
[318] EN/LZTBU 340 101/1 RB UG ISBUQ 130 UGU.u15.11.3.2
[319] EN/LZTBU 350 102/1 RA UG PCON2 115, 142 UGU.u15.21.1.5

[320] EN/LZTBU 360 101/1 RB UG SYNIO 165 UGU.u15.21.2.4

[321] EN/LZTBU 360 102/1 RB UG SYNIF 164 & SYNIC 118 UGU.u15.21.2.3
[322] EN/LZTBU 360 103/1 RB UG SYNAC 163 UGU.u15.21.2.1
[324] EN/LZTBU 340 102/1 RA UG LECA2 056 & LE2Q2 244 UGU.u15.11.3.1
[325] EN/LZTBU 340 104 RC UG ISBUT 110 UGU.u15.11.3.3
[326] EN/LZTBU 360 104 RB UG SYNAM 116 UGU.u15.21.2.2
[327] EN/LZTBU 350 501/1 RB UG LEMU6 236 & LEMQ6 148 UGU.u15.21.1.2
[328] EN/LZTBU 350 502/1 RB UG LAWA4 235 UGU.u15.21.1.1
[329] EN/LZTBU 330 502 RA UG POSUA 206 & BATMO UGU.u15.11.2.2
[330] EN/LZTBU 350 303 RA UG PHLC3 126 UGU.u15.21.1.8
[332] EN/LZTBU 340 105 RA UG TUNOL 299 & TUNOR UGU.u15.11.3.4
[335] EN/LZTBU 330 503 RA UG PODIS 033 & POSUR UGU.u15.11.2.3
[336] EN/LZTBU 390 101 RA UG ETHUB 193, 194 UGU.u15.21.3.1
[401] 4/EN/LZTBU 310 101 RG UCST/System Operation Basics R4E UGS.u15.11.4.1
[701] EN/LZTBU 380 201 RA SM SOHO System COLT soho User manual
[901] EN/LZTBU 910 101 RA Management Communication UMUX UGS.u15.21.1.1
[902] EN/LZTBU 920 101 RA Network Functions UMUX UGS.u15.21.2.1
[903] 2/198 23- RA Cust. Doc. V5.x Questionnaire UMUX 1200/1500
COZBU 120 101/1 Uen (First contact)
[904] 1/159 01- RA Cust. Doc. V5.x Provisioning Checklist
COZBU 120 101/1 Uen UMUX 1200/1500
[905] 1/155 35- RA Cust. Doc. Leased line via a V5-Interface, and its application for
FZFBU 101 019 Uen UMUX-Management
[906] 3/198 23- RA Cust. Doc UMUX V5 explanation booklet
COZBU 120 101/1 Uen
[907] 1/198 23- RC Cust. Doc V5.x Questionnaire UMUX 1200/1500
COZBU 120 101/1 Uen (Deep level version)
Please note that:

• For documents which are assigned at the same time to the
UMUX 1200/1500 and the UMUX 1100(E)/1300, the table
shows only the relationship to the UMUX 1200/1500 cus-
tomer documentation.
• The complete UMUX and UNEM customer documentation is
available on CD-ROM.
• The UMUX V5.x provisioning document [906] is provided
with V5 sales projects only.
• The reliability data summary [003] is available on request
only.

... sorted by “Commercial Tab. 1-3: UCST & UNEM R5A updated and new documents
Customer Documentation” sorted by the structure of the
“Commercial Customer Documentation”
EN/LZTBU 980 702/x RA Rel. note UNEM R5A Basic Package RNO.nem.4.0.4
EN/LZTBU 980 702/xy RA Rel. note Appendix 4 Rel. note UNEM R5A; S. Pack y RNO.nem.4.1.4
[141] EN/LZTBU 990 105 RA Rel. note Limitations UCST & UNEM R5A and related functions RNO.nem.8.0.4
RNO.nem.9.0.0
EN/LZABU 150 201 RA Set of TDs Technical Descriptions: TDS.u15.11.0.0
Amendments UCST R5A
EN/LZBBU 201 216/11 RA TD NE Technical Descriptions Systems: Part 1 TDS.u15.11.0.1
Updates UCST R5A
EN/LZVBU 221 115/1 RA Sect. 1 Preface TDS.u15.11.1.0
1/EN/LZTBU 221 115/1 RA About This Document TDS.u15.11.1.1
2/EN/LZTBU 221 115/1 RA Declarations of Conformity TDS.u15.11.1.2
EN/LZVBU 222 215/1 RA Sect. 2 UMUX 1500 TDS.u15.11.2.0
EN/LZVBU 222 212/1 RA Sect. 3 UMUX 1200 TDS.u15.11.3.0
TDS.u15.11.9.0
EN/LZBBU 203 216/11 RA TD Units Technical Descriptions Units: Part 1 TDU.u15.11.0.1
Updates UCST R5A
EN/LZVBU 232 401/2 RA Sect. 1 Control Units TDU.u15.11.1.0
[231] EN/LZTBU 230 103 RB TD COBUL 215 TDU.u15.11.1.3
EN/LZVBU 252 501/1 RA Sect. 4 PBUS Units TDU.u15.11.4.0
[237] EN/LZTBU 250 503 RA TD LESA8 085 & LESAP 095 TDU.u15.11.4.3
EN/LZVBU 262 701/1 RA Sect. 5 SBUS Units TDU.u15.11.5.0
[222] EN/LZTBU 260 103/1 RC TD SYNAC 163 TDU.u15.11.5.1
[226] EN/LZTBU 260 104 RC TD SYNAM 116 TDU.u15.11.5.2
[221] EN/LZTBU 260 102/2 RA TD SYNIF 164, 604 & SYNIC 118, 168 TDU.u15.11.5.3
[220] EN/LZTBU 260 101/2 RA TD SYNIO 165, 605 TDU.u15.11.5.4
EN/LZVBU 292 901/1 RA Sect. 6 Special Units TDU.u15.11.6.0
[233] EN/LZTBU 240 106 RA TD LECAF 070 TDU.u15.11.6.2
[234] EN/LZTBU 240 107 RA TD TUNOF 284 TDU.u15.11.6.3
TDU.u15.11.9.0
EN/LZBBU 301 216/11 RA UG NE User Guide Systems: Part 1 UGS.u15.11.0.1
Updates UCST R5A
EN/LZVBU 321 115/1 RA Sect. 1 Preface UGS.u15.11.1.0
1/EN/LZTBU 321 115/1 RA About This Document UGS.u15.11.1.1
3/EN/LZTBU 321 115/1 RA Precautions and Safety UGS.u15.11.1.2
EN/LZVBU 322 215/1 RA Sect. 2 UMUX 1500 UGS.u15.11.2.0
EN/LZVBU 322 212/1 RA Sect. 3 UMUX 1200 UGS.u15.11.3.0
EN/LZVBU 312 301/1 RA Sect. 4 UCST/System Operation Basics UGS.u15.11.4.0
[401] 4/EN/LZTBU 310 101/1 RA UCST/System Operation Basics R5A UGS.u15.11.4.1
UGS.u15.11.9.0
EN/LZABU 150 301 RA Set of UGs User Guides Units: UGS.u15.11.0.0
Amendments UCST R5A
EN/LZBBU 303 216/11 RA UG Units User Guide Units: Part 1 UGU.u15.11.0.1
Updates UCST R5A
EN/LZVBU 332 401/2 RA Sect. 1 Control Units UGU.u15.11.1.0
[331] EN/LZTBU 330 103 RB UG COBUL 215 UGU.u15.11.1.3


UGU.u15.11.9.0
Updates UCST R5A
EN/LZVBU 352 501/1 RA Sect. 1 PBUS Units UGU.u15.21.1.0
[337] EN/LZTBU 350 503 RA UG LESA8 085 & LESAP 095 UGU.u15.21.1.1
EN/LZVBU 362 701/1 RA Sect. 2 SBUS Units UGU.u15.21.2.0
[322] EN/LZTBU 360 103/1 RC UG SYNAC 163 UGU.u15.21.2.1
[326] EN/LZTBU 360 104 RC UG SYNAM 116 UGU.u15.21.2.2
[321] EN/LZTBU 360 102/2 RA UG SYNIF 164, 604 & SYNIC 118, 168 UGU.u15.21.2.3
[320] EN/LZTBU 360 101/2 RA UG SYNIO 165, 605 UGU.u15.21.2.4
EN/LZVBU 392 901/1 RA Sect. 3 Special Units UGU.u15.21.3.0
[333] EN/LZTBU 340 106 RA UG LECAF 070 UGU.u15.21.3.2
[334] EN/LZTBU 340 107 RA UG TUNOF 284 UGU.u15.21.3.3
UGU.u15.21.9.0
[012] EN/LZTBU 210 101/3 RA SM UNEM UNEM Basic Package: System Manual NEM.bp.2.1.1
[011] EN/LZTBU 310 101/2 RA UG UNEM UNEM Basic Package: User Guide NEM.bp.3.1.1
NEM.bp.9.0.0
[701] EN/LZTBU 380 201/1 RA SM MUSIC MUSIC 100, User Manual

[501] EN/LZTBU 330 901 RA UG 75 Ohm Patch Panel
[502] EN/LZTBU 880 101/1 RA POTS Splitter, Application note

Tab. 1-4: UCST & UNEM R4E documents

sorted by the structure of the “Commercial Customer
Documentation”
[100] EN/LZTBU 120 101 RA Overview UMUX System Overview and Applications RNO.nem.1.0.0
[040] EN/LZTBU 980 401 RA Rel. Note Release Note UCST R4C & UNEM R4 RNO.nem.2.0.0
[041] EN/LZTBU 980 402 RC Rel. Note Release Note UCST R4D & UNEM R4D RNO.nem.2.0.1
[042] EN/LZTBU 980 403 RC Rel. Note Release Note UCST R4E & UNEM R4E RNO.nem.2.1.3
[043] EN/LZTBU 980 404 RA Rel. Note Release Note UCST R5A & UNEM R5A RNO.nem.2.1.3
EN/LZTBU 980 701/1 RA Rel. note UNEM R4E Basic Package RNO.nem.3.1.0
EN/LZTBU 980 701/1y RB Rel. note Appendix 4 Rel. note UNEM R4E; S. Pack y RNO.nem.3.1.1
RNO.nem.9.0.0
EN/LZBBU 201 215/11 RB TD NE Technical Descriptions Systems: Part 1 TDS.u15.11.0.1
EN/LZVBU 221 115 RE Sect. 1 Preface TDS.u15.11.1.0
1/EN/LZTBU 221 115 RE About This Document TDS.u15.11.1.1
2/EN/LZTBU 221 115 RE Declarations of Conformity TDS.u15.11.1.2
EN/LZVBU 222 215 RE Sect. 2 UMUX 1500 TDS.u15.11.2.0
[202] 4/EN/LZTBU 220 115 RE Technical System Description UMUX 1500 TDS.u15.11.2.1
EN/LZVBU 222 212 RA Sect. 3 UMUX 1200 TDS.u15.11.3.0
[203] 4/EN/LZTBU 220 112 RA Technical System Description UMUX 1200 TDS.u15.11.3.1
TDS.u15.11.9.0
EN/LZBBU 203 215/11 RB TD Units Technical Descriptions Units: Part 1 TDU.u15.11.0.1
EN/LZVBU 232 401/1 RA Sect. 1 Control Units TDU.u15.11.1.0
[213] EN/LZTBU 230 102/2 RC TD COBUQ 144 TDU.u15.11.1.1
[215] EN/LZTBU 230 101/3 RA TD COBUV 137,237 & COBUX 145,146 TDU.u15.11.1.2
EN/LZVBU 232 401/2 RA Sect. 2 Power Units TDU.u15.11.2.0
[211] EN/LZTBU 230 501 RC TD POSUS 106 TDU.u15.11.2.1
[229] EN/LZTBU 230 502 RA TD POSUA 206 & BATMO TDU.u15.11.2.2
[235] EN/LZTBU 230 503 RA TD PODIS 033 & POSUR TDU.u15.11.2.3
EN/LZVBU 242 601 RD Sect. 3 UBUS Units TDU.u15.11.3.0
[224] EN/LZTBU 240 102/1 RA TD LECA2 056 & LE2Q2 244 TDU.u15.11.3.1
[218] EN/LZTBU 240 101/1 RB TD ISBUQ 130 TDU.u15.11.3.2
[225] EN/LZTBU 240 104 RC TD ISBUT 110 TDU.u15.11.3.3
[232] EN/LZTBU 240 105 RA TD TUNOL 299 & TUNOR TDU.u15.11.3.4
EN/LZVBU 252 501 RE Sect. 4 PBUS Units TDU.u15.11.4.0
[228] EN/LZTBU 250 502/1 RA TD LAWA4 235 TDU.u15.11.4.1
[227] EN/LZTBU 250 501/1 RA TD LEMU6 236 & LEMQ6 148 TDU.u15.11.4.2
[216] EN/LZTBU 250 201/3 RA TD LOMIF 101, 120, 140 & LOMI4 150 TDU.u15.11.4.3
[214] EN/LZTBU 250 101/3 RA TD PCONV 121,131,143 TDU.u15.11.4.4
[219] EN/LZTBU 250 102/1 RA TD PCON2 115,142 TDU.u15.11.4.5
[230] EN/LZTBU 250 303 RA TD PHLC3 126 TDU.u15.11.4.8
EN/LZVBU 262 701 RC Sect. 5 SBUS Units TDU.u15.11.5.0
[222] EN/LZTBU 260 103/1 RB TD SYNAC 163 TDU.u15.11.5.1
[226] EN/LZTBU 260 104 RA TD SYNAM 116 TDU.u15.11.5.2
[221] EN/LZTBU 260 102/1 RA TD SYNIF 164 & SYNIC 118 TDU.u15.11.5.3
[220] EN/LZTBU 260 101/1 RA TD SYNIO 165 TDU.u15.11.5.4
EN/LZVBU 292 901 RA Sect. 6 Special Units TDU.u15.11.6.0
[236] EN/LZTBU 290 101 RA TD ETHUB 193, 194 TDU.u15.11.6.1

TDU.u15.11.9.0
EN/LZBBU 301 215/11 RE UG NE User Guide Systems: Part 1 UGS.u15.11.0.1
EN/LZVBU 321 115 RE Sect. 1 Preface UGS.u15.11.1.0
1/EN/LZTBU 321 115 RE About This Document UGS.u15.11.1.1
3/EN/LZTBU 321 115 RE Precautions and Safety UGS.u15.11.1.2
EN/LZVBU 322 215 RE Sect. 2 UMUX 1500 UGS.u15.11.2.0
[302] 4/EN/LZTBU 320 115 RE UG System UMUX 1500 UGS.u15.11.2.1
EN/LZVBU 322 212 RA Sect. 3 UMUX 1200 UGS.u15.11.3.0
[303] 4/EN/LZTBU 320 112 RA UG System UMUX 1200 UGS.u15.11.3.1
EN/LZVBU 312 301 RE Sect. 4 UCST/System Operation Basics UGS.u15.11.4.0
[401] 4/EN/LZTBU 310 101 RG UCST/System Operation Basics R4E UGS.u15.11.4.1
UGS.u15.11.9.0
EN/LZBBU 301 215/21 RA UG NE User Guide Systems: Part 2 UGS.u15.21.0.1
EN/LZVBU 912 401 RA Sect. 1 Management Communication UMUX UGS.u15.21.1.0
[901] EN/LZTBU 910 101 RA Management Communication UMUX UGS.u15.21.1.1
EN/LZVBU 922 501 RA Sect. 2 Network Functions UMUX UGS.u15.21.2.0
[902] EN/LZTBU 920 101 RA Network Functions UMUX UGS.u15.21.2.1
UGS.u15.21.9.0
EN/LZBBU 303 215/11 RC UG Units User Guide Units: Part 1 UGU.u15.11.0.1
EN/LZVBU 332 401/1 RA Sect. 1 Control Units UGU.u15.11.1.0
[313] EN/LZTBU 330 102/2 RC UG COBUQ 144 UGU.u15.11.1.1
[315] EN/LZTBU 330 101/3 RA UG COBUV 137, 237 & COBUX 145, 146 UGU.u15.11.1.2
EN/LZVBU 332 401/2 RA Sect. 2 Power Units UGU.u15.11.2.0
[311] EN/LZTBU 330 501 RC UG POSUS 106 UGU.u15.11.2.1
[329] EN/LZTBU 330 502 RA UG POSUA 206 & BATMO UGU.u15.11.2.2
[335] EN/LZTBU 330 503 RA UG PODIS 033 & POSUR UGU.u15.11.2.3
EN/LZVBU 342 601 RD Sect. 3 UBUS Units UGU.u15.11.3.0
[324] EN/LZTBU 340 102/1 RA UG LECA2 056 & LE2Q2 244 UGU.u15.11.3.1
[318] EN/LZTBU 340 101/1 RB UG ISBUQ 130 UGU.u15.11.3.2
[325] EN/LZTBU 340 104 RC UG ISBUT 110 UGU.u15.11.3.3
[332] EN/LZTBU 340 105 RA UG TUNOL 299 & TUNOR UGU.u15.11.3.4
UGU.u15.11.9.0
EN/LZVBU 352 501 RE Sect. 1 PBUS Units UGU.u15.21.1.0
[328] EN/LZTBU 350 502/1 RB UG LAWA4 235 UGU.u15.21.1.1
[327] EN/LZTBU 350 501/1 RB UG LEMU6 236 & LEMQ6 148 UGU.u15.21.1.2
[316] EN/LZTBU 350 201/3 RA UG LOMIF 101, 120, 140 & LOMI4 150 UGU.u15.21.1.3
[314] EN/LZTBU 350 101/3 RA UG PCONV 121, 131, 143 UGU.u15.21.1.4
[319] EN/LZTBU 350 102/1 RA UG PCON2 115, 142 UGU.u15.21.1.5
[312] EN/LZTBU 350 301/2 RA UG PHLC1 125 UGU.u15.21.1.6
[317] EN/LZTBU 350 302/2 RB UG PHLC2 129 UGU.u15.21.1.7
[330] EN/LZTBU 350 303 RA UG PHLC3 126 UGU.u15.21.1.8
EN/LZVBU 362 701 RC Sect. 2 SBUS Units UGU.u15.21.2.0
[322] EN/LZTBU 360 103/1 RB UG SYNAC 163 UGU.u15.21.2.1
[326] EN/LZTBU 360 104 RB UG SYNAM 116 UGU.u15.21.2.2
[321] EN/LZTBU 360 102/1 RB UG SYNIF 164 & SYNIC 118 UGU.u15.21.2.3
[320] EN/LZTBU 360 101/1 RB UG SYNIO 165 UGU.u15.21.2.4
EN/LZVBU 392 901 RA Sect. 3 Special Units UGU.u15.21.3.0
[336] EN/LZTBU 390 101 RA UG ETHUB 193, 194 UGU.u15.21.3.1

UGU.u15.21.9.0
[001] EN/LZBBU 301 013/11 RD UG U1300 User's Guide Part 1: System description, Installation, UGS.u13.1.0.0
U1100 UCST and Guidelines
EN/LZVBU 321 113 RB Sect. 1 Preface to Part 1 UGS.u13.11.1.0
EN/LZVBU 322 213 RA Sect. 2 System Description UGS.u13.11.2.0
EN/LZVBU 322 313 RA Sect. 3 Installation UGS.u13.11.3.0
EN/LZVBU 312 413 RA Sect. 4 UCST 2.5d UGS.u13.11.4.0
EN/LZVBU 312 513 RD Sect. 5 UCST/System Operation Basics UGS.u13.11.5.0
EN/LZTBU 310 101/1 RE UCST/System Operation Basics R4E UGS.u13.11.5.1
EN/LZVBU 312 613 RA Sect. 6 Guidelines UGS.u13.11.6.0
UGS.u13.11.9.0
[002] EN/LZBBU 341 013/11 RC UG Units User's Guide Part 2: Units Vol. 1/2 UGU.u13.21.0.0
EN/LZVBU 341 113 RA Sect. 1 Basic units UGU.u13.21.1.0
EN/LZVBU 341 213 RA Sect. 2 Analog units UGU.u13.21.2.0
EN/LZVBU 341 313 RA Sect. 3 Data units UGU.u13.21.3.0
UGU.u13.21.9.0
[002] EN/LZBBU 341 013/12 RB UG Units User's Guide Part 2: Units Vol. 2/2 UGU.u13.22.0.0
EN/LZVBU 341 413 RB Sect. 4 Transmission units UGU.u13.22.4.0
EN/LZVBU 341 513 RA Sect. 5 HDSL units UGU.u13.22.5.0
EN/LZVBU 391 613 RA Sect. 6 Special units UGU.u13.22.6.0
UGU.u13.22.9.0
[012] EN/LZTBU 210 101/2 RB SM UNEM UNEM Basic Package: System Manual NEM.bp.2.1.1
[011] EN/LZTBU 310 101/1 RC UG UNEM UNEM Basic Package: UG NEM.bp.3.1.1
[013] EN/LZTBU 313 101/1 RA UG UNEM Glossary of Alarms UMUX NEM.bp.3.1.2
NEM.bp.9.0.0
[701] EN/LZTBU 380 201 RA SM SOHO System COLT soho User manual
[003] Cust. Doc. UMUX system: Reliability data summary
[903] 2/198 23- RA Cust. Doc. V5.x Questionnaire UMUX 1200/1500

COZBU 120 101/1 Uen (First contact)
[904] 1/159 01- RA Cust. Doc. V5.x Provisioning Checklist
COZBU 120 101/1 Uen UMUX 1200/1500
[905] 1/155 35- RA Cust. Doc. Leased line via a V5-Interface, and its application for UMUX-
FZFBU 101 019 Uen Management
[906] 3/198 23- RA Cust. Doc UMUX V5 explanation booklet
COZBU 120 101/1 Uen
[907] 1/198 23- RC Cust. Doc V5.x Questionnaire UMUX 1200/1500
COZBU 120 101/1 Uen (Deep level version)
Please note that:

• A "Document number" printed in a shaded grey line is the
ordering number for the corresponding commercial docu-
mentation (booklet or binder).
• The complete UMUX and UNEM customer documentation is
available on CD-ROM.
• The UMUX V5.x provisioning document [906] is provided
with V5 sales projects only.
• The reliability data summary [003] is available on request
only.

Glossary
Abbreviations Meaning Explanations
ADM Add-Drop-Multiplexer Multiplexer which adds and drops traffic signals

for local use to and from the aggregate signal.
AFI Authority and Format Identifier The first part of the IDP of an OSI (NSAP) address
that specifies the type (and the responsible
authority) of the address (second part: IDI).
AGC Automatic Gain Control Signal level is automatically adapted to compen-
sate attenuation of the line length or conditions.
AIS Alarm Indication Signal
ALCAR Alarm unit with 24 binary inputs, 4 command
outputs and 4 ports for serial communication.
ALS Automatic Laser Shutdown Mechanism to switch of the Laser in TX direction
for security reason.
AN Access Network Any system (distributed or monolithic) between
the LE and the user
AC Alternate Current
Active Closed State of the working contact if the relay is actively
driven.
AO Active Open State of the working relay contact if the relay is
actively driven.
APDSW Application Download SoftWare UMUX software which loads the ESW from the
Apdsw EM to the MIB of the NE.
APS Automatic Protection Switching Protects section or trails/paths in the network by
switching traffic to a protecting section / trail in
case of failure of the active section/trail.
ARD Automatic Ring Down Mode of the SUBLA. The SUBLA in the ARD
mode provides a locally timed sequence of ring-
ing signals.
ARP Address Resolution Protocol
ASD Acceleration Spectral Density
AS Autonomous System OSPF expression: Entity of systems that use a
common routing strategy and are managed by a
common administration.
AT Available Time Starts with 10 consecutive ESs (included in AT)
and ends with 10 consecutive SESs (not included
in AT)
ATM Asynchronous Transfer Mode ATM allows the transmission of virtually any
traffic data (and speed) by means of standardised
data packets via the network.
Example of an ATM product: ATR light ring.
ATR Ascom Transmission Limited Provider of Multiservice Access and xDSL trans-
mission equipment
ATU Asynchronous Transfer Unit ATU is a third party product used for the concen-
tration of management access.
AU-n Administrative Unit, level n Level of the SDH multiplexing structure.
AUG-n Administrative Unit Group, level n Ditto.

AUXP AUXiliary Pattern Bit pattern … 1010 … used for the signalling of
particular PRA conditions.
AWG American Wire Gauge Wire diameter unit used in USA
BA Basic Access 2B+D ISDN channel (2x64kb/s)
BATMO BATtery MOdule Installation set to implement an external battery
backup with the POSUA unit. The BATMO does
not include the batteries.
BBE Background Block Error
BBER Background Block Error Ratio
BHCA Busy Hour Call Attempts
BIP Bit Interleaved Parity Measurement method for detecting errors occur-
ring in a digital signal
BORSCHT Battery feed, Over-voltage protection, Common explanation of PSTN functions.
Ringing injection, Supervision, Codec,
Hybrid, and Testing
BR Border Router OSPF expression: Router that connects an OSPF
area to the backbone (area).
BRI Basic Rate Interface ISDN interface
C-n Container, level n Level of the SDH multiplexing structure. Often
the hierarchy type (European =2, American =1) is
amended to n.
CA Carrier Adapter PSTN Signalling mode for interworking between
AN and exchange.
CAP Carrier-less Amplitude Phase (Modulation) Modulation method specially adapted for the
data transmission via copper pairs in PSTN net-
works. CAP allows e.g. the transmission of 1168
kbit/s within a bandwidth of 278 kHz.
CAS Channel Associated Signalling The signalling information for each TS in the
frame is transmitted in the same TS and is syn-
chronised to the frame.
CCM Customer Configuration Management Database with data on equipment and customer
configuration allows you to identification and
trace materials
CCR Customer Configuration Registration Registration of data for the CCM database
CCS Common Channel Signalling
CENCA Control unit for UMUX 1100/1300, containing
the cross connect matrix and control and monitor
functionality for all the other UBUS Units.
CLK CLocK (Internal) Timing signal.
CLNP ConnectionLess Network Protocol Protocol for the data transfer in the OSI world
(equivalent to TCP/IP in the IP world).
CPE Customers Premises Equipment
CPS Customer Parameter Set Used in V5 applications to define the custom
specific parameters of the V5 interface.
COBU<X> Generic term for the COBUX and COBUV control
units of the UMUX 1200/1500. The units provide
central system control, synchronisation and fea-
ture the MIB for the NE, including the unit SW

for units with SWDL. The control units fit slots 11

and 12 (redundant unit only).
COBUL Control unit for the UMUX 1200/1500. The
COBUL provides access to 4 x 2 Mbit/s for the
UBUS and 128 x 2 Mbit/s for the PBUS) but pro-
vides no SDH, no voice, no ECC, no conference
or diagnostic functions.
COBUQ Control unit for the UMUX 1500 providing re-
duced functionality compared to COBU<X> (no
ECC, no conference or diagnostic functions,
access capacity limited to 4 x 2 Mbit/s for the
UBUS and 32 x 2 Mbit/s for the PBUS).
With the former UCST 3.3a/1: Control unit for
the NE UMUX 1400
COBUX Control unit for the UMUX 1200/1500. The unit
features serial, Ethernet and PDH/SDH ECC access
for management communication and Diagnostic
functions for traffic data channels. The COBUX
provides capacity for 2 times 4 x 2 Mbit/s UBUS
and 128 x 2 Mbit/s PBUS accesses.
COBUV Control unit for the UMUX 1200/1500. The same
features as the COBUX but with additional con-
ference functions for 64 kbit/s traffic data.
COLT Legacy name of the xDSL line terminal xDSL line terminal equipment provides data
equipment transmission via copper pairs and optical fibres.
xDSL equipment is available as units for subrack
(COpper Line Terminal) operation or as desktop units (e.g. MUSIC 100).
The functions and units are available for the
UMUX multiservice access system.
COLT soho Legacy name of the MUSIC 100. The MUSIC 100 is a desktop unit with Ethernet
interfaces and bridge/router functionality. MUSIC
100 uses xDSL transmission via copper pairs at
the aggregate side.
COM COMmon Common contact for the working relay contacts
(AO, AC).
CPU Central Processing Unit
CRC4 Cyclic Redundancy Check The cyclic redundancy check uses a 4th order
polynomial.
CU Control Unit
DAS D-channel ISDN: 64 kbit/s channel carrying the D-channel,
the Alarm-bit and the Service bits.
DB DataBase
DCC Data Communication Network
DCN Data Communication Network General term for communication networks. Often
used in the meaning of MCN.
DHCP Dynamic Host Configuration Protocol The DHCP allows the following process: The host
looks for a DHCP server and gets a temporary IP
address from the server if WINS is enabled.
DISC DISConnect Command of OSI user network
DNU Do Not Use

DS Digital Section
(Access Digital Section)
DSL Digital Subscriber Loop Describes the digital transmission via the (ana-
logue telephone) subscriber loop. DSL is used in
countless variations such as:
- ADSL Asymmetrical bit-rate DSL
- HDSL High bit rate DSL
- SDSL Symmetrical DSL
- MSDSL Multirate Symmetrical DSL
etc.
to closer indicated the particularity of the DSL
transmission.
DSLAM Digital Subscriber Line Access Multiplexer

DSP Domain Specific Part The second (of two) basic parts of an OSI (NSAP)
address (first part: IDP). The DSP consists of the
High Order DSP, the SID and the SEL.
DTMF Dual Tone Multi Frequency Used to transmit signalling information inband (in
the voice-band) of telecom networks.
DU Dial-Up
DUN Dial-Up Networking package Windows software for serial the implementation
of communication networks.
DXC Digital Cross Connect Switch fabric for the cross connection of signals,
here 2 Mbit/s and n x 64 kbit/s signals
E Erlang A measurement of occupancy ([E], but actually
without unit). International unit of average traffic
on a facility during a period of time (usually a
busy hour)
EA Element Agent UNEM functional block that serves a set of NEs.
The element agents of the UCST are sets of pa-
rameters which define the UCST access to a set
of NEs.
EB Errored Block A block of data with one or more bit errors.
EBR Errored Block Ratio
ECC Embedded Communication Channel System integrated data channel for the manage-
ment communication of the UMUX 1200/1500.
EF Envelope Function
EF Addr Envelope Function Address 13 bit number (for ISDN) which uniquely refer-
ences a user port within a V5 interface
EM Element Manager Managing tool for NEs:
UCST and the EM part of UNEM
EMC ElectroMagnetic Compatibility
EMS Element Manager System High performance managing tool for the man-
agement of NEs and networks of NEs:
UNEM, featuring networking functions and a
graphical network overview.
EN European Norm

EOC Embedded Operation Channel Independent data channel for the management
communication of NEs with F-interfaces.
EOW Engineering Order Wire Voice channel using overhead bits in a transmis-
sion system. Commonly used for service commu-
nication between different stations.
EPROM Erasable Programmable Read Only Mem-
ory
ER End Router OSPF expression: Router that terminates a virtual
link in the remote area.
ES Errored Second Second with one or more EBs
Electrical Section The section between two electrical STM-1 inter-
faces.
End System System that terminates the OSI protocol.
ESD Electrostatic Discharge
ESM PSTN Signalling mode for interworking between
AN and Ericsson exchange.
ESI Equipment Synchronisation Input Inputs on the COBU<X> for 2 MHz timing sig-
nals.
ESO Equipment Synchronisation Output Outputs on COBU<X> for 2 MHz timing signals.
ESR Errored Seconds Ratio
ESW Embedded SoftWare The ESW is the downloadable software for the
units with software download. Sometimes the
ESW is called the unit SW.
ET Elapsed Time Duration of measurement interval.
ET Exchange Terminal
ETHUB Ethernet HUB Hub unit with 5 10BaseT / 100BaseTX Ethernet
interfaces. Fits to the UMUX subracks but has no
bus access.
ETS European Telecommunication Standard
ETSI European Telecommunication Standards
Institute
EXBAT UBUS unit with 8 U-interfaces (4B3T coding) to
the ISDN exchange.
EXLA<X> Exchange Line Analogue UBUS unit with 12 POTS interfaces to the PSTN
interface of the exchange.
EXLIC UBUS unit with 8 U-interfaces (2B1Q coding) to
ISDN exchange.
E0 Electrical interface signal 64 kbit/s
E0-nc E0 n times concatenated
E-12 Short form for the first level of the European PDH
hierarchy (= 2 Mbit/s).
F Local Management Interface for UMUX NEs
FANUV FAN Unit 19-inch fan unit with 3 fans for rack installation.
The FANUV is used with the UMUX 1500 in con-
junction with heat deflection shields.

FANU2 FAN Unit 2 Integrated fan unit for the UMUX 1200 subrack.
The FANU2 is mandatory for horizontal operation
of the UMUX 1200.
FAS Frame Alignment Signal
FE Front End Used to locate loops, performance evaluation etc.
of traffic signals.
FEBE Far End Block Error
FOP Failure Of Protocol Failure of the protocol in the protecting channel
which controls the MSP (SYNIO).
FR Frame Relay
FRAD FRame Assembler Disassembler
FSP Frame Synchronisation Pulse Timing signal of the PBUS that indicates the start
of a frame
FTP File Transfer Protocol
FW Firmware
F15 F-interface of the UMUX 1200/1500.
GECOD G.703 CODirectional UBUS unit for 8 full duplex 64 kbit/s channels
according to ITU-T G.703.
GND GrouND Ground or zero volt potential of the power sup-
ply.
GSM Global System for Mobile applications
GSM-R Global System for Mobile applications
with Railways
GUI Graphical User Interface Mainly used in the context of UNEM
GWF GleichWellenFunk The GWF application requires a phase locked
relationship between the sent and the received
frames (MEGIF 272).
HDLC High Level Data Link Control
HIRAC UMUX HDSL modem with 5 interfaces for the
digital transmission of up to 1024 kbit/s over
copper pairs to the AM64/<xxx>-type remote
modems.
HU Height Unit Corresponds to 44.45 mm. Basic measure used
with the 19-inch construction practice.
HW Hardware
HWY Highway UBUS or PBUS Highway
ICN Internal Communication Network UMUX 1200/1500 internal communication struc-
ture.
ID Identifier Used together with a type of identifier (Customer
Id Id, User Id, Node Id etc.)
IDI Initial Domain Identifier Second part of the IDP of an OSI (NSAP) address
that specifies the domain and the institution
responsible for the address (first part: AFI).
IDP Initial Domain Part The first (of two) basic parts of an OSI (NSAP)
address (second part: DSP). The IDP consists of
the AFI and IDI.

ISP Internet Service Provider

IE Intermediate transmission Equipment U-interface Repeater equipment.
IEC International Electrotechnical Committee
IEEE Institute of Electrical and Electronic Engi-
neers
IF InterFace
If
IP Internet Protocol
IS Intermediate System Element of the OSI hierarchy
IS-IS Intermediate System-to-Intermediate
System Protocol
ISBUQ UBUS unit for UMUX 1100/1300 and UMUX
1200/1500 providing 8 ISDN-BRA user ports
(2B1Q) for V5.x applications.
ISBUT UBUS unit for UMUX 1100/1300 and UMUX
1200/1500 providing 8 ISDN-BRA user ports
(4B3T) for V5.x applications.
ISDN Integrated Services Digital Network
ISDN-BA ISDN - Basic Access Same meaning as ISDN-BRA Capacity: 2B+1D
channel
ISDN-BRA ISDN - Basic Rate Access Same meaning as ISDN-BA
ISDN-PRA ISDN - Primary Rate Access Capacity: 30B+1D channel
ISP Internet Service Provider
ITU-T International Telecommunication Union -
Telecommunication Standardisation Sec-
tor
I/F Interface
L3 Addr Layer 3 Address 15 bit number (for PSTN) which uniquely refer-
ences a user port within a V5 interface
LAN Local Area Network
LAWA4 PBUS unit that connects a local area network
(LAN) over a 10BaseT interface to UMUX units
with aggregate interfaces.
LE Local Exchange The local exchange provides the analogue tele-
phone and ISDN services.
LECAF Special unit with 2 xDSL IFs for twisted copper
pairs. The LECAF has no bus access and provides
front access for all signals and services. The xDSL
IFs are compatible with the LECA2 xDSL IFs.
LECAR Desktop unit with 2 DSL interfaces compatible
with LECA2 (CAP). The LECAR provides locally a 2
Mbit/s G.703/G.704 IF or n x 64 kbit/s
G.703/G.704, X.21/V.11, V35 or V.36 IFs.
Local 48 volt DC or mains powering.

LECA2 Family of UBUS units with 2 IFs for twisted cop-

per pairs and front or UBUS data access. The
LECA2 family supports xDSL services.
LECA2 uses CAP.
LED Light Emitting Diode
LEMQ6 PBUS unit that concentrates the xDSL IP-packed
oriented traffic of its 6 subscribers and transfers
the traffic to the local 10BaseT front interface or
to the PBUS cross connect.
The LEMQ6 uses the 2B1Q line code.
LEMU6 PBUS unit that concentrates the xDSL IP-packed
oriented traffic of its 6 subscribers and transfers
the traffic to the local 10BaseT front interface or
to the PBUS cross connect.
The LEMU6 supports CAP.
LESAP PBUS unit with 8 DSL IFs and 4 x 2 P12 PBUS
access. The LESAP provides up to 4 DSL services
via 1 pair or 2 pairs. Mixed modes are possible.
The current version supports the CAP line code.
Other codes are FUTURE OPTIONS.
The LESAP supports line powering for 1 DSL
service.
LESA8 PBUS unit with 8 DSL IFs and 8 x 2 P12 PBUS
access. The LESA8 provides up to 8 DSL services
via 1 pair or up to 4 DSL services via 2 pairs.
Mixed modes are possible.
The current version supports the CAP line code.
Other codes are FUTURE OPTIONS.
LE2QR Desktop unit with 2 DSL interfaces compatible
with LE2Q2 (2B1Q). The LE2QR provides locally a
2 Mbit/s G.703/G.704 IF or n x 64 kbit/s
G.703/G.704, X.21/V.11, V35 or V.36 IFs.
Local 48 volt DC or mains powering.
LE2Q2 Family of UBUS units with 2 IFs for twisted cop-
per pairs and front or UBUS data access. The
LECA2 family supports xDSL services.
The LECA2 uses the 2B1Q line code.
LFA Loss of Frame Alignment
LINTE Telephone line test unit for the UMUX
1300/1100(E). LINTE is no longer supported.
LOMIF PBUS unit for UMUX 1200/500 with 8 2 Mbit/s
interfaces G.703 for transparent or structured
signals. Performance monitoring, protection and
diagnostic functions are provided.
LOMI4 PBUS unit for UMUX 1200/1500 with 4 2 Mbit/s
interfaces G.703 for transparent or structured
signals. Performance monitoring, protection and
diagnostic functions are provided. Functionally
identical with the LOMIF.

LOS Loss Of Synchronisation

LSP Link State Protocol Protocol used with OSPF to update the link state
information for the routers.
LT Functional group for PRA applications. The LT
functional group consists of the 2 function blocks
LT-U and LT-V3.
LTE Line Terminal Equipment Used for interfaces providing direct termination
of the physical transmission (copper pairs, optical
fibres).
LTP Linear Trail Protection To protect VC-12 Tributaries over two STM-1
paths
LT-U Reference point for PRA applications. LT-U con-
nects the LT to the transmission (network) side.
LT-V3 Reference point for PRA applications. LT-V3 pro-
vides the reference point V3 for the UMUX net-
work (exchange side).
MAC Media Access Control Unique identifier (address) of the COBU<X> used
for addressing (QX-interface, NSAP with IP tun-
nelling)
MCAS Mercury CAS Proprietary CAS signalling system supported by
the SUBLA and PHLC<X> units.
MADT Mean Accumulated Down Time
MC Management Communication
MCN Management Communication Network The MCN is the network that transports the
management communication of the UMUX.
MDF Main Distribution Frame
MEGIF UBUS unit with 2 2 Mbit/s interfaces according to
ITU-T G.703/704.
MFA Multi Frame Alignment Indicates the alignment of the CRC-4 multi-frame
of structured 2 Mbit/s traffic signals.
MIB Management Information Base NE database which the COBU<X> manages.
MIRIG Ringing signal generator unit for the SUBL<X >
units in the UMUX 1100(E).
MON Monitored Fault reporting option „monitored“.
MS Multiplex Section The Multiplex Section Layer allows synchronisa-

tion routing information to be carried over the
STM-1 signal via the SSM (Synchronisation Status
Message).
MSP Multiplex Section Protection Protection of the Multiplex Section e.g. via the 2
optical ports of the SYNIO.
MS-DOSâ Microsoftâ Disk Operating System Microsoftâ and MS-DOSâ are trademarks of
Microsoft Corporation USA and world-wide.
MTBF Mean Time Between Failure
MTTF Mean Time To Failure
MTTR Mean Time To Repair

MTU Maximum Transmission Unit Maximum size of a data packet (number of oc-
MtU Maximum Transfer Unit tets) that is allowed for the medium (network).
Media Transfer Unit
MSDSL Multi service Symmetric Digital Subscriber Transmission rate for the subscriber line select-
Line able according to requirements. Same rates for
up- and downstream.
MUSIC 100 The MUSIC 100 is a desktop unit with Ethernet
interfaces and bridge/router functionality. MUSIC
100 uses xDSL transmission via copper pairs at
the aggregate side (legacy name of the COLT
soho).
NA Non-urgent Alarm
NAT Network Address Translation
NE Network Element The NE is the basic (manageable) element of the
network, normally a UMUX Multi-service Access
System or subrack based xDSL equipment.
NEM Network Element Manager Tool for the management of NEs and networks of
NEs:
UNEM, featuring networking functions and a
graphical network overview.
NEMCA UBUS unit with 8 analogue interfaces for 2- or 4-
wire voice and E+M signalling.
NEMGE UBUS unit with 8 analogue interfaces for 2- or 4-
wire voice and E+M signalling. High signal level
inputs.
NM Network Management
NMON Not monitored Fault reporting option „not monitored“
NSAP Network Service Access Point OSI address according to ISO 8348
NT Functional group for PRA applications. The NT
functional group consists of the 2 function blocks
NT1-U and NT1-T.
NTU Network Terminating Unit For example the NTU remote data unit for the
SULIS UBUS unit.
NT1-T Reference point for PRA applications. The NT1-T
provides the reference point T for the UMUX
network.
NT1-U Reference point for PRA applications. The NT1-U
connects the NT1 to the transmission (network)
side.
O&M Operation and Maintenance
ONP Open Network Provision ETSI specification (ETSI TBR12) for 2 Mbit/s leased
lines of public networks that are synchronised by
private network operators.
OOF Out Of Frame

OS Operating System Here: Software system of the NE including basic

and unit SW
Optical Section Deals with the Optical Section Layer on the STM-
1 side.
OSI Open Systems Interconnection Reference model for the system independent
interconnection of systems.
OSPF Open Shortest Path First Router protocol used for ECC routing with
COBUX.
The LEMU6 and LAWA4 support OSPF routing for
their subscriber traffic.
PBUS PBUS Internal highway structure implemented with
UMUX 1200/1500 for cross connection on 1/1
and 1/0 level. Depending on type of UMUX,
limitations on use apply.
PBX Private Branch Exchange
PC memory card PCMCIA card fitted to COBU<X>. Standard ca-
pacity 8 MBytes.
PCMCIA card Official name for PC memory card.
PCONV PBUS unit for the UMUX 1200/1500 providing
protocol conversion for 4 V5.1 interfaces or 1
V5.2 interface (2 2 Mbit/s links). The PCONV has
2 2 Mbit/s G.703 electrical interfaces for struc-
tured and unstructured signals.
PCON2 PBUS unit for the UMUX 1200/1500 providing
protocol conversion for 10 V5.1 interfaces and 1
V5.2 interface (8 2 Mbit/s links).
PDH Plesiochronous Digital Hierarchy
PDU Protocol Data Unit
PETS Plesiochronous Equipment Timing Source Timing system of for PDH traffic signals and
equipment.
PHA PBUS Highway Access Number of PBUS highways (each 2 Mbit/s of
traffic signals plus corresponding signalling) pres-
ently seized by a unit.
PHAU PBUS Highway Access Per Unit This UMUX specific figure provides the maximum
number of PBUS accesses per unit in 2 Mbit/s
accesses. This number is always a multiple of 4 (n
x 4, n = 0 … 32).
PHLC1 PSTN High density Line Card 3 slot wide PBUS unit for UMUX 1200/1500 with
60 PSTN subscriber line interfaces featuring sub-
scriber line test. Used with V5.x and other special
protocol based signalling systems.
PHLC2 Ditto Ditto for 30 subscribers
PHLC3 Ditto Ditto for 10 subscribers
PICS Performance Implementation Compliance Standard compliance lists for the definition of the
Statement national V5.x performance

PJE Pointer Justification Event A PJE is an inversion of the I- or D-bits of the

pointer, together with an increment or decre-
ment of the pointer value to signify a frequency
justification.
PJE counts are reported separately for pointer

increments (positive events) +PJE and decrements
(negative events) -PJE.
PLL Phase Locked Loop
PLS Physical LAN Signalling
PM Performance Monitoring Most UMUX units provide PM for their traffic
signals.
PMA Physical Medium Attachment A device that e.g. attaches the NE to a 10 BASE-T
Ethernet LAN.
PODIS POwerDIStribution Power distribution unit for the remote powering
of 4 HDSL CAP desktop units in conjunction with
the POSUR unit.
POP Point Of Presence
POTS Plain Old Telephone Service
POSUA Power supply unit for the UMUX 1200. It con-
verts the mains voltage first to the primary bat-
tery voltage and then to the internal VCC supply
voltages. The POSUA can drive an external bat-
tery for power backup (BATMO option).
POSUR Power Supply Remote Power source for the remote powering of the
LECAR/LE2QR and DSL regenerator in conjunc-
tion with the PODIS unit.
POSUS Power converter unit for the UMUX, which con-
verts the battery voltage to the internal power
supply voltages. The unit fits any slot in the
UMUX 1200/1500 subrack and can be operated
in parallel in order to build up protection.
PPP Point-to-Point Protocol
PRA Primary Rate Access The Primary Rate Access is an ISDN based func-
tion that provides a 2 Mbit/s access.
PRBS Pseudo Random Bit Sequence Sequence of bits with a random pattern of bits
which repeats after a number of bits (e.g. se-
quences of 1011-1, 1015-1, 1020-1 bits).
PRC Primary Reference Clock
PSC Protection Switch Count The PSC is a protection performance parameter
and provides information of the number of
switching events.
PSTN Public Switched Telephone Network
PVC Private Virtual Circuit
PW Password Used in context with User Classes, Customer Id
and System Access.
P0 64 kbit/s signal
P0-nc P0 n times concatenated

P12s 2Mbit/s signal, structured according to ITU-T

G.704
P12x 2Mbit/s signal, unstructured or with unknown
structure
Q1 Local Management Interface allowing to connect
several NEs
QL Quality Level 4-bit code in the TS 0 of a PCM frame (SSM)
indicating the "quality level" of the signal pro-
vided for synchronisation use.
QX LAN Management Interface
RAI Remote Alarm Indication
RAS Remote Access Service Modems for the remote access of NEs.
RDB Router DataBase Database of the (OSPF) router with the router
tables and link state information.
RDI Remote Defect Indication The Remote Defect Indication signal is repre-
senting the defection of the received signal.
REI Remote Error Indication The Remote Error Indicator signal is containing
the number of detected error detection code.
REN Ringer Equivalent Normal
RIGEN Ringing signal generator unit for the SUBL<X>
units in the UMUX 1300 and UMUX 1500.
ROM Read Only Memory
RPF Reference Publication Format The RPF notification for NSAP addresses is speci-
fied in the ITU-T standard X.213 and represents
the NSAP addresses in the format IDP + DSP.
RPS Remote Powering System Stands mostly for the remote powering system of
UMUX 500 equipment.
RS Regenerator Section The Regenerator Section Layer allows the STM-1
signal to be labelled with a STM-1 TTI for ensur-
ing that any incorrect connection of the wrong
optical signals is monitored and alarmed.
RX Interface which receives the signal (normally
Rx equal to input).
SABME Set Asynchronous Balanced Mode Ex- Command of OSI user network.
tended
SASE Stand Alone Synchronisation Equipment The SASE reconditions clock signals by eliminat-
ing jitter from the clock (function according to
ITU-T G.812). The UMUX do not provide this
function.
SbU Subunit Term of an generic element in the structure of
UMUX (refer to units)
SBUS UMUX 1200/1500 internal bus for cross connec-
tion of SDH signals.
SD Signal Degraded
SDH Synchronous Digital Hierarchy
SEC Synchronous Equipment Clock Block of the SETS timing system.

SEL Severely Errored Second Selector switch within the NSAP address. SEL is a
part of the DSP (other parts: High DSP, SID).
SES Severely Errored Second
SESR Severely Errored Second Ratio
SETS Synchronous Equipment Timing Source Timing system for SDH signals and equipment.
SETS P Synchronous Equipment Timing Source Protection of the SETS timing system.
Protection
SF Signal Fail
SID System IDentifier Sequence of the NSAP address that identifies the
system (=system address). The SID is a part of the
DSP (other parts: High DSP, SEL).
SIFOX SIxty-FOur kbit/s X.24 UBUS unit with 4 full-duplex synchronous 64
kbit/s interfaces (X.24 and V.11). Unit is required
to implement the EOC.
SNAP SubNetwork Access Point Same as SID
SNCP SubNetwork Connection Protection
SNCP/I SNCP with Inherent monitoring For P12x, P0-nc signals
SNCP/N SNCP with Non-intrusive monitoring For P12s signals
SNI Service Node Interface
SNMP Simple Network Management Protocol The UNEM provides an SNAMP interface for
alarms.
SOH Section OverHead Section overhead in SDH signals and containers
(e.g. the SOH in the STM-1 frame).
SRQ Signal ReQuest Indicates the result of the input signal monitoring
for the SYNI<X> units with MSP (SF,SD/high No
request)
SSI Synchronisation Status Indication Indicates weather the data stream can be used as
timing source for synchronisation or not.
SSM Synchronisation Status Message Encoded information in TS 0 of PCM frames,
providing a quantitative value for the usability of
the data stream for synchronisation purposes.
Standardised by G.704.
STM-1 Synchronous Transport Module, level 1
SUBL<X> UBUS unit with 12 POTS interfaces to telephone
sets.
SULIC UBUS unit with 8 U-interfaces (2B1Q coding) to
connect the NTU remote data unit.
SULIS UBUS unit with 8 U-interfaces (2B1Q coding) to
NT1s (ISDN subscriber side).
SUBAT UBUS unit with 4 U-interfaces (4B3T coding) to
NT1s (ISDN subscriber side).
SUBUK UBUS unit with 12 POTS interfaces to telephone
sets. UK version.
SW Software General expression for any kind of software.
SYNAC SBUS unit that terminates 8 VC-12 traffic signals
provided via the SBUS on the PBUS.

SYNAM SBUS unit with 8 interfaces (G.703) for termi-

nated 8 VC-12 traffic signals that are provided via
the SBUS
Sync Synchronisation
SYNIC SBUS unit with one electrical STM-1 interface and
SETS.
SYNIF SBUS unit with one optical STM-1 interface and
SETS.
SYNIO SBUS unit with two optical STM-1 interfaces and
SETS.
TCP Transmission Control Protocol Mainly used in the combination TCP/IP.
TDM Time Division Multiplexer
TD(S) Time Domain Signals
TE Terminal Equipment ISDN equipment connecting to the S interface of
NT1.
TM Terminal Multiplexer
TS Time Slot 64 kbit/s channel in a PCM structure
TTI Trail Termination Identifier Unique identifier assigned to a trail and carried by
the traffic signal.
Trail Trace Identifier
TTP Trail Termination Point
TTRP Tunnel-Tunnel Router Protocol
TU-n Tributary Unit, level n Level of the SDH multiplexing structure.
TUG-n Tributary Unit Group Ditto.
TUN<XY> Family of UBUS transmission units. Member of
this family are units such as TUNOL, TUNOP,
TUNOS and TUNEL.
TUNEL UBUS unit with 2 electrical 8 Mbit/s interfaces
according to ITU-T G.703. Built in 2 Mbit/s DMX
for local cross connection or UBUS access.
TUNOF Special unit with 1 optical 8 Mbit/s IF and 4 elec-
trical 2 Mbit/s IFs according to ITU-T G.703. Built
in 2 Mbit/s DMX for local cross connection. The
LECAF has no bus access and provides front
access for all signals.
TUNOL UBUS unit with 1 optical 8 Mbit/s interface and 4
electrical 2 Mbit/s interfaces according to ITU-T
G.703. Built in 2 Mbit/s DMX for local cross con-
nection or UBUS access.
TUNOP UBUS unit with 2 optical 8 Mbit/s interfaces.
TUNOR Desktop unit with 1 optical 8 Mbit/s IF and 4 E12
IFs. The TUNOR supports the G.703 and V.11
2 Mbit/s standard and ISDN-PRA functionalities.
Mains or local 48 V battery powering.
TX Interface which send the signal (normally equal to
Tx output).
UA Urgent Alarm

UAT UnAvailable Time

UBUS UBUS Internal 2 Mbit/s PCM-highway for traffic and
signalling data implemented with all the UMUX.
Depending on UMUX limitations on use apply.
UCST UMUX Configuration Software Tool PC/computer based EM to manage the NE of
ATR.
ULCAS Universal LineCard for AScostream UMUX modem unit with 5 interfaces for the
transmission of up to 128 kbit/s over copper pairs
to the AM-type Analogue Network Terminating
Units. X.21/X.21bis interface options.
UMTS Universal Mobile Telecommunications UMTS is the new standard to connect all types
System services via mobiles to the network controllers.
UMUX Universal MUltipleXer Family of application optimised Multi-service
Access Systems. The modular structure of the
UMUX equipment supports a large range of
traffic interfaces (voice and data) and transmis-
sion interfaces from 64 kbit/s up to STM-1. This
includes interfaces for the electrical, optical and
DSL transmission.
UNEM UMUX Network Element Manager Workstation based EM for large UMUX networks
with an enhanced graphical user interface. The
UNEM allows multi-sessions and supports multi-
ple EAs and redundant databases.
UNI User Network Interface
UNIDA UNIversal Data Access unit UBUS unit with 4 (or 2) data interfaces (depend-
ing on the type of the interface): X.24/V.11, V.36
RS-449, V.36 RS-499, V.35, V.24/V.28.
Unit Term of a generic element in the structure of
UMUX. A unit contains 1 or more Subunits.
UP User Port Mainly used in relation to V5 applications. Physi-
cal or logical user port implemented in the AN to
provide the relevant interface functions towards
the end-user
UT Unavailable Time Starts with 10 consecutive SESs (included in UT)
and ends with 10 consecutive ESs (not included
in UT).
VC-n Virtual Container, level n Level of the SDH multiplexing structure. Often
the hierarchy type (European =2, American =1) is
amended to n.
VCOX Voltage Controlled Oscillator
VLAN Virtual LAN
V5 Protocol and interface for the switch-
independent deployment of PSTN and ISDN traf-
fic in the access network with provides the corre-
sponding user ports.
V5.1 V5.1 uses one structured 2 Mbit/s signal for 30
PSTN subscribers or a PRA access. V5.1 does not
allow concentration.
V5.2 V5.2 allows concentration of the PSTN and ISDN
subscriber traffic and multiple protection of the
traffic on the concentrated section.

Windows 95 Windows 95/98 and Windows NT are trade-

Windows 98 marks of Microsoft Corporation USA and world-
Windows NT wide.
WINS Windows Internet Name Services

µCLAN Micro Computer LAN Internal communication structure for UMUX unit
microprocessors
10BaseT Ethernet standard for a maximum transmission

rate of 10 Mbit/s.
2B1Q 2 Binary, 1 Quaternary Line code for the ISDN U-interface.
2 Mbit/s 2048 kbit/s
2 MHz 2048 kHz
4B3T 4 Binary, 3 Tertiary Alternate line code for the ISDN U-interface. This
code is manly used in Germany.

Compatibility of UCST/UMUX with Windows®

The UCST R5A and the UMUX equipment have been verified and tested
with the UCST software installed on PC/computers running the operating
system Windows® ME, 98, 2000 and NT4.
Features and descriptions of the UCST/UMUX software and the equip-
ment are stated for the UCST installed on PC/computers running the Eng-
lish version of the operating system Windows® ME or NT4. Accordingly,
the installation and operation of the UCST with your operation system
might show minor differences in functional and operational details as
compared to the documentation.
Please note that:

• ATR lists deviations from standard behaviour due to a par-
ticular operation system as far as known and relevant for
UCST operation. There is however no claim for completeness
nor for accuracy in details.
• Although not listed, there might apply additional restrictions
for features and operation of the UCST/UMUX with your
particular operation system.
• To install the UCST and configure the network parameters
on PC/computer running Windows® 2000 and NT4, you
need a system account with sufficient rights, e.g. the rights
of the “local administrator”.
Please note that:

• In the customer documentation the term UCST is used as a
short term for the 32-bit versions of UCST (releases UCST
R4<X> and higher).
• The dialogues shown are for explanation and demonstration
purposes and might not correspond one to one to the dia-
logues produced with your PC/computer.
• The UCST creates all dialogues based on the English lan-
guage. Dialogues created by Windows will show up in the
language that matches the language of your operating sys-
tem.
• The features of the UCST 5A release are available as stated
in the corresponding release note [043] and might not be
necessarily on a par for Windows ME, 98, 2000 and NT4.

Support
Sales contact address: Ascom Transmission AG
Belpstrasse 37
CH-3000 Bern 14, Switzerland
Tel.: ++41 31 999 1303
Fax: ++41 31 999 1874
Technical support: ATR help desk

Tel.: ++41 31 999 3000
Fax: ++41 31 999 1874
E-Mail: atrhelp@ascom.ch
Time tables Official business office hours ATR: Monday - Friday

08h00 - 12h00 CET
13h00 - 17h00 CET
Help desk:
Open for customers
• without Service Level Agreement: Official business office hours
• with Service Level Agreement: According to the terms of the
service level agreement
Repairs If you have goods for repair, contact your local distributor.
If you need to return equipment for repair directly, please follow the in-
structions below:
• Issue a proforma invoice for customs clearance with the addressee
Dept. GAPX
Belpstrasse 37
Tel.: ++41 31 999 3437
Fax: ++41 31 999 3133
The invoice must clearly state the
− Reason why the goods are returned.
− ATR reference number (ATR order number).
− Additional information as follows:
− Invoice address (as listed above)
− Delivery address (as listed below)
− Sender‘s reference
− Good description
− Quantity
− Price per unit
− Currency
− Marking

− Packing details with dimensions

− Country of origin
− Forwarding Agent and method of transport
− Incoterms
• Transmit a copy of the proforma invoice and all the shipping details via
the
Fax: ++41 31 999 3133
to ATR.
• Ship the goods for repair to the address
attn: Repair Centre/GAPE
Werk Bodenweid
Freiburgstrasse 251
CH-3018 Bern-Bümpliz, Switzerland

ascom
Declarations of Conformity 2
1. CE declaration
2. AD 2000 declaration of conformity

ascom Declarations of Conformity
CE declaration

Ascom Declarations of Conformity
AD 2000 declaration of conformity
Available on request.
Please contact ATR.

ascom

system.

(UCST R5A)

UMUX 1500


Order number:
Belpstrasse 37
CH-3000 Bern 14
Switzerland © June 2001 by Ascom Transmission AG
ascom
Table of contents i
System Summary 1- 1
Overview 1- 1
Introduction to the UMUX 1500 1- 1
Main features 1- 2
Architecture 1- 2
Cross connect 1- 2
Synchronisation 1- 2
Installation 1- 3
Compatibility with other UMUX 1- 3
Summary of features 1- 3
Views of the UMUX 1500 1- 4
Compatibility with the UMUX system family 1- 5
Services 1- 6
Multiservice Access Multiplexing 1- 6
IP Digital Subscriber Line Access Multiplexer 1- 6
Cross Connection 1- 6
V5 Multiplexing 1- 6
V5.2 protocol processing 1- 6
High density of user ports 1- 7
Channel Bank 1- 7
Open Network Provisioning 1- 7
PRA related functionalities 1- 7
STM-1 Access 1- 7
Hubbing 1- 7
Dedicated networks 1- 8
Bridging, routing and frame relay 1- 8
Interfaces and units 1- 9
Synoptic overview of interfaces and units 1- 9
Interfaces 1- 10
Definition and overview 1- 10
Tributary 1- 10
Aggregate 1- 11
Power 1- 11
Auxiliary 1- 11
Units 1- 12
EN/LZVBU 222 215/1 RA Technical System Description UMUX 1500 iii

ascom Table of contents

Traffic units 1- 12
Control units 1- 12
Auxiliary units 1- 13
System and management functions 1- 13
Cross connection 1- 13
System capacity 1- 13
Subrack and units 1- 13
UBUS 1- 14
PBUS 1- 14
SBUS 1- 14
Management 1- 14
Overview 1- 14
Element managers UCST and UNEM 1- 15
Management communication 1- 16
Management access and interfaces 1- 17
Software download 1- 18
Compatibility 1- 19
Internal interfaces 1- 19
System compatibility of functions 1- 19
Traffic functions 1- 19
System functions 1- 19
System compatibility of units 1- 19
UBUS units 1- 20
PBUS units 1- 20
SBUS units 1- 20
Control units 1- 20
Power units 1- 20
Tributary and aggregate interfaces 1- 21
General 1- 21
PSTN 1- 21
2 Mbit/s 1- 21
STM-1 1- 21
Management 1- 22
Management systems 1- 22
Interfaces 1- 22
Communication 1- 22
Compatibility with previous releases 1- 23
NE configuration 1- 23
Functions and units 1- 23
Upgrade procedures 1- 23
System Architecture 2- 1
Block diagram 2- 1
Bus Structures and Cross Connection 2- 2
PBUS 2- 2
UBUS 2- 3
iv Technical System Description UMUX 1500 EN/LZVBU 222 215/1 RA

SBUS 2- 3
System control 2- 4
Communication between controllers 2- 5
Synchronisation and system timing 2- 5
Power supply 2- 7
Traffic units 2- 7
Subrack 2- 7
Implementation of functional blocks 2- 8
Functions and features 2- 8
Architecture and functional blocks 2- 8
Control units 2- 8
Power unit 2- 9
Traffic units 2- 9
PBUS units 2- 9
SBUS units 2- 10
UBUS units 2- 10
Subrack 2- 11
Function 2- 11
Slots in the subrack 2- 11
Limiting factors for the implementation of units 2- 13
Functional Descriptions 3- 1
SDH multiplex functions 3- 1
E1→VC-12 3- 2
VC-12→STM-1 3- 2
Signal termination 3- 3
Terminated signals 3- 3
Monitored signals 3- 3
Transparent signals 3- 3
Signal adaptation 3- 3
n x 64 kbit/s cross connections 3- 4
2 Mbit/s cross connections 3- 4
VC-12 (cross) connections 3- 4
VC-3 (cross) connections 3- 4
V5.x functions 3- 5
V5.x implementation of UMUX 3- 5
V5 traffic handling capacity 3- 7
V5.x implementation in the operator's network 3- 9
Custom parameter sets for V5.x applications 3- 9
Conference function 3- 10
Central diagnostic for traffic signal channels 3- 10
Traffic units 3- 11
PBUS units 3- 11
LAWA4 3- 11
LEMU6 3- 12
EN/LZVBU 222 215/1 RA Technical System Description UMUX 1500 v

LEMQ6 3- 14
LESA8 3- 14
LESAP 3- 16
LOMIF 8 x 2 Mbit/s interface unit 3- 17
LOMI4 3- 19
PCON<X> 3- 20
General specifications 3- 20
PHLC1 subscriber line interface unit 3- 23
UBUS units 3- 26
UBUS units legacy 3- 26
ISBUQ user port units for ISDN-BA 3- 27
ISBUT user port units for ISDN-BA 3- 28
SBUS units 3- 28
SYNAC 3- 28
SYNAM 3- 30
SYNIC 3- 32
SYNIF 3- 33
SYNIO 3- 35
Special traffic units 3- 37
LECAF 3- 37
TUNOF 3- 39
Control units 3- 40
COBU<X> units 3- 40
COBUX/COBUV 3- 40
COBUL 3- 41
COBUQ 3- 42
Overview of specific technical data of control units 3- 43
Power units 3- 45
POSUS power unit 3- 45
Special units 3- 45
ETHUB Ethernet hub unit 3- 45
Synchronisation functions NE 3- 49
Synchronisation and timing sources 3- 49
Synchronisation systems 3- 49
Timing sources 3- 50
SSM and SSI 3- 51
Mapping tables 3- 51
Synchronisation selection modes and recovery 3- 51
Automatic modes 3- 51
Manual override 3- 52
Clock recovery 3- 52
Distribution of timing signals 3- 53
Traffic signals 3- 53
vi Technical System Description UMUX 1500 EN/LZVBU 222 215/1 RA

Synchronisation Outputs 3- 53
SSI and SSM 3- 54
Mapping tables 3- 54
Real Time Clock 3- 55
Redundancy and protection 3- 56
Power management and protection with POSUS 3- 56
Control units 1+1 protection 3- 56
PETS and SETS 3- 57
PETS 3- 57
SETS 3- 57
Cross connect 3- 58
Subnetwork protection 3- 59
Section protection 3- 60
Linear trail protection 3- 61
Multiplex Section protection (STM-1) 3- 61
Protection Modes 3- 62
Compatibility of modes 3- 62
Trail monitoring / protection 3- 63
Performance Monitoring 3- 64
Principles 3- 64
Units and PM 3- 65
Management Functions 4- 1
Configuration of NE and units 4- 1
Configuration tools 4- 1
The managers 4- 1
UCST 4- 1
UNEM 4- 1
Custom parameter sets 4- 2
Inventory management 4- 3
Equipment Identification 4- 3
Inventory data 4- 4
Fault management 4- 5
Alarm Generation 4- 5
Alarm processing 4- 6
Print services 4- 7
Summary and overview 4- 8
Interfaces of the NE 4- 11
F-interface 4- 11
Q1-Interface 4- 12
QX-Interface 4- 13
Communication via ECC 4- 14
Principles of management communication 4- 17
Encapsulation and tunnelling of TCP/IP in OSI DCN 4- 17
Routing 4- 18
EN/LZVBU 222 215/1 RA Technical System Description UMUX 1500 vii

IP address administration 4- 21
Head end access 4- 22
Remote access 4- 23
Communication via EOC 4- 23
Communication via Q1-master interface 4- 25
Construction and EMC/ESD 5- 1

Construction 5- 1
Overview 5- 1
Subrack and cable tray 5- 3
Design and dimensions 5- 3
Partitioning and backplane arrangement 5- 3
Heat deflection shield (optional) 5- 4
Fan unit (optional) 5- 5
Subrack with front cover 5- 6
ETSI adapters 5- 6
Plug-In Units 5- 8
Cabling and connections 5- 9
Signal cables 5- 9
Cable tray and grounding bar 5- 9
Connection panel 5- 10
ESD / EMC and grounding 5- 10
Operation and Maintenance 6- 1

Management interfaces 6- 1
Alarm interfaces 6- 2
Optical fault and alarm indication 6- 2
Electrical alarm indication 6- 3
Alarm description 6- 3
Notifications 6- 3
NE fault list 6- 3
Logbook 6- 3
Performance control and monitoring 6- 4
Test functions and diagnostics 6- 4
System level 6- 4
Functional level 6- 5
Unit and subunit (traffic signal) level 6- 5
Central diagnostic for traffic signal channels 6- 6
Test signal 6- 7
Analyses for 8-bit patterns 6- 7
Analyses for pseudo random bit pattern sequences 6- 8
Upgrading 6- 8
Upgrading hardware 6- 8
Upgrading with hardware protection 6- 8
Upgrading unit SW 6- 8
viii Technical System Description UMUX 1500 EN/LZVBU 222 215/1 RA

Units with SW download 6- 8

Units without SW download 6- 9
Manipulation of the equipment 6- 10
Unit handling 6- 10
Equipment handling 6- 10
System labelling 6- 10
Identification label 6- 10
Identification label “Unit Hardware” 6- 11
Identification label “Function” level 6- 12
EMC and safety label ("CE" label) 6- 14
Location of "CE" label 6- 14
Limitation of liability 6- 14
Warning labels 6- 15
"Hazardous voltages" 6- 15
"Laser radiation" 6- 16
Electrostatic sensitive devices 6- 16
System Specification 7- 1
Functional specification 7- 1
General 7- 1
Signals 7- 1
Protection 7- 2
Monitoring traffic signals 7- 3
V5 functions 7- 3
Diagnostic functions 7- 3
Conference functions 7- 4
General 7- 4
PETS 7- 4
SETS 7- 5
Maintenance and Diagnostics 7- 6
Fault management 7- 7
SSM and QL processing 7- 7
Management functions 7- 8
System control 7- 8
Software system 7- 9
Test and diagnostic functions 7- 9
Compatibility with other UMUX equipment 7- 10
Technical specification 7- 11
Architecture 7- 11
System 7- 11
PBUS 7- 11
UBUS 7- 12
SBUS 7- 12
EN/LZVBU 222 215/1 RA Technical System Description UMUX 1500 ix

Element Manager 7- 12
Management communication structures 7- 12
Routing 7- 13
Cross connections and delays 7- 14
PBUS cross connect 7- 14
Traffic signal delays PBUS and UBUS 7- 14
Traffic signal delays SBUS and PBUS 7- 15
Signal Interfaces 7- 15
Traffic interfaces 7- 15
Units implemented 7- 15
Synchronisation interfaces inputs 7- 15
Synchronisation interfaces outputs 7- 15
Access to SOH of STM-1 7- 17
Power interfaces 7- 18
DC interface 7- 18
Power consumption 7- 18
Internal power supply 7- 18
Power dissipation 7- 18
Subrack 7- 18
Construction 7- 18
Capacity and slots 7- 19
FANUV fan unit 7- 19
Construction 7- 19
Specification 7- 19
Alarm interface 7- 19
Power supply 7- 19
EMC 7- 20
Product family standard 7- 20
Emission 7- 20
Immunity 7- 20
ESD 7- 20
Safety 7- 20
Ambient conditions 7- 20
Storage 7- 20
Transport 7- 21
Operation 7- 21
Mechanical parameters 7- 21
Dimensions 7- 21
Weight 7- 21
Installation 7- 22
Subrack, cable tray 7- 22
Connection of signals 7- 22
Connection of power supply 7- 22
Dependability 7- 22
Availability 7- 22
MTTF 7- 23
x Technical System Description UMUX 1500 EN/LZVBU 222 215/1 RA

Implementation and Application Notes 8- 1

Configuration of the subrack 8- 1
Summary of limiting factors for unit implementation 8- 1
General all units 8- 1
Synoptic overview 8- 2
Control units and power supply 8- 3
Control Units 8- 3
Power supply 8- 3
UBUS 8- 3
UBUS structure 8- 3
UBUS access 8- 4
UBUS units and UMUX 1500 8- 5
Selection of UBUS highways and connection points 8- 6
Summary of UBUS access of units 8- 7
PBUS 8- 11
PBUS structure 8- 11
PBUS access 8- 11
SBUS 8- 13
SBUS structure 8- 13
SBUS access 8- 13
Mechanical and thermal 8- 15
Unit width 8- 15
Restrictions of unit implementation 8- 16
Heat dissipation 8- 16
Summary of rules for unit implementation 8- 16
Templates for unit implementation 8- 18
Standard configurations 8- 18
Cross connect 8- 19
DXC 128 x 2 Mbit/s 8- 19
V5.1 Access Systems 8- 20
PSTN x 240 8- 20
PSTN x 180 / ISDN-BA x 24 8- 21
PSTN x 120 / ISDN-BA x 56 8- 22
PSTN x 60 / ISDN-BA x 80 8- 23
ISDN-BA x 112 8- 24
V5.2 Access System 8- 25
PSTN x 240 8- 25
PSTN x 180 / ISDN-BA x 24 8- 26
PSTN x 120 / ISDN-BA x 56 8- 27
PSTN x 60 / ISDN-BA x 80 8- 28
ISDN-BA x 112 8- 29
STM-1 aggregate and applications 8- 30
TM/ADM for k x 8 x VC-12 with MSP 8- 30
TM/ADM for k x 8 x VC-12 with SETS protection 8- 31
TM/ADM for 48 x 2 Mbit/s via PBUS 8- 32
TM/ADM for 48 x 2 Mbit/s direct front access 8- 33
TM/ADM + V5.1 hub 8- 34
TM/ADM + V5.2: 180 x PSTN / 16 x ISDN BA 8- 35
EN/LZVBU 222 215/1 RA Technical System Description UMUX 1500 xi

TM/ADM + V5.2 8- 36
Generic template for unit implementation 8- 37
Power consumption and heat dissipation 8- 38
Calculating power dissipation 8- 39
IP addresses 8- 40
Calculating the number of UMUX spare units 8- 41
System and Ordering Information 9- 1

Functions and unit software ESW 9- 1
Element manager 9- 1
Control and power units 9- 2
PBUS units 9- 4
SBUS units 9- 7
UBUS units 9- 9
Special units 9- 14
Ordering information 9- 15
Cable cross-references 9- 15
Selected accessories 9- 17
Time tables 9- 18
xii Technical System Description UMUX 1500 EN/LZVBU 222 215/1 RA

ascom
System Summary 1
Overview
Introduction to the The UMUX1500 is a member of ATR's Multiservice Access System family.
UMUX 1500 The UMUX 1500 is a flexible access system with an enhanced system
design and integrated transmission capabilities.
The UMUX 1500 is a network element of medium to large capacity in the
access network and particularly suited as
• Multiservice Access System similar to other UMUXs but with
considerably higher traffic handling capacity, with new functionalities
and services such as the handling of SDH signals and V5.x service
provisioning.
• Interface for the UMUX Access Network to a Backbone
Network. This implies the ability to terminate high capacity aggregate
signals (SDH STM-1) down to 64 kbit/s circuits and to provide physical
user service interfaces (POTS, ISDN, data leased lines). As a multi-
service Access System, the UMUX 1500 bridges the gap between the
individual subscriber service and the backbone network.
• Transmission Device which uses its STM-1 interfaces for the
integration into SDH based transport networks and which provides at
the same time cross connect functionality for the PDH tributary signals.
• IP Digital Subscriber Line Access System for Internet Service
Providers.
The UMUX 1500 has a 19-inch subrack with 21 slots for traffic, control
and power units.
The UMUX 1500 and the UMUX 1200 use the same types of control units
and provide a large set of integrated transmission interfaces (optical fibres
and copper based). These interfaces allow you to connect the network
element directly to your transport backbone or to build a transport
network (limited transmission capacity) with the UMUX 1500 and
UMUX 1200.
The STM-1 interface (electrical and optical) is the interface with the
highest traffic capacity that is available with the UMUX 1500 and
UMUX 1200. It is possible to configure the UMUX 1500 as a terminal
Access System or as an add and drop multiplexer for STM-1 SDH signals.
The UMUX 1500 features the F- and the Q1-interface for local and remote
management access, which are both functionally compatible with the
corresponding interfaces of the UMUX 1100(E) and UMUX 1300.
EN/LZTBU 220 115/1 RA Technical System Description UMUX 1500 1-1

Ascom System Summary
Additionally, the UMUX 1500 provides the QX-interface. This is an

Ethernet interface (10BaseT) which allows management accesses via LANs.
The key to present and future network operation is an integrated
Network Management. The management systems UNEM and UCST
manage the UMUX 1500 as well as the other members of the UMUX (e.g.
UMUX 1200, UMUX 1300 and UMUX 1100(E)) and the DSL product
family. With the UCST and UNEM, the management platform provides
both, management for networks (UNEM) and NEs (UCST).
For the remote management of NEs with the UCST and UNEM, the
UMUX 1500 provides the ECC (Embedded Communication Channel). The
ECC is a high performance in-band data channel, which allows the
implementation of versatile in-band networks for the management
communication of the UMUX 1500 and UMUX 1200.
If required, it is possible to connect the UMUX 1500 via the SIFOX to the
EOC (Embedded Operation Channel), the management communication
network of the UMUX 1300 and UMUX 1100(E). The implementation of
the SDH functionality with the UMUX 1500 and UMUX 1200 allows the
tunnelling of the PDH ECC via SDH transmission sections.
Main features
Architecture The UMUX 1500 implementation is based on a new construction of a 19-
inch subrack and the control units COBU<X> (COBUX, COBUV, COBUQ
and COBUL). You can implement redundancy for both the control unit
and the power supply units (POSUS). A set of optimised control units
(COBUX, COBUV, COBUQ and COBUL) offers an economic choice of the
control function for a specific application without restrictions on future
system expansions and upgrades.
A set of traffic units with a new design satisfies the enhanced
requirements for capacity and functions for the multi-service applications
with the UMUX 1500. These units provide access to the high capacity
PBUS. Units with SDH functionality provide access to the SBUS and (if
applicable) also to the PBUS. All new units feature software download
(except for the POSUS).
Cross connect The UMUX 1500 enhances the UMUX Access System portfolio with 1/0,
1/1 cross-connect and SDH transmission capacity in one 19-inch subrack.
The UMUX 1500 is capable of multiplexing and cross connecting both n x
64 kbit/s and 2 Mbit/s signals. The cross connect is implemented on the
PBUS, which is the typical BUS structure of the UMUX. The cross connect
capacity is in total 128 x 2 Mbit/s.
The plesiochronous 2 Mbit/s signals are either switched transparently or
demultiplexed and switched as n x 64 kbit/s signals. Structured
synchronous signals are terminated and synchronised by the local system
clock. The cross connect handles unstructured 2 Mbit/s signals for
transparent cross connecting.
The UMUX 1500 also provides UBUS access with a capacity of 2 times 4 x
2 Mbit/s for traffic signals with and without signalling.
Synchronisation The UMUX 1500 provides PETS and SETS (with STM-1 interfaces only) for
system synchronisation.
1-2 Technical System Description UMUX 1500 EN/LZTBU 220 115/1 RA

Installation The UMUX 1500 allows installation in 19-inch or ETSI racks.

Optional heat deflection shield for controlled air convection and fan unit
(19-inch) for forced air cooling.
Compatibility with other The UMUX 1500 offers backward compatibility with the proven UMUX
UMUX system philosophy and equipment. The COBU<X> control units have been
specially designed for the new UMUX Multiservice Access Systems. It is
not possible to use these units with the UMUX 1100/1300.
The open system architecture allows you to use all the UMUX traffic
interfaces (data, voice, V5.x, xDSL and optical fibres) with the UMUX 1500
and UMUX 1200 network elements.
Summary of features The UMUX 1500 is the most powerful of the UMUX Multiservice Access
Systems. You can operate the UMUX 1500 as a Network Element in any
type of network (i.e. linear, star, ring and meshed). The network element's
main features are:
• Modular design for the implementation of flexible NEs
• Compact 19-inch subrack and adapters for ETSI installation practice
• DC powering with modular implementation of power converter units
• Use of highly integrated circuits for a high density of traffic interfaces
• Software download for unit software ESW (Embedded Software)
• Inventory management
• Cross connect of 64 kbit/s and n x 64 kbit/s signals
• Cross connect of 2 Mbit/s signals
• Highly dependable and single point failure tolerant cross connect
• Set of optimised control units
• Local voice & data interfaces
• Voice and data interfaces for remote access
• V5.2 and V5.1 functionality
• Custom parameter sets for V5.x and PSTN applications
• Transmission interfaces and integrated LTE
• DSL transmission interfaces
• High speed IP Internet/Intranet access via xDSL and the UMUX network
• Termination and add/drop functions for STM-1 traffic signals
• Optical STM-1 interfaces S1.1, L1.1 and L1.2
• Electrical STM-1 interface
• SETS and PETS
• ECC (Embedded Communication Channel) for enhanced management
communication
• Full redundancy for system control
• Full redundancy and load sharing for power supply
• Diagnostic functions (cross connect, synchronisation, data)
• Configuration of conference circuits for traffic signals

Views of the UMUX 1500 The UMUX 1500 is based on a 19-inch subrack with front access for all
signal and power cables. A removable cover closes the front of the
subrack. A cable tray below the subrack allows for an easy installation of
the signal cables.
The construction of the subrack and the cable connections provide
Faraday cage-like EMC characteristics, provided the front cover is installed
and the signal cables have been installed and shielded as instructed.
Figure 1-1: UMUX 1500 with front cover
Optional ETSI adapters allow you to install the UMUX 1500 19-inch
subrack in an ETSI rack.
Figure 1-2: Sample of the UMUX 1500 without front cover
The subrack accepts all the PBUS and SBUS traffic units as well as old and
new UBUS traffic units.

Compatibility with the The UMUX 1500 Access System is compatible with the other members of
UMUX system family the UMUX Access Systems, that is, to the UMUX 1100(E) and
UMUX 1300. Compatibility means that the UMUX 1500 and its interfaces
are compatible with most of the units, with the transmission and traffic
interfaces and with all the management communication structures.
Like the other members of the UMUX family, the UCST EM and the UNEM
NEM manage the UMUX 1500. It is possible to add the UMUX 1500 to
existing UMUX networks and integrate the new Access System into their
management communication.
The UMUX 1500 provides with the ECC (Embedded Communication
Channel) a performance–enhanced, management communication system
but is still fully compatible with the existing communication principles and
structures. The ECC is however not available for the UMUX 1100(E) and
the UMUX 1300.
Figure 1-3: UMUX 1500 and UMUX product family
Transport
Network
PSTN
SDH PDH
2 Mbit/s
- electrical
STM-1
- optical
PDN
Network & 8 Mbit/s
- electrical
Element Manager - optical
(HP OpenView)
UNEM
UMUX 1500 UMUX 1200
xDSL 10BaseT 8 Mbit/s or

2 Mbit/s
UCST
Element
Manager
(PC base)d
MUSIC 100 NTU
Desktop
Remote LAN POTS Data Access

LAN Access
10BaseT ISDN n x 64 kbit/s
10BaseT 2 Mbit/s
PRA
The figure above shows the hierarchical relationship between the

members of the UMUX system family. Ideally, you implement the
Transport Network so that it is based on the UMUX Access Systems
(management of NEs).
For an overview of the interfaces in the UMUX 1500, refer to the figures
in the paragraph "Synoptic overview of interfaces and units".

Services
The flexible Multiservice Access System UMUX 1500 features a powerful
cross connect for the signal levels 1/1 and 1/0. It is easy to tailor the
UMUX 1500 for the following services and functions:
Multiservice Access The UMUX 1500 provides the multiplexing of tributary signals into
Multiplexing aggregate signals (e.g. STM-1 signals). The UMUX 1500 benefits from the
various transmission and traffic interfaces (voice and data) available for the
UMUX Access System family. The UMUX 1500 also supports 2 Mbit/s
signals as tributaries.
The units designed for the UMUX 1500 and 1200 provide a high density
of traffic interfaces.
IP Digital Subscriber Line The UMUX 1500 is ideally suited to provide the Internet Service access for
Access Multiplexer IP users at remote locations.
Cross Connection It is possible to implement cross connects with capacities of up to 128 x

2 Mbit/s or 4096 x 64 kbit/s. The 21 slots of the UMUX 1500 allow you to
implement the required traffic units with the aggregate and tributary
interfaces.
If required, the UMUX 1500 provides the possibility to protect the cross
connections.
V5 Multiplexing
V5.2 protocol processing The UMUX 1500 provides V5.2 protocol processing for up to 480 PSTN
user ports or 224 ISDN BA user ports.
The UMUX 1500 provides two units for the protocol processing of one
V5.2 interface. The two units feature a capacity equivalent to 240 and
480 PSTN user ports respectively. The units can handle configurations with
mixed user ports (PSTN and ISDN BA) up to the equivalent of 480 PSTN
user ports. It is possible to implement units for the protocol processing of
multiple V5.2 interfaces in one UMUX 1500.
There are pre-defined custom parameter sets available that allow you a
fast and reliable commissioning of the UMUX 1500 and its V5.2 function
in ANs with a high volume of UMUX 1500 Access Systems.
The UMUX 1500 subrack allows the implementation of V5.2 multiplexers
with capacities of up to 240 PSTN or 112 ISDN-BA user ports in one
subrack. The simultaneous configuration of PSTN and ISDN-BA user ports
is possible; the total number of interfaces depends on the remaining
subrack capacity.
It is possible to use the remaining subrack capacity for aggregate
interfaces and voice and/or data services.

V5.1 protocol processing The UMUX 1500 provides two units for the protocol processing of V5.1
PSTN and ISDN user ports.
The two units feature a capacity of 4 and 10 V5.1 interfaces respectively.
The units can handle configurations with mixed user ports (PSTN and ISDN
BA). It is possible to implement units for the protocol processing of
multiple V5.1 interfaces in one UMUX 1500.
There are pre-defined custom parameter sets available to allow you a fast
and reliable commissioning of the UMUX 1500 and its V5.1 function in
ANs with a high volume of UMUX 1500 Access Systems.
The UMUX 1500 subrack allows the implementation of V5.1 multiplexers
with up to 240 PSTN interfaces or 112 ISDN-BA user ports in the same
subrack. The simultaneous configuration of PSTN and ISDN-BA user ports
is possible. The number of interfaces depends on the remaining subrack
capacity.
interfaces and voice and/or data services.
High density of user ports The new units designed for the UMUX 1500 provide a high density of
traffic interfaces for V5.x and channel bank applications.
Channel Bank It is possible to implement channel banks with up to 240 PSTN interfaces.
interfaces and other voice and/or data services.
Open Network Provisioning The cross connect of the UMUX 1500 allows the transparent switching of
structured and unstructured 2 Mbit/s signals, thus providing fully open
transport and access networks for payload traffic.
PRA related functionalities Due to the transparency of the UMUX 1500 for 2 Mbit/s traffic signals,
the UMUX 1500 is suited to providing the termination of ISDN primary
rate access. The UMUX 1500 can provide the NT1-T and LT functional
groups of the PRA with the NT1-T / NT1-U / LT-U / LT-V3 functional
blocks.
STM-1 Access The UMUX 1500 allows the implementation of backbone networks based
on STM-1 and provides all the access multiplexing for STM-1 SDH network
access.
The UMUX 1500 allows the implementation of:
• The optical STM-1 interface implemented as S1.1, L1.1 and L1.2.
• The electrical STM-1 interface (according to ITU-T G.703)
Hubbing The UMUX 1500 can serve as a hub for other UMUX Access Systems.

Dedicated networks The UMUX 1500 can operate as a multi-service Access System, combining
multiple functions per NE (transport, access, cross connection), in
dedicated networks such as telecommunication networks of railway and
power companies.
Bridging, routing and frame The UMUX 1500 together with the corresponding unit(s) allow you to
relay implement
• Public bridging and private bridging for remote LAN access
via local MSDSL transmission and
− local Ethernet interface.
− WAN access via DCN.
• IP routing with remote LAN access
• Frame Relay switching with remote LAN access
via local MSDSL transmission and WAN access via DCN.
• FRAD function with local routing with remote LAN access
All these functions are also available without local MSDSL transmission
interfaces.

Interfaces and units

Synoptic overview of While the UMUX 1500 features higher cross connection and transmission
interfaces and units capacity than the other UMUX Access Systems, it maintains backward
compatibility with existing units and interfaces. The figures below illustrate
the interfaces and units provided with the UMUX 1500 (power
interfaces/units are not shown).
Figure 1-4: Overview of interfaces and units of the UMUX 1500

Part 1
current sense
Current loop input (16) 2048kHz
voltage sense ALCAR uC-LAN Ext. clock input ESI (2)
Voltage input (8) COBUX, COBUV
Alarm relay output (4) open/close Clock output ESO (3 + 1)
Multipurpose COBUQ, COBUL
(Serial interfaces (4) (RS 232 C) I/O unit high/low
no highway access) UBUS access Ext. alarm inputs (4)
open/close
PETS (Synchronisation) Alarm relay output (2)
Synchronisation IF
MIB Q1-master interface
Alarm IF 115k2 bit/s
F-interface
Management communicaton Q1-(slave) interface
10Base T
EXLA<X> Qx-interface
2-Wr. a,b
64k
Exchange line IF UCST
a,b-wire: 12 IFs (64k) UNEM
TS16
2-Wr. a,b NEMCA/NEMGE LOMIF
64k
2 Mbit/s G.703/G.704
E&M Voice frequency IF 2 Mbit/s electrical IF
(64k) data: 8 IFs
(E'&M') 4/6-wire: 8 IFs
TS16
SUBLx/SUBUK LOMI4
2-Wr. a,b
64k
2 Mbit/s G.703/G.704
Subscriber line IF 2 Mbit/s electrical IF
a,b-wire: 12 IFs (64k) data: 4 IFs
TS16
LAWA4 10 BaseT
LAN / Ethernet device
Ethernet: 1 IF
10BaseT LAN
MUSIC 100 (deskt.)
10 BaseT Ethernet device
LEMU6 MSDSL or DSL (Hub with 4 ports)
MSDSL transm. CAP or <X>DSL: 1 IF RS 232 C
2B1Q data: 1 IF Local management
Ethernet: 1 IF 2-Wr. a,b
MSDSL: 6 IFs CAP
LECAR (desktop) 2 Mbit/s G.703/G.704
GECOD LEMQ6 10 BaseT CAP or DSL transm. or
64k LAN / Ethernet device
2B1Q DSL: 2 IFs
64k MSDSL trans. nx64 kbit/s G.703/G.704
64 kbit data IF Ethernet: 1 IF 2-Wr. a,b data: 1 IF X.21/V.11 or V.35 or V.36
G.703 (64k)
data: 8 IFs MSDSL: 6 IFs 2B1Q
DTE TS16 LESAR (desktop) 2 Mbit/s G.703/G.704, VC-12
CAP or
SIFOX LESA8 DSL transm. or
2B1Q or
64k DSL: 2 IFs nx64 kbit/s G.703/G.704
64k DSL transm. PAM16
Data IF / EOC DSL 1 pair: 8 IFs data: 1 IF X.21/V.11 or V.35 or V.36
X.24/V.11 2-Wr. a,b
data: 4 IFs (64k) DSL 2 pairs: 4 IFs
DTE TS16 CAP, 2B1Q, PAM16
UBUS
PBUS
Subrates, UNIDA LESAP

nx64k n x 64k DSL transm.
X.24/V.11 Data IF DSL 1/2 pairs: 4 IFs 2-Wr. a,b
V.35, V.36 data: 2 or 4 IFs
(64k) Rem. power: 1 IF CAP, 2B1Q, PAM16
DTE V.24/V.28 TS16
128k/64k
X.21/V.11 2-Wr. a,b SULIC PCONV
V.35 64k V5.x protocol
NTU 2B1Q transm. 2 Mbit/s G.703/G.704
V.24/V.28 144k Data IF for NTU
DTE 0,6-38,4k 2B1Q 64k
2-wire: 8 IFs 2 Mbit/s: 2 IFs
PCON2
V5.x protocol
PHLC1
2-Wr. a,b
Subscriber line IF
a,b-wire: 60 IFs
EXLIC 64k PHLC2

2-Wr. a,b ISDN-U (2B1Q) 64k 2-Wr. a,b
Exchange line IF (16K) Subscriber line IF
144k
2B1Q a,b-wire: 8 IFs 64k a,b-wire: 30 IFs
SULIS 64k PHLC3

S 2-Wr. a,b ISDN-U (2B1Q) 64k 2-Wr. a,b
NT-1 Subscriber line IF (16K) Subscriber line IF
144k
ISDN 2B1Q a,b-wire: 8 IFs 64k a,b-wire: 10 IFs
ISBUQ (V5) 64k

S 2-Wr. a,b
NT-1 ISDN-U (2B1Q) 64k
144k Subscriber line IF (16K)
ISDN 2B1Q a,b-wire: 8 IFs 64k
2-Wr. a,b
ISBUT (V5) 64k SYNAC SYNAM
S
NT-1 ISDN-U (4B3T) 64k SBUS access SBUS access
144k (16K) 2 Mbit/s G.703
Subscriber line IF VC-12 TU-12 / G.703
ISDN 4B3T a,b-wire: 8 IFs channels: 8 data: 8 IFs
64k
EXBAT 64k SYNVA

2-Wr. a,b ISDN-U (4B3T) 64k SBUS access
144k Exchange line IF (16K) TU-12
SBUS (sectors A + B)
4B3T a,b-wire: 8 IFs 64k channels: 32
SUBAT 64k SYNOT 155 Mbit/s

S 2-Wr. a,b ISDN-U (4B3T) 64k STM-1 optical IF S1.1
NT-1 Subscriber line IF (16K) VC-4 L1.1, L1.2
144k
a,b-wire: 4 IFs optical: 1 IF G. 957
ISDN 4B3T 64k
SYNIO 155 Mbit/s

STM-1 optical IF S1.1
VC-4, SETS L1.1, L1.2
optical: 2 IFs G. 957
SYNIF 155 Mbit/s

VC-4, SETS L1.1, L1.2
optical: 1 IF G.957
SYNIC
STM-1 electrical IF 155 Mbit/s
VC-4, SETS G. 703, koaxial
electrical: 1 IF


Part 2
8 Mbit/s optical
TUNOP 31 x 64k MEGIF 2 Mbit/s G.703/G.704
31 x 64k 2 Mbit/s electrical
8 Mbit/s optcal IF 31 x 64k
8 Mbit/s optical 31 x 64k G.703/G.704
optical: 2 IFs 31 x 64k 2 IFs 2 Mbit/s G.703/G.704
31 x 64k
8 Mbit/s optical 31 x 64k 31 x 64k TUNEL
TUNOS 8 Mbit/s G.703
V.11 OHC 8 Mbit/s optcal IF 31 x 64k 31 x 64k 2 Mbit/s electrical
8 Mbit/s optical optical: 2 IFs 31 x 64k 31 x 64k G.703
electrical: 2 IFs 31 x 64k 31 x 64k 2 IFs 8 Mbit/s G.703
V.11 OHC
UBUS
2 Mbit/s G.703/G.704 2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704 or
LECA2 (LE2Q2)
transmission IF nx64 kbit/s
CAP
G.703/G.704
(2B1Q) 2 DSL IFs
X.21/V.11 or V.35 or v.36
1 data IF or
2-Wr. a,b
2 Mbit/s G.703/G.704 TUNOL 31 x 64k LECA2 UMUX highway access
31 x 64k DSL transm. CAP nx64 kbit/s
2 Mbit/s G.703/G.704 opt. / electrical IFs n x 64k
2 Mbit/s G.703/G.704 optical: 1 IF 31 x 64k 2 DSL IFs
(1 data IF) 2-Wr. a,b
2 Mbit/s G.703/G.704 electrical: 4 IFs 31 x 64k
CAP
V.11 OHC
2-Wr. a,b
LE2Q2 10BaseT LAN
8 Mbit/s optical 2B1Q MUSIC 100 (deskt.)
DSL transm. Ethernet device
n x 64k DSL (Hub with 4 ports)
2 Mbit/s G.703/G.704 TUNOL 2 DSL IFs DSL: 1 IF
2-Wr. a,b CAP or RS 232 C
2 Mbit/s G.703/G.704 opt. / electrical IFs (1 data IF) 2B1Q data: 1 IF Local management
2 Mbit/s G.703/G.704 2B1Q
optical: 1 IF
2 Mbit/s G.703/G.704 electrical: 4 IFs LECAR (desktop)
2 Mbit/s G.703/G.704
CAP DSL transm. or
(1/2 pairs) DSL: 2 IFs nx64 kbit/s G.703/G.704
V.11 OHC
data: 1 IF X.21/V.11 or V.35 or V.36
2 Mbit/s G.703/G.704 LE2QR (desktop)

TUNOR (desktop) 2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704 DSL transm.
opt. / electrical IFs 2B1Q or
2 Mbit/s G.703/G.704 optical: 1 IF DSL: 2 IFs nx64 kbit/s G.703/G.704
2 Mbit/s G.703/G.704 electrical: 4 IFs data: 1 IF X.21/V.11 or V.35 or V.36
PRA
LESAR (desktop) 2 Mbit/s G.703/G.704
CAP
DSL transm. or
DSL: 2 IFs nx64 kbit/s G.703/G.704
data: 1 IF X.21/V.11 or V.35 or V.36
Please note that:

• Components with dashed outlines designate units
(interfaces) that are FUTURE OPTIONS.
• The diagram does not show power interfaces/units and units
with auxiliary functions (e.g. ringing generators, ETHUB unit
etc.).
• The chapter 9 “System and Ordering Information” provides
a detailed list of units and functions released for the
UMUX 1500.
Interfaces
Definition and overview The UMUX 1500 provides the following types of interfaces for signals,
power supply and auxiliary functions:
• Tributary interfaces
• Aggregate interfaces
• Power interface
• Auxiliary interfaces
− Alarm interfaces
− Interfaces for synchronisation
− Interfaces for management communication
Tributary and aggregate interfaces are physically implemented on

dedicated units. The auxiliary interfaces (management communication,
alarming and synchronisation) are physically integrated with the control
units.
The power interface connects the power converter units of the
UMUX 1500 to the external dc power supply.
Tributary Most of the various tributary interfaces provided with the

UMUX 1100/1300 are also available with the UMUX 1500 Access System,

provided the corresponding units have been released for the UMUX 1500.
The unit descriptions and user guides specify the technical data and
describe the corresponding applications. Detailed information on released
functions and units are provided in the chapter 9 "System and Ordering
Information" and in the corresponding release note (e.g. [043] for the
UCST R5A).
Aggregate It is possible to use the various aggregate interfaces released with the
UMUX 1100/1300 in the UMUX 1500 Access System, provided the units
have been released for the UMUX 1500 system.
The unit descriptions and user guides specify the technical data and
describe the corresponding applications. Detailed information on released
UCST R5A).
Some of these interfaces provide direct LTE functionality.
Power The UMUX 1500 has one power interface for a -48/60 VDC nominal power
supply (not shown in the figures above).
Auxiliary The UMUX 1500 features 4 physical and 2 internal interfaces for
management communication:
• F-interface (physical)
• Q1-(slave) interface (physical)
• Q1-master interface (physical)
• QX-interface (physical)
• PDH ECC (internal)
• SDH ECC (internal)
The F- and the Q1-interfaces are management interfaces based on serial
communication familiar from the UMUX 1100/1300. The QX-interface is a
high speed Ethernet interface that allows the implementation of local
LANs for management communication between the NEs and the EM.
The internal ECC interfaces allow the implementation of inband
management communication via the UMUX 1500 network. All interfaces
for management communication are implemented physically and logically
on the control unit (availability depends on the selected control unit).
For alarm and synchronisation signals, the UMUX 1500 provides dedicated
interfaces set-up as input or output:
• Alarm signals
− System alarms (output): Relay contacts
− External alarms (inputs): Monitoring of signal levels
• Synchronisation
− Inputs ESI (2) : 2048 kHz
− Outputs ESO (3): 2048 kHz

Units
Definition and overview The modular design of UMUX Access Systems is based on the flexible
combination of specialised units which perform either a specific (system)
function or provide (traffic) interfaces. Depending on requirement, we use
different schemes to group units in the UMUX 1500 environment. Units
are grouped either according to system architecture or according to unit
function:
• The architectural grouping classifies the units as follows
− UBUS units
− PBUS units
− SBUS units
− Control units
− Power units
− Special units
The architectural grouping of units is based on the implementation of

the system and is explained in the chapter 2 "System architecture".
• The functional grouping of units classifies the units as follows
− Traffic units
− UBUS units
− PBUS units
− SBUS units
− Special (traffic) units
− Control units
− Auxiliary units
− Power units
− Special units
The functional grouping is based on interfaces and functions.
Traffic units The traffic units provide interfaces as follows

• Internal interface(s) for the processing of traffic signals
Most of the various traffic units available with the UMUX 1100/1300 can
also be used with the UMUX 1500 Access System, provided the units have
been released with the UMUX 1500 system. The corresponding unit
descriptions and user guides specify the technical data and applications.
Detailed information on released functions and units are provided in the
chapter 9 "System and Ordering Information" and in the corresponding
release note (e.g. [043] for the UCST R5A).
For units already released with the UMUX 1100/1300, rules for system
implementation and features mostly remain the same with the UMUX
1500. Due to different layouts of the UBUS and different numbers of slots
in the multiplexer subracks, the UBUS access of corresponding slots might
be different between the systems.
Control units Control units provide interfaces as follows

• Interface(s) for internal access to the UBUS
(depends on selected control unit)
• Interfaces for synchronisation signals

• Alarm interfaces
• Management interfaces
• Diagnostic interfaces
It is not possible to use the CENCA control units released for the
UMUX 1100/1300 with the UMUX 1500. The UMUX 1500 has its own set
of control units (COBU<X>).
Auxiliary units Auxiliary units provide internal system interfaces and special interfaces for
external signals. An auxiliary unit provides a common service for the NE or
special applications for traffic signals:
• Interfaces for (internal) power supply
• Interfaces for (internal) ringing signals
• Interfaces for dedicated diagnostic functions
• Fan units
• Hub unit for management communication
• etc.
The few auxiliary units available are mostly designed for a particular type
of UMUX Access System or subscriber service. Therefore, the units are not
generally released for the UMUX 1500.
System and management functions

Cross connection The cross connect of the UMUX 1500 allows for switching on signal levels
1/1 and 1/0. The switch mechanism is implemented across the PBUS.
The 1/1 switch architecture is non-blocking with a total capacity of 128 x
2 Mbit/s equivalents with and without CAS. The capacity available will be
reduced compared to the maximum capacity depending on the control
unit implemented. It is possible to cross connect structured as well as
unstructured 2 Mbit/s signals "bit and clock transparent". The transparent
cross connection of 2 Mbit/s signals is only available with interfaces
terminated directly on the PBUS (e.g. LOMIF/LOMI4) but not with
interfaces terminated on the UBUS. The cross connections can be
configured bi-directional, unidirectional or for broadcasting of signals.
The 1/0 cross connect provides the connection of 64 kbit/s and n x
64 kbit/s signals, with and without CAS, such as that provided by the
various traffic units with voice and data interfaces. The cross connect
facility allows you to drop and insert n x 64 kbit/s signals.
The architecture of the PBUS cross connect is resistant to single points of
failures.
System capacity
Subrack and units The UMUX 1500 subrack has 21 slots for traffic units, control and power
units. In a subrack with redundant control units and protection of the
power converter units, you will still dispose of 16 to 17 standard width
slots for the implementation of traffic units.

Units with PBUS or SBUS access have a high density of traffic interfaces.
This allows the implementation of far more interfaces per unit as
compared to UBUS units with similar types of interfaces.
The UMUX 1500 allows any mix of traffic interfaces and units, provided
the required bus capacity and/or the slots in the subrack are available.
UBUS The UBUS of the UMUX 1500 allows the implementation of UBUS units
up to the capacity of 8 x 2 Mbit/s, for traffic signals with and without CAS
(similar to the UMUX 1300).
It is not possible to increase this capacity for signals without CAS. The
UBUS capacity available is reduced compared to the maximum capacity
depending on the control unit implemented. The UBUS has no dedicated
cross connect but is a tributary to the PBUS cross connect.
PBUS The 1/1 switch architecture is non-blocking with a total capacity of 128 x
2 Mbit/s equivalents with and without CAS.
The capacity available is reduced compared to the maximum capacity
depending on the control unit implemented.
Units with PBUS access feature a high density of traffic interfaces. This
allows the implementation of far more interfaces per unit as compared to
UBUS units with similar types of interfaces.
Due to the high density of traffic interfaces, the compact power supply
unit and the subrack with 21 slots, it is possible to implement traffic
interfaces up to the full PBUS capacity of 128 x 2 Mbit/s.
SBUS The SBUS of the UMUX 1500 allows the internal handling of the SDH
signals provided via the STM-1 interfaces. The SBUS has no dedicated
Management
Overview The UMUX Access Systems are mainly used as network elements in the
access network. The UMUX equipment also fits into small, dedicated
networks and operates as stand-alone equipment.
The requirements on the management tool for the commissioning, the
control of operation and maintenance of the NEs depend therefore on the
size of the network and the local requirements for management
communication. In order to provide economic and flexible management
communication, the UMUX provides two software tools, the EM UCST
and the EMS UNEM, as well as various interfaces for management
communication.

Figure 1-6: Management and access of the UMUX with the UCST
and UNEM
UMUX 1500
UMUX 1200
UMUX 1300
UMUX 1100(E)
UMUX 1500
UMUX 1200
UMUX 1300
UMUX 1100(E)
Transport Network
UCST
UNEM Access Network
UMUX 1500
UMUX 1200
UMUX 1300 UMUX 1500
UMUX 1100(E)
UMUX 1200
UMUX 1300
UCST
UMUX 1100(E)
Element managers UCST and Both managers, the UCST and UNEM, can configure and manage the full
UNEM range of the UMUX and DSL equipment. The UCST provides local or
remote access to one NE at a time, either for NE configuration or for NE
status and/or performance interrogation. The UCST can be connected to
the NE either locally via corresponding interfaces of the control unit, or
remotely via any of the management communication structures provided
for the UMUX. With the UCST, it is also possible and common practice, to
create configurations off-line, for later download to the NE(s).
The UCST is used for initial commissioning, local NE configuration, local
fault and performance monitoring. The UCST manager is also suited to
manage small access networks.
The UCST provides a structured user interface (menu) based on dialogues,
selection boxes, graphs and mouse selection. It is also possible to establish
the configuration for the NE off-line. The configuration data is only
downloaded to the NE after the establishment of a corresponding
management communication channel between the EM and the NE. The
proper set-up of the management communication for a NE, requires local
commissioning of the NE with the UCST, even if the corresponding
configuration has been created off-line.
The UCST R5A software runs on the PC type of computers under the
Windowsâ 98, ME, NT and 2000 operating systems.
The UNEM basic package provides administration and simultaneous
supervision and performance control for all network elements of medium
to large access networks. Options are available for
• Multiple EOC or EA extensions
• Multi-user environment including X-terminal

• Distributed deployment of EM and EA

• Synchronisation network view
• Foreign element alarming
• Active sections
• SNMP (alarms only)
• IP tunnelling for F-addresses
The UNEM features a sophisticated graphical user interface and includes
the functions of the UCST. The UNEM runs on workstations under the
UNIX operating system.
Management communication As the figure above shows, the two managers provide various ways to
access the UMUX NEs:
• The UCST can access single UMUX Access Systems directly. The Access
System can be a stand-alone system or an NE, which is part of the
access network. The UCST also manages small clusters (networks) of
UMUXs. The UCST accesses the NEs via the transport and/or access
network.
• The UNEM manages network elements in a network. The UNEM
accesses the NE either via the transport network or directly via the
(access) network.
The management communication of UMUX has to cope with different
and changing conditions in the transport and access network. At the
same time, it must remain compatible with implemented network
elements.
The UMUX 1500 management communication is based on TCP/IP.
Dedicated communication channels in the access and the transport
network transport the UMUX management communication. Several types
of channel are available in order to maintain the flexibility of management
and to adapt to the requirements of the transport and access network.
• ECC (Embedded Communication Channel)
− The ECC is an in-band communication structure for the UMUX
1500 NEs. The NEs route the communication from the EM via the
ECC structure to the addressed NE. The ECC provides a bandwidth
of up to 2 Mbit/s. The ECC is proprietary and available for the
UMUX 1500 only.
− The transport of the UMUX 1500 management communication via
SDH transport networks requires the encapsulation of TCP/IP into
OSI, which is the stack used for the DCN of SDH. This process is
called the tunnelling of TCP/IP in OSI and is available with the
COBU<X> control units released with the UCST R4D.
• LAN
It is possible to connect the UMUX 1500 Access Systems to a LAN and
access them via a LAN from the EM(S) connected to the LAN. The
COBU<X> control units provide an Ethernet 10BaseT LAN interface.
• EOC
The EOC (Embedded Operation Channel) is used for access networks
with mixed types of UMUX equipment. The EOC is a proprietary
communication structure for UMUX Access Systems based on the

SIFOX unit. The EOC requires a time slot in the data transmission
network and provides a net transmission rate of 9600 kbit/s.
Due to the limited throughput of the EOC, download of
embedded SW via the EOC is not recommended.
Management access and For management communication, the UMUX 1500 features 3 physical
interfaces interfaces, the F-, Q1- and QX-interface, and the inband interface for the
ECC (Embedded Communication Channel). It is possible to segment the
management access of the EM to the UMUX 1500 as follows:
• Direct access to the NE by means of a (physical) point to point
connection.
Such access is typically established via the F-interface. The access is
established as a
− local point-to-point connection between the EM and NE.
− remote access via a modem for a point-to-point connection
between the EM and the NE.
• Local access
− via a LAN
The control units of the UMUX 1500 provide an Ethernet LAN
interface, which allows you to connect the EM(S) and the NEs to a
LAN. The LAN access is established via the QX-interface (Ethernet
10BaseT).
− via the Q-bus (Q1-interface)
The control units of the UMUX 1500 provide a Q-bus interface,
which allows you to connect a local cluster of NEs to the local Q-
bus.
The UMUX 1500 control units additionally provide the Q1-master
interface. This interface allows you to access a local Q-bus via the
ECC. The Q1-master interface provides remote access to local Q-
buses.
• Remote access to the NE by means of in-band management
communication with the ECC (Embedded Communication Channel).
The EM accesses the ECC management communication structure
physically via any UMUX 1500, which is acting as a gateway to the
ECC network. Preferably, this access is established via the QX-Ethernet
interface.
• Remote access to the NE by means of an external (out-band)
communication structure.
This communication structure can be organised as a data
communication network. For communication, it is required to build up
a communication channel between the EM and the NE throughout
this communication structure. The EM and the NE connect via their
(physical) management interfaces to the communication structure.
Such access is typically established via the EOC (Embedded Operation
Channel) for access networks with mixed types of UMUX equipment.
The EOC is a proprietary communication structure for UMUX Access
Systems based on the SIFOX unit. The EOC uses 1 timeslot in the data
communication network and operates with a net transmission rate of

9600 kbit/s. The NEs connect via their F-interfaces and the EM with its
serial interface to the SIFOX units and thus to the EOC.
Software download The functions provided for systems and units are increasingly defined by
the unit software rather than by the unit hardware. This evolution is
underlined with the introduction of software download (for the unit
software ESW) for new units. In contrast to the existing units released
with the UMUX 1100/1300, the unit software of the new generation
units is no longer an integral part of the unit hardware, but can be
updated by means of software download. The hardware's functionality is
enhanced! SW download is a standard commissioning and maintenance
process integrated into the management concept of the UMUX 1500 and
is controlled via the EM.
SW download has major consequences:
• The functionality of a new generation unit is defined only when the
ESW is assigned to the unit. This assignment is accomplished via the
EM within the scope of the NE configuration. It is possible to schedule
SW download. This allows homogenous enhancements of features for
whole networks. If necessary, rapid intervention for the
implementation of Service Packs for released software is possible as
well.
• Units featuring SW download are ordered together with a
corresponding SW (licence). No hardware without SW licence is
available. Data carriers with the corresponding ESW are (optionally)
provided together with the ordered hardware.
Installed hardware and ESW can be checked with the built-in inventory
management function at any time. There is no need for local access to the
NE, since inventory and SW download use the same management
communication channels as used for standard remote management
access. The time required for ESW delivery to the NE depends heavily on
the capacity of the communication channel involved. Traffic and system
operation is not affected during software delivery. The time of service
interruption for affected units is limited to the time required for the local
SW installation, the unit reconfiguration and rebooting.

Compatibility
The design of the UMUX 1500 Access System guarantees compatibility
with existing units and UMUX systems for external and internal interfaces
(where applicable).
Internal interfaces The UBUS interface and the µC-LAN interface of the UMUX 1500 are
compatible with the corresponding UBUS interfaces of the
UMUX 1300/1100(E) multiplexers. The compatibility covers the functional,
electrical and mechanical parameters (bus connector) of the interfaces.
This compatibility ensures the implementation of existing UBUS units in
the UMUX 1500.
The power supply for the units uses the same connector as the UBUS and
remains compatible with the UMUX 1100(E)/1300.
There are no other commonly used internal interfaces.
System compatibility of
functions
Traffic functions Since it is possible to implement most traffic units available for the
UMUX 1300/1100(E) with the UMUX 1500 and UMUX 1200, the
functions provided by these units remain compatible between the
systems. The EM features the same sets of parameters for the control of
the units function and operation for either type of system.
New functions and units implemented with the UMUX 1500 and
UMUX 1200 are not generally backward compatible with the
UMUX 1300/1100(E) since they are based on the new architecture and
features of the UMUX 1500 system. However, the EM provides similar
dialogues to control similar functions.
System functions The availability of system functions with the UMUX 1500 such as
synchronisation, alarm handling and management communication is not
principally different from the corresponding functions of the
UMUX 1300/1100(E). Due to the enhanced features of the UMUX 1500
system, parameters and the control of such functions have become more
flexible and comprehensive.
The UMUX 1500 also features new system functions such as ECC
(Embedded Communication Channel), protection for the control unit, SW
download for unit software (Embedded Software) and inventory
management none of which are available with existing UMUX systems.
System compatibility of It is possible to operate traffic and transmission units released with the
units UMUX 1300/1100(E) with the UMUX 1500 (release provided), with some
exceptions however:
• It is not possible to use the
− CENCA control unit
− POSUP power converter unit
in the UMUX 1500 subrack.

The POSUA AC/DC converter unit is not released for the UMUX 1500.

• It is not possible to use the power supply units and special units
designed for the UMUX 1100(E) (3 HU of unit height) with the
UMUX 1500, in particular it is not possible to implement the:
− MIPOS
− MIRIG
− MISUP
− MIFAN
It is not possible to use the new FANU2 unit introduced with the
UMUX 1200 in the UMUX 1500 subrack.
• Not all traffic units available for the UMUX 1300/1100 (E) have been
released for the implementation with the UMUX 1500.
Only units released for the UMUX 1500 must be
implemented!
Detailed information on the availability of units is provided in the

chapter 9 "System and Ordering Information" at the end of this
document. The paragraphs following give a short overview of the
compatibility of units and interfaces.
UBUS units Previously released UBUS (traffic) units can be plugged into and operated
within the UMUX 1500 as far as they have been released for use in this
system. A list of all units released for the UMUX 1500 is available in
chapter 9 "System and Ordering Information" at the end of this
document.
New UBUS units are compatible with the UMUX 1500. Compatibility with
the UMUX 1300/1100(E) multiplexers has to be checked against the
corresponding compatibility lists.
PBUS units PBUS units have been designed specially for the UMUX 1500 system and
are dependent on the PBUS for operation. Therefore, it is not possible to
use the PBUS units with the UMUX 1300 and UMUX 1100(E).
SBUS units SBUS units have been designed specially for the UMUX 1500 system and
are dependent on the SBUS for operation. Therefore, it is not possible to
use the SBUS units with the UMUX 1300 and UMUX 1100(E).
Control units The control units are specific for each brand of UMUX Access System and
are not interchangeable between the UMUX 1300/1100(E) (with the
CENCA control unit) and the UMUX 1500 (with the COBU<X> control
units).
Power units The UMUX 1500 operates with the POSUS DC/DC power converter unit.
It is not possible to use existing power supply units (such as the POSUP)
with the UMUX 1500. With the UMUX 1500, you can only use power
supply units that are released for the UMUX 1500.
For the use of the POSUS with the UMUX 1300, refer to the
corresponding system information.

Tributary and aggregate

interfaces
General The interfaces provided by identical units are compatible independently of
the type of UMUX Access System in which you operate the units.
Similar types of interface on different units and/or UMUX Access Systems
are partially compatible. The parts of the interfaces not compatible are
mainly due to enhanced functionality provided with new units and
systems.
PSTN The PSTN interfaces remain compatible as outlined in the paragraphs

above on "System compatibility of functions".
The PSTN units PHLC<X> feature a high density of subscriber line
interfaces, such as is required for V5.x applications.
It is possible to operate the interfaces of the PHLC<X> in the modes
• V5.x
• MCAS Direct Line
• Carrier Adapter
• Phone-Exchange
The interfaces implemented on a unit all operate in the same mode (of
operation) with identical sets of parameters.
The SUBLA type of subscriber line interface allows the individual setting of
operation mode and parameters per subscriber line interface but requires
the RIGEN ringing generator unit. The V5.x modes are however not
available for SUBLA<x> and there is no subscriber line test facility available
for SUBLA<X> units.
The PHLC<X> units provide interfaces and ringing generator.
2 Mbit/s The 2 Mbit/s interfaces remain compatible as outlined in the paragraphs

on "System compatibility of functions" above.
The LOMIF/LOMI4 unit can terminate 2 Mbit/s structured signals and
handle 2 Mbit/s structured and unstructured signals for transparent cross
connection.
Additional features of the LOMIF/LOMI4, SYNAC and SYNAM are the
handling of PRA functionalities and the re-timing capability for
transparent 2 Mbit/s traffic signals. These units feature enhanced
performance monitoring and trail handling. The 2 Mbit/s traffic interface
of the LOMIF/LOMI4 unit can be configured to remain compatible with
the traffic interface of the MEGIF unit.
The MEGIF terminates structured signals only and cannot handle
structured or unstructured 2 Mbit/s signals for transparent cross
connection.
STM-1 The STM-1 interfaces are available with the UMUX 1500 and UMUX 1200
only and remain compatible as outlined in the paragraphs on "System
compatibility of functions" above.

Management
Management systems The operation and maintenance concept for the UMUX platform relies on
the UCST and UNEM element and network managers.
The UCST is the element manager required for the initial commissioning
of any UMUX Access System and recommended for the management of a
single UMUX or small networks of UMUX family products. The UNEM
(UMUX Network Element Manager) manages medium to large sized
UMUX networks.
Both the UCST (release 3.3a/1 and higher) element managers and the
UNEM are compatible with all UMUX Access Systems including the
UMUX 1500.
The improved system dialogues feature more graphical elements and an
easy to use dialogue for the configuration of cross connections. The entry
to the dialogues for the configuration of units is based on functional
layers. For existing units, the dialogues for the configuration of
parameters are almost identical (provided minor differences) compared to
former UCST versions.
Interfaces The UMUX 1500 features the same types of management interface as
provided with the UMUX 1300/1100(E) multiplexers, and additionally the
new QX-Ethernet interface. Due to the enhanced features of management
communication and SDH, the UMUX 1500 uses more powerful protocols
stacks. The availability of stacks depends on the selected control unit
COBU<X> however.
Although the control units of the UMUX 1500/1200 and
UMUX 1300/1100(E) are different, the management interfaces of the
control units provide functionally (and partially physically) compatible
interfaces for management communication:
Tab. 1-1: System compatibility of management interfaces
Management Compatibility of the UMUX 1200 and 1300/1100(E)
Interface functional physical
F Yes Connectors different

Q1 Yes Connectors different
QX not available for the Not applicable
UMUX 1300/1100(E)
The F-interfaces of the UMUX 1300/1100(E) and the UMUX

1500 use different protocol stacks.
Communication With the UCST R4D (or higher) the menu for the connection of the EM is
common for all UMUX Access Systems. The availability of interfaces and
protocol stacks depends on the selected type of NE (subrack and control
unit assigned).
The management communication via the structures EOC and Q-bus,
provided with the UMUX 1300/1100(E), are also fully implemented for the
UMUX 1500. The communication remains compatible, if the UCST is a
release 3.3a/1 and the UNEM a release R3.0 (or higher).

The new ECC management communication structure can be used for the
UMUX 1500 with the COBUX/COBUV control units only and is not
implemented for the UMUX 1300/1100(E).
Tab. 1-2: System compatibility of management communication
Channel functional physical
Q-bus Yes Yes

Q1-master IF Yes UMUX 1500 only
EOC Yes Yes
ECC UMUX 1500 only Not applicable
(COBUX, COBUV)
Compatibility with previous

releases
NE configuration With the UCST R5A it is possible to read and modify configurations of NEs
created with previous releases of the UCST or UNEM.
For functions (units) not supported with the new UCST the backward
compatibility for configurations depends on the general availability of the
function (unit).
• For functions (units) no longer supported:
The UCST R5A is not able to read configurations containing such
functions (units). To read and modify the configuration you must use a
previous release of UCST supporting the required functions (units).
• For functions (units) still supported but not available with UCST R5A:
You can read and modify the configuration with UCST R5A. It is
however not possible to create new configurations containing such
functions (units).
It is not possible to convert configurations of other UMUX into
UMUX 1500 configurations.
Functions and units You can upgrade existing functions (units) via the conversion function of
the UCST to more recent and powerful functions (units) if the
hardware/software requirements are satisfied:
• The new UCST software must be installed.
• The new ESW (Embedded SoftWare) providing the new function (unit)
has to be delivered and installed on the corresponding unit.
• The hardware implemented and the new ESW have to be compatible
(refer to the corresponding compatibility lists).
Upgrade procedures The recommended upgrade procedures allow you to control the
provisioning of existing installations with the new UCST management SW
and new ESW for the COBU<X> control units.

ascom
System Architecture 2
Block diagram
The block diagram below shows the main elements of the UMUX 1500
Access System.
Figure 2-1: Block diagram of the UMUX 1500
SYNIO SYNIF SYNIC SYNAM SYNOT FUTURE

OPTION
VC-4 VC-4 VC-4 TU-12 VC-4
2 x STM-1 [AD] <--> 1 x STM-1 [X] 2) Sector B

SBUS
2 x STM-1 [AD] <--> 1 x STM-1 [X] 2) Sector A
SYNAC SYNVA FUTURE PCONV PCON2 LOMIF PHLC LEMU6 LAWA4 LESA8
OPTION LOMI4 <X> LEMQ6 LESAP
VC-12 TU-12
PBUS 128 x 2 Mbit/s 1)
-48 Vdc
System Control
COBU<X> POSUS
System Control POSUS
POSUS
Management
COBU<X> POSUS
Alarming Management POSUS
Synchronisation POSUS
Diagnostics
PBUS Access of Power
Synchronisation UBUS
th supply
UBUS 8 x 2 Mbit/s 1)
TUNxy LECA2 MEGIF SIFOX GECOD NEMCA NEMCA

SULIx SUBLx lSBUQ Special
LE2Q2 UNIDA EXLIx EXLAx ISBUT
1)
Capacity availability depends on the COBU<X> control unit
2)
[AD] Add Drop
[X] Through connect

Ascom System Architecture
Bus Structures and Cross In order to cope with the requirements for high bit-rate traffic interfaces,
Connection enhanced internal traffic switching capacity and compatibility with existing
traffic units, three different buses for traffic data have been implemented
with the UMUX 1500:
• PBUS
• UBUS
• SBUS
While the PBUS is a completely new design created for the UMUX 1500
Access Systems, the UBUS has been introduced already with the
UMUX 1300/1100(E) multiplexers.
The SBUS is also a new design created for the UMUX 1500 and carries the
SDH format signals.
PBUS The PBUS is a bus structure for traffic signals of various formats with and
without CAS. The PBUS provides a non-blocking cross connect with the
equivalent capacity of 128 x 2 Mbit/s for traffic signals with and without CAS.
The formats are set individually for each termination. The PBUS allows cross
connections for 2 Mbit/s and n x 64 kbit/s (n = 1 ... 31) traffic signals.
The PBUS provides digital cross connections for the levels DXC 1/1 and
1/0. The 1/1 cross connect of the UMUX 1500 allows the "bit and clock
transparent" switching of structured and unstructured 2 Mbit/s signals.
All types of cross connections may be bi-directional, unidirectional or of
the broadcast type.
The PBUS consists of 32+1 physical bus lines each with a bit-rate of 16384
kbit/s. 32 PBUS lines are available for traffic signals. The remaining bus line
is used for diagnostics and other system purposes and is not available for
traffic signals (payload). Each PBUS line carries 4 x 2 Mbit/s of traffic
signals and the corresponding signalling information in additional TSs.
The architecture of the PBUS provides linear bus access. Any PBUS unit
can read all the information from the PBUS but can write to one (or more)
assigned PBUS line(s) only.
The access to the PBUS is established via an application specific circuit,
which handles, among other things, the write access for 1 PBUS line,
corresponding to 4 x 2 Mbit/s of traffic signals and corresponding
signalling information. One (or more) of these ASICs is implemented on
each PBUS unit that provides cross connection and termination for traffic
signals. An active access circuit always seizes all 4 assigned 2 Mbit/s
highways.
The PHAU number (PBUS highway Access per Unit) provided with each PBUS
unit indicates the maximum number of PBUS highways accessed by a unit.
Since the cross connect is distributed on the PBUS, the cross connections are
resistant to single points of failure. Due to this design, the UMUX 1500
Access Systems provide a highly reliable and economic cross connect.
All newly created units with traffic volumes of 2 Mbit/s or higher bit rates
have access to the PBUS. This also applies to some of the SBUS units. The
PBUS interface of such units is identical with the PBUS interface of PBUS
units. The PBUS is connected to all the slots of the subrack except slot 21.
The number of accesses to the PBUS available depends on the COBU<X>
control unit implemented.

Units providing PBUS access (and no SBUS access at the same time) for
their traffic interfaces and/or signals are PBUS units.
UBUS The UBUS has already been implemented with the UMUX 1300/1100(E)
and provides a total bus capacity of up to 8 x 2 Mbit/s. The capacity of the
UMUX 1500 implementation of the UBUS remains the same for signals
with and without CAS. The access to the UBUS is based on n x 64 kbit/s
TSs. The UCST R4D, and more recent versions of the EM, provide an
automatic mode for setting connection points to the UBUS.
You can select the UBUS "Expert Mode" which allows you to set
connection points manually. In contrast to the UMUX 1300/1100(E) the
connection points for traffic signalling are automatically set independently
of whether the traffic signal uses CAS or not. The UMUX 1500 signalling
highways are not available for the cross connection of traffic signals
without CAS. The UMUX 1500 implementation of the UBUS allows the
existing traffic and aggregate units available with the UMUX family to
operate.
Like the generic UBUS, the UMUX 1500 implementation of the UBUS is
divided into a left and a right side set of four 2 Mbit/s highways (each with a
shadow highway structure for CAS signalling). The physical layout of the
highway access for the slots of the subracks differs between the layout with
the UMUX 1500 and the layout with the UMUX 1300/1100(E):
• 21 slots provide access to the UBUS
• Cross over of “upper” and “lower” highways within left and right side
set of highways
• 6 slots with access to all 8 highways
The UBUS of the UMUX 1500 is a tributary to the PBUS. The access to the
PBUS is implemented on the COBU<X> control unit separately for the left
and right side highways. The cross connections for the traffic on the UBUS
are established via the PBUS. Thus, in contrast to the CENCA control unit,
the COBU<X> does not feature any cross connect functionality for the
UBUS. The number of UBUS highways available depends on the type of
the control unit implemented.
The UBUS determines not only the structure for traffic signals but also
includes standard channels for processor communication, system timing
and power rails. All units implemented in the UMUX 1500 have access to
at least this second set of signals.
Units providing UBUS access for their traffic interfaces and/or signals are
UBUS units.
SBUS The SBUS carries SDH traffic signals to allow drop and insertion of traffic
signals from/to STM-1 signal frames as well as the through connection
between STM-1 interfaces for the traffic signals that remain in the STM-1
frame. The structure of the VC-4 container can be set to VC-3 and VC-12
structures or to a mixture of both.
The SBUS consists of DROP and ADD buses for the traffic signals and
several auxiliary signals e.g. signals for synchronisation. The 2 DROP and
ADD buses carry essentially synchronised TU-12 signals. To access the
SBUS there are 2 types of units provided: units with aggregate and access
interfaces, each type of unit access' the SBUS differently.

• Aggregate interfaces write the contents of an STM-1 signal frame to

an assigned DROP bus and read back selected traffic signals from a
second DROP bus and the assigned ADD bus.
• Access interfaces read selected traffic signals from either of 2 DROP
buses and write selected traffic signals to any of 2 ADD buses.
The STM-1 aggregate interfaces are implemented on dedicated traffic
units. These terminate VC-4 and provide frame synchronised SDH signals
as TU-12 or TUG3 structured traffic signals to the SBUS. Units with access
interfaces terminate the structured traffic signals provided on the SBUS.
The SYNAC unit for example terminates VC-12 and writes corresponding
2 Mbit/s signals to the PBUS and reads 2 Mbit/s signals from the PBUS
respectively. SDH traffic switched via the SBUS from aggregate to
aggregate interface does not impede the internal PBUS capacity of the
UMUX 1500.
The specific structure of the SBUS allows the implementation of 2 STM-1
interfaces on the SBUS to
• ADD and DROP VC-12 traffic signals into/from from 2 STM-1 frames.
• Cross connect VC-12 and VC-3 traffic signals between 2 STM-1
interfaces. The UMUX 1500 is however not considered as an SDH cross
connect.
Normally a mixture of both ADD/DROP and cross connect are
implemented. With 1 STM-1 interface the UMUX 1500 terminates the
STM-1 signal.
The UMUX 1500 subrack provides 2 independent SBUS sectors, each
sector with features and capacity as stated above:
• Sector A (to the left): Slots 2 - 9
• Sector B (to the right): Slots 15 - 20
With the UCST R5A it is possible to operate both SBUS sectors
simultaneously. The 2 SBUS sectors constitute one logical SETS system
(SETS is an NE level function). For details of the SBUS access, refer to
"Configuration of the subrack" in the chapter "System and Application
Notes".
Units providing SBUS access for their traffic interfaces and/or signals are
SBUS units. Units providing SBUS and PBUS access at the same time are
also SBUS units.
System control The system control of the UMUX 1500 relies on a central control block
and on processors on the peripheral units (traffic, aggregate units). Such
decentralised processing can control several functions if required (unit
control and control of traffic interfaces). The processors use dedicated
communication channels (µ-LAN, ICN) for the communication between
the central control and the peripheral units.
The system control block is implemented on the COBU<X> control units.
A second control unit (of the same type) can provide protection for the
system control. The central control
• manages the NE configuration
• controls the system operation

• management communication
• synchronisation
• monitors the system performance
The control block holds copies of the ESW that runs on units with
software download and controls the installation of such ESW on the units.
All the information on system/unit configuration is stored and
administrated via the management information database. In the case of a
redundant control unit, the management information database of the
standby control unit is continuously updated.
The control unit holds the various interfaces for the management
communication to the EM or EMS and provides the access to the ECC
(availability depends on the control unit). The local alarm interfaces (inputs
and outputs) are implemented on the control unit as well.
Additional functions such as UBUS access, synchronisation, diagnostic and
conferencing functions are also implemented on the control unit, but are
not directly part of the central control. The implementation and availability
of these functions depend on the COBU<X> control unit and the system
release.
Communication between The communication between the central control block and the processors
controllers on the peripheral units is established via 2 different internal
communication structures. Depending on the type of unit, the ICN
channel serves the PBUS and SBUS units, while the µC-LAN serves UBUS
units.
The communication channels are embedded in the physical structures of
the PBUS and the UBUS respectively.
Synchronisation and system The UMUX 1500 provides PETS and SETS for the NEs with STM-1
timing interfaces. The SETS function is implemented on the STM-1 aggregate
units. The main part of PETS timing system and the clock control block is
implemented on the COBU<X> control units.
Systems without SDH signals use PETS only. In systems with SDH, the NE
can operate the PETS and SETS autonomously without a fix-phased
relationship between the SETS and PETS synchronised equipment. If
required the PETS timing system is synchronised to SETS.
The timing signals are groomed and distributed via dedicated timing
signal lines which are embedded in the physical structures of the UBUS,
the PBUS and the SBUS respectively. Traffic units provide timing signals to
the signal lines as configured during system commissioning. The control
unit features interfaces to input and output timing signals from and to
external equipment.
The NE can be synchronised with incoming traffic signals (i.e. the clock is
extracted from traffic signals) or with the 2 MHz signals provided at the
terminals for external clock signals. If both sources fail the Access System
synchronises to its internal timing source(s) (Timing source(s): PETS (and
SETS)). The NE provides a second set of terminals for timing signals for the
synchronisation of external equipment.

The selection algorithm and provisioning of clock signals is programmable

in order to prevent loss of synchronisation and to avoid synchronisation
loops. The system handles both timing signals using SSI and SSM.
The UMUX 1500 supports PETS and SETS (depending on the SBUS unit)
equipment protection.
Power supply The UMUX 1500 needs only one primary power source for operation. Any
voltages required for system operation are generated locally in the
subrack.
The power supply unit(s) convert the primary voltage to the internal
power supply voltage of +5 V/-5 VDC required for the operation of the
units. The converted power is distributed to the units via power rails,
which are embedded within the physical structure of the UBUS.
The nominal range for the primary supply voltage is -48 VDC or -60 VDC
with the 0 volt potential connected to signal ground.
It is possible to protect the local power supply with additional power
converter units from a n+1 up to a real 1+1 protection. All power
converter units implemented operate in load share mode.
Traffic units All traffic units are implemented as peripheral units and connected via
their corresponding (traffic) bus structure(s) to the UMUX 1500 core
system.
Traffic units connected to the
• PBUS provide
− n x 2 Mbit/s access for structured and unstructured signals or
− n x 64 kbit/s (n = 1 ... 31) for structured signals terminated on the
unit or for units providing n x 64 kbit/s traffic signals.
• UBUS provide
− n x 64 kbit/s (n = 1 ... 31) access for structured signals terminated
on the unit (units with aggregate interfaces) or for units providing
n x 64 kbit/s traffic signals.
• SBUS provide (for each of the 2 SBUS sectors)
− n x STM-1 (n= 1, 2) access for units with aggregate interfaces
− n x TU-12 or TUG-3 (FUTURE OPTION) access for units with access
functionality. The access to the PBUS (if applicable) is n x 2 Mbit/s
structured and unstructured or TU-12 (FUTURE OPTION).
Subrack Although not shown in the block diagram of the UMUX 1500, the
subrack is an important functional block of the UMUX 1500. The subrack
provides the mechanical and electrical infrastructure for the operation of
all units. The subrack guarantees the interconnection between the units
via the bus structures and provides the interface for the DC power supply.
The subrack supports the inventory management.
The UMUX 1500 subrack allows the installation of the UMUX 1500 in 19-
inch and ETSI racks.

Implementation of functional blocks

Functions and features The UMUX 1500 is a Access System with highly modular functions and
features. Each UMUX 1500 NE and thus the applicable system features are
defined by 2 elements:
• the UMUX 1500 subrack
• the selected COBU<X> control unit
You can have all the system features defined for the UMUX 1500 or a
subset of those features depending on the control unit implemented with
the UMUX 1500 subrack.
The implementation of control units that are optimised for typical
applications allows the customer to provision cost optimised Access
Systems for a particular application, while still preserving the option of a
later system upgrade.
With the UCST 3.3a/1 the following rules apply for the
selection of the NE and the control units:
• Select the NE UMUX 1500
to configure a full feature multi-service Access System
UMUX 1500. The corresponding COBUX control unit will be
automatically presented for selection (the COBUV is not
available with UCST 3.3a/1).
• Select the NE UMUX 1400
to configure a cost optimised Access System for voice
and ISDN services including V5.x service provisioning
(corresponds to a subset of the features UMUX
1500/COBUX). The EM presents automatically the COBUQ
control unit for selection.
The UMUX 1400 is not available with the UCST R4<X> and R5<X>. The
UMUX 1500 with COBUQ fully replaces this functionality.
Architecture and functional The majority of functional blocks that you can identify in the block
blocks diagram are implemented on units. Most of the units are dedicated to
some particular type of interface or functional block. Some of the units
(e.g. the control unit) provide the physical platform for the
implementation of several functional blocks.
Control units The system control block is implemented on the control unit. The control
units are unique to the UMUX 1500. Depending on the required NE
functions, you can select one out of several types of control units.
The control unit has a high performance on-board CPU and uses software
download for its own unit software (ESW). A major task of the control
unit is the maintenance of the NE database (MIB), which covers the
complete information of the NE configuration and all ESW loaded to the
NE. The control unit also holds important auxiliary functions. Such
auxiliary functions (features and availability depend on the selected
control unit) are:

• Management interfaces of the NE

• Management access to the ECC (COBUX and COBUV only)
• Management and selection of timing sources and clock control
• UBUS access to the PBUS
• Conference for voice and CAS signals (COBUV only)
• Diagnostic functions (COBUX and COBUV only)
• PETS
• Interfaces for synchronisation signals (input, output)
• Local alarm interfaces (input, output)
The UMUX 1500 allows the implementation of a redundant control unit.
The redundant control unit is in hot standby mode. If the active
equipment fails, the redundant unit takes over the system control. The
switchover can affect, for a short period, the traffic on the UBUS and
PBUS.
The configuration and MIB stored on the standby control unit is
continuously updated and thus identical to the information on the master
control unit. Hence, the redundant control unit can take over system
control with a cloned database.
The switchover due to equipment failure is non-revertive. You can initiate
a switchover at any time via the EM or EMS.
2 slots in the UMUX 1500 subrack are reserved for the master control unit
and the corresponding backup unit. If this redundancy is not implemented
the slot is available for other units.
Power unit The power unit converts the external supply voltage of nominal -48 VDC to
the NE internal supply voltages of +/- 5 VDC. The power unit has no
specific BUS designation, since it has no (traffic) access to internal buses
and does not feature a processor of its own.
The UMUX 1500 allows several power supply units for simultaneous
operation in a subrack, depending on the power consumption of the units
implemented and requirement for power backup (redundancy). The
power units operated in parallel share the load among the units. The load
sharing provides less stress to individual units and thus higher reliability.
Additionally n+1 or full 1+1 unit protection can be implemented for
power supply units.
The power converter units can be inserted into any of the slots of the
subrack of the UMUX 1500 (Slot 21 is preferred for the first unit
implemented).
Traffic units
PBUS units PBUS units have direct access to the PBUS and thus to the cross connect.
Hence, PBUS units provide a traffic capacity of several times 2 Mbit/s.
The PBUS units are µ-processor controlled and feature SW download for
the unit SW (ESW). The unit program code is locally stored in a non-
volatile flash EPROM or, in cases such as the PCON<X>, in a volatile
program memory. While the program code, once copied to non-volatile
memories, is available for execution, the volatile memories need to be

reprogrammed with the program code after each power up. PBUS units
feature full inventory management for information on unit hardware and
software.
For more information on PBUS unit functions, refer to the unit
descriptions below and the corresponding user guides.
SBUS units SBUS units have direct access to the SBUS. Some of the SBUS units also
have access to the PBUS and the associated cross connect. Accordingly,
SBUS units provide a traffic capacity of several times 2 Mbit/s.
The SBUS units are µ-processor controlled and feature SW download for
the unit SW (ESW). The unit program code is locally stored in a non-
volatile flash EPROM or, in cases such as the SYNI<X>, in a volatile
program memory. While the program code, once copied to non-volatile
memories, is available for execution, the volatile memories need to be
reprogrammed with the program code after each power up. SBUS units
software.
For more information on SBUS unit functions, refer to the unit
descriptions below and the corresponding user guides.
UBUS units UBUS units have direct access to the UBUS. Although UBUS units have no
direct access to the PBUS they are indirectly connected to the PBUS via the
UBUS highways, which are tributaries to the PBUS. Depending on the
selected control unit, the full UBUS capacity of 8 x 2Mbit/s or half the
capacity of 4 x 2 Mbit/s is available to connect UBUS units. Traffic units,
which feature aggregate interfaces of a capacity of 2 or 4 x 2 Mbit/s
(MEGIF or TUNO<X>) load the UBUS rather than the PBUS.
Due to the UBUS implementation in the UMUX 1500, most UBUS units
released with the UMUX 1300/1100(E) are also compatible with the
architecture of the UMUX 1500.
Although µ-processor controlled, previously released UBUS units do not
feature SW download and provide reduced inventory data (Slot
designation, unit name, HW key, SW version). The unit program code is
locally stored in PROMs. Information on unit hardware and software is
available within the scope of system discovery. In contrast to this the new
generation of UBUS units (such as the ISBUQ and ISBUT) feature both SW
download and inventory management.
For more information on the functions implemented with UBUS units and
the operation of the units, refer to the user guides for the units.

Subrack
Function Although the subrack is not directly identified as a functional block, it is
an important element of the architectural implementation of the
UMUX 1500. The subrack provides the electrical and mechanical
infrastructure for the units and is an integral part of the EMC concept of
the UMUX 1500. The subrack provides the following system functions:
• Connection to and distribution of the primary power supply voltage
• Internal distribution of converted power (power rails)
• Distribution of signals
• Connection of slots to the UBUS, PBUS and SBUS (2 sectors)
• Installation/connection and grounding of signal cables
• Mechanical installation of units
• Electrical connection of the units to power supply, buses and control
signals
• EMC and EMD protection for system and units
• Mechanical protection for units and components
• Inventory data of the subrack (backplane)
• Installation of the NE into racks and cabinets.
All cables connected to the UMUX 1500 are fixed onto a cable tray.
Although the cable tray is a separate unit (for the convenience of
installation), it is an integral part of the basic mechanical equipment of the
UMUX 1500. The subrack is always installed together with its cable tray.
Complementary mechanical elements and subsystems such as
• heat deflection shield
• fan unit
• ETSI adapters
• etc.
are optionally provided for the UMUX 1500.
Slots in the subrack The UMUX 1500 subrack features a total of 21 equally spaced slots.
While the slots are identical from a mechanical point of view, the access
to the buses varies. Segments made of several slots with identical bus
access can be identified for each bus. The implementation of traffic units
in slots is mainly limited by the bus access. Control units can be
implemented on dedicated slots only. It is possible to plug the power
converter units into any slot of the subrack. The figure below shows a
synoptic overview of the subrack, bus access per slot and the
implementation of control and power units in the subrack.

Figure 2-2: Bus access, control and power units for slots of the
UMUX 1500 subrack (graphical view)
UBUS 4 Hwy.s
UBUS 4 Hwy.s
PBUS
SBUS (sector A) SBUS (sector B)
CU CU
Power Supply Unit (POSUS)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
CU = Control Unit
The table below summarises the slot information on bus access and the
implementation of control and power units.
Tab. 2-1: Bus access, control and power units vs. slots of the
UMUX 1500 subrack
Slots
Access Unit type 1 2-9 10 11 12 13,14 15,16 17-20 21
COBU<X> ü ü
POSUS ü ü ü ü ü ü ü 1)
ü
UBUS UBUS ü ü ü ü ü
4 Hwy.s
UBUS UBUS ü ü ü ü
8 Hwy.s
PBUS PBUS ü ü ü ü ü ü ü ü
SBUS_A SBUS 2)
ü
SBUS_B SBUS 2)
ü 2)
ü
1)
Preferred slot for first POSUS unit implemented.
2)
The UCST R5A allows the simultaneous use of SBUS_A and
SBUS_B.
4)
The COBUX, COBUV, COBUQ and COBUL control units are
released for the UMUX 1500.

Limiting factors for the The limiting factors for the implementation of units and interfaces are
implementation of units mainly given by the
• remaining capacity on the UBUS (for UBUS units).
• remaining capacity on the PBUS (number of active PBUS accesses).
• number and disposition of free slots.
• availability of the required bus access with respect to the slots
available.
• remaining available power
• power dissipation per slot and per subrack
For details on limiting factors and implementation rules for units, refer to
the chapter 8 "Implementation and Application Notes".

ascom
Functional Descriptions 3
Traffic functions
The traffic functions are outlined with respect to PBUS access and, if
appropriate, to the SBUS. Units with traffic interfaces provide, among
other functions, the following traffic signal related functions:
• SDH multiplexing (termination, add and drop)
• Termination
• Adaptation
• Cross Connection
• Through Cross Connection
• Traffic signal processing
SDH multiplex functions The figure below shows the STM-1 multiplexing structure according to the
ITU G.707 recommendations.
Figure 3-1: Multiplexing structure according to ITU-T G.707
x1 x1
STM-1 AUG AU-4 VC-4
x3
x1
TUG-3 TU-3 VC-3
x7
TUG-2
Pointer Processing
x3
Multiplexing TU-12 VC-12 C-12 2 048 kbit/s
Aligning
Mapping
C-n Container-n
The multiplexing structure in the figure above without the paths that are
shaded grey corresponds to the multiplexing structure according to ETSI.

Ascom Functional Descriptions
The UMUX 1500 and the related units provide STM-1 multiplexing and
mapping functions as shown in the next figure:
Figure 3-2: SDH multiplex and mapping functions
x1 x1
STM-1 AUG AU-4 VC-4
x3
x1
TUG-3 TU-3 VC-3
x7
TUG-2
Pointer Processing
x3
Multiplexing TU-12 VC-12 C-12 2 048 kbit/s
Aligning
Mapping
C-n Container-n
The UMUX 1500 provides the optical and electrical STM-1 interface for
SDH traffic signals. The multiplex and mapping functions consist of the
following steps:
E1→VC-12 - E1 (2048 kbit/s) + stuffing bits (adaptation) → C-12 (2176 kbit/s)

- C-12 + Lower Order POH → VC-12 (2240 kbit/s)
Lower Order POH (Path OverHead) consists of remote alarm
indications, Trail Trace Identifier (TTI), Access Point Identifier, etc.
VC-12→STM-1 - VC-12 + pointer → TU-12 (2304 kbit/s)

- 3 x (TU-12) + overhead → TUG-2 multi-frame
(byte interleaved)
- 7 x (TUG-2) + overhead → TUG-3 multi-frame
(byte interleaved)
- 3 x (TUG-3) + Higher Order POH → VC-4 (150.336Mb/s)
Higher Order POH (Path OverHead) consists of Trail Trace Identifier
(TTI), protection switching signalling (APS), etc.
- VC-4 + pointer → AU-4
- AU-4 → AUG
- AUG + RSOH + MSOH + pointer → STM-1 frame
(155.520 Mbit/s)
MSOH (Multiplex Section OverHead) consists of remote alarm
indications, error monitoring, DCC, Synchronisation signalling (SSMB),
etc

RSOH (Regenerator Section OverHead) consists of frame alignment,

Section Identifier, service channel, ,etc.
Signal termination
Terminated signals Terminated P12s signals are demultiplexed (into timeslots) and monitored
for performance. The signal is continuously checked for integrity on the
related trail, e.g. detection of LOS, AIS, bit errors, error detection etc. If
necessary, the UMUX 1500 generates signals to indicate remote errors.
The signals are integrated into the time slot 0 of the data stream leaving
the traffic interface.
Traffic units connected to the UBUS only provide terminated signals.
The STM-1 signals are terminated on corresponding SDH traffic units as
VC-4 signals. VC-12 signals are terminated on the SDH access units,
which provide P12s or P12x on the PBUS. The connection of VC-12 not
terminated on the PBUS is a FUTURE OPTION.
Monitored signals It is possible to monitor the performance of unterminated structured

signals. However it is not possible to write signalling information to the
time slot 0. Monitored signals are treated as transparent signals in cross
connection. This means that monitored signal channels are also fully
transparent.
Transparent signals Unterminated Transparent Signals (P12x) are not terminated since the
complete signal is transparently cross connected. Units with external
interfaces (e.g. the LOMIF/LOMI4) provide limited performance monitoring
also for transparent signals (SES).
Signal adaptation The function Signal Adaptation performs the conversion between the
aggregate and the PBUS or SBUS layer. This includes functions such as
framing/deframing, multiplexing/demultiplexing, bit rate adaptation and
frequency justification.
SDH signals are adapted to the PBUS layer via STM-1 interface units, the
SBUS and dedicated traffic units. These traffic units terminate the SDH
signals (here VC) for the PBUS.
Cross Connection The Cross Connect of the UMUX 1500 represents a switch architecture
implemented simultaneously in time and space. The cross connect is
implemented on the PBUS. Cross connections can be applied for traffic
signals connected via any of the 3 bus systems PBUS, UBUS and SBUS.
For the description of the 3 bus structures and the implementation of the
cross connection, refer to the corresponding paragraphs in the chapter 2
"System Architecture".
The new EM allows you to control the cross connect for all types of
Access System more easily than previous releases of the EM, even if the
functionality of the cross connect has been dramatically increased. The
system architecture and the different buses (of the UMUX 1500) are no
longer visible to you if you access the cross connect menus. The UCST
shows the signals for cross connection directly with the corresponding
traffic interfaces. It is possible to create unidirectional or bi-directional

connections. The EM helps in the configuration and only allows the

connection of matching signal types.
It is possible to create 1+1 protected connections. You configure the
protecting connection for the signal the same way as a standard
connection. Naming signals, creating signal groups and filters for the
display of connections helps to keep a clear overview of cross
connections.
For experienced users, an expert mode is available to connect traffic
signals provided via the UBUS. This allows you to optimise manually the
use of UBUS highways. Additionally the EM provides dialogues to display
the use of highways on the UBUS and the PBUS.
The traffic signals for the cross connection on the PBUS are identified as 2
Mbit/s, n x 64 kbit/s or 64 kbit/s signals. The SBUS does not allow cross
connections. It is however possible to (cross) connect through the V-12 or
VC-3 between 2 STM-1 interfaces within the SBUS sector (sector A and
sector B).
A status dialogue is provided to check the present state of protected
connections together with information on the availability of the
corresponding traffic signals.
n x 64 kbit/s cross connections The cross connections of a 64 kbit/s traffic signal use a single timeslot
(64 kbit/s). The switching of signals n x 64 kbit/s (n = 1 ... 31) uses
multiple timeslots (n x 64 kbit/s) which may be arranged consecutively or
non consecutively within the highways.
The system has 2 options to control the delay created by the cross
connect: Minimum delay and constant delay. Minimum delay is applied by
default for the cross connection of single time slots and consecutively
arranged timeslots of n x 64 kbit/s traffic signals. If the timeslots of an
n x 64 kbit/s connection are not consecutive (e.g. TS 1 ... 3, 7, 8),
constant delay is applied by default. The system control assigns the
respective delay time automatically.
2 Mbit/s cross connections Cross connections can be defined for structured and unstructured
2 Mbit/s signals. Structured signals are terminated on the traffic units.
Unstructured signals are not terminated (i.e. the signal is not
demultiplexed) on the traffic unit but switched transparently through the
cross connect.
VC-12 (cross) connections There are 2 ways to (cross) connect VC-12 signals via the SBUS:
• Through (cross) connection between 2 STM-1 interfaces within the
SBUS sector (sector A and sector B). The signals connected through do
not load the PBUS. Consequently, it is not possible to interchange TSs
in the SDH signal (here VC-12).
• Connection to an SBUS traffic unit for signal termination or for PBUS
access. The PBUS allows cross connections for VC-12 (FUTURE
OPTION).
VC-3 (cross) connections VC-3 signals can be through (cross) connected between 2 STM-1
interfaces within the SBUS sector (sector A and sector B). The signals

connected through do not load the PBUS. Consequently, it is not possible

to interchange TSs in the SDH signal (here VC-3).
V5.x functions
V5.x implementation of UMUX The UMUX provides the V5.1 and V5.2 interface for the LE, V5 protocol
processing and the corresponding user ports in the access network. The
UMUX implementation of the V5 function is based on 3 functions
required for V5.x in the AN and the transport of traffic signals:
• V5 link access (V5 basic function)
• Protocol processing (V5 basic function)
• Transport
• User ports (V5 basic function)
With the UMUX, the 3 basic V5 functions are physically implemented on
separate traffic units. This allows you most flexibility for the transport of
the V5 traffic signals in the access network and the provisioning of user
ports. For each basic function, the UMUX provides a set of units to
implement the corresponding basic V5 functionality for the AN:
• V5.x protocol processing
2 units with different processing power are available, either optimised
for central or for decentral V5 protocol processing:
− PCONV (decentral protocol processing)
− PCON2 (central protocol processing)
• PSTN User Ports
3 units are available for the implementation of PSTN user ports:
− PHLC1
− PHLC2
− PHLC3
• ISDN-BA User Ports
2 units are available for the implementation of ISDN-BA user ports:
− ISBUQ (2B1Q)
− ISBUT (4B3T)
The various capacities of ports provided by each of the units allows you to
economically scale the number of ports per NE. Depending on the type of
unit, you can implement the unit (user ports) in the UMUX 1500 and the
UMUX 1300/1100(E). The transport functionality is provided via the
aggregate interfaces, which are available for the UMUX Access Systems.
The UMUX implementation of V5 provides only 1 management interface
for both the access network and the V5.x function.

Figure 3-3: Implementation of V5.x with PCON<X>

PHLC<X>, ISBUQ and ISBUT
UMUX1500
UMUX1500 LE
PHLC<X> V5.x
LTE
LTE PCON<X>
ISBUQ Integrated
ISDN-BA Transmission LTE PHLC<X>
UMUX1300/1100
Q
LE
ISDN-BA
ISBUQ
LTE Access Network
LECO3
UMUX 500
U5AP1
Q
AN
Location of the V5.x protocol processing
A PCON<X> unit can handle several V5.1 interfaces but only one V5.2
interface. It is however possible to implement several units processing
V5.1 and V5.2 interfaces in the same NE. To create the V5.x protocol a
PCON<X> is required at the V5 link access. The link access can be
implemented at the border between the access network and the LE or
remotely in a NE close to the user ports. You can implement the user
ports in the same NE as you implement the PCON<X> unit, or you can
forward all or a part of the user ports to remote NEs. In this case, the V5
traffic is processed and transported with the CAS type signalling via the
AN (or transport network) to the NE with the corresponding user ports. It
is possible to connect the user ports of one unit to several V5.x interfaces.
To optimise the benefit of traffic concentration provided with the V5.2
service, the V5.2 protocol is preferably processed as close as possible to
the user ports. With the V5.1 service, the location of protocol processing
is far less critical, since the transport of the V5.1 access links and the
processed traffic require the same bandwidth in the (access) network.

V5 traffic handling capacity The V5.x protocol processing units are available for the UMUX 1500
Access Systems only. Depending on the service, compatible units with
user ports are available for the UMUX 1500 and UMUX 1300/1100(E)
multiplexers:
Tab. 3-1: Summary units/NEs with V5.x functionality
Unit V5.1 V5.2 V5 protocol User ports UMUX system

Name conversion implementation
IF IF Links capabilities PSTN ISDN- 1500 1300

max. BA 1100(E)
PCONV 4 1 2 → MCAS 240 112 ü -
PCON2 10 1 8 → MCAS 480 224 ü -
PHLC1 ü ü - n.a. 60 - ü -
PHLC2 ü ü - n.a. 30 - ü -
ISBUQ ü ü - n.a. - 8 ü ü
n.a. not applicable

Please note that the traffic handling capacity of the PCON<X> units is not
cumulative for V5.2 PSTN and ISDN-BA user ports:
Tab. 3-2: Traffic handling capacity PCON<X> for V5.2
ISDN-BA UP
224
196 PCON2 capacity limit
168 PCONV capacity limit
140
112
84
56
28
PSTN UP
0 60 120 180 240 300 360 420 480
The capacity of the PCONV allows you to implement V5.x Access Systems
(AM) for up to 240 PSTN user ports (equivalents) in one subrack. Since the
PCONV unit additionally provides two 2 Mbit/s interfaces (G.703), you can
implement a V5.2 interface with a traffic concentration of 4:1 (240 PSTN
user ports) without additional interfaces for the V5 links (G.703 level).
The PCON2 units provide higher processing capacity than the PCONV
units, which allows you to implement a central V5.x protocol processing

Access System with the V5.x links provided via a high capacity transport
network such as SDH.
Figure 3-4: Example of V5.x provisioning with the UMUX
Feature
Services ADM
E1
POTS
V5.2 V5.2
LE U1500 ISDN-BA
ADM ADM NT-1
SDH AM S
E1
(CAS) Drop-off
Management ADM
Fibre or
Copper
U1500 CPE
AM Feature
UCST UMUX
UNEM 1100
Services
The capacity of a UMUX 1500 subrack for V5 functionalities is driven by

several parameters and is multi dimensional. The number of V5.x
interfaces with local protocol processing and local user port provisioning
depends on
• The type and number of V5 interfaces/links
This affects the capacity required on the PBUS cross connect.
• The type of selected PCON<X> unit
This affects the capacity required on the PBUS cross connect and the
number of slots required in the subrack.
• The type and number of V5 user ports
This affects the capacity required on the PBUS cross connect and on
the UBUS.
• The type of selected COBU<X> control unit
This defines the capacity provided on the PBUS cross connect and on
the UBUS.
• Whether the user ports are locally implemented (same subrack) or in
remote NEs
This affects the number of slots required in the subrack and the
capacity required on the UBUS.
• The number of free slots
The capacity on the PBUS cross connect needed by the V5 link access and
the provisioning of the processed V5 traffic for the user ports has to be
provided by the selected control unit. The PHAU figures that are provided
for each PBUS unit allow you to evaluate the PBUS bus usage for a
particular configuration. Rules and examples of corresponding subrack
implementations are provided in chapter 8 "Implementation and

Application Notes". The technical unit descriptions of the PCON<X> units

provide details on the traffic handling capacity of the protocol processing
units.
V5.x implementation in the Because of many existing national PSTN protocols and features as well as
operator's network the obligation for the network to be backward compatible with the
deployed subscriber’s equipment, V5 is not a generic interface. The types
of services which are deployed are not the same in all networks. The types
of functions supported and the architectural limitations are not the same
for all local switches.
Therefore national or operator specific specifications are required in
addition to the ETSI standards in order to define the interworking of
access networks with the national PSTN protocol and the V5 protocol
implementation in the local switch. PICS (Performance Implementation
Compliance Statement) specify such features and parameters for a
network.
Proper interworking between access network and local switch can only be
achieved when the same subset of V5-options/functions is supported
from both sides. Finally the interoperability between the V5.x interfaces of
the AN and the LE has to be verified for each type of LE and each
software load.
Therefore the V5 implementation in a network is specific to each network
and requires considerable resources for implementation and verification.
Please contact ATR for information on implementation and
performance of V5.x interfaces.
Custom parameter sets for To allow a fast and reliable commissioning of the UMUX 1500 and its V5.x
V5.x applications function in ANs with a high volume of UMUX 1500 Access Systems, it is
possible to create custom parameter sets for the V5.x function of the
UMUX.
The custom parameters are integrated as sets of custom parameters into a
corresponding database of the EM(S) software. Each set has its unique
identifier. You cannot subsequently modify individual parameters of the
set. The selection of the appropriate custom parameter set from the
database allows you to pre-set fast and reliably several hundreds of
parameters that are required for the operation of the V5.x interface.
The groups of V5.x and PSTN related parameters defined via custom
parameter sets are (UCST R5A):
• V5.x interface
− General V5 interface parameters
− V5 PSTN Information Element Status
− V5 PSTN Autonomous Actions
− V5 PSTN Cadence Ringing Signal Parameters
− V5 PSTN Pulse Signal Parameters
− V5 PSTN Hook Switch Time Parameters
− V5 PSTN Signal Recognition Time Parameters
− V5 PSTN Autonomous Signalling Sequences
• PSTN interfaces
− PHLC<X> PSTN Parameters
− PHLC<X> PSTN/Line Time Parameters
− PHLC<X> Line Test Parameters

The EM(S) uses the custom parameters to initialise the templates of the
corresponding units properly. Depending on the parameter the custom
set parameter may also influence the operation of other units such as
SUBL<X> and EXLA<X>.
Please contact ATR for information on the custom parameters
sets available.
Conference function The COBUV control unit provides conference functions for 64 kbit/s traffic
signals. These signals represent mostly digitised voice signals. The
signalling information accompanying the traffic signals is processed as
well.
You can assign up to 64 participants to up to 21 conference parties. It is
possible to configure the following parameters per participant of a
conference party:
• Name (16 characters max.)
• The attenuation for the traffic signal
− Fed to the conference (0 dB … 9 dB in steps of 3 dB)
− Received from the conference (0 dB, 3 dB)
• Noise suppression in 3 steps (5th, 9th and 16th step) or no noise

suppression.
To create the signalling that is provided to all participants of the
conference, the COBUV applies a logical AND to the bits of the signalling
pattern received from the participants of the conference.
Central diagnostic for traffic The COBUV and COBUX control units provide versatile diagnostic
signal channels functions for the analysis of the performance of data channels set up
between two access points. The access points are defined as the interfaces
to a test signal generator and a signal analyser. Both functions (the test
signal generator and analyser) are implemented on the control unit.
For more information on this function, refer to chapter 6 "Operation and
Maintenance".

Traffic units
PBUS units
LAWA4 The LAWA4 is a versatile network unit with bridging and routing functions,
a 10BaseT Ethernet LAN interface and an internal PBUS WAN interface.
Typically, one LAWA4 or several cascaded LAWA4 units of a UMUX 1500
collect traffic data via the PBUS or Ethernet interfaces. The LAWA4
processes the traffic in bridging or routing mode and passes it, via the
10baseT Ethernet interface or the PBUS WAN interface and the PBUS, to a
router or server.
The processing and transmission of traffic data is always symmetrical for
both directions.
With the UCST R5A the LAWA4 provides functions and features as
follows:
• Bridging, with the sub modes
− Transparent MAC bridge (standard mode)
All LANs connected via the LAWA4 Ethernet interface reside in a
common subnet.
− Port based virtual LAN, with up to seven independent bridge
instances
Each bridge instance is logically isolated from its neighbour bridge.
All ports connected to the same bridge instance reside in a
common subnet. The WAN interface provides a separate n x
64 kbit/s channel for each bridge instance.
• IP routing
− Static IP routes
You can configure up to 64 static routes.
− OSPF V2 dynamic IP routing
The Open Shortest Path First (OSPF) TCP/IP internet routing
protocol is classified as an Interior Gateway Protocol (IGP). This
means that it distributes routing information between routers
belonging to a single Autonomous System (AS). The OSPF protocol
is based on link-state or SPF technology.
OSPF quickly detects topological changes in the AS (such as router
interface failures) and calculates new loop-free routes after a
period of convergence. This period of convergence is short and
involves a minimum of routing traffic.
• Frame Relay
Frame Relay (FR) is an OSI layer 2 protocol (link layer) with unique
properties. The FR protocol provides for:
− FRAD (Frame Relay Assembler Disassembler)
− FR switching
− dynamic bandwidth control for each PVC (Private Virtual Circuit)
− guaranteed privacy for each PVC
− fast data transport
− economic use of available bandwidth
• PBUS WAN interface with PPP on layer 2
The LAWA4 provides a PBUS access for structured traffic signals with
up to 4 Mbit/s.

• Front panel 10BaseT LAN interface for Ethernet V2

• Unnumbered IP links on WAN interfaces
Unnumbered links are preferably used for point-to-point WAN links
between two routers.
• Fault management
• Status/Maintenance functions for the performance control and
statistics of the
− IP Routing Table
− Interface Statistics
− IP Common Statistics
− OSPF Statistics
• System characteristic LAWA4

− Unit type designation PBUS
− PBUS Highway Access per Unit (PHAU) 4
− Software download Yes
− Inventory Yes
− Memory for program code Non-volatile
− Unit width 1 slot
− Unit fitting slots of subrack 1 - 10, (12), 13 - 20
− Front panel connector none
(12): Slot 12 is not available in systems with protection of
the control unit.
For more information on the LAWA4 unit, refer to the unit description
[228] and the unit user guide [328].
LEMU6 The LEMU6 is a versatile network unit with bridging and routing functions
and 6 MSDSL line interfaces (to connect to MUSIC 100), a 10BaseT
Ethernet LAN interface and an internal PBUS WAN interface.
The LEMU6 works with the MUSIC 100 desktop unit. Typically, one
LEMU6 or several cascaded LEMU6 units of a UMUX 1500 collect data
traffic from the remote soho units. The LEMU6 processes the traffic in
bridging or routing mode and passes it on to the local router or server
that is connected to the 10BaseT Ethernet interface.
Alternatively, the LEMU6 passes the concentrated traffic from the MUSIC
100 units via the PBUS WAN interface and corresponding cross
connections to e.g. a LOMIF/LOMI4 unit and from there to the remote
server or router.
The processing and transmission of traffic data is always symmetrical for
both directions.
With the UCST R5A the LEMU6 provides functions and features as follows:
• Bridging, with the sub modes
− Transparent MAC bridge (standard mode)
All LANs connected the MUSIC 100 and all the LANs connected via
the LEMU6 Ethernet interface reside in a common subnet.
− Star bridge mode
This mode bridges the MUSIC 100 LANs to a central server or
router, but isolates the MUSIC 100 LANs from each other.

Traffic is transmitted between two "public" ports and between a

"public" and a "protected" port, but no traffic must be
transmitted between two "protected" ports.
− Port based virtual LAN, with up to seven independent bridge
instances
Each bridge instance is logically isolated from its neighbour's
bridge. All ports connected to the same bridge instance reside in a
common subnet. The WAN interface provides a separate n x 64
kbit/s channel for each bridge instance.
• IP routing
− Static IP routes
You can configure up to 64 static routes.
− OSPF V2 dynamic IP routing
The Open Shortest Path First (OSPF) TCP/IP internet routing
protocol is classified as an Interior Gateway Protocol (IGP). This
means that it distributes routing information between routers
belonging to a single Autonomous System (AS). The OSPF protocol
is based on link-state or SPF technology.
OSPF quickly detects topological changes in the AS (such as router
interface failures) and calculates new loop-free routes after a
period of convergence. This period of convergence is short and
involves a minimum of routing traffic.
• Frame Relay
Frame Relay (FR) is an OSI layer 2 protocol (link layer) with unique
properties. The FR protocol provides for:
− FRAD (Frame Relay Assembler Disassembler)
− FR switching
− dynamic bandwidth control for each PVC (Private Virtual Circuit)
− guaranteed privacy for each PVC
− fast data transport
− economic use of available bandwidth
• MSDSL WAN interface to MUSIC 100 with PPP or FR on layer 2
The Multi-rate Single line Digital Subscriber Line according to ETSI TS
101 135 is used to connect the DSL interfaces of the LEMU6 to the
remote MUSIC 100 units.
MSDSL supports 9 transmission rates from 144 kbit/s up to 2320
kbit/s, with a transmission range from a few km to over 10 km.
• PBUS WAN interface with PPP on layer 2
The LEMU6 provides a PBUS access for structured traffic signals with
up to 4 Mbit/s:
− 10BaseT Ethernet port used: 1 x 2 Mbit/s
n x 64 kbit/s or transparent
− 10BaseT Ethernet port not used: 2 x 2 Mbit/s
n x 64 kbit/s or transparent
• Front panel 10BaseT LAN interface for Ethernet V2
• Unnumbered IP links on WAN interfaces
Unnumbered links are preferably used for point-to-point WAN links
between two routers.

• DHCP relay configurable for MUSIC 100

The UCST configuration menu for DSL allows specification of up to
four DHCP servers for each MUSIC 100.
• IP managed bridge configurable for MUSIC 100
• Status/Maintenance functions for the performance control and
statistics of the
− DSL sections (noise margin etc.)
− IP Routing Table
− Interface Statistics
− IP Common Statistics
− OSPF Statistics
• Performance monitoring available for all DSL interfaces according to

ITU-T G.826 for the near and far end.
• System characteristic LEMU6
− Inventory Yes
− Front panel connector 3 x 1/4 size
1 RJ-45
the control unit.
• Interfaces for traffic signals and cables
The LEMU6 136 provides
− 6 MSDSL line interfaces (to connect tthe MUSIC 100)
The connection and cabling at the interface of the LEMU6 are
symmetrical.
− 10BaseT Ethernet LAN interface (RJ-45)
For more information on the LEMU6 unit, refer to the unit description
LEMQ6 The LEMQ6 provides the identical features as the LEMU6 but uses the
2B1Q line code instead of CAP.
LESA8 The LESA8 contains 8 DSL line interfaces and provides access to the PBUS
for Nx64 kbit/s, P12 and VC-12 (FUTURE OPTION) traffic signals.
The LESA8 provides a maximum of 4 two-pair DSL services, or 8 single-
pair DSL services, or a mixture of both. Each pair of DSL interfaces can be
connected to a single PBUS access circuit or to two individual ones. This
represents a capacity of 8 x 2 Mbit/s.
The LESA8 does not support remote powering for the far end DSL
equipment.

A regenerator using the CAP line code at a line rate of 1168 kbit/s is
available. It approximately doubles the transmission range. The indoor
version of the regenerator can be used with both the LESA8 and the
LESAP. The outdoor version has to be line powered. It can only be used
together with the LESAP.
With the UCST R5A the LESA8 provides functions and features as follows:
• DSL line interfaces
− Max. 8 single pair services
− Max. 4 two-pair services
− or a mixture of both
− Max. transmission capacity 8 x 2 Mbit/s
• Line codes
The LESA8 supports line codes as follows:
− CAP
− FUTURE OPTIONS
− 2B1Q
− PAM
• Compatible (remote) devices for the LESA8:
− LESA8 (1 and 2 pairs)
− LESAP (1 and 2 pairs)
− LECAR (1 and 2 pairs)
− CAP regenerator (LESA8: only locally powered)
− FUTURE OPTIONS:
− LECA2 (as NT with front access only)
− LECAF (as NT only)
− MUSIC 200
− MUSIC 100
• Traffic signal structures
− P12 and Nx64 kbit/s traffic signals
− VC-12 (FUTURE OPTION) traffic signals
The LESA8 supports the standard UMUX fault management and
additionally provides an alarm relay output for urgent LECAR alarms.
• Status/Maintenance functions
− For each subunit the following status information can be retrieved:
− DSL noise margin near end
− DSL noise margin far end for desktop units
− Line power (if applicable)
− Transceiver state
− NT state (if applicable): hardware, software and client interface
− Service channel state
− Regenerator presence
− The following loops on the 2 Mbit/s level are available for testing of
the signal path:
− Local loop in LESA8/P towards the backplane
− Local loop in LESA8/P towards the DSL link
− Remote loop towards the DSL link (with LECAR only)
− Local loop in regenerator (if present) towards the LESA8/P
operating as LT

• Performance monitoring according to ITU-T G.826 for the DSL link

offers data for the path as well as for the individual DSL lines (near and
far end).
• System characteristic LESA8 implementation
− Inventory Yes
− Front panel connector 1 full size
the control unit.
− The LESA8 provides 8 DSL line interfaces
− The connection and cabling at the interface of the LESA8 are
symmetrical (8 open ended, twisted pairs).
For more information on the LESA8 unit, refer to the unit description
LESAP The LESAP contains 8 DSL line interfaces and provides access to the PBUS
for Nx64 kbit/s, P12 and VC-12 (FUTURE OPTION) traffic signals.
The LESAP offers a maximum of 4 two-pair DSL services, or 4 single-pair
DSL services, or a mixture of both. This represents a capacity of
4 x 2 Mbit/s.
In addition, the LESAP provides line power to one two-pair interface
without the need of any external equipment.
A regenerator using the CAP line code at a line rate of 1168 kbit/s is
available. It approximately doubles the transmission range. The indoor
version of the regenerator can be used with both the LESA8 and the
LESAP. The outdoor version has to be line powered. It can only be used
together with the LESAP.
With the UCST R5A the LESAP provides functions and features as follows:
• DSL line interfaces
− Max. 4 single pair services
− Max. 4 two-pair services
− or a mixture of both
− Max. transmission capacity 4 x 2 Mbit/s
• Line power
One DSL interface provides line power for the remote powering of a
remote device (e.g. regenerator).
The other features of the LESAP are identical with the LESA8 features. For
information, refer to the LESA8 short description above.

• System characteristic LESAP implementation

− Inventory Yes
the control unit.
− The LESAP provides 8 DSL line interfaces
− The connection and cabling at the interface of the LESAP are
symmetrical (8 open ended, twisted pairs). The LESAP uses the
same cable as the LESA8.
For more information on the LESAP unit, refer to the unit description
LOMIF 8 x 2 Mbit/s interface The LOMIF unit features 8 electrical interfaces according to ITU-T G.703
unit for 2 Mbit/s traffic signals and provides the corresponding cross connect
capacity on the PBUS. The interfaces are available according to the
symmetrical 120 Ohm and the asymmetrical 75 Ohm standard.
The LOMIF supports features and functions as follows:
• Each of the 8 2 Mbit/s subunits of the LOMIF can process signals on
the 2 Mbit/s traffic signal layer
− Structured signals in one of 3 modes of operation
− Transparent (time slot 0 not monitored or regenerated)
− Monitored (time slot 0 monitored only)
− Terminated (time slot 0 monitored and regenerated)
− Clock master (re-timing of the signal)
The LOMIF allows the processing of structured signals with and
without signalling.
2 Mbit/s signals structured according to ITU-T G.704 can be
− Terminated for demultiplexing into 31 time slots, 64 kbit/s each
(or 30 time slots and a time slot for CAS). The terminated signal
and its time slots can be used for 1/0 cross connections.
− Monitored. In this mode the contents of the TS0 is read only. It
is not possible to write a CRC4 or Sa bits to the signal leaving
the LOMIF.
− Transparent
− Unstructured signals transparently
− Transparent (signal without structure)
You can configure the operation parameters for each of the 8
interfaces independently.
• Cross connection for
− n x 64kbit/s traffic signals (n = 1 … 31) for terminated 2Mbit/s signals.
− plesiochronous (structured or unstructured) 2Mbit/s signals

The 2 Mbit/s signals can be forwarded for transparent 1/1 cross

connection, independently of their structure and contents.
• CRC 4 operation for structured 2 Mbit/s signals.
With the UCST R5A and the ESW LOMIF_R3.B01, the LOMIF 140
provides the CRC-4 MFA function which allows you to control and
trigger the multi-frame alignment.
• Use of the five Sa spare bits in the TS0 of structured 2 Mbit/s signals:
Sa Mode Description
SSI Synchronisation Status Indication in Sa5 bit
SSM G.704 Synchronisation Status Message in any Sa bit
according to ITU-T G.704
ECC PDH ECC transmitted in bits Sa5-Sa8 with
SSM/TTI 16 kbit/s
SSM and Trail Trace Identifier with proprietary
transmission in Sa4 bit
V5.x app. Fixed Sa bits for V5.1; Sa7 bit used for link
identification control with V5.2
NT1-U PRA functional blocks.
LT-U Loop back indication to ET in Sa5 bit, commands
and indications in Sa6 bit according to ITU-T G.962
fixed Each Sa bit can be set individually to 0 or 1
• Setting of the three TS16 spare bits

• Implementation of PRA direct access with the NT1 and LT functional
blocks integrated in the UMUX network.
The implementation of each PRA functional groups (NT1 and LT) in
the UMUX requires two function blocks each based on a subunit with
PBUS access. A functional group, NT1 or LT, thus requires two UMUX
1500 2Mbit/s (sub)units:
− The NT1 functional group consists of the 2 function blocks:
− NT1-T which provides the reference point T for the UMUX
network.
− NT1-U which connects the NT1 to the transmission (network)
side.
− The LT functional group consists of the 2 function blocks:
− LT-V3 which provides the reference point V3 for the UMUX
network.
− LT-U which connects the LT to the transmission (network) side.
The LOMIF (LOMIF 140 only) provides all four functional blocks.
• The Clock Master mode of the LOMIF (LOMIF 140 only)
allows you to synchronise any 2 Mbit/s traffic signal independently on
its structure to the host NE timing source even if the signal is not
terminated in the NE.

• Synchronisation
− Provisioning of timing signals for the PETS and SETS timing blocks.
If the signals contain SSM or SSI information, this information is
forwarded together with the timing signal as a parameter for
timing source selection.
− Routing tables for SSM or SSI information. Depending on the
selected timing source, the SSM/SSI information indicates whether
the data signal leaving the LOMIF can be used for synchronisation
purposes or not.
This feature prevents timing loops (SSI/SSM) in the UMUX network
when the UMUXs switch over to a backup synchronisation source.
• Status/Maintenance functions
• Performance monitoring for structured 2 Mbit/s traffic signals
according to ITU-T G.826. The performance of unstructured signals is
monitored in the same way.
• System characteristic LOMIF implementation
− Inventory Yes
the control unit.
− The LOMIF provides 8 electrical interfaces according to ITU-T G.703
for
− 120 Ω symmetrical
− 75 Ω asymmetrical
by selecting the corresponding signal pins on the front panel connector.
− The connection and cabling at the interface of the LOMIF are
symmetrical for both types of signals. If you need asymmetrical
signals, the conversion to asymmetric cables has to be provided by
an external patch panel nearby.
The LOMIF is available with 2 licences for ESW:
• Standard functionalities (LOMIF 101)
• Standard functionalities plus (LOMIF 140)
− Performance monitoring
− PRA functionalities
− Clock master mode
− CRC-4 Multi-Frame Alignment
For more information on the LOMIF unit, refer to the unit description
LOMI4 The LOMI4 unit features 4 electrical interfaces according to ITU-T G.703
for 2 Mbit/s traffic signals and provides the corresponding cross connect

capacity on the PBUS. The interfaces are available according to the

symmetrical 120 Ohm and the asymmetrical 75 Ohm standard.
The LOMI4 supports features and functions as follows:
• The LOMI4 provides for its 4 interfaces the same features and
functions as the LOMIF (140) unit.
This includes
− Performance monitoring
− PRA functionalities
− Clock master mode
− CRC-4 Multi-Frame Alignment
• System characteristic LOMI4 implementation

− Inventory Yes
the control unit.
For more information on the LOMI4 unit, refer to the unit description
PCON<X>
General specifications The PCONV and PCON2 units process the protocols required by the various
standardised signalling systems provided in the access network. The PCONV
and PCON2 are mainly used to create the V5.1 or V5.2 protocols for access
networks and user ports implemented with UMUX Access Systems.
The PCON<X> units provide the following main services and features:
• V5.2 protocol processing
Protocol processing at the V5.2 access point in order to provide the
V5.2 interface and user ports for the AN (according to ETS 300 347-1
and ETS 300 324-1).
Synoptic overview of V5.2 features PCON<X>:
Features V5.2 PCONV PCON2
Max. number of User Ports 1) 2)

– PSTN 240 480
– ISDN-BA 112 224
– mixed services of PSTN and ISDN
V5.2 IF per unit 1 1
V5.2 links per V 5.2 IF 2 8
2 Mbit/s (G.703) IF per unit 2 -
3)
BHCA 3000 E/h 3000 E/h

1)
The maximum number of user ports that you can implement per
subrack
− is given by the capacity of the subrack
- Maximum of 240 PSTN user ports per subrack
- Maximum of 112 ISDN-BA user ports per subrack
− depends on the selected control unit and services implemented
– COBUV 137: full system capacity available
– COBUX 145: full system capacity available
– COBUX 146: limited PBUS access
– COBUQ 144: limited PBUS and UBUS
− access
– COBUL 215: Not released for V5 applications.
2)
The user port handling capacity of the PCON<X> units is decreased
if p- and f-data are packed into the IC channels.
3)
Considering a busy hour average occupancy per UNI channel of 0.2
E and a corresponding holding time (per call) of 100 s, the PCONV
is able to handle a total number of Busy Hour Call Attempts
(BHCA) of 1728 E/h.
• V5.1 protocol processing
Protocol processing at the V5.1 access point in order to provide the
V5.1 interface and user ports for the AN (according to ETS 300 347-1
and ETS 300 324-1).
Synoptic overview of V5.1 features PCON<X>:
Features V5.1 PCONV PCON2
Max. number of User Ports 1) 2)

– PSTN 240 480
– ISDN-BA 112 224
– mixed services of PSTN and ISDN
V5.1 IF/unit 4 10
2 Mbit/s (G.703) IF/unit 2 -
3)
BHCA 3000 E/h 3000 E/h
1)
The maximum number of user ports that you can implement per
subrack
− is given by the capacity of the subrack
- Maximum of 240 PSTN user ports per subrack
– Maximum of 112 ISDN-BA user ports per subrack
− depends on the selected control unit and services implemented
– COBUV 137: full system capacity available
– COBUX 145: full system capacity available
– COBUX 146: limited PBUS access
– COBUQ 144: limited PBUS and UBUS
− access
– COBUL 215: Not released for V5 applications
2)
The user port handling capacity of the PCON<X> units is decreased
if p- and f-data are packed into the IC channels.
3)
BHCA = Busy Hour Call Attempts.

• The units can process V5.1 or V5.2 protocols

• V5.x protocol processing and user ports are completely separated.
• Processing of p- and f-data of ISDN in the IC-channels.
• Support of the digital leased line mode ("Standard Festverbindungs
Modus").
• It is possible to implement the user ports of a V5.x interface in multiple NEs.
• Operation of multiple PCON<X> systems in 1 UMUX 1500 NE is possible.
• Supports link connections via local E1 interfaces or remote via
integrated HDSL / SDSL or optical fibre system.
PCONV The general specification of the V5 protocol processing of the PCONV unit
and the corresponding capacities are as specified in the previous
paragraphs.
The PCONV additionally provides:
• Implementation of two 2048 kbit/s interfaces according to ITU-T
G.703 in order to provide the access to the physical 2 Mbit/s link(s) of
the V5.x interface directly, avoiding the use of extra traffic units. This
feature is mainly used for V5.2 service provisioning.
The two 2 Mbit/s traffic interfaces on the unit provide the same
features and parameters as the traffic interfaces of the LOMIF. The
interfaces can be used for other purposes than V5.x link access and are
completely independent of the V5.x protocol function implemented on
the unit.
• System characteristic PCONV
− Inventory Yes
− Memory for program code Volatile
the control unit.
− The PCONV provides 2 electrical interfaces according to ITU-T
G.703 for
by selecting the corresponding signal pins on the front panel
connector.
− The connection and cabling at the interface of the PCONV are
an external patch panel nearby.
For more information on the PCONV unit, refer to the unit description

PCON2 The general specification of the V5 protocol processing of the PCON2 unit
and the corresponding capacities are as specified in the previous
paragraphs.
The PCON2 additionally provides:
• In addition to the specified V5 processing the PCON2 unit provides
signalling conversion to MCAS signalling for the processed V5 traffic.
This latter feature is not available with the PCONV unit. The PCON2
allows the processed V5 traffic to access the PSTN user ports as
standard V5 user ports or user ports with MCAS signalling. The MCAS
modes supported are:
− DEL (Direct Exchange Line)
− Loop Calling PBX
− Earth Calling PBX
Conversion has limited conformance to V5 standards (e.g.
blocking, resource unavailable messages are not supported) and
are only supported with the UK Customer Parameter Sets.
• System characteristic PCON2

− Inventory Yes
− Front panel connector None
the control unit.
The PCON2 has no external interfaces for link access.
For more information on the PCON2 unit, refer to the unit description
PHLC1 subscriber line interface The PHLC1 unit provides subscriber line interfaces for PSTN services. The
unit PHLC1 has been specially designed for V5.x and channel bank
applications. The PHLC1 features 60 a/b-wire subscriber line interfaces on
a triple width unit. The operation and subscriber loop parameters of the
PSTN interfaces are software controlled and can be programmed via the
EM. Most of the parameters apply for all the subscriber line interfaces. It is
possible to program the loop length and cyclic subscriber line test
individually per user port.
The PHLC1 can be operated in the following modes (applies for all
subscriber line interfaces):
• V5 Mode:
The PHLC1 provides PSTN user ports for V5.x interfaces in the AN. The
operation of the PHLC1 in the V5 mode requires a PCONV or a PCON2
unit in the AN to create the V5.x protocol. The creation of the V5.x
protocol with a PCON<X> can be performed in the same NE or in any
other NE (UMUX 1500) of the AN (refer to figure above). It is not
possible to implement a PHLC1 in the UMUX 1300/1100(E).

• MCAS direct line:

The PHLC1 can be connected (via 2 Mbit/s links) to LEs supporting the
Mercury CAS protocol. It is not possible to alter the coding of the
signalling bits.
• Carrier Adapter Mode:
The PHLC1 can be connected (via 2 Mbit/s links) to LEs which support
the CAS protocol as specified for the Carrier Adapter mode. It is not
possible to alter the coding of the signalling bits.
• Phone-Exchange Mode:
The subscriber line interfaces of the PHLC1 are connected via the AN
to the exchange line interfaces of an EXLA<X> implemented in UMUX
Access Systems (channel banks). Since the signalling bits can be
adapted, it is possible to connect the PHLC1 to similar third party
equipment.
The PHLC1 supports the following functions and parameters:
• Selection of operation mode (V5, MCAS, Carrier Adapter, Phone-
Exchange)
• Programmable ringing frequency.
The ringing signal is injected either over
− b-wire
− b-wire with earth back
− a-wire (On request only)
Each type of ringing signal injection is implemented on a specific
hardware version of the PHLC1.
• Programmable voice impedance (pre-set values).
PHLC1 provides impedances for A- and µ-law.
• Programmable voice levels (input, output) for
− Long loops
− Short loops
• Pulse and tone dialling.

• Programmable loop current.
• Programmable earth key, flash impulse and metering pulses (12 or 16
kHz).
• Programmable level of metering pulses.
• Indication of busy lines.
• Requests for the shutdown of subscriber line interfaces (deferred
locking) to the V5 LE. This maintenance function is activated from the
unit front panel or via the EM(S).
• Line lock requests to the V5 LE. This maintenance function is activated
via the EM(S).
• Intelligent management of the heat dissipation for user ports.
• 2 user ports can be operated as spare interfaces.
• Manual or automatic (cyclic) subscriber line test for
− Isolation
− Noise
− Capacity
• Cyclic checks programmable for each subscriber line circuit for foreign
voltages, for short circuits to battery and ground.

• System characteristic PHLC1 implementation

− Inventory Yes
− Unit width 3 slots
− Front panel connectors 2 full size
the control unit.
The signal cable for the subscriber line interfaces normally features no
shield. Instead a toroidal core ferrite is installed close to the connector
of the unit interface. Each of the 2 signal cables connects 30
subscriber line interfaces.
For more information on the unit PHLC1 and operation of the unit, refer
to the unit description [212] and the unit user guide [312].
unit PHLC2 provides the same modes of operation, features and functions as
PHLC1 but features only 30 a/b-wire subscriber line interfaces on a double
width unit.
• System characteristic PHLC2
− Inventory Yes
the control unit.
of the unit interface. The signal cable connects all 30 subscriber line
interfaces.

unit PHLC3 provides the same modes of operation, features and functions as
PHLC1 but features only 10 a/b-wire subscriber line interfaces on a double
width unit.
• System characteristic PHLC3
− Inventory Yes
the control unit.
of the unit interface. The signal cable connects all 10 subscriber line
interfaces.
UBUS units
UBUS units legacy Because of the successful history of the UMUX Access System, a number
of units with various transmission, data and voice interfaces are available.
This includes (list not complete) the:
• EXLA<X> units with PSTN exchange line IFs.
• EXBAT units with ISDN BA (4B3T) exchange line IFs.
• EXLIC units with ISDN BA (2B1Q) exchange line IFs.
• GECOD units with 64 kbit/s G.703 data IFs.
• LECA2 units with CAP transmission IFs and the corresponding remote
desktop units.
• LE2Q2 units with 2B1Q transmission IFs and the corresponding remote
desktop units.
• MEGIF unit with G.703 electrical 2 Mbit/s IFs.
• NEM<XY> units with 2/4-wire voice grade analogue IFs.
• SIFOX units with 64 kbit/s X.24/V.11 IFs.
• SUBAT unit with ISDN BA (4B3T) IFs for the NT1.
• SUBL<X> and SUBUK units with PSTN subscriber line IFs.
• SULIC units for the 2B1Q based data transmission to the
corresponding remote desktop unit.
• SULIS unit with ISDN BA (2B1Q) IFs for the NT1.
• TUN<XY> units with optical and electrical 8 Mbit/s transmission IFs.

• UNIDA units with various data IFs and features for data rates up to 2
Mbit/s.
With some exceptions, it is possible to operate most of the existing UBUS
units with the UMUX 1500 and UMUX 1200. For information on the
availability, refer to the chapter 9 "System and Ordering Information".
Please note that the UBUS units terminate their traffic signals. For more
information on functions implemented with UBUS units and operation of
UBUS units, refer to the relevant descriptions and user guides.
Refer to the paragraphs below for new UBUS based units that have been
introduced with the UMUX 1500.
ISBUQ user port units for The ISBUQ unit provides ISDN-BA user ports for V5.x interfaces in the AN
ISDN-BA and features 8 BA U-interfaces. The operation of the ISBUQ requires a
PCONV or PCON2 unit in the AN to create the V5.x protocol. The creation
of the V5.x protocol with the PCON<X> can be performed in the same NE
or in any other NE (UMUX 1500) of the AN. The ISBUQ can be
implemented in a UMUX 1300/1100(E) as well.
The ISBUQ supports the following functions and parameters:
• ISDN BA user ports for V5.1 and V5.2 services. Operates with the
PCONV and PCON2 protocol processing units.
• U-interface with 2B1Q line code.
• Remote powering for the NT-1.
• Remote power feeding on U-interface is individually configurable for
all eight interfaces.
• Common IC-channel for the D-channels of all interfaces.
• Configuration of p- and f-data in the IC-channel. Support of p- and f-
data related services.
• The p- and f-data can be assigned to up to 3 separate c-paths
• Permanent activation of the DS (Digital Section)
• Performance monitoring for ISDN B channels
• Performance grading
• Status inquiry and diagnostics via EM.
• Blocking requests (lock, shutdown, unlock) implemented
• Test of activation/deactivation state of subscriber lines
• Diagnostic loops (local ISBUQ, up to 6 IEs, NT-1) implemented
• Performance tests loop back 1
• Quick loop back test
• System characteristic ISBUQ implementation
− Unit type designation UBUS
− PBUS Highway Access per Unit (PHAU) not applicable
− Inventory Yes
− Memory for unit program code Non-volatile
the control unit.

For more information on the ISBUQ unit and operation of the unit, refer
ISBUT user port units for ISDN- The ISBUT unit provides ISDN-BA user ports for V5.x interfaces in the AN
BA and features 8 BA U-interfaces. The operation of the ISBUT requires a
PCONV or PCON2 unit in the AN to create the V5.x protocol.
The ISBUT supports functions and parameters as follows:
• The ISBUT supports the same functions as the ISBUQ but uses the
4B3T line code.
• Additionally, the ISBUT supports the mode for digital leased lines
("Standard Festverbindungs Modus").
For a short description of the common features and the system
characteristics, refer to the paragraphs on the ISBUQ.
For more information on the ISBUT and operation of the unit, refer to the
unit description [225] and the unit user guide [325].
SBUS units
SYNAC The SYNAC unit terminates VC-12 from the SBUS and provides the
corresponding P12 (2 Mbit/s (n x 64kbit/s)) access to the PBUS. The unit
terminates up to 8 VC-12. You can implement several SYNAC units in
order to terminate more SDH traffic in the NE.
The SYNAC supports features and functions as follows:
• Asynchronous mapping/de-mapping of 2 Mbit/s to/from VC-12.
• Each of the 8 P12 (2 Mbit/s) subunits of the SYNAC can process signals
on the P12 traffic signal layer
− Structured signals in one of 3 modes of operation
− Transparent (time slot 0 not monitored or regenerated)
− Monitored (time slot 0 monitored only)
− Terminated (time slot 0 monitored and regenerated)
The SYNAC allows the processing of structured signals with and
without signalling.
2 Mbit/s signals structured according to ITU-T G.704 can be
− Terminated for de multiplexing into 31 time slots, 64 kbit/s each
(or 30 time slots and a time slot for CAS). The terminated signal
and its time slots can be used for 1/0 cross connections.
− Monitored. In this mode the contents of the TS0 is read only. It
is not possible to write a CRC4 or Sa bits to the signal leaving
the LOMIF.
− Transparent.
− Unstructured signals transparently
− Transparent (signal without structure)
You can configure the operation parameters for each of the 8
interfaces independently.

• Cross connection for

− n x 64kbit/s traffic signals (N = 1 … 31) for terminated 2Mbit/s
signals.
− plesiochronous (structured or unstructured) 2Mbit/s signals
The 2 Mbit/s signals can be forwarded for transparent 1/1 cross

connection, independently of their structure and contents.
• CRC 4 operation for structured 2 Mbit/s signals.
• Use of the five Sa spare bits in the TS0 of framed signals:
Sa Mode Description
SSI Synchronisation Status Indication in Sa5 bit

SSM G.704 Synchronisation Status Message in any Sa bit according to
ITU-T G.704
ECC PDH ECC transmitted in bits Sa5-Sa8 with
SSM/TTI 16 kbit/s
SSM and Trail Trace Identifier with proprietary
transmission in Sa4 bit
V5.x app. Fixed Sa bits for V5.1; Sa7 bit used for link identification
control with V5.2
NT1-U PRA functional blocks.
LT-U Loop back indication to ET in Sa5 bit, commands and
indications in Sa6 bit according to ITU-T G.962
fixed Each Sa bit can be set individually to 0 or 1
• Setting of the three TS16 spare bits

• Implementation of PRA direct access with the NT1 and LT functional
blocks integrated in the UMUX network.
The implementation of each PRA functional groups (NT1 and LT) in
the UMUX requires two function blocks each based on a subunit with
PBUS access. A functional group, NT1 or LT, thus requires two
UMUX 1500 2Mbit/s (sub)units:
− The NT1 functional group consists of the 2 function blocks:
− NT1-T which provides the reference point T for the UMUX
network.
− NT1-U which connects the NT1 to the transmission (network)
side.
− The LT functional group consists of the 2 function blocks:
− LT-V3 which provides the reference point V3 for the UMUX
network.
− LT-U which connects the LT to the transmission (network) side.
The SYNAC 163 provides the functional blocks NT1-U and LT-U.
• Clock Master mode
allows you to synchronise any 2 Mbit/s traffic signal independently on
its structure to the host NE timing source even if the signal is not
terminated in the NE.
• Synchronisation


the data signal leaving the SYNAC can be used for synchronisation
purposes or not.
• TTI for VC12 (J2 byte): 16 byte format according to G.707.
• VC12 signal label (bits 5-7 of V5 byte). This indicates the composition
of the signal. Transmitted (HW set) and expected values are ‘2’
corresponding to the TUG structure.
• VC-12 Linear 1+1 Trail Protection (LTP) switching (non-revertive)
• Performance Monitoring for the
− VC-12 and P12 traffic layers
− Near and far end performance monitoring:
• Fault management for

− Board, P12 and VC-12 traffic layers
− Excessive and degraded error rates (VC-12 layer). It is possible to
configure the
− Thresholds for excessive and degraded error rates. Crossing of a
threshold creates a Threshold Crossing Notification (TCN).
− Distribution function of errors (Poisson, Bursts)
• System characteristic SYNAC
− Unit type designation SBUS
− Inventory Yes
− Unit fitting slots of subrack 2 - 9, 15 - 20
− Front panel connectors none
For more information on the SYNAC and operation of the unit, refer to
the unit description [222] and the unit user guide [322].
SYNAM The SYNAM unit terminates VC-12 from the SBUS and provides local
2 Mbit/s interfaces for the corresponding E12 signals. The SYNAM has no
access to the PBUS and thus allows no cross connection. The unit
terminates up to 8 VC-12. You can implement several SYNAM units in
order to terminate more SDH traffic in the NE.
The SYNAM supports features and functions as follows:
• Asynchronous mapping/de-mapping of E12 (2 Mbit/s) to/from VC-12.
• 8 E12 (2 Mbit/s) subunits with local interfaces according to
ITU-T G.703.

The SYNAC supports the symmetrical 120 Ω and the asymmetrical 75

Ω standard.
• Synchronisation
the data signal leaving the SYNAC can be used for synchronisation
purposes or not.
• TTI for VC-12 (J2 byte): 16 byte format according to G.707.
• VC-12 signal label (bits 5-7 of V5 byte). This indicates the composition
of the signal. Transmitted (HW set) and expected values are ‘2’
corresponding to the TUG structure.
• VC-12 Linear 1+1 Trail Protection (LTP) switching (non-revertive)
• Performance Monitoring for the
− VC-12 and E12 (2 Mbit/s) traffic layers
− Near and far end performance monitoring:
• Fault management for

− Board, E12 and VC-12 traffic layers
− Excessive and degraded error rates (VC-12 layer). It is possible to
configure the
• System characteristic SYNAM
− Inventory Yes
− Unit fitting slots of subrack 2 - 9, 15 - 20
− Front panel connectors 1 full size
− The SYNAM provides electrical interfaces according to ITU-T G.703
for
by selecting the corresponding signal pins on the front panel
connector.
− The connection and cabling at the interface of the SYNAM are
an external patch panel nearby. The SYNAM uses the same
cables as the LOMIF.

For more information on the SYNAM and operation of the unit, refer to
SYNIC The SYNIC unit provides 1 electrical STM-1 transmission interface for
SDH traffic signals. The SYNIC unit allows you to implement the TM on
one unit and the ADM functionality on two units.
The SYNIC terminates the STM-1 frame and provides the VC-4 container.
You can configure the structure of the VC-4 container for VC-12 and VC-
3. A mixture of both structures is possible. The VC-12 traffic provided by
the SYNIC unit is connected via the SBUS and the SYNAC unit to the PBUS
for the cross connection and the provisioning of services. With the
SYNAM unit is possible to terminate the VC-12 signals from the SBUS and
provide corresponding E-12 signals on local G.703 interfaces.
The VC-12 and VC-3 traffic can be directly routed to a neighbouring STM-
1 interface as well.
The SYNIC extracts the D, E and F bytes of the SDH section overhead and
provides corresponding interfaces on the UBUS. You can use the channels
provided by the overhead bytes for the SDH ECC, EOW and other purposes.
The following features and functions are supported:
• STM-1 aggregate interfaces for the electrical signal transmission
according to ITU-T G.703.
• Termination of STM-1 traffic signals.
− Through connection (aggregate to aggregate) of STM-1 signals for
VC-12 and VC-3
− Drop and insert functionality in the NE for VC-12.
• Supports network topologies for ring, linear or meshed networks.

• Payload tributaries are VC-3 and VC-12 traffic signals.
• Processing of the Regenerator Section, the Multiplex Section and the
VC-4 path overhead.
• Provisioning of the D, E and F Bytes of the SOH for cross connection (n
x 64 kbit/s) via UBUS.
− SDH ECC: Bytes D1 … D12
− EOW: Bytes E1 and E2
− User Channel: Byte F1
• SETS SDH synchronisation functionality (SETS) according to ITU-T

G.783 or EN 300 417-6-1.
• SETS equipment protection.
The SETS circuits of a SYNIC and a second SYNIC/SYNIF unit allow 1+1
equipment protection for the NE SETS function.
• Processing of SSM according to G.707.
• Timing sources
− STM-1 aggregate signals
− External 2 MHz clock
− 2 Mbit/s traffic signals
− Internal clock (SEC)
• VC-4 path trace (31 bytes) for the transmission of the access point
identifier.

• Regenerator Section Trace (J0 byte) configurable as 1 (values ‘01’ or

‘81’ meaning ‘trace unspecific’) or 16-byte format according to G.707
for transmission of the Access Point Identifier
• VC-4 Signal Label (C2 byte). This indicates the composition of the
signal. Transmitted and expected values are ‘2’ corresponding to the
TUG structure.
• MSP (Multiplex Section Protection) with the SYNIC is a FUTURE
OPTION.
• Performance monitoring for the
− Electrical Section (ET, OOF)
− RS, MS and AU-4/VC-4 layers:
• Fault management for the

− Board, ES, RS, MS, AU-4/VC-4, TUG-3/TU-3 and TU-12 layers
− Fault management for excessive and degraded error rates (MS and
AU-4/VC-4 layer of the STM-1 signal). It is possible to configure the
• Remote Error Indication for MS (MS-REI: M1 byte). This byte indicates
the number of BIP-24 (B2 byte) errors.
• System characteristic SYNIC
− Inventory Yes
− Unit fitting slots of subrack 2 (4), 3 (5), 6 (8), 7 (9),
15 (17), 16 (18), 19 (20)
− Front panel connectors 2 x series 1.6/5.6
75 Ω
You can operate simultaneously both SBUS sectors (sector A or sector B)
of the UMUX 1500.
With the UCST R5A some limitations apply:
• SETS protection switching is only possible between the SYNIC and
SYNIC/SYNIF units.
• The SYNIF_R2A.50 ESW does not allow you to operate the SYNIC unit
in the slot 8 (no UBUS access). This limitation is obsolete with the
SYNIF_R3xx ESW.
For more information on the SYNIC and operation of the unit, refer to the
SYNIF The SYNIF unit provides 1 optical STM-1 transmission interface for SDH
traffic signals. There are hardware versions of the unit with interfaces for
short haul and long haul applications available. The SYNIF unit allows you
to implement the TM on one unit and the ADM functionality on two
units.

The SYNIF terminates the STM-1 frame and provides the VC-4 container.
the SYNIF unit is connected via the SBUS and the SYNAC unit to the PBUS
for the cross connection and the provisioning of services. With the
provide corresponding E-12 signals on local G.703 interfaces.
1 interface as well.
The SYNIF extracts the D, E and F bytes of the SDH section overhead and
provided by the overhead bytes for the SDH ECC, EOW and other
purposes.
• STM-1 aggregate interfaces for optical transmission. There are 3
versions available:
− 1300 nm short and long haul (S-1.1 and L-1.1)
− 1550 nm long haul (L-1.2)
All applications are according to ITU-T G.957.

VC-12 and VC-3

• Processing of the Regenerator Section, the Multiplex Section and the
VC-4 path overhead.

G.783 or EN 300 417-6-1.
• SETS equipment protection.
The SETS circuits of a SYNIF and a second SYNIF/SYNIC unit allow 1+1
equipment protection for the NE SETS function.
• Timing sources
identifier.


TUG structure.
• MSP (Multiplex Section Protection) with the SYNIF is a FUTURE
OPTION.
• Automatic laser shutdown and restart configurable.
− Optical Section (ET, OOF)

− Board, OS, RS, MS, AU-4/VC-4, TUG-3/TU-3 and TU-12 layers
• System characteristic SYNIF
− Inventory Yes
− Unit fitting slots of subrack 2 (4), 3 (5), 6 (8), 7 (9),
15 (17), 16 (18), 19 (20)
− Front panel connectors 2 x E-2000
(type LSH-HRL)
With the UCST R4E some limitations apply:
• You can only operate 1 sector of the SBUS at a time (sector A or sector B).
• SETS protection switching is only possible between the SYNIF and
SYNIF/SYNIC units.
• The SYNIF_R2A.50 ESW does not allow you to operate the SYNIF unit
in the slot 8 (no UBUS access).
For more information on the SYNIF and operation of the unit, refer to the
SYNIO The SYNIO unit provides 2 optical STM-1 transmission interfaces for SDH
traffic signals. There are hardware versions of the unit with interfaces for
short haul and long haul applications available. The SYNIO unit allows you
to implement ADM and TM functionality on one unit.
The SYNIO terminates the STM-1 frame and provides the VC-4 container.

the SYNIO unit is connected via the SBUS and the SYNAC unit to the
PBUS for the cross connection and the provisioning of services. With the
provide corresponding E12 signals on local G.703 interfaces.
1 interface as well. This interface can be the second interface on the unit
or the STM-1 interface of a second SYNIO unit (FUTURE OPTION).
The SYNIO extracts the D, E and F bytes of the SDH section overhead and
provided by the overhead bytes for the SDH ECC, EOW and other
purposes.
• STM-1 aggregate interfaces for optical transmission. There are 3
versions available:
− 1300 nm short and long haul (S-1.1 and L-1.1)
− 1550 nm long haul (L-1.2)
All applications are according to ITU-T G.957.

VC-12 and VC-3

• Processing of the Regenerator Section, the Multiplexer Section and the
VC-4 path overhead.

G.783 or EN 300 417-6-1.
• SETS equipment protection with the SYNIO is a FUTURE OPTION.
• Timing sources
identifier.

TUG structure.
• MSP (Multiplex Section Protection) switching.
The SYNIO supports 1+1 MSP according to ETS 300 417-3-1 and ITU-T
G.783 for the protection modes
− 1+1 unidirectional protection mode
− 1+1 bi-directional protection mode
The SYNIO 1+1 protection mode is compatible with the 1:1 protection
mode of other units.
• Automatic laser shutdown and restart configurable.
− Electrical Section (ET, OOF)
− MSP layer (PSC) if MSP is configured

− Board, OS, RS, MS, AU-4/VC-4, TUG-3/TU-3 and TU-12 layers
• System characteristic SYNIO
− Inventory Yes
− Unit fitting slots of subrack 2, 3, 6, 7, 15, 16 and 19
− Front panel connectors 4 x E-2000
(type LSH-HRL)
You can simultaneously operate both SBUS sectors (sector A or sector B)
of the UMUX 1500.
With the UCST R5A some limitations apply:
• MSP (Multiplex Section Protection) switching is only possible between
the 2 interfaces of one SYINO.
• The SYNIF_R2A.50 ESW does not allow you to operate the SYNIO unit
in the slot 8 (no UBUS access). This limitation is obsolete with the
SYNIF_R3xx ESW.
For more information on the SYNIO and operation of the unit, refer to the
Special traffic units
LECAF The LECAF unit has DSL (Digital Subscriber Line) transmission and traffic
data interfaces. The LECAF uses the CAP (Carrierless Amplitude Phase)

technology for the transmission over the DSL lines. The LECAF transmits a
payload of up to 2.048 Mbit/s over 1 or 2 twisted copper pairs (DSL lines).
The LECAF has no access to the UMUX internal BUS system but provides
front access only for its DSL and data interfaces.
The LECAF occupies 1 slot in the UMUX subrack and operates with a
remote terminal of the same family. This can be a
• LECAF or LECA2 operated in a UMUX 1500/1200 subrack
• DSL desktop unit LECAR
• router/bridge terminal MUSIC 100
A regenerator is available for applications using 2 DSL lines. It
approximately doubles the transmission range.
• Interfaces (all front access):
− DSL lines: 2 copper pairs with optional line powering facility on the
front panel.
− 2 Mbit/s according to ITU-T G.703 on the front panel. Jumpers
allow you to terminate the lines with 120 Ohms (symmetrical) or 75
Ohms (asymmetrical).
− X.21 / V.11 Nx64 kbit/s (N=1...32) on the front panel
Only one of the client interfaces (G.703, X.21) can be active.

• DSL transmission modes
− 2-pair mode
− line rate: 1168 kbit/s
− typical dynamic range: 32 dB
− 1-pair mode
− line rate: 2320 kbit/s
− typical dynamic range: 22 dB
In the 1-pair mode, the second interface remains inactive.
• Supported operational modes
− 2 Mbit/s transparent
− 2 Mbit/s structured G.704
− ISDN PRA ITU-T I.431
− Fractional E1 over 1 pair
• System characteristic LECAF implementation

− Unit type designation Special (traffic) unit
− Software download No
− Inventory Yes
− Memory for unit program code not applicable
the control unit.
For more information on the LECAF and operation of the unit, refer to the

TUNOF The TUNOF allows the optical transmission of up to four 2 Mbit/s traffic
signals over one optical port. The port connects to two fibres, one to the
transmitter, and one to the receiver. The TUNOF supports single mode
and multi-mode optical fibres.
The TUNOF has no access to the UMUX internal BUS system but provides
front access only for its optical and data interfaces.
The TUNOF occupies 1 slot in the UMUX subrack and operates with a
remote terminal of the same family. This can be a
• TUNOF, TUNOP, TUNOS or TUNOL operated in a UMUX 1500/1200
subrack
• optical desktop unit TUNOR
• Interfaces (all front access):
− Optical interfaces (transmitter and receiver) for single or multi-
mode fibres:
− wavelength: 1300 nm
− dynamic rang (including 3,5 dB system margin): 22 dB
− 4 x 2 Mbit/s according to ITU-T G.703 electrical interfaces for traffic
data. Jumpers allow you to terminate the lines with 120 Ohms
(symmetrical) or 75 Ohms (asymmetrical).
− 1 x V.11 overhead channel. Jumpers allow you to select a
− 100 Ohms termination
− no termination
− Alarm relay output
• System characteristic TUNOF implementation
− Unit type designation Special (traffic) unit
− Inventory Yes
− Memory for unit program code not applicable
− Unit fitting slots of subrack 1 - 10, (12), 13 – 21
− 2 x FC/PC
the control unit.
For more information on the TUNOF and operation of the unit, refer to

Control units
COBU<X> units
COBUX/COBUV The COBUX/COBUV control units control the configuration and
operation of the NE, maintain the MIB of the NE and provide some
important auxiliary functions. Most of the functions controlled by the
COBUX/COBUV are functions on the NE level and require interaction
between several hardware and software systems. The main functions
controlled by the COBUX/COBUV are:
• NE management functions such as
− Configuration management of the NE
− Management of ESW
− Maintenance of the management information base MIB of the NE
− Control of the Management communication including
− Routing of the PDH and SDH ECCs Embedded Communication
Channels
− Tunnelling of TCP/IP in the OSI stack.
− Routing of HDLC addresses for the Q1-master interface
− Control of internal and external management communication via
the interfaces (F, Q1, QX) and the ECCs including OSI tunnels.
− Fault management
− Performance management
− Inventory management
− Control of the PBUS access capacity. The capacity available depends
on the control unit (refer to the table "Synoptic overview of
features and control units" below).
• NE PDH synchronisation functions such as
− Conditioning of clock signals
− PETS (PDH Equipment Timing Source), internal oscillator
− Synchronisation source selection
• NE SDH synchronisation functions such as

− Synchronisation source selection
• UBUS access
− PBUS <-> UBUS access 8 x 2 Mbit/s with signalling
− in slots 1 … 21
− UBUS connection points
• 1+1 equipment protection such as

− Control of equipment protection (redundancy of control unit)
− Updating the MIB of the redundant control unit
The COBUX/COBUV control units provide the following auxiliary

functions:
• Event logbook
• Optical indicators of the NE alarm condition
• Provisioning of alarm interfaces (inputs for external sources and relay
contacts for NE alarm conditions)
• Provision of synchronisation interfaces (inputs and outputs)
• Conference for voice and CAS/data (COBUV only)
• Centralised diagnostics functions

Other functions such as external alarm integration and central

generation of metering pulses have been included with the control
unit mainly for practical reasons.
The MIB is stored in a PCMCIA card. The MIB contains information on NE
configuration, unit parameters and the software run in the units featuring
ESW download. For service purposes, it is possible to remove the PCMCIA
card with the complete MIB from the control unit (change of the control
unit hardware). The control unit needs a PCMCIA card with a minimum of
SW for operation. If the PCMCIA card or the minimum SW is missing, the
control unit is seen as a unit failure.
The COBUX/COBUV controls the UBUS and provides its access to the
PBUS. The connection points of the traffic interfaces to the UBUS are
automatically set and are normally not visible to the user. To optimise the
use of the UBUS highways, the UMUX 1500 provides an expert mode to
set connection points. The expert mode you can manually define the
connection points on the UBUS. The cross connections for the UBUS are
established via the PBUS cross connect.
• System characteristic COBUX/COBUV
− Unit type designation Not applicable
− Inventory Yes
− Memory for unit program code Non volatile
− Unit fitting slots of subrack 11, (12)
1 submini-D (9 pin)
1 RJ-45
(12): Slot 12 is mandatory for the back-up control unit.
For detailed information on the COBUX/COBUV unit, refer to the unit
description [215] and the unit user guide [315].
COBUL The COBUL control unit provides the same basic control functions
including the MIB for the NE as the COBUX/COBUV control units.
The following features are different for the COBUL compared to the
COBUX/COBUV control units:
• No support of
− PDH and SDH ECCs (Embedded Communication Channels)
− EOC (Embedded Operation Channels)
− OSI stack and tunnelling of TCP/IP in OSI
− SDH units and functions
− Centralised diagnostic functions
− Conference for voice and CAS/data
• Reduced UBUS access

(PHAU = 4)
For detailed information on the COBUL unit, refer to the unit description

COBUQ The COBUQ control unit provides the same basic control functions
including the MIB for the NE as the COBUX/COBUV control units.
The following features are different for the COBUQ compared to the
COBUX/COBUV control units:
• No support of
− PDH and SDH ECCs Embedded Communication Channels
− SDH units and functions
− Centralised diagnostic functions
− Conference for voice and CAS/data
• Reduced UBUS access

(PHAU = 4)
• Reduced PBUS access capacity

− 32 x 2 Mbit/s with signalling
For detailed information on the COBUQ unit, refer to the unit description

Overview of specific The table below provides information on those features of the NE
technical data of control UMUX 1500 and UMUX 1200, which depend only on the selection of the
units control unit COBU<X>. Features not mentioned are identical for all
control units (e.g. protection of the control unit).
Tab. 3-3: Synoptic overview of features and control units
UMUX type 1500 1500 1300 Remarks

1200 1100
Feature COBUV COBUX COBUL COBUQ CENCA
137 237 145 146 215 144 2<XY>
PBUS access 128 40 128 40 128 32 - Number of 2 Mbit/s highways (each

capacity including CAS signalling).
Access to PBUS via all slots of the subrack
but slot 21.
UBUS access 8 1) 8 1) 8 1) 8 1) 4 2) 4 2) 8 3) Number of 2 Mbit/s traffic highways (odd
capacity (16) numbered) plus the highways for CAS
signalling (even numbered)
1+1 protection ü ü ü ü ü ü - Equipment protection control unit
SW download ü ü ü ü ü ü - For ESW (unit SW)
Inventory ü ü ü ü ü ü - 4)
Alarm outputs ü ü ü ü ü ü - Relay contacts for 2 NE alarm levels
QX-interface ü ü ü ü ü ü - TCP/IP LAN protocol stack over Ethernet
10BaseT LAN interface
Q1-master IF ü ü ü ü ü ü - Functionally replaces "via ATU …".
EOC ü ü ü ü - ü ü F-interface via SIFOX
PDH ECC ü ü ü ü - - - ECC via 2 Mbit/s and TS 0 (LOMIF/LOMI4)
SDH ECC ü ü ü ü - - - ECC via STM-1 DCC
SDH DCC ü ü ü ü - - - Access to SDH Data Communication
Channel
OSI stack and ü ü ü ü - ü - IS-IS and IP router for the encapsulation of
tunnelling of TCP/IP in OSI DCN (for management
TCP/IP in OSI communication of UMUX via OSI DCN)
SETS ü ü ü ü - - - Function implemented on SYNI<X>
ESO-4 ü ü ü ü - - - With SDH only
Diagnostics ü ü ü ü - - - Central (data channel) diagnostic function
Conferencing ü ü - - - - ü Conference function for 64 kbit/s services.
5) 5) 5) 5) 5) 5) 6)
Units Restrictions apply for the units available.
1)
COBU<X>:
Access to the UBUS highways 1 … 8 in the slots 1 … 16; access to
highways 9 … 16 in the slots 11 … 21 (even numbered highways
are always reserved for CAS).
2)
COBUQ, COBUL:
Access to the UBUS highways 1 … 8 in the slots 1 … 16. No UBUS
highway access in slots 17 … 21 (even numbered highways are
always reserved for CAS).
3)
CENCA:

the highways 9 … 16 in slots the 9 … 17 (even numbered

highways are always reserved for CAS). If there are only traffic
signals without CAS you can use the odd numbered highways for
traffic signals as well.
4)
The discovery function provides limited inventory information.
5)
For the exact definition of units available with the UMUX
1500/1200, refer to the release note provided with the UCST R5A.
6)
Only UBUS units. For the exact definition of units available with the
UMUX 1100(E)/1300 refer to the applicable release notes.
Please note:
• Even and odd numbered UBUS highways:
− In the UMUX 1500/1200 the even numbered UBUS
highways are reserved exclusively for the channel
associated signalling (CAS) of the corresponding (odd
numbered highways) traffic signals, independently of
whether CAS is used or not.
− This is in contrast to the UMUX 1100/1300 (CENCA),
where it is possible to use the even numbered highways
for traffic signals if no CAS is required.
• The COBUQ is not released for the UMUX 1200.

Auxiliary units
Power units
POSUS power unit The POSUS unit provides DC/DC power conversion. The POSUS converts
the primary voltage of nominal -48 V or -60 VDC to the secondary voltages
of +/-5 VDC required for the operation of the units. The POSUS accepts
input voltages in the range from -40.5 up to -72 VDC.
• Parallel operation of units
It is possible to operate several POSUS units in parallel. Units operated
in parallel share the load on the power rails equally. This provides
modular implementation of protection. It also lowers the load per unit
which enhances the reliability of the individual units.
• System characteristic POSUS
− PBUS Highway Access per Unit (PHAU) Not applicable
− Inventory Yes
− Memory for unit program code Not applicable
− Front panel connector None
the control unit.
By preference, the first POSUS uses the slot 21 since this slot provides
UBUS access only.
For more information on the POSUS unit and its operation, refer to the
Special units
ETHUB Ethernet hub unit The ETHUB Ethernet hub unit allows you to connect several COBU<X>
control units to the PC/Work Station, which runs the Element Manager
software. The ETHUB functionality is also useful for various applications
with the LEMU6 and LAWA4 units.
The ETHUB uses 1 slot in the UMUX subrack and depends on the power
from the subrack. The ETHUB does not require configuration of
operational parameters via the UCST/UNEM but has an alarm interface
with the NE. The SW system of the ETHUB is independent of the UMUX
and does not allow SW downloads.
The ETHUB has 5 10/100BASE-T/TX interfaces. One of them allows
interchanging the Rx and Tx lines via a push button switch. This allows the
cascading of units without crossed cables.
The main function of the ETHUB is to distribute the data frames
between its interfaces. These interfaces use the independent, but internal
connected modules to provide the data transmission.
For better performance, the ETHUB uses a layer-2 switch approach instead
of a standard hub circuit.
The following interfaces are located on the front panel of the ETHUB:

• One 10BASE-T/100BASE-TX interface (LAN interface 5) with the

interchangeable Rx and Tx lines by push button switch near the Unit
LED.
• Four 10BASE-T/100BASE-TX interfaces (LAN interface 1....4) with fixed
wiring of Rx and Tx lines
After signal connection, the Auto-Negotiation procedure sets individually
the operation mode and parameters for each of the interfaces.
• System characteristic ETHUB
− Inventory Yes
− Front panel connector 5 RJ45
the control unit.
For more information on the ETHUB unit and its operation, refer to the

Software download
In the context of the UMUX 1500 the performance of a unit (with respect
to traffic signals and the system) is called a “FUNCTION” and is defined by
the unit hardware and the ESW. Existing units (e.g. most UBUS units)
feature firmware, which is an integral part of the unit hardware (since
there is no SW download possible). For these units, the unit hardware
identifies the FUNCTION (performance) of the unit at the same time.
Units with software download only feature bootloader software for the
local microprocessor system in their on-board PROM's. All functionality
specific software has to be downloaded to the local EPROM or RAM.
These units are able to perform their FUNCTION after the download of
corresponding ESW only (and the FUNCTION of the unit is only identified
then!)
SW download as a general term defines the (remote) download of the
unit software (ESW) from the EM to the units of an NE and is established
in 2 phases, each phase with its own typical process:
• Software delivery
• Software installation
The figure below shows the 2 download processes and the basic SW
systems involved in SW download.
Figure 3-5: Principles of SW download
UM UX Rem ot
1500
SW
D li
Fl a sh -
M
MIB .
N et w or Da t a .
k
ECC, ( EOC) .
Qx - o r F- PCM CI A
IF Fl a sh - Fl a sh -
M M
Con t r ol RAM
U COBUx
i
Fl a sh - Fl ash -
M M
Un i t Rem ot
Un i t (s
)
UN EM (EM S)
UCST (EM ) SW
I t ll ti
The unit software (ESW) is stored in 3 software systems:

• The EM holds a set of all ESW that is used in the NEs as a "master
copy". The SW code is compressed and cannot be executed in this
form. Each ESW has its own file with a unique file name, which allows
the identification within the SW download process.
• The PCMCIA memory card, which is fitted to each control unit, holds
copies of at least the ESW that is required to operate the installed units

of the NE. The files on the PCMCIA card are identical to the files stored
in the EM.
• The program memory of each unit (or remote unit), which holds a
copy of its current ESW (the executable code).
2 types of program memories are used with UMUX units:
− Non volatile program memories (Flash-Memories)
(all units but PCON<X> and SYNI<X>)
− Volatile program memories (RAMs)
(PCON<X> and SYNI<X>)
While the program code persists in non volatile memories after a
power off, the ESW has to be re-installed at each power on for units
with volatile program memories. The COBU<X> features a flash
memory for its own executable program code, which is downloaded
from the PCMCIA card.
A copy of the ESW has to be stored in the PCMCIA memory card of the
COBU<X> control unit in order to make such software available for
installation on the units and remote units. A unit without installed ESW
does not operate. It will be signalled as a unit hardware failure! In any
case, the PC memory card has to hold copies of at least one ESW for
control units and the application download SW. A control unit without
this minimum SW cannot operate or load ESW and will be seen as "unit
failure". This state is indicated by a permanently active red unit LED.
Some functions with remote units provide SW download for the unit
inserted in the subrack and the remote unit(s). Software download is
configured with one set of timing parameters for both the local and the
remote units. You can define ESW independently for the local and the
remote units (providing they are compatible).
The download of ESW is handled by 2 distinct system processes:
• SW delivery
is a process, which transfers the compressed unit software to the PC
memory card of the control unit COBU<X>. The software is stored in
the PC memory card of the controller unit.
The ESW can be provided via a local management interface or via a
remote management channel. The delivery process is directly
controlled by the EM and is not part of the configuration data of the
NE.
• SW installation
is a local process, which loads the decompressed ESW from the control
unit down to the individual units. To this end, the software is copied
from the PC memory card to the program memory of the unit.
It is possible to assign different versions of ESW to each of the units,
assuming they are compatible with the hardware and the configuration.
This local installation is set up as configuration data for the unit. Software
installation is only possible if the control unit holds the software required
for the installation. This means that software has to be delivered and
checked before the configuration of the software installation.
You can start SW delivery at any time as long as the EM is connected to
the NE. The SW installation can be configured for immediate application,
or scheduled, i.e. for a pre-defined time without having the EM
connected to the NE.

Synchronisation
Synchronisation functions On the NE level the UMUX 1500 provides synchronisation functions as
NE follows:
• Extraction of timing signals from traffic signals
• Local clock recovery, generation and distribution
• Selection of timing signals input to the NE for clock generation
− Selection of the timing sources by the operator via configuration
− Automatic selection of the timing sources according to the
selection algorithm defined for timing sources in the case of
failures or degradation of the sources
• Establishment of synchronisation "routing tables" for the data streams
leaving the NE.
• Implementation of synchronisation information into the data streams
leaving the NE.
• Diagnostic functions to check NE synchronisation.
Synchronisation and timing

sources
Synchronisation systems The UMUX 1500 provides 2 systems for the synchronisation of the NE and
the traffic signals leaving the NE:
• PETS (Plesiochronous Equipment Timing Source)
The PETS system synchronises the PDH traffic signals and the ESO-
1 … 3 timing signal outputs of the NE. The ESI-1 … 2 accept 2 MHz
timing signals for the PETS system.
It is possible to lock the PETS to SETS if required. In this case, the SETS
system provides the leading timing source. The PETS function is
implemented on the COBU<X> control units.
The implementation of two control units automatically provides
protection for the PETS timing system.
• SETS (Synchronous Equipment Timing Source)
The SETS system synchronises the STM-1 traffic signals and the ESO-4
timing signal output of the NE. The ESI-1 accepts a 2 MHz timing
signal for the PETS system.
Synchronisation via SETS is independent of PETS. It is however possible
to synchronise the PETS system to SETS. The SETS function is
implemented on the SYNI<X> units and hence only available with at
least one SYNI<X> unit implemented.
With the SYNIF and SYNIC units, it is possible to implement SETS
equipment protection. SETS equipment protection with the SYNIO is a
FUTURE OPTION.

Figure 3-6: Functional diagram of the SETS timing system
Sync Sources:
SDH (T1)
STM-1
Select A
PDH (T2) Select C
Squelch ESO-4/SDH (T4)
2 Mbit/s
2MHz
ESI-1 (T3)
2 MHz
Squelch
SETG Internal Timing (T0)

Select B (PLL)
SBUS, STM-1
Internal SETS
The three blocks Select <X> select the timing sources as follows:
− Select A
selects the timing source (via Select C) for the output ESO-4/SDH if
this output operates in the mode Non SETS locked.
− Select B
selects the timing source for the SBUS and consequently for all
STM-1 traffic signals leaving the NE. Simultaneously it provides the
timing source for the output ESO-4/SDH if this output operates in
the mode SETS locked.
− Select C
selects between Non SETS locked and SETS locked for the
output ESO-4/SDH.
The 2 SBUS sectors of the UMUX 1500 constitute one logical SETS system
(SETS is an NE level function). The physical SETS systems in the 2 sectors
run synchronously. The SETS system of one of the sectors is the leading
Prime SETS Sector and the other sector is the slave Agent SETS Sector.
The Prime SETS Sector provides all the SETS functions and the ESO-4
signal as described in the functional diagram above. The Agent SETS
Sector just synchronises to the T0 output signal of the Prime SETG to
create a synchronous T0 for its sector.
It is not possible to protect the Prime SETS Sector with the Agent SETS
Sector.
The sector with the first configured SYNI<X> becomes automatically the
Prime SETS Sector.
Timing sources For the synchronisation of the traffic signals the UMUX 1500 provides 3
groups of timing sources:
• Each of the 2 Mbit/s traffic signals input to the NE and terminated or
monitored within the NE (e.g. on LOMIF/LOMI4, SYNAC) can be used

as timing source (PETS and SETS). It is possible to synchronise to the 64

kbit/s or n x 64 kbit/s data signals provided by some of the UBUS units
sources (PETS only).
• Each of the STM-1 traffic signals input to the NE can be used as a
timing source (SETS). It is possible but not recommended to use the 2
Mbit/s signal extracted from a VC-12 terminated on a SYNAC as a
timing source for PETS or SETS.
• Inputs for external 2 MHz signals, which can be programmed as timing
sources for system synchronisation. The interfaces are physically
implemented on the COBU<X> control unit. The unit provides 2 inputs
(ESI-1, 2):
− ESI-1: Timing source for PETS and SETS.
− ESI-2: Timing source for PETS
Both interfaces provide galvanic isolation from the NE ground while only
ESI-1 provides 75 Ω and 120 Ω signal termination. If no timing source is
available, the oscillator implemented on the COBU<X> becomes the
timing source for the PETS synchronised signals (PBUS) and the oscillator
on the SYNI<X> the timing source for the SETS synchronised signals
(SBUS).
SSM and SSI The signals of the selected timing sources are forwarded for NE timing
source selection together with their respective quality level QL (signals
with SSM only). If the incoming signal features no QL information (signals
with SSI or no information), a QL will be assigned to these signals by
default. It is possible to assign a new QL value via the EM.
Mapping tables The STM-1 interfaces of the SYNI<X> units provide an Input Mapping
Table for QLs. The mapping table allows the timing system to adapt the
QL values of the incoming timing signal to new selectable QLs. This
feature allows you to adapt proprietary ways of setting of QLs to the ITU-
T standards.
Synchronisation selection
modes and recovery
Automatic modes For both PETS and SETS 2 basic selection modes for system
synchronisation are provided. Both algorithms provide the automatic
selection of the 'best' timing source, among the sources available:
• Priority table based
The timing source for synchronisation is automatically selected based
on the priorities assigned to the timing sources. The priorities are
assigned to the timing signals via the priority table. At any time the
signal with the highest priority (lowest number) is selected. This mode
is suited for all types of synchronisation sources. Separate tables can
be defined for PETS and SETS.
• Quality level (QL) based
The timing source for synchronisation is automatically selected based
on the QL provided with the timing source. The signal with the highest
level of quality is selected (lowest figure). This mode is particularly
suited for synchronisation sources providing QL information. If there is

no QL information provided with the timing source such information

has to be assigned.
If two timing sources provide the same QL the timing system selects
the timing source with the higher priority.
The STM-1 MS interfaces of the SYNI<X> units provide timing sources
with QL (as received) for SETS.
If appropriate, both, priorities and QL values, can be assigned to the
timing sources via the EM or EMS. Default values are assigned
automatically.
Manual override For diagnostics and test purposes, the EM(S) provides a manual override
function for the selection of timing sources.
• Forced timing source
With this function, it is possible to (temporarily) force the
synchronisation system of the NE to synchronise to a selected timing
source. The function overrides the automatic selection of the timing
source and is useful for commissioning and the analysis of
synchronisation loops.
• Locked out timing source
With this function, it is possible to (temporarily) lock out a particular
timing source from the synchronisation system of the NE. The function
is useful for commissioning and the analysis of synchronisation loops.
Clock recovery In order to cope with applications in public networks and private networks
with ONP (Open Network Provision), the UMUX 1500 provides two filters
for clock recovery (PETS only). The filter circuit of COBU<X> provides:
• Low-Q filter
The corresponding filter features a low Q, wide band filter with a cut
off frequency of 40 Hz (attenuating jitter above 40 Hz).
This filter is used for normal applications and public networks. The
requirement for the jitter transfer of 2 Mbit/s (G.703) signals is
specified by G.736.
• High-Q filter
The corresponding filter features a high Q, narrow band filter with a
cut off frequency of 2.5 Hz (attenuating jitter above 2.5 Hz).
This filter is used for ONP applications. In order to avoid potential
synchronisation problems (slips) in the public PDH transmission
network due to synchronisation processes in the private networks,
ONP specifies additional jitter filtering for frequencies below 40 Hz.
As the ONP setting of the filter (high Q) results in a slower reacting PLL,
the high-Q filter is only recommended at the nodes connecting to the
public network, and when required by the public network operator.

Distribution of timing signals

Traffic signals Signals suitable for synchronisation can be fed to and distributed from the
NE via traffic signals (e.g. 2 Mbit/s signals; STM-1 signals) or via the local
interfaces for 2 MHz timing signals.
Any STM-1 or 2 Mbit/s signals terminated within the NE and leaving the
NE can be used for the provisioning of timing signals. With some
restrictions, it is also possible to use monitored 2 Mbit/s signals for
synchronisation purposes.
Synchronisation Outputs The NE provides 4 outputs (ESO-1 … 4) for 2 MHz timing signals, which
can be programmed for signal provisioning depending on selected timing
sources:
• ESO-1 … 3 (PDH): PETS locked.
The mode allows the following configurations for each output:
− Each of the 3 ESO interfaces generates its timing signal only if a
particular timing source(s) is (are) selected for the system
synchronisation.
− It is possible to suppress (squelch) the timing signal at the ESO
interfaces (PDH and SDH) for selectable values of QL (values
provided by the active timing source).
If PETS is locked to SETS, it is not possible to select other timing
sources than the sources defined for SETS.
• ESO-4/SDH (SDH): SETS locked or NON SETS locked.
The fourth ESO (SDH) interfaces provides 2 modes of operation (refer
to the figure below):
− The signal for the ESO-4/SDH is locked to SETS
The mode allows the following configurations:
− ESO-4/SDH generates its timing signal only if a particular timing
source(s) is (are) selected for system synchronisation.
− It is possible to suppress (squelch) the timing signal at the ESO-
4/SDH for selectable values of QL (values provided by the active
timing source).
− The signal for the ESO-4/SDH is not locked to SETS
The signal for the ESO-4/SDH is directly selected from the SETS
timing sources without recovery via PLL (The internal timing source
is not available). The mode allows the following configurations:
− The selection of the timing source for the ESO-4/SDH is
configured like a timing source for SETS including priorities, QLs
etc. Both algorithms for the selection of timing sources, quality
level based and priority based, are available.
− It is possible to suppress (squelch) the timing signal at the ESO-
4/SDH for selectable values of QL (values provided by the active
timing source).

Figure 3-7: Functional diagram of the SETS timing system
Sync Sources:
SDH (T1)
STM-1
Select A
PDH (T2) Select C
2 Mbit/s
2MHz
ESI-1 (T3)
2 MHz
Squelch

Select B (PLL)
SBUS, STM-1
Internal SETS
All ESO interfaces are physically implemented on the COBU<X> control

unit. The ESO-1 and ESO-4/SDH interfaces provide galvanic isolation from
the NE ground while only ESI-4 provides 75 Ω and 120 Ω signal
termination.
SSI and SSM You can program the 2 Mbit/s traffic signals to provide a synchronisation
status message (SSM) according to ITU-T G.704 or a synchronisation
status indication (SSI) in order to control the synchronisation throughout
the network and to avoid timing loops. You can configure the type of
synchronisation information that the signal carries on the selection of a
particular synchronisation source by means of "routing tables".
The flag (one bit) for the synchronisation status indication (SSI), or the
four bits of synchronisation status message (SSM) in the traffic signal is
used to report on the quality of the signal for synchronisation purposes.
Such information is used in the NEs for the selection of the timing source
(in the QL based selection mode for signals input to the NE) and added to
the distributed signals (signals output from the NE).
Mapping tables In addition to the routing tables, the STM-1 interfaces of the SYNI<X>
units provide an Output Mapping Table for QLs. The mapping table allows
the timing system to adapt the QL values of the active timing source to
new selectable QLs. This feature allows you to adapt the ITU-T standards
to proprietary ways of setting of QLs.

Real Time Clock The UMUX 1500 features a real time clock. This clock is mainly used for
the time stamping of events (i.e. for logbook entries such as alarms and
notifications) and performance monitoring. The NE real time clock can be
adjusted to the clock of the EM with a special user command, while the
EM is connected to the NE.
With the loss of power or similar resets of the COBU<X>, the real time of
the NE gets lost. After power up or similar resets of the NE, its real time
clock has to be set manually via the EM(S). The real time clock is not part
of the configuration data. Even a full configuration download („Full
download“) cannot set the real time clock.

Redundancy and protection

Power management and The POSUS power supply unit provides load sharing with several units
protection with POSUS working in parallel. When more than one POSUS is implemented in the
subrack, the load is shared equally among the implemented units. This
enhances the individual unit's reliability and provides the implementation
of power unit protection as required. It is possible to implement the
protection of the power supply unit as a simple n+1 unit protection up to
1+1 redundant unit protection.
The entry dialogue of the UMUX 1500 provides a display, which reports
the (calculated) load on the internal +5 V power supply rail with respect
to the POSUS units implemented.
It is possible to plug the POSUS power supply unit into the subrack under
any load condition, if the primary supply is able to deliver the increased
rush-in current. It is possible to remove the POSUS power supply unit from
the subrack under any load condition, if the remaining capacity of POSUS
still meets the requirements of the implemented units and functions.
Control units 1+1 protection It is possible to duplicate the COBU<X> control unit in the subrack in
order to provide full hot standby redundancy. Hot standby implies an
updated MIB (database) for the standby control unit and short switchover
times. Switching from the master to the slave control unit is automatically
initiated upon detection of a failure in the active control unit.
For test and maintenance purposes the EM(S) provides a control dialogue,
which allows you to switch manually between the redundant control
units.
Figure 3-8: Principles of protection of the control unit
Active control unit Standby control unit
MASTER SLAVE
PBUS PBUS
Data base Data base

Synchronisation Synchronisation MIB
MIB
of the NE of the NE
Access to PBUS Access to PBUS

cross connect cross connect Selector switch
for syncronisation
Management / IFs of the Management / IFs of the provisioning
control of the NE NE control of the NE NE
UBUS UBUS
If redundancy for the control unit is implemented, the front panel

interfaces of the COBU<X> have to be cabled for redundancy as well. The
signalling outputs of the inactive COBU<X> are in high impedance states
(if applicable), while signalling inputs and management communication
are automatically handled via the active control unit.

The identical MIB of the master and the slave unit also implies identical IP-
addresses for both units. However only the interface of the master unit is
available for management communication.
The switch over between the control units is not hitless for the traffic
signals. Because of a small phase shift between the clock signals provided
by the two control units, the switch over from the active control unit to
the hot standby unit affects the traffic on the UBUS and PBUS. The
influence on the traffic signals depend mainly on the bus:
• Short interruption of the UBUS traffic.
This leads to a traffic interruption of two frames, which corresponds to
a burst of errors (for specifications, refer to the chapter "System
Specification").
• Insertion of one 0-bit in the traffic from the PBUS.
Depending on the traffic signal and the evaluation of errors, this
corresponds to a 1-bit slip or a very short burst of errors (for
specifications, refer to the chapter "System Specification").
PETS and SETS

PETS The implementation of two control units provides automatically
equipment protection for the PETS timing system (refer to the figure
above).
SETS With the SYNIF and SYNIC units, it is possible to implement a 1+1
equipment protection for SETS.
Each SYNIF/SYNIC unit features its individual SETS circuit. Since only one
SETS circuit can be active, the SYNIF/SYNIC provide equipment protection
for the SETS function. SETS equipment protection with the SYNIO is a
FUTURE OPTION.
SETS protection requires the implementation of two units in pre-defined
paired slots. Local control signals and the signals from the unit in the
associated slot allow the local SETS control circuit to enable or disable the
local SETS circuit for the NE.
Normally, the working and the protecting SETS circuits are synchronised
to the same timing source. Both circuits provide thus identical timing
signals for the NE. However, only the timing signals of the active unit drive
the clock lines, while the outputs of the line drivers of the standby unit
are high impedance.
The following failures and defects essentially define the availability of the
local SETS function:
• Failure of the SETS circuit
One or more of the monitored internal clock signals is/are missing.
• Failure of the local microprocessor system (bootloader, ESW, clock and
watchdog reset)
• SETS Source out of limits
The SETS circuit produces a clock signal with a frequency or phase shift
that is/that are out of the tolerated limits.
• SETS not calibrated

The internal reference frequency is not calibrated or the corresponding

entry in the inventory data block is corrupted.
These failures and a manual command can trigger the SETS switchover as
follows:
• Unconditional switchover
if the SETS circuit fails or the local microprocessor system fails.
The local clock drivers are shut down independently on whether a
protecting unit is available or not. If a protecting unit is available, it
provides the SETS function for the NE.
• Conditional switchover
if the parameters of the SETS circuit are out of limits (low frequency,
phase shift) and the protecting unit is available.
Only if a protecting unit is available the local clock drivers are shut
down to allow the protecting unit to provide the SETS function for the
NE.
• Manual switchover
It is possible to control the SETS systems via a dedicated UCST status
menu. The menu allows you to investigate on the status of the
presently active SETS system and to manually force the activation of
the working or protecting SETS system.
The SETS not calibrated condition cannot trigger SETS switchover but
will instead initiate the distribution of the QL (Quality Level) value DNU
(Do Not Use) with the timing signals in the SETS timing signal domain.
The switchover from the working to the protecting unit and vice versa is
not hitless for the internal clock signals and thus may affect the
synchronisation and the traffic signals.
With the UMUX 1500, SETS equipment protection is available as
described above within each of the 2 sectors. However, it is not possible
to protect the Prime SETS Sector with the Agent SETS Sector.
Cross connect The PBUS cross connect relies on a distributed architecture for signal
switching. Due to its architecture the cross connect of the UMUX 1500 is
resistant to single points of failure. It is also resistant to failures of one of
the redundant control units.
The PBUS access features a mechanism to implement a true 1+1
protection for the selected cross connection via the PBUS. The protection
switch automatically selects the signal with the better performance from
one of 2 input signals on the PBUS and broadcasts its own signal (via the
PBUS) to the 2 corresponding signal access points for output.
This protection mechanism is mainly used for SNCP protection and is
applicable for units with PBUS access only.
The traffic of the UBUS is routed via the COBU<X> control unit to the
PBUS. While the UBUS access is protected via the redundant control units,
the cross connections for the UBUS traffic rely on the PBUS cross connect
and benefit from its protection mechanism.

Subnetwork protection Subnetwork protection on the PBUS protects traffic signals between their
connection points throughout the network including the NEs. The traffic
signal is monitored only on its way through the protected subnetwork.
The protection is implemented on the same network layer with a
duplicated path.
Figure 3-9: Subnetwork protection SNCP
Path
Consistency of Server Layer
UMUX 1500 UMUX 1500

User Access 1 User Access
Terminating 1 Terminating
Point IF IF Point
Equipment Equipment
IF + Network + IF
2Mbit/s (UMUX 1500) IF IF (UMUX 1500) 2 Mbit/s
nx 64 kbit/s SNCP 1 1 SNCP
SNCP n x 64 kbit/s
Not protected SNCP Not protected
The NE provides the following types of SNCP:

• SNCP/I
1+1 SubNetwork Connection Protection with Inherent monitoring
− for n x 64 kbit/s signals (P0-nc).
The switching criteria are derived from the service layer of the 2
Mbit/s structured signal or of the aggregate signals n x 64 kbit/s.
The service layer provides criteria such as
-Loss of signal
-AIS
-BER
-etc.
− for unstructured 2 Mbit/s signals (P12x).
The switching criteria are derived from the service layer of the
signal, which provides
-Loss of signal
-HDB3 code violations (thresholds)
• SNCP/N
1+1 SubNetwork Connection Protection with Non-intrusive monitoring
for structured 2 Mbit/s signals (P12s). SNCP for VC-12 with the SYNVA
unit is a FUTURE OPTION).
The switching criterion is derived from the service layer of the 2 Mbit/s
structured signal.
The access from the connection points to the cross connect of the host NE
provides 2 redundant paths. The configuration of corresponding cross
connections implements the protection processing and switching on the
system level.
SNCP is available for traffic units with PBUS access only (e.g.
LOMIF/LOMI4, SYNAC).

Section protection Section protection protects the section of physical transmission between 2
neighbouring traffic units with redundant transmission (traffic) interfaces.
For both transmission (traffic) interfaces there is only one internal access
to the cross connect of the host NE provided. Depending on the traffic
interface the access is routed to the PBUS via the UBUS or SBUS. The
switching criteria are mainly signals corresponding to the physical layer of
the protected section such as LOS etc.
The protection processing and switching is implemented and configured
on the unit and requires no interaction of the NE control unit or
management system.
Section protection with the UMUX 1500 is compatible with the
UMUX 1100 / 1300 provided that the traffic interfaces are
supported in both systems.
Figure 3-10: UMUX section protection
Section
4 x 2 Mbit/s
UMUX1500 IF IF UMUX1300
UMUX1500
IF IF
4 x 2 Mbit/s
Connection Point
(border of service layer)
Physical section protection can be implemented with some of the units.

However, most of the units do not provide pure section protection but a
similar process:
• TUNOP and TUNOS 8 Mbit/s optical transmission interfaces
• TUNEL 8 Mbit/s electrical interface
• STM-1 MS protection with SYNIO
(MS protection with SYNIF and SYNIC are FUTURE OPTIONS)
For details on section protection available, refer to the corresponding unit
descriptions.

Linear trail protection With the UMUX 1500, it is possible to implement linear trail protection for
the VC-12 tributaries (and thus the 2 Mbit/s payload signals) between the
terminations on the PBUS. The protection is independent of the topology
of the backbone network. The protected tributaries are transmitted via
two different STM-1 ports through the network.
The SYNAC and SYNAM units provide the Linear Trail Protection function.
Figure 3-11: Principle of Linear Trail Protection (SYNAC)
STM-1
SYNIO SYNIO
SBUS SBUS
SYNAC
SYNAC
PBUS PBUS
LOMIF LOMIF
UMUX 1500 UMUX 1500
Active trail
Protecting trail
The 2 Mbit/s tributary is connected (via VC-12) to both STM-1 ports. The
first port is the active port, the second port is the protecting port for the
protected VC-12 (2 Mbit/s). The active and the protecting VC-12 must
have the same position (klm number) in the structure of the redundant
STM-1 signal frames. Failures of the VC-12 tributaries and all failures of
the server layer provide the switching criteria for the trail protection. The
switchover is non-revertive and uni-directional (i.e. no APS protocol is
used).
Multiplex Section The SYNIO unit provides 1+1 MSP (Multiplex Section Protection) for the
protection (STM-1) STM-1 section served with its 2 optical ports according to ETS 300 417-3-
1 and ITU-T G.783. To implement MSP with the SYNIO, you have to
configure the UMUX 1500 as an SDH TM (Terminal Multiplexer) for the
corresponding section.
MSP for the SYNIF and SYNIC units is a FUTURE OPTION.

Protection Modes The SYNIO supports the 1+1 unidirectional and the 1+1 bi-directional MSP
mode. In the 1+1 protection modes, each direction of transmission
provide its STM-1 signal on both ports:
• 1+1 unidirectional protection mode
The protection is non-revertive (i.e. the system does not switch back to
the Working Channel if the Working Channel becomes available again
after a switchover to the Protecting Channel).
• 1+1 bi-directional protection mode
A dedicated protocol, which exclusively runs in the Protecting Channel,
forces both directions of the STM-1 traffic signal transmission to the
same local and remote port.
The protection is non-revertive (i.e. the system does not switch back to
the Working channel if the Working channel becomes available again
after a switchover to the Protecting channel).
If after protection switchover the Working Channel is available again
while the Protecting channel fails the system switches back to the
Working Channel.
The MSP for SYNIO supports 2 basic types of switching requests which
apply for both modes of MSP:
• Traffic signal driven requests
The locally generated SF (Signal Fail) and SD (Signal Degraded) flags
that are derived from the traffic signal drive the switchover.
• External requests
The UCST provides maintenance functions that allow you to create
requests for switchover.
Compatibility of modes Both MSP modes of the SYNIO are compatible with partner units that
operate in the 1:1 protection mode. In the 1:1 protection mode, the units
use the Protecting Channel only if the Working Channel fails (thus the
Protecting Channel is a hot standby channel).

Trail monitoring / You can use trail monitoring (protection) to trace the path of a traffic
protection signal from termination to termination to make sure that the signal
received corresponds to the signal of the expected opposite termination.
Trail monitoring with Trail Trace Identifier (TTI) is provided for 2 Mbit/s
structured signals (P12s) and for VC-12 with the SYNVA unit (FUTURE
OPTION). Terminated signals can be marked with a Trace Trail Identifier
which can be checked in terminated or monitored signals against the
expected trail identifier. Mismatching identifiers will be alarmed.
Figure 3-12: Path (Trail) monitoring / protection
Path (Trail)
User Access User Access

Point UMUX 1500 UMUX 1500 UMUX 1500 Point
2Mbit/s Terminating Terminating 2 Mbit/s

Equipment Monitoring Equipment
Trail Trace Identifier

(Check TTI)
Traffic Signal Rx Traffic Signal Tx
Check TTI Add TTI
(Check TTI)
Traffic Signal Tx Traffic Signal Rx
Add TTI Check TTI
TTI functionality requires ECC mode for the Sa bits of the

LOMIF/LOMI4 and is not available with the other modes.

Performance Monitoring
Principles You can apply performance monitoring on digital trails, e.g. on 2 Mbit/s
paths for terminated and monitored traffic signals. All the units released
with the UMUX 1500 support filtered and unfiltered performance
monitoring according to ITU-T-G.826:
• Filtered performance monitoring
Based on counts of anomalies and faults of the traffic signal, filtered
performance monitoring evaluates the following parameters per traffic
signal layer:
− EB (Errored Block)
− BBE (Background Block Errors)
− ES (Errored Seconds)
− SES (Severely Errored Seconds)
− UT (Unavailable Time)
• Unfiltered performance monitoring
Unfiltered performance monitoring counts specified events associated
with the traffic signal per traffic signal layer. The type of events
depend on the traffic signal layer and interface.
The performance can be calculated for 24 hours or 15 minutes intervals
for the near and the far end of the signal path (refer to the figure below):
• Near end
where the performance is calculated based on the anomalies and
faults of the signal received.
• Far end
where the E/A bits received with the incoming 2 Mbit/s traffic signal
are used to calculate the performance of the incoming traffic signal at
the far end. The fault management process at the far end sets the E/A
bits according to the performance of the incoming traffic signal.
The same principles apply for the VC-12 traffic signals. The monitored
bits from the remote end are the REI and RDI bits instead.
The availability of the of the far end performance monitoring depends on
the traffic signal layer and interface

Figure 3-13: Principles of performance monitoring (2 Mbit/s signals)
Path
User Access User Access

Point UMUX 1500 UMUX 1500 UMUX 1500 Point
2Mbit/s
Terminating Terminating 2 Mbit/s
Equipment Monitoring Equipment
Performance
Monitoring
Near End
Near End
Traffic Signal Rx (Far End) Traffic Signal Tx
Far End Add E/A Bits

Traffic Signal Tx
Traffic Signal Rx
Units and PM To determine the quality of service these parameters can be displayed via
the EM(S) by means of counts or ratios according to ITU-T G.826.
Performance monitoring with the UMUX 1500 is available for the units
• LOMIF/LOMI4
• MEGIF
• SYNAC
The SYNAC unit provides performance monitoring for
− terminated or monitored 2 Mbit/s traffic signals
− the VC-12 SDH traffic signals
• SYNI<X>
The SYNI<X> unit provides performance monitoring for the levels
− Optical section (OS) with Out Of Frame (OOF) monitoring
− Repeater Section (RS)
− Multiplex Section (MS)
− AU4/VC-4
• Some traffic units providing data interfaces (based on traffic signals n x
64 kbit/s) are available with performance monitoring for their
respective traffic signal trails. Such units are
− UNIDA
− SULIC with NTU
− LECA2.
The LOMIF/LOMI4 and MEGIF units are available as versions

with or without performance monitoring.
The diagnostic function of the COBUV/COBUX units provides
performance monitoring for the channel under test. The monitoring
complies with ITU-T G.821.

ascom
Management Functions 4
Configuration of NE and units
Configuration tools
The managers You can control the configuration of the NE and its units using the UCST
EM or the UNEM EMS. Both managers can configure and manage the full
range of the UMUX and DSL equipment.
UCST The UCST provides local or remote access to one NE at a time, either for
NE configuration or for NE status and/or performance interrogation.
The UCST can be connected to the NE either locally via the management
interfaces of the COBU<X> unit or remotely via any of the management
communication structures provided for the UMUX. With the UCST, it is
also possible and common practice, to create configurations off-line, for
later download to the NE(s).
It is mandatory to use the UCST for the initial commissioning, local NE
configuration, local fault and performance monitoring. The UCST
manager is also suited to manage small access networks.
selection boxes, graphs and mouse selection techniques. It is possible to
create the NE configuration off-line. The configuration data is
downloaded to the NE after the establishment of a corresponding
management communication channel between the EM and the NE. To set
up the management communication for each NE properly, an initial local
configuration of the NE is required, even if the corresponding
configuration has been created off-line.
The UCST version R5A is required to configure both SBUS Sectors of the
UMUX 1500. The UCST software runs on PC type of computers under the
Windowsâ 98, ME, NT and 2000 operating systems.
UNEM Additionally, the UNEM basic package provides administration and

simultaneous supervision and performance control for all network
elements of medium to large access networks. Options are available for

Ascom Management Functions
• Active sections
Custom parameter sets To allow a fast and reliable commissioning of the UMUX for frequent
applications with high volumes of UMUX 1500 Access Systems, it is
possible to create custom parameter sets for several of the functions of
the UMUX 1500.
The custom parameters are integrated as sets of parameters into a
corresponding database of the EM(S) software. Each set has its unique
identifier. You cannot subsequently modify individual parameters of a set.
The selection of the appropriate custom parameter set from the database
allows you e.g. to pre-set fast and reliably several hundreds of parameters
that are required for the operation of the V5.x interface.
The UCST R5A defines several parameters sets for the following functions:
• V5.x application
• PHLC<X> PSTN and line test functions
The EM(S) uses the custom parameters to properly initialise the templates
of the units implied with the corresponding function. Today both
functions mentioned above are integrated within one type of sets. The
principle of custom parameter sets will be expanded as required with new
sets, new functions and new types of sets.

Inventory management
The UMUX 1500 provides inventory management that allows the
registration of hardware and software data, the control of unit functions
and compatibility checks as well as customer configuration registration
(CCR). Inventory data includes part numbers and identifiers for versions of
hardware and software, date of manufacturing and identification of
manufacturer and customer (optional).
A write-protected serial EEPROM on the unit stores the corresponding
inventory data. Only the PBUS, SBUS and new UBUS units (ISBU<X>) provide
this type memory for inventory data. To prevent inventory data from faults or
loss, the data is stored in several copies and protected with CRC.
The inventory data stored is split into 2 types of data
• Control data
controls the function of the unit and ensures compatibility between
system, hardware and software. This type of data is created during the
manufacturing process.
• Inventory information
contains unit name, manufacturer identification and ordering
information. The customer related part of the inventory data is also
referred to as "provisioning data", since the data is created during
provisioning.
The inventory data is factory-programmed during manufacturing and
provisioning. You can read back the inventory data for information and
identification of the units at any time by means of the EM(S).
Equipment Identification All equipment and parts that are relevant for system function and unit
compatibility, such as plug-in units and the subrack, carry inventory data.
This is to enable a unique identification of the equipment on the
hardware and functional level. This identification is accomplished via two
subsystems:
• Product label attached to the front panel of each plug-in unit
• Inventory data stored (electronically) on the unit
Existing UBUS units (without SW download) do not provide the
complete set of inventory data. However they provide the
control data and information on the unit firmware.

Inventory data The inventory data stored on the unit is comprehensive. A part of the data
can be displayed via the EM(S). The following entries can be inspected per
unit with the inventory dialogues of the EM(S):
Tab. 4-1: Inventory data accessible via EM
Data Description Use/remarks
CU Type Number of the generic type of function defined by Generated by the OS.
HW and SW OS use only
Board ID Number that identifies the (functional) type of unit. Identification and
compatibility check.
OS use only
HW-Key Number that specifies the (functional) version of Identification and
the unit HW. compatibility check.
OS use only
HW-Name Symbolic name of the hardware. This name defines Identification
generally also the name of the function.
Manufacturer ID Allows the identification of the manufacturer of ATR use only
the hardware
Serial Number Serial number of the unit assigned by the ATR use only
manufacturer
Manufacturer Part Number Part number assigned by the manufacturer ATR use only
HW Part Number ATR part number Identification
HW Version Version part of part number Identification
Delivery Date Assigned at the moment of CCR. Normally defines Provisioning inf.
the beginning of the warranty period.
Customer ID Customer identifier (optional). Identification
Set by CCR. Customer use
Customer Part Number Set by CCR (optional). Identification
Customer use
SW Name Symbolic name of the SW. The name can be Identification
different from the symbolic HW name !
SW Version Version of SW Identification
HW Change History Information on changes and repairs ATR use only
The UBUS units introduced with the UMUX 1300 (and without software
download) provide only a subset of the inventory data available with the
new PBUS and SBUS units.

Fault management
You can use the UMUX fault management to detect equipment, function
and transmission failures, or more generally, to monitor the availability of
the equipment and transmission paths.
The following description relies on the terms failure, defect,
degradation, fault etc. to distinguish between the different
levels in the alarm processing.
The built-in functions of the fault management detect failures, defects

and degradations of availability and, depending on configured options
generates alarms and/or logbook entries. Based on detected defects (AIS,
LOS and LOF), the NE can initiate other consequent actions, such as 1+1
protection switching. The UMUX 1500 is able to store time stamped
information on events, failures and notifications in a logbook. The
COBU<X> control unit creates the logbook locally. It is possible to transfer
the contents of the logbook and the pending alarms of the NE to the
EM(S) for display and inspection.
Alarm indicator LEDs implemented on the control unit show the present
state of alarms (UA, NA) on the NE level. Simultaneously 2 changeover
relay contacts signal the alarm state for external alarm state processing.
A dedicated LED indicator signals faults of unit hardware or failures of
functions on each unit. This fault signalling is independent of the
generation of alarms.
Units with interfaces for traffic signals provide an additional LED indicator
which signals a degradation of the quality of the traffic signals connected
to the unit.
Alarm Generation Each unit of the UMUX 1500 is able to detect equipment and/or traffic
related defects and anomalies. For further processing, these defects or
anomalies are transformed into fault causes. For each of the fault causes
you can set a reporting option (via the EM(S)) which enable (MON) or
block (NMON) the further processing of the fault causes. Only fault causes
with the reporting option set to MON will be considered for further
processing. Faults with the option set to NMON will not be considered.
Setting the reporting option to NMON is useful for interfaces without
traffic and prevents the generation of useless alarms during
commissioning and maintenance.
A fault cause is declared a failure if the fault cause persists for a certain
time, called the persistence time. The failure is cleared if the fault cause is
absent for a certain time, called the absent time. You can set persistence
time and absence time individually per fault cause.

Alarm processing Alarms are generated based on failures. For each fault cause one out of
the three severities can be assigned:
• „logbook only“
• „non urgent“ alarm (NA)
• „urgent“ alarm (UA)
An alarm or entry to the logbook is created only if the MON option is on.
If the severity is set to „non urgent“ or „urgent“ alarm, the alarm
indicator LEDs on the front panel of the control unit are
activated/deactivated and the alarm relay contacts are switched over
correspondingly. A yellow LED is used to indicate a non urgent alarm, and
a red LED is used to indicate an urgent alarm. If the severity is set to
„logbook only“, an entry to logbook is created but no alarm is generated.
All unit failures and anomalies are signalled via the local fault indication
LED on the front panel of the affected unit(s).
Traffic related fault causes are processed similarly. The traffic failure LED
on each unit is activated for all traffic failures set to MON. The generation
of alarms and logbook entries are handled the same way as unit faults.
The actual alarm condition and the logbook can be loaded for display and
inspection to the EM(S) at any time.

Print services
The EM provides several print services to print out formatted lists of the
NE configuration and specific information on the performance of its
traffic. The access to the print services depends on the type of
information:
• A dedicated menu provides the print service for data based on
configuration data (including alarm condition).
This service allows you to print out formatted lists or to store the
information to a file (*.CSV) for further processing.
• The print services for information based on dynamic data is directly
accessible in the dialogues providing the corresponding information.
The information is typically loaded with a GET command to the NE.
The EM(S) allows you to print the following lists and data:
• Configuration based data
− Units (slot, unit, short description of functions)
− Unit parameters
− Subunits
− Alarms
− Cross connections
− Timing sources
• Data based on dynamic processes
− Logbook
− Performance data
− Inventory data
Any list like information presented in the dialogues of UCST can
be selected and copied to a text processing tool using the copy
function of Windowsâ.

Management communication
Summary and overview The management communication of the UMUX 1500 relies on TCP/IP for
the layers 3/4. All addressing required for the management of the
UMUX 1500 is therefore established via IP addresses.
Each UMUX 1500 needs at least 2 IP addresses; an address for
• the QX-interface (including subnet mask)
• the F-interface. The IP address of the F-interface is at the same time
the node ID, which is used to address the NE via the ECC.
The assignment of IP addresses to the UMUX 1500 NEs requires careful
planning, since the use of IP addresses is strictly regulated. At the time of
the commissioning of the NE, its IP addresses have to be defined, since a
subsequent change of the addresses might create an address jam and will
interrupt service provisioning.
Figure 4-1: Overview of management communication UMUX
UMUX 1500
1300
UMUX 1500
UCST 1100(E)
1300
1100(E)
Transport Network
LAN PDH
SDH
UMUX 1500
Q1-master
UMUX 1500
UMUX 1300
1100(E) Q1-master
UMUX 1300
1100(E)
UNEM
LAN Access Network
UMUX 1500 NEs: UMUX 1500

UMUX 1500 UMUX 1300
Q1-master 1300
1100(E) UMUX 1100(E)
UMUX 1300
1100(E)
UMUX 1500
UCST Q1-master
The UMUX 1500s are directly accessed via their management interfaces or
if required, the UMUX management communication is transported via the
transport and access network by means of dedicated communication
channels. Several types of channels are provided in order to maintain the
flexibility of management and to adapt to the requirements of the
transport and access network:


− The ECC is an in-band communication structure for the
UMUX 1500 NEs. The NEs route the communication from the EM
via the ECC structure to the addressed NE. The ECC provides a
bandwidth of up to 2 Mbit/s. The ECC is proprietary and available
for the UMUX 1500 only.
− The transport of the UMUX 1500 management communication via
SDH transport networks requires the encapsulation of TCP/IP into
OSI, which describes the stack used for the DCN of SDH. This process
of encapsulation and decapsulation is called tunnelling of TCP/IP in
OSI and is provided by the COBU<X> control unit.
• EOC
EOC (Embedded Operation Channel) for access networks with mixed
types of UMUX equipment. The EOC is a proprietary communication
structure for UMUX Access Systems based on the SIFOX unit. The
EOC requires a time slot in the data transmission network and provides
a net transmission rate of 9600 kbit/s.
• LAN
The UMUX 1500 Access Systems can be connected to a LAN and
accessed via a LAN from the EM(S) connected to the LAN. The control
units of the UMUX 1500 provide an Ethernet 10BaseT LAN interface.
• Q1-master interface
With the Q1-master interface you can subtend remote Q-buses
(UMUX 1300/1100(E)) from a UMUX 1500.
To manage an NE, the EM(S) needs to connect to the corresponding NE.
The connect function of the EM(S) uses 2 components, which you can
define independently:
• Management Network Agent
The management network agent defines the communication parameters
and the communication interfaces for the EM(S). Such parameters are:
− Type of connection
− Type of supported NEs
− Address (Id) of the EM(S)
− Interface
− Modem device
− Serial port
− Speed on serial port
− Configuration of (local host) routing
• Network Element
The NE provides the following parameters.
− Type of NE
− IP address of the NE
− Domain
− Dial-up numbers
− HDLC router parameters
− Passwords
Depending on the type of connection and the selected NE, only some of
the parameters might apply. You can define several management network
agents each with a list of the NEs that the agent manages. You can edit
the list and the parameters of the NEs.

The management network agent of the EM(S) provides access and

connections for management communication as follows:
Tab. 4-2: Summary of access and interfaces management

communication
Connection type Management Connection
EM(S) Connects to the NE Interface EM Modem Device EM
Permanent via LAN to the QX-interface, Ethernet -
Remote Permanent via the F-interface of a gateway UCST RAS direct F, via standard null
to the LAN and QX on F modem
RS-232C F-interface UCST RAS direct F, via standard null

on F modem
Modem Point-to- via modem to F-interface RAS connection Device

Point corresponding to corresponding to
your modem 2) your modem 1)
ATU Not applicable - -
RS-485 via local Q-bus (converter RS- UCST RAS direct Q1, via RS-232/RS-
232C/RS-485) to Q1-interface on Q 485
SIFOX via EOC (access SIFOX) to UCST RAS direct F, via a SIFOX
F-interface on F via SIFOX network
SIFOX and RS-485 via modem to EOC (access RAS connection Device
via Modem SIFOX) to F-interface, corresponding to corresponding to
your modem 2) your modem 1)
via modem to remote Q-bus
(converter RS-232C/RS-485) to
Q1-interface,
1)
You have to manually install your modem in the operating system
of your PC/computer.
2)
You have to manually add a corresponding RAS connection
(Windows 95/98) or phone book entry (Windows NT) in the
operating system of your PC/computer.
Manual installation of modems provides the flexibility which is required to
install and operate almost any modem that is locally available and/or
already operating with your computer/PC. The installation process of
UCST installs however all interfaces of the type 'UCST RAS …'
automatically.
The UMUX 1500 provides 3 external (all front access on the
COBU<X>/COBUQ units) and 2 internal interfaces for management
communication:
• F-interface
• Q1-interface
• QX-interface (Ethernet 10BaseT)
• ECC interfaces (are not available for COBUQ/COBUL)
− PDH ECC
− SDH ECC

In transport networks with management communication via OSI based

DCN, the management communication of the UMUX 1500 (TCP/IP) has to
be tunnelled through the OSI DCN. This tunnelling function is
implemented on the COBU<X> control units. The following table
summarises the availability of the internal interfaces and the tunnelling
functions:
Tab. 4-3: Summary of management interfaces of UMUX 1500
Management Interface Connection and Access
external internal physical COBUX COBUQ COBUL

COBUV
F - RS-232C Pt.-to-Pt. Pt.-to-Pt. Pt.-to-Pt.
EOC EOC
Q1 - RS-485 Q-bus Q-bus Q-bus
Q1-master - RS-485 Q-bus master Q-bus master Q-bus master
QX - 10BaseT TCP/IP TCP/IP TCP/IP

Ethernet OSI OSI
- PDH ECC P0 n x 64 kbit/s PDH ECC - -
TS0 (Sa5… 8) 16 kbit/s 1 … 32
- SDH ECC SOH SDH ECC - -
(D1 … D3, D4 … D12) 1…8
Interfaces of the NE
F-interface The F-interface is a serial interface, which is mainly used for a (local) point-
to-point management access to the NE. It is implemented on the
COBU<X> control unit and features a 9 pin D-submini connector. The F-
interface is connected
• directly or
• via modem
to the serial interface of a PC or laptop computer which is running the EM
software.
The F-interface allows local configuration of the NE and local fault and
performance management. The F-interface of the COBU<X> accepts bit-
rates up to 115.2 kbit/s. The F-interface is used for the initial
commissioning of the NE and the set-up of the parameters of its
The F-interface of the UMUX 1500 uses standard PPP on layer 2, TCP/IP
on layers 3/4 and a proprietary layer 7 protocol. This part of the protocol
stack differs from the F-interface used with the UMUX 1300/1100(E). The
layer 1 remains compatible. The physical layer is according to ITU-T V.28
and RS-232 respectively.
The Internet Protocol (IP) used on the network layer, also requires an IP
address for the F-interface. The default IP address for the F-interface
provided with unconfigured systems is 10.1.1.1. When connecting the NE
to the EM, UCST selects automatically the appropriate protocol stack for
the F-interface that matches the type of your Access System. After the
initial commissioning, the NE’s IP address(es) for the F-interface (and QX-

interface) has (have) to be configured according to the implemented

management communication and to your requirements.
Q1-Interface The Q1-interface is a serial bus interface that connects to the Q-bus. The Q-bus
provides management access to a local cluster of up to 31 NEs (plus bus
master) and is typical for the UMUX 1300/1100(E) multiplexers. It is however
possible to mix the UMUX 1300/1100(E) with the UMUX 1500 on the Q-bus.
The Q1-interface of the UMUX 1500 is implemented on the COBU<X> control
unit and is connected in parallel with the Q1-interfaces of other NEs to the Q-
bus. The NEs on the Q-bus are addressed via the serial interface of the PC or
laptop computer running the EM UCST. Since the Q-bus is symmetrical an
interface converter RS-232 / RS-485 is required.
The Q-bus allows bit rates as follows:
• 9600 bit/s for configurations with the UMUX 1300/1100(E).
• up to 57600 bit/s for configurations with the UMUX 1500 only.
Figure 4-2: Q-bus (standard application)
UCST
UNEM
Modem
(optional)
only UCST
Q-bus
RS-232 C
RS-485
Converter
Q1 Q1 Q1
CENCA COBU<X> CENCA
HDLC address HDLC address HDLC address
UMUX 1300 UMUX 1500 UMUX 1300
UMUX 1100(E) UMUX 1100(E)
The COBU<X> (UMUX 1500) provides 2 Q1-interfaces with

different functionalities:
• Q1-interface (standard interface refer to figure above)
The EM(S) controls the Q-bus directly via its serial interface.
The EM(S) accesses the Q-bus locally or remotely via a
modem. This mode is of little importance for the UMUX
1500.
• Q1-master interface
The EM(S) controls the NEs on the remote Q-bus via the
TCP/IP management communication of the UMUX 1500.

The Q1-master interface of the local UMUX 1500 provides

the control for the local Q-bus. Refer to the corresponding
paragraphs below for more information on the Q1-master
interface.
The F- and the Q1-interface of the UMUX 1500 can be used alternately
only! The COBU<X> provides 2 connectors and electrical interfaces (one
for the F- and one for the Q1-interface) but the F- and the Q1-interface
share internally the same communication circuits. Hardware and software
based mechanisms have been implemented to avoid conflicts resulting
from simultaneous access via the F- and the Q1-interfaces.
The IP address of the F-interface also applies for management
communication via the Q1-interface.
The layers 2 to 7 of the Q1-interface are the same as for the F-interface.
The physical layer of the Q1-interface is according to RS-485 which allows
you to connect up to 31 NEs (plus 1 bus master) to the Q-bus. To connect
the Q-bus to the EM a converter RS-485 to RS-232 is required. When
connecting the EM to the NE, UCST automatically selects the appropriate
protocol stack for the Q1-interface, which matches the type of your
Access System.
QX-Interface The QX-interface is an Ethernet LAN interface on the COBU<X> that

provides flexible management communication via LAN / WAN structures.
The QX-interface is implemented according to the 10BaseT Ethernet
standard (IEEE 802.3/802.2) on layer 1/2. TCP/IP is used on layers 3/4,
together with a proprietary layer 7.
Figure 4-3: QX-interface and LAN
UCST
UNEM
F UMUX F UMUX LAN access

1500 1500 EM(S)
QX QX
LAN (IEEE 802.3/802.2)
F- and QX-interface use different IP addresses. The default IP address of

the LAN interface of the COBU<X> is 10.1.2.1 with the subnet mask
255.255.255.0. After the initial commissioning, the NE’s IP addresses for
the QX-interface and the F-interface have to be configured according to
the implemented management communication and to your requirements.

Communication via ECC The ECC (Embedded Communication Channel) provides an integrated
communication structure for the management communication of the
UMUX 1500. The ECC is unique for UMUX 1500 Access Systems
equipped with the COBUX and COBUV control units. It provides an
efficient means for the management communication of UMUX 1500
systems (the ECC is not available for a UMUX 1500 with the
COBUQ/COBUL).
The EM(S) normally accesses the ECC via the QX -interface of a
UMUX 1500 that is connected to the same LAN. The ECC is transported
via aggregate signals connecting the NEs, normally via n x 64 kbit/s time
slots of structured 2 Mbit/s signals or via Sa bits in the time slot 0. The NEs
are internally connected via the COBUX and COBUV units to the ECC.
You can simultaneously connect a local EM to the ECC via the F-interface
of any UMUX 1500. Multiple management access to the NEs via the ECC
is possible.
The COBUX and COBUV control units provide router functionality to route
the management traffic between the various ECC channels and the NEs.
Figure 4-4: Principles of management communication via ECC
UNEM
UCST
ECC:
n x 64 kbit/s or
16 kbit/s in TS0 in
2 Mbit/s (LOMIF)
LAN
QX
UMUX
1500 UMUX
1500
WAN
UCST
F UMUX
UMUX
LAN 1500
1500
QX
UMUX
1500
UMUX
1500
To keep the ECC function operating in OSI based DCN (such as SDH
networks) the UMUX 1500 provides 2 types of ECCs:

• PDH ECC
The PDH ECC is transported via P0 (n x 64 kbit/s) and/or the TS0 of a
structured 2 Mbit/s signal. The following parameters specify the PDH
ECC function:
− 32 ports for PDH ECCs per NE (PDH ECC-1 … 32)
The ports are implemented on the COBUX and COBUV units.
− n x 64 kbit/s up to 31 x 64 kbit/s in an structured 2 Mbit/s signal
(per PDH ECC port)
− 16 kbit/s in the TS0 of an E1 signal (per PDH ECC port).
Using TS0, a subtended UMUX 1500 can be managed without
using any of the traffic bandwidth. This will use the COBUX or
COBUV control unit and a LOMIF/LOMI4 type 2 Mbit/s interface
(2Mbit/s mode set to ‘terminated’, Sa Mode set to ‘ECC’)
• SDH ECC
The SDH ECC is transported via the SDH section overhead bytes in the
STM-1 signal. The following parameters specify the SDH ECC function:
− 8 ports for SDH ECCs per NE (SDH ECC-1 … 8)
The ports are implemented on the COBUX and COBUV units.
− 192 kbit/s or 576 kbit/s (per SDH ECC port).
Using the SOH (D1 … D3, D4 … D12), a subtended UMUX 1500 can
be managed without using any of the traffic bandwidth. This will
use the COBUX or COBUV control unit and a SYNI<X> type STM-1
interface.
− Manual or automatic link mode to select the network or user
interface.
• The ECC function is only provided with the COBUX and
COBUV control units.
• The maximum bandwidth which is available for all the ECC
channels is 2048 kbit/s per NE. The assigned bandwidth for
an ECC has to be totalled over all the SDH and PDH ECC
channels.
The maximum bandwidth that you can assign per E1 link is
31 x 64 kbit/s corresponding to an ECC of 1984 kbit/s.
Management communication based on ECC provides:

• Implementation of flexible WAN/LAN structures for management
communication.
• No restrictions on an ECC network structure (redundancy for paths).
• No practical restrictions on number of connected NEs.
For limitations on routers, refer to design rules for OSPF and OSI
networks and routers in the paragraphs on routing.
• Multiple connections to the ECC are possible.
• ECC transported in PDH and SDH (overhead bytes) traffic signals
• Uses direct access to “inband" transmission capacity in the (access and
transport) network.
No additional units for the implementation of the ECC required.

• High throughput (compared to EOC) such as required for the

download of embedded software.
• Implementation of multiple channels with variable bit-rates between
the nodes.
• QX-interface as LAN / WAN interface for management access to the
ECC (UCST & UNEM).
• The serial F-interface can be used simultaneously for local PC access.
The flexibility and performance of the ECC concept for management
communication is achieved by the router functionality, which is
implemented on the COBUX and COBUV.
The figure below shows the various elements required for the
implementation of a PDH ECC in a generic example. The EM accesses
Access System A directly via the LAN. Access System B is accessed via the
Access System A, which is the gateway to the ECC. The function of
Access System A can be realised with any UMUX 1500 (COBUX or
COBUV). The connection from the EM to Access System B is established
with the EM (UCST). The Node Id of Access System B is specified as the
address.
Figure 4-5: Example of Management access via LAN and ECC
A B
UCST
Node Id : 10.1.1.1 Node Id : 10.1.1.10
UMUX UMUX
1500 1500
F 2Mbit/s F
Qx G.703/G.704 Qx
Ethernet IF
IP Addr : 10.1.3.2
IP Addr : 10.1.2.200 IP Addr : 10.1.2.1
LAN
You must configure your PC/laptop computer, to route the corresponding

Access System node addresses (Access System B) via its Ethernet interface.
You must enable and configure the ECC and router functionality of the
COBUX (COBUV) for all NEs connected to the ECC. The router uses OSPF
and offers all the facilities to cope with complex situations requiring e.g.
external routes, virtual links etc.
Since the ECC allows the implementation of versatile and efficient
networks for management communication, the proper planning of such
networks and provisioning of corresponding IP addresses for the individual
NEs becomes an essential issue. It is important to know such addresses at
the time of commissioning the NEs. This prevents the NEs from costly
service interruptions due to reassignment of IP addresses and provides
reliable availability of service.

Principles of management
communication
Encapsulation and tunnelling Often the SDH transport networks, especially all higher order SDH
of TCP/IP in OSI DCN networks, are not based on UMUX equipment. Standard SDH NEs rely on
the OSI stack for their management communication. The transport of the
TCP/IP based management communication of the UMUX 1500 via a DCN
with SDH NEs requires tunnelling of the TCP/IP protocol via the OSI DCN.
With the UMUX 1500 and UCST R4D, this bridging function is integrated
in the NE. The TCP/IP messages are encapsulated in ConnectionLess
Network Protocol (CLNP) packets to cross SDH DCN. The UMUX 1500 at
the boundary node encapsulate the TCP/IP packets before they enter the
SDH DCN. Another UMUX 1500 at the other boundary node decapsulates
the packets when they leave the SDH DCN. The image of a tunnel can be
used, where the boundary nodes play the role of the entrance and the
exit of the tunnel respectively.
The tunnelling function is performed in the COBU<X> control units. The
tunnel is a further IP interface and is accessible via CLNP over the QX and
SDH ECC ports. At the IP network layer, a virtual LAN interface is
introduced in the system for processing the encapsulation and the
decapsulation. Packets are then sent or received to or from the CLNP layer
and then passed to the IP via this interface. The way the tunnel routers are
interconnected looks like a virtual LAN within the SDH DCN. With the
exception of ARP messages, any IP service is available on that interface.
This interface is also attached to the dynamic IP routing protocol, OSPF, so
that knowledge of IP sub-networks is exchanged across SDH DCN.
Only one tunnel interface instance exists in an NE. A dynamic protocol,
tunnel-tunnel router protocol (TTRP) is used so that all tunnel nodes are
aware of the other tunnels in the network.
Figure 4-6: Example of IP sub-networks around a single area SDH DCN
IP sub-network
10.1.10.0 IP sub-network
10.1.3.0
UMUX 1500 UMUX 1500

10.1.10.1
10.1.3.1
NE-45-15-17-00-08
NE-45-15-17-00-18
SDH DCN
Virtual LAN 10.10.1.0
UMUX 1500
10.1.4.1
NE-45-15-17-03-9F
IP sub-network
10.1.4.0

The tunnelling functionality has been introduced with UCST R4A and the
new COBU<X> control units. The implications for OSI based access to the
DCN are:
• Encapsulation of TCP/IP management communication (‘tunnelling’) at
the management head-end:
− Direct connection of the EM(S) UNEM to an OSI based
management LAN.
Since the encapsulation function is implemented in the UMUX
1500 control unit, a dedicated UMUX NE at the head-end is
required to interface to the SDH NE equipment.
− V.24 serial interface required only for legacy communication
• Decapsulation of TCP/IP management communication at the remote
NE.
The remote UMUX 1500 NE can be either part of the SDH network or
subtended from an SDH NE. This provides a high bandwidth for the
communication to UMUX 1500 whether the NE is part of the SDH ring
or subtended via other SDH NEs.
Routing All COBU<X> control units provide 3 router functions for management
communication:
• IP routing
The IP routers are implemented as OSPF routers. The routers provide 4
types of router interfaces per NE:
− F(Q1)-interface
− QX-interface
− PDH or SDH ECC (not available with COBUQ/COBUL)
− OSI tunnel (interface to virtual LAN of the OSI tunnel)
The router allows you to configure all the relevant parameters of the
OSPF routing and of the interfaces. In particular it provides
− Implementation and support of multiple areas including stub areas.
− Virtual links (transit areas)
− External routes (autonomous systems)
− Configuration of router interfaces including connectivity (no
connectivity, dynamic host, static host, no flooding)
• OSI DCN routing
The routing for the OSI DCN is implemented as an IS–IS router. Since
the IS-IS router of the COBU<X> is a level 1 router, external Level 2
routers required to connect several (more than 1) OSI DCNs (domains)
together. The COBU<X> router provides configuration for all the
relevant parameters of the routing and tunnelling function for TCP/IP.
In particular it provides
− Definition of up to 3 OSI (NSAP) area addresses per NE.
The address parameters are fully supported (AFI, IDI etc.)
− Activation of the QX-interface for the CLNP layer.
If enabled, the COBU<X> will exchange TCP/IP and OSI messages
via the QX-interface and the LAN connected to the interface. This
double functionality allows you to connect the UNEM (TCP/IP) and
the OSI based management communication of SDH equipment to
the same LAN and thus encapsulation/decapsulation of TCP/IP

into/from OSI. This function is independent on the tunnelling of

TCP/IP via OSI DCN and also available with the COBUQ.
− Parameters (number of routers, lowest throughput router, packet
size) that allow you to optimise the HELLO time for the router.
− Manually maintained routing table for NSAP addresses of the
COBU<X> routers (level 1) which are linked via the tunnel (Level 2
routers).
− Mask that allows the router to filter the addresses for subsequent
processing.
• HDLC routing
The Q1-master interface of COBU<X> uses HDLC serial address
routing. The COBU<X> decapsulates (encapsulates) the
UMUX 1100(E)/1300 management data from (to) the TCP/IP
connection to the EM and sends (receives) transparently (Layer 2)
UMUX 1300 data via the Q1-master interface. The routing relies on the
HDLC address specified for the remote UMUX 1100(E)/1300 to
establish the connection between the Q1-master and the selected
UMUX NEs on the remote Q-bus.
It is not possible to address UMUX Access Systems with COBU<X>
control units via the Q1-master interface since these control units use a
different protocol.
The IP router is responsible for the routing of all management
communication provided via the ECCs and corresponding 'OSI tunnels'.
Please note that:
• The router of the COBU<X> provides default settings. The
defaults cover standard ECC applications meeting about
95% of the ECC implementation requirements. Principles of
OSPF and OSI CLNP are provided in detail in standard
literature.
• A careful and competent planning of the IP addresses for the
NEs is necessary! Principles and rules for such planning are
provided in detail in standard literature on networking.
Guidelines for an ECC application with the UMUX are
provided in [901].
To operate the routers of the control units within specified workload you
should observe the following design guidelines:
• For the OSPF areas:
− The number of NEs that can be OSPF hosts is unlimited.
− The number of NEs that can be OSPF routers is limited to 200.
• For the OSI domain:

− The number of NEs that can be OSI routers is limited to 150.
− The total number of intermediate systems (IS) and end systems (ES)
is 260, of which no more than 160 can be IS.
− The maximum number of IS on a (virtual) LAN is 32.
• For the NE performing the IP encapsulation, you can add entries

manually to the routing table. The number of entries is limited to
1000.

• In general, the SDH network will be regarded as one OSPF area

covering many OSI areas. Further OSPF areas can be created if groups
of UMUX 1300 exist in the network.
Since some of the NEs feature OSPF and the OSI routers, the network
view is different depending on whether the view is OSI or OSPF. An
example that shows the boundaries of the OSI and OSPF areas for a
network consisting of a single OSI area is shown below:
Figure 4-7: Example boundaries of OSI and OSPF areas
UMUX
UNEM Encapsulation
1500
TCP/IP <> OSI
STM-1 OSI area

OSPF & OSI
router UMUX
1500
UMUX UMUX
1500 1500
STM-1 STM-1
UMUX
1500
OSPF area
Q-bus UMUX UMUX UMUX
1500 1500 1500
UMUX UMUX
1300 1300 UMUX
1500 OSPF router
HDLC router
The OSI area contains the following elements:

• The UMUX 1500 that performs the IP encapsulation at the
management head-end.
• The SDH network elements, including the UMUX 1500 with integrated
SDH.
The OSPF area consists of the following items:
• The items contained in the OSI area as defined above.
• The UMUX 1500 NEs subtended via their QX-interfaces.
• The UMUX 1500 NEs connected via the PDH ECC to other
UMUX 1500s.

The UMUX 1500 routes as follows:

• A UMUX 1500 with integrated SDH operates as an OSI and OSPF
router.
• A UMUX 1500
− that is connected via its QX-interface and
− that uses the PDH ECC to communicate with a further UMUX 1500
operates as an OSPF router.
• Within the OSI area, a UMUX 1500 acts as an OSI intermediate system (IS).
• The COBU<X> router supports OSPF features as follows
− Unnumbered link
− Backbone area with subnets
− Additional areas without subnets
− External Routes (via QX interface only)
IP address administration Each UMUX 1500 will have up to three IP addresses. These are:
• node IP address
• QX LAN IP address, for those nodes that use this interface
• the tunnel IP address
for those NEs at each end of the OSI tunnel
Each of these IP addresses can be on a different sub-network.
On initial power up, each UMUX 1500 starts up with default IP addresses
for the QX- and the F-interface. The addresses are adapted to adequate
values during commissioning. Only now can the new NE be integrated
into the management communication structure of the network (of
network elements).

Head end access The figure below shows the possibilities of management access to UMUX
equipment via DCN with encapsulation of the TCP/IP and access to the
UMUX network via an Ethernet LAN.
Figure 4-8: Head end management communication
Third party SDH ECC PDH ECC

SDH Equipment •OSI •TCP/IP
•TCP/IP over OSI
PDH ECC
STM-N STM-1 P0,
TS0
UNEM NWM NE UMUX1500 UMUX1500

COBUX 146/145 COBUQ 144
UCST (head end) COBUV 137
QX Q1 master QX Q1 master
LAN
TCP/IP
OSI
LAN: Ethernet 10 BaseT

(HUB not shown)
Q1 Q1
UMUX1300 UMUX1300
Q1 Q1
UMUX1300 UMUX1300
The elements connected with dashed lines to the Q1-master interfaces are
not typical for the head-end.
The LAN connects the management communications between the
Element Controllers (NWM and UNEM/UCST) and the Network Elements.
In order to manage the UMUX 1500, the TCP/IP management traffic of
the UCST/UNEM is connected to the LAN.
For some applications and if you do not wish to carry IP and OSI protocols
over the same physical LAN, a router will be required in order to provide
the separation of the TCP/IP and OSI protocols.
To transport the UMUX management communication via STM-N the IP
traffic from the UNEM must be encapsulated into OSI. This function is
performed by a UMUX 1500 at the head-end. This NE must contain a
COBUQ control unit, or if the SDH or PDH ECC is used, a COBUX or
COBUV control unit is required. The control unit will perform the
encapsulation function and route the OSI traffic to the head-end SDH
node.
The EMS UNEM is connected to a LAN segment that is reserved for OSI
and IP traffic, if you do not want that the OSI and IP traffic are present on
the same LAN. This LAN segment is connected to the OSI LAN via an OSI
router.

Remote access Figure 4-9: Remote NE management communication
Third party SDH ECC PDH ECC

SDH Equipment •OSI •TCP/IP
•TCP/IP over OSI
PDH ECC
STM-N STM-1 P0,
TS0
NE UMUX1500 UMUX1500
COBUX 146/145 COBUQ 144
(remote) COBUV 137
QX Q1 master QX Q1 master
LAN
TCP/IP
OSI
LAN: Ethernet 10 BaseT

(HUB not shown)
Q1 Q1
UMUX1300 UMUX1300
Q1 Q1
UMUX1300 UMUX1300
The UMUX management communication provided via STM-1 or the LAN

(remote SDH NE) must be decapsulated from OSI. This function is
performed by a remote UMUX 1500. This NE must contain a COBUQ
control unit, or if the SDH or PDH ECC is used, a COBUX or COBUV
control unit is required. The control unit will perform the decapsulation
function and route the TCP/IP traffic back to the LAN or the PDH ECC
(COBUX and COBUV only).
Communication via EOC The EOC provides a proprietary communication network for the
management communication within a network of UMUX Access Systems
at 9600 bit/s. The EOC is implemented by means of the SIFOX UBUS unit
and via the F-interfaces of the control units. A communication channel is
built up from the EM(s) throughout the EOC network to the addressed
NE. EOC addresses are used for this purpose. The EM(S) accesses the EOC
via a serial port of the SIFOX gateway. This SIFOX interface operates in the
EOC master mode and connects the EOC to the UBUS. The EOC is
transmitted in a 64 kbit/s channel to the remote NEs. The EOC uses its
own addressing with HDLC addresses (formerly EOC addresses). The
address range for EOC HDLC addresses is 1 … 254.
A SIFOX in a remote UMUX provides the interfaces to connect the F-
interfaces of the local NEs and connects the EOC to the UBUS for
transmission to other NEs. A dedicated 64 kbit/s channel (normally a TS in
the aggregate signal) is configured between the gateway SIFOX and the

remote SIFOX. All NEs connected to the EOC must have access to a SIFOX
interface operated in the EOC slave mode.
The management communication is set up from the EM(S) to the NE
according to an EOC specific protocol and seizes the EOC for a particular
management access. The EOC is released as soon as the exchange of data
is finished.
With a UMUX 1500 the EOC is mainly used for the management
communication for NE with the COBUQ control unit since it does not
provide the ECC functionality. The EOC is compatible with all UMUX
Access Systems. The EOC can be optimised for throughput for various
sizes of networks and provides net bit-rates as follows:
• For the UMUX 1100(E)/1300 and mixed equipment
UMUX 1100(E)/1300 and UMUX 1500: 9600 bit/s
• UMUX 1500 Access Systems only: up to 19200 bit/s.
Figure 4-10: Management communication via EOC
UNEM
UCST
Qx F
Serial IF (EOC)
C S
O I
B F
U O
Q X UMUX1500
Aggregate
with EOC
UMUX Network
Aggregate
with EOC Aggregate
with EOC with EOC
C S C S
O I E I
B F N F
U O C O
UMUX1500 Q X UMUX1300 A X
(existing)
Serial IF (EOC) Serial IF (EOC)
Qx F F
You can use the QX-interface of COBUX and COBUV in parallel with the
EOC to access the NE locally or to access the ECC. You can implement the
EOC communication structure for UMUX 1500 networks or single NEs
(such as the UMUX 1300/1100(E)) independent of the ECC (see previous
paragraphs).

Communication via Q1- The Q1-master interface allows the EM(S) to control NEs connected to a
master interface remote Q-bus via the DCN. The Q1-master function is implemented for the
UMUX 1500 and available with all the control units. The Q1-master
interface of the COBU<X> uses HDLC serial address routing. The
COBU<X> decapsulates (encapsulates) the UMUX 1300/100(E)
management data from (to) the TCP/IP connection to the EM and sends
(receives) transparently (Layer 2) the UMUX 1300/1100(E) data via the Q1-
master interface. The routing relies on the HDLC address specified for the
remote UMUX 1300/1100(E) to establish the connection between the Q1-
master and the selected UMUX NEs on the remote Q-bus. The Q1-master
interface is addressed via the (TCP/IP) addresses of the corresponding
UMUX 1500 and the address of the TCP/IP port assigned to the Q1-master
interface.
This mode is important since it allows you to control remote clusters of
the UMUX 1300/1100(E) directly from your EM(S) via the management
DCN of the transport and/or the UMUX 1500 access network.
Figure 4-11: Q1-master interface
UCST
UNEM
DCN
•SDH ECC
•PDH ECC
UMUX 1500
IP address
COBU<X>
Q1-master
interface
Q-bus
Q1 Q1 Q1
CENCA CENCA CENCA
HDLC address HDLC address HDLC address
UMUX 1300 UMUX 1300 UMUX 1300
UMUX 1100(E) UMUX 1100(E) UMUX 1100(E)
Please note that:

• The standard Q1-interface and the Q1-master interface are 2
separate interfaces of the COBU<X> (UMUX 1500).

• Only the UMUX 1300 and the UMUX 1100(E) can be

addressed via the Q1-master interface.
The Q1-master function is enabled on the COBU<X> control unit of the
NE, which operates as a gateway to the remote Q-bus. The EM(S)
addresses the NE on the Q-bus by the IP address of the gateway
multiplexer and the HDLC address of the (Q-bus) NE.

ascom
Construction and EMC/ESD 5

Construction
Overview The subrack provides the mechanical packaging for the units and the
backplane with electrical connections to the bus structures and the power
supply. The subrack is a compact construction with a removable front
cover. The cover provides apertures so that the LED indicators on the units
remain visible even with the front cover installed. The subrack is provided
with a cable tray.
Heat deflection shields or fan units are optional. Such devices are required
if the environmental conditions of the installation do not allow the
UMUX 1500 to operate within specified temperature range, e.g. if
systems are installed on top of each other. The fan unit has to be installed
if the passive control of the air flow provided by the heat deflection shield
is not sufficient.
The basic construction practice for the subrack and its auxiliary elements
relies on the 19-inch standard. Adapters are provided for ETSI
installations. Illustrations of the subrack with and without front cover are
provided at the beginning of this document. Design and dimensions of
the subrack and the auxiliary elements are provided in the figures below:

Ascom Construction and EMC/ESD
Figure 5-1: Overview of 19-inch practice

(dimensions [mm])
1 Subrack 19 inch
2 Cable tray 19 inch
3 Heat deflection shield or fan unit (optional)
The fan unit takes half of the height that is reserved for the
heat deflection shield.

Subrack and cable tray

Design and dimensions The figure below shows the layout and the mechanical dimensions of the
19-inch subrack, including the grounding bars.
Figure 5-2: Subrack UMUX 1500

(dimensions [mm])
Figure 5-3: Cable tray subrack UMUX 1500

(dimensions [mm])
Partitioning and backplane The subrack of the UMUX 1500 features 21 evenly spaced slots. The
arrangement width of every slot is 4 TE (20,32 mm). While the mechanical parameters
are identical for all slots, the electrical interface to the backplane depends
on the slot position.
The backplane provides the physical bus structures and carries the power
rails for the internal power supply. The backplane features a row of
connectors compatible with the UBUS connectors of the UBUS units and a
second row of connectors providing access to the PBUS. Where
applicable, a third row of connectors provides access to the SBUS. The
backplane is protected and shielded by the construction of the subrack,
namely at the rear.

Figure 5-4: Layout subrack UMUX 1500

(dimensions [mm])
UBUS
PBUS
SBUS
Heat deflection shield

(optional)
Figure 5-5: Heat deflection shield UMUX 1500
(dimensions [mm])
The heat deflection shield can be installed above the subrack or below the
cable tray. Depending on the orientation of the heat shield, the hot air is
evacuated to the front or to the rear of the rack.

Fan unit (optional) Figure 5-6: FANUV fan unit (dimensions [mm])
The FANUV fan unit features three individual fans, which are monitored
for operation. The operation of the fans is controlled by the temperature
of the air. The design of the fan unit provides a minimum air velocity of
0,6 m/s through the subrack even if a lateral fan fails (worst case).
The FANUV is installed above the subrack and operates from the 48 VDC
power supply (range 39.5 … 75 VDC). The fan unit provides an interface to
indicate operation of the unit and failures of the individual fans. The unit
provides an alarm contact, which you can connect to the alarm interface
of the COBU<X> control unit. A set of cables is available to make it easier
for the connection of the alarm contact and the power supplies (FANUV -
UMUX 1500). You can install an optional heat deflection shield to
evacuate the hot air to the front or to the rear of the rack.

Subrack with front cover The figure below shows the mechanical dimensions of the 19-inch
subrack with installed front cover.
Figure 5-7: Subrack UMUX 1500 with installed front cover

(dimensions [mm])
ETSI adapters Subrack, cable tray and heat deflection shield (fan unit) are designed for a
19-inch rack. To install these units into a rack complying with ETSI, special
adapters are available. There are 2 sets of adapters provided as indicated
in figures below.
Figure 5-8: Adapters 8 HU for the installation of subrack and cable

tray into ETSI racks
(dimensions [mm])

Figure 5-9: Adapters 10 HU for the installation of subrack, cable tray

and the heat deflection shield (fan unit) into ETSI racks
(dimensions [mm])
Figure 5-10: Adapters 1 HU for the independent installation of the

FANUV unit into ETSI racks
(dimensions [mm])
Figure 5-11: Adapters 2 HU for the independent installation of heat

deflection shield into ETSI racks
(dimensions [mm])
The adapters provide M6 nuts for the fixing holes of the 19-inch
mounting.

Plug-In Units
All the plug-in units of the UMUX are designed for standard subracks of 6
HU and have the same depth while the width is variable. Plug-in units
have a width of 1 to 3 slots (20 ... 60 mm).
Two fixing screws secure the units plugged into the subrack (exceptions
with 4 screws are large units such as the PHLC1). Two pull-out handles at
the top and the bottom of the front of the unit help you to insert the
units into and remove the units from the subrack. Exception are the
POSUS and the "old" UBUS units, which provide one handle only on the
top.
A standardised connector system connects the signals of the units to the
backplane. All units feature the top connector providing power supply,
timing signals, internal management communication and, if applicable,
access to the UBUS of the UMUX 1500. PBUS and SBUS units additionally
feature the PBUS and SBUS connector.
Front connectors are provided for traffic and control signal interfaces. The
standard connector for traffic signal interfaces and some of the control
signal interfaces provide a latching system that can be released without
tools.
Figure 5-12: Plug-in unit
Fixing screw
Pull-out handle
Unit
Label
Unit LED (red)
Connector
Traffic LED (red) compatible
to UBUS
PBUS
connector
DIN 41 612 connector type C,

Latching clips 2(3) x 32 contacts, male,
full access
Pull-out handle
Fixing screw

Cabling and connections

Signal cables All signal cables connect via front connectors to the corresponding traffic
or control units. The traffic units designed for the UMUX 1500 feature
connector frames based on the standard DIN 41 612. The connector caps
of the cables are locked to the units by means of latching clips (refer to
figure above).
The standard traffic signal connector of the UMUX 1500 is slimmer than
its predecessor used with the UMUX 1300/1100(E). It is possible to install
units featuring the connector practice of the UMUX 1300/1100(E) in the
UMUX 1500 subrack while using the corresponding signal cables and
latching system.
Cables and connectors are available for all of the interfaces of the
UMUX 1500.
Cable tray and grounding The signal cables are fed from the connection panel to the cable tray
bar below the subrack. The cable tray provides strain relief and holds the
cables in position for the units in the subrack above. The cable tray also
features a connection point for the power supply. Thus the subrack can
be installed and removed independently from the cable tray and any
installed cables.
The grounding bar for signal cables is in front at the bottom of the
subrack. It connects the screens of the signal cables to the equipment
ground. A simple clamping mechanism holds and connects the cable
screens to the grounding bar. The grounding bar is a part of the
construction of the subrack and consists of two independent halves.
The bar features a thread for the connection of the protective earth or as
a bonding point for wrist straps for maintenance.
Figure 5-13: Signal cables and grounding bar

Connection panel The connection panel terminates the external traffic signal cabling with
your standard type of connectors. It converts the signal cables fitting the
UMUX units, each cable fitted with the appropriate UMUX connector. A
connection panel is also used to convert between different types of signal
cables e.g. between symmetrical and asymmetrical cables.
You must use a connection panel if you operate the interfaces of traffic
units such as the LOMIF/LOMI4 in the 75 Ω mode. Due to space
congestion, the connectors and cables interfacing the LOMIF/LOMI4 use
symmetrical cables. A connection panel nearby establishes the conversion
to the coaxial cabling.
The implementation of such a connection panel depends on your
application and is available on request.
ESD / EMC and grounding

The subrack with the front cover installed represents a Faraday cage like
construction if the cables are connected to the cable grounding bar as
instructed. Conductive metal sheets all around the subrack protect the
UMUX 1500 from ESD and electromagnetic fields.
The 19-inch mounting flanges of the subrack are conductive and provide
a conductive contact to the rack if the rails of the rack provide a
conductive surface.
When in operation, the equipment is protected against ESD in accordance
with IEC 61000-4-2, provided that all parts have been installed as
instructed by the user documentation.
The power supply connection of the subrack provides a lead for system
ground. The system ground connects internally to the construction of the
subrack.
All the plug-in units used with the UMUX 1500 are ESD
sensitive units; they must be handled with care.

ascom
Operation and Maintenance 6

Management interfaces
Most of the maintenance and operation for the UMUX 1500 is based on
functions of the EM and EMS. The management access of the EM(S) to
the UMUX 1500 relies on the 3 physical interfaces and if applicable on the
ECC (EOC uses the physical interfaces of the control units for
management access). Depending on the type of intervention and
management infrastructure one of the 3 interfaces is used:
• F-interface for point-to-point access:
Mainly used for local commissioning of the UMUX 1500 or for on site
fault debugging. The F-interface allows bit-rates up to 115 200 bit/s
for local access (The speed available depends on the driver section of
the PC/computer and the length of the signal cables). The F-interface
also provides the NE access to the EOC management communication
channel. The bit-rate for EOC access is limited to 9600 bit/s. To
connect to the UMUX 1500, the IP address of the F-interface of the NE
is required.
The EM can also access the F-interface of the UMUX 1500 remotely via
a modem.
• QX-interface for Ethernet LAN access:
The QX-interface is normally used for remote management access, but
can be useful for local commissioning, provided the PC/computer
features an Ethernet interface. The QX-interface is used to address NEs
(UMUX 1500) that are directly connected to a corresponding LAN
and/or to access the ECC. The QX-interface offers high bit-rates
(10BaseT).
To connect to the NE, the EM(S) needs to know the IP address of the
QX-interface of the NE.
• Q1-interface for local clustering of the management access:
The Q1-interfaces of several local NEs are connected in parallel to the
4-wires of the local Q-BUS . The Q-BUS is a serial bus and terminated
to the EM with a conversion box, which converts the Q-BUS to a
standard RS-232C interface. The EM accesses the NEs via its serial
interface using EOC addressing to select the Access Systems on the Q-
BUS , while the IP address of the F-interface is required for the
connection.
The ECC is an internal management interface of the UMUX 1500 NEs
which is not directly accessible, but is accessible to the EM via the
gateway function of a NE.

Ascom Operation and Maintenance
Alarm interfaces
Optical fault and alarm Optical fault and alarm indication is a part of the fault management
indication system of the UMUX 1500. Optical indications are implemented on both
"system" and "unit" level. Alarms are concentrated on system level to
"Urgent alarms" (UA) and "Non-urgent Alarms" (NUA). The present
system alarm state is optically indicated with corresponding LEDs
implemented on the COBU<X> unit.
Fault indications are available with all units. Standard (traffic) units feature
2 fault indicator LEDs:
• Red "unit" LED (position 1 in figure below):
All units:
Indicates a hardware failure or a general non-availability of the unit
(due to missing software, configuration etc.). The COBU<X> features a
multi-functional red/green LED indicator at this position. The green
colour is used to indicate the active state of the software system of the
COBU<X>.
• Red "Traffic" LED (position 2 in figure below):
All units but the POSUS:
Indicates failures or defects due to the subunits or traffic functions.
The COBU<X> control unit provides both unit LED fault indicators and the
indicators for alarms. It therefore features additional LEDs (positions 3 and 4
in figure below) to indicate urgent and non urgent alarms.
The PHLC<X> unit provides additionally to the standard LED indicators
(positions 1 and 2 in the figure below) a green LED (positions 5 in the
figure below) to indicate the shut down status of user ports.
Figure 6-1: Position of LEDs (front panel of units)
1 3
2 4
5
Unit front view
(not to scale)
Please note that:

• The indicators positions 3 and 4 are implemented on the
COBU<X> control units only.
• The indicator on the position 5 is implemented on the
PHLC<X> units only.

Electrical alarm indication The electrical alarm indication is also part of the fault management
system. The electrical interfaces are implemented as 2 solid-state
"changeover relay contacts" on the COBU<X> control unit:
• 1 output indicates the NE alarm status Urgent Alarm (UA).
• 1 output indicates the NE alarm status Non-urgent Alarm (NA).
The contacts are switched synchronously to the optical indicators for UA
and NA (position 3 and 4 in figure above). The relay contacts are
connected via the front panel connector of the COBU<X>.
Alarm description Since alarms are initiated by a failure of a function or traffic signal, the
alarms are assigned to the unit, which carries or controls the function or
traffic signal. Entries to the alarm list are thus sorted by unit. Alarms
create an entry to the alarm list and to the logbook of the NE. Alarm texts
are defined when the corresponding unit is provisioned.
Notifications The notification function plays a secondary role in fault management. It

helps you to find out the relationship between NE internal events and
possible failures associated with these events. Notifications create an entry
in the logbook of the NE.
NE fault list The NE fault list is a structured list of pending faults (generating alarms)
sorted by units and subunits. Each fault entry contains a short fault (alarm)
description. The alarm status at system level is indicated as well.
The list of faults (alarm list) can be loaded to the EM for detailed
inspection and printed for documentation.
Logbook The logbook is an internal buffer of the COBU<X> containing a log of

incidents with time stamps (the term “incident” is used here instead of
“event” to distinguish “incidents” from “incidents” of the “event” type).
In addition to the time stamps, the logbook shows the information and
state for each incident. The following incidents create entries in the
logbook:
• State change to active failure
for fault causes monitored for alarms (MON = alarms) or for entries to
the logbook only (MON = logbook only).
• The state change to inactive failure
for fault causes monitored for alarms (MON = alarms) or for entries to
the logbook only (MON = logbook only).
• Events
Entries of the type "Event" are incidents which do not create alarms,
but are logged for debugging and tracing important manipulations
(incidents) on the NE. An important source for “Event” type incidents
is the software system of the NE.
The logbook can be loaded to the EM for detailed inspection and printed
for documentation.

Performance control and monitoring

Performance control and monitoring is the enveloping process for all the
control of system performance and monitoring of traffic performance.
According to this definition, the UMUX 1500 provides the following
functions and subsystems for performance control and monitoring:
• Alarm system
• Test functions and diagnostics
• Traffic signal performance monitoring
A description of the performance monitoring for traffic signals is provided
in the chapter 3 “Functional descriptions”. The alarm system and the
alarm interfaces of the UMUX 1500 have been described in the previous
paragraphs and in the chapter 3 “Functional descriptions”. The
paragraphs following are dedicated to the test and diagnostic functions
provided with the UMUX 1500.
Test functions and diagnostics

The UMUX 1500 provides diagnostics and test functions, which allow
active testing, or verification of functional blocks, important functions,
selected hardware items and traffic signals. Test functions and diagnostics
provided are available on
• System level
• Functional level
• Unit and subunits (traffic level)
• Central diagnostics
You can control the diagnostic and test functions with the EM(S) via the
menus Status/Maintenance and Diagnostics Parameters respectively,
depending on the level (system, function, unit) and the type of
diagnostics. For some of the functions the dialogues for the function's
configuration provide “Diagnostic” buttons to verify the configuration.
The diagnostic and test functions do not generally belong to the
configuration management. The corresponding settings are therefore not
part of the configuration data. The functions can be controlled only when
the EM is connected to the NE. All test settings get lost with the loss of
power or a system reset.
System level On the system level, test and diagnostic functions are provided as follows:
• Alarm indicators
LED indicators for urgent and non urgent alarms including associated
switchover relay contacts.
• NE fault list
Time stamped entries of all pending alarms
• Logbook
The logbook is a list with chronological time stamps and descriptive
text for each alarm. The logbook contains an entry for the time the

alarm comes up and the time the alarm disappears. Events and
notifications create additional entries.
Inventory provides access to the inventory data of each unit and the
related information of the MIB of the NE. Inventory is particularly
powerful, for trouble shooting and questions of compatibility.
Access to diagnostic functions is with the EM(S) via dedicated dialogues.
Some of the functions provide local interfaces (optical indicators).
Functional level On the functional level, test and diagnostic functions are provided as
follows:
• Diagnostics for PETS, SETS and ESO SDH
informs you of the availability of the configured timing sources. For
diagnostic purposes, the UCST provides the dedicated status menu.
The status menu allows the analysis of the timing system of the NE.
Control functions allow you to force the system to synchronise to
selected timing sources, overriding the automatic source selection. It is
also possible to lock out a particular timing source from the selection
process.
• Diagnostic function for protected cross connections
informs you of your presently active signal path and the quality of the
corresponding tributary signal.
• Information of the usage of UBUS and PBUS
informs you of your present use of the UBUS and PBUS. The diagnostic
provides details of the connection points on the UBUS and the
remaining capacity on the UBUS and PBUS.
• State indication and diagnostics for redundant system control
informs you of your presently active control unit and the state of the
MIB of the standby unit. Switching to the inactive control unit can be
forced (if unit available).
• State indication and diagnostics for the ECC OSPF router
− Routing table of the local OSPF router.
− IP statistics reflecting the activities and traffic on the respective
router interfaces.
− OSPF link state and neighbour tables.
• State indication and diagnostics for ECC links

informs you of the availability of configured ECCs.
Access to all functions is with the EM(S). Most of these functions
(exceptions are diagnostics of synchronisation and cross connections) are
accessed via the “Status” menu of the COBU<X> control unit.
Unit and subunit (traffic On the unit and subunit (traffic signal) level test and diagnostic functions
signal) level are provided as follows:
• Fault indicators of units
Optical indicators for the physical localisation of unit and traffic
failures.

• Test loops
Most of the traffic units feature points within the traffic signal path for
the application of test loops. Test loops might be set as front end
(towards the traffic interface) or back end (towards the cross connect)
loops. Test loops are helpful tools for the detection of equipment
and/or transmission faults.
• State indication for traffic signals
Read back of signalling and TS 0 Sa-bit information. If applicable the
trail identifier received is displayed as well.
• Central diagnostics for traffic signal channels
For details, refer to paragraphs below.
• Performance monitoring
A description of performance monitoring for traffic signals is provided
in the paragraphs on “Redundancy and protection” in the chapter 3
“Functional Descriptions”.
• Subscriber line test
The PBUS units with PSTN subscriber line interfaces feature built-in test
facilities to test subscriber lines (PHLC1 and PHLC2). The test can be
programmed for automatic execution.
Most of these functions (exceptions are optical indicators) are accessed
with the EM(S) via “Status” or “Diagnostic” menus.
For details refer to the respective unit descriptions.
Central diagnostic for traffic The COBUV and COBUX control units provide versatile diagnostic
signal channels functions for the analysis of the performance of traffic channels set up
between two access points. The access points are defined as the interfaces
to a test signal generator and a signal analyser. Both of the two functions,
the test signal generator and analyser, are implemented on the control
unit.
The access points to the traffic channel under test can be
• on the same COBUV/COBUX unit
• on 2 different COBUV/COBUX units
• on the COBUV/COBUX unit and an external measurement equipment
(providing there is compatibility between the test signal and the
testing method).
Due to standardised test signals, most external generators and analysers
can be used in co-operation with the complementary function on board
of the COBUV/COBUX. The test signal is cross connected via the PBUS
between the generator/analyser of COBUV/COBUX and the physical
interface of the NE.

Figure 6-2: Principles of traffic channel diagnostics
UMUX 1500 Any NE
PI Transmission Network PI
COBUV
COBUX
UMUX 1500 UMUX 1500
PI Transmission Network PI
COBUV COBUV
COBUX COBUX
Symbols and abbreviations:
Pattern Generator
Pattern Analyser
Cross Connect
PI: Physical Interface
Test signal The test signal, a fixed bit pattern or pseudo random bit pattern, is
injected into the data channel under test. The test signal can be defined as
n x 64 kbit/s (1 ≤ n ≤ 31) assigned to the corresponding number of
timeslots or as a transparent 2 Mbit/s data stream. A separate bit pattern
can be defined for the signalling channel.
You can program a fixed bit pattern or one out of 3 pseudo random bit
pattern signals with variable sequence length:
• 8 bits of the fixed bit pattern
• Pseudo random pattern with sequence length of
− 2^11-1 bits
− 2^15-1 bits
− 2^20-1 bits
To allow you to verify the test set-up, you can define an artificial bit error
rate of 1 bit error per second for the test signal. Depending on the type of
the test signal, you can control the analyses via the menus for status or
performance monitoring.
Analyses for 8-bit patterns The bit pattern sent and received in n x 64 kbit/s signals are both
displayed while the signalling bits received are analysed for "AIS" and
"Failure of Signalling". You can select the time slot for the analysis. If the
bandwidth of the test signal has been set to 64 kbit/s the signalling bits
can be made directly visible as well.
If the bit patterns are injected into a 2 Mbit/s transparent signal, an offset
can be set in order to compensate for the phase shift between the pattern
sent and received.

Analyses for pseudo random The signal with pseudo random bit pattern sequences can be used for
bit pattern sequences
• Performance measurement (according to ITU-T G.821).
• Signal delay measurements
The pseudo random bit sequence with the longest sequence can be
used to measure the delay between the 2 access points (same
COBUV/COBUX only). The delay is directly indicated in µs.
Upgrading
Upgrading hardware The verification of the compatibility of the new hardware with the system
before the upgrade is essential!
Upgraded or new units can be plugged into the powered subrack. Units
with SW download require a suitable ESW and the purchase of a
corresponding licence.
The inventory data and the identification label on the front panel of
upgraded hardware have to be adapted accordingly. To comply with this
requirement all hardware has to be upgraded as instructed by the
manufacturer. Such a procedure ensures correct CCR processing for the
upgraded hardware. Correct CCR (Customer Configuration Registration)
is a prerequisite for rapid and efficient after sales service.
Upgrading with hardware The verification of the compatibility of the hardware providing protection
protection with the system and units before the upgrade is essential!
You can implement the protection of the power supply and the system
control at any time without interrupting traffic signals (payload). You
must follow the rules provided for the implementation of units. For some
signals (management communication, timing sources, alarm signals etc.)
you may need to install additional cabling, in order to provide full
functional protection.
Upgrading unit SW
Units with SW download The verification of the compatibility of the new ESW with the unit
hardware before the upgrade is essential!
Upgrading the ESW requires management access of the EM(S) to the NE
with the units to upgrade. The ESW is upgraded as follows:
• The new ESW is first delivered to the NE (to the MIB of the COBU<X>).
• Afterwards the installation of the new ESW has to be configured by
means of the corresponding menus of the EM(S) for all the units
affected.
You can program the installation for immediate application or for
scheduled installation at a defined date and time. This last feature
allows the simultaneous installation (and application) of new ESW
throughout the whole access network.
• The identification label on the front panel is not affected.
To operate new ESW, corresponding licences need to be purchased.

Units without SW download The verification of the compatibility of the upgraded function with the
unit hardware before the upgrade is essential!
For units without SW download, you can upgrade the unit SW by
changing the corresponding FW PROM. A functional upgrade for units
without SW download corresponds to an upgrade of the hardware.
The inventory data and the identification label on the front panel of
functionally upgraded units have to be adapted accordingly. To comply
with this requirement you have to upgrade all hardware as instructed by
the manufacturer. This ensures correct CCR (Customer Configuration
Registration) processing for the upgraded hardware. Correct CCR is a
prerequisite for rapid and efficient after sales service.
Upgrade procedures The following upgrade procedure allows you to control the provisioning
of existing installations with the new UCST management SW and new
ESW for the COBU<X> control units. The controlled provisioning includes
proper mapping of the existing configuration into a NE configuration with
new unit templates.
The following procedure upgrades the UCST 3.3a/1 to UCST R5A and the
COBU<X> ESW R2x to R3x respectively.
1. Install your new UCST R5A including the required files with ESW in
the directory FW.
2. Connect from UCST R5A to the NE and upload the configuration.
3. Deliver the new COBU<X> software (R3e or more recent) including
the file with the application download SW apdsw_R1.C00 to the
NE.
4. Configure the installation of the new ESW for the COBU<X> and
start a partial download.
For NEs with a redundant control unit, you have to wait until the
ESW of the redundant unit is upgraded as well (control via status
dialogue).
5. Now convert the units from R2x templates to R3x templates (e.g.
COBUX 117 to COBUX 145).
6. A full or partial download of the configuration concludes the
upgrade.
Please note that:
• New settings are initialised with default values. Additional
commissioning for these parameters might be required after
the upgrade.
• Do not remove the existing application download SW
(apdsw_R1.A00) from the NE. The SW is locally required as
long as there is ESW that has been installed with this type of
application download SW.
• Do never create a PC card without a valid COBU<X> ESW.
Remove old ESW only if after the delivery of the new
version.

Manipulation of the equipment

Unit handling All units can be plugged into / removed from the powered subrack. If a
unit is extracted, the traffic and functions affected by the respective unit
are interrupted. Traffic and functions are not affected, if the units
removed are in hot standby mode (e.g. slave control unit) or are providing
n+1 protection (power converter units).
Plugging a unit into the wrong slot position does not cause damage to
the unit nor to the surrounding equipment. For the system to operate
successfully take care to adhere to the rules for correct unit to slot
assignment in the slot arrangement of the subrack. This applies in
particular for the control units.
Equipment handling The subrack is usually mounted in a 19-inch or an ETSI rack suited to
miscellaneous types of equipment. The installation of the subrack into an
ETSI rack requires the ETSI rack mounting kit with corresponding adapters.
During operation, install the front cover of the subrack and ground the
cables as instructed to provide the specified ESD and EMC characteristics.
All units for the UMUX 1500 are plug-in units with front access for traffic
and infrastructure signals. They are usually plugged in and connected
during installation. For upgrade and maintenance purposes, units can be
plugged in and taken out while powered. Configured units will create
alarms as specified by the unit configuration.
System labelling
Identification label Each system and unit with active components carries an identification
label on the front. The label is an integral part of the unit and must never
be removed.
Depending on the functional level of the unit labelled, the layout of the
label is slightly different. The main types (functional levels) of labels (used
with the UMUX 1500) are
• Unit hardware
for units with SW download
• Unit function for
− units without SW
− units with FW
• Subrack and CE brand

Detailed information on labels and their contents is provided in the
following paragraphs.

Identification label “Unit The label specifies hardware only. To create a FUNCTION, requires a unit
Hardware” hardware and a unit (embedded) SW. This type of label is typical for new
units with SW download. The information on the label gives the
identification of the units and provides detailed information on the build
and change status of each unit. A separate field at the top of the label is
reserved for optional customer specified data.
Figure 6-3: Example identification label of units with SW download

(PCONV)
6V MFR ID: 120771

S/N: 97987654
S
ROFBU 367 108/1 1P

R1A/C 2P
97W40 10D
PCONV 32P
Legend:
Mandatory information (bottom):
1P Product number (assigned by supplier)
2P Build state (assigned by supplier)
10D Delivery date (format: yyWww)
32P Short name (assigned by supplier)
6V Manufacturer's identification code
S Serial number (assigned by supplier)
Optional information (top):
This field contains customer specific information. The field remains
empty (as shown above) for neutral equipment.
Please note that:
• It is essential to replace the identification label if the
hardware is modified (or updated).
• Due to the hardware designation of such units the name of
the UCST template (*.cdu, *.ocu, *.cox etc.) cannot be read
from the label. The templates are defined by the product
number of the hardware and the corresponding SW as
defined in the chapter 9 "System and Ordering
Information".

Identification label “Function” The label specifies the function. For most units the function is defined by
level the unit hardware and the unit firmware, which is here a part of the
hardware. This type of label is typical for units (released with the
UMUX 1300/1100) without download of the ESW or without SW at all
(such as power supplies). The information on the label identifies the units
and provides detailed information on the build and change status of each
unit. Separate fields are reserved for optional customer specified data.
Figure 6-4: Example identification label of units without SW download

(LECA2)
F LECA2 XY O
P 12345678901234567
A 3.3072.052
98W40 D
M G01
L A01
97254356
E
S A
E
Legend:
Mandatory information:
A Product number (assigned by supplier)
D Delivery date
E Build state (assigned by supplier)
F Short name (assigned by supplier)
L Serial number (assigned by supplier)
M Serial number
Optional information:
O Customer ID or User ID
P Customer Product Identification
Please note that:
• It is essential to replace the identification label if the function
is modified (or updated).
• Due to the functional designation of such units, you can not
read the name of the corresponding UCST template (*.cdu)
directly from the label (short name plus last 3 figures of field A).
• The E fields in the figure above define the hardware and the
software.

Figure 6-5: Example identification label of units without SW

(POSUS)
6V MFR ID: 214414

S/N: 32802309
S
COZBU 110 106/1 1P

R1A/C 2P
98W28 10D
POSUS 32P
Legend:
10D Delivery date (format: yyWww)

EMC and safety label ("CE" The "CE" label is integrated into the product identification label of the
label) subrack. The "CE" label declares conformity with the European EMC
Directive 89/336/EEC for Electromagnetic Compatibility and the Directive
73/23/EEC for Safety.
Figure 6-6: Identification label with "CE" declaration
MFR ID: S/N:

6V S
201595 97987654
BFDBU 101 101/1 1P

R1A 2P
98W01 10D
BFD01 32P
Legend:
10D Delivery date (format yyWww)
Location of "CE" label The "CE" label is attached on top of the right side mounting flange of the
subrack.
The label is visible with mounted front cover.
Limitation of liability The UMUX equipment is intended for the installation in locations with
restricted access (rooms, enclosures, cabinets). Only authorised personnel
who have been instructed on safety rules and precautions as stated in the
respective user guides can access these locations.

All UMUX equipment in subracks with the "CE" label conform with the
European EMC Directive 89/336/EEC for Electromagnetic Compatibility
and the Directive 73/23/EEC for Safety, provided the equipment is
installed according to the instructions given with the applicable system
and unit user guides, in particular:
• the subracks and racks must be grounded to station ground.
• the front covers of the UMUX 1500 subracks have to be installed.
• the shields of all signal cables must be grounded or, if specifically
required, provide a ferrite core as specified.
• provision for safe equipment operation and the safety of people is
implemented as instructed for systems with remote and/or mains
powering.
Warning labels
"Hazardous voltages" Figure 6-7: Label "Hazardous voltages"
Interfaces and connection points with hazardous voltage are marked with
a corresponding warning label. Corresponding warnings for connection
points marked in this way are provided with the customer documentation
and can be summarised:
Hazardous voltages can cause danger to life!
• Before working on high power level interfaces and
connections, it is absolutely essential that the incoming
power supply line is disconnected so that the equipment is
no longer under power.
• Adhere to instructions provided with warnings!

"Laser radiation" Figure 6-8: Label "Laser radiation"
Interfaces and connection points with laser transmitters are marked with a
corresponding warning label. Corresponding warnings for connection
points marked in this way are provided with the customer documentation
and can be summarised:
Invisible laser radiation can cause damage to the eyes !
• Before working on interfaces and connections with laser
outputs, it is absolutely essential that the laser power is
turned off to avoid inadvertently staring into the laser beam.
• Adhere to instructions provided with warnings!
Electrostatic sensitive devices Figure 6-9: Electrostatic sensitive device
Systems and units with electrostatic sensitive devices are marked with a
corresponding warning label. The rules provided for the handling of
electrostatic sensitive devices have to be adhered to in order to minimise
the risk of damages and interferences.
Electrostatic sensitive device!
Adhere to instructions for the handling of electrostatic sensitive
device provided with the user guides!
Since almost any of the UMUX equipment relies on such components, this
label has been integrated into the product information labels.

ascom
System Specification 7
Functional specification
General System application
- Access multiplexing
- Traffic signal types : data and voice
- Multiplexing/demultiplexing : traffic signals
V5.x
CAS
VC-12, VC-3 / VC-4
- Bit-rates of traffic signals : nx64 kbit/s (n = 1 ...
31)
2 Mbit/s structured
and unstructured
STM-1
- Cross connecting : 2 Mbit/s and 64
kbit/s
DXC 1/1 and 1/0
- Transport : nx64 kbit/s (n = 1 ...
31)
2 Mbit/s
8 Mbit/s
STM-1 (optical and
electrical)
- Any mixture of above : up to subrack and
system capacity
Commissioning
- Traffic interfaces : modular hardware
- Functions : units and software
Traffic functions
Signals STM-1
- Termination : physical section
- Multiplex Section protection : with SYNIO
(MSP for
SYNIF/SYNIC is a
FUTURE OPTION)
SDH traffic signals

- Multiplexing/demultiplexing from/into : STM-1 according to
ITU-T G.707
for VC-12 and VC-3
- Termination : VC-12

Ascom System Specification
- Add and drop : VC-12

- Through connection : VC-12 and VC-3
- Cross connection : VC-12
- Protection VC-12 : Linear trail protection
SNC protection
(FUTURE OPTION)
8 Mbit/s signals
- Protection 8 Mbit/s : 1+1 physical section
protection
- Multiplexing/demultiplexing from/into : 4 2 Mbit/s signals
unstructured or
structured according
to ITU-T G.704
2 Mbit/s signals
- Protection 2 Mbit/s : 1+1 physical section
protection
SNCP/N and SNCP/I
- Adaptation : structured,
synchronous and
unstructured signals
- Termination and monitoring : structured,
synchronous signals
- Multiplexing/demultiplexing of VC-12 from/into : STM-1 signals
- Cross connection : structured and
unstructured
- Special functionalities : V5.x
PRA
64 kbit/s signals
- Cross connection : DXC 1/0
Protection Section protection : Implemented by
transmission unit
Subnetwork protection for signals
- SNCP/N : 2 Mbit/s (P12s)
(with PBUS units
only)
- SNCP/I : 2 Mbit/s and 64
kbit/s
(P12x, P0 and P0-nc)
(with PBUS units only)
Linear trail protection : VC-12
Multiplex Section protection STM-1 : with SYNIO
(MSP for
SYNIF/SYNIC is a
FUTURE OPTION)

Monitoring traffic signals Performance monitoring : ITU-T-G.826

Monitoring points
- PDH : 2 Mbit/s traffic
signals
SULIC-NTU
(64 kbit/s TS
required)
UNIDA
(64 kbit/s TS required)
- SDH : VC-12
VC-4
RS and MS in STM-1
Trail monitoring with TTI

- PDH : 2 Mbit/s (ECC mode)
- SDH : VC-12
VC-4
RS in STM-1
V5 functions V5 protocol processing

- Function unit : PCONV
- V5.1 interfaces : 4
- Max. number of V5.2 link accesses : 2
- Capacity of PSTN user ports V5.2 : 240
- Capacity of ISDN BA user ports V5.2 : 112
incl. processing of p- and f-data
- Integrated IFs G.703 for V5 link access : 2 x 2 Mbit/s
- Function unit : PCON2

- Max. number of V5.2 link accesses : 8
- Capacity of PSTN user ports V5.2 : 480
- Capacity of ISDN BA user ports V5.2 : 224
incl. processing of p- and f-data
- Access for PSTN user ports : selectable for
V5
MCAS
PSTN User Ports

- PHLC1 : 60 sub. line IFs
ISDN-BA
- ISBUQ (2B1Q) : 8 ISDN BA
- ISBAT (4B3T) : 8 ISDN BA
Diagnostic functions Function unit : COBUV and COBUX

Test purposes : Channel
performance
Signal delays

Conference functions Function unit : COBUV

- Data type : 64 kbit/s incl. CAS
- Processing for CAS signalling : bit-wise AND of all
input signalling
- Max. number of participants : 64
- Max. number of conferences : 21
- Proposed max. number of participants : 8
Parameters : settable per
participant
- Attenuation of input signal : 0, 3, 6 and 9 dB
- Attenuation of output signal : 0, 3 dB
- Noise suppression : selectable
3 steps
Synchronisation
General Basic configurations : PETS
: PETS and SETS
: SETS only (PETS
locked to SETS)
Selection algorithm
-QL based : QL 1...15
-Priority based : 1...7/8 (1 highest)
-Switching : revertive
-Configurable Hold off time : 0-60 s
-Configurable wait to restore time : 0-600 s
PETS - Timing sources for PETS

- Traffic signals (up to 4) : 2 Mbit/s terminated
: 2 Mbit/s monitored
: 64 kbit/s signals
- External 2048 kHz sources (ITU-T G.703) : 2 (ESI-1 … 2)

- Internal source : ± 50 ppm
- Filter for clock recovery selectable : high Q

: low Q
Jitter transfer characteristic (high Q)
- Max. Bandwidth : 2.5 Hz
- Jitter gain : < 0.5 dB
Jitter transfer characteristic (low Q)

- Max. Bandwidth : 40 Hz
- Jitter gain : < 0.5 dB
Synchronisation outputs (ESO)

- Number : 3 (ESO-1 … 3)
- Squelching configurable per : - source selected
- QL of NE (1...15)
Equipment protection : requires two control

units

SETS - Architecture : see figure below
In ESO-4/ESO-SDH
(T4) non SETS locked
mode, Select A and
Select B may share
the same timing
sources, but they are
autonomous in terms
of selection.
Sync Sources:
SDH (T1)
STM-1
Select A
PDH (T2) Select C
2 Mbit/s
2MHz
ESI-1 (T3)
2 MHz
Squelch

Select B (PLL)
SBUS, STM-1
Internal SETS
- Optimised for 2048 kbit/s hierarchy : Option 1, ITU-T G.813

- Accuracy under free-running conditions : better than ± 4.6 ppm
- Minimum pull in range : ± 4.6 ppm
- Wander generation in locked mode : Table 1, 2, 3 /G.813

Figure 1, 2 /G.813
- Wander tolerance : Table 8, 9, 10 /G.813
Figure 5, 6, 7 /G.813
- Jitter tolerance for 2048 kHz, 2048 kbit/s : Figure 9/G.813
- Noise transfer characteristic

- Min Bandwidth : 1 Hz
- Max. Bandwidth : 10 Hz
- Gain in the pass band : lower than 0.2 dB
- Short-term phase transient response : Figure 12/G.813

- Long-term phase transient response : Figure 14/G.813
- Phase response to input signal interruption : G.813 §10.3
- Timing sources for SETS

- Traffic signals : STM-1 MS (T1)
2 Mbit/s terminated (T2)
2 Mbit/s monitored (T2)
- External 2048 kHz input (ITU-T G.703) : 1 ESI-1 (T3)

Synchronisation Output (ESO)

- Number : 1 ESO-4/SDH (T4)
- Mode of operation : - SETS locked
- Non SETS locked
- Squelching configurable per : - selected source
- QL of NE (1...15)
Synchronisation Selection Process (Select B) : Figure A.1/ETS 417-6-1
QL /SF hold off time : 0 to 60s
QL /SF wait to restore time : 0 to 720s
Equipment protection : requires 2 SYNIF or

SYNIC units in the
same SDH sector
(protection with
SYNIO is a FUTURE
OPTION)
Maintenance and Diagnostics Relevant Standard Document : ETS 300 417-6-1
Selection
- Auto-selection (SETS Select B/A, PETS): : § 4.12
(QL-enabled mode
corresponds to QL
based selection
algorithm
QL disabled mode
corresponds to
Priority based
selection algorithm )
Select A fix to Auto-
selection
- Forced free-run : SETS Select B, PETS
- Forced holdover : SETS Select B (only if
HO frequency
available)
Timing source (SETS Select B, Select A, PETS)

- Forced switch according to ETS 300 417-6-1 : § 4.11.2.2
- Manual switch : § 4.11.2.3
- Clear switch : § 4.11.2.1
- Set lockout : § 4.11.1.1
- Clear WTR : § 4.9
Status
- Timing Source : - QL
- Priority
- Available
- Failed
- Not supervised
- SETS Clock operation mode : - locked

- free-run
- holdover
- PETS Clock operation mode : (not applicable)

Fault management - SETS (STM-1 aggregate unit):

- Loss of External
Clock source
- Loss of clock source
PDH<X>/SDH<Y>
- Loss of SEC Timing
input
- Loss of ESO Timing
inputs
- SEC Source not
Primary
- ESO Source not
Primary
- SETS in Holdover
- SETS HW Failure
- SEC Source out of
limits
- PETS (COBU<X>):
- Loss of external clock
1, 2
- wrong impedance
external clock 1, 2
- Loss of clock source
PDH<X>
SSM and QL processing SSM transmission in SDH : S1 byte of STM-1 MS
SSM transmission in PDH : - any Sa bit of 2 Mbit/s

acc. to G.704
- Sa4 in bit of 2 Mbit/s

acc. to G.704,
UMUX1500
proprietary ECC
mode
Mapping of the QL in receive direction

SETS mapping table : override by QL 1 to
15 depending on
received QL
Mapping of the QL in transmit direction

SETS mapping table : By QL 1 to 15
depending on NE QL
Unit routing table, ESO : override by “Do not

use” (QL=15, SSI=0,
ESO = squelched)
depending on timing
source selected to
avoid network timing
loops
SETS, PETS timing source configuration : assignment of a fix QL

Management functions Configuration management : for NE and traffic

functions
Unit software
- Embedded Software (ESW) : most UBUS units
- SW download (for ESW) : PBUS units
SBUS units
new UBUS units
- Control of download : via EM
Performance management for : traffic signals and NE

Fault management
- Hardware failures : NE and units
- Failures and performance : traffic signals
Alarm generation and reporting

- Generation and severity : programmable
- Indication : local indicators
- Reporting : alarm lists
logbook
remote access
Inventory management : for hardware and

software
Real time clock : ± 50 ppm
Management tool and versions : UCST R5A

UNEM R5A
System control Basic control system : distributed processor

system
Central system control : dedicated unit with
master processor
Traffic units : local slave processors
Management Information Base (MIB) : control unit

- Configuration data : MIB
- Unit software (for units with download only) : MIB
Physical implementation of MIB : PCMCIA card

(removable)
Capacity of PCMCIA card : 8 MBytes
Protection of control unit : 1+1 (slots 11 and 12)

- Type of protection : hot standby
non-revertive
- MIB of redundant unit : permanently updated
- Control unit switch-over : automatic failure
driven and
UCST command
- Implications of the switch-over on traffic signals:
- automatic and UCST commanded switchover
- UBUS (UNIDA - UNIDA X.24) : short interruption
≤ 250 µs
- PBUS (LOMIF - LOMIF 2 Mbit/s transparent) : insertion of one 0-bit

corresponding to an
interruption of
≤ 488 ns
- removal of active control unit
- UBUS (UNIDA - UNIDA X.24) : interruption
≤ 4 ms
- PBUS (LOMIF - LOMIF 2 Mbit/s transparent) : insertion of 1 … 4 0-
bits corresponding to
an interruption of
≤ 1952 ns
Software system Unit software (ESW)

- PBUS, SBUS and some UBUS units : provided from EM via
software download
Units provided with the UMUX 1300 releases
mostly UBUS, exceptions !! : local firmware
Test and diagnostic functions System level

- Alarm system
- Alarm indicators : LED and relay
contacts
- Lists : NE fault list
logbook
- Inventory data : for hardware and
software system
Functional level
- Diagnostics : PETS, SETS
ESO SDH
protected cross
connections
U/PBUS usage
system control
ECC and OSPF router
Unit level
- Fault indicators : unit hardware and
traffic signals
- Test loops : unit specific
- State indication: : Traffic signals
- Performance monitoring : Traffic signals G. 826
(selected units)
Central diagnostic for traffic signal channels
- Function (implemented on COBU<X>) : Test signal generator
signal analyser
- Test signal
- Type : 8-bit pattern and
pseudo random bit
patterns
- Structure and bandwidth : n x 64 kbit/s and 2
Mbit/s unstructured
- Analyses
- 8-bit pattern : matching patterns
- Pseudo random bit pattern : performance
monitoring
channel delay
- Channel connection : via cross connect

Compatibility with other Compatible platform : UMUX

UMUX equipment Accommodation of existing units in subrack : traffic units UMUX
(provided released
for UMUX 1500)
Interfaces (applications based on the platform) : external traffic and
management
Synchronisation : SSI
(structured 2 Mbit/s
signals only)
Backward compatibility
- New units to existing systems : only if specified
- New front access connectors to existing system : not compatible
- UCST to existing systems : UMUX 1300
UMUX 1100(E)
DSL product family

Technical specification
Architecture
System System architecture : fully modular
open architecture
Implementation : configurable
according to
requirements
System control
- Control units : type COBU<X>
- Subsystems : MIB of the NE
PETS
Management Com
Control of BUS
access
Diagnostics
Conference functions
- Features and control units
- Diagnostics : COBUX, COBUV
- ECC : COBUX, COBUV
- SETS : COBUX, COBUV
- Conference function : COBUV
- UBUS highways
- 8 x 2 Mbit/s : COBUX, COBUV
- 4 x 2 Mbit/s : COBUQ, COBUL
- PBUS highways
-128 x 2 Mbit/s : COBUX 145
COBUV 137
COBUL
- 40 x 2 Mbit/s : COBUX 146
- 32 x 2 Mbit/s : COBUQ
Functional equipment protection : for

– system control
and PETS
– SETS
– power supply
Implementation of external interfaces : on removable units
Unit software (EWS) : down loaded
Compatibility to existing UMUX equipment : for traffic units and
functions
Configuration : software based
UCST and UNEM
PBUS Capacity : 128 x 2 Mbit/s

with and without
CAS
Logical structure : linear 128 x 2 Mbit/s
with and without
CAS
Physical structure : 32 x 16 Mbit/s
PBUS access and slot arrangement : non segmented
linear

UBUS Capacity : 8 x 2 Mbit/s

with and without
CAS
Logical structure : 2 sets of highways
each 4 x 2 Mbit/s
with and without
CAS
UBUS access and slot arrangement : 4 segments, non
linear, overlapping
highway sets
SBUS Capacity
- VC-4 terminating : 2 x STM-1 (63 x VC-12)
- Add and drop to/from STM-1 : VC-12 in 2 STM-1
segment
Logical structure : 63 x VC-12 (TU-12)
with and without
CAS
Physical structure : 2 sectors each with
4 x 8 x 19.44 Mbit/s
SBUS access and slot arrangement : linear in 2 sectors
pairs of slots
interleaved for MSP
Element Manager Element Manager : UCST R5A
Element Manager System : UNEM R5A
Management communication EOC

structures - Function unit : COBUV, COBUX
COBUQ
- Structure : proprietary multi-
path
based on SIFOX
- NE interface to EOC : SIFOX / F-interface
- EM(s) interface to EOC : SIFOX / RS-232 C
- Addressing : proprietary EOC
addresses
Bandwidth
- Mixed NEs UMUX 1100(E)/1300 and 1500 : 9600 bit/s
- NEs UMUX 1500 only up to : 19200 bit/s
ECC
- Function unit : COBUV, COBUX
- Structure : proprietary multi-
path
based on OSPF
routing
- PDH ECC channels max. : 32
- Bandwidth PDH channels : 16 kbit/s (TS0
LOMIF/LOMI4)
64 … 1984 kbit/s
- SDH ECC channels max. : 8 with tunnelling in
OSI DCN (SDH)

- Bandwidth SDH channels : 192kbit/s, 576 kbit/s

- Total bandwidth PDH and SDH channels max. : up to 2048 kbit/s
- NE interface to ECC : internal (cross
connect)
- EM(S) interface to ECC : QX-interface
(10BaseT)
F-interface (RS-232C)
Tunnelling for OSI
DCN
- Addressing : IP addresses
LAN (WAN)
- Type : Ethernet 10BaseT
- NE interface : QX-interface
- EM(S) interface : Ethernet 10BaseT
Q-BUS
- Structure : local bus
based on RS-485
- NE interface to Q-BUS : Q1-interface
- EM(s) interface to Q-BUS : RS-232 C via
converter RS-232 C /
RS-485
- Addressing : proprietary EOC
addresses
- Bandwidth
Q1-master interface
based on RS-485
- Implementation : UMUX 1500 only
- Use : Access to remote Q-
BUS via UMUX 1500
- Interface UMUX 1500 : Q1-master interface
- EM(S) interface : any
Routing IP routing
- Function unit : COBUX, COBUV
COBUQ, COBUL
- Routing protocol : OSPF V2.0 (RFC
2178)
- Router interfaces
- COBU<X> : F, Q1, QX,
- COBUX, COBUV, COBUQ : OSI tunnel
- COBUX, COBUV : PDH and SDH ECC
(not available with
COBUQ, COBUL)
OSI routing
COBUQ
- Routing protocol : IS-IS (level 1)
- Router interfaces : QX, OSI tunnels
HDLC routing
COBUQ, COBUL

- Routing protocol : proprietary

- Router interface : Q1-interface
Cross connections and delays

PBUS cross connect Type : non-blocking
structured and non
structured signals
Capacity
- 2 Mbit/s equivalents max. : 128 x 2048 kbit/s
- 64 kbit/s equivalents max. : 4096 x 64 kbit/s
Protection between access ports

- Bi-directional (quality criteria for input selection) : 2 Mbit/s
nx64 kbit/s (n = 1 ...
31)
- Control : status monitor UCST
Broadcasting : 2 Mbit/s
nx64 kbit/s (n = 1 ...
31)
Delay assignment
- Single TS and consecutive TS n x 64 kbit/s : minimum delay
- Non consecutive TS n x 64 kbit/s : constant delay
Traffic signal delays PBUS and Delays (access points cross connect)
UBUS - Unstructured signals P12x (PBUS - PBUS) : min. 14 µs
max. 48 µs
- Structured signals P12s (PBUS - PBUS)
- Minimum delay : min. 21 µs
max. 380 µs
- Constant delay : min. 21 µs
max. 501 µs
- Structured signals P12s (PBUS - UBUS)
max. 378 µs
max. 499 µs
- Structured signals P12s (UBUS - PBUS))
max. 248 µs
max. 369 µs
- Structured signals P12s (UBUS - UBUS)
max. 246 µs
max. 367 µs

Traffic signal delays SBUS and Delays (2 Mbit/s traffic signal reference)
PBUS - TM (X = F, O, C):
- SYNAM → SYNI<X> → SYNI<X> → SYNAM : typ. 90 µs
- ADM:
- SYNIO <m> IF_1 → SYNIO <m> IF_2 : typ. 16 µs
- SYNIF (SYNIC) <m> → SYNIF (SYNIC) <n> : typ. 16 µs
Signal Interfaces
Traffic interfaces Physical implementation of traffic interfaces : dedicated units
Types
- Units with access to UBUS : UBUS units
- Units with access to PBUS : PBUS units
- Units with access to SBUS : SBUS units
Characteristics and specifications : refer to unit

descriptions
Units implemented Units available with UCST R5A : refer to chapter 9

"System and
ordering
information"
Synchronisation interfaces ESI-1:

inputs - Synchronisation system : SETS/PETS
- Frequency : 2048 kHz
- Galvanic isolation from NE and battery : yes
- Impedance : configurable
- According ITU-T G.703, section 10 : 75 Ω or
120 Ω (R2A)
- High impedance : | Zin | ≥ 3 kΩ
ESI-2:
- Synchronisation system : PETS
- Impedance
- According ITU-T G.703, section 10 : 75 Ω
Resistibility to surge voltages ESI-1 and ESI-2 : 1.2/50 µs impulses
U = ±100 V
Insulation signal pins of ESI-1 and ESI-2
- ECLK2MIN<X> : 1 kV/50 Hz/60 s
- ECLK2MGUARD<X> to earth : 1 kV/50 Hz/60 s
Synchronisation interfaces ESO-1:

outputs - Synchronisation system : PETS
- Galvanic isolation from NE and battery : yes (R2A)
- Impedance according ITU-T G.703, section 10 : 75 Ω
ESO-2 and ESO-3:

- Galvanic isolation from NE and battery : no

ESO-4:
- Synchronisation system : SETS
120 Ω (R2A)
Resistibility to surge voltages ESO-1 … ESO-4 : 1.2/50 µs impulses
U = ±100 V
Insulation signal pins
- ESO-1 and ESO-4 : (R2A)
- ECLK2MOUT<X> : 1 kV/50 Hz/60 s
- ECLK2MGUARD<X> : 1 kV/50 Hz/60 s
- ESO-2 and ESO-3 : no galvanic
separation
Alarm interfaces Alarm inputs:

- Number : 4
- User defined names for input signals : yes
- Active signal level : configurable via EM
- active ground
- active open.
- Thresholds for detection
- Reference : positive leg of the
battery (earth)
- "Ground state“ range : -8 V ... +75 V
with respect to
reference
- "Open state“ range : -75 V … -16 V
with respect to
reference
- Load equivalent of input @ voltage of -16 V : a current sink of at
least 1 mA with an
impedance not
higher than 20
kOhm
- Surge immunity : to 1.2/50µs surge
impulses with U =
±2000 V
- Physical implementation : COBU<X>
Alarm outputs:
- Number : 2
- Type : solid state relays
double throw
overload protected
- Use : alarm status of NE
- "Urgent Alarm“
- "Non-urgent
Alarm“
- Current admissible : < 50 mA
- Resistance : < 50 Ohm
- Open contact leakage current @ 75V : ≤ 100µA

- Open contact max. voltage : 150 V

- Immunity
- Surges
- Voltage (any alarm output lead to earth) : to 1.2/50µs surge
impulses with U =
±2000 V
- Current (between the alarm output leads) : to 0.5A applied for
10µs
- Insulation (any alarm output lead to earth) : 1 kV/50 Hz/60 s
Conditions at the alarm outputs in case of
- power fail
- "Urgent Alarm" output : active
- "Non-urgent Alarm" output : not active
- inactive control unit
- "Urgent Alarm" output : not active
Management interfaces F-interface

- Application Layer : proprietary layer 7
- Transport Layer : TCP
- Network Layer : IP
- Data Link Layer : PPP
- Physical Layer : RS-232
Q1-interface
QX-interface
- Data Link Layer : IEEE 802.3 Ethernet
- Physical Layer : 10BaseT
OSI-tunnel for TCP/IP management com. : Virtual LAN

via COBU<X>
Q1-master interface
- Application : Remote Q-bus
master access via
UMUX 1500
Access to SOH of STM-1 - Access to SOH bytes : via UBUS

n x 64 kbit/s
- Order wire (EOW) and user channel : E1, E2 and F1
- RS DCC : D1 … D3
- MS DCC : D4 … D12

Power interfaces
DC interface Power supply interface according : ETS 300 132-2
interface A
Nominal voltages
- -48 VDC, voltage range : -40.5 VDC … -57 VDC
Maximum continuous current : 10 A
Recommended fusing : 10 A slow blow
Power consumption Maximum admissible peak power consumption

- -57 VDC : 570 W
- -72 VDC : 720 W
Internal power supply Power conversion : dedicated units
Operation of power supply units

- Parallel operation of units : load sharing
- Number of units operating in parallel : ≤5
Protection and load sharing : n + 1 (n = 0 ... 4)
Power dissipation Maximum power dissipation : depending on traffic

interfaces
Maximum admissible power dissipation
- Natural air convection (for specified ambient) : 150 W
- Forced air convection or air conditioning : 720 W
provided specified
ambient conditions
are fully met.
Subrack
Construction Card cage for UMUX units : 19-inch practice
Modularity : subrack
cable tray
heat deflection shield
fan unit
Installation into racks
- 19 inch : direct
- ETSI (applicable standard ETS 300 119-4) : with adapters
Basic construction : metallic

- Sides and rear : sheet metal
- Top and bottom : perforated sheet
metal
- Front : front cover
Connection of signal and power cables

- Power supply : integrated connector
- Shields of signal cables : grounding bars in
front
- Cable installation and strain relief : matching cable tray

Capacity and slots Slots

- Number of slots : 21
- Slot width : 20.32 mm
4 TE
Segmentation of access
- UBUS : 21 slots
- PBUS : 20 slots
- SBUS : 14 slots
Allocation of units to slots : flexible

slot 11 dedicated
FANUV fan unit

Construction Unit construction : 19-inch practice
1 HU (44.45 mm)
- 19-inch : direct
- ETSI (applicable standard ETS 300 119-4) : with adapters
Connection of signal and power cable : front access
Specification Number of fans : 3

Operation : temperature
controlled
- low speed
- high speed
Temperature control of the fan speed
- low speed : < 25 °C
- high speed : > 40 °C
Performance
- low speed (free blowing)
- air velocity : 0.8 m/s
- transported air volume : 0.053 m3/s
- high speed (free blowing)
Alarm interface Types

- Optical indicators:
- Operation control : 1 green LED
- Failure indicator : 1 red LED per fan
- Electrical contacts:
- Type : double throw relay
contacts
- Current : < 200 mA
Connection to COBU<X> : proprietary cable
Power supply Supply circuit : battery

Voltage range
- nominal : -48 VDC
- range : -39.5 VDC … -75 VDC

Power consumption (-48 VDC battery)

- low speed (all fans operating, T < 25 °C) : < 80 mA
- high speed (all fans operating, T > 40 °C) : < 220 mA
Connection to UMUX subrack : proprietary cable
EMC
Product family standard Public Telecommunication network equipment : EN 300 386-2 V1.1.3
Emission Interference voltage 0.15 MHz ... 30 MHz

- power supply port : EN 55022, class B
- traffic signal ports : Amendment to CISPR
22, class B
Radiated field 30 MHz ... 1000 MHz : EN 55022, class B
Immunity Electromagnetic field

80 MHz ... 1000 MHz, level 2, 3 V/m : IEC 1000-4-3
Conducted common mode HF disturbance

150 kHz ... 150 MHz,
modulated 1 kHz 80% AM, 3 V : IEC 1000-4-6
Fast transients/bursts : IEC 1000-4-4

- On primary supply input (C/DN) : 1 kV
- On signal cables (capacitive clamp) : 0.5 kV
Surge immunity
- Traffic and control ports : EN 300 386-2 and
ITU-T K.20
- Power supply interface : IEC 1000-4-5
- Common mode : 1 kV
1.2/50 µs (8/20µs)
- Differential mode : 0.5 kV
1.2/50 µs (8/20µs)
ESD Electrostatic Discharge : IEC 1000-4-2

- contact discharge : 6 kV
- air discharge : 8 kV
Safety Safety according to : EN 60950 / IEC 950
Ambient conditions
Storage All equipment according to : ETS 300 019-1-1
class 1.2
Temperature range : -25°C ... +55°C
Humidity : according to class
1.2
Biological and chemical active substances : Not specified

Transport All equipment according to : ETS 300 019-1-2

class 2.2
Temperature ranges
- ambient air for unventilated enclosures : -25°C .. +70°C
- ambient air for ventilated enclosures or outdoor : -25°C .. +40°C
Humidity : according to class
2.2
Vibration random Acceleration Spectral Density
- ASD @ 10-200 Hz : 1.0 m2s-3
- ASD @ 200-2000 Hz : 0.3 m2s-3
Operation All equipment according to : ETS 300 019-1-3

class 3.2
Temperature range system : -5°C ... +45°C
(for partly
temperature-
controlled locations)
Humidity : according to class 3.2
up to 95%, non-
condensing
Direct ambient temperature range PBUS units
- Range of operation : -20°C ... +85°C
- Compliant with specifications : 0°C … +70°C
Mechanical parameters
Dimensions 19-inch subrack without front cover (W x H x D) : 482.6 x 308.2 x
279.7 [mm]
19-inch subrack with front cover (W x H x D) : 482.6 x 308.2 x 283
[mm]
Cable tray (W x H x D) : 482.6 x 87.1 x 240
[mm]
Heat deflection shield (W x H x D) : 482.6 x 87.8 x 237
[mm]
FANUV fan unit (W x H x D) : 482.6 x 43.6 x 230
[mm]
Construction and layout : 19-inch and ETSI

mounting practice
refer to figures
Weight 19-inch subrack with front cover (without units) : 7.430 kg

19-inch subrack without front cover (without units) : 6.440 kg
Cable tray : 0.870 kg
Heat deflection shield : 1.580 kg
FANUV fan unit : 2.420 kg
ETSI adapters 8 HU (set) : 0.360 kg
ETSI adapters 10 HU (set) : 0.450 kg
Weight of units : refer to unit
descriptions

Installation
Subrack, cable tray Construction and installation : 19-inch practice
Height of subrack and cable tray : 8 HU (= 355.6 mm)
Installation into ETSI racks : with adapters
Connection of signals Traffic signals (new UMUX units) : DIN 41 612

32 pins, rows a, c (b)
- Male connector : unit
- Connector cover : proprietary
- Coding keys : where applicable
- Latching system : yes
- Strain relief : grounding bar, cable
tray
Traffic signals (old UMUX units) : refer to UMUX 1300

description
Management interfaces (control unit)

- F-interface : SUBMINI D, 9 p./f.
- QX-interface : 10BaseT (RJ-45)
- Q1-interface : DIN 41 612
8 pins, rows a, c
latching system
tray
Auxiliary signals (control unit)

- Synchronisation inputs/outputs : DIN 41 612
8 pins, rows a, c
- Alarm inputs/outputs : DIN 41 612
8 pins, rows a, c
- Latching system and coding keys : yes
tray
EMC protection of signal interfaces

- Signal cables with shields : grounding bar of
subrack
- Signal cables without shields : toroidal core ferrite
Mechanical shock and vibration : ETS 300 019-1-3
Connection of power supply Subrack (internal access for power supply) : 3 pin FAST-ON type
connection
(cable provided with
subrack)
Cable tray (external access for power supply) : 3 pin WAGO
connector block
Dependability
Availability Mean accumulated down time (MADT)
traffic between any two 2 Mbit/s ports of 2 NE’s : < 10 min. per year
(excluding failures of
the transmission
media)

MTTF Calculated MTTF for all categories of failures

- Single unit : > 20 years
- Detailed MTTF figures per unit : refer to the unit
descriptions.
Predictions based on : MIL-HD BK-217F
MTTF values of operating systems are available on request.

ascom
Implementation and Application Notes 8

Configuration of the subrack
Summary of limiting factors
for unit implementation
General all units In order to avoid functional limitations and congestions on the
UMUX 1500 buses, you should adhere to some rules for the
implementation of units:
• Converted power available:
It is not possible to implement a unit (without the risk of a system
crash) if the remaining amount of converted power is insufficient (i.e.
smaller than the maximum power consumption of the unit to be
implemented).
In such cases, the number of power converter units (POSUS) has to be
increased. The UCST shows an indicator which displays the present
power requirements of the units configured in the subrack.
• Number of free slots in the subrack:
It is not possible to implement a unit if the required number of
consecutive free slots (1 ... 3) is not available.
• Equipment protection:
Depending on the unit and the protected function there are some
rules to follow if you plan to implement equipment protection. This
affects mainly:
− Protection of the control unit
− MSP with the SYNIO
− SETS protection with the SYNIF/SYNIC
• Bus access:
Each of the 3 UMUX buses (PBUS, SBUS and UBUS) provides its
particular structure and capacity. Depending on the bus the access to
the bus is varying with the slots of the subrack.
It is highly recommended that you follow the rules for unit
implementation as outlined in the next paragraphs. This procedure
ensures the optimum system use and avoids system reconfiguration due
to later implementation of new units and functions.

Ascom Implementation and Application Notes
Synoptic overview Tab. 8-1: Limiting factors for unit implementation UMUX 1500
Limiting factor Applies for ...
PBUS Units UBUS Units SBUS Units Control Units Power Units
Slot number No access in slot UBUS access of Access in slots Operation in slot No limitation 1)
21. 1) the slot. 1) 2-9 and 15-20 11 (and 12) only.
1)
only.
Number of accessed Up to the UBUS structure Up to the Dedicated PBUS No limitation 1)

PBUS, UBUS or SBUS maximum of 32 x can limit UBUS maximum of 4 highway for the
highways 4 highways (each access. Refer to SBUS lines in Control Unit
2 Mbit/s with implementation sectors A and B (diagnostics etc.)
signalling). notes. (1 line common)
General MS and SETS Backup unit If possible, first

protection operates in slot 12 implement the
require the only. POSUS in slot 21.
use of
predefined
slots.
4) 4) 4) 4)
Converted power No limitations 1)
available POSUS 2)
Power available from Independently of the power supply voltage you must fuse the external -48 VDC supply for 10 A of
primary -48 VDC continuous current (Refer also to power dissipation).
supply
Power dissipation The maximum total power dissipation per subrack (without forced cooling) must not exceed 150 W. You
must implement forced cooling with the FANUV unit if
- the power dissipation in the subrack is higher than 150 W
- you operate units with a power dissipation exceeding 15 W per slot
- the UMUX 1500 is operated in environments with higher air temperatures than specified
Number of You can implement a unit only if the number of consecutive free slots is greater or equal to the unit width
consecutive free (this is a mechanical limitation).
slots
1)
Slot 11 is reserved for the control unit. With optional protection of
the control unit, slot 12 is reserved for the backup control unit.
2)
Power taken directly from the -48 V supply does not load the POSUS.
3)
Not applicable.
4)
Add a POSUS if
− you want to implement equipment protection.
− the remaining available power is less than the totalled worst
case power consumption of all units.

Control units and power supply

Control Units If the implementation of a redundant control unit is considered, the slots
11 and 12 are reserved for control units.
Power supply The power supply unit POSUS fits any slot of the subrack of the UMUX
1500. For the implementation of power supply units consider the following:
• Required converted power
Depending on the number and the type of units implemented, the
capacity of 1 power supply unit might not be sufficient. In these cases,
you must implement additional power supply units.
• Equipment protection
The degree of power supply protection is largely variable depending
requirements and system application. You can add additional power
supply units for equipment protection.
The UCST shows an indicator that displays the present power
requirements based on the power consumption of the units configured in
the subrack and the power provided by the power supply units.
UBUS
UBUS structure In order to provide maximum flexibility for the UBUS access, the
UMUX 1500 UBUS structure is optimised for load distribution.
The UBUS of the UMUX 1500 has a capacity of 16 x 2 Mbit/s. The odd
numbered highways carry the traffic signals and the even numbered
highways the signalling of the preceding odd numbered highway. The
total UBUS capacity for traffic signals is therefore 8 x 2 Mbit/s,
independently of whether CAS signalling is used or not.
The UBUS of the UMUX 1500 is divided into 2 sets of 8 highways each.
The highways 1 to 8 serve the slots to the left and the highways 9 to 16
serve the slots to the right, with an overlapping zone in the middle. The
structural layout of the UBUS highways of the UMUX 1500 is different
from the layout implemented with the UMUX 1300 (refer to the figure
below). This results in differences between the 2 UMUX systems for
highways accessible vs. slot number. The main differences are due to:
• 21 slots are connected to the UBUS
• Cross over within each set of highways
• 6 slots with access to all highways (slots 6 - 10)
• 4 segments of slots (S1 - S4) with different highway access are
implemented
The UBUS layout provides an equal distribution of the UBUS access among
the slots of the UMUX 1500 subrack. Additionally it helps to prevent the
blocking of free slots due to units with limited bus access.

Figure 8-1: Structure of the UBUS vs. slots of the UMUX 1500
subrack
UBUS highways vs slots of the UMUX 1500 subrack
Highways 9 - 16
Highways 1 - 8
5 (+ 6) 1 (+ 2) 9 13 (+ 14)
7 (+ 8) 3 (+ 4) 15 (+ 16)
11
3
1 (+ 2) 5 (+ 6) 9 (+ 10)
13
5
3 (+ 4) 7 (+ 8) 11 (+ 12)
15
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
S1 S2 S3 S4
Please note that:

• The highways reserved for signalling (even numbered) are
not available for traffic signals (the highway structure for
CAS signalling is included but not shown in the figure
above).
• The control units provide access to UBUS highways as
follows
– COBUQ/COBUL: Highways 1 … 8
– COBUX/COBUV: Highways 1 … 8 and 9 … 16
• The UBUS units are released for the UMUX 1500
independently from the control unit COBU<X>. The system
implementation of these units depends however on the
COBU<X> (see next paragraph).
• Although the UCST allows you to implement a particular
UBUS unit in the sector S3, the slots 11 … 16 may or may
not allow you to operate (cross connect) the unit with the
COBUQ/COBUL. This is due to the structure of the UBUS and
the hardware defined access of the UBUS unit to the UBUS
highways.
UBUS access There are a few additional limitations for the implementation of units with
UBUS access:
• Slot number:
− The special layout of the UMUX 1500 UBUS implementation has to
be considered when inserting UBUS units. All 16 highways are
accessible from slots 11-16, 8 highways are accessible from all
other slots (1-10, 17-21).

− For several of the UBUS units, operation in slots 17-21 is not

possible since they cannot be addressed in these slots.
• Capacity of the UBUS:
The number of timeslots and highways available on the UBUS is
reduced with each UBUS unit connected. Depending on the unit
implementation on a segment, free slots might become unavailable for
further UBUS units due to highway congestion. This becomes quite
evident if you implement aggregate units such as the TUNOP, seizing
four highways at a time.
A new unit cannot access timeslots or highways already occupied by
other units.
You can inspect the present highway usage and connection points on
the UBUS via the dialogue Bus Usage à UBUS. The dialogue shows
the currently accessed UBUS highways and corresponding connection
points. The highways with even numbers carry the signalling of the
preceding odd numbered highway.
• Control Units:
No traffic units can be operated in the slot(s) reserved for the Control
Unit (slot 11 or slots 11and 12 for systems with redundant control
unit). If you do not plan to implement a backup for the system control,
you can use slot 12 for other UBUS (or PBUS) units.
Depending on the control unit, the UBUS access differs.
Tab. 8-2: BUS usage and available PBUS capacity vs. control units
Control Unit PBUS highways UBUS highway access
Name PHAU Highways Hwy.s 1 … 8 Hwy.s 9 … 16

available slots 1 … 16 slots 11 … 21
COBUV 137 8 128 Yes Yes
COBUX 145 8 128 Yes Yes
COBUQ 144 4 32 Yes No
COBUL 215 4 128 Yes No
UBUS units and UMUX 1500 Please consider the following:

• Depending on the selected unit, a UBUS unit might block a complete
set of highways (4 x 2 Mbit/s).
• Some of the UBUS units feature only access to subsets of the
highways, which means, that such units cannot use the remaining
capacity on other highways.

• Due to a limited addressing range, it is not possible to operate some of

the units in the slots 17 to 21. For details on the UBUS access, refer to
the table “Summary of UBUS access of units”.
Selection of UBUS highways With the UMUX 1500, you can choose between an automatic mode and
and connection points an expert mode to select highways and connections points on the UBUS.
Automatic mode With this mode the traffic from/to the UBUS is automatically cross
connected. The EM does not provide dialogues for the definition of UBUS
highways and 'connection points'. An auto-configurator automatically
assigns the UBUS highways and connection points required in the
background.
For optimum performance of the auto-configurator adhere to the
following rules for unit implementation of UBUS units:
Tab. 8-3: Rules for the implementation of UBUS units
Assignment of Aggregate IF Tributary IF

UBUS units
Priority 1 2 3 4 1 2 3 4
Subrack S4 S3 S1 S2 S2 S1 S3 S4
Where S1 ... S4 designs the UBUS segments of the UMUX 1500 as follows:
Segment Slots
S1 1 ... 5
S2 6 ... 10
S3 11 ... 16
S4 17 ... 21
Adhere to the following complementary rules:

• Do not mix "aggregate" and "tributary" units within a segment.
• Implement the "tributary" units in the slots to the left of COBU<X>.
• If possible, implement the "aggregate" units in the slots to the right of
COBU<X>.
Expert mode The EM(S) provides an expert mode for cross connecting traffic from/to
the UBUS. The expert mode allows you to select the UBUS highways and
set connection points (64 kbit/s TS) on the highways. Setting connection
points manually allows you to use the UBUS capacity optimally.
You can inspect the present highway usage and connection points on the
UBUS via the dialogue Bus Usage → UBUS. The currently accessed UBUS
highways and corresponding connection points are graphically
represented. The highways with even numbers carry the signalling of the

Summary of UBUS access of The table below shows this relationship between the UBUS highways of
units the COBUV/COBUX and the UBUS access of units released for the
UMUX 1500.
Tab. 8-4: Summary of UBUS highway access for the COBUV/COBUX

(UCST R5A)
UBUS access COBUV Addr. Highways Highways Highways Width Remarks

COBUX slots 1…7 1 … 15 9 … 15
Template Name >16 S1 S2 S3 S4 [Slots]
ALCAR 804 ALCAR - n.a. n.a. n.a. n.a. 1 No highway access
EXBAT 401 EXBAT - 5, 7 1, 3 9, 11 n.a. 1

EXLA3 361 EXLA3 - 5, 7 1, 3 9, 11 n.a.
EXLA6 352 EXLA6 - 5, 7 1, 3 9, 11 n.a. 1
EXLAN 342 EXLAN - 5, 7 1, 3 9, 11 n.a. 1
EXLAN 343 EXLAN ü 5, 7 1, 3 9, 11 13, 15 1
EXLIC 451 EXLIC - 5, 7 1, 3 9, 11 n.a. 1
GECOD 371 GECOD - 5, 7 1, 3 9, 11 n.a. 1

GECOD 372 GECOD - 5, 7 1, 3 9, 11 n.a. 1
HIRAC 810 HIRAC ü 5, 7 1, 3 9, 11 13, 15 1
ISBUQ 109 ISBUQ ü 1, 3, 5, 7 1, 3, 5, 7 1 - 15 9, 11, 13, 15 1

ISBUQ 130 ISBUQ ü 1, 3, 5, 7 1, 3, 5, 7 1 - 15 9, 11, 13, 15 1
ISBUT 110 ISBUT ü 1, 3, 5, 7 1, 3, 5, 7 1 - 15 9, 11, 13, 15 1
LECAF 070 LECAF ü n.a. n.a. n.a. n.a. 1 No highway access

LECA2 050 LE2UA ü 1, 3, 5, 7 1, 3, 5, 7 1 - 15 9, 11, 13, 15 1 Aggregate IF
LE2Q2 244 LE2UA ü 1, 3, 5, 7 1, 3, 5, 7 1 - 15 9, 11, 13, 15 1 Aggregate IF
MAGIC 317 - ü n.a. n.a. n.a. n.a. 1 No highway access

MEGIF 261 MEGIF - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1 Aggregate IF
MEGIF 262 MEGIF ü 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 9, 11, 13, 15 1 Aggregate IF
NEMCA 311 NEMCA - 5, 7 1, 3 9, 11 n.a. 1

NEMCA 312 NEMCA - 5, 7 1, 3 9, 11 n.a. 1
NEMGE 315 NEMGE - 5, 7 1, 3 9, 11 n.a. 1


COBUX slots 1…7 1 … 15 9 … 15
PHONE 324 PHONE ü 5, 7 1, 3 9, 11 13, 15 1
RIGEN 241 RIGEN ü n.a. n.a. n.a. n.a. 2 Fits any slot 1 ... 20
except 11 (and 12)
except 11 (and 12)
SIFOX 381 SIFOX - 5, 7 1, 3 9, 11 n.a. 1

SIFOX 382 SIFOX - 5, 7 1, 3 9, 11 n.a. 1
SUBAT 461 SUBAT - 5, 7 1, 3 9, 11 n.a.
SUBLA 328 SUBLA ü 5, 7 1, 3 9, 11 13, 15 1

SUBLA 334 SUBLA ü 5, 7 1, 3 9, 11 13, 15 1
SUBLA 336 SUBLA ü 5, 7 1, 3 9, 11 13, 15 1
SUBL6 327 SUBL6 ü 5, 7 1, 3 9, 11 13, 15 1
SUBL6 335 SUBL6 ü 5, 7 1, 3 9, 11 13, 15 1
SUBUK 333 SUBUK ü 5, 7 1, 3 9, 11 13, 15 1
SULIC 391 SULIC - 5, 7 1, 3 9, 11 n.a. 1

SULIC 392 SULIC - 5, 7 1, 3 9, 11 n.a. 1
SULIC 396 SULIC ü 5, 7 1, 3 9, 11 13, 15 1
SULIS 393 SULIS - 5, 7 1, 3 9, 11 n.a. 1
SYNIO 165 SYNIO ü 1, 3, 5, 7 1, 3, 5, 7 1, 3, 13, 15 9, 11, 13, 15 For SOH data only!
SYNIF 164 5, 7, 9, 11
SYNIC 118
TUNEL 481 TUNEL - n.a. 1 Aggregate IF

SbU 1, 2 1, 3 5, 7 1, 3, 13, 15
SbU 3, 4 5, 7 1, 3 5, 7, 9, 11
TUNOF 384 TUNOF ü n.a. n.a. n.a. n.a. 1 No highway access
TUNOL 299 TUNOL ü 1 Aggregate IF
SbU 1, 2 1, 3 5, 7 1, 3, 13, 15 9, 11
SbU 3, 4 5, 7 1, 3 5, 7, 9, 11 13, 15
TUNOP 292 TUNOP - 1, 3 5, 7 5, 7, 13, 15 n.a. 1 Aggregate IF
TUNOS 293 TUNOS - n.a. 2 Aggregate IF
SbU 1, 2 1, 3 5, 7 1, 3, 13, 15
SbU 3, 4 5, 7 1, 3 5, 7, 9, 11
SbU 1, 2 1, 3 5, 7 1, 3, 13, 15
SbU 3, 4 5, 7 1, 3 5, 7, 9, 11
ULCAS 471 ULCAS - 5, 7 1, 3 9, 11 n.a. 1
UNIDA 431 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1

UNIDA 432 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1
UNIDA 433 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1


COBUX slots 1…7 1 … 15 9 … 15
UNIDA 434 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1

UNIDA 435 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1
UNIDA 436 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1
UNIDA 437 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1
UNIDA 438 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 9, 11, 13, 15 n.a. 1
The table disregards the signalling highways (even numbered

highways). With the UMUX 1500 the signalling highways are
always assigned to their respective traffic highway and cannot
be used for other purposes.
Although the UCST allows you to implement a particular UBUS unit in the
sector S3, the slots 11 … 16 may or may not allow you to operate (cross
connect) the unit with the COBUQ/COBUL. This is due to the structure of
the UBUS and the hardware defined access of a UBUS unit to UBUS
highways. The table below shows this relationship between the UBUS
highways of the COBUQ/COBUL and the UBUS access of units released
for the UMUX 1500.
Tab. 8-5: Summary of UBUS highway access for the

COBUQ/COBUL (UCST R5A)
UBUS access COBUQ Addr. Highways Highways Highways Width Remarks

slots 1…7 1 … 15 9 … 15
ALCAR 804 ALCAR - n.a. n.a. n.a. n.a. 1 No highway access
EXBAT 401 EXBAT - 5, 7 1, 3 n.a. n.a. 1

EXLA3 361 EXLA3 - 5, 7 1, 3 n.a. n.a.
EXLA6 352 EXLA6 - 5, 7 1, 3 n.a. n.a. 1
EXLAN 342 EXLAN - 5, 7 1, 3 n.a. n.a. 1
EXLAN 343 EXLAN ü 5, 7 1, 3 n.a. n.a. 1
EXLIC 451 EXLIC - 5, 7 1, 3 n.a. n.a. 1
GECOD 371 GECOD - 5, 7 1, 3 n.a. n.a. 1

GECOD 372 GECOD - 5, 7 1, 3 n.a. n.a. 1
HIRAC 810 HIRAC ü 5, 7 1, 3 n.a. n.a. 1
ISBUQ 109 ISBUQ ü 1, 3, 5, 7 1, 3, 5, 7 1, 3, 5, 7 n.a. 1

ISBUQ 130 ISBUQ ü 1, 3, 5, 7 1, 3, 5, 7 1, 3, 5, 7 n.a. 1
LECAF 070 LECAF ü n.a. n.a. n.a. n.a. 1 No highway access

LECA2 050 LE2UA ü 1, 3, 5, 7 1, 3, 5, 7 1, 3, 5, 7 n.a. 1 Aggregate IF


slots 1…7 1 … 15 9 … 15

LE2Q2 244 LE2UA ü 1, 3, 5, 7 1, 3, 5, 7 1, 3, 5, 7 n.a. 1 Aggregate IF
MAGIC 317 - ü n.a. n.a. n.a. n.a. 1 No highway access
MEGIF 261 MEGIF - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1 Aggregate IF

MEGIF 262 MEGIF ü 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1 Aggregate IF
NEMCA 311 NEMCA - 5, 7 1, 3 n.a. n.a. 1

NEMCA 312 NEMCA - 5, 7 1, 3 n.a. n.a. 1
NEMGE 315 NEMGE - 5, 7 1, 3 n.a. n.a. 1
PHONE 324 PHONE ü 5, 7 1, 3 n.a. n.a. 1
except 11 (and 12)
except 11 (and 12)
SIFOX 381 SIFOX - 5, 7 1, 3 n.a. n.a. 1

SIFOX 382 SIFOX - 5, 7 1, 3 n.a. n.a. 1
SUBAT 461 SUBAT - 5, 7 1, 3 n.a. n.a.
SUBLA 328 SUBLA ü 5, 7 1, 3 n.a. n.a. 1

SUBL6 327 SUBL6 ü 5, 7 1, 3 n.a. n.a. 1
SUBL6 335 SUBL6 ü 5, 7 1, 3 n.a. n.a. 1
SUBUK 333 SUBUK ü 5, 7 1, 3 n.a. n.a. 1
SULIC 391 SULIC - 5, 7 1, 3 n.a. n.a. 1

SULIC 392 SULIC - 5, 7 1, 3 n.a. n.a. 1
SULIC 396 SULIC ü 5, 7 1, 3 n.a. n.a. 1
SULIS 393 SULIS - 5, 7 1, 3 n.a. n.a. 1
TUNEL 481 TUNEL - n.a. 1 Aggregate IF

SbU 1, 2 1, 3 5, 7 1, 3
SbU 3, 4 5, 7 1, 3 5, 7
TUNOF 384 TUNOF ü n.a. n.a. n.a. n.a. 1 No highway access
TUNOL 299 TUNOL ü n.a. 1 Aggregate IF


slots 1…7 1 … 15 9 … 15
SbU 1, 2 1, 3 5, 7 1, 3
SbU 3, 4 5, 7 1, 3 5, 7
TUNOP 292 TUNOP - 1, 3 5, 7 5, 7 n.a. 1 Aggregate IF
SbU 1, 2 1, 3 5, 7 1, 3
SbU 3, 4 5, 7 1, 3 5, 7
SbU 1, 2 1, 3 5, 7 1, 3
SbU 3, 4 5, 7 1, 3 5, 7
ULCAS 471 ULCAS - 5, 7 1, 3 n.a. n.a. 1
UNIDA 431 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1

UNIDA 432 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 433 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 434 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 435 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 436 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 437 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
UNIDA 438 UNIDA - 1, 3, 5, 7 1, 3, 5, 7 n.a. n.a. 1
The table disregards the signalling highways (even numbered

highways). With the UMUX 1500 the signalling highways are
assigned to their respective traffic highway and cannot be used
for other purposes.
PBUS
PBUS structure The PBUS provides a linear bus structure and thus equal bus access for the
slots 1 ... 20 of the subrack.
traffic signals (payload). Each PBUS line carries 4 x 2 Mbit/s of traffic
signals and the corresponding signalling information in additional TSs.
Only PBUS access circuits with configured traffic interfaces seize
PBUS highways.
For most applications of the UMUX 1500 this requirement is automatically

honoured.
PBUS access There are a few additional limitations for the implementation of units with
PBUS access:
• Slot number:
No PBUS access is available in slot 21.

However, slot 21 has access to the UBUS. Slot 21 is used preferably for
the implementation of the first power supply unit POSUS.
• PBUS capacity:
Depending on the selected control unit, all 128 2 Mbit/s highways of
the PBUS or a subset of the 128 highways are available (each highway
consists of 2 Mbit/s of traffic signals plus the corresponding signalling
information). A unit with PBUS access always seizes the PBUS in steps
of 4 highways (2 Mbit/s), independently of whether 1, 2, 3 or 4
highways are required to satisfy the requirements of the traffic
signal(s). As soon as the first TS of the first highway is configured
(cross connected), the complete set of 4 highways is seized on the
PBUS, thus reducing the remaining capacity by 4 highways.
This limits the number of physical PBUS accesses to 32 (32 x 4 = 128).
The PHAU figure (PBUS Highway Access per Unit) typical for each
PBUS unit indicates the maximum number of PBUS highways accessed
by a unit. This number is indicated in the tables (PHAU column)
provided in the chapter 9 “System and Ordering Information”.
Depending on the unit and its configuration the unit can seize less
than the PHAU figure indicated (but always in steps of 4 highways).
You can inspect the present highway usage on the PBUS via the
dialogue Bus Usage à PBUS. The number of accessed PBUS
highways is indicated in the PHA column (PBUS Highway Access). The
maximum figure under PHA is smaller or equal to PHAU.
• Control Units:
It is not possible to operate traffic or power units in slot 11. This slot is
reserved for the control unit(s). In systems with redundant control unit,
slot 12 is reserved as well. If the system has no backup for the control
unit, it is possible to implement other PBUS (or UBUS) units in slot 12.
The COBU<X> control unit affects the capacity on the PBUS in 2 ways:
− The COBU<X> as a PBUS unit (PBUS access for the UBUS):
− The type of the COBU<X> control unit defines the available PBUS
capacity:

available slots 1 … 16 slots 11 … 21
COBUQ 144 4 32 Yes No

SBUS
SBUS structure The UMUX 1500 provides 2 equivalent sectors, each with its own SBUS
structure:
• Sector A: Slots 2 … 9
• Sector B: Slots 15 … 20
The structure of the SBUS with respect to slots is prepared for Multiplex
Section Protection. The implementation of protection requires a special
relationship between the slots assigned to the working and the protecting unit.
Figure 8-2: Structure of the SBUS vs. slots of the UMUX 1500
subrack
SECTOR A SECTOR B
SBUS Set A SBUS Set B
Drop Bus A Drop Bus A
Add Bus A Add Bus A
Drop Bus B Drop Bus B
Add Bus B Add Bus B
Interconnection of slots for protection
W2 W3 P2 P3 W6 W7 P6 P7 W15 W16 P15 P16 W19 P19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
W Working
You must implement units providing interfaces for protection in
slots with the attribute W.
P Protecting
You must implement units providing protection in slots with the
attribute P. Protection works between the working and the
protecting unit implemented in slots with the same value.
SBUS access There are a few additional limitations for the implementation of units with
SBUS access:
• Slot number:
There is no SBUS access in the slots 1, 11, 12, 13, 14 and 21.
− Slots 2 … 9: SBUS sector A
− Slots 15 … 20: SBUS sector B
Please consider the note at the end of the paragraphs on the SBUS.
The note shows additional limitations that are due to the release.
• Implementation of the SYNI<X>:
The SBUS structure imposes defined unit to slot allocations if you want
to implement MSP and SETS equipment protection.
If you want to implement equipment protection please note that the
structure of the SBUS implies, that

− You configure the SYNIO units as follows:
SYNIO Slots Sector A Slots Sector B

2 3 4 5 6 7 8 9 15 16 17 18 19 20
Working unit A -- B -- C -- D --
Protecting unit A' -- B' -- C' --
It is mandatory to start the SYNIO implementation with the

working unit (slots 2, 6 and 15)! Protection is not available for the
unit in slot 19.
MSP between interfaces of 2 SYNIO units (FUTURE OPTION) is only
possible with units of the same type!
− You configure the SYNIF/SYNIC units as follows:
SYNIC Slots Sector A Slots Sector B

SYNIF
2 3 4 5 6 7 8 9 15 16 17 18 19 20
Working unit A B C D E F G
Protecting unit A' B' C' D' E' F' G'
It is mandatory to start the SYNIC/SYNIF implementation with the

working unit (slots 2, 3, 6, 7 and 15, 16, 19)!
SETS equipment Protection is possible between 2 units of the same
type:
− SYNIF - SYNIF
− SYNIC - SYNIC
− SYNIF - SYNIC
You can simultaneously operate the 2 SBUS sectors (sector A and B) at
a time.
• Implementation of the SYNAC, SYNAM:
You can configure the SYNAC/SYNAM units to any slot of the SBUS
sectors configured with the SYNI<X> unit(s)
• Capacity of the SBUS sectors:
The UMUX 1500 SBUS Sectors A and B do not provide equal capacity.
This allows you to
− terminate 1 STM-1 (SYNIF/SYNIC) for
− 7 x 8 (= 56) VC-12 in sector A.
− 5 x 8 (= 40) VC-12 in sector B.
− add/drop with 2 STM-1 IFs (1 SYNIO or 2 SYNIC/SYNIFs)
− 6 x 8 (= 48) VC-12 in sector A.
− 4 x 8 (= 32) VC-12 in sector B.
Please consider the note on the SBUS at the end of the paragraphs.

• Control units:
The COBUQ and COBUL control units are not released for SDH
functions!
There is no support available for NEs with SDH units and functionalities
controlled via the COBUQ and COBUL.
Please consider the note below which shows additional limitations that
are due to the release.
With the UCST R5A the following restrictions apply for the
implementation of units and features
• The UCST R5A allows the implementation of SYNI<X> units
as follows:
− It is not possible to configure more than 1 SYNIO per
SBUS sector.
− It is not possible to implement more than 2 SYNIF/SYNIC
units per sector.
• Protection is available as follows (exclusively):
− Multiplex Section Protection is only available between the
2 ports of a SYNIO (please note the restrictions for the
number of units implemented per sector).
− SETS Protection is only available with the SYNIC and
SYNIF units (please note the restrictions for the number
of units implemented per sector).
• The SYNIF_R2A.50 ESW does not allow you to operate the
SYNIF, SYNIC or SYNIO unit in the slot 8 (no UBUS access).
• The operation of 2 SBUS Sectors requires the unit templates
and corresponding ESW:
− SYNIO 605
− SYNIF 604
− SYNIC 168
Mechanical and thermal

Unit width The subrack of the UMUX 1500 features 21 slots. Each slot has a width of
4 TE ( 4 x 5.08 mm = 20.32 mm).
The width of most units is 4 TE, thus fitting a slot in the subrack. Some of
the PBUS units are 2 or 3 times this basic width. Examples:
• PHLC1: 3 x 4 TE = 12 TE
• PHLC2: 2 x 4 TE = 8 TE
• PHLC3: 2 x 4 TE = 8 TE
• SYNIO: 2 x 4 TE = 8 TE
Some units released with the UMUX 1300 (e.g. RIGEN) are double in
width 2 x 4 TE = 8 TE.
The width of each unit released for the UMUX 1500 is indicated in
chapter 9 “System and Ordering Information”.

Restrictions of unit For some units, restrictions apply to the proximity of units.
implementation
If applicable, the restrictions and details are provided with the technical
description of the unit.
Heat dissipation Heating up the air within the subrack might become a limiting factor,
especially if systems are stacked. For the management of heat dissipation,
consider
• Hot spots within the subrack due to local power dissipation
To avoid local overheating, it is recommended that you distribute the
dissipating units among the subrack. Some units such as the PHLC1
feature integrated heat management with a fan to prevent the unit
from local overheating.
• Heating up due to ambient air
The installation instructions provided with the UMUX 1500 user guide
describes the installation of the subracks and consider the thermal
conditions within the racks.
It is essential that you respect the specified ambient
temperature range for the subrack in order to preserve the
system specifications and prevent the system from overheating.
Summary of rules for unit Depending on application and units to be implemented the above aspects
implementation impact differently on the layout of the subrack. Apply the following rules
and instructions (summary) in the order:
• Protection of the control unit.
This defines whether slot 12 remains available for the implementation
of other units.
• Power consumption with respect to power supply units.
This defines the number of power supply units required for operation
(consider protection and future system expansions).
• Degree of protection required for power supply units.
This defines the number of additional power supply units required.
• Total of required bus access and slots (considering unit width)
including power supply units.
This shows principally whether there are enough slots available in the
subrack. Reducing the degree of protection for the power supply units
might increase the number of slots available.
• Draft layout for the physical layout of unit to slot assignment
Avoid covering slots which provide a highly flexible access to the
UMUX bus systems with "large" units (a width of more than 4 TE).
Templates for such layouts are provided.
• Assignment of SBUS units.
The UMUX 1500 SBUS has 2 sectors (A = slots 2 … 9 and B = slots 15
… 20). The structure of the SBUS implies rules for the unit
implementation if you want to implement equipment protection.
Apply the rules and consider future expansions.

• Assignment of UBUS units.

Since the implementation of UBUS units is critical for bus capacity and
bus access, UBUS units should be assigned first if the capacity of the
UBUS is an issue.
• Assignment of PBUS units.
No PBUS access for slot 21.
Check for sufficient PBUS capacity while adding units. Consider
− the number of PBUS highways managed by the selected control
unit.
− that the UBUS takes capacity from the PBUS (8 or 16 highways), if
you configure UBUS units.
• Distribution of power supply units.
Use slot 21 for one of the power supply units, since the PBUS is not
available in this slot.
The power supply units are best fitted into the slots that cannot be
used for UBUS units (no or wrong highway access, unit width
mismatching) or PBUS units (no bus access, unit width mismatching).
• Checking the layout with the EM.
Check the layout of the subrack with the EM e.g. in a standalone
session. This helps to avoid problems of configuration coming up
during commissioning.
Several iterations might be necessary to find the most appropriate
configuration for given requirements.

Templates for unit implementation

Standard configurations The UMUX 1500 is a multi-service Access System based on a modular
construction, which allows the flexible implementation of traffic
interfaces. Due to this flexibility the Access Systems are implemented
following the present requirements for traffic and transmission units
rather than building up standard configurations. The variable
requirements of the applications covered by the UMUX 1500 and the
flexibility of the Access System makes it almost impossible to provide
templates for standard system implementations.
For some of the most important applications however, proposals for
system implementation have been engineered:
• Cross connect with 2 Mbit/s traffic interfaces
• Access System for V5.1 service provisioning
The templates proposed for the V5.x Access Systems allow (if applicable
for service) migrations without physical reconfiguration and re-cabling of
the implemented user port interfaces:
• Migration from low end capacity of user ports to maximum capacity
available per subrack.
• Migration from PSTN to ISDN service provisioning with intermediate
steps.
• Migration from a V5.1 Access System to V5.2 service provisioning.
Although the standard management communication for the UMUX 1500
is based on the ECC, most templates reserve a slot for the SIFOX to offer
the implementation of EOC based management communication (however
not possible for all templates!). The templates propose dual power units
as a standard (except for the cross connect) plus 1 additional unit for n+1
power protection.
Please note that:
• The templates of course allow variants with fewer user ports
(e.g. with fewer ISBUQ or PHLC2 units).
• Other layouts than the proposed are possible as well, but
might not allow the types of migration cited above.
• All templates for V5.x Access Systems require 2 power units.
The units are loaded with approximately 60 % of their
capacity.
• The implementation of UBUS units requires particular care
with respect to the UBUS capacity available.

Cross connect
DXC 128 x 2 Mbit/s Tab. 8-7: Cross connect: 128 x 2 Mbit/s
Template Slot
DXC m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 1 X
POSUS n+1 1 X
LOMIF 16 X X X X X X X X X X X X X X X X
Spare slots 1
UBUS S1,2 X
UBUS S3
UBUS S4
PBUS X
SBUS SA
SBUS SB
Please note that:

• For NEs without protection of the COBUX/COBUV, slot 12
becomes a spare slot.
• You can not use the COBUQ unit to implement this cross
connect.
• The spare slot (slot 9) could be used for the implementation
of a SIFOX, if EOC access is required.
• The implementation of the EOC reduces the capacity of the
DXC to 124 x 2 Mbit/s (4 x 2 Mbit/s are required for UBUS
access).

V5.1 Access Systems It is recommended that you implement the Access Systems with V5.1
service provisioning according to the templates given, in order to maintain
flexibility of system expansion (e.g. PSTN, ISDN, V5.2 services) and to
avoid congestion on the UBUS.
The templates also allow you to prepare and preserve the cabling for user
ports in case of future expansions.
PSTN x 240 Tab. 8-8: V5.1: PSTN x 240
Template Slot
V5.1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 2 X X
PHLC1 4 X3 -- -- X4 -- -- X2 -- -- X1 -- --
ISBUQ
LOMIF 1 X
Spare slots 1
UBUS S1,2 X
UBUS S3
UBUS S4
PBUS X
SBUS SA
SBUS SB
Please note that:

• For NEs without protection of the COBU<X>, slot 12
• The spare slot (slot 9) can be used for the implementation of
a SIFOX, if EOC access is required.

PSTN x 180 / ISDN-BA x 24 Tab. 8-9: V5.1: PSTN x 180 / ISDN-BA x 24
Template Slot
V5.1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 2 X X
PHLC1 3 X3 -- -- X2 -- -- X1 -- --
ISBUQ 3 X1 X X
LOMIF 1 X
Spare slots 1
UBUS S1,2 X
UBUS S3
UBUS S4
PBUS X
SBUS SA
SBUS SB
Please note that:

• If no protection for the COBU<X> is required, slot 12
• The spare slot (slot 9) can be used for the implementation of
a SIFOX, if EOC access is required.
• The ISBUQ is a UBUS unit loading the UBUS with 17 TSs per
unit.

Template Slot
V5.1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 2 X X
PHLC1 2 X2 -- -- X1 -- --
ISBUQ 7 X2 X X X1 X X X
LOMIF 1 X
Spare slots
UBUS S1,2
UBUS S3
UBUS S4
PBUS
SBUS SA
SBUS SB
Please note that:

• There is no spare slot left unless n+1 power protection is not
implemented (slot 20). The slot can be used for the
implementation of a SIFOX, if EOC access is required.
unit.

Template Slot
V5.1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 2 X X
PHLC1 1 X1 -- --
ISBUQ 10 X2 X X X1 X X X X3 X X
LOMIF 1 X
Spare slots
UBUS S1,2
UBUS S3
UBUS S4
PBUS
SBUS SA
SBUS SB
Please note that:

• There is no spare slot left, unless n+1 power protection is
not implemented (slot 20). The slot can be used for the
unit.

ISDN-BA x 112 Tab. 8-12: V5.1: ISDN-BA x 112
Template Slot
V5.1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1
PCONV 2 X X
PHLC1
ISBUQ 14 X2 X X X1 X X X X3 X X X X X X
LOMIF 1 X
Spare slots
UBUS S1,2
UBUS S3
UBUS S4
PBUS
SBUS SA
SBUS SB
Please note that:

• There is no n+1 protection for the power supply units
provided.
• There is no spare slot left.

V5.2 Access System It is recommended that you implement the Access Systems with V5.2
service provisioning according to the templates given, in order to maintain
flexibility of system expansion (e.g. PSTN, ISDN) and to avoid congestion
on the UBUS.
The templates also allows you to prepare and preserve cabling for user
ports in case of future expansions.
PSTN x 240 Tab. 8-13: V5.2: PSTN x 240
Template Slot
V5.2 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 1 X
PHLC1 4 X3 -- -- X4 -- -- X2 -- -- X1 -- --
ISBUQ
Spare slots 3
UBUS S1,2 X X X
UBUS S3
UBUS S4
PBUS X X X
SBUS SA
SBUS SB
Please note that:

• A spare slot (slot 1, 8, 9) can be used for the implementation
of a SIFOX, if EOC access is required.

Template Slot
V5.2 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 1 X
PHLC1 3 X3 -- -- X2 -- -- X1 -- --
ISBUQ 3 X1 X X
Spare slots 3
UBUS S1,2 X X X
UBUS S3
UBUS S4
PBUS X X X
SBUS SA
SBUS SB
Please note that:

• A spare slot (slot 1, 8, 9) could be used for the
unit.

Template Slot
V5.2 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 1 X
PHLC1 2 X2 -- -- X1 -- --
ISBUQ 7 X2 X X X1 X X X
Spare slots 2
UBUS S1,2 X X
UBUS S3
UBUS S4
PBUS X X
SBUS SA
SBUS SB
Please note that:

• A spare slot (slot 1, 8) can be used for the implementation of
n+1 protection for the POSUS. This frees slot 20 for a SIFOX,
if EOC access is required.
unit.

Template Slot
V5.2 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 1 X
PHLC1 1 X1 -- --
ISBUQ 10 X2 X X X1 X X X X3 X X
Spare slots 2
UBUS S1,2 X X
UBUS S3
UBUS S4
PBUS X X
SBUS SA
SBUS SB
Please note that:

• A spare slot (slot 1, 8) can be used for the implementation of
n+1 protection for the POSUS. This frees slot 20 for a SIFOX,
if EOC access is required.
unit.

ISDN-BA x 112 Tab. 8-17: V5.2: ISDN-BA x 112
Template Slot
V5.2 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
PCONV 1 X
PHLC1
ISBUQ 14 X2 X X X1 X X X X3 X X X X X X
SIFOX (EOC)
Spare slots 1
UBUS S1,2 X
UBUS S3
UBUS S4
PBUS X
SBUS SA
SBUS SB
Please note that:

• The spare slot 8 can be used for the implementation of n+1
protection for the POSUS.
unit.

STM-1 aggregate and

applications
TM/ADM for k x 8 x VC-12 Tab. 8-18: STM-1 TM/ADM: k x 8 x VC-12
with MSP
Template Slot
STM-1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
SYNIO 1 X --
SYNAC k X6 X5 X4 X3 X2 X1
Spare slots 13
UBUS S1,2 X
UBUS S3 X X X X
UBUS S4 X X X
PBUS X X X X X X X X
SBUS SA
SBUS SB X X X X X
k: k=1…6
Please note that:
• You can not use the COBUQ/COBUL unit to implement this
TM/ADM.
• It is possible to implement MSP with the 2 IFs of the SYNIO.
• Traffic units in the free slots provide corresponding traffic
interfaces (e.g. 48 x 2 Mbit/s).

TM/ADM for k x 8 x VC-12

with SETS protection
Tab. 8-19: STM-1 TM/ADM: k x 8 x VC-12
Template Slot
STM-1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
SYNIF/SYNIC 1 X2 X1
SYNAC k X6 X5 X4 X3 X2 X1
Spare slots 13
UBUS S1,2 X
UBUS S3 X X X X
UBUS S4 X X X
SBUS SA
SBUS SB X X X X X
k: k=1…6
Please note that:
TM/ADM.
• It is possible to implement SETS equipment protection with
the 2 SYNIF/SYNICs.
• Traffic units in the free slots provide corresponding traffic
interfaces (e.g. 48 x 2 Mbit/s refer to next template).

TM/ADM for 48 x 2 Mbit/s via

PBUS
Tab. 8-20: STM-1 TM/ADM: 48 x 2 Mbit/s via LOMIF
Template Slot
DXC m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 1 X
POSUS n+1 1 X
LOMIF 6 X X X X X X
SYNIO 1 X1 --
SYNAC 6 X6 X5 X4 X3 X2 X1
Spare slots
UBUS S1,2
UBUS S3
UBUS S4 3 X X X
PBUS 3 X X X
SBUS SA
SBUS SB 3 X X X
Please note that:

TM/ADM.
• If you use 2 SYNIF/SYNIC (slots 2 and 4) instead of 1 SYNIO
and change the SYNAC X6 from slot 4 to slot 3 you can
implement SETS equipment protection.
• Total PHAU (without COBUX/COBUV): 48 One or two more
PHAU is/are used if an UBUS unit is implemented or the
management uses the SDH SOH

TM/ADM for 48 x 2 Mbit/s

direct front access
Tab. 8-21: STM-1 TM/ADM: 48 x 2 Mbit/s via SYNAM
Template Slot
STM-1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
SYNIO 1 X --
SYNAM k X6 X5 X4 X3 X2 X1
Spare slots 13
UBUS S1,2 X
UBUS S3 X X X X
UBUS S4 X X X
SBUS SA
SBUS SB X X X X X
Please note that:

TM/ADM.
• If you use 2 SYNIF/SYNIC (slots 2 and 4) instead of 1 SYNIO
and change the SYNAM X6 from slot 4 to slot 3 you can
implement SETS equipment protection.
• Total PHAU (without COBUX/COBUV): 0 !!!
One or two PHAU is/are used if an UBUS unit is implemented
or the management uses the SDH SOH.

TM/ADM + V5.1 hub Tab. 8-22: STM-1 TM/ADM + V5.1 hub: 30 V5.1 interfaces
Template Slot
DXC m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 1 X
POSUS n+1 1 X
LOMIF 4 X X X X
SYNIO 1 X1 --
SYNAC 4 X X X X
PCON2 3 X X X
Spare slots
UBUS S1,2 3 X X X
UBUS S3 1 X
UBUS S4
PBUS 4 X X X X
SBUS SA 2 X X
SBUS SB 1 X
Please note that:

TM/ADM and V5.1 hub.
• Total PHAU (without COBU<X>): 124
• The remaining PHAU is used if a UBUS unit is implemented
or the management uses the SDH SOH.
The V5.1 Access System provides services and interfaces as follows:
• Implementation of thirty V5.1 interfaces with V5 link access via the
STM-1 interface, local protocol processing but without local user ports.
The user ports are deployed via 2 Mbit/s links to remote NEs.
• The PCON2 units provide 30 V5.1 interfaces, each with a maximum of
30 PSTN user ports or ISDN BA equivalents. The remote deployment of
the user ports requires 30 x 2 Mbit/s interfaces.
• The SYNAC units provide 4 x 8 (=32) VC-12 from the STM-1 signal
providing the 30 V5.1 access links.
• The LOMIF units provide 4 x 8 (=32) G.703 2 Mbit/s interfaces for the
deployment of the 3 x 30 PSTN user ports.

TM/ADM + V5.2: 180 x PSTN / Tab. 8-23: STM-1 TM/ADM + V5.2: 180 x PSTN / 16 x ISDN BA
16 x ISDN BA
Template Slot
STM-1 m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 2 X X
POSUS n+1 1 X
SYNIO 1 X --
SYNAC 1 X1
PCONV 1 X
PHLC1 3 X3 -- -- X2 -- -- X1 -- --
ISBUQ 2 X2 X1
Spare slots 1
UBUS S1,2 X
UBUS S3
UBUS S4
PBUS X
SBUS SA
SBUS SB
Please note that:

TM/ADM.
• Total PHAU (with COBUX/COBUV): 32
• Depending on the COBUX/COBUV, it is possible to use
remaining PHAU for 2 Mbit/s traffic signals.

TM/ADM + V5.2 Tab. 8-24: TM/ADM + V5.2 hub: 3 V5.2 interfaces
Template Slot
DXC m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1 1 X
POSUS 1 X
POSUS n+1 1 X
LOMIF 6 X X X X X X
SYNIO 1 X1 --
SYNAC 2 X X
PCON2 3 X X X
Spare slots
UBUS S1,2 3 X X X
UBUS S3 1 X
UBUS S4
PBUS 4 X X X X
SBUS SA 3 X X X
SBUS SB 1 X
Please note that:

TM/ADM.
• Total PHAU (without COBUX/COBUV): 124
• The remaining PHAU is used if an UBUS unit is implemented.
The V5.2 Access System provides services and interfaces as follows:
• Implementation of three V5.2 interfaces with V5 link access via STM-1
interfaces, local protocol processing but without local user ports. The
user ports are deployed via 2 Mbit/s links to remote NEs.
• The PCON2 units provide 3 V5.2 interfaces, each with a maximum of
480 PSTN user ports or ISDN BA equivalents. There are four 2 Mbit/s
links per V5 interface recommended. The remote deployment of the
user ports requires 3 x 16 2 Mbit/s interfaces.
• The SYNAC units provide 2 x 8 VC-12 from the STM-1 signal providing
three times 5 x 2 Mbit/s for the V5.2 link access.
• The LOMIF units provide 3 x 2 x 8 (= 3 x 16) 2 Mbit/s interfaces for the
deployment of the 3 x 480 PSTN user ports.

Generic template for unit Tab. 8-25: Generic template for UMUX 1500 unit implementation
implementation
Template Slot
m 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS 1)
POSUS n+1
Spare slots
UBUS S1,2
UBUS S3
UBUS S4
PBUS
SBUS SA
SBUS SB
1)
Preferred slot to implement the first POSUS unit.

Power consumption and heat dissipation

Power consumption The power consumption of the UMUX 1500 has to be evaluated at 2
power interfaces:
• Interface to external power supply
This interface covers all power requirements of the subrack and its
units (power supply units included). Units with PSTN, ISDN and remote
data interfaces (NTUs) might considerably contribute to the power
consumption on this interface.
This total power consumption has to be considered for the
specification of the capacity of the external power supply. The
interface of the UMUX 1500 to the external power supply is specified:
− -48 VDC / -60 VDC
− 10 A continuous maximum current.
The contribution of each unit to the power consumption on the
external power supply can be read from the tables provided with the
unit descriptions and the tables provided in the user guide [001].
• Internal power rails
The power consumption on the internal power rails defines the
number of power supply units required for operation. For the
implementation of protection, additional units might be provided.
The nominal specifications for a POSUS power supply unit are:
− +5 VCC (POSUS): 10 A max.
− -5 VCC (POSUS): 2.5 A max.
The technical data provided with each unit description indicate the
power consumption on the internal power supply rails for each unit.
It is possible to use the UCST to evaluate the power consumption on
the power rails of the subrack for all configured units. The main menu
provides a power indicator, which displays the percentage of power
consumed with respect to the amount of total converted power
available. A red coloured field indicates a lack of converted power.
Heat dissipation Power dissipation within the subrack might be a limiting factor, especially
if several systems are stacked.
To avoid local overheating, you should distribute the dissipating units
equally among the subrack. Installation of the subracks within racks
considers ambient and internal thermal conditions.
In order to preserve the system specifications and prevent the
system from overheating, it is essential that you respect the
specified range of the ambient temperature for the installation
of the subrack.
If you plan to stack systems, take into account that each system will heat
the air. In this way heated air could define the ambient thermal condition
for the system(s) installed above!
If the thermal ambient condition (in general or due to heating by systems
below) is out of the range specified for the UMUX 1500, consider and

implement the following measures, till the ambient conditions are within
the specified temperature range:
• Implementation of heat deflection shield(s) below (and above) each
subrack.
• Forced air flow through the subracks.
The FANUV fan unit fits 19-inch and ETSI racks. This unit features 3
fans, the operation of which is controlled by the ambient temperature.
The fan unit has an interface that signals failures of the individual fans.
It is possible to integrate the status signals into the alarm system of the
UMUX 1500 via the alarm inputs of the COBU<X> control units.
• Air conditioning.
Air conditioning is normally provided for telecommunication rooms or
for equipment that is installed in outdoor cabinets.
Calculating power While the theoretical maximum power dissipation in a subrack is

dissipation straightforward to calculate, it is not easy to estimate the mean power
dissipated in a subrack. The power dissipation depends heavily on the type
of units implemented and the traffic load.
There are 2 ways to approach the mean power dissipation of a the
UMUX 1500, via the theoretical maximum power dissipation or via
summing the power dissipation of units under real traffic load.
• Theoretical maximum power dissipation
The theoretical maximum dissipation is evaluated by summing the
maximum power consumption at the external power supply interface
of the UMUX 1500. It is assumed that all energy is dissipated within
the subrack. This value is easy to calculate but provides a worst case
value which is, depending on units and traffic, far above the real mean
power dissipation.
− The evaluation of the mean power dissipation according to this
method however provides reasonable results for the mean power
dissipation if the UMUX 1500 is operated as follows:
- cross connect
- Access System for data interfaces
(no remote data units)
- channel banks with exchange line interfaces
(no ground keys)
− The method is not suited to estimating the mean power dissipation
if a considerable part of the energy provided via the power
interface of the UMUX 1500 is dissipated in equipment external to
the NE. This applies for the following applications:
- Access System for data interfaces with remote data units
including ISDN (remote powering)
- applications with SUBLA<X> and PHLC<X> units
(subscriber loops)
- channel banks with subscriber line interfaces
In the latter cases, you must calculate the mean power dissipation as
follows:

• Estimated mean power dissipation

The estimated mean power dissipation is calculated in 2 steps:
− Evaluation of the theoretical maximum power dissipation for
− Control units
− Power supply units
− Transmission units
− etc.
− Summing of the power dissipation of the remaining units for a
specified traffic load. Values depending on traffic load and mode of
operation are provided with the technical data in the unit
descriptions (e.g. for the PHLC1, PHLC2) and in the user guide
[001] (UBUS units).
The estimated mean power dissipation is the total power of all values.
IP addresses
The management communication of the UMUX 1500 is based on TCP/IP.
For this reason, all UMUX 1500 NEs and the corresponding interfaces of
the EM need individual IP addresses. Control units not yet configured
provide 2 default IP addresses, one for management access via the serial
interfaces (here F-interface) and one for the access via the QX-interface. A
subnet mask is specified for the QX-interface.
Depending on size an access network built with the UMUX 1500 Access
Systems might require several hundred addresses. To ease the
implementation of a management communication network it is preferable
that the IP addresses are structured. Since the use of IP addresses is
standardised and globally regulated, you can not freely assign IP
addresses. The local representation of the IANA (Internet Assigned
Numbers Authority) provides IP addresses for public use.
The requirement for IP addresses also depends on your existing and
planned infrastructure for the management of your access network.
The default IP addresses provided with the UMUX 1500 are in accordance
with the rules for addresses used in closed private networks without
Internet access.

Calculating the number of UMUX spare units

The UMUX system and its units feature high values of MTBF (Mean Time
Between Failure). The document [003] describes periodically updated life
MTBF values and additional information on the reliability of the system
(under defined conditions). The document is available on request.
In the case of failures, all UMUX equipment provides very low values of
MTTR (Mean Time To Repair). This low MTTR is a result of
• Quick location of failures due to the comprehensive operation and
maintenance concept of the UMUX.
• Quick replacement of failed units due to
− inventory data identifying equipment and easing the logistics and
provisioning of spare units
− front access of signal cables
− central MIB database allowing immediate automatic re-
programming of the operational parameters for the substitute unit.
− SW download (new units only) reconfiguring the unit SW (ESW) for
the configured unit function independently of the former unit
history.
• Functional protection of the power supply
If the NE features equipment protection for the power converter units,
single or multiple unit failures (depending on the degree of protection)
will not affect the system operation.
• Functional protection of the control unit
If the NE features equipment protection for the control units, the
failure of a control unit will not affect system operation (excepted for
some bit errors in the traffic signals connected via the UBUS and via
the PBUS).
It is essential that you dispose of spare units to re-establish or maintain
the original degree of the quality of service after failures:
• For units without functional protection (traffic, transmission units):
− a minimum of 1 unit of each type, or
− 2 … 4% for each type of unit in service
• For units with functional protection (power supply, control units)

Please note that the above figures are valid considering that:
• The failed units are immediately sent to the manufacturer for
repair.
• The reduced number of reserve units for power supply and
control units as indicated above only apply if the
corresponding protection has been implemented for a large
majority of the NEs.

ascom
System and Ordering Information 9

Functions and unit software ESW
The following tables describe the functions and software released for the
UMUX 1500 together with the releases UCST and UNEM R5A. Four
tables, one for each type of unit provide the corresponding ordering
information.
Please note that:
• The lists are definitive for the UCST and UNEM release R5A!
• If you configure/operate other functions than the functions
quoted in the tables below, ATR disclaims any responsibility
for system malfunction and/or failures/disturbances of the
traffic signals.
• New functions will be added with the next releases.
Element manager Tab. 9-1: Element Managers R5A
EM Part number Current APDSW SW Functional Description / Remarks

R5A
Standard Name Version Name Version
UCST EN/LZYBU 151 819/1 R5A APDSW R1C03 UCST R5Axx UCST R5A for Windows 98, ME, NT
and 2000.
CD-ROM
UNEM EN/LZYBU 351 001/1 R5A APDSW R1C03 UNEM R5Axx UNEM Basic Package R5A for HP-UX 10.20
This package supports the
UMUX 1500 / 1200 with management
communication via ECC.
CD-ROM

ascom System and Ordering Information
Control and power units Tab. 9-2: Functions and software of the UMUX 1500 control and
power units (UCST R5A)
Functions Unit Hardware Bootloader SW ESW Functional Description / Remarks

R5A or APDSW or System SW
Template T.I.U. Name Version HK PH Name Version Name Version
COBUX 145 4C ROFBU 367 103/1 R2A 103 8 BCOBU R2A06 COBUX R3Dxx Control Unit UMUX 1500 / 1200
R3Exx - access to 8 UBUS Hwys
- support of 128 PBUS Hwys
TCP/IP tunnelling, Q1-master IF
ECC, diagnostics.
ROFBU 367 103/1 R2B 105 BCOBU R2B01 Ditto plus symmetrical IFs for
the ESI-1 and ESO-4.
ROFBU 367 103/1 R2C 107 COBUX R3Exx Ditto with new unit HW/ESW.
ECC, diagnostics.
COBUV 137 4C ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R3Dxx Control Unit UMUX 1500 / 1200
ECC, diagnostics and
conference function,
symmetrical IFs for the ESI-1
and ESO-4.
ROFBU 367 103/2 R1B 207 COBUX R3Exx Ditto with new unit HW/ESW.
COBUV 237 4E ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R3Dxx Control Unit UMUX 1500 / 1200
ECC, diagnostics and
conference function,
symmetrical IFs for the ESI-1
and ESO-4.
COBUQ 144 4C ROFBU 367 114/1 R2A 3 4 BCOBU R2A06 COBUX R3Dxx Control Unit UMUX 1500 / 1200
ROFBU 367 114/1 R2C 5 BCOBU R2B01 Ditto plus symmetrical IF for
ESI-1 and ESO-4.
ROFBU 367 114/1 R2D 7 COBUX R3Exx Ditto with new unit HW/ESW.
COBUL 215 5A ROFBU 367 215/1 R1A 403 4 BCOBU R2A06 COBUX R3Dxx Control Unit UMUX 1500 / 1200
R3Exx - access to 4 UBUS Hwy.s
- support of 128 PBUS Hwy.s
Ethernet IF, F-, Q1- and Q1-
master IF.
All synchronisation interfaces
are 75 Ohm impedance.
ROFBU 367 215/1 R1B 407 BCOBU R2B01 COBUX R3Exx Ditto.
ESI-1 provides additionally 120
Ohm impedance and ESO-1

Ascom System and Ordering Information


has galvanic isolation.
POSUS 106 3.2a COZBU 110 106/1 R1A 1 - - - - - Power converter for
UMUX 1500 / 1200
Vin -48/-60 V, Pmax. 62 W
PODIS 033 ≤ 2.5d COZBU 401 133/1 R2A - - - - PODIS R1A Power distribution unit for the
remote powering of 4 HDSL
CAP desktops.
T.I.U.: Template Introduced with the indicated UCST version.

HK: Hardware Key
Part of the inventory data.
PH: PHAU (PBUS Highway Access per Unit)
Maximum number of PBUS highways (2 Mbit/s of traffic signals
plus corresponding signalling) accessed per unit.
Please note that:
• Empty fields are "not applicable" for the corresponding
function.
• The "Bootloader" software is included in the table. The data
is readable with the inventory function of the EM.
• You can compose the name of the files with compressed
unit software (ESW) by composing the expressions from the
columns "Name" and "Version" as follows (example):
"Name": COBUX
"Version": R3E02
"Filename": COBUX_R3.E02

PBUS units Tab. 9-3: Functions and software of the PBUS units
with the UMUX 1500 (UCST R5A)
Functions Unit Hardware Bootloader Unit Software Functional Description / Remarks

R5A Software ESW
LAWA4 235 4E ROFBU 367 135/1 R1A 1 8 BLEMU R1A01 LAWA4 R3Bxx Connects a local area network
R3Cxx (LAN) over a 10BaseT interface to
the UMUX units with aggregate
interfaces.
- Flexible Layer 2 or 3 IP
concentration
- Cascadable over the UMUX
internal cross connect
- Frame Relay FRAD functionality
- Static routing
- Supported routing protocol:
OSPF2 (optional)
- Support of VLAN (port based,
TDM or IEEE 802.1q)
- Hardware prepared for NAT
and for Voice over IP
applications
ROFBU 367 135/1 R1B 2 LAWA4 R3Bxx Ditto with new unit HW/ESW.
R3Cxx
LEMU6 236 4E ROFBU 367 134/1 R1A 2 8 BLEMU R1A01 LEMU6 R3Bxx xDSL multiuser unit that
R3Cxx concentrates the xDSL IP-packed
oriented traffic of 6 subscribers
and transfers it to the local
10BaseT front interface or to the
PBUS cross connect.
- Bridging, with diverse sub
modes
- IP static routing
- IP OSPF V2 dynamic routing
- Unnumbered IP links on DSL
and PBUS interfaces
- Frame Relay FRAD functionality
- DHCP relay configurable for
MUSIC 100
- IP managed bridge
configurable for MUSIC 100
- Uses CAP encoding.
ROFBU 367 134/1 R1B 3 LEMU6 R3Bxx Ditto with new unit HW/ESW.
R3Cxx
LEMQ6 148 4E ROFBU 367 148/1 R1A 2 8 BLEMU R1A01 LEMQ6 R3Bxx Same as LEMU6 but uses 2B1Q
R3Cxx encoding.
ROFBU 367 148/1 R1B 3 LEMU6 R3Bxx Ditto with new unit HW/ESW.
R3Cxx
LESA8 085 5A ROFBU 367 161/1 R1A 201 8 BLESA R1A01 LESAC R1Cxx XDSL unit with 8 x 2 Mbit/s PBUS
access and
- 8 DSL services via 1 pair
- 4 DSL services via 2 pairs
- a mixture of the above
- nx64 kbit/s, P12
VC-12 FUTURE OPTION
- Line code: CAP (2B1Q, PAM16
FUTURE OPTIONS)
- No remote powering
ROFBU 367 161/1 R1A/A 203 BLESA R1B00 Ditto with new unit HW
ROFBU 367 161/1 R1B 202 Ditto with new unit HW

(2 Mbytes Flash)


R5A Software ESW
LESAP 095 5A ROFBU 367 162/1 P1B 102 4 BLESA R1B00 LESAC R1Cxx XDSL unit with 4 x 2 Mbit/s PBUS
access and
- 4 DSL services via 1 pair
- 4 DSL services via 2 pairs
- a mixture of the above
- nx64 kbit/s, P12
VC-12 FUTURE OPTION
- Line code: CAP (2B1Q, PAM16
FUTURE OPTIONS)
- 1 service with remote powering
for the remote unit
LOMIF 101 3.2a ROFBU 367 101/1 R1A 1 8 B302I R1A21 LOMIF R3B00 2 Mbit/s IF, G.703
R3Cxx 8 ports 120 / 75 Ohm
ROFBU 367 101/1 R1B B302I R1B00 Transparent and terminated
modes.
LOMIF 120 3.3a Template no longer available.
The function is fully replaced
with LOMIF 140
LOMIF 140 4C Ditto as LOMIF 101 with
additional features: PM, PRA and
Clock Master mode
LOMIF R3B01 Ditto as LOMIF 140.
R3Cxx
Supports additionally the CRC-4
MFA Status/Maintenance
functions
LOMI4 150 4E ROFBU 367 152/1 R1A 101 4 B302I R1B00 LOMIF R3Cxx 2 Mbit/s IF, G.703
4 ports 120 / 75 Ohm
Supports the same features as
the LOMIF 140 (incl. CRC-4
MFA).
PCONV 143 4E ROFBU 367 108/1 P1B 2 12 B360I R1A12 PCONV R4Axx V5.x protocol processing unit for
R4Bxx PSTN and ISDN service
R4Cxx 240 PSTN user ports
112 ISDN-BA user ports including
- processing of p- and f-data
- digital leased lines
ROFBU 367 108/1 R1A B360I R1B00 Ditto
ROFBU 367 108/1 R1A/1 3 12 B360I R1C00 Ditto
R1B
R2A
PCON2 142 4E ROFBU 367 115/1 R1A 103 20 B360I R1C00 PCONV R4Axx V5.x protocol processing unit for
R4Bxx PSTN and ISDN service
R4Cxx 480 PSTN user ports
224 ISDN-BA user ports including
- processing of p- and f-data
- digital leased lines
PHLC1 125 4C ROFBU 367 107/1 R1B 2 4 B302I R1A21 PHLC1 R3Exx Subscriber line IF PSTN
R3Fxx 60 ports a/ b-wire, impedance
programmable, modes V5.x,
MCAS, Carrier adapter, Phone-
Exchange
Full test for subscriber lines is
included
Ring over b-wire.


R5A Software ESW
ROFBU 367 107/2 R1B 3 Ditto but ring over b-wire with
earth back
ROFBU 367 107/1 R1C 5 PHLC1 R3Fxx Ditto ring over b-wire
New unit HW/ESW
ROFBU 367 107/2 R1C 6 Ditto but ring over b-wire with
earth back.
New unit HW/ESW.
PHLC2 129 4C ROFBU 367 128/1 R1A 2 4 B302I R1A21 PHLC1 R3Exx Subscriber line IF PSTN
Exchange
included
Ring over b-wire
ROFBU 367 128/2 R1A 3 Ditto ring over b-wire with earth
back
ROFBU 367 128/1 R1B 5 PHLC1 R3Fxx Ditto ring over b-wire
New unit HW/ESW
ROFBU 367 128/2 R1B 6 Ditto but ring over b-wire with
earth back.
New unit HW/ESW.
PHLC3 126 4E ROFBU 367 126/1 R1A 2 4 B302I R1A21 PHLC1 R3Exx Subscriber line IF PSTN
Exchange
included
Ring over b-wire
ROFBU 367 126/1 R1B 5 PHLC1 R3Fxx Ditto ring over b-wire
New unit HW/ESW
ROFBU 367 126/2 R1A 6 Ditto but ring over b-wire with
earth back.

HK: Hardware Key
Please note that:
• The version of the "Bootloader" software is included in the
table. The data is readable with the inventory function of the
EM.
"Name": PHLC1
"Version": R3E20
"Filename": PHLC1_R3.E20

SBUS units Tab. 9-4: Functions and software of the SBUS units

R5A Software ESW
SYNAC 163 4D ROFBU 367 113/1 R1A 3 8 B302I R1B00 SYNAC R2Axx Access to 8 VC-12 on the SBUS
R1A/1 R2Bxx and 8 2 Mbit/s with PBUS access.
New functionalities:
- PRA NT1-U and LT-U
- Clock master mode
ROFBU 367 113/1 R1B 4 SYNAC R2Bxx Ditto with new unit HW/ESW.
SYNAM 116 4D ROFBU 367 116/1 R1A 1 - B302I R1B00 SYNAC R2Axx Access to 8 VC-12 on the SBUS
R2Bxx and 8 2 Mbit/s interfaces (G.703)
for E12 signals.
ROFBU 367 116/1 R1B 2 SYNAC R2Bxx Ditto with new unit HW/ESW.
SYNIC 118 4D ROFBU 367 118/1 R1A 1 - B360I R1D00 SYNIF R2Axx STM-1 aggregate interface.
R3Axx 1 electrical STM-1 port and
corresponding access to the
SBUS
SETS equipment protection.
ROFBU 367 118/1 R1B 2 SYNIF R3Axx Ditto with new unit HW/ESW.
SYNIC 168 5A ROFBU 367 118/1 R1A 1 - B360I R1D00 SYNIF R3Axx Ditto. Supports additionally the
simultaneous operation of 2
SBUS Sectors (UMUX 1500)
ROFBU 367 118/1 R1B 2 Ditto with new unit HW.
SYNIF 164 4D ROFBU 367 104/1 R1A 105 - B360I R1D00 SYNIF R2Axx STM-1 aggregate interface.
R3Axx 1 optical STM-1 port S1.1 and
corresponding access to the
SBUS.
SETS equipment protection.
ROFBU 367 104/2 R1A - Ditto 1 optical STM-1 port L1.1
ROFBU 367 104/1 R1B 106 - SYNIF R3Axx Ditto with new unit HW/ESW
and
- 1 optical STM-1 port S1.1
ROFBU 367 104/2 R1B - - 1 optical STM-1 port L1.1
SYNIF 604 5A ROFBU 367 104/1 R1A 105 - B360I R1D00 SYNIF R3Axx Ditto. Supports additionally the
1 optical STM-1 port S1.1
ROFBU 367 104/1 R1B 106 - Ditto with new unit HW and
- 1 optical STM-1 port S1.1
SYNIO 165 4D ROFBU 367 105/1 R1A 3 - B360I R1D00 SYNIF R2Axx STM-1 aggregate interface.
R3Axx 2 optical STM-1 ports S1.1 and
corresponding access to the SBUS.
Multiplex Section Protection.


R5A Software ESW
ROFBU 367 105/1 R1B 5 - Ditto.

ROFBU 367 105/2 R1B - Ditto 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1A - Ditto 2 optical STM-1 ports L1.2
ROFBU 367 105/1 R1C 6 - SYNIF R3Axx Ditto with new unit HW/ESW and
- 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1C - - 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1B - - 2 optical STM-1 ports L1.2
SYNIO 605 5A ROFBU 367 105/1 R1A 3 - B360I R1D00 SYNIF R3Axx Ditto. Supports additionally the
1 optical STM-1 port S1.1
ROFBU 367 105/1 R1B 5 - Ditto 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1B - Ditto 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1A - Ditto 2 optical STM-1 ports L1.2
ROFBU 367 105/1 R1C 6 - Ditto with new unit HW and
- 2 optical STM-1 ports S1.1
ROFBU 367 105/2 R1C - - 2 optical STM-1 ports L1.1
ROFBU 367 105/3 R1B - - 2 optical STM-1 ports L1.2

HK: Hardware Key
Please note that:
• The version of the "Bootloader" software is included in the
table. The data is readable with the inventory function of the
EM.
"Name": SYNIF
"Version": R3A72
"Filename": SYNIF_R3.A72

UBUS units Tab. 9-5: Functions and software of the UBUS units
Functions Unit Hardware Bootloader Unit Firm/Software Description / Remarks

R5A Software
Template T.I.U. Name HK Name Version Name Version
EXBAT 401 ≤ 2.5.d COZBU 103 401/5 R1D 7 - - EXBAT R1C ISDN BA exchange line IF
8 ports, 4B3T line code
EXLA3 361 ≤ 2.5.d COZBU 103 361/10 R1L 0 - - EXLA3 R1C PSTN exchange line IF
12 ports a/b,
EXLA6 352 ≤ 2.5.d COZBU 103 352/3 R1H 6 - - EXLA6 R2F PSTN exchange line IF
12 ports a/b, imp. 600 Ohm
EXLAN 342 ≤ 2.5.d COZBU 103 342/4 R1H 7 - - EXLAN R2F PSTN exchange line IF
12 ports a/b, complex imp.
EXLAN 343 ≤ 2.5.d COZBU 103 343/3 R1F 5 - - EXLAN R2F PSTN exchange line IF, remote
op.
12 ports a/b, complex imp.
Sensitive metering detection
EXLIC 451 ≤ 2.5.d COZBU 103 451/4 R1B 7 - - EXLIC R1A ISDN BA exchange line IF
12 ports, 2B1Q line code
GECOD 371 ≤ 2.5.d COZBU 103 371/5 R1C 7 - - GECOD R1B Data IF 64 kbit/s G.703, co-
directional
8 ports
GECOD 372 ≤ 2.5.d COZBU 103 372/2 R1B 7 - - GECOD R2A Ditto plus
1+1 protection
HIRAC 810 - AM64/512 2B1Q
ISBUQ 130 4C ROFBU 367 109/1 R1A/1 1 B302U R1A22 ISBUQ R3Cxx Subscriber line IF ISDN BA
R3Dxx 8 ports, 2B1Q line code, 96 V
R3Exx remote powering for NT-1
Additionally support of
- p- and f-data
- permanent activation of digital
section
- extended test and maintenance
functions
ROFBU 367 109/1 R1B 4 ISBUQ R3Dxx Ditto with new unit HW/ESW
R3Exx
ISBUT 110 4C ROFBU 367 110/1 R1A 102 B302U R1A22 ISBUQ R3Cxx Subscriber line IF ISDN BA
R1B R3Dxx 8 ports, 4B3T line code, 96 V
R3Exx remote powering for NT-1
Additionally support of
- p- and f-data
- permanent activation of digital
section
- extended test and maintenance
functions
- digital leased lines ("Standard
Festverbindungs Modus")
ROFBU 367 110/1 R1C 104 ISBUQ R3Dxx Ditto with new unit HW/ESW
R3Exx


R5A Software
LECA2 050 ≤ 2.5.d COZBU 402 050/1 R5D/A 20 - - LECA2 R3B 2 Mbit/s transmission IF
R5E Line IF for 2 twisted pairs with
CAP encoding.
NOTE: All modes of operation
available with exceptions
as follows:
1. LECA2 is not
released for any
application UMUX
internal highway<->
UMUX internal
highway with split
site installation.
2. The application
LECA2 UMUX
internal highway <-
> remote unit with
split site installation
is not released for
UMUX 1500.
LECA2 052 3.3a COZBU 402 052/1 R1E/A 20 - - LECA2 R4C Ditto (note included !)
R1H including operation of MUSIC 100
LECA2 056 4E COZBU 402 056/1 R1C 20 - - LECA2 R6A Ditto (note included !)
including operation of MUSIC 100
LE2Q2 244 4E COZBU 402 244/1 R1C 20 - - LE2Q2 R6A Ditto (note included !) with 2B1Q
encoding.
MEGIF 261 ≤ 2.5.d COZBU 103 261/10 R1C 7 - - MEGIF R1H 2 x 2 Mbit/s, G.703
2 ports 75 Ohm
MEGIF 262 ≤ 2.5.d COZBU 103 262/2 R1B 7 - - MEGIF R2B Ditto including PM
MEGIF 264 4C COZBU 103 264/1 R1A 7 - - MEGIF R3A Ditto including PM and disable
SSI-mode
MEGIF 271 ≤ 2.5.d COZBU 103 271/8 R1C 7 - - MEGIF R1H 2 Mbit/s, G.703
2 ports 120 Ohm
MEGIF 272 ≤ 2.5.d COZBU 103 272/1 R1A 6 - - MEGIF R1G 2 Mbit/s, G.703
2 ports 120 Ohm, GWF
MEGIF 273 ≤ 2.5.d COZBU 103 273/2 R1B 7 - - MEGIF R2B 2 Mbit/s, G.703
2 ports 120 Ohm and PM
MEGIF 274 4C COZBU 103 274/1 R1A 7 - - MEGIF R3A Ditto including PM and disable
SSI-mode
NEMCA 311 ≤ 2.5.d COZBU 103 311/2 R1A 6 - - NEMCA R2A Analogue telephone. IF, 2/4w
8 ports
NEMCA 312 ≤ 2.5.d COZBU 103 312/2 R1C 6 - - NEMCA R3A Ditto including 1+1 protection
NEMGE 315 ≤ 2.5.d COZBU 103 315/1 R1B 7 - - NEMGE R1A German parameter version of
NEMCA
SIFOX 381 ≤ 2.5.d COZBU 103 381/7 R1C 7 - - SIFOX R1C Data IF 64 kbit/s IF X.24/V.11
4 ports
SIFOX 382 ≤ 2.5.d COZBU 103 382/2 R1B 7 - - SIFOX R2A Ditto including 1+1 protection
SUBAT 461 3.2a COZBU 103 461/1 R1C 7 - - SUBAT R1B Trunk IF for ISDN NT1
4 ports, 4B3T line code
SUBLA 328 3.3a COZBU 103 328/1 R1A 7 - - SUBLA R3A Subscriber line IF PSTN
12 ports a/b, imp. complex, hot
line


R5A Software
SUBLA 334 4C COZBU 103 334/1 R1A 7 - - SUBLA R4A Subscriber line IF PSTN
12 ports a/b, imp. complex,
hot line, auto ring down
SUBLA 336 4C COZBU 103 336/1 R1A 5 - - SUBLA R4A Subscriber line IF PSTN
12 ports a/b, imp. complex,
ILoop = 44 mA
SUBL6 327 3.3a COZBU 103 327/1 R1A 6 - - SUBL6 R3A Subscriber line IF PSTN
12 ports a/b, imp. 600 Ohm
hot line
SUBL6 335 4C COZBU 103 335/1 R1A 6 - - SUBL6 R4A Subscriber line IF PSTN
12 ports a/b, 600 Ohm,
SUBUK 333 3.3a COZBU 103 333/1 R1C 12 - - SUBUK R3C Subscriber line IF (UK/LINTE)
12 ports a/b, hot line
SULIC 391 ≤ 2.5.d COZBU 103 391/5 R1F 7 - - SULIC R1C Trunk IF for NTU
SULIC 392 ≤ 2.5.d COZBU 103 392/2 R1D 7 - - SULIC R2A Ditto including 1+1 protection
SULIC 396 ≤ 2.5.d COZBU 103 396/1 R1B 7 - - SULIC R3A Ditto including PM
SULIS 393 ≤ 2.5.d COZBU 103 393/2 R1D 7 - - SULIS R1A Trunk IF for ISDN NT1
TUNEL 481 ≤ 2.5.d COZBU 103 481/1 R1C 7 - - TUNEL R1A Electrical IF 8 Mbit/s
2 el. ports 8 Mbit/s, G.703/75 Ohm
TUNOL 299 ≤ 2.5.d COZBU 103 299/1 R1C 1 - - TUNOL R2B Optical/electrical transmission IF:
- 1 optical 8 Mbit/s interface
- 4 el. 2 Mbit/s front IFs (G.703)
- UBUS and front access for the
4 electrical 2 Mbit/s IFs,
120/75 Ohm
- 2 to 8 Mbit/s DMX
- Cross connect configurable
- Overhead channel
TUNOP 292 ≤ 2.5.d COZBU 103 292/6 R1C 7 - - TUNOP R1E Opt. IF 8 Mbit/s single and multi-
mode fibres
2 ports
NOTE: TUNOP 292 versions
3.3564.292/04 (V1.3)
and
3.3564.292/05 (V1.4)
cannot be used with
UMUX 1500. Version
3.3564.292/06 (V1.4)
cannot be used with
UMUX 1100(E)/1300
TUNOS 293 ≤ 2.5.d COZBU 103 293/3 R1G 7 - - TUNOS R1D Opt. IF 8 Mbit/s
single mode fibres 1300 nm
2 ports
TUNOS 294 ≤ 2.5.d COZBU 103 294/3 R1H 7 - - TUNOS R1D Opt. IF 8 Mbit/s
single mode fibres 1500 nm
2 ports
ULCAS 471 ULCAS R1C For more information please
contact ATR


R5A Software
UNIDA 431 ≤ 2.5.d COZBU 103 431/2 R1C 6 - - UNIDA R1B Data interface V.24
4 ports
4 ports
UNIDA 433 ≤ 2.5.d COZBU 103 433/2 R1C 6 - - UNIDA R1B Data interface V.11/X.24
4 ports
2 ports
4 ports
UNIDA 436 4C COZBU 103 436/1 R1A 5 - - UNIDA R1C Data interface X.24/V.11
4 ports
without Subrate Multiplexing
UNIDA 437 4C COZBU 103 437/1 R1A 5 - - UNIDA R1C Data interface V.35
4 ports
without Subrate Multiplexing
UNIDA 438 4E COZBU 103 438/1 R1A 5 - - UNIDA R1D Data interface X.24/V.11
4 ports
- without Subrate Multiplexing
- with Scrambler (ITU-T V.38)
COZBU 103 438/11 R1A 5 UNIDA R1D Ditto with
- PM (= option 2)
Note: With the active scrambler
PM is not available
- Point-to-Multipoint (= option 3)
- PM
- Point-to-Multipoint
(PM + P-to-MP = options 2 + 3)
Note: With the active scrambler
PM is not available

HK: Hardware Key
Please note that:
• Partial inventory data means that the units only provide a
part of the standard information for inventory management.
• If the UMUX 1500 implementation of a particular function
(unit) goes with functional restrictions compared to the
features quoted in the unit description, the table shows the
limitations.
• The tables include the version of the "Bootloader" software.
The inventory function of the EM can read the data (if
applicable).
• New UBUS units and some of the existing UBUS units
feature SW download as well.

• The UMUX 1500 does not support the SUBL<x> R2.x

versions. They are fully replaced as follows:
SUBL6 326 → 327
SUBLA 322 → 328
SUBUK 332 → 333
• You can compose the name of the files with (compressed)
"Name": ISBUQ
"Version": R2B00
"Filename": ISBUQ_R2.B00

Special units Tab. 9-6: Functions and software of the UMUX 1500 special units
(UCST R5A)

Template T.I.U. Name Version HK Name Version Name Version
ALCAR 804 ≤ 2.5.d COZBU 103 804/1 R1B 7 - - ALCAR R1A Alarm unit with 24 binary inputs/
4 command outputs and 4 ports
for serial communication
ETHUB 193 4E COZBU 110 193/1 R1A 1 - - - - Ethernet Hub with 5

10/100BaseT interfaces (front
access). The ETHUB provides the
full UMUX inventory and alarm
and IFs.
ETHUB 194 4E COZBU 110 193/1 R1A 1 - - - - Ditto.
The ETHUB 194 is included with
the Service Pack 02 and provides
a separate alarm for failures of
the local 3.3 VDC power supply.
LECAF 070 4E COZBU 402 070/1 R1A 10 - - LECAF R6A DSL transmission IF (CAP)
R1B 2 HDSL IFs for twisted pairs.
- Data IF with front access, no
highway access
- Support of LECAR
- Support of MUSIC 100
- Support of the regenerator
- equal to LECA2 056 but
without backplane access.
MAGIC 317 ≤ 2.5.d COZBU 103 317/1 R1A - - - For more information please
contact ATR
RIGEN 241 ≤ 2.5.d COZBU 103 241/16 R1A 5 - - - - Ringing Generator f. SUB<xx>
16 Hz, b-wire
COZBU 103 241/4 R1F 5 - - - - Ringing Generator f. SUB<xx>
25 Hz, b-wire
COZBU 103 241/50 R1A 5 - - - - Ringing Generator f. SUB<xx>
50 Hz, b-wire
RIGEN 251 ≤ 2.5.d COZBU 103 251/4 R1E 5 - - - - Ringing Generator
25 Hz, a-wire
TUNOF 284 4E COZBU 110 284/1 R1A 3 - - TUNOF R2B Optical/electrical transmission IF:
- 1 optical 8 Mbit/s interface
- 4 el. 2 Mbit/s front IFs (G.703)
- 2 to 8 Mbit/s DMX
- Front access for the 4 electrical
2 Mbit/s IFs, 120/75 Ohm
- Overhead channel

HK: Hardware Key
Empty fields are "not applicable" for the corresponding
function.

Ordering information
Please contact ATR or your sales representative for detailed
information on ordering and product availability.
Cable cross-references Tab. 9-7: Cross-references for unit cables used with the
UMUX 1500/1200
Unit cables used with the UMUX 1500/1200 Max. length State Doc. reference ATR reference
available [m] ordering number
COBU<X>: Synchronisation IFs 150 COBUX/C1.1-1 TSRBU 201 194/5000

ESI-1/ESO-1,2,3 (75 Ohm) (5m)
COBU<X>: Synchronisation IFs 150 No longer COBUX/C1.1-2 TSRBU 201 205/5000
ESI-1,2/ESO-1,2 (75 Ohm) (5m) supported
COBU<X>: Synchronisation IFs 150 New COBUX/C1.1-3 TSRBU 201 112/5000
ESI-1/ESO-1,2,4 (75 Ohm) (5m)
ESI-1,2/ESO-1,4 (75 Ohm) (5m)
ESI-1/ESO-4 (120 Ohm) (5m)
COBU<X>: Alarm IFs 50 COBUX/C1.2 TSRBU 102 195/5000

4 In/UA, NUA Out (5m)
COBU<X>: Q1-master interface (5m) 50 COBUX/C1.3 TSRBU 302 197/5000
COBU<X>: Q1-(slave) interface (5m) 50 COBUX/C1.4 TSRBU 302 197/5000
COBU<X>: F-interface 10 COBUX/C3.1-1 TSRBU 102 206/5000
Control unit – PC/computer [X] (5m)
Control unit - Modem [=] (5m)
COBU<X>: F- interface 15 COBUX/C3.1-3 TSRBU 102 216/540
Control unit - SIFOX cable adapter (0.5)
COBU<X>: QX-interface RJ-45 10 COBUX/C2.1-1 TSRBU 302 006/6000
Control unit - Hub [=] (6m)
FANUV: Power supply + alarms fixed FANUV/C1.1-1 TSRBU 101 023/330

for UMUX 1500 subracks
FANUV: Power supply + alarms fixed New FANUV/C1.1-2 TSRBU 101 026/330
for UMUX 1500 subracks with red. control units
ISBUQ: BRA subscriber line IFs 180 ISBUQ/C1.1 TSRBU 302 204/5000
8 IFs (5m)
ISBUT: BRA subscriber line IFs 180 New ISBUT/C1.1 TSRBU 302 204/5000
8 IFs (5m)
LEMU6: CAP line IFs 180 LEMU6/C1.1 TSRBU 302 201/5000
6 IFs (5m)
LEMQ6: HDSL line IFs 180 New LEMQ6/C1.1 TSRBU 302 201/5000
6 IFs (5m)

LESA8: HDSL line IFs 180 New LESA8/C1.1 TSRBU 302 210/5000
8 IFs (5m)
LESAP: HDSL line IFs 180 New LESA8/C1.1 TSRBU 302 210/5000
8 IFs (5m)
LOMIF: 2 Mbit/s IFs, 75 Ohms 120 LOMIF/C1.1-1 TSRBU 102 199/5000
8 IFs (open ended cable) (5m)
LOMIF: 2 Mbit/s IFs, 75 Ohms 10 New [501] TSRBU 102 208/760
cable with BT43 for 75 Ω patch panel 1500
8 IFs (<x>m) 2900
5000
10000
cable with Minicoax for 75 Ω patch panel
8 IFs (1.7m)
8 IFs (5m)
LOMI4: 2 Mbit/s IFs, 75 Ohms 120 LOMIF/C1.1-1 TSRBU 102 199/5000
LOMI4: 2 Mbit/s IFs, 75 Ohms 10 New [501] TSRBU 102 208/760
4 IFs (<x>m) 2900
5000
10000
4 IFs (1.7m)
LOMI4: 2 Mbit/s IFs, 120 Ohms 120 New LOMIF/C1.1-2 TSRBU 302 200/5000
4 IFs (5m)
PCONV: 2 Mbit/s IFs, 75 Ohms 120 PCONV/C1.1-1 TSRBU 201 202/5000
2 IFs (5m)
PCONV: 2 Mbit/s IFs, 120 Ohms, 120 PCONV/C1.1-2 TSRBU 302 203/5000
2 IFs (5m)
PHLC<X>: Subscriber line IFs 180 PHLC1/C1.1 TSRBU 301 198/5000
30 user ports (5m)
PHLC3: Subscriber line IFs 180 PHLC3/C1.1 TSRBU 301 200/5000
10 user ports (5m)
SYNAM: 2 Mbit/s IFs, 75 Ohms 120 New SYNAM/C1.1-1 TSRBU 102 199/5000
8 IFs (5m)
8 IFs (5m)
SYNIC: electrical STM-1 IFs 120 New SYNIC/C1.1-1 TSRBU 201 118/5000
1 IF (requires 2 coaxial cables) (5m)
SYNIF/SYNIO: optical STM-1 IFs E2000 HRL 1 SYNIF/F1.1-1 TOKBU 101 010/1000
opt. adapter cable E2000 HRL to FC/PC
1 IF (requires 2 optical cables) (1m)
Please note that:

• The specified maximum length is a commercial length
limitation and not a physical limitation! For physical
limitations, refer to the technical specifications of the
interface.

• The standard lengths are

− 5 m (= 5000 mm) for electrical cables is
− 1 m (= 1000 mm) for optical fibres.
It is possible to order cables with other lengths up to the
specified maximum length available. The length must be a
multiple of 1 m.
• The COBUX/C2.1-<X> cables are shielded cables with RJ-45
connectors:
- [=]: Signal connection as for standard ISDN cables
(4 pairs, connected 1:1)
Suited to connect the QX-interface to a LAN or
HUB.
- [X]: Signal crossed
Suited to directly connect the Ethernet-interface
of the COBU<X> to a PC/computer.
Selected accessories The table below shows important accessories for the UMUX 1500 system:
Tab. 9-8: Accessories UMUX 1500
Accessory Description Name State Doc. reference ATR reference

ordering number
75 Ohm patch panel frame 2 HU for the U1500-AC New [501] 1/BGKBU 202 101/1
UMUX 1500 and UMUX 1200.
Supported adapter cables
- TSRBU 102 208/<x>
- TSRBU 102 214/<x>
Connector locks BFD01-AC [302] NTMBU 901 101/100
(for connector sets, 100 pieces)
ETSI adapter set 19" to ETSI, 1 HE BFD01-AC [302] BFYBU 201 106/2
(for UMUX 1500)
(for UMUX 1500 and connector field)
ETSI adapter set 19" to ETSI, 8HU BFD01-AC [302] BFYBU 201 106/1
(for UMUX 1500)
ETSI adapter set 19" to ETSI, 10HU BFD01-AC [302] BFYBU 201 106/4
(for UMUX 1500)
48VDC Fan unit variable 1U FANUV-CO [302] BPDBU 101 02/1

(for UMUX 1500)
Heat deflection shield 19" 2HU BFD01-AC [302] BFYBU 150 103/1
For more information, please contact your ATR sales

representative.


Belpstrasse 37
Tel.: ++41 31 999 1303
Fax: ++41 31 999 1874
Technical support: ATR help desk

Tel.: ++41 31 999 3000
Fax: ++41 31 999 1874
Time tables Official business office hours ATR: Monday - Friday

08h00 - 12h00 CET
13h00 - 17h00 CET
Help desk:
Open for customers
• without Service Level Agreement: Official business office hours.
• with Service Level Agreement: According to the terms of the
service level agreement.

ascom

system.

(UCST R5A)

UMUX 1200


Order number:
Belpstrasse 37
CH-3000 Bern 14
Switzerland © July 2001 by Ascom Transmission AG
ascom
Table of contents i
System Summary 1- 1
Overview 1- 1
Introduction to the UMUX 1200 1- 1
Main features 1- 2
Architecture 1- 2
Cross connect 1- 2
Installation 1- 3
Compatibility with other UMUX 1- 3
Summary of features 1- 3
Views of the UMUX 1200 1- 5
Compatibility with the UMUX system family 1- 6
Services 1- 8
Multiservice Access Multiplexing 1- 8
Access and Transmission Device for GSM 1- 8
IP Digital Subscriber Line Access Multiplexer 1- 8
High density of user ports 1- 8
Channel Bank 1- 8
Open Network Provisioning 1- 9
PRA related functionalities 1- 9
STM-1 Access 1- 9
Hubbing 1- 9
Dedicated networks 1- 9
Bridging, routing and frame relay 1- 9
V5 Multiplexing 1- 10
Interfaces and units 1- 11
Synoptic overview of interfaces and units 1- 11
Interfaces 1- 12
Tributary 1- 13
Aggregate 1- 13
Power 1- 13
Auxiliary 1- 13
EN/LZVBU 222 212/1 RA UMUX 1200 Technical System Description iii

Units 1- 14
Traffic units 1- 14
Control units 1- 15
System and management functions 1- 16
Cross connection 1- 16
System capacity 1- 16
Subrack and units 1- 16
UBUS 1- 16
PBUS 1- 16
SBUS 1- 16
Management 1- 17
Overview 1- 17
Element managers UCST and UNEM 1- 17
Management access and interfaces 1- 19
Compatibility 1- 22
Internal interfaces 1- 22
System compatibility of functions 1- 22
System functions 1- 22
System compatibility of units 1- 23
UBUS units 1- 23
PBUS units 1- 23
SBUS units 1- 24
Control units 1- 24
Power units 1- 24
Tributary and aggregate interfaces 1- 24
General 1- 24
PSTN 1- 24
2 Mbit/s 1- 25
STM-1 1- 25
Management 1- 25
Management systems 1- 25
Interfaces 1- 25
Communication 1- 26
Compatibility with previous releases 1- 27
NE configuration 1- 27
Functions and units 1- 27
System Architecture 2- 1
Block diagram 2- 1
Bus Structures and Cross Connection 2- 2
PBUS 2- 3
iv UMUX 1200 Technical System Description EN/LZVBU 222 212/1 RA

UBUS 2- 3
SBUS 2- 4
System control 2- 5
Communication between controllers 2- 6
Synchronisation and system timing 2- 6
Power supply 2- 6
Traffic units 2- 7
Subrack 2- 7
Implementation of functional blocks 2- 8
Functions and features 2- 8
Architecture and functional blocks 2- 8
Control units 2- 8
Power units 2- 9
Traffic units 2- 9
PBUS units 2- 9
SBUS units 2- 10
UBUS units 2- 10
Subrack 2- 10
Function 2- 10
Slots in the subrack 2- 11
Limiting factors for the implementation of units 2- 13
Functional Descriptions 3- 1
Traffic units 3- 1
Control units 3- 1
COBU<X> units 3- 1
COBUX/COBUV 3- 1
COBUL 3- 1
COBUQ 3- 1
Overview of specific technical data of control units 3- 2
Power units 3- 4
POSUS power unit 3- 4
POSUA power unit 3- 4
Special units 3- 5
Redundancy and protection 3- 5
Performance Monitoring 3- 6
EN/LZVBU 222 212/1 RA UMUX 1200 Technical System Description v

Management Functions 4- 1
Mechanical and EMC/ESD 5- 1

Construction 5- 1
Overview 5- 1
The subrack 5- 1
The installation 5- 2
Cooling 5- 3
UMUX 1200 subrack 5- 4
Design and dimensions 5- 4
Partitioning and backplane arrangement 5- 4
19-inch installation option with cable tray 5- 6
ETSI adapters 5- 7
Wall mounting option with cable tray 5- 9
Fan unit (optional) 5- 11
Air filter (optional) 5- 12
BATMO battery package (optional) 5- 12
Plug-In Units 5- 15
Cabling and connections 5- 16
Signal cables 5- 16
Cable tray and grounding bar 5- 16
Rack mounting 5- 17
Wall mounting 5- 18
Connection panel 5- 19
ESD / EMC and grounding 5- 19
Operation and Maintenance 6- 1

Performance control and monitoring 6- 1
Test functions and diagnostics 6- 1
Upgrading 6- 1
Manipulation of the equipment 6- 2
System labelling 6- 2
System Specification 7- 1
Functional specification 7- 1
Technical specification 7- 2
Architecture 7- 2
System 7- 2
PBUS 7- 2
vi UMUX 1200 Technical System Description EN/LZVBU 222 212/1 RA

UBUS 7- 2
SBUS 7- 3
Element Manager 7- 3
Management communication structures 7- 3
Routing 7- 4
Cross connections and delays 7- 4
PBUS cross connect 7- 4
Traffic signal delays PBUS and UBUS 7- 4
Traffic signal delays SBUS and PBUS 7- 5
Signal interfaces 7- 5
Traffic interfaces 7- 5
Units implemented 7- 5
Synchronisation interfaces inputs 7- 5
Synchronisation interfaces outputs 7- 6
Access to SOH of STM-1 7- 7
Power interfaces 7- 7
DC interface 7- 7
AC interface 7- 8
DC battery backup interface 7- 8
Internal power supply 7- 8
Power conversion 7- 8
Protection and life insertion: 7- 8
Power dissipation 7- 9
Vertical installation 7- 9
Horizontal installation 7- 9
Subrack 7- 9
Construction 7- 9
Capacity and slots 7- 10
FANU2 fan unit 7- 10
Construction 7- 10
Specification 7- 10
Alarm interface 7- 10
Power supply 7- 10
BATMO battery package 7- 11
Battery case 7- 11
Batteries 7- 11
EMC 7- 11
Product family standard 7- 11
Emission 7- 11
Immunity 7- 11
ESD 7- 12
Safety 7- 12
Ambient conditions 7- 12
Storage 7- 12
Transport 7- 12
EN/LZVBU 222 212/1 RA UMUX 1200 Technical System Description vii

Operation 7- 12
Mechanical parameters 7- 12
Dimensions 7- 12
Weight 7- 13
Installation 7- 13
Subrack 7- 13
BATMO battery package 7- 13
Connection of signals 7- 13
Connection of power supply 7- 14
Dependability 7- 14
Availability 7- 14
MTTF 7- 14
Implementation and Application Notes 8- 1

Configuration of the subrack 8- 1
Summary of limiting factors for unit implementation 8- 1
General all units 8- 1
Synoptic overview 8- 2
Control units and power supply 8- 3
Control Units 8- 3
POSUS DC/DC converter 8- 3
POSUA AC/DC converter 8- 3
UBUS 8- 4
UBUS structure 8- 4
UBUS access 8- 5
UBUS units and UMUX 1200 8- 6
Selection of UBUS highways and connection points 8- 6
Summary of UBUS access of units 8- 7
PBUS 8- 7
PBUS structure 8- 7
PBUS access 8- 8
SBUS 8- 9
SBUS structure 8- 9
SBUS access 8- 10
Mechanical and thermal 8- 12
Unit width 8- 12
Restrictions of unit implementation 8- 12
Summary of rules for unit implementation 8- 12
Templates for unit implementation 8- 14
Standard configurations 8- 14
Cross connect 8- 15
DXC 48 x 2 Mbit/s 8- 15
DXC 40 x 2 Mbit/s 8- 16
2 Mbit/s services 8- 17
STM-1 TM 24 x E-12 with MSP 8- 17
STM-1 TM 32 x E-12 without MSP 8- 18
STM-1 TM for 16 x 2 Mbit/s without MSP 8- 19
viii UMUX 1200 Technical System Description EN/LZVBU 222 212/1 RA

STM-1 TM for 8 x E12, 8 x 2 Mbit/s and 1 x 10BaseT, no MSP 8- 20

Multi-service applications 8- 21
STM-1 TM for multiple data services, no MSP 8- 21
CAP/HDSL access for multiple data, PSTN and ISDN services 8- 22
Optical access for multiple data, PSTN and ISDN services 8- 23
xDSL access point 8- 24
30 x MSDL 8- 24
STM-1 TM 18 x MSDL, no MSP 8- 25
Generic template for unit implementation 8- 26
Power consumption and heat dissipation 8- 27
Calculating power dissipation 8- 29
IP addresses 8- 30
Calculating the number of UMUX spare units 8- 30
System and Ordering Information 9- 1

Functions and unit software ESW 9- 1
Element manager 9- 1
Control and power units 9- 2
PBUS units 9- 3
SBUS units 9- 3
UBUS units 9- 4
Special units 9- 4
Ordering information 9- 5
Cable cross-references 9- 5
Selected accessories 9- 7
Time tables 9- 8
EN/LZVBU 222 212/1 RA UMUX 1200 Technical System Description ix

ascom
System Summary 1
Overview
Introduction to the The UMUX1200 is a new member of ATR's Multiservice Access System
UMUX 1200 family. The UMUX 1200 is a flexible and compact access system with inte-
grated transmission capabilities.
The UMUX 1200 is a network element of medium capacity in the access
network and particularly suited as
• Multiservice Access System at the customer premises of medium to
large enterprises for the network access via optical fibres.
• Transmission Device in the base stations of mobile networks GSM
(Global System for Mobile applications) and UMTS (Universal Mobile
Telecommunications System) which links the local traffic to the net-
work controllers.
• IP Digital Subscriber Line Access Multiplexer for Internet Service
Providers at small remote locations.
The design of the UMUX 1200 allows versatile equipment installation ver-
tically and horizontally in racks and cabinets. It can operate directly from
the local DC power supply or mains with optional battery backup for AC
powering. The powering options and the mechanical construction of the
UMUX 1200 allow you to install the equipment in a non-telecom envi-
ronment.
The UMUX 1200 relies on the system design of the UMUX 1500 and pro-
vides a compact subrack with 8 slots for traffic, control and power units
instead of the 21 slots of the UMUX 1500 subrack.
This still offers a high handling capacity for aggregate traffic and all the
new functionalities and services such as the handling of SDH signals, the
V5.x service provisioning and IP service capabilities.
The UMUX 1200 and the UMUX 1500 use the same types of control units
and provide a large set of integrated transmission interfaces (optical fibres
and copper based). These interfaces allow you to connect the network
element directly to your transport backbone or to build a transport net-
work (limited transmission capacity) with UMUX 1500 and UMUX 1200.
The STM-1 interface (electrical and optical) is the interface with the high-
est traffic capacity that is available with the UMUX 1200 and UMUX
1500. It is possible to configure the UMUX 1200 as a terminal Access Sys-
tem or as an add and drop multiplexer for the STM-1 SDH signals.
EN/LZTBU 220 112/1 RA UMUX 1200 Technical System Description 1-1

ascom System Summary
This implies the ability to terminate high capacity aggregate signals (SDH
STM-1) down to 64 kbit/s circuits and to provide physical user service in-
terfaces (POTS, ISDN, data leased lines). As a multi-service access system,
the UMUX 1200 bridges the gap between the individual subscriber service
and the backbone network.
The UMUX 1200 features the F- and the Q1-interface for local and remote
management access, which are both functionally compatible with the cor-
responding interfaces of the UMUX 1100(E) and UMUX 1300. Addition-
ally, the UMUX 1200 provides the QX-interface. This is an Ethernet inter-
face (10BaseT) which allows management accesses via LANs.
The key to present and future network operation is an integrated Net-
work Management. The management systems UNEM and UCST manage
the UMUX 1200 as well as the other members of the UMUX (e.g.
UMUX 1500, UMUX 1300 and UMUX 1100(E)) and the DSL PRODUCTS
family. With the UCST and UNEM, the management platform provides
both, management for networks (UNEM) and NEs (UCST).
For the remote management of NEs with the UCST and UNEM, the UMUX
1200 provides the ECC (Embedded Communication Channel). The ECC is
a high performance in-band data channel, which allows the implementa-
tion of versatile in-band networks for the management communication of
the UMUX 1500 and 1200.
If required, it is possible to connect the UMUX 1200 via the SIFOX to the
EOC (Embedded Operation Channel), the management communication
network of the UMUX 1300 and UMUX 1100(E). The implementation of
the SDH functionality with the UMUX 1500 and 1200 allows the tunnel-
ling of the PDH ECC via SDH transmission sections.
Main features
Architecture The UMUX 1200 implementation is based on a slim subrack and the stan-
dard control units COBU<X> (COBUX, COBUV and COBUL). You can
implement redundancy for both the control unit and the power supplies.
A set of optimised control units (COBUX, COBUV and COBUL) and multi-
ple powering options offer an economic choice for a specific application
without restrictions on future system expansions and upgrades.
A set of traffic units with a new design satisfies the enhanced require-
ments for capacity and functions for the multi-service applications with
the UMUX 1200. These units provide access to the high capacity PBUS.
Units with SDH functionality provide access to the SBUS and (if applicable)
also to the PBUS. All new units feature software download (except for the
power supply and fan units).
Cross connect The UMUX 1200 enhances the UMUX Access System portfolio with 1/0,
1/1 cross connect and SDH transmission capacity in a compact versatile
subrack.
The UMUX 1200 is capable of multiplexing and cross connecting both n x
64 kbit/s and 2 Mbit/s signals. The cross connect is implemented on the
PBUS, which is the typical BUS structure of the UMUX. The cross connect
capacity is in total 128 x 2 Mbit/s.
The plesiochronous 2 Mbit/s signals are either switched transparently or
demultiplexed and switched as n x 64 kbit/s signals. Structured synchro-
1-2 UMUX 1200 Technical System Description EN/LZTBU 220 112/1 RA

nous signals are terminated and synchronised by the local system clock.
The cross connect handles unstructured 2 Mbit/s signals for transparent
cross connecting.
The UMUX 1200 also provides UBUS access with a capacity of 2 times 4 x
2 Mbit/s for signals with and without signalling.
Synchronisation The UMUX 1200 provides PETS and SETS (with STM-1 interfaces only) for
system synchronisation.
Installation The UMUX 1200 is the most compact of the UMUX Access Systems and
allows flexible installation in 19-inch or ETSI racks and on walls or in cabi-
nets.
Compatibility with other The UMUX 1200 offers backward compatibility with the proven UMUX
UMUX system philosophy and traffic interfaces and corresponding units. The
COBU<X> control units have been specially designed for the new UMUX
Access Systems and cannot be used with the UMUX 1100/1300.
The open system architecture allows you to use all the UMUX traffic inter-
faces (data, voice, V5.x, xDSL and optical fibres) with the UMUX 1500 and
UMUX 1200 network elements.
Summary of features You can operate the UMUX 1200 as a remote service access point or small
flexible Access System in any type of network (i.e. linear, star, ring and
meshed). The new network element's main features are:
• Modular design for the implementation of flexible NEs.
• Compact subrack with adapters for 19-inch and ETSI installation prac-
tice.
It is possible to install the UMUX 1200 subrack in vertically and hori-
zontally oriented rack set-ups; thus the UMUX 1200 allows horizontal
and vertical installation.
• The UMUX 1200 provides an adapter which allows direct wall mount-
ing (vertical) and the installation cabinets without rack infrastructure.
• Integrated fan option for forced air convection (e.g. required for
subracks when operating in the horizontal position).
• DC and AC powering with integrated charger for an external backup
battery. The BATMO battery package is an option for AC powering
with the POSUA power converter unit.
• Use of highly integrated circuits for a high density of traffic interfaces.
• Software download for unit software ESW (Embedded Software).
• Cross connect of 64 kbit/s and n x 64 kbit/s signals.
• Cross connect of 2 Mbit/s signals.
• Highly dependable and single point failure tolerant cross connect
• Set of optimised control units

• Local voice & data interfaces

• Voice and data interfaces for remote access
• V5.2 and V5.1 functionality
• Custom parameter sets for V5.x and PSTN applications
• Transmission interfaces and integrated LTE
• DSL transmission interfaces
• High speed IP Internet/Intranet access via xDSL and the UMUX network
• Termination and add/drop functions for STM-1 traffic signals
• Optical STM-1 interfaces S1.1, L1.1 and L1.2
• Electrical STM-1 interface
• SETS and PETS
• ECC (Embedded Communication Channel) for enhanced management
communication
• Full redundancy for system control possible
• Redundancy for power supply including battery backup for AC pow-
ering possible
• Diagnostic functions (cross connect, synchronisation, data)
• Configuration of conference circuits for traffic signals

Views of the UMUX 1200 The UMUX 1200 is based on a compact subrack with front access for all
signal and power cables. The subrack is prepared for the fan unit option
and the implementation of an air filter. A removable cover closes the front
of the subrack.
The construction of the subrack and the cable connections provide Fara-
day cage-like EMC characteristics, provided that the front cover is installed
and the signal cables have been installed and shielded as instructed.
A set of adapters allows you the installation of the UMUX 1200 subrack in
19-inch and ETSI racks. It is possible to install the subrack horizontally or
vertically in vertically or horizontally oriented racks.
A wall-mounting adapter allows you to install the UMUX 1200 vertically
on walls or in cabinets without rack infrastructure.
The adapters provide at the same time the cable tray functionality, which
allows an easy installation of the signal cables for each type of installation.
Figure 1-1: UMUX 1200 subrack with adapters/cable tray

for horizontal and vertical 19-inch rack installation
(with and without front cover)

Two optional ETSI adapters allow you to install the 19-inch set-up of the
UMUX 1200 subrack in an ETSI rack.
Figure 1-2: UMUX 1200 subrack with adapter for vertical wall
mounting
(with and without front cover)
You can use the same adapter to install the UMUX 1200 in outdoor or in-
door cabinets without 19-inch or ETSI mounting system.
The subrack accepts all the PBUS and SBUS traffic units as well as old and
new UBUS traffic units.
Compatibility with the The UMUX 1200 is compatible with the other members of the UMUX
UMUX system family Access System, that is, to the UMUX 1500, UMUX 1100(E) and UMUX
1300. Compatibility means that the UMUX 1200 and its interfaces are
compatible with most of the units, with the transmission and traffic inter-
faces and with all the management communication structures.
Like the other members of the UMUX family, the EM UCST and the NEM
UNEM manage the UMUX 1200. It is possible to add the UMUX 1200 to
existing UMUX networks and integrate the new Access System into their

The UMUX 1200 provides with the ECC (Embedded Communication

Channel) the performance–enhanced, management communication of
the UMUX 1500 system but is still fully compatible with the existing
communication principles and structures. The ECC is however not avail-
able for the UMUX 1100(E) and the UMUX 1300.
Figure 1-3: UMUX 1200 and UMUX Access Systems
Transport
Network
PSTN
SDH PDH
2 Mbit/s
- electrical
STM-1
- optical
PDN
Network & 8 Mbit/s
- electrical
Element Manager - optical
(HP OpenView)
UNEM
UMUX 1500 UMUX 1200
xDSL 10BaseT 8 Mbit/s or

2 Mbit/s
UCST
Element
Manager
(PC base)d
MUSIC 100 NTU
Desktop
Remote LAN POTS Data Access

LAN Access
10BaseT ISDN n x 64 kbit/s
10BaseT 2 Mbit/s
PRA
The figure above shows the hierarchical relationship between the mem-
bers of the new UMUX Access System family. Ideally, you implement the
Transport Network so that it is based on the UMUX Access Systems (man-
agement of NEs).
For an overview of the interfaces in the UMUX 1200, refer to the figures
in the paragraph "Synoptic overview of interfaces and units".

Services
The flexible multi-service Access System UMUX 1200 features a powerful
cross connect for the signal levels 1/1 and 1/0. It is easy to tailor the
UMUX 1200 for the following services and functions:
Multiservice Access Multi- The UMUX 1200 provides the multiplexing of tributary signals into aggre-
plexing gate signals (e.g. STM-1 signals). The UMUX 1200 benefits from the vari-
ous transmission and traffic interfaces (voice and data) available for the
UMUX Access System family. The UMUX 1200 also supports 2 Mbit/s sig-
nals as tributaries.
The units designed for the UMUX 1500 and 1200 provide a high density
of traffic interfaces.
Access and Transmission The UMUX 1200 provides the multiplexing of the local traffic in the base
Device for GSM stations of mobile networks GSM into aggregate signals (e.g. STM-1 sig-
nals). The aggregate signals are fed via the GSM backbone to the base
station and network controllers.
The UMUX 1200 can provide the same function for UMTS (Universal Mo-
bile Telecommunications System) and GSM for railroads.
IP Digital Subscriber Line The UMUX 1200 is ideally suited to provide the Internet Service access for
Access Multiplexer a small number of IP users at small remote locations.
The AC powering option and the versatile installation of the UMUX 1200
is an asset for the Internet Service Provider.
Cross Connection It is possible, in principal, to implement cross connects with capacities of

up to 128 x 2 Mbit/s or 4096 x 64 kbit/s. However, the units available
today and the maximum of 6 slots available in the UMUX 1200 subrack
for traffic functions, allow you to implement cross connects of up to 48 x
2 Mbit/s.
If required, the UMUX 1200 provides the possibility to protect the cross
connections.
High density of user ports The new units designed for the UMUX 1500 and 1200 provide a high
density of traffic interfaces for V5.x and channel bank applications.
Channel Bank It is possible to implement small channel banks for data services and PSTN
or other voice services.

Open Network Provisioning The cross connect of the UMUX 1200 allows the transparent switching of
structured and unstructured 2 Mbit/s signals, thus providing fully open
transport and access networks for payload traffic.
PRA related functionalities Due to the transparency of the UMUX 1200 for 2 Mbit/s traffic signals,
the UMUX 1200 is suited to providing the termination of ISDN primary
rate access. The UMUX 1200 can provide the NT1-T and LT functional
groups of the PRA with the NT1-T / NT1-U / LT-U / LT-V3 functional
blocks.
STM-1 Access The UMUX 1200 allows the implementation of backbone networks based
on STM-1 and provides all the access multiplexing for STM-1 SDH network
access.
The UMUX 1200 allows the implementation of:
• The optical STM-1 interface implemented as S1.1, L1.1 and L1.2.
• The electrical STM-1 interface (according to G.703)
Hubbing The UMUX 1200 can serve as a hub for other UMUX Access Systems.
Dedicated networks The UMUX 1200 can operate as a multi-service Access System, combining
multiple functions per NE (transport, access, cross connection), in dedi-
cated networks such as telecommunication networks of railway and
power companies.
Bridging, routing and frame The UMUX 1200 together with the corresponding unit(s) allow you to
relay implement
• Public bridging and private bridging for remote LAN access
• IP routing with remote LAN access

• Frame Relay switching with remote LAN access

• FRAD function with local routing with remote LAN access
All these functions are also available without local MSDSL transmission in-
terfaces.

V5 Multiplexing
V5.2 protocol processing The UMUX 1200 can operate with the PCON2 and the PCONV unit for
the user port protocol processing of one V5.2 interface. The UMUX 1200
provides V5.2 protocol processing for up to 480 PSTN user ports or 224
ISDN BA user ports.
The two units feature a capacity equivalent to 240 and 480 PSTN user
ports respectively. The units can handle configurations with mixed user
ports (PSTN and ISDN BA) up to the equivalent of 480 PSTN user ports.
The UMUX provides pre-defined custom parameter sets that allow you a
in ANs with a high volume of UMUX 1500 and 1200 Access Systems.
The UMUX 1200 subrack allows the implementation of V5.2 Access Sys-
tems with capacities of up to 60 PSTN or 24 ISDN-BA user ports. The si-
multaneous configuration of PSTN and ISDN-BA user ports is possible; the
total number of interfaces depends on the remaining subrack capacity.
The Access System uses the remaining subrack capacity for aggregate in-
terfaces.
V5.1 protocol processing The UMUX 1200 can operate with the PCON2 and the PCONV unit for
the protocol processing of V5.1 PSTN and ISDN user ports. The two units
feature a capacity of 10 V5.1 and 4 V5.1 interfaces respectively. The units
can handle configurations with mixed user ports (PSTN and ISDN BA).
The UMUX provides pre-defined custom parameter sets that allow you a
in ANs with a high volume of UMUX 1500 and 1200 Access Systems.
The UMUX 1200 subrack allows the implementation of V5.1 Access Sys-
tems with up to 60 PSTN interfaces or 24 ISDN-BA user ports. The simul-
taneous configuration of PSTN and ISDN-BA user ports is possible. The
number of interfaces depends on the remaining subrack capacity.
The Access System uses the remaining subrack capacity for aggregate in-
terfaces.

Interfaces and units

Synoptic overview of inter- While the UMUX 1200 features fewer slots for traffic units than the
faces and units UMUX 1500, it maintains backward compatibility with existing units and
interfaces. The figures below illustrate the interfaces and units provided
with the UMUX 1200 (power interfaces/units are not shown).

Part 1
current sense
Current loop input (16) 2048kHz
voltage sense ALCAR uC-LAN Ext. clock input ESI (2)
Voltage input (8) COBUX, COBUV
Alarm relay output (4) open/close Clock output ESO (3 + 1)
Multipurpose COBUL
(Serial interfaces (4) (RS 232 C)
I/O unit high/low
no highway access) UBUS access Ext. alarm inputs (4)
open/close
PETS (Synchronisation) Alarm relay output (2)
Synchronisation IF
MIB Q1-master interface
Alarm IF 115k2 bit/s
F-interface
Management communicaton Q1-(slave) interface
10Base T
EXLA<X> Qx-interface
2-Wr. a,b
64k
Exchange line IF UCST
a,b-wire: 12 IFs (64k) UNEM
TS16
2-Wr. a,b NEMCA/NEMGE LOMIF
64k
2 Mbit/s G.703/G.704
E&M Voice frequency IF 2 Mbit/s electrical IF
(64k) data: 8 IFs
(E'&M') 4/6-wire: 8 IFs
TS16
SUBLx/SUBUK LOMI4
2-Wr. a,b
64k
2 Mbit/s G.703/G.704
Subscriber line IF 2 Mbit/s electrical IF
a,b-wire: 12 IFs (64k) data: 4 IFs
TS16
LAWA4 10 BaseT
Ethernet: 1 IF
10BaseT LAN
MUSIC 100 (deskt.)
10 BaseT Ethernet device
LEMU6 MSDSL or DSL (Hub with 4 ports)
MSDSL transm. CAP or <X>DSL: 1 IF RS 232 C
2B1Q data: 1 IF Local management
Ethernet: 1 IF 2-Wr. a,b
MSDSL: 6 IFs CAP
GECOD LEMQ6 10 BaseT CAP or DSL transm. or
64k LAN / Ethernet device
2B1Q DSL: 2 IFs
64k MSDSL trans. nx64 kbit/s G.703/G.704
64 kbit data IF Ethernet: 1 IF 2-Wr. a,b data: 1 IF X.21/V.11 or V.35 or V.36
G.703 (64k)
data: 8 IFs MSDSL: 6 IFs 2B1Q
DTE TS16
LESAR (desktop) 2 Mbit/s G.703/G.704, VC-12
CAP or
SIFOX LESA8 2B1Q or
DSL transm. or
64k DSL: 2 IFs nx64 kbit/s G.703/G.704
64k DSL transm. PAM16
Data IF / EOC DSL 1 pair: 8 IFs 2-Wr. a,b
data: 1 IF X.21/V.11 or V.35 or V.36
X.24/V.11 (64k)
data: 4 IFs DSL 2 pairs: 4 IFs CAP, 2B1Q, PAM16
DTE TS16
UBUS
PBUS
Subrates, UNIDA LESAP

nx64k n x 64k DSL transm.
X.24/V.11 Data IF DSL 1/2 pairs: 4 IFs 2-Wr. a,b
V.35, V.36 (64k) Rem. power: 1 IF
data: 2 or 4 IFs CAP, 2B1Q, PAM16
DTE V.24/V.28 TS16
128k/64k
X.21/V.11 2-Wr. a,b SULIC PCONV
V.35 64k V5.x protocol
NTU 2B1Q transm. 2 Mbit/s G.703/G.704
V.24/V.28 144k
DTE 0,6-38,4k Data IF for NTU
2B1Q 2-wire: 8 IFs 64k 2 Mbit/s: 2 IFs
PCON2
V5.x protocol
PHLC1
2-Wr. a,b
Subscriber line IF
a,b-wire: 60 IFs
EXLIC 64k PHLC2

2-Wr. a,b ISDN-U (2B1Q) 64k 2-Wr. a,b
Exchange line IF (16K) Subscriber line IF
144k
2B1Q a,b-wire: 8 IFs 64k a,b-wire: 30 IFs
SULIS 64k PHLC3

S 2-Wr. a,b ISDN-U (2B1Q) 64k 2-Wr. a,b
NT-1 Subscriber line IF (16K) Subscriber line IF
144k
ISDN 2B1Q a,b-wire: 8 IFs 64k a,b-wire: 10 IFs
2-Wr. a,b
ISBUQ (V5) 64k
S
NT-1 ISDN-U (2B1Q) 64k
144k Subscriber line IF (16K)
ISDN 2B1Q a,b-wire: 8 IFs 64k
2-Wr. a,b
ISBUT (V5) 64k SYNAC SYNAM
S
NT-1 ISDN-U (4B3T) 64k SBUS access SBUS access
144k (16K) 2 Mbit/s G.703
Subscriber line IF VC-12 TU-12 / G.703
ISDN 4B3T a,b-wire: 8 IFs channels: 8 data: 8 IFs
64k
EXBAT 64k SYNVA

2-Wr. a,b ISDN-U (4B3T) 64k SBUS access
144k Exchange line IF (16K) TU-12
4B3T a,b-wire: 8 IFs 64k channels: 32
SUBAT 64k SYNOT 155 Mbit/s

S 2-Wr. a,b ISDN-U (4B3T) 64k STM-1 optical IF S1.1
SBUS (1 sector)
NT-1 Subscriber line IF (16K) VC-4 L1.1, L1.2

144k
4B3T a,b-wire: 4 IFs 64k optical: 1 IF G. 957
ISDN
SYNIO 155 Mbit/s

VC-4, SETS L1.1, L1.2
optical: 2 IFs G. 957
SYNIF 155 Mbit/s

VC-4, SETS L1.1, L1.2
optical: 1 IF G.957
SYNIC
STM-1 electrical IF 155 Mbit/s
VC-4, SETS G. 703, koaxial
electrical: 1 IF


Part 2
8 Mbit/s optical
TUNOP 31 x 64k MEGIF 2 Mbit/s G.703/G.704
31 x 64k 2 Mbit/s electrical
8 Mbit/s optcal IF 31 x 64k
8 Mbit/s optical 31 x 64k G.703/G.704
optical: 2 IFs 31 x 64k 2 IFs 2 Mbit/s G.703/G.704
31 x 64k
8 Mbit/s optical 31 x 64k 31 x 64k
TUNOS TUNEL 8 Mbit/s G.703
V.11 OHC 8 Mbit/s optcal IF 31 x 64k 31 x 64k 2 Mbit/s electrical
8 Mbit/s optical optical: 2 IFs 31 x 64k 31 x 64k G.703
electrical: 2 IFs 31 x 64k 31 x 64k 2 IFs 8 Mbit/s G.703
V.11 OHC
UBUS
2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704 TUNOL 31 x 64k LECAF
or
31 x 64k nx64 kbit/s
2 Mbit/s G.703/G.704 opt. / electrical IFs CAP transmission IF G.703/G.704
2 Mbit/s G.703/G.704 optical: 1 IF 31 x 64k 2 DSL IFs X.21/V.11 or V.35 or v.36
2 Mbit/s G.703/G.704 electrical: 4 IFs 31 x 64k 1 data IF
V.11 OHC 2 Mbit/s G.703/G.704
LECA2 (LE2Q2) or
8 Mbit/s optical
transmission IF nx64 kbit/s
CAP
G.703/G.704
2 Mbit/s G.703/G.704 TUNOL (2B1Q) 2 DSL IFs
X.21/V.11 or V.35 or v.36
2 Mbit/s G.703/G.704 opt. / electrical IFs 1 data IF or
2-Wr. a,b
2 Mbit/s G.703/G.704 optical: 1 IF LECA2 UMUX highway access
DSL transm. CAP nx64 kbit/s
2 Mbit/s G.703/G.704 electrical: 4 IFs n x 64k 2 DSL IFs
(1 data IF) 2-Wr. a,b
V.11 OHC CAP
2-Wr. a,b
LE2Q2 10BaseT LAN
2 Mbit/s G.703/G.704 8 Mbit/s optical MUSIC 100 (deskt.)
TUNOF DSL transm. 2B1Q Ethernet device
2 Mbit/s G.703/G.704 opt. / electrical IFs n x 64k DSL (Hub with 4 ports)
2 DSL IFs DSL: 1 IF
2 Mbit/s G.703/G.704 optical: 1 IF 2-Wr. a,b CAP or RS 232 C
(1 data IF) data: 1 IF Local management
2 Mbit/s G.703/G.704 electrical: 4 IFs 2B1Q
2B1Q

V.11 OHC CAP DSL transm. or
(1/2 pairs) DSL: 2 IFs nx64 kbit/s G.703/G.704
2 Mbit/s G.703/G.704 data: 1 IF X.21/V.11 or V.35 or V.36
TUNOR (desktop)
2 Mbit/s G.703/G.704 opt. / electrical IFs
2 Mbit/s G.703/G.704 optical: 1 IF LE2QR (desktop) 2 Mbit/s G.703/G.704
2 Mbit/s G.703/G.704 electrical: 4 IFs DSL transm. or
2B1Q
PRA DSL: 2 IFs nx64 kbit/s G.703/G.704
data: 1 IF X.21/V.11 or V.35 or V.36
LESAR (desktop) 2 Mbit/s G.703/G.704

CAP
DSL transm. or
DSL: 2 IFs nx64 kbit/s G.703/G.704
data: 1 IF X.21/V.11 or V.35 or V.36
Please note that:

• Components with dashed outlines designate units (inter-
faces) that are not yet released or are FUTURE OPTIONS.
• The diagram does not show power interfaces/units and units
with auxiliary functions (e.g. ringing generators, ETHUB unit
etc.).
• The COBUQ control unit is not released for the UMUX 1200!
• The chapter 9 “System and Ordering Information” provides
a detailed list of units and functions released for the
UMUX 1200.
Interfaces
Definition and overview The UMUX 1200 provides the following types of interfaces for signals,
power supply and auxiliary functions:
• Power interface
• Auxiliary interfaces
− Alarm interfaces
− Interfaces for synchronisation
− Interfaces for management communication
Tributary and aggregate interfaces are physically implemented on dedi-

cated units. The auxiliary interfaces (management communication, alarm
and synchronisation) are physically integrated with the control units.

The power interface connects the power converter units of the

UMUX 1200 to the external dc power supply and/or mains.
Tributary Most of the various tributary interfaces provided with the

UMUX 1100/1300 are also available with the UMUX 1200 Access System,
provided the corresponding units have been released for the UMUX 1200.
The corresponding unit descriptions and user guides specify the technical
data and applications. Detailed information on released functions and
units are provided in the chapter 9 "System and Ordering Information"
and in the corresponding release note (e.g. [043] for the UCST R5A).
Aggregate It is possible to use the various aggregate interfaces released with the
UMUX 1100/1300 in the UMUX 1200, provided that the units have been
released for the UMUX 1200 Access System.
The unit descriptions and user guides specify the technical data and de-
scribe the corresponding applications. Detailed information on released
UCST R5A).
Some of these interfaces provide direct LTE functionality.
Power The UMUX 1200 has several powering options with corresponding power
interfaces:
• One power interface for a -48/60 VDC nominal power supply (not
shown in the figures above) integrated in the UMUX 1200 subrack.
• Mains interface provided with the POSUA AC/DC power converter
unit.
This converter is a unit for the UMUX 1200 subrack and takes 2 slots
in the subrack. The AC/DC converter can charge an external backup
battery (implemented with the BATMO battery package) and allows
protection of the UMUX 1200 power supply.
Auxiliary The UMUX 1200 features 4 physical and 2 internal interfaces for man-
agement communication:
• F-interface (physical)
• Q1-(slave) interface (physical)
• Q1-master interface (physical)
• QX-interface (physical)
• PDH ECC (internal)
• SDH ECC (internal)
The F- and the Q1-interfaces are management interfaces based on serial
communication familiar from the UMUX 1100/1300. The QX-interface is a
high speed Ethernet interface that allows the implementation of local
LANs for management communication between the NEs and the EM.
The internal ECC interfaces allow the implementation of inband manage-
ment communication via the UMUX 1500/1200 network. All interfaces

for management communication are implemented physically and logically

on the control unit (availability depends on the selected control unit).
For alarm and synchronisation signals, the UMUX 1200 provides dedicated
interfaces set-up as input or output:
• Alarm signals
− System alarms (output): Relay contacts
− External alarms (inputs): Monitoring of signal levels
• Synchronisation
− Inputs ESI (2) : 2048 kHz
− Outputs ESO (3): 2048 kHz
Units
Definition and overview The modular design of UMUX Access Systems is based on the flexible
combination of specialised units which perform either a specific (system)
function or provide (traffic) interfaces. Depending on requirement, we use
different schemes to group units in the UMUX 1200 environment. Units
are grouped either according to system architecture or according to unit
function:
• The architectural grouping classifies the units as follows
− UBUS units
− PBUS units
− SBUS units
− Control units
− Power units
− Special units
The architectural grouping of units is based on the implementation of

the system and is explained in the chapter 2 "System architecture".
• The functional grouping of units classifies the units as follows
− Traffic units
− UBUS units
− PBUS units
− SBUS units
− Special (traffic) units
− Control units
− Auxiliary units
− Power units
− Special units
The functional grouping is based on interfaces and functions.
Traffic units The traffic units provide interfaces as follows

• Internal interface(s) for the processing of traffic signals
Most of the various traffic units available with the UMUX 1100/1300 can
also be used with the UMUX 1200 Access System, provided the units have
been released with the UMUX 1200 system. The corresponding unit de-
scriptions and user guides specify the technical data and applications. De-
tailed information on released functions and units are provided in the

chapter 9 "System and Ordering Information" and in the corresponding

release note (e.g. [043] for the UCST R5A).
For units already released with the UMUX 1100/1300, rules for system
implementation and features mostly remain the same with the UMUX
1200.
Due to different layouts of the UBUS and different numbers of slots in the
Access System subracks, the UBUS access of corresponding slots might be
different between the systems.
Control units Control units provide interfaces as follows

• Interface(s) for internal access to the UBUS
• Interfaces for synchronisation signals
• Alarm interfaces
• Management interfaces
• Diagnostic interfaces
It is not possible to use the CENCA control units released for the
UMUX 1100/1300 with the UMUX 1200. The UMUX 1200 operate with
the COBU<X> control units of the UMUX 1500. However, the COBUQ is
not available for the UMUX 1200.
Auxiliary units Auxiliary units provide internal system interfaces and special interfaces for
external signals. An auxiliary unit provides a common service for the NE or
special applications for traffic signals:
• Interfaces for (internal) power supply
• Interfaces for (internal) ringing signals
• Interfaces for dedicated diagnostic functions
• Fan units
• Hub unit for management communication
• etc.
The few auxiliary units available are mostly designed for a particular type
of UMUX Access System or subscriber service. Therefore, the units are not
generally released for the UMUX 1200.

System and management functions

Cross connection The cross connect of the UMUX 1200 allows for switching on signal levels
1/1 and 1/0. The switch mechanism is implemented across the PBUS.
It is possible to cross connect structured as well as unstructured 2 Mbit/s
signals "bit and clock transparent". The transparent cross connection of
2 Mbit/s signals is only available with interfaces terminated directly on the
PBUS (e.g. LOMIF/LOMI4) but not with interfaces terminated on the
UBUS. The cross connections can be configured bi-directional, unidirec-
tional or for broadcasting of signals.
The 1/0 cross connect provides the connection of 64 kbit/s and n x
64 kbit/s signals, with and without CAS, such as that provided by the
various traffic units with voice and data interfaces. The cross connect fa-
cility allows you to drop and insert n x 64 kbit/s signals.
The architecture of the PBUS cross connect is resistant to single points of
failures.
System capacity
Subrack and units Because of the compact UMUX 1200 subrack with its 8 slots, you can
implement up to 6 standard width traffic units. Powering options and
redundancy of the control unit further decreases the number of slots
available.
Units with PBUS or SBUS access have a high density of traffic interfaces.
This allows the implementation of far more interfaces per unit as com-
pared to UBUS units with similar types of interfaces.
The UMUX 1200 allows any mix of traffic interfaces and units, provided
that the required bus capacity and/or the slots in the subrack are available.
UBUS The UBUS of the UMUX 1200 allows the implementation of UBUS units
up to the capacity of 8 x 2 Mbit/s, for traffic signals with and without CAS
(similar to the UMUX 1300).
It is not possible to increase this capacity for signals without CAS. The
UBUS capacity available is reduced compared to the maximum capacity
depending on the control unit implemented. The UBUS has no dedicated
PBUS The 1/1 switch architecture is non-blocking with a total capacity of 128 x
2 Mbit/s equivalents with and without CAS.
The capacity available is reduced compared to the maximum capacity de-
pending on the control unit implemented. Because of the compact UMUX
1200 subrack with a maximum of 6 slots available for traffic units, the full
capacity of the cross connect is hardly required.
As an example the maximum of 6 LOMIF units provide 6 x 8 2 Mbit/s traf-
fic signals which require 48 2 Mbit/s cross connections.
SBUS The SBUS of the UMUX 1200 allows the internal handling of the SDH
signals provided via the STM-1 interfaces. The SBUS has no dedicated

Management
Overview The UMUX Access Systems are mainly used as network elements in the
access network. The UMUX equipment also fits into small, dedicated net-
works and operates as stand-alone equipment.
The requirements on the management tool for the commissioning, the
control of operation and maintenance of the NEs depend therefore on the
size of the network and the local requirements for management commu-
nication. In order to provide economic and flexible management commu-
nication, the UMUX provides two software tools, the EM UCST and the
NEM UNEM, as well as various interfaces for management communica-
tion.
Figure 1-6: Management and access of the UMUX with the UCST
and UNEM
UMUX 1500
UMUX 1200
UMUX 1300
UMUX 1100(E)
UMUX 1500
UMUX 1200
UMUX 1300
UMUX 1100(E)
Transport Network
UCST
UNEM Access Network
UMUX 1500
UMUX 1200
UMUX 1300 UMUX 1500
UMUX 1100(E)
UMUX 1200
UMUX 1300
UCST
UMUX 1100(E)
Element managers UCST and Both managers, the UCST and UNEM, can configure and manage the full
UNEM range of the UMUX and DSL equipment. The UCST provides local or re-
mote access to one NE at a time, either for NE configuration or for NE
status and/or performance interrogation. The UCST can be connected to
the NE either locally via corresponding interfaces of the control unit, or
remotely via any of the management communication structures provided

for the UMUX. With the UCST, it is also possible and common practice, to
create configurations off-line, for later download to the NE(s).
The UCST is used for initial commissioning, local NE configuration, local
fault and performance monitoring. The UCST manager is also suited to
manage small access networks.
selection boxes, graphs and mouse selection. It is also possible to establish
the configuration for the NE off-line. The configuration data is only
downloaded to the NE after the establishment of a corresponding man-
agement communication channel between the EM and the NE. The
proper set-up of the management communication for a NE, requires local
commissioning of the NE with the UCST, even if the corresponding con-
figuration has been created off-line.
The UCST R5A software runs on PCs under the Windowsâ 98, ME, NT
and 2000 operating systems.
The UNEM basic package provides administration and simultaneous su-
pervision and performance control for all network elements of medium to
large access networks. Options are available for
• Active sections
Management communication As the figure above shows, the two managers provide various ways to
access the UMUX NEs:
• The UCST can access single UMUX Access Systems directly. The Access Sys-
tem can be a stand-alone system or an NE, which is part of the access
network. The UCST also manages small clusters (networks) of UMUXs. The
UCST accesses the NEs via the transport and/or access network.
• The UNEM manages network elements in a network. The UNEM ac-
cesses the NE either via the transport network or directly via the (ac-
cess) network.
The management communication of UMUX has to cope with different
and changing conditions in the transport and access network. At the
same time, it must remain compatible with implemented network ele-
ments.
The UMUX 1200 management communication is based on TCP/IP. Dedi-
cated communication channels in the access and the transport network
transport the UMUX management communication. Several types of chan-
nel are available in order to maintain the flexibility of management and to
adapt to the requirements of the transport and access network.


− The ECC is an in-band communication structure for the UMUX
1500 and 1200 NEs. The NEs route the communication from the
EM via the ECC structure to the addressed NE. The ECC provides a
bandwidth of up to 2 Mbit/s. The ECC is proprietary and available
for the UMUX 1500 only.
− The transport of the UMUX 1500 and 1200 management commu-
nication via SDH transport networks requires the encapsulation of
TCP/IP into OSI, which is the stack used for the DCN of SDH. This
process is called the tunnelling of TCP/IP in OSI and is available with
the COBU<X> (COBUQ is not available for the UMUX 1200 !) con-
trol units released with the UCST R4D.
• LAN
It is possible to connect the UMUX 1500 and 1200 Access Systems to
a LAN and access them via a LAN from the (N)EM that is connected to
the LAN. The COBU<X> control units provide an Ethernet 10BaseT
LAN interface.
• EOC
The EOC (Embedded Operation Channel) is used for access networks
with mixed types of UMUX equipment. The EOC is a proprietary com-
munication structure for UMUX Access Systems based on the SIFOX
unit. The EOC requires a timeslot in the data transmission network and
provides a net transmission rate of 9600 kbit/s.
Due to the limited throughput of the EOC, download of em-
bedded SW via the EOC is not recommended.
Management access and inter- For management communication, the UMUX 1200 features 3 physical
faces interfaces, the F-, Q1- and QX-interface, and the inband interface for the
ECC (Embedded Communication Channel). It is possible to segment the
management access of the EM to the UMUX 1200 as follows:
• Direct access to the NE by means of a (physical) point to point connec-
tion.
Such access is typically established via the F-interface. The access is es-
tablished as a
− local point-to-point connection between the EM and NE.
− remote access via a modem for a point-to-point connection be-
tween the EM and the NE.
• Local access
− via a LAN
The control units for the UMUX 1500 and 1200 provide an
Ethernet LAN interface, which allows you to connect the (N)EM
and the NEs to a LAN. The LAN access is established via the QX-
interface (Ethernet 10BaseT).
− via the Q-bus (Q1-interface)
The control units of the UMUX 1500 and 1200 provide a Q-bus in-
terface, which allows you to connect a local cluster of NEs to the
local Q-bus.

These control units additionally provide the Q1-master interface.

This interface allows you to access a local Q-bus via the ECC. The
Q1-master interface provides remote access to local Q-buses.
• Remote access to the NE by means of in-band management communi-
cation with the ECC (Embedded Communication Channel).
The EM accesses the ECC management communication structure
physically via any UMUX 1500, which is acting as a gateway to the
ECC network. Preferably, this access is established via the QX-Ethernet
interface.
• Remote access to the NE by means of an external (out-band) commu-
nication structure.
This communication structure can be organised as a data communica-
tion network. For communication, it is required to build up a commu-
nication channel between the EM and the NE throughout this com-
munication structure. The EM and the NE connect via their (physical)
management interfaces to the communication structure.
Such access is typically established via the EOC (Embedded Operation
Channel) for access networks with mixed types of UMUX equipment.
The EOC is a proprietary communication structure for UMUX Access
Systems based on the SIFOX unit. The EOC uses 1 timeslot in the data
communication network and operates with a net transmission rate of
9600 kbit/s. The NEs connect via their F-interfaces and the EM with its
serial interface to the SIFOX units and thus to the EOC.
Software download The functions provided for systems and units are increasingly defined by
the unit software rather than by the unit hardware. This evolution is un-
derlined with the introduction of software download (for the unit soft-
ware ESW) for new units. In contrast to the existing units released with
the UMUX 1100/1300, the unit software of the new generation units is
no longer an integral part of the unit hardware, but can be updated by
means of software download. The hardware's functionality is enhanced!
SW download is a standard commissioning and maintenance process in-
tegrated into the management concept of the UMUX 1500 and is con-
trolled via the EM.
SW download has major consequences:
• The functionality of a new generation unit is defined only when the
ESW is assigned to the unit. This assignment is accomplished via the
EM within the scope of the NE configuration. It is possible to schedule
SW download. This allows homogenous enhancements of features for
whole networks. If necessary, rapid intervention for the implementa-
tion of Service Packs for released software is possible as well.
• You must order units featuring SW download together with a corre-
sponding SW (licence). No hardware without a SW licence is available.
Data carriers with the corresponding ESW are (optionally) provided to-
gether with the ordered hardware.
Installed hardware and ESW can be checked with the built-in inventory
management function at any time. There is no need for local access to the
NE, since inventory and SW download use the same management com-
munication channels as used for standard remote management access.

The time required for ESW delivery to the NE depends heavily on the ca-
pacity of the communication channel involved. Traffic and system opera-
tion is not affected during software delivery. The time of service interrup-
tion for affected units is limited to the time required for the local SW in-
stallation, the unit reconfiguration and rebooting.

Compatibility
The design of the UMUX 1200 Access System guarantees compatibility
with the existing units and the UMUX system for external and internal in-
terfaces (where applicable).
Internal interfaces The UBUS interface and the µC-LAN interface of the UMUX 1200 are
compatible with the corresponding UBUS interfaces of the UMUX 1500
and 1300/1100(E) Access Systems. The compatibility covers the functional,
electrical and mechanical parameters (bus connector) of the interfaces.
This compatibility ensures the implementation of existing UBUS units in
the UMUX 1200.
The DC power supply for the units uses the same connector as the UBUS
and remains compatible with the UMUX 1500 and 1100(E)/1300 Access
Systems.
There are no other commonly used internal interfaces.
System compatibility of
functions
Traffic functions Since it is possible to implement most traffic units available for the UMUX
1300/1100(E) and all the units available for the UMUX 1500 with the
UMUX 1200, the functions provided by the units remain compatible be-
tween the systems. The EM features the same sets of parameters for the
control of the units function and operation for either type of system.
New functions and units implemented with the UMUX 1500 and 1200
are not generally backward compatible with the UMUX 1300/1100(E)
since they are based on the new architecture and features of the UMUX
1500 system. However, the EM provides similar dialogues to control simi-
lar functions.
System functions The availability of system functions with the UMUX 1200 such as synchro-
nisation, alarm handling and management communication is not princi-
pally different from the corresponding functions of the UMUX
1300/1100(E). These features are fully compatible with the UMUX 1500.
Due to the enhanced features of the UMUX 1500 system, parameters and
the control of such functions have become more flexible and comprehen-
sive.
The UMUX 1200 also features new system functions such as ECC (Em-
bedded Communication Channel), protection for the control unit, SW
download for the ESW, and inventory management, none of which are
available with existing UMUX systems.

System compatibility of Traffic and transmission units released with the UMUX 1500 and
units UMUX 1300/1100(E) can be operated with the UMUX 1200 (release pro-
vided), with some exceptions however:
• It is not possible to use the
− CENCA control unit
− POSUP power converter unit
in the UMUX 1200 subrack.

The COBUQ control unit is not released for the UMUX 1200.
• It is not possible to use the power supply units and special units de-
signed for the UMUX 1100(E) (3 HU of unit height) with the
UMUX 1200, in particular it is not possible to implement the:
− MIPOS
− MISUP
− MIRIG
− MIFAN
The UMUX 1200 uses the POSUS DC/DC power converter, introduced
with the UMUX 1500 and provides a new power unit and a new fan
unit:
− POSUA
− FANU2
The new units are not backward compatible with the
UMUX 1300/1100(E).
• Not all traffic units available for the UMUX 1300/1100 (E) have been
released for the implementation with the UMUX 1200.
Only units released for the UMUX 1200 must be imple-
mented!
Detailed information on the availability of units is provided in the chap-

ter 9 "System and Ordering Information" at the end of this document.
The paragraphs following give a short overview of the compatibility of
units and interfaces.
UBUS units Previously released UBUS (traffic) units can be plugged into and operated
within the UMUX 1200 as far as they have been released for use in this
system. A list of all units released for the UMUX 1200 is available in chap-
ter 9 "System and Ordering Information" at the end of this document.
New UBUS units are compatible with the UMUX 1200. Compatibility with
the UMUX 1300/1100(E) multiplexers has to be checked against the cor-
responding compatibility lists.
PBUS units PBUS units have been designed specially for the UMUX 1500 system and
are dependent on the PBUS for operation. Therefore, PBUS units are com-
patible with the UMUX 1200 but it is not possible to use these units with
the UMUX 1300/1100(E).

SBUS units SBUS units have been designed specially for the UMUX 1500 system and
are dependent on the SBUS for operation. Therefore, SBUS units are com-
patible with the UMX 1200 but it is not possible to use the SBUS units
with the UMUX 1300/UMUX 1100(E).
Control units The control units are specific for each brand of UMUX Access System and
are not interchangeable between the UMUX 1300/1100(E) (with the
CENCA control unit) and the UMUX 1500/1200 (with the COBU<X> con-
trol units).
However, the COBUQ unit is not released for the UMUX 1200!
Power units The UMUX 1200 operates with the:

• POSUS DC/DC power converter unit.
• POSUA AC/DC power converter unit which has been designed exclu-
sively for the UMUX 1200.
It is not possible to use existing power supply units (such as the POSUP,
MIPOS, etc.) with the UMUX 1200. With the UMUX 1200 you can only
use the power supply units that are released for the UMUX 1200.
Tributary and aggregate

interfaces
General The interfaces provided by identical units are compatible independently of
the type of UMUX Access System in which you operate the units.
Similar types of interface on different units and/or UMUX Access Systems
are partially compatible. The parts of the interfaces not compatible are
mainly due to enhanced functionality provided with new units and sys-
tems.
PSTN The PSTN interfaces remain compatible as outlined in the paragraphs

above on "System compatibility of functions".
The PSTN units PHLC<X> feature a high density of subscriber line inter-
faces, such as is required for V5.x applications.
It is possible to operate the interfaces of the PHLC<X> in the modes
• V5.x
• MCAS Direct Line
• Carrier Adapter
• Phone-Exchange
The interfaces implemented on a unit all operate in the same mode (of
operation) with identical sets of parameters.
The SUBLA type of subscriber line interface allows the individual setting of
operation mode and parameters per subscriber line interface. The V5.x
modes are however not available for SUBLA<x> and there is no subscriber
line test facility available for SUBLA<X> units.
Please note that the number of slots available in the UMX 1200 subrack
may limit the use of UBUS units. For example, the implementation of a

SUBLA (subscriber line interfaces) with the RIGEN ringing generator occu-
pies 3 of the 8 slots for just 12 subscriber line interfaces.
The PHLC<X> subscriber line interfaces (PBUS units) avoid this waste of
slots since they provide the interfaces and the ringing generator.
2 Mbit/s The 2 Mbit/s interfaces remain compatible as outlined in the paragraphs

on "System compatibility of functions" above.
The LOMIF/LOMI4 unit can terminate 2 Mbit/s structured signals and han-
dle 2 Mbit/s structured and unstructured signals for transparent cross
connection.
Additional features of the LOMIF/LOMI4, SYNAC and SYNAM are the
handling of PRA functionalities and the re-timing capability for transpar-
ent 2 Mbit/s traffic signals. These units feature enhanced performance
monitoring and trail handling. The 2 Mbit/s traffic interface of the
LOMIF/LOMI4 unit can be configured to remain compatible with the traf-
fic interface of the MEGIF unit.
The MEGIF terminates structured signals only and cannot handle struc-
tured or unstructured 2 Mbit/s signals for transparent cross connection.
STM-1 The STM-1 interfaces are available with the UMUX 1500 and UMUX 1200
only and remain compatible as outlined in the paragraphs on "System
compatibility of functions" above.
Management
Management systems The operation and maintenance concept for the UMUX platform relies on
the UCST and UNEM element and network managers.
The UCST is the element manager required for the initial commissioning
of any UMUX Access System and recommended for the management of a
single UMUX or small networks of UMUX family products. The UNEM
(UMUX Network Element Manager) manages medium to large sized
UMUX networks.
Both the UCST (release 3.3a/1 and higher) element managers and the
UNEM are compatible with all UMUX Access Systems including the
UMUX 1200.
The improved system dialogues feature more graphical elements and an
easy to use dialogue for the configuration of cross connections. The entry
to the dialogues for the configuration of units is based on functional lay-
ers. For existing units, the dialogues for the configuration of parameters
are almost identical (provided minor differences) compared to former
UCST versions.
Interfaces The UMUX 1200 features the same types of management interface as the
UMUX 1300/1100(E) multiplexers, and additionally the new QX-Ethernet
interface. Due to the enhanced features of management communication
and SDH, the UMUX 1200 and UMUX 1500 use more powerful protocol
stacks. The availability of stacks depends on the selected control unit
COBU<X> however.

Although the control units of the UMUX 1500/1200 and

UMUX 1300/1100(E) are different, the management interfaces of the
control units provide functionally (and partially physically) compatible in-
terfaces for management communication:
Tab. 1-1: System compatibility of management interfaces
Interface functional physical
F Yes Connectors different

Q1 Yes Connectors different
QX not available for the Not applicable
UMUX 1300/1100(E)
The F-interfaces of the UMUX 1300/1100(E) and the

UMUX 1200 use different protocol stacks.
Communication With the UCST R4D (or higher), the menu for the connection of the EM is
common for all UMUX Access Systems. The availability of interfaces and
protocol stacks depends on the selected type of NE (subrack and control
unit assigned).
The management communication via the structures EOC and Q-bus, pro-
vided with the UMUX 1300/1100(E), are also fully implemented for the
UMUX 1200. The communication remains compatible, if the UCST is a
release 3.3a/1 and the UNEM a release R3.0 (or higher).
The ECC management communication structure is particular for the
UMUX 1500 and 1200 (with the COBUX/COBUV) and is not implemented
for the UMUX 1300/1100(E) and UMUX 1500 with the COBUQ/COBUL
control unit.
Tab. 1-2: System compatibility of management communication
Channel functional physical
Q-bus Yes Yes

Q1-master IF Yes UMUX 1500/1200 only
EOC Yes Yes
ECC UMUX 1500/1200 only Not applicable
(COBUX, COBUV)

Compatibility with previous

releases
NE configuration With the UCST R5A it is possible to read and modify configurations of NEs
created with previous releases of the UCST or UNEM.
For functions (units) not supported with the new UCST the backward
compatibility for configurations depends on the general availability of the
function (unit).
• For functions (units) no longer supported:
The UCST R5A is not able to read configurations containing such func-
tions (units). To read and modify the configuration you must use a
previous release of UCST supporting the required functions (units).
• For functions (units) still supported but not available with UCST R5A:
You can read and modify the configuration with UCST R5A. It is how-
ever not possible to create new configurations containing such func-
tions (units).
It is not possible to convert configurations of other UMUX into
UMUX 1200 configurations.
Functions and units You can upgrade existing functions (units) via the conversion function of
the UCST to more recent and powerful functions (units) if the hard-
ware/software requirements are satisfied:
• The new UCST software must be installed.
• The new ESW (Embedded SoftWare) providing the new function (unit)
has to be delivered and installed on the corresponding unit.
• The hardware implemented and the new ESW have to be compatible
(refer to the corresponding compatibility lists).
Upgrade procedures The recommended upgrade procedures allow you to control the provi-
sioning of existing installations with the new UCST management SW and
new ESW for the COBU<X> control units.

ascom
System Architecture 2
Block diagram
The architecture of the UMUX 1200 is based on the architecture of the
UMUX 1500. The main architectural differences between the two Access
Systems are due to the different number of slots available for the units
and the powering options for the UMUX 1200.
To understand the relationship between the Access Systems, you can look
at the UMUX 1200 as a UMUX 1500 subrack with only the slots 5, 6, 7,
8, 9, 11, 12 and 21 available.
The block diagram below shows the main elements of the UMUX 1200
system.
Please note that the number of slots might limit the practical usable ca-
pacity and some of the backup features of the UMUX 1200.

ascom System Architecture
Figure 2-1: Block diagram of the UMUX 1200
SYNIO SYNIF SYNIC SYNAM SYNOT FUTURE

OPTION
VC-4 VC-4 VC-4 TU-12 VC-4
SBUS 2 x STM-1 [AD] <--> 1 x STM-1 [X] 2)
SYNAC SYNVA FUTURE PCONV PCON2 LOMIF PHLC LEMU6 LAWA4 LESA8
OPTION LOMI4 <X> LEMQ6 LESAP
VC-12 TU-12
PBUS 128 x 2 Mbit/s 1)
-48 Vdc
System Control
COBU<X> POSUA
Mains
Management System Control
COBU<X> POSUS 115 / 230 Vac
Alarming Management POSUS 3)
Synchronisation POSUS 3)
Diagnostics
PBUS Access of Power
Synchronisation th
UBUS supply
UBUS 8 x 2 Mbit/s 1)
TUNxy LECA2 MEGIF SIFOX GECOD NEMCA NEM

SULIx
CA SUBLx lSBUQ Special
LE2Q2 UNIDA EXLIx EXLAx ISBUT
1)
Capacity availability depends on the COBUX, COBUV control unit
2)
[AD] Add Drop
[X] Through connect
3)
The maximum 6 slots in the UMUX 1200 subrack available for traf-
fic units do normally not require more than 1 POSUS unit for the
power supply.
Bus Structures and Cross In order to cope with the requirements for high bit-rate traffic interfaces,
Connection enhanced internal traffic switching capacity and compatibility with existing
traffic units, three different buses for traffic data have been implemented
with the UMUX 1200:
• PBUS
• UBUS
• SBUS
While the PBUS is a completely new design created for the UMUX 1500
Access Systems, the UBUS has been introduced already with the
UMUX 1300/1100(E) multiplexers.
The SBUS is also a new design created for the UMUX 1500 and carries the
SDH format signals.

PBUS The PBUS is a bus structure for traffic signals of various formats with and
without CAS. The PBUS provides a non-blocking cross connect with the
equivalent capacity of 128 x 2 Mbit/s for traffic signals with and without
CAS. The formats are set individually for each termination. The PBUS al-
lows cross connections for 2 Mbit/s and n x 64 kbit/s (n = 1 ... 31) traffic
signals.
The PBUS provides digital cross connections for the levels DXC 1/1 and
1/0. The 1/1 cross connect of the UMUX 1200 allows the "bit and clock
transparent" switching of structured and unstructured 2 Mbit/s signals.
All types of cross connections may be bi-directional, unidirectional or of
the broadcast type.
traffic signals (payload). Each PBUS line carries 4 x 2 Mbit/s of traffic sig-
nals and the corresponding signalling information in additional TSs.
The architecture of the PBUS provides linear bus access. Any PBUS unit
can read all the information from the PBUS but can write to one (or more)
assigned PBUS line(s) only.
The access to the PBUS is established via an application specific circuit,
which handles, among other things, the write access for 1 PBUS line, cor-
responding to 4 x 2 Mbit/s of traffic signals and corresponding signalling
information. One (or more) of these ASICs is implemented on each PBUS
unit that provides cross connection and termination for traffic signals. An
active access circuit always seizes all 4 assigned 2 Mbit/s highways.
The PHAU number (PBUS highway Access per Unit) provided with each
PBUS unit indicates the maximum number of PBUS highways accessed by
a unit.
Since the cross connect is distributed on the PBUS, the cross connections
are resistant to single points of failure. Due to this design, the
UMUX 1500 Access Systems provide a highly reliable and economic cross
connect.
All newly created units with traffic volumes of 2 Mbit/s or higher bit rates
have access to the PBUS. This also applies to some of the SBUS units. The
PBUS interface of such units is identical with the PBUS interface of PBUS
units. The PBUS is connected to all the slots of the subrack except slot 21.
The number of accesses to the PBUS available depends on the COBU<X>
control unit implemented.
Units providing PBUS access (and no SBUS access at the same time) for
their traffic interfaces and/or signals are PBUS units.
UBUS The UBUS has already been implemented with the UMUX 1300/1100(E)
and provides a total bus capacity of up to 8 x 2 Mbit/s. The capacity of the
UMUX 1500 implementation of the UBUS remains the same for signals
with and without CAS. The access to the UBUS is based on n x 64 kbit/s
TSs. The UCST R4D, and more recent versions of the EM, provide an
automatic mode for setting connection points to the UBUS.
You can select the UBUS "Expert Mode" which allows you to set connec-
tion points manually. In contrast to the UMUX 1300/1100(E) the connec-
tion points for traffic signalling are automatically set independently of
whether the traffic signal uses CAS or not. The UMUX 1200 signalling

highways are not available for the cross connection of traffic signals with-
out CAS. The UMUX 1200 implementation of the UBUS allows the exist-
ing traffic and aggregate units available with the UMUX family to operate.
Like the generic UBUS, the UMUX 1200 implementation of the UBUS is
divided into a left and a right side set of four 2 Mbit/s highways (each
with a shadow highway structure for CAS signalling). The physical layout
of the highway access for the slots of the subracks differs between the
layout with the UMUX 1200 and the layout with the
UMUX 1300/1100(E):
• 8 slots provide access to the UBUS
• Cross over of “upper” and “lower” highways within left and right side
set of highways
• 2 slots with access to all 8 highways
The UBUS of the UMUX 1200 is a tributary to the PBUS. The access to the
PBUS is implemented on the COBU<X> control unit separately for the left
and right side highways. The cross connections for the traffic on the UBUS
are established via the PBUS. Thus, in contrast to the CENCA control unit,
the COBU<X> does not feature any cross connect functionality for the
UBUS.
The UBUS determines not only the structure for traffic signals but also in-
cludes standard channels for processor communication, system timing
and power rails. All units implemented in the UMUX 1200 have access to
at least this second set of signals.
Units providing UBUS access for their traffic interfaces and/or signals are
UBUS units.
SBUS The SBUS carries SDH traffic signals to allow drop and insertion of traffic
signals from/to STM-1 signal frames as well as the through connection
between STM-1 interfaces for the traffic signals that remain in the STM-1
frame. The structure of the VC-4 container can be set to VC-3 and VC-12
structures or to a mixture of both. The SBUS consists of DROP and ADD
buses for the traffic signals and several auxiliary signals e.g. signals for
synchronisation. The 2 DROP and ADD buses carry essentially synchro-
nised TU-12 signals. To access the SBUS there are 2 types of units pro-
vided: units with aggregate and access interfaces, each type of unit ac-
cess' the SBUS differently.
• Aggregate interfaces write the contents of an STM-1 signal frame to
an assigned DROP bus and read back selected traffic signals from a
second DROP bus and the assigned ADD bus.
• Access interfaces read selected traffic signals from either of 2 DROP
buses and write selected traffic signals to any of 2 ADD buses.
The STM-1 aggregate interfaces are implemented on dedicated traffic
units. These terminate VC-4 and provide frame synchronised SDH signals
as TU-12 or TUG3 structured traffic signals to the SBUS. Units with access
interfaces terminate the structured traffic signals provided on the SBUS.
The SYNAC unit for example terminates VC-12 and writes corresponding
2 Mbit/s signals to the PBUS and reads 2 Mbit/s signals from the PBUS re-
spectively. SDH traffic switched via the SBUS from aggregate to aggregate
interface does not impede the internal PBUS capacity of the UMUX 1200.

The specific structure of the SBUS allows the implementation of 2 STM-1

interfaces on the SBUS to
• ADD and DROP VC-12 traffic signals into/from 2 STM-1 frames.
• Cross connect VC-12 and VC-3 traffic signals between 2 STM-1 inter-
faces. The UMUX 1500 is however not considered as an SDH cross
connect.
Normally a mixture of both ADD/DROP and cross connect are imple-
mented. With 1 STM-1 interface the UMUX 1200 terminates the STM-1
signal.
The UMUX 1200 subrack provides the SBUS on the slots 5, 6, 7, 8, 9.
For details of SBUS access, refer to "Configuration of the subrack" in the
chapter "System and Application Notes".
Units providing SBUS access for their traffic interfaces and/or signals are
SBUS units. Units providing SBUS and PBUS access at the same time are
also SBUS units.
System control The system control of the UMUX 1200 relies on a central control block
and on processors on the peripheral units (traffic, aggregate units). Such
decentralised processing can control several functions if required (unit
control and control of traffic interfaces). The processors use dedicated
communication channels (µ-LAN, ICN) for the communication between
the central control and the peripheral units.
The system control block is implemented on the COBU<X> control units.
A second control unit (of the same type) can provide protection for the
system control. The central control
• manages the NE configuration
• controls the system operation
• management communication
• synchronisation
• monitors the system performance
The control block holds copies of the ESW that runs on units with soft-
ware download and controls the installation of such ESW on the units. All
the information on system/unit configuration is stored and administrated
via the management information database. In the case of a redundant
control unit, the management information database of the standby con-
trol unit is continuously updated.
The control unit holds the various interfaces for the management com-
munication to the EM or NEM and provides the access to the ECC (avail-
ability depends on the control unit). The local alarm interfaces (inputs and
outputs) are implemented on the control unit as well.
Additional functions such as UBUS access, synchronisation, diagnostic and
conferencing functions are also implemented on the control unit, but are
not directly part of the central control. The implementation and availability
of these functions depend on the type of the COBU<X> control unit and
the system release.

Communication between The communication between the central control block and the processors
controllers on the peripheral units is established via 2 different internal communica-
tion structures. Depending on the type of unit, the ICN channel serves the
PBUS and SBUS units, while the µC-LAN serves UBUS units.
The communication channels are embedded in the physical structures of
the PBUS and the UBUS respectively.
Synchronisation and system The UMUX 1200 provides PETS and SETS for the NEs with STM-1 inter-
timing faces. The SETS function is implemented on the STM-1 aggregate units.
The main part of PETS timing system and the clock control block is imple-
mented on the COBU<X> control units.
Systems without SDH signals use PETS only. In systems with SDH, the NE
can operate PETS and SETS autonomously without a fix-phased relation-
ship between the SETS and PETS synchronised equipment. If required the
PETS timing system is synchronised to SETS.
The timing signals are groomed and distributed via dedicated timing sig-
nal lines which are embedded in the physical structures of the UBUS, the
PBUS and the SBUS respectively. Traffic units provide timing signals to the
signal lines as configured during system commissioning. The control unit
features interfaces to input and output timing signals from and to exter-
nal equipment.
The NE can be synchronised with incoming traffic signals (i.e. the clock is
extracted from traffic signals) or with the 2 MHz signals provided at the
terminals for external clock signals. If both sources fail the Access System
synchronises to its internal timing source(s) (Timing source(s): PETS (and
SETS)). The NE provides a second set of terminals for timing signals for the
synchronisation of external equipment.
The selection algorithm and provisioning of clock signals is programmable
in order to prevent loss of synchronisation and to avoid synchronisation
loops. The system handles both timing signals using SSI and SSM.
The UMUX 1200 supports PETS and SETS (depending on the SBUS unit)
equipment protection.
Power supply The UMUX 1200 operates from one power supply unit. Any voltages re-
quired for system operation are generated locally in the subrack.
The power supply unit(s) always convert the primary voltage to the inter-
nal power supply voltage of +5 V/-5 VDC required for the operation of the
units. The converted power and the primary voltage are distributed to the
units via power rails, which are embedded within the physical structure of
the UBUS.
The UMUX 1200 has two basic powering options:
• DC powering
The nominal supply voltage is -48 VDC or -60 VDC with the 0 volt poten-
tial connected to signal ground. This supply voltage corresponds to the
primary voltage.
The POSUS power converter unit converts the primary supply to the
+5 V/-5 VDC required for the operation of the units.

It is possible to protect the local power supply with an additional

power converter unit. The power converter units implemented operate
in a load share mode.
• AC powering
The UMUX 1200 is powered from the mains via the POSUA AC/DC
power converter unit. The POSUA supports the nominal mains voltage
of 115 VAC and 230 VAC.
The POSUA power converter unit generates first the primary supply
voltage (nominally -48 VDC) and then the internal power supply volt-
ages of +5 V/-5 VDC. On the POSUA front panel you find a switch for
the selection of the nominal mains voltage and an apparatus plug for
the mains.
The AC powering option has protection class I.
The AC powering option with the POSUA allows you also to implement a
48 Volt battery backup for the primary power supply. The POSUA con-
verter charges and controls the external batteries. The optional BATMO
battery package is a separate case for installation of the external batteries.
Traffic units All traffic units are implemented as peripheral units and connected via
their corresponding (traffic) bus structure(s) to the UMUX 1200 core sys-
tem.
Traffic units connected to the
• PBUS provide
− n x 2 Mbit/s access for structured and unstructured signals or
− n x 64 kbit/s (n = 1 ... 31) for structured signals terminated on the
unit or for units providing n x 64 kbit/s traffic signals.
• UBUS provide
− n x 64 kbit/s (n = 1 ... 31) access for structured signals terminated
on the unit (units with aggregate interfaces) or for units providing
n x 64 kbit/s traffic signals.
• SBUS provide
− n x STM-1 (n= 1, 2) access for units with aggregate interfaces
− n x TU-12 or TUG-3 (FUTURE OPTION) access for units with access
functionality. The access to the PBUS (if applicable) is n x 2 Mbit/s
structured and unstructured or TU-12 (FUTURE OPTION).
Subrack Although not shown in the block diagram of the UMUX 1200, the
subrack is an important functional block of the UMUX 1200. The subrack
provides the mechanical and electrical infrastructure for the operation of
all units. The subrack guarantees the interconnection between the units
via the bus structures and provides the interface for the DC power supply.
The subrack supports the inventory management.
The UMUX 1200 subrack has many mechanical options that allow the in-
stallation of the UMUX 1200 subrack
• in 19-inch and ETSI racks
− horizontally
− vertically

• Vertical wall mounting

The optional fan unit guarantees sufficient cooling if the natural air con-
vection through the subrack is not sufficient (e.g. for the horizontal in-
stallation options).
Implementation of functional blocks

Functions and features The UMUX 1200 is a Access System with highly modular functions and
features. Each UMUX 1200 NE and thus the applicable system features are
defined by 2 elements:
• the UMUX 1200 subrack
• the selected COBU<X> control unit
You can have all the system features defined for the UMUX 1200 or a
subset of those features depending on the control unit implemented with
the UMUX 1200 subrack.
The implementation of control units that are optimised for typical applica-
tions allows the customer to provision cost optimised Access Systems for a
particular application, while still preserving the option of a later system
upgrade.
Architecture and functional The majority of functional blocks that you can identify in the block dia-
blocks gram are implemented on units. Most of the units are dedicated to some
particular type of interface or functional block. Some of the units (e.g. the
control unit) provide the physical platform for the implementation of sev-
eral functional blocks.
Control units The system control block is implemented on the control unit. The control
units are unique to the UMUX 1500 and 1200. Depending on the re-
quired NE functions, you can select one out of several types of control
units.
The control unit has a high performance on-board CPU and uses software
download for its own unit software (ESW). A major task of the control
unit is the maintenance of the NE database (MIB), which covers the com-
plete information of the NE configuration and all ESW loaded to the NE.
The control unit also holds important auxiliary functions. Such auxiliary
functions (features and availability depend on the selected control unit)
are:
• Management interfaces of the NE
• Management access to the ECC (COBUX and COBUV only)
• Management and selection of timing sources and clock control
• UBUS access to the PBUS
• Conference for voice and CAS signals (COBUV only)
• Diagnostic functions (COBUX and COBUV only)
• PETS
• Interfaces for synchronisation signals (input, output)
• Local alarm interfaces (input, output)

The UMUX 1200 allows the implementation of a redundant control unit.

The redundant control unit is in hot standby mode. If the active equip-
ment fails, the redundant unit takes over the system control. The switch-
over can affect, for a short period, the traffic on the UBUS and PBUS.
The configuration and MIB stored on the standby control unit is continu-
ously updated and thus identical to the information on the master control
unit. Hence, the redundant control unit can take over system control with
a cloned database.
The switchover due to equipment failure is non-revertive. You can initiate
a switchover at any time via the EM or NEM.
2 slots in the UMUX 1200 subrack are reserved for the master control unit
and the corresponding backup unit. If this redundancy is not implemented
the slot is available for other units.
Power units The power units convert the external primary voltage (-48 VDC or mains) to
the NE internal supply voltages. The power units have no specific BUS
designation, since they have no (traffic) access to internal buses and do
not feature a processor of their own.
The UMUX 1200 allows several DC power supply units for simultaneous
operation in the subrack, depending on the power consumption of the
units implemented and requirement for power backup (redundancy). The
power units operated in parallel share the load among the units. The load
sharing provides less stress to individual units and thus higher reliability.
The number of slots available in the UMUX 1200 subrack practically limits
the number of DC/DC convert units to 2. This allows a full 1+1 unit pro-
tection for the converter.
You can insert the power converter units into any slot of the UMUX 1200
subrack (Slot 21 is preferred for the first DC/DC converter unit imple-
mented).
The AC/DC converter unit takes 2 slots in the UMUX 1200 subrack. The
slots 12+21 are preferred for the implementation of the AC/DC converter
unit if the UMUX 1200 has no redundant control unit.
Traffic units
PBUS units PBUS units have direct access to the PBUS and thus to the cross connect.
Hence, PBUS units provide a traffic capacity of several times 2 Mbit/s.
The PBUS units are microprocessor controlled and feature SW download
for the unit SW (ESW). The unit program code is locally stored in a non-
volatile flash EPROM or, in cases such as the PCON<X>, in a volatile pro-
gram memory. While the program code, once copied to non-volatile
memories, is available for execution, the control unit must reprogram
volatile memories with the program code after each power up.
PBUS units feature full inventory management for information on unit
hardware and software.
For more information on PBUS unit functions, refer to the unit descrip-
tions below and the corresponding user guides.

SBUS units SBUS units have direct access to the SBUS. Some of the SBUS units also
have access to the PBUS and the associated cross connect. Accordingly,
SBUS units provide a traffic capacity of several times 2 Mbit/s.
The SBUS units are microprocessor controlled and feature SW download
for the unit SW (ESW). The unit program code is locally stored in a non-
volatile flash EPROM or, in cases such as the SYNI<X>, in a volatile pro-
gram memory. While the program code, once copied to non-volatile
memories, is available for execution, the control unit must reprogram
volatile memories with the program code after each power up. SBUS units
software.
For more information on SBUS unit functions, refer to the unit descrip-
tions below and the corresponding user guides.
UBUS units UBUS units have direct access to the UBUS. Although UBUS units have no
direct access to the PBUS, they are indirectly connected to the PBUS via
the UBUS highways. The UBUS highways are tributaries to the PBUS. De-
pending on the selected control unit, the full UBUS capacity of 8 x 2Mbit/s
or half the capacity of 4 x 2 Mbit/s is available to connect UBUS units.
Traffic units, which feature aggregate interfaces of a capacity of 2 or 4 x 2
Mbit/s (MEGIF or TUNO<X>) load the UBUS rather than the PBUS.
Due to the UBUS implementation in the UMUX 1200, most UBUS units
released with the UMUX 1300/1100(E) are also compatible with the archi-
tecture of the UMUX 1200.
Although microprocessor controlled, previously released UBUS units do
not feature SW download and provide reduced inventory data (Slot des-
ignation, unit name, HW key, SW version). The unit program code is lo-
cally stored in PROMs.
Information on unit hardware and software is available within the scope
of system discovery. In contrast to this the new generation of UBUS units
(such as the ISBUQ, ISBUT, etc.) feature both SW download and inventory
management.
For more information on the functions implemented with UBUS units and
the operation of the units, refer to the user guides for the units.
Subrack
Function Although the subrack is not directly identified as a functional block, it is
an important element of the architectural implementation of the UMUX
1200. The subrack provides the electrical and mechanical infrastructure
for the units and is an integral part of the EMC concept of the UMUX
1200.
The UMUX 1200 subrack provides the following system functions:
• Connection to and distribution of the primary power supply voltage
• Internal distribution of converted power (power rails)
• Distribution of signals
• Connection of slots to the UBUS, PBUS and SBUS
• Installation/connection and grounding of signal cables
• Mechanical installation of units

• Electrical connection of the units to power supply, buses and control

signals
• EMC and EMD protection for system and units
• Mechanical protection for units and components
• Inventory data of the subrack (backplane)
• Host for complementary elements and subsystems such as
− fan unit (optional)
− filter for ventilated air (optional for vertical installation)
The UMUX 1200 subrack together with dedicated adapters allows you to
define the installation option for the UMX 1200. The adapters also pro-
vide the cable tray for the cables connected to the UMUX 1200. The in-
stallation options are:
• Installation in racks
The UMUX 1200 subrack is suited for horizontal and vertical installa-
tion in 19-inch or ETSI racks.
The 19-inch adapter provides the cable tray (for the convenience of in-
stallation) and the set up for the subrack for 19-inch rack installation.
ETSI adapters allow you to install the 19-inch set-up in ETSI racks.
• Installation on walls and in cabinets.
The wall-mounting adapter allows the vertical installation of the
UMUX 1200 subrack on walls or in cabinets. This optional adapter
provides the cable tray (for the convenience of installation).
Please note that the BATMO battery package is not integrated into the
UMUX 1200 subrack but is an optional external equipment. You can in-
stall the BATMO on walls and in cabinets with the UMUX 1200 or simple
place it on the ground near the UMUX 1200.
Slots in the subrack The UMUX 1200 subrack features a total of 8 equally spaced slots and a
special slot for the fan unit.
While the slots are identical from a mechanical point of view, the access
to the buses varies. You can identify segments made of several slots with
identical bus access for each bus.
The implementation of traffic units in slots is mainly limited by the bus ac-
cess. Slot 11 is reserved for the control unit. Only the slot 12 can accept
the redundant control unit, if you want to implement equipment protec-
tion for the control unit. It is possible to plug the power converter units
into any slot of the subrack.
The figure below shows a synoptic overview of the subrack, bus access
per slot and the implementation of control and power units in the
subrack.

Figure 2-2: Bus access, control and power units for slots of the
UMUX 1200 subrack (schematic view)
No BUS access
1 (special)
UBUS 4 Hwy.s
UBUS 4 Hwy.s
PBUS
SBUS
CU CU
Power Supply Unit

5 6 7 8 9 11 12 21
CU = Control Unit
The UMUX 1200 subrack has the special slot 1 on top of the subrack to
implement the optional fan unit. This slot has no BUS access and is exclu-
sive for the fan unit.
The BUS access in the UMUX 1200 slots corresponds exactly to the BUS
access of the slots with the same number in the UMUX 1500 subrack:
Figure 2-3: Equivalent slots of the UMUX 1200 subrack in the UMUX
1500 subrack (schematic view)
UBUS 4 Hwy.s
UBUS 4 Hwy.s
PBUS
SBUS SBUS
CU CU
Power Supply Unit (POSUS)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
UMUX 1200 5 6 7 8 9 11 12 21
CU = Control Unit

Please note that the slot 1 of the UMUX 1200 subrack is not equivalent to
the slot 1 in the UMUX 1500 subrack!
The table below summarises the slot information on bus access and the
implementation of control and power units.
Tab. 2-1: Bus access, control and power units vs. slots of the
UMUX 1200 subrack
Slots
Access Unit type 1 5-9 11 12 21
COBU<X> 4) - - ✔ ✔ -
POSUS - ✔ - ✔ ✔ 1)
POSUA 2) - ✔ - ✔ 3) -
UBUS UBUS - ✔ ✔ ✔ ✔
4 Hwy.s
UBUS UBUS - - ✔ ✔ -
8 Hwy.s
PBUS PBUS - ✔ ✔ ✔ -
SBUS_A SBUS - ✔ - - -
None FANU2 ✔ - - - -
1)
Preferred slot for first POSUS unit implemented.
2)
The POSUA AC/DC converter takes 2 slots.
3)
Preferred slot for first POSUA unit implemented.
4)
The COBUX, COBUV and COBUL are the control units for the
UMUX 1200.
Limiting factors for the im- The limiting factors for the implementation of units and interfaces are
plementation of units mainly given by the
• number and disposition of free slots.
• remaining capacity on the UBUS (for UBUS units).
• remaining capacity on the PBUS (number of active PBUS accesses).
• availability of the required bus access with respect to the slots avail-
able.
• remaining available power
• power dissipation per slot and per subrack
For details on limiting factors and implementation rules for units refer to
the chapter 8 "Implementation and Application Notes".

ascom
Functional Descriptions 3
Traffic functions
The UMUX 1200 provides the same traffic functions as the UMUX 1500.
For the functional description of the traffic functions, please refer to the
corresponding chapter in [202].
Traffic units
The UMUX 1200 supports the same traffic units as the UMUX 1500.
For the functional description of the traffic functions, please refer to the
corresponding chapter in [202]. Please note that the UMUX 1200 subrack
provides only a subset of the slots indicated for the unit operation in the
UMUX 1500 (slot 1 is not available for traffic units).
For detailed information on supported traffic units, refer to the chapter
"System and Ordering Information".
Control units
COBU<X> units
COBUX/COBUV The UMUX 1200 supports the COBUX and COBUV control units the
same way as the UMUX 1500.
For the functional description of the control units, please refer to the cor-
responding chapter in [202].
COBUL The UMUX 1200 supports the COBUL control unit the same way as the
UMUX 1500.
For the functional description of the control units, please refer to the cor-
COBUQ The COBUQ control unit is not released for the UMUX 1200!

ascom Functional Descriptions
Overview of specific techni- The table below provides information on those features of the NE
cal data of control units UMUX 1500 and UMUX 1200, which depend only on the selection of the
control unit COBU<X>. Features not mentioned are identical for all con-
trol units (e.g. protection of the control unit).
Tab. 3-1: Synoptic overview of features and control units
UMUX type 1500 1500 1300 Remarks

1200 1100
Feature COBUV COBUX COBUL COBUQ CENCA
137 237 145 146 215 144 2<XY>
PBUS access ca- 128 40 128 40 128 32 - Number of 2 Mbit/s highways

pacity (each including CAS signalling).
Access to PBUS via all slots of the
subrack but slot 21.
UBUS access 8 1) 8 1) 8 1) 8 1) 4 2) 4 2) 8 3) Number of 2 Mbit/s traffic high-
capacity (16) ways (odd numbered) plus the
highways for CAS signalling (even
numbered)
1+1 protection ü ü ü ü ü ü - Equipment protection control unit
SW download ü ü ü ü ü ü - For ESW (unit SW)
Inventory ü ü ü ü ü ü - 4)
Alarm outputs ü ü ü ü ü ü - Relay contacts for 2 NE alarm lev-
els
QX-interface ü ü ü ü ü ü - TCP/IP LAN protocol stack over
Ethernet 10BaseT LAN interface
Q1-master IF ü ü ü ü ü ü - Functionally replaces "via ATU
…".
EOC ü ü ü ü - ü ü F-interface via SIFOX
PDH ECC ü ü ü ü - - - ECC via 2 Mbit/s and TS 0
(LOMIF/LOMI4)
SDH ECC ü ü ü ü - - - ECC via STM-1 DCC
SDH DCC ü ü ü ü - - - Access to SDH Data Communica-
tion Channel
OSI stack and ü ü ü ü - ü - IS-IS and IP router for the encap-
tunnelling of sulation of TCP/IP in OSI DCN (for
TCP/IP in OSI management communication of
UMUX via OSI DCN)
SETS ü ü ü ü - - - Function implemented on
SYNI<X>
ESO-4 ü ü ü ü - - - With SDH only
Diagnostics ü ü ü ü - - - Central (data channel) diagnostic
function
Conferencing ü ü - - - - ü Conference function for 64 kbit/s
services.
5) 5) 5) 5) 5) 5) 6)
Units Restrictions apply for the units
available.

1)
COBU<X>:
highways 9 … 16 in the slots 11 … 21 (even numbered highways
are always reserved for CAS).
2)
COBUQ, COBUL:
Access to the UBUS highways 1 … 8 in the slots 1 … 16. No UBUS
highway access in slots 17 … 21 (even numbered highways are al-
ways reserved for CAS).
3)
CENCA:
the highways 9 … 16 in slots the 9 … 17 (even numbered high-
ways are always reserved for CAS). If there are only traffic signals
without CAS you can use the odd numbered highways for traffic
signals as well.
4)
The discovery function provides limited inventory information.
5)
For the exact definition of units available with the UMUX
1500/1200, refer to the release note provided with the UCST R5A.
6)
Only UBUS units. For the exact definition of units available with the
UMUX 1100(E)/1300 refer to the applicable release notes.
Please note:
• Even and odd numbered UBUS highways:
− In the UMUX 1500/1200 the even numbered UBUS
highways are reserved exclusively for the channel associ-
ated signalling (CAS) of the corresponding (odd num-
bered highways) traffic signals, independently of whether
CAS is used or not.
− This is in contrast to the UMUX 1100/1300 (CENCA),
where it is possible to use the even numbered highways
for traffic signals if no CAS is required.
• The COBUQ is not released for the UMUX 1200.

Auxiliary units
Power units The UMUX 1200 has a DC and an AC powering option. The DC powering
is based on the standard POSUS power converter for the UMUX 1500.
POSUS power unit The UMUX 1200 supports the POSUS power converter unit the same way
as the UMUX 1500.
Please note that the UMUX 1200 subrack provides only a subset of the
slots indicated for the unit operation in the UMUX 1500 (slot 1 is not
available for powering units).
For the functional description of the POSUS powering unit, please refer to
the corresponding chapter in [202].
For detailed information on supported traffic units, refer to the chapter
POSUA power unit The POSUA unit provides AC/DC power conversion for the UMUX 1200.
The POSUA converts the mains voltage of nominal 115 VAC or 230 VAC to -
51 VDC (-54.6 VDC with backup battery). The temperature controlled out-
put characteristic of the AC/DC converter allows the POSUA to load an
external backup battery. The second converter of the POSUA converts the
primary voltage to the internal supply voltages of +/-5 VDC required for the
operation of the units.
The POSUA is a protection class I equipment. A switch on the POSUA
front panel allows you to select between the nominal mains voltages of
115 VAC or 230 VAC.
An apparatus plug in the front panel connects the POSUA to the mains. A
second connector establishes the connection for the external battery.
• Parallel operation of units
You can operate the POSUA unit in parallel with a POSUS unit. Units
operated in parallel share the load on the 5 VDC power rails. This pro-
vides modular implementation of protection for the DC/DC power
conversion. It also lowers the load per unit. This feature enhances the
reliability of the individual units.
The parallel operation of two POSUA units is not possible!
• Interface for the external backup battery
The POSUA provides an interface for an external backup battery which al-
lows you to implement a backup capacity of up to 17 Ah (48 Volts). The
POSUA feeds simultaneously current for the UMUX 1200 units and the
battery. The POSUA has temperature controlled charging characteristic
with the temperature sensor in the BATMO battery package.
The maximum current drain from the backup battery is 3 A.
The BATMO battery package provides a special case that allows for the
installation of these batteries and the connections required for the
POSUA charging circuit.

• System characteristic POSUA

− Inventory Yes
− Unit fitting slots of subrack (5 - 8), 12
− Front panel connector 3-pin mains apparatus
plug
(5 - 8): Slot 12 is the preferred slot for the POSUA
implementation.
Slot 12 is not available in systems with protection of
the control unit.
For more information on the POSUA unit and its operation, refer to the
Special units The UMUX 1200 supports the special units in the same way as the
UMUX 1500.
For the functional description of the traffic units, please refer to the corre-
sponding chapter in [202].
For detailed information on supported traffic units, refer to the chapter 0
Software download
The UMUX 1200 supports the software download in the same way as
the UMUX 1500.
For the functional description of the software download, please refer to
Synchronisation
The UMUX 1200 supports the synchronisation in the same way as the
UMUX 1500.
For the functional description of the software download, please refer to
Redundancy and protection

The UMUX 1200 supports the redundancy of functions and protection
in the same way as the UMUX 1500.
For the functional descriptions of redundancy and protection, please refer
to the corresponding chapter in [202].

Performance Monitoring
The UMUX 1200 supports the performance monitoring in the same
way as the UMUX 1500.
For the functional description of the performance monitoring, please refer

ascom
Management Functions 4
The UMUX 1200 supports the management functions in the same way
as the UMUX 1500.
For the functional description of the performance monitoring, please refer

ascom
Mechanical and EMC/ESD 5

Construction
Overview
The subrack The UMUX 1200 subrack provides the mechanical packaging for the units
and the backplane with electrical connections to the bus structures and
the power supply. The subrack is a compact construction of a height (in
the horizontal position) equivalent to 4 HU and a depth which is compati-
ble with the 19-inch and ETSI standards.
The UMUX 1200 subrack provides a special slot for the implementation of
the optional fan unit. In subracks without a fan unit, a dummy bezel al-
lows you to cover this slot. The subrack also allows the installation of an
optional filter unit to filter the air that is circulating through the subrack.
Figure 5-1: UMUX 1200 subrack with fan and air filter options
Slot for air filter

(optional)
21
11 12
9
8
7
6
5
Slot for fan unit

(optional)
The subrack has a removable front cover (not shown in the figure above).
This cover provides apertures so that the LED indicators on the units re-
main visible even with the front cover installed.

ascom Mechanical and EMC/ESD
The installation The basic UMUX 1200 subrack features a universal mounting gusset (to
the left in the figure above) which allows you to install the UMUX 1200
subrack together with a set of adapters in 19-inch and ETSI racks. Rack in-
stallation of the UMUX 1200 subrack is possible in the horizontal and the
vertical position.
Figure 5-2: UMUX 1200 19-inch and ETSI rack installation

(horizontal and vertical)
ETSI installation:
+ ETSI adapters
19-inch installation:
+ 19-inch adapter
Subrack
21
11 12
9
8
7
6
5
The universal gusset mounted at the rear of the subrack together with the
wall-mounting adapter allows you to install the UMUX 1200 subrack (ver-
tically) on a wall or in cabinets without rack infrastructure.

Figure 5-3: UMUX 1200 rack wall mounting

(vertical)
Wall mounting:
Subrack + wall-mounting
adapter
5 6 7 8 9 11 12 21
The 19-inch and the wall-mounting adapters also provide the cable tray
functionality. This convenience allows you to first install the cabling and
mount the UMUX subrack afterwards.
Cooling The UMUX 1200 subrack allows operation of the Access System in the
horizontal and vertical position. In the horizontal position, or if the envi-
ronmental conditions of the installation do not allow the UMUX 1200 to
operate within specified temperature range (e.g. if systems are installed
on top of each other), the units require forced cooling. The UMUX 1200
subrack has a special slot to host the (optional) FANU2 fan unit.
The FANU2 has two independent fans. Each fan has its active operational
control, which for example increases the rotation of the remaining fan if
the other fan fails. The UMUX 1200 system control monitors the opera-
tion of each fan unit and can generate alarms in the case of failures.
It is possible to install an optional filter in the UMUX 1200 subrack to filter
the air circulating through the subrack. The access to the filter unit re-
quires space to the left or right of the subrack.
Illustrations of the UMUX 1200 subrack in the first chapter of this docu-
ment show the UMUX 1200 with and without front cover. Design and
dimensions of the subrack and the auxiliary elements are shown in the
figures below.

UMUX 1200 subrack

Design and dimensions Plain metal sheets close both sides and the rear of the UMUX 1200
subrack. The perforated metal sheets close the top and bottom of the
UMUX 1200 subrack. The subrack includes the cable grounding bar and a
versatile mounting gusset which is used for the subrack installation in
conjunction with adapters. The gusset mounted in the front level of the
subrack together with the corresponding adapter(s) allows rack installa-
tion. The gusset mounted at the rear of the subrack together with the
wall-mounting adapter allows wall mounting.
The figure below shows the layout and the mechanical dimensions of the
UMUX 1200 subrack, including the mounting gusset and grounding bar.
Figure 5-4: UMUX 1200 basic subrack

(dimensions [mm])
458.45
437.3 280.3
20.32
176.1
149.5
352.6
241.1
283.1
42
Depending on the installation option, the mounting gusset (left,

front) is installed in front or at the rear of the subrack.
Partitioning and backplane The UMUX 1200 subrack features 8 evenly spaced slots. The width of
arrangement every slot is 4 TE (20,32 mm). While the mechanical parameters are identi-
cal for all slots, the electrical interface to the backplane depends on the
slot position.
The backplane provides the physical bus structures and carries the power
rails for the internal power supply. The backplane features a row of con-
nectors compatible with the UBUS connectors of the UBUS units and a
second row of connectors providing access to the PBUS. Where applica-

ble, a third row of connectors provides access to the SBUS. The construc-
tion of the subrack provides protection and shielding for the backplane,
namely at the rear.
Figure 5-5: UMUX 1200 subrack and backplane layout

(dimensions [mm])
163,1
Connector for fan unit
UBUS
PBUS
SBUS
20,32

19-inch installation option An optional adapter allows you to install the UMUX 1200 subrack in 19-
with cable tray inch racks. The 19-inch adapter provides the cable tray and allows you to
install the signal and power cables before the installation of the subrack.
The figures below show the mechanical dimensions of the 19-inch
adapter and the set-up of the UMUX 1200 subrack for the installation 19-
inch racks.
Figure 5-6: 19-inch adapter for the UMUX 1200 subrack

(dimensions [mm])
49,15
166,55
101,6
32,48
View A
A
57,89
Figure 5-7: UMUX 1200 subrack layout for 19-inch installation

(dimensions [mm])
482,6 283,1 176,1

101,6
143,4
101,6
241,1
42

ETSI adapters To install the UMUX 1200 into a rack complying with ETSI, a special ETSI
adapter set is available. The installation in ETSI racks requires the
UMUX 1200 subrack set up for 19-inch installation plus the ETSI adapters.
The figures below show the mechanical dimensions of the ETSI adapter
and the set-up of the UMUX 1200 subrack for the installation in ETSI
racks.
Figure 5-8: ETSI adapter for the UMUX 1200 subrack

(dimensions [mm])
UMUX 1200
with
19-inch adapter
166,55
100
101,6
33,28
41,1
7,1
The adapters provide M6 nuts for the fixing holes of the 19-inch
adapters.

Figure 5-9: UMUX 1200 subrack layout for ETSI installation

(dimensions [mm])
532,4 +/-
482,6
100
241
42

Wall mounting option with An optional adapter allows you to install the UMUX 1200 subrack on
cable tray walls or in cabinets. The adapter provides the cable tray and allows you to
install the signal and power cables before the installation of the subrack.
The figures below show the mechanical dimensions of the wall-mounting
adapter and the set-up of the UMUX 1200 subrack for wall mounting.
Figure 5-10: Wall-mounting adapter for the UMUX 1200 subrack

(dimensions [mm])
176,5
35,25 106 7,25
45
298,85
507
40

Figure 5-11: UMUX 1200 subrack layout for wall mounting

(dimensions [mm])
176,5 290,35
507

Fan unit (optional) Figure 5-12: FANU2 fan unit

(dimensions [mm])
Air flow
The FANU2 fan unit features two individual fans, which are individually
powered and monitored for operation. The speed of the fans is tempera-
ture controlled (30 °C to 50 °C). The design of the fan unit provides a
minimum air velocity of 0,75 m/s through the subrack. If one of the fan
fails, the remaining unit speeds up to compensate for the failure (0.39 m/s
in total).
The FANU2 is directly installed in the UMUX 1200 subrack and operates
from the 48 VDC power supply (range 39.5 … 75 VDC). The fan unit has an
internal interface that allows the monitoring and alarming of failures via
the alarm system of the UMUX 1200.

Air filter (optional) The air filter is optionally installed at the cable tray side of the UMUX 1200
subrack. The filter cleans the air flowing along the units in the subrack
from dirt particles.
The air filter is particularly useful with the fan option and is required if the
UMUX 1200 is operated in an environment with dirty air. This affects
mainly UMUX 1200 in outdoor cabinets.
Figure 5-13: UMUX 1200 subrack and air filter
Air filter
5 6 7 8 9 11 12 21
For cleaning and maintenance you can easily remove and re-insert the fil-
ter. This maintenance operation requires free space (min. 180 mm) to ei-
ther side of the subrack.
BATMO battery package The POSUA power converter unit can charge an external battery for the
(optional) backup of the primary supply voltage (-48 VDC). The optional BATMO bat-
tery package provides the
• case that allows for the installation of the batteries and provides the
temperature sensor for temperature controlled charging.
• cable set with the cables for the serial interconnection of the batteries
and the combined power and signal cable to connect the BATMO with
the POSUA battery interface.
• optionally the batteries. The four maintenance-free lead batteries
are connected in series for a backup battery block of nominal 48 VDC
with a capacity of up to 17 Ah.
The recommended batteries (refer to chapter 7: "Technical Specifica-
tions") allow operation in the upright and horizontal position.
The battery case has compartments for 4 batteries (type 12 V/17 Ah) and
provides the connection for the POSUA charging circuit and the tempera-
ture sensor. The connectors and their contact pins are mechanically pro-
tected to prevent the energised pins from short circuits. The protection

prevents from touching the contacts by metal devices or similar according

to EN 60 950.
Figure 5-14: Open BATMO battery case with batteries

(interconnecting cables not shown)
A front cover closes the battery case and protects batteries and their con-
nection points from external access. The rear of the battery case gives no
access to electric circuits or the cabling.
It is possible to install the BATMO case on walls, in cabinets or on the
ground near the UMUX 1200. The length of the power cable between the
POSUA battery interface and the batteries is limited to 3 m.

Figure 5-15: Dimensions of the BATMO battery case
227
206
425
188
Please note that the weight of the battery case with the batteries is ap-
proximately 33 kg!
The POSUA feeds simultaneously the external battery and the
UMUX 1200 units. When connecting the external battery, the battery
drains all the power from the POSUA. Thus, connecting the backup bat-
tery to an operating system is normally not hitless and creates a system re-
set.
The backup time provided by the external battery depends on the
• physical condition of the battery (age)
• charge state of the battery
• environmental temperature (battery)
• power consumption of the UMUX 1200
The maximum admissible current drain from the backup battery is 3 A.
With a mean power consumption of 100 W and a "healthy" battery this
gives the UMUX 1200 a theoretical independence of approximately 7 h.

Plug-In Units
All the plug-in units of the UMUX are designed for standard subracks of 6
HU and have the same depth while the width is variable. Plug-in units
have a width of 1 to 3 slot widths (20 ... 60 mm).
Two fixing screws secure the units plugged into the subrack (exceptions
with 4 screws are large units such as the PHLC1). Two pull-out handles at
the top and the bottom of the front of the unit help you to insert the
units into and remove the units from the subrack. Exception are the
POSUS and the "old" UBUS units, which provide one handle only on the
top.
A standardised connector system connects the signals of the units to the
backplane. All units feature the top connector providing power supply,
timing signals, internal management communication and, if applicable,
access to the UBUS of the UMUX 1200. PBUS and SBUS units additionally
feature the PBUS and SBUS connector.
Front connectors are provided for traffic and control signal interfaces. The
standard connector for traffic signal interfaces and some of the control
signal interfaces provide a latching system. You can release the connec-
tors without tools.
Figure 5-16: Plug-in unit

Cabling and connections

Signal cables All signal cables connect via front connectors to the corresponding traffic
or control units. The traffic units designed for the UMUX 1500 and
UMUX 1200 feature connector frames based on the standard DIN 41 612.
The connector caps of the cables are locked to the units by means of
latching clips (refer to figure above).
The standard traffic signal connector of the UMUX 1500 and 1200 is
slimmer than its predecessor used with the UMUX 1300/1100(E). It is pos-
sible to install units featuring the connector practice of the
UMUX 1300/1100(E) in the UMUX 1200 subrack while using the corre-
sponding signal cables and latching system.
Cables and connectors are available for all of the interfaces of the
UMUX 1500 units.
Cable tray and grounding The signal cables are fed from the connection panel to the UMUX 1200
bar cable tray. The cable tray is integrated with the adapters for 19-inch rack
installation and wall mounting.
The grounding bar for signal cables is in front at the bottom of the
subrack. It connects the screens of the signal cables to the equipment
ground. A simple clamping mechanism holds and connects the cable
screens to the grounding bar. The grounding bar is a part of the subrack
construction.
The bar features a thread for the connection of the protective earth or as
a bonding point for wrist straps for maintenance.
The cable tray provides strain relief and holds the cables in position for the
units in the UMUX 1200 subrack. Thus, it is possible to install and remove
the UMUX 1200 subrack independently from the cable tray and any in-
stalled cables.

Rack mounting The 19-inch adapter provides the cable tray and the connection point for
the external DC power supply. The access to the cable tray and to the
power connection point is in front.
Figure 5-17: Rack installation and signal cables
Legend:
1 Cable ties fix the signal cables onto the fixing bows of the 19-inch
adapter/cable tray
2 Standard ferrite toroid (all signal cables)
3 Second ferrite toroid (cables with EMC filter)

Wall mounting The wall-mounting adapter provides the cable tray and the connection
point for the external DC power supply. The access to the cable tray and
to the power connection point is at the rear.
Figure 5-18: Wall mounting and signal cables
3
1
Legend:
1 Cable ties fix the signal cables onto the fixing bows of the wall-
mounting adapter/cable tray
2 Standard ferrite toroid (all signal cables)
3 Second ferrite toroid (cables with EMC filter)

Connection panel The connection panel terminates the external traffic signal cabling with
your standard type of connectors. It converts the signal cables fitting the
UMUX units, each cable fitted with the appropriate UMUX connector. A
connection panel is also used to convert between different types of signal
cables e.g. between symmetrical and asymmetrical cables.
You must use a connection panel if you operate the interfaces of traffic
units such as the LOMIF/LOMI4 in the 75 Ω mode. Due to space conges-
tion, the connectors and cables interfacing the LOMIF/LOMI4 use symmet-
rical cables. A connection panel nearby establishes the conversion to the
coaxial cabling.
The implementation of such a connection panel depends on your applica-
tion and is available on request.
ESD / EMC and grounding

The subrack with the front cover installed represents a Faraday cage-like
construction if the cables are connected to the cable grounding bar as in-
structed. Conductive metal sheets all around the subrack protect the
UMUX 1200 from ESD and electromagnetic fields.
The mounting flanges of the UMUX 1200 subrack are conductive and
provide a conductive contact to the adapters and if applicable to the rack
if the rails of the rack provide a conductive surface.
When in operation, the equipment is protected against ESD in accordance
with IEC 61000-4-2, provided that all parts have been installed as in-
structed by the user documentation.
The power supply connection of the subrack provides a lead for system
ground. The system ground connects internally to the construction of the
subrack.
All the plug-in units used with the UMUX 1200 are ESD sensi-
tive units; they must be handled with care.

ascom
Operation and Maintenance 6

Management interfaces
The UMUX 1200 supports management interfaces in the same way as
the UMUX 1500.
For the functional description of the management interfaces, please refer
Alarm interfaces
The UMUX 1200 supports alarm interfaces in the same way as the
UMUX 1500.
For the functional description of the alarm interfaces, please refer to the
corresponding chapter in [202].
Performance control and monitoring

The UMUX 1200 supports performance control and monitoring in the
same way as the UMUX 1500.
For the functional description of the performance control and monitoring,
please refer to the corresponding chapter in [202].
Test functions and diagnostics

The UMUX 1200 supports test functions and diagnostics in the same
way as the UMUX 1500.
For the functional description of the test functions and diagnostics, please
refer to the corresponding chapter in [202].
Upgrading
For the description of the upgrade procedures, please refer to the cor-

ascom Operation and Maintenance
Manipulation of the equipment

For the description and advice on the manipulation of the equipment,
please refer to the corresponding chapter in [202].
System labelling
For the description of the system labelling, please refer to the corre-

ascom
System Specification 7
Functional specification
The UMUX 1200 has the same functional specifications as the
UMUX 1500.
For the details on the functional specifications, please refer to the corre-

ascom System Specification
Technical specification
Architecture
System System architecture : fully modular
open architecture
Implementation : configurable
according to require-
ments
System control
- Control units : type COBU<X>
- Subsystems : MIB of the NE
PETS
Management Com
Control of BUS access
Diagnostics
Conference functions
- Features and control units
- Diagnostics : COBUX, COBUV
- ECC : COBUX, COBUV
- SETS : COBUX, COBUV
- Conference function : COBUV
- UBUS highways
- 8 x 2 Mbit/s : COBUX, COBUV
COBUL
- PBUS highways
-128 x 2 Mbit/s : COBUX 145
COBUV 137
COBUL 215
- 40 x 2 Mbit/s : COBUX 146
COBUV 237
Functional equipment protection : for

– system control
and PETS
– SETS
– power supply
Implementation of external interfaces : on removable units
Unit software (EWS) : down loaded
Compatibility to existing UMUX equipment : for traffic units and
functions
Configuration : software based
UCST and UNEM
PBUS Capacity : 128 x 2 Mbit/s

with and without CAS
Logical structure : linear 128 x 2 Mbit/s
PBUS access and slot arrangement : non segmented linear
UBUS Capacity : 8 x 2 Mbit/s

Logical structure : 2 sets of highways each
4 x 2 Mbit/s
UBUS access and slot arrangement : 3 segments, non linear,
1 segment with over-
lapping highway sets.

SBUS Capacity
- VC-4 terminating : 1 x STM-1 (63 x VC-12)
- Add and drop to/from STM-1 : VC-12 in 1 STM-1
segment
Logical structure : 63 x VC-12 (TU-12)
Physical structure : 5 slots with
4 x 8 x 19.44 Mbit/s
SBUS access and slot arrangement : linear over 5 slots
pairs of slots inter-
leaved for MSP
Element Manager Element Manager : UCST R5A
Element Manager System : UNEM R5A
Management communication struc- EOC

tures - Functional unit : COBUV, COBUX
- Structure : proprietary multi-path
based on SIFOX
- NE interface to EOC : SIFOX / F-interface
- EM(s) interface to EOC : SIFOX / RS-232 C
- Addressing : proprietary EOC ad-
dresses
Bandwidth
ECC
- Functional unit : COBUV, COBUX
- Structure : proprietary multi-path
based on OSPF routing
- PDH ECC channels max. : 32
- Bandwidth PDH channels : 16 kbit/s (TS0
LOMIF/LOMI4)
64 … 1984 kbit/s
- SDH ECC channels max. : 8 with tunnelling in OSI
DCN (SDH)
- Bandwidth SDH channels : 192kbit/s, 576 kbit/s
- Total bandwidth PDH and SDH channels max. : up to 2048 kbit/s
- NE interface to ECC : internal (cross connect)
- (N)EM interface to ECC : QX-interface (10BaseT)
F-interface (RS-232C)
Tunnelling for OSI DCN
- Addressing : IP addresses
LAN (WAN)
- Type : Ethernet 10BaseT
- NE interface : QX-interface
- (N)EM interface : Ethernet 10BaseT
Q-BUS
based on RS-485
- NE interface to Q-BUS : Q1-interface
- EM(s) interface to Q-BUS : RS-232 C via converter
RS-232 C / RS-485
- Addressing : proprietary EOC ad-
dresses
- Bandwidth


Q1-master interface
based on RS-485
- Implementation : UMUX 1500 and 1200
only
- Use : Access to remote Q-
BUS via UMUX 1500
- Interface UMUX 1500 : Q1-master interface
- (N)EM interface : any
Routing IP routing
- Functional unit : COBUX, COBUV
- Routing protocol : OSPF V2.0 (RFC 2178)
- Router interfaces
- COBU<X> : F, Q1, QX,
- COBUX, COBUV : OSI tunnel
PDH and SDH ECC (not
available with COBUQ,
COBUL)
OSI routing
- Routing protocol : IS-IS (level 1)
- Router interfaces : QX, OSI tunnels
HDLC routing
COBUL
- Routing protocol : proprietary
- Router interface : Q1-interface
Cross connections and delays

PBUS cross connect Type : non-blocking
structured and non
structured signals
Capacity
- 2 Mbit/s equivalents max. : 128 x 2048 kbit/s
- 64 kbit/s equivalents max. : 4096 x 64 kbit/s
Protection between access ports

- Bi-directional (quality criteria for input selection) : 2 Mbit/s
nx64 kbit/s (n = 1 ...
31)
- Control : status monitor UCST
Broadcasting : 2 Mbit/s
nx64 kbit/s (n = 1 ... 31)
Traffic signal delays PBUS and UBUS Delay assignment

- Single TS and consecutive TS n x 64 kbit/s : minimum delay
- Non consecutive TS n x 64 kbit/s : constant delay
Delays (access points cross connect)

- Unstructured signals P12x (PBUS - PBUS) : min. 14 µs
max. 48 µs
- Structured signals P12s (PBUS - PBUS)
max. 380 µs
max. 501 µs
- Structured signals P12s (PBUS - UBUS)
max. 378 µs


max. 499 µs
- Structured signals P12s (UBUS - PBUS))
max. 248 µs
max. 369 µs
- Structured signals P12s (UBUS - UBUS)
max. 246 µs
max. 367 µs
Traffic signal delays SBUS and PBUS Delays (2 Mbit/s traffic signal reference)
- TM (X = F, O, C):
- SYNAM → SYNI<X> → SYNI<X> → SYNAM : typ. 90 µs
- ADM:
- SYNIO <m> IF_1 → SYNIO <m> IF_2 : typ. 16 µs
- SYNIF (SYNIC) <m> → SYNIF (SYNIC) <n> : typ. 16 µs
Signal interfaces
Traffic interfaces Physical implementation of traffic interfaces : dedicated units
Types
- Units with access to UBUS : UBUS units
- Units with access to PBUS : PBUS units
- Units with access to SBUS : SBUS units
Characteristics and specifications : refer to unit descrip-

tions
Units implemented Units available with UCST R5A : refer to chapter 9 "Sys-
tem and ordering in-
formation"
Synchronisation interfaces inputs ESI-1:

- Synchronisation system : SETS/PETS
- According ITU-T G.703, section 10 : 75 Ω or
120 Ω (R2A)
ESI-2:
- Impedance
- According ITU-T G.703, section 10 : 75 Ω
Resistibility to surge voltages ESI-1 and ESI-2 : 1.2/50 µs impulses
U = ±100 V
Insulation signal pins of ESI-1 and ESI-2
- ECLK2MIN<X> : 1 kV/50 Hz/60 s
- ECLK2MGUARD<X> to earth : 1 kV/50 Hz/60 s

Synchronisation interfaces outputs ESO-1:

ESO-2 and ESO-3:
- Galvanic isolation from NE and battery : no
ESO-4:
- Synchronisation system : SETS
120 Ω (R2A)
Resistibility to surge voltages ESO-1 … ESO-4 : 1.2/50 µs impulses
U = ±100 V
Insulation signal pins
- ESO-1 and ESO-4 : (R2A)
- ECLK2MOUT<X> : 1 kV/50 Hz/60 s
- ECLK2MGUARD<X> : 1 kV/50 Hz/60 s
- ESO-2 and ESO-3 : no galvanic separation
Alarm interfaces Alarm inputs:

- Number : 4
- User defined names for input signals : yes
- Active signal level : configurable via EM
- active ground
- active open.
- Thresholds for detection
- Reference : positive leg of the
battery (earth)
- "Ground state“ range : -8 V ... +75 V
with respect to refer-
ence
- "Open state“ range : -75 V … -16 V
with respect to refer-
ence
- Load equivalent of input @ voltage of -16 V : a current sink of at
least 1 mA with an im-
pedance not higher
than 20 kOhm
- Surge immunity : to 1.2/50µs surge
impulses with U =
±2000 V
Alarm outputs:
- Number : 2
- Type : solid state relays
double throw
overload protected
- Use : alarm status of NE
- "Urgent Alarm“
- "Non-urgent Alarm“
- Current admissible : < 50 mA
- Resistance : < 50 Ohm
- Open contact leakage current @ 75V : ≤ 100µA

- Immunity
- Surges
- Voltage (any alarm output lead to earth) : to 1.2/50µs surge
impulses with U =
±2000 V
- Current (between the alarm output leads) : to 0.5A applied for
10µs
- Insulation (any alarm output lead to earth) : 1 kV/50 Hz/60 s
Conditions at the alarm outputs in case of
- power fail
- "Urgent Alarm" output : active
- inactive control unit
- "Urgent Alarm" output : not active
Management interfaces F-interface

Q1-interface
QX-interface
- Data Link Layer : IEEE 802.3 Ethernet
- Physical Layer : 10BaseT
OSI-tunnel for TCP/IP management com. : Virtual LAN

via COBU<X>
Q1-master interface
- Application : Remote Q-bus master
access via UMUX 1500
and 1200
Access to SOH of STM-1 - Access to SOH bytes : via UBUS

n x 64 kbit/s
- Order wire (EOW) and user channel : E1, E2 and F1
- RS DCC : D1 … D3
- MS DCC : D4 … D12
Power interfaces
DC interface Power supply interface according : ETS 300 132-2
interface A
Interface access : subrack
Nominal input voltages (POSUS)
Maximum continuous input current : 3.0 A

Recommended fusing : 3.15 A slow blow
AC interface Power supply interface according : ETS 300 132-1

interface A
Interface access : POSUA
Nominal input voltages
- 115 VAC, voltage range : 88 VAC … 132 VAC
max. 90 % of rated power : 88 VAC … 99 VAC
- 230 VAC, voltage range : 176 VAC … 264 VAC
max. 90 % of rated power : 176 VAC … 198 VAC
Frequency : 45 Hz … 63 Hz
Operation from DC power sources : not possible
Max. converted power (internal -48 VDC rail)
- Nominal power @ 115/230 VAC : 140 W
- 88 … 99 VAC / 176 … 198 VAC : 126 W
Max. current (internal -48 VDC rail) : 2.8 A
Maximum continuous input current
- 115 VAC : < 2.0 A
- 230 VAC : < 1.0 A
DC battery backup interface Interface access : POSUA

Charger interface
- nominal voltage @ 20°C : -54.6 VDC
- temperature compensation : +72 mV/°C
Max. power drain from battery : 3A
Protection of the battery from excessive
discharging : via FET switch (POSUA)
- Automatic shutdown at : UTF = -42 VDC ± 1.5 VDC
- Automatic restart at : UTF = -45 VDC ± 1.5 VDC
Interface protection BATMO side
- Protection via : self-healing PTC fuse
- Time to high impedance : < 60 ms
Max. cable length between POSUA and BATMO : 3m
Power consumption Max. power consumption

- DC power interface
- -48 VDC : 144 W
- -60 VDC : 180 W
- Mains power interface : 180 W
Internal power supply

Power conversion DC/DC (primary to secondary voltage) : POSUS
POSUA
AC/DC (mains to primary voltage) : POSUA
Protection and life insertion: DC/DC conversion with the POSUS

- unit protection : 1+1
- load sharing : yes
- hitless life insertion : yes
AC/DC conversion with the POSUA
- unit protection : no
- protection of the AC/DC conversion : no (only 1 unit)
protection of primary
voltage via battery

backup
- load sharing : not applicable
- hitless life insertion : no
DC/DC conversion with the POSUA
- unit protection : no (only 1 unit)
- protection of DC/DC conversion : with POSUS
- load sharing : yes with POSUS
- hitless life insertion
- POSUS : yes
- POSUA : no
Concurrent power supply of the UMUX 1200 via
mains (POSUA) and the
- BATMO battery backup : yes
- power supply terminal of the subrack : not possible
Power dissipation Maximum power dissipation : depending on traffic

interfaces and installa-
tion
Vertical installation Maximum admissible power dissipation

- Natural air convection (for specified ambient) : 60 W
- Forced air convection or air conditioning : 180 W
provided specified am-
bient conditions are
fully met.
Horizontal installation Maximum admissible power dissipation

- Natural air convection (for specified ambient) : not admitted
- Forced air convection with FANU2 fan unit : 180 W
provided specified am-
bient conditions are
fully met.
Subrack
Construction Card cage for UMUX units : proprietary subrack
Modularity : versatile subrack with
- 19-inch adapter
- ETSI adapters
- wall-mounting
adapter

- 19-inch : with adapter
- ETSI (applicable standard ETS 300 119-4) : 19-inch with adapters
Installation on walls and in cabinets : with adapter
Basic construction : metallic

- Sides and rear : sheet metal
- Top and bottom : perforated sheet metal
Connection of signal and power cables

- Power supply (DC) : integrated connector
- Shields of signal cables : grounding bars in front
- Cable installation and strain relief : installation adapters
with cable tray

Capacity and slots Slots

- Number of slots : 8 standard
1 special for fan unit
- Slot width (standard slots) : 20.32 mm
4 TE
Segmentation of access
- UBUS : 8 slots
- PBUS : 7 slots
- SBUS : 5 slots
Allocation of units to slots : flexible

slot 11 dedicated
FANU2 fan unit

Construction Unit construction : proprietary for the
UMUX 1200 subrack
Installation : in slot 1of the subrack
Connection of signals and power : all internal connections
Specification Number of fans : 2

Operation : individually tempera-
ture controlled
- low speed
- high speed
Temperature control of the fan speed
- low speed : < 30 °C
- high. speed : > 50 °C
Performance
- low speed (both fans operating)
- high speed (both fans operating)
- Compensation for single fan failure
Alarm interface Types

- Optical indicator
- Local failure indicator : 1 red LED
- Failure and alarm indication : integrated with the
UMUX alarm system
- Electrical contacts
- Local contacts : none
- Failure and alarm indication : integrated with the
UMUX alarm system
Connection to the COBU<X> : all internal connections
Power supply Supply circuit : -48 VDC

(internal power rail)
Power consumption (-48 VDC rail)
- low speed (both fans operating, T = 25 °C) : < 36 mA
- high speed (both fans operating, T > 50 °C) : < 88 mA
Connection of power supply : all internal connections

BATMO battery package

Battery case Basic construction : Proprietary metal case
- Sides : sheet metal
- Rear : open
- Top and bottom : sheet metal
Battery power cable : 3-pin WAGO plug
Batteries Battery type : maintenance-free

lead batteries
- Nominal voltage : 12 VDC
- Nominal capacity : 17 Ah
Mechanical parameters:
- Dimensions max. (W x H x D) : 77 x 168 x 183 [mm]
- Weight : ca. 6.5 kg
- Cable terminals : bolts and nuts M5
Recommended commercial grade batteries : YUASA NP17-12I
Panasonic LC-RD1217P
or equivalent products
Expected lifetime for
- 20 % loss of capacity
- operation at 20 °C : up to 4 years
Performance vs. temperature
- Operation (with reduced performance) : -10 °C … + 55 °C
- Temperature range for correct charging : -10 °C … + 40 °C
- Reduction of the battery capacity by
- 20 % at : 0 °C
- 50 % at : -20 °C
Other battery types might have different parameter specifications.
EMC
Product family standard Public Telecommunication network equipment : EN 300 386-2 V1.1.3
Emission Interference voltage 0.15 MHz ... 30 MHz

- power supply port : EN 55022, class B
- traffic signal ports : Amendment to CISPR
22, class B
Radiated field 30 MHz ... 1000 MHz : EN 55022, class B
Immunity Electromagnetic field

80 MHz ... 1000 MHz, level 2, 3 V/m : IEC 1000-4-3
Conducted common mode HF disturbance
150 kHz ... 150 MHz,
modulated 1 kHz 80% AM, 3 V : IEC 1000-4-6
Fast transients/bursts : IEC 1000-4-4
- On primary supply input (C/DN) : 1 kV
- On signal cables (capacitive clamp) : 0.5 kV
Surge immunity
- Traffic and control ports : EN 300 386-2 and
ITU-T K.20
- Power supply interface : IEC 1000-4-5
- Common mode : 1 kV
1.2/50 µs (8/20µs)
- Differential mode : 0.5 kV
1.2/50 µs (8/20µs)

ESD Electrostatic Discharge : IEC 1000-4-2

- contact discharge : 6 kV
- air discharge : 8 kV
Safety Safety according to : EN 60950 / IEC 950
Ambient conditions
Storage All equipment (exclusive batteries) according to : ETS 300 019-1-1
class 1.2
Temperature range : -25°C ... +55°C
Batteries (BATMO option) : According to the speci-
fications of the battery
supplier
Transport All equipment (exclusive batteries) according to : ETS 300 019-1-2

class 2.2
Temperature ranges
- ambient air for unventilated enclosures : -25°C .. +70°C
- ambient air for ventilated enclosures or outdoor : -25°C .. +40°C
Vibration random Acceleration Spectral Density
- ASD @ 10-200 Hz : 1.0 m2s-3
- ASD @ 200-2000 Hz : 0.3 m2s-3
supplier
Operation All equipment (exclusive batteries) according to : ETS 300 019-1-3

class 3.2
Temperature range system (extended)
- Operation : -20°C ... +55°C
- Start up temperature : -20°C
up to 95%, non-
condensing
Direct ambient temperature range units (PBUS,
SBUS, new UBUS, control and power units)
- Range of operation : -20°C ... +85°C
- Compliant with specifications : 0°C … +70°C

supplier
Mechanical parameters
Dimensions Subrack without front cover (W x H x D) : 177.0 x 458.8 x 279.7
[mm]
Subrack with 19-inch adapter (horizontal view)
- without front cover (W x H x D) : 482.6 x 177.0 x 279.7
[mm]
- with front cover (W x H x D) : 482.6 x 177.0 x 283
[mm]
Subrack with ETSI adapters (horizontal view)
- without front cover (W x H x D) : 532.6 x 177.0 x 279.7
[mm]

- with front cover (W x H x D) : 532.6 x 177.0 x 283

[mm]
Subrack with wall-mounting adapter
- without front cover (W x H x D) : 177.0 x 510 x 286.2
[mm]
- with front cover (W x H x D) : 177.0 x 510 x 289.5
[mm]
Construction and layout : proprietary, adaptable

for 19-inch and ETSI
mounting practice
(refer to figures)

- without rear flanges ( W x H x D) : 188 x 425 x 206 [mm]
- with flanges ( W x H x D) : 227 x 425 x 206 [mm]
Weight Subrack (without units, FANU2)

- with front cover : 4.71 kg
- without front cover : 4.07 kg
Subrack with front cover (without units)

- with 19-inch adapter : 4.89 kg
- with ETSI adapters : 5.06 kg
- with wall-mounting adapter : 5.67 kg
FANU2 fan unit : 0.62 kg

Front cover for FANU2 : 0.07 kg
Filter unit : 0.11 kg
Weight of units : refer to unit descrip-

tions

- case without batteries : 4.2 kg
- case with batteries : ca. 32 kg
Installation
Subrack Construction and installation : proprietary with instal-
lation adapters for
horizontal and vertical
installation
Width (horizontal height) of subrack : 4 HU (= 177 mm)
Installation
- in 19-inch racks (horizontal, vertical) : with adapter
- in ETSI racks (horizontal, vertical) : with adapters
- on walls or in cabinets (vertical) : with adapter
Cable tray : 19-inch adapter
wall-mounting adapter
BATMO battery package Installation

- wall- and cabinet-mounting : via screws or similar.
- ground installation : stand alone on the
ground
Connection of signals Traffic signals (new UMUX units) : DIN 41 612

32 pins, rows a, c (b)
- Male connector : unit
- Connector cover : proprietary

- Coding keys : where applicable

- Latching system : yes
tray
Traffic signals (old UMUX units) : refer to UMUX 1300

description
Management interfaces (control unit)

- F-interface : SUBMINI D, 9 p./f.
- QX-interface : 10BaseT (RJ-45)
- Q1-interface : DIN 41 612
8 pins, rows a, c
latching system
tray
Auxiliary signals (control unit)

- Synchronisation inputs/outputs : DIN 41 612
8 pins, rows a, c
- Alarm inputs/outputs : DIN 41 612
8 pins, rows a, c
- Latching system and coding keys : yes
tray
EMC protection of signal interfaces

- Signal cables with shields : grounding bar of
subrack
- Signal cables without shields : toroidal core ferrite
Mechanical shock and vibration : ETS 300 019-1-3
Connection of power supply Subrack (internal access for power supply) : 3-pin FAST-ON type
connection
(cable provided with
subrack)
Cable tray (external access for power supply) : 3-pin WAGO connector
block
Mains : POSUA front
3-pin apparatus plug
Interface for the external backup battery : POSUA front

3-pin WAGO plug
Dependability Mean accumulated down time (MADT)

Availability traffic between any two 2 Mbit/s ports of 2 NE’s : < 10 min. per year
(excluding failures of
the transmission media)
MTTF Calculated MTTF for all categories of failures

- Single unit : > 20 years
- Detailed MTTF figures per unit : refer to the unit de-
scriptions.
Predictions based on : MIL-HD BK-217F
MTTF values of operating systems are available on request.

ascom
Implementation and Application Notes 8

Configuration of the subrack
Summary of limiting factors
for unit implementation
General all units In order to avoid functional limitations and congestions on the
UMUX 1200 buses, you should adhere to some rules for the implementa-
tion of units:
• Converted power available:
It is not possible to implement a unit (without the risk of a system
crash) if the remaining amount of converted power is insufficient (i.e.
smaller than the maximum power consumption of the unit to be im-
plemented).
In such cases, the number of power converter units (POSUS) has to be
increased. The UCST shows an indicator which displays the present
power requirements based on the units configured in the subrack.
• Number of free slots in the subrack:
The UMUX 1200 subrack offers only 8 slots for traffic, control and
power units.
It is not possible to implement a unit if the required number of con-
secutive free slots (1 ... 3) is not available.
• Equipment protection:
Depending on the unit and the protected function there are some
rules to follow if you plan to implement equipment protection. This af-
fects mainly:
− Protection of the control unit
− MSP with the SYNIO
− SETS protection with the SYNIF/SYNIC
• Bus access:
Each of the 3 UMUX busses (PBUS, SBUS and UBUS) provides its par-
ticular structure and capacity. Depending on the bus the access to the
bus is varying with the slots of the subrack.
It is highly recommended that you follow the rules for unit implementa-
tion as outlined in the next paragraphs. This procedure ensures the opti-
mum system use and avoids system reconfiguration due to later imple-
mentation of new units and functions.

ascom Implementation and Application Notes
Synoptic overview Tab. 8-1: Limiting factors for unit implementation UMUX 1200
Limiting factor Applies for ...
PBUS Units UBUS Units SBUS Units Control Units Power Units
Slot number No access in slot 21. UBUS access of Access in slots Operation in slot No limitation 1)
1)
the slot. 1) 5-9 only. 11 (and 12)
only.
Number of accessed Up to the maximum UBUS structure Up to the maxi- Dedicated PBUS No limitation 1)
PBUS, UBUS or SBUS of 32 x 4 highways can limit UBUS mum of 4 SBUS Hwy. for the
highways (each 2 Mbit/s with access. Refer to lines Control Unit
signalling). implementation (diagnostics,
notes. ECC etc.)
General - - MS and SETS Backup unit If possible, first

protection re- operates in slot implement the
quire the use 12 only. - POSUS in slot 21
of predefined
- POSUA in slot 12
slots.
4) 4) 4) 4)
Converted power No limitations 1)
available POSUS 2)
POSUA 3)
Power from external Independently of the power supply voltage you must fuse the external -48 VDC supply for 2.5 A of con-
-48 VDC supply tinuous current (Refer also to power dissipation).
Power dissipation The maximum total power dissipation per subrack (without forced cooling) must not exceed 60 W. You
must implement forced cooling with the FANU2 unit if
- the power dissipation in the subrack is higher than 60 W
- you operate units with a power dissipation exceeding 15 W per slot
- the UMUX 1200 is operated in the horizontal position
Number of consecu- You can implement a unit only if the number of consecutive free slots is greater or equal to the unit width
tive free slots (this is a mechanical limitation).
1)
Slot 11 is reserved for the control unit. With optional protection of
the control unit, slot 12 is reserved for the backup control unit.
2)
Power taken directly from the -48 V supply does not load the
POSUS.
3)
The POSUA does
− not support hitless life insertion.
− not allow simultaneous powering via the external -48 VDC bat-
tery and mains.
4)
Add a POSUS if
− you want to implement equipment protection.
− the remaining available power is less than the totalled worst
case power consumption of all units.

Control units and power

supply
Control Units If you plan to implement a redundant control unit, you must reserve the
slots 11 and 12 for control units.
The UCST shows an indicator that displays the present power require-
ments based on the power consumption of the units configured in the
subrack and the power provided by the power supply units.
POSUS DC/DC converter The POSUS power converter fits any slot of the subrack of the UMUX 1200.
For the implementation of power supply units consider the following:
• Required converted power
Depending on the number and the type of units implemented, the ca-
pacity of 1 power supply unit might not be sufficient. In these cases,
you must implement an additional power supply unit.
on requirements and system application.
The POSUS allows hitless live insertion if operated together with other
POSUS units.
POSUA AC/DC converter For the implementation of power supply units consider the following:
• Slot use
The POSUA power converter requires 2 consecutive slots in the UMUX
1200 subrack.
on requirements and system application. The 1+1 equipment protec-
tion for the POSUA is not possible.
However, it is possible to protect the DC/DC converter part of the
POSUA if the remaining 4 slots (+1 for the control unit) satisfy the re-
quirements for traffic units. This type of protection is particularly rec-
ommended if the POSUA loads an external backup battery.
Tab. 8-2: Use of the UMUX 1200 slots and protection
Power supply Protection Hitless removal Remaining slots

via and insertion
Without CU With CU
protection protection
Type Unit Traffic CU Traffic CU
DC POSUS POSUS POSUS 5 1 4 2
AC POSUA POSUS POSUS only 4 1 3 2
POSUA Not possible 3 1 1+1 2
DC interface Not possible n.a. n.a. n.a. n.a.
The POSUA does not allow hitless live insertion.

UBUS
UBUS structure The UMUX 1200 provides a subset of the UMUX 1500 UBUS access which
is optimised for maximum flexibility and load distribution.
You can look at the UMUX 1200 as a UMUX 1500 subrack with only the
slots 5, 6, 7, 8, 9, 11, 12 and 21 available.
The UBUS of the UMUX 1200 has a capacity of 16 x 2 Mbit/s. The odd
numbered highways carry the traffic signals and the even numbered
highways the signalling of the preceding odd numbered highway. The to-
tal UBUS capacity for traffic signals is therefore 8 x 2 Mbit/s, independ-
ently of whether CAS signalling is used or not.
The UBUS of the UMUX 1200 is divided into 2 sets of 8 highways each.
The highways 1 to 8 serve the slots to the left and the highways 9 to 16
serve the slots to the right, with an overlapping zone in the middle. The
structural layout of the UBUS highways in the UMUX 1200 is identical to
the layout in the UMUX 1500, if you look at the same slot numbers:
• 8 slots are connected to UBUS
• Cross over within each set of highways
• 2 slots with access to all highways (slots 10, 12)
• 4 segments of slots (S1 - S4) with different highway access are imple-
mented
The UBUS layout provides an equal distribution of the UBUS access among
the slots of the UMUX 1200 subrack. Additionally it helps to prevent the
blocking of free slots due to units with limited bus access.

Figure 8-1: Structure of the UBUS vs. slots of the UMUX 1200
subrack
UBUS highways vs slots of the UMUX 1200 subrack
Highways 9 - 16
Highways 1 - 8
5 (+ 6) 1 (+ 2) 9 13 (+ 14)
1
7 (+ 8) 3 (+ 4) 15 (+ 16)
11
3
1 (+ 2) 5 (+ 6) 9 (+ 10)
13
5
3 (+ 4) 7 (+ 8) 11 (+ 12)
15
5 6 7 8 9 11 12 21
S1 S2 S3 S4
Please note that:

• The highways reserved for signalling (even numbered) are
not available for traffic signals (the highway structure for
CAS signalling is included but not shown in the figure
above).
• The control units provide access to UBUS highways as fol-
lows
– COBUX/COBUV: Highways 1 … 8 and 9 … 16
- COBUL: Highways 1 … 8
– COBUQ: not released for UMUX 1200
• The shaded grey interconnections in the figure above show
logical connections only and represent the complements to
the UMUX 1500 UBUS implementation.
UBUS access There are a few additional limitations for the implementation of units with
UBUS access:
• Slot number:
− The special layout of the UMUX 1200 UBUS implementation has to
be considered when inserting UBUS units. All 16 highways are ac-
cessible from slots 11 and 12, 8 highways are accessible from all
other slots (5 … 9, 21).

− For several of the UBUS units, operation in slot 21 is not possible

since they cannot be addressed in this slot.
For more information on UBUS highways and slot access UBUS refer to
the table above and the corresponding paragraphs in the chapter
• Capacity of the UBUS:
The number of timeslots and highways available on the UBUS is re-
duced with each UBUS unit connected. Depending on the unit imple-
mentation on a segment, free slots might become unavailable for fur-
ther UBUS units due to highway congestion. This becomes quite evi-
dent if you implement aggregate units such as the TUNOP, seizing four
highways at a time.
A new unit cannot access timeslots or highways already occupied by
other units.
You can inspect the present highway usage and connection points on
the UBUS via the dialogue Bus Usage à UBUS. The dialogue shows
the currently accessed UBUS highways and corresponding connection
points. The highways with even numbers carry the signalling of the
• Control Units:
No traffic units can be operated in the slot(s) reserved for the control
unit (slot 11 or slots 11and 12 for systems with redundant control
unit). If you do not plan to implement a backup for the system control,
you can use slot 12 for other UBUS (or PBUS) units.
UBUS units and UMUX 1200 Please consider the following:

• Depending on the selected unit, a UBUS unit might block a complete
set of highways (4 x 2 Mbit/s).
• Some of the UBUS units feature only access to subsets of the high-
ways, which means, that such units cannot use the remaining capacity
on other highways.
• Due to a limited addressing range, it is not possible to operate some of
the units in the slot 21. For details on the UBUS access, refer to the ta-
ble “Summary of UBUS access of units”.
Selection of UBUS highways With the UMUX 1200, you can choose between an automatic mode and
and connection points an expert mode to select highways and connections points on the UBUS.
Automatic mode With this mode the traffic from/to the UBUS is automatically cross con-
nected. The EM does not provide dialogues for the definition of UBUS
highways and 'connection points'. An auto-configurator automatically as-
signs the UBUS highways and connection points required in the back-
ground.
For optimum performance of the auto-configurator adhere to the fol-
lowing rules for unit implementation of UBUS units:

Tab. 8-3: Rules for the implementation of UBUS units
Assignment of Aggregate IF Tributary IF

UBUS units
Priority 1 2 3 4 1 2 3 4
Subrack S4 S3 S1 S2 S2 S1 S3 S4
Where S1 ... S4 designs the UBUS segments of the UMUX 1200 as fol-
lows:
Segment Slots
S1 5
S2 6 ... 9
S3 11 ... 12
S4 21
Adhere to the following complementary rules:

• Do not mix "aggregate" and "tributary" units within a segment.
• Implement the "tributary" units in the slots to the left of COBU<X>.
• If possible, implement the "aggregate" units in the slots to the right of
COBU<X>.
Expert mode The (N)EM provides an expert mode for cross connecting traffic from/to
the UBUS. The expert mode allows you to select the UBUS highways and
set connection points (64 kbit/s TS) on the highways. Setting connection
points manually allows you to use the UBUS capacity optimally.
You can inspect the present highway usage and connection points on the
UBUS via the dialogue Bus Usage → UBUS. The currently accessed UBUS
highways and corresponding connection points are graphically repre-
sented. The highways with even numbers carry the signalling of the pre-
ceding odd numbered highway.
Summary of UBUS access of For details on the UBUS access of units released for the UMUX 1200 and
units the UBUS highways of the COBUV/COBUX, refer to the corresponding
table in [202].
The COBUL provides a reduced UBUS access (Highways 1 … 8). The
COBUQ is not released for the UMUX 1200.
PBUS
PBUS structure The PBUS provides a linear bus structure and thus equal bus access for the
slots 5 ... 12 of the subrack.

traffic signals (payload). Each PBUS line carries 4 x 2 Mbit/s of traffic sig-
nals and the corresponding signalling information in additional TSs.
Only PBUS access circuits with configured traffic interfaces seize
PBUS highways.
For most applications of the UMUX 1200 this requirement is automatically

honoured.
PBUS access There are a few additional limitations for the implementation of units with
PBUS access:
• Slot number:
No PBUS access is available in slot 21.
However, slot 21 has access to the UBUS. Slot 21 is used preferably for
the implementation of the first power supply unit POSUS.
• PBUS capacity:
Depending on the selected control unit, all 128 2 Mbit/s highways of
the PBUS or a subset of the 128 highways are available (each highway
consists of 2 Mbit/s of traffic signals plus the corresponding signalling
information). A unit with PBUS access always seizes the PBUS in steps
of 4 highways (2 Mbit/s), independently of whether 1, 2, 3 or 4 high-
ways are required to satisfy the requirements of the traffic signal(s). As
soon as the first TS of the first highway is configured (cross con-
nected), the complete set of 4 highways is seized on the PBUS, thus
reducing the remaining capacity by 4 highways.
This limits the number of physical PBUS accesses to 32 (32 x 4 = 128).
The PHAU figure (PBUS Highway Access per Unit) typical for each
PBUS unit indicates the maximum number of PBUS highways accessed
by a unit. This number is indicated in the tables (PHAU column) pro-
vided in the chapter 9 “System and Ordering Information”. Depending
on the unit and its configuration the unit can seize less than the PHAU
figure indicated (but always in steps of 4 highways).
You can inspect the present highway usage on the PBUS via the dia-
logue Bus Usage à PBUS. The number of accessed PBUS highways is
indicated in the PHA column (PBUS Highway Access). The maximum
figure under PHA is smaller or equal to PHAU.
• Control Units:
It is not possible to operate traffic or power units in slot 11. This slot is
reserved for the control unit. In systems with a redundant control unit,
slot 12 is reserved as well. If the system has no backup for the control
unit, it is possible to implement other PBUS (or UBUS) units in slot 12.
The COBU<X> control unit affects the capacity on the PBUS in 2 ways:
− The COBU<X> as a PBUS unit (PBUS access for the UBUS):
− The type of the COBU<X> control unit defines the available PBUS
capacity:


available slots 5 … 9 slots 11, 12,
slots 11, 12 slot 21
SBUS
SBUS structure The UMUX 1200 provides the SBUS on the slots 5 … 9.
The structure of the SBUS with respect to slots is prepared for Multiplex
Section Protection. The implementation of protection requires a special
relationship between the slots assigned to the working and the protecting
unit.
Figure 8-2: Structure of the SBUS vs. slots of the UMUX 1200
subrack
SBUS Set A SBUS Set B
Drop Bus A Drop Bus A
Add Bus A Add Bus A
Drop Bus B Drop Bus B
Add Bus B Add Bus B
Interconnection of
slots for protection
W2 W3 P2 P3 W6 W7 P6 P7 W15 W16 P15 P16 W19 P19
5 6 7 8 9 11 12 21
W Working
You must implement units providing interfaces for protection in
slots with the attribute W.
P Protecting

You must implement units providing protection in slots with the at-
tribute P. Protection works between the working and the pro-
tecting unit implemented in slots with the same value.
Please note that the shaded grey structures and interconnec-
tions in the figure above show logical connections only and rep-
resent the complements to the UMUX 1500 SBUS implementa-
tion.
SBUS access There are a few additional limitations for the implementation of units with
SBUS access:
• Slot number:
There is no SBUS access in the slots 11, 12 and 21.
• Implementation of the SYNI<X>:
The SBUS structure imposes defined unit to slot allocations if you want
to implement MSP and SETS equipment protection.
If you want to implement equipment protection please note that the
structure of the SBUS implies, that
− You configure the SYNIO units as follows:
SYNIO Slots
5 6 7 8 9
working unit B --
protecting unit B' --
It is mandatory to start the SYNIO implementation with the work-

ing unit (slot 6)!
MSP between interfaces of 2 SYNIO units (FUTURE OPTION) is only
possible with units of the same type!
− You configure the SYNIF/SYNIC units as follows:
SYNIC Slots
SYNIF
5 6 7 8 9
working unit C D
protecting unit C' D'
It is mandatory to start the SYNIC/SYNIF implementation with the

working unit (slots 6, 7)!
SETS equipment Protection is possible between 2 units of the same
type:
− SYNIF - SYNIF
− SYNIC - SYNIC
− SYNIF - SYNIC

• Implementation of the SYNAC, SYNAM:

You can configure the SYNAC/SYNAM units to any slot of the SBUS
sectors configured with the SYNI<X> unit(s)
• Capacity of the SBUS sectors:
The UMUX 1200 SBUS allows you to
− terminate 1 STM-1 (SYNIF/SYNIC) for
− 4 x 8 (= 32) VC-12.
− add/drop with 2 STM-1 IFs (1 SYNIO or 2 SYNIC/SYNIFs)
− 3 x 8 (= 24) VC-12.
Please consider the note on the SBUS at the end of the paragraphs.
• Control units:
The COBUL control unit is not released for SDH functions!
There is no support available for NEs with SDH units and functionalities
controlled via the COBUL.
Please consider the note below which shows additional limitations that
are due to the release.
With the UCST R5A the following restrictions apply for the im-
plementation of units and features
• The UCST R5A allows the implementation of SYNI<X> units
as follows:
− It is not possible to configure more than 1 SYNIO.
− It is not possible to implement more than 2 SYNIF/SYNIC
units.
• Protection is available as follows (exclusively):
− Multiplex Section Protection is only available between the
2 ports of a SYNIO (please note the restrictions for the
number of units implemented per sector).
− SETS Protection is only available with the SYNIC and
SYNIF units (please note the restrictions for the number
of units implemented per sector).
• The SYNIF_R2A.50 ESW does not allow you to operate the
SYNIF, SYNIC or SYNIO unit in the slot 8 (no UBUS access).
• The operation of 2 SBUS Sectors requires the unit templates
and corresponding ESW:
− SYNIO 605
− SYNIF 604
− SYNIC 168

Mechanical and thermal

Unit width The subrack of the UMUX 1200 features 8 slots. Each slot has a width of
4 TE ( 4 x 5.08 mm = 20.32 mm).
The width of most units is 4 TE, thus fitting a slot in the subrack. Some of
the PBUS units feature 2 or 3 times this basic width. Examples:
• PHLC1: 3 x 4 TE = 12 TE
• PHLC2: 2 x 4 TE = 8 TE
• PHLC3: 2 x 4 TE = 8 TE
• SYNIO: 2 x 4 TE = 8 TE
Some units released with the UMUX 1300 (e.g. RIGEN) feature double
width of 2 x 4 TE = 8 TE.
The width of each unit released for the UMUX 1200 is indicated in chap-
ter 9 “System and Ordering Information”.
Restrictions of unit implemen- For some units, restrictions apply to the proximity of units.
tation
If applicable, the restrictions and details are provided with the technical
description of the unit.
Heat dissipation Heating up the air within the subrack might become a limiting factor,
especially if the UMUX 1200 subrack is stacked or operated horizontally.
For the management of heat dissipation, consider
• Hot spots within the subrack due to local power dissipation
To avoid local overheating, it is recommended that you distribute the
dissipating units among the subrack. Some units such as the PHLC1
feature integrated heat management with a fan to prevent the unit
from local overheating.
• Operation in horizontal position
It is possible to install and operate the UMUX 1200 horizontally into
19-inch and ETSI racks. The horizontal operation of the UMUX 1200
requires the implementation of the FANU2 unit.
• Heating up due to ambient air
The user guide describes the installation of the UMUX 1200 subrack
considering thermal conditions within the racks.
It is essential that you respect the specified ambient tempera-
ture range for the subrack in order to preserve the system speci-
fications and prevent the system from overheating.
Summary of rules for unit Depending on application and units to be implemented the above aspects
implementation impact differently on the layout of the subrack. Apply the following rules
and instructions (summary) in the order:
• Protection of the control unit.
This defines whether slot 12 remains available for the implementation
of other units.
• Power consumption with respect to power supply units.

This defines the number of power supply units required for operation
(consider protection and future system expansions).
• Degree of protection that is required for the power supply units.
This defines the number of additional power supply units required.
• Total of required bus access and slots (considering unit width) in-
cluding power supply units.
This shows principally whether there are enough slots available in the
subrack. Reducing the degree of protection for the power supply units
might increase the number of slots available.
• Draft layouts for the physical layout of unit to slot assignment
Avoid covering slots which provide a highly flexible access to the
UMUX bus systems with "large" units (a width of more than 4 TE).
Templates for such layouts are provided.
• Assignment of SBUS units.
The UMUX 1200 SBUS covers the slots 5 … 9. The structure of the
SBUS implies rules for the unit implementation if you want to imple-
ment equipment protection.
• Assignment of UBUS units.
Since the implementation of UBUS units is critical for bus capacity and
bus access, UBUS units should be assigned first, if the capacity of the
UBUS is an issue.
• Assignment of PBUS units.
No PBUS access for slot 21.
Although the PBUS capacity is hardly an issue for the UMUX 1200,
check for sufficient PBUS capacity while adding units. Consider
− the number of PBUS highways managed by the selected control
unit.
− that the UBUS takes capacity from the PBUS (8 or 16 highways), if
you configure UBUS units.
• Distribution of power supply units.
Use slot 21 for one of the power supply units, since the PBUS is not
available in this slot.
The power supply units are best fitted into the slots that cannot be
used for UBUS units (no or wrong highway access, unit width mis-
matching) or PBUS units (no bus access, unit width mismatching).
• Checking the layout with the EM.
Check the layout of the subrack with the EM e.g. in a standalone ses-
sion. This helps to avoid problems of configuration coming up during
commissioning.
Several iterations might be necessary to find the most appropriate con-
figuration for given requirements.

Templates for unit implementation

Standard configurations The UMUX 1200 is a multi-service Access System based on a modular
construction, which allows the flexible implementation of traffic inter-
faces. Due to this flexibility the Access Systems are implemented following
the present requirements for traffic and transmission units rather than
building up standard configurations. The variable requirements of the ap-
plications covered by the UMUX 1500 and the flexibility of the Access Sys-
tem makes it almost impossible to provide templates for standard system
implementations.
For some of the most important applications however, proposals for sys-
tem implementation have been engineered:
• Cross connect with 2 Mbit/s traffic interfaces
The templates proposed for the V5.x Access Systems allow (if applicable
for service) migrations without physical reconfiguration and re-cabling of
the implemented user port interfaces:
• Migration from low end capacity of user ports to maximum capacity
available per subrack.
• Migration from PSTN to ISDN service provisioning with intermediate
steps.
• Migration from a V5.1 Access System to V5.2 service provisioning.
Although the standard management communication for the UMUX 1500
is based on the ECC, most templates reserve a slot for the SIFOX to offer
the implementation of EOC based management communication (however
not possible for all templates!). The templates propose dual power units
as a standard (except for the cross connect) plus 1 additional unit for n+1
power protection.
Please note that:
• The COBU<X> control units and control unit templates pro-
vide different bus access capacities and features:
− COBUX 146 and COBUV 237 support only 40 x 2 Mbit/s
of PBUS access capacity.
− COBUQ is not released for the UMUX 1200.
− COBUL does not support voice, V5 and SDH functions.
Accordingly, not all of the control units and unit templates
support the templates shown below.
The COBUX 145 and COBUV 137 support all the tem-
plates shown below.
• The templates of course allow variants with fewer user ports
(e.g. with fewer ISBUQ or PHLC2 units).
• Other layouts than the proposed are possible as well, but
might not allow the types of migration cited above.
• All templates for V5.x Access Systems require 2 power units.
The units are loaded with approximately 60 % of their capacity.
• The implementation of UBUS units requires particular care
with respect to the UBUS capacity available.

Cross connect
DXC 48 x 2 Mbit/s
Tab. 8-5: Cross connect: 48 x 2 Mbit/s
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS 1 X
POSUS n+1
POSUA 2)
LOMIF 1 X
LOMIF 1 X
LOMIF 1 X
LOMIF 1 X
LOMIF 1 X
LOMIF 1 X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

• The Access System is DC powered via one POSUS.
• Implement a COBU<X> instead of the LOMIF unit in the slot
12, if you need equipment protection for the control unit.
This reduces the capacity to 40 x 2 Mbit/s.

DXC 40 x 2 Mbit/s Tab. 8-6: Cross connect: 40 x 2 Mbit/s
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
LOMIF 5 X X X X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

• The Access System is AC powered via the POSUA.
• This configuration does not allow equipment protection for
the control units without substantial loss of the cross con-
nect capacity.

2 Mbit/s services
STM-1 TM 24 x E-12 with MSP Tab. 8-7: STM-1 TM: 24 x VC-12 with MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIO 1 X --
SYNAM 3 X X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

DC powering from the local battery with the POSUS allows the
implementation of equipment protection (slots 12 and 21).
• You can not use the COBUL unit to implement this
TM/ADM.
nect capacity.

STM-1 TM 32 x E-12
without MSP Tab. 8-8: STM-1 TM: 32 x E-12 without MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIF 1 X
SYNAM 4 X X X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

DC powering from the local battery with the POSUS allows the
implementation of equipment protection (slots 12 and 21).
TM/ADM.
nect capacity.

STM-1 TM for 16 x 2 Mbit/s

without MSP Tab. 8-9: STM-1 TM for 16 x 2 Mbit/s without MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIF 1 X
SYNAC 2 X X
LOMIF 2 X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

DC powering from the local battery with the POSUS allows
the implementation of equipment protection
(slots 12 and 21).
TM/ADM.
nect capacity.

STM-1 TM for 8 x E12, 8 x 2 Mbit/s Tab. 8-10: STM-1 TM for 8 x E12, 8 x 2 Mbit/s and 1 x 10BaseT,
and 1 x 10BaseT, no MSP no MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIF 1 X
SYNAC 1 X
SYNAM 1 X
LOMIF 1 X
LAWA4 1 X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
TM/ADM.
nect capacity.

Multi-service applications
STM-1 TM for multiple data
services, no MSP Tab. 8-11: STM-1 TM for multiple data services, no MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIF 1 X
SYNAC 1 X
SYNAM 1 X
LOMIF 1 X
UNIDA 1 X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
TM/ADM.
nect capacity.

CAP/HDSL access for multiple

data, PSTN and ISDN services Tab. 8-12: CAP/HDSL access for multiple data, PSTN and ISDN
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
LECA2 2 X X
PHLC2 1 X --
ISBUQ 1 X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
• You can not use the COBUL unit.
nect capacity.

Optical access for multiple

data, PSTN and ISDN services Tab. 8-13: Optical access for multiple data, PSTN and ISDN
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
TUNOL 2 X
PHLC1 1 X -- --
ISBUQ 1
Spare slots
UBUS S1, 2 X
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
nect capacity.

xDSL access point

30 x MSDL Tab. 8-14: 30 x MSDL
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
LEMU6 5 X X X X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
nect capacity.

STM-1 TM 18 x MSDL, no MSP Tab. 8-15: STM-1 TM 18 x MSDL, no MSP
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
POSUS
POSUS n+1
POSUA 2) 1 X --
SYNIF 1 X
SYNAC 1 X
LEMU6 1 X X X
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
Please note that:

(slots 12 and 21).
nect capacity.

Generic template for unit

implementation Tab. 8-16: Generic template for UMUX 1200 unit implementation
Template Slot
m 5 6 7 8 9 11 12 21
Units
COBU<X> 1 X
COBU<X> 1+1
1)
POSUS
POSUS n+1
2)
POSUA
Spare slots
UBUS S1, 2
UBUS S3
UBUS S4
PBUS
SBUS
1)
Preferred slot to implement the first POSUS unit.
2)
Preferred slot for the POSUA unit.

Power consumption and heat dissipation

Power consumption The power consumption of the UMUX 1200 has to be evaluated at 2
power interfaces:
• Interface to external power supply
This interface covers all power requirements of the subrack and its
units (power supply units included). Units with PSTN, ISDN and remote
data interfaces (NTUs) might considerably contribute to the power
consumption on this interface.
The total power consumption has to be considered for the specifica-
tion of the capacity of the external power supply.
− DC power supply
The UMUX 1200 interface to the external battery is specified:
− -48 VDC / -60 VDC
− 3 A continuous maximum current.
− Mains power supply
The POSUA mains interface is specified:
− 115 VAC / 230 VAC (45 - 63 Hz)
− 2 A / 1 A continuous maximum current.
The contribution of each unit to the power consumption on the exter-
nal power supply can be read from the tables provided with the unit
descriptions and the tables provided in the user guide [001].
• Internal power rails
The power consumption on the internal power rails defines the num-
ber of power supply units required for operation. For the implementa-
tion of protection, additional units might be provided.
The nominal specifications for the POSUS and the POSUA power sup-
ply units are:
Tab. 8-17: Capacity of power supplies
POSUS POSUA
max. current max. current
+5 VCC power rail 10 A 16 A
-5 VCC power rail 2.5 A 1A
Both rails cumulated 12.5 A 16 A
The technical data provided with each unit description indicate the
power consumption on the internal power supply rails.
It is possible to use the UCST to evaluate the power consumption on
the power rails of the subrack for all configured units. The main menu
provides a power indicator, which displays the percentage of power
consumed with respect to the amount of total converted power avail-
able. A red coloured field indicates a lack of converted power.

Heat dissipation Power dissipation within the subrack might be a limiting factor, especially
if you
• stack several systems (UMUX 1200 and other systems).
• operate the UMUX 1200 in the horizontal position.
To avoid local overheating, you should distribute the dissipating units
equally among the subrack. Installation of the subracks within racks con-
siders ambient and internal thermal conditions.
In order to preserve the system specifications and prevent the
system from overheating, it is essential that you respect the
specified range of the ambient temperature for the installation
of the subrack.
If you plan to stack systems, take into account that each system will heat
the air. In this way heated air could define the ambient thermal condition
for the system(s) installed above!
If the thermal ambient condition (in general or due to heating by systems
below) is out of the range specified for the UMUX 1200, consider and
implement the following measures, till the ambient conditions are within
the specified temperature range:
• Forced air convection through the subracks.
The UMUX 1200 subrack provides a slot for the FANU2 fan unit. The
FANU2 operates in the horizontal and vertical position.
The FANU2 features 2 fans, the operation of which is controlled by the
ambient temperature. Powering and monitoring are fully integrated
into the alarm system of the UMUX 1200. The fan unit has an alarm
interface that signals failures of the individual fans.
The subrack allows the installation of an optional air filter which filters
the air circulating through the subrack.
Depending on the installation, forced air convection is
− optional
if the UMUX 1200 subrack is operated vertically in racks, on walls
or in cabinets.
Forced air convection becomes mandatory, if the dissipated power
and ambient temperatures are not within the specified limits for
the natural convection.
− mandatory
if the UMUX 1200 is operated horizontally in 19-inch or ETSI
racks.
For forced air convection, you have two options:
− FANU2 unit (integrated in the UMUX 1200 subrack).
The implementation of the FANU2 can also help to control the
temperature in (outdoor) cabinets.
− External fan device
The external device must provide sufficient air motion via the
subrack to evacuate the heated air.
The FANUV unit, which is provided for the UMUX 1500, is not
suited for this application since it fits into vertical 19-inch and ETSI

racks and forces the air to circulate through the cross-section of

the rack.
• Implementation of heat deflection shield(s) below (and above) each
subrack.
This method is particularly applicable if you stack the UMUX 1200
horizontally with other equipment or UMUX 1200.
The heat deflection shield, which is provided for the UMUX 1500, is
not suited for this application since it fits into vertical 19-inch and ETSI
racks and evacuates the heated air to the front or rear of the rack.
• Air conditioning.
Air conditioning is normally provided for telecommunication rooms or
for equipment that is installed in outdoor cabinets.
Calculating power dissipa- While the theoretical maximum power dissipation in a subrack is straight-
tion forward to calculate, it is not easy to estimate the mean power dissipated
in a subrack. The power dissipation depends heavily on the type of units
implemented and the traffic load.
There are 2 ways to approach the mean power dissipation of a the
UMUX 1200, via the theoretical maximum power dissipation or via sum-
ming the power dissipation of units under real traffic load.
• Theoretical maximum power dissipation
The theoretical maximum dissipation is evaluated by summing the
maximum power consumption at the external power supply interface
of the UMUX 1200. It is assumed that all energy is dissipated within
the subrack. This value is easy to calculate but provides a worst case
value which is, depending on units and traffic, far above the real mean
power dissipation.
− The evaluation of the power dissipation according to this method
however provides reasonable results for the mean power dissipa-
tion if the UMUX 1200 is operated as follows:
− cross connect
− Access System for data interfaces
(no remote data units)
− channel banks with exchange line interfaces
(no ground keys)
− The method is not suited to estimating the mean power dissipation
if a considerable part of the energy provided via the power inter-
face of the UMUX 1200 is dissipated in equipment external to the
NE. This applies for the following applications:
− Access System for data interfaces with remote data units
including ISDN (remote powering)
− applications with SUBLA<X> and PHLC<X> units
(subscriber loops)
− channel banks with subscriber line interfaces
In the latter cases, you must calculate the mean power dissipation as
follows:
• Estimated mean power dissipation
The estimated mean power dissipation is calculated in 2 steps:

− Evaluation of the theoretical maximum power dissipation for

− Control units
− Power supply units
− Transmission units
− etc.
− Summing of the power dissipation of the remaining units for a
specified traffic load. Values depending on traffic load and mode of
operation are provided with the technical data in the technical de-
scriptions (e.g. for the PHLC1, PHLC2) and in the user guide [001]
(UBUS units).
The estimated mean power dissipation is the total power of all values.
IP addresses
The management communication of the UMUX 1200 and UMUX 1500 is
based on TCP/IP. For this reason, all UMUX 1200 NEs and the corre-
sponding interfaces of the EM need individual IP addresses.
Control units not yet configured use 2 default IP addresses, one for man-
agement access via the serial interfaces (here F-interface) and one for the
access via the QX-interface. A subnet mask is specified for the QX-
interface.
Depending on size an access network built with the UMUX 1200 and
UMUX 1500 Access Systems might require several hundred addresses. To
ease the implementation of a management communication network the
IP addresses are preferably structured. Since the use of IP addresses is
standardised and globally regulated, you cannot freely assign IP addresses.
The local representation of the IANA (Internet Assigned Numbers Author-
ity) provides IP addresses for public use.
The requirement for IP addresses also depends on your existing and
planned infrastructure for the management of your access network.
The default IP addresses provided with the UMUX 1200 are in accordance
with the rules for addresses used in closed private networks without
Internet access.
Calculating the number of UMUX spare units

The UMUX system and its units feature high values of MTBF (Mean Time
Between Failure). Periodically updated life MTBF values and additional in-
formation on the reliability of the system (under defined conditions) are
described in the document [003] available on request.
In the case of failures, all UMUX equipment provides very low values of
MTTR (Mean Time To Repair). The low MTTR is a result of
• Quick location of failures due to the comprehensive operation and
maintenance concept of the UMUX.
• Quick replacement of failed units due to
− inventory data identifying equipment and easing the logistics and
provisioning of spare units
− front access of signal cables

− central MIB database allowing immediate automatic re-

programming of the operation parameters for the substitute unit.
− SW download (new units only) reconfiguring the unit SW (ESW) for
the configured unit function independently of the former unit his-
tory.
• Functional protection of the power supply
If protection has been implemented, single or multiple unit failures
(depending on the degree of protection) will not affect the system op-
eration.
• Functional protection of the control unit
If protection for the control unit has been implemented, the failure of
a control unit will not affect system operation (excepted for a short in-
terruption of the traffic signals connected via the UBUS).
It is essential that you dispose of spare units to re-establish or maintain
the original degree of the quality of service after failures:
• For units without functional protection (traffic, transmission units):
• For units with functional protection (power supply, control units)

Please note that:

• It is assumed that failed units are immediately sent to the
manufacturer for repair.
• The reduced number of reserve units for power supply and
control units as indicated above apply only if the corre-
sponding protection has been implemented for a large ma-
jority of the NEs.

ascom
System and Ordering Information 9

Functions and unit software ESW
The tables following describe the functions and software released for the
UMUX 1500 together with the releases UCST and UNEM R5A. Four ta-
bles, one for each type of unit provide the corresponding ordering infor-
mation.
Please note that:
• The lists are definitive for the UCST and UNEM release R5A!
• If you configure/operate other functions than the functions
quoted in the tables below, ATR disclaims any responsibility
for system malfunction and/or failures/disturbances of the
traffic signals.
• New functions will be added with the next releases.
Element manager Tab. 9-1: Element Manager R5A
EM Part number Current APDSW SW Functional Description / Remarks

R5A
Standard Name Version Name Version
UCST EN/LZYBU 151 819/1 R5A APDSW R1C03 UCST R5Axx UCST R5A for Windows 98, ME, NT
and 2000.
CD-ROM
UNEM EN/LZYBU 351 001/1 R5A APDSW R1C03 UNEM R5Axx UNEM Basic Package R5A for HP-UX 10.20
This package supports the UMUX 1500 / 1200
and management communication via ECC.
CD-ROM

Control and power units Tab. 9-2: Functions and software of the UMUX 1200 control and
power units (UCST R5A)
Functions Unit Hardware Bootloader SW ESW Functional Description / Re-

R5A or APDSW or System SW marks

ECC, diagnostics.
ECC, diagnostics.
ROFBU 367 103/1 R2C 107 COBUX R3Exx Ditto with new unit HW/ESW
COBUV 137 4C ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R3Dxx Control Unit UMUX 1500 / 1200
ECC, diagnostics and confer-
ence function, symmetrical IFs
for the ESI-1 and ESO-4.
COBUV 237 4E ROFBU 367 103/2 R1A 205 8 BCOBU R2B01 COBUX R3Dxx Control Unit UMUX 1500 / 1200
ECC, diagnostics and confer-
ence function, symmetrical IFs
for the ESI-1 and ESO-4.
COBUL 215 5A ROFBU 367 215/1 R1A 403 4 BCOBU R2A06 COBUX R3Dxx Control Unit of UMUX 1500 / 1200
R3Exx - access to 4 UBUS Hwy.s
- support of 128 PBUS Hwy.s
Ethernet IF, F-, Q1- and Q1-
master IF.
All synchronisation interfaces
are 75 Ohm impedance.
ROFBU 367 215/1 R1B 407 BCOBU R2B01 COBUX R3Exx Ditto.
ESI-1 provides additionally 120
Ohm impedance and ESO-1
has galvanic isolation.
BATMO-SE 4E BFYBU 401 104/1 R1A - - - - - Battery module for the battery
backup with the POSUA.
The batteries are not included
with the BATMO package.
FANU2 209 4E COZBU 102 209/1 R1A 1 - - - - - Fan unit for the UMUX 1200.

Functions Unit Hardware Bootloader SW ESW Functional Description / Re-

R5A or APDSW or System SW marks
PODIS 033 ≤ 2.5d COZBU 401 133/1 R2A - - - - PODIS R1A Power distribution unit for the
remote powering of 4 HDSL
CAP desktops.
POSUA 206 4E COZBU 110 206/1 R1A 1 - - - - - Power converter unit for the
UMUX 1200. POSUA provides:
- AC/DC power conversion
to the primary voltag
(-48 VDC) and charging
(temperature controlled) of
the external backup battery
(with the BATMO option)
VIN = 110/230 VAC
PMAX = 140 W
- DC/DC power conversion
for the secondary power
supply
+IMAX = 16 A (+5 VDC)
-IMAX = 1 A (-5 VDC)
POSUS 106 3.2a COZBU 110 106/1 R1A 1 - - - - - DC/DC power converter unit
Uin -48/-60 V, Pmax. 62 W

HK: Hardware Key
PHAU: PBUS Highway Access per Unit
Please note that:
• Empty fields are "not applicable" for the corresponding
function.
• The "Bootloader" software is included in the table. The data
is readable with the inventory function of the EM.
"Name": COBUX
"Version": R3D20
"Filename": COBUX_R3.D20
PBUS units The UMUX 1200 supports the same set of PBUS units as the UMUX 1500.
For details, refer to the corresponding table in [202].
SBUS units The UMUX 1200 supports the same set of SBUS units as the UMUX 1500.

UBUS units The UMUX 1200 supports the same set of UBUS units as the UMUX 1500.
Special units The UMUX 1200 supports the same set of SBUS units as the UMUX 1500.

Ordering information
Please contact ATR or your sales representative for detailed in-
formation on ordering and product availability.
Cable cross-references Tab. 9-3: Cross-references for unit cables used with the
UMUX 1500/1200
COBU<X>: Synchronisation IFs 150 COBUX/C1.1-1 TSRBU 201 194/5000

ESI-1/ESO-1,2,3 (75 Ohm) (5m)
COBU<X>: Synchronisation IFs 150 No longer COBUX/C1.1-2 TSRBU 201 205/5000
ESI-1,2/ESO-1,2 (75 Ohm) (5m) supported
ESI-1/ESO-1,2,4 (75 Ohm) (5m)
ESI-1,2/ESO-1,4 (75 Ohm) (5m)
ESI-1/ESO-4 (120 Ohm) (5m)
COBU<X>: Alarm IFs 50 COBUX/C1.2 TSRBU 102 195/5000

4 In/UA, NUA Out (5m)
COBU<X>: Q1-master interface (5m) 50 COBUX/C1.3 TSRBU 302 197/5000
COBU<X>: Q1-(slave) interface (5m) 50 COBUX/C1.4 TSRBU 302 197/5000
Control unit - Modem [=] (5m)
COBU<X>: F- interface 15 COBUX/C3.1-3 TSRBU 102 216/540
Control unit - SIFOX cable adapter (0.5)
Control unit - Hub [=] (6m)
FANUV: Power supply + alarms fixed FANUV/C1.1-1 TSRBU 101 023/330

for UMUX 1500 subracks
FANUV: Power supply + alarms fixed New FANUV/C1.1-2 TSRBU 101 026/330
for UMUX 1500 subracks with red. control units
ISBUQ: BRA subscriber line IFs 180 ISBUQ/C1.1 TSRBU 302 204/5000
8 IFs (5m)
ISBUT: BRA subscriber line IFs 180 New ISBUT/C1.1 TSRBU 302 204/5000
8 IFs (5m)
LEMU6: CAP line IFs 180 LEMU6/C1.1 TSRBU 302 201/5000
6 IFs (5m)
LEMQ6: HDSL line IFs 180 New LEMQ6/C1.1 TSRBU 302 201/5000
6 IFs (5m)

LESA8: HDSL line IFs 180 New LESA8/C1.1 TSRBU 302 210/5000
8 IFs (5m)
LESAP: HDSL line IFs 180 New LESA8/C1.1 TSRBU 302 210/5000
8 IFs (5m)
8 IFs (<x>m) 2900
5000
10000
8 IFs (1.7m)
8 IFs (5m)
LOMI4: 2 Mbit/s IFs, 75 Ohms 120 LOMIF/C1.1-1 TSRBU 102 199/5000
4 IFs (<x>m) 2900
5000
10000
4 IFs (1.7m)
LOMI4: 2 Mbit/s IFs, 120 Ohms 120 New LOMIF/C1.1-2 TSRBU 302 200/5000
4 IFs (5m)
PCONV: 2 Mbit/s IFs, 75 Ohms 120 PCONV/C1.1-1 TSRBU 201 202/5000
2 IFs (5m)
PCONV: 2 Mbit/s IFs, 120 Ohms, 120 PCONV/C1.1-2 TSRBU 302 203/5000
2 IFs (5m)
PHLC<X>: Subscriber line IFs 180 PHLC1/C1.1 TSRBU 301 198/5000
30 user ports (5m)
PHLC3: Subscriber line IFs 180 PHLC3/C1.1 TSRBU 301 200/5000
10 user ports (5m)
8 IFs (5m)
8 IFs (5m)
SYNIC: electrical STM-1 IFs 120 New SYNIC/C1.1-1 TSRBU 201 113/5000
1 IF (requires 2 coaxial cables) (5m)
SYNIF/SYNIO: optical STM-1 IFs E2000 HRL 1 SYNIF/F1.1-1 TOKBU 101 010/1000
opt. adapter cable E2000 HRL to FC/PC
1 IF (requires 2 optical cables) (1m)
Please note that:

• The specified maximum length is a commercial length limita-
tion and not a physical limitation! For physical limitations, re-
fer to the technical specifications of the interface.

• The standard lengths are

− 5 m (= 5000 mm) for electrical cables is
− 1 m (= 1000 mm) for optical fibres.
It is possible to order cables with other lengths up to the
specified maximum length available. The length must be a
multiple of 1 m.
• The COBUX/C2.1-<X> cables are shielded cables with RJ-45
connectors:
- [=]: Signal connection as for standard ISDN cables
(4 pairs, connected 1:1)
Suited to connect the QX-interface to a LAN or
HUB.
- [X]: Signal crossed
Suited to directly connect the Ethernet-interface
of the COBU<X> to a PC/computer.
Selected accessories The table below shows important accessories for the UMUX 1200 system:
Tab. 9-4: Accessories UMUX 1200
Accessory Description Name State Doc. reference ATR reference

ordering number
75 Ohm patch panel frame 2 HE for the U1500-AC New [501] 1/BGKBU 202 101/1
UMUX 1500 and UMUX 1200.
Supported adapter cables
- TSRBU 102 208/<x>
- TSRBU 102 214/<x>
Connector locks BFD01-AC [302] NTMBU 901 101/100
(for connector sets, 100 pieces)
ETSI adapter set 4HU BFD01-SE [303] BFYBU 201 108/1

(for UMUX 1200)
(for UMUX 1500 and connector field)
Air filter set BFD01-SE [303] BFYBU 401 109/1

(for UMUX 1200)
For more information, please contact your ATR sales representa-

tive.


Belpstrasse 37
Tel.: ++41 31 999 1303
Fax: ++41 31 999 1874
Technical support: ATR Help desk

Tel.: ++41 31 999 3000
Fax: ++41 31 999 1874
Time tables Official office hours ATR: Monday - Friday 08h00 - 12h00 CET
13h00 - 17h00 CET
Help desk: 24 h a day
answering machine outside
official office hours.

Part 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Part 1

Uploaded by

Copyright:

Available Formats

ascom

UMUX from Ascom, covers all your

Technical Descriptions Systems

EN/LZVBU 221 115/1 RA

This document is protected by copyright. All rights in this c onnection remain

EN/LZVBU 221 115/1 RA Technical Descriptions System, Preface iii

About this document 1

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-1

The UNEM is based on HP workstations (UNIX). The UNEM relies on a

1-2 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

The CAUTION pictograph warns from risk of system damage

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-3

Generic sign which signals the presence of hazardous voltages!

Signals the presence of invisible laser radiation!

Signals danger for your eyes due to physically (laser), chemically

Signals activities and/or procedures which carry a significant po-

Signals possible bugs and/or malfunctions.

1-4 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Installation, maintenance and

Danger of flammable or potentially explosive gas mixtures.

ESD sensitive, related to ESD.

EMC sensitive, related to EMC.

Grounding sensitive, related to grounding.

General information on maintenance.

Temperature sensitive, related to temperatures.

Distance sensitive, related to distances.

Restricted access, related to access permissions.

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-5

Finding information ...

1-6 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-7

1-8 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-9

Please note that:

Rank within section

Short names and abbreviations used in the

1-10 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-11

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

1-12 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Tab. 1-2: UCST & UNEM R4E documents

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-13

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

[320] EN/LZTBU 360 101/1 RB UG SYNIO 165 UGU.u15.21.2.4

Please note that:

1-14 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-15

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

[701] EN/LZTBU 380 201/1 RA SM MUSIC MUSIC 100, User Manual

1-16 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Tab. 1-4: UCST & UNEM R4E documents

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-17

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

1-18 Technical Descriptions System, Preface EN/LZTBU 221 115/1 RA

Ref. Document Number RS Vol./Sect. Title Structural Doc. Id

[003] Cust. Doc. UMUX system: Reliability data summary

[903] 2/198 23- RA Cust. Doc. V5.x Questionnaire UMUX 1200/1500

Please note that:

EN/LZTBU 221 115/1 RA Technical Descriptions System, Preface 1-19

ADM Add-Drop-Multiplexer Multiplexer which adds and drops traffic signals