Fungsi Unode

DOI-N08152
NEC Corporation
7-1, Shiba 5-Chome, Minato-Ku, Tokyo 108-8001, Japan
TEL: +81-3-3454-1111
FAX: +81-3-3798-1510
TELEX: NECTOK J22686
EMAIL: otd-doc@onw.nec.co.jp
SpectralWave
UNIVERSAL NODE
BROAD BAND MANAGER
FUNCTIONAL DESCRIPTION
DOI-N08152
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 2001, 2002 by NEC Corporation
All rights reserved.
Printed in Japan
1st Edition July 2001, approved by H. Momiji of NEC-1ONW/1DD
2nd Edition September 2001, approved by K. Sakamoto of NEC-1ONW/1DD
3rd Edition September 2001, approved by K. Sakamoto of NEC-1ONW/1DD
4th Edition February 2002, approved by K. Sakamoto, S. Fukunaga of NEC-1ONW/1DD
5th Edition May 2002, approved by S. Fukunaga of NEC-1ONW/1DD
6th Edition July 2002, approved by S. Fukunaga, H. Takeda of NEC-1ONW/1DD
7th Edition September 2002, approved by H. Momiji of NEC-1ONW/1DD
DOI-N08152
SpectralWave U-Node BBM
Contents
Contents
- i -
1. SIGNAL INTERFACE FUNCTION 1-1
1.1 Overhead Process ...............................................................................1-2
1.1.1 Regenerator Section (RS) ................................................................... 1-2
1.1.2 Multiplex Section (MS) [Line (L)] ......................................................... 1-4
1.1.3 Higher Order Path (VC-4) & Lower Order Path (VC-3) ........................ 1-6
1.1.4 Higher Order Path (VC-3) .................................................................... 1-9
1.1.5 Lower Order Path (VC-12) ................................................................. 1-12
1.1.6 DS3 Interface Frame ......................................................................... 1-14
1.1.6.1 Frame Format ....................................................................... 1-14
1.1.6.2 DS3 Mapping ........................................................................ 1-15
1.1.7 GFP Frame Process .......................................................................... 1-16
1.1.7.1 GFP Frame Format ............................................................... 1-16
1.1.7.2 GFP Mapping ........................................................................ 1-17
1.2 Trace Function ..................................................................................1-18
1.2.1 16-Byte Mode .................................................................................... 1-19
1.2.2 64-Byte Mode .................................................................................... 1-19
1.2.3 1-Byte Mode ...................................................................................... 1-19
1.2.4 Trace Message Character ................................................................. 1-20
1.3 Signal Label Function .......................................................................1-21
1.3.1 SDH Path C2 Byte Codes ................................................................. 1-21
1.3.2 SDH Path V5 Byte Codes .................................................................. 1-22
1.3.3 SONET STS Path Signal Label Assignments ................................... 1-23
2. CROSSCONNECT 2-1
2.1 Crossconnect Process Capacity .......................................................2-1
2.1.1 Matrix Capacity .................................................................................... 2-1
2.1.2 Lower Order Crossconnect .................................................................. 2-4
2.1.2.1 Crossconnection between Main Shelf and EXTWB Shelf ...... 2-4
2.1.2.2 Crossconnection between EXTWB Shelves ........................... 2-8
2.2 Crossconnect Level ..........................................................................2-10
2.2.1 Crossconnect Termination Point ....................................................... 2-10
DOI-N08152
Contents
- ii -
2.3 Crossconnect Types .........................................................................2-11
2.3.1 Higher Order Path ............................................................................. 2-11
2.3.1.1 1-Way ................................................................................... 2-11
2.3.1.2 2-Way ................................................................................... 2-12
2.3.2 Lower Order Path .............................................................................. 2-12
2.3.2.1 1-Way ................................................................................... 2-13
2.3.2.2 2-Way ................................................................................... 2-14
2.3.3 Supplementary Explanation ............................................................... 2-15
2.3.4 Idle Signal Processing ....................................................................... 2-16
2.4 Time Slot Management .....................................................................2-17
2.4.1 Assignments for Main Shelf Front ..................................................... 2-17
2.5 Virtual Concatenation .......................................................................2-19
2.5.1 Overview ............................................................................................ 2-19
2.5.2 Crossconnect Levels ......................................................................... 2-19
2.5.3 Crossconnect ..................................................................................... 2-20
2.5.3.1 GBE Package ....................................................................... 2-20
2.5.3.2 GBEM Package .................................................................... 2-20
2.5.3.3 Crossconnection Images ...................................................... 2-20
3. PROTECTION 3-1
3.1 Package Protection .............................................................................3-4
3.1.1 Switching Configuration ....................................................................... 3-4
3.1.2 Switching Mode ................................................................................... 3-4
3.1.3 Lockout Mode ...................................................................................... 3-5
3.1.4 Switching Status .................................................................................. 3-5
3.2 Line Protection ....................................................................................3-6
3.2.1 Switching Configuration ....................................................................... 3-6
3.2.2 Applicable Interface Package .............................................................. 3-6
3.2.3 Linear Protection ................................................................................. 3-7
3.2.3.1 Linear Protection Mode ........................................................... 3-7
3.2.3.2 Switching Mode ...................................................................... 3-9
3.2.3.3 Switching Status ................................................................... 3-10
3.2.3.4 Maintenance ......................................................................... 3-10
3.2.4 Ring Protection .................................................................................. 3-11
3.2.4.1 Ring Protection Mode ........................................................... 3-13
3.2.4.2 Switching Mode .................................................................... 3-14
DOI-N08152
Contents
- iii -
3.2.4.4 Maintenance ......................................................................... 3-15
3.3 Path Protection ..................................................................................3-16
3.3.1 Switching Mode ................................................................................. 3-16
3.3.1.2 Maintenance ......................................................................... 3-17
3.4 Interlocking Ring Protection ............................................................3-18
3.5 Overhead (OH) Protection ................................................................3-19
3.5.1 Objects for OH Protection .................................................................. 3-19
3.5.2 Types of OH Protection ..................................................................... 3-19
4. SYNCHRONIZATION 4-1
4.1 Synchronization ..................................................................................4-1
4.1.1 Clock Interface ..................................................................................... 4-1
4.1.1.1 External Timing Incoming ................................................... 4-1
4.1.1.2 External Timing Outgoing ................................................... 4-1
4.1.1.3 SDH [SONET] Line Timing ..................................................... 4-2
4.1.1.4 2M Line Timing ....................................................................... 4-2
4.1.2 Timing Mode ........................................................................................ 4-3
4.1.3 Clock Features .................................................................................... 4-4
4.2 Timing Source Control .......................................................................4-5
4.2.1 Quality Level ........................................................................................ 4-5
4.2.2 Priority Level Setting ............................................................................ 4-5
4.2.3 SSM Control ........................................................................................ 4-6
4.3 Timing Source Selection ....................................................................4-7
4.3.1 External Output Timing Source Switching Modes ............................... 4-7
4.3.2 External Output Message Translation Modes ..................................... 4-7
4.3.3 Signal Fail ............................................................................................ 4-7
4.3.4 Hold-off Time ....................................................................................... 4-8
4.3.5 SSM Hold-off Time .............................................................................. 4-8
4.3.6 Wait-to-Restore Time .......................................................................... 4-8
4.3.7 Switching Control ................................................................................. 4-8
4.4 Precautions ..........................................................................................4-9
4.4.1 Timing Loop Example .......................................................................... 4-9
DOI-N08152
Contents
- iv -
5. CONFIGURATION MANAGEMENT 5-1
5.1 Configuration Management Object ...................................................5-1
5.1.1 NODE (NE: Network Element) ............................................................. 5-2
5.1.2 SHELF ................................................................................................. 5-2
5.1.3 Package (PKG) .................................................................................... 5-3
5.1.3.1 SINFM PKG ............................................................................ 5-4
5.1.3.2 Slot Number ............................................................................ 5-4
5.1.4 CPU ..................................................................................................... 5-6
5.1.5 Facility ................................................................................................. 5-7
5.1.6 External Clock (EXTCLK) .................................................................... 5-7
5.1.7 Switch Group ....................................................................................... 5-8
5.1.8 Synchronization ................................................................................. 5-10
5.1.9 Overhead Access Channel (OHCH) .................................................. 5-10
5.1.10 Data Communication Channel (DCC) .............................................. 5-10
5.1.10.1 OHC/OHCEXT Package Type and DCC ........................... 5-11
5.1.10.2 COM Package Type and DCC ........................................... 5-11
5.1.11 HKC/HKA .......................................................................................... 5-11
5.1.12 V.11 Port ........................................................................................... 5-11
5.2 Service State ......................................................................................5-12
5.2.1 Service State Definition ..................................................................... 5-12
5.2.1.1 Primary Service State (PST) ................................................. 5-12
5.2.1.2 Secondary Service State (SST) ............................................ 5-12
5.3 Other Administration States ............................................................5-13
5.3.1 Port Mode .......................................................................................... 5-13
5.3.2 Mode Mismatch ................................................................................. 5-13
5.4 Memory Backup ................................................................................5-14
5.4.1 Overview ............................................................................................ 5-14
5.4.2 Memory Configuration ....................................................................... 5-14
5.5 Starting up NE ...................................................................................5-16
5.5.1 Hot Start ............................................................................................ 5-16
5.5.2 Cold Start ........................................................................................... 5-16
5.6 Inventory ............................................................................................5-17
5.6.1 Package Inventory ............................................................................. 5-17
5.6.2 NE Information Inventory ................................................................... 5-17
DOI-N08152
Contents
- v -
5.7 Object AIDs ........................................................................................5-18
5.7.1 Node .................................................................................................. 5-18
5.7.2 Shelf .................................................................................................. 5-19
5.7.3 Package ............................................................................................. 5-20
5.7.4 Line Facility ........................................................................................ 5-21
5.7.5 Package Protection Switch Group ..................................................... 5-22
5.7.6 Line Protection Switch Group ............................................................ 5-23
5.7.7 Synchronization ................................................................................. 5-24
5.7.8 Path Facility ....................................................................................... 5-25
5.7.8.1 Higher-Order Path ................................................................ 5-25
5.7.8.2 Lower-Order Path (to/from SDH) .......................................... 5-26
5.7.8.3 Lower-Order Path (to/from PDH) .......................................... 5-26
5.7.9 Path Monitor ...................................................................................... 5-27
5.7.9.1 Higher-Order Path ................................................................ 5-27
5.7.9.2 Lower-Order Path ................................................................. 5-28
5.7.10 Path Termination Point .................................................................... 5-29
5.7.10.1 Higher-Order Path .............................................................. 5-29
5.7.10.2 Lower-Order Path ............................................................... 5-29
5.7.11 External Clock Input ......................................................................... 5-30
5.7.12 Housekeeping Alarm ........................................................................ 5-30
5.7.13 Housekeeping Control ..................................................................... 5-30
5.7.14 V11 User Channel Port .................................................................... 5-30
5.7.15 Overhead Access Channel .............................................................. 5-31
5.7.16 Data Communication Channel (DCC Port) ...................................... 5-31
5.7.17 Virtual Concatenation (GBEM) ......................................................... 5-31
5.7.18 Channel ID (GBEM) ......................................................................... 5-31
5.7.19 CPU ................................................................................................. 5-32
5.7.20 Profile ............................................................................................... 5-33
5.7.21 Memory Card .................................................................................... 5-33
5.7.22 Temporary Memory ........................................................................... 5-33
5.7.23 All ...................................................................................................... 5-33
6. PERFORMANCE MONITORING 6-1
6.1 Performance Monitoring (PM) Type ..................................................6-1
6.1.1 Physical Layer ..................................................................................... 6-1
DOI-N08152
Contents
- vi -
6.1.2 Regenerator Section Layer (Section Layer) ........................................ 6-2
6.1.3 Multiplex Section Layer (Line Layer) ................................................... 6-3
6.1.4 DS3 Line Layer .................................................................................... 6-5
6.1.5 E12/E31/E32 Line Layer ...................................................................... 6-6
6.1.6 GBE Line Layer ................................................................................... 6-7
6.1.7 GBEM Line Layer ................................................................................ 6-9
6.1.8 HPT3 Layer ....................................................................................... 6-11
6.1.9 HPTM3 Layer .................................................................................... 6-12
6.1.10 VCT Layer ......................................................................................... 6-13
6.1.11 HP Monitor ........................................................................................ 6-14
6.1.12 LP Monitor ......................................................................................... 6-16
6.1.13 HPT ................................................................................................... 6-17
6.1.14 LPT ................................................................................................... 6-19
6.1.15 Multiplex Section Protection .............................................................. 6-21
6.1.16 AU Path ............................................................................................. 6-22
6.1.17 SES Threshold .................................................................................. 6-23
6.2 PM Data Management .......................................................................6-24
6.2.1 PM Data Type .................................................................................... 6-24
6.2.2 Data Reliability ................................................................................... 6-24
6.3 TCA Function .....................................................................................6-25
6.3.1 TCA Threshold .................................................................................. 6-25
6.4 IPPM Management ............................................................................6-26
6.4.1 Monitor Point ..................................................................................... 6-26
6.4.1.1 Monitor Points for STMn Interface ........................................ 6-26
6.4.1.2 Monitor Points for PSWWB (EXTWB Shelf) ......................... 6-26
6.4.2 Accumulation ..................................................................................... 6-27
7. FAULT MANAGEMENT 7-1
7.1 Monitored Items ..................................................................................7-1
7.2 Management Parameters ....................................................................7-2
7.2.1 Alarm Severity ..................................................................................... 7-2
7.2.2 Delay/Stretch Time .............................................................................. 7-3
7.3 Alarm Report .......................................................................................7-4
DOI-N08152
Contents
- vii -
7.3.1 LED Process ........................................................................................ 7-4
7.3.2 Report to User Interface ...................................................................... 7-4
7.3.3 Office Alarm ......................................................................................... 7-4
7.3.3.1 Office Alarm Type ................................................................... 7-4
7.3.3.2 Delay/Stretch Process ............................................................ 7-5
7.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-1
8.1.1 Mode of Logging .................................................................................. 8-1
8.2 AO Buffer .............................................................................................8-2
8.2.1 Mode of Logging .................................................................................. 8-2
9. MAINTENANCE OPERATION 9-1
9.1 Loopback Function .............................................................................9-1
9.1.1 Line Loopback ..................................................................................... 9-1
9.1.1.1 Facility Loopback .................................................................... 9-2
9.1.1.2 Terminal Loopback ................................................................. 9-2
9.1.1.3 Remote Loopback ................................................................... 9-3
9.1.2 V.11 Port Loopback ............................................................................. 9-5
9.1.2.1 Facility Loopback .................................................................... 9-5
9.1.2.2 Terminal Loopback ................................................................. 9-5
9.2 Automatic Laser Shutdown ................................................................9-6
9.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
9.2.3 Lower-Level Optical Output (Reflected Alarm Detection) .................... 9-9
9.2.4 Forced Optical Output Shutdown ........................................................ 9-9
9.3 Overhead Access ..............................................................................9-10
9.3.1 User Channel Access ........................................................................ 9-10
9.3.1.1 Accessible Facility ................................................................ 9-10
9.3.1.2 Usable Overhead Byte .......................................................... 9-10
DOI-N08152
Contents
- viii -
9.3.1.3 User Channel Loopback ....................................................... 9-10
9.3.2 DCC LAPD Access ............................................................................ 9-11
9.3.3 Overhead Through ............................................................................ 9-11
9.3.4 Orderwire Access .............................................................................. 9-11
9.3.4.1 Orderwire Interface ............................................................... 9-11
9.3.4.2 Calling ................................................................................... 9-12
9.4 Line Switch Exercise ........................................................................9-13
9.5 Housekeeping ....................................................................................9-14
9.5.1 Housekeeping Alarm ......................................................................... 9-14
9.5.2 Housekeeping Control ....................................................................... 9-14
9.6 Reset Function ..................................................................................9-15
9.6.1 How to Reset CPU ............................................................................ 9-15
9.6.2 Restart Level ..................................................................................... 9-15
9.7 Path Test ............................................................................................9-16
9.7.1 Example of Operation ........................................................................ 9-16
9.7.2 Test Access Sending Function .......................................................... 9-17
9.7.3 Test Access Receiving Function ....................................................... 9-17
10. SECURITY MANAGEMENT 10-1
10.1 Type of User Account ......................................................................10-1
10.1.1 Super User ........................................................................................ 10-1
10.1.2 Normal User ...................................................................................... 10-1
10.2 User Attributes .................................................................................10-1
10.2.1 User Identification (UID) .................................................................... 10-2
10.2.1.1 Valid ASCII Characters for UID .......................................... 10-2
10.2.2 Password (PID) ................................................................................. 10-3
10.2.2.1 Valid Password ................................................................... 10-3
10.2.2.2 Valid ASCII Characters for PID ........................................... 10-4
10.2.3 User Account Expiration ................................................................... 10-5
10.2.4 Password Aging ................................................................................ 10-5
10.2.5 Password Expiration ......................................................................... 10-5
10.2.6 User Privilege Code Level ................................................................ 10-5
10.3 Addition, Modification, and Deletion of Users ............................10-12
10.3.1 Addition ........................................................................................... 10-12
DOI-N08152
Contents
- ix -
10.3.2 Modification ..................................................................................... 10-12
10.3.3 Deletion ........................................................................................... 10-12
10.4 Accessing the Network Element ...................................................10-13
10.4.1 Login ............................................................................................... 10-13
10.4.2 Logout ............................................................................................. 10-13
10.4.2.1 Manual Logout .................................................................. 10-13
10.4.2.2 Automatic Logout .............................................................. 10-13
10.4.2.3 Forced Logout ................................................................... 10-13
DOI-N08152
Contents
- x -
E
This page is intentionally left blank.
DOI-N08152
Signal Interface Function
1-1
1. SIGNAL INTERFACE FUNCTION
This section provides a description of the function for managing signal interface supported by
U-Node BBM: access methods and input/output main signal operation. Physical
specifications for interfaces are given in the General Information manual.
U-Node BBM supports the following main signals:
!SDH [SONET] Optical Signal
STM-64 [OC-192]
STM-16 [OC-48]
STM-4 [OC-12]
STM-1 [OC-3]
STM-0
!STM1e Signal
!DS3 Signal
!Gigabit Ethernet Signal
!2M Signal
!34M Signal
!45M Signal
DOI-N08152
Signal Interface Function Overhead Process
1-2
1.1 OVERHEAD PROCESS
Descriptions given here show the overhead byte process managed by U-Node BBM.
1.1.1 Regenerator Section (RS)
The following table lists the functions related to the RS (Regenerator Section) overhead byte
on the SDH [SONET] signal.
! A1, A2 Byte
A1, A2 byte is used to synchronize the SDH [SONET] frame. If neither the A1 or A2
pattern is detected, the frame goes out of synchronization, and the OOF (out of frame)
alarm is issued.
! J0/C1 Byte
J0/C1 byte can be used as J0 byte or C1 byte, according to the users definition. In the J0
mode, the connection of section layers can be verified by transferring the Section Access
Point 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 Trace
STM-ID (STS-ID)
Fault Management (TIM)
Z0 Overhead Access Function
NU(1row) Overhead Access Function
B1 Section Error Monitor (BIP-8) PM Function (CV, etc.)
E1 (1) USER-Ch
(2) Section Orderwire
Overhead Access Function
F1 USER-Ch Overhead Access Function
NU(2row) Overhead Access Function
D1-3 Regenerator Section DCC Overhead Access Function
Media Byte
Unuse Byte
DOI-N08152
1-3
! NU Byte (1st row, 2nd row)
NU byte is used for the overhead byte access function. When this byte is not used,
! Receiving side: ignores the rows
! Sending Side: can insert the Idle Code to the rows
! B1 Byte
B1 byte based on the BIP-8 is used to detect an error from the main signal. The detected bit
error is used for the performance monitoring function and failure detection.
! E1 Byte
E1 byte is used for the overhead byte access function. E1 byte can be used for the
orderwire or a user channel that is between regenerator sections of -law or A-law. When
this byte 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 Byte
F1 Byte is used for the overhead byte access function. F1 byte is also available for the user
channel. When this byte is not used,
! Receiving Side: ignores
! Sending Side: can insert the Idle Code
! D1-D3 Byte
D1 through D3 bytes are used for the overhead byte access function. These three bytes are
used together in communication as a Data Communication Channel (DCCr) signal at
192 K. When these bytes are not used,
DOI-N08152
1-4
1.1.2 Multiplex Section (MS) [Line (L)]
! B2 Byte
The error count is detected by using B2 byte based on BIP-n 24. The detected bit error is
used 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 Byte
Upper 13 bits of K1, K2 byte are used for line protection. Lower 3 bits of K1, K2 byte are
used 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 failure
related to the main signal is detected, an MS-AIS is inserted to the main signal.
! D4-D12 Byte
D4 through D12 bytes are used for the overhead byte access function. These nine bytes are
used together in communication as a Data Communication Channel (DDCm) at 576 K, or
as 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 Control
Line Status Transfer
Protection Function (APS Process)
D4-12 (1) USER-Ch
(2) Line DCC
S1 Synchronization Status Synchronization Function (SSM Process)
Z1/Z2 Overhead Access Function
M1 Line Remote Side Error Display PM Function
E2 (1) USER-Ch
(2) Line Orderwire
Unuse Byte
DOI-N08152
1-5
! S1 Byte
The b1 to b4 bits of S1 byte are not used. The b5 to b8 bits are used to display the
synchronization status for timing source selection. Refer to the 4. Synchronization section
for synchronization using the S1 byte. When this byte is not used,
! Z1 Byte
Z1 byte is used for the overhead byte access function. When this byte is not used,
! Z2 Byte
Z2 byte is used for the overhead byte access function. When this byte is not used,
! M1 Byte
M1 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 Byte
E2 byte is used for the overhead byte access function. E2 byte can be used for the
orderwire or the user channels that are between multiplex sections of -law or A-law.
When this byte is not used,
! Sending Side: can insert the Silence Code (for the use of orderwire)
can insert the Idle Code (for the use of data channel)
DOI-N08152
1-6
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) through EXTWB only.
4. For Higher Order Path (VC-4) through GBEM only.
! J1 Byte
The connection of path layers can be verified by transferring the Path Access Point
Identifier 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 Monitoring
points for failure detection. Refer to the 1.2 Trace Function subsection for details.
! B3 Byte
The error count is detected by using B3 byte based on BIP-8. The detected bit error is used
for the performance monitor function and failure detection. Refer to the 6. Performance
Monitoring section for details. Conditions detected as B3 alarms are:
! DEG: degraded bit error, causing man signal deterioration
These alarms are monitored at monitoring points. Also, the Intermediate Path Performance
Monitor (IPPM) function at monitoring points is supported.
J1 Path Trace Failure Detecting Function (J1-TIM)
B3 Path Error Monitor (BIP-8) PM Function
C2 Signal label Failure Detecting Function (UNEQ, PDI,
PLM
NOTE 1
, VC-AIS
NOTE 2
)
G1 SDH
b1-b4: Path Remote Side Error (REI)
b5: Path Remote Side Defect (RDI)
b6-b8: Unused
PM Function, Fault Management
SONET
b1-b4: Path Remote Side Error (REI)
b5-b7: Path Remote Side Defect (RDI)
b8: Unused
F2
H4
Position Identifier
NOTE 3
Failure Detecting Function (LOM)
Virtual Concatenation Multiframe
NOTE4
F3
K3
N1
DOI-N08152
1-7
! C2 Byte
C2 byte indicates VC path configuration. A failure in the VC path configuration can be
detected by verifying the received C2 byte. When an EXTWB shelf is used to terminate
HPT, the TUG structure label is output as a C2 byte. At VC-3 Lower Order Path
Termination points, Async-VC-3 is output as a C2 byte. At monitoring points, only the
UNEQ alarm is detected. Refer to the 1.3 Signal Label Function subsection for details.
! G1 Byte
Monitoring the G1 byte enables Performance Monitoring at HPT termination points of the
EXTWB shelf, and detection of the error status on a remote side. Intermediate Path
Performance Monitor (IPPM) function is also available. However, the use of this byte is
not available for the EXTWB shelfs Performance Monitoring function at Lower Order
Path Monitoring points. Refer to the 6. Performance Monitoring section and the 7. Fault
Management section for details.
! F2 Byte
This byte is not managed and the status of each side is as follows:
! H4 Byte
This byte is not managed except for higher order path (VC-4) through EXTWB and
GBEM. When not managed, the status of each side is as follows:
When an EXTWB shelf is used and the crossconnect level VC-12 exists, this byte is used as
a multiframe position indicator at Higher Order Path Termination points. When the
crossconnect level VC-12 does not exist or the byte is not used at monitoring points, the
status of each side is as follows:
! Sending Side: outputs multiframe indicator
When a GBEM package is used, this byte synchronizes multiframes in order to detect
phase difference among each VC-4 path configuring virtual concatenation. Following
shows the H4 byte multiframe sequence:
DOI-N08152
1-8

