Abb Fox Tdm System r8 Rd 1khw002001

ABB Power Systems

FOX515 TDM System & Cross Connections User Manual

User Guide TDM System & Cross Connections (R8)

User Guide

TDM System & Cross Connections Platform FOX515 Release R8

Release History: Release 7B: February 2007 Release 8B: December 2008 Release 8C: August 2009 December 2009 May 2010

Copyright and Confidentiality: All rights of this document remain with ABB Ltd (ABB). This document contains confidential information which is the property of ABB. It must be held in confidence by the recipient and may not be used for any purposes except those specifically authorised by contract or otherwise in writing by ABB. This document may not be copied in whole or in part, or any of its contents disclosed by the recipient to any third party, without the prior written agreement of ABB.

Disclaimer: ABB has taken reasonable care in compiling this document, however ABB accepts no liability whatsoever for any error or omission in the information contained herein and gives no other warranty or undertaking as to its accuracy. ABB reserves the right to amend this document at any time without prior notice.

Document number: 1KHW002001 ABB Ltd Power Systems Bruggerstrasse 72 5400 Baden – Switzerland © ABB Switzerland Ltd, 2010 The right to modifications or deviations due to technical progress is reserved.

1KHW002001 page 2 of 57 ABB


Table of contents i Precautions and safety 4

Referenced documents 4

1 Overview of functions 7

Introduction 7

TDM traffic signals and cross connections 8 Traffic signals and cross connections 8 UBUS expert mode 9

BUS usage 9

Compatibility with other FOX 9 Signalling mode TS + 1 9

2 TDM Cross Connections 11

Cross connect dialogue and filter 11 Overview 11 Create TDM cross connections 12 Through X connections 16 Create SPR cross connections 17

UBUS Expert Modes 24 Cross connections 24 UBUS connection points 32

Protected connections 37 Basics 37 Creation of protected connections 39 UBUS 1+1 cross connections 42 Status monitoring for protected connections 45

3 Bus Usage 52

UBUS assignment 52

PBUS assignment 55

ABB page 3 of 57 1KHW002001


Precautions and safety

For generic information on precautions and safety refer to the Precautions and Safety user Guide..

Read carefully through the chapter "Precautions and Safety" before you start work and ensure that you are familiar with all safety information provided.

Observe all the precautions to limit the risk of personal injury or damage to equipment. In addition, observe the general safety procedures established by your company.

Read now "Precautions and Safety" User Guide.

Referenced documents

1KHW002000 Precautions and Safety 1KHW002057 FOX 515 Technical Description 1KHW002058 FOX 512 Technical Description 1KHW002059 FOX User Guide

1KHW002008 FOX Synchronisation System User Guide 1KHW002041 SYN4E 610 User Guide 1KHW002060 UCST / System Operation Basics User Guide 1KHW002007 FOX Network Functions User Guide



Technical support

ABB Technical Support is available as follows:

ABB Switzerland Ltd

Power Systems

Utility Communications

Bruggerstrasse 72

5400 Baden

Switzerland

Phone: +41 58 589 37 35

or: +41 844 845 845 (Call Center)

Fax: +41 58 585 16 82

E-Mail: [email protected]

URL: www.abb.com/utilitycommunications


mailto:[email protected]

http://www.abb.com/utilitycommunication



User Guide TDM System & Cross Connections (R8) Overview of functions

1 Overview of functions

Introduction

The UCST R8 provides a unified procedure for cross connections, which ap-plies to all FOX NEs.

Since the equipment have different architectures, the capacity of the cross con-nect depends on the type of the NE and the control unit implemented. For in-formation on the system capacity and the implementation of units (especially for units with respect to slots), refer to the FOX Technical Description FOX515 Technical Description and FOX User Guide.

Please note:

The FOX allows unlimited cross connections between data signals with and without CAS. The timeslot 16 is separately cross connected!

The bus access capability and available cross connect capacity depends on the selected COBU<X> control unit and control unit template.

The terms "Input" and "Output" in the TDM cross connection dialogues describe the access points/interfaces of the signals and facilitate the implementation of unidirectional and protected cross connections for data signals.

The configuration created with the UCST is a local image of a possi-ble NE configuration accessible via corresponding dialogues of the EM. To apply cross connections in the NE you have to

establish an appropriate management communication channel between the UCST and the NE.

start a full or partial download of the configuration to the NE.

You can download the configuration data as one final download for the com-pletely configured NE or in steps. A download in steps allows you a better con-trol of the interactions between the NE and the environment during configura-tion. It is possible to debug each problem coming up one by one.


Overview of functions User Guide TDM System & Cross Connections (R8)

TDM traffic signals and cross connections

Traffic signals and cross connections

The FOX allows you to cross connect TDM traffic signals as follows:

Cross connections via PBUS: 1/1 and 1/0 for 2 Mbit/s and n x 64 kbit/s traffic signals (with and without CAS)

Cross connections via UBUS: 1/0 for n x 64 kbit/s traffic signals (with and without CAS)

All cross connections for the UBUS are established via the PBUS access of the control unit.

Cross connections via SBUS: VC-3 and VC-12 Through connections (STM-4/1 to STM-4/1) for VC-3 and VC-12 Add and Drop for VC-3, VC-12 and the corresponding 34 Mbit/s, 2 Mbit/s

and n x 64 kbit/s traffic signals (with and without CAS)

Cross connections on traffic units: SYN4E: VC-4, VC-3 and VC-12

Through connections (STM-4/1 to STM-4/1) for VC-4, VC-3 and VC-12

Add and Drop for VC-3 and VC-12

For more information on the architecture and the FOX cross connect, refer to FOX515 Technical Description.

The configuration of cross connections for traffic signals is straightforward with the FOX. The switch fabric is not directly visible. The configuration of cross con-nections relies on

Traffic signals (signal rates)

Inputs and outputs (traffic interfaces of units and subunits)

Connection parameters Direction of signal flow (bi-directional, unidirectional) Protection (protected connection)

