Beruflich Dokumente
Kultur Dokumente
Product Description
Issue 1.0
Date 2013-03-07
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.
Website: http://www.huawei.com
Email: support@huawei.com
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.
Contents
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
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
1 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.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.
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.
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
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
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.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.
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.
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."
System Reliability
Table 2-1 describes the solutions that the GTSOFTX3000 uses to achieve 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."
VQE
The VQE feature improves voice quality by providing the following functions:
Electrical echo cancelation (EEC): The EEC function eliminates electrical echoes caused
by 2-wire/4-wire conversion on the PSTN side.
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.
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.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.
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.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.
Service Description
Type
GSM bearer The GTSOFTX3000 supports the BS20 asynchronous transparent and
services 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 The GTSOFTX3000 supports the BS20 asynchronous non-transparent
services bearer services and BS30 synchronous transparent bearer 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.
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.
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.
Call control
SSP
Handovers
Charging
CAMEL services
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:
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.
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 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.
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.
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
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.
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 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.
The procedure for subsequent handover to a third party (MSCb') is as follows:
MSCb responds to the handover request received from the BSC.
MSCb sends the "subsequent handover to the third party (MSCb')" request to MSCa by
using MAP signaling.
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.
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.
SCP
SS7 signaling
network
SSP SSP
SS7
GMSC/SSP GMSC/SSP
VMSC/ VMSC/ VMSC/ VMSC/
SSP SSP SSP SSP
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.
4 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.
Backplane
IPMB
UPB/ UPB/ UPB/ UPB/ UPB/ UPB/
USI USI USI USI USI USI BASE
NOTE
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.
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
IEC60297-2, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
2:Cabinets and pitches of rack structures
IEC60297-3, Dimensions of mechanical structures of the 482.6 mm (19 in) series Part
3:Subracks and associated plug-in units
Cabinet Configuration
In typical configuration, the GTSOFTX3000 has one cabinet with one subrack. Figure 4-3
shows the cabinet configuration.
Subrack 0 (14U)
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.
2
3
5
1. Board slots 2. Fan box 1 3. Fan box 2
4. Air intake vent 5. Slots for the SMMs
5
6
7
1. Grounding points of the subrack 2. Upper air exhaust vent 3. Slots for interface boards
4. Lower air exhaust vent 5 and 6 Power entry modules (PEMs) 7. Slots for the SDMs
Boards
Table 4-1 lists the boards configured in a subrack.
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.
Middleware
Operating system
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.
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.
Figure 4-7 Hierarchical relationships between the OMU server software, operating system, and
database
Application layer
Operating system
layer
Database
Linux
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
Equipment management
Alarm management
Call and signaling tracing
CDR management
Report generation
This chapter describes physical interfaces and protocol interfaces provided by the
GTSOFTX3000.
UPB COM serial Used for local The COM serial port on the UPB
port commissioning 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 This port complies with USB2.0, which is
connection backward compatible with USB1.1.
SWU BMC COM Used for This port complies with RS232 and supports
serial port loading or 115,200 bit/s baud rate. It is connected to an
upgrading the RJ45 connector. This port does not have an
BMC software indicator.
USI GE port Used to connect to the This port is an RJ45 port that
Ethernet supports 10 Mbit/s, 100 Mbit/s, or
1,000 Mbit/s Base-T
auto-negotiation.
VGA Used to connect to the This port supports a monitor with
monitor 1024 x 768 or higher SVGA
resolution.
USB port Used to connect to the This port complies with USB2.0.
mouse and keyboard
SWI Base GE port Used to connect to the The port is a 4-channel Gigabit
Base plane 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 Used to connect to the The port is a 4-channel Gigabit
port Fabric plane Ethernet port, which supports 10
Mbit/s, 100 Mbit/s, and 1,000
Mbit/s Base-T auto-negotiation and
has two indicators.
ETIA0 E1/T1 port Each ETMA daughter The ETIA0 has two ETMA
board provides a daughter boards configured to
16-channel E1/T1 provide two DB-78 ports. From top
port. to bottom, the two daughter boards
are marked E1/T1_0-15 and
E1/T1_16-31.
8 kHz clock Used to transmit the The board provides two RJ45 clock
port 8-kHz clock signals ports, which are marked with
extracted from the E1 8K_OUT0 and 8K_OUT1 from top
line to the active and to bottom.
standby SWIA1
boards
ETIA2 E1/T1 port Each ETMA daughter The ETIA2 board has an ETMA
board provides a daughter board configured to
16-channel E1/T1 provide one DB-78 port. The
port, and each GE daughter board is marked with
daughter board E1/T1_0-15.
provides two Ethernet
ports.
8 kHz clock Used to transmit the The board provides two RJ45 clock
port 8-kHz clock signals ports, which are marked with
extracted from the E1 8K_OUT0 and 8K_OUT1 from top
line to the active and to bottom.
standby SWIA1
boards
GE port Each ETMA daughter The board has one external GE
board provides a daughter board configured to
16-channel E1/T1 provide two RJ45 Ethernet ports
port, and each GE which support 10 Mbit/s, 100
daughter board Mbit/s, and 1,000 Mbit/s Base-T
provides two Ethernet auto-negotiation. From top to
ports. bottom, the two Ethernet ports on
the daughter board are marked
LAN0 and LAN1.
BSC: Base Station GMLC: Gateway Mobile Location HLR: Home Location Register
Controller Center
BC: Billing Center SCP: Service Control Point SMC: Short Message Center
SG: Signaling Gateway SGSN: Serving GPRS Support Node AC Server: Acknowledgement
Center Server
MGW: Media Gateway PLMN: Public Land Mobile Network FFN: Follow-Me Function Node
PSTN: Public Switched RBC: Radio Block Center ISS: Integrated Service Server
Telephone Network
Table 5-3 describes the interfaces and protocols supported by 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:
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.
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
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.
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.
MS
PSTN/PBX
MS BTS 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.
BSC
BSC
FE
E1
POS/E1
POS/E1
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.
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.
iManager
BC
M2000
GTSOFTX 3000
HUB
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.
8 Reliability
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
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.
Data Security
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.
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.
EMS
LAN Maintenance
terminal
switch
LAN
BC
switch
S S
U U U U U U U U
S W W
S S S S S S S S S
M I I
I I I I I I I I M
M A A
1 1 7 7 1 1 1 1 M
0 0
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
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.
9 Technical Specifications
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
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 128
a WBSG process
Maximum 2-Mbit/s MTP links supported by a 8
WBSG process
Maximum SCTP links supported by a WBSG 256
process
Maximum rate of packet dispatching by a 128,000 packets/second
WIFM process
Clock stratum Stratum-2 A
Item Specifications
Item Specifications
Maximum length of a number for analysis 32 digits
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
Table 9-6 Specifications of call setup duration (for 95% of the calls)
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%
Item Specifications
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.
NOTE
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.
Item Specifications
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
Item Specifications
9.10 EMC
Table 9-14 lists the electromagnetic compatibility (EMC) specifications that the
GTSOFTX3000 complies with.
Item Specifications
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.
Table 9-16 Interfaces provided by the GTSOFTX3000 and standards that the GTSOFTX3000
complies with
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
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
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
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
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
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
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
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
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