! F3 Byte
! K3 Byte
! N1 Byte
H4 Byte Multiframe Sequence
Bit 1 Bit 2 Bit 3 Bit 4 1st Multiframe MFI1 (Bits 1 - 4) 1st Multiframe # 2nd Multiframe #
Previous Frame (n1) n1
2nd Multiframe Indicator
MFI2 MSB (Bits 1 - 4)
0 0 0 0 0
n
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
(Bits 5 - 8)
1 1 1 1 15
Next Frame (n+1)
n+1
DOI-N08152
1-9
1.1.4 Higher Order Path (VC-3)
NOTES:
1. Detected at termination points.
3. For Higher Order Path (VC-3) through GBEM only.
! J1 Byte
TIM alarm is issued. Refer to the 1.2 Trace Function subsection for details.
! B3 Byte
The error count is detected by using B3 byte based on BIP-8. The detected bit error is used
for the performance monitor function and failure detection. Refer to the 6. Performance
Monitoring section for details. Conditions detected as B3 alarms are:
! DEG: degraded bit error, causing man signal deterioration
These alarms are monitored at monitoring points. Also, the Intermediate Path Performance
Monitor (IPPM) function at monitoring points is supported.
! C2 Byte
C2 byte indicates VC path configuration. A failure in the VC path configuration can be
detected by verifying the received C2 byte. When mapping the DS3 signal to a SONET
signal, and sending it to a remote node, the C2 byte outputs the DS3 asynchronous label.
Refer to the 1.3 Signal Label Function subsection for details.
B3 Path Error Monitor (BIP-8) PM Function
C2 Signal label Failure Detecting Function (UNEQ, PDI,
PLM
NOTE 1
, VC-AIS
NOTE 2
)
G1 b1-b4: Path Remote Side Error (REI)
b5-b7: Path Remote Side Defect (RDI)
b8: Unused
PM Function, Fault Management
F2
H4
Virtual Concatenation Multiframe
NOTE3
Z3
Z4
Z5
DOI-N08152
1-10
! G1 Byte
Monitoring the G1 byte enables Performance Monitoring at HPT3 on the DS3 package, and
detection of the error status on a remote side. Intermediate Path Performance Monitor
(IPPM) function is also available. Refer to the 6. Performance Monitoring section and the
7. Fault Management section for details.
! F2 Byte
This byte is not managed since the U-Node BBM does not have path termination points.
! H4 Byte
This byte is not managed except for a path through GBEM. When not managed, the status
of each side is as follows:
When a GBEM package is used, this byte synchronizes multiframes in order to detect
phase difference among each VC-3 path configuring virtual concatenation. Following
shows the H4 byte multiframe sequence:

H4 Byte Multiframe Sequence
Bit 1 Bit 2 Bit 3 Bit 4 1st Multiframe MFI1 (Bits 1 - 4) 1st Multiframe # 2nd Multiframe #
Previous Frame (n1) n1
MFI2 MSB (Bits 1 - 4)
0 0 0 0 0
n
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
(Bits 1 - 4)
1 1 1 0 14
(Bits 5 - 8)
1 1 1 1 15
Next Frame (n+1) n+1
DOI-N08152
1-11
! Z3 Byte
! Z4 Byte
! Z5 Byte
DOI-N08152
1-12
1.1.5 Lower Order Path (VC-12)
NOTES:
1. Not detected at monitoring points.
! J2 Byte
TIM alarm is issued. This byte, however, is not monitored at Lower Order Path Monitoring
points for failure detection. Refer to the 1.2 Trace Function subsection for details.
! V5 Byte
Bits 1 and 2
The error count is detected by using bits 1 and 2 based on BIP-2. The detected bit error is
used 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
Bit 3
The 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 the far-end side for its PM. PM detection using this
bit at monitoring points is not supported.
Bit 4
This bit is not managed since the U-Node BBM does not have a process function using this bit.
Bits 5 thru 7
These bits indicate VC path configuration. A failure in the VC path configuration can be
detected by verifying the received bits 5 to 7 of the V5 byte. For VC-12, ASYNC-FLOAT
is output. Refer to the 1.3 Signal Label Function subsection for details.
Bit 8
By monitoring this bit, a path error status is output to a remote side as an RDI alarm. The
far-end side detects the RDI alarm from this information and uses this bit for its PM.
V5 b1, b2: Path Error Monitor (BIP-2)
b3: Path Remote Side Error (REI)
b4: Unused
b5-b7: Signal Label
b8: Path Remote Side Defect (RDI)
PM Function, Failure Detecting Function
(UNEQ, PLM
NOTE 1
, PDI, VC-AIS
NOTE 2
,
RDI)
K4
N2
DOI-N08152
1-13
! K4 Byte
This byte is not managed since the U-Node BBM does not have a process function using
this byte.
! N2 Byte
This byte is not managed since the U-Node BBM does not have a process function using
this byte.
DOI-N08152
1-14
1.1.6 DS3 Interface Frame
1.1.6.1 Frame Format
The DS3 signal is partitioned into multiframes (M-Frames) of 4760 bits each, then these M-
Frames are divided into 7 M-Subframes having 680 bits each. Two types of framings are
supported as shown below:
! M13 Multiframe
! C-Bit Parity Multiframe
An unframed DS3 is also available for the use of other purposes.
Control Bit Usage
X Bit Monitors remote alarms
P Bit Monitors terminal section
M Bit Patterns M-frame period (M0=0, M1-1)
F Bit Patterns M-subframe period (F0=0, F1=1)
C Bit Used for stuffing control
S Bit Stuffing bit
Control Bit Usage
X Bit Monitors remote alarms
P Bit Monitors errors in terminal section
M Bit Patterns M-frame period (M0=0, M1-1)
F Bit Patterns M-subframe period (F0=0, F1=1)
C Bit Used for stuffing control
AIC Bit Monitors frames (AIC=1)
Nr Bit Unused (Nr=1
FEAC Bit Monitors far-end failure/status
CP Bit Monitors errors in terminal section
FEBE Bit Monitors errors in far-end terminal section
DLt Bit Unsupported (user channel for terminal section)
S Bit Stuffing bit
DOI-N08152
1-15
1.1.6.2 DS3 Mapping
The DS3 signal is mapped to a payload (information bit) on STS-1 SPE signal. Following
shows the composition for mapping DS3 signal to STS-1 SPE signal, and STS-1 SPE signal
to STS-1 signal:
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
R R C1 I 25 R R C2 I 25 R R C3 I 25
S
T
S

P
O
H
F
I
X
E
D

S
T
U
F
F
F
I
X
E
D

S
T
U
F
F
28 BYTES 28 BYTES 28 BYTES
BYTE:
I = i i i i i i i i
R = r r r r r r r r
C1 = r r c i i i i i
C2 = c c r r r r r r
C3 = c c r r o o r s
BIT:
i: information (payload) bit
r: fixed stuff bit
c: stuff control bit
s: stuff opportunity bit
o: overhead communication channel bit
680 BIT
M-Subframe 1
M-Subframe 2
M-Subframe 3
M-Subframe 4
M-Subframe 5
M-Subframe 6
M-Subframe 7
DS3 MULTIFRAME (M13 / C BIT PARITY / UNFRAMED)
DOI-N08152
1-16
1.1.7 GFP Frame Process
1.1.7.1 GFP Frame Format
Following shows the GFP frame format:
! Core Header
This header is a fixed-length filed of four octets, and is used for frame synchronization and
basic data link:
PLI
PLI expresses the length of payload area (unit: octet), and its values are from 0 thru
65535. Among these values, especially between 0 thru 3 indicates GFP control
frame.
cHEC
cHEC is a 16-bit CRC obtained from PLI, and is used for frame synchronization
and correction of core header errors. Polynomial to obtain the value is:
x
16
+ x
15
+ x
12
+ 1
! Payload Header
This header is a variable-length field of 4 thru 64 octets, and is used for managing specific
data link for upper protocol. Following three fields make up the he payload header:
Type
Type expresses classification of payloads (upper protocol).
tHEC
tHEC is a 16 bit CRC obtained from the Type. Polynomial to obtain the value is:
x
16
+ x
15
+ x
12
+ 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)
DOI-N08152
1-17
Extension Header
This 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 multiple
packets.
eHEC
eHEC is a 16 bit CRC obtained from the Extension Header. Polynomial to obtain
the value is:
x
16
+ x
15
+ x
12
+ 1
! Payload Information Field
PDU
This filed stores upper protocol data. The size is the remaining where taking other
headers from full length of GFP frame (min. 0, max. 65535 octets).
Payload FCS
Payload FCS is 32 bits CRC obtained by Payload field; this field is not used.
1.1.7.2 GFP Mapping
Frame-Mapped GFP is the process where recognizing frame partitions of upper protocol, and
encapsulating each frame to GFP (Generic Framing Procedure). Following shows the
process that Ethernet signal is mapped to GFP.
Taking IFG (Inter Frame Gap), Preamble, and SFD (Start of Frame Delimiter) out of the
Ethernet frame, the remaining fields are stored in Payload field of GFP frame. Between GFP
and 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 BBM 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)
DOI-N08152
Signal Interface Function Trace Function
1-18
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 [SONET] optical interface, such
as STM-64 [OC-192], STM-16 [OC-48], STM-4 [OC-12], STM-1 [OC-3], and STM-0, and
an STM-1e electrical interface.
The path trace using J1 byte includes the 16-byte mode and 64-byte mode. The J1 byte path
trace supports the monitoring function to all the paths on the line facilities of STM-64
[OC-192], STM-16 [OC-48], STM-4 [OC-12], STM-1 [OC-3], STM-0, and STM-1e.
J1 byte is terminated at the Higher Order Path Termination points by the DS3 package or the
PSW5WB/PSW10WB packages on the EXTWB shelf, in the 16-byte or 64-byte mode.
For the Lower Order Path trace, J1 or J2 byte is terminated at the Lower Order Path
Termination points by the PDH interface package in the 16-byte mode. However, the Lower
Order 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 (trace
indication mismatch) alarm is issued; this detection can be inhibited by a user definition.
DOI-N08152
1-19
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 assigned
to the trace data.
! C
1
to C
7
(C1=MSB) at Byte # 1 are the results of the calculation from the fore
frame CRC-7 (X
7
+X
3
+1). U-Node BBM automatically adds these CRC
calculation 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, the
received bytes are converted to be indicated as numerals using 1 through 256.
Byte # Value (bits 1 to 8)
1 1 C
1
C
2
C
3
C
4
C
5
C
6
C
7
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
DOI-N08152
1-20
1.2.4 Trace Message Character
To specify the section trace or path trace in the 16-byte mode or 64-byte mode described
above, and to enter the expected value and transmitting value for the trace, use the following
ASCII 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
DOI-N08152
Signal Interface Function Signal Label Function
1-21
1.3 SIGNAL LABEL FUNCTION
The signal label function is provided to monitor the path configuration status. See the
following tables for the SDH/SONET path signal labels:
1.3.1 SDH Path C2 Byte Codes
The following shows the SDH signal labels for VC-4-64c, VC-4-16c, VC-4-4c, VC-4, and
VC-3:
Hex Code Description
00 Unequipped or supervisoryunequipped
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
CF HDLC according
FE Test signal, O.181 specific mapping
AIS Alarm Indication Signal
ATM Asynchronous Transfer Mode
DQDB Distributed Queue Dual Bus
FDDI Fiber Distributed Data Interface
HDLC High-level Data Link Control
MAN Metropolitan Area Network
TUG Tributary Unit Group
DOI-N08152
1-22
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
DOI-N08152
1-23
1.3.3 SONET STS Path Signal Label Assignments
The following shows the signal labels for STS-192c, STS-48c, STS-12c, STS-3c, and STS-1:
At the receiving side, if a signal label 00 (unequipped) is detected, a UNEQ_RX (or UNEQ
for HPT3) alarm is issued.
If the values of the received signal label and the expected signal label do not match, a PLMF
alarm is issued (for HPT3).
If the detected signal label is FF (bit: all-1), a VC_AIS alarm is issued.
If the detected signal label is FC, a PDI_RX (or PDI for HPT3) alarm is issued.
At the sending side, 00 (unequipped) is inserted to an unused path. For the DS3 interface, 01
(equipped) and 04 (asynchronous for DS3) can be specified as well.
Hex Code Content of STS SPE
00 Unequipped
01 Equipped NonSpecific Payload
02 VT-structured STS1 SPE
03 Locked VT Mode
04 Asynchronous mapping for DS3
12 Asynchronous mapping for DS4NA
13 Mapping for ATM
14 Mapping for DQDB
15 Asynchronous mapping for FDDI
16 HDLC Over Sonet Mapping
FE Test signal, O.181 specific mapping
FC Non-VT-structured STS-1 SPE with a Payload Defect
ATM Asynchronous Transfer Mode
DQDB Distributed Queue Dual Bus
FDDI Fiber Distributed Data Interface
HDLC High-level Data Link Control
SPE Synchronous Payload Envelope
VT Virtual Tributary
DOI-N08152
Signal Interface Function
1-24
E
DOI-N08152
Crossconnect Crossconnect Process Capacity
2-1
2. CROSSCONNECT
This section provides an overview of the crossconnect function.
2.1 CROSSCONNECT PROCESS CAPACITY
The crossconnect function of U-Node BBM is performed by the PSW package (PSW40 or
PSW80) mounted on the Main shelf and by the PSWWB package (PSW5WB or PSW10WB)
mounted on the EXTWB shelf. The PSW package performs the Higher Order Crossconnect
function, while the PSWWB package performs the Lower Order Crossconnect function.
Refer to the 4.4 Common Packages subsection in the Provisioning manual for details.
2.1.1 Matrix Capacity
The following tables show the crossconnect capacity supported by U-Node BBM:
! PSW40 Package
! PSW80 Package
Crossconnect Level Capacity
VC-4 (STS-3C) 256 256
VC-3 (STS-1) 768 768
VC-4 (STS-3C) 512 512
VC-3 (STS-1) 1536 1536
DOI-N08152
2-2
! PSW5WB Package
! PSW10WB Package
VC-12 2016 2016
VC-3 96 96
VC-12 4032 4032
VC-3 192 192
DOI-N08152
2-3
The following shows the connection between shelves. Numbers shown in the illustrations
indicate a reference number, counting one VC-3 [STS-1] as one channel time slot for the
PSW40 and PSW80.
Shelf Connection Image - PSW40
Shelf Connection Image - PSW80
385 1
2
48
49
337
384 768
INF1
INF8
PSW40 (MAIN)
TIME SLOTS (1 TO 384) FOR

