MSOFTX3000V100R008 Additional Feature Description V1.0

Doc. code

MSOFTX3000V100R008

Additional Feature Description

Issue 1.0

Date 2010-06-04

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. 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 commercial contract made

between Huawei and the customer. All or partial products, services and features described in this

document may not be within the purchased scope or the usage scope. Unless otherwise agreed by

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 the 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]

MSOFTX3000V100R008

Additional Feature

Description

Issue 1.0 (2010-06-04) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

Page 3 of 131

Contents

1 Additional Features ............................................................................................................6

1.1 WRFD-010600 UMTS bearer services ................................................................................................6

1.2 WRFD-020700 Closed User Group (CUG) .........................................................................................7

1.3 WRFD-020800 Explicit call transfer (ECT) ........................................................................................7

1.4 WRFD-020900 Enhanced Multi-Level Precedence and Pre-emption service(EMLPP) ......................8

1.5 WRFD-021000 Follow Me ................................................................................................................10

1.6 WRFD-021100 Supplementary service restriction.............................................................................13

1.7 WRFD-040400 Operator determinate call purge (ODR) ...................................................................14

1.8 WRFD-040500 Optimal Routing (OR) ..............................................................................................15

1.9 WRFD-040600 Black and white lists.................................................................................................16

1.10 WRFD-040900 Notification of Failure to Multimedia Calls (NFMC).............................................17

1.11 WRFD-041000 USSD Query for Cell-Based Charging ...................................................................18

1.12 WRFD-042100 North American Equal Access (NAEA) .................................................................19

1.13 WRFD-042300 Enhanced roaming restriction .................................................................................20

1.14 WRFD-042400 Enhanced MSRN allocation ...................................................................................21

1.15 WRFD-042700 Alternate Line Selection (ALS) ..............................................................................22

1.16 WRFD-042800 Dual-MSISDN for multimedia and speech telephony ............................................23

1.17 WRFD-043700 MAP Bypass ...........................................................................................................24

1.18 WRFD-043800 Malicious Call Trace (MCT) ..................................................................................25

1.19 WRFD-046000 E911........................................................................................................................25

1.20 WRFD-048000 Text Telephony (TTY) ............................................................................................28

1.21 WRFD-050500 GERAN/UTRAN Access Restriction (ARD) .........................................................29

1.22 WRFD-050600 Shared Network Area in Connected Mode (SNA)..................................................30

1.23 WRFD-050700 Local-based service restriction ...............................................................................31

1.24 WRFD-050900 Roaming restriction for CAMEL............................................................................32

1.25 WRFD-080700 Signaling handover .................................................................................................32

1.26 WRFD-080900 Load based handover ..............................................................................................33

1.27 WRFD-091200 Announcement to abnormal IN users .....................................................................34

1.28 WRFD-091300 DTMF sending restriction ......................................................................................36

1.29 WRFD-091500 Call in Progress Tone..............................................................................................37

1.30 WRFD-100700 Hot Billing..............................................................................................................38

1.31 WRFD-100800 Advice of Charge Charging/Information (AOCI/AOCC).......................................39

MSOFTX3000V100R008

Additional Feature

Description



Page 4 of 131

1.32 WRFD-101100 ISDN CDR..............................................................................................................40

1.33 WRFD-101200 Cell-based charging ................................................................................................41

1.34 WRFD-101700 Whether to generate the SMS CDRs is configurable based on the attribute (national

or international) of the SMC. ...................................................................................................................41

1.35 WRFD-110500 R2 signaling (No.1 signaling in China) ..................................................................43

1.36 WRFD-111200 BSSAP+ protocol (Gs interface).............................................................................44

1.37 WRFD-111300 Location service (LCS) (Lg interface) ....................................................................45

1.38 WRFD-111400 CHECK IMEI and F interface ................................................................................46

1.39 WRFD-111500 MAP Policing .........................................................................................................48

1.40 WRFD-111600 SCCP Policing ........................................................................................................49

1.41 WRFD-111800 MAP AC version configured...................................................................................50

1.42 WRFD-112100 SCTP multi-homing................................................................................................51

1.43 WRFD-112300 ISUP for international interconnections..................................................................52

1.44 WRFD-112500 MTP policing ..........................................................................................................53

1.45 WRFD-112600 ANSI ISUP .............................................................................................................54

1.46 WRFD-119800 SIP-I Based Nc .......................................................................................................55

1.47 WRFD-121600 Malicious SMS warning .........................................................................................60

1.48 WRFD-121700 Union trace .............................................................................................................61

1.49 WRFD-131600 Special Number Matching ......................................................................................62

1.50 WRFD-131700 Routing Based on Time Section .............................................................................63

1.51 WRFD-131900 Call loop control .....................................................................................................63

1.52 WRFD-132200 Low cost routing.....................................................................................................66

1.53 WRFD-140100 Multiple signaling points ........................................................................................68

1.54 WRFD-140200 TDM 2M signaling link ..........................................................................................68

1.55 WRFD-140300 Embedded STP function .........................................................................................69

1.56 WRFD-140800 A interface Satellite Transmission Mode ................................................................69

1.57 WRFD-141000 Mc interface Satellite Transmission Mode .............................................................69

1.58 WRFD-141100 Inverse Multiplexing ATM(IMA,ATM2M) ............................................................69

1.59 WRFD-141200 T1 Digital Trunk (ISUP/PRA) ................................................................................69

1.60 WRFD-141300 Signaling SSP (LOOPBACK) ................................................................................69

1.61 WRFD-141400 Route between MGWs in one MSC .......................................................................69

1.62 WRFD-141500 Connecting MGWs in one MSC by transit switch..................................................69

1.63 WRFD-141605 Manual load balancing............................................................................................69

1.64 WRFD-141606 Call termination solution ........................................................................................69

1.65 WRFD-142500 Multi-Operator Core Network ................................................................................69

1.66 WRFD-150400 OVERLAY SSP......................................................................................................69

1.67 WRFD-160200 Equivalent PLMN (ePLMN) ..................................................................................69

1.68 WRFD-161800 Dialing without NDC..............................................................................................69

1.69 WRFD-161900 Call reestablishment ...............................................................................................69

1.70 WRFD-162000 Pre-paging ..............................................................................................................69

1.71 WRFD-162100 Enhanced DCH.......................................................................................................69

MSOFTX3000V100R008

Additional Feature

Description



Page 5 of 131

1.72 WRFD-162200 Continuity check.....................................................................................................69

1.73 WRFD-162300 Assign half rate channel by user priority ................................................................69

1.74 WRFD-162400 Enhanced subscriber category g .............................................................................69

1.75 WRFD-162500 Daylight saving time...............................................................................................69

1.76 WRFD-162600 Mobile Virtual Network Operator (MVNO)...........................................................69

1.77 WRFD-162700 Multiple time zones ................................................................................................69

1.78 WRFD-162900 Camel trigger based on INClassMark.....................................................................69

1.79 WRFD-163100 User differentiated service ......................................................................................69

1.80 WRFD-163200 Service based handover ..........................................................................................69

1.81 WRFD-163400 Update Network Indicator and Time Zone (NITZ).................................................69

1.82 WRFD-163400 Paging based on service type..................................................................................69

1.83 WRFD-163700 Dual Transfer Mode (DTM) ...................................................................................69

1.84 WRFD-164100 REL reroute ............................................................................................................69

1.85 WRFD-164200 BICC bearer redirection..........................................................................................69

1.86 WRFD-164300 Anti-Cheat (to restrict forwarding and the number of ECTs) .................................69

1.87 WRFD-164900 TDM circuit selection based on bearer capability of circuits .................................69

1.88 WRFD-165000 TDM&IP dual bearer ..............................................................................................69

1.89 WRFD-165300 Batch conversion of calling numbers .....................................................................69

1.90 WRFD-165500 Wideband AMR......................................................................................................69

1.91 WRFD-165800 Forced call release upon dialing back.....................................................................69

1.92 WRFD-168100 IP bearer AutoTest ..................................................................................................69

1.93 WRFD-168200 Time-Based Service................................................................................................69

1.94 WRFD-168500 BICC fail re-route...................................................................................................69

1.95 WRFD-168600 IP QoS Monitor ......................................................................................................69

1.96 WRFD-168700 Support MediaX3600 services................................................................................69

1.97 WRFD-168800 Export user number base on cell.............................................................................69

1.98 WRFD-168900 Support generic number's length exceeding ...........................................................69

1.99 WRFD-169000 Query detail information of a call...........................................................................69

1.100 WRFD-169700 Support for High Compression Rate of Bearer Transmission...............................69

1.101 WRFD-190400 Dual BAM Backup ...............................................................................................69

1.102 WRFD-200300 TDM redundancy for IP congestion .....................................................................69

2 Acronyms and Abbreviations.........................................................................................69

MSOFTX3000V100R008

Additional Feature

Description



Page 6 of 131

1 Additional Features This Document is used for V100R008 Version.

1.1 WRFD-010600 UMTS bearer services

Availability

This feature is introduced in V100R002 Version.

Summary

Huawei MSOFTX3000 supports the BS20 and BS30 bearer services.

Benefits � For carriers

Providing the UMTS CS data service and video phone service

� For subscribers

Enjoying the GSM CS data service and video phone service

Description

Huawei MSOFTX3000 supports the following BS20 and BS30 bearer services:

� WMFD-010602 Non-transparent asynchronous bearer services-3.1kHz audio, and

under the UMTS, Fixed Network User Rate is 9.6/14.4/19.2/28.8 kbit/s.

� WMFD-010603 Non-transparent asynchronous bearer services-UDI, and under the

UMTS, the rate is 9.6/14.4/19.2/28.8 kbit/s, and the rate adaptation is V.110/V.120.

� WMFD-010605 Transparent synchronous bearer services-UDI, Fixed Network

User Rate is 64 kbit/s.

� WMFD-010606 Transparent synchronous bearer services-multimedia, Fixed

Network User Rate is 64 kbit/s, the rate adaptation is H223 and H245.

MSOFTX3000V100R008

Additional Feature

Description



Page 7 of 131

Enhancement

None.

Dependency

Configuration of IWF equipment.

1.2 WRFD-020700 Closed User Group (CUG)

Availability


Summary

One or several users with the same attributes form into a group, so the members have

the same call attribute. CUG service is applicable for a small group with several

members or a large enterprise with thousands of subscribers.


− Enhancing service capability

− Attracting more group subscribers

� For subscribers

The group members enjoy flexible charging preferential.

Description

One or several users with the same attributes form into a group, so the members have

the same call attribute. CUG service is applicable for a small group with several

members or a large enterprise with thousands of subscribers.

Enhancement

None.

Dependency

None.

1.3 WRFD-020800 Explicit call transfer (ECT)

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 8 of 131

Summary

ECT is the abbreviation of explicit call transfer.


This function helps carriers to:

− Provide various services.

− Attract more subscribers.

− Improve the competition.

� For subscribers

This function helps a subscriber to exit a call after connecting other two

subscribers that were in conversation with the subscriber.

Description

The ECT service functions in this way: Mobile subscriber A is in two calls. A connects

B with C though the ECT operation. Then A exits from the call. B and C can be local

mobile subscribers, mobile subscribers in other office, or fixed line subscribers. A is

required to keep two calls at the same time. Therefore, A must subscribe to the HOLD

service. Before the ECT is originated, the A-B call and the A-C call can be in

conversation state at the same time, or one of the calls is in conversation state, the

other is in alerting state.

If A is a subscriber that subscribes to the ring back tone service, and the A-B call is in

conversation state, A can originate the ECT to realize the call between B and C,

irrespective of whether A acts as a caller or a callee.

Assume that the A-B call is in conversation state, C has subscribed to the ring back

tone service, and A dials C. If A originates the ECT when C is in alerting state, B can

hear the ring back tone of C.

Enhancement

None.

Dependency

None.

1.4 WRFD-020900 Enhanced Multi-Level Precedence and Pre-emption service(EMLPP)

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 9 of 131

Summary

The enhanced Multi-Level Precedence and Pre-emption (eMLPP) service is a

supplementary service that divides calls into different levels and grants higher priority

to high-level calls.


The carrier can divide subscribers into different levels based on the network

operation policy. Thus, the carrier can provide differentiated services for

subscribers with different requirements.

− Resource contention

When the resources are insufficient, the subscribers configured with

pre-emption capability can contend for the resources used by other subscribers.

In this process, the system first contends for the resources used by the

subscribers with the lowest priority level.

− Queuing

When the resources are insufficient, the system can also queue certain

subscribers besides contending for resources. The FIFO principle is applied

when the connections are queued. In addition, the queuing time of a

connection with high priority is shorter than that of a connection with lower

priority.

� For subscribers

The subscribers with different eMLPP precedence levels can enjoy services of

different levels.

Description

The enhanced Multi-Level Precedence and Pre-emption (eMLPP) service is a

supplementary service that divides calls into different levels and grants higher priority

to high-level calls. For example, circuit contention and quick connection can be

enabled for these calls. When the network resources are sufficient, the advantages of

the eMLPP service, such as the outstanding pre-emption capability, are not so obvious.

When the network resources are insufficient, the advantages of the eMLPP service

become significant. It helps to bring more profits for the carrier.

In the eMLPP service, each subscriber has a specific authority that determines the

available priority levels of each call of the subscriber. Calls are given different priority

when contending for network resources. Calls of different priority levels can choose

different call setup modes.

The eMLPP service includes:

� Quick call setup

� Queuing and contention.

Quick call setup: Calls of all priority levels can choose the quick call setup flow. In the

quick call setup flow, the authentication and encryption are skipped to reduce the time

required for call setup.

MSOFTX3000V100R008

Additional Feature

Description



Page 10 of 131

Queuing and contention: When the network resources such as the circuits are

insufficient, calls of high priority levels are not released and are queued first, and can

contend for resources of the calls of low priority levels.

Enhancement

None.

Dependency

The BSC/RNC, MS/UE, and HLR must support the eMLPP service.

1.5 WRFD-021000 Follow Me

Availability


Summary

The functionality of the Follow Me service is equivalent to the functionality of the

Call Forwarding Unconditional service. The difference is that the call forwarding is

controlled by the initiating subscriber (forwarded-to subscriber) during the Follow Me

service whereas controlled by the forward subscriber during the Call Forwarding

Unconditional service. The Follow Me service is typically delivered to railway hotline

service staff who work on shifts.


This function adds values to carriers and helps carriers provide feature services to

enterprise and private-network subscribers.

� For subscribers

− This function simplifies subscribers' operations by defining a functional

number.

− Subscribers can reach the currently on-duty staff simply by dialing a uniform

number, without a need to know the MSISDN of every staff working on shifts.

Description

The Follow Me service is also called functional addressing. This service enables you

to define a functional number for a particular service group in a certain service area

and to have all calls destined for the functional number forwarded to the on-duty staff.

(The functional number identifies the number of an on-duty staff instead of an actual

terminal number.) The functional number is bound to the MSISDN of the staff

currently on duty, thus establishing a relation between the functional number and the

actual subscriber. Each time there is a shift change, the MSISDN to which the

functional number is bound changes. The functional number, however, remains the

MSOFTX3000V100R008

Additional Feature

Description



Page 11 of 131

same. In this way, your customers can dial the functional number to reach the on-duty

staff, without a need to know the shift change.

In the functional addressing service, each MSISDN is bound to multiple functional

numbers, but a subscriber can be assigned only one functional number at a time. The

authorized subscriber can bind the MSISDN to a functional number or cancel the bind

operation through USSD operations. The relations between functional numbers and

actual subscriber numbers are stored in the Home Location Register (HLR) or

Follow-Me Function Node (FFN).

The following concepts are defined in the Follow Me service:

� Remote number

It is a number defined by carriers. It is also called functional number when being used

as the remote subscriber during an FM call. It is generally a virtual subscriber. In some

special cases, a remote subscriber can be a mobile subscriber. A remote subscriber can

be associated with an initiating subscriber. The calls to the remote subscriber are

forwarded to the corresponding initiating subscriber.

� Remote party

It refers to a functional number associated with the initiating subscriber. Generally, it is

a virtual number rather than an actual subscriber. If a remote party refers to a GSM

subscriber in the PLMN, the remote number is the MSISDN of the remote party.

� Initiating subscriber

It refers to a mobile subscriber who modifies the Follow Me data of a remote party so

that the call destined for the remote party can be forwarded to its own. An initiating

subscriber can associate with several remote subscribers. That is, the calls destined for

the remote subscribers can be forwarded to the same initiating subscriber.

� Initiating number

It refers to the number (the MSISDN of the initiating subscriber) to which incoming

calls destined for the remote party are forwarded.

The Follow Me function implements functional addressing of voice service, data

services, and SMMO services. The following shows the message flow of the Follow

Me service:

MSOFTX3000V100R008

Additional Feature

Description



Page 12 of 131

The flow is described as follows:

(1) The (G)MSC server receives a call destined for the functional number.

(2) The (G)MSC server analyzes the functional number and then sends the SRI

request to the HLR to obtain the routing information.

(3) After identifying the functional number, the HLR queries the internal database for

the initiating number and then sends the SRI_ACK message carrying the

information about the registered functional number to the (G)MSC server.

(4) The (G)MSC server originates a call destined for the initiating number.

The following shows the forwarding flow of the Follow Me service in the case of

SMMO:

The flow is described as follows:

(1) The MSC server receives an MO short message sent by the local subscriber to the

functional number.

(2) After identifying that the target object is a functional number, the MSC server

sends an SRI message to the HLR to obtain the Follow Me information of the

callee.

(3) After identifying the functional number, the HLR queries the internal database for

the initiating number and then sends the SRI_ACK message carrying the

information about the registered functional number to the MSC server.

After receiving the initiating number, the MSC server replaces the called number in

the short message with the initiating number and then sends the short message to the

short message center (SMC).

Enhancement

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 13 of 131

Dependency

The HLR should support the FFN function and the subscription of the Follow Me

service. In addition, it should be able to send the Follow Me subscription information

to the (G)MSC server through an SRI message.

1.6 WRFD-021100 Supplementary service restriction

Availability


Summary

The function is used to restrict a special number being HOLD, passively being added

to the MPTY, or passively serving as an ECT diverting party. It aims to prevent illegal

subscribers from deceiving by using the network supplementary service function. For

example, cheater A dials the number of cheatee B who has a rechargeable card, holds

B, and dials 0850. After dialing 0850, A enters his own MSISDN according to the

voice prompt first, and then sets up the MPTY. B listens to the alert tone, requiring

him to enter the information about the rechargeable card. Thus when B completes the

operation, the money in the card is put on the account of A. This function can restrict

this deceiving method, greatly reducing the probability of subscribers being deceived.

It only supports the restriction function of supplementary services HOLD, MPTY and

ECT.


The supplementary service restriction function makes carriers restrict malicious

subscribers to deceive through supplementary services provided by the network,

thus improving subscriber satisfaction.

� For subscribers

It greatly reduces the probability of subscribers being deceived.

Description

In the service, you can set self-defined properties 36, 37 and 38 for special numbers by

setting the subscriber service property data to restrict HOLD, MPTY, and ECT

respectively. When a calling subscriber calls a special number, because the subscriber

service property data is matched, and restricting HOLD, MPTY, and ECT is set, the

calling subscriber cannot perform the operation of HOLD, MPTY, and ECT.

The function supports subscribers to directly dial some specific numbers which restrict

the three supplementary services such as HOLD, MPTY, and ECT.

� A calls B, or B calls A, and A originates call hold after call completion.

If B is a restricted subscriber, the HOLD operation of A to B fails.

� A calls B, and A originates call hold after call completion.

MSOFTX3000V100R008

Additional Feature

Description



Page 14 of 131

A calls C, and A originates the MPTY or ECT service after call completion.

If B is not a restricted subscriber, while C is a restricted subscriber, the MPTY or ECT

service originated by A fails after C is put through.

� B calls A, and A originates the call hold after call completion.

A calls C, and A originates the MPTY or ECT service after call completion.

If C is a restricted subscriber, the multi-connection request of A fails.

� A calls B, and A originates call hold after call completion.

C calls A, and A originates the MPTY or ECT service after call completion.

If C is a restricted subscriber, the multi-connection request of A fails.

The MPTY also contains adding new subscribers to the existing meeting.

Through the forwarding mode, the function supports transferring subscribers to some

specific numbers which restrict the three supplementary services such as HOLD,

MPTY, and ECT.

When subscribers are transferred to some specific numbers such as 0850 through the

forwarding mode, the three supplementary services such as HOLD, MPTY, and ECT

can be transplanted. That is, restrict the function of HOLD, MPTY or ECT according

to the latest put-through numbers, but not the intermediate numbers of subscribers. In

which, the forwarding contains intra-office forwarding and other office forwarding.

In addition, the function of whether to restrict these supplementary services is related

to calls formed by subscriber dialing some specific numbers. When these calls are

released, it is not required to restrict the function. For example, subscriber A dials and

holds B who is not a restricted subscriber, and then dials C who is a restricted

subscriber. At this time, it is not allowable for A to originate HOLD, MPTY or ECT.

