Transmission and Multiplexing (TM); Synchronous cross connect equipment; 64 kbit/s and n x 64 kbit/s cross connection rate 2 048 kbit/s access ports; Part 2: Management aspects

Draft ETS 300 010-2 covering management ascpects of 64 kbit/s DXCs

Prenos in multipleksiranje (TM) – Oprema za sinhrono prespajanje za 64 kbit/s in n x 64 kbit/s za dostopovne porte s hitrostjo prespajanja 2 048 kbit/s – 2. del: Vidiki upravljanja

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
SIST ETS 300 010-2 E1:2003
English language
68 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST ETS 300 010-2 E1:2003
01-december-2003

Prenos in multipleksiranje (TM) – Oprema za sinhrono prespajanje za 64 kbit/s in n

x 64 kbit/s za dostopovne porte s hitrostjo prespajanja 2 048 kbit/s – 2. del: Vidiki

upravljanja

Transmission and Multiplexing (TM); Synchronous cross connect equipment; 64 kbit/s

and n x 64 kbit/s cross connection rate 2 048 kbit/s access ports; Part 2: Management

aspects
Ta slovenski standard je istoveten z: ETS 300 010-2 Edition 1
ICS:
33.040.20 Prenosni sistem Transmission systems
SIST ETS 300 010-2 E1:2003 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST ETS 300 010-2 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 010-2 E1:2003
EUROPEAN ETS 300 010-2
TELECOMMUNICATION March 1997
STANDARD
Source: ETSI TC-TM Reference: DE/TM-01014-3
ICS: 33.020
Key words: Cross connect, digital, management, transmission, SDH, leased line
Transmission and Multiplexing (TM);
Synchronous cross connection equipment
64 kbit/s and n x 64 kbit/s
cross connection rate 2 048 kbit/s access ports;
Part 2: Management aspects
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16

Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the

foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1997. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 010-2 E1:2003
Page 2
ETS 300 010-2: March 1997

Whilst every care has been taken in the preparation and publication of this document, errors in content,

typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to

"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------
SIST ETS 300 010-2 E1:2003
Page 3
ETS 300 010-2: March 1997
Contents

Foreword .......................................................................................................................................................5

1 Scope ..................................................................................................................................................7

2 Normative references..........................................................................................................................7

3 Abbreviations.......................................................................................................................................8

4 DXC management network...............................................................................................................10

5 Information model .............................................................................................................................10

6 Management interfaces.....................................................................................................................11

7 Applications functions........................................................................................................................11

7.1 Fault management.............................................................................................................11

7.1.1 Alarm surveillance.........................................................................................11

7.1.1.1 Principle...............................................................................11

7.1.1.2 Alarm-related functions........................................................13

7.1.2 Alarm classification........................................................................................14

7.1.2.1 Alarm type............................................................................14

7.1.2.1.1 Communications alarm.........................14
7.1.2.1.2 Equipment alarms.................................14
7.1.2.1.3 Processing alarm..................................15
7.1.2.1.4 Environmental alarm.............................15

7.1.2.2 Perceived severity level .......................................................15

7.1.2.3 Alarm record ........................................................................16

7.1.3 Test functions................................................................................................16

7.1.3.1 Loopbacks ...........................................................................16

7.1.3.1.1 Loopbacks at the 2 048 kbit/s level.......16
7.1.3.1.2 n x 64 kbit/s dropping function..............17
7.1.3.1.3 Internal n x 64 kbit/s loopback ..............18
7.1.3.1.4 Loopback characteristics ......................18
7.1.3.1.5 Internal tests .........................................18

7.2 Performance management ................................................................................................18

7.2.1 Long term performance evaluation ...............................................................19

7.2.2 Short term performance evaluation...............................................................19

7.2.2.1 Elementary events for in-service measurement ..................19
7.2.2.1.1 Anomaly event, receive part .................19
7.2.2.1.2 Anomaly event, transmit part ................20
7.2.2.1.3 Defect events, receive part ...................20
7.2.2.1.4 Defect events, transmit part..................20
7.2.2.2 Elementary events for out-of-service measurement............20

7.2.3 Condition of measurement ............................................................................20

7.2.4 Performance parameters evaluation.............................................................21

7.2.5 Performance process....................................................................................21

7.2.5.1 15 minute process ...............................................................21