To cross connect traffic signals you have to select the corresponding signal rate and specify the connection parameters. Then you can cross connect the traffic signal between the Input and Output(s). The Inputs and Output(s) represent the signal structure in accordance with the selected traffic signal rate. The UCST automatically creates the required connection points for the SBUS, PBUS and the UBUS or on the traffic unit.

Due to some particularities of the UBUS, this automatic method does not al-ways create optimal connection points and optimal use of the UBUS capacity for all types of UBUS traffic. To bypass possible limitations the UCST provides the UBUS expert mode.


User Guide TDM System & Cross Connections (R8) Overview of functions

The UBUS expert mode allows experienced users to control the connection points on the UBUS. The architectures of the SBUS and PBUS always allow a fully automatic process.

UBUS expert mode

Thoughtless use of the UBUS expert mode will create problems rather than optimise the UBUS usage!

To use the UBUS expert mode you have to fully understand the UBUS architecture, the principles of the UBUS access and cross connection on the UBUS.

For information on system capacity and the implementation of units (especially for UBUS units) in the subrack and their UBUS access, refer to FOX515 Tech-nical Description.

The FOX allows you unlimited cross connections between data sig-nals with and without CAS.

The timeslot 16 is always cross connected separately! For details on the dialogues for (protected) cross connections and BUS usage, refer to the corresponding paragraphs in this document.

BUS usage

You can investigate the BUS usage via the menu NE Configuration Bus Usage.

The dialogue provides a tab for the UBUS and the PBUS. Bus Usage is not ap-plicable for the SBUS.

For details, refer to the corresponding paragraphs in this document.

Compatibility with other FOX

The FOX processing of the traffic signals is compatible with the processing of the FOX- U/E and-U with the exceptions as described below.

Signalling mode TS + 1 With the FOX- U/E and -U, it is possible to transport the signalling information for traffic data in the TS next to the traffic data signal (= TS+1) instead of the TS 16. The GECOD and SIFOX units provide this signalling mode.

The cross connect of the CENCA unit provides the corresponding allocation of the signalling information from/to the unit on the internal signalling highways to/from the TS of the data highways.

It is not possible to terminate or cross connect traffic signals TS+1 (= TS for the signalling) on the FOX. The FOX does not support the TS+1 signalling type.


Overview of functions User Guide TDM System & Cross Connections (R8)


User Guide TDM System & Cross Connections (R8) TDM Cross Connections

2 TDM Cross Connections

Cross connect dialogue and filter

Overview The UCST uses a generic dialogue for the overview of TDM and ATM cross connections. Via this dialogue you can access the dialogues for the creation of TDM or ATM cross connections.

To access the Cross connections overview select NE Configuration Cross Connections….The figure below shows a sample of the Cross Connections overview dialogue with TDM connections only:

Figure 2-1: Cross Connections sample dialogue

A detailed description of this dialogue and the functions of the control buttons are provided in FOX User Guide.


TDM Cross Connections User Guide TDM System & Cross Connections (R8)

The UCST R8 provides a partially-automatic process to create the cross con-nections. The process is identical for all types of units and traffic signals and is independent of the type of the access system.

Create TDM cross connec-tions

You specify the connection points (connection points means now the access points of the traffic signals), the UCST establishes all internal connections automatically. The process normally only shows the connection points available for cross connection.

From the menu NE Configuration Cross Connections

press [Create TDM …] and the Create Cross Connections dialogue opens. The dialogue pro-vides several control buttons and now empty fields.

Figure 2-2: Start dialogue Create Cross Connections

To create new cross connections (for protected cross connections, refer to the next paragraph) proceed as follows:

Specify a Group name for cross connections (traffic signals) describing the new cross connections you want to create.

To add new connections to an existing group, select the name from the field Group or enter the name of the new group (max. 32 characters).

Layer to specify the traffic signal layer: - P0 (64 kbit/s) - P0_nc (n x 64 kbit/s) - P12 (2 Mbit/s) - VC12 - VC3 - VC4



tag [Bi-directional] to clear the bi-directional selection and specify a uni-directional traffic signal connection . The default value of the option is bi-directional.

[Protected] to create protected connections. The default value of the option is not pro-tected. Refer to the paragraphs below for fur-ther explanations.

open the list Input to get the list of the units available.

and select your <unit> from the list. The UCST displays all the connection points available in the Input window below. The UCST filters the connection points according to: - selected unit (of course) - selected traffic signal layer - direction

If there are no matching connection points, the list remains empty.

select connection points from the Input window. Multiple selec-tion is possible with dragging or shift + click.

open the list Output to get the list of the units available.

and select your <unit> from the list. The UCST displays all the connection points available in the Output window below. The UCST fil-ters the connection points according to: - selected unit (of course) - selected traffic signal layer - direction

If there are no matching connection points, the list remains empty.

Select connection points from the Output window. The number of selected connection points has to match the number of selected con-nection points in the input window.

The [Create] button becomes selectable if the connection points match.

Please note that:

The [Create] button is not selectable if the number of selected con-nection points in each of the windows does not match.

The UCST needs some seconds to build up long lists of connec-tion points.

If you have selected connection points and you change the traffic signal layer in the header, you have to redo the selection of con-nection points.



Figure 2-3: Create Cross Connections sample dialogue

The UCST only presents connection points (input and output) which correspond to the specified Layer and available interfaces/ports. The UCST does not list

disabled units or subunits/functions.

connection points already connected.

connection points from subunits/interfaces that do not match the specified traffic signal layer.

connection points of UBUS units, if the UBUS capacity is insuffi-cient or the free highways do not match the possibilities of bus ac-cess of the unit (due to the hardware of the unit).

The cross connect handling on the SYN4E traffic unit is explained in detail in the SYN4E user guide.

The UCST provides two special functions for cross connections:

Through X Connections This function instructs the UCST to connect a number of matching connec-tion points in a way typically used in drop and insert applications.

UBUS Expert Mode The UCST automatically allocates the internal bus resources. For connec-tion points with UBUS units involved, you have the opportunity to select the UBUS Expert Mode. This mode allows experienced FOX experts to override the automatic allocation of the connection points on the UBUS.

