03_N08342 Func. Descrip

REFERENCE-2.1DOI-N08342

NEC Corporation 7-1, Shiba 5-Chome, Minato-Ku, Tokyo 108-8001, JapanTEL: +81-3-3454-1111FAX: +81-3-3798-1510

TELEX: NECTOK J22686EMAIL: [email protected]

SpectralWave™

UNIVERSAL NODEWIDE BAND MANAGER

FUNCTIONAL DESCRIPTION

REFERENCE-2.1DOI-N08342

The information in this document was approved by the engineer(s) listed below,and was intended to be complete and accurate at the time of printing. However,information is subject to change.

This document contains proprietary information of NEC Corporation, and is not to be disclosed or used except in accordance with applicable agreements. Please contact NEC Corporation or the project contractor.

Copyright © 2003 by NEC CorporationAll rights reserved.

Printed in Japan

1st Edition January 2003, approved by S. Fukunaga of NEC-1ONW/1DD2nd Edition March 2003, approved by S. Fukunaga of NEC-1ONW/1DD3rd Edition June 2003, approved by S. Arai of NEC-BBN-CNW

REFERENCE-2.1DOI-N08342FUNCTIONAL DESCRIPTION

SpectralWave U-Node WBM

Contents

1. SIGNAL INTERFACE FUNCTION 1-1

1.1 Overhead Process ..............................................................................1-21.1.1 Regenerator Section (RS) ................................................................... 1-21.1.2 Multiplex Section (MS) ........................................................................ 1-41.1.3 Higher Order Path (VC-4) & Lower Order Path (VC-3) ....................... 1-61.1.4 Lower Order Path (VC-12) .................................................................. 1-91.1.5 GFP Frame Process ......................................................................... 1-11

1.1.5.1 GFP Frame Format .............................................................. 1-111.1.5.2 GFP Mapping ....................................................................... 1-12

1.2 Trace Function ..................................................................................1-131.2.1 16-Byte Mode .................................................................................... 1-141.2.2 64-Byte Mode .................................................................................... 1-141.2.3 1-Byte Mode ...................................................................................... 1-141.2.4 Trace Message Character ................................................................. 1-15

1.3 Signal Label Function ......................................................................1-161.3.1 SDH Path C2 Byte Codes ................................................................. 1-161.3.2 SDH Path V5 Byte Codes ................................................................. 1-17

2. CROSSCONNECT 2-1

2.1 Crossconnect Process Capacity ......................................................2-12.1.1 Matrix Capacity ................................................................................... 2-12.1.2 Crossconnect Configuration ................................................................ 2-2

2.2 Crossconnect Level ...........................................................................2-42.2.1 Crossconnect Termination Point ......................................................... 2-4

2.3 Crossconnect Types ..........................................................................2-52.3.1 Higher Order Path ............................................................................... 2-5

2.3.1.1 1-Way .................................................................................... 2-52.3.1.2 2-Way .................................................................................... 2-5

2.3.2 Lower Order Path ................................................................................ 2-62.3.2.1 1-Way .................................................................................... 2-62.3.2.2 2-Way .................................................................................... 2-7

Contents- i -


2.3.3 Additional Samples ............................................................................. 2-92.3.4 Idle Signal Processing ....................................................................... 2-10

2.4 Squelch Settings ..............................................................................2-112.4.1 Squelch Table ................................................................................... 2-12

2.4.1.1 Simple 2F/4F MS-SPRing .................................................... 2-12

2.5 Virtual Concatenation ......................................................................2-132.5.1 Overview ........................................................................................... 2-132.5.2 Crossconnect Levels ......................................................................... 2-132.5.3 Crossconnect .................................................................................... 2-14

2.5.3.1 GBEM/FEH Package ........................................................... 2-142.5.3.2 Crossconnection Images ..................................................... 2-15

3. PROTECTION 3-1

3.1 Overview .............................................................................................3-13.1.1 Protection Types ................................................................................. 3-13.1.2 Protection Types and Package Slots .................................................. 3-2

3.1.2.1 WBM Shelf Front View ........................................................... 3-23.1.2.2 Available Package Slots for Protections ................................ 3-3

3.2 Package Protection ............................................................................3-53.2.1 Switching Configuration ...................................................................... 3-53.2.2 Switching Mode and Switching Priority ............................................... 3-5

3.2.2.1 1+1 Package Protection Switching Priority ............................ 3-63.2.2.2 1:n Package Protection Switching Priority ............................. 3-6

3.2.3 Lockout Mode ...................................................................................... 3-63.2.4 Switching Status .................................................................................. 3-6

3.3 Line Protection ...................................................................................3-73.3.1 Switching Configuration ...................................................................... 3-73.3.2 Applicable Interface Types .................................................................. 3-73.3.3 Linear Protection ................................................................................. 3-8

3.3.3.1 Linear Protection Mode .......................................................... 3-83.3.3.2 1+1 Unidirectional Linear Protection ...................................... 3-93.3.3.3 1+1 Bidirectional Linear Protection ........................................ 3-93.3.3.4 1:1 Bidirectional Linear Protection ....................................... 3-103.3.3.5 Standby Line Access (SLA) ................................................. 3-103.3.3.6 Switching Mode ................................................................... 3-113.3.3.7 Linear Protection Switching Priority ..................................... 3-12

Contents- ii -


3.3.3.8 Lockout Mode ...................................................................... 3-123.3.3.9 Switching Status .................................................................. 3-133.3.3.10 Maintenance ........................................................................ 3-13

3.3.4 Ring Protection .................................................................................. 3-143.3.4.1 Ring Switch Protection Types .............................................. 3-143.3.4.2 Span Switch Protection (4F MS-SPRing only) ..................... 3-143.3.4.3 Ring Switch Protection ......................................................... 3-153.3.4.4 Standby Line Access (SLA) ................................................. 3-153.3.4.5 Switching Mode ................................................................... 3-163.3.4.6 Switching Status .................................................................. 3-173.3.4.7 Maintenance ........................................................................ 3-17

3.4 Path Protection .................................................................................3-183.4.1 Path Protection Mode ........................................................................ 3-183.4.2 Switching Mode ................................................................................. 3-19

3.4.2.1 Switching Status .................................................................. 3-193.4.2.2 Maintenance ........................................................................ 3-19

3.5 Interlocked Ring Protection ............................................................3-20

3.6 Overhead (OH) Protection ...............................................................3-213.6.1 Objects for OH Protection ................................................................. 3-213.6.2 Types of OH Protection ..................................................................... 3-21

4. SYNCHRONIZATION 4-1

4.1 Synchronization .................................................................................4-14.1.1 Clock Interface .................................................................................... 4-1

4.1.1.1 External Timing — Incoming .................................................. 4-14.1.1.2 External Timing — Outgoing .................................................. 4-14.1.1.3 SDH Line Timing .................................................................... 4-14.1.1.4 2M PDH Line Timing .............................................................. 4-2

4.1.2 Timing Mode ....................................................................................... 4-34.1.3 Clock Features .................................................................................... 4-4

4.2 Timing Source Control .......................................................................4-54.2.1 Quality Level ....................................................................................... 4-54.2.2 Priority Level Setting ........................................................................... 4-54.2.3 SSM Control ........................................................................................ 4-6

4.3 Timing Source Selection ...................................................................4-74.3.1 External Output Timing Source Switching Modes ............................... 4-7

Contents- iii -


4.3.2 External Output Message Translation Modes ..................................... 4-74.3.3 Signal Fail ........................................................................................... 4-74.3.4 Hold-off Time ....................................................................................... 4-84.3.5 SSM Hold-off Time .............................................................................. 4-84.3.6 Wait-to-Restore Time .......................................................................... 4-84.3.7 Switching Control ................................................................................ 4-8

4.4 Precautions .........................................................................................4-94.4.1 Timing Loop Example ......................................................................... 4-9

5. CONFIGURATION MANAGEMENT 5-1

5.1 Configuration Management Object ...................................................5-15.1.1 NODE (NE: Network Element) ............................................................ 5-25.1.2 SHELF ................................................................................................. 5-25.1.3 PKG (Package) ................................................................................... 5-3

5.1.3.1 SINFM PKG ........................................................................... 5-35.1.3.2 Slot Number ........................................................................... 5-4

5.1.4 CPU ..................................................................................................... 5-55.1.5 Facility ................................................................................................. 5-65.1.6 External Clock (EXTCLK) .................................................................... 5-65.1.7 Switch Group ....................................................................................... 5-75.1.8 Synchronization ................................................................................... 5-75.1.9 Overhead Access Channel (OHCH) ................................................... 5-85.1.10 Data Communication Channel (DCC) ................................................. 5-8

5.1.10.1 OHC Package Type and DCC ............................................... 5-8

5.1.11 HKC/HKA ............................................................................................ 5-85.1.12 V.11 Port ............................................................................................. 5-8

5.2 Service State .......................................................................................5-95.2.1 Service State Definition ....................................................................... 5-9

5.2.1.1 Primary Service State (PST) .................................................. 5-95.2.1.2 Secondary Service State (SST) ............................................. 5-9

5.3 Other Administration States ............................................................5-105.3.1 Port Mode .......................................................................................... 5-105.3.2 Mode Mismatch ................................................................................. 5-10

5.4 Memory Backup ................................................................................5-11

Contents- iv -


5.4.1 Overview ........................................................................................... 5-115.4.2 Memory Configuration ....................................................................... 5-11

5.5 Starting Up NE ..................................................................................5-135.5.1 Hot Start ............................................................................................ 5-135.5.2 Cold Start .......................................................................................... 5-13

5.6 Inventory ...........................................................................................5-145.6.1 Package Inventory ............................................................................ 5-145.6.2 NE Information Inventory .................................................................. 5-14

5.7 Object AIDs .......................................................................................5-155.7.1 Node .................................................................................................. 5-155.7.2 Shelf .................................................................................................. 5-155.7.3 Package ............................................................................................ 5-165.7.4 CPU ................................................................................................... 5-175.7.5 Memory Card .................................................................................... 5-185.7.6 Temporary Memory ........................................................................... 5-185.7.7 Line Facility ....................................................................................... 5-195.7.8 Package Protection Switch Group .................................................... 5-205.7.9 Line Protection Switch Group ............................................................ 5-205.7.10 Synchronization ................................................................................ 5-215.7.11 Path Facility ...................................................................................... 5-22

5.7.11.1 Higher-Order Path ............................................................... 5-225.7.11.2 Lower-Order Path (to/from SDH) ......................................... 5-235.7.11.3 Lower-Order Path (to/from PDH) ......................................... 5-23

5.7.12 Path Monitor ...................................................................................... 5-245.7.12.1 Higher-Order Path ............................................................... 5-245.7.12.2 Lower-Order Path ................................................................ 5-24

5.7.13 Path Termination Point ..................................................................... 5-255.7.13.1 Higher-Order Path ............................................................... 5-255.7.13.2 Lower-Order Path ................................................................ 5-25

5.7.14 External Clock Input .......................................................................... 5-255.7.15 Housekeeping Alarm ......................................................................... 5-265.7.16 Housekeeping Control ...................................................................... 5-265.7.17 V11 User Channel Port ..................................................................... 5-265.7.18 Overhead Access Channel ............................................................... 5-265.7.19 Data Communication Channel (DCC Port) ....................................... 5-265.7.20 Virtual Concatenation (GBEM/FEH) ................................................. 5-27

Contents- v -


5.7.21 Channel ID (GBEM/FEH) .................................................................. 5-275.7.22 Profile ................................................................................................ 5-275.7.23 All ...................................................................................................... 5-27

6. PERFORMANCE MONITORING 6-1

6.1 Performance Monitoring (PM) Type ..................................................6-16.1.1 Physical Layer ..................................................................................... 6-16.1.2 Regenerator Section Layer ................................................................. 6-26.1.3 Multiplex Section Layer ....................................................................... 6-36.1.4 E12/E31/E32 Line Layer ..................................................................... 6-46.1.5 1000BASE-X Interface (GBEM) .......................................................... 6-56.1.6 10BASE-T/100BASE-TX Ethernet Interface (FEH) ............................. 6-76.1.7 HPTM3 Layer ...................................................................................... 6-96.1.8 VCT Layer ......................................................................................... 6-106.1.9 HP Monitor ........................................................................................ 6-116.1.10 LP Monitor ......................................................................................... 6-126.1.11 HPT ................................................................................................... 6-136.1.12 LPT ................................................................................................... 6-146.1.13 Multiplex Section Protection .............................................................. 6-156.1.14 AU Path ............................................................................................. 6-166.1.15 SES Threshold .................................................................................. 6-17

6.2 PM Data Management ......................................................................6-186.2.1 PM Data Type ................................................................................... 6-186.2.2 Data Reliability .................................................................................. 6-18

6.3 TCA Function ....................................................................................6-196.3.1 TCA Threshold .................................................................................. 6-19

6.4 IPPM Management ............................................................................6-206.4.1 Monitor Point ..................................................................................... 6-20

6.4.1.1 Monitor Points for Higher Order Path .................................. 6-206.4.1.2 Monitor Points for Lower Order Path ................................... 6-20

6.4.2 Accumulation ..................................................................................... 6-21

7. FAULT MANAGEMENT 7-1

Contents- vi -


7.1 Monitored Items ..................................................................................7-1

7.2 Management Parameters ...................................................................7-27.2.1 Alarm Severity ..................................................................................... 7-27.2.2 Delay/Stretch Time .............................................................................. 7-3

7.3 Alarm Report .......................................................................................7-47.3.1 LED Process ....................................................................................... 7-47.3.2 Report to User Interface ...................................................................... 7-47.3.3 Office Alarm ........................................................................................ 7-4

7.3.3.1 Office Alarm Type .................................................................. 7-47.3.3.2 Delay/Stretch Process ........................................................... 7-57.3.3.3 ACO Function ........................................................................ 7-5

7.3.4 Processing Alarm Masks ..................................................................... 7-5

7.4 Offline Monitoring ..............................................................................7-6

8. LOG FUNCTION 8-1

8.1 Command Log ....................................................................................8-18.1.1 Mode of Logging ................................................................................. 8-1

8.2 AO Buffer ............................................................................................8-28.2.1 Mode of Logging ................................................................................. 8-2

9. MAINTENANCE OPERATION 9-1

9.1 Loopback Function ............................................................................9-19.1.1 Line Loopback ..................................................................................... 9-1

9.1.1.1 Facility Loopback ................................................................... 9-29.1.1.2 Terminal Loopback ................................................................ 9-29.1.1.3 Remote Loopback .................................................................. 9-3

9.1.2 V.11 Port Loopback ............................................................................. 9-59.1.2.1 Facility Loopback ................................................................... 9-59.1.2.2 Terminal Loopback ................................................................ 9-5

9.2 Automatic Laser Shutdown ...............................................................9-69.2.1 Automatic Laser Shutdown (ALS) ....................................................... 9-6

9.2.1.1 Exception for GBEM Package ............................................... 9-7

9.2.2 Automatic Power Shutdown (APSD) ................................................... 9-8

Contents- vii -


9.2.3 Lower-Level Optical Output (Reflected Alarm Detection) ................... 9-99.2.4 Forced Optical Output Shutdown ........................................................ 9-9

9.3 Overhead Access .............................................................................9-109.3.1 User Channel Access ........................................................................ 9-10

9.3.1.1 Accessible Facility ............................................................... 9-109.3.1.2 Usable Overhead Byte ......................................................... 9-109.3.1.3 User Channel Loopback ...................................................... 9-10

9.3.2 DCC LAPD Access ........................................................................... 9-119.3.3 Overhead Through ............................................................................ 9-119.3.4 Orderwire Access .............................................................................. 9-11

9.3.4.1 Orderwire Interface .............................................................. 9-119.3.4.2 Calling .................................................................................. 9-12

9.4 Line Switch Exercise ........................................................................9-13

9.5 Housekeeping ...................................................................................9-149.5.1 Housekeeping Alarm ......................................................................... 9-149.5.2 Housekeeping Control ....................................................................... 9-14

9.6 Reset Function .................................................................................9-159.6.1 How to Reset CPU ............................................................................ 9-159.6.2 Restart Level ..................................................................................... 9-15

10. SECURITY MANAGEMENT 10-1

10.1 Type of User Account ......................................................................10-110.1.1 Super User ........................................................................................ 10-110.1.2 Normal User ...................................................................................... 10-1

10.2 User Attributes .................................................................................10-110.2.1 User Identification (UID) .................................................................... 10-2

10.2.1.1 Valid ASCII Characters for UID ........................................... 10-2

10.2.2 Password (PID) ................................................................................. 10-310.2.2.1 Valid Password .................................................................... 10-310.2.2.2 Valid ASCII Characters for PID ............................................ 10-4

10.2.3 User Account Expiration ................................................................... 10-410.2.4 Password Aging ................................................................................ 10-510.2.5 Password Expiration ......................................................................... 10-510.2.6 User Privilege Code Level ................................................................ 10-5

Contents- viii -


10.3 Addition, Modification, and Deletion of Users ............................10-1210.3.1 Addition ........................................................................................... 10-1210.3.2 Modification ..................................................................................... 10-1210.3.3 Deletion ........................................................................................... 10-12

10.4 Accessing the Network Element ...................................................10-1310.4.1 Login ............................................................................................... 10-1310.4.2 Logout ............................................................................................. 10-13

10.4.2.1 Manual Logout ................................................................... 10-1310.4.2.2 Automatic Logout ............................................................... 10-1310.4.2.3 Forced Logout .................................................................... 10-13

Contents- ix -


This page is intentionally left blank.

Contents- x - E


1. SIGNAL INTERFACE FUNCTION

This section provides a description of the function for managing signal interface supportedby U-Node WBM: access methods and input/output main signal operation. Physicalspecifications for interfaces are given in the General Information manual.

U-Node WBM supports the following main signals:

!SDH Optical Signal

• STM-64 (supported from Release 2.1)

• STM-16

• STM-4

• STM-1

!STM1e Signal; E4 Signal

!Ethernet Signal (supported from Release 2.1)

!2M Signal

!34M Signal

!45M Signal

Signal Interface Function1-1


1.1 OVERHEAD PROCESS

Descriptions given here show the overhead byte process managed by U-Node WBM.

1.1.1 Regenerator Section (RS)

The following table lists the functions related to the RS (Regenerator Section) overhead byteon the SDH signal.

! A1, A2 ByteA1, A2 byte is used to synchronize the SDH frame. If neither the A1 or A2 pattern isdetected, the frame goes out of synchronization, and the LOF alarm is issued.

! J0/C1 ByteJ0/C1 byte can be used as J0 byte or C1 byte, according to the user’s definition. In the J0mode, the connection of section layers can be verified by transferring the Section AccessPoint Identifier to a remote NE. Refer to the 1.2 Trace Function subsection for J0 byte.

RS Overhead Process

OH Byte Usage Related Functions

A1, A2 Frame Synchronization PM Function (OOF)/Fault Management (LOF)

J0/C1 Section TraceSTM-ID

Fault Management (TIM)

Z0 ——— ———

NU(1row) ——— ———

B1 Section Error Monitor (BIP-8) PM Function (BBE, etc.)

E1 (1) USER-Ch(2) Section Orderwire

Overhead Access Function

F1 USER-Ch Overhead Access Function

NU(2row) ——— ———

D1-3 Regenerator Section DCC Overhead Access Function

Media Byte ——— ———

Unuse Byte ——— ———

Signal Interface Function — Overhead Process1-2


! B1 ByteB1 byte based on the BIP-8 is used to detect an error from the main signal. The detected biterror is used for the performance monitoring function and failure detection.

! E1 ByteE1 byte is used for the overhead byte access function. E1 byte can be used for theorderwire that is between regenerator sections of A-law, or the user channels. When thisbyte is not used,

! Receiving side: ignores

! Sending Side: • can insert the Silence Code (for the orderwire-use)• can insert the Idle Code (for the data channel-use)

! F1 ByteF1 Byte is used for the overhead byte access function. F1 byte is also available for the userchannel. When this byte is not used,

! Receiving Side: ignores

! Sending Side: can insert the Idle Code

! D1-D3 ByteD1 through D3 bytes are used for the overhead byte access function. These three bytes areused together in communication as a Data Communication Channel (DCCr) signal at192 K. When these bytes are not used,





1.1.2 Multiplex Section (MS)

! B2 ByteThe error count is detected by using B2 byte based on BIP-n × 24. The detected bit error isused for the performance monitoring function and failure detection. Refer to 6.Performance Monitoring section for details. Conditions detected as B2 alarms are:

! EXC: excessive bit error, causing main signal failure

! DEG: degraded bit error, causing main signal deterioration