7.2.5.1.1 Option 1 - evaluation without
hysteresis..............................................22
7.2.5.1.2 Option 2 - Evaluation with hysteresis....23

7.2.5.2 24 Hour process ..................................................................23

7.2.6 Performance evaluation ................................................................................24

7.2.7 General performance functional diagram......................................................25

7.3 Configuration management ...............................................................................................26

7.3.1 Configuration management overview............................................................26

7.3.1.0 Glossary...............................................................................26

7.3.1.1 Functional architecture ........................................................27

---------------------- Page: 5 ----------------------
SIST ETS 300 010-2 E1:2003
Page 4
ETS 300 010-2: March 1997
7.3.1.1.1 Main functions ...................................... 27
7.3.1.1.2 CAS cross-connection functions .......... 28
7.3.1.1.3 Transfer of unstructured CCITT
Recommendation G.703 / 2 048 kbit/s. 29
7.3.1.1.4 Synchronization function ...................... 30
7.3.1.1.5 Time Slot 0 cross-connection
functions............................................... 30
7.3.1.1.5.1 4 kbit/s granularity ................................ 30
7.3.1.1.5.2 64 kbit/s granularity .............................. 33

7.3.1.2 Object classes..................................................................... 35

7.3.1.3 Entities-relationships diagrams ........................................... 35

7.3.2 Description of the fragments......................................................................... 38

7.3.2.1 Managed element fragment................................................ 39

7.3.2.2 Termination point fragment................................................. 42

7.3.2.3 Cross-connection fragment................................................. 47

7.3.2.4 Synchronization fragment ................................................... 51

7.3.2.5 Power feeding fragment...................................................... 55

7.3.2.6 Time Slot 0 cross-connection.............................................. 56

7.3.2.6.1 4 kbit/s granularity ................................ 56
7.3.2.6.1.1 Termination point fragment .................. 56
7.3.2.6.1.2 Cross-Connection fragment ................. 58
7.3.2.6.2 64 kbit/s granularity .............................. 59
7.3.2.6.2.1 Termination point fragment .................. 59
7.3.2.6.2.2 Cross-Connection fragment ................. 63

Annex A (informative): Management functions ......................................................................................65

A.1 Object classes .................................................................................................................................. 65

A.2 Entities-relationship diagrams........................................................................................................... 65

A.3 Cross-connection fragment .............................................................................................................. 67

A.4 Management fragment ..................................................................................................................... 67

History......................................................................................................................................................... 68

---------------------- Page: 6 ----------------------
SIST ETS 300 010-2 E1:2003
Page 5
ETS 300 010-2: March 1997
Foreword

This European Telecommunication Standard (ETS) has been produced by the Transmission and

Multiplexing (TM) Technical Committee of the European Telecommunications Standards Institute (ETSI).

The ETS is required in order to meet the requirements of network operators and equipment

manufacturers for the deployment and design of synchronous cross connect equipment to be used in

synchronous digital leased line networks.

The corresponding standard for equipment used in cross connection of subrate signals is under

development.
This ETS consists of 2 parts as follows:
Part 1: "Core functions and characteristics";
Part 2: "Management aspects".
Transposition dates
Date of adoption 21 February 1997
Date of latest announcement of this ETS (doa): 30 June 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 December 1997
Date of withdrawal of any conflicting National Standard (dow): 31 December 1997
---------------------- Page: 7 ----------------------
SIST ETS 300 010-2 E1:2003
Page 6
ETS 300 010-2: March 1997
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 010-2 E1:2003
Page 7
ETS 300 010-2: March 1997
1 Scope

This ETS addresses management aspects of the 64 (or n x 64) kbit/s cross connect. The Digital Cross

Connect (DXC) equipment management functions are specified and management network architecture is

described.

Part 1 of this ETS describes requirements of cross connect equipment with 2 048 kbit/s access ports for

use in synchronous digital leased line networks. These requirements are limited to the basic functions,

external characteristics and performance of the equipment.

The part 1 of this ETS (ETS 300 010-1[14]) defines functions and makes precise whether they are

mandatory or not. If supported, a function has to be managed according to part 2 of this ETS. Part 2 of

this ETS specifies when necessary the optional management characteristics (attributes, operations and

notifications) of the objects.
2 Normative references

This ETS incorporates by dated or undated reference, provisions from other publications. These

normative references are cited at the appropriate places in the text and the publications are listed

