SDX-MSC Ii SD

SDX-MSC II
System Description
EBBD-014116
Ed. 00
10. 2002.
COPYRIGHT
This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright. No
information contained herein may be copied, translated, transcribed or duplicated for any
commercial purposes or disclosed to third parties in any form without the prior written consent of
SAMSUNG Electronics Co., Ltd.
TRADEMARKS
SDX-MSC II is registered trademark of SAMSUNG.
Product names mentioned in this document may be trademarks and/or registered trademarks of
their respective companies.
This manual should be read before the installation and operation, and the operator should correctly install
and operate the system by using this manual.
This manual may be changed for the system improvement, standardization and other technical reasons without prior
notice.
For further information on the updated manual or have a question the content of manual, contact Document Center at
the address below .
Address : 442-742 Document Center 2th Fl. IT Center. 416 Metan-3dong Paldal-gu, Suwon-si, Gyeonggi-do,
Korea
e-mail : manual@samsung.com
Or contact Call Center at the telephone below if you have any questions or concerns regarding the operation of your
system.
Phone : 81-1588-4141
http://www.samsungnetwork.com
2002 SAMSUNG Electronics Co., Ltd. All rights reserved.
INTRODUCTION
Purpose
This description explains the functions, features and configuration of the switching
function on the CDMA network.
Audience
This description is written for an engineer who requires an understanding of the
SDX-MSC II system operator and SDX-MSC II system.
Document Content and Organization

This manual is organized and separated into seven chapters as follows :
Chapter 1. SDX-MSC II Introduction
This chapter describes the introduction of the SDX-MSC II.

Configuration of the Samsung CDMA network
Major functions, specifications and features of the SDX-MSC II
Basic architecture and configuration of the SDX-MSC II
Chapter 2. Hardware Architecture
This chapter describes the hardware of the SDX-MSC II.

Hardware configuration by function.
Page I
Introduction
Page II
SDX-MSC II System Description/Ed.00
Hardware type, function and detailed configuration that perform the control.
Hardware type, function and detailed configuration that perform the switching.
Hardware type, function and detailed configuration for performing the network
synchronization.
Hardware type, function and detailed configuration for performing the trunk and
subscriber interface.
Hardware type and function for performing other systems
SDX-MSC II System Description/Ed.00Introduction
Introduction
Chapter 3. Software Architecture
This chapter describes the SDX-MSC II software.

Software features and basic architecture.
Application software functions.
Chapter 4. Call Processing and Mobile Management
This chapter describes the call processing and mobile management of the SDX-MSC
II.
Subscriber classification, number system and number decoding procedure.
Routine outline, routine method and routine application.
Authentication and encryption procedure.
Outline of location registration, type and procedure.
Mobile call control and call processing.
Type and procedure of handoff.
Call processing in status of overload.
Chapter 5. Operation and Maintenance
This chapter describes the operation and maintenance of the SDX-MSC II.
Billing/Charging.
Statistics.
Network management and overload control.
Chapter 6. Supplementary Service
This chapter describes the supplementary service provided in the SDX-MSC II.
Supplementary type and outline.
Supplementary service and outline.
Alternative performance among service.
Chapter 7. VLR
This chapter describes the VLR build-into the SDX-MSC II.

Alternative working between the VLR and HLR, VLR and MSC, VLR and
VLR.
Data types stored in the VLR.
Performance in the VLR.
Page III
Introduction
Page IV
Troubleshooting when a database fault occurs for the VLR.
SDX-MSC II System Description/Ed.00Introduction
Introduction
Conventions
The following special paragraphs are used in this document to point out information.
This information may be set-off from the surrounding text.
NOTE
Indicates additional information as a reference
Revision History
EDITION
DATE OF ISSUE
REMARKS
00
10.2002
First Draft
Page V
Introduction
This page intentionally left blank
Page VI
TABLE OF CONTENTS
INTRODUCTION
Purpose................................................................................................................................. I
Audience................................................................................................................................ I
Document Content and Organization.....................................................................................I
Conventions......................................................................................................................... III
Revision History................................................................................................................... III
CHAPTER 1. SDX-MSC II Introduction

1
Mobile Communication Network Configuration............................................................1-2
Functions of the SDX-MSC II.......................................................................................... 1-5
Specifications of the SDX-MSC II...................................................................................1-6
Features of the SDX-MSC II............................................................................................. 1-8
Configuration of the SDX-MSC II....................................................................................1-9
CHAPTER 2. Hardware Architecture

1
ASS Architecture............................................................................................................. 2-2

1.1
DTI Block.................................................................................................................. 2-4
1.2
PRI Block.................................................................................................................. 2-5
1.3
SLI Block................................................................................................................... 2-6
1.4
TSL Block.................................................................................................................. 2-7
1.5
DSC Block................................................................................................................. 2-9
Page VII
Table of Contents
1.6
FPH Block............................................................................................................... 2-10
1.7
S7H Block............................................................................................................... 2-11
1.8
MVQT Block............................................................................................................ 2-12
1.9
ASP/ASPP Block..................................................................................................... 2-13
INS System..................................................................................................................... 2-14

2.1
SSL Block................................................................................................................ 2-16
2.2
CIN Block................................................................................................................ 2-18
2.3
NES Block............................................................................................................... 2-19
2.4
INP Block................................................................................................................ 2-20
2.5
INPP Block.............................................................................................................. 2-21
CCS Architecture........................................................................................................... 2-22

3.1
OMP Block.............................................................................................................. 2-23
3.2
APC Block............................................................................................................... 2-24
3.3
CCPP Block............................................................................................................ 2-25
LRS Structure................................................................................................................. 2-26

4.1
LRP Block.................................................................................................................. 26
The Processor Structure............................................................................................... 2-28

5.1
MP ....................................................................................................................... 2-28
5.2
PP
5.3
Processor Configuration of Each Subsystem..........................................................2-29
....................................................................................................................... 2-29
Others............................................................................................................................. 2-32
6.1
Remote Alarm Panel Unit (RAPU)..........................................................................2-32
6.2
Auxiliary Memory Unit............................................................................................. 2-32
6.3
Input/Output Device................................................................................................ 2-32
CHAPTER 3. Software Architecture

1
Features of the Software................................................................................................. 3-1
Software Architecture...................................................................................................... 3-3
Page VIII
Table of Contents
CHAPTER 4. Call Processing and Mobility Managment

1
Number Translation and Sending...................................................................................4-1

1.1
Mobile Communication Subscribers Numbering System..........................................4-1
1.2
Call Processing Related Information.........................................................................4-2
1.3
MSC Number Translating and Sending.....................................................................4-4
Routing and Other Carrier Roaming..............................................................................4-6

2.1
Routing System......................................................................................................... 4-6
2.2
Routing Applications................................................................................................. 4-6
Page IX
Table of Contents
Security Procedures (Authentication and Encryption)...........................................................4-8

3.1
General Matters........................................................................................................ 4-8
3.2
Authentication......................................................................................................... 4-10
3.3
Encryption............................................................................................................... 4-12
Location Registration.................................................................................................... 4-13

4.1
Introduction............................................................................................................. 4-13
4.2
Types of Location Registrations..............................................................................4-13
4.3
Location Registrations.............................................................................................4-15
Mobile Communication Subscriber Call Processing.......................................................4-17

5.1
Call Processing Functions.......................................................................................4-17
5.2
Controls of the Incoming and Outgoing Calls..........................................................4-18
5.3
Call Release............................................................................................................ 4-20
Handoff........................................................................................................................... 4-21
6.1
Handoff Functions of the MSC................................................................................4-21
6.2
Handoff Classification.............................................................................................4-23
CHAPTER 5. Operations and Maintenance

1
Billing/Charging............................................................................................................... 5-1
1.1
Collection of Billing Data........................................................................................... 5-1
1.2
Control of Billing Information.....................................................................................5-2
1.3
Operations of Billing Storage Media..........................................................................5-3
1.4
Operations of Billing Operation Modes.....................................................................5-4
1.5
Billing Backup........................................................................................................... 5-5
1.6
Billing for Each Type of Call......................................................................................5-5
Statistics........................................................................................................................... 5-6
2.1
Statistics Collection Types........................................................................................ 5-6
2.2
Statistics Storing and Sending..................................................................................5-9
Network Management.................................................................................................... 5-10
Overload Control........................................................................................................... 5-12
Audit............................................................................................................................... 5-13
Page X
Table of Contents
CHAPTER 6. Supplementary Service Functions

1
Supplementary Functions............................................................................................... 6-1
Interactions Between Service Functions.......................................................................6-9
Page XI
Table of Contents
CHAPTER 7. VLR Functions

1
Interactive Operation....................................................................................................... 7-1
Types of Data within the VLR.......................................................................................... 7-2
Functions.......................................................................................................................... 7-4
ABBREVIATION
A ~ C................................................................................................................ Abbreviation-1
D ~ E................................................................................................................ Abbreviation-3
G ~ F................................................................................................................ Abbreviation-4
L ~ M................................................................................................................ Abbreviation-5
N
................................................................................................................ Abbreviation-6
O ~ R............................................................................................................... Abbreviation-7
S
................................................................................................................ Abbreviation-8
................................................................................................................ Abbreviation-9
U ~ X.............................................................................................................. Abbreviation-10
Page XII
Table of Contents
LIST OF FIGURES
Figure 1.1 Shape of the SDX-MSC II...............................................................................1-1
Figure 1.2 Mobile communication network configuration.................................................1-4
Figure 1.3 Configuration of the SDX-MSC II....................................................................1-9
Figure 2.1 ASS architecture............................................................................................. 2-3
Figure 2.2 Diagram of DTI Block Mounting......................................................................2-4
Figure 2.3 Diagram of PRI block mounting......................................................................2-5
Figure 2.4 Diagram of SLI block mounting.......................................................................2-6
Figure 2.5 Diagram of TSL block mounting......................................................................2-7
Figure 2.6 Diagram of DSC block mounting.....................................................................2-9
Figure 2.7 Diagram of FPH block mounting...................................................................2-10
Figure 2.8 Diagram of S7H block mounting...................................................................2-11
Figure 2.9 Diagram of MVQT block mounting................................................................2-12
Figure 2.10 ASP/ASPP block mounting..........................................................................2-13
Figure 2.11 INS Structure...............................................................................................2-15
Figure 2.12 Diagram of SSL block mounting..................................................................2-16
Figure 2.13 Diagram of CIN block mounting...................................................................2-18
Figure 2.14 Diagram of NES block mounting..................................................................2-19
Figure 2.15 Diagram of INP block mounting...................................................................2-20
Figure 2.16 Diagram of INPP block mounting.................................................................2-21
Figure 2.17 CCS Architecture......................................................................................... 2-22
Figure 2.18 Diagram of OMP block mounting.................................................................2-23
Figure 2.19 Diagram of APC block mounting..................................................................2-24
Figure 2.20 Diagram of CCPP block mounting...............................................................2-25
Figure 2.21 Diagram of LRS Structure............................................................................2-26
Figure 2.22 Diagram of LRP block mounting..................................................................2-26
Figure 2.23 Structure of the MP and OMP......................................................................2-28
Figure 2.24 PP Structure................................................................................................ 2-29
Figure 2.25 SDX-MSCII Processor Configuration...........................................................2-29
Figure 3.1 Software Functions Structure..........................................................................3-3
Figure 4.1 The numbering system of mobile communication subscribers........................4-1
Figure 4.2 Generation of Identity & Authentication and Encryption Data.......................4-10
Page XIII
Table of Contents
Figure 4.3 Originating & Terminating Procedures..........................................................4-18

Figure 4.4 Call Release Procedures..............................................................................4-20
Page XIV
Table of Contents
LIST OF TABLES
Table 1.1 Relation between rack, subsystem and function block mounting...................1-10
Table 2.1 Configurations and functions of the DTI block..................................................2-4
Table 2.2 PRI block configuration and functions..............................................................2-5
Table 2.3 SLI block configuration and functions...............................................................2-6
Table 2.4 TSL block configuration and functions..............................................................2-8
Table 2.5 DSC block configuration and functions.............................................................2-9
Table 2.6 FPH block configuration and functions...........................................................2-10
Table 2.7 S7H block configuration and functions...........................................................2-11
Table 2.8 MVQT block configuration and functions........................................................2-12
Table 2.9 ASP/ASPP block mounting and functions.......................................................2-13
Table 2.10 SSL block configuration and functions...........................................................2-17
Table 2.11 CIN block configuration and functions...........................................................2-18
Table 2.12 NES block configuration and functions..........................................................2-19
Table 2.13 INP block configuration and functions...........................................................2-20
Table 2.14 INPP block configuration and functions.........................................................2-21
Table 2.15 OMP block configuration and functions.........................................................2-23
Table 2.16 APC block configuration and functions..........................................................2-24
Table 2.17 CCPP block configuration and functions.......................................................2-25
Table 2.18 LRP block configuration and functions..........................................................2-27
Table 5.1 Disk Capacities................................................................................................. 5-3
Table 6.1 Interactions between Service Functions...........................................................6-9
Page XV
CHAPTER 1
SDX-MSC II Introduction
The SDX-MSC II is a Mobile Switching Center (MSC) performing an exchange

function to provide mobile communication services.
The SDX-MSC II has adopted an open architecture that has functionally modularized
hardware and software, and has been designed to improve systems in flexible ways in
accordance with technological development.
In addition, the SDX-MSC II has minimized the system changes for expansion and
reduction of system capacity, and can properly change the capacity depending upon
the variety of network environments.
Figure 1.1 Shape of the SDX-MSC II
Page 1-1
CHAPTER 1
1
Mobile Communication Network Configuration

The CDMA2000 1X mobile communication network consists of the following
Network Elements (NEs) :
Mobile Switching Center (MSC)
The MSC is placed at the center of the mobile communication network and
interworks with other networks (i.e. PSTN, PLMN, PSPDN and Internet, etc).
The MSC interfaces with the Base Station Controller (BSC) to transmit and receive
signals and voice data to and from the mobile communication terminals.
In addition, the MSC exchanges information with Home Location Register (HLR) and
Visitor Location Register (VLR) which store the subscribers information.
Base Station Controller (BSC)
The BSC interfaces with several Base Station Transceiver Systems (BTSs) and
provides a handoff process among the cells, call control and BTS operation and
maintenance, etc. The BSC and the MSC interface through the No. 7 link.
Base Station Transceiver System (BTS)
The BTS communicates with the Mobile Station (MS) in the cell(the area on which
the BTS has influence) over the radio system, and provides subscribers with mobile
communication services. The BTS performs coding and decoding of radio channels
to transmit and receive radio signals to and from the MS. To provide good quality and
economical radio calls to the subscribers, the BTS controls the transmitting and
receiving of signals intensity and measures the up-links quality, controls space
diversity, radio resources and maintains itself.
Visitor Location Register (VLR)
The VLR temporarily stores and controls all of the MS information, which exists in
the area controlling itself. When the mobile communication subscribers set calls, the
Page 1-2
CHAPTER 1. System Introduction
VLR transmits the subscriber related information to the MSC.

The VLR always retains its control data the same as the HLR.
Home Location Register (HLR)
The HLR is a database control system that stores and controls the subscribers
parameters and location information regarding all the MSs registered in its own area.
The HLR controls important data, such as terminals access capabilities, basic services
and supplementary services etc, and performs routing for the called party.
Page 1-3
Data Core Network (DCN)
The DCN interfaces with either the Internet or Packet Switched Public Data Network
(PSPDN) to provide the mobile communication subscribers with packet data services.
DCN consists of Packet Data Serving Node (PDSN), Packet Data Gateway Node
(PDGN) and Authentication, Authorization, Accounting (AAA) Server, etc.
Page 1-4
SDX-MSC II /Ed.00
1 . SDX-MSC II
PSTN
HLR
BSM
MSC
AIWF
BSC
BTS
PDSN
DCN
BTS
Internet
MS
MS
Figure 1.2 Mobile communication network configuration
Page 1-5
Functions of the SDX-MSC II

Based on a circuit exchange system, the SDX-MSC II performs the following
functions to process the mobile subscribers calls.
System and Network Interface
The SDX-MSC II interfaces with the BSC to transmit and receive traffic data of the
mobile communication subscribers, and also interfaces with the PSTN, the ISIN and
PLMN, etc to transmit to and receive data from, other networks. In addition, the
SDX-MSC II interworks with the AIWF to process the circuit data calls. Accordingly,
the mobile communication subscribers can use modem based data communication
and fax Tx/Rx services.
Routing and Other Providers Roaming
The SDX-MSC II performs routing of calls coming from other service

networks(PSTN, ISDN and PSMN), or roaming of calls coming from other
providers networks.
To do so, the SDX-MSC II inquires on the routing number information that the HLR
has assigned at the incoming terminal, and informs the calling partys exchange of it.
In addition, the SDX-MSC II analyzes the originating call information that the
mobile terminal in the area transmits, and interworks with the terminating party
exchange to perform the routing or roaming of the calls.
Handoff Processing
The SDX-MSC II supports handoff processing when the mobile communication

terminals move between cells. In other words, the SDC-MSC II supports handoff
between the BTSs, between the BSCs and between the MSCs.
Visited Location Register (VLR)
The SDX-MSC II has a built-in Visited Location Register(VLR) function. Therefore,

the SDX MSC II interworks with the HLR to control information on the mobile
communication terminals within the MSC area and performs location registration.
Page 1-6
Authorization and Encryption
The SDX-MSC II performs authorization and decoding functions to verify legality of

the mobile communication subscribers services, and to prevent calls from being
tapped. To do so, the SDX-MSC II interworks with internal VLR and HLR to analyze
the subscribers permissions for use and the subscribers service registration status,
and to provide encryption of traffic data and signals.
Page 1-7
Supplementary Service Functions
To provide various Supplementary services, the SDX-MSC II interworks with