! K1, K2 ByteUpper 13 bits of K1, K2 byte are used for line protection. Lower 3 bits of K1, K2 byte areused for detecting MS-AIS alarm and transferring/detecting MS-RDI alarm. Refer to 3.Protection section for a detailed description on the line protection. If equipment failurerelated to the main signal is detected, an MS-AIS is inserted to the main signal.

! D4-D12 ByteD4 through D12 bytes are used for the overhead byte access function. These nine bytes areused together in communication as a Data Communication Channel (DCCm) at 576 K, oras the user channel. When these bytes are not used,




B2 Line Error Monitor (BIP-n × 24) Fault Management (EXC/DEG)/PM Func-tion

K1 Line Switching Control Protection Function (APS Process)

K2 Line Switching ControlLine Status Transfer

Protection Function (APS Process)

D4-12 (1) USER-Ch(2) Line DCC


S1 Synchronization Status Synchronization Function (SSM Process)

Z1/Z2 ——— ———

M1 Line Remote Side Error Display PM Function

E2 (1) USER-Ch(2) Line Orderwire


Unuse Byte ——— ———



! S1 ByteThe b1 to b4 bits of S1 byte are not used. The b5 to b8 bits are used to display thesynchronization status for timing source selection. Refer to the 4. Synchronization sectionfor synchronization using the S1 byte. When this byte is not used,



! M1 ByteM1 byte outputs the number of errors detected by the B2 byte to a remote side on a frame-by-frame basis. This value is used at the far-end for its PM.

! E2 ByteE2 byte is used for the overhead byte access function. E2 byte can be used for theorderwire that is between multiplex sections of A-law, or the user channels. When this byteis not used,

! Receiving side: ignores

! Sending Side: • can insert the Silence Code (for the use of orderwire)• can insert the Idle Code (for the use of data channel)



1.1.3 Higher Order Path (VC-4) & Lower Order Path (VC-3)

NOTES:

1. Detected at termination points.

2. Detected at monitoring points.

3. For Higher Order Path (VC-4) terminating Lower Order Path only.

4. For Higher Order Path (VC-4) through GBEM/FEH only; supported fromRelease 2.1.

! J1 ByteThe connection of path layers can be verified by transferring the Path Access PointIdentifier to a remote NE. If the received byte and the expected value do not match, a J1-TIM alarm is issued. This byte, however, is not monitored at Lower Order Path Monitoringpoints for failure detection. Refer to the 1.2 Trace Function subsection for details.

! B3 ByteThe error count is detected by using B3 byte based on BIP-8. The detected bit error is usedfor the performance monitor function and failure detection. Refer to the 6. PerformanceMonitoring section for details. Conditions detected as B3 alarms are:


! DEG: degraded bit error, causing man signal deterioration

These alarms are monitored at the higher order path monitoring points where theIntermediate Path Performance Monitor (IPPM) function is also supported.


J1 Path Trace Failure Detecting Function (J1-TIM)

B3 Path Error Monitor (BIP-8) PM Function

C2 Signal label Failure Detecting Function (UNEQ, PLMNOTE 1, VC-AISNOTE 2)

G1 SDHb1-b4: Path Remote Side Error (REI)b5: Path Remote Side Defect (RDI)b6-b8: Unused

PM Function, Fault Management

F2 ——— ———

H4 Position Identifier NOTE 3 Failure Detecting Function (LOM)

Virtual Concatenation Multiframe NOTE 4

F3 ——— ———

K3 ——— ———

N1 ——— ———



! C2 ByteC2 byte indicates VC path configuration. A failure in the VC path configuration can bedetected by verifying the received C2 byte. For a Lower Order path that is terminated atHPT, the TUG structure label is output as a C2 byte. At VC-3 Lower Order PathTermination points, Async-VC-3 is output as a C2 byte. At HPTM3 Higher Order PathTermination points, the GFP mapping is output as C2 byte (supported from Release to 2.1).At monitoring points, only the UNEQ alarm is detected. Refer to the 1.3 Signal LabelFunction subsection for details.

! G1 ByteMonitoring the G1 byte enables Performance Monitoring at HPT termination points of thePSW40B/GBEM/FEH package (for Higher Order path) or E31/E32 package (for LowerOrder Path), and detection of the error status on a remote side. Intermediate PathPerformance Monitor (IPPM) function is also available. Refer to the 6. PerformanceMonitoring section and the 7. Fault Management section for details.

NOTE: GBEM and FEH interface packages are supported from Release 2.1.

! F2 ByteThis byte is not managed and the status of each side is as follows:



! H4 ByteThis byte is not managed except for Higher Order path (VC-4) that is terminating LowerOrder path, and for GBEM/FEH. When not managed, the status of each side is as follows:



For a Higher Order path that is terminating Lower Order path, this byte is used as amultiframe position indicator at Higher Order Path Termination points. When thecrossconnect level VC-12 does not exist or the byte is not used at monitoring points, thestatus of each side is as follows:


! Sending Side: outputs multiframe indicator

When a GBEM/FEH package is used, this byte synchronizes multiframes in order to detectphase difference among each VC-4 path configuring virtual concatenation.

NOTE: GBEM and FEH packages are supported from Release 2.1.

Following shows the H4 byte multiframe sequence:



! F3 ByteThis byte is not managed and the status of each side is as follows:



! K3 ByteThis byte is not managed and the status of each side is as follows:



! N1 ByteThis byte is not managed and the status of each side is as follows:



H4 Byte Multiframe Sequence for GBEM/FEH

Bit 1 Bit 2 Bit 3 Bit 4 1st Multiframe MFI1 (Bits 1 - 4) 1st Multiframe # 2nd Multiframe #

Previous Frame (n–1) n–1

2nd Multiframe Indicator MFI2 MSB (Bits 1 - 4) 0 0 0 0 0 n

2nd Multiframe Indicator MFI2 LSB (Bits 5 - 8) 0 0 0 1 1

Reserved (“0000”) 0 0 1 0 2

Reserved (“0000”) 0 0 1 1 3

Reserved (“0000”) 0 1 0 0 4

Reserved (“0000”) 0 1 0 1 5

Reserved (“0000”) 0 1 1 0 6

Reserved (“0000”) 0 1 1 1 7

Reserved (“0000”) 1 0 0 0 8

Reserved (“0000”) 1 0 0 1 9

Reserved (“0000”) 1 0 1 0 10

Reserved (“0000”) 1 0 1 1 11

Reserved (“0000”) 1 1 0 0 12

Reserved (“0000”) 1 1 0 1 13

Sequence Indicator SQ MSB (Bits 1 - 4) 1 1 1 0 14

Sequence Indicator SQ MSB (Bits 5 - 8) 1 1 1 1 15

Next Frame (n+1) n+1



1.1.4 Lower Order Path (VC-12)

NOTES:

1. Not detected at monitoring points.2. Detected at monitoring points.

! J2 ByteThe connection of path layers can be verified by transferring the Path Access PointIdentifier to a remote NE. If the received byte and the expected value do not match, a J2-TIM alarm is issued. This byte, however, is not monitored at Lower Order Path Monitoringpoints for failure detection. Refer to the 1.2 Trace Function subsection for details.

! V5 Byte

• Bits 1 and 2The error count is detected by using bits 1 and 2 based on BIP-2. The detected bit error isused for the performance monitor function and failure detection. Refer to the 6.Performance Monitoring section for details. Conditions detected as V5 alarms are:


! DEG: degraded bit error, causing main signal deterioration

These alarms are monitored at the lower order path monitoring points where theIntermediate Path Performance Monitor (IPPM) function is also supported.

• Bit 3The number of errors detected based on BIP-2 is output to a remote side on a frame-by-frame basis. This value is used at the far-end side for its PM. PM detection using this bit atmonitoring points is not supported.

• Bit 4This bit is not managed since U-Node WBM does not have a process function using this bit.

• Bits 5 thru 7These bits indicate VC path configuration. A failure in the VC path configuration can bedetected by verifying the received bits 5 to 7 of the V5 byte. For VC-12, ASYNC-FLOATis output. Refer to the 1.3 Signal Label Function subsection for details.


J2 Path Trace Failure Detecting Function (J2-TIM)

V5 b1, b2: Path Error Monitor (BIP-2)b3: Path Remote Side Error (REI)b4: Unusedb5-b7: Signal Labelb8: Path Remote Side Defect (RDI)

PM Function, Failure Detecting Function (UNEQ, PLMNOTE 1, VC-AISNOTE 2, RDI)

K4 ——— ———

N2 ——— ———



• Bit 8By monitoring this bit, a path error status is output to a remote side as an RDI alarm. Thefar-end side detects the RDI alarm from this information and uses this bit for its PM.

! K4 ByteThis byte is not managed since the U-Node WBM does not have a process function usingthis byte.

! N2 ByteThis byte is not managed since the U-Node WBM does not have a process function usingthis byte.



1.1.5 GFP Frame ProcessNOTE: GBEM package is supported from Release 2.1.

1.1.5.1 GFP Frame Format

Following shows the GFP frame format:

! Core HeaderThis header is a fixed-length filed of four octets, and is used for frame synchronization andbasic data link:

• PLIPLI expresses the length of payload area (unit: octet), and its values are from 0 thru65535. Among these values, especially between 0 thru 3 indicates GFP controlframe.

• cHECcHEC is a 16-bit CRC obtained from PLI, and is used for frame synchronizationand correction of core header errors. Polynomial to obtain the value is:

x16 + x15 + x12 + 1

! Payload HeaderThis header is a variable-length field of 4 thru 64 octets, and is used for managing specificdata link for upper protocol. Following three fields make up the payload header:

• TypeType expresses classification of payloads (upper protocol).

• tHECtHEC is a 16 bit CRC obtained from the Type. Polynomial to obtain the value is:

x16 + x15 + x12 + 1

Field Usage

GFP Frame Core Header PLI PDU Length Indicator

cHEC Core Header Error Control

Payload Header Type GFP Type Field

tHEC Type Header Error Control

Extension Header

GFP Extension Header

eHEC Extension Header Error Control

Payload Information Header

PDU Protocol Data Unit

Payload FCS Payload Frame Check Sequence (unused)



• Extension HeaderThis header is defined by the Type field with logical topology as shown below:

Null: No header is applied; used for logical point-to-point connection.

Linear Frame: Used for logical point-to-point connection; supporting multiplepackets.

• eHECeHEC is a 16 bit CRC obtained from the Extension Header. Polynomial to obtainthe value is:

x16 + x15 + x12 + 1

! Payload Information Field

• PDUThis filed stores upper protocol data. The size is the remaining where taking otherheaders from full length of GFP frame (min. 0, max. 65535 octets).

• Payload FCSPayload FCS is 32 bits CRC obtained by Payload field; this field is not used.

1.1.5.2 GFP Mapping

Frame-Mapped GFP is the process where recognizing frame partitions of upper protocol, andencapsulating each frame to GFP (Generic Framing Procedure). Following shows theprocess that Ethernet signal is mapped to GFP.

Taking IFG (Inter Frame Gap), Preamble, and SFD (Start of Frame Delimiter) out of theEthernet frame, the remaining fields are stored in Payload field of GFP frame. Between GFPand Ethernet, the order of their bits are inverted because the bit order of GFP is MSB-First,and that of Ethernet is LSB-First.

MAC frame that U-Node WBM supports are DIX (Ethernet), IEEE802.3, and IEEE802.1q.

CORE HEADER

PAYLOAD HEADER

PAYLOAD FIELD

PREAMBLE

SFB

DESTINATION MAC

SOURCE MAC

LENGTH/TYPE

FCS

CLIENT DATA

transmission bit order

transmission bit order

LSB MSB

MSB LSB

GFP

IEEE802.3

GFP FRAME

ETHERNET MAC FRAME

(IFG)



1.2 TRACE FUNCTION

The trace function is provided to monitor the connection status in each layer.

The section trace using J0 byte includes the following modes: 1-byte mode, 16-byte mode,and 64-byte mode. The C1 mode without using the section trace function is available as well.The section trace (J0 byte) function is supported by an SDH optical interface, such asSTM-64, STM-16, STM-4, and STM-1, and an STM-1e electrical interface.

The path trace using J1 byte includes the 16-byte mode and 64-byte mode. The J1 byte pathtrace supports the monitoring function to all the paths on the line facilities of STM-64*,STM-16, STM-4, STM-1, and STM-1e.

J1 byte is terminated at the Higher Order Path Termination points by the PSW40B/GBEM*/FEH* package in the 16-byte or 64-byte mode.

For the Lower Order Path trace, J1 or J2 byte is terminated at the Lower Order PathTermination points by the PDH interface package in the 16-byte mode. However, the LowerOrder Path trace does not support the monitoring function at monitoring points.

If the received value and the expected value specified by a user do not match, a TIM (traceindication mismatch) alarm is issued; this detection can be inhibited by a user definition.

*: STM-64 interface (SINF64(B) interface package), GBEM, and FEH interface packagesare supported from Release 2.1.

Signal Interface Function — Trace Function1-13


1.2.1 16-Byte Mode

The following is the frame configuration in the 16-byte mode:

! Within 15 characters of ASCII data (indicated as X in the above table) is assignedto the trace data.

! C1 to C7 (C1=MSB) at Byte # 1 are the results of the calculation from the fore

frame CRC-7 (X7+X3+1). U-Node WBM automatically adds these CRCcalculation results to the user defined 15-byte data, then sends them out.

1.2.2 64-Byte Mode

The following is the frame configuration in the 64-byte mode:

! Within 62 characters of ASCII data is assigned to the trace data.

! The 64-byte data synchronizes the 64-byte frame by using the CR character of the#63-byte (0 DH) and the LF character of the #64-byte (0 AH).

1.2.3 1-Byte Mode

At the sending side, the user defined 1-byte data is output in binary. At the receiving side, thereceived bytes are converted to be indicated as numerals using 0 through 255. Specifying “0”to the expected value disables TIM detection.

Byte # Value (bits 1 to 8)

1 1 C1 C2 C3 C4 C5 C6 C7

2 0 X X X X X X X

3 0 X X X X X X X

: : :

16 0 X X X X X X X

1 2 3 4 5 ........ 63 64

CR LF



1.2.4 Trace Message Character

To specify the section trace or path trace in the 16-byte mode or 64-byte mode describedabove, and to enter the expected value and transmitting value for the trace, use the followingASCII characters:

Valid ASCII Characters for Trace Message

MSB B6 0 0 0 0 1 1 1 1

B5 0 0 1 1 0 0 1 1

LSB B4 0 1 0 1 0 1 0 1

B3 B2 B1 B0 0 1 2 3 4 5 6 7

0 0 0 0 0 0 @ P ‘ p

0 0 0 1 1 ! 1 A Q a q

0 0 1 0 2 2 B R b r

0 0 1 1 3 # 3 C S c s

0 1 0 0 4 $ 4 D T d t

0 1 0 1 5 % 5 E U e u

0 1 1 0 6 & 6 F V f v

0 1 1 1 7 ’ 7 G W g w

1 0 0 0 8 ( 8 H X h x

1 0 0 1 9 ) 9 I Y i y

1 0 1 0 A J Z j z

1 0 1 1 B + K [ k

1 1 0 0 C L l |

1 1 0 1 D - = M ] m

1 1 1 0 E . N ^ n ~

1 1 1 1 F / ? O _ o



1.3 SIGNAL LABEL FUNCTION

The signal label function is provided to monitor the path configuration status. See thefollowing tables for the SDH path signal labels:

1.3.1 SDH Path C2 Byte Codes

The following shows the SDH signal labels for VC-4-16c, VC-4-4c, VC-4, and VC-3:

Hex Code Description

00 Unequipped or supervisory–unequipped

01 Equipped – NonSpecific

02 TUG structure

03 Locked TU-n

04 Asynchronous mapping, or 34,368 kbit/s or 44,736 kbit/s into Container-3

12 Asynchronous mapping, or 139,264 kbit/s into Container-4

13 ATM mapping

14 MAN (DQDB) mapping

15 FDDI mapping

16 HDLC according

1B GFP mapping

FE Test signal, O.181 specific mapping

AIS Alarm Indication SignalATM Asynchronous Transfer ModeDQDB Distributed Queue Dual BusFDDI Fiber Distributed Data InterfaceHDLC High-level Data Link ControlMAN Metropolitan Area NetworkTUG Tributary Unit Group

Signal Interface Function — Signal Label Function1-16


1.3.2 SDH Path V5 Byte Codes

The following shows the SDH signal labels for VC-12:

Hex Code Description

00 Unequipped

01 Equipped – NonSpecific

02 Asynchronous mapping

03 Bit synchronous

04 Byte synchronous

05 Extend signal label

06 Test signal, O.181 specific mapping

Signal Interface Function — Signal Label Function1-17



Signal Interface Function1-18 E


2. CROSSCONNECT

This section provides an overview of the crossconnect function.

2.1 CROSSCONNECT PROCESS CAPACITY

The crossconnection of U-Node WBM is performed by the PSW40B package. The PSW40Bpackage provides the Higher Order Crossconnect function and the Lower OrderCrossconnect function. Refer to the 4.4 Common Packages subsection in the Provisioningmanual for details.

2.1.1 Matrix Capacity

The following tables show the crossconnect capacity supported by U-Node WBM:

! Higher Order Path

! Lower Order Path

Crossconnect Level Capacity

VC-4 224 × 224

Crossconnect Level Capacity

VC-12 2016 × 2016

VC-3 96 × 96

Crossconnect — Crossconnect Process Capacity2-1


2.1.2 Crossconnect Configuration

A block diagram for the PSW40B package is shown below:

The U-Node WBM provides 40G capacity for Higher Order path and 5G capacity for LowerOrder path. Crossconnection of Higher Order path between STM-n interfaces or betweenSTM-n interface and Ethernet interface* is made at Higher Order SW, while that of LowerOrder path is made at Lower Order SW via Higher Order SW. Crossconnection betweenPDH interfaces is made at Lower Order SW via Higher Order SW as well.

When connecting to the Lower Order SW, be aware that the Lower Order SW capacity islimited in order to perform crossconnection. Therefore, total capacity of signals sent fromthe STM-n and PDH interface packages for Lower Order SW should be less than the valuesof 5G.

(*: Ethernet interface is supported from Release 2.1.)

PDH Interface

STM-n Interface

Lower Order SW(5G)

PSW40B Package

Higher Order SW (40G)

Ethernet Interface



The minimum unit of signals connected to the Lower Order SW from the Higher Order SW isAU-4 (155M). The minimum unit of signals connected to the Lower Order SW from PDHinterface packages is also 155M, and the combination of PDH signal channels is as follows:

The following table shows the capacity required for connecting to the Lower Order SW whenthe maximum number of PDH interface packages is registered on one WBM shelf:

PackageCombination of Minimum Unit (155M) Channels

Connected to Lower Order SW

E12 1 to 63 ch

E31 1 to 3 ch

4 to 6 ch

E32 1 to 3 ch

4 to 6 ch

Package Capacity of Lower Order SWMaximum Number of Interface

Channels

E12 1.25G 504 ch

E31 2.5G 48 ch

E32 2.5G 48 ch



2.2 CROSSCONNECT LEVEL

! For an SDH input signal, the Higher Order signal is mapped into a time slot by VC-4,VC-4-4c, VC-4-16c, or VC-4-1V to VC-4-7V* level.

! Lower Order signals can be mapped into a time slot by VC-3 or VC-12 level.

Each signal level indicates the following bit rates:

NOTE: VC-4-7V is supported from Release 2.1.

2.2.1 Crossconnect Termination Point

The path band level and the operation mode within the path band should be selected whenspecifying the crossconnect termination points:

! Path Band LevelFor the Higher Order Crossconnect, select a path band level from AU-4, AU-4-4c,AU-4-16c, and AU-4-1V to AU-4-7V*. For the Lower Order Crossconnect, select a pathband level from TU-12 and TU-3.

NOTE: AU-4-7V is supported from Release 2.1.

! Operation ModeThe following two modes are provided for AU-n Higher Order band level:

! AUTO: The path band level to be managed varies according to the input signallevels received within the specified levels, where alarm detection andperformance monitoring are performed.

! FIX: Alarm detection and performance monitoring are enabled only when aninput signal of the specified level is received.

SIGNAL LEVEL BIT RATES SIGNAL LEVEL BIT RATES

VC-12 2 Mbit/s VC-4-4c 600 Mbit/s

VC-3 50 Mbit/s VC-4-16c 2.5 Gbit/s

VC-4 150 Mbit/s VC-4-1V to VC-4-7V* 150 Mbit/s to 1.05 Gbit/s

Crossconnect — Crossconnect Level2-4


2.3 CROSSCONNECT TYPES

2.3.1 Higher Order Path

The U-Node WBM has the following crossconnect types:

! 1-Way

• LXC (Local Cross-Connect)

• PPS (Path Protection Selector)