hereafter. For dated references, subsequent amendments to or revisions of any of these publications

apply to this ETS only when incorporated in it by amendment or revision. For undated references, the

latest edition of the publication referred applies.
[1] CCITT Recommendation G.703: "Physical/electrical characteristics of
hierarchical digital interfaces".
[2] CCITT Recommendation G.704: "Synchronous frame structures used at primary
and secondary hierarchical levels".
[3] ITU-T Recommendation G.826: "Error performance parameters and objectives

for international, constant bit-rate digital paths at or above the primary rate".

[4] ITU-T Recommendation M.20: "Maintenance philosophy for telecommunications
networks".
[5] ITU-T Recommendation M.2100: "Performance limits for bringing into service
and maintenance of international digital paths, sections and transmission
systems".
[6] ITU-T Recommendation M.2110: "Bringing into service international digital
paths, sections and transmission systems".
[7] ITU-T Recommendation M.2120: "Digital path, section and transmission system
fault detection and localization procedures".
[8] ITU-T Recommendation M.3010: "Principles for a telecommunications
management network".
[9] ITU-T Recommendation M.3100: "Generic network information model".
[10] ITU-T Recommendation O.151: "Error performance measuring equipment
operating at the primary rate and above".
[11] CCITT Recommendation X.710: "Common management information service
definition for CCITT applications".
[12] ITU-T Recommendation X.733: "Information technology - Open Systems
Interconnection - Systems Management: Alarm reporting function".
[13] ITU-T Recommendation G.784: "Synchronous digital hierarchy (SDH)
management".
---------------------- Page: 9 ----------------------
SIST ETS 300 010-2 E1:2003
Page 8
ETS 300 010-2: March 1997
[14] ETS 300 010-1 (1995): "Transmission and Multiplexing (TM); Synchronous
cross connect equipment 64 and n x 64 kbit/s cross connection rate 2 048 kbit/s
access ports. Part 1: Core functions and characteristics".
[15] ETS 300 371 (1994): "Transmission and Multiplexing (TM); Plesiochronous
Digital Hierarchy (PDH) information model for the Network Element (NE) view".
[16] ETR 135 (1994): "Transmission and Multiplexing (TM); Network aspects and
applications for a 4 (and n x 4 kbit/s) data link in a 2 048 kbit/s frame".
[17] ETR 241: "Transmission and Multiplexing (TM); Functional architecture of
2 Mbit/s based Plesiochronous Digital Hierarchy (PDH) transport networks".
[18] ITU-T Recommendation X.731: "Information technology - Open Systems
Interconnection - Systems Management: State management function".
[19] ETS 300 304 (1994): "Synchronous Digital Hierarchy (SDH) information model
for the network element (NE) view".

[20] ETS 300 376-1: "Signalling Protocols and Switching (SPS); Q3 interface at the

