TAM-CS1000 System Description

TAM-CS1000
(Access Gateway)
System Description
SM0-000-S00050(V1.0)
Safety Instructions
This section describes the meaning of symbols used in this manual.
The following safety instructions for Danger, Warning and Caution are intended to prevent unexpected
physical danger or injury and system damage or malfunctioning. Therefore, to ensure your safety and
safe system operation, please read the following safety instructions thoroughly before operating the
system and follow them during operation.
Depending on the degree of expected danger and damage and the urgency of danger, dangers are
classified into the following categories.
Danger: Ignoring these warning results in an imminent danger such as death or

serious injury.
Ignoring this warning may result in a fatal condition such as death or serious
Warning:
injury.
Caution: Ignoring this warning may result in minor injury, or product damage or
malfunctioning.
※ After reading this Manual, keep it in a place that people can easily access for reference.
Copyright
The copyright of this Manual belongs to LG Electronics Inc.

Any reproduction, redistribution, or modification of this Manual without prior written approval of
LG Electronics Inc. is expressly prohibited.
Trademarks
LG Electronics and are the registered trademarks of LG Electronics Inc.

All other trademarks used in this Manual are the trademarks of the corresponding companies.
LG Electronics shall not be liable in any way for the results of any kind resulting from random
interpretation of the content of this Manual or voluntary assumption of the content not described here.
This Manual is subject to change by LG Electronics without prior notification for the purpose of
function improvement and design change of the product. If you want receive updated Manual or have
any questions about the information state in the Manual, please contact at the following address.
Address:
LG Research Complex 1 Customer Support Center
533 Hogye 1-dong, Dongan-gu, Anyang-si, Gyeonggido
TEL: 1588-9388
Copyright © 2004 LG Electronics, Inc. All Rights Reserved

Revisions
Version Date Reason Description
1.0 2005/05/25 Initial Issue

Contents
Contents
Chapter 1. TAM Overview .................................................................1-1

1. Overview..................................................................................................... 1-1
1.1 TAM Configuration ..................................................................................................................... 1-1
1.1.1 Applied Network Configurations....................................................................................... 1-2
1.1.2 Elements to Configure Application Network ..................................................................... 1-2
1.1.3 Network Configurations..................................................................................................... 1-4
1.2 System Specifications .................................................................................................................. 1-7
1.2.1 TAM-CS1000 (Host Mode) ............................................................................................... 1-7
1.2.2 TAM-CS1000 (RS Mode) .................................................................................................. 1-7
1.3 Housing........................................................................................................................................ 1-8
1.3.1 TAM-CS1000 (Host & RS Mode) ..................................................................................... 1-8
1.4 Power ......................................................................................................................................... 1-11
Chapter 2. TAM Architecture and Configuration ............................2-1

1. System and Hardware Architecture ......................................................... 2-1
1.1 TAM-CS Configuration ............................................................................................................... 2-3
1.1.1 Interface ............................................................................................................................. 2-5
1.1.2 Configuration ..................................................................................................................... 2-6
1.1.3 Hardware Capacity........................................................................................................... 2-11
1.2 Hardware Architecture............................................................................................................... 2-13
1.2.1 TAM-CS1000 (Host Mode) ............................................................................................. 2-13
1.2.2 TAM-CS1000 (RS Mode) ................................................................................................ 2-27
2. Software Configuration ........................................................................... 2-30
2.1 Overview ................................................................................................................................... 2-30
2.2 Call Processing Functions.......................................................................................................... 2-31
2.2.1 PSTN Control .................................................................................................................. 2-31
2.2.2 Softswitch Interface Function .......................................................................................... 2-33
2.2.3 V5.2 Connection Control ................................................................................................. 2-34
2.2.4 V5.2 Configuration Protocol Control............................................................................... 2-36
2.2.5 Data Service Control........................................................................................................ 2-40
2.3 Operation and Management Functions ...................................................................................... 2-44
2.3.1 TMS ................................................................................................................................. 2-44
2.3.2 TAM Agent ...................................................................................................................... 2-45
2.3.3 Data Processing Functions ............................................................................................... 2-46
2.3.4 Statistics Functions .......................................................................................................... 2-46
2.3.5 Start, Restart, and Loading Functions .............................................................................. 2-48
2.3.6 MMI (Man Machine Interface) Function......................................................................... 2-49
2.3.7 Time Management Function ............................................................................................ 2-55
2.4 Maintenance Functions .............................................................................................................. 2-56
2.4.1 Configuration Control Function....................................................................................... 2-56
2.4.2 Resource Management Functions .................................................................................... 2-57
PAGE : i
Contents
2.4.3 Fault Handling Function .................................................................................................. 2-58

2.4.4 Audit Function ................................................................................................................. 2-61
2.4.5 System Sync Fault Handling Function............................................................................. 2-61
3. Outdoor Housing ..................................................................................... 2-62
3.1 Overview of Outdoor Housing................................................................................................... 2-62
3.1.1 Overview.......................................................................................................................... 2-62
3.1.2 General............................................................................................................................. 2-62
3.1.3 Features............................................................................................................................ 2-63
3.2 Structure and Shape ................................................................................................................... 2-64
3.2.1 Configuration ................................................................................................................... 2-64
3.2.2 Specifications................................................................................................................... 2-64
3.2.3 Appearance ...................................................................................................................... 2-65
3.2.4 Cooling Method ............................................................................................................... 2-66
3.2.5 Equipment Requirements................................................................................................. 2-67
3.2.6 Environmental Conditions ............................................................................................... 2-67
3.3 Functional Description............................................................................................................... 2-68
3.3.1 Power Cooling Module (Heat Exchanger)....................................................................... 2-68
3.3.2 Power Distribution Panel (PDP) ...................................................................................... 2-68
3.3.3 Optical Fiber Distribution (OFD) .................................................................................... 2-68
3.3.4 Storage Battery................................................................................................................. 2-68
3.3.5 Main Distribution Frame (MDF) ..................................................................................... 2-69
3.3.6 GND Panel....................................................................................................................... 2-69
3.3.7 Fan ................................................................................................................................... 2-69
3.4 Operation Description............................................................................................................... 2-70
3.4.1 Cable Clustering .............................................................................................................. 2-70
3.4.2 Connecting Ground Cable................................................................................................ 2-70
3.4.3 Main Power Supply.......................................................................................................... 2-71
3.4.4 Installing Power Distribution Panel (PDP) ...................................................................... 2-71
3.4.5 Installing Battery.............................................................................................................. 2-71
3.5 Maintenance............................................................................................................................... 2-72
3.5.1 Maintenance of Housing .................................................................................................. 2-72
3.5.2 Battery Maintenance ........................................................................................................ 2-74
Chapter 3. Appendix .........................................................................3-1
PAGE : ii
Preface
Preface
Introduction to the Manual
This Manual describes the Total Access Module (TAM) in general including its architectural,
functional and performance characteristics.
Intended Readers
This Manual is intended for the TAM developers and operators.
Content Composition
This Manual is composed as follows:
Chapter 1 Overview
This Chapter describes the following information in order to introduce the TAM:
- Overview
- Network Configuration and Environment of the System
- System Specifications
Chapter 2 System Architecture and Configuration

This Chapter describes the following information about the TAM architecture and configuration.
- System Architecture
- System and Rack Configuration
- Hardware
- Software
- Outdoor Housing
Chapter 3 Appendix
This Chapter describes the definition of abbreviations.
PAGE : i
Chapter 1 TAM Overview
Chapter 1. TAM Overview
1. Overview
Total Access Module (TAM) provides telephone services and high-speed data service on a single
platform, accommodating voice subscribers (POTS) and data subscribers (VDSL, Ethernet), and thus
is available on both Pre-NGN and NGN environments.
The Pre-NGN refers to the phase before the NGN is fully implemented in which Softswitch that
configures the Service and Control layer; servers including Application Server (AS); packet network
equipment that configures the Transport layer; and gateways such as access, trunk, and signaling
gateways that configure the Access layer are not yet implemented.
In the Pre-NGN phase, TAM provides subscriber services in interworking with the Local Exchange
(LE) while in the NGN phase, it provides subscriber services in interworking with Softswitch instead
of the LE.
1.1 TAM Configuration

TAM can provide the following functions and services.
System Type
1) TAM-CS1000
(1) Host Mode
- Installed in various locations such as CO/remote CO/APT/biz. Buildings, to accommodate

subscribers
- Accommodates remote subscribers via a small number of TAM-CS1000s (RS Mode) (Also possible
to operate it independently without accommodating RSs)
- Interworks directly with LE or Softswitch.
- Available as outdoor-housing type, depending on the installation location
SM0-000-S00050(V1.0)
PAGE : 1-1
LG Electronics, Inc. All Rights Reserved
Edited by Foxit Reader
Copyright(C) by Foxit Software Company,2005-2007
For Evaluation Only.
(2) RS Mode
- Installed in various remote locations such as remote CO/APT/business buildings, to accommodate

subscribers.
- Applied as a remote system of TAM-HS, to accommodate remote subscribers.

- Applied as a remote system of TAM-CS1000 (Host Mode), to accommodate remote subscribers.
- Interworks indirectly with the LE or Softswitch via TAM-HS or TAM-CS1000 (Host Mode).
- Available as outdoor-housing type, depending on the installation location.
Subscriber Types Provided by the System
TAM-HS and TAM-CS (Host and RS Modes) provide the following subscribers.[U1]
(1) POTS
(2) IP-VDSL
(3) Ethernet
(4) Leased lines
1.1.1 Applied Network Configurations
TAM can be applied for the following purposes:
1) To replace the local exchange in CO and remote COs
2) To accommodate voice subscribers in apartment complexes and business buildings
3) To accommodate VDSL subscribers in the areas near the CO area
4) To replace VDSL subscribers in apartment complexes and business buildings
5) To accommodate Ethernet subscribers in the areas near the CO area
6) To accommodate Ethernet subscribers in apartment complexes and business buildings
1.1.2 Elements to Configure Application Network
The applied network is configured with the following network elements.
PAGE : 1-2 SM0-000-S00050(V1.0)

TAM-HS
Installed in CO, TAM-HS accommodates both voice and data subscribers near the CO. As designed to
accommodate numbers of TAM-CS1000s (RS Mode) as remote systems, TAM-HS can accommodate
remote subscribers.
TAM-CS1000 (Host Mode)
Installed in various locations such as CO/remote CO/APT/business building, TAM-CS1000 (Host

Mode) accommodates both voice and data subscribers. As designed to accommodate numbers of TAM-
CS1000s (RS Mode) as remote systems, TAM-CS1000 can accommodate remote subscribers
seamlessly. In order to control services, it interworks with the Local Exchange or Softswitch. When
installed outdoors, TAM-CS1000 (Host Mode) should be installed in an outdoor housing that meets the
environmental conditions of the outdoor.
TAM-CS1000 (RS Mode)
Installed in various locations such as remote CO/APT/business buiding as a remote system of TAM-
HS or TAM-CS1000 (Host Mode), TAM-CS1000 (RS Mode) accommodates both voice and data
subscribers. In order to control the system services, it interworks with the LE or Softswitch via the
TAM-HS or the TAM-CS1000 (Host Mode).
When intalled outdoors, the TAM-CS1000 (RS Mode) should be installed in an outdoor housing that
meets the environmental conditions of the outdoor.
Local Exchange (LE)
In the Pre-NGN phase, the LE provides call services for the subscribers accommodated in TAM, in
interworking with the TAM-CS1000 (Host Mode). For this, it is connected to TAM-CS1000 (Host
Mode) via E1 physical interface. Signaling between these systems is performed according to V5.2
protocol. Consisting of LAPV5 in Layer 2, and PSTN, Port Control, Link Control, and Protection
protocols in Layer 3, the V5.2 protocol performs call connection and disconnection and transfers voice
traffic to the defined bearer channel. Besides, it also transfers voice traffic among subscribers in a
reverse direction, according to the same procedure.
Softswitch
In the NGN phase, Softswitch provides call services to the subscribers accommodated in TAM, in
interworking with TAM-CS1000 (Host Mode). For this, TAM-CS1000 (Host Mode) and Softswitch
are connected via the physical interface by 10/100Base-T Ethernet. Signaling between them is
performed by open protocol “MEGACO”.
Element Management System (EMS)
The EMS is a centralized management system for TAM-CS1000 with which it is connected via the
physical interface of 10/100Base-T Ethernet. TAM-CS1000 (RS Mode) is not connected directly to the
EMS but it is still managed by the MS through the interworking with TAM-CS1000 (Host Mode).
SM0-000-S00050(V1.0)
PAGE : 1-3
1.1.3 Network Configurations
1) For replacing the LE
2) For accommodating VDSL subscribers
- Near the CO area

- In remote areas
3) Accommodating Ethernet subscribers
- Near the CO area

- In remote areas
PSTN
Softswitch Class5
switch
H.248/Megaco E1/V5.2 E1/V5.2

IP Network
10/100BT/FX 10/100BT/FX
TAM-HS
Residential TAM-CS1000(Host)
TAM-CS1000(RS)
POTS STM-1/E1
POTS
Residential
Office /
Apartment
POTS Office /
Apartment
TAM-CS1000
[Figure 1-1] Network Configuration for Replacing the LE
PAGE : 1-4 SM0-000-S00050(V1.0)

PSTN
Softswitch Class5
switch
H.248/Megaco E1/V5.2
IP Network
GbE
GbE
TAM-HS
Residential GbE
TAM-CS1000(Host)
TAM-CS1000(RS)
POTS STM-1/E1
POTS
xDSL Residential
VDSL
Office /
Apartment
POTS Office /
Apartment
TAM-CS1000(RS) VDSL
[Figure 1-2] VDSL subscriber
SM0-000-S00050(V1.0)
PAGE : 1-5
Softswitch
H.248/Megaco
IP Network
GbE
GbE
TAM-HS GbE
Residential
TAM-CS1000(Host)
TAM-CS1000(RS)
STM-1/E1
Ethernet
Ethernet Residential
Ethernet
Office /
Apartment
Office /
Ethernet
Apartment
TAM-CS1000
[Figure 1-3] Network Configuration for Accommodating Ethernet Subscribers
PAGE : 1-6 SM0-000-S00050(V1.0)