various systems of the CDMA2000.
Specifications of the SDX-MSC II

Capacity
Classification
Capacity
BSC interface modules
Max. 12
Mobile communication subscribers accommodation
Max. 500,000 subscribers
Cable system subscriber accommodation capacity
Busy Hour Call Attempt(BHCA)
Max. 1,250,000 BHCA
Call processing capacity
38,500 Erlang
VLR capacity
Telephony Specification
Classification
Dimensions
Switch network structure
T-S-T
Time switch capacity
4K 6K
Space switch capacity
80K 80K
Controlling Method
Classification
Page 1-8
Controlling method
Controlling method
Distributed control
Processor
MC 68060, MC 68360
Programming language
CHILL, C
Interface Specifications
Classification
MSC/PSTN interface
MSC/MSC interface
MSC/BSC interface
MSC/HLR interface
MSC/IWF interface
MSC/AMPS interface
MSC/CAMA interface
MSC/VMS & FMS interface
MSC/OMC interface
MSC/WIN interface
Specifications
Digital interface
T1/E1
Signal specifications
CSS NO.7, R2
Digital interface
T1/E1
IS-41C,D,E
Digital interface
T1/E1
IS-634-A,B(or TSB-80), IOS4.x
Digital interface
T1/E1
IS-41D,E
Digital interface
E1
PRI, frame relay
Digital interface
T1/E1
ANSI CCS NO.7, IS-41
Digital interface
Dedicated Lines
TCP/IP, X.25 Protocol
Digital interface
T1/E1
CCS No.7(ISUP)
Digital interface
Dedicated Lines
TCP/IP, TMN-Q3
Digital interface
T1/E1
CCS No.7, IS-41D,E(IS-771)
Equipment Specifications
Classification
Equipment dimensions
Rack dimensions
800 mm(W) 650 mm(D) 1,709 mm(H)a
a. Height length excludes top unit(110 mm) and foot(70 mm).
Power System Specifications
DC -48 Vdc nominal(-43.5~-56V variable)

DC -60 Vdc nominal(-48~-72V variable)
Built-in battery
Page 1-9
Page 1-10
Features of the SDX-MSC II

The SDX-MSC II has the following features :
Distributed Control System
The SDX-MSC II control system has a multiplex processor structure with microprocessors
(2-layer hierarchy where the upper layer processor controls the lower layer
processor). The Main Processor (MP) performs the upper layer functions, such as
mobile communication call process, number translation, exchange controls, system
operation and maintenance, etc. The Peripheral Processor (PP) performs the lower
layer functions for real time processes, such as telephony monitoring, analysis and
signal process, etc.
The SDX-MSC II can easily add new functions and expand the capacity owing to the
distributed functions into the main and peripheral processors. Therefore, when some
functions fail, the SDX-MSC II can minimize the influence on other functions.
Parallel Processing Operation System
Digital exchange system shall perform concurrent processing of hundreds of real-time

processes.
To handle processes effectively, the SDX-MSC II has adopted a Concurrent Real-time
Operating System (CROS) using the CCITT High-Level Language (CHILL) that
supports the parallel system.
Use of CHILL/SDL Programming Languages
To improve software productivity and maintenance capabilities, the SDX-MSC II can

program software using both the CHILL language and System Description Language
(SDL).
DBMS (Database Management System)
The SDX-MSC II controls generation, modification and deletion of various data

using the DBMS. Data control using the DBMS has the following advantages :
1) Effective control of data variations 2) Reduced replicated data, and 3) Smooth
system operation due to a standardized data expression.
Page 1-11
Redundancy
The SDX-MSC II has made major facilities redundant, such as processors,

communication networks between processors, switch system, data link and network
synchronization equipment, etc.
The SDX-MSC II has adopted a redundancy system of active-standby, load sharing
and n+k, etc.
Page 1-12
Configuration of the SDX-MSC II

The SDX-MSC II consists of following racks :
ASS-T, ASS-W, ASS-W/T
SDX-MSC II
ASCR-T
SDX-MSC II
ASSASCR-
SDX-MSC II
ASCR-P
ASS-C
SDX-MSC II
SLIR
SDX-MSC II
ASCR-C
DTI
2
DTI
DTI
DTI
DTI
PRI
PRI
PRI
PRI
3
DTI
2
DTI
3
DTI
2
PRI
3
PRI
0
DTI
1
DTI
0Air Baffle 1
0Air Baffle1
DSC
DSC
TSL
(4K)
TSL
(4K)
S7H FPH
S7H FPH
ASP/ASPPX3
0Air Baffle 1
DSC
TSL
(4K)
SSWR
SDX-MSC II
DSC
SLI
(ASI:1024
)
ASP/ASPPX3
ASP/ASPPX3
LRS
SSWR
SDX-MSC II
CNIR
SDX-MSC II
CCS
LRIR
SSL 14
SSL 12
SSL 10
LRP
LRP
SSL 04
SSL 02
SSL 00
LRP
LRP
Air Baffle
Air Baffle
Air Baffle
SSL 13
SSL 11
SSL 03
SSL 01
CIN(IPC)
TSL
(4K)
S7H FPH
INS
SDX-MSC II
MV
QT
S7H FPH
ASP/ASPPX3
0Air Baffle1 1
Air Baffle
Air Baffle
SDX-MSC II
CCIR
APC
Air Baffle
LRP
LRP
CC INP
NESD PP P
X2
LRP
LRP
INP
SDUX3
LRP
LRP
OM
DKUX
PO
Figure 1.3 Configuration of the SDX-MSC II
Page 1-13
Table 1.1 Relation between rack, subsystem and function block mounting
Name of rack
Subsystem a
Function blocks a
ASCR-W/T, T, P, C
ASS
DTI, PRI, DSC, S7H, FPH, TSL, ASP, ASPP
SLIR
ASS
SLI, MVQT
SSWR
INS
SSL
CNIR
INS
SSL, CIN
LRIR
LRS
LRP
CCIR b
CCS
OMP, CCPP, APC
INS
INP, INPP, NES
a. For more information on the subsystem and function block, refer to Chapter 2 Hardware Architecture.
b. The DKU and SDU, which are auxiliary memory units, are also mounted on the CCIR.
Page 1-14
CHAPTER 2
Hardware Architecture
The SDX-MSC II consists of subsystems, such as the CCS, INS, LRS and ASS etc,
and each subsystem includes various function blocks.
Access Switching Subsystem (ASS)
The ASS performs the interfacing between the SDX-MSC II and external systems,
time switching, processing of most calls and number translating, etc.
The ASS is classified as follows depending upon the interface functions :
ASS-W/T(Access Switching Subsystem-Wireless Subscriber/Trunk) : BSC
interface and trunk line interface.
ASS-P(Access Switching Subsystem-Primary Rate Interface) : Interworking
Function(IWF) interface.
ASS-C(Access Switching Subsystem-Complex) : Analog system subscriber
interface, trunk line interface and IWF interface, etc.
Interconnection Network Subsystem (INS)
The INS connects each subsystem using space switches and performs centralized call
processing. In addition, the INS controls the Inter Processor Communication (IPC)
that is transmitted to and received from each subsystem, and generates and distributes
the system clock.
Central Control Subsystem (CCS)
The CCS performs operating and maintaining functions of the SDX-MSC II, such as
billing, statistics, configuration controlling, fault handling, storage and database
controlling, etc.
Page 2-1
LRS (Location Registration Subsystem)
The LRS stores and manages mobile communication subscriber information within the
MSC area concerned, and interworks with the HLR to authorize mobile
communication subscribers and to register locations.
The SDX-MSC II consists of one INS, one CCS, one LRS and up to 20 ASS.
Page 2-2
SDX-MSC II /Ed.00
2 .
ASS Architecture
The ASS consists of following function blocks :
Digital Trunk Interface (DTI) W T C
Primary Rate Interface (PRI) P C
Subscriber Line Interface (SLI) C
Time Switch & Link (TSL) W T C P
Digital Service Circuit (DSC) W T C P
Frame Relay & Packet Handler (FPH) W T C P
Signaling system No.7 protocol Handler (S7H) W T C P
Mobile Voice Quality Test (MVQT) C
Access Switching Processor/Access Switch Peripheral Processor (ASP/ASPP)
WTCP
Page 2-3
2 .
PSTN, BSC
D
T
I
SDX-MSC II /Ed.00
ASP
ASPP3
CDTIA 0
TDCMA A
P - Bus
MPDMA A
TD - Bus
CDTIA 7
Control TSL
Control DTL, FPH, DSH, SLI, PRI
D
S
C
T
S
L
DSVMB 0
IWF
P
R
I
IPCIA 0
IDCPA A
DSVMB 1
SMDXA
0A
Wire
subscriber
CALIA 31
SCCIA A
RSGUA A
DSCMA 1
DSMSA 0
0B
DSMSA 2
DSDTA
OTRMA A
F
P
H
1B
FPHCA 0
FPHCA 4
FPRCA A
S
7
H
SSPHA 0
SSPHA 3
B
SSL Plane 0
0B
OTRMA A
TSCMA A
SMDXA
1A
CALIA 0
DSCMA 0
LTRMA
0A
IPCIA 7
S
L
I
LTRIMA
1A
OTRMA A
1B
M
V
QT
OTRMA A
MVQTA 0
SSL Plane 1
MVQTA 3
Figure 2.1 ASS architecture
Page 2-4
Page 2-5
1.1
DTI Block
The DTI block interfaces with an E1 or T1 trunk line and Tx/Rx data to and from the
TSL. The network synchronization clock is received from the TSL and transmits
signals of the trunk to the TSL.
The DTI block consists of :
Digital Trunk Back Panel Assembly (DTBPA)
CEPT Digital Trunk Interface board Assembly (CDTIA)
T1 Digital Trunk Interface board Assembly (TDTIA)
SDX-MSC II
ASCR-T
SDX-MSC II
ASCR-C
DTI
DTI
CDTIA 6
CDTIA 7
DTI
CDTIA 4
CDTIA 5
DTI
CDTIA 2
CDTIA 3
DTI
CDTIA 0
CDTIA 1
DTBPA
DTI
Figure 2.2 Diagram of DTI Block Mounting
Table 2.1 Configurations and functions of the DTI block

Board
Number
Functions
of boards
DTBPA
DTI block rear board
CDTIA
Interfaces with the PCM trunk line of the E1(T1) mode :
(TDTIA) a
Interfaces with four(or five) E1s(T1s) per board : 32 E1 / block?

..128 E1 / bay?
Receives network synchronization clock from the TSL :
Receives PCM signals from the trunk line and extracts the 2.048 MHz
(1.544 MHz) signals from that signal to transmit it to the TSL.
a. The TDTIA is a board to be mounted on the DTI block when interfacing with a T1 mode trunk line.
Page 2-6
Contents in parentheses indicate available functions when the TDTIA board is mounted.
Page 2-7
1.2
PRI Block
The PRI block has interface functions to provide the mobile communication system
subscribers with circuit exchange data communication services. To accommodate
more capacity, two paths connected to the IWF are mounted on one PRI block.
The PRI block consists of :
ISDN Primary Subscriber Back Panel Assembly (IPBPA)
ISDN D-channel Control Processor Advanced (IDCPA)
ISDN Primary Subscriber CEPT Interface type A (IPCIA)
SDX-MSC II
ASCR-P
SDX-MSC II
ASCR-C
IPCIA 4
IPCIA 5
IPCIA 6
IPCIA 7
IPCIA 1
IPCIA 2
IPCIA 3
IPCIA 7
IPCIA 0
IPCIA 6
IPCIA 3
IDCPA B
IPCIA 5
IPCIA 2
IDCPA A
IPCIA 4
IPCIA 1
PRI
PRI
IDCPA B
PRI
PRI
IPCIA 0
PRI
IDCPA A
IPBPA
PRI
Figure 2.3 Diagram of PRI block mounting
Table 2.2 PRI block configuration and functions