When A releases the call between A and C, and then dials D who is not a restricted

subscriber, A can originate HOLD, MPTY or ECT after call completion.

Enhancement

None.

Dependency

Configuration of IWF equipment.

1.7 WRFD-040400 Operator determinate call purge (ODR)

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 15 of 131

Summary

The operators can forcedly disconnect a call being in conversation at any time.


− Forcedly disconnect the malicious long-time conversation of fraud subscribers

to reduce charging loss.

− Forcedly disconnect the long-time conversation because of network

abnormality to reduce charging variance as possible and charging loss of end

subscriber arising thereof.

� For subscribers

Avoid the calls from being embezzled maliciously to reduce charging loss.

Description

The operators can forcedly disconnect a call being in conversation at any time.

Enhancement

None.

Dependency

None.

1.8 WRFD-040500 Optimal Routing (OR)

Availability


Summary

Optimal Routing (OR) is a network optimization strategy of carriers. Its description is

available in 3GPP TS 23.079. Supporting OR can reduce alternate speech path routing

of some calls to save the network resource and reduce the operation cost.


OR can help save the operation cost. As the operation strategy, OR also help to

win more subscribers by reducing the call costs of subscribers using the OR.

� For subscribers

Subscribers can save call costs if carriers reduce the call costs of subscribers

using the OR.

MSOFTX3000V100R008

Additional Feature

Description



Page 16 of 131

Description

Through negotiation and cooperation between carriers, three types of OR call

procedures can be supported:

� Basic OR call: The GMSCA belonging to operator A can directly obtain the roaming

number from the HLRB belonging to operator B and directly route the call to the

VMSCB of the roaming subscriber, instead of routing the subscriber number to

GMSCB for processing.

� Early forwarding OR call: If early forwarding occurs in the call upon the query of

basic optimal route, early forwarding can be processing on the GMSCA so far the

corresponding early forwarding charging principles are met.

Late forwarding OR call: If late forwarding occurs in the call on the VMSCB, and the

corresponding early forwarding charging principles are met, late forwarding procedure

can be carried out on the GMSCA that obtains the roaming number to reduce alternate

speech path routing when the call is transited through the VMSCB.

Enhancement

None.

Dependency

Negotiation and cooperation between carriers and support of the network entity HLR

are required.

1.9 WRFD-040600 Black and white lists

Availability


Summary

The black and white lists function restricts calls based on the calling number and/or

the source of the calling number and the number of the callee. It is mainly used by the

GMSCs to restrict inter-network calls.


A carrier can determine whether to allow or restrict the connection of toll calls

from the network of other carriers.

The calls with incorrect calling numbers can be intercepted to avoid billing

errors.

� For subscribers

None

MSOFTX3000V100R008

Additional Feature

Description



Page 17 of 131

Description

At present, the function is actually an enhanced call barring function. You can set the

caller or the callee to the blacklist group, white list group, or an ordinary group

through data configuration. The calls from subscribers in the white list group to

subscribers in other groups are allowed. The calls from subscribers in the blacklist

group to subscribers in groups other than the white list group are restricted. Whether

the calls between subscribers in ordinary groups are restricted is determined by the

inter-group relationships.

This function includes two parts: caller discrimination and black and white lists. In an

incoming trunk group call, the discrimination group number and call barring group

number of the caller can be configured for the trunk group. If the discrimination group

number of the caller is valid, the caller discrimination can be performed with the

discrimination result as direct call barring, call barring based on the maximum or

minimum number length, or attribute (call barring group number of the caller)

modification. After the caller discrimination is performed, the final call barring group

of the caller can be determined if no call barring is implemented. The call barring

group of the callee can also be determined through data configuration. If the black and

white lists relationship between the caller and the callee cannot be determined, the

configured inter-group relationship determines whether the call is to be released.

By performing the preceding steps, you can include the caller and callee of a trunk

incoming call in the black and white lists.

An MSC Server can support up to 30,000 black lists, 30,000 white lists, and 4,000

ordinary lists.

Enhancement

None.

Dependency

None..

1.10 WRFD-040900 Notification of Failure to Multimedia Calls (NFMC)

Availability


Summary

If the calling party originates an unsuccessful VP call, a "USSD" format notice will be

returned immediately to the calling party. Because the call originated by calling party

is video one, it is impossible to play announcement directly. The service will provide a

"USSD" to perfect subscriber interface dramatically once the call is not connected. If

multimedia fallback or video gateway function is selected, the subscriber also achieves

the same result through playing failure announcement or video prompt.

MSOFTX3000V100R008

Additional Feature

Description



Page 18 of 131


Enhance QoS

� For subscribers

Experience more friendly subscriber and optimized service <0}

Description

If the calling party originates an unsuccessful VP call, a "USSD" format notice will be

returned immediately to the calling party. Because the call originated by calling party

is video one, it is impossible to play announcement directly. The service will provide a

"USSD" to perfect subscriber interface dramatically once the call is not connected. If

multimedia fallback or video gateway function is selected, the subscriber also achieves

the same result through playing failure announcement or video prompt.

Enhancement

None.

Dependency

None.

1.11 WRFD-041000 USSD Query for Cell-Based Charging

Availability


Summary

In an MOC or MO-SMS, the MSOFTX3000 can send a USSD message to notify a

subscriber whether the current cell is a preferential cell based on information such as

the cell in which the subscriber resides, the ZC subscribed by the subscriber, and the

configuration of preferential cells. This function enables an idle subscriber to query

whether the current cell is a preferential cell in USSD mode. Thus, the service

experience of subscribers is improved.


Enhance QoS

� For subscribers

Experience more friendly subscriber and optimized service <0}

MSOFTX3000V100R008

Additional Feature

Description



Page 19 of 131

Description

In an MOC or MO-SMS, the MSOFTX3000 can send a USSD message to notify a

subscriber whether the current cell is a preferential cell based on information such as

the cell in which the subscriber resides, the ZC subscribed by the subscriber, and the

configuration of preferential cells. This function enables an idle subscriber to query

whether the current cell is a preferential cell in USSD mode. Thus, the service

experience of subscribers is improved.

Enhancement

None.

Dependency

None.

1.12 WRFD-042100 North American Equal Access (NAEA)

Availability


Summary

Equal access service: The mobile subscriber can select freely the network of each toll

operator to implement the equal competition of toll operator.


Satisfy the requirements for equal competition.

� For subscribers

Select the toll call service of each toll carriers freely.

Description

To implement the equal access, each toll operator is allocated for a CIC. After signing

an agreement with relevant toll operator, the mobile subscriber can select freely the

toll network of this toll operator to originate a call through adding CIC of this toll

operator. Two modes to use the service are: Preset CIC and Dial up freely CIC.

Mobile subscriber can add the function of network selection through preset. The

mobile subscriber can select freely toll operator through the preset function. After the

preset, mobile subscriber can select a preset toll network channel of one operator to

originate a toll call without dialing the CIC.

MSOFTX3000V100R008

Additional Feature

Description



Page 20 of 131

The mobile subscriber with the preset function still can select non-preset toll operator

through adding CIC. The subscriber neither dialing CIC nor performing preset for the

operator adopts the default toll network set by the operator for the call proceeding.

According to the technical specifications stipulated by Information Industry Ministry,

the function of network selection through preset is implemented by enabling a

subscriber parameter "North American Equal Access Preferred Carrier ID (NAEA)"

defined in the ETSI 09.02 (MAP2+) specifications.

This parameter is stored in HLR, identifying the toll operator selected by the mobile

subscriber. This parameter can be located in the "Insert subscriber data" in case of

location update and the "Send routing information ack" in case of call connection.

HLR sends the parameter to MSC/VLR. According to the received NAEA parameter,

MSC/VLR maps the "Carrier ID" value of the parameter to toll service network code

(CIC) of each toll operator. If the service requirements are satisfied, add the code to

called number and send them to GMSC. In addition, GMSC completes the subsequent

call proceeding.

Enhancement

None.

Dependency

HLR should be able to support the subscription of this service data..

1.13 WRFD-042300 Enhanced roaming restriction

Availability


Summary

Subscribers can be restricted to perform location update at local MSC based on the

Zone Code, location area, roaming type and IMSI of current roaming subscriber to

implement flexible roaming restriction function.

It enables the operator to implement flexible roaming restriction function based on the

Zone Code, location area, roaming type and IMSI of current roaming subscriber.


− Provide flexible and controllable roaming restriction mechanism.

− Provide localization service similar to Wireless Local Loop (WLL) service.

− Attract more low-priority subscriber.

− Increase customer group.

− Increase the traffic.

� For subscribers

MSOFTX3000V100R008

Additional Feature

Description



Page 21 of 131

Enjoy rich localization service to avoid the charging increment because of the

roaming in another place.

Description

Subscribers can be restricted to perform location update at local MSC based on the

Zone Code, location area, roaming type and IMSI of current roaming subscriber to

implement flexible roaming restriction function.

It enables the operator to implement flexible roaming restriction function based on the

Zone Code, location area, roaming type and IMSI of current roaming subscriber.

Enhancement

None.

Dependency

None.

1.14 WRFD-042400 Enhanced MSRN allocation

Availability


Summary

Support the function of allocating roaming number based on location area cell.

MSOFTX3000 also supports the function of allocating roaming number based on the

MSC-ID in case of virtual multi-MSC solution.


Determine the cell through roaming number to adopt different customer strategy,

such as charging strategy.

� For subscribers

None

Description

Support the function of allocating roaming number based on location area cell.

MSOFTX3000 also supports the function of allocating roaming number based on the

MSC-ID in case of virtual multi-MSC solution.

MSOFTX3000V100R008

Additional Feature

Description



Page 22 of 131

Enhancement

None.

Dependency

None.

1.15 WRFD-042700 Alternate Line Selection (ALS)

Availability


Summary

Support the functions of line1 and line 2 through the terminal and subscribe a number

for each line. For two numbers of ALS, the subscriber can set different CF SS and Call

barring SS.

When the subscriber adopts line 2 number:

� Perform only speech service and its supplementary service.

� Adopt ODB for service restriction.

� Only receive SM instead of sending SM.

� Cannot perform USSD operation.


Provide two independent numbers for the subscriber to enhance the competition.

� For subscribers

Apply for dual-line for office and private numbers.

Description

Support the functions of line1 and line 2 through the terminal and subscribe a number

for each line. For two numbers of ALS, the subscriber can set different CF SS and Call

barring SS.

When the subscriber adopts line 2 number:

� Perform only speech service and its supplementary service.

� Adopt ODB for service restriction.

� Only receive SM instead of sending SM.

� Cannot perform USSD operation.

MSOFTX3000V100R008

Additional Feature

Description



Page 23 of 131

Enhancement

None.

Dependency

None.

1.16 WRFD-042800 Dual-MSISDN for multimedia and speech telephony

Availability


Summary

Subscribe two services of independent numbers respectively based on video and

speech service. This function is different from that with multiple MSISDN. After the

subscriber subscribes the service, calling/called video and speech calls adopt different

numbers, and dual-MSISDN function is effective only when the subscriber is a called

party. If the subscriber registers this function and ALS, the subscriber has 3 telephone

numbers.


Provide two independent speech and video calls completely for the subscriber to

enhance the competition.

� For subscribers

Apply for two numbers for speech and video call respectively.

Description

Subscribe two services of independent numbers respectively based on video and

speech service. This function is different from that with multiple MSISDN. After the

subscriber subscribes the service, calling/called video and speech calls adopt different

numbers, and dual-MSISDN function is effective only when the subscriber is a called

party. If the subscriber registers this function and ALS, the subscriber has 3 telephone

numbers.

Enhancement

None.

Dependency

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 24 of 131

1.17 WRFD-043700 MAP Bypass

Availability


Summary

The MSOFTX3000 supports the MAP Bypass function when obtaining routes from

the HLR fails.


This service guarantees the success of intra-MSC calls in the case of the

breakdown of the HLR. This can greatly lower the loss of carriers.

� For subscribers

The subscribers can still make an intra-MSC call in the case of the breakdown of

the HLR.

Description

When the failure of the HLR results in unreachable links between the MSOFTX3000

and the HLR or the timeout of the HLR response, the MSOFTX3000 does not release

the call if it can determine that the callee is a local subscriber. Specifically, the

MSOFTX3000 obtains the information on the callee from the local VDB and then

sends the paging request to enable the call flow to continue.

The MAP Bypass function is applicable in the following scenarios:

� The HLR breaks down and the physical links between the HLR and the MSC are

interrupted.

� The physical links between the HLR and the MSC are normal, but the traffic

congestion results in the timeout of the message handling.

� The physical links between the HLR and the MSC are normal, but the failure of user

data server results in the failure of obtaining routes.

Enhancement

None.

Dependency

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 25 of 131

1.18 WRFD-043800 Malicious Call Trace (MCT)

Availability


Summary

The MSC stores information on a The information on MCT contains the calling

number, which can be used to trace the subscriber who originates the malicious call.


The MCT service enables carriers to implement various services.

� For subscribers

The MCT service enables subscribers to enjoy various services.

Description � If a subscriber registers a special SS_CODE in the HLR, it indicates that the

subscriber subscribes to the MCT function. When the subscriber that subscribes to

the MCT function receives a malicious call, the subscriber can dial an access code to

activate the MCT function. After activating the MCT function, the MSC sends MCT

information to the subscriber through a short message.

� After receiving a malicious call, a subscriber can activate the MCT function after the

call is completed, or the subscriber can also place the caller on hold during the call

and then activate the MCT function.

Enhancement

None.

Dependency

The SS_CODE of the MCT service must be registered in the HLR.

1.19 WRFD-046000 E911

Availability

This feature is introduced in V100R007C03 Version.

Summary

911 is the emergency service number in the USA. E911 is the enhanced emergency

service applicable to the USA. The service complies with the following specifications:

J-STD-034: Enhanced Emergency Services

MSOFTX3000V100R008

Additional Feature

Description



Page 26 of 131

J-STD-036-B-1 [E] v0.1: Enhanced Wireless 9-1-1 Phase II PN-3-3890-RV2-AD1

GR_2956_CORE.i05: CCS/SS7 Generic Requirements in Support of E9-1-1 Service


This function can meet the requirement of the Federal Communications

Commission (FCC).

� For subscribers

− When a subscriber makes an emergency call, the emergency call center can

quickly locate the subscriber and provide emergency assistance.

− If an emergency call is disconnected abnormally, the emergency call center

can call back the subscriber based on the MSISDN.

Description

On receiving an emergency call, the MSC connects the call to the Public Safety

Answering Point (PSAP). Then, the MSC obtains location information of the caller

during the call and reports it to the GMLC.

According to the E911 specifications, the E911 is implemented in two phases: E911

Phase I implements the rough location of a caller. E911 phase II implements the

precise location of a caller. For details on the location information and the format, see

J-STD-036-B-1 [E] v0.1.

Figure 1-1 shows the network architecture of E911 Phase I.

Figure 1-1 Network architecture of E911 Phase I

In E911 Phase I, an E911 emergency call is connected as follows: According to the

called number in Emergency Category or Setup in Emergency Setup message, the

MSC determines that the call is an E911 emergency call through number analysis. The

MSC then obtains the corresponding ESRD parameter based on the location

information of the caller. Through the called number and ESRD parameter, the MSC

routes the call to the S/R, and then the S/R routes the call to the PSAP. The MSC is not

required to know whether the S/R exists and whether the MSC is directly connected to

the PSAP. The MSISDN and ESRD of the subscriber are contained in the outgoing

MSOFTX3000V100R008

Additional Feature

Description



Page 27 of 131

IAM message. If the MSISDN cannot be obtained, the MSC uses the IMEI to

construct an MSISDN.

Figure 1-2 shows the network architecture of E911 Phase II.

Figure 1-2 Network architecture of E911 Phase II

E2

Lg

GMLC ESME

MSC/ VLRA

S/R

ESNE

MSa

ISUP

In E911 Phase II, an E911 emergency call is connected as follows: According to the

called number in Emergency Category or Setup in Emergency Setup message, the

MSC determines that the call is an E911 emergency call. According to the called

number, ESRD, and precise location information of the caller, the MSC routes the call

to the ESNE flexibly. The precise location of a subscriber is completed by the MSC

and RNC jointly. The precise location information is reported to the GMLC or

Emergency Services Network Entity (ESNE). The Emergency Services Message

Entity (ESME) can request the MSC for the precise location of the caller through the

Gateway Mobile Location Center (GMLC) in real time.

Enhancement

None.

Dependency

The BSC or the RNC on the access network side should support the E911 function.

MSOFTX3000V100R008

Additional Feature

Description



Page 28 of 131

1.20 WRFD-048000 Text Telephony (TTY)

Availability

This feature is introduced in V100R007C03 Version.

Summary

The TTY service provides text conversation for subscribers with disabilities (for

example, the deaf and dumb). It complies with the 3GPP TS 22.226 and 29.232

specifications. A TTY terminal consists of a TTY terminal device and a mobile phone.

When a call is connected through the mobile phone, subscribers can enter characters

on the TTY terminal device and communicate with each other. Compared with the SMS,

the TTY service enables subscribers to communicate in real time.


The TTY service satisfies the need of people with disabilities and therefore

increases the subscriber base for carriers.

� For subscribers

The deaf and dumb can communicate in real time through the TTY service. In

case of any emergency, they can dial 911 for help by using the TTY service.

Description

The TTY service adopts the cellar text Modem (CTM) technology. After CTM

modulation, the Baudot monophonic signal of the TTY terminal is demodulated

through the CTM at the MGW connecting to the PSTN. After demodulation, the

Baudot monophonic signal is restored. Currently, there are eight TTY standards,

including the Baudot. The Baudot is the widely used TTY standard in the United

States. V.18 is an ITU standard that is compatible with the eight TTY standards.

MSOFTX3000V100R008

Additional Feature

Description



Page 29 of 131

Figure 1-3 Application of the TTY service

CTM capable

Mobile

PSTN

V.18 V.18

V.18

CTM

CTM

MSC server

RAN server

MGW/

Transcoder CTM

adapter

Enhancement

None.

Dependency


1.21 WRFD-050500 GERAN/UTRAN Access Restriction (ARD)

Availability


Summary

This function allows carriers to control the access of subscriber to the GERAN or

UTRAN. Provision of this function requires the collaboration of MSOFTX3000 and

HLR and the HLR must support the ARD subscription function.


MSOFTX3000V100R008

Additional Feature

Description



Page 30 of 131

Flexibly control the subscribers’ access to GERAN or UTRAN.

� For subscribers

None

Description

The MSOFTX3000 provides the function to determine whether the subscriber has

subscribed to the ARD service. For example, if

GREANAllowed/UTRANNOTAllowed is configured upon the subscription of ARD

on the HLR, if the local MSFTX3000 supports the ARD 3G function, location update

will fail due to the access restriction when the subscriber tries to access the network of

local office from the 3G UTRAN. In this way, the subscriber is restricted from

accessing the 3G network.

Enhancement

None.

Dependency

The network must be equipped with HLR and the HLR must support the ARD

subscription function.

1.22 WRFD-050600 Shared Network Area in Connected Mode (SNA)

Availability


Summary

At present, roaming restriction of mobile network is implemented in idle mode. There

are ZC roaming restriction and enhanced roaming restriction and these types of

restrictions are all controlled by the CN. If relocation occurs when a subscriber is

engaged in the conversion, the CN cannot restrict the roaming area of the subscriber.

In this case, the area that cannot be accessed in idle can be accessed in connected

mode. The Shared Network Area in Connected Mode (SNA) function is used to solve

this problem. For example, if two 2G network carriers shares one 3G network, carriers

can use this function to ensure that subscribers use their own 2G network only.


Realize consistent mobile access restriction in idle mode and in connected mode

and enhance the network restriction function.

� For subscribers

None

MSOFTX3000V100R008

Additional Feature

Description



Page 31 of 131

Description

The SNA function is implemented by CN and UTRAN together. The MSC provides

the configuration of roaming restriction information in connected mode and the shared

network information and transfers the roaming restriction information to the RNC. The

RNC completes the roaming restriction in connected mode based on the roaming

restriction information received. The configuration of shared network information

contains the configuration of shared network area, which helps realize the area-based

roaming restriction. Configuration of subscriber roaming restriction information is

completed through the IMSI number segment. The roaming restriction in connected

mode is implemented by configuring the allowed shared network area group.

Enhancement

None.

Dependency

RNC must support the SNA function.

1.23 WRFD-050700 Local-based service restriction

Availability


Summary

When a subscriber who subscribes to a ZoneCode updates a location or performs

services, the MSC determines whether the subscriber belongs to a ZoneCode, and

performs logic judgment according to the area service. For local smart services, this

function allows or refuses subscribers to update location, complete calls (calling or

called), or to use the SMS, supplementary service and LCS service.


It is convenient for carriers to develop the area service of local smart services.

� For subscribers

None

Description

When a subscriber who subscribes to a ZoneCode updates a location or performs

services, the MSC determines whether the subscriber belongs to a ZoneCode, and

