Railway Operational Communication Solution GSM-R 5.0 GTSOFTX3000 Product Description V1.0 (20120925)

eWSE GSM-R 5.
0 GTSOFTX3000
Product Description
Issue
1.6
Date
2012-05-03
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 1.6 (2012-05-03)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eWSE GSM-R 5.0 GTSOFTX3000 Product Description
About This Document
About This Document

Summary
This document describes HUAWEI GTSOFTX3000 mobile switching center (MSC) server in
terms of product orientation, product features, services and functions, product structure,
interfaces and protocols, application scenarios, and technical specifications.
Intended Audience
This document is intended for:
Sale engineers
Customers
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue V1.1 (2012-05-03)

This issue is the first formal release.
Issue 1.6 (2012-05-03)

ii
Contents
Contents
About This Document .................................................................................................................... ii
1 Overview......................................................................................................................................... 1
1.1 Background ...................................................................................................................................................... 1
1.2 Huawei GSM-R Solution ................................................................................................................................. 1
1.2.1 MSC ........................................................................................................................................................ 2
1.2.2 GCR ........................................................................................................................................................ 3
1.2.3 IWF ......................................................................................................................................................... 3
1.2.4 VLR ........................................................................................................................................................ 3
1.2.5 HLR ........................................................................................................................................................ 3
1.2.6 AUC ........................................................................................................................................................ 3
1.2.7 EIR .......................................................................................................................................................... 3
1.2.8 FFN ......................................................................................................................................................... 3
1.2.9 SSP .......................................................................................................................................................... 4
1.2.10 SCP ....................................................................................................................................................... 4
1.2.11 BSC ....................................................................................................................................................... 4
1.2.12 BTS ....................................................................................................................................................... 4
1.2.13 Mobile Terminals .................................................................................................................................. 4
1.2.14 OMC ..................................................................................................................................................... 5
1.2.15 AC ......................................................................................................................................................... 5
1.2.16 ISS......................................................................................................................................................... 5
1.3 GTSOFTX3000 Orientation ............................................................................................................................. 5
1.4 Application Entities of the GTSOFTX3000 ..................................................................................................... 6
1.4.1 MSC Server............................................................................................................................................. 6
1.4.2 VLR ........................................................................................................................................................ 6
1.4.3 SSP .......................................................................................................................................................... 6
1.4.4 Built-in GCR ........................................................................................................................................... 7
2 Product Features ............................................................................................................................ 8

2.1 High Efficiency ................................................................................................................................................ 8
2.1.1 High Equipment Efficiency..................................................................................................................... 8
2.1.2 High Network Efficiency ........................................................................................................................ 9
2.1.3 High Operation and Maintenance Efficiency .......................................................................................... 9
2.2 High-Quality Service Provisioning .................................................................................................................. 9
2.2.1 High Reliability ....................................................................................................................................... 9
Issue 1.6 (2012-05-03)

iii
Contents
2.2.2 Excellent Voice Quality......................................................................................................................... 10

2.2.3 Value-added Services ............................................................................................................................ 12
2.3 Smooth Migration .......................................................................................................................................... 12
2.4 System Features ............................................................................................................................................. 13
2.4.1 Softswitch ............................................................................................................................................. 13
2.4.2 Multi-SP Technology and 2 Mbit/s Signaling Technology.................................................................... 13
2.4.3 Middle-Ware Technology ...................................................................................................................... 13
2.4.4 Advanced GSM-R Network Platform ................................................................................................... 14
3 Services and Functions ............................................................................................................... 15

3.1 Basic Services ................................................................................................................................................ 15
3.1.1 Teleservices ........................................................................................................................................... 15
3.1.2 Supplementary Services ........................................................................................................................ 16
3.1.3 IN Services ............................................................................................................................................ 18
3.1.4 Value-added Services ............................................................................................................................ 18
3.2 Basic Functions .............................................................................................................................................. 18
3.2.1 Mobility Management ........................................................................................................................... 19
3.2.2 Security Management ........................................................................................................................... 21
3.2.3 Call Control........................................................................................................................................... 22
3.2.4 SSP ........................................................................................................................................................ 23
3.2.5 Handover ............................................................................................................................................... 24
3.2.6 Charging ................................................................................................................................................ 25
3.2.7 CAMEL Services .................................................................................................................................. 29
3.3 GSM-R Dispatching Service and Function .................................................................................................... 31
4 Product Structure......................................................................................................................... 32
4.1 Hardware ........................................................................................................................................................ 32
4.1.1 Logical Structure ................................................................................................................................... 32
4.1.2 Physical Structure ................................................................................................................................. 34
4.2 Software ......................................................................................................................................................... 38
4.2.1 Overall Structure ................................................................................................................................... 38
4.2.2 Service Processing Software ................................................................................................................. 39
4.2.3 Server Software ..................................................................................................................................... 40
5 Interfaces and Protocols ............................................................................................................. 43

5.1 Physical Interfaces ......................................................................................................................................... 43
5.2 Protocol Interfaces ......................................................................................................................................... 46
6 Networking and Application .................................................................................................... 50

6.1 Networking..................................................................................................................................................... 50
6.2 Application ..................................................................................................................................................... 51
6.2.1 Typical Networking............................................................................................................................... 51
6.2.2 WIN Networking................................................................................................................................... 52
6.2.3 IP Networking ....................................................................................................................................... 53
Issue 1.6 (2012-05-03)

iv
Contents
7 Operation and Maintenance ..................................................................................................... 54

7.1 Fault Management .......................................................................................................................................... 54
7.2 Performance Measurement ............................................................................................................................. 55
7.3 Charging Management ................................................................................................................................... 56
7.4 Security Management ..................................................................................................................................... 57
7.5 Terminal System ............................................................................................................................................. 57
8 Reliability ..................................................................................................................................... 59
8.1 Hardware Reliability ...................................................................................................................................... 59
8.1.1 Distributed Hardware Structure ............................................................................................................ 59
8.1.2 Redundancy Design .............................................................................................................................. 59
8.1.3 Derating Design .................................................................................................................................... 59
8.1.4 Maintainability Design .......................................................................................................................... 60
8.1.5 Selection and Usage of Components ..................................................................................................... 60
8.1.6 Power Reliability .................................................................................................................................. 60
8.2 Software Reliability ....................................................................................................................................... 61
8.2.1 Compliance with the CMM Flow ......................................................................................................... 61
8.2.2 Protective Measures .............................................................................................................................. 61
8.2.3 Fault Tolerance ...................................................................................................................................... 61
8.2.4 Troubleshooting .................................................................................................................................... 61
8.2.5 Support of Hot Patches ......................................................................................................................... 61
8.3 Charging Reliability ....................................................................................................................................... 62
8.3.1 Hardware Reliability of Charging Gateway .......................................................................................... 62
8.3.2 Software Reliability of Charging Gateway ........................................................................................... 62
8.3.3 CDR Reliability .................................................................................................................................... 63
8.4 Data Reliability .............................................................................................................................................. 65
9 Technical Specifications ............................................................................................................ 66

9.1 System Capacity ............................................................................................................................................. 66
9.2 System Processing Capability ........................................................................................................................ 67
9.3 Call Setup Duration ........................................................................................................................................ 68
9.4 Wireless Train Control ................................................................................................................................... 68
9.5 Power Supply ................................................................................................................................................. 69
9.6 Power Consumption ....................................................................................................................................... 69
9.7 Clock System ................................................................................................................................................. 69
9.8 Reliability ....................................................................................................................................................... 71
9.9 Environmental Requirements ......................................................................................................................... 71
9.10 EMC ............................................................................................................................................................. 72
9.11 Operating Environment ................................................................................................................................ 73
9.12 Interfaces and Standards ............................................................................................................................... 73
A Acronyms and Abbreviations .................................................................................................. 75
Issue 1.6 (2012-05-03)

1 Overview
Overview
1.1 Background
Huawei Global System for Mobile Communications - Railway (GSM-R) solution is an
integrated, customizable solution that can meet the needs of various railway operators and
networks. It is secure and reliable, and easy to maintain, operate, and manage.
1.2 Huawei GSM-R Solution

As shown in Figure 1-1, the GSM-R mobile switching center (MSC) plays an important part
in Huawei GSM-R mobile communication system and integrates the MSC server and the
media gateway (MGW). As a GSM-R MSC server, the GTSOFTX3000 supports standard
interfaces and all the services defined in the European integrated railway radio enhanced
network (EIRENE) specifications and can interconnect with non-Huawei devices, for example,
a dispatching center.
Issue 1.6 (2012-05-03)

1 Overview
Figure 1-1 Networking of Huawei GSM-R solution
AC Server: Acknowledge
Center Server
EIR: Equipment Identification
Register
HLR: Home Location Register
MSC: Mobile Switching
Center
SCP: Service Control Point
IWF: Interworking Function
ISS: Integrated Service Server
MGW: Media Gateway
BSS: Base Station Subsystem
VLR: Visitor Location Register
FFN: Follow-Me function node
GCR: Group call register

OMC: Operation & Maintenance
Center
GGSN: Gateway GPRS Support
Node
PSTN: Public Switched Telephone
Network
IP PBX: PBX that supports Simple
Internet Protocol (SIP)
MS: Mobile Station

PBX: Private Branch Exchange
SGSN: Serving GPRS Support
Node
AUC: Authentication Center
1.2.1 MSC
The MSC consists of the MSC server and the MGW. It controls calls and manages the
communication of mobile stations (MSs) within the local network as well as those with other
networks such as the Public Switched Telephone Network (PSTN), Integrated Services Digital
Network (ISDN), Packet Switched Public Data Network (PSPDN), and other mobile networks.
It also provides the interworking function (IWF), group call register (GCR), and charging
information.
Issue 1.6 (2012-05-03)

1 Overview
1.2.2 GCR
The GCR is a new functional entity employed in the GSM-R system to enable the advanced
speech call item (ASCI). It stores the data of the voice group call service and provides
information for the voice group call service (VGCS) and voice broadcast service (VBS).
1.2.3 IWF
The GSM-R is equipped with the IWF subrack, which resides in the UMG8900 cabinet, and
enables the data service interworking between the GSM-R and other networks (such as the
PSTN and ISDN).
1.2.4 VLR
The visitor location register (VLR) stores the temperate details of subscribers active in the
MSC area. It provides necessary conditions for call connection of mobile subscribers. The
VLR can be regarded as a dynamic database.
1.2.5 HLR
The home location register (HLR) is the central database of the GSM-R system. It stores the
detailed data of all mobile subscribers within the HLR area.
1.2.6 AUC
The authentication center (AUC) stores authentication algorithms and ciphering keys to
prevent illegal subscribers from accessing the system, ensuring communication security over
the air (Um) interface.
1.2.7 EIR
The equipment identity register (EIR) stores the international mobile station equipment
identity (IMEI).
The IMEIs are stored in the following three lists:
White list
List of IMEIs allowed for use.
Black list
List of IMEIs monitored for use due to faults.
Gray list
List of IMEIs forbidden for use due to theft.
By checking the three lists, network operators provide, restrict, or reject services to
subscribers, ensuring uniqueness and security of the mobile devices.
1.2.8 FFN
The follow me function node (FFN) is a new functional entity employed in the GSM-R
system to enable functional addressing. It stores functional numbers and the mapping between
functional numbers and MSISDNs. Based on this mapping, the FFN can translate functional
numbers to mobile station international ISDN numbers (MSISDNs).
Physically, the AUC, EIR, and FFN are integrated with the HLR.
Issue 1.6 (2012-05-03)

1 Overview
1.2.9 SSP
The service switching point (SSP) switches intelligent services and implements the interface
functions between the MSC and the SCP.
1.2.10 SCP
The service control point (SCP) stores the service control logic for intelligent services. It
sends call control commands to the SSP based on the control logic, implementing flexible
control over wireless intelligent services.
1.2.11 BSC
The base station controller (BSC) implements the following functions:
Wireless network resources management
Cell configuration data management
Power control
Positioning
Handover
1.2.12 BTS
The base transceiver station (BTS) is controlled by the BSC. It implements the following
functions:
Radio connection
Conversion between radio and wired signal
Radio diversity
Radio channel encryption
Frequency hopping
1.2.13 Mobile Terminals

There are four mobile terminals in the GSM-R, including:
Cab Radio
General Purpose Handset (GPH)
Operational Purpose Handset (OPH)
Operational Purpose Handset of Shunting (OPS)
Cab Radio
A cab radio is a vehicle mounted station installed on the locomotive and train. The driver uses
the cab radio for wireless dispatching communications and data transmission between the
train and the ground.
The cab radio consists of three parts:
MMI (Human-machine interfaces)
MRM (mobile Radio modules)
Applications
Issue 1.6 (2012-05-03)

1 Overview
GPH
The GPH is used by the railway staff in common cases. The GPH is the same with an ordinary
GSM handset except that the GPH is added with the PTT push-button, and provides GSM-R
services, such as VGCS/VBS, eMLPP, and functional addressing.
OPH
The OPH is used by the railway staff who charges the train running. Different with an
ordinary handset, the OPH is added with an emergency call push-button, so that the user can
press it to initiate railway emergency calls quickly.
OPS
Supporting the shunting mode, the OPS is the OPH used for the shunting service. The OPS in
the shunting mode (initiating a shunting group call) can send link assurance signaling (LAS)
automatically on a regular basis and notify each member of the shunting group that the current
group call link is normal.
The four mobile terminals vary in services, but are applied to the GSM-R and the public
GSM.
1.2.14 OMC
The operation and maintenance center (OMC) manages and monitors the entire GSM-R
network. The OMC connects to the GSM-R network equipment (MSC, BSC, HLR, and FFN)
and it also connects to a computer as the man-machine interface. The OMC provides multiple
functions such as real-time monitoring, status report, and fault diagnosis.
1.2.15 AC
The acknowledge center (AC) processes and answers the AC messages from mobile terminals.
It also stores the AC data and provides means such as query for future analysis. The AC is
used for railway emergency calls.
1.2.16 ISS
The ISS provides an MLP interface for subscriber information interaction between the
dispatching system and the GTSOFTX3000. The ISS allows authorized users to visit the ISS
database using web pages and to manage functional numbers and query engine information.
1.3 GTSOFTX3000 Orientation

As a GSM-R MSC server, the GTSOFTX3000 provides rich GSM-R railway services in
cooperation with other equipment, such as:
VGCS
VBS
Enhanced multi-level precedence and preemption (eMLPP) service
Functional addressing
Call matrix
Railway emergency call
Issue 1.6 (2012-05-03)

1 Overview
In addition, it provides multiple value-added services and user-defined supplementary

services as required by mobile operators.
1.4 Application Entities of the GTSOFTX3000

The GTSOFTX3000 is embedded with the VLR and GCR functions and can also serve as an
SSP.
1.4.1 MSC Server