Uncontrolled manual allocation of bus capacity can drastically reduce the capacity available and lead to malfunction. The automatic process provides an optimum use of the bus capacity in most cases and avoids malfunction.



The use of the UBUS Expert Mode is explicitly restricted to experi-enced FOX experts!

The UBUS expert has to fully understand the UBUS structure, the ac-cess of the units to the UBUS bus and the internal allocation princi-ples.

For more information on Through X Connections and the UBUS Expert Mode, refer to the next paragraphs.

Press [Create] to create the cross connections. [Cre-ate] remains grey and is not available as long as the selected connection points do not match.

The UCST does not create any con-nections unless you press [Create].

[Close] to quit to the dialogue.

A subunit configured for the “Clock Master” P12 mode must be cross connected to a subunit in the “Clock Master” P12 mode only!

The data format on the PBUS of the “Clock Master” mode traffic is not compatible with the data format of the “Monitored” and “Transparent” mode traffic. The UCST can not inhibit the incompatible cross connec-tions!

For details of the “Clock Master” mode, refer to FOX Network Func-tions User Guide.



The Through X Connections creates connections, where two bundles of iden-tical number and traffic signals layers are cross connected systematically be-tween corresponding numbers of connection points. The connection points at the input and output must be continuous.

Through X connections

Through X Connections are typically possible for traffic signals

VC-4, VC-3 and VC-12 in the SDH environment

A prerequisite for the use of this function is of course that the connection points presented in the Input and Output have such correspondence.

To create Through X Connections proceed as instructed above but do not se-lect connection points in the Output window.

Figure 2-4: Create Cross Connections sample dialogue Through X Connections

Press [Through X Connections] to instruct the UCST to look for matching connection points in the Output window. The UCST assigns a corresponding number of continuous connection points at the lowest posi-tion possible.



Figure 2-5: Create Cross Connections sample dialogue Through X Connections


[Close] to quit to the dialogue.

Create SPR cross connec-tions

In the linear point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) network applications, the network survivability can be enhanced by a shared protection ring (SPR).

P2MP and MP2MP applications are supported by the following FOX units:

DATAS, DATAV, DATAR, DATAT,

STIC1, STIC2, the terminal type must be CPE; the CPE must have a data interface,

NEMSG.

A shared protection ring (SPR) makes economical use of the available band-width by sharing the protecting bandwidth for all network sections in the linear network.



Figure 2-6: Protected P2MP connections

A network element in a linear P2MP or MP2MP network requires up to 6 unidi-rectional SNC protected cross connections to be configured:

Figure 2-7: Unidirectional cross connections in a slave network element with NEMSG, P2MP application

The cross connections configuration for the P2MP or MP2MP application with a SPR is supported by UCST through a specific configuration window, the SPR



connections wizard. This wizard is started by clicking the “Create SPR…” but-ton in the cross connections dialogue.

Figure 2-8: UCST cross connection window

The empty SPR connections wizard dialogue opens:

Figure 2-9: UCST SPR wizard window



The SPR connections wizard fields are completed step by step. Please refer to figure 2-10:

Optional step: Group A group name for the SPR cross connections can be given. All created cross connections will have the same group name. A group name allows easier maintenance and operation of the SPR cross connections.

1st step: NE type The P2MP and MP2MP applications use different NE types, depending of the role an NE plays and where it is located in the linear network. The avail-ability of NE types depends also from the application type and the unit type involved. :

DATAx, STICx NEMSG

NE type P2MP MP2MP P2MP MP2MP

Master NE Head End E - E E

Master NE Half Duplex All-to-All - E - -

Master NE E - E -

Slave NE E E E E

Slave NE without DTE n.a. n.a. n.a. n.a.

Slave NE Tail End E E E E

2nd step: Point to multipoint interface – Unit: Select the unit performing the P2MP or MP2MP application. Depending of the NE type the unit transport operation mode (DATAx, STICx) or confer-ence type (NEMSG) must be configured accordingly:

NE type DATAx, STICx NEMSG

Master NE Head End normal point-to-multipoint or multipoint-to-multipoint

Master NE Half Duplex All-to-All point-to-multipoint -

Master NE point-to-multipoint point-to-multipoint or multipoint-to-multipoint

Slave NE point-to-multipoint point-to-multipoint or multipoint-to-multipoint

Slave NE without DTE n.a. n.a.

Slave NE Tail End normal point-to-multipoint or multipoint-to-multipoint



3rd step: Point to multipoint interface – SbU: Select the subunit performing the P2MP or MP2MP application. Depending of the unit the following subunits are available:

NE type DATAx STICx NEMSG

Master NE Head End interface DSL interface or conference MP->Sl orconference participant

Master NE Half Duplex All-to-All interface DSL -

Master NE interface DSL conference

Slave NE interface DSL conference

Slave NE without DTE n.a. n.a. n.a.

Slave NE Tail End interface DSL interface or conference MP->Ms

4th step: Trunking interface – Towards SPR or master – Unit and SbU: Select the P12 transport unit and subunit used for the network direction to-wards the SPR or towards the master NE. The availability of directions de-pends on the NE type, see table below. Note that the working and shared protection ring time slots in a direction are always transported in the same P12 signal.

5th step: Trunking interface – Towards SPR or slave – Unit and SbU: Select the P12 transport unit and subunit used for the network direction to-wards the SPR or towards the slave NE. The availability of directions de-pends on the NE type. Note that the working and shared protection ring time slots in a direction are always transported in the same P12 signal:

towards

NE type Master SPR Slave

Master NE Head End - E E

Master NE Half Duplex All-to-All - E E

Master NE E - E

Slave NE E - E

Slave NE without DTE E - E

Slave NE Tail End E E -

6th to 9th step: Working path TS and shared protection ring TS: Select the time slots for the working and protecting path towards the master NE or towards the slave NE or towards the SPR. The number of time slots in all paths must be the same and must correspond to the selected SbU band-width. Note that in direction towards SPR no working path is available.



Figure 2-10: SPR wizard configuration

Optional step:cross connection group name

1. step:select the NE type

2. step:select the multipoint unit

3. step:select the subunit of the multipoint unit

