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.

Issue 1.6 (2012-05-03) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i

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: [email protected]

eWSE GSM-R 5.0 GTSOFTX3000 Product Description About This Document



ii

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.

eWSE GSM-R 5.0 GTSOFTX3000 Product Description Contents



iii

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




iv

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




v

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

eWSE GSM-R 5.0 GTSOFTX3000 Product Description 1 Overview



1

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 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.




2

Figure 1-1 Networking of Huawei GSM-R solution

AC Server: Acknowledge

Center Server

MGW: Media Gateway BSS: Base Station Subsystem

EIR: Equipment Identification

Register

VLR: Visitor Location Register FFN: Follow-Me function node

HLR: Home Location Register GCR: Group call register MS: Mobile Station

MSC: Mobile Switching

Center

OMC: Operation & Maintenance

Center

PBX: Private Branch Exchange

SCP: Service Control Point GGSN: Gateway GPRS Support

Node

SGSN: Serving GPRS Support

Node

IWF: Interworking Function PSTN: Public Switched Telephone

Network

AUC: Authentication Center

ISS: Integrated Service Server IP PBX: PBX that supports Simple

Internet Protocol (SIP)

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.




3

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.




4

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




5

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




6

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.




7

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.

eWSE GSM-R 5.0 GTSOFTX3000 Product Description 2 Product Features



8

2 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.




9

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.




10

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:

Electrical echo cancelation (EEC): The EEC function eliminates electrical echoes caused

by 2-wire/4-wire conversion on the PSTN side.




11

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.




12

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




13

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.




14

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

eWSE GSM-R 5.0 GTSOFTX3000 Product Description 3 Services and Functions



15

3 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.




16

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.




17

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.




18

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




19

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:

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.




20

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:

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.




21

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




22

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




23

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.




24

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.




25

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.




26


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.




27


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)

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.




28


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.




29


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 gr

railway operational communication solution gsm-r 5.0 gtsoftx3000 product description v1.0(20120925)

Documents

huawei trademarks

huawei proprietary

document issues

document summary

latest document issue

huawei gsmr solution

huawei industrial base

product features