The MSC server enjoys the following features:
Acting as the control-layer equipment in the CN CS domain
Providing external signaling interfaces for the mobile terminals
Controlling media gateways (MGW) to implement call connection
Offering accessing of base station subsystem (BSS)
Interworking with public switched telephone network (PSTN)
Interworking with integrated services digital network (ISDN)
Interworking with fixed network and other public land mobile networks (PLMNs)
Having network functions like mobility management, security management, and call
control
1.4.2 VLR
The GTSOFTX3000 has the built-in VLR function. The VLR contains all the data needed for
the MSC Server to establish and release calls, and for the roaming and supplementary service
management.
It monitors the location update and stores the following information of the mobile subscribers
roaming to this MSC:
International mobile subscriber identity (IMSI)
Mobile station international ISDN number (MSISDN)
Mobile station roaming number (MSRN)
Temporary mobile station identity (TMSI)
Registered location area (LA)
Serving GPRS support node (SGSN) ID
Group ID registered for subscriber
Priority information
1.4.3 SSP
The GTSOFTX3000 enables the GSM service switching function (gsmSSF). It can serve as
an SSP in the WIN and cooperate with the corresponding GSM service control function
(gsmSCF) to provide wireless intelligent services and some GSM-R services. This function
complies with the definition in the related protocols of 3GPP CAMEL Phase 3, and is
compatible with the CAMEL protocol of earlier versions.
Issue 1.6 (2012-05-03)

1 Overview
1.4.4 Built-in GCR

The group call register (GCR) is built in the GTSOFTX3000. It stores the group call attributes
related to the VGCS and VBS.
The group call attributes include:
Group call reference
Dispatcher number
Group call priority
Service area information
In addition, the GCR provides the data management function, through which the administrator
can add, list, and modify these group call attributes.
Issue 1.6 (2012-05-03)

2 Product Features
Product Features
This chapter describes features of the GTSOFTX3000, including high performance,

high-quality service provisioning, and smooth migration.
2.1 High Efficiency

The high efficiency of the GTSOFTX3000 is described in this section in terms of high
equipment efficiency, high network efficiency, and high operation and maintenance efficiency.
2.1.1 High Equipment Efficiency

Advanced Hardware Platform
The GTSOFTX3000 adopts the Open Standards Telecom Architecture (OSTA) 2.0 hardware
platform. The OSTA 2.0 hardware platform provides a set of specifications regarding boards,
backplanes, and software for the next-generation telecom equipment. It was developed based
on the Advanced Telecom Computing Architecture (ATCA) platform and conforms to the
Network Equipment Building System (NEBS) and European Telecommunications Standards
Institute (ETSI) standards. The OSTA 2.0 hardware platform has the following features:
High transmission rate

The switching structure and the use of high-speed serial data links and provide up to 2.5
Tbit/s bandwidths for data switching.
High processing capability

High-performance chips, high-speed buses, and high-speed Intel processors contribute to
high processing capabilities. When the GTSOFTX3000 is fully configured, it can
provide high processing capability.
High availability
All boards and daughter boards, except for switch interface units (SWIs), are hot
swapping. Redundancy backup is provided for all essential components, such as power
supply, fans, management modules, and boards. The hot swap feature and redundancy
configuration bring the system availability rate up to 99.999%.
High scalability
Only interface boards need to be added when you cascade subracks or increase the
number of interfaces on ATCA boards.
Issue 1.6 (2012-05-03)


2 Product Features
Easy to manage
Standard management buses are used to manage all system components.
Large Capacity
In typical configuration (one cabinet with one subrack), the GTSOFTX3000 supports a
maximum of 300,000 subscribers.
2.1.2 High Network Efficiency

Huawei provides the MSC Pool solution to achieve network load balancing, increasing system
resource utilization.
MSC Pool
An MSC Pool consists of multiple MSC servers. Each radio access network (RAN) node in
the MSC Pool area is connected to multiple pooled MSC servers.
For details about the functions that the GTSOFTX3000 implements in an MSC Pool network,
see "MSC Pool Networking" in section 6.1 "Networking."
2.1.3 High Operation and Maintenance Efficiency

Huawei provides the End-to-End Subscriber Trace feature to deploy networks cost-effectively
and make networks easy to maintain.
End-to-end User Tracing

The End-to-End Subscriber Trace feature enables you to create end-to-end subscriber trace
tasks on the M2000 or HLR. It also enables you to view messages flows between various
network elements (NEs) in the same window. This is implemented with the M2000 by
correlating trace files uploaded by NEs such as the MSC, media gateway (MGW), and session
border controller (SBC). The End-to-End Subscriber Trace feature is used in basic services,
handovers, and the MSC Pool.
2.2 High-Quality Service Provisioning

The GTSOFTX3000 delivers high-quality service experience in terms of high reliability,
excellent voice quality, and a variety of value-added services.
2.2.1 High Reliability

The MSC server is the core element in a network. A serious accident to the MSC server such
as a misoperation, equipment fault, or natural disaster would lead to widespread service
interruptions. To prevent this situation, the GTSOFTX3000 provides high reliability at the
system level and network level.
Issue 1.6 (2012-05-03)

2 Product Features
System Reliability
Table 2-1 describes the solutions that the GTSOFTX3000 uses to achieve system reliability.
Table 2-1 Solutions for achieving system reliability
Item
Solution
Hardware
Active/standby backup, load sharing, and redundancy setup are used

for boards.
Fault detection and isolation techniques are optimized to make the

system easy to maintain.
Dual connections are provided for important components, and dual

planes and mesh connections are used for the entire communication
plane. This ensures that the system is not affected when a single node
is faulty.
Software
The layered and modular structure is adopted, which provides functions

such as protection, error tolerance, and fault monitoring.
Billing system
The iGateWay Bill (iGWB), developed by Huawei, is used as the billing

gateway. The iGWB provides mass storage and uses the 1+1 hot backup
mode to implement dual backup of billing data.
MSC Pool
Real-time automatic data backup provides disaster tolerance for pooled MSC servers.
For details about the functions that the GTSOFTX3000 implements in an MSC Pool network,
see "MSC Pool Networking" in section 6.1 "Networking."
Dual Homing
Dual homing is used to establish geographic redundancy between MSC servers. This means
that an MSC server is deployed to work as the backup of the existing MSC server. In normal
cases, the active MSC server processes all signaling and services. When the active MSC
server becomes faulty, the standby MSC server takes over services from the active MSC
server, ensuring the normal service operation of a mobile network.
For details about the functions that the GTSOFTX3000 implements in a dual-homing network,
see "Dual Homing" in section 6.1 "Networking."
2.2.2 Excellent Voice Quality

The GTSOFTX3000 provides features such as the voice quality enhancement (VQE), TrFO,
and high definition (HD) voice features to improve voice quality.
VQE
The VQE feature improves voice quality by providing the following functions:
Issue 1.6 (2012-05-03)
Electrical echo cancelation (EEC): The EEC function eliminates electrical echoes caused
by 2-wire/4-wire conversion on the PSTN side.

10
2 Product Features
Acoustic echo cancelation (AEC): The AEC function eliminates echoes generated when
a voice is being transmitted from a loudspeaker to a receiver. This function is used in a
mobile environment to provide high call quality. Acoustic echo is generated at the far
end but is heard by the near end. Therefore, the near end benefits from this function.
Noise reduction (NR): The NR function is used to detect and eliminate noise from input
voice signals at the local end, remote end, or both ends.
Noise compensation (NC): The NC function automatically adjusts output voice volume
at the local end, remote end, or both ends based on the level of input noise at either end.
This ensures that subscribers can hear clear voices even in noisy environments.
Automatic gain control (AGC): The AGC function is used to compensate for changes in
voice volume. This ensures that the volume of a call is retained at the same level, and
that subscribers hear steady, clear voices.
TrFO
The TrFO feature uses outband negotiation. Because transcoders (TCs) are not used during
voice transmission when the TrFO feature is enabled, expensive TC resources and associated
power consumption are not required. Network bandwidth can also be reduced because voice
can be transmitted across the CN at a rate of compressed codecs, for example, AMR 12.2
kbit/s.
HD Voice
HD voice provides higher quality voice transmission using adaptive multirate wideband
(AMR-WB). AMR-WB extends the frequency range of traditional speech codecs (300 Hz to
3400 Hz) with a sampling rate of 8 kHz to wideband audio ranges (50 Hz to 7000 Hz) with a
sampling rate of 16 kHz. The low-frequency enhancement in AMR-WB from 50 Hz to 300
Hz contributes to clearer, more lifelike voice communications. The high-frequency extension
from 3400 Hz to 7000 Hz provides better fricative differentiation and therefore higher
intelligibility. Although the sampling rate for AMR-WB is higher, AMR-WB offers better
quality compared to AMR-NB in similar radio channel conditions because AMR-WB has a
better compression algorithm.
HD voice provides the following benefits:
Subscribers are willing to use mobile voice services for more communication because of
the high-quality speech provided by HD voice. This increases carriers' revenue and
profits.
Carriers' brand equity increases, and more customers subscribe to the carriers' networks
because HD voice improves the voice service quality. Increased customer satisfaction
means that carriers can spend less money in handling customers' complaints.
Carriers can diversify their marketing approaches by providing package services bound
with HD voice terminals.
When HD voice is used for conference and video services, improved user experience
enables carriers to attract enterprise customers. Carriers can then compete with the voice
over IP (VoIP) service provided by Internet operators.
The GTSOFTX3000 supports FR_AMR-WB and UMTS_AMR-WB. To achieve optimal

voice quality, it is recommended that the tandem free operation (TFO)/TrFO technology be
used and that the HD voice function be deployed after IP transformation is complete on live
networks.
Issue 1.6 (2012-05-03)

11
2 Product Features
2.2.3 Value-added Services

The GTSOFTX3000 provides a variety of value-added services to meet operators'
requirements. Only a few services are described in this section. For details about all the
services and functions supported by the GTSOFTX3000, see GTSOFTX3000 V200R001C00
Feature Description.
Black & White Lists

The Black & White Lists feature supports call restriction based on calling numbers and called
numbers. This feature enables operators to allow or restrict intra-MSC calls and inter-network
calls, and frees subscribers from unwanted calls.
User Differentiated Services

The User Differentiated Services feature allows operators to provide different classes of
services to subscribers of different priorities.
Based on the predefined subscriber priorities, operators can apply different service strategies
for resource allocation, resource reservation, resource preemption, and quality of service
(QoS).
2.3 Smooth Migration

The GTSOFTX3000 is designed to support the application of the 3GPP R4 CS CN and is
compatible with the GSM and 3GPP R99 networks. It also enables R4 networks to migrate
smoothly to the 3GPP R5, 3GPP R6, 3GPP R8, and 3GPP R9 networks. Figure 2-1 shows the
network migration strategy.
Figure 2-1 Migration strategy of the Huawei mobile CN
Issue 1.6 (2012-05-03)

12
2 Product Features
The GTSOFTX3000 uses the same hardware configuration as the network elements (NEs) in
the IP multimedia subsystem (IMS) domain and therefore can serve as the media gateway
control function (MGCF) and IP multimedia service switching function (IM-SSF) in an IMS
network. This enables smooth network migration.
2.4 System Features

The GTSOFTX3000 adopts the mature open standards telecom architecture (OSTA) platform.
It has the following features:
High maintainability
High security and reliability
Advanced architecture
Outstanding networking capability
Abundant service features
Outstanding product continuity
2.4.1 Softswitch
Based on the Softswitch, the GSM-R MSC can get access to the packet switched network
directly, making it easy to construct the GSM-R network.
The GSM-R MSC supports distributed networking and IP bearer, which greatly improves
network transmission efficiency, simplifies interconnection topology and network
management, and lowers the OPEX. In addition, the GSM-R MSC can smoothly evolve along
with the network, protecting carriers' investments.
2.4.2 Multi-SP Technology and 2 Mbit/s Signaling Technology

The GTSOFTX3000 supports multi-signaling-point (Multi-SP) technology and time division
multiplex (TDM) 2 Mbit/s signaling technology.
Their functions are as follows:
The multi-SP technology can break the limitation of the maximum number of links and
trunks set by the SS7 between two SPs.
The 2 Mbit/s signaling solution provides high-speed signaling links to support heavy
signaling traffic between SPs, simplifying networking and reducing cost. If the multi-SP
technology is not supported, the 2 Mbit/s signaling solution can still meet the
requirements on signaling traffic.
With the two technologies, the signaling flow between the GTSOFTX3000 and other SPs is
increased to meet the requirements of the large-capacity system.
2.4.3 Middle-Ware Technology

Middle-ware technology means that the upper layer software does not depend on the bottom
layer operating system, therefore no relationships between the upper layer service software
and the lower layer platform exists. This technology allows migrating functions between
different platforms. Meanwhile, the little change in the service software enables the
manufacturer to provide stable commercial versions quickly.
Issue 1.6 (2012-05-03)

13
2 Product Features
2.4.4 Advanced GSM-R Network Platform

The GMS-R GTSOFTX3000 supports GSM-R trunking services and gives prominence to the
function of the directing dispatch application node, such as the FFN and the GCR. Moreover,
the GTSOFTX3000 adds the automatic call distributor to facilitate the dispatch station to
access the network, providing a more flexible access way to support the dispatch management
application.
The intelligent service platform facilitates the dispatch service directing. Supporting the data
service, the GTSOFTX3000 makes the data application achievable, though these data
applications are difficult to realize by the analog trunking system and even the digital trunking
system.
The GTSOFTX3000 provides rich GSM-R services, including:
VGCS
VBS
Enhanced multi-level precedence and preemption (eMLPP)
Call area restriction
Location dependent addressing
Confirmation of high priority calls
Functional number
Call matrix
Issue 1.6 (2012-05-03)

14
3 Services and Functions
Services and Functions
This chapter describes basic services and functions provided by the GTSOFTX3000.
Only a few important services and functions are described in this chapter. For details about all
the services and functions supported by the GTSOFTX3000, see GTSOFTX3000
V200R001C00 Feature Description.
3.1 Basic Services

Basic services provided by the GTSOFTX3000 include teleservices, supplementary services,
and intelligent network (IN) services.
3.1.1 Teleservices
The GTSOFTX3000 supports basic teleservices such as voice services, short message service
(SMS), GSM fax services, GSM bearer services, and UMTS bearer services. It provides
bidirectional communications for the local office's PLMN subscribers, and other connected
subscribers, such as other offices' PLMN subscribers and PSTN subscribers. Table 3-1 lists
the teleservices supported by the GTSOFTX3000.
Table 3-1 Teleservices supported by the GTSOFTX3000
Service
Type
Description
Voice
services
The GTSOFTX3000 supports telephony (TS 11), emergency calls (TS 12),
VGS (TS91), VBS (TS92), and emergency calls for special services.
SMS
The GTSOFTX3000 supports point-to-point SMS and point-to-multipoint

SMS. The point-to-point SMS includes short message mobile originated
(SMMO) and short message mobile terminated (SMMT).
GSM fax
services
The GTSOFTX3000 supports the GSM G3 transparent fax that complies

with 3GPP TS 03.45 and ITU-T T.30. The transparent fax can be
transmitted at a rate of 9.6 kbit/s, 4.8 kbit/s, or 2.4 kbit/s. Service types
consist of TS61 and TS62.
Issue 1.6 (2012-05-03)

15
Service
Type
Description
GSM bearer
services
The GTSOFTX3000 supports the BS20 asynchronous transparent and

asynchronous non-transparent bearer services. The rate for PSTN
subscribers can be 2.4 kbit/s, 4.8 kbit/s, or 9.6 kbit/s.
UMTS bearer
services
The GTSOFTX3000 supports the BS20 asynchronous non-transparent

bearer services and BS30 synchronous transparent bearer services.
3.1.2 Supplementary Services