4. step:select the unit LOMIF <1> and subunit 2Mbit/s-1 as trunking interface towards the master NE

5. step:select the unit LOMIF <3> and subunit 2Mbit/s-8 as trunking interface towards the slave NE

6. step:select time slot T11 as the working path TS towards the master NE

7. step:select time slot T12 as the shared protection ring TS towards the master NE

8. step:select time slot T21 as the working path TS towards the slave NE

9. step:select time slot T22 as the shared protection ring TS towards the slave NE

The above figure shows the connection wizard setup for the network element in figure 2-7.

When clicking the ‘Create’ button, UCST creates the six SNC protected unidi-rectional cross connections on the P0 layer.



Figure 2-11: SPR wizard created cross connections

Repeat above procedure with the SPR wizard for each network element in-volved in the SPR structure.

Once cross connections are created using the SPR wizard, the cross connec-tions are handled in UCST as any other cross connection, i.e. they can be de-leted, modified and the status can be checked.

Please refer also to the section ‘Protected connections’ in this docu-ment for a description of the SNC protection mechanism.

The SPR configuration for the STICx unit is the same as for the DATAx unit.



UBUS Expert Modes

Cross connections The UCST automatically allocates the internal bus resources. For connection points with UBUS units involved, you have the opportunity to select the UBUS Expert Mode. This mode allows experienced FOX experts to override the auto-matic allocation of the internal buses and timeslots.

The UBUS Expert Mode is useful if the remaining capacity on the UBUS be-comes critical with respect to the traffic to connect or for special applications and units.

The automatic mode can only create new connection points with the knowledge of the existing connections points. The UBUS Expert Mode allows you to plan the allocation of the connection points with the knowledge of all cross con-nections required. This allows you to avoid future problems on the UBUS high-ways in advance.

Uncontrolled manual allocation of bus capacity can drastically reduce the capacity available and lead to malfunction. The automatic process provides an optimum use of the bus capacity in most cases and avoids malfunction.

The use of the UBUS Expert Mode is explicitly restricted to experi-enced FOX experts!

The UBUS expert has to fully understand the UBUS structure, the ac-cess of the units to the UBUS bus and the internal allocation princi-ples (information provided in FOX515 Technical Description).

To enter the UBUS expert mode, you prepare the creation of your connections as usual with the selection of matching connection points of the Input and Out-put.

Tag [UBUS Expert Mode] in the Create Cross Connections dia-logue.

Figure 2-12: Create Cross Connections sample dialogue in with active UBUS Expert Mode




Select only a small number of connection points for cross connection and only if you are sure about the creation of the cross connections.

The UCST does not allow you to quit the creation process unless all the selected cross connections are established!

The new cross connection can use connection points on the UBUS as follows:

Both connection points use the UBUS

Only the first or the second connection point use the UBUS

Depending on the UBUS usage when you start up the UBUS Expert Mode, the automatic procedure adapts the dialogues provided. If the unit connections are already set for a particular unit then the automatic procedure skips the corre-sponding dialogues.

Please note that unused UBUS connection points can interfere with a new configuration, if released UBUS connection points have not been cleared!

To clear released connection points of units without tributary inter-faces, you must

delete the unit from the configuration

disable the corresponding subunit

delete the UBUS connection point via the NE Configuration UBUS Connection Points menu

Assuming that no connection points for the units have been set on the UBUS so far, the UBUS Expert Mode pops up with dialogues as shown below.

Figure 2-13: Create Cross Connections sample dialogue in UBUS Expert Mode (Create first point of first X)



The dialogue allows you to select individually the connection points for P0 (64 kbit/s) traffic signals to time slots and UBUS highways available. The big win-dow shows graphically all the highways and the corresponding time slots and monitors the connection points. The UCST represents the free time slots of the highways with "=" and the configured with "+".

The UCST reduces the representation of the highways that are not configurable with the selected NE, e.g. the even numbered (signalling) highways for the FOX 515/512. For more information on the presentation, refer to the paragraphs on Bus Usage below.

The part New Connection Point of the dialogue indicates at the top the selected (e.g. input) connection point and provides fields for information and functions as follows:

Unit shaded grey The field displays the unit name and corresponding slot number.

Subunit shaded grey The field displays the subunit name and "user label".

Channel shaded grey The field displays the channel number (if applicable).

Highway context sensitive The field allows you to select a high-way from the highways available and which the unit hardware is able to ac-cess (in the selected slot). For infor-mation on the UBUS structure of each NE and the access of units to the UBUS highways, refer to FOX515 Technical Description.

Timeslot context sensitive The field allows you to select time slots in the selected highway. The UCST does not allow any "wild" con-figuration but imposes its rules if ap-plicable. In this case (typically for ag-gregate IF), you cannot select the time slot.

CAS context sensitive The field allows you to define whether the connection is set with or without signalling. If signalling is set it is con-nected as follows: - FOX 515/512: - CAS Off - Highway +1 - FOX- U/E and -U: - CAS Off - Highway +1 - Timeslot +1

The selection is only possible if the selected NE and the corresponding traffic interface allow such options.

This dialogue pops up for each of the connection points to be created on the UBUS. If only one of the 2 connection points of a cross connection uses the UBUS, the dialogue pops up only for this connection point. The other connec-tion point (on the PBUS) is set automatically.



Select <Highway> from the Highways field (here for MEGIF in slot 10: 7, 5, 3, 1).

You cannot select the TS, since the MEGIF unit is an aggregate unit. The UCST sets the first connection point automatically to the TS selected for the first cross connection (here TS 11).

<CAS> from the CAS field (here CAS OFF, Highway +1)

Press [Ok] to create the connection point (here the first connection point on highway 7).

The dialogue pops up again if the cross connection requires a second connec-tion point on the UBUS.

The dialogue monitors the connection point on the highway with a "+" (here TS 1 on highway 7 and the TS1 on the signalling highway 8) and creates a list con-taining the parameters of the connection points. This time the list has only one column for the first connection point with a corresponding entry for highway 7.

Figure 2-14: Create Cross Connections sample dialogue in UBUS Expert Mode (Create second point of first X)