1.2 System Specifications
1.2.1 TAM-CS1000 (Host Mode)
Specification Capacity Remarks
POTS Max. 1,024

Subscriber
VDSL Max. 256 IP VDSL
Ethernet Max. 168 100Base-T, 100FX
Gigabit Ethernet 4 Data & VoIP Traffic
100Base-T
Network Interface Ethernet 1 VoIP traffic only
1+1 redundancy
E1 8 PSTN interworking
Capacity 4 TAM-CS1000 (RS Mode)
Remote System
Capacity STM-1 2
E1 16
Voice CODEC G.711,723.1, 729a/b 256 Channel
Indoor Housing Provided

Outdoor Housing Provided
Softswitch Interworking 1 10/100Base-T 1+1 redundancy
EMS Interworking 1 10/100Base-T 1+1 redundancy
1.2.2 TAM-CS1000 (RS Mode)
Specification Capacity Remarks

POTS Max. 1,024
Subscriber VDSL Max. 256 IP VDSL
Ethernet Max. 168 100Base-T, 100FX
Network Interface Gigabit Ethernet 4 Data & VoIP traffic
STM-1 2
TAM-CS1000(Host
Mode) Interworking
E1 16
Indoor Housing Provided

Outdoor Housing Provided
SM0-000-S00050(V1.0)
PAGE : 1-7
1.3 Housing
The TAM housing has a mechanical block structure, so that it can be easily applied to various purposes.
It consists of a small number of as simplified standard structures as possible. It is designed to endure
all allowable environmental conditions, and manufactured with well-known materials through the
proven process.
System Height (mm) Width (mm) Depth (mm)

Indoor Housing 1040 750 696
TAM-CS1000
Outdoor Housing 1800 1340 850
1.3.1 TAM-CS1000 (Host & RS Mode)
1) Indoor Housing
▶ Height: 1,040 mm
▶ Width: 750 mm
▶ Depth: 696 mm
[Figure 1-7] TAM-CS1000 Indoor Housing– Front and Rear Views
PAGE : 1-8 SM0-000-S00050(V1.0)

[Figure 1-8] TAM-CS1000 Indoor Housing – Side View
[Figure 1-9] TAM-CS1000 Indoor Housing – Top View
SM0-000-S00050(V1.0)
PAGE : 1-9
2) Outdoor Housing
▶ Height: 1,800 mm
▶ Width: 1,340 mm
▶ Depth: 650 mm
1340
1800
[Figure 1-10] TAM-CS1000 Outdoor Housing
PAGE : 1-10 SM0-000-S00050(V1.0)

1.4 Power
Warning
May result in system damage or a fire.

Use the rated power sources specified in the system manual.
1) Power source for the system installed in the CO
Interworking with the power supplies in the CO
DC-48V DC-48V
AC Distribution Power
Panel Rectifier DC Control Distribution
Panel / Closet
Distribution
Circuit /
Automatic
Charger
DC-48V
Story Battery System
[Figure 1-11] In-Office Power Supply Configuration
System power
- For system power supplied to TAM, -48V for communication is used.
Card power
- For cards, an independent power supply system by on-board power source is used.
SM0-000-S00050(V1.0)
PAGE : 1-11
2) Power source for the system installed outside the CO
System
Shelf
Rectifier
AC Distribution Panel
Storage
Battery
[Figure 1-12] Out-of-Office Power Supply Configuration
System power
- For system power supplied to TAM, commercial 220V is used.
Card
- For cards, an independent power supply system by on-board power source is used.
-The power source used in the cards is selected according to each card type.
PAGE : 1-12 SM0-000-S00050(V1.0)

Chapter 2 TAM Architecture and Configuration
Chapter 2. TAM Architecture and Configuration
1. System and Hardware Architecture

TAM is classified into TAM-CS1000 (Host Mode) and TAM-CS1000 (RS Mode) depending on system
capacity and application network. Depending on the functions provided by the system, it is divided
into control part, VoIP CODEC part, subscriber parts (POTS subscriber part, VDSL subscriber part,
and Ethernet subscriber part), and network interworking parts (PSTN interworking part, IP switch and
packet network interworking part).
Overall system configuration diagram of each system is shown below.
1) TAM-CS1000 (Host Mode) Architecture
IP
RS RS Network LE
IP Sw itch
RS POTS VDSL Ethernet & Packet PSTN
VoIP Sub Sub
Inter Subs Netw ork Inter
CODEC
working criber scriber scriber Inter working
Part
Part Part Part Part working Part
Part
Control Part
Softswitch EMS
[Figure 2-1] TAM-CS1000 (Host Mode) General Architecture
SM0-000-S00050(V1.0)
PAGE : 2-1
2) TAM-CS1000 (Remote Mode)
IP
Host Network
IP Switch
&
Host System POTS VDSL Ethernet
Packet
Interworking Subscriber Subscriber Subscriber
Network
Part Part Part Part
Interworking
Part
Control Part
[Figure 2-2] TAM-CS1000 (RS Mode) General Architecture
PAGE : 2-2 SM0-000-S00050(V1.0)

1.1 TAM-CS Configuration

TAM-CS1000 is configured with the following logical modules.
System Control Module:
Performs general operation and management functions of TAM-CS1000
IP Switch Module:
Provides the Ethernet interface in compliance with IEEE802.3 standard for the IP network interface.
PSTN Interface Module:
In independently interworking with the LE, PSTM interface module is provided with call processing
and service functions by the LE. As a module for providing voice call service to the subscribers of the
LE, it provides the standardized protocol such as E1 physical interface and V5.2 interface.
VoIP CODEC Module:
Compresses PCM voice data and converts it into packet data, or provide voice packet data to PCM.
Voice Traffic Control Module:
Provides voice traffic control among devices and provides clock synchronization function.
Synchronization Module:
Provides clock synchronization function.
POTS Subscriber Module:
Accommodates POTS subscribers.
VDSL/Ethernet Subscriber Module:
Accommodates data subscribers (VDSL, Ethernet).
Remote System Interface Module:
Accommodates remote systems.
SM0-000-S00050(V1.0)
PAGE : 2-3
Host System Interface Module:
Acts as RS in interworking with the host system.
Softswitch Interworking Module
Provides gateway control and call services in interworking with Softswitch.
EMS Interworking Module:
Interworks with ESM to provide the EMS services.
PAGE : 2-4 SM0-000-S00050(V1.0)

1.1.1 Interface
1) TAM-CS1000 (Host Mode) provides the interface with the following objects of interworking.
Object of
Physical Interface Applied Protocol Remarks
Interworking
POTS subscriber Twisted Pair
VDSL subscriber Twisted Pair
Ethernet subscriber 100Base-T/FX TCP/IP
10/100Base-T/FX RTP/RTCP VoIP

IP Network
- Router/Switch
1000Base-T/FX TCP/IP, RTP/RTCP VDSL/ Ethernet VoIP
Local Exchange E1 V5.2
Remote System
- TAMCS1000 E1, STM-1 LGE Proprietary
(RS Mode)
H.248
Softswitch 10/100 BT
Megaco
Management System
10/100 BT SNMPv2
- EMS
2) TAM-CS1000 (RS Mode) provides the interface with the following objects of interworking.
Object of
Physical Interface Applied Protocol Remarks
Interworking
POTS subscriber RJ-11
VDSL subscriber RJ-11
Ethernet subscriber 100Base-T/FX TCP/IP
IP Network 10/100Base-T RTP/RTCP VoIP

- Router/Switch
1000Base-T/FX TCP/IP, RTP/RTCP VDSL/ Ethernet VoIP
Host System
- TAM-HS
E1, STM-1 LGE Proprietary
- TAMCS1000
(Host Mode)
SM0-000-S00050(V1.0)
PAGE : 2-5
1.1.2 Configuration
1) Indoor-type rack
PDP
OFD
FAN
Cable Shelf
System Function Card
Rectifier, Ring
Battery
[Figure 2-3] Indoor-type Rack

2) Outdoor-type rack
FAN
Heat Exchanger
PDP
MDF
OFD
Rectifier, Ring
Battery
[Figure 2-4] Outdoor-type Rack
PAGE : 2-6 SM0-000-S00050(V1.0)

3) Front – rear architecture
Rear Card
Cable
Backboard
Front Card
Rear Shelf Side
[Figure 2-5] Front-Rear Architecture
3) Shelf configuration by subscriber types
V V
P P
I I M M b b S b P P P P P P P P P P P P P P P P
C C C C l l T l O O O O O O O O O O O O O O O O
/ / M M a a C a T T T T T T T T T T T T T T T T
I I C C n n C n C C C C C C C C C C C C C C C C
N N k k k
V V
C C
Subscriber Test POTS Subscribers
Processor/EMS Interworking
Network Interface : INVC (for VoIP), VPIC (for V5.2)
[Figure 2-6] POTS Only
SM0-000-S00050(V1.0)
PAGE : 2-7
b b M M b b b G V V V V V V V V V V V V V V V V
l l C C l l l S S S S S S S S S S S S S S S S S
a a M M a a a P L L L L L L L L L L L L L L L L
n n C C n n n C C C C C C C C C C C C C C C C C
k k k k k
Gigabit L3 Switch
VDSL Subscribers
[Figure 2-7] VDSL Only
b b M M b b b G b b E E E E E E E
l l C C l l l S l l S S S S S S S
a a M M a a a P a a I I I I I I I
n n C C n n n C n n C C C C C C C
k k k k k k k
Gigabit L3 Switch
Ethernet Subscribers
[Figure 2-8] Ethernet Only
PAGE : 2-8 SM0-000-S00050(V1.0)

b b M M b b S G P P P P E E P P P P V V V V
l l C C l l T S O O O O S S O O O O S S S S
a a M M a a C P T T T T I I T T T T L L L L
n n C C n n C C C C C C C C C C C C C C C C
k k k k
Gigabit L3 Switch
Subscriber Test POTS Subscribers,
Ethernet Subscribers &
VDSL Subscribers
[Figure 2-9] POTS + VDSL + Ethernet
V V S S
P P I I
I I C C
M M C C S b P P P P P P P P P P P P P P P P
C C C C / / T l O O O O O O O O O O O O O O O O
/ / M M E E C a T T T T T T T T T T T T T T T T
I I C C P P C n C C C C C C C C C C C C C C C C
N N k
V V I I
C C C C
Gigabit L3 Switch
Subscriber Test POTS Subscribers,
Ethernet Subscribers
RS Interworking
& VDSL Subscribers
(SICC for STM-1, EPIC for E1)
Network Interface : INVC (for VoIP), VPIC (for V5.2)
[Figure 2-10] Host Mode (Accommodating Remote System)
SM0-000-S00050(V1.0)
PAGE : 2-9
S S
I I
C C
C C M M b b S b P P P P P P P P P P P P P P P P
/ / C C l l T l O O O O O O O O O O O O O O O O
E E M M a a C a T T T T T T T T T T T T T T T T
P P C C n n C n C C C C C C C C C C C C C C C C
I I k k k
C C
Subscriber Test POTS Subscribers
Processor/ EMS Interworking

Host Interworking (SICC for STM-1, EPIC for E1)
[Figure 2-11] Remote Mode
4) Card
265 mm
Front Card Rear Card
280 mm 150
mm
PAGE : 2-10 SM0-000-S00050(V1.0)

Stiffener
Solder Side Part Side
Connector
Back Board
Connector
Solder Side Part Side
Stiffener
[Figure 2-12] Front / Read Card Configuration
1.1.3 Hardware Capacity
1) Subscriber capacity
Subscriber Type Capacity

POTS Subscribers Maximum 1,024 Consists of 16 POTCs.
VDSL Subscribers Maximum 256 Consists of 16 VSLCs.
Ethernet Subscribers Maximum 168 Consists of 7 ESICs.
2) Remote System (RS) capacity
▶ Maximum 4 RSs
SM0-000-S00050(V1.0)
PAGE : 2-11
3) Per PBA capacity
Card Name Capacity Remarks
Supports VoIP services such as

- 256 Vocoder channels G.711/G.723.1 and G.729a/b CODEC.
INVC
- 1 100Base-T Provides IP network interface.
Provides redundancy.
Supports interworking with LE in the pre-

VPIC - 8 E1 lines NGN.
Provides redundancy.
POTC - 64 POTS lines Accommodates POTS subscribers.
VSLC - 16 VDSL lines Accommodates IP-VDSL subscribers.
ESIC - 24 Ethernet lines Accommodates Ethernet subscribers.
PAGE : 2-12 SM0-000-S00050(V1.0)

1.2 Hardware Architecture
1.2.1 TAM-CS1000 (Host Mode)
Soft
EMS
switch
Sub
Test
scriber
Test
(STCC)
Part
POTS Control PSTN

Sub & Inter E1
scriber Common working
LE
Part Part Part
STM-1 RS
E1 VoIP
RS Inter CODEC
working 10/100BT
Part
Part
IP
Data
IP GbE Network
Sub
Sw itch
scriber
Part
Part
[Figure 2-13] TAM-CS1000 (Host Mode) Architecture
Control and Common Part
(1) Function
The control and common part provides control, statistics, device card control, and alarm collection
functions for call processing and maintenance of the entire system.
(2) Configuration
Card Remarks
Front Card MCMC Active/standby duplication
Daughter Card SCTM POTS subscriber control
Rear Card MCRC Active/standby duplication
SM0-000-S00050(V1.0)
PAGE : 2-13
(3) Structure
LA-Bus
100BT Soft
POTC IPC switch
MCMC
SCTM MCMC
HT-Bus
SICC/EPIC 100BT
IPC
EMS
STCC
HT-Bus IPC IPC
GSPC
INVC VSLC
ESIC
[Figure 2-14] Control Part Interworking Diagram
(4) Implementation
TAM-CS1000 configures MCMC duplicated into Active and Standby sides per system, using
Concurrent Write mode.
The MCMC uses Motorola MPC PowerPC for processor.
It adopts EROS, LG’s proprietary OS.
In order to prevent slips that may occur due to discrepancy of clock frequencies between
switching systems in the digital switching network, the MCMC interworks with the following
cards to receive reference clock and generates and distributes clock synchronized to the
reference clock.
- VPIC (V5.2)
- EPIC (E1) or SICC (STM-1)
* When external reference clock is not received, the MCMC generates and distributes clock by
its own oscillator.
PAGE : 2-14 SM0-000-S00050(V1.0)