Board
Number of
Functions
boards
IPBPA
PRI block rear board
IDCPA
4(redundancy
Tx/Rx data to and from the TSL block :
Controls the IPCIA board under the control of the ASPP :

Controls eight IPCIAs per board :
Receives clocks from the TSL to use.
IPCIA
16
Tx/Rx data to and from the IWF.
a. One path connected to the IWF consists of 2 EA of the IDCPA board and 8 EA of the IPCIA board, so the
PRI block has two paths that are connected to the IWF.
Page 2-8
Page 2-9
1.3
SLI Block
The SLI block has an interface function with cable subscribers for testing (up to
1,024) and consists of :
Subscriber Interface Back Panel Assembly (SIBPA)
Subscriber Circuit Control Interface Assembly (SCCIA)
Compact Analog Line Interface Assembly (CALIA)
Ring Signal Generator Unit Assembly (RSGUA)
CALIA13
CALIA14
CALIA15
CALIA29
CALIA30
CALIA31
RSGUA
CALIA11
CALIA12
CALIA27
CALIA28
RSGUB
CALIA10
CALIA7
CALIA23
CALIA26
CALIA6
CALIA22
CALIA9
CALIA5
CALIA21
CALIA8
CALIA4
CALIA25
CALIA3
CALIA20
CALIA24
CALIA2
CALIA0
CALIA1
SCCIA B
SCCIA A
CALIA19
SIBPA
SLIR
CALIA16
CALIA17
CALIA18
SDX-MSC II
SLI
(ASI:1024)
Figure 2.4 Diagram of SLI block mounting
Table 2.3 SLI block configuration and functions

Board
Number of
Functions
boards
SIBPA
SLI block rear board
SCCIA
2(redundancy
Controls the CALIA and the RSGUA under the control of the ASPP.
)
CALIA
32
Interfaces with the cable subscribers :

Interfaces with 32 cable terminals per board. 32 X 32 = 1024 terminal ?/ bay ?
RSGUA
2(redundancy
Provides cable subscribers with ring signals.
Page 2-10
1.4
TSL Block
The TSL block performs the time switch (4K x 6K) functions and consists of :
Time Switch Back Panel Assembly (TSBPA)
Sub-highway Multiplex & Demultiplex Assembly (SMDXA)
Time Switch Control & Maintenance Assembly (TSCMA)
Local optic Transceiver Interface Assembly (LTRIA)
Optic Transceiver Module Assembly (OTRMA)
TSPBA
ASCR-T
LTRIA 1B
LTRIA 1A
TSBPA
SPA-B
SDX-MSC II
OTRMA
SMDXA 1A
SMDXA 1B
LTRIA 0A
SMDXA 0A
SMDXA 0B
SPA-B
TSL
LTRIA
LTRIA 0B
TSCMA A
TSCMA B
Front view
of rack
Rear view
of rack
Figure 2.5 Diagram of TSL block mounting
Page 2-11
Table 2.4 TSL block configuration and functions

Board
Number of
Functions
boards
TSBPA
TSL block rear board
SMDXA
4(redundancy)
Tx/Rx traffic data to and from the DTI, PRI and SLI :
Tx/Rx traffic data to and from the TSCMA board :
Each board takes charge of 2K data.
TSCMA
2(redundancy)
Inserts a call quality measuring pattern :

Interfaces with the DSC block to provide various signal processes and
supplementary services :
4K X 6K switching
LTRIA
4(redundancy)
Makes traffic and IPC data redundant and inversely redundant.

Takes charge of 2K data per board :
Provides an IPC path and distributes clocks received from the SSL.
Converts 155.52 Mbps data received from the OTRMA into 16.384 Mbps
data and transmits it to the TSCMA :
Converts 16.384 Mbps data received from the TSCMA into 155.52 Mbps
data and transmits it to the OTRMA.
OTRMA
8(redundancy)
Converts between electrical signals and optical signals :

Tx/Rx STM-1(155.520 Mbps) data :
2K data per board
Page 2-12
1.5
DSC Block
The DSC block is mounted on the ASS to provide a signal-processing function and
voice service. The DSC block handles the DTMF/R2-MFC signals and provides a
conference calling service and recording announcement service.
The DSC block consists of :
Digital Service circuit Back Panel Assembly (DSBPA)
Digital Service circuit for Voice Message Assembly (DSVMB)
Digital Service circuit for Call Mixer Assembly (DSCMA)
Digital Service circuit for Multi-frequency Signaling Assembly (DSMSA)
Digital Service circuit for Digital trunk Test Assembly (DSDTA)
SDX-MSC II
ASCR-T
DSVMB 0
DSVMB 1
DSCMA 0
DSCMA 1
DSMSA 0
DSMSA 1
DSMSA 2
DSDTA 0
DSBPA
DSC
Figure 2.6 Diagram of DSC block mounting
Table 2.5 DSC block configuration and functions

Board
Number
Functions
of boards
DABPA
DSC block rear board
DSVMB
Max. 8
Records, edits and plays recording announcement messages.
DSCMA
Max. 8
Conference calling
DSMSA
Max. 8
Tx/Rx DTMF/R2-MFC signals.
DSDTA
Max. 8
Tests digital trunk line.
Page 2-13
1.6
FPH Block
The FPH block interworks with the PRI block and provides mobile communication
subscribers with frame relay and packet service.
The FPH block consists of :
Frame relay & Packet protocol Back Panel Assembly (FPBPA)
Frame relay & Packet protocol Routing Controller Assembly (FPRCA)
Frame relay & Packet protocol Handling Controller Assembly (FPHCA)
FPHCA 2
FPHCA 4
FPHCA 0
FPBPA
FPRCA A
FPRCA B
ASCR-T
FPHCA 1
FPHCA 3
SDX-MSC II
FPH
Figure 2.7 Diagram of FPH block mounting
Table 2.6 FPH block configuration and functions

Board
Number of
Functions
boards
FPBPA
FPH block rear board
FPRCA
2(redundancy
Controls the FPHCA under the control of the ASPP :
Exchanges messages with the FPH mounted on other subsystems.
Handles the frame relay and Tx/Rx packet data using the TSL.
FPHCA
Page 2-14
1.7
S7H Block
The S7H block handles No.7 type of interoffice signaling.
The S7H block consists of :
Signaling System No.7 Protocol Handler Back Panel Assembly (SPBPA)
Signaling System No.7 Handler Assembly (SSPHA)
SDX-MSC II
ASCR-T
SSPHA 0
SSPHA 1
SSPHA 2
SSPHA 3
SPBPA
S7H
Figure 2.8 Diagram of S7H block mounting
Table 2.7 S7H block configuration and functions

Board
Number
Functions
of boards
SPBPA
S7H block rear board
SSPHA
Tx/Rx No.7 signaling data to the TSL block.
Page 2-15
1.8
MVQT Block
The Mobile Voice Quality Test(MVQT) block measures the quality of the voice path
of the mobile communication system. The MVQTA transmits specific data to the
BSS to measure the voice quality. The BSS receives data from the MVQTA and
transmits it back to the MVQTA via the Vocoder, Channel Element Block and
Transceiver Block, etc. The MVQTA measures voice quality between the MSC and
BSS using data received from the BSS.
The MVQT block consists of :
Digital Service circuit Back Panel (DSBPA)
Mobile Voice Quality Test Assembly (MVQTA)
SLIR
DPBPB
MVQTA 0
MVQTA 1
MVQTA 2
MVQTA 3
SDX-MSC II
MV
QT
Figure 2.9 Diagram of MVQT block mounting
Table 2.8 MVQT block configuration and functions

Board
Number
Functions
of boards
DSBPA
MVQT block rear board
MVQTA
Measures the voice quality between the MSC and BSS.
Page 2-16
1.9
ASP/ASPP Block
The ASP/ASPP block functions as the ASS processor (ASP : MP function and ASPP :
PP function) and consists of :
Main Processor Back Panel (MPBPB)
Main Processor Duplication Manager Assembly (MPDMA)
Telephony Device Control Master Assembly (TDCMA)
SDX-MSC II
ASCR-T
TDCMA B
TDCMA A
TDCMA B
TDCMA A
TDCMA B
TDCMA A
SPA-B
MPDMA B
MPDMA A
SPA-B
MPBPB
ASP/ASPPX3
Figure 2.10 ASP/ASPP block mounting
Table 2.9 ASP/ASPP block mounting and functions

Board
Number of
Functions
boards
MPBPB
ASP/ASPP block rear board
MPDMA
2(redundancy
ASP processor board
)
TDCMA
6(redundancy
ASPP processor board
SDX-MSC II Processor
For more information on the processor board, refer to section 5. Processor
Structure of Chapter 2. Hardware Architecture.
Page 2-17
INS System
The INS consists of :
Space Switch & Link (SSL)
Communication Interworking Network (CIN)
Network Synchronization (NES) CCS
Interconnection Network Processor (INP) CCS
Inter Network Peripheral Processor (INPP) CCS
Page 2-18
2
INPP2
TDCMA A
P - Bus
CIN
INP
MPDMA A
NES
CINMA A
NSCMA 0A
0B
NSCGA A
CINIA 0
TD - Bus
NSCMA 1A
CINIA 27
DOTS
Trunk
1B
U - Link
SSL, NES control
SSL, LRP, OMP
SSL 00
OTRMA A
ASS 0
OTRMA A
OTRMA A
ASS 1
OTRMA A
OTRMA A
ASS 2
B
CDPIA A
CTRIA 0A
0
B
SSMXA 0A
B
CTRIA 1A
0B
1
B
B
B
CTRIA 2A
OTRMA A
OTRMA A
ASS 3
OTRMA A
2
B
B
B
CTRIA 3A
B
1B
SSL 02
SSL 01
CTRIA 0~3
ASS 4
SSMXA 2A
SSMXA 1A
3
B
ASS 7
SSL 03
CTRIA 0~3
ASS 8
2B
ASS 11
SSL 04
CTRIA 0~3
ASS 12
Page 2-19
ASS 15
CTRIA 0~3
ASS 16
ASS 19
Figure 2.11 INS Structure
Page 2-20
2.1
SSL Block
The SSL Block is a Space Switch(80K x 80K) module and performs space switching
of the data received from several TSLs under the INPP control.
The SSL block consists of :
Space Switch Back Panel Assembly (SSBPA)
Central Optic Transfer & Receiver Interface Assembly (CTRIA)
Clock Distribution & Processor Interface Assembly (CDPIA)
Space Switch Matrix Assembly (SSMXA)
Optic Transceiver Module Assembly (OTRMA)
SSMXA 2B
SSMXA 2A
SSMXA 1B
CDPIA B
CDPIA A
CTRIA 3B
CTRIA 3A
CTRIA 2B
CTRIA 2A
CTRIA 1B
CTRIA 1A
SSL
CTRIA 0B
CTRIA 0A
SSL
SSMXA 1A
SSBPA
SSMXA 0B
SSWR
SSMXA 0A
SDX-MSC II
SSL
SSL
SDX-MSC II
CNIR
SSBPA
SSL
OTRMA
Rack
CTRIA
SSL
Rack rear
front
Figure 2.12 Diagram of SSL block mounting
Page 2-21
Table 2.10 SSL block configuration and functions

Board
Number of
Functions
boards
SSBPA
SSL block rear board
CTRIA
8(redundancy)
Makes traffic and IPC data redundant and inversely redundant :

2K data per board :
Receives 155.52 Mbps data from the OTRMA and converts it into 16.384
Mbps data, and then transmits it to the SSMXA board :
Receives 16.384 Mbps data from the SSMXA and converts it into 155.52
Mbps data, and then transmits it to the OTRMA board.
CDPIA
2(redundancy)
Receives clocks from the NSCGA of NES block and provides them to the
SSMAX and CTRIA.
SSMXA
6(redundancy)
Space switching under the control of the INPP :

Receives data from 8 EA of the CTRIA board :
Transmits data switched to 4 EA of the CTRIA board.
OTRMA
16(redundancy
Converts electrical signals and optical signals :
Tx/Rx of the STM-1(155.520 Mbps) data :

2K data per board
Page 2-22
2.2
CIN Block
The CIN block transmits IPC data between the subsystems.
The CIN block consists of :
Communication Interworking Back Panel Assembly (CIBPA)
Communication Interworking Node Interface Assembly (CINIA)
Communication Interworking Node Maintenance Assembly (CINMA)
SDX-MSC II
SDX-MSC II
CNIR
CIBPA
CNIR
CINIA 11
CINIA 11
CINIA 12
CINIA 12
CINIA 13
CINIA 13
CINIA 25
CINIA 25
CINIA 26
CINIA 26
CINIA 27
CINIA 27
SPA-CSPA-C
CINIACINIA
9
9
CINIACINIA
8
8
CINIA 22
CINIA 22
CINIA 10
CINIA 10
CINIACINIA
7
7
CINIA 21
CINIA 21
CINIA 24
CINIA 24
CINIACINIA
6
6
CINIA 23
CINIA 23
CINIACINIA
5
5
CINIA 20
CINIA 20
CINIACINIA
3
3
CINIA 17
CINIA 17
CINIACINIA
4
4
CINIACINIA
2
2
CINIA 16
CINIA 16
CINIA 19
CINIA 19
CINIACINIA
1
1
CINIA 18
CINIA 18
CINIACINIA
0
0
CINIA 15
CINIA 15
CINMA
CINMA
B B
CIN(IPC)
CINIA 14
CINIA 14
CINMA
CINMA
A A
SPA-CSPA-C
CIBPA
CIN(IPC)
Figure 2.13 Diagram of CIN block mounting
Table 2.11 CIN block configuration and functions

Board
Number of
Functions
boards
CIBPA
CIN block rear board
CINIA
28
Provides an IPC data transmission path transmitted/received between the

processors :
Provides four nodes per board(1 node provides 2 U-Links).
CINMA
2(redundancy
CIN processor board
Controls IPC network

Maintains CIN(informs the CCPP of failure of the CIN, if any).
Page 2-23
2.3
NES Block
The NES block generates and distributes clocks required for each system. Generation
and distribution of the clocks used in the SDX-MSC II are as follows :
1) The NES block receives a reference clock from the external system
(the DOTS and Trunk) and generates a base clock and provides it to the SSL.
2) The SSL receives clocks from the NES and generates clocks for the TSL and the
optical interface, and provides them to the TSL.
3) The TSL generates clocks required for each subsystem by itself based on the
clocks received from the SSL, and provides them to each block.
The TSL extracts clocks from the data received from trunk (the DTI and PRI) and
transmits them to the NES via the SSL. The NES uses the clocks that came from the
TSL, as reference clocks.
The NES block consists of :
Network Synchronization Back Panel Assembly (NSBPA)
Network Synchronization Clock Generation Assembly (NSCGA)
Network Synchronization Clock Maintenance Assembly (NSCMA)
SDX-MSC II
CCIR
NSCMA
1A
NSCMA
1B
NSCGA A
NSCGA B
NSCMA
0A
NSCMA
0B
NSBPA
NESD
Figure 2.14 Diagram of NES block mounting
Table 2.12 NES block configuration and functions

Board
Number of
Functions
boards
Page 2-24
NSBPA
NES block rear board
NSCGA
2(redundancy
Receives reference clocks externally(Trunk, DOTS, GPS, etc) and demultiplex
them into 4 KHz and provides them to the NSCMA. Provides basic clocks
(32.768 MHz) that came from the NSCMA, to the SSL block.
NSCMA
2.4
4(redundancy
Generates basic clocks using reference clocks received from the NSCGA,
and provides them to the NSCMA.
INP Block
The INP Block performs the functions of the Main Processor(MP) of the INS and
consists of :
Main Processor Back Panel (MPBPA)
Main Processor Duplication Manager (MPDMA)
SDX-MSC II
CCIR
SPA-B
MPDMA B
MPDMA A
SPA-B
MPBPA
INP
Figure 2.15 Diagram of INP block mounting
Table 2.13 INP block configuration and functions

Board
Number of
Functions
boards
MPBPA
INP Block rear board
MPDMA
2(redundancy)
INP processor board
SDX-MSC II Processor :
Page 2-25
Structure of Chapter 2. Hardware sturucture.
Page 2-26
2.5
INPP Block
The INP Block performs the functions of the Peripheral Processor (PP) of the INS,
and consists of :
Telephony Device Control Master Back Panel (TMBPA)
Telephony Device Control Master (TDCMA)
TMBPA
TDCMA A
TDCMA B
CCIR
TDCMA A
TDCMA B
SDX-MSC II
INPP
X2
Figure 2.16 Diagram of INPP block mounting
Table 2.14 INPP block configuration and functions

Board
EA/block
Functions
TMBPA
INPP block rear board
TDCMA
4(redundancy)
INPP processor board
Page 2-27
CCS Architecture
The CCS consists of the following blocks :
Operation & Maintenance Processor (OMP)
Alarm Panel Control (APC)
Central Control Peripheral Processor (CCPP)
OMP
RS 232C
MPDMA A
MSBIA A
SCSI
PC
CRT
DKU4
SDU3
U - Link
CIN
P - Bus
TD - Bus
CCPP
APC
TDCMA A
TD - Bus
APCIA A
External Alarm
Source
Figure 2.17 CCS Architecture
Page 2-28
3.1
OMP Block
The OMP block performs operation and maintenance and consists of the following
boards :
Operation & Maintenance processor Back Panel (OMBPA)
Main Processor SCSI-bus Interface (MSBIA)
SDX-MSC II
CCIR
SPA-B
MPDMA A
MSBIA
B
MSBIA
A MPDMA B
SPA-B
OMBPA
OMP
O
Figure 2.18 Diagram of OMP block mounting
Table 2.15 OMP block configuration and functions

Board
Number of
Functions
boards
OMBPA
OMP block rear board
MSBIA
2(redundancy
Provides the RS-232C port to interface with the PC, CRT and printer :
Provides the SCSI bus to interface with the DKU and SDU.
2(redundancy
OMP processor board
MPDMA
Page 2-29
3.2
APC Block
The APC Block collects alarms generated in the SDX-MSC II.
The APC Block consists of the following blocks :
Remote Control Back Panel Assembly (RCBPA)
Alarm Panel Control Interface Assembly (APCIA)
SDX-MSC II
CCIR
RCBPA
APCIA A
APCIA B
APC
Figure 2.19 Diagram of APC block mounting
Table 2.16 APC block configuration and functions

Board
Number of
Functions
boards
RCBPA
APC block rear board
APCIA
2(redundancy
Collects and reports alarms generated at the system.
Page 2-30
3.3
CCPP Block
The CCPP block collects information on faults and the environment, and consists of
following boards :
Telephony Device Control Master Back Panel (TMBPA)
Telephony Device Control Master (TDCMA)
SDX-MSC II
CCIR
TDCMA A
TDCMA B
TMBPA
CC
PP
Figure 2.20 Diagram of CCPP block mounting
Table 2.17 CCPP block configuration and functions

Board
Number of
Functions
boards
TMBPA
CCPP block rear board
TDCMA
2(redundancy
CCPP processor board
Page 2-31
LRS Structure
The LRS performs the VLR functions and consists of following function block :
Location Register Processor (LRP)
U - Link
CIN
LRP9
LRP0
MPDMA A
MPDMA A
Figure 2.21 Diagram of LRS Structure
4.1
LRP Block
LRP block consists of following boards :
Main Processor Back Panel (MPBPA)
SDX-MSC II
LRIR
LRP
Air Baffle
LRP
LRP
LRP
LRP
LRP
LRP
SPA-B
LRP
MPDMA B
LRP
MPDMA A
LRP
SPA-B
MPBPA
Figure 2.22 Diagram of LRP block mounting
Page 2-32
Table 2.18 LRP block configuration and functions

Board
Number of
Functions
boards
MPBPB
LRP block rear board
MPDMA
2(redundancy
LRP processor board
Page 2-33
The Processor Structure

The SDX-MSC II Processor is classified as follows depending upon the functions :
Main Processor (MP) : Performs upper level control and during the call
processing performs the upper level functions, general operation and
maintenance of the system, and controls the lower level PP.
Peripheral Processor (PP) : Controls the lower level and various devices to
perform real-time works, and maintains the lower level functions and devices
under the control of the MP during call processing.
5.1
MP
P-BUS
PC
PRT
OMP
MPDMA
MSBIA
redundancy
redundancy
SCSI BUS
MSBIA
SDU
DKU
MPDMA
U-LINK
CIN
MP
MPDMA
redundancy
U-LINK
MPDMA
P-BUS
Figure 2.23 Structure of the MP and OMP
Page 2-34
Consists of : OMP, INP, ASP, ENIP and LRP

Board : Is the MPDMA(the OMP consists of the MPDMA board and MSBIA
interfacing with the auxiliary memory unit and input/output device.)
Functions : Monitors states of Main Processing, P-bus & U-link interface, PP
and other hardware, etc.
Interfaces between blocks :
Interfaces between the MP and PP : P-bus

Interfaces between the MP and other subsystems : U-link
Page 2-35
5.2
PP
P-BUS
MP
P
PP
TDCMA
MPDMA
Redundancy
TD-BUS
H/W
Device
TDCMA
Figure 2.24 PP Structure
Page 2-36
Consists of : CCPP, INPP and ASPP

Board : Is the TDCMA
Functions : Controls various devices(telephony and maintenance systems) under
the control of the MP.
Interface between blocks
Interfaces between the PP and device block : TD-bus
Interfaces between the PP and the MP : P-bus
5.3
Processor Configuration of Each Subsystem

CCS
LRS
LRP 0
LRP 9
ENIP
CCPP
OMP
CIP
INS
CIN
INPP 0
INPP 1
INP
SSL
SSL
ASS 0
ASPP 0
ASPP 1
ASPP 2
ASP
TSL
ASS 19
: P-BUS
: U-LINK
Figure 2.25 SDX-MSC II Processor Configuration
Page 2-37
Operation & Maintenance Processor (OMP)
The OMP is to be mounted on the CCS and performs following functions :

Operation : Network control, billing, statistics and database controls
Maintenance : MSC state control, fault control and test control
Interface : Auxiliary memory unit and input/output device between the operator
and exchange station.
ASP
The ASP is to be mounted on the ASS and performs the following functions :
Call flow control : Processes local calls, outgoing calls and incoming calls.
Operations : Measures, collects and reports statistics for calls, and measures and
reports billing.
Maintenance : Monitors the status of the exchange station and detects, reports
and recovers faults.
ASPP
The ASPP is to be mounted on the ASS and controls the hardware blocks mounted on
the ASS, and manages the statuses of blocks.
LRP
The LRP is to be mounted on the LRS and performs the VLR to temporarily store
and manage information of the terminals within the area concerned. The LRP has a
variety of functions : Number controlling, call processing, authorizing and
encrypting, location registering and deleting, terminal activating/deactivating,
terminal searching and subscriber tracking, etc.
ENIP
The ENIP is to be mounted on the CCS and handles the X25 or TCP/IP to let the
system interface with the network control center or CAMA center.
CCPP
The CCPP is to be mounted on the CCS and collects information on all of the faults
and environments within the CCS and runs an alarm device.
Page 2-38
INP
The INP is to be mounted on the INS and performs call-processing functions such as
searching for telephony, and state managing functions such as detecting and
recovering of faults in the switch network.
Page 2-39
INPP
The INPP is to be mounted on the INS and performs SSL controlling and state
managing functions.
Page 2-40
6
6.1
Others
Remote Alarm Panel Unit (RAPU)
Alarm device of the SDX-MSC II is the RAPU.
The RAPU collects and reports alarms generated inside and outside the system under
the control of the CCPP, and displays the alarms generated at the system to let
operators recognize them easily.
The RAPU has two functions as follows :
Alarm collecting : Collects alarms via 128 EA of alarm cable connected with the
environment alarm detection system outside the system, and then informs the
CCPP of collected alarms via the TD-bus.
Alarm displaying : Displays three kinds of the alarms received from the CCPP
visually and audibly : critical alarms, major alarms and minor alarms.
The major parts are all redundant to improve the reliability of the RAPU, and up to 3
EA of the alarm display part are available. The RAPU can be installed on the OMC,
when necessary. In this case, the alarm status of the system can be checked also in the
OMC.
6.2
Auxiliary Memory Unit

Disk Unit (DKU)
The DKU, a random access storage device, stores the system level generic program,
database and input/output messages, etc.
The DKU interfaces with the OMP via a single-ended type of SCSI-II BUS. Each
redundant SCSI line is connected with two DKUs, and these two DKUs are
redundant. When writing data, the DKU simultaneously writes data at both the active
and standby sides, and when reading data, it reads data from the active side.
Storage Device Unit (SDU)
The SDU uses commercial Digital Audio Tape (DAT) as a storage medium. The DAT
stores information on billing, statistics, maintenance and operation control, etc.
Page 2-41
The SDU interfaces with the OMP via a single-ended type of the SCSI-II Bus.
6.3
Input/Output Device
The SDX-MSC II interfaces with commercial CRTs, PCs and printers, etc in the same
way as the RS-232 or the RS-422.
Page 2-42
CHAPTER 3
Software Architecture
Features of the Software

The SDX-MSC II is a Stored Program Control (SPC) electronic switching system
and the software is modularized. The SDX-MSC II software was designed in
consideration of reusability.
The SDX-MSC II software has the following features :
Distributed Software
The SDX-MSC II has a distributed Software Architecture to perform complex and

comprehensive functions by several processors performing simple functions.
If some of the functions have faults, a distribution software system can minimize the
effects on the system by localizing the fault wave.
Software Modularization
To enable software modularization, the SDX-MSC II consists of elements designed

to minimize overlapped parts between the software. Therefore, it is very easy to
perform debugging, modifying, adding and deleting work.
Fault-tolerant
The SDX-MSC II has a redundant processor, disk and other important parts to
improve stability, and uses a reliable protocol with high speed and low overheads for
communication between the processors.
Virtual Switching Machine (VSM) Mode
Page 3-1
The SDX-MSC II has been designed in the VSM mode. The VSM mode constitutes
an independent unit including hardware and hardware controlling software, and
combines those units to produce a new unit.
The VSM mode system can easily expand, improve and add hardware and software
without modifying application software.
Page 3-2
Applications of the Database Control System
The software of the SDX-MSC II uses a DataBase Management System(DBMS) to

easily maintain and operate the SDX-MSC II. The DBMS has the following
advantages :
Uses standardized expressions of information to remove problems during data
operation and control.
Reduces the amount of redundantly stored data to improve data efficiency.
Ensures data safety and maintains integrity.
Provides an operator-friendly query language.
Applications of Real Time Programming Languages
The Peripheral Processor (PP) of the SDX-MSC II requires real time processing and
has been designed with MC68060/MC68360 assembly and C languages. The Main
Processor (MP) performs functional processes and uses the CHILL language to ensure
programming readability, software maintainability and portability of the software.
International Standardization
The SDX-MSC II is based on the CCITT recommendations and has adopted the most
advanced software designing concepts.
The SDX-MSC II has used the SDL, which is a function statement language, to
produce design documents, and the Man-Machine Language (MML), an input/output
language, which is based on the CCITT recommendations. All of the system
application functions use CHILL, which is the CCITT standard and advanced
language.
Page 3-3
Software Architecture
The SDX-MSC II software consists of one or more execution modules and each of
these modules consists of one or more blocks.
The execution modules are as follows :
Application software
Call processing and mobility management software

Administration and operation software
Maintenance software
DataBase Management System(DBMS)
Operation System(OS)
Administration
&
Operation SW
DBMS
Call Handling
&
Mobility
Management
SW
Telephony
Interface SW
Maintenance
SW
File System
CROS
RMOS
SDX-MSC II Hardware
Figure 3.1 Software Functions Structure
Call Processing and Mobility Management Software
The call processing and mobility management software monitors and controls all of
the statuses, from generation to completion of calls to process calls successfully.
The call processing and mobility management software performs a variety of
Page 3-4
functions such as real time processing, multiprocessing, multiprogramming,

distributed controlling and resource sharing between calls, and is classified into two
levels, which are the upper level and lower level.
Page 3-5
Upper level call processing software : Signal analysis, number translation,

telephony setup, routing/hunting, call monitoring, operation control and data
generation, etc.
Lower level call processing software : Status monitoring, signal processing,
telephony control and interfacing with upper level functions.
Administration and Operation Software
The Administration and Operation Software provides system administration, test,

measurement and statistics, large capacity data control and an operator interface, etc.
The administration and operation software are distributed in the ASS and CCS. The ASS
receives various information from the call processing and mobility management
software, and stores this information. The CCS collects data from the administration and
operation software, and stores the data to a system disk and Digital Audio Tape(DAT).
The administration and operation software includes the following functions :
Man-machine interface management
Billing management
Traffic measurement
Network management
Data management.
Maintenance Software
The maintenance software provides various functions to enable operators to manage

the system conveniently and effectively, maintaining high reliability of the system
and providing high quality services.
Database Management System (DBMS)
The Database Management System (DBMS) stores and manages various data
coherently(at one place) to enable all of the application programs of the SDX-MSC II
to share the data. The DBMS manages data residing in main memory, and retrieves
and modifies the data depending upon the requests of the application programs.
Operating System (OS)
The Operating System (OS) enables various programs(processor manager, IPC

manager, time manager, memory manager, exception manager, input/output manager,
Page 3-6
and file manager, etc.) to exchange programs effectively. The OS consists of the
upper level CROS and lower level RMOS.
Page 3-7
CHAPTER 4
Call Processing and Mobility Management
1
1.1
Number Translation and Sending

Mobile Communication Subscribers Numbering System
The numbering system of the mobile communication subscribers is as follows :
15
14
13
MCC
12
11
10
MNC
MIN
NMSI
IMSI
Figure 4.1 The numbering system of mobile communication subscribers
Mobile Country Code (MCC)
The MCC is the last 3-digits of the IMSI and is a national code regulated by the ITUT(International Telecommunications Union - Telecommunication Standardization
Sector). The ITU-T E.163 has regulated each national code.
Mobile Network Code (MNC)
The MNC, is the last 2-digits of the NMSI and is a network identification number
given to the mobile communication providers.
Mobile Identity Number (MIN)
Page 4-1
CHAPTER 4. Call processing and mobility management
The MIN, is the first 10-digits of the NMSI and includes the identification number of
the mobile communication terminals within the network. The MIN consists of the
MIN1(first 7-digits of MIN) and the MIN2(last 3-digits of MIN). MIN1 is used for
authorization processes and MIN2 is used for unique challenge process.
Page 4-2
National Mobile Station Identification (NMSI)
The NMSI, is the first 12-digits of the IMSI and includes the MNC (network
identification number) and MIN (mobile communication identification number).
International Mobile Subscriber Identity (IMSI)
The IMSI is a mobile communication subscriber identification number used for

international roaming, and is defined by ITU-T E.212. It consists of a maximum 15digits.
Mobile subscriber numbering system per country

The numbering system per country is based on the requirements for each
country and the domestic system of mobile communication subscriber
numbering may vary depending upon the requirements and numbering plans
of each provider.
1.2
Call Processing Related Information

In addition to the mobile communication subscriber numbers, the following
information is used to process the mobile communication calls :
Electronic Serial Number (ESN)
The ESN consists of a 32 digit number(producer symbol, hold number, equipment

serial number and others) that is assigned to each terminal by the terminal
manufacturers. The ESN checks if the mobile communication terminals are being
used legally. The ESN is stored in the HLR and mobile communication terminals.
When the mobile communication terminal registers the location or sends and receives
calls, the MSC receives the ESN from the HLR to store it temporarily.
Temporary Mobile Subscriber Identity (TMSI)
The TMSI is temporary data assigned and stored by the MSC and identifies the
mobile communication subscribers within the area controlled by the MSC. The
purpose of the TMSI is to prevent the IMSI from being exposed on a radio path and
to enable the MSC to search the subscribers data quickly.
Page 4-3
Temporary Local Directory Number (TLDN)
The TLDN is assigned by the terminating side of the MSC and is used to route
incoming calls. However, the originating side of the MSC receives the TLDN from
the terminating MSC via the HLR, and uses the TLDN to route the calls to the system
where the mobile communication terminals are located.
Page 4-4
Location Area Identifier (LAI)
The LAI identifies the location areas.

CELL Identification (CELL ID)
The CELL ID identifies the cells and consists of a BSC ID and BTS ID. Each MSC is
able to connect up to 12 BSCs and each one of the BSCs is able to connect up to 64
BTSs. 12 X 64 = 768 BTS / MSC
AUTHR, AUTHU, AUTHBS, SSD, RAND, RANDU, RANDBS, COUNT
These are the authorization and encryption parameters.

Authorization and Encryption
For more information on authorization and encryption, refer to section 3.
Security Procedures(Authorization and Encryption) of Chapter 4. Call
Processing and Mobility Management.
A-KEY
Secret key only stored in terminals and authorization center, and is used for
encryption. This is neither exposed to radio interface nor used by the PCS.
Voice Privacy (VP) and Signaling Message Encription (SME)
The VP is identical to the Private Long Code Mask and is used for encryption of
voice. However, the SME is used for encryption of signaling messages.
IMSI Detach Flag
Indicates the IMSI detach and attach status of the terminals.

Teleservice
Identifies if the teleservice is provided.

Bearer Services
Page 4-5
Identifies if the bearer service is provided.

Supplementary Services
Identifies what Supplementary services are provided to the subscribers.
Page 4-6
1.3
MSC Number Translating and Sending

The SDX-MSC II shall satisfy the following requirements of the numbering system :
Uses the open numbering and close numbering system together.
Handles a maximum of 20 digits to deal with local calls, international calls,
intelligent network calls and interworking calls of other providers, etc. Also,
when necessary, it can increase the process capability without adding hardware.
The SDX-MSC II performs the following functions of numbering translations :
Translations of service identification numbers, subscriber numbers and special
numbers, etc.
Translation of special service numbers.
Identification and translation of mobile communication subscriber numbers
The TLDN identification and translation to send and receive signals of the
mobile communication subscribers.
Translation of numbers enabling the supply of intelligent network services.
Location registration and call control by estimating the mobile telephone number
of a 3-digit mobile prefix and 4-digit mobile prefix, based on a total digit length.
Prefix Extension
Translates mobile telephone number having a different prefix, based on the
total length. Therefore, 01X-123-4567 and 01X-1234-5678 can be used
together.
The SDX-MSC II can analyze the following information by the trunk EN and route
numbers :
State of the trunk line registration (including the function of handoff only trunk
line).
(Alternative) route number and trunk line EN.
Type of trunk line (one way, both ways, incoming, outgoing and E1).
Available signal types (PS, IMP, DEC, CCS NO.7).
Other required information.
The SDX-MSC II can analyze the following information with the IMSI or the TMSI
Page 4-7
of the mobile communication subscribers :

Status of the subscribers permission for use.
The TMSI, IMSI and DIALDGT of the subscribers, current MSC ID, ESN,
Page 4-8
location areas and BUSY/IDLE.

Status of the subscribers service registration.
The SDX-MSC II has the following sending functions when interfacing with other
exchanges :
Transit the numbers : LINK-BY-LINK mode and END-TO-END mode.
Sending of the numbers : ENBLOC mode and OVERLAP mode.
Screen : Limits incoming calls from specific subscribers and sends a recording
announcement regarding limited calls to the relevant subscribers.
Call screen per incoming route : Limits incoming calls from specific routes and
sends a recorded announcement regarding incoming calls from limited routes.
Page 4-9
Routing and Other Carrier Roaming

The SDX-MSC II can analyze roaming information to perform transmitting and
receiving of calls to and from other mobile communication networks, or analyze
information received from other service networks(the PSTN and ISDN) and network
elements, etc to route calls. Routing of calls includes the interfacing between SDXMSC II and other MSCs, and interfacing between SDX-MSC II and internal network
elements.
2.1
Routing System
The SDX-MSC II shall satisfy the following requirements regarding routing :
Maximum of eight times of alternative routing is permitted.
Priority subscribers can perform routing earlier than other subscribers.
Handoff calls can perform routing earlier than other service routing.
Handoff calls can perform routing using a leased trunk line.
Fixed Routing System
Routes between the originating station and destination station are fixed. Operators
can change the routes manually.
Dynamic Routing System
2.2
Time-dependent routing : Changes routs at the fixed time of one day or one
week. The dynamic routing system considers traffic variations depending upon
the time and can use idle circuits effectively if the busy time is different between
the MSCs.
State-dependent(Adaptive) routing : Decides routes automatically, based on
network status information(outgoing trunks occupancy and call processing
status, etc) that has been sent to the MSC from the MSC or central management
center.
Routing Applications
Page 4-10
Automatic Alternative Routing
The Automatic Alternative Routing applies forward directed sequential call control
and is used for two or more of the other MSCs and routing paths.
Page 4-11
Automatic Rerouting
If the information impossible for routing is received from the MSC that has
generated blocking on the routing path (faulty or occupied outgoing circuits), this
method reroutes the information to another MSC. In automatic rerouting, circular
routing that resets the route to the location were the blocking is generated, is
prevented.
Load sharing
The Load Sharing distributes calls depending upon the specified ratio to share the
load of the MSC or the trunk line related to the routes.
Page 4-12
Security Procedures (Authentication and Encryption)

The SDX-MSC II provides the following functions to prevent illegal use of services
or wiretapping.
Identity and Authentication
Traffic data encryption (Voice Privacy)
Signaling Message Encryption
The identity and authentication verifies the terminal and subscriber information to
prevent an illegal terminal or unauthorized use of services. To do so, the mobile
communication terminal and network share a secret key. When the authentication
procedure is required, the mobile terminal and network perform the same
authentication algorithm, and compare the outcomes to verify the legality of the
terminal and services.
The subscribers will be able to use services after passing this identity and
authentication procedure.
After passing the identity and authentication procedure, subscribers can select the
following functions : encryption for traffic data(prevents wiretapping of subscribers
information received from and transmitted to the radio channels) and encryption of
signal messages of selected calling channels(prevents wiretapping of signal messages
transmitted between mobile terminals and base station via the radio network.)
3.1
General Matters
Shared Secret Data (SSD)
The SSD is stored in the terminals semi-permanent memory and the AC

(Authentication Center), and a 128-bit value for the purpose of authentication and
encryption).
The SSD-A is used for the identity/authentication procedure and the SSD-B is used
for encryption of traffic data and signal messages. Contents of the SSD cannot be
verified at the radio interface section.
Page 4-13
In addition, the MSC shares the SSD that generates the authentication results or
encryption key, with the VLR upon request of the operators and performs
authentication at the AC as well as at the VLR. When the SSD is shared with the
VLR, the VLR performs the following functions :
Performs and compares a Common Encryption Algorithm to generate
authentication result values, such as the AUTHR, AUTHBS and AUTHU.
Updates the call history count.
Selects RANDU, a random value, at the time of a sole attempt and response
procedure.
Generates a voice security key(private long code mask) and signal message
encryption key (SMEKey).
Random Attempt Values (RAND)
The RAND is a 32-bit value stored at the terminal. The RAND, if it is received from
call channel, is the same as the value received from recent access parameter
messages.
Call History Count
The call history count is a modular-64 counter value stored at the terminal and
network. It can be updated at the terminal : 1) whenever the traffic channel with
forward direction receives commands for parameter update, 2) by the parameter
update command after channels are assigned during incoming and outgoing call. This
value is used for identity and authentication by being compared with the count value
that is maintained at the network.
Generation of Identity/Authentication and Encryption Data
Figure 4.2 shows correlation of the data that is used for authentication and
encryption. A Key in the figure indicates a secret key stored only at the terminal and
authentication center, and generates the SSD used for authentication and encryption
using a random variable selected at the Authentication Center.
The authentication procedure generates authentication result values using the SSDA(specific part of the SSD), random variable and other parameters, etc.
On the other hand, the encryption procedure generates the SMEKey (encryption key
of each terminal) or Private Long Code Mask using the SSD-B(specific part of
Page 4-14
shared secret data) and other inputs.
Page 4-15
A-key RANDSSD ESN
SSD_Generation
procedure
Auth_Signature
SSD-A
Procedure
SMEKEY_Generation
SSD-B
Procedure
Authentication Input
SMEKey Generation
Parameter
Parameter
Authentication Result
SMEKEY
Figure 4.2 Generation of Identity & Authentication and Encryption Data
3.2
Authentication
The SDX-MSC II verifies the terminal validity and rejects the services for illegal
terminals, and verifies the validity of the following :
Validity of subscribers (using the IMSI) :
Validity of terminals (using the ESN)
3.2.1 Authentication Procedure and Input Parameters

The authentication procedure processes the related data between the BTS and
terminal to verify the validity of the terminal. The authentication procedure is
performed when the terminal demands location registration and incoming/outgoing
call processing, and is completed when secret data shared by the terminals and the
BTS is identical with each other.
The following are descriptions on authentication input parameters depending upon
the authentication and corresponding procedures.
Page 4-16
Broadcasting Type Authentication Procedure
The Broadcasting Type Authentication broadcasts the RAND values for performing
authentication using forward direction channel/paging channel (access parameter
message). Then, all of the terminals accessed from the cell concerned perform this
procedure at the time of system access (location registration, calling and paging
response). The terminals calculate the AUTHR value using the RAND values received
from the terminals and send it to the MSC. Then, the MSC compares the RAND values
received from the terminals with the pre-calculated AUTHR values to perform the
authentication procedure.
Individual Authentication (Unique Attempt/Response Procedure)
This performs authentication using messages other than the messages used at call setup and location registrations of the MSC. The MSC tries to get authentication by
transmitting authentication parameters including the RANDU values to the terminals.
The terminals use the received RANDU values and calculate the AUTHU and then
transmit the values to the MSC.
The MSC performs authentication by comparing the AUTHU values received from
the terminals with the AUTHU values calculated in advance.
The network including the exchanges always opens or controls the Individual
Authentication Procedure. The Individual Authentication can be performed on the
paging/access channel or traffic channel of forward and backward direction.
3.2.2 Authentication Parameters Update
The MSC updates the following authentication parameters when the Authentication
Center requests to modify the SSD related to terminal authentication and call history
count data.
SSD Update
Updates the Share Secret Data (SSD).

Call History Count Update
Updates the Call History Count, which is authentication data.
Page 4-17
3.3
Encryption
The MSC encrypts radio data and signaling messages between the terminals and BTS
to provide the subscribers with the same security as the cable link.
3.3.1 Voice Privacy

The Voice Privacy makes an encryption of the data, which the mobile communication
terminals and BTS transmit and receive through traffic channels, and prevents the
subscribers voice and data from being wiretapped.
Originating Call :
1) Call originating terminal asks the MSC to set up calls.

2) The MSC asks the Authentication Center to authenticate terminals.
3) The Authentication Center transmits the Private Long Code Mask (PLCM) to the
MSC to respond to authentication requests received from the MSC.
4) The MSC assigns channels and transmits the PLCM to the BSC.
5) The BSC transmits the PLCM to the BTS. The BTS asks for masking of the data
using the PLCM when the outgoing terminal transmits traffic data.
6) Makes use of the PLCM between the BTS and terminals to transmit the masking
data (traffic channels cannot be wiretapped without knowing the PLCM.).
Terminating Call :
1) The BTS sends paging signals to call terminating terminals.