! 2-Way

• LXC (Local Cross-Connect)


NOTE: Specifying a path to a Protection side of Linear 1:1 Bidirectional, 2F MS-SPRing, or 4FMS-SPRing assigns the path to SLA.

2.3.1.1 1-Way

The following illustrations show examples of one-way crossconnect types:

2.3.1.2 2-Way

The following illustrations show examples of two-way crossconnect types:

LXC PPS

LXC PPS

A B

A B A B

Crossconnect — Crossconnect Types2-5


2.3.2 Lower Order Path

The U-Node WBM has the following crossconnect types:

! 1-Way

• Add

• Drop

• LXC (Local Crossconnect)

• Loopback

• PPS (path Protection Selector)

! 2-Way

• Add-Drop

• LXC (Local Crossconnect)

• Loopback


NOTE: When crossconnecting STM-n at Lower Order Path switch, Higher Order pathcrossconnection is required as well.

2.3.2.1 1-Way

The following illustrations show examples of one-way crossconnect types:

Crossconnect Type Without PPS With PPS

Add

———

Drop

LOSW

HOSW

STM-N

PDH

LOSW

HOSW

STM-N

PDH

LOSW

HOSW

STM-N

PDH



HOSW: Higher order switchLOSW: Lower order switch

2.3.2.2 2-Way

The following illustrations show examples of two-way crossconnect types:

LXC

Loopback

—


Add-Drop


LOSW

HOSW

STM-N

LOSW

HOSW

STM-N

LOSW

HOSW

PDH

LOSW

HOSW

STM-N

PDH

LOSW

HOSW

STM-N

PDH



HOSW: Higher order switchLOSW: Lower order switch

LXC

Loopback

—


LOSW

HOSW

STM-N

LOSW

HOSW

STM-N

LOSW

HOSW

PDH



2.3.3 Additional Samples