With the addition of the daughter card SCTM, the MCMC can perform service control for
voice calls, providing the following buses.
- LA (Local Access)-bus
- HT (High Traffic)-bus
The MCMC provides Inter-Processor Communication (IPC) channels for communication with
other function cards in the system.
It provides the duplicated 10/100Base-T interface for interworking between the system and
Softswitch.
It also provides the duplicated 10/100Base-T interface for interworking between the system
and EMS.
The MCMC collects maximum 96 metallic alarms from the cards inserted to the system.
IP Switch Part
(1) Function
The IP switch part provides traffic switching function and interworking with external IP
networks.
It supports switching (L2/L3) of traffic from VDSL and Ethernet subscriber cards, and
interworks with these subscriber cards via Giga interface.
It also provides the gateway function for IPC with MCMC, and VDSL and Ethernet subscriber
cards.
(2) Configuration
Card Remarks
Front Card GSPC Provides L3 switch function.
Rear Card GSRC
SM0-000-S00050(V1.0)
PAGE : 2-15
(3) Structure
MCMC
IPC
Giga
VSLC
1000BT/FX IP
GSPC
Network
Giga
ESIC
[Figure 2-15] IP Switch Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates one GSPC per system.

The GSPC is controlled by its internal processor.
The GSPC consists of the following 5 parts:
Giga Switch
- L2/L3 Giga Switch : 16 ports
- Supports wire-speed L2 switching and L3 routing.
- 128Kbyte internal packet buffer
- Supports 4K VLAN according to port and subnet: IEEE802.1Q
- Supports link aggregation (IEEE802.3ad)
Uplink interface
- Provides 4 GbEs - 1000Base-LX
Ethernet-bus interface
- Provides maximum 18 ports, and accommodates 1000Base-T and100Base-TX standards.
IPC interface
- Provides IPC channel with MCMC.
- MII I/F: Accommodates 100Base-TX specification.
- Provided duplicated IPC channels.
PAGE : 2-16 SM0-000-S00050(V1.0)

Control & alarm interface

- PBA hardware reset by software
- Uplink related control
- Collects alarms inside and outside the card.
POTS Subscriber Part
(1) Function
The POTS subscriber part provides Battery feeding, Over-voltage protection, Ringing,
Supervision, Coder/decoder, Hybrid, Test access (BORSCHT) functions for analog subscribers,
and connects terminals that use voice band signals.
Applicable standards
Environmental conditions of the subscriber line, and subscriber specification: Telephone

Standards by the Ministry of Information and Communication, and the Regulations on
Technical Standards of Telecommunication Equipment.
- Analog Subscriber Line Transmission Characteristic : ITU-T Q.552
- Over-voltage/Over-current Protection : ITU-T K.17, K.20
- Service Aspects : ITU-T I.200 series
- Network Aspects : ITU-T I.300 series
- Internetwork Interface : ITU-T I.500 series
(2) Configuration
Card Remarks
Accommodates 64 subscribers per card.
Front Card POTC
Maximum 16 cards are inserted to the system.
SM0-000-S00050(V1.0)
PAGE : 2-17
(3) Structure
MCMC
LA-Bus
Test-Bus
☎ STCC
☎
☎
☎
☎ POTC
☎
Ring, ZC
64 GRSC
[Figure 2-16] POTS subscriber Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates 16 POTC subscriber cards per system, to accommodate

maximum 1,024 POTS subscribers.
The POTC subscriber card is controlled by MCMC.
It interworks with the MCMC in order to transmit/send PCM signals.
It also interworks with STCC via the test-bus, in order to perform subscriber test (line and
circuit test).
It also interworks with GRSC in order to provide 20 Hz ring signal for the terminating
subscriber during call processing.
PAGE : 2-18 SM0-000-S00050(V1.0)

Subscriber Test Part
(1) Function
The subscriber test part tests analog subscriber lines and circuits and manages their status.
STCC, which configures the subscriber test part, receives the test command from the high-level
processor, tests the corresponding subscriber line, and sends the test result to the processor, so
that the system can perform maintenance for analog subscriber lines and circuits. It performs the
following tests:
Subscriber line test:
The STCC Measures AC voltage, DC voltage, resistance and capacitance for each of T-R
(Tip-Ring), T-G (Tip-Ground) and R-G (Ring-Ground) – It tests the subscriber lines outside
the system in the same condition as the connection between the analog subscribers and the
system is disconnected.
- External voltage (AC and DC)
- Loop resistance
- Insulation
- Capacitance
Subscriber circuit test:
The subscriber test part provides the following test functions for POTS subscriber interface
circuits:
- Loop current measurement
- Dial Tone (DT) measurement and Dial Tone Disconnection (DTD) detection
- Ringing measurement and Ring Trip (RT) detection
- Polarity Reveal (PR) detection
- Transmission Loss (TL) measurement
(2) Configuration
Card Remarks
Front Card STCC
SM0-000-S00050(V1.0)
PAGE : 2-19
(3) Structure
MCMC
IPC HT-Bus
Test-Bus
POTC
STCC
[Figure 2-17] Subscriber Test Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates one STCC per system, to test the entire subscribers
accommodated in the system.
The STCC is controlled by MCMC.
VoIP CODEC Part
(1) Function
The VoIP CODEC part provides the following functions to support VoIP services:
▶ G.711, G.723.1, G.729a/b CODEC
▶ CODEC translation
▶ DTMF detection
▶ Echo cancellation
▶ Announcement
PAGE : 2-20 SM0-000-S00050(V1.0)

(2) Configuration
Card Remarks
Front Card INVC
(3) Structure
MCMC
IPC HT-Bus
10/100BT IP
Network
MCMC
INVC
10/100BT
GSPC
[Figure 2-18] VoIP CODEC Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates two INVCs (when duplicated), to provide VoIP services for the
entire POTC subscriber cards accommodated in the system.
The INVC provides the duplicated 10/100Base-T ports to interwork with the IP network.
SM0-000-S00050(V1.0)
PAGE : 2-21
PSTN Interworking Part
(1) Function
The PSTN interworking part provides the following functions to interwork with PSTN LE:
▶ V5.2 protocol handling
▶ E1 interface function
▶ DOTS link receive function
(2) Configuration
Card Remarks
Front Card VPIC
Rear Card V5RC
(3) Structure
MCMC
IPC HT- Reference Clock

Bus
2E1 MCMC 8E1

VPIC PSTN
DOTS
LE
[Figure 2-19] PSTN Interworking Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates two VPICs (when duplicated), to interwork with PSTN LE.
Each VPIC provides 8 E1 interfaces.
PAGE : 2-22 SM0-000-S00050(V1.0)

VDSL Subscriber Part
(1) Function
Main function of the VDSL subscriber part is to accommodate VDSL subscribers. It also
provides the following functions:
▶ Provides 16 channel VDSL subscriber downlinks.
▶ 4-band QAM mode modulation
▶ Provides uplinks for the IP network interface.
(2) Configuration
Card Remarks
Accommodates 16 subscribers per card.
Front Card VSLC
Maximum 16 cards are inserted to each system.
(3) Structure
MCMC
IPC
Copper Line
Giga
VSLC GSPC
16
[Figure 2-20] VDSL subscriber Part Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-23
(4) Implementation
TAM-CS1000 accommodates 16 VSLCs, to accommodate maximum 256 VSDL subscribers.
The VSLC interworks with GSPC via 1Gbps interface, and the GSPC multiplexes the traffic
from multiple VSLCs.
The VSLC consists of the following 6 logics:
Switching logic consists of switching chip, flash memory, and SDRAM.
FPGA logic provides DHCP filtering and NetBios filtering function for 8 ports per chip.
VDSL logic consists of PoVDSL-D, PoVDSL-A, line driver, and filter logic per port, and
provides 16 ports.
Uplink logic provides 1000Base-X1 port for GMII interface.
Power logic provides power-related functions such as input voltage (-48V) and output voltage
(12V, 3.3V, 2.5V, and 1.8V).
User interface logic provides processor control and monitoring inside the switching chip
through an external terminal.
Ethernet Subscriber Part
(1) Function
Main function of the Ethernet subscriber part is to accommodate Ethernet subscribers. It also
provides the following functions:
▶ Provides 24 channel Ethernet subscriber downlinks. – 100Base-T or FX
▶ Provides the uplink for IP network interface.
▶ L2 and L3 switching
(2) Configuration
Card Remarks
Front Card ESIC Accommodates 24 subscribers per card.
Rear Card ESRC
PAGE : 2-24 SM0-000-S00050(V1.0)

(3) Structure
MCMC
IPC
100BT/FX
GbE IP
Network
ESIC
Giga
7 GSPC
[Figure 2-21] Ethernet Subscriber Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates maximum 168 Ethernet Subscriber Interface Cards (ESICs) per
system.
The ESIC interworks with the IP network by
- Providing 2GbE on its own, or
- Interworking with GSPC via 1Gbps interface, and letting the GSPC multiplexing the traffic
from multiple ESICs.
The ESIC is configured with the following five parts:
Control
- Main processor :MPC8260
- Memory : RAM & ROM
SM0-000-S00050(V1.0)
PAGE : 2-25
L2/L3 switch
- L2/L3 Ethernet switch : 24 FE ports + 4 GE ports
- Supports wire-speed L2 switching and L3 routing.
- 128Kbyte internal packet buffer
-Supports 4K VLAN depending on port or subnet: IEEE802.1Q
- Link aggregation support IEEE802.3ad
- Full duplex 1000Mbps
- Full and half duplex 10/100Mbps
Subscriber line interface
- RGMII I/F: 4 ports (1000Base-T 2 ports, Giga SFP 2 ports)
- Interface with the rear card: 100Base-T, 100Base-Fx 12 ports/24 ports
- RGMII I/F: Accommodates maximum 4 ports , Gigabit Ethernet.
- MII only I/F: 24 ports, accommodating 100Base-TX/FX standards
- External communication mode through the front card: 3 ports
IPC interface
- Supports inband communication mode using the communication via GSPC.
- Support 100Base-T mode through outband.
Control & alarm interface
- PBA hardware reset by software
- Uplink control
- Collects alarms inside and outside the card.
PAGE : 2-26 SM0-000-S00050(V1.0)

1.2.2 TAM-CS1000 (RS Mode)
Sub
scriber
Test
(STCC)
Test
Part
POTS Control
Sub &
scriber Common
Part Part
Host STM-1/
System E1 Host
Interworking System
Part
Data
IP
Sub
Sw itch
GbE IP
scriber Network
Part
Part
[Figure 2-22] TAM-CS1000 (RS Mode) Architecture
Host System Inteworking Part
(1) Function
The host system interworking part provides the following functions to interwork with the host
system (TAM-CS1000 (Host Mode), TAM-HS)):
▶ STM-1 or E1 interface
▶ IPC between the host and the remote.
(2) Configuration
Card Remarks
SICC or SICC is provided as

Front Card
EPIC duplicated.
EPRC for EPIC
Rear Card
LIRC for leased line
SM0-000-S00050(V1.0)
PAGE : 2-27
(3) Structure
MCMC
IPC HT-Bus
STM-1 or
SICC or E1
Host
EPIC System
[Figure 2-23] Host System Interworking Part Interworking Diagram
(4) Implementation
TAM-CS1000 accommodates the followings per system to interwork with the host system (TAM-
CS1000 (Host Mode)):
- 2 SICCs (1+1 APS duplication, providing 2 STM-1s per card), or
- 2 EPICs (providing 8 E1s per card)
Control and Common Part

See “Control and Common Part” in Item 1.2.1.
IP Switch Part
See “IP Switch Part” in Item 1.2.1.
POTS Subscriber Part

See “POTS Subscriber Part” in Item 1.2.1.
PAGE : 2-28 SM0-000-S00050(V1.0)

Subscriber Test Part

See “Subscriber Test Part” in Item 1.2.1.
VDSL Subscriber Part

See “VDSL Subscriber Part” in Item 1.2.1.
Ethernet Subscriber Part

See “Ethernet Subscriber Part” in Item 1.2.1.
SM0-000-S00050(V1.0)
PAGE : 2-29
2. Software Configuration
2.1 Overview
TAM software is configured with call control, operation and management, and maintenance functions,
and its configuration diagram is shown below.
Call Control
V5.2 Connection
PSTN Control
Control
Softswitch V5.2
Interface Configuration
Control
Data Service
Data Link Control
Control
Maintenance Operation & Management

Configuration Start/Restart/
Audit TMS
Control Loading
Resource
Overload TAM Agent MMI
Management
Fault System Duplication

Data Processing
Management Synchronization Control
Clock
Statistics
Management
[Figure 2-24] TAM Software Configuration Diagram
PAGE : 2-30 SM0-000-S00050(V1.0)