2) Call terminating terminal responds to the paging signals.
3) The MSC asks the Authentication Center to authenticate terminals responding to
paging signals.
4) The Authentication Center transmits the Private Long Code Mask (PLCM) to the
MSC to respond to authentication requests received from the MSC.
5) The MSC assigns channels and then transmits the PLCM to the BSC.
6) The BSC transmits the PLCM to the BTS. The BTS asks for data masking using
the PLCM when transmitting traffic data using terminating terminals.
7) Makes use of the PLCM between the BTS and terminals to transmit the masking
data (traffic channels cannot be wiretapped without knowing the PLCM).
Page 4-18
3.3.2 Signaling Message Encryption

The Signaling Message Encryption makes encryption of signaling messages between
the mobile communication terminal and the BTS to prevent wiretapping.
When the mobile communication transmits and receives signals, the MSC receives
the SMEkey from the Authentication Center and transmits it to the BSC. Either the
mobile communication terminal or the BTS makes use of the SMEkey to make
encryption of the signaling messages.
Page 4-19
4
4.1
Location Registration
Introduction
The Location Registration is used to register information on location, status, party
identification and slot frequency, etc for each terminal on the CDMA network to let
the mobile communication terminal handle incoming calls effectively. The MSC
registers locations by itself and the BSS interworks with both the MSC and mobile
communication terminals to support the registration of terminal locations on the
CDMA network.
Registers location for the following cases :
When the mobile communication terminal is activated or deactivated.
Depending upon the periodic time terminal.
When the mobile communication terminal changes the location area.
When the operator demands it.
4.2
Types of Location Registrations