For the explanation of the terms used in the columns Timeslots [1 … 31] and Connection Point <k> refer to the "Bus Usage" paragraphs.

To create the second connection point on the UBUS

select <Highway> from the Highways field (here for SUBLA in slot 14: 9, 11).

<Timeslot> You can now select the TS on the highway (e.g. 14), since the SUBLA is



a tributary unit and allows a free allo-cation.

You cannot set the CAS mode since the SUBLA is configured with CAS. (The FOX- U/E and -U additionally al-lows the CAS mode Timeslot +1).

Press [Ok] to create the connection point (here the first connection point on highway 9).

This concludes the cross connection of the first of the four selected P0 (64 kbit/s) traffic signals and at the same time starts the sequence for the second cross connection.

The UCST automatically pops up with the updated dialogue (first connection point of the SUBLA) for the first connection point (here on MEGIF) of the sec-ond traffic signal:

Figure 2-15: Create Cross Connections sample dialogue in UBUS Expert Mode (Create first point of second X)

In this example, you now can only select the CAS mode, since all other pa-rameters (of the MEGIF access) have been initialised with the first connection point of the first traffic signal.

Press [Ok] to continue and create a new connec-tion point (here the second connection point on highway 7).

The UCST has now added a second column in the list (not visible in the dia-logue below) which monitors the second connection point on the highway (here for TS 12 on highway 7).



Figure 2-16: Create Cross Connections sample dialogue in UBUS Expert Mode (Create second point of second X)

To create the second connection point on the UBUS

select <Highway> from the Highways field (here for SUBLA in slot 16: 9, 11). Since the SUBLA unit is a tributary unit, you are free to select any of the available highways.

<Timeslot> Since the SUBLA unit is a tributary unit, you are free to select any of the available TS (e.g. 15) on the highway.

You cannot set the CAS mode since the SUBLA is configured with CAS. (The FOX- U/E and -U additionally al-lows the CAS mode Timeslot +1).

Press [Ok] to create the connection point for the SUBLA (here the first connection point on highway 11).



Figure 2-17: Create Cross Connections sample dialogue in UBUS Expert Mode (Create first point of third X)

Continue to create connection points on the UBUS, until all selected cross con-nections are established and the Create Cross Connections dialogue pops up for the selection of further cross connections.

If the dialogue does not appear as expected, this means that there is no choice for connection points.

Figure 2-18: Create Cross Connections sample dialogue in UBUS Expert Mode



Please note that

for units with aggregate interfaces (e.g. MEGIF, TUNO<X> etc.) the UCST releases the connection points on the UBUS with the re-moval of the corresponding cross connections.

For the specification of units with aggregate interfaces refer to FOX515 Technical Description):

for units with tributary interfaces (e.g. EXLA<X>, SUBLA<X>, SIFOX, UNIDA etc.) all set connection points remain active even if you delete the cor-responding cross connection unless you delete the unit from the configuration

disable the corresponding subunit

delete the UBUS connection point via the NE Configuration UBUS Connection Points menu

The operation only removes the connections of the affected unit. The second connection point of the cross connection might still ex-ist!

For the specification of units with tributary interfaces refer to FOX515 Technical Description):

The User 0 identifies connection points on the UBUS without (ac-tive) cross connection.

If there are new cross connections for interfaces with already exist-ing connection points, the UCST uses the already set connection points.

The UCST will skip the UBUS expert mode for such connection points!



Outside the Cross Connection dialogues the UCST R8 provides the UBUS Connection Points menu which allows the FOX expert to prepare new and clear unused UBUS connection points for the cross connection.

UBUS connection points

This functionality is only available for UBUS units with tributary interfaces (e.g. EXLA<X>, SUBLA<X>, SIFOX, UNIDA etc.). Units with aggregate interfaces are not supported (it does not make sense).

You access the UBUS connection points dialogue via the menu NE Configu-ration Bus Usage.

Figure 2-19: UBUS Connection Points sample dialogue

Obviously, this dialogue is almost identical with the dialogues provided by the UBUS Expert Mode.

You can now add additional connection points for UBUS tributary units and their traffic signals:

Select <unit name> from the Unit field to select your unit (here UNIDA <12>).

<subunit> from the Subunit field to select your traffic signal (here Port-1 yourLabel-Sub-1).

<channel> if applicable.

<highway> from the Highway field (here for UNIDA in slot 12: 9, 11, 13, 15).

<timeslot> from the Timeslot field (here for UNIDA in slot 12: 1 … 31).

When you have selected all your parameters for the connection point

press [Create] to create the connection point.




Repeat this procedure until you have created all the connection points that you wish.

If there are unused connection points (= connection points with 0 user. Refer to the dialogue above) it is at any time possible to clear such connection points.

The procedure to clear connection points is indirect:

You press [Delete] in the UBUS Connection Points dialogue. This has no ef-fect on the Connection Points but calls the UBUS TP Deletion dialogue.

Select the UBUS Connection Point that you want to delete and press now [Delete] in the UBUS TP Deletion dialogue.

The dialogues below illustrates this procedure.




You want to remove the UNIDA <12> Port-1 from highway 15 and but it to high-way 13.

Press [Delete] to call the UBUS TP Deletion dia-logue.

Select <TP to delete> either via the Unit/Subunit selection fields or by clicking into the corre-sponding Connection <k> field.

Figure 2-22: UBUS TP Deletion sample dialogue

Press [Delete] to delete the selected Connection Point.

[Close] to close the UBUS TP Deletion dia-logue.





Now you can add the UNIDA <12> Port-1 to the highway 13.

Select <13> from the Highway field (here for UNIDA in slot 12: 9, 11, 13, 15).

<5> from the Timeslot field (here for UNIDA in slot 12: 1 … 31).

When you have selected all your parameters for the connection point

press [Create] to create the connection point.




The Connection Points are numbered according to ascending time slots. This can shift the logical connection points with respect to the number <k> when you add new connection points.



Protected connections

The FOX and its units provide various mechanisms and schemes for traffic pro-tection:

SNC protection (SubNetwork Connection protection)

LTP (Linear Trail Protection)

MSP (Multiplex Section Protection)