2.2 Call Processing Functions
2.2.1 PSTN Control
For PSTN control, PSTN call processing between LE subscribers and TAM-CS1000 (Host Mode)
subscribers through V5.2 interface and call processing between TAM-CS1000 (Host Mode) and TAM-
CS1000 (RS Mode) through STM-1/E1 interface are performed by PSH and VPC blocks. The PSTN
control part receives the subscriber status change report from the control processor, forms it into a
message in interworking with V5.2 protocol handling part and sends the message to LE, to establish a
call.
For subscribers allocated to TAM-CS1000 (RS Mode), the host system interworking part is added
between the subscriber and LE. Other than that, as the call processing between the LE and TAM-
CS1000 (Host Mode) is the same, basic status report messages and types are also the same as those for
the subscribers allocated to TAM-CS1000 (Host Mode).
For subscriber control TAM-CS1000 (Host Mode) uses Public Switched Telephone Network (PSTN)
protocol among those provided as V5.2 protocol. Without getting involved in call control, TAM-
CS1000 (Host Mode) sends analog line status information to LE over V5.2 interface, and the LE
controls the calls of the connected subscriber lines. Most line signaling is not interpreted by PSTN
protocol but transparently transferred and processed directly between the subscriber port of TAM-
CS1000 (Host Mode) and LE. The LE performs general call control functions, which include
transmitting/receiving Dual Tone Multi Frequency (DTMF), tone generation and announcement, while
TAM processes connection-related parameters such as analog signal recognition time and period,
meter pulse voltage and frequency, ring current, and detailed processing of signaling sequence.
To provide call processing for analog subscribers, TAM requires a procedure to allocate channels for
V5.2 interface, for which it uses Bearer Channel Connection (BCC) protocol provided by V5.2
protocol. Most other functions including number translation, routing, and speech path setup are
handled by LE.
PSTN control function is performed by PSH and VPC blocks. Overall call processing flow and the
functions of each block are illustrated in the following figure.
SM0-000-S00050(V1.0)
PAGE : 2-31
PSH Handling Flow
SCTM PSH Status Change VPC

Hook_off
Report
Hook_on Changed from Physical Line to Logical Line
Hook_flash
CdDgtRP
SCTM PSH VPC

Ring Connection/ Ring Connection/
Disconnection Request Disconnection Request
VPC Handling Flow
PSH VPC LE
Transmit
Hook_off Changed from Physical Line to Logical Line
Hook_on
Get interface/port number.
Hook_flash
V5.2 Protocol Handling
PSH VPC LE
[Figure 2-25] PSTN Control Function Flow
PSH block
The PSH block is a software block built in MP processor of TAM-CS1000 (Host Mode), which
performs call control through direct communication between VPC and the processor. Subscriber
Control Time-switch Module (SCTM) hardware block scans TAM-CS1000 (RS Mode) subscribers
and when the subscriber status changes (Hook-on -> Hook-off), it sends the status change report to
PSH block. When receiving the hook-off report, the PSH block also receives the corresponding
subscriber’s physical line number. It translates the physical line number into a logical line number
and sends it to the call control interworking block, to inform that the subscriber hooked off.
VPC block
The VPC block manages POTS subscribers’ LNs and interface and port numbers for the LNs. It also
performs mapping between the provisioned subscriber information provided by V5.2 and the control
numbers at TAM. It performs V5.2 protocol processing for Hook_off, Hook_on and Hook_flash
messages from POTS subscribers and reports them to LE, as a means of call control. When receiving
the ring connection or disconnection request with ‘Establish’ message or signaling message, the VPC
block transfers the request to the PSH block, to connect or disconnect the ring.
PAGE : 2-32 SM0-000-S00050(V1.0)

V5.2
Process
LSL
VPC Local
Exchange
FSL
PSH FSH
[Figure 2-26] VPC Block Interworking Diagram
2.2.2 Softswitch Interface Function
Softswitch interface function is a module that handles protocol and messages for Softswitch
interworking, and the related services, which includes call control according to H.248/Megaco
protocol.
H.248/Megaco protocol is the standard control protocol between access gateway and Softswitch, to
control basic call connection and perform supplementary service function for voice subscribers in
NGN, which operates above IP and UDP.
The Softswitch interface function is performed by LMCC block.
LMCC block
The LMCC block performs call connection control functions, such as reporting the message received
from the voice subscriber control card to Softswitch and connecting resources or transferring
messages to the control card depending on the call control information received from Softswitch.
In addition, the LMCC block analyzes the command received from Softswitch, or converts the call
control message into Megaco protocol and sends it to Softswitch.
SM0-000-S00050(V1.0)
PAGE : 2-33
Device
PSH
Library
Relation
FSL
PLD LMCC
LSL
[Figure 2-27] LMCC Block Interworking Diagram
2.2.3 V5.2 Connection Control
TAM subscribers consist of local subscribers directly connected to TAM-CS1000 (Host Mode) or
remote subscribers accommodated in TAM-CS1000 (RS Mode) and connected to TAM-CS1000 (Host
Mode) through STM-1s/E1.
For those directly connected to TAM-CS1000, the PHS block detects changes in the subscriber status,
performs proper protocol processing for the changes, and interfaces the subscribers to LE via V5.2. For
those accommodated in TAM-CS1000 (RS Mode) subscribers, the VPC receives the status change
report through E1/STM-1 and performs V5.2 connection control procedure.
Basic procedures for V5.2 connection control include subscriber connection/disconnection and bearer
channel allocation/deallocation procedures, which are controlled by the VPC block and V5.2 device.
VPC block
The VPC block is a software block equipped in MP of TAM-CS1000 (Host Mode), which processes
V5.2 protocol and performs V5.2 connection control interface with LE in interworking with the
directly connected POTS subscriber control block (PHS block).
The VPC block provides the interface with the RS interworking control part for the subscribers
connected to TAM-CS1000 (RS Mode) and the interface to control V5.2 connection with LE.
It supports management of FSM table set forth in V5.2 related standard, message encoding/decoding,
message sending/receiving, startup procedure, link status change, port status change, and call
processing . See [Figure 2-26].
PAGE : 2-34 SM0-000-S00050(V1.0)
V5.2 device functions
The V5.2 device provides the interface between the link card that processes Layer 2 of V5.2 protocol
and the VPC block that processes Layer 3. The VPI block monitors link card status, detects the status
change, and reports it to a higher level block. It provides the following main functions.
(1) Outgoing call establishment for the directly connected POTS subscribers
The PHS block activates call establishment with LE by the request to establish a call from the
PHS block. Mapping to V5.2 subscriber information is performed by the VPC block through EN
to LN mapping at the subscriber management table. If there is no V5.2 subscriber information to
be mapped, the V5.2 device initiates call disconnection procedure for the subscriber who has
requested the call establishment. If the subscriber information is valid, it performs the procedure
to establish the call to LE using the V5.2 connection control function. If ESTABLISH ACK
message is not received from the LE in response to ESTABLISH message, it retransmits
ESTABLISH message periodically according to the preset timer.
(2) Outgoing call establishment for the POST subscribers connected to TAM-CS1000 (RS Mode)
The V5.2 device activates call establishment with LE by the request to establish a call from the
TAM subscriber interworking control part. The TAM-CS1000 (RS Mode) subscriber information
is mapped to the V5.2 subscriber information in steps: First, the subscriber interworking control
part sends the call establishment request to the VPC block with the corresponding subscriber’s
LN, and the VPC block maps the V5.2 subscriber information to the LN. If there is no V5.2
subscriber information to be mapped, the V5.2 device initiates call disconnection procedure for
the subscriber who has requested the call establishment. If the subscriber information is valid, it
performs the procedure to establish the call to LE using the V5.2 connection control function. If
ESTABLISH ACK message is not received from the LE in response to ESTABLISH message, it
retransmits ESTABLISH message periodically according to the preset timer.
(3) Bearer channel allocation to the V5.2 originating party
The V5.2 device initiates the procedure to allocate bearer channels to LE for establishing the
speech path for the originating subscriber. It checks the bearer channel information received
from the LE, and sends only the valid bearer channel information to the resource control part.
When the received bearer channel information is not valid, it sends ALLOCATION REJECT
message to the LE.
(4) Bearer channel allocation to the V5.2 terminating party
In order to establish speech path for the terminating subscriber, the V5.2 device needs to perform
the bearer channel allocation procedure with LE. It checks the bearer channel information
received from the LE, and sends only the valid bearer channel information to the resource
control part. When the received bearer channel information is not valid, it sends ALLOCATION
REJECT message to the LE. When the bearer channel allocation to the terminating subscriber
fails, the call establishment request from the corresponding originating subscriber is released by
the LE.
SM0-000-S00050(V1.0)
PAGE : 2-35
(5) Call establishment for the V5.2 terminating party
When the bearer channel allocation procedure for the terminating subscriber is normally
completed, the call establishment procedure for the corresponding terminating subscriber is
initiated by LE. When the call establishment procedure for the terminating part is normally
completed, the speech path between the originating and the terminating subscribers is finally
connected.
(6) Call establishment completion
When hook-on signal is received from the originating or the terminating subscriber, the call
establishment completion procedure is initiated. The subscriber hook-on is detected by the
subscriber interworking control part and reported to the V5.2 connection control part. The V5.2
connection control part performs the call establishment completion procedure in interworking
with LE and also with the subscriber interworking control part.
(7) Audit procedure
When the bearer channel information contained in ALLOCATION/DEALLOCATION message

received from LE with regard to bearer channel allocation/de-allocation is not valid, the V5.2
device performs the audit procedure in order to prevent bearer channel status discrepancy with
the LE.
2.2.4 V5.2 Configuration Protocol Control
V5.2 configuration protocol control is an essential function provided for TAM-CS1000 to

communicate with LE via V5.2 interface. V5.2 configuration protocol consists of CONTROL protocol
for controlling the subscriber ports between TAM and LE and for managing the interface and variant
configuration, LINK CONTROL protocol for identifying and managing the V5.2 link status, and
PROTECTION protocol for protecting C-path upon abnormal status occurrence in V5.2 C-channel.
The V5.2 configuration protocol control function is performed by the VPC block.
Control protocol
This protocol is managed by the VPC block, which is divided into subscriber port status control and
general control functions. The subscriber port status control provides blocking/unblocking of certain
subscriber ports, while the general control function supports the procedure for identifying V5.2
interface IDs and variant IDs between TAM and LE, re-provisioning procedure, restart procedure for
PSTN protocol among V5.2 protocols, and ALL PORT UNBLOCK procedure for all subscribers.
Each function is detailed below.
PAGE : 2-36 SM0-000-S00050(V1.0)

(1) Subscriber port blocking command

Upon fault detection in a subscriber port or operator’s request, or according to VPC block’s own
judgement, the VPC block requests CONTORL protocol to block the certain subscriber port. The
subscriber blocking request can be made in both ways, TAM and LE. When the subscriber port
is blocked, LE releases the call being processed for the corresponding subscriber port.
(2) Subscriber port blocking request

Except for emergency, TAM can request LE to block a subscriber port. If it is not subscriber port
blocking in an emergency in the TAM VPC block’s judgment, the VPC block sends the
subscriber port blocking request to the LE. Upon receiving the request, the system management
part of the LE decides whether it is possible to block the subscriber port or not. According to the
decision, it sends the subscriber port blocking report or the subscriber port unblocking report to
TAM.
(3) Subscriber port unblocking

Upon error recovery of a subscriber port or on request of the operator, the VPC block can send
the port unblocking request to CONTROL protocol stack., to perform the subscriber port
unblocking procedure. Subscriber port unblocking requires both sides to coordinate. The
subscriber port unblocking request requires acknowledgement from the other side before the port
is actually unblocked. In order to ensure such coordination, the control function FSM blocks of
both sides have two types of port unblocking statuses (local/remote link unblocking). This
procedure is symmetrical to each other between TAM and LE.
(4) All port unblocking request

ALL PORT UNBLOCK request is used to accelerate the subscriber port alignment (unblocking)
between TAM and LE. When the VPC block sends this request to CONTROL protocol FSM,
and the CONTROL protocol FSM sends it to the remote office. This procedure can be initiated
both by TAM and LE. ALL PORT UNBLOCK request from the LE is sent to the VPC block,
where it may be accepted or rejected according to the VPC block’s decision. When accepting the
request from the LE, the VPC block should change the status of all subscriber ports allocated to
V5.2 interface to unblocking status. When it is impossible to unblock a subscriber port, the VPC
block sends the port unblocking request for the corresponding port to the LE, to unblock the port.
(5) Reprovisioning procedure

For V5.2 configuration management, TAM and LE should be synchronized with each other.
When V5.2 resource status changes during operation or by the operator’s request, the VPC block
can request the remote office for V5.2 configuration change. For configuration change,
CONTORL protocol provides the procedure required for synchronization between TAM and LE.
This procedure is classified into the procedure for identifying interface and variant IDs of the
current configuration, the procedure for checking the possibility of configuration change, and the
procedure for configuration change request. Reprovisioning can be requested by both TAM and
LE. During the reprovisioning procedure, all subscriber ports allocated to the interface are
blocked. The VPC block requests the remote office for the current interface and variant IDs
information, and check if there is any problem in the current configuration information. Then, it
sends new variant information to the remote office, to check if it is possible to change the
configuration information. The remote office may accept or reject the configuration change
request and if rejecting the request, it should specify the cause. When it is possible to change the
configuration, V5.2 interface configuration is changed according to the new variant information,
SM0-000-S00050(V1.0)
PAGE : 2-37
which should be followed by the port unblocking procedure for subscriber ports allocated to the
interface.
(6) PSTN restart procedure

When TAM or LE system management part decides that it is necessary to restart all POTS
subscriber ports, the LE can request to restart the POTS subscriber ports using CONTROL
protocol PSTN protocol FSM restarts the POTS subscriber ports. To restart the POTS subscriber
port, the VPC block interworks with the PSTN protocol FSM. When requesting to restart the
POTS subscriber ports, the VPC block change the status of all POTS subscribers allocated to
V5.2 interface to OUT-OF-SERVICE status and then requests the remote office to restart the
POTS subscriber ports. When the VPC block receives the restart completion message from the
PSTN protocol FSM, the POTS subscriber status is changed to NULL.
Link control
Link control protocol is managed by the VPC block, to identify and manage the status of V5.2 links
between TAM and LE. Upon error occurrence or recovery in a V5.2 link or on request of the operator,
the VPC block performs link block/unblock function, in order to ensure the stability of the V5.2 link
in conjunction with PROTECTION protocol. In addition, the VPC verifies link IDs between TAM
and LE through the V5.2 interface startup process or on request of the operator, in order to prevent
the link ID discrepancy between TAM and LE in the first place. The link control protocol provides
the following functions:
(1) Link blocking command
When L1 error is detected on both TAM and LE or on request of the operator, the VPC block can
block one or more links on V5.2 interface. The link blocking procedure is performed by the link
blocking command from TAM or LE. When the link blocking procedure starts, TAM sends the
link blocking command to the remote office according to LINK CONTROL FSM recommended
in ETS 347-1 and then manages the corresponding link status as blocked. If necessary, the link
blocking command is used for moving logical C-channel upon request of the LE according to
PROTECTION protocol.
(2) Link blocking request
Upon request of the operator, the VPC block can request LC to block links, separately as
delayable and as non-delayable. The link blocking procedure starts when the link blocking
request is sent to LE according to FSM defined in ETS 300 347-1 after the operator’s request is
transferred to LINK CONTROL protocol via the VPC block. After receiving the TAM
delayable/non-delayable link blocking request created by the operator, the LE releases bearer
channels on the corresponding link immediately for the non-delayable link blocking. For
delayable link blocking, it keeps unallocated bearer channels as released and waits until the
allocated bearer channels are released, and then sends the link blocking command to TAM.
PAGE : 2-38 SM0-000-S00050(V1.0)