The SDX-MSC II monitors the BTS periodical broadcasting messages, such as the
system parameters, CDMA channel list, expansion system parameters and access
parameters, etc. When the terminal memory has different values, the SDX-MSC II
registers nine types of locations :
Power Up Registration
When the mobile communication terminal turns ON, the Power Up Registration
informs the MSC of the terminals current activated status. When the mobile
communication terminal repeatedly turns ON and OFF for a short time, the Power
Up Registration turns ON and then registers the locations after an elapse of specific
time to avoid consecutive registration.
Power Down Registration
When the terminal turns OFF after registration, the Power Down Registration turns
ON. At power service interruption, the location information is to be deleted.
Page 4-20
Timer Based Registration
The Timer Based Registration turns ON when the built-in call channel slot counter
value (80 ms) reaches the BTS maximum value. The registration is to be used to let
the BSC automatically release the location of the terminal, which has failed at the
power service interruption registration.
Page 4-21
Zone Based Registration
Zone means the mobile communication service supply area and consists of several
cells. The terminal stores lists of the zone movement. Zone Based Registration is to
be made when the terminal moves to a new area (the area which has no zone list
stored inside the terminal).
Parameter Change Registration
The Parameter Change Registration turns ON regardless of the roaming state, when
parameters of the mobile communication terminal change, for instance, slot
frequency index, slot mode indicator, incoming call set-up indicator, band class,
power grade, transmission speed and operation mode, etc.
Distance Based Registration
The Distance Based Registration turns ON when the distance between the latest
registration system and current system exceeds the threshold. The mobile
communication terminal estimates the distance between the latest location
registration and current system (estimation of the distance between the latitude and
longitude).
Ordered Registration
The Ordered Registration turns ON when the terminal is given a location registration
command from the BSC.
Implicit Registration
The Implicit Registration turns ON when the BSC detects the terminal location at a
successful sending of the call out and calling response messages of the mobile
communication terminals.
User Zone Registration
The User Zone Registration turns ON when the mobile communication terminal
moves to the designated area (users service area).
Page 4-22
4.3
Location Registrations
Initial Location Registrations
When subscribers register terminal location for the first time after subscribing to
mobile communication services (the TMSI has not been assigned to the terminal
during the initial registration), the IMSI is to be used to register the locations. When
the VLR fails to perceive terminals during normal location registrations, the IMSI is
to be used to register the locations.
Normal Location Registrations
Normal Location Registrations shall be made when subscribers move to either the
same MSC area or a different MSC area after completing the location registration at a
specific area. In the case that the serving MSC (supplying services by terminal) reports
the newly registered terminal location to the VLR, and the VLR notifies the HLR of
associated information (ESN, MIN, MSCID and qualification information code, etc)
and takes action against their responses.
Registers locations at the VLR only, not transmitting information to the HLR.
Location has been registered at the VLR in advance.
Terminal is under an active state.
Location can be registered after exchanging information with the HLR.
The terminal of the VLR is under an active status :
The VTR has no information on the terminal.
The information from the terminal cannot be interpreted.
Inactive and Deregistered of the Terminal
When the MSC decides that a terminal registered at the area has become inactive for
more than a specific time, the terminal sets inactivation at the internal data structure
or deletes all of its records and transmits the MSINACT message to the VLR.
The VLR can display an inactive state of the terminal or deregister all of the records
regarding the terminal. When the MSC decides an active state of the terminal after
the VLR deregisters the terminal related information, the VLR launches to notify the
HLR of the registrations and updates the internal data structure.
Page 4-23
Deregistration is to be made when terminal registration is needed to be deleted

because of the terminals power service interruption order, terminals inactive state
report and radio connection loss reports, etc. The deregistration can be done by
serving the MSC, and internal algorithm of the operators and serving VLR. At the
deregistration, the MSC erases the terminal related contents stored in memory and
transmits the associated messages to both the VLR and HLR. The VLR erases the
terminal related contents from the memory after receiving messages, while the HLR
deregisters the pointer of terminal related VLR. When the VLR shares the Shared
Secret Data (SSD) during deregistration, the VLR transmits the Call History Count to
the Authentication Center (AC) via the HLR.
Bulk Deregistration
The Bulk Deregistration is used to notify the HLR of all of the roaming terminal data
by the VLR.
Location Registration Controls
Location registration controls do not ask for the location registration by the HLR
regarding all of the location registrations(which have occurred at terminals and the
Base Station (BS)) but for only specific location registrations registered by the
operators, while the MSC demands location registrations by the HLR.
Operators can register the locations using location registration controls : timer-based
location registrations and zone-based location registrations. In addition, the zonebased location registration can control the location registration requests of the HLR
depending upon the specific base station.
Page 4-24
Mobile Communication Subscriber Call Processing

Mobile communication call processing demands not only basic call processing of the
cable telephone network but also mobile communication subscriber call processing of
the mobile communication.
The SDX-MSC II performs the following to set up the subscriber communication
subscriber calls : authentication of the subscribers, encryption, location registration
and paging, etc. After setting up the call, the subscribers perform handoff to maintain
calls continuously even for cell movement.
5.1
Call Processing Functions

The SDX-MSC II has the following functions to achieve subscriber call processing :
Anchor MSC
The Anchor MSC assigns traffic channels for the first time at call incoming and
outgoing. It becomes a fixed point when the terminal makes handoff by another
MSC.
Candidate MSC
When the MSC demands the best cell identifier and signal quality value to let the
terminal make handoff, the Candidate MSC gives the necessary information.
Visitor MSC
The Visitor MSC registers the moving terminal as a visitor subscriber.
Originating MSC
The Originating MSC performs the MSC-H and the MSC-G to launch the call
transfer.
Serving MSC
The Servicing MSC supplies services to the terminals within current service
area.
Page 4-25
5.2
Controls of the Originating and Terminating Calls

Mobile communication subscribers originating call processing may vary depending
upon the terminating subscribers types. The originating call for terminating to fixed
subscriber sets up a path by the exchange depending upon the terminating DN dialed
after performing the security procedures of the call originating subscriber. The
originating call for terminating to other mobile subscriber inquires on the terminating
subscriber by interworking with the HLR to get the routing information of the
terminating subscriber after performing security procedures.
The subscribers terminating call processing includes : the TLDN assignment for the
supply of routing information, location registrations, route set-up, paging and
terminating subscriber authentication, etc.
The procedures of originating and terminating calls are :
Outgoing call
terminal
BSS
MSC
HLR
MSC
BSS
Incoming call
terminal
Call set-up
Figure 4.3 Originating & Terminating Procedures
Page 4-26
1) Calling party MSC receives the call set-up demand from call originating terminal.
2) Calling party MSC demands authentication of the call originating terminal by the
VLR inside the calling party MSC.
3) Calling party MSC demands location information on the terminating terminal by
the HLR.
4) The HLR demands the TLDN by the destination party MSC.
5) Destination party MSC demands the TDLN by the VLR(the one that the
terminating terminal has registered location) inside the destination party MSC.
6) The HLR transmits the TLDN, which has been given by the destination party
MSC, to the calling party MSC.
7) Calling party MSC analyzes the TLDN and then makes a routing by call
terminating MSC.
8) Destination party MSC analyzes the TLDN, which has been given by the calling
party MSC and demands the location information of the call terminating
terminal by the VLR inside the destination party.
9) When the destination party MSC tries to do paging using the location information
(call terminating terminal location information received from the VLR), the call
terminating terminal responds to the paging received.
10) Destination party MSC sends ring signals to the call terminating terminal. When
the terminating terminal responds, a call path set-up between the terminal and
originating terminal is to be completed.
Page 4-27
5.3
Call Release
The call release starts when demand from the mobile communication terminal is
received or the MSC transmits disconnection messages.
The Call Release procedures are :
Terminal
BSS
MSC
MSC
Terminal
BSS
Call Release
Figure 4.4 Call Release Procedures
1) The MSC receives the call release demand from the terminal.
2) The MSC releases various types of resources in use(for instance, ASP, ASPP, DTI,
Time Switch, Space Switch, etc) at the set-up of calls of each terminal.
3) Transmits the call disconnection notice to the counterpart MSC.
4) Releases various types of resources in use, when the MSC sets up calls after being
informed of the call disconnection.
5) Transmits the Clear Command to the BSS.
6) When the BSS transmits a release order to the terminal, the terminal transmits the
Release Complete to the BSS.
7) As soon as the BSS transmits the Clear Complete to the MSC, the Call Release is
to be completed.
Page 4-28
Handoff
The handoff means changes of the speech path to newly entered cell to maintain a
continuous call, when the mobile communication terminal moves to another cell free
from the cell areas(or sector) in service.
The mobile communication terminal compares the pilot channel intensity, which is
given by the BTS in service, with another pilot channel intensity received from an
adjacent BTS. When a pilot channel measurement at an optional place reaches a
value for handoff, the terminal notifies the BSC of the pilot channel information of
the cell to do handoff, and the BSC makes lists of the cells based on the information
and asks the MSC to do the handoff processing.
The MSC gets a radio channel, which can maintain busy calls against the terminal
requiring handoff, and assigns it to the new call. The MSC does not disconnect busy
calls using a new speech path and instead switches the call to the BTS of the new
area(the area where the terminal moves to).
When handoff is performed within the area of the MSC, the MSC verifies the
possibility of the handoff by interworking with the BSC controlling the target cell
and then makes a switching of the existing speech path to the new path to perform
handoff. If a different MSC performs handoff, the MAP protocol performs the
handoff procedures.
6.1
Handoff Functions of the MSC

The MSC functions to handle the handoff :
Serving MSC : The MSC which has accommodated the mobile communication
subscribers asking for handoff.

Target MSC : The MSC which is to accommodate mobile communication
subscribers asking for handoff.
Anchor MSC : The MSC to which mobile communication subscribers asking for
handoff have set up calls for the first time.
Tandem MSC : The MSC supplying a handoff speech path between the anchor
MSC and the serving MSC, when handoff is made several times.
Page 4-29
When the serving MSC changes at handoff, the anchor MSC controls and maintains
the billing, supplementary services and call processing, etc.
The MSC performs handoff functions as follows :
Page 4-30
Signaling and Voice Information Encryption
Encryption related data processing

Common encryption algorithm, the RAND, the MIN, the ESN and the SSD-B
data processing.
Verifies signal messages encryption key processing.
Verifies voice security processing.
Verifies encryption processing functions of the MSC accepting handoff.
Serving MSC
Demands handoff processing by either the tandem MSC or the anchor

MSC(HandoffBack2)
Asks either the anchor MSC or the tandem MSC to do handoff to the target
MSC(HandoffToThird2).
Asks for handoff processing to the target MSC and to other target MSCs.
Target MSC
Accommodates handoff and increases the segment counter and handles the new
billing ID.
Accommodates new handoff.
Anchor MSC
Handles handoff from the tandem MSC and the serving MSC.
Handles Path Minimization Handoff.
Tandem MSC
Handles handoff between the tandem MSC and the target MSC.
Relays handoff to either the anchor MSC or the tandem MSC.
Page 4-31
6.2
Handoff Classification
From the point of view of the MSC, the handoff can be classified into : 1) handoff
requiring MSC involvement, 2) handoff that the BSC handles by itself.
Handoff requiring MSC involvement : Handoff between the BSC under the
same MSC and handoff between other MSCs.
Handoff that the BSC handles by itself : In the case where the speech path
assigned by the BTS has bad features, the handoff between handled channels and
handoff between the BTS under control of the BSC.
When the BSC handles handoff by itself, it transmits the handoff information to the
MSC and collects the handoff related data.
Handoff Between BSCs Within the Same MSC
The soft handoff is to be performed when the frame offset, which is in use at the
target cell, has the same channel. If not, the hard handoff is to be performed.
Hard Handoff : After performing handoff, makes use of other frequency than the
one which has been used before the handoff, or same frequency. However, with
the channel with a changed frame offset, disconnects calls and switches to the
speech path.
Soft Handoff : When the frequency and frame offset make use of same channel
even after performing handoff, switch the speech path without disconnection of
the calls.
Handoff Between MSCs
When both the Target MSC and Serving MSC exist on the call path and the Serving
MSC does not coincide with the Anchor MSC, apply the backward handoff
procedures. When the Serving MSC does not coincide with the Anchor MSC and the
path minimization function can be applied, apply the path minimization function to
apply continuous handoff procedures. If both cases are not applied, apply forward
handoff procedures.
The MSC functions are included depending upon the handoff type :
Forward handoff : The Target MSC does not include the speech path, and does
not make use of the path minimization.
Page 4-32
Backward handoff : The Target MSC already exists on the path.

Continuous handoff using path minimization : The Target MSC does not include
a speech path and instead makes use of the path minimization.
Page 4-33
Page 4-34
CHAPTER 5
Operations and Maintenance
Billing/Charging
The billing/charging generates information on the call services supplied to the
subscribers, and records it on a secondary recording media(the SD) or transmits it to
the CAMA Center to settle the account of charges.
Generates the billing related information in the following cases :
Mobile communication subscribers sends calls
Calls arrive to the mobile communication subscribers
Mobile communication subscribers send emergency calls
Mobile communication subscribers send diverted calls
Mobile communication subscribers are given supplementary services
Sends a query to the HLR.
1.1
Collection of Billing Data

Handles the charging data as follows :
1) The ASPs billing data generation block generates the billing data.
2) The OMPs billing collection block collects the ASPs billing data to generate the
billing block.
3) The billing gathering software, gathers the billing block(1K) on the disk.
4) The billing transmission/dump block transmits the billing data stored on the disk
to the CAMA Center, or stores it at the SD.
When a fault occurs at both the billing block and billing storing system of the OMP,
the operator can setup to store the billing data temporarily in the memory of billing
Page 5-1
CHAPTER 5. Operation and maintenance
generation block within the ASP to prevent the data from being lost.
In addition to the case of a fault occurrence at the OMP, the ASP can prevent the
transmitting of billing data to the OMP from the ASP, in order to prevent data from
being lost that can be generated when the load of the CPU or I/O within the OMP is
decreased, or when the processor or software is rebooted.
Page 5-2
When one hour has elapsed after the operator prohibits the transmission of the billing
data(the data transmitted from the ASP to the OMP), the command(prohibition of
billing data transmission) is cancelled automatically. Also, if the billing related
memory of the ASP is full, the command is cancelled even though one hour has not
elapsed and billing data is transmitted to the OMP.
1.2
Control of Billing Information