performs logic judgment according to the area service. For local smart services, this

function allows or refuses subscribers to update location, complete calls (calling or

called), or to use the SMS, supplementary service and LCS service.

MSOFTX3000V100R008

Additional Feature

Description



Page 32 of 131

Enhancement

None.

Dependency

The HLR is required to support subscribing the ZoneCode.

1.24 WRFD-050900 Roaming restriction for CAMEL

Availability


Summary

When a subscriber subscribes the O-CSI, the MSC can consider whether the CAMEL

subscriber is allowed or restricted to roam according to the subscribed CAMEL

version.


It is convenient for carriers to control whether to allow the roaming of intelligent

subscribers.

� For subscribers

None

Description

When a subscriber subscribes the O-CSI, the MSC can consider whether the CAMEL

subscriber is allowed or restricted to roam according to the subscribed CAMEL

version.

Enhancement

None.

Dependency

The HLR is required to support subscribing the O-CSI.

1.25 WRFD-080700 Signaling handover

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 33 of 131

Summary

It means the handover when an MS only has signaling connection with network (that

is, traffic channel not assigned).


Facilitate enhancing successful handover ratio.

� For subscribers

The call loss is decreased.

Description

It means the handover when an MS only has signaling connection with network (that

is, traffic channel not assigned).

Enhancement

None.

Dependency

None.

1.26 WRFD-080900 Load based handover

Availability


Summary

In the case of handover between the 2G system and the 3G system, the cell load

information is carried to other systems to balance the traffic and load of the UMTS

network and the GSM network of carriers.


The function is used to balance the traffic and load of the UMTS network and the

GSM network of carriers.

� For subscribers

None

Description � Intra-office handover from 3G to 2G

MSOFTX3000V100R008

Additional Feature

Description



Page 34 of 131

If the HANDOVER REQUEST ACKNOWLEDGE message returned to the MSC by

the BSC contains the cell load information, and the MSC configures the RNC to

support the function of "cell load-based handover", the MSC transparently transmits

the cell load information in the Iu interface message RELOCATION COMMAND.

� Inter-office handover from 3G to 2G

During an inter-office handover, if the HANDOVER REQUEST ACKNOWLEDGE

message returned to the MSC-B by the BSC contains the cell load information, the

MSC-B transparently transmits the information to the MSC-A in the E interface

message MAP-Prep-Handover resp. If the MSC-A configures the RNC to support the

function of "cell load-based handover", and the MAP-Prep-Handover resp message

returned to the MSC-A by the MSC-B contains the cell load information of the

destination side, the MSC-A transparently transmits it to the RNC in the

RELOCATION COMMAND message.

� Intra-office handover from 2G to 3G

If the RELOCATION REQUEST ACKNOWLEDGE message returned to the MSC by

the RNC contains the cell load information, and the MSC configures the BSC to

support the function of "cell load-based handover", the MSC transparently transmits

the cell load information in the A-interface message HANDOVER COMMAND.

� Inter-office handover from 2G to 3G

During an inter-office handover, if the RELOCATION REQUEST ACKNOWLEDGE

message returned to the MSC-B by the RNC contains the cell load information, the

MSC-B transparently transmits the information to the MSC-A in the E interface

message MAP-Prep-Handover resp. During an inter-office handover, if the MSC-A

configures the BSC to support the function of "cell load-based handover", and the

MAP-Prep-Handover resp message returned to the MSC-A by the MSC-B contains the

cell load information of the destination side, the MSC-A transparently transmits it to

the BSC in the HANDOVER COMMAND message of A-interface.

Enhancement

None.

Dependency


1.27 WRFD-091200 Announcement to abnormal IN users

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 35 of 131

Summary

If the HLR does not subscribe the intelligence, for example, the O/T-CSI subscription

information is deleted wrongly, but the subscriber is an intelligent subscriber in the

SCP. When the subscriber calls, the system gives the announcement alert and restricts

the call.


It provides the method of announcement alert and outputting alarms to avoid the

problem that the HLR maintenance personnel modifies an intelligent subscriber

as a postpaid subscriber wrongly, thus to cause the call of the subscriber to be free

from the control of the SCP, therefore carriers cannot charge such subscribers.

− When an affected subscriber originates a call or is called, the system plays the

alert tone to the caller. After the caller complains, the operator maintenance

personnel solve this problem by querying the intelligent subscription

information of the caller and the callee in the HLR

− When an affected subscriber is called, the system plays the alert tone to the

caller. The caller may not complain, and the operator maintenance personnel

solves this problem through the output alarm.

� For subscribers

None

Description

The announcement protection requirements of intelligent subscribers are from a

feature provided by the Ericsson equipment in the existing 2G network found during

the test of Huizhou office of China Mobile. If the HLR does not subscribe the

intelligence, but the subscriber is an intelligent subscriber in the SCP. When the

subscriber calls, the system gives the announcement alert and restricts the call. This

requires the MSOFTX3000 to solve such a problem actually. The HLR maintenance

personnel modify an intelligent subscriber as a postpaid subscriber wrongly, thus to

cause the call of the subscriber to be free from the control of the SCP. Therefore,

carriers cannot charge such subscribers. The detailed specifications of the

requirements are as follows.

� It is only applied in the destination network, but not applied in the OVERLAY

scenario of the cascade network.

� It is applied in the originating office and the gateway office, and can only provide

announcement protection to such situation that the HLR wrongly deletes the O/TCSI

subscription information.

� It can support and distinguish subscribers in the IMSI/MSISDN O-CSI number

segment, and provide announcement protection to subscribers in the IMSI/MSISDN

T-CSI number segment and the IMSI/MSISDN O&T-CSI number segment.

� It cannot restrict calls to free numbers, including free recharge and fee query

numbers used in the existing network, such as 1860, 1861 and 13800138000, and

calling free numbers, such as 800.

� It cannot restrict emergency calls, such as 110, 119, 112, and 120.

� The existing network does not support forwarding intelligent subscribers and that

the intelligent subscriber is free when serving as a callee, so it regards an intelligent

MSOFTX3000V100R008

Additional Feature

Description



Page 36 of 131

subscriber whose O-CSI subscription information is wrongly deleted as a postpaid

subscriber, and allows normal call transfer. But a call to such intelligent subscribers

whose T-CSI subscription information is wrongly deleted is restricted

unconditionally when they are a callee.

� During early forwarding, it checks announcement protection to the T-CSI

subscription information of the forwarding party.

� During a call, it cannot cause the forced release when the O/T-CSI intelligent

subscription information is deleted.

� When the announcement protection causes call release, the announcement EID is

configurable. The announcement content is "The service is restricted temporarily,

please contact 1860" uniformly in the existing network.

� The call of the callee is restricted due to the loss of the T-CSI subscription

information, and there is no way to notify the subscriber, so the alarm information is

outputted for the maintenance personnel to conveniently process it.

Enhancement

None.

Dependency

The intelligent subscriber announcement protection involves two NE entities, MSC

and MGW.

For the service, the originating office (V)MSC or the gateway office (G)MSC mainly

completes different signaling processing, data analysis, and announcement of calls.

1.28 WRFD-091300 DTMF sending restriction

Availability


Summary

The DTMF sending restriction function enables the VMSC to determine whether to

intercept the DTMF numbers sent by a subscriber based on the analysis of the

subscriber number. The function restricts the dialing back service that is triggered

based on the DTMF numbers dialed by a subscriber.


The function restricts the dialing back service that is triggered based on the

DTMF numbers dialed by a subscriber.

� For subscribers

None

MSOFTX3000V100R008

Additional Feature

Description



Page 37 of 131

Description

The VMSC provides the DTMF sending restriction function by restricting the

following DTMF interactions:

� DTMF interaction before the call is answered

� DTMF interaction between a mobile caller and a specific callee

� DTMF interaction between a mobile caller and a specific caller

� DTMF interaction between a caller and a mobile callee when the incoming call does

not carry the calling number

Enhancement

None.

Dependency

None.

1.29 WRFD-091500 Call in Progress Tone

Availability


Summary

This function means that the MSOFTX3000 instructs the MGW to play

announcements to the caller when paging the callee, indicating that the call is ongoing.

This function prevents the caller from hanging up when no response is received due to

long-time paging. Thus, this function improves customer satisfaction. If both the Call

in Progress Tone service and the CRBT service are subscribed to, the CRBT service

has higher priority.


This service improves the call completion rate and increases the revenue of

carriers.

� For subscribers

The caller can hear announcements when the callee is paged, and thus the

customer satisfaction is improved.

Description

This function means that the MSOFTX3000 instructs the MGW to play

announcements to the caller when paging the callee, indicating that the call is ongoing.

This function prevents the caller from hanging up when no response is received due to

long-time paging. Thus, this function improves customer satisfaction. If both the Call

MSOFTX3000V100R008

Additional Feature

Description



Page 38 of 131

in Progress Tone service and the CRBT service are subscribed to, the CRBT service

has higher priority.

Enhancement

None.

Dependency � The MSC and the MGW are involved in the Call in Progress Tone service.

� For this service, the MSC mainly processes signaling of calls, analyzes data, and

instructs the MGW to play announcements to callers when paging the callees.

� The MGW plays announcements during a call.

1.30 WRFD-100700 Hot Billing

Availability


Summary

After the original bill is generated and sent to the iGWB, the iGWB will allocate one

single channel to store the final bill and send them to the billing center at real time to

realize the billing for the subscriber.


Can implement some real time billing service based on the hotbilling service,e.g.,

telephone renting service.

� For subscribers

can receive generally real time billing sheet, and enjoy some real time billing

service.

Description

After the original bill is generated and sent to the iGWB, the iGWB will allocate one

single channel to store the final bill and send them to the billing center at real time to

realize the billing for the subscriber.

Enhancement

None.

Dependency

Require billing center’s support.

MSOFTX3000V100R008

Additional Feature

Description



Page 39 of 131

1.31 WRFD-100800 Advice of Charge Charging/Information (AOCI/AOCC)

Availability


Summary

AOCI: This service provides real-time display of charge. After subscribers register

AOCI services, network side delivers rate information and MS calculates charge

automatically. Subscribers can display charge through menu and accumulate charge.

Bill charges of AOCI services are settled at network side. Mobile subscribers only

obtain charging information of this call.

AOCC: Bill charges of AOCC services are settled at terminal MS. MSC is responsible

for delivering rate information. Coordination of terminal MS supporting Phase2

standard and a special SIM card is required. AOCC is a simple mode to realize prepaid

services.


Enhance service function and implement advice of charging information and

simple pre-paid charging, namely real-time charging in MS.

� For subscribers

After adopting AOCI and leasing their own MSs to others, subscribers can charge

the other party based on displayed charges.

With AOCC, subscribers can buy local temporary card in the case of roaming to

avoid premium roaming rate. The local temporary card features the following:

� One-off usage.

� No network access fees.

� No number fees.

� Un-rechargeable.

� Charged at MS side.

� No balance information of UE at network side.

Description

AOCI: This service provides real-time display of charge. After subscribers register

AOCI services, network side delivers rate information and MS calculates charge

automatically. Subscribers can display charge through menu and accumulate charge.

Bill charges of AOCI services are settled at network side. Mobile subscribers only

obtain charging information of this call.

AOCC: Bill charges of AOCC services are settled at terminal MS. MSC is responsible

for delivering rate information. Coordination of terminal MS supporting Phase2

standard and a special SIM card is required. AOCC is a simple mode to realize prepaid

services.

MSOFTX3000V100R008

Additional Feature

Description



Page 40 of 131

Enhancement

None.

Dependency

Require terminal support.

1.32 WRFD-101100 ISDN CDR

Availability


Summary

PRA subscribers can be accessed to the MSC through the PRA trunk group, serving as

ISDN subscribers to originate services. At the end of the call service of ISDN

subscribers, it is required to provide the ISDN subscriber CDR instead of the gateway

CDR.


The services are enriched by implementing ISDN CDR.

� For subscribers

None.

Description

The generation of the ISDN CDR depends on the type of the outgoing and incoming

trunk groups. If the type of the incoming trunk group is PRA, a software parameter is

adopted to control whether to generate CDRs for the calling ISDN subscribers. If the

type of the outgoing trunk group is PRA, a software parameter is adopted to control

whether to generate CDRs for the called ISDN subscribers.

Enhancement

None.

Dependency

Require billing center’s support.

MSOFTX3000V100R008

Additional Feature

Description



Page 41 of 131

1.33 WRFD-101200 Cell-based charging

Availability


Summary

ZC is subscripted in HLR, and in MSC SERVER ZC list is configured. In the ZC list,

Region service type，Cell number, rate level and TC rate code are contained. As MS

start up the service, MSC SERVER will check if the area of the MS is configured with

the ZC, and record the TC code in the BILL according to the rate information

corresponding the ZC. At the same time, an USSD is sent to the MS to inform that it is

in the favorable CELL.


The Service provider can deploy service more flexibility.

� For subscribers

The users can select different services.

Description

ZC is subscripted in HLR, and in MSC SERVER ZC list is configured. In the ZC list,

Region service type，Cell number, rate level and TC rate code are contained. As MS

start up the service, MSC SERVER will check if the area of the MS is configured with

the ZC, and record the TC code in the BILL according to the rate information

corresponding the ZC. At the same time, an USSD is sent to the MS to inform that it is

in the favorable CELL.

Enhancement

None.

Dependency

HLR needs support the service.

1.34 WRFD-101700 Whether to generate the SMS CDRs is configurable based on the attribute (national or international) of the SMC.

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 42 of 131

Summary

In the original flow, the VMSC generates the CDRs for SMSs involving both national

and international SMCs. This function adds a new handling mode: The VMSC does

not generate the CDRs for SMSs involving the national SMCs. Whether to adopt the

original handling mode or the new handling mode is determined by a software

parameter. If the SMC number is a national number and the software parameter is set

to 1, the VMSC does not generate SMS MO/MT CDRs. If the software parameter is

set to 0, the VMSC generates SMS MO/MT CDRs. By default, the VMSC does not

generate SMS MO/MT CDRs.


The carrier can store the CDRs generated in a longer period without increasing

the disk space of the iGWB.

� For subscribers

The CDRs generated by subscribers in a longer period can be stored. This helps

subscribers to query the CDRs and check their correctness.

Description

This function uses a software parameter to determine whether to generate SMS

MO/MT CDRs if the SMC number is a national number. This function aims to solve

the following problems:

� A large number of SMS CDRs are generated on the VMSC every day. The space

used by SMS CDRs account for more than 60% of the total disk space of the iGWB.

This ratio is still increasing.

� The space for storing CDRs does not change. Originally, the CDRs generated in a

period of 20 days can be stored on the disk. At present, only the CDRs generated in

a period of 10 days can be stored.

Therefore, the disk space is insufficient to store the CDRs. If the disk space does not

change, the number of CDRs must be reduced. Since the majority of the CDRs are

SMS CDRs and the charging of SMSs involving national SMCs can be completed on

the SMC, the VMSC does not need to store SMS CDRs for national SMCs. Therefore,

the problem is solved when the VMSC generates CDRs for SMSs involving

international SMC numbers only and does not generate CDRs for SMSs involving

national SMCs.

This function uses a software parameter to determine whether to generate CDRs

linking to national SMCs. The rule for determining whether a CDR belongs to a

national SMC is as follows: Compare the normalized SMC number (international

number) with the country code in the local office information table based on the

maximum matching method. If the two numbers are the same, the SMC is considered

to be a national SMC.

Enhancement

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 43 of 131

Dependency

None.

1.35 WRFD-110500 R2 signaling (No.1 signaling in China)

Availability


Summary

In China, the R2 CAS signaling is called No.1 signaling. The MSOFTX3000 supports

the R2 signaling. When the MSC server and the MGW jointly serve as the MSC, the

MGW processes the CAS, converts the R2 signaling messages, and then sends the

messages to the MSC server. Processed by both of the MGW and the MSC server, the

R2 signaling can meet the requirements of diverse networking modes of the

VMSC/VLR, GMSC, and TMSC.


Based on the R2 signaling processed by the VMSC/VLR, GMSC, and TMSC, the

networking can be implemented flexibly to meet different requirements.

� For subscribers

None.

Description

The R2 signaling consists of line signaling and register signaling. The line signaling is

always sent through the timeslot 16 of each PCM. The register signaling is sent

through the voice channel based on multiple frequency control. During the session, the

register signaling cannot be transmitted. To obtain the register signaling, two

frequencies are chosen from six (five, or four) frequencies, and then 15, that is, 6 x

(6-1) / 2, kinds of register signaling can be obtained.

The line signaling is used to monitor the status of trunks, which can be occupied,

released, or blocked. It is classified into forward signaling and backward signaling.

Through the combination of the 15 forward and 15 backward multi-frequency codes,

the register signaling can transmit the following information:

� Address information

� The language bit and the discrimination bit of international calls

� Information of echo cancellation

� Caller attribute and call attribute

� Circuit attribute

� Status of the callee

MSOFTX3000V100R008

Additional Feature

Description



Page 44 of 131

Based on the functions of the line signaling and the register signaling, the VMSC/VLR,

GMSC, and TMSC can provide the following functions:

� Connecting basic incoming and outgoing R2 calls, which are completed at the end

office

� Connecting tandem calls

� Interworking with the PSTN to connect PSTN-MS and MS-PSTN calls

� Interworking with other types of trunks, such as ISUP/TUP trunks

� Providing supplementary services, such as call forwarding, call waiting, call hold,

and multiparty service.

To meet different requirements, the networking can be implemented flexibly through

the R2 signaling. For example, the GMSC can use the R2 signaling to connect to the

corporate private branch exchange (PBX).

Enhancement

None.

Dependency

The required network elements differ with the networking mode. The only requirement

is that the peer device must also support the R2 signaling.

1.36 WRFD-111200 BSSAP+ protocol (Gs interface)

Availability


Summary

SGSN association management

If Gs interface is configured between MSC and SGSN, association management can be

implemented between local MSC and related SGSN. For example, record SGSN and

Gs connection status of subscribers.


With association location update of Gs interface, RA of subscribers in PS is

guaranteed. Location update of SGSN and VLR depends on changes in location

area of CS. Therefore, called subscribers can be paged correctly to avoid

disconnection with subscribers in the case of in-service GPRS service. Appeals of

GPRS services are enhanced.

� For subscribers

Ensure subscribers to enjoy GPRS services and speech call services and

important speech incoming calls are not lost.

MSOFTX3000V100R008

Additional Feature

Description



Page 45 of 131

Description

Gs interface paging

Premises: GPRS attaches GPRS and/or MSC in CS in A or B modes.

If local MSC finds that subscriber Gs connection exists, SGSN is required to page

subscribers through Gs interface and existing lu-PS wireless connection when CS

pages subscribers. Correspondingly, subscriber paging establishes connection from

lu-CS and feeds back to MSC. With this mechanism, new paging connection at

wireless interface is saved.

Associated location update of Gs interface

GPRS subscribers can originate location update of routing area (RA) in PS and

location area (LA) in CS. After location of RA in PS is updated, SGSN notifies VLRF

or subscribers to update location through Gs interface.

Alert of Gs interface

MSC can require SGSN to report activities of subscribers through Gs interface, such

as subscriber routing area update.

The following three bearer modes are supported to satisfy different networking

requirements. Generally, the first mode is the basic bearer mode.

� WMFD-111201 MTP2/MTP3/SCCP/BSSAP+

� WMFD-111203 IP/SCTP/M2UA/MTP3/SCCP/BSSAP+

Enhancement

None.

Dependency

Cooperate with SGSN.

1.37 WRFD-111300 Location service (LCS) (Lg interface)

Availability


Summary

The LCS is implemented over the Lg interface.


MSOFTX3000V100R008

Additional Feature

Description



Page 46 of 131

Based on the location function of the MSC and the NEs (such as SCP) that

provide other services, carriers can provide various services related to location. � For subscribers

Subscribers can enjoy the benefits of LCSs, such as self location query, other

location query, emergency call location, location-based welcome and introduction

service. Description

Connected to the gateway mobile location center (GMLC) over the Lg interface, the

MSOFTX3000 provides various LCSs such as:

� MTC LCS: The external equipment can locate a mobile terminal. � MOC LCS: A mobile terminal initiates a location request. � Emergency call LCS: The network subsystem can locate the subscriber for an

emergency call. � Subscriber privacy safeguards: To meet the subscriber privacy requirements, the

MSOFTX3000 can restrict the subscriber who makes a request for location. Enhancement

None.

Dependency

This function requires the coordination of the GMLC and equipment at access side.

1.38 WRFD-111400 CHECK IMEI and F interface

Availability


Summary

The function supports the standard CHECK IMEI flow.

Enhanced functions implemented in the CHECK IMEI function are as follows:

� Multiplexing the IMEI: The function is used to perform CHECK IMEI flows on the

obtained IMEI of the subscriber, without obtaining the IMEI from the subscriber for

each time.

� Performing the CHECK IMEI flow based on the IMSI number segments: The

subscriber groups on which the CHECK IMEI flow must be performed can be

divided based on IMSI number segments.