! Multiple crossconnection sharing the same termination point can be specified. Theillustration below (at left) shows an example of the interlocking path. This pathcomprises two types of setups, as shown in the illustration below (" to #).

! Following is Broadcast crossconnection comprising multiple crossconnect setups.

1-Way Crossconnect - Broadcast

! The path shown below can be achieved by multiple 1-Way PPS setups:

1-Way Crossconnect – PPS Broadcast

! For Through connection between EAST and WEST on the MS-SPRing, connection mustbe made using the same time slots on both the EAST and WEST sides.

" #

1-Way (LXC) 1-Way (PPS)

= +A

B

C

A BA B

C

AB

A B

C

A

= +D E

C

D E

A B

C D

= +A

B

D

C

B

D



2.3.4 Idle Signal Processing

When the path has not been connected, the idle signal interlocking with a facility per line canbe specified for SDH Interface.

An idle signal that matches the registered Band Level for the crossconnect point is output foreach crossconnection.

The optical signal is not output unless you register each line facility and put it into the In-Service state.



2.4 SQUELCH SETTINGS

Within the 2F/4F MS-SPRing configuration, if a node failure occurs where more than onepath that are added/dropped at different nodes are specified to the same time slot, theirconnection will go wrong (misconnection). Following shows an example of path flows thatwill have the misconnection if these paths use the same time slot:

To prevent the path flow from the misconnection, squelch table should be specified to eachpath where an AIS is issued to the miss-connected path.

LINE2 LINE1

LINE2

LINE1

WO

RK

PR

OT

WO

RK

PR

OT

WORK

PROT

WORK

WORK

WORKWORK

WORK

PROT

PROT

PROTPROT

PROT

WO

RK

WO

RK

PR

OT

PR

OT

LINE2

LINE1

LINE2 LINE1 LINE2LINE1

NODE 0

NODE 1

NODE 2

NODE 3

NODE 4

LINE2 LINE1

LINE2

LINE1

WO

RK

PR

OT

WO

RK

PR

OT

WORK

PROT

WORK

WORK

WORKWORK

WORK

PROT

PROT

PROTPROT

PROT

WO

RK

WO

RK

PR

OT

PR

OT

LINE2

LINE1

LINE2 LINE1 LINE2LINE1

NODE 0

NODE 1

NODE 2

NODE 3

NODE 4

Failure has occurred in NODE3

PATH A

PATH BPATH DPATH C

PATH A

PATH C

× PATH C is carried in

× PATH A is carried in

Crossconnect — Squelch Settings2-11


2.4.1 Squelch Table

Following shows an example for making squelch tables:

2.4.1.1 Simple 2F/4F MS-SPRing

For the regular 2F/4F MS-SPRing mode, registrations for Add Node ID (Near Add) andDrop Node ID (Near Drop) are required:

! Squelch Node ID

NOTE: For a 2-Way path, assignments for Near Add node ID and Near Drop node ID can beinverted.

Registration Near Add ID Near Drop ID Far Add ID Far Drop ID

For NODE 1 NODE 3 NODE 1 —— ——



NODE 1

LINE 1LINE 2

NODE 2

NODE 3

NODE 4

ADD NODE DROP NODE

Crossconnect — Squelch Settings2-12


2.5 VIRTUAL CONCATENATION

NOTE: Virtual concatenation is supported from Release 1.2.

2.5.1 Overview

Virtual concatenation allows better use of bandwidth by taking multiple channels as onechannel when transporting data. For example, if accommodating a Gigabit Ethernet signalwith the legacy contiguous concatenation, VC-4-16c is to be used allocating 2.5G bandwidth(42% efficiency). However, with virtual concatenation, using VC-4-7v (7 channels of VC-4)allocates only 1.05G bandwidth, and leaves the additional bandwidth within container forother links (96% efficiency).

U-Node WBM supports this virtual concatenation only for Ethernet signals, such as1000BASE (GBEM), 100BASE (FEH), and 10BASE (FEH).

2.5.2 Crossconnect Levels

U-Node WBM supports the following as the minimum unit of crossconnection level:

• VC-4 (unit: 150M)

• VC-4-4c (unit: 600M)

• VC-4-16c (unit: 2.5G)

Crossconnect — Virtual Concatenation2-13


2.5.3 Crossconnect

2.5.3.1 GBEM/FEH Package

NOTE: GBEM/FEH package is supported from Release 2.1.

For the virtual concatenation, in order to make selection available from bandwidth of 150Mto 2.5G, virtual concatenation termination point (VCT) must be registered.

Available VC (AU) path(s) within GBEM/FEH package can be registered for a VCT. Up tofour VCTs can be registered. Registering necessary VCs (AUs) for VCT specifies its virtualconcatenation.

VCT#1

VCT#2

VCT#3

VCT#4

AU #1

AU #2

AU #3

AU #16

VCT#1

VCT#2

VCT#3

VCT#4

AU #1

AU #2

AU #3

AU #16

GBEM/FEH GBEM/FEH

SDH NETWORK

LINE#1

LINE#2

LINE#1

LINE#2



2.5.3.2 Crossconnection Images

! GBEM/FEH Package

Crossconnection can be arranged in the same way shown for GBEM/FEH package. Also, asshown below, it can be arranged for protection configuration:

Working line and Protecting line can belong to the different SINF as well:

LINE#1

LINE#2

VCT#1

VCT#2

VCT#3

VCT#4

SINF

SINF

W

P

W: WORKP: PROTECTION

GBEM/FEHHigher Order SW(PSW40B)

VCT#1

VCT#2

VCT#3

VCT#4

SINF

SINF

W

P

W: WORKP: PROTECTION

W

P

GBEM/FEH

LINE#1

LINE#2

Higher Order SW(PSW40B)




Crossconnect2-16 E


3. PROTECTION

This section describes the protection function performed by U-Node WBM.

3.1 OVERVIEW

3.1.1 Protection Types

The following table shows the protection types available in U-Node WBM.

Type of Protection Object Method Note

Package PSW40B Package 1+1 –––

STM1E Package None/1+1 E4 signal input/output is available when E4TRM and E4TRM shelf are connected.

E31/32 Package None/1+1 E3 THR PKG must be used for Non-Protection. E3/E32 TRM PKG must be used for Protection.

E12 Package None/1:n (n = 1 to 8) E1 THR PKG is for Non-Protection. E1 TRM PKG is for Protection.

Line Transmission Line(Linear Network)

None/1+1/1:1 –––

Transmission Line(Ring Network)

MS-SPRing(4 Fiber/2 Fiber) –––

Path VC Path SNC/P Set up separate from lines.

OH RS OverheadMS Overhead ––– Interlocking with Linear Protection, Ring Protection.

Protection — Overview3-1


3.1.2 Protection Types and Package Slots

3.1.2.1 WBM Shelf Front View

The following illustration shows the front view of the WBM shelf: M

SC

BS

SC

B

PS

W40

B

PS

W40

B

SLOT # 3

OH

C

4 5 6 1819 20 217 8 9 1011 12 13 1415 1617

INF

#1

INF

#2

INF

#3

INF

#4

INF

(E

12 P

RO

TE

CT

ION

)IN

F #

5IN

F #

6IN

F #

7IN

F #

8IN

F #

8

INF

#9

INF

#10

INF

#11

INF

#12

INF

#13

INF

#14

INF

#15

INF

#16

TR

M #

1T

RM

#2

TR

M #

3T

RM

#4

TR

M #

8T

RM

#7

TR

M #

6T

RM

#5

1 2 22



3.1.2.2 Available Package Slots for Protections

MSCB

SSCB

INF

INF

INF

INF

INF

INF

INF

INF

INF

PSW40B

PSW40B

INF

INF

INF

INF

INF

INF

INF

INF

OHC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

LINE1 LINE2 (supported from Release 2.1)

LINE1 LINE2

LINE1 L2

L1 LINE2

L1 L2 L1 L2 NOTE 1

L1 L2

L1 L2 L1 L2

W P

(Currently not supported)NOTE 2 NOTE 2

W P W P W P

W P W P W P W P

W P W P W P W P

W P W P

W P W P W P W P

W P W P W P

W P W P W P W P

W P

(P) W1 W2 W3 W4 W8 W7 W6 W5

PKG SLOT #

available slot

2F MS-SPRING

SINF16

SINF16(B) + SINF16

STM1E

E31/E32

E12

(P) Protection package slot for E12 1:N Package Protection

vacant slot to be kept when SINF16(B) is installed in the right; or if this slot has aninterface package, the slot to the right cannot have SINF16(B).

SINF16 + SINF16(B)

SINF16(B)

SINF64(B)

SINF16(B)

SINF16(B)4F MS-SPRING

LINEAR

SINF16 / SINFM

SINF16(B) + SINF16

SINF16 + SINF16(B)

SINF16(B)

1+1

PSW40B

1:n

SINF64(B)

SINF16(B)

L1: LINE1, L2: LINE2

W P



NOTES:

1. For Release prior to 1.2, only one switch group of 2F MS-SPRing by SINF16(B) isavailable; one of these two switch groups must be selected. The multi-ring protectionwith two 2F MS-SPRing switch groups by SINF16(B) is available from Release 1.2.

2. The use of these slots is available from Release 1.2.

Also refer to the General Information manual: 2.2 U-Node WBM Composition for detaileddescriptions on installation rules for interface packages.



3.2 PACKAGE PROTECTION

3.2.1 Switching Configuration

For Package Protection, two types of configurations are available:

! 1+1 (Nonrevertive) Package Protection Configuration:

• PSW40B (common package)

• STM1E (interface package)

• E32 (interface package)


! 1:n Package Protection Configuration (n = 1 thru 8)


Packages must be installed into the appropriate slots to configure protections. Refer to 3.1.2.2Available Package Slots for Protections for the use of slots.

U-Node WBM allows these packages listed above Non Protection (No Prot) configurationas well.

3.2.2 Switching Mode and Switching Priority

There are two types of switching modes: the manual switch operated by the user, and theautomatic switch carried out by SF (signal failure) detection. The types of manual/automaticswitch are shown below:

• Forced Switch (FSW): switching is operational regardless of failure status.

• Manual Switch (MSW): switching is operational in Normal status.

• Automatic Switch (AutoSW) (W): switching is carried out by SF detection inWorking side.

• Automatic Switch (AutoSW) (P): switching is carried out by SF detection inProtection side.

The priory for these switching operations differs depending on a package:

Protection — Package Protection3-5


3.2.2.1 1+1 Package Protection Switching Priority

! Switching Priority for PSW40B Package

• FSW > AutoSW > MSW

! Switching Priority for STM1E/E32/E31 Packages

• AutoSW (P)NOTE > FSW > AutoSW (W)NOTE > MSW

NOTE: For STM1E, E32 and E31 packages, if an Automatic Switch has been carried out by afailure at the “protection (P)” side, the Forced Switch operation is disabled.

3.2.2.2 1:n Package Protection Switching Priority

! Switching Priority for E12 Package

• LKOP > AutoSW (P) > FSW > AutoSW (W) > MSW > WTR

NOTE: For E12 package, FSW/MSW from “Protection side (P)” to the “Working side (W)”are not available.

3.2.3 Lockout Mode

The Lockout mode holds the switching status (no switch operation is available) regardless ofthe current switching status; this mode can be set by the user.

3.2.4 Switching Status

The switching status and the online package can be confirmed via the CID. The ONLINELED (green) on front of a package lights up when the package is in the online mode, andgoes out when the package is in the offline mode. The maintenance LEDs (yellow) on therack top and MSCB package light up when the switching command (Lockout, Lockout ofProtection, Lockout of Working, Forced Switch, or Manual Switch) is successfullycompleted by the user.

Protection — Package Protection3-6


3.3 LINE PROTECTION

This subsection describes optical line facility protection.

3.3.1 Switching Configuration

You must specify interface packages that configure line protection. There are two protectionmethods as shown below:

! Two INF PKGs Protection: 2F MS-SPRing, 1+1 Linear, 1:1 Linear

! Four INF PKGs Protection: 4F MS-SPRing

Packages must be installed into the appropriate slots to configure protections. Refer to 3.1.2.2Available Package Slots for Protections for the use of slots.

3.3.2 Applicable Interface Types

$: Available.×: Not available.* This interface is supported from Release 2.1.

INTERFACE150M(OP1)

600M(OP4)

2.5G 10G*

Linear $ $ $ ×

2F-Ring × × $ $

4F-Ring × × $ ×

Protection — Line Protection3-7


3.3.3 Linear Protection

The following illustration shows the protection setup in multi-line interface packages(SINFM PKG) (150 M × 16):

3.3.3.1 Linear Protection Mode

In the Linear Protection mode, the following switch type and APS mode are selectable perline:

! Switch Type

• 1+1 Unidirectional, Nonrevertive

• 1+1 Bidirectional, Nonrevertive

• 1:1 Bidirectional, Revertive

! APS Mode

• ITU-T

3 4 5 6 7 8 9 10 11 14 15 16 17 (18) 19 (20) 21

VACANT

SINFM+

OP1

(W)

SINFM+

OP1

(P)

SWTICH GROUP

LINE 16 (WORK) LINE 16(PROTECTION)

LINE 1 (WORK) LINE 1(PROTECTION)



3.3.3.2 1+1 Unidirectional Linear Protection

The following illustration shows 1+1 Unidirectional Linear Protection Operation:

NOTE: For this protection type, a path cannot individually be specified to the Protection side.Protection line must be left open.

3.3.3.3 1+1 Bidirectional Linear Protection

The following illustration shows 1+1 Bidirectional Linear Protection Operation:

NOTE: For this protection type, a path cannot individually be specified to the Protection side.Protection line must be left open.

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

ONLINE

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

ONLINE



3.3.3.4 1:1 Bidirectional Linear Protection

The following illustration shows 1:1 Bidirectional Linear Protection Operation:

NOTE: For this type of protection, a path can individually be specified to the Protection side,which enables SLA. (SLA is supported from Release 1.2.) See 3.3.3.5 Standby LineAccess (SLA).

3.3.3.5 Standby Line Access (SLA)

For 1:1 Bidirectional protection, a path can also be specified to the Protection side, whichenables SLA. Specified Protection-side path will be in normal service as long as the Workpath has no failure; if a failure occurs to the Work side, the failed Work path will take overthe Protection side, and the path originally specified to the Protection side is terminated. (SLAis supported from Release 1.2.)

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

Optical Interface

Optical Interface

WORK LINE

PROTECTION LINE

ONLINE

WORK LINE

SLA/PROTECTION LINE

ONLINE WORK LINE

SLA/PROTECTION LINE



3.3.3.6 Switching Mode

There are two types of switching modes: the command switch operated by the user, and theautomatic switch carried out by SF (signal failure) and/or SD (signal degrade) detection. Thefollowing table shows switching commands:

Following shows the cause of Automatic Switch:

• AutoSW(SF-W): switching is carried out by SF detection in Working side.

• AutoSW(SF-P): switching is carried out by SF detection in Protection side.

• AutoSW(SD): switching is carried out by SD detection.

SF: Signal Fail SD: Signal Degrade

Command Definition

Lockout of protection (LKOP) LKOP inhibits the switching of service to the protection unit.

Forced Switch to protection (FSW to Protection)

Service is forcibly switched from the working line to the protection line.

Forced Switch to working(FSW to Working)

Service is forcibly switched from the protection line to the working line.

Manual switch to protection(MSW to Protection)

Service is manually switched from the working line to the protection line.

Manual switch to working(MSW to Working)

Service is manually switched from the protection line to the working line.

Clear This command is used to release LKOP, MSW, and FSW; it also releases WTR status.

Exercise This command is used to check the working conditions of the protection switch mechanism.



3.3.3.7 Linear Protection Switching Priority

! 1+1 Protection Switching priority is:

LKOP > AutoSW (SF-P) > FSW > AutoSW (SF-W) > AutoSW (SD) > MSW

The Lockout mode holds the switching status, and stops the transition regardless of thecurrent switching status; this mode can be set by the user.

You can modify the following parameters to the switching operation:

! RGT (Request to Guard Time): if a failed condition has been detected for thisspecified period (Guard Time), NE will regard the condition as a failure.

! WRT (Wait-to-Response Time): in the bi-directional mode, after sending a KByte request, if this specified period has run out without receiving the expected KByte from the opposing NE, NE will regard the condition as a failure.

! FFCT (Fault-Free Confirmation Time): after a failed condition is cleared, NEwaits for this specified period to ensure that the failure is cleared.

! WTR (Wait-to-Restore): in the revertive mode, after a failure is cleared (FFCTprocess has been completed), NE waits for this specified period to confirm thestatus, then switches the line back to the default side.

! 1:1 Protection Switching priority is:

LKOP > AutoSW (SF-P) > FSW > AutoSW (SF-W) > AutoSW (SD) > MSW > WTR

3.3.3.8 Lockout Mode

The Lockout mode holds the switching status (no switch operation is available) regardless ofthe current switching status; this mode can be set by the user.



3.3.3.9 Switching Status

The switching status and online facility can be confirmed via the CID.

The ONLINE LED (green) on the front of the package lights up when the line of the packageis in the online mode, and goes out when the line is in the offline mode. The maintenanceLED (yellow) on the rack top and MSCB package light up when the switching command(Lockout, LKOP, Forced Switch, or Manual Switch) is successfully completed by the user.

3.3.3.10 Maintenance

Performance monitoring (PM) function detects switching operation and switching time.Also, this function is used to notify switching failures to users.



3.3.4 Ring Protection

U-Node WBM supports the Ring Protection for 10G* (except for 4F MS-SPRing) or 2.5GInterfaces only, where those interface packages must be installed into the package slots #3thru 6. The 600M and smaller interfaces are not available for Ring Protection configuration.See 3.1.2.2 Available Package Slots for Protections for the protection type and appropriatepackage slots. [*: 10G interface is supported from Release 2.1.]

3.3.4.1 Ring Switch Protection Types

2F MS-SPRing and 4F MS-SPRing are configured according to the number of interfaces.U-Node WBM provides the In-Service Upgrade function for MS-SPRing from 2-Fiber to4-Fiber (supported from Release 1.2). The following illustration shows an example of 4FMS-SPRing mode operation:

3.3.4.2 Span Switch Protection (4F MS-SPRing only)

Span Switch Protection is the method working on 4F MS-SPRing only; not available on 2FMS-SPRing. Following illustration shows an example configuration and the Span Switching:

W

P

P

W

P

W

W

P

W

P

P

W

P

W

W

P

: Line (fiber): Traffic

W : Working side P : Protection side

: Failure

!!!! Normal Status

NODE 2

NODE 3

NODE 4

NODE 1

NODE 2

NODE 3

NODE 4

NODE 1

!!!! Span Switch is carried out by a failurebetween NODE 3 and NODE 4.



3.3.4.3 Ring Switch Protection

Following illustration shows an example configuration and the Ring Switching:

3.3.4.4 Standby Line Access (SLA)

For 2F/4F MS-SPRing protection, a path can also be specified to the Protection side, whichenables SLA. Specified Protection-side path will be in normal service as long as the Workpath has no failure; if a failure occurs to the Work side, the failed Work path will take overthe Protection side, terminating the path originally specified to the Protection side. If SpanSwitch is carried out, corresponding section of Protection-side path is also terminated. (SLAis supported from Release 1.2.)

: Line (fiber); the same line in 2F MS-SPRing, a different line in 4F MS-SPRing.: Traffic

W : Working side P : Protection side

: Failure

!!!! Normal Status !!!! Ring Switch is carried out by a failure

NODE 3

NODE 2

NODE 1

NODE 4

W

P

P

W

P

W

W

P

NODE 2

NODE 3

NODE 4

NODE 1

W

P

W

P

W

P

P

W

between NODE 2 and NODE 3.

W P/SLA

W

W

W

W

P/SLA

P/SLA

P/SLA

W P/SLA

W P/SLA



3.3.4.5 Switching Mode

There are two types of switching modes: command switch by user operation, and automaticswitch by detection of line failure. The following table shows switching commands:


• AutoSW(SF-W): switching is carried out by SF detection in Working side.

• AutoSW(SF-P): switching is carried out by SF detection in Protection side.

• AutoSW(SD-W): switching is carried out by SD detection in Working side.

• AutoSW(SD-P): switching is carried out by SD detection in Protection side.

• AutoSW(SF-Span): Span switch is carried out by SF detection (not for 2F MS-SPRing).

• AutoSW(SF-Ring): Ring switch is carried out by SF detection.

• AutoSW(SD-Span): Span switch is carried out by SD detection (not for 2F MS-SPRing).

• AutoSW(SD-Ring): Ring switch is carried out by SD detection.


Switching priority is:

LKOP or AutoSw(SF-P) > FSW(Span) > FSW(Ring) > AutoSW(SF-Span) > AutoSW(SF-Ring) > AutoSW(SD-P) > AutoSW(SD-Span)

> AutoSW(SD-Ring) > MSW(Span) > MSW(Ring) > WTR


Command DefinitionLockout of working [LKOW] (Ring) LKOW (Ring) inhibits the ring switching for service from Line 1 working

to Line 2 protection or from Line 2 working to Line 1 protection.

Lockout of working [LKOW] (Span) LKOW (Span) inhibits the span switching of service from Line 1 working to Line 1 protection or from Line 2 working to Line 2 protection.

Clear of lockout of working This command is used to release LKOW (Ring) and LKOW (Span).

Lockout of Protection - All Spans [LKOP]

This command is used to inhibit the switching of both lines of a node.

Clear (Lockout of Protection - All Spans)

This command is used to release the Lockout of Protection - All Spans command.

Lockout of protection [LKOP] LKOP inhibits the switching of service to the protection Line.

Forced Switch [FSW] (Span) Span switching is forcibly done.

Forced Switch [FSW] (Ring) Ring switching is forcibly done.

Manual Switch [MSW] (Span) Span switching is manually done.

Manual Switch [MSW] (Ring) Ring switching is manually done.

Clear This command is used to release LKOP, MSW, and FSW.

Exercise (Span) This command is used to check the span switching.

Exercise (Ring) This command is used to check the ring switching.



You can modify the following parameters to the switching operation:

! RGT (Request to Guard Time): if a failed condition has been detected for thisspecified period (Guard Time), NE will regard the condition as a failure.

! WRT (Wait-to-Response Time): in the bi-directional mode, after sending a KByte request, if this specified period has run out without receiving the expected KByte from the opposing NE, NE will regard the condition as a failure.

! FFCT (Fault-Free Confirmation Time): after a failed condition is cleared, NEwaits for this specified period to ensure that the failure is cleared.

! WTR (Wait-to-Restore): in the revertive mode, after a failure is cleared (FFCTprocess has been completed), NE waits for this specified period to confirm thestatus, then switches the line back to the default side.


The switching status and online facility can be confirmed via the CID.

The ONLINE LED (green) on the front of the package lights up when the line of the packageis in the online mode, and goes out when the line is in the offline mode. The maintenanceLED (yellow) on the rack top and MSCB package lights up when the switching command(Lockout, LKOW, LKOP, Forced Switch, or Manual Switch) is successfully completed bythe user.

3.3.4.7 Maintenance

The performance monitoring (PM) detects switching operation and switching time.



3.4 PATH PROTECTION

U-Node WBM supports the Sub-Network Connection Protection (SNC/P) function forhigher-order path and lower-order path. The protection object is the non-terminating path(VC path).

! Operation Method

• 1+1 Unidirectional, Nonrevertive

• 1+1 Unidirectional, Revertive

! Monitoring MethodAccording to the switching status of the object, the SNC/P monitoring method is classifiedinto the following:

• SNC/I: Sub-Network Connection Protection with Inherent Monitoring

• SNC/N: Sub-Network Connection Protection with Non-intrusive Monitoring

3.4.1 Path Protection Mode

The following illustration shows the path protection operation in the SNC/P mode forexample:

NODE 3

NODE 2

NODE 4

NODE 1

NODE 3

NODE 2

NODE 4

NODE 1

! While in Normal Condition ! If a Failure Occurs between NODE 2 and NODE 3

Add-Drop Add-Drop

Add-Drop Add-Drop

Protection — Path Protection3-18


3.4.2 Switching Mode

There are two types of switching modes: command switch by user operation, and automaticswitch by detection of path failure. The following table shows switching commands:


• AutoSW(SF): switching is carried out by SF detection.

• AutoSW(SD): switching is carried out by SD detection.


Switching priority is:

LKOP > FSW > AutoSW(SF) > AutoSW(SD) > MSW > WTR**only when in the revertive mode


You can modify the following parameters for switching operation:

! Hold-Off Time: the delay time before starting to switch from working side toprotection side after a failure is detected.

! WTR (Wait-to-Restore Time): the delay time to wait for the recovery.

! Threshold Value


The switching status and online path can be confirmed via the CID.

The maintenance LED lights up when the switching command (LKOP, Forced Switch, orManual Switch) is successfully completed by the user.

3.4.2.2 Maintenance

The PM function is used to notify users of switching failures. The lit/unlit status of themaintenance LED on NE and MSCB package is interlocked with the Protection operation.

Command Definition

Lockout of protection (LKOP) LKOP inhibits the switching of service to the non-default path.

Forced Switch (FSW) Service is forcibly switched.

Manual Switch (MSW) Service is manually switched.

Clear This command is used to release LKOP, MSW, and FSW.

Protection — Path Protection3-19


3.5 INTERLOCKED RING PROTECTION

NOTE: This configuration is presently not supported.

The U-Node WBM supports the Interlocked Ring Protection that allows traffic from one ringto be interconnected with traffic from another ring. This protection takes place by using pathprotection and ring protection. This connection is made at two nodes, the primary andsecondary nodes, in each ring. The two rings are interconnected in two places to provide analternate traffic path in case of primary node failure. Service selectors (the crossconnectswitching in the PSW40B) in the primary and secondary nodes allow selection betweenincoming aggregate and tributary signals.

The primary source sends the signal to the primary destination; should the signal fail, eitherbecause the line is cut or because one of the primary nodes suffers a failure, the signal isrerouted through the secondary nodes.

At least three nodes must be available for Interlocked Rings. All U-Node WBM nodes arecapable of performing primary node and secondary node functions.

The following illustration shows an example of Interlocked Ring protection:

Path ProtectionCrossconnect

MS-SPRing

MS-SPRing

Path Bridge Crossconnect

(Service Selector)

(Service Selector)

Protection — Interlocked Ring Protection3-20


3.6 OVERHEAD (OH) PROTECTION

OH Protection is used to select the overhead sent from an external NE. This function isinterlocked with the facility’s on-line status (protection status).

3.6.1 Objects for OH Protection

The following are supported:

! RSOH (Regenerator Section Overhead)

! MSOH (Multiplex Section Overhead)

! Non-OH Protection

3.6.2 Types of OH Protection

OH protection is interlocked with the following line protection:

! Linear Line Protection (STM-1/STM-4/STM-16/STM-64)

! 4F MS-SPRing (STM-16)

NOTES:

1. STM-64 Linear Line Protection is not presently supported.

2. 4F MS-SPRing is available only when Span switching is executed.

Protection — Overhead (OH) Protection3-21



Protection3-22 E


4. SYNCHRONIZATION

This section describes the synchronization function as applicable to U-Node WBM.

4.1 SYNCHRONIZATION

4.1.1 Clock Interface

4.1.1.1 External Timing — Incoming

U-Node WBM supports the following external timing (incoming) interfaces. Two systemsof external timing (incoming) go into a PSW40B package. The incoming interface typefollows the registered/mounted package.

• 2,048 kbit/s Without Traffic (120 Ω/75 Ω)

• 2,048 kHz (120 Ω/75 Ω)

• Option: choice of with/without CRC for 2,048 kbit/s.

4.1.1.2 External Timing — Outgoing

U-Node WBM supports the following external timing (outgoing) interfaces. Two systems ofexternal timing (outgoing) go out of a PSW40B package. The outgoing interface typefollows the registered/mounted package.

• 2,048 kbit/s Without Traffic (120 Ω/75 Ω)

• 2,048 kHz (120 Ω/75 Ω)

• Option: choice of with/without CRC for 2,048 kbit/s.

4.1.1.3 SDH Line Timing

As the timing source, a line timing can be selected from the slots of each STM-n interfacepackage.

Synchronization — Synchronization4-1


4.1.1.4 2M PDH Line Timing

When an E12 interface packages is mounted and 2M PDH signal (with traffic) interface isenabled, the U-Node WBM can use 2M line timing for its equipment timing source. From allthe 2M lines of the equipment, any two lines are the only available entries for 2M line timing.

Following shows applications that require 2M PDH line timing:

! U-Node WBM is placed in a station that can provide only 2M PDH line timing(the station does not provide synchronizer other than the exchange’s built-inSSU):

! Both 2M PDH line timing and the external timing are used in the redundantconfiguration, using one of two EXT IN ports for synchronizer, and the other for2M PDH line timing:

U-NODE WBM

E12 PKG PSW40B PKG

SSU

2M PDH LINE

EXCHANGE

SSU: Synchronization Supply Unit

U-NODE WBM

E12 PKG PSW40B PKG

SSU

2M PDH LINE

EXCHANGE

SEL

SSUSSU: Synchronization Supply Unit



4.1.2 Timing Mode

Timing mode can be set by selecting the timing source.

! Normal Mode (Slow Tracking Mode/Locked Mode)

This mode is synchronized with external timing input or SDH Line timing.

! Fast Mode

This is a faster synchronization pull-in mode. Use this mode for testing.

! Holdover Mode

In this mode, if all the timing source inputs are lost, the phase and frequency of the timingsource previously used for the synchronization is held over.

! Freerun Mode

In this mode, an NE operates independently by synchronizing with the internal OSC.

The following illustration shows the timing mode transition:

FORCEDFREE-RUN

MODE

FORCEDHOLDOVER

MODE

FREE-RUNMODE

FORCED FREE-RUN

FORCED FREE-RUN

AUTO SELECTIONOPERATION

FORCED HOLDOVER

AUTO SELECTION OPERATION

HOLDOVERMODE

ACQUIRING

HOLDOVER HOLDOVERMEMORY

VALIDTIMING SOURCE

AVAILABLE

NO VALIDTIMING SOURCEAVAILABLE

VALIDTIMING SOURCE

AVAILABLETIMING SOURCE

NO VALID

AVAILABLETIMING SOURCE

MEMORYACQUIRED

NORMAL MODE

HOLDOVER ACQUISITION TIME

(H/W AUTO SELECTION)

AUTO SELECTIONOPERATION

PROVISIONING

POWER ON(HOT/COLD)



4.1.3 Clock Features

The following clock features apply to ITU-T Standards:

! Freerun Accuracy

! Pull-in/Hold-in/Pull-out Range

! Frequency Drift Alarm

! Holdover Stability

! Noise Tolerance

! Noise Generation

! Phase Transient Response

! Signal Interruption (µ Interruption)

! Reflective Alarm



4.2 TIMING SOURCE CONTROL

The timing source is selected automatically following the priority shown below:

4.2.1 Quality Level

Timing source is selected by the following Quality Level for S1 byte specified in ITU-TStandards. Also, a selection that does not specify QL value is available.

Four ways to set Quality Level are available:

! Quality Level conveyed from SSM

! Support or not SSM

! Forced QL Setting

! Timing Source Failure

4.2.2 Priority Level Setting

The priority level can be specified for all timing sources. Using priority levels, you canspecify timing source as an object to be excluded from the selection as well.

Priority Criteria

1 PL = NSEL

2 Lockout

3 Forced Switch

4 Signal Fail

5 QL

6 QL is DNU (DUS) or higher

7 Manual Switch

8 PL

Synchronization — Timing Source Control4-5


4.2.3 SSM Control

SSM (Synchronization Status Message) contains information for NEs to identify the qualityof Timing Reference. Enabling SSMUSE Function selects the best quality of timingreference each time, instead of accepting one specified quality level. The followinginterfaces support SSM as timing source control:

! Line Facility Signal

You can select whether or not to support SSM on all SDH Line signals.

! 2,048 kbit/s External Clock Signal

You can select whether or not to send/receive SSM to 2,048 kbit/s External Clock with CRCMultiframe Format signal.

Synchronization — Timing Source Control4-6


4.3 TIMING SOURCE SELECTION

The equipment timing source and external output timing source are available for timingsource selection. There are two systems of external output timing sources; they are selectedand controlled individually.

4.3.1 External Output Timing Source Switching Modes

External Output timing source includes the following modes:

! Fixed Timing ModeThe timing source of a line set by the user is output as the external output timing source.

! Auto Switching Timing ModeOne of the specified timing sources is switched automatically within NE and is output asexternal output timing source.

4.3.2 External Output Message Translation Modes

The following modes are available for outputting messages to external output:

! Message Pass Through ModeIn this mode, SSM value that is the origin of synchronization of external output timingsource is always monitored. SSM value is converted to SSM for External Output and isoutput. This mode is supported only when 2,048 kbit/s with CRC interface is used.

! Threshold AIS Generation ModeQL value of output timing source is always monitored. QL value is compared with the QLvalue already set. If the QL value exceeds the set threshold value, AIS generation occurs.If QL value does not exceed the setting value, AIS generation is released.

4.3.3 Signal Fail

If a failure occurs in SDH line signal or external incoming clock, the timing source becomesQL-FAILED when a timing source failure is evaluated as having occurred.

Synchronization — Timing Source Selection4-7


4.3.4 Hold-off Time

A momentary failure that occurs within the specified period (Hold-off Time) is not countedas a timing source failure. The Hold-off Time period has been specified to 1.5 seconds.

4.3.5 SSM Hold-off Time

Under the SSMUSE mode, if the quality level of the incoming timing reference is held for aspecified period (SSM Hold-off Time), the timing reference is selected. Among thecommeasurable timing sources, specifying the SSM Hold-off Time to one with the highestpriority level can avoid unavailing switching that causes wander variations. If a failureoccurs to the timing source, or if an invalid SSM or DNU (Do Not Use) is received, thisholding-off command will be rejected.

4.3.6 Wait-to-Restore Time

Wait-to-Restore Time is the duration to wait before executing the timing source switch, inorder to determine whether or not the recovery is the momentary status.

4.3.7 Switching Control

In automatic switching timing mode, either equipment timing source or external outputtiming source can be selected depending on the command. The following commands areavailable:

! LockoutIf this command is specified to a timing source, that timing source will be excluded fromtiming source selection.

! Forced SwitchSwitching is forcibly carried out to the timing source selected by this command, regardlessof quality level of the target timing source, except when Lockout is specified.

! Manual SwitchSwitching is carried out when a timing source selected by the command has equivalent toor higher level than that of currently selected timing source, where a signal failure does notexist.

! ClearThis command is used to clear the switching command.

Synchronization — Timing Source Selection4-8


4.4 PRECAUTIONS

An improper configuration of timing synchronization causes timing loop. See the followingexample:

4.4.1 Timing Loop Example

The illustration below shows a timing loop that occurs between NODE 1 and BITS/SSU.Between BITS/SSU and NODE 2, the quality levels (QL) for both the incoming andoutgoing are set to the same value, QL_1 (PRS/PRC; G.811). The quality level for theoutgoing from NODE 2 to NODE 1 is set to QL_1 (PRS/PRC; G.811) where the DNURestoration Time is set to OFF:

NODE 1

QL_1IN

NODE 2

OUTQL_1

OUT

IN

NODE 3

QL_1

QL_6

BITS/SSU

QL_1QL_1

NODE 1

IN

NODE 2

OUTQL_9

OUT

IN

NODE 3

QL_1

BITS/SSU

(PRC; G.811)

(PRC; G.811)(PRC; G.811)

(PRC; G.811)

(SETS)

(PRC; G.811)

(DNU)

QL_1(PRC; G.811)

QL_1(PRC; G.811)

(PRC; G.811)

Change the setups as shown below to stop the timing loop:

DNU Restoration Time is set to any value but OFF.

QL_1

(PRC; G.811)

QL_6

(SETS)

Synchronization — Precautions4-9



Synchronization4-10 E


5. CONFIGURATION MANAGEMENT

This section describes inter-NE management and control methods to manage/control NE.

5.1 CONFIGURATION MANAGEMENT OBJECT

U-Node WBM has items to define and control NE operation; the items are calledManagement Objects. The following table shows the Management Objects for U-NodeWBM.

Classification Object Description

Equipment NODE NE Component (See 5.1.1)

SHELF Shelf Component (See 5.1.2)

PKG (Package) PKG Component (See 5.1.3)

MEMCARD (Memory Card) Memory card inter-MSCB (See 5.1.3)

CPU CPU (See 5.1.4)

Facility Line Facilities Object of each layer of interface (See 5.1.5)

EXTCLK External Clock Interface (See 5.1.6)

Switch Group Protection Switch Group GRP for Package Switching of PSW40B (See 5.1.7)

Synchronization SYNC Common GRP for Timing Source (See 5.1.8)

Overhead OHCH Overhead Access Channel (See 5.1.9)

RSDCC RS-DCC (LAPD) Management Function (See 5.1.10)

MSDCC MS-DCC (LAPD) Management Function (See 5.1.10)

Others HKC Housekeeping Control (See 5.1.11)

HKA Housekeeping Alarm (See 5.1.11)

V11PORT V.11 Port (See 5.1.12)

ASAP Alarm Severity Profile (Alarm Severity Assignment Profile)

THP TCA Threshold Profile

VCT Virtual Concatenation [supported from Release 2.1]

GFPCT Channel ID [supported from Release 2.1]

Configuration Management — Configuration Management Object5-1


5.1.1 NODE (NE: Network Element)

This is the object that represents the network element (NE).

5.1.2 SHELF

This is the object that represents the shelf. U-Node WBM uses a WBM shelf:

Shelf Name Function

WBM The WBM shelf has management/control of NE and crossconnect functions. It contains up to SDH Optical Interface, PDH Interface, STM1E Interface, and Ethernet Interface.



5.1.3 PKG (Package)

This is the object that represents package components. The following table shows a list ofpackage objects.

5.1.3.1 SINFM PKG

Multiple lines (OPn) are equipped on one SINFM PKG. The optical stick component(physical layer) can be mounted/dismounted as shown below. See the Package Description/Installation manual for details.

Package Name Main Function

MSCB NE Control Management

PSW40B Crossconnect + Path Switching + Clock

OHC OH Management, LAPD Termination, HKA, HKC

SSCB Protection Management

SINF64(B) STM-64 Interface; colored/non-colored [supported from Release 2.1]

SINF16/SINF16(B) STM-16 Interface; colored/non-colored

SINFM with OP4OP1

STM-4 Interface (1 to 4 lines) and STM-1 Interface (1 to 16 lines).By mounting OPn, either interface is available.

STM1E with STM1TRME4TRM

STM1-e Electrical Interface (1 to 16 lines); or E4 Electrical Interface

E12 2M Electrical Interface (1 to 63 lines)



GBEM 1000BASE-SX or 1000BASE-LX Ethernet Interface (multiple packets)[supported from Release 2.1]

FEH 100BASE-TX and 10BASE-T Ethernet Interface (1 to 8, or to 16 lines)[supported from Release 2.1]

MEMB Holding backup data and F/W. Size: 32 MByte

#16: OP1

#15: OP1

#14: OP1

#1: OP4

SINFM



5.1.3.2 Slot Number

The following table defines the slot number of each shelf. The slot numbers below areretrieved by the Inventory as AIDs to indicate the locations of slots. The mounting slot isfixed for each package.

Slot #7 (INF P) is used only for a protection package of E12 (2M interface).

MS

CB

SS

CB

PS

W40

B

PS

W40

B

SLOT # 3

OH

C

4 5 6 1819 20 217 8 9 1011 12 13 1415 1617

INF

#1

INF

#2

INF

#3

INF

#4

INF

(E

12 P

RO

TE

CT

ION

)IN

F #

5IN

F #

6IN

F #

7IN

F #

8IN

F #

8

INF

#9

INF

#10

INF

#11

INF

#12

INF

#13

INF

#14

INF

#15

INF

#16

TR

M #

1T

RM

#2

TR

M #

3T

RM

#4

TR

M #

8T

RM

#7

TR

M #

6T

RM

#5

1 2 22



5.1.4 CPU

This is the object representing a CPU which controls a package. The following table showsobject names of CPUs, and those of packages where CPUs are equipped.

PKG CPU Remark

MSCB SCBCPU ––––––

AGCPU ––––––

PSW40B PW40BCPU ––––––

OHC OHCPU Three CPUs can be equipped on one PKG.

SSCB SWBCPU ––––––

SINF64(B) IF64CPU [supported from Release 2.1]

SINF16 IFCPU ––––––

SINFM IFCPU ––––––

STM1E IFCPU ––––––

E12 E12CPU ––––––

E31 E31CPU ––––––

E32 E32CPU ––––––

GBEM GEMUCPU [supported from Release 2.1]

FEH FEHCPU [supported from Release 2.1]



5.1.5 Facility

This object controls each layer signal in the transmission line. The following table showsfacility names and functions.

5.1.6 External Clock (EXTCLK)

This object controls the external clock. PSW40B package has a clock function and providesan external clock. The following table shows EXT CLK object names and PSW packagetypes.

Facility Function Corresponding PKG

SINF64F STM-64 Interface [supported from Release 2.1] SINF64(B)

SINF16F STM-16 Interface SINF16/SINF16(B)

SINFMF STM-4, STM-1 Interface SINFM

GBEMF 1000BASE-SX/LX Ethernet Interface; multiple packets[supported from Release 2.1]

GBEM

FEHF 100BASE-TX/10BASE-T Ethernet Interface[supported from Release 2.1]

FEH

E12F 2M (electrical) Interface E12



STM1EF STM1e (electrical) Interface STM1E

AU3 Section Adaptation [supported from Release 2.1] GBEM/FEH

AU4 Section Adaptation SINF64(B)/SINF16/SINF16(B)/SINFM/STM1E

HPMON4 Higher-order Path Monitor SINF64(B)/SINF16/SINF16(B)/SINFM/STM1E

LPMON Lower-order Path Monitor PSW40B

HPT Higher-order Path Termination PSW40B

HPTM3 GBEM High-order Path Termination [supported from Release 2.1]

GBEM/FEH

LPT Lower-order Path Termination E12/E31/E32

SDHTU TU Termination Point on SDH Interface Side PSW40B

PDHTU TU Termination Point on PDH Interface Side E12/E31/E32

Object Name PSW PKG Type Clock Interface

EXC2MH 2 MHz 2 MHz Clock (75/120 Ω)

EXC2MB 2 Mbit/s 2 Mbit/s (75/120 Ω)



5.1.7 Switch Group

This object manages Package Protection and Line Protection (Linear/MS-SPRing). Thefollowing table shows SW Group names and functions.

Refer to the General Information manual: 2. Application, and/or 3. Protection in thismanual for interface packages and available configuration.

5.1.8 Synchronization

This is not a physical object but is controlled logically by PSW40B packages.

SW GRP Name Function

PSWS PSW40B Package Protection Control

INFNS E12 Package Protection Control

INFS E31/E32 Package Protection Control

STM1ES STM1E Package Protection Control

LINES Linear Protection Control

MS2FS 2-Fiber MS-SPRing Protection Control (only for SINF16F and SINF64F* facilities)

MS4FS 4-Fiber MS-SPRing Protection Control (only for SINF16F facilities)

*: SINF64F is supported from Release 2.1.

SYNC Function

SYNCG This object is used to control common components for Internal Timing Source Selec-tion Group (SYNCISG) and External Clock Timing Source Selection Group (SYNC-ESG).

SYNCU This object is used to control common components for Internal Timing Source Unit (SYNCISU) and External Clock Timing Source Unit (SYNCESU). The PSW40B package, manages SYNCU objects to monitor STM-n line clocks, external clock, and 2M line clock with traffic.

SYNCISG This object is used to control Internal Timing Source selection.

SYNCISU This object is used to control the configuration (source) of Internal Timing Source selection.

SYNCESG This object is used to control External Clock Timing Source selection.

SYNCESU This object is used to control the configuration (source) of External Clock Timing Source selection.



5.1.9 Overhead Access Channel (OHCH)

OHCH is used to manage the line facility that connects an SDH Line facility overhead toMSDCC, RSDCC, V.11 Interface, E1DB (Digital Branch), and E2DB. OHC PKG supportsOHCH.

5.1.10 Data Communication Channel (DCC)

DCC is the object used to manage LAPD for a management network with the datacommunication channel.

NOTE: MSDCC can be selected for SINF64F (supported from Release 2.1) and SINF16Ffacilities.

5.1.10.1 OHC Package Type and DCC

NOTE: DCC number should be registered at the OHC Package parameter settings.

5.1.11 HKC/HKA

HKC is the object that represents intra-office Housekeeping Control function. HKA is theobject that represents intra-office Housekeeping Alarm function.

5.1.12 V.11 Port

V.11 Port is the object that provides the V.11 loopback function.

Data Communication Channel (DCC) Type

DCC Type Function Corresponding PKG

RSDCC RS-DCC (LAPD) Management OHC

MSDCC MS-DCC (LAPD) Management

PKG Type DCC Number RSDCC/MSDCC CH Number

AAxx 4CH RSDCC 4CH

ABxx 8CH RSDCC 8CH

ACxx 12CH RSDCC 8CH, MSDCC 4CH



5.2 SERVICE STATE

To manage equipment configuration, the status for providing service to each object describedabove is defined as its Service State. There are the following functions: Notification ofservice state to maintenance personnel and unnecessary alarm inhibition from an out-of-service object. Some functions are restricted, according to service state.

5.2.1 Service State Definition

There are the following two service state parameters:

! PST (Primary Service State) This indicates primary service state of object.

! SST (Secondary Service State) This is additional information for PST. This indicates cause of PST state or state change.SST is issued for PKG object only.

5.2.1.1 Primary Service State (PST)

5.2.1.2 Secondary Service State (SST)

PST Type PST Name Definition

IS-NR In Service Normal Service is provided normally.

IS-ANR In Service Abnormal Service is provided abnormally as a failure occurs.

OOS-MT Out of Service Maintenance Service is out momentarily for maintenance (for PKG only).

OOS-MA-AS Out of Service Memory Administration Assigned

Service is not provided; but administration information issaved.

OOS-MA-UAS Out of Service Memory Administration Un-Assigned

Service cannot be provided because administration informa-tion is deleted.

SST Type SST Name Definition

MEA Mismatch of Equipment and Attribute

PKG is improperly equipped (for PKG only).

AINS Automatic In-Service Service will be in-service automatically according to PKGequipped status (for PKG only).

EQ Equipped PKG is equipped in NE (for PKG only).

UEQ Unequipped PKG is not equipped in NE (for PKG only).

Configuration Management — Service State5-9


5.3 OTHER ADMINISTRATION STATES

5.3.1 Port Mode

The object holding the incoming signal supports Port Mode as specified in ITU-T G.783, andmanages the Port Mode state.

Port Mode is set to manage Line Facility (main signal interface), PDH Interface Facility (forE12, E31 and E32), and EXT CLK (External Clock Interface). There are two Port Modes:

! AUTOThe AUTO mode inhibits MON, in order to avoid reporting the detected LOS at theinitial power-up. Once the first detected LOS is cleared, the mode is automaticallychanged to MON (normal mode). The AUTO mode will also be changed to MON byremoving/re-installing an interface package and/or optical stick.

! MONIn the MON mode, a detected alarm is always reported (normal mode). This mode is alsoset by removing/re-installing an interface package and/or optical stick in the AUTOmode.

5.3.2 Mode Mismatch

The package type settings are required to register the packages shown in the table below. Ifthe installed package and setting do not match, this function generates an alarm.

NOTES:

1. Mode Mismatches shown above are managed as alarm states.

2. GBEM and FEH packages are supported from Release 2.1.

PKG Mode Mismatch Definition

OHC PKG MODEMIS OHCMODE (PCM coding method) set by user andthe installed package group do not match.

CHMIS CHMODE (DCC support channel number) set byuser and the installed package do not match.

PSW40B PKG MODEMIS PSWMODE (external clock support type) set byuser and the installed package group do not match.

STM1E/GBEM/FEH PKG CHMIS CHMODE (number of facilities) set by user and theinstalled package group do not match.

E12 PKG MODEMIS PDHMODE (2M interface impedance) set by userand the installed package group do not match.

Configuration Management — Other Administration States5-10


5.4 MEMORY BACKUP

5.4.1 Overview

U-Node WBM provides multi-memory backup of the MSCB package by using a memorycard (non-volatile memory). Restoration of data is possible in the following cases: nodefailure, package replacement, and power failure. Memory card is mounted on MSCBpackage; it can be mounted or dismounted from the front of the package.

5.4.2 Memory Configuration

The following illustration shows the backup configuration of U-Node WBM.

NOTE: Download/Upload function via the CID will be supported in the future.

front side

MSCB PACKAGE

MEMORYCARD

ACT Memory

ACT Memory

ACT

RAM

Command

Periodic/Command

Auto BackupStoring Area

FROM

Backup (SUB) Storing Area

Memory Card

Real Time

Command

Command

User Backup (USR) Storing Area

Upload

Download

Upper OS

Data Upload/Download Function

Cold StartDefault Data (DEF)

Storing Area

Configuration Management — Memory Backup5-11


The following describes Memory Areas shown in the above illustration:

! Auto Backup Area on Memory Card (Auto Backup Storing Area)U-Node WBM uses System Administrative information for ACT (RAM). Theinformation is backed up into the auto backup area of the memory card in real time.

! Flash Memory on MSCB PKG (Backup Storing Area)ACT (RAM) information is periodically backed up onto the SUB side on the MSCBpackage. Backup by user operation is also available. This area is used to provide multi-memory backup by combining this area and the backup area on the memory card.

! User Area on Memory Card (User Backup Storing Area)When copy command is issued, ACT (RAM) information is backed up onto user area onthe memory card. The use of this backup area can be defined by the user.

! Default InformationDefault information is held in MSCB package F/W program. The settings of the factorydefault information cannot be modified.

Configuration Management — Memory Backup5-12


5.5 STARTING UP NE

5.5.1 Hot Start

In Hot Start mode, the U-Node WBM starts up according to previously set systemadministration information (customized provisioning data). Starting up in the Hot Startmode does not change the NE setups. Hot Start can be carried out by pressing the RESETbutton on the MSCB package, or by issuing a restart command by CID operation.

Hot Start should be performed in the following cases:

! After the recovery of power failure

! After PKG replacement

5.5.2 Cold Start

Cold Start is the other starting mode that starts up the equipment with the factory defaultprovisioning data. This mode goes in when the equipment is powered up for the first timewhere no customized provisioning data has been registered, or when the maintenancepersonnel starts up NE with the default administration information stored in default memory(DEF) on purpose.

The following two methods may be used:

! Restart by issuing memory backup (the Restore command is issued to restore the defaultinformation).

! Restart by pressing the COLD button and RESET button on MSCB package (refer to6.2.1 Restore the Factory Default Settings in the Operation and Maintenance manualfor the precise operation).

Configuration Management — Starting Up NE5-13


5.6 INVENTORY

5.6.1 Package Inventory

Each package and optical stick stores information to identify itself as shown below. Theinformation can be retrieved.

5.6.2 NE Information Inventory

Network elements have TID (Target Identifier: equipment identity) and NE Addressinformation for remote access. The following table defines default TID and NE address.

This NE Address is used for the download function from CID to remote station; it is not theIP Address used for network management.

ITEM DESCRIPTION

Shelf Location where the selected object is installed.

Slot Location where the selected object is installed.

PKG Package name.

ID Code NEC ID code number of the selected object.

Serial No. Serial product number of the selected object.

PKG Version Release version of the selected object.

BAR Code (not used)

CLEI Code (not used)

History Reference number (for factory use).

CPU Name CPU name of the selected object, if applicable.

Boot Boot firmware version.

Active Version of firmware that is currently running.

Primary Version of firmware stored in Primary memory.

Secondary Version of firmware stored in Secondary memory.

NE TID NE Address

ADM SWUN-ADM-DEFAULT 200.200.200.200

Configuration Management — Inventory5-14


5.7 OBJECT AIDS

The following shows the syntax for each management object’s AID (Access Identifier). TheU-Node WBM specifies these AIDs that are required to control/report objects to/from CIDand upper OS using TL1 interface.

NOTE: “BAY” is defined as a set of systems. For the U-Node WBM, “1” is applied to all itsobjects.

5.7.1 Node

! AID Syntax: (object tag)

NOTE: Node objects are managed by the MSCB package.

5.7.2 Shelf

! AID Syntax: object tag – bay – shelf ID

OBJECT TAG

Node NODE

OBJECT TAG – BAY – SHELF NOTES

WBM Shelf SHELF – 1 – 1 ——

Configuration Management — Object AIDs5-15


5.7.3 Package

! AID Syntax: object tag – bay – shelf ID – slot#

OBJECT TAG – BAY – SHELF – SLOT NOTES

MSCB MSCB – 1 – 1 – 1 ——

SSCB SSCB – 1 – 1 – 2 ——

OHC OHC – 1 – 1 – 22 ——

SINF64(B)* SINF64 – 1 – 1 – m m (slot#) = 4 or 6

SINF16(B) SINF16 – 1 – 1 – m m (slot#) = 3 thru 6, 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

SINF16 SINF16 – 1 – 1 – m m (slot#) = 4, 6, 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

SINFM SINFM – 1 – 1 – m m (slot#) = 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

STM1E STM1E – 1 – 1 – m m (slot#) = 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

GBEM* GBEM – 1 – 1 – m m (slot#) = 9, 11, 15, 17, 19, 21

FEH* FEH – 1 – 1 – m m (slot#) = 9, 11, 15, 17, 19, 21

E12 E12 – 1 – 1 – m m (slot#) = 7 thru 11, 14 thru 17



PSW40B PSW40B – 1 – 1 – m m (slot#) = 12 or 13

* These packages are supported from Release 2.1.



5.7.4 CPU

! AID Syntax: object tag – bay – shelf ID – slot# – CPU#

OBJECT TAG – BAY – SHELF – SLOT – CPU# NOTES

SCBCPU SCBCPU – 1 – 1 – 1 – 1 MSCB

AGCPU AGCPU – 1 – 1 – 1 – 1 MSCB

SWBCPU SWBCPU – 1 – 1 – 2 – 1 SSCB:

OHCPU OHCPU – 1 – 1 – 22 – c OHCc (CPU#) = 1 thru 3

PW40BCPU PW40BCPU – 1 – 1 – m – 1 PSW40B:m (slot#) = 12 or 13

IF64CPU IF64CPU – 1 – 1 – m – 1 SINF64(B)*:m (slot#) = 4, 6

IFCPU IFCPU – 1 – 1 – m – 1 SINF16(B):m (slot#) = 3 thru 6, 9, 11, 15, 17, 19, 21 [slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

IFCPU – 1 – 1 – m – 1 SINF16:m (slot#) = 4, 6, 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

IFCPU – 1 – 1 – m – 1 SINFM/STM1E:m (slot#) = 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

GEMUCPU GEMUCPU – 1 – 1 – m – 1 GBEM*:m (slot#) = 9, 11, 15, 17, 19, 21

FEHCPU FEHCPU – 1 – 1 – m – 1 FEH*:m (slot#) = 9, 11, 15, 17, 19, 21

E12CPU E12CPU – 1 – 1 – m – 1 E12:m (slot#) = 7 thru 11, 14 thru 17



*: These packages are supported from Release 2.1.



5.7.5 Memory Card

! AID Syntax: object tag – bay – shelf ID – slot# – card#

5.7.6 Temporary Memory


Memory Card TAG – BAY – SHELF – SLOT – CARD NOTES

MEMB MEMB – 1 – 1 – 1 – 1 MSCB package

OBJECT TAG

Temporary Memory TMP



5.7.7 Line Facility

! AID Syntax: object tag – bay – shelf ID – slot# – line

OBJECT(TARGET SIGNAL

PACKAGE)

TAG – BAY – SHELF – SLOT – LINE NOTES

STM-64* SINF64F – 1 – 1 – m – 1 m (slot#) = 4 or 6

STM-16 SINF16F – 1 – 1 – m – 1 m (slot#) = 3 thru 6, 9, 11, 15, 17, 19, 21[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

STM-4 SINFMF – 1 – 1 – m – l m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1, 5, 9, 13[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

STM-1 SINFMF – 1 – 1 – m – l m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

STM-1e STM1EF – 1 – 1 – m – l m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

GBEM* GBEMF – 1 – 1 – m – l m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 4

FEH* FEHF – 1 – 1 – m – l m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16

E12 E12F – 1 – 1 – m – l m (slot#) = 8 thru 11, 14 thru 17l (line) = 1 thru 63



*: These signal levels are supported from Release 2.1.



5.7.8 Package Protection Switch Group

! AID Syntax: object tag – bay – shelf ID – slot#

5.7.9 Line Protection Switch Group


OBJECT(Switch Group)

TAG – BAY – SHELF – SLOT NOTES

STM1E STM1ES – 1 – 1 – m STM1E interface packagem (slot#) = 11, 17, 21[slots #11 and 17 are not available for Release prior to 1.2.]

E12 INFNS – 1 – 1 – 7 E12 interface package

E31/32 INFS – 1 – 1 – m E31, E32 interface packages:m (slot#) = 9, 11, 15 or 17

PSW40B PSWS – 1 – 1 – 13 PSW40B package

OBJECT(Switch Group)

TAG – BAY – SHELF – SLOT – LINE NOTES

Linear LINES – 1 – 1 – 6 – 1 SINF64 interface package[currently not supported]

LINES – 1 – 1 – m – 1 SINF16(B) interface package:m (slot#) = 4, 6, 11, 17, 21[slots #11 and 17 are not available for Release prior to 1.2.]

LINES – 1 – 1 – m – 1 SINF16 interface package:m (slot#) = 6, 11, 17, 21[slots #11 and 17 are not available for Release prior to 1.2.]

LINES – 1 – 1 – m – l SINFM interface package (OP1):m (slot#) = 6, 11, 17, 21l (line#) = 1 thru 16[slots #11 and 17 are not available for Release prior to 1.2.]

LINES – 1 – 1 – m – l SINFM interface package (OP4):m (slot#) = 6, 11, 17, 21l (line#) = 1, 5, 9, 13[slots #11 and 17 are not available for Release prior to 1.2.]

2F MS-SPRing MS2FS – 1 – 1 – 6 – 1 SINF64(B) interface package[supported from Release 2.1]

MS2FS – 1 – 1 – m – 1 SINF16(B) interface package:m (slot#) = 4 or 6

MS2FS – 1 – 1 – 6 – 1 SINF16 interface package

4F MS-SPRing MS4FS – 1 – 1 – 6 – 1 SINF16(B) interface package



5.7.10 Synchronization

! AID Syntax: object tag – bay – shelf ID – slot# – timing group – timing line

OBJECT TAG – BAY – SHELF – SLOT – T-GRP – T-LINE NOTES

Timing Source Group

SYNCG – 1 – 1 – 13 – 1 ——

Internal Timing Source Group

SYN-CISG

– 1 – 1 – 13 – 1 ——

External Timing Source Group

SYNC-ESG

– 1 – 1 – 13 – t t (timing group) = 1 or 2

Timing Source Unit

SYNCU – 1 – 1 – 13 – 1 – l l (timing line) = 1 thru 20

Internal Timing Source Unit

SYN-CISU

– 1 – 1 – 13 – 1 – l l (timing line) = 1 thru 20

External Timing Source Unit

SYN-CESU

– 1 – 1 – 13 – t – l t (timing group) = 1 or 2l (timing line) = 1 thru 18



5.7.11 Path Facility

5.7.11.1 Higher-Order Path

! AID Syntax: object tag – bay – shelf ID – slot# – line – time slot

OBJECT TAG – BAY – SHELF – SLOT – LINE – T-SLOT NOTES

AU-3 Path

VC-4-1V ~ 16V

VC-4-4c

VC-4-16c

AU3 – 1 – 1 – m – l – t GBEM*:m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 4t (time slot) = 1 thru 48 (1, 4, 7, 10, …, 46)

AU3 – 1 – 1 – m – l – t FEH*:m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16t (time slot) = 1 thru 48 (1, 4, 7, 10, …, 46)

AU-4 Path

VC-4

VC-4-4c

VC-4-16c

VC-4-64c†

AU4 – 1 – 1 – m – 1 – t SINF64(B)*:m (slot#) = 4, 6t (time slot) = 1 thru 64

AU4 – 1 – 1 – m – 1 – t SINF16(B):m (slot#) = 3 thru 6, 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 16[slots #9, 11, 15 and 17 are not available for Release prior to 1.2.]

AU4 – 1 – 1 – m – 1 – t SINF16:m (slot#) = 4, 6, 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 16[slots #9, 11, 15 and 17 are not available for Release prior to 1.2.]

AU4 – 1 – 1 – m – l – t SINFM (OP4):m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1, 5, 9 or 13t (time slot) = 1 thru 4[slots #9, 11, 15 and 17 are not available for Release prior to 1.2.]

AU4 – 1 – 1 – m – l – 1 SINFM (OP1), STM1E:m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16[slots #9, 11, 15 and 17 are not available for Release prior to 1.2.]

*: These facilities and levels are supported from Release 2.1.

†: This level is not presently supported.



5.7.11.2 Lower-Order Path (to/from SDH)

! AID Syntax: object tag – bay – shelf ID – slot# – line – time slot – TUG3 – TUG2 – TU

5.7.11.3 Lower-Order Path (to/from PDH)


OBJECT TAG – BAY – SHELF – SLOT – LINE – T-SLOT – TUG3 – TUG2 – TU NOTES

TU-3 Path

SDHTU – 1 – 1 – 13 – 1 – t – s – 1 – 1 t (time slot) = 1, 4, 7, 10, …, 94s (TUG3#) = 1 thru 3

TU-12 Path

SDHTU – 1 – 1 – 13 – 1 – t – s – r – q t (time slot) = 1, 4, 7, 10, …, 94s (TUG3#) = 1 thru 3r (TUG2#) = 1 thru 7q (TU#) = 1 thru 3

OBJECT TAG – BAY – SHELF – SLOT – LINE NOTES

TU-3 Path PDHTU – 1 – 1 – m – l E31/E32:m (slot#) = 8 thru 11, 14 thru 17l (line) = 1 thru 6

TU-12 Path PDHTU – 1 – 1 – m – l E12:m (slot#) = 8 thru 11, 14 thru 17l (line) = 1 thru 63



5.7.12 Path Monitor



5.7.12.2 Lower-Order Path

! AID Syntax: object tag – bay – shelf ID – slot# – line – time slot – TUG3 – TUG2 – TU


HPMON4

VC-4

VC-4-4c

VC-4-16c

HPMON4 – 1 – 1 – m – 1 – t SINF64(B)*:m (slot#) = 4, 6t (time slot) = 1 thru 64

HPMON4 – 1 – 1 – m – 1 – t SINF16(B):m (slot#) = 3 thru 6, 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 16[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

HPMON4 – 1 – 1 – m – 1 – t SINF16:m (slot#) = 4, 6, 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 16[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

HPMON4 – 1 – 1 – m – l – t SINFM (OP4):m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1, 5, 9, 13t (time slot) = 1 thru 4[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

HPMON4 – 1 – 1 – m – l – 1 SINFM (OP1), STM1E:m (slot#) = 9, 11, 15, 17, 19, 21l (line) = 1 thru 16[slots #9, 11, 15 and 17 are not avail-able for Release prior to 1.2.]

*: SINF64(B) is not supported for Release prior to 1.2.

OBJECT TAG – BAY – SHELF – SLOT – LINE – T-SLOT – TUG3 – TUG2 – TU NOTES

LPMON

TU-3LPMON – 1 – 1 – 13 – 1 – t – s – 1 – 1 t (time slot) = 1, 4, 7, 10, …, 94

s (TUG3#) = 1 thru 3

LPMON

TU12LPMON – 1 – 1 – 13 – 1 – t – s – r – q t (time slot) = 1, 4, 7, 10, …, 94

s (TUG3#) = 1 thru 3r (TUG2#) = 1 thru 7q (TU#) = 1 thru 3



5.7.13 Path Termination Point



5.7.13.2 Lower-Order Path


5.7.14 External Clock Input

! AID Syntax: object tag – bay – shelf ID – slot# – port#


HPT3(AU-4)

HPT – 1 – 1 – 13 – 1 – t PSW40B:t (time slot) = 1, 4, 7, 10, …, 94

HPTM3(GBEM)*

HPTM3 – 1 – 1 – m – 1 – t m (slot#) = 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 48 (1, 4, 7, 10, …, 46)

HPTM3(FEH)*

HPTM3 – 1 – 1 – m – 1 – t m (slot#) = 9, 11, 15, 17, 19, 21t (time slot) = 1 thru 48 (1, 4, 7, 10, …, 46)

*: GBEM and FEH are supported from Release 2.1.

OBJECT TAG – BAY – SHELF – SLOT – LINE NOTES

LPT(TU-3)

LPT – 1 – 1 – m – l E31/E32:m (slot#) = 8 thru 11, 14 thru 17l (line) = 1 thru 6

LPT(TU-12)

LPT – 1 – 1 – m – l E12:m (slot#) = 8 thru 11, 14 thru 17l (line) = 1 thru 63

OBJECT(TIMING REFERENCE)

TAG – BAY – SHELF – SLOT – PORT NOTES

2 MHz EXC2MH – 1 – 1 – 13 – p p (port#) = 1 or 2

2 Mbit/s EXC2MB – 1 – 1 – 13 – p p (port#) = 1 or 2



5.7.15 Housekeeping Alarm


5.7.16 Housekeeping Control


5.7.17 V11 User Channel Port


5.7.18 Overhead Access Channel


5.7.19 Data Communication Channel (DCC Port)


OBJECT TAG – BAY – SHELF – SLOT – PORT NOTES

Housekeeping Alarm HKA – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 16


Housekeeping Control HKC – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 8


V11 Port V11PORT – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 6


OH Access OHCH – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 20


DCC PortRegenerator

Section

RSDCC – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 8

DCC PortMultiplexer

Section

MSDCC – 1 – 1 – 22 – p OHC:p (port#) = 1 thru 4



5.7.20 Virtual Concatenation (GBEM/FEH)


NOTE: VCT is available from Release 2.1 where GBEM/FEH interface package is supported.

5.7.21 Channel ID (GBEM/FEH)

! AID Syntax: object tag – bay – shelf ID – slot# – channel ID

NOTE: GFPCT is available from Release 2.1 where GBEM/FEH interface package issupported.

5.7.22 Profile

! AID Syntax: object tag – bay – shelf ID – file#

5.7.23 All



Virtual Concatenation(VCT)

VCT – 1 – 1 – m – p GBEM:m (slot #) = 9, 11, 15, 17, 19, 21p (port#) = 1 thru 4

VCT – 1 – 1 – m – p FEH:m (slot #) = 9, 11, 15, 17, 19, 21p (port#) = 1 thru 4

OBJECT TAG – BAY – SHELF – SLOT – ID NOTES

Packet Connection(GFPCT)

GFPCT – 1 – 1 – m – i GBEM:m (slot #) = 9, 11, 15, 17, 19, 21i (ID) = 1 thru 255

GFPCT – 1 – 1 – m – i FEH:m (slot #) = 9, 11, 15, 17, 19, 21i (ID) = 1 thru 255

OBJECT TAG – BAY – SHELF – FILE NOTES

Alarm Severity Assignment Profile ASAP – 1 – 1 – f f (file#) = 1 thru 50

Threshold Profile THP – 1 – 1 – f f (file#) = 1 thru 50

OBJECT (AID)

all applicable objects ALL




Configuration Management5-28 E


6. PERFORMANCE MONITORING

This section describes Performance Monitoring, Intermediate Path Performance Monitoring(IPPM) function, and the processes involved in Performance Monitoring.

6.1 PERFORMANCE MONITORING (PM) TYPE

PM monitor type and its count definition in U-Node WBM are described below according tothe layer.

6.1.1 Physical Layer

Following are the PM monitor types and their definitions of SDH Physical Layer:

Following are the supported monitor types for each facility:

NOTE: STM64 interface is supported from Release 2.1.

PM Monitor Type Definition

OPT (Optical Power of the Transmitter) Current value of transmit level

OPR (Optical Power of the Received signal) Current value of receive level

Target Line Facility Monitor Type

STM64NOTE/STM16 OPT and OPR

Performance Monitoring — Performance Monitoring (PM) Type6-1


6.1.2 Regenerator Section Layer

Following shows the PM monitor types and their definitions of SDH Regenerator SectionLayer:

Following are the monitoring parameter, monitoring point, and monitoring span at NODE 1for each facility:


Near-End

BBE (Near-End Background Block Error) Cumulative value of error block count. B1 is counter value.

ES (Near-End Errored Seconds) EB (Error Block) occurrence is checked per second. If EB occurs or Defect is detected, seconds (time) are accumulated.

SES (Near-End Severely Errored Seconds) If EB count exceeds K times (see 6.1.15 SES Threshold) per second or Defect is detected, seconds (time) are accumulated.

UAS (UnAvailable Seconds) Cumulative value of UAT (UnAvailable Time).

OFS (Out-of-Frame Seconds) OOF (Out of Frame) detection is checked per second. If OOF is detected, seconds (time) are accumulated.

Target Facility Monitoring Parameter Monitoring Point Monitoring Span

Near-End

STM1E RS-BBE, RS-ES, RS-SES, RS-UAS, RS-OFS 1 2 → 1

STM64*/16/4/1 RS-BBE, RS-ES, RS-SES, RS-UAS, RS-OFS 1 2 → 1

*: STM64 facility is supported from Release 2.1.

NODE 2(Regenerator)

2

NODE 1

1

NODE 3



6.1.3 Multiplex Section Layer

Following are the PM monitor types and their definitions of SDH Multiplex Section Layer:

Following are the monitoring parameter, monitoring point, and monitoring span at NODE 1for each facility:


Near-End





Far-End

FEBBE (Far-End Background Block Error) Cumulative value of FEEB (Far-End Errored Block) indi-cated with REI_bit count. M0 is counter value.

FEES (Far-End Errored Seconds) FEEB indicated with REI_bit or RDI detection is checked per second. If FEEB or RDI occurs, seconds (time) are accumulated.

FESES (Far-End Severely Errored Seconds) If FEEB indicated with REI_bit count exceeds K times per second or RDI is detected, seconds (time) are accumulated.

FEUAS (Far-End UnAvailable Seconds) Cumulative value of FEUAT (Far-End UnAvailable Time).


Near-End

STM64*/16/4/1 MS-BBE, MS-ES, MS-SES, MS-UAS 4 3 → 4

STM1E MS-BBE, MS-ES, MS-SES, MS-UAS 4 3 → 4

Far-End

STM64*/16/4/1 MS-FEBBE, MS-FEES, MS-FESES, MS-FEUAS 4 1 → 2

STM1E MS-FEBBE, MS-FEES, MS-FESES, MS-FEUAS 4 1 → 2


NODE 2(Regenerator)NODE 1

4

1

NODE 3

2

3



6.1.4 E12/E31/E32 Line Layer

Following are the PM monitor types and their definitions for E12/E31/E32 Line Layer:

Following are the monitoring parameter, monitoring point and monitoring span at NODE 1for each facility:


Near-End

CV (Code Violation) Occurrence time of Code rule violation. BPV is counter value.

ES (Near-End Errored Seconds) CV (Code Violation) occurrence is checked per sec-ond. If CV occurs or Defect is detected, seconds (time) are accumulated.

SES (Near-End Severely Errored Seconds) If CV count exceeds K times (see 6.1.15 SES Thresh-old) per second or Defect is detected, seconds (time) seconds accumulated.


Near-End

E12F/E31F/E32F CV-L, ES-L, SES-L 2 1 → 2

U-NODE WBM

Terminated E12/E31/E32 Node

1

E12/E31/E32 Signal

2

NODE 1



6.1.5 1000BASE-X Interface (GBEM)

NOTE: This interface is available from Release 2.1 where GBEM package is supported.

Following are the PM monitor types and their definitions for 1000BASE-SX/1000BASE-LXEthernet interfaces:


RX_BRD_OK The number of valid broadcast packets with packet sizes between 64 bytes and the maximum when received.

RX_ERR The number of discarded erred incoming packets.

RX_INV The number of discarded invalid incoming packets.

RX_LONG The number of packets that exceed the maximum packet size when received.

RX_MLT_OK The number of valid multicast packets with packet sizes between 64 bytes and the maximum when received.

RX_OCT The number of valid packets received in bytes.

RX_PAUSE The number of valid overflow-controlled packets received.

RX_PKT The number of valid packets received.

RX_SHORT The number of received packets under 64 bytes.

RX_UNI_OK The number of valid unicast packets with packet sizes between 64 bytes and the maximum size when received.

TX_BRD_OK The number of valid broadcast packets transmitted.

TX_ERR The number of discarded erred packets.

TX_INV The number of discarded invalid packets.

TX_MLT_OK The number of valid multicast packets

TX_OCT_OK The number of valid packets transmitted in bytes.

TX_PAUSE The number of valid overflow-controlled packets transmitted.

TX_PKT The number of valid packets transmitted.

TX_UNI_OK The number of valid unicast packets with packet sizes between 64 bytes and the maximum size when received.





Near-End

GBEMF TX_BRD_OK, TX_ERR, TX_INV, TX_MLT_OK, TX_OCT_OK, TX_PAUSE, TX_PKT, TX_UNI_OK

1 1 → 2

GBEMF RX_BRD_OK, RX_ERR, RX_INV, RX_LONG, RX_MLT_OK, RX_OCT, RX_PAUSE, RX_PKT, RX_SHORT, RX_UNI_OK

4 3 → 4

NODE 1

U-NODE WBM

3 6

ROUTER

4 5

1000BASE-X

1000BASE-X

SDH OPTICAL SIGNAL

ROUTER

1

1000BASE-X

1000BASE-X

NODE 2

U-NODE WBM

2



6.1.6 10BASE-T/100BASE-TX Ethernet Interface (FEH)

NOTE: This interface is available from Release 2.1 where FEH package is supported.

Following are the PM monitor types and their definitions for 10BASE-T/100BASE-TXEthernet interface:


COLLISION The total occurrence number of collisions transmitted.

RX_BRD_OK The number of valid broadcast frames with frame sizes between 64 bytes and the maximum when received.

RX_ERR The number of discarded erred incoming frames.

RX_INV The number of discarded invalid incoming frames.

RX_LONG The number of frames that exceed the maximum frame size when received.

RX_MLT_OK The number of valid multicast frames with frame sizes between 64 bytes and the maximum when received.

RX_OCT The number of valid frames received in bytes.

RX_PAUSE The number of valid overflow-controlled frames received.

RX_PKT The number of valid frames received.

RX_SHORT The number of received frames under 64 bytes.

RX_UNI_OK The number of valid unicast frames with frame sizes between 64 bytes and the maximum size when received.

TX_BRD_OK The number of valid broadcast frames transmitted.

TX_ERR The number of discarded erred frames.

TX_INV The number of discarded invalid frames.

TX_MLT_OK The number of valid multicast frames

TX_OCT_OK The number of valid frames transmitted in bytes.

TX_PAUSE The number of valid overflow-controlled frames transmitted.

TX_PKT The number of valid frames transmitted.

TX_UNI_OK The number of valid unicast frames with frame sizes between 64 bytes and the maximum size when received.



Following are the monitoring parameter, monitoring point and monitoring span at Node 1(U-Node WBM equipment) for each facility:


Near-End

FEHF TX_BRD_OK, TX_ERR, TX_INV, TX_MLT_OK, TX_OCT_OK, TX_PAUSE, TX_PKT, TX_UNI_OK

3 1 → 3

FEHF COLLISION, RX_BRD_OK, RX_ERR, RX_INV, RX_LONG, RX_MLT_OK, RX_OCT, RX_PAUSE, RX_PKT, RX_SHORT, RX_UNI_OK

3 4 → 3

NODE 1 NODE 2

U-NODE WBM U-NODE WBM

23

ROUTER ROUTER

14

10BASE-T/100BASE-TX10BASE-T/100BASE-TX

SDH OPTICAL SIGNAL



6.1.7 HPTM3 Layer

NOTE: This layer is available from Release 2.1 where GBEM package is supported.

HPTM3 Layer is a higher order path termination. Following are the PM monitor types andtheir definitions for HPTM3 Layer:



Near-End

CV (Code Violation) Occurrence time of Code rule violation. B3 is counter value.




Far-End

FECV (Far-End Code Violation) Occurrence time of Far-end code rule violation. Shown as REI_bit and accumulated. G1 is counter value.

FEES (Far-End Errored Seconds) FEEB indicated with REI_bit or RDI detection is checked per second. If FEEB or RDI occurs, seconds (time) are accumu-lated.

FESES (Far-End Severely Errored Seconds) If FEEB indicated with REI_bit count exceeds K times per sec-ond or RDI is detected, seconds (time) are accumulated.



Near-End

HPTM3 CV-P, ES-P, SES-P, UAS-P 5 4 → 5

Far-End

HPTM3 FECV-P, FEES-P, FESES-P, FEUAS-P 5 2 → 3

NODE 1

2

NODE 2

5 43


ROUTER

1

ROUTER

ETHERNET

ETHERNET

ETHERNET

ETHERNET



6.1.8 VCT LayerNOTE: This layer is available from Release 2.1 where GBEM package is supported.

VCT Layer is a VC termination layer. Following are the PM monitor types and theirdefinitions for VCT Layer:



Near-End

RX_PKT_VCT The number of received packets.

TX_PKT_VCT The number of outgoing packets.


Near-End

VCT TX_PKT_VCT, RX_PKT_VCT 5 4 → 5

NODE 1

2

NODE 2

5 43


ROUTER

1

ROUTER

ETHERNET

ETHERNET

ETHERNET

ETHERNET



6.1.9 HP Monitor

Following are the PM monitor types and their definitions of HP monitor (Higher Order PathMonitor):



Near-End





Far-End

FEBBE (Far-End Background Block Error) Cumulative value of FEEB (Far-End Errored Block) indicated with REI_bit. G1 is counter value.





Near-End

HPMON Incoming Signal BBE-P_IN, ES-P_IN, SES-P_IN, UAS-P_IN 2 1 → 2

HPMON Outgoing Signal BBE-P_OUT, ES-P_OUT, SES-P_OUT, UAS-P_OUT 5 4 → 5

Far-End

HPMON Incoming Signal FEBBE-P_IN, FEES-P_IN, FESES-P_IN, FEUAS-P_IN 2 4 → 6

HPMON Outgoing Signal FEBBE-P_OUT, FEES-P_OUT, FESES-P_OUT, FEUAS-P_OUT 5 1 → 3

NODE 1

2

NODE 2

1

SDH Terminal Node

5

6 43

SDH Terminal Node




6.1.10 LP Monitor

Following are the PM monitor types and their definitions of LP monitor (Lower Order PathMonitor):



Near-End

BBE (Near-End Background Block Error) Cumulative value of error block count. B3 or BIP2 is monitored and counted for TU3 or TU12, respectively.


SES (Near-End Severely Errored Seconds) If EB count exceeds K times (see 6.1.15 SES Thresh-old) per second or Defect is detected, seconds (time) are accumulated.



Near-End

LPMON Signal BBE-P, ES-P, SES-P, UAS-P 1 4 → 1

NODE 1

Terminal Node Terminal Node


NODE 2

1 4

2 3



6.1.11 HPT

Following are the PM monitor types and their definitions of HPT (Higher Order PathTermination):



Near-End


ES (Near-End Errored Seconds) EB (Error Block) occurrence is checked per second. If EB occurs or Defect is detected, seconds (time) are accumu-lated.

SES (Near-End Severely Errored Seconds) If EB count exceeds K times (see 6.1.15 SES Threshold) per second or Defect is detected, seconds (time) are accumu-lated.


Far-End

FEBBE (Far-End Background Block Error) Cumulative value of FEEB (Far-End Errored Block) indicated with REI_bit. G1 is counter value.

FEES (Far-End Errored Seconds) FEEB indicated with REI_bit or RDI detection is checked per second. If FEEB or RDI occurs, seconds (time) are accumu-lated.




Near-End

HPT Signal BBE-P, ES-P, SES-P, UAS-P 1 4 → 1

Far-End

HPT Signal FEBBE-P, FEES-P, FESES-P, FEUAS-P 1 2 → 3

NODE 1 NODE 2



1

2 3

4



6.1.12 LPT

Following are the PM monitor types and their definitions of LPT (Lower Order PathTermination):



Near-End

BBE (Near-End Background Block Error) – SDH Cumulative value of error block count. B3 and BIP-2 are counter values for TU3 and TU12, respectively.


SES (Near-End Severely Errored Seconds) If EB count exceeds K times (see 6.1.15 SES Thresh-old) per second or Defect is detected, seconds (time) are accumulated.


Far-End

FEBBE (Far-End Background Block Error) – SDH Cumulative value of FEEB (Far-End Errored Block) indicated with REI_bit. G1 and V5 are counter values for TU3 and TU12, respectively.





Near-End

LPT Signal BBE-P, ES-P, SES-P, UAS-P 1 4 → 1

Far-End

LPT Signal FEBBE-P, FEES-P, FESES-P, FEUAS-P 1 2 → 3

NODE 1 NODE 2



1

2 3

4



6.1.13 Multiplex Section Protection

Following are the PM monitor types and their definitions of Multiplex Section Protection:

Following is the monitoring parameter for each switching group:


PSC (Protection Switching Counts) The number of carried-out Line, Ring and Span switchings.This is applicable to Work and Protection sides regardless of Revertive or Non-Revertive mode.

PSD (Protection Switching Duration) Time while switched to the protection side of Line, Ring, Span protection is counted. This is applicable to Work and Protection sides.

PSC-R (Protection Switching Counts-Ring) The number of carried-out Ring switching.This is applicable to Work and Protection sides in 4F MS-SPRing and 2F MS-SPRing modes.

PSC-S (Protection Switching Counts-Span) The number of carried-out Span switching. This is applicable to Work and Protection sides in 4F MS-SPRing mode.

Switching Group Monitoring Parameter

No Switch GroupNon-Protection Mode

Not Applicable.

MS4FS (4F MS-SPRing) Line 1 (West): PSD-R_W, PSD-S_W, PSC-R_W, PSC-S_WLine 2 (East): PSD-R_E, PSD-S_E, PSC-R_E, PSC-S_E

MS2FS (2F MS-SPRing) Line 1 (West): PSD-R_W, PSC-R_WLine 2 (East): PSD-R_E, PSC-R_E

LINES PSD, PSC



6.1.14 AU Path

Following are the PM monitor types and their definitions for AU path:

Following is the PM monitoring parameter for each facility:


PJE-N(Pointer Justification Event Negative stuff)

A count of pointer justification event stuffed at NE clock (negative). All the path’s parameters con-tained in line are created.

PJE-P (Pointer Justification Event Positive stuff)

A count of pointer justification event stuffed at NE clock (positive). All the path’s parameters contained in line are created.

Target Facility Monitoring Parameter NOTE

AUn PJE-N, PJE-P AUn



6.1.15 SES Threshold

Facility Monitoring SES Parameters SES Threshold NOTE

STM64* RS-SES 2400 ––––

MS-SES/MS-FESES 2400 ––––

STM16 RS-SES 2400 ––––


STM4 RS-SES 2400 ––––


STM1 RS-SES 2400 ––––


STM1E RS-SES 2400 ––––


HPTM3 SES-P/FESES-P 2400 Both In/Out

HPMON4 SES-P/FESES-P 2400 Both In/Out

HPT SES-P/FESES-P 2400 ––––

LPT SES-P/FESES-P 2400 TU LEVEL = TU3

SES-P/FESES-P 600 TU LEVEL = TU12

LPMON SES-P 2400 TU LEVEL = TU3

SES-P 600 TU LEVEL = TU12

E12F SES-L 600 ––––

E31F SES-L 2400 ––––

E32F SES-L 2400 ––––




6.2 PM DATA MANAGEMENT

6.2.1 PM Data Type

PM and IPPM have the following types of registers for each monitor type (time period). Thelabel that manages the registers is the starting time of the accumulating period.

! 15-minute: The 15-minute register holds the accumulated value of every 15-minuteperiod (starting each hour at 00, 15, 30, 45 minutes).

! 1-day: The 1-day register holds the accumulated value of every 24-hour period (startingat 00:00 (midnight) each day).

When the registers exceed the number, the oldest PM condition is overwritten with the latestone.

6.2.2 Data Reliability

Validity information is added to each PM monitor type to validate/invalidate data. Thefollowing table shows the validity and status.

REGISTER TYPE 15-MINUTE 1-DAY

Number of Current PM Status Conditions 1 1

Number of PM Status Condition History 32 1

Validity Status

Completed[COMPL]

Cumulative process is completed in cumulative range under normal status.

Partial[PRTL]

Cumulative process cannot be completed in part of cumula-tive range because error occurs. Asterisks (*) is indicated with valid data when displayed.

Not Applicable[NA]

Cumulative process cannot be completed in all cumulative ranges because error occurs.

Not First[NF]

Path is received normally but it is not head of concatenation signal (for IPPM in Auto Mode).

Performance Monitoring — PM Data Management6-18


6.3 TCA FUNCTION

U-Node WBM provides the Threshold Crossing Alert (TCA) function that issues an alert ifthe value of the monitored PM type reaches or exceeds that of the specified threshold. Thevalues are accumulated every 15 minutes at 00, 15, 30, and 45 minutes of each hour (15Min)or for every 24-hour at 0:00 am (1Day).

6.3.1 TCA Threshold

A TCA threshold value can be customized. If a TCA threshold value of 0 is specified to aPM type, the TCA of that PM type will not be reported. TCA function is disabled when thetarget object’s service state is set to OOS-MA-AS, or its Port Mode is set to AUTO. PMmonitor types for physical layer and switching do not have TCA function.

Performance Monitoring — TCA Function6-19


6.4 IPPM MANAGEMENT

In the U-Node WBM, PM monitoring is carried out on layers of path points that are nottermination points. This function is supported for failure isolation and quality check.

6.4.1 Monitor Point

Registered path can be managed for its Incoming/Outgoing independently. The followingillustrations show the monitor points. Registered path supports the monitor type shown inthe 6.1 Performance Monitoring (PM) Type subsection.

6.4.1.1 Monitor Points for Higher Order Path

6.4.1.2 Monitor Points for Lower Order Path

STMn Interface

STMn Interface

Monitor Point

Monitor Point

Monitor Point

Monitor Point

STMn Interface

Lower Order Monitor Point

PSW40B

Higher Order Crossconnect

Lower Order Crossconnect

PDH Interface

Performance Monitoring — IPPM Management6-20


6.4.2 Accumulation

There are two modes: AUTO mode and FIX mode to support the IPPM function forregistered higher order paths.

For a path set to the AUTO mode, the PM is accumulated/managed according to theconcatenation level of its incoming signal.

For a path set to the FIX mode, the PM is accumulated/managed by the specified range of thepath band.

Performance Monitoring — IPPM Management6-21



Performance Monitoring6-22 E


7. FAULT MANAGEMENT

U-Node WBM reports the failures occurring in the transmission line and NE.

7.1 MONITORED ITEMS

! Transmission Line Failure

! NE Failure

! Timing Reference Failure

! Protection Failure

! Network Control Failure

Refer to the 3.2 Performance Monitoring (PM) subsection in the Operation andMaintenance manual for full items.

Fault Management — Monitored Items7-1


7.2 MANAGEMENT PARAMETERS

7.2.1 Alarm Severity

The alarm severity of each failure is indicated by the following alarm levels and classes.Alarm classes can be modified. The severity levels can be modified by using Alarm SeverityAssignment Profile (ASAP) per condition type.

! Alarm Level

• SA (Service Affecting condition)This level shows when an alarm affecting service has occurred and continues.

• NSA (Non-Service Affecting condition)This level shows when an alarm that does not affect service has occurred and continues.

! Alarm Classifications According to Severity

! ASAP (Alarm Severity Assignment Profile)U-Node WBM manages alarm severity of all the detected alarms in a table format. Thistable is called ASAP.

Severity Description

CR Critical: service-affecting condition has occurred and immediate cor-rective action is required, such as when a managed object becomes totally out of service and its capability must be restored.

MJ Major: service-affecting condition has developed and immediate cor-rective action is required, such as when there is a severe degrada-tion in the capability of the managed object and its full capability must be restored.

MN Minor: existence of non-service-affecting fault and corrective action should be taken to prevent a more serious (i.e., service-affecting) fault. This severity can be used, for example, when the detected alarm is not currently degrading the capacity of the managed object.

NA Not Alarm: Detected alarm is not considered to be an alarm (auto-matic report performed), such as Event Notification, etc. Alarm or event with this severity will not be searched.

NR Not Report: Detected alarm is not considered to be an alarm (no automatic report performed). Alarm or event with this severity will not be searched.

Fault Management — Management Parameters7-2


7.2.2 Delay/Stretch Time

The following describes the functions of Delay and Stretch Time:

! Delay TimeDelay Time is a specific period for the process to determine if the detected failure is analarm to be reported.

! Stretch TimeStretch Time is a specific period for the process to determine if the alarm has been cleared.

Fault Management — Management Parameters7-3


7.3 ALARM REPORT

When an alarm is detected, the user is notified by lighting up the LEDs on the package andthe rack, and reporting the alarm to user interface (for example, the CID). Alarm notificationis also accomplished by an Office alarm, such as the station alarm bell and lamps.

7.3.1 LED Process

The LED on the front of the package lights up when an alarm is generated/cleared to reportthe alarm to the user.

7.3.2 Report to User Interface

An alarm is automatically reported to User Interface when it is generated/cleared. An alarmreport includes time information concerning when MSCB confirms alarm occurrence andrecovery. The user can set whether an automatic report is permitted or prohibited for eachuser port. All alarm statuses in NEs can be read collectively.

7.3.3 Office Alarm

7.3.3.1 Office Alarm Type

The following office alarms are reported:

! Alarm output for Bell (AB)

! Alarm output for Lamp (AL)

! LED on front of MSCB

! LED on front of Rack

Fault Management — Alarm Report7-4


7.3.3.2 Delay/Stretch Process

! Delay TimeDelay Time is a specific period for the process to determine if the detected failure is analarm to be reported.

! Stretch TimeStretch Time is a specific period for the process to determine if the alarm has been cleared.

For an Office alarm, the duration of delay time and stretch time can be customized. Thefollowing table shows delay time and stretch time defaults and ranges:

7.3.3.3 ACO Function

If you execute ACO (Alarm Cut Off) during alarm occurrence (AB/AL output), the audiblealarm (AB) is silenced; however, AB will be output if another alarm occurs later. The U-Node WBM has an ACO lamp on the MSCB package to show the ACO status.

7.3.4 Processing Alarm Masks

! Service State and Processing AlarmThe following table shows the process of when an alarm is generated and the relationshipbetween an NE’s managed object and its service state.

! PORT ModeThis function is used to stop alarm reporting of physical layer, and PORT mode is TP modeavailable only for physical layer. The following two states are supported;

• MON: In this mode, alarm reporting for physical layer will be performed.

• AUTO: In this mode, alarm reporting for physical layer will not be performed.

Default is AUTO mode. PORT mode status is interlocked with facility’s service state. Referto the 5. Configuration Management section for details.

Delay/Stretch Default Setting Range

Delay Time 0 [second] 0 to 60 [second]

Stretch Time 20 [second] 0 to 60 [second]

Service State IS-NR IS-ANR OOS-MT OOS-MA-AS OOS-MA-UAS

NE alarm Report Report*

* Unequipped state of package is not reported.

No Report

Fault Management — Alarm Report7-5


7.4 OFFLINE MONITORING

The offline monitoring function is provided for redundant packages. When one package isoffline, it executes a self-diagnostic test to monitor package failures.

Fault Management — Offline Monitoring7-6 E


8. LOG FUNCTION

U-Node WBM controls and manages the interface with the user according to the TL1command format. The Network Element records a history of the AO Buffer and CommandLog. An operator can retrieve such logs in the CID to review activities on the NetworkElement.

8.1 COMMAND LOG

Command Log is a history of commands issued by the operator and their response from theNetwork Element. Commands that are executed are logged and failed commands are notlogged. Command Log Data can be initialized.

8.1.1 Mode of Logging

U-Node WBM can store up to 500 command logs in total. There are two modes forCommand Log. The logging mode affects the response of the logging function when thenumber of logs reaches the maximum:

! HALT ModeLogging stops when the number of logs reaches the maximum number. The networkelement dispatches an alarm to notify the user.

! WRAP ModeWhen the number of logs reaches the maximum, the network element overwrites the oldestlog with the next log. This mode is the default setting.

Log Function — Command Log8-1


8.2 AO BUFFER

The autonomous output (AO) Buffer is a history of messages (reported automatically) fromthe network element to the CID or NMS. The AO Buffer cannot be initialized.

8.2.1 Mode of Logging

The total number of AO Buffers is 2,500 at maximum. There is only one mode for AOBuffer logging. It is similar to WRAP mode for the Command Log: the oldest log isoverwritten with a new log after the maximum number of logs is reached.

Log Function — AO Buffer8-2 E


9. MAINTENANCE OPERATION

This section describes the Maintenance functions for supporting NEs, traffic, networks, andothers.

9.1 LOOPBACK FUNCTION

9.1.1 Line Loopback

Each Signal Interface package equipped on the U-Node WBM supports the following twoloopback functions for failure isolation:

! Facility Loopback

! Terminal Loopback

In addition to the functions above, the PDH interface package (E12, E31 and E32) alsosupports the following loopback function:

! Remote Loopback

During loopback execution, the MNT LED on the front of the MSCB package lights up toindicate the maintenance mode.

Maintenance Operation — Loopback Function9-1


9.1.1.1 Facility Loopback

The incoming signal from NODE A is looped back to NODE A. The AIS is inserted beforethe crossconnection point, and is output to NODE B:

The facility loopback function is operated in the PDH interface package (E12, E31 and E32)as follows:

9.1.1.2 Terminal Loopback

The signal output from NODE B goes to NODE A, and at the same time, is looped back in apackage, through the crossconnection point, then is output to NODE B:

For the PDH interface package (E12, E31 and E32), the terminal loopback function isoperated as follows:

INF PKG

XCINF PKG

AIS

LOCAL NODENODE A NODE B

NODE A

NODE B

HOSW LOSW PDH PKG

2M/34M/45M

AIS

STMn PKG

INF PKG

XCINF PKG

LOCAL NODE NODE BNODE A

NODE A

NODE B

HOSW LOSW PDH PKG

2M/34M/45MAIS

STMn PKG



9.1.1.3 Remote Loopback

The remote loopback function (an original NEC function known as “L_Bit_LPBK”) isprovided for the PDH interface package (E12, E31 and E32) only, to aid in the maintenanceor troubleshooting of transmission networks. When the remote loopback command issuedfrom the CID at the local station is detected in the remote Node, the received 2M/34M/45Msignal is looped back towards the originating station in the E12/E31/E32 package. When thisoccurs, the MNT LEDs on the MSCB packages at both the local and remote Nodes light on,and an AIS is output downstream by the appropriate interface (i.e., 2M, 34M or 45M) at theremote station.

The following shows the Remote Loopback function control bit formats.

Remote Node

STMn PKG LOSW PDH PKG

2M/34M/45MAIS

2M/34M/45M

Local Node

HOSWLOSWPDH PKG

Remote Loopback

STMn PKG HOSW

R R R R R R L

V5

R R R R R R R R

R R R R R R R R

R R R R R R R R

J (32 bytes)

140bytes(500 µs)

VC-12 Signal(2M)

RemoteLoopback Bit (L Bit)

R

Fixed Stuff Bit for E12 Loopback

I:

R:

V5:

Information Bit

Fixed Stuff Bit

VC-12 Path Overhead Byte



There are no ITU-T recommendations for loopback function since it is not a capabilityenvisaged by the recommendation draft committee; NEC designers utilize a fixed stuff bit inthe VC-12/VC-3 for the transmission of remote loopback command. Remote loopbacksignal can be transmitted from the local station to the remote station through a number ofintermediate stations as long as none of the intermediate stations drops and broadcasts thatloopback channel. The following shows the terms for detecting and clearing remoteloopback signals at remote station.

! Detect: When 1010101010 pattern received! Clear: When 1010101010 pattern not received

In addition, prohibit setting that disables the remote loopback control is also available.

R R R R R

VC-3 Signal(34M/45M)

RemoteLoopback Bit (L Bit)

R

Fixed Stuff Bit for E31/E32 LoopbackR:

J1:

Second Byte of VC-3 POH

First Byte of VC-3 POH

B3

R R R R LRJ1

R

R

R

R



9.1.2 V.11 Port Loopback

For the user channel in V.11 port supported by U-Node WBM, there are the two followingloopback modes, the same as in an interface package:

! Facility Loopback

! Terminal Loopback

During loopback execution, the MNT LED on the front of the MSCB package lights up toindicate the maintenance mode.

9.1.2.1 Facility Loopback

The incoming signal from an external V.11 Incoming Port is looped back in the OHCpackage, and the signal is output to an external interface. The all “1” signal is inserted to theline’s overhead assigned by the port.

9.1.2.2 Terminal Loopback

A signal from the external V11 port is looped back in the OHC package, assigned to the linefacility’s overhead, and is output. All “1” is inserted to the V11 port that carries the assignedline facility.

INF PKG

OHC PKG

WBM SHELF

V.11 Port

Overhead Data Bus

INF PKG

OHC PKG

WBM SHELF

V.11 Port

Overhead Data Bus



9.2 AUTOMATIC LASER SHUTDOWN

U-Node WBM provides the Automatic Laser Shutdown (ALS) function to prevent theoperator or maintenance personnel from any accidental eyesight damage.

9.2.1 Automatic Laser Shutdown (ALS)

If the optical incoming signal is lost for a certain period of time, the Automatic LaserShutdown (ALS) function is enabled to stop optical output in order to prevent the operator ormaintenance personnel from any accidental eyesight damage. The ALS mode is disabledwhen normal signals are received from the far-end NE. The local NE starts transmittingsignals normally.

The following illustration shows an example. The user can choose whether or not to use theALS function via the CID.

There are two ALS restart modes.

! Auto RestartWhile in the ALS mode, NE will regularly transmit optical signals. After receiving normalsignals from the far-end NE, optical output restarts:

• Optical Output Time: 2 sec (default), or 9 sec

• Time Interval: 60 sec, 180 sec (default), or 300 sec

! Manual RestartMakes an NE (SINFn package) release an optical output via the CID or upper OS, whichdisables the ALS.

• Optical Output Time:Short-ON: 2 sec (default), or 9 secLong-ON: 90 sec

INF PKG

LOCAL NODE

INF PKG

LOCAL NODE

Optical Output Shutdown

LOS Detection

Maintenance Operation — Automatic Laser Shutdown9-6


9.2.1.1 Exception for GBEM Package

NOTE: GBEM package is supported from Release 2.1.

GBEMF facility does not have particular setups for ALS. However, to enable ALS function,an opposing side (GBE routers in the following example) must have their ALS functionenabled.

For GBEMF facility, if the following alarm(s) is/are detected from outgoing signal (seebelow), GBEM stops its optical output, which is reported as ALS on GBEMF:

! AIS-P (AU-3/4): on virtual concatenated GBEMF

! RDI-P (HPTM3): on virtual concatenated GBEMF

! L2SYNCLOSS (VCT): on virtual concatenated GBEMF

! CSF (GBEM)

Since GBEM package (or GBEMF facility) does not have ALS setups, any operations ofALS provided by CID are not effective for this facility. When those failures are cleared,GBEM restarts optical output.

GBEM GBEM

PSW SINF SINF PSW

GBE ROUTER GBE ROUTERNODE A NODE B

failure occursalarm detected

GBEM GBEM

PSW SINF SINF PSW

GBE ROUTER GBE ROUTERNODE A NODE B

failure occurs alarm detectedShutdown by ALSalarm detected

Shutdown by ALS



9.2.2 Automatic Power Shutdown (APSD)

In order to prevent an operating/maintenance personnel from any accidental eyesightaccidents, the Automatic Power Shutdown (APSD) function is provided to stop opticaloutput from OPT amplifier if optical input to OPT amplifier is lost or not detected. There aretwo types of OPT amplifier: Pre-Amplifier, which amplifies the Optical Input Signal, andBooster Amplifier, which amplifies the output signal. This function is provided only on anoptical interface package with OPT amplifier (AMP) and on AMP shelf. This function is oneof U-Node WBM interior features.

Automatic Power Shutdown - Pre-AMP Input Shutdown

Automatic Power Shutdown - Booster AMP Input Shutdown

O/E

LOCAL NODE LOCAL NODE

APSD Optical Output Shutdown

AMP

AMP E/O

O/EAMP

AMP E/O


O/E



AMP

AMP E/O

O/EAMP

AMP E/O

AMP Input Shutdown



9.2.3 Lower-Level Optical Output (Reflected Alarm Detection)

This function is one of U-Node WBM interior features, which is provided when AMP shelf isinstalled. If a reflected alarm is detected, the optical output signal is automatically lowered,instead of being shut down. This function is supported by a package with Booster Amplifierswhich can detect the reflected alarm. This function is also enabled when optical outputrestarts when recovering from the APSD condition; a lower-level optical signal is output andreflection is verified.

9.2.4 Forced Optical Output Shutdown

SDH optical output signal can be forcibly shut down by CID operation. During the executionof this function, the condition is notified, and the MNT LED on front of the MSCB packagelights up.

O/E


Lower Level Optical Output by

detecting a reflected alarm

AMP

AMP E/O

O/EAMP

AMP E/O



9.3 OVERHEAD ACCESS

U-Node WBM accesses the user channels on the SDH overhead. This function is providedby SINFn and STM1E* packages with OHC package. [*: supported from Release 1.2.]

9.3.1 User Channel Access

In order to make connection, six ports of V.11 Interface in each shelf are provided.

• Rate: 576 kbit/s data channel or 64 kbit/s data channel

• Number of Ports: 6

• Co-directional/Contra-directional Switching: user can specify this setup for eachport.

9.3.1.1 Accessible Facility

The following interface’s OH bytes can be accessed as a user channel:

• SINF64(B) package: STM64 [supported from Release 2.1]

• SINF16/SINF16(B) package: STM16

• SINFM package: STM4, STM1

• STM1E package: STM1e [supported from Release 1.2.]

9.3.1.2 Usable Overhead Byte

The following OH bytes can be accessed as a user channel:

• RS Layer Overhead: E1 and F1

• MS Layer Overhead: E2 and MDCH (D4 to D12)

9.3.1.3 User Channel Loopback

U-Node WBM has loopback function for the logical V.11 Port that is used as a user channel.Terminal loopback or facility loopback is executable and the connection status can beconfirmed. You can execute the loopback function individually to each port (V.11 Port 1 –Port 6). See the 9.1 Loopback Function subsection in this section for details.

! Facility Loopback: An incoming signal from V.11 port is looped back in OHCPKG, and the signal is output to V.11 port.

! Terminal Loopback: An outgoing signal from V.11 port is looped back in OHCPKG, and the signal is output to the line overhead again. The all “1” signal is sentto V.11 port-side.

Maintenance Operation — Overhead Access9-10


9.3.2 DCC LAPD Access

U-Node WBM supports the LAPD access function to access MSDCC and RSDCC.

For OHC package, 4, 8, or 12 DCC_PORT termination points can be selected.

9.3.3 Overhead Through

U-Node WBM supports the Overhead Through function to an arbitrary line facility’soverhead on SINFn and STM1E* packages. [*: available from Release 1.2.]

The following overhead bytes can be used for this function:

• RS Overhead: Z0-2, Z0-3, Z0-4, E1, F1, NU-1, NU-2, NU-3, and NU-4

• MS Overhead: MDCH (D4 to D12), Z1-1, Z1-2, Z1-3, Z2-1, Z2-2, Z2-3, E2,NU-5, and NU-6

9.3.4 Orderwire Access

U-Node WBM has a digital branch function and supports the orderwire function by using E1or E2 bytes. Up to ten lines can be connected to digital branches per shelf. Available PCMcoding method is A-Law only.

9.3.4.1 Orderwire Interface

U-Node WBM provides the following orderwire interfaces:

• VF (See NOTE 1)

• HEAD SET (See NOTE 2)

• TEL SET (See NOTE 2)

• V.11 Interface with frame pulse

NOTES:

1. VF Interface Transmission Level• Incoming Signal: –15.5 to –0 dBm• Outgoing Signal: –8.5 to 7.0 dBm• Modification is available at every 0.5-dB within the range.

2. Only one of VF interface, HEAD SET interface, or TEL (HAND) SET interface can beselected for an access at a time. These three interfaces are analog-branched within theOHC package.



9.3.4.2 Calling

There are three methods for calling:

! All-CallBy pressing the CALL switch on the front of the OHC package, all the NEs that supportthis function can communicate with the orderwire. At local node (call-receiving station),pressing the ANS. button allows the user to talk.

! Selective-CallAt the call-origination station, connect the telephone set to the TEL SET terminal on theOHC package, and dial the number (call ID) of the NE that you want to communicate with.Only the dialed station is called. At the local node (call-reception station), pressing theANS. button allows the user to talk.

! Group-CallAt the call-origination station, connect the telephone set to the TEL SET terminal on theOHC package, and dial the number (group call ID) of the NE that you want tocommunicate with. Dialed station(s) that has (have) the same group call ID in the networkis (are) called. At the local node (call-reception station), pressing the ANS. button allowsthe user to talk.



9.4 LINE SWITCH EXERCISE

U-Node WBM supports this function to confirm in advance if the switching operation isproperly carried out to the following protection.

! Bi-directional Linear Protection

! 2F/4F MS-SPRing Protection

This function does not affect the main signal. It is performed by sending/receiving K1/K2command between local and remote stations.

Maintenance Operation — Line Switch Exercise9-13


9.5 HOUSEKEEPING

U-Node WBM supports the housekeeping alarm functions and housekeeping controlfunctions. The Housekeeping alarm function is used to read alarms in a station and reportsalarm occurrence. The Housekeeping control function is used to control equipment, such asthe air conditioner, power generators, and alarm bells, via the CID.

9.5.1 Housekeeping Alarm

This function monitors the external alarm received at HKA interface port and sends alarmnotification.

! HKA Ports: 16 built-in ports

! Alarm Logic: HKA alarm polarity is selectable for each port

! Alarm Name Setting: External alarm name can be set for each HKA port

9.5.2 Housekeeping Control

This function is used to output control status to the corresponding HKC interface port byissuing a command via CID.

! HKC Ports: 8 built-in ports

! Control Logic: HKC alarm polarity and duration time can be set for eachport.

! Control Name Setting: Controlling signal name can be set for each HKC port viaCID.

Maintenance Operation — Housekeeping9-14


9.6 RESET FUNCTION

This function is used to reset the CPUs.

9.6.1 How to Reset CPU

To reset a CPU, there are two methods:

! Reset a package CPU by the CID; available for MSCB, SSCB, OHC).

! Reset a package by pressing the RESET button on the front of the package(provided on MSCB package).

9.6.2 Restart Level

! Hot Start: U-Node WBM starts according to the system administration informationspecified by users (customized provisioning setups).

! Cold Start: U-Node WBM starts up with the factory default setups.

See 5.5 Starting Up NE in this manual for descriptions on these starting modes.

Maintenance Operation — Reset Function9-15



Maintenance Operation9-16 E


10. SECURITY MANAGEMENT

The U-Node WBM provides a security system to prevent unauthorized users from accessingthe network element. Only users with proper accounts are authorized to access the system.The following describes security management in the U-Node WBM system.

10.1 TYPE OF USER ACCOUNT

U-Node WBM allows the following two types of user accounts.

10.1.1 Super User

A Super User is a user with a Level 5 User Privilege Code (UPC) in System Administration.If more than one Super User exists, a Super User’s level can be changed by another SuperUser. Only Super Users have the right to add and delete users, and modify attributes of otherusers.

10.1.2 Normal User

A Normal User is any user who is not a Super User. Normal Users have no rights to add ordelete users, or modify attributes of other users.

10.2 USER ATTRIBUTES

There are six attributes that each user retains: User Identification, Password, User PrivilegeCode Level, User Account Expiration, and Password Aging (Password Expiration). See thefollowing descriptions on each attribute.

Security Management — Type of User Account10-1


10.2.1 User Identification (UID)

User Identification is a unique name given to each user. Duplicated names are not allowed inthe network element. UID is specified when the user is created and cannot be modified.

A UID must be at least 6 characters long, and within 10 characters long. Valid characters thatcan be used for the UID are shown in the following table.

10.2.1.1 Valid ASCII Characters for UID

NOTES:

1. UID must be between 6 to 10 characters long.

2. Any of the characters in the above table can be used for the UID. However, thefollowing combinations should not be used:/**/The reason for this restriction is that /* and */ are used respectively as the “beginning ofcomment” and “end of comment” marks in TL1.

3. Case SensitiveUIDs used in system administration commands are case sensitive.Thus, uppercase and lowercase characters must be taken into account.

b3 to b0

B6 to B4 000 001 010 011 100 101 110 111

0 1 2 3 4 5 6 7

0000 0 0 @ P ‘ p

0001 1 ! 1 A Q a q

0010 2 2 B R b r

0011 3 # 3 C S c s

0100 4 $ 4 D T d t

0101 5 % 5 E U e u

0110 6 6 F V f v

0111 7 7 G W g w

1000 8 ( 8 H X h x

1001 9 ) 9 I Y i y

1010 A * J Z j z

1011 B + K [ k

1100 C L l |

1101 D - = M ] m

1110 E . N ^ n ~

1111 F / ? O _ o

Security Management — User Attributes10-2


10.2.2 Password (PID)

The password is a secret code for authorization to access the network element. Every usermust provide a valid password to enter the network element.

10.2.2.1 Valid Password

! Must be between 6 to 10 characters long.

! Must contain at least one uppercase character.

! Must contain at least one lowercase character.

! Must contain at least one numerical character.

! Must contain at least one special character, with the exception of #, $, @, and /.See the following table for valid PID characters.

! Must not contain the UID.

! Must not be a previously-used password (no password toggling).

If the password chosen does not meet the requirements above, the network element will rejectregistration of the new user or changing to a new password, and will prompt the user to enteranother password.



10.2.2.2 Valid ASCII Characters for PID

The Characters with ** in the table are special characters.

10.2.3 User Account Expiration

User Account Expiration is the time period that the user can exist in the network element.After the specified period elapses, the user is deleted automatically from the networkelement. The specifiable period are Infinite or 1 day through 999 days.

Super Users can change the User Account Expiration for Normal Users. However, if UserAccount Expiration becomes 0, it can no longer be changed. Changes must be made beforethe number of days reaches 0.

User Account Expiration cannot be specified for a Super User; selection is fixed to Infinite.

b3 to b0

B6 to B4 000 001 010 011 100 101 110 111

0 1 2 3 4 5 6 7

0000 0 0 P ‘** p

0001 1 !** 1 A Q a q

0010 2 2 B R b r

0011 3 3 C S c s

0100 4 4 D T d t

0101 5 %** 5 E U e u

0110 6 6 F V f v

0111 7 7 G W g w

1000 8 (** 8 H X h x

1001 9 )** 9 I Y i y

1010 A J Z j z

1011 B +** K [** k **

1100 C L l |**

1101 D -** =** M ]** m **

1110 E .** N ^** n ~**

1111 F ?** O _** o



10.2.4 Password Aging

A Super User can limit the expiration of each user’s password by specifying Password Aging.The specifiable period is Infinite or 1 day through 999 days. Once Password Aging isspecified, the days remaining until expiration will be indicated in Password Expiration.

10.2.5 Password Expiration

Password Expiration is an indication showing the days remaining until a user’s passwordexpires (specified in Password Aging). When the password expires, it is invalid and the useris asked to provide a new password. A user is notified by an NE when his/her password willexpire in 7 days or less when he/she logs in to the NE.

10.2.6 User Privilege Code Level

User Privilege Code Level (UPC) is a degree of permission given to each user. Each TL1command is set to a certain UPC level. If the user does not have the same UPC Level as theTL1 command that the user is trying to execute, the Network Element will reject the requestand return an error. The UPC level given to each user can be modified by the Super User.However, the UPC level for TL1 commands is fixed, therefore, not modifiable.

Reference for User Privilege Code Level (1/7)

Command CodeUser Privilege Level

Category Level

ACT-CUTOVER M 4

ACT-CUTOVER-DATA M 4

ACT-USER A ——

ALW-ACTUSER A 5

ALW-DBCHGREPT P 3

ALW-ERRCOMREPT P 3

ALW-MEMRMV M 3

ALW-MSG-ALL M 3

ALW-PROTSTAT-ALL M 3

ALW-SECUREPT A 5

ALW-SWDX-EQPT M 3

ALW-SWTOPROTN-EQPT M 3

ALW-TCAREPT-ALL M 3



ALW-TIMRST M 3

CANC —— ——

CANC-CUTOVER M 4

CANC-USER A ——

CPY-BKMEM M 1

CPY-LCLTFTP-FILE M 4

CPY-LOCAL-FILE M 4

CPY-MEM M 4

CPY-RMT-DATA M 4

CPY-RMT-FILE M 4

CPY-TMP-DATA M 4

CPY-TMP-FILE M 4

DLT-CRS-FCLT P 4

DLT-EQPT P 3

DLT-FCLT P 3

DLT-IPADR P 4

DLT-PPS-FCLT P 4

DLT-SECU-USER A 5

DLT-SRTTBL P 4

DLT-TADRMAP P 4

DLT-TIPADRMAP P 4

ED-CRS-FCLT P 4

ED-EQPT P 2

ED-EXTLAN P 4

ED-FCLT P 2

ED-IPADR P 4

ED-IPINF P 4

ED-OSINF P 4

ED-OSISEL P 4

ED-RINGIDSEQ P 4

ED-SECU-PID A ——

ED-SECU-USER A 5

ED-SQLCH-FCLT P 4

Reference for User Privilege Code Level (Continued) (2/7)


Category Level



ED-SRTTBL P 4

ED-TADRMAP P 4

ED-TARP P 4

ED-TCPIP P 4

ED-TIPADRMAP P 4

ED-ULSDCC P 4

ENT-CRS-FCLT P 4

ENT-EQPT P 3

ENT-FCLT P 3

ENT-IPADR P 4

ENT-PPS-FCLT P 4

ENT-SECU-USER A 5

ENT-SRTTBL P 4

ENT-TADRMAP P 4

ENT-TIPADRMAP P 4

EXIT-LOCL-RST M 4

EX-SW-EQPT M 2

INH-ACTUSER A 5

INH-DBCHGREPT P 3

INH-ERRCOMREPT P 3

INH-MEMRMV M 3

INH-MSG-ALL M 3

INH-PROTSTAT-ALL M 3

INH-SECUREPT A 5

INH-SWTOPROTN-EQPT M 3

INH-TCAREPT-ALL M 3

INIT-ATTR-PROFILE M 4

INIT-LDB M 4

INIT-LOG M 3

INIT-REG-EQPT M 3

INIT-REG-FCLT M 3

INIT-SYS M 4

INIT-TDC M 4



Category Level



INIT-TH-PROFILE M 4

OPR-ACO-ALL M 1

OPR-EXT-CONT M 3

OPR-LEDTST M 2

OPR-LPBK-FCLT M 2

OPR-PKTTST-FCLT M

OPR-PROTNMD-EQPT M 3

OPR-PROTNMD-FCLT M 3

OPR-PROTNSW-EQPT M 3

OPR-PROTNSW-FCLT M 3

OPR-SHTDN-FCLT M 3

OPR-SYNCNSW M 3

OPR-TARP M 4

OPR-TSTACS-RX M 2

OPR-TSTACS-TX M 2

OPR-TSTACSL-RX M 2

OPR-TSTACSL-TX M 2

P-INVENTORY M 1

P-INVENTORY-MEM M 1

P-INVENTORY-OPT M 1

REPTÂLMÊNV —— ——

REPTÂLMÊQPT —— ——

REPTÂLM^FCLT —— ——

REPT^DBCHG —— ——

REPTÊRRCOM —— ——

REPTÊVTÊQPT —— ——

REPTÊVT^FCLT —— ——

REPT^PROTSTATÊQPT —— ——

REPT^PROTSTAT^FCLT —— ——

REPT^SECUÛSER —— ——

RLS-ALS-FCLT M 3

RLS-EXT-CONT M 3

RLS-LEDTST M 2



Category Level



RLS-LPBK-FCLT M 2

RLS-PKTTST-FCLT M 2

RLS-PROTNSW-EQPT M 3

RLS-PROTNSW-FCLT M 3

RLS-SHTDN-FCLT M 3

RLS-SYNCNSW M 3

RLS-SYNCNWTR M 3

RLS-TSTACS-RX M 2

RLS-TSTACS-TX M 2

RLS-TSTACSL-RX M 2

RLS-TSTACSL-TX M 2

RMV-EQPT M 3

RST-EQPT M 3

RTRV-ALM-ALL M 1

RTRV-ALM-ENV M 1

RTRV-ALM-EQPT M 1

RTRV-ALM-FCLT M 1

RTRV-ALM-RING M 1

RTRV-ALM-SUMMARY M 1

RTRV-AO P 4

RTRV-AOINF P 1

RTRV-ATTR-CONT M 1

RTRV-ATTR-ENV M 1

RTRV-ATTR-PROFILE M 1

RTRV-COND-ALL M 1

RTRV-COND-EQPT M 1

RTRV-COND-FCLT M 1

RTRV-CRS-FCLT P 1

RTRV-CUTOVER M 1

RTRV-DATASTAT M 1

RTRV-EQPT P 1

RTRV-EXT-CONT M 1

RTRV-EXTLAN P 1



Category Level



RTRV-FCLT P 1

RTRV-FILESTAT M 1

RTRV-HDR M 1

RTRV-IPADR P 1

RTRV-IPINF P 1

RTRV-LCPYSTAT M 1

RTRV-LDB M 4

RTRV-LED-EQPT M 1

RTRV-LOG M 1

RTRV-LOGMODE M 1

RTRV-MEMINF M 1

RTRV-MEMSTAT-EQPT M 1

RTRV-NEADR M 1

RTRV-NFTSTAT M 1

RTRV-OSINF P 1

RTRV-OSISEL P 1

RTRV-PKTSTAT-FCLT M 1

RTRV-PM-EQPT M 1

RTRV-PM-FCLT M 1

RTRV-PROTNMD-EQPT M 1

RTRV-PROTNMD-FCLT M 1

RTRV-PROTSTAT-EQPT M 1

RTRV-PROTSTAT-FCLT M 1

RTRV-PTHLVL-FCLT P 1

RTRV-RCPYSTAT M 1

RTRV-RIB M 4

RTRV-RINGIDSEQ P 1

RTRV-RTTBL M 4

RTRV-SECU-STATUS A 1

RTRV-SECU-UPC A ——

RTRV-SECU-USER A ——

RTRV-SESSION M 4

RTRV-SQLCH-FCLT P 1



Category Level



RTRV-SRTTBL P 1

RTRV-TADRMAP P 1

RTRV-TARP P 1

RTRV-TARPADJ M 4

RTRV-TARPSEQ M 4

RTRV-TCPIP P 1

RTRV-TDC M 4

RTRV-TH-PROFILE M 1

RTRB-TIPADRMAP P 1

RTRV-TSTACS-RX M 1

RTRV-TSTACS-TX M 1

RTRV-TSTACSL-RX M 1

RTRV-TSTACSL-TX M 1

RTRV-ULSDCC P 1

SET-ATTR-CONT M 3

SET-ATTR-ENV M 3

SET-ATTR-PROFILE M 3

SET-DAT A 2

SET-LOGMODE M 3

SET-NEADR M 4

SET-SID M 4

SET-TH-PROFILE M 3

STA-LOCL-RST M 4

STP-KERMIT M 4

STP-LCPY M 4

STP-RCPY M 4

STP-TFTP M 4

SW-DX-EQPT M 3

SW-MEM M 4

SW-MEM-DATA M 4

SW-TOPROTN-EQPT M 3



Category Level



10.3 ADDITION, MODIFICATION, AND DELETION OF USERS

A Super User can add and delete other users and modify their attributes. A Normal User canrefer to a list of currently logged-in users.

10.3.1 Addition

A Super User can create (add) any user.

10.3.2 Modification

A Super User can modify attributes of any user, including other Super Users.

10.3.3 Deletion

A Super User can delete any user, including other Super Users. However, a Super Usercannot delete users who are currently logged in to the network element.

Security Management — Addition, Modification, and Deletion of Users10-12


10.4 ACCESSING THE NETWORK ELEMENT

10.4.1 Login

The user needs to log in to the network element to configure it. If the user attempts to log inwith an invalid UID or PID three times within 10 minutes, the Network Element will refuseto authenticate that user for 10 minutes. After 10 minutes, the user can try to log in to thenetwork element again. The prohibition of authentication cannot be disabled even by theTL1 command.

A Super User can prohibit any Normal User from logging in to the NE.

10.4.2 Logout

There are three ways to logout from the network element.

10.4.2.1 Manual Logout

The user can log out manually.

10.4.2.2 Automatic Logout

When the user is idle for 30 minutes, the network element will log the user out.

10.4.2.3 Forced Logout

If the connection between the NE and CID is disconnected, the user is forcibly logged out.

Security Management — Accessing the Network Element10-13



Security Management10-14 E

Documents

03_N08342 Func. Descrip