Output of Billing File Data
The billing data is recorded to the disk in the unit of a file in the OMP. The billing file
can be generated at a minimum of a 30-second interval. The maximum number of
files that can be generated a day is 2,880 files.
To control the mass of data effectively, the SDX-MSC II uses a virtual file system,
that generates the billing file which is based on the time (minimum 30 seconds) or
size(minimum. 1 Kbyte).
The operator can check the billing file information that is stored to the disk, using the
MMC. The billing file information is output in units of 10 files, and includes the
following :
File name
The total number of files, blocks and CDRs.
File open time and close time
Whether or not transmitted to the SD or the CAMA.
The billing file has its unique ID and is controlled in the directory structure of the
index mode. Therefore, the index can get access to it immediately without an
independent search, upon the operators requests for billing file information.
Confirmation of the Billing Storing State
The billing block of the OMP generates the billing files using billing data received
from the ASP and then stores it to the disk.
If the billing disk is abnormal, the billing block stores the billing data in its memory
queue of the OMP, and transmits the billing data to the billing center to prevent the
data from being lost. In addition, it reports abnormal status of the billing storage to
Page 5-3
the operator by outputting alarm messages or fault messages. The operator can check
not only the number of billing blocks stored at the billing storage media, but also
details of the billing data of the billing block.
Page 5-4
1.3
Operations of Billing Storage Media

The billing storage media includes the billing disk and various types of auxiliary
memory units.
Billing Disk
The billing disk controls the billing data based on virtual files, which cannot be
deleted optionally. However, when the virtual files are overwritten, the previous data
is deleted.
Basically, the hard disk(HD) having approximately 2 Gbytes is used for the billing
information disk. The billing data storage capacity is influenced not only by the billing
disk capacity, but also by size of the Charging Data Record(CDR).
Four hard disks mounted on the SDX-MSC II consist of two redundancy pairs for
concurrent writing systems(HD0 x 2, HD1 x 2). HD0 stores the software program,
Program Load Data(PLD) and statistics data, etc, while the HD1 stores the billing
data.
Each disk has the following capacities :
Table 5.1 Disk Capacities
Device
Storage capacity
Billing area a
Number of
[bytes]
[bytes]
stored calls b
Remarks
[call]
HD(2 Gbytes)
2.0 G
1.8 G
12,600,000
25 Hour
(standard shape)
HD(4 Gbytes)
4.0 G
3.6 G
25,200,000
50 Hour
a. The size of the billing block is 1 Kbytes, 7 calls per block(for instance, 12,600,000 calls = 7 calls/1K
1.8 G)
b. The number of stored calls is based on 144 bytes of the CDR size.
Auxiliary Memory Unit
The Digital Audio Tape(DAT) is used for the auxiliary memory unit for the billing
data storage. The Storage Device Unit(SDU) is the unit that mounts the auxiliary
Page 5-5
memory unit.
Page 5-6
1.4
Operations of Billing Operation Modes

Types of Billing Operation Modes
The billing operation mode includes the CAMA, LAMA and BOTH.
CAMA Mode : Permits only the transmission of billing data to the CAMA
Center.
LAMA Mode : Permits storage of the billing data to only the DAT.
BOTH Mode : Transmits billing data to the CAMA and stores it in the DAT at
the same time.
The files created at the LAMA mode can be collected in the CAMA mode, and vice
versa.
The billing operation mode can be changed to the MMC. The mode can control the
transmission of the billing data to the CAMA Center or storage of the data to the
DAT by file unit and it can be checked by the MMC. When the MMC is added with
search conditions it gives : lists of files not transmitted to the CAMA and not stored
at the DAT, the number of the files recently transmitted, the number of recently
dumped files, and a list of recently created files. In addition, a file search at the
specified time for file creating is also available.
Automatic Switching of Billing Operation Modes
The billing data that has not been processed by the LAMA or CAMA cannot be
deleted. However, if the billing disk is full, newly generated data has priority over not
processed data. Therefore, not processed data is stored in the memory of the ASP and
OMP.
If the billing disk capacity is full, the billing data can be lost. Therefore, an alarm is
generated when the disk capacity is used over a specific ratio. The alarm has three
levels : minor, major and critical. The alarm level rises or falls down depending upon
the disk occupancy.
When disk occupancy(the ratio of the files that cannot be deleted out of total disk
capacity) exceeds the threshold while operating the billing collection mode in the
LAMA mode or the CAMA mode, the mode is switched to the BOTH mode to
prevent billing data loss.
The threshold that automatically switches the billing operation mode can be inquired
Page 5-7
or changed by the MMC.
Page 5-8
1.5
Billing Backup
The billing data is stored at the disk primarily and then stored at the DAT or transmitted
to the CAMA Center. Therefore, billing data of the DAT can be regenerated using the
disk data. To generate the billing data of the DAT again, each billing data has to be
checked where it is stored. Therefore, storage of the data at the DAT is to be controlled
by the address of data storage disk.
Backup of the billing data from the DAT can be used when the IT Center fails to
analyze the billing data of the DAT.
The billing backup information can be stored up to the latest 100 of the DAT data.
Backup files can be selected in the way that the operator designates the backup start
files and the number of files for backup. In addition, the way, which the number
controlled by history is designated, may be used.
1.6
Billing for Each Type of Call

The SDX-MSC II can use a variety of billing systems depending upon not only
common methods but also the types of calls.
Route Billing
The route billing assigns the billing function for itself against the specific incoming
route or outgoing route, and generates details of the calls relating to calls occupying
each incoming or outgoing route. Only a detailed billing way is permitted to route
billing data. The route billing is used when providers make an account settlement of
the billing or calling party at other provider networks that calculates the bills.
Immediate Billing
Immediate billing generates calls for the purpose of tests inside the telephone
exchange or others, and reports the details of the billing immediately.
Supplementary Service Billing
When mobile communication subscribers register, remove and check the

supplementary services, the Supplementary Service Billing charges for the services.
If billing conditions for the registration, removal and verification prefix of the
supplementary service change, the supplementary service billing data cannot be
Page 5-9
generated.
Page 5-10
Statistics
The statistics control the system functions to collect, store, analyze and handle data
and sends the statistics outcome. The statistics outcome is to be used for the
operation, maintenance and network management, etc.
The statistics data is transmitted regularly : hourly, daily and monthly. It also can be
transmitted irregularly, depending upon the operators requests.
Statistics measurement target is :
Route and trunk
Signal system
Service circuits
Control system
Special services
Overall exchange
Common channel signals
Network controls
System functions
2.1
Statistics Collection Types

Statistics of Routes and Trunk
Measures the trunk and routes :

Incoming traffic
Incoming-terminating traffic
Incoming-outgoing traffic
Event counter by outgoing traffic
Traffic intensity
Holding or seizure time
Statistics of Signaling System
Measurement and statistics of the signaling system can measure the use ratio of the
signaling system mounted on the SDX-MSC II.
MFR circuit
Page 5-11
Page 5-12
R2 circuit
Ring circuit
Continuous check tone circuit
Tone circuit.
Statistics of the Service Circuit
The statistics of the service circuit can measure the use ratio of the service circuit
mounted on the SDX-MSC II. The service circuits to be measured are :
Recording announcement system
Call mixer
Statistics of the Control System
Measurement and statistics of the control system can measure the load of the MP,
such as IPC related information, and transmit it to the operator. It processes data
concerning statistics measurement :
Output time of the daily measurement outcome
Output date and time of the daily measurement outcome.
This function can output or modify the information upon requests of the operators.
Statistics of Special Services
Measures the following special services :

Time of success and failure of the special services
Time of success and failure of the service registration confirmation
Time of success and failure of the service use
Statistics of Overall Exchange
Measures the overall exchange traffic :

Originating traffic
Internal traffic
Originating-outgoing traffic
Incoming Traffic
Incoming Terminating Traffic
Transit Traffic
Terminating Traffic
Disconnection calls during calling
Outgoing Traffic
Traffic intensity
Holding or seizure time
Page 5-13
Statistics of the Common Channel
Measures the utilization, availability and performance of the following, relating to

common channel signaling system No.7 :
Signaling link consisting of common channel signaling system No.7
Signaling route
Link set
Route set
Adjacent signaling point
SCCP : Signaling connection control part, etc
Statistics of the Network Management
Measures the network management statistics :

Terminating code automatic controls
Route automatic controls
Terminating code manual controls
Route manual controls.
Statistics of the System Functions
Measures the system functions :

Call loss ratio
Availability : Subscriber lines, trunk, signaling equipment, switches, intra junctor
channel, ring, tone, call mixer and paging broadcasting channel, etc.
Delay time : Incoming response delay, call request delay, call setup delay and
alerting sending delay, etc.
Incoming response delay : Delay time from recognition of the incoming
trunk occupancy to sending of the backward signals to the originating
party exchange.
Call request delay : Delay time from the exchange receiving the
originating call demand messages of the subscriber terminals to the
message sending in response to the messages.
Call setup delay : Delay time from the time when the information for
selection of transit call is available until the time when the trunk seizing
signal is sent to counter-party station.
Alerting sending delay : Delay time from the time when the signaling
Page 5-14
information for the exchange is available to the time when ringingbackbone or Alerting message is sent to outgoing subscriber circuit.
Page 5-15
2.2
Signaling time
Time from trunk occupation to completion of sending the information
between the exchanges
Time from occupation of the trunk to receiving of the response signals
Time from trunk occupation to completion of receiving the information
between the exchanges
Time from completion of the information between the exchanges to
sending of response signals
Statistics Storing and Sending

The Statistic Storing stores the statistics data on the disks. Measured statistics data is
stored on the disk regularly.
The Statistics Sending sends statistics data. All of statistics data measured is
transmitted regularly or to the operation terminal upon the request of the operator.
Page 5-16
Network Management
The Network Management maintains a proper traffic level and operates the
communication network. The management is performed by the SDX-MSC II itself as
well as the OMC (Operation & Maintenance Center) connected with the data link.
Network Management Information
The SDX-MSC II transmits the information to the OMC to manage the network :
State of current load
Functions and availability depending upon the traffic
Shape information.
Transmits the information in real time, periodically or upon request of the OMC.
Automatic Control
The automatic control takes actions automatically against various kinds of situations
detected during the system inspection. The automatic control includes : Hard-toReach(HTR) control and trunk reservation control.
HTR control : Traffic rush within the network can detect terminating code(HTR
code) having much less call completion, and register it on a list of the HTR to
control it.
The operator can inquire on a list of the HTR and register or remove the specific
terminating code to the list of the HTR artificially.
Trunk reservation control : Trunk group designates the number of backup trunk.
When the number of backup trunk is less than the threshold, the trunk
reservation control manages the traffic. The calls, to which the trunk group
rejects access, are to be skipped or cancelled.
Manual Control
The Manual Control can control the overload state by use of the MMC command by
the operators. Traffic is controlled based on either percentage (0~100%, 12.5%
interval, 9-stages) or gap interval(0, 0.1, 0.25, 0.5, 1, 2, 5, 10, 30, 60, 120, 300, 600
seconds).
Page 5-17
Page 5-18
Trunk group control :

CANT : Connects the limitation target traffic, which enters a specific
route, by recording the announcement.
SKIP : Connects the limitation target traffic, which enters a specific route,
by an alternative route.
CANF : Connects overflow traffic(calls trying to detour because of failures
of primary trunk occupancy) by network control recording announcement
RR : When the basic route is occupied at the Out-of-Chain traffic routing
of the overflow traffic(the call which has failed in the primary trunk
occupancy), Out-of-Chain route is used instead of the normally applied
secondary route.
Overload Control
Overload means that traffic has occurred due to an excess of the capacity of the
system. Improper control of the overload state has a high negative effect on functions
and stability of the call processing performance.
When the traffic inflow exceeds 150 percent of the system processing performance,
the ITU-T Q.543 recommends a capability of more than 90 percent call processing of
the inflow traffic. The SDX-MSC II can control overload automatically or manually
to satisfy the recommendations of the ITU-T Q.543.
Software Overload Detection
The software overload means a rapid decrease of memory availability because

processes have been abnormally generated compared to overall memory quantity.
Each MP regularly inspects the memory availability every six seconds using the
CROS primitive. When memory availability exceeds the threshold consecutively for
more than three times, it is regarded as an overload and the system generates an
alarm to the operator.
Processor Overload Detection
The processor overload detection is very important for overload controls, and the
item that can supremely reflect the event degree of a call event shall be selected.
Currently, ITU-T recommends the overload of the CPU occupancy(%), the number
of non-processed IPC(%) and memory availability(%). The processor overload can
be detected in real time by combining the CPU occupancy and non-processed IPC.
Operators can decide the reference values of the overload detection items. In
addition, it can detect the overload by regularly monitoring the amount of call
processing events, which has been introduced to the actual system together with
processor overload detection.
Page 5-19
Audit
The Audit regularly inspects the occurrence of an error for important data within the
programs and systems to maintain software integrity.
When the various types of data do not coincide with each other, a resource loss is
made or system failure may occur. Data inconsistency occurs for the following
cases :
Data has been destroyed because of the memory mutilation caused by operation
failures of the hardware and software.
The processes, in which the OS is under progress due to redundancy switching
or error handling, etc, are compulsorily destroyed.
The IPC abnormally operates.
Program error produces the wrong data.
When an audit function has been found to be faulty after the performance, selfrecoverable failures shall be recovered and irrecoverable failures are reported to the
operator.
Page 5-20
Page 5-21
CHAPTER 6
Supplementary Service Functions
The SDX-MSC II can handle supplementary functions. In addition to the services

mentioned in the document, the SDX-MSC II can provide new services within the
permitted area of the service functions, depending upon the users requests.
Supplementary Functions
Originating Call Barring
The original call barring can prohibit the originating calls sent by a specific
subscriber. When a subscriber(having no permission of call originating) sends a call,
the call cannot be connected and released. However, terminating the call can be
normally processed.
Despite the registrations of special services to the subscribers, the originating
call barring has priority.
Terminating Call Barring
The terminating call barring prevents the terminating calls for specific subscribers.
When calls arrive for a subscriber who cannot use terminating calls, a recorded
announcement and tone notifies the originating subscriber of the prohibition of the
originating calls for a specific time. However, originating calls are normally
processed.
Normal processing for billing on originating calls
Priority processing for terminating call barring even at the registration of special
services to the subscribers.
Page 6-1
Call Restriction by Operator
The call restriction by operator can restrict a specific type of originating call and
terminating call depending upon the subscribers grade level.
When a registered subscriber of the call restriction function tries to make a call
or the subscriber concerned is given a terminating call demand, recorded
announcement is sent to the calling party.
Page 6-2
Even if other special services than the originating and terminating call
prohibition function are registered for a subscriber, the call restriction by
operators can be processed with priority.
Each of originating calls restriction and terminating call restriction are processed
independently.
Priority Access
The priority access provides services to special subscribers over other general
subscribers by giving priority when an overload or emergency occurs at the system.
At the occurrence of system overload, the priority access is automatically
handled. At the occurrence of an emergency, however, the operators manually
run the priority access.
The priority access grade may vary depending upon the system overload state
and emergency situation.
Subscriber Observation
The subscriber observation stores information on all of the calls of a specific

subscriber and terminating calls of the subscriber concerned.
Upon requests of the HLR operator, the subscriber observation registers, deletes
and sends the call observation of the subscriber within optional MSC.
The subscriber observation sends both completed calls and uncompleted calls of
originating calls/terminating calls.
The subscriber, who has been given the originating call or terminating call
function, is not permitted to register the subscriber observation.
DTMF Protocol Control
The DTMF protocol control provides subscribers with an intelligent network service.
In other words, when a mobile communication terminal sends a DTMF signal to the
service system to use the intelligence network services(for instance, 700 Information
Service), it can convert the subscribers key information to the DTMF messages to
inform the MSC of the information. Then the MSC sends it to the service system
concerned by regenerating it into the DTMF signals.
Message Waiting Notification
Page 6-3
The message waiting notification informs subscribers of message storage at either the
voice post office box or Short Message Service Center (SMC). The subscribers can
find out message storage through a specific pip tone and mobile communication
terminals LED.
Page 6-4
Voice Message Retrieval
The voice message retrieval can make subscribers reproduce the messages stored at
the Voice Mail System (VMS). The subscribers, who have an active post office box
switching function, can store voice messages at the VMS and connect the VMS by
post office box connection code to regenerate the voice messages.
Remote Feature Control
The remote feature control can make a subscriber modify his or her services using
another terminal. The subscriber can call a specific RFC DN using a mobile
communication terminal or cable terminal, and can modify the services by entering
the Personal ID Number (PIN) and then feature code.
The remote feature control includes : terminating call switching, terminating call
rejection, accommodation of selective calls, voice/Fax post office box, and