� Originating the CHECK IMEI flow based on the location update type

� Controlling the access of the unknown subscribers based on the IMSI number

segments: When the result of CHECK IMEI indicates that the subscribers are

unknown, the subscriber groups can be divided into groups for which the access is

MSOFTX3000V100R008

Additional Feature

Description



Page 47 of 131

allowed and groups for which the access is prohibited based on IMSI number

segments.

� Controlling whether the subscribers can be accessed: The subscribers can be

accessed when the EIR is unreachable.

� Controlling the announcements playing and call connection for subscribers in the

grey list: When the result of CHECK IMEI indicates that the subscribers are those in

grey list, the function controls whether to play announcements and whether to

connect the call after the announcements.

� The CHECK IMEI operation carries the IMSI and the MSISDN. When the CHECK

IMEI message must be borrowed to transmit subscriber parameters, the IMSI and

the MSISDN can be carried in the messages related to the CHECK IMEI operation.


The illegal terminals are prohibited to access the network.

� For subscribers

Subscribers can choose the service to prevent the balance of the lost mobile

phone from being used illegally.

Description

The function supports the standard CHECK IMEI flow.

The function enables the IMEI used in the CHECK IMEI operation to be multiplexed.

That is, the OBTAIN IMEI flow can be originated periodically. The OBTAIN IMEI

flow can be configured for one time, and then the IMEI obtained by the OBTAIN

IMEI flow can be used to perform the CHECK IMEI for multiple flows. The number

of times of using IMEI can be set to a value from 0 to 255.

The function controls whether to originate the CHECK IMEI operation based on the

IMSI numbers. When the result of CHECK IMEI indicates that the subscribers are

unknown, the function controls whether the subscribers can be accessed based on the

IMSI numbers. Thus, the requirement that the MSC not send CHECK IMEI REQ

messages to the EIR can be met.

The CHECK IMEI function also provides the following enhanced functions:

� Controlling whether the subscribers can be accessed when the EIR is unreachable

� Controlling whether to play announcements for subscribers in grey list and whether

to connect the call after the announcements

� Enabling the CHECK IMEI flow to be originated based on the location update type

In the CHECK IMEI operation, MAP_OPEN_REQ and MAP_CHECK_IMEI_REQ

can carry the IMSI and MSISDN. The function is used to transmit parameters rather

than perform the CHECK IMEI flow. Thus, the duration of waiting for the EIR

response is one second. After one second, the service flow continues.

Enhancement

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 48 of 131

Dependency

When the enhanced function carrying the subscriber parameters is used, the entities

receiving the CHECK IMEI messages must obtain correct parameters from the

messages.

1.39 WRFD-111500 MAP Policing

Availability


Summary

MAP Policing is defined as follows: After a designated network entity (or a group of

designated network entities) originates a MAP dialog request, the MAP carries out

operation screening function according to the operation request class information upon

the receipt of the first MAP service request.


Screen the incoming messages that are not expected by the local office to realize

the self-protection and avoid the full consumption of resource.

� For subscribers

None

Description

The designated network entity uses the address group for identification purpose. The

format of the address could be GT or OPC.

The operation request class information consists of the MAP operation code, indicated

MAP version upon the setup of MAP dialog, and the SSN in the local end address.

You can use commands to configure the designated network entity and the MAP

operation class to be screened.

Enhancement

None.

Dependency

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 49 of 131

1.40 WRFD-111600 SCCP Policing

Availability


Summary

The function is controlled by LICENSE.

When different networks or carriers are interconnected, to avoid spreading authority

override messages on the signaling network and ensure the security of the signaling

network, SCCP policing function is required.


Enhance the security of signaling network.

� For subscribers

None

Description

The following combinations are available to implement the SCCP policing:

� Calling address DPCSSN screening

� Calling address GTSSN screening

� Calling address GTT screening

� Called address DPCSSN screening

� Called address GTT screening

� Called address GTSSN screening

� Calling address DPCSSN + Called address DPCSSN screening

� Calling address DPCSSN + Called address GTSSN screening

� Calling address DPCSSN + Called address GTSSN screening + Called address

GTT screening

� Calling address DPCSSN + Called address GTT screening

� Calling address GTSSN + Called address DPCSSN screening

� Calling address GTSSN + Called address GTSSN screening

� Calling address GTSSN + Calling address GTT screening

� Calling address GTSSN + Called address GTSSN + Called address GTT

screening

� Calling address GTSSN + Calling address GTT + Called address GTT screening

� Calling address GTSSN + Calling address GTT + Called address DPCSSN

screening

� Calling address GTSSN + Calling address GTT + Called address GTSSN

screening

MSOFTX3000V100R008

Additional Feature

Description



Page 50 of 131

� Calling address GTSSN + Calling address GTT + Called address GTSSN

screening + Called address GTT screening

� Calling address GTSSN + Called address GTT screening

� Calling address GTT + Called address DPCSSN screening

� Calling address GTT + Called address GTSSN screening

� Calling address GTT + Called address GTSSN screening + Called address GTT

screening

� Calling address GTT + Called address GTT screening

� Called address GTSSN + Called address GTT screening

Enhancement

None.

Dependency

None.

1.41 WRFD-111800 MAP AC version configured

Availability


Summary

AC version flexible control refers to the control over the dialog originated by the local

office to the designated network entity. It is one of the functions of AC version and a

method of manual control of AC function. Through manual configuration, AC version

is originated for the dialog of the designated network entity. In this way, the message

generated due to the version negotiation can be reduced.

Before the local office originates a dialog request, if this function is enabled, the

destination address and AC name are used to search the table to obtain the configured

MAP version. If the searching is successful, the searched MAP version is used to

originate the dialog. Otherwise, the latest version supported by the local office is used

instead.


Control the AC version when the local office originates a dialog to the designated

network entity.

� For subscribers

None

MSOFTX3000V100R008

Additional Feature

Description



Page 51 of 131

Description

AC version flexible control refers to the control over the dialog originated by the local

office to the designated network entity. It is one of the functions of AC version and a

method of manual control of AC function. Through manual configuration, AC version

is originated for the dialog of the designated network entity. In this way, the message

generated due to the version negotiation can be reduced.

Before the local office originates a dialog request, if this function is enabled, the

destination address and AC name are used to search the table to obtain the configured

MAP version. If the searching is successful, the searched MAP version is used to

originate the dialog. Otherwise, the latest version supported by the local office is used

instead.

Enhancement

None.

Dependency

None.

1.42 WRFD-112100 SCTP multi-homing

Availability


Summary

In this function, an SCTP association can support multiple pairs of IP addresses, thus

providing multiple paths. Different paths are borne over different bearer planes to

provide backup and improve reliability. At present, an SCTP association of the

MSOFTX3000 supports two pairs of IP addresses (two local IP addresses and two peer

IP addresses), thus providing two paths. The active path is formed by local IP address

1 and peer IP address 1. Normally, the data is sent over the active path. The data is sent

over the standby path only when the active path is inaccessible. After the active path is

restored, the data is sent over the active path.


This function improves the reliability of links.

� For subscribers

None.

Description

In this function, an SCTP association can support multiple pairs of IP addresses, thus

providing multiple paths. Different paths are borne over different bearer planes to

MSOFTX3000V100R008

Additional Feature

Description



Page 52 of 131

provide backup and improve reliability. At present, an SCTP association of the

MSOFTX3000 supports two pairs of IP addresses (two local IP addresses and two peer

IP addresses), thus providing two paths. The active path is formed by local IP address

1 and peer IP address 1. Normally, the data is sent over the active path. The data is sent

over the standby path only when the active path is inaccessible. After the active path is

restored, the data is sent over the active path.

Enhancement

None.

Dependency

To implement this function, the peer NE must support the SCTP multi-homing.

1.43 WRFD-112300 ISUP for international interconnections

Availability


Summary

The MSOFTX3000 supports the interworking with international gateway offices of

other countries on the international signaling network through the ISUP signaling for

international interconnections. Thus, international calls of subscribers of a mobile

carrier need not pass through other international gateway offices in the home country,

such as the international gateway offices of fixed network carriers.


The MSC of mobile carriers can directly interwork with international gateway

offices of other countries through the ISUP signaling for international

interconnections. Thus, the transfer through other international gateway offices in

the home country is not required.

� For subscribers

None

Description

Through this function, the MSOFTX3000 supports:

� ISUP signaling for international interconnections and the interworking

between the international and the national ISUP signaling for the basic call

service and supplementary services

MSOFTX3000V100R008

Additional Feature

Description



Page 53 of 131

� Conversion of numbers in the international format and numbers in the

national format, such as calling numbers and general numbers

This function complies with ITU-T Q.767, Q.764, and Q.850.

Enhancement

None.

Dependency

The peer equipment must also support the international ISUP signaling.

1.44 WRFD-112500 MTP policing

Availability


Summary

The MTP policing function enables the MSOFTX3000 to determine whether to

discard the messages received from other NEs at the MTP layer based on the NI, DPC,

OPC, SI, signaling link set, and traffic.


This function is helpful to enhance the security of signaling network.

� For subscribers

None

Description

The function serves the following purposes:

� Preventing other NEs from using the MSOFTX3000 as the STP to transfer

messages

� Enabling the MSOFTX3000 to flexibly discard the messages received from other

NEs in the case of network congestion

To ensure normal operation of the signaling network, the MSOFTX3000 does not discard the

test messages and administration messages of the signaling network.

Enhancement

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 54 of 131

Dependency

None.

1.45 WRFD-112600 ANSI ISUP

Availability


Summary

The MSS must support the ANSI ISUP protocol in order to interwork with the ANSI

ISUP networks in areas such as the North America.


Meet the requirements for interworking with the ANSI ISUP networks in areas

such as the North America.

� For subscribers

None

Description

The MSS must support the ANSI ISUP protocol in order to interwork with the ANSI

ISUP networks in areas such as the North America.

ANSI MSC Server

ANSI MSC Server

ITU-T MSC Server

ANSI PSTN

ANSI Inter-PLMN

MSS

MSOFTX3000V100R008

Additional Feature

Description



Page 55 of 131

� The MSS can act as a TMSC server between two ANSI MSC servers.

� The MSS can act as a TMSC server between an ANSI MSC server and an ITU-T

MSC server.

� The MSS can act as a GMSC server between an ANSI MSC server and the ANSI

PSTN.

� The MSS can act as a GMSC server between an ANSI MSC server and other

ANSI PLMN.

� The MSS can act as a VMSC server to interwork with any ANSI office.

Enhancement

None.

Dependency

None.

1.46 WRFD-119800 SIP-I Based Nc

Availability


Summary

The SIP-I based Nc function allows the Nc interface to support the SIP-I protocol.


----Adapt to the trend of network development.

The IP transmission is the development trend of the network. Therefore, the

IP-based SIP-I signaling is the best choice.

----Improve the network interworking efficiency.

The SIP-I or SIP signaling is used for interworking between the CS domain

and the IMS or NGN. It is also used for interworking between NEs in the CS

domain. Therefore, the interworking efficiency of the signaling layer and user

layer can be greatly improved.

----Reduce maintenance cost.

The SIP-I or SIP signaling is used for interworking between the CS domain

and the IMS or NGN, which helps to cut investment and reduce maintenance

cost.

� For subscribers

MSOFTX3000V100R008

Additional Feature

Description



Page 56 of 131

None

Description

The SIP-I based Nc interface inherits the following services from the legacy Nc

interface:

� Handover

� Basic call services implemented through interworking between the SIP-I

signaling and BICC/ISUP signaling or external SIP networks

� Precondition

� SIP over SCTP

� Out of Band Transcoder Control (OoBTC)

� Data services

� Video Phone (VP) calls

� Dual-tone multifrequency (DTMF)

� Supplementary services

The typical networking of the SIP-I based Nc function is shown in Figure 1-4.

Figure 1-4 Typical networking of the SIP-I based Nc function

PSTN/ISDN

PLMN

(TDM)

PSTN/ISDN

PLMN

(TDM)

MSC

Server GMSC

Server

UTRAN

(IP)

UTRAN

Mc Mc

RANAP /IP -

ISUP

MGW Iu UP

SIP

MGW Nb

IMS

SIP-I /Nc

(IP)

� Handover

The SIP-I based Nc function provides only the inter-MSC handover, including:

− Basic inter-MSC handover

− Subsequent inter-MSC handover back to the anchor MSC

− Subsequent inter-MSC handover back to a third MSC

− Inter-MSC handover due to direct reattempt

− Inter-MSC handover due to subsequent channel assignment after the

inter-MSC signaling handover

The basic inter-MSC handover procedure is shown in Figure 1-5.

MSOFTX3000V100R008

Additional Feature

Description



Page 57 of 131

Figure 1-5 Basic Inter-MSC handover procedure

� Basic call services implemented through interworking between the SIP-I

signaling and BICC/ISUP signaling or the external SIP networks

In the basic call flow, the SIP-I based Nc function adopts the transparent mode to set

up bearers. It selects the MGW in three manners: the optimized MGW selection,

deferred MGW selection and MGW bypass.

The basic call flow is shown in Figure 1-6.

MSOFTX3000V100R008

Additional Feature

Description



Page 58 of 131

Figure 1-6 Basic call flow

� Precondition

Precondition is a bearer resource reservation mechanism that is introduced to improve

the call completion rate.

The SIP-I based Nc function uses an attribute line defined in the Session Description

Protocol (SDP) to support the precondition. If the negotiation result indicates that the

precondition is supported, the bearer resource is reserved before the callee is alerted.

In this way, calls will not be dropped because of resource shortage. Consequently, the

call completion rate is increased and subscriber satisfaction is improved.

� SIP-I over SCTP

Compared with the SIP over UDP, the SIP-I over SCTP delivers higher reliability and

transmission efficiency. Through the SIP-I over SCTP, the management and

maintenance (such as alarms and performance measurement) of SCTP links are

processed by the SIP signaling.

� OoBTC

OoBTC mechanism aims to achieve the Transcoder Free Operation (TrFO) in the SIP-I

based Nc function. The SIP-I based Nc function uses an attribute line defined in the

SDP to support the OoBTC.

� VP call

Identified by the ISUP Body field of the SIP-I signaling, the VP call service supports

only the Clearmode codec.

If the fallback of a VP call is supported, the voice codec is contained in the SIP

message to implement the voice codec negotiation during the VP call setup and

MSOFTX3000V100R008

Additional Feature

Description



Page 59 of 131

provide the negotiation result for subsequent fallback of VP call. The SIP-I based Nc

function supports the fallback of VP calls caused by an inter-MSC handover.

The VP call flow is shown in Figure 1-7.

Figure 1-7 VP call flow

� Data services

The SIP-I based Nc function provides the following codec for TS61 and TS62 fax

services:

− Clearmode codec

− 2198 redundancy codec

− G.711a codec

− G.711u codec

When the Clearmode codec is used, the service type is obtained through the ISUP

Body field of the SIP-I signaling.

The fax service flow is shown in Figure 1-8.

MSOFTX3000V100R008

Additional Feature

Description



Page 60 of 131

Figure 1-8 Fax service flow

Enhancement

None.

Dependency

None.

1.47 WRFD-121600 Malicious SMS warning

Availability


Summary

The charging mode of the SM origination service for Prepaid Service (PPS)

subscribers of China Mobile fails to satisfy the requirement for some subscribers to

send abundant SM advertisements within a short time using the dedicated equipment.

The sending mode of SM advertisements originated from the dedicated equipment

causes great interference on network running. Therefore, it is required to discriminate

these malicious SMs through warning so that the operator can take corresponding

measures.


Obtain the list of malicious SM subscribers and avoid further losses by taking

corresponding measures.

� For subscribers

MSOFTX3000V100R008

Additional Feature

Description



Page 61 of 131

None

Description

The function generates warning for all malicious SM subscribers, without

distinguishing prepaid service subscribers and postpaid service subscribers. Within the

statistical time period, the system only sends the warning to each malicious MS

subscriber once to avoid frequent warning.

In the MSOFTX3000, the subscriber can discriminate possible malicious SM

subscribers by configuring the threshold of SMs originated by a subscriber within a

time period. That is, within the statistical time period, if the number of SMs sent by a

subscriber exceeds the threshold, the MSOFTX3000 reports warning.

Enhancement

None.

Dependency

None.

1.48 WRFD-121700 Union trace

Availability


Summary

The function supports mobile NEs to trace local HLR-based subscribers. That is, the

subscriber tracing task can be created and deleted in the HLR. The HLR notifies the

current MSC or VLR where the current subscriber is located to trace. The MSC

generates changes each time (including location update, power-on or power-off, call

origination and termination, and SM origination and termination) of the traced

subscriber as a tracing file and saves it in the background host. If required in the future,

the maintenance personnel can use the file to locate problems.


Joint subscriber tracing is effective to remove designated faults, especially in

handing subscriber complaints.

� For subscribers

None

Description

The function supports mobile NEs to trace local HLR-based subscribers. That is, the

subscriber tracing task can be created and deleted in the HLR. The HLR notifies the

MSOFTX3000V100R008

Additional Feature

Description



Page 62 of 131

current MSC or VLR where the current subscriber is located to trace. The MSC

generates changes each time (including location update, power-on or power-off, call

origination and termination, and SM origination and termination) of the traced

subscriber as a tracing file and saves it in the background host. If required in the future,

the maintenance personnel can use the file to locate problems.

Enhancement

None.

Dependency

None.

1.49 WRFD-131600 Special Number Matching

Availability


Summary

The function determines whether to trigger IN services when an IN subscriber dials the

number of special services or an IN call is forwarded to the number.


Reduce the volume of data to be configured and, therefore, cut down the

maintenance cost.

� For subscribers

None

Description

The function is used to configure the number of special services. It also determines

whether to trigger IN services when an IN subscriber dials the number or an IN call is

forwarded to the number. The original number configuration adopts exact matching

mode. Once there are many such numbers, you need to configure plenty of data. To

reduce the volume of data to be configured, reset the number matching mode to

"Prefix (maximal matching) + Minimal length of number + Maximal length of

number".

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 63 of 131

1.50 WRFD-131700 Routing Based on Time Section

Availability


Summary

The function is used to change routing analysis number based on time section

information, that is, the routing number is changed with variation of time sections.

Compared with the original number change function, time section distribution

processing is added. With the function, a number can be changed into different

numbers at different time sections.


The function offers more choices for number change. It can help carriers provide

new services related to the function.

� For subscribers

None

Description

Compared with the original number change table, a number change table of time

section distribution is added. To implement the function, the time section information

is associated with the number change mode defined in the number change table. The

time section information is expressed in a time section (unit: hour) of a day of a week

(for example, Monday, Tuesday).

Enhancement

None

Dependency

None

1.51 WRFD-131900 Call loop control

Availability


Summary

The call loop control service provides a solution to avoid the inter-office oscillation,

and thus to improve the adaptability of the system.

MSOFTX3000V100R008

Additional Feature

Description



Page 64 of 131


The carrier can control the usage of the call loop control service to guarantee the

network quality. Thus, the carrier can provide services with high quality for

subscriber.

� For subscribers

None

Description

In the current network, complicated networking and various data configurations may

lead to errors in the data consistency offices. Thus, unreasonable call loop may occur,

which results in the inter-office oscillation. This kind of call loop may occupy a large

number of trunk circuits. The calls, however, still cannot be connected. Therefore, it is

necessary for the core switch (the MSOFTX3000) to provide a mechanism to avoid the

inter-office oscillation caused by improper data configuration.

The call loop control function is implemented in the MSC server. Logically, the call

loop control function comprises two parts:

� Control (decision-making): This is a complicated process. It is used to analyze

whether it is necessary to control the call loop based on the original call flow, the

special service flow, and the data configuration of call loop control.

� Processing (execution): The incoming office direction and the outgoing office

direction are compared. Thus, the corresponding processing is carried out based

on the control.

The following figure shows the service flow of the call loop control. (The red lines

represent the call path between the MS and the MSC. The blue lines represent the call

path between the MSCs.)

MSOFTX3000V100R008

Additional Feature

Description



Page 65 of 131

Figure 1-9 Call loop control flow

MS MSC2 MSC1 MSC3

P1

MS

Carry out callloop control?

Process for the

call loop control

P2

P3

P4

P5

Yes No

� Call path: P1 -> P3, P1 -> P4, P1 -> P5

Scenario: A local MS originates a call. Regardless of whether the call is outgoing,

MSC 1 does not perform the call loop control, but rather connect the call based

on the original call flow.

� Call path: P2 -> P3

Scenario: MSC 1 receives an incoming call. Based on the existing service flow

and the data configuration of call loop control, MSC 1 determines whether to

perform the call loop control. In this case, the incoming office direction is

different from the outgoing office direction. Therefore, MSC 1 does not restrict

the call regardless whether the call loop control is carried out.


Scenario: MSC 1 receives an incoming call. In this case, the incoming office

direction is the outgoing office direction. Based on the existing service flow and

the data configuration of call loop control, MSC 1 determines whether to perform

the call loop control. If call loop control must be carried out, MSC 1 restricts the