(3) Link unblocking
When the VPC block sends the link block request to LINK CONTROL protocol stack upon L1
error recovery or by the operator’s request, the link unblocking procedure is performed.
Unblocking a link of V5.2 interface requires both sides to coordinate. The link unblocking
request requires acknowledgement from the other side before the link is actually unblocked. In
order to ensure such coordination, the control function FSM blocks of both sides have two types
of link unblocking statuses (local/remote link unblocking). This procedure is symmetrical to
each other between TAM and LE.
(4) Link identification procedure
When Layer 1 error is recovered, Layer 1 link FSM displays MPH-AI message and the message
is sent to the VPC block via LINK CONTROL protocol. Upon receiving this message, the VPC
block decides whether to or not to perform the link identification procedure. The link
identification procedure can be initiated even after reprovisioning, which also depends on the
VPC block’s decision. All V5.2 interfaces of TAM or LE perform only one link identification
request from the VPC block at a time. In order to avoid internal blocking condition caused by
identification of the link requested by both sides at the same time at the same point, the LE is
given the higher priority than TAM. Except the resolution of the link identification, continuing
procedure is described as if it is performed in only one side due to the symmetry between TAM
and LE. The link identification can be successfully started only when LINK CONTROL FSM is
in status 2.0 with MDU-IDReq. In other cases, the link identification request is rejected directly
or indirectly with the information about link control status.
Protection control
Protection control protocol is a function to manage C-channels established between TAM and LE. By
the operator’s request or when a data link error occurs on C-path, the VPC block performs the
switchover procedure for switching the C-path established in active C-channel over to standby C-
channel by blocking/unblocking V5.2 links. The protection control protocol provides the following
functions:
(1) Sequence number reset procedure
The sequence number reset procedure is a symmetric procedure started from an entity that
detects the alignment status of status variables. This procedure is initiated when at least one of
two data links for PROTECTION protocol is established at the time when the system starts. In
this case, the TAM VPC block or the LE VPC generates MDU-PROTECTION (reset sn req) for
the PROTECTION protocol entity, to request the sequence number reset procedure. The
procedure uses message RESET SN COM and RESET SN ACK, which do not include the
sequence number. When this procedure is successfully completed, the Tx status variable VP(S)
and the Rx status variable VP(R) are reset to 0.
SM0-000-S00050(V1.0)
PAGE : 2-39
(2) Switch-over request
When a fault is detected in TAM or when the operator initiates switchover through EMS, the
switchover request procedure is performed. When the switchover request is initiated by the
operator, the standby C-channel to be used is displayed on the EMS. At this time, SWITCH-
OVER REQ message can include the logical C-channel to be switched and the target standby C-
channel. When a standby C-channel is not included in the message, the LE selects a target
standby C-channel. For the switchover request from TAM, the LE decides whether to accept or
to reject the request. When rejecting the request, the LE should send CAUSE to TAM.
(3) (OS) Switch-over command
When LE requests TAM for switchover, the OS switchover procedure is performed. SWITCH-
OVER REQ message includes the logical C-channel to be switched and the target standby C-
channel. The TAM VPC block decides whether to accept or to reject the switchover request from
the LE. When rejecting the request, TAM should send CAUSE to the LE. However, for the OS
switchover command, TAM cannot reject the request because of the reason that the target
physical C-channel already has logical C-channel. Therefore, if the target standby C-channel for
the OS switchover command is active C-channel, the C-channel must be emptied first, which is
called ‘pre-emption’. The pre-emption is performed only for Protection Group 2.
2.2.5 Data Service Control
The data service control provides L3 routing function requested to provide VDSL and Ethernet
subscribers accommodated in TAM with data service, and L2 switch cards (GSPC/VSLC/ESIC)
control function. It is performed by the following three major blocks.
NSM block
The NSM block provides the IP-related configuration management function, and also performs the
following detailed functions:
- Port configuration information management and interface creation [at startup, during operation]
- Interface establishment/release control (HMI/CLI)
- Interface information transmission [at startup, during operation]
- Port status information reception
- Interface shutdown/noshutdown
The NSM block controls information switching among blocks such as Routing Protocol, MCRMF,
OS Kernel and Forwarding Engine (FE). For this, it performs the following functions:
　- Block connection
　- System interface information distribution
　- Virtual Private Network (VPN) function
　- Routing table management
　- Forwarding route selection and distribution
　- Static routing
PAGE : 2-40 SM0-000-S00050(V1.0)

OSPF block
The OSPF block provides the subscribers accommodated in TAM with L3 routing function. OSPF is
an internal routing protocol, that solves the defects of RIP, and OSPF Version 2 is described in
RFC2328. It is the link-state protocol, which uses the concept of ‘area’. Therefore, it can be used in a
large-scale network. It provides a means to prevent loops from being formed and features a short
convergence time.
[Figure 2-28] Hierarchical Routing Structure of OSPF
Based on Shortest Path First (SPF) algorithm, the OSPF block selects the optimal path taking the
following evaluation elements into consideration:
　- Link transmission capability
　- Requirement for delay and productivity
　- Number of packets waiting on the link
　- Network load balance
　- Security requirement for the link
　- Number of intermediate nodes between Tx nodes and Rx nodes
Though varying with network circumstances, the path selection must consider three elements of
(1) transmission delay, (2) productivity and (3) connectivity. The SPF algorithm selects the least-
cost path between two communicating nodes. Here, the cost refers a relative value calculated
from the evaluation elements valued by a certain communication application among those listed
above.
SM0-000-S00050(V1.0)
PAGE : 2-41
To establish a path from the source to the destination, the SFP algorithm operates as follows:
(1) Calculates the cost based on evaluation elements for each path on the network.
(2) Calculates the cost required to travel from the source node to each of adjacent nodes in the
network, and selects the one among adjacent nodes that costs the least as the reference node.
(3) Performs Step (2) for the node adjacent to the source node in steps. But, when a path that
costs the least for the same node is found, replaces the existing cost with this value.
(4) Creates a cost table for each path from the source node to the destination node as a result of
Step (3), and decides the routing topology by selecting only the least-cost nodes from the
cost table.
IDC block
The IDC block performs MMI handling (IMD/OMD) required for interworking with EMS and
modification/updating of the required information with the subscriber card, in order to provide data
subscribers accommodated in TAM with data services. In addition, it collects and transfers
status/fault/statistics information. It provides the following functions:
　- EMS interworking
　- VDSL card interworking (SNMP)
　- VDSL subscriber port setup
　- IP service control
　- Software update
　- Status/fault/statistics information transfer
Statistics Faults
STAT FSH
MMC IDC PL
VSLC ESIC GSPC
[Figure 2-29] IDC Block Interworking Diagram
PAGE : 2-42 SM0-000-S00050(V1.0)

The IDC block provides the following commands:
Inquire about VDSL card status and information

Configure VDSL card initial setting and rate adaptive information
Inquire about VDSL port information such as status, rate, SNR, Power, etc.
Set VDSL port upstream/downstream rates
Inquire about traffic control information set to port
Set the traffic information to port
Set the system mac_aging time
Set mac address to port
Delete mac address from port
Inquire about static mac_address set to port
Inquire about all mac_addresses set to port
Set the constraint for the number of mac_addresses trained to VDSL port
Inquire about the constraint for mac_address set to VDSL port and the number
of currently trained mac_address
Set whether to or not to limit the number of mac_addresses trained to VDSL
port
Set IGMP snooping function status
Inquire about multicast member/router information
Set [status], [priority], [max_age], [hello_time], [fwd_delay] values to VLAN to
operate STP function
Inquire about STP status
Set priority and path_cost to port for STP function
Inquire about port status
Create VLAN with vlan_name (vlan_id)
Modify port information to VLAN with vlan_name
Delete a certain VLAN
Inquire about VLAN information set to the system
Set ingress filter/ untagged filter/ tagged filter status to port
Set VLAN operation status (enable/disable)
Set default VLAN.
Set dhcp_filtering function and netbios/netbeui filtering function to VDSL card
Inquire about filtering information set to VDSL card
Set the number of broadcasting messages that can be accommodated in one
second
Inquire about the number of broadcasting messages that can be accommodated
in one second, which is set to port
Set/inquire about/delete trunking function
VDSL card/port reset
GSPC card reset
LED test for VDSL card
Loopback test for VDSL port
Loopback (phi-loopback) test for up-link port
SM0-000-S00050(V1.0)
PAGE : 2-43
2.3 Operation and Management Functions
2.3.1 TMS
The TMS (TAM Manager System) provides EMS-level system management functions for NEs for
efficient management of TAM NEs, and also provides MD function for the TAM-EMS interworking
(TIMS/ANSWERS). The TAM EMS provides Java-based GUI interface for UI client so that the user
can easily and conveniently monitor and control the target system. It consists of subsystems to perform
EMS management functions, such as UIss, UISFss, MFss, NIss and DBss.
UIss (User Interface SubSystem )

The UIss provides the system operator with the graphical user interface function for the convenience of
TAM operation.
Unlike MFss in EMS, the UIss supports forward-part functions only. As being the part with which the
operator comes in direct contact in EMS software, the UIss provides the operator with the interactive
elements that can greatly reduce the operator’s errors and thus help the operator understand the system
operation status easily and correctly.
UISFss (User Interface Server Function SubSystem)

The UISFss defines the interface with the GUI system of TAM EMS (hereinafter to be referred to as
UIss). The UIss is a client operating mainly in Web/Java or Native TCP/IP environment, which takes
charge of user interface, and the UISFss provides the server environment for the UIss. In addition, the
UISFss uses the functions defined by MFss. The UIss and the UISFss communicate with each other
using IIOP (CORBA). For direct communication with network elements, they use MML messages. For
communication within TAM EMS manager system, the UISFss uses MML messages and the operation
of objects defined to be public in the TAM ESM manager. For MML PDU format of the MML
messages used by the UIss and the UISFss, ASCII printable string is used.
MFss (Management Function SubSystem)

The MFss defines major application program functions of TAM-EMS. It consists of blocks to perform
general, configuration, fault, and performance management functions. Unlike UIss in EMI, these
blocks support backward-part functions, and play pivotal roles in EMS software.
DBss (Data Base SubSystem)

The DBss provides the function to store and manage over a long term the data required for operation
among all events, command responses, messages and log data received from TAM-EMS and NEs. Not
only being capable of reformatting and sending the stored data, the DBss also provides database API,
shared memory management API, and file management API for the convenience of data operation. In
general, the data stored in DB is mostly log data generated during EMS operation and those related to
alarms or performance. When necessary, the data about current status of NEs, the management objects
of EMS, is also stored and managed.
PAGE : 2-44 SM0-000-S00050(V1.0)

Niss (Network Interface SubSystem)

The NIss provides interface between TAM EMS and TAM NEs. It is assumed that each NE is operated
and managed using TL1 messages. UMSC is defined to use TL1 messages, and the IN equipment SCP
and SMS are also considering to use TL1 messages for operation and management. The TL1 messages
used between the NIss and NEs are classified into two types: Operations messages given by the
operator and Response or Notification messages reported from NEs to the operator. The NIss’s main
function is to handle these TL1 messages. The TL1 messages are exchanged between the NIss an d the
NE, in the form of TL1 PDU.
2.3.2 TAM Agent
TAM agent is required to efficiently manage TAM NEs, the management object systems of TAM EMS.
It provides the system management function using the management command received from EMS, and
the system information collection function to provide notifications about system performance and
alarms. TAM agent functions are performed by MFss, EISS and NIss.
MFss(Management Function SubSystem)
The MFss defines the agent functions corresponding to MFss functions of TAM-EMS, and performs
general, configuration, fault, and performance management functions as an agent. It consists of
Accelerator that receives the management command from TAM-EMS and transfers it to the system,
and Translator that translates response or notification messages sent from the system in order to map
them to IIOP (CORBA) PDU.
Eiss(External Interface SubSystem)
The EIss servers as the interface with TAM, and plays the role of a poller that sends the data
generated in MFss to the system and check whether response or notification message arrives from the
system or not.
Niss(Network Interface SubSystem)
The NIss provides the interface between TAMMS (TAM-EMS) and TAMAS (TAM Agent), which is
operated and managed according to IIOP (CORBA). The NIss consists of Operation Manager that
receives the management command from TAMMS, Event Manager that sends the response or
notification message for the command.
SM0-000-S00050(V1.0)
PAGE : 2-45
2.3.3 Data Processing Functions
For data processing functions, there are signaling device data processing function, system data
processing function, and general data processing function.
Signaling device data processing function
By the operator’s request, TMS changes and displays the information about signaling devices such as
tone and ring. It also changes/displays various time values required to be identified during call
service processes. TAM provides the criteria and process for signaling device data processing, and
the interworking with service and resource management functions.
System data processing function
By the operator’s request, TMS modularizes and displays processor configuration information, and
speech path and I/O device configuration status from the aspect of hardware configuration. It
displays the information about out-of-service devices during system operation, and the threshold
values for fault isolation calculated by system resources. It also displays the manufacture version of
application program, and at the same time processes configuration status of various interface devices
and information about service enable and disable status.
Data processing function
Data processing function refers to a function to display, change, delete, and add data interface
information in TAM. It is performed in interworking with the operator interface function.
2.3.4 Statistics Functions
In TAM, the statistics functions are performed for performance, resources, faults, calls, and protocol.
1) Performance
- Total OS CPU load, total dummy CPU load, total user CPU load
- Numbers of internal IPCs, Rx IPCs, and Tx IPCs
2) Resources
- Displays the numbers of V5.2 links equipped, available, blocked, faulty, and deleted.
3) Faults
- DA-bus answer-back
- Deletion and FUF of subscriber control card and subscriber card
- Deletion and FUF of sub-highway (SHW & subscriber card - voice device cable) and signaling
devices
PAGE : 2-46 SM0-000-S00050(V1.0)

