dms-100 mmp spm stm-1 trunking - willow eaton...

297-9051-525

DMS-100 MMP

SPM STM-1 TrunkingService Implementation Guide

ISN04 (TDM) Standard 04.01 April 2002

DMS-100 MMP


Publication number: 297-9051-525Product release: ISN04 (TDM)Document release: Standard 04.01Date: April 2002

Copyright © 2002 Nortel Networks,All Rights Reserved

United Kingdom

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and isstrictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information containedherein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, inwhole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its ownconfidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, theholder is granted no rights to use the information contained herein.

This product complies with the provisions of the Electromagnetic Compatibility (EMC) Directive (89/336/EEC), the AmendingDirective (92/31/EEC), the Low Voltage Directive (73/23/EEC), the CE Marking Directive (93/68/EEC) and the TelecommunicationsTerminal Equipment Directive (91/263/EEC) [where the product may be deployed as a private apparatus connected to the PublicTelephone Network], and as such this product bears the CE marking in accordance with the applicable Directives.

This product is intended for deployment in a light industrial, non-domestic environment, and complies with the relevant EMCstandards for emissions and immunity. Because this is a Class A product, in a domestic environment this product may cause radiointerference. In this case, the user may be required to take adequate measures.

Changes or modification to SPM STM-1 Trunking without the express consent of Nortel Networks may void its warranty and voidthe user’s authority to operate the equipment.

NORTEL NETWORKS, the NORTEL NETWORKS logo, the GLOBEMARK, “HOW THE WORLD SHARES IDEAS, UNIFIEDNETWORKS, DMS, MAP, NORTEL, NORTHERN TELECOM, NT, and SUPERNODE are trademarks of Nortel Networks.

DMS-100 SPM STM-1 Trunking Service Implementation Guide ISN04 (TDM) and up

iii

Publication history

April 2002ISN04 (TDM) and up Issue 04.01 - Standard issued version for ISN04 (TDM)

October 2001MMP16 and up Issue 03.02 - Draft (internal use only)

April 2001MMP15 and up Issue 03.01 - Standard issued version for MMP15

April 2001MMP15 and up Issue 02.03 Final draft

March 2001MMP15 and up Issue 02.02 Second draft

October 2000MMP14 and up Issue 02.01 First draft (internal use only)

March 2000MMP13 and up Issue 01.03 Fourth draft

February 2000MMP13 and up Issue 01.02 Third draft

November 1999MMP13 and up Issue 01.01 Second draft

August 1999MMP12 and up Issue 00.01 First draft

DMS-100 MMP SPM STM-1 Trunking Service Implementation Guide ISN04 (TDM) and up

v

Contents

Service Implementation Guide

Publication history iii

About this document xiStructure of this document xiChanges at ISN04 (TDM) xiiChanges at MMP14 and MMP15 xiiiRelated publications xiiiHow to check the version and issue of this document xivWhat precautionary messages mean xivHow commands, parameters, and responses are represented xv

Input prompt (>) xvCommands and fixed parameters xvVariables xviResponses xvi

Part I Introduction I-1

1 Product overview 1-1Ordering information 1-1

PEC codes 1-1Software optionality control 1-1

Background 1-1What is Spectrum? 1-1What is an SPM? 1-2

Scope of the SPM system in MMP releases 1-2SPM environment 1-2

SPM in the network 1-2Network synchronization 1-2SPM in the DMS-100 architecture 1-3SPM interface to the DMS-100 MMP switch 1-4

Product features 1-5Benefits 1-5

Reduction in central office physical plant 1-5

vi Contents

297-9051-597 Draft 04.01 April 2002

Simplified switching/transmission boundary 1-6Integrated echo cancellation 1-7Integrated tone detection and tone generation 1-7Use of existing OAM&P 1-7

2 Development summary 2-1Functionality deliverables 2-1

ISN04 (TDM) 2-1MMP15 2-8

Hardware development 2-10Product structure 2-10Dependencies 2-11

Software development 2-12

Part II Functional description II-1

3 Functional overview 3-1STM-1 interface 3-1

Protection switching 3-3Automatic SYSB recovery process 3-5Synchronization 3-5

ISUP protocol 3-6Trunk signaling 3-6Call processing services 3-8Interworking 3-8

IUP (formerly BTUP) protocol 3-8Trunk signaling 3-8Call processing services 3-8Interworking 3-9

Echo cancellation 3-9Tones 3-10

Tone detection 3-10Tone generation 3-10

Continuity testing 3-11Intelligent Networks 3-11OAM&P 3-11

MAP interface enhancements 3-13STM-1 RM command descriptions 3-17

Carrier maintenance 3-18Guidelines for VC12 carrier datafill 3-19Alarms 3-20Performance Monitoring parameters 3-20Performance Monitoring archival 3-20MAPCI 3-21Idle bit pattern 3-21

Companding and bit inversion 3-22Error handling 3-23

Device logs 3-23Carrier maintenance logs 3-23Network Protection 3-24

Contents vii

297-9051-597 Draft 04.01 April 2002

Digital Test Access 3-24ETSI PRI 3-25

4 Limitations and restrictions 4-1Operational limitations 4-1Table size 4-2

Part III Interactions III-1

5 Feature interactions 5-1

Part IV Planning and engineering IV-1

6 Planning for installation 6-1Planning 6-1Installation 6-1

7 Hardware requirements 7-1Features 7-1

Unsupported features 7-2SDH multiplexing and mapping 7-2

Functions 7-2

8 Software description 8-1Software architecture 8-1

9 Capacity and Performance Engineering 9-1Collection of performance data 9-1Call types and timings 9-1SPM recovery timings 9-1RTS Timings 9-1Processor real time allocations 9-1Trunk provisioning rules 9-2C-side connectivity 9-2

Calculating DSP and VSP RM requirements 9-3Other performance variables 9-6

10 Signaling requirements 10-1CCS7 signaling 10-1

Specconn 10-1Monitoring CCS7 links 10-2

CCS7 MTP routing 10-2Associated and quasi-associated signaling 10-2Digit processing 10-2

11 Capacity information 11-1

viii Contents

297-9051-597 Draft 04.01 April 2002

Part V Provisioning V-1

12 Provisioning overview 12-1Base STM-1 trunking system 12-1Echo canceller provisioning 12-4Datafill 12-6

13 Data schema 13-1Table MNHSCARR 13-1Table MNPRTGRP 13-1

14 Service order procedures 14-1

15 Datafill procedures 15-1

16 Translations and routing 16-1

Part VI Billing VI-1

17 Billing structures and modules 17-1

Part VII OA&M VII-1

18 Translation verification tool 18-1

19 CI commands 19-1SPM screen 19-3

SPM commands (SPMDIR directory) 19-4CEM commands (SPMCEMDIR directory) 19-4DSP commands (SPMDSPDIR directory) 19-5STM-1 commands 19-5VSP commands (SPMVSP directory) 19-6

Carrier commands (CARRIER directory) 19-6Carrier maintenance commands (CARRUTIL directory) 19-7Trunk maintenance commands (SPMTKCNV directory) 19-8

20 Operational measurements 20-1

21 Administrative log reports 21-1

22 Maintenance 22-1

Part VIII Requirements VIII-1

Contents ix

297-9051-597 Draft 04.01 April 2002

23 Product support 23-1Recovery 23-1Support 23-1Training 23-1

Course objectives 23-1Overview 23-2Prerequisites 23-3

Documentation 23-3

24 Customer acceptance 24-1Acceptance 24-1

Part IX Reference information IX-1

List of terms T-1

References R-1

x Contents

297-9051-597 Draft 04.01 April 2002


xi

About this document

This document describes the functionality of the SPM STM-1 trunkingapplication provided by Nortel Networks for the DMS-100 MMP market(referred to throughout as the SPM system).

The Spectrum Peripheral Module (SPM) is a multi-application platform for theDMS SuperNode. The SPM architecture consists of the following modules:

• Common Equipment Module (CEM)

Contains the functions needed to control the operations of the SPM.

• Digital Signal Processor Resource Module (DSP RM)

Provides voice processing and compression services for the SPM.

• Voice Signal Processor Resource Module (VSP RM)

Provides echo cancellation for the SPM.

• STM-1 Resource Module (STM-1 RM)

Provides an STM-1 interface.

The document contains procedures for engineering, provisioning, andmaintaining the SPM system.

Structure of this documentThe document is divided into the following parts:

Part I: Introduction - This part provides an overview of the SPM system.

Part II: Functional description - This part provides a functional overview ofthe SPM system, describing its operation, limitations, and restrictions.

Part III: Interactions - This part describes the interactions between the SPMsystem and other functionalities.

Part IV: Planning and engineering - This part describes the hardware,software and signaling requirements for the SPM system. It contains the

xii About this document

297-9051-525 Standard 04.01 April 2002

information necessary for planning the integration of the SPM system with theswitches in a network.

Part V: Provisioning - This part contains the procedures for setting up theSPM system in the offices of a customer network.

Part VI: Billing - This part describes the effect of the SPM system on theDMS-100 MMP billing systems.

Part VII: Operation, administration, and maintenance - This partdescribes the CI commands, operational measurements and log reports that aresupported by the SPM system in the MMP14 release.

Part VIII: Requirements and support - This part describes NortelNetworks’ product support arrangements.

Part IX: Reference information - This part contains definitions of technicalterms, a list of references and an index.

Changes at ISN04 (TDM)The ISN04 (TDM) product release includes changes made at MMP16. Thenumbers in brackets represent the feature number associated with thefunctionality change.

The following feature functionality changes were included in the ISN04(TDM) release:

• STM-1 France VN4 / VN6 (59027083)

• STM-1 K1 / K2 Byte Support (59033790)

• STM-1 Turkish ISUP V2 (59034789)

• STM-1 Israel ISUP (59034796)

• STM-1 French ISUP - SPIROU (59034822)

The following feature functionality changes were included in the MMP16release:

• SPECCONN Completion (59022028)

• Australia Interconnect ISUP (59017730)

• Australia Backbone ISUP (59017697)

• France SSUTR2 (59027160)

• STM-1 ETSI PRI (59026237)

• STM-1 PRI - AOC and Metering (59026347)

About this document xiii


• STM-1 PRI Digital Test Access (59028292)

• SPM Hardcoded Tones - Australia, Switzerland, Mexico, Portugal, NewZealand, Ireland (59028988)

Changes at MMP14 and MMP15The following feature functionality changes and chapter audit were includedin the MMP15 release:

• IUP and ECAN Enhancements (59016306)

• STM-1 Italian and Spanish tones (59018949)

• STM-1 Brazilian tones (59018854)

• ETSI-ISUP variant on SPM (Italian ISUP) (59014220)

• ETSI-ISUP variant on SPM (Belgium ISUP) (59017760)

• ETSI-ISUP variant on SPM (Spanish ISUP) (59017644)

• STM-1 Brazil ISUP (59017595)

• STM-1 German Network Protection (59019615 & 59025550)

• KLM numbering (59017369)

• STM-1 SPM Carrier Maintenance (59008275)

• STM-1 Digital Test Access (59008275)

• Contents audit

To ensure that there is not a conflict between the information in thisdocument and that same information in the NTP documents, only changesare highlighted in this document but a cross-reference added to the one setof detailed information. This allows most of Chapter 15 and Chapter 21 tobe deleted.

Chapters 13, 15, 19 and 21 (Data Schema, Datafill Procedures, CICommands, and Administrative Log Reports respectively) briefly listchanges to their data and supply a cross-reference to details of that data.

• Chapter audit

Each chapter is audited by a Nortel specialist.

Related publicationsMore information about SPM can be obtained from the following publications:

• DMS-Spectrum Peripheral Module General Description, 297-1771-130

• DMS-Spectrum Peripheral Module Feature Description ReferenceManual, 297-1771-330

• DMS-Spectrum Peripheral Module Commands Reference Manual,297-1771-819

xiv About this document

297-9051-525 Standard 04.01 April 2002

• DMS-SPM Hardware Maintenance Reference Manual, 297-1771-550

• DMS-100 MMP Customer Data Schema Reference Manual, 297-9051-351

• DMS-100 International Spectrum Peripheral Module Release Document,297-1771-597

• MMP Translations Guide, 297-1771-350

• Other SPM information can be obtained from the References section.

How to check the version and issue of this documentThe version and issue of the document are indicated by numbers, for example,01.01.

The first two digits indicate the version. The version number increases eachtime the document is updated to support a new software release. For example,the first release of a document is 01.01. In the following software release cycle,the first release of the same document would be 02.01.

The second two digits indicate the issue. The issue number increases each timethe document is revised but re-released in the same software release cycle. Forexample, the second release of a document in the same software release cycleis 01.02.

To determine which version of this document applies to the software in youroffice and how documentation for your product is organized, check the releaseinformation in the DMS-100 MMP Product Documentation Directory,297-9051-001.

What precautionary messages meanThe types of precautionary messages used in Nortel documents includeattention boxes and danger, warning, and caution messages.

An attention box identifies information that is necessary for the properperformance of a procedure or task or the correct interpretation of informationor data. Danger, Warning, and Caution messages indicate possible risks.

Examples of precautionary message types follow:

ATTENTION Information needed to perform a task

ATTENTIONThe system requires a restart to activate the changes described in thisprocedure.

About this document xv


DANGER Possibility of personal injury

WARNING Possibility of equipment damage

CAUTION Possibility of service interruption or degradation

How commands, parameters, and responses are representedCommands, parameters, and responses in this document conform to thefollowing conventions.

Input prompt (>)An input prompt (>) indicates that the information that follows is a command:

>BSY

Commands and fixed parametersCommands and fixed parameters that are entered at a MAP terminal are shownin uppercase letters:

DANGERRisk of electrocutionDo not open the front panel of the inverter unless fuses F1,F2, and F3 have been removed. The inverter containshigh-voltage line. Until the fuses are removed, thehigh-voltage lines are active, and you risk being electro-cuted.

WARNINGDamage to the backplane connector pinsAlign the card before seating it, to avoid bending the back-plane connector pins. Use light thumb pressure to align thecard with the connectors. Next, use the levers on the cardto seat the card into the connectors.

CAUTIONPossible loss of serviceBefore continuing, confirm that you are removing the cardfrom the inactive unit of the peripheral module. Subscriberservice will be lost if you remove a card from the activeunit.

xvi About this document

297-9051-525 Standard 04.01 April 2002

>BSY CTRL

VariablesVariables are shown in lowercase letters:

>BSY CTRL

ctrl no

The letters or numbers that the variable represents must be entered. Eachvariable is explained in a list that follows the command string.

ResponsesResponses correspond to the MAP display and are shown in a different type:

FP 3 Busy CTRL 0: Command request has been submitted.FP 3 Busy CTRL 0: Command passed.

The following excerpt from a procedure shows the command syntax used inthis document:

Procedure 1 Busy CTRL

At the MAP terminal

1 To manually busy the CTRL on the inactive plane, type

>BSY CTRL

ctrl_no

and press the Enter key

where

ctrl_no is the number of the CTRL (0 or 1)

Example of a MAP response:FP 3 Busy CTRL 0: Command request has been submitted.FP 3 Busy CTRL 0: Command passed.


I-1

Part IIntroduction

This part contains the following chapters:

• Product overview (Chapter 1)

• Development summary (Chapter 2)

Par

tI

Intr

od

uct

ion


1-1

1 Product overview

This chapter outlines the Spectrum Peripheral Module (SPM) product asimplemented on the DMS-100 MMP switch for the ISN04 (TDM)softwarerelease.

Ordering informationPEC codes

The PEC code for the Spectrum base frame assembly is NTLX91BA. TheNTLX91BA frame can support two Spectrum Peripheral Modules.

The PEC code for the STM-1 Resource Module is NTLX99BA (opticalinterface).

Software optionality controlThe SPM is optional equipment. The relevant order codes are:

• STM00001 - Basic Software

• STM00003 - STM Network PRI

• STM00004 - ISUP and TUP protocols

• STM00010 - Optional Echo Cancellation

BackgroundWhat is Spectrum?

Spectrum is a multi-application high-speed technology platform that providesa flexible, cost-effective and reliable architecture for future applicationdevelopment. Its hardware and software architecture allow it to interface easilywith a wide variety of network traffic, and to perform signal-processingfunctions as well as handling routine call processing in conjunction with theDMS switch.

1-2 Product overview

297-9051-525 Standard 04.01 April 2002

What is an SPM?The first application of Spectrum technology in the international market is anSPM providing a 1+1 redundant STM-1 trunking interface for the DMS-100MMP switch.

Note: Throughout this document, the Spectrum application ‘SPM STM-1trunking for the DMS-100 MMP switch’ is referred to as the SPM system.

Scope of the SPM system in MMP releasesThe SPM features and functionality described in this document areimplemented in the ISN04 (TDM) release. The source material used toproduce this document contains ISN04 (TDM) information. Some chaptersonly highlight changes between previous MMP versions. References to theNTP documents, where detailed information is given, are added wherenecessary.

SPM environmentSPM in the network