Access Network (AN) for configuration management of V5 interfaces and
associated user ports".
3 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
2 048S 2 048 kbit/s CCITT Recommendation G.704 [2] framed Signal
2 048U 2 048 kbit/s Unstructured signal
2MB 2 Mbit/s
2ME 2 Mbit/s - External remote
2MI 2 Mbit/s - Internal local
A2, J1, J2, reference points according to ETS 300 010-1 [14]
A-bit bit 3, TS0 FAS
AE Anomaly Event
AIS 2 048 kbit/s Alarm Indication Signal
AISTS16 64 kbit/s Alarm Indication Signal in TS16
BBE Background Block Error
BBER Background Block Error Ratio
BE Block Error
CASXC Channel Associated Signalling Cross Connection Function
CPU Control Processing Unit
CRC4 Cyclic Redundancy Check procedure-4
DE Defect Event
DFC Defect or Failure Condition
DP Degraded Performance
DXC Digital Cross Connect equipment
EB Errored Block
E-bit Remote block error indication
EOC Embedded Operation Channel
ES Errored Second
ESR Errored Second Ratio
EXBER Excessive Bit Error Ratio
F A management interface according to ITU-T Recommendation M.3010 [8]
FAS Frame Alignment Signal
G1, G2, A1, reference points according to ETS 300 010-1 [14]
G1a, G1b, reference points according to ETS 300 010-1 [14]
G'2, A'1, A'2 reference points according to ETS 300 010-1 [14]
G2a, G2b, reference points according to ETS 300 010-1 [14]
H Hour
J'1, J'2, G'1, reference points according to ETS 300 010-1 [14]
LC Local Control interface
LMFA Loss of Multiframe Alignment
---------------------- Page: 10 ----------------------
SIST ETS 300 010-2 E1:2003
Page 9
ETS 300 010-2: March 1997
LOF Loss of Frame
LOS Loss of Signal
LSYNC Loss of Synchronization
m m reference point according to ITU-T Recommendation M.3010 [8]
M Mandatory
MCF Message Communication Function
MD Mediation Device
min Minute
NE Network Element
NEF Network Element Function
NP Normal Performance
O Optional
OS Operations System
OSF Operations System Function
PI Physical Interface
PLPT Plesiochronous Lower order Path Termination
POH Path Overhead
PPT Plesiochronous Path Termination
PRBS Pseudo Random Bit Sequence
Q Management interface to the TMN
Q3 A management interface according to ITU-T Recommendation M.3010 [8]
Qx A management interface between a Q-adaptation function (QAF) and a
Network Element Function (NEF) according to ITU-T Recommendation
M.3010 [8]
RAI Remote Alarm Indication
RMAI Remote Multiframe
RTR1ES Reset Threshold for Errored Second counting
RTR1SES Reset Threshold for Severely Errored Second
s Second
Sa Spare bit in TS0 NFAS
San A spare bit in TS0 NFAS
SDH Synchronous Digital Hierarchy
SER Severely Errored Second ratio
SES Severely Errored Second
T1 Internal timing signal
T4 Output timing signal
TIPI Timing Input Physical Interface
TMN Telecommunication Management Network
TOPI Timing Output Physical Interface
TR1ES Threshold 1 for Errored Second counting
TR1SES Threshold 1 for Severely Errored Second counting
TR2ES Threshold 2 for Errored Second counting
TR2SES Threshold 2 for Severely Errored Second counting
TS Time Slot
TS0 FAS Time Slot 0 with Frame Alignment Signal
TS0 NFAS Time Slot 0 without Frame Alignment Signal
TS16 Time Slot 16
TX/RX Transmit/Receive
UP Unacceptable Performance
UT Unavailable Time
WS Work Station
XC Cross Connect
XCTS Cross Connect Timing Source
NOTE: Abbreviations used in subclause 7.3 are listed in subclause 7.3.1.0.
---------------------- Page: 11 ----------------------
SIST ETS 300 010-2 E1:2003
Page 10
ETS 300 010-2: March 1997
4 DXC management network

Characterization of a Digital Cross Connect (DXC) equipment management network is derived from ITU-T

Recommendation G.784 [13], especially figure 1 of that document. Figure 1 below reproduces a similar

organization for the management view of management network where an Embedded Operation Channel

EOC replaces the specific Synchronous Digital Hierarchy (SDH) Embedded Control Channel (ECC). This

figure relates only to functional aspects and does not imply implementation or routeing facilities. EOC

could be either supported by a particular 64 kbit/s Time Slot (TS) or by one or some of the Sa bits of the

CCITT Recommendation G.704 [2] frame Network Elements (NE) could be directly connected with a

Mediation Device (MD) or via other devices, including NEs.
NOTE: Network operators may be required to provide duplication of the management
interface.
OSF
NETWORK
Q/EOC
VIEW
TMN
FUNCTIONS
SERVICES
Q/EOC Q/EOC
Q/EOC
NEF NEF
QAF
Network
DXC
element
m reference point
DXC
MD Mediation Device
MF Mediation Function
NEF Network Element Function
QAF Q Adapter Function
OS Operations System
OSF Operations System Function
TMN Telecommunications Management Network
Figure 1: Functional view of management network
5 Information model
There is no information model in this edition of the ETS.
---------------------- Page: 12 ----------------------
SIST ETS 300 010-2 E1:2003
Page 11
ETS 300 010-2: March 1997
6 Management interfaces

The DXC shall be able to terminate and generate the cross connect management control channel(s). For

this purpose, the DXC should present, according to ITU-T Recommendation M.3010 [8], the following

interfaces:

Q-interface: This interface provides a management control channel between the Operations System (OS)

and the DXC. Depending on the management network implementation, it could be a Qx or a Q3 interface.

There are no protocol suites in this edition of the ETS.