1+1 Path protection for selected UBUS units

Section protection (physical section for selected units)

The above protection types are not generally available in the FOX. The avail-ability depends on the traffic unit and the processed traffic signal layer.

The standard (ETSI EN 300 417-1-1 V1.2.1) provides traffic models for the dif-ferent protection schemes which define the applicable layers and termination points.

The chapter "Protection of Traffic Signals" in FOX Network Functions User Guide provides a detailed description of the FOX protection mechanisms and the supported protection types.

Most of these protection types require commissioning on the cross connect level. Her nec-tions in a S units with 1+1 protection are cross connected as any other protecgives an protection

e, the UCST R8 supports the configuration of protected cross con uniform way (e.g. the traffic signals for UBU

ted cross connection). The table below overview of the commissioning levels that are affected by the different types.

Figure 2-25: Commissioning level of protection types

Protection Commissioning level Examples

Mode Cross connect Unit

SNC protec-tion

Yes No P0_nc, P12x and P12s PBUS trafficVC

-12 (SYNVA, NEBRO, NEBRA),

EBRA, SYN4E) VC-3 (NEBRO, NVC-4 (SYN4E)

LTP Yes No VC-12 traffic (SYNAC, SYNAM/D) VC-3 traffic (SYTEL)

1+1 Path Protection

Yes Yes UNIDA, NEMCA, GECOD, SULIC and SIFOX (protection proprietary)

MSP No Yes SYNIO, SYN4E, ATIOP

Section protection

No Yes TUNOP, TUNOS, TUNEL (protection proprietary)

As an exabelow shP12s trafnect.

Basics

mple for the configuration of protected cross connections, the figure ows the connection principles of SNC protection for P0_nc, P12x and fic signals. The protection is a built in feature of the PBUS cross con-



Figure 2-26: SNC (Sub-network Connection) protection with FOX (PBUS access based)

SNC protection between 2 FOXs requires (according to the stan-dards) "Consistency of the Server Layer"!

Such consistency is only possible for transparent network connections (i.e. transparent for 2 Mbit/s traffic signals).

At the network side ("Input") the protection creates a second interface for the backup trail section. The FOX cross connect connects both “Input” interfaces to the same “Output”, which carries the protected traffic signal.

The traffic signals between "Inputs" and "Output" can be unidirectional or bi-directional. For bi-directional connections, the “Output” broadcasts its traffic sig-nal permanently to both "Inputs" while the "Output" selects the incoming traffic signal between the signal outputs of the 2 “Inputs” according to the defined switching criteria provided by the server layer.

The PBUS access of the "Output" selects the active input:

In the case of a failure or if the quality of the selected input signal decreasesthe "Output" automatically selects the signal from the alternate input if the

rtive, non-revertive) depends on protection type and

on switch s rced switchVC-3 and VC-12 traffic.

The FOX 515/512 and legacy FOX- U/E and -U have different imple-entation ss connec

lection and the possibilities for t ng of the protection status are not equivalent.

,

signal is available.

If the formerly failed input signal becomes available again while the now se-lected input signal continues to perform, the path will switch back to the pre-viously selected input signal; thus, the protection switch is revertive.