The SPM serves as a high-capacity feeder into the DMS-100 MMP switch,as shown in Figure 1-1.

Figure 1-1 SPM position in the network

The SPM system directly terminates an STM-1 carrier and feeds the individualDS0 traffic via DS512 from the carrier into the DMS-100 MMP switch. Thisconfiguration does not require external multiplexers to bring the carrier downto an E1 level, as is the case with PCM-30 Digital Trunk Controller (PDTC)trunk modules.

Network synchronizationThe SPM system achieves SDH (Synchronous Digital Hierarchy)synchronization standards by loop timing to the SDH equipment to which it

DXC

DDF

DMS-100 MMP

SPM

Optical

to SDH ring

switch matrix(ENET) interface

(up to 1953S512

STM1

STM1

STM1

DS512

DS0s permodule

Product overview 1-3


is connected, for example, a digital cross-connect (DXC). This means that tomaintain SDH synchronization standards, the SPM must always beconnected to equipment capable of providing an SDH quality clock (DXC orequivalent).

Back-to-back connection of two SPMs via STM-1 is a supportedconfiguration.

Note: All the clocking (message switch, SPMs, DXCs and so on) must bederived from the same source.

SPM in the DMS-100 architectureFigure 1-2 shows the position of both the new SPM and an existing PDTCwithin the DMS-100 MMP architecture.

Figure 1-2 SPM position within the DMS-100 MMP SuperNode

In the DMS-100 MMP architecture, the SPM occupies a similar position to theexisting PDTC peripheral. However, instead of terminating E1 carriers, theSPM terminates a single STM-1 optical carrier, with four times as many trunksas a single PDTC. The SPM can also perform echo cancellation withoutexternal equipment on its terminating trunks.

CMIOC

PDTC

LPP

SPM

DMS-BUS message switch

E1 trunks

STM-1 trunks

Voice /Data Public Network

DMS-100 MMP

ENET

SPM


297-9051-525 Standard 04.01 April 2002

SPM interface to the DMS-100 MMP switchFigure 1-3 shows a high-level view of the internal signal routing within theSPM system.

Figure 1-3 SPM interface connections

The SPM system provides a redundant 1+1 STM-1 optical interface directly tothe DMS-100 MMP switch. This interface supports asynchronous VC12mapping.

The incoming STM-1 TDM signal is broken into its composite DS0 time slotsfor routing to the internal 12K port timeswitch within the Common EquipmentModule (CEM). The DS0 time slots can be used in the following ways:

• routed to any of the other resource modules on the SPM shelf for bit-streamprocessing

• sent directly to the ENET for call processing routing through the DS512host links provided by the CEM card

The DS512 links provide a full 2048 channels of bandwidth to the EnhancedNETwork (ENET), and allow for a full STM-1 payload (1953 channels) plusmessaging between the SPM and the CM without a bandwidth bottleneck.

DMS-100SPM System

DS512interface

DSP-based Resource ModulesTone Receivers and

Echo Cancellers

12KDS0switch

STM-1Asynchronous

interface

STM-1TDM

1953channels

ENET

CM

DS512

2048channels

26 RM slots

CEM

Ext.Ntwk. MS



Product featuresThe SPM system has the following characteristics as an STM-1 trunkingperipheral:

• coexists and interworks with DTCO and DTCOi

• supports ISUP and IUP (formerly BTUP) call processing in the DMS-100MMP environment

• supports integrated echo cancellation with redundancy features

• supports an open interface to allow integrated echo canceller modulesdeveloped by licensed third parties

• supports current requirements for tone reception and COT testing

• supports ESTR capability for IN and other re-origination functionality

BenefitsThe SPM system provides the following physical and operational benefits:

• reduction in central office physical plant

• reduced power consumption

• simplified switching/transmission boundary

• (optional) integrated echo cancellation

• integrated tone detection and tone generation

• use of existing OAM&P

The following paragraphs give details of these benefits.

Reduction in central office physical plantFigure 1-4 shows how the SPM system achieves floorspace savings byproviding an STM-1 trunk interface directly to the DMS-100E switch.


297-9051-525 Standard 04.01 April 2002

Figure 1-4 Captive office equipment replaced by the SPM

A single SPM ANSI-sized frame supports two fully redundant STM-1 trunks(3906 DS0 payload trunking channels). This is the equivalent of 3.94 digitaltrunk controller (DTC) frames (3906/992). The SPM system also eliminates orsignificantly reduces the space required for MUX and external echo cancellers.This reduces the size of the wire centre and eliminates some cable congestion.

An accurate view of the achievable physical benefits requires detailed analysison a per office basis. However, a guideline average figure is a five timesreduction in the peripheral footprint (one SPM, instead of four DTCO framesand an E1/STM-1 MUX frame). This would also lead to a five times reductionin the power consumption for peripheral equipment.

Note: This power saving was evaluated in a comparative study of DTCOpower measurements and SPM data. Nortel Networks Systems Engineeringconfirms the SPM model used as typical for UK customers: non-ECAN and2+1 DSP per SPM.

Simplified switching/transmission boundaryThe SPM system simplifies the network and switch interface. It also providesthe operating company with cost-of-ownership benefits over existing solutions

DS0

PCM30

PCM30

STM1

DDF

TN-4Xe

STM1

STM4

Switch

Matrix

Switch

Matrix

XPM TN-1X

0

0

0

0

SPM TN-4Xe

DS0

STM1

ODF

STM1

STM4

STM-X

STM-X

DDF



through the reduction of transmission equipment, and the elimination ofcopper interfaces and external echo cancellation equipment.

Note: Although the SPM significantly reduces equipment in the wirecentre, it is not intended that the SPM incorporates all transmissionfunctions. The SPM should be viewed as a simplified interface between theDMS switch and SDH, incorporating some of the functional advantages ofSDH equipment.

Integrated echo cancellationThe SPM system provides an optional echo cancellation facility, usingintegrated resource modules called Voice Signal Processors (VSP). The VSPsare plug-in modules and can be provisioned for 100% port coverage or pooledcoverage (where only a percentage of the total number of speech time slots canuse echo cancellation at one time). If less than 100% of the traffic requiresecho cancellation, the SPM requires fewer VSP modules, thus providing amore economical deployment of the echo cancellation function.

Nortel Networks also provides an interface specification to enable licensedthird-party echo canceller vendors to design and supply integrated echocancellers for the SPM system. These units will be fully compatible with allSPM physical, logical, and software support systems.

Integrated tone detection and tone generationThe SPM system provides integrated tone detection and tone generation usingthe Digital Signal Processor Resource Module (DSP RM). The DSP RM is aplug-in module and can be provisioned for 100% trunk coverage or pooledcoverage. Its functionality is equivalent to the Special Tone Receiver (STR)and Universal Tone Receiver (UTR) used in the XPM peripherals. It can alsobe used for both short and long duration tone detection.

Use of existing OAM&PBecause the SPM system is an integral subsystem of the DMS-100 MMPswitch, it uses the existing switch-based operations, administration,maintenance and provisioning (OAM&P) facilities, via the Maintenance andAdministration Position (MAP). This method of network managementrequires minimal retraining of operating company personnel.


297-9051-525 Standard 04.01 April 2002


2-1

2 Development summary

This chapter outlines the hardware and software development for the SPMSTM-1 trunking application.

Functionality deliverablesThe ISN04 (TDM) product release includes changes made at MMP16. Thenumbers in brackets represent the feature number associated with thefunctionality change.

ISN04 (TDM)At ISN04 (TDM), SPM supports the following STM-1 functionality:


— Protocol description

This feature enables Multiplex Section Protection (MSP) switching ofa signal. MSP is a mechanism that protects a number of VC-4 servicesby using an additional hardware and fiber installation. MSP provides acapability such that, in the event of the failure of the Working sectionof an STM-1 resource module, the signal may be made available viathe Protection section.

For STM-1 carriers on a Spectrum Peripheral Module (SPM), thisfeature provides the following modes of switching:

– 1+1 unidirectional protection (revertive mode)

– 1+1 bidirectional protection - compatible with 1:n (revertive mode)

– 1+1 bidirectional protection - compatible with 1:n (non-revertivemode)

– 1+1 bidirectional protection - optimized for 1+1 network

For unidirectional switching, the switching is independent of theremote node operation and switching is complete when the traffic

2-2 Development summary

297-9051-525 Standard 04.01 April 2002

in the failed direction of the local node is switched to the othersection irrespective of whether the remote end has switched or not.

Note: Unidirectional protocol was supported prior to thisfeature being implemented.

Bidirectional switching requires the MSP functions at both ends of theMSP link to be able to communicate with each other and thereby toco-ordinate the switch. This feature provides the necessarybit-orientated protocol, using the K1 and K2 bytes, to perform thisactivity. If one node is configured for unidirectional switching and theother node is configured for bidirectional switching, the node withbidirectional switching will never switch, as the MSP protocol will fail.

In revertive mode: if an MSP switch occurs, the traffic is switched fromthe Working Section to the Protection Section. When the WorkingSection has been repaired, the traffic will automatically revert back tothe Working Section.

— Interface

The operator has the ability to select one of the above modes ofswitching by changing data schema table configuration. This featureallows the STM1 interface of the SPM to be interconnected with anyother vendor's equipment following ITU-T G.841.

This feature introduces the following new commands:

– Lockout

– If applied to optimized protocols, it freezes the position of thesection selector.

– If applied to non-optimized protocols, it prevents switching tothe Protection section.

– Exercise

This command provides the ability to test the bidirectional mode -it only applies when there is no failure.

– Clear

This command clears all other switching commands.

This feature provides eight new alarms for monitoring the system.MSP alarms are raised to indicate a restraint, on the Multiplex

Development summary 2-3


Protection section mechanism, to recover from faults occurring onSTM1M carriers. The alarms will be raised either for a:

– User action (the issue of a lockout, force or manual command), or

– Fault in communication with the distant equipment (that is, adifferent configuration at each end of the link or a fault occurringduring sparing).

• STM-1 France VN4 / VN6 (59027083)

This feature provides support of VN4 and VN6 PRI trunks on the STM-1interface of the Spectrum Peripheral Module (SPM). Functionality isequivalent to that provided on the PCM-30 Digital Trunk Controller(PDTC) for network mode on the DMS-100E. The functionality is definedin NIS A215-1, ETSI PRI (T) Specification, DMS-MMP Implementation ofETSI ISDN Primary Rate Interface at the T Reference Point; 21 January2000.

All VN4 and VN6 supplementary services are supported on the STM-1interface on the SPM by activities: 59026237 and 59026347.


This feature adds the Turkish ISUP V1 and Turkish ISUP V2 protocols tothe Spectrum Peripheral Module (SPM) STM-1 interface, therebyallowing network operators to connect to the Turkish Telecom networkusing a direct STM-1 interface. It introduces functionality to enable theDMS-100 MMP switch to support the Turkish protocol variants TurkishISUP V1 and Turkish ISUP V2 using the SPM STM-1 peripheral. TurkishISUP V1 and Turkish ISUP V2 are variants of the ETSI ISUP V1 and ETSIISUP V2 protocols. Functionality is equivalent to that provided on thePCM-30 Digital Trunk Controller (PDTC) for network mode.

The architecture in the SPM is the same as in XPM (Extended PeripheralModule).


This feature adds the Israel Civilian ISUP V2 and Israel Defense ISUP V2protocols to the Spectrum Peripheral Module (SPM) STM-1 interface,thereby allowing network operators to connect to the Israeli Telecomnetwork using a direct STM-1 interface. It introduces functionality toenable the DMS-100 MMP switch to support the Israeli protocol variantsIsrael Civilian ISUP V2 and Israel Defense ISUP V2 using the SPMSTM-1 peripheral. Israel Civilian ISUP V2 and Israel Defense ISUP V2are variants of the ETSI ISUP V2 protocol. Functionality is equivalent tothat provided on the PCM-30 Digital Trunk Controller (PDTC) fornetwork mode.


297-9051-525 Standard 04.01 April 2002

This implementation provides full backwards charging support.


This feature adds the SPIROU V3 ISUP protocol to the SpectrumPeripheral Module (SPM) STM-1 interface, thereby allowing networkoperators to connect to the French Telecom network using a direct STM-1interface. It introduces functionality to enable the DMS-100 MMP switchto support the French protocol variant SPIROU V3 using the SPM STM-1peripheral.

This implementation provides full backwards charging support, providingan ability to generate charge messages.

SPIROU V3 enables network operators to interface on all French Telecominterconnection points (both transit and local).

Note: The functionality currently available on the DMS-100 forSPIROU ISUP remains unchanged.

At MMP16, SPM supports the following functionality:

• STM-1

— SPECCONN Completion (59022028)

This feature provides the ability to specify a 64 Kbit/s clear pathnailed-up connection between two P-side endpoints (ports) where oneor both endpoints reside on a Spectrum Peripheral Module (SPM)equipped with the 155 Mbits/s STM-1 interface.

– Table SPECCONN

The nailed-up connection is provisioned by datafill in theSPECCONN table in the Computing Module (CM). The datafillconsists of two endpoints, a connection type, and a connectionstatus. SPECCONN is modified to allow SPM to be accepted as avalid peripheral type for D30 endpoint types.



– CI command QSCONN

The QSCONN command is used to query the state of individualconnection segments. Therefore this command supports querieswhere SPM is specified as an endpoint.

Note: Digital Test Access (DTA) or ISDN Line Card (ISLC)functionality, currently supported for XPM, will not besupported for the SPM.

– Logs

Five existing logs (PM231, PM232, PM233, PM234, PM236) aremodified so that entries can be made into these logs for specialconnections.

• ISUP

— Australia Interconnect ISUP (59017730)

This feature introduces functionality to enable the DMS-100 switch tosupport Australia Interconnect ISUP (Ie-ISUP) using the SpectrumPeripheral Module STM-1 peripheral.

This feature adds the Australia Interconnect ISUP protocol to the SPMSTM-1 interface, thereby allowing network operators to connect to theAustralian Telecom network using a direct STM-1 interface.

This activity provides the functionality required within the SPM tosupport the Australian Interconnect ETSI ISUP V2 protocol (referredto as AustraliaIC ISUP) using the STM-1 interface.

— Australia Backbone ISUP (59017697)

This feature is split between two other functionality features, namelyAU2371 and 59017265.

– AU2371 (Serving Carrier ID)

This feature allows the name of the carrier switch name to appearin AMA. It provides a means of associating a serving carrieragainst lines and trunks on a DMS100. The serving carrier isdefined as the carrier providing the service. The serving carrierinformation is used for billing purposes, so that the originating andterminating party lines determine the billing rate.

– 59017265 (MWI over ETSI ISUP and DN Padding forSMDI-Preparation)

The Message Waiting Indication (MWI) supplementary serviceenables the telecommunications network, upon the request of avoice mail centre, to indicate to the subscriber that there is at leastone message to be retrieved. This occurs when an agent,provisioned for the MWI service, receives mail on his mailbox at


297-9051-525 Standard 04.01 April 2002

the Voice Message System (VMS). A request is made to MWI toindicate to the subscriber that mail is pending. The subscriber isinformed instantly and whenever the receiver is in off-hook mode.When the subscriber attempts a call, the MWI supplementaryservice is activated and an indication of a message waiting is sentto the subscriber. The subscriber now accesses the voice mailcentre and the message is delivered. When the subscriber hasretrieved all of their messages by dialling into the VMS, the MWIis deactivated.

This feature extends existing MWI functionality (IBN lines onV5.2, CAS MUX lines, EBS sets and SMDI) to the followingagents: ETSI BRI, ETSI PRI and ETSI TCAP.

A new office parameter, DEFAULT_MWI_XLA_ENTRY withinOFCENG, provides a default entry point to translations for ETSIMWI requests. For ETSI MWI, message waiting indicationrequests are given universal translations to determine the receivinguser of the request.

Voice mail systems are connected to MMP DMS100 via an SMDI(Simplified Message Desk Interface) link. Padding is necessary fordirectory numbers (DNs) which are not either 7 or 10 digits inlength. A voice mail subscriber may only access his mailbox if thesubscriber’s DN is padded correctly for non-7 or 10 digit DNs. Thisfeature enables the MMP DMS100 product to configure SMDIwith the correct padding digit.

— France SSUTR2 (59027160)

This feature introduces functionality to enable the DMS-100 switch tosupport SSUTR2 using the Spectrum Peripheral Module STM-1peripheral.

• PRI

— STM-1 ETSI PRI (59026237)

This feature provides support for ETSI PRI trunks on the STM-1interface of the Spectrum Peripheral Module (SPM). Functionality isequivalent to that provided on the PCM-30 Digital Trunk Controller(PDTC) for network mode. The functionality is defined in NISA215-1, ETSI PRI (T) Specification, DMS_MMP Implementation ofETSI ISDN Primary Rate Interface at the T Reference Point; 21January 2000.



This feature supports the following Supplementary Services:

– Call Completion to Busy Subscriber (CCBS)

– Calling Line Identification Presentation (CLIP)

– Calling Line Identification Restriction (CLIR)

– Closed User Group (CUG)

– COnnected Line identification Presentation (COLP)

– COnnected Line identification Restriction (COLR)

– Direct Dialling In (DDI)

– Diversion - Partial Reroute (PPR) section only

– Explicit Call Transfer (ECT)

– Malicious Call IDentification (MCID)

– Subaddressing (SUB)

– User-to-User Signalling (UUS) - Service 1

— STM-1 PRI - AOC and Metering (59026347)

This feature supports the Advice of Charge (AOC) services that areused to collect and transmit real-time charging information to anoriginating subscriber for the calls they are making.

Charging services can be collected:

– On a regular basis during a call (AOC-D service) or

– At the end of a call (AOC-E service) or

– Both

This feature implements the Spectrum Peripheral Module (SPM)portion of the functionality required to provide both AOC-D andAPC-E services on the SPM platform for the ETSI PRI protocol.

— STM-1 PRI Digital Test Access (59028292)

This feature enhances digital monitoring of STM-1 Common ChannelSignalling (CCS7) links by providing the capability to monitorPCM-30 Primary Rate Interface (PRI) channels on an SPM equippedwith STM-1 RM and CEM cards, and a Data Link Controller (DLC).

The CONNECT command has been enhanced to support the SPM andallow the monitoring equipment to connect to the PRI D-channel. TheCONNECT command also allows Digital Test Access (DTA)connections to be verified and released.


297-9051-525 Standard 04.01 April 2002

• T & C

— SPM Hardcoded Tones - Australia, Switzerland, Portugal, NewZealand, Ireland (59028988)

This feature supports the implementation of tonesets for the followingmarkets:

– Australia

– New Zealand

– Portugal

– Ireland

– Switzerland

The tonesets are selectable through datafill provisioning of sixcorresponding tone synthesizer resource types in table MNCKTPAK.Only one type of tone synthesizer resource can be datafilled on allResource Modules of a given Spectrum Peripheral Module (SPM), thatis, only one tone synthesizer resource type is allowed per node.

MMP15In MMP15, SPM supports: Belgian ISUP, Italian ISUP, Spanish ISUP andBrazilian ISUP as well as Italian, Spanish and Brazilian tones. Belgian toneswere available with MMP13. Whilst providing enhancements to the ECANcapability that was delivered with MMP13, the MMP15 release also supportsKLM numbering and German Network Protection.

The extra SPM functions available in the MMP14 and 15 release are asfollows:

• ETSI ISUP signaling and variants:

— Italian ISUP (59014220)

Supports: ISUP redirection information on call-forward, emergencycalls, and Nuisance Caller Identification (NCI) without trunk hold.

— Spanish ISUP (59017644)

The Spanish ISUP is implemented as a variant of the ETSI ISUP V1protocol. It is dependent on the ETSI ISUP implemented within SPM.A message interface has to be created specifically for Spanish ISUPsdue to the fact that it handles messages in a different way to the baseETSI ISUP V1.



— Belgian ISUP (59017760)

Supports: ISUP redirection information on call-forward, emergencycalls, and Nuisance Caller Identification (NCI) without trunk hold.

— Brazilian ISUP (59017595)

Supports: The following bearer services: Speech, 3.1 kHz audio, and64 kbits/s unrestricted.

Allows: End-users in Brazil to remotely access the DMS-MMP and itsservices, and service providers to connect to Telebras.

The Brazilian ISUP is implemented as a variant of the ETSI ISUP V1protocol. It is dependent on the ETSI ISUP implemented within SPM.

• SPM STM-1 Carrier Maintenance (59008275)

Supports: Carrier maintenance for a new STM-1 high speed accessinterface, primarily for the international market.

• KLM numbering (59017369)

Supports: KLM numbering within the VC4P payload of VC12P and E1Pcarriers.

SETCARR, GETHIST and LISTHIST commands support the use ofpayload positions using KLM co-ordinates.

• STM-1 Italian and Spanish tones (59018949)

International tonesets for Italy, Spain and Brazil are implemented tocomplement those in Germany and the UK. Downloadable tonesets thatrely on matching data in the XPM files are not compatible. These tonesetsrequire reformatting to the newer versions before they can be supported onSPM.

• IUP and ECAN enhancements (59016306)

Provides provisioning and call processing support to control integratedEcho Canceller (ECAN) on SPM. Echo cancellation is now available forBTUP trunks. This feature provides similar functionality to the XPMplatform. The implementation is compatible with the operation ofXPM-based echo cancellers and with interworking between SPMs andXPMs on the same switch.

• Brazilian ISUP for Succession MG4000 (59018854)

Provides the toneset for the Brazilian Market. A programmable tonesynthesizer, BRATONE, is used to generate a variety of call progress,signalling and sequence tones. BRATONE synthesizes the tones fromfundamental parameters (frequency, amplitude and cadence) instead ofwavetables stored in memory. Therefore new types of tones can beproduced by downloading new parameter values. Therefore newwavetables and hardware updates are not required.


297-9051-525 Standard 04.01 April 2002

• Digital Test Access (59022039)

Provides digital monitoring of STM-1 Common Channel Signalling(CCS7) links. It also provides the ability to monitor analogue and digitalvoice trunks. There are four types of monitoring that refer to accessing atrunk that has a trunk-to-trunk call connected.

Note: This is a test only feature.

• German Network Protection (59019615 and 59025550)

This is a regulatory feature required by the German market. It providesPriority Class of Service (PCoS), which is used to prioritize specific typesof calls. If the feature is activated, then under certain predefined conditionsonly, those calls marked as priority are passed on through the network tothe SPM.

Hardware developmentThe Spectrum technology platform represents an entirely new set ofmechanical shelving and circuit pack designs. All circuit packs share commonfeatures and plug into a double-height shelf with a single backplane designedto fit an ANSI rack. (SPM configured in an ETSI rack is not currentlyavailable.) The design is compatible with Model B lineups.

Product structureThe Spectrum product structure is designed to support multiple Spectrumtechnology applications by building applications on the base frame assembly,NTLX91BA. This base assembly contains all the components, other than thecircuit packs, that are common to any Spectrum-based application. The circuitpacks are documented in the Modular Structure (MS) document, according toModular Documentation System (MDS) rules. This documentation methodassumes that all Spectrum technology customers use the currentSPM-designed backpanel and frame mechanicals.

Figure 2-1 shows the main elements of a DMS-sized rack containing twoSTM-1 SPM systems. A single DMS-sized rack is always provisioned withtwo SPM system shelves.



Figure 2-1 STM-1 SPM product structure

The ‘circuit packs’ box shows the circuit packs required to turn the baseframe into an STM-1 SPM. For documentation of these circuit packs and theframe assembly components, see the DMS-SPM Hardware Maintenance Ref-erence Manual, 297-1771-550.

DependenciesDeployment of the SPM STM-1 trunking peripheral on the DMS-100 MMPswitch is dependent on the presence of ENET on the switch.

On the ENET, the DS512 links are terminated by NT9X40DA cards.

NTLX51BA SPM Shelf Assembly (2 per frame)

NTLX55AA Cooling Unit Assembly (2 per frame)

NTLX57AA Power Cabling Interface Unit (PCIU) Assembly (1 per frame)

NTLX5010 Upper Grille Assembly (1 per frame)

NTLX5211 Backplane Assembly (1 per shelf)

NT0X25BE Grey Framework Assembly (1 per frame)

NTLX5011 Lower Grille Assembly (1 per frame)

NTLX5015 Air Filter Assembly (2 per frame)

NTLX91BA SPM-DMS Frame Assembly

NTLX58AA Alarm Card Assembly (1 per PCIU)NTLX59AA Fan Management Unit Assembly (2 per PCIU)

NTLX56AA Fan Unit Assembly (4 per Cooling Unit)

NTLX5101 SPM Shelf Mechanical Assembly (1 per shelf)NTLX5016 Air Filter Tray Assembly (1 per shelf)

NTLX60AA Blank Filler faceplate (0 to 22 per shelf)Circuit packs

NTLX82AA Common Equipment Module (2 per shelf)NTLX99BA STM-1 Interface Module (optical; 2 per shelf)NTLX65BA DSP Resource Module (0 to 24 per shelf)NTLX66BA VSP Resource Module (0 to 24 per shelf)NTLX61AA Shelf Interface Module (2 per shelf)


297-9051-525 Standard 04.01 April 2002

Software developmentThe software required to support the SPM system resides in several nodeswithin the SuperNode office. The loads delivered to the customer are:

• SuperNode core software load including the SPM configuration, centralmaintenance and call processing interfaces; this is the DMS-100 MMPload

• Software in the ENET to support the new ENET paddleboard and linkmaintenance for the SPM-ENET links

• SPM system-resident software including the CEM load, DSP RM load,VSP RM load and STM-1 RM load


II-1

Part IIFunctional description


• Functional overview (Chapter 3)

• Limitations and restrictions (Chapter 4)

Part

IIFu

nctio

nald

escr

iptio

n


3-1

3 Functional overview

This chapter describes how the SPM STM-1 trunking application isimplemented on the DMS-100 MMP switch, in the following sections:

• STM-1 interface

• ISUP protocol

• IUP (formerly BTUP) protocol

• Echo cancellation

• Tones

• Continuity testing

• Intelligent Networks

• OAM&P

• Carrier maintenance

• Companding and bit inversion

• Error handling

• Network Protection

• Digital Test Access

• ETSI PRI

STM-1 interfaceThe STM-1 interface provides the following:

• STM-1 optical interface compliant with G.703

• Automatic Protection Switching (APS) within 50 milliseconds as perG.841

• Full fill capacity (1953 DS0s)

• Asynchronous mapping of 63 E1s to 63 VC12s

• SDH alarm support

3-2 Functional overview

297-9051-525 Standard 04.01 April 2002

• Interface to two SPM common equipment modules (CEM; active andinactive) via nine SPM serial links to each CEM

• Multiplex Section Protection (MSP) switching of a signal (59033790 -ISN04 (TDM)) - see section on Protection Switching for a detaileddescription.

Improves MSP switching by providing:

— STM-1 1+1 unidirectional non-revertive multiplexer sectionprotection

— STM-1 1+1 unidirectional protection (revertive mode)

— STM-1 1+1 bidirectional protection - compatible with 1:n (revertivemode)

— STM-1 1+1 bidirectional protection - compatible with 1:n(non-revertive mode)

— STM-1 1+1 bidirectional protection - optimized for 1+1 network

— Commands (CLEAR, EXERCISE and LOCKOUT) to control theMSP switching of a signal

— Alarms for monitoring the MSP switching of a signal

• SPECCONN Completion (59022028 - MMP16)

This feature provides the ability to specify a 64 Kbit/s clear path nailed-upconnection between two P-side endpoints (ports) where one or bothendpoints reside on a Spectrum Peripheral Module (SPM) equipped withthe 155 Mbits/s STM-1 interface.

The connection has the following attributes:

— The connection is permanent. Once made, it can be removed onlythrough deliberate action by operating company personnel.

— The connection is a dedicated 64 Kbit/s data communication path. Itcan carry voice and/or signalling information from the P-side on anextended peripheral module (XPM) to a P-side on the same or a

Functional overview 3-3


different XPM. The connection can also carry four 16 Kbit/s timedivision multiplexed (TDM) D-channels.

— The connection is defined and controlled by the CM.

— The connections use non-channelized access CCS7 signalling.

— The nailed-up connection is provisioned by datafill in the SPECCONNtable in the Computing Module (CM).

— The QSCONN command is used to query the state of individualconnection segments. Therefore this command supports queries whereSPM is specified as an endpoint.

— Five logs (PM231, PM232, PM233, PM234, PM236) are used so thatentries can be made into these logs for special connections residing onan SPM.

Protection switchingA particular carrier level may be defined as a protection group, where onecarrier is the active carrier and the other carrier is inactive. If a problem occurson the active carrier, traffic can then be switched to the inactive carrier. Thisis known as a ‘protection switch’. For the SPM system, carrier protectionoperates at the multiplexer level and thus carrier protection switching isapplicable only to multiplexor section (STM1M) carriers.

The initial implementation of the STM-1 interface (MMP13) provideduni-directional non-revertive switching only. At ISN04 (TDM), feature59033790 (STM-1 K1 / K2 Byte Support) added significant functionality toprotection switching. From ISN04 (TDM) the following additional protectionmode schemes were provided:

• 1+1 unidirectional protection (revertive mode)

• 1+1 bidirectional protection - compatible with 1:n (revertive mode)

• 1+1 bidirectional protection - compatible with 1:n (non-revertive mode)

• 1+1 bidirectional protection - optimized for 1+1 networkFor unidirectional switching, the decision to perform a protection switch ismade locally and independently of the remote node. Switching is completewhen the traffic received by the SPM is switched to the other section irrespec-tive of whether the remote end has switched or not. Signaling is provided overthe K1, K2 bytes to inform the remote node of the SPM’s actions.

Bidirectional switching requires the MSP functions at both ends of the MSPlink to be able to communicate with each other and thereby to co-ordinate theswitch. This feature provides the necessary bit-orientated protocol, using theK1 and K2 bytes, to perform this activity. Both the local and remote nodesmust be configured to use the same bidirectional switching scheme, otherwiseswitching will not perform correctly.


297-9051-525 Standard 04.01 April 2002

In revertive mode: if a carrier protection switch occurs, the traffic is switchedfrom the Working Section to the Protection Section. When the Working Sec-tion has been repaired, the traffic will automatically revert (protection switch)back to the Working Section.

InterfaceThe operator has the ability to select one of the above modes of switching bychanging data schema table configuration.

This feature introduces the following new commands:

• Lockout

If applied to optimized protocols, it freezes the position of the sectionselector.

If applied to non-optimized protocols, it prevents switching to theProtection section.

• Exercise

This command provides the ability to test the bidirectional mode - it onlyapplies when there is no failure.

• Clear

This command clears all other switching commands. This may initiate aprotection switch.

The force command has also been changed.

This feature provides eight new alarms for monitoring the system. MSP alarmsare raised to indicate a restraint on the Multiplex Protection sectionmechanism, or to recover from faults occurring on STM1M carriers. Thealarms will be raised either for a:

• User action (the issue of a lockout, force or manual command), or

• Fault in communication with the distant equipment (that is, a differentconfiguration at each end of the link or a fault occurring during sparing).

Protection functionality can be summarized as follows:Automatic Protection Switching (APS) is completed within 50 ms (as perITU G.841) when:

— Signal Fail (SF) is detected in the active LTE, and the mate unit is inthe No Fault or Signal Degrade (SD) state.

— Signal Degrade is detected in the active LTE, and the mate unit is in theNo Fault state.

SF is defined as LOS (loss of signal) and LOF (loss of frame) detected in theRegenerator Section, and EXC (excessive errors), AIS (alarm indication sig-



nal), APSAM (Architecture mismatch), APSMM (Mode mismatch),APSCHM (Selector Channel Mismatch), APSIC (Invalid code), APSFEPLF(Far end protection failure), APSLCK (Lockout), APSFC (Forced), APS-MAN (Manual) and RFI (remote failure indication) detected in the Multi-plexer section. SD is detected at the Multiplexer section.The system supports protection mode and independent (simplex) mode.

The active RM always has the active line. This arrangement is known aswelded sparing.

The SPM manual protection switching command is also available at theSTM-1 PM MAP level. This allows operating company personnel to sparefrom an active device to an inactive device.

Automatic SYSB recovery processWhen the SPM goes into simplex mode from inactive (that is, initially bothCEMs are in the MANB state, and both STM-1 RMs are in the CBSY state),the active STM-1 RM behaves in the following way. When one of the CEMsreturns to service (RTS) from a MANB state, the active STM-1 RM changesto SYSB, then changes to INSV. The CEM then changes to INSV in thenormal way.

Note: This process of recovery through the SYSB state is built into thedesign of the new RM data synchronization manager which the STM-1 RMuses. The automatic SYSB recovery process carries out the actions neededto go INSV. Therefore any forcing of the STM-1 RM into an in-service state(INSV or HOLD) causes a SYSB request.

SynchronizationThe SPM system supports a loop timing mode, where the synchronization isderived from the currently active STM-1 signal entering the SPM.

The DMS switch typically receives its synchronization reference via a PDTC.The PDTC measures the phase difference between the received reference andthe message switch (MS) clock, and sends to the MS a message containing thisdifference. Based on the phase difference, the MS updates the frequency of itsoscillators to match the frequency of the reference. The resolution of the phasecomparator and the rate at which phase samples are sent to the MS result in aphase error between the reference and the MS, thus putting the DMS switchoutside the SDH synchronization specification. Derivation of synchronizationfrom the MS clocked externally is also of insufficient accuracy to meet theSDH specification.

Customers can achieve SDH standard synchronization by provisioning theSPM to receive its synchronization from the SDH equipment (for example, aDXC) to which it is connected. This means that the SPM system must always


297-9051-525 Standard 04.01 April 2002

be connected to equipment capable of providing a clock which meets the SDHspecification. This synchronization method is known as loop timing the SPMoff the DXC. For loop timing to operate within the CCITT specification, theMS and the DXC to which the SPM is loop timed must both derive their timingfrom the same source.

Note: Although back-to-back connection of two SPMs via the STM-1interface is a supported configuration, the connection does not conform tothe ITU synchronization standard.

ISUP protocolTrunk signaling

ISUP trunk signaling conforms to the following specifications:

• ETSI ISUP Compliance Templates

• ETSI ISUP Messages and Compliancy

A message interface has to be created specifically for Spanish variantISUPs.

• UK ISUP Compliancy

• ND0071 TCBSPECS German ISUP V2 Supplementary Services

The SPM does not directly participate in ISUP signaling termination. Thatfunction is handled by the link peripheral processor (LPP).

The following SPM national ISUP variants were developed at MMP 15:

• Brazilian ISUP

• Italian ISUP (V1 and V2)

• Spanish ISUP

• Belgian ISUP

The following SPM national ISUP variants were developed at ISN04 (TDM):


This feature adds the Turkish ISUP V1 and Turkish ISUP V2 protocols tothe Spectrum Peripheral Module (SPM) STM-1 interface, therebyallowing network operators to connect to the Turkish Telecom networkusing a direct STM-1 interface. It introduces functionality to enable theDMS-100 MMP switch to support the Turkish protocol variants TurkishISUP V1 and Turkish ISUP V2 using the SPM STM-1 peripheral. TurkishISUP V1 and Turkish ISUP V2 are variants of the ETSI ISUP V1 and ETSI



ISUP V2 protocols. Functionality is equivalent to that provided on thePCM-30 Digital Trunk Controller (PDTC) for network mode.

The architecture in the SPM is the same as in XPM (Extended PeripheralModule).


This feature adds the Israel Civilian ISUP V2 and Israel Defense ISUP V2protocols to the Spectrum Peripheral Module (SPM) STM-1 interface,thereby allowing network operators to connect to the Israeli Telecomnetwork using a direct STM-1 interface. It introduces functionality toenable the DMS-100 MMP switch to support the Israeli protocol variantsIsrael Civilian ISUP V2 and Israel Defense ISUP V2 using the SPMSTM-1 peripheral. Israel Civilian ISUP V2 and Israel Defense ISUP V2are variants of the ETSI ISUP V2 protocol. Functionality is equivalent tothat provided on the PCM-30 Digital Trunk Controller (PDTC) fornetwork mode.

This implementation provides full backwards charging support.


This feature adds the SPIROU V3 ISUP protocol to the SpectrumPeripheral Module (SPM) STM-1 interface, thereby allowing networkoperators to connect to the French Telecom network using a direct STM-1interface. It introduces functionality to enable the DMS-100 MMP switchto support the French protocol variant SPIROU V3 using the SPM STM-1peripheral.

This implementation provides full backwards charging support, providingan ability to generate charge messages.

SPIROU V3 enables network operators to interface on all French Telecominterconnection points (both transit and local).

Note: The functionality currently available on the DMS-100 forSPIROU ISUP remains unchanged.

The following SPM national ISUP variants were developed at MMP16:

• Australian Interconnect ISUP (59017730)

This feature introduces functionality to enable the DMS-100 switch tosupport Australia Interconnect ISUP (Ie-ISUP) using the SpectrumPeripheral Module STM-1 peripheral.

This feature adds the Australia Interconnect ISUP protocol to the SPMSTM-1 interface, thereby allowing network operators to connect to theAustralian Telecom network using a direct STM-1 interface.

• Australian Backbone ISUP (59017697)


297-9051-525 Standard 04.01 April 2002

This feature introduces functionality to enable the DMS-100 switch tosupport Australia Backbone ISUP using the Spectrum Peripheral ModuleSTM-1 peripheral.

This feature adds the Australia Backbone ISUP protocol to the SPMSTM-1 interface, thereby allowing network operators to connect to theAustralian Telecom network using a direct STM-1 interface.

• France SSUTR2 (59027160)

This feature introduces functionality to enable the DMS-100 switch tosupport SSUTR2 using the Spectrum Peripheral Module STM-1peripheral.

Call processing servicesThe ISUP features available are as follows:

• SS7 ISUP

• ISUP IMT trunks

• Operator services ISUP

• Continuity test

• Inband DTMF digit collection on ISUP: MCCS, Supplementary Codecollection, Reset dialing

• Call reorigination: Pound sign and Star reorigination of a call (both longand short duration tones)

• Tones and announcement treatments

InterworkingInterworking to existing protocols on PDTCs and DTCIs is supported. Asingle trunk group can be assigned across both SPM and PDTC. For a list ofcall interworkings see the DMS-100 Base Product Description.

IUP (formerly BTUP) protocolTrunk signaling

IUP trunk signaling conforms to the following specifications:

• DMS-100E Compliance to IUP Sections 2 and 3

The SPM does not directly participate in IUP signaling termination. Thatfunction is handled by the link peripheral processor (LPP).

Call processing servicesThe IUP public network features available are as follows:

• Malicious Call Identification (MCI)

• Operator Override (OOR) /Network Barge-in



• Emergency Calls

• Dynamic Routing Control (DRC)

• Caller Confidentiality (141 service)

• Automatic Recall (1471 service)

• Call Back When Free

• Integrated echo cancellation using ETSI ISUP (V1 and V2 plus variants)and IUP on STM-1

InterworkingInterworking to existing protocols on PDTCs and DTCIs is supported. For alist of call interworkings, see the DMS-100 Base Product Description.

Echo cancellationEcho cancellation is necessary when the echo from voice travelling timebecomes significant, for example, international calls and mobile telephonecalls. Echo cancellation is provided by the VSP (Voice Service Processor)Resource Module. The VSP provides a shared resource pool of echo cancellersthat are assigned to a trunk as required, and then removed from the trunk andput back into the resource pool when the call is completed. Echo cancellers areprovisioned by selecting the percentage of trunk coverage required (0% to100%) based on traffic engineering rules for the particular office. Thecustomer then purchases enough VSP modules to handle the coveragerequirement and the SPM manages the resource allocation automatically.

The VSP RM provides a network echo canceller which handles multipleechoes per channel (sparse impulse response coverage). Coverage is providedin 2-ms ‘chunks’. Capacity estimates are based on an average of 6 ms echocoverage per channel. The maximum tail delay is selectable in 16 ms stepsfrom 16 ms to 128 ms. If the echo canceller encounters conditions such as atail delay greater than the selected maximum, it reports its failure to converge.

The application includes a tone disabler selectable for G.164 or G.165 modeoperation. The disabler also activates on 2010 Hz CCIS tone. When disabled,the echo canceller is bit-transparent, allowing support for a 56 kbit/s dataservice.

MMP SPM echo cancellation provides similar functionality to the extendedperipheral module (XPM) platform (see DMS-100 MMP Translations Guide,297-9051-350). The implementation is compatible with continued andunchanged operation of XPM-based echo cancellers and with interworkingbetween SPMs and XPMs on the same switch.

Echo cancellation devices are integrated with carrier access equipment whichare accessed on a per trunk/per call basis from a resource pool. The size of the


297-9051-525 Standard 04.01 April 2002

resource pool is dependent on the number and types of voice signal processing(VSP) modules available.

TonesTone detection

The SPM provides a resource pool of the DTMF and MF receivers that arerequired for tone detection functionality in international trunking applications.STR (Specialized Tone Receiver) and UTR (Universal Tone Receiver) XPMequivalency is supported, although blue box fraud is not supported.

Tone generationMMP16The following international tonesets are available for the ISN04 (TDM)release of the SPM system.

• Australia

• New Zealand

• Portugal

• Ireland

• Switzerland

The tonesets are selectable through datafill provisioning of six correspondingtone synthesizer resource types in table MNCKTPAK. Only one type of tonesynthesizer resource can be datafilled on all Resource Modules of a givenSpectrum Peripheral Module (SPM), that is, only one tone synthesizerresource type is allowed per node.

MMP15The following international tonesets are available for the MMP15 release ofthe SPM system.

• German

• UK

• Brazil

• Italy

• Spain

• Belgium

Note 1: Other tonesets will be added as feature deliverables, as the STM-1product is deployed in other MMP markets.

Note 2: Downloadable tonesets that rely on matching data in the XPM filesPTCXTONE (formerly ASMXTONE) are not compatible. These tonesets



require reformatting to the newer versions before they can be supported onSPM.

Continuity testingContinuity tone (COT) testing is available to support CCS7 signaling whererequired. This facility is necessary because the CCS7 signaling and voice pathsare separate, so that a successful signaling interaction does not guarantee thata functional voice path has been established. COT tests involve transmissionand reception of special tones over the voice circuit before the call isestablished. COT tests are not required on every call setup, and for operationalsavings can be achieved by provisioning COT tests to occur every nth call ona given trunk.

High-level control of COT tests is performed by the switch core; the SPMprovides the necessary transceivers to generate and detect the COT tones. Thisis accomplished using the Digital Signal Processor (DSP) Resource Module inthe SPM. The continuity tone transmitter/receiver handles complete COT testsfor 2W and 4W circuits. It is selectable as outgoing or incoming mode, andmay be configured for variations in test frequencies/levels and protocols.

Intelligent NetworksThe Intelligent Networks (IN) functionality in the SPM is fully compliant withthe ITU Intelligent Networks System Guide. The following paragraphs providedetails.

On the DMS-100 switch, Intelligent Networks (IN) call processing isimplemented mainly in the Computing Module (CM). The peripheral (XPM)contains no specific IN code. However, the peripheral handles re-supervisionon calls that become IN calls.

The re-supervision is a standard message sent from the CM to the peripheral.The IN re-supervision message contains no IN-specific supervision elements.Re-supervision has the following aims. The peripheral:

• reports to the CM, rather than bouncing messages for call interworking

• sends specific information to the CM, that is, ISUP RELs rather than CLFs

For an IN EDP8 call, the digit collection resource is checked before sendingthe STR supervision element to the peripheral to start digit collection. In theSPM, the DTMF resource in the DSP card provides the digit collectionresource. (In the XPM, the STR card provides this resource.)

OAM&PThe SPM system has a switch-based local/remote MAP interface. The systemcontains new functionality for provisioning and hierarchical carrier


297-9051-525 Standard 04.01 April 2002

maintenance, and provisioning software to introduce the new RM device to theComputing Module (CM).

After a new device is datafilled, it can be posted via the MAP CommandInterpreter (CI) interface, for manual intervention such as maintenanceactivities and queries.



MAP interface enhancementsThe STM-1 RM MAP structure conforms to the standard MAP interface usedfor the existing OC-3, DSP, and VSP RM. The SPM user interface is based onthe DMS MAPCI interface. Figure 3-1 shows the SPM MAP hierarchy,including the STM-1 RM MAP level. The Peripheral Module (PM) MAP levelis an existing sublevel of the MTC MAP, giving access to variousDMS-SuperNode peripheral groups.

Figure 3-1 SPM MAP user interface hierarchy

The MAP display supports KLM numbering with VC12P and E1P carriers onPOST CARRIER level.

DSP

MAPCI

MTC

SPM

OC3 VSP

PM

Status LCM

.... ....

Protection

....

....CARRIER

CEMSTM-1

New STM-1 RM MAP levelExisting SPM MAP hierarchyExisting MAP levels

TRKS


297-9051-525 Standard 04.01 April 2002

Figure 3-2 shows the SPM screen, which gives a summary of an entire SPM.It shows all the modules in an SPM, their slot numbers, activity status (A(active) or I (inactive)) and service state (Insv etc.).

Figure 3-2 SPM summary screen

CM MSN IOD Net PM CCS Trks Ext APPL. . . . . . . . .

SPM 0 Quit 2 Post_ 3 Listset 4 ListRes 5 Trnsl 6 7 8 9 10 11 Disp_12 Next13 Select_14 QueryPM15 ListAlm_16 17 18

SysB ManB OffL CBsy ISTb InSv PM 0 0 2 0 0 27 SPM 0 0 1 0 0 20 SPM 32 InSv Loc: Site HOST Floor 1 Row P FrPos 2

Shlf1 Sl A Stat Shlf1 Sl A Stat Shlf2 Sl A Stat Shlf2 Sl A StatDSP 2 1 A Insv CEM 1 8 I Insv VSP 2 1 A Insv --- - 8 - ----DSP 4 2 A Insv STM 0 9 A Insv --- - 2 - ---- VSP 6 9 A Insv--- - 3 I Insv STM 1 10 I Insv --- - 3 - ---- --- - 10 - ------- - 4 I Insv --- - 11 - ---- --- - 4 - ---- --- - 11 - ------- - 5 - ---- --- - 12 - ---- --- - 5 - ---- --- - 12 - ------- - 6 - ---- VSP 4 13 A Insv --- - 6 - ---- --- - 13 - ----CEM 0 7 A Insv VSP 4 14 A Insv --- - 7 - ---- --- - 14 - ----

CMAP0Time 14:12 >



From the SPM screen, the user can select one or more devices (CEM, DSP,VSP, or STM). Figure 3-3 shows the screen layout for displaying the newSTM-1 RM in the SPM node MAP display.

Figure 3-3 STM-1 MAP screen

CM MSN IOD Net PM CCS Trks Ext APPL . . . . . . . . .

STM 0 Quit 2 3 ListSet 4 5 6 Tst_ 7 Bsy 8 RTS 9 OffL10 LoadMod11 12 Next13 Select_14 QueryMod15 ListAlm16 Prot 17 18

SysB ManB OffL CBsy ISTb InSv PM 0 0 2 0 0 27SPM 0 0 1 0 0 20STM 0 0 1 0 0 0

SPM 32 STM 0

Loc: Row P FrPos 2 ShPos 40" Sh 0 Slot 9 Prot grp: 1Load: STM01 Prot Role: WorkingPOST:STM0:

CMAP0Time 14:12 >


297-9051-525 Standard 04.01 April 2002

The screen layout (see Figure 3-4) of the STM-1 carriers includes thefollowing information:

• Carrier class (CLASS)

• Host site (SITE)

• Node number (SPM)

• Payload positions (STMIR, STM1M, VC4P, VC12P, E1P)

• Circuit number (CKT)

• Carrier service state (STATE)

• Transmit and receive indicators (TR)

• Maintenance and alarm state indicator (MA)

Figure 3-4 STM1R POST screen

For a more detailed description of the MAP levels, see the DMS-SpectrumPeripheral Module Commands Reference Manual, 297-1771-819.

CLASS ML OS ALARM SYSB MANB UNEQ OFFL CBSY PBSY INSVTRUNKS 1 0 7 7 0 0 0 11 0 6REMOTE 1 0 5 0 0 0 0 4 32 29TIMING 1 0 2 0 0 0 0 2 0 0PROTLN 0 0 0 0 0 0 0 0 0 2HSCARR 0 0 0 0 0 0 131 0 0 0

N CLASS SITE SPM RM STM1R CKT STATE TR MA 0 HSCARR HOST 10 0 0 1 OFFL -- -- 1 HSCARR HOST 10 1 0 2 OFFL -- --

CMAP0Time 14:12 >

POST 0 Quit 2 Post_ 3 4 5 Loop_ 6 Tst_ 7 Bsy_ 8 RTS_ 9 OffL_1011 Disp_12 Next1314 Detail_15 ListAlm_1617 PerfMon_18

CM MS IOD Net PM CCS Trks Ext APPL . 12SBPT . RExByp 2 SPM . 30 CC 2Crit . *C* *C* *C*

STM1R



STM-1 RM command descriptionsThe following commands are provided:

• Quit - quit out of the current MAP level.

• Tst - run manually in-service (InSv) and out-of-service (OOS) diagnosticson the selected device.

• Bsy (Busy) - manually place the selected device into a manual OOS(MOOS) state.

• Rts (Return to Service) - manually bring the selected device from an OOSstate (MOOS or SOOS) back to a ready or InSv state.

• OffL - set the selected device into an OFF LINE state.

• LoadMod - manually download a specific load file to the selected device.

• QueryMod - manually query local/CM information on the selected device.

• Prot - carry out a manual protection switch.

Additional commands which do not interface with IDM are as follows:

• ListSet - provides a list of the posted entities in a post set.

• Next - selects the ‘next’ RM in the post set. If there are no more RMs inthe posted set, then the system displays a message and control returns tothe SPM level.

• Select - selects another device of any type configured to this SPM node.

• ListAlm - lists all alarms that are set against the posted RM. If no alarmsare set, the system indicates this for each possible alarm severity.

The hidden commands for the STM-1 MAP level are as follows:

• ResetMod - resets the selected STM-1 circuit pack.

• Wait - turns on/off/query wait mode.


297-9051-525 Standard 04.01 April 2002

Carrier maintenanceFigure 3-5 summarizes the STM-1 carrier hierarchy which may be provisionedusing table MNHSCARR.

Figure 3-5 STM-1 carrier hierarchy

Each E1 contains up to 31 bearer channels which are available to trunkmaintenance.

A maximum of two regenerator section (STM1R) carriers per SPM can bedefined, one on the WORKING STM RM circuit pack and one on the SPARESTM RM circuit pack. A maximum of two Multiplexor section (STM1M)carriers per SPM can be defined, one on the WORKING STM circuit pack andone on the SPARE STM circuit pack. The two STM1R and STM1M carriersform the protection switching mechanism described on page 3-2.

A VC4P carrier must be datafilled against the WORKING STM1M carrier.There can only be one VC4P carrier per STM1M protection group, whichmeans that there can only be one VC4P carrier defined per SPM. A maximumof 63 VC12P carriers can be defined per VC4P carrier (which means amaximum of 63 VC12P carriers per SPM). Only one E1P carrier can be

VC-4

STM-1R

Protected carrierSTM-1M

VC-12

E1

Up to 63 carriers per SPM

Spare

Working

SPM



defined per VC12P carrier (which means a maximum of 63 E1P carriers perSPM).

Guidelines for VC12 carrier datafillVC12P carrier names support the inclusion of KLM numbering. The KLMnumbering system is used for the International market to represent VC12carrier names on VC4P. c.p. with the previous section. Such a naming schemehelps to locate VC12P/E1P carriers in SDH (Synchronous Digital Hierarchy)when troubleshooting. For example, suppose that a problem occurs with afar-end E1 with KLM number 1,1,3 connecting to SPM1. The carrier namecontains all this information and operating company personnel knowimmediately that the carrier to check is SPM_1_VC12P_113.

STM-1 is a high speed digital carrier contained in SDH. SDH uses a set ofstandards that are used by the international market.

The KLM numbering scheme uses a three digit (k, l, m) co-ordinates torepresent the carrier position of VC12P within VC4P. E1P is also representedby KLM numbering since VC12P has a one-to-one mapping with E1P carriers.The relationship between the KLM numbering and the tributary unit group(TUG) is shown below:

TUG3 = K = values 1 to 3

TUG2 = L= values 1 to 7

TVC12 = M= values 1 to 3

The following CI commands use payload positions, and can also use KLMco-ordinates, as inputs and outputs:

• SETCARR

• GETHIST

• LISTHIST

For example, the SETCARR command:

SETCARR VC4P 1 VC12P 112

could be used with a KLM of 112.


297-9051-525 Standard 04.01 April 2002

AlarmsThe supported list of carrier defects is as follows:

• STM1R - LOS, LOF

• STM1M - AIS, APSAM, APSMM, APSCHM, APSIC, APSFEPLF,APSLCK, APSFC, APSMAN, EXC, RFI, SD

• VC4P - AIS, RFI, LOP, TIM, SLM, LOM, UNEQ

• VC12P - AIS, RFI, LOP, TIM, SLM, UNEQ

• E1P - AIS, CRE, LLCMA, LOF, RAI, BER

For each defect the user can provision (by datafill) an alarm severity ofCritical, Major, Minor, or No Alarm. The alarm severities are printed as partof the carrier log. There is no functional consequence of allocating a particularseverity to an alarm.

The system raises an alarm if the defect persists for 2.5 seconds. The systemclears the alarm if the defect is not evident for 10 seconds.

Note: These threshold parameters are not datafillable.

Performance Monitoring parametersThe supported Performance Monitoring parameters are as follows:

• STM1R - ES, SES, UAS, BBE

• STM1M - ES, SES, UAS, BBE

• VC4P - ES, SES, UAS, BBE

• VC12P - ES, SES, UAS, BBE

• E1P - ES, SES, UAS, BBE, CSS, CRC4

For each performance parameter, the user can provision a 15-minute and24-hour performance parameter threshold and an alarm severity of Critical,Major, Minor, or No Alarm.

Note: The performance parameters are supported for near end (NE) only.

Performance Monitoring archivalThe ITU specification G.784 requires terminal equipment to maintainperformance monitoring historical data, for both the 15-minute and 24-hourregisters. The DMS switch fulfills this requirement by storing the performancedata gathered by the SPM in disk files on the CM. The user can then displaythe performance data, and use it to find fault locations within the transmissionsystem.



The following table shows which performance parameters are archived.

MAPCISupport for the new STM-1 carriers (STM1R, STM1M, VC12P, VC4P, andE1P) includes changes to the existing Post and Detail commands at theCARRIER level.

The POST command is available, at the CARRIER level of MAPCI, whichcan be accessed by typing the following command at the command interface:

MAPCI;MTC;TRKS;CARRIER

The user can use the Post command to specify a set of all the carriers on a SPMof a given state (removing the previous restriction of specifying either the SPMnode number or the carrier state). For example, to display all the InSv carrierson SPM 1, the user can enter the command:

POST SPM 1 INSV

The user can use the Detail command to display additional details about theposted carrier.

Idle bit patternITU specifies a number of set bit patterns that must be sent when a trunk is inthe idle state (that is, not involved in call processing but available for callprocessing) to the trunk connected at the far end. For the E1 market, theDMS-100 MMP switch supports two such bit patterns:

• G.714 - 11010101 (hex D5)

• Q.503 - 01010100 (hex 54)

The user can select the required bit pattern by datafilling an entry in the E1Ptuple of table MNHSCARR.

Carriertype

Performance Monitoring parameters collected

UAS ES SES BBE PSC CSS CRC4 LBC OPT OPR

STM1R NE NE NE NE NE NE NE

STM1M NE NE NE NE NE

VC4P NE NE NE NE

VC12P NE NE NE NE

E1P NE NE NE NE NE NE


297-9051-525 Standard 04.01 April 2002

Companding and bit inversionAny byte stream, carried over a trunk which is incoming to the DMS switchand which carries voice, in the E1 market is encoded using A-law companding.ITU specification G.711 specifies that this bit stream must also be even bitinverted (EBI). This E1 companding is called A-law companding plus EBI,denoted ‘A’.

The trunk interface card (NT6X27) on a PDTC even bit inverts all bit streamsas they pass through the card into the XPM. This means that the internal XPMformat is A-law companding without EBI. This is called pure A-lawcompanding, denoted ‘Ac’. Figure 3-6 shows this process.

Figure 3-6 Even bit inversion on a PDTC

For a data call, the bit stream must be clear (no bit inversion or companding).This is called data clear, denoted ‘D’.

The voice trunks incoming to the STM-1 interface are A-law companding plusEBI, just as on a PDTC. However, unlike the NT6X27 on the PDTC, theSTM-1 interface card (NTLX99BA) does not perform any bit inversion on thebit stream. Therefore the internal format of the bit stream on an E1 SPM isA-law companding plus EBI. This means that all Resource Modules arehard-coded to accept bit streams with A-law plus EBI companding.

The ENET requires the bit stream to be pure A-law, therefore all payload bitstreams must be EBIed at the SPM/ENET interface. There is provision withinthe SPM to perform a global EBI at the DS512 interface. Figure 3-7 shows thisprocess.

6X27

A AcTrunk to/fromexternal source

To internal XPMand ENET

(E1 interface)



Figure 3-7 Even bit inversion at the SPM/ENET interface

International standards require trunks to be A-law. No A-law to µ-lawconversion is required in Europe (or Australia).

The SPM interface provides a global even bit inversion between the CEM andthe DS512 interface, that is, EBI is performed on every payload time slot. Alldata calls are EBIed as they enter and exit the ENET. This results in a net effectof no bit inversion and is consistent with what happens currently on the PDTCto ENET interface.

Error handlingDevice logs

Existing SPM logs are used to report on the condition of an STM-1 RM device(the same logs report the condition of the DSP, VSP and CEM RMs). The logsdefined for alarm reporting are as follows:

• SPM300, SPM310, SPM311, SPM313, SPM331, SPM334, SPM335,SPM336, SPM337, SPM338, SPM339, SPM340, SPM350 - fault reportlogs

• SPM500, SPM501, SPM502, SPM503, SPM504, SPM510, SPM600,SPM630, SPM637, SPM638 - state change logs

• SPM650, SPM651, SPM660, SPM661 - loading logs

• SPM700, SPM701, SPM702, SPM703, SPM704, SPM705, SPM706,SPM707, SPM708, SPM709, SPM710 - DDM audit logs

Carrier maintenance logsThe SPM carrier maintenance logs report changes in the level of serviceintegrity provided by an SPM node. The carrier maintenance logs are asfollows:

• CARR300, CARR310 - carrier failure event logs

• CARR340, CARR341 - carrier protection logs

LA ATrunk to/fromexternal source(STM-1 interface)

X99

Ac

Internal SPM To ENET

CEM


297-9051-525 Standard 04.01 April 2002

• CARR500, CARR501, CARR510, CARR511, CARR512 - carrier statechange logs

• CARR800, CARR810, CARR811 - threshold-crossing event logs

The payload position is converted to KLM co-ordinates.

Network ProtectionPriority callsThis is a regulatory feature required by the German market. It provides PriorityClass of Service (PCoS), which is used to prioritize specific types of calls. Ifthe feature is activated, then under certain predefined conditions only, thosecalls marked as priority are passed on through the network to the SPM.

If a Timed Break Recall (TBR) is used on Digitone (DGT) telephones a featurecan be used reliably. An office parameter, ENABLE_TBR_ON_DGT, can beused to enable or disable the collection of dial pulse digits after a DGTtelephone has initiated a feature.

Note: When ENABLE_TBR_ON_DGT is set to ‘Y’, features requiring TBRare not supported on dial pulse telephones using DGT lines. To supportfeatures requiring TBR on dial pulse telephones, the DGT option must beremoved from the lines.

A PCoS allows prioritized users to have privileged access to the telephonesystem during catastrophic situations. So for emergency situations, PCoSgives priority ISDN BRI and PRI calls (for example, police, fire andambulance) priority treatment. There are two levels of PCoS:

• ESP (Essential Service Protection)

When ESP is set to ‘ON’ messages from priority accesses are givenpriority. Priority accesses are ELN line option users and ISDN PRI userswith the PCoS option provisioned.

• NETPROT

When NETPROT (Network Protection) is set to ‘ON’, only priorityaccesses are allowed to use the network.

There are no specific German emergency call (110, 112 or 115) handling.They are treated as priority calls. The dialed emergency number is specificallytranslated to the real number of the nearest emergency bureau and routed.

Digital Test AccessThe Digital Test Application provides a mechanism to monitor individualCCS7 (Common Channel Signaling) links and digital voice trunks.Monitoring refers to accessing a trunk that has a trunk-to-trunk call connected.



The following four commands allow various forms of trunk monitoring:

• MONPOST provides the connection between the incoming path of theposted trunk and the outgoing path of the digital jack ended trunk.

• MONLINK provides the connection between the incoming path of thelinked trunk and the outgoing path of the digital jack ended trunk.

• MONBOTH enables the user to listen to incoming transmission of theposted trunk and incoming transmission of the linked trunk.

• MONTALK establishes a 3-party conference circuit connection betweenthe posted trunk, the linked trunk and the headset of the TTP. Thiscommand is only available for analog monitoring.

ETSI PRIThe following activities provide support of ETSI PRI trunks on the STM-1interface of the SPM:

STM-1 France VN4 / VN6 (59027083)This feature provides support of VN4 and VN6 PRI trunks on the STM-1interface of the Spectrum Peripheral Module (SPM). Functionality isequivalent to that provided on the PCM-30 Digital Trunk Controller (PDTC)for network mode on the DMS-100E. The functionality is defined in NISA215-1, ETSI PRI (T) Specification, DMS-MMP Implementation of ETSIISDN Primary Rate Interface at the T Reference Point; 21 January 2000.

All VN4 and VN6 supplementary services are supported on the STM-1interface on the SPM by activities: 59026237 and 59026347.

STM-1 ETSI PRI (59026237)Provides equivalent functionality to that on the PCM-30 Digital TrunkController (PDTC) for network mode. The functionality is defined in NISA215-1, ETSI PRI (T) Specification, DMS_MMP Implementation of ETSIISDN Primary Rate Interface at the T Reference Point; 21 January 2000.

This feature supports the following Supplementary Services:

• Call Completion to Busy Subscriber (CCBS)

• Calling Line Identification Presentation (CLIP)

• Calling Line Identification Restriction (CLIR)

• Closed User Group (CUG)

• COnnected Line identification Presentation (COLP)

• COnnected Line identification Restriction (COLR)

• Direct Dialling In (DDI)

• Diversion - Partial Reroute (PPR) section only


297-9051-525 Standard 04.01 April 2002

• Explicit Call Transfer (ECT)

• Malicious Call IDentification (MCID)

• Subaddressing (SUB)

• User-to-User Signalling (UUS) - Service 1

Note: The Data Link Controller Resource Module (DLC RM) card isrequired for the SPM to support ETSI PRI.

STM-1 PRI ETSI - AOC and Metering (59026347)This feature supports the Advice of Charge (AOC) services that are used tocollect and transmit real-time charging information to an originatingsubscriber for the calls they are making.

Charging services can be collected:

• On a regular basis during a call (AOC-D service) or

• At the end of a call (AOC-E service) or

• Both

This feature implements the Spectrum Peripheral Module (SPM) portion of thefunctionality required to provide both AOC-D and APC-E services on theSPM platform for the ETSI PRI protocol.

STM-1 PRI Digital Test Access (59028292)This feature enhances digital monitoring of STM-1 Common ChannelSignalling (CCS7) links by providing the capability to monitor PCM-30Primary Rate Interface (PRI) channels on an SPM equipped with STM-1 RMand CEM cards, and a Data Link Controller (DLC).

The CONNECT command has been enhanced to support the SPM and allowthe monitoring equipment to connect to the PRI D-channel. The CONNECTcommand also allows Digital Test Access (DTA) connections to be verifiedand released.

Note: The SPM supporting the PRI D-channel must be equipped with thefollowing, or more recent, hardware:

• SPM processor card - NTLX82AA

• Data Link Controller (DLC) - NTLX72BA

• STM-1 RM - NTLX99BA

The PCM-30 Digital Trunk Controller (PDTC) used as monitoringequipment requires:

• PCM-30 interface card - NT6X27AC


4-1

4 Limitations and restrictions

This chapter discusses the following limitations and restrictions applying tothe SPM STM-1 trunking application:

• operational limitations

• memory utilization

• table size

The following sections give details.

Operational limitationsThe SPM STM-1 trunking application has the following operationallimitations:

• To maintain SDH synchronization standards, the STM-1 SPM mustalways be connected to equipment capable of providing an SDH qualityclock (DXC (Digital Cross-Connect) or equivalent).

• Although back-to-back connection of two SPMs via STM-1 is a supportedconfiguration, the connection does not conform to the ITU synchronizationstandard.

• ECAN is provided for IUP and ETSI ISUP V1 and V2 protocols, GermanISUP and UK ISUP, Italian ISUP, Spanish ISUP, Belgian ISUP, andBrazilian ISUP in the MMP15 timeframe, subject to the following notes:

— In end offices/local exchanges where lines are interworking to ETSIISUP, compliance is 100%.

— In transit nodes where previous nodes have not inserted echocancellation, the SPM inserts the echo canceller on the incoming trunk.Specifications and present DMS behavior insert the echo canceller onthe outgoing trunk. From an end-user perspective, there is nodiscernible difference.

— Reverse Connection is functional with the use of the FAREC booleanin table SPMECAN. However, the echo canceller is applied on the

4-2 Limitations and restrictions

297-9051-525 Standard 04.01 April 2002

incorrect trunk. From an end-user perspective, there is no discernibledifference.

— The MMP SPM echo cancellation implementation provides equivalentfunctionality to that currently available via the extended peripheralmodule (XPM) platform. In addition, the implementation is compatiblewith continued and unchanged operation of XPM-based echocancellers and with interworking between SPMs and XPMs on thesame switch.

• The DTMF and MF receivers provided for tone detection functionality donot support blue box fraud.

• The only supported implementation of the MTP router is internal routing(external routing is not currently a requirement in the E1 market).

• The STM-1 RM does not support the following features:

— E1 path protection

— full-featured multiplexing and mapping (the STM-1 RM supportsasynchronous E1 to STM-1 mapping only)

• For the performance archival facility, only the near-end PerformanceMonitoring parameters are supported.

• The SPM system does not support Specconn. If non-channelized access isused, the physical carriers for the bearer and signaling channels must beseparated so that the two components enter the DMS-100 MMP switch asfollows:

— Only the bearer channels enter via the SPM.

— The signaling channels enter using an E1 connection to the LIU via aMUX.

Table sizeThe size of the tables which support the SPM STM-1 trunking application (thatis, the tables in the datafill sequence) are as follows:

Table Maximum size (tuples)

ENCDINV 592

LOGCLASS 512

MNCKTPAK 1,662

MNHSCARR 8,384

MNLINK 64

MNNODE 64

Limitations and restrictions 4-3


MNPRTGRP 1,792

MNSHELF 128

PMLOADS 255

TRKMEM 16,000,000

Table Maximum size (tuples)

4-4 Limitations and restrictions

297-9051-525 Standard 04.01 April 2002


III-1

Part IIIInteractions

This part contains the following chapter:

• Feature interactions (Chapter 5)

Part

IIIIn

tera

ctio

ns


5-1

5 Feature interactions

The SPM system has no feature interactions.

Note: Although the SPM interacts with other features, it does not changetheir functionality.

5-2 Feature interactions

297-9051-525 Standard 04.01 April 2002


IV-1

Part IVPlanning and engineering


• Planning for installation (Chapter 6)

• Hardware requirements (Chapter 7)

• Software description (Chapter 8)

• System engineering (Chapter 9)

• Signaling requirements (Chapter 10)

• Capacity information (Chapter 11)

Part

IVP

lann

ing

and

engi

neer

ing


6-1

6 Planning for installation

The following manual describes the procedures to be followed in preparationfor installing an SPM:

• IM24-6750 (basic SPMand STM-1 specific procedures)

Note: All installation procedures are carried out by Nortel staff.

PlanningPlanning of the SPM system covers the following topics:

• hints on getting ready to install an SPM

• physical aspects

• organizational aspects

• overview/road map of the planning and provisioning sections of the SIG

• cross-references to NA installation procedures manual

InstallationInstallation of the SPM system covers the following topics:

• alarms

• power and grounding

• cabling

• accessibility

• floor loading

• mounting hardware

• seismic considerations

• ventilation

• thermal loading

• tool requirements

• floor plan restrictions

6-2 Planning for installation

297-9051-525 Standard 04.01 April 2002


7-1

7 Hardware requirements

This chapter outlines the hardware required to support the SPM STM-1trunking application.

FeaturesThe STM-1 Resource Module (STM-1 RM; card NTLX99BA) is an SDHSTM-1 carrier interface module for the Spectrum Peripheral Module (SPM).It allows the SPM to terminate SDH STM-1 transmission systems carryingasynchronous E1 payloads, and it also maps the DS0s in those payloads to theinternal format of the SPM.

The features of the STM-1 RM are as follows:

• single uni-directional STM-1 line interface (two Resource Modules arerequired for carrier protection)

• hardware support for 1+1 protection switching

• STM-1 optical interface compliant with G.957

• on-board Local Processing Complex for

— low level maintenance functions

— Performance Monitoring data collection

• terminates up to 1953 DS0s mapped to a maximum of 63 asynchronous(PDH) E1s

• Channel Associated Signaling supported by hardware on a per E1 basis

• jitter performance as per G.825

• translation of link payload to and from the internal SPM S-Link protocol

• on-board diagnostics, self-test and JTAG capability

• timing recovery from incoming STM-1 for distribution to SPM CEM

• QUICC-baseRM compliant

7-2 Hardware requirements

297-9051-525 Standard 04.01 April 2002

Unsupported featuresThe STM-1 RM does not support the following features:

• Routing of STM-1 section and regenerator DCC to QUICC SCC ports.

• E1 path protection - this feature is not currently planned for the STM-1RM.

• Full-featured multiplexing and mapping - the STM-1 RM supportsasynchronous E1 to STM1 mapping only (see next section).

SDH multiplexing and mappingThe STM-1 RM supports a subset of the complete SDH multiplexing structuredefined in ITU-T G.707, as shown in Figure 7-1.

Figure 7-1 SDH multiplexing/mapping scheme supported by STM-1 RM

FunctionsThe principal functions of the STM-1 RM are as follows:

• STM-1 optical interface, including data and clock recovery

• SDH STM-1 interface termination including frame generation, alarmdetection and generation, and error detection hardware

• termination of asynchronous E1 payloads

• overhead support at all multiplexing levels

• STM-1 and E1 transmit clock generation

• SDH and E1 alarm support

• mapping of DS0s and overhead to nine SPM S-link interfaces to each SPMCEM

• interfaces to two SPM CEMs (active and inactive) via nine SPM seriallinks to each CEM; messaging and payload data is passed over one link andthe remaining links are used for payload data

STM-1 AUG AU-4 VC-4

TUG-3

TUG-2

TU-12 VC-12 C-12

x 3

x 7

x 3

2048 kbit/s

Pointer processing

Multiplexing

Aligning

Mapping

E1


8-1

8 Software description

Software architectureThe software required for the SPM STM-1 application affects the DMS-100MMP Core Processor (CM), the SPM Common Equipment Module (CEM)and the STM-1 Resource Module.

Figure 8-1 shows the general architecture of the DMS-100 MMP software.

Figure 8-1 DMS-100 MMP software architecture

Base

TL

CCM

WT TOPS

SHR

XPM SPM

SDM

8-2 Software description

297-9051-525 Standard 04.01 April 2002

The following table shows the architecture and functionality of the STM-1application software developed in the MMP15 release.

Functionality Software layers affected

Additional ISUP country variants SPM

STM-1 sparing enhancements and KLMnumbering

SHR

IUP and ECAN Enhancements TL, SHR, CNA, WT

German Network Protection (PCOS) SHR, WT, SPM


9-1

9 Capacity and PerformanceEngineering

Collection of performance dataCall processing capacity data make it possible to give a supported level ofperformance while maintaining the required grade of service. Data collectedfor the STM-1 SPM give a per release indication of the change in callprocessing capacity.

SPM capacity data in the SPM are collected using the sperform tool whichresides in the SPM and provides an indication of the number of calls runningin the SPM. A further tool, resmon, displays the CPU occupancy. These toolsallow the measurement of CPU occupancy at different traffic levels.

Call types and timingsFor valid call types and timings, contact your Nortel representative.

SPM recovery timingsFor valid SPM recovery timings, contact your Nortel representative.

RTS TimingsFor valid RTS timings, contact your Nortel representative.

Processor real time allocations

Figure 9-1 shows the way in which processor real time is allocated to callprocessing and other processes.

9-2 Capacity and Performance Engineering

297-9051-525 Standard 04.01 April 2002

Figure 9-1 Processor allocations

Trunk provisioning rules

The STM-1 bearer supports 63 VC12 containers, equivalent to a total of 1953trunks (63 x 31 channels).

The DMS-100 MMP switch is limited to supporting 58,000 ISUP trunks, theequivalent of 30 SPMs, unless external routers are deployed.

Echo cancellation is available for ETSI ISUP V1 and V2, German ISUP, UKISUP, and IUP (formerly BTUP).

C-side connectivity

The unit is connected to the switch by up to four DS512 links providingenough bandwidth to the ENET to allow for a full STM-1 payload plusmessaging between the SPM and CM, without blocking.

This is the headroom provided for trafficfluctuations in order to maintain therequired Grade of Service. Preset to30%.

Buffer

pre-defined

Call Processing

remainder

Idle Occupancy

measured

This is the remaining processor timeavailable for call processing, that is, callprocessing = 100% - idle occupancy % -buffer %. It is recommended that nomore than 80% of the available callprocessing time is engineered. Thispractice allows changes in trafficprofiles or the loading of characteristicswithout re-engineering.

This is the processor time consumed bybackground processes (maintainingintegrity, channel supervision,messaging, maintenance and so on) andis measured when no calls are beingmade.

Capacity and Performance Engineering 9-3


Calculating DSP and VSP RM requirementsOne of the main advantages of SPM over XPM is its flexibility. Thisflexibility is achieved by the number (up to 26) and diversity of optionalresource modules (RMs). Each RM has a finite capacity; therefore the abilityof an SPM to meet the performance expectations is affected by the RMprofile, that is, the mix of RMs plugged into the SPM.

The SPM provides several types of service using the DSP and VSP ResourceModules:

• tone synthesizers - DSP

• continuity tone receivers (CoT) - DSP

• DTMF tone receivers with dial tone generation (DTMF) - DSP

• service test application (STA) - DSP

• echo cancellation (ECAN) - VSP

Each DSP resource module provides nine DSP islands, each capable ofsupporting one of the following:

• 255 circuits with tone synthesizers

• 80 circuits with continuity tone receivers

• 64 circuits with DTMF receivers

• one circuit with STA

Each VSP resource module provides ten turbo DSP islands, each supporting amaximum of 26 channels for echo cancellation.

Note: The ECM does not require a fixed number of DSPs per customer permarket.

To calculate the number of circuits required for each service, and hence thenumber of islands, the user must calculate the expected amount of traffic usingeach service, and then adjust the figures to achieve a specified Grade ofService.


297-9051-525 Standard 04.01 April 2002

There are different methods for calculating the traffic presented for eachservice. The calculations must be made for each trunk type:

• Tone synthesizers

Traffic =(%incoming calls requiring call progress tones × SHTp+ %incoming calls requiring audible ringing × SHTr)× #trks × trk.occ. × % calls incoming ÷ CHT

where SHTx is the service hold time for the appropriate service.

• Continuity tone receivers

Traffic =%outgoing calls requiring CoT× #trks × trk.occ. × %calls outgoing × SHTc ÷ CHT

• DTMF

Traffic =(%DTMF calls with DTMF for part of call × SHTd+ %DTMF calls with DTMF for whole call × CHT)× #trks × trk.occ. × %calls incoming

• Service Test Application

For STA, it is only necessary to know the total number of trunks withECAN and the number of tests per trunk per hour. One STA island cancomplete 1953 tests per hour (that is, it can support a full SPM with 100%ECAN if only one test per trunk per hour is required). Therefore thefollowing calculation, rounded up, gives the STA value:

%trunks with ECAN × #tests per trk per hr × #trks ÷ 1953

• Echo Cancellation

For ECAN, an island can support 26 circuits. Therefore the followingcalculation, rounded up, gives the ECAN value:

%trks with ECAN × #trks ÷ 26



Example

This example shows how to calculate the number of DSP islands required forthe following configuration:

Tone synthesizers:

Traffic = (5s × 20% + 20s × 80%) × 1920 × 0.8 × 60% / 120s= 130.56 Erlangswhich requires 165 circuits for 0.001 GoS= 1 DSP island.

Continuity tone receivers:

Traffic = 5s × 10% × 1920 × 0.8 × 40% ÷ 120s= 2.56 Erlangswhich requires 10 circuits for 0.001 GoS= 1 DSP island.

DTMF:

Traffic = (20s × 10% + 120s × 90%) × 1920 × 60% × 0.8 × 60% ÷ 120s= 506.88 Erlangswhich requires 562 circuits for 0.001 GoS= 9 DSP islands.

Characteristic Value

Number of trunks 1920

Average call hold time 120 second

Trunk occupancy 0.8

Incoming calls 60%

Incoming calls requiring call progress tones 20% (5-second hold time)

Calls requiring audible ringing 80% (20-second hold time)

Trunks requiring DTMF 60% (20-second hold time)

Outgoing calls requiring COT 10% (5-second hold time)

Trunks with ECAN 10% (60 tests per trunk per hour)

Grade of Service 0.001


297-9051-525 Standard 04.01 April 2002

STA:

= 1920 × 10% × 1 ÷ 1953 = 0.098= 1 island

ECAN:

= 1920 × 10% ÷ 26 = 7.38= 8 islands

Total number of islands:

= 17 DSPi × (2 + 1spare DSP RMs) + 8 tDSPi × (1 + 1 spare VSP RM)

The provisioning of individual DSP islands onboard each VSP and DSP RMis left up to the operating company’s customer, since the trunk signallingservice mix must be matched to the needs of the individual tandem office. Thefollowing example shows how the DSP islands can be provisioned.

Other performance variablesOne of the main advantages of SPM over XPM is its flexibility. Thisflexibility is achieved by the number (up to 26) and diversity of optionalresource modules (RM). Each RM has a finite capacity; therefore the abilityof an SPM to meet the performance expectations is affected by the RMprofile, that is, the mix of RMs plugged into the SPM.

DSP RM TONESYNDTMF +DT COT STA

Totalislands

1 1 island255 ccts.

5 islands320 ccts.

0 islands0 ccts.

3 islands3 ccts.

9

2 0 4 islands256 ccts.

1 island80 ccts.

3 islands3 ccts

8

3 (spare) 0 0 0 0 0

Totals:(unspared)

1 island255 ccts.

9 islands576 ccts.

1 island80 ccts.

6 islands6 ccts

17

VSP RM ECAN

1 8 islands 8



To test degradation, a standard configuration is needed. This will enable thepercentage capacity degradation per release to be accurately measured. Therecommended standard configuration is as follows:

• 10% ECAN (that is, 10% of measured calls have ECAN switched on;requires two VSPs)

• 10% COT, 10% DTMF (requires three DSPs)

Testing is required on 100% ISUP, 100% IUP and 50% ISUP/IUP.


297-9051-525 Standard 04.01 April 2002


10-1

10 Signaling requirements

The SPM system supports the following types of signaling:

• CCS7 signaling via channelized and non-channelized access

• CCS7 MTP routing using internal routers

• associated and quasi-associated signaling

• digit processing using enbloc or overlap signaling

The following paragraphs give details.

CCS7 signalingThe CCS7 link interface unit (LIU7) provides the hardware interface betweena DMS-100 switch and a CCS7 network. It allows signaling information topass between the switch and the CCS7 network. Prior to channelized access,the regular DS0 LIU7s connected via a channel bank (MUX) to gain access toa PCM30 span. Channelized access introduced a new interface card, theNetwork Interface Unit (NIU). The NIU allows signaling information to reachthe LIU7 without the need for an external MUX. The SPM system operateswith both channelized and non-channelized access.

SpecconnThe SPM system does not support Specconn. If non-channelized access isused, the physical carriers for the bearer and signaling channels must beseparated so that the two components enter the DMS-100 switch as follows:

• only the bearer channels enter via the SPM

• the signaling channels enter using an E1 connection to the LIU via a MUX

10-2 Signaling requirements

297-9051-525 Standard 04.01 April 2002

Monitoring CCS7 linksThe Digital Test Application provides a mechanism to monitor individualCCS7 (Common Channel Signaling) links and digital voice trunks.Monitoring refers to accessing a trunk that has a trunk-to-trunk call connected.

Digital monitoring is controlled through an existing DMS MAP screen andrequires a PDTC (PCM30 Digital Trunk Controller) equipped with a NT6X55PEC (Product Equipment Code) connected via a jack trunk. Monitoring occursby tapping into the link between the two trunks at the ENET. Monitoring of thetrunk is performed via Digital Test Equipment (DTE).

The following four commands allow various forms of trunk monitoring:

• MONPOST provides the connection between the incoming path of theposted trunk and the outgoing path of the digital jack ended trunk.

• MONLINK provides the connection between the incoming path of thelinked trunk and the outgoing path of the digital jack ended trunk.

• MONBOTH enables the user to listen to incoming transmission of theposted trunk and incoming transmission of the linked trunk.

• MONTALK establishes a 3-party conference circuit connection betweenthe posted trunk, the linked trunk and the headset of the TTP. Thiscommand is only available for analog monitoring.

CCS7 MTP routingThere are currently two implementations of the MTP router on the DMSswitch: internal routing and external routing (although the switch cannotsupport both implementations at the same time). The DMS-100 switchcurrently supports only internal routing. The SPM system also supports MTProuting using internal routers.

Note: External routing is used in the high-capacity IEC switches in NorthAmerica and is not currently a requirement in the E1 market.

Associated and quasi-associated signalingAssociated signaling occurs where the same physical topology carries both thetraffic and the related signaling information. Quasi-associated signalingoccurs where there is no direct physical connection between two CCS7signaling points (SP). The physical connection is made via one or moresignaling transfer points (STP). The SPM system supports associated signalingand quasi-associated signaling.

Digit processingThe SPM system supports both enbloc and overlap signaling on ETSI ISUPand IUP (formerly BTUP). This includes full overlap functionality.

Signaling requirements 10-3


10-4 Signaling requirements

297-9051-525 Standard 04.01 April 2002


11-1

11 Capacity information

See Chapter 9 for all capacity information and performance data.

11-2 Capacity information

297-9051-525 Standard 04.01 April 2002


V-1

Part VProvisioning


• Provisioning overview (Chapter 12)

• Data schema (Chapter 13)

• Service order procedures (Chapter 14)

• Datafill procedures (Chapter 15)

• Translations and routing (Chapter 16)

Part

VP

rovi

sion

ing


12-1

12 Provisioning overview

This chapter provides for the SPM as implemented on the DMS-100 switch.

Base STM-1 trunking systemFor details of the slots in which the cards should be provisioned, see theDMS-SPM Hardware Maintenance Reference Manual, 297-1771-550.

Figure 12-1 shows a simplified view of an SPM STM-1 shelf configurationprovisioned for ISUP signaling on a DMS-100 switch.

12-2 Provisioning overview

297-9051-525 Standard 04.01 April 2002

Figure 12-1 Shelf provisioning for STM-1 trunking

The following modules must always be provisioned on an STM-1 SPM shelf:

• fan units 1 to 4 (housed in the cooling unit)

• CEM 0 and CEM 1, always located in slots 7 and 8 of shelf 0

• STM-1 RMs, always located in slots 9 and 10 of shelf 0

• SIM A and SIM B, always located in the 15th slot of each shelf

DSP Resource Modules are required to provide ISUP and IUP (formerlyBTUP) signaling support. In this configuration, two DSPs are used to providethese services, and one DSP RM acts as a spare.

Filler

1

Filler

2

Filler

3

Filler

4

Filler

5

Filler

6 7 8

Filler

1

Filler

2

Filler

3

Filler

4

Filler

5

Filler

6

CEM0

7

CEM1

8

9

DSP

10

DSP

11

Filler

12

Filler

13

Filler

14

SIMB

15

STM1

9

STM1

10

Filler

11

Filler

12

Filler

13

Filler

14

SIMA

15

Shelf 0

Shelf 1

Cooling Unit

Fan 1 Fan 2 Fan 3 Fan 4

Air filter tray

Filler

Filler

DDP

Provisioning overview 12-3


The DSP RMs provide the following services:

• tone synthesizers (TONESYN)

• continuity tone receivers (COT)

• DTMF tone receivers with dial tone generation (DTMF+DT)

• service test application (STA)

All unused slots must be equipped with filler modules to maintain EMIintegrity and shelf airflow patterns.

Each DSP RM provides nine DSP islands. Table 12-1 shows the number ofDS0 channels that can be serviced simultaneously per island for any givenfunction.

Table 12-2 shows how the DSP services are distributed amongst the DSP RMs.The numbers in brackets indicate the numbers of DSP islands on the indicatedDSP RM assigned to each function.

Note: These numbers are for guidance only and are based on traffic patternapproximations. Customers must choose suitable values for each office.

Table 12-1 DSP RM capacities

Application (function) Quantity per DSPI

Tone synthesizer 255

Continuity tone transceiver 80

DTMF receiver 64

Service test application 1

Table 12-2 DSP services

DSP RM TONESYNDTMF +DT COT STA

Totalislands

1 (1) = 255 (5) = 320 0 (3) 3 9

2 0 (4) = 256 (1) = 80 (3) 3 8

3 (spare) 0 0 0 0 0

Totals:(unspared)

255 576 80 6 17


297-9051-525 Standard 04.01 April 2002

The service provisioning requirements are derived from card sparingconsiderations, taking into account the assumptions regarding trafficcharacteristics shown in Table 12-3.

Table 12-4 shows the DSP resources required, calculated using the trafficcharacteristics and formulae/tables published in Engineering ChangeMemorandums 590 and 597.

Note: Customers who offer Intelligent Networks capability (IN) mayrequire more than a 2+1 DSP configuration. This is because re-originationcapability requires a DTMF resource for the whole duration of the call. Thefollowing table shows how many DSP RMs are required given thepercentage of IN calls which require re-origination capability for the wholeduration of the call.

Echo canceller provisioningEcho cancellers are provisionable from 0% to 100% of trunks. An operatingcompany’s customers can decide which provisioning model works best foreach office. The echo cancellation function is provided by equipping VSPresource modules.

Table 12-3 Traffic characteristics

Call attempt rate 16 CA/s (margin)

Average call holding time 120 s

Traffic density 1920 Erlang (53 CCS)

Percent origination 60%

Origins requiring call progress tones 20% 5 s hold

Calls requiring audible ringing 80% 20 s hold

Calls requiring DTMF 10% 20 s hold

Outgoing calls requiring COT 10% 5 s hold

Table 12-4 DSP requirements

Percentage of calls requiringre-origination for 100% of the call Total number of DSPs required

30% 2+1

60% 2+1

100% 3+1

Provisioning overview 12-5


Each VSP RM provides ten turbo DSP islands (tDSPI). 26 DS0 channels canbe serviced simultaneously per tDSPI for the echo cancellation (ECAN)function.

Table 12-5 shows the possible VSP provisioning levels. The sparing ratio isshown in brackets.

Figure 12-2 shows a view of an STM-1 trunking SPM equipped with 100%echo cancellation.

Table 12-5 VSP provisioning levels

VSP RMs Maximum ECANs % of 1953

2 (1:1) 260 13.3%

3 (2:1) 520 26.6%

4 (3:1) 780 39.9%

5 (4:1) 1040 52%

6 (5:1) 1300 66.6%

7 (6:1) 1560 79.9%

8 (7:1) 1820 93.2%

9 (8:1) 2080 100%


297-9051-525 Standard 04.01 April 2002

Figure 12-2 STM-1 SPM shelf layout with 100% echo cancellation, 100% DTMF, 0% PTS

The configuration shows that eight VSP RMs are required to provide1953-channel coverage plus one spare for 8:1 redundancy provisioning. Theprovisioning of individual DSP islands onboard each VSP and DSP RM is leftup to the operating company’s customer, since the trunk signaling service mixmust be matched to the needs of the individual tandem office.

DatafillDatafill tables are modified to allow for STM-1 carriers and trunks. Fordetails of the changes, see Chapter 13, Data schema. For details of how todatafill the tables, see the DMS-100 MMP Customer Data Schema,297-9051-351.

Filler

1

VSP

2

VSP

3

VSP

4 5

DSP

6

DSP

7

VSP

8

Filler

1

Filler

2 3 4 5 6

CEM0

7

CEM1

8

VSP

9 10

DSP

11

Filler

12

Filler

13

VSP

14

SIMB

15

STM1

9

STM1

10 11

VSP

12 13 14

SIMA

15

Shelf 0

Shelf 1

Cooling Unit

Fan 1 Fan 2 Fan 3 Fan 4

Air filter tray

VSP

VSP

Filler

Filler

Filler

Filler

Filler

Filler

Filler


13-1

13 Data schema

This chapter lists the tables that have been modified, with STM-1 changes, atISN04 (TDM). For details of the changes, see DMS-100 MMP Customer DataSchema Reference Manual, 297-9051-351. (The bracketed numbers relate tothe feature number for the change.)

• MNHSCARR (59033790)

• MNPRTGRP (59033790)

For details of how to datafill the tables, see Chapter 15, Datafill procedures.

Table MNHSCARR


Table MNHSCARR was modified to provide changes to high speed carrierSTM1M, namely eight new Automatic Protection Switching failures, anda timing indicator.

Table MNPRTGRP


Table MNPRTGRP was modified to provide changes to protection groupswitching support, namely protection switching mode (revertive andnon-revertive) and switching direction (unidirectional, bidirectionalcompatible, bidirectional optimized, duration of switching time, regionalindication of switch direction).

13-2 Data schema

297-9051-525 Standard 04.01 April 2002


14-1

14 Service order procedures

The SPM system does not use service orders.

14-2 Service order procedures

297-9051-525 Standard 04.01 April 2002


15-1

15 Datafill procedures

This chapter lists the tables affected by SPM changes that are new or changedin ISN04 (TDM):

• MNCKTPAK (59033790) - changed

• MNPRTGRP (59033790) - changed

The numbers in brackets represent the feature number associated with thechange.

For details of the datafill procedures for tables relevant to the SPM, see theDMS-100 MMP Customer Data Schema Reference Manual, 297-9051-351.This includes the following tables:

• ENIMLAST

• FEATCNTL

• LTDATA

• LTDEF

• MNATMCON

• MNCKTPAK

• MNHSCARR

• MNLINK

• MNNODE

• MNPRIIID

• MNPRTGRP

• MNSHELF

• OFCENG

• SPMECAN

• SPMCHAST

• SPMTIDMP

15-2 Datafill procedures

297-9051-525 Standard 04.01 April 2002

• TRKMEM

• TRKSGRP


16-1

16 Translations and routing

The SPM system does not affect translations.

16-2 Translations and routing

297-9051-525 Standard 04.01 April 2002


Part VI-1

Part VIBilling


• Billing structures and modules (Chapter 17)

Par

tVI

Bill

ing


17-1

17 Billing structures and modules

The SPM system does not affect any billing functionality (AMA, CDR, orSMDR).

17-2 Billing structures and modules

297-9051-525 Standard 04.01 April 2002


Part VII-1

Part VIIOA&M

This part contains the following chapter:

• Translation verification tool (Chapter 18)

• CI commands (Chapter 19)

• Operational measurements (Chapter 20)

• Administrative log reports (Chapter 21)

• Maintenance (Chapter 22)

Part

VII

OA

&M


18-1

18 Translation verification tool

The SPM system does not affect the translation verification tool.

18-2 Translation verification tool

297-9051-525 Standard 04.01 April 2002


19-1

19 CI commands

The command interpreter (CI) commands that are new or changed in ISN04(TDM) are listed below. (The bracketed numbers relate to the feature numberassociated with the change.)

• QSCONN (59022028)

This command is extended to support the SPM allowing the operator toquery the state of individual connections where at least one of theendpoints terminates on an SPM STM-1 64Kbit/s timeslot.

The SPECCONN query command QSCONN is used, as suggests, todisplay the SPECCONN connection data for a specific peripheral port orall segments associated with a particular endpoint.

• CONNECT (59028292)

The CONNECT command is enhanced to support the SPM and allow themonitoring equipment to connect (and disconnect) to (from) the PRID-channel to the monitoring equipment. The CONNECT command alsoallows Digital Test Access (DTA) connections to be verified and released.

CONNECT is a PRADCH level command. PRADCH level commands areused to maintain integrated services digital network (ISDN) digital trunkcontroller (DTC) B-channels and D-channels.

The command interpreter (CI) commands that are new or changed in ISN04(TDM) are listed below. (The bracketed numbers relate to the feature numberassociated with the change.)

• CLEAR (59033790)

This command clears all commands for STM-1 resource modules. It clearsthe lockout, force switch, manual switch and exercise commands. It is notindicated on ’K bytes’ but a Do Not Revert (DNR) request may be issueddependent upon the mode and operation:

— In unidirectional or bidirectional non-revertive mode

If a force switch from Working section to Protection section is activeand the clear command is issued, a DNR request will be issued. But if

19-2 CI commands

297-9051-525 Standard 04.01 April 2002

a force switch from the Protection section to the Working section isactive a No Request will be issued.

— In unidirectional or bidirectional revertive mode

When a clear command is issued, the system will start a switch back tothe Working section. Note that if a clear command is applied when aWait To Restore (WTR) is already sent across ’K bytes’ it will clear theWTR and the system will switch back to the Working section.

Note: When a clear command is issued, the alarm raised, for when theforce, manual or lockout command was issued, should be cleared

• EXERCISE (59033790)

This command exercises the Multiplexer Section Protection (MSP) optionfor STM-1 resource modules.

This command is only available for a bidirectional compatible mode. If afailure or another command is active, the exercise command will berejected. It initiates a switch but does not perform any switching action.

This command will be disabled (but visible) for all resource modules typesexcept STM. In such cases the HMI (Human Machine Interface) will sendan error reply: ‘Functionality not supported’. If the command fails, e.g. ahigher priority request is already activated, the HMI will send a replygiving a precise reason.

• LOCKOUT (59033790)

The lockout command is used differently dependent upon the protocol:

— Optimized protocol

The lockout command, which has the highest priority, freezes theposition of the section selector.

• Other protocols

The lockout command, which has the highest priority, prevents switchingto the Protection section. Therefore signal failure only occurs on theWorking section and as a result, the system will not switch to theProtection section. If the Protection section is active, the system will

WARNING

The lockout information is not transmitted to the Far endtherefore, if not applied identically to both Local and Farend, the system will end up in an unprotected situation.

CI commands 19-3


switch back to the Working section even if a signal failure is raised againstthe Working section.

For all protocols, a card failure or card fault will have the same priority as asignal fail on the corresponding section. For example, for bidirectionalcompatible protocol, if the Working card fails and a ‘Lockout of Protection’ isactive, the lockout command will be applied and the system will stay on theWorking section.

This command will be disabled (but visible) for all resource modules typesexcept STM. In such cases the HMI (Human Machine Interface) will send anerror reply: "Functionality not supported”. If the command fails, e.g. a higherpriority request is already activated, the HMI will send a reply giving a precisereason.

For details of CI commands relevant to the SPM, see the DMS-SpectrumPeripheral Module Commands Reference Manual, 297-1771-819. Thefollowing sections summarize the CI facilities available.

SPM screenThe SPM MAP screen gives a summary of an entire SPM. It shows all themodules in the selected SPM, together with their slot numbers, activity statusand service state. From the SPM screen, the user can select one or moredevices (for example, CEM, DSP, STM, or VSP). The individual MAP screensdisplay the characteristics of the selected device, and the commands availablefor controlling the device.

The full list of SPM commands, with their function, is as follows:

• Bsy (busy) - puts the selected device into a manual out-of-service state

• Clear - clears the lockout, force switch, manual switch and exercisecommands for STM-1 resource modules.

• Disp - displays all carriers that correspond to a given condition

• Exercise - exercises the Multiplexer Section Protection (MSP) option forSTM-1 resource modules.

• ListAlm - displays detailed alarm information

• ListRes - displays the resources provided by the specified device (DSP)

• ListSet - lists the items in the Post set

• LoadMod - manually downloads a specific load file to the selected device

• Lockout - freezes the position of the section selector (for optimizedprotocol) or freezes the position of the section selector (for non-optimizedprotocol). The lockout command, has the highest priority of the three MSPcommands (Clear, Exercise and Lockout)

19-4 CI commands

297-9051-525 Standard 04.01 April 2002

• Next - selects the next RM in the Post set

• OffL - puts the selected device into an offline state

• Post - displays carriers based on a condition or a peripheral type

• Prot - carries out a manual protection switch

• QueryMod - manually queries local/CM information on the selecteddevice

• QueryPM - displays miscellaneous information about the SPM

• Quit - quits the current MAP level

• Rts (return to service) - manually brings the selected device from anout-of-service state to in-service

• Select - selects a specified module (circuit pack)

• Tst - runs manual in-service and out-of-service diagnostics on the selecteddevice

• Trnsl - displays the C-side link information for the selected device

The following sections list the commands available for controlling theindividual devices.

SPM commands (SPMDIR directory)The SPM level commands are as follows:

• Disp

• ListAlm

• ListRes

• ListSet

• Next

• Post

• QueryPM

• Quit

• Select

• Trnsl

CEM commands (SPMCEMDIR directory)The CEM level commands are as follows:

• Bsy

• ListAlm

• ListSet

CI commands 19-5


• LoadMod

• Next

• OffL

• Prot

• QueryMod

• Quit

• Rts

• Select

• Tst

• Trnsl

Note: If the RTS command is used when both the CEMs are in theMANB state, the STM-1 RM is subject to the automatic SYSB recoveryprocess (see Chapter 3).

DSP commands (SPMDSPDIR directory)The DSP level commands are as follows:

• Bsy

• ListAlm

• ListRes

• ListSet

• LoadMod

• Next

• OffL

• Prot

• QueryMod

• Quit

• Rts

• Select

• Tst

STM-1 commandsThe STM-1 level commands are as follows:

• Bsy

• ListAlm

19-6 CI commands

297-9051-525 Standard 04.01 April 2002

• ListSet

• LoadMod

• Next

• OffL

• Prot

• QueryMod

• Quit

• Rts

• Select

• Tst

• Clear

• Exercise

• Lockout

VSP commands (SPMVSP directory)The VSP level commands are as follows:

• Bsy

• ListAlm

• ListRes

• ListSet

• LoadMod

• Next

• OffL

• Prot

• QueryMod

• Quit

• Rts

• Select

• Tst

Carrier commands (CARRIER directory)The CARRIER screen displays carrier information. The screen has two levels:POST level and DISPLAY level.

CI commands 19-7


The POST level allows the user to display carriers based on a condition or aperipheral type. The POST level commands are as follows:

• Bsy (busy) - puts the selected device into a manual out-of-service state

• Detail - displays additional details of one of the posted carriers

• Disp - displays all carriers that correspond to a given condition.

• ListAlm - displays detailed alarm information

• Loop - puts the specified carrier in a given loopback state


• OffL - puts the selected device into an offline state

• Perfmon - displays the performance monitoring screen



• Rts (return to service) - manually brings the selected device from anout-of-service state to in-service

• Tst - runs manual in-service and out-of-service diagnostics on the selecteddevice

The DISPLAY level allows the user to display all carriers in a specified state.The DISPLAY level commands are as follows:

• Disp - displays all carriers that correspond to a given condition




Carrier maintenance commands (CARRUTIL directory)The CARRUTIL level gives the user access to a number of carrier monitoringutilities. The commands are non-menu and support Spectrum carriers only.

The CARRUTIL level commands are as follows:

• DumpHist - retrieves and displays the historical data for all carriers or fora selected carrier

• GetHist - retrieves historical performance monitoring data

• Help - provides information about the CARRUTIL commands

• ListHist - displays the historical data retrieved by the GetHist command

• Quit - quits the CARRUTIL MAP level

• SetCarr - specifies the carrier to be monitored (placed in context)

19-8 CI commands

297-9051-525 Standard 04.01 April 2002

Trunk maintenance commands (SPMTKCNV directory)The MAP display at the SPMTKCNV level now accommodates seven extratime slots in both display positions. This modification is to allow display of the31 time slots of a PCM30 carrier on the SPM.

Figure 19-1 shows an example MAP display at the SPMTKCNV level fortrunk DTC 0 17.

Figure 19-1 Example MAP display: SPMTKCNV level

Internally, changes to the CONVERT command allow for the conversion oftrunks to and from PCM30 carriers. The SPMTKCNV MAP level can handlethe following conversion types:

• PDTC PCM30 carrier to and from SPM PCM30 carrier.

• PDTC PCM30 carrier to and from SPM DS1 carrier.

The SPMTKCNV level commands are as follows:

• Bsy (busy) - busies the circuit in the control position

• Convert - converts the posted trunk to the trunk member specified by thecommand parameters.

• CvCarr - moves trunks from the origination carrier into free slots in thesame position on the destination carrier

• Display - displays information about time slot occupancy on a given carrier

• Hold - holds the posted trunk


• Post - posts one or more circuits for maintenance


• Rts (return to service) - returns to service the circuit in the control position

CKT TYPE PM NO. COM LANG STA S R DOT TE RESULT2W S7 S7 DTC 0 17 24 SPMIC 0 IDL0 Quit2 Post345 Bsy6 Rts7 CARR1: DTC 0 17 (3 trk) CARR2 SPM 1 4 (30 slot)9 1234567890123456789012345678901 -> 123456789012345678901234567890110 **-*--------------------xxxxxxx *------------------------------11 Hold12 Next13 ...

CI commands 19-9


• Swap - reverses the direction of the displayed arrow and exchanges theorigination and destination information

• Undo - reverses the action of the last Convert or CvCarr command

19-10 CI commands

297-9051-525 Standard 04.01 April 2002


20-1

20 Operational measurements

The SPM system does not use operational measurements (OM) to describe theperipheral.

For details of OMs relevant to the SPM, see the DMS100 MMP OperationalMeasurements Reference Manual, 297-9051-814. This includes the followingOMs:

• DSPRMAN

The use of tone synthesizer BRATONE (59018854) is recorded in groupDSPRMAN.

• ECANRMAN

20-2 Operational measurements

297-9051-525 Standard 04.01 April 2002


21-1

21 Administrative log reports

This chapter lists the logs that are new or changed in ISN04 (TDM):

• Information-only logs (MMP16)

There are a number of logs that get updated by Special Connectionsincluding:

— PM231, PM232, PM233 and PM234

Used by Special Connections audit process.

— PM236

Used for logging changes in Integrity status.

No changes are made to the format of these logs but entries are made tothese logs for Special Connections residing on an SPM.

• Carrier failure (STM1M section)

The following STM1M carrier failures may occur for MSP (MultiplexSection Protection):

— APSLCK

— APSFC

— APSMAN

— APSFEPLF

— APSAM

— APSMM

— APSCHM

— APSIC

CARR310 is used to display MSP specific logs associated with the aboveSTM1M carrier failures.

CARR300 is used to display the cleared MSP specific logs associated withthe above STM1M carrier failures.

21-2 Administrative log reports

297-9051-525 Standard 04.01 April 2002

For details of log reports which report failure events in the SPM system, seethe DMS-100 MMP Log Report Reference Manual, 297-9051-840.


22-1

22 Maintenance

For details of maintenance procedures, see the following documents:

• DMS-SPM Hardware Maintenance Reference Manual, 297-1771-550

• DMS-100 MMP Alarm Clearing and Performance MonitoringProcedures, 297-9051-543

• DMS-100 MMP Trouble Locating and Clearing Procedures,297-9051-544

• DMS-100 MMP Recovery Procedures, 297-9051-545

• DMS-100 MMP Routine Maintenance Procedures, 297-9051-546

• DMS-100 MMP Card Replacement Procedures, 297-9051-547

22-2 Maintenance

297-9051-525 Standard 04.01 April 2002


Part VIII-1

Part VIIIRequirements


• Product support (Chapter 23)

• Customer acceptance (Chapter 24)

Part

VIII

Req

uire

men

ts


23-1

23 Product support

RecoveryFor details of the SPM recovery system, see the DMS-100 MMP RecoveryProcedures, 297-9051-545.

SupportSupport for this product is supplied by Nortel Networks Global Customer CareSupport (GCCS) group and the customer is requested to refer to any specificWarranty and Enhanced Support Plan (ESP) agreements that exist betweenthemselves and Nortel Networks.

Training

• Course title: SPM STM-1 Operations and Maintenance

• Number: 05304

This is a single trainer lead training package, which covers the Spectrumperipheral module (SPM) system overview, hardware description, table datafilland MAP interface.

Course objectivesThe course objectives are as follows:

• Identify the SPM system requirements (hardware and software).

• Identify the functions of the different SPM components.

• Understand the STM-1 frame structure.

• Explain how E1 transmission components map into an STM-1 frame.

• Interface with the SPM using the Maintenance and AdministrationPosition Command Interpreter (MAPCI).

• Datafill the Spectrum-related software tables.

• Identify the relationship between table MNHSCARR and the STM-1components.

23-2 Product support

297-9051-525 Standard 04.01 April 2002

OverviewThe course covers the following topics:

• Introduction to the SPM

— system overview

— hardware

— software

• Hardware module description

— physical installation

— hardware units

— system architecture

— system fault indications

• SPM data tables - function, datafill and use

— MNCKTPAK

— MNHSCARR

— MNLINK

— MNNODE

— MNPRTGRP

— MNSHELF

— FEATCNTRL

— SPMECAN

• SPM MAPCI interfaces

— MAP hierarchy and screens

— CEM, DSP and STM-1 MAP screen usage

— Protection MAP screen usage

— SPM carrier hierarchy and carrier MAP screen usage

— Performance Monitoring system and MAP screen usage

• SPM log interface

— Introduction to Spectrum logs

— carrier logs

— SPM logs

— ENET logs

— PRSM logs

Product support 23-3


PrerequisitesTrainees attending the SPM STM-1 Operations and Maintenance course musthave a technical working knowledge of the following:

• DMS-100 switch operation and terminology

• use of the MAP interface and table editor

A working understanding of SDH and STM-1 is also an advantage.

DocumentationThe documentation provided to support the SPM system is listed in theReferences section.

23-4 Product support

297-9051-525 Standard 04.01 April 2002


24-1

24 Customer acceptance

AcceptanceCustomer acceptance is generally the result of a successful Verification Office(VO) test at the customer’s premises. A team consisting of Nortel Networksand customer staff evaluates product performance by executing a series of testcases and an in-service trial. Exceptions to the expected results aredocumented and prioritized through CSRs. Nortel Networks corrects seriousfaults prior to completion of the VO test. Correction of minor faults may bedeferred to a future release.

Regulatory approvals apply to hardware products but are not required forsoftware.

24-2 Customer acceptance

297-9051-525 Standard 04.01 April 2002


Part IX-1

Part IXReference information

This part contains the following sections:

• List of terms

• References

• Index

Par

tIX

Ref

eren

cein

form

atio

n


A-1

List of terms

ANSIAmerican National Standards Institute

APSautomatic protection switching

ATMasynchronous transfer mode

BRISCB-type reduced instruction set computer

BTUPBritish telephone user part

C7see CCS7

CASEcomputer aided software engineering

CCIScommon channel interoffice signalling

CCITTComite Consultatif International Telegraphique et Telephonique

CCS7common channel signalling #7

CCTScircuits

CECall Event

A-2 List of terms

297-9051-525 Standard 04.01 April 2002

CEMcommon equipment module

CHTCall Holding Time

CIcommand interpreter

CMcomputing module

COTcontinuity tone

CPUcentral processor unit

CSPcommon services platform

DMSdigital multiplex switch

DRCdynamic routing control

DS0digital signal level 0

DSPdigital signal processor or processing

DSPRdigital signal processing resource

DTCdigital trunk controller

DTCIdigital trunk controller (ISDN)

DTCOdigital trunk controller offshore

DTCOIdigital trunk controller offshore (ISDN)

List of terms A-3


DTMFdual-tone multi-frequency

DXCdigital cross-connect

E12.048 Mbit/s rate used by European CEPT carriers

EBIeven bit inversion

ECANecho canceller

EMIelectromagnetic interference

ENETenhanced network (component of DMS)

ETSIEuropean Telecommunications Standards Institute

FAMFinal Address Message

GoSGrade of Service

IAMInitial Address Message

IECinterLATA exchange carrier

IMTinter-machine trunk

INintelligent network

ISDNintegrated services digital network

ISUPISDN signalling user part

A-4 List of terms

297-9051-525 Standard 04.01 April 2002

ITU-TInternational Telecommunication Union- Telecommunication Standardization Sector

IUPinterconnect user part

KLMpayload position numbering scheme

LGCline group controller

LIUlink interface unit

LIU7link interface unit for CCS7

LPPlink peripheral processor

LTEline terminating equipment

MAPmaintenance and administration position

MCCSmechanized calling card service

MCImalicious call identification

MDSmodular documentation system

MFmulti-frequency

MMPmulti-market platform

MSmessage switch

List of terms A-5


MSPmessage switch processor

MTPmessage transfer part

MUXmultiplexer

OAMoperations, administration and maintenance

OAM&Poperations, administration, maintenance and provisioning

OC-3optical carrier 3

OMoperational measurement

OORoperator override

PCMpulse-code modulation

PDTCperipheral digital trunk controller

PECproduct equipment code

PMperipheral module

PRIprimary rate interface

PTEpath terminating equipment

QUICCquad integrated communications controller

RMresource module, or resource maintenance

A-6 List of terms

297-9051-525 Standard 04.01 April 2002

RTSreturn to service

SAMSubsequent Address Message

SDsignal degrade

SDHsynchronous digital hierarchy

SFsignal fail

SIMshelf interface module

SOCsoftware optionality control

SONETsynchronous optical network

SPMSpectrum peripheral module

STAservice test application

STM-1synchronous transfer mode 1

STRspecial tone receiver

SWACTswitch of activity

TDMtime division multiplexing

TONESYNtone synthesizer

TUtributary unit

List of terms A-7


UTRuniversal tone receiver

VC12virtual container level 12

VC4virtual container level 4

VOverification office

VSPvoice service processor

XPMextended peripheral module

A-8 List of terms

297-9051-525 Standard 04.01 April 2002


B-1

References

Base Product Description (BAS-PD-xxx)

DMS-SPM Hardware Maintenance Reference Manual, 297-1771-550

DMS-100 International Spectrum Peripheral Module Release Document, 297-1771-597

DMS-Spectrum Peripheral Module Commands Reference Manual, 297-1771-819

DMS-100 MMP Product Documentation Directory, 297-9051-001

DMS-100 MMP Customer Data Schema Reference Manual, 297-9051-351

DMS-100 MMP Alarm Clearing and Performance Monitoring Procedures, 297-9051-543

DMS-100 MMP Trouble Locating and Clearing Procedures, 297-9051-544

DMS-100 MMP Recovery Procedures, 297-9051-545

DMS-100 MMP Routine Maintenance Procedures, 297-9051-546

DMS-100 MMP Card Replacement Procedures, 297-9051-547

DMS-100 MMP Operational Measurements Reference Manual, 297-9051-814

DMS-100 MMP Log Report Reference Manual, 297-9051-840

ITU Intelligent Networks System Guide

STM-1 RM Applications Diagnostics

ToneSyn Application Functional Description

B-2 References

297-9051-525 Standard 04.01 April 2002

3

and up

AAbout this document xiacceptance 24-1Administrative log reports 21-1alarms 3-20Associated signaling 10-2

BBelgium ISUP 2-9benefits 1-5Billing 17-1Billing structures and modules 17-1Bit inversion 3-22Brazilian ISUP 2-9

Ccall processing services 3-8call processing services, IUP protocol 3-8Call timings 9-1call types and timings 9-1capacity engineering 9-1, 9-2Capacity information 11-1Carrier commands 19-6Carrier maintenance 2-9carrier maintenance 3-18Carrier maintenance commands 19-7carrier maintenance logs 3-23CCS7 signaling 10-1CEM commands 19-4CI commands 19-1Companding 3-22continuity testing 3-11customer acceptance 24-1

DData schema 13-1data schema 13-1Datafill 15-1datafill 12-6Datafill procedures 15-1Deliverables 2-1development summary 2-1Digit processing 10-2Digital Test Access 2-10documentation 23-3DSP commands 19-5DSP RM 9-3, 12-2DSPRMAN 20-1DXC 1-3

EECANRMAN 20-1Echo cancellation 2-9echo cancellation 3-9echo canceller provisioning 12-4emergency calls 3-24ENET 1-4error handling 3-23even bit inversion, SPM/ENET interface 3-23

FFeature interactions 5-1

4

feature interactions 5-1features - hardware 7-1features - unsupported (STM-1 RM) 7-2Figure 3-5 3-16Frame assembly 2-10functional overview 3-1

GGerman Network Protection 2-10, 3-24

HHardware 2-10, 7-1hardware - features 7-1hardware functions 7-2hardware requirements 7-1

Iidle bit pattern 3-21installation 6-1intelligent networks 3-11interworking 3-8interworking, IUP protocol 3-9ISUP 3-6Italian ISUP 2-8IUP 3-8

KKLM numbering 2-9

LLimitations 4-1limitations and restrictions 4-1log reports 21-1Logs 3-23, 21-1

MMaintenance 22-1MAP 3-11, 3-21, 19-3MAP interface enhancements 3-13MNCKTPAK 13-1MNPRTGRP 13-1MTP routing 10-2

Nnetwork protection 3-24

OOA&M VII-1OAM&P 3-11Operational measurements 20-1

Ppayload positions 3-19PCOS 3-24PDTC 1-2PEC codes 1-1performance engineering 9-1Performance monitoring 3-20performance monitoring - archival 3-20performance parameters 3-21Planning and engineering IV-1Planning for installation 6-1planning of the SPM system 6-1

5

and up

priority calls 3-24Processor allocations 9-2processor allocations 9-1product features 1-5product overview 1-1product structure 2-10Product support 23-1product support 23-1Protection 3-3Provisioning V-1, 12-1provisioning overview 12-1

QQuasi-associated signaling 10-2

Rrecovery 23-1references R-1related publications xiiiReturns To Service 3-5

SSDH 1-3SDH multiplexing and mapping 7-2Service orders 14-1service orders 14-1Shelf assembly 2-10shelf configuration 12-1Shelf provisioning 12-2Signaling 10-1Software 2-12, 8-1software description 8-1software optionality control 1-1Spanish ISUP 2-8Speccon 10-1Spectrum 1-1SPM commands 19-4SPM environment 1-2SPM in DMS-100 architecture 1-3SPM summary screen 3-14SPM/ENET interface, even bit inversion 3-23STM-1 commands 19-5STM-1 interface 3-1STM-1 RM 7-1STM-1 RM command descriptions 3-17STSB recovery process 3-5support 23-1Synchronization 1-2synchronization 3-5system engineering 9-1

Ttable size 4-2Timed Break Recall (TBR) 3-24tone detection 3-10tone generation 3-10tones 3-10tones - downloadable 2-9training 23-1Translation verification tool 18-1translation verification tool 18-1Translations 16-1

6

Translations and routing 16-1Trunk maintenance commands 19-8trunk signalling - ISUP 3-6trunk signalling - IUP 3-8TUP 2-9

Uunsupported features (STM-1 RM) 7-2

VVO test 24-1VSP commands 19-6VSP RM 9-3, 12-4

DMS-100 MMP


Customer Information AuthorityNortel NetworksConcorde RoadNorreys DriveMaidenheadBerkshire SL6 4AG, UKtelephone: (44) 1628-434463 or (44) 1628-434670

electronic mail: [email protected]: http://www.nortelnetworks.com

Copyright © 2002 Nortel Networks,All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networksand is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a need to know, andshall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degreeof care it uses to protect its own confidential information, but with no less than reasonable care. Except as expresslyauthorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design orcomponents as progress in engineering and manufacturing may warrant.

This product complies with the provisions of the Electromagnetic Compatibility (EMC) Directive (89/336/EEC), theAmending Directive (92/31/EEC), the Low Voltage Directive (73/23/EEC), the CE Marking Directive (93/68/EEC) and theTelecommunications Terminal Equipment Directive (91/263/EEC) [where the product may be deployed as a privateapparatus connected to the Public Telephone Network], and as such this product bears the CE marking in accordance withthe applicable Directives.

This product is intended for deployment in a light industrial, non-domestic environment, and complies with the relevantEMC standards for emissions and immunity. Because this is a Class A product, in a domestic environment this productmay cause radio interference. In this case, the user may be required to take adequate measures.

Changes or modification to SPM STM-1 Trunking without the express consent of Nortel Networks may void its warrantyand void the user’s authority to operate the equipment.

NORTEL NETWORKS, the NORTEL NETWORKS logo, the GLOBEMARK, “HOW THE WORLD SHARES IDEAS,UNIFIED NETWORKS, DMS, MAP, NORTEL, NORTHERN TELECOM, NT, and SUPERNODE are trademarks of NortelNetworks.

Publication number: 297-9051-525Product release: ISN04 (TDM)Document release: Standard 04.01Date: April 2002United Kingdom

dms-100 mmp spm stm-1 trunking - willow eaton...

Documents