SINF PKG SLOTS IN MAIN SHELF
TIME SLOTS (385 TO 768) FOR
EXTENSION SHELF
MAIN SHELF EXTENSION SHELF
PORT 1 AND 2
PORT 3 AND 4
PORT 5 AND 6
385 1
2
48
49
337
384 768
INF1
INF8
PSW80 (MAIN)
MAIN SHELF EXTENSION SHELF
1
2
48
49
337
384
769
1152
1
2
48
49
337
384
1153
1536
1
2
48
49
337
384
DOI-N08152
2-4
2.1.2 Lower Order Crossconnect
Lower Order Crossconnect is available by using an EXTWB shelf. However, the capacity of
the Lower Order Crossconnect is limited. See the following for detailed information:
2.1.2.1 Crossconnection between Main Shelf and EXTWB Shelf
The following shows a crossconnect block diagram when connecting an EXTWB shelf to the
Main shelf:
The Main shelf and an EXTWB shelf are connected by a 10G bus line. In the EXTWB shelf,
only the signals on the 10G bus line that execute Lower Order SW are connected to LOSW.
STM-N
Main Shelf
HOSW
PDH Signals
EXTWB Shelf #1
HOSW
PDH Signals
EXTWB Shelf #2
HOSW
LOSW LOSW
Signals
10G Bus
HOSW:
LOSW:
Higher order switch
Lower order switch
10G Bus
DOI-N08152
2-5
Under the configuration shown above, the following two types of connection are available:
! Add-Drop for PDH Signals
! Connecting STM-N Line Signal to Another STM-N Line through Lower Order
Crossconnection
STM-N
Main Shelf
HOSW
PDH Signal
EXTWB Shelf
HOSW HOSW
LOSW LOSW
Signal
STM-N
Main Shelf
HOSW
EXTWB Shelf
HOSW HOSW
LOSW LOSW
Signal
STM-N
Signal
DOI-N08152
2-6
For more detailed information, a block diagram for the PSWWB package on the EXTWB
shelf is shown below:
The PSWWB package connects a 10G signal line from the Main shelf and a 10G signal line
for the Downstream shelf via the through connection by default. Connection to the Lower
Order SW on the EXTWB shelf is available by specifying an AU signal on the 10G bus line
that enables connection to the Lower Order SW on the PSWWB package (by HPT Object
registration). For connection with PDH interface packages, connection to the Lower Order
SW is also available by specifying a signal that enables connection (by registration of E12F,
E31F, or E32F). Connection in the Lower Order Matrix is made depending on the
crossconnect map settings.
PDH Interface
10G Bus
Main Shelf
Downstream
Shelf
10G Bus
Lower Order
5G (10G)
Matrix
5G (10G)
NOTE: Items in parentheses should be applied
for PSW10WB.
PSW5WB (PSW10WB) Package
Higher Order SW
DOI-N08152
2-7
When connecting to the Lower Order SW, be aware that the Lower Order SW capacity is
limited in order to perform crossconnection. The limited capacity depends on the PSWWB
package as follows:
Therefore, total capacity of signals sent from the Main shelf and PDH interface packages for
Lower Order SW should be less than the values in the table above.
The minimum number of signals connected to the Lower Order SW from the Main shelf is
AU4 (155M). The minimum number of signals connected to the Lower Order SW from
PDH interface 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 when
the maximum number of PDH interface packages is registered on one EXTWB shelf:
PSWWB Type Lower Order SW Capacity
PSW5WB 5G
PSW10WB 10G
Package
Combination 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 SW
Maximum Number of Interface
Channels
E12 1.25G 504 ch
E31 2.5G 48 ch
E32 2.5G 48 ch
DOI-N08152
2-8
2.1.2.2 Crossconnection between EXTWB Shelves
This subsection explains how to connect two or more EXTWB shelves to the Main shelf. For
connection between the Main and EXTWB shelves, the following two types of connection
are available.
! When One EXTWB Shelf Is Directly Connected to the Main Shelf
! When Two EXTWB Shelves Are Directly Connected to the Main Shelf
Main Shelf
STM-N
EXTWB
Shelf
PDH Signal
Signal
10G Bus
Main Shelf
STM-N
EXTWB
Shelf
PDH Signal
Signal
10G Bus
EXTWB
Shelf
PDH Signal
10G Bus
DOI-N08152
2-9
When two EXTWB shelves are directly connected to the Main shelf, the capacity for
connection between the PSW package (PSW40 or PSW80) and the EXTWB shelves is 20G.
Two main signal 10G ports on the faceplate of the PSW package are used to connect with
EXTWB shelves. The table below shows the available combination of ports:
Package
Port Combination for Connecting
Two EXTWB Shelves
PSW40 Port 1, Port 2
PSW80 Port 1, Port 2
Port 3, Port 4
Port 5, Port 6
DOI-N08152
Crossconnect Crossconnect Level
2-10
2.2 CROSSCONNECT LEVEL
! For an SDH input signal, the signal is mapped into a time slot by VC-4, VC-4-4c,
VC-4-16c, VC-4-64c, or VC-4-7V level.
! When using an EXTWB shelf, SDH signals can be mapped into a time slot by VC-3 or
VC-12 level.
! For a SONET input signal, the signal is mapped into a time slot by STS-1, STS-3c,
STS-12c, STS-48c, STS-192c, or STS-3c-7V level.
! For an SDH-Japan input signal, the signal is mapped into a time slot by VC-3, VC-4,
VC-4-4c, VC-4-16c, VC4-64c, or VC-4-7V level.
Each signal level indicates the following bit rates:
2.2.1 Crossconnect Termination Point
The path band level and the operation mode within the path band should be selected when
specifying the crossconnect termination points:
! Path Band Level
For the Higher Order Crossconnect, select a path band level from AU-3 [STS-1], AU-4
[STS-3c], AU-4-4c [STS-12c], AU4-16c [STS-48c], AU-4-64c [STS-192c], and AU-4-7V
[STS-3c-7V]. When the input signal is SDH, AU-3 [STS-1] level cannot be selected.
For the Lower Order Crossconnect, select a path band level from TU12 and TU3.
! Operation Mode
The following two modes are provided for the Higher Order Crossconnect:
! AUTO: The path band level to be managed varies according to the input signal
levels received within the specified levels, where alarm detection and
performance monitoring are performed.
! FIX: Alarm detection and performance monitoring are enabled only when an
input signal of the specified level is received.
SIGNAL LEVEL BIT RATES SIGNAL LEVEL BIT RATES
VC-12 [STS-1] 2 Mbit/s VC-4-4c [STS-12c] 600 Mbit/s
VC-3 [LPT] 50 Mbit/s VC-4-16c [STS-48c] 2.5 Gbit/s
VC-3 [STS-1] 50 Mbit/s VC-4-64c [STS-192c] 10 Gbit/s
VC-4 [STS-3c] 150 Mbit/s VC-4-7V [STS-3c-7V] 1.05 Gbit/s
DOI-N08152
Crossconnect Crossconnect Types
2-11
2.3 CROSSCONNECT TYPES
2.3.1 Higher Order Path
The U-Node BBM Main shelf has the following crossconnect types:
! 1-Way
LXC (Local Cross-Connect)
PPS (Path Protection Selector)
! 2-Way
2.3.1.1 1-Way
The following illustrations show examples of one-way crossconnect types:
Example 1: 1-Way Local Crossconnect (LXC)
Example 2: 1-Way Crossconnect Path Protection Switching (PPS)
A B
DOI-N08152
2-12
2.3.1.2 2-Way
The following illustrations show examples of two-way crossconnect types:
Example 1: 2-Way Local Crossconnect (LXC)
Example 2: 2-Way Crossconnect Path Protection Switching (PPS)
2.3.2 Lower Order Path
The U-Node BBM EXTWB shelf has the following crossconnect types:
! 1-Way
Add
Drop
Loopback
PPS (path Protection Selector)
! 2-Way
Add-Drop
Loopback
A B
A B
DOI-N08152
2-13
2.3.2.1 1-Way
The following illustrations show examples of one-way crossconnect types:
HOSW: Higher order switch
LOSW: Lower order switch
Crossconnect Type Without PPS With PPS
Add

Drop

LXC

Loopback

Main EXTWB
LOSW
HOSW
STM-N
PDH
Main EXTWB
LOSW
HOSW
STM-N
PDH
Main EXTWB
LOSW
HOSW
STM-N
PDH
Main EXTWB
LOSW
HOSW
STM-N
Main EXTWB
LOSW
HOSW
STM-N
Main EXTWB
LOSW
HOSW
PDH
DOI-N08152
2-14
2.3.2.2 2-Way
The following illustrations show examples of two-way crossconnect types:
HOSW: Higher order switch
LOSW: Lower order switch
Crossconnect Type Without PPS With PPS
Add-Drop

LXC

Loopback