If this interface is not provided, an interface supporting an m-reference point shall be provided.

F-interface: This optional interface provides Work Station (WS) access to the OS via the DXC.

m-reference point: This is supported by a proprietary interface and allows, via an external Q Adaptation

Function (QAF), a management connection between an OS conforming to TMN recommendations and a

DXC that does not conform to TMN recommendations.

Additionally, the DXC shall provide a Local Control (LC) interface for local attachment of a proprietary

management entity. This interface is concerned with:

- installation and maintenance (with changes of the DXC-configuration), in cases where the

connection to the OS is interrupted or voluntarily blocked;
- local monitoring of the DXC status (without changes of the DXC-configuration).

NOTE: For the first case, means should be implemented in the DXC and/or the OS to

overcome conflict/misalignment situations between the DXC configuration locally
induced via the LC interface and the DXC configuration as it is stored in the OS
database.
7 Applications functions
7.1 Fault management
7.1.1 Alarm surveillance
7.1.1.1 Principle

Alarm surveillance is concerned with the detection and reporting of relevant events/conditions which occur

in the equipment or which are detected at equipment level. Events/conditions detected within the

equipment and in the incoming signals shall be reportable. Alarms are indications that are automatically

generated by the equipment or NE as the result of certain events/conditions and associated processing.

The user shall have the ability to define which events/conditions generate autonomous reports. The

remaining events/conditions are reportable on request.

The relevant events/conditions are derived from the Defect or Failure Conditions (DFC) given in

ETS 300 010-1 [14]. The processing associated with the occurrence of DFC is described in figure 2.

---------------------- Page: 13 ----------------------
SIST ETS 300 010-2 E1:2003
Page 12
ETS 300 010-2: March 1997
Performance
Internal
Defect
Time
notification
Processing
filtering
filtering
Failure
Q/F/m/LC
(Configure)
Notification
Q/F/m/LC
module
(Notifications)
Maintenance
Q/F/m/LC
log
Q/F/m/LC
(Request)

NOTE 1: TMN requires a notification function: this may be supported either by the equipment itself or by

a QAF function.

NOTE 2: The "configure" arrow is shown according to the text of subclause 7.1.1.1. This representation

does not preclude that the filtering module, internal notification module and processing module

are also configurable.
Figure 2: Alarm related maintenance functions

Functions associated with the various functional blocks to figure 2 are as follows:

defect or failure: This functional block performs the elementary functions necessary for the detection of

any of the defect or failure conditions specified in ETS 300 010-1 [14] or in this ETS.

time filtering: This functional block provides optional programmable time filtering, ranging from 0 to 10 s

in steps of 1 s, which allows notification of a selected defect or failure condition only if its duration is

greater than the predetermined value.
Internal notification

filtering: This functional block manages the sending of notifications (occurrence, disappearance of DFC)

to the appropriate functional block. It also enables/disables discrimination of a given DFC depending upon

its nature and if necessary, to forward it to appropriate functional blocks.

processing: This function receives the various notifications, gathers them and performs the necessary

correlation in such a way that no redundant information will be needed. In addition, this function may allow

provision of a diagnostic for the occurrence of a DFC. The processing functional block also generates

synthetic notifications destined for the Equipment Management Function.
---------------------- Page: 14 ----------------------
SIST ETS 300 010-2 E1:2003
Page 13
ETS 300 010-2: March 1997
Notification

module: This functional block is under the control of the user who may determine the notifications

required to be spontaneously transmitted to the Q/F/m interface/reference point. Also included is

programmable notification filtering in the range of 0 s to 60 s in steps of 10 s.

Maintenance

log: This functional block registers all the DFCs occurring in the DXC in an allotted memory area. A

stored DFC should include: nature (i.e. LOS, LFA, etc.), type, managed function, time (occurrence,

clearing). The user shall have the ability to request transmission or display of stored information according

to criteria which are described in subclause 7.1.1.2.
7.1.1.2 Alarm-related functions

The following alarm-related functions may be required to be supported at the equipment level:

- report autonomous alarms;
- request all alarms;
- report all alarms;
- allow/inhibit alarm reporting over any EOC;
- request status of allow/inhibit alarm reporting;
- report status of allow/inhibit alarm reporting.

The following table 1 contains the minimum list of alarm conditions (default values) described in