- Deletion, FUF, and ALM of V5.2 control card and V5.2 card
- Deletion and FUF of clock receiver/distributor part, network sync. control part, and clock cable
- Vocoder deletion and FUF
- Protocol errors (including Reject and Timeout)
4) Call
- Numbers of V5.2 channels connected/disconnected
- Numbers of data channel connected/disconnected
5) Protocol
- V5.2 protocol message count
- BCC, PSTN, control, link control, protection
- IP protocol message count
The statistics function is performed by MSDP, MDGC, and MSLC blocks.
MSDP block
The MSDP block provides the following functions:
(1) Analyzes and processes MMC command requested by the operator.
(2) Analyzes and displays statistics data collected from MDGC block by the operator’s request.
(3) Stores statistics data collected from MGGC block to the disk at the test interval
(5 minutes usually).
(4) Analyzes and displays statistics data stored in the disk.
(5) Calculates the sum of the 5-minute statistics data by hours, days, and months, and stores the
result in the disk.
(6) Delete the statistics data from the disk by the operator’s request.
MDGC block
The MDGC block collects statistics data from MSLC block at the test interval (5 minutes usually),
sends the result to MSDP block, and then clears the data remaining in the MSLC block.
MSLC block
The MSLC block is a set of procedures for statistics data processing. When the procedure is called by
the relevant block in each stage of call processing or when it is necessary to collect statistics data due
to fault occurrence, the statistics function is performed. In this case, the MSLC block increases the
related data values, which are cleared by MDGC block.
SM0-000-S00050(V1.0)
PAGE : 2-47
2.3.5 Start, Restart, and Loading Functions
These functions are performed by PL block in MP.
PL block
Installed in MP, the PL block performs loading for user block when the loading request is created due
to start or restart.
The PL block applies check-sum for all important signals used for data transmission during loading
process. It checks the return values of OS primitives for signal transmission, to ensure the reliability
of transmitted data, and recovers errors if the data contains any errors.
CIT EMS
SHM
CA OC
EC
FSH
PL
PSH
IDC
VSLC ESIC GSPC
[Figure 2-30] PL Block Interworking Diagram
PAGE : 2-48 SM0-000-S00050(V1.0)

2.3.6 MMI (Man Machine Interface) Function
MMI provides a means of communication between the system and the operator, and regulates I/O
formats, dialog procedure, and interactions between the system and the operator. In addition, it
provides various functions to facilitate system operation and addition of new requests
(add/change/delete I/O messages). As means of dialog, it provides various operation environments to
the operator such as direct command input, command input using menus and formats, and log
management. It also provides the interface with network management center. The MMI functions are
performed by CA, CFC, EC, HR, OC, and SHM blocks.
CA block
The CA block checks whether the operator is qualified to access the system, to provide the interface
path between the operator and the system, and decides the command session. When the dialog
procedure is established, it analyzes the syntax and meaning of the command input by the operator,
and informs the result to the operator and sends the command information to the corresponding block
to execute the command.
EC
SMH CA HR
OC
[Figure 2-31] CA Block Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-49
CFC block
The CFC block provides command batch file activation/inactivation function.
EC
CA CFC
[Figure 2-32] CFC Block Interworking Diagram
PAGE : 2-50 SM0-000-S00050(V1.0)

EC block
The EC block transfers the input information from CA block to the user, and monitors the command
execution status. It also inquires about command execution status and/or stops the execution. It
controls command decomposition, converts the command, sends the command to a relevant block to
execute, and monitors the command execution. As for the execution result, it inserts format data and
converts it to basic output data.
Application
Block
SMH EC HR
OC
[Figure 2-33] EC Block Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-51
HR block
The HR block stores operation messages generated during system operation, and provides the stored
data to the operator upon request. The operation messages include operator’s session information,
input commands, and output messages (ALM, FLT, STS, MMC), which the HR block retrieves and
displays according to the condition requested by the operator (user, time, message type). In addition,
it stores and retrieves history interworking with CA and OC blocks.
SMH
CA
HR
CA
File OC
[Figure 2-34] HR Block Interworking Diagram
PAGE : 2-52 SM0-000-S00050(V1.0)

OC block
The OC block composes and controls output messages in interworking with EC and CA blocks. It
recomposes output data to fit the output mode, and selects and controls an output device according to
the message type to be sent to the operator. It also handles MMC commands related to message
output, and displays the result message.
Application
Block
SMH OC HR
[Figure 2-35] OC Block Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-53
SHM block
The SHM block controls creation of all processes along with the start of dialog with the operator and
their termination along with the end of the dialog, by providing the following functions:.
- Creates/terminates MMI processes
- Manages operator and IO ports.
- Composes data to be displayed on the header window.
- Sends/receives commands and results messages to/from the operator terminal LCT and agents.
SHM
CA HR OC
[Figure 2-36] SHM Block Interworking Diagram
PAGE : 2-54 SM0-000-S00050(V1.0)

2.3.7 Time Management Function
The time management function is to set and manage TAM time, which is performed by TM block.
TM block
The TM block manages TAM time by providing the following functions:

- Sets TAM time by MMC.
- Sets TAM when the system starts.
- Manages time during operation.
EC
Request to set/inquire about time Response
TM
[Figure 2-37] TM Block Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-55
2.4 Maintenance Functions
2.4.1 Configuration Control Function
The configuration control function is to manage TAM processors and IPC configuration and control
duplication status, which is performed by FSH block.
FSH block
Installed in MP, the FSH block manages configuration information including processor equip
information and current status information, and monitors TAM processor status, and IPC with TAM-
CS1000 (RS Mode) and its processor status.
Through communication with EMS, the FSH block transfers current configuration information to the
EMS so that the EMS can display the information to the operator. When status change occurs such as
processor-level fault occurrence and recovery, the FSH block reports the status change to the EMS,
to display the changed configuration information to the operator. It receives control commands for
duplicated processors such as switchover command, and control the processor status It also receives
and controls the status information from MP and TAM-CS1000 (RS Mode) processor periodically.
Application
FSH EMS
Hardware
FSL
[Figure 2-38] FSH Block Interworking Diagram
PAGE : 2-56 SM0-000-S00050(V1.0)

2.4.2 Resource Management Functions
The resource control function is to control service resources in TAM such as traffic pool, Vocoder, and
DLC channels, to connect and releases the resources in interworking with the service and maintenance
function, which is performed by LSL block.
LSL block
Installed in TAM MP, the LSL block provides resource connection control function in interworking
with the service and maintenance function block. The resources subject to control are Vocoder and
traffic pool. For Vocoder, the coding type should be designated by DSP unit at the time of
initialization. In general, the resource control function refers to resource allocation, resource status
change and connection control in interworking with FSL block upon the request of the service and
maintenance function block. Interworking with other blocks is executed in the form of library, during
which service and maintenance should be separated. With regard to service control function, there is
no Ack (response) from the device.
LSL VPC
[Figure 2-39] LSL Block Interworking Diagram
SM0-000-S00050(V1.0)
PAGE : 2-57
2.4.3 Fault Handling Function
The fault handling function includes subscriber fault handling, signaling device fault handling, and
V5.2 fault handling functions.
1) Subscriber fault handling
The subscriber fault handling refers to a series of functions to test/manage/report the status of
subscriber cards in TAM and those accommodated in TAM-CS1000 (RS Mode).The subscriber status
management is performed by FSH and AST blocks in interworking with V5.2 connection control and
V5.2 configuration protocol control functions.
FSH block
The FSH block manages the subscriber status using periodic monitoring result of subscriber card status,
detected hardware alarms, and detected hardware status information. Depending on the fault class of a
subscriber card, it decides whether to or not to isolate/recover the subscriber card out of service. When
a subscriber status is changed, it displays the status change information to the operator so that he or she
can take maintenance measures if necessary. For this, it performs MMC related functions in
interworking with V5.2 block, and reports the result to the operator. It also displays the current status
requested by the operator. It is interrelated with the V5.2 block through FSL block.
The FSH block handles and reports various hardware and software alarms and faults. It collects and
analyzes fault information generated by subscribers, to determine the corresponding fault class. It
provides the analysis result to the operator or uses it within the system, to provide guidelines to handle
the faults and prevent the fault from spreading. It also handles the operator’s request for message
output control. It detects all hardware and software alarms generated in each subsystem, to identify
alarm type, location, class and content and sends the alarm message to the operator. Based on this
alarm message, the operator takes prompt measures to recover normal status, to enhance overall
reliability of the system. See [Figure 2-39]
AST block
The AST block tests qualities and functions of analog subscriber devices such as analog subscriber
lines, analog subscriber line interface circuits, and analog subscriber terminals, for diagnosis and
maintenance purposes. It provides test function and test control function. It also provides on-demand
test functions such as instant test, general test, howler tone transmission test, idle line test, call test for
the subscriber being tested, telephone test, and test by line repair staff.
PAGE : 2-58 SM0-000-S00050(V1.0)

LTTM
Test Request Response
Library
CSL
AST FSL
LSL
[Figure 2-40] AST Block Interworking Diagram
2) Signaling device fault handling
The signaling device fault handling refers to a series of functions to test signaling devices in TAM, so
as to detect and handle faults. It is performed by ADMH and FSH blocks along with the signaling
device status management, in interworking with the status management function block.
ADMH block
The ADMH block performs various tests using BER test device, including the test for each section of
the speech path. It also performs on-demand tests (MMC command = On-demand Test), and reports
the test result to FSH block for status management. If a fault occurs during a periodic test, it outputs
the corresponding fault message. If a fault occurs during an on-demand test, it displays the
corresponding test result.
SM0-000-S00050(V1.0)
PAGE : 2-59
FSH block
The FSH block monitors signaling devices (subscriber lines, trunk lines, speech path, switches,
network sync., I/O, etc.) periodically, and manages the signaling device status using the monitoring
result, hardware alarm information, and hardware status information. Depending on the fault class of a
signaling device, the FSH block decides whether to or not to isolate/recover the signaling device out of
service. If the status of a signaling device is changed, it displays the changed status information to the
operator so that he or she can take maintenance measures if necessary.
The FSH block handles and reports various hardware and software alarms and faults. It collects and
analyzes hardware and software alarms generated by each subsystem, to drive audible and/or visible
alarms. It identifies alarm type, location, class and content and sends the alarm message to the operator.
Based on this alarm message, the operator takes prompt measures to recover normal status, to enhance
overall reliability of the system.
There are two types of alarms – those detected by software (called software alarms) and those detected
by hardware (called hardware alarms). For software alarms, the FSH block actively monitors each
block in processors of each subsystem using the threshold value of the block, and reports abnormal
status according to the threshold value. For hardware alarms, alarm interface control unit and MP
detect alarms by themselves and report them to the FSH block.
The FSH block analyzes the alarm report, decides its authenticity, and outputs alarm message for real
alarm status. It also enables the operator during operation to check the latest alarm history, alarm
generation status for each alarm class, and out-of-service alarm sources. It classifies alarms into three
classes (CRITICAL, MAJOR, MINOR) depending on their importance, and drives audible and/or
visible alarms, so that the operator can recognize the system status in real time. See [Figure 2-39].
3) V5.2 fault handling
The V5.2 fault handling refers to a series of functions to test/manage/report the status of service
resources in TAM such as V5.2 links and protocol handling block. It is performed by VPC and FSH
blocks along with the V5.2 status management, in interworking with the V5.2 connection control and
the V5.2 configuration protocol control function.
VPC block
The VPC block performs V5.2 status management in interworking with FSH block through FSL block.
It receives fault reports on subscribers and V5.2 link resources, stores their status, and performs
necessary functions such as protection switchover to prevent services from being interrupted. See
[Figure 2-26].
PAGE : 2-60 SM0-000-S00050(V1.0)