Supplementary services accompany or convert basic teleservices. A supplementary service
must be offered together with one or more basic teleservices.
The GTSOFTX3000 supports various 3GPP-compliant supplementary services, including
number identification, call forwarding (CF), call completion, MultiParty (MPTY), call barring,
closed user group (CUG), and unstructured supplementary service data (USSD) services.
Number Identification
The GTSOFTX3000 supports the following number identification services:
Calling Line Identification Presentation (CLIP)
Calling Line Identification Restriction (CLIR)
Connected Line Identification Presentation (COLP)
Connected Line Identification Restriction (COLR)
Call Forwarding
The GTSOFTX3000 supports the following call forwarding services:
Call Forwarding Unconditional (CFU)
Call Forwarding on Mobile Subscriber Busy (CFB)
Call Forwarding on Mobile Subscriber Not Reply (CFNRy)
Call Forwarding on Mobile Subscriber Not Reachable (CFNRc)
Call Completion
The GTSOFTX3000 supports two types of call completion services: call waiting (CW) and
call hold (HOLD).
MPTY
The multi-party service refers to the multi-party supplementary service (MPTY).
The MPTY service supports a maximum of six subscribers in a call, conference, or chat. The
control party of the MPTY service can add, disconnect or isolate remote subscribers to or
from an MPTY call. An isolated participant can only talk with the control party.
The MPTY service enriches service versatility. It provides a simple solution for conference
call of commercial purpose.
Issue 1.6 (2012-05-03)

16
Community of Interest Service

The community of interest service refers to the closed user group (CUG) service. The CUG
service enhances service versatility and attracts corporate users.
In the CUG service, one or multiple subscribers sharing a set of same features form a group,
in which all group members share the same call features and tariff discount. A CUG
subscriber can be provided with all common telecom services except for emergency calls and
short message service (SMS). The CUG service can be used for groups of several members or
corporations of thousands of employees.
USSD
Unstructured supplementary service data (USSD) services provides information for
subscribers in the interactive mode.
A subscriber can enter a supplementary service operation command in conformity with the
USSD format through the MS, to originate a specific service request to the network. Or, the
network sends USSD command to the MS to implement a specific service. The USSD service
can be provided by the GSM-R network or other networks. In the latter case, the GSM-R
network transmits signaling transparently.
The USSD center can provide the following services:
Air flight information
Finance and stock information
Foreign exchange information
Sports game information
Cinema ticket booking information
Bank accounting information
In addition to the public information, the USSD can be used by mobile subscribers to query
and manage their own service data, for example:
When the MSC is connected to the intelligent network (IN), subscribers can manage the
IN services through the USSD.
Subscribers can query data in the VLR and HLR, for example, MSISDN.
Call Barring
As defined in the 3GPP specifications, call barring services are classified into incoming call
barring services and outgoing call barring services.
The GTSOFTX3000 supports all call barring services.
ODB
The Operator determined barring (ODB) services are controlled by network operators by
means of managing the HLR data.
The ODB services can be applied to all subscriber terminal services and bearer services
except emergency calls. They have a higher priority than supplementary services. When there
is a conflict between the ODB services and supplementary services, the supplementary
services will be restricted.
Issue 1.6 (2012-05-03)

17
The ODB services are similar to call restriction services and are different from call restriction
services in the following aspects:
The status of the ODB services is controlled by network operators, while the status of
call restriction services is controlled by either subscribers or operators.
The ODB services are activated once they are provided, but call restriction services must
be activated by the subscriber after being provided.
The GTSOFTX3000 supports the following the ODB services:

Barring outgoing calls.
Barring outgoing international calls.
Barring outgoing international calls except those directed to the home PLMN country.
Barring outgoing calls when roaming outside the home PLMN country.
Barring incoming calls.
Barring incoming calls when roaming outside the home PLMN country.
Barring roaming outside the home PLMN country.
Barring outgoing high-premium-rate calls (for information).
Barring outgoing high-premium-rate calls (for entertainment).
Barring supplementary services management.
CCBS
The GTSOFTX3000 supports the Completion of Calls to Busy Subscriber (CCBS) service.
When subscriber A that subscribes to the CCBS service calls subscriber B, the
GTSOFTX3000 allows subscriber A to complete the call automatically after subscriber B
becomes idle, without dialing the number of subscriber B again.
3.1.3 IN Services
By using the intelligent network (IN), the GTSOFTX3000 provides some GSM-R services
such as functional number addressing, call matrix, and location-dependent routing.
3.1.4 Value-added Services

The GTSOFTX3000 provides the following value-added services:
Blacklists and whitelists
Location service (LCS)
Differentiated services
In addition, the GTSOFTX3000 provides a third-party interface so that carriers can customize
value-added services based on their requirements.
3.2 Basic Functions

The GTSOFTX3000 provides the following basic functions:
Mobility management
Security management
Issue 1.6 (2012-05-03)

18

Call control
SSP
Handovers
Charging
CAMEL services
3.2.1 Mobility Management

The mobility management function, also known as location management (LM), enables the
network to trace the current location of the MS and store its location information in the HLR,
MSC, VLR, and MS (SIM card). The LM flow ensures that the location information stored in
these entities is the same. LM enables mobile subscribers to roam between networks.
Location Update
In a mobile communications network, an MS or UE must notify the network of its present
location when it roams so that the network can keep in contact with the MS or UE. To do so,
the MS or UE needs to send a location update request to the MSC to register its present
location on the network. At the same time, the network may need to update the information
about the VLR currently being visited by the MS or UE on the HLR. The HLR sends the
subscription data for the MS or UE to the VLR. Location update is a primary procedure in
location management and is initiated by the MS or UE.
Generic location update

When an MS is roaming or being powered on, if the location area identifier received by
the MS from the MSC is inconsistent with the identifier stored in the MS, the MS sends a
location update request to the network to update the location area identifier. The
GTSOFTX3000 supports the following location update flows:
Location update within the same MSC/VLR area
Location update across different MSC/VLR areas and originated by using the IMSI
Location update across different MSC/VLR areas and originated by using the TMSI
Periodic location update

The MS originates location updates periodically, regardless of whether it moves to a new
location area. If the MS does not originate the periodic location update within a specified
period, the VLR sets the status of the IMSI to detach. In this way, the circuit and wireless
resources can be reserved for future use.
IMSI attach/detach
If the MS can access the network, the VLR automatically sets the status of the
subscriber's IMSI to attach. The subscriber's IMSI is then activated and valid.
When the MS remains switched off for a long time, the VLR sets the status of the
subscriber's IMSI to detach. The system does not send paging messages to a subscriber
whose IMSI is set to detach when the subscriber is called. In this way, the wireless
channel resources can be reserved for future use. The GTSOFTX3000 supports the
following IMSI detach types:
Issue 1.6 (2012-05-03)
Implicit IMSI detach: When the implicit IMSI detach timer expires, the VLR sets the
status of the IMSI to detach.
Explicit IMSI detach: The MS originates the IMSI detach flow when it is being
powered off, and the VLR sets the status of the IMSI to detach.

19

Combined location update