originating call number ID display and barring, etc.
The remote feature control is not to be provided to the subscribers, who have
registered the originating call barring.
Malicious Call Trace
The malicious call trace can detect a specific telephone number and associated
information, when calling a telephone number of the terminating call of the
subscriber(a subscriber who has registered a malicious call trace) is required.
The MSC stores the originating call number of the call concerned. If the originating
call number cannot be identified, the malicious call trace stores the incoming route
and trunk number of the originating call.
SIM Inbound Roaming
The SIM Inbound Roaming can handle a normal call after the Global System for
Mobile Communication(GSM) subscriber performs roaming at the Code Division
Multiple Access(CDMA) network.
The GSM network uses the International Mobile Subscriber Identity (IMSI).
However, the current CDMA network does not support the IMSI and therefore the
GSM SIM card user cannot use the registration of the IMSI and associated services at
the CDMA network roaming. Therefore, the IMSI-MIN (Mobile Identity Number)
conversion is needed at the Global Location Register (GLR) prior to the use of the
Page 6-5
services.
When a GSM subscriber lends the terminal, the SIM Inbound Roaming assigns a
specific bands MIN number(using the MIN number assigned to the GSM subscriber
to identify the CDMA subscriber and the GSM subscriber) and registers the IMSIMIN conversion information at the GLR.
After the IMSI-MIN information is registered at the GLR, put the SIM card into the
terminal and perform normal call processing after the initial location registrations.
User Identification Module (UIM) Data Controls
The UIM terminal enables downloading UIM related data under a radio state, using
the OTASP of the IS-725-A.
In other words, the UIM subscriber can dial a specific Feature Code (OTASP Service
Feature Code) to download the UIM related data on the UIM terminal, and run the
SCP and Call Setup, then downloads the UIM related data over the SMS messages
among the SCP, MSC and terminals.
Local Wireless Telephone Call Busy Processing
The local wireless telephone call busy processing can control the calling state of
subscribers within the LAN at the MSC/VLR to prevent unnecessary paging
procedures and reduce the lowering of the call completion ratio caused by no
response to the paging.
Call Forwarding
The call forwarding transfers the call to be received to another subscribers terminal
or called party subscribers Voice Message System (VMS).
Call forwarding does not provide conflicting functions at the same time : absent
subscriber message service and the Do Not Disturb (DND).
Telephone service number of the no reply time(waiting time until calling is
switched to either another subscribers terminal or called party subscribers
VMS : basic value is 15 seconds) and the call forwarding can be changed.
The originating call barring and terminating call barring has priority over the call
forwarding.
The call forwarding may be classified as follows depending upon the subscribers
setup :
Page 6-6
CFD, Call Forwarding-Default

The CFD switches the terminating call of the subscriber when the subscriber is
busy or does not reply for a certain time(terminal OFF, no reply to the BTS
paging demand).
CFB, Call Forwarding-Busy
The CFB switches calls only when a subscriber is busy at the calling time.
CFNA, Call Forwarding-No Answer
The CFNA switches calls when a subscriber does not answer for a certain time.
CFU, Call Forwarding-Unconditional
The CFU switches calls unconditionally regardless of the status of a subscriber.
Page 6-7
Call Transfer (CT)
The Call Transfer (CT) connects holding calls with called calls by calling the new
subscriber after a subscriber holds the busy call(terminating call).
The CT is applied to only the terminating call.
Call transfer times has no limitation.
Billing continues even when the holding subscriber receives the holding voice.
Call Waiting (CW)
The CW replies to a new call when a subscriber is busy. When a new call arrives
during the calling, the CW informs a subscriber over a waiting tone. When a
subscriber presses the SEND button, they can hold the busy call and reply to a
waiting call. When they press the button again, they can reply to a holding subscriber
again and communicate with holding subscriber and new subscriber alternately.
When a subscriber having the CW is busy, they supply call waiting is supplied to
only one of the terminating calls at the same time.
The CW can perform the Cancel Call Waiting (CCW) and the call under the
CCW is effective for only a busy call.
Cancel Call Waiting (CCW)
The CCW cancels the call waiting when a subscriber does not wish to be interrupted
for a specific period of time, due to data communication or an important call, etc.
The CCW is to set up by a subscriber before call setup or during calling.
The CCW is permitted for only the one who has registered the CW.
Control party, who is using Three-Way Calling, Conference Calling, Call Hold
and Call Transfer, is to cancel the call waiting automatically.
Calling Number Identification Presentation (CNIP)
The CNIP sends information to the called party terminal : calling number of the call
arriving at the subscriber and other information.
When the one, who has registered the Calling Number Identification Restriction,
sends calls to the one who has registered the Calling Number Identification
Presentation, the terminal of terminating call subscriber does not display the calling
partys calling number and associated information(the Calling Number Identification
Page 6-8
Restriction has priority over the Calling Number Identification Presentation).

Calling Number Identification Restriction (CNIR)
The CNIR restricts the display of a subscribers telephone number and associated
information on the called party terminal.
When the one, who has registered the CNIR, sends messages to the one who has
registered the CNIP, the called party terminal does not display the calling party
number and associated information(the CNIR has priority over the CNIP).
Conference Calling (CC)
The CC allows the busy subscriber to call others in turn to let several subscribers talk
at the same time. Maximum number of calling parties is six. When the master
completes the call, the CC is to be terminated. However, when other people other
than the master cancels call, the CC function continues.
When the operator additionally gives the originating call barring and terminating
call barring to the one who has registered the CC, the originating call barring and
terminating call barring have priority over the Conference Calling (CC).
Under conference calling, special services(call transfer and call hold, etc) using
special codes are not permitted.
Do Not Disturb (DND)
The DND restricts the terminating call of a subscribers terminal. The MSC sends the
recording announcement or messages to inform the calling party(the one who has
sent the call to the one who has registered the DND) of No answer.
The Do Not Disturb, the Guide during Absence and the Call Forwarding, etc
cannot be used at the same time.
Originating call of the subscriber having active DND can be normally processed.
Mobile Access Hunting (MAH)
After making a group of specific subscribers, the MAH is the function that attempts
the call, which arrives in a pilot directory number (MAH pilot DN), in a specific
order to the subscribers within the group. The MAH calls one subscriber within the
group each time.
Flexible Alerting (FA)
Page 6-9
The FA is the function that makes a group of subscribers and simultaneously calls
the subscribers receiving terminating calls at the pilot directory number (FA pilot
DN) using different types of ringing tones. When the call is connected to the one who
replies first, the remaining call set up is cancelled.
Password Call Acceptance (PCA)
The PCA can make the calling party(the one who has sent messages to the one who
has set up the PCA) enter a password, and sends the calls only coinciding with the
password. When the password does not coincide, the PCA transmits the calling party
recorded announcement or messages of call barring.
Page 6-10
Selective Call Acceptance (SCA)
The SCA permits the terminating call for only the calling number, which exists at the
restriction list(list of calling numbers which allows the one, who uses the SCA, to
send the call to themselves). When a calling party, who has not been listed, sends
calls to the called party set by the SCA, the MSC sends paging broadcasting or
messages of the call barring to the calling party.
Up to ten of calling number can be put into control list.
Calling number of the control list can include the PSTN subscriber number.
Call Restriction and Do Not Disturb have priority over the SCA.
Subscriber PIN Access (SPINA)
The SPINA enters the Personal Identification Number (PIN) when a

subscriber(SPINA service subscriber) sends calls or uses special services, and sends
calls only at the entry of individual ID number. When the SPINA is used to prevent
the terminal from being used or copied illegally, its use of the subscribers on network
is restricted.
Subscriber PIN Intercept (SPINI)
The SPINI demands entry of the Personal Identification Number (PIN) when a
subscriber(SPINI service subscriber) sends special types of calls(local call, local call
& international call), and sends calls only at the correct entry of the PIN. The special
types of the call include local call and local call & international call, and the
emergency call does not demand the PIN. The SPINI is used to prevent the terminal
from being illegally used or copied, it restricts subscribers network use.
Three-Way Calling (TWC)
The TWC makes a busy subscriber hold the current call and then calls another
subscriber to let three persons talk at the same time.
Under busy three-way calling, the TWC cannot supply special services(Call
Transfer and Call Hold, etc) using special codes.
Conference Calling has priority over the Three-Way Calling (TWC) when both
calls have been registered at the same time.
Call Hold (CH)
Page 6-11
The CH is the function that makes a busy subscriber enter a Call Hold code to hold
the current call and to call another subscriber and talk. When the line is busy, the
subscriber on hold can talk with another subscriber alternately, but three subscribers
cannot talk at the same time.
Page 6-12
When the line is busy, only one subscriber is permitted to hold calling.
When the operator additionally gives call barring to a subscriber having the Call
Hold (CH), the barring has priority over the CH.
Billing continues even when the subscriber on hold is receiving a hold tone.
Short Message Service (SMS)
The SMS sends and receives short messages(about 140 characters) by mobile
communication terminal. The subscriber can transmit character messages using the
terminal keypad, and can also transmit the messages on the computer using a PC
communication program or the Information Provider (IP) service. The message
transmission way supports one-to-one system(one terminal sends messages) and
broadcasting system(several terminals send messages.).
Supports protocols of the IS-637 : SMS link layer, SMS relay layer and SMS
transport layer.
Provides a direct interface between the SMC and the MSC/HLR.
Voice Message Service (VMS)
The VMS is the function that records voice messages of the calling party when a
subscriber cannot receive a phone call, and then regenerates it upon the request of the
subscriber. When a voice message is generated, the VMS informs a subscriber of the
existence of the message at the Voice Mail Service to let them listen to the
message(s).
FAX Mail Service (FMS)
The FMS sends fax messages to multiple numbers of counterparts at the same time,
including a variety of functions which are inspection and receiving of the messages
registered on the bulletin board, checking of the messages received on the persons
own message service and transmitting of the messages to the facsimile of another
mail service subscriber.
Location Based Service (LBS)
The LBS checks the geographical place of the mobile communication subscriber and
provides them with geographical location information. The MSC has an interface
with the PDE, a location inquiry server, to carry out the LBS.
Page 6-13
Color Ring Back Tone (CRBT) Service
The CRBT Service replaces the single type of ring back tone(a tone produced until a
called party replies to the calling party against terminating call) with various kinds of
ring back tones(melody, advertisement, etc).
Page 6-14
Interactions Between Service Functions

Supplementary services may generate interactions between the service functions.
The functions have the following relations :
Table 6.1 Interactions between Service Functions
CW
CW
CC
>
CCW
CH
CT
>
>
DND
CFW
MAL
OCB
OCR
TCB
TWC
VMS
FMS
>
>
CNIP
CNIR
>
CC
>
CCW
CH
CT
DND
>
CFW
>
MAL
>
OCB
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
OCR
SCA
TCB
SCA
>
>
>
>
>
>
>
>
TWC
VMS
FMS
CNIP
CNIR
>
: Simultaneous service impossible
* : The one to start first has priority
> : The left service has priority.
Page 6-15
Page 6-16
CHAPTER 7
VLR Functions
Interactive Operation
Interworking relations between the VLR and network elements are :
Interworking Relations Between the VLR and the HLR
Mutual exchanges of data for location registrations

Service profile Tx/Rx for processing of terminating calls and originating calls
Data Tx/Rx for supplementary services
Data Tx/Rx for authentication and encryption.
Interworking Relations Between the VLR and the MSC
Survey and notice of Active/Inactive subscribers at calling and answering

The TLDN assignment of terminating call.
Interworking Relations between the VLR
When location registrations between the VLR occur at the use of the TMSI, the
IMSI of subscriber concerned is to be brought by Interworking with the previous
VLR to process the location registration procedures.
Page 7-1
Types of Data within the VLR

The following data is to be stored at the VLR :
Identification and Numbering Plan
IMSI : International Mobile Subscriber Identity

ESN : Electronic Serial Number
TMSI : Temporary Mobile Subscriber Identity
Types of Subscriber
Mobile Category : Types of the subscribers, such as Normal, CENTREX and

ISDN.
Priority : Priority of the subscribers to supply call processing services to only
limited subscribers at the occurrence of overload.
Authentication and Encryption
Authentication Capability : AUTHCAP

Indicates whether or not authentication of the terminal has been asked.
Authentication Period : AUTHPER
Time interval for authority inspection
Shared Secret Key : SSD
Call History Count : COUNT
Private Long Code Mask(PLCM)
Roaming
Page 7-2
Temporary Local Directory Number (TLDN)

Location Area Identification (LAI)
Cell Identification (CI)
MSC ID : The MSC identification is stored at the VLR and HLR as a temporary
subscriber data.
HLR ID : Recovers after HLR reset. The HLR ID is to be stored at the VLR
from the HLR at the location update.
Supplementary service data
The VLR stores parameters(provisioned or not provisioned) indicating whether

or not the subscriber can be given supplementary services.
At the supply of supplementary services, the VLR stores the types of services.
Additional Services
For more information on the supplementary services provided, refer to
Chapter 6. Supplementary Service Functions.
Page 7-3
Terminal State Data
Inactive flag of the terminal

Indicates inactive state of the terminal as temporary subscriber data.
Not Confirmed flag
After the VLR is reset and recovered, Not Confirmed Flag displays whether or
not the data is recovered by the subscriber or the HLR.
Call inhibit
The Call Inhibit displays whether or not the subscriber calling is suspended due
to either non-performance of the subscriber or operation of the MSC.
Billing
Billing category
Stores billing category data of the subscribers.
Call processing
Origination triggers
Defines origination trigger place, which is currently active by the subscriber.
Termination triggers
Defines terminating trigger place, which is currently active by the subscriber.
Origination Indicator
Displays call type permitted by the terminal upon the call origination
Supply of bearer service
Supply of teleservice
Bearer capability allocation
Others
Page 7-4
Carrier digits
Indicates carriers between the MSC, which have been designated in advance for
outgoing calls.
Functions
The VLR carries out the following functions :
Number/Identity Management
The VLR stores the IMSI, subscriber identification number of the terminal.
The VLR assigns the TMSI corresponding to the IMSI regarding the terminal,
which the VLR controls to prevent the IMSI from being disclosed on radio
channel(the MSC may assign it).
Call processing
The VLR interface for call processing is :

The VLR sends necessary information upon request of the MSC.
The VLR asks the HLR to inspect information upon request of the MSC.
Authentication and Encryption
The VLR carries out authentication between the terminal and CDMA system to
assure of data security of the subscriber and to prevent the terminal from being
illegally used.
The Authentication Center (AC) carries out authentication through the SSD.
When the SSD is shared, the VLR can also carry out authentication.
COUNT is used to identify a forged terminal. The COUNT records call history
and is stored in the VLR at sharing of the SSD.
The Authentication Center processes authentication failures and associated
recovery.
Registration notification/cancellation
When the terminal is registered at the VLR, location registration procedures are
used :
Normal location registrations due to location area changes of the terminal :
Upon requests of the location registration due to area changes of the terminal, the
VLR registers the location depending upon some factors which are normal
location registrations, periodical location registrations and recovery of the VLR,
Page 7-5
etc.
Registrations by changes of location areas :
The VLR receives location registration request message concerning visited
subscribers, and modifies the location information of each subscriber, and sends
the location change request messages to the HLR to get information on the
subscribers, and collects subscriber information. However, when the location
area with the VLR area changes, interworking with the HLR is not required.
Periodical Location Registrations
When the VLR receives periodical location registration request messages from
the MSC, it inspects the subscribers concerned. When the inspection is
completed, the VLR sends the location registration completion messages and
then completes location registration.
Registrations at recovery state of the VLR
When the VLR receives location registration requests at recovery state, it resets the
recovery confirmed flag and non-confirmed flag of the subscriber and carries out
the registration in the same way as the periodical location registrations.
Cancellation of location registrations
When the VLR receives registration cancellation messages from the HLR, it
cancels the subscriber information from the database.
MS Activation/Inactivation
The Inactivation means the actions, which the terminal takes to inform the mobile
communication network that the terminal is under a suspension state(for example,
terminal OFF). On the other hand, activation means the actions having an opposite
concept of the inactivation(for example, terminal power on).
When the VLR is given the inactivation signal from the terminal, the VLR database
sets the flag of the terminal and informs the HLR of the situation. Recovery of the
activation is informed to the VLR through location registration procedures.
Search
When the VLR is given terminating call requests during recovery, it does not send
terminating call subscribers call requests but terminal search requests to the MSC,
which calls the terminating call subscriber using all of the terminals.
When completing the call, the VLR receives answers on the terminal search
Page 7-6
messages from the MSC, including the LAI (Location Area Identity).
Subscriber tracing
The Subscriber Tracing is to be used to trace the location and calls. When the
subscriber tracing is registered upon requests of the HLR/OMC operator, the HLR
asks the VLR to trace the calls. At this time, the VLR sets flags and informs either the
HLR or the OMC of the associated information.
HLR fault recovery
After recovering failures of the HLR, the VLR is informed of the recovery state and
resets the recovery flag of all of the HLR related terminals. Recovery flag reset
procedure of the VLR is the same as that of the VLR.
Page 7-7
VLR Restoration
When a failure occurs at the VLR database, all of the subscriber related information
is to be removed. The HLR is to be informed of the failure.
Page 7-8
ABBREVIATION
A
AAA
Authentication, Authorization, Accounting
ADPCM
Adaptive Differential Pulse Code Modulation
AIS
Alarm Indication Signal
APC
Alarm Panel Control Block
APC
Alarm Panel Control
APCIA
Alarm Panel Control Interface Assembly
AR
Alternate Route
ASIP
Analog Subscriber Interface Processor
ASMI
Access Switch Maintenance Interface Block
ASMP
Access Switching Maintenance Processor
ASMS
Access Switching Maintenance Subsystem
ASP
Access Switching Processor
ASP/ASPP Access Switching Processor/Access Switch Peripheral Processor

ASS
Access Switching Subsystem
ASS-C
Access Switching Subsystem Complex
ASS-P
Access Switching Subsystem Primary Rate Interface
ASS-W/T Access Switching Subsystem Wireless subscriber/Trunk