FSH block
The FSH block monitors the status of V5.2 link resources and subscribers, and reports their status to
VPC block if any fault is found, so that the corresponding fault status can be stored and notified to LE
via V5.2 protocol. After that, it reports the fault status to the operator with MMC message. It transfers
MMC command to block/unblock a V5.2 device from the operator to the VPC block for corresponding
handling, and reports the result to the operator. See [Figure 2-39].
2.4.4 Audit Function
Audit refers to a function to maintain the integrity of system status by monitoring the status of service
resources in TAM such as subscribers, V5.2 links, signaling devices. The audit function is performed
by FSH block in interworking with the status handling and resource control function.
FSH block
The FSH block stores the status of all hardware devices and operating software and, if it is found
through periodic audit that the current device status and the stored status are inconsistent, it matches
the statuses to maintain consistent services. See [Figure .2-39].
2.4.5 System Sync Fault Handling Function
The system sync fault handling refers to a series of functions to test/manage/report the network sync
status. It is performed by FSH block along with the system sync status management function, in
interworking with the clock management function.
FSH block
FSH block receives the report on NES status change detected by self-diagnosis function of firmware
embedded in SCTM and the result of on-demand test, to identify the fault status and perform prompt
recovery measures. It also provides fault reports on power fail, PBA deletion, PLL error, CPU fail,
RTC fault, and output clock fault to FLM block.
In interworking with the alarm detection block, the FSH block manages and reports fault information
to the operator, displays alarm information, and handles alarm-related MMC commands. It receives
fault messages including hardware and software alarms, and stores the analyzed fault and alarm
information to database. It composes output alarm messages and drives corresponding audible and/or
visual alarms, to inform the operator on the alarm terminal. It provides the audit function for alarms,
and handles on-demand commands such as alarm isolation/recovery, alarm class change, and alarm
masking. See [Figure 2-39].
SM0-000-S00050(V1.0)
PAGE : 2-61
3. Outdoor Housing
3.1 Overview of Outdoor Housing
3.1.1 Overview
By providing EMS management functions and gateway functions by Softswitch control using an
outdoor housing that accommodates remote office subscribers who were conventionally
accommodated by LEs, TAM-CS1000 can accommodate both Ethernet and VDSL subscribers as well
as general POTS subscribers.
As being installed and operated outdoors, the TAM housing facilitates all kinds of management and
maintenance works. In addition, as heat generated from the system can be dissipated sufficiently to the
outside, it can supply power normally even during the rainy season or heavy snow, to ensure stable
system operation even in unfavorable environmental conditions of temperature and humidity. With its
self-contained power supply to communication devices and structure components, cooling system, and
control power outage, it can easily adapt itself to outdoor environments. It needs a minimum space for
installation and thus it is appropriate for efficient system construction. As it allows installing optical
receiver device or equipment through the part where copper lines are clustered, it helps integrate and
take care of devices and instruments that needed and reduce the LAN operation cost and enables
efficient management.General
(1) Matters not specified in this specification with regard to manufacturing of the outdoor housing
should comply with the manufacturing standard for general communication cabinets.
(2) As it is installed and operated over a long period of time, the outdoor housing should have a
watertight structure that can bear outdoor climate conditions.
(3) The housing wall should be made of a special aluminum extruded shape, which ensures
watertightness after installation.
(4) Auxiliary materials other than internal structural materials should have prefabricated structures,
which can be easily replaced if any defect is found during the housing operation. The housing
should be placed in a 26” standard rack.
(5) Sensors to monitor the internal conditions of the housing, such as fire detector, thermometer,
hygrometer, and door sensor should be installed.
(6) An apparatus to install a watt-hour meter should be equipped in the housing.
(7) A space of 200mm should be ensured at the bottom of the housing to accommodating
communication and power cables. The housing should be protected with a corrosion-resistance
cover from rainfall.
PAGE : 2-62 SM0-000-S00050(V1.0)

(8) There should be a conduit at the bottom of the housing, through which cooper-wire cable, ground
cable, spare cable, optical cable, flood-alarm cable can be led in. When the cables are led in
through the conduit, the space between the conduit and the cables should be minimized
mechanically and sealed with the water cut-off foaming agent to prevent moisture from getting into
the housing.
(9) The housing should have two doors respectively on the front and the back to facilitate maintenance
work. The doors should be of minimum possible size so as not to limit the walking space when
they are opened. The doors should be attached with locks, and should be manufactured with cold
rolled steel sheet with the thickness of 1.6mm or more.
(10) The housing should be fixed to the foundation concrete using 12mm anchor bolts.
(11) For protect its external color from ultraviolet ray degradation, the housing should undergo SA 2.5
grade sanding and then should be coated first with epoxy spray and then polyester spray.
(12) Parts where steel or plate materials are used (such as door, side, and roof) should be functionally
protected from corrosion using shot blasting, under-coating and over-coating.
(13) The cabling inside the housing should be protected using cable ducts and pipes except for special
cases.
(14) Components inside the housing should be deployed in consideration of the space required for
installation.
3.1.3 Features
(1) The cooling system consists of the heat exchanger and the blower in the upper part of the housing.
(2) The use of an active heat exchanger reduces noises.
(3) The size of a shelf equipped inside the housing is 26 inch.
(4) Storage battery enables uninterrupted service.
(5) The battery case is placed in the bottom of the TAM.
(6) As being installed outdoors, the housing is designed to be exposure- and environment-friendly.
(7) The housing is protected from external impact and environment.
(8) It is watertight and airtight.
(9) It is provided with alarm functions against flooding and trespassing.
(10) It is equipped with the cooling system to keep proper temperature for stable equipment operation.
(11) The housing has a system structure that allows clustering 24 cores or more of optical cables.
(12) It has 4 doors for easy opening and work, and each door is equipped with a lock.
SM0-000-S00050(V1.0)
PAGE : 2-63
3.2 Structure and Shape
3.2.1 Configuration
(1) FAN module
(2) Heat exchanger
(3) Power distribution panel (PDP)

The PDP is equipped with main circuit-breaker, lighting, outlet, and spare circuit-breaker. In
addition, it has a circuit-breaker to distribute DC power to system, fan, and backup battery.
(4) System (including shelf)
(5) Optical fiber distribution (OFD)
(6) CSU (including shelf)
(7) Router (including shelf)
(8) GND panels (for communication and for power)
(9) Rectifier
(10) Storage battery
(11) MDF
(12) External housing
(13) Fluorescent lamps, outlets, spare circuit-breaker, heater, and cables. Specifications
Item Specifications Remarks
Housing W1350 x H1800 x D850 26inch Rack
Aluminum (AL6063) and stainless
steel (SUS304) for main frame, and
Material thick cold rolled steel plate Main frame and internal materials
(KSD3501) for doors and external
panel
Fan 26 inch, 3U Blower fan, Shelf type
Cooling
26 inch, 5U Heat exchanger (1,500Watt), shelf type
System
Accommodates main power and auxiliary
PDP 26 inch, 2U
circuit-breakers
OFD 26 inch, 1U 24 core wire clustering
Storage Battery W550 x H272 x D538 12V/120AH x 4EA, Rechargeable
IDC-10 W124 x H21.6 x D41.2 Disconnection mode
Accommodates communication GND and
GND Panel W175 x H50 x D5
power GND.
PAGE : 2-64 SM0-000-S00050(V1.0)

3.2.3 Appearance
100
FAN
Heat Exchanger
PDP

MDF
1800
OFD
Rectifier, Ring
Battery
Depth : 850
200
1350
SM0-000-S00050(V1.0) PAGE : 2-65

3.2.4 Cooling Method

Plate Heat Exchanger
Cross flow type - Cross flow type (Subrack mount)
Plate Heat Exchanger - Cooling performance: 100W/℃ or more
(Subrack mount) - Composition: H/E core, external fan, and
internal blower
Internal Cool Air
External Fan
Internal Hot Air
External Cool Air
PAGE : 2-66 SM0-000-S00050(V1.0)

3.2.5 Equipment Requirements
(1) Mechanical and chemical endurance and robustness against twist, bending, deformation, change,
and others
(2) Consistent temperature and humidity (radiant heat, thermal cycle, condensation, etc.)
(3) Flooding and trespassing alarms
(4) Door locks
(5) Easy to move and install (convenience of movement and installation depending on capacity)
(6) Others (ignition prevention, luminosity, painting, others)
3.2.6 Environmental Conditions
(1) Maximum absolute external temperature: +60℃
(2) Minimum absolute external temperature: -20℃
(3) Highest average weekly internal temperature for the summer season: +60℃
(4) Lowest average weekly internal temperature for the winter season: -60℃
(5) Wind velocity: 160Km/h on the level ground (structural aspect)
(6) Total heat value of the equipment: 1,500W
SM0-000-S00050(V1.0)
LG Electronics, Inc. All Rights Reserved PAGE : 2-67
3.3 Functional Description
3.3.1 Power Cooling Module (Heat Exchanger)
(1) Structure
The power cooling module uses the heat exchanger in the upper part of the housing, and its wall is
made up of heat sinks to increase the area in contact with air.
(2) Operation principle
The heat exchanger control the temperature inside the rack to ensure stable system operation even
in unfavorable environmental conditions, through cooling and heating. Its wall is made up of heat
sinks, to provide a high heat exchange capacity.
3.3.2 Power Distribution Panel (PDP)
Accommodated in the standard rack, the PDP supplies ASC power to rectifier, fluorescent lamps,
outlet, and heater. The PDP should contain 2 main C/Bs, 5 A/C auxiliary C/Bs, and 9 DC auxiliary
C/Bs.
Its characteristics should comply with “the environmental test requirements for telecommunication
facilities” in the Quality Standard.
3.3.3 Optical Fiber Distribution (OFD)
The OFD should be installed as 1U shelf type to connect optical transmission devices. Inside the OFD,
a tray for optical connection and the other for effective deployment of remaining cables are made up.
In addition, an adaptor to connect 24-core optical cable is installed.
3.3.4 Storage Battery
(1) Overview
The storage battery is a backup system that can keep the system alive for certain hours during power
outage, which is slid into the 26 inch rack inside the housing for easy installation and replacement. (2)
Characteristics
- The storage battery is a rechargeable lead battery for communication, which consists of four 12V
120AH batteries.
- The storage battery terminal is formed as stud.
- Explosion-proof function
- Its expected lifecycle is 5 ~ 6 years, which should be longer than that of general storage battery.
- The pole plate should be manufactured with rolled extension method, to maximize its durability.
- To prevent internal short-circuit and early extinction, an envelope-type separator should be installed.
PAGE : 2-68 SM0-000-S00050(V1.0)

- Flexible rib should be used to prevent the pole plate from being damaged by contraction and
expansion during charging or discharging.
- The storage battery should have a flat case bottom, to protect the pole plate from minute vibrations
during transportation or operation.
- The terminal should be pressed to be fixed to the cover with the sealant between them, to prevent
leakage of sulfuric acid during the use of the storage battery.
3.3.5 Main Distribution Frame (MDF)
(1) Overview
The MDF connects subscriber cables and office cables using IDC pins in it when VDSL is not
provided, and connects optical VDSL IDLC terminals using SP/Pro to provide VDSL service when
VDSL is provided.
(2) Characteristics
IDC terminals should have an insulated airtight structure, to maintain solidness during copper-wire
clustering at the copper-wire insertion force of 40~75N and copper-wire pulling force of 10.5N. It
should meet the temperature condition of -20℃ ~ 80℃. For materials, it should be made of PBT for
plastic part, and phosphor and 0.5 micrometer silver plate for connection spring.
3.3.6 GND Panel
(1) All steel parts should be grounded.
(2) Ground consists of power ground and communication ground.
(3) All equipment parts should be grounded from GND panel.
(4) Power ground should be constructed with 100Ω or less.
(5) Communication ground should be constructed with 10Ω or less.
(6) Moving parts (like doors) should be connected with 6mm cable ground.
(7) Parts connected to the ground should not be coated to maintain electric conductivity at its best.
3.3.7 Fan
The blower fan circulates the heat generated from the system and the rectifier effectively to
the outside.
SM0-000-S00050(V1.0)
3.4 Operation Description
3.4.1 Cable Clustering
(1) On the front of the housing, 2 sets of 620-circuit IDC back frames can be mounted and on the
back, one set of 490-circuit IDC back frame and one set of 330-circuit IDC back frame can be
mounted.
(2) Each IDC back frame should be mounted depending on service wire type, and then IDC terminal
plate should be mounted additionally, securing space by the unit of100 circuits to help identify
circuits easily.
(3) As the service copper cables should be clustered on the IDC terminal plate mounted on the front
and back of the housing and the high-speed service wiring cables from the optical transmission
device are clustered on the IDC terminal plate mounted on the front part. The copper cables
should be clustered in consideration of post-clustering of high speed service distribution cables.
(4) The led-in feeder cables should be divided in consideration 10 lines of subscriber cables and 10
lines of trunk cables are clustered on an IDC terminal plate.
- For example, up to 62 IDC terminal plates can be mounted on the 620-line-accommodated IDC
back frame installed in the front of the cabinet. The number of IDC terminal plates which
accommodate the subscriber cables and the trunk cables, and those for high-speed service
distribution cables of the optical transmission equipment are summed up in this number.
- From the 620-line-accommodated IDC back frame, 520 lines (52 IDC terminal plates) should be
clustered for subscriber cables and trunk cables, and the remaining 100 lines (10 IDC terminal
plates to which the grounding bars are added) should be clustered in the optical transmission
equipment for high-speed service distribution cables.
- Therefore, the 620-line-accommodated IDC back frame accommodates 520 subscriber cables,
520 trunk cables and 100 high-speed service distribution cables.
3.4.2 Connecting Ground Cable
(1) 2 hole lugs should be adopted in the grounding terminal plate.
(2) 2 pairs of grounding cables led in to the base should be connected to the signal grounding
terminal plate (10Ω) or the frame (main) grounding terminal plate (100Ω) in the outdoor housing
depending on the usage. The person in charge of the grounding work must recheck the grounding
resistance and confirm reliabilities before connecting the cables to the grounding terminal plate.
(3) Copper cables shall be grounded on the signal grounding terminal plate. The IDC back frame,
while insulated from the outdoor housing, should be grounded on the signal grounding terminal
box.
(4) The main power supply should be grounded on the frame grounding terminal plate.
PAGE : 2-70 SM0-000-S00050(V1.0)