When the network is configured with the Gs interface and the MS supports both CS and
PS services, the joint location update flow is originated in the following cases:
The MS roams to a new MSC area.
The MS for which GPRS attach is already performed originates IMSI attach.
GPRS attach and IMSI attach are originated simultaneously.
An association is established between the SGSN and the VLR, and they store each
other's ISDN number.
Handover
Sometimes, an MS is handed over from one radio channel to another due to a signal problem
in the network or a location change of the MS during a call. This process is called a handover.
From the MSC side, the handovers performed by the GTSOFTX3000 can be divided into the
following types:
Intra-MSC handover
Intra-MSC handovers are handovers from the current BSC to another BSC of the same
MSC. A single MSC controls the handover process. Intra-MSC handovers can be divided
into two types: intra-MSCa handover and intra-MSCb handover. The MSC where a call
is initially set up is called the controlling MSC (Anchor MSC, or MSCa). Handovers that
occur in the controlling MSC are called intra-MSCa handovers. Handovers that occur in
the non-controlling MSC are called intra-MSCb handovers.
Inter-MSC handover
Inter-MSC handovers are handovers that occur when a mobile subscriber moves from the
BSC coverage area of one MSC to the BSC coverage area of another MSC during a call.
In an inter-MSC basic handover, MSCa controls the handover process and performs the
following operations:
Sends a handover request through the BSC
Selects the destination MSC
Sends a handover resources request to MSCb by using MAP signaling
Establishes the inter-MSC bearer
Controls the call after the handover
MSCb establishes the wireless resources required for the handover and coordinates with
MSCa to perform call control after the handover.
Subsequent Handover
Subsequent handovers are inter-MSC handovers originated by MSCb after an inter-MSC
handover. Subsequent handovers can be divided into two types: subsequent handover
back to MSCa and subsequent handover to a third-party (MSCb').
The procedure for subsequent handover back to MSCa is as follows:
Issue 1.6 (2012-05-03)
MSCb responds to the handover request received from the BSC.
MSCb sends the "subsequent handover back to MSCa" request to MSCa by using
MAP signaling.
MSCa instructs the local BSC to allocate resources.
MSCa notifies MSCb to send a handover command.
MSCb releases the bearer between MSCa and MSCb.

20
The procedure for subsequent handover to a third party (MSCb') is as follows:
MSCb sends the "subsequent handover to the third party (MSCb')" request to MSCa
by using MAP signaling.
MSCa informs MSCb' to prepare for the handover.
MSCb' instructs the local BSC to allocate resources.
MSCb' notifies MSCb to send a handover command.
Roaming Restriction
When a mobile subscriber originates or terminates a call, the serving MSCe or HLR checks
the roaming authority of the subscriber.
Roaming restriction refers to the management on the area in which a subscriber roams. When
a subscriber enters the service area of a new MSC, the new MSC sends the MSCID of the
subscriber to the HLR in a location update message. The HLR then determines whether the
subscriber is allowed to roam in the current MSC area.
When a subscriber fails to originate a call due to roaming restriction, the system plays an
announcement to the subscriber. Roaming restriction can be divided into two types: roaming
restriction on calling subscribers and roaming restriction on called subscribers.
3.2.2 Security Management

In the network, the security management aims to:
Prevent unauthorized access
Prevent any false network from cheating subscribers
Ensure reliable transmission of subscriber and signaling data
The network provides a series of security measures, including:

Authentication
Encryption
Integrity protection
TMSI reallocation
Equipment identification
On the MSC Server, the GTSOFTX3000 supports four security functions:

Authentication
Encryption
Integrity protection
TMSI reallocation
Issue 1.6 (2012-05-03)

21
3.2.3 Call Control

Call Connection
The GTSOFTX3000 can process the incoming and outgoing calls of both common services
and IN services, including local calls, outgoing calls, incoming calls, and incoming transit
calls. The GTSOFTX3000 supports the following functions:
Querying the Mobile Station Roaming Number (MSRN) of a called subscriber based on
the MSISDN, and then routing the call to the VMSC based on this MSRN
Locating a called subscriber based on the IMSI or TMSI of the subscriber as well as the
location and service area where the subscriber is roaming
Pre-paging
Emergency calls and special service calls defined by the carrier
Alarm function for emergency or long-duration calls
Playing announcements based on DN sets and failure causes
Delaying sending the ringing tone to a called subscriber
Number Analysis
The GTSOFTX3000 provides a powerful number analysis function, which supports a variety
of applications. The GTSOFTX3000 supports the following functions:
Receiving and storing numbers that contain a maximum number of 32 digits
Analyzing numbers that contain a maximum number of 32 digits
65,000 called number prefixes
80,000 GT codes
Service check
Call authority check
Preprocessing of incoming and outgoing numbers
Calling number identification
Call barring based on the black and white lists
Restrictions on the minimum and maximum lengths of numbers
Changing the calling, called, and roaming numbers based on the location of the numbers
or the specified characters
Changing the calling or called number based on the association between them
Changing the calling subscriber type, calling address attribute indicator and called
address attribute indicator in the sent inter-MSC IAM or IAI message
Route Selection
The GTSOFTX3000 can select a route to connect calls based on the number analysis result
and the information about the calling subscriber. The GTSOFTX3000 supports the following
functions:
Intra-office route selection (to a BSC connected to the MSC) and inter-office route
selection (to another MSC)
Sequential or percentage-based subroute selection
Issue 1.6 (2012-05-03)

22
Time-based dynamic route selection
Preventing alternate routes between offices of the same level
Multi-gateway static routing
Inter-gateway route selection based on the random, percentage or alternate selection

policies
Optimal routing function
3.2.4 SSP
The GTSOFTX3000 can function as the mobile Service Switching Point (SSP) to provide
functions such as call control function (CCF), service switching function (SSF), and
specialized resource function (SRF).
CCF
CCF includes the basic IN call processing function and the supplementary functions
supporting IN calls. The basic call processing function refers to the signaling and call control
during the setup and monitoring of the IN call, which is the same as that of the non-IN call.
The supplementary functions include IN trigger detection (including trigger detection point
and trigger criteria), and processing of call-related events and control requests from SSF.
SSF
SSF, in coordination with CCF, offers a group of functions needed by the CCF-SCF
communication.
The following list the major functions of SSF:
Expanding the logic of CCF, including the identification of service control trigger and
the communication with SCF
Managing the signaling between CCF and SCF
Modifying call/connection processing function (in CCF) as required, and processing the
request of IN services under the control of SCF
SRF
SRF provides specialized resources required for implementing IN services, including:
DTMF receiver
Voice generator
Voice announcement
Message transceiver
SRF also manages the following resources:

Capability of searching resources
State of managing resources (such as busy/idle/blocked)
Action of controlling resources
In addition, it provides the functions required for information exchange between the SRF and
other functional entities. The GTSOFTX3000 controls the SRF.
Issue 1.6 (2012-05-03)

23
3.2.5 Handover
Sometimes, an MS is handed over from one radio channel to another due to a signal problem
in the network or a location change of the MS during a call. This process is called a handover.
From the MSC side, the handovers performed by the GTSOFTX3000 can be divided into the
following types:
Intra-MSC handover
Intra-MSC handovers are handovers from the current BSC to another BSC of the same MSC.
A single MSC controls the handover process. Intra-MSC handovers can be divided into two
types: intra-MSCa handover and intra-MSCb handover. The MSC where a call is initially set
up is called the controlling MSC (Anchor MSC, or MSCa). Handovers that occur in the
controlling MSC are called intra-MSCa handovers. Handovers that occur in the
non-controlling MSC are called intra-MSCb handovers.
Inter-MSC handover
Inter-MSC handovers are handovers that occur when a mobile subscriber moves from the
BSC coverage area of one MSC to the BSC coverage area of another MSC during a call. In an
inter-MSC basic handover, MSCa controls the handover process and performs the following
operations:
Sends a handover request through the BSC
Selects the destination MSC
Sends a handover resources request to MSCb by using MAP signaling
Establishes the inter-MSC bearer
Controls the call after the handover
MSCb establishes the wireless resources required for the handover and coordinates with
MSCa to perform call control after the handover.
Subsequent Handover
Subsequent handovers are inter-MSC handovers originated by MSCb after an inter-MSC
handover. Subsequent handovers can be divided into two types: subsequent handover back to
MSCa and subsequent handover to a third-party (MSCb').
The procedure for subsequent handover back to MSCa is as follows:
MSCb sends the "subsequent handover back to MSCa" request to MSCa by using MAP
signaling.
MSCa instructs the local BSC to allocate resources.
MSCa notifies MSCb to send a handover command.
The procedure for subsequent handover to a third party (MSCb') is as follows:

MSCb sends the "subsequent handover to the third party (MSCb')" request to MSCa by
using MAP signaling.
Issue 1.6 (2012-05-03)

24

MSCa informs MSCb' to prepare for the handover.
MSCb' instructs the local BSC to allocate resources.
MSCb' notifies MSCb to send a handover command.
3.2.6 Charging
CDR Types
The GTSOFTX3000 supports many types of original call detail records (CDRs) to meet
various requirements of carriers. Table 3-2 describes the scenarios in which various original
CDRs are generated.
Table 3-2 Scenarios in which various original CDRs are generated
Type of
Original CDR
Generation Scenario
Mobile originated
call (MOC)
If a non-IN mobile subscriber originates a call, and the call is

answered, the MSC generates an MOC CDR for the calling subscriber,
when the call ends or the timer of long-duration call CDRs expires.
Mobile
terminated call
(MTC)
If a non-IN mobile subscriber answers a call, the MSC generates an

MTC CDR for the called subscriber, when the call ends or the timer of
long-duration call CDRs expires.
Call forwarding
(CFW)
During a call connection, assume that:

B is a non-IN mobile subscriber.
B is registered for call forwarding service.
C is the forwarded-to destination code.
A calls B, and the call is forwarded to C by the MSC serving B. C
answers the call. When the call ends or the timer of long-duration call
CDRs expires, the MSC generates a CFW CDR for B. If A, B, and C
are mobile subscribers served by the same MSC/VLR, the MSC
generates an MOC CDR for A, a CFW CDR for B, and an MTC CDR
for C, when the call ends or the timer of long-duration call CDRs
expires.
Mobile originated
SMS (MO_SMS)
When a mobile subscriber sends an SM to the SMC successfully, the

MSC generates an MO_SMS CDR. Short message communication
uses the signaling channel to transfer characters. Compared with a
common call CDR, a short message CDR consists of SM content, SM
operation result, number of SM bytes, and SMC address.
Mobile
terminated SMS
(MT_SMS)
When a mobile subscriber receives an SM from the SMC successfully,

the MSC generates an MT_SMS CDR.
Issue 1.6 (2012-05-03)

25
Type of
Original CDR
Generation Scenario
Transit call
(TRANSIT)
When an incoming trunk originates a call, the MSC (TMSC) connects

the call to an outgoing trunk after analyzing the call. The call is neither
originated nor terminated in the local MSC. If the type of incoming
and outgoing office directions is "Local network", the MSC generates
a TRANSIT CDR, when the call ends or the timer of long-duration
call CDRs expires.
Inter-network
transit call
(OT_TRANSIT)
When an incoming trunk originates a call, the MSC (TMSC) connects

and outgoing office directions is "Other network" (Other PLMN or
PSTN), the MSC generates an OT_TRANSIT CDR, when the call
ends or the timer of long-duration call CDRs expires.
Gateway
outgoing call
(GWO)
When an incoming trunk originates a call, the MSC (GMSC) connects

office direction is "Local network", and the type of outgoing office
direction is "Other network" (Other PLMN or PSTN), the MSC
generates a GWO CDR, when the call ends or the timer of
long-duration call CDRs expires.
Gateway
incoming call
(GWI)
When an incoming trunk originates a call, the MSC (GMSC) connects

office direction is "Other network" (Other PLMN or PSTN), and the
type of outgoing office direction is "Local network", the MSC
generates a GWI CDR when the call ends or the timer of long-duration
call CDRs expires.
Roaming
(ROAM)
Assume that a non-IN roaming mobile subscriber receives a call. If the

call must be routed and connected to the GMSC of the subscriber's
home PLMN, the GMSC generates a CDR called ROAM CDR for the
called subscriber, when the call ends or the timer of long-duration call
CDRs expires.
Call attempt
(CALL_ATTEM
PT)
If the connection of a transit call, inter-network transit call, gateway

outgoing call, or gateway incoming call fails, the MSC generates a
CALL_ATTEMPT CDR. The CALL_ATTEMPT CDR records the
network resources allocated to the unsuccessful call. The
CALL_ATTEMPT CDR is essentially a TRANSIT CDR,
OT_TRANSIT CDR, GWO CDR or GWI CDR. The release cause
value in the CALL_ATTEMPT CDR is unsuccessfulCallAttempt.
The billing center can sort out CALL_ATTEMPT CDRs based on this
value.
Issue 1.6 (2012-05-03)

26
Type of
Original CDR
Generation Scenario
Mobile originated
- instead (MOI)
Assume that:
The MSC in office A cannot function as the SSP.

The MSC in office B can function as the SSP.
Office A routes the IN calls in office A to office B by using the
Overlay mode.
The MSC in office B triggers the IN service.
When a non-IN subscriber in office A or an incoming trunk calls IN
subscriber X (non-forwarding call), office A routes the call to office B.
Therefore, office A fails to obtain the exact location of IN mobile
subscriber X. After triggering the IN service, office B obtains the exact
location of IN mobile subscriber X. If subscriber X answers the call,
when the call ends or the timer of long-duration call CDRs expires, the
MSC in office B generates an MOI CDR. This CDR is provided for
the billing center to charge the calling subscriber accurately. The MOI
CDR is generated only after the incoming trunk triggers the called IN
service in overlay mode. When the mobile IN network adopts the
target networking mode, the MSC does not generate the MOI CDR.
IN
mobile-originated
call (AI_MOC)
If an IN subscriber originates a call, and the call is answered, the MSC

(SSP) that triggers the IN service generates an AI_MOC CDR for the
calling subscriber, when the call ends or the timer of long-duration call
CDRs expires. The AI_MOC CDR is essentially an MOC CDR. The
subscriber type in the AI_MOC CDR is CAMEL user. Based on this
value, the billing center can sort out AI_MOC CDRs.
IN
mobile-terminate
d call (AI_MTC)
If an IN subscriber answers a call, the MSC (SSP) that triggers the IN

service generates an AI_MTC CDR for the called subscriber, when the
call ends or the timer of long-duration call CDRs expires. The
AI_MTC CDR is essentially an MTC CDR. The subscriber type in the
AI_MTC CDR is CAMEL user. Based on this value, the billing center
can sort out AI_MTC CDRs.
IN call
forwarding
(AI_CFW)
Assume that:
B is an IN mobile subscriber.
B is registered for the call forwarding service.
C is the forwarded-to destination code.
A calls B, and the call is forwarded to C. C answers the call. When the
call ends or the timer of long-duration call CDRs expires, the MSC
that triggers the IN service generates an AI_CFW CDR for B. The
AI_CFW CDR is essentially a CFW CDR. The subscriber type in the
AI_CFW CDR is CAMEL user. Based on this value, the billing center
can sort out AI_CFW CDRs.
Location service
(LCS)
Issue 1.6 (2012-05-03)
While processing any type of location request, after the MSC receives
the location report from the BSC, the MSC generates an LCS CDR.
The LCS CDR records the location method, location time, and location
results.

27
Type of
Original CDR
Generation Scenario
Supplementary
service actions
(SS_ACT)
When a non-IN mobile subscriber executes non-call related operations

such as registration, cancelation, activation and deactivation of the SS,
the MSC generates an SS_ACT CDR for the operation.
Hot billing
(HOTBILL)
The MSC first checks whether a mobile subscriber has registered for
the hot billing service. If so, the MSC generates a HOTBILL CDR
when the subscriber uses a voice or data service of any type, such as
an MOC, MTC, MO_SMS, and MT_SMS. The MSC sends the CDRs
related to the call to the billing center immediately. The HOTBILL
CDR is essentially an MOC CDR, MTC CDR, MO_SMS CDR, or
MT_SMS CDR. The hot billing flag in the HOTBILL CDR is true.
Based on the hot billing flag, the billing center can sort out HOTBILL
CDRs.
CHECK IMEI
If the MSC implements the Check IMEI flow in the process of location
update and service access, the MSC generates a CHECK_IMEI CDR.
HLR QUERY
In a call connection, assume that:

The called subscriber is a non-IN mobile subscriber.
The MSC requests route information from the HLR by using MAP
signaling.
The HLR returns the MSRN to the MSC by using MAP signaling.
The MSC generates a CDR called HLR query record or HLR_QUERY
CDR. If the called subscriber is an IN mobile subscriber, the MSC
queries the HLR twice. By default, the MSC generates an
HLR_QUERY CDR when querying the HLR for the second time. If
you select the value Generate HLR query record after getting
T-CSI of the parameter Ticket control flag when running MOD
GBILLCTRL, the MSC generates an HLR_QUERY CDR when
querying the HLR for the first time. That is, the MSC generates two
HLR_QUERY CDRs.
TCANEL
During a call connection, if a mobile subscriber who has registered for

CAMEL service (with the T-CSI) answers a call, the GMSC (SSP) that
triggers the IN service generates a TCAMEL CDR, when the call ends
or the timer of long-duration call CDRs expires.
Common
equipment usage
(COMMONEQU
IP)
During a call connection or a call, if the MSC in office A uses public

resources (for example, conference resources) in office A or in the
MSC of office B, the MSC in office A generates a COMMONEQUIP
CDR.
EVENT
When events such as call-related handover, call hold, call waiting,

multi-party call establishment, and multi-party call split occur, the
MSC generates an EVENT CDR. The EVENT CDR exists in the form
of an original CDR. Although the iGWB merges EVENT CDRs into
MOC and MTC CDRs, the final CDRs do not contain EVENT CDRs.
Failure
When a mobile subscriber fails to activate the location service, SS, or

USSD service, the MSC generates a CDR called failure CDR.
Issue 1.6 (2012-05-03)

28
Type of
Original CDR
Generation Scenario
Calling subscriber
dedicated
connection
This CDR records the connection information from when a subscriber

originates a group call to when the calling subscriber releases the
uplink connection for the first time.
Resource control
connection
During a voice group call, a dedicated voice channel is established for

each cell within the group call area. After the voice channels are
established, the MSC generates a resource control connection CDR.
Cell dedicated
connection
When a subscriber occupies the uplink connection, the MSC generates

a cell dedicated connection CDR if it allocates a dedicated voice
channel to the subscriber. This CDR records the time when the
subscriber successfully occupies the uplink connection and when the
subscriber releases the uplink connection. If the subscriber occupies
the uplink connection multiple times, the MSC generates multiple cell
dedicated connection CDRs.
Group call
connection
The MSC generates a group call connection CDR when a group call is
generated. If a relay MSC is involved, the relay MSC also generates a
group call connection CDR.
Hot Billing
After the GTSOFTX3000 sends the original CDR generated during a call to the iGWB, the
iGWB allocates a single channel to store the final CDR and sends the final CDR to the billing
center in real time. This function allows the carrier to provide subscribers with services that
require real-time charging.
3.2.7 CAMEL Services

The GTSOFTX3000 provides the GSM Service Switching Function (gsmSSF), including the
Call Control Function (CCF), Service Switching Function (SSF), and Specialized Resource
Function (SRF). It also provides the SSP function in a wireless intelligent network (WIN).
The GTSOFTX3000 supports CAMEL 4, and is compatible with CAMEL 3, 2, and 1.
Overlay Networking Mode

Figure 3-1 shows the overlay networking mode. In this mode, the GTSOFTX3000 serving as
a GMSC or VMSC does not provide the SSP function. It has to route WIN calls to an SSP,
which triggers WIN services.
Issue 1.6 (2012-05-03)

29
Figure 3-1 Overlay networking mode
Target Networking Mode

Figure 3-2 shows the target networking mode. In this mode, the GTSOFTX3000 serving as a
GMSC or VMSC provides the SSP function and triggers WIN services based on the CAMEL
subscription information (CSI) in the HLR.
Figure 3-2 Target networking mode
Issue 1.6 (2012-05-03)

30
When serving as a VMSC, the GTSOFTX3000 can trigger MO, MF, and MT WIN calls.
When serving as a GMSC, the GTSOFTX3000 can trigger MF and MT WIN calls.
3.3 GSM-R Dispatching Service and Function

The GTSOFTX3000 provides rich GSM-R dispatching services and function, mainly
including:
Enhanced multi-level precedence and pre-emption (eMLPP) service
Voice group call service
Voice broadcast service
Acknowledgement of high-priority calls
Functional addressing
Location dependent addressing
Access matrix
MSC pool (1+1 main-standby)
Uplink protection
Echo cancelation
Calling number presentation for the called dispatcher
Delayed TCH assignment
Priority cell
Originator-to-dispatcher information
Call area restriction
Multi-Engine data service
Special functional number
Enhanced location dependent addressing
Train list
Mobile station location service (MSLS)
Issue 1.6 (2012-05-03)

31
4 Product Structure
Product Structure
This chapter describes the hardware and software structures of the GTSOFTX3000.
4.1 Hardware
4.1.1 Logical Structure
The GTSOFTX3000 logically consists of the processor subsystem, switching subsystem,
electromechanical subsystem, and equipment management subsystem.
In the entire system, the switching subsystem serves as the pivot, and the processor subsystem
serves as the core. These subsystems, together with the electromechanical subsystem and
equipment management subsystem, constitute a powerful service processing platform. Figure
4-1 shows the logical structure of the GTSOFTX3000.
Figure 4-1 Logical structure of the GTSOFTX3000
Issue 1.6 (2012-05-03)

32
4 Product Structure
The intelligent platform management bus (IPMB) is the monitoring and device management bus of the
OSTA 2.0 subrack. It connects all the devices in the OSTA 2.0 subrack.
The Base bus is the management and control bus of the OSTA 2.0 subrack. It provides channels for
software loading, alarm reporting, and maintenance message delivery.
The Fabric bus provides data channels for the service plane of the system. It is used to carry
service-related information.
The service processing module (SPM) is comprised of the universal process blade (UPB, a front board)
and universal service interface (USI, a rear board). For details about boards, see Table 4-1"Board types".
Processor Subsystem
The processor subsystem is comprised of blade server boards, which are UPBs. Designed with
high-performance and multi-core processors, the blade server boards provide powerful
processing capabilities. In addition, they can provide various service interfaces through the
mapping rear interface boards. The blade server boards can have different software installed
to function as the service processing boards, as well as the operation management unit (OMU)
and iGWB server boards.
Switching Subsystem
The switching subsystem is comprised of the switching units (SWUs) and switching interface
units (SWIs), which are compliant with PCI Industrial Computers Manufacturers Group
(PICMG) 3.0 and 3.1 specifications. The SWUs are the front boards and the SWIs are the rear
boards of the SWUs. Designed with a dual-star structure, the switching subsystem performs
functions such as system control and data exchange and interconnection at the service plane.
Electromechanical Subsystem
The electromechanical subsystem is comprised of the following modules:
The power distribution module provides redundant backup power supplies and power
filters for the system.
The fan control module monitors and controls the temperature of the equipment.
The backplane, which is compliant with PICMG 3.0 specifications, provides power
inputs and signal interconnection for boards in the subrack.
Equipment Management Subsystem

The equipment management subsystem is comprised of the shelf management modules
(SMMs), subrack data modules (SDMs), and baseboard management controllers (BMCs) on
various blade server boards and modules.
The equipment management subsystem performs the following functions:
Hardware status monitoring
Equipment management
Operation and alarm maintenance
Statistics collection
Issue 1.6 (2012-05-03)

33
4 Product Structure
4.1.2 Physical Structure

Cabinet Appearance
The GTSOFTX3000 uses Huawei N68E-22 cabinets. Figure 4-2 shows the appearance of
Huawei N68E-22 cabinet.
Figure 4-2 Huawei N68E-22 cabinet
An N68E-22 cabinet occupies an area of 0.48 square meters. Its dimensions are 600 mm x
800 mm x 2,200 mm (width x depth x height). An empty cabinet weighs 100 kg, and a
fully-configured cabinet weighs about 400 kg.
The N68E-22 cabinet is a standard 19-inch cabinet and complies with the following
international standards:
IEC60297-1, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
1:Panels and racks
2:Cabinets and pitches of rack structures
3:Subracks and associated plug-in units
Issue 1.6 (2012-05-03)

34
4 Product Structure
Cabinet Configuration
In typical configuration, the GTSOFTX3000 has one cabinet with one subrack. Figure 4-3
shows the cabinet configuration.
Figure 4-3 Cabinet configuration
Integrated configuration cabinet
(46U)
Power distribution box (3U)
Filler panel (3U)
Filler panel (3U)
Filler panel (3U)
Filler panel (3U)
Filler panel (2U)

Cabling trough (1U)
LAN Switch 1 (1U)
Cabling trough (1U)
LAN Switch 0 (1U)
Cabling trough (1U)
KVMS (1U)
Subrack 0 (14U)
Filler panel (3U)
Filler panel (3U)
Filler panel (3U)
Issue 1.6 (2012-05-03)

35
4 Product Structure
Power distribution frames (PDFs), service processing subracks, and keyboard & video &
mouse & switcher (KVMS) are installed in the cabinet.
Subrack Appearance
In each subrack, the board area provides 14 slots into which boards can be inserted in pairs at
the front and the rear. Figure 4-4 and Figure 4-5 show the front and rear views of an OSTA 2.0
subrack respectively.
Figure 4-4 Front view of an OSTA 2.0 subrack
2
3
4
5
1. Board slots
4. Air intake vent
Issue 1.6 (2012-05-03)
2. Fan box 1
5. Slots for the SMMs

3. Fan box 2
36
4 Product Structure
Figure 4-5 Rear view of an OSTA 2.0 subrack
4
5
6
7
1. Grounding points of the subrack
4. Lower air exhaust vent
2. Upper air exhaust vent

5 and 6 Power entry modules (PEMs)
3. Slots for interface boards

7. Slots for the SDMs
Boards
Table 4-1 lists the boards configured in a subrack.
Table 4-1 Board types
Physical
Board
Name
Type
Remarks
UPB
Universal Process
Blade
Front board
A maximum of 12 UPBs can be

configured in one subrack.
USI
Universal Service
Interface Unit
Rear board
The USI serves as the optional

interface board of the UPB.
Issue 1.6 (2012-05-03)

37
4 Product Structure
Physical
Board
Name
Type
Remarks
SWU
Switching Unit
Front board
A maximum of 12 SWUs can be

configured in one subrack for load
sharing.
SWI
Switch Interface
Unit
Rear board
The SWI serves as the rear interface

board of the SWU.
SMM
Shelf Management
Module
Front board
Two SMMs are configured in one

subrack and work in active/standby
mode.
SDM
Subrack Data
Module
Rear board
Two SDMs are configured in one

subrack and work in active/standby
mode. The SDMs are installed with
the SMMs in pairs.
4.2 Software
4.2.1 Overall Structure
The GTSOFTX3000 software consists of service processing software and server software.
The software modules are distributed among the boards or servers and can be flexibly
configured to meet the actual networking requirements. Figure 4-6 shows the software
structure of the GTSOFTX3000 in the LAN switch networking mode.
Issue 1.6 (2012-05-03)

38
4 Product Structure
Figure 4-6 Software structure of the GTSOFTX3000
4.2.2 Service Processing Software

The service processing software runs on boards in the OSTA subracks of the GTSOFTX3000.
It performs the following functions:
Signaling access and processing
Call processing
Service control
Resource management
Charging information generation
Working with the server software, the service processing software can also perform the
following operations on the host in response to specific commands:
Data management
Alarm management
Performance measurement
Signaling tracing
CDR management
The service processing software adopts a hierarchical design and consists of the following
parts from top to bottom:
Issue 1.6 (2012-05-03)
Various application software

39

Middleware
Operating system
4 Product Structure
Operating System
The operating system of the service processing software is SUSE Linux, which is real-time
software.
Middleware
The GTSOFTX3000 adopts the middleware technology (DOPRA_C) so that the upper-layer
service software is irrelevant to the operating system.
The use of middleware facilitates the migration of software functions between different
platforms. This ensures that new and stable product versions be released quickly.
Application Software
The application software is the functional part of the GTSOFTX3000 software. Loaded with
different software, boards can provide different functions. The GTSOFTX3000 application
software can be classified into the following types:
Signaling bearer software: It is configured on the WIFM and WBSG modules. It

accesses broadband and narrowband signaling, and processes bottom layer protocols.
Service processing software: It is configured on the WCCU module. It performs

functions such as signaling and call processing, mobility management, and resource
management.
Database software: It is configured on the WCDB and WVDB modules. It manages

switch data and dynamic subscriber data.
System support software: It is configured on the DMU, SRMU, IMU, SMM, and AMU
modules. It is responsible for system management and equipment interconnection.
Operation and maintenance (O&M) software: It is configured on the DMU, SRMU, IMU,
and AMU modules. It receives operation commands from the OMU, and returns
command output to the OMU.
4.2.3 Server Software

The server software includes the OMU server, billing gateway, local maintenance terminal
(LMT), and X protocol transfer unit (XPTU) software. Working with the host software, it
performs the following functions:
Data management
Alarm management
Signaling tracing
CDR management
Interception management
The server software adopts the client/server (C/S) mode.

Issue 1.6 (2012-05-03)
OMU server software

40
4 Product Structure
OMU server software is installed on the OMU board, and serves as the server.
Billing gateway software

Billing gateway software is installed on the iGWB board.
LMT software
LMT software is installed on a workstation, and serves as the client.
XPTU software
XPTU software supports only the System of Operative-Search Measures (SOSM)
protocol. The interception in compliance with other interception protocols is
implemented by the OMU.
OMU Server Software

The OMU server software runs on the OMU board in an OSTA subrack. As a combination of
the communication server and database server, the OMU server software is the essential unit
of the operation, administration and maintenance (OAM) software on the client. It performs
the following functions:
Forwards operation and maintenance commands from workstations to the host.
Returns responses or command output from the host to the workstations that deliver the
commands.
The OMU server software runs on SUSE Linux. It implements functions of the terminal OAM
software through multiple parallel service processes, such as the maintenance process, data
management process, alarm process, and performance measurement process. Figure 4-7
shows the hierarchical relationships between the OMU server software, operating system, and
database.
Figure 4-7 Hierarchical relationships between the OMU server software, operating system, and
database
Billing Gateway Software

The billing gateway software is the core component of the CDR management system. It runs
on the iGWB and performs the following functions:
Stores and backs up CDRs generated by the service processing modules (that is, the
WCCU modules) of the GTSOFTX3000 to the hard disks.
Provides billing interfaces to the billing center using FTP or SFTP.
Issue 1.6 (2012-05-03)

41
4 Product Structure
LMT Software
The LMT software runs on Windows based on the hardware platform of a PC. The LMT
software connects to the OMU and iGWB by serving as the client in Client/Server mode. It
provides graphical terminals based on the man-machine language (MML). The LMT can be
located locally or remotely. For example, a remote LMT can connect to the OMU server
through a wide area network (WAN) in dial-up mode.
You can perform the following maintenance operations on the LMT:
Data maintenance
Alarm management
Call and signaling tracing
CDR management
Report generation
Issue 1.6 (2012-05-03)

42
5 Interfaces and Protocols
Interfaces and Protocols
This chapter describes physical interfaces and protocol interfaces provided by the
GTSOFTX3000.
5.1 Physical Interfaces

Table 5-1 lists the maintenance interfaces supported by the GTSOFTX3000.
Table 5-1 Maintenance interfaces supported by the GTSOFTX3000
Physical
Unit
Interface
Function
Description
UPB
COM serial
port
Used for local

commissioning
The COM serial port on the UPB

incorporates the functions of the BMC serial
port and the system serial port. The type of
serial port to be used can be specified using
the SMM board. The BMC serial port
supports 115,200 bit/s baud rate. The baud
rate of the system serial port can be
configured based on site requirements. This
port complies with RS232.
USB port
Used for USB

connection
This port complies with USB2.0, which is

backward compatible with USB1.1.
BMC COM
serial port
Used for
loading or
upgrading the
BMC software
This port complies with RS232 and supports

115,200 bit/s baud rate. It is connected to an
RJ45 connector. This port does not have an
indicator.
SWU
Issue 1.6 (2012-05-03)

43
Physical
Unit
SMM
SDM
Issue 1.6 (2012-05-03)
Interface
Function
Description
SYS COM
serial port
Used for local

management,
maintenance,
and
commissioning
of the Base and
Fabric planes
This port complies with RS232 and supports

115,200 bit/s baud rate. It is connected to an
RJ45 connector. This port does not have an
indicator. By default, the SYS COM serial
port functions as the serial port of the Base
plane. You can run command lines over the
BMC COM serial port to switch the SYS
COM serial port between the Base plane and
the Fabric GE plane.
LAN0
Ethernet
port
Used for
commissioning
This port works in 10/100 Mbit/s Base-T

auto-negotiation mode. It is connected to a
UTP5 cable with an RJ45 connector. This
port has two indicators. It is used only for
loading drives of the Base plane and internal
commissioning.
LAN1
Ethernet
port
Used for
commissioning
This port works in 10/100 Mbit/s Base-T

auto-negotiation mode. It is connected to a
UTP5 cable with an RJ45 connector. This
port has two indicators. It is used for loading
drives of the Fabric plane or for connecting
the DEBUG Ethernet port of the Fabric GE
daughter board. This port is available only
after the Base plane starts successfully.
COM serial
port
Used for local

commissioning,
maintenance,
configuration,
and local or
remote
connection
management
This port complies with RS232 and provides

115200 bit/s baud rate. It can be connected
to an RJ45 connector. This port does not
have an indicator.
ETH0
Ethernet
port
Used for
commissioning,
maintenance,
and
configuration
This port supports 10/100 Mbit/s Base-T

auto-negotiation mode. It is a standard FE
port connected to a UTP5 cable with an
RJ45 connector.
COM1
serial port
Used for local

commissioning,
maintenance,
configuration,
and local or
remote
connection
management

have an indicator.

44
Physical
Unit
Interface
Function
Description
COM2
serial port
Used for
configuration
and
management of
the PDB

have an indicator.
ETH
Ethernet
port
Used to
implement
operation and
maintenance
such as
command line
executions and
Web UI-based
management
This port supports 10/100 Mbit/s Base-T

auto-negotiation mode. It is a standard FE
port connected to a UTP5 cable with an
RJ45 connector.
Table 5-2 lists the service interfaces supported by the GTSOFTX3000.

Table 5-2 Service interfaces supported by the GTSOFTX3000
Physical
Unit
Interface
Function
Description
USI
GE port
Used to connect to the

Ethernet
This port is an RJ45 port that

supports 10 Mbit/s, 100 Mbit/s, or
1,000 Mbit/s Base-T
auto-negotiation.
VGA

monitor
This port supports a monitor with

1024 x 768 or higher SVGA
resolution.
USB port

mouse and keyboard
This port complies with USB2.0.
Base GE port

Base plane
The port is a 4-channel Gigabit

Ethernet port, which supports 10
Mbit/s, 100 Mbit/s, and 1,000
Mbit/s Base-T auto-negotiation and
has two indicators.
Fabric GE
port

Fabric plane
The port is a 4-channel Gigabit

Ethernet port, which supports 10
Mbit/s, 100 Mbit/s, and 1,000
Mbit/s Base-T auto-negotiation and
has two indicators.
SWI
Issue 1.6 (2012-05-03)

45
Physical
Unit
Interface
Function
Description
ETIA0
E1/T1 port
Each ETMA daughter

board provides a
16-channel E1/T1
port.
The ETIA0 has two ETMA

daughter boards configured to
provide two DB-78 ports. From top
to bottom, the two daughter boards
are marked E1/T1_0-15 and
E1/T1_16-31.
8 kHz clock
port
Used to transmit the

8-kHz clock signals
extracted from the E1
line to the active and
standby SWIA1
boards
The board provides two RJ45 clock

ports, which are marked with
8K_OUT0 and 8K_OUT1 from top
to bottom.
E1/T1 port
Each ETMA daughter

board provides a
16-channel E1/T1
port, and each GE
daughter board
provides two Ethernet
ports.
The ETIA2 board has an ETMA

daughter board configured to
provide one DB-78 port. The
daughter board is marked with
E1/T1_0-15.
8 kHz clock
port
Used to transmit the

8-kHz clock signals
extracted from the E1
line to the active and
standby SWIA1
boards
The board provides two RJ45 clock

ports, which are marked with
8K_OUT0 and 8K_OUT1 from top
to bottom.
GE port
Each ETMA daughter

board provides a
16-channel E1/T1
port, and each GE
daughter board
provides two Ethernet
ports.
The board has one external GE

daughter board configured to
provide two RJ45 Ethernet ports
which support 10 Mbit/s, 100
Mbit/s, and 1,000 Mbit/s Base-T
auto-negotiation. From top to
bottom, the two Ethernet ports on
the daughter board are marked
LAN0 and LAN1.
ETIA2
5.2 Protocol Interfaces

The GTSOFTX3000 provides standard and open protocol interfaces to support various types
of signaling. This enables the GTSOFTX3000 to be configured in a flexible manner. In a
mobile network, the GTSOFTX3000 provides the protocol interfaces shown in Figure 5-1
when it acts as the VMSC server, GMSC server, and TMSC server.
Issue 1.6 (2012-05-03)

46
Figure 5-1 Protocol interfaces provided by the GTSOFTX3000 in a GSM-R network

HLR / FFN SCP GMLC SMC Dispatch
station
PBX
BC
Other
networks
FE
C
Lg
FE
Service
management
layer
AC Server
ISS Server
FE
RBC
M2000
MML
TUP /ISUP
PSTN
PLMN
Network
control
layer
N c /E
GTSOFTX3000
MSC Server
A
Mc
Gs
BSC
SGSN
MGW
BSC: Base Station

Controller
BC: Billing Center
SG: Signaling Gateway
GMLC: Gateway Mobile Location

Center
SCP: Service Control Point
SGSN: Serving GPRS Support Node
MGW: Media Gateway

PSTN: Public Switched
PLMN: Public Land Mobile Network

RBC: Radio Block Center
Edge access layer
HLR: Home Location Register

SMC: Short Message Center
AC Server: Acknowledgement
Center Server
FFN: Follow-Me Function Node
Telephone Network
Table 5-3 describes the interfaces and protocols supported by the GTSOFTX3000.
Table 5-3 Interfaces and protocols supported by the GTSOFTX3000
Interworking
NEs
Interface
Protocol
Protocol Description
Specifications
with Which the
Interface
Complies
MSC
Server-MSC
Server
Nc
BICC
Enables the GTSOFTX3000 to exchange

control signaling with other MSC servers
over the Nc interface to establish, modify,
and terminate calls.
3GPP
ITU-T
Issue 1.6 (2012-05-03)

47
Interworking
NEs
Interface
Protocol
Specifications
with Which the
Interface
Complies
SIP
Enables the GTSOFTX3000 to interwork

with other MSC servers.
3GPP
ITU-T

with other MSC servers using ISUP trunks
(connected using the MGW).
ITU-T
ETSI
Mobile application part.
3GPP
ISUP
MAP
Specifies the signaling interaction flows

between NEs in mobile networks to
implement mobile subscriber roaming.
MSC - MGW
Mc
H.248
Enables the GTSOFTX3000 to control

MGWs.
3GPP
MSC - HLR
MAP

3GPP
VLR-HLR
MAP

3GPP
MSC-EIR
MAP

3GPP
MSC-GMLC
Lg
MAP
Mobile application part.
3GPP

MSC-BSC
BSSAP
Specifies the A interface between the

GTSOFTX3000 and the BSC.
3GPP
MSC-SGSN
Gs
BSSAP+
Specifies the Gs interface between the

GTSOFTX3000 in the CS domain and the
SGSN in the PS domain.
3GPP
MSC-SCP
CAP/INA
P
CAP

with different SCPs. The GTSOFTX3000
can function as the SSP to provide service
switching function (SSF), call control
function (CCF), service resource function
(SRF), and call control agent function
(CCAF) functions.
3GPP
MSC-BC
FTP

with the BC.
IETF
MSC-SG
M2UA/M
3UA
Supports the interworking between the

GTSOFTX3000 and SGs.
IETF
Issue 1.6 (2012-05-03)

48
Interworking
NEs
Interface
Protocol
Specifications
with Which the
Interface
Complies
MSC-PSTN/PL
MN
ISUP

with the PSTN/PLMN using ISUP trunks
ITU-T
ETSI
R2

with certain PSTN switches that support R2
signaling but do not support SS7 signaling.
The GTSOFTX3000 can interwork with
such PSTN switches using channel
associated signaling (CAS) trunks
ITU-T
PRA

with devices such as the PBX over the PRI
interface (connected using the MGW).
ITU-T
SIP

with the IP PBX.
IETF
ITU-T
PRA

with devices such as the PBX over the PRI
interface (connected using the MGW).
ITU-T
ISUP

with dispatch stations using ISUP trunks
ITU-T
ETSI

with SIP dispatch stations.
IETF
Internal protocol.
MSC-PBX
MSC-dispatch
station
SIP
MSC-AC
Server
MSC-ISS
Server
TCP/IP
ITU-T

with AC servers, providing the high-priority
call acknowledgement function.
Issue 1.6 (2012-05-03)
TCP/IP
Internal protocol.

with ISS servers, providing the Master Train
List function.

49
6 Networking and Application
Networking and Application
This chapter describes the networking and application of the GTSOFTX3000.
6.1 Networking
The GTSOFTX3000 provides interfaces with rich functions that support multiple protocols.
The GTSOFTX3000 can be deployed flexibly based on actual network requirements. Apart
from some traditional networking modes, the GTSOFTX3000 can achieve:
TDM 2 Mbit/s Link Networking

The full bandwidth of the E1 cable is available for a 2 Mbit/s signaling link to interconnect
with other SPs. By doing this, the cost is reduced and networking is simplified to expand the
communication capacity between two SPs.
IP Networking
The mobile communications network adopts IP networking to bear voice services, which
helps reduce transmission costs. In a typical IP bearer network, routers can be deployed to
transmit voice data.
Satellite Transmission Link

The GTSOFTX3000 supports satellite transmission links over the Mc and A interfaces. This
enables the GTSOFTX3000 to network flexibly and adapt to various geographical areas.
Intra-Office Networking over TDM Between MGWs

When one MSC server controls over multiple MGWs to form a large-scale MSC, the
intra-office speech channels between MGW are networked over TDM. The GTSOFTX3000
supports the network of multiple zone numbers and the large local network.
Intra-Office Networking over IP Between MGWs

When one MSC server controls over multiple MGWs to form a large-scale MSC, the
intra-office speech channels between MGW are networked over IP. The GTSOFTX3000
supports the network of multiple zone numbers and the large local network.
Issue 1.6 (2012-05-03)

50
Dual Homing
The dual homing scheme enhances the fault tolerance of the MSC server. In a dual homing
scheme, two MSC servers work as the backup for each other. Normally, each MSC server
controls the services of its own domain; when one MSC server is faulty, the other takes over
all of its services.
The GTSOFTX300 supports four dual homing schemes:
1+1 backup
1+1 mutual assistance
N+1 backup
N+1 mutual assistance
MSC Pool Networking

In a traditional mobile network, a BSC can connect only to one MSC server. In an MSC Pool
network, however, a BSC can connect to multiple MSC servers. Pooled MSC servers provide
services for subscribers in the area covered by the MSC Pool. The MSC Pool networking
implements MSC server-level disaster tolerance, improving network reliability.
6.2 Application
6.2.1 Typical Networking
Together with Huawei UMG8900, the GTSOFTX3000 provides the functions of the MSC,
VLR, GCR, SSP, and IWF. The GTSOFTX3000 serves as the MSC, VLR, GCR, SSP, and
IWF in a GSM-R network to meet the requirements of offices at multiple levels.
Figure 6-1 shows the networking of the GTSOFTX3000 in a GSM-R network.
Issue 1.6 (2012-05-03)

51
Figure 6-1 GTSOFTX3000 in a GSM-R network
Other
MSC /VLR
AC Server
ISS Server
MSC / VLR / SSP

GCR / IWF
Dispatch station
equipment
MS
GTSOFTX 3000
BSS
Train
PSTN /PBX
SCP
MGW
Train control
center
SGSN
Datacom
network
HLR /FFN /EIR / AUC
GGSN
Physical connection
Signaling
OMC
Billing center
The GTSOFTX3000 and the UMG8900 are integrated into an MSC (GMSC or TMSC) entity
and support the GSM protocols and the GSM-R protocols.
One GTSOFTX3000 supports the access of multiple UMG8900 to implement the remote
networking of access modules and reduce alternative routes.
6.2.2 WIN Networking

GSM-R MSC supports CAMEL 4 and CAMEL 3 and is compatible with CAMEL 1 and
CAMEL 2. Cooperating with Huawei TELLIN intelligent network system, it can deliver
various wireless intelligent services over the GSM-R network.
Figure 6-2 shows the networking of the GSM-R MSC in a wireless intelligent network
(WIN).
Issue 1.6 (2012-05-03)

52
Figure 6-2 GTSOFTX3000 in a WIN network
HLR/FFN
SCP
Other MSC/VLR/GCR
MS
PSTN/PBX
BTS
MS
MSC/VLR/SSP/GCR
Train
6.2.3 IP Networking
When a GSM-R network uses IP networking, CN NEs are connected to remote routers over
the synchronous digital hierarchy (SDH) transmission network. The remote routers comprise
an IP bearer network and interwork with the NEs.
Figure 6-3 shows the IP networking of a GSM-R network.
Figure 6-3 IP networking of a GSM-R network
Central
equipment room
Remote equipment
room A
MSC
server
Router
Remote equipment
room B
Router
BSC
MGW
MGW
SDH
BSC
BSC
FE
E1
POS/E1
POS/E1
Issue 1.6 (2012-05-03)

53
7 Operation and Maintenance
Operation and Maintenance
This chapter describes O&M functions provided by the GTSOFTX3000, including:

Fault management
Charging management
Security management
Terminal system
7.1 Fault Management

The fault management functions are used to detect, locate, and rectify faults in the system.
You can use the tools provided by the GTSOFTX3000 to perform routine maintenance, which
helps to prevent service interruptions. Fault management functions include system self-check,
alarm management, maintenance management, and message tracing.
System self-check
The GTSOFTX3000 checks the following at regular intervals:
The usage of system resources.
Whether the overload conditions have been met.
The GTSOFTX3000 can automatically handle overload problem.
The system self-check helps minimize the impact of system faults.

Alarm management
This function enables the GTSOFTX3000 to collect information about device faults and
abnormalities, generates alarms in various categories and severities in the Browse
Alarms window, and sends parsed alarms to the element management system (EMS).
Figure 7-1 shows an example of alarms generated in the Browse Alarms window.
Issue 1.6 (2012-05-03)

54
Figure 7-1 Browse Alarms window
Maintenance management
This is a basic function provided by the GTSOFTX3000. It allows you to perform
routine maintenance operations using MML commands or the GUI.
This function allows you to manage and maintain the hardware, system resources,
signaling links, physical ports, MGWs managed by the GTSOFTX3000, and related
bearer resources by querying, displaying, switching over, restarting, isolating, blocking,
and activating them.
Message tracing
The GTSOFTX3000 provides a graphical interface for message tracing. The interface or
signaling message tracing results facilitate data verification and troubleshooting. The
following message tracing functions are provided:
Standard interface message tracing, for example, for messages sent over the A, C/D,
E, Q, Q1, and T1 interfaces
Subscriber message tracing, which allows you to trace the messages of a specific
subscriber over a specific interface
Signaling message tracing, for example, tracing MTP, TCAP, SCCP, and SIGTRAN
signaling messages
Details about traced interface or signaling messages
Message tracing result view, which allows you to export and save message tracing
results so that you can view them both online and offline.
7.2 Performance Measurement

The performance measurement function allows you to measure the following:
Traffic in different directions
Traffic of different bearer objects
Traffic of different services
Failure causes
Issue 1.6 (2012-05-03)

55
These performance measurement entities indicate the system running status, which can in turn
be used to manage devices and optimize network performance.
The performance measurement subsystem provides the following functions:
Creates, modifies, runs, suspends, deletes, and queries performance measurement tasks,
and graphically displays the measurement results.
Performs secondary data analysis, and displays the data in charts such as a bar or line
chart.
7.3 Charging Management

The charging management function is provided by the iGWB, HUAWEI Operation &
Maintenance System, and CDR Query and Browse System. It provides the following
functions:
Receives CDRs generated by the GTSOFTX3000.

CDRs generated for calls are buffered in the CDR pool of the host. The host sends the
CDRs to the iGWB server through the BASE bus.
Saves and backs up original CDRs.

The storage space of the iGWB server can be increased by adding boards. This ensures
that the iGWB server can store large amount of CDR data for a long time. CDRs stored
on the iGWB server can be backed up over the network.
Preprocesses CDRs.
The iGWB server converts, sorts, and filters CDRs to generate final CDRs. Then, the
iGWB stores final CDRs in the local disk. You can query CDRs and perform
CDR-related operations on the iGWB server.
Provides the FTP/SFTP interface for the BC.

The BC can automatically obtain CDRs over the FTP or SFTP interface.
Provides operation log for CDRs.

Information about CDR operations is recorded, including the operator, operation time,
changed data, and details about the operation performed.
Provides the hot billing service.

After a call ends, the iGWB server can send the CDR generated for the call to the BC
through a dedicated channel in seconds.
Allows users to query and view original and final CDRs.

You can search original and final CDRs by setting search criteria and view the search
result in the CDR query and browse system.
Generates CDRs immediately.

When testing services during site deployment, upgrade, migration, and capacity
expansion, you can check the latest CDRs to determine whether the iGWB is working
correctly.
Issue 1.6 (2012-05-03)

56
7.4 Security Management

Multiple users can log in to the GTSOFTX3000 operation and maintenance system at the
same time. To ensure its own security as well as that of the user, the GTSOFTX3000 provides
authorization management and log management.
Authorization management
Operators and maintenance consoles of the GTSOFTX3000 are assigned different
authorization levels. On the operation and maintenance system of the GTSOFTX3000,
an MML command can be executed only when both the operator and the maintenance
console are authorized to run the MML command.
Log management
You can query logs of MML command execution to determine whether any operations
that adversely affect the system have been performed.
7.5 Terminal System

The terminal system is the hardware platform for the GTSOFTX3000 to provide O&M
functions. It consists of the OMU, iGWB, and LMT. Figure 7-2 shows the structure of the
terminal system.
You can use the LMT or the iManager M2000 to perform operations and manage the
GTSOFTX3000.
Figure 7-2 Structure of the terminal system
iManager
M2000
BC
GTSOFTX 3000
To the BC
To the EMS
HUB
LMT
Issue 1.6 (2012-05-03)
LMT
LMT

57
The terminal system works in C/S mode. The OMU and iGWB together act as the server and
connect the host of the GTSOFTX3000 to external computers over the Ethernet. The LMT
acts as the client and can be configured as the maintenance console, data management console,
alarm console, performance measurement console, or CDR console as required.
As the hardware core of the O&M subsystem, the OMU provides a channel for
communications between the LMTs and the hosts. It forwards the O&M commands received
from the LMTs to the hosts, and returns the corresponding responses to the LMTs.
Issue 1.6 (2012-05-03)

58
8 Reliability
Reliability
8.1 Hardware Reliability

8.1.1 Distributed Hardware Structure
The GTSOFTX3000 adopts the distributed hardware structure. The modular design of the
functions realizes the distributed processing. The functions of the modules are independent of
each other, and are controlled by different processors. The fault in one processor does not
affect the operation of the whole system.
8.1.2 Redundancy Design

The hardware of the GTSOFTX3000 adopts designs such as active/standby mode, load
sharing mode, and redundancy configuration, to ensure reliability of the hardware system.
The main parts in the GTSOFTX3000 adopt the multi-processor backup design. For
example, the OMU, SMM, WCCU, WCDB, WCKI, WMGC, and iGWB have two
processors working in active/standby mode. In normal conditions, the active processor
controls the running of the module, and the standby processor synchronizes with the
active one in real time. When the active processor is faulty, the standby one takes over
the service at once. The standby processor takes the place of the faulty active processor
to control the operation of the system without interrupting the service.
The service modules and interface modules of the GTSOFTX3000 adopt load sharing
mode. That is, two or more boards share the related functions during the normal working.
Once a board becomes faulty, the other boards take over the tasks of the faulty board
provided that certain performance indexes, such as call loss, are ensured.
The IP interface of the GTSOFTX3000 supports physical backup, thereby ensuring

reliability of the IP routes between the GTSOFTX3000 and the IP bearer network.
8.1.3 Derating Design

It is to derate the electric stress and heat stress to the values under the rated values when the
electronic components run. As a result, the following purposes can be achieved:
Postpone the degeneration of the parameter
Prolong service lives
Enhance the reliability of the parameter
Issue 1.6 (2012-05-03)

59
8 Reliability
8.1.4 Maintainability Design

Maintainability design aims at meet the specified quantity and quality demands on
maintainability, especially the demand on reducing the maintenance time.
The maintenance design covers the following:
Product design and maintenance simplification
Reachability
Standardization and exchangeability
Modularization
Error prevention design and identifier
Testing and diagnosis technology
Human and environment factors
The details are described as follows:

The boards are designed to be hot-pluggable to reduce the time for board replacement.
No cable is outlet from the front panel, facilitating board removal, and assembly and
decreasing the maintenance time.
When a module in the system is faulty, the maintenance terminal can detect the fault and
report it.
There is a local maintenance MML operation terminal, which is convenient and practical
for the maintenance staff to locate and remove faults fast.
8.1.5 Selection and Usage of Components

The selection and usage of components are key to ensure component reliability.
For the GTSOFTX3000, the component types, specifications, and suppliers are selected based
on the demands on product reliability. The focus is on component replacement and unification.
The component unification and reliability model analysis is used to reduce the number of
components used and improve system running, after the components pass the aging test.
Therefore, the components are of high quality ensuring the reliability of the hardware system.
8.1.6 Power Reliability

To improve the reliability of the power supply system, the following techniques are employed
in the GTSOFTX3000:
Distributed power supply: Two power supply systems work in the redundancy backup
mode. The systems have the protection functions against lightening, power failure, over
and under voltage, and over and under current. When the power fails, the whole system
can restart within five minutes.
The power module of the subrack adopts 2+2 backup design. When one power module is
faulty, it does not affect the operation of the system.
Overvoltage and overcurrent protection measures are applied to +5 V / -48 V power

input and external interfaces (such as E1 interfaces). These measures comply with
Appendix B of ITU-T Recommendation G.703 and relative specifications.
Issue 1.6 (2012-05-03)

60
8 Reliability
8.2 Software Reliability

8.2.1 Compliance with the CMM Flow
Huawei strictly follows the Capability Maturity Model (CMM) procedures throughout the
development of the GTSOFTX3000, from requirement analysis, system design to software
test. Code walk-through, inspection, review, unit test, system test, and other useful quality
assurance measures taken in the GTSOFTX3000 development improve the reliability of the
software considerably.
8.2.2 Protective Measures

The modular design is used for the software. The software modules are based on the loose
coupling mechanism, for which other modules will not be affected in case that one module
fails. In addition, error detection, error isolation, and error recovery are added to facilitate
fault location.
8.2.3 Fault Tolerance

The GTSOFTX3000 has the self-healing ability, which improves the fault tolerance of the
software system and helps avoid the breakdown of the entire system caused by minor
software errors. The error tolerance capabilities of the GTSOFTX3000 are implemented in the
following aspects:
Periodical check of key resources
Task monitoring
Storage protection
Data check
Operation log storage
8.2.4 Troubleshooting
The GTSOFTX3000 has the capabilities to automatically detect and locate hardware faults
and provides the following functions when hardware faults occur:
Fault isolation
Switchover
Restarting
Reloading
8.2.5 Support of Hot Patches

Sometimes the host software must be modified when the equipment is running in order to
remove system bugs, add new functions, and adhere to service requirements. The traditional
way is to stop the equipment for upgrading. This, however, affects the service processing and
communication quality. The GTSOFTX3000 supports installation of hot patches to the host
software. In this way, the host software can be upgraded without interrupting the services,
improving the communication quality.
Issue 1.6 (2012-05-03)

61
8 Reliability
8.3 Charging Reliability

The charging reliability of the GTSOFTX3000 involves the following aspects:
Hardware reliability of charging gateway
Software reliability of charging gateway
CDR reliability
8.3.1 Hardware Reliability of Charging Gateway

In the iGWB system, key devices are redundant for backup. This ensures that services are not
interrupted when a fault occurs in the system.
Two-Node System
In the iGWB two-node system, each pair of boards work in active/standby mode. The
automatic switchover mechanism ensures system reliability and service continuity.
Redundant Disks Using RAID

The iGWB adopts the most commonly used RAID technology. It configures local disks as
RAID 1 to prevent data loss in case of a disk failure.
Dual-Network and Dual-Plane Architecture

Each board of the iGWB communicates with the GTSOFTX3000, OMU, and BC through the
Base plane, Fabric plane, and external network interfaces. This dual-plane architecture
improves system reliability. It provides the following functions:
The GTSOFTX3000 is connected to iGWB through the primary and secondary links on
the Base plane to form two planes.
The primary and secondary boards are connected to the OMU through the Base plane
and then connected to the NMC through the OMU.
Data on disks are synchronized between the primary and secondary boards through the
Fabric plane.
The primary and secondary boards provide an independent external network interface for
connecting to the BC and uploading CDR files to the BC through FTP or SFTP. For
network isolation purpose, this network interface is only used to access the charging
network to ensure the network security.
The primary and secondary boards provide an independent external network interface for
connecting to the third-party server and backing up CDR files to the third-party server
through FTP or SFTP. The network interface is independent to ensure network security.
8.3.2 Software Reliability of Charging Gateway

The iGWB software adopts automatic fault detection, data security, a virtual IP address to
improve system reliability.
Issue 1.6 (2012-05-03)

62
8 Reliability
Automatic Fault Detection

The system automatically detects the running status of software and hardware and
submits faults if it occurs. You can view the running status and faults of software and
hardware on the client.
If a hardware fault occurs in a key component or a fault is not rectified automatically, the
primary and secondary servers are switched over to ensure normal running of the system.
If a software (such as a process) fault occurs or a fault is not rectified automatically, the
active and standby processes are automatically switched over to ensure normal running
of the system.
The CDRs on the primary and secondary boards are synchronized in real time through
the CDR synchronization mechanism.
Local disks are set to a RAID mode to ensure security of important data such as charging
information, original CDRs, final CDRs, and status information.
System data is stored in different paths for redundancy backup. When an exception
occurs, system data is loaded and checked automatically.
To protect important data, the iGWB provides automatic backup of charging data.
Data Security
Virtual IP Address
The virtual IP address technology is used to ensure normal connections between the
GTSOFTX3000 and the BS after the primary and secondary boards of the iGWB are switched
over.
8.3.3 CDR Reliability

CDR Reception
The iGWB receives CDRs from the GTSOFTX3000 by using the Sliding Window Protocol.
Figure 8-1 Shows the CDR reception flow defined in the Sliding Window Protocol.
Issue 1.6 (2012-05-03)

63
8 Reliability
Figure 8-1 CDR reception flow

EMS
Maintenance
terminal
LAN
switch
LAN
BC
switch
S
M
M
S S
U U U U
W W
S S S S
I I
I I I I
A A
1 1 7 7
0 0
U U
S S
I I
1 1
U U
S S S
I I M
1 1 M
G G
S S
C C
i i
O O W W
U U M M U U G G
1 1
W W
U U A A
0 0
B B
0 0
0 0
0#
External link
Internal link
SMM: Shelf Management Module
SWI: Switch Interface Unit
SWU: Switching Unit
GCU100: General Control Unit
IP PBX: PBX that supports SIP
USI: Universal Service Interface

iGWB: iGateway Bill
OMU: Operation and Maintenance Unit
Transmitting CDRs between the GTSOFTX3000 and the iGWB

The GTSOFTX3000 sends CDRs to the iGWB in real time by using the UDP over two
base planes.
Receiving CDRs by the primary and secondary boards of the iGWB

The iGWB uses CDR synchronization technology to synchronize CDR files on the
primary and secondary boards of the iGWB.
Sliding Window Protocol

CDRs are transmitted between the GTSOFTX3000 and the iGWB through the Sliding
Window Protocol. The GTSOFTX3000 sends some CDRs to the iGWB. After receiving
the CDRs, the iGWB checks and filters the CDRs and then stores the CDRs in the
window. After the CDR data is written into the hard disk completely, the iGWB responds
to the GTSOFTX3000. Then the GTSOFTX3000 continues to send new CDRs. To
Issue 1.6 (2012-05-03)

64
8 Reliability
ensure transmission efficiency, the iGWB can receive and check new CDRs while
storing CDR data.
The key data about the sliding window status in the iGWB is written into the hard disk in
time. When the iGWB is restarted or the primary and secondary servers are switched
over, no CDR is lost or duplicate during transmission.
CDR Processing
Three modules are involved in the CDR processing from receiving CDRs to generating final
CDRs. The iGWB creates a reliable CDR processing task between the three modules. CDRs
are processed in the unit of the package. After original CDRs are stored successfully, the
information about CDR packages is also stored in the hard disk. After original CDRs are
processed and stored as final CDRs, the package numbers are also stored. When the iGWB is
restarted, the iGWB can calculate the package number of the original CDRs that are not
processed based on the package numbers of final CDRs. Then the iGWB continues to process
the remaining original CDRs.
CDR Distribution
When CDR files are distributed in PULL mode, the billing center fetches CDRs from the
iGWB. The iGWB provides the FTP or SFTP user name and password to the billing center
and opens the read and write permissions of the directory where the second copy of final
CDRs is stored.
When CDR files are distributed in PUSH mode, the iGWB sends CDRs to the billing center.
The billing center provides the FTP or SFTP user name and password to the iGWB and opens
the directory where the final CDRs are stored.
CDR Backup
CDR backup further ensures CDR reliability. The iGWB automatically backs up CDR files on
other storage devices through the LAN or WAN to improve data security.
8.4 Data Reliability

The GTSOFTX3000 provides the following data protection mechanisms:
The GTSOFTX3000 supports a synchronous data backup mechanism between the active
and standby modules in real time. Whenever an active module is down, the standby
module is automatically switched to be the active one. All programs and data on the
module are immediately brought into effect.
The GTSOFTX3000 supports the backup of data from the database of the active
processor to a flash memory. This enables quick restart of the active processor after data
is obtained from the flash memory.
The GTSOFTX3000 supports the automatic CDR backup mechanism.
The OMU conducts a regular CRC of the mainframe data. If the data of the mainframe is
not consistent with that of the background, the OMU starts a setting procedure to the
foreground. If the setting procedure fails after preset attempts, an alarm is generated to
remind the operation staff to restore the data.
Issue 1.6 (2012-05-03)

65
9 Technical Specifications
Technical Specifications
This chapter describes the technical specifications of the GTSOFTX3000.
9.1 System Capacity

Table 9-1 lists the system capacity of the GTSOFTX3000.
Table 9-1 System capacity of the GTSOFTX3000
Item
Specifications
Maximum number of subscribers
300,000 (0.025 Erl)
Maximum number of MGWs
300
Maximum number of RNCs
256
Maximum number of BSCs
256
Table 9-2 lists the reference traffic model of the GTSOFTX3000.

Table 9-2 Reference traffic model of the GTSOFTX3000
Item
Typical Value
Mobile subscriber busy hour average traffic
0.025 Erl
Mobile subscriber average call duration
60s
Number of location registrations and updates of a mobile

subscriber during busy hours
Number of handovers of a mobile subscriber per call
0.2
Number of SMSs sent by a mobile subscriber during busy hours
Trunk busy hour average traffic
0.8 Erl
Trunk average call duration
60s
Issue 1.6 (2012-05-03)

66
9.2 System Processing Capability

Table 9-3 lists the protocol processing capability of the GTSOFTX3000.
Table 9-3 Protocol processing capability of the GTSOFTX3000
Item
Specifications
Supported signaling point coding types
14-bit and 24-bit coding types
Maximum source signaling points
32 (512 at maximum on an N+1

dual-homing network)
Maximum destination signaling points
800 for narrowband, 1,024 for broadband
Maximum IP signaling bandwidth
160 x 1000 Mbit/s
Maximum SCTP links
20,992
Maximum 64-kbit/s MTP links supported by

a WBSG process
128
Maximum 2-Mbit/s MTP links supported by a

WBSG process
Maximum SCTP links supported by a WBSG

process
256
Maximum rate of packet dispatching by a

WIFM process
128,000 packets/second
Clock stratum
Stratum-2 A
Table 9-4 lists the CDR processing specifications of the GTSOFTX3000.

Table 9-4 CDR processing specifications of the GTSOFTX3000
Item
Specifications
Average length of an original CDR
400 bytes
CDR buffer time on a single WCCU Module
2 hours
Storage capacity for CDRs on the iGWB
230 GB (a pair of boards)
CDR processing capability of the iGWB
4,000 CDR/s (a pair of boards)
Table 9-5 lists the number analysis specifications of the GTSOFTX3000.

Table 9-5 Number analysis specifications of the GTSOFTX3000
Item
Specifications
Maximum length of a number for analysis
32 digits
Issue 1.6 (2012-05-03)

67
Item
Specifications
Maximum call prefixes
200,000
Maximum MSRNs/HONs
10,000
Maximum GT codes
80,000
Maximum GT capability on a single 64-kbit/s MTP link
60 GTT/s
9.3 Call Setup Duration

Table 9-6 lists the specifications of call setup duration.
Table 9-6 Specifications of call setup duration (for 95% of the calls)
Call Type
Specifications
< 2s
Ordinary group call
< 5s
Mobile-to-fixed call
< 5s
Fixed-to-mobile call
< 7s
Mobile-to-mobile call
< 10s
Low priority call
< 10s
PTT seizure time
< 1s
PTT release time
< 1s
9.4 Wireless Train Control

Table 9-7 lists the wireless train control specifications of the GTSOFTX3000.
Table 9-7 Wireless train control specifications of the GTSOFTX3000
Item
Specifications
Establishment delay of mobile originated calls
< 8.5s (for 95% of the calls),

10s (for 100% of the calls)
Error ratio of connection establishment
< 1%
Maximum E2E transfer delay (of 30 byte data block)
0.5s (for 99% of the calls)
Loss rate of connection
< 1%
Issue 1.6 (2012-05-03)

68
9.5 Power Supply

Table 9-8 lists the power supply specifications of GTSOFTX3000.
Table 9-8 Power supply specifications of GTSOFTX3000
Item
Specifications
Operating voltage (standard configuration)
Rated voltage
48 V DC
Voltage fluctuations
40 V to 57 V
Operating voltage (configuration for

Commonwealth of Independent States)
Rated voltage
60 V DC
Voltage fluctuations
51 V to 69 V
Operating current
87.5 A
DC per fuse
60 A
9.6 Power Consumption

Table 9-9 lists the power consumption specifications of GTSOFTX3000.
Table 9-9 Power consumption specifications of GTSOFTX3000
Item
Typical Power
Maximum Power
Remarks
1 subrack (in full

configuration)
1600 W
2100 W
1 W = 3.413 BTU
1 cabinet (in full

configuration)
1600 W
2100 W
9.7 Clock System

Table 9-10 lists the clock system specifications of the GTSOFTX3000.
Table 9-10 Clock system specifications of the GTSOFTX3000
No.
Item
Specifications
Network access
parameter
Lowest accuracy
Stratum-2 clock: 4 x 10-7
Pull-in range
Stratum-3 clock: 4.6 x 10-6
Maximum frequency
offset
Issue 1.6 (2012-05-03)
Stratum-2 clock: 5 x 10-10/day

Stratum-3 clock: 2 x 10-8/day

69
No.
Item
Long-term phase
change
Specifications
Initial maximum
frequency offset
Stratum-2 clock: < 5 x 10-10/day
Ideal working status
MRTIE 1 ms
Hold working status
MRTIE (ns) a x s + (1/2) x b x s2 + c
Stratum-3 clock: < 1 x 10-8/day
where s indicates time in seconds. The unit of

MRTIE is nanosecond (ns).
Stratum-2 clock:
a = 0.5
b = 1.16 x 10-5
c = 1000
Stratum-3 clock:
a = 10
b = 2.3 x 10-4
c = 1000
3
Clock working mode
Fast pull-in, locked, holdover, and free-run
Input jitter tolerance
The relation between the maximum allowed input jitter and the lower limit
of wander is shown as follows.
For example, if the jitter frequency of an input signal is 1 kHz, and the
amplitude is greater than 1.5 UI, and the system continues to work normally,
it indicates that the signal meets the requirements.
UI is the unit interval. The reciprocal of the frequency of the digital signal is one UE.
For example, the UI of 2.048-Mbit/s signal is 488 ns.
Issue 1.6 (2012-05-03)

70
Lowest accuracy is the maximum value of the offset to the nominal frequency in a long term (20
years) if there is no external reference frequency (free-run mode).
Maximum frequency offset is the maximum value of the relative frequency offset in a unit period
during consecutive running of the clock.
Pull-in range is the maximum frequency bandwidth of the input clock signals that the clock can lock.
MRTIE refers to the maximum peak-to-peak delay change of the tested clock when compared with
the actual reference clock during the test.
9.8 Reliability
Table 9-11 lists the reliability specifications of the GTSOFTX3000.
Table 9-11 Reliability specifications of the GTSOFTX3000
Item
Specifications
System availability (A)
99.99953%
System MTBF
24 years (full configuration)
42 years (single subrack)
Mean time to repair (MTTR)
1 hour (excluding the preparation time)
DOWN duration
< 3 min/year
Board restart duration
< 10s (process)

< 150s (service board)
Process switchover duration
< 5s
Startup duration of a single subrack
Service boards starts from the Flash: < 159s
Service boards starts from the OMU that

resides in another subrack: < 279s
Service boards starts from the OMU that

resides in the subrack: < 419s
Restart duration of the entire system in

full configuration
Service boards starts from the Flash: < 249s
Service boards starts from the OMU: <15

minutes
Dual-homing switchover duration
< 3 minutes
9.9 Environmental Requirements

Table 9-12 lists the climate environment requirements of the GTSOFTX3000.
Issue 1.6 (2012-05-03)

71
Table 9-12 Climate environment requirements of the GTSOFTX3000 (operating for a long term)
Item
Specifications
Height above sea level
3000 m
Atmospheric pressure
70 kPa to 106 kPa
Temperature
+5C to +40C
Relative humidity
5% to 85%
Earthquake-proof performance
Richter scale: 7 to 9
Table 9-13 lists noise specifications of the GTSOFTX3000.

Table 9-13 Noise specifications of the GTSOFTX3000
Item
Specifications
NEBS
7.8 bels
ETSI
7.2 bels
9.10 EMC
Table 9-14 lists the electromagnetic compatibility (EMC) specifications that the
GTSOFTX3000 complies with.
Table 9-14 EMC specifications
Item
Specifications
EMC
ETSI EN 300 386V1.3.3: 2005AS/NZS CISPR 22: 2004
CISPR 22: 2002 CLASSA
EN 55022: 1998 + A1: 2000+A2: 2003 CLASSA
EN 55024:1998 + A1:2001 + A2:2003
FCC part 15:2006
VCCI V-3: 2006
CISPR 24: 1997
CENELEC EN 50121-4
EN/IEC 60950
UL60950
IEC60950
GR-1089
Safety
Issue 1.6 (2012-05-03)

72
9.11 Operating Environment

Table 9-15 lists the temperature and humidity requirements of the GTSOFTX3000.
Table 9-15 Temperature and humidity requirements of the GTSOFTX3000
Temperature
Relative humidity
Operating for a
Long Term
Operating for a
Short Term
Operating for a
Long Term
Operating for a Short

Term
+5C to + 40C
5C to + 50C
5% to 85%
5% to 95%
The measurement points of temperature and humidity of the GTSOFTX3000 refer to the values
measured 1.5 meters above the floor and 0.4 meter away from the front of the GTSOFTX3000 shelf
when there are no protection panels in the front and back of the GTSOFTX3000 shelf.
Short term means that the consecutive working duration is not more than 96 hours and that the
accumulated working duration of a year is not more than 15 days.
9.12 Interfaces and Standards

Table 9-16 lists the interfaces provided by the GTSOFTX3000 and the standards that the
GTSOFTX3000 complies with.
Table 9-16 Interfaces provided by the GTSOFTX3000 and standards that the GTSOFTX3000
complies with
Interface
Rate (bit/s)
Standard
E1
2.048 Mbit/s
ITU-T I.431
G.703
G.736
G.823
G.704
G.706
Q.703
G.732
ANSI T1.403
10/100
Base-T
Issue 1.6 (2012-05-03)
10/100 Mbit/s
IEEE802.3

73
Interface
Rate (bit/s)
Standard
ATM
155 Mbit/s
ITU-T GR-253-CORE
I.432
G.709
G.804
Q.921
T1.105
T1.627
I.610
GR-1248
BITS
2 MHz, 2 Mbit/s
G.703
GPS
1575.42 MHz
RS232
115200 bit/s
V.24/V.28
Issue 1.6 (2012-05-03)

74
eWSE GSM-R 5.0 GTSOFTX3000

Product Description
A Acronyms and Abbreviations
Acronyms and Abbreviations
Numeric
3GPP
3rd Generation Partnership Project
A
AIM
Application Interface Module
AIP
Advanced Intelligent Peripheral
ALU
Alarm Unit
ANSI
American National Standard Institute
AoC
Advice of Charge
AoCC
Advice of Charge (Charging)
AoCI
Advice of Charge (Information)
API
Application Programming Interface
APM
Application transport Mechanism
AS
Application Server
ASCII
American Standard Code for Information Interchange
ASIC
Application Specific Integrated Circuit
ASN.1
Abstract Syntax Notation One
ATM
Asynchronous Transfer Mode
B
BAM
Back Administration Module
BC
Bearer Control
BGCF
Breakout Gateway Control Function
BHCA
Busy Hour Call Attempt
Issue 1.6 (2012-05-03)

75

Product Description
BICC
Bearer Independent Call Control Protocol
BIOS
Basic Input/Output System
B-ISDN
Broadband Integrated Services Digital Networks
BITS
Building Integrated Timing Supply System
BNC
Backbone Network Connection
BOIC
Barring of Outgoing International Calls
BOIC-exHC
Barring of Outgoing International Calls except those directed to the Home PLMN Country
BS
Bearer Service
BSC
Base Station Controller
BSS
Base Station Subsystem
BSSAP
Base Station Subsystem Application Part
BSSAP+
Base Station Subsystem Application Part+
BSSMAP
Base Station Subsystem Management Application Part
C
CAC
Connection Admission Control
CAMEL
Customized Applications for Mobile network Enhanced Logic
CAP
CAMEL Application Part; Amplitude Phase modulation
CAPEX
CapEx
CC
Country Code
CCF
Call Control Function
CDR
Call Detail Record
CGI
Cell Global Identification
CFB
Call Forwarding Busy
CFNRc
Call Forwarding on mobile subscriber Not Reachable
CFNRy
Call Forwarding No Reply
CFU
Call Forward Unconditional
CHR
Call History Record
CI
Cell Identity
CIC
Circuit Identification Code
CIC
Call Instance Code
CLIP
Calling Line Identification Presentation
CLIR
Calling Line Identification Restriction
Issue 1.6 (2012-05-03)

76

Product Description
CN
Core Network
COLP
Connected Line Identification Presentation
COLR
Connected Line Identification Restriction
CPU
Center Processing Unit
CRBT
Color Ring Back Tone
CRC
Cyclic Redundancy Check
CS
Circuit Switched
CSCN
Circuit Switched Core Network
CSI
CAMEL Subscription Information
CUG
Closed User Group
CW
Call Waiting
D
DCH
Default Call Handling
DTMF
Dual Tone Multi Frequency
DB
Data Base
DNS
Domain Name Server
E
EC
Echo Cancelation
ECT
Explicit Call Transfer
EIRENE
European Integrated Railway Radio Enhanced Network
EFR
Enhanced full rate speech codec
eLDA
enhanced Location Dependent Addressing
EMC
Electromagnetic Compatibility
EMI
Electro Magnetic Interference
eMLPP
Multi-Level Precedence and Pre-emption service
EMS
Electromagnetic Shield
ESD
Electrostatic discharge
ETS
European Telecommunication Standards
ETSI
European Telecommunications Standards Institute
Issue 1.6 (2012-05-03)

77

Product Description
F
FCC
Federal Communications Commission
FE
Fast Ethernet
FFN
Follow-Me Function Node
FLASH
FLASH memory
FR
Full Rate
FPGA
Field Programmable Gate Array
FTAM
File Transfer Access and Management Protocol
FTP
File Transfer Protocol
G
GCI
Global Cell Identity
GCR
Group Call Register
GE
Gigabit Ethernet
GGSN
Gateway GPRS Support Node
GMLC
Gateway Mobile Location Center
GMSC
Gateway Mobile Switching Center
GPRS
General Packet Radio Service
GPS
Global Position System
GSM
Global System for Mobile Communications
gsmSCF
gsm Service Control Function
GT
Global Title
GUI
Graphic User Interface
GW
GateWay
H
H.248
H.248/MECAMGO protocol
HF
High Frequency
HLR
Home Location Register
HOLD
Call Hold
HTTP
Hypertext TransferProtocol
Issue 1.6 (2012-05-03)

78

Product Description
I
ICMP
Internet Control Message Protocol
ID
Identification/Identity
IEC
International Electrotechnical Commission
IEEE
Institute of Electrical and Electronics Engineers
IETF
Internet Engineering Task Force
IFM
IP Forwarding Module
iGWB
iGateway Bill
IMEI
International Mobile Equipment Identity
IMS
IP Multimedia Subsystem
IMSI
International Mobile Station Identity
IP
Internet Protocol
IP
Intelligent Peripherals
ISDN
Integrated Services Digital Network
ISO
International Standard Organization
ISUP
ISDN User Part
ITU
International Telecommunications Union
ITU-T
International Telecommunication Union - Telecommunication Standardization Sector
IUA
ISDN Q.921-User Adaptation Layer
Iu-Flex
Intra-domain connection of RAN nodes to multiple CN nodes
K
KVM
Keyboard & Video & Mouse
KVMS
Keyboard & Video & Mouse & Switcher
L
LAC
Location Area Code
LAI
Location Area Identity
LAN
Local Area Network
LCD
Liquid Crystal Display
LCS
Location services
Issue 1.6 (2012-05-03)

79

Product Description
M
M2UA
SS7 MTP2-User Adaptation Layer
M3UA
SS7 MTP3-User Adaptation Layer
MAC
Media Access Control
MAP
Mobile Application Part
Mc
Media Control
MGC
Media Gateway Controller
MGCF
Media Gateway Control Function
MGW
Media Gateway
MM
Mobility Management
MMI
Human-machine interfaces
MML
Man Machine Language
MO
Mobile Origination
MPTY
Multiparty Service
MRM
Mobile Radio modules
MS
Mobile Station
MSC
Mobile Service Switching Center
MSC Server
Mobile Switching Center Server
MSISDN
Mobile Station International ISDN Number
MSRN
Mobile Station Roaming Number
MSS
MSC Server
MTBF
Mean Time Between Failures
MTP
Message Transfer Part
MTP2
Message Transfer Part Level 2
MTP3
Message Transfer Part Level 3
MTP3B
Message transfer part (broadband)
MTTR
Mean time to repair
MVNO
Mobile Virtual Network Operator
MVPN
Mobile Virtual Private Network
N
NAT
Network Address Translation
NCH
Notification Channel
Issue 1.6 (2012-05-03)

80

Product Description
NDC
National Destination Code
NGN
Next Generation Network
NI
Network Indication
NIC
Network Interface Card
NSS
Network SubSystem
NTP
Network Time Protocol
O
ODB
Operator Determined Barring
O&M
Operation and Maintenance
OPC
Originating Point Code
OPEX
Operating Expenditure
OSI
Open System(s) Interconnection
OSTA
Open Standards Telecom Architecture
P
PBX
Private Branch Exchange
PLD
Programmable Logic Device
PLMN
Public Land Mobile Network
PS
Packet Switched
PSTN
Public Switched Telephone Network
Q
QoS
Quality of Service
R
RAN
Radio Access Network
RANAP
Radio Access Network Application Part
RBC
Radio Block Center
RBT
Ring Back Tone
RN
Roaming Number
RNC
Radio Network Controller
Issue 1.6 (2012-05-03)

81

Product Description
S
SCCP
Signaling Connection Control Part
SCF
Service Control Function
SCP
Service Control Point
S-CSCF
Serving CSCF
SCTP
Stream Control Transmission Protocol
SG
Signaling Gateway
SGSN
Serving GPRS Support Node
SIGTRAN
Signaling Transport
SIM
Subscriber Identity Module
SMC
Short Message Center
SRF
Specialized Resource Function
SS7
Signaling System No.7
SSF
Service Switching Function
SIP
Session Initiation Protocol
SSP
Service Switching Point
STM-1
SDH Transport Module -1
STP
Signaling Transfer Point
T
TCP
Transport Control Protocol
T-CSI
Terminated-CAMEL Subscription Information
TDM
Time Division Multiple
TMSC
Tandem Mobile Switching Center
TMSI
Temporary Mobile Subscriber Identity
TrFO
Transcoder Free Operation
TS
Technical Specification
TUP
Telephone User Part
U
UDP
User Data gram Protocol
UE
User Equipment
UMG
Universal Media Gateway
Issue 1.6 (2012-05-03)

82

Product Description
UMTS
Universal Mobile Telecommunications System
USSD
Unstructured Supplementary Service Data
UTRAN
UMTS Terrestrial Radio Access Network
UUS
User to User Signaling
V
VBS
Voice Broadcast Service
VDB
VLR Database
VGCS
Voice Group Call Service
VLAN
Virtual Local Area Network
VLR
Visitor Location Register
VMGW
Virtual Media Gateway
VMSC
Visited Mobile Switching Center
VoIP
Voice over IP
VPN
Virtual Private Network
W
WAN
Wide Area Network
WCDMA
Wideband Code Division Multiple Access
WIN
Wireless Intelligent Network
X
XPTU
X Protocol Transfer Unit
Issue 1.6 (2012-05-03)

83

Railway Operational Communication Solution GSM-R 5.0 GTSOFTX3000 Product Description V1.0 (20120925)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Railway Operational Communication Solution GSM-R 5.0 GTSOFTX3000 Product Description V1.0 (20120925)

Uploaded by

Copyright:

Available Formats

eWSE GSM-R 5.

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

About This Document

About This Document

Issue V1.1 (2012-05-03)

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

2 Product Features ............................................................................................................................ 8

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

2.2.2 Excellent Voice Quality......................................................................................................................... 10

3 Services and Functions ............................................................................................................... 15

5 Interfaces and Protocols ............................................................................................................. 43

6 Networking and Application .................................................................................................... 50

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

7 Operation and Maintenance ..................................................................................................... 54

9 Technical Specifications ............................................................................................................ 66

A Acronyms and Abbreviations .................................................................................................. 75

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

1.2 Huawei GSM-R Solution

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

Figure 1-1 Networking of Huawei GSM-R solution

MGW: Media Gateway

BSS: Base Station Subsystem

VLR: Visitor Location Register

FFN: Follow-Me function node

GCR: Group call register

MS: Mobile Station

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

Wireless network resources management

Cell configuration data management

Conversion between radio and wired signal

Radio channel encryption

1.2.13 Mobile Terminals

General Purpose Handset (GPH)

Operational Purpose Handset (OPH)

Operational Purpose Handset of Shunting (OPS)

MMI (Human-machine interfaces)

MRM (mobile Radio modules)

Issue 1.6 (2012-05-03)

Huawei Proprietary and Confidential

eWSE GSM-R 5.0 GTSOFTX3000 Product Description

1.3 GTSOFTX3000 Orientation