Main EXTWB
LOSW
HOSW
STM-N
PDH
Main EXTWB
LOSW
HOSW
STM-N
PDH
Main EXTWB
LOSW
HOSW
STM-N
Main EXTWB
LOSW
HOSW
STM-N
Main EXTWB
LOSW
HOSW
PDH
DOI-N08152
2-15
2.3.3 Supplementary Explanation
! For the Higher Order Crossconnect, multiple crossconnect settings that share the same
start crossconnect point can be specified. The illustration below (at left) shows an
example of the path when interlocking is performed. This path can be set by performing
two steps, as shown in the illustration below (" to #).
! To set the following Broadcast crossconnect type, multiple crossconnect settings must be
done.
1-Way Crossconnect - Broadcast
! The path shown below can be achieved by performing multiple 1-Way PPS settings:
1-Way Crossconnect PPS Broadcast
! In a Ring interface, a connection to the same ring can be set only as Through, which has
no protection configuration.
" #
1-Way (LXC) 1-Way (PPS)
= +
A
B
C
A B
A B
C
A
B
A B
C
A
= +
D E
C
D E
A B
C D
= +
A
B
D
C
B
D
DOI-N08152
2-16
2.3.4 Idle Signal Processing
When the path has not been connected, the idle signal interlocking with a facility per line can
be specified as follows:
! For SDH Interface
! For SONET Interface
! For JAPAN Interface
An idle signal for each crossconnect that matches the registered Band Level for the
crossconnect point is output.
Until you register each line facility and put it into the In-Service state, the signal is not
output.
DOI-N08152
Crossconnect Time Slot Management
2-17
2.4 TIME SLOT MANAGEMENT
! PSW capacity in U-Node BBM is numbered as 1 CH per 50M unit.
! The number is assigned to the slot in which the interface package is mounted.
Main Shelf supports 20G (384 CH) capacity. If PSW40 package is mounted, Extension Shelf
supports 20G (384 CH) capacity. If PSW80 package is mounted, Extension Shelf supports
60G (1152 CH) capacity.
2.4.1 Assignments for Main Shelf Front
The following tables show the relationship between the slot position on the shelf and the time
slot number (VC#).
CHANNEL ASSIGNMENTS MAIN PSW
TIME SLOT #
PORT SLOT TS #
1 1 1 1
48 48
2 1 49
48 96
3 1 97
48 144
4 1 145
48 192
5 1 193
48 240
6 1 241
48 288
7 1 289
48 336
8 1 337
48 384
STM-0 STM-1 STM-4 STM-16
1 LINE-1 LINE-1 VC #1 LINE-1 VC #1 LINE-1 VC #1
2 (blank) VC #2 VC #2 VC #2
4 LINE-2 LINE-2 VC #1 VC #4 VC #4
10 LINE-4 LINE-4 VC #1 VC #10 VC #10
11 (blank) VC #2 VC #11 VC #11
12 (blank) VC #3 VC #12 VC #12
13 LINE-5 LINE-5 VC #1 LINE-2 VC #1 VC #13

24 LINE-8 LINE-8 VC #3 VC #12 VC #24

50 (blank) VC #2 VC #2 VC #2
51 (blank) VC #3 VC #3 VC #3
53 (blank) VC #2 VC #5 VC #5
54 (blank) VC #3 VC #6 VC #6
56 (blank) VC #2 VC #8 VC #8
57 (blank) VC #3 VC #9 VC #9
58 LINE-4 LINE-4 VC #1 VC #10 VC #10
59 (blank) VC #2 VC #11 VC #11
60 (blank) VC #3 VC #12 VC #12

72 LINE-8 VC #3 VC #12 VC #24

96 LINE-16 VC #3 LINE-4 VC #12 VC #48


384 LINE-16 VC #3 LINE-4 VC #12 LINE-4 VC #48
DOI-N08152
Crossconnect Time Slot Management
2-18

CHANNEL ASSIGNMENTS
SHELF PORT TS #
EXTENSION
SHELF
1 1 385
48
49
96
97
144
145
192 576
2 1 577
48
49
96
97
144
145
192 768
STM-0 STM-1 [OC-3] STM-4 [OC-12] STM-16 [OC-48] STM-64 [OC-192]
1 LINE-1 LINE-1 VC #1 LINE-1 VC #1 LINE-1 VC #1 LINE-1 VC #1
2 (blank) VC #2 VC #2 VC #2 VC #2
3 (blank) VC #3 VC #3 VC #3 VC #3
4 LINE-2 LINE-2 VC #1 VC #4 VC #4 VC #4
5 (blank) VC #2 VC #5 VC #5 VC #5
6 (blank) VC #3 VC #6 VC #6 VC #6
8 (blank) VC #2 VC #8 VC #8 VC #8
9 (blank) VC #3 VC #9 VC #9 VC #9
11 (blank) VC #2 VC #11 VC #11 VC #11
12 (blank) VC #3 VC #12 VC #12 VC #12
13 LINE-5 LINE-5 VC #1 LINE-2 VC #1 VC #13 VC #13

24 LINE-8 VC #3 VC #12 VC #24 VC #24

48 LINE-16 VC #3 LINE-4 VC #12 VC #48 VC #48
49 LINE-1 LINE-1 VC #1 LINE-1 VC #1 LINE-1 VC #1 VC #49
50 (blank) VC #2 VC #2 VC #2 VC #50
51 (blank) VC #3 VC #3 VC #3 VC #51
53 (blank) VC #2 VC #5 VC #5 VC #53
54 (blank) VC #3 VC #6 VC #6 VC #54
56 (blank) VC #2 VC #8 VC #8 VC #56
57 (blank) VC #3 VC #9 VC #9 VC #57
59 (blank) VC #2 VC #11 VC #11 VC #59
60 (blank) VC #3 VC #12 VC #12 VC #60
61 LINE-5 LINE-5 VC #1 LINE-2 VC #1 VC #13 VC #61

72 LINE-8 VC #3 VC #12 VC #24 VC #72

96 LINE-16 VC #3 LINE-4 VC #12 VC #48 VC #96

192 LINE-16 VC #3 LINE-4 VC #12 LINE-4 VC #48 VC #192
DOI-N08152
Crossconnect Virtual Concatenation
2-19
2.5 VIRTUAL CONCATENATION
2.5.1 Overview
Virtual concatenation allows better use of bandwidth by taking multiple channels as one
channel when transporting data. For example, if accommodating a Gigabit Ethernet signal
with 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 for
other links (96% efficiency).
Each GBEM package supports up to four channels, which is available for up to 2.5G
bandwidth (VC-3-48v or VC-4-16v).
U-Node BBM supports this virtual concatenation only for Gigabit Ethernet signals.
NOTE: U-Node BBM provides GBEM package with two ports (for two channels) and with four
ports (for four channels).
2.5.2 Crossconnect Levels
U-Node BBM supports the following as the minimum unit of crossconnection level:
! GBE Package
VC-4 (unit: 50M)
! GBEM Package
VC-3 (unit: 50M, for SONET use only)
VC-4 (unit: 150M)
VC-4-4c (unit: 600M)
VC-4-16c (unit: 2.5G)
DOI-N08152
2-20
2.5.3 Crossconnect
2.5.3.1 GBE Package
Its virtual concatenation level that can take in GBE interface is:
VC-4-Xv (X = 1 thru 7)
The VC-4-7v can carry the full wire rate of GBE interface.
2.5.3.2 GBEM Package
For the virtual concatenation, in order to make selection available from bandwidth of 50M to
2.5G, virtual concatenation termination point (VCT) must be registered.
Available VC (AU) path(s) within GBEM package can be registered for a VCT. Up to four
VCTs can be registered. Registering necessary VCs (AUs) for VCT specifies its virtual
concatenation.
2.5.3.3 Crossconnection Images
! GBE Package
LINE
#1
LINE
#2
LINE
#3
LINE
#4
VCT
#1
VCT
#2
VCT
#3
VCT
#4
AU #1
AU #2
AU #3
AU #16
LINE
#1
LINE
#2
LINE
#3
LINE
#4
VCT
#1
VCT
#2
VCT
#3
VCT
#4
AU #1
AU #2
AU #3
AU #16
GBEM GBEM
SDH [SONET]
NETWORK
LINE
#1
LINE
#2
GBE PSW
SINF
SINF
DOI-N08152
2-21
! GBEM Package
Crossconnection can be be arranged in the same way shown for GEBM package. Also, as
shown 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
LINE
#3
LINE
#4
VCT
#1
VCT
#2
VCT
#3
VCT
#4
SINF
SINF
W
P
W: WORK
P: PROTECTION
LINE
#1
LINE
#2
LINE
#3
LINE
#4
VCT
#1
VCT
#2
VCT
#3
VCT
#4
SINF
SINF
W
P
W: WORK
P: PROTECTION
W
P
DOI-N08152
Crossconnect
2-22
E
DOI-N08152
Protection
3-1
3. PROTECTION
This section describes the protection function performed by U-Node BBM. The following
table shows the protection types available in U-Node BBM.
The following illustration shows the front view of the Main and EXT16 shelves and an
example of the protection setting for each interface package:

Type of
Protection
Object Method Note
Package PSW40/80 Package 1+1
ESW Package
PSW5WB/10WB Package
STM1E Package None/1+1
DS3 Package None/1+1
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
(SDH/SONET/JAPAN)

Transmission Line
(Ring Network)
MS-SPRing [BLSR]
(4 Fiber/2 Fiber)

Path VC/STS Path SNC/P
(including UPSR)
Set up separate from lines.
OH RS Overhead [Section Overhead]
MS Overhead [Line Overhead]

Interlocking with Linear Protec-
tion, Ring Protection.
M
S
C
S
S
C
O
H
C
I
N
F

(
1
)
I
N
F

(
2
)
I
N
F

(
3
)
I
N
F

(
4
)
P
S
W

(
W
)
P
S
W

(
P
)
I
N
F

(
5
)
I
N
F

(
6
)
I
N
F

(
7
)
I
N
F

(
8
)
Linear / 2F Ring / INF PKG Protection
4F Ring Protection
PSW PKG Protection
DOI-N08152
Protection
3-2
The following illustration shows the front view of the EXT64 shelf and an example of the
protection setting for each INF package.

The following illustration shows the front view of the EXTWB shelf and an example of the
1:1 protection setting for each INF (E31/E32) package.
NOTE: To configure E31/E32 protection, E3 TRM or E32 TRM package must be installed.
C
O
M
I
N
F

(
1
)
I
N
F

(
2
)
I
N
F

(
3
)
I
N
F

(
4
)
4F Ring
2F Ring
1:1 PKG Protection
PSWWB PKG Protection

S
C
W
B
S
S
C
W
B
I
N
F

(
P
)
I
N
F
I
N
F
I
N
F
I
N
F
P
S
W
W
B

(
W
)
P
S
W
W
B

(
P
)
I
N
F
I
N
F
I
N
F
I
N
F
Slot # 1 2 7 8 9 10 11 12 13 14 15 16 17
DOI-N08152
Protection
3-3
1:N PKG Protection configuration consists of N (INF) working slots #8 thru #11 and #14
thru #7) and one (INF) protection slot #7. The protection configuration also requires E1
TRM package(s). The following illustration shows the slots used for each 1:N PKG
protection configuration (N = 1 to 8).
NOTE: Shaded bars indicate the slots in which E12 packages must be mounted for each 1:N
package protection configuration.
P W1 W4 W2 W3 W8 W5 W7 W6

I
N
F

(
P
)
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
Slot # 7 8 9 10 11 14 15 16 17
1:1
1:2
1:3
1:4
1:5
1:6
1:7
1:8
P
P
P
P
P
P
P
P
W4
W2
W3 W8
W5
W7 W6
W1
W1
W1
W1
W1
W1
W1
W1
W2
W2
W2
W2
W2
W2
W3
W3
W3
W3
W3
W4
W4
W4
W4
W5
W5
W5
W6
W6
W7
DOI-N08152
Protection Package Protection
3-4
3.1 PACKAGE PROTECTION
This subsection describes package protection.
3.1.1 Switching Configuration
1+1 Package Protection Nonrevertive configuration applies to the PSW40, PSW80, ESW,
PSW5WB and PSW10WB packages, and to interface packages (DS3, STM1E). 1:N
Package Protection configuration applies to the E12, E31 and E32 packages (N = 1 for E31
and E32, N = 1 to 8 for E12). STM1E, DS3, E12, E31 and E32 packages can also be used in
an unprotected configuration.
3.1.2 Switching Mode
There are two types of switching modes: the manual switch operated by the user, and the
automatic switch carried out by package alarm detection. The types of manual switch
operated by the user are shown below:
Forced Switch (FSW): switching is operational regardless
NOTE
of failure status.
Manual Switch (MSW): switching is operational in Normal status.
Switching priority of PSW40 and PSW80 packages:
FSW > Automatic Switch > MSW
NOTE: The switching operations of the ESW packages (EXT16 shelf), and PSW5WB/10WB
packages (EXTWB shelf), are carried out in conjunction with PSW40/80 packages on
the Main shelf. When a failure has occurred in the ESW/PSW5WB/10WB package or
the ESW/PSW5WB/10WB package is removed, the PSW40/80 packages on the Main
shelf takes place switching operation, which is followed by ESW/PSW5WB/PSW10WB
packages.
Switching priority of STM1E, DS3, E12, E31 and E32 packages:
Automatic Switch (P)
NOTE
> FSW > Automatic Switch (W)
NOTE
> MSW
NOTE: For STM1E/DS3 package, if an Automatic Switch has been carried out by a failure at
its protection (P) side, the Forced Switch operation is disabled. For E12/E31/E32
package, however, FSW and MSW that switch from the protection side (P) to the
working side (W) are not provided.
DOI-N08152
Protection Package Protection
3-5
3.1.3 Lockout Mode
The Lockout mode holds the switching status (no switch operation is available) regardless of
the current switching status; this mode can be set by the user. The Lockout mode, however,
is not available to execute for ESW, PSW5WB and PSW10WB packages directly. As in the
switching operation, these packages will be in the lockout mode when the PSW40/80
packages in the Main shelf is set into the lockout mode.
3.1.4 Switching Status
The switching status and the online package can be confirmed via the CID. The ONLINE
LED (green) on front of a package lights up when the package is in the online mode, and
goes out when the package is in the offline mode. The maintenance LEDs (yellow) on the
rack top and MSC package light up when the switching command (Lockout, Forced Switch,
or Manual Switch) is successfully completed by the user.
DOI-N08152
Protection Line Protection
3-6
3.2 LINE PROTECTION
This subsection describes optical line facility protection.
3.2.1 Switching Configuration
You must specify interface packages that configure line protection. There are two protection
methods as shown below:
Two INF PKGs Protection: 2F MS-SPRing, 1+1 Linear, 1:1 Linear
Four INF PKGs Protection: 4F MS-SPRing
To configure the protection (Linear, 2F MS-SPRing [2F-BLSR]) by using two packages, the
following packages must be paired:
INF 1 and 2
INF 3 and 4
INF 5 and 6
INF 7 and 8
To configure the protection (4F MS-SPRing [4F-BLSR]) by using four packages, the
following packages must be paired:
INF 1, 2, 3, and 4
INF 5, 6, 7, and 8
3.2.2 Applicable Interface Package
$: Supported.
: Not Supported.
* Optical stick is mounted on SINFM package.
50M* 150M * 600M* 2.4G 10G
Linear
$ $ $ $ $
2F-Ring [BLSR]
$ $
4F-Ring [BLSR]
$ $
DOI-N08152
3-7
3.2.3 Linear Protection
The following illustration shows the protection setup in multi-line interface packages (SINFM
PKG) (150 M 16):
3.2.3.1 Linear Protection Mode
In the linear protection mode, the following switch type and APS mode are selectable per
line:
! Switch Type
1+1 Unidirectional, Nonrevertive
1+1 Bidirectional, Nonrevertive
1:1 Bidirectional, Revertive
! APS Mode
ITU-T
SONET
JAPAN
Main Shelf
I
N
F

(
1
)
I
N
F

(
2
)
I
N
F

(
3
)
I
N
F

(
4
)
I
N
F

(
5
)
I
N
F

(
6
)
I
N
F

(
7
)
I
N
F

(
8
)
Line 16
Line 1
Protection Type
Setting Unit
Protection Line
Work Line
SWGrp
DOI-N08152
3-8
! 1+1 Unidirectional Linear Protection
The following illustration shows 1+1 Unidirectional Linear Protection Operation:
NOTE: You cannot set a path to the protection side.
! 1+1 Bidirectional Linear Protection
The following illustration shows 1+1 Bidirectional Linear Protection Operation:
NOTE: You cannot set a path to the protection side.
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
ONLINE
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
ONLINE
DOI-N08152
3-9
! 1:1 Bidirectional Linear Protection
The following illustration shows 1:1 Bidirectional Linear Protection Operation:
NOTE: You can set a path to the protection line in normal operation (SLA Mode).
3.2.3.2 Switching Mode
There are two types of switching modes: the command switch operated by the user, and the
automatic switch carried out by line failure detection. The following table shows switching
commands:
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.
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
Optical
Interface
Optical
Interface
WORKING LINE
PROTECTION LINE
ONLINE
DOI-N08152
3-10
Switching priority is:
LKOP > FSW > Automatic Switch > MSW
The Lockout mode holds the switching status, and stops the transition regardless of the
current 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): the delay time until switching from the working
side to protection side after a failure is detected.
! WTR (Wait-to-Restore): the delay time until switching back to the default side
after a failure is cleared.
! WRT (Wait-to-Response Time): the delay time until receiving the expected
K Byte after sending a K Byte request.
! FFCT (Fault-Free Confirmation Time): the delay time for confirmation of a
cleared alarm. ON or OFF can be set.
3.2.3.3 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 package is in the
online mode, and goes out when the package is in the offline mode. The maintenance LED
(yellow) on the rack top and MSC package light up when the switching command (LKOP,
Forced Switch, or Manual Switch) is successfully completed by the user.
3.2.3.4 Maintenance
Performance monitoring (PM) function detects switching operation and switching time.
Also, this function is used to notify switching failures to users. The lit/unlit status of the
ONLINE LED on an interface package and the maintenance LEDs on the rack top and MSC
package is interlocked with Protection operation. There is Squelch control for SLA path
when 1:1 protection is configured.
DOI-N08152
3-11
3.2.4 Ring Protection
Ring protection is supported by only 10G or 2.4G Interface. 600M and smaller interfaces do
not support ring protection. This function applies to the Open Ring Network as well. The
following illustration shows the ring protection group for the Main shelf:

! 4F MS-SPRing [BLSR] Protection:
Line 1 Working: Slot 4
Line 1 Protection: Slot 6
OR
Line 1: Slot 4
Line 2: Slot 5
OR
Line 1: Slot 6
Line 2: Slot 7
OR
Line 1: Slot 10
Line 2: Slot 11
OR
Line 1: Slot 12
Line 2: Slot 13
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
S
I
N
F
1
6
Slot# 4 5 6 7 10 11 12 13
DOI-N08152
3-12
The following illustration shows the ring protection group for the EXT64 shelf:

Line 1 Work: Slot 2
Line 2 Work: Slot 3
Line 1: Slot 2
Line 2: Slot 3
OR
Line 1: Slot 4
Line 2: Slot 5
S
I
N
F
6
4
S
I
N
F
6
4
S
I
N
F
6
4
S
I
N
F
6
4
Slot# 2 3 4 5
DOI-N08152
3-13
3.2.4.1 Ring Protection Mode
2F MS-SPRing and 4F MS-SPRing are configured according to the number of interfaces.
U-Node BBM supports an In-service Upgrade function from 2F MS-SPRing to 4F MS-
SPRing. The following illustration shows an example of 4F MS-SPRing mode operation:
Ring Switching
Span Switching
Bridge
Switching
Bridge
Switching
W
W
W
W
W
W
W
W
P P
P
P
P
P
P
P
DOI-N08152
3-14
3.2.4.2 Switching Mode
There are two types of switching modes: command switch by user operation, and automatic
switch by detection of line failure. The following table shows switching commands:
LKOW > LKOP > FSW > Automatic Switch > MSW
You can modify the following parameters to the switching operation:
! RGT (Request-to-Guard Time): the delay time (defined as Hold Time) until
switching from working side to protection side after a failure is detected.
! WRT (Wait-to-Response Time): the delay time until receiving expected K Byte
after sending K Byte request.
! WTR (Wait-to-Restore Time): the delay time to wait for recovery. There are two
types of WTR time; WTR for Span switching and WTR for Ring switching.
! FFCT (Fault-Free Confirmation Time): the delay time for switching operation.
Switching will not be done immediately after clearing a failure by setting this time.
Command Definition
Lockout 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 2 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.
DOI-N08152
3-15
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 package is in the
online mode, and goes out when the package is in the offline mode. The maintenance LED
(yellow) on the rack top and MSC package lights up when the switching command (LKOW,
LKOP, Forced Switch, or Manual Switch) is successfully completed by the user.
3.2.4.4 Maintenance
The performance monitoring (PM) detects switching operation and switching switching time.
Also, this function is used to notify users of switching failures. The lit/unlit status of
ONLINE LED on an interface package and maintenance LED on NE and MSC package is
interlocked with the Protection operation (LED lights up). There is Squelch control for path
to prevent misconnection of Ring switching.
DOI-N08152
Protection Path Protection
3-16
3.3 PATH PROTECTION
U-Node BBM supports the Sub-Network Protection (SNC/P) function for higher-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 Method
According to the switching status of the object, the SNC/P monitoring method is classified
into the following:
SNC/I: Sub-Network Connection Protection with Inherent Monitoring
SNC/N: Sub-Network Connection Protection with Non-intrusive Monitoring
3.3.1 Switching Mode
There are two types of switching modes: command switch by user operation, and automatic
switch by detection of path failure. The following table shows switching commands:
LKOP > FSW > Automatic Switch > MSW
You can modify the following parameters for switching operation:
! Hold-Off Time: the delay time until starting to switch from working side to
protection side after a failure is detected.
! WTR (Wait-to-Restore Time): the delay time to wait for the recovery.
! Threshold Value
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.
DOI-N08152
Protection Path Protection
3-17
The switching status and online path can be confirmed via the CID.
The maintenance LED lights up when the switching command (LKOP, Forced Switch, or
Manual Switch) is successfully completed by the user.
3.3.1.2 Maintenance
The PM function is used to notify users of switching failures. The lit/unlit status of the
maintenance LED on NE and MSC package is interlocked with the Protection operation.
DOI-N08152
Protection Interlocking Ring Protection
3-18
3.4 INTERLOCKING RING PROTECTION
The U-Node BBM supports an interlocking ring protection that allows traffic from one ring
to be interconnected with traffic from another ring. This protection takes place by using path
protection and ring protection. This connection is made at two nodes, the primary and
secondary nodes, in each ring. The two rings are interconnected in two places to provide an
alternate traffic path in case of primary node failure. Service selectors (the crossconnect
switching in the PSW40/80 or PSW5WB/10WB) in the primary and secondary nodes allow
selection between incoming aggregate and tributary signals.
The primary source sends the signal to the primary destination; should the signal fail, either
because the line is cut or because one of the primary nodes suffers a failure, the signal is
rerouted through the secondary nodes.
At least three nodes must be available for interlocking rings. All U-Node BBM nodes are
capable of performing primary node and secondary node functions.
The following illustration shows an example of interlocking ring protection:
Path Protection
Crossconnect
MS-SPRing
[BLSR]
MS-SPRing
[BLSR]
Path Bridge
Crossconnect
(Service Selector)
(Service Selector)
DOI-N08152
Protection Overhead (OH) Protection
3-19
3.5 OVERHEAD (OH) PROTECTION
OH Protection is used to select the overhead sent from an external NE. This function is
interlocked with the facilitys on-line status (protection status).
3.5.1 Objects for OH Protection
The following are supported:
! RSOH (Regenerator Section Overhead)
! MSOH (Multiplex Section Overhead)
! Non-OH Protection
3.5.2 Types of OH Protection
OH protection is interlocked with the following line protection:
! Linear Line Protection
! 4F MS-SPRing
NOTE: 4F MS-SPRing is available only when Span switching is executed; Ring switching will
be supported in the future.
DOI-N08152
Protection
3-20
E
DOI-N08152
Synchronization Synchronization
4-1
4. SYNCHRONIZATION
This section describes the synchronization function as applicable to U-Node BBM.
4.1 SYNCHRONIZATION
4.1.1 Clock Interface
4.1.1.1 External Timing Incoming
U-Node BBM supports the following external timing (incoming) interfaces. Two systems of
external timing (incoming) go into a PSW package on the Main shelf. The incoming
interface type follows the registered/mounted package.
DS1 SF/ESF Without Traffic
2,048 kbit/s Without Traffic (120 /75 )
2,048 kHz (120 /75 )
64K Composite Clock
Option: choices of SF/ESF for DS1 signal, with/without CRC for 2,048 kbit/s.
4.1.1.2 External Timing Outgoing
U-Node BBM supports the following external timing (outgoing) interfaces. Two systems of
external timing (outgoing) go out of a PSW package on the Main shelf. The outgoing
interface type follows the registered/mounted package.
DS1 SF/ESF Without Traffic
2,048 kbit/s Without Traffic (120 /75 )
2,048 kHz (120 /75 )
64K Composite Clock and 6.3 MHz Clock
Option: choices of SF/ESF for DS1 signal, with/without CRC for 2,048 kbit/s.
DOI-N08152
4-2
4.1.1.3 SDH [SONET] Line Timing
Line timing can be entered one-by-one as the timing source from the slots of each interface
package on the Main shelf and EXT64 shelf.
4.1.1.4 2M Line Timing
When an EXTWB shelf with E12 interface packages is mounted and 2M PDH signal (with
traffic) interface is enabled, any two lines of incoming 2M traffic signals can be output as
external clock outgoing signals. The U-Node BBM can use these 2M traffic signals for its
equipment timing source (2M Line Timing). To enable the 2M Line Timing, connect the
external clock output port of the EXTWB shelf and the external clock input port of the Main
shelf, and then select external clock incoming signals of the Main shelf as the timing source.
The following two types of external timing interfaces are available for the EXTWB shelf :
2,048 kbit/s (120 /75 )
2,048 kHz (120 /75 )
Be aware that the same external timing interface type must be selected and used for the
PSW5WB/10WB on the EXTWB shelf and the PSW40/80 on the Main shelf. This interface
is not available, however, when a 0H00 group package (PSW5WB: UB561-0H00,
PSW10WB: UB562-0H00) is used.
DOI-N08152
4-3
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 [SONET] 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 timing
source 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:
FORCED
FREE-RUN
MODE
FORCED
HOLDOVER
MODE
FREE-RUN
MODE
FORCED FREE-RUN
FORCED
FREE-RUN
AUTO SELECTION
OPERATION
FORCED
HOLDOVER
AUTO SELECTION OPERATION
HOLDOVER
MODE
ACQUIRING
HOLDOVER HOLDOVER
MEMORY
VALID
TIMING SOURCE
AVAILABLE
NO VALID
TIMING SOURCE
AVAILABLE
VALID
TIMING SOURCE
AVAILABLE
TIMING SOURCE
NO VALID
AVAILABLE
TIMING SOURCE
MEMORY
ACQUIRED
NORMAL MODE
HOLDOVER
ACQUISITION TIME
(H/W AUTO SELECTION)
AUTO SELECTION
OPERATION
PROVISIONING
POWER ON
(HOT/COLD)
DOI-N08152
4-4
4.1.3 Clock Features
The following clock features apply to ITU-T Standards and Telcordia (Bellcore) 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
DOI-N08152
Synchronization Timing Source Control
4-5
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-T
Standards and Telcordia (Bellcore) Standards. 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 can
specify 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
DOI-N08152
Synchronization Timing Source Control
4-6
4.2.3 SSM Control
SSM (Synchronization Status Message) contains information for NEs to identify the quality
of Timing Reference. Enabling SSMUSE Function selects the best quality of timing
reference each time, instead of accepting one specified quality level. The following
interfaces support SSM as timing source control:
! Line Facility Signal
You can select whether or not to support SSM on all SDH [SONET] Line signals.
! DS1 External Clock Signal
You can select whether or not to send/receive SSM to DS1 ESF Format External Clock
signal.
! 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 CRC
Multiframe Format signal.
DOI-N08152
Synchronization Timing Source Selection
4-7
4.3 TIMING SOURCE SELECTION
The equipment timing source and external output timing source are available for timing
source selection. There are two systems of external output timing sources; they are selected
and controlled individually.
4.3.1 External Output Timing Source Switching Modes
External Output timing source includes the following modes:
! Fixed Timing Mode
The timing source of a line set by the user is output as the external output timing source.
! Auto Switching Timing Mode
One of the specified timing sources is switched automatically within NE and is output as
external 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 Mode
In this mode, SSM value that is the origin of synchronization of external output timing
source is always monitored. SSM value is converted to SSM for External Output and is
output. This mode is supported only when 2,048 kbit/s with CRC or DS1 ESF interface is
used.
! Threshold AIS Generation Mode
QL value of output timing source is always monitored. QL value is compared with the QL
value 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 [SONET] line signal or external incoming clock, the timing source
becomes QL-FAILED when a timing source failure is evaluated as having occurred.
DOI-N08152
Synchronization Timing Source Selection
4-8
4.3.4 Hold-off Time
A momentary failure that occurs within the specified period (Hold-off Time) is not counted
as 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 a
specified period (SSM Hold-off Time), the timing reference is selected. Among the
commeasurable timing sources, specifying the SSM Hold-off Time to one with the highest
priority level can avoid unavailing switching that causes wander variations. If a failure
occurs to the timing source, or if an invalid SSM or DNU (Do Not Use) is received, this
holding-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, in
order 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 output
timing source can be selected depending on the command. The following commands are
available:
! Lockout
If this command is specified to a timing source, that timing source will be excluded from
timing source selection.
! Forced Switch
Switching is forcibly carried out to the timing source selected by this command, regardless
of quality level of the target timing source, except when Lockout is specified.
! Manual Switch
Switching is carried out when a timing source selected by the command has equivalent to
or higher level than that of currently selected timing source, where a signal failure does not
exist.
! Clear
This command is used to clear the switching command.
DOI-N08152
Synchronization Precautions
4-9
4.4 PRECAUTIONS
An improper configuration of timing synchronization causes timing loop. See the following
example:
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 and
outgoing are set to the same value, QL_1 (PRS/PRC; G.811). The quality level for the
outgoing from NODE 2 to NODE 1 is set to QL_1 (PRS/PRC; G.811) where the DNU
Restoration Time is set to OFF:
NODE 1
QL_1
IN
NODE 2
OUT
QL_1
OUT
IN
NODE 3
QL_1
QL_6
BITS/SSU
QL_1
QL_1
NODE 1
IN
NODE 2
OUT
QL_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)
DOI-N08152
Synchronization
4-10
E
DOI-N08152
Configuration Management Configuration Management Object
5-1
5. CONFIGURATION MANAGEMENT
This section describes inter-NE management and control methods to manage/control NE.
5.1 CONFIGURATION MANAGEMENT OBJECT
U-Node BBM has items to define and control NE operation; the items are called
Management Objects. The following table shows the Management Objects for U-Node
BBM.
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-MSC (See 5.1.3)
CPU CPU (See 5.1.4)
Facility SINF64F STM64 [OC192] Interface (See 5.1.5)
SINF16F STM16 [OC48] Interface (See 5.1.5)
SINFMF STM4 [OC12], STM1 [OC3], STM0 Interface (See 5.1.5)
DS3F DS3 (electrical) Interface (See 5.1.5)
E12F 2M (electrical) Interface (See 5.1.5)
STM1EF STM1e (electrical) Interface (See 5.1.5)
GBEF G-Bit Ethernet Interface (See 5.1.5)
GBEMF G-Bit Ethernet Interface; multiple packet (See 5.1.5)
AU3/AU4 Section Adaptation (See 5.1.5)
HPMON3/HPMON4 Higher Order Path Monitor (See 5.1.5)
LPMON Lower Order Path Monitor (See 5.1.5)
HPT HIgher Order Path Termination (See 5.1.5)
HPT3 DS3 Higher-order Path Termination (See 5.1.5)
HPTE4 GBE Higher-order Path Termination (See 5.1.5)
HPTM3 GBEM Higher-order Path Termination (See 5.1.5)
LPT Lower Order Path Termination (See 5.1.5)
SDHTU TU Termination Point on Main Shelf Side (See 5.1.5)
PDHTU TU Termination Point on PDH Interface Package Side (See 5.1.5)
EXTCLK External Clock Interface (See 5.1.6)
DOI-N08152
5-2
(Configuration Management Object; continued)
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 BBM has four types of shelves. The
main function of each shelf is shown in the table below:
Classification Object Description
Switch Group PSWS GRP for Package Switching of PSW40/80 (ESW. PSW5WB/10WB; See 5.1.7)
DS3S GRP for Package Switching of DS3 (See 5.1.7)
INFNS GRP for Package Switching of E12 (See 5.1.7)
INFS GRP for Package Switching of E31/32 (See 5.1.7)
STM1ES GRP for Package Switching of STM1E (See 5.1.7)
LINES GRP for Linear Switching of SINFnF (n=M, 16, 64) (See 5.1.7)
MS2FS GRP for 2F MS-SPRing [BLSR] Switching of SINFnF
(n=M, 16, 64) (See 5.1.7)
MS4FS GRP for 4F MS-SPRing [BLSR] Switching of SINFnF
(n=M, 16, 64) (See 5.1.7)
Synchronization SYNCG Common GRP for Timing Source (See 5.1.8)
SYNCU Common Unit for Timing Source (See 5.1.8)
SYNCISG GRP for Timing Source Switching inter-NE (See 5.1.8)
SYNCISU Unit for Timing Source Switching inter-NE (See 5.1.8)
SYNCESG GRP for EXT OUT Timing Source Switching (See 5.1.8)
SYNCESU Unit for EXT OUT Timing Source Switching (See 5.1.8)
Overhead OHCH Overhead Access Channel (See 5.1.9)
RSDCC [SDCC] RS-DCC [S-DCC] (LAPD) Management Function (See 5.1.10)
MSDCC [LDCC] MS-DCC [L-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 (GEEM)
GFPCT Channel ID (GBEM)
Shelf Name Function Shelf ID
MAIN The Main shelf has management/control of NE and crossconnect functions. It
contains up to 2.5G SDH [SONET] Optical Interface, STM1E Interface, DS3
Interface, and G-Bit Ethernet Interface.
1 (Fixed)
EXT64 This shelf contains 10G SDH [SONET] Optical Interface. 2 (Fixed)
EXT16 This shelf contains up to 2.5G SDH [SONET] Optical Interface, STM1E Inter-
face, DS3 Interface, and Ethernet Interface.
3 to 5
EXTWB This shelf has a lower order crossconnect function. It contains PDH inter-
face, 2M, 34M and 45M interface.
6 to 9
DOI-N08152
5-3
5.1.3 Package (PKG)
This is the object that represents package components. The following table shows a list of
package objects.
Package Name Shelf Main Function
MSC MAIN NE Control Management
SC16 EXT16 Extension EXT16 Shelf Management
SCWB EXTWB Extension EXTWB Shelf Management
PSW40 MAIN 40G Crossconnect + Path Switching + Clock
PSW80 MAIN 80G Crossconnect + Path Switching + Clock
PSW5WB EXTWB 5G Lower Order Crossconnect + Path Switching + 2M Line Timing Out
PSW10WB EXTWB 10G Lower Order Crossconnect + Path Switching + 2M Line Timing Out
ESW EXT16 PSW Interface
OHC MAIN OH Management, LAPD Termination, HKA, HKC
OHCEXT EXT16 OH Management, LAPD Termination
SSC MAIN/EXT16 Protection Management
SSCWB EXTWB Protection Management for E12, E31 and E32
COM EXT64 OH Management/LAPD Termination + MAIN Interface
SINF64 EXT64 STM64 [OC192] Interface; colored/non-colored
SINF16 MAIN/EXT16 STM16 [OC48] Interface; colored/non-colored
SINFM with OP4
OP1
OP0
MAIN/EXT16 STM4 [OC12] Interface (1 to 4 lines)
and STM1 [OC3], STM0 Interface (1 to 16 lines)
By mounting OPn, each interface is available.
STM1E MAIN/EXT16 STM1 Electrical Interface (1 to 16 lines)
DS3 MAIN/EXT16 DS3 Electrical Interface (1 to 12 lines)
E12 EXTWB 2M Electrical Interface (1 to 63 lines)
GBE MAIN/EXT16 1G-bit Ethernet Interface
GBEM MAIN/EXT16 1G-bit Ethernet Interface (multiple packets)
MMEM MAIN (inter MSC) Holding backup data and F/W. Size: 16 MByte
MMEM2 MAIN (inter MSC) Holding backup data and F/W. Size: 32 MByte
EMEM EXT16 (inter SC16) Holding backup data and F/W
WBMEM EXTWB Holding backup data and F/W
DOI-N08152
5-4
5.1.3.1 SINFM PKG
Multiple lines (OPn) are equipped on one SINFM PKG. The optical stick component
(physical layer) can be inserted/extracted as shown below. See the Package Description/
Installation manual for details.
5.1.3.2 Slot Number
The following table defines the slot number of each shelf. The slot numbers below are
retrieved by the Inventory as AIDs to indicate the locations of slots. The mounting slot is
fixed for each package.
SINFM, SINF16, DS3, STM1E, GBE, and GBEM can be mounted on the INF # slots in the
illustration above.
MAIN/EXT16 Shelf
M
S
C
/
S
C
16
S
S
C
O
H
C
/
O
H
C
E
X
T
I
N
F
#1
I
N
F
#2
I
N
F
#3
I
N
F
#4
P
S
W
/
E
S
W
P
S
W
/
E
S
W
I
N
F
#5
I
N
F
#6
I
N
F
#7
I
N
F
#8
Slot# 1 2 3 4 5 6 7 8 9 10 11 12 13
Insertion/Extraction is
possible.
#16: OP1
#15: OP0
#14: OP1
#1: OP4
SINFM
DOI-N08152
5-5

Slot #7 (INF P) is used only for a protection package of E12 (2M interface).
EXT64 Shelf
C
O
M
S
I
N
F
64
#1
S
I
N
F
64
#2
S
I
N
F
64
#3
S
I
N
F
64
#4
Slot# 1 2 3 4 5

EXTWB Shelf
S
C
W
B
S
S
C
W
B
I
N
F
(P)
I
N
F
I
N
F
I
N
F
I
N
F
P
S
W
W
B
(W)
P
S
W
W
B
(P)
I
N
F
I
N
F
I
N
F
I
N
F
Slot# 1 2 7 8 9 10 11 12 13 14 15 16 17
DOI-N08152
5-6
5.1.4 CPU
This is the object representing a CPU which controls a package. The following table shows
object names of CPUs, and those of packages where CPUs are equipped.
PKG CPU Remark
MSC SCCPU
AGCPU
SC16 SC16CPU
SCWB SCWBCPU
PSW40 PW40CPU
PSW80 PW80CPU
PSW5WB PSWWBCPU
PSW10WB PSWWBCPU
ESW EWCPU
OHC OHCPU Three CPUs can be equipped on one PKG.
OHCEXT OHCPU Three CPUs can be equipped on one PKG.
SSC SWCPU
SSCWB SSCWBCPU
COM OHCPU Two CPUs can be equipped on one PKG.
SINF64 IF64CPU
SINF16 IFCPU
SINFM IFCPU
STM1E IFCPU
DS3 IFT3CPU
E12 E12CPU
E31 E31CPU
E32 E32CPU
GBE GECPU
GBEM GEMUCPU
DOI-N08152
5-7
5.1.5 Facility
This object controls each layer signal in the transmission line. The following table shows
facility names and functions.
5.1.6 External Clock (EXTCLK)
This object controls the external clock. PSW (PSW40 or PSW80) package has a clock
function and provides an external clock. PSWWB (PSW5WB or PSW10WB) package has
an external clock output function supporting 2M Line Timing. The following table shows
EXT CLK object names and PSW package types.
NOTE: The PSWWB package supports EXC2MH and EXC2MB only.
Facility Function Corresponding PKG
SINF64F STM64 [OC192] Interface SINF64
SINF16F STM16 [OC48] Interface SINF16
SINFMF STM4 [OC12], STM1 [OC3], STM0 Interface SINFM
DS3F DS3 (electrical) Interface DS3
GBEF G-bit Ethernet Interface GBE
GBEMF G-bit Ethernet Interface; multiple packets GBEM
E12F 2M (electrical) Interface E12
STM1EF STM1e (electrical) Interface STM1E
AU3 Section Adaptation SINF64/SINF16/SINFM/
STM1E/DS3/GBEM
AU4 Section Adaptation SINF64/SINF16/
SINFM/STM1E/GBE
HPMON3 Higher-order Path Monitor SINF64/SINF16/
SINFM/STM1E
HPMON4 Higher-order Path Monitor SINF64/SINF16/
SINFM/STM1E
LPMON Lower-order Path Monitor PSWWB
HPT Higher-order Path Termination PSWWB
HPT3 DS3 Higher-order Path Termination DS3
HPTE4 GBE Higher-order Path Termination GBE
HPTM3 GBEM High-order Path Termination GBEM
LPT Lower-order Path Termination PSWWB
SDHTU TU Termination Point on Main Shelf Side PSWWB
PDHTU TU Termination Point on PDH Interface PKG Side PSWWB
Object Name PSW PKG Type Clock Interface
EXC2MH 2 MHz 2 MHz Clock (75/120 )
EXC2MB 2 Mbit/s E1 (75/120 )
EXC64K 64 K Input 64 kHz + 8 kHz; Output 6.3 M
EXCDS1 DS1 DS1
DOI-N08152
5-8
5.1.7 Switch Group
This object manages Package Protection and Line Protection (Linear/MS-SPRing [BLSR]).
The following table shows SW Group names and functions.
NOTE: ESW, PSW5WB, and PSW10WB packages do not have switch groups to be assigned.
Switching performances for these packages are carried out in conjunction with that for
PSW40/80 packages. Thus, switch group PSWS represents that of these packages.
The following illustration shows an example of SW Group configuration.
SW GRP Name Function
PSWS
PSW40/80 (ESW, PSW5WB/10WB) Package Protection Control
NOTE
DS3S DS3 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 [BLSR] Protection Control (only for SINF16F and SINF64F facilities)
MS4FS 4-Fiber MS-SPRing [BLSR] Protection Control (only for SINF16F and SINF64F facilities)
(1) (2)
: Switch Group
SINF64/16 PKG 4F-Ring SINF16/64 PKG SINFM PKG
DOI-N08152
5-9

: Switch Group
E12 PKG
P W1 W4 W2 W3 W8 W5 W7 W6

I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
Slot # 8 9 10 11 14 15 16 17
W P W P W P W P
E31/32 PKG

I
N
F

(
P
)
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
I
N
F
Slot # 7 8 9 10 11 14 15 16 17
1:1
1:2
1:3
1:4
1:5
1:6
1:7
1:8
P
P
P
P
P
P
P
P
W4
W2
W3 W8
W5
W7 W6
W1
W1
W1
W1
W1
W1
W1
W1
W2
W2
W2
W2
W2
W2
W3
W3
W3
W3
W3
W4
W4
W4
W4
W5
W5
W5
W6
W6
W7
DOI-N08152
5-10
5.1.8 Synchronization
This is not a physical object; this is controlled logically by PSW packages.
! SYNCG
This object is used to control common components for Internal Timing Source Selection
Group (SYNCISG) and External Clock Timing Source Selection Group (SYNCESG).
! SYNCU
This object is used to control common components for Internal Timing Source Unit
(SYNCISU) and External Clock Timing Source Unit (SYNCESU). The PSWWB
package, especially, manages SYNCU objects to monitor 2M line clocks.
! 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 [SONET] Line facility
overhead to MSDCC [SDCC], RSDCC [LDCC], V.11 Interface, E1DB (Digital Branch), and
E2DB. OHC PKG, OHCEXT PKG, and COM PKG support OHCH.
5.1.10 Data Communication Channel (DCC)
DCC is the object used to manage LAPD for a management network with the data
communication channel.
NOTE: MSDCC can be selected for SINF64F and SINF16F facilities.
Data Communication Channel (DCC) Type
DCC Type Function Corresponding PKG
RSDCC [SDCC] RS-DCC [S-DCC] (LAPD) Management
OHC, OHCEXT, COM
MSDCC [LDCC] MS-DCC [L-DCC] (LAPD) Management
DOI-N08152
5-11
5.1.10.1 OHC/OHCEXT Package Type and DCC
NOTE: DCC number should be registered at the OHC/OHCEXT Package parameter settings.
5.1.10.2 COM Package Type and DCC
5.1.11 HKC/HKA
HKC is the object that represents intra-office Housekeeping Control function. HKA is the
object 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.
PKG Type DCC Number RSDCC/MSDCC CH Number
0Axx/AAxx 4CH RSDCC 4CH
0Bxx/ABxx 8CH RSDCC 8CH
0Cxx/ACxx 12CH RSDCC 8CH, MSDCC 4CH
PKG Type DCC Number RSDCC/MSDCC CH Number
0Bxx/ABxx 8CH RSDCC 4CH, MSDCC 4CH
DOI-N08152
Configuration Management Service State
5-12
5.2 SERVICE STATE
To manage equipment configuration, the status for providing service to each object described
above is defined as its Service State. There are the following functions: Notification of
service 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.
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 is
saved.
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 PKG
equipped 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).
DOI-N08152
Configuration Management Other Administration States
5-13
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, and
manages the Port Mode state.
Port Mode is set to manage Line Facility (main signal interface), PDH Interface Facility (for
E12, E31 and E32), and EXT CLK (External Clock Interface). There are two Port Modes:
! AUTO
The AUTO mode inhibits MON, in order to avoid reporting the detected LOS at the
initial power-up. Once the first detected LOS is cleared, the mode is automatically
changed to MON (normal mode). The AUTO mode will also be changed to MON by
removing/re-installing an interface package and/or optical stick.
! MON
In the MON mode, a detected alarm is always reported (normal mode). This mode is also
set by removing/re-installing an interface package and/or optical stick in the AUTO
mode.
5.3.2 Mode Mismatch
The package type settings are required to register the packages shown in the table below. If
the installed package and setting do not match, this function generates an alarm.
NOTE: The Mode Mismatches shown above are managed as alarm states.
PKG Mode Mismatch Definition
OHC/OHCEXT/
COM PKG
MODEMIS OHCMODE (PCM coding method) set by user and
the installed package group do not match.
OHC/OHCEXT
PKG
CHMIS CHMODE (DCC support channel number) set by
user and the installed package do not match.
PSW40/80 PKG MODEMIS PSWMODE (external clock support type) set by
user and the installed package group do not match.
STM1E PKG CHMIS CHMODE (STM1E facility number) set by user and
the installed package group do not match.
PSW5WB/
10WB PKG
MODEMIS PSWMODE (external clock support type) set by
user and the installed package group do not match.
E12 PKG MODEMIS PDHMODE (2M interface impedance) set by user
and the installed package group do not match.
DOI-N08152
Configuration Management Memory Backup
5-14
5.4 MEMORY BACKUP
5.4.1 Overview
U-Node BBM provides multi-memory backup of the MSC, SC16 and SCWB packages by
using a memory card (non-volatile memory). Restoration of data is possible in the following
cases: node failure, package replacement, and power failure. Memory card is mounted on
MSC, SC16 and SCWB packages; 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 BBM.
NOTE: Download/Upload function via the CID will be supported in the future.
front side
MSC/SC16/SCWB PACKAGE
MEMORY
CARD
ACT
Memory
ACT
Memory
ACT
RAM
Command
Periodic/
Command
Auto Backup
Storing 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 Start
Default Data (DEF)
Storing Area
DOI-N08152
Configuration Management Memory Backup
5-15
The following describes Memory Areas shown in the above illustration:
! Auto Backup Area on Memory Card (Auto Backup Storing Area)
U-Node BBM uses System Administrative information for ACT (RAM). The
information is backed up into the auto backup area of the memory card in real time.
Backup is classified into each SC unit (MSC/SC16/SCWB).
! Flash Memory on MSC, SC16 and SCWB PKG (Backup Storing Area)
ACT (RAM) information is periodically backed up onto the SUB side on the MSC, SC16
and SCWB packages. 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 on
the memory card. The use of this backup area can be defined by the user.
! Default Information
Default information is held in MSC, SC16 and SCWB package F/W program. The
settings of the factory default information cannot be modified.
DOI-N08152
Configuration Management Starting up NE
5-16
5.5 STARTING UP NE
5.5.1 Hot Start
In Hot Start mode, the U-Node BBM starts up according to previously set system
administration information. Starting up in the Hot Start mode does not change the NE status.
Hot Start can be carried out by pressing the RESET button on the MSC/SC16/SCWB
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
NOTE: When Hot Start is carried out for the MSC, SC16, or SCWB package, only the
corresponding shelf is restarted. Therefore, even if Hot Start is carried out for the MSC
package, no other shelves are restarted.
5.5.2 Cold Start
Cold Start is used when the equipment is powered up for the first time after installation with
no data in NE or when the maintenance personnel starts up NE with the default
administration information stored in default memory (DEF).
The following two methods may be used:
! Restart by issuing memory backup (the Restore command is issued to restore the default
information).
! Restart by pressing the COLD button on MSC/SCWB package to reset the package.
NOTE: When Cold Start is carried out for the MSC package, each memory on the Main, EXT16
and EXT64 shelves is reset to the default state, but the memory on the EXTWB shelf is
not. When carrying out Cold Start, therefore, it must be done for the Main shelf and all
the EXTWB shelves connected to the Main shelf.
DOI-N08152
Configuration Management Inventory
5-17
5.6 INVENTORY
5.6.1 Package Inventory
Each package and optical stick stores information to identify itself as shown below. The
information can be retrieved.
5.6.2 NE Information Inventory
Network elements have TID (Target Identifier: equipment identity) and NE Address
information 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 the
IP 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 (Inventory information)
CLEI Code Common Language Equipment Identifier.
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
DOI-N08152
Configuration Management Object AIDs
5-18
5.7 OBJECT AIDS
The following shows the syntax for each management objects AID (Access Identifier). The
U-Node BBM specifies these AIDs that are required to control/report objects to/from CID
and upper OS using TL1 interface.
NOTE: BAY is defined as a set of systems. For the U-Node BBM, 1 is applied to all its
objects.
5.7.1 Node
! AID Syntax: (object tag)
NOTE: Node objects are managed by the MSC and SCWB packages.
(AID)
NODE
DOI-N08152
5-19
5.7.2 Shelf
! AID Syntax: object tag bay shelf ID
OBJECT TAG BAY SHELF NOTES
Main Shelf
SHELF