AuC
Authentication Center
BER
Bit Error Rate
BHCA
Busy Hour Call Attempts
BLIP
Base Station Link Interface Processor
Abbreviation-1
Abbreviation
BSC
Base Station Controller
BSM
Base Station Manager
BTS
Base station Transceiver System
CALIA
Compact Analog Line Interface Assembly
CAMA
Centralized Automatic Message Accounting
CC
Conference Calling
CCBS
Customer Care and Billing System
CCITT
International Telegraph and Telephone Consultative Committee
CCM
Charging Counter Metering
CCMS
Central Control Maintenance Subsystem
CCMX
Conference Call Mix
CCP
Call Control Processor
CCPP
Central Control Peripheral Processor
CCS
Central Control Subsystem
CCW
Cancel Call Waiting
CDG
Charging Data Generation Block
CDL
Central Data Link Block
CDMA
Code Division Multiple Access
CDPIA
Clock Distribution & Processor Interface Assembly
CDR
Charging Data Recording Block
CDTIA
CEPT Digital Trunk Interface board Assembly
CFB
Call Forwarding-Busy
CFD
Call Forwarding-Default
CFNA
Call Forwarding-No Answer
CFU
Call Forwarding-Unconditional
CH
Call Hold
CHILL
CCITT High-level Language
CI
Control Interworking Block
CIBPA
Communication Interworking Back Panel Assembly
CIM
Charge Interface Management Block
CIN
Control Interworking on Node
CIN
Communication Interworking Network
CINI
Control Interworking Node Interface
Abbreviation-2
CINIA
Communication Interworking Node Interface Assembly
CINMA
Communication Interworking Node Maintenance Assembly
CIP
Control Interworking Processor
CIS
Control Interworking Subsystem
CLIP
Central Link Interface Processor
CNIP
Calling Number Identification Presentation
CNIR
Calling Number Identification Restriction
CPS
Call Processing Supervisor
CPSE
CHILL Programming Support Environment
CRBT
Color Ring Back Tone
CROS
Concurrent Real-time Operating System
CSS
Central Switching Subsystem
CT
Configuration Table
CT
Call Transfer
CTPS
Call Trace & Path Set-up Block
CTRIA
Central Optic Transfer & Receiver Interface Assembly
CW
Call Waiting
Abbreviation
Abbreviation-3
Abbreviation
D
DAT
Digital Audio Tape
DBMS
Data Base Manager System
DCI
Digital CEPT Interface Block
DCIP
Digital CEPT Interface Processor
DCN
Data Core Network
DG
Data Generator
DKU
Disk Unit
DLI
Data Link Interface
DLL
Digital Local Line
DND
Do Not Disturb
DPRAM
Dual Port RAM
DR
Direct Route
DRC
Data Read Controller Block
DSBPA
Digital Service circuit Back Panel Assembly
DSBPA
Digital Service circuit Back Panel
DSC
Digital Service Circuit
DSCMA
Digital Service circuit for Call Mixer Assembly
DSDTA
Digital Service circuit for Digital trunk Test Assembly
DSM
Device Status Management Block
DSMSA
Digital Service circuit for Multi-frequency Signaling Assembly
DSVMA
Digital Service circuit for Voice Message Assembly
DTBPA
Digital Trunk Back Panel Assembly
DTI
Digital T1 Interface Block
DTI
Digital Trunk Interface
DTMF
Dual Tone Multi-Frequency
EC
Echo Canceller
ESN
Electronic Serial Number
ESS
Electronic Switching System
EXIP
Ether Network and X.25 Interface Processor
Abbreviation-4
Abbreviation
F
FA
Flexible Alerting
FI
Fault Interface Block
FL
Function List Document
FLM
Fault Management Block
FMS
FAX Mailing Service
FMS
FAX Mail Service
FMSC
FMS Control Block
FOL
Fiber Optics Link
FPBPA
Frame relay & Packet protocol Back Panel Assembly
FPH
Frame relay & Packet Handler
FPHCA
Frame relay & Packet protocol Handling Controller Assembly
FPRCA
Frame relay & Packet protocol Routing Controller Assembly
FR
Fault Report
FS
Frame Synchronization
GLR
Global Location Register
GSI
Global Service Interface Block
GSM
Global System for Mobile Communication
GSP
Global Service Processor
HDD
Hard Disk Drive
HLR
Home Location Register
HOC
Handoff Control Block
HRC
Highway Rate Conversion
HTR
Hard-To-Reach
HW
Highway
IBG
Inter Block Gap
Abbreviation-5
Abbreviation
Abbreviation-6
IDCPA
ISDN D-channel Control Processor Advanced
IMSI
International Mobile Subscriber Identity
IN
Intelligent Network
INP
Interconnection Network Processor
INP
Interconnection Network Processor
INPP
Inter Network Peripheral Processor
INS
Interconnection Network Subsystem
INST
Inter Network Supervision & Test Block
IOHU
In Out Hardware Unit
IOM
I/O Management
IP
Intelligent Peripheral
IPBPA
ISDN Primary Subscriber Back Panel Assembly
IPC
Interprocessor Communication
IPCIA
ISDN Primary Subscriber CEPT Interface type A
ISDN
Integrated Services Digital Network
ISUP
ISDN User Part
IWF
Interworking Function
Abbreviation
L
LAI
Location Area Identifier
LAMA
Local Automatic Message Accounting
LBS
Location Based Service
LRP
Location Registration Processor
LRP
Location Register Processor
LRS
Location Registration Subsystem
LSC
Local Service Control Block
LSCS
Local Signaling Channel Supervisor
LSPS
Local Switch Path Supervisor
LTRIA
Local optic Transceiver Interface Assembly
MAH
Mobile Access Hunting
MANM
Mobile Announcement Hardware Block
MBI
Message Billing Index
MC
Menu and Command Analyzer
MCAW
Mobile Call Waiting Control Block
MCC
Mobile Call Control Block
MCFW
Mobile Call Forwarding Control Block
MCHD
Mobile Call Hold Control Block
MCS
Maintenance Control Subsystem
MCTR
Mobile Call Trace Control Block
MDSS
Multifunction Digital Signaling Service
MFP
Multi-Function Peripheral
MGCP
Master Clock Generator Control Processor
MHP
Mobile Handoff Part
MIN
Mobile Identity Number
MIT
Maintenance Interface Block
ML
Modeling Language
MLSI
Mobile Local Service Interface Block
MMC
Man Machine Command
MMDST
Man Machine Device Supervision and Test Block
MMP
Man Machine Processor
Abbreviation-7
Abbreviation
MMS
Man Machine Subsystem
MMUL
Mobile Multiway Calling Block
MNC
Mobile Network Code
MP
Main Processor
MPBPA
Main Processor Back Panel
MPBPB
Main Processor Back Panel
MPC
Mobile Paging Control
MPDM
Main Processor Duplication Manager
MPDMA
Main Processor Duplication Manager Assembly
MPDMA
MPDMA
MPH
Main Processor Hardware Block
MPSH
Main Processor Status Handling Block
MR
Modification Request
MRP
Mobile Routing Part
MSBIA
Main Processor SCSI-bus Interface
MSC
Measurements and Statistics Control Block
MSC
Mobile Switching Center
MSDP
Measurement and Statistics Data Processing Block
MSL
Mobile Call System Library
MSS
Measurements and Statistics Subsystem
MT
Magnetic Tape Drive
MTCS
Mobile Traffic Control Subsystem
MTU
Magnetic Tape Unit
MVQT
Mobile Voice Quality Test
MVQT
Mobile Voice Quality Test
MVQTA
Mobile Voice Quality Test Assembly
NCA
No Circuit Available
NCD
Network Synchronization Clock Distribution Block
NDH
Number Data Handling Block
NES
Network Synchronization Block
NES
Network Synchronization
NEW
New-generation Exchange Workbench
Abbreviation-8
NMC
Network Management Center
NMI
Network Management Interface Block
NMS
Network Management Subsystem
NMSI
National Mobile Station Identification
NPS
Network Performance Supervision Block
NPSV
Supervise Network Performance
NSBPA
Network Synchronization Back Panel Assembly
NSCG
Network Synchronization Clock Generation
NSCGA
Network Synchronization Clock Generation Assembly
NSCMA
Network Synchronization Clock Maintenance Assembly
NSM
Network Synchronization Management
NSP
Network Synchronization Processor
NTP
Number Translation Processor
NTR
Number Translation Block
NWC
Network-Wide Control Block
Abbreviation
Abbreviation-9
Abbreviation
O
O&M
Operation and Maintenance
OMBPA
Operation & Maintenance processor Back Panel
OMC
Operation & Maintenance Center
OMP
Operation & Maintenance Processor
OMP
Operation & Maintenance Processor
OPP
Operation Peripheral Processor
OTRMA
Optic Transceiver Module Assembly
OTRMA
Optic Transceiver Module Assembly
PB
Push Button
PBA
Printed Circuit Board Assembly
PBUS
Packet Bus
PCA
Password Call Acceptance
PCM
Pulse Code Modulation
PCN
Personal Communication Network
PCS
Personal Communication Service
PDGN
Packet Data Gateway Node
PDSN
Packet Data Serving Node
PLCM
Private Long Code Mask
PLCP
Packet Layer Control Processor
PLM
Processor Load Management Block
PLMN
Public Land Mobile Network
PMS
Processor Maintenance Subsystem
POVLD
Processor Overload
PP
Peripheral Processor
PP
Peripheral Processor
PPH
Peripheral Processor Hardware Block
PPM
Periodic Pulse Metering
PPOS
Peripheral Processor Operating System
PRI
Primary Rate Interface
PRN
Printout Reference Number
PSI
Primary Rate Subscriber Interface Block
Abbreviation-10
PSPDN
Packet Switched Public Data Network
PSTN
Public Switched Telephone Network
R2MFC
R2 Multi-Frequency Compelled
RA
Rate Adapter
RAPU
Remote Alarm Panel Unit
RCBPA
Remote Control Back Panel Assembly
RCO
Route Control Block
RDH
Route Data Handling Block
RG
Ring Generator Block
RIC
Request Interface Controller Block
Abbreviation
RMOS_PP Real time Multitasking Operating System _ Peripheral Processor

RR
Rerouting
RSGUA
Ring Signal Generator Unit Assembly
S7DH
Signaling No. 7 Data Handling Block
S7DIR
Signaling No. 7 Data Initial and Restore Block
S7H
Signaling system No.7 protocol Handler
S7INM
Signaling No. 7 Internal Network Management Block
S7LS
Signaling No. 7 Link Set Management Block
S7SDH
Signaling No. 7 SCCP Data Handling Block
S7SL
Signaling No. 7 Signaling Link Management Block
S7SMG
Signaling No. 7 Signaling Connection Control Part Management
S7SRC
Signaling No. 7 SCCP Routing Control Handling
SACL
Subsystem Alarm collection
SAPI
Service Access Point Identifier
SC
Sequence Chart
SCA
Selective Call Acceptance
SCCI
Subscriber Circuit Control Interface
SCCIA
Subscriber Circuit Control Interface Assembly
SCCP
Signaling Connection Control Part
SCCS
Signaling Connection Control Subsystem
Abbreviation-11
Abbreviation
Abbreviation-12
SCE
Service Creation Environment
SCM
Space Switch Control Memory
SCM
System Clock Management Block
SCP
Service Control Point
SCS
Switch Congestion Supervision
SDU
Storage Device Unit
SHW
Subhighway
SIBPA
Subscriber Interface Back Panel Assembly
SIOH
Serial Input Output Handler
SL
Signaling Link
SLCS
Subscriber Line Concentration Switch
SLI
Subscriber Line Interface
SLME
Subscriber Line Measurement Equipment
SMDX
Subhighway Multiplexer & Demultiplexer
SMDXA
Sub-highway Multiplex & Demultiplex Assembly
SME
Signaling Message Encryption
SMHP
Signaling Message Handling Processor
SMHS
Signaling Message Handling Subsystem
SMS
Service Management System
SMS
System Maintenance Subsystem
SMS
Short Message Service
SMSC
Short Message Service Center
SMTS
Signaling Message Transfer Subsystem
SPBPA
Signaling System No.7 Protocol Handler Back Panel Assembly
SPC
Stored Program Control
SPINA
Subscriber PIN Access
SPINI
Subscriber PIN Intercept
SPM
Software Product Management
SS No.7
Signaling System No.7
SSBPA
Space Switch Back Panel Assembly
SSC
System Status Control Block
SSCA
Space Switch Clock Distribution Board Assembly
SSCM
Space Switch Control & Maintenance
SSCO
Subscriber Service Control Block
SSD
Shared Secret Data
SSD
Shared Secret Key
SSIO
Space Switch Input & Output
SSL
Space Switch & Link
SSMX
Space Switch Matrix
SSMXA
Space Switch Matrix Assembly
SSP
Service Switching Point
SSP
Space Switch Processor
SSPHA
Signaling System No.7 Handler Assembly
SSS
Signaling and Service Subsystem
SSW
Space Switch Block
ST
Signaling Terminal Block
STG
Signaling Terminal Group
STM
Signaling Terminal Management Block
STN
Signaling Terminal Network Block
STNI
Signaling Terminal Network Interface Board Assembly
STP
System Test Plant
STRPT
Status Report to NMC
TBSEL
TD-Bus Selection
TC7
Trunk Call Control for SS No.7
TCAP
Transaction Capability Application Part
TCAS
Transaction Capability & Application Subsystem
TD-Bus
Telephony Device Control Bus
TDCMA
Telephony Device Control Master Assembly
TDCMA
Telephony Device Control Master
TDCS
Traffic Data Collection System
TDMA
Time Division Multiple Access
TDN
TDX Development Network
TDSH
Telephony Device Supervision Handling Block
TDSL
Telephony Device System Library Block
TDTIA
T1 Digital Trunk Interface board Assembly
TI
Trunk Interface Block
TLDN
Temporary Local Directory Number
TLT
Trunk Line Test Block
TMBPA
Telephony Device Control Master Back Panel
Abbreviation
Abbreviation-13
Abbreviation
TMS
Test Management Subsystem
TMSI
Temporary Mobile Subscriber Identity
TSBPA
Time Switch Back Panel Assembly
TSCMA
Time Switch Control & Maintenance Assembly
TSL
Time Switch Link
TSL
Time Switch & Link
TSP
Time Switch Processor
TSW
Time Switch Block
TWC
Three-Way Calling
UIM
User Identification Module
UPI
No. 7 User Part Interface Block
VDC
Virtual Data Controller Block
VLR
Visitor Location Register
VLR
Visited Location Register
VMH
Voice Message Handling Block
VMHP
Voice Message Handling Primary Block
VMHS
Voice Message Handling Secondary Block
VMS
Voice Mailing System
VMS
Voice Message Service
VP
Voice Privacy
VSM
Virtual Switching Machine
X.25CM
X.25 Communication Management Block
Abbreviation-14
SDX-MSC II
System Description
2002 Samsung Electronics Co., Ltd.
All rights reserved.
Information in this document is proprietary to SAMSUNG
Electronics Co., Ltd
No information contained here may be copied, translated,
transcribed or duplicated by any form without the prior written
consent of SAMSUNG.
Information in this document is subject to change without notice.
Visit us at
http://www.samsungnetwork.com

SDX-MSC Ii SD

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SDX-MSC Ii SD

Transféré par

Droits d'auteur :

Formats disponibles

SDX-MSC II

Document Content and Organization

Chapter 1. SDX-MSC II Introduction

This chapter describes the introduction of the SDX-MSC II.

This chapter describes the hardware of the SDX-MSC II.

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00Introduction

Chapter 3. Software Architecture

This chapter describes the SDX-MSC II software.

This chapter describes the VLR build-into the SDX-MSC II.

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00

Troubleshooting when a database fault occurs for the VLR.

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00Introduction

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00

This page intentionally left blank

SAMSUNG Electronics Co., Ltd.

CHAPTER 1. SDX-MSC II Introduction

Mobile Communication Network Configuration............................................................1-2

Functions of the SDX-MSC II.......................................................................................... 1-5

Specifications of the SDX-MSC II...................................................................................1-6

Features of the SDX-MSC II............................................................................................. 1-8

Configuration of the SDX-MSC II....................................................................................1-9

CHAPTER 2. Hardware Architecture

ASS Architecture............................................................................................................. 2-2

DTI Block.................................................................................................................. 2-4

PRI Block.................................................................................................................. 2-5

SLI Block................................................................................................................... 2-6

TSL Block.................................................................................................................. 2-7

DSC Block................................................................................................................. 2-9

SAMSUNG Electronics Co., Ltd.

FPH Block............................................................................................................... 2-10

S7H Block............................................................................................................... 2-11

MVQT Block............................................................................................................ 2-12

ASP/ASPP Block..................................................................................................... 2-13

INS System..................................................................................................................... 2-14

SSL Block................................................................................................................ 2-16

CIN Block................................................................................................................ 2-18

NES Block............................................................................................................... 2-19

INP Block................................................................................................................ 2-20

INPP Block.............................................................................................................. 2-21

CCS Architecture........................................................................................................... 2-22

OMP Block.............................................................................................................. 2-23

APC Block............................................................................................................... 2-24

CCPP Block............................................................................................................ 2-25

LRS Structure................................................................................................................. 2-26

SDX-MSC II System Description/Ed.00

The Processor Structure............................................................................................... 2-28

Processor Configuration of Each Subsystem..........................................................2-29

Remote Alarm Panel Unit (RAPU)..........................................................................2-32

Auxiliary Memory Unit............................................................................................. 2-32

Input/Output Device................................................................................................ 2-32

CHAPTER 3. Software Architecture

Features of the Software................................................................................................. 3-1

Software Architecture...................................................................................................... 3-3

SAMSUNG Electronics Co., Ltd.

SDX-MSC II System Description/Ed.00

CHAPTER 4. Call Processing and Mobility Managment

Number Translation and Sending...................................................................................4-1