3.4.3 Main Power Supply
(1) Because the power supply for the housing should be led in through the bottom of the outdoor
housing, the cable path should have been secured when the base is installed.
(2) The is a support for a watt-hour meter inside the housing, and a window for meter reading on the
back of the housing. The watt-hour meter may be installed outside of the housing depending on
the site conditions.
(3) Since the power consumed in a housing is about 1.5KW, the power supply to the housing should
be 1p, 220V and 3KW, which are subject to change depending on the site conditions.
3.4.4 Installing Power Distribution Panel (PDP)
PDP is the equipment which distributes the main AC from power supply and the DC from the rectifier.
PDP is equipped with a breaker.
3.4.5 Installing Battery
(1) Before applying the system, make sure to understand the features of the lead acid batteries of the
sealed maintenance free type which is designed for communication only (Telecom Charge : TC
Battery Series).
(2) Installation guide
- Install a stand enduring against vibration in a safe space without risk of short-circuit and electric
shock, and connect the cable in series to the correct polarity in consideration of maximum
current. The circuits should be arranged correctly between the batteries.
- Fastening nuts : Mount the cable connector on the terminal with nuts. Nuts should be tightened
with the fastening strength of not higher than 15Nm.
- Safety check : If the batteries are installed on the system, cover the terminal with the cap of the
insulating or non-conducting material, in order to secure safety against contact with external
conducting material.
- Charging and discharging : Set the charging and discharging conditions as recommended by the
manufacturer.
(3) Battery fault : If abnormal battery operation including leakage, discharge, gas emission and
deformation of exterior is detected during operation of the battery, you should stop recharging
process immediately, detach the battery from the recharging circuit, cool down and ventilate, and
follow the instruction of the expert or the manufacturer. (Do not disassemble the battery or
execute the battery performance test.)
SM0-000-S00050(V1.0)
3.5 Maintenance
3.5.1 Maintenance of Housing
(1) Maintain the level of the base surface in ±3mm. Leveling of surface will prevent distortion of
housing, fan noise and deformation of exterior.
(2) Do not give excessive force on the roof. (Do not pile up housings.)
(3) When moving a housing, replace the sus bolts with the eye bolts, and use a forklift or crane. Make
sure to fasten the bolts tight with a spanner or a supplementary tool.
(4) Front/rear side of a housing are identified with metering window. The front side has a metering
window, while the rear side has no metering window.
(5) Doors are classified into a system door and an IDC door. The system door is larger than the IDC
door.
(6) In order to open the doors, open the IDC door using a handle, and turn the latch, and then, open
the system door. The door can be open at 105 degree. Do not give excessive force to open the
door wide, or the stopper on the bottom may be detached or broken. In order to close the doors,
follow the above steps in reverse order.
(7) In order to operate the door handle, insert the key on front/rear side, turn the handle
counterclockwise, and pull the door. The direction is indicated on the sticker on the upper side of
the handle.
(8) The door handle has a locking cylinder built-in, that it can be opened with the key only. Unless
there is an extreme impact, the door provides a superior security. Lock the key, and press down
the handle until you hear a click. The hinges can sufficiently support the door as they hold the
door in 3 points. However, excessive force applied down to the door may cause dislocation of the
door or distortion of the hinges.
(9) Make sure that the door part which meets the waterproof gasket is not stained with a foreign
substance. The gasket should not be torn or damaged. The gasket can be easily inserted and
removed.
(10) The heat exchanger is on the top of the rack. The exchanger should be checked at least once in
two years. Interior cleaning and maintenance must be performed by the authorized engineer only.
Make sure to cut the power before repairing the housing. Check from time to time if a
contaminant is created by the environmental cause.
(11) The operator must check the PDP, the optical distribution unit and the grounding unit against the
rest elements including power down, electric leakage and natural disaster.
(12) Because the housing is designed to accommodate the racks of 26” in width and 660mm in length,
check the specifications for installation and replacement.
(13) The battery box is designed in the slide type to facilitate replacement of the batteries. Batteries
should be replaced based on the battery wiring diagram. To open the battery box, remove the 4
bolts from the handle and pull the box. The sliding distance is 500~530mm. Applying excessive
force to pull the box may have the balls off from the slide. Pull the handle on the roof of the box
PAGE : 2-72 SM0-000-S00050(V1.0)
to see the connection of the batteries. To close the battery box, follow the above in reverse order.
After finishing installation, fix the rack to the housing with bolts to avoid interference to the door.
The battery should be of the sealed maintenance free type. If a leakage is found, replace the
battery immediately. (Gas and corrosion may occur.)
(14) Optical distribution box (O.F.D.) is used for clustering of optical cables. Like the battery box, the
optical distribution box is designed in the slide type. To open the box, turn the two captive screws
counterclockwise, and then, lift up and pull the slide. The optical distribution box slide is in 3
units, and is slided out for 320~350mm from the rear side.
(15) The system, rectifier and the battery are to be selected by the user, but via advance consultation
with the manufacturer of the outdoor housing.
(16) The electric outlet is located between the system and the IDC. To use the electric outlet, turn on
the outlet S/W of the PDP. The outlet has two 220V holes.
(17) Lamps are in the front and rear part of the system unit. The power S/W should be always on so
that the system can operate at any time. To replace the lamp, turn the captive screw on the front of
the housing counterclockwise, open the cover down, and replace the stabilizer-embedded lamp
(15~25W).
(18) The heater is inside the heat exchanger. It is recommended that you should use the heater from
mid November to mid March. To use the heater, turn on the AC heater S/W in PDP.
(19) The reflection board on the top of the housing not only blocks UV rays and radiant heat from the
sun, but also conducts heat equally in the housing. Therefore, be careful that the reflection board
should not be stained from the cable insertion cream.
(20) The IDC stand must be strong enough to hold the MDF module and the lightening arrestor
module. The MDF module should be installed from the upper part, and should not be installed in
the lower part if possible. This is to protect the module from interference of door stopper or wires
on the lower part of the housing.
(21) Fix the main and signal grounding cables on the 2 holes of the lug to prevent defective grounding.
(22) After connecting the copper cables, strip the base cover, fix the cable tight to the waterproof
javara with stainless band, and apply sealant in between the copper cable and the waterproof
javara inside the housing.
(23) Sidewalls, doors and the roof of the housing are made of steel and electric-zinc plated, and then
spray-coated to prevent corrosion. Because corrosion is started if the housing is scratched by
external impact, apply coating material and alcohol at the ratio of 1:4 to avoid progress of
corrosion. The housing is made of aluminum except the above mentioned parts. The coating
material applied on the scratch shall conform to the SP’s technical request or specifications.
(24) The user shall request Korea Electric Power Corporation for power supply work (main and circuit
breaker).
SM0-000-S00050(V1.0)
3.5.2 Battery Maintenance
(1) Wiring of input cable
- Check with DVM if input power is 1P, 185VAC~240VAC.

- Connect HOT, NEUT and F.G to the 'AC Input' terminal plate.
(2) Wiring of battery
- Make sure to check the polarity before connect the cables between the batteries as illustrated in
Figure 1.
- Connect 4 x 12V batteries in series.
- Connect the battery lines to the battery terminals with correct polarity markings (+ and -).
<Battery Wiring Diagram>
(3) Wiring of output cable
- The output of the battery consists of 3 terminals (SH1~2, FAN1).

- Shelves 1, 2 and FAN1 can be used when NFB of Output1 on the front of the system is “ON”.
- Check the polarity of GND and -48V terminal of each port before connecting output cables.
(4) Wiring of BATT.TEMP. SENSOR : BATT.TEMP.(1m) SENSOR line should be connected to the
BATT.TEMP.Connector of the backboard of the rectifier via the bracket.(5) Alarm communication
port
- Use 4 stack z-pack connectors and 9P D-Sub cable to connect between the system and the rectifier.
- Check the RS-232C communication port after connecting 9P D-SUB connector to the PC. (Use the
RS-232C port on the rear part of the shelf to connect between PC and the control panel.)(6) Wiring
other units
PAGE : 2-74 SM0-000-S00050(V1.0)

- Battery Cell Sensing

Connect the cell sensing line to the connector (B-cell sensing) on the rear part of the rectifier, and
connect to the lugs with the label as illustrated below. Connect the lug wires to the battery terminal
with M3 x 6 bolts. - Sensor Input : Connect the sensor cables to the terminals with the sensor marking
on the backboard.
BATT (-)
BATT (-)
-12V
-24V
-36V
-48V
SM0-000-S00050(V1.0)
Chapter 3. Appendix
Chapter 3. Appendix
ALM Alarm
API Application Program Interface
ASC Analog Subscriber Control
AST Analog Subscriber Test
BCC Bearer Channel Connection
BER Bit Error Rate
CA Command Analyzer
CAMR Compact Access Module Rack
CID Connection IDentifier
CLI Command Line Interface
CO Central Office
CORBA Common Object Request Broker Architecture
CPU Central Processing Unit
DB Data Base
DBss Data Base SubSystem
DHCP Dynamic Host Configuration Protocol
DOTS Digital Office Timing Supply
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
DSP Digital Signal Processor
EC Execution Control
EMS Element Management System
EN Subscriber Equip Number
EPIC E1 Port Interface Card
ESIC Ethernet Subscriber Interface Card
ESRC Ethernet Subscriber Rear Card
FLM Fault Management
FLT Fault
FSM Finite State Machine
GoS Grade of Service
SM0-000-S00050(V1.0)
Chapter 3. Appendix
GRSC Gateway Ring Supply Card

GSPC Gigabit Switch Processing Card
GSRC Gigabit Switch Rear Card
HR History Recording
HS Host System
IDC IP based Digital subscriber line Control
IGMP Internet Group Management Protocol
IIOP Internet Inter-ORB Protocol
IMD Input Message Description
INVC IP Network Vocoder Card
IPC Inter Processor Communication
LE Local Exchange
LN Subscriber logical Number
LSL Local Shared Library
MCMC Main Control & Maintenance Control
MCRC Main Control Rear Card
MDGC Measurement Data Gathering on Call
LMCC LG Megaco Connection Control
MESH MEgaco Stack Handler
MFss Management Function SubSystem
MMC Man Machine Command
MMI Man Machine Interface
MML Man Machine Language
MP Main Processor
MPSH Main Processor Status Handling
MSDP Measurement Statistics Data on Processing
MSLC Measurement Statistics Library on Call
NE Network Element
NGN Next Generation Network
NSM Network Service Module
OC Output Control
OMD Output Message Description
OSPF Open Shortest Path First
PE1C Primary rate E1 Interface Card
PCM Pulse Code Modulation
PL Process Loader
PM Process Manager
POTC Plain Old Telephony Card
POTS Plain Old Telephony Service
PSH POTS Subscriber Handler
PAGE : 3-2 SM0-000-S00050(V1.0)
Chapter 3. Appendix
PSTN Public Switched Telephone Network

QAM Quadrature Amplitude Modulation
RADI Remote Access Device Interface
RS Remote System
RTP/RTCP Real Time Protocol / Real Time Control Protocol
SC System Check
SCA Status Control Agent
SCSR System Control & Subsystem Interface Rack
SCTM Subscriber Control & TSL interface Module
SHM Shell Manager
SICC STM-1 Interface & Control Card
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
SSC System Status Control
STCC Subscriber Test Card
STM Synchronous Transfer Mode
STS Status
TAM Total Access Module
TDM Time Division Multiplexer
TDMH Telephony Device Maintenance Handing
TM Traffic Management
TMS TAM Manager System
UIss User Interface SubSystem
UISFss User Interface Server Function SubSystem
V5I V5.2 Interface
V5RC V5.2 Rear Card
VDSL Very high data rate Digital Subscriber Line
VLAN Virtual Local Area Network
VPC V5.2 Protocol Control
VPI V5.2 Protocol Interface
VPIC V5.2 Protocol Interface Card
VSLC VDSL Subscriber Line Card
SM0-000-S00050(V1.0)
TAM-CS1000
(Access Gateway)
System Description
Copyright © 2004 LG Electronics Inc.
All Rights Reserved
The copyright of this Manual belongs to LG Electronics Inc.
Any reproduction, redistribution, or modification of this Manual
without prior written approval of LG Electronics Inc. is expressly
prohibited.
This Manual is subject to change by LG Electronics without prior
notification for the purpose of function improvement or design
change of the product.

http://www.lge.com

TAM-CS1000 System Description

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

TAM-CS1000 System Description

Enviado por

Direitos autorais:

Formatos disponíveis

TAM-CS1000

This section describes the meaning of symbols used in this manual.

Danger: Ignoring these warning results in an imminent danger such as death or

The copyright of this Manual belongs to LG Electronics Inc.

LG Electronics and are the registered trademarks of LG Electronics Inc.

Copyright © 2004 LG Electronics, Inc. All Rights Reserved

Version Date Reason Description

1.0 2005/05/25 Initial Issue

Chapter 1. TAM Overview .................................................................1-1

Chapter 2. TAM Architecture and Configuration ............................2-1

2.4.3 Fault Handling Function .................................................................................................. 2-58

Chapter 3. Appendix .........................................................................3-1

Introduction to the Manual

This Manual is intended for the TAM developers and operators.

This Manual is composed as follows:

Chapter 2 System Architecture and Configuration

Chapter 1. TAM Overview

1.1 TAM Configuration

(1) Host Mode

- Installed in various locations such as CO/remote CO/APT/biz. Buildings, to accommodate

- Installed in various remote locations such as remote CO/APT/business buildings, to accommodate

- Applied as a remote system of TAM-HS, to accommodate remote subscribers.

Subscriber Types Provided by the System

(4) Leased lines

1.1.1 Applied Network Configurations

TAM can be applied for the following purposes:

1) To replace the local exchange in CO and remote COs

2) To accommodate voice subscribers in apartment complexes and business buildings

3) To accommodate VDSL subscribers in the areas near the CO area

4) To replace VDSL subscribers in apartment complexes and business buildings

5) To accommodate Ethernet subscribers in the areas near the CO area

6) To accommodate Ethernet subscribers in apartment complexes and business buildings

1.1.2 Elements to Configure Application Network

The applied network is configured with the following network elements.

PAGE : 1-2 SM0-000-S00050(V1.0)

TAM-CS1000 (Host Mode)

Installed in various locations such as CO/remote CO/APT/business building, TAM-CS1000 (Host

TAM-CS1000 (RS Mode)

Local Exchange (LE)

Element Management System (EMS)

1.1.3 Network Configurations

1) For replacing the LE

2) For accommodating VDSL subscribers

- Near the CO area

- Near the CO area

H.248/Megaco E1/V5.2 E1/V5.2

[Figure 1-1] Network Configuration for Replacing the LE

PAGE : 1-4 SM0-000-S00050(V1.0)

[Figure 1-2] VDSL subscriber

[Figure 1-3] Network Configuration for Accommodating Ethernet Subscribers

PAGE : 1-6 SM0-000-S00050(V1.0)

1.2 System Specifications

1.2.1 TAM-CS1000 (Host Mode)

Specification Capacity Remarks

POTS Max. 1,024

Voice CODEC G.711,723.1, 729a/b 256 Channel

Indoor Housing Provided

1.2.2 TAM-CS1000 (RS Mode)

Specification Capacity Remarks

Indoor Housing Provided

System Height (mm) Width (mm) Depth (mm)

1.3.1 TAM-CS1000 (Host & RS Mode)

[Figure 1-7] TAM-CS1000 Indoor Housing– Front and Rear Views