1

1
EXT64 Shelf
SHELF

1

2
EXT16 Shelf
SHELF

1
n n (shelf ID) = 3 thru 5
EXTWB Shelf
SHELF

1
n n (shelf ID) = 6 thru 9
DOI-N08152
5-20
5.7.3 Package
! AID Syntax: object tag bay shelf ID slot#
PACKAGE TAG BAY SHELF SLOT NOTES
MSC
MSC

1

1

1
SC16
SC16

1
n
1
n (shelf ID) = 3, 4 or 5
SCWB
SCWB

1
n
1
n (shelf ID) = 6 thru 9
SSC
SSC

1
n
2
n (shelf ID) = 1, 3, 4 or 5
SSCWB
SSCWB

1
n
2
OHC
OHC

1

1

3
OHCEXT
OHCEXT

1
n
3
COM
COM

1

2

1
SINF64
SINF64

1

2
m m (slot#) = 2, 3, 4 or 5
SINF16
SINF16

1
n m n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 4 thru 7, 10 thru 13
SINFM
SINFM

1
n m n (shelf ID) = 1, 3, 4 or 5
STM1E
STM1E

1
n m n (shelf ID) = 1, 3, 4 or 5
DS3
DS3

1
n m n (shelf ID) = 1, 3, 4 or 5
GBE
GBE

1
n m n (shelf ID) = 1, 3, 4 or 5
GBEM
GBEM

1
n m n (shelf ID) = 1, 3, 4 or 5
E12
E12

1
n m n (shelf ID) = 6 thru 9
m (slot#) = 7 thru 11, 14 thru 17
E31
E31

1
m (slot#) = 8 thru 11, 14 thru 17
E32
E32

1
m (slot#) = 8 thru 11, 14 thru 17
PSW40
PSW40

1

1
m m (slot#) = 8 or 9
PSW80
PSW80

1

1
m m (slot#) = 8 or 9
PSW5WB
PSW5WB

1
m (slot#) = 12 or 13
PSW10WB
PSW10WB

1
m (slot#) = 12 or 13
ESW
ESW

1
n m n (shelf ID) = 3, 4 or 5
m (slot#) = 8 or 9
DOI-N08152
5-21
5.7.4 Line Facility
! AID Syntax: object tag bay shelf ID slot# line
TARGET SIGNAL
PACKAGE
TAG BAY SHELF SLOT LINE NOTES
STM-64 [OC-192]
SINF64F

1

2
m
1
m (slot#) = 2, 3, 4 or 5
STM-16 [OC-48]
SINF16F

1
n m
1
n (shelf ID) = 1, 3, 4 or 5
STM-4 [OC-12]
STM-1 [OC-3]
STM-0
SINFMF

1
n m l n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 thru 16
STM1e
STM1EF

1
n m l n (shelf ID) = 1, 3, 4 or 5
DS3
DS3F

1
n m l n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 4, 6, 10 or 12
GBE
GBEF

1
n m l n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 or 2
GBEM
GBEMF

1
n m l n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 thru 4
E12
E12F

1
n m l n (shelf ID) = 6 thru 9
m (slot#) = 8 thru 11, 14 thru 17
E31
E31F

1
m (slot#) = 8 thru 11, 14 thru 17
l (line) = 1 thru 6
E32
E32F

1
m (slot#) = 8 thru 11, 14 thru 17
l (line) = 1 thru 6
PSW<=>PSWWB
WBG - 1 - 1 - 1 -
p p (PSW40/80 port# used by EXTWB)
= 1 or 2 (on PSW40) or
= 1 thru 6 (w/PSW80)
DOI-N08152
5-22
5.7.5 Package Protection Switch Group
! AID Syntax: object tag bay shelf ID slot#
SW GROUP TAG BAY SHELF SLOT NOTES
STM1E
STM1ES

1
n m n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 5, 7, 11 or 13
DS3
DS3S

1
n m n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 5, 7, 11 or 13
E12
INFNS

1
n
7
E31/32
INFS

1
m (slot#) = 9, 11, 15 or 17
PSW
PSWS

1

1

9
PSW40/80 package
PSWS

1

1

13
PSW5WB/10WB package
Used only for internal process.
ESW
ESWS

1
n
9
ESW package
Used only for internal process.
DOI-N08152
5-23
5.7.6 Line Protection Switch Group
SW GROUP TAG BAY SHELF SLOT LINE NOTES
Linear
LINES

1

1
m l Main Shelf:
m (slot#) = 5, 7, 11 or 13
LINES

1

2
m
1
EXT64 Shelf:
m (slot#) = 3 or 5
LINES

1
n m l EXT16 Shelf:
m (slot#) = 5, 7, 11 or 13
2F MS-SPRing
[2F BLSR]
MS2FS

1

1
m
1
Main Shelf:
m (slot#) = 5, 7, 11 or 13
MS2FS

1

2
m
1
EXT64 Shelf:
m (slot#) = 3 or 5
MS2FS

1
n m
1
EXT16 Shelf:
m (slot#) = 5, 7, 11 or 13
4F MS-SPRing
[4F BLSR]
MS4FS

1

1
m
1
Main Shelf:
m (slot#) = 7 or 13
MS4FS

1

2

5

1
EXT64 Shelf
MS4FS

1
n m
1
EXT16 Shelf:
m (slot#) = 7 or 13
DOI-N08152
5-24
5.7.7 Synchronization
! AID Syntax: object tag bay shelf ID slot# timing group timing line
SYNC GROUP TAG BAY SHELF SLOT T-GRP T-LINE NOTES
Timing Source
Group
SYNCG

1

1

9

1
Internal Timing
Source Group
SYN-
CISG
1

1

9

1
External Timing
Source Group
SYNC-
ESG
1

1

9
t t (timing group) = 1 or 2
Timing Source
Unit
SYNCU

1

1

9

1
l Main Shelf:
l (timing line) = 1 thru 14
SYNCU

1
n
13

1
l EXTWB Shelf:
l (timing line) = 17 or 18
Internal Timing
Source Unit
SYN-
CISU
1

1

9

1
l l (timing line) = 1 thru 14
External Timing
Source Unit
SYN-
CESU
1

1

9
t l t (timing group) = 1 or 2
l (timing line) = 1 thru 12
DOI-N08152
5-25
5.7.8 Path Facility
5.7.8.1 Higher-Order Path
! AID Syntax: object tag bay shelf ID slot# line time slot
LEVEL TAG BAY SHELF SLOT LINE T-SLOT NOTES
VC-3
[STS-1]
VC-4
[STS-3c]
VC-4-4c
[STS-12c]
VC-4-16c
[STS-48c]
VC-4-64c
[STS-192c]
AU3

1

2
m
1
t SINF64:
m (slot#) = 2 thru 5
t (time slot) = 1 thru 192
AU3

1
n m
1
t SINF16:
n (shelf ID) = 1, 3, 4 or 5
AU3

1
n m l t SINFM (OP4):
n (shelf ID) = 1, 3, 4 or 5
l (line) = 1, 5, 9 or 13
AU3

1
n m l t SINFM (OP1), STM1E:
n (shelf ID) = 1, 3, 4 or 5
AU3

1
n m l
1
SINFM (OP0):
n (shelf ID) = 1, 3, 4 or 5
AU3

1
n m l
1
DS3:
n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 4, 6, 10 or 12
VC-3-1V ~ 48V
VC-4-1V ~ 16V
AU3

1

n
m
l
t GBEM:
n (shelf ID) = 1, 3, 4 or 5
VC-4
[STS-3c]
VC-4-4c
[STS-12c]
VC-4-16c
[STS-48c]
VC-4-64c
[STS-192c]
AU4

1

2
m
1
t SINF64:
AU4

1
n m
1
t SINF16:
n (shelf ID) = 1, 3, 4 or 5
AU4

1
n (shelf ID) = 1, 3, 4 or 5
l (line) = 1, 5, 9 or 13
AU4

1
n m l
1
SINFM (OP1), STM1E:
n (shelf ID) = 1, 3, 4 or 5
DOI-N08152
5-26
(5.7.8.1 Higher-Order Path continued)
5.7.8.2 Lower-Order Path (to/from SDH)
! AID Syntax: object tag bay shelf ID slot# line time slot TUG3 TUG2 TU
5.7.8.3 Lower-Order Path (to/from PDH)
VC-4-7V
[STS-3c-7V]
AU4

1
n m l t GBE:
n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 or 2
VC-4
(for HPT)
AUWB - 1 - 1 - 1 - p - t PSW5WB/10WB:
p (PSW40/80 port# used by EXTWB)
= 1 or 2 (on PSW40) or
= 1 thru 6 (w/PSW80)
LEVEL TAG BAY SHELF SLOT LINE T-SLOT TUG3 TUG2 TU NOTES
TU3
SDHTU

1
n
13

1
t s
1

1
t (time slot) = 1, 4, 7,
10, ..., 190
s (TUG3#) = 1 thru 3
TU12
SDHTU

1
n
13

1
t s r q n (shelf ID) = 6 thru 9
t (time slot) = 1, 4, 7,
10, ..., 190
r (TUG2#) = 1 thru 7
q (TU#) = 1 thru 3
LEVEL TAG BAY SHELF SLOT LINE NOTES
TU3
[E31/E32]
PDHTU

1
m (slot#) = 8 thru 11,
14 thru 17
l (line) = 1 thru 6
TU12
[E12]
PDHTU

1
m (slot#) = 8 thru 11,
14 thru 17
DOI-N08152
5-27
5.7.9 Path Monitor
VC-3
[STS-1]
VC-4
[STS-3c]
VC-4-4c
[STS-12c]
VC-4-16c
[STS-48c]
VC-4-64c
[STS-192c]
HPMON3

1

2
m
1
t SINF64:
HPMON3

1
n m
1
t SINF16:
n (shelf ID) = 1, 3, 4 or 5
HPMON3

1
n (shelf ID) = 1, 3, 4 or 5
l (line) = 1, 5, 9 or 13
HPMON3

1
n m l t SINFM (OP1), STM1E:
n (shelf ID) = 1, 3, 4 or 5
HPMON3

1
n m l
1
SINFM (OP0):
n (shelf ID) = 1, 3, 4 or 5
VC-4
[STS-3c]
VC-4-4c
[STS-12c]
VC-4-16c
[STS-48c]
VC-4-64c
[STS-192c]
HPMON4

1

2
m
1
t SINF64:
HPMON4

1
n m
1
t SINF16:
n (shelf ID) = 1, 3, 4 or 5
HPMON4

1
n (shelf ID) = 1, 3, 4 or 5
l (line) = 1, 5, 9 or 13
HPMON4

1
n m l
1
SINFM (OP1), STM1E:
n (shelf ID) = 1, 3, 4 or 5
DOI-N08152
5-28
5.7.9.2 Lower-Order Path
! AID Syntax: object tag bay shelf ID slot# line time slot TUG3 TUG2 TU
LEVEL TAG BAY SHELF SLOT LINE T-SLOT TUG3 TUG2 TU NOTES
TU3
LPMON

1
n
13

1
t s
1

1
t (time slot) = 1, 4, 7,
10, ..., 190
TU12
LPMON

1
n
13

1
t s r q n (shelf ID) = 6 thru 9
t (time slot) = 1, 4, 7,
10, ..., 190
r (TUG2#) = 1 thru 7
q (TU#) = 1 thru 3
DOI-N08152
5-29
5.7.10 Path Termination Point
5.7.10.2 Lower-Order Path
(AU4)
HPT

1
n
13

1
t n (shelf ID) = 6 thru 13
t (time slot) = 1, 4, 7, 10, ..., 190
(DS3)
HPT3

1
n m l
1
n (shelf ID) = 1, 3, 4 or 5
m (slot#) = 4, 6, 10 or 12
(GBE)
HPTE4

1
n m l t n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 or 2
(GBEM)
HPTM3

1
n m l t n (shelf ID) = 1, 3, 4 or 5
l (line) = 1 thru 4
LEVEL TAG BAY SHELF SLOT LINE NOTES
(TU3)
LPT

1
m (slot#) = 8 thru 11, 14 thru 17
l (line) = 1 thru 6
(TU12)
LPT

1
m (slot#) = 8 thru 11, 14 thru 17
DOI-N08152
5-30
5.7.11 External Clock Input
! AID Syntax: object tag bay shelf ID slot# port#

5.7.12 Housekeeping Alarm

5.7.13 Housekeeping Control
5.7.14 V11 User Channel Port
TIMING REFERENCE TAG BAY SHELF SLOT PORT NOTES
64 kHz + 8 kHz
EXC64K

1

1

9
p p (port#) = 1 or 2
DS1
EXCDS1

1

1

9
2 MHz
EXC2MH

1

1

9
2 Mbit/s
EXC2MB

1

1

9
Housekeeping Alarm TAG BAY SHELF SLOT PORT NOTES
Housekeeping Alarm
HKA

1

1

3
p p (port#) = 1 thru 16
Housekeeping Control TAG BAY SHELF SLOT PORT NOTES
Housekeeping Control
HKC

1

1

3
p p (port#) = 1 thru 8
V11 User CH Port TAG BAY SHELF SLOT PORT NOTES
V11 Port
V11PORT

1

1

3
p Main Shelf:
p (port#) = 1 thru 6
V11PORT

1

2

1
p EXT64 Shelf:
V11PORT

1
n
3
p EXT16 Shelf:
DOI-N08152
5-31
5.7.15 Overhead Access Channel
5.7.16 Data Communication Channel (DCC Port)
5.7.17 Virtual Concatenation (GBEM)
5.7.18 Channel ID (GBEM)
OH Access TAG BAY SHELF SLOT PORT NOTES
OH Access
OHCH

1

1

3
p Main Shelf:
OHCH

1

2

1
p EXT64 Shelf:
OHCH

1
n
3
p EXT16 Shelf:
DCC Port TAG BAY SHELF SLOT PORT NOTES
Regenerator
Section
RSDCC

1

1

3
p Main Shelf:
RSDCC

1

2

1
p EXT64 Shelf:
RSDCC

1
n
3
p EXT16 Shelf:
Multiplexer
Section
MSDCC

1

1

3
p Main Shelf:
MSDCC

1

2

1
p EXT64 Shelf:
MSDCC

1
n
3
p EXT16 Shelf:
Virtual Concatenation TAG BAY SHELF SLOT PORT NOTES
VCT
VCT

1
n m p n (shelf ID) = 1, 3, 4 or 5
m (slot #) = 4 thru 7, 10 thru 13
Virtual Concatenation TAG BAY SHELF SLOT ID NOTES
GFPCT
GFPCT

1
n m i n (shelf ID) = 1, 3, 4 or 5
m (slot #) = 4 thru 7, 10 thru 13
i (ID) = 1 thru 255
DOI-N08152
5-32
5.7.19 CPU
! AID Syntax: object tag bay shelf ID slot# CPU#
CPU (PKG) TAG BAY SHELF SLOT CPU# NOTES
SCCPU (MSC)
SCCPU

1

1

1

1
Main Shelf
AGCPU (MSC)
AGCPU

1

1

1

1
Main Shelf
SC16CPU (SC16)
SC16CPU

1
n
1

1
EXT16 Shelf:
SCWBCPU (SCWB)
SCWBCPU

1
n
1

1
EXTWB Shelf:
SWCPU (SSC)
SWCPU

1
n
2

1
Main/EXT16 Shelf:
n (shelf ID) = 1, 3, 4 or 5
SSCWBCPU (SSCWB)
SSCWB-
CPU
1
n
2

1
EXTWB Shelf:
OHCPU (OHC)
OHCPU

1

1

3
c Main Shelf:
c (CPU#) = 1 thru 3
OHCPU (COM)
OHCPU

1

2

1
c EXT64 Shelf:
c (CPU#) = 1 or 2
OHCPU (OHEXT)
OHCPU

1
n
3
c EXT16 Shelf:
c (CPU#) = 1 thru 3
PW40CPU (PSW40)
PW40CPU

1

1
m
1
Main Shelf:
m (slot#) = 8 or 9
PW80CPU (PSW80)
PW80CPU

1

1
m
1
Main Shelf:
m (slot#) = 8 or 9
PSWWBCPU
(PSW5WB/PSW10WB)
PSWWB-
CPU
1
n m
1
EXTWB Shelf:
m (slot#) = 12 or 13
EWCPU (ESW)
EWCPU

1
n m
1
EXT16 Shelf:
m (slot#) = 8 or 9
IF64CPU (SINF64)
IF64CPU

1

2
m
1
EXT64 Shelf:
IFCPU (SINFM/
SINF16/STM1E)
IFCPU

1
n m
1
Main/EXT16 Shelf:
n (shelf ID) = 1, 3, 4 or 5
IFT3CPU (DS3)
IFT3CPU

1
n m
1
Main/EXT16 Shelf:
n (shelf ID) = 1, 3, 4 or 5
GECPU (GBE)
GECPU

1
n m
1
Main/EXT16 Shelf:
n (shelf ID) = 1, 3, 4 or 5
GEMUCPU (GBEM)
GEMUCPU

1
n m
1
Main/EXT16 Shelf:
n (shelf ID) = 1, 3, 4 or 5
E12CPU (E12)
E12CPU

1
n m
1
EXTWB Shelf:
m (slot#) = 7 thru 11, 14 thru 17
E31CPU (E31)
E31CPU

1
n m
1
EXTWB Shelf:
m (slot#) = 8 thru 11, 14 thru 17
E32CPU (E32)
E32CPU

1
n m
1
EXTWB Shelf:
m (slot#) = 8 thru 11, 14 thru 17
DOI-N08152
5-33
5.7.20 Profile
! AID Syntax: object tag bay shelf ID file#
5.7.21 Memory Card
! AID Syntax: object tag bay shelf ID card#
5.7.22 Temporary Memory
5.7.23 All
Profile TAG BAY SHELF FILE NOTES
Alarm Severity Assignment
Profile
ASAP

1
n f n (shelf ID) = 1, 3 thru 13
f (file#) = 1 thru 50
Threshold Profile
THP

1
n f n (shelf ID) = 1, 3 thru 13
f (file#) = 1 thru 50
Memory Card (PKG) TAG BAY SHELF CARD NOTES
MMEM (MSC)
MMEM

1

1

1
Main Shelf
EMEM (SC16)
EMEM

1
n
1
EXT16 Shelf:
WBMEM (SCWB)
WBMEM

1
n
1
EXTWB Shelf:
(AID)
TMP
(AID)
ALL
DOI-N08152
Configuration Management
5-34
E
DOI-N08152
Performance Monitoring Performance Monitoring (PM) Type
6-1
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 BBM are described below according to
the layer.
6.1.1 Physical Layer
The following are the PM monitor types and their definitions of SDH [SONET] Physical
Layer:
The following are the supported monitor types for each facility:
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
STM64/STM16 OPT and OPR
STM64J/STM16J OPT and OPR
OC192/OC48 OPT and OPR
DOI-N08152
6-2
6.1.2 Regenerator Section Layer (Section Layer)
The following shows the PM monitor types and their definitions of SDH [SONET]
Regenerator Section Layer:
The following are the monitoring parameter, monitoring point, and monitoring span at Node
1 (U-Node BBM equipment) for each facility:
Near-End
BBE (Near-End Background Block
Error) SDH
Cumulative value of error block count. B1 is counter
value.
CV (Code Violation) SONET Occurrence time of Code rule violation. B1 is counter
value.
ES (Near-End Errored Seconds) EB (Error Block)/CV (Code Violation) occurrence is
checked per second. If EB/CV occurs or Defect is
detected, seconds (time) are accumulated.
SES (Near-End Severely Errored
Seconds)
If EB (CV) count exceeds K times (see 6.1.17 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)
SDH/Japan
OOF (Out of Frame) detection is checked per second.
If OOF is detected, seconds (time) are accumulated.
SEFS (Severely Errored Frame
Seconds) SONET
SEFS (Severely Errored Frame Seconds) detection is
checked per second. If SEFS is detected, seconds
Target Facility Monitoring Parameter Monitoring Point Monitoring Span
Near-End
STM1E BBE-RS, ES-RS, SES-RS, UAS-RS, OFS-RS 1 2 1
STM64/16/4/1 BBE-RS, ES-RS, SES-RS, UAS-RS, OFS-RS 1 2 1
STM64J/16J/4J/1J/0J BBE-RS, ES-RS, SES-RS, UAS-RS, OFS-RS 1 2 1
OC192/48/12/3 CV-S, ES-S, SES-S, UAS-S, SEFS-S 1 2 1
NODE 2
(Regenerator)
2
NODE 1
1
NODE 3
DOI-N08152
6-3
6.1.3 Multiplex Section Layer (Line Layer)
The following are the PM monitor types and their definitions of SDH [SONET] Multiplex
Section Layer:
Near-End
BBE (Near-End Background Block Error) SDH Cumulative value of error block count. B2 is counter
value.
value.
SES (Near-End Severely Errored Seconds) If EB (CV) count exceeds K times (see 6.1.17 SES
Threshold) per second or Defect is detected, seconds
Far-End
FEBBE (Far-End Background Block Error) SDH Cumulative value of FEEB (Far-End Errored Block) indi-
cated with REI_bit count. M0 is counter value.
FECV (Far-End Code Violation) SONET Occurrence time of Far-end code rule violation. Shown
as REI_bit. M0 is counter value.
FEES (Far-End Errored Seconds) FEEB (FECV) indicated with REI_bit or RDI detection is
checked per second. If FEEB or RDI occurs, seconds
FESES (Far-End Severely Errored Seconds) If FEEB (FECV) 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).
DOI-N08152
6-4
The following are the monitoring parameter, monitoring point, and monitoring span at Node
1 (U-Node BBM equipment) for each facility:
Near-End
STM64/16/4/1/0 BBE-MS, ES-MS, SES-MS, UAS-MS 4 3 4
STM64J/16J/4J/1J/0J BBE-MS, ES-MS, SES-MS, UAS-MS 4 3 4
OC192/48/12/3 CV-L, ES-L, SES-L, UAS-L, SEFS-L 4 3 4
STM1E BBE-MS, ES-MS, SES-MS, UAS-MS 4 3 4
Far-End
STM64/16/4/1/0 FEBBE-MS, FEES-MS, FESES-MS, FEUAS-MS 4 1 2
STM64J/16J/4J/1J/0J FEBBE-MS, FEES-MS, FESES-MS, FEUAS-MS 4 1 2
OC192/48/12/3 FEBBE-L, FEES-L, FESES-L, FEUAS-L 4 1 2
STM1E FEBBE-MS, FEES-MS, FESES-MS, FEUAS-MS 4 1 2
NODE 2
(Regenerator)
NODE 1
4
1
NODE 3
2
3
DOI-N08152
6-5
6.1.4 DS3 Line Layer
The following are the PM monitor types and their definitions for DS3 Line Layer:
The following are the monitoring parameter, monitoring point and monitoring span at Node 1
(U-Node BBM equipment) for each facility:
Near-End
CV (Code Violation) Occurrence time of Code rule violation. BPV and
EXZ are counter value.
ES (Near-End Errored Seconds) CV (Code Violation) occurrence is checked per sec-
ond. If CV occurs or Defect is detected, seconds
SES (Near-End Severely Errored Seconds) If CV count exceeds K times (see 6.1.17 SES
Threshold) per second or Defect is detected, sec-
onds (time) seconds accumulated.
LOSS (LOS Seconds) Cumulative value of seconds during LOS occur-
rence.
Near-End
DS3 CV-L, ES-L, SES-L, LOSS-L 2 1 2
NODE 1
2
DS3 Signal
NODE 2
1
Terminated DS3 Node
U-NODE BBM
U-NODE BBM
DOI-N08152
6-6
6.1.5 E12/E31/E32 Line Layer
The following are the PM monitor types and their definitions for E12/E31/E32 Line Layer on
the EXTWB shelf:
Near-End
CV (Code Violation) Occurrence time of Code rule violation. BPV and
EXZ are counter value.
onds (time) seconds accumulated.
Near-End
E12F/E31F/E32F CV-L, ES-L, SES-L 2 1 2
NODE 1
U-NODE BBM
Main
EXTWB
Terminated E12/E31/E32 Node
1
E12/E31/E32 Signal
2
DOI-N08152
6-7
6.1.6 GBE Line Layer
The following are the PM monitor types and their definitions for GBE Line Layer:
RX_BRD_OK The number of valid broadcast packets with packet sizes between 64 bytes
and the maximum when received.
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
RX_NORM_CRC The number of packets with packet sizes between 64 bytes and the maximum
with a CRC error.
RX_OCT_OK The number of valid packets received in bytes.
RX_OCTET_OK The number of valid packets received in octets.
RX_OVF_LOSS The number of discarded buffer-overflow packets received.
RX_PAUSE The number of valid overflow-controlled packets received.
RX_PKT_OK 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_CV-GFP Occurrence time of Code rule violation. B3 is counter value.
TX_ES-GFP EB (Error Block)/CV (Code Violation) occurrence is checked per second. If
EB/CV occurs or Defect is detected, seconds (time) are accumulated.
TX_MLT_OK The number of valid multicast packets
TX_OCT_OK The number of valid packets transmitted in bytes.
TX_OCTET The number of valid packets transmitted in octets.
TX_OVF_LOSS The number of discarded buffer-overflow packets transmitted.
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
DOI-N08152
6-8
Near-End
GBEF TX_BRD_OK, TX_CV-GFP, TX_ES-GFP,
TX_MLT_OK, TX_OCT_OK, TX_OCTET,
TX_OVF_LOSS, TX_PAUSE, TX_PKT,
TX_UNI_OK
1 1 2
GBEF RX_BRD_OK, RX_LONG, RX_MLT_OK,
RX_NORM_CRC, RX_OCT_OK,
RX_OCTET_OK, RX_OVF_LOSS,
RX_PAUSE, RX_PKT_OK, RX_SHORT,
RX_UNI_OK
4 3 4
NODE 1
NODE 2
U-NODE BBM
U-NODE BBM
1 4
2 3
GBE ROUTER
DOI-N08152
6-9
6.1.7 GBEM Line Layer
The following are the PM monitor types and their definitions for GBEM Line Layer:
RX_BRD_OK The number of valid broadcast packets with packet sizes between 64 bytes
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
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
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
DOI-N08152
6-10
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
NODE 2
U-NODE BBM
U-NODE BBM
1 4
2 3
GBE ROUTER
DOI-N08152
6-11
6.1.8 HPT3 Layer
HPT3 Layer is a higher order path termination layer on the DS3 line. The following are the
PM monitor types and their definitions for HPT3 Layer:
Near-End
value.
onds (time) are accumulated.
Far-End
FECV (Far-End Code Violation) SONET Occurrence time of Far-end code rule violation.
Shown as REI_bit and accumulated. G1 is counter
value.
FEES (Far-End Errored Seconds) FECV indicated with REI_bit or RDI detection is
FESES (Far-End Severely Errored Seconds) If FECV indicated with REI_bit count exceeds K times
per second or RDI is detected, seconds (time) are
accumulated.
Time).
Near-End
HPT3 CV-P, ES-P, SES-P, UAS-P 5 4 5
Far-End
HPT3 FECV-P, FEES-P, FESES-P, FEUAS-P 5 2 3
NODE 1
2
NODE 2
DS3 Terminal Node
5 4 3
DS3 DS3
DS3 Terminal Node
1
U-NODE BBM U-NODE BBM
DOI-N08152
6-12
6.1.9 HPTM3 Layer
HPTM3 Layer is a higher order path termination. The following are the PM monitor types
and their definitions for HPTM3 Layer:
Near-End
value.
Far-End
Shown as REI_bit and accumulated. G1 is counter
value.
FEES (Far-End Errored Seconds) FECV indicated with REI_bit or RDI detection is
FESES (Far-End Severely Errored Seconds) If FECV indicated with REI_bit count exceeds K times
accumulated.
Time).
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
ROUTER/SW
5 4 3
GBEM GBEM
ROUTER/SW
1
DOI-N08152
6-13
6.1.10 VCT Layer
VCT Layer is a VC termination layer. The following are the PM monitor types and their
definitions 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
ROUTER/SW
5 4 3
GBEM GBEM
ROUTER/SW
1
DOI-N08152
6-14
6.1.11 HP Monitor
The following are the PM monitor types and their definitions of SDH [SONET] HP monitor
(Higher Order Path Monitor):
Near-End
value.
value.
SES (Near-End Severely Errored Seconds) If EB (CV) count exceeds K times (see 6.1.17 SES
Far-End
FEBBE (Far-End Background Block Error) SDH Cumulative value of FEEB (Far-End Errored Block)
indicated with REI_bit. G1 is counter value.
Shown as REI_bit. G1 is counter value.
FEES (Far-End Errored Seconds) FEEB (FECV) indicated with REI_bit or RDI detection
is checked per second. If FEEB or RDI occurs, sec-
FESES (Far-End Severely Errored Seconds) If FEEB (FECV) indicated with REI_bit count exceeds
K times per second or RDI is detected, seconds (time)
are accumulated.
Time).
DOI-N08152
6-15
Near-End
HPMON Incoming
Signal SDH/Japan
BBE-P_IN, ES-P_IN, SES-P_IN, UAS-P_IN 2 1 2
HPMON Outgoing
Signal SDH/Japan
BBE-P_OUT, ES-P_OUT, SES-P_OUT,
UAS-P_OUT
5 4 5
HPMON Incoming
Signal SONET
CV-P_IN, ES-P_IN, SES-P_IN, UAS-P_IN 2 1 2
HPMON Outgoing
Signal SONET
CV-P_OUT, ES-P_OUT, SES-P_OUT,
UAS-P_OUT
5 4 5
Far-End
HPMON Incoming
Signal SDH/Japan
FEBBE-P_IN, FEES-P_IN, FESES-P_IN,
FEUAS-P_IN
2
4 6
HPMON Outgoing
Signal SDH/Japan
FEBBE-P_OUT, FEES-P_OUT,
FESES-P_OUT, FEUAS-P_OUT
5
1 3
HPMON Incoming
Signal SONET
FECV-P_IN, FEES-P_IN, FESES-P_IN,
FEUAS-P_IN
2
4 6
HPMON Outgoing
Signal SONET
FECV-P_OUT, FEES-P_OUT,
FESES-P_OUT, FEUAS-P_OUT
5
1 3
NODE 1
2
NODE 2
1
SDH [SONET]
Terminal Node
5
6 4 3
SDH [SONET]
Terminal Node
DOI-N08152
6-16
6.1.12 LP Monitor
The following are the PM monitor types and their definitions of SDH [SONET] LP monitor
(Lower Order Path Monitor) on the EXTWB shelf:
Near-End
BBE (Near-End Background Block Error) SDH Cumulative value of error block count. B3 or BIP2 is
monitored and counted for TU3 or TU12, respectively.
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.17 SES Thresh-
old) per second or Defect is detected, seconds (time)
are accumulated.
Near-End
LPMON Signal SDH BBE-P, ES-P, SES-P, UAS-P 1 4 1
NODE 1
2
SDH
Terminal Node
1 4 3
SDH
Terminal Node
Main
EXTWB EXTWB
NODE 2
Main
DOI-N08152
6-17
6.1.13 HPT
The following are the PM monitor types and their definitions of SDH HPT (Higher Order
Path Termination) on the EXTWB shelf:
Near-End
value.
accumulated.
are accumulated.
Far-End
indicated with REI_bit. G1 is counter value.
FEES (Far-End Errored Seconds) FEEB indicated with REI_bit or RDI detection is
FESES (Far-End Severely Errored Seconds) If FEEB indicated with REI_bit count exceeds K times
accumulated.
Time).
DOI-N08152
6-18
Near-End
HPT Signal SDH BBE-P, ES-P, SES-P, UAS-P 1 4 1
Far-End
HPT Signal SDH FEBBE-P, FEES-P, FESES-P, FEUAS-P 1 2 3
NODE 1
NODE 2
2
SDH
Terminal Node
1 4 3
SDH
Terminal Node
Main Main
EXTWB EXTWB
DOI-N08152
6-19
6.1.14 LPT
The following are the PM monitor types and their definitions of SDH LPT (Lower Order
Path Termination) on the EXTWB shelf:
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.
accumulated.
are accumulated.
Far-End
indicated with REI_bit. G1 and V5 are counter values
for TU3 and TU12, respectively.
FEES (Far-End Errored Seconds) FEEB indicated with REI_bit or RDI detection is
FESES (Far-End Severely Errored Seconds) If FEEB indicated with REI_bit count exceeds K times
accumulated.
Time).
DOI-N08152
6-20
Near-End
LPT Signal SDH BBE-P, ES-P, SES-P, UAS-P 1 4 1
Far-End
LPT Signal SDH FEBBE-P, FEES-P, FESES-P, FEUAS-P 1 2 3
NODE 1
NODE 2
2
SDH
Terminal Node
1 4 3
SDH
Terminal Node
Main Main
EXTWB EXTWB
DOI-N08152
6-21
6.1.15 Multiplex Section Protection
The following are the PM monitor types and their definitions of SDH [SONET] Multiplex
Section Protection:
The 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 Dura-
tion)
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 Group
Non-Protection Mode
Not Applicable.
MS4FS (4F MS-SPRing) Line 1 (West): PSD-R_W, PSD-S_W, PSC-R_W, PSC-S_W
Line 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_W
Line 2 (East): PSD-R_E, PSC-R_E
LINES PSD, PSC
DOI-N08152
6-22
6.1.16 AU Path
The following are the PM monitor types and their definitions for SDH [SONET] AU path:
The following is the PM monitoring parameter for each facility:
PJE-N (Pointer Justification Event
Negative stuff) SDH
A count of pointer justification event stuffed at NE
clock (negative). All the paths parameters con-
tained in line are created.
PJC-N (Pointer Justification Counts
Negative stuff) SONET
A count of pointer justification stuffed at NE clock
(negative). All the paths parameters contained in
line are created.
PJE-P (Pointer Justification Event
Positive stuff) SDH
A count of pointer justification event stuffed at NE
clock (positive). All the paths parameters contained
in line are created.
PJC-P (Pointer Justification Counts
Positive stuff) SONET
A count of pointer justification stuffed at NE clock
(positive). All the paths parameters contained in
line are created.
Target Facility Monitoring Parameter NOTE
AUn PJE-N, PJE-P AUn
STSn PJC-N, PJC-P STSn
DOI-N08152
6-23
6.1.17 SES Threshold
Facility Monitoring SES Parameters SES Threshold NOTE
STM64 SES-RS 2400
SES-MS/FESES-MS 2400
STM16 SES-RS 2400
STM4 SES-RS 2400
STM1 SES-RS 2400
STM1E SES-RS 2400
STM64J SES-RS 2400
STM16J SES-RS 2400
STM4J SES-RS 2400
STM1J SES-RS 2400
STM0J SES-RS 2400
OC192 SES-S 9568
SES-L/FESES-L 9836
OC48 SES-S 2392
SES-L/FESES-L 2459
OC12 SES-S 616
SES-L/FESES-L 615
OC3 SES-S 155
SES-L/FESES-L 154
DS3 Line SES-L/FESES-L 44
HPMON3 SES-P/FESES-P 2400 Both In/OUT
HPT3 SES-P/FESES-P 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 EXTWB Shelf
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
DOI-N08152
Performance Monitoring PM Data Management
6-24
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). The
label 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-minute
period (starting each hour at 00, 15, 30, 45 minutes).
! 1-day: The 1-day register holds the accumulated value of every 24-hour period (starting
at 00:00 (midnight) each day).
When the registers exceed the number, the oldest PM condition is overwritten with the latest
one.
6.2.2 Data Reliability
Validity information is added to each PM monitor type to validate/invalidate data. The
following 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).
DOI-N08152
Performance Monitoring TCA Function
6-25
6.3 TCA FUNCTION
U-Node BBM provides the Threshold Crossing Alert (TCA) function that issues an alert if
the value of the monitored PM type reaches or exceeds that of the specified threshold. The
values 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 a
PM type, the TCA of that PM type will not be reported. TCA function is disabled when the
target objects service state is set to OOS-MA-AS, or its Port Mode is set to AUTO. PM
monitor types for physical layer and switching do not have TCA function.
DOI-N08152
Performance Monitoring IPPM Management
6-26
6.4 IPPM MANAGEMENT
In U-Node BBM, PM monitoring is carried out on layers of path points that are not
termination 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 following
illustrations show the monitor points. Registered path supports the monitor type shown in
the 6.1 Performance Monitoring (PM) Type subsection.
6.4.1.1 Monitor Points for STMn Interface
6.4.1.2 Monitor Points for PSWWB (EXTWB Shelf)
STMn
Interface
STMn
Interface
Monitor Point
Monitor Point
Monitor Point
Monitor Point
STMn
Interface
Lower Order
Monitor Point
PSWWB
Higher Order
Crossconnect
Lower Order
Crossconnect
PDH
Interface
DOI-N08152
Performance Monitoring IPPM Management
6-27
6.4.2 Accumulation
There are two modes: AUTO mode and FIX mode to support the IPPM function for
registered paths.
For a path set to the AUTO mode, the PM is accumulated/managed according to the
concatenation level of its incoming signal.
For a path set to the FIX mode, the PM is accumulated/managed by the specified range of the
path band.
DOI-N08152
Performance Monitoring
6-28
E
DOI-N08152
Fault Management Monitored Items
7-1
7. FAULT MANAGEMENT
U-Node BBM 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 and
Maintenance manual for full items.
DOI-N08152
Fault Management Management Parameters
7-2
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 Severity
Assignment 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 BBM manages alarm severity of all the detected alarms in a table format. This
table 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.
DOI-N08152
Fault Management Management Parameters
7-3
7.2.2 Delay/Stretch Time
The following describes the functions of Delay and Stretch Time:
! Delay Time
Delay Time is a specific period for the process to determine if the detected failure is an
alarm to be reported.
! Stretch Time
Stretch Time is a specific period for the process to determine if the alarm has been cleared.
DOI-N08152
Fault Management Alarm Report
7-4
7.3 ALARM REPORT
When an alarm is detected, the user is notified by lighting up the LEDs on the package and
the rack, and reporting the alarm to user interface (for example, the CID). Alarm notification
is 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 report
the 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 alarm
report includes time information concerning when MSC confirms alarm occurrence and
recovery. The user can set whether an automatic report is permitted or prohibited for each
user 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 MSC
! LED on front of Rack
DOI-N08152
Fault Management Alarm Report
7-5
7.3.3.2 Delay/Stretch Process
! Delay Time
Delay Time is a specific period for the process to determine if the detected failure is an
alarm to be reported.
! Stretch Time
Stretch 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. The
following 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 audible
alarm (AB) is silenced; however, AB will be output if another alarm occurs later. The U-
Node BBM has an ACO lamp on the MSC package to show the ACO status.
7.3.4 Processing Alarm Masks
! Service State and Processing Alarm
The following table shows the process of when an alarm is generated and the relationship
between an NEs managed object and its service state.
! PORT Mode
This function is used to stop alarm reporting of physical layer, and PORT mode is TP mode
available 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 facilitys service state. Refer
to 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
DOI-N08152
Fault Management Offline Monitoring
7-6
E
7.4 OFFLINE MONITORING
The offline monitoring function is provided for redundant packages. When one package is
offline, it executes a self-diagnostic test to monitor package failures.
DOI-N08152
Log Function Command Log
8-1
8. LOG FUNCTION
U-Node BBM controls and manages the interface with the user according to the TL1
command format. The Network Element records a history of the AO Buffer and Command
Log. An operator can retrieve such logs in the CID to review activities on the Network
Element.
8.1 COMMAND LOG
Command Log is a history of commands issued by the operator and their response from the
Network Element. Commands that are executed are logged and failed commands are not
logged. Command Log Data can be initialized.
8.1.1 Mode of Logging
Main, EXT16 and EXT64 shelves can store up to 500 command logs in total, while each
EXTWB shelf can store up to 500 command logs independently. There are two modes for
Command Log. The logging mode affects the response of the logging function when the
number of logs reaches the maximum:
! HALT Mode
Logging stops when the number of logs reaches the maximum number. The network
element dispatches an alarm to notify the user.
! WRAP Mode
When the number of logs reaches the maximum, the network element overwrites the oldest
log with the next log. This mode is the default setting.
DOI-N08152
Log Function AO Buffer
8-2
E
8.2 AO BUFFER
The autonomous output (AO) Buffer is a history of messages (reported automatically) from
the 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 for Main, EXT16 and EXT64 shelves is 2,500 at maximum.
The EXTWB shelf has independent log information (up to 2,500 AO Buffers for each
EXTWB shelf). This cannot be changed. There is only one mode for AO Buffer logging. It
is similar to WRAP mode for the Command Log: the oldest log is overwritten with a new log
after the maximum number of logs is reached.
DOI-N08152
Maintenance Operation Loopback Function
9-1
9. MAINTENANCE OPERATION
This section describes the Maintenance functions for supporting NEs, traffic, networks, and
others.
9.1 LOOPBACK FUNCTION
9.1.1 Line Loopback
Each Signal Interface package equipped on the U-Node BBM supports the following two
loopback functions for failure isolation:
! Facility Loopback
! Terminal Loopback
In addition to the functions above, the PDH interface package (E12, E31 and E32) also
supports the following loopback function:
! Remote Loopback
During loopback execution, the MNT LED on the front of the MSC package lights up to
indicate the maintenance mode.
DOI-N08152
9-2
9.1.1.1 Facility Loopback
The incoming signal from NODE A is looped back to NODE A. The AIS is inserted before
the 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 a
package, through the crossconnection point, then is output to NODE B:
For the PDH interface package (E12, E31 and E32), the terminal loopback function is
operated as follows:
INF
PKG
XC
INF
PKG
AIS
LOCAL NODE
NODE A NODE B
NODE A
Main Shelf EXTWB Shelf
NODE B
HOSW LOSW PDH PKG
2M/34M/45M
AIS
INF
PKG
XC
INF
PKG
LOCAL NODE
NODE B NODE A
NODE A
NODE B
HOSW LOSW PDH PKG
2M/34M/45M
AIS
DOI-N08152
9-3
9.1.1.3 Remote Loopback
The remote loopback function (an original NEC function known as L_Bit_LPBK) is
provided for the PDH interface package on the EXTWB shelf (E12, E31 and E32) only, to
aid in the maintenance or troubleshooting of transmission networks. When the remote
loopback command issued from the CID at the local station is detected in the remote Node,
the received 2M/34M/45M signal is looped back towards the originating station in the E12/
E31/E32 package. When this occurs, the MNT LEDs on the MSC 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 the remote station.
The following shows the Remote Loopback function control bit formats.
Remote Node
HOSW LOSW PDH PKG
2M/34M/45M
AIS
2M/34M/45M
Local Node
HOSW LOSW PDH PKG
Remote Loopback
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)
140
bytes
(500 s)
VC-12 Signal
(2M)
Remote
Loopback Bit (L Bit)
R
Fixed Stuff Bit for E12 Loopback
I:
R:
V5:
Information Bit
Fixed Stuff Bit
VC-12 Path Overhead Byte
DOI-N08152
9-4

There are no ITU-T recommendations for loopback function since it is not a capability
envisaged by the recommendation draft committee; NEC designers utilize a fixed stuff bit in
the VC-12/VC-3 for the transmission of remote loopback command. Remote loopback
signal can be transmitted from the local station to the remote station through a number of
intermediate stations as long as none of the intermediate stations drops and broadcasts that
loopback channel. The following shows the terms for detecting and clearing remote
loopback 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)
Remote
Loopback Bit (L Bit)
R
Fixed Stuff Bit for E31/E32 Loopback
R:
J1:
Second Byte of VC-3 POH
First Byte of VC-3 POH
B3
R R R R L R J1
R
R
R
R
DOI-N08152
9-5
9.1.2 V.11 Port Loopback
For the user channel in V.11 port supported by U-Node BBM, there are the two following
loopback modes, the same as in an interface package:
! Facility Loopback
! Terminal Loopback
During loopback execution, the MNT LED on the front of the MSC package lights up to
indicate the maintenance mode.
9.1.2.1 Facility Loopback
The incoming signal from an external V.11 Incoming Port is looped back in the OHC
package, and the signal is output to an external interface. The all 1 signal is inserted to the
lines 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 line
facilitys overhead, and is output. All 1 is inserted to the V11 port that carries the assigned
line facility.
INF
PKG
OHC
PKG
MAIN SHELF
V.11 Port
Overhead Data Bus
INF
PKG
OHC
PKG
MAIN SHELF
V.11 Port
Overhead Data Bus
DOI-N08152
Maintenance Operation Automatic Laser Shutdown
9-6
9.2 AUTOMATIC LASER SHUTDOWN
U-Node BBM provides the Automatic Laser Shutdown (ALS) function to prevent the
operator 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 Laser
Shutdown (ALS) function is enabled to stop optical output in order to prevent the operator or
maintenance personnel from any accidental eyesight damage. The ALS mode is disabled
when normal signals are received from the far-end NE. The local NE starts transmitting
signals normally.
The following illustration shows an example. The user can choose whether or not to use the
ALS function via the CID.
There are two ALS restart modes.
! Auto Restart
While in the ALS mode, NE will regularly transmit optical signals. After receiving normal
signals 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 Restart
Makes an NE (SINFn package) release an optical output via the CID or upper OS, which
disables the ALS.
Optical Output Time:
Short-ON: 2 sec (default), or 9 sec
Long-ON: 90 sec
INF
PKG
LOCAL NODE
INF
PKG
LOCAL NODE
Optical Output
Shutdown
LOS Detection
DOI-N08152
9-7
9.2.1.1 Exception for GBEM Package
GBEM package does not have this ALS function. However, if the following alarm(s) is/are
detected, GBEM stops its optical output, which is reported as ALS on GBEMF, for the
purpose of alarm transmission:
! 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 function, any operations of
ALS for this package are not effective. When those failures are cleared, GBEM restarts
optical output.
DOI-N08152
9-8
9.2.2 Automatic Power Shutdown (APSD)
The Automatic Power Shutdown (APSD) function stops optical output from OPT amplifier if
optical input to OPT amplifier is lost or not detected. There are two types of OPT amplifier:
Pre-Amplifier, which amplifies the Optical Input Signal, and Booster Amplifier, which
amplifies the output signal. This function is provided only on an optical interface package
with OPT amplifier. This function is an internal U-Node BBM function.
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/E AMP
AMP E/O
APSD Optical
Output Shutdown
O/E
APSD Optical
Output Shutdown
AMP
AMP E/O
O/E AMP
AMP E/O
AMP Input
Shutdown
DOI-N08152
9-9
9.2.3 Lower-Level Optical Output (Reflected Alarm Detection)
This function is an internal U-Node BBM function. 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 Amplifiers which can detect the reflected alarm. This
function is also enabled when optical output restarts when recovering from the APSD
condition; a lower-level optical signal is output and reflection is verified.
9.2.4 Forced Optical Output Shutdown
SDH [SONET] optical output signal can be forcibly shut down by CID operation. During the
execution of this function, the condition is notified, and the MNT LED on front of the MSC
package lights up.
O/E
Lower Level
Optical Output by
detecting a
reflected alarm
AMP
AMP E/O
O/E AMP
AMP E/O
DOI-N08152
Maintenance Operation Overhead Access
9-10
9.3 OVERHEAD ACCESS
U-Node BBM accesses the user channels in the SDH [SONET] overhead. This function is
provided by SINFn and STM1E packages with OHC, COM, and OHCEXT packages.
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 setting for each
port.
9.3.1.1 Accessible Facility
The following interfaces OH bytes can be accessed as a user channel:
SINF64 package: STM64 [OC192]
SINF16 package: STM16 [OC48]
SINFM package: STM4 [OC12], STM1 [OC3], STM0
STM1E package: STM1e
9.3.1.2 Usable Overhead Byte
The following OH bytes can be accessed as a user channel:
RS [Section] Layer Overhead: E1 and F1
MS [Line] Layer Overhead: E2 and MDCH (D4 to D12)
9.3.1.3 User Channel Loopback
U-Node BBM 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 be
confirmed. 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 OHC
PKG, and the signal is output to V.11 port.
! Terminal Loopback: An outgoing signal from V.11 port is looped back in OHC
PKG, and the signal is output to the line overhead again. The all 1 signal is sent
to V.11 port-side.
DOI-N08152
9-11
9.3.2 DCC LAPD Access
U-Node BBM supports the LAPD access function to access MSDCC and RSDCC.
For OHC or OHCEXT package, 4, 8, or 12 DCC_PORT termination points can be selected.
COM package has 8 DCC_PORT termination points.
9.3.3 Overhead Through
U-Node BBM supports the Overhead Through function to an arbitrary line facilitys
overhead on SINFn and STM1E packages.
The following overhead bytes can be used for this function:
RS [Section] Overhead: Z0-2, Z0-3, Z0-4, E1, F1, NU-1, NU-2, NU-3, and NU-4
MS [Line] 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 BBM has a digital branch function and supports the orderwire function by using E1
or E2 bytes. Up to ten lines can be connected to digital branches per shelf. Either of the
following PCM coding methods can be selected: A-Law or -Law.
9.3.4.1 Orderwire Interface
U-Node BBM provides the following orderwire interfaces in the Main shelf. VF and V.11
Interfaces with frame pulse are also provided in EXT64/EXT16 shelves.
VF (See NOTE)
HEAD SET
TEL SET
V.11 Interface with frame pulse
NOTE: VF Interface Transmission Level
Incoming Signal: 15.5 to 0 dBm
Outgoing Signal: 8.5 to 7.0 dBm
Modification is possible in 0.5-dBm units.
DOI-N08152
9-12
9.3.4.2 Calling
There are three methods for calling:
! All-Call
By pressing the CALL switch on the front of the OHC package, all the NEs that support
this function can communicate with the orderwire. At local node (call-receiving station),
pressing the ANS. button allows the user to talk.
! Selective-Call
At the call-origination station, connect the telephone set to the TEL SET terminal on the
OHC 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 the
ANS. button allows the user to talk.
! Group-Call
At the call-origination station, connect the telephone set to the TEL SET terminal on the
OHC package, and dial the number (group call ID) of the NE that you want to
communicate with. Dialed station(s) that has (have) the same group call ID in the network
is (are) called. At the local node (call-reception station), pressing the ANS. button allows
the user to talk.
DOI-N08152
Maintenance Operation Line Switch Exercise
9-13
9.4 LINE SWITCH EXERCISE
U-Node BBM supports this function to confirm in advance if the switching operation is
properly carried out to the following line protection. This function does not affect the main
signal. It is performed by sending/receiving K1/K2 command between local and remote
stations.
! Bi-directional Linear Line Protection
! Ring Protection
DOI-N08152
Maintenance Operation Housekeeping
9-14
9.5 HOUSEKEEPING
U-Node BBM supports the housekeeping alarm functions and housekeeping control
functions. The Housekeeping alarm function is used to read alarms in a station and reports
alarm occurrence. The Housekeeping control function is used to control equipment, such as
the 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 alarm
notification.
! 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 by
issuing a command via CID.
! HKC Ports: 8 built-in ports
! Control Logic: HKC alarm polarity and duration time can be set for each
port.
! Alarm Name Setting: Controlling signal name can be set for each HKA port via
CID.
DOI-N08152
Maintenance Operation Reset Function
9-15
9.6 RESET FUNCTION
All the packages equipped on U-Node BBM have a CPU. This function is used to reset the
CPUs.
9.6.1 How to Reset CPU
To reset a CPU, there are two methods:
! Reset an individual CPU by the CID.
! Reset a package by pressing the RESET button on the front of the package
(provided on MSC, SC16 and SCWB packages).
9.6.2 Restart Level
! Hot Start: U-Node BBM starts according to system administration information previously
set.
! Cold Start: Cold Start is used when the equipment is turned on for the first time after
installation with no data in NE.
DOI-N08152
Maintenance Operation Path Test
9-16
9.7 PATH TEST
U-Node BBM supports the Path Test function. By using this function, the network
administrator can verify the direction and quality of the path in the objective network in path
units.
9.7.1 Example of Operation
You can independently set the test access sending function, which activates the pattern
generator (PG), and the test access receiving function, which activates the error detector (ED)
to an arbitrary AU or TU path registered in U-Node BBM. While executing this function, the
MNT LED on front of the MSC package lights up to show maintenance status.
The following illustrations show examples:
Example 1 - Path Test (1-Way)
Example 2 - Path Test (2-Way)
PG
U-NODE U-NODE U-NODE
ED
Path Test Line
AIS
Insertion
PG
U-NODE U-NODE
Path Test Line
AIS
Insertion
ED
MON
Facility
Loopback or
Cable Loop U-NODE
PG: Path Test Pattern Circuit
ED: Path Test Pattern Monitor or Error Detector
DOI-N08152
Maintenance Operation Path Test
9-17
9.7.2 Test Access Sending Function
This function sends a random test pattern to an AU or TU path in U-Node BBM. When
sending the test pattern, you can specify the following parameters.
*1 Only Outgoing can be specified for the EXTWB path test.
*2 Only PN-15 can be specified for the EXTWB path test.
9.7.3 Test Access Receiving Function
This function receives a random test pattern to an AU facility registered in U-Node BBM,
and counts bit error ratio and out-of-synchronization time. To receive the test pattern, the
following parameters can be specified:
*1 Only Incoming can be specified for the EXTWB path test.
*2 Only PN-15 can be specified for the EXTWB path test.

Parameters Setting Value
Direction Outgoing/Incoming *1
Pattern Type PN-15/PN-23 *2
C2 Value UNEQPT/EQPT
Parameters Setting Value
Direction Outgoing/Incoming *1
Pattern Type PN-15/PN-23 *2
AIS Insertion ON/OFF
Counter Description Setting Value
Bit Error Bit error count 0-65535
Out of Pattern Period of receiving viola-
tion for test pattern
0-65535
DOI-N08152
Maintenance Operation
9-18
E
DOI-N08152
Security Management Type of User Account
10-1
10. SECURITY MANAGEMENT
The U-Node BBM provides a security system to prevent unauthorized users from accessing
the network element. Only users with proper accounts are authorized to access the system.
The following describes security management in the U-Node BBM system.
10.1 TYPE OF USER ACCOUNT
U-Node BBM 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 Users level can be changed by another Super
User. Only Super Users have the right to add and delete users, and modify attributes of other
users.
10.1.2 Normal User
A Normal User is any user who is not a Super User. Normal Users have no rights to add or
delete users, or modify attributes of other users.
10.2 USER ATTRIBUTES
There are six attributes that each user retains: User Identification, Password, User Privilege
Code Level, User Account Expiration, and Password Aging (Password Expiration). See the
following descriptions on each attribute.
DOI-N08152
Security Management User Attributes
10-2
10.2.1 User Identification (UID)
User Identification is a unique name given to each user. Duplicated names are not allowed in
the 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 that
can 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, the
following combinations should not be used:
/*
*/
The reason for this restriction is that /* and */ are used respectively as the beginning of
comment and end of comment marks in TL1.
3. Case Sensitive
UIDs 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
DOI-N08152
10-3
10.2.2 Password (PID)
The password is a secret code for authorization to access the network element. Every user
must 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 reject
registration of the new user or changing to a new password, and will prompt the user to enter
another password.
DOI-N08152
10-4
10.2.2.2 Valid ASCII Characters for PID
The Characters with ** in the table are special characters.
NOTES:
1. PID must be between 6 to 10 characters long.
2. PID must use the following characters:
at least 1 character must be an uppercase character
at least 1 character must be a lowercase character
at least 1 character must be a numeric
at least 1 character must be a special character: ! % ( ) + - . = ? [ ] ^ _ { | } ~
3. PID must be different from UID.
4. PID used in system administration commands is 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
DOI-N08152
10-5
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 network
element. The specifiable period are Infinite or 1 day through 999 days.
Super Users can change the User Account Expiration for Normal Users. However, if User
Account Expiration becomes 0, it can no longer be changed. Changes must be made before
the number of days reaches 0.
User Account Expiration cannot be specified for a Super User; selection is fixed to Infinite.
10.2.4 Password Aging
A Super User can limit the expiration of each users password by specifying Password Aging.
The specifiable period is Infinite or 1 day through 999 days. Once Password Aging is
specified, 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 users password
expires (specified in Password Aging). When the password expires, it is invalid and the user
is asked to provide a new password. A user is notified by an NE when his/her password will
expire 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 TL1
command is set to a certain UPC level. If the user does not have the same UPC Level as the
TL1 command that the user is trying to execute, the Network Element will reject the request
and 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.
DOI-N08152
10-6
Command Code 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
CANC
CANC-CUTOVER M 4
CANC-USER A
CMPR-PTHTRC-FCLT M 3
CPY-BKMEM M 1
CPY-LCLTFTP-FILE M 4
CPY-LOCAL-DATA 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-BRDG-FCLT P 4
DLT-CRS-FCLT P 4
DLT-EQPT P 3
DLT-FCLT P 3
DLT-SECU-USER A 5
DLT-TADRMAP P 4
ED-CRS-FCLT P 4
ED-EQPT P 2
ED-FCLT P 2
DOI-N08152
10-7
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
ED-TADRMAP P 4
ED-TARP P 4
ED-TCPIP P 4
ED-ULSDCC P 4
ENT-BRDG-FCLT P 4
ENT-CRS-FCLT P 4
ENT-EQPT P 3
ENT-FCLT P 3
ENT-ROLL-FCLT P 4
ENT-SECU-USER A 5
ENT-TADRMAP 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
DOI-N08152
10-8
INIT-TDC M 4
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-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
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
RLS-LPBK-FCLT M 2
RLS-PROTNSW-EQPT M 3
RLS-PROTNSW-FCLT M 3
RLS-SHTDN-FCLT M 3
DOI-N08152
10-9
RLS-SYNCNSW M 3
RLS-SYNCNWTR M 3
RLS-TSTACS-RX M 2
RLS-TSTACS-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-EQPT M 1
RTRV-ATTR-FCLT 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-FCLT P 1
RTRV-FILESTAT M 1
RTRV-HDR M 1
RTRV-IPINF P 1
RTRV-LCPYSTAT M 1
RTRV-LDB M 4
RTRV-LED-EQPT M 1
RTRV-LOG M 1
DOI-N08152
10-10
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-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-SECU-STATUS A 1
RTRV-SECU-UPC A
RTRV-SECU-USER A
RTRV-SESSION M 4
RTRV-SQLCH-FCLT 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-FCLT M 1
RTRV-TH-PROFILE M 1
RTRV-TSTACS-RX M 1
RTRV-TSTACS-TX M 1
RTRV-ULSDCC P 1
SET-ATTR-CONT M 3
SET-ATTR-ENV M 3
DOI-N08152
10-11
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
DOI-N08152
Security Management Addition, Modification, and Deletion of Users
10-12
10.3 ADDITION, MODIFICATION, AND DELETION OF USERS
A Super User can add and delete other users and modify their attributes. A Normal User can
refer 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 User
cannot delete users who are currently logged in to the network element.
DOI-N08152
Security Management Accessing the Network Element
10-13
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 in
with an invalid UID or PID three times within 10 minutes, the Network Element will refuse
to authenticate that user for 10 minutes. After 10 minutes, the user can try to log in to the
network element again. The prohibition of authentication cannot be disabled even by the
TL1 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.
DOI-N08152
Security Management
10-14
E

Fungsi Unode

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Fungsi Unode

Hochgeladen von

Copyright:

Verfügbare Formate

DOI-N08152

Das könnte Ihnen auch gefallen