The switching mode (reveunit. The FOX provides maintenance functions which allow the monitoring of theprotecti tatus and fo ing of protected P12x/P12s, VC-4,

m s of the cro t. Hence, the criteria for the input se-he monitori



For more details of the FOX protection mechanisms and supported protection types, refer to the chapter "Protection of Traffic Signals" in FOX Network Func-tions User Guide. The creation of protected connections as described below applies for the FOX 515/512 and FOX- U/E and -U.

Please note, that SNC protection or LTP in the FOX 515/512 is sup-ported as follows (availability of protection and protection type depend on the selected unit and traffic signal layer!):

With PBUS and some SBUS units.

Between PBUS/SBUS and UBUS units with the PBUS/SBUS unit at the network side ("Input").

Not possible between UBUS units.

Figure 2-27: Cross Connections sample dialogue filtered for protected connections

In pr c c ea e ections the same way as you create you have to specify the second input

in iple you can r t protected connstandard cross connections. Additionally for the protected output. The Input becomes a Working and a Protecting Input.

w pr ct Cross Connections.

s

tag Direction ls if ap-

tag Protection .

Creation of protected con-

To create a ne otected cross conne ion select the menu NE Configuration

Press [Create…] to call the Create Cross Connectionsdialogue.

Select Parameter for Group and Layer as required.

for bi-directional traffic signapropriate.

to select protected cross connections

nections



Figure 2-28: Create Cross Connections sample dialogue with protected connections

Instead of one Input field, the dialogue switches the two fields Working and Protecting active (refer to the figure below):

Working is the connection point of the first in-put, which is connected to the nor-mally active signal channel (network side).

Protecting is the connection point of the second input, which is connected to the standby channel (network side).

Output is the connection for the traffic signal (access side) which will be protected in the network (network side).

To create the protected connection

select for the <Working input> the corresponding traffic unit from the list provided for the Working input.

the connection points for the traffic signal from the field provided for the Working input.

select for the <Protecting input> the corresponding traffic unit from the list provided for the Protecting input.

ection ignal from the Protecting input.

select for the <Output> the corresponding traffic unit from the list provided for the Output.

a matching number of connection points for the traffic signal from the field provided for the Working input.

a matching number of connpoints for the traffic sfield provided for the



Figure 2-29: Identification of the Working, Protectintion points for protected traffic

g and Output connec-

Please note, that the above picture is generic and does not imply a particular protection type (the protection type depend on the selected unit and traffic signal layer!):

Figure 2- ons sample dialogue ns

30: Create Cross Connectiwith protected connectio

Press [Create] to create the connections.

[Close] to quit the dialogue.



Figure 2-31: Cross Connections sample dialogue filtered for protected connections

Please note the filter settings.

lementatio s connectionslogues below (it is assumed that you have a configured UBUS unit in a 1+1 pro-

ion option is configured on the unit and subunit level (as it applies e.g. for the UNIDA).

If the 1+1 protection option is not enabled you cannot create the UBUS 1+1 protected connection on the system level.

From the NE Configuration Cross Connections menu

press [Create] to start the Create Cross Connections dialogue.

select a group <name> (optional) here UBUS 1+1

<layer> here P0 for your traffic signal

toggle the box Protection to become active.

select Working <unit, SbU, TS> for the working traffic signal input.

Protecting <unit, SbU, TS> for the protecting traffic signal input.

Output <unit, SbU, 1+1> for the traffic signal output.

UBUS 1+1 cross connections The paragraphs below apply for UBUS units with 1+1 protection modes only!

The imp n of cros requires steps as shown in the dia-

tection mode; the example below is for the NEMCA):

Make sure that the 1+1 protect

Implementation



Figure 2-32: Create Cross Connections sample dialogue UBUS units with 1+1 protection

Press to create the connections.

Reppro le protection mode.

he Cross C e cross connections with the NEMCA.

[Create]

eat the above steps with "NEMCA <12> Port-2 Sub-2-1+1Rev" to create a tected cross connection for the UBUS units 1+1 Reversib

Press [Close] to quit to the Cross Connections dia-logue

Tth

onnections dialogue (with sub-filter Unit: NEMCA<12>) now show



Figure 2-33: Create Cross Connections sample dialogue UBUS units with 1+1 protection

Please note that

With the UCST R8, when reading a UCST R4<X> configuration that contains 1+1 D and 1+1 R connections of a SbU, the connec-tions are grouped in one single protected MC.

The UCST R8 no longer supports all the special 1+1 connection

support. cases provided with the UCST R4<X>. For detailed information, please contact your customer

No status monitoring is available for the UBUS units 1+1 protection modes.



Y US connection points for the U e .

UBUS tab

ou can investigate the implementation of the UBBUS units 1+1 connections via the menu NE Configuration Bus Usag

Figure 2-34: BUS Assignment sample dialogue

The UBUS unit 1+1 protected connections here are on highway 9. The dialogue is scrolled to show the 2 columns with the connection points for the

-

Status monitoring for protected connectionection path and to debug the protection. is available for the FOX 515/512 only.

To monitor a protected connections select the menu NE Configuration Cross Connections.

Select <Protected connection> from the list of connections. You may use the sub-filter Protected to filter protected connections in the list.

Press [Status] and the Cross Connection Status dialogue pops up.

The button [Status] only becomes active if

UBUS Usage

NEMCA<12> 1+1 Reversible protection:

The working connection point has the index W at the end of the naming sequence.

The protecting connection point has the index P at the end of the naming sequence.

ns allows you to trace the active con- Status monitoring for the connections

Status monitoring for pro-tected connections



a rotected connection is selected. p

the NE and the traffic unit support the corresponding function.

The functions available are identical for all types of connections with one excep-tion:

P0 (64 kbit/s) and P0_nc (n x 64 kbit/s) Do not support forced diagnostic switching between the 2 alternate signal paths.

All other types of connections Support the forced diagnostic switching between the 2 alternate signal paths.

Figure 2-35: Cross Connection Status P0_nc layer sample dialogue

The top of the dialogue provides the basic information on the selected cross connection (Group, Type and Direction). The Cross Connection Status dia-logue provides 3 fields to monitor the status of the protection circuit: One field for each connection point.

The initial dialogue provides no information on the protection. To get the corre-sponding information you have to first get the status from the NE:

Press [Get] to upload the status information from

[Get] is only active if the UCST has an active management communication

Cross Connection Status

the NE.

with the NE.

(P0, P0_nc)



Figure 2-36: Cross Connection Status P0_nc layer sample dialogue Reading data

During the upload of the data, the UCST displays the status Reading... in the two status fields.

Figure 2-37: Cross Connection Status P0_nc layer sample dialogue Working condition

The fields provide information as follows:

Working and Protecting Subunit Parameters of the Connection point of the

traffic signal in the working path (Unit name, slot, subunit name, TSs)

Status can take the expressions: OK Signal of the interface is available TSD Trail Signal Degraded (criterion for switching) TSF Trail Signal Failed (criterion for switching)

Output Subunit Parameters of the Connection point of the

traffic signal (Unit name, slot, subunit name, TSs)



The UCST indicates the currently active signal path with a solid arrow pointing from the active Input to the Output field. The other input has a dotted arrow tothe Output window.

the s the signal source.

ig re -38: Cr s o nection Statu

If the input signal of the working path is degraded or fails, the Output selects protecting input a

Press [Get] to update the status fields.

F u 2 os C n s P0_nc layer sample dialogue

The switch of protected connections is revertive. If the signal on the working in-put is available again and not degraded, the output switches back to the work-ing input as its signal source.

Press [Close] to quit to the Cross Connection Status dialogue.



The cross connection status dialogue for the all connection types except P0 and P0_nc provides an additional diagnostic function that allows you to force the signal path to working or protecting.

All other parameters and functions of the Cross Connection Status dialogue remain identical.

Press [Get] to upload the status information from the NE.

[Get] is only active if the UCST has an active management communication with the NE.

Select the box External Command and select e.g. Force Protecting.

The example below shows the P12 layer cross connect status.

Figure 2-39: Cross Connection Status P12 layer sample dialogue

The External Command allows you to force the signal path to the Working or the Protecting circuit.

The selection of a forced switching command calls up a warning dialogue:

Figure 2-40: External Command confirmation dialogue

Press [Ok] if you want to switch the signal path tothe Prote

cting circuit else press [Can-

cel].

[Get] to upload the status information from the NE.

Cross connection status (all types except P0 and P0_nc)


1KHW002001 page 50 of 57


The dialogue now displays the new Cross Connection Status after the forced switch command.

If a circuit fails and a forced switch command forces the circuit selection to the iled circuit, the circuit selection persists.

he Cross Connection Status dialogue below shows this situation after the fail-re of the Protecting circuit.


fa

Tu

You can release a circuit selection which is blocked by a Forced Switch com-mand with the Release command:

Select Release from the External Command box.

Press [Get] to upload the status information from the NE.

ABB




The protection mechanism now automatically selects the Working (available) circuit for the signal path.

User Guide TDM System & Cross Connections (R8) Bus Usage

3 Bus Usage

You can investigate the BUS usage and tand PBUS via the menu NE Configuratio

for each bus

FOX- U/E and -U: UBUS

FOX 515/512: UBUS, PBUS

UBUS assignment

he connection points on the UBUS n Bus Usage.

The dialogue provides a tab system implemented in the selected NE:

The dialogue under the UBUS tab showspresentation that the UCST uses in the U

Bus Assignment sampleUBUS a

the same information with the same BUS Expert mode.

The following dialogues refer to the example of the use of the UBUS Expert Mode.

Figure 3-1: dialogue t b




The dialogue shows graphically all the highways and their corresponding time slots and monitors the connection points. s

HW is the generic number of the UBUS

NE, e.g. the even numbered (signalling) high-

UBUS struc-

UBUS highways, refer to FOX515 Technical Description.

Timeslots [1 … 31] Usage corresponds to the 31 timeslots of the UBUS highways. The timeslots repre-sent a string of 31 characters "=" and/or "+". The UCST represents - free TSs with "=" - configured TSs with "+".

Connection Point <k> specifies the parameters of the con-nection point <k> on the highway. The UCST adds columns to the list as re-quired up to the maximum of 31 col-umns for the 31 TS on each highway.

For each connection point, the UCST provides in the Connection Point <k> col-umn a sequence of parameters (e.g. for the connection point 2 of the highway 7: MEGIF <9> Traffic-1 T12 1 user) as follows:

<Unit Name> Short name of the unit.

<Slot Number> Number of the slot in the subrack where the unit is configured.

<Subunit Name> The UCST name of the subunit.

<"user label"> Optional "User label" assigned the SbU in the Unit Configuration dia-logue.

e number <k> of the con-i-

he TS on the highway.

<Number of Users> Number of users (cross connections) that share the connection point. Multi-ple users are possible for point-to-multi-point unidirectional cross con-nections. The standard value (bi-directional connections) is 1 user.

The dialogue provides information afollows:

highway. The UCST reduces the rep-resentation of the highways not con-figurable with the selected

ways for the FOX 515/512.

For information on the ture of each NE and the access of units to the

<Number of the Time Slot> Number of the time slot in the framed signal. Thnection point is not necessarily identcal with the number of t

Bus Usage User Guide TDM System & Cross Connections (R8)


Please note that:

The 0 User identifies connection points on the UBUS without an

ns

Figure 3-2: Bus Assignment sample dialogue

active cross connection.

The Connection Points are numbered according to ascending timeslots. This can shift the logical connection points with respect to the number <k> when you add new connection points.

If you scroll the window cursor to the right, the dialogue shows the four columcreated with the example of the use of the UBUS Expert Mode:

UBUS Tab

Press [Close] to quit or

select the tab [PBUS] to monitor the PBUS usage (not for the FOX- U/E and -U).


page 55 of 57 1KHW002001

PBUS assignment

This tab is not available for the FOX- U/E and -U.

The dialogue under the terms of PHA ( S Hi hw nd active connections per line access.

age of the PBUS capacity and to cal-S.

critical with respect to new tra

PBUS tab monitors the usage of the PBUS capacity in PBU g ay Access) a

The dialogue allows you to control the usculate the remaining capacity on the PBU

The monitoring of the assignment on the PBUS becomes important if the re-maining capacity on the PBUS becomes ffic units

.

Figure 3-3: Bus Assignment sampleTab PBUS

to connect

dialogue

T e ia g ows graphically all physh d lo ue sh ical PBUS lines and monitors the bus access and u

Line line. One PBUS line represents a ca-

he l unit:

- COBUQ : 8 - COBUL: 32 - COBUX: 32 or 10 - COBUV: 32 or 10

For information on the PBUS structure and the access of units to the PBUS,

sage. The dialogue provides information as follows:

is the generic number of the PBUS

pacity of 4 x 2 Mbit/s (plus the corre-sponding signalling). The number of available PBUS lines depends on tcontro

ABB

Bus Usage User Guide TDM System & Cross Connections (R8)


refer to FOX515 Technical Descrip-tion.

Unit specifies the unit and the slot number of the unit (<X>).

PHA (PBUS Highway Access) specifies the locally (unit level) active 2 Mbit/s ac-cesses to the PBUS. The access is always a set of 4 x 2 Mbit/s. The sets are identified per unit as follows: 1 ... 4, 5 … 8, 9 … 12, etc..

For information on the PBUS structure and the access of units to the PBUS, refer to FOX515 Technical Descrip-tion.

Line Access specifies the number of traffic signals that the corresponding PBUS access connects.

Special Info(rmation)s provides additional information on the local PBUS access.

Please note that:

Only units with active cross connections appear in this list.

The Line Access is a counter, which is incremented each time the corresponding PBUS access connects a new traffic signal. The count corresponds to the lines in the Cross Connections dialogue. The count is independent of the capacity of the connected traffic signal:

- 1 for a 64 kbit/s traffic signal - 1 for a 30 x 64 kbit/s traffic signal

Examples: - SYNAC <5> (1 … 4): 32 = 2 x (30 x 64 kbit/s) + 30 x 64 kbit/s – LOMIF <8> (1 … 4): 31 = 1 x (30 x 64 kbit/s) + 30 x 64 kbit/s – LOMIF <8> (5 … 8): 1 = 1 x (30 x 64 kbit/s)

You can use this information to identify line accesses with few ac-tive traffic signal connections to free the corresponding PBUS line for other traffic units.

The figure PHAU (PBUS Highway Access per Unit) provided with each PBUS and some of the SBUS units give the maximum num-ber of PHA configurable for the corresponding unit. The PHAU value is always a multiple of four.

For more information please contact: ABB Switzerland Ltd Power Systems Utility Communications Bruggerstrasse 72 5400 Baden Switzerland Phone: +41 58 589 37 35 or: +41 844 845 845 (Call Center) Fax: +41 58 585 16 82 E-Mail: [email protected] H www.abb.com/utilitycommunications

Documents

Abb Fox Tdm System r8 Rd 1khw002001