HUAWEI MSOFTX3000 Mobile Softswitch Center V100R005C10

Feature Description

Issue Date Part Number

02 2007-06-10 31400597

Huawei Technologies Proprietary

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com

Copyright © Huawei Technologies Co., Ltd. 2007. 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 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 Proprietary

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
Index ................................................................................................................................................ i-1

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i

HUAWEI MSOFTX3000 Feature Description

Index

Index
A
Alert SC, 2-3 availability alarm for malicious short message, 30-3 authentication, 10-3 automatic device detection, 37-3 call barring service, 7-3 call completion, 5-3 call forwarding, 3-3 call simulation, 31-5 CAMEL4 service, 22-4 dialing test on designated TDM circuit, 35-3 early and late assignment feature, 12-3 ECT, 8-3 enhanced MSRN allocation feature, 11-4 IMSI-based announcement, 23-4 IN service performance measurement enhancement, 36-4 IN service triggering feature, 13-3 IP over E1, 24-4 IP QoS flow control, 25-3 load-based handover, 32-3 MNP feature, 14-3 multiparty, 6-3 O-CSI SMS, 26-3 ODB, 9-4 role-based and domain-based management, 29-7 service restriction, 34-4 short message service, 2-4 speech service, 1-4 union subscriber trace, 33-4 UP header redundancy data service, 27-3 VDB dynamic data backup, 28-4 CW, 5-2 call forwarding CFB, 3-2 CFNRc, 3-3 CFNRy, 3-2 CFU, 3-2 charging and CDR call barring service, 7-15 call completion, 5-17 call forwarding, 3-21 call simulation, 31-17 CAMEL4 service, 22-18 dialing test on designated TDM circuit, 35-11 ECT, 8-9 enhanced MSRN allocation feature, 11-14 IN service triggering feature, 13-14 MNP feature, 14-15 multiparty, 6-12 O-CSI SMS, 26-18 service restriction, 34-24 short message service, 2-15 speech service, 1-22

D
data configuration alarm for malicious short message, 30-7 authentication, 10-7 automatic device detection, 37-7 call barring service, 7-12 call completion, 5-12 call forwarding, 3-18 call simulation, 31-10 CAMEL4 service, 22-13 dialing test on designated TDM circuit, 35-9 early and late assignment feature, 12-17 ECT, 8-7 enhanced MSRN allocation feature, 11-9 IMSI-based announcement, 23-8 IN service performance measurement enhancement, 36-13 IN service triggering feature, 13-10 IP fax feature, 15-7 IP over E1, 24-11

C
call barring service BAIC, 7-3 BAOC, 7-2 BOIC, 7-2 BOIC-exHC, 7-2 call completion CH, 5-2

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i-1

Index

HUAWEI MSOFTX3000 Feature Description

IP QoS flow control, 25-11 line identification, 4-9 load-based handover, 32-12 MNP feature, 14-9 multiparty, 6-10 O-CSI SMS, 26-10 ODB, 9-6 role-based and domain-based management, 29-10 service restriction, 34-9 short message service, 2-13 speech service, 1-21 union subscriber trace, 33-11 UP header redundancy data service, 27-15 VDB dynamic data backup, 28-14

ODB-BIC, 9-3 ODB-BOC, 9-3 ODB-POS, 9-4 ODB-ROAM, 9-3 ODB-SS, 9-3 Operation and Maintenance of License DLD LICENSE, 16-12 DMP LICENSE, 16-10 DSP ESN, 16-7 DSP LICENSE, 16-9 LOD LICENSE, 16-4 LST LICENSE, 16-6 ROL LICENSE, 16-5 STR LICCRC, 16-9 ULD LICENSE, 16-11

E
early and late assignment feature MS-originated call (late assignment), 12-5 MS-terminated call (early assignment), 12-6

P
performance measurement call simulation, 31-17 CAMEL4 service, 22-18 IMSI-based announcement, 23-13 IN service performance measurement enhancement, 36-19 load-based handover, 32-16 UP header redundancy data service, 27-19

F
feature description IP QoS flow control, 25-2 VDB dynamic data backup, 28-2

L
license control items control item, 16-12 resource control item, 16-15 license feature alarm, 16-19 effects of BAM operation, 16-20 invalidation and prevention, 16-17 license checks, 16-17 Upgrade, 16-20 line identification CLIP, 4-3 CLIR, 4-3 COLP, 4-3 COLR, 4-3 Line Identity, 4-2

R
reference authentication, 10-7 automatic device detection, 37-11 call barring service, 7-21 call completion, 5-19 call forwarding, 3-35 call simulation, 31-17 CAMEL4 service, 22-6, 22-21 charging and CDR, 11-15 dialing test on designated TDM circuit, 35-12 ECT, 8-13 IMSI-based announcement, 23-13 IN service performance measurement enhancement, 36-20 IN service triggering feature, 13-15 IP over E1, 24-20 IP QoS flow control, 25-18 license feature, 16-21 line identification, 4-14 load-based handover, 32-16 MNP feature, 14-16 multiparty, 6-14 O-CSI SMS, 26-18 ODB, 9-8 role-based and domain-based management, 25-18, 29-20 service interaction, 12-23

M
MOC, 1-3 MSRN allocation feature based on the LAI number, 11-3 based on the MSC number, 11-2 random allocation, 11-3 MTC, 1-3

O
ODB

i-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Index

service restriction, 34-25 short message service, 2-17 speech service, 1-26 union subscriber trace, 33-5, 33-14 UP header redundancy data service, 27-20 VDB dynamic data backup, 28-22

S
service description alarm for malicious short message, 30-2 authentication, 10-2 automatic device detection, 37-2 call barring service, 7-2 call completion, 5-2 call forwarding, 3-2 call simulation, 31-2 CAMEL4 service, 22-2 dialing test on designated TDM circuit, 35-2 early and late assignment feature, 12-2 ECT, 8-2 enhanced MSRN allocation feature, 11-2 IMSI-based announcement, 23-3 IN service performance measurement enhancement, 36-3 IN service triggering feature, 13-2 IP fax feature, 15-2 IP over E1, 24-2 license feature, 16-2 line identification, 4-2 load-based handover, 32-2 MNP feature, 14-2 multiparty, 6-2 O-CSI SMS, 26-2 ODB, 9-2 role-based and domain-based management, 29-3 service restriction, 34-2 short message service, 2-2 speech service, 1-2 union subscriber trace, 33-2 UP header redundancy data service, 27-2 service flow alarm for malicious short message, 30-5 authentication, 10-4 automatic device detection, 37-5 call barring service, 7-10 call completion, 5-7 call forwarding, 3-7 call simulation, 31-8 CAMEL4 service, 22-6 dialing test on designated TDM circuit, 35-5 early and late assignment feature, 12-9 ECT, 8-5 enhanced MSRN allocation feature, 11-7 IMSI-based announcement, 23-7

IN service performance measurement enhancement, 36-8 IP fax feature, 15-3 IP over E1, 24-8 line identification, 4-6 load-based handover, 32-7 MNP feature, 14-5 multiparty, 6-5 O-CSI SMS, 26-8 ODB, 9-5 role-based and domain-based management, 29-9 service restriction, 34-5 short message service, 2-6 speech service, 1-7 union subscriber trace, 33-5 UP header redundancy data service, 27-9 VDB dynamic data backup, 28-8 service interaction call barring service, 7-15 call completion, 5-18 call forwarding, 3-24 CAMEL4 service, 22-19 early and late assignment feature, 12-22 ECT, 8-12 IN service triggering feature, 13-14 IP QoS flow control, 25-18 line identification, 4-12 MNP feature, 14-16 multiparty, 6-13 ODB, 9-7 short message service, 2-16 speech service, 1-26 service interaction O-CSI SMS, 26-18 service interaction service restriction, 34-24 service management authentication, 10-7 automatic device detection, 37-10 call barring service, 7-13 call completion, 5-14 call forwarding, 3-18 call simulation, 31-11 CAMEL4 service, 22-17 early and late assignment feature, 12-21 ECT, 8-8 IN service performance measurement enhancement, 36-18 line identification, 4-11 load-based handover, 32-15 multiparty, 6-11 O-CSI SMS, 26-16 ODB, 9-7 short message service, 2-15 speech service, 1-22

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i-3

Index

HUAWEI MSOFTX3000 Feature Description

union subscriber trace, 33-12 VDB dynamic data backup, 28-20 service management alarm for malicious short message, 30-9 SM MO, 2-3 SM MT, 2-2

W
working principle alarm for malicious short message, 30-4 authentication, 10-3 automatic device detection, 37-4 call barring service, 7-4 call completion, 5-4 call forwarding, 3-4 call simulation, 31-5 CAMEL4 service, 22-6 dialing test on designated TDM circuit, 35-4 early and late assignment feature, 12-4 ECT, 8-3 enhanced MSRN allocation feature, 11-5

IN service performance measurement enhancement, 36-5 IN service triggering feature, 13-3 IP fax feature, 15-2 IP over E1, 24-4 IP QoS flow control, 25-4 license feature, 16-2 line identification, 4-5 load-based handover, 32-4 MNP feature, 14-3 multiparty, 6-3 O-CSI SMS, 26-4 ODB, 9-5 role-based and domain-based management, 29-8 service restriction, 34-4 short message service, 2-5 speech service, 1-5 union subscriber trace, 33-4, 33-5 UP header redundancy data service, 27-3 VDB dynamic data backup, 28-4

i.

i-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
About This Document.....................................................................................................................1 1 Speech Service ............................................................................................................................1-1
1.1 Service Description .....................................................................................................................................1-2 1.1.1 Function Code ...................................................................................................................................1-2 1.1.2 Definition ..........................................................................................................................................1-2 1.1.3 Benefits .............................................................................................................................................1-4 1.2 Availability ..................................................................................................................................................1-4 1.2.1 Requirements for NEs .......................................................................................................................1-4 1.2.2 Requirements for License..................................................................................................................1-4 1.2.3 Applicable Versions...........................................................................................................................1-4 1.3 Working Principle........................................................................................................................................1-5 1.3.1 MOC..................................................................................................................................................1-5 1.3.2 MTC ..................................................................................................................................................1-6 1.3.3 MMC .................................................................................................................................................1-7 1.4 Service Flow................................................................................................................................................1-7 1.4.1 MOC to Fixed Line Subscriber .........................................................................................................1-8 1.4.2 MTC from Fixed Line Subscriber ................................................................................................... 1-11 1.4.3 MMC ...............................................................................................................................................1-15 1.5 Data Configuration ....................................................................................................................................1-21 1.5.1 Telephony ........................................................................................................................................1-21 1.5.2 Emergency Call for Special Service................................................................................................1-21 1.5.3 Charging Flag of Emergency Call ...................................................................................................1-21 1.6 Service Management .................................................................................................................................1-22 1.6.1 For Carriers .....................................................................................................................................1-22 1.6.2 For Mobile Subscribers ...................................................................................................................1-22 1.7 Charging and CDR ....................................................................................................................................1-22 1.7.1 Generation of CDR..........................................................................................................................1-22 1.7.2 CDR for Ordinary Call ....................................................................................................................1-22 1.7.3 CDR for Emergency Call ................................................................................................................1-25 1.8 Service Interaction.....................................................................................................................................1-26 1.9 Reference...................................................................................................................................................1-26 1.9.1 Protocols and Specifications ...........................................................................................................1-26

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

i

Contents

HUAWEI MSOFTX3000 Feature Description 1.9.2 Acronyms and Abbreviations ..........................................................................................................1-26

2 Short Message Service ..............................................................................................................2-1
2.1 Service Description .....................................................................................................................................2-2 2.1.1 Function Code ...................................................................................................................................2-2 2.1.2 Definition ..........................................................................................................................................2-2 2.1.3 Benefits .............................................................................................................................................2-3 2.2 Availability ..................................................................................................................................................2-4 2.2.1 Requirements for NEs .......................................................................................................................2-4 2.2.2 Requirements for License..................................................................................................................2-4 2.2.3 Applicable Versions...........................................................................................................................2-4 2.3 Working Principle........................................................................................................................................2-5 2.3.1 Networking Structure ........................................................................................................................2-5 2.3.2 Short Message Transfer Path.............................................................................................................2-6 2.4 Service Flows ..............................................................................................................................................2-6 2.4.1 MAP Flows Related to SMS .............................................................................................................2-6 2.4.2 SM MO Flow ....................................................................................................................................2-9 2.4.3 SM MT Flow.....................................................................................................................................2-9 2.4.4 Alert SMC Flows............................................................................................................................. 2-11 2.5 Data Configuration ....................................................................................................................................2-13 2.5.1 Data Configuration of the MSOFTX3000.......................................................................................2-13 2.5.2 Data Configuration of the HLR.......................................................................................................2-14 2.6 Service Management .................................................................................................................................2-15 2.6.1 For Carrier.......................................................................................................................................2-15 2.6.2 For Mobile Subscriber.....................................................................................................................2-15 2.7 Charging and CDR ....................................................................................................................................2-15 2.8 Service Interaction.....................................................................................................................................2-16 2.9 Reference...................................................................................................................................................2-17 2.9.1 Protocols and Specifications ...........................................................................................................2-17 2.9.2 Acronyms and Abbreviations ..........................................................................................................2-17

3 Call Forwarding Supplementary Service ..............................................................................3-1
3.1 Service Description .....................................................................................................................................3-2 3.1.1 Function Code ...................................................................................................................................3-2 3.1.2 Definition ..........................................................................................................................................3-2 3.1.3 Benefits .............................................................................................................................................3-3 3.2 Availability ..................................................................................................................................................3-3 3.2.1 Requirements for NEs .......................................................................................................................3-3 3.2.2 Requirements for License..................................................................................................................3-4 3.2.3 Applicable Versions...........................................................................................................................3-4 3.3 Working Principle........................................................................................................................................3-4 3.3.1 Functions of the NEs .........................................................................................................................3-4 3.3.2 Service Flow Inside the System ........................................................................................................3-4

ii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

3.4 Service Flow................................................................................................................................................3-7 3.4.1 CFU Service Flow.............................................................................................................................3-7 3.4.2 CFB Service Flow .............................................................................................................................3-8 3.4.3 CFNRy Service Flow ......................................................................................................................3-13 3.4.4 CFNRy Service Flow ......................................................................................................................3-15 3.5 Data Configuration ....................................................................................................................................3-18 3.5.1 MSOFTX3000 Data Configuration.................................................................................................3-18 3.5.2 HLR Configuration .........................................................................................................................3-18 3.6 Service Management .................................................................................................................................3-18 3.6.1 Operations by the Carriers...............................................................................................................3-19 3.6.2 Operations by the Subscribers .........................................................................................................3-19 3.7 Charging and CDR ....................................................................................................................................3-21 3.7.1 Charging Principle...........................................................................................................................3-21 3.7.2 Difference Between CFU and CCF in Judging an International Call..............................................3-22 3.7.3 CDR Creation Principles .................................................................................................................3-22 3.8 Service Interaction.....................................................................................................................................3-24 3.8.1 CFU .................................................................................................................................................3-24 3.8.2 CFB .................................................................................................................................................3-27 3.8.3 CFNRy ............................................................................................................................................3-30 3.8.4 CFNRc.............................................................................................................................................3-32 3.9 References .................................................................................................................................................3-35 3.9.1 Protocols and Specifications ...........................................................................................................3-35 3.9.2 Acronyms and Abbreviations ..........................................................................................................3-35

4 Line Identification Service .......................................................................................................4-1
4.1 Service Description .....................................................................................................................................4-2 4.1.1 Function Code ...................................................................................................................................4-2 4.1.2 Definition ..........................................................................................................................................4-2 4.1.3 Types .................................................................................................................................................4-3 4.1.4 Benefits .............................................................................................................................................4-4 4.2 Availability ..................................................................................................................................................4-4 4.2.1 Requirements for NEs .......................................................................................................................4-4 4.2.2 Requirements for License..................................................................................................................4-5 4.2.3 Applicable Versions...........................................................................................................................4-5 4.3 Working Principle........................................................................................................................................4-5 4.3.1 Service Data Management.................................................................................................................4-5 4.3.2 CLIP ..................................................................................................................................................4-5 4.3.3 CLIR..................................................................................................................................................4-5 4.3.4 COLP.................................................................................................................................................4-6 4.3.5 COLR ................................................................................................................................................4-6 4.4 Service Flow................................................................................................................................................4-6 4.4.1 CLIP ..................................................................................................................................................4-6

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

iii

Contents

HUAWEI MSOFTX3000 Feature Description 4.4.2 CLIR..................................................................................................................................................4-7 4.4.3 COLP.................................................................................................................................................4-8 4.4.4 COLR ................................................................................................................................................4-8

4.5 Data Configuration ......................................................................................................................................4-9 4.5.1 Configuring Data at the MSOFTX3000 Side ....................................................................................4-9 4.5.2 Configuring Data at the HLR Side .................................................................................................. 4-11 4.6 Service Management ................................................................................................................................. 4-11 4.6.1 Opreations by Carriers..................................................................................................................... 4-11 4.6.2 Operations by Mobile Subscribers .................................................................................................. 4-11 4.7 Service Interaction.....................................................................................................................................4-12 4.7.1 CLIP ................................................................................................................................................4-12 4.7.2 CLIR................................................................................................................................................4-13 4.7.3 COLP...............................................................................................................................................4-13 4.7.4 COLR ..............................................................................................................................................4-14 4.8 Reference...................................................................................................................................................4-14 4.8.1 Protocols and Specifications ...........................................................................................................4-14 4.8.2 Acronyms and Abbreviations ..........................................................................................................4-15

5 Call Completion Supplementary Service..............................................................................5-1
5.1 Service Description .....................................................................................................................................5-2 5.1.1 Function Code ...................................................................................................................................5-2 5.1.2 Definition ..........................................................................................................................................5-2 5.1.3 Benefits .............................................................................................................................................5-3 5.2 Availability ..................................................................................................................................................5-3 5.2.1 Requirements for NEs .......................................................................................................................5-3 5.2.2 Requirements for License..................................................................................................................5-3 5.2.3 Applicable Versions...........................................................................................................................5-4 5.3 Working Principle........................................................................................................................................5-4 5.3.1 Service Data Management.................................................................................................................5-4 5.3.2 Working Principle of CW ..................................................................................................................5-4 5.3.3 Working Principle of CH...................................................................................................................5-5 5.4 Service Flow................................................................................................................................................5-6 5.4.1 Service Flow of CW ..........................................................................................................................5-6 5.4.2 Service Flow of CH.........................................................................................................................5-10 5.5 Data Configuration ....................................................................................................................................5-12 5.5.1 Configuring Data at the MSOFTX3000 Side ..................................................................................5-12 5.5.2 Configuring Data at the HLR Side ..................................................................................................5-14 5.6 Service Management .................................................................................................................................5-14 5.6.1 Overview .........................................................................................................................................5-14 5.6.2 Operations by Carriers.....................................................................................................................5-15 5.6.3 Operations by Mobile Subscribers ..................................................................................................5-15 5.7 Charging and CDR ....................................................................................................................................5-16

iv

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

5.7.1 CW ..................................................................................................................................................5-16 5.7.2 CH ...................................................................................................................................................5-17 5.8 Service Interaction.....................................................................................................................................5-18 5.8.1 CW ..................................................................................................................................................5-18 5.8.2 CH ...................................................................................................................................................5-19 5.9 Reference...................................................................................................................................................5-19 5.9.1 Protocols and Specifications ...........................................................................................................5-19 5.9.2 Acronyms and Abbreviations ..........................................................................................................5-19

6 Multiparty Service .....................................................................................................................6-1
6.1 Service Description .....................................................................................................................................6-2 6.1.1 Function Code ...................................................................................................................................6-2 6.1.2 Definition ..........................................................................................................................................6-2 6.1.3 Benefits .............................................................................................................................................6-2 6.2 Availability ..................................................................................................................................................6-3 6.2.1 Requirements for NEs .......................................................................................................................6-3 6.2.2 Requirements for License..................................................................................................................6-3 6.2.3 Applicable Versions...........................................................................................................................6-3 6.3 Working Principle........................................................................................................................................6-3 6.3.1 Functions Realized by Network Elements.........................................................................................6-3 6.3.2 Service Data Management.................................................................................................................6-4 6.3.3 MPTY Invocation..............................................................................................................................6-4 6.3.4 MPTY Call Management ..................................................................................................................6-4 6.4 Service Flow................................................................................................................................................6-5 6.4.1 Setting up the MPTY Call .................................................................................................................6-5 6.4.2 Setting Up a Personal Communication with Remote Subscriber ......................................................6-6 6.4.3 Adding a Remote Subscriber.............................................................................................................6-7 6.4.4 Disconnecting a Remote Subscriber..................................................................................................6-8 6.5 Data Configuration ......................................................................................................................................6-9 6.5.1 Data Configuration at MSOFTX3000 Side .......................................................................................6-9 6.5.2 Data Configuration at UMG8900 Side............................................................................................6-10 6.6 Service Management ................................................................................................................................. 6-11 6.6.1 Carrier Operation............................................................................................................................. 6-11 6.6.2 Mobile Subscriber Operation .......................................................................................................... 6-11 6.7 Charging and CDR ....................................................................................................................................6-12 6.8 Service Interaction.....................................................................................................................................6-13 6.9 Reference...................................................................................................................................................6-14 6.9.1 Protocols and Specifications ...........................................................................................................6-14 6.9.2 Acronyms and Abbreviations ..........................................................................................................6-14

7 Call Barring Service ...................................................................................................................7-1
7.1 Service Description .....................................................................................................................................7-2 7.1.1 Function Code ...................................................................................................................................7-2

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

v

Contents

HUAWEI MSOFTX3000 Feature Description 7.1.2 Definition ..........................................................................................................................................7-2 7.1.3 Types .................................................................................................................................................7-2 7.1.4 Benefits .............................................................................................................................................7-3

7.2 Availability ..................................................................................................................................................7-3 7.2.1 Requirements for NEs .......................................................................................................................7-3 7.2.2 Requirements for License..................................................................................................................7-3 7.2.3 Applicable Versions...........................................................................................................................7-4 7.3 Working Principle........................................................................................................................................7-4 7.3.1 Service Data Management.................................................................................................................7-4 7.3.2 BO .....................................................................................................................................................7-4 7.3.3 BI.......................................................................................................................................................7-8 7.4 Service Flow..............................................................................................................................................7-10 7.4.1 BO ...................................................................................................................................................7-10 7.4.2 BI..................................................................................................................................................... 7-11 7.5 Data Configuration ....................................................................................................................................7-12 7.5.1 Configuring Data at the MSOFTX3000 Side ..................................................................................7-12 7.5.2 Configuring Data at the HLR Side ..................................................................................................7-13 7.6 Service Management .................................................................................................................................7-13 7.6.1 Operations by Carriers.....................................................................................................................7-13 7.6.2 Operations by Mobile Subscribers ..................................................................................................7-13 7.7 Charging and CDR ....................................................................................................................................7-15 7.8 Service Interaction.....................................................................................................................................7-15 7.8.1 BAOC..............................................................................................................................................7-15 7.8.2 BOIC ...............................................................................................................................................7-15 7.8.3 BOIC-exHC.....................................................................................................................................7-17 7.8.4 BAIC ...............................................................................................................................................7-18 7.8.5 BIC-ROAM.....................................................................................................................................7-19 7.9 Reference...................................................................................................................................................7-21 7.9.1 Protocols and Specifications ...........................................................................................................7-21 7.9.2 Acronyms and Abbreviations ..........................................................................................................7-21

8 Explicit Call Transfer Service ..................................................................................................8-1
8.1 Service Description .....................................................................................................................................8-2 8.1.1 Function Code ...................................................................................................................................8-2 8.1.2 Definition ..........................................................................................................................................8-2 8.1.3 Benefits .............................................................................................................................................8-2 8.2 Availability ..................................................................................................................................................8-3 8.2.1 Requirements for NEs .......................................................................................................................8-3 8.2.2 Requirements for License..................................................................................................................8-3 8.2.3 Applicable Versions...........................................................................................................................8-3 8.3 Working Principle........................................................................................................................................8-3 8.3.1 Functions of Each NE .......................................................................................................................8-3

vi

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

8.3.2 Service Data Management.................................................................................................................8-3 8.3.3 Invoking the ECT ..............................................................................................................................8-4 8.4 Service Flow................................................................................................................................................8-4 8.4.1 A-B Call Is on Hold and A-C Call Is in the Active State...................................................................8-4 8.4.2 A-B Call Is in the Active State and A-C Call Is in the Alerting State................................................8-5 8.5 Data Configuration ......................................................................................................................................8-7 8.5.1 Data Configuration on the MSOFTX3000 ........................................................................................8-7 8.5.2 Data Configuration on the UMG8900 ...............................................................................................8-7 8.6 Service Management ...................................................................................................................................8-8 8.6.1 Operation Mode.................................................................................................................................8-8 8.6.2 Operations by the Carriers.................................................................................................................8-8 8.6.3 Operations by the Mobile Subscribers ..............................................................................................8-8 8.7 Charging and CDR ......................................................................................................................................8-9 8.7.1 Introduction to the Charging Mode ...................................................................................................8-9 8.7.2 Independent Charging .......................................................................................................................8-9 8.7.3 Segmented Charging .......................................................................................................................8-10 8.8 Service Interaction.....................................................................................................................................8-12 8.9 Reference...................................................................................................................................................8-13 8.9.1 Protocols and Specifications ...........................................................................................................8-13 8.9.2 Acronyms and Abbreviations ..........................................................................................................8-14

9 ODB Service ................................................................................................................................9-1
9.1 Service Description .....................................................................................................................................9-2 9.1.1 Function Code ...................................................................................................................................9-2 9.1.2 Definition ..........................................................................................................................................9-2 9.1.3 Service Type ......................................................................................................................................9-3 9.1.4 Benefits .............................................................................................................................................9-4 9.2 Availability ..................................................................................................................................................9-4 9.2.1 Requirement for NEs.........................................................................................................................9-4 9.2.2 Requirement for License ...................................................................................................................9-4 9.2.3 Applicable Versions...........................................................................................................................9-5 9.3 Working Principle........................................................................................................................................9-5 9.4 Service Flow................................................................................................................................................9-5 9.4.1 Barring of Incoming Calls or MS MT...............................................................................................9-5 9.4.2 Barring of Outgoing Calls or MS MO...............................................................................................9-5 9.4.3 Barring of Roaming...........................................................................................................................9-6 9.4.4 Barring of Supplementary Services...................................................................................................9-6 9.4.5 Barring of Packet Services ................................................................................................................9-6 9.5 Data Configuration ......................................................................................................................................9-6 9.5.1 Data Configuration for MSOFTX3000 .............................................................................................9-6 9.5.2 Data Configuration for UMG8900 ....................................................................................................9-7 9.6 Service Management ...................................................................................................................................9-7

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

vii

Contents

HUAWEI MSOFTX3000 Feature Description

9.7 Charging and CDR ......................................................................................................................................9-7 9.8 Service Interaction.......................................................................................................................................9-7 9.9 Reference.....................................................................................................................................................9-8 9.9.1 Protocols and Specifications .............................................................................................................9-8 9.9.2 Acronyms and Abbreviations ............................................................................................................9-8

10 Authentication Feature..........................................................................................................10-1
10.1 Service Description .................................................................................................................................10-2 10.1.1 Function Code ...............................................................................................................................10-2 10.1.2 Definition ......................................................................................................................................10-2 10.1.3 Benefits .........................................................................................................................................10-2 10.2 Availability ..............................................................................................................................................10-3 10.2.1 Requirements for NEs ...................................................................................................................10-3 10.2.2 Requirements for License..............................................................................................................10-3 10.2.3 Applicable Versions.......................................................................................................................10-3 10.3 Working Principle....................................................................................................................................10-3 10.4 Service Flow............................................................................................................................................10-4 10.4.1 UMTS Authentication ...................................................................................................................10-4 10.4.2 GSM Authentication......................................................................................................................10-5 10.5 Data Configuration ..................................................................................................................................10-7 10.5.1 Data Configuration on MSOFTX3000 ..........................................................................................10-7 10.5.2 Data Configuration on HLR ..........................................................................................................10-7 10.6 Service Management ...............................................................................................................................10-7 10.6.1 Subscription of Authentication ......................................................................................................10-7 10.6.2 Query of Authentication ................................................................................................................10-7 10.7 Reference.................................................................................................................................................10-7 10.7.1 Protocols and Specifications .........................................................................................................10-7 10.7.2 Glossary, Acronyms and Abbreviations.........................................................................................10-8

11 Enhanced MSRN Allocation Feature .................................................................................11-1
11.1 Service Description.................................................................................................................................. 11-2 11.1.1 Function Code ............................................................................................................................... 11-2 11.1.2 Definition ...................................................................................................................................... 11-2 11.1.3 Benefits.......................................................................................................................................... 11-4 11.2 Availability............................................................................................................................................... 11-4 11.2.1 Requirements for NEs ................................................................................................................... 11-4 11.2.2 Requirements for License.............................................................................................................. 11-4 11.2.3 Applicable Versions ....................................................................................................................... 11-4 11.3 Working Principle.................................................................................................................................... 11-5 11.3.1 Functions of NEs ........................................................................................................................... 11-5 11.3.2 Processing in the System ............................................................................................................... 11-5 11.4 Service Flow............................................................................................................................................ 11-7 11.4.1 General Procedure of MSRN Allocation ....................................................................................... 11-7

viii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

11.4.2 Procedure for Random Allocation ................................................................................................. 11-8 11.5 Data Configuration .................................................................................................................................. 11-9 11.5.1 Configuring Data at the MSOFTX3000 Side ................................................................................ 11-9 11.5.2 Configuraing Data at the UMG8900 Side ................................................................................... 11-10 11.5.3 Configuration Examples .............................................................................................................. 11-10 11.6 Service Management ............................................................................................................................. 11-14 11.7 Charging and CDR ................................................................................................................................ 11-14 11.8 Service Interaction................................................................................................................................. 11-14 11.9 Reference............................................................................................................................................... 11-15 11.9.1 Protocols and Specifications........................................................................................................ 11-15 11.9.2 Acronyms and Abbreviations....................................................................................................... 11-15

12 Early and Late Assignment Feature....................................................................................12-1
12.1 Service Description .................................................................................................................................12-2 12.1.1 Function Code ...............................................................................................................................12-2 12.1.2 Definition ......................................................................................................................................12-2 12.1.3 Benefits .........................................................................................................................................12-3 12.2 Availability ..............................................................................................................................................12-3 12.2.1 Requirements for NEs ...................................................................................................................12-3 12.2.2 Requirements for License..............................................................................................................12-3 12.2.3 Applicable Version ........................................................................................................................12-3 12.3 Working Principle....................................................................................................................................12-4 12.3.1 MS-Originated Call (Early Assignment) .......................................................................................12-4 12.3.2 MS-Originated Call (Late Assignment).........................................................................................12-5 12.3.3 MS-Terminated Call (Early Assignment) ......................................................................................12-6 12.4 Service Flow............................................................................................................................................12-9 12.4.1 Early Resource Assignment for the Caller ....................................................................................12-9 12.4.2 Late Resource Assignment for the Caller .................................................................................... 12-11 12.4.3 Early Resource Assignment for the Callee ..................................................................................12-13 12.4.4 Late Resource Assignment for the Callee....................................................................................12-15 12.5 Data Configuration ................................................................................................................................12-17 12.5.1 MSOFTX3000 Data Configuration.............................................................................................12-17 12.5.2 HLR Data Configuration .............................................................................................................12-18 12.5.3 UMG8900 Data Configuration....................................................................................................12-18 12.5.4 Examples .....................................................................................................................................12-18 12.6 Service Management .............................................................................................................................12-21 12.6.1 Querying the Resource Assignment Mode ..................................................................................12-21 12.6.2 Changing the Resource Assignment Mode..................................................................................12-22 12.7 Charging and CDR ................................................................................................................................12-22 12.8 Service Interaction.................................................................................................................................12-22 12.9 Reference...............................................................................................................................................12-23 12.9.1 Protocols and Specifications .......................................................................................................12-23

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

ix

Contents

HUAWEI MSOFTX3000 Feature Description 12.9.2 Acronyms and Abbreviations ......................................................................................................12-23

13 IN Service Triggering Feature .............................................................................................13-1
13.1 Service Description .................................................................................................................................13-2 13.1.1 Function Code ...............................................................................................................................13-2 13.1.2 Definition ......................................................................................................................................13-2 13.1.3 Benefits .........................................................................................................................................13-2 13.2 Availability ..............................................................................................................................................13-3 13.2.1 Requirement for NEs.....................................................................................................................13-3 13.2.2 Requirement for License ...............................................................................................................13-3 13.2.3 Applicable Versions.......................................................................................................................13-3 13.3 Working Principle....................................................................................................................................13-3 13.4 Service Flow..........................................................................................................................................13-10 13.5 Data Configuration ................................................................................................................................13-10 13.5.1 Data Configuration for MSOFTX3000 .......................................................................................13-10 13.5.2 Data Configuration for HLR9820 ...............................................................................................13-10 13.5.3 Data Configuration for UMG8900 ..............................................................................................13-10 13.5.4 Example....................................................................................................................................... 13-11 13.6 Service Management .............................................................................................................................13-14 13.7 Charging and CDR ................................................................................................................................13-14 13.8 Service Interaction.................................................................................................................................13-14 13.9 References .............................................................................................................................................13-15 13.9.1 Specifications ..............................................................................................................................13-15 13.9.2 Acronyms and Abbreviations ......................................................................................................13-15

14 MNP Feature ...........................................................................................................................14-1
14.1 Feature Description .................................................................................................................................14-2 14.1.1 Feature Code .................................................................................................................................14-2 14.1.2 Function Definition .......................................................................................................................14-2 14.1.3 Service Benefits.............................................................................................................................14-2 14.2 Availability ..............................................................................................................................................14-3 14.2.1 Related Network Elements............................................................................................................14-3 14.2.2 License Support.............................................................................................................................14-3 14.2.3 Version Support .............................................................................................................................14-3 14.3 Principle Description ...............................................................................................................................14-3 14.3.1 Functions of NEs...........................................................................................................................14-3 14.3.2 System Interior Processing............................................................................................................14-3 14.4 Service Flows ..........................................................................................................................................14-5 14.4.1 QoR Mode.....................................................................................................................................14-5 14.4.2 OR Mode.......................................................................................................................................14-6 14.4.3 AcQ Mode .....................................................................................................................................14-7 14.5 Data Configuration ..................................................................................................................................14-9 14.5.1 Data Configuration on the MSOFTX3000 ....................................................................................14-9

x

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

.2 Running Status of License............................................................................................................................................15-3 15.15-7 15................................................................16-3 16..........................................2..............5......1 Working Principle of License ....1 LOD LICENSE (Loading a License) ...........15-3 15......................................6 Data Configuration .........4.......................................................................................................16-2 16......................3..............................16-1 16....................9........................................5.....1 Function Code ......3 Data Configuration Examples ...............16-2 16..............3 Benefits...........................................5.......................................................3.......................9 Reference...........................................................................16-2 16.................HUAWEI MSOFTX3000 Feature Description Contents 14..1 Classification of Call Model.15-2 15..................................................................................................3 Invalidation of License......................................................................................1..........................9 Service Interaction.................................................................................................................................................................................................................................14-15 14...15-10 15..........2 Data Configuration on the UMG8900 ....................................................................................................2 Application Scope ....................................16-2 16...............14-15 14.16-7 Issue 02 (2007-02-15) Huawei Technologies Proprietary xi .......1 Application ................................4...........................................3 LST LICENSE (Listing a License) ...2 ROL LICENSE (Rolling Back a License)................................................................................................................................................4 DSP ESN (Displaying the System ESN) .................1 Service Description ...................................................15-2 15...6.............2.....................................3..........................................................................2 To Mobile Subscribers.....................................................................................................................15-3 15..16-6 16...............................................2 Working Principle...................16-4 16.......................................16-5 16....................................5.............................................................................................15-9 15.4 Alerting Mechanism of License...................2 Data Configuration Example................................................................................................................................................................................................................................7 Charging and CDR .....................................................15-3 15............................................................................15-10 16 License Feature ..................................................................................................................2............................................................2 Processing Flow ........................3 Operation and Maintenance of License ............................................................................3....15-2 15.1 To Carriers................................................................................................................................................................................3 Requirements for Hardware ........15-2 15....1 Service Description ...................................................................................................................8 Service Interaction.............................................................3...................4 Availability ...............................................................................................15-1 15..........................................6 Service Management .......................................................................................................................................................9..........................................................................14-16 14.........14-16 14............................6........7 Service Management .....................................................................14-9 14............1 Protocols and Specifications ......................................15-2 15..16-2 16................16-3 16..2 Working Principle...........................................................................................................2 Requirements for Software..........................................................................................................................1......................................................................................................15-2 15..................................................1 Configuring Data at the MSOFTX3000 Side .........14-16 15 IP Fax Feature.......................................................14-16 14................................................................................................................5 Service Flow...15-3 15.............................................................................................................................15-7 15....................................................................15-10 15.............................................................................2..................................................16-4 16.15-2 15....................................................................16-2 16..........3....2 Acronyms and Abbreviations .................................8 Charging and CDR .............................14-9 14........................................4...........

.....4 System Specifications..................................................................16-20 16.........17-4 17.........................16-12 16...............................................16-10 16......................16-21 17 NE User Dynamic Monitoring Feature ......................................................................5.......................17-4 17..2 Requirements for License............3 Working Principle...................17-4 17........................................................................................6 Reference..............4 License Upgrading ...........................1..3...........16-19 16.............................................3.3...................................................................2 Reporting Flow of User Operation ..................17-1 17.....................................................4 Service Flow..........................................................................16-20 16..............4 License Control Items............................................................17-7 17.6 DSP LICENSE (Display Running License File Status) ..................4....................3...........3...............................................17-6 17................ 16-11 16...1...........3...........5.............................................3 Disconnection Flow of User Operation ....................................................................17-7 xii Huawei Technologies Proprietary Issue 02 (2007-02-15) ......................................5 Function Maintenance .......2 Availability ................................................7 Application Limitations..............................................................................................................................................................Contents HUAWEI MSOFTX3000 Feature Description 16..........................1..2 Acornyms and Abbreviations ......4 Others ................................................................................................5 Benefits ......16-17 16............................................................................................................................3 Applicable Versions..................................................................................................................2........17-5 17...............4.................................................................................................................................................................................1 Requirements for NEs ...........................5................4........................................................................................2 Resource Control Items ...............................................2............................................................................1 Overview ....................................................................2.............................................................16-9 16...............................................2 License Invalidation and Prevention .....................................................16-12 16........................................................................................5 Other Precautions .............................................................................16-17 16.....2......................................17-3 17......................................................17-4 17............................................17-6 17...........7 DMP LICENSE (Dumping License File)........................................17-5 17.........17-6 17.........................17-5 17................................................................................5 Effects of BAM Operations on License ..........3 External Interfaces......1 Protocols and Specifications .............................................................................................................................................................................4.......................................17-5 17.................16-21 16................................1.........17-2 17.........17-3 17.................................................1......................................................................................4.................16-17 16..........................1 License Checks...........................17-7 17................1 Monitoring Flow of Online User.............5........3 Standard Compliance ...........................................................17-2 17...........................6..6..16-15 16..................................................................................................................................................................................................17-6 17..............................................................................5 STR LICCRC (Starting CRC Check of License) ............................9 DLD LICENSE (Downloading License File from FTP Server)........................................3 License Alarms.............................................................................................................3...1 Function Code ........................16-21 16............................................................................................................................1 Functions of NEs.....................................................17-6 17...........................16-9 16.........1...1 Function Description ........................6 Application Scenario ..........................5...............17-2 17..........................1 Control Items.17-5 17...........................................2 Definition ..........................................................................................................................................................5...................1...............................................8 ULD LICENSE (Uploading License File to FTP Server) ......17-4 17...................3................................................................................................2 Internal Processing of the System ...................16-12 16.................

...........................................................................................................3 Working Principle..................2 CDR of the SMMT.................................... 18-11 18......................................2 Internal Processing ...........11 FAQ .................18-3 18.9 Service Interaction.......................................................................................................18-3 18.................................................................................................................................8................................8........1....7 Charging and Charging Data Record (CDR) .................................................................................1 Call Service .......................................17-12 18 SMS Notification for Call Failure Feature .....1 Functions of Each NE............................................18-6 18............................... 17-11 17.......................................................................................................................................18-14 18....................3 Charging ............................................................................6...................18-14 Issue 02 (2007-02-15) Huawei Technologies Proprietary xiii ..................................................................................................................3. and Abbreviations......18-6 18...............................................................18-13 18........................................................................................................2.........................9 Reference..............................................................5..................8............................................................................................7 Charging and CDR .............................2 Maintenance Operations................ 17-11 17.................................................................................................................................................18-7 18............................18-3 18.................5.8......................3 Applicable Versions.....................18-2 18......18-1 18........................................................................18-2 18......18-13 18............................................................18-3 18...................................................................................................................................................................2............3 Benefits ..................8 Service Interaction.......................................................... 17-11 17........................................................4 Voice Mailbox Service ............18-13 18........18-13 18...........................................18-2 18..............................................................................HUAWEI MSOFTX3000 Feature Description Contents 17........2 Availability ................................................. 17-11 17................................18-10 18.......................3 Processing Flow After Service Triggering......................................2 Requirements for License......4 Service Flow......................................................................................18-2 18....................18-13 18............................................................17-12 17..............................................2 Definition .....................................................................................................................................................................................18-3 18..........................................6 Service Management .................................................18-13 18.............1 Prerequisites for Service Triggering....................................................................................................................1 Service Description ..................................................................................................10 References ......................................................................18-8 18..........................................3.............1 Standards and Specifications..............6.............................................................................................................1 CDR of the SMMO ..............................................................................2 Data Configuration Sample ..........................................................................3 Call Forwarding Service....18-4 18..........18-12 18..............1 Operations by Carriers....................................................................................7....................................................4..............8 Performance Measurement ...1........................1 Function Code ..............................18-13 18........................2 Glossary.............18-10 18........6 Service Management ..................... Acronyms.....................................................................................................................................................................18-3 18.....18-13 18......................................5 Data Configuration .......5...........................2 Operations by Subscribers.....................................................................2 Service Triggering Point...................7................................1 Requirements for NEs ........18-13 18..........................................................................................................................................................10.................................4.................................................................................2 SM Service .................................................................10.....................................................................1 Data Configuration on the MSOFTX3000 ...........18-10 18..................4.1......2....17-12 17...................17-7 17....................7.................................................................................................................................17-12 17................................................

...............Contents HUAWEI MSOFTX3000 Feature Description 18........20-2 20...................................................................4.......................................................................................................................4 Patch Operation Flow .........................20-3 20...........20-2 20...................................2 Availability ..................18-14 19 Summer Time Feature of Wireless Time Zone ...............................19-8 19................2 License Support.................................................................2 Data Configuration at the UMG8900 Side .........9...............19-3 19........1 Data Configuration at the MSOFTX3000 ....................1 Requirements for NEs ....19-8 19................19-2 19............................9 Reference..............................................19-3 19...........................................................20-12 20.............21-1 Huawei Technologies Proprietary xiv Issue 02 (2007-02-15) ....................................................................................19-6 19....................................5...........................19-3 19......................20-6 20.....................................20-2 20..............................1....2 Definition ............................................................................................................................................................................20-3 20..........................19-7 19........................18-14 18..............................3 Benefits ................1......................1......................................................................2.......................8 Service Interaction.....................4..............1...2.................................................5 Data Configuration .......19-4 19.................7..19-8 20 Version Software Management Feature ..................................6.....................20-2 20........6.........................................................................................................1 Protocols and Specifications .........................5 Charging and CDR ....................................1 Function Code .....................................................................6 Service Management ....................................................................................................................................................................................................................................................................20-1 20..............1 Uploading Patch to The M2000 Server ...............3 Benefits ....................................................................................2 Acronyms and Abbreviations ........7 Reference..........................................................................................3 Applicable Versions...............................20-10 20....................................................19-5 19..........................................................2............................................2 Requirement for License ......................19-3 19..............6 Service Interaction......................................................................................................................................................................................................1 Feature Description ..........19-8 19..........................................................................................................2 Example...................................................................................................................................................1.......5.......20-9 20...............................................................................................................................20-12 20........................................................................................................19-3 19............2 Operating Patch ........................................2 Availability .....20-6 20..20-8 20...............................................19-2 19......20-8 20....................................................2.................................................................................19-1 19...............................................................................................................................................................................................................3 Applicable Version .......20-2 20........................1 Function Code ..................3 Working Principle..........................................................................................................20-4 20......................................9............................................................................................................................................................................7 Charging and CDR ..............................................................................................2 Definition ...................................................1 Protocols and Specifications .2..............20-12 21 Configuration Rollback Feature..........................................19-5 19......................................................................7...........................................................................................................................................................1 Requirement for NEs....1 Service Description ............................................................................................................2...............................................19-2 19...........................................................3 Working Principle...........................................................2 Aronyms and Abbreviations .............................................................................................................................................................20-2 20.........................................................................................................1........4 Data Configuration ....................................1 Data Configuration for the MSOFTX3000 .20-3 20................................................

...................................................6.........21-7 21.....................22-2 22..............................................................................................................................................................21-27 22 CAMEL4 Service .......6.......................21-6 21....................................................2 Definition .........................................................................................................................................................................................................................................1 Basic Principle...................................................22-4 22..........................................21-2 21.........3 System Specifications........................................................................1 Function Code ...............3 Activation and Forcible Activation Commands...................1..............................3 Applicable Versions...............................................................................................................................................................................................22-4 22..21-3 21..........................................................21-3 21.....4 Rollback and Forcible Rollback Commands ................3 Configuration Steps...............................................................................................21-13 21............................................5 Application Scenario .........................................21-14 21....................21-12 21.....................................................................................................................22-5 Issue 02 (2007-02-15) Huawei Technologies Proprietary xv .........21-3 21............................................6......................1 Service Description ...................2.............22-4 22..........................4 Data Configuration on the UMG8900 Side........21-13 21..1...............1 Rollback Commands .................................................................22-2 22................................................3...........................................................21-3 21.................................................................................................................................................................................................................21-17 21............................... 21-11 21...8 Service Interaction.....................................................2......22-5 22.......................22-4 22.............................................................6 Service Management .................2...............................1.........................................2 Configuration Preparations.......................................21-9 21.................22-4 22.......................................................................................HUAWEI MSOFTX3000 Feature Description Contents 21.................1 Requirements for NEs ....................................................................................................................21-21 21....21-2 21..................................................1.................7 Charging and CDR ....1 Function Code ..................................................................................1 Requirements for NEs ...................................................................................................................................................................1...................21-27 21...2.........................................2 Availability ...................................................2 Availability .........5...........................................3 Benefits ...............................1 Service Description ..........................................6..22-1 22.............................3 Applicable Versions.................................................1...........................................................1 Data Configuration on the MSOFTX3000 Side ...............21-4 21............................................................................2 Requirements for License.............................................6...3...............................6........22-5 22............................................................................................................................1.......5 Cancellation and Confirmation Commands ......................21-3 21...............................................................................................22-2 22.........................................5...1.........................6 Application Limitations......................................................................................................................................................21-3 21..............................2 Definition ..................................2 Requirement for License ...............2.......................22-4 22.........................3 Working Principle...............6 Query Commands.....................21-9 21..........................................................................2 Synchronization and Forcible Synchronization Commands.....................5........................................3 Validity Check .............................................................................................2................................21-23 21..................................21-13 21...............5 Data Configuration ......4 Others ............................................................................................................................4 Service Flow.....................................21-2 21..........1....................................................................................21-27 21.....................................................................2...3.4 Benefits .....21-19 21..............................................................................5..................................9 Reference.......................................................2 State Transition.................................................................................................21-3 21...............................

................................................1..............................23-4 23..2 Availability .......................................................................23-4 23..............3 External Interfaces....3............3...............................7 Charging and CDR ....................................................................11 FAQ ...............................................................................................................................................................................................................................22-21 22..................................................................23-3 23..................................23-1 23....................................23-4 23......5.10..............................23-4 23........................................3....4 Data Configuration Examples ..........................................................22-21 22................................................................................................2 Internal Processing of the System ......1 Functions of the NEs ....23-5 23....................................................................................................22-13 22.........22-17 22.................3.........................................................................2............................................22-23 23 IMSI-Based Announcement..2...23-5 xvi Huawei Technologies Proprietary Issue 02 (2007-02-15) .........................4..5................2 Glossary............................................5 Data Configuration ........................................................22-19 22.........................22-18 22.................1 Functions of NEs.............22-10 22...........................................................................2 Restriction Between Multiple CPH Operations in the CAMEL4 Service ....................2..............................23-4 23...................................................................................................................................................1.....2 Definition .......................................22-19 22...................................................................................................................................................................................................................................3 CAMEL4 Simultaneous Ringing ................................23-5 23....9 Service Interaction.....................3..........4 Others .................................................................................................................................................................................................4....23-3 23..............................22-13 22........23-3 23..........................22-6 22...............1 Specifications .......................................22-6 22.......10 Reference............. Acronyms and Abbreviation .............23-5 23............10.............23-3 23.........1...........................................................22-13 22................................................4 Benefits .....3 Applicable Versions.......................1.......22-6 22...............................................................22-19 22...........................................23-4 23............................................................................................................23-3 23.............................22-18 22....................3 Working Principle...................................................5.................1...22-13 22............................................................................5..........................................................................................................................................................................................................................................................5 Application Scenario .........................................................................................................8.............................1....................................................................2.................................................................6 Application Limitations....22-9 22........................................................................................................3 Data Configuration at the UMG8900 Side ..................................................................................6 Service Management ..............................1 Specifications .4....................................2 Data Configuration at the MSOFTX3000 Side .......1 Overview ...................22-7 22.................................................................................................8 Performance Measurement ..........................................................................22-18 22........................................9.........2 CAMEL4 IN RBT Service ................2 Internal Processing of the System ......................................................................3 System Specifications......1 Restriction Between the Supplementary Services ...............22-6 22.......................................................8...........................................................................4 Service Flow...................................................................................................Contents HUAWEI MSOFTX3000 Feature Description 22..............................................................................................................................1 Conference Call......................22-21 22...............................................................22-20 22........................22-6 22..............22-14 22........................1 Function Code ....9................................................2 Implementation Principle ............................1 Service Description .........................................................................................................................1 Requirements for NEs .................................2 Requirements for License...............................................................3 Working Principle...........

...........................1..............3......................4 Data Configuration Examples ..............................................11........................................................................5..............24-8 24........3 Data Configuration at the UMG8900 Side ...5.24-2 24.....................24-2 24..................................................................................................................................................................................5 Data Configuration ..................2...........................2............................2 Availability .......................................................................................................7 Charging and CDR ...............23-13 23...................................................................................................................................23-8 23...................................................24-2 24.....1 Functions Provided by NEs........................................................................................................................................................................................................................................................................4 Benefits ..............2 Data Configuration at the MSOFTX3000 Side ......24-2 24....................................................................................................2....................11................................................................................1 Specifications .......5................................................................3 Working Principle......................................................4 Service Flow.........................................2............10..........5.....................................................................................................................................HUAWEI MSOFTX3000 Feature Description Contents 23....1 Service Description .... 24-11 Issue 02 (2007-02-15) Huawei Technologies Proprietary xvii .............................................................................24-7 24............10 Reference.....................................................1 Requirements for NEs ...................23-13 23..............................................................................................5..............................................................24-5 24.....................4 Others .24-3 24.......................24-8 24.............................24-4 24...............................2 Question 2...............................................23-7 23....23-13 23......................................1.....10......8 Performance Measurement ................................3...........................23-13 23....................................23-7 23....................................................................................................1 Overview ....23-13 23..................................................................................................2 Definition ......3 External Interfaces..2 Acronyms and Abbreviations ........................................................24-4 24............................................................................................................................................5 Application Scenario ............23-14 24 IP over E1 ..........2 Requirements for License....5 Data Configuration ............................5......................................................................................1......................................................................24-3 24....................................24-4 24.............24-4 24.....23-8 23.........................................1 Overview of Data Configuration ...................4 Service Flow..............................................................................................23-14 23..................................11 FAQ ..24-10 24...........................................3 System Specifications.........................................................................................1 Function Code ....................................................11.....................................................................................................................2 Internal Processing Flow of the System .......................................................................3 Question 3....23-9 23...................................................23-10 23................................23-9 23.........3 External Interfaces...................................................................................23-13 23.........................................1.............................................23-13 23.....................1.......................24-4 24.......1 Question 1............................2 Cross-MGW Call Flow Based on IP over E1 .................................5 Querying Tables of the IMSI-Based Announcement Service ........................................................................................................................................................23-8 23........................................3 Applicable Versions.....23-13 23......................................................................................1 Inter-Office Call Flow Based on IP over E1.................................................................................................................................23-13 23........................................24-4 24............24-2 24.....................................................................................................................................................9 Interactions with Other Services........ 24-11 24.......1.........................................................3.......................................24-4 24.....................4........4............................................6 Service Management ...................................................................3............................................................................................................................24-1 24........................................................6 Application Limitations...........................

........................................25-15 25.......................................1.............24-20 24............................................5...........................................1 Function Code ...............................5............................................................3 System Specifications...................................6 Charging and CDR ................................8 Performance Measurement .............................................................................................................1 Index Description ............................................................................24-19 24.............25-2 25......1 IP QoS Flow Control in Inter-Office Office Direction Mode for Outgoing Calls ................................................................................2 Data Configuration at the MSOFTX3000 Side ..........................................................25-8 25........................................................................3....2 Availability .............................6 Application Limitations................4.....................2 Data Configuration at the MSOFTX3000 Side ..................................................25-18 25............................25-8 25............25-18 25......................................3 External Interfaces......................................4............................25-3 25.......5 Application Scenario ..............................................................4 Data Configuration Examples ..........................................................................3 IP QoS Flow Control in Gateway Pair Mode for Intra-Office Calls.....................................................................................................................................................................................3 Working Principle...........................1.............................25-2 25.......1 Functions of NEs..............1...............2.....................................................................................2 Definition .........................7 Performance Measurement ................................................................................................................................3 Data Configuration at the UMG8900 Side ...............1 Specifications ..2.......Contents HUAWEI MSOFTX3000 Feature Description 24........................................... 25-11 25......10............... and Abbreviations.2 IP QoS Flow Control in Inter-Office Gateway Pair Mode for Outgoing Calls........................25-19 xviii Huawei Technologies Proprietary Issue 02 (2007-02-15) ......................................................25-2 25...............2 Glossary.......................24-17 24...........................................................24-13 24....25-9 25..4 Data Configuration Example..........24-19 24...............3....25-4 25........................................3 Data Configuration at the UMG8900 Side ...................24-20 24...............................2 Requirements for License....................................24-20 24.......................................................................7.....................2 Internal Processing of the System .......................................5 Data Configuration .............25-18 25.................................................................. 25-11 25.......................................1 Feature Description ......................................................................6 Service Management ...........4 Service Flow........................................................................3 Applicable Versions.............25-18 25............................................. Acronyms.....................................................................................3.................1 Overview .........................................................................................................................5.........................7 Charging and CDR .....................................................25-10 25.....25-4 25........25-9 25................................................................................................................1.............................................................................................................................................................10...25-16 25...................5......................6 Operations by Mobile Subscribers ....25-4 25........1..........................25-5 25.........25-12 25...................................................25-2 25..........................................................1 Requirements for NEs ........................25-4 25.....................24-20 24..................................................................................................1.......25-1 25.........25-4 25.............................................................................................................................................................2..............24-20 25 IP QoS Flow Control .................................5.........................................................................2.............................................25-3 25.................................................................................................5.................25-3 25................................................................................................................5 Operations by Carriers..............4 Benefits ..............25-3 25...................................................................................................................................................25-3 25..............................4...........5......................9 Service Interaction.........................................................................................4 Others ...10 Reference....................5............ 24-11 24.................5.....................................................................................................................................................................

............................26-10 26..................................................26-2 26..................................................................................2 Intenal System Processing........................26-18 26.......................................................1 Operations by Carriers....................3.5 Benefits ...................26-4 26................................2 Data Configuration at the MSOFTX3000 Side ........................4 Others ........1 Requirements for NEs ............................................................................................26-4 26...................................................HUAWEI MSOFTX3000 Feature Description Contents 25...........................................................1 Service Description .......................1...............6 Service Management ........................................................26-16 26......................1........................................................5..........................................................................1 Charging Principle.....................................................................................................25-19 25........................................................................26-18 26................9.....................8 Performance Measurement .................................................................25-19 25.....26-2 26..............................3 Standard Compliance ....................................................................7 Application Limitations........................................................10 FAQ ......26-2 26.....................................................26-4 26..........................2 Availability ......................................................................5 Table Query Procedure of the O-CSI SMS..............................................................................................................26-2 26...................................................26-8 26...........................................................................................................................................................................................................3 External Interfaces....1..........................7 Charging and CDR ........3 Applicable Versions................................................................................................3 Data Configuration at the HLR Side ....................................2.........................................................................................5..............................................................................26-13 26....2 Definition ....................................................................2 Acronyms and Abbreviations .........................................................26-3 26.........................................................................................26-10 26...............................5.................6.................................26-3 26......................................................6 Application Scenario .............................1.......................................................................................................................................7.................................................5 Data Configuration ........................................................................................................................2 CDR.........................................26-18 26...................................................................................................9 Service Interaction...........................26-2 26.......................................................................26-18 26......................................................................1 Functions of the NEs .....10..........3 Working Principle................................................................26-13 26..............................................................................3....................................6....................1 Standards and Specifications.......................................................................2 Requirements for License..........4 System Specifications................................26-18 26...........4 Data Configuration Example.................26-3 26............................................................................................2..........2.........................................................................1 Function Code ....26-18 26...................................................8 Service Interaction..........................................................................................................1........2...........................................9 References ..........................................................4 Service Flow...........................2 Implementation Principle .............................26-18 26..26-10 26......................................5.........................7...................................26-2 26.....7...............26-7 26.....................................................................................................................................................................................................................................26-14 26...............................................10 Reference.....9................26-4 26..................................1............25-19 25.....26-1 26...................26-2 26...............................2 Operations by Subscribers...........26-18 Issue 02 (2007-02-15) Huawei Technologies Proprietary xix .........................................................................................................26-17 26..................................................................5...................................................3....26-3 26..........................................................................................................................................1 Specifications ..........................................................1 Overview ..............................................26-3 26..1................................................25-19 25.....25-20 26 O-CSI SMS ........25-19 25.........................

......28-3 28.......................................................................27-3 27.....................................................................................................27-20 27...........27-2 27.......................................28-2 28.......................................2 Glossary..........................................................................................................27-19 27.......6 Use Restriction .................2 Internal Processing of the System ...................................................5.............................................3.........2 Function Definition ...................... and Abbreviations..................................................................27-3 27...........................1 Data Configuration at the MSOFTX3000 Side ..................3 Working Principle........2 Availability .............................3 Applicable Versions.........5 Application Limitations...................................2 Requirements for License........................27-4 27.............................4 Service Benefits........................................................................................27-9 27.....1............................9 FAQ .....................................28-2 28.....................1...........27-17 27........................................................................27-17 27.................................27-20 27.........8 Reference..................................1 Specifications .............................4 Service Flow.........1..2.............................1.................2 Availability ....................................................................................................................................................................................................................5 Data Configuration .............................7 Service Interaction....................27-3 27............................................................11 FAQ ....27-3 27.....................................................................................4 Data Configuration Example.....................................................................................................27-15 27..1...3 External Interfaces.2 Requirements for License.......3....1 Function Code ................................................................................................27-2 27................5........................................................................................3 Benefits .....................1.......................................................27-3 27..........................................................................................2......5 Application Scenario ..........................................27-2 27..................2.............................................................................3................................2.....................................................................................................................1.27-20 28 VDB Dynamic Data Backup ................Contents HUAWEI MSOFTX3000 Feature Description 26..........................27-2 27.............................................8.......26-19 27 UP Header Redundancy Data Service..................................27-1 27...........................................27-3 27...........................................................................................................1 Requirements for NEs .............................................28-4 xx Huawei Technologies Proprietary Issue 02 (2007-02-15) ...........5...........1 Function Code .....................................................27-8 27......................................................28-3 28............................... and Abbreviations...............................................................................4 Application Scenario ...........................1 Requirements for NEs ...........................................2 Data Configuration at the UMG8900 Side .......................28-2 28.........................................................................5.................10...........................................................................................................................27-17 27............................................................................27-19 27.................................................................................................... Acronyms...............................................................................................28-3 28.............1 Feature Description .........................................................................................................2 Glossary.........................27-3 27...................................................................................................................................................................1 Functions of the NEs .................6 Performance Measurement .........3 System Specification .....................................................................................................................3 Data Configuration at the HLR Side .28-3 28.....................................................................28-4 28............................................................27-15 27........................................................................................................................................................27-20 27...........2 Definition ..........................................................................................26-19 26......1............1 Service Description ..27-2 27..................................................................................................................................................................2......4 Others .................................................8.................................28-4 28............................1.............1.................................. Acronyms.....................2....................27-2 27.........28-1 28...................................................................................................................................1..................................................

...........29-10 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxi ................................6 Application Scenario ................................................2.2 Data Configuration at the MSOFTX3000 Side ..........................1 Functions of NEs...................................................................3 Working Principle..........................................................3...........................................................29-7 29. Acronyms....5.....................1................................2 Internal System Processing .......................2...................1 Functions Provided by NEs......................................................2 Glossary............................................................1...................................................................28-4 28..28-22 28...............................................................7 Charging and CDR .......................................................................................................................29-7 29.2 Requirements for License..........28-5 28......1 Service Description ............................................................................................................1 Function Code .................................................................................................................................................................................................................................28-16 28..................28-14 28.......................................................................................................................................................4 Service Flow.......................................5...................................................................................29-8 29..........................29-3 29.29-8 29............................................................................................................................................................28-14 28......................3..............1 Overview .............................................................29-6 29.................................................. and Abbreviations.......................................................3 Applicable Versions.........................................................28-8 28............................................1..............................................................................2 Processing of Aging upon Dual-Homing Switchover ..........................................................................................................................29-1 29.................................3 External Interfaces.......5.................28-14 28......................................................................................................................28-4 28...........................................28-14 28.......................................1 Overview ............................................5 Data Configuration ..................29-9 29......................................................................4...........................................................2.............................................3..........................................................5 Benefits ..1 Requirements for NEs ......................................3....5..........................................1.......................................................4 System Specifications....................................................HUAWEI MSOFTX3000 Feature Description Contents 28.........................................................29-8 29............................3 Working Principle...........................................2 System Internal Processing ...28-22 28..............................1 Subscriber Data Backup FLow.............3 Applicable Versions.......28-21 28.28-16 28...........................29-3 29.....................3 MT Flow Optimization upon Dual-Homing Switchover......................4 Service Flow............5.......................................................................................................3........................................9......................7 Application Limitations.........................................................................3 External Interfaces.......4 Example..........28-22 28..............................................29-10 29...........................1......................29-8 29........29-6 29.......29-7 29...............................................9 Reference..........................................................................................5 Data Configuration ...........8 Interaction with Other Services ................................................................................1 Specifications ...................................................................................................................4..................................................................................4 Others .................................29-6 29............................................................................................................................................................28-8 28...............................................................................................................................28-23 29 Multi-Area Network Role-Based and Domain-Based Management Feature...................................................2.........................9...............29-9 29.......4.......................................................................................................3....................3 Data Configuration at the UMG8900 Side .........................................28-8 28.......................28-15 28.........2 Availability ....................................28-4 28..................................................29-8 29.................29-8 29...................1............3 Standard Compliance ...........29-3 29.....28-22 28................2......2 Definition .6 Service Management ............................................29-7 29.............................................1...........................................

.........29-16 29............................2 Availability ....4 Data Configuration Examples .......................................................................................................................................................................11 FAQ .................................................................................5 Benefits ..................29-20 29..........................1 Function Code ..................................................................................2..................31-2 xxii Huawei Technologies Proprietary Issue 02 (2007-02-15) .......................30-4 30..............................................2 Internal Processing of the System ............................................................................................30-5 30..........................................1 Requirements for NEs ........5........................................................................30-2 30.................................2......................................4 Data Configuration Example...................................................................................................................................................................30-3 30.............1.....................................................3 Standard Compliance ...............................9 Service Interaction......................................4 Service Flow...............................................................................30-4 30............................................................................................29-19 29..............................................................................................6 Service Management ................7 Charging and CDR ........................................................................................1..........8 Performance Measurement ...................................................7 Application Limitations............3..3 Applicable Versions.........................................................................................................Contents HUAWEI MSOFTX3000 Feature Description 29....................................................5...30-9 30...........................................................................................................................................................................2.......................................................30-2 30.........30-8 30...1.............................30-5 30......................31-2 31.............30-4 30..........................5................................................................................................31-1 31................................................................................29-10 29.................................................................10 Reference..................1 Service Description ...30-1 30....30-7 30...............................................................30-3 30....30-7 30......................................................................3 Data Configuration on the MSOFTX3000 .......................................................................................1 Function Code ......................................30-8 30..............................30-2 30................................................................................................3 External Interfaces........................................................................................................1 Specifications ......................................................................................................................................6 Service Management ................................................................6 Application Scenario ..............................29-20 29.........................10................2 Definition ............................3 Working Principle.....1......................5 Data Configuration .........................................................................................30-2 30................................30-4 30.1.................................................................................................................30-9 30...............................5 Data Table Relevant to the Alarm for Malicious Short Messages ......................4 Others ...................................................................1...................30-2 30..................................................30-7 30...................................................................................................29-20 29............................................................3.....30-3 30.......................................5...........................1 Overview ...................................30-2 30.......1 Service Description ...................................2 Requirements for License...3............................................................................................7 Service Interaction...................30-3 30......................................................................2 Acronyms and Abbreviations ................................................................30-9 31 Call Simulation.....................................................................................................................................5................30-3 30............5......................1............................1......29-19 29....................................................5....................................30-2 30......1 Functions of the NEs ..............................................................................................................................................2 Data Configuration at the MSOFTX3000 Side ...................................................................3 Data Configuration at the UMG8900 Side ........2 Data Configuration on the M2000..............10....29-16 29.........................................................................................................................29-20 30 Alarm for Malicious Short Messages ..................................................................29-20 29.........5..................4 System Specifications...............2.....29-20 29.............

.....2 Availability .......3 Description of the Shortcut Menu of the Message Output Pane..................................... Acronyms........................................................................................32-1 32.......................31-3 31...........31-8 31........................................3 System Specifications.............31-2 31..........................................................................................................................31-17 31.................................................1 Specifications ............................................4 Benefits ............................................3...........32-2 32.........................................................................................1 Creating a Call Simulation Task..31-9 31............................................1...................................................................32-2 32...........................................................................................1 Selection of LAI/GCI and Circuits..........................................................................................31-5 31..................31-15 31......2 Internal Processing of the System ..................................31-17 31.............................................................................................................................................................31-5 31... 31-11 31..........................................31-5 31.................................................1...............................31-16 31..31-14 31..........................................7 Charging and CDR .......3 Applicable Versions........................5 Data Configuration ..............................2..................1.......2 Definition ..............................................................................31-17 31.1.......................10...............................2....1 Service Description ..31-5 31............................6 Application Limitations..............................8 Performance Measurement .....................................................32-3 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxiii ...........................................................1................................................................................1 Function Code ...................................................................................................................1...............................................................................................................................................................4 Benefits ..............................................................31-4 31....................................................10 Reference.........5 Operations by Carriers...............................................32-2 32.......................................32-3 32....................5............................................................................................5 Application Scenario ....................................................................................................................................................................................................................................4.............................5..........31-10 31...............................9 Service Interaction.................................................................................................1 Configuration Description......................................................................................3......................2 Requirements for License........................... and Abbreviations........................31-17 31.................................6..6 Service Management ...................................................................2 Data Configuration at the MSOFTX3000 Side ......................................2 Handling at the Trunk Side..............31-8 31................................................................................31-10 31.....................................................31-10 31........................................................................6........................................................................................31-4 31................2......................................................................................................1..........................................6............................2 Message Trace and Logs During the Call Simulation ......................................................................................................................31-17 31......31-4 31..........31-16 31.........................31-10 31............................................................................................4 File Saving ...................1..........................3 System Specifications.....................................31-18 32 Load-Based Handover ......................................................................4 Data Configuration Example..........31-8 31...... 31-11 31.....................31-17 31..............................................1 Functions of the NEs .................1..................................31-5 31.................................................................32-3 32.........1.........................................................................................1 Requirements for NEs .6 Application Limitation ............................3 Data Configuration at the UMG8900 Side .............................2 Definition ...31-5 31..........6.....................4.............................10............................................................4 Service Flow.............3 Working Principle........................................................31-10 31.......................................................................11 FAQ ...........................................6........5.....................5 Application Scenario ..........5.................................................1..HUAWEI MSOFTX3000 Feature Description Contents 31.....2 Glossary.........................................................................32-2 32.........................................

.........3 Applicable Versions.......33-2 33....................................7 Charging and CDR ........................................................................................................................6 Service Management .........................................................32-13 32.....................4................................................3 Benefits ..................................................................32-9 32.........................4..........2 Inter-MSC Load-Based Handover From 3G to 2G System.....32-16 32.....................................................................1 Requirements for NEs .......2.................................................................................................................................................32-17 33 Union Subscriber Trace .....................................................................3 Data Configuration at the UMG8900 Side .......32-16 32........6...............1...........................................................................6 Others ..........2 Acronyms and Abbreviations .........................................................................4 Service Flow..........33-3 33..........4..............................................................................32-7 32..............11 FAQ ...........1 Service Description .....6.......10.................................................2 Definition ..............................................................................................Contents HUAWEI MSOFTX3000 Feature Description 32........33-2 33.......................................2 Availability .....................................................6 Inter-MSC Load-Based Handover in 2G System .............3 External Interface ....................................4 Inter-MSC Load-Based Handover From 2G to 3G System.......32-4 32.....................................32-12 32............................................................................................1 Overview ..........................................32-4 32........2 Data Configuration at the MSOFTX3000 Side ..............3.............................................1 Functions of the NEs ....................................................10 Reference..........................................................32-7 32.............................................................................................................................................................................33-1 33............................................................................................4 Others ................................................................2 Requirements for License.....................................................................................................................................2 Internal Processing of the System ...........5......................................................33-3 33...............5..32-3 32................................32-4 32...................................................3 Intra-MSC Load-Based Handover From 2G to 3G System.........................................................................................................................................................................................4..................1................................................................32-16 32......................................8 Performance Measurement ..............2 Availability .......5 Data Configuration .........1 Intra-MSC Load-Based Handover From 3G to 2G System...................................................................................................................................... 32-11 32...................................................1 Specifications ...............5 Intra-MSC Load-Based Handover in 2G System .........................................................................32-3 32.................................1...5.....................................................................................................................................................32-17 32.................................3......................................2 Operations by Subscribers..........................................................32-4 32...32-12 32......................................5 Application Limitation ..........................................................32-13 32......32-6 32.......................................1.....................32-12 32...............4 Data Configuration Example.......................................................................................................32-7 32...................................4...................32-16 32........................................32-4 32...1.....................................................................32-9 32...............................................33-4 xxiv Huawei Technologies Proprietary Issue 02 (2007-02-15) .......9 Service Interaction...........................................................................................................................................1 Operations by Carriers....................5...........1 Function Code ..............................................................32-16 32....2.........................................5 Data Tables Related to Load-Based Handover ................................2...............................................................................................3 Working Principle...............10.................2....................32-15 32.....32-15 32...............................................................................33-3 33................................................33-3 33..................................32-10 32.....................4...........................................................................32-16 32............4 Application Scenario ............................5.............................................3......................32-14 32................................................................1.............32-8 32............................33-2 33..........

.......1 Functions of NEs..............................2................................................................4 Benefits .................33-10 33....33-14 33............................ 33-11 33.........................................4.................4 Service Flow..........................................................................4...................2 Availability ...............................6.............................33-14 33...................................................9 Service Interaction..............................33-10 33.....................4............................................34-2 34.......33-9 33......34-3 34.........................2 Internal Processing of the System ..................................................... 33-11 33........... 33-11 33.......................33-4 33.....................................................................................34-3 34.................................................................................1......................... Acronyms and Abbreviations.......4..........4........................................34-3 34.................................................3 Data Configuration at the HLR Side .............................................................5 Related Tables ..................... 33-11 33............5..............3 Trace Flow of Deactivation Trace Sent by the HLR...................34-2 34.........................3......................................................................................1 Overview ...........................3................2 Trace Flow of Activation Message Sent by the HLR ......................................................................................4 Data Configuration Examples .................................................................33-14 33.................................................. 33-11 33............................................................8 Performance Management...........33-5 33...............................................................33-4 33..............10 Reference.............................................................................................................1...................1.........................33-14 34 Service Restriction by Cell ...........................33-4 33.............34-3 34.....................................................33-7 33..............................................4............................3 External Interface .........................33-13 33.................33-13 33.......................5..............................5....................................................................1..................................9 Trace Flow of Power-Off and Trace File Generated......2 Data Configuration at the MSOFTX3000 Side ....................................................................................................................................................................................1 Function Code .............................................................................................1 Specification........................................7 Trace Flow of the Terminated Short Message ...................33-4 33........2...............................................................................................................................................................................................................3 System Specifications........................................................................................................................................................................................5 Trace Flow of the Termination Call................................1 Requirements for NEs .........................6 Service Management ............................................6 Application Limitations..............................................................33-6 33.........33-12 33...............3 Applicable Version .......................................10...................................6 Trace Flow of the Originated Short Message ............................4 Trace Flow of the Initiation Call ....................33-8 33....2 Operations by Subscribers.....................................................1 Operation by Carriers ...........3 Working Principle.5 Data Configuration ............5.............................................33-13 33.......................................................................................33-12 33..............................................33-8 33...................33-5 33......................................................................6................HUAWEI MSOFTX3000 Feature Description Contents 33..................34-2 34.................5 Application Scenario ...............................................1.........................................................33-4 33.............................................................................1 Service Description ............................................................................4...................33-5 33..............5.....1 Trace Flow of Activation Message Received from the HLR During Location Update/Data Recovery .........33-5 33...................................................................................33-9 33.........................................................................................8 Trace Flow of Power-On/Location Update.............................................................................................................................2 Requirements for License.........2 Glossary.......................10.................................................34-4 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxv ..............................................2...........33-12 33.............................4.7 Charging and CDR .............................................................................4................................................2 Definition ................................................................3.......................................................................1................................................................................................................34-1 34...........

.................................................................................34-25 34...1................2........35-4 35.............................................................34-24 34..............................................34-24 34..............................3..............34-24 34..................................................................1 Index Description ..........................................2..........................................35-3 35........................................................................................................2....9 Service Interaction...............................................................................................................1 Overview ..........................................................................35-4 xxvi Huawei Technologies Proprietary Issue 02 (2007-02-15) ....2.........................................35-4 35......3.34-17 34..................................................1 Requirements for NEs ..............34-25 34..........1 Service Description ..................8.......................................................................3 Terminated Service Message Flow...........................10.............................3 Data Configuration Examples ............3 Applicable Version ............................................6 Service Management ............................................34-24 34....................................................................34-4 34...35-3 35.....3..........................................................................................................................................................................................................34-26 35 Dialing Test on Designated TDM Circuit......................................................................................................................................................34-8 34...........3...1 Functions of the NEs ....................................................................................................................................................34-24 34........................1 Functions of NEs.....34-25 34..........................................................................................2..................................................................................................9.....7 Charging and CDR .....................................2 Requirement for License ....Contents HUAWEI MSOFTX3000 Feature Description 34..........................35-3 35..............................2...................................................1 Specifications ......................34-24 34...............34-6 34.........................................................................................................35-2 35.2 Acronyms and Abbreviations ...........2 Definition ...35-1 35...................................4......................2.34-25 34............................3 Benefits ........................................................10..................1 Requirement for NEs...................35-2 35............................................................................................................................................................................................................................................................34-6 34................................35-3 35.................................................2 Implementation Principle ....34-4 34..............................................................35-3 35..................................................................................34-9 34.........................................................................................1 Enhanced Roaming Restriction and ZC Roaming Restriction .........35-3 35........2 Originated Service Message Flow.........................................................................34-5 34.8.................................................................5 Application Limitations.....................2 Internal Processing of the System .........34-4 34...............................................................................................................................4...............................................5..................................................................................................5.............................35-2 35..........................................1 Function Code ......3 Working Principle...........................1.............10 Reference..............................................................................................................2 Requirements for License..........1 Location Update Message Flow ..............34-4 34.............................................................................35-3 35......................................................34-4 34...........3 Applicable Versions........................................34-4 34......................................2 Service Implementation........4 Service Flow...................................................................................................................................................................................34-9 34......................................................4 Application Scenario .............................................................................................................................................................................2 Data Configuration at the MSOFTX3000 Side ..........................2 Availability ...........................................5.............................................34-4 34.......................34-5 34................................1...............................................................11 FAQ ......................................................1...................3.....................................3 External Interfaces....................................................................1..............................................................8 Performance Measurement ......5 Data Configuration ...........4 Others .............................................................4.......3 Working Principle...........................34-9 34..........

.....................................................................36-3 36.....................36-13 36...............................35-12 36 IN Service Performance Measurement Enhancement ....3................................................................36-4 36.........................................................................35-12 35............................................35-9 35..................................36-1 36...................................2.................................................................................5 Data Configuration ..................................................................36-9 36.................35-9 35..............36-13 36.........................36-5 36......4 Data Configuration Examples ............35-9 35............................................4.......................3............10 FAQ ...............................................................5...........................................................................................................................................................................4 Denefits .................................................................................................................................................35-5 35...........................................................36-4 36............1 Functions of NEs................................1.......36-3 36...............2 Dialing Test on the Designated TDM Circuit for the Intra-Office Call ..................................................................................................................................9.....................2 Acronyms and Abbreviations ...........................5..............................6 Application Limitations....................3 Traffic for Fixed User Calling WIN User..............2......................1...............................................................................................................3 Working Principle......................................2..........2 Internal Processing of the System .....................................................................................1 Requirements for NEs ...........................................................................................................................35-12 35................................................................................1..............3 Applicable Versions..........................................4...........................................1 Function Code ...........................6 Charging and CDR ..............35-12 35.........35-5 35........................1...................................................4...............4......................36-4 36.....................................................................5........................................35-10 35..........................36-8 36..........5........... 36-11 36.....HUAWEI MSOFTX3000 Feature Description Contents 35..36-4 36......................4 Others ....... 35-11 35......................................35-7 35...............................36-8 36.............................................................................................................3 System Specifications.............................................................................................36-3 36...................................................................................................................................2 Requirement for License .............36-14 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxvii .........................................................................................3 Data Configuration at the UMG8900 Side ....................4..........................36-5 36................1..................................1 Description ............................................9 Reference.......................................................................................................36-12 36....................................................................................................................1 Service Description ...............................5..............................2 Availability .......2 Data Configuration at the MSOFTX3000 Side .....................................................4 Service Flow.................................35-12 35......35-10 35...............9..............................................................5...3 External Interfaces.................3 Dialing Test on the Designated TDM Circuit for the Incoming Call.................................................35-9 35.......................36-4 36...7 Performance Measurement ........................5 Application Scenrio .........................1 Specifications ................36-5 36..............................................................................................................................................................2 Traffic for WIN User Calling Other MSC User ..........3....2 Data Configuration at the MSOFTX3000 Side ..........36-8 36.........................................................................................................4 Traffic for Other MSC User Calling WIN User ...........4..............2............1..................................................4 Service Flow..............................................................8 Service Interaction...........................................................4................35-12 35................................1 Traffic for WIN User Calling Fixed User.....................................36-5 36..................................................................36-3 36.......................................................................5 Data Configuration ..................................................................36-5 36..............1 Dialing Test on the Designated TDM Circuit for the Trunk Outgoing Call ..........................................36-5 36........................................1 Configuration Description...2 Definition ........................................................

................10 Reference................................37-5 37............................................................36-20 36...3 External Interfaces..................................1 Requirements for NEs ........10..............2 Data Configuration at the MSOFTX3000 ...........................................37-7 37.........1...................2 Internal Processing of the System ........36-18 36...............................................................................................36-20 36................37-1 37....................................................................................................................................................................................... Acronyms...1.........37-3 37....................................................................................1 Configuration Description.......................37-5 37.........................................................................................37-3 37..............................37-4 37..........................1 Service Description .......................................3 Data Configuration Example...................................................................................2 Operations by Carriers..........36-14 36....................................................................2 Availability ........................3..........................................................................10............................................36-18 36.............................4 Table Query Flow of ADD ...................37-10 37........................................................................................36-19 36.37-7 37.......................................................6................................9 Service Interaction....................................................................................................................1.............5 Benefits ........................................................................2...........2 Requirements for License...........1 Function Code ............................................................................................................................................................................................................................5 Data Configuration .................................6 Service Management .......................................................................................................................................7 Application Limitations........................................................11 FAQ ..37-2 37....8..................................37-2 37....................3 Working Principle..............5..........................................................37-9 37........7 Charging and CDR ..37-3 37...................................................36-20 36.......................................3 Operations by Subscribers.............6..............6 Application Scenario .......................................................................................36-19 36...................Contents HUAWEI MSOFTX3000 Feature Description 36............................................................................................................................................37-4 37...............................................................................5.............................................4 Other...................................................................................37-4 37...............................1 Specification Descriprion ......................36-18 36.................................................................................................................1 Functions of the NEs ..............................................................................................5....................................3.........................................36-20 37 Automatic Device Detection ............36-18 36.............................................2....... 37-11 37..................................................6........................37-3 37....................................................1.........................................2 Implementation Principle .........................................1.........................................................................5.....................................................6.............................................1...................2..........2 Glossary.....................................37-8 37...........................................................................................................3 Data Configuration Examples ...6..........................37-2 37..............................................................................37-10 37.....2.........................6 Service Management .....1 Operations by Carriers...........................................................................................................36-20 36........................1......................37-3 37............................................................................................................................37-2 37..37-3 37.........................................................2 Operations by Subscribers.................36-19 36..................................... and Abbreviations............................................................3 Applicable Versions.............................. 37-11 xxviii Huawei Technologies Proprietary Issue 02 (2007-02-15) .............................................................8.....37-7 37...............1 Overview ....................................................37-2 37.....................................................1 Specifications ........4 Service Flow...37-2 37...................................................3 Standard Compliance ......................2 Definition ..........................................................................................................................5..........................................8 Performance Measurement ...............37-3 37....................................................................................................................................................3.4 System Specifications.................

...............38-3 38...........................................................................................................8 FAQ ..1...............................................................................1 Problem Description.............8........................4 Others .............................................................................................................................................................................................................................................38-4 38.............................................5......................................................................................................................1...........................................................2.........................3 Configuration on the UMG8900 Side .........................................38-7 38............38-6 38.............................................................................38-8 38........................................................................................................38-3 38..2 Availability ...........................................38-5 38..............10..........................................3 Standard Compliance ..........................38-3 38......................................................................................10 Reference..................................................................................................37-12 37......................................................................................................................................................................................38-9 38.......................................................38-12 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxix .................38-4 38........................................................................................38-6 38.....4 System Specifications.....................1 Service Description ..............................................................................5 Benefits ..........................38-2 38..................8.2 Definition .................5 Data Configuration ..................................................................38-2 38..............................................38-2 38.................... 37-11 37...............................................1...38-12 38.............................. 38-11 38.....................................................................................................................................................................................................................................................1 Function Code ...........................................................................................................................................................................1 Operations by Carriers...........................................................37-12 37......1 Specifications .....................................................2 Configuration at the MSOFTX3000 Side.................................. 38-11 38.38-5 38..........................................................................................2 Operations by Subscribers........................9 Service Interaction.............4 Service Flow..................................1 Specifications ..................................................................................2...........................................................................1...38-4 38..........1....................5.........8..............1 Requirements for NEs ..................................37-12 38 Noise Suppression ..................38-1 38...........................................38-4 38.....................................................2 Acronyms and Abbreviations .......................................6..37-12 37....................7 Reference............6 Table Query Flow of Noise Suppression Feature .....5....................38-12 38...........................3....................................5...............................................4 Data Configuration Examples ...................................................................................1 Overview .................................................................2..2 Internal Processing .......38-4 38..............38-2 38...................................................................................................................................................................................................................................6................................................3.......................... 38-11 38.......................................................5......................................................................................................................................................3 Supporting Versions ......................................................................5........6 Service Management .....................................38-12 38...................................................................HUAWEI MSOFTX3000 Feature Description Contents 37.............3 Working Principle................................................................ 37-11 37.....7..........................................................................7 Application Limitations..............................38-4 38...........38-4 38............................................................................................................... 37-11 37.....................8 Performance Measurement ..................................................2 Requirements for License.......................38-5 38...........2............................................................6 Application Scenario ......3 External Interfaces......1........................38-10 38.38-3 38.......................7 Charging and CDR ................................3 Method .................................................................................................. 38-11 38......1..........38-7 38...7............5 Table Query Flow of Noise Suppression Feature ................................................1 Functions of NEs............................................3.............2 Cause of the Problem ................................................

.............40-4 40.......1 Service Description .......................3 Supporting Versions .......1 Requirements for NEs .................40-3 40.............................................2 Availability .............................2 Requirements for License.......3 Supporting Versions ......5 Benefits ..........................................................................................4 Others ................................................................................................................1.1 Overview of Configuration .................1 Functions of the NEs ......1 Function Code ...................................................3 Configuration Examples...................................................9 FAQ ....................................39-3 39.......................................................................................................................39-2 39......................5 Benefits ..............................................................2........................6 Application Scenario .......................................3 Standard Compliance ................................................................................................................6 Application Scenario ............................................39-10 39...................................................................................3 Working Principle.7 Performance Measurement .........8 Service Interaction...........................5 Service Management ...........................................................................................................................................................1..................................................2 Availability ...................................................................................................................................................................2 Definition ................................................................40-3 40..........................................................39-5 39....1 Requirements for NEs ..............................1 Function Code ................................................................................................................................39-10 39.................................4 Data Configuration .4......2..............1.39-2 39................................39-5 39.........................................4...........1.............40-6 40..................................2 External Interface ........................................................................39-3 39.....................................................................................4 Data Configuration at the UMG8900 Side ...........................................................1........................................................4................................................................................................1......................Contents HUAWEI MSOFTX3000 Feature Description 38............. Acronyms and Abbreviations..........................................................2..............................................40-6 xxx Huawei Technologies Proprietary Issue 02 (2007-02-15) .................................................................................................................................2...........................................................................................11 FAQ ...........................................................39-3 39...........39-4 39............38-13 39 TDM Circuit Selection Based on Service Type................................40-2 40.....................................................40-4 40.........1.................................39-6 39..................................................................4.........................39-2 39...........7 Application Limitations...............................................2........................................................................................................................................39-5 39.39-2 39.......................................40-6 40....................................................................................4 System Specifications...........2................................1.....1 Service Description ........................40-5 40...........1......39-5 39.................................................39-4 39...40-2 40.........................................................2 Definition ................................................................................................................................................................................................3.................................1....1......................10.............39-3 39.....2 Requirements for License..............................38-12 38...........................................2 Glossary...........................................39-10 40 BICC and ISUP Route Allowed for the Same Office Direction....2................................................................................................................40-6 40...........................................................................................................................1..........................................................................................................................39-10 39..3.........................2 Data Configuration at the MSOFTX3000 Side ................................................................................................................................................................39-10 39.................................................................................................................................................4 System Specifications.......39-1 39................................39-10 39................................................................39-3 39...............................3 Standard Compliance ..............................1......................................39-2 39...............40-2 40....39-4 39...............................................................................................................39-3 39.........6 Charging and CDR ........................40-1 40.....................

........................................................................................................2.......................5......................................................3...............................................................................................................10.....................3 Working Principle............................................................................................................................................... 40-11 40.....................................................................40-6 40.40-16 40..........................40-17 40..........................40-16 40...............................5...3 Data Configuration at the UMG8900 Side ..............HUAWEI MSOFTX3000 Feature Description Contents 40.....3........................................6..................................40-16 40....................................................................................................40-6 40........................................1 Functions of the NEs .......................................................................4 Service Flow..................................5 Data Configuration ..................40-16 40....................9 Service Interaction...............................................5..................................................................................40-8 40..........................................................................40-6 40................................................................................................................................................4 Data Configuration Examples .......................6..............1 Standards and Specifications............40-16 40............1 Operations by Carriers...........................................................................................................................................40-8 40...............................................................................................................................................................40-8 40................................3.............................6 Service Management ............................40-6 40...................2 Operations by Mobile Subscribers ...........................................................................3 External Interfaces......................................................................................................................................................40-17 40.....................................40-16 40....11 FAQ ...........................................................1 Overview ......................................................................... i-1 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxxi .....2 Internal Processing of the System ..............................5........7 Charging and CDR ....40-8 40...................................................40-12 40...........2 Data Configuration at the MSOFTX3000 Side ..................10 References .............................40-17 Index ...........................................................................4 Others ............................10.............8 Performance Measurement ...........................................................40-8 40...............................................................................................................40-17 40.2 Acronyms and Abbreviations .

.....................................2-8 Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow .............................................................................................................................................................................1-17 Figure 1-8 Flow of the call from a mobile subscriber to another mobile subscriber (3)..........1-16 Figure 1-7 Flow of the call from a mobile subscriber to another mobile subscriber (2)....1-23 Figure 1-11 Process of generating CDRs when a mobile subscriber calls a fixed line subscriber...........................................................................................................2-7 Figure 2-4 MAP_READY_FOR_SM flow ....................................................................................................................................................................................1-24 Figure 1-13 Process of generating CDRs when the mobile caller and callee are in different wireless networks ................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 1-1 Networking model of the call from a mobile subscriber to a fixed line subscriber.................................1-18 Figure 1-9 Process of generating CDRs when the mobile caller and callee are under the same VMSC ...........2-9 Figure 2-7 SM MT flow ......2-7 Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow......................................................................................................................2-12 Figure 2-10 Flow of alert SMC – SMS succeeds ....................1-9 Figure 1-3 Flow of the call from a mobile subscriber to a fixed line subscriber (2)........................................................................................................2-5 Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow.................................................................................................................................................................................................................1-23 Figure 1-10 Process of generating CDRs when the mobile caller and callee are under different VMSCs .............3-7 xxxii Huawei Technologies Proprietary Issue 02 (2007-02-15) ............................1-8 Figure 1-2 Flow of the call from a mobile subscriber to a fixed line subscriber (1).............................................................1-15 Figure 1-6 Flow of the call from a mobile subscriber to another mobile subscriber (1)...1-13 Figure 1-5 Networking model of a call from a mobile subscriber to another mobile subscriber...........................................................................1-25 Figure 2-1 Location of the SMC in a mobile network..........3-6 Figure 3-3 CFU service flow for a call forwarded to a PSTN subscriber.........................................................2-10 Figure 2-8 Flow of alert SMC – mobile station reachable...............................................2-8 Figure 2-6 SM MO flow................................................................................................ 2-11 Figure 2-9 Flow of alert SMC – memory of MS ready ..............................................................................2-13 Figure 3-1 GMSC-originated call forwarding service flow..................................1-10 Figure 1-4 Flow of the call from a fixed line subscriber to a mobile subscriber .....................................1-23 Figure 1-12 Process of generating CDRs when a fixed line subscriber calls a mobile subscriber ...................3-5 Figure 3-2 VMSC-originated call forwarding service flow.............................

..................................................................................................5-7 Figure 5-2 Service flow when a subscriber rejects a waiting call...........6-7 Figure 6-4 Disconnect the remote subscriber by main controller ..................................................................................................................7-10 Figure 7-7 BI service flow.....................................................................................................4-7 Figure 4-3 COLP service flow........3-16 Figure 3-12 CFNRc service flow for the mobile forwarded-to subscriber ........................3-10 Figure 3-7 NDUB service flow for a call forwarded to a mobile subscriber ...........................................3-9 Figure 3-6 UDUB service flow for a call forwarded to a PSTN subscriber .........................3-14 Figure 3-11 CFNRc service flow for call forwarded to a PSTN subscriber ...............................................................................................................................................5-10 Figure 5-4 Service flow for alternating from the A-B call to the A-C call ....................................................................................................................................... ...............................................................................................7-8 Figure 7-5 Check flow of the HLR for the BIC-ROAM service ................................................... 3-11 Figure 3-8 UDUB service flow for a call forwarded to a mobile subscriber .........................................................................................................................................................................................................4-8 Figure 4-4 COLR service flow .....3-12 Figure 3-9 CFNRy service flow for a call forwarded to a PSTN subscriber .......................................................................................................................................................................................................................................................................6-6 Figure 6-2 Create a personal communication .................................................................5-9 Figure 5-3 Service flow for holding and retrieving a call........................................................................................................................................10-4 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxxiii .. 7-11 Figure 8-1 Invoking the ECT when A-B call is on hold and A-C call is in the active state........................................................7-7 Figure 7-4 Check flow of the HLR for the BAIC service................................................................................................................7-9 Figure 7-6 BO service flow ....................................................................3-22 Figure 4-1 CLIP service flow ....................6-8 Figure 6-5 Disconnect the remote subscriber by main controller ............................................................3-17 Figure 3-13 Charging of the call forwarding services .................8-5 Figure 8-2 Invoking the ECT when C is in the alerting state.............7-5 Figure 7-2 Check flow of the VLR for the BOIC service..........................................................................................................8-6 Figure 10-1 Flow of UMTS authentication ............... 5-11 Figure 6-1 Setting up the MPTY call.................................4-8 Figure 5-1 Service flow when a subscriber accepts a waiting call ..........................................................7-6 Figure 7-3 Check flow of the VLR for the BOIC-exHC service .....................................................................................................HUAWEI MSOFTX3000 Feature Description Figures Figure 3-4 CFU service flow for a call forwarded to a mobile subscriber.....................................................................................................3-13 Figure 3-10 CFNRy service flow for a call forwarded to a mobile subscriber...............................................................................3-8 Figure 3-5 NDUB service flow for a call forwarded to a PSTN subscriber ........6-7 Figure 6-3 Add a remote subscriber.......................................................................................................................6-9 Figure 7-1 Check flow of the VLR for the BAOC service ...............4-6 Figure 4-2 CLIR service flow......................................................................................................

........................................13-5 Figure 13-3 Ignoring IN service (T-CSI) .......................13-8 Figure 13-6 Ignoring IN service (early forwarding with O-CSI)..............................................12-10 Figure 12-6 Late resource assignment for the caller...........................17-10 Figure 17-7 Filtering interface................................................... 17-11 Figure 18-1 Processing flow of SMS notification for call failure triggered in the GMSC .........................................................................................13-4 Figure 13-2 Routing out the call directly to another office (T -CSI) ......Figures HUAWEI MSOFTX3000 Feature Description Figure 10-2 Flow of GSM authentication................................................................................................................... 11-6 Figure 11-2 General procedure of MSRN allocation ......................................12-5 Figure 12-3 MS-terminated call (early assignment) ........................................................................................................................................14-6 Figure 14-4 MNP service flow in OR mode ................................18-5 xxxiv Huawei Technologies Proprietary Issue 02 (2007-02-15) ............................................................................................................................................................................14-8 Figure 17-1 Local Maintenance Monitor tabbed page.................................................12-8 Figure 12-5 Early resource assignment for the caller ......................................................................................................13-9 Figure 14-1 Networking of MNP service ...............................10-6 Figure 11-1 Simple MSRN allocation procedure...13-6 Figure 13-4 Triggering IN service (early forwarding with O-CSI).................................................................................................................................................................17-8 Figure 17-3 Subscribed NE List interface .............................17-10 Figure 17-6 User Session interface 2................................................. 11-9 Figure 12-1 MS-originated call (early assignment) .................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................12-12 Figure 12-7 Early resource assignment for the callee............12-6 Figure 12-4 MS-terminated call (late assignment) ................................................12-14 Figure 12-8 Late resource assignment for the callee ..........................................................................14-4 Figure 14-2 External network subscriber calls a ported out local network subscriber ...............................................................14-7 Figure 14-5 Local network subscriber calls a ported out local network subscriber based on the IN......17-2 Figure 17-2 User Monitor interface ..................................................................................................................................12-4 Figure 12-2 MS-originated call (late assignment) .....14-5 Figure 14-3 External network subscriber calls a subscriber ported in the Local Network but does not exist in the local network ................ 11-7 Figure 11-3 Procedure for random allocation ..............................................................................17-8 Figure 17-4 User Monitor interface ..................................................................................................................................................................13-7 Figure 13-5 Routing out the call directly to another office (early forwarding with O-CSI) ....12-16 Figure 13-1 Triggering IN service (T-CSI) .............................................................................................................................................................................................................................................. 11-8 Figure 11-4 Mapping between the MSRN or HON allocation tables ...................................17-10 Figure 17-5 User Session interface 1.............................................................................................................14-8 Figure 14-6 Local network subscriber calls a ported out local network subscriber based on signaling ....................

............21-4 Figure 21-2 Illustration of state transition during configuration rollback.....................................19-6 Figure 20-1 Patch operation flow ..................................................................................................................20-5 Figure 21-1 Sketch of the active and the standby areas...25-10 Figure 25-4 IP QoS processing flow in gateway pair mode for intra-office calls.......................................................................................HUAWEI MSOFTX3000 Feature Description Figures Figure 18-2 Processing flow of SMS notification for call failure generated in the VMSC ..........................................................................................................................................................................24-6 Figure 24-3 IP over E1 bearer adopted by intra-office MGWs...........................................................................................23-12 Figure 24-1 Internal processing of IP over E1 processing in the MSOFTX3000 ..........26-5 Figure 26-2 Internal processing of system when the sending of short message is prohibited by the SCP .....24-9 Figure 24-6 Inter-office call flow of backward delay ..................24-5 Figure 24-2 IP over E1 bearer adopted inter-office MGWs..........................................................................................................................................................................................................................................................25-9 Figure 25-3 IP QoS processing flow in inter-office gateway pair mode for inter-office calls ........................................... BAM server..................26-6 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxxv ..................................................................................................................22-8 Figure 22-2 CAP message flow of the IN RBT ................24-17 Figure 25-1 Networking of the IP QoS flow control granularity...................................19-4 Figure 19-2 Time icon of Windows2000 operating system ..............19-5 Figure 19-3 Adjusting clock for daylight saving changes............................................................22-23 Figure 23-1 International roaming subscriber originates a call and the callee is power-off (the GMSC server and VMSC server are combined) ...........23-6 Figure 23-2 Service flow in the case of an abnormal call.......24-7 Figure 24-4 Inter-office call flow of forward fast.........22-12 Figure 22-5 NC failure in the CAMEL4.............................................................................21-7 Figure 22-1 CAP message flow of the CAMEL4 third-party call ................................................................................................................................................................................................18-8 Figure 18-5 Processing flow after SMS notification for call failure is triggered.................................................................................. 25-11 Figure 26-1 Internal processing of system when the sending of short message is allowed by the SCP ........22-10 Figure 22-3 CAP message flow of the simultaneous ringing with C answering the call first............................18-9 Figure 19-1 Synchronization relationship between the NTP server.................................24-10 Figure 24-7 Setup of intra-office medium cluster....23-7 Figure 23-3 Table query flow in the IMSI-based announcement service ........................................................... 22-11 Figure 22-4 CAP message flow of the simultaneous ringing with B answering the call first............................................................................................................................................24-8 Figure 24-5 Inter-office call flow of forward delay ...........25-6 Figure 25-2 IP QoS processing flow in inter-office office direction mode............................ and the host.......18-6 Figure 18-3 Triggering point of SMS notification for call failure in the GMSC .............18-7 Figure 18-4 Triggering point of SMS notification for call failure in the VMSC ........................24-10 Figure 24-8 Typical networking of IP over E1 .................................................................................................................................................................................................21-5 Figure 21-3 State transition of data in the standby area.....................................

.........................................................................................................................................................................................................................................Figures HUAWEI MSOFTX3000 Feature Description Figure 26-3 Service flow when the sending of short message is allowed by the SCP...........................28-6 Figure 28-4 Registering a backup task for location update .....................................................................27-6 Figure 27-4 Call flow when the access side connects to a narrowband trunk (crossing multiple IP gateways) ............................................ 28-11 Figure 28-8 Flow of status information backup.......28-13 Figure 29-1 Relationship between domains and resources.................................................................................................................................. 27-11 Figure 27-8 Service flow when the access side connects to a BICC trunk (using IP bearer between offices) (TS61) ................................................26-10 Figure 26-5 Procedure for querying the table to obtain the O-CSI SMS processing information ..............................................................................................................................................................................................................................................................................29-14 Figure 29-7 Delete Domain ..........29-6 Figure 29-2 Flowchart of the role-based and domain-based management service ...............................27-14 Figure 28-1 Dual-homing 1 + 1 mutual-aid networking model..............29-12 Figure 29-5 Bind NE ..............................................................29-16 xxxvi Huawei Technologies Proprietary Issue 02 (2007-02-15) ................................................................................................28-9 Figure 28-5 "Dirty" backup flow ..........................29-13 Figure 29-6 Rename Domain.................................................................28-10 Figure 28-6 Complete backup flow ....................................................................................................................................28-5 Figure 28-2 Dual-homing N+1 backup networking model....................................................27-10 Figure 27-7 Service flow when a narrowband trunk connects to a narrowband trunk (crossing multiple IP gateways) (TS61) ........................27-4 Figure 27-2 Call flow when a narrowband trunk connects to a narrowband trunk (crossing multiple IP gateways).........29-9 Figure 29-3 Create Domain ........28-6 Figure 28-3 Block diagram of dual-homing backup.................................................27-7 Figure 27-5 Call flow when the access side connects to a BICC trunk (TS62) ..............................................................................................................28-10 Figure 28-7 Flow of location information backup..................................26-15 Figure 26-6 Procedure for querying the table to obtain the location number in the INITIAL-DP message ..............................................................................27-8 Figure 27-6 Service flow when a narrowband trunk connects to a BICC trunk (voice service switching to fax service) ...................................................................................................................................................................................................................................28-12 Figure 28-9 Flow of authentication data backup .................... 29-11 Figure 29-4 Bind User ...........................................................................................................................................................................................................................................................................................................................................................................................................................27-5 Figure 27-3 Call flow when the access side connects to a BICC trunk (TS61) ..........................................................27-13 Figure 27-9 Service flow when the access side connects to a BICC trunk (TS62)....28-12 Figure 28-10 Flow of synchronous deleting backup data ......................................................................26-8 Figure 26-4 Service flow when the sending of short message is prohibited by the SCP...................................................................................................................................................................26-16 Figure 27-1 Call flow when a narrowband trunk connects to a BICC trunk ..............................................................................

32-12 Figure 33-1 Trace flow of the activation message received from the HLR during location update/data recovery ....................................................................................................................................31-16 Figure 32-1 Flow of the intra-MSC handover ....................33-10 Figure 34-1 Location update message flow....32-7 Figure 32-4 Inter-MSC load-based handover from 3G to 2G system........................................................................................34-8 Figure 35-1 Dialing test model on the designated TDM circuit...............................32-9 Figure 32-6 Inter-MSC load-based handover from 2G to 3G system.. .............................................31-12 Figure 31-4 Displayed query result ......................................31-12 Figure 31-3 Specifying the querying conditions.............................................................................33-7 Figure 33-4 Trace flow of the initiation call ............33-9 Figure 33-7 Trace flow of the terminated short message.................................................................35-4 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxxvii .........................................31-14 Figure 31-8 Shortcut menu in the output pane.....................................................................................................................................................................................31-7 Figure 31-2 Detailed query result ........................................................................................................HUAWEI MSOFTX3000 Feature Description Figures Figure 30-1 Processing of the NEs for the alarm for malicious short messages service ........................................................................................................................................................................................................................................30-6 Figure 31-1 Example of the BAM log ................................................................................................................................................................................................................................33-8 Figure 33-5 Trace flow of the termination call ................................................................................30-5 Figure 30-2 Process of the alarm for malicious short messages ..........................................................................................................................................................................................................................................31-13 Figure 31-5 Call simulation node .33-9 Figure 33-8 Trace flow of power-on/location update ..........31-14 Figure 31-7 Message output format...............................................................................................................................................................................................31-13 Figure 31-6 Specifying call simulation related parameters..32-6 Figure 32-3 Intra-MSC load-based handover from 3G to 2G system..33-10 Figure 33-9 Trace flow of the power-off .......................................................................................................................................................................................................... 32-11 Figure 32-8 Inter-MSC load-based handover in the 2G network ....................................................................... ................................................33-6 Figure 33-2 Trace flow of the activation message sent by the HLR.....................33-7 Figure 33-3 Flow of the deactivation trace sent by the HLR......................................................................................................................................................................................34-6 Figure 34-2 Originated service message flow ................................................................................................................................................................................................................................................................32-8 Figure 32-5 Intra-MSC load-based handover from 2G to 3G system.............35-2 Figure 35-2 Processing flow inside the system.............34-7 Figure 34-3 Terminated service message flow ..................32-6 Figure 32-2 Flow of the inter-MSC handover ...............................................................32-10 Figure 32-7 Intra-MSC load-based handover in the 2G network .....................33-8 Figure 33-6 Trace flow of the originated short message........................................................

.......................................................................Figures HUAWEI MSOFTX3000 Feature Description Figure 35-3 Flow of the dialing test on the designated TDM circuit for the trunk outgoing call from the MS to the PSTN .................................................................................................................................................................................................................................................................................................................................................................................................................................................... 36-11 Figure 36-7 Other MSC user calling WIN user .........................................40-5 Figure 40-4 Scenario 3 ..................................................37-4 Figure 37-2 ADD message flow ...............................................................................................38-10 Figure 38-4 Table query flow of noise suppression service (Support noise removing benefit peer end) ........40-5 xxxviii Huawei Technologies Proprietary Issue 02 (2007-02-15) .....................................36-12 Figure 36-8 Special flow of the number regulation ...............................................................................................36-13 Figure 37-1 Flow of the ADD service ...........................................38-6 Figure 38-3 Table query flow of noise suppression service (Support noise removing benefit local end).......................................................................................................................................37-5 Figure 37-3 Table query flow of the ADD service....38-5 Figure 38-2 Service flow of the noise suppression feature.............................................37-10 Figure 38-1 Networking of the system internal processing .........................35-6 Figure 35-4 Message flow of the dialing test on the designated TDM circuit for the intra-office call .......................................................35-8 Figure 36-1 Transiting a call out after caller IN service invoked in the local office.......36-6 Figure 36-2 Callee IN service invoked in the local office for a trunk incoming call......................................36-7 Figure 36-3 WIN user calling fixed user ....................................................................................................................................... 38-11 Figure 39-1 TDM circuit selection based on the service type ..............39-4 Figure 40-1 Current networking of China Mobile..............36-10 Figure 36-6 Fixed user calling WIN user .......................................................................36-9 Figure 36-5 WIN user calling other MSC user with acquiring roaming number in the local office..............................................................................................36-8 Figure 36-4 WIN user calling other MSC user without acquiring roaming number in the local office...........................................................40-4 Figure 40-3 Scenario 2 .......................................................40-3 Figure 40-2 Scenario 1 ....................................................

.................................................................................................................................................................................1-4 Table 1-5 Versions of the products that support the speech service .......................................................................................2-4 Table 2-3 Functions of NEs in the transmission of SMs.........................................................................................................3-20 Table 3-10 CFNRc service operation.......................................................................................................................................................................................1-21 Table 1-8 Interaction between the emergency call function and other services ........3-4 Table 3-6 Operation modes of the call forwarding service ........................................................................2-5 Table 2-4 Functions of NEs in the transmission of SMs...........................................................................1-20 Table 1-7 Configuration steps ...............3-2 Table 3-2 Definitions of the call forwarding services .....................................................3-2 Table 3-3 Benefits of the call forwarding services........................................................................................................................................................................................................................................................................................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 1-1 Function names and function codes in the speech service ..............................................................................................................1-26 Table 2-1 NEs required to realize the SMS.............................................................................................................3-20 Table 3-9 CFNRy service operations ..........................................................................................................1-5 Table 1-6 Differences between early assignment and late assignment .....................................................................3-3 Table 3-5 Applicable versions.......3-18 Table 3-7 CFU service operations.1-2 Table 1-3 Benefits for carriers and mobile subscribers................................................................................................2-4 Table 2-2 HUAWEI CS product versions that support the SMS.............................1-4 Table 1-4 NEs involved in the speech service ......................2-16 Table 3-1 Function code...............3-21 Table 3-12 All the CCF services .........3-19 Table 3-8 CFB service operations...........................................................................................................................................................................................................................................................................................................................................................................................................1-2 Table 1-2 Definitions of functions in the speech service .........................2-6 Table 2-5 Interaction between the SMS and other services ........................................................................................................................................................................................................................3-3 Table 3-4 Related NEs .......3-23 Issue 02 (2007-02-15) Huawei Technologies Proprietary xxxix ..............................................................................3-20 Table 3-11 Operations applicable to all the call forwarding services.........................3-21 Table 3-13 CDR creation principles..

................................................................................3-24 Table 3-15 Interaction Between CUG and Call Forwarding.....................................................................................................................................................................................................................................3-30 Table 3-18 Interaction between CFNRc and other services ...................................................................................................................................................................................5-14 Table 5-8 Operations performed by mobile subscribers ....................................................................................................................................................................................................................................5-3 Table 5-4 NEs required by the call completion supplementary services.....6-3 Table 6-2 Applicable versions of the MPTY...........4-13 Table 4-10 Interactions between the COLR service and other services........Tables HUAWEI MSOFTX3000 Feature Description Table 3-14 Interaction between the CFU and other services........................4-2 Table 4-2 Beneficiaries and description of the benefits .........7-4 xl Huawei Technologies Proprietary Issue 02 (2007-02-15) .................................................................................................................................................................................................................4-14 Table 5-1 Name and code of the function .........................5-3 Table 5-5 Applicable versions of Huawei wireless core network products.........4-4 Table 4-4 Applicable versions of Huawei wireless core network products............................................................4-4 Table 4-3 NEs required by the line identification services ........................................................................................................................4-12 Table 4-8 Interactions between the CLIR service and other services ..............................5-18 Table 5-10 Interactions between the CH service and other services ..........................................................................4-12 Table 4-7 Interactions between the CLIP service and other services ..........................................................5-2 Table 5-2 Name and definition of the CW and CH services ..........................................................................5-2 Table 5-3 Beneficiaries and description of the benefits .... 6-11 Table 6-4 MPTY service operation (For mobile subscriber)...........6-13 Table 7-1 Name and code of the function ..............................................................................3-28 Table 3-17 Interaction between CFNRy and other services ........... 6-11 Table 6-5 Interactions between the MPTY and the other services ............3-27 Table 3-16 Service interaction between the CFB and other services ...................5-15 Table 5-9 Interactions between the CW service and other services .......5-19 Table 6-1 Network elements involved in MPTY features...............................................................................................5-4 Table 5-6 Related software parameters .........4-5 Table 4-5 Operation modes of the line identification services........................................................................................................................................................................................................4-13 Table 4-9 Interactions between the COLP service and other services ............................................................................................................................................................................................ 4-11 Table 4-6 CLIR service operation performed by mobile subscribers..6-3 Table 6-3 Operation method for MPTY service.........7-3 Table 7-3 Applicable versions of Huawei wireless core network products.......................................................................................................................................................3-33 Table 4-1 Names and codes of functions .......................................................................................................................................................................................7-2 Table 7-2 NEs required by the call barring services .............5-13 Table 5-7 Operation modes of the call completion supplementary services ....................................................

............................8-9 Table 8-8 Scenarios of the ECT segmented charging .........................................................10-3 Table 10-4 Versions of the products that support the authentication and encryption................................................................................................................9-5 Table 9-4 Service interaction between ODB and other services ...........................................................................................................................12-3 Table 12-2 Applicable versions................................................ 11-4 Table 11-3 NEs required by the enhanced MSRN allocation service ..................................................................................................................................................................... ..................................10-2 Table 10-2 Benefits for carriers and mobile subscribers....................................................8-2 Table 8-2 Benefits of the ECT ....................8-12 Table 9-1 Name and function code of the ODB services ..............................................8-3 Table 8-4 Applicable versions.............................12-3 Table 13-1 Name and function code of the IN service triggering.......................................................................................8-2 Table 8-3 Requirements for NEs...........................................................7-15 Table 7-7 Interactions between the BOIC service and other services ............................................. 11-2 Table 11-2 Beneficiaries and description of the benefits .......................................8-8 Table 8-7 Scenarios of the ECT independent charging ..........................................................................................................................................9-7 Table 10-1 Function names and functions codes in the authentication and encryption ...............................13-2 Table 13-3 NEs related to the IN service triggering......................................................................10-3 Table 11-1 Name and code of the function ............................................................................................... 11-5 Table 12-1 Requirement for NEs ...................................................................7-16 Table 7-8 Interactions between the BOIC-exHC service and other services .............................. 8-11 Table 8-9 Interaction between the ECT and other services.................................................................................................................................................................................................................................................................7-18 Table 7-10 Interactions between the BIC-ROAM service and other services............................................8-3 Table 8-5 Parameters of the related software..................................13-3 Issue 02 (2007-02-15) Huawei Technologies Proprietary xli ...........................HUAWEI MSOFTX3000 Feature Description Tables Table 7-4 Operation modes of the call barring supplementary services .....................................................................13-2 Table 13-2 Processing modes of the IN services........................................................................................................................................................................................................................... 11-4 Table 11-4 Applicable versions of HUAWEI wireless core network products ......................................................................................................................7-19 Table 8-1 Function code of the ECT.......................................................7-17 Table 7-9 Interactions between the BAIC service and other services ..............................................................................7-13 Table 7-6 Interactions between the BAOC service and other services ..........................................................................................8-7 Table 8-6 ECT operation mode .................7-13 Table 7-5 Operations performed by mobile subscribers .................................................................9-4 Table 9-3 Versions that support the ODB services...........................................................................................................................................................................................10-2 Table 10-3 NEs involved in the authentication and encryption .....................................9-2 Table 9-2 NEs related with the ODB services ..............................

................14-3 Table 14-2 Product versions that support the MNP feature ..............16-6 Table 16-3 Parameters of the command DSP ESN ........................................18-3 Table 18-4 Script for querying the License.....................................................................................................................................19-3 xlii Huawei Technologies Proprietary Issue 02 (2007-02-15) ...................................................17-5 Table 18-1 Benefits of SMS notification for call failure.................................................................................................................................................................................15-8 Table 15-4 Value options of 2198 redundancy level ...............................................................................................13-3 Table 14-1 Related NEs of MNP feature .................................................19-3 Table 19-3 Versions that support the summer time feature of the wireless time zone ..................................................................15-8 Table 15-2 Value options of Support 2198 redundancy ....................................................................................................................................................................................................................................................................16-19 Table 17-1 Function code of the NE user dynamic monitoring function .............................................................18-2 Table 18-2 Requirements for NEs...........................................................................................................18-3 Table 18-3 Applicable versions...................................................................17-5 Table 17-6 Version that supports this function....................................................................................................................................................................................... 18-11 Table 19-1 Name and function code of the summer time feature ..................16-8 Table 16-4 Parameters of the command DSP LICENSE .................................................................................................................................................................................15-8 Table 15-5 Value options of 2198 redundancy CODEC type.......15-9 Table 15-6 Value options of BICC support red ..................................................................................................17-3 Table 17-3 Specifications of the system..................................................................................................................................................15-9 Table 16-1 Parameters of the command LOD LICENSE ................18-10 Table 18-5 Script for setting MAP parameter ............................................................16-19 Table 16-8 Alarms from BAM .............................................................................................15-8 Table 15-3 Value options of 2198 UP Mode ......................................................................................................17-4 Table 17-5 NEs that are involved in this function........................ 18-11 Table 18-6 Script for adding the content of SMS notification for call failure..17-4 Table 17-4 Description of benefits................. 16-11 Table 16-7 Alarms from host ......................................16-10 Table 16-6 Parameters of the command ULD LICENSE .................................................................................................................16-9 Table 16-5 Parameters of the command DMP LICENSE ..........................Tables HUAWEI MSOFTX3000 Feature Description Table 13-4 Versions that support the IN service triggering.............................................................................................16-4 Table 16-2 Parameters of the command LST LICENSE .................................................................................................................17-2 Table 17-2 Explanations of the Local Maintenance Monitor tabbed page............................................................................................ 18-11 Table 18-7 Script for configuring the processing for SMS notification for call failure ...........19-2 Table 19-2 NEs related to the summer time feature of the wireless time zone ...............................................................................................................................................................14-3 Table 15-1 Value options of Support FAX detection ................................

...............................................21-3 Table 21-3 Applicable versions that support the configuration rollback feature............................................22-18 Table 22-8 List of supplementary services supported in mode A .....21-10 Table 21-6 Synchronization and forcible synchronization commands....21-17 Table 21-8 Rollback and forcible rollback commands....22-4 Table 22-4 NEs required to implement the CAMEL4 feature .......................................................................22-5 Table 22-6 New CSA Measurement...............................................................................................24-2 Table 24-3 NEs related with IP over E1..................................................................................................................21-2 Table 21-2 Benefits of the configuration rollback feature .........................23-10 Table 24-1 Function code about this service......................................................................................20-7 Table 21-1 Feature name and function code .............................................................................21-3 Table 21-4 Tables that support configuration rollback............................................................................................................22-18 Table 22-7 Modified WIN event measurement................................................................................................24-4 Table 24-4 Product versions that support IP over E1.................................................................................23-4 Table 23-4 Version of Huawei UMTS MSOFTX3000 that supports the IMSI-based announcement service 23-5 Table 23-5 Steps of data configuration on the MSOFTX3000........21-9 Table 21-5 List of configuration rollback commands .....................21-19 Table 21-9 Cancellation and confirmation commands.........................................................................................................................................................................................................................................................................24-4 Table 25-1 NEs that are involved in this IP QoS flow control...........................................................22-2 Table 22-3 Benefits for carriers and mobile subscribers.................................................................................................................................................22-20 Table 23-1 Name and code of the function ......HUAWEI MSOFTX3000 Feature Description Tables Table 19-4 Alarms related to summer time ....................................................................................................................................................23-3 Table 23-3 NEs required to implement the IMSI-based announcement service .....................20-3 Table 20-3 MML command table for patch management ....................................................................................................................................................................................................................................................21-21 Table 21-10 Query commands .....23-3 Table 23-2 System specifications...........................................21-24 Table 22-1 Function name and function code in the CAMEL4 service .............................................................................19-5 Table 20-1 Network elements concerning with version software management features ..................................................................22-5 Table 22-5 Versions of the Huawei UMTS products that support the CAMEL4 feature...................................................................................................24-2 Table 24-2 Benefits of this service to carriers and mobile subscribers ..................................................................................................22-2 Table 22-2 Added call functions in the CAMEL4 service ........25-3 Issue 02 (2007-02-15) Huawei Technologies Proprietary xliii ........................20-3 Table 20-2 Applicable versions for the version software management features ..................................................21-14 Table 21-7 Activation and forcible activation commands...............................................23-8 Table 23-6 Related tables in the IMSI-based announcement service..................................................................................................................................................................................

.......................................27-3 Table 28-1 Function code............................................................28-2 Table 28-2 Concepts related to VDB dynamic data backup.................31-2 Table 31-2 System specifications of the call simulation ...............................................................................30-3 Table 30-5 Commands involved in the alarm for malicious short messages ...................................................26-3 Table 26-4 Versions of Huawei core network products that support the O-CSI SMS ................................................................................................................................................................................26-18 Table 27-1 Name and code of the function ....................29-3 Table 29-3 Benefits.............................................................30-3 Table 30-4 Versions of the Huawei CS products that support the alarm for malicious short messages .30-2 Table 30-3 NEs required to implement the alarm for malicious short messages ........................................................................................................................................28-4 Table 28-4 Versions applicable to VDB dynamic data backup ..................................................................................................................................................................................................................................26-7 Table 26-6 Logical relationship to determine whether to allow the triggering of the O-CSI.................25-4 Table 25-3 Software parameter setting for QoS flow control function .............................................................................27-2 Table 27-2 NEs required to implement the UP header redundancy service ....................................................................................................26-15 Table 26-11 interactions between the O-CSI SMS and other services............................................................25-12 Table 26-1 Function code.......................................26-12 Table 26-9 Parameter description of ADD LAISAI (3G) .........30-7 Table 31-1 Definitions of the functions ..............................................................................................30-2 Table 30-2 Benefits of the alarm for malicious short messages function..........26-2 Table 26-3 NEs required to implement the O-CSI SMS ...........................................................................................................................................................................................................................................................26-13 Table 26-10 Tables related to the O-CSI SMS .............................................................................31-5 xliv Huawei Technologies Proprietary Issue 02 (2007-02-15) .................26-2 Table 26-2 Benefits of the O-CSI SMS service ...........................................................................................................................................................................................31-3 Table 31-3 NEs related to call simulation ...Tables HUAWEI MSOFTX3000 Feature Description Table 25-2 Earliest version that implements the IP QoS flow control ........................26-9 Table 26-7 Parameter description of ADD SMOCSI .....................................................................................................29-7 Table 29-5 Versions applicable to role-based and domain-based management feature ....................................................29-3 Table 29-2 Classification of resources ....28-2 Table 28-3 NEs required for the VDB dynamic data backup...................................................................................................................................................................................29-7 Table 29-4 NEs required for role-based and domain-based management feature........................29-8 Table 30-1 Function code of the alarm for malicious short messages function ............................... 26-11 Table 26-8 Parameter description of ADD LAIGCI (2G)......................................................26-3 Table 26-5 Parameters in the Initial-DP message ....28-4 Table 29-1 Function code..................................................................................................................27-3 Table 27-3 Versions of the Huawei GSM/UMTS products that support the UP header redundancy service...................

.........................................................................35-2 Table 35-2 Benefits for carriers ...................................................................33-12 Table 34-1 Function code...................32-14 Table 32-7 Operation modes of load-based handover...................................................34-3 Table 34-3 Earliest version applicable to local-based service restriction..................35-3 Issue 02 (2007-02-15) Huawei Technologies Proprietary xlv .........HUAWEI MSOFTX3000 Feature Description Tables Table 31-4 Versions that support the call simulation ...............................................................................................................................................................................................................................................34-13 Table 34-8 Commands to edit location group ...............................................................32-4 Table 32-6 Data tables related to load-based handover...................................................................................................................................................................................................................................31-10 Table 31-6 Script for changing the virtual subscriber data ...........................31-5 Table 31-5 Script for registering virtual subscriber ..............35-3 Table 35-3 NEs required to implement the dialing test on the designated TDM circuit ......34-10 Table 34-6 Commands to set cell and location area relationship .................................................. and service restriction by cell .....................................................................................................................................33-2 Table 33-2 Movements of mobile subscribers .................................................................................................................................31-15 Table 32-1 Function code of load-based handover ......................32-15 Table 33-1 Function name and function code in the union subscriber trace ...................................................................... 34-11 Table 34-7 Commands to add ZC .....................................................................................................34-15 Table 34-10 Commands to edit user group roaming right.......................................................................................................................................................................................................................................................................................................................34-10 Table 34-5 Commands to set non-preferential cell tariff ..................................................................................................................33-3 Table 33-4 NEs required to implement the union subscriber trace service ....................................................................................................................................................................................................................................33-2 Table 33-3 Benefits for carriers ....31-15 Table 31-9 Description of the shortcut menu of the message output pane....................... 31-11 Table 31-8 Meanings of the message contents............33-12 Table 33-7 Operation modes of the union subscriber trace....32-4 Table 32-5 The earliest version of the MSOFTX3000 that supports load-based handover ................................................................................................................32-2 Table 32-3 Benefits of the load-based handover service....... cell-based charging....................................................................................34-14 Table 34-9 Commands to edit roaming-restricted groups ..........................34-4 Table 34-4 Enabling or disabling command .....................33-4 Table 33-5 Version of the Huawei UMTS products that support the union subscriber trace service .............34-2 Table 34-2 Benefits.....................................................................................................................................................................33-4 Table 33-6 Related tables of the union subscription trace.......................................................................32-3 Table 32-4 NEs required to implement load-based handover ................................... 31-11 Table 31-7 Script for querying the virtual subscriber information.............32-2 Table 32-2 Specifications of the load-based handover service ................................................................34-16 Table 35-1 Function name and function code in the dialing test on the designated TDM circuit ....

...........................................................................40-6 xlvi Huawei Technologies Proprietary Issue 02 (2007-02-15) .....40-2 Table 40-2 Key parameter used in this service ....................................................................................35-10 Table 36-1 Function name and function code in the IN service performance measurement enhancement...................................................36-4 Table 36-4 NEs required to implement the IN service performance measurement enhancement.......39-4 Table 40-1 Function code of the BICC and ISUP route allowed for the same office direction service ........................................................................................................40-4 Table 40-4 NE required to implement this service........37-3 Table 37-5 Operations of data configuration at the MSOFTX3000.......................................................................................................................................................................36-3 Table 36-2 System specifications................................................................................ 37-11 Table 38-1 Function code of the noise suppression feature ........................................................................................................................................................................................................................................................................................................................37-2 Table 37-2 Beneficiaries and description of the benefits of the ADD service .............................................................................................................................................................................38-2 Table 38-2 NEs related to the noise suppression service ..........Tables HUAWEI MSOFTX3000 Feature Description Table 35-4 Versions of the Huawei UMTS products that support the dialing test on the designated TDM circuit ....38-4 Table 39-1 NE required to implement the function of TDM circuit selection based on service type ............................................................36-3 Table 36-3 Benefits for carriers ..................................................................................40-3 Table 40-3 Benefits of the BICC and ISUP route allowed for the same office direction service..................35-4 Table 35-5 Related software parameters .................................................................................................................37-7 Table 37-6 Name and function of tables related to the ADD service................................................................................................................36-18 Table 37-1 Name and code of the function ............................37-9 Table 37-7 Operation modes of the ADD service ..39-3 Table 39-2 The version of the Huawei UMTS CS product that supports TDM circuit selection based on service type................................................................................................................................................36-5 Table 36-6 Operation modes of the IN performance measurement enhancement ................................................37-2 Table 37-3 Network elements involved in the ADD service....37-3 Table 37-4 Versions supported by the ADD service.....................................................................38-4 Table 38-3 Versions supporting the noise suppression service ..40-6 Table 40-5 Version of Huawei MSOFTX3000 that supports the service .....................................................36-4 Table 36-5 Version of the Huawei UMTS products that support the IN service performance measurement enhancement........................................................................................................

...........................1 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ...........................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents About This Document................

service flow. The manual introduces the features of V100R005C10 of the MSOFTX3000. Product Name MSOFTX3000 Version V100R005C10 Intended Audience This document is intended for: Market technical personnel Telecommunications management personnel Mobile network system engineer Organization This document consists of thirty seven chapters is organized as follows. realization principle.HUAWEI MSOFTX3000 Feature Description About This Document About This Document Purpose The manual introduces the features of V100R005C10 of HUAWEI MSOFTX3000 Mobile SoftSwitch Center (hereinafter referred to as MSOFTX3000). data configuration and service interaction of each feature. Related Versions The following table lists the product versions related to this document. audiences can use the MSOFTX3000 more easily. This manual describes the definition. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1 . In this way.

and special service emergency call. charging and CDR. and the interception with other services of the IN service triggering feature. This chapter describes the implementation principle. This chapter describes the implementation method and principle of the explicit call transfer service. This chapter describes the implementation method and principle of the call completion supplementary service. This chapter describes enhanced MSRN allocation methods supported by the system. service flow. data configuration and service management of the authentication feature. service flow. service flow. data configuration service management and the interception with other services of the short message service. and data configuration of the IP fax feature. service flow. This chapter describes the implementation method of the multiparty service. data configuration service management and the interception with other services of the speech services. This chapter describes the implementation principle. service flow. such as phone service. This chapter describes the mobile number portability feature. service flow. This chapter describes the service flow. This chapter describes the implementation principle. This chapter describes the implementation principle. service flow. This chapter describes the implementation principle. and the interception with other services of the call barring service. data configuration and service management of the call forwarding early and late assignment feature. 2 Short Message Service 3 Call Forwarding Supplementary Service 4 Line Identification Service 5 Call Completion Supplementary Service 6 7 Multiparty Service Call Barring Service 8 Explicit Call Transfer Service 9 10 ODB Service Authentication Feature 11 Enhanced MSRN Allocation Feature 12 Early and Late Assignment Feature 13 IN Service Triggering Feature 14 15 MNP Feature IP Fax Feature 2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . and the interception with other services of the call forwarding supplementary service. service flow. This chapter describes the feature of the OBD service. This chapter describes the implementation principle. This chapter describes the implementation principle. and the interception with other services of the line identification service.About This Document HUAWEI MSOFTX3000 Feature Description Chapter 1 Speech Service Content This chapter describes the implementation principle. emergency call.

This chapter describes the implementation principle and data configuration of the NE user dynamic monitoring feature. This chapter describes the implementation principle. This chapter describes the implementation principle. data configuration service management and the interception with other services of the VDB dynamic data backup. data configuration service management and the interception with other services of the IMSI-based announcement. 17 NE User Dynamic Monitoring Feature 18 SMS Notification for Call Failure Feature 19 Summer Time Feature of Wireless Time Zone 20 Version Software Management Feature 21 Configuration Rollback Feature 22 CAMEL4 Service 23 IMSI-Based Announcement 24 IP over E1 25 IP QoS Flow Control 26 O-CSI SMS 27 UP Header Redundancy Data Service 28 VDB Dynamic Data Backup Issue 02 (2007-06-10) Huawei Technologies Proprietary 3 . service flow. service flow. service flow. This chapter describes the implementation principle. data configuration service management and the interception with other services of the UP header redundancy data service. and the stability and safety of the system operation. and its impacts on the charging and CDR. This chapter describes the method of rolling back the data configuration of the system. and the interception with other services of the SMS notification for call failure feature. the control items of the License. data configuration service management and the interception with other services of the IP over E1. data configuration service management and the interception with other services of the IP QoS flow control. to ensure the correctness of the data configuration. This chapter describes the implementation principle. service flow. data configuration service management and the interception with other services of the O-CSI SMS. This chapter describes the implementation principle of the summer time feature of wireless time zone. data configuration service management and the interception with other services of the CAMEL4 service.HUAWEI MSOFTX3000 Feature Description About This Document Chapter 16 License Feature Content This chapter describes the implementation principle of the License feature. service flow. the time of the rollback. This chapter describes the implementation principle. This chapter describes the implementation principle. This chapter describes the management feature of the network management system to the MSOFTX3000 software version. This chapter describes the implementation principle. This chapter describes the implementation principle. service flow. the O&M of the License files. service flow. service flow. and the cautions of using the License.

data configuration service management and the interception with other services of the noise suppression. This chapter describes the implementation principle. service flow. This chapter describes the implementation principle. service flow. service flow. service flow. service flow. This chapter describes the implementation principle. service flow. service flow. service flow. data configuration service management and the interception with other services of the service restriction by cell. service flow. data configuration service management and the interception with other services of the load-based handover. This chapter describes the implementation principle. This chapter describes the implementation principle. data configuration service management and the interception with other services of the union subscriber trace. This chapter describes the implementation principle. data configuration service management and the interception with other services of the multi-area network role-based and domain-based management feature. data configuration service management and the interception with other services of the alarm for malicious short messages. data configuration service management and the interception with other services of the TDM circuit selection based on service type. service flow. data configuration service management and the interception with other services of the dialing test on designated TDM circuit. data configuration service management and the interception with other services of the call simulation. service flow. This chapter describes the implementation principle. data configuration service management and the interception with other services of the IN service performance measurement enhancement. service flow. data configuration service management and the interception with other services of the automatic device detection. This chapter describes the implementation principle. 31 Call Simulation 32 Load-Based Handover 33 Union Subscriber Trace 34 Service Restriction by Cell 35 Dialing Test on Designated TDM Circuit 36 IN Service Performance Measurement Enhancement 37 Automatic Device Detection 38 Noise Suppression 39 TDM Circuit Selection Based on Service Type 40 BICC and ISUP Route Allowed for the Same Office Direction 4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . This chapter describes the implementation principle. This chapter describes the implementation principle. This chapter describes the implementation principle. data configuration service management and the interception with other services of the BICC and ISUP route allowed for the same office direction.About This Document HUAWEI MSOFTX3000 Feature Description Chapter 29 Multi-Area Network Role-Based and Domain-Based Management Feature 30 Alarm for Malicious Short Messages Content This chapter describes the implementation principle.

Book titles are in italics. if not avoided. log in as user root. directories. could result in minor or moderate injury. Provides additional information to emphasize or supplement important points of the main text. if not avoided. Indicates a tip that may help you solve a problem or save time.HUAWEI MSOFTX3000 Feature Description About This Document Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. For example. will result in death or serious injury. if not avoided. Alternative items are grouped in braces and separated by vertical bars. Items (keywords or arguments) in square brackets [ ] are optional. could cause equipment damage. } [ x | y | . Terminal display is in Courier New. data loss. Optional alternative items are grouped in square brackets and separated by vertical bars. Command Conventions Convention Boldface Italic [] { x | y | ... Names of files. Indicates a potentially hazardous situation that. Symbol Description Indicates a hazard with a high level of risk that. One is selected. and users are in boldface. or unexpected results. and performance degradation. ] Description The keywords of a command line are in boldface.. One or none is selected. Indicates a hazard with a medium or low level of risk which.. General Conventions Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Command arguments are in italics. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5 . folders.

Press the keys in turn. the latest document version contains all updates made to previous versions. press Enter and press Tab. Key 2 Mouse Operation Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Multi-level menus are in boldface and separated by the ">" signs. pressing Alt. Keyboard Operation Format Key Key 1+Key 2 Description Press the key. For example.. pressing Ctrl+Alt+A means the three keys should be pressed concurrently. For example. GUI Conventions Convention Boldface > Description Buttons. Press the primary mouse button twice continuously and quickly without moving the pointer. choose File > Create > Folder. Key 1.About This Document HUAWEI MSOFTX3000 Feature Description Convention { x | y | . Press and hold the primary mouse button and move the pointer to a certain position. A means the two keys should be pressed in turn. For example. Update History Updates between document versions are cumulative. Therefore. parameters. 6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . click OK. tabs. Press the keys concurrently. } * Description Alternative items are grouped in braces and separated by vertical bars. and dialog titles are in boldface. A minimum of one or a maximum of all can be selected. For example. For example. menus.. windows.

Updates in Issue 01 (2007-2-15) First release. The updated contents are as follows: The feature description of PCR is added. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7 .HUAWEI MSOFTX3000 Feature Description About This Document Updates in Issue 02 (2007-6-10) Second archive.

....1-21 1.............................................................................................1-2 1.......................7....................1-26 1..............................................3...................2 Requirements for License .........................................................................................................................3 Applicable Versions......................2 Definition .........................................2 CDR for Ordinary Call...........................................................................................................5.............................3 Working Principle.......1-1 1..........................................3 CDR for Emergency Call ...................................1-25 1..................................................................................2...................1-21 1.....................................................1-6 1....................................................................................7...........3 Benefits ............................1-22 1...................................................................................................................................1-21 1.................................................................................................................................................................................................1.........1-21 1............................................................................................................... 1-11 1......................................................................................................................6..........................................1-7 1......................................4....................................................1-4 1.........1.............................9 Reference ..........................1-8 1..1-22 1.................................................1 Function Code.....................................................................1-4 1.........2...................................1-22 1..................................................................................................1-7 1......................3................................................................................................1 Protocols and Specifications ..........................................1 For Carriers .............................1-26 1........................................................................1-4 1...............................................1-22 1.................................................7..........................................1.2 For Mobile Subscribers.........5..................................................................................2 Emergency Call for Special Service..........................................................................................8 Service Interaction ...........1-22 1.........................................1 Generation of CDR ..........................................5 Data Configuration....4 Service Flow..3 Charging Flag of Emergency Call.............................................................7 Charging and CDR ............................................................................3 MMC.............................................3 MMC.........................1 MOC to Fixed Line Subscriber .............1-26 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .....................................1 Service Description ........................................................1 Requirements for NEs..............2 Availability .............................................1-26 1............................1-4 1.............................1 Telephony.....1 MOC .............................................................................................1-2 1.............................6 Service Management ...............................................2.......2 MTC from Fixed Line Subscriber.............HUAWEI MSOFTX3000 Feature Description Contents Contents 1 Speech Service ..4...................................................................................3.........................................................................................................................1-22 1........................................................................................................2 MTC.....................9.......................................................................................................................................................................................................................................................9........................................1-2 1.1-5 1..5.........................................................................4.....................1-5 1.................................................................................................................................................6...........................1-15 1..........................1-4 1.......2 Acronyms and Abbreviations ...................................................

....................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 1-1 Networking model of the call from a mobile subscriber to a fixed line subscriber ..........................................1-8 Figure 1-2 Flow of the call from a mobile subscriber to a fixed line subscriber (1) ........................1-10 Figure 1-4 Flow of the call from a fixed line subscriber to a mobile subscriber .................................1-16 Figure 1-7 Flow of the call from a mobile subscriber to another mobile subscriber (2) ...............1-23 Figure 1-10 Process of generating CDRs when the mobile caller and callee are under different VMSCs...............1-24 Figure 1-13 Process of generating CDRs when the mobile caller and callee are in different wireless networks .................................................1-25 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ..................................1-23 Figure 1-11 Process of generating CDRs when a mobile subscriber calls a fixed line subscriber ........................................................................1-15 Figure 1-6 Flow of the call from a mobile subscriber to another mobile subscriber (1) ..........................................................1-13 Figure 1-5 Networking model of a call from a mobile subscriber to another mobile subscriber ...................1-23 Figure 1-12 Process of generating CDRs when a fixed line subscriber calls a mobile subscriber ..............................................1-18 Figure 1-9 Process of generating CDRs when the mobile caller and callee are under the same VMSC .....................................1-17 Figure 1-8 Flow of the call from a mobile subscriber to another mobile subscriber (3) ....................1-9 Figure 1-3 Flow of the call from a mobile subscriber to a fixed line subscriber (2) ....................

..........1-20 Table 1-7 Configuration steps........................................1-4 Table 1-5 Versions of the products that support the speech service.......1-21 Table 1-8 Interaction between the emergency call function and other services................................................................................................................................1-2 Table 1-2 Definitions of functions in the speech service ..............................................................................................................................................1-2 Table 1-3 Benefits for carriers and mobile subscribers.................1-4 Table 1-4 NEs involved in the speech service ..........................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 1-1 Function names and function codes in the speech service..........................................................................................................................1-5 Table 1-6 Differences between early assignment and late assignment ......................................................................1-26 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ............................................................

Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-1 . and networking requirements. The protocols and specifications that this feature must comply with.8 Service Interaction 1. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. whether Licenses are required.7 Charging and CDR 1.HUAWEI MSOFTX3000 Feature Description 1 Speech Service 1 About This Chapter The following table lists the contents of this chapter. The relationships and restrictions between this feature and other services or features. The data configurations that are required on the MSOFTX3000 and the UMG8900. and the benefits that carriers and mobile subscribers can obtain from this feature. and the acronyms and abbreviations of this chapter.5 Data Configuration 1. The charging and the generation of CDRs when the network provides this feature. The network elements (NEs) that are required for the feature.1 Service Description 1.3 Working Principle 1.9 Reference Describes Speech Service The function code. and the version requirements of the NEs. The service flow of the network when providing this feature. The functions of the NEs. Section 1.4 Service Flow 1. function definition of this feature.6 Service Management 1.2 Availability 1.

Table 1-2 Definitions of functions in the speech service Name Telephony Definition This function enables mobile subscribers to communicate with the subscribers in the PSTN. Compared with the telephony function.1 Service Description 1.1 Function Code Table 1-1 lists the mapping between function names and function codes in the speech service. When a mobile subscriber chooses the type of an emergency call on the menu of an MS/UE or dials 112. Then the device instructs the subscriber how to call the emergency center.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1.1. and emergency call for special service. the processing of the emergency call does not include authentication and specific routing requirements. the call is connected to a record notification device.2 Definition The speech service is the elementary feature of a telecom network. emergency call. Table 1-1 Function names and function codes in the speech service Name Telephony Emergency call Emergency call for special service Code WMFD-010101 WMFD-010102 WMFD-010103 1. An emergency call is of higher priority than an ordinary call.1. The service consists of the functions such as telephony. The subscriber can make an emergency call without a SIM/USIM card. Table 1-2 lists the definitions of these functions. ISDN and PLMN over telephones. Emergency call 1-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

the gateway mobile switching center (GMSC) server initiates the query. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-3 . first-aid center and traffic center. the MSC server/visitor location register (VLR) and media gateway (MGW) perform the following functions: Security control This step is optional. Note PSTN = public switched telephone network.HUAWEI MSOFTX3000 Feature Description 1 Speech Service Name Emergency call for special service Definition When a mobile subscriber dials an emergency number for a special service. the MSC server/VLR and MGW directly perform the following functions: Creating a user panel bearer at the caller side Checking subscription data Pointing to the route of the call to the destination MTC If a mobile subscriber receives a call. Such kind of call can generate alarms. If the caller is a fixed line subscriber. the designated MSC server queries the location information of the callee in the home location register (HLR) to which the callee belongs. Carriers can decide whether to charge the subscriber. If you do not select it. there is a parameter indicating that this is an emergency call. depending on the role of a mobile subscriber in a call. bandit alarm center. because only the HLR stores such information. MOC If a mobile subscriber makes a call. The special service center consists of the fire alarm center. In the universal mobile telecommunications system (UMTS). NOTE The difference between the emergency call for special service function and the emergency call function is that: When a CM service is required. While for the emergency call function. USIM = UMTS Subscriber identity module The call involved in the speech service can be classified into mobile originated call (MOC) and mobile terminated call (MTC). In an MOC. The MSC processes the number as a special service number after analyzing the number. PLMN = public land mobile network. the emergency call for a special service is considered as an ordinary call. this call is an MOC. ISDN = integrated services digital network. the call is connected to a corresponding special service center that is nearest to the base station. SIM = subscriber identity module. the call is an MTC. If the caller is also a mobile subscriber. all network elements (NEs) cooperate with each other to route the call to the mobile subscriber. the MSC server/VLR to which the caller belongs initiates the query. During the setup of an MTC.

NodeB/base transceiver station (BTS). 1. see Table 1-4. The speech service enables mobile subscribers to freely move around the PLMN. Table 1-3 Benefits for carriers and mobile subscribers Beneficiary Carriers Mobile subscribers Description The speech service increases the income of carriers.3 Applicable Versions Table 1-5 lists the versions of the HUAWEI circuited switched (CS) products that support the speech service. because the service is the elementary feature of the HUAWEI wireless core network. radio network controller (RNC)/base station controller (BSC).2.2.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1.2. 1-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .1.2 Availability 1. Table 1-4 NEs involved in the speech service UE/MS √ NodeB/BTS √ RNC/BSC √ MSC Server √ MGW √ SGSN √ VLR √ HLR √ “√” means the NE is required. 1. 1.1 Requirements for NEs The speech service requires the cooperation of the user equipment (UE)/mobile station (MS).2 Requirements for License No License is required to obtain the speech service.3 Benefits Table 1-3 lists the benefits for carriers and mobile subscribers. The service also enables mobile subscribers to make emergency calls without SIM/USIM cards. For details. and make and receive calls in any place at any time. and core network (CN).

can also not be enabled. the MS/UE. MOCs and MTCs enable mobile subscribers to freely move around the global system for mobile communications (GSM)/UMTS. Authentication The authentication function defines whether a mobile subscriber is authorized to access the PLMN. In the GSM and UMTS. This function. This means that the MSC server/VLR performs authentication. Based on the Service request. the UE can also verify the validity of the network. and/or temporary mobile subscriber identity (TMSI) reassignment.1 MOC The processing of the MSC/VLR to an MOC consists of the following aspects: MOC initiation MOC completion MOC Initiation MOC initiation is triggered by the Service request sent from the MS to the MSC/VLR over a radio access network (RAN).3 Working Principle The NEs in the PLMN cooperate with each other to implement MOCs or MTCs. The function prevents invalid subscribers from using the services that the network provides. based on the Service request. encryption/decryption. The MS and AuC calculate authentication parameters respectively. and make and receive calls in any place at any time. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-5 . the following services are processed in MOC initiation: Telephone call and data call Emergency call Input controlled by subscribers Short message The security function is enabled in MOC initiation. In the UMTS. Then the VLR/SGSN compares the two results.3. to verify the validity of the MS/UE. however. 1. VLR/serving GPRS support node (SGSN) and HLR/authentication center (AuC) cooperate with each other to implement authentication.HUAWEI MSOFTX3000 Feature Description 1 Speech Service Table 1-5 Versions of the products that support the speech service Product MSC server MGW MSOFTX3000 UMG8900 Applicable version V100R002 and later V200R002 and later 1.

MOC Completion The MSC/VLR checks subscription data and service compatibility. logical channels are encrypted. The VLR/SGSN must update the CK and IK at least once a day. encryption/decryption guarantees the information exchange through the wireless interface. This function is to prevent intruders from monitoring the signaling on wireless channels and identifying mobile subscribers.2 MTC An MTC is generated when a subscriber in the PSTN/ISDN/PLMN dials the MSISDN of a mobile subscriber. Setup of a user panel bearer at the caller side The MSC server sends a Prepare Bearer request to the MGW. the UE stores a copy of the CK and IK. Call setup between the calling MS/UE and the visited MSC server After the service acceptance message is received or the encryption is complete. Then the VMSC server returns a Call Proceeding message to the calling MS/UE. In the GSM. the Connection request from the mobile subscriber is accepted. is used to identify the subscriber. The processing for the MTC consists of the following aspects: Route information query MTC initiation and completion Route Information Query Route information is used to transfer a call to the MSC/VLR that is in the roaming domain of the mobile subscriber. Secret signaling information and data information are encrypted. 1. cipher key (CK) guarantees the confidentiality of access data. the MS and base station subsystem (BSS) are loaded with the same CK. instead of TMSI or IMSI. That is. which assigns asynchronous transfer mode (ATM) resources dynamically. TMSI is reassigned at the right time. If the check is passed. To obtain the route information. This helps to encrypt channels. The USIM can also send the CK and IK to the UE based on the requirements of the UE. the VMSC/GMSC initiates a query by the steps as follows: 1-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment. That is. encryption/decryption and TMSI reassignment. and sent from the VLR/SGSN to the RNC with the security mode command. The MSC server then sends a Radio Access Bearer (RAB) Assignment message to the radio network subsystem – originated (RNS-O). Integrity key (IK) guarantees the integrity of signaling data. Therefore. To guarantee the confidentiality. to continue the call.1 Speech Service HUAWEI MSOFTX3000 Feature Description Encryption/Decryption In the UMTS.3. Then the originating MSC/VLR assigns service channels and occupies ground circuits. This means that the MSC server/VLR does not perform authentication. the MS sends a Setup message to the visited MSC (VMSC) server. CK and IK are stored in the USIM and VLR/SGSN. When a subscriber makes an emergency call without a SIM/USIM. international mobile station equipment Identity (IMEI). TMSI reassignment The MSC server/VLR assigns a TMSI to a mobile subscriber periodically.

3. it means the mobile subscriber is detected. The HLR requests the mobile station roaming number (MSRN) from the VLR. 2. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-7 . The MSRN is released when the call reaches the VMSC/VLR. encryption. The service MSC/VLR queries the information of the callee in the HLR. The MTC initiation begins. check the cell where the mobile subscriber locates. occupies ground circuits and plays ringing tones. and then requests the MSRN from the VLR.3 MMC A mobile-to-mobile call (MMC) is between two mobile subscribers. The difference between the two functions is that there is no requirement for authenticating the access of the MS in an emergency call.HUAWEI MSOFTX3000 Feature Description 1 Speech Service 1. The MSC/VLR must. TMSI reassignment and equipment control. This means that the system performs authentication. Now the call is connected and the MSC begins to collect the call detail records (CDRs) for charging the subscriber. The MSC server queries the information of the callee in the HLR to which the callee belongs.3. The originating MSC/VLR initiates and completes the MOC. If the mobile subscriber answers the phone. The HLR finds the VLR sequentially based on the mapping between the VLR and ISDN. MTC Initiation and Completion After the call is routed to the VMSC/VLR. 1. depending on the location of the subscriber. the MTC is complete. The MSC/VLR checks the cell by paging. The service MSC/VLR initiates and completes the MTC. 5. If the two mobile subscribers register with the same MSC/VLR and all service channels are exchanged in the same MSC/VLR. MSRN is only used to transfer the call from the GMSC or originating MSC to the VMSC/VLR that is in the roaming domain of the mobile subscriber. During the query. During the requirement for the MSRN. An MMC can be considered as an MOC plus an MTC. The HRL stores the current VLR number of the subscriber and dynamically updates the number. in the location area. The MOC takes place first. the VMSC/VLR transfers the MSRN to the GMSC through the HLR.4 Service Flow The flows in this section are applied to the telephony function and emergency call function. The VLR assigns a temporary MSRN to the callee. The MSC translates the MSISDN and the results include the information of the HLR. If the mobile station responds to the paging. The MSC server begins to query after receiving an MSISDN. followed by the MTC. 2. 6. The MSC/VLR assigns service channels. 7. the MSC/VLR connects the call by the steps as follows if the number analysis result report accepts the MSRN assigned by the VLR. 1. 1. the HLR/AuC and VMSC/VLR check subscription data and service compatibility. The originating MSC/VLR also queries the route to the MS/UE. 4. if required. the service MSC/VLR initiates and completes the MOC and MTC.

Figure 1-1 Networking model of the call from a mobile subscriber to a fixed line subscriber MSC server/VLR RNS-O MGW PSTN UE-O PSTN User The flow of the call from a mobile subscriber to a fixed line subscriber consists of the following aspects: Authentication for the access of the caller Creation of a user panel bearer at the caller side Conversation between the MS/UE and a fixed line subscriber Call disconnection Figure 1-2 and Figure 1-3 show the flow of the call from a mobile subscriber to a fixed line subscriber. 1-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) .4.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1.1 MOC to Fixed Line Subscriber Figure 1-1shows the networking model of the call from a mobile subscriber to a fixed line subscriber.

HUAWEI MSOFTX3000 Feature Description 1 Speech Service Figure 1-2 Flow of the call from a mobile subscriber to a fixed line subscriber (1) UE-O RNS-O CM_Service_Req (Initial UE) MAP_SEND_AUTHENTICATION_INFO MAP_SEND_AUTHENTICATION_ INFO_ACK MSC server/VLR MGW HLR Authentication for the access of the caller AUTHENTICATION REQUEST AUTHENTICATION RESPONSE SECURITY MODE COMMAND(OPTION) SECURITY MODE COMPLETE(OPTION) COMMON ID CM_SERVICE_ACCEPT SETUP CALL PROCEEDING PREP BEARER PREP BEARER RAB ASSIGNMENT REQUEST Creation of a user panel bearer at the caller side RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE BEARER ESTABLISHMENT RAB ASSIGNMENT RESPONSE RESERVE CIRCUIT RESERVE CIRCUIT Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-9 .

1 Speech Service HUAWEI MSOFTX3000 Feature Description Figure 1-3 Flow of the call from a mobile subscriber to a fixed line subscriber (2) UE-O RNS-O (G)MSC Server IAI ACM ALERTING ANC CONNECT CONNECT ACK MGW PSTN Conversation DISCONNECT CLF RELEASE RELEASE COMPLETE RLG IU_RELEASE_COMM AND Call disconnection BEARER RELEASE IU_RELEASE_COMPL ETE RELEASE_TERM RELEASE_TERM RELEASE_TERM RELEASE_TERM 1. The CM Service request consists of the following parameters: Mobile identification Its values are as follows: − − − IMSI TMSI IMEI classmark2 CKSN CM service request type Its values are as follows: 1-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The UE sends a CM Service request to the VMSC server.

4. The two messages are sent through the Iu interface and ISDN User Part (ISUP) trunk respectively. A user panel bearer begins to be created at the caller side. Step 3 takes place immediately after step 1 if there is no security management. the network may obtain authentication set from the HLR/AuC. After the service acceptance message is received or the encryption is complete. 7. The GMSC server releases transaction resources by sending a Release message to the calling UE. After receiving the Setup message. The PSTN returns a Release Guard Signal (RLG) message to the GMSC server after disconnecting the connection. The GMSC server sends an Initial Address Message with Information (IAI) message to the PSTN. The GMSC server releases resources on the user panel after sending two Release Termination messages to the MGW. The PSTN stops sending the ringback tone. The calling UE sends a Release Complete response after receiving the Release message. 6. The VMSC server sends a Prepare Bearer request to the MGW.HUAWEI MSOFTX3000 Feature Description − − − − − 1 Speech Service MOC creation Emergency call creation Short message service Supplementary service Location service CKSN stands for ciphering key sequence number. The GMSC server sends a Clear Forward Signal (CLF) message to the PSTN and instructs it to disconnect the connection. encryption. 3. 14. to obtain the IMSI of the UE. During the process. the called UE sends an ANC message to the network side. 11. 10. The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment. the UE sends a Setup message to the VMSC server. If the caller hangs up first. and sends the ringback tone for the calling MSC. which consists of authentication. 13. the VMSC server returns a Call Proceeding message to the calling UE.4. 1. After the callee hangs up. TMSI reassignment and identity obtaining. The MSC server then sends an RAB Assignment message to the RNS-O. The network may initiate authentication and encryption. 9. 5. The caller and callee begin to talk on the phone. 8. 12. the calling UE sends a Disconnect message to the GMSC server. The MSC/VLR must send a Command ID message to the RNS on not identifying the TMSI of the UE.2 MTC from Fixed Line Subscriber The flow of the call from a fixed line subscriber to a mobile subscriber consists of the following aspects: Route information query Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-11 . The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId (T1). 2. The PSTN returns an Address Complete Message (ACM) message after receiving the IAI message.

ground circuit occupation and ringing tone playing Creation of a user panel bearer at the callee side Conversation between a fixed line subscriber and the MS/UE Release of signaling panel bearer Release of user panel bearer Figure 1-4shows the flow of the call from a fixed line subscriber to a mobile subscriber.1 Speech Service HUAWEI MSOFTX3000 Feature Description Security control for the callee service channel assignment. 1-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

HUAWEI MSOFTX3000 Feature Description 1 Speech Service Figure 1-4 Flow of the call from a fixed line subscriber to a mobile subscriber UE (callee) RNS VMSC server MGW HLR SRI MAP_PROVIDE_ROAMING_NUMBER MAP_PROVIDE_ROAMING_NUMBER_ACK SRI ACK IAI(TUP) PAGING PAGING PAGE RESPONSE AUTHENTICATION REQUEST AUTHENTICATION RESPONSE SECURITY MODE COMMAND SECURITY MODE COMPLETE COMMON ID TMSI REALLOCATION COMMAND TMSI REALLOCATION COMPLETE RESERVE CIRCUIT RESERVE CIRCUIT SETUP CALL CONFIRMED PREPARE BEARER PREPARE BEARER RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE BEAR ESTABLISHMENT RAB ASSIGNMENT RESPONSE ALERTING SENT TONE SENT TONE CONNECT STOP TONE STOP TONE CONNECT ACKNOWLEDGE CONNECT ACKNOWLEDGE ANC RAB ASSIGNMENT REQUEST GMSC server PSTN IAI(TUP) ACM CALL DISCONNECT RELEASE RELEASE COMPLETE IU RELEASE COMMAND BEARER RELEASE IU RELEASE COMPLETE RELEASE_TERM RELEASE_TERM RELEASE_TERM RELEASE_TERM RLG CLF Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-13 .

If the callee hangs up first. 3. The VMSC server sends an IU Release Command message on initiative. The RNS creates the ATM bearer resources at the access side together with the MGW through bearer establishment. and requests the MSRN of the callee. 8. The network initiates authentication. 2. instructing it to play the ringback tone. the MSC server sends a Stop Tone message to the MGW. 17. 19. The callee picks up the phone. The MSC server then sends an RAB Assignment message to the RNS. 15. A transmission control panel and user panel must be created during assignment. The MSC/VLR must send a Command ID message to the RNS on not identifying the TMSI of the UE. The RAN sends the RAB Assignment response only after receiving an acknowledgement message of the creation of the user panel.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1. 18. The VMSC server creates the user panel bearer after receiving the Call Confirmed message from the called UE. During the process. The GMSC creates a signaling connection to the HLR and sends a request for routing. the network may obtain authentication set from the HLR/AuC. The called UE sends a Connect message to the MSC server after the callee picks up the phone. and sends a Send Tone message to the MGW. After the VMSC server receives the paging response from the called UE. 4. The VMSC server/VLR initiates paging to locate the callee after identifying the MSRN. The MSC server sends a Prepare Bearer request to the MGW. the HLR checks the subscription data of the callee. 11. 9. The VMSC sever creates a user panel bearer at the caller side at the same time. After receiving the request. The caller and callee begin to talk on the phone. 21. encryption and TMSI reassignment. The calling UE sends an RLG message to the VMSC server after the caller hangs up. 20. to obtain the IMSI of the UE. encryption and TMSI reassignment. 16. 5. the called UE sends a Disconnect message to the VMSC server. and finds the VLR and MSC server to which the callee currently belongs. The PSTN subscriber sends an IAI message containing the MSISDN of the callee to the GMSC server. The VMSC server releases transaction resources by sending a Release message to the called UE. The MSC server sends an ACM message to the calling UE after receiving an Alerting message. 14. The HLR creates a signaling connection to the VLR based on the VLR number. 7. and begins to release the resources on the signaling panel. 6. step 10 takes place immediately after step 8 if there is no requirement for authentication. instructing it to stop playing the ringback tone. 10. The VMSC server sends a Setup message to the called UE. The GMSC server sends the IAI message to the VMSC server/VLR based on the MSRN. 13. The VMSC server forwards a Connect ACK message to the called UE after receiving the message from the calling UE. The HLR forwards the MSRN to the GMSC server. The MSC server sends an ANC message to the calling UE after receiving the Connect message from the called UE. The VLR sends the MSRN of the callee to the HLR after finding the number. 1-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The VMSC server then sends a CLF message to the calling UE. Meanwhile. The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId. The GMSC server determines the HLR that the callee belongs to by analyzing the MSISDN. 12.

3 MMC Figure 1-5 shows the networking model of the call from a mobile subscriber to another mobile subscriber. The two messages are sent through the Iu interface and ISUP trunk respectively. The VMSC server releases resources on the user panel after sending two Release Termination messages to the MGW. Figure 1-5 Networking model of a call from a mobile subscriber to another mobile subscriber MSC server/VLR RNS-O MGW RNS-T UE-O UE-T Figure 1-6. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-15 .4.HUAWEI MSOFTX3000 Feature Description 1 Speech Service 22. 1. The two subscribers are both in the local office. Figure 1-7and Figure 1-8 show the flow of the call from a mobile subscriber to another mobile subscriber.

1 Speech Service HUAWEI MSOFTX3000 Feature Description Figure 1-6 Flow of the call from a mobile subscriber to another mobile subscriber (1) UE-O RNS-O CM_Service_Req (Initial UE) MAP_SEND_AUTHENTICATION_INFO MAP_SEND_AUTHENTICATION_INFO_ACK Security management (optional) AUTHENTICATION REQUEST AUTHENTICATION RESPONSE SECURITY MODE COMMAND(OPTION) SECURITY MODE COMPLETE(OPTION) COMMON ID CM_SERVICE_ACCEPT SETUP CALL PROCEEDING MSC server/VLR MGW HLR PREP BEARER PREP BEARER RAB ASSIGNMENT REQUEST Creation of a user panel bearer at the caller side RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE BEARER ESTABLISHMENT RAB ASSIGNMENT RESPONSE 1-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

HUAWEI MSOFTX3000 Feature Description 1 Speech Service Figure 1-7 Flow of the call from a mobile subscriber to another mobile subscriber (2) HLR MGW MSC server/VLR RNS-T UE-T MAP_SEND_ROUTING_INFORMATION Obtaining the roaming number MAP_PROVIDE_ROAMING_NUMBER MAP_PROVIDE_ROAMING_NUMBER_ACK MAP_SEND_ROUTING_INFORMATION_AC K PAGING PAGING PAGING RESPONSE AUTHENTICATION REQUEST Security management (optional) AUTHENTICATION RESPONSE SECURITY MODE COMMAND SECURITY MODE COMPLETE COMMON ID SETUP CALL CONFIRMED PREP BEARER PREP BEARER RAB ASSIGNMENT REQUEST Creation of a user panel bearer at the callee side RADIO BEARER SETUP RADIO BEARER SETUP COMPLETE BEARER ESTABLISHMENT RAB ASSIGNMENT RESPONSE Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-17 .

1 Speech Service HUAWEI MSOFTX3000 Feature Description Figure 1-8 Flow of the call from a mobile subscriber to another mobile subscriber (3) UE-O RNS-O VMSC/GMSC ALERTING MGW RNC-T UE-T SENDTONE SENDTONE CONNECT STOP TONE STOP TONE CONNECT CONNECT ACK During the call DISCONNECT RELEASE RELEASE COMPLETE IU_RELEASE_COMMAND DISCONNECT BEARER RELEASE IU_RELEASE_COMPLETE RELEASE_TERM RELEASE_TERM RELEASE RELEASE COMPLETE IU_RELEASE_COMMAND BEARER RELEASE IU_RELEASE_COMPLETE RELEASE_TERM RELEASE_TERM 1-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

The difference between early assignment and late assignment lies in the chance of assigning traffic channels (TCHs). encryption.HUAWEI MSOFTX3000 Feature Description 1 Speech Service The MSC server is combined with the VLR. 7. The VLR initiates paging immediately after the MSC server requests the incoming call data from the VLR. A user panel bearer begins to be created at the caller side. the network may obtain authentication set from the HLR/AuC. The MSC server queries route information in the HLR. For details. which consists of authentication. After the service acceptance message is received or the encryption is complete. After receiving the Setup message. The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment. 3. The MSC server sends a Prepare Bearer request to the MGW. 6. The CM Service request consists of the following parameters: mobile identification Its values are as follows − − − IMSI TMSI IMEI classmark2 CKSN CM service request type Its values are as follows: − − − − − MOC creation Emergency call creation Short message service Supplementary service Location service 2. This step takes place together with step 5. Therefore the B interface is an internal interface and the messages through the B interface are internal messages. 5. The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId (T1). The UE sends a CM Service request to the MSC server. The MSC server then sends an RAB Assignment message to the RNS-O. the MSC server returns a Call Proceeding message to the calling UE. 4. The network may initiate authentication and encryption. Step 3 takes places immediately after step 1 if there is no security management. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-19 . see Table 1-6. During the process. the UE sends a Setup message to the MSC server. Flow at Caller Side (Early Assignment) 1. TMSI reassignment and identity obtaining. The HLR requests the MSRN from the VLR.

thus improving the usage of TCHs. step 3 takes place immediately after step 1. The caller and callee begin to talk on the phone. The MSC server sends a Setup message to the called UE. 1-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) . encryption and TMSI reassignment. If no authentication is required. That is. The calling UE sends a Release Complete response after receiving the Release message. The called UE releases transaction resources by sending a Release message to the VMSC/GMSC. 8. The VMSC server forwards a Connect message to the calling UE after receiving the Connect message from the called UE. During the process. 3. 3. 5. A transmission control panel and user panel must be created during assignment. the network may obtain the authentication set from the HLR/AuC. Prevents TCHs from being occupied during ringing. Q. The RAN sends the RAB Assignment response only after receiving an Establish Confirm message. 10. Flow at Callee Side (Early Assignment) 1. which then forwards the message to the called UE. The MSC server creates user panel bearer after receiving a Call Confirmed message from the called UE. Refers to assigning TCHs after the MSC receives the Call Confirmed message. 9. thus improving the call connection ratio. Late Assignment Refers to assigning TCHs after the Alerting message. 2. Call Disconnection 1. The creation process is similar to that of the ATM bearer at the caller side. The network may initiate authentication. 4.1 Speech Service HUAWEI MSOFTX3000 Feature Description Table 1-6 Differences between early assignment and late assignment Early Assignment Chance of Assigning TCHs Caller Side Refers to assigning TCHs after the MSC sends a Call Proceeding message to the calling UE. 7. the MSC server sends a Stop Tone message to the MGW and instructs it to stop playing the ringback tone. the calling UE sends a Disconnect message to the MSC server/VLR. The MSC server receives a Paging response from the callee. After receiving the Connect message. The MSC server also sends a Send Tone message to the MGW and instructs it to play the ringback tone.AAL2 must be created and ISUP must be initiated. Callee Side Advantages Refers to assigning TCHs after the callee picks up the phone. The MSC server forwards an Alerting message to the calling UE after receiving the Alerting message from the called UE. Decreases call connection delay. The calling UE also sends a Connect ACK message to the MSC sever. The caller hangs up first. which then forwards the message to the called UE. 2. 6. At this moment. which then forwards the message to the calling UE and releases the transaction resources.

you can configure the type and number of an emergency call for special service on the local maintenance terminal. Repeat step 2 to add more types and numbers. The data to be configured involves the number analysis data.HUAWEI MSOFTX3000 Feature Description 1 Speech Service 4. you do not have to configure it again.2 Emergency Call for Special Service At the MSOFTX3000 side.5 Data Configuration 1. Table 1-7 lists the configuration steps. The number of emergency call for special service is configured based on the local situation. see the following manuals: HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide U-SYS UMG8900 Configuration Guide 1.3 Charging Flag of Emergency Call Run MOD CNACLD to modify the charging flag of an emergency call. The TARIFF parameter defines whether to charge for an emergency call. 1. After the configuration. If a number has been configured. the system can obtain the called number based on the type of the emergency call.1 Telephony The telephony is the elementary function of the UMTS. 5. Run ADD ESRVCAT to add a type and number of an emergency call for a special service.5.5. The VMSC/GMSC sends an IU Release Command message on initiative. Table 1-7 Configuration steps Step 1 2 3 Operation Run LST ESRVCAT to list the types and numbers of emergency calls for special services. 1. The values of TARIFF are as follows: Charging indication No charging No indication Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-21 . The VMSC/GMSC sends a Release Termination message to the MGW and releases resources on the user panel. and begins to release the resources on the signaling panel. when the speech service is opened.5. For how to configure the data.

You do not have to subscribe to the emergency call service at the HLR client. 1-22 Huawei Technologies Proprietary Issue 02 (2007-06-10) .6.7. The iGWB transfers the final CDRs to the charging center. The service is opened automatically when you open an account. 2. 3. The iGWB collects.7 Charging and CDR 1.6. 4. A is the caller and B is the callee. 1. 1. In addition.1 For Carriers Carriers can provide and cancel the speech service through the HLR client. Figure 1-9 shows the process of generating CDRs under this condition. sorts and transforms the original CDRs generated by the MSOFTX3000.7.1 Generation of CDR In each call. 1. It also provides an access interface for the charging center. The iGWB processes the original CDRs and generates final CDRs.6 Service Management 1. The CDRs are the basis for carriers to charge mobile subscribers. the MSOFTX3000 collects call data and generates CDRs. The MSOFTX3000 transfers the original CDRs to the iGateway Bill (iGWB) in real time. and stores the CDRs in the bill pool. see the manuals relevant to the HLR.2 CDR for Ordinary Call CDR for the Call Between Two Mobile Subscribers Under the Same VMSC A and B are mobile subscribers under the same VMSC. stores. generates original CDRs. This ensures that the correct CDRs are transferred to the charging center in time.2 For Mobile Subscribers There is nothing for mobile subscribers to do to manage the speech service. The management of carriers to the speech service consists of the following aspects: Providing the speech service Canceling the speech service For the details on configuration steps and parameter description. The MSOFTX3000 collects call data.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1. 1. The PLMN carriers generate telecom CDRs based on the final CDRs. the iGWB transforms original CDRs to final CDRs based on subscriber requirements.

A is the caller and B is the callee. The TMSC forwards the call to the GMSC. CDR for the Call Between Two Mobile Subscribers Under Different VMSCs A and B are mobile subscribers under two VMSCs. VMSC A routes the call from A to the tandem MSC (TMSC). 3. Figure 1-11 shows the process of generating CDRs under this condition. Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-23 . The GMSC forwards the call to a switch in the fixed network. Figure 1-10 shows the process of generating CDRs under this condition. both of which belong to the local network. CDR for the Call from Mobile Subscriber to Fixed Line Subscriber A is a mobile subscriber and B is a fixed line subscriber. One is for the MOC and the charged subscriber is A. VMSC B generates a CDR for the MTC and the charged subscriber is B. Figure 1-10 Process of generating CDRs when the mobile caller and callee are under different VMSCs A VMSCA MOC VMSCB MOC B VMSC A generates a CDR for the MOC and the charged subscriber is A. The other is for the MTC and the charged subscriber is B. The call from A to B involves the GMSC. The process of call connection is as follows: 1.HUAWEI MSOFTX3000 Feature Description 1 Speech Service Figure 1-9 Process of generating CDRs when the mobile caller and callee are under the same VMSC A VMSC MOC MTC B The VMSC generates two CDRs. Figure 1-11 Process of generating CDRs when a mobile subscriber calls a fixed line subscriber B PSTN GMSC GWO TMSC TRANSIT VMSCA MOC A VMSC A generates a CDR for the MOC and the charged subscriber is A. 2.

3. TRANSIT record and GWO record are all defined by MOD GBILLCTRL. CDR for the Call from Fixed Line Subscriber to Mobile Subscriber A is a fixed line subscriber and B is a mobile subscriber. and then to the PSTN. For example. which is the reference for calculating the charge of occupied outgoing trunks between the wireless network and the fixed network. which is the reference for calculating the charge of occupied trunks in the local network. The GMSC obtains the MSRN of B. Figure 1-12 Process of generating CDRs when a fixed line subscriber calls a mobile subscriber A PSTN GMSC GWI TMSC TRANSIT VMSCA MTC B The GMSC generates a gateway incoming (GWI) record. and GWO records can be generated not only by the GMSC. VMSC B generates a CDR for the MTC and the charged subscriber is B. in practice. If the GMSC directly routes the call to the end office (without passing the TMSC). 4. 2. which is the reference for calculating the charge of occupied incoming trunks between the fixed network and the wireless network. TRANSIT records can be generated not only by the TMSC. The roaming record. no TRANSIT record is generated. If the end office directly routes the call to the GMSC (without passing the TMSC). no TRANSIT record is generated. The TRANSIT record and GWO record are defined by MOD GBILLCTRL. The TMSC generates a TRANSIT record. The call from A to B involves the GMSC. The GMSC generates a gateway outgoing (GWO) record.1 Speech Service HUAWEI MSOFTX3000 Feature Description The TMSC generates a transit (TRANSIT) record. The TMSC routes the call to the VMSC. if an end office directly connects to a switch in another network and acts as a gateway office. Figure 1-12 shows the process of generating CDRs under this condition. The GMSC routes the call to the TMSC after obtaining the MSRN. 1-24 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The switch in the fixed network sends an IAI message to the GMSC. That is. which is the reference for calculating the charge of occupied trunks in the local network. The process of call connection is as follows: 1. the end office can also generate GWO records after relevant data is configured.

Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-25 . The GMSCs in the two networks generate CDRs respectively for inter-network calculation. The CDR is stored in the iGWB and waits to be sent to the charging center.3 CDR for Emergency Call After a mobile station successfully originates an emergency call. the network identifies the subscriber through IMEI. Emergency call observation flag is set to True. GMSC 2 routes the call to VMSC 2 after obtaining the MSRN. The CDR consists of the source and destination of the call. the MSC server at the caller side generates a CDR for the emergency call. 1. VMSC 2 generates a CDR for the MTC and the charged subscriber is B. which is the reference for calculating the charge of occupied incoming trunks between the two wireless networks. The switch in the network of carrier W generates CDRs for B.7. The CDR for an emergency call is of the same format as an MOC bill.HUAWEI MSOFTX3000 Feature Description 1 Speech Service CDR for the Call Between Two Mobile Subscribers in Different Wireless Networks Subscriber B belongs to the wireless network of carrier W. The switch in the network of carrier Y generates CDRs for A. 2. TMSC 1 generates a TRANSIT record. which is the reference for calculating the charge of occupied outgoing trunks between the two wireless networks. and user identity. Figure 1-13 Process of generating CDRs when the mobile caller and callee are in different wireless networks GWI A VMSC1 MOC TMSC TRANSIT GMSC1 GWO ROAM GMSC2 VMSC2 MTC B VMSC 1 generates a CDR for the MOC and the charged subscriber is A. GMSC 1 routes the call to GMSC 2 that is in the network of carrier W. If a subscriber makes an emergency call without a SIM/USIM. Figure 1-13 shows the process of generating CDRs under this condition. Subscriber A belongs to the wireless network of carrier Y. GMSC 2 generates a GWI record. VMSC 1 routes the call to GMSC 1. and the service code is of an emergency call. The call from A to B involves GMSC 1 and GMSC 2. GMSC 1 generates a GWO record. 3. The process of call connection is as follows: 1.

The CUG service conflicts with the emergency call service. Note: CLIR = calling line identification restriction.0 1. ODB = operator determined barring.9. The ODB service does not prevent a subscriber from making an emergency call. Table 1-8 Interaction between the emergency call function and other services Services Emergency call and CLIR Emergency call and ODB Emergency call and CUG Interaction If the caller subscribes to the CLIR service.8 Service Interaction Table 1-8 lists the interaction between the emergency call function and other services.1 Speech Service HUAWEI MSOFTX3000 Feature Description 1. the calling number cannot be displayed on the phone of the callee.1 Protocols and Specifications The reference of the speech service is as follows: 3GPP TS 22. CUG = closed user group 1.6.9 Reference 1.2 Acronyms and Abbreviations Acronym/Abbreviation CK CLIR CUG GMSC GSM HLR IK IMEI IMSI ISDN MOC Full Name Cipher Key Calling Line Identification Restriction Closed User Group Gateway Mobile Switching Center Global System for Mobile Communications Home Location Register Integrity Key International Mobile Station Equipment Identity International Mobile Station Identity Integrated Services Digital Network Mobile Originated Call 1-26 Huawei Technologies Proprietary Issue 02 (2007-06-10) .101 4.9.

HUAWEI MSOFTX3000 Feature Description 1 Speech Service Acronym/Abbreviation MSC MSISDN MSRN MTC PLMN PSTN SGSN SIM TMSI UE UMTS USIM VLR Full Name Mobile Switching Center Mobile Station International ISDN Number Mobile Station Roaming Number Mobile Terminated Call Public Land Mobile Network Public Switched Telephone Network Serving GPRS Support Node Subscriber Identity Module Temp Mobile Subscriber Identifier User Equipment Universal Mobile Telecommunication Services UMTS Subscriber Identity Module Visitor Location Register Issue 02 (2007-06-10) Huawei Technologies Proprietary 1-27 .

............................1 Data Configuration of the MSOFTX3000 .......................................4....................................................................2-4 2.................................................5................2-9 2................2 Requirements for License ...........................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 2 Short Message Service .............................................................................................................................................................................................................2-13 2............................. 2-11 2..........................................................................2-9 2.....................................2-15 2.......2-6 2.....................3 SM MT Flow..2-17 2.....................................2-2 2..................................2......................................................................................................................................................................................................................................................................................................................................................1 Requirements for NEs.......................3 Benefits .................2 Definition ....1 Function Code......2-5 2..........3 Applicable Versions...................2-5 2.................................2-16 2.......................................................4 Service Flows ............................................................................1 MAP Flows Related to SMS .....................................1....................5 Data Configuration..........2-3 2......................................................................................................3 Working Principle............................................2-15 2........................2-6 2.......................................................................................7 Charging and CDR .............9.......................2 SM MO Flow .........................................................................2-14 2.....................................2 Short Message Transfer Path........4 Alert SMC Flows ................2-13 2.....2-4 2.....................................2 For Mobile Subscriber ...........1 For Carrier..............................................................................4.................4.........................................................................1.................1 Protocols and Specifications ..........................................................................................................................................................2-15 2.......................9 Reference .................2-1 2...................................................................................................2 Availability ......................................................................2-15 2...........................2-6 2........................................................................................6.........1 Networking Structure.................................3......................................2-2 2..........................................9.......................2-4 2.......................5......2........................................................................................................................................................2................................................................2-17 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ................................2-4 2.....2 Acronyms and Abbreviations ............................2 Data Configuration of the HLR..................................................................................................................................................................................................1 Service Description ........................................................................3................................................................................1......2-2 2......................................6 Service Management .......................................4....2-17 2...............6.........................................................................................................................................8 Service Interaction .............................

..........................................2-13 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ...............................................................2-7 Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow..........2-9 Figure 2-7 SM MT flow .................................................... 2-11 Figure 2-9 Flow of alert SMC – memory of MS ready ................2-8 Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow ..........................................................................2-8 Figure 2-6 SM MO flow..............................................................................................................................................................................................................................................................................................................2-10 Figure 2-8 Flow of alert SMC – mobile station reachable .....................................2-7 Figure 2-4 MAP_READY_FOR_SM flow ....................................................................................................................................................................................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 2-1 Location of the SMC in a mobile network................................2-12 Figure 2-10 Flow of alert SMC – SMS succeeds ...........................................................2-5 Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow ....................................................................

...........................................2-4 Table 2-2 HUAWEI CS product versions that support the SMS ...................................2-6 Table 2-5 Interaction between the SMS and other services .....................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 2-1 NEs required to realize the SMS ...........................2-16 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ......................................2-5 Table 2-4 Functions of NEs in the transmission of SMs.........................................................................................................................................................................2-4 Table 2-3 Functions of NEs in the transmission of SMs............................................

The service flow of the network when providing this feature. The protocols and specifications that this feature must comply with.3 Working Principle 2.5 Data Configuration 2.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 2 About This Chapter Section 2. and the benefits that carriers and mobile subscribers can obtain from this feature. and the version requirements of the NEs. The network elements (NEs) that are required for the feature.4 Service Flows 2. The functions of the NEs. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. and the acronyms and abbreviations of this chapter.7 Charging and CDR 2. 2. The data configurations that are required on the MSOFTX3000 and the UMG8900. Describes The function code. The relationships and restrictions between this feature and other services or features. function definition of this feature.1 Service Description 2. and networking requirements. whether Licenses are required.8 Service Interaction 2.6 Service Management 2. The charging and the generation of CDRs when the network provides this feature.2 Availability Short Message Service The following table lists the contents of this chapter.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-1 .

The PTP SMSs fall into two categories: SM MT service (TS21) SM MO service (TS22) This chapter describes only the PTP SMSs. and voices. A macro broadcast message can have up to 15 pages that are sent continuously. pictures. "Short" means that the length of information sent in the SMS is short.1.The information can be texts. The PTP SMS allows subscribers to send or receive SMs at any time. The broadcast SMS allows subscribers to receive public information periodically and selectively.1. 160 ASCII characters or 70 Chinese characters.1 Function Code Name Short message MO/PP (SMS-MO) Short message MT/PP (SMS-MT) Code WMFD-010201 WMFD-010202 2. A point to point (PTP) short message (SM) can have up to 140 bytes in size. that is. The SMSs fall into two categories: PTP SMSs and PTM SMSs.2 Definition The short message service (SMS) allows subscribers to send or receive information through the short message center (SMC). The following figure shows the process.2 Short Message Service HUAWEI MSOFTX3000 Feature Description 2. Short message delivery SMC report MS 2-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The PTM SMSs mainly refers to the cell broadcast SMSs. that is. Name Mobile-Terminated Short Message (SM MT) Definition It refers to a process in which the SMC sends an SM to the mobile station (MS) and the MS returns a report indicating success or failure of the SMS.1 Service Description 2. A broadcast SM can have 82 bytes per page. PTM is short for point to multipoint. 92 ASCII characters or 41 Chinese characters.

the VLR sends an SM ready alert with the cause as mobile subscriber reachable to the HLR if the VLR detects that the MS interacts with the network and the MNRF flag stored in the VLR indicates subscriber not reachable. Alert SMC – Memory Ready If the SMS in the SM MT flow fails because of MS memory overflow. information inquiry services. the MSC server sends a message indicating memory of MS ready to the HLR. 2. the SMC temporarily stores the SM that fails to be sent. The HLR sends an SM ready alert to the SMC specified in the MWD list. Short message submission SMC report MS Alert Service Centre (Alert SC) Alert SMC – Mobile Station Reachable If the SMS in the SM MT flow fails because of paging no reply or subscriber no answer. At the same time.1. containing the MSISDN of the callee and the address of the MO SMC. Upon receipt of the message. The following figure shows the process. At the same time.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service Name Mobile-Originated Short Message (SM MO) Definition It refers to a process in which the MS sends an SM to another MS through the SMC and the SMC sends a report indicating success or failure of the SMS to the MS. When the MS makes or receives a call.3 Benefits Beneficiary Carriers Description The SMS can help to provide value added services. If the MS deletes an SM and the memory released can be used to receive new messages. the MS sends a message indicating memory ready to the MSC server. The HLR stores the information in the MWD list and enables the Mobile Station Memory Capacity Exceeded Flag (MCEF). It also expands service types and improves the average revenue per user (ARPU). or re-registers with the network through a location update. The HLR receives the message and checks the MCEF. and services such as website SMS and pictures. The HLR stores the information in the message waiting data (MWD) list and enables the Mobile Station Not Reachable Flag (MNRF). the SMC sends an SM status report to the HLR. the SMC temporarily stores the SM that fails to be sent. the SMC sends an SM status report to the HLR.The VLR also enables the MNRF. Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-3 . containing the MSISDN of the callee and the address of the SMC.

2.1 Requirements for NEs The SMS is implemented through the interworking between the MS/UE.3 Applicable Versions Table 2-2 lists the HUAWEI circuit switched (CS) domain product versions that support the SMS. MSC = Mobile Switching Center. and the core network (CN). This eases information query and makes subscribers feel closer to carriers. Table 2-1 lists the network elements (NEs) that are required to realize the SMS. 2. and bank accounts.2. UE = User Equipment. Table 2-2 HUAWEI CS product versions that support the SMS NE MSC server MGW Product MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V200R002 and later versions 2-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . To use the SMS.2 Requirements for License The SMS is an optional feature of the radio access network (RAN) provided by Huawei Technologies Co. MGW = Media Gateway. Ltd. sports news. 2.2. (called Huawei in this manual). the radio access network (RAN)..2 Short Message Service HUAWEI MSOFTX3000 Feature Description Beneficiary Mobile subscribers Description The SMS can be used to send information. Table 2-1 NEs required to realize the SMS MS/UE √ BTS/N odeB √ BSC/R NC √ MSC Server √ MGW √ SGSN √ VLR √ HLR √ SMC √ MS = Mobile Station. weather reports. BSC = Base Station Controller. VLR = Visitor Location Register. both a License of the MSOFTX3000 and that of the SMC are required. HLR = Home Location Register. SMC = Short Message Center The symbol √ indicates that the NE is required. BTS = Base Transceiver Station. SGSN = Serving GPRS Support Node. RNC = Radio Network Controller.2 Availability 2. It can also be used to receive information such as stock prices. 2.

1 Networking Structure As a service processing system independent of the GSM/UMTS network. Table 2-3 lists the functions of the NEs in the transmission of SMs. After an SM is sent from the SMC to the MSC. Table 2-3 Functions of NEs in the transmission of SMs NE MSC Function After an SM is sent from the MS to the MSC through the RAN. Figure 2-1 Location of the SMC in a mobile network MSC/VLR SMC InfoX PSTN/ISDN/ PSPDN RAN HLR SGSN MSC/VLR: Mobile Switching Center/Visited Location Register SMC: Short Message Center RAN: Radio Access Network GGSN: Gateway GPRS Support Node ISDN: Integrated Services Digital Network GGSN Internet HLR: Home Location Register Infox: Infox Integrated Gateway SGSN: Serving GPRS Support Node PSTN: Public Switched Telephone Network PSPDN: Packet Switched Public Data Network In a CS core network.3. and PSPDN to transmit SMs from external short message entities (ESMEs) such as manual stations and automatic stations The SMC. brings together functions of the SMS-GMSC. VLR.3 Working Principle 2. the MSC obtains the routing and subscriber information from the VLR and forwards the SM to the MS through the RAN. the SMS system performs the following functions: Submitting. SMS-interworking MSC (IWMSC). the NEs related to the SMS system are the MSC. as the SMS system provided by Huawei.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 2. Figure 2-1 shows the location of the SMC in a mobile network. and HLR. and service center (SC). storing. Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-5 . ISDN. the MSC forwards the SM to the SMC. and forwarding SMs Interworking with the PSTN. SGSN.

Table 2-4 Functions of NEs in the transmission of SMs Network Access Mode SGSN Short Message Transfer Path GMSC -> SGSN -> MS If the SGSN fails to forward an SM to the MS. 2. After receiving an SM sent from the SMC. If there is no authentication set in the VLR. domain or the CS domain.2 Short Message Service HUAWEI MSOFTX3000 Feature Description NE VLR Function It authenticates the subscriber to whom the SMC sends an SM. 2-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . This 2. the MSC does not request basic subscriber information from the HLR when sending an SM. It provides routing for the MSC when the SMC sends an SM to the subscriber through the MSC. the MSC requests it from the HLR. In all other cases. If authentication is required when the MSC sends an SM. This is similar to the transfer means used in the GSM network.4. the MSC requests the authentication set from the VLR. HLR Before the SMC sends an SM. the SGSN forwards it to the SMC.2 Short Message Transfer Path When different network access modes are used. MSC GMSC -> VMSC -> MS 2.4 Service Flows An SM can be transferred through the packet switched (PS) section described signaling flows of the CS domain only. Table 2-4 lists the details. SGSN When an SM sent by the MS reaches the SGSN through the RAN.3. Thus. the SM can be routed to the MSC or SGSN. the SM transfer paths are different. the GMSC sends it to the VMSC. the SGSN forwards it to the MS through the RAN. Figure 2-2 shows the flow.1 MAP Flows Related to SMS MAP_SEND_ROUTING_INFO_FOR_SM The flow is started by the GMSC to query the location information (MSC number or SGSN number) of the subscriber from the HLR. the HLR searches the MSC that serves the subscriber.

the HLR saves the address of the SMC or the cause of MS not reachable to the MWD list. the HLR may return two numbers: an SGSN number and an MSC number. If the message sending fails. the HLR clears the MNRF and MCEF of the subscriber and starts the Alert_Service_Centre flow to the SMC specified in the MWD list. Figure 2-3 shows the flow. the HLR returns one number and whether the number is an SGSN number or an MSC number is determined by MOD SMDP. If the GMSC does not support the GPRS. MAP_REPORT_SM_DELIVERY_STATUS The flow is started by the GMSC to inform the HLR whether the SM sending succeeds or fails. the HLR clears the MCEF and starts the Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-7 .HUAWEI MSOFTX3000 Feature Description 2 Short Message Service Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow GMSC HLR MAP_SEND_ROUTING_INFO_FOR_SM MAP_SEND_ROUTING_INFO_FOR_SM_ACK If the GMSC supports the general packet radio service (GPRS). If the message sending succeeds. Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow GMSC HLR MAP_REPORT_SM_DELIVERY_STATUS MAP_REPORT_SM_DELIVERY_STATUS _ACK MAP_READY_FOR_SM The flow is started by the VLR/SGSN to inform the HLR that the MS memory is ready. Upon receipt of the message.

After the message is received. the HLR starts the MAP_ALERT_SERVICE_CENTRE flow to the SMC and informs the SMC to resend the SM to the subscriber if the MNRF/MNRG of the subscriber is not reachable and the address of the SMC exists in the MWD list. 2-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . If the HLR detects that the MCEF and the MNFG/MNRG of the subscriber are not enabled. location update flow. the HLR sets a timer. Figure 2-4 shows the flow. the MAP_Alert_Service_Centre message is sent from the HLR to the IWMSC logically. which shows that the MAP_REPORT_SM_DELIVERY message is not sent to the HLR. the HLR sets the flag bits of the MCEF and the MNFG/MNRG to 0.2 Short Message Service HUAWEI MSOFTX3000 Feature Description MAP_ALERT_SERVICE_CENTRE flow to the SMC if the address of the SMC exists in the MWD list. Figure 2-5 shows the flow. Figure 2-4 MAP_READY_FOR_SM flow VLR/SGSN HLR MAP_READY_FOR_SM MAP_READY_FOR_SM _ACK MAP_ALERT_SERVICE_CENTRE When processing the MAP_READY_FOR_SM flow. or GPRS location update flow. Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow HLR SMC MAP_ALERT_SERVICE_CENTRE MAP_ALERT_SERVICE_CENTRE_ACK As the SMC provides the functions of an IWMSC.

Short Message Acknowledgement(RP_ACK) The messages with "(*)" are applicable to the MSC only. If the local office does not support SM MO. the VMSC server directly sends a reject message (RP_ERROR) to the MS.ShortMessage Error (RP_ERROR) 3.MO_FORWARD_SHORT_MESSAGE_ACK (RP_ACK) 6. 1. the SMC sends an SM to the MS. not the SGSN. and sends the result to the VMSC server. the VMSC server sends a subscriber data check request to the VLR based on the MSISDN of the MS.4. ShortMessage (RP_Data) VMSC/SGSN VLR SMC 2. Upon receipt of the request.3 SM MT Flow In an SM MT flow. the SMC sends a message to the VMSC server or the SGSN to acknowledge the transparent transmission of the SM MO. Figure 2-6 shows an SM MO flow. 5.4.MO_FORWARD_SHORT_MESSAGE (RP_DATA) 5. 2. Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-9 . If yes. 2. 3. the VMSC server obtains the address of the SMC from the SM MO and transparently transmits the SM MO to the SMC. 4. Upon receipt of the message. Figure 2-6 SM MO flow MS 1. the SMC checks whether the data is valid. a subscriber uses the MS to send an SM to the SMC. Figure 2-7 shows an SM MT flow. Otherwise. The MS sends an SM to the VMSC server or the SGSN through the A/Iu interface.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 2. 6. the VMSC server or the SGSN sends the result of SM MO sending to the MS. The VLR checks the subscription information and whether the local office supports the SMS.2 SM MO Flow In the SM MO flow.SEND_INFO_FOR_MO_SMS (*) 7. The VMSC server analyzes the result.SEND_INFO_FOR_MO_SMS_ACK (*) 4. or it registers the outgoing call barring service. Upon receipt of the SMS request.

Upon receipt of the SM MT. The subscriber is deleted by the MSC server/VLR to which the subscriber roams. The HLR searches the information of the subscriber in the database and returns a message with a failure cause to the SMC if one of the following occurs: The subscriber does not exist.Short Message (RP_DATA) (11) Short Message Acknowledgemen t (RP_ACK) (12) MT_FORWARD_SHORT_MESSAGE_ACK(RP_ACK) The messages with "(*)" are applicable to the MSC only. the HLR returns a normal response to the SMC even if the MNRF and the MCEF are enabled. Carrier determined call barring – barring of all incoming calls or SMs MT The SM MT service is not supported. When the priority of the SM MT is high. Upon receipt of the routing information. the VMSC server sends a request for checking SM MT subscriber data to the VLR. 4. The MCEF is enabled. 5. 1. the SMC sends a transparent transmission request to the VMSC server.MT_FORWARD_SHORT_MESSAGE (RP_DATA) (4) SEND_INFO_FOR_MT_SMS (*) (5) PAGE/SEARCH_FOR_MOBILE_SUBSCRIBER (*) SMC (6)Page (7) Page response (8) PROCESS_ACCESS_REQUEST_ACK/ SEARCH_FOR_MOBILE_SUBSCRIBER_ACK (*) (9) SEND_INFO_FOR_MT_SMS_ACK (*) (10).2 Short Message Service HUAWEI MSOFTX3000 Feature Description Figure 2-7 SM MT flow MS VMSC/ SGSN VLR HLR (1) SEND_ROUTING_INFO_FOR_SM (2) SEND_ROUTING_INFO_FOR_SM_ACK (3). 2. The VLR checks the subscription data and mobility management status: 2-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Roaming is not allowed. If none of the preceding events occurs. the HLR sends the MSC number or the SGSN number to the SMC. the HLR returns a response. By using the MSC number. Upon receipt of the request. the SMC obtains the called number and uses it to request the routing information from the HLR. The MNRF is enabled. 3. not the SGSN.

Alert SC: Alert_Service_Centre Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-11 . the connections are maintained and (3). (8)(9)(10): Upon receipt of the response.4. The MS sends a response to the VMSC server. and (12) are repeated. After the process is complete. 7. (11)(12): After receiving the result from the MS. Figure 2-8 Flow of alert SMC – mobile station reachable MS MSC/ SGSN VLR HLR SMC (1) CM Service Req (**). that is. the VMSC server starts paging the entire area controlled by the MSC server. the VMSC server sends a failure response to the SMC. the VMSC server starts paging the MS in the specific location area. Page resp or Location Updating (2) Process_Access_Request/ Update_Location_Area (*) (3) Ready_For_SM/ Update_Location (4) Ready_for_SM_ack (5) Alert SC (6) Alert SC ack The flow (2) is not applicable to the SGSN. If there are multiple SMs. If the location area of the MS is unknown. (10). 9.4 Alert SMC Flows There are two scenarios: The activated MS re-alerts the SMC after the SMS fails because of mobile subscriber not reachable. 2. the VMSC server starts the subscriber access process. the MNRF is enabled. If no additional message is to be sent. The MS alerts the SMC when its memory is ready. 10. 8. If the location area of the MS is known. all connections are released. (11). the handset is powered off.HUAWEI MSOFTX3000 Feature Description − 2 Short Message Service If the subscriber cannot be paged because the subscriber does not support SM MT. Alert SMC – Mobile Station Reachable Figure 2-8 shows the flow. 11. the VMSC server sends the SM to the MS through the Iu interface. − − 6. The VMSC server pages the MS. or the roaming is not allowed. the RP-MMS exists in the transparent transmission request. the VMSC server sends it to the SMC.

If the VLR detects that the MNRF of the subscriber is enabled. sends an Alert_Service_Centre message to the SMC. Alert SMC – Memory of MS Ready Figure 2-9 shows the flow. The VLR checks subscriber data. The HLR sends the Alert_Service_Centre message to all SMCs specified in the MWD list. the HLR clears the MNRF. 2. 3. The MSC server sends an access request to the VLR if the MS makes or receives a call. it checks the dynamic data of the subscriber. 5. If the HLR receives a location update request and the MNRF in the dynamic data of the subscriber is enabled. the VLR clears the MNRF and informs the HLR that the SM is ready with the cause as mobile subscriber reachable. The MSC server sends an SM ready message with the cause as memory of MS ready to the HLR. 4. If the HLR receives the SM ready alert. The MS makes or receives a call or updates the location to re-connect with the network. The VLR directly sends a location update request to the HLR in the case of a location update flow. Upon receipt of the Alert_Service_Centre message. the SMC returns a response and tries to send SMs again. and sends a message to the VLR to acknowledge the sending of the SM ready alert. Figure 2-9 Flow of alert SMC – memory of MS ready MS MSC/ SGSN HLR SMC (1) SM memory capacity available (2) READY_FOR_SM (3) READY_FOR_SM_ACK (4) SM memory capacity available (5) ALERT_SERVICE_CENTRE (6) ALERT_SERVICE_CENTRE_ACK 1. If the MNRF is enabled.2 Short Message Service HUAWEI MSOFTX3000 Feature Description 1. the HLR clears it. and continues the location update flow. The MS sends a memory ready message to the MSC server through the Iu interface. Or the MSC server checks the data of the subscriber who updates the location if the MS updates the location. sends an Alert_Service_Centre message to the SMC. The HLR sends the Alert_Service_Centre message only when the MCEF of the MS is set to False. 2. 2-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

the HLR clears the MNRF and the MCEF and starts the Alert_Service_Centre flow to the SMC whose address is in the MWD list. Figure 2-10 shows the flow. The GMSC server sends an SMS succeeds message to the HLR. Upon receipt of the message. Upon receipt of the message. The SMC returns an Alert_Service_Centre_ACK message to the HLR. the HLR clears it. 4.5 Data Configuration The SMS is implemented through the signaling system. the MSC server returns a response to the MS. The HLR sends an Alert_Service_Centre message to the SMC.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 3. 3. you must configure the signaling and service data of the MSOFTX3000 for interworking with the SMC. the SMC returns a response and tries to resend the SM. 2. Therefore. the HLR checks the dynamic data of the subscriber. The timing of the SM resending upon SMS failure is controlled by the SMC through the resending interval setting.5. you must configure data only on the MSC server and the HLR. Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-13 . Alert SMC – SMS Succeeds If the SMS succeeds. Figure 2-10 Flow of alert SMC – SMS succeeds GMSC HLR SMC (1) REPORT_SM_DELIVERY_STATUS (Successful Transfer) (2) REPORT_SM_DELIVERY_ STATUS_ACK (3) ALERT_SERVICE_CENTRE (4) ALERT_SERVICE_CENTRE_ACK 1. the HLR returns a response. and sends an SM ready message to the VLR. 2.1 Data Configuration of the MSOFTX3000 To implement the SMS. not on the MGW. sends an Alert_Service_Centre message to the MSC server. 4. Upon receipt of the Alert_Service_Centre message. If the MCEF of the subscriber is enabled. Upon receipt of the message. 2.

2 Data Configuration of the HLR To implement the SMS. you must configure the signaling and service data of the HLR for interworking with the SMC. Adding SCCP Data To add SCCP data. ----End 2. proceed as follows: Step 1 Add an MTP destination signaling point (DSP) by using ADD N7DSP. For details about the configuration steps and parameter descriptions. Specify the GT group to which the SCCP GT group belongs during the configuration. Select a general global title. The local MSC. proceed as follows: Step 1 Add an SCCP DSP by using ADD SCCPDSP. Step 3 Add an SCCP GT group by using ADD SCCPGTG. for example. Add the MSC and SCCP management subsystem (SCMG) to the remote SMC. Set Numbering Plan to ISDN/telephony numbering Plan. refer to related HLR manuals. ----End Setting MAP Feature Configuration Step 1 Run LST MAPACCFG to see whether Support SMMO function and Support SMMT function are set to Yes. 2-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Therefore. Step 2 Add an MTP linkset by using ADD N7LKS.5. Step 2 Add an SCCP sub-system number by using ADD SCCPSSN. ----End For details about the configuration steps and parameter descriptions. You can set it to National network. Enter an SMC number such as 8613900007 as the GT address information. Step 2 If not. Step 4 Add an SCCP global title by using ADD SCCPGT. Step 3 Add an MTP route by using ADD N7RT. VLR. Select a network indicator based on the actual requirements. run SET MAPACCFG to set them to Yes. run LST SCCPSSN to list the values and there is no need to configure the data again. Step 4 Add an MTP link by using ADD N7LNK. SCMG are already configured in the office information data. Set Network indicator to a value based on the actual requirements from the SMC to the SCCP DSP.2 Short Message Service HUAWEI MSOFTX3000 Feature Description Adding MTP Data To add MTP data. refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

the number of the caller.1 For Carrier The following operations can be performed on an HLR client: Enable or Disable the SMS. the SMC address in E. For details. It is the actual length of an SM after decoding. contains the following elements: Number of bytes: It indicates the actual number of bytes of the UserPart in an SM.6. and the content of the SM. there is no difference between an IN subscriber and an The SMS uses signaling or voice channels to send characters. the charging flag. the iGWB sends the CDR files to the billing center through the TCP/IP connection.6.6 Service Management 2. Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-15 . 2. the VMSC server that serves the subscriber generates an SMS CDR for the callee. FTAM is short for File Transfer Access and Management Protocol. An SMS CDR. The SMS CDR contains the IMSI and MSISDN of the callee. the VMSC server that serves the subscriber who sends an SM generates an SMS CDR for the caller.164 format. the additional charging flag. SMS CDR of Callee When a subscriber receives an SM.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 2.164 format. List the path of an SM. the charging flag. and the content of the SM. Address of SMC: It indicates which SMC is used for communication.7 Charging and CDR Difference Between SMS CDR and Voice Call CDR In an SMS call detail record (CDR). the number of the caller. SMS CDR of Caller If an SM is successfully sent to the SMC. different from an ordinary voice call CDR. The SMS CDR contains the IMSI and MSISDN of the caller.2 For Mobile Subscriber The address of the SMC can be configured. The CDR files are saved in the iGWB. Modify the path of an SM. the additional charging flag. ordinary subscriber. refer to related operation manuals of the HLR. Based on FTAM or FTP. 2. the SMC address in E.

When the VLR sets the subscriber to IMSI detach. After the IMSI is attached. the SM is stored in the SMC. Handover No SM can be sent during an intra-MSC or inter-MSC handover. A handover request is rejected when an SM is being transmitted. If the SM is sent to a subscriber who is in IMSI detach state. the SMC tries to resend the SM.8 Service Interaction Table 2-5 shows how the SMS interacts with other services. a hot billing flag is generated for each SM sent or received. IMSI attach/IMSI detach It interacts with the SM MT service. 2-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . An SM can be sent after the handover is complete. When a subscriber subscribes to the hot billing service. 2. Based on FTAM or FTP. The hot billing flag provides the charging data for all services of a subscriber. It is immediately sent to the billing center. the subscriber is not reachable. It interacts with the SM MO service. the iGWB sends the CDR files to the billing center through the TCP/IP connection. Table 2-5 Interaction between the SMS and other services Service Call barring Interaction The SM MO service is related to the following services: Barring of all outgoing calls (BAOC) Barring of outgoing international calls (BOIC) Barring of outgoing international calls except those directed to the home PLMN (BOIC-exHC) The SM MT service is related to the following services: Barring of all incoming calls (BAIC) Barring of incoming calls when roaming outside the home PLMN country (BICRoam) Call forwarding Hot billing It does not interact with the SMS. The handover continues after the transmission of an SM is complete.2 Short Message Service HUAWEI MSOFTX3000 Feature Description The CDR files are saved in the iGWB.

9 Reference 2.9.2 Acronyms and Abbreviations Acronym/Abbreviation ARPU BAIC BAOC BICRoam BOIC BOIC-exHC Full Name Average Revenue Per User Barring of All Incoming Calls Barring of All Outgoing Calls Barring of Incoming Calls when Roaming Outside the Home PLMN Country Barring of Outgoing International Calls Barring of Outgoing International Calls except those directed to the Home PLMN Country External Short Message Entity Gateway GPRS Support Node Gateway Mobile Switching Center General Packet Radio Service Global System for Mobile Communications Home Location Register Integrated Services Digital Network Mobile Station Mobile Switching Center Mobile Station International ISDN Number Packet Switched Public Data Network Public Switched Telephone Network Radio Access Network Serving GPRS Support Node ESME GGSN GMSC GPRS GSM HLR ISDN MS MSC MSISDN PSPDN PSTN RAN SGSN Issue 02 (2007-06-10) Huawei Technologies Proprietary 2-17 .9.HUAWEI MSOFTX3000 Feature Description 2 Short Message Service 2.1 Protocols and Specifications MNRF: Mobile station Not Reachable Flag MNRG: Mobile station Not Reachable for GPRS flag GPRS MNRR: Mobile station Not Reachable Reason MCEF: Memory Capability Exceed Flag MWD-List: Message Waiting Data-List 2.

2 Short Message Service HUAWEI MSOFTX3000 Feature Description Acronym/Abbreviation SMC SM MT SM MO SMS UMTS Full Name Short Message Center Mobile-Terminated Short Message Mobile-Originated Short Message Short Message Service Universal Mobile Telecommunication Services 2-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

...........................................................................................................................................5 Data Configuration............................................................................................................................2 Operations by the Subscribers...........................3 Working Principle..........................................................................................................................................................3-3 3.....................................................5.....4.................................................................................3-7 3...............................1 CFU Service Flow.3-21 3.........................1 Service Description ..............................................................................4 CFNRc ...............................................3-18 3.......................................3 Benefits ...........................................3-13 3..3 Applicable Versions...........................2 Definition ..................1 CFU.......8 Service Interaction ............3-22 3.3....................................................................2 Service Flow Inside the System ....3-15 3..................................................................................3-32 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ............................................8.......................3-4 3.............................................................................................3-30 3........................3...3-22 3............................................3-24 3....3-19 3........................................4.................6......8................................................................................................................................................................................................1 Function Code.............................................................................................2 HLR Configuration ....................................2 CFB..............................................................................................2....3 CDR Creation Principles.............................................4....................................................................1 Operations by the Carriers ........................3-4 3................7.....................6 Service Management .......................3-24 3.............4 CFNRy Service Flow ................................3-21 3...........................3-18 3.....................8.............1 Requirements for NEs..................................................................................................................................................................1............................................................................................................................8.........................3-2 3...........7 Charging and CDR ........................3-2 3...................3-8 3....3-3 3..................1 Charging Principle ................4.........................................................................6........................................................................................3-18 3.............................................................................................................2 Difference Between CFU and CCF in Judging an International Call ..............................................1 Functions of the NEs..............2 Availability .............................2 Requirements for License ..7........................................................................................1..........1 MSOFTX3000 Data Configuration........................................................................................3-4 3...................................3-7 3.................................................................................................3-1 3...........................................3-2 3...........................................................................................................................3 CFNRy Service Flow .......................................................3-27 3......................................................................3-3 3...............5........4 Service Flow......................................................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 3 Call Forwarding Supplementary Service .................................................................3-19 3.......2 CFB Service Flow......3 CFNRy ................................................................................................................................................7.............1.....................................................3-18 3............................................................2.........2.......................................................................................3-4 3............................3-4 3...

.....1 Protocols and Specifications .....3-35 3.........................................2 Acronyms and Abbreviations ...........3-35 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .....................................................................................................Contents HUAWEI MSOFTX3000 Feature Description 3.......................................9............9 References ..............................................................9...............................................................................................3-35 3.

..............................................................3-9 Figure 3-6 UDUB service flow for a call forwarded to a PSTN subscriber ........................................................3-14 Figure 3-11 CFNRc service flow for call forwarded to a PSTN subscriber ...................3-22 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ................................3-7 Figure 3-4 CFU service flow for a call forwarded to a mobile subscriber ............................................................................................3-6 Figure 3-3 CFU service flow for a call forwarded to a PSTN subscriber.......................................3-12 Figure 3-9 CFNRy service flow for a call forwarded to a PSTN subscriber ......................HUAWEI MSOFTX3000 Feature Description Figures Figures Figure 3-1 GMSC-originated call forwarding service flow.........................................3-8 Figure 3-5 NDUB service flow for a call forwarded to a PSTN subscriber ...........................................3-5 Figure 3-2 VMSC-originated call forwarding service flow...............................................................3-13 Figure 3-10 CFNRy service flow for a call forwarded to a mobile subscriber.......................................................................................................3-17 Figure 3-13 Charging of the call forwarding services .............3-10 Figure 3-7 NDUB service flow for a call forwarded to a mobile subscriber.................................................... ....................................... 3-11 Figure 3-8 UDUB service flow for a call forwarded to a mobile subscriber.............................3-16 Figure 3-12 CFNRc service flow for the mobile forwarded-to subscriber ...............................................................................

......................3-27 Table 3-16 Service interaction between the CFB and other services......................................................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 3-1 Function code .........................................3-4 Table 3-6 Operation modes of the call forwarding service ..................................3-21 Table 3-12 All the CCF services .........................................................................3-2 Table 3-3 Benefits of the call forwarding services ............................................................................................................................................3-30 Table 3-18 Interaction between CFNRc and other services.........3-23 Table 3-14 Interaction between the CFU and other services ..............................................................................................3-20 Table 3-9 CFNRy service operations ......................................................................................................................................................................................................................................................................................................................................................................................................................3-20 Table 3-11 Operations applicable to all the call forwarding services ......................................................3-18 Table 3-7 CFU service operations ................................................................3-33 iv Huawei Technologies Proprietary Issue 02 (2007-06-10) ............................................................................................................................................3-3 Table 3-4 Related NEs ...............................................................................................................................................................3-19 Table 3-8 CFB service operations..........................................................................................3-21 Table 3-13 CDR creation principles .....................................................................................................................3-28 Table 3-17 Interaction between CFNRy and other services.........................................................3-20 Table 3-10 CFNRc service operation....................................3-3 Table 3-5 Applicable versions ..........................................................................3-24 Table 3-15 Interaction Between CUG and Call Forwarding..........................................................3-2 Table 3-2 Definitions of the call forwarding services..........................................................

The charging and the generation of CDRs when the network provides this feature. and the version requirements of the NEs. The network elements (NEs) that are required for the feature.6 Service Management 3. and the acronyms and abbreviations of this chapter. whether Licenses are required. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. 3.3 Working Principle 3. The relationships and restrictions between this feature and other services or features. and the benefits that carriers and mobile subscribers can obtain from this feature.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service 3 Call Forwarding Supplementary Service About This Chapter The following table lists the contents of this chapter.4 Service Flow 3. Section 3. and networking requirements.7 Charging and CDR 3. The service flow of the network when providing this feature. The protocols and specifications that this feature must comply with.9 References Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-1 .5 Data Configuration 3. The functions of the NEs.1 Service Description Describes The function code. The data configurations that are required on the MSOFTX3000 and the UMG8900.2 Availability 3. function definition of this feature.8 Service Interaction 3.

3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description 3. CFNRy. Table 3-2 Definitions of the call forwarding services Name CFU CFB Definition All the calls to a mobile subscriber are forwarded unconditionally to the third party. Table 3-1 Function code Name Call forwarding (CF) supplementary service Call forwarding unconditional (CFU) Call forwarding on mobile subscriber busy (CFB) Call forwarding on no reply (CFNRy) Call forwarding on mobile subscriber not reachable (CFNRc) Code WMFD-020100 WMFD-020101 WMFD-020102 WMFD-020103 WMFD-020104 3.1. Call forwarding services are divided into CFU. and CFNRc.1. or the subscriber. or a service platform such as the voice mailbox. the network.1 Service Description 3. Table 3-2 lists the definitions of the call forwarding services. PSTN.1 Function Code Table 3-1 lists the function codes of the call forwarding services. The CFB can be further divided into: Network determined user busy (NDUB) User determined user busy (UDUB) CFNRy The calls to a mobile subscriber are forwarded to the third party if the no reply timer expires. The calls to a mobile subscriber are forwarded to the third party if the subscriber is busy. the third party can be a subscriber in the PLMN. CFB.2 Definition Call forwarding service is used to forward the calls to a mobile subscriber to the third party according to the requirements of the carriers. ISDN networks. 3-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Here.

the subscriber can select the terminal and the site for answering a call. and the HLR work together to implement the call forwarding services. A subscriber can activate or deactivate the call forwarding services provided by the system through the mobile phones. the VLR.3 Benefits Table 3-3 lists the benefits of the call forwarding services. Table 3-3 Benefits of the call forwarding services Beneficiary Carrier Description The service can both bring added value to the carrier and improve the call connection success rate.1. The wireless channel allocation fails.1 Requirements for NEs The MSC server. Subscriber 3. The mobile station is powered off.2 Availability 3. 3. the calls to the mobile subscriber are forwarded to the third party.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service Name CFNRc Definition If the wireless connection between the network and a called mobile subscriber fails. In this way. The call quality is improved consequently. Table 3-4 lists the related NEs. The triggering conditions of the CFNRc service includes mainly: The mobile subscriber does not respond to the paging. The forwarding may occur in the network where the caller resides or the network that the callee resides.2. Table 3-4 Related NEs UE/MS √ NodeB/ BTS √ RNC/B SC √ MSC Server √ MGW √ SGSN VLR √ HLR √ Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-3 .

2 Requirements for License Call forwarding is a basic service of HUAWEI wireless core network. the system may determine whether to trigger the CFU or the CFNRc service and return the FTN to the GMSC. 3. Call forwarding triggering analysis The system determines which service to be triggered in this process. and billing. Table 3-5 Applicable versions Product MSC Server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V200R002 and later versions 3.3.3 Working Principle 3. 3. the MGW. The MGW is mainly used to load the announcement files related to the call forwarding services. 3.3.2.3 Applicable Versions Table 3-5 lists the applicable versions of the call forwarding service. Two steps need to be implemented on the HLR to ensure the normal operation of the call forwarding services: Call forwarding registration FTNs are analyzed and rectified in this step. For example. and the VLR work together to implement functions such as signaling processing.2 Service Flow Inside the System Based on the call forwarding types. announcement playing. The MSC server and the MGW work together to implement the announcement playing function. PSTN switches are used to process the calls forwarded to them and then route the calls to the destination PSTN terminal.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description The symbol √ represents that the NE is required to implement the service. the service flow inside the system can be divided into GMSC-originated forwarding and VMSC-originated forwarding. data analysis.2. You can use the service without acquiring a license.1 Functions of the NEs The MSC server. 3-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

6. 4. The HLR checks the authentication and subscription information of the callee. The GMSC server sets up the call to the forwarded-to subscriber based on the FTN. 3. 2.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service GMSC-Originated Forwarding The call forwarding services originated by the GMSC server after it has obtained the subscriber information from the HLR consists of: CFU CFNRc (when the called mobile subscriber is roaming in an area forbidding call forwarding or when the VLR number is unavailable. If the callee has subscribed to the CFU service or if the callee has subscribed to the CFNRc service and the call forwarding conditions are met. 5.) Figure 3-1 shows the GMSC-originated call forwarding service flow. An incoming call to the callee is routed to the GMSC server. Figure 3-1 GMSC-originated call forwarding service flow Caller (6) (5) (2) (3) HLR (4) (G)MSC Server Callee (1) Forwarded-to subscriber The GMSC-originated call forwarding service flow is as follows: 1. the HLR does not returns the MSRN but the forwarded to number (FTN) and the call forwarding causes directly to the GMSC server. The GMSC server determines the target subscriber based on the FTN and sends forwarding notification (if the callee has subscribed to the service to notify the caller when forwarding occurs) to the caller. VMSC-Originated Forwarding The call forwarding services originated by the serving MSC of the callee (subscriber B) consists of: CFB CFNRy Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-5 . The GMSC server requests the routing information from the HLR of the callee.

An incoming call to the callee is routed to the GMSC server. The VMSC server requests the subscription information of the callee from the VLR. the MS of the callee is powered off. For CFNRy. 3-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 4. 5. Figure 3-2 VMSC-originated call forwarding service flow Caller (5) (1) (2) (3) (4) HLR GMSC Server Callee (5) (6) (8) (9) VMSC VLR S erver Forwarded-to subscriber 用户 The VMSC-originated call forwarding service flow is as follows: 1. the VMSC server checks whether the conditions to trigger the call forwarding service are met. The HLR checks the authentication and subscription information of the callee. The triggering principles are as follows: − − − 7. The GMSC server requests the VMSC server of the callee to set up the call based on the MSRN.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description CFNRc (when wireless channel congestion occurs) Figure 3-2 shows the VMSC-originated call forwarding service flow. it also returns the value of the no reply timer. The CFNRy service is triggered if the no reply timer expires. 2. The CFB service is triggered if the callee is busy. The CFNRc service is triggered if the callee does not respond to the paging. The VLR returns the call forwarding service information to the VMSC server. 6. The HLR obtains the MSRN of the callee from the VLR. the VMSC server requests the FTN from the VLR. 3. 8. If the conditions for triggering a call forwarding service are met. The GMSC server requests the routing information from the HLR of the callee. After receiving the subscription information of the callee. or the channel allocation fails.

The GMSC server forwards the call based on the FTN.4. The CFU service subscription Forwarding to a PSTN Subscriber Figure 3-3 shows the CFU service flow for a call forwarded to a PSTN subscriber.4 Service Flow This chapter describes only the call forwarding which takes place before a MGW is selected. The GMSC sends the Info req message to the HLR. 2. 3. the call is routed to MSC Server B normally. If the subscriber has not registered to the CFU service.1 CFU Service Flow In CFU service. the HLR includes the FTN in the Info ack message and sends the message to the GMSC server. − On detecting that the callee has subscribed to and activated the CFU. The user plane bearing is established after the call is forwarding to different target offices. information is stored in the HLR.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service 9. Figure 3-3 CFU service flow for a call forwarded to a PSTN subscriber MSa/UEa GMSC Server Set-up Info request Info ack OR1:N Set-up Set-up HLRb MSC Server b PSTN OR1:Y Notification OR2:Y Info req: Information request OR1: Forwarding requested Info ack: Information acknowledge OR2: Notification to calling subscriber required The CFU service flow for call forwarded to a PSTN subscriber is as follows: 1. − Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-7 . If the Info ack message contains the information element Notification to calling party. the GMSC server sends the notification to the caller. The HLR returns the Info ack message to the GMSC. The VMSC server sets up the call to the forwarded-to subscriber based on the FTN. 3. the call is forwarded under any situation.

UDUB refers to the situation that the callee rejects the call after the MS of the callee rings. the GMSC server sends the notification to the caller. 3. The GMSC server forwards the call based on the FTN. 5. The HLR returns the Info ack message to the GMSC.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description 3. NDUB refers to the situation that there is no available 3-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . On detecting that the callee has subscribed to the CFU. 2. HLR C sends the Info ack message containing the routing information to the GMSC server.2 CFB Service Flow In CFB service.4. 4. The GMSC sends the Info request message to the HLR. the HLR includes the FTN in the Info ack message and sends the message to the GMSC server. 3. Forwarding to a Mobile Subscriber Figure 3-4 shows the CFU service flow for a call forwarded to a mobile subscriber. Figure 3-4 CFU service flow for a call forwarded to a mobile subscriber MSa/UEa GMSC Server Set-up Info request Info ack (FTN) OR1:N OR1:Y Set-up Info request Info Set-up Notification OR2:Y ack HLRb MSC Server b HLRc MSC Server c OR1: Forwarding requested Info request: Information request OR2: Notification to calling subscriber required Info ack: Information acknowledge The CFU service flow for a call forwarded to a mobile subscriber is as follows: 1. the GMSC server forwards the call to the PSTN subscriber based on the FTN directly. The GMSC server sends the Info request message to HLR C where the forwarded-to subscriber resides to request the routing information. the call is forwarded in network determined user busy (NDUB) or user determined user busy (UDUB) conditions. the GMSC sends the Set-up message to MSC server C. After receiving the routing information. If the call forwarding conditions are met. MSC server C is responsible for paging the target mobile subscriber. 7. 6. If the Info ack message contains the information element Notification to calling party.

HLR B sends the Info ack message containing the MSRN to the GMSC server. The GMSC server sends the Info req message to HLR B. 3. For the forwarded-to subscriber. 4. After receiving the Set-up message. the call is not affected if the CFB is activated. Figure 3-5 NDUB service flow for a call forwarded to a PSTN subscriber MSa/UEa GMSC Server HLRb VLRb MSC Serverb MSb LEc Set-up Info req Info ack Set-up Info req Page MS Busy Subscriber OR1:N Impossible Call Completion Connect to following address OR2:Y Notification OR3:Y Release Release OR1:Y Notification Set-up Info req: Information request NDUB: Network Determined User Busy OR2: Notification to forwarding subscriber required Info ack: Information acknowledge OR1: Call to be forwarded OR3: Notification to calling subscriber required The NDUB service flow for a call forwarded to a PSTN subscriber is as follows: 1.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service network resource. 2. 5. MSC server B sends a response message to VLR B and indicates that the call setup fails and the failure reason is subscriber busy through the information element user error in the response message. MS A sends the Setup message to the GMSC server. MSC server B sends the Info request message to VLR B to request the information about MS B. Forwarding to a PSTN Subscriber in NDUB Figure 3-5 shows the NDUB service flow for a call forwarded to a PSTN subscriber. The GMSC server sends the Set-up message to MSC server B. 6. 7. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-9 . VLR B sends the Page MS message containing the FTN to MSC server B.

3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description 8. If the subscriber has not registered to the CFB service. After MS B responds to the paging. MSC server B sends the Set-up message to MS B. After receiving the Set-up message. the call fails. The GMSC server sends the Info req message to HLR B. the UDUB service is triggered if the callee rejects the call. 3. HLR B sends the Info ack message to the GMSC server. 4. VLR B sends the Page MS message to MSC server B. go to step 9. 3-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 6. The GMSC server sends the Set-up message to MSC server B based on the routing information. After MS B rings. MSC server B sends the Info req message to VLR B to request the information about MS B. MS A sends the Setup message to the GMSC server. 9. If the subscriber has registered to the CFB service. Figure 3-6 UDUB service flow for a call forwarded to a PSTN subscriber MSa/UEa GMSC Server HLRb VLRb MSC Serverb MSb LEc Set-up Info req Info ack Set-up Info req Page MS Set-up UDUB Busy Subscriber OR1:N Impossible Call Completion Connect to following address OR2:Y Release Release OR1:Y Notification Set-up UDUB: User Determined User Busy OR1: Call to be forwarded Info-req: Information request LEc: Local Exchange c OR2: Notification to calling subscriber required Info-ack: Information acknowledge The UDUB service flow for a call forwarded to a PSTN subscriber is as follow: 1. 5. 7. MSC server B sends the Set-up message to the PSTN subscriber based on the FTN. Forwarding to a PSTN Subscriber in UDUB Figure 3-6 shows the UDUB service flow for a call forwarded to a PSTN subscriber. 2.

The NDUB service flow for mobile forwarded-to subscriber is as follows: Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-11 .HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service 8. 10. Figure 3-7 NDUB service flow for a call forwarded to a mobile subscriber MSa/UEa GMSC Serfer HLRb VLRb MSC Server b MSb HLRc MSC Server c Set-up Info req Info ack Set-up Info req Page MS Busy Subscriber Impossible Call Completion Release Release OR1:N Connect to following address OR1:Y Info-req Info-ack Set-up Notificatio n OR3:Y Notificatio n OR2:Y Info req: Information request NDUB: Network Determined User Busy OR2: Notification to forwarding subscriber required Info ack: Information acknowledge OR1: Call to be forwarded OR3: Notification to calling subscriber required The NDUB service flow for a call forwarded to a mobile subscriber is similar to the NDUB service flow for a call forwarded to a PSTN subscriber. Otherwise. the FTN and whether the caller and the callee is notified when forwarding occurs. MSC server B sends response message to VLR B and indicates that the call setup fails and that the failure reason is subscriber busy through the information element user error in the response message. go to step 12. The Page MS message sent from VLR B to MSC server B contains the information related to the forwarding. 9. for example. the call fails. MSC server B sends the Set-up message to the PSTN forwarded-to subscriber based on the FTN. Forwarding to a Mobile Subscriber in NDUB Figure 3-7 shows the NDUB service flow for call forwarded to a mobile subscriber. 11. If the callee has not subscribed to and activated the CFB service. The only difference lies in the call forwarding flow.

Forwarding to a Mobile Subscriber in UDUB Figure 3-8 shows the UDUB service flow for a call forwarded to a mobile subscriber. The only difference lies in the forwarding flow. 3-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . After HLR C sends the routing information (through Info ack) to MSC server B. Figure 3-8 UDUB service flow for a call forwarded to a mobile subscriber MSa/UEa GMSC Server HLRb VLRb MSC Server b MSb HLRc MSC Server c Set-up Info req Info ack Set-up Info req Page MS Set-up Busy Subscriber OR1:N Release Release OR1:Y Connect to following address Impossible Call Completion UDUB Info req Info ack Notificatio n Set-up OR2:Y Info req: Information request UDUB: User Determined User Busy OR2: Notification to calling subscriber required Info ack: Information acknowledge OR1: Call to be forwarded The UDUB service flow for a call forwarded to mobile subscriber is similar to the UDUB service flow for a call forwarded to a PSTN subscriber. The UDUB service flow for mobile forwarded-to subscriber is as follows: After receiving the FTN. MSC server B sends the Set-up message to MSC server C.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description After receiving the FTN. MSC server B sends the Set-up message to MSC server C. MSC server B requests the routing information (through the Info req message) from HLR C. After HLR C sends the routing information (through the Info ack message) to MSC server B. MSC server B requests the routing information (through the Info req message) from HLR C.

6. MSC server B requests the information of MS B from VLR B. 4. The GMSC server sends the Info req message to HLR B. 5.3 CFNRy Service Flow In CFNRy service. Forwarding to a PSTN Subscriber Figure 3-9 shows the CFNRy service flow for call forwarded to a PSTN subscriber. 2. MS A sends the Setup message to the GMSC server.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service 3. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-13 . Figure 3-9 CFNRy service flow for a call forwarded to a PSTN subscriber MSa/UEa GMSC Server HLRb VLRb MSC Server b MSb LEc Set-up Info req Info ack Set-up Info req Info ack Set-up Start timer Info-req Impossible Call Completion OR1:N Release Release Connect to OR1:Y following address OR2:Y Notification OR3:Y Set-up Call conf Time expires Notification Info req: Information request OR1: Call to be forwarded OR3: Notification to calling subscriber required Info ack: Information acknowledge OR2: Notification to forwarding subscriber required Call conf: Call confirmation The CFNRy service flow when the call is forwarded to a PSTN subscriber is as follow: 1. HLR B sends the Info ack message containing the routing information to the GMSC server. 3. VLR B sends the Info ack message to MSC server B. The GMSC server sends the Set-up message to MSC server B based on the routing information.4. all the calls of the basic service and certain other services are forwarded.

9. 3-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Figure 3-10 CFNRy service flow for a call forwarded to a mobile subscriber.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description 7. At the same time. MSC server B notifies VLR B that the no reply timer expires through the Info req message. the call is released. The GMSC server sends the Info req message to HLR B. a no reply timer is started on MSC server B. After MS B responds to the paging. which routes the call to the forwarded-to subscriber. VLR B determines whether to forward the call as follows: If there is no CFNRy service data. MSC server B starts the call release process. If the callee does not answer the call after the no reply timer expires. Forwarding to a Mobile Subscriber Figure 3-10 shows the CFNRy service flow for a call forwarded to a mobile subscriber. MSa/UEa GMSC Server HLRb VLRb MSC Server b MSb HLRc MSC Server c Set-up Info req Info ack Set-up Info req Info ack Set-up Call Conf Info Req Impossible Call Completion Connect to following address Release Release OR1:N OR1:Y Info req Info ack Set-up Notificatio n OR2:Y Notification OR3:Y Info-req: Information request Call conf: Call confirmation OR2: Notification to forwarding subscriber required Info-ack: Information acknowledge OR1: Call to be forwarded OR3: Notification to calling subscriber required The CFNRy service flow for a call forwarded to a mobile subscriber is as follows: 1. If there is CFNRy service data. VLR B forwards the data to MSC server B. 2. The MS A sends the Setup message to the GMSC server. − − 10. MSC server B pages MS B. 8.

1 “CFU Service Flow”. 5. the CFNRc service flow is initiated by the VMSC. The following CFNRc service flow takes the situation when the subscriber does not respond to the paging as an example. 3. VLR B forwards the data to MSC server B. 7. 6.4. the call is released. which routes the call to the forwarded-to subscriber. refer to section 3. At the same time. The GMSC-initiated CFNRc service flow is similar to the GMSC-initiated CFU service flow. If there is CFNRy service data. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-15 .4. The GMSC server sends the Set-up message to MSC server B. VLR B sends the Info ack message to MSC server B. 8. The MS of the callee is powered off. MSC server B starts the call release process. VLR B determines whether to forward the call as follows: − − 9.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service 3. After MS B responds to the paging.4 CFNRy Service Flow The CFNRc service is triggered in the following situations: The callee does not respond to the paging. MSC server B notifies VLR B through the Info req message. If there is no CFNRy service data. Forwarding to a PSTN Subscriber Figure 3-11 shows the CFNRc service flow for a call forwarded to a PSTN subscriber when the callee does not respond to the paging. The channel allocation fails. If the callee does not answer the call after the no reply timer expires. For detailed information. MSC server B requests the information of MS B from VLR B. a no reply timer is started on MSC server B. 4. HLR B sends the Info-ack message to the GMSC server. MSC server B pages MS B. In the following examples.

MS A or TE A sends the Set-up message to the GMSC server. 7. VLR B determines whether to forward the call.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description Figure 3-11 CFNRc service flow for call forwarded to a PSTN subscriber MSa/UEa GMSC Server HLRb VLRb MSC Server b MSb LEc Set-up Info req Info ack Provide Roaming No Roaming No Set-up Info req Page MS Absent Subscriber Impossible Call OR1:N Completion Paging No response Release Release OR1:Y Notification OR2:Y Connect to following address Set-up Info req: Information request OR1: Call to be forwarded LEc: Local Exchange c Info ack: Information acknowledge OR2: Notification to calling subscriber required The CFNRc service flow for a call forwarded to a PSTN subscriber when the callee does not respond to the call is as follows: 1. 9. 6. VLR B provides the roaming number to HLR B. VLR B sends the Page MS message to MSC server B. MSC server B pages MS B. 8. MSC server B returns page response to VLR B indicating the reason for no response is Absent Subscriber. 3-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . If the forwarding conditions are met. HLR B sends the Info ack message to the GMSC server. The GMSC server sends the Set-up message to MSC server B. If MS B does not respond to the paging. the call is released. MSC server B requests the information of MS B from VLR B. − − 10. the call is routed based on the CFNRc service data. 2. 3. HLR B sends the Provide Roaming Information message to VLR B. 5. If the forwarding conditions are not met. The GMSC server sends the Info request message to HLR B. 4.

VLR B sends Page MS to MSC server B. The GMSC server sends the Set-up message to MSC server B. 4. − − If the forwarding conditions are not met. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-17 . Figure 3-12 CFNRc service flow for the mobile forwarded-to subscriber MSa/UEa GMSC Server HLRb VLRb MSC Server b MSb HLRc MSC Server c Set-up Info req Provide Roaming No Roaming No Info ack Set-up Info req Page MS Absent Subscriber Impossible Call Completion Paging No response OR1:N Release Release OR1:Y Connect to following address Info req Info ack Set-up Notification OR2:Y Info req: Information request OR1: Call to be forwarded Info ack: Information acknowledge OR2: Notification to calling subscriber required The CFNRc service flow for the mobile forwarded-to subscriber when the callee does not respond to the paging is as follows: 1. the call is released. 7. MSC server B pages MS B. 5. MSC server B sends Info req to VLR B. VLR B determines whether to forward the call. If the forwarding conditions are met. the call is routed based on the CFNRc service data. 3. 6.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service Forwarding to a Mobile Subscriber Figure 3-12 shows the CFNRc service flow for the mobile forwarded-to subscriber when the callee does not respond to the paging. 2. MSC server B returns page response to VLR B with the reason of the no response as Absent Subscriber. If MS B does not respond to the paging. MS A or TE A sends the Set-up message to the GMSC server. The GMSC server sends the Info request message to HLR B. HLR B sends the Provide Roaming Number message to VLR B.

Its reverse operation is activation. A call forwarding service should be first provided. as shown in Table 3-6. The definition of each operation is as follows: Provisioning The operation is performed by the carriers.2 HLR Configuration Refer to the corresponding operation manuals of the HLR products for detailed operations. You need not to activate a call forwarding service separately. Its reverse operation is deregistration. Activation The operation is performed by the service providers.5. withdrawal.6 Service Management The management operations of the CF SS consists of provisioning. Table 3-6 Operation modes of the call forwarding service Mode Carrier Site HLR Service Provisioning. or the system. activation.5 Data Configuration 3.5. Its reverse operation is deactivation. For certain services. It makes a service available to the subscribers. and then registered before it can be used by the subscribers. 3-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The call forwarding service has two operation modes. and deregistration. Deregistration The operation is used to delete the information input in the HLR in the registration. Withdrawal The operation is performed by the carriers. The call forwarding services are activated once they are registered. deactivation and deregistration. Please refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide. 3. The operation is mainly used to input some dedicated supplementary service information. the subscribers. The operation makes the service ready for provisioning. It makes a service unavailable to the subscribers. registration. Its reverse operation is withdrawal. or the system. 3. Deactivation The operation is performed by the service providers. registration. Its reverse operation is registration.1 MSOFTX3000 Data Configuration The data configuration of CF SS for the MSOFTX3000 is complex. Registration The operation is performed by the carriers or the subscribers. withdrawal. the subscribers.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description 3. the registration process also activates the services. It is used to terminate the process started by the activation operation. Its reverse operation is provisioning.

and deregistration. deactivate. Table 3-7 lists the procedures of CFU service operations. Otherwise the registration may fail.2 Operations by the Subscribers Prerequisites The system has provided the call forwarding services to the subscribers.6. FN represents the FTN. or deregister a service. 3. activate. The subscriber dials *21# through the MS and then press the button used to send the information.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service Mode Subscriber Site MS Service Registration. registration. Operation Steps By dialing the service feature code through the MSs. The subscriber dials ##21# through the MS and then press the button used to send the information. activation. Table 3-7 CFU service operations Operation Registration (activating the service automatically) Deactivation: Activation Deregistration: Procedure The subscriber dials **21*FN# through the MS and then press the button used to send the information. When registering an international FTN through the MS. you should add a symbol + before the country code. Here. withdrawal. and deregistration of the call forwarding services. 3. An example of the correct number format is as follows: +8613912345678. mobile subscribers can register. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-19 . Table 3-8 lists the procedures of CFB service operations. the carriers can control the provisioning.6. deactivation.1 Operations by the Carriers Through operations in the HLR. The subscriber dials #21# through the MS and then press the button used to send the information.

67kg through the MS and then press the button used to send the information.39kg through the MS and then press the button used to send the information. The subscriber dials *27. Table 3-9 lists the procedures of CFNRy service operations.39kg through the MS and then press the button used to send the information. The subscriber dials *28. The subscriber dials ##30. The subscriber dials #28. FN represents the FTN. Table 3-9 CFNRy service operations Operation Registration (activating the service automatically) Deactivation: Activation Deregistration: Procedure The subscriber dials **61*FN# through the MS and then press the button used to send the information. The subscriber dials #30. 3-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) .67kg through the MS and then press the button used to send the information. The subscriber dials ##27. FN represents the FTN. Table 3-10 CFNRc service operation Operation Registration (activating the service automatically) Deactivation: Activation Procedure The subscriber dials **62*FN# through the MS and then press the button used to send the information. The subscriber dials *30.67kg through the MS and then press the button used to send the information. FN represents the FTN. Here. Table 3-10 lists the procedures of CFNRc service operations.12kg through the MS and then press the button used to send the information. Here. Here. The subscriber dials #27.12kg through the MS and then press the button used to send the information.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description Table 3-8 CFB service operations Operation Registration (activating the service automatically) Deactivation: Activation Deregistration: Procedure The subscriber dials **67*FN# through the MS and then press the button used to send the information.39kg through the MS and then press the button used to send the information.

T represents the value of the no reply timer. as shown in Figure 3-13.7 Charging and CDR 3. Table 3-11 Operations applicable to all the call forwarding services Operation Registration (for all the call forwarding services) Procedure The subscriber dials **002*DN*T# through the MS and then press the button used to send the information. T represents the value of the no reply timer. Deregistration (for all the call forwarding services) Table 3-12 All the CCF services Operation Registration (for all the CCF services) Procedure The subscriber dials **004*DN*T# through the MS and then press the button used to send the information. It ranges from 5 to 30 seconds.7.1 Charging Principle Assume that the caller is A. Here. After querying the information and status of subscriber B. Here. It ranges from 5 to 30 seconds. DN represents the FTN. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-21 . the callee is B. and the forwarded-to subscriber is C. the originating MSC (or GMSC) routes the call to the office where the subscriber C resides.12kg through the MS and then press the button used to send the information. DN represents the FTN. The subscriber dials ##002# through the MS and then press the button used to send the information.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service Operation Deregistration: Procedure The subscriber dials ##28. Table 3-11 lists the procedures of operations applied to all the call forwarding services. Deregistration: 3. The subscriber dials ##004# through the MS and then press the button used to send the information.

C is the callee. In the CCF service. the MSC server within the country initiates the call forwarding and sends the Set-up message to the MSC where the forwarded-to subscriber resides.3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description Figure 3-13 Charging of the call forwarding services Subscriber A MSC A MSC B Subscriber B GMSC MSC C Subscriber C Charging Principle: Subscriber B. 3. and CFNRc. In the CDR. not as a callee. and the forwarded-to subscriber is C. an FTN is considered as an international number if it is not a number within the country where the callee roams to. is charged as a caller. and A is the third party.3 CDR Creation Principles Assume that the caller is A. an FTN is considered as an international number if it is not a number within the country. 3-22 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the callee is B. Conditional Call Forwarding (CCF) consists of CFB. A separate CDR is created for the call forwarding service.7. The CDR creation principles are shown in Table 3-13. 3. In the CFU service.7. who has initiated the call forwarding. CFNRy. the MSC server that the subscriber roams to initiates the call forwarding and sends the Set-up message to the MSC where the forwarded-to subscriber resides. B is the caller. Therefore. In CCF.2 Difference Between CFU and CCF in Judging an International Call Call Forwarding (CF) refers to all the call forwarding services. CFU and CCF define international numbers differently for the charging of international roaming. The CFNRc service initiated by the GMSC judges an international number in the same way as the CFU service. In CFU.

with B as the caller. with B as the caller. A ROAM CDR with A as the caller and B as the callee is created at the GSM or UMTS gateway for trunk charging. and C as the third party. A is a PSTN subscriber and B and C are GSM/UMTS subscribers. and A as the third party. C as the callee. The GSM or UMTS gateway creates a GWO CDR with B as the caller and C as the callee. B as the callee. For subscriber B: The MSC where B resides creates a call forwarding CDR. C as the callee. B as the callee. The GSM or UMTS GWO creates a GWO CDR with B as the caller and C as the callee for trunk charging. The service feature indication is CALL_FORWARD_OTHER. and A as the third party.HUAWEI MSOFTX3000 Feature Description 3 Call Forwarding Supplementary Service Table 3-13 CDR creation principles Subscriber Type A. A and C are PSTN subscribers and B is a GSM or UMTS subscriber. C as the callee. and A as the third party. with B as the caller. The service feature indication is CALL_FORWARD_OTHER. B. C as the callee. Issue 02 (2007-06-10) Huawei Technologies Proprietary 3-23 . CDR Creation Principle For subscriber A: The MSC creates a Mobile Originated Call (MOC) CDR with the A as the caller. C as the callee. and A as the third party. and A as the third party. C as the callee. A and B are GSM/UMTS subscribers and C is a PSTN subscriber. For subscriber B: The GSM or UMTS gateway creates a call forwarding CDR. and C are GSM/UMTS subscribers and belong to the same MSC. The GSM or UMTS GWI creates a call forwarding CDR for B. and C as the third party. For subscriber A: The MSC where A resides creates a Mobile Originated Call (MOC) CDR. with A as the caller. with B as the caller. For subscriber C: The MSC creates a Mobile Terminated Call (MTC) CDR with B as the caller. and A as the third party. The service feature indication is CALL_FORWARD_OTHER. The service feature indication is CALL_FORWARD_OTHER. For subscriber B: The MSC creates a call forwarding CDR. A ROAM CDR with A as the caller and B as the callee is created at the GSM or UMTS incoming gateway for trunk charging. For subscriber C: The MSC where C resides creates a Mobile Terminated Call (MTC) CDR with B as the caller.

1 CFU Table 3-14 lists the interaction between the CFU and other services. CFU has no interaction with COLP. When the call is answered. however. That is. 3. the forwarded-to subscriber cannot display the MSISDN of the caller unless the forwarded-to subscriber has the override capability. the override capability can be invoked to display the forwarded-to number. the forwarded-to number will not be included in the call forwarding notification.8 Service Interaction This section describes the interaction between the call forwarding services and other services. The caller does not activate CLIP service. CFU and COLR The CFU and the COLR have the following interactions: If the forwarded-to subscriber subscribes to the COLR service. If the caller subscribes to the COLR service and has the override capability. To create ROAM CDRs.8. the caller cannot receive the call forwarding notification. 3-24 Huawei Technologies Proprietary Issue 02 (2007-06-10) .3 Call Forwarding Supplementary Service HUAWEI MSOFTX3000 Feature Description To create gateway CDRs. The forwarded-to subscriber subscribes to the CLIP service. When the call is answered. you need to set the General Bill Control table as follows: Execute the MOD GBILLCTRL command and select GWO and GWI in Ticket Control Flag. the number of the forwarded-to subscriber is not presented to the caller unless the forwarded-to subscriber has the override capability. the forwarded-to number will not be sent to the caller in the call forwarding notification. Table 3-14 Interaction between the CFU and other services Service CFU and CLIP Interaction The number of the caller is presented to the forwarded-to subscriber if: The call is forwarded. you need to set the General Bill Control as follows: Execute the MOD GBILLCTRL command and select ROAM in Ticket Control Flag. CFU and COLP If the callee forwards a call without notifying the caller. In other cases. if the caller subscribes to and activates CLIR. 3. CFU and CLIR The CFU has no interaction with the CLIR.

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Service CFU and CFB

Interaction The CFU has a higher priority over the CFB. The CFU and the CFB have the following interactions: If a subscriber activates the CFU first, the subscriber cannot activate the CFB at the same time. The system will prompt that the two services conflict. If a subscriber activates the CFB first, the subscriber can also activate the CFU. If a subscriber receives a call, and if the subscriber activates both the CFB and CFU, the call will be forwarded unconditionally to the forwarded-to number registered in the CFU instead of the forwarded-to number registered in CFB.

CFU and CFNRy

The CFU has a higher priority over the CFNRy. The CFU and the CFNRy have the following interactions: If a subscriber activates the CFU first, the subscriber cannot activate the CFNRy at the same time. The system will prompt that the two services conflict. If a subscriber activates the CFNRy first, the subscriber can also activate the CFU. If a subscriber receives a call, and if the subscriber activates both the CFB and CFNRy, the call will be forwarded unconditionally to the forwarded-to number registered in the CFU instead of the forwarded-to number registered in the CFNRy.

CFU and CFNRc

The CFU has a higher priority over the CFNRc. The CFU and the CFNRc have the following interactions: If a subscriber activates the CFU first, the subscriber cannot activate the CFNRc at the same time. The system will prompt that the two services conflict. If the subscriber activates the CFNRc first, the subscriber can also activate the CFU. If the subscriber receives a call, and if the subscriber activates both the CFB and CFNRc, the call will be forwarded unconditionally to the forwarded-to number registered in the CFU instead of the forwarded-to number registered in the CFNRc.

CFU and CW

The CFU has a higher priority over the CW. When the callee is busy, and when both the CW and CFU of the subscriber are activated, the incoming calls of the subscriber will be forwarded unconditionally and the state of the call will not be changed.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-25

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Service CFU and MPTY

Interaction The CFU has no interaction with the MPTY. For the caller: If a subscriber intends to set up MPTY with the subscriber that activates the CFU, the forwarded-to subscriber receives a notification and joins in the MPTY. For the forwarded-to subscriber: The forwarded-to subscriber can add an existing forwarded call to the MPTY.

CFU and CUG CFU and BAOC

See Table 3-15 for the interaction between the CFU and the CUG. The callee can not activate the CFU and the at the same time. If the callee activates the CFU, the BAOC cannot be activated. If the callee activates the BAOC, the CFU cannot be registered and activated.

CFU and BOIC

The CFU and the BOIC have the following interactions: If the callee activates the BOIC, registering of the CFU to an international number is rejected. If the callee registers an international number for the CFU, the callee cannot activate the BOIC.

CFU and BOIC-exHC

The CFUan the BOIN-exHC have the following interactions: If the callee activates the BOIC-exHC, the callee cannot register the CFU. If the subscriber activates the BOIC-exHC, the subscriber cannot register and activate the CFU service to the non-HPLMN numbers. If the subscriber activates the CFU forwarded to non-HPLMN numbers, the subscriber can not activate the BOIC-exHC.

CFU and BAIC

The callee cannot activate the CFU and the BAIC at the same time. If the callee activates the CFU, the callee cannot activate the BAIC. If the callee activates the BAIC, the callee cannot register and activate the CFU. If the call is forwarded to the subscriber who activates the BAIC, the call is rejected as any other incoming call.

CFU and BIC-ROAM

For the callee, the CFU has a higher priority over the BIC-ROAM. If the callee activates the BIC-ROAM, and if the callee registers or activates the CFU at the same time, the BIC-ROAM cannot be activated. If the callee activates the CFU, the callee cannot activate the BIC-ROAM at the same time. For the forwarded-to subscriber: If the call is forwarded to the subscriber who activates the BAIC, the call is rejected as any other incoming call.

3-26

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Table 3-15 Interaction Between CUG and Call Forwarding CUG Indication Type (from Network) Whether the Caller and Callee are in the Same CUG Attributes of the Callee CUG Subscribers not Allowed for Inter-Group Outgoing Calls InterGrou p Outgo ing Call Allow ed Inter-Group outgoing call not allowed Yes The call can be forwar ded. InterGroup Outgoing Call not Allowed CUG Subscribers Allowed for Inter-Group Outgoing Call Inte r-Gr oup Out goin g Call Allo wed The call can be forw arde d. Inter-Group Outgoing Call not Allowed Non-CUG Subscriber

The call is rejected.

The call is rejected

The call is rejected.

No Inter-Group outgoing call allowed Yes

The call is rejected. The call can be forwar ded. The call is rejected The call can be forw arde d. The call can be forwarded. The call can be forwarded.

No Normal call –

The call is rejected. The call is rejected.

The call can be forwarded. The call can be forwarded. The call can be forwarded.

3.8.2 CFB
Table 3-16 describes the service interaction between the CFB and other services.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-27

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Table 3-16 Service interaction between the CFB and other services Service CFB and CLIP Interaction The number of the caller is presented to the forwarded-to subscriber if: The call is forwarded. The caller does not activate the CLIR service. The forwarded-to subscriber subscribes to the CLIP service. CFB and CLIR The CFB has no interaction with the CLIR. That is, if the caller subscribes to and activates the CLIR, the number of the caller is presented to the forwarded-to subscriber unless the forwarded-to subscriber has the override capability. CFB and COLP If the callee forwards the call without notifying the caller, the caller cannot receive the call forwarding notification. When the call is answered, the number of the forwarded-to party is not presented to the caller unless the forwarded-to subscriber has the override capability. In other cases, the two services have no interaction. CFB and COLR The CFB and the COLR have the following interactions: If the forwarded-to subscriber subscribes to the COLR service, the forwarded-to number will not be sent to the caller in the call forwarding notification. If the caller subscribes to the COLR service and has the override capability, the forwarded-to number will not be included in the call forwarding notification. When the call is answered, however, the override capability can be invoked to display the forwarded-to number. CFB and CFU The CFU has a higher priority over the CFB. If a subscriber activates the CFU first, the subscriber cannot activate the CFB at the same time. The system will prompt that the two services conflict. If a subscriber activates the CFB first, the subscriber can also activate the CFU. If a subscriber receives a call, and if the both the CFB and CFU are activated , the call will be forwarded unconditionally to the forwarded-to number registered in the CFU instead of the forwarded-to number registered in the CFB. CFB and CW The CW has no interaction with the CFB. If the callee is busy owning to the network, the call will be processed as the CFB without notifying the callee. If the callee is busy, which is not caused by the network, the call will be connected to the callee. The callee decides whether to forward the call.

3-28

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Service CFB and MPTY

Interaction The CFU has no interaction with the MPTY. For the caller: If the callee intends to set up MPTY with the subscriber that activates the CFB, the forwarded-to subscriber receives a notification and joins in the MPTY. For the forwarded-to subscriber: The forwarded-to subscriber can use the forwarded call to set up the MPTY.

CFB and CUG CFB and AOC CFB and BAOC

See Table 3-12 for the interaction between the CFB and the CUG. The CFB has no interaction with the AOC. The callee cannot activate the CFB and the BAOC at the same time. If the callee activates the CFB, the BAOC cannot be activated in the same BSG. If the callee activates the BAOC, the CFB cannot be registered and activated in the same BSG.

CFB and BOIC

The CFB and the BOIC have the following interactions: If the callee activates BOIC, registering of the CFU and forwarded-to international number are rejected in the same BSG. If the callee activates the CFB forwarded to an international number (in the local PLMN), the callee cannot activates the BOIC in the same BSG. If the CFB is forwarded to a national number, and if the CFB and BOIC are activated at the same time, the CFB cannot be activated if the subscriber roams to other countries. If the subscriber roams back, the CFB can be activated.

CFB and BOIC-exHC

The CFB and the BOIC-exHC have the following interactions: In the same BSG, if the callee activates the BOIC-exHC, the CFB to a non-HPLMN international number cannot be registered or activated. In the same BSG, if the callee activates the CFB forwarded to a non-HPLMN international number, the BOIC-exHC cannot be activated. In the same BSG, if the callee activates the CFB forwarded to a national number or HPLMN number, the CFB and the BOIC-exHC can be activated in the same BSG. If the subscriber roams to other PLMN countries, the CFB cannot be activated. The CFB can be activated if the subscriber returns to HPLMN or the BOIC-exHC is deactivated.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-29

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Service CFB and BAIC

Interaction The callee cannot activate the CFB and the BAIC at the same time. In the same BSG, if the subscriber activates the CFB, the BAIC cannot be activated. In the same BSG, if the subscriber activates the BAIC, the CFB cannot be registered and activated.

CFB and BIC-ROAM

For the callee: In the same BSG, if the callee activates BIC-ROAM, and if the BIC-ROAM is operational, CFB cannot be registered and activated. In the same BSG, if the callee activates BAIC, CFB cannot be registered and activated. In the same BSG, if the subscriber activates BIC-ROAM, but the BIC-ROAM is in the activation barring state, the subscriber can register and activate CFB. If the BIC-ROAM changes to operational, the CFB cannot be activated. In the same BSG, if the subscriber roams outside the HPLMN, and if the subscriber registers and activates the CFB and the CFB is operational, the subscriber cannot activate the BIC-ROAM. In the same BSG, if the subscriber registers and activates the CFB and the CFB is in the activation barring state, and if the subscriber roams in the HPLMN, the subscriber can activate the BIC-ROAM. For the forwarded-to subscriber: The call that is forwarded to the subscriber that activates the operational BIC-ROAM is rejected as any other incoming call.

3.8.3 CFNRy
Table 3-17 lists interaction between the CFNRy and other services. Table 3-17 Interaction between CFNRy and other services Service CFNRy and CLIP Interaction If a call is forwarded, the calling number is presented to the forwarded-to subscriber who has registered the CLIP, if the CLIP of the caller is not activated. If a call is forwarded, the calling number is not presented to the forwarded-to subscriber unless the forwarded-to subscriber has the override capability, if the caller has subscribed to and activated the CLIR. If the callee forwards a call without notifying the caller, the calling number is not presented to the forwarded-to subscriber unless the caller has the override capability.

CFNRy and CLIR

CFNRy and COLP

3-30

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Service CFNRy and COLR

Interaction If the forwarded-to subscriber has subscribed to the COLP, the forwarded-to number is not sent to the caller along with the forwarding notification. If the caller has subscribed to the COLP and has the override capability, the forwarded-to number is not contained in the forwarding notification received. The forwarded-to number, however, is presented to the caller through the override capability when the call is answered.

CFNRy and CFU

The CFU has higher priority over the CFNRy. If the CFU is activated, activating the CFNRy fails, prompting that a conflict occurs. If the CFNRy is activated, activating the CFU succeeds. When a call is made to a subscriber whose CFNRy and CFU are activated, the call is forwarded based on the CFU instead of the CFNRy.

CFNRy and CW

When a call is made to a subscriber whose CFNRy and CW are activated, the subscriber receives the CW prompt, and forwards the call if the call is not answered within a specific period of time. The CFNRy and MPTY do not affect each other. Assume that the caller wants to set up a MPTY call with the callee. If the CFNRy of the callee is activated, the forwarded-to subscriber receives a prompt and connects to the conference, if the call is not answered. The forwarded-to subscriber can add an existing forwarded call to a MPTY call.

CFNRy and MPTY

CFNRy and CUG CFNRy and BAOC

Table 3-15 lists interaction between the CFNRy and CUG. The CFNRy and BAOC cannot coexist. For the callee: In the same BSG, if the CFNRy is activated, the BAOC cannot be activated. In the same BSG, if the BAOC is activated, the CFNRy cannot be registered or activated.

CFNRy and BOIC

For the callee: In the same BSG, if the BOIC is activated, the CFNRy to an international number cannot be registered or activated. In the same BSG, if the CFNRy to an international number (from a HPLMN network) is activated, the BOIC cannot be activated. In the same BSG, if the CFNRy to a national number is activated, the BOIC can be activated; if the CFNRy to an international number is activated, the CFNRy cannot be activated. If the BOIC is then deregistered or activated to a national number, the CFNRy can be activated.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-31

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Service CFNRy and BOIC-exHC

Interaction For the callee: In the same BSG, if the BOIC-exHC is activated, the CFNRy to an international number (except a HPLMN number) cannot be registered or activated. In the same BSG, if the CFNRy to a national number (except a HPLMN number) is activated, the BOIC-exHC cannot be activated. In the same BSG, if the CFNRy to a local number or HPLMN number is activated, the BOIC-exHC can be activated; if the CFNRy to another PLMN number is activated, the CFNRy cannot be activated. If the BOIC-exHC is then deregistered or activated to a HPLMN number, the CFNRy can be activated.

CFNRy and BAIC

For the callee: The CFNRy and BAOC cannot coexist. In the same BSG, if the CFNRy is activated, the BAIC cannot be activated. In the same BSG, if the BAIC is activated, the CFNRy cannot be registered or activated. For the forwarded-to subscriber: The call forwarded to a BAIC subscriber is rejected.

CFNRy and BIC-ROAM

For the callee: In the same BSG, if the BIC-ROAM is activated, the CFNRy cannot be registered or activated. In the same BSG, if the BIC-ROAM is not activated, the CFNRy can be registered and activated. But when the BIC-ROM is activated, the CFNRy automatically turns inactivated. In the same BSG, if the callee, whose CFNRy is registered and activated, roams outside of the HPLMN, the BIC-ROAM cannot be activated. In the same BSG, if the callee, whose CFNRy is not activated, roams inside of the HPLMN, the BIC-ROAM can be activated. For the forwarded-to subscriber: The call forwarded to a BIC-ROAM subscriber is rejected.

3.8.4 CFNRc
Table 3-18 lists interaction between CFNRy and other services.

3-32

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Table 3-18 Interaction between CFNRc and other services Service CFNRc and CLIP Interaction If a call is forwarded, the calling number is presented to the forwarded-to subscriber who has registered the CLIP, if the CLIP of the caller is not activated. If a call is forwarded, the calling number is not presented to the forwarded-to subscriber unless the forwarded-to subscriber has the override capability, if the caller has subscribed to and activated the CLIR. If the callee forwards a call without notifying the caller, the calling number is not presented to the forwarded-to subscriber unless the caller has the override capability. If the forwarded-to subscriber has subscribed to the COLP, the forwarded-to number is not sent to the caller along with the forwarding notification. If the caller has subscribed to the COLP and has the override capability, the forwarded-to number is not contained in the forwarding notification received. The forwarded-to number is presented to the caller through the override capability when the call is answered. CFNRc and CFU The CFU has higher priority over the CFNRc. If the CFU service is activated, activating the CFNRc fails, prompting that a conflict occurs. If the CFNRc is activated, activating the CFU succeeds. When a call is made to a subscriber whose CFNRc and CFU are activated, the call is forwarded based on the CFU instead of the CFNRc. CFNRc and MPTY The CFNRc and MPTY do not affect each other. Assumes that the caller wants to set up a MPTY call with the callee. If the CFNRc of the callee is activated, the forwarded-to subscriber receives a prompt, and connects to the conference if the callee is not reachable. The forwarded-to subscriber can add an existing forward call to a MPTY call. CFNRc and CUG CFNRc and AOC CFNRc and BAOC Table 3-15 lists interaction between the CFNRc and CUG. There is no interaction between CFNRc and AOC For the callee: In the BSG, the CFNRc and BAOC cannot coexist. In the same BSG, if the CFNRc is activated, the BAOC cannot be activated. In the same BSG, if the BAOC is activated, the CFNRc cannot be registered or activated.

CFNRc and CLIR

CFNRc and COLP

CFNRc and COLR

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-33

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Service CFNRc and BOIC

Interaction For the callee: In the same BSG, if the BOIC service is activated, the CFNRc to an international number cannot be registered or activated. In the same BSG, if the CFNRc to an international number (from a HPLMN network) is activated, the BOIC service cannot be activated. In the same BSG, if the CFNRc to a national number is activated, the BOIC can be activated; if the CFNRc to an international number is activated, the CFNR cannot be activated. If the BOIC is then deregistered or activated to a national number, the CFNRc can be activated.

CFNRc and BOIC-exHC

For the callee: In the same BSG, if the BOIC-exHC is activated, the CFNRc to an international number (except a HPLMN number) cannot be registered or activated. In the same BSG, if the CFNRc to a national number (except a HPLMN number) is activated, the BOIC-exHC cannot be activated. In the same BSG, if the CFNRc to a local number or HPLMN national number is activated, the BOIC-exHC can be activated; if the CFNRc to another PLMN number is activated, the CFNRc cannot be activated. If the BOIC-exHC service is then deregistered or activated to a HPLMN number, the CFNRc service can be activated.

CFNRc and BAIC

For the callee: The CFNRc and BAiC cannot coexist. In the same BSG, if the CFNRc is activated, the BAIC cannot be activated. In the same BSG, if the BAIC is activated, the CFNRc cannot be registered or activated. For the forwarded-to subscriber: The call forwarded to a BAIC subscriber is rejected.

3-34

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Service CFNRc and BIC-ROAM

Interaction For the callee: In the same BSG, if the BIC-ROAM is activated, the CFNRc cannot be registered or activated. In the same BSG, if the BIC-ROAM is registered but not activated, the CFNRc can be registered and activated. But when the BIC-ROM is activated, the CFNRy automatically turns inactivated. In the same BSG, if the callee, whose CFNRc is registered and activated, roams outside of the HPLMN, the BIC-ROAM cannot be activated. In the same BSG, if the callee, whose CFNRc is registered but not activated, roams inside of the HPLMN, the BIC-ROAM can be activated. For the forwarded-to subscriber: The call forwarded to a BIC-ROAM subscriber is rejected.

3.9 References
3.9.1 Protocols and Specifications
3GPP TS 22.082 V4.2.0 (2002-03) 3GPP TS 23.082 V4.3.0 (2002-06)

3.9.2 Acronyms and Abbreviations
Acronym/Abbreviation CFU CFB CFNRy CFNRc Full Name Call Forwarding Unconditional Call Forwarding Busy Call Forwarding No Reply Call Forwarding on mobile subscriber Not Reachable

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-35

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
4 Line Identification Service .......................................................................................................4-1
4.1 Service Description .......................................................................................................................................4-2 4.1.1 Function Code......................................................................................................................................4-2 4.1.2 Definition .............................................................................................................................................4-2 4.1.3 Types ....................................................................................................................................................4-3 4.1.4 Benefits ................................................................................................................................................4-4 4.2 Availability ....................................................................................................................................................4-4 4.2.1 Requirements for NEs..........................................................................................................................4-4 4.2.2 Requirements for License ....................................................................................................................4-5 4.2.3 Applicable Versions..............................................................................................................................4-5 4.3 Working Principle..........................................................................................................................................4-5 4.3.1 Service Data Management ...................................................................................................................4-5 4.3.2 CLIP.....................................................................................................................................................4-5 4.3.3 CLIR ....................................................................................................................................................4-5 4.3.4 COLP ...................................................................................................................................................4-6 4.3.5 COLR...................................................................................................................................................4-6 4.4 Service Flow..................................................................................................................................................4-6 4.4.1 CLIP.....................................................................................................................................................4-6 4.4.2 CLIR ....................................................................................................................................................4-7 4.4.3 COLP ...................................................................................................................................................4-8 4.4.4 COLR...................................................................................................................................................4-8 4.5 Data Configuration........................................................................................................................................4-9 4.5.1 Configuring Data at the MSOFTX3000 Side.......................................................................................4-9 4.5.2 Configuring Data at the HLR Side..................................................................................................... 4-11 4.6 Service Management ................................................................................................................................... 4-11 4.6.1 Opreations by Carriers ....................................................................................................................... 4-11 4.6.2 Operations by Mobile Subscribers ..................................................................................................... 4-11 4.7 Service Interaction ......................................................................................................................................4-12 4.7.1 CLIP...................................................................................................................................................4-12 4.7.2 CLIR ..................................................................................................................................................4-13 4.7.3 COLP .................................................................................................................................................4-13 4.7.4 COLR.................................................................................................................................................4-14

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i

Contents

HUAWEI MSOFTX3000 Feature Description

4.8 Reference ....................................................................................................................................................4-14 4.8.1 Protocols and Specifications ..............................................................................................................4-14 4.8.2 Acronyms and Abbreviations .............................................................................................................4-15

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Figures

Figures
Figure 4-1 CLIP service flow .............................................................................................................................4-6 Figure 4-2 CLIR service flow.............................................................................................................................4-7 Figure 4-3 COLP service flow............................................................................................................................4-8 Figure 4-4 COLR service flow ...........................................................................................................................4-8

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

Tables

HUAWEI MSOFTX3000 Feature Description

Tables
Table 4-1 Names and codes of functions ............................................................................................................4-2 Table 4-2 Beneficiaries and description of the benefits ......................................................................................4-4 Table 4-3 NEs required by the line identification services .................................................................................4-4 Table 4-4 Applicable versions of Huawei wireless core network products ........................................................4-5 Table 4-5 Operation modes of the line identification services.......................................................................... 4-11 Table 4-6 CLIR service operation performed by mobile subscribers ...............................................................4-12 Table 4-7 Interactions between the CLIP service and other services................................................................4-12 Table 4-8 Interactions between the CLIR service and other services ...............................................................4-13 Table 4-9 Interactions between the COLP service and other services ..............................................................4-13 Table 4-10 Interactions between the COLR service and other services............................................................4-14

iv

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

4
About This Chapter
Section 4.1 Service Description 4.2 Availability

Line Identification Service

The following table lists the contents of this chapter. Describes The function code, function definition of this feature, and the benefits that carriers and mobile subscribers can obtain from this feature. The network elements (NEs) that are required for the feature, whether Licenses are required, and the version requirements of the NEs. The functions of the NEs, and networking requirements. The service flow of the network when providing this feature. The data configurations that are required on the MSOFTX3000 and the UMG8900. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The relationships and restrictions between this feature and other services or features. The protocols and specifications that this feature must comply with, and the acronyms and abbreviations of this chapter.

4.3 Working Principle 4.4 Service Flow 4.5 Data Configuration 4.6 Service Management

4.7 Service Interaction 4.8 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-1

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

4.1 Service Description
4.1.1 Function Code
Table 4-1 lists the names and codes of the functions. Table 4-1 Names and codes of functions Name CLIP CLIR COLP COLR Code WMFD-020301 WMFD-020302 WMFD-020303 WMFD-020304

Note: CLIP = Calling Line Identification Presentation; CLIR = Calling Line Identification Restriction; COLP = Connected Line Identification Presentation; COLR = Connected Line Identification Restriction

4.1.2 Definition
Line identification services are classified into two types: One is supplementary services that provide and restrict connected line identification for callers; the other is services that provide and restrict calling line identification for callees. Line Identity (LI) consists of the following information: ISDN/MSISDN number of subscriber Subaddress information (optional). The Public Land Mobile Network (PLMN) is not responsible for the content of subaddress. Calling Line Identity (CLI) identifies callers and Connected Line Identity (COL) identifies connected parties that refer to callees communicating with callers lastly. For common calls, connected parties indicate callees. For forwarding calls, forwarding target parties indicates callees. In some special applications, callers/callees are provided with additional CLI (aCLI) and additional COL (aCOL). When sending LI or additional Line Identity (aLI), the network additionally sends Presentation Indicator (PI) and Screening Indicator (SI): PI
− − −

Presentation allowed Presentation restricted Number not available due to interworking User provided, verified and passed User provided, not screened Network provided

SI
− − −

4-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

if the PI value of a caller is Restrict providing. the system processes according to the CLIP when service conflict occurs. If a subscriber is a callee. Therefore. But if Override Category of the CLIP is Enable. CLIR CLIR is a supplementary service provided for callers. the service restricts that connected line identification is provided for callers. when service conflict occurs. Temporary allowed mode: In default status. COLP and COLR. the COLR enjoys higher priority than the COLP. In general. But if Override Category of the COLP is Enable. Permanent mode: The CLIR service is invoked for every call. the CLIR service is invoked. Subscribers can suppress the CLIR service temporarily through the menus of some mobile phones. In general. service conflict occurs. Temporary restricted mode: In default status.1. CLIR. COLP COLP is a supplementary service provided for callers. COLR COLR is a supplementary service provided for callers. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-3 . The service provides calling line identification for callees. Name CLIP Definition CLIP is a supplementary service provided for callees. the CLIR service is not invoked.3 Types Line identification services are classified into CLIP. when a callee activates the CLIP and the caller activates the CLIR.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service In the Universal Mobile Telecommunications System (UMTS). the system processes according to the COLP when service conflict occurs. the system processes according to the COLR service. temporary allowed and temporary restricted modes. Carriers can provide the CLIR service for subscribers in permanent. when a caller activates the COLP and the callee activates the COLR. COLP and COLR are mutually exclusive. The service restricts that calling line identification is provided for callees. Subscribers can invoke the CLIR service temporarily through the menus of some mobile phones. Therefore. service conflict occurs. The service provides connected line identification for callers. the network may send Cause of No CLI. That is. Cause of No CLI − − − − Unavailable Reject by user Interaction with other services Coin line or pay phone 4. when service conflict occurs. That is. the system processes according to the CLIR service. CLIP and CLIR are mutually exclusive. the CLIR enjoys higher priority than the CLIP.

indicates that the corresponding NE is not required.1 Requirements for NEs Table 4-3 lists the network elements (NEs) required by the line identification services. HLR = home location register The symbol √ indicates that the corresponding NE is required.4 Benefits Table 4-2 lists the beneficiaries and description of the benefits. RNC = radio network controller. 4. The hyphen . the caller number can be kept secret. After the COLP service is provided. BTS = base transceiver station. if the subscriber is unavailable to answer. After the CLIR service is provided. BSC = base station controller. forwarding number is presented on the MS of the caller. 4-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .2 Availability 4. MGW = media gateway. After the CLIP service is provided. SGSN = serving GPRS support node. a subscriber can identify callers based on numbers presented by Mobile Station (MS) to determine whether to answer phones. MS = mobile station. MSC = mobile switching center. the subscriber can reply later based on presented numbers. a called number is not presented on the MS of caller. After the COLR service is provided. Also. VLR = visitor location register. After the COLR service is provided for a forwarding subscriber.1. Table 4-3 NEs required by the line identification services UE/MS √ NodeB/ BTS √ RNC/B SC √ MSC server √ MGW SGSN VLR √ HLR √ Note: UE = user equipment.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description 4. Thus.2. forwarding number is not presented on the MS of caller. Table 4-2 Beneficiaries and description of the benefits Beneficiary Carriers Mobile subscribers Description The line identification services add values of services. a subscriber numbers is not presented on the MS of callee. if a callee activates forwarding service and notifies the caller.

The MSC of caller sends corresponding CLI information in the outgoing signaling.2 CLIP The following section describes the working principle of the CLIP service: The Gateway MSC (GMSC) obtains CLI. 4.3 CLIR The following section describes the working principle of the CLIR service: A subscriber initiates a call. 4. the MSC of callee determines whether to send CLI information to the callee.3.1 Service Data Management The HLR performs the following functions: Completes the management operations of carriers on service data. 4. SI and possible aCLI.3 Applicable Versions Table 4-4 lists the applicable versions of Huawei wireless core network products that the line identification services support. No license is needed. configures them in outgoing signaling and then sends them to the MSC of callee. PI. the parameter whether to invoke the CLIR may be sent at that time. Based on the earlier mentioned information and callee CLIP subscription information stored in the VLR. Modifies the subscription information that it stores.2. Table 4-4 Applicable versions of Huawei wireless core network products Product MSC server MSOFTX3000 Applicable Version V100R002 and later versions 4.3. PI and SI in outgoing signaling based on CLIR subscription information stored in the VLR and CLI.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service 4. aPI and aSI from the VLR or incoming signaling.) The MSC of caller determines CLI.3 Working Principle 4.3. Updates the subscription information in the VLR by inserting subscriber data.2 Requirements for License The line identification services are basic services of Huawei wireless core network. PI and SI in A interface signaling. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-5 .2. (For subscribers that subscribe CLIR temporary mode.

4. The MSC of caller sends answer message with COL information to the caller.1 CLIP Figure 4-1 shows the CLIP service flow. the MSC of caller sets the COL information to be sent to the caller.CoNC) SETUP(CLIPBN.GN) SRI PRN PRN ack SRI ack IAM(CLIPN.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description 4. the answer message sent by the MSC of callee to the MSC of caller carries COL.4 Service Flow 4. PI and SI in A interface signaling. The parameter Calling Party BCD Number in the message contains CLI. 4. If the 4-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Figure 4-1 CLIP service flow MS/PSTN (G)MSC server HLRb MSC server b MS SETUP(CLIPBN) or IAM(CLIPN.3. and caller COLP subscription information stored in the VLR. Based on COL. PI and SI to be sent to the MSC of caller based on callee COLR subscription information stored in the VLR and COL. PI and SI to the MSC of caller. SI and possible aCOL. If a caller is the MS. The MSC of callee sets COI. aPI and aSI in incoming signaling. PI.4 COLP The following section describes the working principle of the COLP service: When a callee answers the phone.3. aPI and aSI information. The MSC of callee sends answer message with COL. the MS sends the SETUP message to the MSC server. PI. PI and SI.GN.5 COLR The following section describes the working principle of the COLR service: A callee answers the phone. The message sent to the MSC of callee carries COL.4. PI and SI. SI and possible aCOL.CoNC) CLIPBN: Calling Party BCD Number CLIPN: Calling Party Number SRI: Send Routing Information ack: acknowledge IAM: Initial Address Message GN: Generic number PRN: Provide Roaming Number CoNC: Cause of NO CLI 1.

The MSC server b sets Calling Party BCD Number and possible Cause of NO CLI in the SETUP message based on received CLI. aPI and aSI in the Generic number.2 CLIR Figure 4-2 shows the CLIR service flow. The HLRb initiates the PRN operation to the MSC server b (VLR). 3.4. 4. the MSC server directly end the call. 2. Figure 4-2 CLIR service flow MS MSC server (G)MSC server SETUP(CLIPBN. when a subscriber shields the CLIR service through the menu of mobile phone. If CLIR service s in temporary allowed mode. In addition. The parameter Calling Party Number in the originated call message contains CLI. Cause of NO CLI and CLIP subscription information. The Calling Party Number contains CLI information. PI and SI. the originated call message may contain parameters Generic number and Cause of NO CLI. aCLI. the originated call message may contain the Generic number. PI and SI in the Calling Party Number.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service caller is a fixed network subscriber. If the call triggers some special application in the MSC server. 5. The MSC server sends the originated call message to called office. The (G)MSC server initiates the SRI operation to the HLRb. The MS sends the SETUP message to the GMSC server. when a subscriber invokes the CLIR service through the menu of mobile phone.CLIR suppression or CLIR invocation) IAM(CLIPN. the SETUP message contains the parameter CLIR invocation. If the SETUP message contains the parameter CLIR invocation and the subscriber does not subscribe the CLIR service. 3. CLIR invocation. CLIR suppression and CLIR subscription information. The parameter Calling Party BCD Number in the message contains CLI. the SETUP message contains the parameter CLIR suppression. 2. The MSC server sets Calling Party Number and possible Cause of NO CLI in originated call message (such as the IAM message) based on CLI.CoNC) CLIPBN: Calling Party BCD Number CLIPN: Calling Party Number IAM: Initial Address Message CoNC: Cause of NO CLI 1. PI and SI. the Public Switched Telephone Network (PSTN) sends originated call message (such as the IAM message) to the GMSC server through trunk signaling. The message contains the Calling Party Number and possible Generic number and Cause of NO CLI. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-7 . After obtaining the roaming number. 6. aPI and aSI. 4. The MSC server b sends the SETUP message to the callee. If the CLIR service is in temporary restricted mode. the (G)MSC server transfers the originated call message to the MSC server b. The Generic number contains aCLI.

4 COLR Figure 4-4 shows the COLR service flow.GN) CON: Connected GN: Generic number ANM: Answer Message 1. If the callee is a fixed network subscriber. SI. PI.4. The (G)MSC server sends the answer message to the MSC server of caller. Figure 4-3 COLP service flow MS MSC server (G)MSC server PSTN/MS ANM(CON number. The MSC server of caller sends the CONNECT message to the caller. possible aCOL. PI and SI. aPI and aSI. 4. 3. The answer message contains Connected number and possible Generic number. The value of Connected number contains COL.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description 4.3 COLP Figure 4-3 shows the COLP service flow. the GMSC server transparently transmits the received answer message (such as the ANM message). and COLP subscription information. 2.4. the answer message may contain Generic number that contains aCOL. Based on the callee COLR subscription information. The Connected number contains COL. The MSC server sets the parameter Connected number in the CONNECT message based on received COL. 4. If a callee is the MS. aPI and aSI information. Figure 4-4 COLR service flow (G)MSC server MSC server MS CONNECT ANM(CON number) CON: Connected ANM: Answer Message 4-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . when the MS answers. the MSC server sets the value of Connected number in the answer message (such as the ANM message) sent to the MSC server of caller. If the call triggers some special application in the MSC server.GN) CONNECT(CON number) CONNECT or ANM(CON number. it sends the CONNECT message to the MSC server. PI and SI.

When the MS answers. PI and SI. The change procedure is listed as follows: Step 1 If necessary.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service 1. Step 2 Run ADD CLIPRO to add a caller number and call source thus to change caller number presentation. DCT=TYPE6. CLIPFX=K'60139. Step 3 If necessary. CLIMAXLEN=13.5 Data Configuration 4. run ADD DNC to add number change format. run ADD CLCRPRO to add a called number related to the caller number thus to change caller number presentation. 4. CLDCORNAME="DEL60". DCL=2. it can change connected numbers for different connected numbers and call sources. The change procedure is listed as follows: Step 1 If necessary. it sends the Connect message to the MSC server. it can change caller number presentation for different caller numbers. Changing Caller Number Presentation When the MSOFTX3000 acts as a landing office. The MSC server sets the value of Connected number in the answer message (such as the ANM message) to be sent to calling office. run ADD DNC to add number change format. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-9 . The value of Connected number contains COL. see the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide. Changing Connected Number When the MSOFTX3000 acts as an originating office.1 Configuring Data at the MSOFTX3000 Side For the details of data configuration.5. delete the prefix 60 when the caller number is presented. Enabling the Service No additional data is required to enable the service. Step 2 Run ADD AIDNUMPRO to add called number and call source thus to change connected number. ADD DNC: DCN="DEL60". ----End The following table lists an example: Description Script For a caller number with call source name A and started with 60139. ADD CLIPRO: CSN="A". 2. The MSC server sends the answer message to the calling office. call sources and called numbers related to caller numbers. 3.

= 0: Provide COLR and CLIR services based on subscriber subscription information. = 0: The PI value in connected number parameter is set to COL not available. ADD DNC: DCN="ADD0". = 1: Process based on protocol. add prefix 0 in front of it. 1 1 1 4-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 1 P123 (BICC operation reserved parameter 10) Bit 11 P123 (BICC operation reserved parameter 10) Bit 8 P140 (VLR software parameter) Bit 1 = 0: The PI value in caller number parameter is set to CLI not available.7 signaling. It indicates whether to release when a subscriber has the CLIR request if the subscriber does not subscribe the CLIR service. = 1: The VLR forces COLR and CLIR supplementary services are provided whether they are subscribed. = 1: Not allow a caller number to be presented. It indicates whether the PI value in caller number parameter is set to CLI not available. Default Value 1 P51 (Call internal parameter 3) Bit 3 = 0: Not release. ADD AIDNUMPRO: CSCNAME="A". CDN="ADD0". NUMTY=TY0. Value = 0: Allow a caller number to be presented. It indicates whether the PI value in connected number parameter is set to COL not available.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description ----End The following table lists an example: Description Script For a connected number with call source name A and started with 755. PFX=K'755. = 1: Release. Related Software Parameters Name P11 (TUP operation reserved parameter 4) Bit 0 Meaning It controls whether a caller number is allowed to be presented when No. = 1: Process based on protocol.1 signaling is incoming office or converted into No. It controls the realization of COLR and CLIR functions. ND=K'0. DCT=TYPE1.

In temporary allowed mode. Value = 0: Set CLIR for all subscribers forcibly.5.2 Configuring Data at the HLR Side No data related to the service needs to be configured at the HLR side. Table 4-5 Operation modes of the line identification services Operation Mode Operation by carriers Operation by mobile subscribers Operation Interface HLR MS Service Operations Provide the service. the services are activated when they are provided. = 1: Set CLIP for all subscribers forcibly. For supplementary line identification services. = 11: Determine the realization of CLIP/CLIR function based on 3GPP protocol.6.6. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-11 . see the corresponding operation manual of the HLR.1 Opreations by Carriers For details.2 Operations by Mobile Subscribers Prerequisite The system has provided the CLIR service in temporary allowed or temporary restricted mode for subscribers. 4.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service Name P148 (Call internal parameter 13) Bit 1 and 0 Meaning It controls the realization of CLIP/CLIR function. 4. invoke the CLIR service. 4.6 Service Management The line identification services have two operation modes. Default Value 3 4. Withdraw the service. and the services are deactivated when they are withdrawn. In temporary restricted mode. suppress the CLIR service. as listed in Table 4-5.

When a callee activates the CLIP service and the caller activates the CLIR service. On the MS.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description Operations On the MS. CFNRy and CFNRc If the system provides the CLIP to a callee and the caller does not activate the CLIR service. DN refers to a called number.7. Of it.7 Service Interaction 4. For details. dial "*31#DN". Subscribers can also perform the operations through the menus of some mobile phones. DN refers to a called number. suppress the CLIR service. In addition. Step On the MS. subscriber A calls subscriber B. the system processes according to the CLIR service. and then press the Send key. If C activates the CLIP service and A does not activate the CLIR service. the caller number is presented to the callee according to the CLIP service. see the user manuals of the mobile phones. and then press the Send key. The call is forwarded to subscriber C. when forwarding occurs. CFB. If a subscriber activates CLIP and CW service. For example. the MS of C can present the number of A. CLIP and CW The CLIP and CW services are compatible. Of it. CLIP and CFU. In temporary restricted mode. But if the CLIP property of the callee is OVERRIDE. the CLIR service enjoys higher priority than the CLIP service. Table 4-6 CLIR service operation performed by mobile subscribers Operation Type In temporary allowed mode. invoke the CLIR service. dial "#31#DN". calls are processed according to the CW service. mobile subscribers can perform the operations listed in Table 4-6.1 CLIP Table 4-7 lists the interactions between the CLIP service and other services. 4. the MS of the subscriber can present caller numbers. the system processes according to the CLIP service. 4-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 4-7 Interactions between the CLIP service and other services Service CLIP and CLIR Interaction In general.

the system processes according to the CLIP service. When the subscriber is a main controller.7. The call is forwarded to subscriber C. CLIR and CFU. subscriber A activates the CLIR service. 4. CFNRy and CFNRc The CLIR and forwarding services are compatible. the COLP and MPTY services are compatible. CFB. the system processes according to the COLP service. Table 4-8 Interactions between the CLIR service and other services Service CLIR and CLIP Interaction In general. the system processes according to the COLR service.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service 4. If a caller activates the CLIR service.7. the CLIR service enjoys higher priority than the CLIP service. Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-13 . The MS of C cannot present the number of A. Table 4-9 Interactions between the COLP service and other services Service COLP and COLR Interaction In general.2 CLIR Table 4-8 lists the interactions between the CLIR service and other services. When the subscriber is remote (participant of the MPTY service) the subscriber cannot receive COLP supplementary service information of other meeting participants. But if the COLP property of caller is OVERRIDE. the MS of forwarding target subscriber cannot present the caller number unless forwarded target subscriber activates the CLIP service and the property of CLIP is OVERRIDE. COLP and MPTY If a subscriber activates both COLP and MPTY service. A calls B. When a caller activates the COLP service and the callee activates the COLR service. the system processes according to the CLIR service. But if the CLIP property of the callee is OVERRIDE.3 COLP Table 4-9 lists the interactions between the CLIP service and other services. When a callee activates the CLIP service and the caller activates the CLIR service. For example. the COLR service enjoys higher priority than the COLP service.

081 V4.8 Reference 4. But if the COLP property of caller is OVERRIDE.4 Line Identification Service HUAWEI MSOFTX3000 Feature Description Service COLP and CFU.081 V4. Table 4-10 Interactions between the COLR service and other services Service COLR and COLP Interaction In general.4 COLR Table 4-10 lists the interactions between the COLR service and other services.1.1. COLR and CFU.0 3GPP TS 24. When a caller activates the COLP service and the callee activates the COLR service.0 3GPP TS 24.7.0 3GPP TS 29. The MS of caller presents callee numbers.081 V4. the COLR service enjoys higher priority than the COLP service. CFB. If a caller activates the COLP service and the forwarded subscriber does not activate the COLR service. the callee notifies the caller. the system processes according to the COLP service. but the COLP service can be invoked to present callee numbers. the system processes according to the COLR service. If a caller activates the COLP service and the property of caller is OVERRIDE.1 Protocols and Specifications This following specifications and manuals are referred to: 3GPP TS 22.0 3GPP TS 23. the MS of caller cannot present the callee number unless the property of caller is OVERRIDE.0 4-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) .15. 4.1. If the callee activates the forwarding service and selects not to notify the caller when forwarding occurs. CFNRy and CFNRc Interaction The COLP and forwarding services are compatible. CFB.002 V4.008 V4.8. the forwarding notification does not provide the number of forwarded subscriber. 4.15. CFNRy and CFNRc If a forwarded subscriber activates the COLR service. when the callee is forwarded. the forwarding notification does not provide the number of forwarded subscriber.

8.HUAWEI MSOFTX3000 Feature Description 4 Line Identification Service HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide HUAWEI HLR9820 Home Location Register Subscriber Management 4.2 Acronyms and Abbreviations Acronym/Abbreviation 3G 3GPP2 CLI COL CLIP CLIR COLP COLR Full Name The Third Generation 3rd Generation Partnership Project 2 Calling Line Identity Connected Line Identity Calling Line Identification Presentation Calling Line Identification Restriction Connected Line Identification Presentation Connected Line Identification Restriction Issue 02 (2007-06-10) Huawei Technologies Proprietary 4-15 .

........2 Configuring Data at the HLR Side......5-17 5...1 Protocols and Specifications ........................................................................................................................................................2 CH.........................................................................6 Service Management ........................5-2 5.....5-18 5......................................................................5-18 5.................................................................................1 CW .............3...5-5 5............................................4 Service Flow..............5-14 5.................................................................................5................................................5-4 5........5-19 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ..........................................3 Applicable Versions...............................1.......................................5-1 5.............................................5-4 5..................................................................................2 Definition .............................................3 Working Principle.......3 Working Principle of CH .............5-3 5.5-14 5...................................................1 Service Description .........9.....................................................................................................................................................................................................1......................................................................................................................................7..................................................................................................................................5................5-19 5.....................................................5-19 5.5-4 5................................................2 Requirements for License .............................................................................................................................................................................3 Operations by Mobile Subscribers .........................3.................................................................................................................................................................5-19 5.................................5-6 5......................................................................................................5-3 5.5-3 5...........5-15 5..................................5-2 5............................................................................................................................................5-12 5..................................................................5-6 5...........................................................................5-3 5..2 Availability ........................................................................................................5-4 5............................5-14 5..3 Benefits ........................................................1.............................5-16 5.......................................................................................6............................4.2 Working Principle of CW..................4...........3.................................................1 Requirements for NEs...............................................................5 Data Configuration....................................1 Function Code..................................................1 Configuring Data at the MSOFTX3000 Side..........5-16 5..................................2.........9................................................................................7............................2 CH.........................................................................................................................................................................................1 Service Flow of CW......................................................................5-10 5..............1 Overview......................2 Acronyms and Abbreviations ..8..............................................5-12 5...................2............................................8.....................8 Service Interaction ...............................................................1 Service Data Management ........................................................................................................................................................6.........2......................9 Reference ......5-15 5......................................1 CW ....................................................................................2 Operations by Carriers ......................................................................5-2 5.......HUAWEI MSOFTX3000 Feature Description Contents Contents 5 Call Completion Supplementary Service.........................................................7 Charging and CDR ..................................2 Service Flow of CH .....6..............................

............................5-7 Figure 5-2 Service flow when a subscriber rejects a waiting call...........................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 5-1 Service flow when a subscriber accepts a waiting call ...................................................................5-10 Figure 5-4 Service flow for alternating from the A-B call to the A-C call .................................................................................5-9 Figure 5-3 Service flow for holding and retrieving a call........................................................ 5-11 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ..

.....5-13 Table 5-7 Operation modes of the call completion supplementary services........5-4 Table 5-6 Related software parameters..........................5-18 Table 5-10 Interactions between the CH service and other services............................................................................................................................................................................5-19 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii .............5-2 Table 5-3 Beneficiaries and description of the benefits ...5-3 Table 5-5 Applicable versions of Huawei wireless core network products ..........................................................................................................................5-14 Table 5-8 Operations performed by mobile subscribers .................................5-3 Table 5-4 NEs required by the call completion supplementary services ..................................................................................5-15 Table 5-9 Interactions between the CW service and other services ......................................................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 5-1 Name and code of the function...................................5-2 Table 5-2 Name and definition of the CW and CH services....................................................................................................................................................................

8 Service Interaction 5. whether Licenses are required. and the benefits that carriers and mobile subscribers can obtain from this feature.4 Service Flow 5. The network elements (NEs) that are required for the feature. The protocols and specifications that this feature must comply with.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-1 . and the acronyms and abbreviations of this chapter. function definition of this feature. The charging and the generation of CDRs when the network provides this feature. The functions of the NEs.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service 5 Call Completion Supplementary Service About This Chapter The following table lists the contents of this chapter. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.2 Availability 5. The relationships and restrictions between this feature and other services or features. and networking requirements.5 Data Configuration 5. and the version requirements of the NEs.1 Service Description Describes The function code.6 Service Management 5. The service flow of the network when providing this feature.7 Charging and CDR 5. The data configurations that are required on the MSOFTX3000 and the UMG8900. 5.3 Working Principle 5. Section 5.

reject. or has a call on hold. and the system disconnects the subsequent incoming calls instantly. 5-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . When a call is on hold.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 5. and an active call is set up. the system reserves the traffic channel allocated for the call. Disconnect the held call. a subscriber can: Retrieve the held call. and retrieve the call later if required. Subscribers can choose either one to process two calls at the same time. Disconnect the held call. only one waiting call is allowed. The subscriber can determine to accept. Table 5-2 lists the name and definition of the CW and CH services. Table 5-1 Name and code of the function Name Call completion supplementary services Code WMFD-020400 5.1 Function Code Table 5-1 lists the name and code of the function.1 Service Description 5. or ignore the incoming call. only one held call is allowed.2 Definition The call completion supplementary services provide two services: call waiting (CW) and call hold (CH).1. When a call is on hold. Table 5-2 Name and definition of the CW and CH services Name CW Definition The CW service enables a mobile subscriber to be notified of an incoming call notification under the following conditions: There is no idle service channel for the incoming call. The caller receives notifications during call waiting. CH The CH service enables a mobile subscriber to interrupt the current call temporarily. When the call is interrupted. The subscriber is in conversation. For one subscriber. and no active call is set up. For one subscriber. the subscriber can: Alternate from one call to the other.1. Disconnect the active call. Set up an active call. Disconnect both the active call and the held call.

RNC = radio network controller. When the CH service is activated.indicates that the corresponding NE is not required. and improve the call completion rate. No license is required. Table 5-4 NEs required by the call completion supplementary services UE/MS √ Node B/BTS √ RNC/BSC √ MSC server √ MGW √ SGSN VLR √ HLR √ Note: UE = user equipment.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service 5. Table 5-3 Beneficiaries and description of the benefits Beneficiary Carriers Mobile subscribers Description The call completion supplementary services add values of services.3 Benefits Table 5-3 lists the beneficiaries and description of the benefits. a subscriber can answer another call in conversation. MSC = mobile switching center. the subscriber can select the one that is more important. and answer another call. a subscriber can hold the current call. The hyphen . SGSN = serving GPRS support node. Therefore.2 Availability 5. After the CW service is activated.1 Requirements for NEs Table 5-4 lists the network elements (NEs) required by the call completion supplementary services. This indicates that subscribers can control the CW service flexibly. VLR = visitor location register. 5. MS = mobile station.1.2. and improves the call completion rate.2 Requirements for License The call completion supplementary services are basic services of Huawei wireless core network.2. BTS = base transceiver station. This minimizes the possibility of missing calls. HLR = home location register The symbol √ indicates that the corresponding NE is required. Subscribers can activate and deactivate the CW service freely. MGW = media gateway. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-3 . BSC = base station controller. 5.

3. 5-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . an A-B call is active or on hold. 5. If the CW service is activated for B.3 Applicable Versions Table 5-5 lists the applicable versions of Huawei wireless core network products that the call completion supplementary services support. indicating that B is busy. and then updates the subscription information in the VLR by inserting subscriber data. the MSC waits for the ALERTING message from the callee. the MS sends a response to the MSC. the MS informs B of the incoming call based on the CW indication. there is no activation or deactivation operation. the MSC processes the CW service. the MSC receives a call from C to B (a C-B call). Therefore. The MSC sends a SETUP message for setting up the C-B call to the MS. The message carries a CW indication. For the CH service.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 5. At the same time.2 Working Principle of CW The following section describes the working principle of the CW service.3. Currently. When subscriber B is in conversation. The HLR modifies the subscription information stored in the HLR based on the message. The MSC queries the subscription information of B.1 Service Data Management Management on Service Data The HLR performs the following functions: Completes the management operations of carriers on service data Modifies the subscription information stored in the HLR Updates the subscription information in the VLR by inserting subscriber data Activation and Deactivation of CW When a subscriber initiates the activation or deactivation operation. After receiving the response. the MSC transparently sends the operation message to the HLR.2.3 Working Principle 5. Table 5-5 Applicable versions of Huawei wireless core network products Product MSC server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V100R002 and later versions 5.

Retrieving a Call The following section describes the working principle for retrieve a call. If T2 or T3 times out. it returns a RETRIEVE ACKNOWLEDGE message to MS A. the MS sends a CONNECT message to the MSC for connecting the C-B call. If B rejects the call before T2 and T3 time out.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Upon receiving the ALERTING message. retrieves the connection of the original channel. 2. the MSC sends a DISCONNECT message to B and C respectively.3. instructing C to wait for the call. and sends an acknowledge to C. If the MSC rejects the request. A retrieves the A-B call. The conversation between A and B continues. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-5 . 5. carrying the CW indication.3 Working Principle of CH Overview The following sections describe the working principle of the CH service. The MSC determines whether to accept the request for the CH service based on the CH activation indication and other factors. If the MSC accepts the requests. the MSC of B plays an announcement to C. for example. 3. The MSC sends a response to the MS. reserves the channel allocated for the current call. If the MSC accepts the request. 2. the MSC starts the CW timer T2 and the no-reply timer T3. the MSC follows the normal flow to disconnect the waiting call. A holds the call when A is in conversation with B. it returns a HOLD REJECT message to MS A. MS A sends a HOLD request to the MSC. 1. instructing them to release the C-B call. it returns a RETRIEVE REJECT to MS A. If B answers before T2 and T3 time out. At the same time. Before B answers or disconnects the call. and sends a message to B or the MSC of B at the same time to notify B. 4. and sends a message to B or the MSC of B at the same time to notify B. The MSC then waits for the answer of B. If the MSC rejects the request. 3. The MSC queries the subscription information of A. including two parts Holding a call Retrieving a call Holding a Call The following section describes the working principle for holding a call. If the CH service is activated for A. The conversation between A and B continues. MS A sends a RETRIEVE request to the MSC. 1. 5. it returns a HOLD ACKNOWLEDGE message to MS A. whether there is a held call. indicating that the C-B call is set up. the MSC sends an ALERTING or ACM message to C. the MSC processes the CH service. 4.

and sends a message to C and the MSC of C at the same time. A returns a HOLD ACKNOWLEDGE message to the MS before 4. The fixed network subscriber C calls B. An A-B call is active. Figure 5-1 shows the call flow.4 Service Flow 5. converts the active call to a held call.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 5. If an A-C call is active.4. 5. 5-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) .1 Service Flow of CW Accepting a Waiting Call The following section describes the flow of the CW service under the following conditions: The CW service is activated for B. B accepts the waiting call.

6. MS B returns a CALL CONFIRMED message. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-7 . 4. MSC server B allocates channels with the BSC or RNC. The PSTN subscriber C sends an IAM message to the gateway mobile switching center (GMSC) server. 5. 3. CONNECT CONNECT ack ANM ANM CALL B-C ACTIVE IAM: Initial Address Message PRN: Provide Roaming Number ANM: Answer Message SRI: Send Routing Information ACM: Address Complete Message ack: Acknowledge The service flow when a subscriber accepts a waiting call is as follows: 1.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Figure 5-1 Service flow when a subscriber accepts a waiting call PSTN C GMSC server HLR B MSC server B MS B CALL A-B ACTIVE IAM SRI PRN PRN ack SRI ack IAM SETUP Call CONFIRMED ALERTING ACM ACM B wants to connect the waiting call. The GMSC server forwards the IAM message to MSC server B after obtaining the mobile station roaming number (MSRN) of MS B by sending an SRI request. MS B sends an ALERTING message. MSC server B sends a SETUP message to MS B. 2. The value of the Cause information element in the message is 17 (user busy). The value of the Signal Information element in the message is 7 (call waiting tone on).

MSC server B then follows the indication to play an announcement to C. The fixed network subscriber C calls B. Thus MS B and MSC server B can identify the signaling messages. The transaction identifier of the signaling messages for the B-C call is different from that for the A-B call. Figure 5-2 shows the call flow. Rejecting a Waiting Call The following section describes the flow of the CW service under the following conditions: The CW service is activated for B. MSC server B sends an ACM message to the GMSC server. The B-C call is set up. instructing C to answer. MSC server B returns a CONNECT ack message to MS B. B rejects the waiting call. An A-B call is active. If B answers.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 7. 10. MSC server B sends an ANM message to the GMSC server. 9. carrying a CW indication. 8. 5-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . instructing C to wait for the call. MS B sends a CONNECT message to MSC server B. 11.

3. The PSTN subscriber C sends an IAM message to the GMSC server.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Figure 5-2 Service flow when a subscriber rejects a waiting call PSTN C GMSC server HLR B MSC server B MS B CALL A-B ACTIVE IAM SRI PRN PRN ack SRI ack IAM SETUP CALL CONFIRMED ALERTING ACM ACM B rejects the call from C. MSC server B sends a SETUP message to MS B. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-9 . 6. If B rejects the call. 8. MS B sends a DISCONNECT message to MSC server B. The value of the Cause information element in the message is 17 (user busy). MS B returns a CALL CONFIRMED message. The value of the Cause information element in the message is 17 (user busy). 5. MS B sends an ALERTING message. MSC server B sends an ACM message to the GMSC server. instructing C to wait for the call. The GMSC server forwards the IAM message to MSC server B after obtaining the MSRN of MS B by sending an SRI request. DISCONNECT RELEASE REL REL RLC RLC RELEASE COMPLETE IAM: Initial Address Message PRN: Provide Roaming Number REL: Release RLC: Release Complete SRI: Send Routing Information ACM: Address Complete Message ack: Acknowledge The service flow when a subscriber rejects a waiting call is as follows: 1. carrying a CW indication. 4. 2. 7. MSC server B then follows the indication to play an announcement to C. The value of the Signal Information element in the message is 7 (call waiting tone on). MSC server B allocates channels with the BSC or RNC.

5. HOLD HOLD ack CPG FACILITY CALL A-B on HOLD A wants to retrieve the A-B call. Figure 5-3 Service flow for holding and retrieving a call MS A MSC server A MSC server B MS B CALL A-B ACTIVE A wants to hold the A-B call. The transaction identifier of the signaling messages for the B-C call is different from that for the A-B call. MSC server B returns a RELEASE message to release the B-C call. Figure 5-3 shows the service flow. The GMSC server returns an RLC message. B is a mobile subscriber.4. 11.2 Service Flow of CH Holding and Retrieving a Call The following section describes the service flow for holding and retrieving a call under the following conditions: The CH service is activated for A. An A-B call is active.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 9. MS B returns a RELEASE COMPLETE message. Thus MS B and MSC server B can identify the signaling messages. 12. 10. MSC server B sends an REL message to the GMSC server for call release. indicating that the call release is complete. The value of the Cause information element is 17 (user busy). indicating that the release of the B-C call is complete at the MS side. RETRIEVE RETRIEVE ack CPG FACILITY CALL A-B ACTIVE CPG: Call Progress ack: Acknowledge 5-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

MSC server B sends a FACILITY message to MS B. An A-B call is active. When A wants to hold the current A-B call. 2. MS A sends a RETRIEVE message to MSC server A. 4. in which CallOnHold-indicator is callRetrieved. carrying a notification for remote hold. 7. 8. Figure 5-4 shows the service flow for alternating from the A-B call to the A-C call. and returns a RETRIEVE ack message to MS A.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service The service flow for holding and retrieving a call is as follows: 1. the invoke component is NotifySS. Figure 5-4 Service flow for alternating from the A-B call to the A-C call MS A MSC server A MSC server B Call A-B active. An A-C call is on hold. requesting MSC server A to retrieve the call. carrying a notification for remote retrieve. MSC server A accepts the request. B and C are mobile subscribers. call A-C on hold A wants to alternate from the A-B call to the A-C call. In the message. and returns a HOLD ack message to MS A. In the message. MSC server A sends a CPG message to MSC server B. When A wants to retrieve the A-B call. MS A sends a HOLD message to MSC server A. 6. 5. The message is used to inform MS B that the call is retrieved. Alternating from One Call to the Other The following section describes the service flow for alternating from one call to the other under the following conditions: The CH service is activated for A. MSC server A accepts the request. in which CallOnHold-indicator is callOnHold. The message is used to inform MS B that the call is on hold. HOLD RETRIEVE HOLD ack CPG RETRIEVE ack CPG FACILITY Call A-B on hold. MSC server B sends a FACILITY message to MS B. requesting MSC server A to hold the call. call A-C active FACILITY MS B MSC server C MSC CPG: Call Progress ack: Acknowledge Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-11 . MSC server A sends a CPG message to MSC server B. the invoke component is NotifySS. 3.

7. and a RETRIEVE request for retrieving the A-C call. 6. and returns a RETRIEVE ack message to MS A.5 Data Configuration 5.1 Configuring Data at the MSOFTX3000 Side Overview For the details of data configuration. MSC server B sends a FACILITY message to MS B. The message is used to inform MS B that the call is retrieved. the invoke component is NotifySS. 2. in which CallOnHold-indicator is callOnHold. In the message. Thus MS A and MSC server A can identify the signaling messages. and returns a HOLD ack message to MS A. see HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide. 4. In the message. Generating CDRs The command MOD GBILLCTRL is used to generate the call detail records (CDRs) of the CW and CH services. The message is used to inform MS B that the call is on hold. MSC server A accepts the request. 5-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the invoke component is NotifySS. carrying a notification for remote hold. carrying a notification for remote retrieve. MSC server A sends a CPG message to MSC server C. MSC server A accepts the request. When A wants to alternate from the A-B call to the A-C call. MSC server C sends a FACILITY message to MS C. MS A sends a HOLD request to MSC server A for holding the A-B call. 3.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description The service flow for alternating from the A-B call to the A-C call is as follows: 1. Enabling the Service No additional data is required to enable the service. Related Software Parameters Table 5-6 lists the related software parameters. 5. in which CallOnHold-indicator is callRetrieved. 5. MSC server A sends a CPG message to MSC server B.5. The transaction identifier of the signaling messages for the A-C call is different from that for the A-B call.

no ALERTING message containing FACILITY-IE is sent to inform C of the CW service. = 1: Play the call hold tone. When A and B are in conversation.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Table 5-6 Related software parameters Name P19 (ISUP Operation Reserved Parameter 2) Bit 0 Meaning It determines whether to play the call waiting tone. the caller hears the call waiting tone if the callee is in the same office. 1 Default Value 1 Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-13 . If A has registered with the call forwarding service. When the CW service interacts with the ring back tone (RBT) service. the caller hears the ringback tone. the caller hears the call waiting tone. P20 (ISUP Operation Reserved Parameter 3) Bit 4 It determines whether to play the call hold tone. Value = 0: If the callee who has registered with the CW service is busy. When A and B are in conversation. The caller hears the tone from another office if the callee is in another office. = 0: Play the ringback tone. an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. If A has registered with the call forwarding service. the caller hears the RBT. If the caller A has not registered with the call forwarding service. C calls B. When the CW service interacts with the RBT service. an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. If the caller A has not registered with the call forwarding service. C calls B. = 1: If the callee who has registered with the CW service is busy.

in call active state.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description Name P129 (CHG Parameter 1) Bit 7 Meaning It determines whether to generate intermediate CDRs or event CDRs when the times of the handover or supplementary service operations exceed the limit.1 Overview The call completion supplementary services have two operation modes.2 Configuring Data at the HLR Side No data related to the service needs to be configured at the HLR side. = 1: Generate event CDRs. Activate the service (for the CW service only). 5-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 5-7 Operation modes of the call completion supplementary services Operation Mode Operations by carriers Operation Interface HLR Service Operations Provide the service.6 Service Management 5. 1 5. Value = 0: Generate intermediate CDRs.6. Withdraw the service. 5. invokes the CW service.5. = 1: Not generate event CDRs. It determines whether to generate event CDRs when the subscriber. as listed in Table 5-7. Default Value 1 P130 (CHG Parameter 2) Bit 10 = 0: Generate event CDRs. Deactivate the service (for the CW service only).

and then press the Send key. 5. dial "43#". Table 5-8 Operations performed by mobile subscribers Service Type CW CW Operation Type Activate the CW service. and the service is deactivated when it is withdrawn.2 Operations by Carriers For details.3 Operations by Mobile Subscribers Prerequisite The CW or CH service is provided for mobile subscribers. Hold an active call. and accept a waiting call. Accept a waiting call. 5. dial "#43#". the service is activated when it is provided.6. For the CH service. and hold the original active call. Retrieve a held call. and release an active call. Set up a call. Release and reject a waiting call.6. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-15 . Release a held call. Step On the MS. Alternate from an active call to a held call. Deactivate the service (for the CW service only). Deactivate the CW service. and hold an active call.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Operation Mode Operations by mobile subscribers Operation Interface MS Service Operations Activate the service (for the CW service only). and then press the Send key. see the corresponding operation manual of the HLR. Operations On the MS. mobile subscribers can perform the operations listed in Table 5-8. On the MS. Release both the active call and the held call.

see the user manuals of the mobile phones.7. press the Release key. 5. dial "0".7 Charging and CDR 5. dial the called number of the new call. Release an active call. Release both the active call and the held call. On the MS. and accept a waiting call. CH On the MS. and then press the Send key. For details. CH CH On the MS. dial "1". and then press the Send key. Set up a call. and then press the Send key. CH CH On the MS. CW On the MS. and hold the original active call. dial "1". and then press the Send key. On the MS. CW On the MS. and release an active call. Step On the MS. and answer a waiting call. Hold an active call. Release a held call.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description Service Type CW Operation Type Release and reject a waiting call.1 CW The MSOFTX3000 provides two ways to generate CDRs for the CW service: Independent charging Segment charging Independent charging means that the MSOFTX3000 generates the following CDRs: The event CDR containing the CW indicator and time stamp based on the CW notification The original MOC or MTC CDR for the whole A-B call 5-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . dial "2". Subscribers can also perform the operations through the menus of some mobile phones. and then press the Send key. and then press the Send key. dial "2". Alternate from an active call to a held call. dial "0". and then press the Send key. Retrieve a held call.

The scenario is as follows: A in the local office calls B in another office. 5. Usually. The scenario is as follows: A in the local office calls B in another office. The following gives an example of independent charging for the CW service. Segment charging means that the MSOFTX3000 generates an intermediate MOC or MTC CDR at the time of the hold and retrieve operations.7. Segment charging means that the MSOFTX3000 generates an intermediate MOC or MTC CDR at the time when a CW notification is generated. The billing center combines the group of CDRs and processes other charging. The supplementary service indicator is CW. Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-17 . The CW indicator and time stamp are in the last CDR. and processes other charging. and the time stamp is the time when A sends a HOLD message. The supplementary service domain in the MOC CDR generated by the local office for the A-B call records the supplementary service operation. A holds the call when A is in conversation with B. The MSOFTX3000 controls the mode for generating CDRs and the frequency for generating event or intermediate CDRs through the integrated CDR control tables of CHG Parameter 1 Bit 7.2 CH The MSOFTX3000 provides two ways to generate CDRs for the CW service: Independent charging Segment charging Independent charging means that the MSOFTX3000 generates the following CDRs: The event CDR containing the CH indicator and time stamp based on the hold and retrieve operations The original MOC or MTC CDR for the whole call The iGWB integrates the event CDR into the supplementary service domain of the original MOC or MTC CDR to generate the final MOC or MTC CDR. The following gives an example of independent charging for the CH service. independent charging is adopted. The supplementary service indicator is CH. The supplementary service domain in the MOC CDR generated by the local office for the A-B call records the supplementary service operation. The billing center combines the group of CDRs. Usually.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service The integrated Gateway Bill (iGWB) integrates the event CDR into the supplementary service domain of the original mobile originated call (MOC) or mobile terminated call (MTC) CDR to generate the final MOC or MTC CDR. The CH indicator and time stamp are in the last CDR. and the time stamp is the time when a SETUP message is sent to A. and the frequency for generating event or intermediate CDRs through the integrated CDR control tables of CHG Parameter 1 Bit 7. independent charging is adopted. C in another office calls A when A is in conversation with B. The MSOFTX3000 controls the mode for generating CDRs.

the subscriber can receive a CW indication. When a callee who has both the CW and CFU services activated is called. but has a call on hold. the incoming call is forwarded unconditionally based on the CFU service. CW and CFB The CW and CFB services are compatible. CW and CH CW and MPTY 5-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) . CW and BAIC CW and BIC-ROAM The BAIC service takes precedence over the CW service. the call is processed based on the CFNRy service.8 Service Interaction 5. If the callee is NDUB. The activation of the BAIC service does not affect any waiting call.5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description 5. the system directly processes the incoming call based on the CFB service. If the callee is UDUB. and the MS of the subscriber displays the number of the caller. If a subscriber has an active MPTY call. a subscriber can receive the CW indication when serving as the callee. If the subscriber is in conversation. but cannot answer the call. When the BAIC service is activated. Table 5-9 Interactions between the CW service and other services Service CW and CFU Interaction The CFU service takes precedence over the CW service. the subscriber can receive a CW indication when being called. the subscriber can still receive a CW indication. and has a call on hold. CW and CLIP The CLIP and CW services are compatible. The BIC-ROAM service takes precedence over the CW service.1 CW Table 5-9 lists the interactions between the CW service and other services. a subscriber cannot activate the CW service if the BIC-ROAM service is activated. the subscriber can answer the waiting call. instead of being processed based on the CW service. When roaming out of the HPLMN. the incoming call is processed based on the CW service. CW and CFNRy If both CFNRy and CW services are activated. and the subscriber determines how to process the incoming call (process it based on the CFB or CW service). The activation of the BIC-ROAM service does not affect any waiting call. The CW and MPTY services are compatible. If both CW and CH services are activated.8. If both CLIP and CW services are activated. the system notifies the subscriber. the CW service cannot be activated. If the subscriber does not send any response before the expiry of the No Reply Condition timer. When holding the MPTY call. without notifying the subscriber. a subscriber can use the CH service to answer a waiting call. If the subscriber is not in conversation.

5.0 3GPP TS 23. Table 5-10 Interactions between the CH service and other services Service CH and CW Interaction If both CW and CH services are activated. CLIP = calling line identification presentation.0.9. If the subscriber is in conversation. but cannot answer the call. a subscriber can hold an active MPTY call. the subscriber can still receive a CW indication.9 Reference 5.083 V4. CH and MPTY The CH and MPTY services are compatible.008 V4.1 3GPP TS 24. BIC-ROAM = barring of incoming calls when roaming outside home PLMN country 5.3. NDUB= network determined user busy.2 Acronyms and Abbreviations Acronym/Abbreviation CW Full Name Call Waiting Issue 02 (2007-06-10) Huawei Technologies Proprietary 5-19 . MPTY = multiparty service.9.1. a subscriber can use the CH service to answer a waiting call.1 Protocols and Specifications This following specifications and manuals are referred to: 3GPP TS 22. CFNRy = call forwarding no reply.083 V4.0 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide HUAWEI HLR9820 Home Location Register Subscriber Management 5. the subscriber can receive a CW indication. BAIC = barring of all incoming calls. but has a call on hold. and has a call on hold. and retrieve the MPTY call after the new call is complete.0 3GPP TS 23.2 CH Table 5-10 lists the interactions between the CH service and other services.8.HUAWEI MSOFTX3000 Feature Description 5 Call Completion Supplementary Service Service Interaction Note: CFU = call forwarding unconditional.083 V4. set up another call. If both CH and MPTY services are activated. If the subscriber is not in conversation. UDUB = user determined user busy.15.

5 Call Completion Supplementary Service HUAWEI MSOFTX3000 Feature Description Acronym/Abbreviation CH Full Name Call Hold 5-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

..6-6 6..........1.........7 Charging and CDR ..................6-9 6..............6-10 6......3 Working Principle...............1 Function Code.....................3 Applicable Versions.......................................1...................3 Benefits .................................................................2 Definition .....................................6....................1......3...............................................................................4 Service Flow..............................................................4.......6...............4...........................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 6 Multiparty Service ...............................1 Carrier Operation .........................................................................................6-2 6...........................................................3...............1 Requirements for NEs......................4.................... 6-11 6.........................................................................................2 Setting Up a Personal Communication with Remote Subscriber ...............................6-3 6...............6-3 6.......6-2 6........2 Availability ...........................................................................................................6-12 6......................................................................6-13 6.............6-8 6....8 Service Interaction .................................................................................................................................6-5 6...........................................................9.......................................................................6-3 6............................5.................2........6-4 6..........................................................................................................................6-5 6................................5...3....1 Functions Realized by Network Elements .................................................6-7 6..................................6-1 6...............6-3 6.................................................................................9...................................................................................................................................................................................3 Adding a Remote Subscriber................3............................................... 6-11 6......................6 Service Management .....................6-14 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ..........2 Requirements for License ......................................................................................................................................................................................................2 Acronyms and Abbreviations ................................................................................4 Disconnecting a Remote Subscriber ........9 Reference ............................................................................. 6-11 6.......................................................................................................................................................6-4 6.................................................4 MPTY Call Management .................................6-3 6..........................................................................6-3 6..................................4...................................................................................................................................................................................................6-9 6...............................................................................................................2 Mobile Subscriber Operation ...........................1 Protocols and Specifications .................................................................................................................1 Service Description ............................................................6-2 6................................1 Data Configuration at MSOFTX3000 Side....2 Service Data Management ..................6-14 6..................................5 Data Configuration.......................................................1 Setting up the MPTY Call........................................................................3 MPTY Invocation ....2.6-14 6.........6-4 6.........................................................................6-2 6..........................................................................................................2...........2 Data Configuration at UMG8900 Side ................

..............................................6-6 Figure 6-2 Create a personal communication...................................6-7 Figure 6-4 Disconnect the remote subscriber by main controller................6-9 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .......................6-7 Figure 6-3 Add a remote subscriber ........................................................................................................................................................................6-8 Figure 6-5 Disconnect the remote subscriber by main controller.........................................................................................................................................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 6-1 Setting up the MPTY call ...............................

....................................................................................6-3 Table 6-3 Operation method for MPTY service .................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 6-1 Network elements involved in MPTY features.............6-13 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ...................................................................................................................................................................... 6-11 Table 6-4 MPTY service operation (For mobile subscriber) ..........................................................................6-3 Table 6-2 Applicable versions of the MPTY ................ 6-11 Table 6-5 Interactions between the MPTY and the other services.......................................

and the benefits that carriers and mobile subscribers can obtain from this feature. The function code. and the version requirements of the NEs. function definition of this feature. 6. The network elements (NEs) that are required for the feature. The charging and the generation of CDRs when the network provides this feature. The functions of the NEs.1 Service Description Describes 6. and the acronyms and abbreviations of this chapter. The service flow of the network when providing this feature. whether Licenses are required.3 Working Principle 6. The relationships and restrictions between this feature and other services or features.2 Availability Multiparty Service The following table lists the contents of this chapter.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-1 . and networking requirements.4 Service Flow 6.5 Data Configuration 6.8 Service Interaction 6. The data configurations that are required on the MSOFTX3000 and the UMG8900.6 Service Management 6. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service 6 About This Chapter Section 6.7 Charging and CDR 6. The protocols and specifications that this feature must comply with.

The maximum number of subscribers that the MSOFTX3000 can support through the MPTY is six. three or more than three subscribers can take part in a session at the same time. Initiate a new call and hold the MPTY call. 6-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 6. which make the communications more convenient. the main controller.3 Benefits Beneficiary Carrier Mobile Subscriber Description The MPTY service can produce service increments. The user can hold a call conference as a main controller at any time.1 Service Description 6. Release an MPTY call. The served mobile subscriber. Disconnect a remote subscriber. Set up personal communications with the remote subscribers. When there is an MPTY call and a single call. alternate the two types of calls or add the single call to the MPTY call.2 Definition The served mobile subscriber is the mobile subscriber who can invoke the MPTY. Multiple subscribers can discuss together. The MPTY provides multiple call connections for one subscriber. In this case. the served mobile subscriber can realize the following functions: Hold the MPTY call and resume the call in subsequent sessions.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description 6. When a served mobile subscriber has an active call and an on-hold call. As for the MPTY calls.1. the served mobile subscriber can invoke the MPTY to combine the two calls to an MPTY call. namely. the served mobile subscriber can communicate with the remote subscriber. That is to say. session separation.1 Function Code Function Name Multiparty SS (MPTY) BOM WMFD-020500 6. The remote party is the party except the served mobile subscriber in the MPTY calls. controls the MPTY when the MPTY is active. and when both calls are answered.1.1. namely.

VLR and HLR. 6. 6.3 Working Principle 6.1 Requirements for NEs The MPTY features are realized by co-operations of the UE/MS. The feature service can be obtained only after the MSOFTX3000 license is obtained.2 Requirements for License The MPTY feature is an optional feature of HUAWEI wireless core network. Table 6-1 Network elements involved in MPTY features UE/MS √ NodeB/ BTS RNC/B SC MS C Server √ MGW √ SGSN VLR √ HLR √ √ indicates the network elements involved.2.3 Applicable Versions The applicable versions of MPTY features for HUAWEI CN are as listed in Table 6-2.2 Availability 6. MGW.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service 6. as listed in Table 6-1.2.2. Table 6-2 Applicable versions of the MPTY Product MS C Server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and subsequent versions V200R002 and subsequent versions 6. MS C Server.1 Functions Realized by Network Elements The functions of the NEs are as follows: The MS C server and the MGW cooperate with each other to process the MPTY service. Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-3 . The HLR stores and manages the subscriber data and service data.3. The HLR updates the subscription information stored in the VLR by inserting subscriber data.

The MS A sends the FACILITY message to the MS C. 3. And then. To invoke the MPTY. Adding a Remote Subscriber When subscriber A has an active single call (A-D) and an on hold MPTY call (A-B-C). the MS C connects A. set up a personal communication to B. The MS C responses to MS A with a message. perform the following steps.3. 2. to instruct the subscriber A to invoke the MPTY. B. 6-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .6 Multiparty Service HUAWEI MSOFTX3000 Feature Description 6. instructing the subscriber to hold the call. 3.3. it queries the subscription information of A. 4. The MS C sends a message to subscriber B. 3. If A subscribes to the MPTY. A talks with B. it applies the call conference resources if the single call meets the requirements of joining the MPTY call. 6.4 MPTY Call Management Setting up Personal Communications with Remote Subscriber When subscriber A has an active MPTY call (A-B-C). The HLR updates the subscription information stored in the VLR by inserting subscriber data. indicating the call is resumed. The MS A sends the FACILITY message to the MS C.3 MPTY Invocation When an on hold call (A-B) and an active call (A-C) are answered. After the MS C receives the message.3. The MS C applies the conference call resources that are used to connect subscriber A. 5. The MS C responses to the MS A with a message. C and D by using the call conference resources. 2. 6. B and C. After the MS C receives the message. The MS C response to MS A with a message.2 Service Data Management The HLR completes the service data management and modifies the stored subscription information of subscribers. 6. 4. To set up personal communications with remote subscribers. perform the following steps: 1. it holds the MPTY call and activates the call A-B. The MS C sends messages to other remote subscriber C subscribing the MPTY. perform the following steps: 1. 1. 2. subscriber A invokes the MPTY. 5. invoke the MPTY. instructing them to set up the MPTY. To add a remote subscriber. the MS C processes the MPTY service. to instructing the subscriber A to set up a personal communication with B. After the MS C receives the message. The MS C sends messages to B and C. The MS A sends the FACILITY message to MS C. to instruct the subscriber A to invoke the MPTY.

6. instructing D to take part in the MPTY service. to instruct the MS C to disconnect the call A-D. perform the following steps: 1. The subscriber A.4. the MPTY call (A-B-C) is an on hold call. perform the following steps: 1. The procedure of setting up the MPTY call is shown as Figure 6-1. The MS C sends message to D to release the call A-D between subscriber D and the MS C. The served mobile subscriber A sends disconnecting message to the MS C. B and C are the MSs under the same MS C server. and then sends message to D to instruct D to join the MPTY service. The remote subscriber disconnects a served mobile subscriber call.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service 4.1 Setting up the MPTY Call The carrier provides the MPTY for subscriber A. disconnecting a remote subscriber falls into the following two occasions: The served mobile subscriber disconnects a remote subscriber call. it disconnects the connections related to remote subscribers and releases the idle call conference resources. The remote subscriber D sends disconnecting message to the MS C. 4. 2. The MS C sends a message to D. 4. to instruct MS C to disconnect the call A-D. 3. The MS C sends message to the served mobile subscriber A to release the call A-D between the MS C and subscriber A. then the MS C sends message to B and C to indicate the call is resumed and instruct B and C to join the MPTY service. After the MS C receives the message. The MS C sends messages to subscriber B and C. To disconnect the call between the remote subscriber and the served mobile subscriber. Disconnecting a Remote Subscriber Based on different active disconnecting parties.4 Service Flow 6. 2. it disconnects the connections related to subscriber D and releases the idle call conference resources. After the MS C receives the message. 5. to instruct them that the call is resumed and they can take part in the MPTY service. The MS C sends message to A to release the call A-D between the MS C and the served mobile subscriber. If the single call (A-D) is an active call. The call A-B is on hold and the call A-C is active. To disconnect a remote subscriber by a served subscriber. 3. Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-5 . The MS C sends message to the disconnected remote subscriber to release the call A-D between subscriber D and the MS C.

The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B.4. the MS A sends a FACILITY message containing the BuildMPTY invoke component to the MS C server. The subscriber A. The MS C server sends the FACILITY message to the MS A. The call A-B-C is the MPTY call. The CallOnHold-indicator in the invoke component is callRetrieved. B and C are the MSs under the same MS C server. indicating that the request of setting up MPTY is accepted. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS C.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description Figure 6-1 Setting up the MPTY call MS A MS C Server MS B MS C CALL A-B on HOLD CALL A-C ACTIVE A wants to build a mutiparty call FACILITY FACILITY FACILITY FACILITY FACILITY MPTY CALL ACTIVE 1. The procedure of setting up the personal communication between A and B is shown as Figure 6-2. The invoke component contains the MPTYindicator. 6. 4. 6-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The invoke component contains the MPTYindicator. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B. informing the MS-B that the call is resumed. 3.2 Setting Up a Personal Communication with Remote Subscriber The carrier provides the MPTY for subscriber A. If A wants to set up a multi-party call. 5. 2.

2.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service Figure 6-2 Create a personal communication MS A MS C Server MPTY CALL A-B-C ACTIVE A wants to create private communication FACILITY FACILITY FACILITY MPTY CALL A-B-C on HOLD A-B CALL ACTIVE MS B MS C 1. The MS C server sends the FACILITY message to the MS A. 3. The procedure of adding subscriber D to the MPTY call is as shown Figure 6-3. 4. 6. C and D are the MSs under the same MS C server. If A wants to set up a new call. informing the MS C that the call is on hold. indicating that the request of SplitMPTY is accepted. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS C and MS B.3 Adding a Remote Subscriber The carrier provides the MPTY for subscriber A. The subscriber A. The MS C server activates the A-B call.4. The A-B-C is the MPTY call on hold and the A-D is the active single call. The CallOnHold-indicator in the invoke component is callOnHold. the MS A sends a FACILITY message containing the SplitMPTY invoke component to the MS C server. Figure 6-3 Add a remote subscriber MS A MS C Server MS B( or C ) MS D MPTY CALL A-B-C on HOLD A-D CALL ACTIVE A wants to add A-D call to MPTY call FACILITY FACILITY FACILITY FACILITY FACILITY MPTY CALL A-B-C-D ACTIVE Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-7 . B.

4. 4. The MS C server A sends a RELEASE message to the MS A to disconnect the A-D call at the wireless side. indicating the request of BuildMPTY is accepted. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-D. Figure 6-4 Disconnect the remote subscriber by main controller MS A MS C Server A MPTY CALL A-B-C-D ACTIVE A wants to disconnect A-D call DISCONNECT RELEASE RLC RELEASE COMPLETE MPTY CALL A-B-C ACTIVE REL PSTN D REL: Release RLC: Release Complete 1. the MS A sends a FACILITY message containing the BuildMPTY invoke component. 5. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B and MS C separately. When subscriber A wants to disconnect the A-D call. The CallOnHold-indicator in the invoke component is callRetrieved. The invoke component contains the MPTYindicator.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description 1. The invoke component contains the MPTYindicator.4 Disconnecting a Remote Subscriber Disconnecting a Remote Subscriber Call by the Served Mobile Subscriber The carrier provides the MPTY service for the subscriber A. The MS C server A sends a REL message to the PSTN C to disconnect the A-D call between the PSTN C and the PSTN D. The procedure for subscriber A to remove the subscriber D from the MPTY calls. 6. is as shown Figure 6-4. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B and MS C separately. The Transaction identifier in the message is instructed to remove the A-D call. 2. 2. the MS A sends a DISCONNECT message to the MS C server. When subscriber A wants to add a remote subscriber. informing the MS-B and MS C that the call is resumed. 6-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The A-B-C-D is the active MPTY call. to the MS C server. The MS C server sends the FACILITY message to the MS A. 3. 3.

6. see HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide. the PSTN D sends the REL message to the MS C server A. Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-9 . The MS A sends the RELEASE message to the MS C server A. The MS C server A sends a RELEASE COMPLETE message to the MS A to disconnect the A-D call at the wireless side.5.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service 4. The MS C server A sends a RLC message to the PSTN D to disconnect the A-D call between the MS C server A and the PSTN D. Removing Subscriber Disconnect the Call The carrier provides the MPTY service for the subscriber A. If subscriber D wants to disconnect the call. 2. The procedures for subscriber D to disconnect the call are as shown Figure 6-5. Figure 6-5 Disconnect the remote subscriber by main controller MS A MS C Server A MPTY CALL A-B-C-D ACTIVE D wants to disconnect A-D call REL DISCONNECT RELEASE RELEASE COMPLETE MPTY CALL A-B-C ACTIVE RLC PSTN D REL: Release RLC: Release Complete 1. 4. The MS C A sends a RELEASE COMPLETE message to the MS C server A to disconnect the A-D call at the wireless side. The PSTN D sends a RLC message to the MS C server A to disconnect the A-D call between the PSTN D and the MS C server A. 5. The Transaction identifier in the message instructs to remove the A-D call. The A-B-C-D is the active MPTY call. 3.1 Data Configuration at MSOFTX3000 Side For detailed operations of data configuration. 5.5 Data Configuration 6. to instruct it to disconnect the A-D call. The MS C server A sends a DISCONNECT message to the MS A.

Setting Tone Playing of Conference If it is required. Value =0:play tones =1:Not play tones Default Value 1 P174 (CM software parameter 7) Bit 8 =0: Support =1: Not support 1 P129 (CHG parameter 1) Bit 7 =0: Generate intermediate bill =1: Generate event bill 1 6. . Related Software Parameter Name P168 (CM software parameter 1) Bit 10 Definition When the main control party retrieves the MPTY. it controls whether the bills generated is outgoing intermediate bill or the event bill. When the times of control handover or the times of supplementary services operation is over the maximum times set by the system.5. it controls whether to play tones to prompt the remote subscriber to enter the conference. Controlling MPTY Service Bill You can control the bill generation of MPTY service by using the MOD GBILLCTRL command. 6-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . When the tone is required to be played by the call release initiated at the network side. set related data of playing conference tone by using the SET LOCALSRV command.2 Data Configuration at UMG8900 Side You can set the conference resources for the TCU board configured with the MVDB subboard by using the SET MPTYRES command. it controls whether to play tone suggesting the conference is entered.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description Enabling Service The service availability does not require special configuration data.

Table 6-4 MPTY service operation (For mobile subscriber) Type Release on-hold calls Release active calls and resume on hold calls Release the remote subscribers resources Step The subscriber dials 0 on the MS and press the "Send" button.6. and release all calls. see compatible operation manuals of HLR products used in the network at present. initiate a new call and hold the MPTY call. the service is cancelled when the service is deactivated. The subscriber dials 1 on the MS and press the "Send" button.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service 6. X is the sequence number of remote subscriber. As for the MPTY service. the service is provided when the service is activated. invoke the MPTY and add remote subscriber.6.6 Service Management There are two operating methods for the MPTY service. Steps For detailed operation steps. the service is provided when being activated. as listed in Table 6-3. see Table 6-4. alternate calls. release active calls and resume on-hold calls.2 Mobile Subscriber Operation Precondition The carrier provides the MPTY service to the subscribers.hold calls. set up personal communications with remote subscribers. 6. For detailed operations. Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-11 . release remote subscriber. and the service is cancelled when being deactivated. 6.1 Carrier Operation As for the MPTY service. Release o. It starts from 1 and increases based on the sequence of setting up or answering the calls for the served mobile subscriber. Table 6-3 Operation method for MPTY service Method Carrier operation Mobile subscriber operation Interface HLR Client MS Service Provide and cancel the MPTY service. The subscriber dials 1X on the MS and press the "Send" button.

The MSOTX3000 controls the mode created by bill. The subscriber dials 2 on the MS and press the "Send" button.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description Type Set up personal communications with remote subscriber Step The subscriber dials 2X on the MS and press the "Send" button. Then. and the frequency created by the event bill. subscriber A holds a call and calls the subscriber C in other offices. The mark and time stamp of MPTY are added to the latter segment of bill. Alternate calls Invoke the MPTY and add the remote subscriber Initiate a new call and keep the MPTY call Release all calls Some mobile phone can realize the operations list above. the independent charging is adopted. or intermediate bill through the CHG parameter 1 (P129) Bit 7 and integrated control table of bill. X is the sequence number of remote subscriber. The subscriber dials 3 on the MS and press the "Send" button. The charging center combines the bills or processes the other charging. see the mobile phone instructions. the final MOC/MTC is generated. In the following occasions. The segmented bill indicates that the MSOTX3000 generates a group of intermediate bill of the MOC/MTC based on the time interval between the BuildMPTY and the SplitMPTY operations. Press "Release" button on the MS. The independent charging indicates that the MSOTX3000 generates the following two kinds of bills based on the BuildMPTY and SplitMPTY operations: Event bill containing the MPTY mark and time stamp Original bill of MOC/MTC for complete A-B and A-C calls The iGWB inserts the contents of event bill to the corresponding supplementary service field for original bill of the MOC/MTC. independent charging and segmented charging. For detailed operations. During the communications of A-B. 6. The following is an independent charging case for MPTY call. The subscribers A under the MS C server calls the subscriber B in other offices.7 Charging and CDR There are two modes to generate the bill of MPTY service for the MSOTX3000. The subscriber dials the number of new subscriber on the MS and press "Send" button. It starts from 1 and increases based on the sequence of setting up or answering the calls for the served mobile subscriber. 6-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . In usual cases.

the forwarding subscriber hears rings and is added to the conference if the forwarding meets the trigger conditions. The local office is the MOC bills created by the A-B call. the outgoing call made after activation of the BO service is to be barred if the call meets the barring requirements. the forwarding call existed is added to the conference as a connection of the MPTY call. When the subscriber sets the MPTY call to on hold. There is one supplementary service operation record in the supplementary service field of the bill. the subscriber receives a call on hold notice when other subscribers call the subscriber. MPTY and Forwarding services Issue 02 (2007-06-10) Huawei Technologies Proprietary 6-13 .8 Service Interaction For the interactions between the MPTY and the other services is listed in Table 6-5. MPTY and CW The MPTY and CW do not affect each other. the subscriber can answer the call on hold. Table 6-5 Interactions between the MPTY and the other services Service MPTY and CLIP Interaction No matter when a served mobile subscriber adds a new remote subscriber to an MPTY call. One indicator of supplementary service is CH and the time stamp is the time for the subscriber A sending the HOLD message. the remote subscriber subscribing the CLIP and involving the MPTY service cannot receive the number of remote subscriber newly added. 6. the other indicator of supplementary service is the MPTY and the time stamp is the time that the subscriber A sends the FACILITY message containing the BuildMPTY information.HUAWEI MSOFTX3000 Feature Description 6 Multiparty Service Subscriber C answers the call and sets up the MPTY call. MPTY and CH Subscribing CH service is the prerequisite of subscribing the MPTY service. If a subscriber activates a MPTY call. the outgoing call of the MPTY is not affected by the BO service. Forwarding subscriber: When the forwarding subscriber sets up the MPTY call. The calling party: When the calling party tries to set up the MPTY call with the called party subscribing the call forwarding service. If a subscriber activates a MPTY call. The time stamp is the time that subscriber A sends the FACILITY message containing the BuildMPTY. the subscriber (the served subscriber or the remote subscriber) is allowed to hold the MPTY call and resume the call. However. The record indicator of supplementary service operations is the MPTY. The MPTY and the forwarding services do not affect each other. There are two supplementary service operation records in the supplementary service field of the bill. MPTY and BO If the BO service is activated after invoking the MPTY call. The MOC bill is created by the local A-C call.

084 V4. the incoming call of the MPTY is not affected by the BI service.0 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide 6.. 6.9.1 Protocols and Specifications The references of the feature are list as follows: 3GPP TS 22.2 Acronyms and Abbreviations Acronym/Abbreviation 3GPP CH CLIP CLIR CM CN CW MOC MPTY MTC Full Name 3rd Generation Partnership Project Call Holding Calling Line Identification Presentation Calling Line Identification Restriction Call Management Core Network Call Waiting Mobile Originated Call MultiParty Service Mobile Terminated Call 6-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the incoming call made after activation of BI service is to be barred if the call meets the barring requirements.0 3GPP TS 24.6 Multiparty Service HUAWEI MSOFTX3000 Feature Description Service MPTY and BI Interaction If the BI service is activated after invoking the MPTY call.9 Reference 6.084 V4. However.0.9.1.084 V4.1.0 3GPP TS 23.

...........................7-2 7.....................1 Function Code.7-18 7...............7-21 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .....9..........................1 BAOC .................5.................................................................7 Charging and CDR ....................................................................................2................4 BAIC................................3 BI ..5 Data Configuration...........1................7-10 7..............2 Configuring Data at the HLR Side............3............................7-17 7.....................................................................................1.........................6...........3.....6..............................1 Requirements for NEs... 7-11 7.......................................7-3 7...........6 Service Management .........................................................................8.......8 Service Interaction .........................................7-21 7..................................7-15 7..................................8...............................................7-15 7....................................................................8..............................4..........................................7-15 7................................................7-3 7.....................................................................................................................................................................................................................7-10 7........5 BIC-ROAM .........................3 Working Principle..................................................................1 Service Description ..................2 Availability .........................................7-13 7.....................................7-12 7.....................................................................................................................3 BOIC-exHC ....................................1 Protocols and Specifications ...................................................................................................................................................2 Definition .............................................................................................................................................................................................................................7-12 7....................................................................................................2 BOIC.................................................................................7-8 7...2 BO..................................................7-13 7...........9 Reference ...............................................................................................7-13 7......................................................................................7-3 7.................7-4 7..............................................................................................................7-2 7................3 Applicable Versions....................................................1 Configuring Data at the MSOFTX3000 Side.......7-3 7....2...............................................1..................HUAWEI MSOFTX3000 Feature Description Contents Contents 7 Call Barring Service ..........................................................................................7-4 7..............................2 BI .........................................1 BO......................................................................7-2 7..8..................................................................................3....................................................................................................................................................................................................1.....................................................1 Service Data Management ......3 Types .8....7-13 7.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................2..........7-1 7..................................2 Requirements for License .................................................................2 Operations by Mobile Subscribers ......7-4 7...........................................................7-19 7.4...........................................................................7-2 7.................................4 Service Flow.......7-4 7...1 Operations by Carriers .................................................................................5...7-15 7..................................................................4 Benefits .....................................................................................................................................

........7-21 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .........................................................Contents HUAWEI MSOFTX3000 Feature Description 7.....................2 Acronyms and Abbreviations ....................9......

...................................................................................................7-8 Figure 7-5 Check flow of the HLR for the BIC-ROAM service ...........................7-9 Figure 7-6 BO service flow .........................................................................................................................................7-6 Figure 7-3 Check flow of the VLR for the BOIC-exHC service ..................................................7-7 Figure 7-4 Check flow of the HLR for the BAIC service ................................................................................................7-5 Figure 7-2 Check flow of the VLR for the BOIC service...................................................7-10 Figure 7-7 BI service flow.................................................. 7-11 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ...............................................................................................................HUAWEI MSOFTX3000 Feature Description Figures Figures Figure 7-1 Check flow of the VLR for the BAOC service ........................

........................................7-3 Table 7-3 Applicable versions of Huawei wireless core network products ........................................................................7-18 Table 7-10 Interactions between the BIC-ROAM service and other services ......................7-13 Table 7-5 Operations performed by mobile subscribers ...............................................................................................................................7-17 Table 7-9 Interactions between the BAIC service and other services.....................7-2 Table 7-2 NEs required by the call barring services .........................................................................................................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 7-1 Name and code of the function...........7-15 Table 7-7 Interactions between the BOIC service and other services...................................................................................................................7-13 Table 7-6 Interactions between the BAOC service and other services ........................................7-16 Table 7-8 Interactions between the BOIC-exHC service and other services ........................................................7-19 iv Huawei Technologies Proprietary Issue 02 (2007-06-10) ......7-4 Table 7-4 Operation modes of the call barring supplementary services .......................................................................

and the benefits that carriers and mobile subscribers can obtain from this feature. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-1 . The charging and the generation of CDRs when the network provides this feature.8 Service Interaction 7.7 Charging and CDR 7. The protocols and specifications that this feature must comply with.9 Reference Describes Call Barring Service The following table lists the contents of this chapter.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service 7 About This Chapter Section 7. whether Licenses are required. function definition of this feature. and the version requirements of the NEs. The service flow of the network when providing this feature.3 Working Principle 7. and the acronyms and abbreviations of this chapter. The relationships and restrictions between this feature and other services or features. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The functions of the NEs.2 Availability 7. The network elements (NEs) that are required for the feature.4 Service Flow 7.1 Service Description 7.5 Data Configuration 7. The data configurations that are required on the MSOFTX3000 and the UMG8900. and networking requirements. The function code.6 Service Management 7.

the subscriber can call only subscribers (mobile subscribers or fixed network subscribers) in homing countries.) The BI service includes: Barring of All Incoming Calls (BAIC is for short. 7. 7-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . a mobile subscriber cannot call any subscribers outside the country (homing to the PLMN) where the caller roaming. BOIC-exHC After the service is activated. Table 7-1 Name and code of the function Name Call barring services Code WMFD-020400 7. a mobile subscriber cannot initiate calls.1 Service Description 7.1 Function Code Table 7-1 lists the name and code of the function.) Barring of Incoming Calls When Roaming Outside Home PLMN Country (BIC-ROAM is for short.2 Definition Call barring supplementary services allow mobile subscribers to perform barring for incoming or outgoing calls with special properties.1.1.) Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC is for short.) Barring of All Outgoing International Calls (BOIC is for short. After the subscriber is roaming outside the country homing to the PLMN. The BO service includes: Barring of All Outgoing Calls (BAOC is for short. a mobile subscriber cannot call any subscriber (including mobile subscriber or fixed network subscriber) outside the country where the caller is.1.) BAOC After the service is activated. BOIC After the service is activated.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description 7.3 Types Call barring services are classified into two types: barring of outgoing calls (BO) and barring of incoming calls (BI).

BTS = base transceiver station.2. 7. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-3 . a mobile subscriber cannot receive calls when the subscriber is roaming outside the country homing to the PLMN. HLR = home location register The symbol √ indicates that the corresponding NE is required. BIC-ROAM After the service is activated.2. Subscribes can perform activation/deactivation operation.indicates that the corresponding NE is not required. VLR = visitor location register. BSC = base station controller. subscribers can activate or deactivate call barring services through their handsets.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service BAIC After the service is activated. thus to control incoming/outgoing calls flexibly.2 Requirements for License The call completion supplementary services are basic services of Huawei wireless core network. subscribes can bar some type of incoming/outgoing calls. Subscribers can select one or several types of call barring service.1. No license is needed. The hyphen .2 Availability 7.1 Requirements for NEs Table 7-2 lists the network elements (NEs) required by the call barring services. In advance. 7. SGSN = serving GPRS support node. MGW = media gateway. a mobile subscriber cannot receive calls. password must be provided. MSC = mobile switching center. After the system provides the call barring service.4 Benefits Beneficiary Carriers Mobile subscribers Description The call barring supplementary services add values of services. If the service controller is set to subscribers. 7. MS = mobile station. RNC = radio network controller. Table 7-2 NEs required by the call barring services UE/MS √ NodeB/BTS √ RNC/BSC √ MSC server √ MGW √ SGSN VLR √ HLR √ Note: UE = user equipment.

Modifies the subscription information that it stores.2.3 Applicable Versions Table 7-3 lists the applicable versions of Huawei wireless core network products that the call barring services support. and then updates the subscription information in the VLR by inserting subscriber data. the MSC transparently sends the operation message to the HLR.3. The MSC transparently sends the registration operation message to the HLR.1 Service Data Management Management on Service Data The HLR performs the following functions: Completes the management operations of carriers on service data.2 BO The following section describes the working principle of the BO service.8 "Service Interaction. The MSC initiates the operation of fetching subscriber information for outgoing call to the VLR. 7-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . see section 7.3. Registration If the service controller of the call barring services is subscribers. The HLR modifies the subscription information that it stores based on the message.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description 7. when a subscriber initiates activation or deactivation operation. For details. Updates the subscription information in the VLR by inserting subscriber data. A subscriber initiates a call. Activation and Deactivation If the service controller of the call barring services is subscribers. the activation may fail." 7. and then updates the subscription information in the VLR by inserting subscriber data If the activated call barring service conflicts with other activated services. Table 7-3 Applicable versions of Huawei wireless core network products Product MSC server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V200R002 and later versions 7.3 Working Principle 7. subscribers can modify the password used for service control through registration.

see Figure 7-1. Figure 7-2 and Figure 7-3. the MSC processes the call according to normal flow. Then the VLR sets the call barring indication based on the check result and sends the indication to the MSC. If the call barring indication is Yes. The MSC determines whether to perform call barring based on the call barring indication. Figure 7-1 Check flow of the VLR for the BAOC service idle initiate handling of BAOC emergency call Yes activated for basic service No set barring indicator ='yes' set barring indicator ='no' continue call handling idle Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-5 . BOIC and BOIC-exHC services. For service check procedures by the VLR for BAOC. if the call barring indication is No.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service The VLR checks the service based on BO information of the subscriber and call property of the outgoing call. the MSC releases the call.

7 Call Barring Service HUAWEI MSOFTX3000 Feature Description Figure 7-2 Check flow of the VLR for the BOIC service idle initiate handling of BOIC Yes emergency call No international call activated for basic service No set barring indicator ='yes' set barring indicator ='no' continue call handling idle 7-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

subscribers can still call special numbers when the BO service is activated. every service check flow is executed. The MSOFTX3000 can suppress BO service check for special prefix based on the service check configuration in configuration data. Thus.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service Figure 7-3 Check flow of the VLR for the BOIC-exHC service idle initiate handling of BOICexHC Yes emergency call No international call destination in HPLMN country Yes activated for basic service No set barring indicator ='yes' set barring indicator ='no' continue call handling idle If the MS activates multiple BO services. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-7 .

see Figure 7-4 and Figure 7-5. The (G)MSC initiates the operation of fetching route information to the HLR.3. A subscriber initiates a call. if the call barring indication is No. If the call barring indication is Yes. The HLR determines whether to perform call barring based on the call barring indication. Then the HLR sets the call barring indication based on the check result. For service check procedures by the HLR for BAIC and BIC-ROAM services. The HLR checks the service based on BI information of callee and call property of the incoming call.3 BI The following section describes the working principle of the BI service. the HLR processes the call according to normal flow. the HLR indicates to reject the call in the response to the operation of fetching route information. Figure 7-4 Check flow of the HLR for the BAIC service idle initiate handling of BAIC activated for basic service Yes set barring indicator ='yes' No set barring indicator ='no' continue call handling idle 7-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) .7 Call Barring Service HUAWEI MSOFTX3000 Feature Description 7.

every service check flow is executed.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service Figure 7-5 Check flow of the HLR for the BIC-ROAM service idle initiate handling of BIC-ROAM Yes emergency call international call No activated for basic service No set barring indicator ='yes' set barring indicator ='no' continue call handling idle If the MS activates multiple BO services. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-9 .

3. The SS-Code of the component refers to service code of the BO service. Figure 7-6 BO service flow MS MSC server MSC server/ PSTN SETUP RELEASE COMPLETE OR1: Yes Facility (Invoke = NotifySS (SSOR1: No Code. The MS sends the SETUP message to the MSC server.4 Service Flow 7. 7-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . For service check procedures. The parameter Facility contains invocation component of NotifySS operation. The MSC determines whether to perform call barring based on the call barring indication. SS-Status)) IAM OR1: call barred IAM: Initial Address Message 1. the MSC processes the call according to normal flow. Figure 7-2 and Figure 7-3.1 BO Figure 7-6 shows the BO service flow. The VLR of the MSC server checks the service based on BO service information and call property. The SS-Status indicates that the BO service is in activated or deactivated status. 4. If the call barring indication is No. If the call barring indication is Yes. Then the VLR sets call barring indication based on the check result. see Figure 7-1.4.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description 7. 2. the MSC sends the RELEASE COMPLETE message or other release message to the MS to release the call. 5.

the HLR processes the call according to normal flow. the HLR b sends the SRI ack message to the (G)MSC server. 6. If the caller is an MS. The HLR b checks the service based on BI service information and call property. The (G)MSC server initiates the SRI operation to the HLR b that callee homes. Then the MSC server b releases the call according to normal flow that is omitted in the figure. 2. the GMSC server sends release message (such as the REL message) to caller office and releases the call according to normal flow that is omitted in the figure. If the call barring indication is Yes. Then the HLR b sets call barring indication based on the check result.4. the PSTN office sends originated call message (such as the IAM message) to the GMSC server through trunk signaling. see Figure 7-4 and Figure 7-5. 5.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service 7. Figure 7-7 BI service flow MS/PSTN (G)MSC server HLRb MSC server b SETUP or IAM SRI OR1: Yes SRI ack(user error=CallBarred) clearing message OR1: No PRN PRN ack SRI ack(MSRN) IAM OR1: call barred SRI: Send Routing Information ack: Acknowledge PRN: Provide Roaming Number IAM: Initial Address Message 1. the MSC server b sends the RELEASE COMPLETE or other release message to the MS. 7. If the call barring indication is No. after receiving the SRI ack message. 3. The parameter User error in the message is Callbarred. If the caller is a fixed network subscriber. 4. the MS sends the SETUP message to the MSC server. If the caller is a fixed network subscriber. For service check procedure. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-11 . If a caller is an MS.2 BI Figure 7-7 shows the voice BI service flow.

BOIC or BOIC_EXHC. Enabling the Service No additional data is required to enable the service. SCM=ODB_BAOC-1&BAOC-1&ODB_BOIC-1&BOIC-1. ISERVICECHECKNAME="NOCHECK". The procedure is as follows: Step 1 Run ADD SRVCHK to define a service check configuration. = 1: Enable forced release function of the supplementary service at once. MAXL=3. ----End The following table lists an example: Description Script BAOC.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description 7. the value of the parameter ISERVICECHECKNAME is the one of SCN that is set in step 1. Default Value 0 7-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Checking the Service The MSOFTX3000 can suppress the BO service for special prefix and special call source through service check configuration. ADD CNACLD: PFX=K'110. if the added supplementary service is BAOC. Of it. IFSC=YES. SCN="NOCHECK". SCC=ODB_BAOC-0&BAOC-0&ODB_BOIC-0&BOIC-0. Step 2 Run ADD CNACLD or MOD CNACLD to set a call prefix. the forced release flow will be initiated to subscribers in conversation. Related Software Parameters Name P140 (VLR software parameter) Bit 5 Meaning It indicates enabling forced release function of the supplementary service at once. Value = 0: Not enable forced release function of the supplementary service. see the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide. That is.5 Data Configuration 7. Of it. BOIC. MINL=3. the value of BO service item of the parameter SCM is 1. ODB_BAOC and ODB_BOIC subscribers are allowed to dial 110. ADD SRVCHK: CSCNAME="ALL". the value of BO service item of the parameter SCC is 0.5.1 Configuring Data at the MSOFTX3000 Side For the details of data configuration.

Withdraw the service.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service 7.6 Service Management The call barring supplementary services have two operation modes. Register the service. 7. dial "**03*330*oldPW*newPW*newPW#".6. see the corresponding operation manual of the HLR. Operation by mobile subscribers MS Register the service Activate the service. 7. Table 7-4 Operation modes of the call barring supplementary services Operation Mode Operation by carriers Operation Interface HLR9820 SMU Client Service Operations Provide the service. Operations On the MS. as listed in Table 7-4.2 Operations by Mobile Subscribers Prerequisite The controller of call barring services is subscribers. Deactivate the service. Modify the service control right. Of it. mobile subscribers can perform the operations listed in Table 7-5. oldPW refers to old password of the call barring service and newPW refers to new password of the call barring service. Deactivate the service.2 Configuring Data at the HLR Side No data related to the service needs to be configured at the HLR side. Step On the MS. Activate the service. 7.1 Operations by Carriers For details. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-13 .5. Table 7-5 Operations performed by mobile subscribers Operation Type Modify call barring service password. and then press the Send key.6.

and then press the Send key. On the MS. On the MS. and then press the Send key. PW refers to call barring service password. and then press the Send key. dial "#330*PW#". Deactivate the BAOC service. PW refers to call barring service password. Deactivate the BIC-Roam service. dial "#353*PW#". and then press the Send key. On the MS. On the MS. Deactivate the BOIC service. On the MS. On the MS. Activate the BOIC service. dial "*331*PW#". dial "#331*PW#". Deactivate all call barring services. Of it.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description Operation Type Activate the BAOC service. The call barring service password is 0000 by default. On the MS. dial "*351*PW#". Of it. and then press the Send key. dial "*35*PW#". Step On the MS. Deactivate all BO services. Of it. PW refers to call barring service password. Deactivate the BOIC-ExHC service. and then press the Send key. On the MS. Of it. Of it. Of it. On the MS. PW refers to call barring service password. and then press the Send key. PW refers to call barring service password. Of it. PW refers to call barring service password. PW refers to call barring service password. Of it. and then press the Send key. PW refers to call barring service password. 7-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . PW refers to call barring service password. dial "#351*PW#". and then press the Send key. dial "#35*PW#". On the MS. For details. Of it. see the user manuals of the mobile phones. Subscribers can also perform the operations through the menus of some mobile phones. Of it. PW refers to call barring service password. PW refers to call barring service password. and then press the Send key. and then press the Send key. On the MS. dial "#332*PW#". PW refers to call barring service password. dial "#33*PW#". Deactivate the BAIC service. On the MS. and then press the Send key. PW refers to call barring service password. dial "*33*PW#". Of it. Of it. Activate the BOIC-ExHC service. Deactivate all BI services. and then press the Send key. Of it. dial "*332*PW#". dial "#333*PW#". Activate the BAIC service. Activate the BIC-Roam service.

7. a subscriber activates the BAOC service.8. Issue 02 (2007-06-10) Huawei Technologies Proprietary 7-15 . The BAOC service enjoys higher priority than the CUG service. BAOC and MPTY After invoking an MPTY call. If a subscriber activates the forwarding service.7 Charging and CDR The call barring services cause call failure. After initiating a call that is in call hold status. When a caller activates the BAOC service. The held call still can be invoked. it is prohibited to register or activate the forwarding service.2 BOIC Table 7-7 lists the interactions between the BOIC service and other services. a caller activates the BAOC service.HUAWEI MSOFTX3000 Feature Description 7 Call Barring Service 7.8. BAOC and CH The BAOC and CH services are compatible. Table 7-6 Interactions between the BAOC service and other services Service BAOC and CFU. BAOC and CUG 7. All new outgoing calls are inhibited. But all new outgoing calls are inhibited. Therefore. During an outgoing call. it is prohibited to activate the BAOC service. BAOC and CW The BAOC and CW services are compatible. CFB. CFNRy and CFNRc Interaction The forwarding and BAOC services are incompatible.8 Service Interaction 7. no waiting call that has been initiated is affected. If a subscriber activates the BAOC service. no CDR is generated for failed call.1 BAOC Table 7-6 lists the interactions between the BAOC service and other services. All outgoing calls in the MPYT call are not affected. a caller activates the BAOC service without affecting any CUG calls.

the CFB service auto changes to available. the BOIC service cannot be activated. All outgoing calls in the MPYT call are not affected. BOIC and CFNRy If a subscriber activates the BOIC service. If the CFB service is registered to a home country number and both CFB and BOIC services are activated. or the subscriber comes back to the home country. If a subscriber activates the CFNRy service to an international number. BOIC and CW BOIC and MPTY BOIC and CH The BOIC and CW services are compatible. BOIC and CFNRc If a subscriber activates the BOIC service. The held call still can be invoked. The BOIC and CH services are compatible. when a subscriber is roaming to another country. After invoking an MPTY call. After initiating an international call that is in call hold status. the CFNRc service is unavailable. When a caller activates the BOIC service. If the BOIC service is deactivated later. BOIC and CFB If a subscriber activates the BOIC service. the BOIC service cannot be activated. the BOIC service cannot be activated. the CFB service is unavailable. the BOIC service cannot be activated. the CFNRy service auto changes to available. If a subscriber activates the CFNRc service to an international number. If a subscriber activates the CFU service to an international number. But all new outgoing international calls are inhibited. a subscriber activates the BOIC service. If the CFNRy service is registered to a home country number and both CFNRy and BOIC services are activated.7 Call Barring Service HUAWEI MSOFTX3000 Feature Description Table 7-7 Interactions between the BOIC service and other services Service BOIC and CFU Interaction If a subscriber activates the BOIC service. or the subscriber comes back to the home country. the CFNRy service is unavailable. the CFNRc service registered and activated to an international number is rejected. the CFNRc service auto changes to available. when a subscriber is roaming to another country. the CFU service registered and activated to an international number is rejected. If a subscriber activates the CFB service to an international number. All new outgoing international calls are inhibited. the CFNRy service registered and activated to an international number is rejected. when a subscriber is roaming to another country. If the BOIC service is deactivated later. or the subscriber comes back to the home country. 7-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the CFB service registered and activated to an international number is rejected. any waiting international call that has been initiated is affected. If the BOIC service is deactivated later. a caller activates the BOIC service. If the CFNRc service is registered to a home country number and both CFNRc and BOIC services are activated.

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

Service BOIC and CUG

Interaction The BOIC service enjoys higher priority than the CUG service. During an outgoing international call, a caller activates the BOIC service without affecting any CUG calls.

7.8.3 BOIC-exHC
Table 7-8 lists the interactions between the BOIC-exHC service and other services. Table 7-8 Interactions between the BOIC-exHC service and other services Service BOIC-exHC and CFU Interaction If a subscriber activates the BOIC-exHC service, the CFU service registered and activated to numbers except the HPLMN number is rejected. If a subscriber activates the CFU service to numbers except the HPLMN number, the BOIC-exHC cannot be activated. BOIC-exHC and CFB If a subscriber activates the BOIC-exHC service, the CFB service registered and activated to numbers except the HPLMN number is rejected. If a subscriber activates the CFB service to numbers except the HPLMN number, the BOIC-exHC cannot be activated. If the CFB service is forwarded to an HPLMN number and both CFB and BOIC-exHC services are activated, when a subscriber is roaming to another PLMN, the CFB service is unavailable. If the BOIC-exHC service is deactivated later, or the subscriber comes back to the HPLMN, the CFB service auto changes to available. BOIC-exHC and CFNRy If a subscriber activates the BOIC-exHC service, the CFNRy service registered and activated to numbers except the HPLMN number is rejected. If a subscriber activates the CFNRy service to numbers except the HPLMN number, the BOIC-exHC cannot be activated. If the CFNRy service is forwarded to an HPLMN number and both CFNRy and BOIC-exHC services are activated, when a subscriber is roaming to another PLMN, the CFNRy service is unavailable. If the BOIC-exHC service is deactivated later, or the subscriber comes back to the HPLMN, the CFNRy service auto changes to available.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-17

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

Service BOIC-exHC and CFNRc

Interaction If a subscriber activates the BOIC-exHC service, the CFNRc service registered and activated to numbers except the HPLMN number is rejected. If a subscriber activates the CFNRc service to numbers except the HPLMN number, the BOIC-exHC cannot be activated. If the CFNRc service is forwarded to an HPLMN number and both CFNRc and BOIC-exHC services are activated, when a subscriber is roaming to another PLMN, the CFNRc service is unavailable. If the BOIC-exHC service is deactivated later, or the subscriber comes back to the HPLMN, the CFNRc service auto changes to available.

BOIC-exHC and CW BOIC-exHC and MPTY BOIC-exHC and CH

The BOIC-exHC and CW services are compatible. When a caller activates the BOIC-exHC service, any waiting international call that has been initiated to outside HPLMN is affected. After invoking an MPTY call, a subscriber activates the BOIC-exHC service. All outgoing calls in the MPYT call are not affected. All new outgoing international calls to outside HPLMN are inhibited. The BOIC-exHC and CH services are compatible. After initiating an international call that is in call hold status to outside HPLMN, a caller activates the BOIC-exHC service. The held call still can be invoked. But all new outgoing international calls to outside HPLMN are inhibited. The BOIC-exHC service enjoys higher priority than the CUG service. During an outgoing international call to outside HPLMN, a caller activates the BOIC-exHC service without affecting any CUG calls.

BOIC-exHC and CUG

7.8.4 BAIC
Table 7-9 lists the interactions between the BAIC service and other services. Table 7-9 Interactions between the BAIC service and other services Service BAIC and CFU, CFB, CFNRy and CFNRc Interaction The forwarding and BAIC services are incompatible. If a subscriber activates the forwarding service, it is prohibited to activate the BAIC service. If a subscriber activates the BAIC service, it is prohibited to activate the forwarding service. BAIC and CW The BAIC service enjoys higher priority than the CW. When the BAIC service is activated, the CW service cannot be activated. The activation of the BAIC service does not affect any waiting call.

7-18

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

Service BAIC and MPTY

Interaction After invoking an MPTY call, a subscriber activates the BAIC service. All incoming calls in the MPYT call are not affected. All new incoming calls are inhibited. The BAIC and CH services are compatible. If an incoming call has been in call hold status, a callee activates the BAIC service. The held call still can be invoked. But all new incoming calls are inhibited.

BAIC and CH

BAIC and CUG

The BAIC service enjoys higher priority than the CUG service. During receiving incoming call, a callee activates the BAIC service without affecting any CUG calls.

7.8.5 BIC-ROAM
Table 7-10 lists the interactions between the BIC-ROAM service and other services. Table 7-10 Interactions between the BIC-ROAM service and other services Service BIC-ROAM and CFU Interaction The CFU service enjoys higher priority than the BIC-ROAM service. If a subscriber has activated the BIC-ROAM service, when the subscriber activates the CFU service, the activation can be successful. But the BIC-ROAM service changes to static status. If a subscriber has activated the CFU service, when the subscriber registers the BIC-ROAM service, the activation is unsuccessful. BIC-ROAM and CFB If a subscriber has activated the BIC-ROAM service and the BIC-ROAM service is in operational status, when the subscriber activates the CFB service, the activation is rejected. If a subscriber has activated the BIC-ROAM service but the BIC-ROAM service is in static status, the CFB service can be activated after registration. If the BIC-ROAM service changes to operational status later, the CFB auto changes to static status. If a subscriber is roaming outside HPLMN and the subscriber activates the CFB service that is in operational status, it is prohibited to activate the BIC-ROAM service. If a subscriber is roaming outside HPLMN and the subscriber activates the CFB service that is in static status, the BIC-ROAM can be activated.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-19

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

Service BIC-ROAM and CFNRy

Interaction If a subscriber has activated the BIC-ROAM service and the BIC-ROAM service is in operational status, when the subscriber activates the CFNRy service, the activation is rejected. If a subscriber has activated the BIC-ROAM service but the BIC-ROAM service is in static status, the CFNRy service can be activated after registration. If the BIC-ROAM service changes to operational status later, the CFNRy auto changes to static status. If a subscriber is roaming outside HPLMN and the subscriber activates the CFNRy service that is in operational status, it is prohibited to activate the BIC-ROAM service. If a subscriber is roaming outside HPLMN and the subscriber activates the CFNRy service that is in static status, the BIC-ROAM can be activated.

BIC-ROAM and CFNRc

If a subscriber has activated the BIC-ROAM service and the BIC-ROAM service is in operational status, when the subscriber activates the CFNRc service, the activation is rejected. If a subscriber has activated the BIC-ROAM service but the BIC-ROAM service is in static status, the CFNRc service can be activated after registration. If the BIC-ROAM service changes to operational status later, the CFNRc auto changes to static status. If a subscriber is roaming outside HPLMN and the subscriber activates the CFNRc service that is in operational status, it is prohibited to activate the BIC-ROAM service. If a subscriber is roaming outside HPLMN and the subscriber activates the CFNRc service that is in static status, the BIC-ROAM can be activated.

BIC-ROAM and CH

The BIC-ROAM and CH services are compatible. When a callee is roaming outside an HPLMN and the callee activates the BIC-ROAM service, if an incoming call has been in call hold status, the held call still can be invoked. But all new incoming calls are inhibited. When a subscriber is roaming outside an HPLMN, if the subscriber activates the BIC-ROAM service after invoking an MPTY call, all incoming calls in the MPYT call are not affected. All new incoming calls are inhibited. The BIC-ROAM service enjoys higher priority than the CUG service. If a callee is roaming outside an HPLMN, during receiving incoming call, the callee activates the BIC-ROAM service without affecting any CUG calls.

BIC-ROAM and MPTY

BIC-ROAM and CUG

7-20

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

7.9 Reference
7.9.1 Protocols and Specifications
This following specifications and manuals are referred to: 3GPP TS 22.088 V4.1.0 3GPP TS 23.088 V4.1.0 3GPP TS 24.088 V4.0.2 3GPP TS 24.008 V4.15.0 3GPP TS 29.002 V4.15.0 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide HUAWEI HLR9820 Home Location Register Operation Manual – Subscriber Management

7.9.2 Acronyms and Abbreviations
Acronym/Abbreviation BO BI BAOC BOIC BOIC-exHC BAIC BIC-ROAM Full Name Barring of outgoing calls Barring of incoming calls Barring of All Outgoing Calls Barring of All Outgoing International Calls Barring of Outgoing International Calls except those directed to the Home PLMN Country Barring of All Incoming Calls Barring of Incoming Calls When Roaming Outside Home PLMN Country

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-21

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
8 Explicit Call Transfer Service ..................................................................................................8-1
8.1 Service Description .......................................................................................................................................8-2 8.1.1 Function Code......................................................................................................................................8-2 8.1.2 Definition .............................................................................................................................................8-2 8.1.3 Benefits ................................................................................................................................................8-2 8.2 Availability ....................................................................................................................................................8-3 8.2.1 Requirements for NEs..........................................................................................................................8-3 8.2.2 Requirements for License ....................................................................................................................8-3 8.2.3 Applicable Versions..............................................................................................................................8-3 8.3 Working Principle..........................................................................................................................................8-3 8.3.1 Functions of Each NE ..........................................................................................................................8-3 8.3.2 Service Data Management ...................................................................................................................8-3 8.3.3 Invoking the ECT.................................................................................................................................8-4 8.4 Service Flow..................................................................................................................................................8-4 8.4.1 A-B Call Is on Hold and A-C Call Is in the Active State .....................................................................8-4 8.4.2 A-B Call Is in the Active State and A-C Call Is in the Alerting State...................................................8-5 8.5 Data Configuration........................................................................................................................................8-7 8.5.1 Data Configuration on the MSOFTX3000...........................................................................................8-7 8.5.2 Data Configuration on the UMG8900..................................................................................................8-7 8.6 Service Management .....................................................................................................................................8-8 8.6.1 Operation Mode ...................................................................................................................................8-8 8.6.2 Operations by the Carriers ...................................................................................................................8-8 8.6.3 Operations by the Mobile Subscribers .................................................................................................8-8 8.7 Charging and CDR ........................................................................................................................................8-9 8.7.1 Introduction to the Charging Mode......................................................................................................8-9 8.7.2 Independent Charging ..........................................................................................................................8-9 8.7.3 Segmented Charging ..........................................................................................................................8-10 8.8 Service Interaction ......................................................................................................................................8-12 8.9 Reference ....................................................................................................................................................8-13 8.9.1 Protocols and Specifications ..............................................................................................................8-13 8.9.2 Acronyms and Abbreviations .............................................................................................................8-14

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 8-1 Invoking the ECT when A-B call is on hold and A-C call is in the active state................................8-5 Figure 8-2 Invoking the ECT when C is in the alerting state .............................................................................8-6

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 8-1 Function code of the ECT...................................................................................................................8-2 Table 8-2 Benefits of the ECT ............................................................................................................................8-2 Table 8-3 Requirements for NEs ........................................................................................................................8-3 Table 8-4 Applicable versions ............................................................................................................................8-3 Table 8-5 Parameters of the related software......................................................................................................8-7 Table 8-6 ECT operation mode...........................................................................................................................8-8 Table 8-7 Scenarios of the ECT independent charging.......................................................................................8-9 Table 8-8 Scenarios of the ECT segmented charging ....................................................................................... 8-11 Table 8-9 Interaction between the ECT and other services...............................................................................8-12

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

8 Explicit Call Transfer Service

8
About This Chapter
Section 8.1 Service Description 8.2 Availability 8.3 Working Principle 8.4 Service Flow 8.5 Data Configuration 8.6 Service Management 8.7 Charging and CDR 8.8 Service Interaction 8.9 Reference

Explicit Call Transfer Service

The following table lists the contents of this chapter. Describes The function code, function definition of this feature, and the benefits that carriers and mobile subscribers can obtain from this feature. The network elements (NEs) that are required for the feature, whether Licenses are required, and the version requirements of the NEs. The functions of the NEs, and networking requirements. The service flow of the network when providing this feature. The data configurations that are required on the MSOFTX3000 and the UMG8900. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The charging and the generation of CDRs when the network provides this feature. The relationships and restrictions between this feature and other services or features. The protocols and specifications that this feature must comply with, and the acronyms and abbreviations of this chapter.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-1

8 Explicit Call Transfer Service

HUAWEI MSOFTX3000 Feature Description

8.1 Service Description
8.1.1 Function Code
Table 8-1 gives the function code of the explicit call transfer (ECT). Table 8-1 Function code of the ECT Name Explicit Call Transfer Code WMFD-020800

8.1.2 Definition
When the served mobile subscriber A has two on-going calls respectively with subscribers B and C, subscriber A can use the ECT function to connect B and C, and then A exits the call. The call between A and B (A-B call) or the call between A and C (A-C call) can be an incoming call or an outgoing call. Before the ECT is triggered, the A-B call and A-C call can be in the active state at the same time, or one of them is in the active state and the other is in the alerting state.

Intelligent subscribers do not support the ECT. The served mobile subscriber refers to the mobile subscriber who invokes the ECT.

8.1.3 Benefits
Table 8-2 gives the benefits of the ECT. Table 8-2 Benefits of the ECT Beneficiary Carrier Mobile subscriber Description Value added services are provided and call connection rate is increased. After the ECT function is provided, subscriber A can transfer a call to another subscriber during the conversation. In this case, subscriber A can flexibly determine the callee and the location of the callee.

8-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

8 Explicit Call Transfer Service

8.2 Availability
8.2.1 Requirements for NEs
Table 8-3 gives the required Network Elements (NEs) for the ECT. Table 8-3 Requirements for NEs UE/MS √ Node B/BTS RNC/BSC MSC Server √ MGW SGSN GGSN HLR √

The symbol "√" indicates that NE is required.

8.2.2 Requirements for License
The ECT is an optional attribute of Huawei wireless core network. The ECT service can be provided only when the License of the MSOFTX3000 is obtained.

8.2.3 Applicable Versions
Table 8-4 gives the applicable versions supported by Huawei core network product. Table 8-4 Applicable versions Product MSC server MSOFTX3000 Applicable Versions V100R003 and later versions

8.3 Working Principle
8.3.1 Functions of Each NE
The functions of the NEs are as follows: The MSC server and MGW work together to handle the ECT service. The HLR stores and manages the subscriber data and service data. The HLR updates the subscription data in the VLR by inserting the subscriber data.

8.3.2 Service Data Management
The HLR provides and withdraws the ECT service and operators modify the subscription data stored in the HLR. The HLR updates the subscription data in the VLR by inserting the subscriber data.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-3

8 Explicit Call Transfer Service

HUAWEI MSOFTX3000 Feature Description

8.3.3 Invoking the ECT
Both the A-B Call and A-C Call Are in the Active State
The A-B call is in the active state. A holds the call with B and calls C. Then the A-C call is established. The working principle is as follows: 1. 2. 3. 4. 5. 6. The MS A sends the FACILITY message to the MSC to prompt subscriber A to invoke the ECT. After receiving the FACILITY message, the MSC queries the subscription information of subscriber A. If the ECT is to be provided, the MSC then handles the ECT service. The MSC sets up the B-C call. The MSC sends a notification to subscriber B to inform B of call recovery and call transfer. (The B-C call is in the active state.) The MSC sends a notification to subscriber C to inform C of call transfer. (The B-C call is in the active state.) The MSC returns the response message and disconnection request to subscriber A. Then subscriber A exits the call.

The A-B Call Is in the Active State and the A-C Call Is in the Alerting State
The A-B call is in the active state. A holds the call with B and calls C. C is in the alerting state. The working principle is as follows: 1. 2. 3. 4. 5. 6. 7. The MS A sends the FACILITY message to the MSC to prompt subscriber A to invoke the ECT. The MSC receives the FACILITY message and queries the subscription information of subscriber A. If the ECT is to be provided, the MSC then handles the ECT service. The MSC sets up the B-C call. The MSC sends a notification to subscriber B to inform B of call recovery and call transfer. (The B-C call is in the alerting state.) The MSC sends a notification to subscriber C to inform C of call transfer. (The B-C call is in the alerting state.) The MSC returns the response message and disconnection request to subscriber A. Then subscriber A exits the call. After subscriber C answers the call, the MSC sends a notification to subscriber B to inform B that the call is in the active state.
If the mobile phone does not support the ECT service, invoke it through the unstructured supplementary service data (USSD).

8.4 Service Flow
8.4.1 A-B Call Is on Hold and A-C Call Is in the Active State
The carrier provides the ECT service for subscriber A. A holds the call with B and calls C. The A-C call is established. Subscribers A, B and C belong to the same MSC server. Figure 8-1 shows the ECT service flow.

8-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

8 Explicit Call Transfer Service

Figure 8-1 Invoking the ECT when A-B call is on hold and A-C call is in the active state
MS A MSC server MS B MS C

A-B CALL ON HOLD A-C CALL ACTIVE

A wants to invoke ECT FACILITY FACILITY FACILITY FACILITY FACILITY DISCONNECT DISCONNECT B-C CALL ACTIVE

The service flow is as follows: 1. 2. 3. 4. 5. The MS A sends a FACILITY message containing ExplicitCT to the MSC server. The MSC server sends the FACILITY message to MS B. The invoke element is NotifySS. The CallOnHold-indicator informs MS B of call recovery. The MSC server sends the FACILITY to MS B. The invoke element is NotifySS. The ECT-CallState is active. The Rdn indicates the number of subscriber C. The MSC server sends the FACILITY message to MS C. The invoke element is NotifySS. The ECT-CallState is active. The Rdn indicates the number of subscriber B. The MSC server sends the FACILITY message to MS A. If the message contains the result element, the ECT is successfully invoked. If the message contains the error or reject element, the ECT invoking is failed. The MSC server does not disconnect MS A. The MSC server sends the DISCONNECT message of A-B call and A-C call to MS A and completes call release. (The release flow is omitted in Figure 8-1.)

6.

8.4.2 A-B Call Is in the Active State and A-C Call Is in the Alerting State
The carrier provides the ECT service for subscriber A. A holds the call with B and calls C. C is in the alerting state. Subscribers A, B and C belong to the same MSC server. Figure 8-2 shows the ECT service flow.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-5

8 Explicit Call Transfer Service

HUAWEI MSOFTX3000 Feature Description

Figure 8-2 Invoking the ECT when C is in the alerting state
MSa MSC Server MSb MSc

CALL A-B on HOLD CALL A-C ALERTING

A wants to invoke ECT FACILITY FACILITY FACILITY FACILITY FACILITY DISCONNECT DISCONNECT CALL B-C ALERTING C waits to answer CONNECT FACILITY CALL B-C ACTIVE

The service flow is as follows: 1. 2. 3. 4. 5. If subscriber A wants to invoke the ECT, the MS A sends a FACILITY message containing ExplicitCT to the MSC server. The MSC server sends the FACILITY message to the MS B. The invoke element is NotifySS. The CallOnHold-indicator informs MS B of call recovery. The MSC server sends the FACILITY to MS B. The invoke element is NotifySS. The ECT-CallState is alerting. The MSC server sends the FACILITY message to MS C. The invoke element is NotifySS. The ECT-CallState is active. The Rdn indicates the number of subscriber B. The MSC server sends the FACILITY message to MS A. If the message contains the result element, it indicates that the ECT is successfully invoked. If the message contains the error or reject element, it indicates that the ECT invoking fails. The MS A cannot exit the call. The MSC server sends the DISCONNECT message of A-B call and A-C call to MS A and completes call release. (The later flow is omitted in Figure 8-2.) Subscriber C answers the call. The MS C sends the CONNECT message to the MSC server. The MSC server sends the FACILITY message to MS B. The invoke element is NotifySS. The ECT-CallState is active. The Rdn indicates the number of C.

6. 7. 8.

8-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

8 Explicit Call Transfer Service

8.5 Data Configuration
8.5.1 Data Configuration on the MSOFTX3000
For detailed data configuration operations, refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Invoking the ECT
If the MS invokes the ECT through the USSD, the data of the USSD must be configured. For details, refer to the service description of the USSD.

Generating the CDR of the ECT
Run MOD GBILLCTRL to generate the Call Detail Record (CDR) of the ECT.

Related Software Parameters
Table 8-5 gives the parameters of the related software. Table 8-5 Parameters of the related software Parameter Name Bit 9 of P18 (ISUP operation reserved parameter 1) Bit 10 of P18 (ISUP operation reserved parameter 1) Bit 5 of P134 (CHG parameter 6) Bit 6 of P134 (CHG parameter 6) Description It determines whether to send the FAC message to the peer office during the ECT. (The ISUP signaling is used between offices.) It determines whether to add the parameter allTransferNumber in the FAC message sent to the peer office. (The signaling between offices is the ISUP signaling.) It determines whether to segment the CDR. It determines the calling numbers filled in the CFW CDR of the forwarding subscriber and in the MTC CDR of the final subscriber after the call is forwarded during the ECT. Value 0: No 1: Yes Default Value 1

0: No 1: Yes

1

0: Yes 1: No 0: Number of the remote end 1: Number of the originating end

1

1

8.5.2 Data Configuration on the UMG8900
None.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-7

8 Explicit Call Transfer Service

HUAWEI MSOFTX3000 Feature Description

8.6 Service Management
8.6.1 Operation Mode
Table 8-6 gives two ECT operation modes. Table 8-6 ECT operation mode Operation Mode Operations by the carriers Interface HLR client Service Operation Service provisioning Service cancellation Operator Determined Barring (ODB) Operations by the mobile subscribers MS ECT invoking

Suggested change: For the ECT service, the service is provided when it is activated; and the service is cancelled when it is deactivated.

8.6.2 Operations by the Carriers
The carriers are allowed to: Provide the ECT service. Withdraw the ECT service. Perform ODB operations on the ECT service. For details, refer to the related operation manuals of the HLR.

8.6.3 Operations by the Mobile Subscribers
Prerequisite
The carriers have already provided the ECT service for the subscribers.

Operation Steps
To invoke the ECT, perform the following steps: Step 1 Dial 4 on the MS. Step 2 Press the send button. ----End

For certain MS, the ECT can be invoked through the menu. Refer to the instruction of the mobile phone for detailed operations. If the MS does not support this mode, invoke the ECT through the USSD.

8-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

8 Explicit Call Transfer Service

8.7 Charging and CDR
8.7.1 Introduction to the Charging Mode
There are two charging modes: Independent charging: The MSOFTX3000 generates the event CDR that contains the ECT flag and timestamp, and the original MOC/MTC CDR that contains the complete record of the A-B call and A-C call. The iGWB integrates the contents of the event CDR to the supplementary service field of the original MOC/MTC CDR to generate the final MOC/MTC CDR. Segmented charging: The MSOFTX3000 generates a group of MOC/MTC CDRs with the B-C call duration as the interval. The charging center integrates the CDRs. The ECT flag and timestamp are contained in the integrated CDR. The MSOFTX3000 controls the charging mode through parameter Bit 5 (P134) and the CDR control table.

To set the CHG parameter Bit 5 (P134), refer to the software parameter table. To set the CDR control table, refer to the corresponding online help.

8.7.2 Independent Charging
The MSOFTX3000 only generates the CDR of the A-B call and A-C call. The CDR of the call between the remote ends (B-C call) will not be generated by the MSOFT3000. Table 8-7 lists the scenarios of generating the CDR. Table 8-7 Scenarios of the ECT independent charging Scenario CDR of Subscriber A in the A-B Call The Call Hold (CH) and ECT operations are recorded in the supplementary service field. Start time: B answers the call. End time: The B-C call is disconnected. CDR of Subscriber B in the A-B Call There is no record in the supplementary service field. Start time: B answers the call. End time: The B-C call is disconnected. CDR of Subscriber A in the A-C Call The ECT operation is recorded in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected. CDR of Subscriber C in the A-C Call There is no record in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected.

During the A-B call, A holds the call with B and calls C. After C answers the call, A invokes the ECT. The B-C call is disestablished.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-9

CDR of Subscriber A in the A-C Call The ECT operation is recorded in the supplementary service field.3 Segmented Charging The MSOFTX3000 only generates the CDR of the A-B call and A-C call. End time: The B-C call is disconnected. 8-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The B-C call is disconnected.8 Explicit Call Transfer Service HUAWEI MSOFTX3000 Feature Description Scenario CDR of Subscriber A in the A-B Call The CH and ECT operations are recorded in the supplementary service field. End time: The B-C call is disconnected.7. There is no CDR. End time: The B-C call is disconnected. A invokes the ECT. A holds the call with B and calls C. 8. Start time: B answers the call. After C is in the alerting state. Start time: C answers the call. Start time: B answers the call. Start time: B answers the call. C does not answer the call. Table 8-8 lists the scenarios of generating the CDR. The CDR of the call between the remote ends (B-C call) will not be generated by the MSOFTX3000. CDR of Subscriber C in the A-C Call There is no record in the supplementary service field. During the A-B call. The CH operation is recorded in the supplementary service field. CDR of Subscriber B in the A-B Call There is no record in the supplementary service field. There is no CDR. Start time: C answers the call. There is no record in the supplementary service field. After C is in the alerting state. End time: The B-C call is disconnected. During the A-B call. Start time: B answers the call. End time: The B-C call is disconnected. A invokes the ECT. End time: The B-C call is disconnected. A holds the call with B and calls C.

End time: The B-C call is disconnected. Interval CDR: The ECT operation is recorded in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected. A holds the call with B and calls C. During the A-B call. A holds the call with B and calls C. Issue 02 (2007-06-10) Huawei Technologies Proprietary 8-11 . There is no record in the supplementary service field. After C is in the alerting state. Interval CDR: The ECT operation is recorded in the supplementary service field. CDR of Subscriber A in the A-C Call The first CDR: There is no record in the supplementary service field. End time: The B-C call is disconnected. End time: The B-C call is disconnected. During the A-B call. Start time: B answers the call. End time: The B-C call is disconnected. Start time: B answers the call. End time: A invokes the ECT. CDR of Subscriber B in the A-B Call There is no record in the supplementary service field. Start time: C answers the call. End time: A invokes the ECT. The B-C call is disconnected. Start time: A invokes the ECT.HUAWEI MSOFTX3000 Feature Description 8 Explicit Call Transfer Service Table 8-8 Scenarios of the ECT segmented charging Scenario CDR of Subscriber A in the A-B Call The first CDR: The CH operation is recorded in the supplementary service field. End time: The B-C call is disconnected. Start time: B answers the call. A invokes the ECT. A invokes the ECT. CDR of Subscriber A in the A-C Call There is no record in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected. The B-C call is The first CDR: The CH operation is recorded in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected. There is no record in the supplementary service field. After C answers the call. Start time: A invokes the ECT. The first CDR: There is no record in the supplementary service field. Start time: B answers the call.

8. The CH operation is recorded in the supplementary service field. the number of the peer end is displayed after the ECT is invoked. End time: The B-C call is disconnected.8 Service Interaction Table 8-9 gives the interaction between the ECT and other services. Start time: B answers the call. There is no CDR. There is no record in the supplementary service field. After C is in the alerting state.8 Explicit Call Transfer Service HUAWEI MSOFTX3000 Feature Description Scenario CDR of Subscriber A in the A-B Call Interval CDR: The ECT operation is recorded in the supplementary service field. the number of C (or B) must be sent to B (or C). the number need not be sent to B (or C). A holds the call with B and calls C. CDR of Subscriber A in the A-C Call disconnected. End time: The B-C call is disconnected. Start time: B answers the call. But if C (or B) also registers with the CLIP. End time: The B-C call is disconnected. During the A-B call. the number of C must be sent to B after A invokes the ECT. Start time: C answers the call. There is no CDR. Start time: C answers the call. If the A-C call is established after the ECT. 8-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 8-9 Interaction between the ECT and other services Service ECT and CLIP Interaction If A is the caller in the A-B call and B (or C) registers with the CLIP. CDR of Subscriber B in the A-B Call CDR of Subscriber A in the A-C Call Interval CDR: The ECT operation is recorded in the supplementary service field. A invokes the ECT. C does not answer the call. End time: The B-C call is disconnected. the number of C must be displayed during the connection. If the A-C call is established before the ECT. If B (or C) is the callee and (or C) registers with the CLIP (OVERRIDE CATEGORY CLIP) service.

B will receive the CW indication after the ECT. If the A-C call is established after the ECT. there will be no CW indication.0. If A is the caller in the A-C call and C registers with the COLR.9 Reference 8. 8.0. the call is forwarded to D when C does not answer the call. But if C (or B) also registers with the COLP. ECT and COLR If A is the caller in the A-B call and B registers with the COLR service. ECT and CFB ECT and CFNRy ECT and CFNRc ECT and CW ECT and MPTY ECT and AoC ECT and cheating prevention Both the MPTY originating party and remote party cannot invoke the ECT. If A has a CW before the ECT. If B (or C) is the caller and B (or C) registers with the COLP (OVERRIDE CATEGORY COLP) service.091 V4. If C registers with the CFB. the number of B must be hidden to C. the number of the peer end is displayed after the ECT is invoked.091 V4.9. If C registers with the CFNRy. process it as an ordinary terminated call. The number of B must not be sent to C.HUAWEI MSOFTX3000 Feature Description 8 Explicit Call Transfer Service Service ECT and CLIR ECT and COLP Interaction If B is the caller in the A-B call and registers with the CLIR. If A is in idle state after invoking the ECT. If C registers with the CW and the A-C call is in the waiting state. the number of C must be hidden to B. the number of C must be displayed during the connection. the number is not required to be sent to B (or C).1 Protocols and Specifications Refer to the following references: 3GPP TS 22. the number of C (or B) must be sent to B (or C). The cheating prevention feature prevents the subscribers from owing fee by continuously invoking the ECT. The ECT and AoC services conflict with each other. The ECT and CFNRc services do not affect each other. If the A-C call is established before the ECT. the number of C must be sent to B after A invokes the ECT. If B is the caller in the A-B call and B (or C) registers with the COLP.0 3GPP TS 23.0 Issue 02 (2007-06-10) Huawei Technologies Proprietary 8-13 . The CFNRy timer is not restarted during the call forwarding. the call is forwarded to D on C busy.

2 Acronyms and Abbreviations Acronym/Abbreviation 3GPP CFB CFNR CFNRc CFNRy CLIP CLIR COLP COLR ECT CW MOC MTC English Name 3rd Generation Partnership Project Call Forwarding on Mobile Subscriber Busy Call Forwarding No Reply Call Forwarding on mobile subscriber Not Reachable Call Forwarding on No Reply Calling Line Identification Presentation Calling Line Identification Restriction Connected Line Identification Presentation Connected Line Identification Restriction Explicit Call Transfer Call Waiting Mobile Originated Call Mobile Terminated Call 8-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) .1 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide 8.9.8 Explicit Call Transfer Service HUAWEI MSOFTX3000 Feature Description 3GPP TS 24.091 V4.0.

.......5 Barring of Packet Services.....................................1.....................................................................................9-5 9............................................4.........................................................1 Data Configuration for MSOFTX3000 ..................................2 Data Configuration for UMG8900....................................................................................1......................3 Service Type.....................9-8 9...................................................................................................................9 Reference .................................6 Service Management .....................................HUAWEI MSOFTX3000 Feature Description Contents Contents 9 ODB Service ...........................................................9-7 9...............9-6 9.....................................................4 Barring of Supplementary Services ................................................................................................................3 Applicable Versions........9-2 9.....1................................................4.......................2....7 Charging and CDR .......................................................................1 Protocols and Specifications ..............................................................9-8 9..1 Requirement for NEs .................................................................................9-7 9.............................................5......2 Definition .................................................4 Benefits ................................................................................4.....................................................................2 Availability ..................................5 Data Configuration........9-2 9.......9-6 9..................................................................................................................9-4 9............................................5.................................9-6 9..........................................................................................4...........................................9-4 9.........................................................................9-4 9.....................................................................9....9-6 9..........................8 Service Interaction ...................................................................................................9-1 9.................................9-3 9..1...........................................................9-8 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ...............4.........................................................................................................................................9-5 9.............................................3 Working Principle...........................9-7 9................................................................2..........................9-7 9.....................................9-5 9....2 Acronyms and Abbreviations ..................................................................................................................................2 Barring of Outgoing Calls or MS MO ......................................9-5 9.......................................................1 Service Description .......................................................................................9-4 9................................................................3 Barring of Roaming ................................................4 Service Flow...............................................................................................1 Function Code.............................1 Barring of Incoming Calls or MS MT.................................................................................9-5 9..........................................................................2 Requirement for License...........................................2...9-6 9.....9...............................................................................9-2 9.................

..........................................................................9-4 Table 9-3 Versions that support the ODB services ...9-5 Table 9-4 Service interaction between ODB and other services.............................9-2 Table 9-2 NEs related with the ODB services ...............................................................................................9-7 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .....................................................................................................................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 9-1 Name and function code of the ODB services.................................

The service flow of the network when providing this feature. The charging and the generation of CDRs when the network provides this feature.4 Service Flow 9. The relationships and restrictions between this feature and other services or features. and networking requirements.6 Service Management 9.9 Reference Describes ODB Service The function code. The network elements (NEs) that are required for the feature.HUAWEI MSOFTX3000 Feature Description 9 ODB Service 9 About This Chapter The following table lists the contents of this chapter. function definition of this feature. Section 9.1 Service Description 9. and the benefits that carriers and mobile subscribers can obtain from this feature. The protocols and specifications that this feature must comply with. Issue 02 (2007-06-10) Huawei Technologies Proprietary 9-1 . and the version requirements of the NEs.7 Charging and CDR 9. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.8 Service Interaction 9.5 Data Configuration 9.2 Availability 9. The functions of the NEs. The data configurations that are required on the MSOFTX3000 and the UMG8900. and the acronyms and abbreviations of this chapter.3 Working Principle 9. whether Licenses are required.

1. The ODB service is activated once it is provided to the user. The ODB is similar to the call restriction supplementary service. and the latter type must be activated by the user. and that of the latter type can be determined by both the operator and the user. Table 9-1 Name and function code of the ODB services Name Operator Determined Barring (ODB) services ODB: Barring of all outgoing calls (BAOC) ODB: Barring of all outgoing international calls (BOIC) ODB: Barring of outgoing international calls except those directed to the home PLMN Country (BOIC-exHC) ODB barring of all incoming calls (BAIC) ODB: Barring of outgoing calls when roaming outside home PLMN country (BOC-ROAM) ODB: Barring of incoming calls when roaming outside home PLMN country (BIC-ROAM) ODB: Barring of outgoing Premium Rate Calls (Information) ODB: Barring of outgoing Premium Rate Calls (Entertainment) ODB barring of supplementary service management ODB: Barring of Roaming outside the home PLMN ODB: Barring of domestic toll calls (HPLMN self-define type1) Self-defined ODB restriction function Code WMFD-030000 WMFD-030100 WMFD-030200 WMFD-030300 WMFD-030400 WMFD-030500 WMFD-030600 WMFD-030700 WMFD-030800 WMFD-030900 WMFD-031000 WMFD-031100 WMFD-031200 9.1 Service Description 9.1 Function Code Table 9-1 lists the name and function code of the ODB services.2 Definition The Operator Determined Barring (ODB) is kind of service through which the PLMN operator determines the access capability of the users to the UMTS or GSM network. The differences between these two services are as follows: The service state of the user subscribing to ODB is determined by the operator.1. 9-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) .9 ODB Service HUAWEI MSOFTX3000 Feature Description 9.

3 Service Type The ODB service has the following types: Barring of incoming calls or mobile-terminated short message (SM MT) Barring of outgoing calls or mobile-originated short message (SM MO) Barring of roaming Barring of supplementary service Barring of packet service Barring of Incoming Calls or SM MT (ODB-BIC) The operator of a PLMN can restrict a user to receive calls of a certain type or SM MT. This service includes: Barring of all incoming calls BIC-ROAM Barring of SM MT Barring of Outgoing Calls or SM MO (ODB-BOC) The operator of a PLMN can restrict a user to originate calls of a certain type or SM MO.1.HUAWEI MSOFTX3000 Feature Description 9 ODB Service 9. In this case. the users can not perform the following supplementary service management operations: − Registration Issue 02 (2007-06-10) Huawei Technologies Proprietary 9-3 . This service includes: Barring of roaming outside HPLMN Barring of roaming outside HPLMN country Barring of Supplementary Services (ODB-SS) Barring of supplementary services includes: Barring of supplementary service management Barring of supplementary service management enables the operator of the PLMN to restrict the user-controlled supplementary services. This service includes: Barring of all outgoing calls Barring of SM MO Barring of outgoing international calls BOIC-exHC BOC-ROAM when roaming outside HPLMN country Barring of outgoing premium rate calls (information) Barring of outgoing premium rate calls (entertainment) Barring of Roaming (ODB-ROAM) The operator of a PLMN can restrict a user to roam within a certain area.

1 Requirement for NEs The ODB requires the corporation of the MSC server.4 Benefits Beneficiary Carrier Mobile subscriber Description The ODB service helps the operator manage the users regarding all kinds of services based on actual situation. and GGSN.2. VLR. 9-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 9-2 NEs related with the ODB services UE/ MS – NodeB /BTS – RNC/ BSC – MSC Server √ MGW – SGSN √ GGSN √ VLR √ HLR √ "√" stands for the related NEs. HLR.2.9 ODB Service − − − − − HUAWEI MSOFTX3000 Feature Description Deregistration Activation Deactivation Querying Invocation Barring of user registration of call forwarding services Barring of call transfer service Barring of Packet Over SONET/SDH (ODB-POS) Barring of POS service includes: Barring of PDP context activation launched by MS Barring of PDP context activation launched by network 9. You can obtain this service only after getting the license of MSOFTX3000. SGSN. Table 9-2 lists the NEs related with the ODB services. 9. None. 9.1.2 Requirement for License The ODB is an optional feature of the Huawei wireless core network.2 Availability 9.

The MSC processes signaling. the HLR sends a refusing message that contains error message to the MSC (or GMSC).1 Barring of Incoming Calls or MS MT Procedure of Barring of Incoming Calls The HLR checks whether the user subscribes to the ODB barring of incoming calls after receiving a routing request from an MS. The HLR stores the subscription data. The MSC (or GMSC) then sends the error message to the network of the calling party.3 Applicable Versions Table 9-3 lists the Huawei core network product versions that support the ODB services. 9. the HLR sends a refusing message that contains error message to the MSC (or GMSC). The MSC (or GMSC) then sends the error message to the related short message center.HUAWEI MSOFTX3000 Feature Description 9 ODB Service 9.2.2 Barring of Outgoing Calls or MS MO The MSC checks the user information in the VLR after receiving a service request launched by the user subscribing to barring of outgoing calls. determines whether to trigger the ODB.3 Working Principle The ODB requires the corporation of the HLR. If the outgoing call barring of the user is Issue 02 (2007-06-10) Huawei Technologies Proprietary 9-5 .4. analyzes data.4 Service Flow 9. 9. Procedure of Barring of SM MT The HLR checks whether the user subscribes to the ODB barring of SM MT after receiving a routing request from an MS.4. and the calling party hears the prompt tone defined by the operator. MSC. and sends subscription data of the user to the VLR. Table 9-3 Versions that support the ODB services Product MSC server MGW MSOFTX3000 UMG8900 Applicable Versions V100R002 an the later versions V200R002 and the later versions 9. and the SGSN. The SGSN processes all the signaling related with packet services. If the user subscribes to this service. and plays announcements. The VLR stores temporally the subscription data of the user which is to be queried by the MSC. If the user subscribes to this service. VLR.

9. Then the HLR responses a location canceling message and refuses the location update. the SGSN returns a refusing message which contains error message. 9.4.5 Data Configuration 9. the VLR sends a location update request to the HLR. 9. 9-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) .5.9 ODB Service HUAWEI MSOFTX3000 Feature Description activated.5 Barring of Packet Services The procedure of the PDP context activation launched by a barred MS is as follows: If the SGSN receives a PDP context activation request. the HLR checks the subscription data of the MS. and if the MS subscribes to the ODB barring of packet services. the MSC refuses the call request of the user and returns a refusing message which contains the cause value. 9. The MSC needs to analyze the number of the called party to determine whether the following types of calls are barred: International calls Outgoing international calls except the home PLMN country Premium rate calls If a user subscribes to BOC-ROAM and roams to non-HPLMN countries. the HLR responses a refusing message which contains error message. the HLR or MSC/VLR refuses the request and sends an error message to the mobile subscriber.4 Barring of Supplementary Services If a mobile subscriber subscribes to barring of supplementary services. If the MS subscription data contains the data for ODB barring of packet services. Then the GGSN sends the error message to the network that launches the PDP context activation. the MSC/HLR bars all the calls originated by this user and returns a refusing message which contains the cause value. The HLR checks the identifier of the VLR and determines that the VLR is in the roaming restriction area. and if the subscriber launches registration to the VLR in the roaming restriction area defined by this barring of roaming service. and if the routing request contains the PDP context activation information. You can perform service check through certain call prefix.1 Data Configuration for MSOFTX3000 The MSOFTX3000 can control the ODB service through call prefix table and service check table: You can add call prefix by using the command ADD CNACLD.4. and if the user launches a supplementary service operation.3 Barring of Roaming If a mobile subscriber subscribes to the ODB barring of roaming. The procedure of the PDP context activation launched by a barred network is as follows: If the HLR receives a routing request message to a certain MS.4.

If the ODB barring of call forwarding is activated. 9.2 Data Configuration for UMG8900 None. The HLR (incoming calls) or the VLR (outgoing calls) checks the ODB service state and then the CUG service state when it receives a call request. You can perform service check through certain call prefix and determines whether to connect the call based on the check result. 9. ODB and call barring Issue 02 (2007-06-10) Huawei Technologies Proprietary 9-7 .5. The HLR (incoming calls) or the VLR (outgoing calls) checks the ODB service state and then the call barring service state when it receives a call request. If the ODB conflicts with supplementary services. the supplementary services will be barred.8 Service Interaction Table 9-4 lists the service interaction between ODB and other services. For details. Table 9-4 Service interaction between ODB and other services Service Terminal service and bearer service Supplementary services ODB and call forwarding ODB and CUG Interaction ODB can be applied to all terminal services and bearer services except emergency call. 9.HUAWEI MSOFTX3000 Feature Description 9 ODB Service You can add service check by using the command ADD SRVCHK. see the related product manuals of the latest version. ODB has higher priority over supplementary services. 9. the user is not allowed to register call forwarding services.7 Charging and CDR None.6 Service Management All the management operations of the ODB services are performed in the HLR.

1 HUAWEI MSOFTX3000 Mobile Softswitch Center Configuration Guide 9.2 Acronyms and Abbreviations Acronym/Abbreviation 3GPP HPLMN GGSN PDP ODB SGSN English Full Name 3rd Generation Partnership Project Home PLMN Gateway GPRS Support Node Packet Data Protocol Operator Determined Barring Serving GPRS Support Node 9-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) .0 3GPP TS 23.0.9.1 Protocols and Specifications This document takes the following protocols and manual as references: 3GPP TS 22.9 Reference 9.9.0.091 V4.9 ODB Service HUAWEI MSOFTX3000 Feature Description 9.091 V4.091 V4.0 3GPP TS 24.0.

............4........10-3 10.2...........................4................................10-7 10..............................10-3 10.....................................................................................................................................................1........10-3 10.................................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 10 Authentication Feature.....................................................................................................................................................................................................7......................2 Requirements for License ..........................................................10-7 10...3 Applicable Versions....................................................................10-3 10......1 Requirements for NEs................................................................................ Acronyms and Abbreviations ........................................................................10-2 10..................................................................................................4 Service Flow...................................2....................................................................10-3 10.............1..............................................................................................................2 Glossary...................................................................................................10-2 10...................6.........................................10-7 10.............................................................10-8 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .........10-7 10..................................................................................................................................10-7 10..................................................................................10-7 10................................................................................................10-7 10....1 Protocols and Specifications ....2 Data Configuration on HLR...............................................................7 Reference ................................................................1 Data Configuration on MSOFTX3000..................................1 UMTS Authentication ....................................................................5...............................3 Benefits ....................2 Query of Authentication..........................2 Definition .................................................10-4 10................................................................................................1 Subscription of Authentication................5.............10-4 10.......7..10-1 10.....................................................................5 Data Configuration................2.........3 Working Principle............1.........................10-7 10....................................................6 Service Management .............................................................................................................2 GSM Authentication ........................................................................................................1 Function Code....................10-2 10.1 Service Description .......10-2 10...............6.........................2 Availability .........................................10-5 10..

...................................................................................................10-4 Figure 10-2 Flow of GSM authentication............................................................10-6 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .......................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 10-1 Flow of UMTS authentication ..........

..........................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 10-1 Function names and functions codes in the authentication and encryption .............................................10-2 Table 10-3 NEs involved in the authentication and encryption ..............................................................................10-2 Table 10-2 Benefits for carriers and mobile subscribers.............................10-3 Table 10-4 Versions of the products that support the authentication and encryption..............................10-3 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ........................

The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. function definition of this feature. and the acronyms and abbreviations of this chapter. The data configurations that are required on the MSOFTX3000 and the UMG8900.6 Service Management 10.HUAWEI MSOFTX3000 Feature Description 10 Authentication Feature 10 About This Chapter Section 10. and the benefits that carriers and mobile subscribers can obtain from this feature.5 Data Configuration 10. The function code.7 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 10-1 . whether Licenses are required.1 Service Description 10.2 Availability Describes Authentication Feature The following table lists the contents of this chapter.3 Working Principle 10.4 Service Flow 10. and networking requirements. The network elements (NEs) that are required for the feature. The service flow of the network when providing this feature. The functions of the NEs. and the version requirements of the NEs. 10. The protocols and specifications that this feature must comply with.

Authentication protects mobile subscribers from illegal attack. Table 10-2 Benefits for carriers and mobile subscribers Beneficiary Carriers Description Authentication is an elementary feature of a network. Table 10-1 Function names and functions codes in the authentication and encryption Name GSM Authentication and Encryption UMTS Authentication and Encryption Note: GSM = Global System for Mobile communications.1. an UE can also verify the validity of a network. 10. so that illegal subscribers cannot use the services that the network provides. Authentication enables carriers to verify the validity of MSs/UEs. guarantees the confidentiality and integrity of the wireless network.3 Benefits Table 10-2 lists the benefits for carriers and mobile subscribers. In the UMTS.1.2 Definition Authentication is a process used for a network to verify the validity of an UE. Mobile subscribers Note: MS = mobile station. Authentication.1. UMTS = Universal Mobile Telecommunications System Code WMFD-060301 WMFD-060302 10. as part of the security management of a wireless network.10 Authentication Feature HUAWEI MSOFTX3000 Feature Description 10. and prevents illegal subscribers from accessing the network and using the services that the network provides.1 Function Code Table 10-1 lists the mapping between function names and function codes in the speech service. UE = user equipment 10-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) .1 Service Description 10.

For details. 10.HUAWEI MSOFTX3000 Feature Description 10 Authentication Feature 10. because the service is the elementary feature of the HUAWEI wireless core network.2. see Table 10-3.1 Requirements for NEs The authentication and encryption requires the cooperation of the UE/MS. Table 10-3 NEs involved in the authentication and encryption UE/ MS √ NodeB /BTS √ RNC/ BSC √ MSC Server √ MGW √ SGSN √ GGSN VLR √ HLR √ "√" means the NE is required.2 Availability 10. base station subsystem (BSS) . Issue 02 (2007-06-10) Huawei Technologies Proprietary 10-3 .3 Applicable Versions Table 10-4 lists the versions of the HUAWEI circuited switched (CS) products that support the authentication and encryption. the MS/UE. 10. to verify the validity of the MS/UE.2 Requirements for License No License is required to obtain the authentication service.2. The MS/UE and AuC calculate authentication parameters respectively. the MS/UE can also verify the validity of the network.3 Working Principle In the GSM and UMTS. Table 10-4 Versions of the products that support the authentication and encryption Product MSC Server MGW MSOFTX3000 UMG8900 Applicable version V100R002 and later V200R002 and later 10.2. radio access network (RAN) and core network (CN). In the UMTS. visitor location register (VLR) and authentication center (AuC) cooperate with each other to implement authentication. The VLR then compares the two results.

The MSC then directly transfers the two parameters to the UE over the RAN. The MSC sends a MAP_PROCESS_ACCESS_REQUEST to the VLR.4. 4.10 Authentication Feature HUAWEI MSOFTX3000 Feature Description 10. − If there are available authentication sets in the VLR. IMSI/TMSI) 5. the VLR returns the RAND and AUTN contained in the authentication set to the MSC before starting authentication. The UE sends an authentication request to the mobile switching center (MSC). The authentication of services is defined by the data configured on the MSC. 2.1 UMTS Authentication UMTS authentication takes place when a UMTS subscriber accesses the UMTS with a UMTS subscriber identity module (USIM) card. Send an authentication response AuC re-synchronization 7. AUTN) 3. 5. Refuse authentication (XMAC ≠ MAC) 6. − 3. Accept the request/ Refuse the request Sends an acceptance response Authentication succeeds legal UE Authentication fails illegal UE 8. Send a service request (call setup/location update/ supplementary serice/SMS) 2. Send a MAP request (CKSN. Start authentication 5 5 (RAND. If no available authentication set is in the VLR. 10-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Compare SRES and XRES Explanations of the flow of UMTS authentication are as follows: 1. Send a request for authntication parameters ( IMSI) 4. Synchronization fails (SQNHE ≠SQNMS) 7. That is. Figure 10-1 Flow of UMTS authentication Uu UE RAN 1. without interacting with the AuC. step 3 takes place. Return parameters (IMSI,RAND,CK, IK,AUTN,XRES) RANAP Iu MSC MAP B VLR MAP D HLR/AuC 6. step 5 takes place immediately after step 2. Figure 10-1 shows the flow of UMTS authentication. The VLR starts authentication. The VLR requests the authentication set from the AuC. The AuC returns one to five groups of quintuples to the VLR based on actual conditions. requesting the authentication set from the VLR.4 Service Flow 10.

and returns AUTN and RAND to the UE. − If the two values are different. to judge whether the re-synchronization is valid. The AuC adjusts its own SQNHE based on the SQNMS in AUTS. SIM stands for subscriber identity module. Issue 02 (2007-06-10) Huawei Technologies Proprietary 10-5 . After receiving the re-synchronization message. and compares the MAC with the MAC-S in AUTS. If the two values are the same. After that. and sends an authentication response carrying XRES to the VLR. In GSM authentication. The UE receives the response. the authentication of the network to the UE succeeds. If the validity verification succeeds. − 10. The VLR starts authentication again with the new group of authentication values. the authentication of the UE to the network fails. − 7. If the difference between SQNMS and SQNHE is not within the specific range. the MS does not have to authenticate the network. the AuC calculates MAC based on the RAND in the message.2 GSM Authentication GSM authentication takes place under one of the following conditions: A GSM subscriber accesses the GSM with a SIM card. and calculates a new group of authentication values for the VLR. A UMTS subscriber accesses the GSM. − − If MAC is not equal to XMAC. it means the authentication of the UE to the network fails. the VLR sends an authentication rejection response to the UE. Figure 10-2 shows the flow of GSM authentication. based on the RAND and AUTN returned by the VLR.HUAWEI MSOFTX3000 Feature Description 10 Authentication Feature 6. A GSM subscriber accesses the UMTS. then the authentication succeeds. The VLR compares the XRES returned by the UE with the XRES calculated by the AuC. The UE calculates the authentication parameters XMAC and SQNMS at the UE side. the VLR sends a re-synchronization message to the AuC. In this case. The re-synchronization flow is similar to the flow of obtaining authentication set from the AuC.4. In this case. 8. This means the UE is invalid and the authentication fails. The UE calculates XRES based on the AUTN and RAND returned from the VLR. In this case. indicating that the service or location update is accepted. steps 3 and 4 are repeated. The difference is that the MAP_SEND_AUTHENTICATION_INFO message carries the re-synchronization information containing AUTS and RAND. the network sends a response to the UE. The UE then compares the XMAC and SQNMS with the MAC and SQNHE in AUTN. the VLR reports the authentication failure message to the AuC.

10 Authentication Feature HUAWEI MSOFTX3000 Feature Description Figure 10-2 Flow of GSM authentication Um MS BSS 1. This means the MS is invalid and the authentication fails. KC. That is. − If there are available authentication sets in the VLR. The MSC sends a MAP_PROCESS_ACCESS_REQUEST to the VLR. requesting the authentication set from the VLR. Send a MAP request MAP B VLR MAP D HLR/AuC 5. The VLR compares the SRES returned by the MS with the SRES calculated by the AuC. The authentication of services is defined by the data configured on the MSC. the VLR returns the RAND and AUTN contained in the authentication set to the MSC before starting authentication. The MS receives the response. RAND) 6. 4. the VLR sends an authentication rejection response to the MS. Send a request for authntication parameters (IMSI) 4. Accept the request/ Refuse the request Authentication succeeds legal UE Authentication fails illegal UE 8. IMSI/TMSI) 3. Send a service request (call setup/location update/ supplementary serice/SMS) (CKSN. step 3 takes place. 6. The MS calculates SRES based on the RAND returned from the VLR. the authentication of the network to the MS succeeds. and sends an authentication response carrying SRES to the VLR. If the two values are the same. S. Start authentication 5 5 (CKSN. Return parameters (IMSI. Send an authentication response 6 Sends an acceptance response 7. If no available authentication set is in the VLR. The VLR starts authentication. indicating that the service or location update is accepted. step 5 takes place immediately after step 2. the network sends a response to the MS. RAND) BSSAP A MSC 2. The MSC then directly transfers the two parameters to the MS. The AuC returns one to five groups of triplets to the VLR based on actual conditions. 2. The MS sends an authentication request to the MSC. Compare SRES and XRES Explanations of the flow of GSM authentication are as follows: 1. − If the two values are different. − 10-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . − 3. without interacting with the AuC. The VLR requests the authentication set from the AuC. 5. 7. In this case.

5.002: <3rd Generation Partnership Project. 10. (Optional) Step 2 Run ADD CHKIMEICTRL to add IMEI check control.102: <3rd Generation Partnership Project. Mobile Application Part (MAP) specification. For details. For details.6. 10. see the manuals relevant to the HLR.HUAWEI MSOFTX3000 Feature Description 10 Authentication Feature When a UMTS subscriber roams in the GSM.7 Reference 10.2 Query of Authentication The query of authentication is on the HLR.3G Security. the AuC may return a quintuple to the VLR. 10.6 Service Management 10.5.1 Data Configuration on MSOFTX3000 To configure the data for the authentication feature.> Issue 02 (2007-06-10) Huawei Technologies Proprietary 10-7 . see the manuals relevant to the HLR. (Optional) Step 3 Run SET CHKIMEICFG to set IMEI check configuration.5 Data Configuration 10. In this case. After that. (Optional) Step 4 Run ADD VEIRUSER to add a virtual EIR subscriber.6. the VLR must transform the quintuple to a triplet.2 Data Configuration on HLR For the details on configuration steps and parameter description. perform the following steps: Step 1 Run MOD AUTHCFG to modify authentication configuration. see the manuals relevant to the HLR.1 Protocols and Specifications 3GPP TS 33.1 Subscription of Authentication The subscription of authentication is on the HLR. the VLR returns the ciphering key sequence number (CKSN) together with the RAND in the triple to the MS. (Optional) ----End 10. Security Architecture> 3GPP TS 29. 10. Technical Specification Group Services and System Aspects. Technical Specification Group Core Network.7.

CK.2 Glossary. IK and AUTN. It is a temporary data used for the MSC/VLR or SGSN to negotiate GSM authentication and key agreement (AKA) with a specific subscriber. A quintuple is a UMTS authentication vector composed of five elements: RAND. SRES and Kc.7. Quintuple Acronyms and Abbreviations Acronym/Abbreviation AuC CKSN GSM MAC MS MSC RAND UMTS UE VLR Full Name Authentication Center Ciphering Key Sequence Number Global System for Mobile Communications Message Authentication Code Mobile Station Mobile Switching Center RANDom number Universal Mobile Telecommunication Services User Equipment Visitor Location Register 10-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Acronyms and Abbreviations Glossary Glossary Triplet Definition A triplet is a GSM authentication vector composed of three elements: RAND. It is a temporary data used for the MSC/VLR or SGSN to negotiate UMTS AKA with a specific subscriber. XRES.10 Authentication Feature HUAWEI MSOFTX3000 Feature Description 10.

............................................................................................................................................................ 11-5 11..........2.............................2 Configuraing Data at the UMG8900 Side..............3..............1 Protocols and Specifications .....................................................................................3 Applicable Versions..........11-1 11.......................................... 11-4 11...HUAWEI MSOFTX3000 Feature Description Contents Contents 11 Enhanced MSRN Allocation Feature ............................................. 11-4 11..................................2........................................................................................................................................................................... 11-15 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ......3 Configuration Examples................................7 Charging and CDR .......................................................................................1 Configuring Data at the MSOFTX3000 Side.......9......2 Requirements for License .........................5 Data Configuration ........................... 11-4 11............................. 11-10 11...................................................................................................................................... 11-9 11...........4.... 11-8 11........................................ 11-5 11..............................2 Availability ..............................................................................................9.........................................................4... 11-5 11....................1 Service Description ....5........3 Benefits ................................ 11-14 11....................................................................... 11-4 11...................1 Functions of NEs......... 11-2 11..........2 Definition ....................................6 Service Management ......................................4 Service Flow.................................................................. 11-9 11.......................1............................................ 11-14 11.........................................................................2.................................1 General Procedure of MSRN Allocation..................................................5....... 11-4 11.......................................... 11-2 11....................................................... 11-7 11............................................2 Acronyms and Abbreviations ...................................................................2 Procedure for Random Allocation..................................................................................................................1 Requirements for NEs ...............................................................................................................................................................1 Function Code .......8 Service Interaction.......................................................................................................................................................... 11-14 11.............................. 11-2 11............................. 11-7 11.................................................................................................................................................................................................................... 11-10 11.................. 11-15 11................1........................................... 11-15 11........................9 Reference............2 Processing in the System....5........................................................................................................................1...............................................................3......................................3 Working Principle....................

............ 11-8 Figure 11-4 Mapping between the MSRN or HON allocation tables...............Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 11-1 Simple MSRN allocation procedure ............................................................................................................................................................. 11-9 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ........................................................................................ 11-7 Figure 11-3 Procedure for random allocation............................. 11-6 Figure 11-2 General procedure of MSRN allocation...........................................

....................... 11-5 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ....HUAWEI MSOFTX3000 Feature Description Tables Tables Table 11-1 Name and code of the function ................................ 11-2 Table 11-2 Beneficiaries and description of the benefits ............................ 11-4 Table 11-4 Applicable versions of HUAWEI wireless core network products .............................................................................................................................................................................. 11-4 Table 11-3 NEs required by the enhanced MSRN allocation service .....................................

4 Service Flow 11.5 Data Configuration 11. The relationships and restrictions between this feature and other services or features.8 Service Interaction 11.9 Reference Describes The function code.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature 11 Enhanced MSRN Allocation Feature About This Chapter The following table lists the contents of this chapter. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. and networking requirements. function definition of this feature.6 Service Management 11. The acronyms and abbreviations in this chapter. The functions of the NEs. The service flow of the network when providing this feature. whether Licenses are required.2 Availability 11.1 Service Description 11. The network elements (NEs) that are required for the feature. and the benefits that carriers and mobile subscribers can obtain from this feature. Section 11. The charging and the generation of CDRs when the network provides this feature. The data configurations that are required on the MSOFTX3000 and the UMG8900.7 Charging and CDR 11.3 Working Principle 11. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-1 . and the version requirements of the NEs.

you are recommended to set MSRN allocation mode to Allocate according to LAI number. Table 11-1 Name and code of the function Name Enhanced MSRN allocation Code WMFD-042400 11. There are several modes for allocating MSRNs. Allocation Based on the MSC Number The VLR ranges the MSRN resources that the local VLR can use based on the MSC number in advance.2 Definition Overview The mobile station roaming number (MSRN) is used by the mobile switching center (MSC) to address callees. the system instructs the visitor location register (VLR) to allocate a temporary MSRN to the MS based on the request of the home location register (HLR).1.1 Function Code Table 11-1 lists the name and code of the function. There are three MSRN allocation modes: Allocation based on the MSC number Allocation based on the LAI number Random allocation The mode of random allocation enables you to allocate roaming numbers based on the attribute of the call or the callee. That is.1 Service Description 11. the VLR allocates MSRN resources for different MSC numbers. When the mobile station (MS) receives a call. Generally. An MSRN has a validity period. the mode of random allocation can meet the requirements of networking except for certain special cases: In the multi-area network. The default value is Allocate randomly. you are recommended to set MSRN allocation mode to Allocate according to MSC number.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description 11. The VLR can allocate specific roaming number resources through different allocation modes to meet various requirements. 11-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . You can set the validity period in the VLR configuration table. and the default value is 90 seconds. The parameter MSRN allocation mode specifies the mode adopted by the VLR to allocate roaming numbers for the mobile subscribers roaming to the local office. When the location area identification (LAI) number is used for charging.1.

HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature When the home HLR of a mobile subscriber requests the local MSC or VLR to allocate an MSRN for the mobile subscriber. Inter-province roaming numbers are classified into four types based on the attribute of the callee. The mapping between the MSRN and the MSC number is configured by using the command ADD MHMSCCFG. the VLR allocates MSRN resources for different LAI numbers. the VLR adds an extended function to the enhanced MSRN allocation service. The mapping between the MSRN and the LAI number is configured by using the command ADD MHLAICFG. the VLR allocates an intra-province roaming number so that the incoming call can be connected to the office. the local MSC or VLR allocates an idle MSRN randomly from the MSRN pool to which the LAI number of the callee corresponds. If the related inter-province roaming numbers are used up. Random Allocation The VLR does not range the MSRN resources that the local VLR can use in advance. Allocation Based on the LAI Number The VLR ranges the MSRN resources that the local VLR can use based on the LAI number in advance. Inter-province roaming numbers Inter-province roaming numbers are configured by using the command ADD IMHSUFFIX. The numbers of which MSRN/HON number type is set to any of the following values are inter-province roaming numbers: − − − − MSRN outer province Is_O_CSI roaming type MSRN outer province No_O_CSI roaming type MSRN outer province Is_O_CSI local type MSRN outer province No O_CSI local type When a roaming number is requested for an inter-province incoming call. the local MSC or VLR allocates an idle MSRN randomly from the MSRN pool to which the MSC number of the callee corresponds. the VLR allocates a roaming number from the corresponding roaming number resource pool based on the attribute of the callee. The VLR divides roaming numbers into two types based on the attributes of the numbers: Intra-province roaming number The numbers of which MSRN/HON number type is set to MSRN and HON or MSRN are intra-province roaming numbers. the local MSC or VLR allocates an idle MSRN randomly from all the MSRN pools that the local MSC or VLR can use. When the home HLR of a mobile subscriber requests the local MSC or VLR to allocate an MSRN for the mobile subscriber. That is. For the mode of random allocation. When the home HLR of a mobile subscriber requests the local MSC or VLR to allocate an MSRN for the mobile subscriber. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-3 .

and the customer satisfaction rate is improved. The hyphen . RNC = radio network controller. the subscriber types are analyzed more effectively. 11-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .2 Requirements for License The enhanced MSRN allocation service is the basic service of HUAWEI wireless core network.3 Benefits Table 11-2 lists the beneficiaries and description of the benefits. MS = mobile station.2.1. BTS = base transceiver station. In this way.3 Applicable Versions Table 11-4 lists the applicable versions of HUAWEI wireless core network products that the enhanced MSRN allocation service supports.indicates that the corresponding NE is not required. SGSN = serving GPRS support node The symbol √ indicates that the corresponding NE is required. None.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description 11.2. Table 11-2 Beneficiaries and description of the benefits Beneficiary Carriers Description Carriers can choose the allocation mode based on their requirements. 11. Mobile subscribers 11. 11.1 Requirements for NEs Table 11-3 lists the network elements (NEs) required by the enhanced MSRN allocation service.2 Availability 11. MGW = media gateway. Table 11-3 NEs required by the enhanced MSRN allocation service UE/MS Node B/BTS RNC /BSC MSC server √ MGW SGSN VLR √ HLR √ Note: UE = user equipment. No license is required. BSC = base station controller.2.

3 Working Principle 11. VLR. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-5 .3.1 Functions of NEs The MSC server determines the MSRN allocation mode through data configuration. Figure 11-1 shows the simple MSRN allocation procedure.2 Processing in the System Messages are exchanged between the MSC server.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature Table 11-4 Applicable versions of HUAWEI wireless core network products Product MSC server MSOFTX3000 Applicable Version V100R002 and later versions 11. The VLR and HLR exchange and transfer the requests for MSRN allocation. The VLR realizes MSRN allocation based on the configuration of the system. The MSC server performs the following functions: Exchanges information with the VLR and HLR through the C/D interface Checks the status of subscribers Conveys flag bits to the VLR The VLR allocates an MSRN based on the configuration in the MSC server. 11. and records the information required after the call is connected.3. and HLR through the Mobile Application Part (MAP) protocol.

the VLR allocates an MSRN related to the MSC number of the callee. 5.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description Figure 11-1 Simple MSRN allocation procedure Caller (1) (2) (G)MSC server (5) HLR (4) (10) (6) (3) (7) (9) VLR (8) VMSC server Callee 1. 2. If the extended MSRN allocation function is enabled for the mode of random allocation. The VLR checks the status of the subscriber. and returns the MSRN to the HLR. The HLR returns the MSRN to the (G)MSC server at the caller side. The HLR obtains an MSRN from the VLR because the HLR records the address of the VLR in the office to which the callee roams. the VLR allocates an MSRN from all MSRN pools. 11-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The (G)MSC server requests routing information from the HLR of the callee. the VLR allocates a corresponding MSRN from the MSRN pool based on the attributes of the call and the callee. 3. the VLR allocates an MSRN related to the LAI number of the callee. − − − − 4. allocates an MSRN based on the current allocation mode. The HLR checks compatibility and the feasibility of subscription. The (G)MSC server receives a call request from the caller. If MSRN allocation mode is set to Allocate according to LAI number. If MSRN allocation mode is set to Allocate randomly. If MSRN allocation mode is set to Allocate according to MSC number.

HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature 6. 7. checks subscriber status. The VMSC sever queries the VLR for the subscription information of the callee. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-7 .1 General Procedure of MSRN Allocation Figure 11-2 shows the general procedure of MSRN allocation. and sends a paging request to the callee. 10. After receiving the subscription information of the callee. MSRN allocation is processed at the callee side in the module. 8. and conveys flag bits to the VLR. The MSC of the callee analyzes access data. and sets up the call with the caller side.4 Service Flow 11. This section does not give details. and updates the values of the counters. and records the information required after the call is connected. The UE of the callee rings. 11. The MSC server completes the interaction between the C/D interfaces of the VLR and the HLR. 9.4. MAP_VLR_MSRNAllocate_RSP MAP_PROVIDE_ROAMING_NUMBER_RSP [msrn] [msrn] The VLR and HLR exchange and transfer the requests for MSRN allocation. The (G)MSC server sends a request for setting up the call to the VMSC server of the callee based on the MSRN. Figure 11-2 General procedure of MSRN allocation HLR MSOFTX3000 VLR MAP_PROVIDE_ROAMING_NUMBER_IND [GMSC NO] VP_VDB_GetCBData_PRN_VLR_Req MAP_VLR_GetCBData_PRN_RSP [CB_STATUS_PRN] Request MSRN after subscriber status check VP_VDB_MSRNAllocate_Req The VLR allocates an MSRN based on the MSRN allocation mode. the VMSC server checks the information. The callee sends a response to the MSC of the callee. The VLR allocates an MSRN based on the configuration in the MSC server.

the VLR allocates an intra-province roaming number so that the incoming call can be configured with a roaming number. and then allocates a roaming number based on the attribute of the callee. Figure 11-3 Procedure for random allocation HLR MSOFTX3000 VLR MAP_PROVIDE_ROAMING_NUMBER_IND [GMSC NO] Identify whether the incoming call is an interprovince call based on the GMSC number in the PRN message. the MSC server judges whether the incoming call is an inter-province call based on the gateway MSC (GMSC) number in the request. the MSC server cannot judge whether the incoming call is an inter-province call. In this case.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description 11. and record the Province Flag VP_VDB_GetCBData_PRN_VLR_Req [Province Flag] MAP_VLR_GetCBData_PRN_RSP [CB_STATUS_PRN] VP_VDB_MSRNAllocate_Req [Province] Flag The VLR allocates a roaming number based on the Province Flag and the property of the callee. MAP_VLR_MSRNAllocate_RSP MAP_PROVIDE_ROAMING_NUMBER_RSP [msrn] [msrn] Transfer the flag to the VLR after subscriber status check The MSC server works with the HLR and VLR to realize the enhanced MSRN allocation function through the C/D interfaces. If the inter-province roaming number resources of the callee are used up. The HLR must carry the GMSC number of the callee. The MSC server then stores the Province Flag in the MAP table so as to transfer the flag to the VLR when allocating a roaming number. When receiving a request for allocating a roaming number from the HLR. the MSC server regards the incoming call as an inter-province call by default. The VLR judges whether to use the inter-province roaming number resources based on the Province Flag in the request for allocating a roaming number.2 Procedure for Random Allocation Figure 11-3 shows the procedure for random allocation. otherwise.4. The MSC server analyzes the attribute of an incoming call. 11-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . and updates the values of the counters.

Both the MHSUFFIX commands and the IMHSUFFIX commands are used to configure the MSRN or HON Suffix table.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature 11.5. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-9 . the MSRN or HON Prefix table. the MSRN or HON Suffix table. The command ADD MHLAICFG or ADD MHMSCCFG is selected to configure the data. The mapping between the tables connected by the broken line is as follows: The MSRN or HON allocation mode is determined based on the parameter MSRN allocation mode or HON allocation mode in the VLR Configuration table. The Mapping Between LAI and MSRN or HON table and the Mapping Between MSC and MSRN or HON table are applicable to different allocation modes.1 Configuring Data at the MSOFTX3000 Side Mapping Between Tables Figure 11-4 shows the mapping between the MSRN or handover (HON) allocation tables. Figure 11-4 Mapping between the MSRN or HON allocation tables ADD/MOD VLRCFG [MSRN Allocation Mode] [HON Allocation Mode] ADD MHLAICFG [LAI Number] [Preferable Suffix Index] ADD MHSUFFIX/IMHSUFFIX ADD MHPREFIX [MSRN Prefix Index] [MSRN Prefix] [MSRN Suffix Length] [MSRN Suffix Index] [MSRN Prefix Index] [MSRN Suffix Start] [MSRN Suffix End] [MSRN Number Type] ADD MHMSCCFG [MSC Number] [Preferable Suffix Index] As shown in Figure 11-4. The differences are as follows: The IMHSUFFIX commands can configure inter-province roaming numbers. but they configure different types of roaming numbers. and the Inner MSRN or HON Suffix table are mandatory. The MHSUFFIX commands cannot configure the inter-province roaming numbers.5 Data Configuration 11.

modify the allocation mode by running MOD VLRCFG.5. This step is optional. Step 6 Run ADD IMHSUFFIX to add. or MOD IMHSUFFIX to modify the intra. MSRN/HON prefix is set to K'8613901106. and End MSRN/HON suffix to 499. Thus the roaming number resources are re-allocated.2 Configuraing Data at the UMG8900 Side None. Start MSRN/HON suffix to 500. run MOD MSFP to change the value of BIT of VLR software parameter 1 to 1 from 11. 11. Step 4 To allocate an MSRN or HON based on the LAI number or the MSC number. and the function of allocation based on the attributes of the call and the callee is enabled.and inter-province roaming numbers. The default allocation mode is Allocate randomly. MSRN/HON suffix ID is set to 1. Step 3 Run ADD MHSUFFIX to configure the suffix of the MSRN. This step is applicable only when the extended MSRN allocation function for the mode of random allocation is enabled. Step 9 For the mode of allocation based on the LAI number. Step 7 Run ADD MSRNCTR to configure the GMSC connected to the local office in the case of an intra-province incoming call. Step 5 To enable the extended MSRN allocation function for the mode of random allocation. Step 8 For the mode of allocation based on the MSC number. Step 2 Run ADD MHPREFIX to configure the prefix of the MSRN. Start MSRN/HON suffix to 000. and End MSRN/HON suffix to 599.3 Configuration Examples Scenario 1 The scenario is as follows: The local MSOFTX3000 serves as the MSC server of the peer office. This step is applicable only when the MSRN allocation control function is enabled. Inner MSRN/HON suffix ID is set to 2. ----End 11. run ADD MHMSCCFG to add the mapping between the MSC number and the MSRN or HON.5. perform the following steps: Step 1 Run ADD VLRCFG to configure the basic functions of the VLR.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description Configuration Steps To configure an MSRN or HON. run ADD MHLAICFG to add the mapping between the LAI number and the MSRN or HON. 11-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

ADD MHPREFIX: ID=1. Step 2 Add a mobile national access code. Step 5 Add an inner MSRN or HON suffix. PFXIDX=1. Description Script Set MSRN allocation mode to Allocate randomly. ADD NACODE: NAC=K'139. Inner MSRN/HON suffix ID is set to 4. and End MSRN/HON suffix to 599. ADD IMHSUFFIX: ID=2. and MSRN/HON suffix length to 3. Description Script Set MSRN/HON suffix ID to 1. The number of the GMSC connected to the MSOFTX3000 is 8613901105. Inner MSRN/HON suffix ID is set to 5. Start MSRN/HON suffix to 600. HPFX=K'8613901106. Start MSRN/HON suffix to 800. and End MSRN/HON suffix to 899. SFXS="500". SFXL=3. Description Script Set Mobile national access code to K'139. SFXS="000". Description Script Set Inner MSRN/HON suffix ID to 2. Description Script Set MSRN/HON prefix to K'8613901106. Scripts The scripts are as follows: Step 1 Modify VLR configuration. Step 3 Add an MSRN or HON prefix. PFXIDX=1. MSRNT=MSRNOPNCL. Step 4 Add an MSRN or HON suffix. Start MSRN/HON suffix to 700. MSRNT=MSRN. and End MSRN/HON suffix to 799. SFXE="599". MOD VLRCFG: MSRNAM=RAND. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-11 . and End MSRN/HON suffix to 499. SFXE="499". Start MSRN/HON suffix to 000. ADD MHSUFFIX: ID=1. and End MSRN/HON suffix to 699.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature Inner MSRN/HON suffix ID is set to 3. Start MSRN/HON suffix to 500.

SFXE="699". Step 9 Enable the extended MSRN allocation function of the VLR for the mode of random allocation. and LAI number to 460000001. Start MSRN/HON suffix to 800. PFXIDX=1. MSRN/HON suffix ID to 0. Step 7 Add an inner MSRN or HON suffix. ----End Scenario 2 The local MSOFTX3000 serves as the MSC server of the peer office. Description Script Set Inner MSRN/HON suffix ID to 4. SFXE="899". PFXIDX=1. ADDRESS=K'8613901105. PFXIDX=1.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description Step 6 Add an inner MSRN or HON suffix. 11-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . and End MSRN/HON suffix to 799. SFXS="600". There are two number ranges: The MSRN or HON of the cell in the 2G network ranges from 86136000040001 to 86136000040999. Description Script Set Inner MSRN/HON suffix ID to 3. and End MSRN/HON suffix to 899. ADD MSRNCTR: ADDRTYPE=GMSC. MSRN allocation mode is set to Allocate according to LAI number. Start MSRN/HON suffix to 700. MSRNT=MSRNOPCL. BIT=11. Start MSRN/HON suffix to 600. ADD IMHSUFFIX: ID=4. Step 8 Add an inner MSRN or HON suffix. MODTYPE=P1. SFXS="800". Description Script Enable the extended MSRN allocation function of the VLR for the mode of random allocation. and End MSRN/HON suffix to 699. Description Script Add MSRN allocation control. MSRNT=MSRNOPNCR. BITVAL=1. ADD IMHSUFFIX: ID=5. SFXE="799". Step 10 Add MSRN allocation control. MOD MSFP: ID=P200. ADD IMHSUFFIX: ID=3. Description Script Set Inner MSRN/HON suffix ID to 5. SFXS="700". MSRN/HON prefix ID is set to 0. MSRNT=MSRNOPCR.

MSRN/HON suffix ID to 1. MSRN/HON prefix ID is set to 0. SUFFIXSTART="0001". ADD MHSUFFIX: PREFIXINDEX=0. SUFFIXEND="1999". Scripts The scripts are as follows: Step 1 Modify VLR configuration. SUFFIXSTART="1000". ADD MHSUFFIX: PREFIXINDEX=1. NUMBERTYPE=MSRNHON. Step 5 Add an MSRN or HON suffix. Step 4 Add an MSRN or HON suffix. NUMBERTYPE=MSRNHON. MOD VLRCFG: MSRNAM=LAI. Description Script Set Mobile national access code to K'136. Description Script Set MSRN/HON suffix ID to 1. Start MSRN/HON suffix to 1000. ADD NACODE: NAC=K'136. SUFFIXEND="0999". and MSRN/HON suffix length to 4. Description Script Set MSRN/HON prefix to K'8613600004.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature The MSRN or HON of the cell in the 3G network ranges from 86136000041000 to 86136000041999. Description Script Set MSRN/HON suffix ID to 0. Description Script Set MSRN allocation mode to Allocate according to LAI number. Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-13 . Step 2 Add a mobile national access code. Step 3 Add an MSRN or HON prefix. and End MSRN/HON suffix to 1999. and LAI number to 460000003. and End MSRN/HON suffix to 0999. Start MSRN/HON suffix to 0001. ADD MHPREFIX: MHPREFIX=K'8613600004. MHSL=4.

8 Service Interaction None. The MSRN or HON of the cell in the 3G network ranges from 86136000041000 to 861360000419999. PRESUFFINDEX=0.6 Service Management None. Step 7 Add mapping between the LAI number and the MSRN or HON. 11. 11-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) .7 Charging and CDR The charging module puts the roaming number to be obtained into the call detail record (CDR). The billing center sorts different CDRs. and MSRN/HON suffix ID to 0. 11. Description You must add a cell first. Description Script List MSRN or HON suffixes.11 Enhanced MSRN Allocation Feature HUAWEI MSOFTX3000 Feature Description Step 6 List MSRN or HON suffixes. and then reports the CDR to the billing center. Script Step 8 Add mapping between the LAI and the MSRN or HON. and MSRN/HON suffix ID to 1. Description You must add a cell first. judges the types of calls. Script ----End 11. set LAI number to 460000003. PRESUFFINDEX=1. To add mapping between the LAI number and the MSRN or HON. LST MHSUFFIX. and charges the calls. ADD MHLAICFG: LAINUM="460000001". ADD MHLAICFG: LAINUM="460000003". The MSRN or HON of the cell in the 2G network ranges from 86136000040001 to 86136000040999. To add mapping between the LAI number and the MSRN or HON. set LAI number to 460000001.

2 Acronyms and Abbreviations Acronym/Abbreviation HON LAI MSRN Full Name Handover Number Location Area Identification Mobile Station Roaming Number Issue 02 (2007-06-10) Huawei Technologies Proprietary 11-15 . 11.9.HUAWEI MSOFTX3000 Feature Description 11 Enhanced MSRN Allocation Feature 11.1 Protocols and Specifications None.9 Reference 11.9.

.......12-9 12........12-18 12............................12-3 12...........1 MS-Originated Call (Early Assignment)............12-23 12..................................................................................................................................12-3 12................................................12-18 12........9............................................................................12-21 12.......................................................12-23 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ..................................................12-6 12.......................12-9 12.....................3............................................HUAWEI MSOFTX3000 Feature Description Contents Contents 12 Early and Late Assignment Feature.................................................12-22 12.....................................2 MS-Originated Call (Late Assignment) .....2...............................1 Service Description ......4...................................12-5 12....................................12-23 12......................................................................................................................................................................................................4...............12-22 12.............................2 Requirements for License ................12-4 12................................................................2 Definition ........................................................................7 Charging and CDR ............................12-22 12.................................12-4 12...................3 MS-Terminated Call (Early Assignment)........5............ 12-11 12..........................................................................................................................................5...............1.....2...................................................................................1 Early Resource Assignment for the Caller ..................................6........................2 Late Resource Assignment for the Caller................................................2 HLR Data Configuration..........12-3 12.........................................................................................................12-21 12................................................1 MSOFTX3000 Data Configuration.........................12-3 12.....12-2 12.............................................................................................................................................3 Benefits ..............................4..4 Late Resource Assignment for the Callee ................................................8 Service Interaction ..12-2 12......................................................................................................................................5.........................................................3 Early Resource Assignment for the Callee..............4.............12-2 12...........12-17 12............................................................3...........1 Function Code............................................................................................................................3 Applicable Version ....................................................................................2................................12-1 12................1 Protocols and Specifications ..................12-3 12..............................5 Data Configuration...9 Reference ...3 Working Principle.........................................9...............................................................................................................................4 Examples......6.......................12-13 12.....................................................................................................1.........................1 Requirements for NEs...............................................................................................................................1.........................2 Acronyms and Abbreviations ..............................................6 Service Management ....................................................................................1 Querying the Resource Assignment Mode...............................12-17 12.....................3......................................................................2 Availability ........................................4 Service Flow...........................................................5.......................................................2 Changing the Resource Assignment Mode ........................12-15 12.......................12-18 12....3 UMG8900 Data Configuration ..............................

.12-16 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ........12-4 Figure 12-2 MS-originated call (late assignment) ................12-12 Figure 12-7 Early resource assignment for the callee..............................12-10 Figure 12-6 Late resource assignment for the caller ....................................................................................................................................................................................................................12-8 Figure 12-5 Early resource assignment for the caller .......................................................................................................................................................12-5 Figure 12-3 MS-terminated call (early assignment) .................................12-6 Figure 12-4 MS-terminated call (late assignment) .....................................................................................12-14 Figure 12-8 Late resource assignment for the callee ..............................................................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 12-1 MS-originated call (early assignment)...........................................................................................

............................................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 12-1 Requirement for NEs .........12-3 Table 12-2 Applicable versions...............................................................12-3 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ............................................................................

Describes The function code. The protocols and specifications that this feature must comply with.7 Charging and CDR 12.3 Working Principle 12. The charging and the generation of CDRs when the network provides this feature. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 12 Section Early and Late Assignment Feature About This Chapter The following table lists the contents of this chapter. and networking requirements. whether Licenses are required.1 Service Description 12. and the benefits that carriers and mobile subscribers can obtain from this feature.6 Service Management 12. The service flow of the network when providing this feature. and the acronyms and abbreviations of this chapter. and the version requirements of the NEs.5 Data Configuration 12. The network elements (NEs) that are required for the feature.4 Service Flow 12.8 Service Interaction 12. The data configurations that are required on the MSOFTX3000 and the UMG8900. The functions of the NEs. 12.2 Availability 12.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-1 . function definition of this feature. The relationships and restrictions between this feature and other services or features.

In the call establishment. The definitions of the two modes of assignments at the caller side are as follows: Name Early assignment Late assignment Definition In the call establishment. the network resources are allocated after the MS of the callee rings. after sending the Call Proceeding message to the caller. after sending the Call Proceeding message to the caller. that is.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description 12.1 Service Description 12. Usually. the traffic channels are allocated after the callee sends the Connect message. the MSC server allocates traffic channels for the caller after routing the call to the network where the callee resides. There are two modes of assignments in call establishment. The MSC server determines when to allocate the traffic channels. The definitions of the two modes of assignments at the callee side are as follows: Name Early assignment Late assignment Definition The MSC server allocates the traffic channels for the subscriber after receiving the Call Confirmed message. Then the callee sends the Call Confirmed message and then immediately the Alerting message to the MSC server. 12-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the MSC server allocates traffic channels for the caller before routing the call to the network where the callee resides.2 Definition Resource assignment refers to the process of wireless resource allocation in call establishment. the MSC server notifies the callee that the traffic channels are allocated in Late assignment mode. Usually.1.1 Function Code Name Early and Late Assignment of Resources for Mobile Subscribers Code WMFD-161100 12. early assignment and late assignment. Through the Setup message.1.

The operator can utilize well the air interface resources based on the actual assignment modes of each location area or service area. if a subscriber dials the wrong number and immediately terminates the call.2.3 Applicable Version The applicable HUAWEI CS product versions are shown in Table 12-2. 12.3 Benefits Beneficiary Operator Description Late assignment can help to save the air interface resources. Table 12-2 Applicable versions Product MSC Server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V100R002 and later versions Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-3 .2. 12. A license is not required.2.1. and CN. Early assignment can help to reduce the wait time of the subscribers and improve the call completion rate. the MSC server needs not to allocate air interface resources for the subscriber. For example. RNC.2 Availability 12.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 12. Table 12-1 Requirement for NEs UE/ MS √ NodeB /BTS √ RNC/ BSC √ MSC Server √ MGW √ SGSN √ GGSN VLR √ HLR √ The symbol √ represents that the NEs are involved. as shown in Table 12-1.2 Requirements for License Early and late assignment is a basic service. Subscriber 12.1 Requirements for NEs The function is implemented through the cooperation of NodeB.

for example. 3. 2. 4.1 MS-Originated Call (Early Assignment) Figure 12-1 illustrates the MS-originated call flow for early assignment. 12. is early assignment. The two assignment modes are both implemented by configuring the information table of the local location area or service area. The MS requests the MM channel to be allocated through the CM Service Request message. emergency calls and data services. The assignment mode for some special services. (optional) 12-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description 12. In the call establishment. the MSOFTX3000 determines that the assignment mode of the call is early or late assignment by querying the information table of the location area or the service area. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. The MSC server starts the authentication flow when the MM channel is being established.3 Working Principle The MSOFTX3000 supports both early and late assignments. The MS sends the Channel Request message. Figure 12-1 MS-originated call (early assignment) MS/UE Channel Request Immediate Assignment CM Service Request Authentication Request Authentication Response Cipher Mode Command Cipher Mode Complete Setup Call Proceeding Assignment Command Assignment Complete Alerting Connect Connect Acknowledge Network The call flow for early assignment is as follows: 1.3.

HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 5. Figure 12-2 MS-originated call (late assignment) MS/UE Channel Request Immediate Assignment CM Service Request Authentication Request Authentication Response Cipher Mode Command Cipher Mode Complete Setup Call Proceeding Alerting Assignment Command Assignment Complete Network Connect Connect Acknowledge The MS-originated call flow for late assignment is as follows: Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-5 . After the callee answers the call.3. the MS sends the Setup message to the MSC server to request the call to be established. The MSC server sends the assignment request and begins the traffic channel allocation. The ring back tone is provided by the MSC server. 10. The MSC server starts the encryption flow when the MM channel is being established.2 MS-Originated Call (Late Assignment) Figure 12-2 illustrates the MS-originated call flow for late assignment. 7. The MSC server determines that the assignment mode is early assignment by querying the information table of the location area and then returns the Call Proceeding message to the MS. (optional) After the MM channel is allocated. the conversation between the two parties begins and the MS-originated call is established successfully. 11. 9. 8. After the MS of the callee rings. 12. the MSC server sends the Alerting message together with the progress indicator cell to the MS of the caller to indicate the MS to tune to the allocated channel. 6.

10. 9.3 MS-Terminated Call (Early Assignment) Figure 12-3 illustrates the MS-terminated call flow for early assignment. 12. After the callee answers the call. After the traffic channel is allocated.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description 1. 6. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. 3. 8. the MSC server plays the ring back tone to the MS. the MSC server sends the Alerting message to the MS of the caller. The MSC server delivers the Assignment request to request the traffic channel to be allocated. 5. 2. The MS requests the MM channel to be allocated through the CM Service Request. After the phone of the callee rings. The MSC server determines that the assignment mode is late assignment by querying the information table of the location area and then returns the Call Proceeding message to the MS. (optional) After the MM channel is allocated. 4. (optional) The MSC server starts the encryption flow when the MM channel is being established. The network starts the authentication flow when the call is being established. 7. the MS sends the Setup message to MSC server to request the call to be established.3. The MS sends the Channel Request message. Figure 12-3 MS-terminated call (early assignment) MS/UE Paging Channel Request Immediate Assignment Paging Response Authentication Request Authentication Response Cipher Mode Command Cipher Mode Complete Setup Call Confirmed Assignment Command Assignment Complete Alerting Connect Connect Acknowledge Network 12-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the MS tunes to the traffic channel and the MS-originated call is established.

(optional) After the MM channel is allocated. 2. 12. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-7 . the MSC server determines that the assignment mode is early assignment by querying the information table of the location area and then sends the Setup message to request the call to be established. The MSC server begins to allocate the MM channel. the MS sends the Paging Response message to the network side. 6. 5. The network starts the authentication flow when the call is being established.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature The MS-terminated call flow for early assignment is as follows: 1. 4. The network sends the Paging message to request the call to be established. the MS sends the Channel Request message to the network side. MS-Terminated Call (Late Assignment) Figure 12-4 illustrates the MS-terminated call flow for late assignment. 8. 9. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. 3. The MS sends the Call Confirmed message to the network. (optional) The MSC server starts the encryption flow when the MM channel is being established. 10. The MSC server begins to allocate the network resources after receiving the Call Confirmed message 11. After detecting that it is the target MS by checking the IMSI/TMSI. 7. The mobile-terminated call is established successfully after the callee answers the call. The MS sends the Alerting message to the network only after the traffic channel is allocated successfully. After the RR channel is allocated.

The network starts the authentication flow when the call is being established. (optional) After the MM channel is allocated. The callee sends the Call Confirmed message to the MSC server. After detecting that it is the target MS by checking the IMSI/TMSI. 9. The MSC server begins to allocate the MM channel. the MSC server determines that the assignment mode is late assignment by querying the information table of the location area and then sends the Setup message to request the call to be established. 12-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 5. 8. 7. 6. the MS sends the Channel Request message to the network side. the MS sends the Paging Response message to the network side. The network sends the Paging message to request the call to be established.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Figure 12-4 MS-terminated call (late assignment) MS/UE Network Paging Channel Request Immediate Assignment Paging Response Authentication Request Authentication Response Cipher Mode Command Cipher Mode Complete Setup Call Confirmed Alerting Connect Assignment Command Assignment Complete Connect Acknowledge The MS-terminated call flow for late assignment is as follows: 1. (optional) The MSC server starts the encryption flow when the MM channel is being established. 2. 3. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. 4. The MSC server notifies the MS that the assignment mode is late assignment by the Setup message. After the RR channel is allocated.

11. 13. The callee sends immediately the Alerting message to the MSC server. the MSC server sends the Connect Acknowledge message to the callee and the call is established successfully. 12. 12. Therefore. The callee sends the Connect message to the MSC server. You can determine whether to start the processes by configuring system data. The MSC server delivers the assignment request after receiving the Connect message.4. 12.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 10. After the network resources are allocated for the callee. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-9 .4 Service Flow This section describes the early and late assignment flow by taking an intra-office call as example. The authentication and encryption processes are optional. the two processes are not included in the following flow chart.1 Early Resource Assignment for the Caller Figure 12-5 illustrates the flow of early resource assignment for the caller.

the MS sends the Setup message to the MSC-O through the BSS. The HLR requests the roaming number of the callee from the MSC/VLR where the callee resides. After receiving the CM Service Accept message. The MSC-O sends the CM Service Accept message to the MS through the BSS to indicate that the request is accepted. 3. The HLR provides the routing information of the callee to the MSC-O. 2.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Figure 12-5 Early resource assignment for the caller MS/UE BSS/RNC MSC-O/VLR HLR MSC-T/VLR CM Service Request CM Service Request CM Service Accept CM Service Accept Setup Call Proceeding Send Routing Information Provide Roaming Number Provide Roaming Number Acknowledge Send Routing Info Acknowledge Alllocate Channel Assignment Command Assignment Complete Allocate Complete Alerting Connect Connect Acknowledge The flow of early resource assignment for the caller is as follows: 1. 7. The VLR provides the roaming number of the callee to the HLR. 5. 4. 12-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 6. 8. The MSC-O requests routing information of the callee from the HLR. The MSC-O sends the Call Proceeding message to the MS. The MS sends the CM Service Request message to the MSC-O through the BSS.

the MS sends the Assignment Complete message to the BSS and the BSS sends the Allocation Complete message to the MSC-O to indicate that the assignment is complete. The MSC-O sends the Connect message to the MS to indicate that the callee has answered the call.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 9. The MS sends the Connect Acknowledge message to the MSC-O and the call is established. The MSC-O requests the BSS to allocate the channel and the BSS sends the assignment request to the MS.2 Late Resource Assignment for the Caller Figure 12-6 illustrates the flow of late resource assignment for the caller. 10. 12. The MSC-O sends the Alerting message to the MS to indicate that the MS of the callee is ringing. 12. 13. After the channel is allocated. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-11 . 11.4.

The HLR requests the roaming number of the callee from the MSC/VLR where the callee resides. The VLR provides the roaming number of the callee to the HLR. the MS sends the Setup message to the MSC-O through the BSS. 3. The MSC-O sends the Call Proceeding message to the MS.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Figure 12-6 Late resource assignment for the caller MS/UE BSS/RNC MSC-O/VLR HLR MSC-T/VLR CM Service Request CM Service Request CM Service Accept CM Service Accept Setup Call Proceeding Send Routing Information Provide Roaming Number Provide Roaming Number Acknowledge Send Routing Info Acknowledge Alerting Alllocate Channel Assignment Command Assignment Complete Allocate Complete Progress Connect Connect Acknowledge The flow of late resource assignment for the caller is as follows: 1. After receiving the CM Service Accept message. The MSC-O requests routing information of the callee from the HLR. 2. The MSC-O sends the CM Service Accept message to the MS through the BSS to indicate that the request is accepted. 4. The MS sends the CM Service Request message to the MSC-O through the BSS. 8. 7. The HLR provides the routing information of the callee to the MSC-O. 12-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 6. 5.

13. The MSC-O sends the Progress message to the MS to indicate that the assignment is complete. The MSC-O requests the BSS to allocate the channel and the BSS sends the assignment request to the MS. The MSC-O sends the Connect message to the MS to indicate that the callee has answered the call. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-13 .4.3 Early Resource Assignment for the Callee Figure 12-7 illustrates the flow of early resource assignment for the callee. The MS sends the Connect Acknowledge message to the MSC-O and the call is established.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 9. 12. 10. 14. the MS sends the Assignment Complete message to the BSS and the BSS sends the Allocation Complete message to the MSC-O to indicate that the assignment is complete. After the channel is allocated. 11. The MSC-O sends the Alerting message to the MS to indicate that the MS of the callee is ringing. 12.

After detecting that it is being paged. the MSC delivers the Paging message to the BSS and the BSS broadcasts the Paging message through the paging channel. 2. the MS sends the Channel Request message to the BSS to request a channel.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Figure 12-7 Early resource assignment for the callee MSC/VLR BSS MS Paging Paging Channel Request Immediate Assignment Paging Response Paging Response Setup Call Confirmed Allocate Channel Assignment Command Assignment Complete Allocate Complete Alerting Connect Connect Acknowledge The flow of early resource assignment for the callee is as follows: 1. The BSS returns the Immediate Assignment message to notify the MS to use a dedicated signaling channel. 3. If no wireless connection is set up between the network and the callee. The MSC sends the Setup message to the MS. The MS sends the Paging Response message through the channel to the BSS and the BSS sends the Paging Response message to the MSC. 4. 12-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

the MS sends the Assignment Complete message to the BSS and the BSS sends the Allocation Complete message to the MSC to indicate that the assignment is complete. 12.4 Late Resource Assignment for the Callee Figure 12-8 illustrates the flow of late resource assignment for the callee. After the callee has answered the call. After the assignment is complete. 10. The MSC sends the Connect Acknowledge message to the MS and the call is established. 7. 8. 6. the MS sends the Connect message to the MSC. The MS returns the Call Confirmed message to the MSC after receiving the Setup message. The MS sends the Alerting message to the MSC to indicate that the MS of the callee is ringing. 9. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-15 .4. The MSC requests the BSS to allocate the channel after receiving the Call Confirmed message and the BSS sends the assignment request to the MS.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 5.

the MS sends the Channel Request message to the BSS to request for a channel. The MSC sends Setup message to the MS. If there is no wireless connection between the network and the callee. 2. The BSS returns the Immediate Assignment to indicate the MS to use a dedicated signaling channel. 12-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . After detecting that it is being paged. The MS sends the Paging Response message through the channel to the BSS and the BSS sends the Paging Response message to the MSC.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Figure 12-8 Late resource assignment for the callee MSC/VLR BSS MS Paging Paging Channel Request Immediate Assignment Paging Response Paging Response Setup Call Confirmed Alerting Connect Allocate Channel Assignment Command Assignment Complete Allocate Complete Connect Acknowledge The flow of late resource assignment for the callee is as follows: 1. the MSC delivers the Paging message to the BSS and the BSS broadcasts the Paging message through the paging channel. 4. 3.

Step 4 Use the LST OFC command to check if the office direction number is configured for the BSC that the cell belongs to. The MSC requests the BSS to allocate the channel and the BSS sends the Assignment request to the MS.) ----End Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-17 . 6. After the callee has answered the call. use the ADD CALLSRC command to add the source code for the cell. If they are not configured. The MS sends the Alerting message to the MSC to indicate that the MS of the callee is ringing. (Configure the parameters based on the information obtained in the preceding query and select GCI for the location area type. use the ADD BSC command to add the BSC and its destination signaling point code.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 5. If it is not configured. The steps are as follows: Step 1 Use the LST INOFFMSC command to check if the local MSC and the VLR numbers are configured. 8. the assignment mode is configured when the GCI is being added.5 Data Configuration 12. The MS returns the Call Confirmed message to the MSC after receiving the Setup message. Step 2 Use LST BSC command to check if the BSC that the cell belongs to and its destination signaling point code are configured. After the assignment is complete. Step 3 Use the LST CALLSRC command to check if the call source code corresponding with the cell is configured. use the SET INOFFMSC command to configure the local MSC and VLR numbers. If it is not configured. 7.) Step 6 Use the ADD LAIGCI command to add a cell and set the assignment type of the cell. Step 5 Use the LST LAIGCI command to check if the LAI that the cell belongs to is configured. 9. the MS sends the Assignment Complete message to the BSS and the BSS sends the Allocation Complete message to the MSC to indicate that the assignment is complete.1 MSOFTX3000 Data Configuration For 2G network. 10. use the ADD LAIGCI command to add the LAI that the cell belongs to. 12. If it is not configured.5. the MS sends the Connect message to the MSC. (Configure the parameters based on the information obtained in the preceding query and set the location area type to LAI. use the ADD OFC command to add the office direction number for the BSC that the cell belongs to. If they are not configured. The MSC sends the Connect Acknowledge message to the MS and the call is established.

Step 3 Use the LST CALLSRC command to check if the call source code of the cell is configured. If it is not configured. 12.5.5. the assignment mode is configured when the SAI is being added. If it is not configured. If they are not configured. Step 5 Use the LST LAISAI command to check if the LAI that the cell belongs to is configured. use the ADD RNC command to add the RNC and its destination signaling point code. use the ADD OFC command to add the office direction number of the RNC that the cell belongs to. The steps are as follows: Step 1 Use the LST INOFFMSC command to check if the MSC and the VLR numbers of the local office are configured. If it is not configured. Step 2 Use the LST RNC command to check if the RNC that the cell belongs to is configured.5. (Configure the parameters based on the information obtained in the preceding query and set the location area type as LAI.) ----End 12.2 HLR Data Configuration None.4 Examples Case 1 In the following environment: Network: 2G Local MSC number: 8613600004 VLR number: 8613600004 Call source name: CS-1 12-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) .12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description For 3G network.) Step 6 Use the ADD LAISAI command to add a cell and set the assignment type of the cell. (Configure the parameters based on the information obtained in the preceding query and set the location area type as SAI. use the ADD LAISAI command to add the LAI that the cell belongs to. If it is not configured.3 UMG8900 Data Configuration None. 12. Step 4 Use the LST OFC command to check if the office direction number of the RNC that the cell belongs to is configured. use the ADD CALLSRC command to add the call source code corresponding with the cell. use the SET INOFFMSC command to configure them.

CSNAME="CS-1". BSCDPC1="C01". LAIT=HVLR. LAIGCINAME="BSC1-LAI". Description ----End Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-19 . Step 2 Add a 2G cell. LAIT=HVLR. LAICAT=LAI. ISEARASN=LATEASN. LAICAT=GCI. CSNAME="CS-1". Description To add a 2G location area with the following attributes: Global cell ID: 460000001 MSC number: 8613600004 VLR number: 8613600004 Location area category: LAI Home BSC DPC: C01 Call source name: CS-1 Script ADD LAIGCI: GCI="460000001". Description To add a 2G cell with the following attributes: Global cell ID: 4600000010001 MSC number: 8613600004 VLR number: 8613600004 Location area category: GCI Early assignment flag: LATEASN Home BSC DPC: C01 Call source name: CS-1 Script ADD LAIGCI:GCI="4600000010001".HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature Add a cell with the following attributes: Assignment mode: late assignment BSC name: BSC-1 Destination signaling point code: C01 Other parameters: default values Script The step to add the 2G cell is as follows: Step 1 Add a 2G location area. VLRN="8613600004". BSCDPC1="C01". MSCN="8613600004". The ISEARASN parameter is valid only when the value of the LAICAT parameter is GCI. VLRN="8613600004".LAIGCINAME="BSC1-GCI". MSCN="8613600004".

LAICAT=LAI. MSCN="8613600004". Step 2 Add the information of the 3G service area. LAISAINAME="RNC1-LAI". VLRN="8613600004". CSNAME="CS-1". Description To add a 3G location area with the following attributes: Service area number: 460000001 MSC number: 8613600004 VLR number: 8613600004 Location area category: LAI RNC ID: 1 Call source name: CS-1 Script ADD LAISAI: SAI="460000001". LAIT=HVLR.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description Case 2 In the following environment: Network: 3G Local MSC ID: 8613600004 VLR number: 8613600004 Call source name: CS-1 Add a 3G service area with the following attributes: Assignment mode: early assignment RNCID: 1 Other parameters: default values Script The step to add the 3G cell is as follows: Step 1 Add the information of the 3G location area. RNCID1=1. 12-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

skip step 2. Step 2 Enter the ID of the cell to be queried in the Global cell ID field. LAISAINAME="RNC1-SAI". Step 3 Press F9 or click ----End If you want to query the assignment modes of all the cells. The ISEARASN parameter is valid only when the value of the LAICAT parameter is SAI. perform the following steps: Step 1 Enter the LST LAISAI command in the command line window of the LMT. Step 2 Enter the number of the service area to be queried in the SAI field. Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-21 . RNCID1=1. CSNAME="CS-1".HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature Description To add a 3G service area with the following attributes: Service area number: 4600000010001 MSC number: 8613600004 VLR number: 8613600004 Service area category: SAI Early assignment flag: EARLYASN RNC ID: 1 Call source name: CS-1 Script ADD LAISAI: SAI="4600000010001". ISEARASN=EARLYASN. perform the following steps: Step 1 Enter the LST LAIGCI command in the command line window of the LMT. Step 3 Press F9 or click ----End . .6 Service Management 12. LAICAT=SAI. MSCN="8613600004".1 Querying the Resource Assignment Mode 2G Network To query the resource assignment mode of a specified cell.6. VLRN="8613600004". Description ----End 12. 3G Network To query the resource assignment mode of a specified service area. LAIT=HVLR.

skip step 2. Step 2 Enter the number of the service area to be modified in the 3G service area number field. 3G Network To change the resource assignment mode of a specified service area. 12. 12-22 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Step 6 Press F9 or click ----End . 12. 12. Step 3 Enter the MSC ID of the location area to be modified in the MSC number of the LA cell field. Step 5 Set the Early assignment flag to the required mode.2 Changing the Resource Assignment Mode 2G Network To change the resource assignment mode of a specified cell.7 Charging and CDR None.12 Early and Late Assignment Feature HUAWEI MSOFTX3000 Feature Description If you want to query the assignment modes of all the service areas. Step 4 Set the Location area type to Local VLR. Step 3 Enter the MSC number of the 3G service area to be modified in the MSC number of 3G service area field. perform the following steps: Step 1 Enter the MOD LAISAI command in the command line window of the LMT. perform the following steps: Step 1 Enter the MOD LAIGCI command in the command line window of the LMT.8 Service Interaction The setting of the resource assignment type has no effect on the supplementary services.6. Step 5 Set the Early assignment flag to the required mode. Step 6 Press F9 or click ----End . Step 2 Enter the ID of the cell to be modified in the Global cell ID field. Step 4 Set the 3G service area type to Local VLR.

9 Reference 12.HUAWEI MSOFTX3000 Feature Description 12 Early and Late Assignment Feature 12.1 Protocols and Specifications None. Abbreviations Abbreviation BSC BSS HLR IMSI MM MS MSC RNC RR TMSI VLR Full Name Base Station Controller Base Station Subsystem Home Location Register International Mobile Station Identity Mobility Management Mobile Station Mobile Switching Center Radio Network Controller Radio Resource management Temp Mobile Subscriber Identifier Visitor Location Register Issue 02 (2007-06-10) Huawei Technologies Proprietary 12-23 . 12.9.2 Acronyms and Abbreviations Acronyms None.9.

.................................................................................................................................13-2 13..................1 Specifications...........................................................3 Data Configuration for UMG8900..9............................................13-2 13............................5......................13-3 13...........4 Example ........13-10 13.........................................13-14 13................................................................5.5.................................2..............................4 Service Flow.......6 Service Management ...............3 Applicable Versions.....................................................13-10 13...................................................................................2....................................................................................................................2 Requirement for License..................................1 Service Description ............13-1 13..................3 Working Principle..............................2..........................................1..............13-15 13.......................................................13-3 13.........13-15 13...........................8 Service Interaction ....................................................................1 Data Configuration for MSOFTX3000 ...........................................................................13-10 13.........................................................................................................................................................13-14 13.............................................................................................................13-3 13.......................1 Requirement for NEs ...........................................................................................................................................9.2 Definition ....................................................................................................2 Acronyms and Abbreviations ........................................................................................................................13-3 13................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 13 IN Service Triggering Feature .................................1..........................1 Function Code...................................13-10 13...........................................................1.........................................................................................................................................13-3 13.......................................9 References ..........................13-10 13..2 Data Configuration for HLR9820 ............................................ 13-11 13.............................................................................................................................3 Benefits .......................13-2 13............................................................................................................2 Availability ...5..............................................13-2 13..13-14 13........................................................................5 Data Configuration...................7 Charging and CDR .........................................................................................13-15 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .........................

...............................................................................................13-8 Figure 13-6 Ignoring IN service (early forwarding with O-CSI) ...........................................................................................................................................13-4 Figure 13-2 Routing out the call directly to another office (T -CSI) .............Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 13-1 Triggering IN service (T-CSI)....13-7 Figure 13-5 Routing out the call directly to another office (early forwarding with O-CSI).........13-5 Figure 13-3 Ignoring IN service (T-CSI)..............................................................13-9 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ......................................................13-6 Figure 13-4 Triggering IN service (early forwarding with O-CSI) ..............................................................

........................13-2 Table 13-3 NEs related to the IN service triggering .............................................13-2 Table 13-2 Processing modes of the IN services .................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 13-1 Name and function code of the IN service triggering...........................................................13-3 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ...13-3 Table 13-4 Versions that support the IN service triggering........................................................................................................................................

and networking requirements.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 13 About This Chapter Section 13.8 Service Interaction 13. The functions of the NEs.9 References Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-1 . The network elements (NEs) that are required for the feature. The relationships and restrictions between this feature and other services or features.6 Service Management 13. 13.1 Service Description 13.7 Charging and CDR 13. whether Licenses are required.5 Data Configuration 13. and the benefits that carriers and mobile subscribers can obtain from this feature.3 Working Principle 13. The data configurations that are required on the MSOFTX3000 and the UMG8900. The charging and the generation of CDRs when the network provides this feature. function definition of this feature. The protocols and specifications that this feature must comply with. The service flow of the network when providing this feature.4 Service Flow 13. and the version requirements of the NEs. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.2 Availability IN Service Triggering Feature The following table lists the contents of this chapter. and the acronyms and abbreviations of this chapter. Describes The function code.

The MSOFTX3000 does not trigger IN service and connects the call to the MSC/SSP that can trigger the IN service normally. The MSOFTX3000 does not trigger IN service and connects the call as an ordinary call. The IN service triggering feature is supported only by the GMSC and TMSC. The carrier can determine the processing mode based on the actual situation. Table 13-1 Name and function code of the IN service triggering. the MSOFTX3000 uses three modes to process the IN service s. thus the competitiveness of the carriers is highly enhanced. To solve this problem.1. the MSOFTX3000 fails to trigger the intelligent service (IN service ) when processing IN calls of the IN service subscribers (the subscribers who subscribe to the IN service s in the HLR).13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description 13.1. Table 13-2 Processing modes of the IN services Processing Mode Triggering IN service Routing out the call directly to another office Ignoring IN service Indication The MSOFTX3000 triggers the IN service in the O-CSI or T-CSI mode. 13.1 Service Description 13.1.1 Function Code Table 13-1 lists the name and function code of the IN service triggering. as shown in Table 13-2.2 Definition If MSOFTX3000 is adopted in the GMSC/SSP networking. The connected to MSC/SSP triggers the IN service. 13-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The subscribers can enjoy the IN services.3 Benefits Beneficiary Carrier Mobile subscriber Description The carrier can control the IN service s more flexibly. Name CAMEL phase2 CAMEL phase3 Code WMFD-150100 WMFD-150200 Applicable Versions V100R005 13. and if the SCP interconnected with the MSOFTX3000 uses private INAP protocol.

2. Table 13-3 lists the NEs related with the IN service triggering. You can obtain this service without any license. it queries the IN service control data table.2 Availability 13.1 Requirement for NEs The IN service triggering feature requires the corporation of the SCP and CN.3 Applicable Versions Table 13-4 lists the Huawei CS product versions that support the IN service triggering. The MSOFTX3000 has the following processing modes: Triggering IN Service (T-CSI) Routing Out the Call Directly to Another Office (T-CSI) Ignoring IN Service (T-CSI) Triggering IN Service (Early Forwarding With O-CSI) Routing Out the Call Directly to Another Office (Early Forwarding with O-CSI) Ignoring IN Service (Early Forwarding With O-CSI) Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-3 . 13. and then processes the IN call based on the query results. Table 13-3 NEs related to the IN service triggering UE – Node B – RNC – MSC Server √ MGW √ SGSN – VLR √ HLR √ SCP √ "√" stands for the related NEs.2 Requirement for License The IN service triggering is an optional feature of the Huawei wireless core network. Table 13-4 Versions that support the IN service triggering Product MSC server MGW MSOFTX3000 UMG8900 Applicable Versions V100R005 and the later versions V100R005 and the later versions 13.2.2. 13.3 Working Principle After the MSOFTX3000 obtains IN service data from the HLR.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 13.

The GMSC sends for the second time the SRI message to the HLR of the called party. The GMSC sends the SRI message to the HLR of the called party. The HLR responses the SRI_ACK message to the GMSC. The SRI_ACK contains the T-CSI subscription information of the called party.IDP(DP12) VMSCa HLR SCP VMSCb 6.ACM 12. 7. The GMSC queries the IN service control data table. 5. the MSOFTX3000 triggers the IN service in the T-CSI mode.SRI_ACK(MSRN) 9. Call process The call procedure is as follows: 1.SRI 3. IN service triggering flow 7. The IN service triggering process completes. The GMSC receives the IAM message from the VMSC of the calling party.IAM 10. The SCP of the called triggers the IN service after receiving the IDP message. and if the T-CSI subscription information is contained in the subscription data of the called party. 3.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description Triggering IN Service (T-CSI) If the call is an IN call of the MT type.SRI 8. 4. 6. Figure 13-1 Triggering IN service (T-CSI) GMSC (MSOFTX3000) 1. The call procedure is as shown in Figure 13-1.IAM 2.SRI_ACK(TCSI) 4. The query result is "Triggering IN service ". Query IN service control data table 5. The GMSC sends the IDP (IDP12) message to the SCP to of the called party according to the SCP address in the T-CSI subscription data. 2. The SRI message contains the suppression T-CSI cell. 13-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) .ACM 11.

SRI_ACK(TCSI) 4. and if the T-CSI subscription information is contained in the subscription data of the called party. 4.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 8. The call is established. Routing Out the Call Directly to Another Office (T-CSI) If the call is an IN call of the MT type. 2. The call procedure is as shown in Figure 13-2. 5. 6. 9. The GMSC responses the ACM message to the VMSC of the calling party. The VMSC of the called party responses an ACM message to the GMSC.IAM 2. The SRI_ACK contains the T-CSI subscription information of the called party.SRI 3. 3. the MSOFTX3000 does not trigger the IN service and connects the call to the MSC/SSP which can trigger the IN service normally. The GMSC sends an IAM message to the MSC/SSP according to the MSC/SSP routing information in the IN service control data table. The MSC/SSP responses the ACM message to the GMSC. The GMSC sends the SRI message to the HLR of the called party.ACM GMSC HLR MSC/SSP 8. 12. 10.ACM 7. Call process The call procedure is as follows: 1. Figure 13-2 Routing out the call directly to another office (T -CSI) VMSCa 1. The GMSC receives the IAM message from the VMSC of the calling party. The HLR responses the SRI_ACK to the GMSC. The GMSC queries the IN service control data table. The GMSC sends the IAM message to the VMSC of the called party according to the MSRN number of the called party. Query the IN service control data table 5IAM 6. The GMSC responses the ACM message to the VMSC of the calling party. The SRI_ACK contains the MSRN number of the called party. 7. Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-5 . The HLR responses the SRI_ACK message to the GMSC. The query result is "Routing out the call directly to another office". 11.

8. The GMSC receives the IAM message from the VMSC of the calling party. The SRI message contains the suppression T-CSI cell. The SRI_ACK contains the MSRN number of the called party. 2. The HLR responses the SRI_ACK message to the GMSC. The query result is "Ignoring IN service ". 10.ACM 10. The call is established. 6. The HLR responses the SRI_ACK to the GMSC. 13-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . and if the T-CSI subscription information is contained in the subscription data of the called party. The GMSC sends for the second time the SRI message to the HLR of the called party.SRI 6. 4. The SRI_ACK contains the T-CSI subscription information of the called party. Query the IN service control data table 5. The call is established. the MSOFTX3000 does not trigger the IN service and connects the call as an ordinary call.SRI_ACK(TCSI) 4. 3.ACM 9. Ignoring IN Service (T-CSI) If the call is an IN call of the MT type. 9. The GMSC responses the ACM message to the VMSC of the calling party. 5. The GMSC sends the IAM message to the VMSC of the called party according to the MSRN number of the called party. The VMSC of the called party responses an ACM message to the GMSC.IAM 8.SRI_ACK(MSRN) 7. The call procedure is as shown in Figure 13-3. Call process 1.SRI 3. The GMSC queries the IN service control data table.IAM GMSC HLR SCP VMSCb 2.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description 8. 7. The GMSC sends the SRI message to the HLR of the called party. Figure 13-3 Ignoring IN service (T-CSI) VMSCa 1.

5. Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-7 . The SRI_ACK contains the call forwarding subscription information and the O-CSI subscription information of the called party. 2. Figure 13-4 Triggering IN service (early forwarding with O-CSI) VMSCa 1. The call procedure is as shown in Figure 13-4. 6. Call process The call procedure is as follows: 1. 3. The GMSC sends the IDP (DP2) message to the SCP of the called party according to the SCP address in the O-CSI subscription information. The GMSC sends the SRI message to the HLR of the called party. the MSOFTX3000 triggers the IN service in the O-CSI mode. The HLR responses the SRI_ACK message to the GMSC. Query the IN servie control data table 3.IAM GMSC HLR SCP VMSCb 2. The query result is "Triggering IN service ".SRI_ACK (early forwarding with O-CSI) 5. 4.ACM 12. and if the called party subscribes to the call forwarding service and the O-CSI service. The GMSC launches call forwarding according to the call forwarding subscription information of the called party.IDP(DP2) 7.ACM 13.SRI_ACK(MSRN) 10. The GMSC receives the IAM message from the VMSC of the calling party. The GMSC queries the IN service control data table.IAM 11.SRI 4. IN service triggering flow 8.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature Triggering IN Service (Early Forwarding With O-CSI) If the call is an IN call of the MF type.SRI 9. Call forwarding flow 6.

The HLR responses the SRI_ACK message to the GMSC. The HLR of the forwarded-to party responses an SRI_ACK to the GMSC.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description 7.SRI_ACK (early forwarding with O-CSI) 5. The GMSC receives the IAM message from the VMSC of the calling party.ACM 4.SRI 3. 10. 12. Query the IN service control data table 8. 4. The SRI_ACK contains the call forwarding subscription information and the O-CSI subscription information of the called party. and if the called party subscribes to the call forwarding service and the O-CSI service. 13-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The VMSC of the forwarded-to party responses the ACM message to the GMSC. The GMSC responses the ACM message to the VMSC of the calling party. The call is established. The query result is "Routing out the call directly to another office". The GMSC sends an IAM message to the VMSC of the forwarded-to party according to the MSRN number of the forwarded-to party. The GMSC sends an SRI message to the HLR of the forwarded-to party. The SCP triggers the IN service after receiving the IDP message. 9. The GMSC sends the SRI message to the HLR of the called party. the MSOFTX3000 does not trigger the IN service and connects the call to the MSC/SSP which can trigger the IN service normally. 3. Call process 1. Figure 13-5 Routing out the call directly to another office (early forwarding with O-CSI) VMSCa 1. The GMSC queries the IN service control data table. 8.ACM 7.IAM 6. Routing Out the Call Directly to Another Office (Early Forwarding with O-CSI) If the call is an IN call of the MF type. The IN service triggering process completes. 11. The call procedure is as shown in Figure 13-5.IAM GMSC HLR MSC/SSP 2. The SRI_ACK contains the MSRN number of the forwarded-to party. 2. 13.

ACM 10. Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-9 . The GMSC queries the IN service control data table. The GMSC sends the SRI message to the HLR of the called party. The SRI_ACK contains the call forwarding subscription information and the O-CSI subscription information of the called party. Figure 13-6 Ignoring IN service (early forwarding with O-CSI) VMSCa 1. 3. 5. 5. 4. The GMSC sends an IAM message to the MSC/SSP according to the MSC/SSP routing information in the IN service control data table.SRI_ACK(MSRN) 8. The GMSC responses the ACM to the VMSC of the calling party. Ignoring IN Service (Early Forwarding With O-CSI) If the call is an IN call of the MF type. 2.SRI_ACK (early forwarding with O-CSI) 4.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 5.SRI Query the IN service control data table 3.Call forwarding flow 6. The query result is "Ignoring IN service ".ACM 11. The GMSC receives the IAM message from the VMSC of the calling party. the MSOFTX3000 does not trigger the IN service and connects the call as an ordinary call.IAM GMSC HLR SCP VMSCb 2.Call process The call procedure is as follows: 1. The call is established. The MSC/SSP responses the ACM message to the GMSC. 8.IAM 9. and if and if the called party subscribes to the call forwarding service and the O-CSI service. 7. 6.SRI 7. The HLR responses the SRI_ACK message to the GMSC. The call procedure is as shown in Figure 13-6. The GMSC launches call forwarding according to the call forwarding subscription information of the called party.

13. and SCP address. 13-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . the charging of the IN service subscribers is affected. The operator can execute the command MOD GBILLCTRL to modify the integrated control data of the call detail record (CDR) to avoid any possible conflict between the carrier and the subscribers concerning the charging. The SRI_ACK contains the MSRN number of the forwarded-to party. 13. 13. Therefore. 8.4 Service Flow No special service flow.5 Data Configuration 13.5. The carrier requires that the MSOFTX3000 connects the calls as ordinary calls (ignores IN service). The GMSC responses the ACM message to the VMSC of the calling party. When configuring the IN service control data. To solve this problem. 13. 7. the operator needs to configure the IN service control data by using the command ADD INSRVCTRL in the following two cases: The carrier requires that the MSOFTX3000 connect the IN calls to MSC/SSP and that the MSC/SSP triggers the IN service. the operator must be cautious when configuring this data. you can configure different processing modes (triggering IN service. IN service key. 11. 9.3 Data Configuration for UMG8900 The UMG8900 can provide this service without any extra data configuration. and ignoring IN service) according to the IN service triggering type.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description 6. The call is established. You need pay attention that if the operator configures the IN service control data by using the command ADD INSRVCTRL. and if the SCP interconnected with the MSOFTX3000 uses private INAP protocol. See online help for the descriptions of the parameters of related commands. The HLR of the forwarded-to party responses an SRI_ACK to the GMSC.2 Data Configuration for HLR9820 The HLR9820 can provide this service without any extra data configuration. routing out the call directly to another office.5. The GMSC sends an IAM message to the VMSC of the forwarded-to party according to the MSRN number of the forwarded-to party. the MSOFTX3000 fails to trigger the IN service when handling the IN service subscribers (the subscribers subscribe to the IN service in the HLR).5. The GMSC sends an SRI message to the HLR of the forwarded-to party. 10. The VMSC of the forwarded-to party responses the ACM message to the GMSC.1 Data Configuration for MSOFTX3000 If MSOFTX3000 is adopted in the GMSC/SSP networking.

The IN service key is 1. Description Configuring the routing analysis data: Routing selection name: 10 Routing selection source name: 0 Routing name: 0 Signaling priority level: constant Script ADD RTANA: RSN="10". No CDR is generated for the IN call of the called party. The SCP address is 8613977888 and the SCP uses the INAP private protocol. the carrier changes the number of the called party and the call is directly transited to another MSC/SSP which triggers the IN service. The routing selection name of Routing out the call directly to another office is 10. DCT=TYPE1. In this case. Description Configuring the number conversion data: Number conversion name: 10 Number conversion type: insert number to designated location Start conversion location: 0 New number: 123 Script ADD DNC: DCN="10". R=0. Assume that: The number of the called party is added with a prefix 123.4 Example Scenario 1 In an IN call.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 13. The MSOFTX3000 can not trigger the IN service when processing this call. RSSN="0". ISUP=NOCHG. Scripts for Configuration Step 1 Configure the routing analysis data. The routing selection source name 0 has been defined in the call source table. Step 2 Configure the number conversion data. ND=K'123.5. Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-11 . Routing name 0 already exists. assume that: The subscriber data of the called party contains the T-CSI subscription information. DCP=0.

----End Scenario 2 In an IN call. Script Note MOD GBILLCTRL: BCF=AI_MTC-0. 13-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The IN service key is 2. If you execute this command. SK=1. you must configure a new routing selective code and assign the correct service feature. assume that: The subscriber data contains the call forwarding unconditional (CFU) and O-CSI subscription information. CLDNCN="10". SA=K'8613977888. the MSOFTX3000 does not generate a CDR for the IN call of the called party. PT=SR.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description Step 3 Configure the IN service control data. In this case. The SCP address is 8613977888 and the SCP uses the INAP private protocol. RSN="10". No CDR is generated for the IN call of CFU. If the processing is configured as routing out the call directly to another office. Description Modifying the integrated control data of the CDR: Unselect the CDR for IN call of the called party in the CDR control indication. NSP=MOO. The MSOFTX3000 can not trigger the IN service when processing this call. Description Configuring the IN service control data: IN service triggering type: mobile subscriber as the called party IN service key: 1 SCP address: 8613977888 Processing mode: routing out the call directly to another office New routing selection name: 10 New service feature: other office of the mobile network Conversion name of the number of the called party: 10 Script Note ADD INSRVCTRL: ITT=MT. Step 4 Modify the integrated control data of the CDR. the carrier ignores the IN attributes of the call and connects the call as an ordinary call.

MOD GBILLCTRL: BCF=AI_CFW-0. SK=2. The SCP address is 8613977888. Description Script Note Modifying the integrated control data of the CDR: Unselect the CDR for IN call of CFU in the CDR control indication. Description Configuring the IN service control data: IN service triggering type: call forwarding of the mobile subscriber IN service key: 2 SCP address: 8613977888 Processing mode: ignoring IN service Script ADD INSRVCTRL: ITT=MF. If you execute this command. assume that: The subscriber data contains the CFU and O-CSI subscription information.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature Scripts for Data Configuration Step 1 Configure the IN service control data. ----End Scenario 3 In an IN call. Scripts for Data Configuration Step 1 Configure the IN service control data. The MSOFTX3000 can trigger the IN service normally in the SCP. SA=K'8613977888. SA=K'8613977888. Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-13 . PT=IGNR. PT=TRG. Step 2 Modify the integrated control data of the CDR. the MSOFTX3000 does not generate a CDR for IN call of CFU. The IN service key is 3. The carrier triggers the IN service and generates a CDR for the IN call of CFU. Description Configuring the IN service control data: IN service triggering type: CFU of the mobile subscriber IN service key: 3 SCP address: 8613977888 Processing mode: triggering the IN service Script ADD INSRVCTRL: ITT=MF. SK=3.

and if the IN service is triggered in the T-CSI mode. and if the IN service is triggered in the O-CSI mode.13 IN Service Triggering Feature HUAWEI MSOFTX3000 Feature Description Step 2 Modify the integrated control data of the CDR.6 Service Management None. 13. If CDR for IN Called Party is selected. Description Script Note Modifying the integrated control data of the CDR: Select CDR for IN call forwarding. You can determine whether to generate a CDR for the IN calls when configuring the parameter CDR control indication in the command MOD GBILLCTRL: If CDR for IN call forwarding is selected. Therefore. no CDR for IN call forwarding is generated.8 Service Interaction The IN service triggering feature has the following interactions with other services: This IN service triggering feature does not affect the IN service triggering feature of the NCSI. The operator can execute the command MOD GBILLCTRL to modify the integrated control data of the call detail record (CDR) to avoid any possible conflict between the carrier and the subscribers concerning the charging. MOD GBILLCTRL: BCF=AI_CFW-1. 13. If you execute this command. 13-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . ----End 13. no CDR for IN called party is generated. It is kept for later upgrade. If CDR for IN Called Party is not selected. the operator must be cautious when configuring this data. the MSOFTX3000 is restricted to generate a CDR for the IN call of CFU. If CDR for IN call forwarding is not selected.7 Charging and CDR If the operator configures the IN service control data by using the command ADD INSRVCTRL. CDR for IN call forwarding is generated. CDR for IN called party is generated. the charging of the IN service subscribers is affected. The option Mobile subscriber as the calling party of the IN service triggering type in the IN service control data is not in current use.

13.HUAWEI MSOFTX3000 Feature Description 13 IN Service Triggering Feature 13.2 Acronyms and Abbreviations Acronym ACM HLR IAM IDP INAP MSC O-CSI SCP SSP T-CSI Full Name Address Complete Message Home Location Register Initial Address Message Initial Detection Point Intelligent Network Application Protocol Mobile Switching Center Originating CAMEL Subscription Information Service Control Point Service Switching Point Terminating CAMEL Subscription Information Issue 02 (2007-06-10) Huawei Technologies Proprietary 13-15 .9.9 References 13.9.1 Specifications None.

...............................................14-16 14...............4 Service Flows ....................3 Version Support.........14-3 14..14-3 14.............3 Service Benefits ............................3 Data Configuration Examples ................................................................................................................2 Data Configuration on the UMG8900...........14-15 14..........1.....................................................................14-3 14.......................................................................................................1......2................................................................6 Service Management ............................9 Reference ...............................1 Data Configuration on the MSOFTX3000...............................................................2........................................1 Feature Code .................................................2 Function Definition...........14-9 14.......................................................................................................................................................2 System Interior Processing........................................................................................................1 Functions of NEs....................................................................................................5.....14-2 14...................................................................4...........................................................................................................................................14-16 14...........................3 Principle Description........................................3...14-9 14...................................2 License Support .................................................5 Data Configuration................HUAWEI MSOFTX3000 Feature Description Contents Contents 14 MNP Feature ..................................14-5 14......1 Protocols and Specifications .........................................................................................14-2 14.......................................................................4...........14-6 14............................................................................................................................................................9...........1 Related Network Elements..........2 Availability ............1................................................1 QoR Mode..........................................................5....................................................................................2 OR Mode.................................................................................................................................14-3 14.......................7 Charging and CDR ..............................................1 Feature Description ...............................................................2......14-3 14........................................................5...................3..........................................................14-7 14......................................................................................8 Service Interaction ................14-5 14..............................9..............................................................................................................................................14-3 14.................................................14-2 14.14-9 14............................3 AcQ Mode...........................................4..................................................................................14-16 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .........................................................14-2 14....................................................................................................................................14-3 14.....14-1 14..........14-15 14...............................................2 Acronyms and Abbreviations .........................................................14-16 14.....................14-9 14.

................................................................................................................................................14-6 Figure 14-4 MNP service flow in OR mode................................................14-5 Figure 14-3 External network subscriber calls a subscriber ported in the Local Network but does not exist in the local network...........................................................................................................................14-8 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ..............14-8 Figure 14-6 Local network subscriber calls a ported out local network subscriber based on signaling ...........14-7 Figure 14-5 Local network subscriber calls a ported out local network subscriber based on the IN.............................................14-4 Figure 14-2 External network subscriber calls a ported out local network subscriber ...........................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 14-1 Networking of MNP service ........

............HUAWEI MSOFTX3000 Feature Description Tables Tables Table 14-1 Related NEs of MNP feature ........................................................................................................14-3 Table 14-2 Product versions that support the MNP feature .............................................................14-3 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ........

and the benefits that carriers and mobile subscribers can obtain from this feature.8 Service Interaction 14.6 Service Management 14. The network elements (NEs) that are required for the feature. The relationships and restrictions between this feature and other services or features.1 Feature Description Describes 14. and networking requirements. and the acronyms and abbreviations of this chapter.3 Principle Description 14.7 Charging and 14.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature 14 About This Chapter The following table lists the contents of this chapter. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The charging and the generation of CDRs when the network provides this feature. The functions of the NEs.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-1 .5 Data Configuration 14.4 Service Flows 14.2 Availability MNP Feature The function code. and the version requirements of the NEs. Section 14. function definition of this feature. The protocols and specifications that this feature must comply with. 14. The data configurations that are required on the MSOFTX3000 and the IMG8900. whether Licenses are required. The service flow of the network when providing this feature.

All the services of the subscriber are provided by the new network. They are not affected by the original network. subscribers cannot enjoy the services.1. Mobile subscribers Based on the changes of locations. If certain services supported by the original network are not supported by the new network. In one network. the subscriber can register the same number in area B. Subscribers can subscribe networks of one carrier in different areas and remain the original number. such as the additional call setup delay.1. One MSISDN can be ported for multiple times and can be ported back and forth in multiple networks. This number belongs to the number segment of area A. For mature carriers. the MNP service brings additional management charges and increases operation revenue. 14-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Independent service: It does not conflict with other mobile services provided by the system. The MNP service provides the following functions: No need to change the MSISDN: Subscribers need not to change their MSISDNs due to the change of carriers or networks. but there are differences in service qualities. After moving to place B. a subscriber registers a number in area A.1 Feature Code Feature Name MNP Feature Feature Code WMFD-042500 14. The new network also assigns a new International Mobile Subscriber Identity (IMSI) to the MNP subscriber. subscribers can choose different networks or more suitable carriers without changing their numbers.1 Feature Description 14. Independent subscription service: The original network has no impact upon the current services of subscribers.3 Service Benefits Beneficiary Carriers Benefit Description For new carriers. Ported many times: There can be numbers ported both in and out in one network.14 MNP Feature HUAWEI MSOFTX3000 Feature Description 14.1. For example.2 Function Definition The Mobile Number Portability (MNP) allows Universal Mobile Telecommunications System (UMTS) or GSM mobile subscribers to change the subscription networks within a country. the MNP feature attracts new subscribers and enhances competition capability. 14. and to preserve the original MSISDNs at the same time. MNP subscribers and non-MNP subscribes enjoy service functions of no difference.

The MNP services are available only when the MSOFTX3000 License is obtained.2.1 Functions of NEs The HLR stores the subscription information.3.2. The MSC server provides services to subscribers based on their subscription information.2 System Interior Processing Figure 14-1 shows the typical networking of the MNP service.2 Availability 14. Table 14-2 Product versions that support the MNP feature Product MSC Server MGW MSOFTX3000 UMG8900 Version V100R002 and later versions V200R002 and later versions 14. 14. 14. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-3 .3 Principle Description 14.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature 14. home area and home network information of subscribers.2.3 Version Support Table 14-2 lists the product versions that support the MNP feature. 14.2 License Support The MNP feature is an optional feature of Huawei wireless core network.3. Table 14-1 Related NEs of MNP feature UE/M S √ NodeB/ BTS RNC/ BSC MSC Server √ MGW NPDB √ SCP √ VLR √ HLR √ "√" indicates the related NEs.1 Related Network Elements The realization of the MNP feature requires the cooperation of the network elements (NEs) listed in Table 14-1.

The MSC queries the MNP Service Processing Table to determine the subsequent processing type: IN based original call query. and use the SPS as the translation point. while the other is based on signaling relay. The IN based original call query mode is not usually used. The MNP feature requires that the network addresses in the "Route on GT" mode. One is based on the IN. the SPS serves as the MNP-Signaling Relay Function (SRF) and Number Portability Database (NPDB).066 defines two modes to realize the MNP. It is used for certain special requirements only. The MSOFTX3000 supports the following MNP modes: Query on Release (QoR) mode Onward Routing (OR) mode All Call Query (AcQ) mode 14-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The 3G TS 23.14 MNP Feature HUAWEI MSOFTX3000 Feature Description Figure 14-1 Networking of MNP service PLMN Other PLMN HLR SMSC Foreign NPDB SPS SPS VMSC GMSC Foreign NPDB: NP database of external network PLMN: Public Land Mobile Network GMSC: Gateway Mobile Switch Center VMSC: Visited Mobile Switch Center SPS: Signaling Service Processing System HLR: Home Location Register SMSC: Short Message Service Center In the networking. Release. or No processing. It is before the HLR in service flows and often configured in pairs.

RNx refers to RN of external network. When receiving the SRIack. The called number does not carry an RN prefix. If the cause value is 14.4. If there is no special note in this article.1 QoR Mode RN is the route number. Based on the result. the VMSC re-routes the call to the NPDB to obtain the RNx. the REL message carries a disconnect cause value of 1. the GMSC processes as follows: If the returned MSRN is "Foreign RNx + MSISDN" or "NonNP + MSISDN". and C0102. the GMSC normally connects the call. Figure 14-2 External network subscriber calls a ported out local network subscriber VMSC GMSC STP/NPDB HLR IAM (MSISDN) SRI (MSISDN) SRIack (RNx+MSISDN) REL (release cause 14) 1. the REL message carries a disconnect cause value of 14. The message carries a called number with the number segment of the local network. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-5 . Based on the result of querying related table.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature 14. RNP4 refers to the RN of P4. the system generates an alarm. Every carrier is assigned with one RN.4 Service Flows 14. If the prefix is NonNP. The VMSC does failure processing to the REL message returned by the GMSC. The MNP service in the QoR mode is used when the GMSC calls the following numbers: Numbers ported from local network to external network Numbers ported from external network to local network The GMSC delivers the SRI to the NPDB. External Network Subscriber Calls a Ported Out Local Network Subscriber Figure 14-2 shows the flow of an external network subscriber calls a ported out local network subscriber. In the latter case.) Otherwise. The GMSC receives an IAM message sent by the VMSC. the GMSC disconnects the call. and NonNP means that no number is ported. the GMSC queries the MNP Service Processing Table. (If the prefix is RN. the NPDB determines whether to deliver the SRI to the HLR or return an SRlack message to the GMSC. such as C0101.

the NPDB returns an SRIack (NonNP + MSISDN or RNx + MSISDN) to the GMSC. 14. If a called number ports to external network. After querying table. In the trial bill. the called number is the MSISDN. The call termination cause value is 14. In the trial bill. The GMSC sends a REL message to the VMSC. 3. the 14-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . indicating that the called number is not allocated. 4. indicating that the called number is ported out. The call termination cause value of 1. 4.4.14 MNP Feature HUAWEI MSOFTX3000 Feature Description 2. Figure 14-3 External network subscriber calls a subscriber ported in the Local Network but does not exist in the local network VMSC GMSC STP/NPDB HLR IAM (RNP4+MSISDN) SRI (MSISDN) SRIack REL (release cause 1) 1. The VMSC disconnects the call. The caller thinks that the callee ported in the local network. indicating that the called number is ported out. External Network Subscriber Calls a Subscriber Who Ported In Local Network But Does Not Exist in the Local Network An external network subscriber calls a local network subscriber. 3. The VMSC sends an IAM message to the GMSC. the NPDB returns an SRIack (RNx + MSISDN) to the GMSC.2 OR Mode The MNP service in the OR mode is used when the GMSC calls the number segment that may port from local network to external network. The call termination cause value is 14. that is. The GMSC sends an SRI to the NPDB. NonNP + MSISDN returned by the STP means that this MSISDN is a non-NP subscriber. The VMSC disconnects the call. the called number is RNP4 + MSISDN. After querying related table. The GMSC sends an SRI to the NPDB. 2. The called number carries the RN prefix of the local network. The GMSC sends an REL message to the VMSC. The call termination cause value is 1. but the called does not exist in the local network. RNP4. indicating that the called number is not allocated. Figure 14-3 shows the flow.

Figure 14-4 shows the MNP service flow in the OR mode. Based on the result. such as the GMSCb. 2. In the GWI. 3. the MSC sends the IAM out of the office or pages the callee. the called number is the MSISDN.4. the called number in the GWO is MSISDN.3 AcQ Mode The MNP service in the AcQ mode is used when the called party is a local network subscriber and may port to external network. The IAM message carries the information of the called number that belongs to the local network number segment. Local Network Subscriber Calls a Ported Out Local Network Subscriber Based on IN Figure 14-5 shows the flow of a local network subscriber calls a ported out local network subscriber based on the IN. the GSMC queries the MNP Service Processing Table and selects a processing type. The PSTN sends an IAM message to the GMSCa. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-7 . In this case. Figure 14-4 MNP service flow in OR mode PSTN GMSCa STP/NPDB HLR GMSCb IAM (MSISDN) SRI (MSISDN) SRIack (RNx+MSISDN) IAM (RNx+MSISDN) 1. The MSC routes the call to the NPDB or reports to the NPDB through an IDP message.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature NPDB returns an SRlack (RN + MSISDN). The GMSCa sends an SRI to the NPDB. When receiving the SRlack. For a GMSC. The called number in the GWO is RNx + MSISDN. After querying table. the subscriber is not charged. the NPDB returns an SRIack (RNx + MSISDN) to the GMSCa. the called number in the GWO is RNx + MSISDN. (For a GV integrated office. The GMSCa routes the call to the correct network. 4.) 14.

Figure 14-6 Local network subscriber calls a ported out local network subscriber based on signaling VMSC STP/NPDB HLR GMSC SRI (MSISDN) SRIack (RNx+MSISDN) IAM (RNx+MSISDN) 14-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) .14 MNP Feature HUAWEI MSOFTX3000 Feature Description Figure 14-5 Local network subscriber calls a ported out local network subscriber based on the IN VMSC STP/NPDB SCP HLR GMSC IDP (DP2. 4. and reports an IDP message to the NPDB. The NPDB transparently transfers the IDP message to the SCP. the called number is the MSISDN. The local network subscriber initiates a call. 2. 3. In the MOC. triggers the IN. IN bills are generated.Cdpa=MSISDN) IDP (DP2. Local Network Subscriber Calls a Ported Out Local Network Subscriber Based on Signaling Figure 14-6 shows the flow of a local network subscriber calls a ported out local network subscriber based on signaling. The translatedNumber is RNx + MSISDN. The VMSC routes the call to the correct network. The SCP returns the CONNECT (RNx + MSISDN) message to the VMSC.Cdpa=MSISDN) Connect (Cdpa=RNx+MSISDN) IAM (RNx+MSISDN) 1.

3.1 Data Configuration on the MSOFTX3000 Step 1 Run ADD MNP to add records in the MNP Service Table.5.) Step 6 Run ADD CLDPREANA to add called number pre-analysis data. 14. Configuration Scripts The data configuration of the local office is as follows: Step 1 Add the GT translation to the NPDB. Step 5 Run ADD SCPPARA to add SCP parameters. Step 2 Run ADD SCCPGT to add GT translation data to the NPDB. Step 3 Run ADD IMSIGT to add the global translation codes of the IMSI. The subscriber initiates a call. The VMSC routes the call to the correct network.2 Data Configuration on the UMG8900 None.5 Data Configuration 14. Step 9 Run ADD DNC to add number change data. ----End 14. The translatedNumber is RNx + MSISDN.5. The NPDB returns an SRlack with the RNx prefix and the MSISDN. 2. The GMSC queries the NPDB. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-9 .HUAWEI MSOFTX3000 Feature Description 14 MNP Feature 1. the NPDB returns an SRIack (RNx + MSISDN) to the VMSC. In the MOC. 14. The VMSC sends an SRI to the NPDB. the called number is the MSISDN. (This step is required only when the MNP processing type is IN-based MO query.5. Step 7 Run ADD AIDNUMPRO to add auxiliary number change data. After querying table. Step 8 Run ADD CFPRO to add failure processing data.3 Data Configuration Examples Case 1 QoR mode: An external network subscriber calls a ported out local network subscriber. Step 4 Run ADD CNACLD to add called number analysis data. The calling office routes the call to a third-party network based on the RNx prefix.

Step 2 Add the global translation code information of the IMSI. Set Processing type to No processing to prevent adding "00" when adjusting the called number. SPC="111111". ICLDTYPE=MS. Script ----End The data configuration of the originating office: Step 1 Configure the Called NO Analysis Table. Disconnect cause code to 142. MINDNLEN=5. Description Script Configure the Called Number Pre-analysis Table. MAXL=20. RSN="5". Description Script Configure the Called NO Analysis Table. MNP processing type to External network NP prefix. ADD CNACLD: P=9. Description Script Add the global translation code information of the IMSI. Step 3 Configure the Called Number Pre-analysis Table. CDADDR=ALL. MAXDNLEN=20. Script ADD SCCPGT: GTN="10". MINL=3. MNPPFT=OTHER. ICLDTYPE=PS. CSA=MLCT. Note: The SCCPDSP and SCCP subsystems require independent configuration. CS=ALL.14 MNP Feature HUAWEI MSOFTX3000 Feature Description Description Add the GT translation to the NPDB to translate corresponding number segments to the NPDB. ADD IMSIGT: MCCMNC=K'460077552000395. PFX=K'C0101. MAXL=32. and Alarm flag to No. 14-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . ADDR=K'48139075203. Step 4 Configure the MNP Service Table. Called prefix to C0101. CRP=ALL. Description Configure the MNP Service Table. Set Call source to 0. Maximum number length to 20. RESULTT=STP1. MNNAME="MNP TEST". PFX=K'C0101. ADD CNACLD: PFX=K'139075203. FCC=CV142. ADD INMNP: CLDPFX=K'C0101. ALMF=NO. PT=DONTPROC. MINCLDLEN=6. Minimum number length to 5. ADD CLDPREANA: CSCNAME=65534. MNPPRT=REL. MINL=5. CCNDC=K'48139075203. MNP processing type to Disconnect. Call originator to MAP non-forwarding.

PT=CPA. Step 6 Configure the Call Failure Processing Table. DCT=TYPE1. Step 5 Configure the Number Change Table. ND=K'123. ADD CFPRO: FCC=CV142. Step 7 Configure the Auxiliary Number Change Table. DCN="1". RESULTT=STP1. Step 4 Configure the Called Number Pre-analysis Table. Note: The SCCPDSP and SCCP subsystems require independent configuration. Script ADD SCCPGT: GTN=10. ADDR=K'48139075203. CDADDR=ALL. PT=DONTPROC.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature Step 2 Add the GT translation to the NPDB. MINCLDLEN=6. ADD CLDPREANA: CSCNAME=65534. FSC=0. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-11 . Set Failure cause code to 142 for failure processing. RUT=CAT10. ADD IMSIGT: MCCMNC=K'460077552000395. Description Script Configure the Number Change Table. PFX=K'C0101. ADD DNC: DCN="1". CRP=ALL. CS=ALL. Set the Number Change Table to add prefix to the called number. Description Script Configure the Called Number Pre-analysis Table. Step 3 Add the global translation code information of the IMSI. SPC="111111". MNNAME="MNP test". Description Script Configure the Call Failure Processing Table. Description Add the GT translation to the NPDB to translate corresponding number segments to the NPDB. Description Script Add the global translation code information of the IMSI. CCNDC=K'48139075203.

PFX=K'123. CS=ALL. ----End Case 2 QoR mode: An external network subscriber calls a local network subscriber. ADD IMSIGT: MCCMNC=K'460077552000395.14 MNP Feature HUAWEI MSOFTX3000 Feature Description Description Configure the Auxiliary Number Change Table. CDX=1. The GMSC queries the NPDB. SPC="111111". but the callee does not exist in the local network. PT=DONTPROC. 14-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Configuration Scripts Step 1 Add the GT translation to the NPDB. Description Add the GT translation to the NPDB. MINCLDLEN=6. CRP=ALL. NUMTY=TY4. RESULTT=STP1. ADD CLDPREANA: CSCNAME="65534". Step 2 Add the global translation code information of the IMSI. CCNDC=K'48139075203. Description Script Configure the Called Number Pre-analysis Table. P=9. ADDR=K'48139075203. Script ADD SCCPGT: GTN="10". Step 3 Configure the Called Number Pre-analysis Table. Description Script Add the global translation code information of the IMSI. CDADDR=ALL. Script ADD AIDNUMPRO: CSCNAME="0". Note: The SCCPDSP and SCCP subsystems require independent configuration. PFX=K'C0101. The NPDB returns an SRlack with the NonNP prefix and the MSISDN. The GMSC sends a disconnecting message to the originating office. Set Processing type to No processing to prevent adding "00" when adjusting the called number. MNNAME="MNP test". Note: Configure the Number Change Table to delete the prefix "123". The caller thinks that the callee ported in the local network.

When receiving the SRlack. Set Processing type to No processing to prevent adding "00" when adjusting the called number. CS=ALL. the GMSC sends an SRI to the NPDB. Step 3 Configure the Called Number Pre-analysis Table. and Alarm flag to No. Note: The SCCPDSP and SCCP subsystems require independent configuration. ADDR=K'48139075203. the GMSC queries the MNP Service Processing Table to select a processing type. MNPPRT=REL. Script ADD SCCPGT: GTN="10".HUAWEI MSOFTX3000 Feature Description 14 MNP Feature Step 4 Configure the MNP Service Table. Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-13 . If the called number ports out of the local network. Called prefix to C0101. ADD IMSIGT: MCCMNC=K'460077552000395. SPC="111111". MINDNLEN=5. Maximum number length to 20. Description Configure the MNP Service Table. Description Add the GT translation to the NPDB. MNPPFT=LOC. ALMF=YES. Call originator to Wildcard. Script ----End Case 3 OR mode: For calls that the callee is a local subscriber and may port to a number segment of external network. Configuration Scripts Step 1 Add the GT translation to the NPDB. CDADDR=ALL. Minimum number length to 5. Description Script Add the global translation code information of the IMSI. PFX=K'C0101. FCC=CV142. Description Script Configure the Called Number Pre-analysis Table. Step 2 Add the global translation code information of the IMSI. ADD CLDPREANA: CSCNAME="65534". CCNDC=K'48139075203. MNNAME="MNP test". PT=DONTPROC. RESULTT=STP1. MNP processing type to Disconnect. MNP processing type to Local network NP prefix. Set Call source to 0. the NPDB returns an SRlack (RNx + MSISDN). CRP=ALL. MAXDNLEN=20. Disconnect cause code to 142. ADD INMNP: CLDPFX=K'C0101. MINCLDLEN=6.

The originating office queries the NPDB. The NPDB returns an SRlack with the RNx and the MSISDN. Description Add the GT translation to the NPDB. Call originator to Wildcard. RESULTT=STP1. Set Processing type to No processing to prevent adding "00" when adjusting the called number. MNPPFT=LOC. Description Configure the MNP Service Table. MNP processing type to Local network NP prefix. CDADDR=ALL. Description Script Add the global translation code information of the IMSI. The originating office routes to a third-party network based on the RNx. Configuration Scripts Step 1 Add the GT translation to the NPDB. MNNAME="MNP test". MNPPRT=DONTPROC. and MNP processing type to No processing. Minimum number length to 5. PT=DONTPROC. MINDNLEN=5. CCNDC=K'48139075203. Maximum number length to 20. Step 2 Add the global translation code information of the IMSI. PFX=K'C0101. Description Script Configure the Called Number Pre-analysis Table. Note: The SCCPDSP and SCCP subsystems require independent configuration. CS=ALL. Script ADD SCCPGT: GTN="10". Called prefix to C0101. SPC="111111". Step 3 Configure the Called Number Pre-analysis Table. MAXDNLEN=20. 14-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . CRP=ALL. MINCLDLEN=6. Script ----End Case 4 AcQ mode: A local network subscriber calls a ported out local network subscriber based on signaling. ADDR=K'48139075203. Set Call source to 0. ADD IMSIGT: MCCMNC=K'460077552000395.14 MNP Feature HUAWEI MSOFTX3000 Feature Description Step 4 Configure the MNP Service Table. ADD CLDPREANA: CSCNAME="65534". ADD INMNP: CLDPFX=K'C0101.

ADD INMNP: CLDPFX=K'C0101. MAXDNLEN=20. ICLDTYPE=PS. bit 1 is invalid. = 1: Fill the numbers the subscribers dial. ADD CNACLD: P=9. = 0: Fill the numbers after adjustment. It can also be controlled by bit 2 of the software parameter P1300: Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-15 . Minimum number length to 5. = 0: Overseas requirement = 1: Domestic requirement Default value: 1 Bit 1: Controls the format of called numbers in the bill. MNPPRT=DONTPROC.7 Charging and CDR The charging and bill generating principles of the MNP feature are as follows: If IN services are triggered. 14. Description Script Configure the Called NO Analysis Table. IN bills are generated.HUAWEI MSOFTX3000 Feature Description 14 MNP Feature Step 4 Configure the Called NO Analysis Table. Maximum number length to 20. MAXL=32. If the roaming number brought back by the NPDB is (RN + MSISDN). CSA=MLCT. MNPPFT=LOC. PFX=K'C0101. MINDNLEN=5. Default value: 1 Bit 1 is valid only when bit 4 is set to 0. Step 5 Configure the MNP Service Table. MNP processing type to Local network NP prefix. Called prefix to C0101. When bit 4 is set to 1. Call originator to Wildcard. RSN="5". the translatedNumber in the bill is RN + MSISDN. and MNP processing type to No processing. Bit 4 and bit 1 of the software parameter P129 control the filling of the called number in the bill: Bit 4: Controls the filling of the numbers in the bills of overseas version and domestic version.6 Service Management None. MINL=5. Set Call source to 0. Script ----End 14. Description Configure the MNP Service Table.

The GWO bill is generated when subscriber A dials subscriber B and triggers the IN flow CONNECT to subscriber C (in other office): = 0: Fill the number of subscriber C.066 Design specifications of the ETSI interception 14.9.2 Acronyms and Abbreviations Acronym/Abbreviation 3GPP AcQ CdPA ETSI MNP MOC MSRN MTC NPDB OR QoR RN SCCP Full Name 3rd Generation Partnership Project All Call Query Called Party Address European Telecommunications Standards Institute Mobile Number Portability Mobile Originated Call Mobile Station Roaming Number Mobile Terminated Call Number Portability Database Onward Routing Query on Release Routing Number Signaling Connection Control Part 14-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) .8 Service Interaction The MNP feature has service interaction with the ETSI interception. For details. = 1: Fill the number of subscriber B. Default value: 1 You should configure a piece of data in the Home PLMN Roaming Prefix Table to limit the generation of roaming bills. refer to the design specifications of the ETSI interception.1 Protocols and Specifications The references of the MNP feature are as follows: 3GPP TS 23.9. The MSRN prefix is the RN number. 14. 14.14 MNP Feature HUAWEI MSOFTX3000 Feature Description Bit 2: Defines the filling principles of the called numbers in the GWO bill.9 Reference 14.

HUAWEI MSOFTX3000 Feature Description 14 MNP Feature Acronym/Abbreviation SCP SPC Full Name Service Control Point Signaling Point Code Issue 02 (2007-06-10) Huawei Technologies Proprietary 14-17 .

.........5............................................................15-2 15......15-3 15........................15-2 15......................................................................9 Service Interaction ................................................................................................................................................7 Service Management ......................................15-3 15.................................................................................................................................15-3 15.....................................................................................................................................................15-10 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .................................................................................4.............................................................................................................................3.........15-2 15.......................................................................1 To Carriers..............................15-7 15.............................................................................15-2 15...............2 Requirements for Software .....6....15-10 15.................................................................................15-2 15.............1 Service Description .............................................................................15-3 15................6 Data Configuration............15-1 15......4...................3 Requirements for Hardware ..............................................................................................................................................................15-9 15................................................................8 Charging and CDR ...............................................................................2 Working Principle......................................4................................................................................................................3.15-7 15..3 Benefits ....2 To Mobile Subscribers ..............................................................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 15 IP Fax Feature........................................................4 Availability ....5 Service Flow................5...................................................................................2 Data Configuration Example.....................................................................................................15-2 15...........................................2 Processing Flow .....................................15-2 15.........................1 Classification of Call Model ...................1 Configuring Data at the MSOFTX3000 Side..........................................................15-3 15...........................................1 Application...........15-10 15.....................................6...............................

....15-8 Table 15-5 Value options of 2198 redundancy CODEC type .........................................................................................................................................................................................................................................................15-8 Table 15-3 Value options of 2198 UP Mode..........................................................15-8 Table 15-4 Value options of 2198 redundancy level................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 15-1 Value options of Support FAX detection ..............................15-9 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .................................................................................................15-8 Table 15-2 Value options of Support 2198 redundancy ...15-9 Table 15-6 Value options of BICC support red..............................................................................

The data configuration that is required at the MSOFTX3000 side. The principle of the implementation of this feature.8 Charging and CDR 15. The charging and the generation of CDRs when the network provides this feature. Section 15. The application and requirements of this feature.2 Working Principle 15. The operations that the carrier and subscribers must perform for the implementation of this feature.5 Service Flow 15. The benefits to the carrier and mobile subscribers when this service is used.9 Service Interaction Describes IP Fax Feature The function code and definition of this feature.HUAWEI MSOFTX3000 Feature Description 15 IP Fax Feature 15 About This Chapter The following table lists the contents of this chapter.3 Benefits 15.6 Data Configuration 15.7 Service Management 15. The service flow of the network when providing this feature.1 Service Description 15. The relationships and restrictions between this feature and other services or features. Issue 02 (2007-06-10) Huawei Technologies Proprietary 15-1 .4 Availability 15.

the MSC server determines whether to notify the MGW to start fax event detection after a call is initiated based on data configuration. 15-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Transmission supporting the data stream redundancy is a type of enhanced service. The TS61 service is applicable to TMSC only. because the quality of data transmission determines that of fax.3. The TS62 service is applicable to visited MSC (VMSC). 15.15 IP Fax Feature HUAWEI MSOFTX3000 Feature Description 15.3 Benefits 15. 15. the TrFO function must be enabled.1 Service Description IP fax is the fax service over IP. The limitations of the IP fax service is as follows: The VMSC cannot trigger the TS61 service that contains 2198 redundancy data. Data transmission plays an important role in the fax process. gateway MSC (GMSC). the MSC server determines whether to send 2198 redundancy parameter of the data service to the MGW based on data configuration.2 Working Principle During a call. and tandem MSC (TMSC). This service can improve the data transmission quality. The MSC server sends indication of modifying codec property to the MGW based on reported detection events.4 Availability 15. thus to support data redundancy.2 To Mobile Subscribers Mobile subscribers can enjoy the high-quality fax service. The VMSC does not support fax detection. The data stream redundancy is a solution to the data packet loss during transmission. 15. The modification of 2198 redundancy configuration is not allowed during data service calls.4.1 To Carriers The IP fax feature increases the quality of the fax data transmission and enhances the competitive edge of carriers.3. In addition. To implement 2198 redundancy transmission for inter-office BICC fax. and reduce or avoid the service termination caused by bad data transmission quality. The MGW reports fax tone detection event and fax status detection event. 15.1 Application The MSOFTX3000 V100R005 provides the IP fax service.

VMSC. the gateway reports the fax event. sends the CODEC modification request to the local-end gateway to modify the terminal point.HUAWEI MSOFTX3000 Feature Description 15 IP Fax Feature All the gateways connected with an MSC must support or not support 2198 redundancy at the same time.5.5 Service Flow 15. and meanwhile sends the modification request to the peer end. After the fax ends.5.2 Requirements for Software None. Issue 02 (2007-06-10) Huawei Technologies Proprietary 15-3 . 15. it also needs to send the intermediate bearer request to the gateway. 15.2 Processing Flow TS61 and TS62 Call Processing Flows on the TMSC when the ISUP/TUP/BICC Signaling is Used ISUP/TUP–ISUP/TUP When a call is initiated. the gateway reports the fax complete event and the local end sends the open EC operation request to the gateway.3 Requirements for Hardware None. the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request. or TMSC 15.1 Classification of Call Model TS61 fax processing on the TMSC TS62 fax processing on the GMSC. When a fax call is initiated. The distributed interworking function (IWF) is not supported. 15. If the local end is the outgoing side.4.4.

Return successful 1T modification response. 4. the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request. 3. ISUP/TUP–BICC When a call is initiated. After the fax ends. The BICC uses the CODEC re-negotiation flow to modify the IP point. Send the 1T modification request. 3. and meanwhile sends the modification request to the peer end. Return successful 1T modification response. sends the CODEC modification request to the local-end gateway to modify the terminal point. Send the 1T modification request. the gateway reports the fax event. MSOFTX3000 (1) (2) (3) (4) IP Incoming side Outgoing side 1. Report the fax detection event. 2. 15-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Notify the peer end to send the CODEC modification request. Notify the peer end to send the CODEC modification request. the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request. 2. BICC–ISUP/TUP When a call is initiated. the gateway reports the fax complete event and the local end sends the open EC operation request to the gateway.15 IP Fax Feature HUAWEI MSOFTX3000 Feature Description MSOFTX3000 (1) (2) (3) (4) IP Incoming side Outgoing side 1. 4. When a fax call is initiated. Report the fax detection event.

sends the CODEC modification request to the local-end gateway to modify the terminal point. the gateway reports the fax event. Notify the peer end to send the CODEC modification request. After the successful modification. the peer end sends the CODEC modification request to the other office. BICC–BICC The MSOFTX3000 receives the CODEC modification request from another MSC (calling party/called party). This feature does not involve the processing of this part. Return successful 1T modification response. Return successful 2T modification response. Send the 1T modification request. Report the fax detection event. "Send the 2T modification request" refers to the intermediate bearer modification request. After the fax ends. and meanwhile sends the modification request to the peer end.HUAWEI MSOFTX3000 Feature Description 15 IP Fax Feature When a fax call is initiated. The BICC uses the CODEC re-negotiation flow to modify the IP point. For the case of switching the fax to the voice call. the gateway reports the fax complete event and the local end sends the open EC operation request to the gateway. MSOFTX3000 (6) (1) (2) (3) (4) (5) Incoming side IP Outgoing side 1. Issue 02 (2007-06-10) Huawei Technologies Proprietary 15-5 . observe the original processing flow. 4. 2. 5. The MSOFTX3000 sends the CODEC modification request to the gateway and meanwhile notifies the peer end to send the CODEC modification request. 3. Send the 2T modification request. 6. "Send the 1T modification request" refers to the local-end terminal point modification request.

5.15 IP Fax Feature HUAWEI MSOFTX3000 Feature Description (1) (6) MSOFTX3000 (2) (3) (4) (5) Incoming side IP Outgoing side 1. Modification request sent by other office Intra-TMSC Cross-Gateway (Over IP) TS61 and TS62 Call Processing Flow The TMSC determines that the current service is a data service. Return successful modification response. the local office judges whether it supports the 2198 redundancy capability and records the result. 6. which carries the redundancy parameter. the MSOFTX3000 sends the CODEC modification request to the gateway. PB response Inter-Office BICC (Over IP) TS61 and TS62 Call Processing Flow If the local office supports the 2198 redundancy in an outgoing BICC call. If the message carrying the 2198 redundancy CODEC is received in an incoming BICC call. 15-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . PB with redundancy parameter 3. PB response 4. 2. Modification request sent by other office 3. PB with redundancy parameter 2. Send the CODED modification request 4. Send the CODED modification request. MSOFTX3000 (1) (2) (3) (4) Incoming side IP Outgoing side 1. Return successful modification response. After the negotiation is completed. The TMSC sends the PREPARE BEARER REQ. the local office negotiates with the peer office.

PB with redundancy parameter 3.6. The VMSC sends the PREPARE BEARER REQ. Table 15-1 lists the value options of this parameter. 3. PB response 4. PB response 15. Return the modification request. Send the modification request. 4. MSOFTX3000 (1) (2) (3) (4) Incoming side IP Outgoing side 1.6 Data Configuration 15. Send the modification request.HUAWEI MSOFTX3000 Feature Description 15 IP Fax Feature MSOFTX3000 BICC MSOFTX3000 (1) (2) (3) (4) MGW 1. Return the modification request. PB with redundancy parameter 2. Intra-VMSC Cross-Gateway (Over IP) TS62 Call Processing Flow The VMSC determines that the current service is a data service. MGW 2. which carries the redundancy parameter. Issue 02 (2007-06-10) Huawei Technologies Proprietary 15-7 .1 Configuring Data at the MSOFTX3000 Side Use the parameter Support FAX detection in the Local Office Information table to control whether the local office supports fax detection.

(default value) The local office does not support the fax detection. Use the parameter Support 2198 redundancy in the Local Office Information table to control whether the local office supports 2198 data redundancy. (default value) The support mode is adopted for the 2198 UP mode of the local office. Table 15-2 lists the value options of this parameter. Table 15-2 Value options of Support 2198 redundancy Value Yes No Meaning The local office supports the 2198 data redundancy. Use the parameter 2198 redundancy level in the Local Office Information table to configure 2198 data redundancy.15 IP Fax Feature HUAWEI MSOFTX3000 Feature Description Table 15-1 Value options of Support FAX detection Value Yes No Meaning The local office supports the fax detection. The 2198 redundancy level of data service is uniformly defined in the whole office. Use the parameter 2198 redundancy CODEC type in the Local Office Information table to configure 2198 data service redundancy. (default value) Use the parameter 2198 UP Mode in the Local Office Information table to configure 2198 data redundancy. Table 15-4 Value options of 2198 redundancy level Value 1 2 Meaning The 2198 redundancy level of data service is level 1. Table 15-5 lists the value options of this parameter. Table 15-3 lists the value options of this parameter. Table 15-4 lists the value options of this parameter. (default value) The 2198 redundancy level of data service is level 1. The local office does not support the 2198 data redundancy. 15-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 15-3 Value options of 2198 UP Mode Value Transparent Mode Support Mode Meaning The transparent mode is adopted for the 2198 UP mode of the local office.

6. these parameters are not displayed in the parameter list. 2198 redundancy level. Parameters 2198 UP Mode. Set bit14 of software parameter 233. when Support 2198 redundancy is set to No. Issue 02 (2007-06-10) Huawei Technologies Proprietary 15-9 . P233 (H248 software parameter 2) It controls whether to forcibly change the UP mode to the transparent mode when the redundancy is sent.2 Data Configuration Example Scenario Description The following lists a scenario description. Thus. and 2198 redundancy payload type value are attributes of 2198 redundancy.HUAWEI MSOFTX3000 Feature Description 15 IP Fax Feature Table 15-5 Value options of 2198 redundancy CODEC type Value G.711a Meaning The codec used for 2198 redundancy of data services is G.711u G. The value range of this parameter is 96–127.711u. Configure the local office information so that the local office supports the fax detection and 2198 data redundancy. (default value) Use the parameter 2198 redundancy payload type value in the Local Office Information table to configure 2198 data redundancy. Configure the office direction table so that redundancy is supported. (default value) The office direction does not support the redundancy. 2198 redundancy CODEC type. = 1: The UP mode is forcibly changed to the transparent mode when the redundancy is sent. The codec used for 2198 redundancy of data services is G. Table 15-6 Value options of BICC support red Value Yes No Meaning The office direction supports the redundancy. The default value is 97. 15. Use the parameter BICC support red in the Office Direction table to configure whether to the office direction supports the redundancy parameters.711u. Table 15-6 lists the value options of this parameter. Bit 14: − − = 0: The UP mode is not forcibly changed to the transparent mode when the redundancy is sent.

IN2S=SP24. IN2=NO. BITVAL=1. SN3=NAT. NN2S=SP14. SPF=YES. NPC="2A1101". ADD OFC: ON="VMSC". NN=YES. 15.15 IP Fax Feature HUAWEI MSOFTX3000 Feature Description Configuration Script SET OFI: OFN="VMSC". REDLEVEL=L1.8 Charging and CDR None. 15-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) .7 Service Management No special management of the service is required. LOT=LOCMSC.9 Service Interaction None. SN4=NATB. NNS=SP24. SN2=NATB. BIT=14. REDCODEC=G711a. IN=NO. REDPT=97. OOFFICT=NATT. SPFAXDT=YES. 15. DOL=SAME. UPMODE=TRANS. IFSUPPORTRED=YES. MOD MSFP: ID=P233. SPRED=YES. SIG=SCTP. NN2=YES. 15. MODTYPE=P1. INS=SP14. SN1=NAT.

........16-2 16.....................5 Effects of BAM Operations on License .16-1 16...................................................................2 Application Scope ........1 LOD LICENSE (Loading a License)...............................HUAWEI MSOFTX3000 Feature Description Contents Contents 16 License Feature ................................................................4......................1 Function Code..................................................................................16-2 16........................16-19 16...............3 License Alarms.............1 License Checks .5..........2 Acornyms and Abbreviations ...............................................................3.........................3.....................................................................16-3 16..................6.........16-9 16...........................................2 Working Principle..................................16-5 16.........................................3..................................................16-10 16......................1 Service Description .............................................5...................................................6 DSP LICENSE (Display Running License File Status) ..............................1 Working Principle of License..4 License Upgrading .....................................................4..............16-12 16........................................................7 DMP LICENSE (Dumping License File) ...........................................3............2..........................................................................1 Protocols and Specifications ...........................16-7 16.......16-17 16...............3 LST LICENSE (Listing a License) ..............................................5 Other Precautions .....4 Alerting Mechanism of License .................................2.......................................................................................................................................................2 ROL LICENSE (Rolling Back a License) ................2..................................16-6 16...........4 License Control Items ....16-2 16....................................................................................16-4 16.........................................................................................3.................16-20 16.......................3...........6 Reference .............................................................16-21 16............................16-4 16.......................................................................................8 ULD LICENSE (Uploading License File to FTP Server)........................................................3..............................................................................................1 Control Items ................5 STR LICCRC (Starting CRC Check of License).....16-17 16.......................................................2 License Invalidation and Prevention ......................16-15 16............6.........................16-2 16.......................16-3 16...................3...................9 DLD LICENSE (Downloading License File from FTP Server) .......................................................................................................................................16-12 16...........1...................................................................................................2 Running Status of License .......3.. 16-11 16....................3 Invalidation of License......16-9 16.....................2 Resource Control Items..5.................16-20 16........................................................5.................................................................................................................................5...........2......................................................................................................16-2 16...................................16-21 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ...............................................................................................................................3 Operation and Maintenance of License...........................................................................................................................................................................16-2 16...................16-21 16...............4 DSP ESN (Displaying the System ESN)......................1.................................................16-17 16.............................................................16-12 16.........................

..... 16-11 Table 16-7 Alarms from host ...................................................16-6 Table 16-3 Parameters of the command DSP ESN........................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 16-1 Parameters of the command LOD LICENSE ..................................................16-8 Table 16-4 Parameters of the command DSP LICENSE ............................................16-10 Table 16-6 Parameters of the command ULD LICENSE .....16-4 Table 16-2 Parameters of the command LST LICENSE ...........16-19 Table 16-8 Alarms from BAM...............16-19 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) .......................................................................................................................................................................................................................................................................................................................................................................................................16-9 Table 16-5 Parameters of the command DMP LICENSE.............................................................................................................................................

The acronyms in this chapter. invalidation definition and alarm mechanism of the License feature.5 Other Precautions 16.4 License Control Items 16. The O&M commands and cautions of the License feature. Other cautions in using the License feature. The working principles. Section 16.HUAWEI MSOFTX3000 Feature Description 16 License Feature 16 About This Chapter The following table lists the contents of this chapter.2 Working Principle 16.3 Operation and Maintenance of License 16.1 Service Description 16.6 Reference Describes License Feature The function code and application scope of the License feature. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-1 . The control items and resource control items of the License feature. running status.

The License features of the MSOFTX3000 achieve customization of the service functions and quantity of the products.1 Working Principle of License The License functions of the MSOFTX3000 are realized on the basis of Huawei License unified platform. the status of the License is Trial. Physically.2 Running Status of License There are four running status of License: Normal: If the ESN in the License files loaded into the system is consistent with the ESN of the system.2 Application Scope For providers.2.1. The application of the License should conform to the related regulations of Huawei. 16. the License is a contract form of being authorized with the usage scope and period of the purchased products.16 License Feature HUAWEI MSOFTX3000 Feature Description 16. customers also obtain the services promised by providers. The following are realized by Huawei unified platform: Key generation management License file generation License file management Encryption/decryption signature verification module The following are realized by the MSOFTX3000 products: ESN setting acquisition License file installation update License file verification Capacity restriction of service function 16. the status of the License is Normal. the License is presented as License authorization certificates and License files.1 Service Description 16. the License is a contract form of authorizing the usage scope and period of the sold products.1.1 Function Code This feature does not have a function code. Trial: If the ESN in the License files loaded into the system is inconsistent with the ESN of the system.2. For customers. 16-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . This document aims to help technical staff to use the License features correctly. Through the License. 16.2 Working Principle 16.

2. The "Rest days" in the alarm represents how many days are left before the due date.3 Invalidation of License The latest date among the due dates of all License segments is taken as the due date of the License file. but a fault alarm indicating that the License is expired is sent every day. and sends another alarm indicating that the License is expired. Each item of the License file also has four running status: Normal.2. It has four running status: Normal. Default: After License files are expired for 60 days or the default minimum values are used for 60 days. there comes a 60-day invalidation alerting period. Invalidating and Default. Partial invalidation of the License: If the due date of a specific feature is not equal to the due date of the whole License file. the system recovers the fault alarm of the first day. the default minimum value is enabled. In the next day. After the 60-day invalidation alerting period.HUAWEI MSOFTX3000 Feature Description 16 License Feature Invalidating: If the License files loaded into the system is expired. Invalidating and Default. After the 60 days. In the next day. the system sends a fault alarm every day indicating that the License will be expired. Trial. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-3 . the feature is handled as "Invalidation of the whole License". and sends another alarm indicating that the License will be expired. For "Partial invalidation of the License". After the whole License file is expired. the system enables the default minimum value. and sends another alarm indicating that the License item is expired. but alarms indicating that the License is expired are sent every day. there comes a 60-day invalidation alerting period. or no valid License file is loaded into the system. the system recovers the fault alarm of the first day. 16. there are three types of alarms: When an item of a License file will be invalid in less than 30 days. the system recovers the fault alarm of the first day. and a fault alarm indicating that the License is expired is sent every day. 16. and sends another alarm indicating that the License is expired. there are three types of alarms: When the whole License will be invalid in less than 90 days. a fault alarm indicating that the License item will be expired soon is sent every day. In this case. and sends another alarm indicating that the License item will be expired. the system recovers the fault alarm of the first day. the original configuration values of the License are remained. the system runs under default License and provides only the default permitted License functions. In the next day. Trial. In the next day. During the period. After a License item is expired. the system recovers the fault alarm of the first day. During this period. the system triggers a 60-day invalidation alerting period. each control item of the License files can still be used for 60 days without any service restriction. but a fault alarm indicating that the License is expired is sent every day. In the next day. Invalidation of License contains the following: Invalidation of the whole License: If the due date of a specific feature is equal to the due date of the whole License file. the original configuration values of the License are remained. the feature is handled as "Partial invalidation of the License".4 Alerting Mechanism of License For "Invalidation of the whole License". The "Rest days" in the alarm represents how many days are left before the due date.

run DSP LICENSE and TR LICCRC immediately to check whether the Licenses of the host and the BAM are consistent. There are 10 alarm cause values for the event alarm "invalid license". you must back up them to avoid unexpected incidents. Notes: The License must be in the License subdirectory under the installation directory. but they are not displayed. in the format of “Lic*. After the loading.16 License Feature HUAWEI MSOFTX3000 Feature Description After the 60-day invalidation alerting period.1 LOD LICENSE (Loading a License) You can run LOD LICENSE to load License files and enlarge the subscriber capability and functions of the system. the system enables the minimum default value of the License item. If not. you must load valid License files again. therefore. because the License items are expired if the whole License file is expired. the License becomes invalid. If not. check the following: Whether the loaded License is normal. Whether the License of the host and the License of the BAM are consistent. 16-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 16. alarms indicating that the License items are expired are not sent. do not edit them.3 Operation and Maintenance of License After getting License files.3. The input parameter cannot contain any other directory name. contact Huawei technical staff for consultation. After the whole License is expired. Table 16-1 Parameters of the command LOD LICENSE Parameter Name FN Data Type String Parameter Description License name Explanation It specifies the License to be loaded. If not. License files are digitally subscribed. Parameter Description Table 16-1 shows the parameters of the command LOD LICENSE. 16.dat”. Or. When such event alarms occur. you must load valid License files again.

If the specified License does not exist. Notes: In general.3. a message indicating failure in running the command is returned.HUAWEI MSOFTX3000 Feature Description 16 License Feature Parameter Name LT Data Type Enumeration Parameter Description Location Explanation It specifies the target location to which License is to be loaded. Then the last License is in use. It is not required for any version later than R002C01B031. for any version between R002C01B022 and R002C01B031 (except B031). Therefore. The options are: BAM. the system has trialed the License). That is. If the system has ever loaded a License with an inconsistent ESN (that is. or the License is expired. the running mode turns to be Default. the system is in trial running (the trial period is specified when applying License files). The configuration values of the License remain. If the ESN of the specified License is inconsistent with that of the equipment. After the 60 days. Or. you must select BAM for loading. the command can be executed successfully. any License with an inconsistent ESN cannot be loaded again. you are recommended to use the default value of the parameter. but an alarm indicating inconsistent ESNs is generated. when you find the License is in Trial status. the License only provides default functions when the Invalidating period is over. if it is required to be updated to any version later than R002C01B031. Notes Pay attention to the following when using this command. This parameter must be set to BAM in certain special cases. the License is verified to be incorrect. This does not affect the License in use. you can run ROL LICENSE to roll back from the current License file to the License file of the last time. In this case. and subscribers are allowed to use the License for 60 days. the system prompts that the trial period is expired. you can switch over Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-5 . The products run under the default License and provide only the default permitted License functions. and BAM and host. If the new License has fewer functions or a lower capacity than the original one. the functions of the License can be normally used. and each module uses the new License data. 16. and the running mode turns to be Invalidating. After the trail period. you must apply for a formal License immediately. To switch over easily. During this period. a prompt for successful loading is prompted. Using this command. But an alarm indicating that the new License has less functions or lower capacity is generated. together with related prompts.2 ROL LICENSE (Rolling Back a License) The host database can store only the License files of the latest 2 loadings. License decryption fails.

16. including the loaded License files. Parameter Description The command ROL LICENSE has no parameter.16 License Feature HUAWEI MSOFTX3000 Feature Description easily between the last two License files. and you can input the License you want to check. The parameter License name is displayed. The parameter File type is displayed. This command is in fact to take the name of the License that has been successfully loaded last time. namely the source type of the License. and then auto run LOD LICENSE to load the License. Table 16-2 Parameters of the command LST LICENSE Parameter Name ST Data Type Enumerati on Parameter Description Source Type Explanation It specifies the location where the License to be queried is stored. Notes When the system performs the rollback operation.3. and you can select Current license or History license to check. The parameter options are: Disk: to query the information of the License stored on the BAM disk. In general. Normal configuration here means the License files that have been successfully loaded in the system. 16-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . and the unloaded License files under D:\MSOFTX3000\License. you can run LST LICENSE to check License files. it rolls back to the last normal License configuration. and then the system obtains the rights to change different functions and customer capacities. DB (database): to query the information of the License stored in the BAM database. you are recommended to run LOD LICENSE directly to reload the License.3 LST LICENSE (Listing a License) During maintenance. Parameter Description Table 16-2 shows the parameters of the command LST LICENSE.

These rules are also applicable to other License operation commands. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-7 . It specifies the name of the License to be displayed. License files must be located in the License subdirectory under the installation directory. When the file name is typed in. This option is the default value.3. You can run DSP ESN to query the ESN information. Parameter Description Table 16-3 shows the parameters of the command DSP ESN. you are recommended to change the License name to "LICENSESerialNo" field content before loading the License. Usually the License files from the License center of Huawei are initiated with "OR" or other letters. History license: to display the history License files in the database. all the License files in “Lic*. the entity serial number (ESN) information is needed when applying License files. Notes: When this parameter is in the default value. FT Enumerati on File type The parameter is valid only when Source type is set to DB. 16.4 DSP ESN (Displaying the System ESN) During deployment or maintenance. without the directory name. The parameter options are: Current license: to display the current License file in the database. the License files of which the names initiate with the characters "LIC" in the License subdirectory under the installation directory are displayed. It specifies the name of the License to be displayed. Notes Pay attention to the following when using this command: When File name is null.HUAWEI MSOFTX3000 Feature Description 16 License Feature Parameter Name FN Data Type String Parameter Description License name Explanation The parameter is valid only when Source type is set to Disk. So.dat” format in the License subdirectory under the installation directory are displayed. the content of the License is displayed. Only a complete file name with extension name can be typed in File name.

After the License is loaded to the equipment. errors occur in obtaining the ESN. Set Display type to Current config in BAM. the system ESN information generated according to certain algorithm is displayed. The serial number of the equipment to be authorized is contained in License file. The system authorizes corresponding services to the equipment only when the two ESNs are consistent. the ESN in the host is displayed. You can change the sequence of the configuration. Step 2 Configure the MSC number and the DPC number offline. When the system is running. The parameter options are: When LT is set to Current config in BAM. If you do have to modify them. Notes ESN means entity serial number. must ensure the correctness of the ESN. therefore. the ESN is irrelevant to the sequence of the signaling points. but any other change leads to different ESNs. When LT is set to Input raw ESN. otherwise. The MSC and DPC number must be identical with the actual data of the current network. The following are the steps to obtain the ESN: Step 1 Install the BAM. Step 3 Run DSP ESN to obtain the ESN. the system compares the ESN in the License file with that of the equipment. you must obtain a new ESN number based on the data after the modification. and then apply a new License. It is: The only identifier of a set of equipment The key guarantee of authorizing a License to a specific set of equipment The most important information of License files You. the ESN in the BAM server is displayed. otherwise the License may become invalid. ----End When there are multiple signaling points. You cannot add or delete signaling points. you cannot modify the MSC number or signaling point number. 16-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) .16 License Feature HUAWEI MSOFTX3000 Feature Description Table 16-3 Parameters of the command DSP ESN Name LT Data Type Enumeration Parameter Description Display type Explanation It specifies the type of the ESN to be displayed. When LT is set to Current config in Device.

The foreground host originates an automatic check every two hours. If yes. If the sizes and names of the licenses are identical. Notes Pay attention to the following when using this command: When the BAM originates STR LICCRC. the licenses are considered consistent. In this case.3. both the licenses in the host and the BAM are displayed. enables the 10-minute basis check timer. The system compares the file names and CRC values only. Parameter Description The command STR LICCRC has no parameter. The BAM sends the information of the License loaded in the BAM to the host.5 STR LICCRC (Starting CRC Check of License) During maintenance. The parameter options are: BAM: The License in the BAM server is displayed. the host enables the 2-hour basis check timer. irrespective of the check results. you can run DSP LICENSE to display the License status of the BAM and the host. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-9 .3. If no parameter is selected. you can run STR LICCRC to compare the consistency of the License data of the host and the BAM. If not. the system checks whether the loaded Licenses of the BAM and the foreground host are consistent. the host keeps the license of itself. the host performs the following: − Check whether the information of the licenses loaded in the host and in the BAM are consistent. Table 16-4 Parameters of the command DSP LICENSE Name DT Data Type Enumeration Parameter Description Display type Explanation It specifies whether to display the status of the License files of the BAM or the host. − − 16.HUAWEI MSOFTX3000 Feature Description 16 License Feature 16. and sends an event alarm indicating that both the licenses of the BAM and the host are valid but inconsistent. Host: The License in the host is displayed.6 DSP LICENSE (Display Running License File Status) During maintenance. Parameter Description Table 16-4 shows the parameters of the command DSP LICENSE.

The parameter options are: Current file: to dump the current License files in the database which are in use. History file: to dump the history License files in the database which were used. Table 16-5 Parameters of the command DMP LICENSE Name ST Data Type Enumeration Parameter Description Source type Explanation It specifies the location where the License to be displaced is stored. It is used to specify the License files in the database to be dumped. such as Lic_current. FN String File name The parameter is valid only when Source type is set to Database. you can run DMP LICENSE to dump License files. 16-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The License files that can be dumped are: The running License files in the host The current License files in the database The history License files in the database Parameter Description Table 16-5 shows the parameters of the command DMP LICENSE. namely the source type of the License.dat. The file names must begin with "Lic".16 License Feature HUAWEI MSOFTX3000 Feature Description Notes DSP LICENSE is different from the command LST LICENSE.3. 16. The parameter options are: DEV: The License files stored in the host are displaced.7 DMP LICENSE (Dumping License File) During maintenance. The backup files are stored under D:\MSOFTX3000\License and named "License + current time". LST LICENSE is used to display the static License information while DSP LICENSE is to display the licenses that is loaded to the system and is in use at present. FT String File type The parameter is valid only when Source type is set to Database. DB: The License files stored in the database are displaced. It is used to specify the names of the current License files in the database to be dumped.

date. the file must be named "LICENSEYYYYMMDDHHMMSS. You are recommended to save the license manually instead of using the DMP method. USR Subscriber name PWD String Password DIR String Directory FN FSN String String File name File serial number Notes This command uploads License file. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-11 .3. The default value is the IP address of the default file server. Mandatory. When exporting the "Current license files" or "History license files" from the database to a file. Subscriber password used to log in to the FTP server. The default value is the subscriber name for logging in to the default file server. 16. month. Mandatory. The default value is the subscriber password for logging in to the default file server. The path on the FTP server where the files to be loaded (License files) are stored.This command has a reverse function comparing to the command DLD LICENSE. Directory name. Subscriber name used to log in to the FTP server. This file is stored in the License subdirectory under the BAM installation directory. Table 16-6 Parameters of the command ULD LICENSE Parameter Name IP Data Type IP address String Parameter Description IP address Explanation IP address of the FTP server.8 ULD LICENSE (Uploading License File to FTP Server) Parameter Description Table 16-6 shows the parameters of the command ULD LICENSE. Optional. Optional.txt" in which the letters in upper case in the latter part indicate the year. minute and second of the current system time. Optional. Full name of the file to be loaded. hour. By default. you can name the file freely.HUAWEI MSOFTX3000 Feature Description 16 License Feature Notes Pay attention to the following when using this command: When you export the contents of the License files being used on the host to a file. the content of the current License file is uploaded. Generated serial numbers of License files. Optional. network elements (NEs) also act as the FTP CLIENT). obtains License files from the system and store them to a specified FTP server (similar to the command DLD LICENSE.

The NEs act as the FTP clients.3. even if the system is restarted. the License files must be updated at the same time.4 License Control Items 16.4.1 Control Items Control Items CAMEL IN service Switching between the GSM and the WCDMA system Description Decide whether to enable the IN service. refer to 16. TMSC VMSC When the HO module processes switching requests originated by the local office or incoming switching requests. and then decide whether the switching can be supported based on the License. If not. Decide whether to enable the SMS based on the License when the MSC interacts with the SMC.16 License Feature HUAWEI MSOFTX3000 Feature Description 16. Disabled SMS Disabled VMSC TFO/TrFO Disabled VMSC. GMSC. decide whether to enable the TFO/TrFO function based on the License. When the CM and the BICC receive the Codec negotiation result from each other.3. GMSC.8 "ULD LICENSE (Uploading License File to FTP Server). TMSC 16-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 16. the TrFO does not deliver the Modify process to the gateway. Parameter Description For more details of the parameters of the command DLD LICENSE. The new License is not effective. Default Value Disabled Scenario VMSC. The NEs still use the original License configuration data. and no decryption and ESN comparison are conducted (These operations are performed while running the command LOD LICENSE). query the destination route from the database to determine the type of the switching side (2G or 3G).If the ESNs of the NEs are changed. Notes DLD LICENSE only downloads License files to NEs.9 DLD LICENSE (Downloading License File from FTP Server) The command DLD LICENSE loads the specific License files on the FTP server to NEs through the FTP protocol.

GMSC. Intra-office Iu-Flex means that one RNC can be connected to multiple MGWs under the control of one MSC Server. GMSC. GMSC VMSC eMLPP Disabled MNP Disabled Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-13 . Decide whether to enable dual homing and handover functions based on the judgment of the License. GMSC Intra-office Iu-Flex Disabled VMSC PRA access Disabled VMSC. Decide whether to enable related configurations and services of valid monitoring based on the judgment of the License. TMSC VMSC. TMSC VMSC VMSC SG Disabled STP Disabled Mc interface encryption CS multimedia service Virtual network operator (VNO) Lawful interception Disabled Disabled Disabled Disabled VMSC. Decide whether to perform signaling bearer conversion. GMSC. Decide whether to enable related configurations and services of eMLPP based on the judgment of the License. GMSC. Decide whether to enable the related configurations and services of VNOs based on the judgment of the License.HUAWEI MSOFTX3000 Feature Description 16 License Feature Control Items LCS Description In the MT_LR. forwarding and related configuration based on the judgment of the License. Default Value Disabled Scenario VMSC Dual homing Disabled VMSC. Decide whether to perform signaling forwarding and related configuration based on the judgment of the License. Decide whether to enable related configurations and services of intra-office Iu-Flex based on the judgment of the License. TMSC VMSC. TMSC VMSC. Decide whether to enable the PS multimedia service based on the judgment of the License. decide whether to reject the LCS requests based on the License. MO_LR and NI_LR processes. GMSC VMSC. Decide whether to enable related configurations and services of PRA based on the judgment of the License. Decide whether to enable related configurations and services of MNP (only IN mode is supported at present) based on the judgment of the License. Decide whether to enable the encryption function over the Mc interface based on the judgment of the License.

GMSC Gs interface Disabled VMSC Built-in EIR Disabled VMSC ARD ECT Disabled Disabled VMSC VMSC SCCP filtering and shielding MAP policing MGCF Half-rate hierarchical access SNA connection mode sharing Inter-office Iu-flex Min-A-Flex Disabled VMSC Disabled Disabled Disabled VMSC VMSC VMSC Disabled VMSC Disabled VMSC Disabled VMSC 16-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Decide whether to enable the Min-A-Flex function based on the judgment of the License.16 License Feature HUAWEI MSOFTX3000 Feature Description Control Items Short message intelligent routing Description Decide whether to enable the related configurations and services of short message intelligent routing (short messages are directly forwarded instead of through the SMC) based on the judgment of the License. Decide whether to enable the half-rate hierarchical access function based on the judgment of the License. Decide to enable the MGCF function based on the judgment of the License. The EIR function is built in the MSC. Decide whether to enable the inter-office Iu-Flex function based on the judgment of the License. Decide to enable the explicit call transfer (ECT) function based on the judgment of the License. Decide to enable the SCCP filtering and shielding function based on the judgment of the License. Decide whether to notify the callee of the calling number through a short message when a call is not connected because of called line busy. Decide whether to enable signaling handling and related configuration over the Gs interface based on the judgment of the License. Decide to enable the MAP Policing function based on the judgment of the License. Decide whether to enable the SNA connection mode sharing function based on the judgment of the License. Default Value Disabled Scenario VMSC Notification by SM Disabled VMSC. Decide whether to enable the EIR based on the License. Decide to enable the ARD function based on the judgment of the License.

The number of connected 2G subscriber calls (total number of 2G end office subscribers x ERL each subscriber). GMSC. GMSC Subscriber protocol tracing Centralized signaling monitoring Disabled Disabled 16.2 Resource Control Items Resource Control Items Total number of subscribers Description Controlled in the DB. Decide whether to enable the NTP function based on the judgment of the License. TMSC VMSC. The number of connected 3G subscriber calls (total number of 3G end office subscribers x ERL each subscriber). Decide whether to enable subscriber tracing and signaling tracing functions based on the judgment of the License.HUAWEI MSOFTX3000 Feature Description 16 License Feature Control Items ISUP LOOP BAC SOR Flexible control of AC version ussd NTP Description Decide whether to enable the ISUP LOOP BACK function based on the judgment of the License. It controls the processing capability. Decide whether to enable the SOR function based on the judgment of the License. Default Value 4000 Scenario VMSC Total number of IN calls 100 VMSC. TMSC VMSC. Default Value Disabled Scenario VMSC Disabled Disabled VMSC VMSC Disabled Disabled VMSC VMSC. Decide whether to enable the centralized signaling monitoring function based on the judgment of the License. GMSC. The number of the attached subscribers is limited in the VDB to be less than total number of subscribers.4. GMSC Number of calls originated by 2G end office Number of calls originated by 3G end office 100 VMSC 100 VMSC Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-15 . It controls the processing capabilities. It controls the processing capability. The number of intelligent connections realized by the IN (total IN subscriber number x ERL each IN subscriber). Decide whether to enable the flexible control of AC version function based on the judgment of the License. Decide whether to enable the ussd function based on the judgment of the License.

It limits the number of multiple signaling points that can be configured. TMSC Cluster service is ready for the VMSC. TMSC VMSC. The number of the subscribers on call hold (total number of subscribers on call hold x ERL each subscriber). GMSC VMSC. GMSC 1 VMSC. The number of the subscribers on call waiting (total number of subscribers on call waiting x ERL each subscriber). GMSC. The number of data service subscribers (total number of data service subscribers x ERL each subscriber). It limits the number of the 2M signaling links can be configured.16 License Feature HUAWEI MSOFTX3000 Feature Description Resource Control Items Number of trunk calls Description The CCB controls the number of various types of trunks (total channel number x 2 or Total E1 number x 31). TMSC Supported number of held calls Supported number of waiting calls Number of subscribers in a multiparty call Number of data service subscribers Number of monitored subscribers Number of monitored centers Number of 2M signaling links Number of multiple signaling points Number of group calls Number of broadcast calls 100 VMSC 100 VMSC 10 VMSC 10 VMSC 10 VMSC. GMSC. 1 1 0 0 16-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . including the ISUP trunk number and BICC trunk number. Cluster service is ready for the VMSC. The number of monitored subscribers that can be configured (VMSC: total system subscriber number x percentage of monitored subscribers) It controls the number of the valid monitoring centers that can be connected with the MSC. The number of the subscribers in a multiparty call (total number of subscribers in a multiparty call x ERL each subscriber). It limits the number of the group calls that can be originated simultaneously (VGCS calls) It limits the number of the broadcast calls that can be originated simultaneously (VBS calls) Default Value 100 Scenario GMSC.

If yes and the license file is in the 60-day invalidation alerting period. and one day is reduced from the rest days in the check every day. 16. irrespective of the check results. If the usage period is exceeded and the license file is in the 60-day invalidation alerting period. an alarm indicating that the License will be expired is sent. Check whether the license files loaded in the host and in the BAM are consistent. or the running period of formal License which is specified in License files is expired. After 60 days. If yes. If yes.5 Other Precautions 16. If not. the system remains the original License configuration information and sends an alarm indicating that the License is expired. At this time.5. judge whether the rest days of an item are less than 30 days. the system remains the original License configuration information and sends an alarm indicating that the License is expired. an alarm indicating that the License will be expired is sent. the license files are considered consistent. the BAM and the host check the dates of the currently used License files. The steps are as follows: Step 1 If the license file is in trial state. If the usage period is exceeded and the license file is in the 60-day invalidation alerting period. the License runs with default configurations and provides the default allowed functions only.5. If they are consistent. judge whether the rest days of the License are less than 90 days.HUAWEI MSOFTX3000 Feature Description 16 License Feature 16. After 60 days. In this case. and one day is reduced from the rest days in the check every day. the BAM sends the information of the License loaded in the BAM to the host. the License runs with the default configurations and provides the default allowed functions only. If they are inconsistent. If the sizes and names of the license files are identical. ----End Check from the Host The foreground host originates an automatic check every two hours. the host enables the 10-minute periodic check timer and sends an alarm indicating that the License is expired. the system remains the original License configuration information and sends an alarm indicating that the License is expired. Step 2 If the License is in normal state. 3. Step 3 If the License is handled by items. The cause value of the alarm is that both the licenses of the BAM and the host are valid but inconsistent.m. 2. Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-17 . judge whether the allowed trial period is expired. reduce one day from the rest days and send an alarm indicating that the License will be expired. every day.2 License Invalidation and Prevention License invalidation contains normal invalidation and abnormal invalidation. the host enables the 2-hour periodic check timer and check every two hours from then on. the host performs the following: 1. Normal invalidation: The trial period of trial License is expired.1 License Checks Timing Check At 01:20 a.

Invalid License on host The symptoms are: When you run DSP LICENSE to check the License on the host. you must set the parameter Position to BAM. The solution to this case: Run LOD LICENSE to load valid License files. At this time. The file names and control items of the License are remained. When loading the License offline. The solution to this case: Run LOD LICENSE to load valid License files. The file names are null and the control items are in the minimum values. Fault alarm "License is expired" (ID: 2183) appears in the alarm window. The symptoms are: Within the 60 days after the License is expired. License Files Are not Reloaded in Emergency Workstation After the Switchover from BAM to Emergency Workstation The prevention method of this case: Load the License on the emergency workstation offline after the database is recovered and before the emergency workstation is connected to the host. and the License control items are in their default maximum values. and the methods to prevent them and solve them. and the License control items are in their default minimum values. Within the 60 days after the License is expired. but the License becomes invalid because of certain maloperations or specific conditions. Fault alarm "License is expired" (ID: 2183) appears in the alarm window. The solution to this case: Run LOD LICENSE to load valid License files. you can run LOD LICENSE to reload the License files. License files Are Expired and not Reloaded License files are expired and not reloaded. the file name is null. you can run DSP LICENSE to check whether the running mode of the License is Invalidating. The tracing function on the operation console of the BAM is out of use. To ensure that the License files on 16-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Fault alarm "License is expired" (ID: 2183) and event alarm "License is invalid" (ID: 2246) appear in the alarm window. The following are certain symptoms of abnormal invalidation. the Licenses of the BAM and the host may be inconsistent. Invalid License on BAM The symptoms are: When you run DSP LICENSE to check the License on the BAM. indicating that the current License files of the system are in their default values with which the system capacities are straightly limited. the file name is null. if you have legal License files.16 License Feature HUAWEI MSOFTX3000 Feature Description Abnormal invalidation: The License files are loaded normally in the system. Alarms with ID 2381 and 2382 are generated. Once the License becomes invalid. you can run DSP LICENSE to check whether the running mode of the License is Default.

you should especially pay attention to the alarms 2181. run LOD LICENSE immediately to load the License to the host online. and 2246. 2187.3 License Alarms and Table 16-8 list the alarms related with the License. 2189.5. 2183.HUAWEI MSOFTX3000 Feature Description 16 License Feature the BAM are normal. In this case. after the emergency workstation and the host are connected. you cannot choose the parameter Position. Table 16-7 Alarms from host Alarm ID 2181 2182 2183 2184 2187 2188 2189 2190 2246 Alarm Name License will be expired License will be expired recovered License is expired License is expired recovered License item will be expired License item will be expired recovered License item is expired License item is expired recovered License is invalid alarm During maintenance. 16. Table 16-8 Alarms from BAM Alarm ID 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 Alarm Name Default license data loaded Default license feature loaded License file is invalid License file ESN does not match with system ESN Capability of license loaded is less than the old one License file trial date reached License file will be invalid License file will be invalid recovered License file expired License file expiry recovered Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-19 .

If the Licenses on the host and the BAM are different. the License files on the BAM are set to the minimum value if they cannot be used. you can only load the default License instead of the BAM License in the memory.5 Effects of BAM Operations on License When the BAM is abnormal. You must load the License files manually. No other special operation is required. alarms "License is invalid" are generated every 10 minutes. the details are given in the upgrade guide released with the version. you must run LOD LICENSE to reload the License files after the upgrade. the License files that were successfully loaded last time are reloaded on the BAM. if all versions of R002 are upgraded to R003. alarms indicating "License is expired" are generated every 10 minutes. When restarting the Maintain process on the BAM. The original License files cannot be auto loaded in the system when the BAM is restarted. the original information about the License is lost. Version Upgrading If there are special requirements upon version upgrading. it does not affect the License of the host. you should load the License with the command LOD LICENSE.5. In this case. if the License on the host is different from that on the BAM.5. Otherwise. 16-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) . because the host can run without the BAM.16 License Feature HUAWEI MSOFTX3000 Feature Description Alarm ID 2391 2392 2393 2394 2395 Alarm Name License file does not exist License file feature will be invalid License file feature will be invalid recovered License file feature expired License file feature expired recovered 16. If the SMU boards are restarted on the host. This severely affects the system function. License is analyzed in the FLASH. In this case. the related information of the License is recorded in the BAM database. When the BAM is reinstalled. 16. This does not affect the BAM and the services.4 License Upgrading License Updating When the signaling point configurations are modified or new service contracts are signed. it is necessary to apply new License files. the original License remains. At this time. If the SMU boards are not restarted on the host. If the record does not exist in the database. When upgrading the BAM.

2 Acornyms and Abbreviations Acronym/Abbreviation AC ARD BAM BICC CAMEL CCB CRC ECT EIR eMLPP ESN FTP GMSC GSM IN LCS MGCF MGW MNP MO MSC MT NTP PRA RNC Full Name Application Context Access Restriction Data Back Administration Module Bearer Independent Call Control Protocol Customized Applications for Mobile network Enhanced Logic Call Control Block Cyclic Redundancy Check Explicit Call Transfer Equipment Identity Register enhanced Multi Level Precedence and Preemption Electronic Serial Number File Transfer Protocol Gateway Mobile Switching Center Global System for Mobile communications Intelligent Network Location Service Media Gateway Control Function Media Gateway Support of Mobile Number Portability Mobile Originated Mobile Switching Center Mobile Terminated Network Time Protocol Primary Rate Adaptation Radio Network Controller Issue 02 (2007-06-10) Huawei Technologies Proprietary 16-21 .6 Reference 16.6.6.1 Protocols and Specifications None. 16.HUAWEI MSOFTX3000 Feature Description 16 License Feature 16.

16 License Feature HUAWEI MSOFTX3000 Feature Description Acronym/Abbreviation SCCP SG SOR STP TFO TMSC TrFO VDB VMSC WCDMA Full Name Signaling Connection and Control Part Signaling Gateway Subsystem Out-of-service Request Signaling Transfer Point Tandem Free Operation Tandem Mobile Service Switching Center Transcoder Free Operation VLR Database Visited Mobile Switching Center Wideband Code Division Multiple Access 16-22 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

..............................................................................................................1...................................1 Monitoring Flow of Online User..........................................................................................................................................................17-6 17..........................................................4 Others.......................3..........................................................17-4 17...........4.....................5 Benefits .............3.........1..............................5....17-5 17.......................................................................................4..HUAWEI MSOFTX3000 Feature Description Contents Contents 17 NE User Dynamic Monitoring Feature ...........................................................2 Glossary.............17-6 17.......................6 Service Management ..........................17-7 17........................3 Working Principle........17-4 17........17-3 17..............4................................2 Reporting Flow of User Operation..................................................................................................17-4 17...............3 Standard Compliance ......2...................... 17-11 17......................2 Maintenance Operations ............................................................................................... 17-11 17..............................................................................2......................................................................4 System Specifications ...............................................10.............. Acronyms...................17-2 17.............................1 Overview..........................1............17-7 17.............................................1 Function Description ...........................................................................10 References ......6 Application Scenario ..................................................................................2 Requirements for License ...............17-12 17......................................17-6 17...............3 Disconnection Flow of User Operation.........................................................9 Service Interaction ...7 Charging and CDR ....4 Service Flow.............................1..........................17-4 17.................................................................................................................1........................8 Performance Measurement.17-5 17...............................................................................................................1..................................................................................3 External Interfaces ....................................1 Functions of NEs.........................................................................................................................................................................................................................2 Internal Processing of the System ...............................1 Standards and Specifications..1........................................................................2 Definition ...............................................2..........................................................................................................................17-4 17..................................17-12 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .17-7 17........................................17-12 17...............................................................................................17-6 17.......................................................2 Availability .......................................................................................................................................................................................................................10.............7 Application Limitations...................1 Requirements for NEs...............................17-6 17..............................................17-1 17.........................................17-2 17..3 Applicable Versions...................2............5.......17-5 17..................... and Abbreviations ................................................ 17-11 17...............................................................................................................17-2 17........................................................... 17-11 17......................................................17-7 17.............1 Function Code..................17-5 17.............................................................5 Function Maintenance .............17-5 17.................................17-3 17..............3...................................................................................................................................................................................................................

................................11 FAQ .Contents HUAWEI MSOFTX3000 Feature Description 17..................................................................................................17-12 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ......................

...................................................................................................................................................................................................................................17-8 Figure 17-4 User Monitor interface......17-2 Figure 17-2 User Monitor interface..............................................17-10 Figure 17-7 Filtering interface..........................................................................................................................................................................17-10 Figure 17-5 User Session interface 1....................................................................................17-8 Figure 17-3 Subscribed NE List interface ..................................................17-10 Figure 17-6 User Session interface 2....................................................... 17-11 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii .................................................................................................HUAWEI MSOFTX3000 Feature Description Figures Figures Figure 17-1 Local Maintenance Monitor tabbed page......................

...........17-5 iv Huawei Technologies Proprietary Issue 02 (2007-06-10) ........................17-3 Table 17-3 Specifications of the system .17-2 Table 17-2 Explanations of the Local Maintenance Monitor tabbed page...............................................................................................................................................................................................................................................................................................................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 17-1 Function code of the NE user dynamic monitoring function...................................17-5 Table 17-6 Version that supports this function..................................................................................................17-4 Table 17-5 NEs that are involved in this function .....17-4 Table 17-4 Description of benefits...................................................

1 Function Description 17. The procedure for performing charging and generating CDRs when the service is provided. The frequently asked questions related to the service and the solutions.HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature 17 NE User Dynamic Monitoring Feature About This Chapter The following table lists the contents of this chapter.11 FAQ Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-1 .10 References 17. Section 17.5 Function Maintenance 17. The standards and specifications with which the service complies and the glossary.4 Service Flow 17. abbreviations.7 Charging and CDR 17. The NEs required to implement the service. The data configuration that must be performed at the MSOFTX3000 side and the UMG8900 side as well as the examples of function maintenance. 17. The functions of the NEs used to implement the service and the requirements on the networking. and acronyms used in this chapter. and versions of the products applicable to the service. The association between the service and other services as well as the restrictions on each other.9 Service Interaction 17. The flow of the service.8 Performance Measurement 17.3 Working Principle 17. The influence of the service on performance measurement and the implementation of performance measurement.2 Availability Describes The function code and definition of the service and the benefits of the service to carriers and mobile subscribers.6 Service Management 17. requirements for the license. The operations that carrier and mobile subscribers must perform when the service is provided.

For the explanations of the Local Maintenance Monitor tabbed page. the network management system (NMS) monitors the operation information and status of online NE users in real time.2 Definition Through the network element (NE) user dynamic monitoring function.17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description 17.1. Table 17-1 Function code of the NE user dynamic monitoring function Name NE user dynamic monitoring function Code - 17.1 Function Description 17.1.1 Function Code Table 17-1 specifies the function code of the NE user dynamic monitoring function. The monitoring information is displayed on the Local Maintenance Monitor tabbed page on the M2000 client. see Table 17-2. Figure 17-1 Local Maintenance Monitor tabbed page 17-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Figure 17-1 shows the Local Maintenance Monitor tabbed page.

1. Specifies the login time of an NE user. By default. including by proxy (Yes) and not by proxy (No). including online and unknown. Specifies the current status of an NE user. used to force a user to exit. 17. Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-3 . including O&M system and performance maintenance system. the NMS refers to the M2000.3 Standard Compliance None.1. used to choose the operation results reported by the NE user. used to obtain the latest information.HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature Table 17-2 Explanations of the Local Maintenance Monitor tabbed page Item NE Name User Name User Type Login IP Login Time Service Definition Specifies the name of the login NE. all names of the NEs that log in to the M2000 are specified. A function button. A function button.4 System Specifications Table 17-3 lists the specifications of the system. Specifies the login mode of an NE user. used to save all information displayed in the page. A function button. Specifies the type of the service console through which the NE user logs in to the M2000. A function button. 17. Specifies the name of the login user. all names of the NEs that log in to the M2000 are specified. Specifies the IP address of the client that is connected to the NE. By proxy Status Filter Refresh Save Subscribe… Force User to Exit In this chapter. Specifies whether the user is a local user (LOCAL) or an NMS user (EMS). By default. used to display information in this page by selection. A function button.

and obtain data configuration updates. The NMS can monitor the operation of the users of all NEs in real time. the M2000 must work with the MSC server. The user of this type is created. Domain user: It refers to a user uniformly managed by the NMS. through the M2000 client. Local user: It refers to users that are individually managed by each NE. By clicking Force User to Exit to disconnect a user from an NE. the NMS can prevent the user from performing subsequent operations. The user of this type can log in to the NE for operation during system initial installation or disconnection from the NMS. 17-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . authenticated or authorized by the NMS.2 Availability 17.6 Application Scenario This function applies to GSM and UMTS R99/R4. the user of this type can log in to the NE for operation. The network can implement the centralized management of NE users.7 Application Limitations All the operations involved in this function must be performed on the M2000. After authorization. Mobile subscriber - 17.1 Requirements for NEs To implement this function. through the local maintenance terminal (LMT).17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description Table 17-3 Specifications of the system Item NE user Specification It can be a local or domain user. 17. See Table 17-5. Table 17-4 Description of benefits Beneficiary Carrier Description The NMS can obtain the login information and manages NEs through monitoring the status of online users of all NEs.1.5 Benefits Table 17-4 describes the benefits for the beneficiary. and can also log in to the M2000 server for operation. including the default local user. modified.2.1.1. 17. 17.

After a user is disconnected from the NMS. The M2000. 17. To monitor only the operations that are cared for by the NMS. The M2000 sends the corresponding commands to NEs. To subscribe to users means to monitor the operations of the users. then. 3. Table 17-6 Version that supports this function Product MSC server MSOFTX3000 Applicable Version V100R005C10 17. the NE sends the disconnection message to the Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-5 .HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature Table 17-5 NEs that are involved in this function UE NodeB RNC MSC Server √ MGW SGSN GGSN M2000 √ "√" indicates the NE that is involved in this function. a subscription and unsubscription mechanism is used between the NEs and NMS. 2. The NMS need not monitor the operations of all NE online users because there are some operations that the NMS does not require.2. 17.3.2 Requirements for License No License is required for the availability of this function. 17.3 Working Principle 17.2. messages between the NEs and NMS are reduced.4 Others None. the NE status displayed is reported by the NEs to the M2000 actively. The NEs returns the command execution results to the M2000. and the load of the NEs and NMS is lowered.2. to unsubscribe to users means to cancel the monitoring of the operations of the users. the user is forced to exit the LMT and disconnect from the NE. The NE supports the forced disconnection from a user. displays the result in the Local Maintenance Monitor pane.1 Functions of NEs The NE user dynamic monitoring function is implemented as follows: 1. Through the subscription and unsubscription mechanism.3 Applicable Versions Table 17-6 shows the version of the HUAWEI core network (CN) that supports his function. Currently. through the disconnection command sent by the NMS. That is.

The NMS issues commands for unsubscribing to monitoring to an NE.4. The user of an NE that is monitored can be a local or domain user. the NMS sends a command for canceling the monitoring of all the users of an NE.4 Service Flow 17. To monitor the operations of all the users of an NE.3. the NE stops reporting the operations of the user to the NMS. indicating that the user is forcedly disconnected from the NMS.3. the NE reports the operations of the user to the NMS through the synchronization report interface.2 Reporting Flow of User Operation The NMS issues commands for subscribing to monitoring to an NE. Implementation of Forced Disconnection of Online User Operation When an NE receives a command.17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description LMT that the user belongs to. through the operation and maintenance port. After a user is disconnected from the NMS. But the NE must take the initiative to update its data to the NMS later. through the operation and maintenance port. Implementation of Monitoring of NE Online User Operation When the NMS issues a command for monitoring an NE user.3 External Interfaces None. 17-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . To cancel the monitoring of the operations of all the users of an NE. a message is displayed. At this time. When an LMT is disconnected from the NE. 17. 17. the NE sends the disconnection message to the LMT that the user belongs to. the NE reports the operations of the user to the NMS immediately. the NMS sends a command for monitoring all the users of an NE. the NMS obtains the status of the online users of the NE automatically. indicating that the user is forcedly disconnected from the NMS. At this time. the NEs report the status to the NMS actively. When the NMS first connects to an NE. a message is displayed on the LMT. a message is displayed on the LMT. the NE disconnects from all the LMTs that the user logged in to. When the NMS issues a command to cancel the monitoring of an NE user. indicating disconnection from a user. After receiving the commands. The NMS can automatically obtain the online user status of NEs for the first time connection.4. After receiving the commands. For the following data update. 17. 17. the NE stops reporting the operations of the user to the NMS.2 Internal Processing of the System Function Implementation The login and logout of an NE user need to be reported to the NMS.1 Monitoring Flow of Online User The login and logout of an NE user must be reported to the NMS through synchronization. indicating that the user is forcedly disconnected from the NMS.

the LMT cancels the user login.4.3 Disconnection Flow of User Operation When the NMS issues commands for forcing user to exit. The User Monitor interface is displayed.5.HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature 17. The function includes: Subscription Canceling the subscription Querying user subscription information Forcing user to exit Filtering 17.5. indicating that the user is disconnected from the NMS. the NE reports the disconnection message to the LMT to which the user belongs to. perform the following steps: Step 1 Choose System > User Monitor on the M20000 client. as shown in Figure 17-2. 17.5 Function Maintenance 17. When the NE disconnects from the LMT.1 Overview The NE user dynamic monitoring function is performed through GUI mode on the M2000 client. Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-7 .2 Maintenance Operations Subscription To subscribe to the monitoring.

17-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Figure 17-3 Subscribed NE List interface Step 3 Tick the NE to be subscribed.17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description Figure 17-2 User Monitor interface Step 2 Click the Local Maintenance Monitor tab and click Subscribe in the Local Maintenance Monitor tabbed page. as shown in Figure 17-3. The Subscribed NE List interface is displayed.

Step 3 Deselect the NE to be un-subscribed. You can find that all subscribed NEs are ticked. ----End Querying User Subscription Information The procedure for querying user subscription information is as follows: Step 1 Choose System > User Monitor on the M20000 client. ----End Canceling Subscription The procedure for canceling the subscription is as follows: Step 1 Choose System > User Monitor on the M20000 client. Step 2 Click the Local Maintenance Monitor tab and click Subscribe in the Local Maintenance Monitor tabbed page. The User Monitor interface is displayed. Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-9 . as shown in Figure 17-4. The Subscribed NE List interface is displayed. The subscription is completed. as shown in Figure 17-3. Step 3 Click OK. The Subscribed NE List interface is displayed. as shown in Figure 17-2. as shown in Figure 17-2. The canceling subscription operation is completed. Step 2 Click the Local Maintenance Monitor tab and click Subscribe in the Local Maintenance Monitor tabbed page. The User Monitor interface is displayed. The querying user subscription information operation is completed. The User Monitor interface is displayed. as shown in Figure 17-3. ----End Forcing User to Exit The procedure for forcing user to exit is as follows: Step 1 Choose System > User Monitor on the M20000 client.HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature Step 4 Click OK. Step 4 Click OK.

The forcing user to exit operation is completed. as shown in Figure 17-7. as shown in Figure 17-6. as shown in Figure 17-5.17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description Figure 17-4 User Monitor interface Step 2 Click the Local Maintenance Monitor tab and select the NE to be disconnected forcedly in the User Session interface. Figure 17-5 User Session interface 1 Step 3 Click Force User to Exit. 17-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Figure 17-6 User Session interface 2 ----End Filtering The procedure for filtering is as follows: Step 1 Click Filter in the Local Maintenance Monitor interface to enter the filtering interface.

17. The system displays the information that meets the conditions to the Local Maintenance Monitor interface. ----End 17.HUAWEI MSOFTX3000 Feature Description 17 NE User Dynamic Monitoring Feature Figure 17-7 Filtering interface Step 2 Set conditions of the NE user to be filtered in the NE. Login IP.7 Charging and CDR None.8 Performance Measurement None. 17. Step 3 Click OK. User. and Service panes.9 Service Interaction None. Issue 02 (2007-06-10) Huawei Technologies Proprietary 17-11 .6 Service Management None. 17.

10. 17.10 References 17.17 NE User Dynamic Monitoring Feature HUAWEI MSOFTX3000 Feature Description 17.2 Glossary.10.1 Standards and Specifications None. Acronyms and Abbreviations Acronym/Abbreviation LMT Full Name Local Maintenance Terminal 17.11 FAQ None. and Abbreviations Glossary None. 17-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Acronyms.

.....................................................1..............................18-6 18.......7.................8........................................18-7 18...............................................................................................2.............................................................................................................................1.....................................................................1 CDR of the SMMO...1 Data Configuration on the MSOFTX3000....................3 Call Forwarding Service ......................................2 SM Service.18-3 18.............................................8.............................2.....5.........3........................................18-4 18.............................................................18-3 18..................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 18 SMS Notification for Call Failure Feature .................18-13 18........................................................................................................................................................18-1 18..............................1 Prerequisites for Service Triggering..18-13 18.................4.............1.......................................18-13 18..............................2 Requirements for License ......2 CDR of the SMMT ......................................6.................................................................................4.......................18-6 18.18-14 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ........18-12 18................................................................................................................3 Benefits ......................................3 Applicable Versions.................................18-10 18............................................................................................18-3 18................................................18-13 18...............................................................................................3 Working Principle..................................................18-10 18.18-2 18........................18-13 18............................................................................8.................4 Voice Mailbox Service ........................................18-2 18..........................................1 Operations by Carriers ...................................................................................................................................................................................5......................3 Processing Flow After Service Triggering ........................................................1 Requirements for NEs......................................6 Service Management ..........................................................................................................................................................................................................................3....18-13 18......2........................................................................................................................................................2 Service Triggering Point .................................18-13 18...........18-13 18.........6............................7..............................................18-2 18..................2 Definition ................................................18-14 18............. 18-11 18.....8 Service Interaction ....................................................................................1 Functions of Each NE .................18-8 18..............................................................................................................................5 Data Configuration.........2 Availability ...................18-13 18.................................2 Operations by Subscribers .............................................................................................................7 Charging and Charging Data Record (CDR)................................8.....................................................18-3 18.......................3 Charging.........................................7...........................1 Service Description .........................4................................................................18-2 18............................2 Data Configuration Sample............................................................2 Internal Processing......................................................................................................18-3 18...................................18-10 18........................................18-3 18......................................................................................................................9 Reference ..........................................1 Call Service..........1 Function Code..............4 Service Flow........................

.......................................................................................................................................18-14 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ...9..........Contents HUAWEI MSOFTX3000 Feature Description 18.1 Protocols and Specifications ........2 Aronyms and Abbreviations.............9.........................................18-14 18.......

................................18-7 Figure 18-4 Triggering point of SMS notification for call failure in the VMSC..........................................18-5 Figure 18-2 Processing flow of SMS notification for call failure generated in the VMSC...................................................................18-6 Figure 18-3 Triggering point of SMS notification for call failure in the GMSC..................18-9 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ..............HUAWEI MSOFTX3000 Feature Description Figures Figures Figure 18-1 Processing flow of SMS notification for call failure triggered in the GMSC......18-8 Figure 18-5 Processing flow after SMS notification for call failure is triggered.....................

..................................................................................................18-3 Table 18-3 Applicable versions........... 18-11 Table 18-7 Script for configuring the processing for SMS notification for call failure .............................................................................................................................................18-10 Table 18-5 Script for setting MAP parameter .....................18-3 Table 18-4 Script for querying the License............ 18-11 Table 18-6 Script for adding the content of SMS notification for call failure ............ 18-11 iv Huawei Technologies Proprietary Issue 02 (2007-06-10) ........................................................................................Tables HUAWEI MSOFTX3000 Feature Description Tables Table 18-1 Benefits of SMS notification for call failure ...........................................................................................................................................................................................................18-2 Table 18-2 Requirements for NEs ..............

18.3 Working Principle 18. Describes The function code. The functions of the NEs.4 Service Flow 18. function definition of this feature. The network elements (NEs) that are required for the feature. and the benefits that carriers and mobile subscribers can obtain from this feature. The data configurations that are required on the MSOFTX3000 and the UMG8900.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-1 .2 Availability 18.1 Service Description 18.8 Service Interaction 18. and the version requirements of the NEs. and networking requirements. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature.7 Charging and Charging Data Record (CDR) 18.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature 18 Section SMS Notification for Call Failure Feature About This Chapter The following table lists the contents of this chapter. whether Licenses are required. The service flow of the network when providing this feature. and the acronyms and abbreviations of this chapter.5 Data Configuration 18. The protocols and specifications that this feature must comply with. The relationships and restrictions between this feature and other services or features. The charging and the generation of CDRs when the network provides this feature.6 Service Management 18.

SMS notification for call failure is a network level service. which improves the customer satisfaction. 18.1 Service Description 18. When there is a missed call. calling number.3 Benefits Table 18-1 lists the benefits of SMS notification for call failure. the former mode is adopted.1. The service can be provided in two modes: The subscribers do not need to subscribe to the service in the HLR. Subscribers can clearly learn the specific causes of the missed call. 18. At present.2 Definition SMS notification for call failure informs the callee of missed calls by sending the Short Message (SM). date and time of the call.1. the network triggers the service: The callee switches off. Table 18-1 Benefits of SMS notification for call failure Beneficiary Carrier Description SMS notification for call failure is a kind of compensation service that provides more compensation measures for subscribers when they cannot answer the call. Notification messages are edited according to the type of call failure. which increases the service profit. The callee is unreachable.1 Function Code The SMS notification for call failure does not have a function code. The callee does not answer the call. the network sends an SM to inform the callee of the date. If the following exception occurs. 18-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The callee is busy.18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description 18. time and calling number of the missed call. It can reduce the loss resulted from missed calls. The subscribers subscribe to the HLR. Subscribers can clearly learn the specific causes of missed calls. There is no limit on the number of subscribers.1. The carriers charge the subscribers with certain amount of fees. Mobile Subscriber SMS notification for call failure provides one more choice of compensation service for subscribers. The service is free of charge.

HLR and SMSC. Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-3 .2. The Gateway Mobile Switching Center (GMSC) or Visited Mobile Switching Center (VMSC) provides the following functions: Processing signaling.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature 18. Table 18-2 Requirements for NEs UE/MS √ Node B/BTS √ RNC/BS C √ MSC Server √ MG W SMSC √ VLR √ HLR √ The symbol √ indicates that the NE is required.2. Analyzing data.1 Functions of Each NE Three NEs are involved in the SMS notification for call failure service: MSC.2 Availability 18.3 Applicable Versions Table 18-3 lists the versions of the Huawei CN products that support SMS notification for call failure.2.1 Requirements for NEs Table 18-2 gives the required network elements (NEs) for SMS notification for call failure service. The service can be provided only when the corresponding License is obtained. Table 18-3 Applicable versions Product MSC server MSOFTX3000 Applicable Version V100R005 and later versions 18. 18. Editing and sending notification messages for call failure. 18.3.2 Requirements for License SMS notification for call failure is an optional attribute of Huawei wireless core network.3 Working Principle 18.

After the call is routed to the VMSC. the processing flow of SMS notification for call failure is classified into two types: GMSC Triggers SMS Notification for Call Failure. the VMSC detects that the callee switches off or is not allowed to roam. the former collides with the latter two services. to complete preparation for triggering the service. It can be triggered only when both call forwarding and voice mailbox are not activated. the VMSC detects that the network encounters congestion. that is. After the call is routed to the VMSC. 18-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . According to triggering places. call forwarding and voice mailbox compensate for the loss resulted from the call missing.3. it triggers SMS notification for call failure. the HLR sends the information that the subscriber is absent in the SRI ACK message to the GMSC. deleted in the VMSC or unreachable). 18. when the callee cannot answer the call. SMS notification for call failure is triggered when the following exception occurs: The GMSC detects in the SRI message that the callee is absent. there is no paging response or the response times out. SMS notification for call failure. After the call is routed to the VMSC.18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description If the callee is absent in the call (turnoff. After the call is routed to the VMSC. GMSC Triggered SMS Notification for Call Failure If the GMSC detects that the callee is absent. roaming not allowed. the callee does not answer the call. the VMSC detects that the callee is busy. The Short Message Service Center (SMSC) receives and sends the call failure SM. VMSC Triggers SMS Notification for Call Failure. However.2 Internal Processing SMS notification for call failure is triggered at every abnormal point during a call. After the call is routed to the VMSC. The processing flow is as shown in Figure 18-1.

5. 6. the VMSC detects that the callee switches off or the roaming is not allowed. 4. After the call is routed to the VMSC. there is no paging response or the response times out. 3. and sends the MO FORWARD SM ARG message to the SMSC. The GMSC triggers SMS notification for call failure. The GMSC sends the MAP SRI REQ message to the HLR of the callee. The SMSC returns MO FORWARD SM RES message to the GMSC.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature Figure 18-1 Processing flow of SMS notification for call failure triggered in the GMSC MS (V)MSC SETUP IAM (G)MSC HLR SMSC MAP_SEND_ROUTING_INF O_REQ MAP_SEND_ROUTING_INF O_CNF MO_FORWARD_SM_ARG MO_FORWARD_SM_RES The processing flow is as follows: 1. The HLR then sends the information to the GMSC in the MAP SRI CNF message. the callee does not answer the call. The VMSC sends the IAM message to the GMSC. the VMSC detects that the callee is busy. the VMSC detects that the network encounters congestion. VMSC Triggered SMS Notification for Call Failure The VMSC triggers SMS notification for call failure when the following exception occurs: After the call is routed to the VMSC. After the call is routed to the VMSC. Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-5 . edits the content of the message. After the call is routed to the VMSC. The processing flow is as shown in Figure 18-2. The Mobile Station (MS) sends the SETUP request to the VMSC of the MS. 2. If the HLR detects that the callee is absent. After the call is routed to the VMSC.

For more information. In most cases.4 Service Flow SMS notification for call failure is mainly used to compensate for abnormal situations in call service. If the MS does not answer the call after alerting. the following must be met: The callee does not subscribe to the forwarding service. The subsequent flow after triggering is almost the same. 6. 4. 5.1 Prerequisites for Service Triggering To trigger this service.4. After receiving the PAGING response. 18. If the VMSC detects that the callee is busy. If the conditions in 2 and 3do not happen. SMS notification for call failure is triggered in the VMSC. the VMSC triggers the SMS notification for call failure. 8. If the MS does not reply to the PAGING or the PAGING response times out. If the wireless channel is congested and thus channel assignment fails. 7. it triggers SMS notification for call failure. the VMSC triggers the SMS notification for call failure. the VMSC sends PAGING to the MS. the VMSC sends the SETUP message to the MS and sends channel assignment request to the MGW. 3. 18-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . 18. see Figure 19-5. 2. If the VMSC detects that the callee switches off or is not allowed to roam.18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description Figure 18-2 Processing flow of SMS notification for call failure generated in the VMSC (G)MSC (V)MSC RNC/BSC MS IAM PAGING PAGING SETUP SETUP The processing flow is as follows: 1. The callee does not subscribe to the voice mailbox. it triggers SMS notification for call failure. the VMSC triggers the SMS notification for call failure. The GMSC sends the IAM request to the VMSC of the callee according to the Mobile Station Roaming Number (MSRN).

The processing flow is as follows: 1. Service Triggering Point in the VMSC The triggering points of SMS notification for call failure in the VMSC are as shown in Figure 18-4: Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-7 . Then the GMSC triggers SMS notification for call failure service. 18. The triggering point is as shown in Figure 18-3. Figure 18-3 Triggering point of SMS notification for call failure in the GMSC (G)MSC HLR MAP_SEND_ROUTING_INFO_REQ MAP_SEND_ROUTING_INFO_CNF The callee is absent. The HLR sends the information that the callee is absent to the GMSC in the MAP SRI CNF message.2 Service Triggering Point Service Triggering Point in the GMSC The GMSC receives the SRI ACK message from the HLR and detects that the callee is absent. The CPU is not overloaded. The GMSC and VMSC activate the SMS notification for call failure service.4.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature The GMSC and VMSC apply for the License of SMS notification for call failure. The GMSC triggers the SMS notification for call failure when receiving the information that the callee is absent. 2. The GMSC sends the MAP SRI REQ message to the HLR of the callee. 3.

If conditions in Step 2 and Step 3 do not happen. If the wireless channel is congested and channel assignment fails. 5. skip to Step 9. The network is busy. skip to Step 9. PAGING There is no response to the PAGING message. skip to Step 9. When receiving the PAGING response. the VMSC sends the SETUP message to the callee and sends channel assignment request to the MGW. 2. 4. If the VMSC detects that the callee is busy. 6. skip to Step 9. SETUP Wireless channel is congested. 18-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The processing flow is as follows: 1. 7. 9. The GMSC sends IAM message to the VMSC. 3. The callee does not reply. If the callee does not answer the call after alerting. The VMSC triggers the SMS notification for call failure. 8. If the VMSC detects that the callee switches off or is not allowed to roam. PAGING response times out.3 Processing Flow After Service Triggering The processing flow of the MSC after triggering the SMS notification for call failure is shown in Figure 18-5. 18. skip to Step 9. the VMSC sends the PAGING message to the callee.18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description Figure 18-4 Triggering point of SMS notification for call failure in the VMSC (G)MSC IAM (V)MSC RNC/BSC The callee switches off or roaming not allowed.4. If there is no PAGING response or the PAGING response times out.

MO_FORWARD_SM ACK SEND_ROUTING_INFO_F OR_SM SEND_ROUTING_INFO_F OR_SM ACK MT_FORWARD_SM PAGING PAGING PAGING ACK PAGING ACK CP_DATA CP_DATA CP_DATA ACK CP_DATA ACK MT_FORWARD_SM ACK The processing flow is as follows: 1. Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-9 . The SMSC sends the MT FORWARD SM request to the VMSC according to the routing information returned by the HLR. After receiving the response message that the MS has received the short message content. The SMSC receives the SM and sends the response message to the GMSC or VMSC. 5.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature Figure 18-5 Processing flow after SMS notification for call failure is triggered MS RNC/BSC (G/V)MSC SMSC HLR MO_FORWARD_SM Trigger SMS notification for call failure. The VMSC receives Paging ACK message from the MS. the VMSC sends the PAGING request to the MS. 2. 8. After receiving the MT FORWARD SM request. the GMSC or VMSC sends it to the SMSC. 7. The SMSC sends SRI FOR SM message to the HLR of the callee to require the routing information of the callee. the VMSC sends MT FORWARD SM ACK to the SMSC. and sends the content of the SM to the MS. 4. After editing the SM for call failure. 3. The HLR sends the routing information of the callee (the number in the VMSC) to the SMSC. 6.

including the supported call failure type. address of the SMS.5. DSP LICENSE:.2 Data Configuration Sample Scenario 1 Subscriber A dials B. format of call failure date and time. Step 3 Run ADD SMCONT to edit the content of SM for call failure. run SET MAPPARA to enable it. If not. Configuration Script The steps for configuring data in the GMSC of subscriber A are as follows: Step 1 Query the License. the GMSC of A triggers the SMS notification for call failure service. Step 4 Run ADD CFSMSPRO to add the related call failure data for a certain callee. ----End 18. Then run LST CFSMSPRO to query the result. If B switches off.5. apply for one and run LOD LICENSE to load the file of License that supports this service.5 Data Configuration 18. If not. If the loaded License does not support the SMS notification for call failure service. Then run LST SMCONT to query the result.1 Data Configuration on the MSOFTX3000 To configure the data of SMS notification for call failure service. including coding scheme. perform the following steps: Step 1 Run DSP LICENSE to check whether there is a License that supports SMS notification for call failure. load the License that supports this function. calling number (the number at the network side) and SM content index. Step 2 Run LST MAPPARA to check whether the function of SMS notification for call failure is enabled. Table 18-4 Script for querying the License Description Script Note Query the License to check whether it supports the SMS notification for call failure service. 18-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) .18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description 18.

CFDATEFMT=YMD. It is opposite to withdrawing the service. SMVT=H12.6 Service Management The service management of SMS notification for call failure includes: Providing: The carriers perform operations to enable the service for the subscribers. Step 3 Add the content of SMS notification for call failure. SRVCTR=K'8613900007555. SCNAME="A". TCID=K'8613907550463. CSCH=BIT7. ADD SMCONT: SCNAME="A". Step 4 Configure the processing for SMS notification for call failure. unreachable. Deregistering: The carriers delete the related information of the subscribers. Table 18-5 Script for setting MAP parameter Description Script Set MAP parameter to enable the SMS notification for call failure function. ADD CFSMSPRO: CFT=POFF-1&NR-1&BUSY-1&NA-1. the callee busy and no answer) for a subscriber.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature Step 2 Set MAP parameter. For example. Registering: The carriers perform operations in the GMSC or VMSC to make the service executable. SET MAPPARA: SUPCFSMSIND = YES. CONTENT="You have an incoming call from". Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-11 . Note ----End 18. Table 18-6 Script for adding the content of SMS notification for call failure Description Script Add the content of SMS notification for call failure. OCID=K'1860. The service is activated during the registration. CFTIMEFMT=H24. Table 18-7 Script for configuring the processing for SMS notification for call failure Description Script Configure the processing for SMS notification for call failure. Withdrawing: The carriers perform operations to disable the service for the subscribers. The processing configuration is intended for subscriber B. they configure the related data information in SMS notification for call failure of certain type (switch off. There is no need to perform other operations. It is opposite to registering.

----End 18-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Step 3 Run LST MAPPARA to query whether the GMSC or VMSC supports the SMS notification for call failure service. Step 4 Run ADD CFSMSPRO to add related data of the designated subscriber to complete the registration with the service for the subscriber. withdraw. that is. set the parameter Support call failed SM indication to TRUE. register and deregister the service through the GMSC and VMSC maintenance console. that is. send specific content to the callee when the call fails.1 Operations by Carriers The carriers can provide. Step 2 Run SET MAPPARA to withdraw the SMS notification for call failure service.18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description 18. that is. Step 4 Run SET MAPPARA to provide the SMS notification for call failure service.6. ----End Deregistering Step 1 Run LST CFSMSPRO to query the configuration of SMS notification for call failure. Providing Step 1 Run DSP LICENSE to query whether the License supports the SMS notification for call failure service. Step 2 Run ADD SMCONT to add the content of SM for call failure. ----End Registering Step 1 Run LST SMCONT to query the setting of SM content for call failure. If it does. Step 2 Run RMV CFSMSPRO to delete related data of the designated subscriber to cancel the registration with the service for this subscriber. skip to Step 3. Step 3 Run LST CFSMSPRO to query the configuration of SMS notification for call failure. Step 2 If the License does not support the service. to set the parameter Support call failed SM indication to FALSE. run LOD LICENSE to load the License of SMS notification for call failure. ----End Withdrawing Step 1 Run LST MAPPARA to query whether the GMSC or VMSC supports the SMS notification for call failure service.

18.2 CDR of the SMMT The Short Message Mobile Terminated (SMMT) flow of SMS notification for call failure is the same as the common SMMT flow. 18. no CDR of Short Message Mobile Originated (SMMO) is provided. Therefore. The common ground is that the service triggering points are the same. they do not charge for the service. That is. Therefore. For example. Issue 02 (2007-06-10) Huawei Technologies Proprietary 18-13 . 18.8. It differs from common SMS in that: common SMS is originated by the MS while the SMS notification for call failure is originated by the network. B will receive the SM for call failure and the ordinary CDR is generated.3 Charging The carriers decide whether to charge for SMS notification for call failure. and the latter enjoys higher priority. the CDR of SMMT is the same as that of ordinary SMMT.8. 18.2 SM Service SMS notification for call failure is realized in the form of SMS. SMS notification for call failure cannot be enabled. the subscriber can enjoy this service without performing any operation. 18.2 Operations by Subscribers As long as the carrier provides and registers with the SMS notification for call failure for the subscriber in the GMSC or VMSC.3 Call Forwarding Service SMS notification for call failure conflicts with the forwarding service.HUAWEI MSOFTX3000 Feature Description 18 SMS Notification for Call Failure Feature 18. if the call forwarding service is activated.7.6.7 Charging and Charging Data Record (CDR) 18. 18. if A calls B and the call fails.8.7.8 Service Interaction This section introduces the interaction of SMS notification for call failure with other services. At present. 18. The SMMT flows are the same.1 CDR of the SMMO SMS notification for call failure is originated at the network side.1 Call Service The SMS notification for call failure is triggered when exception occurs during a call.7.

18 SMS Notification for Call Failure Feature HUAWEI MSOFTX3000 Feature Description 18. SMS notification for call failure cannot be enabled. if the voice mailbox is activated. 18.2 Aronyms and Abbreviations Acronym/Abbreviation HLR IAM MS SMSC SMMO SMMT VLR Full Name Home Location Register Initial Address Message Mobile Station Short Message Service Centre Short Message Mobile Originated Short Message Mobile Terminated Visitor Location Register 18-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) .9 Reference 18.4 Voice Mailbox Service SMS notification for call failure conflicts with voice mailbox service.8.9.1 Protocols and Specifications None. That is.9. 18. The common ground is that the service triggering points are the same. and the latter has higher priority.

...............................................................................................1......................19-3 19..............19-6 19.....................................19-2 19.................6 Service Interaction ...................................7.............................................................................................2 Acronyms and Abbreviations ........19-5 19....................1 Function Code.....19-5 19....................................................................................................................................2.....................................19-1 19..7................................................................................................1 Requirement for NEs ...........................................................................................................19-3 19..1 Feature Description ................................................3 Benefits ....19-3 19.........................................................................................................7 Reference ..................................................................................................2 Requirement for License...........................1 Data Configuration for the MSOFTX3000 ..............................19-8 19.......................4 Data Configuration....................................................19-8 Issue 02 (2007-06-10) Huawei Technologies Proprietary i .....................................................3 Applicable Versions..............2 Definition ...........................................................1 Protocols and Specifications ..........19-2 19.............................1..........................................2 Example ....19-7 19...............................................................................19-4 19..............................19-8 19..................................................................................19-3 19...................................5 Charging and CDR .....................................HUAWEI MSOFTX3000 Feature Description Contents Contents 19 Summer Time Feature of Wireless Time Zone .................1..........................................................4...........................................................................2.............................................................19-2 19.....................................4..........................3 Working Principle.............................................................2........................................................................19-8 19.........................................................................................................................................2 Availability ...........................................................................................................19-3 19...........

...19-4 Figure 19-2 Time icon of Windows2000 operating system................ BAM server.......................19-6 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ...........19-5 Figure 19-3 Adjusting clock for daylight saving changes ............................................................................................ and the host................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 19-1 Synchronization relationship between the NTP server.......

...........................19-2 Table 19-2 NEs related to the summer time feature of the wireless time zone.....................................19-5 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii .................................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 19-1 Name and function code of the summer time feature ...........................19-3 Table 19-4 Alarms related to summer time.................................................19-3 Table 19-3 Versions that support the summer time feature of the wireless time zone .......................................................

and networking requirements. and the acronyms and abbreviations of this chapter.3 Working Principle 19. function definition of this feature. The data configurations that are required on the MSOFTX3000 and the IMG8900.5 Charging and CDR 19.HUAWEI MSOFTX3000 Feature Description 19 Summer Time Feature of Wireless Time Zone 19 Section Summer Time Feature of Wireless Time Zone About This Chapter The following table lists the contents of this chapter.4 Data Configuration 19. The protocols and specifications that this feature must comply with.1 Feature Description 19. and the benefits that carriers and mobile subscribers can obtain from this feature. and the version requirements of the NEs. The functions of the NEs. The charging and the generation of CDRs when the network provides this feature. 19.7 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 19-1 . Describes The function code.2 Availability 19. whether Licenses are required. The network elements (NEs) that are required for the feature.6 Service Interaction 19. The relationships and restrictions between this feature and other services or features.

The time zone boundaries are geographic longitudes in principle.1. most of the countries use the standard time with the unit zone time. The GMT+14 time zone overlaps with the GMT-12 time zone. still use the local time of the capital or some important commercial ports as the standard time. the surface of the earth is divided into 14 and 12 time zones respectively. which is also called daylight saving time.19 Summer Time Feature of Wireless Time Zone HUAWEI MSOFTX3000 Feature Description 19. the surface of the earth is longitudinally divided into 26 time zones. thus the expenditure on lighting and electricity is reduced. however. the offset between the standard time of these countries and that of the GMT is in precision of minute. the eastern standard time 10:00 am.1 Function Code Table 19-1 lists the name and function code of the summer time feature. during the summer time. and every neighboring two time zones observe a clock time one hour offset (some neighboring time zone offsets are 30 minutes or 15 minutes). Thus. The application of summer time makes full use of the sunshine and saves fuels and electricity. you can observe sunrise from the east part and the west part respectively within one hour.5 (with a width of 15).2 Definition Concept of Time Zone The world time zones are divided based on the prime meridian. The standard time has hour(s) offset from the GMT. From the initial zone eastward and westward. For example.1. becomes the eastern summer time 11:00 am. and that we can set out clock backward so that the daylight time can be prolonged. The initial time zone covers the west 7. He points out that the day breaks earlier in summer. about 70 countries including Europe and North American countries have implemented the summer time.1 Feature Description 19. Concept of Summer Time Summer time is a lawfully defined time. they are substituted by the regional boundaries or natural boundaries for easy application. In most of the countries that use the summer time. It is first proposed by the American inventor and politician Benjamin Franklin. At present.5 to east 7. Currently. however. 19-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . Table 19-1 Name and function code of the summer time feature Name Summer time feature of wireless time zone Code None 19. the summer time is usually one hour (it varies with different countries) later than the standard time. In this way. Some countries. In the same time zone. In actual practice.

Table 19-3 Versions that support the summer time feature of the wireless time zone Product MSC Server MSOFTX3000 Applicable Versions V100R005 and the later versions Issue 02 (2007-06-10) Huawei Technologies Proprietary 19-3 . thus the subscribers can enjoy the services more conveniently. Mobile subscriber 19.2.2 Requirement for License Summer time feature of the wireless time zone is a basic feature of the Huawei wireless core network. 19.2.2 Availability 19. The services provided by the carrier comply with the time habit of the subscribers. Table 19-2 NEs related to the summer time feature of the wireless time zone UE/MS √ NodeB/ BTS √ RNC/BSC √ MSC Server √ MGW – SGSN – VLR √ HLR √ √ stands for the related NEs.3 Applicable Versions Table 19-3 lists the Huawei UMTS RAN product versions that support the summer time feature of the wireless time zone. 19. the carriers can configure the system time of the MSOFTX3000 to accommodate all the services to the summer time.1.1 Requirement for NEs The summer time feature of the wireless time zone requires the corporation of the MSC server and the HLR. Table 19-2 lists the NEs related to the summer time feature of the wireless time zone.HUAWEI MSOFTX3000 Feature Description 19 Summer Time Feature of Wireless Time Zone 19.3 Benefits Beneficiary Carrier Description In those regions that use the summer time.2. You can obtain this service without any license.

3 Working Principle The configuration of the time zone and summer time only requires the modification of the local time. the local time of the BAM changes to 08:00:00 immediately. and the host NTP server GM T ne zo e er tim m s t um ho d s ift e n fy th e a s h cti t y re hos tif ang time ly No c h a l th e dic of 1 rio e Pe tim e 2 th Host Time informaton: (BAM Loacal time + time zone+ summer time offset) BAM When modifying the time zone configuration of the BAM server. The NTP synchronization. the configuration of the time zone and summer time does not affect the NTP service. uses only the Greenwich Mean Time (GMT) without involving the time zone and summer time. BAM server.19 Summer Time Feature of Wireless Time Zone HUAWEI MSOFTX3000 Feature Description 19. Therefore. Then the BAM server sends the modified time zone and local time to the host at once. the BAM performs automatically time synchronization with the NTP server if it is in normal communication with the NTP server. Then the BAM server adjusts the local time according to the configuration of the summer time. If the BAM is not configured with an effective NTP server. The BAM server adjusts the local time directly according to the configuration of the summer time. When it reaches the summer time shift point (the beginning time point or the end time point of the summer time). which exerts no impact on the configuration of the BAM time zone and summer time. the BAM does not perform time synchronization with the NTP server. Figure 19-1 Synchronization relationship between the NTP server. the local time of the BAM server is set according to the synchronization mode between the BAM server and NTP server: If the BAM is configured with an effective NTP server. the NTP server can only rectify the GMT of the BAM server. the local time of the system in which the BAM resides changes accordingly. In the following example. if: GMT is 00:00:00 Time zone of the BAM is GMT+7 Local time of the BAM is 07:00:00 If you set the time zone of the BAM to GMT+8 by using the command SET TZ. however. 19-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . or the BAM is disconnected with all the NTP servers. On the other hand. The configuration of the time zone and summer time is managed only by the BAM server itself. as shown in Figure 19-1.

If it is in the summer time. Therefore. unselect Automatically adjust clock for daylight saving changes if is selected. you need to shut down the automatic summer time adjusting of the Windows2000 operating system in which the BAM resides. as shown in Figure 19-3. the consistency between the time of the BAM sever and that of the host and the implementation of the MSOFTX3000 summer time will be affected. To shut down the automatic summer time adjusting of the Windows2000 operating system.4 Data Configuration 19. Table 19-4 lists the detailed alarm information. and then select the correct time zone from the drop-down list. Otherwise. In addition. for example. Table 19-4 Alarms related to summer time Alarm Number 836 837 Alarm Type Event Event Alarm Name Enter daylight saving time Leave daylight saving time Cause The BAM enters the summer time. a DST is suffixed to indicate the summer time. 19. and the summer time with the host. when it reaches the summer time shift point.4. Figure 19-2 Time icon of Windows2000 operating system Step 2 In the Time Zone tab.HUAWEI MSOFTX3000 Feature Description 19 Summer Time Feature of Wireless Time Zone Once the local time is adjusted. time zone. Click Apply and then OK. Issue 02 (2007-06-10) Huawei Technologies Proprietary 19-5 . When in summer time. the BAM server synchronizes immediately the local time. The BAM leaves the summer time. The BAM server also notifies the service processes the summer time. the BAM server raises the "Enter daylight saving time" or "Leave daylight saving time" alarm. when activating the summer time function of the MSOFTX3000. as shown in Figure 19-2.1 Data Configuration for the MSOFTX3000 Preparation The implementation of the summer time of the MSOFTX3000 is totally independent of the summer time function of the Windows2000. the MML message head contains the summer time information. do as follows: Step 1 Double-click the time icon at the bottom right of the Windows2000 system interface. 2006-03-21 15:25:58 DST.

19 Summer Time Feature of Wireless Time Zone

HUAWEI MSOFTX3000 Feature Description

Figure 19-3 Adjusting clock for daylight saving changes

----End

Procedure
To perform data configuration, do as follows: Step 1 Check the configuration information of the BAM time zone and summer time by using the command LST TZ. Step 2 Configure the time zone and summer time of the BAM server by using the command SET TZ. ----End

19.4.2 Example
Scenario
The BAM server is in GMT-6, and the country in which the BAM server resides uses the summer time. The rule for implementing the summer time is as follows: In the wee hours of the last Sunday of every March, set the clock one hour forward when it shifts from the non-summer time to summer time. In the wee hours of the last Sunday of every October, set the clock one hour backward when it shifts from the summer time to non-summer time.

19-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

19 Summer Time Feature of Wireless Time Zone

Scripts for Configuration
To perform data configuration for time zone and summer time, do as follows: Step 1 Set the time zone and summer time. Description Script Setting the time and summer time. SET TZ: ZONET=GMT-0600, DST=YES, SM=WEEK, SMONTH=MAR, SWSEQ=LAST, SWEEK=SUN, ST=00&00&00, EM=WEEK, EMONTH=OCT, EWSEQ=LAST, EWEEK=SUN, ET=00&00&00, TO=60;

Step 2 Query the time zone and summer time. Description Script Querying the time zone and summer time. LST TZ:;

----End

19.5 Charging and CDR
The MSOFTX3000 supports configuration of time zone and summer time through the MML commands. The time zone and summer time, however, have different influence on the call detail record (CDR), alarms, and logs. After the operator configures the BAM time zone by using the MML command, the host records the time zone information for each gateway or trunk group only in the gateway data table or trunk data table. This time zone affects only the absolute time in the CDR, such as the callee answering time, callee terminating time, call establishing time, wireless channel assigned time, and ringing time. The time adjusting principle for charging and CDR is as follows: If the call is paid by the calling party, the system adjusts the time segment in the CDR based on the time zone of the calling party. If the call is paid by the called party, the system adjusts the time segment in the CDR based on the time zone of the called party. That is, the talk time and charging are not affected by the BAM time change caused by the change of the time zone. If the time zone changes during the call session, the callee answering time, callee terminating time, call establishing time, wireless channel assigned time, and ringing time are affected. After the operator configures the summer time of the BAM server through the MML command, the BAM time is adjusted immediately if it reaches the summer time shift point. The BAM then sends the adjusted time and the summer time offset to the host for synchronization. Therefore, the configuration of the summer time affects the absolute time in the CDR, alarms, and logs. Once the summer time starts, there will be a blank area in the local time of the NE. On the contrary, when the summer time ends, there will be an overlapped area in the local time of the NE. Therefore, relevant processing is required for traffic statistics, CDR, and the charging

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

19-7

19 Summer Time Feature of Wireless Time Zone

HUAWEI MSOFTX3000 Feature Description

system that uses the local time. Take the traffic statistics for example, when there is an overlapped area in the local time, the traffic of the overlapped time area will be accumulated. In this way, the traffic statistics of the overlapped area is counted. For the traffic statistics and charging of different time zones, if the local time is involved, you need to convert the time of different time zones according to the local time and the summer time.

19.6 Service Interaction
The settings of the time zone and summer time affect the network management services. If the summer time starts or the time zone changes, the BAM system time shifts accordingly. This shift, however, is only reflected in the local time and it does not affect the GMT, that is, the time controller of the network management system is not affected. The network management system can query the time zone and summer time information of a certain NE by using commands, and then calculates the local time of the NE according to the time zone and summer time of the NE. The network management system delivers tasks to the NE based on the local time of the NE. On the other hand, the network management system can also convert the local time contained in the reported messages by the NE to the local time of the network management system or the GMT according to the time zone and summer time of the NE.

19.7 Reference
19.7.1 Protocols and Specifications
None.

19.7.2 Acronyms and Abbreviations
Acronym/Abbreviation BAM GMT HLR MML NTP VLR Full Name Back Administration Module Greenwich Mean Time Home Location Register Human-Machine Language Network Time Protocol Visitor Location Register

19-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
20 Version Software Management Feature ............................................................................20-1
20.1 Service Description ...................................................................................................................................20-2 20.1.1 Function Code..................................................................................................................................20-2 20.1.2 Definition .........................................................................................................................................20-2 20.1.3 Benefits ............................................................................................................................................20-2 20.2 Availability ................................................................................................................................................20-2 20.2.1 Requirements for NEs......................................................................................................................20-2 20.2.2 License Support ...............................................................................................................................20-3 20.2.3 Applicable Version ...........................................................................................................................20-3 20.3 Working Principle......................................................................................................................................20-3 20.4 Patch Operation Flow................................................................................................................................20-4 20.5 Data Configuration....................................................................................................................................20-6 20.5.1 Data Configuration at the MSOFTX3000........................................................................................20-6 20.5.2 Data Configuration at the UMG8900 Side.......................................................................................20-8 20.6 Service Management .................................................................................................................................20-8 20.6.1 Uploading Patch to The M2000 Server............................................................................................20-9 20.6.2 Operating Patch..............................................................................................................................20-10 20.7 Charging and CDR ..................................................................................................................................20-12 20.8 Service Interaction ..................................................................................................................................20-12 20.9 Reference ................................................................................................................................................20-12

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

i

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 20-1 Patch operation flow .....................................................................................................................20-5

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 20-1 Network elements concerning with version software management features ..................................20-3 Table 20-2 Applicable versions for the version software management features ...............................................20-3 Table 20-3 MML command table for patch management.................................................................................20-7

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

20
About This Chapter
Section

Version Software Management Feature

The following table lists the contents of this chapter. Describes The function code, function definition of this feature, and the benefits that carriers and mobile subscribers can obtain from this feature. The network elements (NEs) that are required for the feature, whether Licenses are required, and the version requirements of the NEs. The functions of the NEs, and networking requirements. The service flow of the network when providing this feature. The data configurations that are required on the MSOFTX3000 and the IMG8900. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The charging and the generation of CDRs when the network provides this feature. The relationships and restrictions between this feature and other services or features. The protocols and specifications that this feature must comply with, and the acronyms and abbreviations of this chapter.

20.1 Service Description

20.2 Availability

20.3 Working Principle 20.4 Patch Operation Flow 20.5 Data Configuration 20.6 Service Management

20.7 Charging and CDR 20.8 Service Interaction 20.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-1

20 Version Software Management Feature

HUAWEI MSOFTX3000 Feature Description

20.1 Service Description
20.1.1 Function Code
Function Name Version software management features Function Code None.

20.1.2 Definition
The software management is a feature in the operation and maintenance field. That is, through the operation and maintenance center or the network management, the following functions can be realized: Manage the version software and data configuration of network elements within the dominated field Realize the lot-size transmission, loading and activation of program and data configuration Therefore, the efficiency and quality of the system maintenance and network element management can be greatly improved.
The version adaptation for software management must be considered. The feature introduces how to load hot patch for the system when the MSOFTX3000 is managed by the M2000 uniformly.

20.1.3 Benefits
Beneficiary Carrier Description Through the maintenance center software and network management software, the carrier can transmit, upload and activate the lot-size files; therefore, the operation efficiency of upgrading, data uploading is improved. Besides, through version identification, the operation quality is also greatly improved. None.

Mobile subscriber

20.2 Availability
20.2.1 Requirements for NEs
The MSC server and the M2000 are required to complete the version software management features, as listed in Table 20-1.

20-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

Table 20-1 Network elements concerning with version software management features UE/ MS Node B/BTS RNC/ BSC MSC Server √ MGW M2000 √ SGSN GGSN HLR -

√ indicates the network elements involved.

20.2.2 License Support
Version software management features are the basic feature of HUAWEI wireless core network, of which services can be obtained without getting License requirement.

20.2.3 Applicable Version
The applicable versions of version software management features for HUAWEI core network (CN) products are as listed in Table 20-2. Table 20-2 Applicable versions for the version software management features Product MSC Server MSOFTX3000 Applicable Version V100R005 and subsequent versions

20.3 Working Principle
The MSC server cooperates with the M2000 to realize the version software management features. M2000: delivers the commands of transmission, uploading and activation and data information to the managed NEs. MSC Server: accepts and checks the commands and the data sent by the M2000; therefore, the auto upgrading of version software can be realized. The functions of the NEs are as follows: Main Control Board : System control and communication is the main control system to realize the features. It serves as a BAM in the MSOFTX3000, while in the text, it is called the main control board. File Downloading : It indicates that the NEs obtain the data from the file server through FTP. File Uploading : It indicates that the data are transmitted to the file server from the NEs. Patch : There are two patches, hot patch and cold patch. The differences between them are listed as follows:
− −

Hot patch is the on-line effective patch and you do not need to reinstall the board program. Cold patch is the reset board and is valid only after you load the board program.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-3

20 Version Software Management Feature

HUAWEI MSOFTX3000 Feature Description

The text does not cover the upgrading process of cold patch. Therefore, if there are no special descriptions, the patch is a hot patch.

Hot Patch : Hot patch, a software program entity, adopting software tailor and programming technology, can load and unload files independently on the base of original version by the independent background or independent install files or file copy. The patch is composed of one or more changes. The original program may be affected after patch loading. The hot patch is realized by on-line effective technology. The tool for making patch creates patch files based on the target files complied by the source code. The patch management modules then operate on the patch files to realize the patch management. Cold Patch : Hot patch can not modify some problems; hence, the board software is required to be reloaded. On this occasion, you can use cold patch to repair the system. Board Locating Parameter : In the commands introduced in the text, patch type, module number or active/standby module information are the parameters for locating board.

20.4 Patch Operation Flow
The patch operation flow is shown in Figure 20-1.

20-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

Figure 20-1 Patch operation flow
M2000 DLD PATCH MSOFTX3000 returns the progress report to the M2000 MSOFTX3000 reports sucesss or failure to the M2000 LOD PATCH Load the patch to specified board MSOFTX3000 reports sucess or failure to the M2000 ACT PATCH MSoftX3000 reports success or failure to the M2000 CON PATCH MSOFTX3000 reports sucess or failure to the M2000 Confirm the patch of specifie board Activate the patches of specified boards and make them effctive MSOFTX3000 File server

MSOFTX3000 downloads patch files from file server

DEA PATCH MSOFTX3000 reports sucess or failure to the M2000

Deactivate the patch of specified board

Patch version upgrade does not cause out of service and has a minor impact on the system; therefore, it is an important method of upgrading version during equipment maintenance. The key problem of patch upgrading is the convenient operation for maintenance staffs during upgrading process. You can complete the upgrading after ensuring the correctness of patch version and you also can roll back when finding abnormal conditions. To upgrade patch, perform the following steps: Step 1 Observe the patch status. As the equipment is used in the network for a long time, the status of current patch loaded may be not archived, or the archived information is not correct. Whether the patch version for upgrading can be loaded is closely related to the current patch status; therefore, it is essential to observe the current patch status of system. You can observe the current patch status by using the commands based on the system, subrack, board type and board. You can observe the patch status when patches are in the state of loading, activation and default. Step 2 Load a patch. Patch loading indicates that after the M2000 deliverers the patch loading commands. The MSOFTX3000 loads the patch files downloaded to the BAM system to the boards. After loading, the status of the new patch can be checked by using commands.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-5

20 Version Software Management Feature

HUAWEI MSOFTX3000 Feature Description

The system loads the corresponding patches for the boards based on the patch types. Patch files must match each version. Each type of board can only have one patch file while one patch file can contain many patch units. Step 3 Validate a patch. To validate the patch is to activate the patch. The patches are managed by the same patch management modules; hence, the patches on the same board can be validated at the same time but the patches on different boards can not. Therefore, the patches on different boards are validated in a certain sequence. The system observes the validated patch on a certain type of board for a period of time. If the running status meets the requirements of system, the patches of other boards are loaded. Therefore, the function validating patches based on the board type is required. Step 4 Cancel a patch.

When you cancel patches, the patches loaded are not validated due to board switchover and reset. Patch cancellation does not differentiate the active/standby boards. Patch cancellation can also be called patch deactivation and patch removal. The patch cancellation is required when the system is abnormal after the patch upgrading is completed. The methods of canceling the patch are listed as follows: Cancellation based on board Cancellation based on board type Step 5 Confirm a patch. Patch confirmation is to set the effective patch to the default patch. After the patch is effective for a period of time, if the system is running normally, update the patch and make the patch loaded to the current default patch. ----End

20.5 Data Configuration
20.5.1 Data Configuration at the MSOFTX3000
The MML command table of patch management is listed in Table 20-3.

20-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

Table 20-3 MML command table for patch management Number 1 2 3 4 Command Name DLD PATCH ULD PATCH LOD PATCH ACT PATCH Description To download the patch from the file server to the NEs. To upload the patch from the network elements to the file server. To download the patch from the main control board to the board loading patch. To active the patch and ensure that the patch is in active state. The active patch can be run but is still in the trial status. After the patch is on trial for a period of time, if it runs normally after confirmation, confirm the patch to switch to the stable running status from the trial running status. If the patch does not run normally, deactivate the patch to stop trial running. To deactivate the patch and ensure that the patch is in deactivated state You can deactivate the patch only at trial status. 6 CON PATCH RMV PATCH To confirm patch. The patch switches to the running status from the active state. Ensure that the patch is effective after restarting. To remove patch. After the patch is removed, if the patch is required to be run again, reload the patch. You can remove the patch at any status. To list the version and status information of each type of patch for network elements. To display the patch status information of each board for network elements.

5

DEA PATCH

7

8 9

LST PATCH DSP PATCH

For the usage of MML commands and the description of parameters, see MML online help of the LMT.

The usages of patch operation commands are listed as follows:

Input
If the patch files are to be loaded, The M2000 delivers DLD PATCH to the MSOFTX3000. The M2000 delivers LOD PATCH to the MSOFTX3000. The M2000 delivers ACT PATCH to the MSOFTX3000. The M2000 delivers CON PATCH to the MSOFTX3000.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-7

20 Version Software Management Feature

HUAWEI MSOFTX3000 Feature Description

If the activated patch files are to be deactivated, The M2000 delivers DEA PATCH to the MSOFTX3000. If the patch files loaded are to be removed, The M2000 delivers RMV PATCH to the MSOFTX3000.

Output
After the M2000 delivers DLD PATCH to the MSOFTX3000, The MSOFTX3000 downloads the patch files from the file server; The MSOFTX3000 reports the download progress (containing the start packet and end packet) to the M2000. If the download is incorrect, the MSOFTX3000 is required to report the failure mistakes and causes to the M2000. If the downloading is successful, the MSOFTX3000 is required to report the packets indicating the successful downloading to the M2000. After the M2000 delivers LOD PATCH to the MSOFTX3000, The MSOFTX3000 must load the patch to the corresponding boards. The MSOFTX3000 reports the success or failure packets to the M2000. After the M2000 delivers ACT PATCH to the MSOFTX3000, The MSOFTX3000 activates the patch of corresponding board. The MSOFTX3000 reports the success or failure packets to the M2000. After the M2000 delivers CON PATCH to the MSOFTX3000, The MSOFTX3000 confirms the patch of corresponding boards. The MSOFTX3000 reports the success or failure packets to the M2000. After the M2000 delivers DEA PATCH to the MSOFTX3000, The MSOFTX3000 is required to deactivate the patch of boards. The MSOFTX3000 reports the success or failure packets to the M2000. After the M2000 delivers RMV PATCH to the MSOFTX3000, The MSOFTX3000 must remove the board patch. The MSOFTX3000 reports the success or failure packets to the M2000.

20.5.2 Data Configuration at the UMG8900 Side
None.

20.6 Service Management
This section describes all patch operations on the M2000 interface.

The M2000 software management only supports the remote operations for MSOFTX3000 patches.

20-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

20.6.1 Uploading Patch to The M2000 Server
Version Files
The version file folder contains the version files provided by the network elements, such as s3000.wcu and the version description configuration files, such as vercfg.xml. The vercfg.xml file describes the related information, such as version number, file name, file size and file path of version files uploaded currently.

Patch Files
The patch file folder contains the patch files provided by the network element, such as patch.wcu and patch description configuration files, such as patchcfg.xml. The patchcfg.xml file describes the related information, such as version number, patch version number, file name, file size and file path of version files uploaded currently.

Uploading Version Files to the M2000 Server
To upload the version files to the M2000 server, perform the following steps: Step 1 Choose Software > Browser to open the software management interface. Step 2 Choose the Version node under the MSC Server node on the Server tab. Right-click Upload Version Files to Current Folder > From Local. The Upload File(s) to Server dialog box is displayed. Step 3 Choose the version file folder prepared and add it to the right table. Step 4 Click Start and the system displays the uploading progress. If the uploading is success, a version node is added under the node Version. ----End

Uploading Patch Files to the M2000 Server
After uploading the version files to the M2000 server, the patch file is required to be uploaded to the M2000. Step 1 Choose the version number node newly created. Right-click the Upload Version File(s) to Current Folder > From Local. The Upload File(s) to Server is displayed. Step 2 Choose the patch file folder prepared and add to the right table. Step 3 Click Start and the system displays the uploading. After successful uploading, a patch number node is added to the version number node. Step 4 Choose the patch node and you can see the patch file lists in the tables on the right of main software management interface, such as the patch name and patch version. ----End

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-9

20 Version Software Management Feature

HUAWEI MSOFTX3000 Feature Description

20.6.2 Operating Patch
Downloading Patch
To download a patch, perform the following steps: Step 1 Choose the Server tab on the main software management interface. Step 2 Choose MSC Server > Software > Version > Patch. The patch file lists uploaded are auto displayed on the right table.

The Version is the specific version uploaded and the Patch is the specific patch uploaded.

Step 3 Choose the patch to be downloaded to the network element. Right-click Download To NE and the NE Selection dialog box is displayed. Step 4 Choose the network element and click OK. The system auto downloads the files. A new task is added to the task progress table on the lower part of the main software management interface to display the downloading progress and status information. ----End

Loading Patch
To load a patch, perform the following steps: Step 1 Choose the NE page on the main software management interface. Step 2 Choose the nodes MSC Server > NE > Software> Version > Patch. The patch file lists are auto displayed on the right table.

The NE is the specific NE name, Version is the specific version of NE and Patch is the specific patch of NE.

Step 3 Choose the patch. Right-click Load and the Load Patch Parameters Selection dialog box are displayed. Step 4 Enter the corresponding parameter value and click OK. A new task is added to the task progress table on the lower part of the main software management interface to display the loading operation progress and status information. ----End

Activating Patch
To activate a patch, perform the following steps: Step 1 Choose the NE page on the main software management interface. Step 2 Choose the nodes MSC Server > NE > Software > Version > Patch. The patch file lists are auto displayed on the right table.

The NE is the specific network element name, Version is the specific version of NE and Patch is the specific patch of network element.

20-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

20 Version Software Management Feature

Step 3 Choose the patch. Right-click Activate and the Activate Patch Parameters Selection dialog box is displayed. Step 4 Enter the corresponding parameter value and click OK. A new task is added to the task progress table on the lower part of the main software management interface to display the activating operation progress and status information. ----End

Confirming Patch
To confirm a patch, perform the following steps: Step 1 Choose the NE page on the main software management interface. Step 2 Choose the nodes MSC Server > NE > Software > Version > Patch. The patch file lists are auto displayed on the right table.

The NE is the specific network element name, Version is the specific version of NE and Patch is the specific patch of network element.

Step 3 Choose the patch. Right-click Confirm and the Confirm Patch Parameters Selection dialog box is displayed. Step 4 Enter the corresponding parameter value and click OK. A new task is added to the task progress table on the lower part of the main software management interface to display the progress and status information of confirming operations. ----End

Deactivating Patch
To deactivate a patch, perform the following steps: Step 1 Choose the NE page on the main software management interface. Step 2 Choose the nodes MSC Server > NE > Software > Version > Patch. The patch file lists are auto displayed on the right table.

The NE is the specific network element name, Version is the specific version of NE and Patch is the specific patch of network element.

Step 3 Choose the patch. Right-click Deactivate and the Deactivate Patch Parameters Selection dialog box is displayed. Step 4 Enter the corresponding parameter value and click OK. A new task is added to the task progress table on the lower part of the main software management interface to display the progress and status information of the deactivating operation. ----End

Removing patch
To remove a patch, perform the following steps: Step 1 Choose the NE page on the main software management interface.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

20-11

7 Charging and CDR The feature does not affect the charging and CDR. Step 4 Enter the corresponding parameter value and click OK. A new task is added to the task progress table on the lower part of the main software management interface to display the progress and status information of the unloading operation. Step 3 Choose the patch.8 Service Interaction None. 20. The patch file lists are auto displayed on the right table.20 Version Software Management Feature HUAWEI MSOFTX3000 Feature Description Step 2 Choose the nodes MSC Server > NE > Software > Version > Patch.9 Reference Acronym/Abbreviation BAM FTP HLR GGSN LMT MML SGSN Full Name Back Administration Module File Transfer Protocol Home Location Register Gateway GPRS Support Node Local Maintenance Terminal Human-Machine Language Serving GPRS Support Node 20-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . ----End 20. Version is the specific version of NE and Patch is the patch of specific network element. The NE is the specific network element name. Right-click Unload and the Unload Patch Parameters Selection dialog box is displayed. 20.

.......................4 Data Configuration on the UMG8900 Side.........................................................................................21-2 21.......................................................................................................................................................21-2 21.............................................5..................................................................................2 State Transition .......................2......3 Working Principle................1 Requirements for NEs..........................2.............................6 Query Commands ..................................................3 Validity Check.........................................................................2 Configuration Preparations ...21-1 21........21-3 21..2 Synchronization and Forcible Synchronization Commands ...........................21-21 21..............................................................21-13 21..3 Activation and Forcible Activation Commands ....21-7 21....21-3 21....................................21-23 21...................21-27 21...............................................................................................................................................................................................................................................5 Cancellation and Confirmation Commands .............................................21-9 21....7 Charging and CDR ....................................9 Reference ........................................3....................................................................2....21-9 21...............................................................................................................................................................................................................6..............1 Service Description .................................................2 Availability ..6............................................................................HUAWEI MSOFTX3000 Feature Description Contents Contents 21 Configuration Rollback Feature..................6..............................2 Definition .............21-3 21...............................21-3 21.......4 Rollback and Forcible Rollback Commands...........................................................................................1 Function Code........................21-27 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ............. 21-11 21....................................................................................................................................................3.....................................................................................................................................21-19 21...............................................................21-27 21...5.......1 Data Configuration on the MSOFTX3000 Side....8 Service Interaction .21-13 21....................................................................1....................................................1...................1...............5 Data Configuration............................21-12 21................................................6..................21-3 21.....................21-3 21....21-14 21..........6 Service Management .............................................................................................21-2 21....................6.......1 Basic Principle ..............................................2 Requirements for License ..........6.......5..................................3 Benefits ............................................................................................4 Service Flow....................................................21-3 21...............................................................................................................................................21-13 21.....................................................1 Rollback Commands ....21-4 21....................................................................................................21-17 21........................................................................3.................................................21-6 21.....................................................3 Configuration Steps...............5.......................................3 Applicable Versions...........................................................................................................

....21-4 Figure 21-2 Illustration of state transition during configuration rollback .............................................................................Figures HUAWEI MSOFTX3000 Feature Description Figures Figure 21-1 Sketch of the active and the standby areas...21-7 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ..............................................................................21-5 Figure 21-3 State transition of data in the standby area...............................................................

................21-21 Table 21-10 Query commands............................................................21-3 Table 21-3 Applicable versions that support the configuration rollback feature............................................................................................................................21-10 Table 21-6 Synchronization and forcible synchronization commands ..............................................................21-19 Table 21-9 Cancellation and confirmation commands .................21-2 Table 21-2 Benefits of the configuration rollback feature ..........21-24 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ..................................................HUAWEI MSOFTX3000 Feature Description Tables Tables Table 21-1 Feature name and function code ............................................................................................................................................................................................21-3 Table 21-4 Tables that support configuration rollback ........................................................................................................................................................21-14 Table 21-7 Activation and forcible activation commands............................21-17 Table 21-8 Rollback and forcible rollback commands ..........................21-9 Table 21-5 List of configuration rollback commands..........................................................................................

and the version requirements of the NEs. and the acronyms and abbreviations of this chapter.9 Reference Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-1 .HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature 21 Section 21. The functions of the NEs. The service flow of the network when providing this feature. The network elements (NEs) that are required for the feature.5 Data Configuration 21. whether Licenses are required.6 Service Management 21. The protocols and specifications that this feature must comply with.8 Service Interaction 21.7 Charging and CDR 21.2 Availability Configuration Rollback Feature About This Chapter The following table lists the contents of this chapter. and networking requirements.4 Service Flow 21. 21. The service operations that carriers and mobile subscribers are required to implement when the network provides this feature. The relationships and restrictions between this feature and other services or features. function definition of this feature. The data configurations that are required on the MSOFTX3000 and the IMG8900. The charging and the generation of CDRs when the network provides this feature.3 Working Principle 21.1 Service Description 21. and the benefits that carriers and mobile subscribers can obtain from this feature. Describes The function code.

after you successfully add. if the data is found to be incorrect. operations of multiple users on the M2000 cannot be distinguished at the BAM side and thus the BAM cannot obtain specific user information. During data configuration. After a period of trial operation. you hand over the active/standby data to roll back to the previous state. Table 21-1 Feature name and function code Name Configuration rollback Code WMFD-121500 21. In addition. If the data is proved correct. "Enable" in rollback state: The host runs the newly configured data and can roll back to the previous configuration. "Enable permanently" in rollback state: It means the same as "Enable" in non-rollback state. As a special internal account is used to log on to the BAM from the M2000 and this account is not related to M2000 users.2 Definition To ensure network security. 21-2 Huawei Technologies Proprietary Issue 02 (2007-06-10) . which may interrupt the services and in turn affect the stable operation. It wastes time to restore the database backup or run the commands one by one to get back to the previous state. Consider that the configuration rollback feature is not enabled.1. the system is equipped with the timely rollback function that can prevent traffic loss caused by incorrect operations. the modified data is stored in the database temporarily. the configuration rollback function is presented.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description 21. if you choose to restore the database. you have to restore the previous configuration. Therefore. you enable the configuration permanently and end the task. you have to set the data table in batch or reset the host. This does not affect the data in the active area or services of the host. This is a basic requirement of telecom products. The configuration rollback mechanism is built on the principle that the operator who locks the table is authorized to perform the related operations. You can first configure data in the standby area.1 Service Description 21.1 Function Code Table 21-1 lists the name and function code of this feature. To solve these problems. It sets up a standby area for each table that supports configuration rollback.1. you hand over the data in the standby area to the active area to validate the configuration. "Enable" in non-rollback state: The host runs the newly configured data and cannot roll back to the previous configuration. After the configuration is complete. delete or modify certain data. If the data is wrongly configured. only the local users of the NE can use the configuration rollback feature. The data is then sent to the host and takes effect immediately after the formatting and online setting functions are enabled.

1.3 Working Principle 21. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-3 . 21.2. including tables in the database and formatting data files. No License is required to obtain the feature.3.2 Availability 21. None. It is in the directory Data.3 Benefits Table 21-2 lists the benefits of the configuration rollback feature. Table 21-3 Applicable versions that support the configuration rollback feature Product MSC Server MSOFTX3000 Applicable Version V100R005 and later versions 21. 21. The standby area that contains the standby tables and formatting files is in the directory Data_Backup.3 Applicable Versions Table 21-3 lists the applicable versions that support the configuration rollback feature of Huawei CN.2. Table 21-2 Benefits of the configuration rollback feature Beneficiary Carriers Subscribers Description It improves the security of configuring sensitive service data and facilitates the maintenance.1 Requirements for NEs The configuration rollback feature is performed without collaborating with peripheral NEs.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature 21. 21.2 Requirements for License The configuration rollback feature is a basic feature of Huawei Core Network (CN).1 Basic Principle The system sets a standby area for the tables that support configuration rollback. The active area consists of the current tables and the formatting files.2.

you can hand over the active/standby data to validate the modification. All the configuration rollback operations are performed in the standby area.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description The standby area directory is in the BAM installation directory MSOFTX3000\ConfigRollBack. if the data is found to be incorrect.2 State Transition In actual operation. Figure 21-1 shows the structure of the active and the standby areas. If the data is proved correct. 21-4 Huawei Technologies Proprietary Issue 02 (2007-06-10) . After a period of trial operation. you can hand over the active/standby data to roll back to the previous state. the state transition of tables during configuration rollback is shown in Figure 21-2.3. you can enable the configuration permanently and end the task. Figure 21-1 Sketch of the active and the standby areas Active area Data BAM tbl_XXXXX Files of standby tables tbl_XXXXX_Backup Data_Backup Standby area 21. After the configuration is complete.

Modify During configuration rollback. its state remains unchanged. the tables that support configuration rollback are in "Normal" state. The table states are used when the configuration rollback function is enabled. If it is disabled. Normal State When the configuration rollback function is enabled. If any problem is found in this state. you cannot perform any configuration operation. before you run the synchronization command. the newly configured data takes effect in the host. represented by V0. The data in the active area is the original data. The standby area has no data. Trial In "Trial" state. the system rolls back to the "Modify" state to correct the configuration. represented by V?. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-5 . original data and backup files of a table in "Modify" or "Trial" state. that is. Suppose there is a record Call prefix = 135 in the active area. you can run commands to configure data in "Modify" state and only in this state. the previous three states do not exist.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Figure 21-2 Illustration of state transition during configuration rollback Active: V0 Active: V1 Standby: V? Normal operation Standby: V? Normal operation Safe configuration (original (Modified configuration) configuration) Synchronize Cancel Active: V0 Standby: V0 Activate/ Activate forcibly Modify Active: V0 Standby: V1 Rollback/ Rollback forcibly Compare data before and after modification Confirm/ timeout Active: V1 Standby: V0 Synchronize forcibly Active: V1 Standby: V1 Trial Modify To facilitate the description of state transition. The restart of the BAM does not affect the table state. If a table in "Modify" state is not processed within a period. Consider the Called Number Analysis Table as an example. the configuration flow is as normal. then the same record exists in the host and no data exists in the standby area. three table states are defined: Normal In "Normal" state.

Therefore. you must perform validity check on the data configured in the standby area. The data in the standby area is handed over to the active area and then set to the host immediately. You are not allowed to perform any operation. After rollback. In "Trial" state. the table changes to be in "Trial" state.3. The commands take effect only in the standby area. the system also hands over the data in the active area to the standby area. The tables are not required to be checked in "Modify" state. After synchronization. run the confirmation command and enable the configuration in the active area and the host permanently. the data V1 in the standby area is deleted. The table changes to be in "Normal" state. the data in the standby area must be checked for validity before handover. The record Call prefix = 135 exists in the standby area. the data in the active and the standby area exchanges again. the data is being tested. if the data in the host is correct. In case of later rollback. Now the data in the active area is V1.There is only one record in the active area and the host. Thus. Trial State After activation or forcible activation. You can proceed with the configuration and then activate. If you want to re-configure the data. Call prefix = 135. The data in the standby area is now represented by V1. that is. You can run commands to configure data in the tables that support configuration rollback feature only in "Modify" state. the data in the two areas is the same. If you add a record Call prefix = 136 to the table. you can roll back the configuration to the original state. four data states are defined: Valid It is a basis for active/standby data handover (activation or rollback) that the data in the standby area is "Valid". The data in the active area and the host remains unchanged. 21. The data in the standby area is V0. The data in the active area does not change and the host is not affected. defects or problems that cannot be located. The data of the host is the same as that in the active area. Two records (Call prefix = 135 and Call prefix = 136) exist in the active area. In "Trial" state. the host is running as usual. to ensure the efficiency and accuracy of the data. the data in the standby area is deleted. Only one record (Call prefix = 135) exists in the standby area. the former data in the standby area is lost completely.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Modify State Synchronization means to synchronize the data in the standby area with that in the active area. you can run the command FSYN XXX to forcibly synchronize the data in the standby area with the data in the active area. If you cancel the operation in "Modify" state. The data in the standby area is V1. 21-6 Huawei Technologies Proprietary Issue 02 (2007-06-10) . To facilitate the description of data credibility. The data in the active area is V0. In "Trial" state. Now the data in the active area is V1. Two records (Call prefix = 135 and Call prefix = 136) exist in the standby area. roll back or confirm the configuration. then there are two records of call prefix in the standby area. Only the record (Call prefix = 135) exists in the active area and the host. The table turns to be in "Modify" state.3 Validity Check During configuration rollback. If you find that the configured data has errors. The table changes to be in "Modify" state. At the same time.

Invalid During validity check. the data in the table is updated to be "Unknown" after rollback. it is set to be "Invalid". including the following: Single user locking Table state query Comparison of data in active and standby areas In actual usage. the basic operation flow of the configuration rollback feature is as follows: Step 1 Run the command SET FMT to enable the formatting function. if the data fails to meet the check rules. The unknown data is the data that has not been verified. Step 3 Consider that you must modify a table that supports configuration rollback. run the command SYN XXX to synchronize the data in the standby area with that in the active area. the configuration rollback feature provides protection/restriction functions for the tables. First. XXX refers to the object to which the command is executed. Figure 21-3 shows the state transition of the data in the standby area.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Unknown The tables rely on each other during data configuration. Step 2 Run the command SET CFGRLB to enable the configuration rollback function and enter the operation state of configuration rollback. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-7 . Figure 21-3 State transition of data in the standby area Modify Valid Unknown Check succeeded Modify Check storage procedure Invalid Check failed Checked 21. Therefore. Before enabling the configuration rollback function. Checked The data in "Checked" state means that the data is being checked. you must enable the formatting function first.4 Service Flow Besides the functions described in the previous sections. The latter cannot be disabled when the former is enabled.

however. Before activation or rollback. At present. he/she must obtain the control right by running the command FSYN XXX. The operator can modify the data based on the previous configuration. you can modify the data based on the previous modification and re-activate it. Note that the data modified by you may be lost then. it is recommended to query the table state to check whether the table is locked by any other operator. the data must be proved valid. use the modified data to overwrite the original data. The data in the standby area. the data in both the active and the standby areas cannot be modified. Modify the data and then activate it again. The configuration can never be rolled back to the original state by using this method. run the command CNL XXX to delete all the modified data in the standby area while the data in the active area remains unchanged. modify the incorrect data and then re-activate it. 21-8 Huawei Technologies Proprietary Issue 02 (2007-06-10) . This is a basis for later modification. Synchronize the data in the standby area with that in the active area. The data in the standby area must be checked for validity before rollback. Step 6 Within 24 hours after activation. Step 4 During data configuration. Run the forcible synchronization command to overwrite the standby area with the data of the active area. Lock the table. You can run the forcible command FRLB XXX to avoid the validity check if necessary. you must obtain agreement of that operator first and keep cautious in operation. This may interrupt the services set up by the newly configured data. if you find errors in the configured data. resumes the previous configuration after rollback. run the forcible command FACT XXX to omit the validity check on certain tables. The configuration must be rolled back to the original state by using this method. If another operator wants to modify the table at the same time. if you want to re-configure the data. 2. use either of the following methods: Roll back the configuration. The validity check can be performed in either of the following ways: The BAM auto checks the data of the tables that support configuration rollback every five seconds. You modify data in the standby area and the modification is not set to the host. It prevents other operators from modifying the data of the locked table in the standby area at the same time. It serves two purposes: − − The data of the locked table in the active area cannot be modified. Within 24 hours after activation. After handover. If the table has been locked by an operator. You can run the command CHK XXX to check the data of a specific table. Step 5 After configuration. run the command ACT XXX to validate the modified data and start the trial operation. Then.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description 1. If you want to run the forcible synchronization command. run the command RLB XXX to hand over the active/standby data again. if you want to cancel the modification. that is. The data in the standby area must be checked for validity before activation. If the check fails because the dependent tables affect each other.

Table 21-4 lists the tables of the MSOFTX3000 that support configuration rollback. a set of commands are provided for operators to query the current state. The same operator can log in to different terminals to perform configuration rollback operations at the same time. Step 8 After confirmation. When a user name is deleted and then added again. the user ID of this user changes.5 Data Configuration 21. 21. The configuration rollback feature only identifies the user ID.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Step 7 Confirm the configuration in either of the following two ways: Manual confirmation You can confirm the configuration within 24 hours after activation and run the command CMT XXX to validate the data. Therefore. the system auto confirms it and enters the "Normal" state. user names can be used to identify the operators. During configuration rollback. you are not allowed to perform any configuration rollback operation. The data becomes valid permanently. These commands are described in the following sections. Auto confirmation If you do not confirm the configuration within 24 hours.1 Data Configuration on the MSOFTX3000 Side Tables The configuration rollback operations are performed on data tables. The configuration can never be rolled back again. standby table data. The system enters the "Normal" state. run the command SET CFGRLB to disable the configuration rollback function. The standby area is now cleaned up.5. A user name often corresponds to a user ID (used inside the BAM). ----End Only the users at the Operator level or higher levels are authorized to perform the configuration rollback operations. Table 21-4 Tables that support configuration rollback Table ID 105 106 108 119 124 125 126 127 Table Name Called Number Analysis Table Called Number Special Process Table Called Number Pre-analysis Table Calling Number Analysis Table DP Prefix Process Table IN Service Description Table CLI Number Display Process Table CLI Number Display CLD Association Table Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-9 . At present. differences between the active and the standby tables.

21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Table ID 129 134 135 136 137 138 139 142 301 302 308 309 368 Table Name Redirecting Analysis Table Incoming Number Pretreatment Table Incoming Calling Number Association Table Incoming Original Called Number Association Table Outgoing Number Pretreatment Table Outgoing Calling Number Association Table Outgoing Original Called Number Association Table HO Number Outgoing Process Table Route Data Table Route Analysis Table Trunk Group Bearer Table Trunk Group Call Bearer Index Table SCCP GT Table Commands Table 21-5 lists the MSOFTX3000 commands used for configuration rollback. Table 21-5 List of configuration rollback commands Command SET CFGRLB SYN XXX FSYN XXX Name Set the Status of CFGRLB Synchronize XXX Forcibly Synchronize XXX Cancel the Modification of XXX Acknowledge XXX Activate XXX Forcibly Activate XXX Function To enable or disable the configuration rollback feature To synchronize the standby table with a certain data table To forcibly synchronize the standby table with a certain data table even when the table is locked To cancel the modification of the data in the standby table To confirm the modification of the data in a table To activate the data of a table in the standby area To forcibly activate a standby table when the data in the table is invalid CNL XXX CMT XXX ACT XXX FACT XXX 21-10 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

During configuration rollback.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Command RLB XXX FRLB XXX LST XXXBKP CMP XXX Name Change Back XXX Forcibly Change Back XXX List Backup XXX Compare XXX in Active/Standby Way Function To roll back the activated table To forcibly roll back the activated table when the data in the table is invalid To list the data in the standby table To compare the differences between the active and the standby areas. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-11 . state transition time. records existing only in the standby area and records that are different in the active and the standby areas To check the validity of the data in the standby area To list the information of tables that support configuration rollback. are used only when the handover fails because of the dependent relationship of tables. The configuration rollback operations may affect the services in the following ways: The command FSYN XXX deletes the original data in the standby area. data credibility. table ID and table name To list the configuration rollback status To list the duration after which the system performs automatic confirmation To modify the duration after which the system performs automatic confirmation CHK XXX LST TBLSTA Check XXX Table List the Status of Configuration Rollback Table List Dataman Status List Auto Confirm Time Modify Auto Confirm Time LST DATAMAN LST CMTTM MOD CMTTM 21. Forcible activation or rollback may lead to invalid data in the active area. It is disabled by default. The data configuration of the configuration rollback feature complies with the normal configuration guide.2 Configuration Preparations Configuration rollback is a supplementary feature for service data configuration. such as records existing only in the active area. including table state. operator locking the table.5. you must ensure that the services are not affected. These commands however.

SET CFGRLB: STS=OFF. RLB CNACLD:. Step 5 Run the command ACT CNACLD to activate the modified data in the standby area. Step 1 Run the command SET CFGRLB to enable the configuration rollback feature. If you need to roll back the data. turn to Step 14. The newly configured data take effect. the BAM auto checks the validity of the data in the tables that support configuration rollback every five seconds. the system auto confirms the modification after 24 hours. PFX=K'111. The Called Number Analysis Table changes back to be in "Modify" state. In "Modify" state. SYN CNACLD:. ADD CNACLD: P=0. The Called Number Analysis Table changes to be in "Trial" state. If you need to synchronize the data forcibly. Step 4 Run the command CHK CNACLD to check the validity of the modified data. turn to Step 9. turn to Step 8. SET CFGRLB: STS=ON.5. Therefore. If you need to check the table state. The auto confirmation duration is 24 hours by default.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description 21.3 Configuration Steps In "Modify" or "Trial" state. Step 8 After Step 5. If you need to synchronize the data forcibly. in "Trial" state. Step 2 Run the command SYN CNACLD to synchronize the call prefix of the active and the standby areas. MINL=1. 21-12 Huawei Technologies Proprietary Issue 02 (2007-06-10) . ACT CNACLD:. You can run the command MOD CMTTM to modify the auto confirmation duration. Consider the Called Number Analysis Table as an example to describe the configuration steps. turn to Step 9. Step 7 Run the command SET CFGRLB to disable the configuration rollback feature. you can run the command CMP XXX to compare the data between the active and the standby areas. MAXL=2. Step 3 Run the command ADD/MOD/RMV CNACLD to modify the call prefix in the standby area. CHK CNACLD:. Step 6 Run the command CMT CNACLD to confirm the modification in "Trial" state. CMT CNACLD:. you can run the command RLB CNACLD to roll back the configuration.

Step 13 Run the command SET CFGRLB to disable the configuration rollback feature. FACT CNACLD:. You can perform the configuration rollback operations only when the two functions are both enabled. you can run the command FSYN CNACLD to forcibly synchronize the data of the active and the standby areas. Step 11 Run the command FRLB CNACLD to roll back the configuration forcibly. FRLB CNACLD:. When the BAM finds after start that the configuration rollback is enabled while the formatting is not. CNL CNACLD:. Step 14 Run the command LST TBLSTA to list the status of tables that support configuration rollback. FSYN CNACLD:. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-13 .1 Rollback Commands This section describes the following commands: SET CFGRLB LST DATAMAN LST TBLSTA LST CMTTM MOD CMTTM SET CFGRLB This command is used to enable or disable the configuration rollback function. Step 15 Run the command LST CNACLDBKP to list the data in the standby area. You can perform the configuration rollback operations only when the command sets it to ON.4 Data Configuration on the UMG8900 Side None. 21.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Step 9 After Step 2 and Step 8. Step 16 Run the command LST DATAMAN to list the status of the configuration rollback feature.6. ----End 21. Step 10 Run the command FACT CNACLD to forcibly activate the modified data in the standby area. LST DATAMAN: . LST CNACLDBKP: . LST TBLSTA: . it enables the formatting function forcibly. Step 12 Run the command CNL CNACLD to cancel the modification in "Modify" state.5.6 Service Management 21. SET CFGRLB: STS=OFF.

The operator who is authorized to run this command can list the information of the tables locked by another operator. You can list the information of a certain table or all tables. formatting and online setting functions. 21. and then run the command SET CFGRLB to enable the configuration rollback function. LST DATAMAN This command is used to list the status of the configuration rollback.2 Synchronization and Forcible Synchronization Commands The synchronization and forcible synchronization commands are applied to a specific table. LST CMTTM This command is used to list the auto confirmation duration for configuration rollback.6.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Therefore. you must first run the command SET FMT to enable the formatting function. data credibility. MOD CMTTM This command is used to modify the auto confirmation duration for configuration rollback. LST TBLSTA This command is used to list the table information. such as table state. The mapping relationship is listed in Table 21-6. Table 21-6 Synchronization and forcible synchronization commands Command SYN CNACLD /FSYN CNACLD SYN CNACLR /FSYN CNACLR SYN PFXPRO /FSYN PFXPRO SYN CLDPREANA /FSYN CLDPREANA SYN IDPNPRO /FSYN IDPNPRO SYN SRVNUM /FSYN SRVNUM Name Synchronize Call Prefix /Forcibly Synchronize Call Prefix Synchronize Calling Number Analysis /Forcibly Synchronize Calling Number Analysis Synchronize Special Dialed Number Processing /Forcibly Synchronize Special Dialed Number Processing Synchronize Called Number Pre-analysis Information /Forcibly Synchronize Called Number Pre-analysis Information Synchronize IPD Number Processing /Forcibly Synchronize IPD Number Processing Synchronize Intelligent Service Number Information /Forcibly Synchronize Intelligent Service Number Information 21-14 Huawei Technologies Proprietary Issue 02 (2007-06-10) . operator locking the table and state switch time.

HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Command SYN CLIPRO /FSYN CLIPRO SYN CLCRPRO /FSYN CLCRPRO Name Synchronize CLIP Processing /Forcibly Synchronize CLIP Processing Synchronize CLIP Called Number Correlation Processing /Forcibly Synchronize CLIP Called Number Correlation Processing SYN REDRCTANA /FSYN REDRCTANA SYN INNUMPREPRO /FSYN INNUMPREPRO SYN INCLRIDX /FSYN INCLRIDX Synchronize Forwarding Number Analysis Information /Forcibly Synchronize Forwarding Number Analysis Information Synchronize Incoming Number Pre-processing /Forcibly Synchronize Incoming Number Pre-processing Synchronize Incoming Calling Number Associated Processing /Forcibly Synchronize Incoming Calling Number Associated Processing SYN INORICLDIDX /FSYN INORICLDIDX Synchronize Incoming Original Called Number Associated Processing /Forcibly Synchronize Incoming Original Called Number Associated Processing SYN OUTNUMPREPRO /FSYN OUTNUMPREPRO SYN OUTCLRIDX /FSYN OUTCLRIDX Synchronize Outgoing Number Pre-processing /Forcibly Synchronize Outgoing Number Pre-processing Synchronize Outgoing Calling Number Associated Processing /Forcibly Synchronize Outgoing Calling Number Associated Processing SYN OUTORICLDIDX /FSYN OUTORICLDIDX Synchronize Outgoing Original Called Number Associated Processing /Forcibly Synchronize Outgoing Original Called Number Associated Processing SYN HDOVPROC /FSYN HDOVPROC Synchronize Handover Number Processing Table Information /Forcibly Synchronize Handover Number Processing Table Information SYN RT /FSYN RT SYN RTANA /FSYN RTANA SYN TGLD /FSYN TGLD Synchronize Routes /Forcibly Synchronize Routes Synchronize Route Analysis /Forcibly Synchronize Route Analysis Synchronize Trunk Group Bearer /Forcibly Synchronize Trunk Group Bearer Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-15 .

dat is the formatting file for the standby area.dat is the backup file for the active area. Table Name_Backup1. the formatting files Table Name_Backup0. FSYN XXX The forcible synchronization works almost the same as synchronization. It however. To improve the configuration efficiency. the storage procedure does not check the consistency of service data in "Modify" state. In "Modify" state. At the same time. The data requires to be synchronized includes the formatting data and the tables in the database. The data in the active table is exported to the standby table in synchronization. Synchronization of database tables: Each table that supports configuration rollback has a standby table named Table Name_Backup1.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Command SYN TGLDIDX /FSYN TGLDIDX SYN SCCPGT /FSYN SCCPGT Name Synchronize Trunk Group Bearer Indexes /Forcibly Synchronize Trunk Group Bearer Indexes Forcibly Synchronize SCCP Global Titles /Forcibly Synchronize SCCP Global Titles SYN XXX Before modifying a table that supports configuration rollback. All the configuration commands are executed on the standby table. The table changes to be in "Modify" state after being forcibly synchronized.dat files of the modules of the table. Let the system auto check or run the command CHK XXX to check the data credibility. 21-16 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The synchronization can be performed in "Normal" or "Modify" state. the data in the standby table is modified. It is locked by the operator who performs the synchronization. After synchronization. Activate the data only when it is valid.dat and Table Name_Backup1. the table changes to be in "Modify" state. It always keeps consistent with the data in the active area. The initial data of these two files comes from the db_?.dat. After the first synchronization. you must synchronize the data of the active and the standby areas. You cannot modify the data in the active table in "Modify" state. An operator can obtain the control right of a table by this operation.dat for the standby area are generated in the BAM installation directory \ConfigRollBack\Data_Backup. Table Name_Backup0. the BAM formats the data in the standby table to the formatting file Table Name_Backup1. Other operators are not allowed to modify the table or perform the configuration rollback operations on the table unless they forcibly synchronize the table to obtain the control right. Note that the data modified after the first synchronization is lost if you synchronize the data in "Modify" state. which is different from synchronization. Synchronization of formatting data: The formatting files for the standby area are generated and organized on the basis of table. The state of the data in the standby table is updated from "Valid" to "Unknown". The data in the standby area is formatted to this file in configuration rollback state. can be performed in any state. The online setting is not enabled now.

The mapping relationship is listed in Table 21-7.6.3 Activation and Forcible Activation Commands The activation and forcible activation commands are applied to a specific table. Table 21-7 Activation and forcible activation commands Command ACT CNACLD /FACT CNACLD ACT CNACLR /FACT CNACLR ACT PFXPRO /FACT PFXPRO ACT CLDPREANA /FACT CLDPREANA ACT IDPNPRO /FACT IDPNPRO ACT SRVNUM /FACT SRVNUM ACT CLIPRO /FACT CLIPRO ACT CLCRPRO /FACT CLCRPRO ACT REDRCTANA /FACT REDRCTANA ACT INNUMPREPRO /FACT INNUMPREPRO ACT INCLRIDX /FACT INCLRIDX Description Activate Call Prefix /Forcibly Activate Call Prefix Activate Calling Number Analysis /Forcibly Activate Calling Number Analysis Activate Special Dialed Number Processing /Forcibly Activate Special Dialed Number Processing Activate Called Number Pre-analysis Information /Forcibly Activate Called Number Pre-analysis Information Activate IPD Number Processing /Forcibly Activate IPD Number Processing Activate Intelligent Service Number Information /Forcibly Activate Intelligent Service Number Information Activate CLIP Processing /Forcibly Activate CLIP Processing Activate CLIP Called Number Correlation Processing /Forcibly Activate CLIP Called Number Correlation Processing Activate Forwarding Number Analysis Information /Forcibly Activate Forwarding Number Analysis Information Activate Incoming Number Pre-processing /Forcibly Activate Incoming Number Pre-processing Activate Incoming Calling Number Associated Processing /Forcibly Activate Incoming Calling Number Associated Processing ACT INORICLDIDX /FACT INORICLDIDX Activate Incoming Original Called Number Associated Processing /Forcibly Activate Incoming Original Called Number Associated Processing Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-17 .HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature 21.

dat in the active area.dat is consistent with the data in the active table. the two tables may be both invalid. db_?. If there are two tables relying on each other in "Modify" state.dat and Table Name_Backup1. run the command CHK XXX to check it or let the system auto check it. After activation.dat to the formatting file. Only the operator who locks the table can activate it and the data in the table must be "Valid".21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Command ACT OUTNUMPREPRO /FACT OUTNUMPREPRO ACT OUTCLRIDX /FACT OUTCLRIDX Description Activate Outgoing Number Pre-processing /Forcibly Activate Outgoing Number Pre-processing Activate Outgoing Calling Number Associated Processing /Forcibly Activate Outgoing Calling Number Associated Processing ACT OUTORICLDIDX /FACT OUTORICLDIDX Activate Outgoing Original Called Number Associated Processing /Forcibly Activate Outgoing Original Called Number Associated Processing ACT HDOVPROC /FACT HDOVPROC Activate Handover Number Processing Table Information /Forcibly Activate Handover Number Processing Table Information ACT RT /FACT RT ACT RTANA /FACT RTANA ACT TGLD /FACT TGLD ACT TGLDIDX /FACT TGLDIDX ACT SCCPGT /FACT SCCPGT Activate Routes /Forcibly Activate Routes Activate Route Analysis /Forcibly Activate Route Analysis Activate Trunk Group Bearer /Forcibly Activate Trunk Group Bearer Activate Trunk Group Bearer Index /Forcibly Activate Trunk Group Bearer Index Activate SCCP Global Titles /Forcibly Activate SCCP Global Titles ACT XXX This command is used to activate the modified data in the standby area. If the data is still "Invalid" after check. the table changes to be in "Trial" state. 21-18 Huawei Technologies Proprietary Issue 02 (2007-06-10) .dat to ensure that the data in Table Name_Backup0. You can perform it only in "Modify" state. you can run the command FACT XXX to activate it forcibly. The key operations for activation are active/standby data handover and data setting. If the data is "Unknown". The data handover contains the following: Handover of formatting data: Update the data in Table Name_Backup1. Hand over the two files Table Name_Backup0.

that is. The data however. Table 21-8 Rollback and forcible rollback commands Command RLB CNACLD /FRLB CNACLD RLB CNACLR /FRLB CNACLR RLB PFXPRO /FRLB PFXPRO RLB CLDPREANA /FRLB CLDPREANA Name Change Back Call Prefix /Forcibly Change Back Call Prefix Change Back Calling Number Analysis /Forcibly Change Back Calling Number Analysis Change Back Special Dialed Number Processing /Forcibly Change Back Special Dialed Number Processing Change Back Called Number Pre-analysis Information /Forcibly Change Back Called Number Pre-analysis Information RLB IDPNPRO /FRLB IDPNPRO RLB SRVNUM /FRLB SRVNUM Change Back IDP Number Processing /Forcibly Change Back IDP Number Processing Change Back Intelligent Service Number Information /Forcibly Change Back Intelligent Service Number Information RLB CLIPRO /FRLB CLIPRO RLB CLCRPRO /FRLB CLCRPRO Change Back CLIP Processing /Forcibly Change Back CLIP Processing Change Back CLIP Called Number Correlation Processing /Forcibly Change Back CLIP Called Number Correlation Processing Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-19 . The table changes to be in "Trial" state after being forcibly activated.4 Rollback and Forcible Rollback Commands The rollback and forcible rollback commands are applied to a specific table.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Handover of tables in the database. FACT XXX The forcible activation works almost the same as activation. Besides. The mapping relationship is listed in Table 21-8. the tables locked by an operator can be activated forcibly by another operator. is not checked for validity before forcible activation. data in the standby table Table Name_Backup1 and that in the active table: After successfully handing over the formatting files and database tables. 21. set the modification to the host to make the host’s data consistent with that of the BAM.6.

21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Command RLB REDRCTANA /FRLB REDRCTANA Name Change Back Forwarding Number Analysis Information /Forcibly Change Back Forwarding Number Analysis Information RLB INNUMPREPRO /FRLB INNUMPREPRO RLB INCLRIDX /FRLB INCLRIDX Change Back Incoming Number Pre-processing /Forcibly Change Back Incoming Number Pre-processing Change Back Incoming Calling Number Associated Processing /Forcibly Change Back Incoming Calling Number Associated Processing RLB INORICLDIDX /FRLB INORICLDIDX Change Back Incoming Original Called Number Associated Processing /Forcibly Change Back Incoming Original Called Number Associated Processing RLB OUTNUMPREPRO /FRLB OUTNUMPREPRO RLB OUTCLRIDX /FRLB OUTCLRIDX Change Back Outgoing Number Pre-processing /Forcibly Change Back Outgoing Number Pre-processing Change Back Outgoing Calling Number Associated Processing /Forcibly Change Back Outgoing Calling Number Associated Processing RLB OUTORICLDIDX /FRLB OUTORICLDIDX Change Back Outgoing Original Called Number Associated Processing /Forcibly Change Back Outgoing Original Called Number Associated Processing RLB HDOVPROC /FRLB HDOVPROC Change Back Handover Number Processing Table Information /Forcibly Change Back Handover Number Processing Table Information RLB RT /FRLB RT RLB RTANA /FRLB RTANA RLB TGLD /FRLB TGLD RLB TGLDIDX /FRLB TGLDIDX RLB SCCPGT /FRLB SCCPGT Change Back Routes /Forcibly Change Back Routes Change Back Route Analysis /Forcibly Change Back Route Analysis Change Back Trunk Group Bearer /Forcibly Change Back Trunk Group Bearer Change Back Trunk Group Bearer Index /Forcibly Change Back Trunk Group Bearer Index Change Back SCCP Global Titles /Forcibly Change Back SCCP Global Titles 21-20 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

Table 21-9 Cancellation and confirmation commands Command CNL CNACLD /CMT CNACLD CNL CNACLR /CMT CNACLR CNL PFXPRO /CMT PFXPRO CNL CLDPREANA /CMT CLDPREANA CNL IDPNPRO /CMT IDPNPRO Name Cancel the Modification of a Call Prefix /Acknowledge Call Prefixes Cancel the Modification of Calling Number Analysis /Acknowledge Calling Number Analysis Cancel the Modification of Special Dialed Number Processing /Acknowledge Special Dialed Number Processing Cancel the Modification of Called Number Pre-analysis Information /Acknowledge Called Number Pre-analysis Information Cancel the Modification of IPD Number Processing /Acknowledge IPD Number Processing Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-21 .dat is consistent with the data in the active area. The table changes to be in "Modify" state after being forcibly rolled back. Only the operator who locks the table can roll it back and the data in the standby table must be "Valid". The data however. run the command FRLB XXX to roll it back forcibly. Handover of database tables: Handover the data in the standby table Table Name_Backup1 and that in the active table. that is. The data handover contains the following: Handover of formatting data: Update the data in Table Name_Backup1.dat to the formatting file. db_?. the two tables may both be invalid. 21. is not checked for validity before forcible rollback. The key operations of rollback are the same as those of activation. (The default check period is five seconds. If the data is "Unknown".dat and Table Name_Backup1.dat in the active area.dat to make sure that the data in Table Name_Backup0. FRLB XXX The forcible rollback works almost the same as rollback.5 Cancellation and Confirmation Commands The cancellation and confirmation commands are applied to a specific table. the table changes back to be in "Modify" state. It can be performed only in "Trial" state. Hand over the two files Table Name_Backup0.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature RLB XXX This command is used to roll back the configuration. Besides. and replace the data in the active area with the data in the standby area and validate it. active/standby data handover and data setting.6. The mapping relationship is listed in Table 21-9. Rollback is a converse operation of activation. If there are two tables relying on each other in "Modify" state. the tables locked by an operator can be rolled back forcibly by another operator. After rollback.)If the data in the standby area is still "Invalid" after check and you are sure to roll it back. you can run the command CHK XXX or let the system auto check it.

21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Command CNL SRVNUM /CMT SRVNUM CNL CLIPRO /CMT CLIPRO CNL CLCRPRO /CMT CLCRPRO CNL REDRCTANA /CMT REDRCTANA CNL INNUMPREPRO /CMT INNUMPREPRO CNL INCLRIDX /CMT INCLRIDX CNL INORICLDIDX /CMT INORICLDIDX Name Cancel the Modification of Intelligent Service Number Information /Acknowledge Intelligent Service Number Information Cancel the Modification of CLIP Processing /Acknowledge CLIP Processing Cancel the Modification of CLIP Called Number Correlation Processing /Acknowledge CLIP Called Number Correlation Processing Cancel the Modification of Forwarding Number Analysis Information /Acknowledge Forwarding Number Analysis Information Cancel the Modification of Incoming Number Pre-processing /Acknowledge Incoming Number Pre-processing Cancel the Modification of Incoming Calling Number Associated Processing /Acknowledge Incoming Calling Number Associated Processing Cancel the Modification of Incoming Original Called Number Associated Processing /Acknowledge Incoming Original Called Number Associated Processing CNL OUTNUMPREPRO /CMT OUTNUMPREPRO CNL OUTCLRIDX /CMT OUTCLRIDX CNL OUTORICLDIDX /CMT OUTORICLDIDX CNL HDOVPROC /CMT HDOVPROC CNL RT /CMT RT CNL RTANA /CMT RTANA Cancel the Modification of Outgoing Number Pre-processing /Acknowledge Outgoing Number Pre-processing Cancel the Modification of Outgoing Calling Number Associated Processing /Acknowledge Outgoing Calling Number Associated Processing Cancel the Modification of Outgoing Original Called Number Associated Processing /Acknowledge Outgoing Original Called Number Associated Processing Cancel the Modification of Handover Number Processing Table Information /Acknowledge Handover Number Processing Table Information Cancel the Modification of Routes /Acknowledge Routes Cancel the Modification of Route Analysis /Acknowledge Route Analysis 21-22 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Command CNL TGLD /CMT TGLD CNL TGLDIDX /CMT TGLDIDX CNL SCCPGT /CMT SCCPGT Name Cancel the Modification of Trunk Group Bearer /Acknowledge Trunk Group Bearer Cancel the Modification of Trunk Group Bearer Index /Acknowledge Trunk Group Bearer Index Cancel the Modification of SCCP Global Titles /Acknowledge SCCP Global Titles CNL XXX This command is used to delete all the modification in the standby area. all the data (including the formatting files and standby table data) in the standby area is deleted. The former validates the modified data while the latter invalidates the data. the system auto confirms it and the table then changes to be in "Normal" state. If you do not confirm the configuration within 24 hours in "Trial" state. It can be performed only in "Trial" state. Only the operator who locks the table can perform it. function differently. Only the operator who locks the table can cancel the modification. The two commands however. After cancellation.6 Query Commands The query commands include the commands to: List active table data List standby table data Compare the data of the active/standby tables Check the data validity in the standby table These four categories of commands are supplementary commands for the configuration rollback feature. Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-23 . All the data modified in "Modify" state is lost. run this command to get back normal running.6. when you want to stop and cancel the data modification. After confirmation. The BAM provides a 24-hour auto confirmation mechanism. 21. all the data in the standby area is cleared. The table changes back to be in "Normal" state. After confirmation. The execution flow of confirmation is similar to that of cancellation. CMT XXX This command is used to confirm the modification and validate it in the active area permanently. In "Modify" state. the table changes to be in "Normal" state. The operator who is authorized to run these commands can query the tables locked by another operator. The command does not affect the data in the active area. The only difference between auto confirmation and CMT XXX is that the system does not report the MML status for the former. The mapping relationship between the commands and the data tables is listed in Table 21-10.

21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Table 21-10 Query commands Command LST CNACLDBKP /CMP CNACLD /CHK CNACLD LST CNACLRBKP /CMP CNACLR /CHK CNACLR LST PFXPROBKP /CMP PFXPRO /CHK PFXPRO LST CLDPREANABKP /CMP CLDPREANA /CHK CLDPREANA LST IDPNPROBKP /CMP IDPNPRO /CHK IDPNPRO LST SRVNUMBKP /CMP SRVNUM /CHK SRVNUM LST CLIPROBKP /CMP CLIPRO /CHK CLIPRO LST CLCRPROBKP /CMP CLCRPRO /CHK CLCRPRO LST REDRCTANABKP /CMP REDRCTANA /CHK REDRCTANA LST INNUMPREPROBKP /CMP INNUMPREPRO /CHK INNUMPREPRO Name List Backup-area Call Prefix /Compare Call Prefixes in Active/Standby Way /Check Call Prefix List Backup-area Caller Number Analysis /Compare Calling Number Analysis in Active/Standby Way /Check Caller Number Analysis List Backup-area Call Prefix Processing /Compare Special Dialed Number Processing in Active/Standby Way /Check Call Prefix Processing List Backup-area Called Number Pre-analysis /Compare Called Number Pre-analysis Information in Active/Standby Way /Check Called Number Pre-analysis List Backup-area IDP Number Processing /Compare IDP Number Processing in Active/Standby Way /Check IDP Number Processing List Backup-area IN Service Number /Compare Intelligent Service Number Information In Active/Standby Way /Check IN Service Number List Backup-area CLIP Processing /Compare CLIP Called Number Correlation Processing in Active/Standby Way /Check CLIP Processing List Backup-area CLIP Called Number Correlation Processing /Compare CLIP Called Associated Processing in Active/Standby Way /Check CLIP Called Number Correlation Processing List Backup-area Redirection Number Analysis /Compare Forwarding Number Analysis Information in Active/Standby Way /Check Redirection Number Analysis List Backup-area Incoming Number Pre-processing /Compare Incoming Number Pre-processing in Active/Standby Way /Check Incoming Number Pre-processing 21-24 Huawei Technologies Proprietary Issue 02 (2007-06-10) .

HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature Command LST INCLRIDXBKP /CMP INCLRIDX /CHK INCLRIDX Name List Backup-area Incoming Caller Number Associated Processing /Compare Incoming Calling Number Associated Processing in Active/Standby Way /Check Incoming Caller Number Associated Processing List Backup-area Incoming Original Called Number Associated Processing /Compare Incoming Original Called Number Associated Processing in Active/Standby Way /Check Incoming Original Called Number Associated Processing LST INORICLDIDXBKP /CMP INORICLDIDX /CHK INORICLDIDX LST OUTNUMPREPROBKP /CMP OUTNUMPREPRO /CHK OUTNUMPREPRO LST OUTCLRIDXBKP /CMP OUTCLRIDX /CHK OUTCLRIDX List Backup-area Outgoing Number Pre-processing /Compare Outgoing Number Pre-processing in Active/Standby Way /Check Outgoing Number Pre-processing List Backup-area Outgoing Caller Number Associated Processing /Compare Outgoing Calling Number Associated Processing in Active/Standby Way /Check Outgoing Caller Number Associated Processing List Backup-area Outgoing Original Called Number Associated Processing /Compare Outgoing Original Called Number Associated Processing in Active/Standby Way /Check Outgoing Original Called Number Associated Processing LST OUTORICLDIDXBKP /CMP OUTORICLDIDX /CHK OUTORICLDIDX LST HDOVPROCBKP /CMP HDOVPROC /CHK HDOVPROC LST RTBKP /CMP RT /CHK RT LST RTANABKP /CMP RTANA /CHK RTANA LST TGLDBKP /CMP TGLD /CHK TGLD List Backup-area Handover Number Processing /Compare Handover Number Processing Tables in Active/Standby Way /Check Handover Number Processing List Backup Route /Compare Routes in Active/Standby Way /Check Route Table List Backup Route Analysis /Compare Route Analysis in Active/Standby Way /Check Route Analysis Table List Trunk Group Bearer /Compare Trunk Group Bearer in Active/Standby Way /Check Trunk Group Bearer Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-25 .

then the system assumes that the record exists only in the active area. The operator who is authorized to run the configuration rollback commands can query the standby tables locked by another operator. To improve work efficiency. you must run this command to check the data validity. For detailed record information. The attributes in the query result are almost the same as those of the active table. Three kinds of result can be returned: Records existing only in the active area Records existing only in the standby area Records that are inconsistent in the active and the standby areas The records are checked based on the service index field. 21-26 Huawei Technologies Proprietary Issue 02 (2007-06-10) . The data in the standby area. Only the tables in "Modify" or "Trial" state can be queried.21 Configuration Rollback Feature HUAWEI MSOFTX3000 Feature Description Command LST TGLDIDXBKP /CMP TGLDIDX /CHK TGLDIDX LST SCCPGTBKP /CMP SCCPGT /CHK SCCPGT Name List Trunk Group Bearer Index Backup /Compare Trunk Group Bearer Indexes in Active/Standby Way /Check Trunk Group Index Backup List Backup SCCP GT /Compare SCCP Global Titles in Active/Standby Way /Check the SCCP GT Table LST XXXBKP This command is used to list the standby table data. Only the fields related to services in a record are checked for inconsistency. then the system assumes that the record is an inconsistent one. The purpose of this command is to ensure the correctness of service data after the data is handed over to the active area. In the result. If the index of a record exists only in the active table. The operator who is authorized to run this command can query the standby tables locked by another operator. you must run the command LST XXX to query the active and the standby tables. This rule also applies to the data in the standby area. the configuration commands do not check the relationship between data tables in "Modify" state. Therefore. At the same time. CMP XXX This command is used to compare the data of the active and the standby areas when the table is in "Modify" or "Trial" state. must be valid before activation. but certain fields are inconsistent between the two areas. If a record exists in both the active and the standby areas. the BAM auto checks the tables with "Unknown" data every five seconds. CHK XXX This command is used to check the validity of the data in the standby area. The data can be checked only when the table is in "Modify" or "Trial" state. the service index fields of the inconsistent records are displayed. the validity check is performed between the target standby table and other active tables. Therefore. When several tables in "Modify" state rely on each other. however.

21.HUAWEI MSOFTX3000 Feature Description 21 Configuration Rollback Feature all of them may fail to pass the check. 21.7 Charging and CDR This feature does not affect the charging function and the CDR generation. If you confirm that the data is correct. you can run the command FACT XXX/FRLB XXX to hand over the data forcibly. 21. The BAM auto checks the data state of the tables that is not "Valid". The operator who is authorized to run this command can check the validity of data in the standby tables locked by another operator. you need not run the command CHK XXX to check the data before activation. If the data is proved "Valid".9 Reference Acronym/Abbreviation BAM LMT Full Name Back Administration Module Local Maintenance Terminal Issue 02 (2007-06-10) Huawei Technologies Proprietary 21-27 .8 Service Interaction None.

.....................................................4 Data Configuration Examples .....................................................................1 Requirements for NEs...2 Implementation Principle...........................22-5 22..............................................................2 Requirement for License............................HUAWEI MSOFTX3000 Feature Description Contents Contents 22 CAMEL4 Service .................................................................1 Conference Call ..........................22-2 22.................5.................22-6 22...........2 Data Configuration at the MSOFTX3000 Side..........................................................................................................3 Working Principle......................................................2 Internal Processing of the System .1 Service Description ...................................................................................................22-2 22................................................................2 Definition ..22-4 22.....................................................................................................................5..2 Availability ..............................................9 Service Interaction ..............................3 Applicable Versions....................................................22-18 22.....................................................5 Data Configuration..............................................................3...................................1.............3 External Interfaces ......................................22-19 22.....................22-14 22..........................................................................................................22-13 22.........22-6 22............3...................................5..............................................................................................................6 Application Limitations..................4 Service Flow............7 Charging and CDR ...................................1............................................................2..22-4 22..........................................................22-13 22..................3 CAMEL4 Simultaneous Ringing ..................................................22-9 22...........................8 Performance Measurement....................................................................................................................................................................22-5 22................2.................................................................................22-4 22..............................................22-13 22.........................................................22-10 22...........3 System Specifications .....................................................................................................................................................3 Data Configuration at the UMG8900 Side..........22-2 22.1 Overview.8................22-6 22....................................................................5.....................22-13 22.....................1 Specifications...................................................................1.............2 CAMEL4 IN RBT Service......5 Application Scenario ...........1 Functions of NEs.........4...................22-18 22............................................................................................................................22-6 22........22-18 22....................................................................4.............22-1 22.................................................................22-7 22...........................................................22-5 22.................................22-17 22.......................1........................8............................22-4 22...1 Function Code.........................4 Others.......................22-19 Issue 02 (2007-06-10) Huawei Technologies Proprietary i ............................................................................................................................................................................................................2......................................22-6 22..................................................................................................................1..............3.6 Service Management ..........................................................................................................................2.........................................................4 Benefits ................................4.22-4 22........................................................................................................................................................................................................................................................................................................................................................22-4 22.....1...

..............................................................22-21 22......................................2 Restriction Between Multiple CPH Operations in the CAMEL4 Service..............................2 Glossary......................................................................................9............................10 Reference.............. Acronyms and Abbreviation............................................................................................22-23 ii Huawei Technologies Proprietary Issue 02 (2007-06-10) ...............22-21 22.............................1 Restriction Between the Supplementary Services.............10....................22-19 22...........11 FAQ .....................................................................1 Specifications....9..........10..................................Contents HUAWEI MSOFTX3000 Feature Description 22...................................................22-20 22...22-21 22.........................

......................................... 22-11 Figure 22-4 CAP message flow of the simultaneous ringing with B answering the call first ....22-12 Figure 22-5 NC failure in the CAMEL4 ......................................................22-10 Figure 22-3 CAP message flow of the simultaneous ringing with C answering the call first .........HUAWEI MSOFTX3000 Feature Description Figures Figures Figure 22-1 CAP message flow of the CAMEL4 third-party call .......................22-8 Figure 22-2 CAP message flow of the IN RBT....................................................................................................................................22-23 Issue 02 (2007-06-10) Huawei Technologies Proprietary iii ....................................................

...22-20 iv Huawei Technologies Proprietary Issue 02