subclause 7.1.2.
Table 1: Alarm conditions
Alarm type Alarm condition Mandatory/ Perceived
optional severity
level
Communication LOS 2 048U M Major
EXBER O Pending
LOS 2 048S M Critical
LOF M Critical
EXBER O Minor
RAI M Minor
AIS M Minor
LMFA M Minor
RMAI (note) M Minor
AIS TS16 M Minor
Management link failure O Critical
LSYNC M Major
Equipment 2MB Port M Major
Power supply M Critical
Cross Connection function M Critical
Common logic M Major
Special functions M Major
Processing Misalignment database M Major
Time management O Minor
Alarm memory M Minor
Downloading software error O Major
Software corrupting M Major
Quality of service Degraded performance (DP) O Minor
Unacceptable performance (UP) O Major

NOTE: Remote Multiframe Alarm Indication (RMAI): this alarm corresponds to the Remote

Alarm Indication (RAI) in time slot 16.
---------------------- Page: 15 ----------------------
SIST ETS 300 010-2 E1:2003
Page 14
ETS 300 010-2: March 1997
7.1.2 Alarm classification

Alarms should be classified using the alarm type categories and perceived severity defined in ITU-T

Recommendation X.733 [12].
7.1.2.1 Alarm type

Five basic categories of alarms are specified. These are given in the following subclauses.

7.1.2.1.1 Communications alarm

This type of alarm includes the following defect or failure conditions which are shown with the related

functional part of the 64 (or n x 64) kbit/s digital cross connect equipment.
- 2 048 kbit/s unstructured;
- loss of incoming signal;
- excessive error ratio (bipolar coding violations) (see note).

- 2 048 kbit/s structured access port carrying signals with channel associated signalling;

- loss of incoming signal (see subclause 11.1.1.2 of ETS 300 010-1 [14]);
- loss of frame alignment (see subclause 10.1 of ETS 300 010-1 [14]);
- excessive error ratio;

- defect indication from remote end (bit3 and any additional spare bit of Time Slot 0 without

Frame Alignment Signal (TS0 NFAS));
- 2 048 kbit/s Alarm Indication Signal (AIS) received (see subclause 11.1.1.5 of
ETS 300 010-1 [14]);
- loss of multiframe alignment (bit 6 in TS16) (see subclause A.11.1.1.7 of
ETS 300 010-1 [14]);

- defect indication from remote end (see subclause A.11.1.1.9 of ETS 300 010-1 [14]);

- AIS received in TS16 (see subclause A.11.1.1.8 of ETS 300 010-1 [14]).

The notification of each alarm shall be in accordance with the filtering values defined in the

subclause 7.1.1.1.
NOTE: The detection of this alarm is optional.
- Management links.
Alarm indicating failure in management link(s), if appropriate.
- Synchronization interface(s).
Loss of synchronization signal (see subclause 11.2.1.2 of ETS 300 010-1 [14]).
7.1.2.1.2 Equipment alarms
This type of alarm includes at least the following defect or failure conditions:
Failure of a 2 048 kbit/s port

The 2 Mbit/s port (Physical Interface (PI) and Plesiochronous Path Termination (PPT) functions) shall be

provided with an appropriate check procedure to detect at least the following defect/failure conditions on

2 Mbit/s port:
- TX/RX circuits, included the elastic stores;

- loss of internal timing signals from Cross Connect Timing Source (XCTS) function;

- loss of internal power feed;
- internal communication interface with common logic;
- internal interface with cross-connection function.
---------------------- Page: 16 ----------------------
SIST ETS 300 010-2 E1:2003
Page 15
ETS 300 010-2: March 1997
Power failure

This alarm shall be activated either by absence of the external power supply or a fault in the single DXC

power supply unit.
Connection failure

The cross-connection function shall be provided with appropriate check procedures to detect defect/failure

conditions on a 64 or n x 64 kbit/s connection. The DXC control system shall be able to indicate the part or

unit of the DXC that caused the connection failure.
Timing failure

The XCTS function shall be provided with an appropriate check procedure to detect the loss of T1 signal

(and/or T4 signal if required).
Common logic failure
The DXC shall be provided with appropriate check procedure to detect at least:
- defect/failure of the CPUs;
- defect of the program memory;
- defect of the data memory;
- loss of the internal power feeding.
Special function failure

Each different special function implemented in the DXC shall be provided with appropriate check

procedures to detect defect/failure condit
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.