call. Otherwise, MSC 1 connects the call.


Scenario: MSC 1 receives an incoming call and the callee is a local subscriber.

That is, the call is not outgoing. In this case, MSC 1 does not carry out call loop

control and connects the call.

� Special cases

The process of determining whether the call loop control must be carried out is

complicated. The original call flow, the special service flow, and the data

configuration of the call loop control are involved. The MSC, however, does not

restrict the permissible call loops in the following cases:

MSOFTX3000V100R008

Additional Feature

Description



Page 66 of 131

− During an IN overlay incoming call, after the IN service is triggered in the

local office, the number is sent back to the originating office for processing.

Therefore, the loop of overlay incoming calls is not restricted.

− The local office cannot function as the SSP. Thus, calls must be routed out of

the office through overlay. Therefore, the loop of overlay outgoing calls is not

restricted.

− The local office forwards a call.

− The called number is changed. Number change can be carried out in several

phases, such as calling number analysis and special processing of the number

prefix. If the numbers are of the same type, to identify the number change, the

number formats can be compared.

− The roaming number is allocated by the local office during a call. For example,

the originating office cannot allocate the roaming number. Therefore, the call

must be routed to the gateway office to obtain the roaming number. The

roaming subscriber, however, is served by the originating office.

− During an outgoing call, the dual-seizure of the circuit occurs. Therefore, the

call is rerouted. In this case, the call loop control is not carried out during

rerouting.

The services in the six special cases can be applied when the same prefix is dialed

continuously in the same office direction. Therefore, if any of the six special cases

exists in the call scenarios described previously, the call loop control is not carried out

by default. You can configure the data however to require the system to carry out the

call loop control.

In addition, the call loop control is not carried out for the establish temporary

connection (ETC), ring back tone (RBT) service, and diversion function unit (DFU).

The service flow shows that the data configuration has the highest priority. Even if the six

special cases exist during a call, whether the call loop control must be carried out is determined

based on the data configuration.

Enhancement

None

Dependency

None

1.52 WRFD-132200 Low cost routing

Availability


Summary

This function enables the MSC to preferentially select the route with the minimum

transmission costs.

MSOFTX3000V100R008

Additional Feature

Description



Page 67 of 131


This function enables the MSC to classify the routes according to their

transmission costs. It helps to lower the OPEX for carriers.

� For subscribers

None

Description

This function enables the MSC to classify the routes to a destination according to their

transmission costs. During route selection, the MSC preferentially selects the route

with the minimum transmission costs.

An example is provided in Figure 1-10.

Figure 1-10 Example of the Low cost routing function

As shown in the preceding figure, there are three routes between the MSC and the

local exchange. Among these routes, route B has the lowest transmission costs. If a

subscriber makes a call from the MSC to the local exchange, route B is selected

preferentially.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 68 of 131

1.53 WRFD-140100 Multiple signaling points

Availability


Summary

One logical node can become multiple signaling points virtually and each signaling

point can be used separately.


After one logical node becomes N × signaling points virtually, number of links

between this node and far signaling points can reach N × 16 instead of 16, and

circuit number can reach N × 4096 instead of 4096 to satisfy large-capacity

requirements. When one of signaling points and one of far signaling points are

congested or faulty, other signaling points are not impacted. Therefore, reliability

is enhanced.

� For subscribers

None.

Description

One logical node can become multiple signaling points virtually and each signaling

point can be used separately.

Enhancement

None.

Dependency

None.

1.54 WRFD-140200 TDM 2M signaling link

Availability


Summary

Use bandwidth of one 2M E1 cable as one 2M bits/s signaling link connecting with

other signaling points.

MSOFTX3000V100R008

Additional Feature

Description



Page 69 of 131


When 2 Mbit/s links are applied between signaling points with large signaling

flows, costs can be lowered and networking can be simplified. Additionally, if

MSOFTX3000 does not support multiple signaling points, one signaling point

can support up to 16 links. When sixteen 64K links cannot satisfy traffic

requirement, application of 2M links can better satisfy flow requirements.

� For subscribers

None

Description

Use bandwidth of one 2M E1 cable as one 2M bits/s signaling link connecting with

other signaling points.

Enhancement

None

Dependency

None

1.55 WRFD-140300 Embedded STP function

Availability


Summary

When MSOFTX3000 works as VMSC/GMSC device and STP device, SCCP and

MTP can be transferred between other signaling points. Transferred signaling can be

transferred directly at MTP layer or signaling at SCCP layer translated by SCCP GT.

MSOFTX3000 can also work as STP equipment medium/small-sized STP device.


In the case of low signaling transfer flow, STP mode is also adopted so that

network establishment costs are saved.

� For subscribers

None

MSOFTX3000V100R008

Additional Feature

Description



Page 70 of 131

Description

When MSOFTX3000 works as VMSC/GMSC device and STP device, SCCP and

MTP can be transferred between other signaling points. Transferred signaling can be

transferred directly at MTP layer or signaling at SCCP layer translated by SCCP GT.

MSOFTX3000 can also work as STP equipment medium/small-sized STP device.

Enhancement

None

Dependency

None

1.56 WRFD-140800 A interface Satellite Transmission Mode

Availability


Summary

Support signaling at A interface to be transmitted through satellite. Therefore,

networking flexibility is enhanced to satisfy requirements of remote areas or countries

with many islands.


Satisfy requirements of remote areas or countries with many islands.

� For subscribers

None

Description

Support signaling at A interface to be transmitted through satellite. Therefore,

networking flexibility is enhanced to satisfy requirements of remote areas or countries

with many islands.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 71 of 131

1.57 WRFD-141000 Mc interface Satellite Transmission Mode

Availability


Summary

MSOFTX3000 can support signaling at Mc interface to be transmitted through

satellite. With this feature, networking flexibility and geography adaptation of

MSOFTX3000 are enhanced.


When MSC Server and MGW are far from each other, this function enables

signaling at Mc interface to be transmitted through satellite.

� For subscribers

None

Description

MSOFTX3000 can support signaling at Mc interface to be transmitted through

satellite. With this feature, networking flexibility and geography adaptation of

MSOFTX3000 are enhanced.

Enhancement

None

Dependency

None

1.58 WRFD-141100 Inverse Multiplexing ATM(IMA,ATM2M)

Availability


Summary

MSOFTX3000 supports ATM data over E1 transmission, called Inverse Multiplexing

ATM(IMA,ATM2M). Protocol stack is MTP3B/SAAL/ATM/E1, upper protocol can

be MAP.

MSOFTX3000V100R008

Additional Feature

Description



Page 72 of 131


Reuse TDM transmission resource.

� For subscribers

None

Description

MSOFTX3000 supports ATM data over E1 transmission, called Inverse Multiplexing

ATM(IMA,ATM2M). Protocol stack is MTP3B/SAAL/ATM/E1, upper protocol can

be MAP.

Enhancement

None

Dependency

None

1.59 WRFD-141200 T1 Digital Trunk (ISUP/PRA)

Availability


Summary

T1 cable is a type of cable used for the voice or data transmission and is widely used

in areas such as North America.


Improve the interconnection and interworking abilities of the network.

� For subscribers

None

Description

T1 cable is different from E1 cable used in other areas. The following table lists the

major physical and standard difference between the T1 cable and E1 cable.

Type Resistance Available timeslots Bandwidth

T1 100 ohm 24 1.5M

E1 75 ohm or 120 ohm 32 (Timeslot 0 is unavailable) 2.0M

MSOFTX3000V100R008

Additional Feature

Description



Page 73 of 131

ISUP supports the circuit management of T1 cables on the MGW.

PRA supports the circuit management of T1 cables on the MGW.

Enhancement

None

Dependency

Equipment of the peer office supports the T1 cable transmission.

1.60 WRFD-141300 Signaling SSP (LOOPBACK)

Availability


Summary

In the network using ISUP for networking, if only signaling transmission but not voice

transmission is needed (especially when the toll call transmission resource is not

required), the signaling SSP (Loopback) function can be used to reduce the

unnecessary voice transmission trunk between network entities and save the cost of

network construction.


Save the toll call transmission resource and the network construction cost.

� For subscribers

None

Description

In the network using ISUP for networking, if only signaling transmission but not voice

transmission is needed (especially when the toll call transmission resource is not

required), the signaling SSP (Loopback) function can be used to reduce the

unnecessary voice transmission trunk between network entities and save the cost of

network construction.

For example, MSCs need to trigger the IN service through the overlaid SSP. Some

MSCs are far away from the SSP. Thus, using the signaling SSP function can save the

toll call transmission resource between the end office and SSP.

Enhancement

None

MSOFTX3000V100R008

Additional Feature

Description



Page 74 of 131

Dependency

Corresponding data configuration is needed on the peer MSC. Two trunk groups and

the transmit/receive loopback of speech path must be configured. The CIC

configuration varies with the requirement of local MSC.

1.61 WRFD-141400 Route between MGWs in one MSC

Availability


Summary

MGW path refers to the route between the MGW of the calling party and the MGW of

the called party. The source MGW and destination MGW is managed by the same

MSC Server. When there are multiple MGW paths between the source MGW and

destination MGW, the route with the shortest span is generally selected. The function

of selecting the route randomly, by percentage, or by turns is also supported.


Allow more flexible networking.

� For subscribers

None

Description

MGW path refers to the route between the MGW of the calling party and the MGW of

the called party. The source MGW and destination MGW is managed by the same

MSC Server. When there are multiple MGW paths between the source MGW and

destination MGW, the route with the shortest span is generally selected. The function

of selecting the route randomly, by percentage, or by turns is also supported.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 75 of 131

1.62 WRFD-141500 Connecting MGWs in one MSC by transit switch

Availability


Summary

In the 3GPP R4 layered architecture, an MSC Server can manage several MGWs. In

the common networking mode, these MGWs are interconnected. MSOFTX3000

supports the networking mode that multiple MGWs in the same MSC are

interconnected through transit switch instead of directly connected.


Allow more flexible networking.

� For subscribers

None

Description

In the 3GPP R4 layered architecture, an MSC Server can manage several MGWs. In

the common networking mode, these MGWs are interconnected. MSOFTX3000

supports the networking mode that multiple MGWs in the same MSC are

interconnected through transit switch instead of directly connected.

Enhancement

None

Dependency

None

1.63 WRFD-141605 Manual load balancing

Availability


Summary

This function is used to transfer subscribers from certain MSC servers in the MSC

Pool to other MSC servers by means of operation and maintenance. When this

function is enabled, you can manually balance the load of the MSC servers.

MSOFTX3000V100R008

Additional Feature

Description



Page 76 of 131


Enable manually balancing the load of the MSC servers

� For subscribers

None

Description

This function is used to transfer subscribers from certain MSC servers in the MSC

Pool to other MSC servers by means of operation and maintenance. When this

function is enabled, you can manually balance the load of the MSC servers.

Enhancement

None

Dependency

None

1.64 WRFD-141606 Call termination solution

Availability


Summary

When an MSC server in the MSC Pool fails, this function enables the call made to a

subscriber served by the faulty MSC server to be connected successfully.


Enable the call made to a subscriber served by the faulty MSC server to be

connected successfully, so as to supply high-level service quality.

� For subscribers

Enjoy better services.

Description

When an MSC server in the MSC Pool fails, this function enables the call made to a

subscriber served by the faulty MSC server to be connected successfully.

Enhancement

V100R007C02 Version add: First call to a subscriber served by the faulty MSC server

is connected successfully.

MSOFTX3000V100R008

Additional Feature

Description



Page 77 of 131

Dependency

None

1.65 WRFD-142500 Multi-Operator Core Network

Availability


Summary

The Multi-Operator Core Network (MOCN) is a solution that provides the shared

radio access network (RAN).

On the traditional network, one RAN is connected to one CN only. In the MOCN

networking, the RAN can be connected to multiple CNs.


Multiple carriers can share the 3G access network, which improves the usage

of the radio resources and helps to reduce the CAPEX.

The networks are shared. At the same time, the CNs can run independently.

� For subscribers

None

Description

What makes MOCN technically possible is that the RNC in the RAN identifies the

home CN of a subscriber by the IMSI-PLMN relation. With the MOCN function,

multiple carriers can share the same RAN and thus drive down CAPEX.

For the 3GPP R6 UE, the MOCN function is implemented through interworking

between the UE and the RNC.

For the UE earlier than 3GPP R6, the MOCN function is implemented through

interworking between the RNC and the CN.

The typical networking of the MOCN is shown in Figure 1-11.

MSOFTX3000V100R008

Additional Feature

Description



Page 78 of 131

Figure 1-11 Typical networking of the MOCN

In the MOCN networking, a reroute procedure is added between the CN and the RNC

to ensure that the UE is connected to only the home PLMN. The reroute procedure is

implemented through new information elements (IEs) contained in the original Initial

UE message and the Direct Transfer message.

Enhancement

None

Dependency

The RNC must support the MOCN function.

The BSC does not support the MOCN function.

1.66 WRFD-150400 OVERLAY SSP

Availability


Summary

When other offices do not support CAMEL SSP function, calls can be routed to local

office and IN services are triggered in local office. MSOFTX3000 features enhanced

SSP functions and can be upgraded to target network fast. Meantime, MSOFTX3000

supports CSI and Overlay trigger modes.

MSOFTX3000V100R008

Additional Feature

Description



Page 79 of 131


When other MSCs even GMSCs of local network cannot upgrade to SSP, IN

services can be provided fast in the case that MOSFTX3000 overlays to trigger

IN services.

� For subscribers

Enjoy IN services.

Description

When other offices do not support CAMEL SSP function, calls can be routed to local

office and IN services are triggered in local office. MSOFTX3000 features enhanced

SSP functions and can be upgraded to target network fast. Meantime, MSOFTX3000

supports CSI and Overlay trigger modes.

Enhancement

None

Dependency

None

1.67 WRFD-160200 Equivalent PLMN (ePLMN)

Availability


Summary

After 3G MS implements location update, MSC sends location update acceptance

messages to MS and carries some parameters to direct MS to the to-be-selected

preferential PLMN. If MS supports this feature, you can select MS-attach PLMN

controlled at network side.


In the case of multiple PLMNs, give priority to select special services of PLMN.

� For subscribers

Have priority to select serving network through setting.

Description

After 3G MS implements location update, MSC sends location update acceptance

messages to MS and carries some parameters to direct MS to the to-be-selected

MSOFTX3000V100R008

Additional Feature

Description



Page 80 of 131

preferential PLMN. If MS supports this feature, you can select MS-attach PLMN

controlled at network side.

Enhancement

None

Dependency

MS is required to support ePLMN.

1.68 WRFD-161800 Dialing without NDC

Availability


Summary

Allow end subscribers to dial MSISDN without NDC, namely connecting call through.


Allow subscribers to dial MSISDN that does not contain NDC to improve

subscriber satisfaction.

� For subscribers

Shorten length of dialed number.

Description

Allow end subscribers to dial MSISDN without NDC, namely connecting call through.

Enhancement

None

Dependency

None

1.69 WRFD-161900 Call reestablishment

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 81 of 131

Summary

When call is dropped due to poor signal at air interface, MS originates procedure of

CM service re-establishment within seven seconds. Network side re-establishes

connection to ensure service continuity.


Decrease call dropped rate and improve service quality.

� For subscribers

There is seldom call disconnection.

Description

When call is dropped due to poor signal at air interface, MS originates procedure of

CM service re-establishment within seven seconds. Network side re-establishes

connection to ensure service continuity.

Enhancement

None

Dependency

None

1.70 WRFD-162000 Pre-paging

Availability


Summary

When HLR requires local MSC to allocate roaming numbers for mobile called

subscribers roaming to local MSC, local MSC pre-pages mobile called subscriber. On

the premises of successful pre-paging, roaming numbers are returned to HLR.


Clear known and disconnected calls at the earlier stage of call proceeding to:

− Decrease invalid network resource usage. For example, circuit resources are

allocated during inter-office ISUP signaling proceeding.

− Decrease invalid call attempts.

− Improve connection rate.

− Speed up call establishment.

MSOFTX3000V100R008

Additional Feature

Description



Page 82 of 131

� For subscribers

End subscribers are unrelated.

Description

When HLR requires local MSC to allocate roaming numbers for mobile called

subscribers roaming to local MSC, local MSC pre-pages mobile called subscriber. On

the premises of successful pre-paging, roaming numbers are returned to HLR.

Enhancement

None

Dependency

None

1.71 WRFD-162100 Enhanced DCH

Availability


Summary

When an IN call is set up and sustained, if errors occur in the interaction between the

MSC and the SCP because the link message to the SCP is unreachable, SSP internal

timer expires, or the SSP internal resource is unavailable, the IN call is no longer

controlled by the SCP. The Default Call Handle (DCH) function can flexibly control

the call handling methods in this case.


When errors occur in the interaction between the MSC and the SCP, the DCH

function can flexibly control the subsequent call handling method according to

the operator’s requirements.

� For subscribers

None

Description

The handling methods include:

� Release the call by force.

� Continue the call by force.

� Use the default call handling method subscribed by the IN subscriber.

In the above case, operators can set the data so as to continue the call by force for

high-end IN subscribers or to release the call by force for low-end IN subscribers.

MSOFTX3000V100R008

Additional Feature

Description



Page 83 of 131

When the traffic is in the peak and the SCP response speed is reduced, such setting can

realize differential service, increase the call completion rate of high-end subscribers,

and improve the service quality.

Enhancement

None

Dependency

Billing center can process Free Call CDRs subsequently.

1.72 WRFD-162200 Continuity check

Availability


Summary

The continuity check (CC) is a function provided for managing SS7 circuits. The CC

signaling messages of SS7 are used to check whether voice signals can be transmitted

through the trunk circuits. Thus, the continuity of the trunk circuits can be checked.


The CC function can be used to improve the network quality and the call

completion rate.

� For subscribers

None

Description

If the CC function is not provided and wrong connection of inter-office trunks (crossed

pair) causes problems, such as cross-talking, one-way audio, and no audio, you have to

conduct troubleshooting through circuit self-loop, disconnection of trunks, or dialing

test of specified circuits. It is very inconvenient to use these methods. The CC function

however, can help to locate the cause of the trunk problems efficiently.

The CC initiator must connect the CC tone sender and the receiver to the send and the

receive paths respectively of the circuit. The CC receiver must connect the check-loop

to the send and the receive paths of the circuit. When the initiator sends a tone in the

send path and receives the tone in the receive path, and the transmission quality of the

received CC tone and the time limit of the transmission comply with Q.724, it

indicates that CC succeeds.

The MSOFTX3000 supports the CC during maintenance and that during calls. (The

MSOFTX3000 V100R006C02 and the later versions support the CC during the setup

of ISUP/TUP calls.

MSOFTX3000V100R008

Additional Feature

Description



Page 84 of 131

Enhancement

None

Dependency

The peer office must also support the CC.

1.73 WRFD-162300 Assign half rate channel by user priority

Availability


Summary

With this function, the MSC can set the Channel Rate and Type (channel type assigned)

in messages such as 2G Assignment Request and Handover Request based on the

subscriber category and terminal capability reported by the MS.

That is, assign subscribers with different priorities according to the subscriber category.

If the terminal capability reported by the MS shows that terminal supports both full

rate and half rate channels, the MSC will set the Channel Rate and Type to full rate

channel (8) for subscribers with high priority. For subscribers with high priority, the

BSC will always assign the full rate channel. For subscribers with low priority, the

BSC will set the channel type to support both full rate and half rate channels and the

full rate channel takes the precedence (10). When the load of BSC radio resource is

light, assign the full rate channel. When the load of BSC radio resource is heavy,

assign the half rate channel.


Ensure the Quality of Service for subscribers with high priority when the traffic is

heavy.

� For subscribers

None

Description

With this function, the MSC can set the Channel Rate and Type (channel type assigned)

in messages such as 2G Assignment Request and Handover Request based on the

subscriber category and terminal capability reported by the MS.

That is, assign subscribers with different priorities according to the subscriber category.

If the terminal capability reported by the MS shows that terminal supports both full

rate and half rate channels, the MSC will set the Channel Rate and Type to full rate

channel (8) for subscribers with high priority. For subscribers with high priority, the

BSC will always assign the full rate channel. For subscribers with low priority, the

MSOFTX3000V100R008

Additional Feature

Description



Page 85 of 131

BSC will set the channel type to support both full rate and half rate channels and the

full rate channel takes the precedence (10). When the load of BSC radio resource is

light, assign the full rate channel. When the load of BSC radio resource is heavy,

assign the half rate channel.

Enhancement

None

Dependency

None

1.74 WRFD-162400 Enhanced subscriber category g

Availability


Summary

On the existing networks, there are many applications using Calling Party‘s Category,

E_CATEGORY, NAEA_CODE, or SS_CODE for special routing. Calling Party‘s

Category, E_CATEGORY, NAEA_CODE, or SS_CODE is treated as a subscriber

category.

Calling Party‘s Category refers to the one defined in the Q.763 protocol.

E_CATEGORY is a special indicator bit of a byte carried by the extension container

and is used to identify the special category of a subscriber. SS_CODE refers to the

customized supplementary service code defined in the protocol. When a subscriber

subscribes to different Calling Party‘s Category, E_CATEGORY, NAEA_CODE, or

SS_CODE, different processing, such as selection of different route and suppression of

mobile originated IN service, will be carried out.


Customize special services using Calling Party‘s Category, E_CATEGORY,

NAEA_CODE, or SS_CODE.

� For subscribers

None

Description

In the MSOFTX3000, all of Party‘s Category, E_CATEGORY, NAEA_CODE, and

SS_CODE are termed as enhanced subscriber category and a subscriber

comprehensive service processing table is added. This table is used to complete the

following processing based on Calling Party‘s Category, E_CATEGORY,

NAEA_CODE, or SS_CODE:

� Conversion of calling and called numbers

MSOFTX3000V100R008

Additional Feature

Description



Page 86 of 131

� Determining whether to suppress the OCSI or DCSI intelligent service

� Determining whether to overwrite the DialNumber

In addition, the enhanced subscriber category together with the service check type can

provide different handling methods, such as failure handling. The announcement

played during the failure handling can be specified by setting the failure source code.

The following lists the specific applications:

� Before a prepaid service number is used, the E_CATEGORY is set to 10 upon

subscription. No matter what number that the subscriber dials for the first time,

the call is forwarded to a service center for registration. After the successful

registration, the service center automatically modifies the value of

E_CATEGORY.

The above function can be realized by carrying out special number change

processing on the E_CATEGORY10 through the comprehensive service

processing table.

� The service center sets the E_CATEGORY of a defaulting post payment

subscriber to 34. No matter what number that the subscriber dials, the call is

forwarded to a service center and the service center informs the subscriber of the

arrearage.


processing on the E_CATEGORY34 through the comprehensive service

processing table.

� If the SS_CODE is set to F5 upon subscription, when the subscriber dials a toll

call, operator 1 (access code: 800) will be selected. If the SS_CODE is set to F6

upon subscription, when the subscriber dials a toll call, operator 2 (access code:

801) will be selected.


processing on the SS_CODE5 and SS_CODE6 through the comprehensive

service processing table, respectively adding prefix 800 and 801 to the called

number, and then configuring different number analysis schemes and route

selection codes.

� The combination of E_CATEGORY and ODB is used for playing announcement.

Different E_CATEGORY can match the ODB sent from the HLR to provide

announcement playing. Assume that when E_CATEGORY is set to 0, it indicates

the ordinary subscriber and when E_CATEGORY is set to 12, it indicates the

pre-paid subscriber.

When an ordinary subscriber is delinquent, the HLR sends the

ODB_BOIC&ODB_BAOC to identify that the subscriber is delinquent. When

the subscriber originates a call, the MSC restricts the call and plays the

announcement "Your mobile phone is out of service due to owning fee."

When a pre-paid subscriber is delinquent, the HLR sends the

ODB_BOIC&ODB_BAOC to identify that the subscriber is delinquent. When

the subscriber originates a call, the MSC restricts the call and plays the

announcement "Sorry, your balance has little money. Please charge."

The MSC can restrict calls through the combination of the E_CATEGORY and

the ODB BAOC or ODB BOIC by setting the subscriber's integrated service

processing data. The MSC also can specify the cause value of disconnection and

the failure code. Different announcements can be played for the same failure

cause.

MSOFTX3000V100R008

Additional Feature

Description



Page 87 of 131

Enhancement

None

Dependency

The HLR must support the Calling Party‘s Category, E_CATEGORY, NAEA_CODE,

and SS_CODE.

1.75 WRFD-162500 Daylight saving time

Availability


Summary

Some countries require the system to support the auto adjustment of daylight saving

time. That is, users can specify the start time and end time of daylight saving time, as

well as the adjustment cycle (the adjustment amplitude when the daylight saving time

comes, for example, one hour). When the system time reaches the start time of

daylight saving time, the system automatically sets the time an adjustment cycle

backward. For example, if the adjustment cycle is one hour and the current time is

09:00, the time will be set one hour backward and become 08:00. When the system

time reaches the end time of daylight saving time, the system automatically sets the

time an adjustment cycle forward. For example, if the adjustment cycle is one hour

and the current time is 09:00, the time will be set one hour forward and become 10:00.


Ensure the accuracy of local time.

� For subscribers

None

Description

Some countries require the system to support the auto adjustment of daylight saving

time. That is, users can specify the start time and end time of daylight saving time, as

well as the adjustment cycle (the adjustment amplitude when the daylight saving time

comes, for example, one hour). When the system time reaches the start time of

daylight saving time, the system automatically sets the time an adjustment cycle

backward. For example, if the adjustment cycle is one hour and the current time is

09:00, the time will be set one hour backward and become 08:00. When the system

time reaches the end time of daylight saving time, the system automatically sets the

time an adjustment cycle forward. For example, if the adjustment cycle is one hour

and the current time is 09:00, the time will be set one hour forward and become 10:00.

MSOFTX3000V100R008

Additional Feature

Description



Page 88 of 131

Enhancement

None

Dependency

None

1.76 WRFD-162600 Mobile Virtual Network Operator (MVNO)

Availability


Summary

MVNO is an operating mode that multiple carriers share the core network (CN) and

access network. Currently, the MSOFTX3000 supports the five scenarios defined by

the TR22.951 (V6.1.0) specifications. This function is available based on the

availability of these techniques: Iu-Flex, network sharing in connected mode, NITZ,

MVNO-based user number control, and charging for different carriers.


Carriers can share networks. Carriers without network infrastructure can operate

virtually through leasing networks of other carriers.

� For subscribers

None

Description

MVNO is an operating mode that multiple carriers share the core network (CN) and

access network. Currently, the MSOFTX3000 supports the five scenarios defined by

the TR22.951 (V6.1.0) specifications. This function is available based on the

availability of these techniques: Iu-Flex, network sharing in connected mode, NITZ,

MVNO-based user number control, and charging for different carriers.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 89 of 131

1.77 WRFD-162700 Multiple time zones

Availability


Summary

One MSC Server can cover an area having multiple time zones or an area having

different daylight saving time. The MSC Server can automatically adjust the time

stamp on the CDR according to the time zone and daylight saving time setting. This

function ensures that the recorded time is the same as the local time where the

subscriber locates, guarantees the accuracy of time reporting, and updates the time on

the UE to the time of the area where the subscriber locates.



different daylight saving time, so carriers can reduce the costs.

� For subscribers

None

Description


different daylight saving time. The MSC Server can automatically adjust the time

stamp on the CDR according to the time zone and daylight saving time setting. This

function ensures that the recorded time is the same as the local time where the

subscriber locates, guarantees the accuracy of time reporting, and updates the time on

the UE to the time of the area where the subscriber locates.

Enhancement

None

Dependency

None

1.78 WRFD-162900 Camel trigger based on INClassMark

Availability


MSOFTX3000V100R008

Additional Feature

Description



Page 90 of 131

Summary

This function indicates whether a user is an IN subscriber by using the SS-CODE

information element (IE) in the call forwarding subscription data. If the SS-CODE IE

is set to plmn-specificSS-4 (0xF4), this is an IN subscriber; if not, this is a common

subscriber. This data is inserted into the VLR during location updating procedure.


The operator can provide caller subscription IN services by using extended

supplementary services and configuring data.

� For subscribers

Subscribers can subscribe to caller IN services as needed.

Description

If the user subscription data includes the previously mentioned extended

supplementary service code in a call, the MSOFTX3000 adds a service attribute code

SERVICE 13 for the subscriber. Then, you must configure the Caller Attribute

Processing table and the Caller Feature Analysis table:

� 1. In the Caller Attribute Processing table, map the service attribute SERVICE 13

to a caller feature.

� 2. In the Caller Feature Analysis table, set the Processing type to Trigger

NCSI_DP2.

When the configuration is completed, IN services can be successfully triggered for the

subscriber.

Example:

During location update, the user subscription data is inserted into the VLR. The

MSOFTX3000 determines whether the user is an IN subscriber according to the

SS-CODE IE in the call forwarding subscription. If so, the MSOFTX3000

automatically adds the service attribute SERVICE 13 for the user.

When the user originates a call, the MSOFTX3000 triggers NCSI DP2 IN service

according to the settings in the Caller Attribute Processing table and Caller Feature

Analysis table.

If a user subscribes to trigger IN services through INClassMark, and the call

forwarding (CF) service:

� When the MSOFTX3000 acquires the called MSRN from the HLR in an early

forwarding, the subscription data is returned to the MSOFTX3000 through an

SRI message. After the call is forwarded, the MSOFTX3000 determines whether

to trigger IN services for the subscriber according to the extended supplementary

service code. If so, it triggers the MF IN flow according to settings in the Caller

Attribute Processing table and Caller Feature Analysis table. If not, it forwards

the call in the common flow.

� In a late forwarding, the user data is inserted into the VLR during location

updating procedure. After the call is forwarded, the MSOFTX3000 determines

whether to trigger IN services for the subscriber according to the extended

MSOFTX3000V100R008

Additional Feature

Description



Page 91 of 131

supplementary service code in the VLR. If so, it triggers the MF IN flow

according to settings in the Caller Attribute Processing table and Caller Feature

Analysis table. If not, it forwards the call in the common flow.

Enhancement

None

Dependency

The HLR must support the subscription of extended supplementary services.

1.79 WRFD-163100 User differentiated service

Availability


Summary

User differentiated service can decide service priority level according to the

subscription information (Category, eMLPP, CARP), service type (emergency call,

voice service, transparent data service, non-transparent data service, facsimile), access

network type (BSC, RNC) and the called number of the subscriber. For IN subscribers,

the MSC can define service brands by using different combinations of the four key

fields: service key, caller number, called number, and SCFID. In addition, it can define

the processing type, call restriction or flow control, of this brand when the SSP is

overloaded. A specific priority level can be set to each service brand. The function

allows the operator to define strategies for different subscribers and scenarios.


This function allows the operator to adopt user strategies flexibly. When the

network is congested, high-end users can enjoy better QoS, such as short

connection time, good voice quality and high connection rate. For low-end users,

resources may be pre-empted and the voice codec rate may be decreased.

� For subscribers

None

Description

The function can

� assign a priority level and pre-empt resources in radio channels. The function can

assign a specific priority level to a mobile subscriber and the subscriber can select

a priority level for each specific call within the authority. Calls of different

priority levels are set up in different modes. Calls of high priority level are set up

faster than those of low priority level, or even allowed to pre-empt resources.

When the network resources (including processing ability, signaling channels and

MSOFTX3000V100R008

Additional Feature

Description



Page 92 of 131

service channels) are highly occupied, the calls of high priority level can

pre-empt the resources occupied by calls of low priority. Preemption can

disconnect ongoing calls of low priority level by force to connect the calls of high

priority level.

� select the corresponding radio channel type (full rate channel or half rate channel)

according to the service priority.

� grand the access of high priority service when the MSOTX3000 lacks resources.

The function ensures more support to high priority services.

� improve the pre-emption capability of high priority services in pre-empting trunk

resources from low priority services when the narrowband circuits are insufficient.

The function ensures that high priority services can gain resource support

efficiently.

Huawei MSOFTX3000 supports subscription information: CATEGORY, eMLPP,

CARP (in 3G networks), service key, and SCFID.

Enhancement

None

Dependency

The HLR must support the subscription of caller category (all HLRs support this

function), eMLPP, CARP, and IN subscription information related to differentiated

service (service key/SCP ID).

The BSC/RNC must support the function of providing differentiated service according

to the priority level, Pre-emption Capability Indicator (PCI), Pre-emption Vulnerability

Indicator (PVI) and Queue Allowed (QA) indicator in the Assignment Request

message.

1.80 WRFD-163200 Service based handover

Availability


Summary

Service based handover decides whether to allow inter-system handover and the

preferred network type (GSM/WCDMA) according to the IMSI number segment,

category and service type of the subscriber. If the current network is not the preferred

network (for example, the subscriber currently registers on a GSM network, but the

preferred network in data configuration is WCDMA network), the MSC Server

notifies the BSC/RNC to activate handover in the Assignment Request message. Thus,

the call is handed over to the target network. Handover can optimize resources.


MSOFTX3000V100R008

Additional Feature

Description



Page 93 of 131

Carriers who have both GSM and WCDMA networks can use the function to

activate the service on the corresponding network and save radio resources.

� For subscribers

None

Description

Currently, the service types supporting the service-based handover function include

voice service, transparent data service and non-transparent data service.

The supported handover strategies include:

For 2G services:

� Handover to 3G should be performed

For the Non-Access Stratum (NAS), calls should be handed over to the UMTS or

cdma2000 network as soon as possible, but the BSS has the final decision on

handover.

� Handover to 3G should not be performed

For the NAS, the user should stay on the GSM network as long as possible, but the

BSS has the final decision.

� Handover to 3G shall not be performed

Handover to UMTS or cdma2000 network is absolutely prohibited.

� Handover to 3G not contained

The Handover Request and Assignment Request messages do not bring the

ServiceHandover IE.

� Handover to 3G reject by card

Handover from a 2G network to a 3G network is rejected according to card type (SIM

or USIM).

� Handover to 3G not reject by card

Handover from a 2G network to a 3G network is rejected not according to card type.

For 3G services:

� Handover to 2G should be performed

For the NAS, this RAB should be handed over to a GSM network as soon as possible,

but the UTRAN has the final decision.

� Handover to 2G should not be performed

For the NAS, this RAB should stay in the UMTS network as long as possible, but the

UTRAN has the final decision.

� Handover to 2G shall not be performed

Handover to the GSM network is absolutely prohibited (unless under normal condition

when the RAB will be released).

MSOFTX3000V100R008

Additional Feature

Description



Page 94 of 131

� Handover to 2G not contained

The Handover Request and Assignment Request messages do not bring the

ServiceHandover IE.

� Handover to 2G reject by card

Handover from a 3G network to a 2G network is rejected according to card type.

� Handover to 2G not reject by card

Handover from a 3G network to a 2G network is rejected not according to card type.

Enhancement

None

Dependency

The BSC/RNC must support activating the required handover request according to

handover parameters in the Assignment Request message.

1.81 WRFD-163400 Update Network Indicator and Time Zone (NITZ)

Availability


Summary

The NITZ function complies with 3GPP 22042 specifications. According to the

location and IMSI of the subscriber, the network sends the carrier name, local time,

time zone and daylight saving time (DST) of the area where the user locates in the

MM INFORMATION message to the MS of the subscriber.


The operator can provide more user experience and increase user’s satisfaction.

� For subscribers

None

Description

After the MM INFORMATION message is sent to the MS, the carrier name (including

full name and short name) displayed in the MS can be updated immediately. The

supported coding schemes include UCS2 and 7Bit.

After the MM INFORMATION message is sent to the MS, the time information

(including time zone and DST) in the MS can also be updated immediately. Huawei

MSOFTX3000V100R008

Additional Feature

Description



Page 95 of 131

MSOFTX3000 can control the sending of the time of the area where the switch locates

or where the mobile subscriber locates. When in the DST time, the system

automatically adjusts the time. The time sent in the MM INFORMATION message is

the adjusted time.

Enhancement

None

Dependency

The MS must support the MM INFORMATION message.

1.82 WRFD-163400 Paging based on service type

Availability


Summary

In 3GPP 48.008 specifications, the optional IE "Channel Needed" is defined in the

Paging message. This IE indicates the radio channel type that may be used in the

subsequent service flows. The BSC can use this IE to decide the subsequent channel

type, distinguish service type and carry out flow control.


If the BSC supports the "Channel Needed" IE in the Paging message, it can

effectively distinguish various service flows, carry out flow control on services

(SMS for example) of low priority level in the case of heavy traffic, reduce the

load of the BSC and 2G access networks, and ensure normal provision of services

of high priority level. The BSC can also reduce the unnecessary usage of TCH

bearer channels according to the "Channel Needed" IE.

� For subscribers

None

Description

In 3GPP 48.008 specifications, the optional IE "Channel Needed" is defined in the

Paging message. This IE indicates the radio channel type that may be used in the

subsequent service flows. The BSC can use this IE to decide the subsequent channel

type, distinguish service type and carry out flow control.

Example:

� In an MT call, the MSC can indicate the subsequent services to use full rate

channel or dual rate channel in the "Channel Needed" cell in the Paging message.

MSOFTX3000V100R008

Additional Feature

Description



Page 96 of 131

� For the SMS reception service/USSD service/LCS, the MSC can indicate the

subsequent services to use SDCCH channel in the "Channel Needed" cell in the

Paging message.

� If the BSC does not support the "Channel Needed" IE, the Paging message does

not necessarily bring the IE.

Enhancement

None

Dependency

The BSC must support the "Channel Needed" IE in the Paging message and carry out

service-based flow control or channel distribution optimization accordingly.

1.83 WRFD-163700 Dual Transfer Mode (DTM)

Availability


Summary

DTM means that one Mobile Equipment is running CS service and PS service

simultaneously, according to 3GPP TS 0355. This function is only for GSM network.


The operator can provide better QoS to the subscribers and improve the user

satisfaction.

� For subscribers

None

Description

DTM means that one Mobile Equipment is running CS service and PS service

simultaneously, according to 3GPP TS 0355. This function is only for GSM network.

Enhancement

None

Dependency

The MS must be a Class A MS (there are class A, B and C MSs that support PS

domain) and support the DTM feature.

The BSC must support the DTM feature.

MSOFTX3000V100R008

Additional Feature

Description



Page 97 of 131

1.84 WRFD-164100 REL reroute

Availability


Summary

During an ISUP/BICC-based outgoing call, after receiving the REL message

containing the redirection number parameter from the peer office, the MSOFTX3000

starts call redirection based on the redirection number.


Carriers can provide the number redirection service and the service for shielding

international roaming subscribers.

� For subscribers

None

Description

The call from A to B is rerouted to C before being answered (UAE requirement):

When A calls B, after the MSOFTX3000 detects that B has subscribed to the REL

reroute service and obtains the international roaming number, the MSOFTX3000

directs the call to a server. The server decides whether to redirect the call to B's

international roaming number, that is, the MSRN or to the voice mail by using the

access number of the voice mail.

The call from A to B is rerouted to C after being answered (Hong Kong SUNDAY

requirement):

A calls a service center (number B). After the call is connected, number C is dialed.

Then, the service center originates the redirection of the REL number change. The

REL message contains the redirection number. This function cannot be realized when

number B is an IN subscriber number.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 98 of 131

1.85 WRFD-164200 BICC bearer redirection

Availability


Summary

The BICC bearer redirection can optimize the inter-office bearer by reducing the

number of offices by which the bearer path passes.


Carriers can optimize the bearer path.

� For subscribers

None

Description

During a call, assume that the MSC Server requires to connect the call to another

destination instead of the original callee (for example, in the case of call forwarding on

mobile subscriber not reply). When the BICC bearer redirection function is enabled,

the bearer connection that has been set up can be disconnected, and a direct bearer

from the caller to the new destination is set up. In this case, the office where the

original callee is located becomes the CMN node and does not control the bearer

resources. The BICC bearer redirection can be used for forwarding only.

Enhancement

None

Dependency

None

1.86 WRFD-164300 Anti-Cheat (to restrict forwarding and the number of ECTs)

Availability


Summary

An example is used for describing the Anti-Cheat function. When A calls B, if B has

subscribed to the service that the call is forwarded to C, connection between A and C is

set up, but it is not required to set up the connection between A and B, or B and C. In

MSOFTX3000V100R008

Additional Feature

Description



Page 99 of 131

this case, if B has activated the forwarding service, B can unrestrictedly set up several

connections between An and Cn. Therefore, a large amount of fee is generated in a

short time. If the fee cannot be paid, carriers consider it as a cheat. The case also

occurs in the explicit call transfer (ECT) service. To avoid the cheat, the number of

times a call is forwarded by a subscriber in the local office and the number of ECTs

are restricted. Carriers can enable the Anti-Cheat function and control the number.


The security of the network can be improved.

� For subscribers

The function can prevent malice subscribers from using the network illegally.

Description

An example is used for describing the Anti-Cheat function. When A calls B, if B has

subscribed to the service that the call is forwarded to C, connection between A and C is

set up, but it is not required to set up the connection between A and B, or B and C. In

this case, if B has activated the forwarding service, B can unrestrictedly set up several

connections between An and Cn. Therefore, a large amount of fee is generated in a

short time. If the fee cannot be paid, carriers consider it as a cheat. The case also

occurs in the explicit call transfer (ECT) service. To avoid the cheat, the number of

times a call is forwarded by a subscriber in the local office and the number of ECTs

are restricted. Carriers can enable the Anti-Cheat function and control the number.

Enhancement

None

Dependency

None

1.87 WRFD-164900 TDM circuit selection based on bearer capability of circuits

Availability


Summary

Based on the service requirement, different types of TDM circuits, compression

circuits (those connected to the compression device) or non-compression circuits

(those not connected to the compression device), between MGWs can be selected.

Thus, the transmission cost of the gateway can be reduced.

MSOFTX3000V100R008

Additional Feature

Description



Page 100 of 131


The compression device can be used between the MGWs to reduce the

transmission cost. The subscribers, however, do not feel the delay of

transmission.

� For subscribers

None

Description

If the TDM bearer is adopted between two gateways, the carrier may connect the TDM

circuits to the inter-gateway compression device for data transmission. Thus, when

services with large amount of data, such as the video phone (VP), occur, the data may

be long delayed after processed by the compression device.

This function ensures that the services with large amount of data are not processed by

the compression device. The data of this kind of service can be transmitted through the

TDM circuits that are not connected to the compression device.

The services with small amount of data, such as the voice call, are however processed

by the compression device. Thus, the transmission cost of the gateway can be reduced.

Application scenario

When multiple gateways are configured in an office or are used to connect offices, the

TDM bearer may be adopted between gateways. In this case, to reduce the cost, the

carrier can connect the TDM circuits to the compression device.

If services with large amount of data, such as the VP service, are processed by the

compression device, the data transmission may be long delayed. For services with

small amount of data, such as the voice call, even if the data is processed by the

compression device, the delay of data transmission is short and acceptable.

Therefore, based on the data configuration and service requirement (that is, the bearer

capability parameter in the service request message and the configured circuit type),

the MSC Server can decide whether to transmit the data of calls through the

compression TDM circuits or non-compression TDM circuits. Thus, the cost can be

reduced and at the same time, long delay of data transmission can be avoided.

The application scenario is as shown Figure 1-12.

MSOFTX3000V100R008

Additional Feature

Description



Page 101 of 131

Figure 1-12 Application scenario of TDM circuit selection based on service type

MSC_A MSC_A

MGW_1 MGW_2 MGW_3

These TDM circuits are not

connected to the compression

device. Thus, data

transmission is not delayed.

Compression

device

These TDM circuits are not


device. Thus, data

transmission is not delayed.

These TDM circuits are


device. The data transmission is

delayed. The impact of delay on

the services with small amount

of data, however, is minor.

These TDM circuits are


device. The data transmission is

delayed. The impact of delay on

the services with small amount

of data, however, is minor.

Compression

device

Enhancement

None

Dependency

The compression device must be used between the MGWs and be connected to the

TDM circuits.

1.88 WRFD-165000 TDM&IP dual bearer

Availability


Summary

The TDM&IP dual bearers are classified into inter-MSC dual bearers and intra-MSC

inter-MGW dual bearers. The inter-MSC dual bearers enable the ISUP (TDM)/TUP

(TDM)/BICC (IP) mixed networking in the same office direction. The MSOFTX3000

can select TDM/IP bearer according to the preference policy of a bearer network. A

mixed office direction is the basis of smooth evolution of the inter-MSC network from

a TDM network to an IP network.


The function supports smooth evolution from a TDM network to an IP network.

MSOFTX3000V100R008

Additional Feature

Description



Page 102 of 131

� For subscribers

None

Description

MSOFTX3000R006C02 supports this function in the following scenarios:

� Bearer selection − Selecting inter-office TDM/IP bearer based on a subscriber priority − Selecting inter-office TDM/IP bearer based on intra-office bearer and

incoming bearer type − Selecting inter-office TDM/IP bearer based on a percentage

� Smooth upgrade at a signaling plane − ISUP and BICC signaling in the same office direction can be borne on the

M3UA link. − ISUP and BICC signaling in the same office direction can be borne on the

MTP3 link. − ISUP and BICC signaling in the same office direction are borne on the M3UA

link and the SCTP link respectively. − ISUP and BICC signaling in the same office direction are borne on the MTP3

link and the SCTP link respectively. − Through data configuration, you can set the office direction type to a common

office direction or a mixed office direction according to your requirements.

The common office direction supports only ISUP/TUP or BICC bearer, and

the mixed office direction supports ISUP, TUP, and BICC bearer at the same

time. You can run ADD OFC to configure an office direction type. The values

of Office Type are Common Office (default value) and Mix Office. In

addition, you must configure BICC Signaling type. You can run MOD OFC

to modify the previous parameters, and thus you can set the office direction

type to a common office direction or a mixed office direction according to

your requirements. The intra-MSC inter-MGW dual bearers support IP (full-mesh connection) and TDM

mixed networking between intra-MSC MGWs. When connecting an intra-MSC call,

the system can select a bearer based on the data configuration and the preference

policy of the bearer network. When the resources of the MGW are insufficient, the

system can reselect a bearer. Thus, the IP bearers and TDM bearers are mutually

backed up. Intra-MSC inter-MGW dual bearers help to implement smooth evolution of

an intra-MSC inter-MGW network from a TDM network to an IP network.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 103 of 131

1.89 WRFD-165300 Batch conversion of calling numbers

Availability


Summary

When two GMSCs interwork with each other, it may be required to shield or convert

the calling numbers so that the real calling numbers are hidden in the outgoing

signaling.

When two GMSCs interwork with each other and the calling numbers are special

numbers (such as the mobile IP public number), the calling numbers must be

converted so that the malicious call interception from the peer office fails. These

calling numbers are scattered ones. Therefore, there is a large number of them. With

this function, you can configure the incoming trunk discrimination table to convert a

large number of calling numbers from different end offices.

The function is not supported if the incoming signaling is BICC.


By using this function, carriers can perform special processing for the calls and

frustrate the malicious call interception from the peer office.

� For subscribers

The number of call failures can be reduced and the subscriber satisfaction can be

improved.

Description

When two GMSCs interwork with each other, it may be required to shield or convert

the calling numbers so that the real calling numbers are hidden in the outgoing

signaling.

When two GMSCs interwork with each other and the calling numbers are special

numbers (such as the mobile IP public number), the calling numbers must be

converted so that the malicious call interception from the peer office fails. These

calling numbers are scattered ones. Therefore, there is a large number of them. With

this function, you can configure the incoming trunk discrimination table to convert a

large number of calling numbers from different end offices.

The function is not supported if the incoming signaling is BICC.

Enhancement

None

MSOFTX3000V100R008

Additional Feature

Description



Page 104 of 131

Dependency

None

1.90 WRFD-165500 Wideband AMR

Availability


Summary

The wideband AMR service is to add a new codec type, that is, UMTS AMR-WB, in

the flow of call establishment and bearer modification. This service is capable of

allocating broader bandwidth for bearer channels, and thus providing voice services in

higher quality.


The broadband AMR function enables customers enjoy the high quality of the

voice service, and thus improving the brand value of carriers and gain higher

benefits.

� For subscribers

Subscribers can enjoy the voice service with higher quality.

Description

The wideband AMR service is to add a new codec type, that is, UMTS AMR-WB, in

the flow of call establishment and bearer modification. This service is capable of

allocating broader bandwidth for bearer channels, and thus providing voice services in

higher quality.

The following flows are involved in this service:

� Codec negotiation and modification during the call establishment

� Codec negotiation and modification in an active call

� Differentiated services

� MAP signaling codec negotiation during the inter-MSC handover

For the wideband AMR service itself, only a new codec is added in the original codec

processing flow. The following takes the flow of codec negotiation and modification

during the call establishment for example to describe the processing flow of the

wideband AMR service.

Codec negotiation and modification during the call establishment

In the wideband AMR service, the original service flow is not modified, but a codec is

added in the codec processing flow; therefore, the processing flow of the wideband

AMR service is the same as the common codec processing flow.

MSOFTX3000V100R008

Additional Feature

Description



Page 105 of 131

Figure 1-13shows the processing flow of the codec negotiation and modification

during the call establishment.

Figure 1-13 Processing flow of the codec negotiation and modification during the call

establishment

RNC MSC UMGUE

SETUP

(Support

Codeclist)SETUP

(Support Codeclist)

MSC processes thecodeclist and

determines to establishthe codec for bearer

ADD REQ(Codeclist

)ADD REPLY

UERNC

Call Confirm

(Support

Codeclist)

ADD REQ(Codeclist

)ADD REPLY

RAB ASSIGNMENTREQ

(NAS

Synchronisation Indicator)

RAB ASSIGNMENT RSP

RAB ASSIGNMENT REQ

(NAS Synchronisation Indicator)

RAB ASSIGNMENTRSP

Call Confirm(Support Codeclist)

1 The calling UE sends the SETUP message containing codec list supported by the

UE.

2 The called UE sends the Call Confirm message containing codec list supported by

the UE.

3 The MSC determines the codec to be used during the call establishment based on

the codec supported by the calling and called UE, RNC, and MGW.

4 The MSC configures the RAB parameter and the NAS Synchronisation Indicator

information element based on the codec used during the call establishment.

The wideband AMR service does not require that mobile subscribers subscribe to any

extra data related to this service.

Following is the function of each NE in the flow.

� MSC: Determines the codec type and rate through the negotiation based on the

codec list supported by UE, MGW, and RNC, and codec list supported by the

peer office; configure the RAB parameter corresponding the broadband AMR

function while delivering the assignment; in the flow of differential services,

determines the codec rate during the whole bearer setup based on the configured

data.

MSOFTX3000V100R008

Additional Feature

Description



Page 106 of 131

� RNC: During the RAB assignment, the RNC processes the RAB parameter in the

broadband AMR function in the current assignment and the RNC adds or

modifies RAB based on the RAB parameter.

� MGW: When adding or modifying terrestrial Bearer, the MGW performs the

negotiation of the user plane and sets up or modifies bearer channel based on the

codec type and codec rate set.

� UE: Supports the coding and decoding of the voice packet based on the algorithm

of the broadband AMR.

Enhancement

None

Dependency

The MSC, RNC, MGW, and UE must support the wideband AMR service.

1.91 WRFD-165800 Forced call release upon dialing back

Availability


Summary

After detecting the inter-network illegal operations by using the third-party device, the

carriers connect the third-party device to the Huawei BAM though the TCP/IP

protocol, and notify Huawei to release the corresponding ISUP/TUP calls.

The specified ISUP/TUP calls can be released manually on the MML client.


Forced call release mode can be used to avoid the inter-network illegal

operations.

� For subscribers

None

Description

Carriers connect the third-party device to the Huawei BAM though the TCP/IP

protocol or run REL CURCALL to notify the MSC to send a call release command.

The interface parameters consist of DPC, OPC, CIC (single), Signaling type

(ISUP/TUP), and NI.

The MSC returns the results of the call release operation through the BAM. If the call

is released successfully, call release information such as calling number, called number,

MSOFTX3000V100R008

Additional Feature

Description



Page 107 of 131

and release time is sent to the third-party device and the client. Otherwise, the release

failure information is sent to the third-party device and the client. Print the information

in the message to the ReleaseCallLog.txt log file on the path:

\MSOFTX3000\RUNLOG\ ReleaseCall\ReleaseCallLog.txt. If the BAM receives the

message that indicates the call fails to be released from the MSC, the BAM sends to

the client the prompt "Fail to release the current call" and does not record the log.

Figure 1-14 Diagram of forced call release upon dialing back

The third-party device or MML client

Huawei BAM 6000 port access Huawei MSC

① ③ ④

②

Enhancement

None

Dependency

None

1.92 WRFD-168100 IP bearer AutoTest

Availability


Summary

The IP bearer AutoTest is a method used for acceptance of core network IP equipment

and IP bearer network.

Currently, the mobile softswitch core network adopts the IP bearer networking mode.

The existing IP bearer networking is complicated. Actual test data is required to

evaluate whether the adopted IP bearer network meets the carrier-class VoIP

requirements.

Using the IP bearer AutoTest feature, you can test the IP bearer network of the mobile

softswitch to obtain the QoS performance entities of the IP bearer network. The

implementation mode is as follows:

The MSOFTX3000 initiates a great number of calls to simulate a heavy-traffic

environment, and then outputs the QoS statistics of the IP bearer network.

By analyzing the QoS performance indexes, you can check whether the IP bearer

network meets the carrier-class VoIP requirements and make plans for network

expansion so that the IP bearer network can meet the growing service demand.

MSOFTX3000V100R008

Additional Feature

Description



Page 108 of 131


Using the IP bearer AutoTest function, carriers can perform acceptance of the IP

equipment and the IP bearer network so that the IP bearer network can meet the

growing service demand after put into commercial use.

Using the IP bearer AutoTest function, carriers can also evaluate the QoS of the

operating IP equipment and IP bearer network so that plans can be made for

network expansion and optimization.

� For subscribers

None

Description

Figure 1-15 shows the application scenarios of the IP bearer AutoTest feature.

Figure 1-15 Application scenarios of the IP bearer AutoTest feature

The application scenarios can be classified as follows:

� Automatic test for IP bearer QoS between the MGWs in the same office

� Automatic test for IP bearer QoS between ordinary offices

� Automatic test for IP bearer QoS between CMN offices

Figure 1-16 shows the networking for the automatic test for IP bearer QoS between the

MGWs in the same office.

MSOFTX3000V100R008

Additional Feature

Description



Page 109 of 131

Figure 1-16 Automatic test for IP bearer QoS between the MGWs in the same office

2. The MSC Server starts the test task.

− Specify the test type (automatic test for IP bearer QoS between MGWs in the

same office), the call traffic, and the test duration.

− Specify the thresholds and indexes for signaling and IP bearer QoS, and the

test path. (One test task supports multiple test paths.)

3. The MSC controls the MGW in setting up the test point.

− Originate test calls based on the traffic parameters.

− Control the MGW in setting up the bearer and starts playing announcement.

4. The MGW sets up the test point and collects statistics about the QoS.

− Set up the test point and play test announcement as instructed.

− Collect statistics about the QoS and reports the result to the MSC Server.

5. MSC Server performs signaling QoS test simultaneously.

Obtain the packet loss rate through issuing ping commands.

6. The MSC Server displays the QoS information.

− Display the QoS information in real time.

− Originate new test calls based on the traffic model.

7. The MSC Server stops the IP bearer QoS test.

− Stop originating new IP bearer QoS test calls.

− Instruct the MGW to stop the test if abnormal QoS indexes are detected.

Figure 1-17 shows the networking for the automatic test for IP bearer QoS between

ordinary offices.

MSOFTX3000V100R008

Additional Feature

Description



Page 110 of 131

Figure 1-17 Automatic test for IP bearer QoS between ordinary offices

MSC Server1

MGW MGW

Signaling Bearer

IP bearer network

MSC Server2

Called number: 1368888

BICC

Called number: 1367777

8. MSC Server1 starts the test task.

− Specify the test type (automatic test for IP bearer QoS between MGWs in the

same office), the call traffic, and the test duration.

− Specify the thresholds and indexes for signaling and IP bearer QoS, and the

test path. (One test task supports multiple test paths.)

9. MSC Server1 performs the IP bearer QoS test based on whether MSC Server2

supports IP bearer QoS test.

If MSC Server2 supports IP bearer QoS test:

− MSC Server1 originates IP bearer QoS test calls based on the called number.

− MSC Server1 sets up the test point and simulates the required signaling to

complete the test calls.

If MSC Server2 does not support IP bearer QoS test:

− MSC Server1 configures the alternative routing data of the called number so

that the call is routed back to the originating office.

− The originating office sets up the test point and simulates the required

signaling to complete the test calls.

10. MSC Server1 stops the IP bearer QoS test.

− The MGW reports the IP bearer QoS to MSC Server1.

− MSC Server1 performs inter-office and Mc interface QoS tests at the same

time.

− MSC Server1 sets up the voice bearer and displays the signaling QoS.

Figure 1-18 shows the networking for the automatic test for IP bearer QoS between

CMN offices.

MSOFTX3000V100R008

Additional Feature

Description



Page 111 of 131

Figure 1-18 Automatic test for IP bearer QoS between CMN offices

MSC Server

MGW MGW

Bearer

MSC ServerMSC Server

MSC Server

MGW MGW

Signaling

IP bearer network

MSC ServerMSC Server

11. The CMN MSC Server configures the routing data for the test numbers to pass

through the non-CMN offices.

− Office direction 1: 1368888xxxx



− No special requirements for other functions

12. The CMN MSC Server performs the IP bearer QoS test in the same way as the

preceding application scenario.

The following provides the auxiliary solutions:

� Normally, one test point occupies one TC. Through TC sharing, multiple test

points can share the same TC. This can effectively reduce the number of TCs.

� The IP bearer test should be performed before and after cutover or upgrade so as

to minimize the impact on the existing services. The test traffic should be

calculated in real time using the following formula: Test traffic = Planned traffic

– Non-test traffic (Note that the test traffic should increase slowly but decrease

sharply during the test to avoid impact on the existing services.)

� The inter-office IP bearer QoS test can be implemented through the MGW. The

intra-office IP bearer QoS test can be implemented through the outgoing gateway

of the local office or the incoming gateway of the peer office. If the test is

implemented through the outgoing gateway of the local office, the MSC Server

sets up test calls on the specified MGW. If the test is implemented through the

incoming gateway of the peer office, static configuration is required for the peer

office and the peer office must support the IP bearer pressure test.

� The MSC Server can perform signaling pressure test independently, without

issuing the announcement indication to the MGW. It performs ping test to the

MSOFTX3000V100R008

Additional Feature

Description



Page 112 of 131

related signaling links. For the TDM network, the transmission quality of the

SIGTRAN signaling, and the H.248 signaling on the Mc interface can be

obtained through the test.

� The IP bearer pressure test can be performed on the iLMT and the M2000. As the

M2000 has the centralized O&M function, it is easier to perform global test on

the M2000.

Enhancement

V100R008 Version add: support TC share.

Dependency

The MGW should work with the MSC Server to share the TC resources and complete

the bearer QoS monitoring.

The peer office can be an MSC or MGW that does not support the IP bearer AutoTest

function.

1.93 WRFD-168200 Time-Based Service

Availability


Summary

The Time-based Service means that the MSOFTX3000 provides different services for

subscribers who dial the same number in different time segments. The time segment

can be set based on a week and a date. The minimum granularity of the time segment

is one minute.


The Time-based Service enables carriers to flexibly customize value-added

services, and improves attractiveness and customer satisfaction.

� For subscribers

None

Description

The Time-based Service means that the MSOFTX3000 provides different services for

subscribers who dial the same number in different time segments. The time segment

can be set based on a week and a date. The minimum granularity of the time segment

is one minute.

Example:

MSOFTX3000V100R008

Additional Feature

Description



Page 113 of 131

The number 1790 is a service number. The MSOFTX3000 successfully connects

subscribers who dial 1790 from 8:00 a.m. to 18:00 p.m., and plays prompt tones to the

subscribers during another time segment.

Enhancement

None

Dependency

None

1.94 WRFD-168500 BICC fail re-route

Availability


Summary

In the case of a BICC call failure caused by faults in the bearer network, the system

can automatically select another outgoing route based on the special cause value

contained in the call disconnection message, thus preventing the subscribers from

redialing.


By implementing this function, the carrier can roll back the call to the originating

IP bearer side for selecting another bearer network. In this way, call failure

caused by circuit unavailability resulted from the fault in the bearer network is

prevented and the call completion rate is increased.

� For subscribers

The calls originated by the subscribers are not affected by the fault in the bearer

network.

Description

In the case of a BICC call failure caused by faults in the bearer network, the system

can automatically select another outgoing route based on the special cause value

contained in the call disconnection message, thus preventing the subscribers from

redialing.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 114 of 131

1.95 WRFD-168600 IP QoS Monitor

Availability


Summary

This function shows the causes of the broadband link fault, traffic statistics indexes

related to SCTP, and measurement for the SCTP messages.


The efficiency for locating the IP related problems is improved.

� For subscribers

None.

Description � Cause description is added to the alarms triggered by broadband link faults.

Cause description is added to the alarms triggered by the fault on the following

links:

− M3UA links

− M2UA links

− IUA links

− H248 links

− BICC links

The description of the cause value reported by the SCTP or that detected by the

MSOFTX3000 is added to the alarms triggered by failure of the SCTP user layer

links (M3UA/M2UA/IUA/H248/BICC links).

� Traffic statistics indexes related to the SCTP are added.

The following performance entities are added to the measurement of the M3UA

links, IUA links, H248 links, and the BICC links:

− Retransfer Count: It is the total times that M3UA link messages are

retransferred.

− Retransfer Ratio: It is the ratio of the number of retransferred messages to

that of all the transferred messages.

− Sending Buffer Overflow Count: It is the total number of times that the

SCTP sending buffer overflow occurs.

− Receiving Buffer Overflow Count: It is the total number of times that the

SCTP receiving buffer overflow occurs.

MSOFTX3000V100R008

Additional Feature

Description



Page 115 of 131

− Average Acknowledgment Delay: It is the estimated time delay occurs

during the process of sending a message and waiting for its response.

− Average Deviation: It is the average offset of the acknowledgment delay.

− Sending Buffer Seizure Ratio: It is the current seizure ratio of the SCTP

sending buffer.

− Receiving Buffer Seizure Ratio: It is the current seizure ratio of the SCTP

receiving buffer.

� Measurement for the SCTP messages is added.

The measurement object is an SCTP quadbit: local IP address, peer IP address,

local port number, and peer port number.

The related measurement entities added are as follows:

− Number of DATA Chunk Sent

− Number of DATA Chunk Resent

− Number of DATA Chunk Received

− Valid Bytes of Sent

− Valid Bytes of Received

− Number of SACK Sent

− Number of SACK Received

− Number of HeartBeat Sent

− Number of HeartBeat Received

− Number of HeartBeat ACK Sent

− Number of HeartBeat ACK Received

− Number of Chunk Out of Order Sent

− Number of Chunk Out of Order Received

− Number of ERROR Chunk Sent

− Number of ERROR Chunk Received

− Number of INIT Sent

− Number of INIT Received

− Number of INIT ACK Sent

− Number of INIT ACK Received

− Number of COOKIE Sent

− Number of COOKIE Received

− Number of COOKIE ACK Sent

MSOFTX3000V100R008

Additional Feature

Description



Page 116 of 131

− Number of COOKIE ACK Received

− Number of ABORT Sent

− Number of ABORT Received

− Number of SHUT DOWN Sent

− Number of SHUT DOWN Received

− Number of SHUT DOWN ACK Sent

− Number of SHUT DOWN ACK Received

− Number of SHUT DOWN COMPLETE Sent

− Number of SHUT DOWN COMPLETE Received

Enhancement

None

Dependency

None

1.96 WRFD-168700 Support MediaX3600 services

Availability


Summary

The MediaX3600 platform is a multimedia conference processing system of Huawei.

This platform can provide conference access for voice, video or data services and the

related management. The MSOFTX3000 can serve as the access layer for the

MediaX3600 at the PLMN side and add mobile subscribers to the conference.

Together with the MediaX3600, the MSOFTX3000 can provide the group call service

and the call hunting service. The interface and the bearing type between the

MSOFTX3000 and the MediaX3600 are SIP-I interface and IP bearing, respectively.


The carrier can provide multimedia conference processing services by

interconnecting with the MediaX3600.

� For subscribers

The subscribers can enjoy multimedia conference services of high quality

conveniently.

MSOFTX3000V100R008

Additional Feature

Description



Page 117 of 131

Description

The MediaX3600 platform is a multimedia conference processing system of Huawei.

This platform can provide conference access for voice, video or data services and the

related management. The MSOFTX3000 can serve as the access layer for the

MediaX3600 at the PLMN side and add mobile subscribers to the conference.

Together with the MediaX3600, the MSOFTX3000 can provide the group call service

and the call hunting service. The interface and the bearing type between the

MSOFTX3000 and the MediaX3600 are SIP-I interface and IP bearing, respectively.

Enhancement

None

Dependency

The MediaX3600 is installed with the V300R003C02 version or later.

1.97 WRFD-168800 Export user number base on cell

Availability


Summary

Export user number base on cell consists of the following functions:

� Exporting the IMSI, MSISDN, and IMEI of all the subscribers in a specified

location area or cell and the time data of recent visits to a text file in the path: D:\

MSOFTX3000\Output


location area or cell and the time data of recent visits to a specified path

immediately after a real-time task is started by running EXP USRINF


location area or cell and the time data of recent visits to a specified path at the

scheduled time point after a scheduled task is added by running ADD EXPTSK


By implementing this function, the key data of the subscribers in a specified

location area or cell can be exported to a file that can be used by the carrier for

analysis purpose. The carrier can provide some special services to the subscribers

in the specified location area or cell based on the analysis result.

� For subscribers

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 118 of 131

Description

Export user number base on cell consists of the following functions:


location area or cell and the time data of recent visits to a text file in the path: D:\

MSOFTX3000\Output


location area or cell and the time data of recent visits to a specified path

immediately after a real-time task is started by running EXP USRINF


location area or cell and the time data of recent visits to a specified path at the

scheduled time point after a scheduled task is added by running ADD EXPTSK

Enhancement

None

Dependency

None

1.98 WRFD-168900 Support generic number's length exceeding

Availability


Summary

The maximum length of the generic number (GN) delivered by the SCP is defined as

11 bytes (including the attribute bytes) in the related protocol. The number part of the

GN occupies only 8 bytes, and the length of the number part cannot exceed 16 digits.

The GN adopted by some carriers, however, does not comply with the protocol

standard and the length of the number part is more than 16 digits. Through special

operation, the MSOFTX3000 can process the GN of a maximum of 16 bytes, and the

maximum length of the number part of the GN supported by the MSOFTX3000 is 32

digits.


The carrier can support GNs of multiple formats.

� For subscribers

None.

MSOFTX3000V100R008

Additional Feature

Description



Page 119 of 131

Description

The maximum length of the generic number (GN) delivered by the SCP is defined as

11 bytes (including the attribute bytes) in the related protocol. The number part of the

GN occupies only 8 bytes, and the length of the number part cannot exceed 16 digits.

The GN adopted by some carriers, however, does not comply with the protocol

standard and the length of the number part is more than 16 digits. Through special

operation, the MSOFTX3000 can process the GN of a maximum of 16 bytes, and the

maximum length of the number part of the GN supported by the MSOFTX3000 is 32

digits.

Enhancement

None

Dependency

None

1.99 WRFD-169000 Query detail information of a call

Availability


Summary

By implementing this function, the carrier can query the CIC and TID used in the call

based on the calling number or the called number by running DSP TLKUSR.


The carrier can locate rapidly the call failure based on the CIC and TID.

� For subscribers

None.

Description

By implementing this function, the carrier can query the CIC and TID used in the call

based on the calling number or the called number by running DSP TLKUSR.

Enhancement

None

Dependency

None

MSOFTX3000V100R008

Additional Feature

Description



Page 120 of 131

1.100 WRFD-169700 Support for High Compression Rate of Bearer Transmission

Availability


Summary

The MSOFTX3000 supports high compression rate for bearer transmission. It can use

compression algorithms to transmit voice packets when the IP over E1 networking is

adopted for the MGW. By issuing AMR codecs and UP header deletion messages to

the MGW, the MSOFTX3000 achieves a compression rate as high as 16:1 for the

voice packets of the MGW.


Decrease the CAPEX.

� For subscribers

None

Description

This function helps improve the bandwidth usage and save the OPEX of carriers when

the IP over E1 networking is adopted for the MGW.

Figure 1-19 shows a typical networking diagram for IP over E1.

Figure 1-19 Typical networking diagram for IP over E1

MGW MGW

MSC Server MSC Server

SDH

transmission

network

Enhancement

None

MSOFTX3000V100R008

Additional Feature

Description



Page 121 of 131

Dependency

Peer MSC Server/MGW supports High Compression Rate of Bearer Transmission

also.

1.101 WRFD-190400 Dual BAM Backup

Availability


Summary

The system adopts two BAMs to implement the backup function. When the active

BAM is faulty, the system is capable of switching the services over to the standby

BAM automatically in a fast and reliable way. Thus, the service is not interrupted.


When a single BAM is configured, it may take a long time to restore the service

in case of the BAM failure. When two BAMs are configured, it takes short time

to restore the service in case of a BAM failure because the other BAM can take

over the services of the faulty BAM. Thus time is saved and the QoS is improved.

The BAMs in active/standby mode can be automatically switched over, which

improves the system reliability, eases the maintenance, and saves the maintenance

cost.

� For subscribers

When one BAM of the dual-node system is faulty, the services are not interrupted,

and thus there is no impact on subscribers.

Description

When the emergency workstation is used, it cannot automatically replace the BAM

when the BAM is faulty. You must manually switch the service over to the emergency

workstation. In this case, there must be someone on duty in the equipment room.

Besides, the emergency workstation backs up data in a unidirectional way, that is, data

can only be backed up from the BAM to the emergency workstation.

The BAM dual-node function solves this problem, and thus the system can provide the

services without service interruption in a way similar to the active/standby strategy of

the MSOFTX3000 boards. The dual-node function enables the standby BAM to back

up the data automatically and take over the services of the active BAM when the

active BAM is faulty. The external interfaces of the dual-node system are fixed and the

standby BAM are transparent to the outside network.

The BAM dual-node function has the following advantages:

� It solves the single-BAM failure problem. When one BAM is faulty, the other

takes over all services.

MSOFTX3000V100R008

Additional Feature

Description



Page 122 of 131

� It eases the maintenance of the BAM system. With dual BAMs, the system can

automatically switch over the BAMs when one is faulty instead of manually

switching over when the emergency workstation is adopted.

The BAM dual-node function has the following disadvantages:

� The data cannot be backed up in real several analog facsimile service time. The

delay exists during the backup.

� The switchover takes a long time because the data must be formatted after the

switchover.

Table 1-1 Design restriction

Design Restriction Reason

The external interfaces of the

dual-node system must be fixed.

This feature adds internal BAM redundancy only

and is irrelevant to external interfaces.

The operating system must be

configured with automatic login.

The system can automatically run the BAM after

the system is restarted.

During the switchover of the

active/standby BAMs, the data

within 30 minutes may be lost.

The dual-node system enables the BAM to

synchronize the data in real time, but the data is not

actually the real-time data. During the switchover,

the risk of data loss exists.

The versions of the two BAMs in

the dual-node system must be

compatible and their version

numbers must be the same.

Both BAMs must support the dual-node function

and the versions of the BAMs must be the same;

otherwise, the dual-node system is the same as the

single-node system.


active/standby BAMs, the BAM

must be disconnected from the client

and the NMS.

During the switchover, the virtual IP address of the

BAM must be switched and bound again, and thus

the client and the NMS are disconnected from the

BAM.


active/standby BAMs, the

communication frames between the

host and the BAM may be lost.

During the switchover, the virtual IP address of the

host must be switched and bound again, and thus

some message frames between the host and the

BAM are lost.

The tables whose structures and

names are changed during the

operation cannot be synchronized.

The database cannot synchronize the tables whose

structures and names are changed after the

subscription and release.

The standby BAM does not support

detecting the HDMonitor alarm.

The service console on the standby BAM is not

started and the HDMonitor does not send alarms to

the SecurityManager.

Figure 1-20 shows the networking structure of the BAM dual-node system.

MSOFTX3000V100R008

Additional Feature

Description



Page 123 of 131

Figure 1-20 Networking structure of the BAM dual-node system

172.20.100.0172.20.100.1 172.30.100.0172.30.100.1

Floating external IP

172.20.200.0 172.30.200.0(Virtual IP)

LAN Switch 1 LAN Switch 2

ActiveBAM

StandbyBAM

NMS or ordinary client

LAN Switch 3

Host

(Virtual IP)

As shown in Figure 1-20, each BAM is configured with two internal network adapters.

Both BAMs communicate with the host through LAN Switch 1 or LAN Switch 2. The

two BAMs are configured with fixed IP addresses and they communicate by heartbeat

messages through LAN Switch 1 or LAN Switch 2. Follow the principles below to

configure the IP addresses for the active/standby BAMs:

� By default, the IP addresses for the active BAM are 172.20.100.1 and

172.30.100.1.

� By default, the IP addresses for the standby BAM are 172.20.100.0 and

172.30.100.0.

� The active BAM binds two virtual IP addresses 172.20.200.0 and 172.30.200.0 to

its internal network adapters, through which the BAM communicates with the

host. In standby mode, the standby BAM does not bind IP addresses and does not

communicate with the host.

� Each BAM must provide at least one external network adapter to connect with

the NMS and LMT of the external network through LAN Switch 3.

� The active and the standby BAMs are configured with the same virtual IP address

in the data table to establish the logical links with the LMT and the NMS.

� The active BAM is connected to the WAN through the virtual IP address bound to

the network adapter of the BAM.

� In standby mode, the standby BAM does not bind IP addresses. When the status

of the standby BAM is changed to active, the standby BAM binds the virtual IP

address.

MSOFTX3000V100R008

Additional Feature

Description



Page 124 of 131

Figure 1-21 shows the operation structure of the BAM dual-node system.

Figure 1-21 Operation of the BAM dual-node system

Heartbeat

Active file

sychronization

Database

release andsubscriptiontechnology

Active BAM

Active/standbystrategy status

machine

Filesynchronization

Standby BAM

NMS

interfaceHost

interface

File

synchronization

Active/standby

strategy statusmachine

Databasesynchronization

Databasesynchronization

The standby BAM uses different hard disks to mirror the folders of the active BAM.

With the file synchronization service of the dual-node system, the folders and files in

the synchronization directory are completely mirrored from the original ones on the

active BAM. When the files on the active BAM are modified, the mirrored files on the

standby BAM are simultaneously modified.

After the dual-node system is installed, the configuration items in the bam.ini file are

as follows:

[MirrorDir]

DirCount=3

Dir1=<ROOT>\FTPRoot

Dir2=<ROOT>\License

Dir3=<DBBACKUP>

ROOT=D:\SXOMC\

DATA=D:\MSSQL\Data\

DBBACKUP=F:\SXOMC\

Table 1-2 lists the synchronization directory corresponding to the relative directory in

the sharp brackets.

Table 1-2 Relative directory

Directory Name Remarks

D:\MSOFTX3000 <ROOT> The root directory for installing the MSOFTX3000

F:\MSOFTX3000 <DBBACKUP> The database backup directory

MSOFTX3000V100R008

Additional Feature

Description



Page 125 of 131

The transient service of the status machine and the database synchronization service

are automatically implemented by the BAM Manager without manual interference.

The BAM dual-node system is classified into three modules:

Status machine module: maintaining status between two BAMs

When the status of a service process on the active BAM changes to abnormal for three

times within five minutes, the system triggers the switchover operation.

Each BAM maintains two status machines that trace the status of the local and peer

sides. When the status changes, the system performs related operations to implement

the switchover of the BAMs.

� When the standby BAM detects that the active BAM is unavailable, it is

prompted to be the active BAM, and the peer-end active BAM is degraded to be

the standby BAM.

� When the status of the active and the standby BAMs conflicts, the status machine

determines the active/standby status of the BAMs based on the preset strategy to

ensure the stable operation of the system.

� The heartbeat messages are used between the BAMs to notify each other the

status. The system performs the status change based on the preset strategy. The

position of the active BAM is the same as that of the standby one.

Database synchronization module: synchronizing data of the database

When the status of the active and the standby BAMs is stable, the system starts to

synchronize the database to ensure that the data between the BAMs is consistent. The

synchronization mechanism is as follows:

� The active BAM notifies the standby BAM to configure the standby BAM as the

distribution server and add the active BAM as the release server.

� When detecting that the standby BAM configures itself to be the distribution

server, the active BAM configures itself to be the release server.

� The active BAM releases the specified database and the standby BAM subscribes

the database.

File synchronization module: synchronizing files

When the status of the active and the standby BAMs is stable, the system starts to

synchronize the files to ensure that the file data between the BAMs is consistent. The

synchronization mechanism is as follows:

� Each BAM establishes two TCP connections to each other because both BAMs

can act as the server. In this case, four full-duplex connections are established

between two BAMs.

� The active BAM detects the folders that need synchronizing through folder

monitoring process.

� To synchronize the data, the system sends signals to start the file synchronization

process to synchronize the data.

MSOFTX3000V100R008

Additional Feature

Description



Page 126 of 131

Enhancement

None

Dependency

None

1.102 WRFD-200300 TDM redundancy for IP congestion

Availability


Summary

Upon selection of the intra-MSC inter-MGW bearer, if the IP bearer cannot be

established within the MSC, the intermediate TDM bearer can be automatically

selected to connect the call. That is, when one type of inter-MGW path (such as the

TDM path) fails to be selected, an attempt is made to select another type of

inter-MGW path (such as the IP path).

Upon selection of the intra-MSC bearer, if the IP bearer cannot be established between

MSCs (for example, adding the IP termination fails or the IP QoS congestion

indication is received), differential processing can be performed based on the

subscriber priority. For example, for a subscriber with higher priority, the system

automatically selects the TDM bearer to connect the call. For a subscriber with lower

priority, the system releases the call.


The inter-MGW networking is more flexible. The TDM network can be smoothly

migrated to the IP network. During this migration process, the system supports

both the IP bearer and the TDM bearer and selects the bearer type based on the

configured proportions of the two bearers.

� For subscribers

Reduce the connection failure due to the problems related to inter-MGW bearer.

Description

Upon selection of the intra-MSC inter-MGW bearer, if the IP bearer cannot be

established within the MSC, the intermediate TDM bearer can be automatically

selected to connect the call. That is, when one type of inter-MGW path (such as the

TDM path) fails to be selected, an attempt is made to select another type of

inter-MGW path (such as the IP path).

Upon selection of the intra-MSC bearer, if the IP bearer cannot be established between

MSCs (for example, adding the IP termination fails or the IP QoS congestion

MSOFTX3000V100R008

Additional Feature

Description



Page 127 of 131

indication is received), differential processing can be performed based on the

subscriber priority. For example, for a subscriber with higher priority, the system

automatically selects the TDM bearer to connect the call. For a subscriber with lower

priority, the system releases the call.

Enhancement

None

Dependency

The MGWs must support the intra-MSC inter-MGW IP-TDM dual bearer feature. The

data, based on which the IP bearer or the TDM bearer is used, must be configured on

the MGWs.

The MGWs must be able to report the IP QoS congestion information to the MSC

server.

MSOFTX3000V100R008

Additional Feature

Description



Page 128 of 131

2 Acronyms and Abbreviations Table 2-1 List of abbreviations

abbreviations Explaination

AAL ATM Adaptation Layer

AAL2 ATM Adaptation Layer type 2

ALU Alarm Unit

AMR Adaptive multi Rate

ARP Address Resolution Protocol

BAIC Barring of All Incoming Calls

BAM Back Administration Module

BAOC Barring of All Outgoing Calls

BAU Bill Administration Unit

BFI Bad Frame Indication

BIC-Roam Barring of Incoming Calls When Roaming Outside

Home PLMN Country

B-ISDN Broadband Integrated Services Digital Networks

BOIC Barring of Outgoing International Calls

BOIC-exHC Barring of Outgoing International Calls except those

directed to the Home PLMN Country

BSSAP Base Station Subsystem Application Part

CB Cell Broadcast

CCU Channel Codec Unit

CFNRc Call Forwarding on mobile subscriber Not

Reachable

MSOFTX3000V100R008

Additional Feature

Description



Page 129 of 131


CFU Call Forwarding Unconditional

CLIP Calling Line Identification Presentation

CLIR Calling Line Identification Restriction

CODEC Coder-decoder

CoLP COnnected Line Identification Presentation

CoLR COnnected Line Identification Restriction

CPC Central Processing Board

cPCI

CPU Central Processing Unit

CUG Closed User Group

DDN Digital Data Network

DTMF Dual Tone Multi Frequency

ESP Early Support Program

EtherNet

FEP Front End Processor

FLASH FLASH memory

FTP File Transfer Protocol

GE Gigabit Ethernet

GLONASS GLObal NAvigation Satellite System

GMLC Gateway Mobile Location Center

HLR Home Location Register

HOLD Call Hold

HSC Hot Swap Controller

HSTP High-level Signaling Transfer Point

HW Highway

ICMP Internet Control Message Protocol

IDP Individual Development Plan

IFM IP Forward Module

IIN Integrated Intelligent Network

IMSI International Mobile Subscriber Identity

MSOFTX3000V100R008

Additional Feature

Description



Page 130 of 131


IN Intelligent Network

ISDN Integrated Services Digital Network

ITU-T International Telecommunication Union -

Telecommunication Standardization Sector

IU Iu Interface

IWF InterWorking Function

LAN Local Area Network

LSTP Low-level Signaling Transfer Point

MAP Mobile Application Part

MML Man Machine Language

MODEM MOdulator-DEModulator

MSISDN Mobile Station International ISDN Number

MSRN Mobile Station Roaming Number

MTP Message Transfer Part

MTP2 Message Transfer Part Layer 2

MTP3 Message Transfer Part Layer 3

MTP3b Message transfer part (broadband)

RARP Reverse Adress Resolution Protocol

RDI Remote Defect Indication

SCTP Stream Control Transmission Protocol

SDF Service Data Function

SDH Synchronous Digital Hierarchy

SGU Software fault-oriented Group Unblocking message

TCU Temprature Control Unit

TDMA Time Division Multiple Access

TFO Tandem Free Operation

TMSI Temporary Mobile Subscriber Identifier

TUP Telephone User Part

UDI Unrestricted Digital Information

UDP User Datagram Protocol

MSOFTX3000V100R008

Additional Feature

Description



Page 131 of 131


UE User Equipment

UL Uplink

UMTS Universal mobile telecommunication

services/Universal Mobile Telecommunications

System;

UPWR UMSC PSM PoWeR module

USSD Unstructured Supplementary Service Data

UTRAN UMTS Terrestrial Radio Access Network

VDB VLR Database

VIEU Versatile Interface Extend Unit

VLR Visitor Location Register

VMSC Visited Mobile Switching Center , Visited MSC

VPN Virtual Private Network

WAD Wireless Advertisement;

WCDMA Wide(band) Code Division Multiple Access

WIN Wireless Intelligent Network

Documents

MSOFTX3000V100R008 Additional Feature Description V1.0